Release Engineering

This project is intented for all release related issues (isos, installer, etc), under the umbrella of the ArchLinux Release Engineers

FS#28710 - Setup should not abort when no packages are selected

Attached to Project: Release Engineering
Opened by Slavi Pantaleev (s.pantaleev) - Wednesday, 29 February 2012, 10:12 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 26 November 2012, 04:48 GMT
Task Type Bug Report
Category AIF
Status Closed
Assigned To Dieter Plaetinck (Dieter_be)
Architecture All
Severity Low
Priority Normal
Reported Version testbuild (specify!)
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


One of the best things I like about the setup (/arch/setup) program is that it usually doesn't abort when it hits a problem, but just tells you about it and lets you fix it. This came in handy to me at least a few times in the past.

One of the areas where it doesn't to to this, however, is when you try to run the "Install packages" step with no package selected for install.
I'd like to have it tell me something like "You haven't selected any packages. Maybe you made a mistake. Go back and fix it." instead of just aborting the whole thing and forcing you to start over.

I have been bitten by this behavior at least once more in the past.

So how do I end up with no packages selected?
That's an even more interesting question. As far as I can remember, in the "Select packages" step I'm also trying to select the base-devel group.
Something weird is going on with the checkboxes there. I'm not even sure how it works till this day, but it seems like I end up deselecting everything (even the base group) unintentionally. I may have to play with this a bit in a VM to see what's going on.
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Monday, 26 November 2012, 04:48 GMT
Reason for closing:  Deferred