Re: Bug#688804: m4 can accidentally link to libsigsegv

2012-11-12 Thread Julien Cristau
On Wed, Sep 26, 2012 at 12:58:08 +0200, Santiago Vila wrote:

 Hi.
 
 [ Cc: debian-release for advice ].
 
 I have received this report which is really two different bugs:
 
 A) The initial one reported by Igor: Building m4 creates a package
 linked with libsigsegv or not depending on the environment. This
 should never happen in a Debian package and that's why we have
 Build-Depends, Build-Conflicts and so on. A Debian package, when built,
 should always create the same .deb.
 
 B) The real fix by Eric: m4 should really be linked against libsigsegv.
 
 
 Release managers: Is it too late in the freeze to fix B? (The patch
 would be very small, it would be a matter of adding a Build-Depends).
 
Yes, it is too late.

 In case it is too late: May I fix bug A in wheezy at least? (In this
 case the .deb would not change in functionality, but the build process
 would never create a different .deb by accident).
 
This one would probably have been ok, but not with 1.4.16-4 now being in
sid with the other change.

Cheers,
Julien


signature.asc
Description: Digital signature


Re: Bug#688804: m4 can accidentally link to libsigsegv

2012-09-26 Thread Santiago Vila
Hi.

[ Cc: debian-release for advice ].

I have received this report which is really two different bugs:

A) The initial one reported by Igor: Building m4 creates a package
linked with libsigsegv or not depending on the environment. This
should never happen in a Debian package and that's why we have
Build-Depends, Build-Conflicts and so on. A Debian package, when built,
should always create the same .deb.

B) The real fix by Eric: m4 should really be linked against libsigsegv.


Release managers: Is it too late in the freeze to fix B? (The patch
would be very small, it would be a matter of adding a Build-Depends).

In case it is too late: May I fix bug A in wheezy at least? (In this
case the .deb would not change in functionality, but the build process
would never create a different .deb by accident).

Thanks.


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.deb.2.02.1209261124450.19...@cantor.unex.es