#342 conflict between generic-logos and fedora-logos
Opened by thomasvs. Modified

After working around previously filed bugs, I get an error dialog saying

generic-logos conflicts with fedora-logos

Console shows:

Checking dependencies - not allowing any conflicts within the package set
generic-logos-9.0.0-1.fc9.noarch from fedora has depsolving problems
--> generic-logos conflicts with fedora-logos
Unable to resolve dependencies for some packages selected:

generic-logos conflicts with fedora-logos

All I selected from the F-9 packages was GNOME desktop, nothing else.


Strangely enough, it lets me continue, then later on shows me this error dialog:
{{{
Error encountered during installation of the software you selected:

[('file /boot/grub/splash.xpm.gz conflicts between attempted installs of fedora-logos-9.0.0-2.fc9.noarch and generic-logos-9.0.0-1.fc9.noarch', (6, '/boot/grub/splash.xpm.gz', 0L)), ('file /usr/lib/anaconda-runtime/syslinux-vesa-splash.jpg conflicts between attempted installs of fedora-logos-9.0.0-2.fc9.noarch and generic-logos-9.0.0-1.fc9.noarch', (6, '/usr/lib/anaconda-runtime/syslinux-vesa-splash.jpg', 0L)), ('file /usr/share/anaconda/pixmaps/anaconda_header.png conflicts between attempted installs of fedora-logos-9.0.0-2.fc9.noarch and generic-logos-9.0.0-1.fc9.noarch', (6, '/usr/share/anaconda/pixmaps/anaconda_header.png', 0L)), ('file /usr/share/anaconda/pixmaps/progress_first-lowres.png conflicts between attempted installs of fedora-logos-9.0.0-2.fc9.noarch and generic-logos-9.0.0-1.fc9.noarch', (6, '/usr/share/anaconda/pixmaps/progress_first-lowres.png', 0L)), ('file /usr/share/anaconda/pixmaps/progress_first.png conflicts between attempted installs of fedora-logos-9.0.0-2.fc9.noarch and generic-logos-9.0.0-1.fc9.noarch', (6, '/usr/share/anaconda/pixmaps/progress_first.png', 0L)), ('file /usr/share/anaconda/pixmaps/splash.png conflicts between attempted installs of fedora-logos-9.0.0-2.fc9.noarch and generic-logos-9.0.0-1.fc9.noarch', (6, '/usr/share/anaconda/pixmaps/splash.png', 0L)), ('file /usr/share/pixmaps/poweredby.png conflicts between attempted installs of fedora-logos-9.0.0-2.fc9.noarch and generic-logos-9.0.0-1.fc9.noarch', (6, '/usr/share/pixmaps/poweredby.png', 0L)), ('file /usr/share/pixmaps/splash/gnome-splash.png conflicts between attempted installs of fedora-logos-9.0.0-2.fc9.noarch and generic-logos-9.0.0-1.fc9.noarch', (6, '/usr/share/pixmaps/splash/gnome-splash.png', 0L)), ('file /usr/share/rhgb/main-logo.png conflicts between attempted installs of fedora-logos-9.0.0-2.fc9.noarch and generic-logos-9.0.0-1.fc9.noarch', (6, '/usr/share/rhgb/main-logo.png', 0L))]
}}}

Not useful as an error dialog. Should show only that there was a conflict between two packages, some info on how to resolve it, and possibly a "more info" button that shows the rest of this.

after clicking OK on THAT one, this traceback:
{{{
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/revisor/modgui/lm_usercustomize.py", line 135, in button_forward_clicked
self.gui.next()
File "/usr/lib/python2.5/site-packages/revisor/modgui/init.py", line 447, in next
self.default[self.current]'disp'
File "/usr/lib/python2.5/site-packages/revisor/modgui/init.py", line 315, in displayBuildMedia
self.BuildMedia.start()
File "/usr/lib/python2.5/site-packages/revisor/modgui/build_media.py", line 65, in start
self.base.lift_off()
File "/usr/lib/python2.5/site-packages/revisor/base.py", line 1104, in lift_off
self.buildLiveMedia()
File "/usr/lib/python2.5/site-packages/revisor/base.py", line 1773, in buildLiveMedia
liveImage.configure()
File "/usr/lib/python2.5/site-packages/imgcreate/creator.py", line 647, in configure
kickstart.RootPasswordConfig(self._instroot).apply(ksh.rootpw)
File "/usr/lib/python2.5/site-packages/imgcreate/kickstart.py", line 192, in apply
self.set_encrypted(ksrootpw.password)
File "/usr/lib/python2.5/site-packages/imgcreate/kickstart.py", line 178, in set_encrypted
self.call(["/usr/sbin/usermod", "-p", password, "root"])
File "/usr/lib/python2.5/site-packages/imgcreate/kickstart.py", line 110, in call
subprocess.call(args, preexec_fn = self.chroot)
File "/usr/lib/python2.5/subprocess.py", line 443, in call
return Popen(popenargs, *kwargs).wait()
File "/usr/lib/python2.5/subprocess.py", line 593, in init
errread, errwrite)
File "/usr/lib/python2.5/subprocess.py", line 1079, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
}}}

Indeed, the chroot does not have usr:
{{{
[root@ana revisor]# ls -l /var/tmp/revisor
total 32
drwxr-xr-x 2 root root 4096 2008-06-27 14:57 boot
drwxr-xr-x 3 root root 4096 2008-06-27 14:57 dev
drwxr-xr-x 3 root root 4096 2008-06-27 14:58 etc
drwx------ 2 root root 16384 2008-06-27 14:57 lost+found
dr-xr-xr-x 251 root root 0 2008-06-26 09:18 proc
drwxr-xr-x 11 root root 0 2008-06-26 09:18 sys
drwxr-xr-x 5 root root 4096 2008-06-27 14:57 var
}}}

Strangely enough, I'm not seeing this.

Metadata Update from @thomasvs:
- Issue assigned to kanarip

Metadata