FS#29455 - Netcfg 2.8.0 breaks network

Attached to Project: Arch Linux
Opened by Borromini (Borromini) - Saturday, 14 April 2012, 19:32 GMT
Last edited by Florian Pritz (bluewind) - Friday, 20 April 2012, 16:18 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

The upgrade to 2.8.0, currently in [testing], breaks network functionality. Whereas with 2.6.8, my wireless connection would be up and running every single time after boot, with 2.8.0, it is conspicuously absent. Running netcg manually fixes this.

Rolling back to 2.6.8 fixes this as well, so something went south with 2.8.0. As a matter of fact, 2.7.3 worked as well, but since it's not present in [testing] anymore, there's no way to roll back to it :P.

Pacman's log:

[2012-04-13 18:24] upgraded netcfg (2.7.3-1 -> 2.8.0-1)
[2012-04-14 15:24] Running 'pacman -S core/netcfg'
[2012-04-14 15:24] upgraded netcfg (2.8.0-1 -> 2.6.8-1)
This task depends upon

Closed by  Florian Pritz (bluewind)
Friday, 20 April 2012, 16:18 GMT
Reason for closing:  Fixed
Additional comments about closing:  netcfg 2.8.1-1
Comment by Borromini (Borromini) - Sunday, 15 April 2012, 13:42 GMT
Apparently this can be fixed by using the /etc/conf.d/netcfg configuration file. It appears 2.8.0 does not use rc.conf anymore (I wonder why, since centralisation of the whole boot procedure is what makes Arch/rc.conf so nice).

Someone helpful pointed me to the NEWS file in the netcfg package, that's where this info is. That's nice, but that's where you put source code info, not packaging info. It should be in the package install file so users can fix their setups.

Even better would be to keep the old way and stick to rc.conf for netcfg integration :).

Loading...