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) d
On Wed, Sep 13, 2023 at 9:27 PM Felix Yan 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`, up
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 We
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
