Your message dated Mon, 31 Jul 2006 17:34:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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: libflorist-3.15p-1
Version: 3.15p-4
Severity: important
I tried building the package with a version of 3.15p-4+pb1 here, and got this
from pbuilder:
...
fakeroot debian/rules clean
dpkg-parsechangelog: warning: no utmp entry available and LOGNAME not defined;
using uid of process (0)
debian: warning: no utmp entry available and LOGNAME not defined; using uid of
process (0)
dpkg-parsechangelog: warning: no utmp entry available and LOGNAME not defined;
using uid of process (0)
debian: warning: no utmp entry available and LOGNAME not defined; using uid of
process (0)
dpkg-parsechangelog: warning: no utmp entry available and LOGNAME not defined;
using uid of process (0)
debian: warning: no utmp entry available and LOGNAME not defined; using uid of
process (0)
debian/rules:61: *** multiple target patterns. Stop.
Since the package still builds fine under pbuilder without the version change,
this looks like a problem parsing the version number. This means that any
attempt to schedule a binNMU on the buildd's will FTBFS.
--
Daniel Schepler
--- End Message ---
--- Begin Message ---
removed from the archive (superseded by libflorist, RC-buggy)
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
