(In reply to Leslie Satenstein from comment #0)
> Description of problem:
> 
> Testing the alpha version
> 
> I chose Gnome, and began testing all downloads possible.
> The following were generating an error message, without identifying that
> they were the cause.
> 
> Cloud Server Tools 
> Security Lab 

The failure is due to a conflict between fedora-release-standard and fedora-release-cloud (which I would have found faster if you had posted logs), and so is related to the separation of the different Fedora products, which is still ongoing.


> If in the first attempt, anaconda recognizes a package that cannot be
> downloaded, can the software selection screen have an update to notify the
> package in error.

It's nice that you think we have a way to determine that information.

*** This bug has been marked as a duplicate of bug 1134524 ***

David, the yum module that does the download of selected groups knows if the group was successfully downloaded or downloadable.

Instead of giving 22 files to yum, there can be a loop to feed yum with one at a time. If that download fails.... bingo, you got it.

The Russian Respin of Fedora 21  has almost double the software choices. Surprisingly, all their extras are fully downloadable.

So, to discover the failing downloads, I select the first half. If there is no error, I redo the selection of half of the half, (binary search).

Yes, selecting the two above options still fail with error message on the spoke page. 

Now that I know what works and what doesn't, I just select all that I require around the two.

Any development will be too late for F21.

(In reply to Leslie Satenstein from comment #2)
> David, the yum module that does the download of selected groups knows if the
> group was successfully downloaded or downloadable.
> 
> Instead of giving 22 files to yum, there can be a loop to feed yum with one
> at a time. If that download fails.... bingo, you got it.

We know from yum whether dependency resolution succeeded or not. What you are proposing is that we turn one dependency resolution cycle, which already takes a noticeably long period of time, into 5 dependency resolutions. We are not doing that.

> The Russian Respin of Fedora 21  has almost double the software choices.
> Surprisingly, all their extras are fully downloadable.

Good for them. Apparently they did a better job of putting a repo together than Fedora releng has.

Maybe a RFE can be opened on DNF to add the needed functionality on their side ? It is tentatively scheduled to become the default packager in F22[0], so it seems to be the best place for new functionality like this.

[0] http://fedoraproject.org/wiki/Changes/ReplaceYumWithDNF

Martin, 

Thank you for your comment.  I am not an anaconda internals guy, just an end-user with 50+ years of software engineering and end-user experience. I have no Linux internals knowledge -- just an end-user experience.

Yes, ergonomically designed systems win converts from other systems to Fedora or RedHat. Especially, having one output that informs to some reasonable detail, what an end-user can understand.  

What was broken is what was promised --security and "cloud service".

The information needed for such a change isn't directly available to dnf, either, and no one particularly wants to change that. So again we're stuck.

David,

I most appreciate your efforts to inform the user doing the Fedora installation with anaconda as to the package(s) causing the problem. 

Have a great day and a sincere thank you for your efforts.

Leslie

Somewhat related to this, I recently fixed a bug that was hiding the dependency errors when you re-entered the software spoke. So now when there is an error, you can return to the spoke and the warning bar will be there, and you can click on that to see the error messages we get from dnf or yum. That will at least tell you which packages have problems, though not the groups that contain them.

Hi David

As an end user of Fedora, how can I test before Fedora22? Am I able to take a Fedora21 spin iso to a bootable flashdrive and swap out anaconda? Is dnf on the spins that are regularly produced?

Thanks . 

Leslie

The rawhide boot.iso is usually at http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/ but it looks like the last compose failed, and there is no images/ subdirectory. The nightly live composes are listed at http://koji.fedoraproject.org/koji/tasks?state=all&view=tree&method=livecd&order=-id

dnf is currently the default in rawhide. It can be turned of by using "inst.nodnf" on the boot command line, which will switch to using yum.