[Debian-med-packaging] Bug#830984: fixed in ball 1.4.3~beta1-2 -- only on amd64

Andreas Tille andreas at an3as.eu
Sun Nov 13 19:21:51 UTC 2016


Hi Danny,

On Sun, Nov 13, 2016 at 07:01:15PM +0100, Danny Edel wrote:
> I have created and git-pushed a patch to debian/rules.  I did not update
> the changelog, since it didn't look like the one uploaded to unstable
> earlier today and I wanted to avoid a merge conflict on your side.

Shame on lazy me - pushed now.
 
> If you could review / edit changelog / upload, that would be nice.
> 
> A quick test on an i386 chroot with the build command replaced by
> /bin/true suggests it does exactly what it's supposed to.  It ran the
> test suite, ignored the inevitable error and issued a diagnostic.  It
> even printed my warning multiple times : )  The computer will ignore it
> of course, but it might prompt a human reader to get involved.

Sounds very sensible.
 
> If the new revision actually builds, I would suggest we keep this bug
> open (I wrote the bug number into d/rules) and downgrade its severity to
> important.

Well, we can do so, yes.
 
> I don't have the time right now to dig into the i386 issues in detail.
> If that changes, I might un-dust my old Celeron-based laptop and let it
> compile for a few days.  If it can actually run stretch/sid.  I remember
> reading something on d-devel about raising the minimum processor
> requirements for the i386 port…

If you want to do so for academic reasons nobody will stop you.
However, for practical cases this might not be very important research.

Kind regards

     Andreas.

-- 
http://fam-tille.de



More information about the Debian-med-packaging mailing list