[artix-general] [atix-general][s6] dhcpcd upgrade from yesterday (9.2.0-1 -> 9.3.1-1) breaks network connectivity

Kian Kasad kian at kasad.com
Fri Oct 30 02:41:32 CET 2020

On 20/10/29 06:47PM, Javier via artix-general wrote:
> On 10/29/20 4:50 PM, Dudemanguy via artix-general wrote:
> > On 10/29/20 5:04 PM, Dudemanguy via artix-general wrote:
> >> Hi all, I talked with upstream a bit about this. There's actually a
> >> solid workaround for this. You just need to run a syslog daemon
> >> (syslog-ng, metalog, etc.) and it will work. The developer is working
> >> on fixing that.
> > 
> > Oh and to be clear, the syslog daemon has to be running first for this
> > to work. So parallel startup will probably not work since there is no
> > guaranteed order. A bit annoying but with a couple of service manager
> > commands you can get internet again.
> So should we update dhcpcd-s6 making it depend on syslog-ng?  And then after getting the fix on dhcpcd, remove that?  So to guarantee the order?

I'd go with no. syslog-ng isn't the only syslog daemon, so it might
require installing extra packages and switching daemons, which could be
a bit of a hassle, especially since the goal is fixing dhcpcd.

> Another workaround is to avoid upgrading dhcpcd until getting the fix.  I already have:
> > % 'grep' '^IgnorePkg' /etc/pacman.conf 
> > IgnorePkg   = dhcpcd

I think this is a much better solution.

> I suppose in both cases we're waiting for the fix, :)
> I'm wondering if it's a good idea to have the s6 logger and another one both working...  Perhaps preventing the dhcpcd upgrade is safest?
> -- 
> Javier

Kian Kasad
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.artixlinux.org/archives/artix-general/attachments/20201029/e59ca8ea/attachment.sig>

More information about the artix-general mailing list