Bug#905761: marked as done (backuppc: FTBFS with merged /usr)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Thu, 18 Oct 2018 06:34:10 +
with message-id 
and subject line Bug#905761: fixed in backuppc 3.3.1-6
has caused the Debian Bug report #905761,
regarding backuppc: FTBFS with merged /usr
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
905761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: backuppc
Version: 3.3.1-5
Severity: serious

Hi,

backuppc fails to build with merged /usr in a sbuild chroot, created with 
current debootstrap. Debootstrap enabled merged /usr since version 1.0.85, see 
https://bugs.debian.org/839046

The build fails when a patch is applied to the generated config.pl file. Since 
the path to cat is now /usr/bin/cat instead of /bin/cat, the patch fails to 
apply.

Here's the failing part of the patch:
-
@@ -224,7 +227,7 @@
 # Full path to various commands for archiving
 #
 $Conf{SplitPath} = '/usr/bin/split';
-$Conf{ParPath}   = '/usr/bin/par2';
+$Conf{ParPath}   = '/usr/bin/par2' if -x '/usr/bin/par2';
 $Conf{CatPath}   = '/bin/cat';
 $Conf{GzipPath}  = '/bin/gzip';
 $Conf{Bzip2Path} = '/bin/bzip2';
-

And here's the failing part of the build log:
--
install --mode=644 debian/apache.conf debian/backuppc/etc/backuppc
rmdir debian/backuppc/var/lib/backuppc/conf/
rmdir: failed to remove 'debian/backuppc/var/lib/backuppc/conf/': No such file o
r directory
make: [debian/rules:67: install] Error 1 (ignored)
(cd debian/backuppc/usr/share/backuppc/cgi-bin; ln -s ../image; ln -s /usr/lib/b
ackuppc/cgi-bin/index.cgi )
patch --no-backup-if-mismatch -p0 < debian/config.pl.diff
patching file debian/backuppc/etc/backuppc/config.pl
Hunk #2 FAILED at 227.
Hunk #4 succeeded at 1021 (offset -3 lines).
1 out of 7 hunks FAILED -- saving rejects to file debian/backuppc/etc/backuppc/c
onfig.pl.rej
make: *** [debian/rules:69: install] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit
status 2
-

Full build log attached.

Apparently, the official builds' chroots didn't use merged /usr when the 
package was last built (February 2018), but at some point some of them will, 
leading to inability to build backuppc on official infrastructure.

IMO, adapting the patch to the merged /usr would not work, since then the patch 
will fail on systems without merged /usr.


-- dam
sbuild (Debian sbuild) 0.77.0 (06 July 2018) on pc1.creditreform.bg

+==+
| backuppc 3.3.1-5 (amd64) Wed, 08 Aug 2018 14:22:31 + |
+==+

Package: backuppc
Version: 3.3.1-5
Source Version: 3.3.1-5
Distribution: sid
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/sid+exp-perl-amd64-b67b90b7-ae44-4d20-b602-62f9cb7b4d9a' 
with '<>'
I: NOTICE: Log filtering will replace 'build/backuppc-t497R0/resolver-4nL5LG' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://proxy:/debian sid InRelease [233 kB]
Get:2 http://proxy:/debian experimental InRelease [101 kB]
Get:3 http://perl.debian.net/test-repo perl-5.28 InRelease [2871 B]
Get:4 http://proxy:/debian sid/main amd64 Packages.diff/Index [27.9 kB]
Get:5 http://proxy:/debian sid/main amd64 Packages 2018-08-04-0814.44.pdiff 
[20.5 kB]
Get:6 http://proxy:/debian sid/main amd64 Packages 2018-08-04-1411.17.pdiff 
[9739 B]
Get:7 http://proxy:/debian sid/main amd64 Packages 2018-08-04-2013.33.pdiff 
[17.8 kB]
Get:8 http://proxy:/debian sid/main amd64 Packages 2018-08-05-0209.24.pdiff 
[15.5 kB]
Get:9 http://proxy:/debian sid/main amd64 Packages 2018-08-05-0806.31.pdiff 
[2966 B]
Get:10 http://proxy:/debian sid/main amd64 Packages 
2018-08-05-1409.33.pdiff [18.0 kB]
Get:11 http://proxy:/debian sid/main amd64 Packages 
2018-08-05-2014.01.pdiff [9558 B]
Get:12 http://proxy:/debian sid/main amd64 Packages 
2018-08-06-0208.11.pdiff [4773 B]
Get:13 http://proxy:/debian sid/main amd64 Packages 
2018-08-06-0809.42.pdiff [5408 B]
Get:14 http://proxy:/debian si

Processed: Re: bless: Don't depend on rarian

2018-10-17 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #885114 [src:bless] bless: Don't depend on rarian
Severity set to 'serious' from 'important'
> tags -1 +patch
Bug #885114 [src:bless] bless: Don't depend on rarian
Added tag(s) patch.

-- 
885114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#907298: CVE-2018-15869

2018-10-17 Thread Shengjing Zhu
Package: awscli
Followup-For: Bug #907298

The corresponding bug on Redhat is closed as

> Closing this bug as NOTABUG and asked MITRE for rejection, since the issue
> does not seem to be in AWS CLI but in Packer.

Can we downgrade this bug and keep awscli in buster?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1623095

-- 
Shengjing Zhu


signature.asc
Description: PGP signature


Bug#911278: php7cc: PHP Fatal error: Uncaught Error: Cannot instantiate interface PhpParser\Parser

2018-10-17 Thread Paul Wise
Package: php7cc
Version: 1.2.1-1
Severity: serious

php7cc doesn't appear to work at all. I tried with a empty directory
and with an empty file as well as with some old PHP code and all three
invocations produced the same set of errors:

$ php7cc .
PHP Fatal error:  Uncaught Error: Cannot instantiate interface PhpParser\Parser 
in /usr/share/php/Sstalle/php7cc/Infrastructure/ContainerBuilder.php:165
Stack trace:
#0 /usr/share/php/Pimple/Container.php(113): 
Sstalle\php7cc\Infrastructure\ContainerBuilder->Sstalle\php7cc\Infrastructure\{closure}(Object(Pimple\Container))
#1 /usr/share/php/Sstalle/php7cc/Infrastructure/ContainerBuilder.php(195): 
Pimple\Container->offsetGet('parser')
#2 /usr/share/php/Pimple/Container.php(113): 
Sstalle\php7cc\Infrastructure\ContainerBuilder->Sstalle\php7cc\Infrastructure\{closure}(Object(Pimple\Container))
#3 /usr/share/php/Sstalle/php7cc/Infrastructure/ContainerBuilder.php(220): 
Pimple\Container->offsetGet('contextChecker')
#4 /usr/share/php/Pimple/Container.php(113): 
Sstalle\php7cc\Infrastructure\ContainerBuilder->Sstalle\php7cc\Infrastructure\{closure}(Object(Pimple\Container))
#5 /usr/share/php/Sstalle/php7cc/Infrastructure/ContainerBuilder.php(229): 
Pimple\Container->offsetGet('pathChecker')
#6 /usr/share/php/Pimple/Container.php(113): Ss in 
/usr/share/php/Sstalle/php7cc/Infrastructure/ContainerBuilder.php on line 165

$ touch foo.php
$ php7cc foo.php 
PHP Fatal error:  Uncaught Error: Cannot instantiate interface PhpParser\Parser 
in /usr/share/php/Sstalle/php7cc/Infrastructure/ContainerBuilder.php:165
Stack trace:
#0 /usr/share/php/Pimple/Container.php(113): 
Sstalle\php7cc\Infrastructure\ContainerBuilder->Sstalle\php7cc\Infrastructure\{closure}(Object(Pimple\Container))
#1 /usr/share/php/Sstalle/php7cc/Infrastructure/ContainerBuilder.php(195): 
Pimple\Container->offsetGet('parser')
#2 /usr/share/php/Pimple/Container.php(113): 
Sstalle\php7cc\Infrastructure\ContainerBuilder->Sstalle\php7cc\Infrastructure\{closure}(Object(Pimple\Container))
#3 /usr/share/php/Sstalle/php7cc/Infrastructure/ContainerBuilder.php(220): 
Pimple\Container->offsetGet('contextChecker')
#4 /usr/share/php/Pimple/Container.php(113): 
Sstalle\php7cc\Infrastructure\ContainerBuilder->Sstalle\php7cc\Infrastructure\{closure}(Object(Pimple\Container))
#5 /usr/share/php/Sstalle/php7cc/Infrastructure/ContainerBuilder.php(229): 
Pimple\Container->offsetGet('pathChecker')
#6 /usr/share/php/Pimple/Container.php(113): Ss in 
/usr/share/php/Sstalle/php7cc/Infrastructure/ContainerBuilder.php on line 165

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), 
LANGUAGE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php7cc depends on:
ii  php-cli   1:7.2+62
ii  php-common1:62
ii  php-parser3.1.5-1
ii  php-pimple3.0.2-2
ii  php-symfony-console   3.4.17+dfsg-1
ii  php-symfony-finder3.4.17+dfsg-1
ii  php7.2-cli [php-cli]  7.2.9-1

php7cc recommends no packages.

php7cc suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



signature.asc
Description: This is a digitally signed message part


Bug#870267: graphicsmagick frequently FTBFS on ppc64el: test hang

2018-10-17 Thread Aee Freedom
On Tue, 22 Aug 2017 17:13:17 +0300 Adrian Bunk  wrote:
> Control: severity -1 serious
>
> On Thu, Aug 10, 2017 at 01:02:54PM +0200, László Böszörményi wrote:
> >...
> >  OK, GCC 7.1.0 arrived to ppc64el and GraphicsMagick no longer FTBFS
> > even on ppc64el-unicamp-01. I don't close this bugreport but lower the
> > severity to let the security fixes finally migrate to Buster
> > (testing). I'll see how future builds do on ppc64el and will act
> > accordingly.
>
> Happened again with 1.3.26-6:
> https://buildd.debian.org/status/fetch.php?pkg=graphicsmagick&arch=ppc64el&ver=1.3.26-6&stamp=1503263346&raw=0
>
> > Regards,
> > Laszlo/GCS
>
> cu
> Adrian
>
> BTW: The mips64el build failure looks unrelated, likely caused by #871514.
>
> --
>
>"Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
>"Only a promise," Lao Er said.
>Pearl S. Buck - Dragon Seed
>
>
>




ส่งจากสมาร์ทโฟน Samsung Galaxy ของฉัน


Bug#870267: graphicsmagick frequently FTBFS on ppc64el: test hang

2018-10-17 Thread Aee Freedom
On Mon, 31 Jul 2017 15:31:20 +0300 Adrian Bunk  wrote:
> Source: graphicsmagick
> Version: 1.3.26-3
> Severity: serious
>
> 2 out of the 4 latest build attempts FTBFS on ppc64el:
>
> https://buildd.debian.org/status/logs.php?pkg=graphicsmagick&arch=ppc64el
> https://buildd.debian.org/status/fetch.php?pkg=graphicsmagick&arch=ppc64el&ver=1.3.26-4&stamp=150145&raw=0
>
> ...
> PASS: Magick++/tests/tests.tap 7 - colorHistogram
> PASS: Magick++/tests/tests.tap 8 - exceptions
> PASS: Magick++/tests/tests.tap 9 - montageImages
> PASS: Magick++/tests/tests.tap 10 - morphImages
> PASS: Magick++/tests/tests.tap 11 - readWriteBlob
> PASS: Magick++/tests/tests.tap 12 - readWriteImages
> E: Build killed with signal TERM after 150 minutes of inactivity
>
>
> The next test is "Magick++/demo/demos.tap 1 - analyze",
> this seems to be the hanging one?
>
>




ส่งจากสมาร์ทโฟน Samsung Galaxy ของฉัน


Bug#911276: elfutils: ftbfs on arm64 with gcc-8

2018-10-17 Thread Michael Hudson-Doyle
Source: elfutils
Version: 0.170-0.4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

elfutils ftbfs on sid on arm64 currently. Current git passes, and git
bisect and logic point to the following upstream commit as fixing it:

commit f881459ffc95b6fad51aa055a158ee14814073aa
Author: Mark Wielaard 
Date:   Wed Apr 11 10:37:45 2018 +0200

aarch64: Add default cfi rule to restore SP from CFA address.

The CFA is set by default to the stack pointer of the previous frame.
So that is also how we can always restore the SP. This default aarch64
CFI rule is necessary on Fedora 28 with GCC8 to make the run-deleted.sh
and run-backtrace-dwarf.sh testcases work.

Signed-off-by: Mark Wielaard 

so this bug can be closed either with an upstream update (this patch is
in 0.171) or a cherry pick of the above commit.

Cheers,
mwh

-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 
'bionic'), (400, 'bionic-proposed'), (100, 'bionic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-36-generic (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Bug#911271: [Pkg-privacy-maintainers] Bug#911271: foolscap: (Build) Depends on non existing python-txtorcon

2018-10-17 Thread Antoine Beaupré
On 2018-10-18 00:16:15, Sebastian Andrzej Siewior wrote:
> Package: foolscap
> Version: 0.13.1-1
> Severity: serious
>
> txtorcon does not build the Python2 variant (python-txtorcon) since its
> last upload, only the python3 one (python3-txtorcon) remains.
>
> As of now the package can't be built due to missing packages.

Seems to me foolscap should be ported to python rather than to force
txtorcon to support a (soon to be) obsolete version of python. :)

A.

-- 
Si Dieu est, l'homme est esclave ; 
or l'homme peut, doit être libre, donc Dieu n'existe pas.
Et si Dieu existait, il faudrait s'en débarrasser!
- Michel Bakounine



Bug#907015: openssl version 1.1.1 breaks multiple reverse dependencies; versioned Breaks needed

2018-10-17 Thread Sebastian Andrzej Siewior
On 2018-10-17 21:21:29 [+0200], Kurt Roeckx wrote:
> > - src:foolscap #898800: foolscap: FTBFS against openssl 1.1.1
> 
> I'm not sure if this is actually still a problem, there have been
> fixes on the python and openssl side for this. reproducible builds
> shows it as having problems trying to install the build
> dependencies for months.

added #911271 to the pile. Not sure if foolscape is usable in testing
due to #905253 (it depends on python-txtorcon).

> > - src:python-boto #909545: SSL CERTIFICATE_VERIFY_FAILED when using gs 
> > (Google Cloud Storage) backend
> 
> Patch is available.

does it make sense to NMU it?

> Kurt

Sebastian



Bug#911271: foolscap: (Build) Depends on non existing python-txtorcon

2018-10-17 Thread Sebastian Andrzej Siewior
Package: foolscap
Version: 0.13.1-1
Severity: serious

txtorcon does not build the Python2 variant (python-txtorcon) since its
last upload, only the python3 one (python3-txtorcon) remains.

As of now the package can't be built due to missing packages.

Sebastian



Bug#910443: marked as done (gir-to-d FTBFS: Error: Expected argument to '-I')

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 22:10:52 +
with message-id 
and subject line Bug#910443: fixed in meson 0.48.1-1
has caused the Debian Bug report #910443,
regarding gir-to-d FTBFS: Error: Expected argument to '-I'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
910443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gir-to-d
Version: 0.16.1-1
Severity: serious
Tags: ftbfs

gir-to-d fails to build from source in sbuild on unstable/amd64. A build
log ends with:

| dh build --buildsystem=meson
|dh_update_autotools_config -O--buildsystem=meson
|dh_autoreconf -O--buildsystem=meson
|dh_auto_configure -O--buildsystem=meson
| cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu 
--libexecdir=lib/x86_64-linux-gnu
| The Meson build system
| Version: 0.48.0
| Source dir: /<>
| Build dir: /<>/obj-x86_64-linux-gnu
| Build type: native build
| Project name: GIR-to-D
| Project version: 0.16.0
| Appending DFLAGS from environment: '-O -g -release -wi'
| Appending LDFLAGS from environment: '-Wl,-z,relro'
| Native D compiler: ldc2 (llvm 1.11.0 "LDC - the LLVM D compiler (1.11.0):")
| Build machine cpu family: x86_64
| Build machine cpu: x86_64
| Build targets in project: 2
| Found ninja-1.8.2 at /usr/bin/ninja
|dh_auto_build -O--buildsystem=meson
| cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v
| [1/20] /usr/bin/meson --internal vcstagger ../VERSION.in VERSION 0.16.0 
/<> @VCS_TAG@ '(.*)' /<>/git describe --dirty=+ --tags
| [2/20] ldc2 -I=girtod@exe -I=. -I=.. -I=../source/ -I= -enable-color 
-J/<>/obj-x86_64-linux-gnu -O -g -release -wi   
-of='girtod@exe/source_girtod.d.o' -c ../source/girtod.d
| FAILED: girtod@exe/source_girtod.d.o 
| ldc2 -I=girtod@exe -I=. -I=.. -I=../source/ -I= -enable-color 
-J/<>/obj-x86_64-linux-gnu -O -g -release -wi   
-of='girtod@exe/source_girtod.d.o' -c ../source/girtod.d
| Error: Expected argument to '-I'
| ninja: build stopped: subcommand failed.
| dh_auto_build: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v 
returned exit code 1
| make: *** [debian/rules:8: build] Error 1
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.48.1-1

We believe that the bug you reported is fixed in the latest version of
meson, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jussi Pakkanen  (supplier of updated meson package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 17 Oct 2018 18:57:16 +0300
Source: meson
Binary: meson
Architecture: source
Version: 0.48.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Jussi Pakkanen 
Description:
 meson  - high-productivity build system
Closes: 909851 910443
Changes:
 meson (0.48.1-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #909851, #910443.
Checksums-Sha1:
 1ceee6cb977cf8c38ccc84f8c2cfa75544a2c9ce 3350 meson_0.48.1-1.dsc
 eb5792ef897b93330c3504e99ce62a336742ac1f 1310184 meson_0.48.1.orig.tar.gz
 5f6224bf04effdd257f2078faf35960b1187a78a 11860 meson_0.48.1-1.debian.tar.xz
 78e9800f598fa4d477b6fce35f328f07c3a977ca 33133 meson_0.48.1-1_source.buildinfo
Checksums-Sha256:
 2a33513aa86e88bb1d207dbf74acba8172048efcbb3bd61be8068ba904f1b183 3350 
meson_0.48.1-1.dsc
 425d12edbb81498314926afa93a3eb2fca4ca6929cbe0f8abeb6ab45d1d9fa8f 1310184 
meson_0.48.1.orig.tar.gz
 4fb377cfd715948e64fe20268157a91f4d84c48f42e5e2756b24b8bf1dff5fdf 11860 
meson_0.48.1-1.debian.tar.xz
 13184a33fe511380fc485d0b884821b5838845cdb8708839b6828fc1dc0efe43 33133 
meson_0.48.1-1_source.buildinfo
Files:
 489b5c95e6266a50258bc14288453cd1 3350 devel optional meson_0.48.1-1.dsc
 d424e2ae88036326cc6c8e3b01e65daf 1310184 devel optional 
meson_0.48.1.orig.tar.gz
 2f7d8360c56fd503618a1a3fbaa40648 11860 devel optional 
meson_0.48.1-1.debian.ta

Bug#909851: marked as done (meson fails: AttributeError: 'list' object has no attribute 'absolute_path')

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 22:10:52 +
with message-id 
and subject line Bug#909851: fixed in meson 0.48.1-1
has caused the Debian Bug report #909851,
regarding meson fails: AttributeError: 'list' object has no attribute 
'absolute_path'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
909851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: meson
Version: 0.48.0-1
Severity: serious
Control: affects -1 src:gnome-initial-setup src:file-roller

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-initial-setup.html

...
dh_auto_configure -- \
--libexecdir=/usr/lib/gnome-initial-setup \
-Ddisable-software-sources=true \
-Dwith-vendor-conf-file=/usr/lib/gnome-initial-setup/vendor.conf
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu 
--libexecdir=lib/x86_64-linux-gnu --libexecdir=/usr/lib/gnome-initial-setup 
-Ddisable-software-sources=true 
-Dwith-vendor-conf-file=/usr/lib/gnome-initial-setup/vendor.conf
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 364, in 
run
app.generate()
  File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 136, in 
generate
self._generate(env)
  File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 165, in 
_generate
intr.run()
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreter.py", line 3836, 
in run
super().run()
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
380, in run
self.evaluate_codeblock(self.ast, start=1)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
404, in evaluate_codeblock
raise e
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
398, in evaluate_codeblock
self.evaluate_statement(cur)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
409, in evaluate_statement
return self.function_call(cur)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
705, in function_call
return func(node, posargs, kwargs)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
273, in wrapped
return f(*wrapped_args, **wrapped_kwargs)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
162, in wrapped
return f(*wrapped_args, **wrapped_kwargs)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreter.py", line 3422, 
in func_subdir
self.evaluate_codeblock(codeblock)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
404, in evaluate_codeblock
raise e
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
398, in evaluate_codeblock
self.evaluate_statement(cur)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
413, in evaluate_statement
return self.method_call(cur)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
741, in method_call
return obj.method_call(method_name, args, kwargs)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreter.py", line 1622, 
in method_call
value = fn(state, args, kwargs)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
219, in wrapped
return f(*wrapped_args, **wrapped_kwargs)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 
162, in wrapped
return f(*wrapped_args, **wrapped_kwargs)
  File "/usr/lib/python3/dist-packages/mesonbuild/modules/i18n.py", line 89, in 
merge_file
ifile_abs = inputfile.absolute_path(state.environment.source_dir,
AttributeError: 'list' object has no attribute 'absolute_path'
The Meson build system
Version: 0.48.0
Source dir: /build/1st/gnome-initial-setup-3.30.0
Build dir: /build/1st/gnome-initial-setup-3.30.0/obj-x86_64-linux-gnu
Build type: native build
WARNING: Unknown options: "disable-software-sources, with-vendor-conf-file"
Project name: gnome-initial-setup
Project version: 3.29.92
Appending CFLAGS from environment: '-g -O2 
-fdebug-prefix-map=/build/1st/gnome-initial-setup-3.30.0=. 
-fstack-protector-strong -Wformat -Werror=format-security'
Appending LDFLAGS from environment: '-Wl,-z,relro -Wl,-z,now -Wl,-z,defs 
-Wl,--as-needed'
Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2'
Native C compiler: cc (gcc 8.2.0 "cc (Debian 8.

Bug#904709: marked as done (python-cobra ftbfs (test failures))

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 21:41:39 +
with message-id 
and subject line Bug#904709: fixed in python-cobra 0.13.4-1
has caused the Debian Bug report #904709,
regarding python-cobra ftbfs (test failures)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
904709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-cobra
Version: 0.5.9-1
Tags: sid buster

see
https://buildd.debian.org/status/package.php?p=python-cobra

apparently incompatible with recent numpy/scipy.
--- End Message ---
--- Begin Message ---
Source: python-cobra
Source-Version: 0.13.4-1

We believe that the bug you reported is fixed in the latest version of
python-cobra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-cobra package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Oct 2018 21:31:48 +0200
Source: python-cobra
Binary: python3-cobra python-cobra-data
Architecture: source
Version: 0.13.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-cobra-data - constraint-based modeling of biological networks (data)
 python3-cobra - constraint-based modeling of biological networks with Python 3
Closes: 904709
Changes:
 python-cobra (0.13.4-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Afif Elghraoui ]
   * New upstream version
 Closes: #904709
   * Update dependencies
   * Refresh patch
   * Drop obsolete patch
 .
   [ Andreas Tille ]
   * Standards-Version: 4.2.1
   * Point Vcs-fields to Salsa
   * debhelper 11
   * cme fix dpkg-control
   * Build-Depends: python*-requests, python*-pip
   * Drop failing test TestCobraFluxSampling.test_fixed_seed
   * Rename debian/tests/control to control.autodep8
   * Testsuite: autopkgtest-pkg-python
   * Drop Python2 package since it has no reverse dependencies
 (as well as autopkgtest of Python2 version)
   * Build-Depends: python3-depinfo, python3-pipdeptree
   * Drop failing test: test_show_versions (needs further investigation
 with upstream)
   * Silence lintian about wrong Python version of data file
Checksums-Sha1:
 224f4ae8c7e22ff1a209febfa412ebdfd7634e1c 2448 python-cobra_0.13.4-1.dsc
 15fc80a76b52e6ce2f1ef785ed80550b0efabf33 1742133 
python-cobra_0.13.4.orig.tar.gz
 597f5465ead6c05aeeb7c3b280f3c488450921c4 5932 
python-cobra_0.13.4-1.debian.tar.xz
 909ff08d89abd6f66e7411f795af78c7643bff0e 8849 
python-cobra_0.13.4-1_amd64.buildinfo
Checksums-Sha256:
 33795e0634804a5f00e1e5439c18bef1457589b3476acb733c9e6e2199f11306 2448 
python-cobra_0.13.4-1.dsc
 bdb6ba742ce4e912301505a08a7334ffbc256fe3580bebab07e63c1004af1413 1742133 
python-cobra_0.13.4.orig.tar.gz
 8f668477943fea1bb2e8f05071a5cbc0cd6f29ccc305b06d72fe02f66738a6fe 5932 
python-cobra_0.13.4-1.debian.tar.xz
 951a852a74e7a4ead06f25c18938079a12ba6375ee64060808668e88a80d0fa6 8849 
python-cobra_0.13.4-1_amd64.buildinfo
Files:
 1496d412193d0617e36dd099e75d378a 2448 python optional python-cobra_0.13.4-1.dsc
 dcb73d895fb56c61f46901605e5816ad 1742133 python optional 
python-cobra_0.13.4.orig.tar.gz
 90430e7a762469962c17b6cb729ce40c 5932 python optional 
python-cobra_0.13.4-1.debian.tar.xz
 16293fd1fbcc4d59efa5b3190fdfa324 8849 python optional 
python-cobra_0.13.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlvHj2kRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHtiw/5AZf00I8BuCEDdIbq+ohMbdYKdiCBcqBQ
3BYe8fAjBB2uT8t8t2lXOWz60qMO/3KM8tTeYIJs33W1cER5lvYKPQpCyFz86Cef
G98Zw2bOWqI7r16KIfvD23iKNCHr8zJEqFXCyeQ+XR/mWFp4RQ+jQeo5jB+GSrS7
deU1dhPAR5JS9MUr0Mo8iQgmqI9aFNOauy2teGunX/+nZsauTeAHp2JWOx1BCk/U
i9NTn6fFh3Wllg7Dr+33g8CZNyrN9YYtvB4jWrX/2ynQ1ktn/2T271Stv+nz0eRJ
p36JMPUqZQlwvgdovE58P5985UKVCzZnxJJxSju2OI2dF7uF7fRt4HtwwGLKOBFh
JxF0CrGXQZkvJwDs3bGAewAfA36o1H5uKZw6Vq92n/HZj/buBy7/fLDi4K78Ix5E
KAHZkjs+mBd/+Fp+rcXv5lbRhYmZicSYoFMxTbuUi8psUIO/mlzeiCemDnAY1cmT
mYKfKIHBIh9GrmziF8mXtNgwYoXY10B9jrIjznJjs49VrMH1hgmhiPzxbkP9Nfxc
B9m7nk1CzZ1I0ze

Bug#910665: marked as done (FTBFS on Debian sid)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Thu, 18 Oct 2018 01:35:26 +0200
with message-id 

and subject line Re: Bug#910665: FTBFS on Debian sid
has caused the Debian Bug report #910665,
regarding FTBFS on Debian sid
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
910665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zeroc-ice
Version: 3.7.1-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

zeroc-ice currently doesn't build in Debian unstable due:

In file included from modules/IcePy/Util.cpp:16:
../cpp/include/Ice/Protocol.h: In function ‘PyObject* 
IcePy::versionToString(PyObject*, const char*) [with T = Ice::ProtocolVersion]’:
../cpp/include/Ice/Protocol.h:186:54: error: ‘v.Ice::ProtocolVersion::major’ 
may be used uninitialized in this function [-Werror=maybe-uninitialized]
 return out << static_cast(version.major) << "." << 
static_cast(version.minor);
  ^~~
modules/IcePy/Util.cpp:124:7: note: ‘v.Ice::ProtocolVersion::major’ was 
declared here
 T v;
   ^
In file included from modules/IcePy/Util.cpp:16:
../cpp/include/Ice/Protocol.h:186:91: error: ‘v.Ice::ProtocolVersion::minor’ 
may be used uninitialized in this function [-Werror=maybe-uninitialized]
 return out << static_cast(version.major) << "." << 
static_cast(version.minor);

   ^
modules/IcePy/Util.cpp:124:7: note: ‘v.Ice::ProtocolVersion::minor’ was 
declared here
 T v;
   ^
cc1plus: all warnings being treated as errors

The full build log is here:
https://buildd.debian.org/status/fetch.php?pkg=zeroc-ice&arch=amd64&ver=3.7.1-2%2Bb1&stamp=1539022732&raw=0

Cheers,
Ondrej

- -- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8), LANGUAGE=en_DK.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAlu8r95fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcICQQ/+L3YZziCbfmKn4sZIWNTK9aPxAQ1P+GhOytxnVu9CPJelRRcisEMpyjkH
hVzJdfAHe3api7V7z2+ZTDoc3oNS8nxE5DtJhe7QR8m3gRh6KfstRYZ/6nDFMdP8
SqT/vT5zBbOV4EFUNJUrT8frNgP6Ge5oB3Np55WukbMg2kj+WCsxs/fhgk8cfDAd
TpqUB7uTiCTWXk1mNSzSkMfiWHIOD2PYLkgITWY/9smMYKb4QkCkKXOJM3c6rC7c
Edz4mLBKXWgPdpxRUJ/Sqi0SkWMDH8d7r4opVoxXUfziyJ0cbE5nfubRiSp8Xd9T
s7rgbznaRuiYNEWT6kvDAk67vo4+9mEhTj1WAiXqHPKLvZiu860+k4Yqd2xgxmRm
dn09YkQmkOnPIFTiAi4UCbQHrMkDXA/01Wkokfpfc8dKVsvjNMZuwKxYaci6I4x+
yBZ1vq1i1TAbl+aen2RG84oNYENpxqiFLPZs1RpMKuVwo8GVckU9eBcg9cWMmPj/
F73cE3Th23Ed2PRjWCkRbaiRzZsea2VIsN9dyZDL7pYxtNzBMl4u21JulE5/zOuS
c7OMDfSeeaaKlcVFhic91NH9f3bO7fnEtW5gPSViJQMXrha5D0PLVD4bqqPPVGrP
K5DJ2LuuTvOex2/O21pP8YeTu9LDjbrBJF1LClEcbbD0Fy7p/Bo=
=m3JQ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Uploaded 3.7.1-3 with a patch for this

https://github.com/zeroc-ice/ice-debian-packaging/commit/7ede38883c09ec2a3ef3b60ecc36f7f29a12fd41

On Wed, Oct 17, 2018 at 11:06 AM Jose Gutierrez de la Concha 
wrote:

>
>
> On Wed, Oct 17, 2018 at 8:09 AM Chris Knadle 
> wrote:
>
>> I'm looking at the build logs of the build failure, and I see that
>> zeroc-ice
>> 3.7.1-2 from June built correctly, but the 3.7.1-2+b1 binNMU fails to
>> build.
>>
>>https://buildd.debian.org/status/logs.php?pkg=zeroc-ice&arch=amd64
>>
>> I'm trying to figure out: which source dependency was uploaded such that a
>> binNMU was triggered?
>>
>> The build error happens when building within a python-3 directory, so I'm
>> guessing this issue is python3 related.
>>
>
> Hi,
>
> I think might be related to a GCC update that now is emitting this
> warning,  we are looking at
> this and I will  upload a new version with a patch shortly.
>
> Cheers,
> José
>
>>
>>-- Chris
>>
>> --
>> Chris Knadle
>> chris.kna...@coredump.us
>>
>>
>
> --
> José Gutiérrez de la Concha
> ZeroC, Inc.
>


-- 
José Gutiérrez de la Concha
ZeroC, Inc.
--- End Message ---


Bug#868411: marked as done (gniall: Please drop the (build-)dependency against gnome-vfs)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 21:33:27 +
with message-id 
and subject line Bug#868411: fixed in gniall 0.7.1-8
has caused the Debian Bug report #868411,
regarding gniall: Please drop the (build-)dependency against gnome-vfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
868411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gniall
Version: 0.7.1-7.1
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-vfs-removal oldlibs

Dear maintainer,

Your package is {build-}depending against gnome-vfs which is
deprecated for quite some times now and has been replaced by gvfs.

We are thinking about removing gnome-vfs for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: gniall
Source-Version: 0.7.1-8

We believe that the bug you reported is fixed in the latest version of
gniall, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 868...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated gniall package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Oct 2018 22:47:33 +0300
Source: gniall
Binary: gniall
Architecture: source
Version: 0.7.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Yavor Doganov 
Description:
 gniall - program that tries to learn a human language
Closes: 284416 478840 868411
Changes:
 gniall (0.7.1-8) unstable; urgency=medium
 .
   * QA upload.
   * debian/compat: Set to 11.
   * debian/control: Run wrap-and-sort -ast.
 (Maintainer): Set to Debian QA Group; the package is orphaned (#97).
 (Build-Depends): Bump debhelper requirement to match the compat
 level.  Replace libgnome2-dev and libgnomeui-dev with libgtk-3-dev.
 (Vcs-Git, Vcs-Browser): Add.
 (Standards-Version): Claim compliance with 4.2.1 as of this release.
   * debian/rules: Rewrite for modern dh; enable hardening.
   * debian/source/format: New file; set format to 3.0 (quilt).
   * debian/patches/gnome2-port.patch: Split from the .diff.gz.
   * debian/patches/gtk3-port.patch: New; port to GTK+ 3 (Closes: #868411).
   * debian/patches/learn-utf8.patch: New; learn words in UTF-8 (add
 support for other languages).  Addresses the first item from #284416.
   * debian/patches/file-input.patch: New; accept a plain text file as user
 input (Closes: #284416).
   * debian/patches/series: New file.
   * debian/dirs: Delete.
   * debian/manpages: New file.
   * debian/autogen.sh: New file; run aclocal before autoreconf.
   * debian/menu: Get rid.
   * debian/gNiall.desktop: Split from the .diff.gz; add additional
 Categories and Keyword keys (Closes: #478840).  Append %f to the value
 of the Exec key.
   * debian/gniall.1: Document that the program accepts a file as input.
   * debian/install: New file; install the .desktop file.
   * debian/watch: Replace with a fake one as the site is no more.
   * debian/gbp.conf: New file.
   * debian/copyright: Switch to machine-readable format.
Checksums-Sha1:
 90a82e3361970eeba95496a3017b2d516c405d39 1770 gniall_0.7.1-8.dsc
 f39ffd3ee7f3c7268639b2c0a986430f66a11b5d 13504 gniall_0.7.1-8.debian.tar.xz
 24d7ba32209eae6c3e58ae5a799bb72d65369bbb 15539 gniall_0.7.1-8_source.buildinfo
Checksums-Sha256:
 753ca440a3c5d286d9fec9ec2d6c05932f6bf01b1661cd644611fc42ddbaa6e3 1770 
gniall_0.7.1-8.dsc
 b2559fe9dda68a945ff6543571b6a6e9cdf86fb565a285cc7c6ab56c805bb642 13504 
gniall_0.7.1-8.debian.tar.xz
 a8ff89c2f25f7297c4c7fe9b8f82c99f00f808387f64e13e81612389b8e38968 15539 
gniall_0.7.1-8_source.buildinfo
Files:
 88e30419577f8a0d3c8ba5c8e9aa991c 1770 gnome optional gniall_0.7.1-8.dsc
 0918de6b7555a690747d1109b083f990 13504 gnome optional 
gniall_0.7.1-8.debian.tar.xz
 e0d80ed107d60fb76b80738ac574a416 15539 gnome optional 
gniall_0.7.1-8_source.buildinfo


Bug#909031: marked as done (dateutils FTBFS: FAIL: dzone.012)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 21:31:28 +
with message-id 
and subject line Bug#909031: fixed in dateutils 0.4.5-1
has caused the Debian Bug report #909031,
regarding dateutils FTBFS: FAIL: dzone.012
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
909031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dateutils
Version: 0.4.4-1
Severity: serious
Tags: ftbfs fixed-upstream patch
Forwarded: https://github.com/hroptatyr/dateutils/issues/84

https://tests.reproducible-builds.org/debian/history/dateutils.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dateutils.html

...
FAIL: dzone.012
===

$ dzone Europe/Berlin Australia/Sydney 08:00:00
--- "expected output  5dac0de2" 2019-10-20 08:26:55.048475193 -1200
+++ "actual output  5dac0de2"   2019-10-20 08:26:55.048475193 -1200
@@ -1,2 +1,2 @@
 10:00:00+02:00 Europe/Berlin
-18:00:00+10:00 Australia/Sydney
+19:00:00+11:00 Australia/Sydney
$? 1
FAIL dzone.012.clit (exit status: 1)


Testsuite summary for dateutils 0.4.4

# TOTAL: 853
# PASS:  852
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to https://github.com/hroptatyr/dateutils/issues

make[6]: *** [Makefile:1227: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: dateutils
Source-Version: 0.4.5-1

We believe that the bug you reported is fixed in the latest version of
dateutils, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated dateutils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Oct 2018 19:59:01 +0200
Source: dateutils
Binary: dateutils
Architecture: source amd64
Version: 0.4.5-1
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 dateutils  - nifty command line date and time utilities
Closes: 907348 909031
Changes:
 dateutils (0.4.5-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #907348, #909031)
   * debian/control: bump standard to 4.2.1 (no changes)
Checksums-Sha1:
 cdc8b70b79d706b50cecf85d43c3f070dbbcf326 2098 dateutils_0.4.5-1.dsc
 8c37337ac28f66f2ebd33cca6f377f79a55b5835 297605 dateutils_0.4.5.orig.tar.gz
 758a40494ee0f0cbe3eb7671a73e9ff6bb01a43f 4488 dateutils_0.4.5-1.debian.tar.xz
 28701a6fa9b182db7a2a8fb12ae30dde13b517be 1756636 
dateutils-dbgsym_0.4.5-1_amd64.deb
 998bdc44606c93f6e673c9818e9047dae69c1165 6348 dateutils_0.4.5-1_amd64.buildinfo
 2425072d2d9044f6c5b094b7773a70332489bfd2 217648 dateutils_0.4.5-1_amd64.deb
Checksums-Sha256:
 1f8b60e1de363599805c4b4ebf8d0fad7ed5cece226bd1e52154dec974c47555 2098 
dateutils_0.4.5-1.dsc
 aba6b7b73b52c075bd6aec776d3c975dcc4402703359ed3edfb4933324bf5013 297605 
dateutils_0.4.5.orig.tar.gz
 1b9ad7ca584cff2754f30d0cbf3ea6558310ad135d27f6b6d904abc863597689 4488 
dateutils_0.4.5-1.debian.tar.xz
 b6bd826ad120dd73739db4f04d73412fd59685436bfaebd3819d1f5a54074eb7 1756636 
dateutils-dbgsym_0.4.5-1_amd64.deb
 ca7154d70814017682f9e9947d867a5b97f18e81b363e6fa1c714a0b85aa3d32 6348 
dateutils_0.4.5-1_amd64.buildinfo
 bfeb132bc62c1ba7a2035e7091b3b9ad6e249046416409e53c1629c70db9d472 217648 
dateutils_0.4.5-1_amd64.deb
Files:
 c8126a6b0c39761927641bc53affa4ad 2098 utils optional dateutils_0.4.5-1.dsc
 fbbed0a14a2da743b680913490aed613 297605 utils optional 
dateutils_0.4.5.orig.tar.gz
 08491429fc8af91e818c8bc4ecbadcac 4488 utils optional 
dateutils_0.4.5-1.debian.tar.xz
 cf33a0f0a39ba4ca73b2f1cc5dbcc022 1756636 debug optional 
dateutils-dbgsym_0.4.5-1_amd64.deb
 bae302d1d5f62439bc3ce27c4c001942 6348 utils optional 
dateutils_0.4.5-1_amd64.buildinfo
 e9b20e940a7d9afa2178d20bf7ff83b3 217648 utils optional 
dateu

Bug#907348: marked as done (dateutils FTBFS on 32bit: test failures)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 21:31:28 +
with message-id 
and subject line Bug#907348: fixed in dateutils 0.4.5-1
has caused the Debian Bug report #907348,
regarding dateutils FTBFS on 32bit: test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
907348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dateutils
Version: 0.4.4-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=dateutils&suite=sid

...
FAIL: dtcore-conv
=

  VALUES DIFFER 1341100836 v 1341100833
  VALUES DIFFER 1341100837 v 1341100835
FAIL dtcore-conv (exit status: 1)

FAIL: dtconv.024


$ dconv '2012-03-01 00:00:00' -z TAI
--- "expected output  5b88a553" 2018-08-26 16:07:27.682809364 +
+++ "actual output  5b88a553"   2018-08-26 16:07:27.682809364 +
@@ -1 +1 @@
-2012-03-01T00:00:34
+2012-03-01T00:00:37
$? 1
FAIL dtconv.024.clit (exit status: 1)

FAIL: dtconv.026


$ dconv '2012-03-01 00:00:00' -z GPS
--- "expected output  5b881603" 2018-08-26 16:07:27.702809312 +
+++ "actual output  5b881603"   2018-08-26 16:07:27.702809312 +
@@ -1 +1 @@
-2012-03-01T00:00:15
+2012-03-01T00:00:18
$? 1
FAIL dtconv.026.clit (exit status: 1)

FAIL: dtconv.027


$ dconv '2012-03-01 00:00:00' --from-zone TAI
--- "expected output  5b8820a2" 2018-08-26 16:07:27.714809281 +
+++ "actual output  5b8820a2"   2018-08-26 16:07:27.714809281 +
@@ -1 +1 @@
-2012-02-29T23:59:26
+2012-02-29T23:59:23
$? 1
FAIL dtconv.027.clit (exit status: 1)

FAIL: dtconv.029


$ dconv '2012-03-01 00:00:00' --from-zone GPS
--- "expected output  5b899088" 2018-08-26 16:07:27.734809230 +
+++ "actual output  5b899088"   2018-08-26 16:07:27.734809230 +
@@ -1 +1 @@
-2012-02-29T23:59:45
+2012-02-29T23:59:42
$? 1
FAIL dtconv.029.clit (exit status: 1)

FAIL: dtconv.030


$ dconv '1970-01-01 00:00:00' -z TAI
--- "expected output  5b89b895" 2018-08-26 16:07:27.746809199 +
+++ "actual output  5b89b895"   2018-08-26 16:07:27.746809199 +
@@ -1 +1 @@
-1970-01-01T00:00:10
+1970-01-01T00:00:37
$? 1
FAIL dtconv.030.clit (exit status: 1)

FAIL: dtconv.031


$ dconv '1972-01-01 00:00:00' -z TAI
--- "expected output  5b89402a" 2018-08-26 16:07:27.754809178 +
+++ "actual output  5b89402a"   2018-08-26 16:07:27.754809178 +
@@ -1 +1 @@
-1972-01-01T00:00:10
+1972-01-01T00:00:37
$? 1
FAIL dtconv.031.clit (exit status: 1)

FAIL: dtconv.032


$ dconv '1972-01-01 00:00:01' -z TAI
--- "expected output  5b8967c5" 2018-08-26 16:07:27.766809147 +
+++ "actual output  5b8967c5"   2018-08-26 16:07:27.766809147 +
@@ -1 +1 @@
-1972-01-01T00:00:11
+1972-01-01T00:00:38
$? 1
FAIL dtconv.032.clit (exit status: 1)

FAIL: dtadd.030
===

$ dadd '2012-06-30 23:59:30' 30rs
--- "expected output  5b8a5636" 2018-08-26 16:07:35.554789033 +
+++ "actual output  5b8a5636"   2018-08-26 16:07:35.554789033 +
@@ -1 +1 @@
-2012-06-30T23:59:60
+2012-07-01T00:00:00
$? 1
FAIL dtadd.030.clit (exit status: 1)

FAIL: dtadd.031
===

$ dadd '2012-06-30 23:59:30' 31rs
--- "expected output  5b8a7e58" 2018-08-26 16:07:35.566789002 +
+++ "actual output  5b8a7e58"   2018-08-26 16:07:35.566789002 +
@@ -1 +1 @@
-2012-07-01T00:00:00
+2012-07-01T00:00:01
$? 1
FAIL dtadd.031.clit (exit status: 1)

FAIL: dtadd.034
===

$ dadd '2012-07-01 00:00:05' -6rs
--- "expected output  5b8bf7d2" 2018-08-26 16:07:35.598788920 +
+++ "actual output  5b8bf7d2"   2018-08-26 16:07:35.598788920 +
@@ -1 +1 @@
-2012-06-30T23:59:60
+2012-06-30T23:59:59
$? 1
FAIL dtadd.034.clit (exit status: 1)

FAIL: dtadd.035
===

$ dadd '2012-07-01 00:00:05' -7rs
--- "expected output  5b8b9fe9" 2018-08-26 16:07:35.606788899 +
+++ "actual output  5b8b9fe9"   2018-08-26 16:07:35.606788899 +
@@ -1 +1 @@
-2012-06-30T23:59:59
+2012-06-30T23:59:58
$? 1
FAIL dtadd.035.clit (exit status: 1)

FAIL: dtdiff.019


$ ddiff '2012-06-30 23:59:00' '2012-07-01 00:00:00' -f '%rSs'
--- "expected output  5b86f62a" 2018-08-26 16:07:36.270787184 +
+++ "actual output  5b86f62a"   2018-08-26 16:07:36.270787184 +
@@ -1 +1 @@
-61s
+60s
$? 1
FAIL dtdiff.019.clit (exit status: 1)

FAIL: dtdiff.021


$ ddiff '2012-06-30 23:59:00' '2012-07-01 00:00:00' -f '%rT'
--- "expected output  5b86a6e9" 2018-08-26 16:07:36.290787133 +
+++ "actual output  5b86a6e9"   2018-08-26 16:07:36.290787133 +
@@ -1 +1 @@

Bug#910704: marked as done (cbmc: Build depend on default-jdk instead of openjdk-8-jdk)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 21:31:02 +
with message-id 
and subject line Bug#910704: fixed in cbmc 5.10-5
has caused the Debian Bug report #910704,
regarding cbmc: Build depend on default-jdk instead of openjdk-8-jdk
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
910704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cbmc
Severity: serious
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java10

cbmc build-depends on openjdk-8-jdk that we plan to remove in Buster,
it should use default-jdk instead.
--- End Message ---
--- Begin Message ---
Source: cbmc
Source-Version: 5.10-5

We believe that the bug you reported is fixed in the latest version of
cbmc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Tautschnig  (supplier of updated cbmc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 17 Oct 2018 19:55:17 +0100
Source: cbmc
Binary: cbmc
Architecture: source
Version: 5.10-5
Distribution: unstable
Urgency: low
Maintainer: Michael Tautschnig 
Changed-By: Michael Tautschnig 
Description:
 cbmc   - bounded model checker for C and C++ programs
Closes: 910704
Changes:
 cbmc (5.10-5) unstable; urgency=low
 .
   * Use default-jdk-headless instead of openjdk-8 (Closes: #910704)
Checksums-Sha1:
 57ee4bb7d4c78155cfa135904b326f1e8e368428 2167 cbmc_5.10-5.dsc
 f42ff433a50bbd23fa4ea7b9289bbacc248d452d 12548 cbmc_5.10-5.debian.tar.xz
Checksums-Sha256:
 225bb25ee1350f776785b51e0308e23347e04c8fd0b9bc552d7fb0e8a8b6c6c3 2167 
cbmc_5.10-5.dsc
 f52e722787b81a974cac6fc8da42d663c73e98e48c34246bb41c8ec987928286 12548 
cbmc_5.10-5.debian.tar.xz
Files:
 43db96e8030f5acc0766e0381d21 2167 science optional cbmc_5.10-5.dsc
 005272fb297ad972e8134cb9c8f28a46 12548 science optional 
cbmc_5.10-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org

iQJCBAEBCAAsFiEErKbD9OEAOYbzU4gEO7+DkzbsqTEFAlvHoUQOHG10QGRlYmlh
bi5vcmcACgkQO7+DkzbsqTHdFxAAlRc5SgSxSdM8GhZUhYTH2p8SeF5OSn/cE/BA
tc2HbWaKI4/9LOCxnRYvfcvLXDX1PjfWTsA6Q2o77rF0Bt51lWWU2DcK7Lnunzv2
iATHTNfRErbI+wXlL41rUsM101xGBWT8igLicjDCzQgTv4MKjrhpLCiicy+sq135
yC8w6SIMVFwQKpA/OnbGrprAJW1+s25I5CXs4D++60wpsD5FennmgE9nDBWMevwv
dNgXSx7wiSvu1OahQ6rZT0VNzQ0TrUsCs7MIqm7BRJ1DlV535VdEKj1tdjW3z6ue
RtGa+cVLRJNoehLA/JrICLGvpHUy0GJ9HFfYndEoV3vsq5FGGhk1n572VwNKcD+/
LXndAVDRXk0mUOk6iVvZ/kQBoadn70I6YUAlPOnr8j7jZjfpd6PzGhlOJkWYm7sw
WjTT4OlLsnTDS5sHmQqRjwjHDxpXiAlrY5T5058hmiFxAD+tggnEvgX8Uwj6B55h
RqA2+madMlhAydiPDJWNbS/a5RHxULvA6YpwNZ04Oq0T1ugimulYc4le/D5kdPg2
1Dp0keMcN7hdLgPSzIukvriFfQTXh55H9aIXZ3wN7Y3fu9Va4acQiJ9gxOqkdVDk
xBZjI/0maCdZAFV48wUsyirsu0uXyWnoqWtEpZYF499jKC0nHVJlgaZtCq8j858u
ftwyw9U=
=h3wd
-END PGP SIGNATURE End Message ---


Bug#911270: infnoise: Fails to upgrade (systemd, no device plugged in)

2018-10-17 Thread Axel Beckert
Package: infnoise
Version: 0.3.0+dfsg-1
Severity: serious

Hi Stephen,

I also have infnoise installed on my laptop with systemd as init system
where I first tried the TRNG stick. There upgrading from 0.2.6+dfsg-1
failed as follows:

Preparing to unpack .../151-infnoise_0.3.0+dfsg-1_amd64.deb ...
Unpacking infnoise (0.3.0+dfsg-1) over (0.2.6+dfsg-1) ...
[…]
Setting up infnoise (0.3.0+dfsg-1) ...
A dependency job for infnoise.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript infnoise, action "restart" failed.
● infnoise.service - Wayward Geek InfNoise TRNG driver
   Loaded: loaded (/lib/systemd/system/infnoise.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead)
 Docs: man:infnoise.service(8)

Oct 08 19:27:51 c-cactus2 systemd[1]: Dependency failed for Wayward Geek 
InfNoise TRNG driver.
Oct 08 19:27:51 c-cactus2 systemd[1]: infnoise.service: Job 
infnoise.service/start failed with result 'dependency'.
Oct 17 22:03:08 c-cactus2 systemd[1]: infnoise.service: Bound to unit 
dev-infnoise.device, but unit isn't active.
Oct 17 22:03:08 c-cactus2 systemd[1]: Dependency failed for Wayward Geek 
InfNoise TRNG driver.
Oct 17 22:03:08 c-cactus2 systemd[1]: infnoise.service: Job 
infnoise.service/start failed with result 'dependency'.
Oct 17 22:06:01 c-cactus2 systemd[1]: infnoise.service: Bound to unit 
dev-infnoise.device, but unit isn't active.
Oct 17 22:06:01 c-cactus2 systemd[1]: Dependency failed for Wayward Geek 
InfNoise TRNG driver.
Oct 17 22:06:01 c-cactus2 systemd[1]: infnoise.service: Job 
infnoise.service/start failed with result 'dependency'.
dpkg: error processing package infnoise (--configure):
 installed infnoise package post-installation script subprocess returned error 
exit status 1

'journalctl -xe' says:
Oct 17 22:10:04 c-cactus2 systemd[1]: Unnecessary job for dev-infnoise.device 
was removed.
-- Subject: Unit dev-infnoise.device has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit dev-infnoise.device has failed.
--
-- The result is RESULT.
Oct 17 22:10:04 c-cactus2 systemd[1]: infnoise.service: Bound to unit 
dev-infnoise.device, but unit isn't active.
Oct 17 22:10:04 c-cactus2 systemd[1]: Dependency failed for Wayward Geek 
InfNoise TRNG driver.
-- Subject: Unit infnoise.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit infnoise.service has failed.
--
-- The result is RESULT.
Oct 17 22:10:04 c-cactus2 systemd[1]: infnoise.service: Job 
infnoise.service/start failed with result 'dependency'.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages infnoise depends on:
ii  libc6 2.27-6
ii  libftdi1  0.20-4

infnoise recommends no packages.

infnoise suggests no packages.

-- no debconf information



Bug#911269: All Qt packages on Debian Sid have broken dependencies.

2018-10-17 Thread scozatigheratten
Package: libqt5core5a
Version: 5.11.2+dfsg-3
Severity: serious

Dear Qt maintainers,

All Qt packages that depend on the virtual package `qtbase-abi-5-11-0` will not 
install because the virtual package is no longer provided by
libqt5core5a since 5.11.1 was upgraded to 5.11.2.
Other virtual packages are broken as well.
This is a serious issue and renders any package that depends on Qt 
uninstallable on Sid, including KDE.

Thanks for the attention.

Bug#911266: mosquitto: CVE-2017-7653

2018-10-17 Thread Salvatore Bonaccorso
Source: mosquitto
Version: 1.4.10-1
Severity: grave
Tags: patch security upstream
Forwarded: https://bugs.eclipse.org/bugs/show_bug.cgi?id=532113

Hi,

The following vulnerability was published for mosquitto. Planned to be
fixed in a DSA, and needs to be fixed for buster as reason for the RC
severity filling.

CVE-2017-7653[0]:
| The Eclipse Mosquitto broker up to version 1.4.15 does not reject
| strings that are not valid UTF-8. A malicious client could cause other
| clients that do reject invalid UTF-8 strings to disconnect themselves
| from the broker by sending a topic string which is not valid UTF-8,
| and so cause a denial of service for the clients.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7653
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7653
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=532113
[2] 
https://github.com/eclipse/mosquitto/commit/729a09310a7a56fbe5933b70b4588049da1a42b4

Regards,
Salvatore



Bug#911265: mosquitto: CVE-2017-7654

2018-10-17 Thread Salvatore Bonaccorso
Source: mosquitto
Version: 1.4.10-1
Severity: grave
Tags: patch security upstream
Forwarded: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533493

Hi,

The following vulnerability was published for mosquitto.

Filling with RC severity as it will be fixed in a DSA, and needs to be
fixed before buster release in unstable/testing as well.

CVE-2017-7654[0]:
| In Eclipse Mosquitto 1.4.15 and earlier, a Memory Leak vulnerability
| was found within the Mosquitto Broker. Unauthenticated clients can
| send crafted CONNECT packets which could cause a denial of service in
| the Mosquitto Broker.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7654
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7654
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=533493
[2] 
https://github.com/eclipse/mosquitto/commit/51ec5601c2ec523bf2973fdc1eca77335eafb8de

Regards,
Salvatore



Bug#910911: command-not-found is affected, too

2018-10-17 Thread Axel Beckert
Hi,

JFTR: command-not-found is affected by this issue, too:

$ acn foo
Unable to open binary database /var/cache/command-not-found//contrib.db: 
Malformed database file header
Sorry, command-not-found has crashed! Please file a bug report for 
the command-not-found package, see http://www.debian.org/Bugs/Reporting
for further information
Please include the following information with the report:

command-not-found version: 0.2.26
$ file /var/cache/command-not-found/*.db
/var/cache/command-not-found/contrib.db:  GNU dbm 1.x or ndbm database, little 
endian, old
/var/cache/command-not-found/main.db: GNU dbm 1.x or ndbm database, little 
endian, old
/var/cache/command-not-found/non-free.db: GNU dbm 1.x or ndbm database, little 
endian, old
$ for i in /var/cache/command-not-found/*.db ; do gdbm_dump $i; done
gdbm_dump: gdbm_open failed: Malformed database file header
gdbm_dump: gdbm_open failed: Malformed database file header
gdbm_dump: gdbm_open failed: Malformed database file header
$

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Processed: affects 910911

2018-10-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # Unable to open binary database /var/cache/command-not-found//contrib.db: 
> Malformed database file header
> affects 910911 + command-not-found
Bug #910911 [libgdbm6] libgdbm6: can't read (some?) older GDBM databases
Added indication that 910911 affects command-not-found
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
910911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#907015: [Pkg-openssl-devel] Bug#907015: openssl version 1.1.1 breaks multiple reverse dependencies; versioned Breaks needed

2018-10-17 Thread Kurt Roeckx
On Wed, Oct 17, 2018 at 09:22:35PM +0300, Niko Tyni wrote:
> 
> As a status update, I count just six packages left in testing that are
> marked as blockers for this bug. (I could be wrong of course; double
> checking welcome.)

I think you missed one.

> - src:foolscap #898800: foolscap: FTBFS against openssl 1.1.1

I'm not sure if this is actually still a problem, there have been
fixes on the python and openssl side for this. reproducible builds
shows it as having problems trying to install the build
dependencies for months.

> - src:kdeconnect #907339: qtbase-opensource-src breaks kdeconnect autopkgtest 
> possibly due to new openssl
> - src:kimap #907427: (kimap) openssl 1.1.1 breaks ssl tests

There is also purpose, they all seem to be related to
qtbase-opensource-src.

> - src:ruby-eventmachine #900160: ruby-eventmachine: FTBFS against openssl 
> 1.1.1

I'm not sure why the patch didn't fix it

> - src:python-boto #909545: SSL CERTIFICATE_VERIFY_FAILED when using gs 
> (Google Cloud Storage) backend

Patch is available.

> - src:m2crypto #897658: m2crypto: FTBFS against openssl 1.1.1

Only test suite problems that don't show any real issues.

> Is it still useful to block openssl 1.1.1 testing migration with this bug?

Things like python are also blocked on it. I have no problem
lowering the severity of this issue, to make it migrate.


Kurt



Bug#911159: marked as done (please stop building the frama-c GUI)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 21:11:06 +0200
with message-id <20181017191105.ga31...@seneca.home.org>
and subject line Re: Bug#911159: please stop building the frama-c GUI
has caused the Debian Bug report #911159,
regarding please stop building the frama-c GUI
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
911159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:frama-c
Version: 20171101+sulfur+dfsg-1
Tags: sid buster
Severity: serious

Bug #885677 filed for lablgtk2 asks for the removal of that package.  To prevent
removing frama-c from the distro, please consider just building the base
package, dropping the GUI package.   Asking because creduce would be removed
otherwise as well.
--- End Message ---
--- Begin Message ---
On Tue, Oct 16, 2018 at 05:09:20PM +0200, Matthias Klose wrote:

> Bug #885677 filed for lablgtk2 asks for the removal of that package.  To 
> prevent
> removing frama-c from the distro, please consider just building the base
> package, dropping the GUI package.   Asking because creduce would be removed
> otherwise as well.

this is no longer relevant as #885677 is fixed now. -Ralf.--- End Message ---


Bug#911260: libkf5xmlgui5: Uninstallable since upload of qtbase-opensource-src 5.11.2+dfsg

2018-10-17 Thread Andreas Tille
Package: libkf5xmlgui5
Severity: grave
Justification: renders package unusable

Hi,


$ sudo apt install libkf5xmlgui5
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libkf5xmlgui5 : Depends: qtbase-abi-5-11-0 but it is not installable
E: Unable to correct problems, you have held broken packages.


The reason is pretty obvious since the version of libqt5core5a
in unstable now provides a higher ABI version

$ apt-cache show libqt5core5a | grep -e Provides -e Version
Version: 5.11.2+dfsg-3
Provides: qtbase-abi-5-11-2
Version: 5.11.1+dfsg-9
Provides: qtbase-abi-5-11-0


Kind regards

   Andreas.

-- System Information:
Debian Release: buster/sid 
  APT prefers unstable 
  APT policy: (500, 'unstable') 
Architecture: amd64 (x86_64) 
 
Kernel: Linux 4.17.0-1-amd64 (SMP w/2 CPU cores) 
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968) 
Shell: /bin/sh linked to /bin/dash 
Init: unable to detect 
 
Versions of packages libkf5xmlgui5 depends on: 
ii  libc6  2.27-6 
pn  libkf5attica5   
pn  libkf5configcore5   
pn  libkf5configgui5
pn  libkf5configwidgets5
pn  libkf5coreaddons5   
pn  libkf5globalaccel-bin   
pn  libkf5globalaccel5  
pn  libkf5i18n5 
pn  libkf5iconthemes5   
pn  libkf5itemviews5
pn  libkf5textwidgets5  
pn  libkf5widgetsaddons5
pn  libkf5windowsystem5 
pn  libkf5xmlgui-data   
pn  libqt5core5a
pn  libqt5dbus5 
pn  libqt5gui5  
pn  libqt5network5  
pn  libqt5printsupport5 
pn  libqt5widgets5  
pn  libqt5xml5  
ii  libstdc++6 8.2.0-7 
pn  qtbase-abi-5-11-0   
 
Versions of packages libkf5xmlgui5 recommends: 
pn  libkf5xmlgui-bin   
 
libkf5xmlgui5 suggests no packages.



Bug#907015: openssl version 1.1.1 breaks multiple reverse dependencies; versioned Breaks needed

2018-10-17 Thread Niko Tyni
On Thu, Aug 23, 2018 at 09:07:31AM +0200, Paul Gevers wrote:
> Source: openssl
> Version: 1.1.1~~pre9-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: breaks
> Control: affects -1 src:ganeti src:libnet-ssleay-perl src:ruby-openssl
> Control: affects -1 src:m2crypto src:python2.7 src:python3.6
> Control: affects -1 src:python3.7 src:stunnel4 isync
> Control: block -1 by 900161 906981 906955

> We file this bug to:
> 1) allow reverse dependencies some time (we let you judge how long is
> reasonable for the serious severity) to adapt to the new situation
> 2) enable the openssl package to collect information which packages it
> breaks and which version of those package fix the issue. With that
> information the openssl package can add versioned Breaks

As a status update, I count just six packages left in testing that are
marked as blockers for this bug. (I could be wrong of course; double
checking welcome.)

- src:foolscap #898800: foolscap: FTBFS against openssl 1.1.1
- src:kdeconnect #907339: qtbase-opensource-src breaks kdeconnect autopkgtest 
possibly due to new openssl
- src:m2crypto #897658: m2crypto: FTBFS against openssl 1.1.1
- src:python-boto #909545: SSL CERTIFICATE_VERIFY_FAILED when using gs (Google 
Cloud Storage) backend
- src:kimap #907427: (kimap) openssl 1.1.1 breaks ssl tests
- src:ruby-eventmachine #900160: ruby-eventmachine: FTBFS against openssl 1.1.1

Is it still useful to block openssl 1.1.1 testing migration with this bug?

My personal concern is that the openssl testing/unstable situation has
been the only blocker for a Perl 5.28 transition for quite some time now,
and the buster transition deadline (2019-01-12) is less than three
months away.
-- 
Niko Tyni   nt...@debian.org



Bug#911258: libopenhmd-dev: missing dependency on libhidapi-dev, required by pkg-config metadata

2018-10-17 Thread Simon McVittie
Package: libopenhmd-dev
Version: 0.2.0-2
Severity: serious
Tags: patch
Justification: Policy 3.5

libopenhmd-dev contains openhmd.pc, which Requires hidapi-libusb.
hidapi-libusb.pc is provided by libhidapi-dev, which is a
build-dependency for libopenhmd but is not included in libopenhmd's
dependencies.

The pkg-config file also contains an incorrect includedir and libdir,
because it assumes that the .pc file is installed 2 directories below
${prefix} (typically ${prefix}/lib/pkgconfig), but this is not true in
Debian. I attach proposed patches to fix this. Note that they include a
non-upstreamed patch for the pkg-config metadata.

This class of bug is easy to detect with an autopkgtest that builds
and runs a simple program (also included in the attached patches).

Regards,
smcv
>From f89ce3e8b599cf7783fb5db23d95d15315c1186e Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 17 Oct 2018 17:14:57 +0100
Subject: [PATCH 1/3] d/tests/build: Add a simple compile/link/execute test

---
 debian/changelog |  6 ++
 debian/tests/build   | 23 +++
 debian/tests/control |  3 +++
 3 files changed, 32 insertions(+)
 create mode 100755 debian/tests/build
 create mode 100644 debian/tests/control

diff --git a/debian/changelog b/debian/changelog
index fdf402e..6d71daa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libopenhmd (0.2.0-3.1) UNRELEASED; urgency=medium
+
+  * d/tests/build: Add a simple compile/link/execute test
+
+ -- Simon McVittie   Wed, 17 Oct 2018 17:14:22 +0100
+
 libopenhmd (0.2.0-3) unstable; urgency=medium
 
   * Fix filename in debian/watch
diff --git a/debian/tests/build b/debian/tests/build
new file mode 100755
index 000..9bb6c12
--- /dev/null
+++ b/debian/tests/build
@@ -0,0 +1,23 @@
+#!/bin/sh
+
+set -e
+exec 2>&1
+set -u
+set -x
+
+cd "$AUTOPKGTEST_TMP"
+cat > example.c <<'EOF'
+/* A very much simplified version of examples/simple/simple.c */
+#include 
+
+int main(void)
+{
+ohmd_context *ctx = ohmd_ctx_create();
+ohmd_ctx_destroy(ctx);
+return 0;
+}
+EOF
+
+gcc -o example example.c $(pkg-config --cflags --libs openhmd)
+test -x ./example
+./example
diff --git a/debian/tests/control b/debian/tests/control
new file mode 100644
index 000..9140881
--- /dev/null
+++ b/debian/tests/control
@@ -0,0 +1,3 @@
+Tests: build
+Restrictions: superficial
+Depends: build-essential, libopenhmd-dev, pkg-config
-- 
2.19.1

>From 66b6c5645d4edadbb2d80121e78a2ef4e901b357 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 17 Oct 2018 17:44:39 +0100
Subject: [PATCH 2/3] Make libopenhmd-dev depend on libhidapi-dev so the
 pkg-config metadata will work

---
 debian/changelog | 2 ++
 debian/control   | 3 ++-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 6d71daa..b7423fd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
 libopenhmd (0.2.0-3.1) UNRELEASED; urgency=medium
 
   * d/tests/build: Add a simple compile/link/execute test
+  * Make libopenhmd-dev depend on libhidapi-dev so the pkg-config
+metadata will work
 
  -- Simon McVittie   Wed, 17 Oct 2018 17:14:22 +0100
 
diff --git a/debian/control b/debian/control
index 00f2ef4..38d4813 100644
--- a/debian/control
+++ b/debian/control
@@ -27,7 +27,8 @@ Description: API and drivers for immersive technology (shared library)
 Package: libopenhmd-dev
 Architecture: any
 Section: libdevel
-Depends: libopenhmd0 (= ${binary:Version}),
+Depends: libhidapi-dev,
+ libopenhmd0 (= ${binary:Version}),
  ${misc:Depends}
 Description: API and drivers for immersive technology (development files)
  OpenHMD aims to provide a Free and Open Source API and drivers for
-- 
2.19.1

>From 3bdd4fd30d4dda02dd101a6954379ad45d3d5832 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 17 Oct 2018 17:53:03 +0100
Subject: [PATCH 3/3] Further fixes to the pkg-config metadata

---
 debian/changelog  |  3 +
 ...code-the-hidapi-dependency-in-the-pk.patch | 70 +++
 ...titute-the-correct-libdir-includedir.patch | 27 +++
 debian/patches/series |  2 +
 4 files changed, 102 insertions(+)
 create mode 100644 debian/patches/Autoconf-do-not-hard-code-the-hidapi-dependency-in-the-pk.patch
 create mode 100644 debian/patches/pkg-config-Substitute-the-correct-libdir-includedir.patch
 create mode 100644 debian/patches/series

diff --git a/debian/changelog b/debian/changelog
index b7423fd..dec15aa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,9 @@ libopenhmd (0.2.0-3.1) UNRELEASED; urgency=medium
   * d/tests/build: Add a simple compile/link/execute test
   * Make libopenhmd-dev depend on libhidapi-dev so the pkg-config
 metadata will work
+  * d/p/Autoconf-do-not-hard-code-the-hidapi-dependency-in-the-pk.patch,
+d/p/pkg-config-Substitute-the-correct-libdir-includedir.patch:
+Further fixes to the pkg-config metadata
 
  -- Simon Mc

Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))

2018-10-17 Thread Andreas Tille
Hi Andrius,

On Wed, Oct 17, 2018 at 01:57:29PM +0300, Andrius Merkys wrote:
> On 10/16/18 5:03 PM, Andreas Tille wrote:
> > Very good.  Let me know if I could be of any help (which basically would
> > boil down to testing and if needed sponsoring).
> 
> Many thanks! I will turn to you once I get the updated package build.

Fine.
 
> > Interesting.  You might like to join the Debian Med sprint in March 2019
> > which will happen in Vilnius[1] (no better details yet).
> 
> Thanks, I will be there.

Meanwile the Wiki page is setup and you (and for sure everybody else
reading this list) can add your name to the list of participants:

   https://wiki.debian.org/Sprints/2019/DebianMed2019

Looking forward to meed you in Vilnius

  Andreas.

-- 
http://fam-tille.de



Bug#885678: gmysqlcc: Depends on unmaintained gtksourceview2

2018-10-17 Thread René Mayorga
On Tue, Oct 16, 2018 at 12:44:52PM -0400, Jeremy Bicha wrote:
> On Mon, Jan 8, 2018 at 11:07 AM René Mayorga  wrote:
> > On Thu, Dec 28, 2017 at 10:14:04PM -0500, Jeremy Bicha wrote:
> > > Please port your package to GTK3 and gtksourceview3 and related
> > > maintained libraries. Otherwise, please consider requesting that your
> > > package be removed from Debian to help us complete this goal.
> >
> > This is quite an old package, upstream is dead for more than 5 years at
> > least. I don't think there is any plan to port this package to use GTK3.
> >
> > Besides this, this package is not longer so usable as it was before, now
> > mysql-workbench fulfill all the needs for the users, thought.
> >
> > So I'll request this package to be removed.
> 
> Do you still intend to file the removal bug? I can file it for you if you 
> want.

Please go ahead, I've been quite busy and haven't time to do this simple
task :(

Cheers

--
René


signature.asc
Description: Digital signature


Bug#894519: xpra 2.4 depends on python-gtkglext1

2018-10-17 Thread Jeremy Bicha
python-gtkglext1 is back in Testing (Buster) now.

Thanks,
Jeremy Bicha



Processed: limit source to gniall, tagging 284416, tagging 478840, tagging 868411

2018-10-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> limit source gniall
Limiting to bugs with field 'source' containing at least one of 'gniall'
Limit currently set to 'source':'gniall'

> tags 284416 + pending
Bug #284416 [gniall] Feature requests
Added tag(s) pending.
> tags 478840 + pending
Bug #478840 [gniall] gniall: Use a desktop with more specific game entries for 
those using submenus
Added tag(s) pending.
> tags 868411 + pending
Bug #868411 [src:gniall] gniall: Please drop the (build-)dependency against 
gnome-vfs
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
284416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284416
478840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478840
868411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#909825: marked as done (pd-iemlib FTBFS with puredata 0.49.0)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 16:06:28 +
with message-id 
and subject line Bug#909825: fixed in pd-iemlib 1.20.1-3
has caused the Debian Bug report #909825,
regarding pd-iemlib FTBFS with puredata 0.49.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
909825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-iemlib
Version: 1.20.1-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pd-iemlib.html

...
em_pbank_csv.c: In function 'iem_pbank_csv_write':
iem_pbank_csv.c:103:29: error: assignment of read-only location 
'*(format->s_name + (sizetype)p)'
   format->s_name[p] += 'a' - 'A';
 ^~
--- End Message ---
--- Begin Message ---
Source: pd-iemlib
Source-Version: 1.20.1-3

We believe that the bug you reported is fixed in the latest version of
pd-iemlib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-iemlib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 17 Oct 2018 17:43:32 +0200
Source: pd-iemlib
Binary: pd-iemlib
Architecture: source
Version: 1.20.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 pd-iemlib  - collection of general purpose objects and filters for Pure Data
Closes: 909825
Changes:
 pd-iemlib (1.20.1-3) unstable; urgency=medium
 .
   * Backported fix for Pd-0.49's API cleanup (Closes: #909825)
   * Backported fix for long filenames
   * Declare that the build doesn't require "root" privileges
   * Bumped standards version to 4.2.1
Checksums-Sha1:
 722f92ebf464f7d75efd135c9a2ca9e5c1586bb3 2054 pd-iemlib_1.20.1-3.dsc
 7a282809b14becf9a8f5e68c759512721992feda 7992 pd-iemlib_1.20.1-3.debian.tar.xz
 55dfa9e209b5f5eb8247420d7b0b1a8503042eff 6359 
pd-iemlib_1.20.1-3_amd64.buildinfo
Checksums-Sha256:
 ff0137d1ec10fddb55de5f9261b12b146841988935bb0ac5d9697519c29cb3ec 2054 
pd-iemlib_1.20.1-3.dsc
 385c200e4741b10932d2e30cba7c69b4816172ca803b4ccf1a08b882feae1a9b 7992 
pd-iemlib_1.20.1-3.debian.tar.xz
 67b1d8c184493cdb6991a047635289179a3e45a555cc024ab96b7e116bdc579b 6359 
pd-iemlib_1.20.1-3_amd64.buildinfo
Files:
 20d00dea26fefc437f588b302e7d0a5c 2054 sound optional pd-iemlib_1.20.1-3.dsc
 baddb86b80d537562908a008ae388291 7992 sound optional 
pd-iemlib_1.20.1-3.debian.tar.xz
 deb64f137410ed42dc40f1cc615b2928 6359 sound optional 
pd-iemlib_1.20.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAlvHWQcACgkQtlAZxH96
Nvjm3Q/+KtmwAnUvC063Bdt/1mx2oGpArk4sLbq59zENKN1ritMf9H6tGj7BpgOQ
xqbhxsOFUIgyHEcaAzxZuZm87kGU5qPprf65gImE58ihKZeIYz/XY3WJmORqhHyK
4DlbSUlWGB8CQaCpM/oUmVShljH4w72wgk4VJJIxCdDnqQ3pu2OU20skj94iu3CH
wSCBczPwzo9VglnvhH4O9uADo4KDPbJj+21w66mfnhz87WZIeJz/wnHK4Z2kFHoL
YNmz/d+d4mqPnO6L1PKEy1Rb10LiG41XNwt/ovGfUrIi/mjkZriq6DwRiP0DctJJ
AZfXcTJUJDzGiGpObF6UFbsLIWbl9fx20b6erOMTLFn7aROYr/boMDtVOi6LToZR
XPI9gHCkDDzE+qfhfAUOJjcXol5e2jdD2zoBtgnhA7ScYKEu8fR7oEf+Z5w9JSF7
onUwtk2VoGose4IYOAV3+9QDxf4G+ui/BksdTd7jLQD+wEmrkxy3jgQ8ZKo8CY0D
QR4/fJux4F1r8LBFTJT0m0UfTYQI2dPDe32opNoR0Db2Eg6N8ryLydbFoMQclMLe
Q3qav2zsiwL/OOwpYY0vw3o3dGbJCaMpiyUNXCA6pD5k6V9zES212JdDZnxpqOVs
yaH7BWxUkyqLgO/sdVfN1uOoeutAo0luPjH637Us05WBJ3ZLTq8=
=8eCP
-END PGP SIGNATURE End Message ---


Bug#899317: mercurial-git: Breaks with python-dulwich 19.1

2018-10-17 Thread Blake C. Rawlings

For reference, the recently-released version 0.8.12 of hg-git seems to fix this.

Upstream release: https://bitbucket.org/durin42/hg-git/commits/tag/0.8.12

Upstream mailing-list discussion: 
https://groups.google.com/forum/#!topic/hg-git/LLyCmSzf9Fw

Thanks,

Blake



Processed: Bug #909825 in pd-iemlib marked as pending

2018-10-17 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #909825 [src:pd-iemlib] pd-iemlib FTBFS with puredata 0.49.0
Added tag(s) pending.

-- 
909825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#909825: Bug #909825 in pd-iemlib marked as pending

2018-10-17 Thread IOhannes zmölnig
Control: tag -1 pending

Hello,

Bug #909825 in pd-iemlib reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/pd/pd-iemlib/commit/6b99db5b057d349051728a637f035f301fa6dfba


Backported fix for Pd-0.49's API cleanup

Closes: #909825



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909825



Bug#911242: grub-legacy - Fails to install on disk

2018-10-17 Thread Bastian Blank
Package: grub-legacy
Version: 0.97-73
Severity: grave

grub-legacy fails to install a proper bootloader on disk.  Given the not
longer existing usefulness of this package, I intend to request removal
in a short time.

Regards,
Bastian

| # grub-install /dev/sda
| Searching for GRUB installation directory ... found: /boot/grub
| [   23.084254] grub[399]: segfault at ee8 ip 080498b3 sp 
f7936000 error 6 in grub[8048000+2b000]
| [   23.085888] Code: 4f 07 08 8b 00 85 c0 74 0a c7 82 e8 0e 00 00 01 00 00 00 
8b 44 24 0c 8b 80 e4 0e 00 00 89 c4 83 c 
| Segmentation fault
| cmp: EOF on /tmp/gruby39ghn which is empty
| [   24.107637] grub[404]: segfault at ee8 ip 080498b3 sp 
f79d6000 error 6 in grub[8048000+2b000]
| [   24.109688] Code: 4f 07 08 8b 00 85 c0 74 0a c7 82 e8 0e 00 00 01 00 00 00 
8b 44 24 0c 8b 80 e4 0e 00 00 89 c4 83 c 
| Segmentation fault
| cmp: EOF on /tmp/gruby39ghn which is empty
| [   25.122698] grub[409]: segfault at ee8 ip 080498b3 sp 
f7953000 error 6 in grub[8048000+2b000]
| [   25.126343] Code: 4f 07 08 8b 00 85 c0 74 0a c7 82 e8 0e 00 00 01 00 00 00 
8b 44 24 0c 8b 80 e4 0e 00 00 89 c4 83 c 
| Segmentation fault
| cmp: EOF on /tmp/gruby39ghn which is empty
| [   26.137539] grub[414]: segfault at ee8 ip 080498b3 sp 
f790c000 error 6 in grub[8048000+2b000]
| [   26.139834] Code: 4f 07 08 8b 00 85 c0 74 0a c7 82 e8 0e 00 00 01 00 00 00 
8b 44 24 0c 8b 80 e4 0e 00 00 89 c4 83 c 
| Segmentation fault
| cmp: EOF on /tmp/gruby39ghn which is empty
| [   27.153064] grub[419]: segfault at ee8 ip 080498b3 sp 
f795 error 6 in grub[8048000+2b000]
| [   27.154898] Code: 4f 07 08 8b 00 85 c0 74 0a c7 82 e8 0e 00 00 01 00 00 00 
8b 44 24 0c 8b 80 e4 0e 00 00 89 c4 83 c 
| Segmentation fault
| cmp: EOF on /tmp/gruby39ghn which is empty
| The file /boot/grub/stage1 not read correctly.

| # lsblk 
| NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
| sda  8:008G  0 disk 
| `-sda1   8:108G  0 part /
| sr0 11:01 1024M  0 rom  

| # sfdisk -l
| Disk /dev/sda: 8 GiB, 8589934592 bytes, 16777216 sectors
| Units: sectors of 1 * 512 = 512 bytes
| Sector size (logical/physical): 512 bytes / 512 bytes
| I/O size (minimum/optimal): 512 bytes / 512 bytes
| Disklabel type: dos
| Disk identifier: 0xd6aa05a3
| 
| Device Boot Start  End  Sectors Size Id Type
| /dev/sda1  * 2048 16777215 16775168   8G 83 Linux


-- 
Bones: "The man's DEAD, Jim!"



Bug#834298: nis: problem appears to be in invocation in /etc/init.d/nis

2018-10-17 Thread Elimar Riesebieter
* Christoph Terasa  [2018-10-17 11:56 +0200]:

> On Tue, 16 Oct 2018 14:56:57 -0600 Joe Pfeiffer 
> wrote:
> > The problem appears to be in line 172 of /etc/init.d/nis:
> > --exec ${NET}/ypbind -- $broadcast ${YPBINDARGS}
> >
> > If I execute this by hand (for my environment, which does not use
> > -broadcast and has empty YPBINDARGS), ie
> >
> > [...]
> >
> > If I delete the -- from the invocation it works.
> >
> 
> Good find, though the "--" is signaling the end of the start-stop-daemon
> options, and is not an option to ypbind. Options to the daemon (ypbind) come
> after the "--". Since your options to ypbind are empty anyway, it works in
> your case, but it might fail otherwise. This still looks like a
> bug/regression in the ypbind binary to me, not like a bug in the init.d
> script.

According to the changelog of 3.17.1-3

Drop -no-dbus from YPBINDARGS= in /etc/default/nis.
We no longer build nis with NetworkManager/D-Bus support, so setting
this option made ypbind fail to start. (Closes: #906436)

Running ypbind with no options and an empty YPBINDARGS= works here. So this bug
isn't relevant any more. Please confirm.

I am thinking about packaging

libnsl 1.2.0  
libnss_nis 3.0
ypbind-mt 
ypserv 2.5
yp-tools 4.2.2

separately to create clean packages. Whatt do you think?

libtirpc has to be updated to minimum 1.0.2 (not only in experimental!). Any co
maintaining would be great ;-) The packaging of Mark Brown aka broonie is
somewhat, h, old fashioned?  The versions are outdated. Anyway FMPOV not
maintainable.


Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)



Processed: merging 910317 910500

2018-10-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 910500 libqt5webengine5 5.11.1+dfsg-5
Bug #910500 [libqt5quick5] libqt5quick5: Sefault in applications using 
QWebEngineView
Bug reassigned from package 'libqt5quick5' to 'libqt5webengine5'.
No longer marked as found in versions qtdeclarative-opensource-src/5.11.1-6.
Ignoring request to alter fixed versions of bug #910500 to the same values 
previously set
Bug #910500 [libqt5webengine5] libqt5quick5: Sefault in applications using 
QWebEngineView
Marked as found in versions qtwebengine-opensource-src/5.11.1+dfsg-5.
> affects 910500 python3-pyqt5.qtwebengine qutebrowser falkon
Bug #910500 [libqt5webengine5] libqt5quick5: Sefault in applications using 
QWebEngineView
Added indication that 910500 affects python3-pyqt5.qtwebengine, qutebrowser, 
and falkon
> merge 910317 910500
Bug #910317 [libqt5webengine5] QtWebEngine in unstable is constantly crashing
Bug #910500 [libqt5webengine5] libqt5quick5: Sefault in applications using 
QWebEngineView
Merged 910317 910500
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
910317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910317
910500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: add blocking bug for 876905

2018-10-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 876905 by 784479
Bug #876905 [src:qtwebkit] qtwebkit should not be released with buster
876905 was not blocked by any bugs.
876905 was not blocking any bugs.
Added blocking bug(s) of 876905: 784479
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
876905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#784477: [kde4libs] Qt4's WebKit removal

2018-10-17 Thread Ivo De Decker
Hi,

On Fri, Nov 24, 2017 at 04:59:58PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Control: tag -1 patch
> 
> There is patch available for this at  packages.git/tree/trunk/kdelibs-no-kdewebkit.patch?h=packages/kdelibs>
> 
> We might want to wait for the last tandem of KF5 apps though.

Is there anything still blocking this?

kde-runtime (#784477) seems to have a patch and libkdegames-kde4 (#875015) is
no longer in testing.

Cheers,

Ivo



Processed: Re: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

2018-10-17 Thread Debian Bug Tracking System
Processing control commands:

> block 895038 by 895037
Bug #895038 [src:libindicator] libindicator: deprecated in Debian, switch to 
libayatana-indicator instead
895038 was not blocked by any bugs.
895038 was not blocking any bugs.
Added blocking bug(s) of 895038: 895037

-- 
895037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895037
895038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

2018-10-17 Thread Debian Bug Tracking System
Processing control commands:

> block 895038 by 895037
Bug #895038 [src:libindicator] libindicator: deprecated in Debian, switch to 
libayatana-indicator instead
895038 was blocked by: 895037
895038 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #895038 to the same blocks 
previously set

-- 
895038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#895037: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

2018-10-17 Thread Ivo De Decker
Control: block 895038 by 895037

Hi,

On Fri, Apr 06, 2018 at 01:07:39PM +, Mike Gabriel wrote:
> Package: src:libappindicator
> Severity: serious
> 
> The libappindicator package is currently QA team maintained in Debian and
> shall be phased out hopfully during the buster release cycle. The
> alternative (maintained upstream and Debian-downstream) is
> libayatana-appindicator.
> 
> There is a lot of porting work to do (little patches are required for each
> application), to let all AppIndicator aware applications build against the
> new and supported AppIndicator shared lib fork "libayatana-appindicator".
> 
> For details, please see [1]
> 
> For a list of applications that require porting and the porting status, see
> [2]

What's the status of this? Looking at testing, there are still quite a few
packages remaining that (build-)depend on libappindicator:

# Broken Depends:
blueman: blueman
caffeine: caffeine
clipit: clipit
diodon: diodon
gmpc: gmpc
gromit-mpx: gromit-mpx
growl-for-linux: growl-for-linux
gtimelog: gtimelog
gxkb: gxkb
hime: hime
kylin-burner: libburner-media3-1
modem-manager-gui: modem-manager-gui
parcellite: parcellite
psensor: psensor
redshift: redshift-gtk
roger-router: roger-router
solaar: solaar-gnome3

# Broken Build-Depends:
clipit: libappindicator3-dev
diodon: libappindicator3-dev (>= 0.3.0)
gcin: libappindicator3-dev
gmpc: libappindicator-dev
gromit-mpx: libappindicator3-dev
growl-for-linux: libappindicator-dev
gxkb: libappindicator-dev
hime: libappindicator-dev
kylin-burner: libappindicator3-dev (>= 0.0.7)
modem-manager-gui: libappindicator3-dev
parcellite: libappindicator-dev
psensor: libappindicator3-dev
roger-router: libappindicator3-dev
zeal: libappindicator-dev


For libindicator, the list is:

# Broken Depends:
cairo-dock-plug-ins: cairo-dock-alsamixer-plug-in
 cairo-dock-messaging-menu-plug-in
libappindicator: libappindicator1
 libappindicator3-1
lightdm-gtk-greeter: lightdm-gtk-greeter
workrave: workrave

# Broken Build-Depends:
cairo-dock-plug-ins: libindicator3-dev
libappindicator: libindicator-dev (>= 0.3.90)
 libindicator3-dev (>= 0.3.90)
lightdm-gtk-greeter: libindicator3-dev
workrave: libindicator3-dev (>= 0.3.19)



Do you still think it's realistic to get this done before the transition
freeze (2019-01-12)? If not, this should be postponed.

To help the overview of what's still missing, it might be good to add blocking
bugs for every package to this one.

Thanks,

Ivo



Processed: block 909203 with 909837

2018-10-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 909203 with 909837
Bug #909203 {Done: Daniel Kahn Gillmor } [libreswan] 
libreswan: Hardcoded dependency on libunbound2 - stalls unbound transition
909203 was not blocked by any bugs.
909203 was not blocking any bugs.
Added blocking bug(s) of 909203: 909839 and 909837
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
909203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#909846: marked as done (libglib2.0-dev: absolute paths in gio-2.0.pc break reverse dependencies that pass them to AC_PATH_PROG)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 14:44:15 +0100
with message-id <20181017134415.ga30...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#909846: libglib2.0-dev: absolute paths in gio-2.0.pc 
break reverse dependencies
has caused the Debian Bug report #909846,
regarding libglib2.0-dev: absolute paths in gio-2.0.pc break reverse 
dependencies that pass them to AC_PATH_PROG
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
909846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-dev
Version: 2.58.1-1
Severity: serious
Control: affects -1 src:tpm2-abrmd src:playerctl

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tpm2-abrmd.html

...
checking for GOBJECT... yes
checking for SAPI... yes
checking for /usr/bin/gdbus-codegen... no
configure: error: *** gdbus-codegen is required to build tpm2-abrmd


https://gitlab.gnome.org/GNOME/glib/issues/1521 even mentions
that this is known to break at least one reverse dependency.

How on earth could it happen that this was anyhow backported
to a stable branch?
--- End Message ---
--- Begin Message ---
On Thu, 04 Oct 2018 at 23:55:12 +0100, Simon McVittie wrote:
> On Sat, 29 Sep 2018 at 10:22:06 -0400, Jeremy Bicha wrote:
> > I believe we don't consider this a bug in glib2.0.
> 
> It doesn't look as though this is going to be changed upstream, so
> I don't think diverging is a good idea in the long term; and only
> two packages seem to be affected, so fixing those packages seems a
> reasonable short-term solution.

Both are now fixed in testing.

> I'm still trying to get clarification from the GLib upstream maintainers
> on what their recommendation is for Autotools projects

It is basically this:

> PKG_CHECK_VAR([GDBUS_CODEGEN], [gio-2.0], [gdbus_codegen])

which can be overridden with
"./configure GDBUS_CODEGEN=/elsewhere/gdbus-codegen" if required.

smcv--- End Message ---


Processed: notfound 909846 in 2.58.1-1

2018-10-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 909846 2.58.1-1
Bug #909846 [libglib2.0-dev] libglib2.0-dev: absolute paths in gio-2.0.pc break 
reverse dependencies that pass them to AC_PATH_PROG
No longer marked as found in versions glib2.0/2.58.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
909846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#895765: IGV

2018-10-17 Thread Andreas Tille
On Wed, Oct 17, 2018 at 02:09:10PM +0200, Olivier Sallou wrote:
> >> in progress (not uploaded) igv packaging *should* be ok, but needs testing
> > That's a problem for Bio-Linux 9 / Ubuntu 18.04 LTS, because the default
> > is now Java 10 and the only other Java in the standard repo's is Java 8.
> 
> well, in my package env for new igv, I use Java 10, so will nto be a pb

I can confirm that the package now builds also on my side

Unfortunately if I start the package I get the following output:

$ igv   

  
log4j: reset attribute= "false".
log4j: Threshold ="null".
log4j: Retreiving an instance of org.apache.log4j.Logger.
log4j: Setting [org.broad.igv] additivity to [true].
log4j: Level value for org.broad.igv is  [INFO].
log4j: org.broad.igv level set to INFO
log4j: Class name: [org.apache.log4j.ConsoleAppender]
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d{-MM-dd HH:mm:ss} %-5p 
%c{1}:%L - %m%n].
log4j: Adding appender named [console] to category [org.broad.igv].
2018-10-17 14:37:58 INFO  DirectoryManager:179 - IGV Directory: 
/home/andreas/igv
2018-10-17 14:37:59 INFO  Main:155 - Startup  IGV Version user not_set
2018-10-17 14:37:59 INFO  Main:156 - Java 10.0.2
2018-10-17 14:37:59 INFO  DirectoryManager:84 - Fetching user directory...
2018-10-17 14:37:59 INFO  Main:157 - Default User Directory: /home/andreas
2018-10-17 14:38:00 INFO  Main:158 - OS: Linux


2018-10-17 14:38:00 INFO  Main:208 - Unknown version: user
2018-10-17 14:38:00 ERROR DefaultExceptionHandler:49 - Unhandled exception
java.lang.VerifyError: class 
org.broad.igv.util.stream.IGVSeekableBufferedStream overrides final method 
htsjdk.samtools.seekablestream.SeekableStream.mark(I)V
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1009)
at 
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:801)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:699)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:622)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:580)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
at org.broad.igv.ui.Main.open(Main.java:282)
at org.broad.igv.ui.Main$1.run(Main.java:109)
at 
java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
at 
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
at java.desktop/java.awt.EventQueue.access$600(EventQueue.java:97)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:87)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
at 
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at 
java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
2018-10-17 14:38:01 INFO  ShutdownThread:46 - Shutting down


I'm running an up to date testing system.  Here is what reportbug
generates:

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information


Ups, that's a bit less.  H. no idea why that's only so few
information.  Here is a bit more:

$ java --version
openjdk 10.0.2 2018-07-17
OpenJDK Runtime Environment (build 10.0.2+13-Debian-1)
OpenJDK 64-Bit Server VM 

Bug#908433: marked as done (skimage build depends on libjs-twitter-bootstrap that will not be in buster)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 11:53:08 +
with message-id 
and subject line Bug#908433: fixed in skimage 0.14.1-1
has caused the Debian Bug report #908433,
regarding skimage build depends on libjs-twitter-bootstrap that will not be in 
buster
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
908433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skimage
Version: 0.14.0-1
Severity: serious
Control: block 907724 by -1

See #907724 for background.
--- End Message ---
--- Begin Message ---
Source: skimage
Source-Version: 0.14.1-1

We believe that the bug you reported is fixed in the latest version of
skimage, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated skimage package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Oct 2018 11:33:00 +
Source: skimage
Binary: python-skimage python3-skimage python-skimage-doc python-skimage-lib 
python3-skimage-lib
Architecture: source
Version: 0.14.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mo Zhou 
Description:
 python-skimage - Python modules for image processing
 python-skimage-doc - Documentation and examples for scikit-image
 python-skimage-lib - Optimized low-level algorithms for scikit-image
 python3-skimage - Python 3 modules for image processing
 python3-skimage-lib - Optimized low-level algorithms for Python 3 scikit-image
Closes: 902478 902479 902480 906207 908433
Changes:
 skimage (0.14.1-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Mo Zhou ]
   * Fixup testsuite (Closes: #902480).
   * Add new deps to debian/tests/control
   * Allow stderr during autopkgtest, some libraries are
 throwing warnings as errors during autopkgtests.
   * Remove deprecated X-Python*-Version fields.
   * Run dh_auto_tests with xvfb-run.
 .
   [ Yangfl  ]
   * New upstream release (Closes: #906207)
   * d/compat
 - bump debhelper compat to 11
   * d/control
 - remove build dep libjs-twitter-bootstrap (Closes: #908433)
 + build dep python-tk and python3-tk
 + build dep python3-sphinx-gallery and python3-sklearn, required by doc
   building
 + build dep python3-doc and python-matplotlib-doc for intersphinx mappings
 + dep libjs-{bootstrap,jquery,mathjax} for python-skimage-doc
 * bump standard to 4.2.1
   * d/copyright
 - no need to remove bootstrap.min.js, provided in missing-sources
   * d/rules
 - switch from python_distutils to pybuild
 - hotfix broken sphinx build command by passing SPHINXBUILD manually
   (Closes: #902478)
 - replace MathJax.js with local file (Closes: #902479)
   * d/patches
 - remove 0001-BF-perform-computation-serially-with-a-warning-if-da.patch
   and skip-failing-test-on-i386.patch since included in new release
 - add allow-warnings-on-dask.patch to bypass false alert on dask missing
 - remove deb_no_sphinx_galery since python3-sphinx-gallery available
 - add no-download-intersphinx-mapping.patch
Checksums-Sha1:
 b1ec88283f4b397d1c6de0c1c551db8932c5b47f 3151 skimage_0.14.1-1.dsc
 1fb485842ace6787231d15f72fab513b9c67fc65 21883972 skimage_0.14.1.orig.tar.gz
 6aae9f30177309d00fdbd94c4e751ddee808ffd5 22116 skimage_0.14.1-1.debian.tar.xz
 feafcfeee8b7dc298ace6010fa44f2e8a1f75240 12640 
skimage_0.14.1-1_source.buildinfo
Checksums-Sha256:
 08a8b7ce2a1d41865579c5530e5ba661d970553324e08951b13b0d5e4ac538bd 3151 
skimage_0.14.1-1.dsc
 81d25b2c9feb80c32341da4105bc1f4afd6385ce104c8dbb7513527368ba38e9 21883972 
skimage_0.14.1.orig.tar.gz
 86021d76b3f648d74ba245aa9e08e9c1a01b364baba5462d71cc88f02452a14b 22116 
skimage_0.14.1-1.debian.tar.xz
 2d4a9e7b67e9c09337758beabbc1a0a244523a9f0fa5cce1b5f5b7b03815e696 12640 
skimage_0.14.1-1_source.buildinfo
Files:
 b807dbdadbeebc73f969dd86af401777 3151 python optional skimage_0.14.1-1.dsc
 48f9dfa8d920eec0eb2a0eeaec425e07 21883972 python optional 
skimage_0.14.1.orig.tar.gz
 1e40af56c078eef330c425267bbc9fd1 22116 python optiona

Bug#906207: marked as done (skimage FTBFS on 32bit: ValueError: Unexpected warning: overflow encountered in long_scalars)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 11:53:08 +
with message-id 
and subject line Bug#906207: fixed in skimage 0.14.1-1
has caused the Debian Bug report #906207,
regarding skimage FTBFS on 32bit: ValueError: Unexpected warning: overflow 
encountered in long_scalars
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
906207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skimage
Version: 0.14.0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=skimage

...
=== FAILURES ===
 test_spacing_1 

def test_spacing_1():
n = 30
lx, ly, lz = n, n, n
data, _ = make_3d_syntheticdata(lx, ly, lz)

# Rescale `data` along Y axis
# `resize` is not yet 3D capable, so this must be done by looping in 2D.
data_aniso = np.zeros((n, n * 2, n))
for i, yz in enumerate(data):
data_aniso[i, :, :] = resize(yz, (n * 2, n),
 mode='constant',
 anti_aliasing=False)

# Generate new labels
small_l = int(lx // 5)
labels_aniso = np.zeros_like(data_aniso)
labels_aniso[lx // 5, ly // 5, lz // 5] = 1
labels_aniso[lx // 2 + small_l // 4,
 ly - small_l // 2,
 lz // 2 - small_l // 4] = 2

# Test with `spacing` kwarg
# First, anisotropic along Y
with expected_warnings(['"cg" mode' + '|' + SCIPY_EXPECTED]):
labels_aniso = random_walker(data_aniso, labels_aniso, mode='cg',
>spacing=(1., 2., 1.))

../debian/tmp/usr/lib/python2.7/dist-packages/skimage/segmentation/tests/test_random_walker.py:263:
 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python2.7/contextlib.py:24: in __exit__
self.gen.next()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

matching = ['"cg" mode|numpy.linalg.matrix_rank|\\A\\Z']

@contextmanager
def expected_warnings(matching):
"""Context for use in testing to catch known warnings matching regexes

Parameters
--
matching : list of strings or compiled regexes
Regexes for the desired warning to catch

Examples

>>> from skimage import data, img_as_ubyte, img_as_float
>>> with expected_warnings(['precision loss']):
... d = img_as_ubyte(img_as_float(data.coins()))

Notes
-
Uses `all_warnings` to ensure all warnings are raised.
Upon exiting, it checks the recorded warnings for the desired matching
pattern(s).
Raises a ValueError if any match was not found or an unexpected
warning was raised.
Allows for three types of behaviors: `and`, `or`, and `optional` 
matches.
This is done to accomodate different build enviroments or loop 
conditions
that may produce different warnings.  The behaviors can be combined.
If you pass multiple patterns, you get an orderless `and`, where all of 
the
warnings must be raised.
If you use the `|` operator in a pattern, you can catch one of several
warnings.
Finally, you can use `|\A\Z` in a pattern to signify it as optional.

"""
with all_warnings() as w:
# enter context
yield w
# exited user context, check the recorded warnings
remaining = [m for m in matching if '\A\Z' not in m.split('|')]
for warn in w:
found = False
for match in matching:
if re.search(match, str(warn.message)) is not None:
found = True
if match in remaining:
remaining.remove(match)
if not found:
>   raise ValueError('Unexpected warning: %s' % 
> str(warn.message))
E   ValueError: Unexpected warning: overflow encountered in 
long_scalars

../debian/tmp/usr/lib/python2.7/dist-packages/skimage/_shared/_warnings.py:121: 
ValueError
=== warnings summary ===
restoration/tests/test_denoise.py::test_cycle_spinning_multichannel
  
/<>/debian/tmp/usr/lib/python2.7/dist-packag

Bug#904648: marked as done (python3-tweepy: fails to install with Python 3.7)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 11:53:19 +
with message-id 
and subject line Bug#904648: fixed in tweepy 3.6.0-1
has caused the Debian Bug report #904648,
regarding python3-tweepy: fails to install with Python 3.7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
904648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-tweepy
Version: 3.5.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up python3-tweepy (3.5.0-1) ...
File "/usr/lib/python3/dist-packages/tweepy/streaming.py", line 355
  def _start(self, async):
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-tweepy (--configure):
   installed python3-tweepy package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-tweepy=3.5.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tweepy
Source-Version: 3.6.0-1

We believe that the bug you reported is fixed in the latest version of
tweepy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sophie Brun  (supplier of updated tweepy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Oct 2018 15:09:28 +0200
Source: tweepy
Binary: python-tweepy python3-tweepy python-tweepy-doc
Architecture: source
Version: 3.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sophie Brun 
Description:
 python-tweepy - Twitter library for Python
 python-tweepy-doc - Documentation for python-tweepy module
 python3-tweepy - Twitter library for Python 3
Closes: 904648
Changes:
 tweepy (3.6.0-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
 .
   [ Sophie Brun ]
   * New upstream version 3.6.0
   * Import upstream patches for Python3.7 (Closes: #904648)
   * d/rules: remove get-orig-source
   * Bump Standards-Version to 4.2.1
   * Add autopkgtest-pkg-python
   * Clean d/rules
   * Use pybuild to install the package
   * Install examples
Checksums-Sha1:
 c046cd3a06d8df07e748e6ea5cd7e36310e3760c 2007 tweepy_3.6.0-1.dsc
 2827e0971123522b275d8ff90b2b5394d766bbed 426906 tweepy_3.6.0.orig.tar.gz
 50bd26868695d63eb4fffdd5c2061eb0b0865c25 5284 tweepy_3.6.0-1.debian.tar.xz
 bcb4e9bca7d8ae0cc8e0938f669a3799ba311499 7859 tweepy_3.6.0-1_source.buildinfo
Checksums-Sha256:
 8a2c4d89664bc308a9900babfb7fe787dd7b8d808fb3b53033d02e54524e2058 2007 
tweepy_3.6.0-1.dsc
 70f0c02b6249a3a7551328f731f1b90c822a780eb2fd15eaef4510a477c9f33c 426906 
tweepy_3.6.0.orig.tar.gz
 f24e610a8793bc3257466b781a0982f453596928fd87f7db16c38571df093e49 5284 
tweepy_3.6.0-1.debian.tar.xz
 4b06440e14f04b645130ccf166b42f8c760611bcfc96adc47ff379cc026cdece 7859 
tweepy_3.6.0-1_source.buildinfo
Files:
 7a8bf078a3fd94ef682c106cab1a1b45 2007 python optional tweepy_3.6.0-1.dsc
 4de9d17b29ba2296f9ded11886954165 426906 python optional 
tweepy_3.6.0.orig.tar.gz
 80a44e67c1bd55d89e6732a145e9da57 5284 python optional 
tweepy_3.6.0-1.debian.tar.xz
 8070d688b3867c887e5b4d3894583247 7859 python optional 
tweepy_3.6.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAlvHH20ACgkQA4gdq+vC
mrnOFAf/VdyPMnj++nMwOrEU1TKk4S8s0/n3YrWZpE8xIKDqOZF6BI7d

Bug#909995: marked as done (Clean LyX install fails to configure correctly)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 11:50:37 +
with message-id 
and subject line Bug#909995: fixed in lyx 2.3.1-2-2
has caused the Debian Bug report #909995,
regarding Clean LyX install fails to configure correctly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
909995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sdcc
Version: 3.7.0+dfsg2-0.1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh_testdir
mkdir -p /<>/sdcc-3.7.0+dfsg2/build
touch sim/ucsim/config.guess sim/ucsim/config.sub
dh_autotools-dev_updateconfig
dh_autotools-dev_updateconfig: dh_autotools-dev_updateconfig is deprecated; 
please see dh_autotools-dev_updateconfig(1) for a replacement
dh_autotools-dev_updateconfig: This feature will be removed in compat 12.
for c_g in `find -type f -name config.guess` ; do if ! test -e 
"$c_g.dh-orig" ; then mv -f "$c_g" "$c_g.dh-orig" ; cp -f 
/usr/share/misc/config.guess "$c_g" ; fi ; done
for c_s in `find -type f -name config.sub`   ; do if ! test -e 
"$c_s.dh-orig" ; then mv -f "$c_s" "$c_s.dh-orig" ; cp -f 
/usr/share/misc/config.sub   "$c_s" ; fi ; done
CFLAGS="-g -O2 -fdebug-prefix-map=/<>/sdcc-3.7.0+dfsg2=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>/sdcc-3.7.0+dfsg2=. -fstack-protector-strong 
-Wformat -Werror=format-security" LDFLAGS="-Wl,-z,relro" \
./configure \
--host=x86_64-linux-gnu \
--build=x86_64-linux-gnu \
--disable-non-free \

[... snipped ...]



LaTeX Warning: Reference `subsec:External-Stack' on page 35 undefined on input 
line 2114.

[35] [36]

LaTeX Warning: Reference `subsec:The-anatomy-of' on page 37 undefined on input 
line 2229.


Underfull \hbox (badness 1) in paragraph at lines 2247--2256


LaTeX Warning: Reference `subsec:Install-paths' on page 37 undefined on input l
ine 2272.


LaTeX Warning: Reference `subsec:Search-Paths' on page 37 undefined on input li
ne 2274.


LaTeX Warning: Reference `subsec:Search-Paths' on page 37 undefined on input li
ne 2276.

[37]

! LaTeX Error: File `MCS51_named' not found.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...  
  
l.2298 \includegraphics{MCS51_named}

? 
! Emergency stop.
 ...  
  
l.2298 \includegraphics{MCS51_named}

Output written on sdccman.dvi (37 pages, 181596 bytes).
Transcript written on sdccman.log.
make[1]: *** [Makefile:67: sdccman.dvi] Error 1
make[1]: Leaving directory '/<>/sdcc-3.7.0+dfsg2/doc'
make: *** [debian/rules:71: build-indep-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sdcc.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: lyx
Source-Version: 2.3.1-2-2

We believe that the bug you reported is fixed in the latest version of
lyx, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated lyx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 17 Oct 2018 13:23:14 +0200
Source: lyx
Binary: lyx lyx-common fonts-lyx
Architec

Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))

2018-10-17 Thread Andrius Merkys
Hi Andreas,

On 10/16/18 5:03 PM, Andreas Tille wrote:
> Very good.  Let me know if I could be of any help (which basically would
> boil down to testing and if needed sponsoring).

Many thanks! I will turn to you once I get the updated package build.

> Interesting.  You might like to join the Debian Med sprint in March 2019
> which will happen in Vilnius[1] (no better details yet).

Thanks, I will be there.

Best,
Andrius

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania



Bug#878800: marked as done (jgit-cli: IllegalStateException: Cannot set value to a final field 'org.eclipse.jgit.pgm.Daemon.enable')

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 10:52:16 +
with message-id 
and subject line Bug#878800: fixed in jgit 3.7.1-6
has caused the Debian Bug report #878800,
regarding jgit-cli: IllegalStateException: Cannot set value to a final field 
'org.eclipse.jgit.pgm.Daemon.enable'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
878800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jgit-cli
Version: 3.7.1-4
Tags: upstream patch fixed-upstream
Severity: important
Justification: renders feature unusable

Steps to reproduce:

 git clone https://kernel.googlesource.com/pub/scm/git/git
 cd git
 make -j8
 cd t
 ./t5512-ls-remote.sh -v -i

Expected result:
 test passes

Actual result:
 java.lang.IllegalStateException: Cannot set value to a final field 
'org.eclipse.jgit.pgm.Daemon.enable'.
at org.kohsuke.args4j.spi.Setters.create(Setters.java:32)
at org.kohsuke.args4j.ClassParser.parse(ClassParser.java:34)
at org.kohsuke.args4j.CmdLineParser.(CmdLineParser.java:96)
at org.kohsuke.args4j.CmdLineParser.(CmdLineParser.java:71)
at org.eclipse.jgit.pgm.opt.CmdLineParser.(CmdLineParser.java:119)
at org.eclipse.jgit.pgm.opt.CmdLineParser.(CmdLineParser.java:102)
at org.eclipse.jgit.pgm.TextBuiltin.parseArguments(TextBuiltin.java:224)
at org.eclipse.jgit.pgm.TextBuiltin.execute(TextBuiltin.java:208)
at org.eclipse.jgit.pgm.Main.execute(Main.java:223)
at org.eclipse.jgit.pgm.Main.run(Main.java:124)
at org.eclipse.jgit.pgm.Main.main(Main.java:98)

Fixed upstream by v4.9.0.201710071750-r~33 (Remove final modifier on args4j
option or argument fields, 2017-09-04, https://git.eclipse.org/r/104304).

I suspect this was triggered by an args4j update.  Once jgit is updated,
can args4j get a Breaks to force upgrades?

Thanks,
Jonathan
--- End Message ---
--- Begin Message ---
Source: jgit
Source-Version: 3.7.1-6

We believe that the bug you reported is fixed in the latest version of
jgit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 878...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated jgit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Oct 2018 12:11:32 +0200
Source: jgit
Binary: libjgit-java libjgit-ant-java libjgit-java-doc jgit-cli
Architecture: source
Version: 3.7.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 jgit-cli   - Java implementation of GIT version control (command line interfac
 libjgit-ant-java - Java implementation of GIT version control (Ant interface)
 libjgit-java - Java implementation of GIT version control
 libjgit-java-doc - Java implementation of GIT version control (documentation)
Closes: 878800
Changes:
 jgit (3.7.1-6) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the compatibility with args4j 2.32 (Closes: #878800)
   * Standards-Version updated to 4.2.1
Checksums-Sha1:
 025ed9eb874b252eaafcf06c12aab1a96e3c5b02 2445 jgit_3.7.1-6.dsc
 05a79cf08ac4283b83f02dd31a9cb6430d71e48a 10944 jgit_3.7.1-6.debian.tar.xz
 9b3b1d3faf2310a70704b42e793919fd0a2d3ce1 16306 jgit_3.7.1-6_source.buildinfo
Checksums-Sha256:
 c7de8e754993e59ed845a2d6cb41673895c6d5af40959273caa8a4548c61caa7 2445 
jgit_3.7.1-6.dsc
 04d6c34849932439bffdf43d58824065d7bab54448979df10f43d2d9b26ad3dc 10944 
jgit_3.7.1-6.debian.tar.xz
 66b857f00a427196fe164fa065e8cb27188d361b63839f557d9b11dee92b10f2 16306 
jgit_3.7.1-6_source.buildinfo
Files:
 c5ee4f3a1c1eee242458c06de259b2fb 2445 java optional jgit_3.7.1-6.dsc
 0dcbde044be60b45efcb71338fef8809 10944 java optional jgit_3.7.1-6.debian.tar.xz
 062e2fcf91f3e04aa091b9a195e64d90 16306 java optional 
jgit_3.7.1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlvHEBYSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsBqUQALqV0lT7+9WTZ8v9TCnSpXNxAG/YvBRQ
r/PCj6bDg1gez1cX9HfonWORIFyVuKkno79xTesQXMIV3T2Nz/Zz2H+4193fcnlh
gNW+3DerrnWysZkAUZ1Y02Ayh2PDBh9G5iyJ14F2QvJF8HpUeaksuh2fk+J9uyP

Bug#911226: lttoolbox: FTBFS on several architectures: test failures

2018-10-17 Thread Emilio Pozuelo Monfort
Source: lttoolbox
Version: 3.5.0-2
Severity: serious
Tags: ftbfs

There are several test failures on various architectures, e.g.:

FAIL: runTest (lt_proc.PrintWeightsNegative)
--
Traceback (most recent call last):
  File "/<>/tests/proctest.py", line 71, in runTest
exp+"[][\n]")
AssertionError: u'^cat/cat+n/cat+v$[][\n]' != 
u'^cat/cat+n/cat+v$[][\n]'
- ^cat/cat+n/cat+v$[][
+ ^cat/cat+n/cat+v$[][
  ]


FAIL: runTest (lt_print.NegativeWeightedFst)
--
Traceback (most recent call last):
  File "/<>/tests/printtest.py", line 62, in runTest
self.assertEqual(self.communicateFlush(), self.expectedOutput)
AssertionError: 
u'0\t1\tc\tc\t4.567895\t\n1\t2\ta\ta\t0.989532\t\n2\t3\tt\tt\t2.796193\t\n3\t4\t
 [truncated]... != 
u'0\t1\tc\tc\t4.567895\t\n1\t2\ta\ta\t0.989532\t\n2\t3\tt\tt\t2.796193\t\n3\t4\t
 [truncated]...
  0 1   c   c   4.567895
  1 2   a   a   0.989532
  2 3   t   t   2.796193
- 3 4   \u03b5  +   0.00
+ 3 4   \u03b5  +   -0.824564   
  4 5   \u03b5  n   1.824564
  4 5   \u03b5  v   2.856296
- 5 0.00
+ 5 -0.525487


Full logs: https://buildd.debian.org/status/package.php?p=lttoolbox

Emilio



Processed: Bug #878800 in eclipse-jgit marked as pending

2018-10-17 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #878800 [jgit-cli] jgit-cli: IllegalStateException: Cannot set value to a 
final field 'org.eclipse.jgit.pgm.Daemon.enable'
Added tag(s) pending.

-- 
878800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#878800: Bug #878800 in eclipse-jgit marked as pending

2018-10-17 Thread Emmanuel Bourg
Control: tag -1 pending

Hello,

Bug #878800 in eclipse-jgit reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/java-team/eclipse-jgit/commit/d63971f5f98a03a483f9a9dba4fc50f55cce2bb6


Fixed the compatibility with args4j 2.32 (Closes: #878800)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/878800



Bug#899240: d-i blank screen on uefi boot

2018-10-17 Thread Dr. Peter J. Bauer


Dear Maintainer,

this problem may be related to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909310

I could solve my problem by setting "Above 4GB mapping" (in the BIOS's 
PCI settings) to "disabled" (following advice from Fujitsu Tech Support).


Best Regards,

   Peter

--
---
Dr. Peter J. Bauer  Universitaet Frankfurt a.M.
Institut fuer Mathematik
Tel. 069/798-23694  Robert-Mayer-Str. 10
Fax  069/798-23674  60325 Frankfurt/Main
---



smime.p7s
Description: S/MIME Cryptographic Signature


Bug#834298: nis: problem appears to be in invocation in /etc/init.d/nis

2018-10-17 Thread Christoph Terasa
On Tue, 16 Oct 2018 14:56:57 -0600 Joe Pfeiffer 
 wrote:

> The problem appears to be in line 172 of /etc/init.d/nis:
> --exec ${NET}/ypbind -- $broadcast ${YPBINDARGS}
>
> If I execute this by hand (for my environment, which does not use
> -broadcast and has empty YPBINDARGS), ie
>
> [...]
>
> If I delete the -- from the invocation it works.
>

Good find, though the "--" is signaling the end of the start-stop-daemon 
options, and is not an option to ypbind. Options to the daemon (ypbind) 
come after the "--". Since your options to ypbind are empty anyway, it 
works in your case, but it might fail otherwise. This still looks like a 
bug/regression in the ypbind binary to me, not like a bug in the init.d 
script.



Christoph



Bug#897726: marked as done (courier-unicode: ftbfs with GCC-8)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 09:49:18 +
with message-id 
and subject line Bug#897726: fixed in courier-unicode 2.1-1
has caused the Debian Bug report #897726,
regarding courier-unicode: ftbfs with GCC-8
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
897726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:courier-unicode
Version: 2.0-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/courier-unicode_2.0-2_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
libtool: install: /usr/bin/install -c .libs/libcourier-unicode.so.4.0.0 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcourier-unicode.so.4.0.0
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libcourier-unicode.so.4.0.0 libcourier-unicode.so.4 || { rm -f 
libcourier-unicode.so.4 && ln -s libcourier-unicode.so.4.0.0 
libcourier-unicode.so.4; }; })
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libcourier-unicode.so.4.0.0 libcourier-unicode.so || { rm -f 
libcourier-unicode.so && ln -s libcourier-unicode.so.4.0.0 
libcourier-unicode.so; }; })
libtool: install: /usr/bin/install -c .libs/libcourier-unicode.lai 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcourier-unicode.la
libtool: install: /usr/bin/install -c .libs/libcourier-unicode.a 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcourier-unicode.a
libtool: install: chmod 644 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcourier-unicode.a
libtool: install: ranlib 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcourier-unicode.a
libtool: warning: remember to run 'libtool --finish /usr/lib/x86_64-linux-gnu'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/aclocal'
 /usr/bin/install -c -m 644 m4/courier-unicode.m4 
'/<>/debian/tmp/usr/share/aclocal'
 /bin/mkdir -p '/<>/debian/tmp/usr/include'
 /usr/bin/install -c -m 644 courier-unicode.h courier-unicode-categories-tab.h 
courier-unicode-script-tab.h '/<>/debian/tmp/usr/include'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man3'
 /usr/bin/install -c -m 644 ./man/unicode::iconvert::convert.3 
./man/unicode::iconvert::convert_tocase.3 ./man/unicode::iconvert::fromu.3 
./man/unicode::iconvert::tou.3 ./man/unicode::iso_8859_1.3 
./man/unicode::linebreak_callback_base.3 
./man/unicode::linebreak_callback_save_buf.3 ./man/unicode::linebreak_iter.3 
./man/unicode::linebreakc_callback_base.3 ./man/unicode::linebreakc_iter.3 
./man/unicode::tolower.3 ./man/unicode::toupper.3 ./man/unicode::ucs_2.3 
./man/unicode::ucs_4.3 ./man/unicode::utf_8.3 
./man/unicode::wordbreak_callback_base.3 ./man/unicode_category_lookup.3 
./man/unicode_convert.3 ./man/unicode_convert_deinit.3 
./man/unicode_convert_fromu_init.3 ./man/unicode_convert_fromu_tobuf.3 
./man/unicode_convert_fromutf8.3 ./man/unicode_convert_init.3 
./man/unicode_convert_tobuf.3 ./man/unicode_convert_tocase.3 
./man/unicode_convert_tocbuf_fromutf8_init.3 
./man/unicode_convert_tocbuf_init.3 ./man/unicode_convert_tocbuf_toutf8_init.3 
./man/unicode_convert_tou_init.3 ./man/unic
 ode_convert_tou_tobuf.3 ./man/unicode_convert_toutf8.3 
./man/unicode_convert_uc.3 ./man/unicode_default_chset.3 
./man/unicode_grapheme_break.3 ./man/unicode_html40ent_lookup.3 
./man/unicode_isalnum.3 ./man/unicode_isalpha.3 ./man/unicode_isblank.3 
./man/unicode_isdigit.3 ./man/unicode_isgraph.3 
'/<>/debian/tmp/usr/share/man/man3'
 /usr/bin/install -c -m 644 ./man/unicode_islower.3 ./man/unicode_ispunct.3 
./man/unicode_isspace.3 ./man/unicode_isupper.3 ./

Processed: Re: transgui: Crashes when opening

2018-10-17 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #906638 [transgui] transgui: Crashes when opening
Severity set to 'important' from 'grave'
> tags -1 + unreproducible moreinfo
Bug #906638 [transgui] transgui: Crashes when opening
Added tag(s) unreproducible and moreinfo.

-- 
906638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#906638: transgui: Crashes when opening

2018-10-17 Thread Graham Inggs

Control: severity -1 important
Control: tags -1 + unreproducible moreinfo

Hi Michael

Thank you for your bug report.  I am unable to reproduce your problem. 
Transgui works fine on the systems where I have tried it.


Looking at the log you attached, I see the same Gtk-CRITICAL messages, 
but do not see anything similar to the following two lines:


Gtk-Message: 22:07:28.310: Failed to load module "gail"

** (transgui:29889): WARNING **: 22:07:28.329: 
(../atk-adaptor/bridge.c:993):atk_bridge_adaptor_init: runtime check 
failed: (root)


Do you have the libatk-adaptor and libgail-common packages installed?

Regards
Graham



Bug#911061: marked as done (ukui-control-center depends on nonexisting package gnome-control-center-faces)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 09:22:49 +
with message-id 
and subject line Bug#911061: fixed in ukui-control-center 1.1.6-2
has caused the Debian Bug report #911061,
regarding ukui-control-center depends on nonexisting package 
gnome-control-center-faces
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
911061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ukui-control-center
Version: 1.1.6-1
Severity: serious

The following packages have unmet dependencies:
 ukui-control-center : Depends: gnome-control-center-faces but it is not 
installable
--- End Message ---
--- Begin Message ---
Source: ukui-control-center
Source-Version: 1.1.6-2

We believe that the bug you reported is fixed in the latest version of
ukui-control-center, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
handsome_feng  (supplier of updated 
ukui-control-center package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 17 Oct 2018 14:04:33 +0800
Source: ukui-control-center
Binary: ukui-control-center
Architecture: source
Version: 1.1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team 
Changed-By: handsome_feng 
Description:
 ukui-control-center - utilities to configure the UKUI desktop
Closes: 911061
Changes:
 ukui-control-center (1.1.6-2) unstable; urgency=medium
 .
   * Debian/control:
 + Drop gnome-control-center-face. (Closes: #911061)
Checksums-Sha1:
 1fc31c0e61c879a83a2294ae2a68419e325b1a6b 2571 ukui-control-center_1.1.6-2.dsc
 d92d88ff6ff349ecac006ffc7726419ddc868dae 5264 
ukui-control-center_1.1.6-2.debian.tar.xz
 e17278638d3d0ce48c459e2575af9d0865268398 16512 
ukui-control-center_1.1.6-2_source.buildinfo
Checksums-Sha256:
 e2c807d7366344ca40b854ecfc763bd3dc38fb717599ec4aeae58bb6f8959160 2571 
ukui-control-center_1.1.6-2.dsc
 e4893c4147f9340ca3533e008f19046d32c08313fb5000b1e7a6b9b8fc060a79 5264 
ukui-control-center_1.1.6-2.debian.tar.xz
 0a91363de98b2adc1fe0e8730fcf5e80d976ea7d08b1dc5af5625a13931e752c 16512 
ukui-control-center_1.1.6-2_source.buildinfo
Files:
 ac9658ffd218991617b8b0c225f3e46e 2571 x11 optional 
ukui-control-center_1.1.6-2.dsc
 a208f11284fdbfc7c34851fd6199f0db 5264 x11 optional 
ukui-control-center_1.1.6-2.debian.tar.xz
 33d333da5d05c91bd6249b5b99372b5b 16512 x11 optional 
ukui-control-center_1.1.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAlvG+tkACgkQ808JdE6f
Xdn/qQ//W8+8xDCykpg+HF1x4cTn1lWS07PSIU+sNKEZyJy/VPEq43gawLa2jKt2
tCJrXZusTrOwg2s7q5ZDO9R6Hb0ehLtK3ZnLo/ZGF6BOJN6SFsmIXubdinPdMpEN
j/2pxsd8p/Bu7vSLSpTl3Yla6tpAl/jK8nAX8wa3dMNa65HetNntod7q1y7MamL8
hXY4ZDl45iNBocTkiQ9JZuc9gmogheTf9Nn8vaj/wjGNPaCqYy6tBMMi6n7RL+8S
sGgB1fwoUWE77CLpK6ojfNmzaPi3Vqfo4RNWfUF+hURzLfhu+LFQtcJG3OJMm+S1
7P6iie3fKpaUbqK6u+umEOkjp+uuaTZhVRpbfv+q6830si1BWspLzLFUTG0mxm/j
YR/uER604FiDM5K6fURTTbpfOPEE+yE8/Qv5wHDZbcgdEm0ulk/vv2M26VAPgxS+
YQbKLQx0W+B/jqiN6uYjk5U8eLU1w2mXkWPynJvT2Dt20iyFwMm8B8Jx6u2DrYKz
SQZfNBjHZpR5mNpDvaSqAMOo66Chvd0ZsPatRqfBe9Ji8CV5wsTyCmzEBesdVB2Q
poLyl1SHtH/kcrKdSCyJU0GRZE3gm62Clrq5LZ3mEwQ4kt+EVfSyeS+jJdTYmwsd
sjXGTKQfLM/pSjsdu0uLBeKJje31jxhQAD++I2ZbByn7RLUGMZc=
=lEtC
-END PGP SIGNATURE End Message ---


Bug#911221: mysql-5.7: Security fixes from the October 2018 CPU

2018-10-17 Thread Salvatore Bonaccorso
Source: mysql-5.7
Version: 5.7.23-2
Severity: grave
Tags: security upstream

Hi

Details at
https://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html#AppendixMSQL

Regards,
Salvatore



Bug#910665: FTBFS on Debian sid

2018-10-17 Thread Jose Gutierrez de la Concha
On Wed, Oct 17, 2018 at 8:09 AM Chris Knadle 
wrote:

> I'm looking at the build logs of the build failure, and I see that
> zeroc-ice
> 3.7.1-2 from June built correctly, but the 3.7.1-2+b1 binNMU fails to
> build.
>
>https://buildd.debian.org/status/logs.php?pkg=zeroc-ice&arch=amd64
>
> I'm trying to figure out: which source dependency was uploaded such that a
> binNMU was triggered?
>
> The build error happens when building within a python-3 directory, so I'm
> guessing this issue is python3 related.
>

Hi,

I think might be related to a GCC update that now is emitting this
warning,  we are looking at
this and I will  upload a new version with a patch shortly.

Cheers,
José

>
>-- Chris
>
> --
> Chris Knadle
> chris.kna...@coredump.us
>
>

-- 
José Gutiérrez de la Concha
ZeroC, Inc.


Bug#889597: marked as done (libtirpc: FTBFS: xdr_sizeof.c:93:13: error: 'uintptr_t' undeclared)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 09:03:57 +
with message-id 
and subject line Bug#889597: fixed in libtirpc 1.1.4-0.1
has caused the Debian Bug report #889597,
regarding libtirpc: FTBFS: xdr_sizeof.c:93:13: error: 'uintptr_t' undeclared
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
889597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtirpc
Version: 1.0.2-0.2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

libtirpc/experimental recently started to FTBFS:

/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
-I../tirpc -include config.h -DPORTMAP -DINET6 -D_GNU_SOURCE -Wall -pipe 
-Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_RPCSEC_GSS -isystem /us
r/include/mit-krb5 -g -O2 -fdebug-prefix-map=/build/libtirpc-1.0.2=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
libtirpc_la-xdr_sizeof.lo `test -f 'xdr_sizeof.c' || echo './'`xdr_sizeof.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../tirpc -include config.h 
-DPORTMAP -DINET6 -D_GNU_SOURCE -Wall -pipe -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_RPCSEC_GSS -isystem /usr/include/mit-krb5 -g -O2 -fde
bug-prefix-map=/build/libtirpc-1.0.2=. -fstack-protector-strong -Wformat 
-Werror=format-security -c xdr_sizeof.c  -fPIC -DPIC -o 
.libs/libtirpc_la-xdr_sizeof.o
xdr_sizeof.c: In function 'x_inline':
xdr_sizeof.c:93:13: error: 'uintptr_t' undeclared (first use in this function); 
did you mean '__intptr_t'?
  if (len < (uintptr_t)xdrs->x_base) {
 ^
 __intptr_t
xdr_sizeof.c:93:13: note: each undeclared identifier is reported only once for 
each function it appears in
xdr_sizeof.c:93:23: error: expected ')' before 'xdrs'
  if (len < (uintptr_t)xdrs->x_base) {
   ^~~~
xdr_sizeof.c:105:38: error: expected ';' before 'len'
   xdrs->x_base = (caddr_t)(uintptr_t)len;
  ^~~
xdr_sizeof.c:109:1: warning: control reaches end of non-void function 
[-Wreturn-type]
 }
 ^
Makefile:977: recipe for target 'libtirpc_la-xdr_sizeof.lo' failed
make[3]: *** [libtirpc_la-xdr_sizeof.lo] Error 1


Andreas


libtirpc_1.0.2-0.2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libtirpc
Source-Version: 1.1.4-0.1

We believe that the bug you reported is fixed in the latest version of
libtirpc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 889...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated libtirpc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Oct 2018 18:10:57 +0200
Source: libtirpc
Binary: libtirpc-dev libtirpc3 libtirpc-common
Architecture: source all amd64
Version: 1.1.4-0.1
Distribution: experimental
Urgency: medium
Maintainer: Anibal Monsalve Salazar 
Changed-By: Laurent Bigonville 
Description:
 libtirpc-common - transport-independent RPC library - common files
 libtirpc-dev - transport-independent RPC library - development files
 libtirpc3  - transport-independent RPC library
Closes: 884029 889597
Changes:
 libtirpc (1.1.4-0.1) experimental; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release (Closes: #889597)
 - Drop d/p/10-CVE-2016-4429.diff: Fixed upstream
   * debian/watch: Update the URL to point to sourceforge
   * debian/control: Bump Standards-Version to 4.2.1 (no further changes)
   * debian/control: Downgrade priority to optional to please lintian
   * debian/control: Remove duplicate Section/Priority to please lintian
   * Create a new libtirpc-common package and move /etc/netconfig and
 netconfig.5 to it, do not conflit with libtirpc1 to ease the
 co-installation of libtirpc1 and libtirpc3 (Closes: #884029)
Checksums-Sha1:
 57a41bcaf4f0311c55fd41f192a7c68e468b604d 1605 libtirpc_1.1.4-0.1.dsc
 d85717035cb9bd6c45557a1eb1351d3af9a69ff7 510924 libtirpc_1.1.4.orig.tar.bz2
 22811c4688eedcbd9d84486dd1fa31d96b45f160 13788 libtirpc_1.1.4-0.1.debian.tar.xz
 cd968947e719b41b217e573800cb276c9

Bug#910974: marked as done (utidylib: FTBFS with new tidy-html5 5.7.16: Build-dep list needs updating, test fails (upstream behaviour change))

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 09:04:10 +
with message-id 
and subject line Bug#910974: fixed in utidylib 0.4-1
has caused the Debian Bug report #910974,
regarding utidylib: FTBFS with new tidy-html5 5.7.16: Build-dep list needs 
updating, test fails (upstream behaviour change)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
910974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: utidylib
Severity: serious
Version: 0.3-1
X-Debbugs-CC: ni...@debian.org

Dear utidylib maintainers,

Currrent utidylib 0.3-1 is not compatible with new tidy-html5.
New tidy-html5 renamed libtidy5 to libtidy5.6, thus it is necessary to
add libtidy5.6 into build-dependency and dependency alternatives.

After fixing that, there is also another problem that lies in a test:

running build_ext
test_bad_options (tidy.test_tidy.TidyTestCase) ... ok
test_big (tidy.test_tidy.TidyTestCase) ... ok
test_encodings (tidy.test_tidy.TidyTestCase) ... ok
test_error_lines (tidy.test_tidy.TidyTestCase) ... ok
test_errors (tidy.test_tidy.TidyTestCase) ... ok
test_missing_load (tidy.test_tidy.TidyTestCase) ... ok
test_nonexisting (tidy.test_tidy.TidyTestCase) ... FAIL
test_options (tidy.test_tidy.TidyTestCase) ... ok
test_parse (tidy.test_tidy.TidyTestCase) ... ok
test_write (tidy.test_tidy.TidyTestCase) ... ok

==
FAIL: test_nonexisting (tidy.test_tidy.TidyTestCase)
--
Traceback (most recent call last):
  File "/<>/tidy/test_tidy.py", line 52, in test_nonexisting
self.assertEquals(str(doc), '')
AssertionError: '\n' != u''

Besides that assertion error, the following several lines would also
have assertion errors. I figured out that it was due to a behaviour
change introduced in tidy-html5 5.5.19 (ce105dcf) that upstream now
emits FILE_NOT_FILE message instead of FILE_CANT_OPEN when the input
file does not exist.

Please consider fixing the test suite to fit the behaviour of new
tidy-html5 or disable this test.

Thanks!

--
Regards,
Boyuan Yang
--- End Message ---
--- Begin Message ---
Source: utidylib
Source-Version: 0.4-1

We believe that the bug you reported is fixed in the latest version of
utidylib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michal Čihař  (supplier of updated utidylib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Oct 2018 15:15:15 +0200
Source: utidylib
Binary: python-utidylib python3-utidylib
Architecture: source all
Version: 0.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michal Čihař 
Description:
 python-utidylib - Python wrapper for TidyLib
 python3-utidylib - Python wrapper for TidyLib
Closes: 910974
Changes:
 utidylib (0.4-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/control: Remove trailing whitespaces
 .
   [ Michal Čihař ]
   * New upstream release.
 - Fixes operation with recent html-tidy (Closes: #910974).
 - Adds support for Python 3.
   * Build Python 3 version of the library.
   * Add libtidy5.6 to dependencies.
Checksums-Sha1:
 cf72510f0bee5d0127a9384428b22c6f9ba2ad43 2149 utidylib_0.4-1.dsc
 ce9bc61e8f3a42e2ca1b4b4beb18b9111a2f814b 14402 utidylib_0.4.orig.tar.bz2
 16e7ff6d2f8a739002f499e50ff99f090c05a659 3660 utidylib_0.4-1.debian.tar.xz
 9b53c87bcf02e706c7d42bf47512ae2e43b04b2e 10872 python-utidylib_0.4-1_all.deb
 abadeac844e0970f278703851af0e19b8c21fd5e 9904 python3-utidylib_0.4-1_all.deb
 967eef5383fb3a6521130327b64847c61c81fc7f 7139 utidylib_0.4-1_amd64.buildinfo
Checksums-Sha256:
 ddb9c014092c8fbc18bef8b64b8555cde053dd5e3770cfaaac8290a6d1d50299 2149 
utidylib_0.4-1.dsc
 424a79007c3c326950c560bade422af13ce57a0ba88c9171690150c93429fc90 14402 
utidylib_0.4.orig.tar.bz2
 edaaf5db9fd52540fc2c03814d2cbba9beb52787217638380f07af0f54fc7b00 3660 
utidylib_0.4-1.debian.tar.xz
 4b16f60b2a27f520307538364d6755039100

Bug#884029: marked as done (libtirpc3: fails to upgrade from 'sid' - trying to overwrite /etc/netconfig)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 09:03:57 +
with message-id 
and subject line Bug#884029: fixed in libtirpc 1.1.4-0.1
has caused the Debian Bug report #884029,
regarding libtirpc3: fails to upgrade from 'sid' - trying to overwrite 
/etc/netconfig
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
884029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtirpc3
Version: 1.0.2-0.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libtirpc3:amd64.
  Preparing to unpack .../libtirpc3_1.0.2-0.2_amd64.deb ...
  Unpacking libtirpc3:amd64 (1.0.2-0.2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libtirpc3_1.0.2-0.2_amd64.deb (--unpack):
   trying to overwrite '/etc/netconfig', which is also in package 
libtirpc1:amd64 0.2.5-1.2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libtirpc3_1.0.2-0.2_amd64.deb


cheers,

Andreas


libtirpc1=0.2.5-1.2_libtirpc3=1.0.2-0.2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libtirpc
Source-Version: 1.1.4-0.1

We believe that the bug you reported is fixed in the latest version of
libtirpc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated libtirpc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Oct 2018 18:10:57 +0200
Source: libtirpc
Binary: libtirpc-dev libtirpc3 libtirpc-common
Architecture: source all amd64
Version: 1.1.4-0.1
Distribution: experimental
Urgency: medium
Maintainer: Anibal Monsalve Salazar 
Changed-By: Laurent Bigonville 
Description:
 libtirpc-common - transport-independent RPC library - common files
 libtirpc-dev - transport-independent RPC library - development files
 libtirpc3  - transport-independent RPC library
Closes: 884029 889597
Changes:
 libtirpc (1.1.4-0.1) experimental; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release (Closes: #889597)
 - Drop d/p/10-CVE-2016-4429.diff: Fixed upstream
   * debian/watch: Update the URL to point to sourceforge
   * debian/control: Bump Standards-Version to 4.2.1 (no further changes)
   * debian/control: Downgrade priority to optional to please lintian
   * debian/control: Remove duplicate Section/Priority to please lintian
   * Create a new libtirpc-common package and move /etc/netconfig and
 netconfig.5 to it, do not conflit with libtirpc1 to ease the
 co-installation of libtirpc1 and libtirpc3 (Closes: #884029)
Checksums-Sha1:
 57a41bcaf4f0311c55fd41f192a7c68e468b604d 1605 libtirpc_1.1.4-0.1.dsc
 d85717035cb9bd6c45557a1eb1351d3af9a69ff7 510924 libtirpc_1.1.4.orig.tar.bz2
 22811c4688eedcbd9d84486dd1fa31d96b45f160 13788 libtirpc_1.1.4-0.1.debian.tar.xz
 cd968947e719b41b217e573800cb276c91c4aec7 16504 
libtirpc-common_1.1.4-0.1_all.deb
 a16d132bcf14cbe05fd75def989ee3d825a41e13 201372 
libtirpc-dev_1.1.4-0.1_amd64.deb
 77d93375aefd5d3a2540fa49c34eac85864931ea 369952 
libtirpc3-dbgsym_1.1.4-0.1_amd64.deb
 aea4ccb093127281c2be67f64cbefb9e546aeb78 93316 libtirpc3_1.1.4-0.1_amd64.deb
 8415e7aaa5185fd54c3aacb40207ac7d513ab0bd 6445 
libtirpc_1.1.4-0.1_amd64.buildinfo
Checksums-Sha256:
 65c380582daef0c5b42f003fe7418ecc5245095a6168c90d4013d535859ebbeb 1605 
libtirpc_1.1.4-0.1.dsc
 2ca529f02292e10c158562295a1ffd95d2ce8af97820e3534fe1b0e3aec7561d 510924 
libtirpc_1.1.4.orig.tar.bz2
 6563e4794884ee600d0e5bdd384c9630c77068cf48642a460f4d7b04be95e244 13788 
libtirpc_1.1.4-0.1.debian.

Bug#906371: Changes in alter-sequence-alignment break build of jmodeltest (Was: Bug#906371: jmodeltest: FTBFS in buster/sid)

2018-10-17 Thread Andreas Tille
On Tue, Aug 21, 2018 at 08:46:17AM +0200, Andreas Tille wrote:
> Hi,
> 
> On Mon, Aug 20, 2018 at 12:39:21AM +0200, Emmanuel Bourg wrote:
> > > do you have any hint how to deal with this issue?
> > 
> > The actual error is:
> > 
> > [javac]
> > /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:28:
> > error: package parser does not exist
> > [javac] import parser.ParseException;
> > [javac]  ^
> > [javac]
> > /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:29:
> > error: package converter does not exist
> > [javac] import converter.Converter;
> > [javac] ^
> > [javac]
> > /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:30:
> > error: package converter does not exist
> > [javac] import converter.DefaultFactory;
> > [javac] ^
> > [javac]
> > /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:31:
> > error: package converter does not exist
> > [javac] import converter.Factory;
> > [javac] ^
> > 
> > There is an issue with a dependency (alter-sequence-alignment maybe?),
> > the Java version isn't to blame here.
> 
> Good catch.  The latest upstream version of alter-sequence-alignment has
> split these to an additional alter-lib.jar and the time of the build
> failure of jmodeltest correlates with the upload of
> alter-sequence-alignment 1.3.4-1.  But now the question is:  How to
> teach the jmodeltest build system to use alter-lib.jar.  I think adding
> it to debian/manifest[1] is needed to *run* jmodeltest but it surely
> does not help at build time.  I have not found any place where the
> build system specifies the needed jars. :-(

I tried to add alter-lib.jar to build.xml[1].  Unfortunately this does
not help to fix the issue

[javac] 
/build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:28:
 error: package parser does not exist
[javac] import parser.ParseException;
[javac]  ^
[javac] 
/build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:29:
 error: package converter does not exist
[javac] import converter.Converter;
[javac] ^
[javac] 
/build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:30:
 error: package converter does not exist
[javac] import converter.DefaultFactory;
[javac] ^
[javac] 
/build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:31:
 error: package converter does not exist
[javac] import converter.Factory;

Any hint how to get the classes in alter-lib.jar found?

Moreover I get lots of

[javac] 
/build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/exe/Distributor.java:23:
 warning: [deprecation] Observable in java.util has been deprecated
[javac] import java.util.Observable;
[javac] ^

Kind regards

   Andreas.


[1] 
https://salsa.debian.org/med-team/jmodeltest/commit/4e5707bbe45cb80d3dc96a3800477affaef73680

-- 
http://fam-tille.de



Bug#910698: dogtag-pki needs jdk8

2018-10-17 Thread Timo Aaltonen
On 17.10.2018 09:52, Emmanuel Bourg wrote:
> Le 17/10/2018 à 07:11, Timo Aaltonen a écrit :
> 
>> ldapjdk is built against jdk8 because jss/dogtag-pki still need it that
>> way or things will break. Though now I realized maybe it might still
>> work with -Dant.build.javac.target=1.8 (or whatever jdk8 uses).
> 
> What errors do you get if you use the Java 11 compiled ldapjdk with
> jss/dogtag-pki?

I can't remember offhand, some compatibility errors with versions.


-- 
t



Bug#911217: uwsgi-plugin-jvm-openjdk-11: required java class file uwsgi.jar missing

2018-10-17 Thread Jonas Smedegaard
Package: uwsgi-plugin-jvm-openjdk-11
Version: 2.0.17.1-8
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

To link jvm with uWSGI the built class file uwsgi.jar must be loaded,
but that file is not shipped with the package.

Workaround is to fetch the class file from source - e.g.
https://raw.githubusercontent.com/unbit/uwsgi/master/plugins/jvm/uwsgi.java
and compile that with "javac uwsgi.java" and place the result in CLASSPATH.

Proper fix is to ship the built class file.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlvG7SIACgkQLHwxRsGg
ASEMAw/+KL9bT1xJQMzbo8iHb83r5mVh50dLZgrIaKxRdpzq7O6C4LzYBbh0Lyze
OJmBQepw0NjA0L3V8aKuseg3ScBULmcV0CiDClBQlMOc3EwWVZ9QUdcQ3pC5NS0g
AGlkcfEMlUGiL/LF/sIqQ/OBYwu+LYZH3wglY6KM062AJnWWTw3v4ZKLysDiqQ6s
6IJ5iPCRTI7JSJB2Y2fDekwQBgOVVYMMn1tLjDq2sOmR93JA4kfxNo/Qksh8uuL9
Y+Zzw2egmVrZk0DluXiWUZAo0hcJPYA3V1SacUtA0UpGMJTCeKYf/Vl5q0vXjWHX
ExGgJG+ouFihebw5adtYltD9Tm8dMsXVrgnOba4fqGSf0czZ6IVADTHh5FpI6M/X
cymPWLY1CTyPVd1bxBvBzaUdPpB3xj8qaHuPmMEMJfB/rdTSzOBewYjLA9TZzhLk
Lznu16Glor+bize3pU7OIJz+nhWZvSVg4DLJ61OiNLRs68fBSr3p7IczHQ7wXGTe
ttavPtDCnB1AH3xbAB2BNkODoX1iBsVb0GIZYvGSqqy/3t+udR43559N5Gd6GoA2
T7i8jUpfPApDGvXmJdEue9oWpkF76VoVgaylYUOvHeWHiHuItFsyT892juQgX+Vr
OFY8lvHP0UAdXCrrFgoAIumv0LvRoQKjYdYSfCqRPAbU1BnEzo8=
=LR2I
-END PGP SIGNATURE-



Bug#885677: marked as done (liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2)

2018-10-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Oct 2018 07:35:50 +
with message-id 
and subject line Bug#885677: fixed in lablgtk2 2.18.5+dfsg-2
has caused the Debian Bug report #885677,
regarding liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblablgtksourceview2-ocaml
Version: 2.18.5+dfsg-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gtksourceview2
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends on gtksourceview2 which has not had a release
since 2010.

Your package has these reverse-depends in Debian (via
liblablgtksourceview2-ocaml-dev package)

- alt-ergo
- coq
- frama-c
- lablgtk-extras
- laby
- marionnet
- why3

Please port your package to GTK3 and gtksourceview3 and related
maintained libraries. Otherwise, please consider requesting that your
package be removed from Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: lablgtk2
Source-Version: 2.18.5+dfsg-2

We believe that the bug you reported is fixed in the latest version of
lablgtk2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated lablgtk2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Oct 2018 18:20:37 +0200
Source: lablgtk2
Binary: liblablgtk2-ocaml liblablgtk2-gl-ocaml liblablgtk2-gnome-ocaml 
liblablgtk2-ocaml-dev liblablgtk2-gl-ocaml-dev liblablgtk2-gnome-ocaml-dev 
liblablgtk2-ocaml-doc
Architecture: source amd64 all
Version: 2.18.5+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Description:
 liblablgtk2-gl-ocaml - runtime libraries for OCaml bindings to GtkGL
 liblablgtk2-gl-ocaml-dev - OCaml bindings to GtkGL
 liblablgtk2-gnome-ocaml - runtime libraries for OCaml bindings to GNOME
 liblablgtk2-gnome-ocaml-dev - OCaml bindings to GNOME
 liblablgtk2-ocaml - runtime libraries for OCaml bindings for GTK+ version 2
 liblablgtk2-ocaml-dev - OCaml bindings to Gtk+ version 2
 liblablgtk2-ocaml-doc - OCaml bindings to Gtk+ version 2 (documentation)
Closes: 885677
Changes:
 lablgtk2 (2.18.5+dfsg-2) unstable; urgency=medium
 .
   * Build without gtksourceview2 and gnomecanvas (Closes: #885677)
   * Remove findlib package lablgtk2-gnome.panel
   * Switch Vcs-* to salsa and other minor changes
Checksums-Sha1:
 79ee6c427db557d8feb6ff5c4d36d6d7d258648e 2391 lablgtk2_2.18.5+dfsg-2.dsc
 d9f114e1e79ac089e1a3083948d88d6c03444184 10072 
lablgtk2_2.18.5+dfsg-2.debian.tar.xz
 b1baf3d1808ff3040ada7b4667f9c197d16b6818 16852 
lablgtk2_2.18.5+dfsg-2_amd64.buildinfo
 ca07b4d9dbd48b3c2f7c9b5a5998dd6529282c41 4012 
liblablgtk2-gl-ocaml-dbgsym_2.18.5+dfsg-2_amd64.deb
 ce77f9aacb33a389ef4ce98e93fb09e7fc3f16e6 44396 
liblablgtk2-gl-ocaml-dev_2.18.5+dfsg-2_amd64.deb
 2ac609efadf87667b80a39a4aacb617577e8aa90 44356 
liblablgtk2-gl-ocaml_2.18.5+dfsg-2_amd64.deb
 acfeb7b59471b591af1f57658369a1abe9f86feb 3912 
liblablgtk2-gnome-ocaml-dbgsym_2.18.5+dfsg-2_amd64.deb
 9fead10be383c430b70fd4d95f230c7bfe3c7dc2 34932 
liblablgtk2-gnome-ocaml-dev_2.18.5+dfsg-2_amd64.deb
 85df80d9f4579cdf801124beb193e0ae6f83c409 43452 
liblablgtk2-gnome-ocaml_2.18.5+dfsg-2_amd64.deb
 49e23a33856bbe2e9d2a8af1fb2ae420ec653a2d 160584 
liblablgtk2-ocaml-dbgsym_2.18.5+dfsg-2_amd64.deb
 dc41e9bee6bf2f1c71abd9e872aad74ab8570010 1499560 
liblablgtk2-ocaml-dev_2.18.5+dfsg-2_amd64.deb
 07e06445478c5be5905e9c9d2a5c72d1f3ea5308 863228 
liblablgtk2-ocaml-doc_2.18.5+dfsg-2_all.deb
 3775f3bd96aa03ba19135f34a50f366b90dee8bc 846424 
liblablgtk2-ocaml_2.18.5+dfsg-2_amd64.deb
Checksums-Sha256:
 e8e473

Bug#904648: Bug #904648 in tweepy marked as pending

2018-10-17 Thread Sophie Brun
Control: tag -1 pending

Hello,

Bug #904648 in tweepy reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/tweepy/commit/dc82f144e96046f9a829c2deef522a9943378894


Import upstream patches for Python3.7 (Closes: #904648)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/904648



Processed: Bug #904648 in tweepy marked as pending

2018-10-17 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #904648 [python3-tweepy] python3-tweepy: fails to install with Python 3.7
Added tag(s) pending.

-- 
904648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems