Work-needing packages report for Feb 25, 2022
The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1216 (new: 2) Total number of packages offered up for adoption: 190 (new: 0) Total number of packages requested help for: 61 (new: 1) Please refer to https://www.debian.org/devel/wnpp/ for more information. The following packages have been orphaned: php-htmlpurifier (#1006399), orphaned today Description: Standards-compliant HTML filter Reverse Depends: civicrm-common movim Installations reported by Popcon: 377 Bug Report URL: https://bugs.debian.org/1006399 php-react-promise (#1006400), orphaned today Description: lightweight implementation of CommonJS Promises/A for PHP Reverse Depends: composer php-react-cache php-react-dns php-react-http php-react-promise-stream php-react-promise-timer php-react-socket Installations reported by Popcon: 1456 Bug Report URL: https://bugs.debian.org/1006400 1214 older packages have been omitted from this listing, see https://www.debian.org/devel/wnpp/orphaned for a complete list. No new packages have been given up for adoption, but a total of 190 packages are awaiting adoption. See https://www.debian.org/devel/wnpp/rfa_bypackage for a complete list. For the following packages help is requested: [NEW] dhcpcd5 (#1006264), requested 2 days ago Description: DHCPv4, IPv6RA and DHCPv6 client with IPv4LL support Reverse Depends: dhcpcd-dbus netscript-2.4 Installations reported by Popcon: 2092 Bug Report URL: https://bugs.debian.org/1006264 apache2 (#910917), requested 1230 days ago Description: Apache HTTP Server Reverse Depends: apache2 apache2-ssl-dev apache2-suexec-custom apache2-suexec-pristine backuppc bfh-container-server courier-webadmin cvsweb debbugs-web doc-central (132 more omitted) Installations reported by Popcon: 99451 Bug Report URL: https://bugs.debian.org/910917 aufs (#963191), requested 614 days ago Description: driver for a union mount for Linux filesystems Reverse Depends: fsprotect Installations reported by Popcon: 9114 Bug Report URL: https://bugs.debian.org/963191 autopkgtest (#846328), requested 1912 days ago Description: automatic as-installed testing for Debian packages Reverse Depends: debci-worker sbuild-qemu Installations reported by Popcon: 1244 Bug Report URL: https://bugs.debian.org/846328 balsa (#642906), requested 3805 days ago Description: An e-mail client for GNOME Reverse Depends: balsa Installations reported by Popcon: 656 Bug Report URL: https://bugs.debian.org/642906 cargo (#860116), requested 1780 days ago Description: Rust package manager Reverse Depends: dh-cargo rust-all Installations reported by Popcon: 2787 Bug Report URL: https://bugs.debian.org/860116 courier (#978755), requested 420 days ago Description: Courier mail server Reverse Depends: courier-faxmail courier-filter-perl courier-imap courier-ldap courier-mlm courier-mta courier-pcp courier-pop courier-webadmin couriergrey (3 more omitted) Installations reported by Popcon: 889 Bug Report URL: https://bugs.debian.org/978755 cron (#984736), requested 354 days ago Description: new maintainer need Reverse Depends: apticron autolog backintime-common btrfsmaintenance buildd checksecurity clamtk cricket email-reminder exim4-base (20 more omitted) Installations reported by Popcon: 209702 Bug Report URL: https://bugs.debian.org/984736 cyrus-imapd (#921717), requested 1112 days ago Description: Cyrus mail system - IMAP support Reverse Depends: cyrus-admin cyrus-caldav cyrus-clients cyrus-dev cyrus-imapd cyrus-murder cyrus-nntpd cyrus-pop3d cyrus-replication Installations reported by Popcon: 416 Bug Report URL: https://bugs.debian.org/921717 debtags (#962579), requested 624 days ago Description: Debian Package Tags support tools Reverse Depends: packagesearch Installations reported by Popcon: 1475 Bug Report URL: https://bugs.debian.org/962579 dee (#831388), requested 2050 days ago Description: model to synchronize mutiple instances over DBus Reverse Depends: dee-tools gir1.2-dee-1.0 gir1.2-unity-7.0 libdee-dev libunity-dev libunity-protocol-private0 libunity-tools libunity9 zeitgeist-core Installations reported by Popcon: 42979 Bug Report URL: https://bugs.debian.org/831388 developers-reference (#759995), requested 2735 days ago Description: guidelines and information for Debian de
Re: Why? "Marked for autoremoval on 24 March due to xdelta3: #965883"
Thanks -Original Message- From: Simon McVittie ... If anyone has a better wording for the autoremoval message, that can express this message as clearly and concisely as possible: - the package you maintain does not have a RC bug itself - but it (recursively) (build-)depends on xdelta3, which has RC bug #965883 >From apt-rdepends -b ``` fonts-wqy-microhei Build-Depends: debhelper (>= 10) Build-Depends: xdelta3 ``` only one out of 56K packages :-) I saw 2 overflow errors on recursions during this check. Chinese font... no wonder only doc packages with Chinese translation in pdf was affected. - we cannot remove xdelta3 from testing without also removing the packages that (build-)depend on xdelta3 from testing - therefore the package you maintain is going to be autoremoved, unless someone fixes #965883 in an xdelta3 upload sufficiently soon then I'm sure the release team accept merge requests. > This is probably very academic now since Andreas Tille has uploaded a fixed > xdelta3 package today. Now that I know that the new xdelta3 is uploaded, I am OK. Anyway, thanks all. Osamu
Re: Why? "Marked for autoremoval on 24 March due to xdelta3: #965883"
On Thu, 24 Feb 2022 at 14:48:42 +0100, Andreas Metzler wrote: > Afaiui xdelta3 was (see below) rc-buggy, because it used dh 5 or 6 and > was therefore marked for autoremoval. Afaik autoremovals are recursive, > i.e. we do not make packages uninstallable by removing their > dependencies but instead also remove these depending packages. I think > this also extends to build-dependencies, we do not want unbuildable > packages in testing so these would be removed, too. Yes, all of that is correct. If anyone has a better wording for the autoremoval message, that can express this message as clearly and concisely as possible: - the package you maintain does not have a RC bug itself - but it (recursively) (build-)depends on xdelta3, which has RC bug #965883 - we cannot remove xdelta3 from testing without also removing the packages that (build-)depend on xdelta3 from testing - therefore the package you maintain is going to be autoremoved, unless someone fixes #965883 in an xdelta3 upload sufficiently soon then I'm sure the release team accept merge requests. > This is probably very academic now since Andreas Tille has uploaded a fixed > xdelta3 package today. Hopefully yes! smcv
Re: Why? "Marked for autoremoval on 24 March due to xdelta3: #965883"
On 2022-02-24 Osamu Aoki wrote: > I favor moving away from pre-dh7 packages and I support people pushing for > it. But I > am in intriguing situation with this effort. Can someone help me. > At: https://udd.debian.org/cgi-bin/autoremovals.cgi > I see: > Osamu Aoki >debian-history: buggy deps xdelta3, flagged for removal in 28.4 days >debian-reference: buggy deps xdelta3, flagged for removal in 28.4 days >maint-guide: buggy deps xdelta3, flagged for removal in 28.4 days > These are all COMPAT=13 packages with d/control having: > > Build-Depends: debhelper-compat (= 13) > Thus, it doesn't make sense to be connected to > > xdelta3: Removal of obsolete debhelper compat 5 and 6 in bookworm > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965883 > Also, these packages are not even listed in the original hit list: > https://lists.debian.org/debian-devel/2020/07/msg00065.html > I have been using at least compat=8 since 2013 for 2 of these packages > and compat=7 since 2010 for another. So I can't figure out why these > packages are suddenly flagged. [...] Hello, Afaiui xdelta3 was (see below) rc-buggy, because it used dh 5 or 6 and was therefore marked for autoremoval. Afaik autoremovals are recursive, i.e. we do not make packages uninstallable by removing their dependencies but instead also remove these depending packages. I think this also extends to build-dependencies, we do not want unbuildable packages in testing so these would be removed, too. The respective set of xdelta3 is probly huge, it includes e.g. pristine-tar. I suspect debian-history et al are part of this set. This is probably very academic now since Andreas Tille has uploaded a fixed xdelta3 package today. - Just doublecheck after the next britney run whether debian-history ist still marked for removal. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Re: Why? "Marked for autoremoval on 24 March due to xdelta3: #965883"
On Thu, Feb 24, 2022 at 10:09:23PM +0900, Osamu Aoki wrote: > Hi, > > I favor moving away from pre-dh7 packages and I support people pushing for > it. But I > am in intriguing situation with this effort. Can someone help me. > > At: https://udd.debian.org/cgi-bin/autoremovals.cgi > > I see: > > Osamu Aoki >debian-history: buggy deps xdelta3, flagged for removal in 28.4 days >debian-reference: buggy deps xdelta3, flagged for removal in 28.4 days >maint-guide: buggy deps xdelta3, flagged for removal in 28.4 days These say "buggy deps". It means they are not affected themselves but they (maybe indirectly) depend on an affected package. -- WBR, wRAR signature.asc Description: PGP signature
Why? "Marked for autoremoval on 24 March due to xdelta3: #965883"
Hi, I favor moving away from pre-dh7 packages and I support people pushing for it. But I am in intriguing situation with this effort. Can someone help me. At: https://udd.debian.org/cgi-bin/autoremovals.cgi I see: Osamu Aoki debian-history: buggy deps xdelta3, flagged for removal in 28.4 days debian-reference: buggy deps xdelta3, flagged for removal in 28.4 days maint-guide: buggy deps xdelta3, flagged for removal in 28.4 days These are all COMPAT=13 packages with d/control having: > Build-Depends: debhelper-compat (= 13) Thus, it doesn't make sense to be connected to > xdelta3: Removal of obsolete debhelper compat 5 and 6 in bookworm https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965883 Also, these packages are not even listed in the original hit list: https://lists.debian.org/debian-devel/2020/07/msg00065.html I have been using at least compat=8 since 2013 for 2 of these packages and compat=7 since 2010 for another. So I can't figure out why these packages are suddenly flagged. The last packaging update of debian-history was in 2021 by Bdale Garbee (not me). So this can't be caused by a silly oversight repeated by a single DD. Does any one have idea what is happening? To whom should I raise issue to avoid being removed? Or should I have to fix something? Regards, Osamu FYI: Since all these build PDF files via the TeTex tool chain, the building of these packages eats a lot of memory even though these have no big programs to build.
GLOBOScan Barcode Fair
Hi, I'm following up to confirm, if you are interested acquiring the Attendee list. GLOBOScan Barcode Fair Counts: 1.500 Each Record of the Attendee Includes: Client Name, Business Name, Title, Email Address, Phone Number, and Web Address etc. Let me know your thoughts, so that I can send discount cost & additional information. Regards, Brinley Hines | Event Analyst
