On Tue, 2005-04-05 at 03:15 +0800, Dan Jacobson wrote: > Yes of course. I'm saying you have some dependency problems, hindering > apt-get dist-upgrade, if one has > ii xprt-common 0.1.0.alpha1-8 > ii xprt-xprintorg 0.1.0.alpha1-8 > installed. Here is what apt-get says: > > Starting > Starting 2 > Or group remove for xprint-common > Package xprint-common has broken dep on xprt-common > Considering xprt-common 1 as a solution to xprint-common 1 > Holding Back xprint-common rather than change xprt-common > Or group remove for xprint > ...
Are you sure you're using "apt-get dist-upgrade" and not one of the other front-ends? I currently have apt-get v0.5.28.6. When I purge the new packages, install xprt-xprintorg and xprt-common (-8) and run "apt-get dist-upgrade, the output and behaviour I see looks significantly different: # apt-get dist-upgrade Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done The following packages will be REMOVED: xprt-common The following NEW packages will be installed: xprint xprint-common The following packages will be upgraded: xprt-xprintorg 1 upgraded, 2 newly installed, 1 to remove and 0 not upgraded. Need to get 2083kB of archives. After unpacking 20.5kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 ftp://debian.anu.edu.au unstable/main xprt-xprintorg 1:0.1.0.alpha1-9 [820B] Get:2 ftp://debian.anu.edu.au unstable/main xprint-common 1:0.1.0.alpha1-9 [368kB] Get:3 ftp://debian.anu.edu.au unstable/main xprint 1:0.1.0.alpha1-9 [1714kB] Fetched 2083kB in 0s (2662kB/s) After unpacking 20.5kB of additional disk space will be used. Do you want to continue? [Y/n] Preconfiguring packages ... (Reading database ... 146619 files and directories currently installed.) Preparing to replace xprt-xprintorg 0.1.0.alpha1-8 (using .../xprt-xprintorg_1%3a0.1.0.alpha1-9_all.deb) ... Stopping Xprint servers: Xprt. Unpacking replacement xprt-xprintorg ... (Reading database ... 146606 files and directories currently installed.) Removing xprt-common ... Stopping Xprint servers: Xprt. Selecting previously deselected package xprint-common. (Reading database ... 145692 files and directories currently installed.) Unpacking xprint-common (from .../xprint-common_1% 3a0.1.0.alpha1-9_all.deb) ... Selecting previously deselected package xprint. Unpacking xprint (from .../xprint_1%3a0.1.0.alpha1-9_i386.deb) ... Setting up xprint-common (0.1.0.alpha1-9) ... Installing new version of config file /etc/default/xprint ... Stopping Xprint servers: Xprt. Starting Xprint servers: Xprt. Setting up xprint (0.1.0.alpha1-9) ... Restarting Xprint server(s): Xprt. Stopping Xprint servers: Xprt. Starting Xprint servers: Xprt. Setting up xprt-xprintorg (0.1.0.alpha1-9) ... ################# Notice how xprt-common gets removed automatically and xprint and xprint-common are pulled in. xprint-common declares a "Conflicts:" dependency on xprt-common in order to make this happen. I get the same behaviour (xprt-common removed and replaced automatically) using the aptitude front-end (v0.2.15.9). Anyway, the quick and easy solution for you to get the system working is to just remove (or purge) xprt-common by hand, and xprt-xprintorg along with it. Then "apt-get install xprint". I apologise for the inconveniences you've been experiencing with the upgrade. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
