#171 Package resolution fails if no kickstart file used
Closed: Invalid Opened by gallegosja@gmail.com.

If you don't set the Use kickstart config, the package selection comes as empty... after that, even if you select packages, packages are not installed and the process gets stuck there, you click "continue" and it supposedly resolves its dependencies, but then it doesn't go to the next step.
Output:

{{{
... snip ...

Building a nice package list from ksdata, and adding it to the transaction
DEBUG:revisor:Building a nice package list from ksdata, and adding it to the transaction
Wanna see the package list?
DEBUG:revisor:Wanna see the package list?
This is what we want to install []
DEBUG:revisor:This is what we want to install []
Search
Adding required packages
DEBUG:revisor:Adding required packages
Checking dependencies
DEBUG:revisor:Checking dependencies
Initting progress bar for Resolving Dependencies
DEBUG:revisor:Initting progress bar for Resolving Dependencies
Apparently we have not yet entered the Build Media stage
DEBUG:revisor:Apparently we have not yet entered the Build Media stage

... snip ...
}}}

The package list should have the packages already selected i.e. [(u'NetworkManager-gnome', u'i386', u'1', u'0.6.5', u'5.fc7'), (u'a2ps', u'i386', u'0', u'4.13b', u'65.fc7')...], instead here appears as an empty list []. If you select a kickstart file and then customize the package selection everything works fine.

Regards


The list you see is what revisor gets from the kickstart file, which as you said, you didn't use. The list is thus empty.

The list you see is what revisor gets from the kickstart file, which as you said, you didn't use. The list is thus empty.

Understood, however, the problem still persists, the process gets stuck in that step if you didn't open a KS file. Something else must be wrong (which I didn't see). I can provide you with the whole debug messages if that helps solving the problem. Actually, I may have been wrong in my wording... problem is this: you select a KS file in the file input above, but unselect "Use package manifest from kickstart data" (see attached screenshot). I am attaching the whole debug text in case something went amiss in the previous snips.

Regards

Understood, however, the problem still persists, the process gets stuck in that step if you didn't open a KS file. Something else must be wrong (which I didn't see). I can provide you with the whole debug messages if that helps solving the problem. Actually, I may have been wrong in my wording... problem is this: you select a KS file in the file input above, but unselect "Use package manifest from kickstart data" (see attached screenshot). I am attaching the whole debug text in case something went amiss in the previous snips.

Regards

Screenshot
Screenshot-Revisor.png

Screenshot
Screenshot-Revisor.png

Can you attach the full log? Run revisor with:

$ sudo /usr/bin/revisor --debug > ~/revisor.log

and attach the resulting revisor.log, please

Can you attach the full log? Run revisor with:

$ sudo /usr/bin/revisor --debug > ~/revisor.log

and attach the resulting revisor.log, please

There's no --debug option with my revisor install... only the previous debug text...

There's no --debug option with my revisor install... only the previous debug text...

Please update to 2.0.4.0-1 in that case

Please update to 2.0.4.0-1 in that case

Metadata Update from @gallegosja@gmail.com:
- Issue assigned to kanarip
- Issue set to the milestone: 2.0.4 Release

Metadata