Bug#839530: e2fsck-static: Completion information triggers SIGILL on powerpc in jessie

[Theodore Ts'o]

On Sat, Oct 01, 2016 at 06:00:06PM +0200, Christoph Biedl wrote:
> 
> Using the binary packages at snapshot.d.o leads to the assumption this
> was introduced in 1.42.9-3 (1.42.9-2 is okay) and fixed in 1.43-1
> (1.43~WIP.2016.03.15-2 still fails). I could not reproduce this by
> compiling e2fsck from git, so I could not use git bisect to identify
> the actual changes. A diff of the sources did not reveal anything
> obvious.
> 
> Using gdb on a re-build of 1.42.12-2 gave the following backtrace:

Hmm so if you build e2fsprogs 1.42.12 or 1.42.13 out of git, you
can't reproduce it.  But if you build 1.42.12-2 from the debian soures
(presumably using dpkg-buildpackage) it does reproduce?   Is that correct?

> So I fear some previous statements disturb an internal buffer. And
> as long as the actual cause is unknown, I am concerned this bug still
> might be there, just no longer manifests this way. And I'm interested
> in getting this fixed in an upcoming stable point release.

Two experiments if you could try them.

1) Create a file, debian/rules.custom which contains the singe line
"SKIP_DIETLIBC = yes".  Then rebuild 1.42.12-2 and see if the problem
goes away.

One of the things which we dropped in 1.43's debian rules file was
trying to use dietlibc to make the installation and e2fsck.static
binaries smaller.  As I recall it was due to random failures on
different architectures.  

2) If the problem is still reproducing, can you try using "valgrind"
to see if that shows up something useful.

> Also I am willing to do further tests as long as they are feasible: A
> full dpkg-buildpackage takes some 30 minutes so I'd like to avoid
> having to do this ten times in a row.

It's possible to speed up dpkg-buildpackage by creating a
debian/rules.custom file that contains:

SKIP_BF = yes
SKIP_UDEB = yes

(You could also add "SKIP_STATIC = yes", but that will probably make
the problem go away, and result in an e2fsck.static which (a) doesn't
use dietlibc, but which (b) still links dynamically with libc
--- although not the other e2fsprogs libaries.)

Cheers,

- Ted

Bug#839554: merge with "linux: please add nls_ascii to fat-modules udeb"

[Geert Stappers]

Control: reassign -1 src:linux
Control: merge -1 839552

On Sun, Oct 02, 2016 at 05:09:03AM +, Debian Bug Tracking System wrote:
> Processing control commands:
> 
> > reassign -1 src:linux   
> >  Control: merge -1 839552
> Unknown command or malformed arguments to command.

Bug#827517: [Pkg-mozext-maintainers] Bug#827517: Bug#827517: xul-ext-ublock-origin: Missing icons in uBlock's popup UI

[Evgeny Kapun]

On 02.10.2016 07:41, Sean Whitton wrote:

Thanks for this feedback.  Unfortunately, installing an absolute symlink
does not make the problem disappear for firefox-esr, contrary to various
reports in this thread.


That's because /usr/share/fonts-font-awesome/fonts/fontawesome-webfont.ttf is 
also a symlink. Symlink handling in Firefox is broken, but using an absolute 
symlink to the actual file (which is 
/usr/share/fonts/truetype/font-awesome/fontawesome-webfont.ttf) works.

Bug#839566: sbuild: please add an option to let sbuild automatically investigate installability problems

[Johannes Schauer]

Package: sbuild
Version: 0.71.0-2
Severity: wishlist

Hi,

it would be cool if sbuild would automatically report why a dependency
situation is unsatisfiable, either by running dose3 or apt with more
verbose options. In case of apt, the options could be:

-o Debug::pkgProblemResolver=true
-o Debug::pkgDepCache::Marker=1
-o Debug::pkgDepCache::AutoInstall=1
-o Debug::BuildDeps=1

This could come in the form of an option like:

 --build-deps-failed-explainer=apt
 --build-deps-failed-explainer=dose3

Thanks!

cheers, josch

Bug#839554: merge with "linux: please add nls_ascii to fat-modules udeb"

[Geert Stappers]

Control: reassign -1 src:linux  
  Control: merge -1 839552  



  
Because   

On Sun, Oct 02, 2016 at 04:51:03AM +, Debian Bug Tracking System wrote:
> Processing control commands:
> 
> > assign -1 linux
> Unknown command or malformed arguments to command.
> 
> > merge -1 839552
> Bug #839554 [installation-reports] Fwd: Message with no Package: tag cannot 
> be processed! (installation-reports: failure to format and mount EFI 
> partition during installation)
> Unable to merge bugs because:
> package of #839552 is 'src:linux' not 'installation-reports'
> Failed to merge 839554: Did not alter merged bugs.

Bug#839565: cln FTCBFS: misses ./configure options --build and --host, runs tests under DEB_BUILD_OPTIONS=nocheck

[Helmut Grohne]

Source: cln
Version: 1.3.4-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

cln fails to cross build from source, because it uses an ancient and now
unsupported way of passing the host architecture to ./configure
directly. Replacing that with --build and --host and adding support for
DEB_BUILD_OPTIONS=nocheck makes a cross build succeed. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru cln-1.3.4/debian/changelog cln-1.3.4/debian/changelog
--- cln-1.3.4/debian/changelog  2014-10-16 07:45:53.0 +0200
+++ cln-1.3.4/debian/changelog  2016-10-02 06:19:21.0 +0200
@@ -1,3 +1,12 @@
+cln (1.3.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Pass --build and --host to ./configure.
++ Support DEB_BUILD_OPTIONS=nocheck.
+
+ -- Helmut Grohne   Sun, 02 Oct 2016 06:18:58 +0200
+
 cln (1.3.4-1) unstable; urgency=low
 
   * New upstream release. (Closes: #748325)
diff --minimal -Nru cln-1.3.4/debian/rules cln-1.3.4/debian/rules
--- cln-1.3.4/debian/rules  2014-06-01 11:53:22.0 +0200
+++ cln-1.3.4/debian/rules  2016-10-02 06:20:15.0 +0200
@@ -39,7 +39,7 @@
 
 build-arch: debian/autoreconf-stamp
dh_testdir
-   ./configure --prefix=/usr `dpkg-architecture -qDEB_HOST_GNU_TYPE` 
CPPFLAGS="$(CPPFLAGS)" CXXFLAGS="$(CXXFLAGS)" LDFLAGS="$(LDFLAGS)"
+   ./configure --prefix=/usr --build=$(DEB_BUILD_GNU_TYPE) 
--host=$(DEB_HOST_GNU_TYPE) CPPFLAGS="$(CPPFLAGS)" CXXFLAGS="$(CXXFLAGS)" 
LDFLAGS="$(LDFLAGS)"
${MAKE}
(cd doc; ${MAKE} cln.html)
touch build
@@ -61,8 +61,10 @@
dh_testdir
dh_testroot
dh_installdirs
+ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),)
# I want to see what the buildd logs of the different architectures say:
-${MAKE} check
+endif
${MAKE} install prefix=${CURDIR}/debian/tmp/usr 
bindir=${CURDIR}/debian/pi/usr/bin mandir=${CURDIR}/debian/pi/usr/share/man 
datadir=${CURDIR}/debian/libcln-dev/usr/share
${MAKE} install-html prefix=${CURDIR}/debian/libcln-dev/usr 
htmldir=${CURDIR}/debian/libcln-dev/usr/share/doc/libcln-dev/html
# This installs into libdir, but we must not set libdir because it 
affects the .la file:

Bug#839554: merge with "linux: please add nls_ascii to fat-modules udeb"

[Geert Stappers]

Control: assign -1 linux
Control: merge -1 839552

On Sun, Oct 02, 2016 at 12:18:34AM +0200, Cyril Brulebois wrote:
> Jeroen Van den Keybus  (2016-10-01):
> > 
> > In dmesg: FAT-fs (sda1): IO charset ascii not found
> > 
> > Mounting is succesful if done with 'mount /dev/sda1 /target/boot/efi -o
> > iocharset=utf8' in a shell. mkfs.fat -F32 is also not a problem.
> > 
> > But installer is unaware of course, and cannot proceed.
> > 
> > From IRC interaction with 'KIBI' and 'bwh' it is apparent that nls_ascii
> > module is missing after default FAT mount options have changed in the
> > kernel (commit 0e156c15e31ac4f3e160a6ac262b172d0390d7e8).
> 
> As debian-boot@ people might have noticed, I filed this bug report
> accordingly:
> 
>   #839552: linux: please add nls_ascii to fat-modules udeb
> 

BTS updated

Bug#827517: [Pkg-mozext-maintainers] Bug#827517: Bug#827517: xul-ext-ublock-origin: Missing icons in uBlock's popup UI

[Sean Whitton]

Dear Evgeny,

On Thu, Sep 15, 2016 at 09:37:59PM +0300, Evgeny Kapun wrote:
> This bug looks similar to bug #819900. That bug was caused by faulty
> handling of symlinks by Firefox, which Mozilla refuses to fix [1].
> 
> There is a simple workaround: use an absolute symlink instead of a relative 
> one.
> 
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1286634

Thanks for this feedback.  Unfortunately, installing an absolute symlink
does not make the problem disappear for firefox-esr, contrary to various
reports in this thread.

If you'd like to try it yourself:

$ sudo apt-get install devscripts
$ sudo apt-get build-dep ublock-origin
$ debcheckout ublock-origin
$ cd ublock-origin
$ origtargz
$ git checkout abs-symlink
$ debuild -b -uc
$ sudo debi

... and fire up Firefox ESR.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#811857: fixed in synaptic 0.83+nmu1

[Jeremy Bicha]

Olly, thanks for fixing this bug.

Since Ubuntu 16.10 has gcc 6 too, the patch should also be added to
00list.Ubuntu like this:

=== modified file 'debian/patches/00list.Ubuntu'
--- debian/patches/00list.Ubuntu2016-10-02 04:10:59 +
+++ debian/patches/00list.Ubuntu2016-10-02 04:14:11 +
@@ -1,3 +1,3 @@
 01_ubuntu_changelog
 #10_ubuntu_maintenance_gui
-
+99_fix_build_with_gcc6



Thanks,
Jeremy Bicha

Bug#826671: libvisca: FTBFS: dh_install: Cannot find (any matches for) "debian/tmp/usr/lib/*.so.*" (tried in "." and "debian/tmp")

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * Use dh-autoreconf to fix FTBFS.

Thanks for considering the patch.

Logan Rosen
diff -u libvisca-1.0.1/debian/control libvisca-1.0.1/debian/control
--- libvisca-1.0.1/debian/control
+++ libvisca-1.0.1/debian/control
@@ -2,7 +2,7 @@
 Maintainer: Alan Woodland 
 Section: libdevel
 Priority: extra
-Build-depends: debhelper (>= 7), cdbs, autotools-dev, libtool, libtool-bin, autoconf, automake
+Build-depends: debhelper (>= 7), cdbs, autotools-dev, libtool, libtool-bin, autoconf, automake, dh-autoreconf
 Standards-version: 3.8.3
 Homepage: http://damien.douxchamps.net/libvisca/
 
diff -u libvisca-1.0.1/debian/rules libvisca-1.0.1/debian/rules
--- libvisca-1.0.1/debian/rules
+++ libvisca-1.0.1/debian/rules
@@ -2,6 +2,7 @@
 
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/autotools.mk
+include /usr/share/cdbs/1/rules/autoreconf.mk
 #include /usr/share/cdbs/1/rules/dpatch.mk
 #include /usr/share/dpatch/dpatch.make
 

Bug#814599: [Bash-completion-devel] Bug#814599: bash-completion: different behavior in /etc/bash_completion.d/ than in /usr/share/bash-completion/completions/

[Paul Wise]

Control: reassign -1 lintian
Control: retitle -1 lintian: package-installs-into-obsolete-dir: mention 
filename requirements for /usr/share/bash-completion/completions/

On Sat, 2016-10-01 at 13:59 +0300, Martin-Éric Racine wrote:
> > 2016-10-01 12:41 GMT+03:00 Paul Wise :
> > 
> > On Sat, 13 Feb 2016 21:50:19 +0200 Martin-Éric Racine wrote:
> > 
> > > 
> > > This detail would need to be added to the error that Lintian throws at
> > > maintainers when their script is still at the old location.
> > 
> > Should this bug be reassigned to lintian and retitled?
> 
> Probably, yes.

Ok, done.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#839564: linux-image-4.6.0-1-amd64: Collaboration with pm-utils unreliable

[Martin Haase]

Package: src:linux
Version: 4.6.4-1
Severity: important

After having been put to sleep apparently with success, the re-awaking
of the system works unreliably. For, say, five out of six times I'll
get the system as it was before, but then again I won't. Instead I can
watch it reboot. Fortunately, no data have been lost so far. (Although
putting Firefox back into the state it had been before can be somewhat
annoying.)

I'm posting this issue as a kernel bug, because it didn't occur in
version 4.4.0-trunk. In version 4.7.0-1 no hibernation ever went
satisfactorily, there was a reboot every time, with 4.6.0 this has
been reduced to at least a percentage. Which is why 4.7.0 no longer is
installed.

I can't find any information in either of the logs concerned. Mcelog
is of size 0. 

Hope this helps after all.
Regards
Martin




-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

** Command line:
BOOT_IMAGE=/vmlinuz-4.6.0-1-amd64 
root=UUID=e5cfcd50-8a83-40ea-8138-f03cb791af07 ro quiet radeon.dpm=1

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[   11.564103] [drm]   Encoders:
[   11.564105] [drm] DFP2: INTERNAL_UNIPHY2
[   11.564106] [drm] Connector 2:
[   11.564107] [drm]   HDMI-A-1
[   11.564108] [drm]   HPD3
[   11.564109] [drm]   DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 
0x646c
[   11.564110] [drm]   Encoders:
[   11.564112] [drm] DFP3: INTERNAL_UNIPHY1
[   11.564113] [drm] Connector 3:
[   11.564114] [drm]   DVI-D-1
[   11.564115] [drm]   HPD1
[   11.564116] [drm]   DDC: 0x6480 0x6480 0x6484 0x6484 0x6488 0x6488 0x648c 
0x648c
[   11.564118] [drm]   Encoders:
[   11.564119] [drm] DFP4: INTERNAL_UNIPHY1
[   11.564120] [drm] Connector 4:
[   11.564121] [drm]   DVI-I-1
[   11.564122] [drm]   HPD6
[   11.564123] [drm]   DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 0x647c 
0x647c
[   11.564124] [drm]   Encoders:
[   11.564126] [drm] DFP5: INTERNAL_UNIPHY
[   11.564127] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[   11.564297] switching from power state:
[   11.564298]  ui class: none
[   11.564300]  internal class: boot 
[   11.564302]  caps: 
[   11.564304]  uvdvclk: 0 dclk: 0
[   11.564306]  power level 0sclk: 1 mclk: 15000 vddc: 950 
vddci: 950
[   11.564308]  power level 1sclk: 1 mclk: 15000 vddc: 950 
vddci: 950
[   11.564309]  power level 2sclk: 1 mclk: 15000 vddc: 950 
vddci: 950
[   11.564310]  status: c b 
[   11.564312] switching to power state:
[   11.564313]  ui class: performance
[   11.564315]  internal class: none
[   11.564316]  caps: 
[   11.564318]  uvdvclk: 0 dclk: 0
[   11.564319]  power level 0sclk: 1 mclk: 15000 vddc: 950 
vddci: 950
[   11.564321]  power level 1sclk: 77500 mclk: 105000 vddc: 1100 
vddci: 1150
[   11.564322]  power level 2sclk: 9 mclk: 105000 vddc: 1175 
vddci: 1150
[   11.564323]  status: r 
[   11.660493] [drm] fb mappable at 0xD0475000
[   11.660495] [drm] vram apper at 0xD000
[   11.660497] [drm] size 8294400
[   11.660498] [drm] fb depth is 24
[   11.660498] [drm]pitch is 7680
[   11.660555] fbcon: radeondrmfb (fb0) is primary device
[   11.663224] switching from power state:
[   11.663225]  ui class: performance
[   11.663226]  internal class: none
[   11.663226]  caps: 
[   11.663227]  uvdvclk: 0 dclk: 0
[   11.663228]  power level 0sclk: 1 mclk: 15000 vddc: 950 
vddci: 950
[   11.663229]  power level 1sclk: 77500 mclk: 105000 vddc: 1100 
vddci: 1150
[   11.663229]  power level 2sclk: 9 mclk: 105000 vddc: 1175 
vddci: 1150
[   11.663230]  status: c r 
[   11.663230] switching to power state:
[   11.663231]  ui class: performance
[   11.663232]  internal class: none
[   11.663232]  caps: 
[   11.663233]  uvdvclk: 0 dclk: 0
[   11.663233]  power level 0sclk: 1 mclk: 15000 vddc: 950 
vddci: 950
[   11.663234]  power level 1sclk: 77500 mclk: 105000 vddc: 1100 
vddci: 1150
[   11.663234]  power level 2sclk: 9 mclk: 105000 vddc: 1175 
vddci: 1150
[   11.663235]  status: c r 
[   11.695330] Console: switching to colour frame buffer device 240x67
[   11.700465] radeon :01:00.0: fb0: radeondrmfb frame buffer device
[   11.711002] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on 
minor 0
[   11.820359] scsi 7:0:0:0: Direct-Access Generic- SD/MMC   1.00 
PQ: 0 ANSI: 0
[   11.821274] scsi 7:0:0:1: Direct-Access Generic- Compact Flash1.01 
PQ: 0 ANSI: 0
[   11.822077] scsi 7:0:0:2: Direct-Access Generic- SM/xD-Picture1.02 
PQ: 0 ANSI: 0
[   11.822898] scsi 7:0:0:3: Direct-Access Generic- MS/MS-Pro1.03 
PQ: 0 ANSI: 0 CCS
[   11.823363] sd 7:0:0:0: Attached scsi generic sg3 type 0
[   11.823637] sd 7:0:0:1: Attached scsi 

Bug#839563: opendmarc-expires fails with "Use of uninitialized value in concatenation"

[Stefan Tittel]

Package: opendmarc
Version: 1.3.0+dfsg-1
Severity: important
Tags: upstream

Running /usr/sbin/opendmarc-expire on a fresh opendmarc installations fails as 
follows:

opendmarc-expire: started at Sun Oct  2 03:59:48 2016
opendmarc-expire: connected to database
opendmarc-expire: expiring messages older than 180 day(s)
opendmarc-expire: no rows deleted
Use of uninitialized value in concatenation (.) or string at 
/usr/sbin/opendmarc-expire line 291.
opendmarc-expire: TRUNCATE failed:

The cause of this bug is a missing exclamation mark in 
/usr/sbin/opendmarc-expire.

The problem has recently been fixed by upsteam (including a patch):
https://sourceforge.net/p/opendmarc/tickets/143/


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
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 opendmarc depends on:
ii  adduser3.113+nmu3
ii  libbsd00.7.0-2
ii  libc6  2.19-18+deb8u6
ii  libopendmarc2  1.3.0+dfsg-1
ii  libspf2-2  1.2.10-5
ii  lsb-base   4.1+Debian13+nmu1

Versions of packages opendmarc recommends:
ii  libdbd-mysql-perl 4.028-2+deb8u1
ii  libdbi-perl   1.631-3+b1
ii  libhttp-message-perl  6.06-1
ii  libopendbx1   1.4.6-8
ii  libopendbx1-mysql 1.4.6-8
ii  libswitch-perl2.17-2
ii  perl  5.20.2-3+deb8u6

opendmarc suggests no packages.

-- Configuration Files:
/etc/default/opendmarc changed [not included]
/etc/opendmarc.conf changed [not included]

-- no debconf information

Bug#839562: ITP: libmojolicious-plugin-assetpack-perl -- Compress and convert css, less, sass, javascript and coffeescript files

[Hideki Yamane]

Package: wnpp
Severity: wishlist
Owner: Hideki Yamane 

* Package name: libmojolicious-plugin-assetpack-perl
  Version : 1.24
  Upstream Author : Jan Henning Thorsen 
* URL : https://metacpan.org/release/Mojolicious-Plugin-AssetPack
* License : Artistic-2.0
  Programming Lang: Perl
  Description : Compress and convert css, less, sass, javascript and 
coffeescript files

 Mojolicious plugin for processing static assets, compress and convert css,
 less, sass, javascript and coffeescript files.

I'll put this package into Debian repository to introduce openQA 
(http://open.qa/)

Bug#839561: ITP: libdbix-class-schema-config-perl -- Credential Management for DBIx::Class

[Hideki Yamane]

Package: wnpp
Severity: wishlist
Owner: Hideki Yamane 

* Package name: libdbix-class-schema-config-perl
  Version : 0.001011
  Upstream Author : Kaitlyn Parkhurst (SymKat)  
* URL : https://metacpan.org/release/DBIx-Class-Schema-Config
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Credential Management for DBIx::Class

 A subclass of DBIx::Class::Schema that allows the loading of credentials &
 configuration from a file. The actual code itself would only need to know
 about the name used in the configuration file. This aims to make it simpler
 for operations teams to manage database credentials.

I'll put this package into Debian repository to introduce openQA 
(http://open.qa/)

Bug#839560: tech-ctte: failure to suspend sesion or lock computer

[Timothy Danielson]

Package: tech-ctte
Severity: serious
Tags: security
Justification: must

Dear Maintainer,

   * Q: What led up to the situation? A: attempt to lock, suspend or hibernate 
the sytemt to NOT shut down entirely.
   * Q: What exactly did you do (or not do) that was effective (or
 ineffective)? A: I attempted the three mentioned options.
   * Q: What was the outcome of this action? A: forced restart in all cases, 
resulting on fallback to journaled entries.
   * Q: What outcome did you expect instead? I expected those functions to... 
function.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/6 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)

Bug#839558: plasma-nm: Shows incorrect status and want to have password entered again

[Diederik de Haas]

On zaterdag 1 oktober 2016 20:42:04 CEST Sten Heinze wrote:
> Upgrade: libnm0:amd64 (1.2.4-2, 1.4.0-4), network-manager:amd64 (1.2.4-2,
> 1.4.0-4)

Unstable has version 1.4.2-1 and I think there's a good chance that fixes it. 
Seems at least worth a try as it resolved an issue I had and also someone 
else's issue.

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

Bug#839165: ltsp: the ltsp-build-client apt-keys option fails

[Vagrant Cascadian]

Control: tags 839165 +moreinfo

On 2016-09-29, Wolfgang Schweer  wrote:
> one more issue. Even with no key provided, 001-apt-keys tries to add 
> /etc/apt/trusted.gpg; this fails and the chroot installation stops.
> I have no idea how to fix it.

I am unable to reproduce this issue.

What are the exact arguments you used to produce this behavior?  Do you
have any packages installed that may provide custom ltsp-build-client
plugins, or an /etc/ltsp/ltsp-build-client.conf ?


A possibly related issue is fixed upstream:

  
https://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2756/server/share/ltsp/plugins/ltsp-build-client/Debian/001-apt-keys


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#839559: debian testing pandoc version not updated since long (although debian unstable has latest version). What is blocking debian testing from having latest version?

[Zaxebo Yaxebo]

Package: pandoc
Version: 1.17.0.3

=
My question/request in Brief(TLDR version): My request is that, if there is
no problem/blocking bug, Then please bring version 1.17.2 of pandoc to
debian testing. If there is a problem/blocking bug in doing so, then please
detail it
=
My question/request in detail:


background information:
http://pandoc.org/releases.html lists that pandoc version 1.17.0.3 was
released on 24 march 2016; 1.17.1 was released on 4 june 2016; version
1.17.2 was released on 17 Jul 2016.

   https://packages.debian.org/testing/pandoc
  debian testing contains panoc version 1.17.0.3 (released on 24 mar
2016)

   https://packages.debian.org/unstable/pandoc
  debian unstable contains pandoc version 1.17.2  (released on 17 jul
2016)

My question: given the possibility that next debian stable will be branched
from debian testing in Nov 2016 and todays date is 2nd Oct 2016.
Can i know what is the blocking bug which is preventing 1.17.2 version of
pandoc to be promoted from debian unstable to debian testing, even though
much time has passed already since march 2016?

My request is that: if there is no problem/blocking bug, Then please bring
version 1.17.2 of pandoc to debian testing . If there is such a blocking
issue, then please mention it

Bug#838694: icu: CVE-2016-7415: Stack based buffer overflow in locid.cpp

[Roberto C . Sánchez]

On Fri, Sep 30, 2016 at 07:45:33AM -0400, Roberto C. Sánchez wrote:
> 
> I am currently preparing an LTS upload for this vulnerability.
> 
I tried for quite some time to reproduce this based on the original PHP
bug report, but I was unable.  I have annotated the security tracker
with my (lack of) findings so far.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Bug#839558: plasma-nm: Shows incorrect status and want to have password entered again

[Sten Heinze]

Package: plasma-nm
Version: 4:5.7.4-1
Severity: normal

Dear Maintainer,

* What led up to the situation?

Upgrade: libnm0:amd64 (1.2.4-2, 1.4.0-4), network-manager:amd64 (1.2.4-2, 
1.4.0-4)

* What exactly did you do (or not do) that was effective (or ineffective)?
* What was the outcome of this action?

After the upgrade, when waking up the laptop from sleep, plasma-nm shows an
incorrect state (not connected, the grayed out wifi-symbol with a red 
questionmark
in the lower right corner). Running nmcli on the command line shows the correct
state (connect to my access point).

When attempting to connect to my access point (which plasma-nm lists in the 
available networks), plasma-nm asks for the network password, even though
the plasma-nm connection editor shows the password as saved.

* What outcome did you expect instead?

The correct network state displayed by plasma-nm.


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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 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 plasma-nm depends on:
ii  libc6   2.24-3
ii  libkf5completion5   5.25.0-1
ii  libkf5configcore5   5.25.0-1
ii  libkf5configwidgets55.25.0-1
ii  libkf5coreaddons5   5.25.0-1
ii  libkf5dbusaddons5   5.25.0-1
ii  libkf5i18n5 5.25.0-1
ii  libkf5iconthemes5   5.25.0-1
ii  libkf5itemviews55.25.0-1
ii  libkf5kdelibs4support5  5.25.0-1
ii  libkf5kiowidgets5   5.25.0-1
ii  libkf5modemmanagerqt6   5.25.0-1
ii  libkf5networkmanagerqt6 5.25.0-1
ii  libkf5notifications55.25.0-1
ii  libkf5service-bin   5.25.0-1
ii  libkf5service5  5.25.0-1
ii  libkf5solid55.25.0-1
ii  libkf5wallet-bin5.25.0-1
ii  libkf5wallet5   5.25.0-1
ii  libkf5widgetsaddons55.25.0-1
ii  libkf5windowsystem5 5.25.0-1
ii  libkf5xmlgui5   5.25.0-1
ii  libopenconnect5 7.06-2+b2
ii  libqca-qt5-22.1.1-2
ii  libqt5core5a5.6.1+dfsg-3+b1
ii  libqt5dbus5 5.6.1+dfsg-3+b1
ii  libqt5gui5  5.6.1+dfsg-3+b1
ii  libqt5network5  5.6.1+dfsg-3+b1
ii  libqt5qml5  5.6.1-8
ii  libqt5widgets5  5.6.1+dfsg-3+b1
ii  libqt5xml5  5.6.1+dfsg-3+b1
ii  libstdc++6  6.1.1-11
ii  mobile-broadband-provider-info  20151214-0.1
ii  network-manager 1.4.0-4
ii  plasma-framework5.25.0-1
ii  qml-module-org-kde-kcoreaddons  5.25.0-1

plasma-nm recommends no packages.

Versions of packages plasma-nm suggests:
ii  network-manager-openconnect  1.2.2-1
ii  network-manager-openvpn  1.2.4-1
ii  network-manager-pptp 1.2.2-1
ii  network-manager-vpnc 1.2.2-1

-- no debconf information

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

OK.  I’ll give it a try.

More when I know more.

Rick

On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian  wrote:

> On 2016-09-17, Rick Thomas wrote:
>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
>>> https://bugs.debian.org/837629
>>> 
>>> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
>>> so that u-boot 2016.09 can migrate to stretch... but it would be more
>>> ideal to fix it, of course! :)
>> 
>> It looks like you’ll have to pull OpenRD support out of this version.
>> I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result
>> with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no
>> response following u-boot “reset” command.
> 
> I've uploaded packages based on 2016.09.01 to:
> 
>  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
> 
> The repository should be signed by my key, available in the
> debian-keyring package in the archive
> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
> 
> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?
> 
> If not, I'll likely be removing OpenRD* from the packages on future
> uploads.
> 
> 
> live well,
>  vagrant

Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed

[James McCoy]

On Sat, Oct 01, 2016 at 10:48:47PM +0100, Steven Chamberlain wrote:
> Hi,

Hi!

> The error is slightly different now.
> 
> Test_communicate was fixed upstream:
> |   1621  7.4.2154  Test_communicate() fails sometimes

Well, worked around. That just marks the test as flaky, so it'll get
retried once. :)

> But now, a new error is being seen on kfreebsd and interestingly, also
> on linux-alpha:
> 
> | Found errors in Test_tagcase():
> | Caught exception in Test_tagcase(): Vim(edit):E37: No write since last 
> change (add ! to override) @ function RunTheTest[9]..Test_tagcase, line 3
> | TEST FAILURE

There's also a segfault on kfreebsd-i386 and a failure in
test_startup_utf8 (Test_read_fifo_utf8) on kfreebsd-*.

I was just trying to reproduce the segfault yesterday on fischer, but
only got the fifo failure.  Haven't had a chance to look into that one
more.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#837528: debhelper: dh_installinit --no-restart-on-upgrade now restarts after upgrade

[Michael Biebl]

Am 02.10.2016 um 02:23 schrieb Michael Biebl:

> I think it's quite confusing that we now have
> --no-restart-on-upgrade and
> --no-restart-after-upgrade which mean something different. I'd say the
> name for --no-restart-on-upgrade was poorly chosen.
> 
> Thoughts on whether/how to clean up this situation?

Renaming -r from --no-restart-on-upgrade to --no-stop-on-upgrade would
make it clearer what this flag does. According to codesearch we have 41
packages using --no-restart-on-upgrade. So it looks feasible to get
affected packages updated to replace --no-restart-on-upgrade, which
means it could be deprecated and eventually dropped from debhelper



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



signature.asc
Description: OpenPGP digital signature

Bug#837528: debhelper: dh_installinit --no-restart-on-upgrade now restarts after upgrade

[Michael Biebl]

On Mon, 12 Sep 2016 09:19:38 +0100 Simon McVittie  wrote:
> Package: debhelper
> Version: 10
> Severity: normal
> 
> dbus contains a service that explicitly does not support being restarted
> without a reboot (it would require an init-style stateful re-exec with a
> lot of state to be transferred, which hasn't been implemented), so for a
> long time we've used
> 
> dh_installinit -pdbus -r
> 
> (where -r is the short form of --no-restart-on-upgrade) to suppress the
> restart that debhelper would normally put in the maintainer scripts.
> 
> After upgrading dbus to compat level 10, I see this:
> 
>--- /var/lib/dpkg/info/dbus.postinst   2016-08-15 22:05:45.0 
> +0100
>+++ dbus_1.10.10-2_amd64/DEBIAN/postinst   2016-08-26 
> 11:07:56.0 +0100
>@@ -97,15 +97,18 @@
> if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ]; then
>   if [ -x "/etc/init.d/dbus" ]; then
>   update-rc.d dbus defaults >/dev/null
>-  invoke-rc.d dbus start || exit $?
>+  if [ -n "$2" ]; then
>+  _dh_action=restart
>+  else
>+  _dh_action=start
>+  fi
>+  invoke-rc.d dbus $_dh_action || exit $?
>   fi
> fi
> # End automatically added section
> 
> i.e. the change of default in compat level 10 has meant we would now
> restart the service. Is this intended?
> 
> It looks as though it'll be possible to work around this with
> 
> dh_installinit -pdbus --no-restart-on-upgrade --no-restart-after-upgrade
> 
> but that seems counter-intuitive: I would have expected
> 
> dh_installinit -pdbus --no-restart-on-upgrade
> 
> to be enough?
> 
> I think this pseudo-patch would do what I expect:
> 
>   if (! $dh{NO_START}) {
>-  if ($dh{RESTART_AFTER_UPGRADE}) {
>+  if ($dh{RESTART_AFTER_UPGRADE} && ! 
> $dh{R_FLAG}) {
> 
> On the other hand, this change would likely also affect compat
> levels < 10 if they did
> 
> dh_installinit -pdbus --no-restart-on-upgrade --restart-after-upgrade

For your particular case, I guess using compat level >= 10 and -r , it
would be somewhat reasonable to imply --no-restart-after-upgrade. This
would also be backwards compatible.


I think it's quite confusing that we now have
--no-restart-on-upgrade and
--no-restart-after-upgrade which mean something different. I'd say the
name for --no-restart-on-upgrade was poorly chosen.

Thoughts on whether/how to clean up this situation?

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



signature.asc
Description: OpenPGP digital signature

Bug#836317: dh_systemd_start should stop the sevice on remove even if --no-start has been passed

[Michael Biebl]

On Thu, 01 Sep 2016 17:03:42 +0200 Laurent Bigonville 
wrote:
> Package: debhelper
> Version: 9.20160814
> Severity: important
> File: /usr/bin/dh_systemd_start
> 
> Hi,
> 
> ATM, if --no-start is passed to dh_systemd_start, the service is never
> stopped even if the package is removed/purged.
> 
> IMHO, is should be stopped in that case, I would do something like:
> 
> -if ($dh{R_FLAG} || $dh{RESTART_AFTER_UPGRADE}) {
> +if ($dh{R_FLAG} || $dh{RESTART_AFTER_UPGRADE} || $dh{NO_START}) {
> # stop service only on remove
> $sd_autoscript->("prerm", "prerm-systemd-restart");
> -} elsif (!$dh{NO_START}) {
> +} else {
> # always stop service
> $sd_autoscript->("prerm", "prerm-systemd");
> }
> 
> What do you think?

I think this makes sense but we should make sure that this is consistent
with dh_installinit/sysv
Have you checked what dh_installinit does in this case?


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



signature.asc
Description: OpenPGP digital signature

Bug#839531: jessie-pu: package asused/3.72-11

[Sebastien Badia]

On Sat, Oct 01, 2016 at 06:05:43PM (+0100), Adam D. Barratt wrote:
> Control: tags -1 + moreinfo
> 
> On Sat, 2016-10-01 at 18:22 +0200, Sebastien Badia wrote:
> > Asused is a tool to check IPv4 allocations and assignments
> > as stored in the RIPE database.
> > 
> > The actual version of asused in Debian/stable (3.72-11) doesn't
> > works due to a upstream change on the RIPE database.
> > 
> > The issue was correctred in Debian/testing (3.72-12), see for references
> > the corresponding bug https://bugs.debian.org/799919 and the patch
> > https://anonscm.debian.org/cgit/collab-
> > maint/asused.git/patch/id=472d9b76587005d808766e6f2818ad00bd5d05b6
> 
> That patch changes nothing to do with RIPE, it only updates some patch
> metadata.
> 
> > This jessie-p-u build fine in jessie, package is ready for an upload
> > here https://marcellin.sebian.fr/debian/
> > 
> > You see any issues to no accept asused_3.72-12+deb8u7 as a jessie-p-u?
> 
> I certainly see issues with that version number. Firstly, it's higher
> than the package version in unstable, and secondly I have no idea why
> you would use "deb8u7" for the first update in jessie - that would be
> 3.72-11+deb8u1. "3.72-12+deb8u7" would be the seventh update in jessie
> to the package 3.72-12 (which isn't even in jessie).
> 
> In any case, before we can agree an upload, we would need to see - as in
> attached to this bug log, not merely on an external resource - a source
> debdiff against the version of the package currently in jessie,
> built /and tested/ on jessie.
> 
> Regards,
> 
> Adam

Hello Adam,

Pff really sorry for the waste time… I was too fast on this one…

Just fixed the version number, and re-builded/uploaded to mentors.d.n
https://mentors.debian.net/debian/pool/main/a/asused/asused_3.72-11+deb8u1.dsc
(build and tested in a clean env on Debian jessie).

The debdiff against 3.72-11 version in jessie is now attached.

Thanks for your time and explanation, and sorry again… :)

Regards,

Seb
diff -Nru asused-3.72/debian/changelog asused-3.72/debian/changelog
--- asused-3.72/debian/changelog	2014-01-28 23:26:47.0 +0100
+++ asused-3.72/debian/changelog	2016-10-02 01:29:40.0 +0200
@@ -1,3 +1,10 @@
+asused (3.72-11+deb8u1) stable-proposed-updates; urgency=medium
+
+  * Use created fields instead of changed (Closes: #799919)
+Thanks Matthias!
+
+ -- Sebastien Badia   Sun, 02 Oct 2016 01:28:19 +0200
+
 asused (3.72-11) unstable; urgency=low
 
   * New maintainer (closes: #612901)
diff -Nru asused-3.72/debian/patches/07_changed_fields_are_gone.patch asused-3.72/debian/patches/07_changed_fields_are_gone.patch
--- asused-3.72/debian/patches/07_changed_fields_are_gone.patch	1970-01-01 01:00:00.0 +0100
+++ asused-3.72/debian/patches/07_changed_fields_are_gone.patch	2016-10-02 01:27:48.0 +0200
@@ -0,0 +1,64 @@
+Description: asused stopped working because changed fields are missing in newer objects
+Author: Matthias Cramer 
+Origin: other, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799919;msg=5;filename=in.pm.patch;att=1
+Bug-Debian: https://bugs.debian.org/799919
+Forwarded: no
+Reviewed-By: Sebastien Badia 
+Last-Update: 2016-03-01
+
+--- asused-3.72.orig/Net/RIPEWhois/in/in.pm
 asused-3.72/Net/RIPEWhois/in/in.pm
+@@ -355,6 +355,10 @@ sub getIn {
+ 		# Changed
+ 		push(@{$in{'ch'}}, $value);
+ 		}
++		elsif($inetnum && $attr eq 'cr') {
++		# Created
++		push(@{$in{'cr'}}, $value);
++		}
+ 		elsif($inetnum && $attr eq 'so') {
+ 		# Source
+ 		$in{'so'} = $value;
+@@ -373,14 +377,14 @@ sub getIn {
+ # Get creation date for valid inetnum object
+ if($inetnum) {
+ # Validate date
+-my $date = $self->creationDate(@{$in{'ch'}});
++my $date = $self->creationDate(@{$in{'cr'}});
+ 	
+ if($date) {
+ $in{'created'} = $date;
+ }
+ else {
+ $self->error($INVALID_DATE, 
+- ("Invalid date in " . join('; ', @{$in{'ch'}})));
++ ("Invalid date in " . join('; ', @{$in{'cr'}})));
+ 
+ push(@{$in{'warning'}}, ($self->error())[1]);
+ }
+@@ -560,7 +564,7 @@ sub  creationDate {
+ my @dateList;
+ #don't trust the date from db
+ foreach my $dateStr (@ch) {
+-	if($dateStr =~ /(\d+)$/) {
++	if($dateStr =~ /([\d\-]+)(T.*)?$/) {
+ 	my $date = $1;
+ return  unless ($date = checkmmDD($date)) ; #look if it is valid date
+ push(@dateList, $date); #make list of valid dates
+@@ -583,6 +587,8 @@ sub checkmmDD {
+ my($yy, $mm, $dd, $utc, $yyActual, $mmActual, $ddActual, $date);
+ my($sec, $min, $hour, $wday, $yday, $isdst); # Temp vars
+ 	
++	$MMdd =~ s/\-//g;
++
+ #MMDD
+ if($MMdd =~ /^(\d{4})(\d{2})(\d{2})$/) {
+ $yy = $1 - 1900;
+@@ -655,6 +661,7 

Bug#839557: Package is empty (aside from man pages)

[Michael Biebl]

Package: debhelper
Version: 10.1
Severity: grave
Tags: patch

My patch to add the dh-systemd transitional package was incomplete. It
missed that debhelper was only building a single binary package and is
now building two.
We either need to add a debhelper.install file now or, as dh-systemd is
actually supposed to be empty, set --destdir=debian/debhelper when
running dh_auto_install.

Attached is a patch for the latter.

Sorry for the mess.

Michael


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (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 debhelper depends on:
ii  autotools-dev20160430.1
ii  binutils 2.27-8
ii  dh-autoreconf12
ii  dh-strip-nondeterminism  0.028-1
ii  dpkg 1.18.10
ii  dpkg-dev 1.18.10
ii  file 1:5.28-4
ii  libdpkg-perl 1.18.10
ii  man-db   2.7.5-1
ii  perl 5.24.1~rc3-3
ii  po-debconf   1.0.19

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201608

-- no debconf information
>From bb6ac51c480a4bff3ebb3377ec583cae22538480 Mon Sep 17 00:00:00 2001
From: Michael Biebl 
Date: Sun, 2 Oct 2016 01:41:34 +0200
Subject: [PATCH] Make sure all files are installed into the debhelper binary
 package

Now that we are building more then one binary package, dh_auto_install
no longer uses debian/debhelper by default. Since the transitional
dh-systemd package is supposed to be empty, override dh_auto_install and
set --destdir=debian/debhelper to make sure all files end up in the
debhelper binary package.
---
 debian/rules | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/rules b/debian/rules
index addfbff..b507359 100755
--- a/debian/rules
+++ b/debian/rules
@@ -16,3 +16,6 @@
 # Disable as they are unneeded (and we can then be sure debhelper
 # builds without needing autotools-dev, dh-strip-nondetermism etc.)
 override_dh_update_autotools_config override_dh_strip_nondeterminism:
+
+override_dh_auto_install:
+	dh_auto_install --destdir=debian/debhelper
-- 
2.9.3

Bug#825487: [Piuparts-devel] Bug#825487: Patch

[Sean Whitton]

Hello Holger,

On Sat, Sep 24, 2016 at 10:30:34AM +, Holger Levsen wrote:
> it would have been easier to me (and thus probably resulted in a sooner
> reply…) if you had presented those questions again, instead of making us
> wade through half answered stuff…
> 
> Huhmf :/ While I could see parts of questions unanswered by me, I do think 
> Andreas
> answered these bits. Could you maybe please just rebase your patch based on 
> that
> feedback and then we comment again? Or, simple isolate the questions and
> repeat them?

Since the questions I asked were quite fundamental to the patch, I'd
prefer to ask some feedback on them before I dive into the code again.

1. --allow-downgrades seems to be necessary when using the `apt-get
install ./foo.deb` invocation, if foo.deb is already installed with the
same version.  Otherwise, the re-install fails.  That breaks piuparts'
standard reinstall test.  (As you say, it is not required with `apt-get
install foo` -- not sure if that is deliberate.)

I'll verify that apt has not changed its behaviour since the time I
prepared my first patch, but if the --allow-downgrades is still
required, do you still object to it?  If so, this bug is wontfix.

2. Andreas said that dropping the call to list_installed_files "breaks
some options that are not frequently used".  What could those options
be?  I thought that list_installed_files should be called once for each
command that is run.  So when I removed the `dpkg -i` call, I removed
the call to list_installed_files.  Why is that wrong?

(of course, I am going to add a check for the version of apt, and if
it's old I'll call `dpkg -i` and list_installed_files, but I'm talking
about the case where apt is new enough and I'm calling `apt-get install
./foo.deb`).

Thanks!

-- 
Sean Whitton

Bug#832824: haskell-src-exts: reporting a bug at GHC for linker error. build fail on mips64el

[Clint Adams]

On Sat, Oct 01, 2016 at 04:06:15PM +0200, Florian Weimer wrote:
> So passing -mxgot would be worth a try.  This seems to be similar to
> the -fpic/-fPIC distinction.

That appears to do the trick.

Bug#705668: mirror submission for ftp.wa.co.za

[Donald Norwood]

Hello,

We are going through the backlog of older mirror submissions and came
across this one. Are you still interested in becoming an official Debian
Mirror? The mirror looks good, though you do not need to carry
/backports/ or /security/.


Best regards,


Donald Norwood
-Debian Mirrors Team


On Fri, 2 May 2014 23:13:59 +0200 Simon Paillard 
wrote:
> Control: tag -1 +moreinfo
>
> Hi,
>
> Sorry for the late reply.
>
> On Thu, Apr 18, 2013 at 09:04:00AM +, Web Africa NOC wrote:
> > Package: mirrors
> > Severity: wishlist
> >
> > Submission-Type: new
> > Site: ftp.wa.co.za
>
> Could you please consider using the recommended tool ftpsync
> at http://debian.org/mirror/ftpmirror#how
> or use http://debian.org/mirror/anonftpsync
>
> > Type: leaf
> > Archive-architecture: amd64 i386 kfreebsd-amd64
> > Archive-ftp: /debian/debian/
> > Archive-http: /debian/debian/
> > Archive-rsync: debian/debian/
> > CDImage-ftp: /debian/debian-cd/
> > CDImage-http: /debian/debian-cd/
> > CDImage-rsync: debian/debian-cd/
> > IPv6: no
> > Archive-upstream: ftp-nyc.osuosl.org
> > CDImage-upstream: free.hands.com
> > Updates: four
> > Maintainer: Web Africa NOC 
> > Country: ZA South Africa
> > Location: Cape Town, South Africa
> > Sponsor: Web Africa http://www.webafrica.co.za/
>
> How much bandwidth is available ?
>
>
> --
> Simon Paillard
>
>



signature.asc
Description: OpenPGP digital signature

Bug#760315: ITP: apache-mesos -- Cluster manager for sharing distributed application frameworks

[Daniel Stender]

I've now spend a couple of hours working on packaging Mesos 1.0.1. There are 
several problems
using Debian packages instead of the libraries vendored/bundled in 3rdparty/.

The config system provides switches like --with-boost, --with-gmock, 
--with-glock etc., but:

1) for Boost they developers are using "-isystem" instead of "-I" imports for 
the CPPFLAGS
to easily overcome some problems 
(https://issues.apache.org/jira/browse/MESOS-3932), but
-isystem makes problems for the other imports:


{...} -c gmock_sources.cc  -fPIC -DPIC -o .libs/libgmock_la-gmock_sources.o
In file included from /usr/include/c++/6/ext/string_conversions.h:41:0,
 from /usr/include/c++/6/bits/basic_string.h:5402,
 from /usr/include/c++/6/string:52,
 from /usr/include/c++/6/bits/locale_classes.h:40,
 from /usr/include/c++/6/bits/ios_base.h:41,
 from /usr/include/c++/6/ios:42,
 from /usr/include/c++/6/ostream:38,
 from gmock-1.7.0/gtest/include/gtest/gtest.h:55,
 from gmock-1.7.0/gtest/src/gtest-all.cc:39,
 from gmock_sources.cc:18:
/usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
directory


see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129 (stdlib.h: No such file 
or directory when using -isystem /usr/... )

2) the gmock import paths are not working out of the box with the google-gmock 
package:

--with-gmock=/usr:


checking gmock-all.cc usability... no
checking gmock-all.cc presence... no
checking for gmock-all.cc... no
configure: error: cannot find gmock
---
You have requested the use of a non-bundled gmock but no suitable
gmock could be found.


it should be going something like:


--- a/configure.ac
+++ b/configure.ac
@@ -808,12 +808,12 @@ AM_CONDITIONAL([WITH_BUNDLED_GLOG],
[test "x$with_bundled_glog" = "xyes"])
  
-GMOCKSRC="gmock-all.cc"
+GMOCKSRC="src/gmock-all.cc"
 GTESTSRC="gtest-all.cc"
 
 if test -n "`echo $with_gmock`"; then
   CPPFLAGS="$CPPFLAGS -I${with_gmock} -I${with_gmock}/include \
--I${with_gmock}/src -I${with_gmock}/gtest -I${with_gmock}/gtest/include \
+-I${with_gmock}/src/gmock -I${with_gmock}/gtest 
-I${with_gmock}/gtest/include \
 -I${with_gmock}/gtest/src"
 
 elif test "x$enable_bundled" != "xyes"; then


The same for the libgtest-dev imports. That could be solved, however

3) the vendored package 3rdparty/nvml-352.79.tar.gz contains solely 
nvidia/gdk/nvml.h, but that
appears not be DFSG-free.

4) libelfio and picojson are both RFP (#839382, #773325), these could be 
packaged by, but

5) the upstream tarball ships own patches for several of the vendored 3rdparts 
tarballs, like
for glog 0.3.3, http-parser 2.6.2 (needs to be updated in Debian, #795492), 
leveldb 1.4, libev 4.22,
protobuf 2.6.1, zookeeper 3.4.8. Some libraries like libprocess are forked in 
own 3rdparty (belonging
to Mesos) repositories on Github (like https://github.com/3rdparty/libprocess). 
I haven't checked
it closer so far, but it could be that there are many things which aren't 
(supposed to being?) integrated
into the other projects.

I haven't given up, but I'm not so sure if there could be solutions for all of 
the points above if
not wanted to ship most of the convenience packages with a mile long 
deb/copyright and just putting the
thing into non-free because of (yet) a single file.

DS

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/



signature.asc
Description: OpenPGP digital signature

Bug#760315: ITP: apache-mesos -- Cluster manager for sharing distributed application frameworks

[Daniel Stender]

On 02.10.2016 01:34, Daniel Stender wrote:
> I've now spend a couple of hours working on packaging Mesos 1.0.1. There are 
> several problems
> using Debian packages instead of the libraries vendored/bundled in 3rdparty/.
> 
> The config system provides switches like --with-boost, --with-gmock, 
> --with-glock etc., but:
> 
> 1) for Boost they developers are using "-isystem" instead of "-I" imports for 
> the CPPFLAGS
> to easily overcome some problems 
> (https://issues.apache.org/jira/browse/MESOS-3932), but
> -isystem makes problems for the other imports:
> 
> 
> {...} -c gmock_sources.cc  -fPIC -DPIC -o .libs/libgmock_la-gmock_sources.o
> In file included from /usr/include/c++/6/ext/string_conversions.h:41:0,
>  from /usr/include/c++/6/bits/basic_string.h:5402,
>  from /usr/include/c++/6/string:52,
>  from /usr/include/c++/6/bits/locale_classes.h:40,
>  from /usr/include/c++/6/bits/ios_base.h:41,
>  from /usr/include/c++/6/ios:42,
>  from /usr/include/c++/6/ostream:38,
>  from gmock-1.7.0/gtest/include/gtest/gtest.h:55,
>  from gmock-1.7.0/gtest/src/gtest-all.cc:39,
>  from gmock_sources.cc:18:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
> 
> 
> see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129 (stdlib.h: No such 
> file or directory when using -isystem /usr/... )
> 
> 2) the gmock import paths are not working out of the box with the 
> google-gmock package:
> 
> --with-gmock=/usr:
> 
> 
> checking gmock-all.cc usability... no
> checking gmock-all.cc presence... no
> checking for gmock-all.cc... no
> configure: error: cannot find gmock
> ---
> You have requested the use of a non-bundled gmock but no suitable
> gmock could be found.
> 
> 
> it should be going something like:
> 
> 
> --- a/configure.ac
> +++ b/configure.ac
> @@ -808,12 +808,12 @@ AM_CONDITIONAL([WITH_BUNDLED_GLOG],
> [test "x$with_bundled_glog" = "xyes"])
>   
> -GMOCKSRC="gmock-all.cc"
> +GMOCKSRC="src/gmock-all.cc"
>  GTESTSRC="gtest-all.cc"
>  
>  if test -n "`echo $with_gmock`"; then
>CPPFLAGS="$CPPFLAGS -I${with_gmock} -I${with_gmock}/include \
> --I${with_gmock}/src -I${with_gmock}/gtest -I${with_gmock}/gtest/include \
> +-I${with_gmock}/src/gmock -I${with_gmock}/gtest 
> -I${with_gmock}/gtest/include \
>  -I${with_gmock}/gtest/src"
>  
>  elif test "x$enable_bundled" != "xyes"; then
> 
> 
> The same for the libgtest-dev imports. That could be solved, however
> 
> 3) the vendored package 3rdparty/nvml-352.79.tar.gz contains solely 
> nvidia/gdk/nvml.h, but that
> appears not be DFSG-free.
> 
> 4) libelfio and picojson are both RFP (#839382, #773325), these could be 
> packaged by, but
> 
> 5) the upstream tarball ships own patches for several of the vendored 
> 3rdparts tarballs, like
> for glog 0.3.3, http-parser 2.6.2 (needs to be updated in Debian, #795492), 
> leveldb 1.4, libev 4.22,
> protobuf 2.6.1, zookeeper 3.4.8. Some libraries like libprocess are forked in 
> own 3rdparty (belonging
> to Mesos) repositories on Github (like 
> https://github.com/3rdparty/libprocess). I haven't checked
> it closer so far, but it could be that there are many things which aren't 
> (supposed to being?) integrated
> into the other projects.
> 
> I haven't given up, but I'm not so sure if there could be solutions for all 
> of the points above if
> not wanted to ship most of the convenience packages with a mile long 
> deb/copyright and just putting the
> thing into non-free because of (yet) a single file.
> 
> DS

... towards 5), https://github.com/3rdparty/glog is a better example, 
libprocess isn't a fork.

DS

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/



signature.asc
Description: OpenPGP digital signature

Bug#839365: libgweather: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2

[Jeremy Bicha]

Control: tags -1 + pending
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=772253

This is fixed in pkg-gnome svn with

https://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/libgweather/debian/patches/Rename-Rangoon-to-Yangon.patch?view=markup

Since I don't think this is urgent, we might just wait until GNOME
gets around to releasing a new version for this issue.

Thanks,
Jeremy

Bug#839547: [pkg-gnupg-maint] Bug#839547: gnupg: unable to decrypt file

[Paul Rogé]

Hi Daniel,

>   dpkg -l 'pinentry-*'

pinentry-gnome3 0.9.7-5 amd64
pinentry-gtk2 0.9.7-5 amd64

>   dpkg -S $(readlink -f $(which pinentry))

pinentry-gnome3: /usr/bin/pinentry-gnome3

> are you running this from a graphical environment (e.g. in an Xterm or
> something), from a virtual terminal, or somewhere else?
> 
I am running this from a graphical environment (rxvt-unicode [9.22-1+b1
amd64]), but the same problem occurs from the console.

> If you do have pinentry installed, does it show you a prompt if you run
> it directly?

This is what I get following your instructions:

OK Pleased to meet you
getpin
D asd
OK
bye
OK closing connection

Bug#826376: mirror submission for muug.ca

[Donald Norwood]

Hi Wyatt,

Sorry about the long delay in getting back to you.

Yes to your question, if you change the rsync url it would be fine. This
would at least give the mirror a uniform appearance:

Archive-ftp: /mirror/debian/
Archive-http: /mirror/debian/
Archive-rsync: /mirror/debian/
CDImage-ftp: /mirror/debian-cd/
CDImage-http: /mirror/debian-cd/
CDImage-rsync: /mirror/debian-cd/

One quick question, your /project/trace directory does not show the name
of your mirror are you mirroring directly from but is instead showing
that of: mirror3.rafal.ca. Are you running your own ftpsync script?

Best regards,

Donald Norwood
-Debian Mirrors Team

On Wed, 8 Jun 2016 14:14:21 -0500 (CDT) mir...@muug.ca wrote:
> Hi Donald, the way our mirror is configured, we have our public
website and the mirror content being served from the same vhost, so it's
preferable for us to keep all of the mirror links as /mirror/* so we're
not filling our root web directory with links. If you guys are adamant
on /debian then we'll create the links, but would prefer not to.
>
> On the note of URL consistency, the rysnc URL could be changed to
/mirror/debian if it's preferable to have everything the same (that link
should work already). The duplicate /mirrors in our ftp directory is
there for a couple of other repos that we haven't moved to the new url yet.
>
> --
> Wyatt
> Manitoba Unix User Group
>
>

-- 
--Donald Norwood
www.debian.org





signature.asc
Description: OpenPGP digital signature

Bug#836226: bug resolved

[Diederik de Haas]

Control: reassign -1 network-manager 1.4.0-3
Control: fixed -1 network-manager/1.4.2-1

On zaterdag 1 oktober 2016 16:04:11 CEST Matt Stamp wrote:
> I would like to confirm that this is now resolved with the newest version
> of  network-manager (1.4.2-1).



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

Bug#822709: cgminer now builds with gcc 6

[Scott Howard]

Hi - I can't reproduce this anymore, and reproducible builds have been
able to compile cgminer with the new gcc default:

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

Maybe something changed somewhere else?

Closing for now.

Thanks

Bug#836226: bug resolved

[Matt Stamp]

I would like to confirm that this is now resolved with the newest version of 
network-manager (1.4.2-1).

You can close this bug.

Bug#839362: assertj-core: FTBFS: Could not resolve dependency cglib:cglib-nodep:jar:3.x

[Emmanuel Bourg]

Control: retitle -1 assertj-core: FTBFS: Could not resolve dependency 
cglib:cglib-nodep:jar:3.x

Thank you for the report Lucas, I'm going to fix this issue. Just note
that the "No such file or directory" message you used in the bug title
isn't the cause of the build failure in this case, you'll see this with every
build using maven-debian-helper and it can be safely ignored. The
actual reason is given by Maven on the first [ERROR] line:

 [ERROR] Failed to execute goal on project assertj-core: Could not
 resolve dependencies for project org.assertj:assertj-core:bundle:2.3.0:
 Cannot access central (https://repo.maven.apache.org/maven2) in
 offline mode and the artifact cglib:cglib-nodep:jar:3.x has not been
 downloaded from it before. -> [Help 1]

This means that a dependency can't be resolved (here cglib:cglib-nodep:jar:3.x
which is currently subject to a transition).

Emmanuel Bourg

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Vagrant Cascadian]

On 2016-09-17, Rick Thomas wrote:
> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
>>  https://bugs.debian.org/837629
>> 
>> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
>> so that u-boot 2016.09 can migrate to stretch... but it would be more
>> ideal to fix it, of course! :)
>
> It looks like you’ll have to pull OpenRD support out of this version.
> I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result
> with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no
> response following u-boot “reset” command.

I've uploaded packages based on 2016.09.01 to:

  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main

The repository should be signed by my key, available in the
debian-keyring package in the archive
(F0ADA5240891831165DF98EA7CFCD8CD257721E9).

There were two critical fixes in 2016.09.01, *maybe* they fix the issue?

If not, I'll likely be removing OpenRD* from the packages on future
uploads.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#839556: mutt: The default 'y' keybind no longer works in a POP mailbox.

[Michel]

Package: mutt
Version: 1.7.0-6
Severity: important

Dear Maintainer,

After entering a POP mailbox and needing to go back to the list of
mailboxes. From the index menu, the pager menu and possibly all others.
Using the default 'y' key bind:

yM ?show incoming mailboxes list

No longer works, get the following error:

Cannot edit message: Operation not permitted by ACL

* What led up to the situation?

After upgrading:

[UPGRADE] mutt:amd64 1.7.0-1 -> 1.7.0-5

* What exactly did you do (or not do) that was effective (or
  ineffective)?

Also tried with previous versions to see where this started. Versions
1.7.0-1 and 1.7.0-2 work as expected. While all versions after 1.7.0-2,
do not. Previous versions where obtained from S.D.O[0].

For all versions IMAP and Maildir mailboxes work as expected. So it
seems to be only an POP mailboxes issue.

Looked through upstream's mutt and neomutt bug reports; did not find a
similar bug report, before filing this bug report.

* What was the outcome of this action?

As explained above, the 'y' key bind no longer works in a POP mailbox
with versions after 1.7.0-2.

The only way to get the back to the mailboxes list is to quit mutt.

* What outcome did you expect instead?

Go back to the list of mailboxes.

Thank You


[0] http://snapshot.debian.org/binary/mutt/


-- Package-specific info:
NeoMutt 20160916 (1.7.0)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 4.7.0-1-amd64 (x86_64)
libidn: 1.33 (compiled with 1.33)
hcache backend: tokyocabinet 1.4.48

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.2.0-4' 
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext 
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib 
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch -
 -with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.2.0 20160914 (Debian 6.2.0-4) 

Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-notmuch' '--disable-fmemopen' 
'--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' 
'--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm' 
'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/mutt-WCcuvM/mutt-1.7.0=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security' 'LDFLAGS=-fPIE -pie 
-Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORT
 IFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 
-fdebug-prefix-map=/build/mutt-WCcuvM/mutt-1.7.0=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security

Compile options:
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME 
+DEBUG +DL_STANDALONE +ENABLE_NLS -EXACT_ADDRESS -HOMESPOOL -LOCALES_HACK 
-SUN_ATTACHMENT +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET +HAVE_GETADDRINFO 
+HAVE_GETSID +HAVE_ICONV +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR 
+HAVE_LIBIDN +HAVE_META +HAVE_REGCOMP +HAVE_RESIZETERM +HAVE_START_COLOR 
+HAVE_TYPEAHEAD +HAVE_WC_FUNCS +ICONV_NONTRANS +USE_COMPRESSED +USE_DOTLOCK 
+USE_FCNTL -USE_FLOCK -USE_FMEMOPEN -USE_GNU_REGEX +USE_GSS +USE_HCACHE 
+USE_IMAP +USE_NOTMUCH +USE_NNTP +USE_POP +USE_SASL +USE_SETGID +USE_SIDEBAR 
+USE_SMTP 

Bug#839554: Fwd: Message with no Package: tag cannot be processed! (installation-reports: failure to format and mount EFI partition during installation)

[Cyril Brulebois]

Hi Jeroen,

Jeroen Van den Keybus  (2016-10-01):
> Dear Maintainer,
> 
> Installed -testing using debian-testing-amd64-netinst.iso over IPMI on a
> Super Micro X10DRL.
> 
> In short: used guided to create EFI and main partitions, then removed the 60G
> swap (?!) and main partitions. Then created a single btrfs partition of around
> 119G (guided took care of the 1M gap at 0..2047).
> 
> It seems the EFI partition is created but not formatted nor mounted.
> After that, the install fails obviously.
> 
> In dmesg: FAT-fs (sda1): IO charset ascii not found
> 
> Mounting is succesful if done with 'mount /dev/sda1 /target/boot/efi -o
> iocharset=utf8' in a shell. mkfs.fat -F32 is also not a problem.
> 
> But installer is unaware of course, and cannot proceed.
> 
> >From IRC interaction with 'KIBI' and 'bwh' it is apparent that nls_ascii
> module is missing after default FAT mount options have changed in the
> kernel (commit 0e156c15e31ac4f3e160a6ac262b172d0390d7e8).

As debian-boot@ people might have noticed, I filed this bug report
accordingly:

  #839552: linux: please add nls_ascii to fat-modules udeb


KiBi.


signature.asc
Description: Digital signature

Bug#797271: Synaptic false positive, does not launch

[Olly Betts]

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

On Fri, Aug 28, 2015 at 09:57:08PM -0400, Carlos Kosloff wrote:
> I did not do anything except dist-upgrade my system with apt-get.
> All of a sudden synaptic will not launch.
> Reports a false positive, bad password given for root.
> This is not correct because I can launch synaptic from console as root.
> I think that this bug arises from a faulty implementation of policykit-1

I just NMUed synaptic, and while testing my build I couldn't reproduce
this issue.  Hence lowering severity and tagging as unreproducible.

Cheers,
Olly

Bug#811857: synaptic: diff for NMU version 0.83+nmu1

[Olly Betts]

Control: tags 811857 + patch

Dear maintainer,

I've prepared an NMU for synaptic (versioned as 0.83+nmu1) and
uploaded it under the zero-day NMU rules as this FTBFS was blocking
the auto-xapian-core transition.

The patch applied was cherry-picked from your git repo.

Cheers,
Olly
diff -Nru synaptic-0.83/debian/changelog synaptic-0.83+nmu1/debian/changelog
--- synaptic-0.83/debian/changelog	2016-01-11 22:20:13.0 +1300
+++ synaptic-0.83+nmu1/debian/changelog	2016-10-02 09:50:57.0 +1300
@@ -1,3 +1,11 @@
+synaptic (0.83+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with GCC6 (Closes: #811857)
++ New patch 99_fix_build_with_gcc6, cherry-picked from git.
+
+ -- Olly Betts   Sun, 02 Oct 2016 09:50:57 +1300
+
 synaptic (0.83) unstable; urgency=medium
 
   [ xuzhen ]
diff -Nru synaptic-0.83/debian/patches/00list synaptic-0.83+nmu1/debian/patches/00list
--- synaptic-0.83/debian/patches/00list	2016-01-11 22:22:42.0 +1300
+++ synaptic-0.83+nmu1/debian/patches/00list	2016-10-02 09:50:57.0 +1300
@@ -0,0 +1 @@
+99_fix_build_with_gcc6
diff -Nru synaptic-0.83/debian/patches/00list.Debian synaptic-0.83+nmu1/debian/patches/00list.Debian
--- synaptic-0.83/debian/patches/00list.Debian	2016-01-11 22:20:13.0 +1300
+++ synaptic-0.83+nmu1/debian/patches/00list.Debian	2016-10-02 09:49:29.0 +1300
@@ -0,0 +1 @@
+99_fix_build_with_gcc6
diff -Nru synaptic-0.83/debian/patches/99_fix_build_with_gcc6.dpatch synaptic-0.83+nmu1/debian/patches/99_fix_build_with_gcc6.dpatch
--- synaptic-0.83/debian/patches/99_fix_build_with_gcc6.dpatch	1970-01-01 12:00:00.0 +1200
+++ synaptic-0.83+nmu1/debian/patches/99_fix_build_with_gcc6.dpatch	2016-10-02 09:50:39.0 +1300
@@ -0,0 +1,38 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 99_fix_build_with_gcc6.dpatch
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: commit a18b8e55c78f735446db69010872b66e8fbd5ff4
+## DP: Author: Michael Vogt 
+## DP: Date:   Thu Jan 21 16:59:53 2016 +0100
+## DP: 
+## DP: Fix build with gcc6
+## DP: 
+## DP: The make_pair() functions does not take a template parameter
+## DP: anymore.
+## DP: 
+## DP: Thanks: Martin Michlmayer
+## DP: Closes: #811857
+
+@DPATCH@
+diff --git a/gtk/rglogview.cc b/gtk/rglogview.cc
+index b55bc8da..317457d2 100644
+--- a/gtk/rglogview.cc
 b/gtk/rglogview.cc
+@@ -23,6 +23,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ 
+ #include "config.h"
+@@ -86,7 +87,7 @@ void RGLogView::readLogs()
+ 			 COLUMN_LOG_TYPE, LOG_TYPE_TOPLEVEL, 
+ 			 -1);
+ 	 g_free(sort_key);
+-	 history_map.insert(make_pair(history_key,month_iter));
++	 history_map.insert(std::make_pair(history_key,month_iter));
+   } else {
+ 	 month_iter = history_map[history_key];
+   }


signature.asc
Description: PGP signature

Bug#838914: mariadb-10.0: testsuite failures on mips/mipsel

[Otto Kekäläinen]

Hello!

Thank you very much and well done for fixing so many test failures in one go!

I noticed however that one test started to fail om amd64 now. Builds
on i386 and ppc64 are OK. Output below and full log visible at
https://launchpadlibrarian.net/287683886/buildlog_ubuntu-xenial-amd64.mariadb-10.0_10.0.27-2~xenial1~1475349704.695a347_BUILDING.txt.gz

The stack trace mentions groonga - maybe you groonga/libatomic change
introduced a regression? Just an idea, I am not an expert on this.

Did you test building on amd64 with your modifications?


***

plugins.show_all_plugins w2 [ fail ]
Test ended at 2016-10-01 20:04:21

CURRENT_TEST: plugins.show_all_plugins


The server [mysqld.1 - pid: 5113, winpid: 5113, exit: 256] crashed
while running 'check warnings'
Server log from this test:
--SERVER LOG START---
161001 20:04:20 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.27-MariaDB-2~xenial1~1475349704.695a347
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
62788 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
--SERVER LOG END-
mysqltest failed but provided no output
The result from queries just before the failure was:
< snip >
show status like '%libraries%';
Variable_name Value
Opened_plugin_libraries 2
show plugins soname like '%example%';
Name Status Type Library License
EXAMPLE NOT INSTALLED STORAGE ENGINE ha_example.so GPL
UNUSABLE NOT INSTALLED DAEMON ha_example.so GPL
daemon_example NOT INSTALLED DAEMON libdaemon_example.so GPL
three_attempts NOT INSTALLED AUTHENTICATION dialog_examples.so GPL
two_questions NOT INSTALLED AUTHENTICATION dialog_examples.so GPL
show status like '%libraries%';
Variable_name Value
Opened_plugin_libraries 6
show plugins soname where library = 'ha_example.so';
Name Status Type Library License
EXAMPLE NOT INSTALLED STORAGE ENGINE ha_example.so GPL
UNUSABLE NOT INSTALLED DAEMON ha_example.so GPL
select variable_value > 10 from information_schema.global_status where
variable_name like '%libraries%';
variable_value > 10
1



 - saving 
'/«PKGBUILDDIR»/builddir/mysql-test/var/2/log/plugins.show_all_plugins/'
to '/«PKGBUILDDIR»/builddir/mysql-test/var/log/plugins.show_all_plugins/'

Bug#839555: apt: build-dep with an non-existent file gives unhelpful error message

[Mattia Rizzolo]

package: apt
version: 1.3
severity: minor

root@chase:~# apt-get build-dep /non-existent-dir/file.dsc
E: Unsupported file /non-existent-dir/file.dsc given on commandline
E: Must specify at least one package to check builddeps for
root@chase:~# apt --version
apt 1.3 (amd64)
root@chase:~# 

Well, I'd like to see a proper ENOENT message, rather than an untrue
"unsupported file" :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#839554: Fwd: Message with no Package: tag cannot be processed! (installation-reports: failure to format and mount EFI partition during installation)

[Jeroen Van den Keybus]

Package: installation-reports
Severity: important

Dear Maintainer,

Installed -testing using debian-testing-amd64-netinst.iso over IPMI on a
Super Micro X10DRL.

In short: used guided to create EFI and main partitions, then removed the 60G
swap (?!) and main partitions. Then created a single btrfs partition of around
119G (guided took care of the 1M gap at 0..2047).

It seems the EFI partition is created but not formatted nor mounted.
After that, the install fails obviously.

In dmesg: FAT-fs (sda1): IO charset ascii not found

Mounting is succesful if done with 'mount /dev/sda1 /target/boot/efi -o
iocharset=utf8' in a shell. mkfs.fat -F32 is also not a problem.

But installer is unaware of course, and cannot proceed.

>From IRC interaction with 'KIBI' and 'bwh' it is apparent that nls_ascii
module is missing after default FAT mount options have changed in the
kernel (commit 0e156c15e31ac4f3e160a6ac262b172d0390d7e8).

Best regards,


J. Van den Keybus


-- Package-specific info:

Boot method: network
Image version: debian-testing-amd64-netinst.iso
Date: 

Machine: SuperMicro X10DRL-I-O
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [E]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




--

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20161001-00:04"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux x10drl 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1
(2016-09-26) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E7
v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 [8086:6f00] (rev 01)
lspci -knn: Subsystem: Super Micro Computer Inc Device [15d9:0831]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E7
v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 [8086:6f02]
(rev 01)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation Xeon E7
v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 [8086:6f08]
(rev 01)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:04.0 System peripheral [0880]: Intel Corporation Xeon
E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 0
[8086:6f20] (rev 01)
lspci -knn: Subsystem: Super Micro Computer Inc Device [15d9:0831]
lspci -knn: 00:04.1 System peripheral [0880]: Intel Corporation Xeon
E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 1
[8086:6f21] (rev 01)
lspci -knn: Subsystem: Super Micro Computer Inc Device [15d9:0831]
lspci -knn: 00:04.2 System peripheral [0880]: Intel Corporation Xeon
E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 2
[8086:6f22] (rev 01)
lspci -knn: Subsystem: Super Micro Computer Inc Device [15d9:0831]
lspci -knn: 00:04.3 System peripheral [0880]: Intel Corporation Xeon
E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 3
[8086:6f23] (rev 01)
lspci -knn: Subsystem: Super Micro Computer Inc Device [15d9:0831]
lspci -knn: 00:04.4 System peripheral [0880]: Intel Corporation Xeon
E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 4
[8086:6f24] (rev 01)
lspci -knn: Subsystem: Super Micro Computer Inc Device [15d9:0831]
lspci -knn: 00:04.5 System peripheral [0880]: Intel Corporation Xeon
E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 5
[8086:6f25] (rev 01)
lspci -knn: Subsystem: Super Micro Computer Inc Device [15d9:0831]
lspci -knn: 00:04.6 System peripheral [0880]: Intel Corporation Xeon
E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 6
[8086:6f26] (rev 01)
lspci -knn: Subsystem: Super Micro Computer Inc Device [15d9:0831]
lspci -knn: 00:04.7 System peripheral [0880]: Intel Corporation Xeon
E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 7
[8086:6f27] (rev 01)
lspci -knn: Subsystem: Super Micro Computer Inc Device [15d9:0831]
lspci -knn: 00:05.0 System peripheral [0880]: Intel Corporation Xeon
E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management
[8086:6f28] (rev 01)
lspci -knn: Subsystem: Super Micro Computer Inc Device [15d9:0831]
lspci -knn: 00:05.1 

Bug#839553: lintian: check the canonical form of the homepage field of CRAN R packages

[Dylan]

Package: lintian
Version: 2.5.47
Severity: wishlist
Tags: patch

Hi,
Please find attached a patch which add the check of the canonical form
of the homepage field for CRAN R packages.

Any comments/suggestions on this patch are welcome :-)

Best,
Dylan
From ca242bed450f305af621992f384a819717ade2cc Mon Sep 17 00:00:00 2001
From: Dylan Aïssi 
Date: Fri, 30 Sep 2016 07:47:04 +
Subject: [PATCH] c/fields: Check for the canonical form of the homepage field of CRAN R packages

---
 checks/fields.desc| 16 
 checks/fields.pm  |  4 
 t/tests/fields-cran-homepage/debian/debian/control.in | 16 
 t/tests/fields-cran-homepage/desc |  4 
 t/tests/fields-cran-homepage/tags |  2 ++
 5 files changed, 42 insertions(+)
 create mode 100644 t/tests/fields-cran-homepage/debian/debian/control.in
 create mode 100644 t/tests/fields-cran-homepage/desc
 create mode 100644 t/tests/fields-cran-homepage/tags

diff --git a/checks/fields.desc b/checks/fields.desc
index abcbd43..1830448 100644
--- a/checks/fields.desc
+++ b/checks/fields.desc
@@ -1291,3 +1291,19 @@ Info: This .dsc file contains no Checksum-Sha256 field and hence only
  Accordingly it can be fixed by simply rebuilding the source package
  with a more recent dpkg-source version, i.e. by uploading a new
  Debian release of the package.
+
+Tag: homepage-for-cran-package-not-canonical
+Severity: wishlist
+Certainty: certain
+Info: The Homepage field for this package points to an uncanonical CRAN URL.
+ Please update to use the current canonical URL instead. The canonical URL is
+ recommended for use in publications, etc., will always redirect to current
+ release version (or devel if package is not in release yet). For example, the
+ link for the package "foo" should be:
+ .
+ https://cran.r-project.org/package=foo
+ .
+ not:
+ .
+ https://cran.r-project.org/web/packages/foo/index.html
+Ref: At the bottom of the page of each CRAN package.
diff --git a/checks/fields.pm b/checks/fields.pm
index 328f0f9..4cc2b65 100644
--- a/checks/fields.pm
+++ b/checks/fields.pm
@@ -616,6 +616,10 @@ sub run {
 {
 tag 'homepage-for-cpan-package-contains-version', $orig;
 }
+if ($homepage=~ m,/cran\.r-project\.org/web/packages/.+,)
+{
+tag 'homepage-for-cran-package-not-canonical', $orig;
+}
 } elsif (not $info->native) {
 if ($type eq 'source') {
 my $binary_has_homepage_field = 0;
diff --git a/t/tests/fields-cran-homepage/debian/debian/control.in b/t/tests/fields-cran-homepage/debian/debian/control.in
new file mode 100644
index 000..0799038
--- /dev/null
+++ b/t/tests/fields-cran-homepage/debian/debian/control.in
@@ -0,0 +1,16 @@
+Source: {$source}
+Priority: extra
+Section: {$section}
+Maintainer: {$author}
+Standards-Version: {$standards_version}
+Build-Depends: {$build_depends}
+Homepage: https://cran.r-project.org/web/packages/foo/index.html
+
+Package: {$source}
+Architecture: {$architecture}
+Depends: $\{shlibs:Depends\}, $\{misc:Depends\}
+Description: {$description}
+ This is a test package designed to exercise some feature or tag of
+ Lintian.  It is part of the Lintian test suite and may do very odd
+ things.  It should not be installed like a regular package.  It may
+ be an empty package.
\ No newline at end of file
diff --git a/t/tests/fields-cran-homepage/desc b/t/tests/fields-cran-homepage/desc
new file mode 100644
index 000..6d4c434
--- /dev/null
+++ b/t/tests/fields-cran-homepage/desc
@@ -0,0 +1,4 @@
+Testname: fields-cran-homepage
+Version: 1.0
+Description: CRAN Homepage URLs should be canonical
+Test-For: homepage-for-cran-package-not-canonical
\ No newline at end of file
diff --git a/t/tests/fields-cran-homepage/tags b/t/tests/fields-cran-homepage/tags
new file mode 100644
index 000..ee519af
--- /dev/null
+++ b/t/tests/fields-cran-homepage/tags
@@ -0,0 +1,2 @@
+I: fields-cran-homepage source: homepage-for-cran-package-not-canonical https://cran.r-project.org/web/packages/foo/index.html
+I: fields-cran-homepage: homepage-for-cran-package-not-canonical https://cran.r-project.org/web/packages/foo/index.html
-- 
2.1.4

Bug#839119: mirror submission for mirrors.xjtu.edu.cn

[Donald Norwood]

Hello,

Your mirror has been added to the official Debian mirrors list.

Thank you for your support and for mirroring Debian!

Best regards,

Donald Norwood
-Debian Mirrors Team

On Thu, 29 Sep 2016 05:50:31 + "Tiaozhan Operation Team"
 wrote:
> Package: mirrors
> Severity: wishlist
> User: mirr...@packages.debian.org
> Usertags: mirror-submission
>
> Submission-Type: new
> Site: mirrors.xjtu.edu.cn
> Aliases: mirrors.tiaozhan.com
> Type: leaf
> Archive-architecture: amd64 i386
> Archive-http: /debian/
> CDImage-http: /debian-cd/
> IPv6: no
> Archive-upstream: mirrors.tuna.tsinghua.edu.cn
> CDImage-upstream: mirrors.tuna.tsinghua.edu.cn
> Updates: four
> Maintainer: Tiaozhan Operation Team 
> Country: CN China
> Location: Xi'an, ShaanXi
>
>



signature.asc
Description: OpenPGP digital signature

Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed

[Steven Chamberlain]

retitle 827319 vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed
found 827319 src:vim/2:7.4.2330-1
thanks

Hi,

The error is slightly different now.

Test_communicate was fixed upstream:
|   1621  7.4.2154  Test_communicate() fails sometimes

But now, a new error is being seen on kfreebsd and interestingly, also
on linux-alpha:

| Found errors in Test_tagcase():
| Caught exception in Test_tagcase(): Vim(edit):E37: No write since last change 
(add ! to override) @ function RunTheTest[9]..Test_tagcase, line 3
| TEST FAILURE

The regression appeared somewhere between
2:7.4.1829-1 and 2:7.4.2330-1.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Bug#839552: linux: please add nls_ascii to fat-modules udeb

[Cyril Brulebois]

Source: linux
Version: 4.7.5-1
Severity: important
Tags: d-i patch

Hi,

Please merge the attached patch to fix a regression with EFI-related
mounts within d-i after the iocharset change in 4.7.2-1, as discussed
earlier on #debian-boot.

Thanks for considering.


KiBi.
>From b070d6c03057027664fef13f154a29d9f81cc0f6 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Sat, 1 Oct 2016 23:40:54 +0200
Subject: [PATCH] Add nls_ascii to the fat-modules udeb.

See commit 0e156c15e31ac4f3e160a6ac262b172d0390d7e8 for the details
about utf8 vs. ascii iocharset for FAT. This fixes a regression with
EFI-related mounts within the Debian Installer.

Signed-off-by: Cyril Brulebois 
---
 debian/changelog | 6 ++
 debian/installer/modules/fat-modules | 2 ++
 2 files changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 29fdb48..4f700c5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,14 @@
 linux (4.7.5-2) UNRELEASED; urgency=medium
 
+  [ Ben Hutchings ]
   * debian/bin/gencontrol.py: Fix cross-build-dependencies if invoked under
 dpkg-buildpackage
 
+  [ Cyril Brulebois ]
+  * Add nls_ascii to the fat-modules udeb, following the change of
+iocharset default in 4.7.2-1. This fixes a regression with EFI-related
+mounts within the Debian Installer.
+
  -- Ben Hutchings   Mon, 26 Sep 2016 22:27:31 +0100
 
 linux (4.7.5-1) unstable; urgency=medium
diff --git a/debian/installer/modules/fat-modules b/debian/installer/modules/fat-modules
index 37e6d05..377ae03 100644
--- a/debian/installer/modules/fat-modules
+++ b/debian/installer/modules/fat-modules
@@ -4,3 +4,5 @@ vfat
 nls_cp437 ?
 # the default i/o character set for fat (as of 2.6.25)
 nls_utf8 ?
+# the default i/o character set for fat (as of 4.7.2-1)
+nls_ascii ?
-- 
2.1.4

Bug#760277: spamassassin: URIDNSBL.pm complains about $rdatanum if URIBL* is turned off

[Noah Meyerhans]

On Thu, Sep 29, 2016 at 11:36:01PM -0400, Peter Colberg wrote:
> I have prepared an NMU based on the upstream patch, which resolves
> the issue of using uninitialized values in URIDNSBL.pm at line 1042.
> 
> Please let me know whether you are going to upload a new version soon,
> or whether I should request sponsorship for an NMU by debian-mentors.

Hi Peter. Thank you. Please proceed with the sponsored NMU. I probably
*should* be preparing a new upload soon, but haven't started work
towards one yet.

noah



signature.asc
Description: PGP signature

Bug#839119: merge 839119 827746

[Donald Norwood]

merge 839119 827746



signature.asc
Description: OpenPGP digital signature

Bug#817742: yaret: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Bump to 10.
  * debian/control:
- Build-depend on debhelper (>= 10).
- Move all Build-Depends-Indep to Build-Depends, since they're used in
  the clean target.

Thanks for considering the patch.

Logan Rosen
diff -u yaret-2.1.0/debian/control yaret-2.1.0/debian/control
--- yaret-2.1.0/debian/control
+++ yaret-2.1.0/debian/control
@@ -2,7 +2,7 @@
 Section: sound
 Priority: optional
 Maintainer: Marco Nenciarini 
-Build-Depends-Indep: cdbs, debhelper (>= 5.0.0), quilt
+Build-Depends: cdbs, debhelper (>= 10), quilt
 Standards-Version: 3.6.2.2
 
 Package: yaret
diff -u yaret-2.1.0/debian/compat yaret-2.1.0/debian/compat
--- yaret-2.1.0/debian/compat
+++ yaret-2.1.0/debian/compat
@@ -1 +1 @@
-4
+10

Bug#839547: [pkg-gnupg-maint] Bug#839547: gnupg: unable to decrypt file

[Daniel Kahn Gillmor]

Hi Paul--

On Sat 2016-10-01 13:33:20 -0700, Paul Roge wrote:
> After updated gnupg, I am unable to decrypt files with "gpg --decrypt 
> [file].gpg". The following error is generated:
>
>> gpg: encrypted with 2048-bit RSA key, ID 3A2B8EB7865452A1, created 2014-02-28
>>   "Paul Rogé "
>> gpg: public key decryption failed: Operation cancelled
>> gpg: decryption failed: No secret key
>
> I have checked that a secret key exists by "gpg --edit-key 3A2B8EB7865452A1", 
> which states:
>
>> Secret key is available.
>> 
>> sec  rsa2048/40E25F025E23DE01
>>  created: 2014-02-28  expires: 2017-03-14  usage: SC  
>>  trust: ultimate  validity: ultimate
>> ssb  rsa2048/3A2B8EB7865452A1
>>  created: 2014-02-28  expires: 2017-03-14  usage: E   
>> [ultimate] (1). Paul Rogé 
>> [ultimate] (2)  Paul Rogé 
>> [ultimate] (3)  Paul Rogé 
>> [ultimate] (4)  Paul Rogé 
>
> I also ran the script "/usr/bin/migrate-pubring-from-classic-gpg --default", 
> but the same problem persists.

Thanks for the report!  it sounds like maybe the problem is with
pinentry, which is what gpg-agent uses to get permission for use of the
secret key -- what version of pinentry do you have installed?

  dpkg -l 'pinentry-*'
  dpkg -S $(readlink -f $(which pinentry))

are you running this from a graphical environment (e.g. in an Xterm or
something), from a virtual terminal, or somewhere else?

If you do have pinentry installed, does it show you a prompt if you run
it directly?  If you run it directly (as "pinentry") it should print out
"OK pleased to meet you".  at that point, you can type "getpin" and hit
enter, and it should prompt you for a passphrase.  enter a dummy
passphrase into whatever dialog you get, and then pinentry should write
it (prefixed with "D ") and then will write "OK".  after that "OK", you
can type "bye" to terminate.

does that work for you?

 --dkg


signature.asc
Description: PGP signature

Bug#839551:

[Joshua Hudson]

Patch included; I sent the same patch upstream but they seem checked out.

diff -ru stock/rdesktop-1.8.3/doc/rdesktop.1 work/rdesktop-1.8.3/doc/rdesktop.1
--- stock/rdesktop-1.8.3/doc/rdesktop.1 2016-10-01 12:21:55.0 -0700
+++ work/rdesktop-1.8.3/doc/rdesktop.1  2016-10-01 13:47:33.913176792 -0700
@@ -63,15 +63,18 @@
 so its use is discouraged.
 .TP
 .BR "-g "
-Desktop geometry (WxH). If geometry is the special word "workarea",
the geometry
-will be fetched from the extended window manager hints property
_NET_WORKAREA, from
-the root window. The geometry can also be specified as a percentage
of the whole
-screen, e.g. "-g 80%".
-
+Desktop geometry (WxH[@DPI][+X[+Y]]). If geometry is the special word
+"workarea", the geometry will be fetched from the extended window
+manager hints property _NET_WORKAREA, from the root window. The geometry
+can also be specified as a percentage of the whole screen, e.g. "-g 80%".
 If the specified geometry depends on the screen size, and the screen
 size is changed, rdesktop will automatically reconnect using the new
 screen size. This requires that rdesktop has been compiled with RandR
 support.
+
+The optional DPI parameter should be specified if the screen rdesktop
+is being displayed on is too far from 96 DPI for unscaled Windows to
+be readable. Windows currently accepts values from 96 to 480.
 .TP
 .BR "-i"
 Use password as smartcard pin. If a valid user certificate is matched
in smart card
@@ -123,6 +126,11 @@
 Do not send mouse motion events.  This saves bandwidth, although some Windows
 applications may rely on receiving mouse motion.
 .TP
+.BR "-M"
+Use the local X cursor rather than the one from the remote machine.
This is most
+useful with "-m" but has other uses. If running with no window manager, use
+xsetroot(1) to set a useful cursor first.
+.TP
 .BR "-C"
 Use private colourmap.  This will improve colour accuracy on an 8-bit display,
 but rdesktop will appear in false colour when not focused.
diff -ru stock/rdesktop-1.8.3/rdesktop.c work/rdesktop-1.8.3/rdesktop.c
--- stock/rdesktop-1.8.3/rdesktop.c 2016-10-01 12:21:55.0 -0700
+++ work/rdesktop-1.8.3/rdesktop.c  2016-10-01 13:41:59.146946782 -0700
@@ -72,6 +72,7 @@
   requested. If 1, the geometry will be fetched
   from _NET_WORKAREA. If negative, absolute 
value
   specifies the percent of the whole screen. */
+int g_dpi = 0; /* device DPI: default not set */
 int g_width = 800;
 int g_height = 600;
 int g_xpos = 0;
@@ -97,6 +98,7 @@
 RD_BOOL g_polygon_ellipse_orders = True;   /* polygon / ellipse orders */
 RD_BOOL g_fullscreen = False;
 RD_BOOL g_grab_keyboard = True;
+RD_BOOL g_local_cursor = False;
 RD_BOOL g_hide_decorations = False;
 RDP_VERSION g_rdp_version = RDP_V5;/* Default to version 5 */
 RD_BOOL g_rdpclip = True;
@@ -190,7 +192,7 @@
fprintf(stderr, "   -p: password (- to prompt)\n");
fprintf(stderr, "   -n: client hostname\n");
fprintf(stderr, "   -k: keyboard layout on server (en-us, de, sv, 
etc.)\n");
-   fprintf(stderr, "   -g: desktop geometry (WxH)\n");
+   fprintf(stderr, "   -g: desktop geometry (WxH[@dpi])\n");
 #ifdef WITH_SCARD
fprintf(stderr, "   -i: enables smartcard authentication, password
is used as pin\n");
 #endif
@@ -204,6 +206,7 @@
fprintf(stderr, "   -e: disable encryption (French TS)\n");
fprintf(stderr, "   -E: disable encryption from client to server\n");
fprintf(stderr, "   -m: do not send motion events\n");
+   fprintf(stderr, "   -M: use local mouse cursor\n");
fprintf(stderr, "   -C: use private colour map\n");
fprintf(stderr, "   -D: hide window manager decorations\n");
fprintf(stderr, "   -K: keep window manager key bindings\n");
@@ -579,7 +582,7 @@
 #define VNCOPT
 #endif
while ((c = getopt(argc, argv,
-  VNCOPT 
"A:u:L:d:s:c:p:n:k:g:o:fbBeEitmzCDKS:T:NX:a:x:Pr:045h?")) != -1)
+  VNCOPT 
"A:u:L:d:s:c:p:n:k:g:o:fbBeEitmMzCDKS:T:NX:a:x:Pr:045h?")) != -1)
{
switch (c)
{
@@ -694,6 +697,16 @@
p++;
}

+   if (*p == '@')
+   {
+   g_dpi = strtol(p + 1, , 10);
+   if (g_dpi <= 0)
+   {
+   error("invalid geometry\n");
+   return EX_USAGE;
+   }
+   }
+
if (*p == '+' || *p == '-')
{
g_pos |= (*p == '-') ? 2 : 1;
@@ -731,6 +744,8 @@
case 

Bug#839551: rdesktop needs fixes for DPI and Mouse Cursor for Windows 10

[Joshua]

Package: rdesktop
Version: 1.8.3-1
Severity: important
Tags: patch

RDP needs the following fixes to work well connecting to Windows 10

1) Support passing DPI to Windows 10 RDP Server; Windows 10 lost support
for using the registry provided value in this case.

2) Support using the desktop manager provided cursor instead of the remote
machine cursor; in some determinstic scenarios the remote cursor is no good,
but this is borderline impossible to detect. The user will know what to do.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages rdesktop depends on:
ii  libasound21.0.28-1
ii  libc6 2.19-18+deb8u6
ii  libgssglue1   0.4-2
ii  libpcsclite1  1.8.13-1
ii  libssl1.0.0   1.0.1t-1+deb8u5
ii  libx11-6  2:1.6.2-3
ii  libxrandr22:1.4.2-1+b1

rdesktop recommends no packages.

Versions of packages rdesktop suggests:
pn  pcscd  

-- no debconf information
diff -ru stock/rdesktop-1.8.3/doc/rdesktop.1 work/rdesktop-1.8.3/doc/rdesktop.1
--- stock/rdesktop-1.8.3/doc/rdesktop.1	2016-10-01 12:21:55.0 -0700
+++ work/rdesktop-1.8.3/doc/rdesktop.1	2016-10-01 13:47:33.913176792 -0700
@@ -63,15 +63,18 @@
 so its use is discouraged.
 .TP
 .BR "-g "
-Desktop geometry (WxH). If geometry is the special word "workarea", the geometry
-will be fetched from the extended window manager hints property _NET_WORKAREA, from
-the root window. The geometry can also be specified as a percentage of the whole
-screen, e.g. "-g 80%". 
-
+Desktop geometry (WxH[@DPI][+X[+Y]]). If geometry is the special word
+"workarea", the geometry will be fetched from the extended window
+manager hints property _NET_WORKAREA, from the root window. The geometry
+can also be specified as a percentage of the whole screen, e.g. "-g 80%". 
 If the specified geometry depends on the screen size, and the screen
 size is changed, rdesktop will automatically reconnect using the new
 screen size. This requires that rdesktop has been compiled with RandR
 support.
+
+The optional DPI parameter should be specified if the screen rdesktop
+is being displayed on is too far from 96 DPI for unscaled Windows to
+be readable. Windows currently accepts values from 96 to 480.
 .TP
 .BR "-i"
 Use password as smartcard pin. If a valid user certificate is matched in smart card
@@ -123,6 +126,11 @@
 Do not send mouse motion events.  This saves bandwidth, although some Windows
 applications may rely on receiving mouse motion.
 .TP
+.BR "-M"
+Use the local X cursor rather than the one from the remote machine. This is most
+useful with "-m" but has other uses. If running with no window manager, use
+xsetroot(1) to set a useful cursor first.
+.TP
 .BR "-C"
 Use private colourmap.  This will improve colour accuracy on an 8-bit display,
 but rdesktop will appear in false colour when not focused.
diff -ru stock/rdesktop-1.8.3/rdesktop.c work/rdesktop-1.8.3/rdesktop.c
--- stock/rdesktop-1.8.3/rdesktop.c	2016-10-01 12:21:55.0 -0700
+++ work/rdesktop-1.8.3/rdesktop.c	2016-10-01 13:41:59.146946782 -0700
@@ -72,6 +72,7 @@
    requested. If 1, the geometry will be fetched
    from _NET_WORKAREA. If negative, absolute value
    specifies the percent of the whole screen. */
+int g_dpi = 0;			/* device DPI: default not set */
 int g_width = 800;
 int g_height = 600;
 int g_xpos = 0;
@@ -97,6 +98,7 @@
 RD_BOOL g_polygon_ellipse_orders = True;	/* polygon / ellipse orders */
 RD_BOOL g_fullscreen = False;
 RD_BOOL g_grab_keyboard = True;
+RD_BOOL g_local_cursor = False;
 RD_BOOL g_hide_decorations = False;
 RDP_VERSION g_rdp_version = RDP_V5;	/* Default to version 5 */
 RD_BOOL g_rdpclip = True;
@@ -190,7 +192,7 @@
 	fprintf(stderr, "   -p: password (- to prompt)\n");
 	fprintf(stderr, "   -n: client hostname\n");
 	fprintf(stderr, "   -k: keyboard layout on server (en-us, de, sv, etc.)\n");
-	fprintf(stderr, "   -g: desktop geometry (WxH)\n");
+	fprintf(stderr, "   -g: desktop geometry (WxH[@dpi])\n");
 #ifdef WITH_SCARD
 	fprintf(stderr, "   -i: enables smartcard authentication, password is used as pin\n");
 #endif
@@ -204,6 +206,7 @@
 	fprintf(stderr, "   -e: disable encryption (French TS)\n");
 	fprintf(stderr, "   -E: disable encryption from client to server\n");
 	fprintf(stderr, "   -m: do not send motion events\n");
+	fprintf(stderr, "   -M: use local mouse cursor\n");
 	fprintf(stderr, "   -C: use private colour map\n");
 	fprintf(stderr, "   -D: hide window manager decorations\n");
 	fprintf(stderr, "   -K: keep window manager key bindings\n");
@@ -579,7 +582,7 @@
 #define VNCOPT
 #endif
 	while ((c = getopt(argc, argv,
-			   VNCOPT 

Bug#839550: sofia-sip FTCBFS: uses build architecture pkg-config and thus fails finding glib

[Helmut Grohne]

Source: sofia-sip
Version: 1.12.11+20110422.1-2.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

sofia-sip fails to cross build from source, because it uses an outdated
PKG_CHECK_MODULES macro that does not prefix pkg-config with
$ac_tool_prefix. Thus it ends up using the build architecture pkg-config
which fails finding required dependencies such as glib. The attached
patch simply forces a triplet-prefixed pkg-config onto configure and
thus makes the build succeed.

Helmut
diff -u sofia-sip-1.12.11+20110422.1/debian/changelog 
sofia-sip-1.12.11+20110422.1/debian/changelog
--- sofia-sip-1.12.11+20110422.1/debian/changelog
+++ sofia-sip-1.12.11+20110422.1/debian/changelog
@@ -1,3 +1,10 @@
+sofia-sip (1.12.11+20110422.1-2.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: export a triplet-prefixed PKG_CONFIG. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 01 Oct 2016 22:54:07 +0200
+
 sofia-sip (1.12.11+20110422.1-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u sofia-sip-1.12.11+20110422.1/debian/rules 
sofia-sip-1.12.11+20110422.1/debian/rules
--- sofia-sip-1.12.11+20110422.1/debian/rules
+++ sofia-sip-1.12.11+20110422.1/debian/rules
@@ -11,6 +11,8 @@
 DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 
+export PKG_CONFIG = $(DEB_HOST_GNU_TYPE)-pkg-config
+
 ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
INSTALL_PROGRAM += -s
 endif

Bug#671847: #3879: mutt: encoded-words are not decoded in mailto:

[Mutt]

#3879: mutt: encoded-words are not decoded in mailto:
+--
  Reporter:  antonio@…  |  Owner:  mutt-dev
  Type:  defect | Status:  closed
  Priority:  major  |  Milestone:
 Component:  charset|Version:  1.7.0
Resolution:  fixed  |   Keywords:
+--
Changes (by Kevin McCarthy ):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"e0c0a2820b8b50c1e622181d4a6bbe7c1850a8ed"
 6803:e0c0a2820b8b]:
 {{{
 #!CommitTicketReference repository=""
 revision="e0c0a2820b8b50c1e622181d4a6bbe7c1850a8ed"
 RFC2047-decode mailto url headers after RFC2822 parsing. (closes #3879)

 Commit 55819a7e6169 performed the RFC2047 decode before the parsing.
 This works okay for headers such as subject, but for others such as
 address fields could lead to parsing errors.

 Change to perform a decode on envelope headers after all the calls to
 mutt_parse_rfc822_line(), using the same list of fields as
 mutt_read_rfc822_header().

 Change the do_2047 parameter of mutt_read_rfc822_line() to true, so
 that user headers are decoded if needed.
 }}}

--
Ticket URL: 
Mutt 
The Mutt mail user agent

Bug#839548: Reports "No certificate was found" on working server

[Pietro Battiston]

Package: gobby
Version: 0.5.0-8
Severity: important

Since I upgraded gobby to 0.5.0-8 (and some libraries with it), when I try to
connect to my server, it fails with the following error message: "The server
certificate is not trusted: No certificate was found.".

At the same time, in the terminal I see the following popping up:

** (gobby:31425): WARNING **: Failure during SRV record lookup: No address
associated with name
Will go on with normal A/ lookup

The server works perfectly with gobby 0.5.0 from a Windows machine, and used to
work perfectly with the previous version of the Debian package.



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

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

Versions of packages gobby depends on:
ii  dpkg1.18.3
ii  libatk1.0-0 2.18.0-1
ii  libatkmm-1.6-1v52.24.2-1
ii  libc6   2.24-3
ii  libcairo-gobject2   1.14.2-2
ii  libcairo2   1.14.2-2
ii  libcairomm-1.0-1v5  1.12.0-1
ii  libgcc1 1:5.2.1-22
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.0-1
ii  libglibmm-2.4-1v5   2.50.0-1
ii  libgnutls30 3.5.4-2
ii  libgsasl7   1.8.0-8+b1
ii  libgtk-3-0  3.22.0-1
ii  libgtkmm-3.0-1v53.22.0-1
ii  libgtksourceview-3.0-1  3.22.0-1
ii  libinfgtk3-0.6-00.6.6-1
ii  libinfinity-0.6-0   0.6.7-1+b1
ii  libpango-1.0-0  1.38.0-3
ii  libpangocairo-1.0-0 1.38.0-3
ii  libpangomm-1.4-1v5  2.40.1-3
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libstdc++6  5.2.1-22
ii  libxml++2.6-2v5 2.40.1-1
ii  libxml2 2.9.2+zdfsg1-4

gobby recommends no packages.

Versions of packages gobby suggests:
ii  avahi-daemon  0.6.31-5

-- no debconf information

Bug#839549: aisleriot: Takes an eternity to build, possibly related to network access

[Santiago Vila]

Package: src:aisleriot
Version: 3.22.0-1

Dear maintainer:

Since this version, aisleriot takes a huge amount of time to build.

Two times I tried to build this, it ended up in this way:

/usr/bin/xmllint --noout --noent --path en_GB --xinclude en_GB/westhaven.xml
/usr/bin/xmllint --noout --noent --path en_GB --xinclude en_GB/whitehead.xml
/usr/bin/xmllint --noout --noent --path en_GB --xinclude 
en_GB/will_o_the_wisp.xml
/usr/bin/xmllint --noout --noent --path en_GB --xinclude en_GB/yield.xml
/usr/bin/xmllint --noout --noent --path en_GB --xinclude en_GB/yukon.xml
/usr/bin/xmllint --noout --noent --path en_GB --xinclude en_GB/zebra.xml
/usr/bin/xmllint --noout --noent --path es --xinclude es/index.docbook
make[2]: *** wait: No child processes.  Stop.
make[2]: *** Waiting for unfinished jobs
make[2]: *** wait: No child processes.  Stop.
make[1]: *** wait: No child processes.  Stop.
make[1]: *** Waiting for unfinished jobs
make[1]: *** wait: No child processes.  Stop.
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.

Now I'm currently trying again on several autobuilders to confirm
this, but they are still working after four hours.

In the reproducible builds site I see this in the build logs:

/usr/bin/xmllint --noout --noent --path C --xinclude C/index.docbook
error : connection refused
C/legal.xml:4: warning: failed to load external entity
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd;
]>
  ^
  error : connection refused
  C/accordion.xml:4: warning: failed to load external entity
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd;
]>


which suggests this is slow because it's trying to do some kind of
network access.

I'm not using any severity here other than the default, but packages
must not need network access to build (this includes the tests).

The only exceptions are packages like debian-installer-netboot-images
which need to access to the Debian archive proper and it does not seem
easy to do so in the form of build-depends.

Thanks.

Bug#839279: ITP: gocryptfs -- Encrypted overlay filesystem written in Go

[David Steele]

On Sat, Oct 1, 2016 at 3:09 PM, Ben Hutchings  wrote:
> On Sat, 2016-10-01 at 09:03 -0400, David Steele wrote:
>> On Sat, Oct 1, 2016 at 7:58 AM, Ben Hutchings 
>> wrote:
>> >
>> > On Sat, 2016-10-01 at 02:35 +, David Steele wrote:
>> > >
>> > > Package: wnpp
>> > > Severity: wishlist
>> > > >
>> > > > Owner: David Steele 
>> > >
>> > > * Package name: gocryptfs
>> >
>> > What benefits does it provide over ecryptfs, which is already
>> > supported
>> > in Debian?
>> >
>>
>> https://nuetzlich.net/gocryptfs/comparison/
>
> OK, but it would be helpful to summarise the main advantages, like:
>
> - Includes integrity checking
> - Doesn't leak information about names of encrypted files
>

In the vs. ecryptfs case, the differences are more basic. I'd list kernel/root
vs FUSE/user, cloud sync support[1], and the availability of a user
management gui[2].

[1] https://www.cryfs.org/comparison#ecryptfs
[2] https://mhogomchungu.github.io/sirikali/

Bug#839547: gnupg: unable to decrypt file

[Paul Roge]

Package: gnupg
Version: 2.1.15-3
Severity: normal

Dear Maintainer,

After updated gnupg, I am unable to decrypt files with "gpg --decrypt 
[file].gpg". The following error is generated:

> gpg: encrypted with 2048-bit RSA key, ID 3A2B8EB7865452A1, created 2014-02-28
>   "Paul Rogé "
> gpg: public key decryption failed: Operation cancelled
> gpg: decryption failed: No secret key

I have checked that a secret key exists by "gpg --edit-key 3A2B8EB7865452A1", 
which states:

> Secret key is available.
> 
> sec  rsa2048/40E25F025E23DE01
>  created: 2014-02-28  expires: 2017-03-14  usage: SC  
>  trust: ultimate  validity: ultimate
> ssb  rsa2048/3A2B8EB7865452A1
>  created: 2014-02-28  expires: 2017-03-14  usage: E   
> [ultimate] (1). Paul Rogé 
> [ultimate] (2)  Paul Rogé 
> [ultimate] (3)  Paul Rogé 
> [ultimate] (4)  Paul Rogé 

I also ran the script "/usr/bin/migrate-pubring-from-classic-gpg --default", 
but the same problem persists.

Thanks,
Paul

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 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 gnupg depends on:
ii  gnupg-agent2.1.15-3
ii  libassuan0 2.4.3-1
ii  libbz2-1.0 1.0.6-8
ii  libc6  2.24-3
ii  libgcrypt201.7.3-1
ii  libgpg-error0  1.24-1
ii  libksba8   1.3.5-2
ii  libreadline6   6.3-8+b4
ii  libsqlite3-0   3.14.2-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages gnupg recommends:
ii  dirmngr 2.1.15-3
ii  gnupg-l10n  2.1.15-3

Versions of packages gnupg suggests:
pn  parcimonie  
pn  xloadimage  

-- no debconf information

Bug#837588: vmlinux in linux-image packages is unstripped

[Helge Deller]

Hi Ben,

On 30.09.2016 23:20, Ben Hutchings wrote:
> On Tue, 2016-09-27 at 23:09 +0200, Helge Deller wrote:
>> On 27.09.2016 21:07, Ben Hutchings wrote:
>>> On Tue, 2016-09-27 at 14:48 +0200, Helge Deller wrote:
 On 23.09.2016 05:39, Ben Hutchings wrote:
>
> I pushed a fix to the sid branch which I've tested on a powerpc
> porterbox.

 The addition of 
  dh_strip --no-automatic-dbgsym

 broke the 64bit parisc/hppa kernel build:
>>>
>>> That's strange, because it's not really an addition (we've always run
>>> dh_strip).
>>>
>>> [...]
> 
> Can you try adding -X$(IMAGE_FILE)?  

Yes, this seems to work:
-  dh_strip --no-automatic-dbgsym
+  dh_strip --no-automatic-dbgsym -X$(IMAGE_FILE)

I had to restart my test-kernel-build because of another error,
but from the logs the build didn't failed now because of this 
dh_strip line any longer. I'll have final convidence tomorrow.
So, please add "-X$(IMAGE_FILE)" for now.


> I have no idea how to access any hppa porterbox myself.

If you need access once, just let me know. 
Maybe, if we have more machines up again, I will try to make one
accessible as porterbox.

Helge

Bug#839317: [pkg-golang-devel] Bug#839317: golang-1.7: FTBFS: tests failed

[Florian Weimer]

* Lucas Nussbaum:

>> --- FAIL: TestLoadFixed (0.00s)
>>  time_test.go:943: Now().In(loc).Zone() = "-01", -3600, want
>> "GMT+1", -3600

Is this due to a tzdata change?

Bug#839189: Corruption?

[Ben Hutchings]

On Fri, 2016-09-30 at 17:26 +0100, Giuliano Procida wrote:
> I just noticed that:
> 
> #  a metadata region starting "VG_TEST {"
> 
> which should be:
> 
> #   a metadata region starting "VG_TEST {"
> 
> has appeared in the bugs web page (checked from two different
> machines).
> 
> Is this memory corruption?

That looks like a space was converted to non-breaking space, then there
has been some confusion about which character encoding was used (UTF-8
vs ISO Latin 1).  Unlikely to indicate memory corruption.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.


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

Bug#839546: apt upgrade wants to install packages that apt autoremove will remove

[Sami Liedes]

Package: apt
Version: 1.3
Severity: normal

apt upgrade lists some packages as new packages that will be
installed, but at the same time lists those packages as "automatically
installed and no longer required".


# apt upgrade --dry-run
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libastro1 libbase-java libbcmail-java libbcpkix-java 
libboost-serialization1.61.0 libboost-test1.61.0 libboost-timer1.61.0 
libehcache-java libfabric1 libflute-java libfonts-java libformula-java 
libitext-java
  libjcommon-java libkf5kipi-bin libkf5sane5 libloader-java 
libmarblewidget-qt5-24 libpixie-java libpsm-infinipath1 libqt5positioning5 
libreoffice-nlpsolver libreoffice-wiki-publisher libsac-java
  libsac-java-gcj libserializer-java libshp2 libxml-java marble-plugins
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  libastro1 libkf5kipi-bin libkf5sane5 libmarblewidget-qt5-24 
libqt5positioning5 libreoffice-nlpsolver libreoffice-wiki-publisher libshp2 
marble-plugins
The following packages have been kept back:
  digikam digikam-data digikam-private-libs gir1.2-gtk-3.0 gwenview 
kde-spectacle kipi-plugins kipi-plugins-common knode ksnapshot libboost-dbg 
libboost-dev libboost-filesystem-dev libboost-iostreams-dev
  libboost-program-options-dev libboost-regex-dev libboost-system-dev 
libboost-test-dev libboost-thread-dev libcalendarsupport4 libgail-3-0 
libgtk-3-0 libgtk-3-bin libgtk-3-dev libincidenceeditorsng4
  libjack-dev libjack0 libjack0:i386 libkdepim4 libkdepimdbusinterfaces4 
libkdgantt2-0 libkleo4 libkpgp4 libmessagecomposer4 libmessagecore4 
libmessageviewer4 libopenmpi-dev libpimcommon4 libpulse-dev
  libpulse-mainloop-glib0 libpulse0 libpulse0:i386 libpulsedsp libreoffice 
libreoffice-avmedia-backend-gstreamer libreoffice-base libreoffice-base-core 
libreoffice-base-drivers libreoffice-calc
  libreoffice-common libreoffice-core libreoffice-dev libreoffice-dev-common 
libreoffice-draw libreoffice-impress libreoffice-java-common libreoffice-math 
libreoffice-report-builder-bin libreoffice-style-galaxy
  libreoffice-style-oxygen libreoffice-style-tango libreoffice-writer 
libsendlater4 libslang2 libslang2-dev libtemplateparser4 metacity 
metacity-common openmpi-bin openmpi-common pulseaudio
  pulseaudio-esound-compat pulseaudio-utils python3-uno
0 upgraded, 9 newly installed, 0 to remove and 74 not upgraded.
Inst libastro1 (4:16.04.1-3 Debian:unstable [amd64])
Inst libkf5kipi-bin (4:16.08.0-1 Debian:unstable [amd64])
Inst libkf5sane5 (16.04.0-1 Debian:unstable [amd64])
Inst libmarblewidget-qt5-24 (4:16.04.1-3 Debian:unstable [amd64])
Inst libqt5positioning5 (5.6.1-2 Debian:unstable [amd64])
Inst libreoffice-wiki-publisher (1.2.0+LibO5.2.2~rc2-2 Debian:unstable [all])
Inst libshp2 (1.3.0-8+b1 Debian:unstable [amd64])
Inst marble-plugins (4:16.04.1-3 Debian:unstable [amd64])
Inst libreoffice-nlpsolver (0.9+LibO5.2.2~rc2-2 Debian:unstable [all])
Conf libastro1 (4:16.04.1-3 Debian:unstable [amd64])
Conf libkf5kipi-bin (4:16.08.0-1 Debian:unstable [amd64])
Conf libkf5sane5 (16.04.0-1 Debian:unstable [amd64])
Conf libmarblewidget-qt5-24 (4:16.04.1-3 Debian:unstable [amd64])
Conf libqt5positioning5 (5.6.1-2 Debian:unstable [amd64])
Conf libreoffice-wiki-publisher (1.2.0+LibO5.2.2~rc2-2 Debian:unstable [all])
Conf libshp2 (1.3.0-8+b1 Debian:unstable [amd64])
Conf marble-plugins (4:16.04.1-3 Debian:unstable [amd64])
Conf libreoffice-nlpsolver (0.9+LibO5.2.2~rc2-2 Debian:unstable [all])


Note that all of the NEW packages that will be installed are also in
the autoremoveable list (contrary to what apt says, those packages are
not yet installed).

Indeed, running apt upgrade will install these, and subsequently
running apt autoremove will remove them:


$ sudo apt autoremove
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 75 not upgraded.
$ sudo apt upgrade   
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libastro1 libbase-java libbcmail-java libbcpkix-java 
libboost-serialization1.61.0 libboost-test1.61.0 libboost-timer1.61.0 
libehcache-java libfabric1 libflute-java libfonts-java libformula-java 
libitext-java
  libjcommon-java libkf5kipi-bin libkf5sane5 libloader-java 
libmarblewidget-qt5-24 libpixie-java libpsm-infinipath1 libqt5positioning5 
libreoffice-nlpsolver libreoffice-wiki-publisher libsac-java libsac-java-gcj
  libserializer-java libshp2 libxml-java marble-plugins
Use 'sudo apt autoremove' to 

Bug#822671: initramfs-tools: preserves unmodified /etc/initramfs-tools/initramfs.conf on upgrades from jessie

[Ben Hutchings]

On Fri, 2016-09-30 at 09:57 +1000, Andrew Worsley wrote:
> Hi, I am a newbie (have a mentor account and looking to help)
> I just looked into this bug and tried to apply the patch - but it
> appears the files are missing - perhaps way out of date?
[...]

The patch applies for me with 'patch -p1'.  But I haven't yet taken the
time to try it out.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.


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

Bug#828387: libcrypt-openssl-rsa-perl: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

control: tags -1 patch

On 2016-06-26 12:22:31 [+0200], Kurt Roeckx wrote:
> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything works.

compiles, test suite passes. There is still RSA_generate_key().

> Kurt

Sebastian
>From 285baad51e3ce9609958a892d6b5246ed9dda9ce Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Sat, 1 Oct 2016 19:52:44 +
Subject: [PATCH] libcrypt-openssl-rsa-perl: get it compiled with openssl 1.1.0

Signed-off-by: Sebastian Andrzej Siewior 
---
 RSA.xs | 164 -
 1 file changed, 142 insertions(+), 22 deletions(-)

diff --git a/RSA.xs b/RSA.xs
index de512e7822d0..767ec0f8fc31 100644
--- a/RSA.xs
+++ b/RSA.xs
@@ -47,9 +47,119 @@ void croakSsl(char* p_file, int p_line)
 
 #define THROW(p_result) if (!(p_result)) { error = 1; goto err; }
 
+#if OPENSSL_VERSION_NUMBER < 0x1010
+
+static void RSA_get0_key(const RSA *r,
+ const BIGNUM **n, const BIGNUM **e, const BIGNUM **d)
+{
+if (n != NULL)
+*n = r->n;
+if (e != NULL)
+*e = r->e;
+if (d != NULL)
+*d = r->d;
+}
+
+static int RSA_set0_key(RSA *r, BIGNUM *n, BIGNUM *e, BIGNUM *d)
+{
+/* If the fields n and e in r are NULL, the corresponding input
+ * parameters MUST be non-NULL for n and e.  d may be
+ * left NULL (in case only the public key is used).
+ */
+if ((r->n == NULL && n == NULL)
+|| (r->e == NULL && e == NULL))
+return 0;
+
+if (n != NULL) {
+BN_free(r->n);
+r->n = n;
+}
+if (e != NULL) {
+BN_free(r->e);
+r->e = e;
+}
+if (d != NULL) {
+BN_free(r->d);
+r->d = d;
+}
+
+return 1;
+}
+
+static int RSA_set0_factors(RSA *r, BIGNUM *p, BIGNUM *q)
+{
+/* If the fields p and q in r are NULL, the corresponding input
+ * parameters MUST be non-NULL.
+ */
+if ((r->p == NULL && p == NULL)
+|| (r->q == NULL && q == NULL))
+return 0;
+
+if (p != NULL) {
+BN_free(r->p);
+r->p = p;
+}
+if (q != NULL) {
+BN_free(r->q);
+r->q = q;
+}
+
+return 1;
+}
+
+static void RSA_get0_factors(const RSA *r, const BIGNUM **p, const BIGNUM **q)
+{
+if (p != NULL)
+*p = r->p;
+if (q != NULL)
+*q = r->q;
+}
+
+static int RSA_set0_crt_params(RSA *r, BIGNUM *dmp1, BIGNUM *dmq1, BIGNUM *iqmp)
+{
+/* If the fields dmp1, dmq1 and iqmp in r are NULL, the corresponding input
+ * parameters MUST be non-NULL.
+ */
+if ((r->dmp1 == NULL && dmp1 == NULL)
+|| (r->dmq1 == NULL && dmq1 == NULL)
+|| (r->iqmp == NULL && iqmp == NULL))
+return 0;
+
+if (dmp1 != NULL) {
+BN_free(r->dmp1);
+r->dmp1 = dmp1;
+}
+if (dmq1 != NULL) {
+BN_free(r->dmq1);
+r->dmq1 = dmq1;
+}
+if (iqmp != NULL) {
+BN_free(r->iqmp);
+r->iqmp = iqmp;
+}
+
+return 1;
+}
+
+static void RSA_get0_crt_params(const RSA *r,
+const BIGNUM **dmp1, const BIGNUM **dmq1,
+const BIGNUM **iqmp)
+{
+if (dmp1 != NULL)
+*dmp1 = r->dmp1;
+if (dmq1 != NULL)
+*dmq1 = r->dmq1;
+if (iqmp != NULL)
+*iqmp = r->iqmp;
+}
+#endif
+
 char _is_private(rsaData* p_rsa)
 {
-return(p_rsa->rsa->d != NULL);
+const BIGNUM *d;
+
+RSA_get0_key(p_rsa->rsa, NULL, NULL, );
+return(d != NULL);
 }
 
 SV* make_rsa_obj(SV* p_proto, RSA* p_rsa)
@@ -136,7 +246,7 @@ unsigned char* get_message_digest(SV* text_SV, int hash_method)
 }
 }
 
-SV* bn2sv(BIGNUM* p_bn)
+SV* bn2sv(const BIGNUM* p_bn)
 {
 return p_bn != NULL
 ? sv_2mortal(newSViv((IV) BN_dup(p_bn)))
@@ -325,10 +435,11 @@ _new_key_from_parameters(proto, n, e, d, p, q)
 croak("At least a modulous and public key must be provided");
 }
 CHECK_OPEN_SSL(rsa = RSA_new());
-rsa->n = n;
-rsa->e = e;
+RSA_set0_key(rsa, n, e, NULL);
 if (p || q)
 {
+BIGNUM *dmp1, *dmq1, *iqmp;
+
 error = 0;
 THROW(ctx = BN_CTX_new());
 if (!p)
@@ -341,8 +452,7 @@ _new_key_from_parameters(proto, n, e, d, p, q)
 q = BN_new();
 THROW(BN_div(q, NULL, n, p, ctx));
 }
-rsa->p = p;
-rsa->q = q;
+RSA_set0_factors(rsa, p, q);
 THROW(p_minus_1 = BN_new());
 THROW(BN_sub(p_minus_1, p, BN_value_one()));
 THROW(q_minus_1 = BN_new());
@@ -353,13 +463,17 @@ _new_key_from_parameters(proto, n, e, d, p, q)
 THROW(BN_mul(d, p_minus_1, q_minus_1, ctx));
 THROW(BN_mod_inverse(d, e, d, ctx));
 }
-rsa->d = d;
-THROW(rsa->dmp1 = BN_new());
-THROW(BN_mod(rsa->dmp1, d, p_minus_1, ctx));
-

Bug#839545: debian/copyright needs update after merge of update-rc.d/invoke-rc.d/service

[Michael Biebl]

Package: init-system-helpers
Version: 1.45
Severity: important

debian/copyright currently lists Michael Stapelberg as the sole
copyright holder and the license as BSD-3-Clause.

dh_systemd_* moved to debhelper. The remaining bits from Michael S are
script/deb-systemd-* and t/.

invoke-rc.d, update-rc.d and service have a different license and
copyright holder. We should update debian/copyright accordingly.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (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 init-system-helpers depends on:
ii  perl-base  5.24.1~rc3-3

init-system-helpers recommends no packages.

init-system-helpers suggests no packages.

Versions of packages init-system-helpers is related to:
pn  insserv  

-- no debconf information

Bug#839145: dpkg-checkbuilddeps: Incorrect "Unmet build dependencies" error for Multi-Arch: foreign :native-qualified dependency

[Ben Hutchings]

Control: tag -1 moreinfo

On Fri, 2016-09-30 at 02:08 +0200, Guillem Jover wrote:
> Control: reassign -1 src:linux
> 
> On Thu, 2016-09-29 at 13:39:30 +0100, James Clarke wrote:
> > 
> > Package: libdpkg-perl
> > Version: 1.18.10
> > Control: affects -1 src:linux
> > X-Debbugs-Cc: debian-sp...@lists.debian.org
> > User: debian-sp...@lists.debian.org
> > Usertags: sparc64
> 
> > 
> > Currently, src:linux FTBFS in experimental on sparc64[1], with the error:
> > 
> > dpkg-checkbuilddeps: error: Unmet build dependencies: openssl:native
> > 
> > However, as you can see from the build log, openssl_1.1.0b-1(_sparc64) is
> > installed. This is the version from experimental, rather than the version 
> > from
> > unstable which is used on all the other buildds, since sparc64 is unable to 
> > use
> > the aspcud resolver[2], and so the apt resolver ends up pulling in more
> > experimental packages than actually needed, but if and when openssl 1.1.0 
> > hits
> > unstable, this will affect *all* architectures. This is because
> > Multi-Arch: foreign was added to openssl 1.1.0 in experimental (see 
> > #827028),
> > and it seems _find_package in /usr/share/perl5/Dpkg/Deps.pm:1472 requires
> > :native dependencies to not be Multi-Arch: foreign.
> 
> Yes (as mentioned on IRC), this is as intended and documented in
> deb-src-control(5). The rationale is that a :native build dependency on
> M-A:foreign package is non-sensical, one of the markings is wrong
> because if the interface is arch-indep then requesting the native
> should not be required.
[...]

I know it's nonsensical, but this was done as a workaround for #827028.

You seem to be saying that dpkg won't allow an M-A foreign package to
satisfy a :native dependency, even if the package is native.  Which
would mean we can't both support cross-building with openssl 1.0, and
building with openssl 1.1, from the same source package.

Please can you allow this 'nonsensical' case so that we are not forced
into a choice between two possible build regressions?

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.

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

Bug#839544: RFS: btrfs-progs/4.7.3-1~bpo8+1

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my updated "btrfs-progs" backport now
that glibc 2.24 has finally made it into testing and allowed
btrfs-progs to migrate there.

Package name: btrfs-progs
Version : 4.7.3-1~bpo8+1
Section : admin

It builds these binary packages:

 btrfs-progs - Checksumming Copy on Write Filesystem utilities
 btrfs-progs-dbg - Checksumming Copy on Write Filesystem utilities (debug)
 btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) 
(udeb)
 btrfs-tools - transitional dummy package
 btrfs-tools-dbg - transitional dummy package

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/btrfs-progs

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.7.3-1~bpo8+1.dsc

Alternatively, consult the following repo:

  git clone https://github.com/sten0/btrfs-progs.git
  git checkout debian/4.7.3-1_bpo8+1
  # or
  git checkout jessie-backports

Changes since the last upload:

btrfs-progs (4.7.3-1~bpo8+1) jessie-backports; urgency=medium

  * Rebuild for jessie-backports.

 -- Nicholas D Steeves   Sun, 25 Sep 2016 21:47:36 -0400

btrfs-progs (4.7.3-1) unstable; urgency=medium

  * New upstream release.

 -- Dimitri John Ledkov   Thu, 22 Sep 2016 14:48:05 +0100

btrfs-progs (4.7.2-1) unstable; urgency=medium

  * New upstream release. (Closes: #836778)

 -- Dimitri John Ledkov   Thu, 08 Sep 2016 12:27:38 +0100

btrfs-progs (4.7.1-1) unstable; urgency=medium

  * New upstream release.

 -- Dimitri John Ledkov   Fri, 26 Aug 2016 15:00:46 +0100

btrfs-progs (4.7-1) unstable; urgency=medium

  * New upstream release.

 -- Dimitri John Ledkov   Thu, 11 Aug 2016 12:52:07 +0100

Thank you,
Nicholas


signature.asc
Description: Digital signature

Bug#839543: pepperflashplugin-nonfree: plugin download fails with GPG error

[Alexis Bezverkhyy]

Package: pepperflashplugin-nonfree
Version: 1.8.3
Severity: important

update-pepperflashplugin-nonfree fails with the following error:

# LC_ALL=C update-pepperflashplugin-nonfree --install --verbose
options :  --install --verbose --
temporary directory: /tmp/pepperflashplugin-nonfree.5tYMb1A6YS
gpg: keybox 
'/tmp/pepperflashplugin-nonfree.5tYMb1A6YS/etc/apt/pubring.kbx' created
gpg: /tmp/pepperflashplugin-nonfree.5tYMb1A6YS/etc/apt/trustdb.gpg: 
trustdb created
gpg: key A040830F7FAC5991: public key "Google, Inc. Linux Package 
Signing Key " imported
gpg: key 7721F63BD38B4796: public key "Google Inc. (Linux Packages 
Signing Authority) " imported

gpg: Total number processed: 2
gpg:   imported: 2
gpg: no ultimately trusted keys found
doing apt-get update on google repository
WARNING: W: GPG error: http://dl.google.com/linux/chrome/deb stable 
Release: The following signatures couldn't be verified because the 
public key is not available: NO_PUBKEY A040830F7FAC5991 NO_PUBKEY 
1397BC53640DB551
W: The repository 'http://dl.google.com/linux/chrome/deb stable Release' 
is not signed.
downloading 
http://people.debian.org/~bartm/pepperflashplugin-nonfree/latest-stable-verified.txt

selected action = --install
end of action --install
cleaning up temporary directory 
/tmp/pepperflashplugin-nonfree.5tYMb1A6YS ...

end of update-pepperflashplugin-nonfree

I looked at the code and I'm puzzled with the following line:

gpg --no-permission-warning --homedir "etc/apt" --import 
/usr/lib/pepperflashplugin-nonfree/pubkey-google.txt


How it is supposed to work ? Getting GPG to import a key doesn't make 
APT trust it. So I replaced it with:


[ "$verbose" != "yes" ] || echo "adding google key to apt trust db"
stdouterr=`APT_CONFIG=apt.conf apt-key add 
/usr/lib/pepperflashplugin-nonfree/pubkey-google.txt 2>&1 || true`


and that got pepperflash to install properly, so maybe it's the fix ?

Bug#834260: freedombox-setup: Run setup script automatically when installed

[James Valleroy]

The first 2 items are fixed with plinth-0.11.0+ds-1:
- Plinth package automatically depends on packages required by essential
modules.
- The setup script run by freedombox-setup will call "plinth
--setup-no-install", which only does configuration and won't try to
install other packages.

I've opened https://github.com/gerasiov/ldapscripts/pull/2 to suggest
using ucf to manage /etc/ldapscripts/ldapscripts.conf so it won't be a
conffile.



signature.asc
Description: OpenPGP digital signature

Bug#652742: debhelper: Add dh_installzabbix script to help deploy Zabbix monitoring probes

[Niels Thykier]

Control: tags -1 moreinfo

On Tue, 20 Dec 2011 14:46:16 +0100 Roland Mas  wrote:
> Package: debhelper
> Version: 8.9.13
> Severity: wishlist
> Tags: patch
> 
> Hi,
> 
> As described in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652206,
> the Zabbix monitoring agent is now going to read bits of configuration
> from a /etc/zabbix/zabbix_agent.confd.d/ directory.  This means that any
> package providing a service that could be monitored can ship
> configuration snippets defining Zabbix probes defining new monitorable
> items, with the commands to gather the matching data.
> 
>   I suggest that the configuration snippets should be handled like
> logcheck rules or logrotate config files, and therefore that there
> should be a dh_installzabbix script; and since it's just a matter of
> shipping files, I cut and pasted from dh_installlogrotate, edited the
> relevant parts, and please find a patch attached.
> 

Hi,

Thanks for the suggestion.

I think I would like to see this script maintained outside debhelper for
a while.  If it becomes widely used, we can always merge it into
debhelper later.

This will also allow you to prototype/experimental at a much faster pace
(if needed).

Thanks,
~Niels

Bug#839542: typo: Send/Que command to all matching filters

[Mathieu Malaterre]

Package: src:ffmpeg
Version: 7:3.1.3-1
Tags: patch upstream

I do not believe this is proper english. Patch attached.
Description: Fix simple typo
Author: Mathieu Malaterre 

--- ffmpeg-3.1.3.orig/ffmpeg.c
+++ ffmpeg-3.1.3/ffmpeg.c
@@ -3551,7 +3551,7 @@ static int check_keyboard_interaction(in
 "+  increase verbosity\n"
 "-  decrease verbosity\n"
 "c  Send command to first matching filter supporting it\n"
-"C  Send/Que command to all matching filters\n"
+"C  Send/Queue command to all matching filters\n"
 "D  cycle through available debug modes\n"
 "h  dump packets/hex press to cycle through the 3 states\n"
 "q  quit\n"

Bug#839541: libgadu FTCBFS: configure check assumes broken snprintf

[Marcin Owsiany]

I will try to do this next week.

Please feel free to NMU earlier if you feel like it, so you are not blocked
on me.
However if you do, then please just pass --with-c99-vsnprintf to configure
unconditionally. No need for the extra complexity with comparing
architectures.

Bug#839279: ITP: gocryptfs -- Encrypted overlay filesystem written in Go

[Ben Hutchings]

On Sat, 2016-10-01 at 09:03 -0400, David Steele wrote:
> On Sat, Oct 1, 2016 at 7:58 AM, Ben Hutchings 
> wrote:
> > 
> > On Sat, 2016-10-01 at 02:35 +, David Steele wrote:
> > > 
> > > Package: wnpp
> > > Severity: wishlist
> > > > 
> > > > Owner: David Steele 
> > > 
> > > * Package name: gocryptfs
> > 
> > What benefits does it provide over ecryptfs, which is already
> > supported
> > in Debian?
> > 
> 
> https://nuetzlich.net/gocryptfs/comparison/

OK, but it would be helpful to summarise the main advantages, like:

- Includes integrity checking
- Doesn't leak information about names of encrypted files

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.


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

Bug#839348: astroml: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13

[Ole Streicher]

Control: reassign -1 python-sklearn 0.18-1
Control: retitle -1 python-sklearn: wrong import of "parallel"
Control: affects -1 src:astroml

This is a bug in scikit-learn, not in astroml:

$ python
Python 2.7.12+ (default, Sep  1 2016, 20:27:38) 
[GCC 6.2.0 20160822] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sklearn.mixture
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/sklearn/mixture/__init__.py", line 5, 
in 
from .gmm import sample_gaussian, log_multivariate_normal_density
  File "/usr/lib/python2.7/dist-packages/sklearn/mixture/gmm.py", line 27, in 

from .. import cluster
  File "/usr/lib/python2.7/dist-packages/sklearn/cluster/__init__.py", line 6, 
in 
from .spectral import spectral_clustering, SpectralClustering
  File "/usr/lib/python2.7/dist-packages/sklearn/cluster/spectral.py", line 16, 
in 
from ..metrics.pairwise import pairwise_kernels
  File "/usr/lib/python2.7/dist-packages/sklearn/metrics/__init__.py", line 33, 
in 
from . import cluster
  File "/usr/lib/python2.7/dist-packages/sklearn/metrics/cluster/__init__.py", 
line 20, in 
from .unsupervised import silhouette_samples
  File 
"/usr/lib/python2.7/dist-packages/sklearn/metrics/cluster/unsupervised.py", 
line 13, in 
from ..pairwise import pairwise_distances
  File "/usr/lib/python2.7/dist-packages/sklearn/metrics/pairwise.py", line 27, 
in 
from ..externals.joblib import parallel
ImportError: cannot import name parallel

It is a regression; 0.17.1-2 (in testing) works fine.

Best regards

Ole

Bug#837650: RFS: cf-python/1.3.1+dfsg.1-1 [ITP]

[Gianfranco Costamagna]

Hi Klaus,

>If I misbehaved I apologize. I tried to follow the pertinent Debian
>documentation, but that can be a challenge in itself.

it is good, just I like the "better safe than sorry" approach :)


(additional review, on top of Sebastiaan's one)
* Requires a python version from 2.6 up to, but not including, 3.0.


Sebastiaan, I'm not sure we can build Python3 version, but I leave this
check to the maintainer :p

>If it's preferable to keep the package in the GIS team, I will also be
>happy to do that. I am inexperienced in Debian politics and submit to
>your better judgment.


not needed, it is fine this way

review:
1)


./docs/source/ttt/cloud_sptheme/themes/redcloud/static/redcloud.css_t: * 
:license: BSD
./docs/source/ttt/cloud_sptheme/themes/cloud/static/jquery.cookie.js: * Dual 
licensed under the MIT and GPL licenses:
./docs/source/ttt/cloud_sptheme/themes/cloud/static/jquery.cookie.js: * 
http://www.opensource.org/licenses/mit-license.php
./docs/source/ttt/cloud_sptheme/themes/cloud/static/jquery.cookie.js: * 
http://www.gnu.org/licenses/gpl.html
./docs/source/ttt/cloud_sptheme/themes/cloud/static/cloud.js_t: * :license: BSD
./docs/source/ttt/cloud_sptheme/themes/cloud/static/cloud.css_t: * :license: BSD
./docs/source/ttt/cloud_sptheme/themes/cloud/layout.html::license: BSD


missing licenses ^^

2) grep copyright . -Ri

some missing copyrights :)

3)

something about: 
cf/um/umread/c-lib/Makefile

CC=gcc

such stuff is a no-go for my personal policy.
People might want to export CC=clang or whatever, and see it build with it.

Changing
CC=gcc
to CC?=gcc fixes this
(set if not already set)
the same applies to other stuff in that file.

$(LDFLAGS)<-- this should be at the end of the line, not at the begin, otherwise
you might see some libraries stripped just because the .o files needing them
are put after (this happens when wl-asneeded is used/default)

4) 
Depends:
libudunits2-0,

please avoid this because it means a sourceful uploads each time that package
has a soname bump.

e.g. you can avoid that by having a dependency on the -dev package,
and for runtime... don't know, you don't link it, do you?

./cf/units.py:_udunits = ctypes.CDLL('libudunits2.so.0')


probably that is the best way, at least a sourceful upload is needed
anyway, to check if the code still works.


5)
http://debomatic-amd64.debian.net/distribution#unstable/cf-python/1.3.2+dfsg.1-1/lintian

something might be addressed, something is not worth a fix
also blhc complains
http://debomatic-amd64.debian.net/distribution#unstable/cf-python/1.3.2+dfsg.1-1/blhc

6) isn't 1.3.1+dfsg1-1 a better versioning? I don't like too much that "."

I think this is all for now :)

G.

Bug#839541: libgadu FTCBFS: configure check assumes broken snprintf

[Helmut Grohne]

Source: libgadu
Version: 1:1.12.1-2
Severity: minor
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libgadu fails to cross build from source for a number of different
reasons. The first of these is that its configure assumes a broken
snprintf implementation during cross compilation and gives up. This can
be alleviated by telling it that snprintf works (which is the case for
all Debian architectures) and is what the attached patch does.

Further down the road, libgadu uses protobuf-c-compiler, which is not
ready for cross compilation. The protofbuf-c-compiler package is
implicitly Multi-Arch: no and thus installed for the host architecture,
which means that protoc-c cannot be run. Fixing this will require
changes to the protobuf-c-compiler packaging, but should not require
changes in libgadu. I didn't look for more issues yet.

So could you apply the attached patch to make the protobuf-c-compiler
issue visible during normal cross builds?

Helmut
diff --minimal -Nru libgadu-1.12.1/debian/changelog 
libgadu-1.12.1/debian/changelog
--- libgadu-1.12.1/debian/changelog 2015-08-07 22:03:01.0 +0200
+++ libgadu-1.12.1/debian/changelog 2016-10-01 20:08:34.0 +0200
@@ -1,3 +1,10 @@
+libgadu (1:1.12.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Partially fix FTCBFS: Assume working snprintf during cross. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 01 Oct 2016 20:08:18 +0200
+
 libgadu (1:1.12.1-2) unstable; urgency=medium
 
   * Upload to unstable
diff --minimal -Nru libgadu-1.12.1/debian/rules libgadu-1.12.1/debian/rules
--- libgadu-1.12.1/debian/rules 2015-08-07 22:00:50.0 +0200
+++ libgadu-1.12.1/debian/rules 2016-10-01 20:12:10.0 +0200
@@ -2,6 +2,12 @@
 # libgadu package rules file
 # Copyright 2002-2015 Marcin Owsiany 
 
+include /usr/share/dpkg/architecture.mk
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+# libgadu doesn't build without a working snprintf
+CONFIGURE_FLAGS += --with-c99-vsnprintf
+endif
+
 # Force the glibc-generated stack dump to stderr instead of /dev/tty for the
 # test suite:
 export LIBC_FATAL_STDERR_=1
@@ -19,7 +25,8 @@
--with-pthread \
--without-bind \
--without-openssl \
-   --with-gnutls
+   --with-gnutls \
+   $(CONFIGURE_FLAGS)
 # Reasons for disabling features are in README.Debian
 # Remember to update README.Debian as well...
 

Bug#628843: login: tty hijacking possible in "su" via TIOCSTI ioctl

[Simon Ruderich]

Package: login
Version: 1:4.2-3+deb8u1
Followup-For: Bug #628843

Hello,

Any news on this?

I'm deeply worried that this security issue in su was not fixed
since it was reported over 5 years ago! It still affects jessie
and sid. And the possible implications are not mentioned in the
man page.

As this breaks the use of su to change to less-privileged users,
what is the recommendation to perform this task without using su?

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x1972F726F0D556E7


signature.asc
Description: Digital signature

Bug#838396: jessie-pu: package zookeeper/3.4.5+dfsg-2

[Markus Koschany]

On 01.10.2016 19:27, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Tue, 2016-09-20 at 21:45 +0200, Markus Koschany wrote:
>> I would like to update zookeeper in Jessie which is currently affected
>> by CVE-2016-5017. The security team does not intend to release a DSA
>> for this issue.
> 
> Please go ahead.

Uploaded. Thanks.




signature.asc
Description: OpenPGP digital signature

Bug#839540: ITP: ace-link -- selecting a link to jump to

[Lev Lamberov]

Package: wnpp
Severity: wishlist
Owner: Lev Lamberov 

* Package name: ace-link
  Version : 0.4.0
  Upstream Author : Oleh Krehel 
* URL : https://github.com/abo-abo/ace-link
* License : GPL-3+
  Programming Lang: Emacs Lisp
  Description : selecting a link to jump to

This package offers an alternative to tabbing through links in buffers, for
instance, in an Info buffer. `avy' is used to turn opening a link from an
O(N) operation into an O(1).

Supported modes: `Info-mode', `help-mode', `org-mode', `eww-mode',
`gnus-article-mode', `Custom-mode', `woman-mode', `goto-address-mode'.

Bug#839538: diffoscope: json: detect order-only differences

[HW42]

Daniel Shahaf:
> It would be better to report "json files are equal up to order of
> elements in an object (= hash, dictionary, associative array)", and to
> print the difference in a more readable way than a hex dump.  (For
> example, a linewise diff of pretty-printed json.)

While at it, it should also be considered that the formating can be
different without changing the order.



signature.asc
Description: OpenPGP digital signature

Bug#784845: Pending fixes for bugs in the libdevel-gdb-perl package

[pkg-perl-maintainers]

tag 784845 + pending
thanks

Some bugs in the libdevel-gdb-perl package are closed in revision
f7f2c98f4690cd5d4ad455838a45484c3e5134b5 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdevel-gdb-perl.git/commit/?id=f7f2c98

Commit message:

Skip test t/expect.t during build and autopkgtest.

The test causes occasional, probably timing-related, failures.

Closes: #784845

Bug#839538: diffoscope: json: detect order-only differences

[Daniel Shahaf]

Control: tags -1 patch

Daniel Shahaf wrote on Sat, Oct 01, 2016 at 17:23:42 +:
> It would be better to report "json files are equal up to order of
> elements in an object (= hash, dictionary, associative array)", and to
> print the difference in a more readable way than a hex dump.  (For
> example, a linewise diff of pretty-printed json.)

Proposed patch attached.  It behaves as follows:

[[[
% head *.json
==> 1.json <==
{ "hello": 42, "world": 43 }

==> 2.json <==
{ "world": 43, "hello": 42 }
% bin/diffoscope *.json
--- 1.json
+++ 2.json
│   --- 1.json
├── +++ 2.json
│┄ ordering differences only
│ @@ -1,4 +1,4 @@
│  {
│ -"hello": 42,
│ -"world": 43
│ +"world": 43,
│ +"hello": 42
│  }
╵
]]]

It passes the existing test suite, but I haven't yet tried writing
a unit test for this.

Cheers,

Daniel

diff --git a/diffoscope/comparators/json.py b/diffoscope/comparators/json.py
index d16a762..8d0c104 100644
--- a/diffoscope/comparators/json.py
+++ b/diffoscope/comparators/json.py
@@ -17,6 +17,7 @@
 # You should have received a copy of the GNU General Public License
 # along with diffoscope.  If not, see .
 
+from collections import OrderedDict
 import re
 import json
 
@@ -34,18 +35,26 @@ class JSONFile(File):
 
 with open(file.path) as f:
 try:
-file.parsed = json.load(f)
+file.parsed = json.load(f, object_pairs_hook=OrderedDict)
 except json.JSONDecodeError:
 return False
 
 return True
 
 def compare_details(self, other, source=None):
-return [Difference.from_text(self.dumps(self), self.dumps(other),
-self.path, other.path)]
+difference = Difference.from_text(self.dumps(self), self.dumps(other),
+self.path, other.path)
+if difference:
+return [difference]
+
+difference = Difference.from_text(self.dumps(self, sort_keys=False),
+  self.dumps(other, sort_keys=False),
+  self.path, other.path,
+  comment="ordering differences only")
+return [difference]
 
 @staticmethod
-def dumps(file):
+def dumps(file, sort_keys=True):
 if not hasattr(file, 'parsed'):
 return ""
-return json.dumps(file.parsed, indent=4, sort_keys=True)
+return json.dumps(file.parsed, indent=4, sort_keys=sort_keys)

Bug#784845: libdevel-gdb-perl: autopkgtest failure in t/expect.t

[gregor herrmann]

On Sun, 25 Sep 2016 13:04:33 +0200, gregor herrmann wrote:

> Currently I'm very tempted to disable t/expect.t since it's both
> unreproducible for me and undebuggable with my amount of tuits.

Done.


Cheers,
gregor

-- 
 .''`.  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: Rolling Stones: Imagination78


signature.asc
Description: Digital Signature

Bug#839112: vim: please provide vim-legacy packages

[Ulrich Klauer]

retitle 839112 Please revert to previous default settings
thanks

I also consider this change of defaults (the "mouse=a" change, at  
least) a bug and would like to have it reverted. It is a very  
disruptive change; to me, it was a sudden "WTF?! Pasting text from  
another terminal no longer works!".


If, on the other hand, this is going to stay, users definitely need to  
be warned about this change when upgrading the package. Furthermore in  
that case, /etc/vim/vimrc needs updating. It currently says (and has  
said for years), among other things:



" The following are commented out as they cause vim to behave a lot
" differently from regular Vi. They are highly recommended though.
(...)
"set mouse=a" Enable mouse usage (all modes)


It should instead say something to the effect of mouse usage being  
enabled for all modes by default despite it being very differently  
from Vi, and how to disable it.


Ulrich

Bug#837650: RFS: cf-python/1.3.1+dfsg.1-1 [ITP]

[Sebastiaan Couwenberg]

On 10/01/2016 07:39 PM, Klaus Zimmermann wrote:
> Am 30.09.2016 um 14:46 schrieb Gianfranco Costamagna:
>> So, if you can answer the above points and ping back, I'll be happy to do a 
>> review and maybe an upload.
>
> Thanks, that would be great!

Regarding package review, please also build the module for Python 3 per
the Python Policy:

 https://www.debian.org/doc/packaging-manuals/python-policy/

Since the package uses pybuild, supporting Python 3 in addition is trivial.

>> BTW you should be member of the Team, and create a repo there if you want to 
>> maintain it
>> under that umbrella [1].
>
> I am already a member and the repository is available under the team
> facilities, i.e. the MR thing with ./checkout cf-python should work.
> In fact I already received a number of comments, particularly from
> bignose and mapreri, that improved the quality of the package (I hope),
> and of the software itself, since some of the necessary patches have
> already moved upstream.
> 
> If it's preferable to keep the package in the GIS team, I will also be
> happy to do that. I am inexperienced in Debian politics and submit to
> your better judgment.

As long as cf-python is properly maintained within the Python Modules
team I'm happy to see it there. The Debian GIS team is low on manpower,
so all packages taken care of by someone other than me is very welcome.
Many of the netcdf reverse dependencies are maintained outside of the
Debian GIS team, so having cf-python maintained elsewhere is in line
with that.

Kind Regards,

Bas

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



signature.asc
Description: OpenPGP digital signature

Bug#837761: vim: doesn't honor local admin settings in /etc/vim/vimrc.local

[James McCoy]

Control: reassign -1 vim-runtime 2:7.4.2330-1
Control: forcemerge -1 837880 837793

On Sat, Oct 01, 2016 at 02:46:33PM +0200, har...@a-little-linux-box.at wrote:
> while it's perfectly ok that upstream changed it's configuration I
> consider it a bug that this configuration can't be overriden systemwide
> - at least it seems the preferred way of creating a /etc/vim/vimrc.local
> file can't override the set mouse=a setting (currently I modified the
> /usr/share/vim/vim80/defaults.vim file but as this file will be
> overwritten when the package is upgraded I consider this a workaround,
> not a solution).

As described in defaults.vim, you can "let skip_defaults_vim = 1" to
prevent it from applying any of its settings, so just put that in
/etc/vim/vimrc.local and your settings will be preserved.

> From my prelimiary analysis it seems the problem is that
> /usr/share/vim/vim80/defaults.vim gets included multiple times

Can you show the output of ":scriptnames" to prove that?

> which it
> definitly shouldn't. As it seems only possible to override this problem
> on a per user base I would consider this definitly a bug...

It is possible to prevent it from setting anything, and then put
whatever config you want in /etc/vim/vimrc.local.  The bug, if anything,
is that I didn't add a NEWS entry describing defaults.vim and how to
disable it.

Merging with the other bugs about the same issue.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#834439: clementine: should suggest gstreamer1.0-plugins-bad

[Thomas Pierson]

On 29/09/2016 23:01, Adrian Bunk wrote:
> I understand the reasons why some people do not want to have the ALSA or 
> PulseAudio GStreamer plugins installed, and this allows them to opt out
> of installing them.
> 
> Not installing recommended packages is for "you know what you are doing" 
> situations, and I do not see a bug here.
> 
> On the input side gstreamer1.0-plugins-bad is beneficial for clementine 
> for some formats, but this is not a strict dependency.
> 
> I would strongly object to making this a dependency:

Yes, me too. And I agree that it would be a good idea to set
gstreamer1.0-plugins-bad as a suggest depend.

I note this change for the next upload.

Thanks again Adrian for your help and Salvo for the report.

Regards,

Thomas Pierson




signature.asc
Description: OpenPGP digital signature

Bug#837650: RFS: cf-python/1.3.1+dfsg.1-1 [ITP]

[Klaus Zimmermann]

Hi Gianfranco,

Am 30.09.2016 um 14:46 schrieb Gianfranco Costamagna:
>> Since the package has been moved to the Python Modules team, finding a
>> sponsor within the team is your best option. Please contact
>> debian-pyt...@lists.debian.org as documented in the Python Modules Team
>> policy:
>>
> 
> I'm member of Python Modules team, not a problem to sponsor the package, just 
> some questions:
> 
> "the netcdf package. There was an ITP for the netcdf-libcf package, but
> development of this source upstream is stalled.
> 
> cf-python depends on netcdf-python being packaged first, and will be 
> maintained
> within the Debian GIS team."
>
> this is what Ross said, where is netcdf-python package?

Bas already answered this one, just a little bit more details:
Ross original ITP was for version 0.9.9.1, which depended on the older
python binding. I packaged version 1.3.2, which depends on the more
modern netCDF4 binding, that is already available in debian as
python-netcdf4.

> I also fail to see where Ross gave you permission to work and ask for 
> sponsorhip on this package
> (this isn't an issue, but it wouldn't be the first time that somebody steals 
> a package
> to another person, so I prefer a written sentence where permission to do it 
> is granted).
I did not obtain permission from Ross previously. I sent an email to him
now, but as Bas pointed out, I took over the ticket as an RFP.
Briefly, the history was like this:
Feb. 2015: Ross reports the ITP
same day: he assigns ownership to the gis team
Aug. 2016: after 18 months without a change the ITP is turned into an
RFP by Bart Martens
Sep. 2016: I take over the RFP.

If I misbehaved I apologize. I tried to follow the pertinent Debian
documentation, but that can be a challenge in itself.

> So, if you can answer the above points and ping back, I'll be happy to do a 
> review and maybe an upload.
Thanks, that would be great!

> BTW you should be member of the Team, and create a repo there if you want to 
> maintain it
> under that umbrella [1].
I am already a member and the repository is available under the team
facilities, i.e. the MR thing with ./checkout cf-python should work.
In fact I already received a number of comments, particularly from
bignose and mapreri, that improved the quality of the package (I hope),
and of the software itself, since some of the necessary patches have
already moved upstream.

If it's preferable to keep the package in the GIS team, I will also be
happy to do that. I am inexperienced in Debian politics and submit to
your better judgment.

Thanks again!
Klaus




signature.asc
Description: OpenPGP digital signature

Bug#839539: svn2git: git-svn should be a dependency for svn2git

[Sajith T S]

Package: svn2git
Version: 2.3.2-2
Severity: normal

Without git-svn installed, svn2git gives an error message when trying
to migrate a svn repository to git.  Once git-svn is installed, svn2git
works normally.

This is what happens when git-svn is not installed:



$ svn2git svn://svn.code.sf.net/p/dustcleaner/code 
git: 'svn' is not a git command. See 'git --help'.

Did you mean this?
sync
command failed:
git svn init --prefix=svn/ --no-metadata --trunk=trunk --tags=tags 
--branches=branches svn://svn.code.sf.net/p/dustcleaner/code




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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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 svn2git depends on:
ii  ruby1:2.3.0+4
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  ruby2.2 [ruby-interpreter]  2.2.4-1

svn2git recommends no packages.

svn2git suggests no packages.

-- no debconf information

-- 
"the lyf so short, the craft so long to lerne."
 -- Chaucer.

Bug#839360: [pkg-go] Bug#839312: prometheus: FTBFS: dh_auto_build: go install -v -p 1 -ldflags -X github.com/prometheus/common/version.Version=1.1.2+ds -X github.com/prometheus/common/version.Revision

[Martín Ferrari]

On 01/10/16 10:50, Lucas Nussbaum wrote:

> Justification: FTBFS on amd64 

>> # github.com/prometheus/prometheus/web
>> src/github.com/prometheus/prometheus/web/web.go:118: not enough arguments in 
>> call to route.New

> If the failure looks somehow time/timezone related:
> Note that this rebuild was performed without the 'tzdata' package
> installed in the chroot. tzdata used be (transitively) part of
> build-essential, but it no longer is. If this package requires it to

Both these bugs are caused by the same issue: I uploaded a new version
of the common prometheus library a bit too soon, since upstream does
niot make releases for it, I did not know it was not safe..

-- 
Martín Ferrari (Tincho)

Bug#790109: Please test with sid packages if possible - DONE

[Juergen Pfennig]

Hello Bjørn

First of all: there is a work-around for gobi 1000 that works fine with newer 
kernels in jessie (we tried 4.5 from BPO) and with 4.6 in SID:

echo "blacklist qmi_wwan" > /etc/modprobe.d/fix-gobi-1000.conf

This disables the defective qmi and uses AT commands (?) instead. With newer 
kernels this works correctly (but was unstable with the original 3.16 jessie 
kernel).

Now back to qmi (tested with sid and kernel 4.6):

Does not work, same as in jessie, same log messages (wrong qmi version).

As we have a work-around and considering the age of gobi 1000 devices, I would 
suggest that you close this bug. 

Thank you very much
Jürgen

Bug#838396: jessie-pu: package zookeeper/3.4.5+dfsg-2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2016-09-20 at 21:45 +0200, Markus Koschany wrote:
> I would like to update zookeeper in Jessie which is currently affected
> by CVE-2016-5017. The security team does not intend to release a DSA
> for this issue.

Please go ahead.

Regards,

Adam

Bug#839538: diffoscope: json: detect order-only differences

[Daniel Shahaf]

Source: diffoscope
Version: 60
Severity: wishlist
Tags: upstream

Dear Maintainer,

When two json files differ only in order of elements, diffoscope falls
back to binary comparison:

[[[
% head -999 /tmp/?.json
==> /tmp/1.json <==
{
  "hello": 42,
  "world": 43
}

==> /tmp/2.json <==
{
  "world": 43,
  "hello": 42
}

% trydiffoscope $_
--- a/1.json
+++ b/2.json
│┄ No file format specific differences found inside, yet data differs
│ @@ -1,3 +1,3 @@
│ -: 7b0a 2020 2268 656c 6c6f 223a 2034 322c  {.  "hello": 42,
│ -0010: 0a20 2022 776f 726c 6422 3a20 3433 0a7d  .  "world": 43.}
│ +: 7b0a 2020 2277 6f72 6c64 223a 2034 332c  {.  "world": 43,
│ +0010: 0a20 2022 6865 6c6c 6f22 3a20 3432 0a7d  .  "hello": 42.}
│  0020: 0a   .%
]]]

It would be better to report "json files are equal up to order of
elements in an object (= hash, dictionary, associative array)", and to
print the difference in a more readable way than a hex dump.  (For
example, a linewise diff of pretty-printed json.)

Cheers,

Daniel

Bug#838780: jessie-pu: package irssi/0.8.17-1+deb8u1

[Adam D. Barratt]

Control: tags -1 -moreinfo +confirmed

On Sun, 2016-09-25 at 11:44 +0200, Rhonda D'Vine wrote:
>   Hi,
> 
> * Adam D. Barratt  [2016-09-24 21:24:18 CEST]:
> > On Sat, 2016-09-24 at 21:18 +0200, Rhonda D'Vine wrote:
> > >  The patch that upstream provides is this:
> > > https://github.com/irssi/scripts.irssi.org/commit/f1b1eb154baa684fad5d65bf4dff79c8ded8b65a
> > > 
> > >  I uploaded it to unstable already and would like to push it to stable,
> > > too.
> > 
> > That looks okay, but please could we have a source debdiff for the
> > proposed upload, as built and hopefully tested on jessie.
> 
>  I commited it locally to my git, the attached diff is
> "git diff HEAD^.." which was the commit from the security update.

Thanks. That's not actually a debdiff though - the reason we ask for a
debdiff specifically is that the build process often ends up introducing
artefacts that aren't visible from a VCS diff or patch; additionally,
maintainers sometimes make "harmless" changes before building, which we
would have likely declined if they'd been included in the submitted
diff.

Assuming that the debdiff does match the git diff supplied, please go
ahead.

Regards,

Adam