Bug#343473: [Pkg-shadow-devel] Please do not build package on hurd-i386, breaks debootstrap

Alexander Gattin xrgtn at yandex.ru
Sun Dec 18 14:58:11 UTC 2005


Hi!

On Sun, Dec 18, 2005 at 12:25:13PM +0100, Michael Banck wrote:
> On Sun, Dec 18, 2005 at 12:47:03PM +0200, Alexander Gattin wrote:
> > On Sun, Dec 18, 2005 at 03:04:00AM +0100, Michael Banck wrote:
> > > On Sun, Dec 18, 2005 at 12:01:41AM +0200, Alexander Gattin wrote:
> > > > WRT to the patch you sent -- alternative way to achieve
> > > > the same effect would be to make "login" package
> > > > non-required on The Hurd, wouldn't it?

BTW, there are 3 other ways to work around the bug:
1) place shadow's login, su et al. in
   /bin/login.shadow, /bin/su.shadow and so on (when
   packaging for the Hurd)
2) use diversions
3) use alternatives

what do you think?

> > You mean "override" files, like e.g. dpkg-scanpackages
> > uses? Sorry for my misunderstanding...
> 
> No, this is an archive-specific thing.  To better manage releases, the
> release manager and ftp-master can override the priorities of packages,
> like demoting something to 'optional' even though the maintainer thinks
> it should really be 'standard' for some reason.  Such, every binary
> package has a hard-defined priority assigned.

Judging by your description it's quite the same file,
e.g. I have the next line in /usr/src/custom/overrides:
> kernel-patch-ntfs2	extra	devel

Because I have pretty small repository of my custom
pkgs, I'm almost satisfied by such simple and rather
limited tool as dpkg-scanpackages, and don't know
details of what Debian uses.

-- 
WBR,
xrgtn




More information about the Pkg-shadow-devel mailing list