Bug#874276: ca-certificates-java: fails to install on armhf: Error: missing `server' JVM at `/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'

[Sebastiaan Couwenberg]

Is anyone working on this issue?

It's preventing the build of many packages on armhf and by extension
their transitions.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#876509: deal.ii FTBFS with lapack

[Graham Inggs]

Control: reassign -1 src:trilinos 12.10.1-4
Control: affects -1 src:deal.ii
Control: block -1 by 876958

Hi Anton

On 23 September 2017 at 01:23, Anton Gladky  wrote:
> deal.ii FTBFS in the sid. Probably due to the new upload of lapack.

Yes indeed, thanks for picking this up.  Trilinos needs a rebuild, I
have requested a binNMU (#876958)

Regards
Graham

Bug#876958: nmu: trilinos_12.10.1-4

[Graham Inggs]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: debian-science-maintain...@lists.alioth.debian.org

Dear Release Team

Lapack recently switched to multiarch and Trilinos needs to be rebuilt
in order to pick up the new locations of liblapack.so and libblas.so.
This causes deal.ii (its only reverse-dependency) to FTBFS (see
#876509).  Please schedule the following binNMU:

nmu trilinos_12.10.1-4 . ANY . -m 'Rebuild against multiarch lapack'

Regards
Graham

Bug#876953: Updating the bip Uploaders list

[Tobias Frost]

Source: bip
Version: 0.8.9-1.1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Arnaud Cornet  wishes no longer to be uploader of bip.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#876956: O: gnudoq -- An open source, graphical Su Doku generator and solver with printer support

[Tobias Frost]

Package: wnpp

The current maintainer of gnudoq, Arnaud Cornet ,
has orphaned this package.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: gnudoq
Binary: gnudoq
Version: 0.94-2.2
Maintainer: Arnaud Cornet 
Build-Depends: cdbs, libqt4-dev, qt4-dev-tools, g++ (>= 4.0.2-2), debhelper (>= 
10)
Architecture: any
Standards-Version: 3.7.3
Format: 3.0 (quilt)
Files:
 fbc2b857ff4d0b5002a6a142e3819444 1871 gnudoq_0.94-2.2.dsc
 f4316042b7f5bc98292f4e082c7ec193 1347765 gnudoq_0.94.orig.tar.gz
 837d09c3cceaa6bab65c523808c8c274 4772 gnudoq_0.94-2.2.debian.tar.xz
Checksums-Sha256:
 b29ce99105fa30dcb14cebc5c23aeca327ca48024199f78ae9680381fc1e4188 1871 
gnudoq_0.94-2.2.dsc
 0bc1143bb462f354852edad4108d6353230f5414304eec9118a681b147df387a 1347765 
gnudoq_0.94.orig.tar.gz
 6d68393ab79ef250991a59f663f11677372f7f54a4b81bdb8f813ed01dfa72b6 4772 
gnudoq_0.94-2.2.debian.tar.xz
Homepage: https://tracker.debian.org/pkg/gnudoq
Package-List: 
 gnudoq deb games optional arch=any
Directory: pool/main/g/gnudoq
Priority: source
Section: games

Package: gnudoq
Source: gnudoq (0.94-2.2)
Version: 0.94-2.2+b1
Installed-Size: 140
Maintainer: Arnaud Cornet 
Architecture: amd64
Depends: libc6 (>= 2.14), libgcc1 (>= 1:3.0), libqtcore4 (>= 4:4.6.1), 
libqtgui4 (>= 4:4.5.3), libstdc++6 (>= 5.2)
Description-en: An open source, graphical Su Doku generator and solver with 
printer support
 GNUDoQ is an open source, graphical Su Doku generator and solver that features
 a powerful Su Doku generator, a Su Doku solver a Puzzle printouts or PDF
 exports.
 This program is based on the excellent work of the GNUDoku team, which
 developed the Su Doku engine behind GNUDoQ.
Description-md5: dd56e9da7de899efd1f2ed32ec4ed4ce
Homepage: https://tracker.debian.org/pkg/gnudoq
Tag: game::puzzle, implemented-in::c++, role::program, suite::gnu,
 uitoolkit::qt, use::gameplaying
Section: games
Priority: optional
Filename: pool/main/g/gnudoq/gnudoq_0.94-2.2+b1_amd64.deb
Size: 40992
MD5sum: 71b640c3481a99545e6f559f98537592
SHA256: 746495c10caed178a7b24277a19b8a55f6737ea219994117d7ba66c2bcd8653c



signature.asc
Description: PGP signature

Bug#876950: O: dns2tcp -- TCP over DNS tunnel client and server

[Tobias Frost]

Package: wnpp

The current maintainer of dns2tcp, Arnaud Cornet ,
has orphaned this package.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: dns2tcp
Binary: dns2tcp
Version: 0.5.2-1.1
Maintainer: Arnaud Cornet 
Build-Depends: debhelper (>= 7.4.0), dh-autoreconf
Architecture: any
Standards-Version: 3.8.4
Format: 3.0 (quilt)
Files:
 e1b9ceb3791bb2d6be3af3fbd0bd69d0 1718 dns2tcp_0.5.2-1.1.dsc
 51c5dc69f5814c2936ce6832217d292d 173585 dns2tcp_0.5.2.orig.tar.gz
 c03f620b4612d00c8a20932f30abd4f3 3188 dns2tcp_0.5.2-1.1.debian.tar.xz
Checksums-Sha256:
 8aa4cfafea0548e7961b8f5944cf2a065ee16925753d1a137db0e7b88e14bc90 1718 
dns2tcp_0.5.2-1.1.dsc
 ea9ef59002b86519a43fca320982ae971e2df54cdc54cdb35562c751704278d9 173585 
dns2tcp_0.5.2.orig.tar.gz
 658b12ae04794fd95ebf370a456b6bb1f54c86686b1bf4f62d4653b9d39a106e 3188 
dns2tcp_0.5.2-1.1.debian.tar.xz
Homepage: http://www.hsc.fr/ressources/outils/dns2tcp/
Package-List: 
 dns2tcp deb net optional arch=any
Directory: pool/main/d/dns2tcp
Priority: source
Section: net

Package: dns2tcp
Source: dns2tcp (0.5.2-1.1)
Version: 0.5.2-1.1+b2
Installed-Size: 140
Maintainer: Arnaud Cornet 
Architecture: amd64
Depends: libc6 (>= 2.14)
Description-en: TCP over DNS tunnel client and server
 dns2tcp is a set of tools allowing to encapsulate a TCP session in DNS
 packets. This type of encapsulation generates smaller packets compeared to
 ip-over-DNS tools, thus allows a better throughput. The client does not need
 root priledges.
Description-md5: b6f006bd6b7256e3d2a8a3ea301a7617
Homepage: http://www.hsc.fr/ressources/outils/dns2tcp/
Tag: network::vpn, protocol::dns, protocol::tcp, role::program,
 works-with::network-traffic
Section: net
Priority: optional
Filename: pool/main/d/dns2tcp/dns2tcp_0.5.2-1.1+b2_amd64.deb
Size: 43732
MD5sum: 990843093d1b64b5bf70fefa90ab066a
SHA256: 32f9d5a1476bf0b682bd397c0816696757ba752d6eaacc95f068245188b66980



signature.asc
Description: PGP signature

Bug#876952: Updating the ruby-gnome2 Uploaders list

[Tobias Frost]

Source: ruby-gnome2
Version: 3.1.8-7
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Arnaud Cornet  wishes no longer to be uploader of 
ruby-gnome2.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#876957: O: gurgitate-mail -- E-mail processor and filter with configuration files in ruby

[Tobias Frost]

Package: wnpp

The current maintainer of gurgitate-mail, Arnaud Cornet ,
has orphaned this package.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: gurgitate-mail
Binary: gurgitate-mail
Version: 1.10.0-1
Maintainer: Arnaud Cornet 
Build-Depends: cdbs, debhelper (>= 5.0.37), ruby
Architecture: all
Standards-Version: 3.7.3
Format: 1.0
Files:
 c29c985c516242774029c8775fa8fa5b 664 gurgitate-mail_1.10.0-1.dsc
 b6dfdbf23ab68a8e0f408635b4895676 33263 gurgitate-mail_1.10.0.orig.tar.gz
 90923265f60463aa57b362ec294ada78 2986 gurgitate-mail_1.10.0-1.diff.gz
Checksums-Sha256:
 11abf4d324a4fd959bba65b60c38b990bdd0040a5e525a21997646c0adc92ff9 664 
gurgitate-mail_1.10.0-1.dsc
 a813a2d27321f0766a3ceeda3ad69991ad26fe49d071860c128f53cd84b52821 2986 
gurgitate-mail_1.10.0-1.diff.gz
 101a5f6646f98a81c34461575abfc177bcb29f4bdbb2de4de232c87e6ebdc7b5 33263 
gurgitate-mail_1.10.0.orig.tar.gz
Homepage: http://www.dagbrown.com/software/gurgitate-mail/
Directory: pool/main/g/gurgitate-mail
Priority: source
Section: mail

Package: gurgitate-mail
Version: 1.10.0-1
Installed-Size: 144
Maintainer: Arnaud Cornet 
Architecture: all
Depends: ruby
Description-en: E-mail processor and filter with configuration files in ruby
 gurgitate-mail is a mail filter that is small and easy to use. The
 configuration files in ruby programming language make gurgitate-mail flexible
 and powerful. It can sort your incoming mail, pipe them through another
 program or do whatever processing you program in one of its configuration
 file. It can store mails in folders of MBox or Maildir formats.
Description-md5: 4bc8081c7d3f80f0d3748b379576d113
Homepage: http://www.dagbrown.com/software/gurgitate-mail/
Section: mail
Priority: optional
Filename: pool/main/g/gurgitate-mail/gurgitate-mail_1.10.0-1_all.deb
Size: 26202
MD5sum: e9b759b81822ca751599ddf3006b6503
SHA256: 3432064fe30476d9899ea1d2fa4a0a6e26ca82ba3622f875e35d06cecf0a881a



signature.asc
Description: PGP signature

Bug#876954: Updating the ruby-cmdparse Uploaders list

[Tobias Frost]

Source: ruby-cmdparse
Version: 2.0.6-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Arnaud Cornet  wishes no longer to be uploader of 
ruby-cmdparse.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#876951: O: libmpd -- High-level client library for accessing Music Player Daemon

[Tobias Frost]

Package: wnpp

The current maintainer of libmpd, Arnaud Cornet ,
has orphaned this package.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: libmpd
Binary: libmpd1, libmpd1-dbg, libmpd-dev
Version: 0.20.0-1.3
Maintainer: Arnaud Cornet 
Build-Depends: libglib2.0-dev, debhelper (>= 7.0.50~), quilt, dh-autoreconf
Architecture: any
Standards-Version: 3.8.4
Format: 1.0
Files:
 cd4e5042fb29a1017c2eb4c8fe63bc90 1458 libmpd_0.20.0-1.3.dsc
 2f1c99e12c69f7d95cfd1e27368056ed 363996 libmpd_0.20.0.orig.tar.gz
 62a7d4490852f3b59bdd3db0e0224a0b 3698 libmpd_0.20.0-1.3.diff.gz
Checksums-Sha256:
 e8d6104fba71870523d9a9600a13d4ce673e2b4ba0654a75696cf422ac96836e 1458 
libmpd_0.20.0-1.3.dsc
 7205b01b007b2ef06f19aacca26fec2673b730f1a9b6c2ce0ed6728c9ac67723 363996 
libmpd_0.20.0.orig.tar.gz
 09a509224c1a9815656333cfcf1d755d069b51c80a32674011d1280ffeb513b9 3698 
libmpd_0.20.0-1.3.diff.gz
Homepage: http://gmpc.wikia.com/
Package-List: 
 libmpd-dev deb libdevel optional arch=any
 libmpd1 deb libs optional arch=any
 libmpd1-dbg deb debug extra arch=any
Directory: pool/main/libm/libmpd
Priority: source
Section: libs

Package: libmpd1
Source: libmpd
Version: 0.20.0-1.3
Installed-Size: 122
Maintainer: Arnaud Cornet 
Architecture: amd64
Depends: libc6 (>= 2.3), libglib2.0-0 (>= 2.16.0)
Description-en: High-level client library for accessing Music Player Daemon
 LibMpd is a library that provides high-level, callback-based access to
 Music Player Daemon (mpd).
 .
 This package contains the shared libraries.
Description-md5: f68285677e81099625f7602eb71ee49e
Homepage: http://gmpc.wikia.com/
Tag: role::shared-lib
Section: libs
Priority: optional
Filename: pool/main/libm/libmpd/libmpd1_0.20.0-1.3_amd64.deb
Size: 39810
MD5sum: 7d9b6ef89f77ba47a6874e58480c6fa8
SHA256: f110f1613b22c6ece7991ac3eca23347039943f5a06960b70bd81a118a5c2acd

Package: libmpd1-dbg
Source: libmpd
Version: 0.20.0-1.3
Installed-Size: 262
Maintainer: Arnaud Cornet 
Architecture: amd64
Depends: libmpd1 (= 0.20.0-1.3)
Description-en: High-level client library for accessing Music Player Daemon
 LibMpd is a library that provides high-level, callback-based access to
 Music Player Daemon (mpd).
 .
 This package contains the debugging symbols.
Description-md5: 7a92a5f548bf85da2d38497b5243483f
Homepage: http://gmpc.wikia.com/
Tag: role::debug-symbols
Section: debug
Priority: optional
Filename: pool/main/libm/libmpd/libmpd1-dbg_0.20.0-1.3_amd64.deb
Size: 63216
MD5sum: cffdcbe2f08949dfa49bfc88d7bc5f8a
SHA256: dccddff4d50ea1abbdfcd6a6a6d4afa64458be76b5b5d9e2b1985728c1d9c2a1

Package: libmpd-dev
Source: libmpd
Version: 0.20.0-1.3
Installed-Size: 92
Maintainer: Arnaud Cornet 
Architecture: amd64
Depends: libmpd1 (= 0.20.0-1.3), pkg-config
Description-en: High-level client library for accessing Music Player Daemon
 LibMpd is a library that provides high-level, callback-based access to
 Music Player Daemon (mpd).
 .
 This package contains the development libraries, headers and documentation.
Description-md5: cbbcab803f9be956e62c0803dc2bba1b
Homepage: http://gmpc.wikia.com/
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/libm/libmpd/libmpd-dev_0.20.0-1.3_amd64.deb
Size: 17716
MD5sum: 4ca3fa20c6e960299a5cea96713e825e
SHA256: f250e9497fc8fa375c6eace616837d539a6b923c06d6faefc10a7ad010465888



signature.asc
Description: PGP signature

Bug#876955: Updating the ruby-rubytorrent Uploaders list

[Tobias Frost]

Source: ruby-rubytorrent
Version: 0.3-5
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Arnaud Cornet  wishes no longer to be uploader of 
ruby-rubytorrent.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#876885: fvwm: FvwmConsole can't be configured with X resources

[Danek Duvall]

> I see this as a bug in the man page to clarify this. Namely the
> default is FvwmConsole's resource is that of the terminal
> x-terminal-emulator points uses. Also clarify that the example
> resources were written for xterm with the -name FvwmConsole flag.

I figured that would be the likely outcome.  That'd be okay by me.  But see
below.

> > For now, my workaround is to simply run FvwmConsole with the -name
> > option explictly added to the commandline.
> 
> I don't see this as a workaround, but how it should be handled in
> Debian. If you want FvwmConsole's terminal to use a different resource
> than your default terminal's resource for configuration, that is what
> the -name feature is for. You can also use it in conjunction with the
> -terminal option to ensure you are running a terminal that supports
> it.

I see it as a workaround because it requires explicit configuration where
none should be necessary.  It seems obvious to me that one would want to
use a different configuration from one's normal terminal emulator, since
that's not really what's needed here.  FvwmConsole simply needs some sort
of text widget with history and line editing and the ability to send a
finalized line to a listening program, which is only superficially similar
to a real terminal.  That said, a terminal emulator is easy to repurpose.

However, it occurred to me that there might be another way to do this.  I
discovered the RESOURCE_NAME environment variable, which I'd never used
before, but if I put

setenv("RESOURCE_NAME", "FvwmConsole", 1);

right before the execvp() call, it works perfectly, and should be
completely ignored by non-X11-toolkit programs.  Using the environment
makes sense here, since the process tree involved here is extremely minimal
-- only FvwmConsoleC in addition to the terminal emulator, and it doesn't
care.  In fact, I think this change (along with the one to remove -name)
might be worth sending upstream.

Thanks,
Danek

Bug#870873: exiv2: FTBFS: some symbols or patterns disappeared in the symbols file

[Raphael Hertzog]

On Sat, 05 Aug 2017, Jakub Wilk wrote:
> exiv2 FTBFS on i386:

And on amd64 currently too:
   dh_makeshlibs -O--parallel -O--buildsystem=cmake
dpkg-gensymbols: avertissement: certains nouveaux symboles sont apparus dans le 
fichier des symboles : Veuillez consulter le fichier de différences ci-dessous
dpkg-gensymbols: avertissement: certains symboles ou motifs ont disparu du 
fichier des symboles : Veuillez consulter le fichier de différences ci-dessous
dpkg-gensymbols: avertissement: debian/libexiv2-26/DEBIAN/symbols ne correspond 
pas complètement à debian/libexiv2-26.symbols
--- debian/libexiv2-26.symbols (libexiv2-26_0.26-1_amd64)
+++ dpkg-gensymbolsp9ehnh   2017-09-26 15:54:10.161285312 +
@@ -465,16 +465,20 @@
  
_ZN5Exiv213parseRationalERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERb@Base
 0.25
  
_ZN5Exiv213pathOfFileUrlERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 0.25
  _ZN5Exiv213plusImageTypeE@Base 0.26
- 
_ZN5Exiv213toBasicStringIcA10_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26
- 
_ZN5Exiv213toBasicStringIcA13_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26
+#MISSING: 0.26-1# 
_ZN5Exiv213toBasicStringIcA10_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26
+#MISSING: 0.26-1# 
_ZN5Exiv213toBasicStringIcA13_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26
  
_ZN5Exiv213toBasicStringIcA14_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26
  
_ZN5Exiv213toBasicStringIcA15_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26
- 
_ZN5Exiv213toBasicStringIcA32_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26
+#MISSING: 0.26-1# 
_ZN5Exiv213toBasicStringIcA32_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26
  
_ZN5Exiv213toBasicStringIcA4_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26
+ 
_ZN5Exiv213toBasicStringIcA59_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26-1
  
_ZN5Exiv213toBasicStringIcA5_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26
+ 
_ZN5Exiv213toBasicStringIcA7_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26-1
+ 
_ZN5Exiv213toBasicStringIcA9_cEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26-1
  
(optional=templinst)_ZN5Exiv213toBasicStringIcNS_8Internal5IfdIdEEENSt7__cxx1112basic_stringIT_St11char_traitsIS5_ESaIS5_EEERKT0_@Base
 0.26
  
(optional=templinst)_ZN5Exiv213toBasicStringIcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcENS2_IT_S3_IS7_ESaIS7_EEERKT0_@Base
 0.26
  
(optional=templinst)_ZN5Exiv213toBasicStringIcPKcEENSt7__cxx1112basic_stringIT_St11char_traitsIS5_ESaIS5_EEERKT0_@Base
 0.26
+ 
_ZN5Exiv213toBasicStringIcPcEENSt7__cxx1112basic_stringIT_St11char_traitsIS4_ESaIS4_EEERKT0_@Base
 0.26-1
  
(optional=templinst)_ZN5Exiv213toBasicStringIciEENSt7__cxx1112basic_stringIT_St11char_traitsIS3_ESaIS3_EEERKT0_@Base
 0.26
  
(optional=templinst)_ZN5Exiv213toBasicStringIclEENSt7__cxx1112basic_stringIT_St11char_traitsIS3_ESaIS3_EEERKT0_@Base
 0.26
  
(optional=templinst)_ZN5Exiv213toBasicStringIcmEENSt7__cxx1112basic_stringIT_St11char_traitsIS3_ESaIS3_EEERKT0_@Base
 0.26
@@ -3137,8 +3141,9 @@
  
(optional=templinst)_ZN5Exiv28stringToIfEET_RKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERb@Base
 0.26
  
(optional=templinst)_ZN5Exiv28stringToIjEET_RKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERb@Base
 0.26
  
(optional=templinst)_ZN5Exiv28stringToIlEET_RKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERb@Base
 0.26
- 
_ZN5Exiv28toStringIA4_cEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKT_@Base
 0.26
- 
_ZN5Exiv28toStringIA9_cEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKT_@Base
 0.26
+ 
_ZN5Exiv28toStringIA37_cEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKT_@Base
 0.26-1
+#MISSING: 0.26-1# 
_ZN5Exiv28toStringIA4_cEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKT_@Base
 0.26
+#MISSING: 0.26-1# 
_ZN5Exiv28toStringIA9_cEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKT_@Base
 0.26
  
(optional=templinst)_ZN5Exiv28toStringIPKhEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKT_@Base
 0.26
  
(optional=templinst)_ZN5Exiv28toStringIPhEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKT_@Base
 0.26
  
(optional=templinst)_ZN5Exiv28toStringISt4pairIiiEEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKT_@Base
 0.26
@@ -3718,7 +3723,7 @@
  _ZNK5Exiv215StringValueBase6toLongEl@Base 0.25
  _ZNK5Exiv215StringValueBase7toFloatEl@Base 0.25
  
_ZNK5Exiv215XmpPropertyInfoeqERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 0.25
- 
_ZNK5Exiv222LangAltValueComparatorclERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_@Base
 0.26
+#MISSING: 0.26-1# 

Bug#876947: di-netboot-assistant: conffiles not removed

[Paul Wise]

Package: di-netboot-assistant
Version: 0.49
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate

The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete conffiles on upgrade.

https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
https://manpages.debian.org/man/1/dh_installdeb

This bug report brought to you by adequate:

http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ pkg=di-netboot-assistant ; adequate $pkg ; dpkg-query -W -f='${Conffiles}\n' 
$pkg | grep obsolete
di-netboot-assistant: obsolete-conffile /etc/di-netboot-assistant/elilo.HEAD
 /etc/di-netboot-assistant/elilo.HEAD 1d203651eba838c1c3ba869038edc7a5 obsolete

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

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

Versions of packages di-netboot-assistant depends on:
ii  curl  7.55.1-1
ii  wget  1.19.1-4

Versions of packages di-netboot-assistant recommends:
ii  grub-efi-amd64-bin2.02-2
pn  tftpd-hpa | atftpd | dnsmasq  

Versions of packages di-netboot-assistant suggests:
pn  dnsmasq | isc-dhcp-server | udhcpd  
ii  syslinux3:6.03+dfsg-14.1
pn  vim-addon-manager   

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#876948: FTBFS: fails to configure due to change in gcc -dumpversion output

[Raphaël Hertzog]

Source: exiv2
Version: 0.25-3.1
Severity: serious
Tags: patch
Justification: FTBFS

I am unable to rebuild exiv2 0.26 in experimental. The build fails on
dh_auto_configure. It turns out CMakeLists.txt tries to parse
g++ -dumpversion as a two component value but we currently get a single one:
$ g++ -dumpversion
7

This patch fixes the issue for me:
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -83,9 +83,8 @@ IF( MINGW OR UNIX )
 execute_process(COMMAND ${CMAKE_CXX_COMPILER} -dumpversion OUTPUT_VARIABLE 
GCC_VERSION)
 string(REGEX MATCHALL "[0-9]+" GCC_VERSION_COMPONENTS ${GCC_VERSION})
 list(GET GCC_VERSION_COMPONENTS 0 GCC_MAJOR)
-list(GET GCC_VERSION_COMPONENTS 1 GCC_MINOR)

-message(STATUS Compiler: ${COMPILER} " Major:" ${GCC_MAJOR} " Minor:" 
${GCC_MINOR})
+message(STATUS Compiler: ${COMPILER} " Major:" ${GCC_MAJOR} " Full version 
string:" ${GCC_VERSION})

 IF ( CYGWIN OR ( ${GCC_MAJOR} GREATER 5 ))
 ADD_DEFINITIONS( -std=gnu++98 ) # to support snprintf

But then I get another error due to missing symbols in 
debian/libexiv2-26.symbols.
But this is already tracked in #870873.

-- System Information:
Debian Release: buster/sid
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#876949: stretch-pu: package postfix/3.1.6-0+deb9u1

[Scott Kitterman]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

This upload is intended to solve several problems.  While it's somewhat
unusual, since it includes new upstream releases, the upstream changes are
very targetted and all things that I believe are appropriate to fix in a
stable update:

Security:

Security: Berkeley DB 2 and later try to read settings from
a file DB_CONFIG in the current directory.

The Debian security team requested this be fixed in a stable update.

Safety:

Safety net: append a null byte to vstring buffers, so that
C-style string operations won't scribble past the end.

Regression corrections (relative to postfix 2.11 in oldstable):

Compatibility fix (introduced: Postfix 3.1): some Milter
applications do not recognize macros sent as {name} when
macros have single-character names. Postfix now sends such
macros without {} as it has done historically.

Workaround (introduced: Postfix 3.0 20140718): prevent MIME
downgrade of Postfix-generated message/delivery status.
It's supposed to be 7bit, therefore quoted-printable encoding
is not expected. Problem reported by Griff. File:
bounce/bounce_notify_util.c.

Additionally, there's a packaging fix for a bug that broke multi-instance.

Each of these changes is small and self-contained.  Due to my recent lack of
time for Debian work, the upstream changes have had three months of use with
no issues reported on the very active postfix-users mailing list.

I have the package built and ready to upload.

Scott K
diff -Nru postfix-3.1.4/debian/changelog postfix-3.1.6/debian/changelog
--- postfix-3.1.4/debian/changelog	2017-05-21 14:38:07.0 -0400
+++ postfix-3.1.6/debian/changelog	2017-09-27 00:59:24.0 -0400
@@ -1,3 +1,40 @@
+postfix (3.1.6-0+deb9u1) stretch; urgency=medium
+
+[Wietse Venema]
+
+  * New Upstream 3.1.5
+- Compatibility fix (introduced: Postfix 3.1): some Milter
+  applications do not recognize macros sent as {name} when
+  macros have single-character names. Postfix now sends such
+  macros without {} as it has done historically. Viktor
+  Dukhovni. File: milter/milter.c.
+- Safety net: append a null byte to vstring buffers, so that
+  C-style string operations won't scribble past the end. File:
+  vstring.c.
+- Workaround (introduced: Postfix 3.0 20140718): prevent MIME
+  downgrade of Postfix-generated message/delivery status.
+  It's supposed to be 7bit, therefore quoted-printable encoding
+  is not expected. Problem reported by Griff. File:
+  bounce/bounce_notify_util.c.
+  * New Upstream 3.1.6 
+- Security: Berkeley DB 2 and later try to read settings from
+  a file DB_CONFIG in the current directory.  This undocumented
+  feature may introduce undisclosed vulnerabilities resulting
+  in privilege escalation with Postfix set-gid programs
+  (postdrop, postqueue) before they chdir to the Postfix queue
+  directory, and with the postmap and postalias commands
+  depending on whether the user's current directory is writable
+  by other users. This fix does not change Postfix behavior
+  for Berkeley DB < 3, but reduces file create performance
+  for Berkeley DB 3 .. 4.6.  File: util/dict_db.c.  Closes: #864942
+
+[Scott Kitterman]
+
+  * Refresh debian/patches/11_postmap_update.diff
+  * Use full path to main.cf in postfix-instance-generator.  Closes: #873957
+
+ -- Scott Kitterman   Wed, 27 Sep 2017 00:56:28 -0400
+
 postfix (3.1.4-7) unstable; urgency=medium
 
   * Fix use of smtp binary for lmtp service on new installs and bump version
diff -Nru postfix-3.1.4/debian/patches/11_postmap_update.diff postfix-3.1.6/debian/patches/11_postmap_update.diff
--- postfix-3.1.4/debian/patches/11_postmap_update.diff	2017-05-19 10:50:13.0 -0400
+++ postfix-3.1.6/debian/patches/11_postmap_update.diff	2017-09-27 00:26:51.0 -0400
@@ -1,7 +1,7 @@
 Index: postfix/html/postmap.1.html
 ===
 postfix.orig/html/postmap.1.html	2016-03-01 05:01:20.999356738 -0700
-+++ postfix/html/postmap.1.html	2016-03-01 05:01:20.995356871 -0700
+--- postfix.orig/html/postmap.1.html	2017-09-27 00:26:44.474769942 -0400
 postfix/html/postmap.1.html	2017-09-27 00:26:44.466769942 -0400
 @@ -10,7 +10,7 @@
 postmap - Postfix lookup table management
  
@@ -24,8 +24,8 @@
instead of the default configuration directory.
 Index: postfix/man/man1/postmap.1
 ===
 postfix.orig/man/man1/postmap.1	2016-03-01 05:01:20.999356738 -0700
-+++ postfix/man/man1/postmap.1	2016-03-01 05:01:20.995356871 -0700
+--- postfix.orig/man/man1/postmap.1	2017-09-27 00:26:44.474769942 -0400
 postfix/man/man1/postmap.1	

Bug#876946: isc-dhcp-client: dhclient does not use enter and exit hooks when using -cf option

[Pedro Ribeiro]

Package: isc-dhcp-client
Version: 4.3.5-3
Severity: normal
Tags: lfs

dhclient is supposed to use the scripts at /etc/dhcp/dhclient-enter-hooks.d/
when it starts.

This works fine with dhclient -v . However, when using dhclient -cf
 , the hook scripts are not used.

This can be seen below, where the use of the the -cf option doesn't use
resolvconf to update /etc/resolv.conf, but when I omit the -cf flag everything
works fine.

I don't see any option in the default config that enables this, so I'm assuming
it's a bug.

~ > sudo dhclient -v -cf /var/lib/wicd/dhclient.conf wlan0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/60:67:20:c7:1b:d0
Sending on   LPF/wlan0/60:67:20:c7:1b:d0
Sending on   Socket/fallback
DHCPREQUEST of 192.168.1.106 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.106 from 192.168.1.1
RTNETLINK answers: File exists
bound to 192.168.1.106 -- renewal in 110002 seconds.
~ > cat /etc/resolv.conf
nameserver 192.168.1.1
~ > sudo dhclient -v wlan0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/60:67:20:c7:1b:d0
Sending on   LPF/wlan0/60:67:20:c7:1b:d0
Sending on   Socket/fallback
DHCPREQUEST of 192.168.1.106 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.106 from 192.168.1.1
RTNETLINK answers: File exists
bound to 192.168.1.106 -- renewal in 99741 seconds.
~ > cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.1
nameserver 127.0.0.1



-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (750, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.50-unofficial+grsec+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages isc-dhcp-client depends on:
ii  debianutils   4.8.1.1
ii  iproute2  4.9.0-1
ii  libc6 2.24-11+deb9u1
ii  libdns-export162  1:9.10.3.dfsg.P4-12.3+deb9u2
ii  libisc-export160  1:9.10.3.dfsg.P4-12.3+deb9u2

Versions of packages isc-dhcp-client recommends:
ii  isc-dhcp-common  4.3.5-3

Versions of packages isc-dhcp-client suggests:
pn  avahi-autoipd 
pn  isc-dhcp-client-ddns  
ii  resolvconf1.79

-- no debconf information

Bug#876945: whois: contact information not shown for .com and .net domains

[ryanc]

Package: whois
Version: 5.2.15
Severity: important

Dear Maintainer,

When I run whois on a .com or .net domain, only registry information is shown - 
for example:

$ whois debian.com
   Domain Name: DEBIAN.COM
   Registry Domain ID: 2012959_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.gandi.net
   Registrar URL: http://www.gandi.net
   Updated Date: 2017-03-30T01:14:19Z
   Creation Date: 1998-05-01T04:00:00Z
   Registry Expiry Date: 2018-04-30T04:00:00Z
   Registrar: Gandi SAS
   Registrar IANA ID: 81
   Registrar Abuse Contact Email: ab...@support.gandi.net
   Registrar Abuse Contact Phone: +33.170377661
   Domain Status: clientTransferProhibited 
https://icann.org/epp#clientTransferProhibited
   Name Server: DNSNODE.DEBIAN.ORG
   Name Server: SEC1.RCODE0.NET
   Name Server: SEC2.RCODE0.NET
   DNSSEC: signedDelegation
   DNSSEC DS Data: 5914 8 2 
E5F76E1F2EF8D2BFA9CFC580088CFA6EEE76520F6139656D68C563344FCA9E1D
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-09-27T03:43:51Z <<<
*TRUNCATED*

vs

$ whois debian.org
Domain Name: DEBIAN.ORG
Registry Domain ID: D4227449-LROR
Registrar WHOIS Server:
Registrar URL: http://www.gandi.net
Updated Date: 2017-04-10T08:37:51Z
Creation Date: 1999-03-10T05:00:00Z
Registry Expiry Date: 2018-03-10T05:00:00Z
Registrar Registration Expiration Date:
Registrar: Gandi SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Reseller:
Domain Status: clientTransferProhibited 
https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: C140274385-LROR
Registrant Name: SPI Hostmaster
Registrant Organization: Software in the Public Interest, Inc. - Debian Project
Registrant Street: P.O. Box 501248
Registrant City: Indianapolis
Registrant State/Province: IN
Registrant Postal Code: 46250-6248
Registrant Country: US
Registrant Phone: +49.6619012303
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: hostmas...@spi-inc.org
Registry Admin ID: C140274385-LROR
Admin Name: SPI Hostmaster
Admin Organization: Software in the Public Interest, Inc. - Debian Project
Admin Street: P.O. Box 501248
Admin City: Indianapolis
Admin State/Province: IN
Admin Postal Code: 46250-6248
Admin Country: US
Admin Phone: +49.6619012303
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: hostmas...@spi-inc.org
Registry Tech ID: C140274387-LROR
Tech Name: Debian Hostmaster
Tech Organization:
Tech Street: P.O. Box 501248
Tech City: Indianapolis
Tech State/Province:
Tech Postal Code: 46250-6248
Tech Country: US
Tech Phone: +43.6505121024
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: hostmas...@debian.org
Name Server: SEC1.RCODE0.NET
Name Server: SEC2.RCODE0.NET
Name Server: DNSNODE.DEBIAN.ORG
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2017-09-27T03:44:05Z <<<
*TRUNCATED*

It seems that verisign has changed the format of whois responsess:

http://www.circleid.com/posts/20170727_some_whois_lookup_services_might_be_broken/

-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages whois depends on:
ii  libc6 2.24-11+deb9u1
ii  libidn11  1.33-1

whois recommends no packages.

whois suggests no packages.

-- no debconf information

Bug#876626: RE : Re: Bug#876626: [Xastir] Bug#876626: Xastir loose TCP/IP data afer 12 hours of use

[mlhpub]

Sorry it is 12 hours and not days.I should have written "12 hours a day"... I 
usually start Xastir on 7.00 am and shutdown around 10:00 pm (saturdays and 
sundays).
Thanks, I will try update and tell if it is better.
73
MatthieuF4ACU
 Message d'origine De : David A Aitcheson 
 Date : 27/09/2017  02:07  (GMT+01:00) À : MLHPUB 
, 876...@bugs.debian.org Cc : "Iain R. Learmonth" 
 Objet : Re: Bug#876626: [Xastir] Bug#876626: Xastir loose 
TCP/IP data afer 12 hours of use 
Matthieu

Please clarify when the problem starts, is it after 12 HOURS or is it
after 12 DAYS? I rarely run my computer beyond 24 hours and probably
only run Xastir about 10 hours at a stretch so I may not be seeing the
issues you are seeing.

Once you convert to building from source for Xastir updating is simple,
just run a included "update" script that does a everything for you. I am
currently running Xastir V2.0.9 (8a3999d) Compiled (from source) on
Monday September 18 2017 at 17:17:00 EDT on my Laptop running Ubuntu
14.04.04-LTS

73
Dave
KB3EFS


On 09/26/2017 05:27 PM, MLHPUB wrote:
> Hello Ian,
>
> I don't know about latest snapshots.
> Maybe it does not occur with 2.0.9 version but I am not comfortable
> with upgrade outside of Debian repositiories...
>
> Regards,
>
> Matthieu
> F4ACU
>
> On Sun, 24 Sep 2017 10:55:13 +0100 "Iain R. Learmonth"
>  wrote:
>> Hi,
>>
>> On Sun, Sep 24, 2017 at 05:20:44AM -0400, David A Aitcheson wrote:
>> > > I usually use Xastir during all day, only with a TCP/IP to APRS-IS
>> > > connection at this moment (no radio link).
>> > > After more than 12 days uptime, Xastir loose many data from
>> APRS-IS :
>> > >
>> > > - ACK messages are not received
>> > > - positions reports (even visible on aprs.fi) are not displayed
>> > >
>> > > There is a kind of latency time on RX data from APRS-IS.
>> > >
>> > > It is necessary to quit and restart Xastir to retreive en normal
>> > > behavior.
>>
>> My question would be: does this occur in the latest Xastir snapshots?
>>
>> It's been a long time since there was a release of Xastir and I'm
>> sure the
>> Debian package is missing a number of fixes that have been applied
>> upstream.
>>
>> It's been on my todo list for a while to just update to a git
>> snapshot to
>> get some fixes into the Debian package, but I've not yet had time. If
>> someone can tell me this doesn't happen if you build from source then
>> that
>> would be an easy fix.
>>
>> Thanks,
>> Iain.
>>
>
>

Bug#876944: jessie-pu: package bwm-ng/0.6-3.1

[Samuel Henrique]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

​This is a small change on d/rules passing "​--without-libstatgrab" (as
advised by upstream on a duplicate bug report[1]) to fix #855215[2].

I confirmed the bug on Jessie, confirmed the fix on jessie-bpo (the 0.6.1
release was fixed), and confirmed this fix attached on jessie at 3
different machines (mine and the two people cited on changelog), it all
looks good. No regressions.

I also pushed the fix on git[3].

As i'm not a DD, Terceiro will sponsor my upload.

There's also more these bugreports[4][5][6].

[1]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746014#15
[2]​https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855215
​[3]
https://anonscm.debian.org/git/collab-maint/bwm-ng.git/log/?h=debian/jessie
[4]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826983
[5]https://bugs.launchpad.net/ubuntu/+source/bwm-ng/+bug/1502593
[6]https://bugs.launchpad.net/ubuntu/+source/bwm-ng/+bug/1719156


-- 
Samuel Henrique 


bwm-ng_0.6-3.1+deb8u1.debdiff
Description: Binary data

Bug#876943: redmine 3.3 allows closing parent tasks with open subtasks

[Joshua Judson Rosen]

Package: redmine
Version: 3.3.1-4

Redmine 3.3 allows closing issues despite the presence of unclosed subtasks;
this is a regression from previous versions of redmine, and has been fixed
upstream in the next minor-version release, redmine 3.4.0; see:

http://www.redmine.org/issues/10989

Should backport this to the stable release; otherwise it's just going to make
later upgrades harder for people who accumulate broken parent/subtask relations
in the interim.

The changeset from upstream *almost* applied cleanly; it required very minor 
changes
to deal with the slight different context.
Index: redmine-3.3.1/app/models/issue.rb
===
--- redmine-3.3.1.orig/app/models/issue.rb
+++ redmine-3.3.1/app/models/issue.rb
@@ -713,6 +713,9 @@ class Issue < ActiveRecord::Base
   @parent_issue.self_and_ancestors.any? {|a| a.relations_from.any? {|r| r.relation_type == IssueRelation::TYPE_PRECEDES && r.issue_to.would_reschedule?(self)}}
 )
 errors.add :parent_issue_id, :invalid
+  elsif !closed? && @parent_issue.closed?
+# cannot attach an open issue to a closed parent
+errors.add :base, :open_issue_with_closed_parent
   elsif !new_record?
 # moving an existing issue
 if move_possible?(@parent_issue)
@@ -931,9 +934,14 @@ class Issue < ActiveRecord::Base
   statuses << initial_status unless statuses.empty?
   statuses << default_status if include_default || (new_record? && statuses.empty?)
   statuses = statuses.compact.uniq.sort
-  if blocked?
+  if blocked? || descendants.open.any?
+# cannot close a blocked issue or a parent with open subtasks
 statuses.reject!(&:is_closed?)
   end
+  if ancestors.open(false).any?
+# cannot reopen a subtask of a closed parent
+statuses.select!(&:is_closed?)
+  end
   statuses
 end
   end
Index: redmine-3.3.1/config/locales/ar.yml
===
--- redmine-3.3.1.orig/config/locales/ar.yml
+++ redmine-3.3.1/config/locales/ar.yml
@@ -129,6 +129,7 @@ ar:
 circular_dependency: "هذه العلاقة سوف تخلق علاقة تبعية دائرية"
 cant_link_an_issue_with_a_descendant: "لا يمكن ان تكون المشكلة مرتبطة بواحدة من المهام الفرعية"
 earlier_than_minimum_start_date: "cannot be earlier than %{date} because of preceding issues"
+open_issue_with_closed_parent: "An open issue cannot be attached to a closed parent task"
 
   actionview_instancetag_blank_option: الرجاء التحديد
 
Index: redmine-3.3.1/config/locales/az.yml
===
--- redmine-3.3.1.orig/config/locales/az.yml
+++ redmine-3.3.1/config/locales/az.yml
@@ -197,6 +197,7 @@ az:
 circular_dependency: "Belə əlaqə dövri asılılığa gətirib çıxaracaq"
 cant_link_an_issue_with_a_descendant: "Tapşırıq özünün alt tapşırığı ilə əlaqəli ola bilməz"
 earlier_than_minimum_start_date: "cannot be earlier than %{date} because of preceding issues"
+open_issue_with_closed_parent: "An open issue cannot be attached to a closed parent task"
 
   support:
 array:
Index: redmine-3.3.1/config/locales/bg.yml
===
--- redmine-3.3.1.orig/config/locales/bg.yml
+++ redmine-3.3.1/config/locales/bg.yml
@@ -131,6 +131,7 @@ bg:
 circular_dependency: "Тази релация ще доведе до безкрайна зависимост"
 cant_link_an_issue_with_a_descendant: "Една задача не може да бъде свързвана към своя подзадача"
 earlier_than_minimum_start_date: "не може да бъде по-рано от %{date} поради предхождащи задачи"
+open_issue_with_closed_parent: "An open issue cannot be attached to a closed parent task"
 
   actionview_instancetag_blank_option: Изберете
 
Index: redmine-3.3.1/config/locales/bs.yml
===
--- redmine-3.3.1.orig/config/locales/bs.yml
+++ redmine-3.3.1/config/locales/bs.yml
@@ -141,6 +141,7 @@ bs:
 circular_dependency: "Ova relacija stvar cirkularnu zavisnost"
 cant_link_an_issue_with_a_descendant: "An issue can not be linked to one of its subtasks"
 earlier_than_minimum_start_date: "cannot be earlier than %{date} because of preceding issues"
+open_issue_with_closed_parent: "An open issue cannot be attached to a closed parent task"
 
   actionview_instancetag_blank_option: Molimo odaberite
 
Index: redmine-3.3.1/config/locales/ca.yml
===
--- redmine-3.3.1.orig/config/locales/ca.yml
+++ redmine-3.3.1/config/locales/ca.yml
@@ 

Bug#876885: fvwm: FvwmConsole can't be configured with X resources

[Jaimos Skriletz]

On Tue, Sep 26, 2017 at 11:40 AM, Danek Duvall  wrote:
> In my X resources file, I specify
>
> FvwmConsole*VT100*geometry: 40x4
>
> as suggested in the FvwmConsole(1) manpage, but this doesn't work; the console
> comes up with a different geometry entirely.
>
> I see that this is happening  because of fix-hardcoded-xterm.patch, which is
> there to conform to Debian policy
>
> 
> https://www.debian.org/doc/debian-policy/ch-customized-programs.html#s11.8.3
>
> which implies that the -name option isn't required by x-terminal-emulator, and
> so the patch removes its use.
>
> Unfortunately, that's the way that xterm lets you change the name under which 
> it
> figures out which resources to use.  At least, I don't know of a better way.
> And this has been working for decades under other operating systems.
>
> It's not clear to me what the right answer is, or even a good answer.  It 
> might
> involve tweaking the policy a bit (which also seems to exclude gnome-terminal 
> as
> a possible alternative, since its -t option is supposedly deprecated and may 
> be
> removed).  It may involve rewriting the manpage to at least be correct with 
> the
> way the code actually works on Debian.
>

I see the same thing. The -name option sets the terminal window's
Resource which is used for its configuration via ~/.Xresources. The
default is to not include this option, since the terminal
x-terminal-emulator points at is unknown. I see the issue you
mentioned, which is not all terminal emulators need to support the
-name option, but further different terminal emulators may not all
support the same resources in the ~/.Xresources file, so the resources
used may need tailoring to the terminal emulator being used.

I think it is best to keep it as it is, which is don't include -name
by default so the FvwmConsole's resource defaults to the terminal that
runs it. On my system this is xterm, so when configuring my resources
I just have to configure all my xterms via "xterm*VT100*geometry:
40x4" and it also affects FvwmConsole. The -name option is there if
the user wants to run FvwmConsole as it's own resource.

I see this as a bug in the man page to clarify this. Namely the
default is FvwmConsole's resource is that of the terminal
x-terminal-emulator points uses. Also clarify that the example
resources were written for xterm with the -name FvwmConsole flag.

> For now, my workaround is to simply run FvwmConsole with the -name option
> explictly added to the commandline.
>

I don't see this as a workaround, but how it should be handled in
Debian. If you want FvwmConsole's terminal to use a different resource
than your default terminal's resource for configuration, that is what
the -name feature is for. You can also use it in conjunction with the
-terminal option to ensure you are running a terminal that supports
it.

jaimos

Bug#876942: libpoppler68: poppler-based viewers show a blank page when they should not

[Rogério Brito]

Package: libpoppler68
Version: 0.57.0-2
Severity: important

Hi.

While using a program not yet packaged in Debian (namely, pdfsizeopt), I was
comparing the files before and after optimization and noticed a bug with any
poppler-based viewers and programs that I tried (I first discovered the bug
with diffpdf).

The first and second files (which I will send after I get the bug number
assigned by the BTS) should show exactly the same output, but with atril,
diffpdf, tools from poppler-utils etc., I that I get is a blank output for
the second file.

I tested both files with mupdf, gv (via ghostscript) and firefox's PDF
viewer and they all show the expected output, while poppler doesn't.

If any extra information is desired, please let me know and I will try my
best to provide it.


Thanks,

Rogério.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libpoppler68 depends on:
ii  libc62.24-17
ii  libfontconfig1   2.12.3-0.2
ii  libfreetype6 2.8-0.2
ii  libjpeg62-turbo  1:1.5.2-2
ii  liblcms2-2   2.8-4
ii  libnspr4 2:4.16-1
ii  libnss3  2:3.32-2
ii  libopenjp2-7 2.1.2-1.3
ii  libpng16-16  1.6.32-2
ii  libstdc++6   7.2.0-5
ii  libtiff5 4.0.8-5
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages libpoppler68 recommends:
ii  poppler-data  0.4.8-1

libpoppler68 suggests no packages.

-- no debconf information

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Bug#869416: [pkg-gnupg-maint] Bug#869416: pinentry-gtk2: fails to request passphrase when importing OpenPGP secret key with Seahorse

[NIIBE Yutaka]

intrigeri  wrote:
> Can you please take a look, and maybe attach an updated patch?

OK.

Attached is updated patch for gcr to fix this issue, by simply supplying
parent's environ untouched, intended to be put under debian/patches/.
While this patch fixes the particular issue, I think that more clean up
will be needed, perhaps.

The function g_spawn_async_with_pipes let inherit child process parent's
environ when envp=NULL.  By the change, _gcr_gnupg_process_run_async
does so for its envp, when GCR_GNUPG_PROCESS_RESPECT_LOCALE is
specified.

I put the patch in public domain, or it may be distributed
under the licence of LGPL-2.1+.

It is tested by seahorse and pinentry-gtk-2.
-- 
Index: gcr-3.20.0/gcr/gcr-gnupg-importer.c
===
--- gcr-3.20.0.orig/gcr/gcr-gnupg-importer.c
+++ gcr-3.20.0/gcr/gcr-gnupg-importer.c
@@ -330,7 +330,7 @@ _gcr_gnupg_importer_import_async (GcrImp
 	 _gcr_gnupg_importer_import_async);
 
 	_gcr_gnupg_process_run_async (self->pv->process, argv, NULL,
-	  GCR_GNUPG_PROCESS_WITH_STATUS,
+	  GCR_GNUPG_PROCESS_RESPECT_LOCALE|GCR_GNUPG_PROCESS_WITH_STATUS,
 	  cancellable, on_process_run_complete,
 	  g_object_ref (res));
 
Index: gcr-3.20.0/gcr/gcr-gnupg-process.c
===
--- gcr-3.20.0.orig/gcr/gcr-gnupg-process.c
+++ gcr-3.20.0/gcr/gcr-gnupg-process.c
@@ -1027,12 +1027,13 @@ _gcr_gnupg_process_run_async (GcrGnupgPr
 		!g_str_has_prefix (envp[i], "LOCALE="))
 			g_ptr_array_add (envs, (gpointer)envp[i]);
 	}
-	if (!(flags & GCR_GNUPG_PROCESS_RESPECT_LOCALE))
-		g_ptr_array_add (envs, (gpointer)"LOCALE=C");
-	g_ptr_array_add (envs, NULL);
-
+	if (i || !(flags & GCR_GNUPG_PROCESS_RESPECT_LOCALE)) {
+		if (!(flags & GCR_GNUPG_PROCESS_RESPECT_LOCALE))
+			g_ptr_array_add (envs, (gpointer)"LOCALE=C");
+		g_ptr_array_add (envs, NULL);
+	}
 	gchar *command = g_strjoinv (" ", (gchar**)args->pdata);
-	gchar *environ = g_strjoinv (", ", (gchar**)envs->pdata);
+	gchar *environ = envs->pdata?g_strjoinv (", ", (gchar**)envs->pdata):NULL;
 	g_debug ("running command: %s", command);
 	g_debug ("process environment: %s", environ);
 	g_free (command);

Bug#876941: apt-get: reports wrong time period to fetch repositories

[Marek Sebera]

Package: apt
Version: 1.4.7
Severity: normal

Dear Maintainer,

when I run 'apt-get update' right after the connection to LAN/WLAN is 
established, apt wrongly reports time period that it took to fetch repositories 
updates.
This does not occur when I run the same command a while after internet 
connection is available.

today, the apt reported this, after fetching the repositories in matter of 
seconds.

--snip--
Get:52 https://debian.ethz.ch/debian-security stretch/updates InRelease [62.9 
kB] 
Get:56 https://debian.ethz.ch/debian-security stretch/updates/main i386 
Packages [175 kB]   
  
Get:57 https://debian.ethz.ch/debian-security stretch/updates/main amd64 
Packages [174 kB] 
Fetched 1,243 kB in 213503982334601d 6h 55min 39s (0 B/s)   
  
Reading package lists... Done
--snip--

This might be partially connected to processes connected with ntp package (ie. 
#833136 or #461461), but I'm unable to tell.
I've included ntp install and configuration info at the end of system info.

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^postgresql-";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "test -x /usr/bin/apt-show-versions || exit 
0 ; apt-show-versions -i";
APT::Update::Post-Invoke-Success:: "[ ! -f /var/run/dbus/system_bus_socket ] || 
/usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt 
org.debian.apt.CacheChanged || true";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension 

Bug#876940: boinc: Depends on libwxgtk-webview3.0-0v5 which depends on webkit1

[Olly Betts]

Package: boinc
Version: 7.8.2+dfsg-3
Severity: serious
Tags: sid buster patch
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1
Control: block 790222 by -1

boinc-manager depends on libwxgtk-webview3.0-0v5 which
depends on libwxgtk-webview3.0-0v5 which depends on
libwebkitgtk-1.0-0. libwebkitgtk-1.0-0 is the old webkitgtk library
that suffers from many reported CVEs that have been fixed in
libwebkit2gtk-4.0-37 (src: webkit2gtk ).  The pkg-webkit maintainers
do not intend to release Debian 10 "Buster" with libwebkitgtk-1.0-0.

boinc-manager is the only reverse dependency of libwxgtk-webview3.0-0v5,
and apparently will soon be the only package blocking removal of webkit1.

I've attached a patch which changes boinc-manager to use wxHtmlWindow
instead of wxWebView.  I can build the package with this patch applied,
but I don't know boinc well enough to usefully test its functionality.
wxHtmlWindow is not a full-featured web browser, but hopefully this
gives a usable application - please test it out.

Cheers,
Olly
diff -Nru boinc-7.8.2+dfsg/debian/changelog boinc-7.8.2+dfsg/debian/changelog
--- boinc-7.8.2+dfsg/debian/changelog	2017-09-07 19:41:28.0 +1200
+++ boinc-7.8.2+dfsg/debian/changelog	2017-09-27 11:13:58.0 +1300
@@ -1,3 +1,10 @@
+boinc (7.8.2+dfsg-3exp1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to use wxHtmlWindow instead of wxWebView.
+
+ -- Olly Betts   Wed, 27 Sep 2017 11:13:58 +1300
+
 boinc (7.8.2+dfsg-3exp1) experimental; urgency=medium
 
   * Upload to experimental again, with the boinc-server-* packages.
diff -Nru boinc-7.8.2+dfsg/debian/control boinc-7.8.2+dfsg/debian/control
--- boinc-7.8.2+dfsg/debian/control	2017-09-07 19:41:28.0 +1200
+++ boinc-7.8.2+dfsg/debian/control	2017-09-27 11:13:58.0 +1300
@@ -26,7 +26,6 @@
libsqlite3-dev,
libssl-dev,
libtool,
-   libwxgtk-webview3.0-dev,
libwxgtk3.0-dev,
libxcb-util0-dev,
libxi-dev,
diff -Nru boinc-7.8.2+dfsg/debian/control.in boinc-7.8.2+dfsg/debian/control.in
--- boinc-7.8.2+dfsg/debian/control.in	2017-09-06 18:23:42.0 +1200
+++ boinc-7.8.2+dfsg/debian/control.in	2017-09-27 11:07:10.0 +1300
@@ -26,7 +26,6 @@
libsqlite3-dev,
libssl-dev,
libtool,
-   libwxgtk-webview3.0-dev,
libwxgtk3.0-dev,
libxcb-util0-dev,
libxi-dev,
diff -Nru boinc-7.8.2+dfsg/debian/patches/series boinc-7.8.2+dfsg/debian/patches/series
--- boinc-7.8.2+dfsg/debian/patches/series	2017-09-07 19:36:02.0 +1200
+++ boinc-7.8.2+dfsg/debian/patches/series	2017-09-27 11:13:58.0 +1300
@@ -30,3 +30,4 @@
 fix-underlinking.patch
 static_scientific_apps.patch
 0001-Fix-build-with-new-glibc-2.26.patch
+use-wxhtmlwindow-instead-of-wxwebview.patch
diff -Nru boinc-7.8.2+dfsg/debian/patches/use-wxhtmlwindow-instead-of-wxwebview.patch boinc-7.8.2+dfsg/debian/patches/use-wxhtmlwindow-instead-of-wxwebview.patch
--- boinc-7.8.2+dfsg/debian/patches/use-wxhtmlwindow-instead-of-wxwebview.patch	1970-01-01 12:00:00.0 +1200
+++ boinc-7.8.2+dfsg/debian/patches/use-wxhtmlwindow-instead-of-wxwebview.patch	2017-09-27 11:13:58.0 +1300
@@ -0,0 +1,104 @@
+Description: Use wxHtmlWindow instead of wxWebView
+Author: Olly Betts 
+Forwarded: no
+Last-Update: 2017-09-26
+
+--- a/clientgui/NoticeListCtrl.cpp
 b/clientgui/NoticeListCtrl.cpp
+@@ -50,8 +50,8 @@
+ BEGIN_EVENT_TABLE( CNoticeListCtrl, wxWindow )
+ 
+ @begin CNoticeListCtrl event table entries
+-EVT_WEBVIEW_NAVIGATING(ID_LIST_NOTIFICATIONSVIEW, CNoticeListCtrl::OnLinkClicked)
+-EVT_WEBVIEW_ERROR(ID_LIST_NOTIFICATIONSVIEW, CNoticeListCtrl::OnWebViewError)
++EVT_HTML_LINK_CLICKED(ID_LIST_NOTIFICATIONSVIEW, CNoticeListCtrl::OnLinkClicked)
++//EVT_WEBVIEW_ERROR(ID_LIST_NOTIFICATIONSVIEW, CNoticeListCtrl::OnWebViewError)
+ @end CNoticeListCtrl event table entries
+  
+ END_EVENT_TABLE()
+@@ -84,7 +84,7 @@
+ wxWindow::Create( parent, ID_LIST_NOTIFICATIONSVIEW, wxDefaultPosition, wxDefaultSize,
+ wxSUNKEN_BORDER | wxTAB_TRAVERSAL );
+ 
+-m_browser = wxWebView::New( this, ID_LIST_NOTIFICATIONSVIEW );
++m_browser = new wxHtmlWindow( this, ID_LIST_NOTIFICATIONSVIEW );
+ @end CNoticeListCtrl creation
+ 
+ wxBoxSizer *topsizer;
+@@ -238,7 +238,7 @@
+ m_noticesBody += wxT("");
+ // baseURL is not needed here (see comments above) and it
+ // must be an empty string for this to work under OS 10.12.4
+-m_browser->SetPage(m_noticesBody, wxEmptyString);
++m_browser->SetPage(m_noticesBody);
+ }
+ 
+ 
+@@ -248,22 +248,27 @@
+ }
+ 
+ 
+-void CNoticeListCtrl::OnLinkClicked( wxWebViewEvent& event ) {
+-if (event.GetURL().StartsWith(wxT("http://;)) || event.GetURL().StartsWith(wxT("https://;))) {
+-

Bug#876939: pgpool2: FTBFS on hurd-i386: rt_msghdr and RTM_* missing

[Aaron M. Ucko]

Source: pgpool2
Version: 3.6.6-2
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-h...@lists.debian.org

Builds of pgpool2 for hurd-i386 (admittedly not a release
architecture) have been failing lately:

  wd_if.c: In function 'read_interface_change_event':
  wd_if.c:466:14: error: dereferencing pointer to incomplete type 'struct 
rt_msghdr'
  wd_if.c:468:8: error: 'RTM_DELETE' undeclared (first use in this function); 
did you mean 'CMD_DELETE'?
  wd_if.c:470:8: error: 'RTM_ADD' undeclared (first use in this function)
  wd_if.c:475:8: error: 'RTM_DELADDR' undeclared (first use in this function); 
did you mean 'RTM_ADD'?
  wd_if.c:477:8: error: 'RTM_NEWADDR' undeclared (first use in this function); 
did you mean 'RTM_DELADDR'?

Could you please take a look and either accommodate the absence of
this struct (and the corresponding macros) or restrict the package's
architecture so that Hurd autobuilders don't bother trying to cover
it?  (Please note that kFreeBSD builds are unaffected.)

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#876918: juffed FTBFS: symbol differences

[Alf Gaida]

Guess what - we can read the FTBFS in reproducible builds too - but if
you really want to be helpful, we accept proudly bugs with attached
patches.

Cheers Alf

Bug#855173: ITP status?

[Hillel Lubman]

On Thu, 10 Aug 2017 06:37:58 -0400 Julian Andres Klode  wrote:

> I basically prepared the debian/copyright list of things to
> add / change, but did not actually update it yet.

Hi Julian.

Do you still plan to package it? It would really be nice to finally see 
keepassxc in Debian (unstable and testing).
Thanks!

Hillel Lubman.

Bug#876626: [Xastir] Bug#876626: Xastir loose TCP/IP data afer 12 hours of use

[David A Aitcheson]

Matthieu

Please clarify when the problem starts, is it after 12 HOURS or is it
after 12 DAYS? I rarely run my computer beyond 24 hours and probably
only run Xastir about 10 hours at a stretch so I may not be seeing the
issues you are seeing.

Once you convert to building from source for Xastir updating is simple,
just run a included "update" script that does a everything for you. I am
currently running Xastir V2.0.9 (8a3999d) Compiled (from source) on
Monday September 18 2017 at 17:17:00 EDT on my Laptop running Ubuntu
14.04.04-LTS

73
Dave
KB3EFS


On 09/26/2017 05:27 PM, MLHPUB wrote:
> Hello Ian,
>
> I don't know about latest snapshots.
> Maybe it does not occur with 2.0.9 version but I am not comfortable
> with upgrade outside of Debian repositiories...
>
> Regards,
>
> Matthieu
> F4ACU
>
> On Sun, 24 Sep 2017 10:55:13 +0100 "Iain R. Learmonth"
>  wrote:
>> Hi,
>>
>> On Sun, Sep 24, 2017 at 05:20:44AM -0400, David A Aitcheson wrote:
>> > > I usually use Xastir during all day, only with a TCP/IP to APRS-IS
>> > > connection at this moment (no radio link).
>> > > After more than 12 days uptime, Xastir loose many data from
>> APRS-IS :
>> > >
>> > > - ACK messages are not received
>> > > - positions reports (even visible on aprs.fi) are not displayed
>> > >
>> > > There is a kind of latency time on RX data from APRS-IS.
>> > >
>> > > It is necessary to quit and restart Xastir to retreive en normal
>> > > behavior.
>>
>> My question would be: does this occur in the latest Xastir snapshots?
>>
>> It's been a long time since there was a release of Xastir and I'm
>> sure the
>> Debian package is missing a number of fixes that have been applied
>> upstream.
>>
>> It's been on my todo list for a while to just update to a git
>> snapshot to
>> get some fixes into the Debian package, but I've not yet had time. If
>> someone can tell me this doesn't happen if you build from source then
>> that
>> would be an easy fix.
>>
>> Thanks,
>> Iain.
>>
>
>

Bug#876938: node-tap FTBFS: test failures

[Adrian Bunk]

Source: node-tap
Version: 10.7.2+ds1-3
Severity: serious

Some recent change in unstable makes node-tap FTBFS:

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

...
9281 passing (3m)
  7 pending
  4 failing

  1) test/test-buffer.js timeout-via-runner-ignore-sigterm.js bail=false 
buffer=true timeout!:
 Error: timeout!
  at Test.Base.timeout (lib/base.js:118:14)
  at Test.timeout (lib/test.js:208:28)
  at Test.timeout (lib/test.js:206:19)
  at TAP.Test.timeout (lib/test.js:206:19)
  at EventEmitter. (lib/tap.js:202:9)
  at emit (/usr/lib/nodejs/signal-exit/index.js:68:11)
  at process.listener (/usr/lib/nodejs/signal-exit/index.js:82:7)

  2) test/test-buffer.js test count !== plan:

  test count !== plan
  + expected - actual

  -89
  +1
  
  

  3) test/test.js timeout-via-runner.js bail=false buffer=false timeout!:
 Error: timeout!
  at Test.Base.timeout (lib/base.js:118:14)
  at Test.timeout (lib/test.js:208:28)
  at Test.timeout (lib/test.js:206:19)
  at TAP.Test.timeout (lib/test.js:206:19)
  at EventEmitter. (lib/tap.js:202:9)
  at emit (/usr/lib/nodejs/signal-exit/index.js:68:11)
  at process.listener (/usr/lib/nodejs/signal-exit/index.js:82:7)

  4) test/test.js test count !== plan:

  test count !== plan
  + expected - actual

  -91
  +1
  
  

debian/rules:38: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#876937: node-findit2: missing build dependency on node-mkdirp

[Adrian Bunk]

Source: node-findit2
Version: 2.2.3-1
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-findit2-2.2.3'
tap test/*.js
TAP version 13
module.js:471
throw err;
^

Error: Cannot find module 'mkdirp'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/build/1st/node-findit2-2.2.3/test/empty.js:1:76)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
# Subtest: test/empty.js
1..0 # no tests found
not ok 1 - test/empty.js # time=111.575ms
...
1..6
# failed 1 of 6 tests
# time=1853.815ms
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#876936: node-isexe: missing build dependency on node-mkdirp

[Adrian Bunk]

Source: node-isexe
Version: 2.0.0-2
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-isexe-2.0.0'
tap -R spec test/*.js --branches=100 --statements=100 --functions=100 
--lines=100;
Code coverage is disabled because some modules are missing

Error: Cannot find module 'mkdirp'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/build/1st/node-isexe-2.0.0/test/basic.js:10:14)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
test/basic.js

  1) test/basic.js

  0 passing (396.536ms)
  1 failing

  1) test/basic.js test/basic.js:
 test/basic.js
  

debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#876935: node-tape FTBFS: failed 2 of 41 tests

[Adrian Bunk]

Source: node-tape
Version: 4.6.3-1
Severity: serious

Some recent change in unstable makes node-tape FTBFS:

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

...
# Subtest: test/deep-equal-failure.js
# Subtest: deep equal failure
not ok 1 - Class constructor Parser cannot be invoked without 'new'
  ---
  stack: |
Test. (test/deep-equal-failure.js:10:18)
  at:
line: 10
column: 18
file: test/deep-equal-failure.js
function: Test.
  type: TypeError
  test: deep equal failure
  source: |
var parser = tapParser();
  ...

1..1
# failed 1 test
not ok 1 - deep equal failure # time=48.626ms

# Subtest: deep equal failure, depth 6, with option
not ok 1 - Class constructor Parser cannot be invoked without 'new'
  ---
  stack: |
Test. (test/deep-equal-failure.js:63:18)
  at:
line: 63
column: 18
file: test/deep-equal-failure.js
function: Test.
  type: TypeError
  test: 'deep equal failure, depth 6, with option'
  source: |
var parser = tapParser();
  ...

1..1
# failed 1 test
not ok 2 - deep equal failure, depth 6, with option # time=15.629ms

# Subtest: deep equal failure, depth 6, without option
not ok 1 - Class constructor Parser cannot be invoked without 'new'
  ---
  stack: |
Test. (test/deep-equal-failure.js:116:18)
  at:
line: 116
column: 18
file: test/deep-equal-failure.js
function: Test.
  type: TypeError
  test: 'deep equal failure, depth 6, without option'
  source: |
var parser = tapParser();
  ...

1..1
# failed 1 test
not ok 3 - deep equal failure, depth 6, without option # time=11.04ms

1..3
# failed 3 of 3 tests
# time=114.464ms
not ok 7 - test/deep-equal-failure.js # time=515.11ms
  ---
  timeout: 3
  file: test/deep-equal-failure.js
  command: /usr/bin/node
  args:
- test/deep-equal-failure.js
  cwd: /build/1st/node-tape-4.6.3
  exitCode: 1
  ...
...
# Subtest: test/stackTrace.js
# Subtest: preserves stack trace with newlines
1..3
not ok 1 - Class constructor Parser cannot be invoked without 'new'
  ---
  stack: |
Test. (test/stackTrace.js:12:30)
  at:
line: 12
column: 30
file: test/stackTrace.js
function: Test.
  type: TypeError
  test: preserves stack trace with newlines
  source: |
var parser = stream.pipe(tapParser());
  ...

# test count(1) != plan(3)
# failed 1 test
not ok 1 - preserves stack trace with newlines # time=153.453ms

1..1
# failed 1 test
# time=218.834ms
not ok 33 - test/stackTrace.js # time=1175.134ms
  ---
  timeout: 3
  file: test/stackTrace.js
  command: /usr/bin/node
  args:
- test/stackTrace.js
  cwd: /build/1st/node-tape-4.6.3
  exitCode: 1
  ...
...
1..41
# failed 2 of 41 tests
# skip: 5
# time=27406.068ms
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#876933: kcodecs FTBFS: test failures

[Adrian Bunk]

Source: kcodecs
Version: 5.37.0-2
Severity: serious

Some recent change in unstable makes kcodecs FTBFS:

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

...
dh_auto_test '--buildsystem=kf5' --parallel  
cd obj-x86_64-linux-gnu && make -j15 test ARGS\+=-j15
make[2]: Entering directory '/build/1st/kcodecs-5.37.0/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j15
Test project /build/1st/kcodecs-5.37.0/obj-x86_64-linux-gnu
Start 1: kcharsetstest
Start 2: kencodingprobertest
Start 3: base64benchmark
Start 4: rfc2047test
Start 5: codectest
Start 6: kemailaddresstest
1/6 Test #2: kencodingprobertest ..***Failed0.05 sec
* Start testing of KEncodingProberTest *
Config: Using QtTest library 5.9.1, Qt 5.9.1 (x86_64-little_endian-lp64 shared 
(dynamic) release build; by GCC 7.2.0)
PASS   : KEncodingProberTest::initTestCase()
PASS   : KEncodingProberTest::testReset()
WARNING: KEncodingProberTest::testProbe() testdata data could not be located!
   Loc: [kcodecs_5.37.0-2/autotests/kencodingprobertest.cpp(77)]
FAIL!  : KEncodingProberTest::testProbe() 'file.open(QIODevice::ReadOnly)' 
returned FALSE. ()
   Loc: [kcodecs_5.37.0-2/autotests/kencodingprobertest.cpp(80)]
PASS   : KEncodingProberTest::cleanupTestCase()
Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 14ms
* Finished testing of KEncodingProberTest *

2/6 Test #6: kemailaddresstest    Passed0.11 sec
3/6 Test #4: rfc2047test ..   Passed0.13 sec
4/6 Test #1: kcharsetstest    Passed0.16 sec
5/6 Test #5: codectest ***Exception: Other  0.12 sec
* Start testing of CodecTest *
Config: Using QtTest library 5.9.1, Qt 5.9.1 (x86_64-little_endian-lp64 shared 
(dynamic) release build; by GCC 7.2.0)
PASS   : CodecTest::initTestCase()
WARNING: CodecTest::testCodecs() testdata data could not be located!
   Loc: [kcodecs_5.37.0-2/autotests/codectest.cpp(42)]
QFATAL : CodecTest::testCodecs() ASSERT failure in QTest::fetchData(): "Test 
data requested, but no testdata available.", file qtestcase.cpp, line 1105
FAIL!  : CodecTest::testCodecs() Received a fatal error.
   Loc: [Unknown file(0)]
Totals: 1 passed, 1 failed, 0 skipped, 0 blacklisted, 5ms
* Finished testing of CodecTest *

6/6 Test #3: base64benchmark ..   Passed3.68 sec

67% tests passed, 2 tests failed out of 6

Total Test time (real) =   3.70 sec

The following tests FAILED:
  2 - kencodingprobertest (Failed)
  5 - codectest (OTHER_FAULT)
Errors while running CTest
Makefile:109: recipe for target 'test' failed
make[2]: *** [test] Error 8

Bug#876934: openorienteering-mapper FTBFS: test failures

[Adrian Bunk]

Source: openorienteering-mapper
Version: 0.7.0-1
Severity: serious

Some recent change in unstable makes openorienteering-mapper FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/openorienteering-mapper-0.7.0'
# The tests need a running X server, so use Xvfb to run the tests in automated
# build environments.
cd obj-x86_64-linux-gnu ; xvfb-run /usr/bin/ctest --force-new-ctest-process -j1 
--extra-verbose
UpdateCTestConfiguration  from 
:/build/1st/openorienteering-mapper-0.7.0/obj-x86_64-linux-gnu/DartConfiguration.tcl
UpdateCTestConfiguration  from 
:/build/1st/openorienteering-mapper-0.7.0/obj-x86_64-linux-gnu/DartConfiguration.tcl
Test project /build/1st/openorienteering-mapper-0.7.0/obj-x86_64-linux-gnu
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 1
  Start  1: tst_qglobal

1: Test command: /usr/bin/cmake "-P" "tst_qglobal-RUN.cmake"
1: Test timeout computed to be: 9.99988e+06
1: * Start testing of tst_QGlobal *
1: Config: Using QtTest library 5.9.1, Qt 5.9.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 7.2.0)
1: PASS   : tst_QGlobal::initTestCase()
1: PASS   : tst_QGlobal::testqOverload()
1: PASS   : tst_QGlobal::cleanupTestCase()
1: Totals: 3 passed, 0 failed, 0 skipped, 0 blacklisted, 1ms
1: * Finished testing of tst_QGlobal *
 1/17 Test  #1: tst_qglobal ..   Passed0.07 sec
test 2
  Start  2: encoding_t

2: Test command: /usr/bin/cmake "-P" "encoding_t-RUN.cmake"
2: Test timeout computed to be: 9.99988e+06
2: * Start testing of EncodingTest *
2: Config: Using QtTest library 5.9.1, Qt 5.9.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 7.2.0)
2: PASS   : EncodingTest::initTestCase()
2: PASS   : EncodingTest::testCodepageForLanguage(cs)
2: PASS   : EncodingTest::testCodepageForLanguage(cs_x)
2: PASS   : EncodingTest::testCodepageForLanguage(ru)
2: PASS   : EncodingTest::testCodepageForLanguage(ru_RU)
2: PASS   : EncodingTest::testCodepageForLanguage(de)
2: PASS   : EncodingTest::testCodepageForLanguage(??)
2: PASS   : EncodingTest::testCodecForName()
2: PASS   : EncodingTest::cleanupTestCase()
2: Totals: 9 passed, 0 failed, 0 skipped, 0 blacklisted, 3ms
2: * Finished testing of EncodingTest *
 2/17 Test  #2: encoding_t ...   Passed0.08 sec
test 3
  Start  3: georeferencing_t

3: Test command: /usr/bin/cmake "-P" "georeferencing_t-RUN.cmake"
3: Test timeout computed to be: 9.99988e+06
3: * Start testing of GeoreferencingTest *
3: Config: Using QtTest library 5.9.1, Qt 5.9.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 7.2.0)
3: PASS   : GeoreferencingTest::initTestCase()
3: PASS   : GeoreferencingTest::testEmptyProjectedCRS()
3: PASS   : GeoreferencingTest::testGridScaleFactor()
3: PASS   : GeoreferencingTest::testCRS(EPSG:4326)
3: PASS   : GeoreferencingTest::testCRS(UTM)
3: PASS   : GeoreferencingTest::testCRSTemplates()
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Koblenz UTM)
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Koblenz GK3)
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Pruem UTM)
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Pruem GK2)
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Landau UTM)
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Landau GK3)
3: PASS   : GeoreferencingTest::testProjection(EPSG 5514 ČÚZK Dolní Temenice)
3: PASS   : GeoreferencingTest::cleanupTestCase()
3: Totals: 14 passed, 0 failed, 0 skipped, 0 blacklisted, 4ms
3: * Finished testing of GeoreferencingTest *
 3/17 Test  #3: georeferencing_t .   Passed0.08 sec
test 4
  Start  4: locale_t

4: Test command: /usr/bin/cmake "-P" "locale_t-RUN.cmake"
4: Test timeout computed to be: 9.99988e+06
4: * Start testing of LocaleTest *
4: Config: Using QtTest library 5.9.1, Qt 5.9.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 7.2.0)
4: PASS   : LocaleTest::initTestCase()
4: XFAIL  : LocaleTest::testEsperantoQLocale() Cannot construct Esperanto 
QLocale from "eo" (issue #792).
4:Loc: [openorienteering-mapper_0.7.0-1/test/locale_t.cpp(46)]
4: XFAIL  : LocaleTest::testEsperantoQLocale() Cannot construct Esperanto 
QLocale from "eo_C".
4:Loc: [openorienteering-mapper_0.7.0-1/test/locale_t.cpp(49)]
4: XFAIL  : LocaleTest::testEsperantoQLocale() Cannot construct Esperanto 
QLocale for AnyScript, AnyCountry.
4:Loc: [openorienteering-mapper_0.7.0-1/test/locale_t.cpp(52)]
4: PASS   : 

Bug#876932: sphinx-issuetracker FTBFS with Sphinx 1.6: KeyError: 'refdomain'

[Adrian Bunk]

Source: sphinx-issuetracker
Version: 0.11-1
Severity: serious
Tags: buster sid

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

...
Running Sphinx v1.6.3
making output directory...
Generating grammar tables from /usr/share/sphinx/pycode/Grammar-py2.txt
loading pickled environment... not yet created
loading intersphinx inventory from /usr/share/doc/python2.7/html/objects.inv...
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 5 source files that are out of date
updating environment: 5 added, 0 changed, 0 removed
reading sources... [ 20%] changes

Exception occurred:
  File "/usr/lib/python2.7/dist-packages/docutils/nodes.py", line 567, in 
__getitem__
return self.attributes[key]
KeyError: 'refdomain'
The full traceback has been saved in /tmp/sphinx-err-60ez5O.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
debian/rules:8: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1

Bug#876931: psycopg2 FTBFS with Sphinx 1.6: Could not import extension dbapi_extension

[Adrian Bunk]

Source: psycopg2
Version: 2.7.3-1
Severity: serious

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

...
sphinx-build -b text -d _build/doctrees   . _build/text
Running Sphinx v1.6.3
making output directory...
Generating grammar tables from /usr/lib/python3.5/lib2to3/Grammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Skipping optional fixer: buffer
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Skipping optional fixer: idioms
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Skipping optional fixer: set_literal
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Skipping optional fixer: ws_comma
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/lib/python3.5/lib2to3/PatternGrammar.txt
Generating grammar tables from /usr/share/sphinx/pycode/Grammar-py3.txt
/usr/lib/python3/dist-packages/sphinx/util/compat.py:40: 
RemovedInSphinx17Warning: 

Bug#849400: debian-installer: LUKS on rootfs and boot

[Julian 1]

I am affected by this as well.

Googling shows shows people experimenting with workarounds - creating an
additional unencrypted /boot partition independent of the unencrypted EFI
partition.

This is overly complicated when the subsequent install workflow already
does the correct thing - in creating a /boot partition and
kernel/initrd/grub on the EFI parition.

One just needs to be able to hint that the EFI/fat32 parition will be used
for /boot, or else simply let the user 'continue' the installation, rather
than have both 'go-back' and 'continue' return to the same menu.



On Mon, 26 Dec 2016 18:02:28 +0100 Pali =?utf-8?q?Roh=C3=A1r?= <
pali.ro...@gmail.com> wrote:
> Package: debian-installer
> Severity: normal
>
> Dear Maintainer,
>
> Debian installer refuse me to install entire system (including /boot) on
> one encrypted partition. It shows me this red fatal error message:
>
>   [!!] Partition disks
>
>   Encryption configuration failure
>
>   You have selected the root file system to be stored on an encrypted
partition. This
>   feature requires a separate /boot partition on which the kernel and
initrd can be stored.
>
>   You should go back and setup a /boot partition.
>
> There are two buttons  and  but both buttons go
> back and refuse to continue...
>
> Then I tried to have separate /boot and separate / partitions, both
> LUKS encrypted. But Debian installer again refused to install such
> configuration. It show me another red fatal error message:
>
>   [!!] Partition disks
>
>   Encrypted configuration failure
>
>   You have selected the /boot file system to be stored on an encrypted
partition. This is
>   not possible because the boot loader would be unable to load the kernel
and initrd.
>   Continuing now would result in an installation that cannot be used.
>
>   You should go back and choose a non-encrypted partition for he /boot
file system.
>
> Again there are two buttons:  and  and again both go
> back and does not allow me to process changes and continue.
>
> And that error message is incorrect. Grub2 has already supports for
> accessing LUKS partitions. Just add GRUB_ENABLE_CRYPTODISK=y (or in
> older versions GRUB_CRYPTODISK_ENABLE=y) to /etc/default/grub.
>
> Debian installer should allow users to install system on fully
> encrypted disk (also with /boot) and should not force users to have
> always /boot unencrypted.
>
> At least expert users should be able to skip that error message and
> continue installation as error message is not truth anymore.
>
> --
> Pali Rohár
> pali.ro...@gmail.com

Bug#876930: golang-github-mattn-go-sqlite3 FTBFS: FAIL: TestSimpleError

[Adrian Bunk]

Source: golang-github-mattn-go-sqlite3
Version: 1.2.0+git20170802.105.6654e41~dfsg1-1
Severity: serious

Some recent change in unstable makes golang-github-mattn-go-sqlite3 FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-mattn-go-sqlite3.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-mattn-go-sqlite3.html

...
=== RUN   TestSimpleError
--- FAIL: TestSimpleError (0.00s)
error_test.go:19: wrong error code:SQL logic error
...
FAIL
exit status 1
FAILgithub.com/mattn/go-sqlite3 16.054s
dh_auto_test: go test -v -p 16 github.com/mattn/go-sqlite3 returned exit code 1
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 1

Bug#876929: packer FTBFS with Go 1.9

[Adrian Bunk]

Source: packer
Version: 1.0.4+dfsg-1
Severity: serious

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

...
=== RUN   TestAzureErrorSimpleShouldFormat
result never approved
approved: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/azure_error_response_test.TestAzureErrorSimpleShouldFormat.approved.txt
received: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/azure_error_response_test.TestAzureErrorSimpleShouldFormat.received.txt
--- FAIL: TestAzureErrorSimpleShouldFormat (0.00s)
azure_error_response_test.go:61: open 
packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/azure_error_response_test.TestAzureErrorSimpleShouldFormat.received.txt:
 no such file or directory
=== RUN   TestAzureErrorNestedShouldFormat
result never approved
approved: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/azure_error_response_test.TestAzureErrorNestedShouldFormat.approved.txt
received: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/azure_error_response_test.TestAzureErrorNestedShouldFormat.received.txt
--- FAIL: TestAzureErrorNestedShouldFormat (0.00s)
azure_error_response_test.go:74: open 
packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/azure_error_response_test.TestAzureErrorNestedShouldFormat.received.txt:
 no such file or directory
...
=== RUN   TestVirtualMachineDeployment03
result never approved
approved: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/template_factory_test.TestVirtualMachineDeployment03.approved.json
received: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/template_factory_test.TestVirtualMachineDeployment03.received.json
--- FAIL: TestVirtualMachineDeployment03 (0.01s)
template_factory_test.go:115: open 
packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/template_factory_test.TestVirtualMachineDeployment03.received.json:
 no such file or directory
=== RUN   TestVirtualMachineDeployment04
result never approved
approved: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/template_factory_test.TestVirtualMachineDeployment04.approved.json
received: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/template_factory_test.TestVirtualMachineDeployment04.received.json
--- FAIL: TestVirtualMachineDeployment04 (0.00s)
template_factory_test.go:145: open 
packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/template_factory_test.TestVirtualMachineDeployment04.received.json:
 no such file or directory
=== RUN   TestVirtualMachineDeployment05
result never approved
approved: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/template_factory_test.TestVirtualMachineDeployment05.approved.json
received: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/template_factory_test.TestVirtualMachineDeployment05.received.json
--- FAIL: TestVirtualMachineDeployment05 (0.01s)
template_factory_test.go:177: open 
packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/template_factory_test.TestVirtualMachineDeployment05.received.json:
 no such file or directory
=== RUN   TestVirtualMachineDeployment06
result never approved
approved: 
/build/1st/packer-1.0.4+dfsg/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/packer_1.0.4+dfsg-1/obj-x86_64-linux-gnu/src/github.com/hashicorp/packer/builder/azure/arm/template_factory_test.TestVirtualMachineDeployment06.approved.json
received: 

Bug#876928: qbittorrent: Please have qbittorrent-dbgsym file instead of qbittorrent-dbg

[shirish शिरीष]

Package: qbittorrent
Version: 3.3.15-1
Severity: normal

Dear Maintainer,

It would be nice if you could move from qbittorrent-dbg to
qbittorrent-dbgsym. From my limited experience of debugging, the
experience has been dbgsyms give much more info. to maintainers as
well as upstream which in-turn helps people a more bug-free program.

FWIW, for a long time I do run qbittorrent under gdb in case it runs
into any problems.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (1, 'experimental-debug'), (1, 'experimental'), (1,
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages qbittorrent depends on:
ii  geoip-database 20170912-1
ii  libboost-system1.62.0  1.62.0+dfsg-4+b1
ii  libc6  2.24-17
ii  libgcc11:7.2.0-5
ii  libqt5core5a   5.9.1+dfsg-9
ii  libqt5dbus55.9.1+dfsg-9
ii  libqt5gui5 5.9.1+dfsg-9
ii  libqt5network5 5.9.1+dfsg-9
ii  libqt5widgets5 5.9.1+dfsg-9
ii  libqt5xml5 5.9.1+dfsg-9
ii  libstdc++6 7.2.0-5
ii  libtorrent-rasterbar9  1.1.4-1
ii  python 2.7.13-2
ii  zlib1g 1:1.2.8.dfsg-5

qbittorrent recommends no packages.

Versions of packages qbittorrent suggests:
ii  qbittorrent-dbg  3.3.15-1

-- no debconf information


-- 
  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#876927: moonshot-ui FTBFS with vala 0.36

[Adrian Bunk]

Source: moonshot-ui
Version: 0.7.2-1
Severity: serious
Tags: buster sid

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

...
CDPATH="${ZSH_VERSION+.}:" && cd . && /usr/bin/valac --pkg gdk-2.0 --pkg 
gtk+-2.0 -g config.vapi --vapidir=./vapi --pkg gio-2.0   --pkg 
moonshot-gnome-keyring --define=GNOME_KEYRING   --pkg gio-2.0 
--define=IPC_GDBUS --define=IPC_DBUS --define=GIO_VAPI_USES_ARRAYS --pkg 
gee-0.8   -C src/moonshot-identity-manager-app.vala 
src/moonshot-identity-management-view.vala 
src/moonshot-local-flat-file-store.vala src/moonshot-keyring-store.vala 
src/moonshot-idcard-store.vala src/moonshot-id.vala 
src/moonshot-add-dialog.vala src/moonshot-idcard-widget.vala 
src/moonshot-custom-vbox.vala src/moonshot-identities-manager.vala 
src/moonshot-identity-request.vala src/moonshot-server.vala 
src/moonshot-password-dialog.vala src/moonshot-provisioning-common.vala 
src/moonshot-utils.vala
src/moonshot-add-dialog.vala:36.5-36.66: warning: the modifier `static' is not 
applicable to constants
static const string displayname_labeltext = _("Display Name");
^^
src/moonshot-add-dialog.vala:37.5-37.55: warning: the modifier `static' is not 
applicable to constants
static const string issuer_labeltext = _("Issuer");
^^^
src/moonshot-add-dialog.vala:38.5-38.59: warning: the modifier `static' is not 
applicable to constants
static const string username_labeltext = _("Username");
^^^
src/moonshot-add-dialog.vala:39.5-39.59: warning: the modifier `static' is not 
applicable to constants
static const string password_labeltext = _("Password");
^^^
gtk+-2.0.vapi:5871.40-5871.42: warning: Gtk is deprecated. Use gtk+-3.0
src/moonshot-idcard-widget.vala:95.21-95.23: warning: Gdk is deprecated. Use 
gdk-3.0
src/moonshot-utils.vala:73.26-73.28: warning: Gtk is deprecated. Use gtk+-3.0
src/moonshot-utils.vala:74.50-74.52: warning: Gtk is deprecated. Use gtk+-3.0
src/moonshot-idcard-widget.vala:142.21-142.23: warning: Gtk is deprecated. Use 
gtk+-3.0
src/moonshot-identity-management-view.vala:627.32-627.34: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:628.39-628.41: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:629.39-629.41: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:630.39-630.41: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:637.26-637.28: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:488.41-488.43: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:779.44-779.46: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:753.34-753.36: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:712.9-712.11: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-utils.vala:39.5-39.7: warning: Gtk is deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:801.79-801.81: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:808.82-808.84: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:216.12-216.14: warning: Gdk is 
deprecated. Use gdk-3.0
src/moonshot-identity-management-view.vala:180.28-180.30: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:940.31-940.33: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:357.40-357.43: error: Argument 1: 
Cannot pass value to reference or output parameter
listmodel->remove (iter);
   
src/moonshot-identity-management-view.vala:393.30-393.32: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:394.45-394.47: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:395.45-395.47: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:396.45-396.47: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:402.30-402.32: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:403.45-403.47: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:404.45-404.47: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:405.45-405.47: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:411.26-411.28: warning: Gtk is 
deprecated. Use gtk+-3.0
src/moonshot-identity-management-view.vala:412.45-412.47: warning: Gtk is 
deprecated. Use gtk+-3.0

Bug#876924: golang-github-facebookgo-ensure FTBFS with Go 1.9

[Adrian Bunk]

Source: golang-github-facebookgo-ensure
Version: 0.0~git20160127.0.b4ab57d-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-facebookgo-ensure.html

...
--- FAIL: TestExtras (0.00s)
ensure.go:65: 
golang-github-facebookgo-ensure_0.0~git20160127.0.b4ab57d-1/obj-x86_64-linux-gnu/src/github.com/facebookgo/ensure/common_test.go:29
 (*capture).Equal

golang-github-facebookgo-ensure_0.0~git20160127.0.b4ab57d-1/obj-x86_64-linux-gnu/src/github.com/facebookgo/ensure/ensure_test.go:42
 TestExtras
expected these to be equal:
ACTUAL:
(string) (len=194) "ensure_test.go:32: unexpected error: 
foo\n(map[string]int) (len=1) {\n (string) (len=6) \"answer\": (int) 
42\n}\n(string) (len=3) \"baz\"\n(int) 43\n(float64) 44.45\n(ensure_test.typ) 
{\n Answer: (int) 46\n}"

EXPECTED:
(string) (len=194) "ensure_test.go:41: unexpected error: 
foo\n(map[string]int) (len=1) {\n (string) (len=6) \"answer\": (int) 
42\n}\n(string) (len=3) \"baz\"\n(int) 43\n(float64) 44.45\n(ensure_test.typ) 
{\n Answer: (int) 46\n}"

Bug#876926: pbuilder FTBFS: 'msgid' and 'msgstr' entries do not both end with '\n'

[Adrian Bunk]

Source: pbuilder
Version: 0.228.8
Severity: serious

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

...
make -C Documentation all
make[2]: Entering directory '/build/1st/pbuilder-0.228.8/Documentation'
xsltproc pbuilder-doc.xsl pbuilder-doc.xml > pbuilder-doc.html.tmp
po4a-updatepo -f docbook -m pbuilder-doc.xml -p pbuilder-doc.ja.po 
po4a-updatepo -f docbook -m pbuilder-doc.xml -p pbuilder-doc.fr.po 
po4a-updatepo -f docbook -m pbuilder-doc.xml -p pbuilder-doc.de.po 
mv pbuilder-doc.html.tmp pbuilder-doc.html

 done.
po4a-translate -f docbook -m pbuilder-doc.xml -p pbuilder-doc.fr.po -l 
pbuilder-doc.fr.xml -k 1
.
 done.
...
 done.
po4a-translate -f docbook -m pbuilder-doc.xml -p pbuilder-doc.de.po -l 
pbuilder-doc.de.xml -k 1
po4a-translate -f docbook -m pbuilder-doc.xml -p pbuilder-doc.ja.po -l 
pbuilder-doc.ja.xml -k 1
Invalid po file pbuilder-doc.ja.po:
pbuilder-doc.ja.po:1366: 'msgid' and 'msgstr' entries do not both end with '\n'
msgfmt: found 1 fatal error

Makefile:23: recipe for target 'pbuilder-doc.ja.xml' failed
make[2]: *** [pbuilder-doc.ja.xml] Error 1

Bug#876925: golang-github-gopherjs-gopherjs FTBFS with Go 1.9

[Adrian Bunk]

Source: golang-github-gopherjs-gopherjs
Version: 0.0~git20170702.0.2b1d432-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-gopherjs-gopherjs.html

...
   dh_auto_build -O--buildsystem=golang
go install 
-gcflags=\"-trimpath=/build/1st/golang-github-gopherjs-gopherjs-0.0\~git20170702.0.2b1d432/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-github-gopherjs-gopherjs-0.0\~git20170702.0.2b1d432/obj-x86_64-linux-gnu/src\"
 -v -p 15 github.com/gopherjs/gopherjs github.com/gopherjs/gopherjs/build 
github.com/gopherjs/gopherjs/compiler 
github.com/gopherjs/gopherjs/compiler/analysis 
github.com/gopherjs/gopherjs/compiler/astutil 
github.com/gopherjs/gopherjs/compiler/filter 
github.com/gopherjs/gopherjs/compiler/natives 
github.com/gopherjs/gopherjs/compiler/natives/src/sync 
github.com/gopherjs/gopherjs/compiler/natives/src/text/template 
github.com/gopherjs/gopherjs/compiler/prelude 
github.com/gopherjs/gopherjs/compiler/typesutil github.com/gopherjs/gopherjs/js 
github.com/gopherjs/gopherjs/nosync github.com/gopherjs/gopherjs/tests 
github.com/gopherjs/gopherjs/tests/main 
github.com/gopherjs/gopherjs/tests/otherpkg 
github.com/gopherjs/gopherjs/third_party/importer
golang.org/x/sys/unix
github.com/gopherjs/gopherjs/compiler/astutil
github.com/gopherjs/gopherjs/compiler/typesutil
github.com/gopherjs/gopherjs/compiler/prelude
github.com/gopherjs/gopherjs/third_party/importer
github.com/neelance/astrewrite
golang.org/x/tools/go/types/typeutil
github.com/neelance/sourcemap
github.com/kisielk/gotool
github.com/spf13/pflag
golang.org/x/crypto/ssh/terminal
github.com/gopherjs/gopherjs/compiler/natives/src/sync
github.com/gopherjs/gopherjs/compiler/natives/src/text/template
github.com/gopherjs/gopherjs/compiler/natives
github.com/gopherjs/gopherjs/js
github.com/gopherjs/gopherjs/nosync
github.com/gopherjs/gopherjs/tests
github.com/gopherjs/gopherjs/tests/main
github.com/gopherjs/gopherjs/tests/otherpkg
github.com/gopherjs/gopherjs/compiler/analysis
github.com/gopherjs/gopherjs/compiler/filter
github.com/gopherjs/gopherjs/compiler
# github.com/gopherjs/gopherjs/compiler
src/github.com/gopherjs/gopherjs/compiler/compiler.go:20:9: undefined: 
___GOPHERJS_REQUIRES_GO_VERSION_1_8___
github.com/fsnotify/fsnotify
github.com/spf13/cobra
dh_auto_build: go install 
-gcflags=\"-trimpath=/build/1st/golang-github-gopherjs-gopherjs-0.0\~git20170702.0.2b1d432/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-github-gopherjs-gopherjs-0.0\~git20170702.0.2b1d432/obj-x86_64-linux-gnu/src\"
 -v -p 15 github.com/gopherjs/gopherjs github.com/gopherjs/gopherjs/build 
github.com/gopherjs/gopherjs/compiler 
github.com/gopherjs/gopherjs/compiler/analysis 
github.com/gopherjs/gopherjs/compiler/astutil 
github.com/gopherjs/gopherjs/compiler/filter 
github.com/gopherjs/gopherjs/compiler/natives 
github.com/gopherjs/gopherjs/compiler/natives/src/sync 
github.com/gopherjs/gopherjs/compiler/natives/src/text/template 
github.com/gopherjs/gopherjs/compiler/prelude 
github.com/gopherjs/gopherjs/compiler/typesutil github.com/gopherjs/gopherjs/js 
github.com/gopherjs/gopherjs/nosync github.com/gopherjs/gopherjs/tests 
github.com/gopherjs/gopherjs/tests/main 
github.com/gopherjs/gopherjs/tests/otherpkg 
github.com/gopherjs/gopherjs/third_party
 /importer returned exit code 2
debian/rules:4: recipe for target 'binary' failed
make: *** [binary] Error 2

Bug#876923: golang-check.v1 FTBFS with Go 1.9

[Adrian Bunk]

Source: golang-check.v1
Version: 0.0+git20161208.0.20d25e2-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-check.v1.html

...
   dh_auto_test -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -v -p 1 gopkg.in/check.v1
=== RUN   Test

--
FAIL: 
golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/fixture_test.go:447:
 FixtureS.TestFixtureLogging

golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/fixture_test.go:451:
...open 
golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/fixture_test.go:
 no such file or directory
... value string = "" +
... "\n" +
... 
"--\n" +
... "FAIL: 
golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/fixture_test.go:436:
 FixtureLogHelper.Test\n" +
... "\n" +
... "1\n" +
... "2\n" +
... "3\n" +
... "4\n" +
... "5\n"
... regex string = "" +
... "\n" +
... "---+\n" +
... "FAIL: fixture_test\\.go:[0-9]+: FixtureLogHelper\\.Test\n" +
... "\n" +
... "1\n" +
... "2\n" +
... "3\n" +
... "4\n" +
... "5\n"


--
FAIL: 
golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/fixture_test.go:129:
 FixtureS.TestPanicOnSetUpSuite

golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/fixture_test.go:149:
...open 
golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/fixture_test.go:
 no such file or directory
... value string = "" +
... "\n" +
... 
"--\n" +
... "PANIC: 
golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/check_test.go:120:
 FixtureHelper.SetUpSuite\n" +
... "\n" +
... "... Panic: SetUpSuite (PC=0x4588AA)\n" +
... "\n" +
... "/usr/lib/go-1.9/src/runtime/panic.go:491\n" +
... "  in gopanic\n" +
... "/usr/lib/go-1.9/src/reflect/value.go:302\n" +
... "  in Value.Call\n" +
... "/usr/lib/go-1.9/src/runtime/asm_amd64.s:2337\n" +
... "  in goexit\n"
... regex string = "" +
... "^\n" +
... "-+\n" +
... "PANIC: check_test\\.go:[0-9]+: FixtureHelper.SetUpSuite\n" +
... "\n" +
... "\\.\\.\\. Panic: SetUpSuite \\(PC=[xA-F0-9]+\\)\n" +
... "\n" +
... ".+:[0-9]+\n" +
... "  in (go)?panic\n" +
... ".*check_test.go:[0-9]+\n" +
... "  in FixtureHelper.trace\n" +
... ".*check_test.go:[0-9]+\n" +
... "  in FixtureHelper.SetUpSuite\n" +
... "(.|\n" +
... ")*$"


--
FAIL: 
golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/fixture_test.go:68:
 FixtureS.TestPanicOnSetUpTest

golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/fixture_test.go:95:
...open 
golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/fixture_test.go:
 no such file or directory
... value string = "" +
... "\n" +
... 
"--\n" +
... "PANIC: 
golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/check_test.go:128:
 FixtureHelper.SetUpTest\n" +
... "\n" +
... "... Panic: SetUpTest (PC=0x4588AA)\n" +
... "\n" +
... "/usr/lib/go-1.9/src/runtime/panic.go:491\n" +
... "  in gopanic\n" +
... "/usr/lib/go-1.9/src/reflect/value.go:302\n" +
... "  in Value.Call\n" +
... "/usr/lib/go-1.9/src/runtime/asm_amd64.s:2337\n" +
... "  in goexit\n" +
... "\n" +
... 
"--\n" +
... "PANIC: 
golang-check.v1_0.0+git20161208.0.20d25e2-1/obj-x86_64-linux-gnu/src/gopkg.in/check.v1/check_test.go:136:
 FixtureHelper.Test1\n" +
... "\n" +
... "... Panic: Fixture has panicked (see related PANIC)\n"
... regex string = "" +
... "^\n" +
... "-+\n" +
... "PANIC: check_test\\.go:[0-9]+: FixtureHelper\\.SetUpTest\n" +
... "\n" +
... "\\.\\.\\. Panic: SetUpTest \\(PC=[xA-F0-9]+\\)\n" +
... "\n" +
... ".+:[0-9]+\n" +
... "  in (go)?panic\n" +
... ".*check_test.go:[0-9]+\n" +
... "  in FixtureHelper.trace\n" +
... ".*check_test.go:[0-9]+\n" +
... "  in FixtureHelper.SetUpTest\n" +
... "(.|\n" +
... ")*\n" +
... "-+\n" +
... "PANIC: check_test\\.go:[0-9]+: FixtureHelper\\.Test1\n" +
... "\n" +
... "\\.\\.\\. Panic: Fixture has panicked \\(see related PANIC\\)\n" +
... "$"

Bug#876922: golang-github-approvals-go-approval-tests FTBFS with Go 1.9

[Adrian Bunk]

Source: golang-github-approvals-go-approval-tests
Version: 0.0~git20170712.0.c1e747e-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-approvals-go-approval-tests.html

...
   dh_auto_test -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -v -p 16 
github.com/approvals/go-approval-tests 
github.com/approvals/go-approval-tests/reporters 
github.com/approvals/go-approval-tests/utils
=== RUN   TestVerifyStringApproval
--- FAIL: TestVerifyStringApproval (0.00s)
=== RUN   TestReporterFromSetup
--- FAIL: TestReporterFromSetup (0.00s)
=== RUN   TestVerifyXMLStruct
--- FAIL: TestVerifyXMLStruct (0.00s)
=== RUN   TestVerifyBadXMLStruct
--- FAIL: TestVerifyBadXMLStruct (0.00s)
=== RUN   TestVerifyXMLBytes
--- FAIL: TestVerifyXMLBytes (0.00s)
=== RUN   TestVerifyBadXMLBytes
--- FAIL: TestVerifyBadXMLBytes (0.00s)
=== RUN   TestVerifyJSONStruct
--- FAIL: TestVerifyJSONStruct (0.00s)
=== RUN   TestVerifyJSONBytes
--- FAIL: TestVerifyJSONBytes (0.00s)
=== RUN   TestVerifyBadJSONBytes
--- FAIL: TestVerifyBadJSONBytes (0.00s)
=== RUN   TestVerifyMap
--- FAIL: TestVerifyMap (0.00s)
=== RUN   TestVerifyMapBadMap
--- FAIL: TestVerifyMapBadMap (0.00s)
=== RUN   TestVerifyMapEmptyMap
--- FAIL: TestVerifyMapEmptyMap (0.00s)
=== RUN   TestVerifyArray
--- FAIL: TestVerifyArray (0.00s)
=== RUN   TestVerifyArrayBadArray
--- FAIL: TestVerifyArrayBadArray (0.00s)
=== RUN   TestVerifyArrayEmptyArray
--- FAIL: TestVerifyArrayEmptyArray (0.00s)
=== RUN   TestVerifyArrayTransformation
--- FAIL: TestVerifyArrayTransformation (0.00s)
=== RUN   TestVerifyAllCombinationsFor1
--- FAIL: TestVerifyAllCombinationsFor1 (0.00s)
=== RUN   TestVerifyAllCombinationsForSkipped
--- FAIL: TestVerifyAllCombinationsForSkipped (0.00s)
=== RUN   TestVerifyAllCombinationsFor2
--- FAIL: TestVerifyAllCombinationsFor2 (0.00s)
=== RUN   TestVerifyAllCombinationsFor9
--- FAIL: TestVerifyAllCombinationsFor9 (0.00s)
=== RUN   Test00
--- PASS: Test00 (0.00s)
=== RUN   TestUseReporter
--- PASS: TestUseReporter (0.00s)
=== RUN   TestFrontLoadedReporter
--- PASS: TestFrontLoadedReporter (0.00s)
FAIL
FAILgithub.com/approvals/go-approval-tests  0.010s
=== RUN   TestFirstWorkingReporter
--- PASS: TestFirstWorkingReporter (0.00s)
=== RUN   TestMultiReporter
--- PASS: TestMultiReporter (0.00s)
=== RUN   TestMultiReporterWithNoWorkingReporters
--- PASS: TestMultiReporterWithNoWorkingReporters (0.00s)
=== RUN   TestCIReporter
--- PASS: TestCIReporter (0.00s)
PASS
ok  github.com/approvals/go-approval-tests/reporters0.008s
?   github.com/approvals/go-approval-tests/utils[no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -v -p 16 
github.com/approvals/go-approval-tests 
github.com/approvals/go-approval-tests/reporters 
github.com/approvals/go-approval-tests/utils returned exit code 1
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 1

Bug#876921: python-pint FTBFS with python-numpy 1.13.1: test failures

[Adrian Bunk]

Source: python-pint
Version: 0.8.1-1
Severity: serious

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose 
S.S./usr/lib/python2.7/unittest/case.py:340:
 RuntimeWarning: TestResult has no addExpectedFailure method, reporting as 
passes
  RuntimeWarning)
...S...SSSS.S...E.E...E.../build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/test_quantity.py:287:
 RuntimeWarning: to_compact applied to non numerical types has an undefined 
behavior.
  self.assertQuantityAlmostIdentical(q.to_compact(unit=unit),
...F..F..
==
ERROR: test_inplace_exponentiation 
(pint.testsuite.test_quantity.TestOffsetUnitMath) [with input = ((10, u'degC'), 
(2, u'')); expected_output = [u'error', (80173.9224999, u'kelvin**2')]]
--
Traceback (most recent call last):
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/parameterized.py",
 line 116, in new_method
return method(self, *param_values)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/parameterized.py",
 line 137, in newfunc
return func(*arg, **kwargs)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/test_quantity.py",
 line 1165, in test_inplace_exponentiation
self.assertEqual(op.ipow(in1_cp, in2).units, expected.units)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/quantity.py", 
line 961, in __ipow__
self._magnitude **= _to_magnitude(other, self.force_ndarray)
TypeError: unsupported operand type(s) for ** or pow(): 'numpy.ndarray' and 
'Quantity'

==
ERROR: test_inplace_exponentiation 
(pint.testsuite.test_quantity.TestOffsetUnitMath) [with input = ((10, 
u'kelvin'), (2, u'')); expected_output = [(100.0, u'kelvin**2'), (100.0, 
u'kelvin**2')]]
--
Traceback (most recent call last):
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/parameterized.py",
 line 116, in new_method
return method(self, *param_values)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/parameterized.py",
 line 137, in newfunc
return func(*arg, **kwargs)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/test_quantity.py",
 line 1165, in test_inplace_exponentiation
self.assertEqual(op.ipow(in1_cp, in2).units, expected.units)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/quantity.py", 
line 961, in __ipow__
self._magnitude **= _to_magnitude(other, self.force_ndarray)
TypeError: unsupported operand type(s) for ** or pow(): 'numpy.ndarray' and 
'Quantity'

==
ERROR: test_inplace_exponentiation 
(pint.testsuite.test_quantity.TestOffsetUnitMath) [with input = ((10, u'degC'), 
(500.0, u'millikelvin/kelvin')); expected_output = [u'error', 
(16.827061537891872, u'kelvin**0.5')]]
--
Traceback (most recent call last):
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/parameterized.py",
 line 116, in new_method
return method(self, *param_values)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/parameterized.py",
 line 137, in newfunc
return func(*arg, **kwargs)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/test_quantity.py",
 line 1165, in test_inplace_exponentiation
self.assertEqual(op.ipow(in1_cp, in2).units, expected.units)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/quantity.py", 
line 961, in __ipow__
self._magnitude **= _to_magnitude(other, self.force_ndarray)
TypeError: unsupported operand type(s) for ** or pow(): 'numpy.ndarray' and 
'Quantity'

Bug#876920: brian FTBFS: weave has been removed from scipy

[Adrian Bunk]

Source: brian
Version: 1.4.3-1
Severity: serious
Tags: buster sid

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

...
I: Running Brian unittests using python2.7
Failure: ImportError (cannot import name weave) ... ERROR

==
ERROR: Failure: ImportError (cannot import name weave)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 407, in 
loadTestsFromName
module = resolve_name(addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 312, in 
resolve_name
module = __import__('.'.join(parts_copy))
  File 
"/build/1st/brian-1.4.3/debian/tmp/usr/lib/python2.7/dist-packages/brian/__init__.py",
 line 51, in 
from connections import *
  File 
"/build/1st/brian-1.4.3/debian/tmp/usr/lib/python2.7/dist-packages/brian/connections/__init__.py",
 line 1, in 
from sparsematrix import *
  File 
"/build/1st/brian-1.4.3/debian/tmp/usr/lib/python2.7/dist-packages/brian/connections/sparsematrix.py",
 line 1, in 
from base import *
  File 
"/build/1st/brian-1.4.3/debian/tmp/usr/lib/python2.7/dist-packages/brian/connections/base.py",
 line 14, in 
from scipy import weave
ImportError: cannot import name weave

--
Ran 1 test in 0.001s

FAILED (errors=1)
debian/rules:37: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1



python-scipy (0.19.1-1) unstable; urgency=medium

  * New upstream release
  * weave has been removed, drop its patch blitz++.patch
...
 -- Julian Taylor   Wed, 06 Sep 2017 18:07:38 
+0200

Bug#876919: ipmitool sdr output shows incorrect values for present and remoteon fields

[Howard Finer - Westford]

Package: ipmitool
Version: 1.8.14
Severity: normal

Dear Maintainer,

I am using ipmitool version 1.8.14 on Debian Jessie.  (The same issue exists in 
1.8.18-3 which i built myself, but does not exist in version 1.8.11 from wheezy)
We use the 'ipmitool sdr option' for troubleshooting and diagnostics.

The proper output, which can also be sen from the BMC, shows something like the 
following:
  PSB/PRESENT  | 0x02  | ok
  PSA/PRESENT  | 0x01  | ok
  PSB/REMOTEON | 0x02  | ok
  PSA/REMOTEON | 0x01  | ok
  48V_PWRGD| 0x02  | ok
  33_PWRGD | 0x02  | ok
  5_PWRGD  | 0x02  | ok
  FAN2/PRESENT | 0x02  | ok
  FAN1/PRESENT | 0x02  | ok
  FAN3/PRESENT | 0x02  | ok
  FAN4/PRESENT | 0x02  | ok
  DSP1/PRESENT | 0x01  | ok
  DSP2/PRESENT | 0x01  | ok
  DSP3/PRESENT | 0x01  | ok
  DSP4/PRESENT | 0x01  | ok


the incorrect output which we are seeing shows:
  PSB/PRESENT  | 0x00  | ok
  PSA/PRESENT  | 0x00  | ok
  PSB/REMOTEON | 0x00  | ok
  PSA/REMOTEON | 0x00  | ok
  48V_PWRGD| 0x00  | ok
  33_PWRGD | 0x00  | ok
  5_PWRGD  | 0x00  | ok
  FAN2/PRESENT | 0x00  | ok
  FAN1/PRESENT | 0x00  | ok
  FAN3/PRESENT | 0x00  | ok
  FAN4/PRESENT | 0x00  | ok
  DSP1/PRESENT | 0x00  | ok
  DSP2/PRESENT | 0x00  | ok
  DSP3/PRESENT | 0x00  | ok
  DSP4/PRESENT | 0x00  | ok

we also see a problem with the output of the PSB/INPUT_OK and PSB/OUTPUT_OK 
fields
< PSB/INPUT_OK | 0x02  | ok
< PSB/OUTPUT_OK| 0x02  | ok
---
> PSB/INPUT_OK | 0x00  | ok
> PSB/OUTPUT_OK| 0x00  | ok

the BMC's version of ipmitool shows what the 'correct' versions are above.


(note: we were looking to update to at least 1.8.15 for the fix that prevents 
output of the fru ID 0 info twice)




-- System Information:
Debian Release: 8.7
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Bug#876912: [Pkg-lirc-maint] Bug#876912: lirc: nodaemon option

[Alec Leamas]

Hi,

On 26/09/17 23:02, Arno None wrote:

Source: lirc
Version: 0.10.0
Severity: normal

Dear Maintainer,

To start the lirc service lircd with the option 'nodaemon' in 
/etc/lirc/lirc_options.conf I had to remove the option --nodaemon from 
/etc/systemd/system/multi-user.target.wants/lircd.service

Why is this option set in a file that starts a service (daemon)?

When this option is removed the 'nodaemon' option in 
/etc/lirc/lirc_options.conf has to be set to 'True' to start lircd

Shouldn't that be 'False'?


First of all, the lirc package does not ship any files in /etc/systemd - 
these are by definition custom-maintained files.


Secondly, the --nodaemon *is* indeed used in 
/lib/system/system/lircd.service since this is a simple service. Refer 
to the systemd docs for an explanation.


Note that  any setting in /etc/systemd will overrule corresponding 
setting in /lib/systemd. Again, check the systemd docs.


I'm leaning to closing this as not-a-bug. Please raise these kind of 
concerns which are more like support issues on the upstream mailing list 
at http://sf.net/p/lirc.



Cheers!

--alec

Bug#876918: juffed FTBFS: symbol differences

[Adrian Bunk]

Source: juffed
Version: 0.10-85-g5ba17f9-13
Severity: serious

Some recent change in unstable makes juffed FTBFS:

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

...
   dh_makeshlibs -O--buildsystem=cmake -O--fail-missing 
-O--builddirectory=./build
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libjuffed-engine-qsci0.10/DEBIAN/symbols 
doesn't match completely debian/libjuffed-engine-qsci0.10.symbols
--- debian/libjuffed-engine-qsci0.10.symbols 
(libjuffed-engine-qsci0.10_0.10-85-g5ba17f9-13_amd64)
+++ dpkg-gensymbolsT8_ce7   2018-10-28 20:03:58.139800363 -1200
@@ -224,7 +224,7 @@
  (c++)"Juff::stringToBool(QString const&)@Base" 0.10
  (c++)"Juff::stringToColor(QString const&)@Base" 0.10
  (c++)"QByteArray::~QByteArray()@Base" 0.10
- (c++)"QForeachContainer::QForeachContainer(QStringList 
const&)@Base" 0.10
+#MISSING: 0.10-85-g5ba17f9-13# 
(c++)"QForeachContainer::QForeachContainer(QStringList 
const&)@Base" 0.10
  
(c++)"QList::append(Juff::DocEngine::ColorOption 
const&)@Base" 0.10
  (c++)"QList::detach_helper_grow(int, int)@Base" 
0.10
  (c++)"QList::QList(QList const&)@Base" 0.10
@@ -253,7 +253,7 @@
  (c++)"QList::detach_helper_grow(int, int)@Base" 0.10
  (c++)"QList::~QList()@Base" 0.10
  (c++)"QMap::detach_helper()@Base" 0.10
- (c++)"QMap::~QMap()@Base" 0.10
+#MISSING: 0.10-85-g5ba17f9-13# (c++)"QMap::~QMap()@Base" 0.10
  (c++)"QMap::detach_helper()@Base" 0.10
  (c++)"QMap::operator[](QString const&)@Base" 0.10
  (c++)"QMap::detach_helper()@Base" 0.10
@@ -390,6 +390,8 @@
  (c++)"Ui_FileTypesPage::setupUi(QWidget*)::{lambda()#8}::operator()() 
const::qstring_literal@Base" 0.10
  (c++)"Ui_FileTypesPage::setupUi(QWidget*)::{lambda()#9}::operator()() 
const::qstring_literal@Base" 0.10
  (c++)"Ui_FileTypesPage::setupUi(QWidget*)@Base" 0.10
+ _ZN9QtPrivate17QForeachContainerI11QStringListEC1ERKS1_@Base 
0.10-85-g5ba17f9-13
+ _ZN9QtPrivate17QForeachContainerI11QStringListEC2ERKS1_@Base 
0.10-85-g5ba17f9-13
  (c++|arch= !amd64 !arm64 !mips64el !ppc64el !s390x !alpha !kfreebsd-amd64 
!ppc64 !sparc64)"int const* std::__find_if >(int const*, int const*, 
__gnu_cxx::__ops::_Iter_equals_val, 
std::random_access_iterator_tag)@Base" 0.10
  (c++)"non-virtual thunk to Juff::FileTypesPage::~FileTypesPage()@Base" 0.10
  (c++)"non-virtual thunk to Juff::JuffScintilla::~JuffScintilla()@Base" 0.10
dh_makeshlibs: failing due to earlier errors
debian/rules:14: recipe for target 'binary' failed
make: *** [binary] Error 2

Bug#876561: transition: gdal

[Emilio Pozuelo Monfort]

Control: forwarded -1 
https://release.debian.org/transitions/html/gdal-2.2.2.html
Control: block -1 with 874276

On 23/09/17 21:46, Bas Couwenberg wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> For the Debian GIS team I'd like to transition to GDAL 2.2.2.
> 
> Like the previous transition to GDAL 2.2.1 (#866797), there is no SONAME
> bump, only the virtual ABI package changed to account for the C++ symbol
> changes.
> 
> All reverse dependencies rebuilt successfully with GDAL 2.2.2 from
> experimental as summarized below, except gazebo.
> 
> gazebo (7.8.1+dfsg-1) FTBFS for some unclear reason unrelated to gdal
> (it FTBFS with plain unstable too):
> 
>  [ 88%] Built target gazebo_gui
>  make[2]: Leaving directory '/build/gazebo-7.8.1+dfsg/obj-x86_64-linux-gnu'
>  Makefile:165: recipe for target 'all' failed
> 
> 
> libgdal-grass doesn't need a binNMU as the 2.2.2 version will be
> uploaded to unstable instead. liblas likewise doesn't need a binNMU,
> the version is experimental will be moved to unstable instead.
> 
> 
> A complication for the transition is the inability to build the gdal
> package on armhf, due to an issue with ca-certificates-java:
> 
>  Setting up ca-certificates-java (20170531+nmu1) ...
>  Error: missing `server' JVM at 
> `/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'.
>  Please install or use the JRE or JDK that contains these missing components.
> 
> But openjdk-8-jdk-headless cannot be installed because it depends on
> ca-certificates-java, see:
> 
>  
> https://buildd.debian.org/status/fetch.php?pkg=gdal=armhf=2.2.1%2Bdfsg-2%2Bb2=1505204615=0

That's #874276, and that's a blocker to start this.

Cheers,
Emilio

Bug#876917: ki18n FTBFS: test failures

[Adrian Bunk]

Source: ki18n
Version: 5.37.0-2
Severity: serious

Some recent change in unstable makes ki18n FTBFS:

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

...
cd obj-x86_64-linux-gnu && make -j16 test ARGS\+=-j16
make[3]: Entering directory '/build/1st/ki18n-5.37.0/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j16
Test project /build/1st/ki18n-5.37.0/obj-x86_64-linux-gnu
Start 1: ki18n-declarativetest
Start 2: ki18n-klocalizedstringtest
Start 3: ki18n-ktranscripttest
Start 4: ki18n-ktranscriptcleantest
Start 5: ki18n_install
1/5 Test #3: ki18n-ktranscripttest ***Failed0.01 sec
* Start testing of KTranscriptTest *
Config: Using QtTest library 5.9.1, Qt 5.9.1 (x86_64-little_endian-lp64 shared 
(dynamic) release build; by GCC 7.2.0)
WARNING: KTranscriptTest::initTestCase() testdata ktranscript-test.ini could 
not be located!
   Loc: [ki18n_5.37.0-2/autotests/testhelpers.cpp(50)]
QWARN  : KTranscriptTest::initTestCase() Could not locate test data file ""
FAIL!  : KTranscriptTest::initTestCase() 'deployTestConfig()' returned FALSE. 
(Could not deploy test ktranscript.ini)
   Loc: [ki18n_5.37.0-2/autotests/ktranscripttest.cpp(46)]
FAIL!  : KTranscriptTest::cleanupTestCase() 'removeTestConfig()' returned 
FALSE. (Could not remove test ktranscript.ini)
   Loc: [ki18n_5.37.0-2/autotests/ktranscripttest.cpp(63)]
Totals: 0 passed, 2 failed, 0 skipped, 0 blacklisted, 1ms
* Finished testing of KTranscriptTest *

2/5 Test #4: ki18n-ktranscriptcleantest ...***Failed0.01 sec
* Start testing of KTranscriptCleanTest *
Config: Using QtTest library 5.9.1, Qt 5.9.1 (x86_64-little_endian-lp64 shared 
(dynamic) release build; by GCC 7.2.0)
PASS   : KTranscriptCleanTest::initTestCase()
WARNING: KTranscriptCleanTest::test(test_basic) testdata test.js could not be 
located!
   Loc: [ki18n_5.37.0-2/autotests/ktranscriptcleantest.cpp(78)]
FAIL!  : KTranscriptCleanTest::test(test_basic) Funny module path '', skipping.

   Loc: [ki18n_5.37.0-2/autotests/ktranscriptcleantest.cpp(91)]
PASS   : KTranscriptCleanTest::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 3ms
* Finished testing of KTranscriptCleanTest *

3/5 Test #1: ki18n-declarativetest ***Failed0.12 sec
* Start testing of KI18nDeclarativeTest *
Config: Using QtTest library 5.9.1, Qt 5.9.1 (x86_64-little_endian-lp64 shared 
(dynamic) release build; by GCC 7.2.0)
PASS   : KI18nDeclarativeTest::initTestCase()
WARNING: KI18nDeclarativeTest::testLocalizedContext(translation) testdata 
test.qml could not be located!
   Loc: [ki18n_5.37.0-2/autotests/ki18ndeclarativetest.cpp(47)]
QWARN  : KI18nDeclarativeTest::testLocalizedContext(translation) QQmlComponent: 
Component is not ready
FAIL!  : KI18nDeclarativeTest::testLocalizedContext(translation) 'object' 
returned FALSE. ()
   Loc: [ki18n_5.37.0-2/autotests/ki18ndeclarativetest.cpp(58)]
WARNING: KI18nDeclarativeTest::testLocalizedContext(singular translation) 
testdata test.qml could not be located!
   Loc: [ki18n_5.37.0-2/autotests/ki18ndeclarativetest.cpp(47)]
QWARN  : KI18nDeclarativeTest::testLocalizedContext(singular translation) 
QQmlComponent: Component is not ready
FAIL!  : KI18nDeclarativeTest::testLocalizedContext(singular translation) 
'object' returned FALSE. ()
   Loc: [ki18n_5.37.0-2/autotests/ki18ndeclarativetest.cpp(58)]
WARNING: KI18nDeclarativeTest::testLocalizedContext(plural translation) 
testdata test.qml could not be located!
   Loc: [ki18n_5.37.0-2/autotests/ki18ndeclarativetest.cpp(47)]
QWARN  : KI18nDeclarativeTest::testLocalizedContext(plural translation) 
QQmlComponent: Component is not ready
FAIL!  : KI18nDeclarativeTest::testLocalizedContext(plural translation) 
'object' returned FALSE. ()
   Loc: [ki18n_5.37.0-2/autotests/ki18ndeclarativetest.cpp(58)]
WARNING: KI18nDeclarativeTest::testLocalizedContext(plural translation with 
domain) testdata test.qml could not be located!
   Loc: [ki18n_5.37.0-2/autotests/ki18ndeclarativetest.cpp(47)]
QWARN  : KI18nDeclarativeTest::testLocalizedContext(plural translation with 
domain) QQmlComponent: Component is not ready
FAIL!  : KI18nDeclarativeTest::testLocalizedContext(plural translation with 
domain) 'object' returned FALSE. ()
   Loc: [ki18n_5.37.0-2/autotests/ki18ndeclarativetest.cpp(58)]
PASS   : KI18nDeclarativeTest::cleanupTestCase()
Totals: 2 passed, 4 failed, 0 skipped, 0 blacklisted, 13ms
* Finished testing of KI18nDeclarativeTest *

4/5 Test #2: ki18n-klocalizedstringtest ...   Passed0.12 sec
5/5 Test #5: ki18n_install    Passed3.46 sec

40% tests passed, 3 tests failed out of 5

Total Test time (real) =   3.47 sec

The following tests FAILED:
  1 - ki18n-declarativetest (Failed)
  3 - ki18n-ktranscripttest 

Bug#876041: transition: gl2ps

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 26/09/17 19:12, Anton Gladky wrote:
> Control: tags -1 -moreinfo
> 
> All rdeps are tested against new version (except vtk6
> due to the current dependency problem in sid).
> 
> Package: avogadro OK
> Package: drawxtlOK
> Package: gabedit   OK
> Package: gfsview   OK
> Package: giac   OK
> Package: gmshOK
> Package: oce OK
> Package: octave  OK
> Package: paraviewOK
> Package: qtiplot OK
> Package: sumoOK
> Package: vtk6Not testable now in sid, fails to install deps
> Package: xcrysdenOK
> 
> Please consider scheduling the transition.

Go ahead.

Cheers,
Emilio

Bug#876898: manpages: versioned dependency "<< 4.13-3" in Breaks field is too restrictive for stretch-backports

[Daniel Reichelt]

4.13-3~bpo9+2 works fine now.

Thanks, Tobias!




signature.asc
Description: OpenPGP digital signature

Bug#876899: apt: Log to the systemd journal

[Julian Andres Klode]

On Tue, Sep 26, 2017 at 02:46:55PM -0400, Jeremy Bicha wrote:
> Source: apt
> Version: 1.5
> Severity: wishlist
> 
> Ubuntu 17.10 has switched from the unmaintained gnome-system-log app
> to gnome-logs by default. While gnome-system-log is a traditional log
> viewer, gnome-logs only displays logs from systemd. apt was identified
> as a particular part of the system that doesn't use systemd logging
> and so this is a regression compared to previous Ubuntu releases.
> 
> I expect Debian will need to maintain the ability to emit traditional
> logs without using systemd's journal. It makes sense to me for apt on
> Ubuntu to use systemd logging by default, but I think it makes sense
> on Debian too. At least on Ubuntu, it would make sense to *only* log
> to the systemd journal (systemd can be configured to create
> traditional logs for users that want that).

So, not discussing about usefulness or not but practical aspects:

- chroots would also log in the machine journal, which is wrong
- same for some other weird temporary chroot thingies
- term.log might contain sensitive data that should not be
  easily available (I think)
- dpkg.log and update-alternatives.log are more detailed step-by-step
  logs.

Maybe someone on debian-devel has some more opinion, but I'm not sure
if it is worthwhile pursuing this.
-- 
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#876858: gnudatalanguage build depends on (and recommends) removed package plplot12-driver-xwin

[Axel Beckert]

Control: tag -1 + pending

Hi Ole,

Ole Streicher wrote:
> On 26.09.2017 22:21, Axel Beckert wrote:
> > Ole: Do you have specific plans for the next upload of gnudatalanguage
> > or is this just something which needs to be done by some team member?
> 
> I'd do it in the next days, but if you have spare time: go ahead :-)

Thanks for the prompt feedback. Will do.

> There is nothing else in the queue for gnudatalanguage in the moment.

I noticed a few minor things, e.g. the deprecation of the extra
priority.

I also noticed that the watch file is no more working. But then again,
Sourceforge seems severly broken at the moment. So that might just be
Sourceforge, not us. Hopefully a temporary issue.

> Thanks for still having an eye on these packages!!!

That's what I promised when I downgraded myself to just co-maintainer.
:-)

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

Bug#876829: "pkg-config --libs cfitsio" contains -lcurl but no dependency on libcurl4-gnutls-dev

[Aurelien Jarno]

Version: 3.420-3

On 2017-09-26 12:11, Adrian Bunk wrote:
> Package: libcfitsio-dev
> Version: 3.420-2
> Severity: serious
> Control: affects -1 src:python-astropy src:gyoto src:vips
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-astropy.html
> 
> ...
> creating build/temp.linux-x86_64-2.7/astropy/io/fits
> creating build/temp.linux-x86_64-2.7/astropy/io/fits/src
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/lib/python2.7/dist-packages/numpy/core/include 
> -I/usr/include/python2.7 -c astropy/io/fits/src/compressionmodule.c -o 
> build/temp.linux-x86_64-2.7/astropy/io/fits/src/compressionmodule.o
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
> -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fdebug-prefix-map=/build/python2.7-VlMpWk/python2.7-2.7.14=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 
> build/temp.linux-x86_64-2.7/astropy/io/fits/src/compressionmodule.o -lcfitsio 
> -lpthread -lcurl -o build/lib.linux-x86_64-2.7/astropy/io/fits/compression.so
> /usr/bin/ld: cannot find -lcurl
> collect2: error: ld returned 1 exit status
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> debian/rules:20: recipe for target 'build-python2.7' failed
> make[1]: *** [build-python2.7] Error 1
> 
> 
> Root cause:
> 
> $ pkg-config --libs cfitsio
> -lcfitsio -lpthread -lcurl  
> $ 
> 
> Either the -lcurl should not be there or libcfitsio-dev
> must depend on libcurl4-gnutls-dev.

It looks like I forgot to close the bug in the changelog. Doing so with
this mail.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#876916: Updating the bum Uploaders list

[Tobias Frost]

Source: bum
Version: 2.5.2-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Federico Di Gregorio  has not been working on
the bum package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#876915: Updating the ois Uploaders list

[Tobias Frost]

Source: ois
Version: 1.3.0+dfsg0-6
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Federico Di Gregorio  has not been working on
the ois package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

Bug#876913: stretch-pu: package dose3/5.0.1-8+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2017-09-26 at 22:59 +0200, Ralf Treinen wrote:
> please consider accepting dose3 version 5.0.1-8+deb9u1 for the next
> stable point release. This source package generates in particular
> the binary package dose-distcheck and dose-builddebcheck; the latter
> is used by wanna-build to decide whether packages can be scheduled
> for rebuild.
> 
> This version contains a fix for an erroneous handling of versioned
> provides. Please refer to 
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867104
> 
> for a full history of the discussion.
> 

Please go ahead.

Regards,

Adam

Bug#875895: ITP: chkservice -- Systemd units manager with ncurses, terminal interface

[Ana C. Custura]

retitle 875895 ITP: chkservice -- Systemd units manager with ncurses,
terminal interface
owner 875895 !
thanks

Hi,

I would like to work on this.

Regards,
Ana

Bug#876626: [Xastir] Bug#876626: Xastir loose TCP/IP data afer 12 hours of use

[MLHPUB]

Hello Ian,

I don't know about latest snapshots.
Maybe it does not occur with 2.0.9 version but I am not comfortable with 
upgrade outside of Debian repositiories...


Regards,

Matthieu
F4ACU

On Sun, 24 Sep 2017 10:55:13 +0100 "Iain R. Learmonth"  
wrote:

Hi,

On Sun, Sep 24, 2017 at 05:20:44AM -0400, David A Aitcheson wrote:
> > I usually use Xastir during all day, only with a TCP/IP to APRS-IS
> > connection at this moment (no radio link).
> > After more than 12 days uptime, Xastir loose many data from APRS-IS :
> >
> > - ACK messages are not received
> > - positions reports (even visible on aprs.fi) are not displayed
> >
> > There is a kind of latency time on RX data from APRS-IS.
> >
> > It is necessary to quit and restart Xastir to retreive en normal
> > behavior.

My question would be: does this occur in the latest Xastir snapshots?

It's been a long time since there was a release of Xastir and I'm sure the
Debian package is missing a number of fixes that have been applied upstream.

It's been on my todo list for a while to just update to a git snapshot to
get some fixes into the Debian package, but I've not yet had time. If
someone can tell me this doesn't happen if you build from source then that
would be an easy fix.

Thanks,
Iain.

Bug#876914: mozjs shouldn't ship in buster

[Adrian Bunk]

Source: mozjs
Version: 1.8.5-1.0.0+dfsg-7
Severity: serious

mozjs is an ancient JS engine with unfixed security issues
that shouldn't ship in buster.

RC bugs have already been filed against the reverse dependencies.

Bug#876819: Debian mirror ftp.heikorichter.name: out-of-date

[Heiko Richter]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

Just found the error and fixed it. ftpsync is running right now, so the
mirror should be in sync again shortly.

Heiko


Am 26.09.2017 um 10:37 schrieb Peter Palfrader:
> Package: mirrors
> User: mirr...@packages.debian.org
> Usertags: mirror-problem may-auto-close
> Control: submitter -1 mirr...@debian.org
> 
> Hi,
> 
> I was checking some things in the Debian mirror universe and noticed
> a problem with your mirror:
> 
> 
> o Your mirror is out of date by almost a week
>   Status: https://mirror-master.debian.org/status/mirror-info/ftp.heik
orichter.name.html
> 
> o we recommend mirrors not sync directly from service aliases such as
>   ftp..debian.org (only http is guaranteed to be available at
>   ftp..d.o sites).  Maybe change your config to sync from
>   the site currently backing the ftp..debian.org service you sync
>   from?
> 
> Peter
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZysRSAAoJECKEz6pWghImcU4QAJPI0m7/EhZv1IO39CbSniK6
y3Y7hroIcdnWAcvRHw/buNvbBjfouMshbNpiEX+YmF9+VLJo3aHYIrW0ii1TNyjj
tL0SAdoMmdBlY4rvJ6VbM7MFSFifHDSgRAfH7JbmE30wdvJAOPLvqENVO1534q5q
tugnGV7GaJv1Lv71JRDQOOyVdw3IzfP4fdSTg0ST+QctdsTV5j/qtF3TMDZ4XRct
fP+x/opb8DGv3fEQXlDhFwfIDPfkxZeuzcbYQK/mtxOyWoHRf7a/y+XJAh+o2Shv
SCpyykiSo6mZdGAKTb8SjcKzhHTdcGCp6HKqpLZ56XXt3vcAF0cIzvPnBFCqUXOI
4lld/aDyL+wDynnJn4x7+eOdMmxo8GKJ7TXBqH4POrRTAi0LASHMHHHxYnByTf+E
8u+j1ikAdx+FKtXfpodHJO7Gg3gXwjOiYF6RhXL7AHkbTyzY0yo3A21Hl4XbD/+U
KRVfYOje/JVQc8/h5qpqYwmidoPsoVC/pjJyMUBPrME9xmzjTTQznDK5C2Ih5pK6
BBSpkkijDfMlnO121Acb+erpfyW4Jbm6qOezBLX3OWXPU4X6212S/IdE4aLvXrxX
adLt/idzZDwXdr18DVvJQUpK+BWEBc/a+OEjPSOKPp4bK6pXVJEBMNaY6Oj0vYBE
50LtiNiymMiXtcYJJtmG
=5fhb
-END PGP SIGNATURE-

Bug#597580: [PATCH] copy_exec: use 'which' to find full path to executable.

[Scott Moser]

Suggested patch is attached.

This would help to fix other bugs such as 852569.
From c16eddf70f92d1de9f77b4d39c00db329036ea1e Mon Sep 17 00:00:00 2001
From: Scott Moser 
Date: Tue, 26 Sep 2017 16:55:20 -0400
Subject: [PATCH] copy_exec: use 'which' to find full path to executable.

Add support in 'copy_exec' to not require a full path to the executable
that will be copied.  This is related to #852569.

Debian: #597580
---
 hook-functions | 11 ---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/hook-functions b/hook-functions
index 5da0cde..02a4477 100644
--- a/hook-functions
+++ b/hook-functions
@@ -159,10 +159,15 @@ copy_file() {
 # Location of the image dir is assumed to be $DESTDIR
 # We never overwrite the target if it exists.
 copy_exec() {
-	local src target x nonoptlib ret
+	local osrc src target x nonoptlib ret
 
-	src="${1}"
-	target="${2:-$1}"
+	osrc="${1}"
+	if ! src=$(which "$osrc"); then
+		echo "Error: could not find path to '$osrc'"
+		return 2
+	fi
+
+	target="${2:-$src}"
 
 	copy_file binary "${src}" "${target}" || return $(($? - 1))
 
-- 
2.7.4

Bug#876913: stretch-pu: package dose3/5.0.1-8+deb9u1

[Ralf Treinen]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

please consider accepting dose3 version 5.0.1-8+deb9u1 for the next
stable point release. This source package generates in particular
the binary package dose-distcheck and dose-builddebcheck; the latter
is used by wanna-build to decide whether packages can be scheduled
for rebuild.

This version contains a fix for an erroneous handling of versioned
provides. Please refer to 

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

for a full history of the discussion.

The diff with respect of the version of the package in stable consists
essentially of 7 lines of changed OCaml code, plus an additional test case
for ci tests. Full diff is attached.

Thanks for considering -Ralf.

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

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index f70cf83..88bdbd3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+dose3 (5.0.1-8+deb9u1) stretch; urgency=medium
+
+  * patch virtual_provides: packages that provide the same virtual package
+in different versions, or that provide the same versioned virtual package
+as a real package, are co-installable (closes: #867104).
+  * add test-case for versioned virtual packages
+
+ -- Ralf Treinen   Tue, 29 Aug 2017 14:43:57 +0200
+
 dose3 (5.0.1-8) unstable; urgency=medium
 
   * Patches taken from upstream (thanks, Josch!)
diff --git a/debian/patches/series b/debian/patches/series
index beee4c9..b0ebd7d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -12,3 +12,4 @@ ocaml-4.02.3+gcc-6.2.0
 architecture-tuples
 architectures-dpkg-1.18.15
 deb-drop-b-d-arch
+versioned_provides
diff --git a/debian/patches/versioned_provides 
b/debian/patches/versioned_provides
new file mode 100644
index 000..63609de
--- /dev/null
+++ b/debian/patches/versioned_provides
@@ -0,0 +1,30 @@
+Author: Ralf Treinen 
+Description: packages that provide the same virtual package in different
+  versions, or that provide the same versioned virtual package as a real
+  package, are co-installable
+Debian-bug: #867104
+
+diff --git a/deb/debcudf.ml b/deb/debcudf.ml
+index 44f72e8..c70ed67 100644
+--- a/deb/debcudf.ml
 b/deb/debcudf.ml
+@@ -307,12 +307,13 @@ let loadlc ?native_arch ?package_arch tables name l =
+ let loadlp ?native_arch ?package_arch tables l =
+   List.flatten (
+ List.map (fun ((name,_) as vpkgname,constr) ->
+-  let encname = add_arch_info ?native_arch ?package_arch vpkgname in
+-  match constr with
+-  |None -> [("--virtual-"^encname,Some(`Eq,Util.max32int - 1))]
+-  |Some("=",v) ->
+-let constr = Some(`Eq,get_cudf_version tables (name,v)) in
+-[("--virtual-"^encname,constr);(encname,constr)]
++let encname = add_arch_info ?native_arch ?package_arch vpkgname in
++let vencname = "--virtual-"^encname in 
++match constr with
++|None -> [(vencname,Some(`Eq,Util.max32int - 1))]
++|Some("=",v) ->
++  let constr = Some(`Eq,get_cudf_version tables (name,v)) in
++  [(vencname,constr);(vencname,Some(`Eq,Util.max32int - 1))]
+   |_ -> fatal "This should never happen : a provide can be either = or 
unversioned"
+ ) l
+   )
diff --git a/debian/tests/bug867104 b/debian/tests/bug867104
new file mode 100755
index 000..9697c11
--- /dev/null
+++ b/debian/tests/bug867104
@@ -0,0 +1,17 @@
+#!/bin/sh
+
+# debian bug 867104: wanna-build issue with src:perl versioned Provides
+
+set -e
+
+this=dose-debcheck
+indir=debian/tests/repos
+outdir=${ADT_ARTIFACTS}/${this}
+mkdir -p ${outdir}
+
+packfile=$indir/virtual_and_real
+base=$(basename $packfile)
+
+dose-debcheck --checkonly=main ${packfile} \
+| tee ${outdir}/${base}.out \
+| grep -q "broken-packages: 0"
diff --git a/debian/tests/control b/debian/tests/control
index 29b1424..abb12d7 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,4 +1,4 @@
-Tests: dose-debcheck bug811569 bug790422
+Tests: dose-debcheck bug811569 bug790422 bug867104
 Depends: dose-distcheck
 
 Tests: dose-builddebcheck
diff --git a/debian/tests/repos/virtual_and_real 
b/debian/tests/repos/virtual_and_real
new file mode 100644
index 000..28553c6
--- /dev/null
+++ b/debian/tests/repos/virtual_and_real
@@ -0,0 +1,14 @@
+Package: main
+Version: 1
+Architecture: amd64
+Depends: perl-base, libscalar-list-utils-perl (= 1:1.48-1)
+
+Package: perl-base
+Version: 5.24.1-5

Bug#876912: lirc: nodaemon option

[Arno None]

Source: lirc
Version: 0.10.0
Severity: normal

Dear Maintainer,

To start the lirc service lircd with the option 'nodaemon' in 
/etc/lirc/lirc_options.conf I had to remove the option --nodaemon from 
/etc/systemd/system/multi-user.target.wants/lircd.service
Why is this option set in a file that starts a service (daemon)?

When this option is removed the 'nodaemon' option in 
/etc/lirc/lirc_options.conf has to be set to 'True' to start lircd
Shouldn't that be 'False'?


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 9.1 (stretch)
Release:9.1
Codename:   stretch
Architecture: armv7l

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

Bug#876911: openmpi FTBFS with debhelper 10.9

[Adrian Bunk]

Source: openmpi
Version: 2.1.1-6
Severity: serious

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

...
dh_link -p libopenpi-dev usr/lib/x86_64-linux-gnu/libmpi_java.so.20 
usr/lib/x86_64-linux-gnu/libmpi_java.so ; \
...
dh_link: unknown option or error during option parsing; aborting
debian/rules:101: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 25


libopenpi-dev looks like a typo.

Bug#861616: Bug #861616 update

[Thierry Rascle]

Dear Maintainer,

Here's an update to the bug report #861616:

1. The "not overriding" indicators appear as "overriding" indicators.
   NOT FIXED with gnat-gps 6.1.2016-1.

2. The line numbers shown for the subprogram declarations are wrong (one
   unit too high) if there is an "overriding" or a "not overriding"
   indicator on the previous line. NOT FIXED with gnat-gps 6.1.2016-1.

3. The rendering of the declaration of subtypes erroneously includes
   preceding lines of code : FIXED with gnat-gps 6.1.2016-1.

4. When there is a quantified expression in the precondition or
   postcondition of a subprogram, then the documentation for the
   subprogram is not rendered. I guess it's not a new issue but I
   discovered it recently with 6.1.2016-1. I managed to patch the
   frontend. The sample code at
   https://github.com/thierr26/gnatdoc_test has been updated to make
   this issue visible.

Please find attached an updated patch for 6.1.2016-1 (fixes points 1, 2
and 4).

Do you plan to forward this bug report upstream ? Do you know whether
that kind of issues are currently being worked out upstream ?
--- a/gnatdoc/src/gnatdoc-backend-html.adb
+++ b/gnatdoc/src/gnatdoc-backend-html.adb
@@ -938,12 +938,45 @@
declare
   Buffer : aliased String := To_String (Get_Src (E));
   Code   : JSON_Value;
+  Line : Positive := LL.Get_Location (E).Line;
+  Start_Col : Positive;
 
begin
+  if Buffer'Length > 0
+and then (Get_Kind (E) = E_Procedure
+or else Get_Kind (E) = E_Function
+or else Get_Kind (E) = E_Entry) then
+ Start_Col := Buffer'First;
+ while (Buffer (Start_Col) = ' '
+   or else Buffer (Start_Col) = ASCII.HT)
+   and then Start_Col < Buffer'Last loop
+Start_Col := Start_Col + 1;
+ end loop;
+ if Buffer (Start_Col) /= ' '
+   and then Buffer (Start_Col) /= ASCII.HT
+   and then Buffer'Last >= Start_Col + 11
+   and then (Buffer (Start_Col + 10) = ASCII.LF
+   or else Buffer (Start_Col + 11) = ASCII.LF) then
+if Buffer (Start_Col .. Start_Col + 9)
+  = "overriding" then
+   Line := Line - 1;
+end if;
+ end if;
+ if Buffer (Start_Col) /= ' '
+   and then Buffer (Start_Col) /= ASCII.HT
+   and then Buffer'Last >= Start_Col + 15
+   and then (Buffer (Start_Col + 14) = ASCII.LF
+   or else Buffer (Start_Col + 15) = ASCII.LF) then
+if Buffer (Start_Col .. Start_Col + 13)
+  = "not overriding" then
+   Line := Line - 1;
+end if;
+ end if;
+  end if;
   Self.Print_Source_Code
 (Tree.File,
  Buffer'Unchecked_Access,
- LL.Get_Location (E).Line,
+ Line,
  Printer,
  Code);
   Prepend (Description, Code);
--- a/gnatdoc/src/gnatdoc-frontend.adb
+++ b/gnatdoc/src/gnatdoc-frontend.adb
@@ -64,6 +64,7 @@
   Tok_Is,
   Tok_Limited,
   Tok_New,
+  Tok_Not,
   Tok_Null,
   Tok_Overriding,
   Tok_Others,
@@ -1250,6 +1251,8 @@
  Cursor : Extended_Cursor.Extended_Cursor;
  Last_Idx   : Natural := 0;
  Par_Count  : Natural := 0;
+ Prev_Prev_Token: Tokens := Tok_Unknown;
+ Prev_Prev_Token_Loc: Source_Location;
  Prev_Token : Tokens := Tok_Unknown;
  Prev_Token_Loc : Source_Location;
  Token  : Tokens := Tok_Unknown;
@@ -1309,12 +1312,14 @@
  procedure Clear_Parser_State is
 No_Source_Location : constant Source_Location := (0, 0, 0);
  begin
-Last_Idx   := 0;
-Par_Count  := 0;
-Prev_Token := Tok_Unknown;
-Prev_Token_Loc := No_Source_Location;
-Token  := Tok_Unknown;
-Token_Loc  := No_Source_Location;
+Last_Idx:= 0;
+Par_Count   := 0;
+Prev_Prev_Token := Tok_Unknown;
+Prev_Prev_Token_Loc := No_Source_Location;
+Prev_Token  := Tok_Unknown;
+Prev_Token_Loc  := No_Source_Location;
+Token   := Tok_Unknown;
+Token_Loc   := No_Source_Location;
 
 Nested_Variants_Count  := 0;
 

Bug#836546: enchant FTCBFS: uses build architecture pkg-config

[Manuel A. Fernandez Montecelo]

Hi,

2017-09-26 0:56 GMT+02:00 Manuel A. Fernandez Montecelo
:
> 2017-09-25 6:57 GMT+02:00 Prach Pongpanich :
>> Hi,
>>
>> On Mon, Sep 25, 2017 at 01:25:17AM +0200, Manuel A. Fernandez Montecelo 
>> wrote:
>>> Hi,
>>>
>>> I'd like to get this issue fixed, I could prepare an NMU in the next few
>>> days.
>>>
>>> This package is under LowNMU clause, but still I though that it would be
>>> nice to ask if it's OK with the maintainer,because the patch is slightly
>>> intrusive with the upstream source.
>>>
>>
>> Please go ahead, the repo is in collab-maint [0].
>>
>> [0] https://anonscm.debian.org/cgit/collab-maint/enchant.git
>
>
> Done and pushed, thanks!
>
> BTW, there's a lintian error about using "activate-noawait ldconfig",
> I think that it's because of the triggers file:
> debian/libenchant1c2a.triggers , it's probably implicit due to being a
> package with libraries or something, thus appearing as duplicate even
> if there's only one line in that file.
>
> My advice is to remove the file and check that nothing breaks in the
> local system.  I didn't fix it because I am not familiar with the
> library and what uses it.

After 2 unsuccessful attempts due to mismatching .orig.tar
(git-buildpackage changed the place where it looks for such files), it
went through and built in almost all arches in the buildds.

I also pushed the fix for the double triggers, but didn't include it
in the upload:

  
https://anonscm.debian.org/cgit/collab-maint/enchant.git/commit/?id=7d688257524064d98e8ee0450996a7dc068487b8


This is the current file in my system, which shows the duplicated
lines  that cause the lintian error, due to dh_makeshlibs adding a
line automatically:

  $ cat '/var/lib/dpkg/info/libenchant1c2a:amd64.triggers'
  activate-noawait ldconfig
  # Triggers added by dh_makeshlibs
  activate-noawait ldconfig


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#852569: related bug 597580

[Scott Moser]

I'll fix cloud-initramfs-tools to find udevadm in PATH, but
it seems like the right thing to do is to fix:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597580

And then to make cloud-initramfs-tools just use:
  copy_exec udevadm

Bug#876840: fseeko() on reference file: Invalid argument (Was: Bug#876840: staden-io-lib FTBFS on non-i386 32bit: FAIL: java)

[Andreas Tille]

control: forwarded -1 James Bonfield 
control: tags -1 upstream

Hi James,

there is another issue reported to the Debian packaged io_lib
which you can read here:

https://bugs.debian.org/876840

Below is a hint what might have caused the issue.

Kind regards

  Andreas.

On Tue, Sep 26, 2017 at 10:38:12PM +0200, Christian Seiler wrote:
> Hi Andreas,
> 
> On 09/26/2017 10:08 PM, Andreas Tille wrote:
> > I need to admit I have no idea why
> > 
> >fseeko() on reference file: Invalid argument
> > 
> > is happening on some architectures.
> 
> According to the manpage of fseek(), which is identical to fseeko()
> apart from the offset data type:
> 
> ERRORS
>[...]
>EINVAL The whence argument to fseek() was not SEEK_SET,
>SEEK_END, or SEEK_CUR.  Or: the resulting file offset would
>be negative.
> 
> I suspect that something is calling fseeko() with a negative offset.
> 
> I'd recommend doing an strace on the specific test binary that
> fails on a porterbox (e.g. armhf) + on amd64 for comparison and
> then look for the offending fseeko() call. That might help isolate
> the issue.
> 
> Regards,
> Christian
> 

-- 
http://fam-tille.de

Bug#876839: staden-io-lib FTBFS on big endian: error: invalid operands to binary

[Andreas Tille]

control: forwarded -1 James Bonfield 
control: tags -1 upstream

Hi James,

There is a bug report against the Debian package of the latest
io_lib version.  See the full bug log here:

https://bugs.debian.org/876839

Below you can read about a suggested solution.

Kind regards

   Andreas.

On Tue, Sep 26, 2017 at 10:31:01PM +0200, Christian Seiler wrote:
> On 09/26/2017 10:06 PM, Andreas Tille wrote:
> >> ...
> >> In file included from bgzip.c:56:0:
> >> bgzip.c: In function 'gzi_index_dump':
> >> ../io_lib/os.h:127:10: error: invalid operands to binary & (have 'uint64_t 
> >> * {aka long long unsigned int *}' and 'long long int')
> >>  (((x & 0x00ffLL) << 56) + \
> >>   ^
> >> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
> >>  #define le_int8(x) iswap_int8((x))
> >> ^~
> >> bgzip.c:190:16: note: in expansion of macro 'le_int8'
> >>  if (fwrite(le_int8(), sizeof(n), 1, idx_f) != 1)
> >> ^~~
> 
> This code is completely wrong.
> 
> le_int8 appears to do a 64 bit byte order swap to adjust the
> endianness of a quantity. What bgzip.c does at this point is the
> following (removed if() for clarity):
> 
> uint64_t n = idx->n;
> fwrite(le_int8(), sizeof(n), 1, idx_f);
> 
>  is the pointer to the 'n' variable, but you really don't want
> to byte swap a pointer to a local variable before passing it to
> a function that reads that pointer (also note that the pointer
> could be 32 bit on 32 bit systems!).
> 
> What you presumably want to do is byte swap the _contents_ of the
> pointer (especially since n is a 64 bit integer). If you look at
> the read code in the same file this is actually what happens:
> 
> if (8 != fread(, 1, 8, fp))
>   goto err;
> n = le_int8(n);
> 
> So what you'd rather want to have is the following code:
> 
> uint64_t n = le_int8(idx->n);
> fwrite(, sizeof(n), 1, idx_f);
> 
> Or, if I adjust the entirety of that section in the original write
> code:
> 
> int i;
> uint64_t n = le_int8(idx->n);
> if (fwrite(), sizeof(n), 1, idx_f) != 1)
>   goto fail;
> for (i=0; in; i++) {
> uint64_t nn;
> nn = le_int8(idx->c_off[i]);
>   if (fwrite(, sizeof(nn), 1, idx_f) != 1)
>   goto fail;
> nn = le_int8(idx->u_off[i]);
>   if (fwrite(, sizeof(nn), 1, idx_f) != 1)
>   goto fail;
> }
> 
> That should fix the compiler error you're seeing.
> 
> The only reason that doesn't fail on Little Endian is because the
> le_int8(x) function is a no-op on those systems and just passes
> through the original pointer.
> 
> Regards,
> Christian
> 

-- 
http://fam-tille.de

Bug#876840: fseeko() on reference file: Invalid argument (Was: Bug#876840: staden-io-lib FTBFS on non-i386 32bit: FAIL: java)

[Christian Seiler]

Hi Andreas,

On 09/26/2017 10:08 PM, Andreas Tille wrote:
> I need to admit I have no idea why
> 
>fseeko() on reference file: Invalid argument
> 
> is happening on some architectures.

According to the manpage of fseek(), which is identical to fseeko()
apart from the offset data type:

ERRORS
   [...]
   EINVAL The whence argument to fseek() was not SEEK_SET,
   SEEK_END, or SEEK_CUR.  Or: the resulting file offset would
   be negative.

I suspect that something is calling fseeko() with a negative offset.

I'd recommend doing an strace on the specific test binary that
fails on a porterbox (e.g. armhf) + on amd64 for comparison and
then look for the offending fseeko() call. That might help isolate
the issue.

Regards,
Christian

Bug#875882: bwm-ng FTCBFS: ./configure detects no input methods

[Samuel Henrique]

Hello Helmut

2017-09-26 1:51 GMT-03:00 Helmut Grohne :

> Hi Samuel,
>
> On Tue, Sep 26, 2017 at 01:09:19AM -0300, Samuel Henrique wrote:
> > Thanks for the bugreport and patch, but did you realized that there's a
> > FTBFS on linux when this patch is applied?
>
> Thanks for considering. I didn't see that coming, but a closer at
> configure.in explains that behaviour.
>

​I think you've opened FTCBFS bugs on at least 3 packages i maintain
(bwm-ng, aircrack-ng, and some netfilter package), and i'm thankful for
that, i'll consider all of them.​



> I see two (maybe three) ways forward:
>
>  a)  Fix configure.in. It should be checking DISK_INPUT_FOUND and others
>  to avoid adding input methods twice.
>
>  a2) In theory it should also stop special casing $cross_compiling.
>  AC_CHECK_FILE(/proc/diskstats) is perfectly fine during cross
>  compilation. The check will fail, but the cross builder will
>  supply the right cache variable to make it succeed.
>
>  b)  Acknowledge that configure.in is weird and only pass these flags
>  for cross compilation. Make them conditional to
>  "ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))".
>
> Do you have a preference?
>

​Yes, i would like a mix of a) and b), i think this should be fixed
upstream[1], and at the same time we could use b) until there's a new
release with a fixed configure.
Are you willing to send a patch upstream to fix this? In the meantime i can
apply option b) [i'd appreciate if you could update your patch to ack b),
but if you don't, i can do it myself on my next free time].

Thanks a lot!

[1]https://github.com/vgropp/bwm-ng​



-- 
Samuel Henrique 

Bug#876121: FTBFS: error: 'std::index_sequence' has not been declared

[Oliver Kurth]

Thank you - looks like it's working.


Oliver

Bug#876839: staden-io-lib FTBFS on big endian: error: invalid operands to binary

[Christian Seiler]

On 09/26/2017 10:06 PM, Andreas Tille wrote:
>> ...
>> In file included from bgzip.c:56:0:
>> bgzip.c: In function 'gzi_index_dump':
>> ../io_lib/os.h:127:10: error: invalid operands to binary & (have 'uint64_t * 
>> {aka long long unsigned int *}' and 'long long int')
>>  (((x & 0x00ffLL) << 56) + \
>>   ^
>> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
>>  #define le_int8(x) iswap_int8((x))
>> ^~
>> bgzip.c:190:16: note: in expansion of macro 'le_int8'
>>  if (fwrite(le_int8(), sizeof(n), 1, idx_f) != 1)
>> ^~~

This code is completely wrong.

le_int8 appears to do a 64 bit byte order swap to adjust the
endianness of a quantity. What bgzip.c does at this point is the
following (removed if() for clarity):

uint64_t n = idx->n;
fwrite(le_int8(), sizeof(n), 1, idx_f);

 is the pointer to the 'n' variable, but you really don't want
to byte swap a pointer to a local variable before passing it to
a function that reads that pointer (also note that the pointer
could be 32 bit on 32 bit systems!).

What you presumably want to do is byte swap the _contents_ of the
pointer (especially since n is a 64 bit integer). If you look at
the read code in the same file this is actually what happens:

if (8 != fread(, 1, 8, fp))
goto err;
n = le_int8(n);

So what you'd rather want to have is the following code:

uint64_t n = le_int8(idx->n);
fwrite(, sizeof(n), 1, idx_f);

Or, if I adjust the entirety of that section in the original write
code:

int i;
uint64_t n = le_int8(idx->n);
if (fwrite(), sizeof(n), 1, idx_f) != 1)
goto fail;
for (i=0; in; i++) {
uint64_t nn;
nn = le_int8(idx->c_off[i]);
if (fwrite(, sizeof(nn), 1, idx_f) != 1)
goto fail;
nn = le_int8(idx->u_off[i]);
if (fwrite(, sizeof(nn), 1, idx_f) != 1)
goto fail;
}

That should fix the compiler error you're seeing.

The only reason that doesn't fail on Little Endian is because the
le_int8(x) function is a no-op on those systems and just passes
through the original pointer.

Regards,
Christian

Bug#876858: gnudatalanguage build depends on (and recommends) removed package plplot12-driver-xwin

[Ole Streicher]

Hi Axel,

On 26.09.2017 22:21, Axel Beckert wrote:
> Ole: Do you have specific plans for the next upload of gnudatalanguage
> or is this just something which needs to be done by some team member?

I'd do it in the next days, but if you have spare time: go ahead :-)
There is nothing else in the queue for gnudatalanguage in the moment.

If you have even more spare time, you can have a look how to get the CI
tests for plplot running; this seems not so simple (and gets even more
complicated with my all-python-versions-support patch).

Thanks for still having an eye on these packages!!!

Cheers

Ole

Bug#861419: 4.12.0-0.bpo.1-amd64 does not seem to have this issue

[Rainer Dorsch]

Hi,

just a short update:

with 4.9.0 from Stretch I hit this issue within a week and had to reboot the 
system. With 4.12.0-0.bpo.1-amd64 I run now for almost three weeks and the 
issue did not pop up.

Either it is fixed or it seems to be at least triggered less frequently.

Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

Bug#868357: installation-guide: get rid of "not up to date for " warnings

[Holger Wansing]

Control: tags -1 + pending

Samuel Thibault  wrote:
> Holger Wansing, on mar. 26 sept. 2017 20:51:34 +0200, wrote:
> > Holger Wansing  wrote:
> > > Those warnings are there since Woody or Sarge, and I think they are no
> > > longer true.
> > > We should remove them.
> > 
> > A patch is attached.
> > It removes the warnings for all archs except hurd and kfreebsd variants.
> 
> It should be fine indeed :)

Committed.

Tagging bug as pending.


Holger

Bug#836675: sinntp: Unable to download news because of error

[Jakub Wilk]

Hi David!

Upstream speaking here. Thanks for the bug report, and sorry for the 
late reply.


* David Creelman , 2016-09-05, 01:49:
I have a small bash script that runs sinntp to download NNTP news in 
batch.

...

nntp-pull of comp.lang.javascript
Traceback (most recent call last):
 File "/usr/bin/sinntp", line 351, in 
   command(connection)
 File "/usr/bin/sinntp", line 192, in __call__
   start = config[group] if not self.options.reget else 0
 File "/usr/bin/sinntp", line 86, in __getitem__
   return int(file.read())
ValueError: invalid literal for int() with base 10: ''


That's weird. We only write integers to the state file, so they should 
never be empty. :\


Now, sinntp before 1.5.2 didn't write the state files atomically, so if 
you killed the sinntp process in a bad moment, or if the filesystem 
wasn't unmounted cleanly, then you could indeed end up with empty state 
files. Maybe that's what happened?



To get around this, I changed the line 86 to :-
return int("0" + file.read())


I'd rather not apply this change, since it's curing only symptoms, not 
the cause.


--
Jakub Wilk

Bug#876858: gnudatalanguage build depends on (and recommends) removed package plplot12-driver-xwin

[Axel Beckert]

Control: tag -1 + confirmed

Hi Adrian,

Adrian Bunk wrote:
> gnudatalanguage build depends on the removed package
> plplot12-driver-xwin.

Yes, this needs to be changed to the new, versionless package names
like plplot-driver-xwin.

JFTR: There's an intersection of the maintainers of gnudatalanguage in
Debian and those guys who have kept the plplot package alive with NMUs
over years and those who have now adopted plplot in Debian — so that's
not an unexpected bug. It's the plan. :-) See also
https://release.debian.org/transitions/html/auto-plplot.html

Ole: Do you have specific plans for the next upload of gnudatalanguage
or is this just something which needs to be done by some team member?

> Additionally, gnudatalanguage and python-gdl also recommend this
> package.

The same applies here again.

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

Bug#876757: gnome-terminal: does not set the underlying setting key for "show menubar"

[Egmont Koblinger]

Hi,

Right click menu's "Show Menubar" by design only influences the
current window (similarly to some other options there, such as
selecting a Profile or toggling Read-Only).

What you're looking for is the global menu's Edit -> Preferences ->
"Show menubar by default in new terminals".

cheers,
egmont

Bug#876908: Is blcr completely useless?

[Adrian Bunk]

On Tue, Sep 26, 2017 at 08:52:08PM +0100, Alan Woodland wrote:
>...
> In theory people could still be running old kernels to keep support
> alive and if that's the case then we should try to avoid breaking
> things,
>...

The last Debian release with blcr-dkms was wheezy,
and #776920 seems to make it clear that even the
jessie kernel is too new for blcr.

Running a pre-jessie kernel in buster is nothing that is supported, 
jessie userspace is likely the most recent that will work properly
with such old kernels.

> Alan

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#876840: fseeko() on reference file: Invalid argument (Was: Bug#876840: staden-io-lib FTBFS on non-i386 32bit: FAIL: java)

[Andreas Tille]

control: tags -1 help

Hi,

I need to admit I have no idea why

   fseeko() on reference file: Invalid argument

is happening on some architectures.

Any help is welcome

  Andreas.

On Tue, Sep 26, 2017 at 12:28:38PM +0300, Adrian Bunk wrote:
> Source: staden-io-lib
> Version: 1.14.9-2
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=staden-io-lib=sid
> 
> ...
> FAIL: java
> ==
> 
> === testing ./data/aux#aux_java.cram ===
> root=aux#aux_java
>  ../progs/scramble  -r ./data/aux.fa ./data/aux#aux_java.cram 
> test.out/aux#aux_java.scramble.sam
> fseeko() on reference file: Invalid argument
> Unable to fetch reference #0 1..20
> Failure to decode slice
> Failed to decode sequence
> FAIL java.test (exit status: 1)
> 
> 
> Testsuite summary for io_lib 1.14.9
> 
> # TOTAL: 10
> # PASS:  9
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See tests/test-suite.log
> 
> Makefile:706: recipe for target 'test-suite.log' failed
> make[4]: *** [test-suite.log] Error 1
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#876839: staden-io-lib FTBFS on big endian: error: invalid operands to binary

[Andreas Tille]

control: tag -1 help

Hi,

it seems this problem happens in bgzip interface.  Is there any known
change to the compression library that is incompatible since
staden-iu-lib was successfully uploaded and built (at least on several
architectures) yesterday.

Any help is welcome

 Andreas.

On Tue, Sep 26, 2017 at 12:27:27PM +0300, Adrian Bunk wrote:
> Source: staden-io-lib
> Version: 1.14.9-2
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=staden-io-lib=sid
> 
> ...
> In file included from bgzip.c:56:0:
> bgzip.c: In function 'gzi_index_dump':
> ../io_lib/os.h:127:10: error: invalid operands to binary & (have 'uint64_t * 
> {aka long long unsigned int *}' and 'long long int')
>  (((x & 0x00ffLL) << 56) + \
>   ^
> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
>  #define le_int8(x) iswap_int8((x))
> ^~
> bgzip.c:190:16: note: in expansion of macro 'le_int8'
>  if (fwrite(le_int8(), sizeof(n), 1, idx_f) != 1)
> ^~~
> ../io_lib/os.h:128:10: error: invalid operands to binary & (have 'uint64_t * 
> {aka long long unsigned int *}' and 'long long int')
>   ((x & 0xff00LL) << 40) + \
>   ^
> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
>  #define le_int8(x) iswap_int8((x))
> ^~
> bgzip.c:190:16: note: in expansion of macro 'le_int8'
>  if (fwrite(le_int8(), sizeof(n), 1, idx_f) != 1)
> ^~~
> ../io_lib/os.h:129:10: error: invalid operands to binary & (have 'uint64_t * 
> {aka long long unsigned int *}' and 'long long int')
>   ((x & 0x00ffLL) << 24) + \
>   ^
> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
>  #define le_int8(x) iswap_int8((x))
> ^~
> bgzip.c:190:16: note: in expansion of macro 'le_int8'
>  if (fwrite(le_int8(), sizeof(n), 1, idx_f) != 1)
> ^~~
> ../io_lib/os.h:130:10: error: invalid operands to binary & (have 'uint64_t * 
> {aka long long unsigned int *}' and 'long long int')
>   ((x & 0xff00LL) <<  8) + \
>   ^
> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
>  #define le_int8(x) iswap_int8((x))
> ^~
> bgzip.c:190:16: note: in expansion of macro 'le_int8'
>  if (fwrite(le_int8(), sizeof(n), 1, idx_f) != 1)
> ^~~
> ../io_lib/os.h:131:10: error: invalid operands to binary & (have 'uint64_t * 
> {aka long long unsigned int *}' and 'long long int')
>   ((x & 0x00ffLL) >>  8) + \
>   ^
> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
>  #define le_int8(x) iswap_int8((x))
> ^~
> bgzip.c:190:16: note: in expansion of macro 'le_int8'
>  if (fwrite(le_int8(), sizeof(n), 1, idx_f) != 1)
> ^~~
> ../io_lib/os.h:132:10: error: invalid operands to binary & (have 'uint64_t * 
> {aka long long unsigned int *}' and 'long long int')
>   ((x & 0xff00LL) >> 24) + \
>   ^
> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
>  #define le_int8(x) iswap_int8((x))
> ^~
> bgzip.c:190:16: note: in expansion of macro 'le_int8'
>  if (fwrite(le_int8(), sizeof(n), 1, idx_f) != 1)
> ^~~
> ../io_lib/os.h:133:10: error: invalid operands to binary & (have 'uint64_t * 
> {aka long long unsigned int *}' and 'long long int')
>   ((x & 0x00ffLL) >> 40) + \
>   ^
> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
>  #define le_int8(x) iswap_int8((x))
> ^~
> bgzip.c:190:16: note: in expansion of macro 'le_int8'
>  if (fwrite(le_int8(), sizeof(n), 1, idx_f) != 1)
> ^~~
> ../io_lib/os.h:134:10: error: invalid operands to binary & (have 'uint64_t * 
> {aka long long unsigned int *}' and 'long long unsigned int')
>   ((x & 0xff00LL) >> 56))
>   ^
> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
>  #define le_int8(x) iswap_int8((x))
> ^~
> bgzip.c:190:16: note: in expansion of macro 'le_int8'
>  if (fwrite(le_int8(), sizeof(n), 1, idx_f) != 1)
> ^~~
> ../io_lib/os.h:127:10: error: invalid operands to binary & (have 'uint64_t * 
> {aka long long unsigned int *}' and 'long long int')
>  (((x & 0x00ffLL) << 56) + \
>   ^
> ../io_lib/os.h:185:20: note: in expansion of macro 'iswap_int8'
>  #define le_int8(x) iswap_int8((x))
> ^~
> bgzip.c:193:13: note: in expansion of macro 'le_int8'
>   if (fwrite(le_int8(>c_off[i]), sizeof idx->c_off[i], 1, idx_f) != 1)
>  ^~~
> ../io_lib/os.h:128:10: error: invalid operands to binary & (have 'uint64_t * 
> {aka long long unsigned int *}' and 'long long int')
>   ((x & 

Bug#876908: Is blcr completely useless?

[Alan Woodland]

On 26 September 2017 at 20:28, Adrian Bunk  wrote:
>
> Source: blcr
> Version: 0.8.5-2.1
> Severity: serious
> Tags: buster sid
>
> As far as I can see:
> 1. blcr is dead upstream since 2013.
> 2. blcr requires both userspace and kernel parts.
> 3. The -dkms package is removed in unstable.
> 4. The beta version in experimental has an RC bug against
>the -dkms package that the module does not build
>with the jessie (sic) kernel.
>
> mpich is linked with the userspace library,
> but does that make any sense without the kernel part?

There was some activity in 2014 - 0.8.6 beta4, but the last I heard it
still had some issues with PPC64 that meant it wasn't worth uploading
to experimental and my plan was to hold out. Since there haven't been
any new versions released since then I'm inclined to agree. That'll
need a patch to the MPI build config though to stop linking against
and requiring the blcr userspace libraries as a precursor to actually
removing BLCR from sid.

In theory people could still be running old kernels to keep support
alive and if that's the case then we should try to avoid breaking
things, but certainly I've not actively been using BLCR in my work for
quite some time now.

Alan

Bug#876910: ruby-json: Provide an arch independent package for Java extension

[Miguel Landaeta]

Package: src:ruby-json
Version: 2.1.0+dfsg-1
Severity: wishlist
Tags: newcomer

Currently, Java extension files (parser.jar and generator.jar) are
being built in every release architecture.

A new package libruby-json-java should be introduced to built those
files only once in that package.

An approach similar to the one used in ruby-psych package.

I'll complete this task later unless somebody beats me to it.

-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

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

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature

Bug#874580: stretch-pu: package waagent/2.2.14-1~deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

> Am 25. September 2017 22:35:33 MESZ schrieb "Adam D. Barratt"
> :
> > On Wed, 2017-09-20 at 13:27 +0200, Martin Zobel-Helas wrote:
> > >  On Wed, Sep 20, 2017 at 11:43:56AM +0200, Bastian Blank wrote:
[...]
> > > > >  Find attached the full diff gzip'd.
> > 
> > Thanks.
> > 
> > That appears to be missing a changelog stanza for the stable
> > upload. Is
> > that the only proposed difference from the 2.2.14-1 unstable
> > upload?
> > 

On Tue, 2017-09-26 at 04:45 +0200, Martin Zobel-Helas wrote:
> Yes

OK. Please feel free to upload a package built and tested on stretch
that matches the provided diff plus a changelog stanza for 2.2.14-
1~deb9u1 with a changelog distribution of "stretch".

Regards,

Adam

Bug#876194:

[A. Jesse Jiryu Davis]

forwarded https://jira.mongodb.org/browse/CDRIVER-2286

Bug#876909: stretch-pu: package samba/2:4.5.12+dfsg-2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2017-09-26 at 21:33 +0200, Mathieu Parent wrote:
> This upload will bring the same security changes than 2:4.5.8+dfsg-
> 2+deb9u2.
> 
> samba (2:4.5.12+dfsg-2) stretch; urgency=high
>   * This is a security release in order to address the following
> defects:
> - CVE-2017-12150: Some code path don't enforce smb signing, when
> they should
> - CVE-2017-12151: Keep required encryption across SMB3 dfs
> redirects
> - CVE-2017-12163: Server memory information leak over SMB1
> 

Please go ahead.

Regards,

Adam

Bug#876194: libbson-dev: Please install the cmake package config file

[A. Jesse Jiryu Davis]

forward: https://jira.mongodb.org/browse/CDRIVER-2286

Bug#876908: Is blcr completely useless?

[Adrian Bunk]

Source: blcr
Version: 0.8.5-2.1
Severity: serious
Tags: buster sid

As far as I can see:
1. blcr is dead upstream since 2013.
2. blcr requires both userspace and kernel parts.
3. The -dkms package is removed in unstable.
4. The beta version in experimental has an RC bug against
   the -dkms package that the module does not build
   with the jessie (sic) kernel.

mpich is linked with the userspace library,
but does that make any sense without the kernel part?

Bug#876789: [Freewx-maint] Bug#876789: python-wxgtk-webview3.0: Depends on libwxgtk-webview3.0-0v5 which depends on webkit1

[Olly Betts]

On Tue, Sep 26, 2017 at 08:24:06AM -0400, Scott Talbert wrote:
> 
> 
> On September 26, 2017 1:54:34 AM EDT, Olly Betts  wrote:
> >On Mon, Sep 25, 2017 at 10:37:34PM -0400, Scott Talbert wrote:
> >> I would think the person who was trying to use wx.html2 might not
> >> agree with that.
> >
> >"wx.html2" is actually how wxPython wraps webview:
> >
> >| I have put the wxPython verison of them in the wx.html2 module
> >| because the wxWebKit project already produces a wx.webview module for
> >| wxPython.
> >
> >So it's inevitable that wx.html2 is not going to work once webview is
> >disabled in wxWidgets.
> 
> I am fully aware of that.  I just think it would have been better to
> leave it until wxWebview was being removed.

That's imminent anyway.

And the original reporter of #821934 wasn't even using Debian!

Cheers,
Olly

Bug#876909: stretch-pu: package samba/2:4.5.12+dfsg-2

[Mathieu Parent]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

This upload will bring the same security changes than 2:4.5.8+dfsg-2+deb9u2.

samba (2:4.5.12+dfsg-2) stretch; urgency=high
  * This is a security release in order to address the following defects:
- CVE-2017-12150: Some code path don't enforce smb signing, when they should
- CVE-2017-12151: Keep required encryption across SMB3 dfs redirects
- CVE-2017-12163: Server memory information leak over SMB1

See attached debdiff.

Regards

Mathieu Parent

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

Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru samba-4.5.12+dfsg/debian/changelog samba-4.5.12+dfsg/debian/changelog
--- samba-4.5.12+dfsg/debian/changelog  2017-08-26 17:35:49.0 +0200
+++ samba-4.5.12+dfsg/debian/changelog  2017-09-25 15:19:34.0 +0200
@@ -1,3 +1,12 @@
+samba (2:4.5.12+dfsg-2) stretch; urgency=high
+
+  * This is a security release in order to address the following defects:
+- CVE-2017-12150: Some code path don't enforce smb signing, when they 
should
+- CVE-2017-12151: Keep required encryption across SMB3 dfs redirects
+- CVE-2017-12163: Server memory information leak over SMB1
+
+ -- Mathieu Parent   Mon, 25 Sep 2017 15:19:34 +0200
+
 samba (2:4.5.12+dfsg-1) stretch; urgency=medium
 
   * gbp.conf: change debian-branch to stretch
diff -Nru 
samba-4.5.12+dfsg/debian/patches/CVE-2017-12150-v4-5.patches.metze02.txt 
samba-4.5.12+dfsg/debian/patches/CVE-2017-12150-v4-5.patches.metze02.txt
--- samba-4.5.12+dfsg/debian/patches/CVE-2017-12150-v4-5.patches.metze02.txt
1970-01-01 01:00:00.0 +0100
+++ samba-4.5.12+dfsg/debian/patches/CVE-2017-12150-v4-5.patches.metze02.txt
2017-09-25 15:15:46.0 +0200
@@ -0,0 +1,234 @@
+From f14a94b5cd3e9977e8483e8a6ba06f48045edc15 Mon Sep 17 00:00:00 2001
+From: Stefan Metzmacher 
+Date: Thu, 3 Nov 2016 17:16:43 +0100
+Subject: [PATCH 1/6] CVE-2017-12150: s3:lib:
+ get_cmdline_auth_info_signing_state smb_encrypt SMB_SIGNING_REQUIRED
+
+This is an addition to the fixes for CVE-2015-5296.
+
+It applies to smb2mount -e, smbcacls -e and smbcquotas -e.
+
+BUG: https://bugzilla.samba.org/show_bug.cgi?id=12997
+
+Signed-off-by: Stefan Metzmacher 
+---
+ source3/lib/util_cmdline.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/source3/lib/util_cmdline.c b/source3/lib/util_cmdline.c
+index 80c3ecd..539fa55 100644
+--- a/source3/lib/util_cmdline.c
 b/source3/lib/util_cmdline.c
+@@ -123,6 +123,9 @@ bool set_cmdline_auth_info_signing_state(struct 
user_auth_info *auth_info,
+ 
+ int get_cmdline_auth_info_signing_state(const struct user_auth_info 
*auth_info)
+ {
++  if (auth_info->smb_encrypt) {
++  return SMB_SIGNING_REQUIRED;
++  }
+   return auth_info->signing_state;
+ }
+ 
+-- 
+1.9.1
+
+
+From f82c235484d03e22ad78a79e9cf2f14c8455df56 Mon Sep 17 00:00:00 2001
+From: Stefan Metzmacher 
+Date: Fri, 9 Dec 2016 09:26:32 +0100
+Subject: [PATCH 2/6] CVE-2017-12150: s3:pylibsmb: make use of
+ SMB_SIGNING_DEFAULT for 'samba.samba3.libsmb_samba_internal'
+
+BUG: https://bugzilla.samba.org/show_bug.cgi?id=12997
+
+Signed-off-by: Stefan Metzmacher 
+---
+ source3/libsmb/pylibsmb.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/source3/libsmb/pylibsmb.c b/source3/libsmb/pylibsmb.c
+index 0c5d7e9..97aa39e 100644
+--- a/source3/libsmb/pylibsmb.c
 b/source3/libsmb/pylibsmb.c
+@@ -447,7 +447,7 @@ static int py_cli_state_init(struct py_cli_state *self, 
PyObject *args,
+   cli_credentials_get_username(cli_creds),
+   cli_credentials_get_domain(cli_creds),
+   cli_credentials_get_password(cli_creds),
+-  0, 0);
++  0, SMB_SIGNING_DEFAULT);
+   if (!py_tevent_req_wait_exc(self->ev, req)) {
+   return -1;
+   }
+-- 
+1.9.1
+
+
+From 5d296e6ea32ca2df035dd35e6f21b82390f87f86 Mon Sep 17 00:00:00 2001
+From: Stefan Metzmacher 
+Date: Mon, 12 Dec 2016 05:49:46 +0100
+Subject: [PATCH 3/6] CVE-2017-12150: libgpo: make use of SMB_SIGNING_REQUIRED
+ in gpo_connect_server()
+
+It's important that we use a signed connection to get the GPOs!
+
+BUG: https://bugzilla.samba.org/show_bug.cgi?id=12997
+
+Signed-off-by: Stefan Metzmacher 
+---
+ libgpo/gpo_fetch.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/libgpo/gpo_fetch.c b/libgpo/gpo_fetch.c
+index 836bc23..3740d4e 100644
+--- a/libgpo/gpo_fetch.c
 b/libgpo/gpo_fetch.c
+@@ -133,7 +133,7 @@ static NTSTATUS 

Bug#876907: /usr/bin/plasmashell: System tray popups and application menu break when virtual desktops used

[mdmilosz]

Package: plasma-workspace
Version: 4:5.10.5-2
Severity: normal
File: /usr/bin/plasmashell

Dear Maintainer,

I have been encountering the following problem:

After opening one of the System Tray popups [1] and switching to another 
virtual desktop without closing the popup, the popup disappears and can't be 
opened again (the icon in the System Tray acts as if it worked, but the content 
isn't visible [2]). It affects the whole System Tray at once.

The same happens to the Application Menu, although independently. (It often 
ends up with broken System Tray and working Application Menu, or vice versa.)

Once `plasmashell` has been restarted, the System Tray and Application Menu 
resume to work normally.

I have a set up with multiple Virtual Desktops which can be changed using the 
mouse wheel, or by using the Pager widget on the panel. In both scenarios, the 
popup becomes inaccessible.

[1] https://i.imgur.com/8Y45Bn8.png
[2] https://i.imgur.com/Nen1Dbn.png


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages plasma-workspace depends on:
ii  dbus-x11 1.11.16+really1.10.24-1
ii  frameworkintegration 5.37.0-2
ii  gdb-minimal [gdb]7.12-6
ii  iso-codes3.76-1
ii  kactivitymanagerd5.10.5-2
ii  kde-cli-tools4:5.10.5-2
ii  kded55.37.0-2
ii  kinit5.37.0-2
ii  kio  5.37.0-2
ii  kpackagetool55.37.0-2
ii  kwin-common  4:5.8.7-2
ii  libappstreamqt2  0.11.5-1
ii  libc62.24-17
ii  libcln6  1.3.4-2+b1
ii  libgcc1  1:7.2.0-7
ii  libgps22 3.16-4
ii  libice6  2:1.0.9-2
ii  libkf5activities55.37.0-2
ii  libkf5auth5  5.37.0-2
ii  libkf5baloo5 5.37.0-2
ii  libkf5bookmarks5 5.37.0-2
ii  libkf5calendarevents55.37.0-2
ii  libkf5completion55.37.0-2
ii  libkf5configcore55.37.0-2
ii  libkf5configgui5 5.37.0-2
ii  libkf5configwidgets5 5.37.0-2
ii  libkf5coreaddons55.37.0-2
ii  libkf5crash5 5.37.0-2
ii  libkf5dbusaddons55.37.0-2
ii  libkf5declarative5   5.37.0-2
ii  libkf5globalaccel-bin5.37.0-2
ii  libkf5globalaccel5   5.37.0-2
ii  libkf5guiaddons5 5.37.0-2
ii  libkf5holidays5  16.04.2-1
ii  libkf5i18n5  5.37.0-2
ii  libkf5iconthemes55.37.0-2
ii  libkf5idletime5  5.37.0-2
ii  libkf5itemviews5 5.37.0-2
ii  libkf5jobwidgets55.37.0-2
ii  libkf5js55.37.0-2
ii  libkf5jsembed5   5.37.0-2
ii  libkf5kdelibs4support5   5.37.0-2
ii  libkf5kiocore5   5.37.0-2
ii  libkf5kiofilewidgets55.37.0-2
ii  libkf5kiowidgets55.37.0-2
ii  libkf5networkmanagerqt6  5.37.0-2
ii  libkf5newstuff5  5.37.0-2
ii  libkf5notifications5 5.37.0-2
ii  libkf5notifyconfig5  5.37.0-2
ii  libkf5package5   5.37.0-2
ii  libkf5plasma55.37.0-2
ii  libkf5plasmaquick5   5.37.0-2
ii  libkf5prison55.37.0-2
ii  libkf5quickaddons5   5.37.0-2
ii  libkf5runner55.37.0-2
ii  libkf5service-bin5.37.0-2
ii  libkf5service5   5.37.0-2
ii  libkf5solid5 5.37.0-2
ii  libkf5texteditor55.37.0-2+b1
ii  libkf5textwidgets5   5.37.0-2
ii  libkf5wallet-bin 5.37.0-2
ii  libkf5wallet55.37.0-2
ii  libkf5waylandclient5 4:5.37.0-2
ii  libkf5widgetsaddons5 5.37.0-2
ii  libkf5windowsystem5  5.37.0-2
ii  libkf5xmlgui5

Bug#790222: [boinc_dev] Bug#790222: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

[Olly Betts]

On Tue, Sep 26, 2017 at 08:05:57AM +, Gianfranco Costamagna wrote:
> >Gianfranco: Is there any progress on the boinc front?  If not, I think
> >we just need to do this rather than letting this removal drag on for
> >even longer.
> 
> so, the plan now is to remove boinc from testing?

Or stop it from using webview, e.g. by using wxHtmlWindow instead (as I
suggested months ago).

> what is the plan to fix it BTW? moving to the new webkitgtk and transition to
> gtk3?

I think that's the only way to get webview back, but we need people to
actually do the work to make that happen.  I'm not realistically able to
commit to doing a transition unaided at this point - initial
investigations showed that it's likely to shake out a significant number
of bugs in both wx's GTK+ 3 support and in apps themselves.  It's not
just a case of uploading and binNMUing all rdeps.

As things stand, the plan is probably that there's no webview for buster.

Cheers,
Olly