Bug#837495: closing 837495

[Tobias Frost]

close 837495 
thanks

Have been marked as fixed, but not yet closed.

--
tobi

Processed: closing 837495

[Debian Bug Tracking System]

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

> close 837495
Bug #837495 [src:gnome-shell-extension-suspend-button] 
gnome-shell-extension-suspend-button: uninstallable in sid: Depends: 
gnome-shell (< 3.21) but 3.21.91-2 is to be installed
Bug #837592 [src:gnome-shell-extension-suspend-button] 
gnome-shell-extension-suspend-button: Not compatible with gnome-shell 
3.21.x/3.22
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#836162: diversions for linkers need an update

[Kees Cook]

On Thu, Sep 01, 2016 at 05:17:06PM +0200, Moritz Muehlenhoff wrote:
> I think we should remove hardening-wrapper for the stretch release? 
> dpkg-buildflags/dh
> are around for a long time now and we're down to about 50 reverse 
> dependencies at
> this point. Plus, lintian marks it as deprecated for quite a while now.
> 
> Kees, what do you think?

Yeah, it (and hardening-includes) should get removed in favor of
the dpkg-buildflags method.  However, this means we need to move the
"hardening-check" script from hardening-includes to lintian, probably.

-Kees

-- 
Kees Cook@debian.org

Bug#837786: mutter: Issues repainting the display on mouse movement

[John M.]

I tried setting the "DRI" option to "false" (and to "2", as suggested
by ArchWiki), but the result is the same ---maybe due to the fact that
I also have a discrete display (Nvidia Optimus):

$ sudo lshw -c video
  *-display UNCLAIMED   
   description: VGA compatible controller
   product: GK208M [GeForce GT 730M]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:02:00.0
   version: a1
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress vga_controller cap_list
   configuration: latency=0
   resources: memory:f000-f0ff memory:c000-cfff
memory:d000-d1ff ioport:3000(size=128)
  *-display
   description: VGA compatible controller
   product: 4th Gen Core Processor Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 06
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:32 memory:f100-f13f memory:e000-
efff ioport:4000(size=64) memory:c-d


Or maybe it's something in my modprobe.d directory:

$ for file in `ls`; do echo -e "\n\n#$(pwd)/$file:" >>
/tmp/combined.txt; cat $file >> /tmp/combined.txt; done && cat
/tmp/combined.txt


#/etc/modprobe.d/amd64-microcode-blacklist.conf:
# The microcode module attempts to apply a microcode update when
# it autoloads.  This is not always safe, so we block it by default.
blacklist microcode


#/etc/modprobe.d/bumblebee.conf:
# This file is installed by bumblebee, do NOT edit!
# to be used by kmod / module-init-tools, and installed in
/etc/modprobe.d/
# or equivalent

# do not automatically load nouveau as it may prevent nvidia from
loading
blacklist nouveau
# do not automatically load nvidia as it's unloaded anyway when
bumblebeed
# starts and may fail bumblebeed to disable the card in a race
condition.
# Debian
blacklist nvidia
blacklist nvidia-current
blacklist nvidia-legacy-304xx
blacklist nvidia-legacy-340xx
# Ubuntu
blacklist nvidia
blacklist nvidia-current
blacklist nvidia-current-updates
# 304
blacklist nvidia-304
blacklist nvidia-304-updates
blacklist nvidia-experimental-304
# 310
blacklist nvidia-310
blacklist nvidia-310-updates
blacklist nvidia-experimental-310
# 313
blacklist nvidia-313
blacklist nvidia-313-updates
blacklist nvidia-experimental-313
# 319
blacklist nvidia-319
blacklist nvidia-319-updates
blacklist nvidia-experimental-319
# 325
blacklist nvidia-325
blacklist nvidia-325-updates
blacklist nvidia-experimental-325
# 331
blacklist nvidia-331
blacklist nvidia-331-updates
blacklist nvidia-experimental-331
# 334
blacklist nvidia-334
blacklist nvidia-334-updates
blacklist nvidia-experimental-334
# 337
blacklist nvidia-337
blacklist nvidia-337-updates
blacklist nvidia-experimental-337
# 340
blacklist nvidia-340
blacklist nvidia-340-updates
blacklist nvidia-experimental-340
# 343
blacklist nvidia-343
blacklist nvidia-343-updates
blacklist nvidia-experimental-343
# 346
blacklist nvidia-346
blacklist nvidia-346-updates
blacklist nvidia-experimental-346
# 349
blacklist nvidia-349
blacklist nvidia-349-updates
blacklist nvidia-experimental-349
# 352
blacklist nvidia-352
blacklist nvidia-352-updates
blacklist nvidia-experimental-352
# 355
blacklist nvidia-355
blacklist nvidia-355-updates
blacklist nvidia-experimental-355
# 358
blacklist nvidia-358
blacklist nvidia-358-updates
blacklist nvidia-experimental-358
# 361
blacklist nvidia-361
blacklist nvidia-361-updates
blacklist nvidia-experimental-361
# 364
blacklist nvidia-364
blacklist nvidia-364-updates
blacklist nvidia-experimental-364


#/etc/modprobe.d/dkms.conf:
# modprobe information used for DKMS modules
#
# This is a stub file, should be edited when needed,
# used by default by DKMS.


#/etc/modprobe.d/i915.conf:
options i915 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1



#/etc/modprobe.d/intel-microcode-blacklist.conf:
# The microcode module attempts to apply a microcode update when
# it autoloads.  This is not always safe, so we block it by default.
blacklist microcode


#/etc/modprobe.d/nvidia-blacklists-nouveau.conf:
# You need to run "update-initramfs -u" after editing this file.

# see #580894
blacklist nouveau


#/etc/modprobe.d/nvidia.conf:
install nvidia modprobe -i nvidia-current $CMDLINE_OPTS

install nvidia-modeset modprobe nvidia ; modprobe -i nvidia-current-
modeset $CMDLINE_OPTS

install nvidia-uvm modprobe nvidia ; modprobe -i nvidia-current-uvm
$CMDLINE_OPTS

remove nvidia modprobe -r -i nvidia-modeset nvidia-uvm nvidia

# These aliases are defined in *all* nvidia modules.
# Duplicating them here sets higher precedence and ensures the selected
# module gets loaded instead of a random first match if more than one
# version is installed. See #798207.
alias   pci:v10DEd0E00sv*sd*bc04sc80i00*nvidia
alias   

Processed: reassign 836947 to src:gnome-shell-extension-redshift, forcibly merging 837593 836947

[Debian Bug Tracking System]

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

> reassign 836947 src:gnome-shell-extension-redshift
Bug #836947 [gnome-shell-extension-redshift] gnome-shell-extension-redshift: 
uninstallable in sid
Bug reassigned from package 'gnome-shell-extension-redshift' to 
'src:gnome-shell-extension-redshift'.
No longer marked as found in versions gnome-shell-extension-redshift/3.20.1-1.
Ignoring request to alter fixed versions of bug #836947 to the same values 
previously set
> forcemerge 837593 836947
Bug #837593 [src:gnome-shell-extension-redshift] 
gnome-shell-extension-redshift: Not compatible with gnome-shell 3.21.x/3.22
Bug #836947 [src:gnome-shell-extension-redshift] 
gnome-shell-extension-redshift: uninstallable in sid
Marked as found in versions gnome-shell-extension-redshift/3.20.1-1.
Bug #837593 [src:gnome-shell-extension-redshift] 
gnome-shell-extension-redshift: Not compatible with gnome-shell 3.21.x/3.22
Added tag(s) sid.
Merged 836947 837593
> thanks
Stopping processing here.

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

Bug#834281: Bug#835770: Failure is triggered by fix to #834281

[Sunil Mohan Adapa]

On 09/15/2016 12:46 AM, Daniel Kahn Gillmor wrote:
[...]
> The fix for this problem, is to drop the workaround and correctly fix
> #834281, which i've done by sending patches to upstream's test suite at
> https://rt.cpan.org/Ticket/Display.html?id=102651 , and i aim to upload
> to debian shortly.

Thanks for the proper fix.

-- 
Sunil




signature.asc
Description: OpenPGP digital signature

Processed: Re: clementine: please backport 1.3.1 for jessie

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 834439
Bug #833671 [clementine] clementine: please backport 1.3.1 for jessie
833671 was blocked by: 827882 833620
833671 was not blocking any bugs.
Added blocking bug(s) of 833671: 834439

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

Bug#837123: [anna] segfault in wheezy installer

[Vincent McIntyre]

On Wed, Sep 14, 2016 at 09:01:20AM +0200, Aurelien Jarno wrote:
> > ...
> > warning: Can't read pathname for load map: Input/output error.
> > 
> > warning: Could not load shared library symbols for 4 libraries, e.g. 
> > /lib/libc.so.6.
> > Use the "info sharedlibrary" command to see the complete listing.
> > Do you need "set solib-search-path" or "set sysroot"?
> > Core was generated by `ping ftp.au.debian.org'.
> > Program terminated with signal 11, Segmentation fault.
> > #0  0x7f826609d0ca in ?? ()
> > (gdb) bt full
> > #0  0x7f826609d0ca in ?? ()
> > No symbol table info available.
> > #1  0x in ?? ()
> > No symbol table info available.
> > (gdb) q
> 
> Have you installed libc6-dbg on this wheezy machine? Anyway I am afraid
> that gdb is confused as the libc6 in debian-installer got some symbols
> removed...

I hadn't in the example above but it makes no difference if I have
libc6-dbg installed, the bt is the same.

Vince

Bug#836259: marked as done (gnupg2: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 22:22:55 +
with message-id 
and subject line Bug#836259: fixed in gnupg2 2.1.15-3
has caused the Debian Bug report #836259,
regarding gnupg2: accesses the internet during build
to be marked as done.

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

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


-- 
836259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnupg2
Version: 2.1.15-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst gnupg2 builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP 2144c8152453.52165 > 10.0.1.1.domain: 10277+ CERT? 
simon.josefsson.org. (37)
  00:00:02.091222 IP 10.0.1.1.domain > 2144c8152453.52165: 10277 ServFail 0/0/0 
(37)
  00:00:02.091449 IP 2144c8152453.33849 > 10.0.1.1.domain: 10277+ CERT? 
simon.josefsson.org. (37)
  00:00:04.189179 IP 10.0.1.1.domain > 2144c8152453.33849: 10277 ServFail 0/0/0 
(37)
  00:00:04.189389 IP 2144c8152453.43668 > 10.0.1.1.domain: 10277+ CERT? 
simon.josefsson.org. (37)
  00:00:06.327647 IP 10.0.1.1.domain > 2144c8152453.43668: 10277 ServFail 0/0/0 
(37)
  00:00:06.327842 IP 2144c8152453.51705 > 10.0.1.1.domain: 10277+ CERT? 
simon.josefsson.org. (37)
  00:00:08.373406 IP 10.0.1.1.domain > 2144c8152453.51705: 10277 ServFail 0/0/0 
(37)

  [..]

The full build log (including tcpdump output) is attached.


Regards,

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


gnupg2.2.1.15-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: gnupg2
Source-Version: 2.1.15-3

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

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

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated gnupg2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Sep 2016 17:08:58 -0400
Source: gnupg2
Binary: gnupg-agent scdaemon gpgsm gnupg gnupg2 gpgv gpgv2 dirmngr gpgv-udeb 
gpgv-win32 gnupg-l10n
Architecture: source
Version: 2.1.15-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers 
Changed-By: Daniel Kahn Gillmor 
Description:
 dirmngr- GNU privacy guard - network certificate management service
 gnupg  - GNU privacy guard - a free PGP replacement
 gnupg-agent - GNU privacy guard - cryptographic agent
 gnupg-l10n - GNU privacy guard - localization files
 gnupg2 - GNU privacy guard - a free PGP replacement (dummy transitional pa
 gpgsm  - GNU privacy guard - S/MIME version
 gpgv   - GNU privacy guard - signature verification tool
 gpgv-udeb  - minimal signature verification tool (udeb)
 gpgv-win32 - GNU privacy guard - signature verification tool (win32 build)
 gpgv2  - GNU privacy guard - signature verification tool (dummy transition
 scdaemon   - GNU privacy guard - smart card support
Closes: 836259
Changes:
 gnupg2 (2.1.15-3) unstable; urgency=medium
 .
   * Use upstream fix to avoid touching homedir during test suite
   * backward compatibility for preset-passphrase and protect-tool
   * add Breaks: for python3-apt too (thanks, Harald Jenny!)
   * Avoid network access during tests (Closes: #836259)
   * more patches from upstream
- gpgv --output now works
- fingerprint display doesn't vary with --keyid-format
- minor cleanup to scdaemon dealing with removed cards
Checksums-Sha1:
 ac5f86ca26fb3bea7762f57c9ea7482761f2046d 3191 gnupg2_2.1.15-3.dsc
 7d02d4ca69f12284ac0505f1944e4ca589641ebe 53648 gnupg2_2.1.15-3.debian.tar.bz2
Checksums-Sha256:
 873693e194498b03e3a6c984920b6c88779e9a121782bc3c0b51f99fde6812f0 3191 
gnupg2_2.1.15-3.dsc
 7870c91a2431a7db3bf64a865c8563630b4b5b0da52f42d694d930f554e704f1 53648 
gnupg2_2.1.15-3.debian.tar.bz2
Files:
 

Bug#837594: marked as done (gnome-shell-extension-autohidetopbar: Not compatible with gnome-shell 3.21.x/3.22)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 22:22:42 +
with message-id 
and subject line Bug#837594: fixed in gnome-shell-extension-autohidetopbar 
20160828-2
has caused the Debian Bug report #837594,
regarding gnome-shell-extension-autohidetopbar: Not compatible with gnome-shell 
3.21.x/3.22
to be marked as done.

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

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


-- 
837594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-extension-autohidetopbar
Version: 20160828-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-3-22

Hi,

your package gnome-shell-extension-autohidetopbar declares a strictly
versioned dependency on gnome-shell. We've uploaded gnome-shell
3.21.91 to unstable, which makes gnome-shell-extension-autohidetopbar
uninstallable.

Please test if your package is compatible with that version and
update the information in metadata.json and the package dependencies
accordingly.

There will be one more development release, 3.21.92, before the final
version 3.22.0 is released [1]. gnome-shell development is frozen, so
if gnome-shell-extension-autohidetopbar works with 3.21.91, it's
pretty safe to assume it will also work with 3.21.92 and 3.22. So you
might list those as supported versions as well

Regards, Michael

[1] https://wiki.gnome.org/ThreePointTwentyone
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-autohidetopbar
Source-Version: 20160828-2

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

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

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated 
gnome-shell-extension-autohidetopbar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 08:05:15 +0200
Source: gnome-shell-extension-autohidetopbar
Binary: gnome-shell-extension-autohidetopbar
Architecture: source
Version: 20160828-2
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gnome-shell-extension-autohidetopbar - GNOME shell automatic topbar hider
Closes: 837594
Changes:
 gnome-shell-extension-autohidetopbar (20160828-2) unstable; urgency=medium
 .
   * d/control: Relax upper version limit on gnome-shell. (Closes: #837594)
 As the next Gnome version will by default not enforce the version via
 metadata.json, a change in this file is not required. See the bug for
 details.
Checksums-Sha1:
 c9c03e85b95832719b3157c253db82b457d61082 2167 
gnome-shell-extension-autohidetopbar_20160828-2.dsc
 23be1e456f7cc97ffad3d7b8e77a4251539e28c4 4200 
gnome-shell-extension-autohidetopbar_20160828-2.debian.tar.xz
Checksums-Sha256:
 ad774d7cece0050cec93dc67ff4278036cfdad166d01eb7b165efd511267cab2 2167 
gnome-shell-extension-autohidetopbar_20160828-2.dsc
 478df49d3103d2d5c67e2a1a8936b5eeb49d85ef38391396fa852c263449c98c 4200 
gnome-shell-extension-autohidetopbar_20160828-2.debian.tar.xz
Files:
 f592f9cfaf7a05914415c21aa159937f 2167 gnome optional 
gnome-shell-extension-autohidetopbar_20160828-2.dsc
 027e545cff3d8db575f539b3eafa46f3 4200 gnome optional 
gnome-shell-extension-autohidetopbar_20160828-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX2OnBAAoJEJFk+h0XvV027N0QAIxbVM+TDAfO4Jb6ItxGXhgY
LPdeoYB1LpMgcjNhs1QLOaRt8jXcQKqoFhAtjRipdHsz9wVjaJLR2xRD7Zxkv2Vl
FhSMu/hN1VB3fB5bcb+AnaG3lFMFss99cDFenHTAbBqR6XRsv6+CyxyQCFA0tek1
4rZ50uf5i/Z92PCWsckZQKUu3BPDKoJuW4ksSgWChspiiCI0vP5uUtofwaXLeInx
ohWjYsBbDHIuBaluPc5vAxJTbfOn0elXFfP9DBIwgo1IHzkZ9XIpWLK50wceAlmT
KTGNN6ybc+0llYc4GOGcSQi/BssP2EhbtAElXi2P14AUIiG+LNs71JY0BtSfHoas
cWMT6Btk2VSxkEvRrVJGLkMRMZivx8ZPTPILlen+Y3lJPnFwB716cxYVPxD5MiuH
XajsZG+M2+PgNcZY1BAC976P4MmwxBOH6AWCNdKls+XDpd/FcgMA8+BCbBjr4qHb
03DS3+Q7Dr1Va8aJjx1if6aQpaGpd/lfxL66Hx7CHrnnhbRtMyqPacxWh5WGZjWL
b6SAmSOYuTYIgsMZSpM+BqY93lcWCg5IGZCkiydV9JEQ249glMwAbU61eLCp+OHi

Bug#834251: marked as done (openmw: FTBFS with GCC 6)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 22:24:55 +
with message-id 
and subject line Bug#834251: fixed in openmw 0.38.0-3
has caused the Debian Bug report #834251,
regarding openmw: FTBFS with GCC 6
to be marked as done.

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

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


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

Dear maintainer:

This package currently fails to build from source in stretch:

-
In file included from /usr/include/c++/6/unordered_map:35:0,
 from
/<>/components/files/configurationmanager.hpp:7,
 from
/<>/components/files/configurationmanager.cpp:1:
/usr/include/c++/6/bits/c++0x_warning.h:32:2: error: #error This file
requires compiler and library support for the ISO C++ 2011 standard.
This support must be enabled with the -std=c++11 or -std=gnu++11
compiler options.
 #error This file requires compiler and library support \
   ^
-

The full build log is attached.

(Note: The build log is for "dpkg-buildpackage -A" but that's probably
irrelevant considering the way it fails).

Thanks.

openmw_0.38.0-1_amd64-20160812-1532.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: openmw
Source-Version: 0.38.0-3

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

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

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

Debian distribution maintenance software
pp.
Bret Curtis  (supplier of updated openmw package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Sep 2016 08:14:09 +0200
Source: openmw
Binary: openmw openmw-cs openmw-data openmw-launcher
Architecture: source
Version: 0.38.0-3
Distribution: unstable
Urgency: low
Maintainer: Bret Curtis 
Changed-By: Bret Curtis 
Description:
 openmw - Reimplementation of The Elder Scrolls III: Morrowind
 openmw-cs  - Replacement of The Elder Scrolls Construction Set
 openmw-data - Resources for the OpenMW engine
 openmw-launcher - Launcher for OpenMW using the Qt-Gui-Toolkit
Closes: 834251
Changes:
 openmw (0.38.0-3) unstable; urgency=low
 .
   [ Bret Curtis ]
   * Added patch to replace unordered_map with map (Closes: #834251)
 .
 openmw (0.38.0-2) unstable; urgency=low
 .
   [ Bret Curtis ]
   * Updated Standards-Version
   * Removed unnecessary depends.
Checksums-Sha1:
 b4d34ea73caad14f3663ec5a16277fdf71352a68 2305 openmw_0.38.0-3.dsc
 cde667451c4fd298f35b524dcd788ceb2c2a26b3 8048 openmw_0.38.0-3.debian.tar.xz
Checksums-Sha256:
 d9451071e9fa5973d3212af8cdac9c89c35c52bef71ac0cc3935c1b75b1fed4c 2305 
openmw_0.38.0-3.dsc
 1665a93a3cef6a8d08ddcb80005d0e5cc4e0ca647f98c350868ea51c622824de 8048 
openmw_0.38.0-3.debian.tar.xz
Files:
 dea6c486fc4e1fa35114bbb790599402 2305 contrib/games optional 
openmw_0.38.0-3.dsc
 fd884e0022a4071f4bd3360065bd2d6c 8048 contrib/games optional 
openmw_0.38.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJX2bIVAAoJEK/P7I5mnOHCSnQP/i/i8422VZyhODZBt9pwEjFJ
nSUYW19mnPzUkirpS86X2UHiXz4idU4U2Sa2OLNjbg/gcvgVhyXPLTsgh3myjP+J
CqiTS53bLPzei8oSpSdSoJfUNzuvXqj6QyXkum/Z5bFcZuFRoPLhZWVtlX1AfTva
S9BjSRhDKRZmxqt7H11sPfJvh03vMm6yD7JHo4uHmFESQ0cjbUzxY7kXMJHAzPxl
2Ru9tMSNBTApEEwd6TQI1lxyY1nFmB1wkR6puKFUWyLeTQC6tR9XgOn3MnF/ZMRC
2jXv/PCQcFdBCNy4dsBK77poLRl6RUzI5xNihVDT1aRWwm32KtryuJmkl6CklvqP
+2SPjMc6IpseHUW5Ip2jf0TW6bC9ujfHnVwrjdRs4gMbxq7Wtmz3dClahkjvyLJ+
wqh85MW+ITeF31rfdgeiJtfmI0c6fS7kcJ0Vur14Yw4jfi+Haon43Y9fL8FOlrXO
rPoJHYvIQGbZ6IJs5n1+fwUKFadFmTDucyUVHZdPFrueEpja4Sh98HPTb0n9dfX3
y8gxXXJvcDOYxDLv4YC+mmUWQbzBOKn5UTKzpMHRmLBp378SsiKdlXOk1rqYDZKp
7HGTSVFr5rW+LjmtsuVE7yZ+l0S12IFdBRLdWN8pkVa3OtmmSEFMRlxEyuIs22U0
09Wp9KIYR04syHCnAgsO
=KnTk
-END PGP SIGNATURE End Message ---

Bug#837700: gnutls: GNUTLS segfaults on initialization

[J Phelps]

>Can you provide a (simple) way to reproduce the issue?

Reproduction was simple on my machine: Just try to run Chromium 53.0.2785.92,
which depends on libgnutls30. It crashed immediately.

I had just upgraded from a much older version of Chromium (in the 30s IIRC)
using Aptitude.

Running it under GDB showed that the segfault happened in Nettle.

>Your diagnosis cannot be completely correct. e.g. libgnutls30
>3.5.4-2 on i386 (which you reported the issue against) was built against
>nettle-dev i386 3.2-1 which continues to be the latest version of nettle
>available in Debian. So you cannot experience a breakage in Debian
>caused by the Debian-installed nettle version being newer and having a
>different ABI than the version GnuTLS was built against.

I think that the binary in the .deb package was compiled from a different
Nettle source than the one that you find in the corresponding .dsc package.
Otherwise, compiling the .dsc package should have given me a binary that was
compatible with the one that was already installed on my system.

Instead, I had unresolved symbols (I don't remember which ones), and I had
to go to Nettle's Git repository (https://git.lysator.liu.se/nettle/nettle)
to find source code that could produce a linkable library. The symbols
that were unresolved were only found in the "ecc-support" branch of that
repo. Compiling from the trunk led to the same symbols being unresolved.

The recompiled library produced the same crash as the original binary. The
diagnosis was done with the Git version of Nettle and the .dsc version of
libgnutls.

Bug#837759: network configuration stops working reliably

[Wolfgang Walter]

On Wednesday, 14 September 2016 10:00:28 CEST Felipe Sateler wrote:
> Control: tags -1 moreinfo
> 
> On 14 September 2016 at 06:59, Wolfgang Walter  
> wrote:
> > Package: systemd
> > Version: 231-6
> > Severity: grave
> > 
> > Starting with version 231-6 the configuration of network interfaces stops
> > working reliably when rebooting a system. Downgrading to 231-5 fixes the
> > problem.
> > 
> > Symptoms: If a network interface is configured using
> > /etc/network/interfaces it seems that systemd now sometimes removes the
> > configured ip4 and/or ipv6 addresses in the boot process. It also seems
> > to remove routes of network interfaces configured manually or with
> > /etc/network/interfaces if the link state changes.
> > 
> > This seems not only be the case with interfaces configured via
> > /etc/network/ interfaces but with any interface one creates and assigns
> > ip addresses manually.
> > 
> > I tested this with a script:
> > 
> > #!/bin/sh
> > if [ "$1" = start ]; then
> > ip link del TEST >/dev/null 2>&1 || true
> > ip link add name TEST type dummy
> > ip -b - <<"EOF"
> > link set TEST up
> > addr add 10.10.10.10/32 dev TEST nodad
> > addr add 2a01:1:1:1::1/128 dev TEST nodad
> > addr add 2a01:1:1:1::2/128 dev TEST nodad
> > addr add 2a01:1:1:1::3/128 dev TEST nodad
> > addr add 2a01:1:1:1::4/128 dev TEST nodad
> > addr add 2a01:1:1:1::5/128 dev TEST nodad
> > EOF
> > ip addr ls TEST
> > sleep 2
> > elif [ "$1" = stop ]; then
> > ip addr flush dev TEST
> > ip link del TEST
> > fi
> > 
> > which I start with as a systemd oneshot service with
> > 
> > Before=systemd-networkd.service
> > 
> > I can see in the journal that TEST has all adresses assigned but with
> > 231-6 it looses them again (probably when systemd-networkd.service
> > starts). With 231-5 or earlier this in not the case.
> 
> It appears you are using systemd-networkd. Could you please attach
> your networkd configuration?
> 
> Version 231-6 is built with iptables support, so that may be causing
> an interaction that was not visible before.

I think this is the problem:

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=debian/231-6=79e10aaee1cdd412bd42f13f26e558ba1cd2196b

I suppose is that the check for LINK_STATE_UNMANAGED may be racy. The interface 
may go down and up before LINK_STATE_UNMANAGED is set. Maybe the state is 
LINK_STATE_PENDING ?

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

Bug#836259: marked as pending

[Daniel Kahn Gillmor]

tag 836259 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-gnupg/gnupg2.git;a=commitdiff;h=fd9652f

---
commit fd9652f346c7687b360273a4bf67522cc2295081
Author: Daniel Kahn Gillmor 
Date:   Wed Sep 14 17:15:56 2016 -0400

prepare new release

diff --git a/debian/changelog b/debian/changelog
index 2fc38f5..dd29f27 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+gnupg2 (2.1.15-3) unstable; urgency=medium
+
+  * Use upstream fix to avoid touching homedir during test suite
+  * backward compatibility for preset-passphrase and protect-tool
+  * add Breaks: for python3-apt too (thanks, Harald Jenny!)
+  * Avoid network access during tests (Closes: #836259)
+  * more patches from upstream
+   - gpgv --output now works
+   - fingerprint display doesn't vary with --keyid-format
+   - minor cleanup to scdaemon dealing with removed cards
+
+ -- Daniel Kahn Gillmor   Wed, 14 Sep 2016 17:08:58 
-0400
+
 gnupg2 (2.1.15-2) unstable; urgency=medium
 
   * restore keyid output in gpgv (Closes: #836144)

Processed: Bug#836259 marked as pending

[Debian Bug Tracking System]

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

> tag 836259 pending
Bug #836259 [src:gnupg2] gnupg2: accesses the internet during build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837591:

[Neil Muller]

Control: severity -1 minor


Removing support for user deletion was specifically asked for when the
package was adopted into PAPT. I also don't see any compelling reason
to re-add it from policy, so I'm downgrading this bug.

If there are files being left after the package is purged, please
provide details.

Processed: affects 835711

[Debian Bug Tracking System]

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

> affects 835711 + gnupg2
Bug #835711 {Done: gregor herrmann } 
[src:libconfig-identity-perl] libconfig-identity-perl: FTBFS: Tests failures
Added indication that 835711 affects gnupg2
> thanks
Stopping processing here.

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

Processed:

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #837591 [irker] leaves user (and files?) behind on purge
Severity set to 'minor' from 'serious'

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

Bug#837325: (no subject)

[Breno Leitao]

Thanks Andreas,

I am preparing a new version for cappuccino to solve this issue.

Bug#809832: marked as done (base: fails to inser modules ext2 or ext3)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 22:46:15 +0200 (CEST)
with message-id 
and subject line Re: base: fails to inser modules ext2 or ext3
has caused the Debian Bug report #809832,
regarding base: fails to inser modules ext2 or ext3
to be marked as done.

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

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


-- 
809832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base
Severity: critical
Justification: breaks unrelated software

# LANG=C mount -o ro /dev/sdc1 /mnt/disk/
mount: unknown filesystem type 'ext2'

# modprobe -vv ext2
insmod /lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko
libkmod: INFO ../libkmod/libkmod-module.c:829 kmod_module_insert_module: Failed
to insert module '/lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko': No such
file or directory
ERROR: could not insert 'ext2': Unknown symbol in module, or unknown parameter
(see dmesg)
libkmod: INFO ../libkmod/libkmod.c:319 kmod_unref: context 0x7fa6136ae210
released

/var/log/kern.log:
Jan  4 11:19:50 dbdev kernel: [1561590.271996] ext2: Unknown symbol __bread_gfp
(err 0)
Jan  4 11:19:50 dbdev kernel: [1561590.272039] ext2: Unknown symbol
__getblk_gfp (err 0)



-- System Information:
Debian Release: 7.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Hello.

[ Sorry for all the time you waited before receiving a reply, there are
  not many people answering to bugs in "base", and we really prefer bugs
  about real packages and not this "base" pseudo-package ].

On Mon, 4 Jan 2016, Mario Pereyra wrote:

> Package: base
> Severity: critical
> Justification: breaks unrelated software
> 
> # LANG=C mount -o ro /dev/sdc1 /mnt/disk/
> mount: unknown filesystem type 'ext2'
> 
> # modprobe -vv ext2
> insmod /lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko
> libkmod: INFO ../libkmod/libkmod-module.c:829 kmod_module_insert_module: 
> Failed
> to insert module '/lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko': No such
> file or directory

The error message itself explains why it can't load the ext2 module:

It can't because the file /lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko
does not seem to exist.

This file was in the linux-image-3.2.0-4-amd64 package in Debian 7:

$ dpkg -c linux-image-3.2.0-4-amd64_3.2.78-1_amd64.deb | grep ext2
drwxr-xr-x root/root 0 2016-03-09 05:25 
./lib/modules/3.2.0-4-amd64/kernel/fs/ext2/
-rw-r--r-- root/root103568 2016-03-09 05:25 
./lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko

Why the file was not there in your system?

We will probably never know with the information provided in the bug.

So, we are sorry but even if this was a real bug that we could fix,
we would not even know where to start for lack of information.

In Debian 8, there is not even ext2/ext3 independent modules by default,
as the same ext4 module is able to mount ext2, ext3 and ext4 partitions,
so in some sense, we can consider this to be fixed in Debian 8.

Thanks.--- End Message ---

Bug#837591:

[Tobias Frost]

Actually, whether deleting a user on purge or not is disputed.
https://wiki.debian.org/AccountHandlingInMaintainerScripts

(I wouldn't say this is RC, but I let the maintainer decide if it
should be downgraded)


--
tobi

Processed: notfound 822104 in 0.56

[Debian Bug Tracking System]

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

> notfound 822104 0.56
Bug #822104 {Done: Reiner Herrmann } [src:guessnet] 
guessnet: FTBFS: *** libiw not found. Check 'config.log' for more details.
No longer marked as found in versions guessnet/0.56.
> thanks
Stopping processing here.

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

Bug#822104: marked as done (guessnet: FTBFS: *** libiw not found. Check 'config.log' for more details.)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 22:21:25 +0200
with message-id <20160914202124.gc5...@reiner-h.de>
and subject line Re: guessnet: FTBFS: *** libiw not found. Check 'config.log' 
for more details.
has caused the Debian Bug report #822104,
regarding guessnet: FTBFS: *** libiw not found. Check 'config.log' for more 
details.
to be marked as done.

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

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


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

Dear Maintainer,

guessnet fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'guessnet-build-deps' in 
'../guessnet-build-deps_0.56_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package guessnet-build-deps.
  (Reading database ... 22998 files and directories currently installed.)
  Preparing to unpack guessnet-build-deps_0.56_all.deb ...
  Unpacking guessnet-build-deps (0.56) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
cdbs dh-buildinfo libiw-dev libiw30 libnet1 libnet1-dev libpcap-dev
libpcap0.8 libpcap0.8-dev libtut-dev libwibble-dev pkgconf
  Suggested packages:
pkg-config
  The following NEW packages will be installed:
cdbs dh-buildinfo libiw-dev libiw30 libnet1 libnet1-dev libpcap-dev
libpcap0.8 libpcap0.8-dev libtut-dev libwibble-dev pkgconf
  0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 1831 kB of archives.
  After this operation, 18.4 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 cdbs all 0.4.130 
[76.4 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 dh-buildinfo all 
0.11+nmu1 [18.1 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libnet1 amd64 
1.1.6+dfsg-3 [60.4 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libnet1-dev amd64 
1.1.6+dfsg-3 [118 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libpcap0.8 amd64 
1.7.4-2 [136 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libpcap0.8-dev amd64 
1.7.4-2 [233 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libpcap-dev all 
1.7.4-2 [24.0 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 libtut-dev all 
0.0.20070706-1 [99.2 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 libwibble-dev amd64 
1.1-1+b1 [977 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 pkgconf amd64 
0.9.12-1 [29.5 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 libiw30 amd64 
30~pre9-9 [21.2 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 libiw-dev amd64 
30~pre9-9 [38.8 kB]
  Fetched 1831 kB in 0s (85.0 MB/s)
  Selecting previously unselected package cdbs.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23002 files and directories currently installed.)
  Preparing to unpack .../archives/cdbs_0.4.130_all.deb ...
  Unpacking cdbs (0.4.130) ...
  Selecting previously unselected package dh-buildinfo.
  Preparing to unpack .../dh-buildinfo_0.11+nmu1_all.deb ...
  Unpacking dh-buildinfo (0.11+nmu1) ...
  Selecting previously unselected package libnet1:amd64.
  Preparing to unpack .../libnet1_1.1.6+dfsg-3_amd64.deb ...
  Unpacking libnet1:amd64 (1.1.6+dfsg-3) ...
  Selecting previously unselected package libnet1-dev.
  Preparing to unpack 

Processed: Re: vim-youcompleteme: Missing python dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #837646 [vim-youcompleteme] vim-youcompleteme: Missing python dependencies
Severity set to 'serious' from 'important'
> tags -1 patch
Bug #837646 [vim-youcompleteme] vim-youcompleteme: Missing python dependencies
Added tag(s) patch.

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

Bug#834281: Bug#835770: Failure is triggered by fix to #834281

[Daniel Kahn Gillmor]

Control: reassign 835770 libgnupg-interface-perl 0.52-3

Hi all--

On Wed 2016-09-14 04:17:21 -0400, Sunil Mohan Adapa wrote:

> Recently test cases where failing in libgnupg-interface-perl
> (https://bugs.debian.org/834281) due to gpg binary now defaulting to
> gpg2 in Debian. It was patched to explicitly use 'gpg1' binary instead
> of 'gpg'.  This is causing the test suite and monkeysphere to use
> different gpg binaries leading to test case failure.

I think Sunil's diagnosis is correct.  gpg1 and gpg in debian unstable
work on different keyrings by default and mixing the two is bound for
trouble.

So the temporary workaround for #834281 is actually causing the failures
in #835770, where everything is expected to use gpg itself.

The fix for this problem, is to drop the workaround and correctly fix
#834281, which i've done by sending patches to upstream's test suite at
https://rt.cpan.org/Ticket/Display.html?id=102651 , and i aim to upload
to debian shortly.

> One solution could be to patch the test suite in Debian to use gpg1
> instead of gpg until monkeysphere and libgnupg-interface-perl support
> gpg2.

I'm really hoping to avoid this kind of thing.  let's try to reduce the
dependencies on packages built from src:gnupg1, not extend them.

 --dkg


signature.asc
Description: PGP signature

Processed: Re: Bug#835770: Failure is triggered by fix to #834281

[Debian Bug Tracking System]

Processing control commands:

> reassign 835770 libgnupg-interface-perl 0.52-3
Bug #835770 [src:mod-gnutls] mod-gnutls: FTBFS: Tests failures
Bug reassigned from package 'src:mod-gnutls' to 'libgnupg-interface-perl'.
No longer marked as found in versions mod-gnutls/0.7.5-2.
Ignoring request to alter fixed versions of bug #835770 to the same values 
previously set
Bug #835770 [libgnupg-interface-perl] mod-gnutls: FTBFS: Tests failures
Marked as found in versions libgnupg-interface-perl/0.52-3.

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

Processed: Re: Bug#835770: Failure is triggered by fix to #834281

[Debian Bug Tracking System]

Processing control commands:

> reassign 835770 libgnupg-interface-perl 0.52-3
Bug #835770 [libgnupg-interface-perl] mod-gnutls: FTBFS: Tests failures
Ignoring request to reassign bug #835770 to the same package
Bug #835770 [libgnupg-interface-perl] mod-gnutls: FTBFS: Tests failures
Ignoring request to alter found versions of bug #835770 to the same values 
previously set

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

Bug#837797: Brain Fart

[Greg Flynn]

Sorry, everywhere I wrote "America/Eastern" was me having a brain
deficiency, I meant "America/New_York"

Sorry, I've updated my gist

Bug#834281: [rt.cpan.org #102651] patches to fix the GnuPG::Interface test suite to work with GnuPG 2.1

[Daniel Kahn Gillmor]

On Wed 2016-09-14 13:26:40 -0400, Daniel Kahn Gillmor wrote:
> Attached is a series of 7 patches that let the GnuPG::Interface test
> suite work with GnuPG 2.1.
>
> These patches can also be found on the improve-test-suite branch at
> git://lair.fifthhorseman.net/~dkg/gnupg-interface (commit ID
> f5ca0742dd1f724de1765679b493d4cfb7ea216b).

Sorry: i've made minor corrections to patch 6 to avoid breakage when it
was built in a new location.  The newly-revised patch is attached.

I've also force-pushed these changes to my improve-test-suite branch,
and the correct git commit ID is now:
d831296e0c18f0f9dba8e63193f5457792744f88.

Regards,

--dkg

From 9e4f77faaca087de35101b5d414180aaad9a709f Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor 
Date: Tue, 13 Sep 2016 14:46:13 -0400
Subject: [PATCH 6/7] test suite:  match plaintext output across versions of
 GnuPG

The human-readable version of --list-keys is *not* expected to be
static over time or as the user's environment changes (e.g. LANG or
LC_MESSAGES), so expecting it to be machine-parseable is probably a
mistake.

That said, some users might want to pull textual information about
specific keys to display directly to the user, so it's not a terrible
idea to have it in the test suite.

Modern GnuPG (2.1 or later) changes the default structure of the
human-readable output in a few significant ways:

 * it writes the path to the keyring as an absolute path, even if
   $GNUPGHOME is set to a non-absolute path.

 * it shows the calculated user id validity by default (see
   show-uid-validity in gpg's --list-options).  (note that this is a
   translated string, so that "unknown" (in the default C locale)
   becomes "inconnue" when LANG or LC_MESSAGES is set to fr_CH.UTF-8,
   for example.

 * it writes the key algorithm names differently (e.g. rsa2048 instead
   of 2048R)

 * it does not display the key ID at all by default

 * it displays the full fingerprint in compact form by default

This changeset fixes the test suite so that it can do a rough
verification of the human-readable text output by list_secret_keys in
the C locale in modern versions of GnuPG, while leaving it working for
older GnuPG suites.
---
 t/list_secret_keys.t   | 15 +--
 test/secret-keys/1.modern.test |  8 
 2 files changed, 21 insertions(+), 2 deletions(-)
 create mode 100644 test/secret-keys/1.modern.test

diff --git a/t/list_secret_keys.t b/t/list_secret_keys.t
index 1fe9b7e..51e3651 100644
--- a/t/list_secret_keys.t
+++ b/t/list_secret_keys.t
@@ -16,13 +16,22 @@ TEST
 {
 reset_handles();
 
+$ENV{LC_MESSAGES} = 'C';
 my $pid = $gnupg->list_secret_keys( handles => $handles );
 close $stdin;
 
 $outfile = 'test/secret-keys/1.out';
 my $out = IO::File->new( "> $outfile" )
   or die "cannot open $outfile for writing: $ERRNO";
-$out->print( <$stdout> );
+while (<$stdout>) {
+  if ($gpg_is_modern && /^\/.*\/test\/gnupghome\/pubring.kbx$/) {
+$out->print("test/gnupghome/pubring.kbx\n");
+  } elsif ($gpg_is_modern && /^--*$/) {
+$out->print("--\n");
+  } else {
+$out->print( $_ );
+  }
+}
 close $stdout;
 $out->close();
 waitpid $pid, 0;
@@ -33,7 +42,9 @@ TEST
 
 TEST
 {
-my @files_to_test = ( 'test/secret-keys/1.0.test' );
+my $suffix = '0';
+$suffix = 'modern' if ($gpg_is_modern);
+my @files_to_test = ( 'test/secret-keys/1.'.$suffix.'.test' );
 
 return file_match( $outfile, @files_to_test );
 };
diff --git a/test/secret-keys/1.modern.test b/test/secret-keys/1.modern.test
new file mode 100644
index 000..3e46407
--- /dev/null
+++ b/test/secret-keys/1.modern.test
@@ -0,0 +1,8 @@
+test/gnupghome/pubring.kbx
+--
+sec   dsa1024 2000-02-06 [SCA]
+  93AFC4B1B0288A104996B44253AE596EF950DA9C
+uid   [ unknown] GnuPG test key (for testing purposes only)
+uid   [ unknown] Foo Bar (1)
+ssb   elg768 2000-02-06 [E]
+
-- 
2.9.3



signature.asc
Description: PGP signature

Bug#825524: marked as done (liblexical-underscore-perl: FTBFS with Perl 5.24: Can't use global $_ in "my")

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 18:19:21 +
with message-id 
and subject line Bug#825524: fixed in liblexical-underscore-perl 0.003-2
has caused the Debian Bug report #825524,
regarding liblexical-underscore-perl: FTBFS with Perl 5.24: Can't use global $_ 
in "my"
to be marked as done.

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

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


-- 
825524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblexical-underscore-perl
Version: 0.003-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=108203

This package fails to build with Perl 5.24 (currently in experimental.)

  Can't use global $_ in "my" at t/01basic.t line 12, near "my $_ "
  Can't use global $_ in "my" at t/01basic.t line 23, near "my $_ "
  Can't use global $_ in "my" at t/01basic.t line 28, near "my $_ "
  Execution of t/01basic.t aborted due to compilation errors.
  # Looks like your test exited with 255 before it could output anything.
 
Quoting perldelta.pod:

  Lexical $_ has been removed
"my $_" was introduced in Perl 5.10, and subsequently caused
much confusion with no obvious solution. In Perl 5.18.0, it was
made experimental on the theory that it would either be removed or
redesigned in a less confusing (but backward-incompatible) way. Over
the following years, no alternatives were proposed. The feature has
now been removed and will fail to compile.

A full build log is available at
  
http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/liblexical-underscore-perl_0.003-1/

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: liblexical-underscore-perl
Source-Version: 0.003-2

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated 
liblexical-underscore-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 19:55:14 +0200
Source: liblexical-underscore-perl
Binary: liblexical-underscore-perl
Architecture: source
Version: 0.003-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Jonas Smedegaard 
Description:
 liblexical-underscore-perl - access your caller's lexical underscore
Closes: 825524
Changes:
 liblexical-underscore-perl (0.003-2) unstable; urgency=medium
 .
   * Update watch file:
 + Bump to version 4.
 + Use only MetaCPAN URL.
 + Mention gpb in usage comment.
   * Stop track upstream source with CDBS (use gpb --uscan).
   * Modernize git-buildpackage config: Filter any .git* file.
   * Declare compliance with Debian Policy 3.9.8.
   * Modernize Vcs-Git field: Use https protocol URL.
   * Bump debhelper compatibility level to 9.
   * Add lintian override regarding debhelper 9.
   * Update copyright info:
 + Use License-Grant and License-Reference fields. Thanks to Ben Finney.
 + Extend coverage of packaging to include current year.
   * Add lintian override regarding license in License-Reference field.
 See bug#786450.
   * Add patch 1001 to avoid lexical underscore.
 Closes: Bug#825524. Thanks to Niko Tyni.
   * Build-depend on licensecheck (not devscripts).
Checksums-Sha1:
 64fef146cfa6e00e124ce0eab1b2106e9a733ca9 2150 
liblexical-underscore-perl_0.003-2.dsc
 06dca2c74620b13aed8e9f43fa71da2202f77e57 4548 
liblexical-underscore-perl_0.003-2.debian.tar.xz
Checksums-Sha256:
 44728e56a33ee6c67a4d696151f3158d6322e00dc42a25e1c75ebb8d080b43c5 2150 
liblexical-underscore-perl_0.003-2.dsc
 a9e8de954251c233d8b920a95c0368d23802f15cdcce1f1869bf3582cb6ff251 4548 
liblexical-underscore-perl_0.003-2.debian.tar.xz
Files:
 9747af81f96caf4878f1d540d81f100e 2150 perl optional 
liblexical-underscore-perl_0.003-2.dsc
 9766195ecbc197be1f21412db073556c 4548 perl optional 

Bug#832291: marked as done (bogofilter-{bdb, sqlite, tokyocabinet}: copyright file missing after upgrade (policy 12.5))

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 18:18:41 +
with message-id 
and subject line Bug#832291: fixed in bogofilter 1.2.4+dfsg1-8
has caused the Debian Bug report #832291,
regarding bogofilter-{bdb, sqlite, tokyocabinet}: copyright file missing after 
upgrade (policy 12.5)
to be marked as done.

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

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


-- 
832291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bogofilter-bdb,bogofilter-sqlite,bogofilter-tokyocabinet
Version: 1.2.4+dfsg1-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

jessie -> stretch

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

1m18.5s ERROR: WARN: Inadequate results from running adequate!
  bogofilter-bdb: missing-copyright-file /usr/share/doc/bogofilter-bdb/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/bogofilter-bdb/copyright
  # ls -lad /usr/share/doc/bogofilter-bdb
  drwxr-xr-x 2 root root 40 Jun 10 11:52 /usr/share/doc/bogofilter-bdb
  # ls -la /usr/share/doc/bogofilter-bdb/
  total 0
  drwxr-xr-x   2 root root   40 Jun 10 11:52 .
  drwxr-xr-x 109 root root 2300 Jun 10 11:52 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


bogofilter-bdb_1.2.4+dfsg1-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bogofilter
Source-Version: 1.2.4+dfsg1-8

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

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

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

Debian distribution maintenance software
pp.
Herbert Parentes Fortes Neto  (supplier of updated bogofilter 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 14:39:50 -0300
Source: bogofilter
Binary: bogofilter bogofilter-bdb bogofilter-sqlite bogofilter-tokyocabinet 
bogofilter-common
Architecture: source amd64 all
Version: 1.2.4+dfsg1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Herbert Parentes Fortes Neto 
Description:
 bogofilter - fast Bayesian spam filter (dummy package)
 bogofilter-bdb - fast Bayesian spam filter (Berkeley DB)
 bogofilter-common - fast Bayesian spam filter (common files)
 bogofilter-sqlite - fast Bayesian spam filter (sqlite)
 bogofilter-tokyocabinet - fast Bayesian spam filter (tokyocabinet)
Closes: 832291
Changes:
 bogofilter (1.2.4+dfsg1-8) unstable; urgency=medium
 .
   * QA upload.
   * debian/*.preinst:
   - using dpkg-maintscript-helper. So the file's suffix is .maintscript 
now.
 Packages affected:
   bogofilter and bogofilter-{bdb, sqlite, tokyocabinet}
 Option used: dir_to_symlink
 (Closes: #832291) Thanks Andreas Beckmann and James Cowgill.
Checksums-Sha1:
 7d921c7b1bda1ddb32d06449dbcd3f3f82bdc5e5 2260 bogofilter_1.2.4+dfsg1-8.dsc
 45df2c9dba228dcd73a6f49bbcdb993412a2cb87 18952 
bogofilter_1.2.4+dfsg1-8.debian.tar.xz
 29e460f0b2b66ce96b42b284854edf75e90a6cf7 1076184 
bogofilter-bdb-dbgsym_1.2.4+dfsg1-8_amd64.deb
 c63018c3bb7ea2ef01005d69959e9a4996092694 135494 

Bug#837797: tzdata: America/Eastern reports Local Mean Time by default instead of EST

[Greg Flynn]

Package: tzdata
Version: 2016f-1
Severity: critical
Tags: newcomer
Justification: breaks unrelated software

Dear Maintainer,

   * What led up to the situation?
Running unit tests in Python while set timezone using the string
'America/Eastern'.
The offset was reported as UTC-4.9333 which resulted in
a discrepency of about 4 minutes
When running the same test on a server running Debian 8.5 with tzdata
2016f-0+deb8u1 the same test passed
   * What exactly did you do (or not do) that was effective (or ineffective)?
Changing timezone to 'EST' fixed the particular test and gave the
expected -5 offset for Standard time, but I think EST and America/Eastern
should be returning the same value
   * What was the outcome of this action?
I was sad
   * What outcome did you expect instead?
-5 offset instead of -4.9333...

https://en.wikipedia.org/wiki/Local_mean_time

Here's a gist with an example:
https://gist.github.com/gregflynn/2ac90ee0c39568f2e45f33ade476df51



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

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

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.59

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
  tzdata/Zones/Antarctica:
  tzdata/Zones/Europe:
  tzdata/Zones/Australia:
* tzdata/Zones/America: New_York
  tzdata/Zones/Atlantic:
* tzdata/Zones/Etc: UTC
  tzdata/Zones/Pacific:
  tzdata/Zones/Africa:
  tzdata/Zones/Asia:
  tzdata/Zones/Arctic:
  tzdata/Zones/Indian:
* tzdata/Areas: America
  tzdata/Zones/US:
  tzdata/Zones/SystemV:

Bug#825762: marked as done (libtext-sprintfn-perl: FTBFS with Perl 5.24: t/01-basics.t failure)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 17:51:10 +
with message-id 
and subject line Bug#825762: fixed in libtext-sprintfn-perl 0.08-1
has caused the Debian Bug report #825762,
regarding libtext-sprintfn-perl: FTBFS with Perl 5.24: t/01-basics.t failure
to be marked as done.

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

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


-- 
825762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtext-sprintfn-perl
Version: 0.07-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition
Tags: fixed-upstream
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=105989

This package fails to build with Perl 5.24 (currently in experimental.)
This seems to be fixed upstream in 0.08.
  
  #   Failed test '<%*1$.*f> = <4.>'
  #   at t/01-basics.t line 60.
  #  got: '<5.>'
  # expected: '<4.>'
  Invalid conversion in sprintf: "%(" at 
/<>/blib/lib/Text/sprintfn.pm line 69.
  Redundant argument in sprintf at /<>/blib/lib/Text/sprintfn.pm 
line 69.
  # Looks like you failed 1 test of 31.

A full build log is available at
  
http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/libtext-sprintfn-perl_0.07-1/

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libtext-sprintfn-perl
Source-Version: 0.08-1

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated libtext-sprintfn-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 19:20:06 +0200
Source: libtext-sprintfn-perl
Binary: libtext-sprintfn-perl
Architecture: source all
Version: 0.08-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Jonas Smedegaard 
Description:
 libtext-sprintfn-perl - drop-in replacement for sprintf(), with named 
parameter support
Closes: 825762
Changes:
 libtext-sprintfn-perl (0.08-1) unstable; urgency=medium
 .
   [ upstream ]
   * New release.
 Closes: Bug#825762. Thanks to Niko Tyni.
 .
   [ Jonas Smedegaard ]
   * Declare compliance with Debian Policy 3.9.8.
   * Modernize Vcs-Git field: Use https protocol URL.
   * Modernize git-buildpackage config: Filter any .git* file.
   * Update watch file:
 + Bump to version 4.
 + Use only MetaCPAN URL.
 + Tighten to ignore prereleases.
 + Mention gpb in usage comment.
   * Stop track upstream source with CDBS (use gpb --uscan).
   * Update copyright info:
 + Extend coverage of packaging to include current year.
Checksums-Sha1:
 e0b86d7d0624f9bd4cb49768d3cc4246423b54c9 2114 libtext-sprintfn-perl_0.08-1.dsc
 bff81c0806b95b27ddea6b514f922a5dea367f91 17205 
libtext-sprintfn-perl_0.08.orig.tar.gz
 f3f733e6bbc9a254c121dba655f6f4212e62b6cd 3244 
libtext-sprintfn-perl_0.08-1.debian.tar.xz
 5e9dd2c64c09ecc9ff3448ff0789a822ad0ebd8b 13562 
libtext-sprintfn-perl_0.08-1_all.deb
Checksums-Sha256:
 6e02765c3784ade93df0134fb46e869f1b9806a7d6c7b7b59c140466cc5be29a 2114 
libtext-sprintfn-perl_0.08-1.dsc
 2075fb511cd51998739b29a29a5b100983491e6bf9d2f4a1b229374c57a524c0 17205 
libtext-sprintfn-perl_0.08.orig.tar.gz
 18ef933d06702ec19a3016dd4eb01349a7be60b80ff5a4b333b4bfde4b2e68b0 3244 
libtext-sprintfn-perl_0.08-1.debian.tar.xz
 a4aa50395e47d13e03100080e2874de2cbcf6023f4a6d0b3b1d10250959c4c94 13562 
libtext-sprintfn-perl_0.08-1_all.deb
Files:
 23554e574ee83306501c6dd3eba6d501 2114 perl optional 
libtext-sprintfn-perl_0.08-1.dsc
 5833c1348bced06a949fb6ef0cb370da 17205 perl optional 
libtext-sprintfn-perl_0.08.orig.tar.gz
 795539141c7d0eefe2d683c7c19d2138 3244 perl optional 
libtext-sprintfn-perl_0.08-1.debian.tar.xz
 f0bd46ea4ee48a70ef864b5f9a90d155 13562 perl optional 
libtext-sprintfn-perl_0.08-1_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX2YdaAAoJECx8MUbBoAEhI1cQAJFgoUmIawRuoID98f7o0H6+

Bug#837791: marked as done (vino: FTBFS: ./configure: line 4067: GNOME_MAINTAINER_MODE_DEFINES: command not found)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 17:54:02 +
with message-id 
and subject line Bug#837791: fixed in vino 3.21.92-2
has caused the Debian Bug report #837791,
regarding vino: FTBFS:  ./configure: line 4067: GNOME_MAINTAINER_MODE_DEFINES: 
command not found
to be marked as done.

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

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


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

Dear Maintainer,

vino fails to build from source in unstable/amd64:

  [..]

  configure:3498: $? = 0
  configure:3505: ./conftest
  configure:3509: $? = 0
  configure:3524: result: no
  configure:3529: checking for suffix of object files
  configure:3551: gcc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:3555: $? = 0
  configure:3576: result: o
  configure:3580: checking whether we are using the GNU C compiler
  configure:3599: gcc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:3599: $? = 0
  configure:3608: result: yes
  configure:3617: checking whether gcc accepts -g
  configure:3637: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:3637: $? = 0
  configure:3678: result: yes
  configure:3695: checking for gcc option to accept ISO C89
  configure:3758: gcc  -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:3758: $? = 0
  configure:3771: result: none needed
  configure:3796: checking whether gcc understands -c and -o together
  configure:3818: gcc -c conftest.c -o conftest2.o
  configure:3821: $? = 0
  configure:3818: gcc -c conftest.c -o conftest2.o
  configure:3821: $? = 0
  configure:3833: result: yes
  configure:3861: checking for style of include used by make
  configure:3889: result: GNU
  configure:3915: checking dependency style of gcc
  configure:4026: result: none
  configure:4045: checking whether to enable maintainer-specific portions of 
Makefiles
  configure:4054: result: no
  
  ##  ##
  ## Cache variables. ##
  ##  ##
  
  ac_cv_c_compiler_gnu=yes
  ac_cv_env_CC_set=
  ac_cv_env_CC_value=
  ac_cv_env_CFLAGS_set=set
  ac_cv_env_CFLAGS_value='-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security'
  ac_cv_env_CPPFLAGS_set=set
  ac_cv_env_CPPFLAGS_value='-Wdate-time -D_FORTIFY_SOURCE=2'
  ac_cv_env_CPP_set=
  ac_cv_env_CPP_value=
  ac_cv_env_EGG_SMCLIENT_CFLAGS_set=
  ac_cv_env_EGG_SMCLIENT_CFLAGS_value=
  ac_cv_env_EGG_SMCLIENT_LIBS_set=
  ac_cv_env_EGG_SMCLIENT_LIBS_value=
  ac_cv_env_LDFLAGS_set=set
  ac_cv_env_LDFLAGS_value='-fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,defs 
-Wl,-O1 -Wl,--as-needed'
  ac_cv_env_LIBS_set=
  ac_cv_env_LIBS_value=
  ac_cv_env_LT_SYS_LIBRARY_PATH_set=
  ac_cv_env_LT_SYS_LIBRARY_PATH_value=
  ac_cv_env_PKG_CONFIG_LIBDIR_set=
  ac_cv_env_PKG_CONFIG_LIBDIR_value=
  ac_cv_env_PKG_CONFIG_PATH_set=
  ac_cv_env_PKG_CONFIG_PATH_value=
  ac_cv_env_PKG_CONFIG_set=
  ac_cv_env_PKG_CONFIG_value=
  ac_cv_env_VINO_SERVER_CFLAGS_set=
  ac_cv_env_VINO_SERVER_CFLAGS_value=
  ac_cv_env_VINO_SERVER_LIBS_set=
  ac_cv_env_VINO_SERVER_LIBS_value=
  ac_cv_env_XMKMF_set=
  ac_cv_env_XMKMF_value=
  ac_cv_env_build_alias_set=set
  ac_cv_env_build_alias_value=x86_64-linux-gnu
  ac_cv_env_host_alias_set=
  ac_cv_env_host_alias_value=
  ac_cv_env_target_alias_set=
  ac_cv_env_target_alias_value=
  ac_cv_objext=o
  ac_cv_path_install='/usr/bin/install -c'
  ac_cv_path_mkdir=/bin/mkdir
  ac_cv_prog_AWK=mawk
  ac_cv_prog_ac_ct_CC=gcc
  ac_cv_prog_cc_c89=
  ac_cv_prog_cc_g=yes
  ac_cv_prog_make_make_set=yes
  am_cv_CC_dependencies_compiler_type=none
  am_cv_make_support_nested_variables=yes
  am_cv_prog_cc_c_o=yes
  
  ## - ##
  ## Output variables. ##
  ## - ##
  
  ACLOCAL='${SHELL} 

Bug#837121: marked as done (gazebo: please restrict libkido-dev (build-)dependency to architectures where it is available.)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 17:50:16 +
with message-id 
and subject line Bug#837121: fixed in gazebo 7.3.0+dfsg-6
has caused the Debian Bug report #837121,
regarding gazebo: please restrict libkido-dev (build-)dependency to 
architectures where it is available.
to be marked as done.

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

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


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

Package: gazebo
Version: 7.3.0+dfsg-3
Severity: serious
Tags: patch

The most recent version of gazebo added a build-dependency on 
libkido-dev to the source package and added a binary on libkido-dev to 
libgazebo7-dev


No mention of this was made in the changelog and no other changes in the 
upload seem to be related but 
https://anonscm.debian.org/git/debian-science/packages/gazebo.git/commit/?id=80f9a218ccebb32258812afdf1cce6b50ab88126 
indicates this was to add support for a new feature.


libkido-dev is only available on a handful of architectures. As a result 
this new (build-)dependency is blocking the migration of the new version 
of the package (and hence the FTBFS fix) to testing.


The attatched patch restricts the (build-)dependencies on libkido-dev to 
the architectures where it is actually available (amd64, arm64, i386, 
ppc64el and alpha)
diff -Nru gazebo-7.3.0+dfsg/debian/changelog gazebo-7.3.0+dfsg/debian/changelog
--- gazebo-7.3.0+dfsg/debian/changelog  2016-08-31 17:57:53.0 +
+++ gazebo-7.3.0+dfsg/debian/changelog  2016-09-07 15:06:23.0 +
@@ -1,3 +1,10 @@
+gazebo (7.3.0+dfsg-3+rpi1) stretch-staging; urgency=medium
+
+  * Restrict (build-)dependency on libkido-dev to architectures where that 
package
+is actually available (amd64, arm64, i386, ppc64el and alpha). 
+
+ -- Peter Michael Green   Wed, 07 Sep 2016 15:06:23 
+
+
 gazebo (7.3.0+dfsg-3) unstable; urgency=medium
 
   [ Jochen Sprickerhof ]
diff -Nru gazebo-7.3.0+dfsg/debian/control gazebo-7.3.0+dfsg/debian/control
--- gazebo-7.3.0+dfsg/debian/control2016-08-30 22:54:59.0 +
+++ gazebo-7.3.0+dfsg/debian/control2016-09-07 15:06:07.0 +
@@ -45,7 +45,7 @@
libbullet-dev,
libsimbody-dev,
libsimbody-dev (<< 4.0.0),
-   libkido-dev,
+   libkido-dev [amd64 arm64 i386 powerpc alpha],
libgdal-dev,
ruby-ronn,
libgtest-dev
@@ -138,7 +138,7 @@
  libignition-math2-dev,
  libbullet-dev,
  libsimbody-dev,
- libkido-dev,
+ libkido-dev [amd64 arm64 i386 powerpc alpha],
  libgazebo7 (= ${binary:Version}),
  gazebo7-common (= ${source:Version}),
  gazebo7-plugin-base (= ${binary:Version}),
--- End Message ---
--- Begin Message ---
Source: gazebo
Source-Version: 7.3.0+dfsg-6

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

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

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated gazebo 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Sep 2016 17:00:37 +
Source: gazebo
Binary: gazebo7-common gazebo7 libgazebo7 libgazebo7-dev gazebo7-plugin-base 
gazebo7-doc
Architecture: source
Version: 7.3.0+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 gazebo7- Open Source Robotics Simulator - Binaries
 gazebo7-common - Open Source Robotics Simulator - Shared files
 gazebo7-doc - Open Source Robotics Simulator - Documentation
 gazebo7-plugin-base - Open Source Robotics Simulator - base plug-ins
 libgazebo7 - Open Source Robotics Simulator - shared library
 libgazebo7-dev - Open Source Robotics Simulator - Development Files
Closes: 837121
Changes:
 gazebo (7.3.0+dfsg-6) unstable; urgency=medium
 .
   * Fix 

Processed: Pending fixes for bugs in the liblexical-underscore-perl package

[Debian Bug Tracking System]

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

> tag 825524 + pending
Bug #825524 [liblexical-underscore-perl] liblexical-underscore-perl: FTBFS with 
Perl 5.24: Can't use global $_ in "my"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: bug 811672 is forwarded to https://bugs.kde.org/show_bug.cgi?id=360844

[Debian Bug Tracking System]

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

> forwarded 811672 https://bugs.kde.org/show_bug.cgi?id=360844
Bug #811672 [qt4-perl] FTBFS with GCC 6: cannot convert x to y
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=360844'.
> thanks
Stopping processing here.

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

Processed: bug 834281 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=102651, tagging 834281

[Debian Bug Tracking System]

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

> forwarded 834281 https://rt.cpan.org/Public/Bug/Display.html?id=102651
Bug #834281 {Done: intrigeri } [libgnupg-interface-perl] 
libgnupg-interface-perl: FTBFS, test failures, probably gpg2
Ignoring request to change the forwarded-to-address of bug#834281 to the same 
value
> tags 834281 + patch
Bug #834281 {Done: intrigeri } [libgnupg-interface-perl] 
libgnupg-interface-perl: FTBFS, test failures, probably gpg2
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#811672: qt4-perl: diff for NMU version 4.8.4-1.3

[gregor herrmann]

Control: tags 811672 + patch
Control: tags 811672 + pending

Dear maintainer,

I've prepared an NMU for qt4-perl (versioned as 4.8.4-1.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Aziza Mustafà Zadeh: Dance Of Fire
diff -Nru qt4-perl-4.8.4/debian/changelog qt4-perl-4.8.4/debian/changelog
--- qt4-perl-4.8.4/debian/changelog	2014-11-01 03:54:49.0 +0100
+++ qt4-perl-4.8.4/debian/changelog	2016-09-14 19:54:03.0 +0200
@@ -1,3 +1,12 @@
+qt4-perl (4.8.4-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS with GCC 6: cannot convert x to y":
+add patch from upstream bug tracker to properly initialize
+smokeperl_object. (Closes: #811672)
+
+ -- gregor herrmann   Wed, 14 Sep 2016 19:54:03 +0200
+
 qt4-perl (4.8.4-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru qt4-perl-4.8.4/debian/patches/Qt-0.96.0-Initialize-smokeperl_object-properly.patch qt4-perl-4.8.4/debian/patches/Qt-0.96.0-Initialize-smokeperl_object-properly.patch
--- qt4-perl-4.8.4/debian/patches/Qt-0.96.0-Initialize-smokeperl_object-properly.patch	1970-01-01 01:00:00.0 +0100
+++ qt4-perl-4.8.4/debian/patches/Qt-0.96.0-Initialize-smokeperl_object-properly.patch	2016-09-14 19:47:06.0 +0200
@@ -0,0 +1,37 @@
+From 1d30fbbd8fad3d9ee87f1b524384bb337c559d88 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
+Date: Mon, 1 Feb 2016 16:31:45 +0100
+Subject: [PATCH] Initialize smokeperl_object properly
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+This patch fixes this build failure with GCC 6:
+
+/builddir/build/BUILD/Qt-0.96.0/qtcore/src/util.cpp:2248:59: error: cannot convert 'bool' to 'void*' in initialization
+ static smokeperl_object nothis = { 0, 0, 0, false };
+   ^
+
+CPAN RT#111630
+
+Signed-off-by: Petr Písař 
+
+
+Bug: https://bugs.kde.org/show_bug.cgi?id=360844
+Bug-Debian: https://bugs.debian.org/811672
+
+---
+ qtcore/src/util.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/qtcore/src/util.cpp
 b/qtcore/src/util.cpp
+@@ -2231,7 +2231,7 @@
+ methcache.insert(mcid, new Smoke::ModuleIndex(mi));
+ }
+ 
+-static smokeperl_object nothis = { 0, 0, 0, false };
++static smokeperl_object nothis = { 0, 0, 0, NULL };
+ smokeperl_object* call_this = 0;
+ if ( SvOK(sv_this) ) {
+ call_this = sv_obj_info( sv_this );
diff -Nru qt4-perl-4.8.4/debian/patches/series qt4-perl-4.8.4/debian/patches/series
--- qt4-perl-4.8.4/debian/patches/series	2014-11-01 03:54:59.0 +0100
+++ qt4-perl-4.8.4/debian/patches/series	2016-09-14 19:46:20.0 +0200
@@ -2,3 +2,4 @@
 qtcore4.pmupdate.diff
 perl5.20.diff
 additionalperl5.20.diff
+Qt-0.96.0-Initialize-smokeperl_object-properly.patch


signature.asc
Description: Digital Signature

Bug#834281: [rt.cpan.org #102651] patches to fix the GnuPG::Interface test suite to work with GnuPG 2.1

[Daniel Kahn Gillmor]

Attached is a series of 7 patches that let the GnuPG::Interface test
suite work with GnuPG 2.1.

These patches can also be found on the improve-test-suite branch at
git://lair.fifthhorseman.net/~dkg/gnupg-interface (commit ID
f5ca0742dd1f724de1765679b493d4cfb7ea216b).

If you want to try them out:

git remote add dkg git://lair.fifthhorseman.net/~dkg/gnupg-interface
git remote update dkg
git checkout -b improve-test-suite dkg/improve-test-suite
perl Makefile.PL
make test

Feel free to merge them directly if you like 'em :)

GnuPG 2.1 hasn't actually changed the interface to GnuPG very much:
there's a little bit of a change around expectations of where the
passphrase comes from and who needs to have access to it, but that's a
positive change that helps users to isolate which processes have access
to their secret key material

What has changed more significantly is the structure of the files in
GnuPG's homedir, which has never been part of GnuPG's publicly-declared
stable interface, and GnuPG::Interface's test/ directory sort of
implicitly assumed that it was.

The revised test suite now uses a temporary/throwaway GnuPG homedir,
which it seeds with the data from test/ , rather than assuming that
test/ can act as a pre-formed homedir in the first place.

You'll note that there's very little changed in the non-test-suite part
of GnuPG::Interface with this series.

   --dkg

>From d49813d8b82245b1d7b6c7541aa80ed92b249557 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor 
Date: Tue, 13 Sep 2016 10:38:12 -0400
Subject: [PATCH 1/7] Generalize the test suite

The test suite currently assumes it knows something about the internal
state of GnuPG's homedir.

It's safer and less brittle to rely explicitly on the public interface
that GnuPG has committed to, such as --import-keys and --list-keys,
rather than assuming that certain files are in certain places in the
GnuPG homedir.

It's also better to create a fresh homedir and allow GnuPG to populate
it during the test suite, cleaning it up at the end, rather than hope
that GnuPG will leave a pre-existing homedir untouched.

With this change, many more of the tests pass when /usr/bin/gpg is
provided by GnuPG 2.1.
---
 .gitignore |  2 --
 t/000_setup.t  | 28 
 t/MyTestSpecific.pm|  2 +-
 t/zzz_cleanup.t| 17 +
 test/fake-pinentry.pl  | 28 
 test/{options => gpg.conf} |  0
 test/secret-keys/1.0.test  |  4 ++--
 7 files changed, 76 insertions(+), 5 deletions(-)
 create mode 100644 t/000_setup.t
 create mode 100644 t/zzz_cleanup.t
 create mode 100755 test/fake-pinentry.pl
 rename test/{options => gpg.conf} (100%)

diff --git a/.gitignore b/.gitignore
index 3100061..44e438a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -6,8 +6,6 @@
 /pm_to_blib
 *.tar.gz
 /test/*/*.out
-/test/random_seed
 /test/temp
-/test/trustdb.gpg
 /MYMETA.*
 /MANIFEST.SKIP.bak
diff --git a/t/000_setup.t b/t/000_setup.t
new file mode 100644
index 000..7f7f7b0
--- /dev/null
+++ b/t/000_setup.t
@@ -0,0 +1,28 @@
+#!/usr/bin/perl -w
+
+use strict;
+use English qw( -no_match_vars );
+
+use lib './t';
+use MyTest;
+use MyTestSpecific;
+use Cwd;
+use File::Path qw (make_path);
+use File::Copy;
+
+TEST
+{
+make_path('test/gnupghome', { mode => 0700 });
+my $agentconf = IO::File->new( "> test/gnupghome/gpg-agent.conf" );
+$agentconf->write("pinentry-program " . getcwd() . "/test/fake-pinentry.pl\n");
+$agentconf->close();
+copy('test/gpg.conf', 'test/gnupghome/gpg.conf');
+reset_handles();
+
+my $pid = $gnupg->import_keys(command_args => [ 'test/pubring.gpg', 'test/secring.gpg' ],
+  options => [ 'batch'],
+  handles => $handles);
+waitpid $pid, 0;
+
+return $CHILD_ERROR == 0;
+};
diff --git a/t/MyTestSpecific.pm b/t/MyTestSpecific.pm
index 053b749..1af98ae 100644
--- a/t/MyTestSpecific.pm
+++ b/t/MyTestSpecific.pm
@@ -40,7 +40,7 @@ use vars qw( @ISA   @EXPORT
 
 $gnupg = GnuPG::Interface->new( passphrase => 'test' );
 
-$gnupg->options->hash_init( homedir  => 'test',
+$gnupg->options->hash_init( homedir  => 'test/gnupghome',
 armor=> 1,
 meta_interactive => 0,
 meta_signing_key_id  => '0xF950DA9C',
diff --git a/t/zzz_cleanup.t b/t/zzz_cleanup.t
new file mode 100644
index 000..5c03a72
--- /dev/null
+++ b/t/zzz_cleanup.t
@@ -0,0 +1,17 @@
+#!/usr/bin/perl -w
+
+use strict;
+use English qw( -no_match_vars );
+
+use lib './t';
+use MyTest;
+use MyTestSpecific;
+use File::Path qw (remove_tree);
+
+# this is actually no test, just cleanup.
+TEST
+{
+my $err = [];
+remove_tree('test/gnupghome', {error => \$err});
+return ! @$err;
+};
diff --git a/test/fake-pinentry.pl b/test/fake-pinentry.pl
new file mode 

Bug#837786: mutter: Issues repainting the display on mouse movement

[Roman Pavlík]

I can confirm this issues.

As usable workaround, I disabled DRI for Intel driver via Xorg 
configuration.


Section "Device"
Identifier  "Intel Graphics"
Driver  "Intel"
Option  "DRI"  "false"
EndSection



$ lshw -c video
  *-display
   description: VGA compatible controller
   product: 2nd Generation Core Processor Family Integrated 
Graphics Controller

   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:35 memory:f640-f67f 
memory:c000-cfff ioport:f000(size=64) memory:c-d



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

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

Versions of packages mutter depends on:
ii  gsettings-desktop-schemas  3.21.4-2
ii  libc6  2.23-5
ii  libglib2.0-0   2.49.6-1
ii  libmutter0i3.21.92-1
ii  libx11-6   2:1.6.3-1
ii  libxcomposite1 1:0.4.4-1
ii  mutter-common  3.21.92-1
ii  zenity 3.20.0-1

Versions of packages mutter recommends:
ii  gnome-session [x-session-manager]3.20.2-1
ii  gnome-session-flashback [x-session-manager]  3.20.2-1

Versions of packages mutter suggests:
ii  gnome-control-center  1:3.21.90-1
ii  xdg-user-dirs 0.15-2

-- no debconf information

Bug#825524: Pending fixes for bugs in the liblexical-underscore-perl package

[pkg-perl-maintainers]

tag 825524 + pending
thanks

Some bugs in the liblexical-underscore-perl package are closed in
revision 38298f6d4b6dd21c6ca1c6502664b7c86de1f1c9 in branch 'master'
by Jonas Smedegaard

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/liblexical-underscore-perl.git/commit/?id=38298f6

Commit message:

Add patch 1001 to avoid lexical underscore. Closes: Bug#825524. Thanks to 
Niko Tyni.

Processed: qt4-perl: diff for NMU version 4.8.4-1.3

[Debian Bug Tracking System]

Processing control commands:

> tags 811672 + patch
Bug #811672 [qt4-perl] FTBFS with GCC 6: cannot convert x to y
Added tag(s) patch.
> tags 811672 + pending
Bug #811672 [qt4-perl] FTBFS with GCC 6: cannot convert x to y
Added tag(s) pending.

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

Processed (with 1 error): #837595 and #837192 are duplicates (forcemerge)

[Debian Bug Tracking System]

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

> forcemerge 837595 837192
Bug #837595 [src:gnome-shell-pomodoro] gnome-shell-pomodoro: Not compatible 
with gnome-shell 3.21.x/3.22
Unable to merge bugs because:
package of #837192 is 'gnome-shell-pomodoro' not 'src:gnome-shell-pomodoro'
Failed to forcibly merge 837595: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed (with 1 error): #837595 and #837192 are duplicates

[Debian Bug Tracking System]

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

> merge 837595 837192
Bug #837595 [src:gnome-shell-pomodoro] gnome-shell-pomodoro: Not compatible 
with gnome-shell 3.21.x/3.22
Unable to merge bugs because:
forwarded of #837192 is '' not 
'https://github.com/codito/gnome-pomodoro/issues/236'
package of #837192 is 'gnome-shell-pomodoro' not 'src:gnome-shell-pomodoro'
Failed to merge 837595: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#813722: Bug#814183: marked as done (openmpi 1.10.2 is broken on powerpc)

[Graham Inggs]

Hi Alastair

On 13 September 2016 at 17:15, Debian Bug Tracking System
 wrote:
> I'm closing these bugs as fixed / unreproducible in 2.0.1-5. In
> particular I've rebuilt both aces3 and petsc on powerpc and mipsel (on
> partch.debian.org and eller.debian.org) and they build successfully.

Note that many of the packages are already carrying patches to skip
tests on powerpc, or limit the number of MPI processes on powerpc
(np=1).

> There have been code changes and bug fixes in the wait /lock code, as
> well as now using standard gcc atomics on both architectures, which
> means the relevant code paths have changed.

That's good to hear.

> Please reopen if the bug is seen again, but it is believed fixed.

That's fine with me.

Regards
Graham

Bug#836659: marked as done (units-filter: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 16:30:33 +
with message-id 
and subject line Bug#836659: fixed in units-filter 3.7-2
has caused the Debian Bug report #836659,
regarding units-filter: please drop the build dependency on hardening-wrapper
to be marked as done.

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

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


-- 
836659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: units-filter
Version: 3.7-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: units-filter
Source-Version: 3.7-2

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

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

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated units-filter 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 15:50:13 +0200
Source: units-filter
Binary: units-filter
Architecture: source amd64
Version: 3.7-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 units-filter - Parser for expressions concerning physical values
Closes: 836659
Changes:
 units-filter (3.7-2) unstable; urgency=medium
 .
   * dropped the dependency on hardening-wrapper. Closes: #836659
   * upgraded Standards-Version to 3.9.8
Checksums-Sha1:
 097d37cad7191b0760b334a3159d2b042297e724 1730 units-filter_3.7-2.dsc
 2c720f97c720d22089838e4eb2d3f9fc80dabc86 4608 units-filter_3.7-2.debian.tar.xz
 a99694fd4f67e7b152bd163ed144add9238cc3a6 127146 
units-filter-dbgsym_3.7-2_amd64.deb
 4988d53616a4ca7c7053c2c6bcbcb85cf4edacc8 31282 units-filter_3.7-2_amd64.deb
Checksums-Sha256:
 8924886ff25fb906c4206d67cee9c329a9644cb4f7eddc793834ada026de1bee 1730 
units-filter_3.7-2.dsc
 18c9cdff943289f12f16b3c21346a24635812c920c164ecca6f23dd44e0c979e 4608 
units-filter_3.7-2.debian.tar.xz
 2c6c49a240afdcdacbc499b46801212555f1e42dba8af3dba16b033a52167f2c 127146 
units-filter-dbgsym_3.7-2_amd64.deb
 506d8f70d3f5fbe1eca61f5100c1a57a3afdbca7dcd8b475e495c54122044047 31282 
units-filter_3.7-2_amd64.deb
Files:
 be387dfcd96ff50b0d209362697c4cf5 1730 science optional units-filter_3.7-2.dsc
 e2fa8917facf4572667fba7fc4649037 4608 science optional 
units-filter_3.7-2.debian.tar.xz
 25536f5efd71b2f7f86206ac2e90f8b5 127146 debug extra 
units-filter-dbgsym_3.7-2_amd64.deb
 55bb29a55ba12ba161e4f94f8577256d 31282 science optional 
units-filter_3.7-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBV9lXOBwoFpBxNq45AQhN4A//W5JQAE8BtGzT5znTAiEjBdG0MaX90txl
pdtNeK8fOqF9K6656vC/nVd8cPAo37Xg9I074sVeoO+6gu1tRe4kKWo1nogIh/q7
KR4iX4T5ij+U6nqrGQYLMpWdI5WZ/WlQEE7RrR0f7Xt3DzIbKmS0zgGXPlvAiIRw
qrvtjbTyRqX49x9T74OFLD4opyaZ9v8FQJiyiZjTZmDXtYrNbNv6K3+dcOpIFvCg
KJ2tq/EmsA8AiENW5VwVA8RqX3mkDa4F8V+z6lwJDVqChel3g4vQTmEQTpNun1ae
6jnld6owsugdNZlJ0ha8tW+yrZ5F8njHZnTVXNJSWvrePDaM+/w+RPiIefaWjY87
3Wk/vZZGGyeP3AzjS+h/25+gqf/GpIc3sh/nrjysV6O/jeAEogxwdQGm1YUZm34g
p5w2vnCoq23p8Jya2hLm15axiPeS5GGCZff4FjHpHWLd745nTd7ovrtS/7M0XhGW
UtHh/XNxvgfmQ7e9AuvHWtZ+qhrmaLoF5rgHwDKEEGjodpSb2JC5lA5YJLxQHj5W
rQXzx1W7vq9Jzlz0t37NfhQiGt9dsBf0rAs0kzjuyN5S2PuPUxGPWaQ3ejlvymxv
a+GHBqx8ctgmMEvhoWF154C8HFzvxjiKcg+PjsnTosS/YuO8cx/+MPOE6ifJheR0
vjsnI6UfTys=
=20L2
-END PGP SIGNATURE End Message ---

Bug#835213: marked as done (python-cogent: FTBFS in testing (AssertionError))

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 16:29:41 +
with message-id 
and subject line Bug#835213: fixed in python-cogent 1.9-1
has caused the Debian Bug report #835213,
regarding python-cogent: FTBFS in testing (AssertionError)
to be marked as done.

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

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


-- 
835213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-cogent
Version: 1.5.3-10
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

  File "/<>/cogent/util/unit_test.py", line 316, in failUnlessEqual
(msg or 'Got %s, but expected %s' % (`observed`, `expected`))
AssertionError: Got [['cdhit_test_seqs_0'], ['cdhit_test_seqs_1'], 
['cdhit_test_seqs_2'], ['cdhit_test_seqs_3'], ['cdhit_test_seqs_4'], 
['cdhit_test_seqs_5'], ['cdhit_test_seqs_6'], ['cdhit_test_seqs_7'], 
['cdhit_test_seqs_8'], ['cdhit_test_seqs_9']], but expected 
[['cdhit_test_seqs_0'], ['cdhit_test_seqs_1'], ['cdhit_test_seqs_2'], 
['cdhit_test_seqs_3'], ['cdhit_test_seqs_4'], ['cdhit_test_seqs_5'], 
['cdhit_test_seqs_6', 'cdhit_test_seqs_8'], ['cdhit_test_seqs_7'], 
['cdhit_test_seqs_9']]

==
FAIL: test_base_command (test_app.test_cd_hit.CD_HIT_Tests)
CD_HIT BaseCommand should return the correct BaseCommand
--
Traceback (most recent call last):
  File "/<>/tests/test_app/test_cd_hit.py", line 25, in 
test_base_command
''.join(['cd "',getcwd(),'/"; ','cdhit']))
  File "/<>/cogent/util/unit_test.py", line 316, in failUnlessEqual
(msg or 'Got %s, but expected %s' % (`observed`, `expected`))
AssertionError: Got 'cd "/<>/tests/"; cd-hit', but expected 'cd 
"/<>/tests/"; cdhit'

==
FAIL: test_cdhit_from_seqs (test_app.test_cd_hit.CD_HIT_Tests)
CD_HIT should return expected seqs
--
Traceback (most recent call last):
  File "/<>/tests/test_app/test_cd_hit.py", line 52, in 
test_cdhit_from_seqs
self.assertEqual(res.toFasta(), protein_expected)
  File "/<>/cogent/util/unit_test.py", line 316, in failUnlessEqual
(msg or 'Got %s, but expected %s' % (`observed`, `expected`))
AssertionError: Got 
'>seq1\nMGNKWSKSWPQVRDRMRRAAPAPAADGVGAVSQDLAKHGAITSSNTAATNDDCAWLEAQTEEEVGFPVRPQVPLRPMTYK\n>seq2\nMGGKWSKSSIVGWSTVRERMRKTPPAADGVGAVSQDLDKHGAVTSSNTAFNNPDCAWLEAQEDEDVGFPVRPQVPLRPT\n>seq3\nMGGKWSKSSIVGWPAIRERMRRARPAADRVGTQPAADGVGAVSQDLARHGAVTSSNTSHNNPDCAWLEAQVGVR\n>seq4\nMGKIWSKSSIVGWPEIRERMRRQRPHEPAVEPAVGVGAASQDLANRGALTTSNTRTNNPTVAWVEAQEEEGEVVRPQ\n>seq6\nMGKIWSKSSLVGWPEIRERIRRQTPEPAVGVGAVSQDLANRGAITTSNTKDNNQTVAWLEAQEEPVRPQVPLRPM\n>seq7\nMGNALRKGKFEGWAAVRERMRRTRTFPESEPCAPGVGQISRELAARGGIPSSHTPQNNESHQEEEVGFPVAPQV\n>seq8\nMGNAWSKSKFAGWSEVRDRMRRSSSDPQQPCAPGVGAVSRELATRGGISSSALAFLDSHKDEDVGFPVRPQVP\n>seq9\nMGNVLGKDKFKGWAAVRERMRKTSSDPDPQPCAPGVGPVSRELSYTPQNNAALAFLESHEDEDVGFPVXPQV',
 but expected 
'>seq1\nMGNKWSKSWPQVRDRMRRAAPAPAADGVGAVSQDLAKHGAITSSNTAATNDDCAWLEAQTEEEVGFPVRPQVPLRPMTYK\n>seq2\nMGGKWSKSSIVGWSTVRERMRKTPPAADGVGAVSQDLDKHGAVTSSNTAFNNPDCAWLEAQEDEDVGFPVRPQVPLRPT\n>seq3\nMGGKWSKSSIVGWPAIRERMRRARPAADRVGTQPAADGVGAVSQDLARHGAVTSSNTSHNNPDCAWLEAQVGVR\n>seq4\nMGKIWSKSSIV
 
GWPEIRERMRRQRPHEPAVEPAVGVGAASQDLANRGALTTSNTRTNNPTVAWVEAQEEEGEVVRPQ\n>seq5\nMGKIWSKSSLVGWPEIRERMRRQTQEPAVEPAVGAGAASQDLANRGAITIRNTRDNNESIAWLEAQEEEFPVRPQV\n>seq7\nMGNALRKGKFEGWAAVRERMRRTRTFPESEPCAPGVGQISRELAARGGIPSSHTPQNNESHQEEEVGFPVAPQV\n>seq8\nMGNAWSKSKFAGWSEVRDRMRRSSSDPQQPCAPGVGAVSRELATRGGISSSALAFLDSHKDEDVGFPVRPQVP\n>seq9\nMGNVLGKDKFKGWAAVRERMRKTSSDPDPQPCAPGVGPVSRELSYTPQNNAALAFLESHEDEDVGFPVXPQV'

==
FAIL: test_changing_working_dir 

Bug#837791: vino: FTBFS: ./configure: line 4067: GNOME_MAINTAINER_MODE_DEFINES: command not found

[Chris Lamb]

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

Dear Maintainer,

vino fails to build from source in unstable/amd64:

  [..]

  configure:3498: $? = 0
  configure:3505: ./conftest
  configure:3509: $? = 0
  configure:3524: result: no
  configure:3529: checking for suffix of object files
  configure:3551: gcc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:3555: $? = 0
  configure:3576: result: o
  configure:3580: checking whether we are using the GNU C compiler
  configure:3599: gcc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:3599: $? = 0
  configure:3608: result: yes
  configure:3617: checking whether gcc accepts -g
  configure:3637: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:3637: $? = 0
  configure:3678: result: yes
  configure:3695: checking for gcc option to accept ISO C89
  configure:3758: gcc  -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:3758: $? = 0
  configure:3771: result: none needed
  configure:3796: checking whether gcc understands -c and -o together
  configure:3818: gcc -c conftest.c -o conftest2.o
  configure:3821: $? = 0
  configure:3818: gcc -c conftest.c -o conftest2.o
  configure:3821: $? = 0
  configure:3833: result: yes
  configure:3861: checking for style of include used by make
  configure:3889: result: GNU
  configure:3915: checking dependency style of gcc
  configure:4026: result: none
  configure:4045: checking whether to enable maintainer-specific portions of 
Makefiles
  configure:4054: result: no
  
  ##  ##
  ## Cache variables. ##
  ##  ##
  
  ac_cv_c_compiler_gnu=yes
  ac_cv_env_CC_set=
  ac_cv_env_CC_value=
  ac_cv_env_CFLAGS_set=set
  ac_cv_env_CFLAGS_value='-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security'
  ac_cv_env_CPPFLAGS_set=set
  ac_cv_env_CPPFLAGS_value='-Wdate-time -D_FORTIFY_SOURCE=2'
  ac_cv_env_CPP_set=
  ac_cv_env_CPP_value=
  ac_cv_env_EGG_SMCLIENT_CFLAGS_set=
  ac_cv_env_EGG_SMCLIENT_CFLAGS_value=
  ac_cv_env_EGG_SMCLIENT_LIBS_set=
  ac_cv_env_EGG_SMCLIENT_LIBS_value=
  ac_cv_env_LDFLAGS_set=set
  ac_cv_env_LDFLAGS_value='-fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,defs 
-Wl,-O1 -Wl,--as-needed'
  ac_cv_env_LIBS_set=
  ac_cv_env_LIBS_value=
  ac_cv_env_LT_SYS_LIBRARY_PATH_set=
  ac_cv_env_LT_SYS_LIBRARY_PATH_value=
  ac_cv_env_PKG_CONFIG_LIBDIR_set=
  ac_cv_env_PKG_CONFIG_LIBDIR_value=
  ac_cv_env_PKG_CONFIG_PATH_set=
  ac_cv_env_PKG_CONFIG_PATH_value=
  ac_cv_env_PKG_CONFIG_set=
  ac_cv_env_PKG_CONFIG_value=
  ac_cv_env_VINO_SERVER_CFLAGS_set=
  ac_cv_env_VINO_SERVER_CFLAGS_value=
  ac_cv_env_VINO_SERVER_LIBS_set=
  ac_cv_env_VINO_SERVER_LIBS_value=
  ac_cv_env_XMKMF_set=
  ac_cv_env_XMKMF_value=
  ac_cv_env_build_alias_set=set
  ac_cv_env_build_alias_value=x86_64-linux-gnu
  ac_cv_env_host_alias_set=
  ac_cv_env_host_alias_value=
  ac_cv_env_target_alias_set=
  ac_cv_env_target_alias_value=
  ac_cv_objext=o
  ac_cv_path_install='/usr/bin/install -c'
  ac_cv_path_mkdir=/bin/mkdir
  ac_cv_prog_AWK=mawk
  ac_cv_prog_ac_ct_CC=gcc
  ac_cv_prog_cc_c89=
  ac_cv_prog_cc_g=yes
  ac_cv_prog_make_make_set=yes
  am_cv_CC_dependencies_compiler_type=none
  am_cv_make_support_nested_variables=yes
  am_cv_prog_cc_c_o=yes
  
  ## - ##
  ## Output variables. ##
  ## - ##
  
  ACLOCAL='${SHELL} 
/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92/build-aux/missing
 aclocal-1.15'
  ALL_LINGUAS=''
  AMDEPBACKSLASH=''
  AMDEP_FALSE=''
  AMDEP_TRUE='#'
  AMTAR='$${TAR-tar}'
  AM_BACKSLASH='\'
  AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
  AM_DEFAULT_VERBOSITY='1'
  AM_V='$(V)'
  AR=''
  AUTOCONF='${SHELL} 
/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92/build-aux/missing
 autoconf'
  AUTOHEADER='${SHELL} 
/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92/build-aux/missing
 autoheader'
  AUTOMAKE='${SHELL} 
/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92/build-aux/missing
 automake-1.15'
  AWK='mawk'
  CC='gcc'
  CCDEPMODE='depmode=none'
  CFLAGS='-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914171706.A1Iq1p8Nz0.db.vino/vino-3.21.92=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security'
  CPP=''
 

Bug#835743: z3: FTBFS: ../src/util/mpz.cpp:137:8: error: call of overloaded 'set(mpz&, long unsigned int)' is ambiguous

[Fabian Wolff]

Control: tags -1 + upstream patch fixed-upstream

Hi,

the following patch fixes this issue:

--- a/src/util/mpz.cpp
+++ b/src/util/mpz.cpp
@@ -134,7 +134,7 @@
 #endif
 
 mpz one(1);
-set(m_two64, UINT64_MAX);
+set(m_two64, static_cast(UINT64_MAX));
 add(m_two64, one, m_two64);
 }
 

The problem has already been fixed in the upstream repository by this commit:

  https://github.com/Z3Prover/z3/commit/27399309009314f56cdfbd8333f287b1a9b7a3a6

Kind regards,
Fabian

Processed: Re: z3: FTBFS: ../src/util/mpz.cpp:137:8: error: call of overloaded 'set(mpz&, long unsigned int)' is ambiguous

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream patch fixed-upstream
Bug #835743 [src:z3] z3: FTBFS: ../src/util/mpz.cpp:137:8: error: call of 
overloaded 'set(mpz&, long unsigned int)' is ambiguous
Added tag(s) fixed-upstream, patch, and upstream.

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

Bug#836619: marked as done (cdcover: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 16:19:50 +
with message-id 
and subject line Bug#836619: fixed in cdcover 0.9.1-12
has caused the Debian Bug report #836619,
regarding cdcover: please drop the build dependency on hardening-wrapper
to be marked as done.

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

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


-- 
836619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cdcover
Version: 0.9.1-11
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: cdcover
Source-Version: 0.9.1-12

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

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

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated cdcover package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 16:00:18 +0200
Source: cdcover
Binary: cdcover
Architecture: source amd64
Version: 0.9.1-12
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 cdcover- Creating Data-CD Covers
Closes: 836619
Changes:
 cdcover (0.9.1-12) unstable; urgency=medium
 .
   * upgraded Standards-Version to 3.9.8
   * dropped the dependency on hardening-wrapper. Closes: #836619
Checksums-Sha1:
 99f0789807ebcdb962ca186c87cacc4b423a65cf 1680 cdcover_0.9.1-12.dsc
 14a2a9e260855bdd84115ed5e1d6adaee505eddc 7932 cdcover_0.9.1-12.debian.tar.xz
 eee71e77c3d91a5a9294d8a34a7c573fb02f1424 88070 
cdcover-dbgsym_0.9.1-12_amd64.deb
 321f0faccb6ac437dc51eef93bd601b4f4dd6bad 23520 cdcover_0.9.1-12_amd64.deb
Checksums-Sha256:
 d641b5f1d263edf0120158d6010c21f068d97d9dda03f7f0f96c265dd182aff1 1680 
cdcover_0.9.1-12.dsc
 4018bbbcad77ebdabfcb55654271d8f7b19ddee94e282e84e3d951bac3eb008d 7932 
cdcover_0.9.1-12.debian.tar.xz
 1c16a5feb2564c8c5f3dd0dd24c25390104d58aeacb89d08323053fcc72d2a25 88070 
cdcover-dbgsym_0.9.1-12_amd64.deb
 65baccde1dae3974f7d3e48109193aea6f954844dcfd79c7bef80363039c0fa7 23520 
cdcover_0.9.1-12_amd64.deb
Files:
 e23c555f939c7dc4e3722bf874281945 1680 text optional cdcover_0.9.1-12.dsc
 da2e45d233714c6a2460bef007a94fb6 7932 text optional 
cdcover_0.9.1-12.debian.tar.xz
 e3635de00ace57d0c30155b6f51e03f3 88070 debug extra 
cdcover-dbgsym_0.9.1-12_amd64.deb
 f9c31122d1597e551b853a87f226e8a7 23520 text optional cdcover_0.9.1-12_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBV9lYghwoFpBxNq45AQiy4hAAmnnFFsDfYsJsHSHhnYBDwHUJH7J+klT2
AI4xOM7RoxvrXlWfmJWFtNYDVokNF4RH6fdmY0guyekHVQGeEXyp/qjKj+trkeTt
18I+ToHoeBIAarTWAZls38cjGJ8B4P+Ckp3+L9BLiOcvHa0inqFryd4ooVaHxNwx
pX3z5N7OHHF+kgdsZfkttavmf9GJEdmaxM6SepUr52ZGQjHEEkqwmECzDmhdhOI3
/lf1c17IwAj9VBzne/ePoGMREcINv7IoK9RMOrNbt0FmiIeeChmHAn5amKgDG5vy
JKTwAGufiisUX58IHVH5B1Bf+IRKura2MjgdHThFHJSI8Ux7fdJ33yeuJR2c8Ii0
x5XDgGPsTfn7yVZWyRdBkUI2qWr/e0EIl9zeVDMm0v0I3BrZU3qDQY8EIXW7M0BE
3jAeCNSwD1Jy+7LGgDy1uIjGxG4WHtTmxg51XO349GvtLBDut02sJ+7f3jOglLN7
8LRQjF1+qnofG48NyZpUVRFOTkFworyuoZEUvzxP8RCzyMLAqBnKH9vo3T5A8kDz
ZxzUu67t5ozuyeBGyBVCr//rqsZzZbw7wG5WKzWVG11pgfXFPgrLzxyBTmYfwg6j
CLOuj5iCRjcXd4goXoD5L2x2e2emWffcOU9zSCExd2P4f7Sq91KsYI1BKsHFBS30
bcCozUH8vFI=
=G1Ab
-END PGP SIGNATURE End Message ---

Bug#837759: network configuration stops working reliably

[Wolfgang Walter]

Am Mittwoch, 14. September 2016, 10:00:28 schrieben Sie:

> Control: tags -1 moreinfo
> 
> On 14 September 2016 at 06:59, Wolfgang Walter  
wrote:

> > Package: systemd
> > Version: 231-6
> > Severity: grave
> > 
> > Starting with version 231-6 the configuration of network interfaces stops
> > working reliably when rebooting a system. Downgrading to 231-5 fixes the
> > problem.
> > 
> > Symptoms: If a network interface is configured using
> > /etc/network/interfaces it seems that systemd now sometimes removes the
> > configured ip4 and/or ipv6 addresses in the boot process. It also seems
> > to remove routes of network interfaces configured manually or with
> > /etc/network/interfaces if the link state changes.
> > 
> > This seems not only be the case with interfaces configured via
> > /etc/network/ interfaces but with any interface one creates and assigns
> > ip addresses manually.
> > 
> > I tested this with a script:
> > 
> > #!/bin/sh
> > if [ "$1" = start ]; then
> > ip link del TEST >/dev/null 2>&1 || true
> > ip link add name TEST type dummy
> > ip -b - <<"EOF"
> > link set TEST up
> > addr add 10.10.10.10/32 dev TEST nodad
> > addr add 2a01:1:1:1::1/128 dev TEST nodad
> > addr add 2a01:1:1:1::2/128 dev TEST nodad
> > addr add 2a01:1:1:1::3/128 dev TEST nodad
> > addr add 2a01:1:1:1::4/128 dev TEST nodad
> > addr add 2a01:1:1:1::5/128 dev TEST nodad
> > EOF
> > ip addr ls TEST
> > sleep 2
> > elif [ "$1" = stop ]; then
> > ip addr flush dev TEST
> > ip link del TEST
> > fi
> > 
> > which I start with as a systemd oneshot service with
> > 
> > Before=systemd-networkd.service
> > 
> > I can see in the journal that TEST has all adresses assigned but with
> > 231-6 it looses them again (probably when systemd-networkd.service
> > starts). With 231-5 or earlier this in not the case.

> 
> It appears you are using systemd-networkd. Could you please attach
> your networkd configuration?

Yes, systemd-networkd ist active. But on most machines I only have *.link 
entries, usually one to name the device:

==
[Match]
MACAddress=11:22:33:44:55:66

[Link]
Name=net
WakeOnLan=off
==

Most of them are virtual machines.


On those machine where I also habe *.netdev and *.network entries this also 
happens. The one with the simpliest has only one *.network:

==
[Match]
Name=net

[Network]
LinkLocalAddressing=ipv6
IPv6AcceptRouterAdvertisements=no
DHCP=no
Address=10.11.12.13/24
Gateway=10.11.12.1
Address=2001:1234:1::abc1
Address=2001:1234:1::abc2
Address=2001:1234:1::abc3
Address=2001:1234:1::abc4
NTP=2001:1234:1::123

[Route]
Gateway=fe80::1
PreferredSource=2001:1234:1::abc1
==

This interface works fine. But other interfaces configured by 
/etc/network/interfaces or the manually created interface TEST loose there 
ipv4 and ipv6 addresses.

Please note, that I did not create a *.link entry for TEST on any of the 
machines. 


If I later restart these interfaces (with ifdown + ifup for 
/etc/network/interfaces, systemctl restart test-network-device.service for 
TEST) they keep their addresses.



> 
> Version 231-6 is built with iptables support, so that may be causing
> an interaction that was not visible before.

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

Bug#820965: [Pkg-samba-maint] Bug#820965: marked as pending

[Jelmer Vernooij]

On Wed, Sep 14, 2016 at 11:51:14AM +0300, Vlad Orlov wrote:
> Hi,
> 
> I'd like to know if there's any progress on uploading the new
> version to jessie-security. Just want to check if the update
> would fix https://bugs.debian.org/831851 as well.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836795 for the current
discussion.

Jelmer

Bug#775689: Re URGENT

[Christies, Trish]

I need your urgent assistance concerning a very important proposal, kindly 
contact me only at mrs.cherry...@hotmail.com

Best Regards,
Mrs Cherry Lee









































This e-mail is solely for the named addressee and may be confidential. You 
should only read, disclose, transmit, copy, distribute, act in reliance on or 
commercialise the contents if you are authorised to do so. If you are not the 
intended recipient of this e-mail, please notify postmas...@museum.vic.gov.au 
  by email immediately, or notify the 
sender and then destroy any copy of this message. Views expressed in this email 
are those of the individual sender, except where specifically stated to be 
those of an officer of Museum Victoria. Museum Victoria does not represent, 
warrant or guarantee that the integrity of this communication has been 
maintained nor that it is free from errors, virus or interference.

Bug#837786: mutter: Issues repainting the display on mouse movement

[JWM]

Package: mutter
Version: 3.21.92-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

After upgrading my system this morning and restarting a new gnome-shell session
(by rebooting), everything being displayed fails to repaint properly.

Everytime I launch an application and try to move the window it leaves traces
(i.e., shadows of its previous positions). The same happens on mouse hover.

Also, the clock (on the top desktop) flickers constantly.  Something similar
happens with the title bar in certain applications (e.g., vivaldi).

Since the only packages upgraded were related to mutter and gnome-shell, I
figure the one to blame is mutter.

I tried upgrading mutter to the version in unstable, but the result is the
same.

There is also no difference by using the classic gnome session or the wayland
session ---although, with wayland, the flickering and repainting is slightly
less frequent.

I tried recording the desktop session (with GNOME's screencast functionality),
but funnily the flickering stops while recording.



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

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

Versions of packages mutter depends on:
ii  gsettings-desktop-schemas  3.21.4-2
ii  libc6  2.23-5
ii  libglib2.0-0   2.49.6-1
ii  libmutter0i3.21.92-1
ii  libx11-6   2:1.6.3-1
ii  libxcomposite1 1:0.4.4-1
ii  mutter-common  3.21.92-1
ii  zenity 3.20.0-1

Versions of packages mutter recommends:
ii  gnome-session [x-session-manager]  3.20.2-1

Versions of packages mutter suggests:
ii  gnome-control-center  1:3.21.90-1
ii  xdg-user-dirs 0.15-2

-- no debconf information

Bug#837783: iio-sensor-proxy: hold transition to testing

[Ritesh Raj Sarraf]

Package: iio-sensor-proxy
Version: 1.2-1
Severity: grave
Tags: upstream
Justification: renders package unusable

https://github.com/hadess/iio-sensor-proxy/issues/100

There are some issues that need to be ironed out with the new flip in
kernel 4.8. Also, for 1.2, one more change needs to be picked up.


Until all settles down, block this version's migration to testing.

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

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

Versions of packages iio-sensor-proxy depends on:
ii  libc6   2.24-2
ii  libglib2.0-02.49.7-1
ii  libgudev-1.0-0  230-3
ii  systemd 231-6

iio-sensor-proxy recommends no packages.

iio-sensor-proxy suggests no packages.

-- no debconf information

Bug#821731: ctk: FTBFS: ctkDICOMUtil.cpp:33:3: error: 'log4cplus' has not been declared

[Andreas Tille]

Hi,

thanks for the clarification - ROM bug filed

Andreas.

On Tue, Sep 13, 2016 at 05:07:26PM +0200, Gert Wollny wrote:
> Hi,
> 
> Some time ago there was some activity with an upstream issue [1] about
> making the package ready for proper inclusion into Debian.
> 
> Unfortunately upstream doesn't properly document dependencies and seems
> to have the habit to use locally patched versions of these dependencies
> if they feel like it.
> 
> Given that they are also reluctant to tag a release, and the only useful
> dependent package would be Slicer (which has exactly the same issues), I
> think that packaging CTK doesn't make much sense.
> 
> Best,
> 
> Gert
> 
> [1] https://github.com/commontk/CTK/issues/608
> 
> 
> 




-- 
http://fam-tille.de

Bug#837738: marked as done (Fails to start, Invalid property: GtkScrolledWindow.propagate-natural-height)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 13:48:46 +
with message-id 
and subject line Bug#837738: fixed in nautilus 3.21.92-2
has caused the Debian Bug report #837738,
regarding Fails to start, Invalid property: 
GtkScrolledWindow.propagate-natural-height
to be marked as done.

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

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


-- 
837738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nautilus
Version: 3.21.92-1
Severity: grave

When running nautilus, one get's

(nautilus:28168): Gtk-CRITICAL **: Error building template class
'NautilusToolbar' for an instance of type 'NautilusToolbar': .:194:52
Invalid property: GtkScrolledWindow.propagate-natural-height
Segmentation fault



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

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

Versions of packages nautilus depends on:
ii  desktop-file-utils 0.23-1
ii  gsettings-desktop-schemas  3.21.4-2
ii  gvfs   1.29.92-1
ii  libatk1.0-02.21.90-2
ii  libc6  2.24-2
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libexempi3 2.3.0-2
ii  libexif12  0.6.21-2
ii  libgail-3-03.21.5-3
ii  libgdk-pixbuf2.0-0 2.35.5-1
ii  libglib2.0-0   2.49.7-1
ii  libglib2.0-data2.49.7-1
ii  libgnome-autoar-0-00.1.1-4
ii  libgnome-desktop-3-12  3.21.92-1
ii  libgtk-3-0 3.21.5-3
ii  libnautilus-extension1a3.21.92-1
ii  libpango-1.0-0 1.40.2-1
ii  libselinux12.5-3
ii  libtracker-sparql-1.0-01.9.1-2
ii  libx11-6   2:1.6.3-1
ii  nautilus-data  3.21.92-1
ii  shared-mime-info   1.7-1

Versions of packages nautilus recommends:
ii  gnome-sushi  3.21.91-1
ii  gvfs-backends1.29.92-1
ii  librsvg2-common  2.40.16-1

Versions of packages nautilus suggests:
ii  brasero3.12.1-2
ii  eog3.20.4-1
ii  evince [pdf-viewer]3.21.4-1
ii  okular [pdf-viewer]4:16.04.2-1
ii  totem  3.21.91-1
ii  tracker1.9.1-2
ii  vlc [mp3-decoder]  2.2.4-3+b4
ii  vlc-nox [mp3-decoder]  2.2.4-3+b4
ii  xdg-user-dirs  0.15-2
ii  xpdf [pdf-viewer]  3.04-1+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nautilus
Source-Version: 3.21.92-2

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

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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated nautilus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 15:30:00 +0200
Source: nautilus
Binary: nautilus libnautilus-extension1a libnautilus-extension-dev 
gir1.2-nautilus-3.0 nautilus-data
Architecture: source
Version: 3.21.92-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Biebl 
Description:
 gir1.2-nautilus-3.0 - libraries for nautilus components - gir bindings
 libnautilus-extension-dev - libraries for nautilus components - development 
version
 libnautilus-extension1a - libraries for nautilus components - runtime version
 nautilus   - file manager and graphical shell for GNOME
 nautilus-data - data files for nautilus
Closes: 837738
Changes:
 nautilus (3.21.92-2) unstable; urgency=medium
 .
   [ Jeremy Bicha ]
   * Multiarchify
   * Add multiarch_fallback.patch:
 Load extensions from non-multiarch directory too
 .
   [ Laurent Bigonville ]
   * Bump libgtk-3-dev to 3.21.6, nautilus now uses 

Processed: Re: Bug#837759: network configuration stops working reliably

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #837759 [systemd] network configuration stops working reliably
Added tag(s) moreinfo.

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

Bug#837759: network configuration stops working reliably

[Felipe Sateler]

Control: tags -1 moreinfo

On 14 September 2016 at 06:59, Wolfgang Walter  wrote:
> Package: systemd
> Version: 231-6
> Severity: grave
>
> Starting with version 231-6 the configuration of network interfaces stops
> working reliably when rebooting a system. Downgrading to 231-5 fixes the
> problem.
>
> Symptoms: If a network interface is configured using /etc/network/interfaces
> it seems that systemd now sometimes removes the configured ip4 and/or ipv6
> addresses in the boot process. It also seems to remove routes of network
> interfaces configured manually or with /etc/network/interfaces if the link
> state changes.
>
> This seems not only be the case with interfaces configured via /etc/network/
> interfaces but with any interface one creates and assigns ip addresses
> manually.
>
> I tested this with a script:
>
> #!/bin/sh
> if [ "$1" = start ]; then
> ip link del TEST >/dev/null 2>&1 || true
> ip link add name TEST type dummy
> ip -b - <<"EOF"
> link set TEST up
> addr add 10.10.10.10/32 dev TEST nodad
> addr add 2a01:1:1:1::1/128 dev TEST nodad
> addr add 2a01:1:1:1::2/128 dev TEST nodad
> addr add 2a01:1:1:1::3/128 dev TEST nodad
> addr add 2a01:1:1:1::4/128 dev TEST nodad
> addr add 2a01:1:1:1::5/128 dev TEST nodad
> EOF
> ip addr ls TEST
> sleep 2
> elif [ "$1" = stop ]; then
> ip addr flush dev TEST
> ip link del TEST
> fi
>
> which I start with as a systemd oneshot service with
> Before=systemd-networkd.service
>
> I can see in the journal that TEST has all adresses assigned but with 231-6 it
> looses them again (probably when systemd-networkd.service starts). With 231-5
> or earlier this in not the case.

It appears you are using systemd-networkd. Could you please attach
your networkd configuration?

Version 231-6 is built with iptables support, so that may be causing
an interaction that was not visible before.

-- 

Saludos,
Felipe Sateler

Bug#829752: please lower the severity

[Thomas Lange]

IMO the justification on the severity is strange. A package should not
need to handle every case of corrupted parts on disk or otherwise
strange broken things. In this case your whole system is broken, and
you should fix this anyhow, but not blame netfilter-persistent for not
handling this correctly.

Please lower the severity, so that netfilter-persistent is going back
into testing.

-- 
regards Thomas

Bug#837744: marked as done (gupnp-dlna: FTBFS: usr/bin/ld: cannot find -lgupnp-dlna-gst-2.0)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 12:35:17 +
with message-id 
and subject line Bug#837744: fixed in gupnp-dlna 0.10.5-3
has caused the Debian Bug report #837744,
regarding gupnp-dlna: FTBFS: usr/bin/ld: cannot find -lgupnp-dlna-gst-2.0
to be marked as done.

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

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


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

Dear Maintainer,

gupnp-dlna fails to build from source in unstable/amd64:

  [..]

  test -d "$destdir" || mkdir -p "$destdir"; \
  test -f 
/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5/doc/gupnp-dlna-metadata/$file
 && \
  cp -pf 
/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5/doc/gupnp-dlna-metadata/$file
 
/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5/doc/gupnp-dlna-metadata/$file
 || true; \
  done; \
  fi; \
  fi
  /bin/mkdir -p xml && ( \
echo ""; \
echo "https://bugzilla.gnome.org/enter_bug.cgi?product=gupnp=gupnp-dlna\;>";
 \
echo ""; \
echo ""; \
echo ""; \
echo "http://www.gupnp.org/\;>"; \
echo ""; \
  ) > xml/gtkdocentities.ent
  touch setup-build.stamp
  _source_dir='' ; \
  for i in ./../../libgupnp-dlna/metadata ; do \
  _source_dir="${_source_dir} --source-dir=$i" ; \
  done ; \
  gtkdoc-scan --module=gupnp-dlna-metadata --ignore-headers="" ${_source_dir} 
--deprecated-guards="GUPNP_DISABLE_DEPRECATED" 
  if grep -l '^..*$' gupnp-dlna-metadata.types > /dev/null 2>&1 ; then \
  scanobj_options=""; \
  gtkdoc-scangobj 2>&1 --help | grep  >/dev/null "\-\-verbose"; \
  if test "$?" = "0"; then \
  if test "x" = "x1"; then \
  scanobj_options="--verbose"; \
  fi; \
  fi; \
  CC="/bin/bash ../../libtool --tag=CC --mode=compile gcc  
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -g -O0 -g -Wall" 
LD="/bin/bash ../../libtool --tag=CC --mode=link gcc -lgobject-2.0 -lglib-2.0  
-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -g -O0 -g -Wall  
-Wl,-z,relro" RUN="/bin/bash ../../libtool --mode=execute" CFLAGS="-I../.. -g 
-O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -g -O0 -g -Wall" 
LDFLAGS="../../libgupnp-dlna/libgupnp-dlna-2.0.la -Wl,-z,relro" \
  gtkdoc-scangobj  $scanobj_options --module=gupnp-dlna-metadata; \
  else \
  for i in gupnp-dlna-metadata.args gupnp-dlna-metadata.hierarchy 
gupnp-dlna-metadata.interfaces gupnp-dlna-metadata.prerequisites 
gupnp-dlna-metadata.signals ; do \
  test -f $i || touch $i ; \
  done \
  fi
  touch scan-build.stamp
  _source_dir='' ; \
  for i in ./../../libgupnp-dlna/metadata ; do \
  _source_dir="${_source_dir} --source-dir=$i" ; \
  done ; \
  gtkdoc-mkdb --module=gupnp-dlna-metadata --output-format=xml 
--expand-content-files="" --main-sgml-file=gupnp-dlna-metadata-docs.sgml 
${_source_dir} --sgml-mode --output-format=xml
  touch sgml-build.stamp
  rm -rf html && mkdir html && \
  mkhtml_options=""; \
  gtkdoc-mkhtml 2>&1 --help | grep  >/dev/null "\-\-verbose"; \
  if test "$?" = "0"; then \
if test "x" = "x1"; then \
  mkhtml_options="$mkhtml_options --verbose"; \
fi; \
  fi; \
  gtkdoc-mkhtml 2>&1 --help | grep  >/dev/null "\-\-path"; \
  if test "$?" = "0"; then \
mkhtml_options="$mkhtml_options 
--path=\"/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5/doc/gupnp-dlna-metadata\"";
 \
  fi; \
  cd html && gtkdoc-mkhtml $mkhtml_options  gupnp-dlna-metadata 
../gupnp-dlna-metadata-docs.sgml
  gtkdoc-fixxref --module=gupnp-dlna-metadata --module-dir=html 
--html-dir=/usr/share/gtk-doc/html --extra-dir=/usr/share/gtk-doc/html/gobject 
--extra-dir=/usr/share/gtk-doc/html/glib 

Bug#837744: marked as pending

[Andreas Henriksson]

tag 837744 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-gnome/gupnp-dlna.git;a=commitdiff;h=b1f15ef

---
commit b1f15efba944b8335c1c3288278029a1ee3e5e9b
Author: Andreas Henriksson 
Date:   Wed Sep 14 14:20:42 2016 +0200

Update debian/changelog

diff --git a/debian/changelog b/debian/changelog
index 16363be..60244e5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+gupnp-dlna (0.10.5-3) unstable; urgency=medium
+
+  * debian/rules: use --no-parallel to avoid FTBFS (Closes: #837744)
+
+ -- Andreas Henriksson   Wed, 14 Sep 2016 14:20:36 +0200
+
 gupnp-dlna (0.10.5-2) unstable; urgency=medium
 
   * Convert from cdbs to dh

Processed: Bug#837744 marked as pending

[Debian Bug Tracking System]

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

> tag 837744 pending
Bug #837744 [src:gupnp-dlna] gupnp-dlna: FTBFS: usr/bin/ld: cannot find 
-lgupnp-dlna-gst-2.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: gupnp-dlna: FTBFS: usr/bin/ld: cannot find -lgupnp-dlna-gst-2.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #837744 [src:gupnp-dlna] gupnp-dlna: FTBFS: usr/bin/ld: cannot find 
-lgupnp-dlna-gst-2.0
Added tag(s) confirmed.

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

Bug#837744: gupnp-dlna: FTBFS: usr/bin/ld: cannot find -lgupnp-dlna-gst-2.0

[Andreas Henriksson]

Control: tags -1 + confirmed

Hello Chris Lamb.

Thanks for your bug report.

On Wed, Sep 14, 2016 at 08:27:10AM +0100, Chris Lamb wrote:
[...]
> gupnp-dlna fails to build from source in unstable/amd64:
[...]

Sorry I missed it but I'm actually aware that this package fails
to build in parallell. It's a long-standing issue in the upstream
build system. If someone would volunteer to locate the problem
and send a patch upstream that would be much appreciated.
I'll just add --no-parallell to close this for now...

Regards,
Andreas Henriksson

Bug#735347: marked as done (Sourceless file)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 11:50:21 +
with message-id 
and subject line Bug#735347: fixed in bacula-doc 7.4.3-1
has caused the Debian Bug report #735347,
regarding Sourceless file
to be marked as done.

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

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


-- 
735347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bacula-doc
Severity: serious
User: debian...@lists.debian.org
Usertags: source-contains-prebuilt-flash-object
X-Debbugs-CC: ftpmas...@debian.org

I could not find the source of:
   home-page/conferences/T5RrEVAzdM4


Bastien
--- End Message ---
--- Begin Message ---
Source: bacula-doc
Source-Version: 7.4.3-1

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

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

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

Debian distribution maintenance software
pp.
Carsten Leonhardt  (supplier of updated bacula-doc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Sep 2016 12:56:53 +0200
Source: bacula-doc
Binary: bacula-doc
Architecture: source
Version: 7.4.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian Bacula Team 
Changed-By: Carsten Leonhardt 
Description:
 bacula-doc - Documentation for Bacula
Closes: 735347
Changes:
 bacula-doc (7.4.3-1) unstable; urgency=low
 .
   * New upstream version.
   * Removed inactive uploaders, added myself.
   * Source changed significantly (Closes: #735347).
   * Revamped almost all of debian/*.
Checksums-Sha1:
 ea2f5fe2ea691d0aaff494e2b1c12c8d5008533e 1990 bacula-doc_7.4.3-1.dsc
 cc1b33f99e069256071ebdcce71fc4b603eeb44f 44510956 bacula-doc_7.4.3.orig.tar.bz2
 82a1c0a2172a64d7aa484e4b914363f0ff2ebb6e 11880 bacula-doc_7.4.3-1.debian.tar.xz
Checksums-Sha256:
 60212cf058b4b98556cc58b41857d2e16246fc9ffbeffe9fef740018a48133a3 1990 
bacula-doc_7.4.3-1.dsc
 19d8998f7065fe28433ee5932f786d566205073e5556db84adcb39132881fb59 44510956 
bacula-doc_7.4.3.orig.tar.bz2
 6af99029c5ce38b43c8e040c7e88d533525870094982db6dd87191786e369cc6 11880 
bacula-doc_7.4.3-1.debian.tar.xz
Files:
 b6070cdfae9b4ec03bfbf76850ebdc3d 1990 doc optional bacula-doc_7.4.3-1.dsc
 a97de09e663af20102423f983321520e 44510956 doc optional 
bacula-doc_7.4.3.orig.tar.bz2
 0e8f1c556595849418e7e16dc4355b4b 11880 doc optional 
bacula-doc_7.4.3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX2TerAAoJEFbggnbEQhZ0Ez4P/0YVihMiNVu6dKOLDBstvodV
Ld/V7bhV3xX7eA92Qw+Ugc8QxjQBScRzGR53Lb90J2GmOZnKpW04OxVV+antvY1A
Mx82+Tpb928lkmOWAWjOZ+PoN1L+3jXzqdxzrI+QI+HQ4LeVcSdnw4lNg4L5puK6
1yyUUenNXdBenPoQXpujm0O8OL98ye8lDFcPd1OgQ+7zQHKJq044AvHlpO2sUpU1
ep1hZXcQV2/NxwWldPkpwO/MuY6TE9oX8x78RzADtOQvETM3SDGNxl4H29rIFwQl
W9jDJCNwl00waAyJKfRGr1578xqG9XFi/h4eR7G1Rfu2HTgg5zP0ABxFSpDvdXI3
623SsNdxeE2ON/eCUD0gPYuCSgfqlFGl721c56vzcjkVW34GQQQGSkRjn5Sdc8Aw
19/wkSW38Qbql4JqgFTqmmtH6p57eMp5Z0SIUilwobW/gixq5bi4C2iFAnBd8qRq
eShpp6Jd2f71MYB019egnvR49qTamLYRG105DoiSyaU2WCPJfiAYo1nHfIGoaudN
8li0iIEoA73IMzl08GxBtTyqmTyCNH8RTYS+rHh5OSmZZc4byZmWkv7ZAQRs9o0x
ulZfh3o0yXm8xgnTXb0JuMiLtC58+YVxFtUgw/acTEfiPX47QvS3/PmNcXppObPL
fjKrbJap+w4+RlHXBXDX
=WtYz
-END PGP SIGNATURE End Message ---

Bug#832077: Info received (emacs clutter screen on windows switch)

[Vincent Lefevre]

On 2016-09-14 13:11:20 +0200, Marco d'Itri wrote:
> On Sep 14, Vincent Lefevre  wrote:
> > IMHO, a warning in this case is bad. This is just debugging
> > information, which annoys the end user. If the goal was to make
> > the cause of the problem visible enough to that the user could
> > report a bug, then fine, but there should be an *easy* way to
> > silence this warning (e.g. once the bug has been reported),
> > without other side effects.
> This is even more broken, because for some reason the errors end up in 
> kern.log!

That's strange. For the Gtk version of Emacs, on my machines, they
just remain on stderr (thus in the terminal, when I run Emacs from
a terminal).

I also get Gtk messages from gcr-prompter in kern.log, but this is
not this bug (this also occurs with libgtk-3-0 3.20.9-1).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#832077: Info received (emacs clutter screen on windows switch)

[Marco d'Itri]

On Sep 14, Vincent Lefevre  wrote:

> IMHO, a warning in this case is bad. This is just debugging
> information, which annoys the end user. If the goal was to make
> the cause of the problem visible enough to that the user could
> report a bug, then fine, but there should be an *easy* way to
> silence this warning (e.g. once the bug has been reported),
> without other side effects.
This is even more broken, because for some reason the errors end up in 
kern.log!

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#837614: Use and abuse of the unreproducible tag

[Andreas Tille]

On Tue, Sep 13, 2016 at 07:38:37PM +0200, Markus Koschany wrote:
> 
> What I find disturbing is that we really think that shaming the
> maintainer would be a better approach.

I also consider the time of all involved persons (bug reporter,
maintainer, posters and readers on this list) well better spent if the
initial mail here would have been

   a) more friendly
   b) coming better to the point rather than inventing unrelated
  examples not connected to the issue

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#836713: marked as done (usbguard: FTBFS: No package 'systemd' found)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 10:32:36 +
with message-id 
and subject line Bug#836713: fixed in usbguard 0.5.14+ds1-2
has caused the Debian Bug report #836713,
regarding usbguard: FTBFS: No package 'systemd' found
to be marked as done.

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

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


-- 
836713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: usbguard
Version: 0.5.14+ds1-1
Severity: important
Justification: fails to build from source

The hppa build of usbguard failed:

  Package systemd was not found in the pkg-config search path.
  Perhaps you should add the directory containing `systemd.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'systemd' found
  configure: error: in `/<>/usbguard-0.5.14+ds1':
  configure: error: Cannot detect the systemd system unit dir

AFAICT, systemd.pc comes from the systemd package; please try
declaring a build dependency on it.

Thanks!
--- End Message ---
--- Begin Message ---
Source: usbguard
Source-Version: 0.5.14+ds1-2

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

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

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

Debian distribution maintenance software
pp.
Muri Nicanor  (supplier of updated usbguard package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Sep 2016 18:39:53 +0200
Source: usbguard
Binary: libusbguard-dev libusbguard0 usbguard usbguard-applet-qt
Architecture: source
Version: 0.5.14+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Muri Nicanor 
Changed-By: Muri Nicanor 
Description:
 libusbguard-dev - USB device authorization policy framework - development files
 libusbguard0 - USB device authorization policy framework - shared library
 usbguard   - USB device authorization policy framework
 usbguard-applet-qt - USB device authorization policy framework - qt applet
Closes: 836712 836713 837175 837176
Changes:
 usbguard (0.5.14+ds1-2) unstable; urgency=medium
 .
   * d/control:
- Add systemd to build dependencies (Closes: #836713)
- Change architectures to linux-any in d/control
   * d/rules
- Add sysconfdir flag to autoconf (Closes: #837176)
   * d/patches/
- Fix mips build (Closes: #836712)
- Set correct IPCAllowedGroups (Closes: #837175)
Checksums-Sha1:
 a444d7047698c6e9292dfe27b27986a2ca7d9b48 2270 usbguard_0.5.14+ds1-2.dsc
 54d6da684aa81867d26005acb1d075008eeb7f41 16152 
usbguard_0.5.14+ds1-2.debian.tar.xz
Checksums-Sha256:
 35482e0cc24f8633c0ed116bca31414e1a8e410731c53b6ece4678d611ee059a 2270 
usbguard_0.5.14+ds1-2.dsc
 666caf46c13f0600b11e5611c71498ddca18bbe4e66c038c5c4a359c52e90d72 16152 
usbguard_0.5.14+ds1-2.debian.tar.xz
Files:
 170100f4076b667a6c1e1e4f275df3f7 2270 utils optional usbguard_0.5.14+ds1-2.dsc
 0a1f2fc6501da246b7eee364e35c90cf 16152 utils optional 
usbguard_0.5.14+ds1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJX2RMdAAoJEPNPCXROn13ZmMUQAImb+To8jy4RQISfKtqDq4SZ
hwamw2sF5TrEz5pkkPa7ljSWCr/pHXpAqNBnJPvm9qc6l7+yNEH5s49dFHhm13qD
igl1/5hBlKKsdrBqAQ8nItkvGNwWq7Y9aj51q24f/w60u8ORMCfJ2g17gaUX5J4s
af9pbuXNpcyQmF7psv/yRtMz/0sQQKWm4j1pOdMt8Mpgwb5HLOXTI/v0cX0vaMGV
F28yCAcevSF+3fB52rLEYlTp62vsicMr813Os6abNXkyT3CC5o10NG+aI5Kq9cSl
8SwXb9tO6+yl+9QpgFq+9BYCuMQh2623iMPmNwiFRzt2GvOei6df2XVcw4ANYEKI
dio+FHb/wHUR4jsB0bTUoQILNX9Z9lUAZPaS0y/AXERWHVkzKqtrQ6p5oJ2GiXIm
UMtzFuQ9DWHMXEsG4hxBYmvDraLsFfjPywUX2qv4t9yZ4OQNfYy7pXMH5fYU2GSR
jn2JZ93FJHziS1lzQbvqTqcjsc4F0bLyM66LFtkTUogLQZsYfTSJQmEzU5inkuEZ
QWk+1vOngXJzljPF2OpRp+RodSS+dkzjwlqUqK6bzi8XU1lQ90rqtZ7sXV1JKMtx
GksINGwErn1vKDA9HYONCROl3PGZq2QxeRkurxqyWRocuB/PW1v8DCoWlQJVXb2y
wisbQqECgiTuitoYgHKo
=gQ1B
-END PGP SIGNATURE End Message ---

Bug#837726: marked as done (gnome-shell-extension-mediaplayer: Not installable with gnome-shell >= 3.21.92)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 10:23:43 +
with message-id 
and subject line Bug#837726: fixed in gnome-shell-extension-mediaplayer 
0~git20160509-3
has caused the Debian Bug report #837726,
regarding gnome-shell-extension-mediaplayer: Not installable with gnome-shell 
>= 3.21.92
to be marked as done.

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

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


-- 
837726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-extension-mediaplayer
Version: 0~git201600509-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-3-22

Hi,

your package gnome-shell-extension-mediaplayer declares a strictly
versioned dependency on gnome-shell. We've uploaded gnome-shell
3.21.92 to unstable, which makes gnome-shell-extension-mediaplayer
uninstallable.

In the past, it was necessary to explicitly declare supported
gnome-shell versions in metadata.json. This was lifted in gnome-shell
3.21.92 [1].

"Nowadays, the user interface has mostly stabilized with most changes
happening under the hood. As a result, extensions written for
previous versions of GNOME Shell are very much expected to keep
working on updates, if it wasn't for the version check that requires
a version bump in the extension metadata. There has been a setting to
disable that check for a while, but it's existence isn't widely known
(hence the common perception that "everything breaks on updates").
While there is still some risk that an out-of-date extension can be
enabled without error, but fails spectacularly later (where we cannot
catch the exception), it is reasonably small by now when compared to
the ~95% of extensions that can be "unbroken", so swap the default
value to disable version checks by default."

As a result, you could drop the gnome-shell << XXX version limitation
altogether. The Debian release cycle is pretty long though, so we
don't know yet if the gnome-shell version in Buster will actually be
compatible with your extension today. We will release Stretch with
GNOME Shell 3.22, so my recommendation would be to use gnome-shell
(<< 3.23) as upper limt.

Modifications for metadata.json are no longer required.

Regards, Michael

[1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-mediaplayer
Source-Version: 0~git20160509-3

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated 
gnome-shell-extension-mediaplayer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 09:18:45 +0100
Source: gnome-shell-extension-mediaplayer
Binary: gnome-shell-extension-mediaplayer
Architecture: source
Version: 0~git20160509-3
Distribution: unstable
Urgency: medium
Maintainer: Simon McVittie 
Changed-By: Simon McVittie 
Description:
 gnome-shell-extension-mediaplayer - GNOME Shell extension to control media 
players
Closes: 837726
Changes:
 gnome-shell-extension-mediaplayer (0~git20160509-3) unstable; urgency=medium
 .
   * Rely on gnome-shell >= 3.21.92 having dropped version-checks
 by default (Closes: #837726)
 - Drop patch to metadata.json. It only declares compatibility with
   3.20, but that's OK because the version-check is disabled by
   default now.
 - Depends: gnome-shell (<< 3.23). This avoids using stretch versions
   of this extension with buster versions of GNOME Shell, since we
   can't predict whether it will be 100% compatible
Checksums-Sha1:
 f0d6f86aeaee045fe80a91cbac3396288a466200 2254 
gnome-shell-extension-mediaplayer_0~git20160509-3.dsc
 bf5558c6aa848656c6b1bc57ca25fe3ad9ed87ec 3192 
gnome-shell-extension-mediaplayer_0~git20160509-3.debian.tar.xz
Checksums-Sha256:
 1ab57947e42d102d86b05a823786012fc94a295f45952a8a71c47199309983b5 2254 

Bug#837727: marked as done (gnome-shell-extension-top-icon-plus: Not installable with gnome-shell >= 3.21.92)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 10:23:48 +
with message-id 
and subject line Bug#837727: fixed in gnome-shell-extension-top-icons-plus 15-3
has caused the Debian Bug report #837727,
regarding gnome-shell-extension-top-icon-plus: Not installable with gnome-shell 
>= 3.21.92
to be marked as done.

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

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


-- 
837727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-extension-top-icon-plus
Version: 15-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-3-22

Hi,

your package gnome-shell-extension-top-icon-plus declares a strictly
versioned dependency on gnome-shell. We've uploaded gnome-shell
3.21.92 to unstable, which makes gnome-shell-extension-top-icon-plus
uninstallable.

In the past, it was necessary to explicitly declare supported
gnome-shell versions in metadata.json. This was lifted in gnome-shell
3.21.92 [1].

"Nowadays, the user interface has mostly stabilized with most changes
happening under the hood. As a result, extensions written for
previous versions of GNOME Shell are very much expected to keep
working on updates, if it wasn't for the version check that requires
a version bump in the extension metadata. There has been a setting to
disable that check for a while, but it's existence isn't widely known
(hence the common perception that "everything breaks on updates").
While there is still some risk that an out-of-date extension can be
enabled without error, but fails spectacularly later (where we cannot
catch the exception), it is reasonably small by now when compared to
the ~95% of extensions that can be "unbroken", so swap the default
value to disable version checks by default."

As a result, you could drop the gnome-shell << XXX version limitation
altogether. The Debian release cycle is pretty long though, so we
don't know yet if the gnome-shell version in Buster will actually be
compatible with your extension today. We will release Stretch with
GNOME Shell 3.22, so my recommendation would be to use gnome-shell
(<< 3.23) as upper limt.

Modifications for metadata.json are no longer required.

Regards, Michael

[1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-top-icons-plus
Source-Version: 15-3

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-top-icons-plus, which is due to be installed in the 
Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated 
gnome-shell-extension-top-icons-plus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 09:01:14 +0100
Source: gnome-shell-extension-top-icons-plus
Binary: gnome-shell-extension-top-icons-plus
Architecture: source
Version: 15-3
Distribution: unstable
Urgency: medium
Maintainer: Simon McVittie 
Changed-By: Simon McVittie 
Description:
 gnome-shell-extension-top-icons-plus - GNOME Shell extension to move system 
tray icons to top bar
Closes: 837727
Changes:
 gnome-shell-extension-top-icons-plus (15-3) unstable; urgency=medium
 .
   * Rely on gnome-shell >= 3.21.92 having dropped version-checks
 by default (Closes: #837727)
 - Drop patch to metadata.json. It only declares compatibility with
   3.20, but that's OK because the version-check is disabled by
   default now.
 - Depends: gnome-shell (<< 3.23). This avoids using stretch versions
   of this extension with buster versions of GNOME Shell, since we
   can't predict whether it will be 100% compatible
Checksums-Sha1:
 44e0405c3d231f34a4f026b329120d34fb7c0a95 2120 
gnome-shell-extension-top-icons-plus_15-3.dsc
 0f1d0339e9de54b0c5bdf1e5a5b7c6ca0f6cff0b 3408 
gnome-shell-extension-top-icons-plus_15-3.debian.tar.xz
Checksums-Sha256:
 bc43da3418af66413b9aa50a43cea5a3712041f270e5592bc7c08199b11fc3b1 2120 

Bug#837725: marked as done (gnome-shell-extension-caffeine: Not installable with gnome-shell >= 3.21.92)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 10:23:38 +
with message-id 
and subject line Bug#837725: fixed in gnome-shell-extension-caffeine 
0~git20160329-3
has caused the Debian Bug report #837725,
regarding gnome-shell-extension-caffeine: Not installable with gnome-shell >= 
3.21.92
to be marked as done.

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

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


-- 
837725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-extension-caffeine
Version: 0~git20160329-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-3-22

Hi,

your package gnome-shell-extension-caffeine declares a strictly
versioned dependency on gnome-shell. We've uploaded gnome-shell
3.21.92 to unstable, which makes gnome-shell-extension-caffeine
uninstallable.

In the past, it was necessary to explicitly declare supported
gnome-shell versions in metadata.json. This was lifted in gnome-shell
3.21.92 [1].

"Nowadays, the user interface has mostly stabilized with most changes
happening under the hood. As a result, extensions written for
previous versions of GNOME Shell are very much expected to keep
working on updates, if it wasn't for the version check that requires
a version bump in the extension metadata. There has been a setting to
disable that check for a while, but it's existence isn't widely known
(hence the common perception that "everything breaks on updates").
While there is still some risk that an out-of-date extension can be
enabled without error, but fails spectacularly later (where we cannot
catch the exception), it is reasonably small by now when compared to
the ~95% of extensions that can be "unbroken", so swap the default
value to disable version checks by default."

As a result, you could drop the gnome-shell << XXX version limitation
altogether. The Debian release cycle is pretty long though, so we
don't know yet if the gnome-shell version in Buster will actually be
compatible with your extension today. We will release Stretch with
GNOME Shell 3.22, so my recommendation would be to use gnome-shell
(<< 3.23) as upper limt.

Modifications for metadata.json are no longer required.

Regards, Michael

[1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-caffeine
Source-Version: 0~git20160329-3

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated 
gnome-shell-extension-caffeine package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 09:19:41 +0100
Source: gnome-shell-extension-caffeine
Binary: gnome-shell-extension-caffeine
Architecture: source
Version: 0~git20160329-3
Distribution: unstable
Urgency: medium
Maintainer: Simon McVittie 
Changed-By: Simon McVittie 
Description:
 gnome-shell-extension-caffeine - GNOME Shell extension to keep your computer 
awake
Closes: 837725
Changes:
 gnome-shell-extension-caffeine (0~git20160329-3) unstable; urgency=medium
 .
   * Rely on gnome-shell >= 3.21.92 having dropped version-checks
 by default (Closes: #837725)
 - Drop patch to metadata.json. It only declares compatibility with
   3.20, but that's OK because the version-check is disabled by
   default now.
 - Depends: gnome-shell (<< 3.23). This avoids using stretch versions
   of this extension with buster versions of GNOME Shell, since we
   can't predict whether it will be 100% compatible
Checksums-Sha1:
 40843c498dd12c3a92ea37a460287249645a2a15 2157 
gnome-shell-extension-caffeine_0~git20160329-3.dsc
 ff7a26d8b0ebb903b1ad90736a29d9cab03df587 3756 
gnome-shell-extension-caffeine_0~git20160329-3.debian.tar.xz
Checksums-Sha256:
 cc5e874dd00d280df94ceed11ba1410b7b8ec39647087cf6325941085d007045 2157 
gnome-shell-extension-caffeine_0~git20160329-3.dsc
 

Bug#837759: network configuration stops working reliably

[Wolfgang Walter]

Package: systemd
Version: 231-6
Severity: grave

Starting with version 231-6 the configuration of network interfaces stops 
working reliably when rebooting a system. Downgrading to 231-5 fixes the 
problem.

Symptoms: If a network interface is configured using /etc/network/interfaces 
it seems that systemd now sometimes removes the configured ip4 and/or ipv6 
addresses in the boot process. It also seems to remove routes of network 
interfaces configured manually or with /etc/network/interfaces if the link 
state changes.

This seems not only be the case with interfaces configured via /etc/network/
interfaces but with any interface one creates and assigns ip addresses 
manually.

I tested this with a script:

#!/bin/sh
if [ "$1" = start ]; then
ip link del TEST >/dev/null 2>&1 || true
ip link add name TEST type dummy
ip -b - <<"EOF"
link set TEST up
addr add 10.10.10.10/32 dev TEST nodad
addr add 2a01:1:1:1::1/128 dev TEST nodad
addr add 2a01:1:1:1::2/128 dev TEST nodad
addr add 2a01:1:1:1::3/128 dev TEST nodad
addr add 2a01:1:1:1::4/128 dev TEST nodad
addr add 2a01:1:1:1::5/128 dev TEST nodad
EOF
ip addr ls TEST
sleep 2
elif [ "$1" = stop ]; then
ip addr flush dev TEST
ip link del TEST
fi

which I start with as a systemd oneshot service with
Before=systemd-networkd.service

I can see in the journal that TEST has all adresses assigned but with 231-6 it 
looses them again (probably when systemd-networkd.service starts). With 231-5 
or earlier this in not the case.


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

Processed: perl 5.24 transition severities

[Debian Bug Tracking System]

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

> # The transition is now imminent
> severity 825011 serious
Bug #825011 [libdata-alias-perl] libdata-alias-perl: FTBFS with Perl 5.24: 
undefined symbol: LEAVESUB
Severity set to 'serious' from 'important'
> severity 825012 serious
Bug #825012 [libalgorithm-permute-perl] libalgorithm-permute-perl: FTBFS with 
Perl 5.24: undefined symbol: PUSHBLOCK
Severity set to 'serious' from 'important'
> severity 825231 serious
Bug #825231 [libdevel-beginlift-perl] libdevel-beginlift-perl: FTBFS with Perl 
5.24: t/constcalc.t failure
Severity set to 'serious' from 'important'
> severity 825524 serious
Bug #825524 [liblexical-underscore-perl] liblexical-underscore-perl: FTBFS with 
Perl 5.24: Can't use global $_ in "my"
Severity set to 'serious' from 'important'
> severity 825611 serious
Bug #825611 [libparse-http-useragent-perl] libparse-http-useragent-perl: FTBFS 
with newer version.pm: t/02-parser.t failure
Severity set to 'serious' from 'important'
> severity 825762 serious
Bug #825762 [libtext-sprintfn-perl] libtext-sprintfn-perl: FTBFS with Perl 
5.24: t/01-basics.t failure
Severity set to 'serious' from 'important'
> severity 834800 serious
Bug #834800 [libkavorka-perl] libkavorka-perl: depends on libdata-alias-perl, 
broken with Perl 5.24
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
825011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825011
825012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825012
825231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825231
825524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825524
825611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825611
825762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825762
834800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#837614: python-geopandas: FTBFS in testing (failing tests)

[Sebastiaan Couwenberg]

On 09/13/2016 11:10 AM, Sebastiaan Couwenberg wrote:
> On 09/12/2016 11:29 PM, Santiago Vila wrote:
>> I tried to build this package in stretch with "dpkg-buildpackage -A"
>> (which is what the "Arch: all" autobuilder would do to build it)
>> but it failed:
> 
> Like the Stetl issue I cannot reproduce it in unstable, and it also
> seems to be caused by gdal in testing not having been rebuilt with proj
> 4.9.3. gdal is waiting for perl to migrate to testing which should
> happen tomorrow.

Confirmed fixed in stretch now that gdal (2.1.1+dfsg-4) has migrated to
testing.

Processed: block 830200 with 834249

[Debian Bug Tracking System]

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

> block 830200 with 834249
Bug #830200 [release.debian.org] transition: perl
830200 was blocked by: 834797 834800 825524 825762 825231 834796 836162 836636 
825014 825609 834799 834795 837719 825611 834798 825012
830200 was not blocking any bugs.
Added blocking bug(s) of 830200: 834249
> thanks
Stopping processing here.

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

Processed: unblock 830200 with 836162

[Debian Bug Tracking System]

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

> unblock 830200 with 836162
Bug #830200 [release.debian.org] transition: perl
830200 was blocked by: 836162 825609 834799 836636 825231 825012 837719 825524 
834797 825762 834798 825611 834249 834796 825014 834800 834795
830200 was not blocking any bugs.
Removed blocking bug(s) of 830200: 836162
> thanks
Stopping processing here.

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

Bug#837622: python-stetl: FTBFS in testing (failing tests)

[Sebastiaan Couwenberg]

On 09/13/2016 10:45 AM, Sebastiaan Couwenberg wrote:
> On 09/13/2016 12:07 AM, Santiago Vila wrote:
>> I tried to build this package in stretch with "dpkg-buildpackage -A"
>> (which is what the "Arch: all" autobuilder would do to build it)
>> but it failed:
> 
> I cannot reproduce this is in unstable, so I suspect it's caused by gdal
> in testing not having been rebuilt with proj 4.9.3 yet. It should
> migrate to testing tomorrow.

Confirmed fixed in stretch now that gdal (2.1.1+dfsg-4) has migrated to
testing.

Bug#837682: libconfig-model-itself-perl: FTBFS in unstable (failing tests)

[Dominique Dumont]

On Tue, 13 Sep 2016 16:46:47 +0200 Dominique Dumont  wrote:
> Looks like I cannot find a way to handle the removal of '.' from @INC
> I may need to avoid using 'do' and revisit completely the way model files
> are loaded...

Fortunately, it was a stupid mistake on my side :-$ 
I can eschew a rewrite of model loader (for now...)

To be on the safe side, I need to update upstream both libconfig-model-perl 
and libconfig-model-itself-perl.

The first is done, the latter will be released in the next few days.

All the best

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

Bug#820965: marked as pending

[Vlad Orlov]

Hi,

I'd like to know if there's any progress on uploading the new
version to jessie-security. Just want to check if the update
would fix https://bugs.debian.org/831851 as well.

Processed: fix tobi's mess

[Debian Bug Tracking System]

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

> reopen 837595
Bug #837595 {Done: Tobias Frost } [src:gnome-shell-pomodoro] 
gnome-shell-pomodoro: Not compatible with gnome-shell 3.21.x/3.22
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 
gnome-shell-extension-suspend-button/0~git20160525-2.
> fixed 837495 gnome-shell-extension-suspend-button/0~git20160525-2
Bug #837495 [src:gnome-shell-extension-suspend-button] 
gnome-shell-extension-suspend-button: uninstallable in sid: Depends: 
gnome-shell (< 3.21) but 3.21.91-2 is to be installed
Bug #837592 [src:gnome-shell-extension-suspend-button] 
gnome-shell-extension-suspend-button: Not compatible with gnome-shell 
3.21.x/3.22
Marked as fixed in versions 
gnome-shell-extension-suspend-button/0~git20160525-2.
Marked as fixed in versions 
gnome-shell-extension-suspend-button/0~git20160525-2.
> thanks
Stopping processing here.

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

Processed: fixed 832285 in 2.0.1-5, found 836858 in 3.4.1+dfsg-2

[Debian Bug Tracking System]

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

> fixed 832285 2.0.1-5
Bug #832285 {Done: Alastair McKinstry } [libopenmpi2] 
libopenmpi2: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/openmpi/lib/libompitrace.so.0.0.0
Marked as fixed in versions openmpi/2.0.1-5.
> found 836858 3.4.1+dfsg-2
Bug #836858 [nomacs-l10n] nomacs-l10n: fails to upgrade from 'sid' - trying to 
overwrite /usr/share/nomacs/translations/nomacs_als.qm
Marked as found in versions nomacs/3.4.1+dfsg-2.
> thanks
Stopping processing here.

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

Bug#832077: Info received (emacs clutter screen on windows switch)

[Vincent Lefevre]

On 2016-09-14 11:40:41 +0900, Yasushi SHOJI wrote:
> On Thu, 08 Sep 2016 10:38:09 +0900,
> Leon Meier wrote:
> > 
> > By the way, I don't know who is the culprit: libgtk-3-0, emacs, or
> > someone else. So please consider my found / nofound tags just as
> > additional information on my configuration rather as a bug source
> > hint. Sorry about that.
> 
> https://mail.gnome.org/archives/commits-list/2016-May/msg06553.html
> 
> I found this commit on Gtk+. So I assume this is an intended change
> for Gtk+ 3.22, no?

According to the bug report it refers:

  https://bugzilla.gnome.org/show_bug.cgi?id=765410

there was already an issue since Gtk+ 3.20 at least. The warning was
added recently to signal that this was the fault of the application,
which did something wrong.

IMHO, a warning in this case is bad. This is just debugging
information, which annoys the end user. If the goal was to make
the cause of the problem visible enough to that the user could
report a bug, then fine, but there should be an *easy* way to
silence this warning (e.g. once the bug has been reported),
without other side effects.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#832077: Info received (emacs clutter screen on windows switch)

[Vincent Lefevre]

On 2016-09-13 19:58:48 +0100, D. B. wrote:
> It's not the maintainers fault if 3rd-party software is not up to
> date with the libraries on which it relies. And by using unstable or
> testing, the user accepts the very likely possibility of temporary
> breakage.

This bug had been reassigned to the library. So, this appears to be a
bug in gtk+3.0 rather than 3rd-party software.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#835770: Failure is triggered by fix to #834281

[Sunil Mohan Adapa]

Hello,

Recently test cases where failing in libgnupg-interface-perl
(https://bugs.debian.org/834281) due to gpg binary now defaulting to
gpg2 in Debian. It was patched to explicitly use 'gpg1' binary instead
of 'gpg'.  This is causing the test suite and monkeysphere to use
different gpg binaries leading to test case failure.  One solution could
be to patch the test suite in Debian to use gpg1 instead of gpg until
monkeysphere and libgnupg-interface-perl support gpg2.

-- 
Sunil



signature.asc
Description: OpenPGP digital signature

Bug#837745: sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

[Sven Joachim]

Control: reassign -1 xml-core 0.13+nmu2
Control: tags -1 stretch sid

On 2016-09-14 08:27 +0100, Chris Lamb wrote:

>   dh_installxmlcatalogs
>   dh_installxmlcatalogs: Unexpected debhelper version format

This is a bug in dh_installxmlcatalogs which contains the following gem:

,
| use Debian::Debhelper::Dh_Lib;
| use Debian::Debhelper::Dh_Version;
| 
| $Debian::Debhelper::Dh_Version::version =~ /^(\d+)\.(\d+)/
|   or error("Unexpected debhelper version format");
`

There is currently no dot in the debhelper version number:

,
| $ cat /usr/share/perl5/Debian/Debhelper/Dh_Version.pm
| package Debian::Debhelper::Dh_Version;
| $version='10';
| 1
`

Cheers,
   Sven

Processed: Re: Bug#837745: sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 xml-core 0.13+nmu2
Bug #837745 [src:sgml-data] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug reassigned from package 'src:sgml-data' to 'xml-core'.
No longer marked as found in versions sgml-data/2.0.10.
Ignoring request to alter fixed versions of bug #837745 to the same values 
previously set
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Marked as found in versions xml-core/0.13+nmu2.
> tags -1 stretch sid
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added tag(s) sid and stretch.

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

Bug#837028: [Pkg-gauche-devel] Bug#837028: gauche-gtk: FTBFS: pango-font.c:249:44: error: 'desc' undeclared (first use in this function)

[Jens Thiele]

forwarded upstream:
https://github.com/shirok/Gauche-gtk2/issues/5

Bug#835284: marked as done (urdfdom: FTBFS: Could not find a configuration file for package "urdfdom_headers" that is 367 compatible with requested version "0.4".)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 09:42:42 +0200
with message-id 
and subject line urdfdom: FTBFS: Could not find a configuration file for 
package "urdfdom_headers" that is 367 compatible with requested version "0.4".
has caused the Debian Bug report #835284,
regarding urdfdom: FTBFS: Could not find a configuration file for package 
"urdfdom_headers" that is 367 compatible with requested version "0.4".
to be marked as done.

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

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


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

Dear Maintainer,

urdfdom fails to build from source in unstable/amd64:

  [..]

  CMAKE_INSTALL_LIBDIR:PATH=lib/x86_64-linux-gnu
  
  //program executables (libexec)
  CMAKE_INSTALL_LIBEXECDIR:PATH=libexec
  
  //locale-dependent data (DATAROOTDIR/locale)
  CMAKE_INSTALL_LOCALEDIR:PATH=
  
  //No help, variable specified on the command line.
  CMAKE_INSTALL_LOCALSTATEDIR:UNINITIALIZED=/var
  
  //man documentation (DATAROOTDIR/man)
  CMAKE_INSTALL_MANDIR:PATH=
  
  //C header files for non-gcc (/usr/include)
  CMAKE_INSTALL_OLDINCLUDEDIR:PATH=/usr/include
  
  //Install path prefix, prepended onto install directories.
  CMAKE_INSTALL_PREFIX:PATH=/usr
  
  //system admin executables (sbin)
  CMAKE_INSTALL_SBINDIR:PATH=sbin
  
  //modifiable architecture-independent data (com)
  CMAKE_INSTALL_SHAREDSTATEDIR:PATH=com
  
  //No help, variable specified on the command line.
  CMAKE_INSTALL_SYSCONFDIR:UNINITIALIZED=/etc
  
  //Path to a program.
  CMAKE_LINKER:FILEPATH=/usr/bin/ld
  
  //Path to a program.
  CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make
  
  //Flags used by the linker during the creation of modules.
  CMAKE_MODULE_LINKER_FLAGS:STRING= -Wl,-z,relro
  
  //Flags used by the linker during debug builds.
  CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=
  
  //Flags used by the linker during release minsize builds.
  CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=
  
  //Flags used by the linker during release builds.
  CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=
  
  //Flags used by the linker during Release with Debug Info builds.
  CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=
  
  //Path to a program.
  CMAKE_NM:FILEPATH=/usr/bin/nm
  
  //Path to a program.
  CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy
  
  //Path to a program.
  CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump
  
  //Value Computed by CMake
  CMAKE_PROJECT_NAME:STATIC=urdfdom
  
  //Path to a program.
  CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib
  
  //Flags used by the linker during the creation of dll's.
  CMAKE_SHARED_LINKER_FLAGS:STRING= -Wl,-z,relro
  
  //Flags used by the linker during debug builds.
  CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=
  
  //Flags used by the linker during release minsize builds.
  CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=
  
  //Flags used by the linker during release builds.
  CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=
  
  //Flags used by the linker during Release with Debug Info builds.
  CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=
  
  //If set, runtime paths are not added when installing shared libraries,
  // but are added when building.
  CMAKE_SKIP_INSTALL_RPATH:BOOL=NO
  
  //If set, runtime paths are not added when using shared libraries.
  CMAKE_SKIP_RPATH:BOOL=NO
  
  //Flags used by the linker during the creation of static libraries.
  CMAKE_STATIC_LINKER_FLAGS:STRING=
  
  //Flags used by the linker during debug builds.
  CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=
  
  //Flags used by the linker during release minsize builds.
  CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=
  
  //Flags used by the linker during release builds.
  CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=
  
  //Flags used by the linker during Release with Debug Info builds.
  CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=
  
  //Path to a program.
  CMAKE_STRIP:FILEPATH=/usr/bin/strip
  
  //If this value is on, makefiles will be generated without the
  // .SILENT directive, and all commands will be echoed to the console
  // during the make.  This is useful for debugging only. With Visual
  // Studio IDE projects all commands are done without /nologo.
  CMAKE_VERBOSE_MAKEFILE:BOOL=ON
  
  //Path to a file.
  TinyXML_INCLUDE_DIR:PATH=/usr/include
  
  //Path to a library.
  

Bug#837744: gupnp-dlna: FTBFS: usr/bin/ld: cannot find -lgupnp-dlna-gst-2.0

[Chris Lamb]

Source: gupnp-dlna
Version: 0.10.5-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

gupnp-dlna fails to build from source in unstable/amd64:

  [..]

  test -d "$destdir" || mkdir -p "$destdir"; \
  test -f 
/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5/doc/gupnp-dlna-metadata/$file
 && \
  cp -pf 
/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5/doc/gupnp-dlna-metadata/$file
 
/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5/doc/gupnp-dlna-metadata/$file
 || true; \
  done; \
  fi; \
  fi
  /bin/mkdir -p xml && ( \
echo ""; \
echo "https://bugzilla.gnome.org/enter_bug.cgi?product=gupnp=gupnp-dlna\;>";
 \
echo ""; \
echo ""; \
echo ""; \
echo "http://www.gupnp.org/\;>"; \
echo ""; \
  ) > xml/gtkdocentities.ent
  touch setup-build.stamp
  _source_dir='' ; \
  for i in ./../../libgupnp-dlna/metadata ; do \
  _source_dir="${_source_dir} --source-dir=$i" ; \
  done ; \
  gtkdoc-scan --module=gupnp-dlna-metadata --ignore-headers="" ${_source_dir} 
--deprecated-guards="GUPNP_DISABLE_DEPRECATED" 
  if grep -l '^..*$' gupnp-dlna-metadata.types > /dev/null 2>&1 ; then \
  scanobj_options=""; \
  gtkdoc-scangobj 2>&1 --help | grep  >/dev/null "\-\-verbose"; \
  if test "$?" = "0"; then \
  if test "x" = "x1"; then \
  scanobj_options="--verbose"; \
  fi; \
  fi; \
  CC="/bin/bash ../../libtool --tag=CC --mode=compile gcc  
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -g -O0 -g -Wall" 
LD="/bin/bash ../../libtool --tag=CC --mode=link gcc -lgobject-2.0 -lglib-2.0  
-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -g -O0 -g -Wall  
-Wl,-z,relro" RUN="/bin/bash ../../libtool --mode=execute" CFLAGS="-I../.. -g 
-O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -g -O0 -g -Wall" 
LDFLAGS="../../libgupnp-dlna/libgupnp-dlna-2.0.la -Wl,-z,relro" \
  gtkdoc-scangobj  $scanobj_options --module=gupnp-dlna-metadata; \
  else \
  for i in gupnp-dlna-metadata.args gupnp-dlna-metadata.hierarchy 
gupnp-dlna-metadata.interfaces gupnp-dlna-metadata.prerequisites 
gupnp-dlna-metadata.signals ; do \
  test -f $i || touch $i ; \
  done \
  fi
  touch scan-build.stamp
  _source_dir='' ; \
  for i in ./../../libgupnp-dlna/metadata ; do \
  _source_dir="${_source_dir} --source-dir=$i" ; \
  done ; \
  gtkdoc-mkdb --module=gupnp-dlna-metadata --output-format=xml 
--expand-content-files="" --main-sgml-file=gupnp-dlna-metadata-docs.sgml 
${_source_dir} --sgml-mode --output-format=xml
  touch sgml-build.stamp
  rm -rf html && mkdir html && \
  mkhtml_options=""; \
  gtkdoc-mkhtml 2>&1 --help | grep  >/dev/null "\-\-verbose"; \
  if test "$?" = "0"; then \
if test "x" = "x1"; then \
  mkhtml_options="$mkhtml_options --verbose"; \
fi; \
  fi; \
  gtkdoc-mkhtml 2>&1 --help | grep  >/dev/null "\-\-path"; \
  if test "$?" = "0"; then \
mkhtml_options="$mkhtml_options 
--path=\"/home/lamby/temp/cdt.20160914082221.fqYsDdkxNi.db.gupnp-dlna/gupnp-dlna-0.10.5/doc/gupnp-dlna-metadata\"";
 \
  fi; \
  cd html && gtkdoc-mkhtml $mkhtml_options  gupnp-dlna-metadata 
../gupnp-dlna-metadata-docs.sgml
  gtkdoc-fixxref --module=gupnp-dlna-metadata --module-dir=html 
--html-dir=/usr/share/gtk-doc/html --extra-dir=/usr/share/gtk-doc/html/gobject 
--extra-dir=/usr/share/gtk-doc/html/glib 
--extra-dir=/usr/share/gtk-doc/html/gmodule --extra-dir=../gupnp-dlna/html
  html/GUPnPDLNAMetadataExtractor.html:83: warning: no link for: 
'G-SIGNAL-RUN-LAST:CAPS' -> (Run Last).
  html/GUPnPDLNAMetadataExtractor.html:123: warning: no link for: 'GModule' -> 
(GModule).
  html/GUPnPDLNAMetadataExtractor.html:135: warning: no link for: 
'g-module-build-path' -> (g_module_build_path()).
  html/GUPnPDLNAMetadataExtractor.html:137: warning: no link for: 
'GUPnPDLNAInformation' -> (GUPnPDLNAInformation).
  html/GUPnPDLNAMetadataExtractor.html:137: warning: no link for: 
'GUPnPDLNAAudioInformation' -> (GUPnPDLNAAudioInformation).
  html/GUPnPDLNAMetadataExtractor.html:138: warning: no link for: 
'GUPnPDLNAContainerInformation' -> (GUPnPDLNAContainerInformation).
  html/GUPnPDLNAMetadataExtractor.html:138: warning: no link for: 
'GUPnPDLNAImageInformation' -> (GUPnPDLNAImageInformation).
  

Processed: tagging 837738

[Debian Bug Tracking System]

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

> tags 837738 + pending
Bug #837738 [nautilus] Fails to start, Invalid property: 
GtkScrolledWindow.propagate-natural-height
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837745: sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

[Chris Lamb]

Source: sgml-data
Version: 2.0.10
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

sgml-data fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  sgml-data
   Version:  2.0.10
   Build architecture:   amd64
   Date: Wed, 14 Sep 2016 08:26:38 +0100
   Hostname: 5f5bad433eba
   Uname:Linux 5f5bad433eba 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'sgml-data-build-deps' in 
'../sgml-data-build-deps_2.0.10_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package sgml-data-build-deps.
  (Reading database ... 23320 files and directories currently installed.)
  Preparing to unpack sgml-data-build-deps_2.0.10_all.deb ...
  Unpacking sgml-data-build-deps (2.0.10) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
sgml-base xml-core
  Suggested packages:
sgml-base-doc
  The following NEW packages will be installed:
sgml-base xml-core
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 38.9 kB of archives.
  After this operation, 263 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 sgml-base all 1.28 
[14.7 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 xml-core all 
0.13+nmu2 [24.2 kB]
  Fetched 38.9 kB in 0s (972 kB/s)
  Selecting previously unselected package sgml-base.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23324 files and directories currently installed.)
  Preparing to unpack .../0-sgml-base_1.28_all.deb ...
  Unpacking sgml-base (1.28) ...
  Selecting previously unselected package xml-core.
  Preparing to unpack .../1-xml-core_0.13+nmu2_all.deb ...
  Unpacking xml-core (0.13+nmu2) ...
  Setting up sgml-base (1.28) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up xml-core (0.13+nmu2) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up sgml-data-build-deps (2.0.10) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=5f5bad433eba
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20160914082636.TdexkE4xBe.db.sgml-data/sgml-data-2.0.10
  OLDPWD=/home/lamby/temp/cdt.20160914082636.TdexkE4xBe.db.sgml-data
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building sgml-data 2.0.10 on amd64 
  **
  

Bug#837526: marked as done (libshibsp7: needs rebuild before testing migration)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 09:19:47 +0200
with message-id <878tuv7xt8@lant.ki.iif.hu>
and subject line The rebuild is done
has caused the Debian Bug report #837526,
regarding libshibsp7: needs rebuild before testing migration
to be marked as done.

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

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


-- 
837526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shibboleth-sp2-common
Version: 2.6.0+dfsg1-3
Severity: important
Tags: patch

Dear Maintainer,

   * What led up to the situation?

  Updated shibboleth from previous 2.5.x; two packages refused to
install due to configuration errors.


   * What was the result of updating?

 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : fatal error
on line 0, column 0, message: unable to open primary document entity
'/catalog.xml'
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : catalog
loader caught exception: XML error(s) during parsing, check log for
specifics
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : fatal error
on line 0, column 0, message: unable to open primary document entity
'/saml20-catalog.xml'
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : catalog
loader caught exception: XML error(s) during parsing, check log for
specifics
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : fatal error
on line 0, column 0, message: unable to open primary document entity
'/saml11-catalog.xml'
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : catalog
loader caught exception: XML error(s) during parsing, check log for
specifics
 2016-09-06 17:31:45 WARN XMLTooling.ParserPool : warning on
line 0, column 0, message: unable to open primary document entity
'/usr/share/xml/shibboleth/xmldsig-core-schema.xsd'
 2016-09-06 17:31:45 WARN XMLTooling.ParserPool : warning on
line 0, column 0, message: unable to open primary document entity
'/usr/share/xml/shibboleth/xml.xsd'
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : error on
line 143, column 56, message: namespace
'http://www.w3.org/XML/1998/namespace' is referenced without import
declaration
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : error on
line 254, column 56, message: namespace
'http://www.w3.org/2000/09/xmldsig#' is referenced without import
declaration
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : error on
line 254, column 56, message: referenced element 'ds:Signature' not
found
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : error on
line 277, column 31, message: namespace
'http://www.w3.org/2000/09/xmldsig#' is referenced without import
declaration
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : error on
line 277, column 31, message: referenced element 'ds:KeyInfo' not
found
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : error on
line 291, column 48, message: namespace
'http://www.w3.org/2000/09/xmldsig#' is referenced without import
declaration
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : error on
line 291, column 48, message: referenced element 'ds:Signature' not
found
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : fatal error
on line 1, column 1, message: invalid document structure
 2016-09-06 17:31:45 ERROR XMLTooling.ParserPool : fatal error
on line 9, column 154, message: fatal error during schema scan
 2016-09-06 17:31:45 ERROR Shibboleth.Config : error while
loading resource (/etc/shibboleth/shibboleth2.xml): XML error(s)
during parsing, check log for specifics
 2016-09-06 17:31:45 FATAL Shibboleth.Config : caught
exception while loading configuration: XML error(s) during parsing,
check log for specifics
 <3>configuration is invalid, check console for specific problems


   * What exactly did you do to try and address the situation?

  I used "/usr/sbin/shibd -t" to test the configuration changes I
added this to console.logger to debug the problem:

 log4j.category.XMLTooling.ParserPool=DEBUG

  Finally, modified the /usr/share/xml/shibboleth/catalog.xml file
to add the six required lines:

 http://www.w3.org/XML/1998/namespace;
uri="/usr/share/xml/xmltooling/xml.xsd"/>
 http://www.w3.org/2001/04/xmlenc#;
uri="/usr/share/xml/xmltooling/xenc-schema.xsd"/>
 http://www.w3.org/2000/09/xmldsig#;
uri="/usr/share/xml/xmltooling/xmldsig-core-schema.xsd"/>

 
 
 


   * What was the outcome from this action?

  The service started successfully, despite some suspicious error 

Bug#837123: [anna] segfault in wheezy installer

[Aurelien Jarno]

On 2016-09-14 16:08, Vincent McIntyre wrote:
> On Wed, Sep 14, 2016 at 09:29:18AM +1000, Vincent McIntyre wrote:
> > > Also you might want to use the console (alt+f2) to run wget by hand and
> > > see if the issue happen with all hosts or only some of them.
> > 
> > I tried to wget pages from a few web sites from the alt+f2 console.
> > It segfaulted every time when I used a DNS name in the URL,
> > but worked if I used an IP address in the URL.
> > ping does the same thing; segfaults only when using domain names.
> > 
> > If I put an entry in /etc/hosts and try to access that hostname,
> > wget and ping also segfault, until I add this line to nsswitch.conf:
> > 
> >   hosts: files dns
> > 
> > Then they both work for that hostname.
> > The only other nsswitch.conf lines are for passwd, group & shadow.
> > 
> 
> I was able to netcat busybox & the coredump to a wheezy machine
> and got this backtrace, which does not look like it is much help...
> 
> % gdb ./ping ./ping.core
> GNU gdb (GDB) 7.4.1-debian
> ...
> warning: Can't read pathname for load map: Input/output error.
> 
> warning: Could not load shared library symbols for 4 libraries, e.g. 
> /lib/libc.so.6.
> Use the "info sharedlibrary" command to see the complete listing.
> Do you need "set solib-search-path" or "set sysroot"?
> Core was generated by `ping ftp.au.debian.org'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x7f826609d0ca in ?? ()
> (gdb) bt full
> #0  0x7f826609d0ca in ?? ()
> No symbol table info available.
> #1  0x in ?? ()
> No symbol table info available.
> (gdb) q

Have you installed libc6-dbg on this wheezy machine? Anyway I am afraid
that gdb is confused as the libc6 in debian-installer got some symbols
removed...

Aurelien

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

Bug#837123: [anna] segfault in wheezy installer

[Aurelien Jarno]

On 2016-09-14 09:29, Vincent McIntyre wrote:
> On Tue, Sep 13, 2016 at 11:03:19PM +0200, Aurelien Jarno wrote:
> 
> ...
> 
> > > If all of that makes no difference, what would be the next step?
> > 
> > What would be interesting would be to try to reproduce the issue in
> > qemu or virtualbox, with as many things as possible close to your
> > system.
> > 
> 
> Just to clarify - you mean try to run the installer using a qemu VM
> as the target for installation? I can certainly try that.

Yes, that's the idea, to see if by using the same network environment
you have the same issue.

> More details.
> The target system is pxe booted and next-server takes it to a (debian)
> system running tftpd-hpa. The defaults.cfg has lots of boot targets
> but the one I have been testing with is the netboot image, in manual
> install mode. The only boot options it is given are 
>  'append vga=normal initrd=yadayada'
> It also falls over if I feed it a preseed file, where we use
>  'append auto=true priority=critical vga=normal initrd=yadayda 
>   url=blahdeblah'

Thanks for the details. Here in a QEMU VM, both work fine.

> > Also you might want to use the console (alt+f2) to run wget by hand and
> > see if the issue happen with all hosts or only some of them.
> 
> I tried to wget pages from a few web sites from the alt+f2 console.
> It segfaulted every time when I used a DNS name in the URL,
> but worked if I used an IP address in the URL.
> ping does the same thing; segfaults only when using domain names.
> 
> If I put an entry in /etc/hosts and try to access that hostname,
> wget and ping also segfault, until I add this line to nsswitch.conf:
> 
>   hosts: files dns
> 
> Then they both work for that hostname.
> The only other nsswitch.conf lines are for passwd, group & shadow.

That means the segmentation fault happen as soon as there is a name
resolution.

Aurelien

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

Bug#837595: marked as done (gnome-shell-pomodoro: Not compatible with gnome-shell 3.21.x/3.22)

[Debian Bug Tracking System]

Your message dated Wed, 14 Sep 2016 06:34:06 +
with message-id 
and subject line Bug#837595: fixed in gnome-shell-extension-suspend-button 
0~git20160525-2
has caused the Debian Bug report #837595,
regarding gnome-shell-pomodoro: Not compatible with gnome-shell 3.21.x/3.22
to be marked as done.

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

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


-- 
837595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-pomodoro
Version: 0.11.2-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-3-22

Hi,

your package gnome-shell-pomodoro declares a strictly versioned
dependency on gnome-shell. We've uploaded gnome-shell 3.21.91 to
unstable, which makes gnome-shell-pomodoro uninstallable.

Please test if your package is compatible with that version and
update the information in metadata.json and the package dependencies
accordingly.

There will be one more development release, 3.21.92, before the final
version 3.22.0 is released [1]. gnome-shell development is frozen, so
if gnome-shell-pomodoro works with 3.21.91, it's pretty safe to
assume it will also work with 3.21.92 and 3.22. So you might list
those as supported versions as well

Regards, Michael

[1] https://wiki.gnome.org/ThreePointTwentyone
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-suspend-button
Source-Version: 0~git20160525-2

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-suspend-button, which is due to be installed in the 
Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated 
gnome-shell-extension-suspend-button package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 08:14:39 +0200
Source: gnome-shell-extension-suspend-button
Binary: gnome-shell-extension-suspend-button
Architecture: source
Version: 0~git20160525-2
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gnome-shell-extension-suspend-button - Gnome-shell extension to modify the 
suspend/shutdown buttons
Closes: 837595
Changes:
 gnome-shell-extension-suspend-button (0~git20160525-2) unstable; urgency=medium
 .
   * d/control: Relax upper version limit on gnome-shell. (Closes: #837595)
 As the next Gnome version will by default not enforce the version via
 metadata.json, a change in this file is not required. See the bug for
 details.
Checksums-Sha1:
 9fca8bc1276d9d3e562355b81251904384040ec4 2223 
gnome-shell-extension-suspend-button_0~git20160525-2.dsc
 c387b5579738a3cd7ca5fd8f10ba18468ba5fcdf 4068 
gnome-shell-extension-suspend-button_0~git20160525-2.debian.tar.xz
Checksums-Sha256:
 301a102c1f7a0aacc4d9e375fe8bafbffaa3818977580c5b8a873d7289baec4d 2223 
gnome-shell-extension-suspend-button_0~git20160525-2.dsc
 817351d4434cc0994d06a4cb4bffa3f3f1926e2d80aa7fa72df9dcb5f6d038da 4068 
gnome-shell-extension-suspend-button_0~git20160525-2.debian.tar.xz
Files:
 cbcd528cbfca4a779bf40ff08469eaf6 2223 gnome optional 
gnome-shell-extension-suspend-button_0~git20160525-2.dsc
 4ed6b9ce5308f361dd63a9e36e6fcc33 4068 gnome optional 
gnome-shell-extension-suspend-button_0~git20160525-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX2OshAAoJEJFk+h0XvV02EecP/j46h00cqgOfZASqClrfYrF/
CGxVtOuotbouNl2x9dWIG15k5IyfdrL/OnzvpLyfjrZVBlJ5f4YaDI6ScWVV1KZ4
jzamcI/L7HPKzxsZkxmfugBDCUcWm9e93es7Sf1zCoejX8/sb0U1iR1TMXMGuNE4
bhGEiEmioKbqTjqtpT1VhRO6lZuPmF2ND//W7qjhNT3GUzLNfCQr1+jRdRaMxv9Q
TFjvb/frh4SbsmFh837QzipuUvL+TxV2sjcsXEoc8JZl6qNgAwpTQUXUQiHZ9ba7
9sXHFfxVZ8WoOsr1XUatzTZZqIENGzXbJOf3c7IqmHztnPrJEDeJiw3S4+3Zqcb8
qepa1i1DvmP3en6i85FTXT/HNMcbJl8qEO1etxrWsTVGj8fV5oYSVSfv/6GM0Rtv
3bG6BMyMy+nUSs1/i6bQBK5qHhjigFWLLIsS4R38knsLjlReRJbkL5X4pag0DHL4
U6Wm+OAcrF03dM+ZsfHc7aul+gDTotxcZ8RgzxNi3Dta17/eaBKpjSwlJqxdi95A
uVnwJDgNuqc4c7liTVkUUkCQ0xP+kaRyCb1EWRQekEx2mrl1MCnmSmnyLogsYKIs

Bug#837121: gazebo: please restrict libkido-dev (build-)dependency to architectures where it is available

[Graham Inggs]

Control: reopen -1


Hi Maintainer

I see you updated gazebo's build-dependencies in 7.3.0+dfsg-5.
Please do the same for libgazebo7-dev's binary dependencies, i.e.


--- a/debian/control
+++ b/debian/control
@@ -137,7 +138,7 @@
  libignition-math2-dev,
  libbullet-dev,
  libsimbody-dev,
- libkido-dev [amd64 arm64 i386 powerpc alpha],
+ libkido-dev [amd64 arm64 i386 ppc64el alpha mipsel],
  libgazebo7 (= ${binary:Version}),
  gazebo7-common (= ${source:Version}),
  gazebo7-plugin-base (= ${binary:Version}),


Regards
Graham