cohomcalg_0.31d+ds-1_amd64.changes uploaded successfully to localhost
along with the files:
cohomcalg_0.31d+ds-1.dsc
cohomcalg_0.31d+ds.orig.tar.gz
cohomcalg_0.31d+ds-1.debian.tar.xz
cohomcalg-common_0.31d+ds-1_all.deb
cohomcalg-dbgsym_0.31d+ds-1_amd64.deb
frobby_0.9.0-4_amd64.changes uploaded successfully to localhost
along with the files:
frobby_0.9.0-4.dsc
frobby_0.9.0-4.debian.tar.xz
frobby_0.9.0-4_amd64.buildinfo
frobby_0.9.0-4_amd64.deb
libfrobby-dev_0.9.0-4_amd64.deb
libfrobby-doc_0.9.0-4_all.deb
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 27 Aug 2017 09:44:02 +
Source: coinmp
Binary: coinor-libcoinmp-dev coinor-libcoinmp1v5
Architecture: source amd64
Version: 1.8.3-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Team
Hi Rene,
thanks for the bug report and sorry for inconvenience. Upstream did
not change the SO-version, so I decided not to do it explicitly and
request transition. Looks like the changes were minimal.
If the coinmp-recompilation really fixes your problem, I would ask for
binnmus of all
Hi,
On Sun, Aug 27, 2017 at 01:26:30PM +0200, Anton Gladky wrote:
> thanks for the bug report and sorry for inconvenience. Upstream did
> not change the SO-version, so I decided not to do it explicitly and
> request transition. Looks like the changes were minimal.
>
> If the coinmp-recompilation
On Sun, 2017-08-27 at 12:00 +, Luca Falavigna wrote:
> Hi,
>
> libdolfin2017.1 gained a dependency on libparmetis4.0, which is in
> non-free.
Weird. parmetis support is explicitly switched off at configure time.
Drew
--
debian-science-maintainers mailing list
coinmp_1.8.3-2_amd64.changes uploaded successfully to localhost
along with the files:
coinmp_1.8.3-2.dsc
coinmp_1.8.3-2.debian.tar.xz
coinmp_1.8.3-2_amd64.buildinfo
coinor-libcoinmp-dev_1.8.3-2_amd64.deb
coinor-libcoinmp1v5-dbgsym_1.8.3-2_amd64.deb
coinor-libcoinmp1v5_1.8.3-2_amd64.deb
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 13 Aug 2017 19:56:10 -0400
Source: frobby
Binary: frobby libfrobby0 libfrobby-dev libfrobby-doc
Architecture: source amd64 all
Version: 0.9.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science
binary:cohomcalg is NEW.
binary:cohomcalg-common is NEW.
binary:cohomcalg-common is NEW.
binary:cohomcalg is NEW.
source:cohomcalg 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
binary:liboce-foundation11 is NEW.
binary:liboce-modeling11 is NEW.
binary:liboce-ocaf-lite11 is NEW.
binary:liboce-ocaf11 is NEW.
binary:liboce-visualization11 is NEW.
binary:liboce-visualization11 is NEW.
binary:liboce-modeling11 is NEW.
binary:liboce-ocaf11 is NEW.
binary:liboce-foundation11 is
Your message dated Sun, 27 Aug 2017 08:54:22 +
with message-id
and subject line Bug#872020: fixed in frobby 0.9.0-4
has caused the Debian Bug report #872020,
regarding frobby FTBFS: latex: not found
to be marked as done.
This means that you claim that the
Hi,
libdolfin2017.1 gained a dependency on libparmetis4.0, which is in non-free.
Cheers,
Luca
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
--
debian-science-maintainers mailing
On Sun, Aug 27, 2017 at 01:59:04PM +0200, Rene Engelhard wrote:
> for coinmp and libreoffice (5.4.1 release will be next week) if we uploaded
> coinmp 1.8.3 to unstable...
Now uploaded coinmp 1.8.3-2 to unstable.
Let's see.
Test succeeds at least.
Still I believe that this should be "correctly"
oce_0.18.2-1~exp1_amd64.changes uploaded successfully to localhost
along with the files:
oce_0.18.2-1~exp1.dsc
oce_0.18.2.orig.tar.gz
oce_0.18.2-1~exp1.debian.tar.xz
liboce-foundation-dev_0.18.2-1~exp1_amd64.deb
liboce-foundation11-dbgsym_0.18.2-1~exp1_amd64.deb
coinmp_1.8.3-1_amd64.changes uploaded successfully to localhost
along with the files:
coinmp_1.8.3-1.dsc
coinmp_1.8.3.orig.tar.gz
coinmp_1.8.3-1.debian.tar.xz
coinmp_1.8.3-1_amd64.buildinfo
coinor-libcoinmp-dev_1.8.3-1_amd64.deb
coinor-libcoinmp1v5-dbgsym_1.8.3-1_amd64.deb
sagemath_8.0-5_source.changes uploaded successfully to localhost
along with the files:
sagemath_8.0-5.dsc
sagemath_8.0-5.debian.tar.xz
sagemath_8.0-5_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
debian-science-maintainers mailing list
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 27 Aug 2017 22:12:28 +0200
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca
sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu
sagemath-doc-it
Title: Documento sin tÃtulo
Dear Exporter ,
We want to purchase your exporting goods, pls quote your last price.Attached PO #193 - #194 is our quotation and list of items wanted from you.Kindly check it.
Ponir Hossain
--
debian-science-maintainers mailing list
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: r-cran-lmertest
Version : 2.0-33
Upstream Author : Alexandra Kuznetsova, Per Bruun Brockhoff, Rune Haubo
Bojesen Christensen
* URL : https://cran.r-project.org/package=lmerTest
*
sagemath-database-conway-polynomials_0.5-3_source.changes uploaded successfully
to localhost
along with the files:
sagemath-database-conway-polynomials_0.5-3.dsc
sagemath-database-conway-polynomials_0.5-3.debian.tar.xz
sagemath-database-conway-polynomials_0.5-3_source.buildinfo
Greetings,
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 27 Aug 2017 14:52:58 +0200
Source: brial
Binary: python-brial python-polybori libbrial-dev libbrial0 libbrial0-dbg
libbrial-groebner-dev libbrial-groebner0 libbrial-groebner0-dbg
Architecture: source
Version:
On Sun, Aug 27, 2017 at 03:16:46PM +0200, Anton Gladky wrote:
> > Still I believe that this should be "correctly" fixed.
>
> You mean to increase so-version even if upstream does not do it and
> to start the normal transition process? I think it is possible.
That's actually your only option.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 27 Aug 2017 14:50:01 +0200
Source: sagemath-database-conway-polynomials
Binary: sagemath-database-conway-polynomials
Architecture: source
Version: 0.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian
brial_0.8.7-2_source.changes uploaded successfully to localhost
along with the files:
brial_0.8.7-2.dsc
brial_0.8.7-2.debian.tar.xz
brial_0.8.7-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
debian-science-maintainers mailing list
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 27 Aug 2017 12:42:17 +
Source: coinmp
Binary: coinor-libcoinmp-dev coinor-libcoinmp1v5
Architecture: source amd64
Version: 1.8.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Processing commands for cont...@bugs.debian.org:
> # 3.8
> block 873331 by 873401 873403 873409 873410 873408 873407 873405 873417
Bug #873331 [ftp.debian.org] RM: llvm-toolchain-3.8 -- ROM; Too many version of
llvm-toolchain in unstable
873331 was not blocked by any bugs.
873331 was not
Source: frobby
Version: 0.9.0-4
Severity: serious
Example:
https://buildd.debian.org/status/fetch.php?pkg=frobby=i386=0.9.0-4=1503827903=0
...
Transcript written on bin/doc//manual.log.
cd bin; dvips doc/manual.dvi
rm -rf bin/doc
mkdir bin/doc
for i in 1 2 3; do pdflatex
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 27 Aug 2017 16:00:52 +0200
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca
sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu
sagemath-doc-it
eStatement verification
Account : **
ID Number : **
Dear Account Beneficiary 01799
Your statement
Attached is your electronic statement foR aPRIL
Your security
The additional verifications were added to help prevent online fraud.
Information only known to you isdisplayed
Hi Mattia,
thanks for the tip! I have recompiled both libs with the same
current gcc-7.2. And it looks like there are no dropped symbols
(see file old-gcc7_new-gcc7.diff in attachment).
But if I compare new so-file with the one shipped with Stretch
(compiled with gcc6)
the diff contains some
> Still I believe that this should be "correctly" fixed.
You mean to increase so-version even if upstream does not do it and
to start the normal transition process? I think it is possible.
> P.S.: Is it intended that coinutils contains
> /usr/lib/x86_64-linux-gnu/pkgconfig/coindatasample.pc or
binary:r-cran-lmertest is NEW.
binary:r-cran-lmertest is NEW.
source:r-cran-lmertest 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
sagemath_8.0-4_source.changes uploaded successfully to localhost
along with the files:
sagemath_8.0-4.dsc
sagemath_8.0-4.debian.tar.xz
sagemath_8.0-4_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
debian-science-maintainers mailing list
r-cran-lmertest_2.0-33-1_amd64.changes uploaded successfully to localhost
along with the files:
r-cran-lmertest_2.0-33-1.dsc
r-cran-lmertest_2.0-33.orig.tar.gz
r-cran-lmertest_2.0-33-1.debian.tar.xz
r-cran-lmertest_2.0-33-1_all.deb
r-cran-lmertest_2.0-33-1_amd64.buildinfo
Greetings,
Source: caffe-contrib
Severity: normal
Hello,
Currently, we have 6 versions of the llvm toolchain in the archive.
I would like to move to 3 versions (4.0, 5.0 and snapshot, aka 6.0)
Could you please update your package to use 4.0 (or, better, 5.0 which will be
released very
soon)?
I will
FYI: The status of the hfst-ospell source package
in Debian's testing distribution has changed.
Previous version: 0.4.5~r343-2
Current version: 0.4.5~r343-2.1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
FYI: The status of the sketch source package
in Debian's testing distribution has changed.
Previous version: 1:0.3.7-4
Current version: 1:0.3.7-6
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
Control: clone -1 -2
Control: reassign -2 nvidia-cuda-toolkit 8.0.44-4
Control: retitle -2 cuda: moving away from clang-3.8 to gcc-6 ?
Control: severity -2 important
Hi,
The CUDA toolkit will not be ready for Clang-4.0 . As claimed by Nvidia,
the highest version that CUDA 9.0 (will be released
Processing control commands:
> clone -1 -2
Bug #873405 [src:caffe-contrib] caffe-contrib: Please update to llvm-toolchain
4.0 or, better, 5.0
Bug 873405 cloned as bug 873468
873331 was blocked by: 873408 873407 873401 873427 873417 873409 873418 873405
873416 873410 873403 873428
873331 was not
39 matches
Mail list logo