<div dir="auto"><div>I let the dust a little rest before replying. So far so good.<br><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Le jeu. 14 août 2025, 14:24, gregor herrmann <<a href="mailto:gregoa@debian.org">gregoa@debian.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, 12 Aug 2025 21:07:46 +0200, Alexandre Detiste wrote:<br>
<br>
Let's have a look:<br>
<br>
> diff --git a/lib/Debian/PkgPerl/Util.pm b/lib/Debian/PkgPerl/Util.pm<br>
> index c670425..a51d9c9 100644<br>
> --- a/lib/Debian/PkgPerl/Util.pm<br>
> +++ b/lib/Debian/PkgPerl/Util.pm<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Indeed, maybe some proprietary tooling import this library, no need to needlessly break their workflow</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Now for the other cases:<br>
<br>
> diff --git a/examples/mass-commit b/examples/mass-commit<br>
> index 5ccb3a8..5f5e945 100755<br>
> --- a/examples/mass-commit<br>
> +++ b/examples/mass-commit<br>
> @@ -11,7 +11,6 @@<br>
> <br>
> set -eu<br>
> <br>
> -CDBS=0<br>
> DEBUG=0<br>
> <br>
> usage() {<br>
> @@ -20,7 +19,6 @@ usage() {<br>
> echo<br>
> echo " Parameters:"<br>
> echo " -h help"<br>
> - echo " -c exclude CDBS packages"<br>
> echo " -d debug / dry-run"<br>
> exit 0<br>
> }<br>
> @@ -56,9 +54,6 @@ die() {<br>
> <br>
> while getopts cdh OPT; do<br>
> case "$OPT" in<br>
> - c)<br>
> - CDBS=1<br>
> - ;;<br>
> d)<br>
> DEBUG=1<br>
> ;;<br>
> @@ -79,9 +74,6 @@ for PKG in $(ls -1d */ | sed -e 's:/$::') ; do<br>
> dh_testdir || { skip "$PKG doesn't look like a debian package.";<br>
> continue; }<br>
> [ -d .git ] || { skip "No .git directory in $PKG."; continue; }<br>
> git checkout master<br>
> - if [ "$CDBS" = "1" ] ; then<br>
> - grep -q cdbs debian/control && { skip "Skipping CDBS package<br>
> $PKG."; continue; }<br>
> - fi<br>
> <br>
> # start real work<br>
> # ADJUSTME start<br>
> diff --git a/scripts/new-upstream b/scripts/new-upstream<br>
> index f72db5e..0067777 100755<br>
> --- a/scripts/new-upstream<br>
> +++ b/scripts/new-upstream<br>
> @@ -115,7 +115,6 @@ foreach (@newupstream) {<br>
> unless -f $controlfile;<br>
> my $control = Dpkg::Control::Info->new($controlfile); #<br>
> Dpkg::Control object<br>
> my $build_depends = $control->get_source()->{'Build-Depends'}; # string!<br>
> - my $cdbs = $build_depends =~ /cdbs/m;<br>
> <br>
> # categorize new upstream releases<br>
> my $pkg = {<br>
> @@ -127,13 +126,12 @@ foreach (@newupstream) {<br>
> push @{ $new_categorized->{'ignore-version'} }, $pkg if $ignore_version;<br>
> push @{ $new_categorized->{'waits-for'} }, $pkg if $waits_for;<br>
> push @{ $new_categorized->{'problem'} }, $pkg if $problem;<br>
> - push @{ $new_categorized->{'cdbs'} }, $pkg if $cdbs;<br>
> push @{ $new_categorized->{'default'} }, $pkg<br>
> - unless ( $ignore_version or $waits_for or $problem or $cdbs );<br>
> + unless ( $ignore_version or $waits_for or $problem );<br>
> <br>
> }<br>
> <br>
> -my @categories = (qw/default cdbs problem ignore-version waits-for/);<br>
> +my @categories = (qw/default problem ignore-version waits-for/);<br>
> foreach (@categories) {<br>
> my $category = $_;<br>
> next unless defined( $new_categorized->{$category} );<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
For historical reasons both examples/mass-commit and dpt-new-upstream <br>
either allow one to or unconditionally special-case packages using <br>
cdbs. The resaon for this is that there was a strong correlation <br>
between preference for using cdbs and preference for using specific <br>
other packaging styles, and it made sense (to me) to exempt them from <br>
routine updates and common changes. -- Not sure if this still is the <br>
case but OTOH this special casing also doesn't cause any harm and is <br>
no active promotion of cdbs. -- On yet another other hand :) if there <br>
are (soon) no more cdbs packages it also has no function within the <br>
team anymore.</blockquote></div></div><div dir="auto"><br></div><div dir="auto">The goal is that soonish the only packages left using CDBS will be the one from the Haskell monorepo.</div><div dir="auto"><br></div><div dir="auto">They use their own tooling for mass-changes.</div><div dir="auto"><br></div><div dir="auto">The other CDBS-using packages have been mostly neglected for a very long time and need a complete overall.</div><div dir="auto"><br></div><div dir="auto">So I think this has no function for Debian as a whole. If they were proprietary mass user of CDBS I d be sorry for them but they have two more years from now to adapt.</div><div dir="auto"><br></div><div dir="auto">I m myself a mass user of little known of dh-cruft (writen in Perl) in my own proprietary Debian derivative, so this kind of scenario is not totaly impossible... but well.</div><div dir="auto"><br></div><div dir="auto">The cleansing of old Python libraries in Debian did broke some external Calibre plugins, that happens all the time. A well curated distribution should lead the way and don't encourage users to depends forever on abandonned tech.</div><div dir="auto"><br></div><div dir="auto">Have a nice day</div><div dir="auto"><br></div><div dir="auto"><br></div></div>