With the exact same commandline, roughly 50% of the time I get a
conflict betweem generic-logos and fedora-logos. This happens with
stock F9 revisor from rpm and the tip of the F-9 branch in git.
Nothing whatsoever requires fedora-logos.

Sometimes it works, sometimes it doesn't. !?

$ sudo revisor --cli --config revisor/revisor.conf
--kickstart=revisor/anaconda-f9.ks
--kickstart-include --kickstart-default
--install-unified --model 'xs-f9-i386' --yes
--rebrand-name=xs
SELinux on this host is disabled. Composed media will not have
SELinux, and as a result the system you install from the composed
media will not have SELinux either.
Loading Repositories:
######################################## 100.0%
Select kickstart packages:
######################################## 100.0%
Resolving Dependencies:
######################################## 100.0%
generic-logos-9.0.0-1.fc9.noarch from fedora has depsolving problems
--> generic-logos conflicts with fedora-logos
Resolving Dependencies:
######################################## 100.0%
Unable to resolve dependencies for some packages selected:

generic-logos conflicts with fedora-logos

*nothing* requires fedora-logos.

Calling revisor with debug=5 shows...

Adding required package kernel-0:2.6.25-14.fc9.i686
Adding required package kernel-xen-0:2.6.25-2.fc9.i686
Checking dependencies - not allowing any conflicts within the package set
Resolving Dependencies:
0.0% Removing package fedora-release-0:9-2.noarch for rebranding
Removing package fedora-release-notes-0:9.0.0-1.noarch for rebranding
Removing package fedora-logos-0:9.0.0-2.fc9.noarch for rebranding
Resolving Dependencies:
######################################## 100.0%
generic-logos-9.0.0-1.fc9.noarch from fedora has depsolving problems
--> generic-logos conflicts with fedora-logos
Resolving Dependencies:
######################################## 100.0%
Unable to resolve dependencies for some packages selected:

cheers,



m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

On Thu, 2008-09-11 at 14:50 +1200, Martin Langhoff wrote:
> With the exact same commandline, roughly 50% of the time I get a
> conflict betweem generic-logos and fedora-logos. This happens with
> stock F9 revisor from rpm and the tip of the F-9 branch in git.
> Nothing whatsoever requires fedora-logos.
>

isn't fedora-logos being pulled in in @core in comps?

that's why kickstart is pulling it in, I think.


-sv


--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Seth Vidal wrote:

On Thu, 2008-09-11 at 14:50 +1200, Martin Langhoff wrote:

With the exact same commandline, roughly 50% of the time I get a
conflict betweem generic-logos and fedora-logos. This happens with
stock F9 revisor from rpm and the tip of the F-9 branch in git.
Nothing whatsoever requires fedora-logos.



isn't fedora-logos being pulled in in @core in comps?

that's why kickstart is pulling it in, I think.



Very true, notting has just closed #456882, having removed fedora-logos
from @core, but that is rawhide only.


In help of Martin, add exclude=fedora-logos to the YUM configuration
file for the model you are using (probably located in /etc/revisor/conf.d/).


Kind regards,

Jeroen van Meeuwen
-kanarip

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

On Fri, Sep 12, 2008 at 3:11 AM, Jeroen van Meeuwen <kanarip@kanarip.com> wrote:
> Seth Vidal wrote:
>> isn't fedora-logos being pulled in in @core in comps?
>> that's why kickstart is pulling it in, I think.
> Very true, notting has just closed #456882, having removed fedora-logos from
> @core, but that is rawhide only.
>
> In help of Martin, add exclude=fedora-logos to the YUM configuration file
> for the model you are using (probably located in /etc/revisor/conf.d/).

Jeroen, Seth, thanks a ton for the hints. Happy to see that it's
getting smoother for F10, and extra happy that I have a workaround.

Now, on to the 200 more things I got to do to get the school server out...



m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list