Bug#842569: mark autoconf2.13 Multi-Arch: foreign

[Manuel A. Fernandez Montecelo]

2017-11-13 17:24 GMT+01:00 Ben Pfaff :
> On Mon, Nov 13, 2017 at 09:22:01AM +0100, Manuel A. Fernandez Montecelo wrote:
>> Hi,
>>
>> Should we close then the bug as fixed in -68?
>
> Oh, the problem is just that the bug wasn't closed?  That's easy enough
> to fix.  I'll close the bug.

Yeah, the reason why I looked into it was that I thought that it was
not fixed, when it actually was.

Thanks!

-- 
Manuel A. Fernandez Montecelo 

Bug#842569: mark autoconf2.13 Multi-Arch: foreign

[Ben Pfaff]

On Mon, Nov 13, 2017 at 09:22:01AM +0100, Manuel A. Fernandez Montecelo wrote:
> Hi,
> 
> 2017-11-13 1:27 GMT+01:00 Ben Pfaff :
> > On Sat, Nov 11, 2017 at 02:48:31PM +0100, Manuel A. Fernandez Montecelo 
> > wrote:
> >> Hi Ben,
> >>
> >> 2016-10-30 13:48 Helmut Grohne:
> >> >Package: autoconf2.13
> >> >Version: 2.13-67
> >> >Tags: patch
> >> >User: helm...@debian.org
> >> >Usertags: rebootstrap
> >> >Control: affects -1 + src:firefox src:firefox-esr src:gcc-3.3 
> >> >src:gcc-m68hc1x src:grass src:icedove src:postgis src:vflib3
> >> >
> >> >The affected packages fail to satisfy their cross Build-Depends, because
> >> >their dependency on autoconf2.13 is not satisfiable. In general,
> >> >Architecture: all packages cannot satisfy cross build dependencies
> >> >unless marked Multi-Arch: foreign.
> >>
> >> The patch is simple enough and affects important packages.
> >>
> >> Would it be possible to apply it in your next uploads?
> >
> > As far as I can tell, this was applied in 2.13-67 and is still in
> > 2.13-68.  What is missing?
> 
> Right, so the header is there but this bug is not mentioned in those
> changelog entris and this bug is not closed.
> 
> It seem that the M-A:foreign wasn't present in -67, that's why Helmut
> reported it, but it's there in -68, uploaded this august:
> 
> https://sources.debian.net/src/autoconf2.13/2.13-67/debian/control/
> https://sources.debian.net/src/autoconf2.13/2.13-67/debian/control/
> 
> Should we close then the bug as fixed in -68?

Oh, the problem is just that the bug wasn't closed?  That's easy enough
to fix.  I'll close the bug.

Bug#842569: mark autoconf2.13 Multi-Arch: foreign

[Manuel A. Fernandez Montecelo]

Hi,

2017-11-13 1:27 GMT+01:00 Ben Pfaff :
> On Sat, Nov 11, 2017 at 02:48:31PM +0100, Manuel A. Fernandez Montecelo wrote:
>> Hi Ben,
>>
>> 2016-10-30 13:48 Helmut Grohne:
>> >Package: autoconf2.13
>> >Version: 2.13-67
>> >Tags: patch
>> >User: helm...@debian.org
>> >Usertags: rebootstrap
>> >Control: affects -1 + src:firefox src:firefox-esr src:gcc-3.3 
>> >src:gcc-m68hc1x src:grass src:icedove src:postgis src:vflib3
>> >
>> >The affected packages fail to satisfy their cross Build-Depends, because
>> >their dependency on autoconf2.13 is not satisfiable. In general,
>> >Architecture: all packages cannot satisfy cross build dependencies
>> >unless marked Multi-Arch: foreign.
>>
>> The patch is simple enough and affects important packages.
>>
>> Would it be possible to apply it in your next uploads?
>
> As far as I can tell, this was applied in 2.13-67 and is still in
> 2.13-68.  What is missing?

Right, so the header is there but this bug is not mentioned in those
changelog entris and this bug is not closed.

It seem that the M-A:foreign wasn't present in -67, that's why Helmut
reported it, but it's there in -68, uploaded this august:

https://sources.debian.net/src/autoconf2.13/2.13-67/debian/control/
https://sources.debian.net/src/autoconf2.13/2.13-67/debian/control/

Should we close then the bug as fixed in -68?


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#842569: mark autoconf2.13 Multi-Arch: foreign

[Ben Pfaff]

On Sat, Nov 11, 2017 at 02:48:31PM +0100, Manuel A. Fernandez Montecelo wrote:
> Hi Ben,
> 
> 2016-10-30 13:48 Helmut Grohne:
> >Package: autoconf2.13
> >Version: 2.13-67
> >Tags: patch
> >User: helm...@debian.org
> >Usertags: rebootstrap
> >Control: affects -1 + src:firefox src:firefox-esr src:gcc-3.3 
> >src:gcc-m68hc1x src:grass src:icedove src:postgis src:vflib3
> >
> >The affected packages fail to satisfy their cross Build-Depends, because
> >their dependency on autoconf2.13 is not satisfiable. In general,
> >Architecture: all packages cannot satisfy cross build dependencies
> >unless marked Multi-Arch: foreign.
> 
> The patch is simple enough and affects important packages.
> 
> Would it be possible to apply it in your next uploads?

As far as I can tell, this was applied in 2.13-67 and is still in
2.13-68.  What is missing?

Thanks,

Ben.

Bug#842569: mark autoconf2.13 Multi-Arch: foreign

[Manuel A. Fernandez Montecelo]

Hi Ben,

2016-10-30 13:48 Helmut Grohne:

Package: autoconf2.13
Version: 2.13-67
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:firefox src:firefox-esr src:gcc-3.3 src:gcc-m68hc1x 
src:grass src:icedove src:postgis src:vflib3

The affected packages fail to satisfy their cross Build-Depends, because
their dependency on autoconf2.13 is not satisfiable. In general,
Architecture: all packages cannot satisfy cross build dependencies
unless marked Multi-Arch: foreign.


The patch is simple enough and affects important packages.

Would it be possible to apply it in your next uploads?


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#842569: mark autoconf2.13 Multi-Arch: foreign

[Helmut Grohne]

Package: autoconf2.13
Version: 2.13-67
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:firefox src:firefox-esr src:gcc-3.3 src:gcc-m68hc1x 
src:grass src:icedove src:postgis src:vflib3

The affected packages fail to satisfy their cross Build-Depends, because
their dependency on autoconf2.13 is not satisfiable. In general,
Architecture: all packages cannot satisfy cross build dependencies
unless marked Multi-Arch: foreign.

For autoconf2.13, we need to look closely to determine whether such a
marking is correct. It does have a postinst script. Such scripts can
have architecture-dependent behaviour (e.g. compiling python modules),
but removing diversions is not considered architecture-dependent. It
also has runtime dependencies that are not marked Multi-Arch: foreign.
In particular, autoconf2.13 depends on:
 * m4 (marked Multi-Arch: foreign) 
 * debianutils (marked Multi-Arch: foreign)
 * perl
 * libfile-temp-perl
 * dpkg | install-info (both marked Multi-Arch: foreign)
So the only dependencies that may expose architecture-awareness are the
perl ones. Fortunately, autoconf2.13 does not export any perl modules
and its scripts (e.g. autoscan2.13) do not use architecture-specific
behaviour. So marking autoconf2.13 Multi-Arch: foreign looks correct and
fits with the fact that autoconf already is marked that way.

Please consider applying the attached patch.

Helmut
diff --minimal -Nru autoconf2.13-2.13/debian/changelog 
autoconf2.13-2.13/debian/changelog
--- autoconf2.13-2.13/debian/changelog  2015-10-17 08:58:58.0 +0200
+++ autoconf2.13-2.13/debian/changelog  2016-10-30 13:39:29.0 +0100
@@ -1,3 +1,10 @@
+autoconf2.13 (2.13-67.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark autoconf2.13 Multi-Arch: foreign.  Closes: #-1.
+
+ -- Helmut Grohne   Sun, 30 Oct 2016 13:39:13 +0100
+
 autoconf2.13 (2.13-67) unstable; urgency=low
 
   * debian/rules: Force LC_ALL=C to ensure that [a-z]*.1 does not match
diff --minimal -Nru autoconf2.13-2.13/debian/control 
autoconf2.13-2.13/debian/control
--- autoconf2.13-2.13/debian/control2015-08-02 18:10:05.0 +0200
+++ autoconf2.13-2.13/debian/control2016-10-30 13:39:05.0 +0100
@@ -8,6 +8,7 @@
 
 Package: autoconf2.13
 Architecture: all
+Multi-Arch: foreign
 Depends: m4, debianutils (>= 1.8), perl, libfile-temp-perl, ${misc:Depends}, 
dpkg (>= 1.15.4) | install-info
 Suggests: gnu-standards
 Description: automatic configure script builder (obsolete version)