FS#28815 - Install CD is due for a new release due to pacman, filesystem, and initscripts

Attached to Project: Release Engineering
Opened by Max Pray (synthead) - Wednesday, 07 March 2012, 14:44 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 22 October 2012, 22:43 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Dieter Plaetinck (Dieter_be)
Architecture All
Severity High
Priority Flash
Reported Version testbuild (specify!)
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

filesystem and initscripts require a manual upgrade, and upgrading from pacman v3.x to v4.x requires some configuration changes on the superuser's part. This is fine and normal from the standpoint of a rolling release, but not very easy to explain to new users that install Arch and immediately "break" it on their first upgrade. Their computer might not boot due to udev issues, and if they figure out how to get into a chroot, pacman won't work either due to untrusted keys.

The solution: A new CD with the same stuff on it, nothing needs to be changed, just an upgrade of the images getting installed from the "core" .iso's.
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Monday, 22 October 2012, 22:43 GMT
Reason for closing:  Fixed
Comment by Karol Błażewicz (karol) - Wednesday, 07 March 2012, 15:39 GMT
Why not use the netinstall image? You won't run into any of these issues as you get only the current (i.e. pacman 4 etc.) packages installed.
Comment by Will Brokenbourgh (willbprog127) - Wednesday, 14 March 2012, 21:55 GMT
@karol: I agree that the netinstall is the best option, but why offer a now-badly-broken complete install .iso in the first place? It should be removed or updated with the latest packages for those who don't want to use the netinstall.

Loading...