Re: dpkg conffiles weirdness
On Tue, Jun 06, 2000 at 11:25:43PM +0100, Julian Gilbey wrote: > I used dselect with an APT backend. One of the upgraded packages was > xterm, from version 3.3.6-6 to 3.3.6-7. There's a conffile in the > package: /etc/X11/Xresources/xterm. due to a mistake in xterm package xterm no longer sources this file. a bugreport has already been filed this will be fixed in -8 regards Marcin -- ++ The reason we come up with new versions |Marcin Owsiany | is not to fix bugs. It's the stupidest |[EMAIL PROTECTED]| reason to buy a new version ++ I ever heard.- Bill Gates
dpkg conffiles weirdness
I've just had a bizarre experience upgrading from test-cycle-1 to test-cycle-2, perhaps someone can shed some light? I used dselect with an APT backend. One of the upgraded packages was xterm, from version 3.3.6-6 to 3.3.6-7. There's a conffile in the package: /etc/X11/Xresources/xterm. I had a modified version, which was unceremoniously moved to xterm.dpkg-old and replaced by the new version. No questions were asked. (Incidentally, the backspace key in emacs in an xterm now behaves like ctrl-H. Any ideas why? Yuck!) I tried reinstating the old xterm conffile and reinstalling version 3.3.6-7, but now the conffile wasn't touched. I then tried deleting the conffile and reinstalling; no conffile was installed at all this time. Purging and reinstalling reinstalled the conffile, but nothing less would do so. Does anyone have a clue what might be up? Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED] Debian GNU/Linux Developer, see http://www.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/
Shared directories: Installing the Debian way?
Hi there, I've an interesting problem here: I've several machines running Slink here, and those machines have the /usr directory shared! On every machine there should be the same packages installed. (I think about sharing some other directories as well.) Imagine the following scenario: If I want to install a package on every machine, every machine will need write access to the /usr directory... This doesn't make sense in my situation, because I think write access for ONE machine should be sufficient. If I install a package on a machine having write access to the shared (/usr) directory, the package isn't installed properly on the other machines- the machine doesn't have access to the root (/) of the others. And I've consistency problems with the dpkg database, of course: On all machines but the one I ran dpkg on the package is in the state of being not installed. So I need a method to exclude some directories from installation. The best thing would be (in my case) just to instruct dpkg to ignore everything under the /usr directory tree. (Because it has been already installed) Is this possible? I read several man pages, but didn't find anything. And before I'd start to write huge scripts, I decieded it would be better to askthe experts (you!) how to do it the Debian way. :) Any help is greatly appreciated! Yours, Andreas Jaehnigen P.S.: Please respond to my mail adress, I'm not subscribed to the list (yet). Thanks!
