Hi Matt! On Thu, 07 Aug 2003, Matt Zimmerman wrote:
> Can you explain what the problem is with having file-rc Depend on sysvinit > (>= ...)? That seems like a more correct way of expressing this > relationship. I just tried this out whit the following dependencies of file-rc: Conflicts: ash (<< 0.3.5-1) Depends: sysvinit (>= 2.85-3) Replaces: sysv-rc (which means that I replaced the "Conflicts: sysvinit (<< 2.85-3)" by "Depends: sysvinit (>= 2.85-3)). But this still causes problems with apt: # apt-get -t unstable install sysvinit file-rc=0.8.2 Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: file-rc initscripts The following NEW packages will be installed: initscripts 2 packages upgraded, 1 newly installed, 0 to remove and 444 not upgraded. Need to get 133kB of archives. After unpacking 309kB will be used. Do you want to continue? [Y/n] Get:1 http://besan.sail.does-not-exist.org ./ file-rc 0.8.2 [30.8kB] Get:2 ftp://ftp.de.debian.org unstable/main initscripts 2.85-7 [15.1kB] Get:3 ftp://ftp.de.debian.org unstable/main sysvinit 2.85-7 [86.8kB] Fetched 133kB in 1s (80.3kB/s) E: Internal Error, Could not perform immediate configuration (2) on sysvinit I don't understand why the problem changed, but now we seems to be a bug in apt, doesn't it? I noticed the above behavior with apt 0.5.4 (sarge) as well as with 0.5.9 (sid). Tschoeeee Roland -- * [EMAIL PROTECTED] * http://www.spinnaker.de/ *
