Bug#849787: probably best to just ignore this for Stretch

[Russell Coker]

priority 849787 wishlist
thanks

I've made selinux policy packages conflict with mcstrans so this shouldn't be 
a problem any more.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Processed: probably best to just ignore this for Stretch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> priority 849787 wishlist
Bug #849787 [mcstrans] mcstrans: Running mcstrans triggers 849748 and is the 
most serious SE Linux problem
Severity set to 'wishlist' from 'critical'
> thanks
Stopping processing here.

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

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

[intrigeri]

shirish शिरीष:
> in-line :-

> On 07/01/2017, Daniel Kahn Gillmor  wrote:
>> Have you restarted dirmngr since the upgrade?

> how do I restart it ?

systemctl --user restart dirmngr.socket 

:)

Bug#841598: marked as done (ftp.app: FTBFS: install: cannot stat 'FTP.xpm': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 08 Jan 2017 05:18:26 +
with message-id 
and subject line Bug#841598: fixed in ftp.app 0.5-1
has caused the Debian Bug report #841598,
regarding ftp.app: FTBFS: install: cannot stat 'FTP.xpm': No such file or 
directory
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.)


-- 
841598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ftp.app
Version: 0.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> This is gnustep-make 2.6.8. Type 'make print-gnustep-make-help' for help.
> Making all for app FTP...
> make[4]: Nothing to be done for 'internal-app-compile'.
>  Copying resources into the app wrapper...
> Making install for app FTP...
>  Creating /<>/debian/ftp.app//usr/lib/GNUstep/Applications...
>  Installing bundle directory...
> make[1]: Leaving directory '/<>'
> dh_install debian/*.desktop usr/share/applications/
> dh_install: Compatibility levels before 9 are deprecated (level 7 in use)
> rm 
> /<>/debian/*.app/usr/lib/GNUstep/Applications/*.app/Resources/*.desktop
> #move resources to /usr/share/GNUstep and add a symlink if the installation 
> is following the FHS
> dh_installdirs usr/share/GNUstep
> dh_installdirs: Compatibility levels before 9 are deprecated (level 7 in use)
> mv 
> /<>/debian/ftp.app/usr/lib/GNUstep/Applications/FTP.app/Resources
>  \
>   /<>/debian/ftp.app/usr/share/GNUstep/FTP.app
> dh_link usr/share/GNUstep/FTP.app \
>   /usr/lib/GNUstep/Applications/FTP.app/Resources
> # Install the XPM icon.
> install -D -m 644 FTP.xpm 
> /<>/debian/ftp.app/usr/share/pixmaps/FTP.xpm
> install: cannot stat 'FTP.xpm': No such file or directory
> debian/rules:35: recipe for target 'install' failed
> make: *** [install] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/ftp.app_0.3-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ftp.app
Source-Version: 0.5-1

We believe that the bug you reported is fixed in the latest version of
ftp.app, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated ftp.app 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, 08 Jan 2017 06:01:23 +0100
Source: ftp.app
Binary: ftp.app
Architecture: source amd64
Version: 0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Federico Gimenez Nieto 
Changed-By: Gürkan Myczko 
Description:
 ftp.app- File transfer protocol application for GNUstep
Closes: 841598
Changes:
 ftp.app (0.5-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Gürkan Myczko ]
   * New upstream version.
   * Bump standards version to 3.9.8.
   * Bump debhelper version to 9.
   * debian/rules: Fix image resizing wrt. convert adds numbered suffixes
 to file names since recently.  (Closes: #841598)
 .
   [ Axel Beckert ]
   * Switch Vcs-* 

Bug#850113: vim-youcompleteme: 'KeyError's on every key press flooding vim

[Vitry David Gilbert]

Bonjour,
For me patch from
https://github.com/Valloric/YouCompleteMe/commit/85d58448732b46359db3e38b862ba935d7c3bb02

seems to work

Thank


signature.asc
Description: OpenPGP digital signature

Processed: reopening 850430

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 850430
Bug #850430 [postfix] postfix 3.1.4-1 breaks on lmtp interface
Bug 850430 is not marked as done; doing nothing.
> thanks
Stopping processing here.

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

Processed: found 850430 in 3.1.4-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 850430 3.1.4-2
Bug #850430 {Done: LaMont Jones } [postfix] postfix 3.1.4-1 
breaks on lmtp interface
Marked as found in versions postfix/3.1.4-2; no longer marked as fixed in 
versions postfix/3.1.4-2 and reopened.
> thanks
Stopping processing here.

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

Processed: tagging 841598

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Got a package to sponsor which builds again
> tags 841598 + pending
Bug #841598 [src:ftp.app] ftp.app: FTBFS: install: cannot stat 'FTP.xpm': No 
such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#849663: marked as done (golang-github-boltdb-bolt: FTBFS on 32-bit: db_test.go:534: constant 2147483648 overflows int)

[Debian Bug Tracking System]

Your message dated Sun, 08 Jan 2017 03:18:20 +
with message-id 
and subject line Bug#849663: fixed in golang-github-boltdb-bolt 1.3.0-1
has caused the Debian Bug report #849663,
regarding golang-github-boltdb-bolt: FTBFS on 32-bit: db_test.go:534: constant 
2147483648 overflows int
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.)


-- 
849663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-boltdb-bolt
Version: 1.2.1-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

dh_auto_test -- -short
go test -v -p 1 -short github.com/boltdb/bolt 
github.com/boltdb/bolt/cmd/bolt
# github.com/boltdb/bolt_test
src/github.com/boltdb/bolt/db_test.go:534: constant 2147483648 overflows int
FAILgithub.com/boltdb/bolt [build failed]

Full build log:
https://tests.reproducible-builds.org/debian/unstable/i386/golang-github-boltdb-bolt
https://tests.reproducible-builds.org/debian/unstable/armhf/golang-github-boltdb-bolt
--- End Message ---
--- Begin Message ---
Source: golang-github-boltdb-bolt
Source-Version: 1.3.0-1

We believe that the bug you reported is fixed in the latest version of
golang-github-boltdb-bolt, 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 849...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated 
golang-github-boltdb-bolt 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: Sat, 07 Jan 2017 23:59:11 -0300
Source: golang-github-boltdb-bolt
Binary: golang-github-boltdb-bolt-dev
Architecture: source
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 golang-github-boltdb-bolt-dev - low-level key/value database for Go
Closes: 849663
Changes:
 golang-github-boltdb-bolt (1.3.0-1) unstable; urgency=medium
 .
   * Add myself to Uploaders.
   * Patch a test that fails on 32-bit architectures due to the usage of a
 constnat that is too big to fit in an int. Closes: #849663
   * New upstream release.
Checksums-Sha1:
 26e3ffcaaead7a7bd987ce6346631ed0bf419765 2281 
golang-github-boltdb-bolt_1.3.0-1.dsc
 3190754216c8c1b601a74260d83a41c66161873a 80322 
golang-github-boltdb-bolt_1.3.0.orig.tar.gz
 a32c6730cdc180196df4904c6087e6aa64272389 2736 
golang-github-boltdb-bolt_1.3.0-1.debian.tar.xz
Checksums-Sha256:
 eea8e474cc7d659de1bee80546b67a9a658028f9c01e62685562a5e3c2c3ae9c 2281 
golang-github-boltdb-bolt_1.3.0-1.dsc
 e417fccc1186dcf8807e3b2a7afb31bad31faf2ca383d203002a7d783c872f13 80322 
golang-github-boltdb-bolt_1.3.0.orig.tar.gz
 261bcbcbf6071f70330403d9f2bdcc66381c94bd16150e537db2fae718fe6237 2736 
golang-github-boltdb-bolt_1.3.0-1.debian.tar.xz
Files:
 dc62acc0e950c41913f1db3093e907de 2281 devel extra 
golang-github-boltdb-bolt_1.3.0-1.dsc
 a0ccc04a3d77e0e5f3ad0eecfbfd44a5 80322 devel extra 
golang-github-boltdb-bolt_1.3.0.orig.tar.gz
 621bb900fd9552264f191464bf410337 2736 devel extra 
golang-github-boltdb-bolt_1.3.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlhxq2gACgkQXdjgv5Gj
09qTfxAAoyd0rPeqPe3U7spU6+VgKx1WtMTCII0Dq2yPaArdEH7k1TVk2UFS7bmE
fE3LNyhR4vc8adTeVyBQL3JPMUS6l+ULBYpT5L+RrZJLMgC8O8Dkw/0LmMRErN/m
LR/AdWJlEOnfLXSDhSBgkP1LmvZplOqVaLlXhDlZqaKclwZ+6AoEwGCVc24j47Sh
0Hstvk9KOY1dNg9XgARDimvseNnHRbyhtIeIn5ZPE5FnP7PHe+FHl5UGCRgGlq1F
/Gob4ZtvXlhY83g24/dnZ2wZ/xkqH1APLPIti57AZyk7mDOTR3aV5SXVKd3X8zY4
AK8aez1i3UgXjwubR7hhLNwXTeNzj1zqf4Ij9hBFwfsswbqduMfbNv/9oadDycaC
En+eFwCUYthMUS9FzkGg8ZyNDfr6ZvfOaJ+diHds/5wbS1djGdft39AxR2KqgbD6
Bcthnu2mXMNtEwoMSe5I27kXa/ShivaCN5We1F5+HtC5+9GDAqQYvGinidVlyAr4
t2Qta2lKKopeXoVJpjxKj+a11OlssSTQ1Ki/LzkK6vu4uyQsGN3CsPGWsW9rkguE
oHrreU/fIYqkaxu2xcfvCYDjiykj2+v5ray3llqc9IzHcPunxA6uOiVysvnQW6hl

Bug#849663: Pending fixes for bugs in the golang-github-boltdb-bolt package

[pkg-go-maintainers]

tag 849663 + pending
thanks

Some bugs in the golang-github-boltdb-bolt package are closed in
revision 8e938b6075967aa48d768f854731edb1636d019b in branch 'master'
by Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-boltdb-bolt.git/commit/?id=8e938b6

Commit message:

Patch a test that fails on 32-bit architectures due to the usage of a 
constnat that is too big to fit in an int. Closes: #849663

Bug#835800: marked as done (transmission: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Sun, 08 Jan 2017 03:06:58 +
with message-id 
and subject line Bug#835800: fixed in transmission 2.92-2
has caused the Debian Bug report #835800,
regarding transmission: FTBFS with openssl 1.1.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.)


-- 
835800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: transmission
Version: 2.84-3.1
Severity: important

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all
packages using OpenSSL this package fail to build.  A log of that
build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-08-26/failed/transmission_2.84-3.1_amd64-2016-08-26T19%3A54%3A31Z

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see
various of the reasons why it might fail.  There are also updated
man pages at https://www.openssl.org/docs/manmaster/ that should
contain useful information.

Experimental has the libssl-dev 1.1.0 packages in it. I suggest
you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: transmission
Source-Version: 2.92-2

We believe that the bug you reported is fixed in the latest version of
transmission, 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 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated transmission 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: Sat, 07 Jan 2017 21:15:41 -0500
Source: transmission
Binary: transmission transmission-common transmission-cli transmission-gtk 
transmission-qt transmission-daemon
Architecture: source amd64 all
Version: 2.92-2
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 transmission - lightweight BitTorrent client
 transmission-cli - lightweight BitTorrent client (command line programs)
 transmission-common - lightweight BitTorrent client (common files)
 transmission-daemon - lightweight BitTorrent client (daemon)
 transmission-gtk - lightweight BitTorrent client (GTK+ interface)
 transmission-qt - lightweight BitTorrent client (Qt interface)
Closes: 831467 835800 836738
Changes:
 transmission (2.92-2) unstable; urgency=medium
 .
   * debian/watch
 - point to transmission-release github repository
   * Support OpenSSL 1.1.0; Closes: #835800
   * debian/copyright
 - point source field to github
 - extend packaging copyright years
   * debian/control
 - use HTTPS for Vcs-* fields
 - drop cmake from b-d, not needed; Closes: #836738
   * debian/patches/transmission-daemon_execstop_service.patch
 - add ExecStop to transmission-daemon service file; Closes: #831467
Checksums-Sha1:
 7f4dab30cbae246e0b53df8238c1ebfdbfbabe94 2622 transmission_2.92-2.dsc
 92cd71bb4c77ff55d118775087d49aeb478e9171 21900 
transmission_2.92-2.debian.tar.xz
 ceafdc0b7d71a08534b9d3a5bd97a78ad1d60576 4925482 
transmission-cli-dbgsym_2.92-2_amd64.deb
 7d02800aa1e5053f24af4c279973de05034b2643 404736 
transmission-cli_2.92-2_amd64.deb
 b72552f8e9aabef01afa7b06d8c45cb6817e3f25 287396 
transmission-common_2.92-2_all.deb
 73fa1d541570067dd15e401c736c809d26d009ab 1002352 
transmission-daemon-dbgsym_2.92-2_amd64.deb
 fd73323c7127d7b4197fd8675d82d7eae07c304f 218672 
transmission-daemon_2.92-2_amd64.deb
 0dc152a7fd95cdad5ddb06b5923c76a8df278b35 1581648 
transmission-gtk-dbgsym_2.92-2_amd64.deb
 84cfd843fc03b32c03a5bed1e87aa37bbb5ce872 700558 
transmission-gtk_2.92-2_amd64.deb
 ec219d10cd881bf4b8463f50c60bd5396cfd1459 10412900 
transmission-qt-dbgsym_2.92-2_amd64.deb
 a21087a2847ca4d616d7b80f87cb166c5ddf8e60 664358 
transmission-qt_2.92-2_amd64.deb
 969a4049fa8756173e2ce14767d87b6bc6981a42 1146 transmission_2.92-2_all.deb
 b43e4c262d64bb942fb8d6b19673c5be96efa42b 17820 
transmission_2.92-2_amd64.buildinfo
Checksums-Sha256:
 2521871300ed867934f4e2043ab619728ad83306d1b63d19f9f3c5184ca2d15f 2622 

Processed: Pending fixes for bugs in the golang-github-boltdb-bolt package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 849663 + pending
Bug #849663 [src:golang-github-boltdb-bolt] golang-github-boltdb-bolt: FTBFS on 
32-bit: db_test.go:534: constant 2147483648 overflows int
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 850226 https://bugzilla.quagga.net/show_bug.cgi?id=870
Bug #850226 [quagga-bgpd] no longer advertises route
Set Bug forwarded-to-address to 
'https://bugzilla.quagga.net/show_bug.cgi?id=870'.
> severity 850226 important
Bug #850226 [quagga-bgpd] no longer advertises route
Severity set to 'important' from 'grave'
> --
Stopping processing here.

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

Bug#850575: diaspora: cannot install because broken maintscript line in preinst and missing gem files

[Pirate Praveen]

Control: severity -1 important

On ഞായര്‍ 08 ജനുവരി 2017 06:49 രാവിലെ, Julian Gilbey wrote:
> Package: diaspora
> Version: 0.6.0.0+debian-7
> Severity: grave
> 
> In the debian/maintscript file, you have:
> dir_to_symlink /usr/share/diaspora/config 0.5.9.1+debian3 diaspora-common
> 
> This is not the correct syntax for the dir_to_symlink command: it
> should be
> dir_to_symlink pathname new-target [prior-version [package]]
> 
> So I guess this line should read:
> dir_to_symlink /usr/share/diaspora/config /etc/diaspora 0.5.9.1+debian3 
> diaspora-common
> 
> With this change, then diaspora installs more successfully.  (Well,
> successfully, except that it couldn't find the gem mysql2 (I've gone
> for the mysql option.):
> 

I don't think the dir_to_symlink bug warrants grave severity.

> Could not find gem 'mysql2 (~> 0.4.4)' in any of the gem sources listed in 
> your
> Gemfile or available on this machine.

Because the diaspora package currently only supports postgresql. I have
added mysql support to diaspora-installer via diaspora-installer-mysql
but did not get time to create diaspora-mysql.

> Installing ruby-mysql2 then gave the error:
> 
> export DB_NAME=diaspora_production
> RAILS_ENV=production DB=mysql ENVIRONMENT_URL=https://diaspora.d-and-j.net
> Verifying we have all required libraries...
> Resolving dependencies...
> Bundler could not find compatible versions for gem "jquery-ui-rails":
>   In Gemfile:
> jquery-ui-rails (~> 6.0)
> 
> rails_admin (~> 0.8.1) was resolved to 0.8.1, which depends on
>   jquery-ui-rails (~> 5.0)
> 
> Oh dear :-(
> 
> Any suggestions?

This is fixed in ruby-rails-admin, so just update it. If you are
interested you can try creating diaspora-mysql in the same way I did
diaspora-installer-mysql.

1. Make postgres optional dependency for diaspora (change postgresql ->
postgresql | virtual-mysql-server and dbconfig-postgres ->
dbconfig-postgres | dbconfig-mysql and ruby-pg | ruby-mysql2)
2. Create new binary package diaspora-mysql whcih depends on
dbconfig-mysql, default-mysql-server | virtual-mysql-server, ruby-mysql2
and diaspora.




signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#850575: diaspora: cannot install because broken maintscript line in preinst and missing gem files

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #850575 [diaspora] diaspora: cannot install because broken maintscript line 
in preinst and missing gem files
Severity set to 'important' from 'grave'

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

Bug#850575: diaspora: cannot install because broken maintscript line in preinst and missing gem files

[Julian Gilbey]

Package: diaspora
Version: 0.6.0.0+debian-7
Severity: grave

In the debian/maintscript file, you have:
dir_to_symlink /usr/share/diaspora/config 0.5.9.1+debian3 diaspora-common

This is not the correct syntax for the dir_to_symlink command: it
should be
dir_to_symlink pathname new-target [prior-version [package]]

So I guess this line should read:
dir_to_symlink /usr/share/diaspora/config /etc/diaspora 0.5.9.1+debian3 
diaspora-common

With this change, then diaspora installs more successfully.  (Well,
successfully, except that it couldn't find the gem mysql2 (I've gone
for the mysql option.):

Could not find gem 'mysql2 (~> 0.4.4)' in any of the gem sources listed in your
Gemfile or available on this machine.

Installing ruby-mysql2 then gave the error:

export DB_NAME=diaspora_production
RAILS_ENV=production DB=mysql ENVIRONMENT_URL=https://diaspora.d-and-j.net
Verifying we have all required libraries...
Resolving dependencies...
Bundler could not find compatible versions for gem "jquery-ui-rails":
  In Gemfile:
jquery-ui-rails (~> 6.0)

rails_admin (~> 0.8.1) was resolved to 0.8.1, which depends on
  jquery-ui-rails (~> 5.0)

Oh dear :-(

Any suggestions?

   Julian

-- System Information:
Debian Release: stretch/sid
  APT prefers jessie
  APT policy: (500, 'jessie'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#811653: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 23:55:47 +
with message-id 
and subject line Bug#811653: fixed in libaria 2.8.0+repack-1.1
has caused the Debian Bug report #811653,
regarding FTBFS with GCC 6: cannot convert x to y
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.)


-- 
811653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libaria
Version: 2.8.0+repack-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_REENTRANT   -fPIC -fno-exceptions 
>  -Iinclude src/ArCameraCommands.cpp -o obj/ArCameraCommands.o
> g++ -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_REENTRANT   -fPIC -fno-exceptions 
>  -Iinclude src/ArCameraCollection.cpp -o obj/ArCameraCollection.o
> src/ArCameraCollection.cpp: In member function 
> 'ArCameraCollection::CommandInfo* ArCameraCollection::findCommandInfo(const 
> char*, const char*)':
> src/ArCameraCollection.cpp:569:12: error: cannot convert 'bool' to 
> 'ArCameraCollection::CommandInfo*' in return
>  return false;
> ^
> 
> src/ArCameraCollection.cpp: In member function 
> 'ArCameraCollection::ParamInfo* ArCameraCollection::findParamInfo(const 
> char*, const char*)':
> src/ArCameraCollection.cpp:591:12: error: cannot convert 'bool' to 
> 'ArCameraCollection::ParamInfo*' in return
>  return false;
> ^
> 
> Makefile:659: recipe for target 'obj/ArCameraCollection.o' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: libaria
Source-Version: 2.8.0+repack-1.1

We believe that the bug you reported is fixed in the latest version of
libaria, 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 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jan Luca Naumann  (supplier of updated libaria 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: Sat, 07 Jan 2017 23:19:19 +0100
Source: libaria
Binary: libaria-dev libaria-demo libaria2 libaria-dev-doc python-ariapy
Architecture: source amd64 all
Version: 2.8.0+repack-1.1
Distribution: unstable
Urgency: medium
Maintainer: Srećko Jurić-Kavelj 
Changed-By: Jan Luca Naumann 
Description:
 libaria-demo - C++ library for MobileRobots/ActivMedia robots (demo example)
 libaria-dev - C++ library for MobileRobots/ActivMedia robots (devel)
 libaria-dev-doc - C++ library for MobileRobots/ActivMedia robots (devel docs)
 libaria2   - C++ library for MobileRobots/ActivMedia robots
 python-ariapy - C++ library for MobileRobots/ActivMedia robots (Python 
bindings)
Closes: 806055 811653
Changes:
 libaria (2.8.0+repack-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add debian/patches/fix-cannot-convert-x-to-y.patch to fix
 FTBFS with GCC 6: cannot convert x to y. (Closes: #811653)
   * debian/rules:
 Fix FTBFS when built with dpkg-buildpackage -A. (Closes: #806055)
Checksums-Sha1:
 6675e451978178e978aaeba0631e2f5121d02bb4 2155 libaria_2.8.0+repack-1.1.dsc
 fcae0f971db4406e9fe7c5cb6232bf7c5c858ea6 11328 
libaria_2.8.0+repack-1.1.debian.tar.xz
 d6dd532a2e9205ad22ddc65e7ad3e4adf3f58512 170188 
libaria-demo-dbgsym_2.8.0+repack-1.1_amd64.deb
 f6ca732e08de254dabba19affdd5a0762951110a 34432 
libaria-demo_2.8.0+repack-1.1_amd64.deb
 4014f9f600a412d32c99cdd51277752617aa8fae 1819550 

Bug#806055: marked as done (libaria: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 23:55:47 +
with message-id 
and subject line Bug#806055: fixed in libaria 2.8.0+repack-1.1
has caused the Debian Bug report #806055,
regarding libaria: FTBFS when built with dpkg-buildpackage -A (No such file or 
directory)
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.)


-- 
806055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libaria
Version: 2.8.0+repack-1
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh binary-indep --with python2 --parallel
   dh_testroot -i -O--parallel
   dh_prep -i -O--parallel
   dh_auto_install -i -O--parallel
make -j1 install DESTDIR=/<>/libaria-2.8.0\+repack/debian/tmp 
AM_UPDATE_INFO_DIR=no
make[1]: Entering directory '/<>/libaria-2.8.0+repack'
install --preserve-timestamps -m 755 -d 
/<>/libaria-2.8.0+repack/debian/tmp/usr
install --preserve-timestamps -d -m 755 
/<>/libaria-2.8.0+repack/debian/tmp/usr/include/Aria
install --preserve-timestamps -D -m 644 include/*.h 
/<>/libaria-2.8.0+repack/debian/tmp/usr/include/Aria
install --preserve-timestamps -d -m 755 
/<>/libaria-2.8.0+repack/debian/tmp/usr/share/Aria/params
install --preserve-timestamps -D -m 644 params/* 
/<>/libaria-2.8.0+repack/debian/tmp/usr/share/Aria/params
install: cannot stat 'params/*': No such file or directory
Makefile:738: recipe for target 'install' failed
make[1]: *** [install] Error 1
make[1]: Leaving directory '/<>/libaria-2.8.0+repack'
dh_auto_install: make -j1 install 
DESTDIR=/<>/libaria-2.8.0+repack/debian/tmp AM_UPDATE_INFO_DIR=no 
returned exit code 2
debian/rules:9: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).

Thanks.
--- End Message ---
--- Begin Message ---
Source: libaria
Source-Version: 2.8.0+repack-1.1

We believe that the bug you reported is fixed in the latest version of
libaria, 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 806...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jan Luca Naumann  (supplier of updated libaria 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: Sat, 07 Jan 2017 23:19:19 +0100
Source: libaria
Binary: libaria-dev libaria-demo libaria2 libaria-dev-doc python-ariapy
Architecture: source amd64 all
Version: 2.8.0+repack-1.1
Distribution: unstable
Urgency: medium
Maintainer: Srećko Jurić-Kavelj 
Changed-By: Jan Luca Naumann 
Description:
 libaria-demo - C++ library for MobileRobots/ActivMedia robots (demo example)
 libaria-dev - C++ library for MobileRobots/ActivMedia 

Bug#846335: cross-toolchain-base: FTBFS in testing (2 out of 2 hunks FAILED)

[Santiago Vila]

On Sat, 7 Jan 2017, Johannes Schauer wrote:

> The Built-Using field is for binary packages to indicate that they incorporate
> code from other source packages than the source package that the build from.

I see that's the case indeed, but in an indirect way.

The package cross-toolchain-base-ports, for example, has this in Build-Depends:

  binutils-source (>= 2.27.51.20161101-1~),
  glibc-source (>= 2.24-5~),
  gcc-6-source (>= 6.2.0-11~),
  linux-source (>= 4.8),

So they incorporate code from other source packages, but only as far
as they are distribured in "foo-source"-like packages. This is to be
able to build-depend on them.

So, the normal build-depends mechanism is used to decide which version
need to be installed for the build.

> If the package really fails to build from source because you are not 
> installing
> the right package versions or not the right packages, then these are missing
> from the Build-Depends-* fields.

That's basically what I thought.

Matthias, I have built these two packages in stretch again.

Now they build ok so I did a diff between old (failed) and new
build logs and found this:


-if dpkg --compare-versions 6.2.0-13 le 6.2.1-4; then \
+if dpkg --compare-versions 6.2.1-5 le 6.2.1-4; then \
   cd gcc; \
   patch -p1 < ../debian/patches/gcc/gcc-stage1.diff; \
 fi
-patching file debian/rules.patch
-Hunk #1 FAILED at 151.
-Hunk #2 FAILED at 187.
-2 out of 2 hunks FAILED -- saving rejects to file debian/rules.patch.rej
-debian/rules:213: recipe for target 'stamp-dir/init-gcc' failed
-make: *** [stamp-dir/init-gcc] Error 1
-dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


> The Built-Using header is for binary packages to assure copyright compliance 
> in
> the archive. They are not indicators of the binary packages required to build 
> a
> source package.

Again as I thought: Neither I or sbuild is supposed to look at the
Built-Using field in the binary packages when trying to rebuild
packages for testing purposes.

Instead, I suggest Matthias that he just updates the (already versioned)
build-depends on the *-source packages in the control file.

Then we could avoid filddling with conditional patching in
debian/rules, which we all see that it's prone to error.

If you are worried of this package propagating to testing before its
build-dependencies, I consider that to be a bug in britney and do not
usually report it as a bug in the package itself.

An error of type "build-dependencies not met" (i.e. "wait-dep" in
wannabuild speak) is always better than a tried-then-failed build.


Thanks a lot.

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

[shirish शिरीष]

in-line :-

On 07/01/2017, Daniel Kahn Gillmor  wrote:
> On Fri 2017-01-06 17:49:04 -0500, shirish शिरीष wrote:
>> But issue is still continuing -
>>
>> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197
>>
>> [4:22:18]
>> gpg: keyserver receive failed: No keyserver available
>>
>> I tried multiple times with various other keys but didn't succeed.
>
> Have you restarted dirmngr since the upgrade?

how do I restart it ?

dirmngr.service isn't even found :(

─[$] dpkg -L dirmngr | grep dirmngr.service
/usr/lib/systemd/user/dirmngr.service

─[$] ll -h /usr/lib/systemd/user/dirmngr.service

-rw-r--r-- 1 root root 250 2016-11-18 19:53
/usr/lib/systemd/user/dirmngr.service

and trying to see if it works got me nothing :(


[$] sudo systemctl status dirmngr.service

[sudo] password for shirish:
Unit dirmngr.service could not be found.


I did do a cat and saw this -

─[$] cat /usr/lib/systemd/user/dirmngr.service

[4:57:44]
[Unit]
Description=GnuPG network certificate management daemon
Documentation=man:dirmngr(8)
Requires=dirmngr.socket
After=dirmngr.socket
## This is a socket-activated service:
RefuseManualStart=true

[Service]
ExecStart=/usr/bin/dirmngr --supervised

Can you help ?


>are you using tor?  if
> you're using tor, have you removed all the ipv6 entries ?

I actually have this in grub for few years now

─[$] cat /etc/default/grub | grep ipv6

GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"

Maybe this goves a clue, dunno

> what does:
>
>gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye
>
> show you?
>
>  --dkg
>
└─[$] gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye

gpg-connect-agent: no running Dirmngr - starting '/usr/bin/dirmngr'
gpg-connect-agent: waiting for the dirmngr to come up ... (5s)
gpg-connect-agent: connection to the dirmngr established
S # hosttable (idx, ipv6, ipv4, dead, name, time):


Look forward to guidance.
-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#849935: marked as done (sogo: FTBFS (gen-saml2-exceptions.py: Command not found))

[Debian Bug Tracking System]

Your message dated Sun, 8 Jan 2017 00:24:21 +0100
with message-id <20170107232419.4ugyr75hlwgxc...@oskuro.net>
and subject line Missing python Build-Depends
has caused the Debian Bug report #849935,
regarding sogo: FTBFS (gen-saml2-exceptions.py: Command not found)
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.)


-- 
849935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sogo
Version: 2.2.17a-1.1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./configure --with-ssl=gnutls --enable-saml2 --prefix=/usr/System
GNUstep environment:
  system: /usr/System
  local:  /usr/Local
  user:   /sbuild-nonexistent/GNUstep
  path:   /usr/System:/usr/Network:/usr/Local:/sbuild-nonexistent/GNUstep
  flat:   yes

[... snipped ...]

/usr/bin/install -c -p  -m 644 NSNumber+Utilities.h 
SOGo.framework/Versions/2/Headers/NSNumber+Utilities.h
/usr/bin/install -c -p  -m 644 NSObject+DAV.h 
SOGo.framework/Versions/2/Headers/NSObject+DAV.h
/usr/bin/install -c -p  -m 644 NSObject+Utilities.h 
SOGo.framework/Versions/2/Headers/NSObject+Utilities.h
/usr/bin/install -c -p  -m 644 NSString+DAV.h 
SOGo.framework/Versions/2/Headers/NSString+DAV.h
/usr/bin/install -c -p  -m 644 NSString+Utilities.h 
SOGo.framework/Versions/2/Headers/NSString+Utilities.h
/usr/bin/install -c -p  -m 644 NSString+Crypto.h 
SOGo.framework/Versions/2/Headers/NSString+Crypto.h
/usr/bin/install -c -p  -m 644 NSData+Crypto.h 
SOGo.framework/Versions/2/Headers/NSData+Crypto.h
/usr/bin/install -c -p  -m 644 NSURL+DAV.h 
SOGo.framework/Versions/2/Headers/NSURL+DAV.h
/usr/bin/install -c -p  -m 644 SOGoAuthenticator.h 
SOGo.framework/Versions/2/Headers/SOGoAuthenticator.h
/usr/bin/install -c -p  -m 644 SOGoSession.h 
SOGo.framework/Versions/2/Headers/SOGoSession.h
/usr/bin/install -c -p  -m 644 SOGoCASSession.h 
SOGo.framework/Versions/2/Headers/SOGoCASSession.h
/usr/bin/install -c -p  -m 644 SOGoDAVAuthenticator.h 
SOGo.framework/Versions/2/Headers/SOGoDAVAuthenticator.h
/usr/bin/install -c -p  -m 644 SOGoProxyAuthenticator.h 
SOGo.framework/Versions/2/Headers/SOGoProxyAuthenticator.h
/usr/bin/install -c -p  -m 644 SOGoStaticAuthenticator.h 
SOGo.framework/Versions/2/Headers/SOGoStaticAuthenticator.h
/usr/bin/install -c -p  -m 644 SOGoWebAuthenticator.h 
SOGo.framework/Versions/2/Headers/SOGoWebAuthenticator.h
/usr/bin/install -c -p  -m 644 SOGoWebDAVAclManager.h 
SOGo.framework/Versions/2/Headers/SOGoWebDAVAclManager.h
/usr/bin/install -c -p  -m 644 SOGoWebDAVValue.h 
SOGo.framework/Versions/2/Headers/SOGoWebDAVValue.h
/usr/bin/install -c -p  -m 644 SOGoMailer.h 
SOGo.framework/Versions/2/Headers/SOGoMailer.h
/usr/bin/install -c -p  -m 644 SOGoGroup.h 
SOGo.framework/Versions/2/Headers/SOGoGroup.h
/usr/bin/install -c -p  -m 644 SOGoUser.h 
SOGo.framework/Versions/2/Headers/SOGoUser.h
/usr/bin/install -c -p  -m 644 DOMNode+SOGo.h 
SOGo.framework/Versions/2/Headers/DOMNode+SOGo.h
/usr/bin/install -c -p  -m 644 WORequest+SOGo.h 
SOGo.framework/Versions/2/Headers/WORequest+SOGo.h
/usr/bin/install -c -p  -m 644 WOResourceManager+SOGo.h 
SOGo.framework/Versions/2/Headers/WOResourceManager+SOGo.h
/usr/bin/install -c -p  -m 644 WOResponse+SOGo.h 
SOGo.framework/Versions/2/Headers/WOResponse+SOGo.h
/usr/bin/install -c -p  -m 644 WOContext+SOGo.h 
SOGo.framework/Versions/2/Headers/WOContext+SOGo.h
/usr/bin/install -c -p  -m 644 SOGoCredentialsFile.h 
SOGo.framework/Versions/2/Headers/SOGoCredentialsFile.h
/usr/bin/install -c -p  -m 644 SOGoSAML2Session.h 
SOGo.framework/Versions/2/Headers/SOGoSAML2Session.h
./gen-saml2-exceptions.py -DXMLSEC_CRYPTO=\"openssl\" 
-D__XMLSEC_FUNCTION__=__FUNCTION__ -DXMLSEC_NO_SIZE_T -DXMLSEC_NO_GOST=1 
-DXMLSEC_NO_XKMS=1 -DXMLSEC_NO_CRYPTO_DYNAMIC_LOADING=1 -DXMLSEC_OPENSSL_100=1 
-DXMLSEC_CRYPTO_OPENSSL=1 -I/usr/include/libxml2 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/xmlsec1 
make[5]: ./gen-saml2-exceptions.py: Command not found
GNUmakefile:172: recipe for target 'SOGoSAML2Exceptions.h' failed
make[5]: *** [SOGoSAML2Exceptions.h] Error 127
/usr/share/GNUstep/Makefiles/Master/rules.make:311: 

Processed: tagging 850430

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 850430 + pending
Bug #850430 {Done: LaMont Jones } [postfix] postfix 3.1.4-1 
breaks on lmtp interface
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#811783: marked as done (vnc4: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 23:03:54 +
with message-id 
and subject line Bug#811783: fixed in vnc4 4.1.1+X4.3.0+t-1
has caused the Debian Bug report #811783,
regarding vnc4: FTBFS with GCC 6: narrowing conversion
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.)


-- 
811783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vnc4
Version: 4.1.1+X4.3.0-37.6
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> make[2]: Entering directory '/<>/vnc4-4.1.1+X4.3.0/unix/tx'
> c++  -DX_DISPLAY_MISSING=1  -I../../common   -Wall -g -Wall  -c TXWindow.cxx
> TXWindow.cxx: In static member function 'static void TXWindow::init(Display*, 
> const char*)':
> TXWindow.cxx:93:76: error: narrowing conversion of '128' from 'int' to 'char' 
> inside { } [-Wnarrowing]
>static char tickBits[] = { 0x80, 0xc0, 0xe2, 0x76, 0x3e, 0x1c, 0x08, 0x00};
> ^
> 
> TXWindow.cxx:93:76: error: narrowing conversion of '192' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> TXWindow.cxx:93:76: error: narrowing conversion of '226' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> Makefile:55: recipe for target 'TXWindow.o' failed
> make[2]: *** [TXWindow.o] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: vnc4
Source-Version: 4.1.1+X4.3.0+t-1

We believe that the bug you reported is fixed in the latest version of
vnc4, 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 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ola Lundqvist  (supplier of updated vnc4 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: Sat, 07 Jan 2017 23:33:39 +0100
Source: vnc4
Binary: vnc4server xvnc4viewer
Architecture: source amd64
Version: 4.1.1+X4.3.0+t-1
Distribution: unstable
Urgency: high
Maintainer: Ola Lundqvist 
Changed-By: Ola Lundqvist 
Description:
 vnc4server - transitional package
 xvnc4viewer - transitional package
Closes: 491433 512703 578978 656862 811783
Changes:
 vnc4 (4.1.1+X4.3.0+t-1) unstable; urgency=high
 .
   * Made the package a transitional package to ensure tigervnc is installed
 as a replacement.
 Closes: #811783, #491433, #578978, #656862, #512703.
Checksums-Sha1:
 6bfbc42ae37359b924bb9953a7b58bc068394d24 1733 vnc4_4.1.1+X4.3.0+t-1.dsc
 fdc36faa2c4e29c6b85bdd03db3b13dcd72ae3db 126 vnc4_4.1.1+X4.3.0+t.orig.tar.gz
 e9348908e67469095cc9f17a4d9624e1e2af3ea8 35652 
vnc4_4.1.1+X4.3.0+t-1.debian.tar.xz
 230b27ff5fc07ba0696ccf5047a93bdf29cf9f57 7208 
vnc4server_4.1.1+X4.3.0+t-1_amd64.deb
 e84a03b9c68cc803f54740718eb2e7e4ba2eb510 7164 
xvnc4viewer_4.1.1+X4.3.0+t-1_amd64.deb
Checksums-Sha256:
 ab367f009cad98e40411e21a6fdbce413e2307589fa8e667d27c32702c01546e 1733 
vnc4_4.1.1+X4.3.0+t-1.dsc
 881e1d055cb6abf0fdc3e1f6a0aeb12dc5761bb9de6fbb7542e8f3dff479e60b 126 
vnc4_4.1.1+X4.3.0+t.orig.tar.gz
 7f516aaa85b8eda418ae1e2320eaa855302b9e508bd562255bc55f79a03e2f8c 35652 
vnc4_4.1.1+X4.3.0+t-1.debian.tar.xz
 d3a5f477c1d8ff4222b0da77102c193ca1982bcc8f289781249729419ad2c4a1 7208 
vnc4server_4.1.1+X4.3.0+t-1_amd64.deb
 4854cafab70e4aa6087ae8886849d89aa53e93c7df1248f5a7ee13f533ac3940 7164 
xvnc4viewer_4.1.1+X4.3.0+t-1_amd64.deb
Files:
 cbb398b446a3bbdd3a087de2d4c66112 1733 x11 optional vnc4_4.1.1+X4.3.0+t-1.dsc
 6da3076f284ed6d70dad26cb190b5565 126 x11 optional 
vnc4_4.1.1+X4.3.0+t.orig.tar.gz
 

Bug#811632: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 22:19:12 +
with message-id 
and subject line Bug#811632: fixed in hupnp 1.0.0-1.1
has caused the Debian Bug report #811632,
regarding FTBFS with GCC 6: cannot convert x to y
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.)


-- 
811632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hupnp
Version: 1.0.0-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -c -m64 -pipe -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W 
> -fPIC -DH_BUILD_UPNP_CORE_LIB -DDEBUG -DQT_NO_DEBUG -DQT_XML_LIB 
> -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXml -I/usr/include/qt4 
> -Iinclude -Ilib/qtsoap-2.7-opensource/src -Iobj -o 
> obj/moc_hdevicehost_ssdp_handler_p.o obj/moc_hdevicehost_ssdp_handler_p.cpp
> src/devicehosting/devicehost/hservermodel_creator_p.cpp: In member function 
> 'Herqq::Upnp::HServerDevice* 
> Herqq::Upnp::HServerModelCreator::parseDevice(const QDomElement&, 
> Herqq::Upnp::HServerDevice*)':
> src/devicehosting/devicehost/hservermodel_creator_p.cpp:496:16: error: cannot 
> convert 'bool' to 'Herqq::Upnp::HServerDevice*' in return
>  return false;
> ^
> 
> src/devicehosting/devicehost/hservermodel_creator_p.cpp:563:24: error: cannot 
> convert 'bool' to 'Herqq::Upnp::HServerDevice*' in return
>  return false;
> ^
> 
> g++ -c -m64 -pipe -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W 
> -fPIC -DH_BUILD_UPNP_CORE_LIB -DDEBUG -DQT_NO_DEBUG -DQT_XML_LIB 
> -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXml -I/usr/include/qt4 
> -Iinclude -Ilib/qtsoap-2.7-opensource/src -Iobj -o 
> obj/moc_hdevicehost_http_server_p.o obj/moc_hdevicehost_http_server_p.cpp
> g++ -c -m64 -pipe -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W 
> -fPIC -DH_BUILD_UPNP_CORE_LIB -DDEBUG -DQT_NO_DEBUG -DQT_XML_LIB 
> -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXml -I/usr/include/qt4 
> -Iinclude -Ilib/qtsoap-2.7-opensource/src -Iobj -o 
> obj/moc_hevent_subscriber_p.o obj/moc_hevent_subscriber_p.cpp
> Makefile.src:1328: recipe for target 'obj/hservermodel_creator_p.o' failed
> make[3]: *** [obj/hservermodel_creator_p.o] Error 1
> make[3]: *** Waiting for unfinished jobs

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: hupnp
Source-Version: 1.0.0-1.1

We believe that the bug you reported is fixed in the latest version of
hupnp, 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 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jan Luca Naumann  (supplier of updated hupnp 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: Sat, 07 Jan 2017 22:35:31 +0100
Source: hupnp
Binary: libhupnp1 libhupnp-dev libqtsolutions-soap-2.7-1
Architecture: source amd64
Version: 1.0.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Jan 

Processed: Re: Bug#850569: jstest-gtk: Crash for missing data files

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 850022 -1
Bug #850022 [jstest-gtk] jstest-gtk: Does Not Open
Bug #850569 [jstest-gtk] jstest-gtk: Crash for missing data files
Severity set to 'grave' from 'important'
Merged 850022 850569

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

Bug#850430: fixed in postfix 3.1.4-2

[Wolfgang Walter]

On Fri, 06 Jan 2017 16:49:17 + LaMont Jones  wrote:
> Source: postfix
> Source-Version: 3.1.4-2
> 
> We believe that the bug you reported is fixed in the latest version of
> postfix, which is due to be installed in the Debian FTP archive.

This does not fix the problem here. What fixes the problem is making a symlink 
to smtp called lmtp and changing master.cf to call lmtp instead of smtp.

I don't think you can call smtp as smtp if you want it to act in lmtp mode. 
Here code from smtp.c:
(from https://git.launchpad.net/postfix/tree/src/smtp/smtp.c?h=stable/v3.1)


/*
 * XXX At this point, var_procname etc. are not initialized.
 * 
 * The process name, "smtp" or "lmtp", determines the protocol, the DSN
 * server reply type, SASL service information lookup, and more. Prepare
 * for the possibility there may be another personality.
 */
sane_procname = sane_basename((VSTRING *) 0, argv[0]);
if (strcmp(sane_procname, "smtp") == 0)
smtp_mode = 1;
else if (strcmp(sane_procname, "lmtp") == 0)
smtp_mode = 0;


So I think there must be a link lmtp => smtp and in master.cf it sould be

lmtp  unix  -   -   -   -   -   lmtp

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

Bug#811745: marked as done (ncc: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 21:33:44 +
with message-id 
and subject line Bug#811745: fixed in ncc 2.8-2.1
has caused the Debian Bug report #811745,
regarding ncc: FTBFS with GCC 6: narrowing conversion
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.)


-- 
811745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ncc
Version: 2.8-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -g -O2 -Wno-write-strings -Wl,-z,relro main.C objdir/*.o -o objdir/nccgen 
> Compiling nccnav viewer.
> make[2]: Entering directory '/<>/nccnav'
> g++ -Wl,-z,relro -g -Wno-write-strings nccnav.C -I.. -lncurses -o nccnav 
> ../objdir/dbstree.o ../objdir/inttree.o
> nccnav.C:334:22: error: narrowing conversion of '-1' from 'int' to 'unsigned 
> int' inside { } [-Wnarrowing]
>  } NoChunk = { ~0, ~0 };
>   ^
> 
> nccnav.C:334:22: error: narrowing conversion of '-1' from 'int' to 'unsigned 
> int' inside { } [-Wnarrowing]
> Makefile:10: recipe for target '../objdir/nccnav' failed
> make[2]: *** [../objdir/nccnav] Error 1
> make[2]: Leaving directory '/<>/nccnav'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: ncc
Source-Version: 2.8-2.1

We believe that the bug you reported is fixed in the latest version of
ncc, 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 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
ncc 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: Sat, 07 Jan 2017 22:10:15 +0100
Source: ncc
Binary: ncc
Architecture: source amd64
Version: 2.8-2.1
Distribution: sid
Urgency: medium
Maintainer: Anuradha Weeraman (anu) 
Changed-By: John Paul Adrian Glaubitz 
Description:
 ncc- C source code analyzer
Closes: 811745
Changes:
 ncc (2.8-2.1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * Fixed type for file_chunk::start,end from unsigned int to int
 to fix narrowing conversion issues with gcc-6 (Closes: #811745)
Checksums-Sha1:
 d4e51eafc7ed2c8834efa128f41bd2cc6007b5d8 1711 ncc_2.8-2.1.dsc
 dbe5aabcd194b4d5818493bfd30cabe6bb007b25 5948 ncc_2.8-2.1.diff.gz
 42c3c83dac926e8d2234f5566b03b152eaac6d91 173414 ncc-dbgsym_2.8-2.1_amd64.deb
 135195bf342fc32088804f707539f590216f5a3f 4653 ncc_2.8-2.1_amd64.buildinfo
 5ab5164b5360b5c7d10b9207fb85e3147991bd66 110192 ncc_2.8-2.1_amd64.deb
Checksums-Sha256:
 6c5338db82bf9cc1d5f953b437fca5ccbed25d9376eefba7ad6daaea60e81f4f 1711 
ncc_2.8-2.1.dsc
 7f662b7f103086342a34cb275fe461d541dfa777f91b0ab02c517f9eacb4d492 5948 
ncc_2.8-2.1.diff.gz
 1e78bc280dfd3288e6601761067825b9e73175ab03804cda418254f4be5f0c9a 173414 
ncc-dbgsym_2.8-2.1_amd64.deb
 e3fd05413d92c7d1412d1dc31d912d57c81214116863be2e55e0e84df0f116d2 4653 
ncc_2.8-2.1_amd64.buildinfo
 d1da6b67c96b7bcb6946b966f29bc41d057c0530382b4dff9e0e2c2e876ae64e 110192 
ncc_2.8-2.1_amd64.deb
Files:
 874dd8f58ca63ed101b43b34b34a1414 1711 devel optional ncc_2.8-2.1.dsc
 779f8c4a80530ccb2c8739f526266d72 5948 devel optional ncc_2.8-2.1.diff.gz
 175256d9b7b93e09ca2efb6f8643aed1 173414 debug extra 
ncc-dbgsym_2.8-2.1_amd64.deb
 4b2ccd67021b648ed015f6b3b751ce81 4653 devel optional 
ncc_2.8-2.1_amd64.buildinfo
 a4133204299f27040df20a98cf182944 110192 devel optional ncc_2.8-2.1_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#850320: mock: CVE-2016-6299: privilige escalation via mock-scm

[Tzafrir Cohen]

On Fri, Jan 06, 2017 at 01:37:58PM +, Holger Levsen wrote:
> Hi Tzafrir,
> 
> On Fri, Jan 06, 2017 at 12:25:07AM +0100, Tzafrir Cohen wrote:
> > The version in Jessie-backports seems to be the only one affected by it.
> 
> will you upload a fixed version to jessie-bpo or should I? (I'd be happy
> if you did, but I was the person introducing mock to bpo, so I'd take
> responsibility and fix, if needed.)

I prepared a version in the branch jessie-backports in git[1].

It seems to work OK here. I don't hae my key in the backports keyring,
so I prefer that you upload it.


-- 
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il ||  best
tzaf...@debian.org|| friend

Bug#811727: marked as done (nzb: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 21:18:39 +
with message-id 
and subject line Bug#811727: fixed in nzb 0.2-1.1
has caused the Debian Bug report #811727,
regarding nzb: FTBFS with GCC 6: narrowing conversion
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.)


-- 
811727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nzb
Version: 0.2-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -c -m64 -pipe -O2 -D_REENTRANT -Wall -W -DQT_NO_DEBUG -DQT_XML_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui 
> -I/usr/include/qt4/QtXml -I/usr/include/qt4 -I. -I. -o downloader.o 
> downloader.cpp
> downloader.cpp: In member function 'void 
> Downloader::gotError(QAbstractSocket::SocketError)':
> downloader.cpp:180:56: warning: unused parameter 'err' [-Wunused-parameter]
>  void Downloader::gotError(QAbstractSocket::SocketError err)
> ^~~
> 
> g++ -c -m64 -pipe -O2 -D_REENTRANT -Wall -W -DQT_NO_DEBUG -DQT_XML_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui 
> -I/usr/include/qt4/QtXml -I/usr/include/qt4 -I. -I. -o decoder.o decoder.cpp
> decoder.cpp: In member function 'void Decoder::uDecode(int, int, bool, int)':
> decoder.cpp:357:5: warning: suggest explicit braces to avoid ambiguous 'else' 
> [-Wparentheses]
>   if (!multi || (multi && type == 1))
>  ^
> 
> decoder.cpp:340:7: warning: variable 'badnl' set but not used 
> [-Wunused-but-set-variable]
>   bool badnl = false; // Newlines only \n, not \r\n,
>^
> 
> decoder.cpp: In member function 'void Decoder::crcAdd(int*, int)':
> decoder.cpp:485:2: error: narrowing conversion of '3993919788u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
>   };
>   ^
> 
> decoder.cpp:485:2: error: narrowing conversion of '2567524794u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '3915621685u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '2657392035u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '3772115230u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '2547177864u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '3887607047u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '2428444049u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '4089016648u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '2227061214u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '4107580753u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '2211677639u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> decoder.cpp:485:2: error: narrowing conversion of '4251122042u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
...

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: nzb
Source-Version: 0.2-1.1

We believe that the bug you reported is fixed in the latest version of
nzb, 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 

Bug#849382: [apt] Every package on the system gets silently upgraded to backports. The result is severe system breakage, malfunctioning and data loss.

[Sven Hartge]

On 07.01.2017 21:24, Julian Andres Klode wrote:
> On Sat, Jan 07, 2017 at 09:15:15PM +0100, Sven Hartge wrote:
>> On Mon, 26 Dec 2016 14:40:05 +0100 (CET) <34tg...@tutanota.com> wrote:
>>
>>> I use Debian 8 64bit with GNOME installed with standard install
>>> procedure from netinstall and using tasksel. This occured to me the
>>> second time. First time was a year ago, I reinstalled Debian then and
>>> a year after this happens again. Both occurences were on Debian 8,
>>> stable at the time.
>>
>> I have seen this as well and know under which circumstances this happens:
>>
>> a) backports repository is enabled in source.list (obviously)
>> b) "apt update" is run and all normal repositories fail to download or
>> are invalid
>>
>> When this happens, apt will happily upgrade all packages where a
>> backported version exists to that version.
> 
> This should not happen. The old repository state should be used, and thus
> the pinning should not change. 

That's what I thought as well.

> That said, maybe that only works right in 1.1 and newer, I don't
> really know.

I have definitely seen this in Jessie, maybe even Wheezy (memory a bit
fuzzy in that regard).

I run apticron on all our servers (~250) and it happened about once a
month that one (a different one every time) of the server prompted to
upgrade all packages to their backports-version.

But after switching from httpredir.debian.org to deb.debian.org this
problem did not occur again, so far at least.

But there is absolutely something problematic with the version in Jessie
where it is possible to trigger the behavior from this bug report.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Processed: Re: lambdabot FTBFS in stretch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 850286 lambdabot FTBFS in stretch: missing build-dependencies
Bug #850286 [lambdabot] lambdabot FTBFS in stretch
Changed Bug title to 'lambdabot FTBFS in stretch: missing build-dependencies' 
from 'lambdabot FTBFS in stretch'.
> thanks
Stopping processing here.

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

Bug#849382: [apt] Every package on the system gets silently upgraded to backports. The result is severe system breakage, malfunctioning and data loss.

[Julian Andres Klode]

On Sat, Jan 07, 2017 at 09:15:15PM +0100, Sven Hartge wrote:
> On Mon, 26 Dec 2016 14:40:05 +0100 (CET) <34tg...@tutanota.com> wrote:
> 
> > I use Debian 8 64bit with GNOME installed with standard install
> > procedure from netinstall and using tasksel. This occured to me the
> > second time. First time was a year ago, I reinstalled Debian then and
> > a year after this happens again. Both occurences were on Debian 8,
> > stable at the time.
> 
> I have seen this as well and know under which circumstances this happens:
> 
> a) backports repository is enabled in source.list (obviously)
> b) "apt update" is run and all normal repositories fail to download or
> are invalid
> 
> When this happens, apt will happily upgrade all packages where a
> backported version exists to that version.

This should not happen. The old repository state should be used, and thus
the pinning should not change. 

That said, maybe that only works right in 1.1 and newer, I don't
really know.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#849382: [apt] Every package on the system gets silently upgraded to backports. The result is severe system breakage, malfunctioning and data loss.

[Sven Hartge]

On Mon, 26 Dec 2016 14:40:05 +0100 (CET) <34tg...@tutanota.com> wrote:

> I use Debian 8 64bit with GNOME installed with standard install
> procedure from netinstall and using tasksel. This occured to me the
> second time. First time was a year ago, I reinstalled Debian then and
> a year after this happens again. Both occurences were on Debian 8,
> stable at the time.

I have seen this as well and know under which circumstances this happens:

a) backports repository is enabled in source.list (obviously)
b) "apt update" is run and all normal repositories fail to download or
are invalid

When this happens, apt will happily upgrade all packages where a
backported version exists to that version.

Why?

Because of the pin value of a package in such a case. For example:

# apt-cache policy exim4
exim4:
  Installed: 4.84.2-2+deb8u2
  Candidate: 4.84.2-2+deb8u2
  Version table:
 4.88~RC6-2~bpo8+1 0
100 http://deb.debian.org/debian/ jessie-backports/main amd64
Packages
 *** 4.84.2-2+deb8u2 0
500 http://deb.debian.org/debian-security/ jessie/updates/main
amd64 Packages
500 http://security.debian.org/ jessie/updates/main amd64 Packages
100 /var/lib/dpkg/status
 4.84.2-2+deb8u1 0
500 http://deb.debian.org/debian/ jessie/main amd64 Packages

The backports pacakges has a value of 100 as has the installed package.
The package from the normal repository is at 500 and thus the candidate.

If the normal repositories fail to download and are invalid the
backported package and the installed package both are the only
candidates left (and are both at the same pin value) and because the
backported package has a higher version it is installed.

Workaround:

Have more than one mirror configured so that the chance is higher that
at least one is valid.

Grüße,
Sven.

Bug#847577: [PATCH] integrit: Generate Built-Using field

[Andreas Henriksson]

Control: tags -1 + patch

Hello!

Please see attached patch to generate the Built-Using field.

(This needs to be generate as the Built-Using is supposed to declare a
strict relation to the exact version of dietlibc that was used to build
the package.)

Regards,
Andreas Henriksson
diff -u integrit-4.1/debian/changelog integrit-4.1/debian/changelog
--- integrit-4.1/debian/changelog
+++ integrit-4.1/debian/changelog
@@ -1,3 +1,10 @@
+integrit (4.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Generate Built-Using field for dietlibc (Closes: #847577)
+
+ -- Andreas Henriksson   Sat, 07 Jan 2017 20:39:30 +0100
+
 integrit (4.1-1) unstable; urgency=low
 
   * new upstream release.
diff -u integrit-4.1/debian/control integrit-4.1/debian/control
--- integrit-4.1/debian/control
+++ integrit-4.1/debian/control
@@ -9,6 +9,7 @@
 Architecture: any
 Depends: ${shlibs:Depends}
 Recommends: cron, mailx
+Built-Using: ${Built-Using}
 Description: A file integrity verification program
  Integrit helps you determine whether an intruder has modified your
  system.  Without the use of integrit, a sysadmin wouldn't know if the
diff -u integrit-4.1/debian/rules integrit-4.1/debian/rules
--- integrit-4.1/debian/rules
+++ integrit-4.1/debian/rules
@@ -100,7 +100,8 @@
 binary-indep:
 
 binary-arch: deb-checkdir deb-checkuid install integrit.deb
-	dpkg-gencontrol -isp -pintegrit -P'$(DIR)'
+	dpkg-gencontrol -isp -pintegrit -P'$(DIR)' \
+		-VBuilt-Using="$(shell dpkg-query -f '$${source:Package} (= $${source:Version}), ' -W dietlibc-dev)"
 	dpkg -b '$(DIR)' ..
 
 binary: binary-indep binary-arch

Processed: [PATCH] integrit: Generate Built-Using field

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #847577 [integrit] Embeds dietlibc (GPL) but does not have a Built-Using 
field
Added tag(s) patch.

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

Bug#850528: marked as done (firejail: CVE-2017-5207: root shell via --bandwidth and --shell)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 19:48:28 +
with message-id 
and subject line Bug#850528: fixed in firejail 0.9.44.4-1
has caused the Debian Bug report #850528,
regarding firejail: CVE-2017-5207: root shell via --bandwidth and --shell
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.)


-- 
850528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firejail
Version: 0.9.44.2-1
Severity: grave
Tags: upstream security patch fixed-upstream
Justification: user security hole
Forwarded: https://github.com/netblue30/firejail/issues/1023

Hi

There is no CVE assigned for this one yet: 

https://github.com/netblue30/firejail/issues/1023
https://github.com/netblue30/firejail/commit/5d43fdcd215203868d440ffc42036f5f5ffc89fc

CVE requested here:

http://www.openwall.com/lists/oss-security/2017/01/07/3

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: firejail
Source-Version: 0.9.44.4-1

We believe that the bug you reported is fixed in the latest version of
firejail, 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 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated firejail 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: Sat, 07 Jan 2017 20:24:40 +0100
Source: firejail
Binary: firejail
Architecture: source
Version: 0.9.44.4-1
Distribution: unstable
Urgency: high
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Description:
 firejail   - sandbox to restrict the application environment
Closes: 850528 850558
Changes:
 firejail (0.9.44.4-1) unstable; urgency=high
 .
   * New upstream release.
 - Security fixes for: CVE-2017-5180, CVE-2017-5206, CVE-2017-5207
   (Closes: #850528, #850558)
   * Drop patches applied upstream.
Checksums-Sha1:
 a87a960ef7c9d87e55dece847f90691ee120fa47 2375 firejail_0.9.44.4-1.dsc
 710de2e9791142edcc6ab46b64d595e09ff4071d 213648 firejail_0.9.44.4.orig.tar.xz
 9dfa38cf6708cf25834919a650784e9808684d28 473 firejail_0.9.44.4.orig.tar.xz.asc
 24f52ba92871e14d0f93405c0ac8f5f6da1cc809 6028 firejail_0.9.44.4-1.debian.tar.xz
Checksums-Sha256:
 f91186d24681e0d47f3ad6af121948cb5c62b61151fd2283aa99c530fb3fcd8d 2375 
firejail_0.9.44.4-1.dsc
 2d70a2cd554835db0e2eba201c0466e247fbaa2b60c86abd34b9170e0eebc10f 213648 
firejail_0.9.44.4.orig.tar.xz
 965d6ce0416680baf6d6028759ac8a90a13a672342172fbbacdde04528b9f7a7 473 
firejail_0.9.44.4.orig.tar.xz.asc
 bc9f7abd0ee38d1916175854422218edf385564efbbaee17fee00ab467114629 6028 
firejail_0.9.44.4-1.debian.tar.xz
Files:
 47e66ccff2cbbca333d58226a7855198 2375 utils optional firejail_0.9.44.4-1.dsc
 d1b77101fd0e35a18242d7593486d984 213648 utils optional 
firejail_0.9.44.4.orig.tar.xz
 4c223fec5bcddb0cc56cc5b16f11 473 utils optional 
firejail_0.9.44.4.orig.tar.xz.asc
 3098bae66a536e9c7ca3d331140f50b3 6028 utils optional 
firejail_0.9.44.4-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2Pb6feok2Q1urHM7zPBJKNsO6qcFAlhxQJQACgkQzPBJKNsO
6qdJWxAA0jyQmPE8+QJe7DyE+QP7GmtvyCHA0KecwH3iaaQXzv8ZyhPiPNg1FOgX
nfbyScIBpvDZr9u4Xb3n3hEC79KzvhiZprhsJ9l2r9HZEtcKbikvv6gH1FPg15fa
GGTybS7QfXv0AAXRelz+fI6wKqVSrs0pjVfLLt8TKPgzn/2FGCzGFsJkryaGemUi
LkW00MNCB2lIKjav6rEMIjlAAL5IzP6a0oKQtsBOyy3RN1W6X21ApzVOpyxy8+4s
xxFtkLo6DdXrtsIAeVbgs3tcmPbeE9/uxlFFWeXyhv2E5qSu1UxUviyh01K7ELgn
8vlJ0CHDzr317EhlKx3DkGMPvUXbqn1JQhE5dX8PYXwofOe704XbBpN8nV6dxCx7
GUmVPFbo7GbqD+1YE6sujTFovv+cbk9X1+T4Q5xmekwrt2nT9si72F0oUQeKiplj
rgDOz0MCOoVPFoTMFs+cRqL7v01Z/QhNdz3LE/b2pBbOe0nHdnLjOqyEMkYQr7kY
MbNNztpnmnS8uzA0NatDljfKNPzk04/f57S91g49NP0yEZRhbomy29Og//6c76qJ
z1xrOqk0gLB9hZgHrAf0KuYWb7FFLe9TXtQFzxNK8tt8zfsTC37gGD0FauF8dj0x
oBubMaPy64ckOT5th3GEQ0kRyJey5L6mSgFuclUCzHQYq+KF2/4=
=g3BU
-END PGP SIGNATURE End Message ---

Bug#850558: marked as done (firejail: CVE-2017-5206)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 19:48:28 +
with message-id 
and subject line Bug#850558: fixed in firejail 0.9.44.4-1
has caused the Debian Bug report #850558,
regarding firejail: CVE-2017-5206
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.)


-- 
850558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firejail
Version: 0.9.44.2-1
Severity: grave
Tags: security upstream patch fixed-upstream
Justification: user security hole

Hi,

the following vulnerability was published for firejail.

CVE-2017-5206[0]:
| allows ptrace with --allow-debuggers, which allows a
| sandboxed program to escape the seccomp profile by rewriting
| permitted system calls into unpermitted ones pre-Linux-4.8.

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-5206
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5206
[1] 
https://github.com/netblue30/firejail/commit/6b8dba29d73257311564ee7f27b9b14758cc693e

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: firejail
Source-Version: 0.9.44.4-1

We believe that the bug you reported is fixed in the latest version of
firejail, 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 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated firejail 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: Sat, 07 Jan 2017 20:24:40 +0100
Source: firejail
Binary: firejail
Architecture: source
Version: 0.9.44.4-1
Distribution: unstable
Urgency: high
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Description:
 firejail   - sandbox to restrict the application environment
Closes: 850528 850558
Changes:
 firejail (0.9.44.4-1) unstable; urgency=high
 .
   * New upstream release.
 - Security fixes for: CVE-2017-5180, CVE-2017-5206, CVE-2017-5207
   (Closes: #850528, #850558)
   * Drop patches applied upstream.
Checksums-Sha1:
 a87a960ef7c9d87e55dece847f90691ee120fa47 2375 firejail_0.9.44.4-1.dsc
 710de2e9791142edcc6ab46b64d595e09ff4071d 213648 firejail_0.9.44.4.orig.tar.xz
 9dfa38cf6708cf25834919a650784e9808684d28 473 firejail_0.9.44.4.orig.tar.xz.asc
 24f52ba92871e14d0f93405c0ac8f5f6da1cc809 6028 firejail_0.9.44.4-1.debian.tar.xz
Checksums-Sha256:
 f91186d24681e0d47f3ad6af121948cb5c62b61151fd2283aa99c530fb3fcd8d 2375 
firejail_0.9.44.4-1.dsc
 2d70a2cd554835db0e2eba201c0466e247fbaa2b60c86abd34b9170e0eebc10f 213648 
firejail_0.9.44.4.orig.tar.xz
 965d6ce0416680baf6d6028759ac8a90a13a672342172fbbacdde04528b9f7a7 473 
firejail_0.9.44.4.orig.tar.xz.asc
 bc9f7abd0ee38d1916175854422218edf385564efbbaee17fee00ab467114629 6028 
firejail_0.9.44.4-1.debian.tar.xz
Files:
 47e66ccff2cbbca333d58226a7855198 2375 utils optional firejail_0.9.44.4-1.dsc
 d1b77101fd0e35a18242d7593486d984 213648 utils optional 
firejail_0.9.44.4.orig.tar.xz
 4c223fec5bcddb0cc56cc5b16f11 473 utils optional 
firejail_0.9.44.4.orig.tar.xz.asc
 3098bae66a536e9c7ca3d331140f50b3 6028 utils optional 
firejail_0.9.44.4-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2Pb6feok2Q1urHM7zPBJKNsO6qcFAlhxQJQACgkQzPBJKNsO
6qdJWxAA0jyQmPE8+QJe7DyE+QP7GmtvyCHA0KecwH3iaaQXzv8ZyhPiPNg1FOgX
nfbyScIBpvDZr9u4Xb3n3hEC79KzvhiZprhsJ9l2r9HZEtcKbikvv6gH1FPg15fa
GGTybS7QfXv0AAXRelz+fI6wKqVSrs0pjVfLLt8TKPgzn/2FGCzGFsJkryaGemUi
LkW00MNCB2lIKjav6rEMIjlAAL5IzP6a0oKQtsBOyy3RN1W6X21ApzVOpyxy8+4s
xxFtkLo6DdXrtsIAeVbgs3tcmPbeE9/uxlFFWeXyhv2E5qSu1UxUviyh01K7ELgn
8vlJ0CHDzr317EhlKx3DkGMPvUXbqn1JQhE5dX8PYXwofOe704XbBpN8nV6dxCx7
GUmVPFbo7GbqD+1YE6sujTFovv+cbk9X1+T4Q5xmekwrt2nT9si72F0oUQeKiplj
rgDOz0MCOoVPFoTMFs+cRqL7v01Z/QhNdz3LE/b2pBbOe0nHdnLjOqyEMkYQr7kY
MbNNztpnmnS8uzA0NatDljfKNPzk04/f57S91g49NP0yEZRhbomy29Og//6c76qJ
z1xrOqk0gLB9hZgHrAf0KuYWb7FFLe9TXtQFzxNK8tt8zfsTC37gGD0FauF8dj0x
oBubMaPy64ckOT5th3GEQ0kRyJey5L6mSgFuclUCzHQYq+KF2/4=
=g3BU

Bug#850413: marked as done (python-axolotl: FTBFS (ValueError: CTR mode needs counter parameter, not IV))

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 19:33:57 +
with message-id 
and subject line Bug#850413: fixed in python-axolotl 0.1.35-3
has caused the Debian Bug report #850413,
regarding python-axolotl: FTBFS (ValueError: CTR mode needs counter parameter, 
not IV)
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.)


-- 
850413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-axolotl
Version: 0.1.35-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,quilt --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   debian/rules override_dh_quilt_patch
make[1]: Entering directory '/<>'
dh_quilt_patch
Applying patch 000-rename-protobuf-genetared-files.patch
patching file axolotl/groups/state/senderkeyrecord.py
patching file axolotl/groups/state/senderkeystate.py
patching file axolotl/identitykeypair.py
patching file axolotl/protocol/keyexchangemessage.py
patching file axolotl/protocol/prekeywhispermessage.py
patching file axolotl/protocol/senderkeydistributionmessage.py

[... snipped ...]

==
ERROR: test_basicSessionV2 (axolotl.tests.test_sessioncipher.SessionCipherTest)
--
Traceback (most recent call last):
  File "axolotl/tests/test_sessioncipher.py", line 21, in test_basicSessionV2
self.runInteraction(aliceSessionRecord, bobSessionRecord)
  File "axolotl/tests/test_sessioncipher.py", line 40, in runInteraction
message = aliceCipher.encrypt(alicePlaintext)
  File "axolotl/sessioncipher.py", line 53, in encrypt
ciphertextBody = self.getCiphertext(sessionVersion, messageKeys, 
paddedMessage)
  File "axolotl/sessioncipher.py", line 217, in getCiphertext
cipher = self.getCipher_v2(messageKeys.getCipherKey(), 
messageKeys.getCounter())
  File "axolotl/sessioncipher.py", line 247, in getCipher_v2
cipher = AES.new(key, AES.MODE_CTR, IV=bytes(ivBytes), counter=ctr)
  File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94, in new
return AESCipher(key, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59, in 
__init__
blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line 141, 
in __init__
self._cipher = factory.new(key, *args, **kwargs)
ValueError: CTR mode needs counter parameter, not IV

==
ERROR: test_basicPreKeyV2 (axolotl.tests.test_sessionbuilder.SessionBuilderTest)
--
Traceback (most recent call last):
  File "axolotl/tests/test_sessionbuilder.py", line 52, in test_basicPreKeyV2
outgoingMessage = aliceSessionCipher.encrypt(originalMessage)
  File "axolotl/sessioncipher.py", line 53, in encrypt
ciphertextBody = self.getCiphertext(sessionVersion, messageKeys, 
paddedMessage)
  File "axolotl/sessioncipher.py", line 217, in getCiphertext
cipher = self.getCipher_v2(messageKeys.getCipherKey(), 
messageKeys.getCounter())
  File "axolotl/sessioncipher.py", line 247, in getCipher_v2
cipher = AES.new(key, AES.MODE_CTR, IV=bytes(ivBytes), counter=ctr)
  File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94, in new
return AESCipher(key, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59, in 
__init__
blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line 141, 
in __init__
self._cipher = factory.new(key, *args, **kwargs)
ValueError: CTR mode needs counter parameter, not IV

--
Ran 22 tests in 0.246s

FAILED (errors=2)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover 
-v 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules 

Bug#749661: ifuse: Segfault

[Andreas Henriksson]

Control: tags -1 + moreinfo

Hello Tino, "George B.",

Thanks for the bug report and the backtrace.

On Sun, Jun 29, 2014 at 12:55:41PM +0200, Tino Keitel wrote:
[...]
> #2  0x7777d1da in plist_new_string (val=0x0) at plist.c:118
> #3  0x7798b94c in pair_record_generate (pair_record=0x7fffe0d0, 
> client=0x650310) at lockdown.c:879
[...]

This error looks to me like it would be an issue in libimobiledevice
lockdown code rather than in what ifuse passes into it.

Seeing that libimobiledevice has new upstream releases uploaded since
this bug was reported I wonder if you can still reproduce this
issue or if it might have been solved in imobiledevice since?

Regards,
Andreas Henriksson

Processed: Re: ifuse: Segfault

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #749661 [ifuse] ifuse: Segfault
Added tag(s) moreinfo.

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

Processed: limit source to transmission, tagging 835800

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

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

> tags 835800 + pending
Bug #835800 [src:transmission] transmission: FTBFS with openssl 1.1.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#850559: dune-pdelab: FTBFS (not enough slots available)

[Santiago Vila]

Package: src:dune-pdelab
Version: 2.5.0~20161204gdb53a76-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --builddirectory=build
   dh_testdir -i -O--parallel -O--builddirectory=build
   dh_update_autotools_config -i -O--parallel -O--builddirectory=build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DBUILD_SHARED_LIBS=1
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DBUILD_SHARED_LIBS=1
-- The C compiler identification is GNU 6.2.1
-- The CXX compiler identification is GNU 6.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done

[... snipped ...]

Status:FAILED
Output:
   
--
   There are not enough slots available in the system to satisfy the 2 
slots
   that were requested by the application:
 testnonoverlappingsinglephaseflow-ug
   
   Either request fewer slots for your application, or make more slots 
available
   for use.
   
--

==
Name:  testnonoverlappingsinglephaseflow-boilerplate-mpi-2
FullName:  
./dune/pdelab/test/testnonoverlappingsinglephaseflow-boilerplate-mpi-2
Status:FAILED
Output:
   
--
   There are not enough slots available in the system to satisfy the 2 
slots
   that were requested by the application:
 testnonoverlappingsinglephaseflow-boilerplate
   
   Either request fewer slots for your application, or make more slots 
available
   for use.
   
--

==
Name:  testnonoverlapping-mpi-2
FullName:  ./dune/pdelab/test/testnonoverlapping-mpi-2
Status:FAILED
Output:
   
--
   There are not enough slots available in the system to satisfy the 2 
slots
   that were requested by the application:
 testnonoverlapping
   
   Either request fewer slots for your application, or make more slots 
available
   for use.
   
--

/usr/share/dune/dune-debian.mk:16: recipe for target 'override_dh_auto_test' 
failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is how the build ends, and also the relevant part.

The bug should be reproducible with sbuild on a single CPU virtual machine.

Thanks.

Bug#850558: firejail: CVE-2017-5206

[Salvatore Bonaccorso]

Source: firejail
Version: 0.9.44.2-1
Severity: grave
Tags: security upstream patch fixed-upstream
Justification: user security hole

Hi,

the following vulnerability was published for firejail.

CVE-2017-5206[0]:
| allows ptrace with --allow-debuggers, which allows a
| sandboxed program to escape the seccomp profile by rewriting
| permitted system calls into unpermitted ones pre-Linux-4.8.

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-5206
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5206
[1] 
https://github.com/netblue30/firejail/commit/6b8dba29d73257311564ee7f27b9b14758cc693e

Regards,
Salvatore

Bug#846728: gcr: FTBFS: Test failures

[Lucas Nussbaum]

On 07/01/17 at 17:00 +0100, Michael Biebl wrote:
> Am 07.01.2017 um 08:16 schrieb Lucas Nussbaum:
> > 
> > On 07/01/17 at 01:15 +0100, Michael Biebl wrote:
> 
> >> I just tried to reproduce this in an up-to-date sid chroot and the
> >> package built fine. The built was using gnupg_2.1.16-2 whereas my chroot
> >> has 2.1.17-3. I wonder if that makes a difference.
> >>
> >> Can you try to reproduce the issue?
> > 
> > I just did a rebuild of testing. Yes, I can reproduce it, see attached
> > log.
> 
> Hm, odd. Any idea how your build chroot differs from a newly created
> pbuilder chroot?
> Any help appreciated with finding out what exactly triggers the
> test-suite / gnupg failure.

It also fails with gnupg 2.1.17-3 here.

In test-suite.org, the failing test has:
# Gcr-DEBUG: running command: /usr/bin/gpg --homedir /tmp/gcr-tests.5I3XTY 
--list-secret-keys --fixed-list-mode --with-colons --with-fingerprint
# Gcr-DEBUG: process environment: LOCALE=C
# Gcr-DEBUG: process started: 6231
# Gcr-DEBUG: closing fd: 8
gpg: starting migration from earlier GnuPG versions
# Gcr-DEBUG: received error line: gpg: starting migration from earlier GnuPG 
versions
gpg: porting secret keys from '/tmp/gcr-tests.5I3XTY/secring.gpg' to gpg-agent
# Gcr-DEBUG: received error line: gpg: porting secret keys from 
'/tmp/gcr-tests.5I3XTY/secring.gpg' to gpg-agent
**
ERROR:gcr/test-gnupg-collection.c:214:test_reload: assertion failed: 
(test->result)
# ERROR:gcr/test-gnupg-collection.c:214:test_reload: assertion failed: 
(test->result)
not ok 3 /gcr/gnupg-collection/reload


The failing lines seem to be: (./gcr/test-gnupg-collection.c:214)
_gcr_gnupg_collection_load_async (test->collection, NULL, 
on_async_ready, test);
egg_test_wait_until (2500);
g_assert (test->result);
_gcr_gnupg_collection_load_finish (test->collection, test->result, 
);
g_assert_no_error (error);

Increasing the timeout value (2500) to something big (25) makes the test 
pass.

I don't understand the logic in this test.  It seems to do something
(with a short timeout), then doing it again (with a larger timeout).
What's the point?

The machine I'm using for the tests is not slow. 63 cores
with Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz (Amazon m4.16xlarge instance).

Lucas

Bug#850553: (Tidying pde-build failures)

[Chris Lamb]

reassign 850553 javahelper
affects 850553 + eclipse-gef eclipse-anyedit eclipse-linuxtools 
eclipse-mercurialeclipse
thanks

(Also closing "duplicate" #850554 in bcc)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#850528: firejail: root shell via --bandwidth and --shell

[Salvatore Bonaccorso]

Control: retitle -1 firejail: CVE-2017-5207: root shell via --bandwidth and 
--shell

Hi

On Sat, Jan 07, 2017 at 02:33:26PM +0100, Salvatore Bonaccorso wrote:
> Source: firejail
> Version: 0.9.44.2-1
> Severity: grave
> Tags: upstream security patch fixed-upstream
> Justification: user security hole
> Forwarded: https://github.com/netblue30/firejail/issues/1023
> 
> Hi
> 
> There is no CVE assigned for this one yet: 
> 
> https://github.com/netblue30/firejail/issues/1023
> https://github.com/netblue30/firejail/commit/5d43fdcd215203868d440ffc42036f5f5ffc89fc
> 
> CVE requested here:
> 
> http://www.openwall.com/lists/oss-security/2017/01/07/3

This one has been assigned CVE-2017-5207 now.

Regards,
Salvatore

Processed: (Tidying pde-build failures)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 850553 javahelper
Bug #850553 [src:eclipse-gef] eclipse-gef: FTBFS: pde-build -a 
"-DjavacTarget=1.5 -DjavacSource=1.5 -DbuildId=dist 
-DforceContextQualifier=dist" -f org.eclipse.draw2d returned exit code 13
Bug reassigned from package 'src:eclipse-gef' to 'javahelper'.
No longer marked as found in versions eclipse-gef/3.9.100-1.
Ignoring request to alter fixed versions of bug #850553 to the same values 
previously set
> affects 850553 + eclipse-gef eclipse-anyedit eclipse-linuxtools 
> eclipse-mercurialeclipse
Bug #850553 [javahelper] eclipse-gef: FTBFS: pde-build -a "-DjavacTarget=1.5 
-DjavacSource=1.5 -DbuildId=dist -DforceContextQualifier=dist" -f 
org.eclipse.draw2d returned exit code 13
Added indication that 850553 affects eclipse-gef, eclipse-anyedit, 
eclipse-linuxtools, and eclipse-mercurialeclipse
> thanks
Stopping processing here.

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

Processed: Re: Bug#850528: firejail: root shell via --bandwidth and --shell

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 firejail: CVE-2017-5207: root shell via --bandwidth and --shell
Bug #850528 [src:firejail] firejail: root shell via --bandwidth and --shell
Changed Bug title to 'firejail: CVE-2017-5207: root shell via --bandwidth and 
--shell' from 'firejail: root shell via --bandwidth and --shell'.

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

Bug#850554: marked as done (eclipse-anyedit: FTBFS: pde-build -a "-DjavacTarget=1.5 -DjavacSource=1.5 -DbuildId=dist -DforceContextQualifier=dist" -f AnyEditTools returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 17:57:00 +
with message-id 
<1483811820.3084753.840384737.05e01...@webmail.messagingengine.com>
and subject line (Tidying pde-build failures)
has caused the Debian Bug report #850554,
regarding eclipse-anyedit: FTBFS: pde-build -a "-DjavacTarget=1.5 
-DjavacSource=1.5 -DbuildId=dist -DforceContextQualifier=dist" -f AnyEditTools 
returned exit code 13
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.)


-- 
850554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-anyedit
Version: 2.4.4-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

eclipse-anyedit fails to build from source in unstable/amd64:

  […]

 dh_auto_configure
  dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in 
use)
 dh_auto_build
  dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
 jh_setupenvironment
  jh_setupenvironment: Compatibility levels before 9 are deprecated (level 8 in 
use)
 jh_generateorbitdir
 debian/rules override_jh_compilefeatures
  make[1]: Entering directory '«BUILDDIR»'
  jh_compilefeatures --build-opts="-DjavacTarget=1.5 -DjavacSource=1.5 
-DbuildId=dist -DforceContextQualifier=dist"
  jh_compilefeatures: Compatibility levels before 9 are deprecated (level 8 in 
use)
  mkdir -p «BUILDDIR»/debian/.eclipse-build/build
  mkdir -p «BUILDDIR»/debian/.eclipse-build/build/home
  mkdir -p «BUILDDIR»/debian/.eclipse-build/build/home/workspace
  Building feature = AnyEditTools.
  Symlinking SDK into «BUILDDIR»/debian/.eclipse-build/build/SDK directory.
  /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
«BUILDDIR»/debian/.eclipse-build/build/SDK /usr/lib/eclipse
  ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
directory
  ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
directory
  ln: failed to create symbolic link 'icon.xpm': File exists
  ln: failed to create symbolic link 'notice.html': File exists
  ln: failed to create symbolic link 'readme': File exists
  ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
  ln: failed to create symbolic link 'swt-gtk.jar': File exists
  ln: failed to create symbolic link 'swt.jar': File exists
  Starting build:
  An error has occurred. See the log file
  «BUILDDIR»/debian/.eclipse-build/build/home/workspace/.metadata/.log.
  jh_compilefeatures: cd debian/.eclipse-build && 
/usr/lib/eclipse/buildscripts/pde-build -a "-DjavacTarget=1.5 -DjavacSource=1.5 
-DbuildId=dist -DforceContextQualifier=dist"  -f AnyEditTools returned exit 
code 13
  debian/rules:10: recipe for target 'override_jh_compilefeatures' failed
  make[1]: *** [override_jh_compilefeatures] Error 2
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


eclipse-anyedit.2.4.4-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
reassign 850553 javahelper
affects 850553 + eclipse-gef eclipse-anyedit eclipse-linuxtools 
eclipse-mercurialeclipse
thanks

(Also closing "duplicate" #850554 in bcc)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   ` End Message ---

Bug#850553: eclipse-gef: FTBFS: pde-build -a "-DjavacTarget=1.5 -DjavacSource=1.5 -DbuildId=dist -DforceContextQualifier=dist" -f org.eclipse.draw2d returned exit code 13

[Chris Lamb]

Source: eclipse-gef
Version: 3.9.100-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

eclipse-gef fails to build from source in unstable/amd64:

  […]

 dh_auto_configure
  dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in 
use)
 dh_auto_build
  dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
 jh_setupenvironment
  jh_setupenvironment: Compatibility levels before 9 are deprecated (level 8 in 
use)
 jh_generateorbitdir
 debian/rules override_jh_compilefeatures
  make[1]: Entering directory '«BUILDDIR»'
  jh_compilefeatures --build-opts="-DjavacTarget=1.5 -DjavacSource=1.5 
-DbuildId=dist -DforceContextQualifier=dist"
  jh_compilefeatures: Compatibility levels before 9 are deprecated (level 8 in 
use)
  mkdir -p «BUILDDIR»/debian/.eclipse-build/build
  mkdir -p «BUILDDIR»/debian/.eclipse-build/build/home
  mkdir -p «BUILDDIR»/debian/.eclipse-build/build/home/workspace
  Building feature = org.eclipse.draw2d.
  Symlinking SDK into «BUILDDIR»/debian/.eclipse-build/build/SDK directory.
  /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
«BUILDDIR»/debian/.eclipse-build/build/SDK /usr/lib/eclipse
  ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
directory
  ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
directory
  ln: failed to create symbolic link 'icon.xpm': File exists
  ln: failed to create symbolic link 'notice.html': File exists
  ln: failed to create symbolic link 'readme': File exists
  ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
  ln: failed to create symbolic link 'swt-gtk.jar': File exists
  ln: failed to create symbolic link 'swt.jar': File exists
  Starting build:
  An error has occurred. See the log file
  «BUILDDIR»/debian/.eclipse-build/build/home/workspace/.metadata/.log.
  jh_compilefeatures: cd debian/.eclipse-build && 
/usr/lib/eclipse/buildscripts/pde-build -a "-DjavacTarget=1.5 -DjavacSource=1.5 
-DbuildId=dist -DforceContextQualifier=dist"  -f org.eclipse.draw2d returned 
exit code 13
  debian/rules:10: recipe for target 'override_jh_compilefeatures' failed
  make[1]: *** [override_jh_compilefeatures] Error 2
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


eclipse-gef.3.9.100-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#850554: eclipse-anyedit: FTBFS: pde-build -a "-DjavacTarget=1.5 -DjavacSource=1.5 -DbuildId=dist -DforceContextQualifier=dist" -f AnyEditTools returned exit code 13

[Chris Lamb]

Source: eclipse-anyedit
Version: 2.4.4-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

eclipse-anyedit fails to build from source in unstable/amd64:

  […]

 dh_auto_configure
  dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in 
use)
 dh_auto_build
  dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
 jh_setupenvironment
  jh_setupenvironment: Compatibility levels before 9 are deprecated (level 8 in 
use)
 jh_generateorbitdir
 debian/rules override_jh_compilefeatures
  make[1]: Entering directory '«BUILDDIR»'
  jh_compilefeatures --build-opts="-DjavacTarget=1.5 -DjavacSource=1.5 
-DbuildId=dist -DforceContextQualifier=dist"
  jh_compilefeatures: Compatibility levels before 9 are deprecated (level 8 in 
use)
  mkdir -p «BUILDDIR»/debian/.eclipse-build/build
  mkdir -p «BUILDDIR»/debian/.eclipse-build/build/home
  mkdir -p «BUILDDIR»/debian/.eclipse-build/build/home/workspace
  Building feature = AnyEditTools.
  Symlinking SDK into «BUILDDIR»/debian/.eclipse-build/build/SDK directory.
  /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
«BUILDDIR»/debian/.eclipse-build/build/SDK /usr/lib/eclipse
  ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
directory
  ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
directory
  ln: failed to create symbolic link 'icon.xpm': File exists
  ln: failed to create symbolic link 'notice.html': File exists
  ln: failed to create symbolic link 'readme': File exists
  ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
  ln: failed to create symbolic link 'swt-gtk.jar': File exists
  ln: failed to create symbolic link 'swt.jar': File exists
  Starting build:
  An error has occurred. See the log file
  «BUILDDIR»/debian/.eclipse-build/build/home/workspace/.metadata/.log.
  jh_compilefeatures: cd debian/.eclipse-build && 
/usr/lib/eclipse/buildscripts/pde-build -a "-DjavacTarget=1.5 -DjavacSource=1.5 
-DbuildId=dist -DforceContextQualifier=dist"  -f AnyEditTools returned exit 
code 13
  debian/rules:10: recipe for target 'override_jh_compilefeatures' failed
  make[1]: *** [override_jh_compilefeatures] Error 2
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


eclipse-anyedit.2.4.4-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#850552: txfixtures: FTBFS: MismatchError: > returned None

[Chris Lamb]

Source: txfixtures
Version: 0.2.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

txfixtures fails to build from source in unstable/amd64:

  […]

  test_stalePidFile (tests.test_tachandler.TacTestFixtureTestCase)
  tests.test_tachandler.TacTestFixtureTestCase.test_stalePidFile ... ok
  test_hung (tests.test_service.ServiceIntegrationTest)
  tests.test_service.ServiceIntegrationTest.test_hung ... ok
  test_non_executable_command (tests.test_service.ServiceIntegrationTest)
  tests.test_service.ServiceIntegrationTest.test_non_executable_command ... FAIL
  test_service_ready (tests.test_service.ServiceIntegrationTest)
  tests.test_service.ServiceIntegrationTest.test_service_ready ... ok
  test_unknown_command (tests.test_service.ServiceIntegrationTest)
  tests.test_service.ServiceIntegrationTest.test_unknown_command ... ok
  test_no_expected_output_exit 
(tests.test_service.ServiceProtocolIntegrationTest)
  
tests.test_service.ServiceProtocolIntegrationTest.test_no_expected_output_exit 
... ok
  test_no_expected_output_timeout 
(tests.test_service.ServiceProtocolIntegrationTest)
  
tests.test_service.ServiceProtocolIntegrationTest.test_no_expected_output_timeout
 ... ok
  test_no_expected_port_exit (tests.test_service.ServiceProtocolIntegrationTest)
  tests.test_service.ServiceProtocolIntegrationTest.test_no_expected_port_exit 
... ok
  test_no_expected_port_timeout 
(tests.test_service.ServiceProtocolIntegrationTest)
  
tests.test_service.ServiceProtocolIntegrationTest.test_no_expected_port_timeout 
... ok
  test_no_min_uptime (tests.test_service.ServiceProtocolIntegrationTest)
  tests.test_service.ServiceProtocolIntegrationTest.test_no_min_uptime ... ok
  test_ready (tests.test_service.ServiceProtocolIntegrationTest)
  tests.test_service.ServiceProtocolIntegrationTest.test_ready ... ok
  test_ready_with_expected_output 
(tests.test_service.ServiceProtocolIntegrationTest)
  
tests.test_service.ServiceProtocolIntegrationTest.test_ready_with_expected_output
 ... ok
  test_ready_with_expected_port 
(tests.test_service.ServiceProtocolIntegrationTest)
  
tests.test_service.ServiceProtocolIntegrationTest.test_ready_with_expected_port 
... ok
  test_ready_with_expected_port_retry 
(tests.test_service.ServiceProtocolIntegrationTest)
  
tests.test_service.ServiceProtocolIntegrationTest.test_ready_with_expected_port_retry
 ... ok
  
  ==
  FAIL: test_non_executable_command (tests.test_service.ServiceIntegrationTest)
  tests.test_service.ServiceIntegrationTest.test_non_executable_command
  --
  _StringException: Empty attachments:
fake-process
  
  pythonlogging:'': {{{
  Starting Twisted reactor in a separate thread
  Reactor started
  Spawning service process ['/tmp/tmpBzBsYY/foobar']
  Service process spawned
  Service process alive for 0.1 seconds
  Service process ready
  Stopping Twisted reactor and wait for its thread
  Reactor stopped
  }}}
  
  Traceback (most recent call last):
File "tests/test_service.py", line 65, in test_non_executable_command
  error = self.assertRaises(MultipleExceptions, self.fixture.setUp)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 422, in 
assertRaises
  self.assertThat(our_callable, matcher)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in 
assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: > returned None
  
  
  --
  Ran 71 tests in 7.658s
  
  FAILED (failures=1, skipped=2)
  E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
«BUILDDIR»/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
  debian/rules:9: recipe for target 'build' failed
  make: *** [build] Error 25
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


txfixtures.0.2.3-1.unstable.amd64.log.txt.gz
Description: Binary data

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 843594 serious
Bug #843594 [src:ilmbase] ilmbase: Proprietary licence in halfExport.h
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#849947: marked as done (w3af-console depends on no longer built python-guess-language)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 16:58:23 +
with message-id 
and subject line Bug#849959: Removed package(s) from unstable
has caused the Debian Bug report #849947,
regarding w3af-console depends on no longer built python-guess-language
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.)


-- 
849947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: w3af-console
Version: 1.6.54+git20160429-3
Severity: serious

w3af-console depends on python-guess-language
that is no longer being built.
--- End Message ---
--- Begin Message ---
Version: 1.6.54+git20160429-3+rm

Dear submitter,

as the package w3af has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/849959

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#846728: gcr: FTBFS: Test failures

[Michael Biebl]

Am 07.01.2017 um 17:00 schrieb Michael Biebl:
> Am 07.01.2017 um 08:16 schrieb Lucas Nussbaum:
>>
>> On 07/01/17 at 01:15 +0100, Michael Biebl wrote:
> 
>>> I just tried to reproduce this in an up-to-date sid chroot and the
>>> package built fine. The built was using gnupg_2.1.16-2 whereas my chroot
>>> has 2.1.17-3. I wonder if that makes a difference.
>>>
>>> Can you try to reproduce the issue?
>>
>> I just did a rebuild of testing. Yes, I can reproduce it, see attached
>> log.
> 
> Hm, odd. Any idea how your build chroot differs from a newly created
> pbuilder chroot?
> Any help appreciated with finding out what exactly triggers the
> test-suite / gnupg failure.

Also builds fine on barriere.d.o via schroot



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#849931: marked as done (jackson-module-afterburner: FTBFS (Missing dependency))

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 16:52:17 +
with message-id 
and subject line Bug#850423: Removed package(s) from unstable
has caused the Debian Bug report #849931,
regarding jackson-module-afterburner: FTBFS (Missing dependency)
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.)


-- 
849931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jackson-module-afterburner
Version: 2.7.1-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven --with javahelper
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
sh debian/replace-generate.sh 
src/main/java/com/fasterxml/jackson/module/afterburner/PackageVersion.java
dh_auto_configure
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibjackson2-module-afterburner-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
make[1]: Leaving directory '/<>'
   jh_linkjars -i -O--buildsystem=maven
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] 'dependencies.dependency.version' for 
com.fasterxml.jackson.core:jackson-annotations:jar is missing. @ line 62, 
column 15
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project 
com.fasterxml.jackson.module:jackson-module-afterburner:2.7.1 
(/<>/pom.xml) has 1 error
[ERROR] 'dependencies.dependency.version' for 
com.fasterxml.jackson.core:jackson-annotations:jar is missing. @ line 62, 
column 15
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit 
code 1
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

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 page for this package.

If you could not reproduce this using sbuild on a single CPU virtual machine 
(as I did),
please do not downgrade or mark as unreproducible, I would then consider giving 
you access
to a virtual machine on which I can reproduce it so that you can as well.
(In such case, please contact me off-list for details).

Thanks.
--- End Message ---
--- Begin Message 

Bug#672390: marked as done (Please consider chaging dependency of libsigc++1.2 to 2.0)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 16:51:19 +
with message-id 
and subject line Bug#850210: Removed package(s) from unstable
has caused the Debian Bug report #672390,
regarding Please consider chaging dependency of libsigc++1.2 to 2.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.)


-- 
672390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freqtweak
Version: 0.7.2-4
Severity: normal

Hello,

I would like to ask you to consider changing the build-depends from
libsigc++-1.2-dev to libsigc++-2.0-dev.

The version in 1.2 is very old, unsupported (last release on 2005,
more than 7 years ago) and it should probably be removed from Debian
when possible.

There are only 3 packages in the whole archive depending on it (versus
150+ for 2.0), and this is one of them.

Regards.


--- End Message ---
--- Begin Message ---
Version: 0.7.2-4.1+rm

Dear submitter,

as the package freqtweak has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/850210

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#770240: marked as done (libsigc++-1.2: Keep out of testing)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 16:45:14 +
with message-id 
and subject line Bug#738897: Removed package(s) from unstable
has caused the Debian Bug report #770240,
regarding libsigc++-1.2: Keep out of testing
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.)


-- 
770240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsigc++-1.2
Severity: normal

Hello,

This version (1.2) of libsigc++ is very old, unsupported (last release on
2005, more than 7 years ago) and should probably be removed from Debian when
possible.

There are only 2 packages in the whole archive depending on it (versus 150+
for 2.0) : asc and freqtweak. These packages are themselves quite dusty.

Regards,

-- 
Stéphane Aulery

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 1.2.7-2+rm

Dear submitter,

as the package libsigc++-1.2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/738897

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#817551: marked as done (libsigc++-1.2: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 16:45:14 +
with message-id 
and subject line Bug#738897: Removed package(s) from unstable
has caused the Debian Bug report #817551,
regarding libsigc++-1.2: Removal of debhelper compat 4
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.)


-- 
817551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsigc++-1.2
Severity: important
Usertags: compat-4-removal

Hi,

The package libsigc++-1.2 uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 1.2.7-2+rm

Dear submitter,

as the package libsigc++-1.2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/738897

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#833245: marked as done (openssl-blacklist: Uses obsolete compressor for .deb data.tar member)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 16:47:33 +
with message-id 
and subject line Bug#849027: Removed package(s) from unstable
has caused the Debian Bug report #833245,
regarding openssl-blacklist: Uses obsolete compressor for .deb data.tar member
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.)


-- 
833245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openssl-blacklist
Source-Version: 0.5-3
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-obsolete-deb-data-tar-compressor

Hi!

This source package builds one or more binary packages using the
deprecated compressor bzip2. The default has been xz for a while now
which should usually compress better than bzip2. If instead you'd like
speed then switch to use gzip.

Using a deprecated compressor when building binary packages will
become an error in the near future. Please update the packages.

See also .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Version: 0.5-3+rm

Dear submitter,

as the package openssl-blacklist has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/849027

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#833197: marked as done (libsigc++-1.2: Uses obsolete Source-Version substvar)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 16:45:14 +
with message-id 
and subject line Bug#738897: Removed package(s) from unstable
has caused the Debian Bug report #833197,
regarding libsigc++-1.2: Uses obsolete Source-Version substvar
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.)


-- 
833197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsigc++-1.2
Source-Version: 1.2.7-2
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-obsolete-source-version-substvar

Hi!

This source package uses the ${Source-Version} substvar variable
deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced
the substvars binary:Version and source:Version which can be used
instead.

Using this deprecated substvar will become an error in the near
future. Please update the package.

See also .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Version: 1.2.7-2+rm

Dear submitter,

as the package libsigc++-1.2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/738897

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#847997: marked as done (golang-github-jessevdk-go-flags-dev: Cannot bo co-installed golang-go-flags-dev)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 16:46:29 +
with message-id 
and subject line Bug#848092: Removed package(s) from unstable
has caused the Debian Bug report #847997,
regarding golang-github-jessevdk-go-flags-dev: Cannot bo co-installed 
golang-go-flags-dev
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.)


-- 
847997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-jessevdk-go-flags-dev
Version: 1.1-1
Severity: grave
Control: tag -1 patch

Dear Maintainer,

when trying to install golang-github-jessevdk-go-flags-dev, I got the
following error:

,
| Preparing to unpack .../0-golang-github-jessevdk-go-flags-dev_1.1-1_all.deb 
...
| Unpacking golang-github-jessevdk-go-flags-dev (1.1-1) ...
| dpkg: error processing archive 
/tmp/apt-dpkg-install-XO4p4v/0-golang-github-jessevdk-go-flags-dev_1.1-1_all.deb
 (--unpack):
|  trying to overwrite 
'/usr/share/gocode/src/github.com/jessevdk/go-flags/arg.go', which is also in 
package golang-go-flags-dev 0.0~git20160302-1
`

At least a Breaks/Replaces is needed; Since golang-go-flags-dev is
superseeded by this package, it might also make sense to add a
transitional package. (In this case, you should make Brekas/Replaces
versioned.)

Cheers,
-Hilko
>From 84ddd477f3b6754209bd8701f5a8cb29dbb5aa07 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Tue, 13 Dec 2016 00:36:20 +0100
Subject: [PATCH] Add Brekas/Replaces: golang-go-flags-dev

---
 debian/control | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/control b/debian/control
index f6e368f..f38bdf7 100644
--- a/debian/control
+++ b/debian/control
@@ -17,6 +17,8 @@ Architecture: all
 Depends: ${shlibs:Depends},
  ${misc:Depends},
  golang-go
+Breaks: golang-go-flags-dev
+Replaces: golang-go-flags-dev
 Description: Go library for parsing command line arguments
  This library provides similar functionality to the builtin flag library
  of go, but provides much more functionality and nicer formatting. From
-- 
2.11.0

--- End Message ---
--- Begin Message ---
Version: 1.1-1+rm

Dear submitter,

as the package golang-github-jessevdk-go-flags has just been removed from the 
Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/848092

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#850226: no longer advertises route

[Steinar H. Gunderson]

On Sun, Jan 08, 2017 at 01:16:20AM +1100, Scott Leggett wrote:
> Though the broken versions appear to be different, this issue looks
> similar to an existing upstream bug:
> https://bugzilla.quagga.net/show_bug.cgi?id=870
> 
> Does this look like the same issue to you?

It might be the same, but it's hard to say. I use iBGP, but this route isn't
learned from iBGP; it's advertised out from the host in question (through a
network statement).

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#821883: ImportError: When using gi.repository you must not import static modules like "gobject"

[Benjamin Barenblat]

Sounds good to me. I've filed an RFP (https://bugs.debian.org/850541).
Would you like to take it? I'm also happy to package.

Bug#846728: gcr: FTBFS: Test failures

[Michael Biebl]

Am 07.01.2017 um 08:16 schrieb Lucas Nussbaum:
> 
> On 07/01/17 at 01:15 +0100, Michael Biebl wrote:

>> I just tried to reproduce this in an up-to-date sid chroot and the
>> package built fine. The built was using gnupg_2.1.16-2 whereas my chroot
>> has 2.1.17-3. I wonder if that makes a difference.
>>
>> Can you try to reproduce the issue?
> 
> I just did a rebuild of testing. Yes, I can reproduce it, see attached
> log.

Hm, odd. Any idea how your build chroot differs from a newly created
pbuilder chroot?
Any help appreciated with finding out what exactly triggers the
test-suite / gnupg failure.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

[Daniel Kahn Gillmor]

On Fri 2017-01-06 17:49:04 -0500, shirish शिरीष wrote:
> But issue is still continuing -
>
> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197
>
> [4:22:18]
> gpg: keyserver receive failed: No keyserver available
>
> I tried multiple times with various other keys but didn't succeed.

Have you restarted dirmngr since the upgrade?  are you using tor?  if
you're using tor, have you removed all the ipv6 entries ?

what does:

   gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye

show you?

 --dkg

Processed: fw

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 846640 https://llvm.org/bugs/show_bug.cgi?id=31571
Bug #846640 [lldb-3.8] lldb-3.8: lldb freezes after "run"
Set Bug forwarded-to-address to 'https://llvm.org/bugs/show_bug.cgi?id=31571'.
> block 846531 by 846640 846638 846616
Bug #846531 [lldb-3.8] lldb-3.8 and lldb-3.9 are completely unusable in stretch 
(multiply problems); fix them or remove from scretch
846531 was not blocked by any bugs.
846531 was not blocking any bugs.
Added blocking bug(s) of 846531: 846638, 846640, and 846616
> thanks
Stopping processing here.

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

Bug#846335: cross-toolchain-base: FTBFS in testing (2 out of 2 hunks FAILED)

[Johannes Schauer]

Hi,

Quoting Santiago Vila (2017-01-07 15:46:30)
> This package, cross-toolchain-base, has a small collection of Build-Using
> fields on other source packages.
> 
> I'm building packages in stretch, and when a package FTBFS in stretch,
> I report it as a serious bug.
> 
> Matthias complains that I'm not building packages "the same way" he did.
> 
> He seems to suggest (please correct me if I'm wrong) that I should use
> the exact same version he used in the Built-Using field.
> 
> But I think this information is only in the binary packages.
> 
> So: Is sbuild supposed to take this information from the binary
> packages I'm trying to rebuild (unlikely, but I ask just in case),
> or maybe it's that the Built-Using fields should just be versioned
> when there is a risk that not every version of the Built-Used packages
> is ok for the build? (May Built-Using be versioned, like Depends
> or Build-Depends?)
> 
> [ My theory is that this is a bug in either cross-toolchain-base,
>   sbuild, or maybe our package format, but definitely not in myself building
>   packages on stretch ].

thanks!

The Built-Using field is for binary packages to indicate that they incorporate
code from other source packages than the source package that the build from.
This is important so that the archive can keep these source versions around
even if a newer source package gets uploaded. You can identify source packages
that are only kept around because some binary package incorporates material
from them through the "Extra-Source-Only: yes" header in Sources lists.
Conversely, the Packages list files contain the Built-Using header listing
these source packages. This mechanism is used to make sure that the source code
for all binary packages that we ship is still distributed by us. Without the
Built-Using header, it could easily happen that a new version of a source
package gets uploaded, the old version is dropped from the archive and suddenly
we have a binary in the archive for which we do not provide the source anymore.
So the Built-Using header is a mechanism that keeps us copyright compliant. It
is not a mechanism to list the requirements to build a source packages. These
requirements are contained in the Build-Depends, Build-Depends-Indep,
Build-Depends-Arch and their corresponding Conflicts fields.

If the package really fails to build from source because you are not installing
the right package versions or not the right packages, then these are missing
from the Build-Depends-* fields.

The Built-Using header is for binary packages to assure copyright compliance in
the archive. They are not indicators of the binary packages required to build a
source package.

If I misunderstood the Built-Using situation, please point me to the resource
that states otherwise.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#846335: cross-toolchain-base: FTBFS in testing (2 out of 2 hunks FAILED)

[Santiago Vila]

On Sat, Jan 07, 2017 at 02:41:40PM +0100, Johannes Schauer wrote:

> Quoting Santiago Vila (2017-01-07 13:37:27)
> > On Sat, Jan 07, 2017 at 01:02:19PM +0100, Matthias Klose wrote:
> > > You could detect these as well by inspecting the Built-Using flag
> > > and using the very same versions for your test builds.
> > 
> > Well, maybe this is a bug in sbuild.
> > 
> > I'm Cc:ing Johannes Schauer, sbuild maintainer, in case he has any
> > idea about how to avoid this minor glitch.
> 
> even after having read the bug I'm unsure what the problem with sbuild is 
> here.
> 
> What do you want to use the Built-Using header for? What is sbuild not doing
> that you think it should do?

This package, cross-toolchain-base, has a small collection of
Build-Using fields on other source packages.

I'm building packages in stretch, and when a package FTBFS in stretch,
I report it as a serious bug.

Matthias complains that I'm not building packages "the same way" he did.

He seems to suggest (please correct me if I'm wrong) that I should use
the exact same version he used in the Built-Using field.

But I think this information is only in the binary packages.

So: Is sbuild supposed to take this information from the binary
packages I'm trying to rebuild (unlikely, but I ask just in case),
or maybe it's that the Built-Using fields should just be versioned
when there is a risk that not every version of the Built-Used packages
is ok for the build? (May Built-Using be versioned, like Depends
or Build-Depends?)

[ My theory is that this is a bug in either cross-toolchain-base,
  sbuild, or maybe our package format, but definitely not in myself
  building packages on stretch ].

Thanks.

Bug#846728: gcr: FTBFS: Test failures

[Lucas Nussbaum]

Hi,

On 07/01/17 at 01:15 +0100, Michael Biebl wrote:
> Control: tags -1 moreinfo unreproducible
> 
> Hi Lucas
> 
> On Sat, 3 Dec 2016 08:41:49 +0100 Lucas Nussbaum  wrote:
> > Source: gcr
> > Version: 3.20.0-3
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20161202 qa-ftbfs
> > Justification: FTBFS on amd64
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> 
> This is the error message from the log:
> 
> **
> ERROR:gcr/test-gnupg-collection.c:214:test_reload: assertion failed:
> (test->result)
> FAIL: test-gnupg-collection 3 /gcr/gnupg-collection/reload
> ERROR: test-gnupg-collection process failed: 250
> 
> I just tried to reproduce this in an up-to-date sid chroot and the
> package built fine. The built was using gnupg_2.1.16-2 whereas my chroot
> has 2.1.17-3. I wonder if that makes a difference.
> 
> Can you try to reproduce the issue?

I just did a rebuild of testing. Yes, I can reproduce it, see attached
log.

Lucas


gcr_3.20.0-3_testing.log.gz
Description: application/gzip

Bug#850226: no longer advertises route

[Scott Leggett]

On 2017-01-05.09:46, Steinar H. Gunderson wrote:
> Package: quagga-bgpd
> Version: 1.1.0-3
> Severity: grave
> 
> Hi,
> 
> I lost all of my IPv6 connectivity this morning; a bit of searching shows that
> it is due to an automated upgrade of:
> 
>   2017-01-05 07:36:26 upgrade quagga:amd64 1.0.20160315-2 1.1.0-3
> ...

Hi, thanks for the bug report.

Though the broken versions appear to be different, this issue looks
similar to an existing upstream bug:
https://bugzilla.quagga.net/show_bug.cgi?id=870

Does this look like the same issue to you?

FYI a similar issues is also discussed here:
https://lists.quagga.net/pipermail/quagga-users/2016-December/014596.html

-- 
Regards,
Scott.


signature.asc
Description: Digital signature

Bug#846335: cross-toolchain-base: FTBFS in testing (2 out of 2 hunks FAILED)

[Johannes Schauer]

Hi,

Quoting Santiago Vila (2017-01-07 13:37:27)
> On Sat, Jan 07, 2017 at 01:02:19PM +0100, Matthias Klose wrote:
> > You could detect these as well by inspecting the Built-Using flag
> > and using the very same versions for your test builds.
> 
> Well, maybe this is a bug in sbuild.
> 
> I'm Cc:ing Johannes Schauer, sbuild maintainer, in case he has any
> idea about how to avoid this minor glitch.

even after having read the bug I'm unsure what the problem with sbuild is here.

What do you want to use the Built-Using header for? What is sbuild not doing
that you think it should do?

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#850528: firejail: root shell via --bandwidth and --shell

[Salvatore Bonaccorso]

Source: firejail
Version: 0.9.44.2-1
Severity: grave
Tags: upstream security patch fixed-upstream
Justification: user security hole
Forwarded: https://github.com/netblue30/firejail/issues/1023

Hi

There is no CVE assigned for this one yet: 

https://github.com/netblue30/firejail/issues/1023
https://github.com/netblue30/firejail/commit/5d43fdcd215203868d440ffc42036f5f5ffc89fc

CVE requested here:

http://www.openwall.com/lists/oss-security/2017/01/07/3

Regards,
Salvatore

Bug#850453: marked as done (Non-fatal harmful errors upgrading from pre-0.82 to 0.82 under cow-shell)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 13:03:49 +
with message-id 
and subject line Bug#850453: fixed in cowdancer 0.83
has caused the Debian Bug report #850453,
regarding Non-fatal harmful errors upgrading from pre-0.82 to 0.82 under 
cow-shell
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.)


-- 
850453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cowdancer
Version: 0.82
Severity: serious

Running cowbuilder --update gives a load of the following errors:

> ERROR: ld.so: object '/usr/lib/cowdancer/libcowdancer.so' from LD_PRELOAD 
> cannot be preloaded (cannot open shared object file): ignored.

The entire update process runs under cow-shell, so when a pre-0.82
chroot is upgraded to 0.82 (which moved libcowdancer.so to a multiarch
path), future processes run in the same session can no longer load
libcowdancer.so, as they still think it's in the old place.

Either a compatibility symlink needs to be provided, or if that cannot
be done so that pre-0.82 *and* 0.82 chroots can be upgraded without
these errors, the file should just be duplicated for the stretch release
in the old and new paths.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cowdancer depends on:
ii  libc62.24-8
ii  libncurses5  6.0+20161126-1
ii  libtinfo56.0+20161126-1

cowdancer recommends no packages.

cowdancer suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cowdancer
Source-Version: 0.83

We believe that the bug you reported is fixed in the latest version of
cowdancer, 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 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Clarke  (supplier of updated cowdancer 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: Sat, 07 Jan 2017 11:51:22 +
Source: cowdancer
Binary: cowdancer cowbuilder qemubuilder
Architecture: source
Version: 0.83
Distribution: unstable
Urgency: medium
Maintainer: Debian pbuilder maintenance team 

Changed-By: James Clarke 
Description:
 cowbuilder - pbuilder running on cowdancer
 cowdancer  - Copy-on-write directory tree utility
 qemubuilder - pbuilder using QEMU as backend
Closes: 753008 850453
Changes:
 cowdancer (0.83) unstable; urgency=medium
 .
   * parameter.c: Print a friendlier message when basepath can't be created
 (Closes: #753008)
   * debian/control: Use my @debian.org email address
   * debian/copyright: Add myself (2016-2017)
   * Revert "cowdancer: Use multiarch library path"
   * Symlink multiarch path to non-multiarch path (Closes: #850453)
 - If a user has updated their chroot to 0.82, this will cause a few errors
   again on unpack, but this will be a very short window.
Checksums-Sha1:
 ea6294f8a75dac701df5cbfcdb58cbc648748edf 1876 cowdancer_0.83.dsc
 ff089a3fa8c736b16d9cbfa7647d91d2accf27b6 69832 cowdancer_0.83.tar.xz
Checksums-Sha256:
 f248bdf2d5dc04aeb3a02ac8614bc88a0d179184fa698a05cf3c1e4a5ce73148 1876 
cowdancer_0.83.dsc
 1613a54e4620a19f75b9d0897f8a8f3439a61eceafe4b792d013e2424e6161db 69832 
cowdancer_0.83.tar.xz
Files:
 f3b021f197fd4e4d7730fe3aac0e3599 1876 utils optional cowdancer_0.83.dsc
 cb56070a8ef81ff1701ae30a7c52d95a 69832 utils optional cowdancer_0.83.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEj1g0K+q+HvQ3lVH7sZN3DBhqHH0FAlhw4K4SHGpydGMyN0Bk
ZWJpYW4ub3JnAAoJELGTdwwYahx9aq8P/j5drq70KGsjuOavnEQk2of+KC4U1n49
dZdj/CaExdcZ51xoUcDEMadGoMYsRRekgDnVpQzeTXP5Wkhi6A2A14cYaATtGW4y
b+WitPNyRTJ2OOAT4eZpdGj1fpvLT3sUGDps41rA9aYzahdm5SZBdAn6sQZV0w04

Bug#845860: marked as done (lcd4linux: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Sat, 7 Jan 2017 12:49:29 +
with message-id <20170107124929.lepiyiee4576m...@lambda.dereenigne.org>
and subject line Fixed in lcd4linux 0.11.0~svn1203-1
has caused the Debian Bug report #845860,
regarding lcd4linux: switch to build depend on the metapackage 
default-libmysqlclient-dev
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.)


-- 
845860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lcd4linux
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Hi,

This was fixed in lcd4linux/0.11.0~svn1203-1, but I forgot to mark it as
closed.

Jon


signature.asc
Description: PGP signature
--- End Message ---

Bug#784619: Draft fix for Creepy in git

[Petter Reinholdtsen]

There is a draft fix for this in 
https://anonscm.debian.org/cgit/pkg-grass/creepy.git >.  Not quite
complete, but if you want to help fix Creepy, patches are most
welcome. :)

-- 
Happy hacking
Petter Reinholdtsen

Processed: Bug#850453 in cowdancer marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 850453 pending
Bug #850453 [cowdancer] Non-fatal harmful errors upgrading from pre-0.82 to 
0.82 under cow-shell
Added tag(s) pending.

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

Bug#850453: in cowdancer marked as pending

[James Clarke]

Control: tag 850453 pending

Hello,

Bug #850453 in cowdancer reported by you has been fixed in the Git repository. 
You can
see the commit message below, and you can check the diff of the fix at:

https://anonscm.debian.org/git/pbuilder/cowdancer.git/commit/?id=d36c911

(this message was generated automatically based on the git commit message)
---
commit d36c9110a6993b4845649a3aa992961b1a6b4426
Author: James Clarke 
Date:   Fri Jan 6 19:02:11 2017 +

Symlink multiarch path to non-multiarch path

This is not ideal, since some users may already have updated their
unstable chroots to 0.82, but unstable is unstable, and trying to make
upgrades from 0.82 work would be a nightmare. Sorry for the breakage.

Closes: #850453

Bug#846334: cross-toolchain-base: FTBFS in testing (2 out of 2 hunks FAILED)

[Santiago Vila]

On Sat, Jan 07, 2017 at 01:02:19PM +0100, Matthias Klose wrote:
> This has nothing to do with -A builds.

That's right. In such cases, I do not say "fails to build when using
dpkg-buildpackage -A" in the Subject itself. If I say that in
the body, it's just for completeness. A good bug report should
be exact and accurate, and "dpkg-buildpackage -A" is what I really did.

> Apparently you did that test rebuild for testing, not unstable.

Not just apparently. I said it clearly in the bug report:

"I tried to build this package in stretch [...]"

> Please could you do such test rebuilds in unstable
> instead?

Sorry, no. There are too many broken packages in unstable,
and Lucas Nussbaum and Chris Lamb already report most of them.

> Then you avoid filing issues which are non-issues.

Please don't say that. This was an issue when I reported it, because
packages in stretch *must* be buildable in stretch. This is
just Release Policy, not an invention of mine.

> You could detect these as well by inspecting the Built-Using flag
> and using the very same versions for your test builds.

Well, maybe this is a bug in sbuild.

I'm Cc:ing Johannes Schauer, sbuild maintainer, in case he has any
idea about how to avoid this minor glitch.

Thanks.

Processed: Re: python-eventlet: FTBFS (failing tests)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 850508 python-eventlet: FTBFS "assert udp in [ai[:3] + (ai[4],) for 
> ai in res]" (failing tests)
Bug #850508 [src:python-eventlet] python-eventlet: FTBFS (failing tests)
Changed Bug title to 'python-eventlet: FTBFS "assert udp in [ai[:3] + (ai[4],) 
for ai in res]" (failing tests)' from 'python-eventlet: FTBFS (failing tests)'.
> thanks
Stopping processing here.

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

Bug#846335: marked as done (cross-toolchain-base: FTBFS in testing (2 out of 2 hunks FAILED))

[Debian Bug Tracking System]

Your message dated Sat, 7 Jan 2017 13:02:19 +0100
with message-id <4fd2cc35-181b-6f74-6a7e-04754ee0a...@debian.org>
and subject line Re: cross-toolchain-base: FTBFS in testing (2 out of 2 hunks 
FAILED)
has caused the Debian Bug report #846335,
regarding cross-toolchain-base: FTBFS in testing (2 out of 2 hunks FAILED)
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.)


-- 
846335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cross-toolchain-base
Version: 14
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
linux: 4.8.7-1 / 4.8.7-1cross1
glibc: 2.24-5 / 2.24-5cross1

old linux version: 4.8.7-1 / 1
old glibc version: 2.24-5 / 1

new linux version: 4.8.7-1cross2
new glibc version: 2.24-5cross2
START stamp-dir/init-glibc
rm -rf glibc-2.24
tar -x -f  /usr/src/glibc/glibc-2.24.tar.xz
cp -a /usr/src/glibc/debian/ glibc-2.24
cd glibc-2.24 ; \
QUILT_PATCHES=/<>/debian/patches/glibc/debian quilt --quiltrc 
/dev/null push -a && \
rm -rf .pc/
Applying patch dpkg-shlibs.patch
patching file debian/rules.d/debhelper.mk
Hunk #1 succeeded at 81 (offset 2 lines).

Applying patch local-kill-locales.patch
patching file localedata/SUPPORTED

Now at patch local-kill-locales.patch
if dpkg --compare-versions 2.24-5 le 2.24-5; then \
  cd glibc-2.24; \
  patch -p1 < ../debian/patches/glibc/glibc-update.diff; \
fi
patching file iconv/gconv.h
patching file sysdeps/powerpc/powerpc32/power6/memset.S
patching file sysdeps/powerpc/powerpc64/power6/memset.S
cd glibc-2.24; \
patch -p1 < ../debian/patches/glibc/glibc-depends.diff
patching file debian/rules.d/debhelper.mk
touch stamp-dir/init-glibc
START stamp-dir/init-gcc
set -e; \
mkdir gcc -p ; \
cd gcc ; \
ln -sf /usr/src/gcc-6/gcc-6.2.0.tar.xz gcc-6.2.0.tar.xz ;\
cp -a  /usr/src/gcc-6/debian/ . ; \
if [ -n "$(grep -v '^\#' /<>/debian/patches/gcc/series)" ]; then \
  QUILT_PATCHES=/<>/debian/patches/gcc quilt --quiltrc /dev/null  
push -a ; \
fi;
if dpkg --compare-versions 6.2.0-13 le 6.2.1-4; then \
  cd gcc; \
  patch -p1 < ../debian/patches/gcc/gcc-stage1.diff; \
fi
patching file debian/rules.patch
Hunk #1 FAILED at 151.
Hunk #2 FAILED at 187.
2 out of 2 hunks FAILED -- saving rejects to file debian/rules.patch.rej
debian/rules:213: recipe for target 'stamp-dir/init-gcc' failed
make: *** [stamp-dir/init-gcc] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

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 page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
This has nothing to do with -A builds.  Apparently you did that test rebuild for
testing, not unstable.  Please could you do such test rebuilds in unstable
instead?  Then you avoid filing issues which are non-issues.  You could detect
these as well by inspecting the Built-Using flag and using the very same
versions for your test builds.

Matthias--- End Message ---

Bug#846334: marked as done (cross-toolchain-base-ports: FTBFS in testing (2 out of 2 hunks FAILED))

[Debian Bug Tracking System]

Your message dated Sat, 7 Jan 2017 13:02:19 +0100
with message-id <4fd2cc35-181b-6f74-6a7e-04754ee0a...@debian.org>
and subject line Re: cross-toolchain-base: FTBFS in testing (2 out of 2 hunks 
FAILED)
has caused the Debian Bug report #846334,
regarding cross-toolchain-base-ports: FTBFS in testing (2 out of 2 hunks FAILED)
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.)


-- 
846334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cross-toolchain-base-ports
Version: 7
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
linux: 4.8.7-1 / 4.8.7-1cross1
glibc: 2.24-5 / 2.24-5cross1

old linux version: 4.8.7-1 / 1
old glibc version: 2.24-5 / 1

new linux version: 4.8.7-1cross2
new glibc version: 2.24-5cross2
START stamp-dir/init-glibc
rm -rf glibc-2.24
tar -x -f  /usr/src/glibc/glibc-2.24.tar.xz
cp -a /usr/src/glibc/debian/ glibc-2.24
cd glibc-2.24 ; \
QUILT_PATCHES=/<>/debian/patches/glibc/debian quilt --quiltrc 
/dev/null push -a && \
rm -rf .pc/
Applying patch dpkg-shlibs.patch
patching file debian/rules.d/debhelper.mk
Hunk #1 succeeded at 81 (offset 2 lines).

Applying patch local-kill-locales.patch
patching file localedata/SUPPORTED

Now at patch local-kill-locales.patch
if dpkg --compare-versions 2.24-5 le 2.24-5; then \
  cd glibc-2.24; \
  patch -p1 < ../debian/patches/glibc/glibc-update.diff; \
fi
patching file iconv/gconv.h
patching file sysdeps/powerpc/powerpc32/power6/memset.S
patching file sysdeps/powerpc/powerpc64/power6/memset.S
cd glibc-2.24; \
patch -p1 < ../debian/patches/glibc/glibc-depends.diff
patching file debian/rules.d/debhelper.mk
touch stamp-dir/init-glibc
START stamp-dir/init-gcc
set -e; \
mkdir gcc -p ; \
cd gcc ; \
ln -sf /usr/src/gcc-6/gcc-6.2.0.tar.xz gcc-6.2.0.tar.xz ;\
cp -a  /usr/src/gcc-6/debian/ . ; \
if [ -n "$(grep -v '^\#' /<>/debian/patches/gcc/series)" ]; then \
  QUILT_PATCHES=/<>/debian/patches/gcc quilt --quiltrc /dev/null  
push -a ; \
fi;
if dpkg --compare-versions 6.2.0-13 le 6.2.1-4; then \
  cd gcc; \
  patch -p1 < ../debian/patches/gcc/gcc-stage1.diff; \
fi
patching file debian/rules.patch
Hunk #1 FAILED at 151.
Hunk #2 FAILED at 187.
2 out of 2 hunks FAILED -- saving rejects to file debian/rules.patch.rej
debian/rules:213: recipe for target 'stamp-dir/init-gcc' failed
make: *** [stamp-dir/init-gcc] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

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 page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
This has nothing to do with -A builds.  Apparently you did that test rebuild for
testing, not unstable.  Please could you do such test rebuilds in unstable
instead?  Then you avoid filing issues which are non-issues.  You could detect
these as well by inspecting the Built-Using flag and using the very same
versions for your test builds.

Matthias--- End Message ---

Bug#850253: retty doesn't work anymore

[Christoph Biedl]

Christoph Berg wrote...

> while looking at fixing #817652 I tried to use retty but couldn't get
> it to work. In the second terminal, nothing happens:

Saw the same here when I checked a few weeks ago, and just gave up.

> Maybe it's time to RM retty?

Probably yes. Even if it can be fixed, it's for i386 only, and there's
the reptyr package that appears to serve the same purpose (this requires
more checking).

> Christoph

Christoph


signature.asc
Description: Digital signature

Processed: Marking as fixed in 4.5.2-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 849220 4.5.2-2
Bug #849220 {Done: Jerome BENOIT } [src:ipykernel] 
ipykernel: FTBFS (failing tests)
Marked as fixed in versions ipykernel/4.5.2-2.
> thanks
Stopping processing here.

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

Bug#850508: python-eventlet: FTBFS (failing tests)

[Santiago Vila]

Package: src:python-eventlet
Version: 0.19.0-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
debian/rules:32: warning: overriding recipe for target 
'override_dh_installchangelogs'
/usr/share/openstack-pkg-tools/pkgos.make:70: warning: ignoring old recipe for 
target 'override_dh_installchangelogs'
dh build-indep -O--buildsystem=python_distutils --with python2,python3,sphinxdoc
   dh_testdir -i -O-O--buildsystem=python_distutils
   dh_update_autotools_config -i -O-O--buildsystem=python_distutils
   dh_auto_configure -i -O-O--buildsystem=python_distutils
   dh_auto_build -i -O-O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py build --force

[... snipped ...]

return func(*a, **kw)
  File "/<>/tests/greendns_test.py", line 521, in test_getaddrinfo
assert udp in filt_res
AssertionError

==
FAIL: test_getaddrinfo_idn (tests.greendns_test.TestGetaddrinfo)
--
Traceback (most recent call last):
  File "/<>/tests/__init__.py", line 95, in wrapped
return func(*a, **kw)
  File "/<>/tests/greendns_test.py", line 536, in 
test_getaddrinfo_idn
assert udp in filt_res
AssertionError

==
FAIL: test_getaddrinfo_inet (tests.greendns_test.TestGetaddrinfo)
--
Traceback (most recent call last):
  File "/<>/tests/__init__.py", line 95, in wrapped
return func(*a, **kw)
  File "/<>/tests/greendns_test.py", line 547, in 
test_getaddrinfo_inet
assert udp in [ai[:3] + (ai[4],) for ai in res]
AssertionError

==
FAIL: test_getaddrinfo_inet6 (tests.greendns_test.TestGetaddrinfo)
--
Traceback (most recent call last):
  File "/<>/tests/__init__.py", line 95, in wrapped
return func(*a, **kw)
  File "/<>/tests/greendns_test.py", line 558, in 
test_getaddrinfo_inet6
assert udp in [ai[:3] + (ai[4],) for ai in res]
AssertionError

--
Ran 584 tests in 56.786s

FAILED (SKIP=95, failures=4)
debian/rules:18: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/python-eventlet/

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 page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine.

Thanks.

Bug#845793: Bug#787956: raising the severity, prevents usage of the multilib packages

[Matthias Klose]

On 06.01.2017 15:47, Mark Brown wrote:
> On Fri, Jan 06, 2017 at 08:48:06AM +0100, Matthias Klose wrote:
>> On 05.12.2016 18:50, Mark Brown wrote:
> 
>>> As we have been discussing it is still not clear to me if I should fix
>>> or remove the multilib packages since it is still not clear to me that
>>> there is a sensible use case for them.  As things stand I'm still not
>>> seeing much of a use case here so it seems like the best thing to do
>>> would be to remove the multilibs.
> 
>> If this didn't become clear, may I suggest to fix the packages for the 
>> release
>> instead of removing them?
> 
> I got that, what I still don't have a handle on is why that's a good
> idea - it was a worrying struggle to understand what was going on and
> even now that I think I've got that figured out it feels like something
> that's just being done by default and I am concerned that the packages
> will do more harm than good given the confusion they can cause with
> respect to multiarch.

multiarch is not yet ready; you can't build it on the buildds, you can't depend
on foreign architectures on the buildds.  If you want to spend some time working
on this, it would be appreciated, but until then I think it's better to make
these packages working.

Matthias

Bug#850023: marked as done (ImportError when importing ruamel.yaml)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 10:04:25 +
with message-id 
and subject line Bug#850023: fixed in ruamel.yaml 0.13.4-2
has caused the Debian Bug report #850023,
regarding ImportError when importing ruamel.yaml
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.)


-- 
850023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-ruamel.yaml
Version: 0.13.4-1
Severity: grave

Importing ruamel.yaml fails with the following traceback:

$ bpython
bpython version 0.16 on top of Python 2.7.13 /usr/bin/python
>>> import ruamel.yaml
Traceback (most recent call last):
  File "", line 1, in 
import ruamel.yaml
  File "/usr/lib/python2.7/dist-packages/ruamel/yaml/__init__.py", line 81, 
in 
from ruamel.yaml.main import *  # NOQA
  File "/usr/lib/python2.7/dist-packages/ruamel/yaml/main.py", line 6, in 

from typing import List, Set, Dict, Tuple, Optional, Union, BinaryIO, 
IO, Any  # NOQA
ImportError: No module named typing

Note that doing the same under python3 works, this only applies to the
python2 version:

$ bpython3
bpython version 0.16 on top of Python 3.5.2+ /usr/bin/python3
>>> import ruamel.yaml
>>>

(Using bpython is not relevant: the same error occours with the standard
python interpreter)
-- 
Elena ``of Valhalla''
--- End Message ---
--- Begin Message ---
Source: ruamel.yaml
Source-Version: 0.13.4-2

We believe that the bug you reported is fixed in the latest version of
ruamel.yaml, 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 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Bernat  (supplier of updated ruamel.yaml 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: Sat, 07 Jan 2017 08:43:02 +0100
Source: ruamel.yaml
Binary: python-ruamel.yaml python3-ruamel.yaml
Architecture: source amd64
Version: 0.13.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Vincent Bernat 
Description:
 python-ruamel.yaml - roundtrip YAML parser/emitter (Python 2 module)
 python3-ruamel.yaml - roundtrip YAML parser/emitter (Python 3 module)
Closes: 850023
Changes:
 ruamel.yaml (0.13.4-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Enable autopkgtest-pkg-python testsuite
 .
   [ Vincent Bernat ]
   * Build-Depends on python-typing. Closes: #850023.
Checksums-Sha1:
 33bd7361e50f53810f7176e8d33dce3344eda4dc 2308 ruamel.yaml_0.13.4-2.dsc
 f66e612598ef290b8c17c9de0fea4243cd661d6f 3060 
ruamel.yaml_0.13.4-2.debian.tar.xz
 bd48d3c0a35ebbb1897366ba225785a5d1c26527 288030 
python-ruamel.yaml-dbgsym_0.13.4-2_amd64.deb
 f9a01b4bc5d7e081ae913c0a999f87408cc02083 170772 
python-ruamel.yaml_0.13.4-2_amd64.deb
 998c0e920b42441d28bae02d3ab6d02a0c6c5ce3 311366 
python3-ruamel.yaml-dbgsym_0.13.4-2_amd64.deb
 471ecfeb5e51db7899468318b57d2701b66f8c9c 171850 
python3-ruamel.yaml_0.13.4-2_amd64.deb
 ceab53a407de1340582147dd47d7f3f42eb2c957 6962 
ruamel.yaml_0.13.4-2_amd64.buildinfo
Checksums-Sha256:
 9ddaf6222c2ab4841b1e5c4d6cf1563beebf0891f35d309b6a939454f645ccdb 2308 
ruamel.yaml_0.13.4-2.dsc
 bdd2d8e628eda6cb80b1e16b574be9499b426319ccc5ca84004ed8ec3ef52984 3060 
ruamel.yaml_0.13.4-2.debian.tar.xz
 dd8628cfa7bbee56b4d428dddedc8b9ada72a378ad4bdc3256f1f3b3fef67ed0 288030 
python-ruamel.yaml-dbgsym_0.13.4-2_amd64.deb
 c4b761ff5b96da4ce7cb18445629fbacbc725dcba4922a5ac99f7d44abcbdd20 170772 
python-ruamel.yaml_0.13.4-2_amd64.deb
 e507de612495f362c7f0cc7b35bbcd76d470abdacdfc875d553aaaff70fafee8 311366 
python3-ruamel.yaml-dbgsym_0.13.4-2_amd64.deb
 b542eb048090a61132634e76c8feb6e43de236425b51b12fec532a7e1487694a 171850 
python3-ruamel.yaml_0.13.4-2_amd64.deb
 f3e18e23abfbf031b2c6691bd869c42cd4362e4af9476074ddd7dd1918022b53 6962 
ruamel.yaml_0.13.4-2_amd64.buildinfo
Files:
 02034aa6718c996131fe8bb935ecd22c 2308 python optional ruamel.yaml_0.13.4-2.dsc
 2c3abfb51cbbcf54f624c439f584c91b 3060 python optional 

Processed: dump a quick workaround

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # So I stop writing it every time I need it...
> outlook 817236 Dirty workaround: inside the chroot: rm /dev/ptmx && mknod -m 
> 666 /dev/ptmx c 5 2
Outlook recorded from message bug 817236 message 
Outlook recorded from message bug 817236 message 
Outlook recorded from message bug 817236 message 
> --
Stopping processing here.

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

Processed: Re: dleyna-server: Segfault when pluggin secondary screen

[Debian Bug Tracking System]

Processing control commands:

> tags  -1 + moreinfo
Bug #848863 [dleyna-server] dleyna-server: Segfault when plugging in a 
secondary screen
Added tag(s) moreinfo.

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

Bug#848863: dleyna-server: Segfault when pluggin secondary screen

[Andreas Henriksson]

Control: tags  -1 + moreinfo

Hello Younes SERRAJ,

Thanks for your bug report. Could you please get a backtrace
for the segfault?

On Tue, Dec 20, 2016 at 10:53:20AM +0100, Younes SERRAJ wrote:
> When pluggin a secondary screen, the primary one goes black.
> After investigating, I found that dleyna-server segfaulted.
> 
> * What led up to the situation?
> 
> Pluggin a secondary screen (whether it's VGA or HP DisplayPort).
> The secondary screen works properly but the primary one goes black and I need 
> to reboot to make it work again.
> 

First make sure you have debug symbols:

apt install dleyna-server-dbg

(See also https://wiki.debian.org/AutomaticDebugPackages )

> $ sudo dmesg --clear

# attach gdb to the process
gdb --pid=$(pidof dleyna-server-service)
continue

> $ # plug secondary screen
> $ dmesg
> [  831.184618] dleyna-server-s[2654]: segfault at 8 ip 7f6ae6c13132 sp 
> 7fff82ba7850 error 4 in libdleyna-server-1.0.so.1.0.3[7f6ae6c03000+21000]
[...]

bt full

(See also https://wiki.debian.org/HowToGetABacktrace )

Regards,
Andreas Henriksson

Bug#850023: ImportError when importing ruamel.yaml

[Chris Lamb]

Vincent Bernat wrote:

> > However, it looks like this "should" work:
> >
> >install_requires=dict(
> >[…]
> >py27=["ruamel.ordereddict", "typing"],
> >[…]
> >)
> 
> This seems to only work if the package is installed at build time. I'll push a
> fixed version soon.

Ah, ie. missing Build-Depends on python[2]-typing?


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#811971: marked as done (telepathy-logger-qt: FTBFS with GCC 6: symbol changes)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2017 09:03:37 +
with message-id 
and subject line Bug#811971: fixed in telepathy-logger-qt 15.04.0-2
has caused the Debian Bug report #811971,
regarding telepathy-logger-qt: FTBFS with GCC 6: symbol changes
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.)


-- 
811971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: telepathy-logger-qt
Version: 15.04.0-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-symbols

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libtelepathy-logger-qt5/DEBIAN/symbols 
> doesn't match completely debian/libtelepathy-logger-qt5.symbols
> --- debian/libtelepathy-logger-qt5.symbols 
> (libtelepathy-logger-qt5_15.04.0-1_amd64)
> +++ dpkg-gensymbolsy0jrpl 2016-01-19 09:24:55.707778966 +
> @@ -1,10 +1,10 @@
>  libtelepathy-logger-qt.so.5 libtelepathy-logger-qt5 #MINVER#
> - 
> (optional=templinst)_Z17qRegisterMetaTypeI15QDBusObjectPathEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS3_Xaasr12QMetaTypeId2IS3_E7DefinedntsrS8_9IsBuiltInEE11DefinedTypeE@Base
>  15.04.0
> +#MISSING: 15.04.0-1# 
> (optional=templinst)_Z17qRegisterMetaTypeI15QDBusObjectPathEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS3_Xaasr12QMetaTypeId2IS3_E7DefinedntsrS8_9IsBuiltInEE11DefinedTypeE@Base
>  15.04.0
>   _ZN10QByteArrayD1Ev@Base 15.04.0
>   _ZN10QByteArrayD2Ev@Base 15.04.0
> - _ZN10QDBusErrorD1Ev@Base 15.04.0
> - _ZN10QDBusErrorD2Ev@Base 15.04.0
> - 
> (optional=templinst)_ZN14QSharedPointerIN3Tpl5EventEE5derefEPN15QtSharedPointer20ExternalRefCountDataE@Base
>  15.04.0
> +#MISSING: 15.04.0-1# _ZN10QDBusErrorD1Ev@Base 15.04.0
> +#MISSING: 15.04.0-1# _ZN10QDBusErrorD2Ev@Base 15.04.0
> +#MISSING: 15.04.0-1# 
> (optional=templinst)_ZN14QSharedPointerIN3Tpl5EventEE5derefEPN15QtSharedPointer20ExternalRefCountDataE@Base
>  15.04.0
>   
> (optional=templinst)_ZN14QSharedPointerIN3Tpl6EntityEE5derefEPN15QtSharedPointer20ExternalRefCountDataE@Base
>  15.04.0
>   
> (optional=templinst)_ZN14QSharedPointerIN3Tpl9CallEventEE5derefEPN15QtSharedPointer20ExternalRefCountDataE@Base
>  15.04.0
>   
> (optional=templinst)_ZN14QSharedPointerIN3Tpl9LogWalkerEE5derefEPN15QtSharedPointer20ExternalRefCountDataE@Base
>  15.04.0
> @@ -14,25 +14,25 @@
>   
> (optional=templinst)_ZN15QtSharedPointer33ExternalRefCountWithCustomDeleterIN3Tpl9CallEventENS_13NormalDeleterEE7deleterEPNS_20ExternalRefCountDataE@Base
>  15.04.0
>   
> (optional=templinst)_ZN15QtSharedPointer33ExternalRefCountWithCustomDeleterIN3Tpl9LogWalkerENS_13NormalDeleterEE7deleterEPNS_20ExternalRefCountDataE@Base
>  15.04.0
>   
> (optional=templinst)_ZN15QtSharedPointer33ExternalRefCountWithCustomDeleterIN3Tpl9TextEventENS_13NormalDeleterEE7deleterEPNS_20ExternalRefCountDataE@Base
>  15.04.0
> - 
> (optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI15QDBusObjectPathLb1EE6CreateEPKv@Base
>  15.04.0
> - 
> (optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI15QDBusObjectPathLb1EE6DeleteEPv@Base
>  15.04.0
> +#MISSING: 15.04.0-1# 
> (optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI15QDBusObjectPathLb1EE6CreateEPKv@Base
>  15.04.0
> +#MISSING: 15.04.0-1# 
> (optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI15QDBusObjectPathLb1EE6DeleteEPv@Base
>  15.04.0
>   
> (optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI15QDBusObjectPathLb1EE8DestructEPv@Base
>  15.04.0
>   
> (optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI15QDBusObjectPathLb1EE9ConstructEPvPKv@Base
>  15.04.0
> - 
> (optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIP23QDBusPendingCallWatcherLb1EE6CreateEPKv@Base
>  15.04.0
> - 
> (optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIP23QDBusPendingCallWatcherLb1EE6DeleteEPv@Base
>  15.04.0
> +#MISSING: 15.04.0-1# 
> 

Bug#850023: ImportError when importing ruamel.yaml

[Elena ``of Valhalla'']

On 2017-01-06 at 22:51:55 +, Chris Lamb wrote:
> > ImportError when importing ruamel.yaml
> 
> So, the binary package is missing a Depends on `python-typing`.

uh, thanks, I didn't think to check of typing for a backport to py2.

That's indeed easy to workaround

-- 
Elena ``of Valhalla''

Bug#849777: shutter: CVE-2016-10081: Insecure use of perl exec()

[Dominique Dumont]

On Friday, 6 January 2017 21:57:57 CET Salvatore Bonaccorso wrote:
> Btw, it would be good/great to forward any applied patch to upstream.

Done: https://bugs.launchpad.net/shutter/+bug/1652600/comments/6

(this is a bit confusing because launchpad is usually downstream...)

All the best
-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Processed: Bug#850023 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 850023 pending
Bug #850023 [python-ruamel.yaml] ImportError when importing ruamel.yaml
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#850023: marked as pending

[Vincent Bernat]

tag 850023 pending
thanks

Hello,

Bug #850023 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=python-modules/packages/ruamel.yaml.git;a=commitdiff;h=a0a9ef3

---
commit a0a9ef3eebe1fd45a60af6b4e8c29ec04c276077
Author: Vincent Bernat 
Date:   Sat Jan 7 08:43:18 2017 +0100

Build-Depends on python-typing

diff --git a/debian/changelog b/debian/changelog
index 4850af3..49f2d76 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,12 @@
-ruamel.yaml (0.13.4-2) UNRELEASED; urgency=medium
+ruamel.yaml (0.13.4-2) unstable; urgency=medium
 
+  [ Ondřej Nový ]
   * Enable autopkgtest-pkg-python testsuite
 
- -- Ondřej Nový   Tue, 03 Jan 2017 10:48:33 +0100
+  [ Vincent Bernat ]
+  * Build-Depends on python-typing. Closes: #850023.
+
+ -- Vincent Bernat   Sat, 07 Jan 2017 08:43:02 +0100
 
 ruamel.yaml (0.13.4-1) unstable; urgency=medium