Your message dated Wed, 20 Dec 2006 18:02:42 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402331: FTBFS: "unable to find user alias"
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: qmail
Version: 1.03-40
Severity: serious
Using pbuilder in an i386 chroot:
[...]
( ./auto-uid auto_uida `head -1 conf-users` \
&&./auto-uid auto_uidd `head -2 conf-users | tail -1` \
&&./auto-uid auto_uidl `head -3 conf-users | tail -1` \
&&./auto-uid auto_uido `head -4 conf-users | tail -1` \
&&./auto-uid auto_uidp `head -5 conf-users | tail -1` \
&&./auto-uid auto_uidq `head -6 conf-users | tail -1` \
&&./auto-uid auto_uidr `head -7 conf-users | tail -1` \
&&./auto-uid auto_uids `head -8 conf-users | tail -1` \
&&./auto-gid auto_gidq `head -1 conf-groups` \
&&./auto-gid auto_gidn `head -2 conf-groups | tail -1` \
) > auto_uids.c.tmp && mv auto_uids.c.tmp auto_uids.c
fatal: unable to find user alias
make[1]: *** [auto_uids.c] Error 111
make[1]: Leaving directory `/tmp/buildd/qmail-1.03'
make: *** [build] Error 2
pbuilder: Failed autobuilding of package
[...]
Cheers,
--
Thomas Huriaux
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Quoting Thomas Huriaux <[EMAIL PROTECTED]>:
My previous emails have gone unanswered, but I have uploaded a new release that
should fix this issue. Look in the upload queue for -41, or wait for when
qmail-src shows back up in testing.
I found the offending single-line of code in the debian/rules file that was
causing the error you were experiencing.
If you feel that this is not fixed, please feel free to re-open the bug.
Cheers!
Jon
--- End Message ---
