Bug#824130: ITP: libgames-support -- Useful functionality shared among GNOME games

[Jeremy Bicha]

Michael C.,

I'm sorry I wasn't subscribed to this bug and didn't see your most
recent response until this week.

I'd like to see this rename happen for GNOME 3.22 which means it would
be best if it could happen this weekend because of the impending
Freeze. By correcting this issue for 3.22, it should be relatively
easy to get the updated games in before Ubuntu 16.10 and Debian
Stretch.

I don't mind helping out but I'm not sure that my contributions will
save you much time. I can do a sed replace on the git repositories and
send you the patches but I don't currently have GNOME git commit
rights. And I expect you'd have to be the one to talk to the GNOME
System Administrators about renaming the git repo and bugzilla
project.

Thanks,
Jeremy Bicha

Bug#784565: Shipment delivery problem #00000947440

[FedEx Standard Overnight]

Dear Customer,

We could not deliver your parcel.
Please, open email attachment to print shipment label.

Thanks and best regards,
Bob Donaldson,
Support Agent.



Malware Alert Text.txt
Description: Malware Alert Text.txt

Bug#669818: mumble-server-web: package removed in 2012

[Chris Knadle]

fixed 669818 1.2.3-349-g315b5f5-2
fixed 683023 1.2.3-349-g315b5f5-2
thanks

The mumble-server-web package was removed in July 2012 by the previous
maintainer, who stated that it was unmaintained.  #676815 and #676816
were closed, but apparently #669818 and #683023 were left open and were
recently reassigned to src:mumble.  Marking the version where this was
removed and closing.

   -- Chris

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

Bug#823007: Icedove segfault and core dump

[Carsten Schoenert]

Hello Massimo,

unfortunately like the reporters before you use the wrong bug report for
your issue.  Daniel startet this report due the noisy output on the
terminal about a the pixman_region32_reset() function. Please don't
mixup various problems in one report. That makes it impossible to track
the issues for us.

On Thu, Aug 11, 2016 at 11:49:15PM +0200, Massimo Maiurana wrote:
> Well, I found some instructions and here is a backtrace from that core file
> :)
...
> (gdb) bt

Then it seems the information you found is partially wrong. We need all
threads in the log.
Please read the section on the Debian wiki with teh relevant information
about making gdb logs.

https://wiki.debian.org/Icedove#Starting_Debugging

And please append your log as an attachement (so it's not line wrapped)
to a suitable bug report.

Regards
Carsten

Bug#819158: hokey: : commitBuffer: invalid argument (invalid character)

[Clint Adams]

On Thu, Mar 24, 2016 at 09:51:01AM +, Aníbal Monsalve Salazar wrote:
> hokey dies with the error below.
> 
> hkt export-pubkeys 056E61A6F3B6C9323049DBF9565EE9641503F0AA | hokey lint
> hokey (hopenpgp-tools) 0.13
> Copyright (C) 2012-2014  Clint Adams
> hokey comes with ABSOLUTELY NO WARRANTY. This is free software, and you are 
> welcome to redistribute it under certain conditions.
> 
> Key has potential validity: good
> Key has fingerprint: 056E 61A6 F3B6 C932 3049  DBF9 565E E964 1503 F0AA
> Checking to see if key is OpenPGPv4: V4
> Checking to see if key is RSA or DSA (>= 2048-bit): RSA 4096
> Checking user-ID- and user-attribute-related items:
>   Marko Dimjahokey: : commitBuffer: invalid argument (invalid 
> character)

Sorry, I didn't see this.

Is this still reproducible with 0.19.2?  What is the output of `locale`?

Bug#820786: (no subject)

[gustavo panizzo (gfa)]

reassign -1 linux
severity -1 normal
tags -1 moreinfo

thanks

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: http://keybase.io/gfa

Bug#834115: ITP: libtest-deep-json-perl -- Test::Deep plugin for comparing JSON data

[Nick Morrott]

Package: wnpp
Owner: Nick Morrott 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libtest-deep-json-perl
  Version : 0.03
  Upstream Author : motemen 
* URL : https://metacpan.org/release/Test-Deep-JSON
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Test::Deep plugin for comparing JSON data

Test::Deep::JSON provides the sub json to indicate that the data
being tested is a JSON string. An error condition is reported if
the data cannot be parsed as valid JSON.

The package will be maintained under the umbrella of the Debian Perl Group.

Bug#810672: firmware-linux-free should include the ath9k_htc firmware binaries

[Legimet]

Since this firmware is now free software, it should be possible to use 
AR7010/AR9271 wireless adapters using only packages from main. I hope the 
firmware will be included in firmware-linux-free in time for stretch.

Bug#833752: hopenpgp-tools: cannot use GNUPGHOME env to specify gpg home directory

[Clint Adams]

On Fri, Aug 12, 2016 at 11:32:59AM +0900, Roger Shimizu wrote:
> A bit wishlist style suggestion.
> I maintain a package that I created manpages from --help output by
> using "help2man" command.
> You can take a look at it:
> - https://github.com/rogers0/libcorkipset/blob/debian/debian/rules

Thanks, this is a good start.  I wonder if there's a way to get
help2man to run --help for each of the subcommands too.

Bug#833752: hopenpgp-tools: cannot use GNUPGHOME env to specify gpg home directory

[Roger Shimizu]

On Fri, Aug 12, 2016 at 2:04 AM, Clint Adams  wrote:
> On Mon, Aug 08, 2016 at 10:02:40PM +0900, Roger Shimizu wrote:
>> I have more than one GPG keys stores in different folders.
>> Usually, I run gpg or gpg2 command by:
>>  GNUPGHOME=/path/to/gpg/home/ gpg 
>>
>> But I failed this practice by:
>>  GNUPGHOME=/path/to/gpg/home/ hkt 
>>
>> And I cannot find the param to specify GPG home directory in "hkt --help"
>>
>> Please help to explain how to use, if already implemented; or add this
>> new feature if it's not available yet.
>
> It looks like the help output for `hkt findpaths` is working but
> not for the other hkt subcommands.
>
> The way you can specify a non-default keyring is with --keyring,
> such as
>
> hkt list --keyring /usr/share/keyrings/debian-role-keys.gpg
>
> At present the only environment variable hkt cares about is HOME.
>
> I'll try to figure out what's going on with the help output.

Thanks for the fix!

A bit wishlist style suggestion.
I maintain a package that I created manpages from --help output by
using "help2man" command.
You can take a look at it:
- https://github.com/rogers0/libcorkipset/blob/debian/debian/rules

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

On Fri, Aug 12, 2016 at 2:04 AM, Clint Adams  wrote:
> On Mon, Aug 08, 2016 at 10:02:40PM +0900, Roger Shimizu wrote:
>> I have more than one GPG keys stores in different folders.
>> Usually, I run gpg or gpg2 command by:
>>  GNUPGHOME=/path/to/gpg/home/ gpg 
>>
>> But I failed this practice by:
>>  GNUPGHOME=/path/to/gpg/home/ hkt 
>>
>> And I cannot find the param to specify GPG home directory in "hkt --help"
>>
>> Please help to explain how to use, if already implemented; or add this
>> new feature if it's not available yet.
>
> It looks like the help output for `hkt findpaths` is working but
> not for the other hkt subcommands.
>
> The way you can specify a non-default keyring is with --keyring,
> such as
>
> hkt list --keyring /usr/share/keyrings/debian-role-keys.gpg
>
> At present the only environment variable hkt cares about is HOME.
>
> I'll try to figure out what's going on with the help output.



-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#722348: libc6: compile without --enable-lock-elision=no

[Fabio Andrijauskas]

Package: libc6
Version: 2.19-18+deb8u4
Followup-For: Bug #722348



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/56 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libc6 depends on:
ii  libgcc1  1:4.9.2-10

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.56
pn  glibc-doc  
ii  locales2.19-18+deb8u4

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = "en_US.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
  glibc/restart-services:
  glibc/restart-failed:
  libraries/restart-without-asking: false
  glibc/disable-screensaver:
  glibc/upgrade: true


Was necessary to recompile glibc with --enable-lock-elision=no, i believe is a 
bug on intel xeon microcode.

The backtrace from pbs_sever

#0  __lll_unlock_elision (lock=0x5100480, private=0) at 
../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#1  0x00495a0d in unlock_ji_mutex (pjob=0x5115fd0, id=0x510160 
 "svr_enquejob", 
msg=0x50eb85 "1", logging=0) at svr_jobfunc.c:4011
#2  0x0048f31e in svr_enquejob (pjob=0x5115fd0, has_sv_qs_mutex=1, 
prev_job_id=0x0, have_reservation=false, being_recovered=true)
at svr_jobfunc.c:421
#3  0x0045340a in pbsd_init_reque (pjob=0x5115fd0, change_state=0) at 
pbsd_init.c:2785
#4  0x00452de1 in pbsd_init_job (pjob=0x5115fd0, type=1) at 
pbsd_init.c:2623
#5  0x004513f9 in handle_job_recovery (type=1) at pbsd_init.c:1764
#6  0x00451f10 in handle_job_and_array_recovery (type=1) at 
pbsd_init.c:2061
#7  0x004525be in pbsd_init (type=1) at pbsd_init.c:2277
#8  0x004591ff in main (argc=2, argv=0x7fffdec8) at pbsd_main.c:1883

Bug#830765: ITA: uptimed -- utility to track high uptimes

[gustavo panizzo (gfa)]

On Mon, Aug 08, 2016 at 06:33:45PM +0200, Axel Beckert wrote:
> Hi Gustavo,
> 
> gustavo panizzo (gfa) wrote:
> > I will maintain this package from now on
> 
> Great, looking forward to it.
> 
> In case you plan to maintain uptimed's packaging in git or another
> VCS, feel free to post the link here.
I plan to use git and keep the repo in collab-maint, I'm fighting
debconf. As soon as I have something I'll push to alioth

> 
> I can also review sponsor your upload if I'm not too busy at that
> moment.

thanks for your offer

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: http://keybase.io/gfa

Bug#833979: O: pidgin-privacy-please -- plugin for enhanced privacy in pidgin

[Stefan Ott]

On Thu, Aug 11, 2016 at 11:28:08AM -0700, Francois Marier wrote:
> On Thu, 11 Aug 2016 02:13:19 +0200 Stefan Ott  wrote:
> > Since I am no longer using Debian as my primary operating system I am
> > not in a position to look after this package anymore.
> 
> Is this the new official upstream repository, now that Google Code is gone?
> 
>   https://github.com/cockroach/pidgin-privacy-please

For now it is, yes.

-- 
Stefan Ott
http://www.ott.net/

Bug#834114: libzstd: new upstream version available

[Robert Edmonds]

Package: libzstd
Version: 0.5.1-1
Severity: wishlist

Hi!

Any chance zstd could be updated to the newest upstream release? I've
pasted the NEWS entries since 0.5.1 below.

Thanks!


v0.8.0
Improved : better speed on clang and gcc -O2, thanks to Eric Biggers
New : Build on FreeBSD and DragonFly, thanks to JrMarino
Changed : modified API : ZSTD_compressEnd()
Fixed : legacy mode with ZSTD_HEAPMODE=0, by Christopher Bergqvist
Fixed : premature end of frame when zero-sized raw block, reported by Eric 
Biggers
Fixed : large dictionaries (> 384 KB), reported by Ilona Papava
Fixed : checksum correctly checked in single-pass mode
Fixed : combined --test amd --rm, reported by Andreas M. Nilsson
Modified : minor compression level adaptations
Updated : compression format specification to v0.2.0
changed : zstd.h moved to /lib directory

v0.7.4
Added : homebrew for Mac, by Daniel Cade
Added : more examples
Fixed : segfault when using small dictionaries, reported by Felix Handte
Modified : default compression level for CLI is now 3
Updated : specification, to v0.1.1

v0.7.3
New : compression format specification
New : `--` separator, stating that all following arguments are file names. 
Suggested by Chip Turner.
New : `ZSTD_getDecompressedSize()`
New : OpenBSD target, by Juan Francisco Cantero Hurtado
New : `examples` directory
fixed : dictBuilder using HC levels, reported by Bartosz Taudul
fixed : legacy support from ZSTD_decompress_usingDDict(), reported by Felix 
Handte
fixed : multi-blocks decoding with intermediate uncompressed blocks, reported 
by Greg Slazinski
modified : removed "mem.h" and "error_public.h" dependencies from "zstd.h" 
(experimental section)
modified : legacy functions no longer need magic number

v0.7.2
fixed : ZSTD_decompressBlock() using multiple consecutive blocks. Reported by 
Greg Slazinski.
fixed : potential segfault on very large files (many gigabytes). Reported by 
Chip Turner.
fixed : CLI displays system error message when destination file cannot be 
created (#231). Reported by Chip Turner.

v0.7.1
fixed : ZBUFF_compressEnd() called multiple times with too small `dst` buffer, 
reported by Christophe Chevalier
fixed : dictBuilder fails if first sample is too small, reported by Руслан 
Ковалёв
fixed : corruption issue, reported by cj
modified : checksum enabled by default in command line mode

v0.7.0
New : Support for directory compression, using `-r`, thanks to Przemyslaw 
Skibinski
New : Command `--rm`, to remove source file after successful de/compression
New : Visual build scripts, by Christophe Chevalier
New : Support for Sparse File-systems (do not use space for zero-filled sectors)
New : Frame checksum support
New : Support pass-through mode (when using `-df`)
API : more efficient Dictionary API : `ZSTD_compress_usingCDict()`, 
`ZSTD_decompress_usingDDict()`
API : create dictionary files from custom content, by Giuseppe Ottaviano
API : support for custom malloc/free functions
New : controllable Dictionary ID
New : Support for skippable frames

v0.6.1
New : zlib wrapper API, thanks to Przemyslaw Skibinski
New : Ability to compile compressor / decompressor separately
Changed : new lib directory structure
Fixed : Legacy codec v0.5 compatible with dictionary decompression
Fixed : Decoder corruption error (#173)
Fixed : null-string roundtrip (#176)
New : benchmark mode can select directory as input
Experimental : midipix support, VMS support

v0.6.0
Stronger high compression modes, thanks to Przemyslaw Skibinski
API : ZSTD_getFrameParams() provides size of decompressed content
New : highest compression modes require `--ultra` command to fully unleash 
their capacity
Fixed : zstd cli return error code > 0 and removes dst file artifact when 
decompression fails, thanks to Chip Turner


-- 
Robert Edmonds
edmo...@debian.org

Bug#833961: [PATCH] Selftests have moved into selftest sub-directory

[Jason A. Donenfeld]

---
The previous dff I sent got screwed up by line wrapping,
so here's one directly from git that should apply cleanly
into the repository.

 debian/wireguard-dkms.install | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/wireguard-dkms.install b/debian/wireguard-dkms.install
index ab9d8a4..b657b0e 100755
--- a/debian/wireguard-dkms.install
+++ b/debian/wireguard-dkms.install
@@ -1,3 +1,3 @@
 #!/usr/bin/dh-exec
-src/*.c src/*.h src/crypto/ usr/src/wireguard-${DEB_VERSION_UPSTREAM}
+src/*.c src/*.h src/selftest/ src/crypto/ 
usr/src/wireguard-${DEB_VERSION_UPSTREAM}
 src/Kbuild src/Kconfig src/Makefile src/tests/ 
usr/src/wireguard-${DEB_VERSION_UPSTREAM}
-- 
2.9.2

Bug#834003: rustc: armhf FTBFS because upstream assumes armhf has neon but debian does not

[Angus Lees]

A relevant upstream discussion[*] seems to suggest that we should be using
arm-unknown-linux-gnueabihf and not armv7-*
I think this results in armv6, which sounds preferable to armv7+neon, and I
don't think will cause any other issues (Steve?).  Other options include
creating a new combination of "armv7 without neon" using either build flags
(see [*]) or via a new armv7-debian-linux-gnueabihf triple definition.

[*] https://users.rust-lang.org/t/rust-on-armv7l-with-no-neon-support/6037

 - Gus

Bug#834113: linux-image-3.16.0-4-amd64: Logitech camera microphone does not work / makes "chipmunk" sound

[Kevin Lucas]

Package: src:linux
Version: 3.16.7-ckt25-2+deb8u3
Severity: normal
Tags: patch

Dear Maintainer,

* What led up to the situation?
Attempted to use google hangouts for audio call on a desktop machine
with Debian 8 (KDE)

* What exactly did you do (or not do) that was effective (or ineffective)?
Recorded audio from Bus 003 Device 005: ID 046d:0819 Logitech, Inc.
Webcam C210 was high-pitched and rendered my voice unintelligible.
Copied /etc/pulse/daemon.conf, /etc/pulse/default.pa to ~/.pulse
Added 'set-default-source alsa_input.usb-
046d_0819_DC70B3D0-02-U0x46d0x819.analog-mono' to ~/.pulse/default.pa to make
the webcam microphone the default.
Added 'default-sample-rate = 16000' to ~/.pulse/daemon.conf to fix
audio issue
Restarted pulseaudio with pulseaudio --kill && pulseaudio --start
Restarted Crome so that it would use the restarted pulseaudio server

   * What was the outcome of this action?
Audio sounded normal in the hangout call

   * What outcome did you expect instead?
Recorded audio from the webcam's microphone should sound normal without
the custom ~/.pulse configurations.

My hunch is this kernel is affected by the same bug as this in Ubuntu
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/843431) and this in
Fedora (https://bugzilla.redhat.com/show_bug.cgi?id=742010). Changing the
sample rate was a workaround I found in the comments to the bug on Launchpad. I
didn't try the other solution of adding 'usbcore.autosuspend=-1' to the boot
parameter.

I'm not sure if this should be filed against the pulseaudio or kernel package
so I'm filing it here.  If it should be filed there please feel free to toss
this ball to the pulseaudio maintainers.

If there's anything else you need from my side on this please don't hesitate to
ask.

Thanks for looking at this.

kev.



-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=06286bf2-3ae4-4e0b-ab9c-81268c8a752c ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[120526.311145] [UFW BLOCK] IN=wlan0 OUT= 
MAC=01:00:5e:00:00:01:64:70:02:8f:1a:d0:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 
TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[120582.633367] [UFW BLOCK] IN=wlan0 OUT= 
MAC=33:33:00:00:00:01:64:70:02:8f:1a:d0:86:dd 
SRC=fe80::::6670:02ff:fe8f:1ad0 
DST=ff02:::::::0001 LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=ICMPv6 TYPE=130 CODE=0 
[120591.235242] [UFW BLOCK] IN=wlan0 OUT= 
MAC=33:33:00:00:00:fb:0c:84:dc:a6:68:23:86:dd 
SRC=fe80::::0e84:dcff:fea6:6823 
DST=ff02:::::::00fb LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=ICMPv6 TYPE=131 CODE=0 
[120651.653497] [UFW BLOCK] IN=wlan0 OUT= 
MAC=01:00:5e:00:00:01:64:70:02:8f:1a:d0:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 
TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[120707.974732] [UFW BLOCK] IN=wlan0 OUT= 
MAC=33:33:00:00:00:01:64:70:02:8f:1a:d0:86:dd 
SRC=fe80::::6670:02ff:fe8f:1ad0 
DST=ff02:::::::0001 LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=ICMPv6 TYPE=130 CODE=0 
[120714.526837] [UFW BLOCK] IN=wlan0 OUT= 
MAC=33:33:00:00:00:fb:0c:84:dc:a6:68:23:86:dd 
SRC=fe80::::0e84:dcff:fea6:6823 
DST=ff02:::::::00fb LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=ICMPv6 TYPE=131 CODE=0 
[120777.196603] [UFW BLOCK] IN=wlan0 OUT= 
MAC=01:00:5e:00:00:01:64:70:02:8f:1a:d0:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 
TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[120833.518232] [UFW BLOCK] IN=wlan0 OUT= 
MAC=33:33:00:00:00:01:64:70:02:8f:1a:d0:86:dd 
SRC=fe80::::6670:02ff:fe8f:1ad0 
DST=ff02:::::::0001 LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=ICMPv6 TYPE=130 CODE=0 
[120840.072354] [UFW BLOCK] IN=wlan0 OUT= 
MAC=33:33:00:00:00:fb:0c:84:dc:a6:68:23:86:dd 
SRC=fe80::::0e84:dcff:fea6:6823 
DST=ff02:::::::00fb LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=ICMPv6 TYPE=131 CODE=0 
[120902.537047] [UFW BLOCK] IN=wlan0 OUT= 
MAC=01:00:5e:00:00:01:64:70:02:8f:1a:d0:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 
TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[120958.859613] [UFW BLOCK] IN=wlan0 OUT= 
MAC=33:33:00:00:00:01:64:70:02:8f:1a:d0:86:dd 
SRC=fe80::::6670:02ff:fe8f:1ad0 
DST=ff02:::::::0001 LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=ICMPv6 TYPE=130 CODE=0 
[120959.882561] [UFW BLOCK] IN=wlan0 OUT= 
MAC=33:33:00:00:00:fb:0c:84:dc:a6:68:23:86:dd 
SRC=fe80::::0e84:dcff:fea6:6823 
DST=ff02:::::::00fb LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=ICMPv6 TYPE=131 CODE=0 
[121028.082525] [UFW BLOCK] IN=wlan0 OUT= 
MAC=01:00:5e:00:00:01:64:70:02:8f:1a:d0:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 
TOS=0x00 

Bug#834083: libc-bin: essential tag

[Javier Serrano Polo]

X-Debbugs-CC: cl...@debian.org, aure...@debian.org, adcon...@0c3.net, 
sthiba...@debian.org

El dj 11 de 08 de 2016 a les 22:42 +0200, Aurelien Jarno va escriure:
> | dpkg: warning: 'ldconfig' not found in PATH or not executable.
> | dpkg: 1 expected program not found in PATH or not executable.
> | NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin.
> | E: Sub-process /usr/bin/dpkg returned an error code (2)
> 
> So it is clearly not correct to say that a squeeze or a sid system can
> work without them.

Sorry, by "system based on Squeeze" I meant a Debian derivative; it
works "with a dpkg that does not require ldconfig". The matter is
whether this ability to run without libc-bin could be merged back into
Debian. Since libc-bin is intended to be essential and the POSIX
requirement looks like a good reason, it is better not to push these
changes.


smime.p7s
Description: S/MIME cryptographic signature

Bug#804638:

[Rubin Abdi]

I too am having this issue

Debian Sid amd64
Linux lines 4.7.0-custom01 #1 SMP Sun Jul 31 12:01:59 PDT 2016 x86_64
GNU/Linux
plasma-desktop4:5.6.5-1

-- 
Rubin
ru...@starset.net

Bug#834112: icedove crashes at start

[jEsuSdA]

Package: icedove
Version: 1:45.2.0-2+b1
Severity: important

Dear Maintainer,

Last icedove update does not work at all. It crashes at start.



   * What led up to the situation?
starting icedove.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
starting icedove vía console or vía shorcut icon.


   * What was the outcome of this action?

Icedove crashes:


icedove

1470963057643   addons.xpi  WARNUnable to activate the default theme
[calBackendLoader] Using libical backend at
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components
/libical-manifest
messenger.groupdav.overlay.js: failed to include 'chrome://sogo-
connector/content/general/vcards.utils.js'
TypeError: redeclaration of let kPhotoImageCache
File: chrome://sogo-connector/content/general/vcards.utils.js
Line: 22

 Stack:

@chrome://sogo-connector/content/general/vcards.utils.js:22:5
jsInclude@chrome://sogo-
connector/content/addressbook/messenger.groupdav.overlay.js:26:13
@chrome://sogo-connector/content/addressbook/messenger.groupdav.overlay.js:37:1
Violación de segmento




Thank you for your work. ;)



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

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages icedove depends on:
ii  debianutils   4.7
ii  fontconfig2.11.0-6.4
ii  libasound21.1.0-1
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.23-4
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.8-1
ii  libdbus-glib-1-2  0.106-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-4
ii  libfontconfig12.11.0-6.4
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-9
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.1-1
ii  libgtk2.0-0   2.24.30-4
ii  libhunspell-1.4-0 1.4.1-2
ii  libicu57  57.1-2
ii  libnspr4  2:4.12-1
ii  libnss3   2:3.23-1
ii  libpango-1.0-01.40.1-1
ii  libpangocairo-1.0-0   1.40.1-1
ii  libpangoft2-1.0-0 1.40.1-1
ii  libpixman-1-0 0.33.6-1
ii  libsqlite3-0  3.13.0-1
ii  libstartup-notification0  0.12-4
ii  libstdc++66.1.1-9
ii  libvpx3   1.5.0-2
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  iceowl-extension1:45.2.0-2+b1
ii  myspell-en-us [myspell-dictionary]  1:3.3.0-4
ii  myspell-es [myspell-dictionary] 1.11-14

Versions of packages icedove suggests:
pn  apparmor  
ii  fonts-lyx 2.2.0-2
ii  libgssapi-krb5-2  1.14.2+dfsg-1

-- no debconf information

Bug#834011: linux-image-4.6.0-1-amd64: Intermittent hang on macboook pro

[Ben Hutchings]

Control: tag -1 moreinfo

On Thu, 2016-08-11 at 22:01 +1000, Erik de Castro Lopo wrote:
> Erik de Castro Lopo wrote:
> 
> I didn't notice this before:
> 
> > 
> > ** Tainted: OE (12288)
> >  * Out-of-tree module has been loaded.
> >  * Unsigned module has been loaded (currently expected).
> 
> How can I find out which module that is?

The module list in your original report shows the taint flags for each
module.

- hid_apple is the out-of-tree module.  There is also an in-tree
version, so it seems you are using a modified version.  What's the
reason for that?  Can you try using the in-tree version?

- All the modules are unsigned since you didn't install linux-4.6.0-1-
amd64-signed.

Ben.

-- 
Ben Hutchings
Humans are not rational beings; they are rationalising beings.


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

Bug#832284: [Pkg-fonts-devel] Bug#832284: closed by Hideki Yamane <henr...@debian.org> (Bug#832284: fixed in octicons 4.3.0-1)

[Tiago Ilieve]

Hideki,

On 11 August 2016 at 13:40, Hideki Yamane  wrote:
>  Q: Only needs octicons.svg as 
> /usr/share/fonts/web-fonts/octicons/octicons.svg?

Yes, for the grip package use-case this is the file I need. Maybe
other packages can benefit from the "svg" folder with multiple files,
but I can't say for sure.

Regards,
Tiago.

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Belo Horizonte - MG, Brasil

Bug#834107: Also affects metview

[Sebastiaan Couwenberg]

Hi Alastair,

metview FTBFS with the same error:

 make[3]: *** No rule to make target
 '/usr/lib/x86_64-linux-gnu/libopenjp2.so',
 needed by 'bin/Datacoverage'.  Stop.

This leads me to suspect the root cause is actually in libterralib which
is a build dependency of both.

Can you confirm my suspicion?

Kind Regards,

Bas

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

Bug#826718: Fwknop 2.6.9 packaged

[gregor herrmann]

On Wed, 10 Aug 2016 22:52:09 +0200, Franck Joncourt wrote:

> I am almost ready to push new files to debian mentor (updated package with
> QA upload + patches + lintian fixes) - I have just detected a minor problem
> with hardening flags. I hoped I could achieve this before going on holidays
> but I currently run out of time. I will continue at the end of August and I
> would be delighted if you or Gregor could sponsor the upload if you have
> time.

I'm happy to take a look once the package is ready.
If you still have access to the git repo, working there would also be
nice.
 

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: Pink Floyd: A New Machine (Part 2)


signature.asc
Description: Digital Signature

Bug#833335: namazu2-index-tools and namazu2: error when trying to install together

[NOKUBI Takatsugu]

At Thu, 11 Aug 2016 20:21:07 +0200,
Andreas Beckmann wrote:
> Hi,
> 
> the Breaks+Replaces unfortunately got into the wrong package ...
> you probably want
> 
> Package: namazu2
> Breaks: ..., namazu2-index-tools (<< 2.0.21-16)
> Replaces: ..., namazu2-index-tools (<< 2.0.21-16)
> 
> instead.

Thank you, I tested it and seems to work fine. My old packages made
to hold namazu2 package on upgrade.

Bug#796212: bittornado: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: bittornado
> Version: 0.3.18-10
> Tags: patch

There hasn't seem to be any update on this bug in 357 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#797215: getdns: incorrect call to dpkg-parsechangelog could lead to package becoming unreproducible

[Chris Lamb]

Dear Maintainer,

> Source: getdns
> Version: 0.1.6-2
> Tags: patch

There hasn't seem to be any update on this bug in 349 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#778433: p3scan: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: p3scan
> Version: 2:2.3.2-8.1
> Tags: patch

There hasn't seem to be any update on this bug in 544 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#805773: keylaunch: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: keylaunch
> Version: 1.3.6
> Tags: patch

There hasn't seem to be any update on this bug in 263 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#776933: maildirsync: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: maildirsync
> Version: 1.1-2
> Tags: patch

There hasn't seem to be any update on this bug in 555 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#776430: dictd: add --no-name flag to help reproducible builds

[Chris Lamb]

Dear Maintainer,

> Source: dictd
> Version: 1.12.1+dfsg-3
> Tags: patch

There hasn't seem to be any update on this bug in 556 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#777488: pyntor: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: pyntor
> Version: 0.6-4
> Tags: patch

There hasn't seem to be any update on this bug in 550 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#777288: bcron: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: bcron
> Version: 0.10-3
> Tags: patch

There hasn't seem to be any update on this bug in 551 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#776603: triplane: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: triplane
> Version: 1.0.8-1
> Tags: patch

There hasn't seem to be any update on this bug in 560 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#330695: [Pkg-openldap-devel] Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Ryan Tandy]

On Fri, Aug 12, 2016 at 12:08:43AM +0200, Julian Andres Klode wrote:

Hey, it's been 3 months, what's your status on this?


Oh, man. Time flies, eh? :(

Last status was this:

http://lists.alioth.debian.org/pipermail/pkg-openldap-devel/2016-June/006723.html

and it's still current.

I want to say I might be able to upload something (maybe just the 
pending RC fixes) "soon", but given I haven't found time in the past 3 
months to move anything forward at all, that seems unwise...

Bug#834111: gnunet-gtk: please make the build reproducible

[Chris Lamb]

Source: gnunet-gtk
Version: 0.10.1-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the "reproducible builds" effort [0], we noticed
that gnunet-gtk could not be built reproducibly.

Patch attached.

 [0] https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible_build.diff1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible_build.diff2016-08-12 00:13:10.569507433 
+0100
@@ -0,0 +1,19 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-12
+
+--- gnunet-gtk-0.10.1.orig/configure.ac
 gnunet-gtk-0.10.1/configure.ac
+@@ -538,7 +538,11 @@ AC_SUBST(GNUNET_PEERINFO_GTK_YEARFROM, [
+ AC_SUBST(GNUNET_STATISTICS_GTK_YEARFROM, [2010], [year of the first release])
+ AC_SUBST(GNUNET_SETUP_GTK_YEARFROM, [2010], [year of the first release])
+ 
+-thisyear=$(date | sed -e 's/.* \([[[:digit:]]]\+\)$/\1/')
++if test -n "$SOURCE_DATE_EPOCH"; then
++  thisyear=$(date --utc --date="@SOURCE_DATE_EPOCH" +%Y)
++else
++  thisyear=$(date +%Y)
++fi
+ AC_SUBST(GNUNET_FS_GTK_YEARTO, ${thisyear}, [year of the most current 
release])
+ AC_SUBST(GNUNET_PEERINFO_GTK_YEARTO, ${thisyear}, [year of the most current 
release])
+ AC_SUBST(GNUNET_STATISTICS_GTK_YEARTO, ${thisyear}, [year of the most current 
release])
--- a/debian/patches/series 2016-08-12 00:04:58.561295091 +0100
--- b/debian/patches/series 2016-08-12 00:13:09.261496277 +0100
@@ -2,3 +2,4 @@
 ac_init_version.diff
 dont_copy_license.diff
 typos.diff
+reproducible_build.diff

Bug#834110: bedtools: please make the build reproducible

[Chris Lamb]

Source: bedtools
Version: 2.26.0+dfsg-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the "reproducible builds" effort [0], we noticed
that bedtools could not be built reproducibly.

Patch attached.

 [0] https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/Makefile  2016-08-11 23:29:31.526903353 +0100
--- b/Makefile  2016-08-12 00:03:39.192612221 +0100
@@ -99,7 +99,7 @@
$(SRC_DIR)/utils/ToolBase \
$(SRC_DIR)/utils/driver
 
-BUILT_OBJECTS = $(OBJ_DIR)/*.o
+BUILT_OBJECTS = $(sort $(OBJ_DIR)/*.o)
 
 
 INCLUDES = -I$(SRC_DIR)/utils/bedFile \

Bug#775993: Please don't embed build time in /usr/share/doc/statnews/README.Debian

[Chris Lamb]

> Package: statnews
> Version: 2.5
> Tags: patch

There hasn't seem to be any update on this bug in 567 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#834109: tuxpaint: please make the build reproducible

[Chris Lamb]

Source: tuxpaint
Version: 1:0.9.22-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the "reproducible builds" effort [0], we noticed
that tuxpaint could not be built reproducibly.

Patch attached.

 [0] https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2016-08-11 23:21:14.202675808 +0100
--- b/debian/rules  2016-08-12 00:01:33.767530971 +0100
@@ -10,6 +10,8 @@
 
 export DH_ALWAYS_EXCLUDE=CVS
 
+VER_DATE = $(shell date --utc --date="$$(dpkg-parsechangelog -SDate)" 
'+%Y-%m-%d')
+
 ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
DEBUG_FLAGS += -g
 endif
@@ -31,7 +33,7 @@
 
# Add here commands to compile the package.
$(MAKE) clean
-   $(MAKE) all PREFIX=/usr DEBUG_FLAGS="$(DEBUG_FLAGS)"
+   $(MAKE) all PREFIX=/usr DEBUG_FLAGS="$(DEBUG_FLAGS)" 
VER_DATE="$(VER_DATE)"
 
touch build-arch-stamp
 

Bug#834098: libc6: name resolution fails for keys.gnupg.net on some machines / networks

[Vincent Lefevre]

On 2016-08-11 23:33:30 +0200, Vincent Lefevre wrote:
[...]
> I wondered whether this was a bug from gnupg, until I tried:
> 
> zira:~> ping keys.gnupg.net
> ping: keys.gnupg.net: Temporary failure in name resolution
> zsh: exit 2 ping keys.gnupg.net
> 
> which I always get. Ditto with telnet.
[...]

I'd add that there's no such name resolution failure under Android
(same network, same name server 192.168.0.1).

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

Bug#832593: apt-listbugs: Ctrl-C is not handled correctly

[Julian Andres Klode]

On Fri, Aug 12, 2016 at 12:40:44AM +0200, Francesco Poli wrote:
> Control: found -1 apt/1.3~rc1
> 
> 
> On Mon, 8 Aug 2016 01:05:31 +0200 Francesco Poli wrote:
> 
> [...]
> > > On Sun, Aug 07, 2016 at 12:22:47AM +0200, Francesco Poli wrote:
> [...]
> > > > [1] https://www.cons.org/cracauer/sigint.html
> [...]
> > Do I read the git diff output [2] correctly? It seems to me that the
> > modification implements the WUE approach (explained in [1]), rather
> > than the WCE approach.
> > I think that the WCE approach is really the way to go, since the hook
> > could use SIGINT for something very different from an abnormal exit.
> > Maybe, when the hook has finished its job, it exits successfully
> > without killing itself with a SIGINT. In that case, APT should *not*
> > abort the installation/upgrade!
> > 
> > [2] https://anonscm.debian.org/cgit/apt/apt.git/diff/?id=b2cfacf
> > 
> > In other words, I think that APT should wait for the child process to
> > exit (already implemented), but it should also figure out whether the
> > child process has exited on SIGINT or normally, in order to decide
> > whether it should abort or continue with the installation/upgrade.
> [...]
> > What is needed is the WCE strategy, as explained above.
> > Please implement it.
> > 
> > Thanks for your time.
> 
> Please reply to my question (quoted above).
> 
> In the meanwhile, I am reopening the bug.

Yes, sorry, I forgot to take this out of the changelog. So, basically,
AFAICT, what we should do is ignore the interrupt, because if the child
process exits with any error, we will error out as well. And if a child
exits because of a SIGINT, it's exit code won't be 0.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#832593: apt-listbugs: Ctrl-C is not handled correctly

[Francesco Poli]

Control: found -1 apt/1.3~rc1


On Mon, 8 Aug 2016 01:05:31 +0200 Francesco Poli wrote:

[...]
> > On Sun, Aug 07, 2016 at 12:22:47AM +0200, Francesco Poli wrote:
[...]
> > > [1] https://www.cons.org/cracauer/sigint.html
[...]
> Do I read the git diff output [2] correctly? It seems to me that the
> modification implements the WUE approach (explained in [1]), rather
> than the WCE approach.
> I think that the WCE approach is really the way to go, since the hook
> could use SIGINT for something very different from an abnormal exit.
> Maybe, when the hook has finished its job, it exits successfully
> without killing itself with a SIGINT. In that case, APT should *not*
> abort the installation/upgrade!
> 
> [2] https://anonscm.debian.org/cgit/apt/apt.git/diff/?id=b2cfacf
> 
> In other words, I think that APT should wait for the child process to
> exit (already implemented), but it should also figure out whether the
> child process has exited on SIGINT or normally, in order to decide
> whether it should abort or continue with the installation/upgrade.
[...]
> What is needed is the WCE strategy, as explained above.
> Please implement it.
> 
> Thanks for your time.

Please reply to my question (quoted above).

In the meanwhile, I am reopening the bug.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpw7VxCIrN3w.pgp
Description: PGP signature

Bug#833950: [Pkg-alsa-devel] Bug#833950: libasound2: brltty-espeak stops working with 1.1.2-1

[Luke Yelavich]

On Fri, Aug 12, 2016 at 08:18:15AM AEST, Samuel Thibault wrote:
> Luke Yelavich, on Fri 12 Aug 2016 08:04:56 +1000, wrote:
> > On Fri, Aug 12, 2016 at 03:40:03AM AEST, Elimar Riesebieter wrote:
> > > Control: tags +1 pending
> > > 
> > > * Sebastian Humenda  [2016-08-10 20:30 +0200]:
> > > 
> > > > Package: libasound2
> > > > Version: 1.1.2
> > > > Severity: serious
> > > > Tags: patch
> > > > Justification: breaks system for blind users [RC, stretch]
> > > > 
> > > > After an upgrade to the specified version, BRLTTY starts up with speech 
> > > > working
> > > > (brltty-espeak is using libao -> libasoun2), but speech stops working 
> > > > after
> > > > roughly a minute. The BRLTTY process is still running, but speech 
> > > > cannot be
> > > > brought back, only a restart of BRLTTY fixes this issue. All other 
> > > > playback of
> > > > sound using ALSA works fine. Since it is not related to any changes in 
> > > > BRLTTY
> > > > (tried several stable versions), the issue must be in libasound2. The 
> > > > provided
> > > > patch fixes the issue reliably for me.
> > > 
> > > Thanks for the patch.
> > > 
> > > Jordi, could you please upload?
> > 
> > Has anybody sent this upstream?
> 
> I have sent a mail to alsa-devel but it doesn't seem to have been
> moderated yet.

Ok cool, I should have assumed you would. :)

Luke

Bug#834106: apt-mirror: Uses obsolete dpkg --print-installation-architecture command

[Guillem Jover]

Package: apt-mirror
Version: 0.5.1-1
Severity: normal

Hi!

This package is using the following code:

  "defaultarch" => `dpkg --print-installation-architecture 2>/dev/null` || 
'i386'

which supresses the warning emitted by dpkg about the command being
obsolete, because it is targetted for removal. Please switch to
--print-architecture w/o suppressing error messages.

The code also defaults to i386, which seems rather arbitrary. If this
is to catter for systems w/o dpkg then maybe it's about time to change
it to amd64 perhaps?

Thanks,
Guillem

Bug#833532: icedove crashes sometimes. To crash reproducibly, install calendar-google-provider

[Leon Meier]

found 833532 icedove/1:45.2.0-2+b1
found 833532 calendar-google-provider/1:45.2.0-2
found 833532 iceowl-extension/1:45.2.0-2+b1
severity 833532 grave
thanks
--

If icedove is started with calendar-google-provider (version 
1:45.2.0-2), it always crashes during the start. If I disable the add-on 
or remove the package calendar-google-provider, icedove starts sometimes 
as usual, and sometimes crashes. It seems to me that without 
calendar-google-provider, the crash happens exactly every second time 
(but it might be a coincidence). In safe mode, no crash is observed. 
Feel free to reassign appropriately to another package if deemed necessary.


Justification for severity: calendar-google-provider is pulled in by 
default as a recommended package, making the default setup unusable.


There are a few weird messages printed to the console anyway even 
without calendar-google-provider. These messages may or may not be related:




my_user_name@my_host:~$ icedove &
[1] 6236
my_user_name@my_host:~$ [calBackendLoader] Using libical backend at 
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest


[1]+  Speicherzugriffsfehler  icedove
my_user_name@my_host:~$
my_user_name@my_host:~$
my_user_name@my_host:~$ icedove &
[1] 6309
my_user_name@my_host:~$ [calBackendLoader] Using libical backend at 
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*
A coding exception was thrown and uncaught in a Task.

Full message: TypeError: require is not a function
Full stack: 
exports.Utils.yield@resource://gre/modules/addons/XPIProvider.jsm -> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/utils.js:354:19
INIParser.prototype.process@resource://gre/modules/addons/XPIProvider.jsm 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/filterStorage.js:798:7
exports.IO.readFromFile/onProgress@resource://gre/modules/addons/XPIProvider.jsm 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/io.js:97:15
exports.IO.readFromFile/<@resource://gre/modules/addons/XPIProvider.jsm 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/io.js:182:11

TaskImpl_run@resource://gre/modules/Task.jsm:315:40
Handler.prototype.process@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:933:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:812:7
this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm 
-> resource://gre/modules/Promise-backend.js:746:1


*
*
A coding exception was thrown in a Promise rejection callback.
See 
https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise


Full message: TypeError: Cu is null
Full stack: 
exports.FilterStorage.loadFromDisk/readFile-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/filterStorage.js:380:11
exports.IO.readFromFile/onError@resource://gre/modules/addons/XPIProvider.jsm 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/io.js:149:9
Handler.prototype.process@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:936:21
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:812:7
this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm 
-> resource://gre/modules/Promise-backend.js:746:1


*

[1]+  Fertig  icedove
my_user_name@my_host:~$


Thanks in advance for 

Bug#834105: transition: libsfml

[James Cowgill]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi,

The new upstream version of libsfml bumped the SONAME and therefore
requires a transition.

These packages will need rebuilding:
 dolphin-emu
 extremetuxracer
 libcsfml
 marsshooter
 python-sfml

I did a test rebuild of all of them and they all built fine with the new
SFML.

Thanks,
James

Ben file:

title = "libsfml";
is_affected = .depends ~ /libsfml-[a-z]*2\.3v5/ | .depends ~
/libsfml-[a-z]*2\.4/;
is_good = .depends ~ /libsfml-[a-z]*2\.4/;
is_bad = .depends ~ /libsfml-[a-z]*2\.3v5/;


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

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



signature.asc
Description: OpenPGP digital signature

Bug#834104: reportbug-ng: Uses obsolete dpkg --print-installation-architecture

[Guillem Jover]

Package: reportbug-ng
Version: 2.1
Severity: normal

Hi!

This package is using the following command to get system information
«dpkg --print-installation-architecture 2>/dev/null», and quiescing
the dpkg invocation which supresses the warning mentioning that the
command is obsolete. Please switch to use the --print-architecture
command because the other is targetted for removal.

Thanks,
Guillem

Bug#833950: [Pkg-alsa-devel] Bug#833950: libasound2: brltty-espeak stops working with 1.1.2-1

[Samuel Thibault]

Luke Yelavich, on Fri 12 Aug 2016 08:04:56 +1000, wrote:
> On Fri, Aug 12, 2016 at 03:40:03AM AEST, Elimar Riesebieter wrote:
> > Control: tags +1 pending
> > 
> > * Sebastian Humenda  [2016-08-10 20:30 +0200]:
> > 
> > > Package: libasound2
> > > Version: 1.1.2
> > > Severity: serious
> > > Tags: patch
> > > Justification: breaks system for blind users [RC, stretch]
> > > 
> > > After an upgrade to the specified version, BRLTTY starts up with speech 
> > > working
> > > (brltty-espeak is using libao -> libasoun2), but speech stops working 
> > > after
> > > roughly a minute. The BRLTTY process is still running, but speech cannot 
> > > be
> > > brought back, only a restart of BRLTTY fixes this issue. All other 
> > > playback of
> > > sound using ALSA works fine. Since it is not related to any changes in 
> > > BRLTTY
> > > (tried several stable versions), the issue must be in libasound2. The 
> > > provided
> > > patch fixes the issue reliably for me.
> > 
> > Thanks for the patch.
> > 
> > Jordi, could you please upload?
> 
> Has anybody sent this upstream?

I have sent a mail to alsa-devel but it doesn't seem to have been
moderated yet.

Samuel

Bug#699219: icon: New upstream version, git, 3.0 (quilt) format

[Игорь Пашев]

Sure, http://cgit.osdyson.org/icon.git

2016-08-12 1:05 GMT+03:00 Santiago Vila :
> On Tue, 29 Jan 2013, Igor Pashev wrote:
>
>> Source: icon
>> Severity: wishlist
>>
>> Dear Maintainer,
>>
>> I've adopted icon for the 3.0 (quilt) fromat, created git repository, and
>> updated to the lastest upstream version (9.5.0):
>>
>> http://git.osdyson.org/?p=icon.git
>
> URL does not work. Do you still have the git repository somewhere?
>
> Thanks.

Bug#834103: chicken: Uses obsolete and conceptually wrong dpkg option

[Guillem Jover]

Source: chicken
Source-Version: 4.10.0-1
Severity: normal

Hi!

This package uses «dpkg --print-installation-architecture» in
debian/rules to set a BUILD_ARCH variable. Which is wrong on several
accounts. First because the option is obsolete and targetted for
removal, second because that gets the build machine, and not the host
one, which is what should be used here when deciding what to set LDFLAGS,
and third because ia64 supposedly had a broken bindnow implementation,
so that override should not even work there.

I'd suggest just getting rid of the ia64 handling and removing the
BUILD_ARCH entirely.

Thanks,
Guillem

Bug#330695: [Pkg-openldap-devel] Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Julian Andres Klode]

On Tue, May 10, 2016 at 12:50:19PM -0700, Ryan Tandy wrote:
> On Tue, May 10, 2016 at 09:21:56PM +0200, Helmut Grohne wrote:
> > Control: severity -1 serious
> > Control: tags -1 + patch
> 
> Thanks for the update and patch. I'm dropping Russ from CC because he is no
> longer actively involved in maintaining openldap. I will try to get this
> uploaded ASAP.

Hey, it's been 3 months, what's your status on this?

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#833950: [Pkg-alsa-devel] Bug#833950: libasound2: brltty-espeak stops working with 1.1.2-1

[Luke Yelavich]

On Fri, Aug 12, 2016 at 03:40:03AM AEST, Elimar Riesebieter wrote:
> Control: tags +1 pending
> 
> * Sebastian Humenda  [2016-08-10 20:30 +0200]:
> 
> > Package: libasound2
> > Version: 1.1.2
> > Severity: serious
> > Tags: patch
> > Justification: breaks system for blind users [RC, stretch]
> > 
> > After an upgrade to the specified version, BRLTTY starts up with speech 
> > working
> > (brltty-espeak is using libao -> libasoun2), but speech stops working after
> > roughly a minute. The BRLTTY process is still running, but speech cannot be
> > brought back, only a restart of BRLTTY fixes this issue. All other playback 
> > of
> > sound using ALSA works fine. Since it is not related to any changes in 
> > BRLTTY
> > (tried several stable versions), the issue must be in libasound2. The 
> > provided
> > patch fixes the issue reliably for me.
> 
> Thanks for the patch.
> 
> Jordi, could you please upload?

Has anybody sent this upstream?

Luke

Bug#834102: jcc: fix kfreebsd-* builds

[Dmitry Nezhevenko]

Package: jcc
Version: 2.21-1.1
Severity: normal
Tags: patch
Usertags: kfreebsd

Please include followed patch to build jcc for kfreebsd. I've verified that
produced jcc package is able to build pylucene.

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

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

Versions of packages jcc depends on:
ii  default-jdk [java7-sdk]2:1.8-57
ii  libc6  2.23-4
ii  libgcc11:6.1.1-11
ii  libstdc++6 6.1.1-11
ii  openjdk-8-jdk [java7-sdk]  8u102-b14.1-2
ii  python 2.7.11-2

jcc recommends no packages.

jcc suggests no packages.

-- no debconf information

-- 
WBR, Dmitry
Description: Add support for kfreebsd arches
Author: Dmitry Nezhevenko 
Last-Update: 2016-08-11

--- jcc-2.21.orig/setup.py
+++ jcc-2.21/setup.py
@@ -19,6 +19,8 @@ if machine.startswith("iPod") or machine
 platform = 'ipod'
 elif sys.platform == "win32" and "--compiler=mingw32" in sys.argv:
 platform = 'mingw32'
+elif sys.platform.startswith('gnukfreebsd'):
+platform = 'gnukfreebsd'
 else:
 platform = sys.platform.split('-')[0]
 
@@ -58,7 +60,8 @@ JDK = {
 'sunos5': '/usr/jdk/instances/jdk1.6.0',
 'win32': JAVAHOME,
 'mingw32': JAVAHOME,
-'freebsd7': '/usr/local/diablo-jdk1.6.0'
+'freebsd7': '/usr/local/diablo-jdk1.6.0',
+'gnukfreebsd': JAVAHOME,
 }
 if 'JCC_JDK' in os.environ:
 JDK[platform] = os.environ['JCC_JDK']
@@ -98,6 +101,8 @@ INCLUDES = {
 '%(mingw32)s/include/win32' %(JDK)],
 'freebsd7': ['%(freebsd7)s/include' %(JDK),
  '%(freebsd7)s/include/freebsd' %(JDK)],
+'gnukfreebsd': ['%(gnukfreebsd)s/include' %(JDK),
+ '%(gnukfreebsd)s/include/bsd' %(JDK)],
 }
 
 CFLAGS = {
@@ -109,6 +114,7 @@ CFLAGS = {
 'win32': ["/EHsc", "/D_CRT_SECURE_NO_WARNINGS"],  # MSVC 9 (2008)
 'mingw32': ['-fno-strict-aliasing', '-Wno-write-strings'],
 'freebsd7': ['-fno-strict-aliasing', '-Wno-write-strings'],
+'gnukfreebsd': ['-fno-strict-aliasing', '-Wno-write-strings'],
 }
 
 # added to CFLAGS when JCC is invoked with --debug
@@ -120,6 +126,7 @@ DEBUG_CFLAGS = {
 'win32': ['/Od', '/DDEBUG'],
 'mingw32': ['-O0', '-g', '-DDEBUG'],
 'freebsd7': ['-O0', '-g', '-DDEBUG'],
+'gnukfreebsd': ['-O0', '-g', '-DDEBUG'],
 }
 
 LFLAGS = {
@@ -175,6 +182,7 @@ JAVAC = {
 'win32': ['%(win32)s/bin/javac.exe' %(JDK)],
 'mingw32': ['%(mingw32)s/bin/javac.exe' %(JDK)],
 'freebsd7': ['javac'],
+'gnukfreebsd': ['javac'],
 }
 
 JAVADOC = {
@@ -185,6 +193,7 @@ JAVADOC = {
 'win32': ['%(win32)s/bin/javadoc.exe' %(JDK)],
 'mingw32': ['%(mingw32)s/bin/javadoc.exe' %(JDK)],
 'freebsd7': ['javadoc'],
+'gnukfreebsd': ['javadoc'],
 }
 
 try:

Bug#699219: icon: New upstream version, git, 3.0 (quilt) format

[Santiago Vila]

On Tue, 29 Jan 2013, Igor Pashev wrote:

> Source: icon
> Severity: wishlist
> 
> Dear Maintainer,
> 
> I've adopted icon for the 3.0 (quilt) fromat, created git repository, and
> updated to the lastest upstream version (9.5.0):
> 
> http://git.osdyson.org/?p=icon.git

URL does not work. Do you still have the git repository somewhere?

Thanks.

Bug#834101: firefox-esr: YouTube videos won't play with mediasouce enabled for WebM

[Lisette]

Package: firefox-esr
Version: 45.3.0esr-1~deb8u1
Severity: normal

When playing any YouTube video, it will show buffering and play maybe a frame
or two and then just sit and spin as though it needs to buffer, but it never
plays.

If I set media.mediasource.enabled to false, then it works fine

If I set media.mediasource.webm.enabled and
media.mediasource.webm.audio.enabled to false, then it works fine

Setting media.mediasource.mp4.enabled to false has no effect



-- Package-specific info:

-- Extensions information
Name: Default theme
Location: 
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: Disconnect
Location: ${PROFILE_EXTENSIONS}/2...@disconnect.me.xpi
Status: enabled

Name: Firefox Hello Beta
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled

Name: HTTPS-Everywhere
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/https-everywh...@eff.org
Package: xul-ext-https-everywhere
Status: enabled

Name: Pin It button
Location: ${PROFILE_EXTENSIONS}/jid1-ycmv6ngymqr...@jetpack.xpi
Status: enabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled

Name: Y U no validate
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{20d36f97-15da-47ed-9f0a-13cbe85bdc84}
Package: xul-ext-y-u-no-validate
Status: enabled

-- Plugins information
Name: Citrix Receiver for Linux
Location: /opt/Citrix/ICAClient/npica.so
Package: icaclient
Status: enabled

Name: MozPlugger 1.14.5 handles QuickTime and Windows Media Player Plugin 
(1.14.5)
Location: /usr/lib/mozilla/plugins/mozplugger.so
Package: mozplugger
Status: enabled


-- Addons package information
ii  firefox-esr45.3.0esr-1~ amd64Mozilla Firefox web browser - Ext
ii  icaclient  13.2.0.32224 amd64Citrix Receiver for Linux
ii  mozplugger 1.14.5-2 amd64Plugin allowing external viewers 
ii  xul-ext-https- 4.0.2-3  all  extension to force the use of HTT
ii  xul-ext-y-u-no 2013052401-2 all  browser extension to make securit

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.4+b1
iu  fontconfig2.11.0-6.3+deb8u1
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u4
ii  libcairo2 1.14.0-2.1+deb8u1
ii  libdbus-1-3   1.8.20-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.1-2+b2
iu  libfontconfig12.11.0-6.3+deb8u1
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libglib2.0-0  2.42.1-1+b1
ii  libgtk2.0-0   2.24.25-3+deb8u1
ii  libhunspell-1.3-0 1.3.3-3
ii  libpango-1.0-01.36.8-3
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-10
ii  libx11-6  2:1.6.2-3
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  procps2:3.3.9-9
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages firefox-esr recommends:
ii  gstreamer1.0-libav 1.4.4-2
ii  gstreamer1.0-plugins-good  1.4.4-2

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-2.1
pn  libgnomeui-0   
ii  libgssapi-krb5-2   1.12.1+dfsg-19+deb8u2
ii  mozplugger 1.14.5-2

-- no debconf information

Bug#834100: w3m: confusing and probably not usable denotion of input in help panel

[Markus Hiereth]

Package: w3m
Version: 0.5.3-19
Severity: normal

Dear Maintainer,

the help panel displays for some Functions ANSI Escape Codes like ^[[6~, 
^[[5~:

  +,^[[6~,C-v,SPC Move to next page (NEXT_PAGE)
  ESC-v,b,-,^[[5~ Move to previous page (PREV_PAGE)
  g,^[[1~,ESC-<   Go to the first line (BEGIN)
  ESC->,G,^[[4~   Go to the last line (END)
  ESC-TAB,^[[Z,C-uMove to previous link (PREV_LINK)
  ^[[L,^[[28~,^[[2~,^[[E  Popup menu (MENU)
  ^[[28~,^[[2~,C-cClose menu
  C-v,^[[6~,C-f   Go to next page
  C-b,^[[5~,ESC-v Go to previous page

(see 
https://en.wikipedia.org/wiki/ANSI_escape_code#Example_of_use_in_shell_scripting)

I doubt whether these codes are helpful for the normal user. In 
contrast, users with limitations would need information on how to type 
in something like ^[[6~

Therefore, either omit these codes or give an introduction in there 
usage.


-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages w3m depends on:
ii  libc62.19-18
ii  libgc1c2 1:7.2d-6.4
ii  libgpm2  1.20.4-6.1+b2
ii  libssl1.0.0  1.0.1k-3
ii  libtinfo55.9+20140913-1+b1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages w3m recommends:
ii  ca-certificates  20141019

Versions of packages w3m suggests:
pn  cmigemo   
ii  man-db2.7.0.2-5
ii  mime-support  3.58
pn  w3m-el
ii  w3m-img   0.5.3-19

-- no debconf information

Bug#834063: gosa: GOsa setup complains about missing php mysql module even if php-mysql is installed

[Wolfgang Schweer]

On Thu, Aug 11, 2016 at 07:55:21PM +0200, Andreas B. Mundt wrote:
> I tried to update the GOsa configuration in Debian-LAN and started the 
> web interface without '/etc/gosa.conf' in place.  The installation 
> check complains about missing mysql support and recommends to install 
> and activate the MySQL PHP module. However, after installing all 
> suspicious packages, for example php-mysql, the issue remains and the 
> setup process can't be continued and finished.

Hi Andreas,

looks like a misleading error message.
 
Most probably this is due to the PHP5 -> PHP 7.0 transition. As far as I 
was able to find out 'mysql_' has been deprecated as of PHP 5.5 and has 
been dropped in PHP 7.0. Apparently it has slipped our attention while 
trying to cope with the migration.

The fix might be as simple as below, but maybe it requires more 
investigation. The related file is located in /usr/share/gosa/setup/.

--- a/class_setupStep_Checks.inc2016-08-11 23:38:41.461895899 +0200
+++ b/class_setupStep_Checks.inc2016-08-11 23:37:37.0 +0200
@@ -138,7 +138,7 @@
 $N = msgPool::checkingFor(_("MySQL"));
 $D = _("GOsa requires this module to communicate with several supported 
databases.");
 $S = msgPool::installPhpModule("MySQL");
-$R = is_callable("mysql_query");
+$R = is_callable("mysqli_query");
 $M = True;
 $this->basic_checks[] = array("NAME" => $N , "DESC" => $D , "RESULT" => $R 
, "SOLUTION" => $S , "MUST" => $M );
 
Please test if this patch works.

Wolfgang


signature.asc
Description: Digital signature

Bug#823007: Icedove segfault and core dump

[Massimo Maiurana]

Well, I found some instructions and here is a backtrace from that core 
file :)


[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `icedove'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7facc2e9ada9 in raise (sig=sig@entry=11) at 
../sysdeps/unix/sysv/linux/pt-raise.c:35

35  ../sysdeps/unix/sysv/linux/pt-raise.c: File o directory non esistente.
[Current thread is 1 (Thread 0x7facc3290740 (LWP 7035))]
(gdb) bt
#0  0x7facc2e9ada9 in raise (sig=sig@entry=11) at 
../sysdeps/unix/sysv/linux/pt-raise.c:35
#1  0x7facbed74ddb in nsProfileLock::FatalSignalHandler (signo=11, 
info=0x7ffd08977370, context=0x7ffd08977240) at 
./mozilla/toolkit/profile/nsProfileLock.cpp:185
#2  0x7facbf547b59 in AsmJSFaultHandler (signum=, 
info=0x7ffd08977370, context=0x7ffd08977240)

at ./mozilla/js/src/asmjs/AsmJSSignalHandlers.cpp:1161
#3  
#4  0x7facbe8baf52 in nsTArray_base::Length (this=0x7fac9f8dbbb0) at 
../../dist/include/nsTArray.h:358
#5  mozilla::DisplayItemClip::ApplyNonRoundedIntersection 
(this=0x7fac9f8dbba0, aRect=...) at 
./mozilla/layout/base/DisplayItemClip.cpp:328
#6  0x7facbe8dc882 in nsDisplayItem::GetClippedBounds 
(this=this@entry=0x7fac7314e168, aBuilder=aBuilder@entry=0x7ffd08978178)

at ./mozilla/layout/base/nsDisplayList.cpp:2144
#7  0x7facbe8dc8f8 in nsDisplayList::GetBounds 
(this=this@entry=0x7ffd08977f58, aBuilder=aBuilder@entry=0x7ffd08978178)

at ./mozilla/layout/base/nsDisplayList.cpp:1399
#8  0x7facbe8cfc71 in 
mozilla::FrameLayerBuilder::BuildContainerLayerFor 
(this=this@entry=0x7fac662f4200, aBuilder=aBuilder@entry=0x7ffd08978178, 
aManager=
0x7fac703ba500, 
aContainerFrame=aContainerFrame@entry=0x7fac75226a50, 
aContainerItem=aContainerItem@entry=0x0, aChildren=0x7ffd08977f58, 
aParameters=...,
aTransform=0x0, aFlags=0) at 
./mozilla/layout/base/FrameLayerBuilder.cpp:5233
#9  0x7facbe9041f8 in nsDisplayList::PaintRoot 
(this=this@entry=0x7ffd08977f58, aBuilder=aBuilder@entry=0x7ffd08978178, 
aCtx=aCtx@entry=0x0,

aFlags=aFlags@entry=13) at ./mozilla/layout/base/nsDisplayList.cpp:1622
#10 0x7facbe932c08 in nsLayoutUtils::PaintFrame 
(aRenderingContext=aRenderingContext@entry=0x0, 
aFrame=aFrame@entry=0x7fac75226a50, aDirtyRegion=...,
aBackstop=aBackstop@entry=4281084715, aFlags=) at 
./mozilla/layout/base/nsLayoutUtils.cpp:3389
#11 0x7facbe937612 in PresShell::Paint (this=0x7fac74f20800, 
aViewToPaint=aViewToPaint@entry=0x7fac668ffe00, aDirtyRegion=..., 
aFlags=aFlags@entry=1)

at ./mozilla/layout/base/nsPresShell.cpp:6105
#12 0x7facbe758d20 in nsViewManager::ProcessPendingUpdatesPaint 
(this=0x7fac6f6ff880, aWidget=aWidget@entry=0x7fac8c949470) at 
./mozilla/view/nsViewManager.cpp:467
#13 0x7facbe758ed1 in nsViewManager::ProcessPendingUpdatesForView 
(this=this@entry=0x7fac6f6ff880, aView=,
aFlushDirtyRegion=aFlushDirtyRegion@entry=true) at 
./mozilla/view/nsViewManager.cpp:398
#14 0x7facbe758fa2 in nsViewManager::ProcessPendingUpdates 
(this=this@entry=0x7fac6f6ff880) at ./mozilla/view/nsViewManager.cpp:1103
#15 0x7facbe8b1afb in nsRefreshDriver::Tick 
(this=this@entry=0x7fac7314ec00, aNowEpoch=, aNowTime=...)

at ./mozilla/layout/base/nsRefreshDriver.cpp:1857
#16 0x7facbe8b22c6 in nsRefreshDriver::DoTick (this=0x7fac7314ec00) 
at ./mozilla/layout/base/nsRefreshDriver.cpp:1354
#17 0x7facbe8b23fb in nsRefreshDriver::FinishedWaitingForTransaction 
(this=0x7fac7314ec00) at ./mozilla/layout/base/nsRefreshDriver.cpp:1946
#18 0x7facbdb5dacf in 
mozilla::layers::ClientLayerManager::DidComposite 
(this=this@entry=0x7fac703ba500, aTransactionId=5096, aCompositeStart=...,
aCompositeEnd=...) at 
./mozilla/gfx/layers/client/ClientLayerManager.cpp:411
#19 0x7facbdb96007 in 
mozilla::layers::CompositorChild::RecvDidComposite (this=out>, aId=, aTransactionId=@0x7ffd08978c88: 5096,
aCompositeStart=..., aCompositeEnd=...) at 
./mozilla/gfx/layers/ipc/CompositorChild.cpp:359
#20 0x7facbd8fe41d in 
mozilla::layers::PCompositorChild::OnMessageReceived 
(this=0x7fac7d78c800, msg__=...) at 
./obj-icedove/ipc/ipdl/PCompositorChild.cpp:967
#21 0x7facbd76cbc3 in 
mozilla::ipc::MessageChannel::DispatchAsyncMessage 
(this=this@entry=0x7fac7d78c868, aMsg=...) at 
./mozilla/ipc/glue/MessageChannel.cpp:1479
#22 0x7facbd77355f in mozilla::ipc::MessageChannel::DispatchMessage 
(this=this@entry=0x7fac7d78c868, aMsg=...) at 
./mozilla/ipc/glue/MessageChannel.cpp:1414
#23 0x7facbd7741c8 in 
mozilla::ipc::MessageChannel::OnMaybeDequeueOne (this=0x7fac7d78c868) at 
./mozilla/ipc/glue/MessageChannel.cpp:1383
#24 0x7facbd759f98 in MessageLoop::RunTask (this=0x7facc1e9d840, 
task=0x7fac6ceffb70) at ./mozilla/ipc/chromium/src/base/message_loop.cc:364
#25 0x7facbd75c145 in MessageLoop::DeferOrRunPendingTask 

Bug#793214: openocd: OpenRD Ultimate unsupported since removal of ft2232 (so >=0.8.0)

[Benjamin Rodgers]

Patched and re-ran.  I can see the difference in the debug output, but the
behavior does not appear to be affected.  I've attached both a debug and
dmesg log.  This time, I've included the dmesg messages printed as a result
of running OpenOCD.


Cheers!

Benjamin Rodgers



On Wed, Aug 10, 2016 at 5:17 PM, Andreas Fritiofson <
andreas.fritiof...@gmail.com> wrote:

> Looking into it. The failure is on a really low level because the scan
> chain discovery just finds garbage. I suspect a problem with the reset
> signals because the I/O initialization seems to otherwise match the legacy
> driver. Looking at the old driver it seems the adapter has fully
> tristate-buffered reset signals even though they are not used as such. Not
> sure why that should be a problem but can you anyway try the following
> config file patch?
>
> diff --git a/tcl/interface/ftdi/sheevaplug.cfg b/tcl/interface/ftdi/
> sheevaplug.cfg
> index f299f27..5e3f369 100644
> --- a/tcl/interface/ftdi/sheevaplug.cfg
> +++ b/tcl/interface/ftdi/sheevaplug.cfg
> @@ -10,5 +10,5 @@ ftdi_vid_pid 0x9e88 0x9e8f
>  ftdi_channel 1
>
>  ftdi_layout_init 0x0608 0x0f1b
> -ftdi_layout_signal nTRST -data 0x0200
> -ftdi_layout_signal nSRST -noe 0x0400
> +ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100
> +ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400
>




>
> Nothing in dmesg when openocd starts and ttyUSB0 goes missing? I just want
> to confirm that openocd actually opens the correct interface, otherwise
> that could be the problem (talking JTAG with the serial port circuitry).
> The "ftdi_channel 1" option is not used a lot and I've never tested it
> myself. A disappearing serial port might indicate that the interface is
> actually wrong, but it could also be some quirk of
> libusb/ftdi_sio/virtualbox.
>
> Regards,
> Andreas Fritiofson
>
vagrant@jessie:~$ git -C openocd-code rev-parse HEAD
cd9b9a636411671808e8669ad8d6ee8f8815ad1b
vagrant@jessie:~$ git -C openocd-code diff
diff --git a/tcl/interface/ftdi/sheevaplug.cfg 
b/tcl/interface/ftdi/sheevaplug.cfg
index f299f27..5e3f369 100644
--- a/tcl/interface/ftdi/sheevaplug.cfg
+++ b/tcl/interface/ftdi/sheevaplug.cfg
@@ -10,5 +10,5 @@ ftdi_vid_pid 0x9e88 0x9e8f
 ftdi_channel 1
 
 ftdi_layout_init 0x0608 0x0f1b
-ftdi_layout_signal nTRST -data 0x0200
-ftdi_layout_signal nSRST -noe 0x0400
+ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400
vagrant@jessie:~$ sudo openocd -d 3 -f 
/usr/local/share/openocd/scripts/board/sheevaplug.cfg
Open On-Chip Debugger 0.10.0-dev-00335-gcd9b9a6 (2016-08-10-20:54)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
User : 13 2 command.c:544 command_print(): debug_level: 3
Debug: 14 2 options.c:96 add_default_dirs(): bindir=/usr/local/bin
Debug: 15 3 options.c:97 add_default_dirs(): pkgdatadir=/usr/local/share/openocd
Debug: 16 3 options.c:98 add_default_dirs(): run_prefix=
Debug: 17 3 configuration.c:42 add_script_search_dir(): adding /root/.openocd
Debug: 18 4 configuration.c:42 add_script_search_dir(): adding 
/usr/local/share/openocd/site
Debug: 19 4 configuration.c:42 add_script_search_dir(): adding 
/usr/local/share/openocd/scripts
Debug: 20 4 configuration.c:82 find_file(): found 
/usr/local/share/openocd/scripts/board/sheevaplug.cfg
Debug: 21 4 configuration.c:82 find_file(): found 
/usr/local/share/openocd/scripts/interface/ftdi/sheevaplug.cfg
Debug: 22 5 command.c:143 script_debug(): command - ocd_command ocd_command 
type ocd_interface ftdi
Debug: 23 5 command.c:143 script_debug(): command - interface ocd_interface ftdi
Debug: 25 5 command.c:364 register_command_handler(): registering 
'ocd_ftdi_device_desc'...
Debug: 26 5 command.c:364 register_command_handler(): registering 
'ocd_ftdi_serial'...
Debug: 27 5 command.c:364 register_command_handler(): registering 
'ocd_ftdi_location'...
Debug: 28 5 command.c:364 register_command_handler(): registering 
'ocd_ftdi_channel'...
Debug: 29 5 command.c:364 register_command_handler(): registering 
'ocd_ftdi_layout_init'...
Debug: 30 5 command.c:364 register_command_handler(): registering 
'ocd_ftdi_layout_signal'...
Debug: 31 6 command.c:364 register_command_handler(): registering 
'ocd_ftdi_set_signal'...
Debug: 32 6 command.c:364 register_command_handler(): registering 
'ocd_ftdi_vid_pid'...
Debug: 33 6 command.c:364 register_command_handler(): registering 
'ocd_ftdi_tdo_sample_edge'...
Debug: 34 6 command.c:143 script_debug(): command - ocd_command ocd_command 
type ocd_ftdi_device_desc SheevaPlug JTAGKey FT2232D B
Debug: 35 6 command.c:143 script_debug(): command - ftdi_device_desc 
ocd_ftdi_device_desc SheevaPlug JTAGKey FT2232D B
Debug: 37 6 command.c:143 script_debug(): command - ocd_command ocd_command 
type ocd_ftdi_vid_pid 0x9e88 0x9e8f
Debug: 38 6 command.c:143 script_debug(): command - ftdi_vid_pid 
ocd_ftdi_vid_pid 0x9e88 0x9e8f
Debug: 40 6 command.c:143 script_debug(): command - ocd_command ocd_command 
type 

Bug#830344: Moving forward with the Project Roadmap question

[Margarita Manterola]

El Jueves 11 Agosto 2016 21:37 CEST, Lucas Nussbaum  Ha 
escrito:
> On 11/08/16 at 20:17 +0200, Margarita Manterola wrote:
> > 2) The TC will act as an advisor to the Roadmap Team
> > 3) The TC will not be involved as body with the Roadmap Team
>
> I'm not sure about those two options.
>
> Would (2) go further than powers already available to the TC under
> §6.1? What would it mean in practice, in terms of workflows?

Of course not.
I guess the option should be rephrased as "The TC offers to be an
advisory body to the Roadmap team".
The whole idea is that if we are not the Roadmap team, then the Roadmap team
should come up with their own processes and what exactly they want from us,
but this option winning means that we would be happy to be part of the process
as a body.

> Does (3) mean that the TC waives its §6.1 powers for Roadmap issues?

No, I wouldn't state it like that.  Rather that we would not participate in the
Roadmap team regular processes, participating instead only when explicitly
asked to do so.

> Wouldn't it be better to just state that:
> 2') the TC declines to be the Roadmap team, but will of course be
> available, if necessary, under Constitution §6.1.

We will always be available.  The question here is if we want to be part
of the regular workflow, or only participate when they ask us to do so.

The whole point of my proposing the vote is to make a decision on what 
our involvement should be, not on the details of the workflow, which we
should either discuss later (should we choose to be the Roadmap team)

or let the Roadmap team come up with.

I hope that helped clarify,
Thanks,
Marga

Bug#834099: libkf5akonadicore-bin: circular dependency with libkf5akonadiwidgets5

[Bill Allombert]

Package: libkf5akonadicore-bin
Version: 4:16.04.3-1
Severity: important

Hello Debian/Kubuntu Qt/KDE Maintainers,

There is a circular dependency between libkf5akonadicore-bin and
libkf5akonadiwidgets5:

libkf5akonadicore-bin   :Depends: libkf5akonadiwidgets5 (= 4:16.04.3-1)
libkf5akonadiwidgets5   :Depends: libkf5akonadicore-bin (= 4:16.04.3-1)

Circular dependencies are known to cause problems during upgrade, so we
should try to avoid them.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#834098: libc6: name resolution fails for keys.gnupg.net on some machines / networks

[Vincent Lefevre]

Package: libc6
Version: 2.23-4
Severity: normal

I always get the folloing error on this machine:

zira:~> gpg --keyserver-options verbose,debug --keyserver hkp://keys.gnupg.net 
--recv-key 
gpg: requesting key  from hkp server keys.gnupg.net
gpgkeys: curl version = GnuPG curl-shim
* HTTP proxy is "null"
* HTTP URL is 
"http://keys.gnupg.net:11371/pks/lookup?op=get=mr=0x;
* SRV tag is "pgpkey-http": host and port may be overridden
* HTTP auth is "null"
* HTTP method is GET
?: keys.gnupg.net: Host not found
gpgkeys: HTTP fetch error 7: couldn't connect: Connection refused
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: keyserver unreachable
gpg: keyserver communications error: public key not found
gpg: keyserver receive failed: public key not found
zsh: exit 2 gpg --keyserver-options verbose,debug --keyserver 
hkp://keys.gnupg.net  

even though the host exists:

zira:~> host keys.gnupg.net
keys.gnupg.net is an alias for pool.sks-keyservers.net.
pool.sks-keyservers.net has address 5.9.50.141
pool.sks-keyservers.net has address 91.143.92.136
pool.sks-keyservers.net has address 108.18.103.116
pool.sks-keyservers.net has address 131.155.141.70
pool.sks-keyservers.net has address 85.10.205.199
pool.sks-keyservers.net has address 163.172.29.20
pool.sks-keyservers.net has address 104.236.209.43
pool.sks-keyservers.net has address 84.200.66.125
pool.sks-keyservers.net has address 5.9.143.170
pool.sks-keyservers.net has address 185.95.216.79
pool.sks-keyservers.net has IPv6 address 2607:5300:60:490f:1::19
pool.sks-keyservers.net has IPv6 address 2604:a880:800:10::227:e001
pool.sks-keyservers.net has IPv6 address 2001:41d0:2:55c2:5054:ff:fe12:3
pool.sks-keyservers.net has IPv6 address 2a01:4f8:a0:4024::2:0
pool.sks-keyservers.net has IPv6 address 2a02:180:a:65:2456:6542:1101:1010
pool.sks-keyservers.net has IPv6 address 2a01:4f8:d16:24c1::2
pool.sks-keyservers.net has IPv6 address 2a01:7c8:aabc:45a:5054:ff:fe9b:59a3
pool.sks-keyservers.net has IPv6 address 2001:470:d:367::555
pool.sks-keyservers.net has IPv6 address 2a01:4f8:161:4283:1000::203
pool.sks-keyservers.net has IPv6 address 2001:4c80:40:628:5c70:d1ff:fe44:1424

This seems to be a known issue:

  https://lists.gnupg.org/pipermail/gnupg-users/2015-October/054532.html

(searching for "keys.gnupg.net: Host not found" gives much more
examples).

I wondered whether this was a bug from gnupg, until I tried:

zira:~> ping keys.gnupg.net
ping: keys.gnupg.net: Temporary failure in name resolution
zsh: exit 2 ping keys.gnupg.net

which I always get. Ditto with telnet.

An excerpt of the strace for gnupg:

30419 stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=23, ...}) = 0
30419 socket(AF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 4
30419 connect(4, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0
30419 poll([{fd=4, events=POLLOUT}], 1, 0) = 1 ([{fd=4, revents=POLLOUT}])
30419 sendmmsg(4, {{{msg_name(0)=NULL, 
msg_iov(1)=[{"\343\376\1\0\0\1\0\0\0\0\0\0\4keys\5gnupg\3net\0\0\1\0\1", 32}], 
msg_controllen=0, msg_flags=0}, 32}, {{msg_name(0)=NULL, 
msg_iov(1)=[{"'J\1\0\0\1\0\0\0\0\0\0\4keys\5gnupg\3net\0\0\34\0\1", 32}], 
msg_controllen=0, msg_flags=0}, 32}}, 2, MSG_NOSIGNAL) = 2
30419 poll([{fd=4, events=POLLIN}], 1, 5000) = 1 ([{fd=4, revents=POLLIN}])
30419 ioctl(4, FIONREAD, [500]) = 0
30419 recvfrom(4, 
"'J\203\200\0\1\0\v\0\10\0\0\4keys\5gnupg\3net\0\0\34\0\1"..., 2048, 0, 
{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 
[16]) = 500
30419 close(4)  = 0
30419 socket(AF_INET, SOCK_STREAM, IPPROTO_IP) = 4
30419 connect(4, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = -1 ECONNREFUSED (Connection refused)
30419 close(4)  = 0
30419 socket(AF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 4
30419 connect(4, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0
30419 poll([{fd=4, events=POLLOUT}], 1, 0) = 1 ([{fd=4, revents=POLLOUT}])
30419 sendmmsg(4, {{{msg_name(0)=NULL, 
msg_iov(1)=[{"\227\30\1\0\0\1\0\0\0\0\0\0\4keys\5gnupg\3net\0\0\1\0\1", 32}], 
msg_controllen=0, 
msg_flags=MSG_RST|MSG_ERRQUEUE|MSG_NOSIGNAL|MSG_MORE|MSG_WAITFORONE|MSG_BATCH|MSG_FASTOPEN|0x8c7a},
 32}, {{msg_name(0)=NULL, 
msg_iov(1)=[{"\347\360\1\0\0\1\0\0\0\0\0\0\4keys\5gnupg\3net\0\0\34\0\1", 32}], 
msg_controllen=0, 
msg_flags=MSG_OOB|MSG_PEEK|MSG_CTRUNC|MSG_WAITALL|MSG_FIN|MSG_SYN|MSG_CONFIRM|MSG_WAITFORONE|MSG_BATCH|MSG_FASTOPEN|0x85b0},
 32}}, 2, MSG_NOSIGNAL) = 2
30419 poll([{fd=4, events=POLLIN}], 1, 5000) = 1 ([{fd=4, revents=POLLIN}])
30419 ioctl(4, FIONREAD, [500]) = 0
30419 recvfrom(4, 
"\347\360\203\200\0\1\0\v\0\10\0\0\4keys\5gnupg\3net\0\0\34\0\1"..., 2048, 0, 
{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 
[16]) = 500
30419 close(4)  = 

Bug#834097: memtest86+: Error Address conversion to MB incorrect

[Philippe Waroquiers]

Package: memtest86+
Version: 5.01-2
Severity: normal

Dear Maintainer,
I am using memtest86+ to test the memory of an old Pentium 4 PC.
memtest86+ reports errors (which I believe are real RAM errors).

However, in the error list or in the error summary, the translation
from the address into a 'MB' representation seems strange:

I have not kept track of the report with detailed memory, but I wrote down
the strange  message in error summary mode.

the output indicates (copied manually but checked several times
and I have also a photo just to be sure :).
Lowest Error Address:  00040d0fe8c - 1037.9MB
   Highest Error Address:  00040d1bedc - 1037.6MB

What is strange is that the highest error address is
'less' MB than the lowest error address : the lowest
address is shown as 1037.9, and the highest as 1037.6

I am expecting to have the highest error address be 'equal more MB'
than the lowest address.
It is also not very clear how the address is translated in MB.
E.g. this is what I obtain when I am dividing by (1024 * 1024.0)
 (gdb) p 0x00040d0fe8c / (1024 * 1024.0)
 $1 = 1037.0621452331543
 (gdb) p 0x00040d1bedc / (1024 * 1024.0)
 $2 = 1037.1090965270996
 (gdb) 
At least the nrs given by the above gdb commands are logical.

I hope I have given all the relevant info.

Thanks

Philippe

-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 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 memtest86+ depends on:
ii  debconf [debconf-2.0]  1.5.56

memtest86+ recommends no packages.

Versions of packages memtest86+ suggests:
ii  grub-pc  2.02~beta2-22+deb8u1
pn  hwtools  
pn  kernel-patch-badram  
pn  memtest86
ii  memtester4.3.0-3
pn  mtools   

-- debconf information:
  shared/memtest86-run-lilo: false

Bug#816569: mrs: FTBFS with GCC 6: was not declared in this scope

[Graham Inggs]

Hi Gert

> The fix will have to wait until libboost1.60 becomes the default and is
> build by using g++-6. In addition libzeep needs then to be fixed first
> (see blocker).

Boost 1.61 and GCC 6 are now the defaults and libzeep has been binNMU'd.
Is there anything else that needs to be done before MRS can be uploaded?

Regards
Graham

Bug#833383: ros-std-msgs: split headers and message definitions

[Jochen Sprickerhof]

* Daniele E. Domenichelli  [2016-08-11 18:57]:
> Another reason why I would like a cmake config file installed with the
> package and not a Findstd_msgs.cmake file in my projects is to be able
> to check the version... At some point, perhaps, some message might be
> added, removed, or modified, and I would like to be able to pass the
> version to find_package and be sure that the version found is compatible
> with the one I require.
> But perhaps this is something that should be fixed upstream (i.e. in
> catkin)? I'm not sure if it is still in development or if it is frozen
> though, since for ROS2 they are using a different tool.

Yes, talking to upstream about it is a good idea and judging from the
git repo it is quite active:

https://github.com/ros/catkin/commits/kinetic-devel

> From the tests I made, I couldn't find any difference, the messages are
> probably used only to produce the bindings, but they are useless for ROS
> user after.
> So perhaps "Recommends" is too much. Maybe "Suggests"? Or maybe
> nothing...

I think people doing development in ROS will use the available meta
packages and get them automatically.

> Perfect, I'll work on that as soon as possible then, but I'll be on
> holiday until Tuesday though, so it will have to wait for a few days...

No problem, enjoy your vocation. Btw. would you be interested to
regularly work on the packages? There is still a lot that needs to be
done, so we would be glad to have an other helping (and thinking ;) )
hand. You can find the current process here:

https://wiki.debian.org/DebianScience/Robotics/ROS

Cheers Jochen


signature.asc
Description: PGP signature

Bug#834095: libcwidget-dev: Bad Declaration in cwidget.pc

[Leo L. Schwab]

Package: libcwidget-dev
Version: 0.5.17-4+b1
Severity: normal

Dear Maintainer,

Upon installation of libcwidget-dev, 'pkg-config --cflags' returns
an incomplete set of options:


$ pkg-config --cflags cwidget
-I/usr/lib/x86_64-linux-gnu/cwidget -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include


Missing from this list is '-I/usr/include/cwidget', needed for any
compilation to succeed.  Looking at cwidget.pc, it appears that Cflags is
defined incorrectly, referring to ${includedir} rather than
${pkgincludedir}.  I've attached a diff/patch that fixes the problem on my
local machine.

Schwab


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

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

Versions of packages libcwidget-dev depends on:
ii  libcwidget3v5  0.5.17-4+b1
ii  libncursesw5-dev   6.0+20160625-1
ii  libsigc++-2.0-dev  2.8.0-2
ii  pkg-config 0.29-4

libcwidget-dev recommends no packages.

Versions of packages libcwidget-dev suggests:
ii  libcwidget-doc  0.5.17-4

-- no debconf information
--- cwidget.pc	2016-08-11 13:31:17.468526964 -0700
+++ cwidget-fixed.pc	2016-08-11 13:31:47.212517197 -0700
@@ -15,4 +15,4 @@
 URL: http://cwidget.alioth.debian.org
 Requires: sigc++-2.0
 Libs: -L${libdir} -lcwidget -lncursesw
-Cflags: -I${includedir} -I${pkglibdir}
+Cflags: -I${pkgincludedir} -I${pkglibdir}

Bug#834083: libc-bin: essential tag

[Aurelien Jarno]

On 2016-08-11 22:12, Javier Serrano Polo wrote:
> X-Debbugs-CC: cl...@debian.org, aure...@debian.org, adcon...@0c3.net, 
> sthiba...@debian.org
> 
> El dj 11 de 08 de 2016 a les 21:55 +0200, Aurelien Jarno va escriure:
> > On 2016-08-11 21:32, Javier Serrano Polo wrote:
> > > libc-bin is tagged essential since 2.13-10. Old systems based on Squeeze
> > > can work without libc-bin, with a dpkg that does not require ldconfig.
> > 
> > No they can't. In squeeze, the binaries from libc-bin were included in
> > libc6. The package has been split as part of the switch to multiarch.
> 
> This is not correct:
> https://archive.debian.net/squeeze/libc-bin

Indeed I was wrong. Looking at the history we had to do that in multiple
steps to be able to provide and upgrade path and have libc-bin depends on
libc6 and not the other way around.

This has been done with the following steps:
- libc6 was de facto essential (essential packages depending on it), but
  it was not possible to mark it as essential as it is a library.
- libc-bin has been split from libc6. libc6 got added a dependency on
  libc-bin. libc-bin therefore became de facto essential.
- libc-bin has been marked Essential
- libc6 dropped the dependency on libc-bin. libc-bin added a dependency
  on libc6.

As per policy permission to make libc-bin essential has been asked on
debian-devel. You'll find the mail there:

https://lists.debian.org/debian-devel/2011/07/msg6.html

> > > Could anyone explain why libc-bin is essential?
> > 
> > Because it provides binaries and configuration files essential for the
> > system: ldconfig, getent, ld.so.conf, nsswitch.conf, C.UTF-8 locale, etc.
> 
> These elements are very useful, but a system based on Squeeze can work
> without them. Is there any other reason in a Sid system?

ldconfig is definitely necessary, it is called in all postinst scripts.
If you don't have it, packages fail to configure:

| (squeeze-amd64)root@ohm:~# dpkg-reconfigure libpcre3 ; echo $?
| debconf: unable to initialize frontend: Dialog
| debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
75.)
| debconf: falling back to frontend: Readline
| /var/lib/dpkg/info/libpcre3.postinst: 6: ldconfig: not found
| 127

Further more you can't install a package:

| (squeeze-amd64)root@ohm:~# apt-get install -y dialog
| Reading package lists... Done
| Building dependency tree   
| Reading state information... Done
| The following extra packages will be installed:
|   libncursesw5
| The following NEW packages will be installed:
|   dialog libncursesw5
| 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
| Need to get 684 kB of archives.
| After this operation, 2367 kB of additional disk space will be used.
| Get:1 http://localhost/debian-archive/ squeeze/main libncursesw5 amd64 
5.7+20100313-5 [390 kB]
| Get:2 http://localhost/debian-archive/ squeeze/main dialog amd64 
1.1-20100428-1 [295 kB]
| Fetched 684 kB in 0s (63.2 MB/s)
| debconf: delaying package configuration, since apt-utils is not installed
| dpkg: warning: 'ldconfig' not found in PATH or not executable.
| dpkg: 1 expected program not found in PATH or not executable.
| NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin.
| E: Sub-process /usr/bin/dpkg returned an error code (2)

So it is clearly not correct to say that a squeeze or a sid system can
work without them. And I am sure many of the other binaries are
necessary to make the system working given what the policy says:

| Packages may assume that functionality provided by essential packages
| is always available without declaring explicit dependencies.

Some of them are even required by POSIX.

Regards,
Aurelien

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


signature.asc
Description: Digital signature

Bug#808419: starting to work on this bug and a question

[Dieter Adriaenssens]

Control: owner !

Hi,

1) Seems like a nice bug to get more familiar with several aspects of
packaging. I'll give it a go, but I'll need some time to go through some
documentation and tutorials, before starting to work on this one.

2) I assume the mariadb-server-10.0.postinst script has to take care of all
different cases :

- no previous install of mariadb, or feedback plugin wasn't enabled before
-> 50-feedback.conf should be created
- feedback plugin was enabled before, but is disabled with debconf ->
remove 50-feedback.conf file
- feedback plugin was enabled before, and is enabled with debconf -> do
nothing (or delete and recreate the 50-feedback.conf file just to be sure)

-- 
Kind regards,

Dieter Adriaenssens

Bug#831184: mumble: FTBFS with GCC 6, seems Ice related

[Chris Knadle]

tags 831184 + patch pending
thanks

Attached are two patches (thanks to Mikkel Krautz for finding the
solution and for the c++11 patch) both which fix the build.  Unless
there's an objection I'm going to use the patch to build with c++03
because that's what Mumble upstream tests Mumble with.

Thanks
  -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us
Description: Fix FTBFS bug with GCC 6
  Mumble expcets -std=c++03 but doesn't explicitly set this in order to allow
  the compiler to choose, and g++-6 defaults to -std=gnu++14.  zeroc-ice ships
  both c++03 and c++11 libs, and the c++03 libs are the default.  The
  combination leads to c++11 linking errors unless the -std is explicity set.
  Additionally the location of the c++11 libs differs depending on whether
  the architecture is 32-bit or 64-bit, so this needs to be specified as well.
Author: Mikkel Krautz 
Bugs-Debian: https://bugs.debian.org/831184
Bugs-Mumble: https://github.com/mumble-voip/mumble/issues/2494
Last-Updated: 2016-08-11

--- a/compiler.pri
+++ b/compiler.pri
@@ -89,6 +89,14 @@
 	QMAKE_LFLAGS   *= $(shell dpkg-buildflags --get LDFLAGS)
 	QMAKE_CFLAGS *= -Wfatal-errors -fvisibility=hidden
 	QMAKE_CXXFLAGS *= -Wfatal-errors -fvisibility=hidden
+	QMAKE_CXXFLAGS *= -std=c++11
+
+	# ZeroC Ice's C++11 libs are in /usr/lib/$triple/c++11 on Debian.
+	MULTIARCH_TRIPLE = $$system($${QMAKE_CXX} -print-multiarch)
+	!isEmpty(MULTIARCH_TRIPLE) {
+		QMAKE_LIBDIR *= /usr/lib/$${MULTIARCH_TRIPLE}/c++11
+	}
+
 	!CONFIG(quiet-build-log) {
 		QMAKE_CFLAGS *= -Wshadow -Wconversion -Wsign-compare
 		QMAKE_CXXFLAGS *= -Wshadow -Woverloaded-virtual -Wold-style-cast -Wconversion -Wsign-compare
Description: Fix FTBFS bug with GCC 6
  Mumble expcets -std=c++03 but doesn't explicitly set this in order to allow
  the compiler to choose, and g++-6 defaults to -std=gnu++14.  zeroc-ice ships
  both c++03 and c++11 libs, and the c++03 libs are the default.  The
  combination leads to c++11 linking errors unless the -std is explicity set.
Author: Mikkel Krautz 
Bugs-Debian: https://bugs.debian.org/831184
Bugs-Mumble: https://github.com/mumble-voip/mumble/issues/2494
Last-Updated: 2016-08-11

--- a/compiler.pri
+++ b/compiler.pri
@@ -89,6 +89,8 @@
 	QMAKE_LFLAGS   *= $(shell dpkg-buildflags --get LDFLAGS)
 	QMAKE_CFLAGS *= -Wfatal-errors -fvisibility=hidden
 	QMAKE_CXXFLAGS *= -Wfatal-errors -fvisibility=hidden
+	QMAKE_CXXFLAGS *= -std=c++03
+
 	!CONFIG(quiet-build-log) {
 		QMAKE_CFLAGS *= -Wshadow -Wconversion -Wsign-compare
 		QMAKE_CXXFLAGS *= -Wshadow -Woverloaded-virtual -Wold-style-cast -Wconversion -Wsign-compare


signature.asc
Description: OpenPGP digital signature

Bug#834094: xserver-xorg-input-evdev: Aiptek tablet driver includes function key area into the pointer area

[Tobias Schlemmer]

Package: xserver-xorg-input-evdev
Version: 1:2.10.2-1
Severity: normal

I have a Trust tablet attached to my PC. It works well with xserver-xorg-input-
aiptek, but usage is problematic with xserver-xorg-input-evdev:
The pad as a row of „function keys“ (drawn rechtangles with „F1“ …
„F12“ written on them) at the top of the pen area. This area creates
simultaneously keyboard and pointer events. A correct implementation would
assign this area either to the keyboard (default) or to the pointer device
(user configurable). The calibration data should be altered depending on the
configuration, so that in either configuration the whole screen can be reached
by the pointer and no place is wasted unnecessarily.

I'm talking about:
~$ lsusb
…
Bus 003 Device 011: ID 08ca:0021 Aiptek International, Inc. APT-2 Tablet
…



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Feb  4  2012 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Jul 20 05:00 /usr/bin/Xorg

Diversions concerning libGL are in place

diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 
by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so 
by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by 

Bug#834024: mutt: "double free or corruption" when closing a compressed mbox

[Alberto Garcia]

On Thu, Aug 11, 2016 at 05:09:48PM +0100, Richard Russon wrote:

> I saw a lot of version info, but not that of mutt/neomutt.

Sorry, I removed it from my bug report because it was crashing
reportbug (#822463).

Anyway...

> mutt -v | head -n 1
> 
> Known broken:
> Mutt 1.6.2-neo (2016-07-23)

That's the one that I have.

> Latest version:
> Mutt 1.6.2-neo (2016-08-08)

Has that one been packaged for Debian? The latest mutt in Debian is
1.6.2-1, and that's the one that I have.

Berto

Bug#830344: Moving forward with the Project Roadmap question

[Sam Hartman]

I think that calling for that vote would be fine.
I view that as an informalish internal vote, not some formal resolution
that we're going to announce on d-d-a.
Mostly I think we're going to try and figure out the direction at a high
level.
For options 1, 2, 4, and possibly 3, I think we'll need significantly
more discussion before voting on  something formalish.
If we choose option 1 or 2, we may find that during the process of
fleshing something out, we flip-flop back and forth.

So, I think that you've done a great job of getting the level of
specificity that we need now.

Bug#722348: libc6: pbs_server generating general protection

[Fabio Andrijauskas]

Package: libc6
Version: 2.19-18+deb8u4
Followup-For: Bug #722348



-- System Information:
Debian Release: 8.5
  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/56 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: systemd (via /run/systemd/system)

Versions of packages libc6 depends on:
ii  libgcc1  1:4.9.2-10

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.56
pn  glibc-doc  
ii  locales2.19-18+deb8u4

-- debconf information:
  glibc/restart-services:
  libraries/restart-without-asking: false
  glibc/disable-screensaver:
  glibc/upgrade: true
  glibc/restart-failed:


 I am trying to install torque 6.0.2 on Debian 8.5 on a Intel Xeon E5-2620v4. 
However, when i try start pbs_server i returned a segment fault, with gdb:

#1  0x00440ab6 in container::item_container::unlock 
(this=0xb5d900 ) at ../../src/include/container.hpp:537
#2  0x004b787f in mom_hierarchy_handler::nextNode (this=0x4e610c0 
, iter=0x7fff98b8) at mom_hierarchy_handler.cpp:122
#3  0x004b7a7d in mom_hierarchy_handler::make_default_hierarchy 
(this=0x4e610c0 ) at mom_hierarchy_handler.cpp:149
#4  0x004b898d in mom_hierarchy_handler::loadHierarchy (this=0x4e610c0 
) at mom_hierarchy_handler.cpp:433
#5  0x004b8ae8 in mom_hierarchy_handler::initialLoadHierarchy 
(this=0x4e610c0 ) at mom_hierarchy_handler.cpp:472
#6  0x0045262a in pbsd_init (type=1) at pbsd_init.c:2299
#7  0x004591ff in main (argc=2, argv=0x7fffdec8) at pbsd_main.c:1883

dmesg:

 traps: pbs_server[22249] general protection ip:7f9c08a7a2c8 sp:7ffe520b5238 
error:0 in libpthread-2.19.so[7f9c08a69000+18000]

valgrind:

==22381== Memcheck, a memory error detector
==22381== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==22381== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==22381== Command: pbs_server
==22381==
==22381==
==22381== HEAP SUMMARY:
==22381== in use at exit: 18,051 bytes in 53 blocks
==22381==   total heap usage: 169 allocs, 116 frees, 42,410 bytes allocated
==22381==
==22382==
==22382== HEAP SUMMARY:
==22382== in use at exit: 19,755 bytes in 56 blocks
==22382==   total heap usage: 172 allocs, 116 frees, 44,114 bytes allocated
==22382==
==22381== LEAK SUMMARY:
==22381==definitely lost: 0 bytes in 0 blocks
==22381==indirectly lost: 0 bytes in 0 blocks
==22381==  possibly lost: 0 bytes in 0 blocks
==22381==still reachable: 18,051 bytes in 53 blocks
==22381== suppressed: 0 bytes in 0 blocks
==22381== Rerun with --leak-check=full to see details of leaked memory
==22381==
==22381== For counts of detected and suppressed errors, rerun with: -v
==22381== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==22383==
==22383== Process terminating with default action of signal 11 (SIGSEGV)
==22383==  General Protection Fault
==22383==at 0x72192CB: __lll_unlock_elision (elision-unlock.c:33)
==22383==by 0x4E7E1A: unlock_node(pbsnode*, char const*, char const*, int) 
(u_lock_ctl.c:268)
==22383==by 0x4B7A66: mom_hierarchy_handler::make_default_hierarchy() 
(mom_hierarchy_handler.cpp:164)
==22383==by 0x4B898C: mom_hierarchy_handler::loadHierarchy() 
(mom_hierarchy_handler.cpp:433)
==22383==by 0x4B8AE7: mom_hierarchy_handler::initialLoadHierarchy() 
(mom_hierarchy_handler.cpp:472)
==22383==by 0x452629: pbsd_init(int) (pbsd_init.c:2299)
==22383==by 0x4591FE: main (pbsd_main.c:1883)
==22382== LEAK SUMMARY:
==22382==definitely lost: 0 bytes in 0 blocks
==22382==indirectly lost: 0 bytes in 0 blocks
==22382==  possibly lost: 0 bytes in 0 blocks
==22382==still reachable: 19,755 bytes in 56 blocks
==22382== suppressed: 0 bytes in 0 blocks
==22382== Rerun with --leak-check=full to see details of leaked memory
==22382==
==22382== For counts of detected and suppressed errors, rerun with: -v
==22382== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==22383==
==22383== HEAP SUMMARY:
==22383== in use at exit: 325,348 bytes in 186 blocks
==22383==   total heap usage: 297 allocs, 111 frees, 442,971 bytes allocated
==22383==
==22383== LEAK SUMMARY:
==22383==definitely lost: 134 bytes in 6 blocks
==22383==indirectly lost: 28 bytes in 3 blocks
==22383==  possibly lost: 524 bytes in 17 blocks
==22383==still reachable: 324,662 bytes in 160 blocks
==22383== suppressed: 0 bytes in 0 blocks
==22383== Rerun with --leak-check=full to see details of leaked memory
==22383==
==22383== For counts of detected and suppressed errors, rerun with: -v
==22383== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
~

 No other software have this behavior, i 

Bug#834083: libc-bin: essential tag

[Javier Serrano Polo]

X-Debbugs-CC: cl...@debian.org, aure...@debian.org, adcon...@0c3.net, 
sthiba...@debian.org

El dj 11 de 08 de 2016 a les 21:55 +0200, Aurelien Jarno va escriure:
> On 2016-08-11 21:32, Javier Serrano Polo wrote:
> > libc-bin is tagged essential since 2.13-10. Old systems based on Squeeze
> > can work without libc-bin, with a dpkg that does not require ldconfig.
> 
> No they can't. In squeeze, the binaries from libc-bin were included in
> libc6. The package has been split as part of the switch to multiarch.

This is not correct:
https://archive.debian.net/squeeze/libc-bin

> > Could anyone explain why libc-bin is essential?
> 
> Because it provides binaries and configuration files essential for the
> system: ldconfig, getent, ld.so.conf, nsswitch.conf, C.UTF-8 locale, etc.

These elements are very useful, but a system based on Squeeze can work
without them. Is there any other reason in a Sid system?


smime.p7s
Description: S/MIME cryptographic signature

Bug#833820: sphinx: Avoid evaulating default function arguments when including them in the documentation

[Petter Reinholdtsen]

[Dmitry Shachnev]
> Speaking about your example, I would recommend against using such
> functions at all: the default argument of that function is module
> *import* time, not the actual time when it is executed; this is not
> what one may expect.

I agree completely, and that issue is being tracked as 
http://bugs.debian.org/833821 > and is going to be fixed upstream.

-- 
Happy hacking
Petter Reinholdtsen

Bug#834093: guile-2.0: leaves alternatives after purge: /usr/bin/guile, /usr/share/man/man1/guile.1.gz

[Andreas Beckmann]

Package: guile-2.0
Version: 2.0.11+1-11
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8:

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

The leftover files are actually alternatives that were installed by the
package but have not been properly removed.

While there is ongoing discussion how to remove alternatives correctly
(see https://bugs.debian.org/71621 for details) the following strategy
should work for regular cases:
* 'postinst configure' always installs the alternative
* 'prerm remove' removes the alternative
* 'postrm remove' and 'postrm disappear' remove the alternative
In all other cases a maintainer script is invoked (e.g. upgrade,
deconfigure) the alternatives are not modified to preserve user
configuration.
Removing the alternative in 'prerm remove' avoids having a dangling link
once the actual file gets removed, but 'prerm remove' is not called in
all cases (e.g. unpacked but not configured packages or disappearing
packages) so the postrm must remove the alternative again
(update-alternatives gracefully handles removal of non-existing
alternatives).

Note that the arguments for adding and removing alternatives differ, for
removal it's 'update-alternatives --remove  '.

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

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

0m38.2s INFO: Warning: Package purging left files on system:
  /etc/alternatives/guile -> /usr/lib/x86_64-linux-gnu/guile-2.0/bin/guile  
 not owned
  /etc/alternatives/guile.1.gz -> /usr/share/man/man1/guile-2.0.1.gz not 
owned
  /usr/bin/guile -> /etc/alternatives/guile  not owned
  /usr/share/man/man1/guile.1.gz -> /etc/alternatives/guile.1.gz not 
owned


cheers,

Andreas


guile-2.0_2.0.11+1-11.log.gz
Description: application/gzip

Bug#834092: libapache2-mod-php7.0: Need to declare dependency on mpm_prefork in php7.0.load

[Stefan Fritsch]

Package: libapache2-mod-php7.0
Version: 7.0.9-2
Severity: normal

If the admin

  * installs mod_php
  * disables it
  * switches to a threaded mpm
  * enables it again some time later

apache2 will fail to start with "Apache is running a threaded MPM, but
your PHP Module is not compiled to be threadsafe.  You need to recompile
PHP."

If you put a "# Depends: mpm_prefork" into the php7.0.load file, the
"a2enmod php7.0" will already fail with a better error message.

Bug#834091: RM: fakepop -- RoQA; unused, orphaned, dead upstream

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Hi,
please remove fakepop. It's virtually unused, orphaned since
two years without an adopter and the former maintainer is
also upstream, suggesting that it's also dead upstream.

Cheers,
Moritz

Bug#834090: diaspora-common: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/diaspora-common/nginx.conf.example

[Andreas Beckmann]

Package: diaspora-common
Version: 0.5.9.1+debian4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
https://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Selecting previously unselected package diaspora-common.
  (Reading database ... 
(Reading database ... 11233 files and directories currently installed.)
  Preparing to unpack .../diaspora-common_0.5.9.1+debian4_all.deb ...
  Unpacking diaspora-common (0.5.9.1+debian4) ...
  Setting up diaspora-common (0.5.9.1+debian4) ...
  dbconfig-common: writing config to /etc/dbconfig-common/diaspora-common.conf
  
  Creating config file /etc/dbconfig-common/diaspora-common.conf with new 
version
  creating postgres user diaspora:  success.
  verifying creation of user: success.
  creating database diaspora_production: success.
  verifying database diaspora_production exists: success.
  dbconfig-common: flushing administrative password
  SSL enabled, configuring nginx for localhost...
  nginx.conf.example not found
  dpkg: error processing package diaspora-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   diaspora-common


Cheers,

Andreas


diaspora-common_0.5.9.1+debian4.log.gz
Description: application/gzip

Bug#832599: Fails to start after upgrade

[Chris Knadle]

gregor herrmann:
[...]
> But I also started looking at deb-systemd-helper (in
> init-system-helpers) and found an interesting example:
> 
> https://sources.debian.net/src/isatapd/0.9.7-2/debian/postinst/?hl=12#L12
> 
> Maybe this is the way to go?
> (And if yes: "disable" or "mask"?)

The code in the above link is what I expected to help: sourcing in the
/etc/default file, and having systemd enable or disable the service in
the postinst.


I just had a look at the way this is being done in the vsftpd package;
it Buidl-Depends on dh-systemd, and in the debian/rules file it has:

   dh ${@} --parallel --with=systemd

which is the same as you have in iodine, except for the --parallel...
where it differes slightly is in debian/postinst where it has the
following snippet in the "configure" case:

if [ -f "systemd-tmpfiles" ]
then
systemd-tmpfiles --create --exclude-prefix=/dev
fi
;;

When the package installs, it appears dh_systemd_enable modifies the
vsftpd.postinst file (thus the file in /var/lib/dpkg info differs from
that of the source package after installation -- ugh) which removes the
above snippet and adds the following after the case statement:


---
# Automatically added by dh_systemd_enable
# This will only remove masks created by d-s-h on package removal.
deb-systemd-helper unmask vsftpd.service >/dev/null || true

# was-enabled defaults to true, so new installations run enable.
if deb-systemd-helper --quiet was-enabled vsftpd.service; then
# Enables the unit on first installation, creates new
# symlinks on upgrades if the unit file has changed.
deb-systemd-helper enable vsftpd.service >/dev/null || true
else
# Update the statefile to add new symlinks (if any), which need
to be
# cleaned up on purge. Also remove old symlinks.
deb-systemd-helper update-state vsftpd.service >/dev/null || true
fi
# End automatically added section
# Automatically added by dh_installinit
if [ -x "/etc/init.d/vsftpd" ]; then
update-rc.d vsftpd defaults >/dev/null
invoke-rc.d vsftpd start || exit $?
fi
# End automatically added section
---



The 'purge' case of the vsftpd.postrm has this:


---
purge)
#
# purge systemd files
#
rm -f /etc/systemd/system/vsftpd.service
rm -f /etc/systemd/system/multi-user.target.wants/vsftpd.service
rm -f
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/vsftpd.service
rm -f
/var/lib/systemd/deb-systemd-helper-enabled/vsftpd.service.dsh-also
rm -f /var/lib/systemd/deb-systemd-helper-masked/vsftpd.service
if [ -d
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ ]; then
rmdir --ignore-fail-on-non-empty
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/
fi
if [ -d /var/lib/systemd/deb-systemd-helper-enabled ]; then
rmdir --ignore-fail-on-non-empty
/var/lib/systemd/deb-systemd-helper-enabled
fi
if [ -d /var/lib/systemd/deb-systemd-helper-masked ]; then
rmdir --ignore-fail-on-non-empty
/var/lib/systemd/deb-systemd-helper-masked
fi
;;

---

and after installation the file in /var/lib/dpkg/info/vsftpd.postrm has
the entirety of the above snippet removed, with the following added
after the case statement:


---
# Automatically added by dh_installinit
if [ "$1" = "purge" ] ; then
update-rc.d vsftpd remove >/dev/null
fi


# In case this system is running systemd, we make systemd reload the
unit files
# to pick up changes.
if [ -d /run/systemd/system ] ; then
systemctl --system daemon-reload >/dev/null || true
fi
# End automatically added section
# Automatically added by dh_systemd_enable
if [ "$1" = "remove" ]; then
if [ -x "/usr/bin/deb-systemd-helper" ]; then
deb-systemd-helper mask vsftpd.service >/dev/null
fi
fi

if [ "$1" = "purge" ]; then
if [ -x "/usr/bin/deb-systemd-helper" ]; then
deb-systemd-helper purge vsftpd.service >/dev/null
deb-systemd-helper unmask vsftpd.service >/dev/null
fi
fi
# End automatically added section
# Automatically added by dh_installdebconf
if [ "$1" = purge ] && [ -e /usr/share/debconf/confmodule ]; then
. /usr/share/debconf/confmodule
db_purge
fi
# End automatically added section
---



This seems to be ... a bit more confusing than I would have hoped.

   -- Chris

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

Bug#834085: RM: yui -- RoQA; obsolete, RC-buggy

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Hi,
please remove yui. It's superceded by src:yui3 and the old version is
unsecure and otherwise RC-buggy.

Cheers,
Moritz

Bug#834084: RM: webgui -- RoQA; depends on obsolete package, RC-buggy, not in testing for a long time, unused

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Hi,
please remove webgui. It's blocking the removal of src:yui for many
years now, it RC-buggy for a long time, dead upstream, not in testing
since 2010(!) and virtually unusued according to popcon.

Cheers,
Moritz

Bug#830344: Moving forward with the Project Roadmap question

[Lucas Nussbaum]

Hi,

On 11/08/16 at 20:17 +0200, Margarita Manterola wrote:
> 2) The TC will act as an advisor to the Roadmap Team
> 3) The TC will not be involved as body with the Roadmap Team

I'm not sure about those two options.

Would (2) go further than powers already available to the TC under
§6.1? What would it mean in practice, in terms of workflows?

Does (3) mean that the TC waives its §6.1 powers for Roadmap issues?

Wouldn't it be better to just state that:
2') the TC declines to be the Roadmap team, but will of course be
available, if necessary, under Constitution §6.1.

Lucas

Bug#834083: libc-bin: essential tag

[Javier Serrano Polo]

Package: libc-bin
Version: 2.23-4
Severity: wishlist
X-Debbugs-CC: cl...@debian.org, aure...@debian.org, adcon...@0c3.net, 
sthiba...@debian.org

libc-bin is tagged essential since 2.13-10. Old systems based on Squeeze
can work without libc-bin, with a dpkg that does not require ldconfig.
Could anyone explain why libc-bin is essential?


smime.p7s
Description: S/MIME cryptographic signature

Bug#733961: Migration to yui3

[Moritz Mühlenhoff]

On Thu, Jul 14, 2016 at 10:00:53PM +0200, Moritz Mühlenhoff wrote:
> On Thu, Jan 02, 2014 at 03:05:20PM -0430, Ernesto Hernández-Novich wrote:
> > On Thu, 2014-01-02 at 19:06 +0100, Moritz Muehlenhoff wrote:
> > [...]
> > > Please migrate from src:yui to src:yui3.
> > > 
> > > src:yui is abandoned, see
> > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730104
> > 
> > Hi Moritz.
> > 
> > Thanks for the report.
> > 
> > WebGUI uses YUI 2.9 and since YUI 3 is not backwards compatible with YUI
> > 2.x, I'll have to wait for upstream to transition. There hasn't been
> > upgrades to WebGUI 7.10 for a while now, so I'm not sure when will that
> > happen, if it happens at all.
> 
> It's been 2.5 years. Is that fixed upstream, otherwise let's remove webgui
> along with yui 2 now.

I'm requesting removal now, this has been blocking the removal of yui2 for
a long time now.
 
Cheers,
 Moritz

Bug#834081: Missing dependency on libfastjson-dev

[Michael Biebl]

Package: liblognorm-dev
Version: 2.0.1-1
Severity: serious
Tags: patch

Hi,

liblognorm.pc has

Requires: libfastjson
Requires.private: libestr

This means, the package needs a dependency on libestr-dev and
libfastjson-dev.

The package currently depends on libjson-c-dev, but not libfastjson-dev.
This needs to be changed.

Patch attached.

Regards,
Michael

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

Kernel: Linux 4.6.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 liblognorm-dev depends on:
ii  libestr-dev  0.1.10-2
ii  libjs-sphinxdoc  1.4.5-1
ii  libjson-c-dev0.12-3
ii  liblognorm5  2.0.1-1

liblognorm-dev recommends no packages.

liblognorm-dev suggests no packages.

-- no debconf information
diff --git a/debian/control b/debian/control
index 701fb6d..f52d57a 100644
--- a/debian/control
+++ b/debian/control
@@ -21,7 +21,7 @@ Architecture: any
 Depends: liblognorm5 (= ${binary:Version}),
 ${misc:Depends},
 ${sphinxdoc:Depends},
-libjson-c-dev,
+libfastjson-dev,
 libestr-dev
 Multi-Arch: foreign
 Description: log normalizing library - development files

Bug#834082: RM: mariadb-client-lgpl -- RoQA; renamed to mariadb-connector-c

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

Hi,

please remove the remaining bits of the mariadb-client-lgpl package,
this has been renamed upstream to mariadb-connector-c.

The old name libmariadb-client-lgpl-dev is still provided by
libmariadb-dev, so the only rdepends using it (rmysql) is still OK
after the removal.


Andreas

Bug#833283: syslog-ng: Can't upgrade to latest version

[Nigel Horne]

Hi,


Thanks for your reply.

 > I'm quite sure, this issue happened because your configuration file is

incompatible with the new version. To prove this, please send the output
of the "systemctl status syslog-ng.service" command after the failed
upgrade and/or the configuration file if it possible. Also I'm thinking
about a more robust upgrade path, covering this situation.


# systemctl status syslog-ng.service
● syslog-ng.service - System Logger Daemon
   Loaded: loaded (/lib/systemd/system/syslog-ng.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: start-limit-hit) since Thu 2016-08-11 15:09:18 EDT; 
2min 56s ago
 Docs: man:syslog-ng(8)
  Process: 26870 ExecStart=/usr/sbin/syslog-ng -F $SYSLOGNG_OPTS (code=exited, 
status=1/FAILURE)
 Main PID: 26870 (code=exited, status=1/FAILURE)
   Status: "Starting up... (Thu Aug 11 15:09:17 2016"

Aug 11 15:09:17 compaq systemd[1]: syslog-ng.service: Failed with result 
'exit-code'.
Aug 11 15:09:18 compaq systemd[1]: syslog-ng.service: Service hold-off time 
over, scheduling restart.
Aug 11 15:09:18 compaq systemd[1]: Stopped System Logger Daemon.
Aug 11 15:09:18 compaq systemd[1]: syslog-ng.service: Start request repeated 
too quickly.
Aug 11 15:09:18 compaq systemd[1]: Failed to start System Logger Daemon.
Aug 11 15:09:18 compaq systemd[1]: syslog-ng.service: Unit entered failed state.
Aug 11 15:09:18 compaq systemd[1]: syslog-ng.service: Failed with result 
'start-limit-hit'.

There are quite a few configuration files, here is 
/etc/syslog-ng/syslog-ng.conf.  Please let me
know if you need something else.

@version: 3.5
@include "scl.conf"
@include "`scl-root`/system/tty10.conf"

# Syslog-ng configuration file, compatible with default Debian syslogd
# installation.

# First, set some global options.
options { chain_hostnames(off); flush_lines(0); use_dns(yes); use_fqdn(no);
  owner("root"); group("adm"); perm(0640); stats_freq(0);
  normalize_hostnames(yes); dns_cache_hosts(/etc/hosts);
  bad_hostname("^gconfd$");
};


# Sources

# This is the default behavior of sysklogd package
# Logs may come from unix stream, but not from another machine.
#
source s_src {
   system();
   internal();
};

# If you wish to get logs from remote machine you should uncomment
# this and comment the above source line.
#
source s_net { tcp(ip(127.0.0.1) port(1000)); tcp(ip(192.168.1.2) port(1000)); 
udp(); };


# Destinations

# First some standard logfile
#
destination d_auth { file("/var/log/syslog/local/auth.log"); };
destination d_cron { file("/var/log/syslog/local/cron.log"); };
destination d_daemon { file("/var/log/syslog/local/daemon.log"); };
destination d_kern { file("/var/log/syslog/local/kern.log"); };
destination d_lpr { file("/var/log/syslog/local/lpr.log"); };
destination d_mail { file("/var/log/syslog/local/mail.log"); };
destination d_syslog { file("/var/log/syslog/local/syslog"); };
destination d_user { file("/var/log/syslog/local/user.log"); };
destination d_uucp { file("/var/log/syslog/local/uucp.log"); };

# This files are the log come from the mail subsystem.
#
destination d_mailinfo { file("/var/log/syslog/local/mail/mail.info"); };
destination d_mailwarn { file("/var/log/syslog/local/mail/mail.warn"); };
destination d_mailerr { file("/var/log/syslog/local/mail/mail.err"); };

# Logging for INN news system
#
destination d_newscrit { file("/var/log/syslog/local/news.crit"); };
destination d_newserr { file("/var/log/syslog/local/news.err"); };
destination d_newsnotice { file("/var/log/syslog/local/news.notice"); };

# Some `catch-all' logfiles.
#
destination d_debug { file("/var/log/syslog/local/debug"); };
destination d_error { file("/var/log/syslog/local/error"); };
destination d_messages { file("/var/log/syslog/local/messages"); };

# The root's console.
#
destination d_console { usertty("root"); };

# Virtual console.
#
destination d_console_all { file(`tty10`); };

# The named pipe /dev/xconsole is for the nsole' utility.  To use it,
# you must invoke nsole' with the -file' option:
#
#$ xconsole -file /dev/xconsole [...]
#
destination d_xconsole { pipe("/dev/xconsole"); };

# Send the messages to an other host
#
#destination d_net { tcp("127.0.0.1" port(1000) log_fifo_size(1000)); };

# Debian only
destination d_ppp { file("/var/log/syslog/local/ppp.log"); };

# http://www.linuxjournal.com/content/creating-centralized-syslog-server
destination d_net_auth {
file("/var/log/syslog/remote/$HOST_FROM/auth.log");
};
destination d_net_cron {
file("/var/log/syslog/remote/$HOST_FROM/cron.log");
};
destination d_net_daemon {
file("/var/log/syslog/remote/$HOST_FROM/daemon.log");
};
destination d_net_kern {
file("/var/log/syslog/remote/$HOST_FROM/kern.log");
};
destination d_net_lpr {
file("/var/log/syslog/remote/$HOST_FROM/lpr.log");
};
destination d_net_mail {

Bug#834079: atril: FTBFS: ./autogen.sh: 80: shift: can't shift that many

[Chris Lamb]

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

Dear Maintainer,

atril fails to build from source in unstable/amd64:

  [..]

  Setting up libxcb-dri2-0-dev:amd64 (1.11.1-1) ...
  Setting up libxcb-render0-dev:amd64 (1.11.1-1) ...
  Setting up x11proto-damage-dev (1:1.2.1-2) ...
  Setting up libxft-dev (2.3.2-1) ...
  Setting up gtk-update-icon-cache (3.20.7-1) ...
  Setting up libgdk-pixbuf2.0-dev (2.34.0-1) ...
  Setting up libxcb-dri3-dev:amd64 (1.11.1-1) ...
  Setting up libxcursor1:amd64 (1:1.1.14-1+b1) ...
  Setting up libxext-dev:amd64 (2:1.3.3-1) ...
  Setting up libpango-1.0-0:amd64 (1.40.1-1) ...
  Setting up libwayland-egl1-mesa:amd64 (11.2.2-1) ...
  Setting up libxcb-shape0-dev:amd64 (1.11.1-1) ...
  Setting up libatk-bridge2.0-0:amd64 (2.20.1-3) ...
  Setting up librest-0.7-0:amd64 (0.8.0-1) ...
  Setting up libxxf86vm1:amd64 (1:1.1.4-1) ...
  Setting up libxxf86vm-dev:amd64 (1:1.1.4-1) ...
  Setting up libxfixes-dev:amd64 (1:5.0.2-1) ...
  Setting up x11proto-composite-dev (1:0.4.2-2) ...
  Setting up libxrandr2:amd64 (2:1.5.0-1) ...
  Setting up libxi6:amd64 (2:1.7.6-1) ...
  Setting up gir1.2-atspi-2.0 (2.20.2-1) ...
  Setting up libsoup2.4-dev (2.54.1-1) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up libnotify4:amd64 (0.7.6-2) ...
  Setting up libxinerama1:amd64 (2:1.1.3-1+b1) ...
  Setting up libxcursor-dev:amd64 (1:1.1.14-1+b1) ...
  Setting up libxcb-randr0-dev:amd64 (1.11.1-1) ...
  Setting up libpoppler-glib8:amd64 (0.44.0-3) ...
  Setting up libxdamage1:amd64 (1:1.1.4-2+b1) ...
  Setting up libxrandr-dev:amd64 (2:1.5.0-1) ...
  Setting up libxcomposite-dev (1:0.4.4-1) ...
  Setting up libcairo-script-interpreter2:amd64 (1.14.6-1+b1) ...
  Setting up libxcb-xfixes0-dev:amd64 (1.11.1-1) ...
  Setting up libstartup-notification0-dev:amd64 (0.12-4) ...
  Setting up libcairo-gobject2:amd64 (1.14.6-1+b1) ...
  Setting up libxdamage-dev:amd64 (1:1.1.4-2+b1) ...
  Setting up libxtst6:amd64 (2:1.2.2-1+b1) ...
  Setting up libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Setting up libgl1-mesa-glx:amd64 (11.2.2-1) ...
  Setting up libxinerama-dev:amd64 (2:1.1.3-1+b1) ...
  Setting up libgxps2:amd64 (0.2.4-1) ...
  Setting up libxcb-present-dev:amd64 (1.11.1-1) ...
  Setting up libxi-dev (2:1.7.6-1) ...
  Setting up libcairo2-dev (1.14.6-1+b1) ...
  Setting up gir1.2-freedesktop:amd64 (1.48.0-3) ...
  Setting up at-spi2-core (2.20.2-1) ...
  Setting up libpangoxft-1.0-0:amd64 (1.40.1-1) ...
  Setting up libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Setting up gir1.2-poppler-0.18 (0.44.0-3) ...
  Setting up gir1.2-pango-1.0:amd64 (1.40.1-1) ...
  Setting up libxtst-dev:amd64 (2:1.2.2-1+b1) ...
  Setting up gir1.2-gxps-0.1:amd64 (0.2.4-1) ...
  Setting up libegl1-mesa-dev:amd64 (11.2.2-1) ...
  Setting up libpango1.0-dev (1.40.1-1) ...
  Setting up libgxps-dev:amd64 (0.2.4-1) ...
  Setting up libgirepository1.0-dev (1.48.0-3) ...
  Setting up librsvg2-2:amd64 (2.40.16-1) ...
  Setting up libpoppler-glib-dev (0.44.0-3) ...
  Setting up libatspi2.0-dev (2.20.2-1) ...
  Setting up librsvg2-common:amd64 (2.40.16-1) ...
  Setting up libatk-bridge2.0-dev:amd64 (2.20.1-3) ...
  Setting up adwaita-icon-theme (3.20-3) ...
  update-alternatives: using /usr/share/icons/Adwaita/cursor.theme to provide 
/usr/share/icons/default/index.theme (x-cursor-theme) in auto mode
  Setting up libgtk-3-0:amd64 (3.20.7-1) ...
  Setting up libcaja-extension1:amd64 (1.14.1-1) ...
  Setting up libgail-3-0:amd64 (3.20.7-1) ...
  Setting up libmate-desktop-2-17:amd64 (1.14.1-1) ...
  Setting up gir1.2-gtk-3.0:amd64 (3.20.7-1) ...
  Setting up libwebkit2gtk-4.0-37:amd64 (2.12.3-1+b2) ...
  Setting up libgtk-3-dev:amd64 (3.20.7-1) ...
  Setting up gir1.2-webkit2-4.0:amd64 (2.12.3-1+b2) ...
  Setting up libwebkit2gtk-4.0-dev:amd64 (2.12.3-1+b2) ...
  Setting up libmate-desktop-dev:amd64 (1.14.1-1) ...
  Setting up libgail-3-dev:amd64 (3.20.7-1) ...
  Setting up libcaja-extension-dev:amd64 (1.14.1-1) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up docbook-xsl (1.79.1+dfsg-1) ...
  Setting up sgml-data (2.0.10) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up docbook (4.5-6) ...
  Setting up docbook-xml (4.5-7.3) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up docbook-to-man (1:2.0.0-34) ...
  Setting up liblwp-protocol-https-perl (6.06-2) ...
  Setting up libcupsfilters1:amd64 (1.10.0-1) ...
  Setting up libcupsimage2:amd64 (2.1.4-4) ...
  Setting up libgs9 (9.19~dfsg-1+b1) ...
  Setting up libspectre1:amd64 (0.2.7-4) ...
  Setting up libwww-perl (6.15-1) ...
  Setting up libspectre-dev (0.2.7-4) ...
  Setting up libxml-parser-perl (2.44-2) ...
  Setting up intltool (0.50.2-3) ...
  Setting up gnome-common (3.18.0-2) ...
  Setting up gtk-doc-tools (1.25-3) ...
  Setting up mate-common (1.14.0-1) ...
  Setting 

Bug#834080: elasticsearch: FTBFS: Could not resolve dependencies for project org.elasticsearch:elasticsearch:jar:1.7.5

[Chris Lamb]

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

Dear Maintainer,

elasticsearch fails to build from source in unstable/amd64:

  [..]

  Setting up libsurefire-java (2.17-2) ...
  Setting up maven-debian-helper (2.1.1) ...
  Setting up elasticsearch-build-deps (1.7.5-1) ...
  Processing triggers for libc-bin (2.23-4) ...
  Processing triggers for systemd (231-1) ...
  Processing triggers for ca-certificates (20160104) ...
  Updating certificates in /etc/ssl/certs...
  173 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  
  Adding debian:ACCVRAIZ1.pem
  Adding debian:ACEDICOM_Root.pem
  Adding debian:AC_Raíz_Certicámara_S.A..pem
  Adding debian:Actalis_Authentication_Root_CA.pem
  Adding debian:AddTrust_External_Root.pem
  Adding debian:AddTrust_Low-Value_Services_Root.pem
  Adding debian:AddTrust_Public_Services_Root.pem
  Adding debian:AddTrust_Qualified_Certificates_Root.pem
  Adding debian:AffirmTrust_Commercial.pem
  Adding debian:AffirmTrust_Networking.pem
  Adding debian:AffirmTrust_Premium.pem
  Adding debian:AffirmTrust_Premium_ECC.pem
  Adding debian:ApplicationCA_-_Japanese_Government.pem
  Adding debian:Atos_TrustedRoot_2011.pem
  Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
  Adding debian:Baltimore_CyberTrust_Root.pem
  Adding debian:Buypass_Class_2_CA_1.pem
  Adding debian:Buypass_Class_2_Root_CA.pem
  Adding debian:Buypass_Class_3_Root_CA.pem
  Adding debian:CA_Disig.pem
  Adding debian:CA_Disig_Root_R1.pem
  Adding debian:CA_Disig_Root_R2.pem
  Adding debian:CA_WoSign_ECC_Root.pem
  Adding debian:CFCA_EV_ROOT.pem
  Adding debian:CNNIC_ROOT.pem
  Adding debian:COMODO_Certification_Authority.pem
  Adding debian:COMODO_ECC_Certification_Authority.pem
  Adding debian:COMODO_RSA_Certification_Authority.pem
  Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
  Adding debian:Camerfirma_Global_Chambersign_Root.pem
  Adding debian:Certification_Authority_of_WoSign_G2.pem
  Adding debian:Certigna.pem
  Adding debian:Certinomis_-_Autorité_Racine.pem
  Adding debian:Certinomis_-_Root_CA.pem
  Adding debian:Certplus_Class_2_Primary_CA.pem
  Adding debian:Certum_Root_CA.pem
  Adding debian:Certum_Trusted_Network_CA.pem
  Adding debian:Chambers_of_Commerce_Root_-_2008.pem
  Adding 
debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
  Adding debian:ComSign_CA.pem
  Adding debian:Comodo_AAA_Services_root.pem
  Adding debian:Comodo_Secure_Services_root.pem
  Adding debian:Comodo_Trusted_Services_root.pem
  Adding debian:Cybertrust_Global_Root.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
  Adding debian:DST_ACES_CA_X6.pem
  Adding debian:DST_Root_CA_X3.pem
  Adding debian:Deutsche_Telekom_Root_CA_2.pem
  Adding debian:DigiCert_Assured_ID_Root_CA.pem
  Adding debian:DigiCert_Assured_ID_Root_G2.pem
  Adding debian:DigiCert_Assured_ID_Root_G3.pem
  Adding debian:DigiCert_Global_Root_CA.pem
  Adding debian:DigiCert_Global_Root_G2.pem
  Adding debian:DigiCert_Global_Root_G3.pem
  Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem
  Adding debian:DigiCert_Trusted_Root_G4.pem
  Adding debian:E-Tugra_Certification_Authority.pem
  Adding debian:EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
  Adding debian:EC-ACC.pem
  Adding debian:EE_Certification_Centre_Root_CA.pem
  Adding debian:Entrust.net_Premium_2048_Secure_Server_CA.pem
  Adding debian:Entrust_Root_Certification_Authority.pem
  Adding debian:Entrust_Root_Certification_Authority_-_EC1.pem
  Adding debian:Entrust_Root_Certification_Authority_-_G2.pem
  Adding debian:Equifax_Secure_CA.pem
  Adding debian:Equifax_Secure_Global_eBusiness_CA.pem
  Adding debian:Equifax_Secure_eBusiness_CA_1.pem
  Adding debian:GeoTrust_Global_CA.pem
  Adding debian:GeoTrust_Global_CA_2.pem
  Adding debian:GeoTrust_Primary_Certification_Authority.pem
  Adding debian:GeoTrust_Primary_Certification_Authority_-_G2.pem
  Adding debian:GeoTrust_Primary_Certification_Authority_-_G3.pem
  Adding debian:GeoTrust_Universal_CA.pem
  Adding debian:GeoTrust_Universal_CA_2.pem
  Adding debian:GlobalSign_ECC_Root_CA_-_R4.pem
  Adding debian:GlobalSign_ECC_Root_CA_-_R5.pem
  Adding debian:GlobalSign_Root_CA.pem
  Adding debian:GlobalSign_Root_CA_-_R2.pem
  Adding debian:GlobalSign_Root_CA_-_R3.pem
  Adding debian:Global_Chambersign_Root_-_2008.pem
  Adding debian:Go_Daddy_Class_2_CA.pem
  Adding debian:Go_Daddy_Root_Certificate_Authority_-_G2.pem
  Adding debian:Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem
  Adding debian:Hongkong_Post_Root_CA_1.pem
  Adding debian:IGC_A.pem
  Adding debian:IdenTrust_Commercial_Root_CA_1.pem
  Adding debian:IdenTrust_Public_Sector_Root_CA_1.pem
  Adding debian:Izenpe.com.pem
  Adding debian:Juur-SK.pem
  Adding 

Bug#834073: [Aptitude-devel] Bug#834073: aptitude search gives less results than apt-cache search

[Axel Beckert]

Hi shirish,

shirish शिरीष wrote:
> As shared above, aptitude search gives far less results than
> apt-cache search.

Yes. It does so for ages.

> For instance -
>
> [$] aptitude search marathi
>
> p   task-marathi-
> Marathi environment
> p   task-marathi-desktop-
> Marathi desktop
>
> Now let's try the same using either apt-cache or axi-cache
>
> [$] apt-cache search marathi
>  [0:07:03]
> aspell-mr - Marathi (mr) dictionary for GNU aspell
> festival-mr - festival text to speech synthesizer for Marathi language
[...]

"apt-cache search" by default searches package name _and_ description.

"aptitude search" by default searches only in packages names -- which
also can be seen nicely in your examples.

See the documentation at e.g.
http://aptitude.alioth.debian.org/doc/en/ch02s04s05.html#searchTermReferenceList

If you want the same result as with apt-cache use e.g. this command:

→ aptitude search "~dmarathi" "~nmarathi"
p   aspell-mr  - Marathi (mr) dictionary for GNU aspell
p   festival-mr- festival text to speech synthesizer for 
Marathi language
p   festvox-mr-nsk - Marathi male speaker for festival
p   firefox-esr-l10n-mr- Marathi language package for Firefox ESR
p   firefox-l10n-mr- Marathi language package for Firefox
p   fonts-deva-extra   - Free fonts for Devanagari script
p   fonts-gargi- OpenType Devanagari font
p   fonts-lohit-deva   - Lohit TrueType font for Devanagari script
p   fonts-nakula   - Free Unicode compliant Devanagari font
p   fonts-sahadeva - Free Unicode compliant Devanagari font
p   fonts-samyak-deva  - Samyak TrueType font for Devanagari script
p   fonts-sarai- truetype font for devanagari script
p   gcompris-sound-mr  - Indian Marathi sound files for GCompris
p   hyphen-mr  - Marathi hyphenation patterns for 
LibreOffice
p   iceweasel-l10n-mr  - Marathi language package for Iceweasel - 
Transitional package
p   iok- Indic Onscreen Keyboard
p   iok:i386   - Indic Onscreen Keyboard
p   kde-l10n-mr- Marathi (mr) localization files for KDE
p   libreoffice-l10n-mr- office productivity suite -- Marathi 
language package
p   task-marathi   - Marathi environment
p   task-marathi-desktop   - Marathi desktop
p   tesseract-ocr-mar  - tesseract-ocr language files for Marathi

In the opposite direction, you'll get the same result as "aptitude
search" with "apt-cache search -n":

→ apt-cache search -n marathi
task-marathi - Marathi environment
task-marathi-desktop - Marathi desktop

So unless you want to change aptitude's default, I don't see any bug
here and would like to close this bug report again.

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

Bug#834076: autopkgtest: Use pycodestyle instead of pep8

[Ondřej Nový]

Package: autopkgtest
Version: 4.0.3
Severity: normal

pep8 was renamed to pycodestyle. Patch attached.

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 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 autopkgtest depends on:
ii  apt-utils   1.3~pre3
ii  libdpkg-perl1.18.10
ii  procps  2:3.3.12-2
ii  python3 3.5.1-4
pn  python3-debian  

Versions of packages autopkgtest recommends:
ii  autodep8  0.7.1

Versions of packages autopkgtest suggests:
pn  lxc  
pn  lxd-client   
pn  qemu-system  
pn  qemu-utils   
ii  schroot  1.6.10-2

-- no debconf information
commit 40e6142680fdecb0c4829c708f5037d347a91151
Author: Ondřej Nový 
Date:   Thu Aug 11 21:00:06 2016 +0200

Use pycodestyle instead of pep8

diff --git a/debian/changelog b/debian/changelog
index 3b63059..d4d2568 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+autopkgtest (4.0.4) UNRELEASED; urgency=medium
+
+  * Use pycodestyle instead of pep8
+
+ -- Ondřej Nový   Thu, 11 Aug 2016 20:59:09 +0200
+
 autopkgtest (4.0.3) unstable; urgency=medium
 
   [ Christian Kastner ]
diff --git a/debian/control b/debian/control
index 6194693..31c7502 100644
--- a/debian/control
+++ b/debian/control
@@ -11,7 +11,7 @@ Build-Depends: debhelper (>= 9),
  python3-docutils,
  pyflakes,
  procps,
- pep8
+ pycodestyle
 Vcs-Git: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git
 Vcs-Browser: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git
 X-Python3-Version: >= 3.1
diff --git a/debian/rules b/debian/rules
index a7259e3..b4640d7 100755
--- a/debian/rules
+++ b/debian/rules
@@ -36,7 +36,7 @@ override_dh_auto_install:
 override_dh_auto_test:
 ifeq (, $(findstring nocheck, $(DEB_BUILD_OPTIONS)))
 	if type pyflakes3 >/dev/null 2>&1; then tests/pyflakes; else echo "pyflakes3 not available, skipping"; fi
-	tests/pep8 || true
+	tests/pycodestyle || true
 	tests/testdesc
 	tests/run_args
 	env NO_PKG_MANGLE=1 tests/autopkgtest NullRunner
diff --git a/tests/pep8 b/tests/pep8
deleted file mode 100755
index 65884e5..000
--- a/tests/pep8
+++ /dev/null
@@ -1,12 +0,0 @@
-#!/bin/sh
-set -e
-testdir="$(dirname $(readlink -f $0))"
-rootdir="$(dirname $testdir)"
-
-pep8 --ignore E402,E501 $rootdir/lib/*.py $rootdir/tools/autopkgtest-buildvm-ubuntu-cloud
-
-for v in chroot null schroot lxc lxd qemu ssh; do
-pep8 --ignore E501,E402 $rootdir/virt/$v
-done
-
-pep8 --ignore E501,E402 $rootdir/runner/autopkgtest $testdir/autopkgtest $testdir/adt-run $testdir/testdesc $testdir/run_args $testdir/*.py
diff --git a/tests/pycodestyle b/tests/pycodestyle
new file mode 100755
index 000..4cfbca1
--- /dev/null
+++ b/tests/pycodestyle
@@ -0,0 +1,12 @@
+#!/bin/sh
+set -e
+testdir="$(dirname $(readlink -f $0))"
+rootdir="$(dirname $testdir)"
+
+pycodestyle --ignore E402,E501 $rootdir/lib/*.py $rootdir/tools/autopkgtest-buildvm-ubuntu-cloud
+
+for v in chroot null schroot lxc lxd qemu ssh; do
+pycodestyle --ignore E501,E402 $rootdir/virt/$v
+done
+
+pycodestyle --ignore E501,E402 $rootdir/runner/autopkgtest $testdir/autopkgtest $testdir/adt-run $testdir/testdesc $testdir/run_args $testdir/*.py
diff --git a/tests/run-parallel b/tests/run-parallel
index fa1a2e5..4c3b103 100755
--- a/tests/run-parallel
+++ b/tests/run-parallel
@@ -5,7 +5,7 @@ MYDIR=$(dirname $0)
 
 # these are fast, run them first
 set -e
-$MYDIR/pep8
+$MYDIR/pycodestyle
 $MYDIR/pyflakes
 $MYDIR/testdesc
 $MYDIR/autopkgtest_args

Bug#832851: python-argh: diff for NMU version 0.26.1-1.1

[Sean Whitton]

Control: tags 832851 + patch

Dear maintainer,

I've prepared an NMU for python-argh (versioned as 0.26.1-1.1) and
submitted an RFS to have it uploaded.

Regards.

-- 
Sean Whitton
diff -Nru python-argh-0.26.1/debian/changelog python-argh-0.26.1/debian/changelog
--- python-argh-0.26.1/debian/changelog	2015-02-16 21:51:21.0 -0700
+++ python-argh-0.26.1/debian/changelog	2016-08-11 11:58:52.0 -0700
@@ -1,3 +1,11 @@
+python-argh (0.26.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update 0001-fix-unit-tests.patch for newer sbuild (Closes: #832851).
+The LANG environment variable might not be set.
+
+ -- Sean Whitton   Thu, 11 Aug 2016 11:58:52 -0700
+
 python-argh (0.26.1-1) unstable; urgency=medium
 
   [ Marco Nenciarini ]
diff -Nru python-argh-0.26.1/debian/patches/0001-fix-unit-tests.patch python-argh-0.26.1/debian/patches/0001-fix-unit-tests.patch
--- python-argh-0.26.1/debian/patches/0001-fix-unit-tests.patch	2015-02-16 21:51:21.0 -0700
+++ python-argh-0.26.1/debian/patches/0001-fix-unit-tests.patch	2016-08-11 11:54:21.0 -0700
@@ -1,6 +1,7 @@
 From: Marco Nenciarini 
 Date: Mon, 16 Feb 2015 20:22:58 +0100
 Subject: fix unit tests
+Last-Update: 2016-08-11
 
 ---
  test/test_integration.py | 3 ++-
@@ -45,7 +46,7 @@
  
  
 +@pytest.mark.xfail(sys.version_info <= (3,0)
-+   and os.environ['LANG'] == 'C',
++   and ('LANG' not in os.environ or os.environ['LANG'] == 'C'),
 +   reason='It fails on buildd')
  def test_encoding():
  "Unicode is accepted as prompt message"


signature.asc
Description: PGP signature

Bug#834078: RFS: python-argh/0.26.1-1.1 [NMU, RC] -- simple argparse wrapper

[Sean Whitton]

Package: sponsorship-requests
Severity: important
Control: block 832851 by -1

Dear mentors,

I am looking for a sponsor for an NMU of python-argh, fixing a stretch RC
bug (older than 7 days and no maintainer activity).

* Package name: python-argh
  Version : 0.26.1-1.1
  Upstream Author : Andrey Mikhailenko 
* URL : http://pypi.python.org/pypi/argh
* License : LGPL-3.0+
  Section : python

Changes since the last upload:

  * Non-maintainer upload.
  * Update 0001-fix-unit-tests.patch for newer sbuild (Closes: #832851).
The LANG environment variable might not be set.

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/p/python-argh/python-argh_0.26.1-1.1.dsc

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#834077: llvm-3.9: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/bugpoint.1.gz

[Andreas Beckmann]

Package: llvm-3.9
Version: 1:3.9~+rc1-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package llvm-3.9.
  Preparing to unpack .../llvm-3.9_1%3a3.9~+rc1-1~exp1_amd64.deb ...
  Unpacking llvm-3.9 (1:3.9~+rc1-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/llvm-3.9_1%3a3.9~+rc1-1~exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/bugpoint.1.gz', which is also in 
package llvm 1:3.6-33
  Processing triggers for libc-bin (2.23-4) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/llvm-3.9_1%3a3.9~+rc1-1~exp1_amd64.deb


cheers,

Andreas


llvm=1%3.6-33_llvm-3.9=1%3.9~+rc1-1~exp1.log.gz
Description: application/gzip

Bug#834075: libvariantslib-ocaml{, -dev}: fails to upgrade from 'sid' - trying to overwrite /usr/lib/ocaml/variantslib/{META, variantslib.a}

[Andreas Beckmann]

Package: libvariantslib-ocaml,libvariantslib-ocaml-dev
Version: 113.33.03-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libvariantslib-ocaml.
  Preparing to unpack .../libvariantslib-ocaml_113.33.03-1_amd64.deb ...
  Unpacking libvariantslib-ocaml (113.33.03-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvariantslib-ocaml_113.33.03-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/ocaml/variantslib/META', which is also in 
package libvariants-camlp4-dev 109.15.03-2
  Selecting previously unselected package libvariantslib-ocaml-dev.
  Preparing to unpack .../libvariantslib-ocaml-dev_113.33.03-1_amd64.deb ...
  Unpacking libvariantslib-ocaml-dev (113.33.03-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvariantslib-ocaml-dev_113.33.03-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/ocaml/variantslib/variantslib.a', which is 
also in package libvariants-camlp4-dev 109.15.03-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libvariantslib-ocaml_113.33.03-1_amd64.deb
   /var/cache/apt/archives/libvariantslib-ocaml-dev_113.33.03-1_amd64.deb


cheers,

Andreas


libvariants-camlp4-dev=109.15.03-2_libvariantslib-ocaml-dev=113.33.03-1.log.gz
Description: application/gzip

Bug#834074: libsexplib-ocaml{, -dev}: fails to upgrade from 'sid' - trying to overwrite /usr/lib/ocaml/sexplib/{META, conv.annot}

[Andreas Beckmann]

Package: libsexplib-ocaml,libsexplib-ocaml-dev
Version: 113.33.03-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libsexplib-ocaml.
  Preparing to unpack .../libsexplib-ocaml_113.33.03-2_amd64.deb ...
  Unpacking libsexplib-ocaml (113.33.03-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libsexplib-ocaml_113.33.03-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/ocaml/sexplib/META', which is also in package 
libsexplib-camlp4-dev 113.00.00-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Selecting previously unselected package libsexplib-ocaml-dev.
  Preparing to unpack .../libsexplib-ocaml-dev_113.33.03-2_amd64.deb ...
  Unpacking libsexplib-ocaml-dev (113.33.03-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libsexplib-ocaml-dev_113.33.03-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/ocaml/sexplib/conv.annot', which is also in 
package libsexplib-camlp4-dev 113.00.00-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libsexplib-ocaml_113.33.03-2_amd64.deb
   /var/cache/apt/archives/libsexplib-ocaml-dev_113.33.03-2_amd64.deb


cheers,

Andreas


libsexplib-camlp4-dev=113.00.00-1_libsexplib-ocaml-dev=113.33.03-2.log.gz
Description: application/gzip

Bug#834073: aptitude search gives less results than apt-cache search

[shirish शिरीष]

Package: aptitude
Version: 0.8.3-1
Severity: normal

Dear Maintainer,
As shared above, aptitude search gives far less results than apt-cache search.

For instance -

[$] aptitude search marathi

p   task-marathi-
Marathi environment
p   task-marathi-desktop-
Marathi desktop

Now let's try the same using either apt-cache or axi-cache

[$] apt-cache search marathi
 [0:07:03]
aspell-mr - Marathi (mr) dictionary for GNU aspell
festival-mr - festival text to speech synthesizer for Marathi language
festvox-mr-nsk - Marathi male speaker for festival
firefox-esr-l10n-mr - Marathi language package for Firefox ESR
iceweasel-l10n-mr - Marathi language package for Iceweasel -
Transitional package
fonts-deva-extra - Free fonts for Devanagari script
fonts-gargi - OpenType Devanagari font
fonts-lohit-deva - Lohit TrueType font for Devanagari script
fonts-nakula - Free Unicode compliant Devanagari font
fonts-sahadeva - Free Unicode compliant Devanagari font
fonts-samyak-deva - Samyak TrueType font for Devanagari script
fonts-sarai - truetype font for devanagari script
gcompris-sound-mr - Indian Marathi sound files for GCompris
hyphen-mr - Marathi hyphenation patterns for LibreOffice
iok - Indic Onscreen Keyboard
kde-l10n-mr - Marathi (mr) localization files for KDE
libreoffice-l10n-mr - office productivity suite -- Marathi language package
task-marathi - Marathi environment
task-marathi-desktop - Marathi desktop
tesseract-ocr-mar - tesseract-ocr language files for Marathi
firefox-l10n-mr - Marathi language package for Firefox

And this is the same search with axi-cache

─[$] axi-cache search marathi

21 results found.
Results 1-20:
100% festvox-mr-nsk - Marathi male speaker for festival
99% task-marathi - Marathi environment
99% task-marathi-desktop - Marathi desktop
98% festival-mr - festival text to speech synthesizer for Marathi language
97% aspell-mr - Marathi (mr) dictionary for GNU aspell
97% firefox-l10n-mr - Marathi language package for Firefox
96% firefox-esr-l10n-mr - Marathi language package for Firefox ESR
96% kde-l10n-mr - Marathi (mr) localization files for KDE
96% hyphen-mr - Marathi hyphenation patterns for LibreOffice
89% gcompris-sound-mr - Indian Marathi sound files for GCompris
89% iceweasel-l10n-mr - Marathi language package for Iceweasel -
Transitional package
85% libreoffice-l10n-mr - office productivity suite -- Marathi language package
84% tesseract-ocr-mar - tesseract-ocr language files for Marathi
80% fonts-lohit-deva - Lohit TrueType font for Devanagari script
80% fonts-deva-extra - Free fonts for Devanagari script
79% fonts-gargi - OpenType Devanagari font
79% fonts-samyak-deva - Samyak TrueType font for Devanagari script
79% fonts-sarai - truetype font for devanagari script
78% fonts-nakula - Free Unicode compliant Devanagari font
78% fonts-sahadeva - Free Unicode compliant Devanagari font
More terms: devanagari hindi sanskrit konkani kashmiri sindhi maithili
More tags: accessibility::speech suite::debian role::app-data
role::metapackage sound::speech made-of::audio accessibility::input
`axi-cache more' will give more results

And this is without updating apt-xapian-index .

There is possibility that there is something that I may have missed
although I did search the debian bts (bugs.debian.org/aptitude) as
well as scanned the whole of aptitude manual in order to see if I
missed something about some index updation or something else but came
up empty.

Look forward to answers.

-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.3
Compiler: g++ 6.1.1 20160802
Compiled against:
  apt version 5.0.0
  NCurses version 6.0
  libsigc++ version: 2.8.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20160625
  cwidget version: 0.5.17
  Apt version: 5.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffca1bbc000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
(0x7fe327f86000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fe327d56000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7fe327b2b000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
(0x7fe327924000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3
(0x7fe327627000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
(0x7fe327322000)
libboost_iostreams.so.1.61.0 =>
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.61.0
(0x7fe32710a000)
libboost_filesystem.so.1.61.0 =>
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.61.0
(0x7fe326ef1000)
libboost_system.so.1.61.0 =>
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.61.0
(0x7fe326cec000)
libxapian.so.22 

Bug#833820: sphinx: Avoid evaulating default function arguments when including them in the documentation

[Dmitry Shachnev]

Control: forwarded -1 https://github.com/sphinx-doc/sphinx/issues/2844

Hi Petter,

On Tue, Aug 09, 2016 at 01:08:23AM +0200, Petter Reinholdtsen wrote:
> Hi.  The documentation generated by sphinx expands default python
> arguments instead of reproducing the values listed in the source.

Thanks for the bug report. Indeed such behavior is not only breaking the
reproducible builds, but also a bit misleading.

However I think this may be non-trivial to fix, as Sphinx tries to import
the module, rather than parse it, and Python evaluates the arguments during
module import.

The same result (evaluated argument) can be seen if you call the built-in
help() against that function.

Speaking about your example, I would recommend against using such functions
at all: the default argument of that function is module *import* time,
not the actual time when it is executed; this is not what one may expect.

In any case, I have forwarded this bug to upstream developers, let's see
what they think about it.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#833798: krb5: FTBFS with -O3: uninitialized variables

[Steve Langasek]

On Thu, Aug 11, 2016 at 01:57:11PM -0400, Benjamin Kaduk wrote:
> On Tue, 9 Aug 2016, Benjamin Kaduk wrote:

> > I guess I can take responsibility for telling upstream about it, since no
> > one seems to have done so yet :-/

> Upstream would prefer a different patch, something like
> https://github.com/kaduk/krb5/commit/16430a78dd6e909af74ec1a9aa48724c6d57db3f
> .  Steve, can you test whether that still quiets the ppc64el build?

Well, gcc -O3 should give you the same answer anywhere, not just on ppc64el
:)  Yes, I can confirm that the above patch also fixes the build failure
(after fixing the syntax error in the patch to src/tests/asn.1/trval.c).

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature