Bug#1109510: [Pkg-swan-devel] Bug#1109510: Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2025-07-22 at 08:43 +0200, Jochen Sprickerhof wrote: > > as already said, that's not an option for us. There's no plan to retire > > strongswan-charon (and strongswan-starter) packages. > > Why would you drop the alternate dependency in Forky then? Because at some point I'd like that strongswan only dependency would be for charon-systemd and strongswan-swanctl. > > What should happen to users having strongswan and strongswan-charon > installed when upgrading to Forky? I think I would have expected strongswan to be upgraded, strongswan-charon (and strongswan-starter) removed and charon-systemd/strongswan-swanctl installed. It would have been better to have the package co-installable but they bind on the same port so that doesn't really make sense. > > Btw. there is currently a new solver in apt that would remove > strongswan-charon and install charon-systemd instead. That will likely > become the default in Forky so it could work without a transition dummy > package then. That would be nice, yes. > > In any case, I would propose to add the alternate dependency for Trixie > and do do an upload soon as time is running out. I guess so… - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh/t4gACgkQ3rYcyPpX RFuvSAgAtFc/s/rDb91CcOMPR8W55GAYlbJHYlab+w+B2y0KgFdvkicRsF0FrmAI 3gXIzxhQWMgx8gbydhuntRflJxph14jZgE6D218lsoLVHftrtfF7UnQ40lfcYCRB SR7A2KtvxvtZ9xcozwyTyWaT+MNupfq+n/qAtJ3lfQjGV9AJN/H346Zr3nYEhKft hjxGDhwIYbCq6uDD0hLX2hhxNBUZuIQ3jmvO/MC6RLjwS4mRjKcydaOeQ0wvzK3m TA14vjtYzlaEvtYcSQp4aigwXF7SHUGV6IPmsYX0WH6SowsCl6B45zb641ddbG7v JIG7i2KX1MK6yo0c7IwPudB70wiZuw== =elR7 -END PGP SIGNATURE-
Bug#1109510: [Pkg-swan-devel] Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
* Yves-Alexis Perez [2025-07-22 08:04]: On Mon, 2025-07-21 at 18:55 +0200, Jochen Sprickerhof wrote: > So, it seems to work on Bookworm -> Trixie but won't that mean we'll have > the > same problem again (for those installs) in Trixie -> Forky if I remove the > alternate dependency at that point? For Forky you would have to do the transition dummy package and maintainer scripts conversion then. Hey Jochen as already said, that's not an option for us. There's no plan to retire strongswan-charon (and strongswan-starter) packages. Why would you drop the alternate dependency in Forky then? What should happen to users having strongswan and strongswan-charon installed when upgrading to Forky? Btw. there is currently a new solver in apt that would remove strongswan-charon and install charon-systemd instead. That will likely become the default in Forky so it could work without a transition dummy package then. In any case, I would propose to add the alternate dependency for Trixie and do do an upload soon as time is running out. Cheers Jochen signature.asc Description: PGP signature
Bug#1109510: [Pkg-swan-devel] Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2025-07-21 at 18:55 +0200, Jochen Sprickerhof wrote: > > So, it seems to work on Bookworm -> Trixie but won't that mean we'll have > > the > > same problem again (for those installs) in Trixie -> Forky if I remove the > > alternate dependency at that point? > > For Forky you would have to do the transition dummy package and > maintainer scripts conversion then. Hey Jochen as already said, that's not an option for us. There's no plan to retire strongswan-charon (and strongswan-starter) packages. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh/KgkACgkQ3rYcyPpX RFs5egf/cblvIoRsQQHYm1GI5GlrwVHeK8g2GgAV1tosJukPE3lvQrGN944DZMqF MXdOwi4NT0lW5HmAuIk1GnY6X5W58i+8e6P6k6M8FinWdwPQJfn99aufWIdRhM6X T6caYBBfSCqa40K2xlqi0bIYYoX7ox0HkRUdKjHsnGEtFtD+GLdi34gAdYY+A+1+ hKieit+tTkDg/k9RA2FRu9bscug5BOBhG92lQvubYUOzRKvEz1bA8Tzyyw5N87qv yOtyzo+kcPcucBV0hsRpn3mM0YFYBM96C9+btgh03by+bbCbF6Sj/SYBW/XkiUA/ fj02u+ur6L7JWCxF4QB0vmszQWeNNg== =YlHa -END PGP SIGNATURE-
Bug#1109510: [Pkg-swan-devel] Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
* Yves-Alexis Perez [2025-07-21 18:50]: On Mon, 2025-07-21 at 18:42 +0200, Yves-Alexis Perez wrote: > If both should be in trixie I would say: > > Package: strongswan > Depends: charon-systemd | strongswan-charon, strongswan-swanctl Ah, good point, that might work, let's try that. I'll report back here. So, it seems to work on Bookworm -> Trixie but won't that mean we'll have the same problem again (for those installs) in Trixie -> Forky if I remove the alternate dependency at that point? For Forky you would have to do the transition dummy package and maintainer scripts conversion then. Cheers Jochen signature.asc Description: PGP signature
Bug#1109510: [Pkg-swan-devel] Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2025-07-21 at 18:42 +0200, Yves-Alexis Perez wrote: > > If both should be in trixie I would say: > > > > Package: strongswan > > Depends: charon-systemd | strongswan-charon, strongswan-swanctl > > Ah, good point, that might work, let's try that. I'll report back here. So, it seems to work on Bookworm -> Trixie but won't that mean we'll have the same problem again (for those installs) in Trixie -> Forky if I remove the alternate dependency at that point? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh+b9MACgkQ3rYcyPpX RFvZpAgAp/7aHmRrgE0LRChTXxrkv66s6LG8CyTI75XdqLtC23X5HkA+mnRWPwEd TL6FlrqllKkSGeQwHeChisjXA7L8bCDa7Mr+IK2t/JfWcV+suYcmO2zialxJKr2C gBswBp68j5aQj/kfcioCt3ZxE02P0EVTdEFZ5caP/DAYF7GCBfgPA9pgExgb/WB3 ItabU2PHA954kK1dD3+mcjZpn9eMuZB+lYqOzzzTWpAPtjeHo3ZzfNU61jZgYv7L MRBVgvrGAXZefvAMjul8ibDhzJ0ZyasXlCAhQd5/iHH0VITpgv7k7eNKPbk07/cc yzUaoL1qrzusy60u5X8U/F5CseRk0Q== =dZfo -END PGP SIGNATURE-
Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2025-07-21 at 18:40 +0200, Jochen Sprickerhof wrote: > > strongswan-charon is the "historical" (legacy) charon daemon, which is > > beeing > > phased out in favor of charon-systemd. That's why we updated the > > dependency > > for the strongswan metapackage. We recommend people to migrate to the new > > daemon, and for new install that'll be the case. For old installations one > > could actually wonder if we should actually migrate, but in any case we > > would > > still want to actually upgrade the packages. > > Why would people not upgrade? > I think a new Debian release is a good reason to migrate. Yes indeed, we just don't want to force that on them. They can still keep strongswan-charon (and strongswan-starter) along with their current configuration, and migrate on their own term. > > > So I'm not sure how to express that in apt relationships. > > If both should be in trixie I would say: > > Package: strongswan > Depends: charon-systemd | strongswan-charon, strongswan-swanctl Ah, good point, that might work, let's try that. I'll report back here. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh+bfcACgkQ3rYcyPpX RFvlNwf/fxRNWlBYMonBMKtNivxgxqPKruU/wsMH9OF3WcyIqBLdBRjQ2xsx4haB aEBMHTY5u5jknAoq/9B740ZLztxacg3BoFm93uz7Vv8vU39yDAv6qyG63Wnt9X5p ip4PyG/zhmjJhRAvuHKs1sh+FoHevMpspbUn2TaCrVFFJYVsBykPLSyt2oI3JQ7P GVtJChFMNydnS0Y9c44xy2VdOwenNYYnH4onurdopYyTjdBv/WKySY3dpdqnSsHs bR6uxBM2bmMbB1AoWlK2F1yukvmvo/uKN0FGRdmSCinfief+G6RR42dhKJqNbd/s h6u11/xYDm1yeGm4EEKn+Gk7eYZU7A== =RHxU -END PGP SIGNATURE-
Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2025-07-21 at 18:12 +0200, Jochen Sprickerhof wrote: > > I have no idea why apt doesn't want to 'change charon-systemd:amd64'. > > The problem is that bookworm apt prefers keeping strongswan-charon > installed over other solutions. This is described in: > > https://wiki.debian.org/RenamingPackages > > So strongswan-charon would need to become a transitional dummy package > that depend on charon-systemd and the maintainer scripts should take > care of transitioning the configuration files. The Conflicts: can also > be dropped then. > > Feel free to ask if you need more explanation. Hi Jochen, thanks but it's not a case of renaming packages. Both strongswan-charon and charon-systemd exist in Bookworm and Trixie. Both are working and can be installed if the users choses so. They fill the same role (they include an IKE daemon for setting up IPsec tunnels) but differently. strongswan-charon is the "historical" (legacy) charon daemon, which is beeing phased out in favor of charon-systemd. That's why we updated the dependency for the strongswan metapackage. We recommend people to migrate to the new daemon, and for new install that'll be the case. For old installations one could actually wonder if we should actually migrate, but in any case we would still want to actually upgrade the packages. So I'm not sure how to express that in apt relationships. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh+a+wACgkQ3rYcyPpX RFuTwQgAzP+lKMPhqwnu8i/ebDDC2uXLV8Kkunk42r3mj1EHGLLclpSPm2IXO+tC oPV6DXXCwEIteR8nE/+vgxuVsq/+dMlJ1oAYbL9WPB3nivyBkESzMNlf4L2xyTZy NHM073WHw7qIFC+BiUDH6xzWDVw9JAzssDr5lfsVmYTjTuNhOelziz99SsQzo0sU Dbr979a+Vt5jZEOGOCvxxYCxsnsoBtxMgyiYCpWozy87FKv3WT1XWKSCxGA3zJ4I ErD0GWDf5ryg7mIkKM5rolsaaA2AeG5lFIqdUmWGVKfJ6x/n8FAKdj5MtDz6MIj2 PyAh4w23ihOzy9or44olpu/tV0UmEQ== =Rriw -END PGP SIGNATURE-
Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
Hi Yves-Alexis, * Yves-Alexis Perez [2025-07-20 16:29]: I'm still not sure it's the right solution but I tried to add: Package: charon-systemd [...] Replaces: strongswan-charon (<< 6.0.1-1~) But I still get the same during the upgrade: Investigating (0) strongswan:amd64 < 5.9.8-5+deb12u1 -> 6.0.1-6 @ii umU Ib > Broken strongswan:amd64 Depends on charon-systemd:amd64 < none | 6.0.1-6 @un uH > Considering charon-systemd:amd64 -1 as a solution to strongswan:amd64 0 Holding Back strongswan:amd64 rather than change charon-systemd:amd64 Try to Re-Instate (1) strongswan:amd64 I have no idea why apt doesn't want to 'change charon-systemd:amd64'. The problem is that bookworm apt prefers keeping strongswan-charon installed over other solutions. This is described in: https://wiki.debian.org/RenamingPackages So strongswan-charon would need to become a transitional dummy package that depend on charon-systemd and the maintainer scripts should take care of transitioning the configuration files. The Conflicts: can also be dropped then. Feel free to ask if you need more explanation. Cheers Jochen signature.asc Description: PGP signature
Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2025-07-20 at 12:25 +0200, Yves-Alexis Perez wrote: > In any case, help would be appreciated on how to interpret apt output and > how > to make it accept the removal of strongswan-charon for upgrading the > strongswan metapackage. > > Maybe I need to add Replaces: strongswan-charon to the charon-systemd > package > but I'm not sure it really express the situation. I'm still not sure it's the right solution but I tried to add: Package: charon-systemd [...] Replaces: strongswan-charon (<< 6.0.1-1~) But I still get the same during the upgrade: Investigating (0) strongswan:amd64 < 5.9.8-5+deb12u1 -> 6.0.1-6 @ii umU Ib > Broken strongswan:amd64 Depends on charon-systemd:amd64 < none | 6.0.1-6 @un uH > Considering charon-systemd:amd64 -1 as a solution to strongswan:amd64 0 Holding Back strongswan:amd64 rather than change charon-systemd:amd64 Try to Re-Instate (1) strongswan:amd64 I have no idea why apt doesn't want to 'change charon-systemd:amd64'. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh8/UQACgkQ3rYcyPpX RFshbwf8CXCTAJg5Vv1ubcZswDF5AtZ7Yt4qfaScZ34PQ/4PvgJSWsvDu7nfuaQU yV0gBqaYUNUbzOSBLFI20JGT1rl9xrddtbZep3DE/Y4QVQRlwbEwXAtyy1Z9e1O4 ZpEce4iYM/lZvIQ2/W2cQnT5vdxjD3YtfxQfkWoF2dZsXDwbwWGrndg6tWexpbnv eNthF0WYCChkloVF6ZFwDMGQcAINrNtJT8lcnlo0YCl1/b6DkzuJsI998lvQ3Bcf eoQF90U2kiTd+tp+PKwkbVGQLzjmEKHKoyJP91eiAn8KRYTDj9wV2b/VsRsXWJQe i4h7QmXtZQIbV1HkqEunpI8fGmHM6Q== =Ehh8 -END PGP SIGNATURE-
Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: tag -1 help On Sat, 2025-07-19 at 20:25 +0200, Lucas Nussbaum wrote: > > > MWE: > > > PKG=strongswan; mmdebstrap --chrooted-customize-hook="set -x ; apt -y > > > install $PKG && sed -e s/bookworm/trixie/ -i /etc/apt/sources.list && > > > apt > > > update && apt dist-upgrade -y -o Debug::pkgProblemResolver=true && apt - > > > y > > > install $PKG" bookworm /dev/null > > > > Hi Lucas, thanks for the report but I'm not too sure what happens here. > > There's indeed a change in the metapackage dependencies for Bookworm and I > > had > > the impression everything was working. > > > > I noticed you used dist-upgrade and not full upgrade. Does that change > > anything? I'll try to reproduce using the above command line but if you > > already have a working setup it might be faster for you. > > Hi Yves-Alexis, > > No, it's the same with full-upgrade. Hey Lucas, I tried using my pbuilder chroot and it seems that I'm able to reproduce, but I'm honestly not sure how to fix that. I don't know enough about apt solver to really understand the debug output. The strongswan metapackage was indeed updated between Bookworm and Trixie. In bookworm strongswan pulls strongswan-charon and strongswan-starter In trixie strongswan pulls charon-systemd and strongswan-swanctl That's expected and it's especially ok for new installs. For existing ones it'll likely need administrator action (to port the configuration) and they're warned by a NEWS.Debian entry (and I think it might deserve a release note entry as well). I guess it could be argued that manually upgrading the strongswan metapackage would be best so the administrator wouldn't be too surprised by the change, but maybe that's suboptimal for unattended upgrades? In any case, help would be appreciated on how to interpret apt output and how to make it accept the removal of strongswan-charon for upgrading the strongswan metapackage. Maybe I need to add Replaces: strongswan-charon to the charon-systemd package but I'm not sure it really express the situation. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh8w/4ACgkQ3rYcyPpX RFu+tgf/Ukb1vV/KaoiyEs3e69lW5meAr7n7DetVdG/tLDgAVZfBlTTna+nJswAR 4Fe/pBI4E/zJ6MSNUSbAWykn36MF5BqTMlMr9OJI25VDOPO7ZtGe+rL4re8NyQXD VE6uoeJ8CGGl/2Qpo1FSD3c5Iuf391e6AjwcCrWrznXNnLQciXT529oR8ZvgAm6P Yq4ilNZprsYgBUV2ICgjmo1DwH+CNSp99YKwnKOmRMTRTP1lmeGhc2PGrWkwHEkH 7Lla9qTgpIxuKZgksgTN+k/s+3DQOCJB03LRK5k0ZFZsdgH2xFk4GQl+TPT7incT eg91eTS5yLoxv5DUxDLDLQe6K0Du+Q== =v8sK -END PGP SIGNATURE-
Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
On 19/07/25 at 18:30 +0200, Yves-Alexis Perez wrote: > On Sat, 2025-07-19 at 11:51 +0200, Lucas Nussbaum wrote: > > The following fails: > > - In bookworm, install strongswan > > - dist-upgrade to trixie > > I would expect strongswan to be upgraded, but it is not. It remains at the > > bookworm version. > > 'apt install'ing manually in trixie works fine. > > > > There might be some missing Replaces/Provides somewhere to hint apt at > > upgrading the package. > > > > MWE: > > PKG=strongswan; mmdebstrap --chrooted-customize-hook="set -x ; apt -y > > install $PKG && sed -e s/bookworm/trixie/ -i /etc/apt/sources.list && apt > > update && apt dist-upgrade -y -o Debug::pkgProblemResolver=true && apt -y > > install $PKG" bookworm /dev/null > > Hi Lucas, thanks for the report but I'm not too sure what happens here. > There's indeed a change in the metapackage dependencies for Bookworm and I had > the impression everything was working. > > I noticed you used dist-upgrade and not full upgrade. Does that change > anything? I'll try to reproduce using the above command line but if you > already have a working setup it might be faster for you. Hi Yves-Alexis, No, it's the same with full-upgrade. Lucas
Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2025-07-19 at 11:51 +0200, Lucas Nussbaum wrote: > The following fails: > - In bookworm, install strongswan > - dist-upgrade to trixie > I would expect strongswan to be upgraded, but it is not. It remains at the > bookworm version. > 'apt install'ing manually in trixie works fine. > > There might be some missing Replaces/Provides somewhere to hint apt at > upgrading the package. > > MWE: > PKG=strongswan; mmdebstrap --chrooted-customize-hook="set -x ; apt -y > install $PKG && sed -e s/bookworm/trixie/ -i /etc/apt/sources.list && apt > update && apt dist-upgrade -y -o Debug::pkgProblemResolver=true && apt -y > install $PKG" bookworm /dev/null Hi Lucas, thanks for the report but I'm not too sure what happens here. There's indeed a change in the metapackage dependencies for Bookworm and I had the impression everything was working. I noticed you used dist-upgrade and not full upgrade. Does that change anything? I'll try to reproduce using the above command line but if you already have a working setup it might be faster for you. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh7yC0ACgkQ3rYcyPpX RFuR5gf/doF95JoBVUMn97QDIINueNSoPpdFryFPCOFfuuYYI3uyNGy57LaGdtlb OhssWpzvVBoYHZg+WsQmVVD9RD3KXS/jHF3WT7+CrqCzbCAxkIN3hYHDk+MNOLD1 a2zqTdWggKoGzOtmZmW921BZEV+972bHOkGhMkNl9q5WWRWMaywZoNAfaLLMZxVC CPYpecTlm8g+ITqOzrZqIeJj1Lo33/5k8Zd66BbyTKA0+4RUGr8BkuYX9DvAKKJg SVsHurE+1obt5nN4IYNA8uc/MG79AVKJKDxsb69IsvUMg2wfjvJoEu0IsZVs13a0 GqPIm+szbqDgd9sLNPPR5UWmKxW6IA== =st41 -END PGP SIGNATURE-
Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie
Package: strongswan Version: 6.0.1-5 Severity: serious Hi, The following fails: - In bookworm, install strongswan - dist-upgrade to trixie I would expect strongswan to be upgraded, but it is not. It remains at the bookworm version. 'apt install'ing manually in trixie works fine. There might be some missing Replaces/Provides somewhere to hint apt at upgrading the package. MWE: PKG=strongswan; mmdebstrap --chrooted-customize-hook="set -x ; apt -y install $PKG && sed -e s/bookworm/trixie/ -i /etc/apt/sources.list && apt update && apt dist-upgrade -y -o Debug::pkgProblemResolver=true && apt -y install $PKG" bookworm /dev/null Relevant part: Investigating (0) strongswan-charon:amd64 < 5.9.8-5+deb12u1 -> 6.0.1-5 @ii umU Ib > Broken strongswan-charon:amd64 Conflicts on charon-systemd:amd64 < none -> 6.0.1-5 @un uN Ib > Considering charon-systemd:amd64 -1 as a solution to strongswan-charon:amd64 1 Added charon-systemd:amd64 to the remove list Fixing strongswan-charon:amd64 via keep of charon-systemd:amd64 Investigating (0) libgdbm-compat4t64:amd64 < none -> 1.24-2 @un uN Ib > Broken libgdbm-compat4t64:amd64 Breaks on libgdbm-compat4:amd64 < 1.23-3 @ii mK > (< 1.24-2) Considering libgdbm-compat4:amd64 -2 as a solution to libgdbm-compat4t64:amd64 1 Added libgdbm-compat4:amd64 to the remove list Fixing libgdbm-compat4t64:amd64 via remove of libgdbm-compat4:amd64 Investigating (0) strongswan:amd64 < 5.9.8-5+deb12u1 -> 6.0.1-5 @ii umU Ib > Broken strongswan:amd64 Depends on charon-systemd:amd64 < none | 6.0.1-5 @un uH > Considering charon-systemd:amd64 -1 as a solution to strongswan:amd64 0 Holding Back strongswan:amd64 rather than change charon-systemd:amd64 Try to Re-Instate (1) strongswan:amd64 [...] + apt -y install strongswan The following packages were automatically installed and are no longer required: libapt-pkg6.0 libargon2-1 libgnutls30 libtasn1-6 libunistring2 strongswan-starter Use 'apt autoremove' to remove them. Upgrading: strongswan Installing dependencies: charon-systemd strongswan-swanctl REMOVING: strongswan-charon
