Bug#813415: libvigraimpex5v5: soname bump without package name change

On 2016-02-13 Daniel Stender wrote: > On 13.02.2016 07:52, Andreas Metzler wrote: [...] > > You are going for 1.11 rc1, I assume? > That's a good idea! That's not official release candidate but would > be much clearer. According to dpkg-gensymbols the ABI has not

Bug#813415: libvigraimpex5v5: soname bump without package name change

On 13.02.2016 10:32, Andreas Metzler wrote: > On 2016-02-13 Daniel Stender wrote: > [...] >> Ubuntu has patched -O2 for -O3 on ppc64el, but it's -O2 anyway. Is Ubuntu >> building with -O3? > > Yes, Ubuntu is building with -O3 by default, at least on some archs. Ah,

Bug#813415: libvigraimpex5v5: soname bump without package name change

On 13.02.2016 10:37, Andreas Metzler wrote: > On 2016-02-13 Daniel Stender wrote: >> On 13.02.2016 07:52, Andreas Metzler wrote: > [...] >>> You are going for 1.11 rc1, I assume? > >> That's a good idea! That's not official release candidate but would >> be much

Bug#814596: please default to openmpi on x32

Package: src:mpi-defaults Version: 1.2 please default to openmpi on x32. Please do it now, so that package maintainers can do the changes for s390x and x32 at once, instead of having to touch packages twice. -- debian-science-maintainers mailing list

Bug#813415: libvigraimpex5v5: soname bump without package name change

On 2016-02-12 Daniel Stender wrote: > Sorry for the delay, a fix is coming up. > In the meanwhile I've did also a ABI check and it seems this one needs a > transition: > http://www.danielstender.com/uploads/compat_report.html [...] FWIW I have doublechecked almost all

Re: python-pynlpl_0.7.7.1-1_amd64.changes REJECTED

Quoting Thorsten Alteholz (2016-02-13 00:00:21) > according to the file header, the license is only GPL-3. > So can you please adapt your debian/copyright? Hi Thorsten, Thanks for processing the package. If I understand correctly (it's my first package) this issue is only because of

Bug#814596: already done... ?

> Package: src:mpi-defaults > Version: 1.2 > > please default to openmpi on x32. Please do it now, so that package > maintainers can do the changes for s390x and x32 at once, instead of > having to touch packages twice. Uhm, mpi-defaults=1.2 does seem to default to openmpi on x32. The changelog

Bug#814596: marked as done (please default to openmpi on x32)

Your message dated Sat, 13 Feb 2016 12:46:53 +0100 with message-id <20160213114653.ga19...@angband.pl> and subject line Re: already done... ? has caused the Debian Bug report #814596, regarding please default to openmpi on x32 to be marked as done. This means that you claim that the problem has

freefem++ REMOVED from testing

FYI: The status of the freefem++ source package in Debian's testing distribution has changed. Previous version: 3.38.1-1 Current version: (not in testing) Hint: # 813357,813490 in blacs-mpi Bug #807200: freefem++: Update

mpich 3.2-6 MIGRATED to testing

FYI: The status of the mpich source package in Debian's testing distribution has changed. Previous version: 3.1-6 Current version: 3.2-6 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

Processed: user debian...@lists.debian.org, usertagging 811300, found 798374 in usrmerge/9 ..., affects 814393 ...

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 811300 piuparts There were no usertags set. Usertags are now: piuparts. > found 798374 usrmerge/9 Bug #798374 [piuparts] usrmerge: cannot

Processing of pytango_8.1.8-1_i386.changes

pytango_8.1.8-1_i386.changes uploaded successfully to localhost along with the files: pytango_8.1.8-1.dsc pytango_8.1.8.orig.tar.gz pytango_8.1.8-1.debian.tar.xz python-pytango-dbgsym_8.1.8-1_i386.deb python-pytango-doc_8.1.8-1_all.deb python-pytango_8.1.8-1_i386.deb

pytango_8.1.8-1_i386.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 13 Feb 2016 16:19:55 +0100 Source: pytango Binary: python-pytango python3-pytango python-pytango-doc Architecture: source i386 all Version: 8.1.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Science

Bug#813415: libvigraimpex5v5: soname bump without package name change

On 2016-02-13 Daniel Stender wrote: [...] > Ubuntu has patched -O2 for -O3 on ppc64el, but it's -O2 anyway. Is Ubuntu > building with -O3? Yes, Ubuntu is building with -O3 by default, at least on some archs. cu Andreas -- `What a good friend you are to him, Dr.

Bug#814671: libgmp10: please update symbols for nios2

Source: gmp Version: 2:6.0.0+dfsg-6 Tags: patch User: helm...@debian.org Usertags: rebootstrap Dear gmp maintainer, gmp fails to build from source on nios2 (which is a new architecture from a Debian point of view). dpkg-gensymbols fails missing a lot of symbols. This is kinda expected for a new

Re: python-pynlpl_0.7.7.1-1_amd64.changes REJECTED

Hi Maarten, On Sat, 13 Feb 2016, Maarten van Gompel wrote: Thanks for processing the package. If I understand correctly (it's my first package) this issue is only because of pynlpl/datatypes.py which subsumes MIT licensed code and I should just stick to the the GPLv3 for it as indicated in the

Bug#813415: libvigraimpex5v5: soname bump without package name change

On 2016-02-13 Daniel Stender wrote: > On 13.02.2016 07:52, Andreas Metzler wrote: [...] > > Is there something I can do to help? Currently reverse dependencies are > > broken, due to a binNMU hugin in *testing* will not run at all. > Thanks for the note and the offer.