Bug#887454: Re-uploaded console-bridge

Hi Jochen, I'm putting Debian Science list in CC. More information about this discussion is in bug #887454. On Sun, Feb 18, 2018 at 01:41:10AM +0100, Jochen Sprickerhof wrote: > * Andreas Tille [2018-02-17 22:30]: > > A not uploaded state has the target distribution

vlfeat 0.9.20+dfsg0-2 MIGRATED to testing

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

lua-torch-image 0~20170420-g5aa1881-5 MIGRATED to testing

FYI: The status of the lua-torch-image source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0~20170420-g5aa1881-5 -- This email is automatically generated once a day. As the installation of new packages into testing happens

lua-torch-optim 0~20170208-g656c42a-3 MIGRATED to testing

FYI: The status of the lua-torch-optim source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0~20170208-g656c42a-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens

spass REMOVED from testing

FYI: The status of the spass source package in Debian's testing distribution has changed. Previous version: 3.7-4 Current version: (not in testing) Hint: Bug #887646: spass FTBFS with glibc 2.26 The script that generates this

lua-torch-graph 0~20161121-g37dac07-2 MIGRATED to testing

FYI: The status of the lua-torch-graph source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0~20161121-g37dac07-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens

ros-metapackages is marked for autoremoval from testing

ros-metapackages 1.8 is marked for autoremoval from testing on 2018-03-09 It (build-)depends on packages with these RC bugs: 887931: gazebo: gazebo FTBFS with libtinyxml2-dev 6.0.0+dfsg-1 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

lua-torch-torch7 0~20170926-g89ede3b-2 MIGRATED to testing

FYI: The status of the lua-torch-torch7 source package in Debian's testing distribution has changed. Previous version: 0~20170926-g89ede3b-1 Current version: 0~20170926-g89ede3b-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens

nlopt 2.4.2+dfsg-4 MIGRATED to testing

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

gazebo is marked for autoremoval from testing

gazebo 7.8.1+dfsg-4 is marked for autoremoval from testing on 2018-03-09 It is affected by these RC bugs: 887931: gazebo: gazebo FTBFS with libtinyxml2-dev 6.0.0+dfsg-1 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

lua-torch-xlua 0~20160719-g41308fe-6 MIGRATED to testing

FYI: The status of the lua-torch-xlua source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0~20160719-g41308fe-6 -- This email is automatically generated once a day. As the installation of new packages into testing happens

libdogleg 0.14-1 MIGRATED to testing

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

Proposal

Hello Greetings to you i need your collaboration to invest in your region i have some funds under my management please get back to me asap thanks Regards Melisa Mehmet -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

ignition-fuel-tools_1.0.0+dfsg4-2_amd64.changes is NEW

binary:libignition-fuel-tools1-1 is NEW. binary:libignition-fuel-tools1-dev is NEW. binary:libignition-fuel-tools1-dev is NEW. binary:libignition-fuel-tools1-1 is NEW. source:ignition-fuel-tools is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to

Processing of ignition-fuel-tools_1.0.0+dfsg4-2_amd64.changes

ignition-fuel-tools_1.0.0+dfsg4-2_amd64.changes uploaded successfully to localhost along with the files: ignition-fuel-tools_1.0.0+dfsg4-2.dsc ignition-fuel-tools_1.0.0+dfsg4.orig.tar.gz ignition-fuel-tools_1.0.0+dfsg4-2.debian.tar.xz ignition-fuel-tools_1.0.0+dfsg4-2_amd64.buildinfo

Proposal

Hello Greetings to you i need your collaboration to invest in your region i have some funds under my management please get back to me asap thanks Regards Melisa Mehmet -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

ignition-fuel-tools_1.0.0+dfsg4-2_amd64.changes REJECTED

ignition-fuel-tools_1.0.0+dfsg4-2.dsc: Refers to non-existing file 'ignition-fuel-tools_1.0.0+dfsg4.orig.tar.gz' Perhaps you need to include the file in your upload? === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new

Processing of ignition-fuel-tools_1.0.0+dfsg4-2_amd64.changes

ignition-fuel-tools_1.0.0+dfsg4-2_amd64.changes uploaded successfully to localhost along with the files: ignition-fuel-tools_1.0.0+dfsg4-2.dsc ignition-fuel-tools_1.0.0+dfsg4-2.debian.tar.xz ignition-fuel-tools_1.0.0+dfsg4-2_amd64.buildinfo

Bug#887454: Re-uploaded console-bridge

* Andreas Tille [2018-02-17 22:30]: A not uploaded state has the target distribution "UNRELEASED". Once it is uploaded this is set to "unstable" and the commit log says something like: "Uploaded to unstable (or new)" I think that's pretty obvious vor everybody even

code-saturne_5.1.3+repack-1_source.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Feb 2018 23:12:49 +0100 Source: code-saturne Binary: code-saturne code-saturne-bin code-saturne-data code-saturne-include code-saturne-doc Architecture: source Version: 5.1.3+repack-1 Distribution:

Accepted code-saturne 5.1.3+repack-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Feb 2018 23:12:49 +0100 Source: code-saturne Binary: code-saturne code-saturne-bin code-saturne-data code-saturne-include code-saturne-doc Architecture: source Version: 5.1.3+repack-1 Distribution: experimental Urgency:

Processing of code-saturne_5.1.3+repack-1_source.changes

code-saturne_5.1.3+repack-1_source.changes uploaded successfully to localhost along with the files: code-saturne_5.1.3+repack-1.dsc code-saturne_5.1.3+repack.orig.tar.gz code-saturne_5.1.3+repack-1.debian.tar.xz code-saturne_5.1.3+repack-1_source.buildinfo Greetings, Your Debian

Bug#887918: marked as done (tkgate uses deprecated Tcl/Tk 8.5)

Your message dated Sat, 17 Feb 2018 21:49:36 + with message-id and subject line Bug#887918: fixed in tkgate 2.0~b10-6 has caused the Debian Bug report #887918, regarding tkgate uses deprecated Tcl/Tk 8.5 to be marked as done. This means that you claim

Bug#890577: marked as done (tkgate: please make the build reproducible)

Your message dated Sat, 17 Feb 2018 21:49:36 + with message-id and subject line Bug#890577: fixed in tkgate 2.0~b10-6 has caused the Debian Bug report #890577, regarding tkgate: please make the build reproducible to be marked as done. This means that you

Accepted tkgate 2.0~b10-6 (source all amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 17 Feb 2018 18:25:41 +0100 Source: tkgate Binary: tkgate tkgate-data tkgate-doc Architecture: source all amd64 Version: 2.0~b10-6 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

tkgate_2.0~b10-6_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 17 Feb 2018 18:25:41 +0100 Source: tkgate Binary: tkgate tkgate-data tkgate-doc Architecture: source all amd64 Version: 2.0~b10-6 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

r-cran-mclust_5.4-1~bpo9+1_amd64.changes is NEW

binary:r-cran-mclust is NEW. binary:r-cran-mclust is NEW. source:r-cran-mclust 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

Processing of tkgate_2.0~b10-6_amd64.changes

tkgate_2.0~b10-6_amd64.changes uploaded successfully to localhost along with the files: tkgate_2.0~b10-6.dsc tkgate_2.0~b10-6.debian.tar.xz tkgate-data_2.0~b10-6_all.deb tkgate-dbgsym_2.0~b10-6_amd64.deb tkgate-doc_2.0~b10-6_all.deb tkgate_2.0~b10-6_amd64.buildinfo

Bug#887454: Re-uploaded console-bridge

On Sat, Feb 17, 2018 at 07:18:11PM +0100, Jochen Sprickerhof wrote: > * Andreas Tille [2018-02-17 19:13]: > > I tend to disagree. A package that's rejected by ftpmaster will not > > reach the archive. I'm tagging only those commits that have an > > equivalent package inside

Processing of r-cran-mclust_5.4-1~bpo9+1_amd64.changes

r-cran-mclust_5.4-1~bpo9+1_amd64.changes uploaded successfully to localhost along with the files: r-cran-mclust_5.4-1~bpo9+1.dsc r-cran-mclust_5.4-1~bpo9+1.debian.tar.xz r-cran-mclust-dbgsym_5.4-1~bpo9+1_amd64.deb r-cran-mclust_5.4-1~bpo9+1_amd64.buildinfo

Bug#887454: Re-uploaded console-bridge

Hi Jochen, On Sat, Feb 17, 2018 at 06:12:09PM +0100, Jochen Sprickerhof wrote: > > * Andreas Tille [2018-02-17 13:48]: > > I've re-uploaded console-bridge_0.4.0+dfsg-1 to new. > > I did so as well yesterday, that's why your upload was rejected. That's fine. > > Please note:

Bug#887454: Re-uploaded console-bridge

* Andreas Tille [2018-02-17 19:13]: I tend to disagree. A package that's rejected by ftpmaster will not reach the archive. I'm tagging only those commits that have an equivalent package inside the package pool. But how would you know which state you uploaded to ftp-master?

Bug#887454: Re-uploaded console-bridge

Hi Andreas, * Andreas Tille [2018-02-17 13:48]: I've re-uploaded console-bridge_0.4.0+dfsg-1 to new. I did so as well yesterday, that's why your upload was rejected. (I wasn't aware of the bug, so sorry for not commenting about it.) Please note: I have removed the

z88_13.0.0+dfsg2-5_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Feb 2018 15:15:01 +0100 Source: z88 Binary: z88 z88-doc z88-data Architecture: source Version: 13.0.0+dfsg2-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processing of z88_13.0.0+dfsg2-5_source.changes

z88_13.0.0+dfsg2-5_source.changes uploaded successfully to localhost along with the files: z88_13.0.0+dfsg2-5.dsc z88_13.0.0+dfsg2-5.debian.tar.xz z88_13.0.0+dfsg2-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Accepted mseed2sac 2.2+ds1-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Feb 2018 20:13:09 +0100 Source: mseed2sac Binary: mseed2sac Architecture: source Version: 2.2+ds1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processing of sac2mseed_1.12+ds1-3_source.changes

sac2mseed_1.12+ds1-3_source.changes uploaded successfully to localhost along with the files: sac2mseed_1.12+ds1-3.dsc sac2mseed_1.12+ds1-3.debian.tar.xz sac2mseed_1.12+ds1-3_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Accepted sac2mseed 1.12+ds1-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Feb 2018 14:30:15 +0100 Source: sac2mseed Binary: sac2mseed Architecture: source Version: 1.12+ds1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

sac2mseed_1.12+ds1-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Feb 2018 14:30:15 +0100 Source: sac2mseed Binary: sac2mseed Architecture: source Version: 1.12+ds1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

mseed2sac_2.2+ds1-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Feb 2018 20:13:09 +0100 Source: mseed2sac Binary: mseed2sac Architecture: source Version: 2.2+ds1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processing of mseed2sac_2.2+ds1-3_source.changes

mseed2sac_2.2+ds1-3_source.changes uploaded successfully to localhost along with the files: mseed2sac_2.2+ds1-3.dsc mseed2sac_2.2+ds1-3.debian.tar.xz mseed2sac_2.2+ds1-3_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --

ignition-fuel-tools_1.0.0+dfsg4-1_amd64.changes is NEW

binary:libignition-fuel-tools is NEW. binary:libignition-fuel-tools-dev is NEW. binary:libignition-fuel-tools is NEW. binary:libignition-fuel-tools-dev is NEW. source:ignition-fuel-tools is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to

Processing of ignition-fuel-tools_1.0.0+dfsg4-1_amd64.changes

ignition-fuel-tools_1.0.0+dfsg4-1_amd64.changes uploaded successfully to localhost along with the files: ignition-fuel-tools_1.0.0+dfsg4-1.dsc ignition-fuel-tools_1.0.0+dfsg4.orig.tar.xz ignition-fuel-tools_1.0.0+dfsg4-1.debian.tar.xz ignition-fuel-tools_1.0.0+dfsg4-1_amd64.buildinfo

console-bridge_0.4.0+dfsg-1_amd64.changes REJECTED

console-bridge_0.4.0+dfsg-1.dsc: Does not match file already existing in the pool. binary:libconsole-bridge0.4 is NEW. binary:libconsole-bridge0.4 is NEW. === 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

Processing of console-bridge_0.4.0+dfsg-1_amd64.changes

console-bridge_0.4.0+dfsg-1_amd64.changes uploaded successfully to localhost along with the files: console-bridge_0.4.0+dfsg-1.dsc console-bridge_0.4.0+dfsg.orig.tar.xz console-bridge_0.4.0+dfsg-1.debian.tar.xz console-bridge_0.4.0+dfsg-1_amd64.buildinfo

Bug#887454: Re-uploaded console-bridge

Hi Jose, I've re-uploaded console-bridge_0.4.0+dfsg-1 to new. Please note: I have removed the changelog entry console-bridge (0.4.0-1) unstable; urgency=medium * New upstream version 0.4.0 -- Jose Luis Rivero Mon, 15 Jan 2018 18:21:19 + since this

Bug#890657: not usable with qt 5.7.1

Package: libqcustomplot-dev Version: 1.3.2+dfsg1-1 Severity: important libqcustomplot-dev is not usable in Stretch with qt 5.7.1 since when trying to compile and link an application with this package it gives the following error: /usr/include/qcustomplot.h:54:28: fatal error: QtPrintSupport:

Processed: Forwarded bug

Processing commands for cont...@bugs.debian.org: > forwarded 890088 https://salsa.debian.org/science-team/nlopt/merge_requests/1 Bug #890088 {Done: Sébastien Villemot } [src:nlopt] nlopt: Build-depend on dh-octave instead of octave-pkg-dev Set Bug forwarded-to-address to

pyfai_0.15.0+dfsg1-1~bpo9+1_source.changes ACCEPTED into stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Feb 2018 08:39:15 +0100 Source: pyfai Binary: pyfai python-pyfai python-pyfai-dbg python3-pyfai python3-pyfai-dbg python-pyfai-doc Architecture: source Version: 0.15.0+dfsg1-1~bpo9+1 Distribution:

Accepted pyfai 0.15.0+dfsg1-1~bpo9+1 (source) into stretch-backports

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Feb 2018 08:39:15 +0100 Source: pyfai Binary: pyfai python-pyfai python-pyfai-dbg python3-pyfai python3-pyfai-dbg python-pyfai-doc Architecture: source Version: 0.15.0+dfsg1-1~bpo9+1 Distribution: stretch-backports

console-bridge_0.4.0+dfsg-1_amd64.changes is NEW

binary:libconsole-bridge0.4 is NEW. binary:libconsole-bridge0.4 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.

Processing of console-bridge_0.4.0+dfsg-1_amd64.changes

console-bridge_0.4.0+dfsg-1_amd64.changes uploaded successfully to localhost along with the files: console-bridge_0.4.0+dfsg-1.dsc console-bridge_0.4.0+dfsg.orig.tar.gz console-bridge_0.4.0+dfsg-1.debian.tar.xz console-bridge_0.4.0+dfsg-1_amd64.buildinfo

Processing of pyfai_0.15.0+dfsg1-1~bpo9+1_source.changes

pyfai_0.15.0+dfsg1-1~bpo9+1_source.changes uploaded successfully to localhost along with the files: pyfai_0.15.0+dfsg1-1~bpo9+1.dsc pyfai_0.15.0+dfsg1-1~bpo9+1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing