[Apt-Rpm] apt-get dist-upgrade tries to replace syslog-nw with rsyslog on F9

[Alexander 'Leo' Bergolth]

Hi!

I'm experiencing problems when using syslog-ng as a replacement for 
rsyslog on F9. (I have several boxes with F8, where the same works 
without problems.)

After having installed syslog-ng, apt-get dist-upgrade suggests to 
remove syslog-ng and replace it with rsyslog:

-------------------- 8< --------------------
# apt-get -o Debug::pkgProblemResolver=1 -V dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Starting
Starting 2
Investigating syslog-ng
Package syslog-ng has broken dep on rsyslog
   Considering rsyslog 5103 as a solution to syslog-ng 2
   Removing syslog-ng rather than change rsyslog
Done
Done
The following packages will be REMOVED:
    syslog-ng (2.0.8-1.fc9)
The following NEW packages will be installed:
    rsyslog (3.14.1-2.fc9)
WARNING: The following essential packages will be removed
This should NOT be done unless you know exactly what you are doing!
   syslog-ng (due to initscripts)
0 upgraded, 1 newly installed, 1 removed and 0 not upgraded.
Need to get 317kB of archives.
After unpacking 291kB of additional disk space will be used.
You are about to do something potentially harmful
To continue type in the phrase 'Yes, do as I say!'
-------------------- 8< --------------------

However, syslog-ng doesn't _depend_ on rsyslog, it rather _conflicts_ 
with rsyslog. Later, apt reports that it has to remove syslog-ng "due to 
initscripts" but initscripts only depends on the capability "syslog" 
which is provided by both packages:

# rpm -q --conflicts syslog-ng
rsyslog

# rpm -q --requires syslog-ng | uniq
/bin/sh
chkconfig
config(syslog-ng) = 2.0.8-1.fc9
initscripts
libc.so.6
libc.so.6(GLIBC_2.0)
libc.so.6(GLIBC_2.1)
libc.so.6(GLIBC_2.2)
libc.so.6(GLIBC_2.3)
libc.so.6(GLIBC_2.3.4)
libc.so.6(GLIBC_2.4)
libevtlog.so.0
libglib-2.0.so.0
libnsl.so.1
librt.so.1
libwrap.so.0
logrotate
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)

# apt-cache policy syslog-ng rsyslog
syslog-ng:
   Installed: 2.0.8-1.fc9
   Candidate: 2.0.8-1.fc9
   Version Table:
  *** 2.0.8-1.fc9 0
         500 http://wolfcastle.wu-wien.ac.at dist/f9-i386/everything pkglist
         100 RPM Database
rsyslog:
   Installed: (none)
   Candidate: 3.14.1-2.fc9
   Version Table:
      3.14.1-2.fc9 0
         500 http://wolfcastle.wu-wien.ac.at dist/f9-i386/everything pkglist

# apt-cache depends initscripts
initscripts-8.76.2-1
[...]
   Depends: <syslog>
     rsyslog-3.14.1-2.fc9
     syslog-ng-2.0.8-1.fc9
[...]

# apt-cache whatdepends syslog
<syslog>
   initscripts-8.76.2-1
     Depends: <syslog>
       rsyslog-3.14.1-2.fc9
       syslog-ng-2.0.8-1.fc9
   cronie-1.0-7.fc9
     Depends: <syslog>
       rsyslog-3.14.1-2.fc9
       syslog-ng-2.0.8-1.fc9
   fcron-3.0.3-4.fc9
     Depends: <syslog>
       rsyslog-3.14.1-2.fc9
       syslog-ng-2.0.8-1.fc9


Sadly, the only workaround I could find is ignoring rsyslog completely with
   RPM::Ignore { "rsyslog" };

Either getting rsyslog ignored using negative pinning or elevating 
syslog-ng with positive pinning didn't work. :(

Any hints?

Cheers,
--leo
-- 
e-mail   ::: Leo.Bergolth (at) wu-wien.ac.at
fax      ::: +43-1-31336-906050
location ::: Computer Center | Vienna University of Economics | Austria