
| Msg # 1102 of 1179 on ZZLI4422, Wednesday 10-21-25, 10:14 |
| From: =?UTF-8?B?T3R0BYBLZWVDPGZ |
| To: ALL |
| Subj: Re: pcre2 10.47-1 uploaded to experiment |
From: otto@debian.org Hi! ... > >> I'll be running builds in ci for php8.4 and glib2.0, but please do test > >> your package against the new pcre2 if it makes extensive and/or unusual > >> use of pcre2 features. > >> > >> Assuming all is good, I'll upload to unstable in a couple of weeks or so. > > > > Please run ratt manually or via > > (https://salsa.debian.org/salsa-ci-team/pipeline#build-rever e-dependencies) > > to see how many reverse dependency builds this change breaks. If you > > break many packages, you should probably postpone uploading to > > unstable for a longer time and file bugs on your reverse deps that > > need to test building in experimental and fix compatibility issues. > > I don't have the computing power available to re-build all of pcre2's > reverse dependencies, particularly given glib2.0 and php8.4 (both of > which do make extensive use of pcre2 and have tripped over changes in > the past) have built just fine. You don't need to have computing available yourself, you can use Salsa CI (see link above) or Debusine (as Timo already did, thanks to him!). If any of the dependencies don't compile, it will lead to a fails-to-build-from-sources bug, which will eventually trigger autoremoval from Debian. We already have ~2000 packages pending autoremoval mostly due to build failures (https://udd.debian.org/cgi-bin/autoremovals.cgi) and we should be diligent in updates and thoughtful on what is reasonable to push through in what timeframe. Testing what happens to your reverse dependencies before uploading is worth the extra effort. --- SoupGate-Win32 v1.05 * Origin: you cannot sedate... all the things you hate (1:229/2) |
328,084 visits
(c) 1994, bbs@darkrealms.ca