Bug#807074: marked as done (fbreader: includes files with unclear DFSG-freeness and/or copyright status)

[Debian Bug Tracking System]

Your message dated Sat, 23 Jan 2016 11:17:49 +0100
with message-id <56a3534d.9070...@debian.org>
and subject line Re: Bug#807074: fbreader: includes files with unclear 
DFSG-freeness and/or copyright status
has caused the Debian Bug report #807074,
regarding fbreader: includes files with unclear DFSG-freeness and/or copyright 
status
to be marked as done.

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

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


-- 
807074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fbreader
Version: 0.10.7dfsg-4
Severity: serious
Justification: Policy 2.2.1

Hello Eugene and thanks for maintaining FBReader in Debian!

I noticed something awkward in the debian/copyright file:

[...]
|  Html entity files (fbreader/data/formats/docbook/*.ent) with
|  these licenses:
|  
|  
|  
|  
[...]

The problem is: among these two licenses, the first one is non-free,
as it does not grant permission to modify (thus failing DFSG#3) and
only grants a limited permission to copy and use, restricting the
field of endeavor to conforming SGML systems and applications as
defined in ISO 8879 (thus failing DFSG#6).
The second license is instead fine for Debian main.

By only reading the debian/copyright file, it was not clear to me
whether both licenses apply (which would mean that these files
are non-free in fbreader) or, instead, whether the recipient may
choose which of the two licenses will apply (which would mean that
we can choose the second license and everything is fine for fbreader).

This freeness issue has been discussed on the debian-legal mailing list:
https://lists.debian.org/debian-legal/2015/11/msg00048.html
https://lists.debian.org/debian-legal/2015/11/msg00049.html

During that debian-legal thread, I was pointed out that the licensing
of those files in fbreader is a bit different from what is documented
in the fbreader debian/copyright file:
https://lists.debian.org/debian-legal/2015/11/msg00050.html
And indeed, the files under consideration include that permission grant,
saying that the DFSG-free license applies, but that the files are
derived, in part, from files (copyrighted by ISO) which grant no
permission to modify.
As I said in
https://lists.debian.org/debian-legal/2015/11/msg00051.html
I cannot fully understand how those files could be derived from
the ISO files in the first place, if the ISO files are not legally
modifiable.
Maybe OASIS obtained a special permission from ISO, but this does
not seem to be documented.
Otherwise, this looks like a copyright violation, which, if confirmed,
would result in undistributable files.

An FTP Assitant confirmed that files under the ISO license under
consideration are not fit for Debian main:
https://lists.debian.org/debian-legal/2015/12/msg0.html


Please investigate and clarify and/or fix this issue.

Possible solutions I can think of:

 A) clarify the licensing status of those files and find out
that they are distributable under DFSG-free terms; explain
and document why this is the case
 
 B) get in touch with the copyright holder (ISO) and persuade
them to re-license the ISO files in a DFSG-free manner
 
 C) find DFSG-free replacements for the non-free files

 D) drop the non-free files from the package, assuming they are
not strictly needed for the package to provide significant
functionality


Thanks for your time!
--- End Message ---
--- Begin Message ---
On 09.01.2016 12:51, Francesco Poli wrote:
> FTP Masters are often very busy, and in some cases they do not have
> time to reply to queries of this kind. Hence, we should *not*
> interpret their silence as if they were saying that everything is OK.
> 
> I am consequently reopening the bug report.

Francesco, we have a technical disagreement. Re-opening a bug won't change my 
opinion. To overrule, please refer to
usual authorities: archive masters or tech-ctte or DAMs.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#812396: Acknowledgement (nvidia-kernel-dkms: fail to load nvidia-uvm.)

[Pascal Obry]

Some more information to help tracking this down. In the system log I
have:

$ dmesg | grep nvidia_uvm
[  103.476413] nvidia_uvm: no symbol version for nvUvmInterfaceChannelDestroy
[  103.476417] nvidia_uvm: Unknown symbol nvUvmInterfaceChannelDestroy (err -22)
[  103.476424] nvidia_uvm: no symbol version for nvUvmInterfaceQueryCaps
[  103.476425] nvidia_uvm: Unknown symbol nvUvmInterfaceQueryCaps (err -22)
[  103.476436] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryAllocSys
[  103.476437] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryAllocSys (err -22)
[  103.476443] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuMap
[  103.476444] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuMap (err -22)
[  103.476450] nvidia_uvm: no symbol version for nvUvmInterfaceKillChannel
[  103.476450] nvidia_uvm: Unknown symbol nvUvmInterfaceKillChannel (err -22)
[  103.476457] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuUnMap
[  103.476458] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuUnMap (err -22)
[  103.476465] nvidia_uvm: no symbol version for 
nvUvmInterfaceAddressSpaceCreateMirrored
[  103.476466] nvidia_uvm: Unknown symbol 
nvUvmInterfaceAddressSpaceCreateMirrored (err -22)
[  103.476493] nvidia_uvm: no symbol version for 
nvUvmInterfaceServiceDeviceInterruptsRM
[  103.476494] nvidia_uvm: Unknown symbol 
nvUvmInterfaceServiceDeviceInterruptsRM (err -22)
[  103.476501] nvidia_uvm: no symbol version for nvUvmInterfaceDeRegisterUvmOps
[  103.476502] nvidia_uvm: Unknown symbol nvUvmInterfaceDeRegisterUvmOps (err 
-22)
[  103.476508] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryFree
[  103.476508] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryFree (err -22)
[  103.476514] nvidia_uvm: no symbol version for nvUvmInterfaceGetUvmPrivRegion
[  103.476515] nvidia_uvm: Unknown symbol nvUvmInterfaceGetUvmPrivRegion (err 
-22)
[  103.476522] nvidia_uvm: no symbol version for nvUvmInterfaceGetAttachedUuids
[  103.476523] nvidia_uvm: Unknown symbol nvUvmInterfaceGetAttachedUuids (err 
-22)
[  103.476531] nvidia_uvm: no symbol version for nvUvmInterfaceSessionDestroy
[  103.476532] nvidia_uvm: Unknown symbol nvUvmInterfaceSessionDestroy (err -22)
[  103.476538] nvidia_uvm: no symbol version for 
nvUvmInterfaceCheckEccErrorSlowpath
[  103.476539] nvidia_uvm: Unknown symbol nvUvmInterfaceCheckEccErrorSlowpath 
(err -22)
[  103.476545] nvidia_uvm: no symbol version for 
nvUvmInterfaceAddressSpaceCreate
[  103.476546] nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceCreate (err 
-22)
[  103.476551] nvidia_uvm: no symbol version for 
nvUvmInterfaceCopyEngineAllocate
[  103.476552] nvidia_uvm: Unknown symbol nvUvmInterfaceCopyEngineAllocate (err 
-22)
[  103.476558] nvidia_uvm: no symbol version for 
nvUvmInterfaceAddressSpaceDestroy
[  103.476559] nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceDestroy 
(err -22)
[  103.476565] nvidia_uvm: no symbol version for 
nvUvmInterfaceRegisterUvmCallbacks
[  103.476566] nvidia_uvm: Unknown symbol nvUvmInterfaceRegisterUvmCallbacks 
(err -22)
[  103.476572] nvidia_uvm: no symbol version for nvUvmInterfaceGetGpuArch
[  103.476573] nvidia_uvm: Unknown symbol nvUvmInterfaceGetGpuArch (err -22)
[  103.476579] nvidia_uvm: no symbol version for nvUvmInterfaceChannelAllocate
[  103.476579] nvidia_uvm: Unknown symbol nvUvmInterfaceChannelAllocate (err 
-22)
[  103.476588] nvidia_uvm: no symbol version for nvUvmInterfaceDupAllocation
[  103.476589] nvidia_uvm: Unknown symbol nvUvmInterfaceDupAllocation (err -22)
[  103.476597] nvidia_uvm: no symbol version for nvUvmInterfaceSessionCreate
[  103.476598] nvidia_uvm: Unknown symbol nvUvmInterfaceSessionCreate (err -22)
[  442.286717] nvidia_uvm: no symbol version for nvUvmInterfaceChannelDestroy
[  442.286720] nvidia_uvm: Unknown symbol nvUvmInterfaceChannelDestroy (err -22)
[  442.286727] nvidia_uvm: no symbol version for nvUvmInterfaceQueryCaps
[  442.286728] nvidia_uvm: Unknown symbol nvUvmInterfaceQueryCaps (err -22)
[  442.286738] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryAllocSys
[  442.286738] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryAllocSys (err -22)
[  442.286744] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuMap
[  442.286745] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuMap (err -22)
[  442.286750] nvidia_uvm: no symbol version for nvUvmInterfaceKillChannel
[  442.286751] nvidia_uvm: Unknown symbol nvUvmInterfaceKillChannel (err -22)
[  442.286758] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuUnMap
[  442.286758] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuUnMap (err -22)
[  442.286765] nvidia_uvm: no symbol version for 
nvUvmInterfaceAddressSpaceCreateMirrored
[  442.286765] nvidia_uvm: Unknown symbol 
nvUvmInterfaceAddressSpaceCreateMirrored (err -22)
[  442.286791] nvidia_uvm: no symbol version for 
nvUvmInterfaceServiceDeviceInterruptsRM
[  442.286791] nvidia_uvm: Unknown symbol 
nvUvmInterfaceServiceDeviceInterruptsRM (err -22)
[  

Bug#812398: openldap: FTBFS on buildss.

[Mattia Rizzolo]

Source: openldap
Version: 2.4.42+dfsg-2+b1
Severity: serious


Dear maintainer,
openldap started failing on buildds with

btool: link: aarch64-linux-gnu-gcc -shared  -fPIC -DPIC  .libs/smbk5pwd.o   
-Wl,-rpath -Wl,/usr/lib/aarch64-linux-gnu/heimdal -Wl,-rpath 
-Wl,/«BUILDDIR»/openldap-2.4.42+dfsg/debian/build/libraries/libldap_r/.libs 
-Wl,-rpath 
-Wl,/«BUILDDIR»/openldap-2.4.42+dfsg/debian/build/libraries/liblber/.libs 
-Wl,-rpath -Wl,/usr/lib/aarch64-linux-gnu/heimdal 
-L/usr/lib/aarch64-linux-gnu/heimdal 
/usr/lib/aarch64-linux-gnu/heimdal/libkadm5srv.so 
../../../debian/build/libraries/libldap_r/.libs/libldap_r.so 
../../../debian/build/libraries/liblber/.libs/liblber.so -lnettle  -O2 -Wl,-z 
-Wl,relro -Wl,-z -Wl,now   -pthread -Wl,-soname -Wl,smbk5pwd.so.0 -o 
.libs/smbk5pwd.so.0.0.0
libtool: link: (cd ".libs" && rm -f "smbk5pwd.so.0" && ln -s 
"smbk5pwd.so.0.0.0" "smbk5pwd.so.0")
libtool: link: (cd ".libs" && rm -f "smbk5pwd.so" && ln -s "smbk5pwd.so.0.0.0" 
"smbk5pwd.so")
libtool: link: ar cru .libs/smbk5pwd.a  smbk5pwd.o
ar: `u' modifier ignored since `D' is the default (see `U')
libtool: link: ranlib .libs/smbk5pwd.a
/bin/sed: can't read /usr/lib/aarch64-linux-gnu/libhdb.la: No such file or 
directory
libtool: link: `/usr/lib/aarch64-linux-gnu/libhdb.la' is not a valid libtool 
archive
Makefile:59: recipe for target 'smbk5pwd.la' failed
make[2]: *** [smbk5pwd.la] Error 1
make[2]: Leaving directory 
'/«BUILDDIR»/openldap-2.4.42+dfsg/contrib/slapd-modules/smbk5pwd'
debian/rules:100: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2


This was noticed during the libgnutls-deb0-28 → libgnutls30 transition.

Your package is now failing to build from source everywhere, see
https://buildd.debian.org/status/package.php?p=openldap
https://buildd.debian.org/status/logs.php?pkg=openldap=2.4.42%2Bdfsg-2%2Bb2=sid

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://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#812406: usb: Strange USB bugs

[Nickolay Ilyushin]

Package: libusb-1.0-0
Version: 2:1.0.20-1
Severity: critical
File: usb
Tags: upstream
Justification: causes serious data loss

One PC sees only 10 MiB on my JetFlash Transcend USB and NTFS partition. Second 
PC (this) sees ~16 GiB and Mac & EFI partitions. But all statements are false: 
i don't have Windows, i don't have Mac, size of USB - 4 GiB. Also, sometimes, 
sector size from kernel does not matches sector size from usb driver. Can you 
fix it, maintainer?

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages libusb-1.0-0:i386 depends on:
ii  libc6 2.21-6
ii  libudev1  228-4

libusb-1.0-0:i386 recommends no packages.

libusb-1.0-0:i386 suggests no packages.

-- no debconf information

Bug#812396: nvidia-kernel-dkms: fail to load nvidia-uvm.

[Pascal Obry]

Package: nvidia-kernel-dkms
Version: 349.16-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

The issue is reported by programs like darktable, for example here is
the ouptut on the console:

$ darktable
modprobe: ERROR: could not insert 'nvidia_current_uvm': Invalid argument
modprobe: ERROR: ../libkmod/libkmod-module.c:977 command_do() Error running 
install command for nvidia_uvm
modprobe: ERROR: could not insert 'nvidia_uvm': Operation not permitted

The same output can be reproduced by just trying to modprob nvidia-uvm:

$ sudo modprobe nvidia-uvm
modprobe: ERROR: could not insert 'nvidia_current_uvm': Invalid argument
modprobe: ERROR: ../libkmod/libkmod-module.c:977 command_do() Error running 
install command for nvidia_uvm
modprobe: ERROR: could not insert 'nvidia_uvm': Operation not permitted

This issue was first seen in nvidia 346.96 and now in 349.16.

So current version for testing 340.96-4 does not have this issue.

Please let me know if you need me do some more testing.

Regards,

-- Package-specific info:
uname -a:
Linux pascal 4.3.0-1-amd64 #1 SMP Debian 4.3.3-7 (2016-01-19) x86_64 GNU/Linux

/proc/version:
Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160114 (Debian 5.3.1-6) ) #1 SMP Debian 4.3.3-7 (2016-01-19)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  349.16  Wed Apr  8 00:17:22 PDT 
2015
GCC version:  gcc version 5.3.1 20160121 (Debian 5.3.1-7) 

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GLM [Quadro 
K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell GK107GLM [Quadro K1100M] [1028:05cc]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.259753] vgaarb: setting as boot device: PCI::01:00.0
[0.259754] vgaarb: device added: 
PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.259755] vgaarb: loaded
[0.259756] vgaarb: bridge control possible :01:00.0
[0.521399] Linux agpgart interface v0.103
[9.811401] nvidia: module license 'NVIDIA' taints kernel.
[9.817502] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[9.817842] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[9.817846] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  349.16  Wed Apr  
8 00:17:22 PDT 2015
[   11.203080] snd_hda_intel :01:00.1: Handle VGA-switcheroo audio client
[   11.679577] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input17
[   11.679625] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input18
[  103.476413] nvidia_uvm: no symbol version for nvUvmInterfaceChannelDestroy
[  103.476417] nvidia_uvm: Unknown symbol nvUvmInterfaceChannelDestroy (err -22)
[  103.476424] nvidia_uvm: no symbol version for nvUvmInterfaceQueryCaps
[  103.476425] nvidia_uvm: Unknown symbol nvUvmInterfaceQueryCaps (err -22)
[  103.476436] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryAllocSys
[  103.476437] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryAllocSys (err -22)
[  103.476443] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuMap
[  103.476444] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuMap (err -22)
[  103.476450] nvidia_uvm: no symbol version for nvUvmInterfaceKillChannel
[  103.476450] nvidia_uvm: Unknown symbol nvUvmInterfaceKillChannel (err -22)
[  103.476457] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuUnMap
[  103.476458] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuUnMap (err -22)
[  103.476465] nvidia_uvm: no symbol version for 
nvUvmInterfaceAddressSpaceCreateMirrored
[  103.476466] nvidia_uvm: Unknown symbol 
nvUvmInterfaceAddressSpaceCreateMirrored (err -22)
[  103.476493] nvidia_uvm: no symbol version for 
nvUvmInterfaceServiceDeviceInterruptsRM
[  103.476494] nvidia_uvm: Unknown symbol 
nvUvmInterfaceServiceDeviceInterruptsRM (err -22)
[  103.476501] nvidia_uvm: no symbol version for nvUvmInterfaceDeRegisterUvmOps
[  103.476502] nvidia_uvm: Unknown symbol nvUvmInterfaceDeRegisterUvmOps (err 
-22)
[  103.476508] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryFree
[  103.476508] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryFree (err -22)
[  103.476514] nvidia_uvm: no symbol version for nvUvmInterfaceGetUvmPrivRegion
[  103.476515] nvidia_uvm: Unknown symbol nvUvmInterfaceGetUvmPrivRegion (err 
-22)
[  103.476522] nvidia_uvm: no symbol version for nvUvmInterfaceGetAttachedUuids
[  103.476523] nvidia_uvm: Unknown symbol nvUvmInterfaceGetAttachedUuids (err 
-22)
[  103.476531] nvidia_uvm: no symbol 

Bug#810676: marked as done (python-keyring: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11)

[Debian Bug Tracking System]

Your message dated Sat, 23 Jan 2016 11:02:30 +
with message-id <20160123110230.285d9be4@sylvester.codehelp>
and subject line Fixed in python-keyring 7.3-1
has caused the Debian Bug report #810676,
regarding python-keyring: Unable to autolaunch a dbus-daemon without a $DISPLAY 
for X11
to be marked as done.

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

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


-- 
810676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-keyring
Version: 6.1-1
Severity: grave
Justification: renders package unusable

Processes using python-keyring 6.1 can no longer run as a daemon - a regression
from previous support, causing lava-server to halt all daemon operations.

dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: Unable 
to autolaunch a dbus-daemon without a $DISPLAY for X11

Traceback (most recent call last):
  File "/usr/bin/lava-server", line 9, in 
load_entry_point('lava-server==2015.12+5459.74d110f', 'console_scripts', 
'lava-server')()
  File "/usr/lib/python2.7/dist-packages/lava_server/manage.py", line 125, in 
main
run_with_dispatcher_class(LAVAServerDispatcher)
  File "/usr/lib/python2.7/dist-packages/lava_tool/dispatcher.py", line 45, in 
run_with_dispatcher_class
raise cls.run()
  File "/usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py", line 153, in 
run
raise SystemExit(cls().dispatch(args))
  File "/usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py", line 143, in 
dispatch
return command.invoke()
  File "/usr/lib/python2.7/dist-packages/lava_server/manage.py", line 114, in 
invoke
execute_from_command_line(['lava-server'] + self.args.command)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 353, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 345, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
348, in run_from_argv
self.execute(*args, **cmd_options)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
399, in execute
output = self.handle(*args, **options)
  File 
"/usr/lib/python2.7/dist-packages/lava_scheduler_app/management/commands/scheduler.py",
 line 46, in handle
from lava_scheduler_daemon.service import JobQueue
  File "/usr/lib/python2.7/dist-packages/lava_scheduler_daemon/service.py", 
line 28, in 
from lava_scheduler_daemon.worker import WorkerData
  File "/usr/lib/python2.7/dist-packages/lava_scheduler_daemon/worker.py", line 
31, in 
from lava_tool.authtoken import AuthenticatingServerProxy, MemoryAuthBackend
  File "/usr/lib/python2.7/dist-packages/lava_tool/authtoken.py", line 25, in 

import keyring.core
  File "/usr/lib/python2.7/dist-packages/keyring/__init__.py", line 12, in 

from .core import (set_keyring, get_keyring, set_password, get_password,
  File "/usr/lib/python2.7/dist-packages/keyring/core.py", line 158, in 
init_backend()
  File "/usr/lib/python2.7/dist-packages/keyring/core.py", line 58, in 
init_backend
set_keyring(load_config() or _get_best_keyring())
  File "/usr/lib/python2.7/dist-packages/keyring/core.py", line 66, in 
_get_best_keyring
keyrings = backend.get_all_keyring()
  File "/usr/lib/python2.7/dist-packages/keyring/util/__init__.py", line 20, in 
wrapper
func.always_returns = func(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/keyring/backend.py", line 180, in 
get_all_keyring
exceptions=TypeError))
  File "/usr/lib/python2.7/dist-packages/keyring/util/__init__.py", line 29, in 
suppress_exceptions
for callable in callables:
  File "/usr/lib/python2.7/dist-packages/keyring/backend.py", line 172, in 
is_class_viable
keyring_cls.priority
  File "/usr/lib/python2.7/dist-packages/keyring/util/properties.py", line 22, 
in __get__
return self.fget.__get__(None, owner)()
  File "/usr/lib/python2.7/dist-packages/keyring/util/XDG.py", line 18, in 
wrapper
return func(*args, **kwargs) * self.multiplier
  File "/usr/lib/python2.7/dist-packages/keyring/backends/kwallet.py", line 
134, in priority
bus = dbus.SessionBus()
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 211, in __new__
mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 100, in __new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 122, 

Processed: bug 811136 is forwarded to https://github.com/ossc-db/pg_reorg/issues/1

[Debian Bug Tracking System]

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

> forwarded 811136 https://github.com/ossc-db/pg_reorg/issues/1
Bug #811136 [pg-reorg] Incompatible with PostgreSQL 9.5
Set Bug forwarded-to-address to 'https://github.com/ossc-db/pg_reorg/issues/1'.
> thanks
Stopping processing here.

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

Bug#811138: marked as done (FTBFS: debian/control needs updating from debian/control.in)

[Debian Bug Tracking System]

Your message dated Sat, 23 Jan 2016 12:45:23 +0100
with message-id <20160123114523.ga25...@msg.df7cb.de>
and subject line Re: Bug#811138: FTBFS: debian/control needs updating from 
debian/control.in
has caused the Debian Bug report #811138,
regarding FTBFS: debian/control needs updating from debian/control.in
to be marked as done.

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

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


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

pg-partman fails to build in unstable:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
>  fakeroot debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2015-12-31 12:25:49.0 +
> +++ debian/control.8goaVz 2016-01-15 23:02:35.577075720 +
> @@ -9,9 +9,9 @@
>  Vcs-Git: https://anonscm.debian.org/git/pkg-postgresql/pg-partman.git
>  XS-Testsuite: autopkgtest
>  
> -Package: postgresql-9.4-partman
> +Package: postgresql-9.5-partman
>  Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.4, python
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.5, python
>  Description: PostgreSQL Partition Manager
>   pg_partman is a PostgreSQL extension to create and manage both time-based 
> and
>   serial-based table partition sets. Sub-partitioning is also supported. Child
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> /usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target 
> 'debian/control' failed
> make: *** [debian/control] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 2.2.2-2

Re: Martin Michlmayr 2016-01-16 <20160116001924.gb1...@jirafa.cyrius.com>
> >  Description: PostgreSQL Partition Manager
> >   pg_partman is a PostgreSQL extension to create and manage both time-based 
> > and
> >   serial-based table partition sets. Sub-partitioning is also supported. 
> > Child
> > Error: debian/control needs updating from debian/control.in. Run 
> > 'pg_buildext updatecontrol'.
> > If you are seeing this message in a buildd log, a sourceful upload is 
> > required.

This was recently fixed but not noted in the changelog.

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


signature.asc
Description: PGP signature
--- End Message ---

Bug#812094: marked as done (ros-roscpp-core: FTBFS: Could not find a package configuration file provided by "console_bridge")

[Debian Bug Tracking System]

Your message dated Sat, 23 Jan 2016 13:21:14 +0100
with message-id <20160123122114.ga14...@vis.informatik.uni-osnabrueck.de>
and subject line ros-roscpp-core: FTBFS: Could not find a package configuration 
file provided by "console_bridge"
has caused the Debian Bug report #812094,
regarding ros-roscpp-core: FTBFS: Could not find a package configuration file 
provided by "console_bridge"
to be marked as done.

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

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


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

Dear Maintainer,

ros-roscpp-core fails to build from source in unstable/amd64:

  [..]

  //Path to a program.
  NOSETESTS:FILEPATH=NOSETESTS-NOTFOUND
  
  //Path to a program.
  PYTHON_EXECUTABLE:FILEPATH=/usr/bin/python
  
  //Specify specific Python version to use ('major.minor' or 'major')
  PYTHON_VERSION:STRING=
  
  //Path to a library.
  RT_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/librt.so
  
  //Enable debian style python package layout
  SETUPTOOLS_DEB_LAYOUT:BOOL=ON
  
  //Path to a file.
  _CATKIN_GTEST_INCLUDE:FILEPATH=/usr/include/gtest/gtest.h
  
  //Path to a file.
  _CATKIN_GTEST_SRC:FILEPATH=/usr/src/gtest/src/gtest.cc
  
  //The directory containing a CMake configuration file for catkin.
  catkin_DIR:PATH=/usr/share/catkin/cmake
  
  //The directory containing a CMake configuration file for console_bridge.
  console_bridge_DIR:PATH=console_bridge_DIR-NOTFOUND
  
  //Value Computed by CMake
  
cpp_common_BINARY_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu/cpp_common
  
  //Value Computed by CMake
  
cpp_common_SOURCE_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/cpp_common
  
  //Value Computed by CMake
  
gtest_BINARY_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu/gtest
  
  //Dependencies for the target
  gtest_LIB_DEPENDS:STATIC=general;-lpthread;
  
  //Value Computed by CMake
  gtest_SOURCE_DIR:STATIC=/usr/src/gtest
  
  //Build gtest's sample programs.
  gtest_build_samples:BOOL=OFF
  
  //Build all of gtest's own tests.
  gtest_build_tests:BOOL=OFF
  
  //Disable uses of pthreads in gtest.
  gtest_disable_pthreads:BOOL=OFF
  
  //Use shared (DLL) run-time lib even when Google Test is built
  // as static lib.
  gtest_force_shared_crt:BOOL=OFF
  
  //Dependencies for the target
  gtest_main_LIB_DEPENDS:STATIC=general;-lpthread;general;gtest;
  
  //Value Computed by CMake
  
roscpp_core_BINARY_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu
  
  //Value Computed by CMake
  
roscpp_core_SOURCE_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6
  
  //Value Computed by CMake
  
roscpp_traits_BINARY_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu/roscpp_traits
  
  //Value Computed by CMake
  
roscpp_traits_SOURCE_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/roscpp_traits
  
  
  
  # INTERNAL cache entries
  
  
  //ADVANCED property for variable: Boost_DIR
  Boost_DIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_INCLUDE_DIR
  Boost_INCLUDE_DIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_LIBRARY_DIR_DEBUG
  Boost_LIBRARY_DIR_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_LIBRARY_DIR_RELEASE
  Boost_LIBRARY_DIR_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SYSTEM_LIBRARY_DEBUG
  Boost_SYSTEM_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SYSTEM_LIBRARY_RELEASE
  Boost_SYSTEM_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_THREAD_LIBRARY_DEBUG
  Boost_THREAD_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_THREAD_LIBRARY_RELEASE
  Boost_THREAD_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //catkin environment
  
CATKIN_ENV:INTERNAL=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu/catkin_generated/env_cached.sh
  
CATKIN_TEST_RESULTS_DIR:INTERNAL=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu/test_results
  

Processed: Re: Bug#811136: FTBFS: debian/control needs updating from debian/control.in

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #811136 [pg-reorg] FTBFS: debian/control needs updating from 
debian/control.in
Added tag(s) upstream.
> retitle -1 Incompatible with PostgreSQL 9.5
Bug #811136 [pg-reorg] FTBFS: debian/control needs updating from 
debian/control.in
Changed Bug title to 'Incompatible with PostgreSQL 9.5' from 'FTBFS: 
debian/control needs updating from debian/control.in'

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

Bug#812409: postgresql-prioritize: depends on unavailable postgresql-9.5.0

[Andreas Beckmann]

Package: postgresql-prioritize
Version: 1.0.4-1.1
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

After the binNMU against postgresql-9.5 it picked up a dependency on
postgresql-9.5.0 which does not exist. Probably some substvars have
changed with the new version.

Also Maintainer and Uploader are the same person with different
addresses.


Cheers,

Andreas

Bug#811136: FTBFS: debian/control needs updating from debian/control.in

[Christoph Berg]

Control: tags -1 upstream
Control: retitle -1 Incompatible with PostgreSQL 9.5

I've updated the package to 1.1.13 (found on github, released April 2015),
and tweaked bin/Makefile to support 9.5. Unfortunately this isn't enough:

--- 109,127 
  -- do reorg
  --
  \! pg_reorg --dbname=contrib_regression --no-order
! Segmentation fault (core dumped)
  \! pg_reorg --dbname=contrib_regression

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


signature.asc
Description: PGP signature

Processed: severity of 802264 is important

[Debian Bug Tracking System]

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

> severity 802264 important
Bug #802264 [camlp5] src:matita: FTBFS with OCaml 4.02.3
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed (with 1 error): FTBFS: error: 'else' without a previous 'if'

[Debian Bug Tracking System]

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

> reassign 812297 libconsole-bridge-dev
Bug #812297 [ros-ros-comm] FTBFS: error: 'else' without a previous 'if'
Bug reassigned from package 'ros-ros-comm' to 'libconsole-bridge-dev'.
No longer marked as found in versions 1.11.16-2.
Ignoring request to alter fixed versions of bug #812297 to the same values 
previously set
> affects 812297 ros-ros-comm
Bug #812297 [libconsole-bridge-dev] FTBFS: error: 'else' without a previous 'if'
Added indication that 812297 affects ros-ros-comm
> reassign 812298 libconsole-bridge-dev
Bug #812298 [ros-class-loader] FTBFS: error: 'else' without a previous 'if'
Bug reassigned from package 'ros-class-loader' to 'libconsole-bridge-dev'.
No longer marked as found in versions 0.3.2-1.
Ignoring request to alter fixed versions of bug #812298 to the same values 
previously set
> affects 812298 ros-class-loader
Bug #812298 [libconsole-bridge-dev] FTBFS: error: 'else' without a previous 'if'
Added indication that 812298 affects ros-class-loader
> block 812129 by 812298
Bug #812129 [libxmlrpcpp-dev] libxmlrpcpp-dev: /usr/include/base64.h already 
shipped by heimdal-dev
812129 was not blocked by any bugs.
812129 was not blocking any bugs.
Added blocking bug(s) of 812129: 812298
> merge 812297 812298
Bug #812297 [libconsole-bridge-dev] FTBFS: error: 'else' without a previous 'if'
Unable to merge bugs because:
blocks of #812298 is '812129' not ''
affects of #812298 is 'ros-class-loader' not 'ros-ros-comm'
Failed to merge 812297: Did not alter merged bugs.

>
End of message, stopping processing here.

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

Processed: severity of 812404 is important

[Debian Bug Tracking System]

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

> severity 812404 important
Bug #812404 [initramfs-tools] cp: failed to access 
'/tmp/user/0/mkinitramfs_2ypg84//bin/touch': Too many levels of symbolic links
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#812413: cups-driver-gutenprint: transitional arch:all package uninstallable after binNMU due to strict versioned dependency

[Andreas Beckmann]

Package: cups-driver-gutenprint
Version: 5.2.10-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 cups-driver-gutenprint : Depends: printer-driver-gutenprint (= 5.2.10-3) but 
5.2.10-3+b1 is to be installed

This is also a problem on jessie/s390x where the package got binNMUed
long ago.


Cheers,

Andreas

Bug#812400: urdfdom: FTBFS: Unable to find the requested Boost libraries: Boost version: 1.58.0

[Chris Lamb]

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

Dear Maintainer,

urdfdom fails to build from source in unstable/amd64:

  [..]

  dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var returned 
exit code 1
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


urdfdom.0.3.0-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#812404: cp: failed to access '/tmp/user/0/mkinitramfs_2ypg84//bin/touch': Too many levels of symbolic links

[Cristian Ionescu-Idbohrn]

Package: initramfs-tools
Version: 0.122
Severity: grave
Justification: renders package unusable



Setting up initramfs-tools-core (0.122) ...
Installing new version of config file /etc/initramfs-tools/initramfs.conf ...
Setting up initramfs-tools (0.122) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.122) ...
update-initramfs: Generating /boot/initrd.img-4.3.0-1-amd64
cp: failed to access '/tmp/user/0/mkinitramfs_2ypg84//bin/touch': Too many 
levels of symbolic links
E: /usr/share/initramfs-tools/hooks/fsprotect failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.3.0-1-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools



# ls -al /tmp/user/0/mkinitramfs_Rfce4o/bin/
total 2172
drwxr-xr-x  2 root root4096 Jan 23 10:53 .
drwxr-xr-x 11 root root4096 Jan 23 10:53 ..
-rwxr-xr-x  1 root root 1837392 Jan 22 08:31 busybox
-rwxr-xr-x  1 root root3963 Jan 10 18:58 cryptroot-unlock
-rwxr-xr-x  1 root root  211136 Nov  9 14:35 grep
-rwxr-xr-x  1 root root 244 May 13  2010 is_aufs
-rwxr-xr-x  1 root root  154696 Dec 20 19:02 kmod
lrwxrwxrwx  1 root root   7 Jan 23 10:53 sh -> busybox
lrwxrwxrwx  1 root root   5 Jan 23 10:53 touch -> touch
 ^^
That should probably be:

 touch -> busybox

I don't really understand what's creating the `touch' symlink.

Never mind that, I found two `touch' instances in the mkinitramfs script.
Those can also be replaced with redirections.  But, the correct shell
redirection replacement for `touch' is:

>>filepath

not:

>filepath

as the latter will also truncate the 'filepath'.

Here is a patch proposal:

--- mkinitramfs.orig2016-01-18 21:05:05.0 +0100
+++ mkinitramfs 2016-01-23 12:18:26.970456642 +0100
@@ -98,7 +98,7 @@
usage
 fi

-touch "$outfile"
+>> "$outfile"
 outfile="$(readlink -f "$outfile")"

 # And by "version" we really mean path to kernel modules
@@ -273,7 +273,7 @@
 fi

 # fstab and mtab
-touch "${DESTDIR}/etc/fstab"
+>> "${DESTDIR}/etc/fstab"
 ln -s /proc/mounts "${DESTDIR}/etc/mtab"

 # module-init-tools



Still, that is not the problem cause.  The problem occurs somewhere in
or after `update-initramfs', in a copy operation.

Downgrading to version 0.120 for now.



-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 19M Dec 23 14:43 /boot/initrd.img-4.2.0-1-amd64
-rw-r--r-- 1 root root 20M Jan 23 10:57 /boot/initrd.img-4.3.0-1-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 
root=UUID=86271730-a611-4f51-a4d0-f0028b70b2ce ro cgroup_enable=memory 
swapaccount vga=795

...

-- /etc/initramfs-tools/modules

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:
reiserfsprogs

/usr/share/initramfs-tools/hooks:
bootcdinitramfshook
busybox
cryptgnupg
cryptkeyctl
cryptopenct
cryptopensc
cryptpassdev
cryptroot
cryptroot-unlock
dmsetup
fsck
fsprotect
fuse
keymap
klibc
kmod
lvm2
mdadm
ntfs_3g
resume
thermal
udev
v86d
zz-busybox
zz_nvidia-blacklists-nouveau


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages initramfs-tools depends on:
ii  busybox-static [busybox]  1:1.22.0-17
ii  cpio  2.11+dfsg-4.1
ii  klibc-utils   2.0.4-7
ii  kmod  22-1
ii  udev  228-4+b1

Versions of packages initramfs-tools recommends:
ii  busybox-static [busybox]  1:1.22.0-17

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.1-4.2

-- no debconf information

Processed: Re: Bug#812402: texlive-base: fails to install: basename: missing operand

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ucf 3.0032
Bug #812402 [texlive-base] texlive-base: fails to install: basename: missing 
operand
Bug reassigned from package 'texlive-base' to 'ucf'.
No longer marked as found in versions texlive-base/2015.20160117-1.
Ignoring request to alter fixed versions of bug #812402 to the same values 
previously set
Bug #812402 [ucf] texlive-base: fails to install: basename: missing operand
Marked as found in versions ucf/3.0032.
> retitle 812402 ucf breaks installation of texlive-base (basename: missing 
> operand)
Bug #812402 [ucf] texlive-base: fails to install: basename: missing operand
Changed Bug title to 'ucf breaks installation of texlive-base (basename: 
missing operand)' from 'texlive-base: fails to install: basename: missing 
operand'

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

Bug#812402: texlive-base: fails to install: basename: missing operand

[Andreas Metzler]

Control: reassign -1 ucf 3.0032
Control: retitle 812402 ucf breaks installation of texlive-base (basename: 
missing operand)

On 2016-01-23 Andreas Metzler  wrote:
> Package: texlive-base
> Version: 2015.20160117-1
> Severity: serious

> texlive-base fails to install:
[...]
> Setting up texlive-base (2015.20160117-1) ...
> basename: missing operand
> Try 'basename --help' for more information.
> dpkg: error processing package texlive-base (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Processing triggers for libc-bin (2.21-6) ...
> Errors were encountered while processing:
>  texlive-base
> E: Sub-process /usr/bin/dpkg returned an error code (1)
[...]

Downgrading ucf from 3.0032 to 3.0031 made the package installable
again. The failing command is this one in texlive-base postinst:37
 ucf --purge /etc/texmf/dvips/config/config.ps

This file does not exist at this time and /etc/texmf/dvips/config/ is
an empty directory.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#812396: Info received (Bug#812396: Acknowledgement (nvidia-kernel-dkms: fail to load nvidia-uvm.))

[Pascal Obry]

And the workaround seems to be:

$ sudo modprobe --force-modversion nvidia-current-uvm

Which load the module properly.

$ lsmod | grep nvidia
nvidia_uvm 77824  0
nvidia   8445952  106 nvidia_uvm
drm   348160  6 nvidia

Regards,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://v2p.fr.eu.org
  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Processed: retitle 812398 to openldap: FTBFS: can't read /usr/lib/x86_64-linux-gnu/libhdb.la

[Debian Bug Tracking System]

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

> retitle 812398 openldap: FTBFS: can't read /usr/lib/x86_64-linux-gnu/libhdb.la
Bug #812398 [src:openldap] openldap: FTBFS on buildss.
Changed Bug title to 'openldap: FTBFS: can't read 
/usr/lib/x86_64-linux-gnu/libhdb.la' from 'openldap: FTBFS on buildss.'
> thanks
Stopping processing here.

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

Processed: 812402 metadata

[Debian Bug Tracking System]

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

> affects 812402 + texlive-base
Bug #812402 [ucf] ucf breaks installation of texlive-base (basename: missing 
operand)
Added indication that 812402 affects texlive-base
> user helm...@debian.org
Setting user to helm...@debian.org (was hel...@subdivi.de).
> usertags 812402 + rebootstrap
There were no usertags set.
Usertags are now: rebootstrap.
> thanks
Stopping processing here.

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

Bug#812418: libgd-dev,libowfat-dev: error when trying to install together

[Andreas Beckmann]

Package: libgd-dev,libowfat-dev
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.30-1
Control: found -1 2.1.1-4

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package libowfat-dev.
  Preparing to unpack .../libowfat-dev_0.30-1_amd64.deb ...
  Unpacking libowfat-dev (0.30-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libowfat-dev_0.30-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/entities.h', which is also in package 
libgd-dev:amd64 2.1.1-4+b1
  Processing triggers for libc-bin (2.21-6) ...
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libowfat-dev_0.30-1_amd64.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/include/entities.h

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.


entities.h sounds like a very generic name that could be used by many
packages:
https://packages.debian.org/search?searchon=contents=entities.h=path=unstable=any
Most of them have them prefixed and/or in a subdirectory of
/usr/include.


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


libgd-dev=2.1.1-4+b1_libowfat-dev=0.30-1.log.gz
Description: application/gzip

Processed: libgd-dev,libowfat-dev: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.30-1
Bug #812418 [libgd-dev,libowfat-dev] libgd-dev,libowfat-dev: error when trying 
to install together
There is no source info for the package 'libgd-dev' at version '0.30-1' with 
architecture ''
Marked as found in versions libowfat/0.30-1.
> found -1 2.1.1-4
Bug #812418 [libgd-dev,libowfat-dev] libgd-dev,libowfat-dev: error when trying 
to install together
There is no source info for the package 'libowfat-dev' at version '2.1.1-4' 
with architecture ''
Marked as found in versions libgd2/2.1.1-4.

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

Bug#801413: wheezy: update for polarssl's CVE-2015-5291

[Guido Günther]

Hi,
I've forward ported Thorsten's fix fow squeeze to wheezy and added some
autopkgtest (debdiff attached). Please find the debdiff attached. I'd be
happy to upload ths to security master.
Cheers,
 -- Guido
diff --git a/debian/changelog b/debian/changelog
index b52643b..b6c42f0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+polarssl (1.2.9-1~deb7u6) wheezy-security; urgency=high
+
+  * Non-maintainer upload by the LTS Security Team.
+  * CVE-2015-5291: Remote attack on clients using session tickets or SNI
+
+ -- Guido Günther   Sat, 23 Jan 2016 15:47:29 +0100
+
 polarssl (1.2.9-1~deb7u5) wheezy-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff --git a/debian/patches/CVE-2015-5291-1.patch b/debian/patches/CVE-2015-5291-1.patch
new file mode 100644
index 000..f1dc35c
--- /dev/null
+++ b/debian/patches/CVE-2015-5291-1.patch
@@ -0,0 +1,27 @@
+Index: polarssl-1.2.9/include/polarssl/ssl.h
+===
+--- polarssl-1.2.9.orig/include/polarssl/ssl.h	2015-10-22 15:42:52.0 +0200
 polarssl-1.2.9/include/polarssl/ssl.h	2015-10-22 15:44:14.0 +0200
+@@ -123,6 +123,8 @@
+ #define SSL_LEGACY_ALLOW_RENEGOTIATION  1
+ #define SSL_LEGACY_BREAK_HANDSHAKE  2
+ 
++#define SSL_MAX_HOST_NAME_LEN   255 /*!< Maximum host name defined in RFC 1035 */
++
+ /*
+  * Size of the input / output buffer.
+  * Note: the RFC defines the default size of SSL / TLS messages. If you
+Index: polarssl-1.2.9/library/ssl_tls.c
+===
+--- polarssl-1.2.9.orig/library/ssl_tls.c	2015-10-22 15:42:52.0 +0200
 polarssl-1.2.9/library/ssl_tls.c	2015-10-22 15:45:02.0 +0200
+@@ -3260,6 +3260,9 @@
+ if( ssl->hostname_len + 1 == 0 )
+ return( POLARSSL_ERR_SSL_BAD_INPUT_DATA );
+ 
++if( ssl->hostname_len > SSL_MAX_HOST_NAME_LEN )
++return( POLARSSL_ERR_SSL_BAD_INPUT_DATA );
++
+ ssl->hostname = (unsigned char *) malloc( ssl->hostname_len + 1 );
+ 
+ if( ssl->hostname == NULL )
diff --git a/debian/patches/series b/debian/patches/series
index 929750e..06dd432 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -5,3 +5,11 @@
 CVE-2014-4911.patch
 CVE-2014-8628.patch
 CVE-2015-1182.patch
+
+# fix for CVE-2015-5291
+# -> https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-5291
+CVE-2015-5291-1.patch
+# vulnerable code not present
+#CVE-2015-5291-2.patch
+#CVE-2015-5291-3.patch
+#CVE-2015-5291-4.patch
diff --git a/debian/patches/vulernable-code-not-present/CVE-2015-5291-2.patch b/debian/patches/vulernable-code-not-present/CVE-2015-5291-2.patch
new file mode 100644
index 000..f4d43ee
--- /dev/null
+++ b/debian/patches/vulernable-code-not-present/CVE-2015-5291-2.patch
@@ -0,0 +1,323 @@
+diff --git a/library/ssl_cli.c b/library/ssl_cli.c
+index f603cff..d33 100644
+--- a/library/ssl_cli.c
 b/library/ssl_cli.c
+@@ -65,6 +65,7 @@ static void ssl_write_hostname_ext( ssl_context *ssl,
+ size_t *olen )
+ {
+ unsigned char *p = buf;
++const unsigned char *end = ssl->out_msg + SSL_MAX_CONTENT_LEN;
+ 
+ *olen = 0;
+ 
+@@ -74,6 +75,12 @@ static void ssl_write_hostname_ext( ssl_context *ssl,
+ SSL_DEBUG_MSG( 3, ( "client hello, adding server name extension: %s",
+ssl->hostname ) );
+ 
++if( (size_t)(end - p) < ssl->hostname_len + 9 )
++{
++ SSL_DEBUG_MSG( 1, ( "buffer too small" ) );
++ return;
++}
++
+ /*
+  * struct {
+  * NameType name_type;
+@@ -117,6 +124,7 @@ static void ssl_write_renegotiation_ext( ssl_context *ssl,
+  size_t *olen )
+ {
+ unsigned char *p = buf;
++const unsigned char *end = ssl->out_msg + SSL_MAX_CONTENT_LEN;
+ 
+ *olen = 0;
+ 
+@@ -125,6 +133,12 @@ static void ssl_write_renegotiation_ext( ssl_context *ssl,
+ 
+ SSL_DEBUG_MSG( 3, ( "client hello, adding renegotiation extension" ) );
+ 
++if( (size_t)(end - p) < 5 + ssl->verify_data_len )
++{
++SSL_DEBUG_MSG( 1, ( "buffer too small" ) );
++return;
++}
++
+ /*
+  * Secure renegotiation
+  */
+@@ -151,6 +165,7 @@ static void ssl_write_signature_algorithms_ext( ssl_context *ssl,
+ size_t *olen )
+ {
+ unsigned char *p = buf;
++const unsigned char *end = ssl->out_msg + SSL_MAX_CONTENT_LEN;
+ size_t sig_alg_len = 0;
+ #if defined(POLARSSL_RSA_C) || defined(POLARSSL_ECDSA_C)
+ unsigned char *sig_alg_list = buf + 6;
+@@ -163,9 +178,54 @@ static void ssl_write_signature_algorithms_ext( ssl_context *ssl,
+ 
+ SSL_DEBUG_MSG( 3, ( "client hello, adding signature_algorithms extension" ) );
+ 
++#if defined(POLARSSL_RSA_C)
++#if defined(POLARSSL_SHA512_C)
++/* SHA512 + RSA signature, SHA384 + RSA signature */
++sig_alg_len += 4;
++#endif

Processed: tagging 812337, tagging 812178, tagging 812188, tagging 812085, tagging 811714

[Debian Bug Tracking System]

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

> tags 812337 + sid stretch
Bug #812337 [file-rc] file conflict with init-system-helpers
Ignoring request to alter tags of bug #812337 to the same tags previously set
> tags 812178 + sid
Bug #812178 [matita] FTBFS: The implementation hExtlib.ml does not match the 
interface hExtlib.cmi
Ignoring request to alter tags of bug #812178 to the same tags previously set
> tags 812188 + sid stretch
Bug #812188 [src:debiandoc-sgml-doc-pt-br] debiandoc-sgml-doc-pt-br: FTBFS: 
make[1]: nsgmls: Command not found
Ignoring request to alter tags of bug #812188 to the same tags previously set
> tags 812085 + sid stretch
Bug #812085 {Done: Emmanuel Bourg } 
[src:libcommons-jexl2-java] libcommons-jexl2-java: FTBFS: Error resolving 
version for plugin 'org.apache.felix:maven-bundle-plugin' from the repositories 
Ignoring request to alter tags of bug #812085 to the same tags previously set
> tags 811714 + sid
Bug #811714 [feel++] FTBFS: unknown type name 'matrix'; did you mean 
'Feel::tag::matrix'
Ignoring request to alter tags of bug #811714 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#812419: dlm-controld: fails to install, missing Breaks+Replaces: cman

[Andreas Beckmann]

Package: dlm-controld
Version: 4.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: user trei...@debian.org
Control: usertag -1 edos-file-overwrite


Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package dlm-controld.
  Preparing to unpack .../dlm-controld_4.0.2-1_amd64.deb ...
  Unpacking dlm-controld (4.0.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/dlm-controld_4.0.2-1_amd64.deb (--unpack):
   trying to overwrite '/usr/sbin/dlm_controld', which is also in package cman 
3.1.8-1.3
  Errors were encountered while processing:
   /var/cache/apt/archives/dlm-controld_4.0.2-1_amd64.deb


cheers,

Andreas


cman=3.1.8-1.3_dlm-controld=4.0.2-1.log.gz
Description: application/gzip

Bug#812396: nvidia-kernel-dkms: fail to load nvidia-uvm.

[Andreas Beckmann]

On 2016-01-23 10:24, Pascal Obry wrote:
> $ sudo modprobe nvidia-uvm
> modprobe: ERROR: could not insert 'nvidia_current_uvm': Invalid argument
> modprobe: ERROR: ../libkmod/libkmod-module.c:977 command_do() Error running 
> install command for nvidia_uvm
> modprobe: ERROR: could not insert 'nvidia_uvm': Operation not permitted
> 
> This issue was first seen in nvidia 346.96 and now in 349.16.

These were the missing bits:

[...]
> [  103.476413] nvidia_uvm: no symbol version for nvUvmInterfaceChannelDestroy
> [  103.476417] nvidia_uvm: Unknown symbol nvUvmInterfaceChannelDestroy (err 
> -22)
> [  103.476424] nvidia_uvm: no symbol version for nvUvmInterfaceQueryCaps
[...]

I had fixed this for 346.96, but apparently the fix only worked for the
nvidia-kernel-source package (which is much better suited for automatic
testing than dkms ...).


Andreas

Bug#812431: polymake: normaliz.o compile error on i386, powerpc, kfreebsd-i386

[David Bremner]

Package: polymake
Version: 3.0-1
Severity: serious
Tags: upstream
Justification: FTBFS

On several 32 bit architectures it looks liks there problems related
to the size of integers.

At a guess, it looks like the problem is the difference between
"unsigned int" and "long unsigned int" on these architectures.

Here is a sample from the build log:

/usr/bin/perl /«PKGBUILDDIR»/support/guarded_compiler.pl g++ -c -o normaliz.o 
-fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-I/«PKGBUILDDIR»/include/core-wrappers -I/«PKGBUILDDIR»/include/core 
-I/«PKGBUILDDIR»/bundled/libnormaliz/include/app-wrappers 
-I/«PKGBUILDDIR»/bundled/libnormaliz/include/apps 
-I/«PKGBUILDDIR»/include/app-wrappers -I/«PKGBUILDDIR»/include/apps -fopenmp -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security 
-ftemplate-depth-200 -Wall -Wno-strict-aliasing -Wno-parentheses -fwrapv 
-fopenmp -DPOLYMAKE_APPNAME=polytope -DNDEBUG -DPOLYMAKE_DEBUG=0 -O2 -MD 
-I/«PKGBUILDDIR»/bundled/libnormaliz/external/libnormaliz -std=c++0x 
-DPM_FORCE_TR1  -I/«PKGBUILDDIR»/bundled/libnormaliz/apps/polytope 
-I/«PKGBUILDDIR»/apps/polytope -include src/normaliz.cc 
/«PKGBUILDDIR»/bundled/libnormaliz/apps/polytope/src/perl/wrap-normaliz.cc
In file included from 
/«PKGBUILDDIR»/bundled/libnormaliz/external/libnormaliz/libnormaliz/libnormaliz-all.cpp:31:0,
 from 
/«PKGBUILDDIR»/bundled/libnormaliz/apps/polytope/src/normaliz.cc:77,
 from :0:
/«PKGBUILDDIR»/bundled/libnormaliz/external/libnormaliz/libnormaliz/full_cone.cpp:
 In instantiation of 'void 
libnormaliz::Full_Cone::compute_class_group() [with Integer = 
pm::Integer]':
/«PKGBUILDDIR»/bundled/libnormaliz/external/libnormaliz/libnormaliz/full_cone.cpp:4453:24:
   required from 'void libnormaliz::Full_Cone::dual_mode() [with 
Integer = pm::Integer]'
/«PKGBUILDDIR»/bundled/libnormaliz/external/libnormaliz/libnormaliz/cone.cpp:1998:5:
   required from 'void 
libnormaliz::Cone::compute_dual_inner(libnormaliz::ConeProperties&) 
[with IntegerFC = pm::Integer; Integer = pm::Integer]'
/«PKGBUILDDIR»/bundled/libnormaliz/external/libnormaliz/libnormaliz/cone.cpp:1849:36:
   required from 'void 
libnormaliz::Cone::compute_dual(libnormaliz::ConeProperties&) [with 
Integer = pm::Integer]'
/«PKGBUILDDIR»/bundled/libnormaliz/external/libnormaliz/libnormaliz/cone.cpp:1430:21:
   required from 'libnormaliz::ConeProperties 
libnormaliz::Cone::compute(libnormaliz::ConeProperties) [with Integer 
= pm::Integer]'
/«PKGBUILDDIR»/bundled/libnormaliz/apps/polytope/src/normaliz.cc:237:27:   
required from here
/«PKGBUILDDIR»/bundled/libnormaliz/external/libnormaliz/libnormaliz/full_cone.cpp:3658:5:
 error: conversion from 'size_t {aka unsigned int}' to 
'std::vector::value_type {aka 
pm::Integer}' is ambiguous
 ClassGroup.push_back(Support_Hyperplanes.nr_of_rows()-rk);
 ^
In file included from 
/«PKGBUILDDIR»/include/core-wrappers/polymake/Integer.h:20:0,
 from 
/«PKGBUILDDIR»/bundled/libnormaliz/apps/polytope/src/normaliz.cc:22,
 from :0:
/«PKGBUILDDIR»/include/core/polymake/Integer.h:168:4: note: candidate: 
pm::Integer::Integer(double)
Integer(double d)
^
/«PKGBUILDDIR»/include/core/polymake/Integer.h:162:4: note: candidate: 
pm::Integer::Integer(int)
Integer(int i)
^
/«PKGBUILDDIR»/include/core/polymake/Integer.h:156:4: note: candidate: 
pm::Integer::Integer(long unsigned int)
Integer(unsigned long i)
^
/«PKGBUILDDIR»/include/core/polymake/Integer.h:150:4: note: candidate: 
pm::Integer::Integer(long long int)
Integer(long long i)
^
/«PKGBUILDDIR»/include/core/polymake/Integer.h:144:4: note: candidate: 
pm::Integer::Integer(long int)
Integer(long i)
^

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

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

Versions of packages polymake depends on:
ii  g++ 4:5.3.1-1
ii  libbliss1d  0.72-5
ii  libc6   2.21-6
ii  libcdd0d094g-5
ii  libgcc1 1:5.3.1-5
ii  libgmp102:6.1.0+dfsg-2
ii  libgmpxx4ldbl   2:6.1.0+dfsg-2
ii  libgomp15.3.1-5
ii  liblrsgmp0  0.51-2
ii  libmpfr-dev 3.1.3-2
ii  libmpfr43.1.3-2
ii  libppl13v5  1:1.1-7.2
ii  libstdc++6  5.3.1-5
ii  libterm-readline-gnu-perl   1.28-2+b1
ii  libxml-libxml-perl  2.0123+dfsg-1+b1
ii  libxml-libxslt-perl 1.94-2+b1
ii  libxml-writer-perl  0.625-1
ii  libxml2 2.9.3+dfsg1-1
ii  make4.0-8.2
ii  perl5.22.1-4
ii  perl-base 

Processed: Re: Bug#812398: openldap: FTBFS: can't read /usr/lib/x86_64-linux-gnu/libhdb.la

[Debian Bug Tracking System]

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

> reassign 812398 heimdal-multidev 1.7~git20150920+dfsg-3
Bug #812398 [src:openldap] openldap: FTBFS: can't read 
/usr/lib/x86_64-linux-gnu/libhdb.la
Bug reassigned from package 'src:openldap' to 'heimdal-multidev'.
No longer marked as found in versions openldap/2.4.42+dfsg-2+b1.
Ignoring request to alter fixed versions of bug #812398 to the same values 
previously set
Bug #812398 [heimdal-multidev] openldap: FTBFS: can't read 
/usr/lib/x86_64-linux-gnu/libhdb.la
Marked as found in versions heimdal/1.7~git20150920+dfsg-3.
> retitle 812398 heimdal-multidev: broken file references in .la files
Bug #812398 [heimdal-multidev] openldap: FTBFS: can't read 
/usr/lib/x86_64-linux-gnu/libhdb.la
Changed Bug title to 'heimdal-multidev: broken file references in .la files' 
from 'openldap: FTBFS: can't read /usr/lib/x86_64-linux-gnu/libhdb.la'
> affects 812398 src:openldap
Bug #812398 [heimdal-multidev] heimdal-multidev: broken file references in .la 
files
Added indication that 812398 affects src:openldap
> thanks
Stopping processing here.

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

Processed: Creating own bug for swarp

[Debian Bug Tracking System]

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

> clone 811500 -1
Bug #811500 [cpl-plugin-visir] cpl-plugin-visir: does not work
Bug 811500 cloned as bug 812432
> reassign -1 swarp 2.38.0+dfsg-2
Bug #812432 [cpl-plugin-visir] cpl-plugin-visir: does not work
Bug reassigned from package 'cpl-plugin-visir' to 'swarp'.
No longer marked as found in versions cpl-plugin-visir/4.1.0+dfsg-1.
Ignoring request to alter fixed versions of bug #812432 to the same values 
previously set
Bug #812432 [swarp] cpl-plugin-visir: does not work
Marked as found in versions swarp/2.38.0+dfsg-2.
> retitle -1 swarp: WEIGHT_TYPE MAP_RMS does not work
Bug #812432 [swarp] cpl-plugin-visir: does not work
Changed Bug title to 'swarp: WEIGHT_TYPE MAP_RMS does not work' from 
'cpl-plugin-visir: does not work'
> severity -1 important
Bug #812432 [swarp] swarp: WEIGHT_TYPE MAP_RMS does not work
Severity set to 'important' from 'serious'
> affects -1 cpl-plugin-visir
Bug #812432 [swarp] swarp: WEIGHT_TYPE MAP_RMS does not work
Added indication that 812432 affects cpl-plugin-visir
> thanks
Stopping processing here.

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

Bug#812345: fixed in git

[Pirate Praveen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Control: tags -1 pending

removed mysql2 gem dependency.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWo6zwAAoJEM4fnGdFEsIqiyMP/jxakkxG0HfpYjpDl0FX3yg7
udZtMS+fJbeY7NllwIGqit7O3E7hWpZ6OojLp9PKhI3bYDAFDkhd9hKnmcAJWBBd
kOwgX2S2q9R0tZ04m/YfP8bqTke2SYCrFv+XCVrIasVKBoqd+zb16Zp91mtzQWId
KBO6N7MU5J3UDGlqMxEQ3QlxMzPQU7Pkf0IPiZoLlB520aMnM7rlF+vnydzfLBm2
hFb649m2Z/hckbdkfh7bflFJdRMBChlGnNAo331O5UwMqwH5Le5de9ZGtf8syEz5
uggC1p5JI6Ev5Y5Jqh3jS/M9flEf9PKBy3eQ/aXP2jDz7dg2py4JDcNjEX7ELoLo
EKSsyPBAuFXcUXjSvn/SSaqTiZFP5gz4K4233+cVH5Bj6O5wJzHNKz+oJdz3MzGT
NMbh8aVvlNX2G0WqCyHyG7J5IEo0BYL2aJqWtb7D/eVSfUWOE6BynG+jJrw7duo9
VW+LtkBgIQKJ/pzDhwqI//oXZafDngch4qHxeWdDo7Da67mu+X9mrfRiRT/6IsLB
Rj3WjLrZ/9TldrXodBn2WZ2hg1YnYLztTJEKqwQ1h5kpSTnOLzU2+/o5xb5ui9lh
jMK1DwFGce1Qq3522oGpnuaWlHVjmd/2FJaD56hzn501HEMycoYnPjw6cJdD1CIQ
sg6zvPV1NPdLj/jyEjqp
=wKP5
-END PGP SIGNATURE-

Bug#812452: python-openstackclient-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc-base/python-openstackclient

[Andreas Beckmann]

Package: python-openstackclient-doc
Version: 2.0.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python-openstackclient-doc.
  Preparing to unpack .../python-openstackclient-doc_2.0.0-2_all.deb ...
  Unpacking python-openstackclient-doc (2.0.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-openstackclient-doc_2.0.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/python-openstackclient', which is 
also in package python-openstackclient 1.7.1-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Processing triggers for libc-bin (2.21-6) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/python-openstackclient-doc_2.0.0-2_all.deb


cheers,

Andreas


python-openstackclient=1.7.1-1_python-openstackclient-doc=2.0.0-2.log.gz
Description: application/gzip

Bug#812453: libsxclient3: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/sxclient/libsxf_undelete-12.so

[Andreas Beckmann]

Package: libsxclient3
Version: 2.0+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libsxclient3.
  Preparing to unpack .../libsxclient3_2.0+ds-1_amd64.deb ...
  Unpacking libsxclient3 (2.0+ds-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libsxclient3_2.0+ds-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/sxclient/libsxf_undelete-12.so', which is also in 
package libsxclient2 1.2+ds-1
  Processing triggers for libc-bin (2.21-6) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libsxclient3_2.0+ds-1_amd64.deb


cheers,

Andreas


libsxclient2=1.2+ds-1_libsxclient3=2.0+ds-1.log.gz
Description: application/gzip

Bug#812458: debsums installation fails with basename: missiong operand

[Alf Gaida]

Package: debsums
Version: 2.1.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,
the installation of debsums stops with
LANG=C apt install debsums
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  debsums
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/48.4 kB of archives.
After this operation, 121 kB of additional disk space will be used.
Selecting previously unselected package debsums.
(Reading database ... 479060 files and directories currently installed.)
Preparing to unpack .../archives/debsums_2.1.2_all.deb ...
Unpacking debsums (2.1.2) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for siduction-dynamic-dms (2016.01.04.3) ...
Setting up debsums (2.1.2) ...
basename: missing operand
Try 'basename --help' for more information.
dpkg: error processing package debsums (--configure):
 subprocess installed post-installation script returned error exit
status 1 Processing triggers for siduction-dynamic-dms
(2016.01.04.3) ... Errors were encountered while processing:
 debsums
E: Sub-process /usr/bin/dpkg returned an error code (1)

It seems, that the ucf calls in postinst cause this behaviour.

Greetz Alf



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

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

Versions of packages debsums depends on:
ii  dpkg  1.18.4
ii  libdpkg-perl  1.18.4
ii  libfile-fnmatch-perl  0.02-2+b2
ii  perl  5.22.1-4
ii  ucf   3.0032

debsums recommends no packages.

debsums suggests no packages.

-- no debconf information


-- 
Alf Gaida
BDBF C688 EFAD BA89 5A9F  464B CD28 0A0B 4D72 827C


pgp8XneIxG0fh.pgp
Description: Digitale Signatur von OpenPGP

Bug#812396: marked as done (nvidia-kernel-dkms: fail to load nvidia-uvm.)

[Debian Bug Tracking System]

Your message dated Sat, 23 Jan 2016 17:45:30 +
with message-id 
and subject line Bug#812396: fixed in nvidia-graphics-drivers 349.16-2
has caused the Debian Bug report #812396,
regarding nvidia-kernel-dkms: fail to load nvidia-uvm.
to be marked as done.

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

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


-- 
812396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-kernel-dkms
Version: 349.16-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

The issue is reported by programs like darktable, for example here is
the ouptut on the console:

$ darktable
modprobe: ERROR: could not insert 'nvidia_current_uvm': Invalid argument
modprobe: ERROR: ../libkmod/libkmod-module.c:977 command_do() Error running 
install command for nvidia_uvm
modprobe: ERROR: could not insert 'nvidia_uvm': Operation not permitted

The same output can be reproduced by just trying to modprob nvidia-uvm:

$ sudo modprobe nvidia-uvm
modprobe: ERROR: could not insert 'nvidia_current_uvm': Invalid argument
modprobe: ERROR: ../libkmod/libkmod-module.c:977 command_do() Error running 
install command for nvidia_uvm
modprobe: ERROR: could not insert 'nvidia_uvm': Operation not permitted

This issue was first seen in nvidia 346.96 and now in 349.16.

So current version for testing 340.96-4 does not have this issue.

Please let me know if you need me do some more testing.

Regards,

-- Package-specific info:
uname -a:
Linux pascal 4.3.0-1-amd64 #1 SMP Debian 4.3.3-7 (2016-01-19) x86_64 GNU/Linux

/proc/version:
Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160114 (Debian 5.3.1-6) ) #1 SMP Debian 4.3.3-7 (2016-01-19)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  349.16  Wed Apr  8 00:17:22 PDT 
2015
GCC version:  gcc version 5.3.1 20160121 (Debian 5.3.1-7) 

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GLM [Quadro 
K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell GK107GLM [Quadro K1100M] [1028:05cc]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.259753] vgaarb: setting as boot device: PCI::01:00.0
[0.259754] vgaarb: device added: 
PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.259755] vgaarb: loaded
[0.259756] vgaarb: bridge control possible :01:00.0
[0.521399] Linux agpgart interface v0.103
[9.811401] nvidia: module license 'NVIDIA' taints kernel.
[9.817502] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[9.817842] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[9.817846] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  349.16  Wed Apr  
8 00:17:22 PDT 2015
[   11.203080] snd_hda_intel :01:00.1: Handle VGA-switcheroo audio client
[   11.679577] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input17
[   11.679625] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input18
[  103.476413] nvidia_uvm: no symbol version for nvUvmInterfaceChannelDestroy
[  103.476417] nvidia_uvm: Unknown symbol nvUvmInterfaceChannelDestroy (err -22)
[  103.476424] nvidia_uvm: no symbol version for nvUvmInterfaceQueryCaps
[  103.476425] nvidia_uvm: Unknown symbol nvUvmInterfaceQueryCaps (err -22)
[  103.476436] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryAllocSys
[  103.476437] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryAllocSys (err -22)
[  103.476443] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuMap
[  103.476444] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuMap (err -22)
[  103.476450] nvidia_uvm: no symbol version for nvUvmInterfaceKillChannel
[  103.476450] nvidia_uvm: Unknown symbol nvUvmInterfaceKillChannel (err -22)
[  103.476457] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuUnMap
[  103.476458] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuUnMap (err -22)
[  103.476465] nvidia_uvm: no symbol version for 
nvUvmInterfaceAddressSpaceCreateMirrored
[  103.476466] nvidia_uvm: Unknown symbol 
nvUvmInterfaceAddressSpaceCreateMirrored (err -22)
[  

Bug#811139: marked as done (FTBFS: debian/control needs updating from debian/control.in)

[Debian Bug Tracking System]

Your message dated Sat, 23 Jan 2016 16:55:37 +
with message-id 
and subject line Bug#811139: fixed in repmgr 3.0.3-2
has caused the Debian Bug report #811139,
regarding FTBFS: debian/control needs updating from debian/control.in
to be marked as done.

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

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


-- 
811139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: repmgr
Version: 3.0.2-2
Severity: serious

repmgr fails to build in unstable:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> dpkg-buildpackage: host architecture amd64
>  fakeroot debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2015-10-16 16:02:40.0 +
> +++ debian/control.HkK0AX 2016-01-15 15:39:53.580859882 +
> @@ -68,11 +68,11 @@
>  Description: transitional dummy package
>   This is a transitional dummy package. It can safely be removed.
>  
> -Package: postgresql-9.4-repmgr
> +Package: postgresql-9.5-repmgr
>  Architecture: any
> -Depends: postgresql-9.4, repmgr-common (>= ${source:Version}), 
> ${misc:Depends}, ${shlibs:Depends}
> +Depends: postgresql-9.5, repmgr-common (>= ${source:Version}), 
> ${misc:Depends}, ${shlibs:Depends}
>  Suggests: rsync
> -Description: replication manager for PostgreSQL 9.4
> +Description: replication manager for PostgreSQL 9.5
>   Since version 9.0, PostgreSQL allow you to have replicated hot
>   standby servers which you can query and/or use for high availability.
>   While the main components of the feature are included with
> @@ -82,15 +82,15 @@
>   repmgr allows you to monitor and manage your replicated PostgreSQL
>   databases as a single cluster.
>   .
> - This package contains repmgr for PostgreSQL 9.4.
> + This package contains repmgr for PostgreSQL 9.5.
>  
> -Package: postgresql-9.4-repmgr-dbg
> +Package: postgresql-9.5-repmgr-dbg
>  Section: debug
>  Architecture: any
> -Depends: postgresql-9.4-repmgr (= ${binary:Version}), ${misc:Depends}, 
> ${shlibs:Depends}
> +Depends: postgresql-9.5-repmgr (= ${binary:Version}), ${misc:Depends}, 
> ${shlibs:Depends}
>  Replaces: repmgr-dbg (<< 3.0.1-1)
>  Breaks: repmgr-dbg (<< 3.0.1-1)
> -Description: debug symbols for repmgr for PostgreSQL 9.4
> +Description: debug symbols for repmgr for PostgreSQL 9.5
>   Since version 9.0, PostgreSQL allow you to have replicated hot
>   standby servers which you can query and/or use for high availability.
>   While the main components of the feature are included with
> @@ -100,5 +100,5 @@
>   repmgr allows you to monitor and manage your replicated PostgreSQL
>   databases as a single cluster.
>   .
> - This package contains debug symbols for repmgr for PostgreSQL 9.4.
> + This package contains debug symbols for repmgr for PostgreSQL 9.5.
>  
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> /usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target 
> 'debian/control' failed
> make: *** [debian/control] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: repmgr
Source-Version: 3.0.3-2

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

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

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

Debian distribution maintenance software
pp.
Marco Nenciarini  (supplier of updated repmgr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 23 Jan 2016 10:08:27 +0100
Source: repmgr
Binary: repmgr-common repmgr repmgr-dbg postgresql-9.5-repmgr 
postgresql-9.5-repmgr-dbg
Architecture: source amd64 all
Version: 3.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Marco Nenciarini 
Changed-By: Marco Nenciarini 
Description:
 postgresql-9.5-repmgr - replication manager for PostgreSQL 9.5

Bug#812337: init-system-helpers: file conflict with openrc: /usr/sbin/update-rc.d

[Andreas Henriksson]

Hello Michael Prokop.

On Sat, Jan 23, 2016 at 12:07:58AM +0100, Michael Prokop wrote:
> I've worked on a patch for file-rc which takes care of diverting the
> relevant invoke-rc.d. + update-rc.d files (following instructions as
> documented at
> https://www.debian.org/doc/debian-policy/ap-pkg-diversions.html), so
> file-rc can be co-installed with init-system-helpers >=1.25.
> 

Thanks for looking into this.

> I'd highly appreciate a review and if there are no objections I'd
> upload this then.

Overall looks good to me and seems to install fine in a container here
(after init-system-helpers has been rebuilt with a versioned conflict).

There's one question on my mind though, shouldn't the upgrade case
be versioned? eg. so in additional future releases you don't try to
divert when you've already diverted. You only want the diversion to
happen once when upgrading to this exact version you're preparing now.

Regards,
Andreas Henriksson

Bug#812442: django-compat: FTBFS: ImportError: No module named django_nose

[Chris Lamb]

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

Dear Maintainer,

django-compat fails to build from source in unstable/amd64:

  [..]

 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160123210359.IB8zm9ZnDR/django-compat-1.0.8'
  python runtests.py
  Traceback (most recent call last):
File "runtests.py", line 61, in 
  runtests(*sys.argv[1:])
File "runtests.py", line 53, in runtests
  from django_nose import NoseTestSuiteRunner
  ImportError: No module named django_nose
  debian/rules:8: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160123210359.IB8zm9ZnDR/django-compat-1.0.8'
  debian/rules:5: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


django-compat.1.0.8-2.unstable.amd64.log.txt.gz
Description: Binary data

Processed: limit source to dlm, tagging 812419

[Debian Bug Tracking System]

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

> limit source dlm
Limiting to bugs with field 'source' containing at least one of 'dlm'
Limit currently set to 'source':'dlm'

> tags 812419 + pending
Bug #812419 [dlm-controld] dlm-controld: fails to install, missing 
Breaks+Replaces: cman
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#812448: rustc: FTBFS: =format-security: No such file or directory

[Aaron M. Ucko]

Source: rustc
Version: 1.6.0+dfsg1-1
Severity: serious
Justification: fails to build from source

Builds of rustc have been failing with errors along the lines of

  gcc -I/«BUILDDIR»/rustc-1.6.0+dfsg1/src/compiler-rt/lib 
-I/«BUILDDIR»/rustc-1.6.0+dfsg1/src/compiler-rt/include -Wall -g -fPIC -m32 -g 
-O2 -fstack-protector-strong -Wformat =format-security -std=c99 -c -o 
/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/rt/compiler-rt/triple/builtins/i386/SubDir.lib__builtins/ashlti3.o
 /«BUILDDIR»/rustc-1.6.0+dfsg1/src/compiler-rt/lib/builtins/ashlti3.c
  gcc: error: =format-security: No such file or directory
  Makefile:267: recipe for target 
'/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/rt/compiler-rt/triple/builtins/i386/SubDir.lib__builtins/ashlti3.o'
 failed
  make[3]: *** 
[/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/rt/compiler-rt/triple/builtins/i386/SubDir.lib__builtins/ashlti3.o]
 Error 1
  make[3]: Leaving directory '/«BUILDDIR»/rustc-1.6.0+dfsg1/src/compiler-rt'
  /«BUILDDIR»/rustc-1.6.0+dfsg1/mk/rt.mk:364: recipe for target 
'i686-unknown-linux-gnu/rt/libcompiler-rt.a' failed
  make[2]: *** [i686-unknown-linux-gnu/rt/libcompiler-rt.a] Error 2

The issue appears to stem from logic in mk/rt.mk that tries to strip
-Werror from CFLAGS via $(subst ...), which is happy to replace partial
words, and as such interacts poorly with typical hardening flags.  I'd
suggest instead using $(filter-out ...).

Could you please take a look?

Thanks!

Bug#812459: python3-stem: fails to upgrade from 'testing' - trying to overwrite /usr/bin/tor-prompt

[Andreas Beckmann]

Package: python3-stem
Version: 1.4.1b-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python3-stem.
  Preparing to unpack .../python3-stem_1.4.1b-2_all.deb ...
  Unpacking python3-stem (1.4.1b-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-stem_1.4.1b-2_all.deb (--unpack):
   trying to overwrite '/usr/bin/tor-prompt', which is also in package 
python-stem 1.2.2-1.1
  Processing triggers for mime-support (3.58) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-stem_1.4.1b-2_all.deb


cheers,

Andreas


python-stem=1.2.2-1.1_python3-stem=1.4.1b-2.log.gz
Description: application/gzip

Processed: tagging 812224

[Debian Bug Tracking System]

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

> tags 812224 - help
Bug #812224 [wicd-curses] wicd-curses: IndexError: list index out of range
Removed tag(s) help.
> thanks
Stopping processing here.

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

Processed: forcemerge

[Debian Bug Tracking System]

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

> # second attempt
> reassign 812145 initramfs-tools-core
Bug #812145 {Done: Ben Hutchings } [initramfs-tools-core] 
sysvinit: 2.88dsf-59.3 generates bad initrd.img and boot on hppa
Bug #811479 {Done: Ben Hutchings } [initramfs-tools-core] 
boot fails in "run-init -n ..."
Bug #811566 {Done: Ben Hutchings } [initramfs-tools-core] 
run-init: opening console: No such file or directory
Bug #812116 {Done: Ben Hutchings } [initramfs-tools-core] 
newly built initrd complains about missing init
Ignoring request to reassign bug #812145 to the same package
Ignoring request to reassign bug #811479 to the same package
Ignoring request to reassign bug #811566 to the same package
Ignoring request to reassign bug #812116 to the same package
> forcemerge 811479 812145
Bug #811479 {Done: Ben Hutchings } [initramfs-tools-core] 
boot fails in "run-init -n ..."
Bug #811566 {Done: Ben Hutchings } [initramfs-tools-core] 
run-init: opening console: No such file or directory
Bug #812116 {Done: Ben Hutchings } [initramfs-tools-core] 
newly built initrd complains about missing init
Bug #812145 {Done: Ben Hutchings } [initramfs-tools-core] 
sysvinit: 2.88dsf-59.3 generates bad initrd.img and boot on hppa
Bug #811566 {Done: Ben Hutchings } [initramfs-tools-core] 
run-init: opening console: No such file or directory
Bug #812116 {Done: Ben Hutchings } [initramfs-tools-core] 
newly built initrd complains about missing init
Bug #812145 {Done: Ben Hutchings } [initramfs-tools-core] 
sysvinit: 2.88dsf-59.3 generates bad initrd.img and boot on hppa
Merged 811479 811566 812116 812145
> thanks
Stopping processing here.

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

Processed (with 1 error): [dave.ang...@bell.net: Re: Please check initramfs-tools 0.122]

[Debian Bug Tracking System]

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

> reassign 812145 initramfs-tools
Bug #812145 [sysvinit] sysvinit: 2.88dsf-59.3 generates bad initrd.img and boot 
on hppa
Bug reassigned from package 'sysvinit' to 'initramfs-tools'.
No longer marked as found in versions 2.88dsf-59.3+b1.
Ignoring request to alter fixed versions of bug #812145 to the same values 
previously set
> forcemerge 811479 812145
Bug #811479 {Done: Ben Hutchings } [initramfs-tools-core] 
boot fails in "run-init -n ..."
Bug #811566 {Done: Ben Hutchings } [initramfs-tools-core] 
run-init: opening console: No such file or directory
Bug #812116 {Done: Ben Hutchings } [initramfs-tools-core] 
newly built initrd complains about missing init
Unable to merge bugs because:
package of #812145 is 'initramfs-tools' not 'initramfs-tools-core'
Failed to forcibly merge 811479: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#812431: polymake ticket notification: #891: normaliz.o compilation failure on several 32bit debian architectures

[polymake Trac site]

#891: normaliz.o compilation failure on several 32bit debian architectures
+-
 Reporter:  bremner |  Owner:  benmuell
 Type:  defect  | Status:  new
 Priority:  major   |  Milestone:
Component:  bundled-extensions  |Version:  development
 Keywords:  |
+-
 Dear Polymake Team;

 I've just filed a serious bug on Debian's bug tracker.
 This is probably a priority to fix for you as well as it will effect
 Ubuntu/i386

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

--
Ticket URL: 
polymake 
The polymake project

Bug#812450: android-platform-frameworks-native-headers: fails to upgrade from 'sid' - trying to overwrite /usr/include/android/android/rect.h

[Andreas Beckmann]

Package: android-platform-frameworks-native-headers
Version: 1:6.0.0+r26-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package 
android-platform-frameworks-native-headers.
  Preparing to unpack 
.../android-platform-frameworks-native-headers_1%3a6.0.0+r26-1_all.deb ...
  Unpacking android-platform-frameworks-native-headers (1:6.0.0+r26-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/android-platform-frameworks-native-headers_1%3a6.0.0+r26-1_all.deb
 (--unpack):
   trying to overwrite '/usr/include/android/android/rect.h', which is also in 
package android-libutils-dev 21-3+b3
  Errors were encountered while processing:
   
/var/cache/apt/archives/android-platform-frameworks-native-headers_1%3a6.0.0+r26-1_all.deb


cheers,

Andreas


android-libutils-dev=21-3+b3_android-platform-frameworks-native-headers=1%6.0.0+r26-1.log.gz
Description: application/gzip

Processed: reassign 812145 to initramfs-tools-core, forcibly merging 811479 812145

[Debian Bug Tracking System]

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

> reassign 812145 initramfs-tools-core
Bug #812145 [initramfs-tools] sysvinit: 2.88dsf-59.3 generates bad initrd.img 
and boot on hppa
Bug reassigned from package 'initramfs-tools' to 'initramfs-tools-core'.
Ignoring request to alter found versions of bug #812145 to the same values 
previously set
Ignoring request to alter fixed versions of bug #812145 to the same values 
previously set
> forcemerge 811479 812145
Bug #811479 {Done: Ben Hutchings } [initramfs-tools-core] 
boot fails in "run-init -n ..."
Bug #811566 {Done: Ben Hutchings } [initramfs-tools-core] 
run-init: opening console: No such file or directory
Bug #812116 {Done: Ben Hutchings } [initramfs-tools-core] 
newly built initrd complains about missing init
Bug #812145 [initramfs-tools-core] sysvinit: 2.88dsf-59.3 generates bad 
initrd.img and boot on hppa
Severity set to 'critical' from 'important'
Marked Bug as done
Added indication that 812145 affects xen-tools
Marked as fixed in versions initramfs-tools/0.122.
Marked as found in versions initramfs-tools/0.121.
Added tag(s) patch.
Bug #811566 {Done: Ben Hutchings } [initramfs-tools-core] 
run-init: opening console: No such file or directory
Bug #812116 {Done: Ben Hutchings } [initramfs-tools-core] 
newly built initrd complains about missing init
Merged 811479 811566 812116 812145
> thanks
Stopping processing here.

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

Bug#812456: davfs2: dies with stack smashing error; can't mount

[Sean Whitton]

Package: davfs2
Version: 1.5.2-1.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After a recent upgrade to davfs2 (I am tracking Debian Testing), I can
no longer mount my WebDAV share with davfs2.  When I run

mount ~/lib/fm

the program exits with the following error:

*** stack smashing detected ***: /sbin/mount.davfs terminated

and the WebDAV share is not mounted.

Attached to this e-mail is the full output of the program.  Below I have
included the relevant configuration file snippets.

Please excuse me if a bug severity of "grave" is not appropriate.  The
package is currently unusable for me, but I don't know if it renders
it unusable for others.

Regards,
 Sean Whitton

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: i386 (i686)

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

Versions of packages davfs2 depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.58
ii  libc6  2.21-6
ii  libneon27  0.30.1-2+b1

davfs2 recommends no packages.

davfs2 suggests no packages.

-- Configuration Files that I have modified:
/etc/fstab (snippet):

https://myfiles.messagingengine.com/ /home/swhitton/lib/fm davfs 
user,noauto,uid=swhitton,file_mode=600,dir_mode=700 0 1

/home/swhitton/.davfs2/secrets:

https://myfiles.messagingengine.com/ "" ""

-- debconf information:
  davfs2/non_root_users_confimed:
* davfs2/suid_file: true
  davfs2/group_name: davfs2
  davfs2/new_group: true
  davfs2/user_name: davfs2
  davfs2/new_user: true
artemis ~ % mount lib/fm
*** stack smashing detected ***: /sbin/mount.davfs terminated
=== Backtrace: =
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x69439)[0xb7545439]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__fortify_fail+0x37)[0xb75d4807]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0xf87ca)[0xb75d47ca]
/sbin/mount.davfs[0x8059dc5]
/sbin/mount.davfs[0x804bbdd]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xde)[0xb74f470e]
/sbin/mount.davfs[0x804d8fb]
=== Memory map: 
08048000-08068000 r-xp  fb:00 17057181   /usr/sbin/mount.davfs
08068000-08069000 r--p 0001f000 fb:00 17057181   /usr/sbin/mount.davfs
08069000-0806a000 rw-p 0002 fb:00 17057181   /usr/sbin/mount.davfs
08dd-08df5000 rw-p  00:00 0  [heap]
b4e4b000-b4e57000 r-xp  fb:00 45482067   
/lib/i386-linux-gnu/i686/cmov/libnss_files-2.21.so
b4e57000-b4e58000 r--p b000 fb:00 45482067   
/lib/i386-linux-gnu/i686/cmov/libnss_files-2.21.so
b4e58000-b4e59000 rw-p c000 fb:00 45482067   
/lib/i386-linux-gnu/i686/cmov/libnss_files-2.21.so
b4e59000-b4e64000 r-xp  fb:00 45482072   
/lib/i386-linux-gnu/i686/cmov/libnss_nis-2.21.so
b4e64000-b4e65000 r--p a000 fb:00 45482072   
/lib/i386-linux-gnu/i686/cmov/libnss_nis-2.21.so
b4e65000-b4e66000 rw-p b000 fb:00 45482072   
/lib/i386-linux-gnu/i686/cmov/libnss_nis-2.21.so
b4e66000-b4e7d000 r-xp  fb:00 45482059   
/lib/i386-linux-gnu/i686/cmov/libnsl-2.21.so
b4e7d000-b4e7e000 r--p 00016000 fb:00 45482059   
/lib/i386-linux-gnu/i686/cmov/libnsl-2.21.so
b4e7e000-b4e7f000 rw-p 00017000 fb:00 45482059   
/lib/i386-linux-gnu/i686/cmov/libnsl-2.21.so
b4e7f000-b4e81000 rw-p  00:00 0 
b4e81000-b4e88000 r-xp  fb:00 45482061   
/lib/i386-linux-gnu/i686/cmov/libnss_compat-2.21.so
b4e88000-b4e89000 ---p 7000 fb:00 45482061   
/lib/i386-linux-gnu/i686/cmov/libnss_compat-2.21.so
b4e89000-b4e8a000 r--p 7000 fb:00 45482061   
/lib/i386-linux-gnu/i686/cmov/libnss_compat-2.21.so
b4e8a000-b4e8b000 rw-p 8000 fb:00 45482061   
/lib/i386-linux-gnu/i686/cmov/libnss_compat-2.21.so
b4e8b000-b5015000 r--p  fb:00 17057124   /usr/lib/locale/locale-archive
b5015000-b5019000 rw-p  00:00 0 
b5019000-b5035000 r-xp  fb:00 45351390   
/lib/i386-linux-gnu/libgcc_s.so.1
b5035000-b5036000 rw-p 0001b000 fb:00 45351390   
/lib/i386-linux-gnu/libgcc_s.so.1
b5036000-b519c000 r-xp  fb:00 17052224   
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.21
b519c000-b519d000 ---p 00166000 fb:00 17052224   
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.21
b519d000-b51a2000 r--p 00166000 fb:00 17052224   
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.21
b51a2000-b51a3000 rw-p 0016b000 fb:00 17052224   
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.21
b51a3000-b51a6000 rw-p  00:00 0 
b51a6000-b51f1000 r-xp  fb:00 45482054   
/lib/i386-linux-gnu/i686/cmov/libm-2.21.so
b51f1000-b51f2000 r--p 0004a000 fb:00 45482054   
/lib/i386-linux-gnu/i686/cmov/libm-2.21.so
b51f2000-b51f3000 rw-p 0004b000 fb:00 45482054   
/lib/i386-linux-gnu/i686/cmov/libm-2.21.so
b51f3000-b5219000 r-xp  fb:00 45350950   
/lib/i386-linux-gnu/liblzma.so.5.0.0
b5219000-b521b000 r--p 00026000 fb:00 45350950   

Bug#812458: debsums installation fails with basename: missiong operand

[Axel Beckert]

Control: reassign -1 ucf
Control: forcemerge 812402 -1 
Control: affects -1 + debsums

Hi Alf,

thanks for the bug report.

Alf Gaida wrote:
> Setting up debsums (2.1.2) ...
> basename: missing operand
> Try 'basename --help' for more information.
> dpkg: error processing package debsums (--configure):
>  subprocess installed post-installation script returned error exit
> status 1 Processing triggers for siduction-dynamic-dms
> (2016.01.04.3) ... Errors were encountered while processing:
>  debsums
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> It seems, that the ucf calls in postinst cause this behaviour.

Correct. Which is the reason why this is a bug in ucf and not in
debsums itself. Reassigning accordingly and marking debsums as
affected.

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

Bug#812462: ganglia: [FTBFS, patch] out-of-date and missing build-depends

[Michael Tautschnig]

Package: ganglia
Version: 3.6.0-6
Usertags: goto-cc
Tags: patch
Severity: serious
Justification: FTBFS

As of its version 1.5.4-3, rrdtool no longer Provides: librrd2-dev from
librrd-dev. This breaks the build of ganglia. Changing the build-dependency to
librrd-dev fixes this first problem.

The build then fails with

./configure: line 12863: PKG_PROG_PKG_CONFIG: command not found

Checking for apr
./configure: line 12978: syntax error near unexpected token `APR,apr-1'
./configure: line 12978: `  PKG_CHECK_MODULES(APR,apr-1)'

and

Checking for zlib
checking zlib.h usability... no
checking zlib.h presence... no
checking for zlib.h... no
checking for deflate in -lz... no
zlib library not configured properly

The attached patch addresses all these problems, and the build succeeds
eventually.

Best,
Michael

diff -urN a/debian/control b/debian/control
--- a/debian/control2014-09-11 10:59:34.0 +0100
+++ b/debian/control2016-01-23 13:51:49.0 +
@@ -4,7 +4,7 @@
 Maintainer: Debian Monitoring Maintainers 

 Uploaders: Stuart Teasdale , Daniel Pocock 
 Homepage: http://ganglia.info/
-Build-Depends: debhelper (>> 9.0.0), librrd2-dev, autoconf, autotools-dev, 
automake, libapr1-dev, libexpat1-dev, python-dev, libconfuse-dev, po-debconf, 
libxml2-dev, libdbi0-dev, libpcre3-dev, gperf, libtool, rsync, libkvm-dev 
[kfreebsd-any]
+Build-Depends: debhelper (>> 9.0.0), librrd-dev, autoconf, autotools-dev, 
automake, libapr1-dev, libexpat1-dev, python-dev, libconfuse-dev, po-debconf, 
libxml2-dev, libdbi0-dev, libpcre3-dev, gperf, libtool, rsync, libkvm-dev 
[kfreebsd-any], pkg-config, libz-dev
 Standards-Version: 3.9.4
 Vcs-Git: git://anonscm.debian.org/pkg-monitoring/ganglia.git
 Vcs-Browser: http://anonscm.debian.org/cgit/pkg-monitoring/ganglia.git


signature.asc
Description: PGP signature

Processed (with 1 error): found 812371 in 0.2.3-0.1, merging 812298 812297, found 812297 in 0.3.0-3

[Debian Bug Tracking System]

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

> found 812371 0.2.3-0.1
Bug #812371 [rpcbind] nis: NIS is started before rpcbind since rpcbind was 
migrated to systemd
Marked as found in versions rpcbind/0.2.3-0.1.
> merge 812298 812297
Bug #812298 [libconsole-bridge-dev] FTBFS: error: 'else' without a previous 'if'
Unable to merge bugs because:
blocks of #812297 is '' not '812129'
affects of #812297 is 'ros-ros-comm' not 'ros-class-loader'
Failed to merge 812298: Did not alter merged bugs.

> found 812297 0.3.0-3
Bug #812297 [libconsole-bridge-dev] FTBFS: error: 'else' without a previous 'if'
Marked as found in versions console-bridge/0.3.0-3.
> thanks
Stopping processing here.

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

Bug#812398: openldap: FTBFS: can't read /usr/lib/x86_64-linux-gnu/libhdb.la

[Jelmer Vernooij]

On Sun, Jan 24, 2016 at 11:44:53AM +1100, Brian May wrote:
> Ryan Tandy  writes:
> 
> > Since the .la files moved from /usr/lib/$arch to /usr/lib/$arch/heimdal, 
> > looks like their contents also need to be updated.
> 
> According to debian/changelog I deleted the *.la files in version
> 1.4.0-5 with a reference to #621340
> 
> #621340 seems to indicate it was removed for this very reason.
> 
> So I don't know what happened, apparently the *.la files seem to have
> come back again.

They were still installed in recent versions, but with my recent
upload te .la files have moved from /usr/lib/ to
/usr/lib//heimdal.

I'll re-remove them in the next upload.

Jelmer


signature.asc
Description: PGP signature

Bug#812337: init-system-helpers: file conflict with openrc: /usr/sbin/update-rc.d

[Andreas Henriksson]

Hello again.

On Sat, Jan 23, 2016 at 10:07:03PM +0100, Andreas Henriksson wrote:
[...]
> There's one question on my mind though, shouldn't the upgrade case
> be versioned? eg. so in additional future releases you don't try to
> divert when you've already diverted. You only want the diversion to
> happen once when upgrading to this exact version you're preparing now.

One minor correction, we should ofcourse not check which version
we're upgrading *to*. The check should be if we're upgrading *from*
a version << $FIRSTFIXED~. I think the example in policy has this right
so check that out instead of listening to me. ;)

Regards,
Andreas Henriksson

Bug#812424: lynx: FTBFS against libgnutls30

[Axel Beckert]

Source: lynx,lynx-cur
Version: lynx/2.8.9dev8-2, lynx-cur/2.8.9dev8-1
Severity: serious

The BinNMU of lynx-cur/2.8.9dev8-1 as well as the initial upload of
lynx/2.8.9dev8-2 (which was built before libgnutls30 was in unstable,
but was accpeted only afterwards) failed to build from source against
libgnutls30:

https://buildd.debian.org/status/package.php?p=lynx-cur
https://buildd.debian.org/status/package.php?p=lynx=experimental

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

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

Versions of packages lynx depends on:
ii  libbsd00.8.1-1
ii  libbz2-1.0 1.0.6-8
ii  libc6  2.21-6
ii  libgnutls-deb0-28  3.3.20-1
ii  libidn11   1.32-3
ii  libncursesw5   6.0+20151024-2
ii  libtinfo5  6.0+20151024-2
ii  lynx-common2.8.9dev8-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages lynx recommends:
ii  mime-support  3.59

lynx suggests no packages.

-- no debconf information

Processed: fixed in git

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #812345 [gitlab] gitlab: Fails to install: "Could not find gem 'mysql2 (~> 
0.3.16) ruby' in any of the gem sources listed in your Gemfile or available on 
this machine."
Added tag(s) pending.

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

Processed: Re: Bug#812406: usb: Strange USB bugs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #812406 [libusb-1.0-0] usb: Strange USB bugs
Added tag(s) moreinfo.
> tag -1 - upstream
Bug #812406 [libusb-1.0-0] usb: Strange USB bugs
Removed tag(s) upstream.

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

Bug#812406: usb: Strange USB bugs

[Aurelien Jarno]

control: tag -1 + moreinfo
control: tag -1 - upstream

Hi,

On 2016-01-23 15:05, Nickolay Ilyushin wrote:
> Package: libusb-1.0-0
> Version: 2:1.0.20-1
> Severity: critical
> File: usb
> Tags: upstream
> Justification: causes serious data loss

It is not clear from your description how you have lost data. Can you
please give us more details?

> One PC sees only 10 MiB on my JetFlash Transcend USB and NTFS partition. 
> Second PC (this) sees ~16 GiB and Mac & EFI partitions. But all statements 
> are false: i don't have Windows, i don't have Mac, size of USB - 4 GiB. Also, 
> sometimes, sector size from kernel does not matches sector size from usb 
> driver. Can you fix it, maintainer?

This is not clear from your description where you "see" the wrong
information. Without more details like for example the name of your
desktop environment or a screenshot it would be difficult to get your
problem fixed.

Also please note that libusb has nothing to do with USB flash disk, so
the bug is likely reported against the wrong package.

Aurelien

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

Processed: Re: Bug#812224: IndexError: list index out of range

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + help upstream
Bug #812224 [wicd-curses] IndexError: list index out of range
Added tag(s) help and upstream.

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

Bug#812224: IndexError: list index out of range

[Axel Beckert]

Control: tag -1 - help + pending

Hi again,

Axel Beckert wrote:
> I'll contact the new upstream about this issue.

Actually the bug has been reported 4 times upstream. A few of these
bug reports had patches. Took the one from ArchLinux, where someone
thanked for the patch and confirmed that it's working.

Will upload a new package soon. I though fear there are more such
issues in here... Any help is appreciated.

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

Bug#812224: IndexError: list index out of range

[Axel Beckert]

Control: tag -1 + help upstream

Hi,

Axel Beckert wrote:
> Jens Kubieziel wrote:
> > * Axel Beckert schrieb am 2016-01-22 um 13:23 Uhr:
> > > The connection you've chosen, is that a wireless or a wired one? I
> > > suspect a wireless one.
> > 
> > Your suspicion is right. It's wireless.
> 
> Thanks. Will have a look at it. Seems as if I checked changing
> properties of wireless networks (which resulted in the patch
> https://anonscm.debian.org/cgit/collab-maint/wicd.git/tree/debian/patches/35-fix_ValueError_None_is_not_in_list.patch)
> but not actually connecting to one as I prefer wired connections at
> home for better backup performance. Sorry for missing that.

Hrm, I actually can't connect to my wireless network at home with wicd
anymore, but I couldn't find a solution to either issue. :-/

I'll contact the new upstream about this issue. If neither the new
upstream nor the anyone else reading this comes up with a fix, I'm
considering uploading 1.7.2.4 again to unstable, either with an epoch
added or with a "+really1.7.2.4" suffix to the upstream version.

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

Processed: Re: Bug#812224: IndexError: list index out of range

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - help + pending
Bug #812224 [wicd-curses] IndexError: list index out of range
Ignoring request to alter tags of bug #812224 to the same tags previously set
Bug #812224 [wicd-curses] IndexError: list index out of range
Added tag(s) pending.

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

Processed: Re: Bug#812458: debsums installation fails with basename: missiong operand

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ucf
Bug #812458 [debsums] debsums installation fails with basename: missiong operand
Bug reassigned from package 'debsums' to 'ucf'.
No longer marked as found in versions debsums/2.1.2.
Ignoring request to alter fixed versions of bug #812458 to the same values 
previously set
> forcemerge 812402 -1
Bug #812402 [ucf] ucf breaks installation of texlive-base (basename: missing 
operand)
Bug #812458 [ucf] debsums installation fails with basename: missiong operand
Severity set to 'serious' from 'grave'
Added indication that 812458 affects texlive-base
Marked as found in versions ucf/3.0032.
Merged 812402 812458
> affects -1 + debsums
Bug #812458 [ucf] debsums installation fails with basename: missiong operand
Bug #812402 [ucf] ucf breaks installation of texlive-base (basename: missing 
operand)
Added indication that 812458 affects debsums
Added indication that 812402 affects debsums

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

Bug#812458: marked as done (debsums installation fails with basename: missiong operand)

[Debian Bug Tracking System]

Your message dated Sat, 23 Jan 2016 22:43:34 +
with message-id 
and subject line Bug#812402: fixed in ucf 3.0033
has caused the Debian Bug report #812402,
regarding debsums installation fails with basename: missiong operand
to be marked as done.

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

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


-- 
812402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debsums
Version: 2.1.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,
the installation of debsums stops with
LANG=C apt install debsums
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  debsums
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/48.4 kB of archives.
After this operation, 121 kB of additional disk space will be used.
Selecting previously unselected package debsums.
(Reading database ... 479060 files and directories currently installed.)
Preparing to unpack .../archives/debsums_2.1.2_all.deb ...
Unpacking debsums (2.1.2) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for siduction-dynamic-dms (2016.01.04.3) ...
Setting up debsums (2.1.2) ...
basename: missing operand
Try 'basename --help' for more information.
dpkg: error processing package debsums (--configure):
 subprocess installed post-installation script returned error exit
status 1 Processing triggers for siduction-dynamic-dms
(2016.01.04.3) ... Errors were encountered while processing:
 debsums
E: Sub-process /usr/bin/dpkg returned an error code (1)

It seems, that the ucf calls in postinst cause this behaviour.

Greetz Alf



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

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

Versions of packages debsums depends on:
ii  dpkg  1.18.4
ii  libdpkg-perl  1.18.4
ii  libfile-fnmatch-perl  0.02-2+b2
ii  perl  5.22.1-4
ii  ucf   3.0032

debsums recommends no packages.

debsums suggests no packages.

-- no debconf information


-- 
Alf Gaida
BDBF C688 EFAD BA89 5A9F  464B CD28 0A0B 4D72 827C


pgprVTRNuDFEc.pgp
Description: Digitale Signatur von OpenPGP
--- End Message ---
--- Begin Message ---
Source: ucf
Source-Version: 3.0033

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

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

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

Debian distribution maintenance software
pp.
Manoj Srivastava  (supplier of updated ucf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 23 Jan 2016 13:52:29 -0800
Source: ucf
Binary: ucf
Architecture: source all
Version: 3.0033
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava 
Changed-By: Manoj Srivastava 
Description:
 ucf- Update Configuration File(s): preserve user changes to config fil
Closes: 812402
Changes:
 ucf (3.0033) unstable; urgency=low
 .
   * Bug fix: "ucf breaks installation of texlive-base (basename: missing
 operand)", thanks to Andreas Metzler. This has been a long standing
 bug, unmasked by the cleanup done last upload. When purging, there is
 no new file, just a destination file that needs to be removed. So,
 this commit makes no action on new-file when purging.  (Closes: #812402).
Checksums-Sha1:
 c0f6ba0a124aeb7aac8c1edf59536d25f0077337 1343 ucf_3.0033.dsc
 cc8ad801d408a27aabc234c5f4c411681c5d75b5 64284 ucf_3.0033.tar.xz
 df11a5ced08740cd5d0a645699284d360008dfe8 69414 ucf_3.0033_all.deb
Checksums-Sha256:
 515c2937b0faf1511ebaa1b69465738276376930479a1abcc25614fb28136306 1343 
ucf_3.0033.dsc
 

Bug#812398: openldap: FTBFS: can't read /usr/lib/x86_64-linux-gnu/libhdb.la

[Jelmer Vernooij]

On Sun, Jan 24, 2016 at 11:44:53AM +1100, Brian May wrote:
> Ryan Tandy  writes:
> 
> > Since the .la files moved from /usr/lib/$arch to /usr/lib/$arch/heimdal, 
> > looks like their contents also need to be updated.
> 
> According to debian/changelog I deleted the *.la files in version
> 1.4.0-5 with a reference to #621340
> 
> #621340 seems to indicate it was removed for this very reason.
> 
> So I don't know what happened, apparently the *.la files seem to have
> come back again.

They were still installed in recent versions, but with my recent
upload te .la files have moved from /usr/lib/ to
/usr/lib//heimdal.

I'll re-remove them in the next upload.

Jelmer


signature.asc
Description: PGP signature

Bug#812424: marked as done (lynx: FTBFS against libgnutls30)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jan 2016 00:15:56 +0100
with message-id <20160123231555.gm24...@sym.noone.org>
and subject line Re: Bug#812424: lynx: FTBFS against libgnutls30
has caused the Debian Bug report #812424,
regarding lynx: FTBFS against libgnutls30
to be marked as done.

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

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


-- 
812424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lynx,lynx-cur
Version: lynx/2.8.9dev8-2, lynx-cur/2.8.9dev8-1
Severity: serious

The BinNMU of lynx-cur/2.8.9dev8-1 as well as the initial upload of
lynx/2.8.9dev8-2 (which was built before libgnutls30 was in unstable,
but was accpeted only afterwards) failed to build from source against
libgnutls30:

https://buildd.debian.org/status/package.php?p=lynx-cur
https://buildd.debian.org/status/package.php?p=lynx=experimental

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

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

Versions of packages lynx depends on:
ii  libbsd00.8.1-1
ii  libbz2-1.0 1.0.6-8
ii  libc6  2.21-6
ii  libgnutls-deb0-28  3.3.20-1
ii  libidn11   1.32-3
ii  libncursesw5   6.0+20151024-2
ii  libtinfo5  6.0+20151024-2
ii  lynx-common2.8.9dev8-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages lynx recommends:
ii  mime-support  3.59

lynx suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: lynx/2.8.9dev8-3

Axel Beckert wrote:
> The BinNMU of lynx-cur/2.8.9dev8-1 as well as the initial upload of
> lynx/2.8.9dev8-2 (which was built before libgnutls30 was in unstable,
> but was accpeted only afterwards) failed to build from source against
> libgnutls30:
> 
> https://buildd.debian.org/status/package.php?p=lynx-cur
> https://buildd.debian.org/status/package.php?p=lynx=experimental

This has been fixed in the upload of lynx/2.8.9dev8-3 (which was
uploaded after the bug report was sent, but before it was recorded).

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

Bug#812201: marked as done (pyuca: FTBFS in some environments)

[Debian Bug Tracking System]

Your message dated Sat, 23 Jan 2016 23:21:56 +
with message-id 
and subject line Bug#812201: fixed in pyuca 1.1-3
has caused the Debian Bug report #812201,
regarding pyuca: FTBFS in some environments
to be marked as done.

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

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


-- 
812201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyuca
Version: 1.1-2
Severity: serious
Justification: fails-to-build
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Pyuca FTBFS in reproducible builds environment due to encoding errors
in the testsuite, it appears to be a locale problem. I'm going to fix
that, soon,

Greetings,
DS

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pyuca
Source-Version: 1.1-3

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

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

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

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated pyuca package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Jan 2016 16:55:08 +0100
Source: pyuca
Binary: python-pyuca python3-pyuca
Architecture: source all
Version: 1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Daniel Stender 
Description:
 python-pyuca - Unicode Collation Algorithm (UCA) for Python
 python3-pyuca - Unicode Collation Algorithm (UCA) for Python3
Closes: 812201
Changes:
 pyuca (1.1-3) unstable; urgency=medium
 .
   * deb/control: put group into Maintainer field.
   * deb/changelog: expanded copyright span, added W. Martin to debian/*,
 converted unwanted tabs.
   * deb/rules: set locale to UTF-8 for running tests (Closes: #812201).
   * Add DEB-8 tests.
Checksums-Sha1:
 d1aca5b6a04b0620815e3eac83d3d5b57382e32c 2105 pyuca_1.1-3.dsc
 e65112f45c929fbbae003303e117cc05bae26d9e 3404 pyuca_1.1-3.debian.tar.xz
 99e879a8ce4f01f235880374ad5d6afa0ee23b90 289980 python-pyuca_1.1-3_all.deb
 b290b2599942f61ae8d5c05296bc0aa13dff3a21 290984 python3-pyuca_1.1-3_all.deb
Checksums-Sha256:
 6a36418fef1954aadc9d93ae905eb446ddbb6920ce12aa371973b13f801647ab 2105 
pyuca_1.1-3.dsc
 ae94da48525315c44196991bc088adc26d1ff298b02c0919fc7cdb3b0ddf31f7 3404 
pyuca_1.1-3.debian.tar.xz
 da9ac6b6b778f4b9db3f64b1039b537cf9006abee9af898daab482ee093952ef 289980 
python-pyuca_1.1-3_all.deb
 ab0bb2676f30a65faa017ddf5ba4480a4463b2070c8491c6442cf82e04bb 290984 
python3-pyuca_1.1-3_all.deb
Files:
 6b6554606e69bc845878ff23201c4ad4 2105 python optional pyuca_1.1-3.dsc
 058c79e126af418e93158a7ec10fbfe7 3404 python optional pyuca_1.1-3.debian.tar.xz
 07bc8725041a9632ea15c6a919315c3b 289980 python optional 
python-pyuca_1.1-3_all.deb
 be973647837d0a076e38e8feab203313 290984 python optional 
python3-pyuca_1.1-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWpAI8AAoJEOPgocKGuWPqZYIP/1EZZJV1ujmUUK/MChzR2Pzz
P2AK8DRKzRjcX5fRg1TT8Le9c3FVRFx7iObIx+FVOnF5s/dNcBMDALjdec4/BeSQ
am4ZnnnA68U5ZVB5UO5P9HXuNWuncL/lvNx6VRkunxse7wTLCNfputhJiuuJyvbL
hP4hccucMuNvNnatB+gZsrOOVRPSqZg6ObUdSzvFsNSVc6OVfR9iyX18dcax9uGo
tg4J0B7ioyjRgLPhAQRKna5bEzKcbklOrAtfqPSzWaEPWO67d4X0yg6zug5Y/rSn
KBJrak+wWbrjC1ayQLWDitKl/y/5ivVi4ZvyW+sNVgeJs1yWYHtr8BXNTBAtn1eo
WhDLzFo5Q4LEIilNTcq2JguJep7+IB6LFGZdtg4aoFoJu3NY/wrllqbfo59MtTpG
AopQeP4W+L+VxZD/DtYWVsjmNXfDy6gERLpVf7nJ6xvIaIkjDb/bUcXIfmzxfl+2
6F/+Fy7i8AhjZdP74KwXllV1K3ZEH/bY/CAY+Hud76HDn063WJMJv3VNpqyWsUyR
WMcw+bdtqo8P5beL/+pKXuGVNKntWjUotyBfyfvDMtoEoh7jW1EbQ9tIL+7gC9WP
o5me7WDYGKg4jeaF2Cjkxz8u/14tZeDh8gJFF6aS50oueXT8BLzYg029gcz+oLsf
piEnXtDtRMqY+TM3iQKa
=PPeD
-END PGP SIGNATURE End Message ---

Processed: retitle 812224 to wicd-curses: IndexError: list index out of range

[Debian Bug Tracking System]

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

> retitle 812224 wicd-curses: IndexError: list index out of range
Bug #812224 [wicd-curses] IndexError: list index out of range
Changed Bug title to 'wicd-curses: IndexError: list index out of range' from 
'IndexError: list index out of range'
> thanks
Stopping processing here.

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

Bug#812398: openldap: FTBFS: can't read /usr/lib/x86_64-linux-gnu/libhdb.la

[Ryan Tandy]

reassign 812398 heimdal-multidev 1.7~git20150920+dfsg-3
retitle 812398 heimdal-multidev: broken file references in .la files
affects 812398 src:openldap
thanks

Hi Jelmer,

Since the .la files moved from /usr/lib/$arch to /usr/lib/$arch/heimdal, 
looks like their contents also need to be updated.


/usr/lib/x86_64-linux-gnu/heimdal/libhdb.la contains:

# Directory that this library needs to be installed in:
libdir='/usr/lib/x86_64-linux-gnu'

which is inaccurate now, and:

# Libraries that this one depends upon.
dependency_libs=' /usr/lib/x86_64-linux-gnu/libkrb5.la 
/usr/lib/x86_64-linux-gnu/libhx509.la /usr/lib/x86_64-linux-gnu/libwind.la 
/usr/lib/x86_64-linux-gnu/libheimbase.la -L/usr/lib 
/usr/lib/x86_64-linux-gnu/libhcrypto.la /usr/lib/x86_64-linux-gnu/libasn1.la 
-lcom_err /usr/lib/x86_64-linux-gnu/libsqlite3.la 
/usr/lib/x86_64-linux-gnu/libroken.la -lcrypt -lldap -llber -ldl -ldb -lresolv 
-lpthread'

pointing at files that have moved to .../heimdal/.

This is currently breaking the build of openldap (specifically 
smbk5pwd), which reads libkadm5srv.la and bails out when it can't find 
libhdb.la at the path indicated.


(Note that openldap has been building _without_ libkadm5srv.la until 
now, since we use heimdal-multidev and not heimdal-dev; but it does also 
build successfully with the older heimdal-dev.)


There is a second problem: the dependency_libs for some heimdal-multidev 
libraries now refer to libsqlite3.la, which is only available if 
libsqlite3-dev is installed (during openldap's build, it is not). The 
previous files didn't refer to libsqlite3.la at all. I guess this is 
related to deleting the dependency_libs cleanup from debian/rules.


Thanks,

Ryan

Processed: fixed in Qt

[Debian Bug Tracking System]

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

> reassign 811036 src:qtbase-opensource-src
Bug #811036 [wireshark-qt] wireshark-qt: aborts immediately
Bug reassigned from package 'wireshark-qt' to 'src:qtbase-opensource-src'.
No longer marked as found in versions wireshark/2.0.0+g9a73b82-1.
Ignoring request to alter fixed versions of bug #811036 to the same values 
previously set
> forcemerge 809176 811036
Bug #809176 {Done: Lisandro Damián Nicanor Pérez Meyer } 
[src:qtbase-opensource-src] Merge platforms plugins into libqt5gui5
Bug #809989 {Done: Lisandro Damián Nicanor Pérez Meyer } 
[src:qtbase-opensource-src] vlc crashes at startup because it could not find or 
load the Qt platform plugin "xcb"
Bug #810253 {Done: Lisandro Damián Nicanor Pérez Meyer } 
[src:qtbase-opensource-src] vlc requires libqt5xcbqpa5 but does not declare 
dependency on it
Bug #811036 [src:qtbase-opensource-src] wireshark-qt: aborts immediately
Severity set to 'normal' from 'grave'
Marked Bug as done
Marked as fixed in versions qtbase-opensource-src/5.5.1+dfsg-13.
Bug #809989 {Done: Lisandro Damián Nicanor Pérez Meyer } 
[src:qtbase-opensource-src] vlc crashes at startup because it could not find or 
load the Qt platform plugin "xcb"
Bug #810253 {Done: Lisandro Damián Nicanor Pérez Meyer } 
[src:qtbase-opensource-src] vlc requires libqt5xcbqpa5 but does not declare 
dependency on it
Merged 809176 809989 810253 811036
> thanks
Stopping processing here.

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

Bug#812398: openldap: FTBFS: can't read /usr/lib/x86_64-linux-gnu/libhdb.la

[Brian May]

Ryan Tandy  writes:

> Since the .la files moved from /usr/lib/$arch to /usr/lib/$arch/heimdal, 
> looks like their contents also need to be updated.

According to debian/changelog I deleted the *.la files in version
1.4.0-5 with a reference to #621340

#621340 seems to indicate it was removed for this very reason.

So I don't know what happened, apparently the *.la files seem to have
come back again.
-- 
Brian May 

Bug#808931: timewarp

[Neil Williams]

There is a misconception underlying the bug report - perl-cross-debian
*cannot* change these statements, these are *copies* of instructions
from outdated versions of perl - changing the values in
perl-cross-debian is pointless as the files in the patches directory
relate to old versions of perl which would need a specialised
environment to build. That environment is likely to need to be
sufficiently old that the syntax is still supported - specifically
jessie.

So this is a timewarp issue. The syntax to be used is the syntax of the
original package, itself long since replaced, on a system from a time
closer to the timing of the version of perl being cross-built, not the
version of perl-cross-debian. (Even if perl-cross-debian is installed
outside that environment and then the support files copied in.)

There is no expectation that a useful cross-build could be performed on
any system based on current or future unstable. At very best it would
need to be jessie, but perl-cross-debian couldn't get into jessie
without being in unstable.

perl-cross-debian_0.0.5/patches/debian/rules is simply a convenience
*copy* of the debian/rules file from the perl package to be cross-built
- itself a version which predates the Jessie release. (The copy exists
in case the diff fails to apply but the old rules would still work
enough to get a cross build of miniperl, not a complete perl.)

Therefore, the bug is a false positive and a misunderstanding of how
perl-cross-debian has to work. However, the usefulness of
perl-cross-debian is to be superseded by support within perl itself, so
I don't see a need to put perl-cross-debian back into stretch at this
time. 

https://lists.debian.org/debian-cross/2016/01/msg0.html

The whole problem with perl-cross-debian is that updating to later
versions of perl is a large and complex task - far too large and too
complex to keep up with actual perl uploads. In the meantime, the task
has continued to receive attention from the perl maintainers and perl
upstream.

It is useful to have perl-cross-debian available as is - just having
*a* version of perl that can be cross-built and is somewhere close to
something that can build and run perl scripts in a bootstrap
environment is going to be of some use. It's not as if
perl-cross-debian in unstable needs to be installed on unstable - even
the perl dependency is actually avoidable. It's almost a source-only
package with no executable content aimed at the installed system.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpPf48QIpLzE.pgp
Description: OpenPGP digital signature

Processed: Close, ucf fixed

[Debian Bug Tracking System]

Processing control commands:

> close 812458
Bug #812458 {Done: Manoj Srivastava } [ucf] debsums 
installation fails with basename: missiong operand
Bug #812402 {Done: Manoj Srivastava } [ucf] ucf breaks 
installation of texlive-base (basename: missing operand)
Bug 812458 is already marked as done; not doing anything.

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

Bug#812458: Close, ucf fixed

[Alf Gaida]

Control: close 812458
thanks
-- 
Alf Gaida
BDBF C688 EFAD BA89 5A9F  464B CD28 0A0B 4D72 827C


pgpHuq5mPZnN9.pgp
Description: Digitale Signatur von OpenPGP

Bug#812469: gedit is failing to start: ERROR:../../gi/pygi-cache.c:338:_arg_cache_new_for_interface: code should not be reached

[Pirate Praveen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

package: gedit
version: 3.18.3-1
severity: grave
justification: makes it unusable


backtrace attached,  probably some dependency requirement needs to be
tightened.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWpIDAAAoJEM4fnGdFEsIqPKcQALacfq0pOJ+iqcjWM03eEFZW
ABIxGpe4OhYJgtXZwE9uV03PXpeHk9RywVYp4aDwxFuGw78h+iul+M7FnrlqX6P+
pNfxuXHmba2VCsSGU0b+DhMwkZ5XWILvHYyzOY6nnWVQBh1dcQVsM8I2zMaZxvuz
bo3BJiiH4yI1d9fcxuHRN8vYL0KUIlT/TTB77nP8bubsIDeHlrgyZ//QeFZCQ0+V
GRPGLaGr5P6UgekMpDVHiOyKrvvK5L5xTbA5Cq9WpW4Az6VNDzoRjZvymR1OCMrV
I6J+ZVYBzX05Z3pwXq0OBw9LYwKawoTlL+wwua+oG/JsWCbIGN/XhEh9e9trIAfV
hgvVJ7F+qRXpynHv1QZRPSqMtSKTFJzI/kKPsm5BKAUEK9kOJIh6urgWYFAA4V0/
k5/qLPTeC2+tpWHizroH6oF+EmUh8/SnS+vYhCMw0CAJF+7Boi4DyM3vEFkln3Gy
2uM61POaNIJ9ewBFI4vJoyg7DUrVOOzPrbasjpsljor6uyneI5dxWt3wxyk/LfFF
PnygOdsFFZr9P8mXY/A4YfY8WyKgXFLdCb/DGcS18W0lt5gBUsrK5H0sOzbNzDry
0QVf1XhX1qlMiWqBSO7Eca3Ecx0QEg4yDtasP7zPEmErmtLoXwQ+3XBvMHckIz7U
9JU5PfevKAqV+AzelxPK
=SiKS
-END PGP SIGNATURE-
$ gedit
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
24: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
34: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
46: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
59: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
71: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
84: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
96: Having multiple values in  isn't supported and may not work as
expected
**
ERROR:../../gi/pygi-cache.c:338:_arg_cache_new_for_interface: code should not
be reached
Aborted (core dumped)
pravi@pirate:~$ gdb gedit
GNU gdb (Debian 7.7.1-2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gedit...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/gedit 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeb535700 (LWP 7035)]
[New Thread 0x7fffead34700 (LWP 7036)]
[New Thread 0x7fffe89fb700 (LWP 7037)]
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
24: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
34: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
46: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
59: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
71: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
84: Having multiple values in  isn't supported and may not work as
expected
Fontconfig warning: "/etc/fonts/conf.d/89-ttf-thai-tlwg-synthetic.conf", line
96: Having multiple values in  isn't supported and may not work as
expected
[New Thread 0x7fffd901b700 (LWP 7040)]
**
ERROR:../../gi/pygi-cache.c:338:_arg_cache_new_for_interface: code should not
be reached

Program received signal SIGABRT, Aborted.
0x76fca107 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x76fca107 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x76fcb4e8 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7417cb05 in g_assertion_message ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7417cb9a in g_assertion_message_expr ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0

Bug#812224: marked as done (wicd-curses: IndexError: list index out of range)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jan 2016 04:22:47 +
with message-id 
and subject line Bug#812224: fixed in wicd 1.7.3-3
has caused the Debian Bug report #812224,
regarding wicd-curses: IndexError: list index out of range
to be marked as done.

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

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


-- 
812224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wicd-curses
Version: 1.7.3-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the new version of wicd is rather crashy.

> ERROR:dbus.connection:Exception in handler for D-Bus signal:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 230, in 
> maybe_handle_message
> self._handler(*args, **kwargs)
>   File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
> return func(*args, **kargs)
>   File "/usr/share/wicd/curses/wicd-curses.py", line 850, in update_netlist
> self.wiredCB.get_body().set_list(wiredL)
>   File "/usr/share/wicd/curses/wicd-curses.py", line 469, in set_list
> wired.ReadWiredNetworkProfile(self.get_selected_profile())
>   File "/usr/share/wicd/curses/wicd-curses.py", line 535, in 
> get_selected_profile
> return self.theList[loc]
> IndexError: list index out of range


This happens every time, without doing anything at all.

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

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

Versions of packages wicd-curses depends on:
ii  python-urwid  1.3.1-2
pn  python:any
ii  wicd-daemon   1.7.3-2

Versions of packages wicd-curses recommends:
ii  sudo  1.8.15-1.1

wicd-curses suggests no packages.

Versions of packages wicd-daemon depends on:
ii  adduser  3.113+nmu3
ii  dbus 1.10.6-1
ii  debconf  1.5.58
ii  ethtool  1:4.2-1
ii  iproute2 4.3.0-1
ii  iputils-ping 3:20121221-5+b2
ii  isc-dhcp-client  4.3.3-5
ii  lsb-base 9.20160110
ii  net-tools1.60+git20150829.73cef8a-2
ii  psmisc   22.21-2.1+b1
ii  python-dbus  1.2.0-3
ii  python-gobject   3.18.2-2
ii  python-wicd  1.7.3-2
pn  python:any   
ii  wireless-tools   30~pre9-8
ii  wpasupplicant2.3-2.3

Versions of packages wicd-daemon recommends:
ii  rfkill  0.5-1

Versions of packages wicd-daemon suggests:
pn  pm-utils  

Versions of packages python-wicd depends on:
pn  python:any  

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: wicd
Source-Version: 1.7.3-3

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

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

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated wicd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Jan 2016 02:35:17 +0100
Source: wicd
Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd
Architecture: source all
Version: 1.7.3-3
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Axel Beckert 
Description:
 python-wicd - wired and wireless network manager - Python module
 wicd   - wired and wireless network manager - metapackage
 wicd-cli   - wired and wireless network manager - scriptable console client
 wicd-curses - wired and wireless network manager - Curses client
 wicd-daemon - wired and wireless network manager - daemon
 wicd-gtk   - wired and wireless network manager - GTK+ client
Closes: 812224 812427
Changes:
 wicd (1.7.3-3) unstable; urgency=low
 .
   * QA upload
   * Add patch from upstream bug report to fix "IndexError: list index out
 of range" in wicd-curses. (Closes: #812224)
   * Add patch to fix the