[posting only to bugreport - seems all others are subscribed] Quoting Niko Tyni (2017-06-26 20:02:01) > On Sun, Jun 25, 2017 at 09:57:14PM +0300, Niko Tyni wrote: >> On Fri, Jun 23, 2017 at 09:19:43PM +0100, Dominic Hargreaves wrote: > >>> I feel like we should try and not diverge further from upstream; >>> that seems almost guaranteed to end up with similar issues later. >> >> FWIW, I've scheduled a test rebuild of all the 679 >> libmodule-build-perl reverse build dependencies on perl.debian.net to >> get a feeling of how widespread this issue actually is. > > Not that widespread. We have 12 clearly affected packages, and a > couple that I'm not sure of. See below. Logs can be found at > > http://perl.debian.net/rebuild-logs/experimental/report.html > > (it's really a sid chroot, don't mind the "experimental" part.) > >> If it's bad enough, we should probably patch around it temporarily in >> any case and drop it later in a more controlled fashion. > > Given the low number of broken packages, it does look feasible to fix > those instead. I have no strong opinion atm. Others? > > Affected packages: > > libtest-name-fromline-perl_0.13-1 > libregexp-log-perl_0.06-3 > libperl-critic-perl_1.126-1 > libparser-mgc-perl_0.15-1 > libnet-proxy-perl_0.12-6 > libmoox-options-perl_4.023-1 > libjson-webtoken-perl_0.10-2 > libfurl-perl_3.08-2 > libdevel-callparser-perl_0.002-3 > libdevel-callchecker-perl_0.007-1 > libcatmandu-sru-perl_0.039-1 > libcatmandu-perl_1.0304-2
Hmm - 10 out of above 12 packages use CDBS. Might be totally unrelated, but suspicious... Also, only few of the CDBS-based packages were touched since 2015. For starters (admittedly without really understanding the issue here), let my simply go through and modernize those packages. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
