caffe is marked for autoremoval from testing

caffe 1.0.0~rc3+20161127-g24d2f67-4 is marked for autoremoval from testing on 2017-02-03 It (build-)depends on packages with these RC bugs: 841610: statsmodels: FTBFS: TypeError: cannot sort an Index object in-place, use sort_values instead 848771: numexpr: FTBFS: Test failures --

caffe-contrib is marked for autoremoval from testing

caffe-contrib 1.0.0~rc3+20161127-g24d2f67-3 is marked for autoremoval from testing on 2017-02-03 It (build-)depends on packages with these RC bugs: 835940: nvidia-cuda-toolkit: non-standard gcc/g++ used for build (gcc-5) 841610: statsmodels: FTBFS: TypeError: cannot sort an Index object

gap-design_1r6+ds-1_source.changes REJECTED

Source-only uploads to NEW are not allowed. binary:gap-design is NEW. source:gap-design 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 address our concerns. -- debian-science-maintainers mailing

Processing of gap-design_1r6+ds-1_source.changes

gap-design_1r6+ds-1_source.changes uploaded successfully to localhost along with the files: gap-design_1r6+ds-1.dsc gap-design_1r6+ds.orig.tar.xz gap-design_1r6+ds-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers

gap-scscp_2.1.4+ds-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 31 Dec 2016 16:12:58 + Source: gap-scscp Binary: gap-scscp Architecture: source Version: 2.1.4+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processing of gap-scscp_2.1.4+ds-3_source.changes

gap-scscp_2.1.4+ds-3_source.changes uploaded successfully to localhost along with the files: gap-scscp_2.1.4+ds-3.dsc gap-scscp_2.1.4+ds-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list

Processed: Re: Bug#848137: problem with the upgrade of tango-db

Processing control commands: > clone -1 -2 Bug #848137 [tango-db] tango-db: fails to upgrade from 'jessie': mysqldump: tango has insufficent privileges to SHOW CREATE PROCEDURE `class_att_prop`! Bug 848137 cloned as bug 850190 > reassign -2 dbconfig-common Bug #850190 [tango-db] tango-db: fails

Bug#848137: problem with the upgrade of tango-db

Control: clone -1 -2 Control: reassign -2 dbconfig-common Control: retitle -2 dbc: db-dump must use root credentials when needed Hi all, I think I found the issue. Since commit 95571e6¹ the postinst script of dbconfig properly executes install code with user privileges as it has always said it

Bug#848137: problem with the upgrade of tango-db

Hi Frederic-Emmanuel, Andreas, @Andreas, am I correct in the assumption that jessie to stretch with tango-db was fine until MariaDB became the default? Or was this migration with tango-db just never tested before? Have you seen other dbconfig-common dependent packages fail since MariaDB became

Bug#848859: FTBFS randomly (failing tests)

On Wed, Jan 04, 2017 at 07:58:43PM +0100, Anton Gladky wrote: > 2017-01-04 13:26 GMT+01:00 Santiago Vila : > > No matter how much glitch-free is the autobuilder you use to build the > > above package, it will fail to build 1 every 147 times on average, > > mathematically, because

Bug#848859: FTBFS randomly (failing tests)

Le 04/01/2017 à 19:58, Anton Gladky a écrit : > 2017-01-04 13:26 GMT+01:00 Santiago Vila : >> No matter how much glitch-free is the autobuilder you use to build the >> above package, it will fail to build 1 every 147 times on average, >> mathematically, because the test is wrongly

Bug#844134: Request for help - scilab segfaults with TSX

On 2017-01-04 19:51, Samuel Thibault wrote: Hello, Gilles Filippini, on Wed 04 Jan 2017 19:31:28 +0100, wrote: On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote: > This looks like a threading bug in Scilab exposed by TSX. I've just noticed this RC bug [1] against scilab.

Processed: Re: Request for help - scilab segfaults with TSX

Processing control commands: > severity 844134 normal Bug #844134 [scilab] scilab segfaults with TSX Bug #844135 [scilab] scilab segfaults with TSX Bug #844138 [scilab] scilab segfaults with TSX Severity set to 'normal' from 'serious' Severity set to 'normal' from 'serious' Severity set to

Bug#844134: Request for help - scilab segfaults with TSX

Control: severity 844134 normal Samuel Thibault writes ("Re: Request for help - scilab segfaults with TSX"): > Gilles Filippini, on Wed 04 Jan 2017 19:31:28 +0100, wrote: > > On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote: > > > This looks like a threading bug in Scilab

Bug#848859: FTBFS randomly (failing tests)

2017-01-04 13:26 GMT+01:00 Santiago Vila : > No matter how much glitch-free is the autobuilder you use to build the > above package, it will fail to build 1 every 147 times on average, > mathematically, because the test is wrongly designed. That is not always true. If you look in

Bug#844134: Request for help - scilab segfaults with TSX

Hello, Gilles Filippini, on Wed 04 Jan 2017 19:31:28 +0100, wrote: > On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote: > > This looks like a threading bug in Scilab exposed by TSX. > > I've just noticed this RC bug [1] against scilab. FYI, glibc is about to just disable TSX

Processed: Request for help - scilab segfaults with TSX

Processing control commands: > tag -1 + help Bug #844134 [scilab] scilab segfaults with TSX Bug #844135 [scilab] scilab segfaults with TSX Bug #844138 [scilab] scilab segfaults with TSX Added tag(s) help. Added tag(s) help. Added tag(s) help. -- 844134:

Bug#844134: Request for help - scilab segfaults with TSX

Control: tag -1 + help Hi, On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote: > This looks like a threading bug in Scilab exposed by TSX. I've just noticed this RC bug [1] against scilab. After reading through the recent thread on this subject [2] I must admit I have no clue

Bug#848137: [Dbconfig-common-devel] Bug#848137: RE:Bug#848137: Info received (problem with the upgrade of tango-db)

Hello, > I am suspecting that this commit may be related to the current behavior: > https://anonscm.debian.org/cgit/collab-maint/dbconfig-common.git/commit/?id=acdb99d61abfff54630c4cfba6e4452357a83fb9 > I believe I implemented there that the drop of the database is performed > with the user

skimage 0.12.3-7 MIGRATED to testing

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

caffe-contrib 1.0.0~rc3+20161127-g24d2f67-3 MIGRATED to testing

FYI: The status of the caffe-contrib source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.0.0~rc3+20161127-g24d2f67-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens

Bug#841089: wrong file type recognized for J2K and WEBP images (and most likely SGI, EXR, JP2, PFM, PICT, RAW, JXR)

Hi, I am not a FreeImage dev at all, just a user who encountered a bug and tried to fix it. Maybe my patch wasn't the best way to solve this issue, it passed a very basic unit test but was merely a suggestion. The real problem here is that a previous debian patch in FreeImage, disabled the

Bug#848859: FTBFS randomly (failing tests)

On Wed, Jan 04, 2017 at 08:44:17AM +0100, Ole Streicher wrote: > > It's in Release Policy: Packages *must* autobuild *without* failure. > > > > If a package fails to build from time to time, that's a failure. > > Packages actually *do* fail from time to time, when I look into my > autobuilder.

Bug#850150: freemat ftbfs with LLVM 3.9

Package: src:freemat Version: Severity: important Tags: sid stretch [100%] Linking CXX executable FreeMat cd /home/packages/tmp/freemat-4.2+dfsg1/debian/build/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/FreeMat.dir/link.txt --verbose=1 /usr/bin/x86_64-linux-gnu-g++ -g -O2

Processed: Oops...

Processing commands for cont...@bugs.debian.org: > reopen 848771 Bug #848771 {Done: Ole Streicher } [src:numexpr] numexpr: FTBFS: Test failures 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to