Hi, intrig...@debian.org (2019-07-26): > libcgi-application-perl build-depends on pkg-components. The Debian > Perl group has decided today that we don't want pkg-components to be > included in the Bullseye release, unless someone steps up and > volunteers to be its upstream maintainer: > https://bugs.debian.org/933110 > > If libcgi-application-perl is suitable for Bullseye, please either > port libcgi-application-perl away from pkg-components or consider > taking over its maintenance upstream.
Once autoremovals do their job in the next few weeks, libcgi-application-perl will be the only blocker left for removing pkg-components from testing. Since we decided a year ago that we don't want to ship pkg-components in Bullseye, I think it's now time to figure out what's going to happen about libcgi-application-perl. I took a look at the chain of rdeps (see below) and did not feel like negotiating the removal from testing of all these packages. It felt easier to just migrate CGI::Application away from pkg-components, so I did that. FTR, rdeps of CGI::Application as of today: - lots of CGI::Application plugins and development helpers - libsru-perl: tiny popcon, last upstream release in 2013, no recent activity on upstream's GitHub - libtitanium-perl: webapp framework, overlay on top of CGI::Application, last upstream release in 2009, tiny popcon, but I see Richard Hansen added themselves to Uploaders a few days ago, so perhaps you're particularly interested in Titanium, and thus transitively in having a working CGI::Application underlying stack? - webauth: orphaned - libhtml-wikiconverter-perl: one single optional feature needs CGI::Application but core functionality doesn't; it seems easy to drop that feature in the Debian packaging, in order to drop the dependency.