Bug#862243: unblock: linux/4.9.25-1

2017-05-12 Thread Niels Thykier
Salvatore Bonaccorso:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hi
> 
> Please unblock package linux
> 

Ok with me, CC'ing KiBi for a d-i ack.

> The update includes stable releases 4.9.19 up to 4.9.25 with many
> improvements, bugfixes, security issues fixed. On top of the stable
> release the following additional changes were made:
> 
>>   [ Ben Hutchings ]
>>   * w1: Really enable W1_MASTER_GPIO as module (Closes: #858975)
>>   * debian/rules.real: Undefine $LANGUAGE, which can break debug symbols for
>> vDSOs (Closes: #859807)
>>   * Bump ABI to 3
>>   * [s390x] Set NR_CPUS=256 (Closes: #858731)
>>   * [x86] usbip: Increase USBIP_VHCI_NR_HCS to 8 and USBIP_VHCI_HC_PORTS to 
>> 31
>> (Closes: #859641)
>>   * [powerpc/powerpc64,ppc64*] target: Enable SCSI_IBMVSCSIS as module
>>   * cpupower: Fix turbo frequency reporting for pre-Sandy Bridge cores
>> (Closes: #859978)
>>   * udeb: Include all AHCI drivers in sata-modules (Closes: #860335)
>>   * [powerpc/powerpc64,ppc64] Set NR_CPUS=2048, matching ppc64el
>>   * [powerpc*/*64*] Enable CPUMASK_OFFSTACK to reduce stack usage
>>   * [mips*el/loongson-3] Set NR_CPUS=16 to allow for Loongson 3B2000
>>   * [mips*/octeon] Set NR_CPUS=64 to allow for Cavium CN7890
>>   * [arm64] Set NR_CPUS=256 to allow for multi-SoC systems (Closes: #861209)
>>   * [powerpc/powerpc-smp,powerpcspe] Explicitly set NR_CPUS=4
>>   * Move debug symbols back to the main archive, to avoid problems with the
>> current handling in dak
>>   * linux-image: Disable signing until it's supported in dak
>>   * [rt] Update to 4.9.20-rt16:
>> - rtmutex: Make lock_killable work
>> - rtmutex: Provide rt_mutex_lock_state()
>> - rtmutex: Provide locked slowpath
>> - rwsem/rt: Lift single reader restriction
>>   * PCI: Enable PCIE_PTM (except on armel/marvell)
>>   * 6lowpan: Enable Generic Header Compression modules
>>   * net/sched: Enable NET_ACT_SKBMOD as module
>>   * ethernet: Enable NFP_NETVF as module
>>   * net/phy: Enable MICROSEMI_PHY as module
>>   * input/tablet: Enable TABLET_USB_PEGASUS as module
>>   * [x86] input/touchscreen: Enable TOUCHSCREEN_SURFACE3_SPI as module
>>   * serial/8250: Enable SERIAL_8250_MOXA as module
>>   * [x86] gpio: Enable GPIO_AMDPT as module
>>   * [x86] thermal: Enable INT3406_THERMAL as module
>>   * watchdog: Enable WATCHDOG_SYSFS
>>   * integrity: Enable IMA, IMA_DEFAULT_HASH_SHA256, IMA_APPRAISE,
>> IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY, IMA_BLACKLIST_KEYRING
>> (except on armel/marvell) (Closes: #788290)
>>   * media: Enable VIDEO_TW5864, VIDEO_TW686X as modules
>>   * [x86] amdgpu,sound/soc: Enable DRM_AMD_ACP; enable SND_SOC_AMD_ACP as 
>> module
>>   * hda: Set SND_HDA_PREALLOC_SIZE=2048 as recommended for PulseAudio
>>   * HID: Enable HID_SENSOR_CUSTOM_SENSOR as module
>>   * leds,USB: Enable USB_LEDS_TRIGGER_USBPORT as module
>>   * usbip: Enable USBIP_VUDC as module
>>   * USB/misc: Enable UCSI as module
>>   * leds: Enable LEDS_TRIGGER_DISK, LEDS_TRIGGER_MTD, LEDS_TRIGGER_PANIC
>>   * IB: Enable INFINIBAND_HFI1, INFINIBAND_I40IW, INFINIBAND_QEDR, RDMA_RXE
>> as modules
>>   * [amd64] EDAC: Enable EDAC_SKX as module
>>   * [x86] comedi: Enable COMEDI_ADV_PCI1720, COMEDI_ADV_PCI1760 as modules
>>   * [x86] platform: Enable INTEL_HID_EVENT as module
>>   * [x86] hwtracing: Enable INTEL_TH, INTEL_TH_PCI, INTEL_TH_GTH, 
>> INTEL_TH_MSU,
>> INTEL_TH_PTI as modules
>>   * [rt] tracing: Enable HWLAT_TRACER
>>   * [x86] crypto: Enable CRYPTO_DEV_QAT_C3XXX, CRYPTO_DEV_QAT_C62X,
>> CRYPTO_DEV_QAT_C3XXXVF, CRYPTO_DEV_QAT_C62XVF as modules
>>   * crypto: Enable CRYPTO_DEV_CHELSIO as module
>>   * [arm64] Enable ARMV8_DEPRECATED, SWP_EMULATION, CP15_BARRIER_EMULATION,
>> SETEND_EMULATION (Closes: #861384)
>>   * udeb: Add tifm_7xx1 to mmc-modules (Closes: #861195)
>>   * leds: Enable LEDS_GPIO as module for all configurations with GPIOs
>> (Closes: #860569)
>>   * selinux: Set SECURITY_SELINUX_CHECKREQPROT_VALUE=0, per default.
>> This may break some old applications if SELinux is enabled, and can be
>> reverted using the kernel parameter: checkreqprot=1
>>   * udeb: Move mfd-core to kernel-image, as both input-modules and
>> mmc-modules need it
>>   * crypto: Change CRYPTO_SHA256 from module to built-in, as required by IMA
>> .
>>   [ Salvatore Bonaccorso ]
>>   * ping: implement proper locking (CVE-2017-2671)
>>   * macsec: avoid heap overflow in skb_to_sgvec (CVE-2017-7477)
>>   * macsec: dynamically allocate space for sglist
>>   * nfsd: check for oversized NFSv2/v3 arguments (CVE-2017-7645)
>>   * nfsd4: minor NFSv2/v3 write decoding cleanup
>>   * nfsd: stricter decoding of write-like NFSv2/v3 ops (CVE-2017-7895)
>> .
>>   [ Aurelien Jarno ]
>>   * [mips*/octeon] Drop obsolete patch adding support for the UBNT E200
>> board.
>>   * [mips*el/loongson-3] Disable PAGE_EXTENSION and 

Bug#862410: unblock: mysql-transitional/5.5.9999+default

2017-05-12 Thread Ondřej Surý
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package mysql-transitional

Dear release team,

as agreed upon in <7f872a85-0d08-6bd1-f731-52e26a769...@thykier.net>
the MySQL packaging team needs to upload src:mysql-transitional
directly into stretch to fix the smooth upgrade issues.

This goes hand in hand with mariadb-10.1_10.1.23-7 update, but I'll
update the existing unblock bug separately.

unblock mysql-transitional/5.5.+default

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.4.0-67-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#862408: Xen should trigger reboot-required notification on hypervisor upgrade

2017-05-12 Thread Sébastien Chaumat
Source: xen
Package: xen-hypervisor-4.4-amd64
Version:  4.4.1-9+deb8u8

When the xen hypervisor is updated there's no specific indication that the
system should be rebooted whereas this is as important to notify as a
kernel upgrade.

 I suggest the xen-hypervisor*.postinst calls :
/usr/share/update-notifier/notify-reboot-required

 Thanks,
Sébastien


Bug#862409: Concurrent gem2deb processes fail updating packages cache

2017-05-12 Thread Dominic Cleal
Package: gem2deb
Version: 0.30.1
Tags: patch

When two gem2deb processes are executed by the same user concurrently
(e.g. in a CI system building many packages), the Gem2Deb::DhMakeRuby
class can raise an error when updating its gem_to_package_data cache:

-- Creating Debian source package from ./apipie-bindings-0.2.0.tar.gz ...
/usr/lib/ruby/vendor_ruby/gem2deb/dh_make_ruby.rb:149:in `stat': No such
file or directory @ rb_file_s_stat -
/home/jenkins/.cache/gem2deb/gem_to_packages.yaml.new (Errno::ENOENT)
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_make_ruby.rb:149:in
`generate_or_update_gem_to_package_data'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_make_ruby.rb:66:in 
`initialize'
from ../../gem2deb:96:in `new'
from ../../gem2deb:96:in `'

It appears that both processes might be running the `apt-file` command,
redirecting into the same .new file and then only one succeeds in moving
the file, while the other fails to either stat or mv it.

Patch against version 0.33.1 attached, which uses a separate temporary
cache file per process, so it doesn't matter if another process is also
updating the same cache.

-- 
Dominic Cleal
domi...@cleal.org
--- lib/gem2deb/dh_make_ruby.rb.orig	2017-05-12 13:21:53.381044007 +0100
+++ lib/gem2deb/dh_make_ruby.rb	2017-05-12 13:23:06.368255601 +0100
@@ -144,11 +144,11 @@
   end
 
   if update
-new_cache = cache + '.new'
+new_cache = cache + ".new.#{$$}"
 if system('apt-file search /usr/share/rubygems-integration/ > ' + new_cache)
   if File.stat(new_cache).size > 0
 system('sed', '-i', '-e', 's#/.*/##; s/-[0-9.]\+.gemspec//', new_cache)
-FileUtils.mv(cache + '.new', cache)
+FileUtils.mv(new_cache, cache)
   else
 puts 'E: dh-make-ruby needs an up-to-date apt-file cache in order to map gem names'
 puts 'E: to package names but apt-file has an invalid cache. Please run '


Bug#861484: llvm-toolchain-3.8: Fix R_AARCH64_MOVW_UABS_G3 relocation

2017-05-12 Thread Graham Inggs

The one line fix on its own:

-*TargetPtr |= Result >> (48 - 5);
+*TargetPtr |= (Result & 0xULL) >> (48 - 5);

...allows julia from the archive to run on my Raspberry Pi 3.
Building julia now also succeeds.

On 11/05/2017 20:42, Edmund Grimley Evans wrote:

There is probably no need to rebuild julia when the LLVM bug has been fixed,
but you should probably check that with someone who properly understands
how julia works.


Julia needs to be rebuilt on arm64 for the LLVM versioned symbols 
transition (see #849098) anyway.


This line of code is still present in LLVM 3.9.1 (and 3.7 and 3.5), but 
seems to be fixed in 4.0 (thanks jcristau and bunk for checking).


Unfortunately, this one line fix does not solve the problem of the LLVM 
build hanging during the sanitizer tests.


Both issues appeared around the same time and seem to be linked to 
specific kernel versions.  In Ubuntu, both julia and llvm-toolchain-3.8 
built in late March with Ubuntu's 4.4.0-66-generic kernel.  In late 
April, the next build of llvm-toolchain-3.8 failed with kernel 
4.4.0-72-generic and a few days later, the next build of julia failed 
with kernel 4.4.0-77-generic.




Bug#845938: pulseaudio: It doesn't since last update of Debian Testing (11-05-2017)

2017-05-12 Thread Bertrand Pinlet
Package: pulseaudio
Version: 10.0-1
Followup-For: Bug #845938

Dear Maintainer,


   * What led up to the situation?



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64
 (x86_64)

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

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-10
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.18-1
ii  libgcc1  1:6.3.0-17
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.27-2
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-17
ii  libsystemd0  232-23
ii  libtdb1  1.3.11-2
ii  libudev1 232-23
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4+b1

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-3+b3
pn  pavumeter
ii  udev 232-23

-- Configuration Files:
/etc/pulse/default.pa changed:
.fail
load-module module-switch-on-connect
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
load-module module-augment-properties
load-module module-switch-on-port-available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
load-module module-detect
.endif
.ifexists module-jackdbus-detect.so
.nofail
load-module module-jackdbus-detect channels=2
.fail
.endif
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.endif
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix
.ifexists module-gconf.so
.nofail
load-module module-gconf
.fail
.endif
load-module module-default-device-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-intended-roles
load-module module-suspend-on-idle
.ifexists module-console-kit.so
load-module module-console-kit
.endif
.ifexists module-systemd-login.so
load-module module-systemd-login
.endif
load-module module-position-event-sounds
load-module module-role-cork
load-module module-filter-heuristics
load-module module-filter-apply


-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should 

Bug#862186: unblock: cryptsetup/2:1.7.3-4

2017-05-12 Thread Niels Thykier
Guilhem Moulin:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hi there,
> 
> cryptsetup/2:1.7.3-4 closes RC bug #861074.  Quoting myself from Message
> #15,
> 
> initramfs-tools 0.130 landed into testing on May 1st, and as of
> 2:1.7.3-3 the cryptroot hook doesn't detect resume devices with the
> new logic from initramfs-tools >=0.129:
> 
>   * setting RESUME under in an initramfs-tools configuration file
> other than /etc/initramfs-tools/conf.d/resume isn't supported
>   * setting RESUME=none yields a (harmless) warning
>   * setting RESUME=auto (or leaving the variable undefined) might
> result into an unresumable device: the initrd is then configured
> to resume from the largest swap partition, which might not be
> unlocked in time
> 
> 2:1.7.3-4 also closes #861802 (license mismatch) as well as #847620
> (drop obsolete update-rc.d parameters).  Debdiff attached.
> 
> Thanks for considering its inclusion in Stretch!
> Cheers,
> 

Ack from here, CC'ing KiBi for a d-i ack.

Thanks,
~Niels



Bug#862407: unblock: epiphany-browser/3.22.7-1

2017-05-12 Thread Jeremy Bicha
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package epiphany-browser

3.22.7 is the latest bugfix release in the stable 3.22 series and is
highly recommended by the Epiphany developers for distros that ship
epiphany 3.22. (It is included in Ubuntu 16.10, Fedora 25, etc.).
According to the NEWS file, this version fixes a crash, memory
corruption issues, and critical warnings.

The Debian Developer who uploaded this version supports my filing an
unblock request for it.

https://git.gnome.org/browse/epiphany/log/?h=gnome-3-22

unblock epiphany-browser/3.22.7-1

Thanks,
Jeremy Bicha


epiphany-browser_3.22.7-1.debdiff
Description: Binary data


Bug#862295: unblock: v4l-utils/1.12.5-1

2017-05-12 Thread Niels Thykier
Control: tags -1 moreinfo

Gregor Jasny:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package v4l-utils
> 
> Hello,
> 
> please unblock the latest stable version of v4l-utils 1.12. It fixes
> a crash in the Digital Video Broadcasting (DVB) library that occurs
> when a German DVB-T2 transport stream is parsed. Additionally it fixes
> a bug where identical transport streams were not detected as such.
> 
> Thanks,
> Gregor
> 
> [...]
> diff -Nru v4l-utils-1.12.3/lib/include/libdvbv5/desc_t2_delivery.h 
> v4l-utils-1.12.5/lib/include/libdvbv5/desc_t2_delivery.h
> --- v4l-utils-1.12.3/lib/include/libdvbv5/desc_t2_delivery.h  2017-01-22 
> 18:33:34.0 +0100
> +++ v4l-utils-1.12.5/lib/include/libdvbv5/desc_t2_delivery.h  2017-05-10 
> 20:21:39.0 +0200
> @@ -45,10 +45,14 @@
>   *
>   * @param cell_id_extension  cell id extension
>   * @param transposer_frequency   transposer frequency
> + *
> + * NOTE: This struct is deprecated and will never be filled. All
> + * subcell transposer frequencies will be added to
> + * dvb_desc_t2_delivery::centre_frequency array.
>   */
>  struct dvb_desc_t2_delivery_subcell {
>   uint8_t cell_id_extension;
> - uint16_t transposer_frequency;
> + uint16_t transposer_frequency;  // Should be 32 bits, instead
>  } __attribute__((packed));
>  
>  /**
> @@ -65,7 +69,8 @@
>   * @param other_frequency_flag   other frequency flag
>   * @param tfs_flag   tfs flag
>   *
> - * @param centre_frequency   centre frequency vector
> + * @param centre_frequency   centre frequency vector, for all cell and
> + *   subcel ID's
>   * @param frequency_loop_length  size of the 
> dvb_desc_t2_delivery::centre_frequency
>   *   vector
>   *
> @@ -86,13 +91,15 @@
>   uint16_t transmission_mode:3;
>   uint16_t guard_interval:3;
>   uint16_t reserved:2;
> - uint16_t bandwidth:3;
> + uint16_t bandwidth:4;
>   uint16_t SISO_MISO:2;
>   } __attribute__((packed));

Doesn't this change break the ABI?

> [...]
> diff -Nru v4l-utils-1.12.3/lib/libdvbv5/descriptors/desc_t2_delivery.c 
> v4l-utils-1.12.5/lib/libdvbv5/descriptors/desc_t2_delivery.c
> --- v4l-utils-1.12.3/lib/libdvbv5/descriptors/desc_t2_delivery.c  
> 2017-01-22 18:33:34.0 +0100
> +++ v4l-utils-1.12.5/lib/libdvbv5/descriptors/desc_t2_delivery.c  
> 2017-05-10 20:21:39.0 +0200
> [...]
> @@ -40,53 +40,76 @@
> [...]
> + d->frequency_loop_length += n;
> + d->centre_frequency = realloc(d->centre_frequency,
^^

Smells very much like the common "realloc memory leak on error" bug
(Usually cppcheck can spot this kind of bug).  Not sure how long lived
that leak is, but fixing it might be faster than figuring it out.

> +   d->frequency_loop_length * 
> sizeof(*d->centre_frequency));
> + if (!d->centre_frequency) {
> + dvb_logerr("%s: out of memory", __func__);
> + return -3;
> + }
> [...]
> + // Add transposer_frequency at centre_frequency table
> + d->frequency_loop_length++;
> + d->centre_frequency = realloc(d->centre_frequency,


Same, except ...

> +   d->frequency_loop_length 
> * sizeof(*d->centre_frequency));
> + memcpy(>centre_frequency[pos], p, 
> sizeof(*d->centre_frequency));
   ^

No check for an error (inconsistent with the previous realloc of same field)

> [...]
> 
> unblock v4l-utils/1.12.5-1
> 
> [...]
> 

Please clarify the possible ABI breakage situation and resolve the above
issues.

Thanks,
~Niels



Bug#862328: clang-4.0: ClangConfig.cmake is broken by Debian packaging

2017-05-12 Thread Sylvain Joubert
Package: clang-4.0
Version: 1:4.0.1~+rc1-1
Followup-For: Bug #862328

Hi,

After some digging, here is what I've come up with:

1- Dependencies

I think that ClangConfig.cmake (and the symlinks,... described above) and its
two sibling files should be provided by libclang-x.y-dev not by clang-x.y.
Most of the targets provided by this CMake file are installed with
libclang-x.y-dev so that makes much more sense (and LLVMConfig.cmake is
provided by llvm-x.y-dev)
However, some target artifacts are provided by other packages as well:
- clang (executable) by clang-x.y
- clang-format (executable) by clang-format-x.y

If these artifacts are not installed during configure, CMake will error-
complain about that.
I'm not really sure what's the best approach here but, as is, the package
providing ClangConfig.cmake must depends on clang-x.y and clang-format-x.y in
order to work.

2- Fixing find_package(Clang)

Install ClangConfig.cmake and siblings in /usr/lib/llvm-x.y/lib/cmake/clang
(instead of /usr/share/llvm-x.y/cmake)
Add a symlink /usr/share/clang-x.y/cmake -> /usr/lib/llvm-x.y/lib/cmake/clang

This matches what's done for LLVMConfig.cmake
This way find_package(Clang) can automatically find the config files.
To be consistent with LLVMConfig.cmake the symlink can instead be put in
/usr/lib/clang-x.y/cmake

3- Fixing CLANG_INSTALL_PREFIX

Apply the attached patch (fix-cmake-clang-confix.patch based on the 5.0
snapshot) to ClangConfig.cmake in the clang sources to fix the prefix location

With that ClangConfig.cmake and siblings can correctly compute the path of the
target artifacts

4- Fixing clang executable name

The targets files expect the clang executable to be named and located in
/usr/lib/llvm-x.y/bin/clang-x.y but the rules file (line 374) strips its
version suffixes.

I'm not sure why this was done but I guess we can either:
- not rename the executable (and fix /usr/bin/clang-x.y symlink and maybe
others)
- fix the ClangTargets-*.cmake file post generation to strip the version suffix


With these changes, one should be able to use the provided ClangConfig.cmake
and its targets.
I'm not really able to test that much more, nor provide a full patch for the
packaging repo but I can test any .deb that would have such fixes (including
the 5.0 snapshots).

Regards,
Sylvain



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'stable-updates'), (800, 'stable'), (700, 
'unstable'), (90, 'experimental')
Architecture: amd64
 (x86_64)

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

Versions of packages clang-4.0 depends on:
ii  binutils 2.28-4
ii  libc62.24-10
ii  libc6-dev2.24-10
ii  libclang-common-4.0-dev  1:4.0.1~+rc1-1
ii  libclang1-4.01:4.0.1~+rc1-1
ii  libgcc-6-dev 6.3.0-16
ii  libgcc1  1:6.3.0-16
ii  libjsoncpp1  1.7.4-3
ii  libllvm4.0   1:4.0.1~+rc1-1
ii  libobjc-6-dev6.3.0-16
ii  libstdc++-6-dev  6.3.0-16
ii  libstdc++6   6.3.0-16

Versions of packages clang-4.0 recommends:
ii  llvm-4.0-dev  1:4.0.1~+rc1-1
ii  python2.7.13-2

Versions of packages clang-4.0 suggests:
pn  clang-4.0-doc  
pn  gnustep
pn  gnustep-devel  

-- no debconf information
diff --git a/cmake/modules/CMakeLists.txt b/cmake/modules/CMakeLists.txt
index be6d1d7257..b97afbf7c0 100644
--- a/cmake/modules/CMakeLists.txt
+++ b/cmake/modules/CMakeLists.txt
@@ -28,16 +28,7 @@ set(CLANG_CONFIG_LLVM_CMAKE_DIR)
 set(CLANG_CONFIG_EXPORTS_FILE)
 
 # Generate ClangConfig.cmake for the install tree.
-set(CLANG_CONFIG_CODE "
-# Compute the installation prefix from this LLVMConfig.cmake file location.
-get_filename_component(CLANG_INSTALL_PREFIX \"\${CMAKE_CURRENT_LIST_FILE}\" 
PATH)")
-# Construct the proper number of get_filename_component(... PATH)
-# calls to compute the installation prefix.
-string(REGEX REPLACE "/" ";" _count "${CLANG_INSTALL_PACKAGE_DIR}")
-foreach(p ${_count})
-  set(CLANG_CONFIG_CODE "${CLANG_CONFIG_CODE}
-get_filename_component(CLANG_INSTALL_PREFIX \"\${CLANG_INSTALL_PREFIX}\" 
PATH)")
-endforeach(p)
+set(CLANG_CONFIG_CODE "set(CLANG_INSTALL_PREFIX \"${CMAKE_INSTALL_PREFIX}\")")
 set(CLANG_CONFIG_CMAKE_DIR 
"\${CLANG_INSTALL_PREFIX}/${CLANG_INSTALL_PACKAGE_DIR}")
 set(CLANG_CONFIG_LLVM_CMAKE_DIR 
"\${CLANG_INSTALL_PREFIX}/${LLVM_INSTALL_PACKAGE_DIR}")
 set(CLANG_CONFIG_EXPORTS_FILE "\${CLANG_CMAKE_DIR}/ClangTargets.cmake")


Bug#862406: RM: ears/1.0.1-2.1

2017-05-12 Thread Adrian Bunk
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Control: tags -1 jessie

#786338 ears: broken since python-musicbrainz has been removed

I can reproduce that none of the commands works in jessie,
despite the dependency python-musicbrainz2 being installed.

It seems the #628475 "fix" changed the dependency from
python-musicbrainz to python-musicbrainz2 without any
conversion to make it also work with python-musicbrainz2.



Bug#793631: workaround

2017-05-12 Thread martin f krafft
Just a quick note, here's a workaround for jessie:

cat <<_eof > /etc/udev/rules.d/65-md-raid-blkid-HACK_FOR_JESSIE.rules
SUBSYSTEM!="block", GOTO="md_hack_end"
ACTION!="add|change", GOTO="md_hack_end"
KERNEL!="md*", GOTO="md_hack_end"
IMPORT{builtin}="blkid"
LABEL="md_hack_end"
_eof
udevadm control --reload

Remove it after upgrade to stretch, although it also won't hurt much
if it stays around.

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)


Bug#862389: X gets locked up after several switches to VT

2017-05-12 Thread Łukasz Stelmach
I've rebuilt lightdm 1.18.3-1 from Stretch on my Jessie desktop and
after a few VT-to-X switches some data is still stuck between lightdm
and X.

--8<---cut here---start->8---
Netid  State  Recv-Q Send-Q   Local Address:Port   Peer Address:Port   
u_str  ESTAB  3840* 20164523   * 
20167969 users:(("lightdm",pid=21965,fd=11))
u_str  ESTAB  0  9216   @/tmp/.X11-unix/X0 20167969   * 
20164523 users:(("Xorg",pid=21969,fd=18))
--8<---cut here---end--->8---

-- 
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics


signature.asc
Description: PGP signature


Bug#862291: closed by Thomas Goirand <z...@debian.org> (Re: Bug#862290: Version displayed 2.5, but version packaged 2.6)

2017-05-12 Thread Stéphane Aulery

hi Thomas,

Le 11/05/2017 22:24, Thomas Goirand a écrit :

On 05/11/2017 05:03 PM, Stéphane Aulery wrote:


I expect to control a rotation for each periodicity. It's supported in
V. 3.0, so I have installed and configured it by myself.

But if it is packaged it's better.

Upstream seems dead. I have sent a mail yesterday, offering to become
the maintainer.

Is the packaging of a new upstream version excluded for you?

In that case it would be better to change it's name because it's a
noiseless fork.


If someone is able to recover all the functionalities added to the
Debian package to the version 3.0, then I'll happily package that.
However, I don't have time to do it myself, and also, Stretch is frozen
so it will only be possible to upload to Experimental until the 
release.


I leave it to the developer to react and if nothing happens,
I will consider the forker and how to integrate your improvements
in version 3.0.

Cheers,

--
Stéphane Aulery



Bug#862405: libjson-xs-perl: dropped support for to_json

2017-05-12 Thread Dominic Hargreaves
Package: libjson-xs-perl
Version: 3.030-1
Severity: important

3.0 (released 2013) removed to_json/from_json with no further
information given
(https://sources.debian.net/src/libjson-xs-perl/3.030-1/Changes/#L40)

This seems to break a documented interface of libjson-perl's if installed.
I don't know the full history but it seems that there are other known
issues with JSON::XS not working nicely with JSON, and the recommendation
is to not use it at all.

https://rt.cpan.org/Public/Bug/Display.html?id=94784

This was observed with #848041 in request-tracker4. I'm honestly not sure
about the best route forward on that ticket; looking at the rdeps of
libjson-xs-perl, Conflicting on it may be too invasive...

Thoughts welcomed!

Dominic.



Bug#862404: pwauth : binary is executable by "other"

2017-05-12 Thread Laurent Bonnaud
Package: pwauth
Version: 2.3.11-0.2


Dear maintainer,

the pwauth binary is installed with the following permissions:

-rwsr-xr-x 1 root www-data 10232 sept. 25  2016 /usr/sbin/pwauth

If it is intended to be used by web servers only, shouldn't permissions be

-rwsr-x--- 1 root www-data 10232 sept. 25  2016 /usr/sbin/pwauth

instead ?

-- 
Laurent.



Bug#862023: [Qa-jenkins-dev] Bug#862023: reproducible-builds.org: don't mark packages as FTBFS when they fail on the second try

2017-05-12 Thread Holger Levsen
Hi Ivo,

On Sun, May 07, 2017 at 04:27:09PM +0200, Ivo De Decker wrote:
> It would be nice if these failures were displayed in a different way than
> packages that don't build at all, even on the first attempt. 

why? 

They do fail to build…

So instead I could rather imagine to use a note/issue here: 
first_build_succeeded_but_2nd_not or such and then automatically
detect and set them…

> Maybe just
> 'FTBFS2' instead of 'FTBFS'?

besides that I'm really not sure about the benefits, we have lots of other
work on our todo, eg rebuilding against ftp.debian.org instead of our 
own builds (and also integrating other distros in the setup) and this
change would also require internal changes (think db) too…


-- 
cheers,
Holger


signature.asc
Description: Digital signature


Bug#862071: Bug#861591: Bug#862071: password-store: FTBFS when built in a path with >= 74 characters

2017-05-12 Thread Niels Thykier
Control: tags -1 stretch-ignore

intrigeri:
> Dominic Hargreaves:
>> Please could you rule on whether the above class of bugs should be RC
>> for stretch? It doesn't seem productive at this late stage.
> 
> Indeed: I'll be happy to fix that in Buster or in a Stretch
> point-release (also because I've noticed it breaks autopkgtests for
> some packages of "mine"), but IMO this shouldn't block the Stretch
> release, so a stretch-ignore tag would seem suitable to me.
> 
> Cheers,
> 

Definitely RC, happy to see a fix in stretch, but I agree it is deferrable.

Thanks,
~Niels



Bug#849366: FW: Bug#849366: Acknowledgement (Debian8.2 cannot handle memory hot-add)

2017-05-12 Thread Roger Shimizu
On Fri, 12 May 2017 07:23:57 +
Yanhui He  wrote:

> Hi,
> 
> I have tested Debian 9.0 RC3 memory hot-adding and the problem is still 
> existed.
> 
> Would you please help me take a look?

Please avoid top-posting.
If you report kernel bug, please use "reportbug kernel" command. [0]

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

For the specific problem you report, could you inform what upstream
patch can support that feature? Thank you!

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


pgpRFc1gsj2ul.pgp
Description: PGP signature


Bug#862403: RFP: paper-gtk-theme -- modern desktop GTK2/GTK3 theme suite

2017-05-12 Thread nodiscc
Package: wnpp
Severity: wishlist

* Package name : paper-gtk-theme
  Version : v2.1.0
  Upstream Author : Sam Hewitt 
* URL : http://snwh.org/paper
* License : GPL
  Programming Lang: CSS
  Description : Modern desktop GTK2/GTK3 theme suite

Source: https://github.com/snwh/paper-gtk-theme

Paper is a modern desktop theme suite. Its
design is mostly flat with a minimal use of shadows for depth. Its design is 
mostly flat

RFP for the assorted icon theme, from the same author:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802505



Bug#860169:

2017-05-12 Thread Angel Abad
If you execute glue-sprite on terminal:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
655, in _build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
963, in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
854, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (Jinja2 2.9.5
(/usr/lib/python3/dist-packages), Requirement.parse('Jinja2<2.8,>=2.7'),
{'glue'})

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/glue-sprite", line 5, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3019, in 
@_call_aside
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3003, in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3032, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
657, in _build_master
return cls._build_from_requirements(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
670, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
849, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'Jinja2<2.8,>=2.7' distribution was
not found and is required by glue

-- 
Angel Abad
an...@debian.org | angela...@ubuntu.com | angela...@gmail.com
http://www.pastelero.net
FPR: 4A08 9719 1621 CCF7 FBEE  F752 A6D5 8816 010A 1096


Bug#862248: [Debian-ha-maintainers] Bug#862248: No straightforward and permanent way to disable DRBD autostart, no drbd systemd unit file

2017-05-12 Thread Apollon Oikonomopoulos
On 09:54 Fri 12 May , Christian Balzer wrote:
> On Thu, 11 May 2017 09:33:59 +0300 Apollon Oikonomopoulos wrote:
> 
> > On 09:15 Thu 11 May , Christian Balzer wrote:
> > > Firstly I recreated the initial state bu unmasking drbd and enabling 
> > > it, > then reloading systemd.
> > > 
> > > That find then gives us:
> > > ---
> > > /run/systemd/generator.late/drbd.service
> > > /etc/systemd/system/multi-user.target.wants/drbd.service  
> > 
> > So, now we need ls -l 
> > /etc/systemd/system/multi-user.target.wants/drbd.service to see how old 
> > the symlink is and where it points to. Can you also zgrep drbd-utils 
> > /var/log/dpkg.log*?
> > 
> 
> 
> Sure thing, that's quite the old chestnut indeed:
> ---
> lrwxrwxrwx 1 root root 32 Aug 11  2015 
> /etc/systemd/system/multi-user.target.wants/drbd.service -> 
> /lib/systemd/system/drbd.service
> ---
> 
> Note that this link is also present on:
> A Wheezy system with "8.9.2~rc1-1~bpo70+1" installed.
> On a system that was initially installed with Jessie but had
> 8.9.2~rc1-2+deb8u1 installed first.
> The plot thickens, see below.

Yes, it makes prefect sense. This is what happened:

We were originally shipping a systemd unit since 8.4.4-1 and up to 
8.9.5-1, where the systemd unit was dropped as it didn't make much 
sense, at least in the way it was implemented.

Now, the symlinks under /etc/systemd/system/multi-user.target.d which 
are created by systemctl enable/update-rc.d enable are only cleaned up 
during package *purge*. So, when you had a version with the systemd unit 
and upgraded to a version without it, the symlink would still be there, 
while the unit file itself would not be there.

So, what should be done in the package actually is invoke 

 deb-systemd-helper purge drbd.service

in drbd-utils.postinst iff upgrading from versions that had a systemd 
unit in place.

There's an additional problem here: upstream's initscript does not have 
any Default-Start runlevels, as upstream doesn't suggest enabling the 
initscript by default. This however causes update-rc.d (and systemctl 
enable) to shortcircuit the action by default:

 # update-rc.d drbd disable
 update-rc.d: error: drbd Default-Start contains no runlevels, aborting.

To recap: we need to properly clean up systemd's symlinks to the 
obsolete service file *and* fix the initscript to contain Default-Start 
levels. I would also consider disabling the service by default on new 
installations, as this is what upstream also recommends.

Ideas?

Cheers,
Apollon



Bug#862402: RFP: ceti-2-theme -- theme for GTK 3, GTK 2 and Gnome-Shell

2017-05-12 Thread nodiscc
Package: wnpp
Severity: wishlist

* Package name: ceti-2-theme
  Version : 20150923
  Upstream Author : Horst3180 
* URL : https://github.com/horst3180/ceti-2-theme
* License : GPL
  Programming Lang: CSS
  Description : theme for GTK 3, GTK 2 and Gnome-Shell

Ceti-2 is a theme for GTK 3, GTK 2 and Gnome-Shell. It supports GTK 3 and GTK 2 
based
desktop environments like Gnome, Unity, Budgie, Pantheon, etc.

This GTK theme is from the same author as 
https://packages.debian.org/sid/arc-theme



Bug#862401: unblock: kwidgetsaddons/5.28.0-3

2017-05-12 Thread Maximiliano Curia
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

I've recently uploaded kwidgetsaddons in order to fix #860515, as apparently 
the 5.28 version failed to update update the French translation. It seems that 
there are some other pending issues in the qt translations that made the 
problem difficult to diagnose.

The debdiff is 258k, so I'm publishing it in:
 https://freak.gnuservers.com.ar/~maxy/debian/kwidgetsaddons_5.28.0-3_unblock/

The change per se is importing the po files from the 5.29 version.

The package is currently in sid and has already built in all the release 
architectures.

Happy hacking,

Please unblock package kwidgetsaddons

unblock kwidgetsaddons/5.28.0-3

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.9.0-2-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/bash
Init: systemd (via /run/systemd/system)



Bug#862394: libreoffice-writer: Cannot open a .docx document it just saved: "Attribute w:themeColor redefined"

2017-05-12 Thread Rene Engelhard
found 862394 1:5.2.5-1
forwarded 862394 https://bugs.documentfoundation.org/show_bug.cgi?id=106086
thanks

Hi,

On Fri, May 12, 2017 at 11:21:00AM +0200, Stéphane Bortzmeyer wrote:
> I open a .docx document and I save it as a different document, same
> format (.docx).
> 
> Then LibreOffice cannot open the document it just saved:
> 
> File format error found at
> SAXParseException: '[word/document.xml line 2]: Attribute w:themeColor 
> redefined
> ', Stream 'word/document.xml', Line 2, Column 41832(row,col).

This is not very helpful without the document...

And maybe even try with 5.3.3, that's
the current upstream series. 5.2.x is basically dead upstream by now (see 
https://wiki.documentfoundation.org/ReleasePlan/5.2)

Hmm, actually it seems this is
https://bugs.documentfoundation.org/show_bug.cgi?id=106086

Regards,

Rene



Bug#862399: unblock: konsole/4:16.12.0-4

2017-05-12 Thread Maximiliano Curia
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

A couple of weeks back I cherry picked some upstream fixes for konsole, the 
package was uploaded to experimental first and then to unstable as a way get 
more testers, recently I've updated konsole further, improving one of the 
patches and updating the manpage, the full list of changes against the version 
in stretch follows:

 + upstream_render_text_at_primary_fonts_baseline.patch (Closes: 858584)
   This fixes the font rendering when a glyph is being replaced (for example
   using the powerline glyphs), otherwise the glyph might be shown out of
   place, and moved around on redraw.

 + Add-nofork-as-compatibility-alias-for-separate.patch
   Upstream description:

Subject: Add --nofork as compatibility alias for --separate

In previous incarnations of kuniqueapplication it used to inject a common
command option --nofork which is meant to bypass single-instance behavior.
Given that konsole can and is being invoked from scripts they may well want
to ensure that the fork they created is the actual instance of konsole.
i.e. to monitor return values and life time

Presently, since the options are divergent between konsole4 and konsole5,
scripts are either incompatible with older konsoles or with newer konsoles.
To make life easier for everyone add a compat alias --nofork, which
behaves exactly like separate.

(this unbreaks steam, which is a notable recent offender of falling into
 this particular trap)

REVIEW: 129647
CHANGELOG: Added compatibility command option `--nofork` for 
single-instance behavior

  + Add patch: Update-release-date-scripting-and-command-line-help.patch.
Cherry-Picked from "Update release/date, scripting and command line
help" (792eda5).
Update manpage. KDE#373905

 + Fix-build.patch

 syntax error in the preprocessor causing an incomplete build.

 + TerminalDisplay-Abort-painting-invalid-rect.patch

 Reflect in Kate Konsole part see https://git.reviewboard.kde.org/r/129903/

 + Screen-Fix-potential-crash-when-ExtendedCharTable-tries-t.patch

 + Handle-surrogate-utf16-characters.patch

   Upstream description:

Subject: Handle surrogate utf16 characters

For our own sanity we (falsely) assume that all surrogate characters are
double width, otherwise we have to go back and reflow the line.

This makes it work better with emojis in vim at least.

 + Fix-word-boundaries-with-combining-characters.patch

   Upstream description:

Subject: Fix word boundaries with combining characters

Without this it doesn't correctly detect word boundaries e. g. in
arabic.
  Inverts the logic.

 + Don-t-include-newlines-in-selection-if-trimming-is-on.patch

   Fix triple click behaviour.

 + Limit-ourselves-to-3-combining-characters.patch

   Upstream description:

Subject: Limit ourselves to 3 combining characters

This seems to be the limit in all the test files I've been trying.
Without this we get an issue with too many combining characters where
Konsole will eventually just hang.

 + Allow-ANSI-string-terminator-to-work.patch

   Upstream description:
Treat "\e]0;\e\\" (set window title) the same way
it interprets "\e]0;\007".

It seems that Konsole does not recognize the standard string terminator
sequence "\e\\" (ESC \). Everything works fine if I use "\007" (BEL).



  + Add patch: Correct-ANSI-string-terminator.patch.
Cherry-picked from "Correct ANSI string terminator" (7a41b73)
Fixes Allow-ANSI-string-terminator-to-work.patch, \e is 033 which is 27
decimal.

 + Fix-opening-of-new-tabs-with-multiple-processes.patch

   Upstream description:
Subject: Fix opening of new tabs with multiple processes

Make sure we re-use the process if the user wants a new tab.

   Fixes KDE#373440

  + Add patch: Add-check-for-valid-container-possible-crash-fix.patch.
Cherry-picked from "Add check for valid container (possible crash fix)"
(a2b6a81)
Related to KDE#375540

konsole 4:16.12.0-4 is currently in unstable and has built in all the release 
architectures. I'm attaching the full debdiff between the version 4:16.12.0-1 
currently in stretch and the 4:16.12.0-4 version.

Happy hacking,

Please unblock package konsole

unblock konsole/4:16.12.0-4

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.9.0-2-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/bash
Init: systemd (via /run/systemd/system)
diff -Nru konsole-16.12.0/debian/changelog 

Bug#862219: unblock: at-spi2-atk/2.22.0-2

2017-05-12 Thread Niels Thykier
Samuel Thibault:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hello,
> 
> Upstream of at-spi has released some serious fixes for at-spi2-atk,
> which I have uploaded as at-spi2-atk 2.22.0-2, and attached to this
> mail.
> 
> git-7cdc1f91c9802b0b8ecd2afea38c1717b1921736 fixes a memory corruption
> reported by valgrind, which could make basically any application crash
> when the Orca screen reader is running, when processing events. It does
> so by just using the right glib function for what the buggy code meant
> to do.
> 
> git-8d3cc68f7bc62c7015d986212be0d5d776920ee2 fixes memory references
> after dropping a refcount from the object (thus potentially freed), also
> leading to potential crash of any application when the Orca screen
> reader is running.
> 
> unblock at-spi2-atk/2.22.0-2
> 
> [...]

Ack from here, CC'ing KiBi for a d-i ack.

Thanks,
~Niels



Bug#862220: unblock: at-spi2-core/2.22.0-6

2017-05-12 Thread Niels Thykier
Samuel Thibault:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hello,
> 
> Upstream of at-spi has released some serious fixes for at-spi2-core,
> which I have uploaded as at-spi2-core 2.22.0-6, and attached to this
> mail.
> 
> git-329ef2c4ebcb3aec6dcfcac15357fd583a60c969 is reported to help fixing
> https://bugzilla.gnome.org/show_bug.cgi?id=767074
> Orca would sometimes hang or crash when closing an application, thus
> leaving blind users without access to the computer, and have to restart
> Orca blindly.  It seems there are still some cases where the crash
> happens, but only after upgrading at-spi2-atk to version 2.24, which we
> do not have in Debian yet.
> 
> git-eba079f3e72e61e6b55d81727ab50c85d505d296 fixes crashes in Orca too
> when getting the Position property fails.
> 
> These would probably help with the grave orca Bug#862008
> 
> Samuel
> 
> unblock at-spi2-core/2.22.0-6
> 
> [...]

Ack from here, CC'ing KiBi for a d-i ack.

Thanks,
~Niels



Bug#862398: build wks client and server tools

2017-05-12 Thread Stefan Bühler
Package: gnupg2
Version: 2.1.18-8
Severity: wishlist
Tags: patch

Hi,

it would be nice to build and have packages for the gpg-wks-* tools.

It seems there was already done some work in

https://anonscm.debian.org/git/pkg-gnupg/gnupg2.git/log/?h=dev/wks

I rebased that commit to the experimental branch, fixed some file names,
modified some texts and added man pages.

Upstream install gpg-wks-client to /usr/lib/gnupg/, but I moved it in
the package to /usr/bin - I get that it was designed to be a backend
tool for MUAs, but right now I guess most people installing it will have
to use it manually.

I builds fine for me (I didn't test it completely yet though).

My own changes are in:

0001-wks-fix-debian-provide-man-pages-improve-texts.patch

The complete patch (squashed with the dev/wks commit) is:

0001-create-WKS-server-and-client-packages.patch

cheers,
Stefan
From b0f3c201e648980f90bce6c9ab5e47f9b199a985 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Stefan=20B=C3=BChler?= 
Date: Fri, 12 May 2017 12:22:39 +0200
Subject: [PATCH 1/1] create WKS server and client packages
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- install gpg-wks-client into /usr/bin (upstream installs in
  /usr/lib/gnupg/ which I consider not "convenient" for users).

Based on work by Sandro Knauß .
---
 debian/control   | 45 +
 debian/gnupg-wks-client.install  |  1 +
 debian/gnupg-wks-client.manpages |  1 +
 debian/gnupg-wks-server.install  |  1 +
 debian/gnupg-wks-server.manpages |  1 +
 debian/gpg-wks-client.1  | 86 
 debian/gpg-wks-server.1  | 80 +
 debian/rules |  1 +
 8 files changed, 216 insertions(+)
 create mode 100644 debian/gnupg-wks-client.install
 create mode 100644 debian/gnupg-wks-client.manpages
 create mode 100644 debian/gnupg-wks-server.install
 create mode 100644 debian/gnupg-wks-server.manpages
 create mode 100644 debian/gpg-wks-client.1
 create mode 100644 debian/gpg-wks-server.1

diff --git a/debian/control b/debian/control
index ac0b07907..2b9360477 100644
--- a/debian/control
+++ b/debian/control
@@ -72,6 +72,51 @@ Description: GNU privacy guard - cryptographic agent
  provides a passphrase cache, which is used by pre-2.1 versions of
  GnuPG for OpenPGP operations.
 
+Package: gnupg-wks-server
+Architecture: any
+Multi-Arch: foreign
+Depends:
+ gnupg (= ${binary:Version}),
+ ${misc:Depends},
+ ${shlibs:Depends},
+Description: GNU privacy guard - Web Key Service server
+ GnuPG is GNU's tool for secure communication and data storage.
+ It can be used to encrypt data and to create digital signatures.
+ It includes an advanced key management facility and is compliant
+ with the proposed OpenPGP Internet standard as described in RFC4880.
+ .
+ This package provides the GnuPG server for the Web Key Service
+ protocol.
+ .
+ A Web Key Service is a service that allows users to upload keys per
+ mail to be verified over https as described in
+ https://tools.ietf.org/html/draft-koch-openpgp-webkey-service
+ .
+ For more information see: https://wiki.gnupg.org/WKS
+
+Package: gnupg-wks-client
+Architecture: any
+Multi-Arch: foreign
+Depends:
+ dirmngr (= ${binary:Version}),
+ gnupg (= ${binary:Version}),
+ ${misc:Depends},
+ ${shlibs:Depends},
+Description: GNU privacy guard - Web Key Service client
+ GnuPG is GNU's tool for secure communication and data storage.
+ It can be used to encrypt data and to create digital signatures.
+ It includes an advanced key management facility and is compliant
+ with the proposed OpenPGP Internet standard as described in RFC4880.
+ .
+ This package provides the GnuPG client for the Web Key Service
+ protocol.
+ .
+ A Web Key Service is a service that allows users to upload keys per
+ mail to be verified over https as described in
+ https://tools.ietf.org/html/draft-koch-openpgp-webkey-service
+ .
+ For more information see: https://wiki.gnupg.org/WKS
+
 Package: scdaemon
 Architecture: any
 Multi-Arch: foreign
diff --git a/debian/gnupg-wks-client.install b/debian/gnupg-wks-client.install
new file mode 100644
index 0..3ec2ebcaa
--- /dev/null
+++ b/debian/gnupg-wks-client.install
@@ -0,0 +1 @@
+debian/tmp/usr/lib/gnupg/gpg-wks-client /usr/bin/
diff --git a/debian/gnupg-wks-client.manpages b/debian/gnupg-wks-client.manpages
new file mode 100644
index 0..d2edd3e69
--- /dev/null
+++ b/debian/gnupg-wks-client.manpages
@@ -0,0 +1 @@
+debian/gpg-wks-client.1
diff --git a/debian/gnupg-wks-server.install b/debian/gnupg-wks-server.install
new file mode 100644
index 0..c18c2e7fd
--- /dev/null
+++ b/debian/gnupg-wks-server.install
@@ -0,0 +1 @@
+debian/tmp/usr/bin/gpg-wks-server
diff --git a/debian/gnupg-wks-server.manpages b/debian/gnupg-wks-server.manpages
new file mode 100644
index 0..5bd206c91
--- /dev/null
+++ 

Bug#862335: openssl creates and accepts certificates with bad notAfter field

2017-05-12 Thread Tim Rühsen
On Thu, 11 May 2017 18:42:17 +0200 Kurt Roeckx  wrote:
> On Thu, May 11, 2017 at 02:59:20PM +0200, Harald Dunkel wrote:
>> 
>> Please note the "-enddate 20451231235959Z" and compare with RFC
>> 5280 section 4.1.2.5 (https://www.ietf.org/rfc/rfc5280.txt). The
>> GeneralizedTime format is not allowed for 2045, but apparently
>> openssl doesn't convert the string to UTCTime format.
> 
> Please note that the manual says the format is: YYMMDDHHMMSSZ
> 
> I guess it would be nice we converted it properly.

Just for the record, the latest openssl (1.1.1-dev from Github) accepts
this (seen from the code):

[SS] is optional, <+|-> = either + or - must be present

1.
YYMMDDHHMM[SS]Z YYMMDDHHMM[SS]<+|->hhmm
If valid, these date strings are written to ASN.1 into an UTCTime field.

2.
MMDDHHMM[SS]Z or MMDDHHMMSS<+|->hhmm
If valid, these date strings are written to ASN.1 into a GeneralizedTime
field.

Regarding RFC5280 in both cases (UTCTime and GeneralizedTime) the
seconds (SS) and Z (Zulu) timezone is a MUST.

See RFC5280 '4.1.2.5.1.  UTCTime' and '4.1.2.5.2.  GeneralizedTime'.

OpenSSL relies on their ASN.1 code to check for validity, which is
simply not strict enough. Other implementors do a strict check and thus
might reject certificates generated by openssl.

Regards, Tim



signature.asc
Description: OpenPGP digital signature


Bug#862397: thunar: Thunar crashes when left open for a time showing a folder with thousands of items in it

2017-05-12 Thread Chris Tillman
Package: thunar
Version: 1.6.11-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
Repeatedly, I was working in another window and came back to the file
manager to do something different when
I found the window to be totally non-responsive. A couple of times it
froze the machine completely so it
did not respond to keystrokes at all.
I noticed that it only happened when I left it showing the main folder
I am working in, which has 4,597 items
currently according to ls * | wc -l.
Finally I switched to PCManFM and it does not seem to have these
issues.



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

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

Versions of packages thunar depends on:
ii  desktop-file-utils  0.23-1
ii  exo-utils   0.10.7-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-9
ii  libcairo2   1.14.8-1
ii  libdbus-1-3 1.10.16-1
ii  libdbus-glib-1-20.108-2
ii  libexo-1-0  0.10.7-1
ii  libgdk-pixbuf2.0-0  2.36.5-2
ii  libglib2.0-02.50.3-2
ii  libgtk2.0-0 2.24.31-2
ii  libgudev-1.0-0  230-3
ii  libice6 2:1.0.9-2
ii  libnotify4  0.7.7-1+b1
ii  libpango-1.0-0  1.40.4-1
ii  libsm6  2:1.2.2-1+b3
ii  libthunarx-2-0  1.6.11-1
ii  libxfce4ui-1-0  4.12.1-2
ii  libxfce4util7   4.12.1-3
ii  libxfconf-0-2   4.12.1-1
ii  shared-mime-info1.8-1
ii  thunar-data 1.6.11-1

Versions of packages thunar recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.10.16-1
ii  dbus-x11 [dbus-session-bus]   1.10.16-1
ii  gvfs  1.30.3-1
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.1
ii  libpangocairo-1.0-0   1.40.4-1
ii  libpangoft2-1.0-0 1.40.4-1
ii  thunar-volman 0.8.1-2
ii  tumbler   0.1.31-2+b3
ii  xdg-user-dirs 0.15-2+b1
ii  xfce4-panel   4.12.1-2

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.3.1-4
ii  thunar-media-tags-plugin  0.2.1-1+b2

-- no debconf information



Bug#862075: [Ceph-maintainers] Bug#862075: ceph-detect-init: Platform is not supported.: debian 9.0

2017-05-12 Thread Gaudenz Steinlin


The first version of the patch did not work as expected. Attached is a
fixed version. Back to building and testing ...



bug_862075_v2.debdiff
Description: Binary data


Gaudenz Steinlin  writes:

> Control: forwarded -1 http://tracker.ceph.com/issues/19884
> Control: tags -1 +patch
>
> Simon McVittie  writes:
>
>> On Mon, 08 May 2017 at 11:16:48 +0200, Pim van den Berg wrote:
>>> As you can see ceph assumes our init system is sysvinit in stretch, while it
>>> is systemd.
>>
>> No, our init system is "either sysvinit or systemd, or maybe even Upstart".
>> get_init_system() in reportbug's reportbug.utils demonstrates how to detect
>> which one we're dealing with.
>>
>> (In particular, /run/systemd/system is the canonical way to probe for
>> a system where systemctl can be expected to work.)
>>
>
> There is already a patch proposed upstream doing exactly this. I
> modified it a bit to apply to the current version in stretch and removed
> some more code which is now unused to avoid confusion.
>
> My proposed debdiff is attached to this mail. I'm currently building the
> package and will then do some tests to verify that the patch works as
> expected with systemd and sysvinit. This will take some time (the build
> alone takes several hours).
>
> Gaudenz
>
>
>>>  debian_codenames = {
>>> +'9': 'stretch',
>>
>> The codenames for what will become Debian 10 (buster) and Debian 11
>> (bullseye) are already known, precisely to be able to avoid this sort
>> of bug. However, if what Ceph really wants to know is a fact like
>> "what is the init system?", it should be probing for the init system,
>> not going via the OS vendor and version.
>>
>> S
>> ___
>> Ceph-maintainers mailing list
>> ceph-maintain...@lists.ceph.com
>> http://lists.ceph.com/listinfo.cgi/ceph-maintainers-ceph.com
>>
> -- 
> PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5
> ___
> Ceph-maintainers mailing list
> ceph-maintain...@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-maintainers-ceph.com
-- 
PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5


Bug#861612: pixbros: level designs appear to be non-free

2017-05-12 Thread Fabian Greffrath
Markus Koschany wrote:
> graphics are completely different. Yes, the level design of pixbros
> resembles those of the other non-free games but it is not a direct copy.
> Also the gameplay is much different. I am not aware of any design
> patents for those non-free games hence I am quite sure that there is no
> risk for Debian or any breach of law.

I agree wholeheartedly! If a game should be non-free because it resembles
another, commercial game, then we'd have a huge problem in Debian (and in
free software as a whole).

 - Fabian



Bug#862396: newer version available

2017-05-12 Thread Gürkan Myczko

Package: dbuskit
Version: 0.1.1-2
Severity: wishlist

There's a newer version of dbuskit available at:
https://github.com/gnustep/dbuskit

Yours,



Bug#862331: [php-maint] Bug#862331: libapache2-mod-php5: Segmentation fault in Apache master on apache2 graceful

2017-05-12 Thread Ondřej Surý
Cedric,

as a first thing you should disable all non-Debian provided modules in
your configuration. You have a lot of non-Debian modules and we simply
cannot debug whether the segfault comes from PHP itself or it is some of
the modules you are using.

If that doesn't help, try disabling one Debian-provided module at time
and test whether you can pinpoint the exact place.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Thu, May 11, 2017, at 14:03, Cedric Knight wrote:
> Package: libapache2-mod-php5
> Version: 5.6.30+dfsg-0+deb8u1
> Severity: important
> 
> Apache appeared to be segfaulting every morning during logrotate and 
> needed manual restarting.
> 
> [Sat May 06 06:27:41.175349 2017] [mpm_prefork:notice] [pid 17191]
> AH00171: Graceful restart requested, doing restart
> [Sat May 06 06:27:41.634308 2017]
> [core:notice] [pid 17191] AH00060: seg fault or similar nasty error
> detected in the parent process
> 
> This happens (reproducibly) during apachectl graceful and (at least 
> occasionally) apache2ctl restart but not apache2ctl start.
> 
> Result of an strace -ff:
> 
> apachegraceful.log.3741:10:43:12.084448
> clone(child_stack=0x7f70f8dcef70,
> flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
> parent_tidptr=0x7f70f8dcf9d0, tls=0x7f70f8dcf700,
> child_tidptr=0x7f70f8dcf9d0) = 4446
> apachegraceful.log.3741:10:43:12.084746 futex(0x7f70f8dcf9d0,
> FUTEX_WAIT, 4446, NULL) = 0
> apachegraceful.log.3741:10:43:12.085122 rt_sigaction(SIGPIPE,
> {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x7f71345ad0e0}, {SIG_IGN,
> [], SA_RESTORER, 0x7f7134937890}, 8) = 0
> apachegraceful.log.3741:10:43:12.089773 --- SIGSEGV {si_signo=SIGSEGV,
> si_code=SEGV_ACCERR, si_addr=0x7f710db5ce30} ---
> 
> apachegraceful.log.4446
> 10:43:12.084633 set_robust_list(0x7f70f8dcf9e0, 24) = 0
> 10:43:12.084853 madvise(0x7f70f85cf000, 8368128, MADV_DONTNEED) = 0
> 10:43:12.084955 _exit(0)= ?
> 10:43:12.085022 +++ exited with 0 +++
> 
> gdb attached to running master:
> Program received signal SIGUSR1, User defined signal 1.
> 0x7f86ccce1893 in select () at ../sysdeps/unix/syscall-template.S:81
> 81  in ../sysdeps/unix/syscall-template.S
> (gdb) cont
> Continuing.
> [New Thread 0x7f8691457700 (LWP 12123)]
> [Thread 0x7f8691457700 (LWP 12123) exited]
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x7f86a596c6c0 in zm_startup_redland ()
>from /usr/lib/php5/20131226/redland.so
> 
> #0  0x7f86a596c6c0 in zm_startup_redland ()
>from /usr/lib/php5/20131226/redland.so
> #1  0x7f86c96fb43e in zend_startup_module_ex ()
>from /usr/lib/apache2/modules/libphp5.so
> #2  0x7f86c96fb4e9 in ?? () from /usr/lib/apache2/modules/libphp5.so
> #3  0x7f86c9703eb3 in zend_hash_apply ()
>from /usr/lib/apache2/modules/libphp5.so
> #4  0x7f86c96fb7ca in zend_startup_modules ()
>from /usr/lib/apache2/modules/libphp5.so
> #5  0x7f86c96914f3 in php_module_startup ()
>from /usr/lib/apache2/modules/libphp5.so
> #6  0x7f86c97a5df5 in ?? () from /usr/lib/apache2/modules/libphp5.so
> #7  0x7f86c97a69b3 in ?? () from /usr/lib/apache2/modules/libphp5.so
> #8  0x7f86cdb2a2a3 in ap_run_post_config ()
> #9  0x7f86cdb075c4 in main ()
> 
> But it doesn't seem specific to that PHP module.  After `php5dismod red`,
> instead get:
> 
> #0  0x7fac6b39a49e in zm_startup_vtkgdcm ()
>from /usr/lib/php5/20131226/vtkgdcm.so
> #1  0x7fac931a343e in zend_startup_module_ex ()
>from /usr/lib/apache2/modules/libphp5.so
> #2  0x7fac931a34e9 in ?? () from /usr/lib/apache2/modules/libphp5.so
> #3  0x7fac931abeb3 in zend_hash_apply ()
>from /usr/lib/apache2/modules/libphp5.so
> #4  0x7fac931a37ca in zend_startup_modules ()
>from /usr/lib/apache2/modules/libphp5.so
> #5  0x7fac931394f3 in php_module_startup ()
>from /usr/lib/apache2/modules/libphp5.so
> #6  0x7fac9324ddf5 in ?? () from /usr/lib/apache2/modules/libphp5.so
> #7  0x7fac9324e9b3 in ?? () from /usr/lib/apache2/modules/libphp5.so
> #8  0x7fac975d22a3 in ap_run_post_config ()
> #9  0x7fac975af5c4 in main ()
> 
> # apache2ctl -M
> Loaded Modules:
>  core_module (static)
>  so_module (static)
>  watchdog_module (static)
>  http_module (static)
>  log_config_module (static)
>  logio_module (static)
>  version_module (static)
>  unixd_module (static)
>  access_compat_module (shared)
>  alias_module (shared)
>  auth_basic_module (shared)
>  authn_core_module (shared)
>  authn_file_module (shared)
>  authz_core_module (shared)
>  authz_host_module (shared)
>  authz_user_module (shared)
>  autoindex_module (shared)
>  deflate_module (shared)
>  

Bug#862391: [Pkg-privacy-maintainers] Bug#862391: onionshare: Please ensure onionshare is in Stretch

2017-05-12 Thread intrigeri
u:
> This will also allow adding some upstream modifications that were made
> recently.

Great! (assuming they satisfy the criteria for freeze exception at
this very late stage of the release process :)



Bug#862395: mirror submission for debian.ipserverone.com

2017-05-12 Thread IPServerOne Solutions Sdn Bhd
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: debian.ipserverone.com
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
CDImage-http: /debian-cd/
Archive-upstream: ftp.sg.debian.org
CDImage-upstream: ftp.sg.debian.org
Updates: four
Maintainer: IPServerOne Solutions Sdn Bhd 
Country: MY Malaysia
Location: Cyberjaya
Sponsor: IPServerOne Solutions Sdn Bhd https://www.ipserverone.com/



Trace Url: 
http://debian.ipserverone.com/debian/project/trace/ftp-master.debian.org
Trace Url: 
http://debian.ipserverone.com/debian/project/trace/debian.ipserverone.com
Trace Url: 
http://debian.ipserverone.com/debian-cd/project/trace/cdimage.debian.org
Trace Url: 
http://debian.ipserverone.com/debian-cd/project/trace/debian.ipserverone.com



Bug#862394: libreoffice-writer: Cannot open a .docx document it just saved: "Attribute w:themeColor redefined"

2017-05-12 Thread Stéphane Bortzmeyer
Package: libreoffice-writer
Version: 1:5.2.6-2
Severity: normal

Dear Maintainer,

I open a .docx document and I save it as a different document, same
format (.docx).

Then LibreOffice cannot open the document it just saved:

File format error found at
SAXParseException: '[word/document.xml line 2]: Attribute w:themeColor redefined
', Stream 'word/document.xml', Line 2, Column 41832(row,col).


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

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

Versions of packages libreoffice-writer depends on:
ii  dpkg   1.18.23
ii  libabw-0.1-1   0.1.1-4
ii  libc6  2.24-10
ii  libe-book-0.1-10.1.2-4
ii  libetonyek-0.1-1   0.1.6-5
ii  libgcc11:6.3.0-16
ii  libicu57   57.1-6
ii  libmwaw-0.3-3  0.3.9-1
ii  libodfgen-0.1-10.1.6-2
ii  libreoffice-base-core  1:5.2.6-2
ii  libreoffice-core   1:5.2.6-2
ii  librevenge-0.0-0   0.0.4-6
ii  libstdc++6 6.3.0-16
ii  libwpd-0.10-10 0.10.1-5
ii  libwpg-0.3-3   0.3.1-3
ii  libwps-0.4-4   0.4.5-1
ii  libxml22.9.4+dfsg1-2.2
ii  uno-libs3  5.2.6-2
ii  ure5.2.6-2
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages libreoffice-writer recommends:
ii  libreoffice-math  1:5.2.6-2

Versions of packages libreoffice-writer suggests:
ii  default-jre [java5-runtime]2:1.8-58
ii  fonts-crosextra-caladea20130214-1
ii  fonts-crosextra-carlito20130920-1
ii  libreoffice-base   1:5.2.6-2
pn  libreoffice-gcj
ii  libreoffice-java-common1:5.2.6-2
ii  openjdk-8-jre [java5-runtime]  8u131-b11-1

Versions of packages libreoffice-core depends on:
ii  fontconfig2.11.0-6.7+b1
ii  fonts-opensymbol  2:102.7+LibO5.2.6-2
ii  libboost-date-time1.62.0  1.62.0+dfsg-4
ii  libc6 2.24-10
ii  libcairo2 1.14.8-1
ii  libclucene-contribs1v52.3.3.4+dfsg-1
ii  libclucene-core1v52.3.3.4+dfsg-1
ii  libcmis-0.5-5v5   0.5.1+git20160603-3+b1
ii  libcups2  2.2.1-8
ii  libcurl3-gnutls   7.52.1-5
ii  libdbus-1-3   1.10.18-1
ii  libdbus-glib-1-2  0.108-2
ii  libdconf1 0.26.0-2+b1
ii  libeot0   0.01-4+b1
ii  libexpat1 2.2.0-2
ii  libexttextcat-2.0-0   3.4.4-2+b1
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-16
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libglew2.02.0.0-3+b1
ii  libglib2.0-0  2.50.3-2
ii  libgltf-0.0-0v5   0.0.2-5
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgraphite2-31.3.9-4
ii  libharfbuzz-icu0  1.4.2-1
ii  libharfbuzz0b 1.4.2-1
ii  libhunspell-1.4-0 1.4.1-2+b2
ii  libhyphen02.8.8-5
ii  libice6   2:1.0.9-2
ii  libicu57  57.1-6
ii  libjpeg62-turbo   1:1.5.1-2
ii  liblangtag1   0.6.2-1
ii  liblcms2-22.8-4
ii  libldap-2.4-2 2.4.44+dfsg-4+b1
ii  libmythes-1.2-0   2:1.2.4-3
ii  libneon27-gnutls  0.30.2-2
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26.2-1
ii  libodfgen-0.1-1   0.1.6-2
ii  libpcre3  2:8.39-3
ii  libpng16-16   1.6.28-1
ii  librdf0   1.0.17-1.1
ii  libreoffice-common1:5.2.6-2
ii  librevenge-0.0-0  0.0.4-6
ii  libsm62:1.2.2-1+b3
ii  libstdc++66.3.0-16
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxinerama1  2:1.1.3-1+b3
ii  libxml2   2.9.4+dfsg1-2.2
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1
ii  libxslt1.11.1.29-2.1
ii  uno-libs3 5.2.6-2
ii  ure   5.2.6-2
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages libreoffice-core recommends:
ii  libpaper-utils  1.1.24+nmu5

-- no debconf information



Bug#862354: ITP: installation-birthday -- Receive congratulations on system installation anniversaries

2017-05-12 Thread Chris Lamb
Chris Lamb wrote:

> > does it also work when the package is installed years after
> > the birthday?
> 
> Yes; it attempts to determine the system installation date - it's
> not based on the installation date of the package itself.

Updated the package description to make this clearer. :)


Regards,

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



Bug#842635: Incorrect output on i386 due to UB

2017-05-12 Thread Chris Lamb
tags 858389 + pending
tags 842635 + pending
thanks

> Re: Incorrect output on i386 due to UB

Applied & uploaded; many thanks! :)


Regards,

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



Bug#862391: [Pkg-privacy-maintainers] Bug#862391: onionshare: Please ensure onionshare is in Stretch

2017-05-12 Thread u
Hi!

intrig...@debian.org:
> Package: onionshare
> Version: 0.9.1-1
> Severity: normal
> 
> Hi,
> 
> unless we do something about it, onionshare will be auto-removed from
> testing soon as it depends on torbrowser-launcher that itself won't
> make it into Stretch.
> 
> There are plans to address the root cause of the problem in Buster
> (thanks to onion-grater), but for Stretch I suggest we:
> 
> 1. demote "Depends: torbrowser-launcher" to Recommends
> 2. document in README.Debian that to use onionshare, one needs
>either:
>a) to install and run torbrowser-launcher so onionshare uses this
>   instance
>b) to configure access to the control port of a system-wide Tor,
>   and point onionshare to it
> 
> … which would allow us to ship onionshare in Stretch, with sub-optimal
> usability, sure, but still better than not having it at all IMO.
> 
> What do you think? Sounds doable?

Thanks for caring and coming up with this plan. I'll handle it that way.
This will also allow adding some upstream modifications that were made
recently.

Cheers!
u.



Bug#860981: [pkg-cryptsetup-devel] Bug#860981: CVE-2016-4484 still Exists

2017-05-12 Thread ??. ?
Dear Guilhem,


Well when installing a Debian system and enabling encryption in 
https://anonscm.debian.org/cgit/d-i/partman-crypto.git/, the `panic` kernel 
parameter will not be automatically added, so I don't think everyone who has 
enabled full-disk encryption will disable the debug shell. If necessary, I 
think we should contact the d-i team.


More importantly, the claim that the security hole has been fixed by patches, 
while actually not, is misleading and confusing. I don't think it is 
appropriate to do actually NOTHING for even a trivial bug; at least we should 
have a sign noticing the problem here and avoiding unnecessary troubles for 
future users. Thank you.


Regards,


XU Guang-zhao



Bug#862393: linux: FTBFS on m68k due outdated revert-m68k-move-exports-to-definitions.patch

2017-05-12 Thread John Paul Adrian Glaubitz
Source: linux
Version: 4.11-1~exp2
Severity: normal
User: debian-...@lists.debian.org
Usertags: m68k

Hi!

linux currently fails to build from source in experimental because the
patch revert-m68k-move-exports-to-definitions.patch removes at least
one #include directive from arch/m68k/lib/ashldi3.c [1] which is now
required due to some upstream changes in the compiler macros used:

 CC  arch/m68k/lib/ashldi3.o
/<>/arch/m68k/lib/ashldi3.c:18:22: error: expected '=', ',', ';', 
'asm' or '__attribute__' before '__mode'
 typedef   int SItype __mode(SI);
  ^~
/<>/arch/m68k/lib/ashldi3.c:19:30: error: expected '=', ',', ';', 
'asm' or '__attribute__' before '__mode'
 typedef unsigned int USItype __mode(SI);
  ^~
/<>/arch/m68k/lib/ashldi3.c:20:22: error: expected '=', ',', ';', 
'asm' or '__attribute__' before '__mode'
 typedef   int DItype __mode(DI);
  ^~
/<>/arch/m68k/lib/ashldi3.c:21:33: error: expected '=', ',', ';', 
'asm' or '__attribute__' before '__mode'
 typedef int word_type   __mode(__word__);
 ^~
/<>/arch/m68k/lib/ashldi3.c:23:18: error: unknown type name 
'SItype'
 struct DIstruct {SItype high, low;};
  ^~
/<>/arch/m68k/lib/ashldi3.c:28:3: error: unknown type name 'DItype'
   DItype ll;
   ^~
/<>/arch/m68k/lib/ashldi3.c:31:1: error: unknown type name 'DItype'
 DItype
 ^~
/<>/arch/m68k/lib/ashldi3.c:32:12: error: unknown type name 
'DItype'
 __ashldi3 (DItype u, word_type b)
^~
/<>/arch/m68k/lib/ashldi3.c:32:22: error: unknown type name 
'word_type'
 __ashldi3 (DItype u, word_type b)
  ^
/<>/scripts/Makefile.build:299: recipe for target 
'arch/m68k/lib/ashldi3.o' failed
make[6]: *** [arch/m68k/lib/ashldi3.o] Error 1

arch/m68k/lib/ashldi3.c requires  now because that's where
__mode() is defined as a compiler-specific macro. So the patch needs to be
updated accordingly. Since I currently don't understand why this particular
patch is necessary, I don't have a patch myself at hand.

Thanks,

Adrian

> [1] 
> https://anonscm.debian.org/cgit/kernel/linux.git/tree/debian/patches/bugfix/m68k/revert-m68k-move-exports-to-definitions.patch#n86

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#862071: Bug#861591: Bug#862071: password-store: FTBFS when built in a path with >= 74 characters

2017-05-12 Thread intrigeri
Dominic Hargreaves:
> Please could you rule on whether the above class of bugs should be RC
> for stretch? It doesn't seem productive at this late stage.

Indeed: I'll be happy to fix that in Buster or in a Stretch
point-release (also because I've noticed it breaks autopkgtests for
some packages of "mine"), but IMO this shouldn't block the Stretch
release, so a stretch-ignore tag would seem suitable to me.

Cheers,
-- 
intrigeri



Bug#862392: unblock: nexus/4.3.2-svn1921-5

2017-05-12 Thread Andreas Tille
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package nexus

The package fixes #861736 in a patch provided by Gilles Filippini
(thanks for this Gilles).

I did another admittedly questionable change.  I moved the package to
Debian Science team (so some d/control information was changed) which is
probably fine even under freeze policy.  I also added a watch file to
make sure a signal is raised that there is also a new upstream version
so the package is definitely better than before (even if I admit that
I would have applied more changes outside freeze policy).

The questionable part is that I intentionally left out a human beeing as
Uploader.  To compensate this I'm CCing Debian Science team as well as
the contributors to this bug report who are known members of Debian
Science team.  I'm hereby explicitly asking you to consider adding your
name as Uploader in Git[1] to make sure we will add a responsible person
as soon as possible.  If it turns out that nobody else would volunteer I
would consider adding myself to follow policy - but I have a really bad
feeling to do so since I feel totally incompetent to maintain this
package and while beeing sure that I could do better than annonymous QA
member it will be far from what I consider "properly".

So thanks for considering to add yourself as Uploader.

Kind regards

   Andreas.


[1] https://anonscm.debian.org/git/debian-science/packages/nexus.git


unblock nexus/4.3.2-svn1921-5

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=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)
diff -Nru nexus-4.3.2-svn1921/debian/changelog nexus-4.3.2-svn1921/debian/changelog
--- nexus-4.3.2-svn1921/debian/changelog	2016-07-22 23:05:27.0 +0200
+++ nexus-4.3.2-svn1921/debian/changelog	2017-05-11 09:23:17.0 +0200
@@ -1,3 +1,19 @@
+nexus (4.3.2-svn1921-5) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Andreas Tille ]
+  * Take over package into Debian Science team
+  * Fix wrong Priority: extra -> optional
+  * Add watch file
+  * Add Homepage field
+
+  [ Gilles Filippini ]
+  * New patch hdf5-1.10-support.patch to fix incorrect type for HDF5
+handles: should be hid_t instead of int (closes: #861736)
+
+ -- Andreas Tille   Thu, 11 May 2017 09:23:17 +0200
+
 nexus (4.3.2-svn1921-4) unstable; urgency=medium
 
   * QA upload.
diff -Nru nexus-4.3.2-svn1921/debian/control nexus-4.3.2-svn1921/debian/control
--- nexus-4.3.2-svn1921/debian/control	2015-12-13 23:47:48.0 +0100
+++ nexus-4.3.2-svn1921/debian/control	2017-05-11 09:23:17.0 +0200
@@ -1,6 +1,6 @@
 Source: nexus
-Priority: extra
-Maintainer: Debian QA Group 
+Priority: optional
+Maintainer: Debian Science Team 
 Build-Depends: ant,
autoconf,
automake,
@@ -18,6 +18,9 @@
python-numpy
 Standards-Version: 3.9.6
 Section: libs
+Vcs-Browser: https://anonscm.debian.org/cgit/debian-science/packages/nexus.git
+Vcs-Git: https://anonscm.debian.org/git/debian-science/packages/nexus.git
+Homepage: https://github.com/nexusformat/code
 
 Package: libnexus0v5
 Section: libs
diff -Nru nexus-4.3.2-svn1921/debian/patches/hdf5-1.10-support.patch nexus-4.3.2-svn1921/debian/patches/hdf5-1.10-support.patch
--- nexus-4.3.2-svn1921/debian/patches/hdf5-1.10-support.patch	1970-01-01 01:00:00.0 +0100
+++ nexus-4.3.2-svn1921/debian/patches/hdf5-1.10-support.patch	2017-05-11 09:23:17.0 +0200
@@ -0,0 +1,111 @@
+Description: HDF5 1.10.x uses 64 bit handles. They're not int anymore.
+Author: Gilles Filippini 
+Bug-Debian: https://bugs.debian.org/861736
+Index: nexus-4.3.2-svn1921/src/napi5.c
+===
+--- nexus-4.3.2-svn1921.orig/src/napi5.c
 nexus-4.3.2-svn1921/src/napi5.c
+@@ -54,12 +54,12 @@ extern  void *NXpData;
+   hsize_t iCurrentIDX;
+ } iStack5[NXMAXSTACK];
+ struct iStack5 iAtt5;
+-int iFID;
+-int iCurrentG;
+-int iCurrentD;
+-int iCurrentS;
+-int iCurrentT;
+-int iCurrentA;
++hid_t iFID;
++hid_t iCurrentG;
++hid_t iCurrentD;
++hid_t iCurrentS;
++hid_t iCurrentT;
++hid_t iCurrentA;
+ int iNX;
+ int iNXID;
+ int iStackPtr;
+@@ -434,7 +434,7 @@ NXstatus  NX5open(CONSTCHAR *filename, N
+   NXstatus  NX5makegroup (NXhandle fid, CONSTCHAR *name, CONSTCHAR *nxclass) 
+   {
+ pNexusFile5 pFile;
+-herr_t iRet;
++hid_t iRet;
+ hid_t iVID;
+ hid_t attr1,aid1, aid2;
+ char pBuffer[1024] = "";
+@@ 

Bug#859773: gearman-job-server: Source code migrated from launchpad to github, please consider to update

2017-05-12 Thread Alex Mestiashvili
The new version is already in git and will be uploaded after the freeze.
 https://anonscm.debian.org/cgit/collab-maint/gearmand.git

Best regards,
Alex


Bug#771563: gnome-control-center: bluetooth devices not listed

2017-05-12 Thread Gabriele Brosulo
Same problem here, on debian Jessie fully upgraded. Sometime it works,
but the most of the time it doesn't.
I've also installed firmware-atheros_0.43_all.deb, but it doesn't solve
the issue.

-- 
Gabriele Brosulo





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


Bug#862391: onionshare: Please ensure onionshare is in Stretch

2017-05-12 Thread intrigeri
Package: onionshare
Version: 0.9.1-1
Severity: normal

Hi,

unless we do something about it, onionshare will be auto-removed from
testing soon as it depends on torbrowser-launcher that itself won't
make it into Stretch.

There are plans to address the root cause of the problem in Buster
(thanks to onion-grater), but for Stretch I suggest we:

1. demote "Depends: torbrowser-launcher" to Recommends
2. document in README.Debian that to use onionshare, one needs
   either:
   a) to install and run torbrowser-launcher so onionshare uses this
  instance
   b) to configure access to the control port of a system-wide Tor,
  and point onionshare to it

… which would allow us to ship onionshare in Stretch, with sub-optimal
usability, sure, but still better than not having it at all IMO.

What do you think? Sounds doable?

Cheers,
-- 
intrigeri



Bug#862322: [xml/sgml-pkgs] Bug#862322: [libxml2] Wrong warning/error about "colons are forbidden from PI names"

2017-05-12 Thread Andre Naujoks
On 05/12/17 09:19, Mattia Rizzolo wrote:
> Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=782520
> 
> On Thu, May 11, 2017 at 03:55:33PM +0200, Andre Naujoks wrote:
>> Done: https://bugzilla.gnome.org/show_bug.cgi?id=782520
> 
> Great, thank you!
> 
>> Is it possible to link this bug to the upstream bug? I mean in a more
>> direct way than the textual link above.
> 
> Yap, does the above fit what you had in mind?  (now at the top of the
> bug page there will be a "Forwarded" line)
> 

Yes that is exactly what I had in mind. Thank you!



Bug#862390: ship CMake config files with the nlopt package

2017-05-12 Thread slayoo

Package: libnlopt-dev
Version: 2.4.2+dfsg-2

Building nlopt from source (https://github.com/stevengj/nlopt) using 
CMake causes "make install" to install CMake config files:


$ sudo make install
[ 88%] Built target nlopt
[100%] Built target testopt
Install the project...
-- Install configuration: "Release"
-- Up-to-date: /usr/lib/x86_64-linux-gnu/pkgconfig/nlopt.pc
-- Up-to-date: /usr/include/nlopt.h
-- Up-to-date: /usr/include/nlopt.hpp
-- Up-to-date: /usr/include/nlopt.f
-- Up-to-date: /usr/lib/x86_64-linux-gnu/libnlopt.so.0.9.0
-- Up-to-date: /usr/lib/x86_64-linux-gnu/libnlopt.so.0
-- Up-to-date: /usr/lib/x86_64-linux-gnu/libnlopt.so
-- Up-to-date: 
/usr/lib/x86_64-linux-gnu/cmake/nlopt/NLoptLibraryDepends.cmake
-- Up-to-date: 
/usr/lib/x86_64-linux-gnu/cmake/nlopt/NLoptLibraryDepends-release.cmake
-- Up-to-date: 
/usr/lib/x86_64-linux-gnu/cmake/nlopt/NLoptConfig.cmake
-- Up-to-date: 
/usr/lib/x86_64-linux-gnu/cmake/nlopt/NLoptConfigVersion.cmake

-- Up-to-date: /usr/share/man/man3/nlopt.3
-- Up-to-date: /usr/share/man/man3/nlopt_minimize.3
-- Up-to-date: /usr/share/man/man3/nlopt_minimize_constrained.3

These *.cmake files enable CMake users to use find_package(NLopt) in 
their CMake scripts.
It would be great to ship these *.cmake files in the Debian package as 
well.


Thanks,
Sylwester



Bug#862389: lightdm: X gets locked up after several switches to VT

2017-05-12 Thread Łukasz Stelmach
Package: lightdm
Version: 1.10.3-3
Severity: normal

Dear Maintainer,

After I had switched from X to VT several times (maybe there are other
cuases too, but I don't know them) X stopped updating windows. The mouse
cursor was moving and changing its shape as I moved it over different
windows. I could still switch betwen VT and X. On VT I found that,
apparently, lightdm wan't handling data from X properly because there
was over 200kB worth of data waiting in X's send queue and 8k in receive
queue in lightdm.

--8<---cut here---start->8---
Netid  State  Recv-Q Send-Q  Local Address:Port  Peer Address:Port   
u_str  ESTAB  0  213504  @/tmp/.X11-unix/X0 9689907  * 9691709 
users:(("Xorg",pid=11405,fd=18))
u_str  ESTAB  8896   0* 9691709  * 9689907 
users:(("lightdm",pid=10124,fd=11))
--8<---cut here---end--->8---


The numbers had been growing each time I switched between X and VT.


I had reported[1] this problem to the lighdm mailing list but there was no
response.

[1] https://lists.freedesktop.org/archives/lightdm/2017-March/001056.html


-- System Information:
Debian Release: 8.8
  APT prefers stable-updates
  APT policy: (950, 'stable-updates'), (950, 'stable'), (500, 
'proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: armel, arm64

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

Versions of packages lightdm depends on:
ii  adduser3.113+nmu3
ii  consolekit 0.4.6-5
ii  dbus   1.8.22-0+deb8u1
ii  debconf [debconf-2.0]  1.5.56
ii  libc6  2.19-18+deb8u9
ii  libgcrypt201.6.3-2+deb8u2
ii  libglib2.0-0   2.42.1-1+b1
ii  libpam-systemd 215-17+deb8u7
ii  libpam0g   1.1.8-3.1+deb8u2
ii  libxcb11.10-3+b1
ii  libxdmcp6  1:1.1.1-1+b1
ii  lightdm-gtk-greeter [lightdm-greeter]  1.8.5-2

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+7

Versions of packages lightdm suggests:
ii  accountsservice  0.6.37-3+b1
ii  upower   0.99.1-3.2

-- Configuration Files:
/etc/apparmor.d/lightdm-guest-session 9d3af5806375ac868fcaf5aaf3d56a00 [Errno 
2] Nie ma takiego pliku ani katalogu: u'/etc/apparmor.d/lightdm-guest-session 
9d3af5806375ac868fcaf5aaf3d56a00'
/etc/init/lightdm.conf b5de8ae57f7a4f102b6a6943139957a5 [Errno 2] Nie ma 
takiego pliku ani katalogu: u'/etc/init/lightdm.conf 
b5de8ae57f7a4f102b6a6943139957a5'

-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm

-- 
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics


signature.asc
Description: PGP signature


Bug#862222: Version 1:2.14.04.dfsg.2-9+b1 (jessie) still working

2017-05-12 Thread Simon Baumgartner
Dear maintainer,
the version 1:2.14.04.dfsg.2-9+b1  (jessie)  seems not to be affected by
this bug, at least it
starts without any error. Whatever the difference is in the +b2 version it
seems to have an
impact on amd64. Hopefully this can be fixed before it gets kicked out of
stretch due to the
upcoming freeze. Some people are still using this.
Thanks for your efforts & kind regards,
simon


Bug#862355: mate-settings-daemon: Can't change wallpaper when selecting one

2017-05-12 Thread Zorzi

Hello Dear Maintainer

The same problem occurs with my system since last update.

Can't be sure if this is linked to the package mate-settings-daemon. Or 
may the package mate-control-center be in cause ?


After update and reboot, my desktop wallpaper got stuck to the lightdm 
wallpaper instead of the usual one.


Can't change it, nor in the appearance parameters, neither by opening an 
image file and trying to define it as wallpaper.


Thanks for your help.

Dearly.

Zorzi



Bug#861580: (pre-approval) unblock: mysql-connector-python/2.1.6

2017-05-12 Thread Salvatore Bonaccorso
Hi,

On Sun, May 07, 2017 at 07:41:00PM +, Niels Thykier wrote:
> Control: tags -1 confirmed moreinfo
> 
> Sandro Tosi:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > 
> > Hello,
> > BTS 861511 was reported yesterday against mysql-connector-python stating 
> > the new
> > upstream version (2.1.6) fixes CVE-2017-3590.
> > 
> > The upstream versions diff (attached) is quite important, so i would 
> > understand
> > if you decide not to accept a potential upload of this new version aiming 
> > for an
> > unblock to strech, but i would still like you to have a look and decide on 
> > it.
> > 
> > Thanks,
> > Sandro
> > 
> > [...]
> 
> Ack, please go ahead and remove the moreinfo tag once the upload has
> been processed and has been built on all relevant release architectures.
> 
> NOTE: the test suite contains certificates that expire in 2018.  If that
> causes test failures, then that is an RC bug (as it would mean we would
> be unable to compile mysql-connector-python in stretch before its EOL).
> AFAICT, said problem would also exists in the current version (except
> the expiry reads 2017 instead).
>   Please consider replacing the certificates with once that can survive
> stretch + stretch-lts's life-time.

Sandro, any news on the upload?

Regards,
Salvatore



Bug#862388: ITP: node-har-validator -- Extremely fast HTTP Archive (HAR) validator using JSON Schema

2017-05-12 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-har-validator
  Version : 5.0.2
  Upstream Author : Ahmad Nassri 
(https://www.ahmadnassri.com/)
* URL : https://github.com/ahmadnassri/har-validator
* License : ISC
  Programming Lang: JavaScript
  Description : Extremely fast HTTP Archive (HAR) validator using
JSON Schema

 HTTP Archive (HAR) format defines an archival format for HTTP transactions
 that can be used by a web browser to export detailed performance data about
 web pages it loads.
 .
 This library is a dependency of request, the simplest way possible to make
 http calls.
 .
 Node.js is an event-based server-side JavaScript engine.



signature.asc
Description: OpenPGP digital signature


Bug#752050: Please reply, I have a genuine business to discuss with you.

2017-05-12 Thread Hussein Saleh
I have a business proposal to discuss with you, this business is
genuine, legal and highly lucrative. You will be happy at the end, for
more details, please reply


Sincerely
Hussein Saleh



Bug#862354: ITP: installation-birthday -- Receive congratulations on system installation anniversaries

2017-05-12 Thread Chris Lamb
Holger Levsen wrote:

> >   Description : Receive congratulations on system installation 
> > anniversaries
>  
> lol, nice one!
> 
> does it also work when the package is installed years after
> the birthday?

Yes; it attempts to determine the system installation date - it's
not based on the installation date of the package itself. :)


Regards,

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



Bug#849366: FW: Bug#849366: Acknowledgement (Debian8.2 cannot handle memory hot-add)

2017-05-12 Thread Yanhui He
Hi,

I have tested Debian 9.0 RC3 memory hot-adding and the problem is still existed.

Would you please help me take a look?


Thanks!

--
Best Regards,
Yanhui

On 26/12/2016, 5:57 PM, "Debian Bug Tracking System"  
wrote:

Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
  h...@vmware.com, 
l...@vmware.com, 
yan...@vmware.com,
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
 unknown-pack...@qa.debian.org

If you wish to submit further information on this problem, please
send it to 849...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

-- 
849366: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__bugs.debian.org_cgi-2Dbin_bugreport.cgi-3Fbug-3D849366=DgIFaQ=uilaK90D4TOVoH58JNXRgQ=br9wuzL1fvzS68DIWik55V8CR3RHqUJK3Jgttay85T0=hCyxfyqczSzBNrAPbIVIknJ-cXdfsDS3oHFF6-U7leU=oWh09OY5DXNJkeGxz-sP5Xwv-L6EHX-9Kgkd2EM3jd4=
 
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems




Bug#862322: [xml/sgml-pkgs] Bug#862322: [libxml2] Wrong warning/error about "colons are forbidden from PI names"

2017-05-12 Thread Mattia Rizzolo
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=782520

On Thu, May 11, 2017 at 03:55:33PM +0200, Andre Naujoks wrote:
> Done: https://bugzilla.gnome.org/show_bug.cgi?id=782520

Great, thank you!

> Is it possible to link this bug to the upstream bug? I mean in a more
> direct way than the textual link above.

Yap, does the above fit what you had in mind?  (now at the top of the
bug page there will be a "Forwarded" line)

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#862387: openstack-dashboard: instance delete fails with: 403 Forbidden - CSRF verification failed. Request aborted.

2017-05-12 Thread Valentin Vidic
Package: openstack-dashboard
Version: 3:10.0.1-1
Severity: normal

Dear Maintainer,

Instance delete fails when I access:

  http://os-ctrl/horizon/project/instances/

and select "Delete Instance" from the list of actions with
the error:

  Forbidden (403)
  CSRF verification failed. Request aborted.

  Help
  Reason given for failure:
CSRF token missing or incorrect.

while I see the csrftoken being sent in the request:

  csrftoken: tMhcr99nId798AXdULs8dUjuEHemALp0ONGCa4Y8ahpIuckFFqxexCuD13uR5ATy

Apache error.log just reports the same thing:

  Forbidden (CSRF token missing or incorrect.): /horizon/project/instances/, 
referer: http://os-ctrl/horizon/project/instances/

Deleting the instance works if I enter the instance first:

  http://os-ctrl/horizon/project/instances/6a167f8a-f0c6-440a-a1c1-c0063058d5c4/

and than select "Delete Instance" from the list of actions.

The same issue exists when deleting volumes from:

  http://os-ctrl/horizon/project/volumes/


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

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openstack-dashboard depends on:
ii  adduser3.115
ii  libjs-jquery   3.1.1-2
ii  libjs-jquery-cookie11-3
ii  python-django-horizon  3:10.0.1-1
pn  python:any 

openstack-dashboard recommends no packages.

Versions of packages openstack-dashboard suggests:
ii  memcached   1.4.33-1
ii  openstack-dashboard-apache  3:10.0.1-1

-- no debconf information



Bug#862386: incomplete build

2017-05-12 Thread Gürkan Myczko

Package: gnustep-examples
Version: 1:1.4.0-1+b2
Severity: wishlist

I guess we should also build Finger, GFractal, GPuzzle, HostAddress 
examples included in the current version in sid.
There's an added app PowerPaint (Document based) in the git. And an 
OpenGL example MyGL?


This bug is just a reminder to not forget with the next update of the 
package... I will try myself as well.


Yours,



Bug#861736: closed by Andreas Tille <ti...@debian.org> (Bug#861736: fixed in nexus 4.3.2-svn1921-5)

2017-05-12 Thread Marc Rosanes

Hi,

We have found that python-nxs is still affected by problems:

The following piece of code fails on stretch + the lastest nexus from 
unstable:


```
import nxs
f = nxs.open("/tmp/foo.h5", "w5")
f.makegroup('entry', 'NXentry')
f.opengroup('entry')
f.makegroup('g', 'NXcollection')
f.opengroup('g', 'NXcollection')
f.makedata('d', 'float64', shape=(1,))
f.opendata('d')
f.putdata(1.23)
f.closedata()
f.closegroup()
f.flush()
f.close()
```


It fails with the exception:

```
Traceback (most recent call last):
  File "nxs_flush_bug.py", line 12, in 
f.flush()
  File "/usr/lib/python2.7/dist-packages/nxs/napi.py", line 397, in flush
raise NeXusError, "Could not flush NeXus file %s"%(self.filename)
nxs.napi.NeXusError: Could not flush NeXus file /tmp/foo.h5
```


The same code works correctly on a clean jessie docker.

This ticket should be reopened, till this issue is solved.




On 05/11/2017 11:12 AM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the python-nxs package:

#861736: python-nxs: Cannot save files with nxs python module

It has been closed by Andreas Tille .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Andreas Tille 
 by
replying to this email.




--
Marc Rosanes Siscart

Computing & Control Division
CELLS – ALBA

ALBA Synchrotron Light Facility
Carrer de la Llum 2-26
08290 Cerdanyola del Vallès, Barcelona (SPAIN)

Tel: +34 93 592 40 41 Fax: +34 93 592 43 01
web page: http://www.cells.es/



Bug#715646: Processed: Bug#715646 marked as pending

2017-05-12 Thread Moritz Mühlenhoff
On Thu, May 11, 2017 at 11:48:47PM +0200, Marcos Fouces wrote:
> Hi Adrian,
> 
> i agree to prepare a package for the next Jessie point release. I think
> these issues are not grave enough for a DSA.
> 
> That is my opinon, but i would appreciate feedback.

Agreed, please fix this via the jessie 8.9 point release.

Cheers,
Moritz



Bug#862373: Unconditionally instantiates objects from yaml data

2017-05-12 Thread Dominique Dumont
> As previously mentioned in debian-perl@, there is no easy solution,

A possibility to limit the impact is to deny object creation if the class has 
a DESTROY method.

Knowing that UNIVERSAL has no DESTROY method, It's fairly easy to test:

$ perl -MFile::Temp -E 'say File::Temp->can("DESTROY") ? "yes" : "no";'
yes
$ perl -E 'say UNIVERSAL->can("DESTROY") ? "yes" : "no";'
no
$ perl -MGetopt::Long -E 'say Getopt::Long->can("DESTROY") ? "yes" : "no";'
no

HTH

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



Bug#862385: ITP: node-har-schema -- JSON Schema for HTTP Archive (HAR)

2017-05-12 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-har-schema
  Version : 2.0.0
  Upstream Author : Ahmad Nassri 
(https://www.ahmadnassri.com/)
* URL : https://github.com/ahmadnassri/har-schema
* License : ISC
  Programming Lang: JavaScript
  Description : JSON Schema for HTTP Archive (HAR)

 HTTP Archive (HAR) format defines an archival format for HTTP transactions
 that can be used by a web browser to export detailed performance data about
 web pages it loads.
 .
 This library is a dependency of har-validator.
 .
 Node.js is an event-based server-side JavaScript engine.



signature.asc
Description: OpenPGP digital signature


<    1   2