News Draft: ppp >= 2.5.0-1 update may require manual intervention
As you may or may not have noticed, both `ppp` and `rp-pppoe` package used to ship a `rp-pppoe.so` and they are not 100% compatible. Back in 2021, ppp 2.4.9 starts to rename its own copy of `rp-pppoe.so` to `pppoe.so`. As of `ppp 2.5.0`, upstream decided to remove the `rp-pppoe.so` symlink and thus broke configurations with the old name. If you still have the old ppp package's `rp-pppoe.so` configured somewhere (likely in /etc/ppp/peers/), please update it to use just `pppoe.so`. Configurations with the same plugin from the `rp-pppoe` package (using full path like /usr/lib/rp-pppoe/rp-pppoe.so) are not affected. -- Regards, Felix Yan
I had no idea what this even was, and the description isn't making it any better - 'A daemon which implements the Point-to-Point Protocol for dial-up networking'. How many users are gonna be affected by this? Maybe it makes sense to list (transitive) deps that are affected by this change. On Wed, 13 Sep 2023 22:27:22 +0300 Felix Yan <felixonmars@archlinux.org> wrote:
As you may or may not have noticed, both `ppp` and `rp-pppoe` package used to ship a `rp-pppoe.so` and they are not 100% compatible. Back in 2021, ppp 2.4.9 starts to rename its own copy of `rp-pppoe.so` to `pppoe.so`. As of `ppp 2.5.0`, upstream decided to remove the `rp-pppoe.so` symlink and thus broke configurations with the old name.
If you still have the old ppp package's `rp-pppoe.so` configured somewhere (likely in /etc/ppp/peers/), please update it to use just `pppoe.so`. Configurations with the same plugin from the `rp-pppoe` package (using full path like /usr/lib/rp-pppoe/rp-pppoe.so) are not affected.
-- hashworks Web https://hashworks.net Public Key 0x4FE7F4FEAC8EBE67
On 9/13/23 22:53, Justin Kromlinger wrote:
I had no idea what this even was, and the description isn't making it any better - 'A daemon which implements the Point-to-Point Protocol for dial-up networking'. How many users are gonna be affected by this? Maybe it makes sense to list (transitive) deps that are affected by this change.
Mostly affects only people having ppp configured themselves. Other packages should fix themselves if they hit this. On 9/14/23 00:42, Jan Alexander Steffens (heftig) wrote:
Bare PPP seems obscure enough a post_upgrade message might be sufficient? I've only ever used PPP with NetworkManager, which handles this already.
Multiple people are hitting this and had to travel across cities to get this fixed. Well I'm also fine with only a post_upgrade message. -- Regards, Felix Yan
On Wed, Sep 13, 2023 at 9:27 PM Felix Yan <felixonmars@archlinux.org> wrote:
As you may or may not have noticed, both `ppp` and `rp-pppoe` package used to ship a `rp-pppoe.so` and they are not 100% compatible. Back in 2021, ppp 2.4.9 starts to rename its own copy of `rp-pppoe.so` to `pppoe.so`. As of `ppp 2.5.0`, upstream decided to remove the `rp-pppoe.so` symlink and thus broke configurations with the old name.
If you still have the old ppp package's `rp-pppoe.so` configured somewhere (likely in /etc/ppp/peers/), please update it to use just `pppoe.so`. Configurations with the same plugin from the `rp-pppoe` package (using full path like /usr/lib/rp-pppoe/rp-pppoe.so) are not affected.
Bare PPP seems obscure enough a post_upgrade message might be sufficient? I've only ever used PPP with NetworkManager, which handles this already.
participants (3)
-
Felix Yan
-
Jan Alexander Steffens (heftig)
-
Justin Kromlinger