Bug#833870: libprimesieve7-dev-common: fails to upgrade from 'testing' - trying to overwrite /usr/include/primesieve/Callback.hpp

Package: libprimesieve7-dev-common Version: 5.7.0+ds-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to

r-cran-tgp 2.4-14-2 MIGRATED to testing

FYI: The status of the r-cran-tgp source package in Debian's testing distribution has changed. Previous version: 2.4-14-1 Current version: 2.4-14-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

python-dtcwt 0.11.0-2 MIGRATED to testing

FYI: The status of the python-dtcwt source package in Debian's testing distribution has changed. Previous version: 0.11.0-1 Current version: 0.11.0-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

surf-alggeo 1.0.6+ds-3 MIGRATED to testing

FYI: The status of the surf-alggeo source package in Debian's testing distribution has changed. Previous version: 1.0.6+ds-2 Current version: 1.0.6+ds-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

imview 1.1.9c-17 MIGRATED to testing

FYI: The status of the imview source package in Debian's testing distribution has changed. Previous version: 1.1.9c-16 Current version: 1.1.9c-17 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

python-arrayfire 3.3.20160516-1 MIGRATED to testing

FYI: The status of the python-arrayfire source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 3.3.20160516-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple

arrayfire 3.3.2+dfsg1-3 MIGRATED to testing

FYI: The status of the arrayfire source package in Debian's testing distribution has changed. Previous version: 3.2.2+dfsg1-2 Current version: 3.3.2+dfsg1-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

nfft 3.3.2~rc2-2 MIGRATED to testing

FYI: The status of the nfft source package in Debian's testing distribution has changed. Previous version: 3.3.0-5 Current version: 3.3.2~rc2-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

Bug#833870: libprimesieve7-dev-common: fails to upgrade from 'testing' - trying to overwrite /usr/include/primesieve/Callback.hpp

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Andreas, thanks for your report. On 09/08/16 17:50, Andreas Beckmann wrote: > Package: libprimesieve7-dev-common > Version: 5.7.0+ds-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with

sympy 1.0-2 MIGRATED to testing

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

gnuplot 5.0.4+dfsg1-3 MIGRATED to testing

FYI: The status of the gnuplot source package in Debian's testing distribution has changed. Previous version: 5.0.3+dfsg3-7 Current version: 5.0.4+dfsg1-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

libitpp 4.3.1-7 MIGRATED to testing

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

ignition-transport 1.3.0-1 MIGRATED to testing

FYI: The status of the ignition-transport source package in Debian's testing distribution has changed. Previous version: 0.9.0-3 Current version: 1.3.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

Processing of primesieve_5.7.0+ds-2_source.changes

primesieve_5.7.0+ds-2_source.changes uploaded successfully to ftp-master.debian.org along with the files: primesieve_5.7.0+ds-2.dsc primesieve_5.7.0+ds.orig.tar.xz primesieve_5.7.0+ds-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org) --

Processing of primesieve_5.7.0+ds-2_source.changes

primesieve_5.7.0+ds-2_source.changes uploaded successfully to localhost along with the files: primesieve_5.7.0+ds-2.dsc primesieve_5.7.0+ds.orig.tar.xz primesieve_5.7.0+ds-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) --

Bug#817017: libopencv-highgui-dev: Should not depend on libgtk2.0-dev

Hello, I was just going to file the same bug (against unstable, and not because of any install problems). I also believe libopencv-highgui-dev should not depend on libgtk2.0- dev, since:  - libgtk2.0 appears to only be used internally by libopencv_highgui   - gtk/gdk headers are not referenced

primesieve_5.7.0+ds-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Aug 2016 00:58:23 + Source: primesieve Binary: primesieve libprimesieve7 libprimesieve7-dev libprimesieve7-dev-common primesieve-bin primesieve-doc Architecture: source Version: 5.7.0+ds-2 Distribution:

Bug#833870: marked as done (libprimesieve7-dev-common: fails to upgrade from 'testing' - trying to overwrite /usr/include/primesieve/Callback.hpp)

Your message dated Wed, 10 Aug 2016 04:29:44 + with message-id and subject line Bug#833870: fixed in primesieve 5.7.0+ds-2 has caused the Debian Bug report #833870, regarding libprimesieve7-dev-common: fails to upgrade from 'testing' - trying to overwrite

Dezaktywacja Przypominamy !!!

Drogi konto uzytkownika poczty elektronicznej, Konto e-mail zostal umieszczony na naszej czarnej liscie serwera SMTP z powodu nieregularnego ruchu z konta email OD. Masz 12 godzin, aby zweryfikowac swoje konto e-mail konta, aby uniknac zawieszenia. i usuwanie wiadomosci

Bug#833846: fflas-ffpack: don't generate optimised code based on the build machine

Package: fflas-ffpack Version: 2.2.1-1 Severity: important Dear Maintainer, fflas-ffpack on amd64 was built with "-msse4.1 -mfma -mavx2" as can be seen from the output of `pkg-config --cflags fflas-ffpack`. This unfortunately makes it crash on amd64 machines that don't support these

Bug#833846: fflas-ffpack: don't generate optimised code based on the build machine

Control: severity -1 serious I was recommended by multiple people to bump the severity of this bug. Also to clarify that i386 should have no optimisation flags, and not "-msse -msse2". My earlier comment was based on a misunderstanding of what "i386 doesn't have mmx" meant; sse and sse2 build

Processed: Re: fflas-ffpack: don't generate optimised code based on the build machine

Processing control commands: > severity -1 serious Bug #833846 [fflas-ffpack] fflas-ffpack: don't generate optimised code based on the build machine Severity set to 'serious' from 'important' -- 833846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833846 Debian Bug Tracking System Contact

Processed: severity of 833846 is serious

Processing commands for cont...@bugs.debian.org: > severity 833846 serious Bug #833846 [fflas-ffpack] fflas-ffpack: don't generate optimised code based on the build machine Ignoring request to change severity of Bug 833846 to the same value. > thanks Stopping processing here. Please contact me

Bug#831442: mpich: Broken /usr/lib/libmpich.so.12 symlink, depending on installation order

Control: severity -1 normal Dear all, I have been able to work around this bug in yorick by adding a file debian/shlibs.local in the source tree with this single line: libmpich 12 libmpich12 Le 08/08/2016 12:12, Thibaut Paumard a écrit : > Hi have open a new bug against libc-bin (ldconfig) to

Processed: Re: Bug#831442: mpich: Broken /usr/lib/libmpich.so.12 symlink, depending on installation order

Processing control commands: > severity -1 normal Bug #831442 [src:mpich] mpich: Broken /usr/lib/libmpich.so.12 symlink, depending on installation order Severity set to 'normal' from 'serious' -- 831442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831442 Debian Bug Tracking System Contact

Bug#831406: marked as done (yorick: FTBFS: dpkg-shlibdeps: error: no dependency information found for /usr/lib/libmpich.so.12 (used by debian/yorick-mpy-mpich2/usr/lib/yorick/bin/mpy.mpich2))

Your message dated Tue, 09 Aug 2016 06:33:57 + with message-id and subject line Bug#831406: fixed in yorick 2.2.04+dfsg1-6 has caused the Debian Bug report #831406, regarding yorick: FTBFS: dpkg-shlibdeps: error: no dependency information found for

Processing of yorick_2.2.04+dfsg1-6_source.changes

yorick_2.2.04+dfsg1-6_source.changes uploaded successfully to localhost along with the files: yorick_2.2.04+dfsg1-6.dsc yorick_2.2.04+dfsg1-6.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- debian-science-maintainers mailing list

yorick_2.2.04+dfsg1-6_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 09 Aug 2016 06:01:28 +0200 Source: yorick Binary: yorick yorick-dbg yorick-data yorick-dev yorick-mpy-mpich2 yorick-mpy-openmpi yorick-mpy-common yorick-doc yorick-full Architecture: source Version:

Processing of libgetdata_0.9.3-2_amd64.changes

libgetdata_0.9.3-2_amd64.changes uploaded successfully to localhost along with the files: libgetdata_0.9.3-2.dsc libgetdata_0.9.3-2.debian.tar.xz libf95getdata6-dbgsym_0.9.3-2_amd64.deb libf95getdata6_0.9.3-2_amd64.deb libfgetdata5-dbgsym_0.9.3-2_amd64.deb

Bug#833846: fflas-ffpack: don't generate optimised code based on the build machine

Control: tags -1 pending On 08/09/2016 07:53 AM, Ximin Luo wrote: Control: severity -1 serious I was recommended by multiple people to bump the severity of this bug. Also to clarify that i386 should have no optimisation flags, and not "-msse -msse2". My earlier comment was based on a

Processed: Re: Bug#833846: fflas-ffpack: don't generate optimised code based on the build machine

Processing control commands: > tags -1 pending Bug #833846 [fflas-ffpack] fflas-ffpack: don't generate optimised code based on the build machine Added tag(s) pending. -- 833846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833846 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processing of fflas-ffpack_2.2.1-2_amd64.changes

fflas-ffpack_2.2.1-2_amd64.changes uploaded successfully to localhost along with the files: fflas-ffpack_2.2.1-2.dsc fflas-ffpack_2.2.1-2.debian.tar.xz fflas-ffpack-common_2.2.1-2_all.deb fflas-ffpack-dev-doc_2.2.1-2_all.deb fflas-ffpack-user-doc_2.2.1-2_all.deb

fflas-ffpack_2.2.1-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 09 Aug 2016 08:47:36 -0400 Source: fflas-ffpack Binary: fflas-ffpack fflas-ffpack-common fflas-ffpack-user-doc fflas-ffpack-dev-doc Architecture: source all amd64 Version: 2.2.1-2 Distribution: unstable Urgency:

libgetdata_0.9.3-2_amd64.changes is NEW

Mapping sid to unstable. binary:python3-pygetdata is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are

Bug#833846: marked as done (fflas-ffpack: don't generate optimised code based on the build machine)

Your message dated Tue, 09 Aug 2016 16:21:21 + with message-id and subject line Bug#833846: fixed in fflas-ffpack 2.2.1-2 has caused the Debian Bug report #833846, regarding fflas-ffpack: don't generate optimised code based on the build machine to be

apertium-hbs-mkd 0.1.0~r57554-1 MIGRATED to testing

FYI: The status of the apertium-hbs-mkd source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.1.0~r57554-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple

apertium-kaz-tat 0.2.1~r57554-1 MIGRATED to testing

FYI: The status of the apertium-kaz-tat source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.2.1~r57554-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple

Bug#818817: Closing the bug #818817

notfound 818817 1.0+dfsg1-1 tag 818817 +unreproducible thanks Hi Martin, I am not able to reproduce the bug in current sid environment, where libc_2.23 is by default already. Thus I am closing the bug. Best regards Anton -- debian-science-maintainers mailing list

Processing of getfem++_5.0+dfsg1-1_amd64.changes

getfem++_5.0+dfsg1-1_amd64.changes uploaded successfully to localhost along with the files: getfem++_5.0+dfsg1-1.dsc getfem++_5.0+dfsg1.orig.tar.xz getfem++_5.0+dfsg1-1.debian.tar.xz libgetfem++-dev_5.0+dfsg1-1_amd64.deb libgetfem5++-dbgsym_5.0+dfsg1-1_amd64.deb

Bug#833383: ros-std-msgs: split headers and message definitions

Hello Jochen, On 2016-08-05 10:28, Jochen Sprickerhof wrote: So we move everything in /usr/share/std_msgs, right? Package: ros-std-msgs Section: devel Something like that? Sounds good to me. Would you be interested in working on it? Yes, I can work on it. I suppose this should be done

Bug#833383: ros-std-msgs: split headers and message definitions

Hi Daniele, * Daniele E. Domenichelli [2016-08-09 20:03]: > I suppose this should be done to all the ros-*-msgs packages, right? Yes :). > I already have a patch for ros-std-msgs, you can find it here: > >

Processed: Closing the bug #818817

Processing commands for cont...@bugs.debian.org: > notfound 818817 1.0+dfsg1-1 Bug #818817 [woo] woo: FTBFS with libc 2.23: 'isnan' was not declared in this scope There is no source info for the package 'woo' at version '1.0+dfsg1-1' with architecture '' Unable to make a source version for

Bug#818817: marked as done (woo: FTBFS with libc 2.23: 'isnan' was not declared in this scope)

Your message dated Tue, 9 Aug 2016 21:46:32 +0200 with message-id and subject line Closing the bug #818817 has caused the Debian Bug report #818817, regarding woo: FTBFS with libc 2.23: 'isnan' was not declared in this scope to

getfem++_5.0+dfsg1-1_amd64.changes is NEW

binary:libgetfem5++ is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the