Re: Bug#539278: lib32z1: not installable on kfreebsd-amd64/ppc64
On Thu, Jul 30, 2009 at 01:41:51PM +0200, Aurelien Jarno wrote: > Note that this solution (suggested by one of the dpkg maintainers) is > the one that has been tested and implemented for libc6-dev-i386. No > problem have been reported so far, contrary to the Pre-Depends version > which sometimes causes troubles to apt and aptitude. Given that and what you say on IRC I'll have a look soon. I'm very wary of anything to do with this transition due to the multiple issues with it. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#539278: lib32z1: not installable on kfreebsd-amd64/ppc64
On Thu, Jul 30, 2009 at 01:00:11PM +0200, Aurelien Jarno wrote: > In this case a Pre-Depends is overkill, a simple Conflicts is enough. > Please find a patch below to fix the problem. Please confirm this with the amd64 porters. This whole transitions has been plagued with problems; the predepency was added due to breakage in the original transition plan. I'm not going to do anything with this without confirmation, this transition has been nothing but trouble. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: chroot with NIS
On Thu, Aug 10, 2006 at 11:35:52AM +0200, Bernd Schubert wrote: > for us it was just sufficient to bind mount /var/yp into the chroot > environment. This should be the only unusual thing that is required. The ypbind daemon maintians state in this directory which tells applications that need to get information from the NIS server where to look. Everything else works over the network. > Of course, you need to adjust the > chroots /etc/passwd, /etc/group and /etc/nssswitch.conf. You shouldn't need to update nsswitch.conf for normal password access. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
