[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#485922: marked as done (apr: -fstack-protector results in FTBFS on etch)

Your message dated Tue, 20 Apr 2010 23:51:50 +0200
with message-id <201004202351.50715.sf@sfritsch.de>
and subject line Re: Bug#485922: apr: -fstack-protector results in FTBFS on etch
has caused the Debian Bug report #485922,
regarding apr: -fstack-protector results in FTBFS on etch
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
485922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485922
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apr
Version: 1.2.12-3
Severity: wishlist


Dear Maintainer,

The new stack-protector options prevent this package from being
backported to etch.

Please make the -fstack-protector clase in debian/rules optional for releases 
later than etch (for example using lsb_release -c -s) or even nicer, optional 
for releases of GCC that provide the stack-protector feature.

Otherwise, please conflict with earlier verions of GCC (for example the
one in etch, etc).

Thanks!

Regards,

Allard


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (600, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.7-fwsh-byte
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8)

--- End Message ---
--- Begin Message --- 
On Thursday 12 June 2008, Allard Hoeve wrote:
> The new stack-protector options prevent this package from being
> backported to etch.

Unfortunately this bug has not been fixed before etch reached its end 
of life. I am therefore closing the report.

--- End Message ---
Reply to: