Your message dated Sat, 4 Mar 2006 07:34:35 +0100
with message-id <[EMAIL PROTECTED]>
and subject line wrong bug reopened
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: mrename
Version: 1.2-9
Severity: serious

From my pbuilder build log:

...
dh_shlibdeps
dh_gencontrol
dpkg-gencontrol: warning: no utmp entry available and LOGNAME not defined; 
using uid of process (0)
dpkg-architecture: 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-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; 
using uid of process (0)
dpkg-gencontrol: warning: can't parse dependency  
dpkg-gencontrol: error: error occoured while parsing Depends
dh_gencontrol: command returned error code 2304
make: *** [binary-arch] Error 1

Using cat -A build-log, the "can't parse dependency" line ends with two
spaces, so it appears it's choking on a dependency consisting of just a
space.
-- 
Daniel Schepler


--- End Message ---
--- Begin Message ---
I'm closing this bus, since it was reopened by mistake.
Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=353311
for more informations Sjoerd Simons provided about bug #353131,
which was the correct one! :)

Regards,
-- 
Tommaso Moroni
[EMAIL PROTECTED]

--- End Message ---

Reply via email to