Bug#883047: [Debian-med-packaging] Bug#883047: canu: Build-depend on mhap to avoid uninstallable binaries

[Afif Elghraoui]

On December 1, 2017 9:12:19 PM EST, Steve Langasek 
 wrote:
>On Fri, Dec 01, 2017 at 03:37:47AM -0500, Afif Elghraoui wrote:
>>  I believe this is
>primarily
>> an issue with wanna-build queuing the package for building on those
>> architectures to begin with [1].
>
>The behavior of wanna-build is by design and I don't believe it will
>ever
>(or should ever) change.  You are asking that the buildds avoid queuing
>the
>package for build based on the availability of dependencies for the
>binary
>packages /that have not yet been built/.  For wanna-build to introspect
>debian/control and parse the Depends: fields of the binary package
>stanzas
>would be an abstraction violation, given that the vast majority of
>binary
>packages in the archive have dependency fields that are at least partly
>generated at package build time.

They could alternatively be checked post-build, pre-upload.

Anyway, there must be a better solution than abusing the build-depends field, 
but if everyone seems content with this, maybe I'll just start copying all 
Depends into Build-Depends from now on.

Afif

Bug#883047: [Debian-med-packaging] Bug#883047: canu: Build-depend on mhap to avoid uninstallable binaries

[Steve Langasek]

On Fri, Dec 01, 2017 at 03:37:47AM -0500, Afif Elghraoui wrote:
> Hi, Steve,

> On November 29, 2017 12:50:55 AM EST, Steve Langasek 
>  wrote:
> >In Ubuntu, we observed that the canu package was not releasable because
> >it generates per-architecture binary packages with a transitive
> >dependency on libssw-java, which is only available on amd64.

> >To work around this issue, I have added an "artificial" build dependency
> >on mhap to the canu package in Ubuntu, so that the package will not build
> >on architectures where mhap is not available.

> >This problem also affects canu in Debian, and is the reason that canu has
> >not migrated to Debian testing;

> Yes, as I saw in https://lists.debian.org/debian-release/2017/10/msg00239.html

> > so I would suggest applying this patch in Debian as well.

> Thanks for your concern.  I did not see much interest on this package and
> so was not really interested in a workaround.  I believe this is primarily
> an issue with wanna-build queuing the package for building on those
> architectures to begin with [1].

The behavior of wanna-build is by design and I don't believe it will ever
(or should ever) change.  You are asking that the buildds avoid queuing the
package for build based on the availability of dependencies for the binary
packages /that have not yet been built/.  For wanna-build to introspect
debian/control and parse the Depends: fields of the binary package stanzas
would be an abstraction violation, given that the vast majority of binary
packages in the archive have dependency fields that are at least partly
generated at package build time.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#883047: [Debian-med-packaging] Bug#883047: canu: Build-depend on mhap to avoid uninstallable binaries

[Afif Elghraoui]

Hi, Steve,

On November 29, 2017 12:50:55 AM EST, Steve Langasek 
 wrote:
>In Ubuntu, we observed that the canu package was not releasable because
>it
>generates per-architecture binary packages with a transitive dependency
>on
>libssw-java, which is only available on amd64.
>
>To work around this issue, I have added an "artificial" build
>dependency on
>mhap to the canu package in Ubuntu, so that the package will not build
>on
>architectures where mhap is not available.
>
>This problem also affects canu in Debian, and is the reason that canu
>has
>not migrated to Debian testing;

Yes, as I saw in https://lists.debian.org/debian-release/2017/10/msg00239.html

> so I would suggest applying this patch
>in
>Debian as well.
>

Thanks for your concern. I did not see much interest on this package and so was 
not really interested in a workaround. I believe this is primarily an issue 
with wanna-build queuing the package for building on those architectures to 
begin with [1].

regards
Afif

1. https://lists.debian.org/debian-wb-team/2017/10/msg9.html

Bug#883047: canu: Build-depend on mhap to avoid uninstallable binaries

[Steve Langasek]

Package: canu
Version: 1.6+dfsg-1
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Afif,

In Ubuntu, we observed that the canu package was not releasable because it
generates per-architecture binary packages with a transitive dependency on
libssw-java, which is only available on amd64.

To work around this issue, I have added an "artificial" build dependency on
mhap to the canu package in Ubuntu, so that the package will not build on
architectures where mhap is not available.

This problem also affects canu in Debian, and is the reason that canu has
not migrated to Debian testing; so I would suggest applying this patch in
Debian as well.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru canu-1.6+dfsg/debian/control canu-1.6+dfsg/debian/control
--- canu-1.6+dfsg/debian/control2017-09-02 06:59:58.0 -0700
+++ canu-1.6+dfsg/debian/control2017-11-28 21:24:18.0 -0800
@@ -9,6 +9,7 @@
libmeryl-dev,
 # For File::Path
libfilesys-df-perl,
+   mhap (>= 2.1),
 Standards-Version: 4.1.0
 Homepage: http://canu.readthedocs.org/en/latest/
 Vcs-Git: https://anonscm.debian.org/git/debian-med/canu.git