Processing commands for controlbugs.debian.org:

> #FTBFS on i386 bug, current lenny/sid version built fine on the i386 buildd
> close 426415 2.4.6-1
Bug#426415: gimp: Build stalls
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.4.6-1, send any further explanations to 
"Clayborne Arevalo" <[EMAIL PROTECTED]>

> #request to change a build dependency, current lenny/sid version has the
> change
Unknown command or malformed arguments to command.

> close 426306 2.2.10-3
Bug#426306: Suspend function in laptop broken
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.2.10-3, send any further explanations to 
Rodrigo Gadea <[EMAIL PROTECTED]>

> #complaint about non-free files in source, files are not there in current
> #lenny/sid version
> close 438326 3.1.1-3
Bug#438326: Source package contains non-free IETF RFC/I-D's
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 3.1.1-3, send any further explanations to Simon 
Josefsson <[EMAIL PROTECTED]>

> #FTBFS on sparc bug, current lenny/sid version built fine on the sparc
> buildd
Unknown command or malformed arguments to command.

> close 442308 1.8.8.git.2008.03.24-8
Bug#442308: parted_1.8.7.git.2007.07.30-1(sparc/experimental): FTBFS: C99 
inline functions are not supported; using GNU89
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 1.8.8.git.2008.03.24-8, send any further 
explanations to Frank Lichtenheld <[EMAIL PROTECTED]>

> #FTBFS if built twice in a row bug, current lenny/sid version FTBFS if built
> #twice in a row in my lenny chroot
> found 442635 1.2.1-3
Bug#442635: libgenerics: FTBFS if build twice in a row
Bug marked as found in version 1.2.1-3 and reopened.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to