givaro_4.0.2-1_amd64.changes uploaded successfully to localhost
along with the files:
givaro_4.0.2-1.dsc
givaro_4.0.2.orig.tar.gz
givaro_4.0.2-1.debian.tar.xz
givaro-dev-doc_4.0.2-1_all.deb
givaro-user-doc_4.0.2-1_all.deb
libgivaro-dev_4.0.2-1_amd64.deb
libgivaro-doc_4.0.2-1_all.deb
Une belle bouffée d'oxygène .textbody_body_fe547 {
font-family: Arial, Helvetica, sans-serif !important;
font-size: 16px !important;
line-height: 20px !important;
}
.titre_1_h2_aea04 {
color: #003399 !important;
font-family: Arial, Helvetica, sans-serif !important;
}
.titre_2_h3_96608 {
color: #0
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 /usr/include/primesieve/Callback.hpp
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: uns
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 przych
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)
--
debian-science-mai
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)
--
debia
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 i
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 arc
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
libgetfem5++_5.0+dfsg1-1
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
debian-science-maintainers@li
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 be marked as done.
This means that you claim that the problem has be
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 versi
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:
>
> https://github.com/drdanz/ros-std-msgs/commit/41dcc24cd3a654e612a33e16e5442bf276d861fe
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 t
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
later
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 tim
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 wi
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 rece
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
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 re
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 w
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 yo
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 receiv
-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 pi
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
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 receive
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
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 tim
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 tim
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 marked as done.
This means that you claim
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 routinel
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: m
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
libfgetdata5_0.9.3-2_amd64.deb
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_amd
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 misunder
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 with
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 i
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 o
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 o
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 instructions,
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
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 f
43 matches
Mail list logo
