Bug#905996: nmu: clsync_0.4.1-1
On 2018-08-15 05:45, Niels Thykier wrote: > Aurelien Jarno: > [...] > >> then removing clsync from testing is also an option > >> AFAICT. > >> > >> I am considering since clsync has had its FTBFS bug against sid for > >> almost 2 years now with no reaction from its maintainers. > > > > That solution has the same result than the binNMU, so that's also fine > > for me. I would leave the decision about what is the best way to achieve > > that to the release team. > > > > Thanks, > > Aurelien > > > > Could you please file an RC bug against clsync that affects the > *testing* version (tags sid + buster if that version is also in stable) > about this issue? I have just filled #906307 for that. Thanks, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#905996: nmu: clsync_0.4.1-1
Aurelien Jarno: > [...] >> >> Hi Aurelien, >> >> If the goal is to make testing free of packages (Pre-)Depending on >> multiarch-support > > Yes, that's exactly the goal, that way we can just stop building the > package in the next upload. There are still a few depending packages > in sid/experimental, but given the bug reports have been sent with > patches attached more than one year ago, I don't mind breaking them. > Ok, thanks for confirming. >> then removing clsync from testing is also an option >> AFAICT. >> >> I am considering since clsync has had its FTBFS bug against sid for >> almost 2 years now with no reaction from its maintainers. > > That solution has the same result than the binNMU, so that's also fine > for me. I would leave the decision about what is the best way to achieve > that to the release team. > > Thanks, > Aurelien > Could you please file an RC bug against clsync that affects the *testing* version (tags sid + buster if that version is also in stable) about this issue? I am happy to consider removing clsync earlier than the auto-removal would have if time is an issue. Thanks, ~Niels
Bug#905996: nmu: clsync_0.4.1-1
Hi Niels, On 2018-08-14 17:53, Niels Thykier wrote: > Control: tags -1 moreinfo > > Aurelien Jarno: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: binnmu > > > > Hi release team, > > > > One of the goal of the glibc team for buster is to get rid of the > > multiarch-support package, given that multiarch support in the dynamic > > loader is fully supported in debian for a long time. Debhelper used to > > add this dependency, but it's not the case anymore. > > > > clsync is one out of two packages left in buster, the other one, > > gtk2-engines-oxygen, should hopefully migrate in the next days. > > Unfortunately clsync has an RC bug in sid, which prevents it to migrate > > to buster. This RC bug is not present in buster, so the package hasn't > > been autoremoved from there. > > > > Therefore the easiest way to fix the issue is to trigger a binNMU in > > *buster*, against a "recent" debhelper: > > > > nmu clsync_0.4.1-1 . ANY . buster . -m "Rebuild to remove the > > pre-dependency on multiarch-support" > > > > Thanks, > > Aurelien > > > > [...] > > Hi Aurelien, > > If the goal is to make testing free of packages (Pre-)Depending on > multiarch-support Yes, that's exactly the goal, that way we can just stop building the package in the next upload. There are still a few depending packages in sid/experimental, but given the bug reports have been sent with patches attached more than one year ago, I don't mind breaking them. > then removing clsync from testing is also an option > AFAICT. > > I am considering since clsync has had its FTBFS bug against sid for > almost 2 years now with no reaction from its maintainers. That solution has the same result than the binNMU, so that's also fine for me. I would leave the decision about what is the best way to achieve that to the release team. Thanks, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: Re: Bug#905996: nmu: clsync_0.4.1-1
Processing control commands: > tags -1 moreinfo Bug #905996 [release.debian.org] nmu: clsync_0.4.1-1 Added tag(s) moreinfo. -- 905996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905996: nmu: clsync_0.4.1-1
Control: tags -1 moreinfo Aurelien Jarno: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > Hi release team, > > One of the goal of the glibc team for buster is to get rid of the > multiarch-support package, given that multiarch support in the dynamic > loader is fully supported in debian for a long time. Debhelper used to > add this dependency, but it's not the case anymore. > > clsync is one out of two packages left in buster, the other one, > gtk2-engines-oxygen, should hopefully migrate in the next days. > Unfortunately clsync has an RC bug in sid, which prevents it to migrate > to buster. This RC bug is not present in buster, so the package hasn't > been autoremoved from there. > > Therefore the easiest way to fix the issue is to trigger a binNMU in > *buster*, against a "recent" debhelper: > > nmu clsync_0.4.1-1 . ANY . buster . -m "Rebuild to remove the pre-dependency > on multiarch-support" > > Thanks, > Aurelien > > [...] Hi Aurelien, If the goal is to make testing free of packages (Pre-)Depending on multiarch-support, then removing clsync from testing is also an option AFAICT. I am considering since clsync has had its FTBFS bug against sid for almost 2 years now with no reaction from its maintainers. Thanks, ~Niels
Bug#905996: nmu: clsync_0.4.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi release team, One of the goal of the glibc team for buster is to get rid of the multiarch-support package, given that multiarch support in the dynamic loader is fully supported in debian for a long time. Debhelper used to add this dependency, but it's not the case anymore. clsync is one out of two packages left in buster, the other one, gtk2-engines-oxygen, should hopefully migrate in the next days. Unfortunately clsync has an RC bug in sid, which prevents it to migrate to buster. This RC bug is not present in buster, so the package hasn't been autoremoved from there. Therefore the easiest way to fix the issue is to trigger a binNMU in *buster*, against a "recent" debhelper: nmu clsync_0.4.1-1 . ANY . buster . -m "Rebuild to remove the pre-dependency on multiarch-support" Thanks, Aurelien -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
