Bug#979397: transition: ntfs-3g
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi RMs, Only three packages are affected: partclone, testdisk and wimlib. Test rebuilds are fine on amd64 but as freeze is around the corner I can test it on more architectures if needed. The main note that it has an udeb so probably KiBi also would like to ACK / NACK this transition. Regards, Laszlo/GCS
Re: Release status of i386 for Bullseye and long term support for 3 years?
On Tue, Jan 5, 2021 at 10:24 PM Lou Poppler wrote: > I would like to help. ... > Please suggest any debian lists or IRC channels or webpages I should look at, > or other steps to make myself useful. Thanks. The general page for how to help Debian is here: https://www.debian.org/intro/help More specifically, you could: Join the #debian-cd, #debian-boot, #debian-buildd, #debian-ftp, #debian-ports (introduce yourself here at minimum), #debian-release and #debian-toolchain IRC channels (and maybe #debian-devel). There isn't really a mailing list for i386, so maybe use debian-devel or debian-amd64. Help test the installer: https://wiki.debian.org/Teams/DebianCD/ReleaseTesting Install and enable popularity-contest on your i386 machines and submit to the Linux hardware database. Encourage other i386 users to do the same. https://popcon.debian.org/ https://wiki.debian.org/Hardware/Database https://linux-hardware.org/ Create install wiki pages for the hardware you own: https://wiki.debian.org/InstallingDebianOn Help maintain the installer and documentation: https://wiki.debian.org/DebianInstaller https://www.debian.org/releases/stable/i386/ Create a new i386 page in the Ports area on the wiki based on the template: https://wiki.debian.org/Ports https://wiki.debian.org/PortTemplate Maintain the other documentation about the i386 port: https://www.debian.org/ports/i386/ https://wiki.debian.org/i386 Create a scheme to tag i386-specific bugs (maybe user debian-devel, usertag i386) and maintain the installer usertags for debian-boot and the port usertags. Work on fixing the bugs tagged i386. https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debian-b...@lists.debian.org=i386 https://wiki.debian.org/Teams/Debbugs/ArchitectureTags Work on increasing the amount of software that builds and works on i386: https://udd.debian.org/cgi-bin/ftbfs.cgi?arch=i386 https://buildd.debian.org/status/architecture.php?a=i386 https://tests.reproducible-builds.org/debian/testing/index_suite_i386_stats.html https://ci.debian.net/status/ Follow #debian and #debian-next and help out any i386 users asking questions (although there aren't (m)any in practice). -- bye, pabs https://wiki.debian.org/PaulWise
Bug#979341: transition: gpsd
Control: forwarded -1 https://release.debian.org/transitions/html/auto-gpsd.html Control: tags -1 + confirmed On 2021-01-05 16:15:57 +0100, Bernd Zeimetz wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi release team, > > > just in time gpsd upstream pushed the first release candidate of 3.22, > which is due to be released within the next few days. > > As usual its comes with a soname bump and a small api change, so I've > uploaded -rc1 to experimental, ready to upload to unstable. > > Only one build-rdep fails to build against it (foxtrotgps, fix in > progress, #979252), as you can see here. > > https://salsa.debian.org/debian-gps-team/pkg-gpsd/-/pipelines/215214 > > Please ack the start of the transition. Please go ahead. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: Bug#979341: transition: gpsd
Processing control commands: > forwarded -1 https://release.debian.org/transitions/html/auto-gpsd.html Bug #979341 [release.debian.org] transition: gpsd Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-gpsd.html'. > tags -1 + confirmed Bug #979341 [release.debian.org] transition: gpsd Added tag(s) confirmed. -- 979341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#979320: transition: xmltooling
Processing control commands: > tags -1 + confirmed Bug #979320 [release.debian.org] transition: xmltooling Added tag(s) confirmed. -- 979320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979320: transition: xmltooling
Control: tags -1 + confirmed
On 2021-01-05 10:47:56 +0100, Ferenc Wágner wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> Dear Release Team,
>
> The recent 3.2 release of the Shibboleth SP is a minor release, but due
> to the internal structure of the stack it entails the usual three
> transitions for xmltooling, opensaml and shibboleth-sp. I'd like to do
> successive sourceful uploads for these (the updated packages are already
> in experimental). The two other impacted packages build fine without any
> change: shibboleth-resolver and moonshot-gss-eap. The auto-{xmltooling,
> opensaml,shibboleth-sp} trackers are good. I'm ready to upload to
> unstable on your word.
Please go ahead
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#979043: marked as done (transition: dart)
Your message dated Wed, 6 Jan 2021 01:03:46 +0100 with message-id and subject line Re: Bug#979043: transition: dart has caused the Debian Bug report #979043, regarding transition: dart to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear release team, I would like to transition the dart library. I've successfully rebuild and tested it's only reverse build dependency: gazebo. The automatically generated ben file looks fine. Cheers Jochen --- End Message --- --- Begin Message --- On 2021-01-02 12:20:52 +0100, Jochen Sprickerhof wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Dear release team, > > I would like to transition the dart library. I've successfully rebuild > and tested it's only reverse build dependency: gazebo. > > The automatically generated ben file looks fine. The old binaries got removed. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#978730: marked as done (transition: fcl)
Your message dated Wed, 6 Jan 2021 01:03:11 +0100 with message-id and subject line Re: Bug#978730: transition: fcl has caused the Debian Bug report #978730, regarding transition: fcl to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 978730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: transition: fcl Package: release.debian.org User: release.debian@packages.debian.org Usertags: transition Severity: normal Dear release team, I would like to ask a transition slot for the fcl library. Upstream published a new version with a soname bump. We have had a lot of problems to build in many archs, but the last one, (mipsel) finally worked with the last version of the package. The only package that depends on fcl is dart, and I have built it (amd64). Please accept the transition slot. Best regards, Leopold - Ben file: title = "fcl"; is_affected = .depends ~ /\b(libfcl0\.6|libfcl0\.5)\b/ is_good = .depends ~ /\b(libfcl0\.6)\b/ is_bad = .depends ~ /\b(libfcl0\.5)\b/ https://buildd.debian.org/status/package.php?p=fcl=experimental -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On 2020-12-31 00:46:32 +0100, Leopold Palomo-Avellaneda wrote: > Subject: transition: fcl > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: transition > Severity: normal > > Dear release team, > > I would like to ask a transition slot for the fcl library. Upstream > published a new version with a soname bump. > > We have had a lot of problems to build in many archs, but the last one, > (mipsel) finally worked with the last version of the package. > > The only package that depends on fcl is dart, and I have built it (amd64). > > Please accept the transition slot. The old binary got removed. Closing. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#978155: marked as done (transition: libqb)
Your message dated Wed, 6 Jan 2021 01:05:20 +0100 with message-id and subject line Re: Bug#978155: transition: libqb has caused the Debian Bug report #978155, regarding transition: libqb to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 978155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear Release Team, I'd like to transition to libqb version 2. The dependency list is fairly short, and mostly contains packages under the HA Team umbrella. The only breakage is caused by symbols file changes, which I'm ready to fix by sourceful uploads of corosync and pacemaker. The kronosnet package will also receive a sourceful upload to use the new binary package doxygen2man. Altogether I rebuilt the following packages in preparation: kronosnet (with source changes) corosync (with source changes) corosync-qdevice pacemaker (with source changes) dlm booth fence-virt sbd ocfs2-tools lvm2 usbguard The auto-libqb tracker seems usable just too broad. Ben file: title = "libqb"; is_affected = .depends ~ "libqb0" | .depends ~ "libqb100"; is_good = .depends ~ "libqb100"; is_bad = .depends ~ "libqb0"; When you see fit, I'll upload libqb, kronosnet, corosync and pacemaker in succession, then request the necessary binNMUs. -- Thanks, Feri. --- End Message --- --- Begin Message --- On 2020-12-26 19:43:53 +0100, Ferenc Wágner wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Dear Release Team, > > I'd like to transition to libqb version 2. The dependency list is > fairly short, and mostly contains packages under the HA Team umbrella. > The only breakage is caused by symbols file changes, which I'm ready to > fix by sourceful uploads of corosync and pacemaker. The kronosnet > package will also receive a sourceful upload to use the new binary > package doxygen2man. Altogether I rebuilt the following packages in > preparation: > > kronosnet (with source changes) > corosync (with source changes) > corosync-qdevice > pacemaker (with source changes) > dlm > booth > fence-virt > sbd > ocfs2-tools > lvm2 > usbguard > > The auto-libqb tracker seems usable just too broad. The old binaries got removed. Closing Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#976609: marked as done (transition: capstone)
Your message dated Wed, 6 Jan 2021 01:04:40 +0100 with message-id and subject line Re: Bug#976609: transition: capstone has caused the Debian Bug report #976609, regarding transition: capstone to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear release team, please schedule a transition to capstone4. While rebuilding all reverse dependencies with capstone4, I have only found problems that are not related to Capstone. Affected pacakges: - radare2 - wcc - qemu - edb-debugger (unrelated FTBFS: #975146) - uftrace (unrelated FTBFS: #966988) Ben file: Affected: .build-depends ~ /libcapstone-dev/ Good: .depends ~ /libcapstone4/ Bad: .depends ~ /libcapstone3/ Cheers, -Hilko --- End Message --- --- Begin Message --- On 2020-12-05 19:56:35 +0100, Hilko Bengen wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Dear release team, > > please schedule a transition to capstone4. While rebuilding all reverse > dependencies with capstone4, I have only found problems that are not > related to Capstone. > > Affected pacakges: > - radare2 > - wcc > - qemu > - edb-debugger (unrelated FTBFS: #975146) > - uftrace (unrelated FTBFS: #966988) > > Ben file: > > Affected: .build-depends ~ /libcapstone-dev/ > Good: .depends ~ /libcapstone4/ > Bad: .depends ~ /libcapstone3/ The old binary packages got removed. Closing. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#979084: transition: hamlib
Re: To 979...@bugs.debian.org > I'll upload the two rdeps needing source changes and then provide a > list for binnmus for the rest. Here we go: cubicsdr direwolf fldigi freedv klog qsstv soapyaudio soundmodem tucnak xlog Plus for the limesuite transition: gr-limesdr osmo-trx Thanks, Christoph
Re: Release status of i386 for Bullseye and long term support for 3 years?
On Wed, 2020-12-30 at 14:27 +, Andrew M.A. Cater wrote: > On Mon, Dec 07, 2020 at 07:55:11PM +, Andrew M.A. Cater wrote: > > Dear release team > > > > There seems to be only one maintainer. > > > > Still true as far as I can see - others have stepped up to test i386 > executables but no more developers. > > > Is i386 going to be supportable for the next 3 1/2 years and buildable for > > that long (given that almost all machines are now 64 bit capable and we're > > having to build some packages on amd64 for i386 - per ballombe)? I would like to help. I have one "Pentium III (Katmai)" based Gateway2000 machine, with debian_etch, 384MB ram (max possible I think), ethernet, USB1.6, DVD-RW, 3.5" FDD, IDE disks; and one "VIA C7-M" Pentium M based HP 2133 netbook, Jessie installed, 512MB ram, ethernet, USB2.0, 4GB SSD, 32GB SD-card, "Express Card/54" slot, WiFi+Bluetooth; (and one working 486, running an ancient 2.0.30 kernel I compiled myself; plus some more modern machines we actually use here). I volunteer using those pentiums for testing and/or building. I have pretty good internet speeds with pretty large monthly limits here. Both pentiums can run Buster live systems (needing swapspace for DEs), and can be re-installed with any desired releases. Various external USB disks are available. I also volunteer some amount of my own time for this cause -- I have somewhat rusty but hopefully still serviceable experience coding, reviewing code, building, integrating, testing, debugging, troubleshooting. Please suggest any debian lists or IRC channels or webpages I should look at, or other steps to make myself useful. Thanks.
Bug#979341: transition: gpsd
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi release team, just in time gpsd upstream pushed the first release candidate of 3.22, which is due to be released within the next few days. As usual its comes with a soname bump and a small api change, so I've uploaded -rc1 to experimental, ready to upload to unstable. Only one build-rdep fails to build against it (foxtrotgps, fix in progress, #979252), as you can see here. https://salsa.debian.org/debian-gps-team/pkg-gpsd/-/pipelines/215214 Please ack the start of the transition. Thanks, Bernd Ben file: title = "gpsd"; is_affected = .depends ~ /^lib.*gps.*26$/ | .depends ~ /^lib.*gps.*28$/; is_good = .depends ~ /^lib.*gps.*28$/; is_bad = .depends ~ /^lib.*gps.*26$/; -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#979145: marked as done (RM: xfce4-equake-plugin/1.3.8.1-2+b2)
Your message dated Tue, 5 Jan 2021 10:55:09 +0100 with message-id and subject line Re: Bug#979145: RM: xfce4-equake-plugin/1.3.8.1-2+b2 has caused the Debian Bug report #979145, regarding RM: xfce4-equake-plugin/1.3.8.1-2+b2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm X-Debbugs-Cc: andr...@e-quake.org Hi, xfce4-equake-plugin is not compatible with the 4.16 release of the Xfce desktop environement, and thus FTBFS in unstable right now, and prevents migration of the xfce4-panel package (and xfce4 metapckage). There's an open bug about that (#978237) as well as a request for the package to be ported to latest library (#977626) but the package seems unmaintained upstream and in Debian (it's not under the pkg-xfce team umbrella). Right now I think the most sensible decision would be to remove it from testing and let xfce4-panel migrate. Maybe Jeroen could chime in but I'm afraid he's not very active at the moment. Regards, -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- On 2021-01-03 15:36:49 +0100, Yves-Alexis Perez wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: rm > X-Debbugs-Cc: andr...@e-quake.org > > Hi, > xfce4-equake-plugin is not compatible with the 4.16 release of the Xfce > desktop environement, and thus FTBFS in unstable right now, and prevents > migration of the xfce4-panel package (and xfce4 metapckage). There's an > open bug about that (#978237) as well as a request for the package to be > ported to latest library (#977626) but the package seems unmaintained > upstream and in Debian (it's not under the pkg-xfce team umbrella). > > Right now I think the most sensible decision would be to remove it from > testing and let xfce4-panel migrate. Maybe Jeroen could chime in but I'm > afraid he's not very active at the moment. I added the removal hint yesterday and xfce4-panel migrated to testing. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#979320: transition: xmltooling
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Dear Release Team,
The recent 3.2 release of the Shibboleth SP is a minor release, but due
to the internal structure of the stack it entails the usual three
transitions for xmltooling, opensaml and shibboleth-sp. I'd like to do
successive sourceful uploads for these (the updated packages are already
in experimental). The two other impacted packages build fine without any
change: shibboleth-resolver and moonshot-gss-eap. The auto-{xmltooling,
opensaml,shibboleth-sp} trackers are good. I'm ready to upload to
unstable on your word.
--
Thanks,
Feri.
Processed: Re: Bug#979303: transition: ppp
Processing control commands: > tags -1 + confirmed Bug #979303 [release.debian.org] transition: ppp Added tag(s) confirmed. -- 979303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979303: transition: ppp
Control: tags -1 + confirmed On 2021-01-05 00:19:13 +, Chris Boot wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi release team folks, > > There has been a new upstream release of ppp (2.4.9). I know this is > very soon after my upload of 2.4.8 and its transition, but I'm also both > aware of the transition freeze that's coming up and a large number of > improvements in the new release. The 2.4.8 transition is not done yet … we are waiting for gnutls28 to be ready. So please go ahead. Cheers > > Before I go ahead and update all my packaging, is it likely that we can > get ppp 2.4.9 into bullseye? I dont' wish to over-burden you or push the > boundaries of the freeze, hence the query. > > In case this is acceptable: > > Ben file: > > title = "ppp"; > is_affected = .build-depends ~ /ppp-dev/; > is_good = .depends ~ /ppp \(>= 2\.4\.9-1\+~\)/ | .breaks ~ /ppp \(<< > 2\.4\.9-1\+~\)/; > is_bad = .depends ~ /ppp \(>= 2\.4\.8-1\+~\)/ | .breaks ~ /ppp \(<< > 2\.4\.8-1\+~\)/; > > Many thanks in advance, > Chris > -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#977452: marked as done (transition: fmtlib)
Your message dated Tue, 5 Jan 2021 09:06:12 +0100 with message-id and subject line Re: Bug#977452: transition: fmtlib has caused the Debian Bug report #977452, regarding transition: fmtlib to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 977452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: z...@debian.org Hi, I have uploaded fmtlib 7.1.3 to experimental, I would like to request a slot to start this transition. In the past (fmtlib <= 6.x), it's a static only library. Last month I adopted it, and decide to build a shared library for 7.x. The old package has too much patches which are not merged by/forwarded to upstream, thus I do want have the 7.x(which is re-packaged from scratch) for bullseye. The new version will use what upstream provides. It will has two targets in its cmake system, one is head-only version, one is shared library version. So when r-depend packages rebuild with this new version, it can either use head-only version, or the shared library. For example in https://sources.debian.org/src/fcitx5/5.0.3-2/CMakeLists.txt/#L82 it will check which target exists. The ben file seems hard to rewrite, as there's no good way to check what is_good and is_bad. Following packages need to be rebuilt bear dpaste fcitx5 fcitx5-chinese-addons hinge intel-gmmlib knxd kodi libpog lizardfs mkvtoolnix nheko open3d opendht openimageio osmid purify pytorch rapmap restinio ring salmon sopt spdlog tiledb waybar yaramod I will start to check if they can be rebuilt successfully. One thing to mention is that spdlog should be rebuilt first. As it uses fmtlib internal API and embedded fmtlib in its shared library previously. So if packages both use fmtlib and spdlog, they need to be rebuilt later. Thanks Shengjing Zhu --- End Message --- --- Begin Message --- On 2020-12-15 17:32:48 +0800, Shengjing Zhu wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: z...@debian.org > > > Hi, > > I have uploaded fmtlib 7.1.3 to experimental, I would like to request a > slot to start this transition. > > In the past (fmtlib <= 6.x), it's a static only library. Last month I > adopted it, and decide to build a shared library for 7.x. > > The old package has too much patches which are not merged by/forwarded > to upstream, thus I do want have the 7.x(which is re-packaged from > scratch) for bullseye. > > The new version will use what upstream provides. It will has two targets > in its cmake system, one is head-only version, one is shared library > version. > > So when r-depend packages rebuild with this new version, it can either > use head-only version, or the shared library. > > For example in > https://sources.debian.org/src/fcitx5/5.0.3-2/CMakeLists.txt/#L82 > it will check which target exists. > > The ben file seems hard to rewrite, as there's no good way to check > what is_good and is_bad. > > Following packages need to be rebuilt > > bear > dpaste > fcitx5 > fcitx5-chinese-addons > hinge > intel-gmmlib > knxd > kodi > libpog > lizardfs > mkvtoolnix > nheko > open3d > opendht > openimageio > osmid > purify > pytorch > rapmap > restinio > ring > salmon > sopt > spdlog > tiledb > waybar > yaramod > > I will start to check if they can be rebuilt successfully. > > One thing to mention is that spdlog should be rebuilt first. As it uses > fmtlib internal API and embedded fmtlib in its shared library > previously. So if packages both use fmtlib and spdlog, they need to be > rebuilt later. fmtlib and its reverse dependencies migrated. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
