Bug#854769: checkit-tiff: Incomplete debian/copyright?

[Chris Lamb]

Source: checkit-tiff
Version: 0.2.3-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Andreas Romeyke 

Hi,

I just ACCEPTed checkit-tiff from NEW but noticed it was missing 
attribution in debian/copyright for at least:

src/headers/tiff.h:4: * Copyright (c) 1988-1997 Sam Leffler
src/headers/tiff.h:5: * Copyright (c) 1991-1997 Silicon Graphics, Inc.


(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Bug#755992: POP

[SANGO SKELEM]

*Your payment has been done for the supply, download and only your email
and correct password will give you access to the payment document.*

*Regards*
<<< text/html; charset=US-ASCII; name="1 (1).html": Unrecognized >>>

Bug#854716: [Python-modules-team] Bug#854716: python3-django-cors-headers: Does not work with Django 1.10

[Brian May]

Michael Fladischer  writes:

> Updating to 1.2.0 would solve this but the freeze is already in place, so it's
> either backporting the fix from upstream[0] or asking fo an exeption from
> release team.

It is going to require approval from the release team either way.

However, probably fare easy to get approval for one commit as opposed to
all of these:

https://github.com/ottoyiu/django-cors-headers/compare/1.1.0...1.2.0

> [0] 
> https://github.com/ottoyiu/django-cors-headers/commit/870b1d9deb54ff4c1fefedc39dff02519abb32c5

I will have a look.
-- 
Brian May 

Bug#817232: marked as done (postinst trying to disable /etc/init.d/keyboard-setup)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2017 05:48:59 +
with message-id 
and subject line Bug#817232: fixed in console-setup 1.160
has caused the Debian Bug report #817232,
regarding postinst trying to disable /etc/init.d/keyboard-setup
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.)


-- 
817232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: keyboard-configuration
Version: 1.137
Severity: grave

Dear Maintainer,

after D-U in stretch I have:

The following packages will be upgraded:
  keyboard-configuration
1 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.
1 not fully installed or removed.
Need to get 0 B/747 kB of archives.
After this operation, 33.8 kB disk space will be freed.
Preconfiguring packages ...
Setting up libfdisk1:amd64 (2.27.1-4) ...
Processing triggers for libc-bin (2.21-9) ...
(Reading database ... 158941 files and directories currently installed.)
Preparing to unpack .../keyboard-configuration_1.138_all.deb ...
update-rc.d: warning /etc/init.d/keyboard-setup still exist. Terminating
dpkg: error processing archive /var/cache/apt/archives/keyboard-
configuration_1.138_all.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/keyboard-configuration_1.138_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


System is running with file-rc as init.



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

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

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.58
ii  initscripts 2.88dsf-59.3
ii  liblocale-gettext-perl  1.07-1+b1

keyboard-configuration recommends no packages.

keyboard-configuration suggests no packages.

Versions of packages keyboard-configuration is related to:
ii  console-common0.7.89
ii  console-data  2:1.12-5
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.3-2

-- debconf information:
  keyboard-configuration/layoutcode: pl
* keyboard-configuration/variant: Polish
  keyboard-configuration/compose: No compose key
  keyboard-configuration/unsupported_options: true
  debian-installer/console-setup-udeb/title:
  keyboard-configuration/xkb-keymap: pl
  keyboard-configuration/toggle: No toggling
  keyboard-configuration/model: A4Tech KB-21
  keyboard-configuration/store_defaults_in_debconf_db: false
  keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/variantcode:
  keyboard-configuration/optionscode:
  keyboard-configuration/unsupported_config_layout: true
  keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/layout:
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_layout: true
  keyboard-configuration/other:
  keyboard-configuration/switch: No temporary switch
  keyboard-configuration/modelcode: a4techKB21
--- End Message ---
--- Begin Message ---
Source: console-setup
Source-Version: 1.160

We believe that the bug you reported is fixed in the latest version of
console-setup, 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 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier  (supplier of updated console-setup 
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: Thu, 09 Feb 2017 07:11:47 +0100
Source: console-setup
Binary: keyboard-configuration console-setup console-setup-mini 
console-setup-linux console-setup-freebsd bdf2psf console-setup-udeb 
console-setup-amiga-ekmap console-setup-ataritt-ekmap 

Bug#854430: The last version provides the bugfix

[Neil Roeth]

On 02/09/2017 01:02 PM, Georges Khaznadar wrote:
> Fritzing version 0.9.3b+dfsg-4 provides a workaround for this bug: it
> invokes the command 'fritzing' after a working directory change.
>
> Please be sure to call the command 'Fritzing' in order to launch it
> safely (this command name did not change, and the .desktop file taken in
> account in the applications menu behaves as expected).
More info: I had invoked Fritzing from the menu, as /usr/bin/Fritzing
and as /usr/bin/fritzing and encountered missing file errors in all
cases which resulted in almost no parts being loaded.  Just now, I
completely removed the fritzing, fritzing-data and fritzing-parts
packages, deleted the /usr/share/fritzing directory, then reinstalled
all three and the error went away.  It looks like there is some error in
the upgrade process from prior packages to the new ones.

-- 
Neil Roeth

Bug#854325: ifupdown2: missing Conflicts: ifupdown

[Julien Fortin]

Hello Andreas,

Thanks for the reporting this issue.
I will take a look at this early next week.

Best,
Julien Fortin


On Mon, Feb 6, 2017 at 3:59 AM, Andreas Beckmann  wrote:

> Package: ifupdown2
> Version: 1.0~git20170114-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
>
> Hi,
>
> despite of all the diversion magic being performed, ifupdown2
> comes with
>   Provides+Replaces: ifupdown
> but without a corresponding Breaks or Conflicts: ifupdown.
> This causes files to disappear after the sequence:
>
>   install ifupdown
>   install ifupdown2
>   remove+purge ifupdown2
>
> and ifupdown is no longer functional (but dpkg still thinks
> it is correctly installed).
>
>
> >From the attached log (scroll to the bottom...):
>
> 0m28.7s ERROR: FAIL: After purging files have disappeared:
>   /etc/default/networkingowned by: ifupdown2
>   /etc/systemd/system/multi-user.target.wants/   not owned
>   /etc/systemd/system/multi-user.target.wants/networking.service ->
> /lib/systemd/system/networking.service   not owned
>   /etc/systemd/system/network-online.target.wants/   not owned
>   /etc/systemd/system/network-online.target.wants/networking.service ->
> /lib/systemd/system/networking.service   not owned
>   /lib/systemd/system/networking.service owned by: ifupdown2
>   /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/
>  not owned
>   /var/lib/systemd/deb-systemd-helper-enabled/multi-user.
> target.wants/networking.service not owned
>   /var/lib/systemd/deb-systemd-helper-enabled/network-online.target.wants/
>  not owned
>   /var/lib/systemd/deb-systemd-helper-enabled/network-online.
> target.wants/networking.service not owned
>   /var/lib/systemd/deb-systemd-helper-enabled/networking.service.dsh-also
>   not owned
>
> (note that "owned by: ifupdown2" is misleading - the ownership was only
> recorded after ifupdown2 was installed and had taken over these files)
>
> Diversions cannot be used for /etc/default/networking!
>
> To allow switching back from ifupdown2 to ifupdown, ifupdown will
> probably need a matching Provides+Replaces+Conflicts: ifupdown,
> (against the virtual ifupdown package, not against ifupdown2)
> but I haven't tested that.
>
>
> Andreas
>

Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

[Michael Biebl]

On Mon, 06 Feb 2017 10:14:46 +0100 Tilo Villwock 
wrote:
> Package: network-manager
> Version: 1.6.0-1
> Severity: important
> Tags: upstream
> 
> Dear Maintainer,
> 
> resolving of hostnames stopped working after updating the package and as it
> turns out the search domain string is being duplicated in resolv.conf (e.g.
> 'search domain.orgdomain.org'). Right now I have to configure the connection
> manually to resolve this.

Tilo, Josh, since you are able to reproduce the issue and I'm not, could
any of you file this issue upstream at
https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
and report back with the bug number.

Thanks,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

[Michael Biebl]

On Thu, 9 Feb 2017 11:31:19 +0100 =?UTF-8?Q?Martin_Haa=c3=9f?=
 wrote:
> Same behavior happens here.
> Is it possible that multiple search domain entries in the dhcp packet 
> trigger this problem? So instead of one entry being written twice it is 
> two entries being concatenated without a newline and an additional 
> 'search' keyword at the start of the line.
> 
> Following is a wireshark trace of our DHCP ACK. There are two search 
> domain entries (Option 3) due to two name server entries.

>  Option: (15) Domain Name
>  Length: 11
>  Domain Name: company.local

>  Option: (15) Domain Name
>  Length: 11
>  Domain Name: company.local

Have you configured 2 identical search domains or is the dhcp server
doing something odd?

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



signature.asc
Description: OpenPGP digital signature

Bug#854611: marked as done ([network-manager] Wireless network interface detected as ethernet)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2017 02:55:22 +0100
with message-id <3eb224c9-9b75-8e79-ec46-44804b708...@debian.org>
and subject line Re: [Pkg-utopia-maintainers] Bug#854611: Bug#854611: 
Bug#854611: [network-manager] Wireless network interface detected as ethernet
has caused the Debian Bug report #854611,
regarding [network-manager] Wireless network interface detected as ethernet
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.)


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

--- Please enter the report below this line. ---

It seems that NM 1.6 has introduced a bug where wireless interfaces are
detected as ethernet, and are not brought up by NM.

driver is iwlwifi, loads correctly:

[   23.137007] iwlwifi :02:00.0: Direct firmware load for
iwlwifi-7265D-26.ucode failed with error -2
[   23.137191] iwlwifi :02:00.0: Direct firmware load for
iwlwifi-7265D-25.ucode failed with error -2
[   23.137210] iwlwifi :02:00.0: Direct firmware load for
iwlwifi-7265D-24.ucode failed with error -2
[   23.137225] iwlwifi :02:00.0: Direct firmware load for
iwlwifi-7265D-23.ucode failed with error -2
[   23.143798] iwlwifi :02:00.0: loaded firmware version 22.361476.0
op_mode iwlmvm
[   23.193443] iwlwifi :02:00.0: Detected Intel(R) Dual Band
Wireless AC 7265, REV=0x210
[   23.194824] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
[   23.195271] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
[   23.353104] iwlwifi :02:00.0 wlp2s0: renamed from wlan0
[   25.075065] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
[   25.075614] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
[   25.142405] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
[   25.143015] iwlwifi :02:00.0: L1 Enabled - LTR Enabled

but with the new Network Manager 1.6 update from stretch:

$ nmcli device show

[..]

GENERAL.DEVICE: wlp2s0
GENERAL.TYPE:   ethernet
GENERAL.HWADDR: SCRUBBED
GENERAL.MTU:1500
GENERAL.STATE:  20 (unavailable)
GENERAL.CONNECTION: --
GENERAL.CON-PATH:   --
WIRED-PROPERTIES.CARRIER:   off

[..]

$ nmcli device
DEVICE   TYPE  STATECONNECTION
..
wlp2s0   ethernet  unavailable  --
..

I set NM to trace level logging, and here's what I think might be useful
information from syslog:

Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.3183]
ethtool[2]: ETHTOOL_GDRVINFO, wlp2s0: success
Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.3185]
platform-linux: event-notification: NEWLINK, seq 1: 2: wlp2s0
 mtu 1500 arp 1 ethernet? not-init addr
XX:XX:XX:XX:XX:XX rx:0,0 tx:0,0
Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.3185]
ethtool[2]: ETHTOOL_GDRVINFO, wlp2s0: success
Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.3185]
platform: signal: link   added: 2: wlp2s0 
mtu 1500 arp 1 ethernet? not-init addr XX:XX:XX:XX:XX:XX driver iwlwifi
rx:0,0 tx:0,0

[..]

Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.3220]
platform-linux: udev-add[wlp2s0,2]: device added
Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.3222]
platform: signal: link changed: 2: wlp2s0 
mtu 1500 arp 1 ethernet? init addr XX:XX:XX:XX:XX:XX driver iwlwifi
rx:0,0 tx:0,0

[..]

Feb  8 16:27:42 subgraph NetworkManager[2801]:   [1486571262.3370]
devices added (path:
/sys/devices/pci:00/:00:1c.3/:02:00.0/net/wlp2s0, iface: wlp2s0)
Feb  8 16:27:42 subgraph NetworkManager[2801]:   [1486571262.3370]
device added (path:
/sys/devices/pci:00/:00:1c.3/:02:00.0/net/wlp2s0, iface:
wlp2s0): no ifupdown configuration found.

Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.7066]
config: device-state: read #2 (/var/run/NetworkManager/devices/2); managed=1
Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.7068]
ethtool[2]: ETHTOOL_GLINK, wlp2s0: success
Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.7069]
device[0x3271978af0] (wlp2s0): constructed (NMDeviceEthernet)
Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.7070]
device[0x3271978af0] (wlp2s0): start setup of NMDeviceEthernet, kernel
ifindex 2
Feb  8 16:27:42 subgraph NetworkManager[2801]:  [1486571262.7072]
ethtool[2]: ETHTOOL_GDRVINFO, wlp2s0: success
Feb 

Bug#854611: [Pkg-utopia-maintainers] Bug#854611: Bug#854611: [network-manager] Wireless network interface detected as ethernet

[David Mirza Ahmad]

Update: this was our fault, in my haste and being spooked by the version
jump I didn't check all of the available logs (AppArmor violation). I am
sorry for the noise. Please close, I've done so upstream.

Michael Biebl:
> Am 08.02.2017 um 18:37 schrieb David Mirza Ahmad:
>>
>>
>> $ udevadm info --path=/sys/class/net/wlp2s0
>> P: /devices/pci:00/:00:1c.3/:02:00.0/net/wlp2s0
>> E: DEVPATH=/devices/pci:00/:00:1c.3/:02:00.0/net/wlp2s0
>> E: DEVTYPE=wlan
>> E: ID_BUS=pci
>> E: ID_MODEL_FROM_DATABASE=Wireless 7265 (Dual Band Wireless-AC 7265)
>> E: ID_MODEL_ID=0x095a
>> E: ID_NET_DRIVER=iwlwifi
>> E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
>> E: ID_NET_NAME=wlp2s0
>> E: ID_NET_NAME_MAC=wlxSCRUBBED
>> E: ID_NET_NAME_PATH=wlp2s0
>> E: ID_OUI_FROM_DATABASE=Intel Corporate
>> E: ID_PATH=pci-:02:00.0
>> E: ID_PATH_TAG=pci-_02_00_0
>> E: ID_PCI_CLASS_FROM_DATABASE=Network controller
>> E: ID_PCI_SUBCLASS_FROM_DATABASE=Network controller
>> E: ID_VENDOR_FROM_DATABASE=Intel Corporation
>> E: ID_VENDOR_ID=0x8086
>> E: IFINDEX=2
>> E: INTERFACE=wlp2s0
>> E: SUBSYSTEM=net
>> E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/wlp2s0
>> /sys/subsystem/net/devices/wlp2s0
>> E: TAGS=:systemd:
>> E: USEC_INITIALIZED=23368270
>>
> 
> Ok, that looks fine.
> 
> Would you mind filing this issue upstream at [1] and report back with
> the bug number?
> 
> Thanks,
> Michael
> 
> [1] https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
> 

-- 
David Mirza Ahmad
https://subgraph.com
78A1 CCFD 1C60 4BA7 5E1C C1F2 42D7 08C0 2520 8C7B

Processed: tagging 851060

[Debian Bug Tracking System]

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

> tags 851060 + patch
Bug #851060 [libnids1.21] libnids1.21: can't assemble TCP streams on armhf
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#854719: [pkg-wpa-devel] Bug#854719: Bug#854719: hostapd: Failed to set beacon parameters

[Andrew Shadura]

On 10/02/17 00:05, Vincent Danjean wrote:
> Le 09/02/2017 à 23:20, Andrew Shadura a écrit :
>> Hi,
>>
>> On 9 February 2017 at 21:10, Vincent Danjean  wrote:
>>> Package: hostapd
>>> Version: 1:2.5-2+v2.4-3+b1
>>> Severity: grave
>>> Justification: renders package unusable
>>>
>>>   Hi,
>>>
>>>   I just upgraded a machine from jessie to stretch. With the stretch
>>> version of hostapd, the deamon does not start:
>>> # hostapd /etc/hostapd/hostapd.conf
>>> Configuration file: /etc/hostapd/hostapd.conf
>>> Using interface wlan0 with hwaddr f4:ec:38:c5:fd:94 and ssid "dino-wpa1"
>>> Failed to set beacon parameters
>>> Interface initialization failed
>>> wlan0: interface state UNINITIALIZED->DISABLED
>>> wlan0: AP-DISABLED
>>> wlan0: Unable to setup interface.
>>> wlan0: interface state DISABLED->DISABLED
>>> wlan0: AP-DISABLED
>>> hostapd_free_hapd_data: Interface wlan0_2 wasn't started
>>> wlan0: AP-DISABLED
>>> hostapd_free_hapd_data: Interface wlan0_1 wasn't started
>>> wlan0: AP-DISABLED
>>> hostapd_free_hapd_data: Interface wlan0 wasn't started
>>> nl80211: deinit ifname=wlan0 disabled_11b_rates=0
>>> #
>>>
>>>   If I downgrade the hostapd package to the jessie version
>>> (1:2.3-1+deb8u4), then it works perfectly:
>>> # apt-get install --reinstall hostapd/jessie
>>> [...]
>>> Les paquets suivants seront mis à une VERSION INFÉRIEURE :
>>>   hostapd
>>> 0 mis à jour, 0 nouvellement installés, 1 remis à une version inférieure, 0 
>>> à enlever et 44 non mis à jour.
>>> [...]
>>> Préparation du dépaquetage de .../hostapd_1%3a2.3-1+deb8u4_amd64.deb ...
>>> Dépaquetage de hostapd (1:2.3-1+deb8u4) sur (1:2.5-2+v2.4-3+b1) ...
>>> Paramétrage de hostapd (1:2.3-1+deb8u4) ...
>>> [...]
>>> #  hostapd /etc/hostapd/hostapd.conf
>>> Configuration file: /etc/hostapd/hostapd.conf
>>> Using interface wlan0 with hwaddr f4:ec:38:c5:fd:94 and ssid "dino-wpa1"
>>> Using interface wlan0_1 with hwaddr f4:ec:38:c5:fd:95 and ssid "dino"
>>> Using interface wlan0_2 with hwaddr f4:ec:38:c5:fd:96 and ssid
>>> "dino-guess"
>>> wlan0: interface state UNINITIALIZED->ENABLED
>>> wlan0: AP-ENABLED
>>> [.. and then authentifications from client...]
>>>
>>>   So, it seems there is a major regression in the hostapd package.
>>> Feel free to ask more information if required.
>>
>> I'm going to ask you to tell me what hardware you use.
> 
> From lspci:
> 04:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter 
> (PCI-Express) (rev 01)
> If you need more information, just tell me where to look at.
> 
>> Also, please try
>> and get more logs please, especially those wpa_supplicant produces with
>> -dt (you can add it with a systemd override file).
> 
> I do not use wpa_supplicant. I only run hostapd. I use this computer
> (and this wireless card) as an AP at home.
> You can find in attachment the output of
> # hostapd -dd /etc/hostapd/hostapd.conf
> - for the testing version
> - for the stable version
> - for the unstable version

Here, I meant hostapd. However, wpa_supplicant and hostapd are two parts
of the same software package, and they use the same drivers AFAIK.

>>>   Note that the unstable version works. So I will mark this bug as fixed
>>> for the 1:2.6-3 version as soon as I get its number
>>
>> That's pretty much a bad news, as 2.6 breaks networking for lot more
>> people, it seems.
>>
>> There's a thread about a related issue:
>> http://lists.infradead.org/pipermail/hostap/2017-January/037042.html
>>
>> Please have a look and let me know whether what you're observing is the
>> same bug or not, and whether the patch works.
> 
> I'm not using wpa_supplicant, so it does not seem the same bug.
> Moreover, the proposed patch in
> http://lists.infradead.org/pipermail/hostap/2017-January/037060.html
> do not apply at all for the testing sources.
> In the testing sources, in the wpa_driver_nl80211_set_ap function,
> the "if (beacon_set)" test do not have any "else" clause to patch.

That doesn't sound good. Maybe try emailing the hostap mailing list?

-- 
Cheers,
  Andrew

Bug#854723: diffoscope writes to arbitrary locations on disk based on the contents of an untrusted archive

[Chris Lamb]

Ximin Luo wrote:

> this particular scheme might not work so well with large archives
> with lots and lots of members

Mm although unlikely to be a serious problem as we aren't iterating
over the directory. 

> Also, are you sure this doesn't interfere with the detection of
> order-only differences, or the ability to match up
> similar-member-names?

We still use the archive's member name throughout diffoscope; the
unpacked path shouldn't leak outside of that comparator. Also, the
tests pass… *g*


Regards,

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

Bug#854742: CVE-2017-5930

[Moritz Muehlenhoff]

Package: postfixadmin
Severity: grave
Tags: security

Please see http://seclists.org/oss-sec/2017/q1/345

Cheers,
Moritz

Bug#854740: CVE-2017-5591

[Moritz Muehlenhoff]

Source: slixmpp
Severity: grave
Tags: security

Please see http://seclists.org/oss-sec/2017/q1/373

Cheers,
Moritz

Bug#854723: diffoscope writes to arbitrary locations on disk based on the contents of an untrusted archive

[Ximin Luo]

Ximin Luo:
> Chris Lamb:
>> tags 854723 + pending
>> thanks
>>
>>> diffoscope may write to arbitrary locations on disk depending on the 
>>> contents
>>> of an untrusted archive
>>
>> We can actually avoid all edge-cases of sanitisation by simply not using
>> the supplied filename and maintaining our own mapping.
>>
>> Given this is both safer (and has far less code) I've gone ahead and 
>> committed
>> that here:
>>
>>   
>> https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=632a40828a54b399787c25e7fa243f732aef7e05
>>
> 
> Thanks, this is better.
> 
> However this particular scheme might not work so well with large archives 
> with lots and lots of members (>many thousands), depending on what filesystem 
> the tempdir contained in. I'd suggest to use names like $x/$y where $x = idx 
> // 4096, $y = idx % 4096.
> 

Also, are you sure this doesn't interfere with the detection of order-only 
differences, or the ability to match up similar-member-names?

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#854739: CVE-2017-5591

[Moritz Muehlenhoff]

Source: sleekxmpp
Severity: grave
Tags: security

Please see http://seclists.org/oss-sec/2017/q1/373

Cheers,
Moritz

Bug#854723: diffoscope writes to arbitrary locations on disk based on the contents of an untrusted archive

[Ximin Luo]

Chris Lamb:
> tags 854723 + pending
> thanks
> 
>> diffoscope may write to arbitrary locations on disk depending on the contents
>> of an untrusted archive
> 
> We can actually avoid all edge-cases of sanitisation by simply not using
> the supplied filename and maintaining our own mapping.
> 
> Given this is both safer (and has far less code) I've gone ahead and committed
> that here:
> 
>   
> https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=632a40828a54b399787c25e7fa243f732aef7e05
> 

Thanks, this is better.

However this particular scheme might not work so well with large archives with 
lots and lots of members (>many thousands), depending on what filesystem the 
tempdir contained in. I'd suggest to use names like $x/$y where $x = idx // 
4096, $y = idx % 4096.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#854738: CVE-2017-5604

[Moritz Muehlenhoff]

Package: mcabber
Severity: grave
Tags: security

Please see http://seclists.org/oss-sec/2017/q1/373

Cheers,
Moritz

Bug#854737: CVE-2017-5603

[Moritz Muehlenhoff]

Package: jitsi
Severity: grave
Tags: security

Please see http://seclists.org/oss-sec/2017/q1/373

Cheers,
Moritz

Bug#854735: CVE-2017-5592

[Moritz Muehlenhoff]

Package: profanity
Severity: grave
Tags: security

Please see http://seclists.org/oss-sec/2017/q1/373

Cheers,
Moritz

Bug#854719: [pkg-wpa-devel] Bug#854719: hostapd: Failed to set beacon parameters

[Vincent Danjean]

Le 09/02/2017 à 23:20, Andrew Shadura a écrit :
> Hi,
> 
> On 9 February 2017 at 21:10, Vincent Danjean  wrote:
>> Package: hostapd
>> Version: 1:2.5-2+v2.4-3+b1
>> Severity: grave
>> Justification: renders package unusable
>>
>>   Hi,
>>
>>   I just upgraded a machine from jessie to stretch. With the stretch
>> version of hostapd, the deamon does not start:
>> # hostapd /etc/hostapd/hostapd.conf
>> Configuration file: /etc/hostapd/hostapd.conf
>> Using interface wlan0 with hwaddr f4:ec:38:c5:fd:94 and ssid "dino-wpa1"
>> Failed to set beacon parameters
>> Interface initialization failed
>> wlan0: interface state UNINITIALIZED->DISABLED
>> wlan0: AP-DISABLED
>> wlan0: Unable to setup interface.
>> wlan0: interface state DISABLED->DISABLED
>> wlan0: AP-DISABLED
>> hostapd_free_hapd_data: Interface wlan0_2 wasn't started
>> wlan0: AP-DISABLED
>> hostapd_free_hapd_data: Interface wlan0_1 wasn't started
>> wlan0: AP-DISABLED
>> hostapd_free_hapd_data: Interface wlan0 wasn't started
>> nl80211: deinit ifname=wlan0 disabled_11b_rates=0
>> #
>>
>>   If I downgrade the hostapd package to the jessie version
>> (1:2.3-1+deb8u4), then it works perfectly:
>> # apt-get install --reinstall hostapd/jessie
>> [...]
>> Les paquets suivants seront mis à une VERSION INFÉRIEURE :
>>   hostapd
>> 0 mis à jour, 0 nouvellement installés, 1 remis à une version inférieure, 0 
>> à enlever et 44 non mis à jour.
>> [...]
>> Préparation du dépaquetage de .../hostapd_1%3a2.3-1+deb8u4_amd64.deb ...
>> Dépaquetage de hostapd (1:2.3-1+deb8u4) sur (1:2.5-2+v2.4-3+b1) ...
>> Paramétrage de hostapd (1:2.3-1+deb8u4) ...
>> [...]
>> #  hostapd /etc/hostapd/hostapd.conf
>> Configuration file: /etc/hostapd/hostapd.conf
>> Using interface wlan0 with hwaddr f4:ec:38:c5:fd:94 and ssid "dino-wpa1"
>> Using interface wlan0_1 with hwaddr f4:ec:38:c5:fd:95 and ssid "dino"
>> Using interface wlan0_2 with hwaddr f4:ec:38:c5:fd:96 and ssid
>> "dino-guess"
>> wlan0: interface state UNINITIALIZED->ENABLED
>> wlan0: AP-ENABLED
>> [.. and then authentifications from client...]
>>
>>   So, it seems there is a major regression in the hostapd package.
>> Feel free to ask more information if required.
> 
> I'm going to ask you to tell me what hardware you use.

>From lspci:
04:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter 
(PCI-Express) (rev 01)
If you need more information, just tell me where to look at.

> Also, please try
> and get more logs please, especially those wpa_supplicant produces with
> -dt (you can add it with a systemd override file).

I do not use wpa_supplicant. I only run hostapd. I use this computer
(and this wireless card) as an AP at home.
You can find in attachment the output of
# hostapd -dd /etc/hostapd/hostapd.conf
- for the testing version
- for the stable version
- for the unstable version

>>   Note that the unstable version works. So I will mark this bug as fixed
>> for the 1:2.6-3 version as soon as I get its number
> 
> That's pretty much a bad news, as 2.6 breaks networking for lot more
> people, it seems.
> 
> There's a thread about a related issue:
> http://lists.infradead.org/pipermail/hostap/2017-January/037042.html
> 
> Please have a look and let me know whether what you're observing is the
> same bug or not, and whether the patch works.

I'm not using wpa_supplicant, so it does not seem the same bug.
Moreover, the proposed patch in
http://lists.infradead.org/pipermail/hostap/2017-January/037060.html
do not apply at all for the testing sources.
In the testing sources, in the wpa_driver_nl80211_set_ap function,
the "if (beacon_set)" test do not have any "else" clause to patch.

  Regards,
Vincent

> 
> Thanks!
> 


-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd.conf
ctrl_interface_group=0
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=2 op=0 soft=0 hard=0
nl80211: TDLS supported
nl80211: TDLS external setup
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-0f-ac:10
nl80211: Supported cipher 00-0f-ac:8
nl80211: Supported cipher 00-0f-ac:9
nl80211: Supported cipher 00-0f-ac:6
nl80211: Supported cipher 00-0f-ac:13
nl80211: Supported cipher 00-0f-ac:11
nl80211: Supported cipher 00-0f-ac:12
nl80211: Using driver-based off-channel TX
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 4 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=0 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 

Bug#854736: CVE-2017-5593

[Moritz Muehlenhoff]

Source: psi-plus
Severity: grave
Tags: security

Please see http://seclists.org/oss-sec/2017/q1/373

Cheers,
Moritz

Bug#854734: CVE-2017-5896

[Moritz Muehlenhoff]

Source: mupdf
Severity: grave
Tags: security

Please see http://seclists.org/oss-sec/2017/q1/322

Cheers,
Moritz

Bug#854733: CVE-2017-5367 / CVE-2017-5367 / CVE-2017-5368

[Moritz Muehlenhoff]

Source: zoneminder
Severity: grave
Tags: security

Please see
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5367
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5368
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5595

Cheers,
Moritz

Bug#854727: Multiple vulnerabilities / unsuitable for stretch?

[Moritz Muehlenhoff]

Source: zziplib
Severity: grave
Tags: security

Hi,
multiple security issues have been found in zziplib by Agostino Sarubbo
of Gentoo:

http://www.openwall.com/lists/oss-security/2017/02/09/10
http://www.openwall.com/lists/oss-security/2017/02/09/11
http://www.openwall.com/lists/oss-security/2017/02/09/12
http://www.openwall.com/lists/oss-security/2017/02/09/13
http://www.openwall.com/lists/oss-security/2017/02/09/14
http://www.openwall.com/lists/oss-security/2017/02/09/15
http://www.openwall.com/lists/oss-security/2017/02/09/16
http://www.openwall.com/lists/oss-security/2017/02/09/17
http://www.openwall.com/lists/oss-security/2017/02/09/18
http://www.openwall.com/lists/oss-security/2017/02/09/19
http://www.openwall.com/lists/oss-security/2017/02/09/20

He points out that upstream seems dead:
http://www.openwall.com/lists/oss-security/2017/02/09/21

Aside from that, there's also older, unacknowleged bugs from the
Mayhem project in the BTS.

So unless you want to pick up upstream maintenace yourself, we should
rather remove zziplib from stretch.

Cheers,
Moritz

Bug#854719: [pkg-wpa-devel] Bug#854719: hostapd: Failed to set beacon parameters

[Andrew Shadura]

Hi,

On 9 February 2017 at 21:10, Vincent Danjean  wrote:
> Package: hostapd
> Version: 1:2.5-2+v2.4-3+b1
> Severity: grave
> Justification: renders package unusable
>
>   Hi,
>
>   I just upgraded a machine from jessie to stretch. With the stretch
> version of hostapd, the deamon does not start:
> # hostapd /etc/hostapd/hostapd.conf
> Configuration file: /etc/hostapd/hostapd.conf
> Using interface wlan0 with hwaddr f4:ec:38:c5:fd:94 and ssid "dino-wpa1"
> Failed to set beacon parameters
> Interface initialization failed
> wlan0: interface state UNINITIALIZED->DISABLED
> wlan0: AP-DISABLED
> wlan0: Unable to setup interface.
> wlan0: interface state DISABLED->DISABLED
> wlan0: AP-DISABLED
> hostapd_free_hapd_data: Interface wlan0_2 wasn't started
> wlan0: AP-DISABLED
> hostapd_free_hapd_data: Interface wlan0_1 wasn't started
> wlan0: AP-DISABLED
> hostapd_free_hapd_data: Interface wlan0 wasn't started
> nl80211: deinit ifname=wlan0 disabled_11b_rates=0
> #
>
>   If I downgrade the hostapd package to the jessie version
> (1:2.3-1+deb8u4), then it works perfectly:
> # apt-get install --reinstall hostapd/jessie
> [...]
> Les paquets suivants seront mis à une VERSION INFÉRIEURE :
>   hostapd
> 0 mis à jour, 0 nouvellement installés, 1 remis à une version inférieure, 0 à 
> enlever et 44 non mis à jour.
> [...]
> Préparation du dépaquetage de .../hostapd_1%3a2.3-1+deb8u4_amd64.deb ...
> Dépaquetage de hostapd (1:2.3-1+deb8u4) sur (1:2.5-2+v2.4-3+b1) ...
> Paramétrage de hostapd (1:2.3-1+deb8u4) ...
> [...]
> #  hostapd /etc/hostapd/hostapd.conf
> Configuration file: /etc/hostapd/hostapd.conf
> Using interface wlan0 with hwaddr f4:ec:38:c5:fd:94 and ssid "dino-wpa1"
> Using interface wlan0_1 with hwaddr f4:ec:38:c5:fd:95 and ssid "dino"
> Using interface wlan0_2 with hwaddr f4:ec:38:c5:fd:96 and ssid
> "dino-guess"
> wlan0: interface state UNINITIALIZED->ENABLED
> wlan0: AP-ENABLED
> [.. and then authentifications from client...]
>
>   So, it seems there is a major regression in the hostapd package.
> Feel free to ask more information if required.

I'm going to ask you to tell me what hardware you use. Also, please try
and get more logs please, especially those wpa_supplicant produces with
-dt (you can add it with a systemd override file).

>   Note that the unstable version works. So I will mark this bug as fixed
> for the 1:2.6-3 version as soon as I get its number

That's pretty much a bad news, as 2.6 breaks networking for lot more
people, it seems.

There's a thread about a related issue:
http://lists.infradead.org/pipermail/hostap/2017-January/037042.html

Please have a look and let me know whether what you're observing is the
same bug or not, and whether the patch works.

Thanks!

-- 
Cheers,
  Andrew

Bug#854289: newbiedoc: Too outdated for being useful

[Chris Lamb]

Chris Lamb wrote:

> I agree. Any objection to removing this from Debian...?

Filed as #854726.


Regards,

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

Processed: fixed 854719 in 1:2.6-3

[Debian Bug Tracking System]

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

> fixed 854719 1:2.6-3
Bug #854719 [hostapd] hostapd: Failed to set beacon parameters
Marked as fixed in versions wpa/2.6-3.
> thanks
Stopping processing here.

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

Bug#854723: diffoscope writes to arbitrary locations on disk based on the contents of an untrusted archive

[Chris Lamb]

tags 854723 + pending
thanks

> diffoscope may write to arbitrary locations on disk depending on the contents
> of an untrusted archive

We can actually avoid all edge-cases of sanitisation by simply not using
the supplied filename and maintaining our own mapping.

Given this is both safer (and has far less code) I've gone ahead and committed
that here:

  
https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=632a40828a54b399787c25e7fa243f732aef7e05


Regards,

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

Processed: Re: Bug#854723: diffoscope writes to arbitrary locations on disk based on the contents of an untrusted archive

[Debian Bug Tracking System]

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

> tags 854723 + pending
Bug #854723 [diffoscope] diffoscope writes to arbitrary locations on disk based 
on the contents of an untrusted archive
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#854587: icedove: incorrect start-version in {icedove,thunderbird}.maintscript

[Carsten Schoenert]

Hello Viktor,

On Thu, Feb 09, 2017 at 09:01:00PM +, Viktor Jägersküpper wrote:
 
> A suggestion from a user's point of view:
> 
> You could also move/incorporate the content of the icedove.NEWS file to
> the popup which will be shown during the migration of the icedove
> profile(s) (#854488). This covers the (unusual?) case when
> apt-listchanges is not installed.

https://anonscm.debian.org/cgit/pkg-mozilla/icedove.git/commit/?h=debian/experimental=f3d64ae40b8538d666d2cc5b2ae5fd74642bdbfb

Attention, it's still hot. ;)

> I also want to mention users who don't have root privileges like me when
> I used a PC in my university. These users will never see the
> icedove.NEWS info, but only the popup, and they will probably see the
> Icedove->Thunderbird link provided by the icedove.desktop file.
> 
> The reason for my suggestion is that I believe you have already planned
> to provide the info about the re-branding to thunderbird
> - for jessie and wheezy in the security-announce email
> - for upgrades from jessie to stretch in the release notes

We got recently the o.k. from the release team for introducing the
de-branded Thunderbird packages into the Stretch release. So we can now
start.
We was thinking about the Jessie and Wheezy releases but we will now
start with Stretch. Hopefully we don't have to much adjust here so we
can go quickly over to the de-branding in the other releases too.

> So you only need to have the new src:thunderbird package in stretch (the
> release team has to give their ok to this of course because it is a new
> source package), jessie and wheezy.

No, not really as this requirement is only true about binary packages.
So we don't need to go through NEW again for the change of the source
package. The stable-security team was noting they will probably accept
the new thunderbird packages. But we need to get in contact with them.

> Maybe I forgot something, but I hope this will simplify the work for
> you. It is of course your decision if the additional work for two source
> packages is worth it only for giving the info about the re-branding via
> apt-listchanges. My point of view is that you will have the attention of
> all users when they want to *use* Icedove/Thunderbird, that means when
> the actual migration of the profile(s) takes place, and the popup is the
> best way to get attention.

We will see if we still got now some corner cases with the new
additional pop-up window. With the 45.7.1 starting we need to collect
other probably visible issues of the transmigration. It's planned to
upload the next version to unstable/sid this weekend.

Regards
Carsten

Bug#854723: diffoscope writes to arbitrary locations on disk based on the contents of an untrusted archive

[Ximin Luo]

Package: diffoscope
Version: 67
Severity: grave
Tags: patch security
Justification: user security hole

Dear Maintainer,

5fdfe91e71f1c520d902350b18f793b8c69d9118 introduced a security hole where
diffoscope may write to arbitrary locations on disk depending on the contents
of an untrusted archive. For example, comparing the following two files:

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=843811;filename=libBrokenLocale.a.0;msg=5
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=843811;filename=libBrokenLocale.a.1;msg=5

Traceback (most recent call last):
  File "/home/infinity0/xx/diffoscope/diffoscope/main.py", line 281, in main
sys.exit(run_diffoscope(parsed_args))
[..]
  File 
"/home/infinity0/xx/diffoscope/diffoscope/comparators/utils/libarchive.py", 
line 174, in extract
self.ensure_unpacked()
  File 
"/home/infinity0/xx/diffoscope/diffoscope/comparators/utils/libarchive.py", 
line 219, in ensure_unpacked
os.makedirs(os.path.dirname(dst), exist_ok=True)
  File "/usr/lib/python3.5/os.py", line 241, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/SYM64'

Note that this could easily have been something like /home/infinity0/.profile.

I have pushed a nearly-complete fix to git (after version 75 was just released)
which prevents the writes. However reads are still done using the uncleaned
names, but this is a much less severe issue. So, if I don't supply a fix for
the second lesser issue soon, the existing fix should be released ASAP.

X

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 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 diffoscope depends on:
ii  python3-libarchive-c   2.1-3.1
ii  python3-magic  1:5.29-3
ii  python3-pkg-resources  33.1.1-1
pn  python3:any

Versions of packages diffoscope recommends:
ii  acl2.2.52-3
ii  apktool2.2.1+dfsg-2
ii  binutils-multiarch 2.27.90.20170124-2
ii  bzip2  1.0.6-8.1
ii  caca-utils 0.99.beta19-2+b1
ii  colord 1.3.3-2
ii  cpio   2.11+dfsg-6
ii  default-jdk [java-sdk] 2:1.8-58
ii  default-jdk-headless   2:1.8-58
ii  enjarify   1:1.0.3-3
ii  fontforge-extras   0.3-4
ii  fp-utils   3.0.0+dfsg-10
ii  fp-utils-3.0.0 [fp-utils]  3.0.0+dfsg-10
ii  genisoimage9:1.1.11-3
ii  gettext0.19.8.1-2
ii  ghc8.0.1-17
ii  ghostscript9.20~dfsg-2
ii  gnupg  2.1.18-3
ii  jsbeautifier   1.6.4-6
ii  llvm   1:3.8-34+b1
ii  mono-utils 4.6.2.7+dfsg-1
ii  openjdk-8-jdk [java-sdk]   8u121-b13-2
ii  openssh-client 1:7.4p1-6
ii  pdftk  2.02-4+b1
ii  poppler-utils  0.48.0-2
ii  python3-argcomplete1.8.1-1
ii  python3-debian 0.1.30
ii  python3-guestfs1:1.34.3-7
ii  python3-progressbar2.3-4
ii  python3-rpm4.12.0.2+dfsg1-1
ii  python3-tlsh   3.4.4+20151206-1+b1
ii  rpm2cpio   4.12.0.2+dfsg1-1
ii  sng1.1.0-1+b1
ii  sqlite33.16.2-2
ii  squashfs-tools 1:4.3-3
ii  unzip  6.0-21
ii  vim-common 2:8.0.0197-1
ii  xxd2:8.0.0197-1
ii  xz-utils   5.2.2-1.2

Versions of packages diffoscope suggests:
ii  libjs-jquery  3.1.1-2

-- no debconf information

Bug#854587: icedove: incorrect start-version in {icedove,thunderbird}.maintscript

[Viktor Jägersküpper]

Andreas Beckmann:
> On 2017-02-08 16:23, Carsten Schoenert wrote:
>>> PS: do you plan to rename the source package to thunderbird, too?
>>
>> Yes, this is planned. But probaly after the Stretch release. Otherwise
>> we may conflict with apt-listchanges and the wanted pop-up for the
>> change of the icedove package.
> 
> You could continue building the transitional packages from src:icedove
> (so icedove.NEWS will be shown as intended) and only move the new
> content-bearing thunderbird packages to src:thunderbird.
> IMO that would make maintenance over stretch lifetime easier ... than
> having src:icedove (non-transitional) in stretch (stable) and
> src:thunderbird in buster (testing) over stretch's lifetime (expecting
> some new upstream releases going into stretch, too).
> It might make maintenance a bit more difficult for jessie (oldstable)
> though ...

A suggestion from a user's point of view:

You could also move/incorporate the content of the icedove.NEWS file to
the popup which will be shown during the migration of the icedove
profile(s) (#854488). This covers the (unusual?) case when
apt-listchanges is not installed.

I also want to mention users who don't have root privileges like me when
I used a PC in my university. These users will never see the
icedove.NEWS info, but only the popup, and they will probably see the
Icedove->Thunderbird link provided by the icedove.desktop file.

The reason for my suggestion is that I believe you have already planned
to provide the info about the re-branding to thunderbird
- for jessie and wheezy in the security-announce email
- for upgrades from jessie to stretch in the release notes

So you only need to have the new src:thunderbird package in stretch (the
release team has to give their ok to this of course because it is a new
source package), jessie and wheezy.

Maybe I forgot something, but I hope this will simplify the work for
you. It is of course your decision if the additional work for two source
packages is worth it only for giving the info about the re-branding via
apt-listchanges. My point of view is that you will have the attention of
all users when they want to *use* Icedove/Thunderbird, that means when
the actual migration of the profile(s) takes place, and the popup is the
best way to get attention.

Viktor

Bug#854468: marked as done (lprng silently loses authentication support when compiled with OpenSSL 1.1)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 20:50:48 +
with message-id 
and subject line Bug#854468: fixed in lprng 3.8.B-2.1
has caused the Debian Bug report #854468,
regarding lprng silently loses authentication support when compiled with 
OpenSSL 1.1
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.)


-- 
854468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lprng
Version: 3.8.B-2
Severity: serious
Tags: stretch sid
Control: block 827061 by -1

https://buildd.debian.org/status/package.php?p=lprng

...
checking if ssl authentication is disabled... enabled
checking for OpenSSL include files... found in /usr/include
checking for OpenSSL libraries... not found.
...
--- End Message ---
--- Begin Message ---
Source: lprng
Source-Version: 3.8.B-2.1

We believe that the bug you reported is fixed in the latest version of
lprng, 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 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated lprng 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Feb 2017 21:20:30 +0100
Source: lprng
Binary: lprng
Architecture: source
Version: 3.8.B-2.1
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Sebastian Andrzej Siewior 
Description:
 lprng  - lpr/lpd printer spooling system
Closes: 854468
Changes:
 lprng (3.8.B-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Don't lose authentication support when compiled with OpenSSL 1.1, patch by
 Reiner Herrmann  (Closes: #854468).
Checksums-Sha1:
 4384937b359c5215384ae0f963a9395f02d9819c 1785 lprng_3.8.B-2.1.dsc
 befb1c27d6afb2488ee5952c08655eb001b6c3ec 31804 lprng_3.8.B-2.1.debian.tar.xz
 cbdfd96689934dca62c52977e12ea3da6c8048c0 4878 lprng_3.8.B-2.1_source.buildinfo
Checksums-Sha256:
 1a2ecc7447f4b4af3fa02616be72d77eae2b6e24f37805b074bf70ea719bc325 1785 
lprng_3.8.B-2.1.dsc
 ed541ef35e2352884c8eb47904d021aa9598151c51b6a0a6ed15d38cd8dbc0bf 31804 
lprng_3.8.B-2.1.debian.tar.xz
 a3fd51c9a87d27761bb7b334eea80690343bfbc4e180ea07b76bca7a4cf0 4878 
lprng_3.8.B-2.1_source.buildinfo
Files:
 71e16729d4b0ec0a39b4e764b287fbc1 1785 net extra lprng_3.8.B-2.1.dsc
 45958c62824a065b2f99c3bb7bd7b45f 31804 net extra lprng_3.8.B-2.1.debian.tar.xz
 9e7c60a38abbce5f18f92eed5f711700 4878 net extra 
lprng_3.8.B-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZCVGlf/wqkRmzBnme5boFiqM9dEFAlibfnEACgkQe5boFiqM
9dG2XA/+NVmyFLZTSHNsGT9GOZjjhEv84tvV5nvtBPbw7OIdLPkBZGZqwm0mi7lx
OGFWtsvqeErcy1vh4q2xNcgXszobx/W9uRwgS0QY/8b5IgJkQPaRV155bjpR5qN9
prEQi5ePiKMCo/AN3sUMszuOEOKtt1XdAP7uzJjaPszAR7W8QF5gKl/G+3oBTeZY
0U5e8XShDril5SnwXFUN3RM4I2/8SIGHG0AGa2YOWoekc3Pqeku0PPUKz5yO9Qap
oEZ5TmJHwBoUAaEmdkkY45q/b5paauSWOVUKYHD9YXrBGPPzjpPSl705NtiS+N3O
6q3n4lEdOn5Aquf2fznWBr4fuOxEFzrwPBeHPIAhkrR3vn+IV2MsnTUmaV99tYrs
GHqnsVlEiBu7Eo74+MRM7irbf6LNo0sjE6iwnd/squ0bQ/j/Sc5i3bfOk6dYXSKd
OVpLA7VUEw7aSp1iK/jEkxna5qBnNnHIz7UPrOiK2hFMZoXsoXEg0rzCUYrZPodL
MzMY4BmrKqfdyL7UpH1ymc4zHRQIvys/g84Pj/H9VaWWiLCyyAgKwgsiTYYa6Ntl
iWe3eeDlg1cfzZYQ6Djtkns/aYTCk3ShKgqtrIfaNBwvku0jtpF0ftjDT45AJKy1
fY27Gr8vwns7cjNGJ1/nJ4zdTXhGm3Gea/dhBF06FfZ/mSxycfc=
=Ibv8
-END PGP SIGNATURE End Message ---

Processed: Re: python3-django-cors-headers: Does not work with Django 1.10

[Debian Bug Tracking System]

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

> severity 854716 serious
Bug #854716 [python3-django-cors-headers] python3-django-cors-headers: Does not 
work with Django 1.10
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#854720: sidedoor-sudo: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/sidedoor/examples/sudoers

[Andreas Beckmann]

Package: sidedoor-sudo
Version: 0.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

  Selecting previously unselected package sidedoor-sudo.
  (Reading database ... 
(Reading database ... 4686 files and directories currently installed.)
  Preparing to unpack .../sidedoor-sudo_0.2.0-2_all.deb ...
  Unpacking sidedoor-sudo (0.2.0-2) ...
  Setting up sidedoor-sudo (0.2.0-2) ...
  Error: The new file /usr/share/doc/sidedoor/examples/sudoers does not exist!
  dpkg: error processing package sidedoor-sudo (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   sidedoor-sudo


Cheers,

Andreas


sidedoor-sudo_0.2.0-2.log.gz
Description: application/gzip

Bug#854719: hostapd: Failed to set beacon parameters

[Vincent Danjean]

Package: hostapd
Version: 1:2.5-2+v2.4-3+b1
Severity: grave
Justification: renders package unusable

  Hi,

  I just upgraded a machine from jessie to stretch. With the stretch
version of hostapd, the deamon does not start:
# hostapd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
Using interface wlan0 with hwaddr f4:ec:38:c5:fd:94 and ssid "dino-wpa1"
Failed to set beacon parameters
Interface initialization failed
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED 
wlan0: Unable to setup interface.
wlan0: interface state DISABLED->DISABLED
wlan0: AP-DISABLED 
hostapd_free_hapd_data: Interface wlan0_2 wasn't started
wlan0: AP-DISABLED 
hostapd_free_hapd_data: Interface wlan0_1 wasn't started
wlan0: AP-DISABLED 
hostapd_free_hapd_data: Interface wlan0 wasn't started
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
#

  If I downgrade the hostapd package to the jessie version
(1:2.3-1+deb8u4), then it works perfectly:
# apt-get install --reinstall hostapd/jessie
[...]
Les paquets suivants seront mis à une VERSION INFÉRIEURE :
  hostapd
0 mis à jour, 0 nouvellement installés, 1 remis à une version inférieure, 0 à 
enlever et 44 non mis à jour.
[...]
Préparation du dépaquetage de .../hostapd_1%3a2.3-1+deb8u4_amd64.deb ...
Dépaquetage de hostapd (1:2.3-1+deb8u4) sur (1:2.5-2+v2.4-3+b1) ...
Paramétrage de hostapd (1:2.3-1+deb8u4) ...
[...]
#  hostapd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
Using interface wlan0 with hwaddr f4:ec:38:c5:fd:94 and ssid "dino-wpa1"
Using interface wlan0_1 with hwaddr f4:ec:38:c5:fd:95 and ssid "dino"
Using interface wlan0_2 with hwaddr f4:ec:38:c5:fd:96 and ssid
"dino-guess"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED 
[.. and then authentifications from client...]

  So, it seems there is a major regression in the hostapd package.
Feel free to ask more information if required.

  Note that the unstable version works. So I will mark this bug as fixed
for the 1:2.6-3 version as soon as I get its number

  Regards
Vincent

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

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

Versions of packages hostapd depends on:
ii  libc6  2.24-9
ii  libnl-3-2003.2.27-1
ii  libnl-genl-3-200   3.2.27-1
ii  libnl-route-3-200  3.2.27-1
ii  libssl1.0.01.0.2k-1~bpo8+1
ii  lsb-base   9.20161125

hostapd recommends no packages.

hostapd suggests no packages.

-- no debconf information

Bug#854587: icedove: incorrect start-version in {icedove,thunderbird}.maintscript

[Andreas Beckmann]

On 2017-02-08 16:23, Carsten Schoenert wrote:
>> PS: do you plan to rename the source package to thunderbird, too?
> 
> Yes, this is planned. But probaly after the Stretch release. Otherwise
> we may conflict with apt-listchanges and the wanted pop-up for the
> change of the icedove package.

You could continue building the transitional packages from src:icedove
(so icedove.NEWS will be shown as intended) and only move the new
content-bearing thunderbird packages to src:thunderbird.
IMO that would make maintenance over stretch lifetime easier ... than
having src:icedove (non-transitional) in stretch (stable) and
src:thunderbird in buster (testing) over stretch's lifetime (expecting
some new upstream releases going into stretch, too).
It might make maintenance a bit more difficult for jessie (oldstable)
though ...


Andreas

Bug#850559: openmpi-bin: default for oversubscription changed

[Alastair McKinstry]

Hi,

Debian stretch is now frozen.

The next version of openmpi 2.0.2 (released last week!) contains an
SOVERSION transition, and hasn't a hope of making stretch, IMO.

While I can file an upstream bug to get the default changed, it would
happen at best in the next release,  June-July timeframe. This gives
realistically two options:
(1) Cherry pick a fix / patch to undo the change to openmpi to revert
the behavior. Have the same program fail to work across different
platforms due to our local version of openmpi.
(2) Add the '--oversubscribe' flag / set -np correctly on the test cases
of the packages affected.

Personally I favour (2).

(In the interests of disclosure, I will have to do an upload of a new
version of openmpi anyway for stretch, to fix #848574. This will be a
copy of 2.0.2 backing out the API change that necessitated the SOVERSION
change, but only that).

Best regards
Alastair


-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 




signature.asc
Description: OpenPGP digital signature

Bug#852130: redmine: fails to install, *purge*, and install again - maybe an issue with dbconfig-common?

[Paul Gevers]

On 09-02-17 13:35, Antonio Terceiro wrote:
> When re-installing redmine after having it purged, it seems that
> dbconfig-common is not re-recreating the configuration file. When
> debugging this, I tested both deleting and not deleting the database,
> but always selecting "deconfigure database using dbconfig-common".
> 
> The original context if in the bug report here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852130
> 
> Could you maybe check if that is the case?

Helped on IRC: redmine needs to handle deleting configuration files with
ucf during purging itself, as documented:

https://www.debian.org/doc/manuals/dbconfig-common/ch-develguide.html#s-genconfig

Paul



signature.asc
Description: OpenPGP digital signature

Bug#854430: marked as done (fritzing: Fritzing fails to find core parts)

[Debian Bug Tracking System]

Your message dated Thu, 9 Feb 2017 19:02:50 +0100
with message-id <20170209180250.3i2vzxt3bbctq6gb@localhost>
and subject line The last version provides the bugfix
has caused the Debian Bug report #854430,
regarding fritzing: Fritzing fails to find core parts
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.)


-- 
854430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fritzing
Version: 0.9.3b+dfsg-4
Severity: grave

Similar to 847655, while displaying a screen that says, "loading bin
'Core Parts'", Fritzing displays another screen that says, "Cannot read
file screw_terminal_2_3.5mm.fzp: No such file or directory.".  That file
exists in /usr/share/fritzing/parts/core/.  After clicking OK on that
screen, Fritzing displays a screen titled "Unable to find the following
143 parts:".  I randomly selected several and all were in
/usr/share/fritzing/parts/core.  After continuing from there, almost no
parts are displayed.

Directly calling /usr/bin/fritzing instead of the wrapper
/usr/bin/Fritzing generates an error that it cannot find the file
/usr/share/fritzing/parts/core/bins/core.fzb.  That file is actually in
/usr/share/fritzing/parts/bins/core.fzb.  Again, continuing results in
almost no parts displayed.

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fritzing depends on:
ii  fritzing-data 0.9.3b+dfsg-4
ii  libc6 2.24-9
ii  libgcc1   1:6.3.0-6
ii  libgit2-240.24.5-1
ii  libgl1-mesa-glx [libgl1]  13.0.4-1
ii  libqt5concurrent5 5.7.1+dfsg-3+b1
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5network55.7.1+dfsg-3+b1
ii  libqt5printsupport5   5.7.1+dfsg-3+b1
ii  libqt5serialport5 5.7.1~20161021-2
ii  libqt5sql55.7.1+dfsg-3+b1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+b1
ii  libqt5svg55.7.1~20161021-2
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5xml55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-6
ii  zlib1g1:1.2.8.dfsg-5

fritzing recommends no packages.

Versions of packages fritzing suggests:
ii  fritzing-parts  0.9.3b-1

-- no debconf information


-- 
Neil Roeth
--- End Message ---
--- Begin Message ---
Fritzing version 0.9.3b+dfsg-4 provides a workaround for this bug: it
invokes the command 'fritzing' after a working directory change.

Please be sure to call the command 'Fritzing' in order to launch it
safely (this command name did not change, and the .desktop file taken in
account in the applications menu behaves as expected).



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

Bug#826727: anki: Anki does not start anymore

[Julian Gilbey]

On Mon, Jan 30, 2017 at 09:46:46PM +, Julian Gilbey wrote:
> As this is a grave bug, I propose uploading an NMU with a working
> version in about a week unless you request me not to.

I have just uploaded version 2.1.0+dfsg~a10-0.1 to DELAYED/7.  I've
also created a separate git branch in collab-maint called
anki-2.1alpha with the current version of the sources in it.  Feel
free to merge this into master if you wish to.

Best wishes,

   Julian

Bug#853887: marked as done (ruby-signet: conflicts with ruby-uuidtools over securerandom.rb)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 17:48:37 +
with message-id 
and subject line Bug#853887: fixed in ruby-uuidtools 2.1.5-2
has caused the Debian Bug report #853887,
regarding ruby-signet: conflicts with ruby-uuidtools over securerandom.rb
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.)


-- 
853887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-signet
Version: 0.7.3-1
Severity: serious
Justification: Policy 6.6(4)

ruby-signet is impossible to install alongside ruby-uuidtools:

  Unpacking ruby-signet (0.7.3-1) ...
  dpkg: error processing archive 
/tmp/user/0/apt-dpkg-install-psUCUp/19-ruby-signet_0.7.3-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/compat/securerandom.rb', 
which is also in package ruby-uuidtools 2.1.5-1

Could you please take a look?  You might consider splitting
securerandom.rb into its own package on which ruby-signet and
ruby-uuidtools both depend.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: ruby-uuidtools
Source-Version: 2.1.5-2

We believe that the bug you reported is fixed in the latest version of
ruby-uuidtools, 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 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marc Dequènes (Duck)  (supplier of updated ruby-uuidtools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Feb 2017 06:14:56 +0900
Source: ruby-uuidtools
Binary: ruby-uuidtools ruby-uuidtools-doc
Architecture: source all
Version: 2.1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Marc Dequènes (Duck) 
Changed-By: Marc Dequènes (Duck) 
Description:
 ruby-uuidtools - UUIDs generation library for Ruby
 ruby-uuidtools-doc - UUIDs generation library for Ruby - documentation
Closes: 853887
Changes:
 ruby-uuidtools (2.1.5-2) unstable; urgency=medium
 .
   * Removed embedded compat library, useless and causing conflict
 (Closes: #853887)
Checksums-Sha1:
 794c52cb2c3f809bf8cefb52ac36b2fb375bde74 2122 ruby-uuidtools_2.1.5-2.dsc
 dec7dffbfe39c8d942c5ab3c1a9172feab62f8ea 4156 
ruby-uuidtools_2.1.5-2.debian.tar.xz
 7a6cf2dd0862d753705073007fa3236a3e2c71c9 1342782 
ruby-uuidtools-doc_2.1.5-2_all.deb
 e4320aee673ba7967d127eefd3a1c688823689b0 10902 ruby-uuidtools_2.1.5-2_all.deb
 a58339377ae1b415543c3607ec1ae88a7e2a5fca 5995 
ruby-uuidtools_2.1.5-2_amd64.buildinfo
Checksums-Sha256:
 d649a8f6087093e83889fbab64f67bc5486b099ae63f07ed95bb0ad63adce6df 2122 
ruby-uuidtools_2.1.5-2.dsc
 c07bc2bef7f4ea938f06a2b78bee7511ddeeb059ae83e21f3a2df5a710a284be 4156 
ruby-uuidtools_2.1.5-2.debian.tar.xz
 eb18af8551ce81687f8327e4319dd86d17798f96ab9b497add63f5bf2b9f12ec 1342782 
ruby-uuidtools-doc_2.1.5-2_all.deb
 39e75a598e4d576fb052b0e47697c443dae3a5f69897b032407e5a7cb5ea23bc 10902 
ruby-uuidtools_2.1.5-2_all.deb
 fa050cbb00091ec87139460044d38dfccc7b275eac070d1a9d795823cd781b04 5995 
ruby-uuidtools_2.1.5-2_amd64.buildinfo
Files:
 22dee2b04301b5d9eda5f4df19518e7d 2122 ruby optional ruby-uuidtools_2.1.5-2.dsc
 7f7b4eaa86e7928dfe83476b3da487db 4156 ruby optional 
ruby-uuidtools_2.1.5-2.debian.tar.xz
 2c5cea717799eb184f87743b884c255c 1342782 doc optional 
ruby-uuidtools-doc_2.1.5-2_all.deb
 f34e2184d366053b112600c7b1fca015 10902 ruby optional 
ruby-uuidtools_2.1.5-2_all.deb
 9cc96c4580869d5315956693741612fb 5995 ruby optional 
ruby-uuidtools_2.1.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlicoBgACgkQVen596wc
RD9HZhAAkoDX4UnUihWilOPCb/Gb6e1U18/opUooixsnSfFZJC1z1aCfPBaCjO2F
8YOei4/dPKHP2ax6TDKp7fdbINehaJIrvK3b5m0oMah6P5XZ7Ih5xotRo3c4gplm
iDe9b8sWRWUAdEKgaBh0/aAGfzv/1ZCGf+xnfPRGGEtnT0hY4RKQV775SEhd46Df
rzbZMroYUC7KHnGArT0uGDIDdapwLxhg/iMaaOQMHjSYEpsexaPX2MbjPBvm/ZpF
3yyMcs09xS5R+C+qQZIxYsiNIaAbObox08nAkdT4BhX11cS3MrDr7lzm9JMO7VYk

Bug#853755: marked as done (udev: Doesn't start after upgrade mipsel, powerpc)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 17:34:33 +
with message-id 
and subject line Bug#852811: fixed in systemd 232-16
has caused the Debian Bug report #852811,
regarding udev: Doesn't start after upgrade mipsel, powerpc
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.)


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

Boot method: ISO image
Image version: 
http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso
Date: Tue Jan 31 16:18:45 2017

Machine: qemu VM
Processor: ppc64el
Memory: 4Gb
Partitions: 
/dev/sda1 7.3 MBPowerPC PReP boot partition
/dev/sda2 6.6 GBext4
/dev/sda3 4.2 GBswap
 
Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Using qemu, I created a ppc64el virtual machine.
I selected the guided partitioning to use the entire disk (all the default 
options).
The installation went well but it failed to boot then.
I got the same on P8 PowerVM and P8 baremetal.


Loading Linux 4.9.0-1-powerpc64le ...
Loading initial ramdisk ...
OF stdout device is: /vdevice/vty@7100
Preparing to boot Linux version 4.9.0-1-powerpc64le 
(debian-ker...@lists.debian.org) (gcc version 6.3.0 20161229 (Debian 6.3.0-2) ) 
#1 SMP Debian 4.9.2-2 (2017-01-12)
Detected machine type: 0101
Max number of cores passed to firmware: 512 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
command line: BOOT_IMAGE=/boot/vmlinux-4.9.0-1-powerpc64le root=/dev/sda2 ro 
quiet
memory layout at init:
  memory_limit :  (16 MB aligned)
  alloc_bottom : 0420
  alloc_top: 3000
  alloc_top_hi : 0001
  rmo_top  : 3000
  ram_top  : 0001
instantiating rtas at 0x2fff... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0421 -> 0x04210a2f
Device tree struct  0x0422 -> 0x0423
Quiescing Open Firmware ...
Booting Linux via __start() @ 0x0200 ...
 -> smp_release_cpus()
spinning_secondaries = 3
 <- smp_release_cpus()
Linux ppc64le
#1 SMP Debian 4./dev/sda2: clean, 29927/400624 files, 271614/160 blocks
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[DEPEND] Dependency failed for Flush Journal to Persistent Storage.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Stopped Journal Service.
 Starting Journal Service...
 Starting Apply Kernel Variables...
[  OK  ] Started Remount Root and Kernel File Systems.
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[  OK  ] Stopped Journal Service.
 Starting Journal Service...
 Starting udev Coldplug all Devices...
 Starting Load/Save Random Seed...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Stopped Journal Service.
 Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[  OK  ] Stopped Journal Service.
 Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[  OK  ] Stopped Journal Service.
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Create Static Device Nodes in /dev.
 Starting udev Kernel Device Manager...
[1.398789] systemd[968]: systemd-udevd.service: Failed at step 
ADDRESS_FAMILIES spawning /lib/systemd/systemd-udevd: File exists
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
 Starting udev Kernel Device Manager...
[1.423971] systemd[978]: systemd-udevd.service: Failed at step 
ADDRESS_FAMILIES spawning 

Bug#852811: marked as done (udev: Doesn't start after upgrade mipsel, powerpc)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 17:34:33 +
with message-id 
and subject line Bug#852811: fixed in systemd 232-16
has caused the Debian Bug report #852811,
regarding udev: Doesn't start after upgrade mipsel, powerpc
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.)


-- 
852811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 232-14
Severity: important

Dear Maintainer,

Maybe the problem is because / is a RAID0 ?

Setting up udev (232-14) ...
addgroup: The group `input' already exists as a system group. Exiting.
Job for systemd-udevd.service failed because the control process exited with 
error code.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript udev, action "restart" failed.
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor 
preset: enabled)
   Active: activating (start) since Fri 2017-01-27 14:50:00 CET; 16ms ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
 Main PID: 13630 ((md-udevd))
Tasks: 1
   CGroup: /system.slice/systemd-udevd.service
   ‣ 13630 [(md-udevd)]

Jan 27 14:50:00 fabian.marillat.net systemd[1]: Starting udev Kernel Device 
Manager...
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1


$ systemctl status systemd-udevd.service
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Fri 2017-01-27 14:51:23 CET; 3min 
52s ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
  Process: 15711 ExecStart=/lib/systemd/systemd-udevd (code=exited, 
status=232/ADDRESS_FAMILIES)
 Main PID: 15711 (code=exited, status=232/ADDRESS_FAMILIES)

Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Main 
process exited, code=exited, status=232/ADDRESS_FAMILIES
Jan 27 14:51:23 fabian.marillat.net systemd[1]: Failed to start udev Kernel 
Device Manager.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Unit 
entered failed state.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Failed 
with result 'exit-code'.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Service 
has no hold-off time, scheduling restart.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: Stopped udev Kernel Device 
Manager.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Start 
request repeated too quickly.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: Failed to start udev Kernel 
Device Manager.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Unit 
entered failed state.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Failed 
with result 'exit-code'.




Christian

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc64)

Kernel: Linux 4.9.0-1-powerpc64 (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 udev depends on:
ii  adduser  3.115
ii  dpkg 1.18.19
ii  libacl1  2.2.52-3
ii  libblkid12.28.2-1
ii  libc62.24-9
ii  libgcc1  1:6.3.0-5
ii  libkmod2 23-2
ii  libselinux1  2.6-2
ii  libudev1 232-14
ii  lsb-base 9.20161125
ii  procps   2:3.3.12-3
ii  util-linux   2.28.2-1

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  232-14

-- debconf information:
  udev/new_kernel_needed: false
  udev/title/upgrade:
  udev/reboot_needed:
  udev/sysfs_deprecated_incompatibility:

P: /devices/breakpoint
E: DEVPATH=/devices/breakpoint
E: SUBSYSTEM=event_source

P: /devices/cpu
E: DEVPATH=/devices/cpu
E: SUBSYSTEM=event_source

P: /devices/pci:00/:00:0b.0
E: DEVPATH=/devices/pci:00/:00:0b.0
E: ID_MODEL_FROM_DATABASE=CPC945 PCIe Bridge
E: ID_PCI_CLASS_FROM_DATABASE=Bridge
E: ID_PCI_INTERFACE_FROM_DATABASE=Normal decode
E: ID_PCI_SUBCLASS_FROM_DATABASE=PCI bridge
E: ID_VENDOR_FROM_DATABASE=Apple Inc.
E: MODALIAS=pci:v106Bd005Bsvsdbc06sc04i00
E: OF_ALIAS_0=pci0
E: OF_COMPATIBLE_0=u4-pcie
E: OF_COMPATIBLE_N=1
E: OF_FULLNAME=/pci@0,f000
E: 

Processed: [bts-link] source package ruby-minitar

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package ruby-minitar
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #853249 (http://bugs.debian.org/853249)
> # Bug title: ruby-archive-tar-minitar: CVE-2016-10173: directory traversal 
> vulnerability
> #  * https://github.com/halostatue/minitar/issues/16
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 853249 + fixed-upstream
Bug #853249 [ruby-archive-tar-minitar] ruby-archive-tar-minitar: 
CVE-2016-10173: directory traversal vulnerability
Added tag(s) fixed-upstream.
> usertags 853249 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 853249 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#809669: unattended-upgrades: files got created under /var/ mountpoint

[Alexandre Detiste]

Le jeudi 9 février 2017, 17 h 14 min 44 s CET Louis Bouchard a écrit :
> The unattended-upgrade-shutdown script uses a lock in /var/run to check if an
> upgrade job is running. After /var is unmounted, /var/run is no longer present

Hi,

I thought that by now all reference to /var/run could be replaced by simply 
"/run".

This would solve this problem.

Alexandre

Bug#854703: more details

[Antoine Beaupré]

FWIW, the log lines leading up to that crash are:

fév 08 21:36:14 curie pcscd[15485]: 00500819 winscard_svc.c:359:ContextThread() 
Received command: CMD_GET_READERS_STATE from client 14
fév 08 21:36:15 curie pcscd[15485]: 00152751 
hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
fév 08 21:36:15 curie pcscd[15485]: 0398 
hotplug_libudev.c:360:HPRemoveDevice() Removing USB device[0]: Yubico Yubikey 
NEO OTP+CCID at /dev/bus/usb/001/020
fév 08 21:36:15 curie pcscd[15485]: 0025 
readerfactory.c:608:RFRemoveReader() UnrefReader() count was: 1
fév 08 21:36:15 curie pcscd[15485]: 0013 
eventhandler.c:176:EHDestroyEventHandler() Stomping thread.
fév 08 21:36:15 curie pcscd[15485]: 0014 
ifdhandler.c:382:IFDHGetCapabilities() tag: 0xFB1, 
usb:1050/0111:libudev:1:/dev/bus/usb/001/020 (lun: 0)
fév 08 21:36:15 curie pcscd[15485]: 0010 
ifdhandler.c:382:IFDHGetCapabilities() tag: 0xFB2, 
usb:1050/0111:libudev:1:/dev/bus/usb/001/020 (lun: 0)
fév 08 21:36:15 curie pcscd[15485]: 0009 
eventhandler.c:201:EHDestroyEventHandler() Request stopping of polling thread
fév 08 21:36:15 curie pcscd[15485]: 0010 ifdhandler.c:347:IFDHStopPolling() 
usb:1050/0111:libudev:1:/dev/bus/usb/001/020 (lun: 0)
fév 08 21:36:15 curie pcscd[15485]: 00347689 winscard_svc.c:359:ContextThread() 
Received command: CMD_GET_READERS_STATE from client 14
fév 08 21:36:15 curie pcscd[15485]: 00047625 
eventhandler.c:502:EHStatusHandlerThread() Die
fév 08 21:36:15 curie pcscd[15485]: 0106 
eventhandler.c:216:EHDestroyEventHandler() Thread stomped.
fév 08 21:36:15 curie pcscd[15485]: 0013 
readerfactory.c:1130:RFUnInitializeReader() Attempting shutdown of Yubico 
Yubikey NEO OTP+CCID 00 00.
fév 08 21:36:15 curie pcscd[15485]: 0007 
ifdhandler.c:285:IFDHCloseChannel() 
usb:1050/0111:libudev:1:/dev/bus/usb/001/020 (lun: 0)
fév 08 21:36:15 curie pcscd[15485]: 0028 ccid_usb.c:797:WriteUSB() write 
failed (1/20): -4 LIBUSB_ERROR_NO_DEVICE
fév 08 21:36:15 curie pcscd[15485]: 0054 
ccid_usb.c:189:close_libusb_if_needed() libusb_exit
fév 08 21:36:15 curie pcscd[15485]: 0236 
readerfactory.c:991:RFUnloadReader() Unloading reader driver.
fév 08 21:36:15 curie pcscd[15485]: 0154 
hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
fév 08 21:36:15 curie pcscd[15485]: 00452517 winscard_svc.c:359:ContextThread() 
Received command: CMD_GET_READERS_STATE from client 14
fév 08 21:36:15 curie pcscd[15485]: 0406 winscard_svc.c:359:ContextThread() 
Received command: DISCONNECT from client 14
fév 08 21:36:15 curie pcscd[15485]: 0019 winscard_svc.c:544:ContextThread() 
DISCONNECT rv=0x80100011 for client 14
fév 08 21:36:15 curie pcscd[15485]: 0097 winscard_svc.c:359:ContextThread() 
Received command: RELEASE_CONTEXT from client 14
fév 08 21:36:15 curie pcscd[15485]: 0013 
winscard.c:226:SCardReleaseContext() Releasing Context: 0x1804DB5B
fév 08 21:36:15 curie pcscd[15485]: 0008 winscard_svc.c:470:ContextThread() 
RELEASE_CONTEXT rv=0x80100011 for client 14
fév 08 21:36:15 curie pcscd[15485]: 0062 winscard_svc.c:351:ContextThread() 
Client die: 14
fév 08 21:36:15 curie pcscd[15485]: 0018 
winscard.c:226:SCardReleaseContext() Releasing Context: 0x1804DB5B
fév 08 21:36:15 curie pcscd[15485]: 0010 
winscard_svc.c:1013:MSGCleanupClient() Thread is stopping: dwClientID=14, 
threadContext @0x5600a00ed690
fév 08 21:36:15 curie pcscd[15485]: 0007 
winscard_svc.c:1019:MSGCleanupClient() Freeing SCONTEXT @0x5600a00ed690
fév 08 21:36:15 curie pcscd[15485]: 0008 
winscard_svc.c:1034:MSGCleanupClient() Starting suicide alarm in 60 seconds
fév 08 21:37:15 curie pcscd[15485]: 6100 pcscdaemon.c:192:signal_thread() 
Received signal: 14
fév 08 21:37:15 curie pcscd[15485]: 0023 pcscdaemon.c:225:signal_thread() 
Preparing for suicide
fév 08 21:37:15 curie pcscd[15485]: 1280 
hotplug_libudev.c:710:HPStopHotPluggables() Hotplug stopped
fév 08 21:37:16 curie pcscd[15485]: 01000100 
readerfactory.c:1363:RFCleanupReaders() entering cleaning function
fév 08 21:37:16 curie pcscd[15485]: 0027 
winscard_svc.c:152:ContextsDeinitialize() remaining threads: 0
fév 08 21:37:16 curie pcscd[15485]: 0007 pcscdaemon.c:781:at_exit() 
cleaning /var/run/pcscd

A.

-- 
Il est sage de nous réconcilier avec notre adolescence ; haїr, mépriser,
nier ou simplement oublier l’adolescent que nous fûmes est en soi une
attitude adolescente.
- Daniel Pennac, Comme un roman

Bug#854616: [pkg-gnupg-maint] Bug#854616: scdaemon cannot access yubikey using ccid driver without pcscd

[Antoine Beaupré]

On 2017-02-09 06:38:18, NIIBE Yutaka wrote:
> Antoine Beaupré  writes:
>> This reminds me - it sure looks like pcscd was crashing back
>> there. Should I revert back to using pcscd to try and reproduce the
>> problem and file a pcscd bug about this?
>
> Yes.  I think that this is a different problem, and it's pcscd issue.

Okay then - I have reported this as a bug against the pcscd package
(#854703), hopefully it will get some traction there.

Do note that what is happening with pcscd is that it is exiting on its
own when I unplug the Yubikey:

fév 08 21:36:15 curie pcscd[15485]: 0008 
winscard_svc.c:1034:MSGCleanupClient() Starting suicide alarm in 60 seconds

Maybe pcscd expects to be reactivated through the systemd socket instead
of just running forever? Does scdaemon talk to the right socket
(/var/run/pcscd/pcscd.comm, according to the systemd config file)?

Thanks for any information,

A.

-- 
Si l'image donne l'illusion de savoir
C'est que l'adage pretend que pour croire,
L'important ne serait que de voir
- Lofofora

Bug#854703: disappears and never returns?

[Antoine Beaupre]

Package: pcscd
Version: 1.8.20-1
Severity: grave

Since I upgraded from 1.8.19-1 to 1.8.20-1 (or maybe it is because of
scdaemon 2.1.18, unclear), I cannot reliably use pcscd for multiple
days.

After a while, the pcscd daemon just disappears, and then scdaemon
cannot talk to it anymore:

fév 09 11:37:57 curie gpg-agent[23116]: scdaemon[32496] pcsc_establish_context 
failed: no service (0x8010001d) 

This was partly documented in #854005 (GnuPG bug) and #854616
(scdaemon bug) which both have workarounds, and I was able to finally
use my yubikey *without* pcscd. But I believe there is a
pcscd-specific bug here that makes it basically unusable (hence the
grave severity).

$ systemctl --system status pcscd
● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/etc/systemd/system/pcscd.service; indirect; vendor preset: 
enabled)
   Active: inactive (dead) since Wed 2017-02-08 21:37:16 EST; 14h ago
  Process: 15485 ExecStart=/usr/sbin/pcscd --foreground --auto-exit --debug 
(code=exited, status=0/SUCCESS)
 Main PID: 15485 (code=exited, status=0/SUCCESS)

As you may have noticed, I have modified the .service file to enable
debugging:

[Unit]
Description=PC/SC Smart Card Daemon
Requires=pcscd.socket

[Service]
ExecStart=/usr/sbin/pcscd --foreground --auto-exit --debug
ExecReload=/usr/sbin/pcscd --hotplug

[Install]
Also=pcscd.socket

After that, I  have noticed that pcscd gladly commits suicide:

fév 08 21:37:15 curie pcscd[15485]: 0023 pcscdaemon.c:225:signal_thread() 
Preparing for suicide

That time is about the time I stopped working last night. I unplugged
my Yubikey and went to bed.

The workaround is, obviously, to restart pcscd:

sudo systemctl restart pcscd

It is unclear to me why this regression happened. The systemd files
haven't changed since 2011, so presumably the use of --auto-exit is
normal. Maybe something changed in the --auto-exit algorithm? Looking
upstream, I can't find anything specific.

Maybe scdaemon doesn't talk to the right socket anymore, or that
socket activation is failing somehow?

Am I the only one seeing this behavior?

Thanks to scdaemon changes, I can now use my Yubikey *without* pcscd,
but that makes the package basically unusable for me... So I figured
this should be fixed for stretch.

Thanks for your attention.

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

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

Versions of packages pcscd depends on:
ii  init-system-helpers 1.47
ii  libc6   2.24-9
ii  libccid [pcsc-ifd-handler]  1.4.26-1
ii  libpcsclite11.8.20-1
ii  libudev1232-15
ii  lsb-base9.20161125

pcscd recommends no packages.

Versions of packages pcscd suggests:
ii  systemd  232-15

-- no debconf information

Processed: Adjust found/fixed as described in the bug report

[Debian Bug Tracking System]

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

> found 854688 3.2.2-2
Bug #854688 [bitlbee] bitlbee: The versions in stable/testing are vulnerable to 
CVE-2016-10189 and CVE-2016-10188
Marked as found in versions bitlbee/3.2.2-2.
> fixed 854688 3.5.1-1
Bug #854688 [bitlbee] bitlbee: The versions in stable/testing are vulnerable to 
CVE-2016-10189 and CVE-2016-10188
Marked as fixed in versions bitlbee/3.5.1-1.
> thanks
Stopping processing here.

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

Bug#809669: unattended-upgrades: files got created under /var/ mountpoint

[Louis Bouchard]

Hello,

For info, this also has the potential effect of blocking shutdown (see Ubuntu's
LP: #1654600 [1]) for details.

The unattended-upgrade-shutdown script uses a lock in /var/run to check if an
upgrade job is running. After /var is unmounted, /var/run is no longer present
and  apt_pkg.get_lock() return -1 which normally means that the lock cannot be
taken. In this case, -1 is caused by the fact that the /var/run path no longer
exists. The lock appears to be present, so unattended-upgrade-shutdown waits for
it to go away. The delay to timeout is 10 minutes so the shutdown may block for
10 minutes.

Thought it was worth mentionning.

Kind regards,

...Louis

[1] https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600
-- 
Louis Bouchard
Software engineer,
Ubuntu Developer / Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63  B9C4 8B3D 867C 823E 7A61

Bug#854701: python-asyncssh: FTBFS (failing tests)

[Santiago Vila]

Package: src:python-asyncssh
Version: 1.8.1-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.5/build/asyncssh
copying asyncssh/agent_win32.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/asyncssh
copying asyncssh/known_hosts.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/asyncssh

[... snipped ...]

==
ERROR: test_xauth_environment (tests.test_x11._TestX11)
Test getting Xauthority path from the environment
--
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/mock.py", line 1159, in patched
return func(*args, **keywargs)
  File "/<>/tests/util.py", line 59, in async_wrapper
return self.loop.run_until_complete(wrapped_func)
  File "/usr/lib/python3.5/asyncio/base_events.py", line 466, in 
run_until_complete
return future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
raise self._exception
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
  File "/<>/tests/test_x11.py", line 498, in test_xauth_environment
yield from self._check_x11()
  File "/<>/tests/test_x11.py", line 339, in _check_x11
proc = yield from _create_x11_process(conn, command, **kwargs)
  File "/<>/tests/test_x11.py", line 52, in _create_x11_process
x11_display=x11_display, **kwargs))
  File "/<>/asyncssh/misc.py", line 152, in __iter__
return (yield from self._coro)
  File "/<>/asyncssh/connection.py", line 2487, in create_process
**kwargs)
  File "/<>/asyncssh/connection.py", line 2408, in create_session
bool(self._agent_path)))
  File "/<>/asyncssh/channel.py", line 895, in create
'X11 forwarding request failed')
asyncssh.misc.ChannelOpenError: Channel Open Error: X11 forwarding request 
failed

--
Ran 638 tests in 268.661s

FAILED (errors=18, skipped=2)
Test failed: 
error: Test failed: 
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: 
python3.5 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13
debian/rules:15: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/python-asyncssh/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine.

If you could not reproduce this using sbuild on a single CPU virtual machine 
(as I did),
please do not downgrade or mark as unreproducible, I would then consider giving 
you access
to a virtual machine on which I can reproduce it so that you can as well.
(In such case, please contact me off-list for details).

Thanks.

Bug#854688: bitlbee: The versions in stable/testing are vulnerable to CVE-2016-10189 and CVE-2016-10188

[dequis]

Package: bitlbee
Version: 3.4.2-1.1
Severity: grave
Tags: upstream security patch fixed-upstream

Hi,

I'm opening this bug since #853282, which was just fixed by the
3.5.1-1 upload, seems to apply to sid only.

CVE-2016-10188 is "bitlbee-libpurple: Use after free when expiring
file transfer requests"

https://security-tracker.debian.org/tracker/CVE-2016-10188

CVE-2016-10189 is "Null pointer dereference with file transfer request
from unknown contacts"

https://security-tracker.debian.org/tracker/CVE-2016-10189

The current version in sid would fix both of these issues for stretch,
but it's blocked due to the freeze. I would like to request an unblock
for that particular case, if possible.

Thanks.

Bug#854659: marked as done (tcsh: fails to configure)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 13:34:18 +
with message-id 
and subject line Bug#854659: fixed in tcsh 6.20.00-7
has caused the Debian Bug report #854659,
regarding tcsh: fails to configure
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.)


-- 
854659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tcsh
Version: 6.20.00-6
Severity: serious

There was a problem when upgrading from 6.20.00-5 (sorry for the German):

,
| (Lese Datenbank ... 218742 Dateien und Verzeichnisse sind derzeit 
installiert.)
| Vorbereitung zum Entpacken von .../tcsh_6.20.00-6_i386.deb ...
| Entpacken von tcsh (6.20.00-6) über (6.20.00-5) ...
| /usr/bin/update-menus
| postrm called with unknown argument `upgrade'
| dpkg: Warnung: Unterprozess altes post-removal-Skript gab den Fehlerwert 1 
zurück
| dpkg: stattdessen wird Skript aus dem neuen Paket probiert ...
| /usr/sbin/remove-shell
| dpkg: ... sieht so aus, als hätte das geklappt.
| Vorbereitung zum Entpacken von .../debootstrap_1.0.88_all.deb ...
| Entpacken von debootstrap (1.0.88) über (1.0.87) ...
| Trigger für menu (2.1.47) werden verarbeitet ...
| tcsh (6.20.00-6) wird eingerichtet ...
| update-alternatives: Fehler: Alternativen-Pfad /bin/tcsh existiert nicht
| dpkg: Fehler beim Bearbeiten des Paketes tcsh (--configure):
|  Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 
zurück
`

The update-alternatives error happens because the postinst script is
trying to set up the alternative before creating the /bin/tcsh symlink,
AFAICS.


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)

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

Versions of packages tcsh depends on:
ii  libc6  2.24-9
ii  libtinfo5  6.0+20161126-1

tcsh recommends no packages.

tcsh suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tcsh
Source-Version: 6.20.00-7

We believe that the bug you reported is fixed in the latest version of
tcsh, 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 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Lange  (supplier of updated tcsh 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: Thu, 09 Feb 2017 13:07:47 +
Source: tcsh
Binary: tcsh
Architecture: source amd64
Version: 6.20.00-7
Distribution: unstable
Urgency: high
Maintainer: Thomas Lange 
Changed-By: Thomas Lange 
Description:
 tcsh   - TENEX C Shell, an enhanced version of Berkeley csh
Closes: 852117 854659
Changes:
 tcsh (6.20.00-7) unstable; urgency=high
 .
   * postrm: remove symlink, not executable, Closes: #852117
   * postinst: create symlink before calling update-alternatives,
 Closes: #854659
Checksums-Sha1:
 3b866fcc2f033067e30620ff79e37ad7d8633ddf 1844 tcsh_6.20.00-7.dsc
 7c928470930eb75d518e4cce2212b0fe9b21a401 23757 tcsh_6.20.00-7.diff.gz
 8b980a5e9308cbc6c2e2cf53cd8265931cb59fa9 538644 tcsh-dbgsym_6.20.00-7_amd64.deb
 7a016bd65681ff53d78f27d91cb429663a63d61c 4956 tcsh_6.20.00-7_amd64.buildinfo
 24d9cf7c6a7e9a0b1b97682528a3a33cfd87684c 470606 tcsh_6.20.00-7_amd64.deb
Checksums-Sha256:
 801ac1371af58c5c1e96958fe38ab1149d4bd53057528930ddec53b68e0313ec 1844 
tcsh_6.20.00-7.dsc
 1fb59305574e9adfcbc1ad16649dc679d737ca6c0571839c819e34a92949fc8b 23757 
tcsh_6.20.00-7.diff.gz
 bd197a875c13833db19913cc9f560c598a6317e8f3ec4308d0433891c76cf833 538644 
tcsh-dbgsym_6.20.00-7_amd64.deb
 d7f90b6e087354d097ec41be44e6a5334c311581b609886f003b684bf82c3c54 4956 
tcsh_6.20.00-7_amd64.buildinfo
 81136bcd80b8cb41d4b41cae0201cd5fc138c2cf73e531162e12ccee4cd86641 470606 
tcsh_6.20.00-7_amd64.deb
Files:
 95603856d771c0d435a3de0e5936fbfb 1844 shells optional tcsh_6.20.00-7.dsc
 3cb9097eac78c4599cf3275b15db308b 23757 shells 

Bug#853755: installation-reports: ppc64el fails to boot after installation

[Erwan Prioul]

I ran successful tests from [1] which includes the upstream commit from [2].

[1] 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=4de2441f351136a0f6f5b9797a77f9705879ccdf
[2] https://github.com/systemd/systemd/issues/5230

Erwan.



signature.asc
Description: OpenPGP digital signature

Bug#854548: marked as done (xrdp-sesman.service fails to start)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 12:35:19 +
with message-id 
and subject line Bug#854548: fixed in xrdp 0.9.1-5
has caused the Debian Bug report #854548,
regarding xrdp-sesman.service fails to start
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.)


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

Dear Maintainer,
the installation of xrdp fails sayng:
[...]
Created symlink /etc/systemd/system/multi-user.target.wants/xrdp-sesman.service
-> /lib/systemd/system/xrdp-sesman.service.
Created symlink /etc/systemd/system/multi-user.target.wants/xrdp.service ->
/lib/systemd/system/xrdp.service.
A dependency job for xrdp.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript xrdp, action "start" failed.
* xrdp.service - xrdp daemon
   Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset:
enabled)
   Active: inactive (dead)
 Docs: man:xrdp(8)
   man:xrdp.ini(5)

Feb 08 08:23:00 psala-lx2 systemd[1]: Dependency failed for xrdp daemon.
Feb 08 08:23:00 psala-lx2 systemd[1]: xrdp.service: Job xrdp.service/start
failed with result 'dependency'.
Feb 08 08:23:51 psala-lx2 systemd[1]: Dependency failed for xrdp daemon.
Feb 08 08:23:51 psala-lx2 systemd[1]: xrdp.service: Job xrdp.service/start
failed with result 'dependency'.
Feb 08 08:39:04 psala-lx2 systemd[1]: Dependency failed for xrdp daemon.
Feb 08 08:39:04 psala-lx2 systemd[1]: xrdp.service: Job xrdp.service/start
failed with result 'dependency'.
Feb 08 08:39:14 psala-lx2 systemd[1]: Dependency failed for xrdp daemon.
Feb 08 08:39:14 psala-lx2 systemd[1]: xrdp.service: Job xrdp.service/start
failed with result 'dependency'.
Feb 08 08:40:24 psala-lx2 systemd[1]: Dependency failed for xrdp daemon.
Feb 08 08:40:24 psala-lx2 systemd[1]: xrdp.service: Job xrdp.service/start
failed with result 'dependency'.
dpkg: error processing package xrdp (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (232-15) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up xorgxrdp (0.9.1-4) ...
Processing triggers for libc-bin (2.24-9) ...
Errors were encountered while processing:
 xrdp
E: Sub-process /usr/bin/dpkg returned an error code (1)

The dependency problem seems to be tied to xrdp-sesman.service that hangs on
starting:

$ systemctl status xrdp-sesman.service
● xrdp-sesman.service - xrdp session manager
   Loaded: loaded (/lib/systemd/system/xrdp-sesman.service; enabled; vendor
preset: enabled)
   Active: failed (Result: resources) since Wed 2017-02-08 08:50:29 CET; 1min
44s ago
 Docs: man:xrdp-sesman(8)
   man:sesman.ini(5)
  Process: 5850 ExecStart=/usr/sbin/xrdp-sesman $SESMAN_OPTIONS (code=exited,
status=0/SUCCESS)

$ sudo cat /var/log/xrdp-sesman.log
[20170208-08:40:24] [DEBUG] libscp initialized
[20170208-08:40:24] [ERROR] error opening pid file[/var/run/xrdp/xrdp-
sesman.pid]: No such file or directory
[20170208-08:40:24] [CORE ] shutting down log subsystem...
[20170208-08:50:29] [DEBUG] libscp initialized
[20170208-08:50:29] [ERROR] error opening pid file[/var/run/xrdp/xrdp-
sesman.pid]: No such file or directory
[20170208-08:50:29] [CORE ] shutting down log subsystem...




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

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
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 xrdp depends on:
ii  adduser  3.115
ii  init-system-helpers  1.47
ii  libc62.24-9
ii  libfuse2 2.9.7-1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libopus0 1.2~alpha2-1
ii  libpam0g 1.1.8-3.5
ii  libssl1.11.1.0c-2
ii  libx11-6 2:1.6.4-3
ii  libxfixes3   1:5.0.3-1
ii  libxrandr2   2:1.5.1-1
ii  lsb-base 9.20161125
ii  ssl-cert 1.0.38

Versions of packages xrdp recommends:
ii  fuse  2.9.7-1
ii  xorgxrdp  0.9.1-4

Versions of packages xrdp suggests:
pn  guacamole  

Versions of packages xorgxrdp depends on:
ii  libc6  2.24-9
pn  xorg-input-abi-24  
ii  xserver-xorg-core [xorg-video-abi-23]  2:1.19.1-4

Versions of packages xorgxrdp recommends:
ii  xorg  

Bug#852130: redmine: fails to install, *purge*, and install again - maybe an issue with dbconfig-common?

[Antonio Terceiro]

Hello dbconfig-common maintainer(s):

When re-installing redmine after having it purged, it seems that
dbconfig-common is not re-recreating the configuration file. When
debugging this, I tested both deleting and not deleting the database,
but always selecting "deconfigure database using dbconfig-common".

The original context if in the bug report here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852130

Could you maybe check if that is the case?


signature.asc
Description: PGP signature

Bug#854548: marked as pending

[Dominik George]

tag 854548 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-remote/xrdp.git;a=commitdiff;h=1d67bb8

---
commit 1d67bb891ccb3d27b99bf4fde1720135a1f464ce
Author: Dominik George 
Date:   Thu Feb 9 12:48:35 2017 +0100

Ensure creation of /run directory.

diff --git a/debian/changelog b/debian/changelog
index 1ddbfb1..f545629 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+xrdp (0.9.1-5) unstable; urgency=medium
+
+  * Ensure creation of /run directory. (Closes: #854548)
+
+ -- Dominik George   Thu, 09 Feb 2017 12:47:36 +0100
+
 xrdp (0.9.1-4) unstable; urgency=high
 
   [ Thorsten Glaser ]

Bug#854279: matplotlib: contains fonts without DFSG-compatible licensing

[Jonas Smedegaard]

Quoting Sandro Tosi (2017-02-09 02:10:57)
>> 0.82-1 seems to confirm [my] guess that the c*ttf [fonts] are BaKoMa 
>> and that they are restricted to non-commercial use: That release 
>> contains file fonts/BaKoMa-CM.Fonts with the following text:
>>
>>> The author of this fonts grants to any individual or non-commercial 
>>> organization the right to use and to make an unlimited number of 
>>> copies of full package or selected fonts when this is done WITHOUT 
>>> CHARGE and has attached this file with licence agreement.
>>>
>>> This fonts cannot be sold or distributed with any commercial product 
>>> or used in any commercial organization without additional agreement 
>>> with author. If you want to charge a small fee via distribution 
>>> these fonts or any derivations from this fonts, you should contact 
>>> the author.
>>>
>>> This restriction is also true for only outlines from this fonts. 
>>> i.e. outlines exported into other font formats, for example TrueType 
>>> or Type3.
>>>
>>> This restriction is not intended to apply to connect time charges, 
>>> or flat rate connection/download fees for electronic bulletin board 
>>> services.
>
> 0.82-1 is way old and cannot be used as reference.

Interesting logic.


> those fonts are the same as provided by fonts-lyx
> 
> $ ls -l /usr/share/fonts/truetype/lyx/c*ttf
> -rw-r--r-- 1 root root 20688 Jul  2  2016
> /usr/share/fonts/truetype/lyx/cmex10.ttf
> -rw-r--r-- 1 root root 32036 Jul  2  2016
> /usr/share/fonts/truetype/lyx/cmmi10.ttf
> -rw-r--r-- 1 root root 26188 Jul  2  2016
> /usr/share/fonts/truetype/lyx/cmr10.ttf
> -rw-r--r-- 1 root root 28476 Jul  2  2016
> /usr/share/fonts/truetype/lyx/cmsy10.ttf

Nice to know - but possibly not adequate for licensing needs.

Some (but not all) licenses are invalidated if not preserving the 
licensing verbatim: Debian is only permitted to redistribute the fonts 
via matplotlib if the license granted to matplotlib permitted removal of 
the license text.


> see also 
> https://github.com/matplotlib/matplotlib/issues/6976#issuecomment-270002766
> 
> i'll include that copyright notice as well

Bug opened upstream, referencing above: 
https://github.com/matplotlib/matplotlib/issues/8051


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: Bug#854548 marked as pending

[Debian Bug Tracking System]

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

> tag 854548 pending
Bug #854548 [xrdp] xrdp-sesman.service fails to start
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#744753: sleep script

[Tino Mettler]

Hi,

meanwhile, the hdparm package was updated to use the solution using a
sleep script.

Regards,
Tino

Bug#834910: marked as done (lasagne: two tests failing on Python 3.5)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 12:03:45 +
with message-id 
and subject line Bug#834910: fixed in lasagne 0.1+git20160728.8b66737-2
has caused the Debian Bug report #834910,
regarding lasagne: two tests failing on Python 3.5
to be marked as done.

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

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


-- 
834910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lasagne
Version: 0.1+git20160728.8b66737-1
Severity: normal

On Python 3.5, there are two failures in the tests:


=== FAILURES ===
 TestGetOutput_Layer.test_get_output_with_unused_kwarg _

self = 
layers = (, , )
get_output = 

def test_get_output_with_unused_kwarg(self, layers, get_output):
l1, l2, l3 = layers
unused_kwarg = object()
with warnings.catch_warnings(record=True) as w:
warnings.simplefilter('always')
get_output(l3, kwagg=unused_kwarg)
>   assert len(w) == 1
E   assert 3 == 1
E+  where 3 = len([, , 
])

lasagne/tests/layers/test_helper.py:237: AssertionError
___ TestGetOutput_Layer.test_get_output_with_no_unused_kwarg ___

self = 
layers = (, , )
get_output = 

def test_get_output_with_no_unused_kwarg(self, layers, get_output):
l1, l2, l3 = layers
with warnings.catch_warnings(record=True) as w:
warnings.simplefilter('always')
get_output(l3)
>   assert len(w) == 0
E   assert 2 == 0
E+  where 2 = len([, ])

lasagne/tests/layers/test_helper.py:246: AssertionError
= 2 failed, 687 passed, 302 skipped in 649.78 seconds ==
E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: python3.5 
-m pytest -v -rs lasagne/


DS

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



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: lasagne
Source-Version: 0.1+git20160728.8b66737-2

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

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

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

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated lasagne 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: Thu, 09 Feb 2017 12:25:30 +0100
Source: lasagne
Binary: python-lasagne python3-lasagne lasagne-doc
Architecture: source all
Version: 0.1+git20160728.8b66737-2
Distribution: unstable
Urgency: medium
Maintainer: Daniel Stender 
Changed-By: Daniel Stender 
Description:
 lasagne-doc - deep learning Python library build on the top of Theano (docs)
 python-lasagne - deep learning library build on the top of Theano (Python2 
modules
 python3-lasagne - deep learning library build on the top of Theano (Python3 
modules
Closes: 834910
Changes:
 lasagne (0.1+git20160728.8b66737-2) unstable; urgency=medium
 .
   * Use inspect.signature instead of inspect.getargspec if possible
 (Closes: #834910) [Ole Streicher].
Checksums-Sha1:
 7b4676c1c9d831cd88311f34cf30bec7df013c2b 2423 
lasagne_0.1+git20160728.8b66737-2.dsc
 2ab81ea2b8176b388ea79e99b264aa0e2fd9803d 129792 
lasagne_0.1+git20160728.8b66737.orig.tar.xz
 78204abcabcff2bfc39169370751890e664a2299 4636 
lasagne_0.1+git20160728.8b66737-2.debian.tar.xz
 8c8409d3b9faefdfac11deeff6d06a996f53 117610 
lasagne-doc_0.1+git20160728.8b66737-2_all.deb
 8a15b7a516e4daf4236780bcf972b1df353544ce 8096 
lasagne_0.1+git20160728.8b66737-2_amd64.buildinfo
 82ce336f834787c1feb566e56c9d799d966966ab 82120 
python-lasagne_0.1+git20160728.8b66737-2_all.deb
 07ae192f4d32677568ce1902c02fe944988ea8f7 82198 
python3-lasagne_0.1+git20160728.8b66737-2_all.deb
Checksums-Sha256:
 eb3f2f16c6bb98ecc9a1e436d386a0982e08c1e46a46f6b43c68b0d2f6f6f820 2423 
lasagne_0.1+git20160728.8b66737-2.dsc
 a4884105e7e092795f8194a449dc5ab08a32080a995085d3c954c0b85f01f92b 129792 
lasagne_0.1+git20160728.8b66737.orig.tar.xz
 

Bug#744753: sleep script

[Tino Mettler]

Hi,

meanwhile, the hdparm package was updated to use the solution using a
sleep script.

Regards,
Tino

Bug#852130: redmine: fails to install, *purge*, and install again

[Antonio Terceiro]

Control: retitle -1 redmine: fails to install, purge and install again

On Sat, Feb 04, 2017 at 11:12:44AM +0100, Gilles Filippini wrote:
> Hi,
> 
> On Sun, 22 Jan 2017 14:29:27 -0200 Antonio Terceiro  
> wrote:
> > On Sat, Jan 21, 2017 at 08:46:22PM +0100, Andreas Beckmann wrote:
> > > Package: redmine
> > > Version: 3.3.1-2
> > > Severity: serious
> > > User: debian...@lists.debian.org
> > > Usertags: piuparts
> > > 
> > > Hi,
> > > 
> > > during a test with piuparts I noticed your package failed to install,
> > > remove (but not purge), and install again.
> > > Before the second installation the package is in config-files-remaining
> > > state. The configuration is remaining from the last version that was
> > > successfully configured - which is the same version that is going to be
> > > installed again.
> > 
> > Hi,
> > 
> > First of all thanks for your work on piuparts.
> > 
> > However, I am not able to reproduce this without piuparts. I tried
> > install/remove/install by hand on a clean chroot twice, and even
> > automating it with a script like this:
> > 
> > export DEBIAN_FRONTEND=noninteractive
> > apt-get install -qy redmine
> > apt-get remove -qy redmine
> > apt-get install -qy redmine
> 
> I can reproduce a similar error without piuparts using the following sequence 
> in a clean sid chroot:
> # export DEBIAN_FRONTEND=noninteractive
> # apt-get install -y redmine
> ...
> # apt-get remove --purge -y redmine
> ...
> # apt-get install -y redmine

So this means that the original submission was misleading.

The piuparts log posted in the bug report says piuparts was called with
--install-purge-install, while the bug report itself says "remove (but
purge)".  So the bug is that redmine fails to install after being
*purged*, not just being removed.


signature.asc
Description: PGP signature

Processed: Re: Bug#852130: redmine: fails to install, *purge*, and install again

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 redmine: fails to install, purge and install again
Bug #852130 [redmine] redmine: fails to install, remove, and install again
Changed Bug title to 'redmine: fails to install, purge and install again' from 
'redmine: fails to install, remove, and install again'.

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

Bug#854487: marked as done (puppet: puppet agent service enabled and running by default)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 11:03:51 +
with message-id 
and subject line Bug#854487: fixed in puppet 4.8.2-2
has caused the Debian Bug report #854487,
regarding puppet: puppet agent service enabled and running by default
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.)


-- 
854487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puppet
Severity: critical
Tags: security
Justification: Potentially opens up a new security hole

Hi!

In the old days, users wanting the puppet binaries but not the puppet
daemon would install the puppet-common but not the puppet package [0].
This changed when puppet 4.5 was uploaded to Debian, now the puppet
package contained the binaries and the puppet-agent package contained
the service [1]. This transition was done properly, as the new service
packages would not be installed by default.

However, now somebody decided, that it's a good idea to drop the
puppet-agent package and move the service file back to the puppet
package [1]. This is bad, very, very bad. Here's why:

   1. As of today, there is no apparently no package shipping only the
  binaries but not the service files.
   2. I have quite a few systems where I occasionally run puppet manually,
  but which should never run puppet automatically.
   3. Those systems began to look for a puppet master at the default
  server address "puppet" recently as the new package version got
  installed.
   4. As a result, anybody with control over DNS could have responded and
  potentially taken over those systems.

Please understand that your change made my and potentially other
people's system vulnerable without even telling them about it. I urge
you strongly to revert this change!

Best regards

Alexander Kurtz

[0] https://packages.debian.org/source/jessie/puppet
[1] https://tracker.debian.org/news/771535
[2] https://tracker.debian.org/news/833773

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: puppet
Source-Version: 4.8.2-2

We believe that the bug you reported is fixed in the latest version of
puppet, 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 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated puppet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Feb 2017 15:24:55 +0200
Source: puppet
Binary: puppet puppet-master puppetmaster puppet-master-passenger 
puppetmaster-passenger puppet-common
Architecture: source all
Version: 4.8.2-2
Distribution: unstable
Urgency: high
Maintainer: Puppet Package Maintainers 

Changed-By: Apollon Oikonomopoulos 
Description:
 puppet - configuration management system
 puppet-common - transitional dummy package
 puppet-master - configuration management system, master service
 puppet-master-passenger - configuration management system, scalable master 
service
 puppetmaster - configuration management system, master service - transitional 
pa
 puppetmaster-passenger - configuration management system, scalable master 
service - transi
Closes: 854487
Changes:
 puppet (4.8.2-2) unstable; urgency=high
 .
   * Do not enable the puppet service by default on fresh installs
 (Closes: #854487).
 + Preserve the agent lock on upgrade from 3.x to safeguard upgrades from
   Jessie systems where puppet was installed but never used.
   * Update the DEP-8 tests to check that the service is disabled.
   * Strip the agent locking logic from puppet.preinst now that we disable the
 service by default.
   * Add a debian/NEWS entry documenting the disabled service.
   * Update the information in README.Debian and remove the (now obsolete)
 paragraph about stored configs.
Checksums-Sha1:
 6e9a9fddba21106e0fe27435a533c0a9c45c1dfe 2495 puppet_4.8.2-2.dsc
 2f9ddc5454a5d8e6d2678073396cdcfeb4992f95 32844 puppet_4.8.2-2.debian.tar.xz
 

Bug#854463: marked as done (FTBFS without user input with a controlling TTY)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 10:33:40 +
with message-id 
and subject line Bug#854463: fixed in kodi 2:17.0+dfsg1-2
has caused the Debian Bug report #854463,
regarding FTBFS without user input with a controlling TTY
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.)


-- 
854463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kodi
Version: 2:17.0~rc3+dfsg1-2
Severity: serious

In a freshly-unpacked source directory, dpkg-buildpackage (or pdebuild,
or sbuild) blocks in the clean target trying to reverse some patches,
because they were never applied (they get applied during configure) and
patch prompts the user for input. The user needs to answer 44 questions
before the clean target actually finishes:

> ls /«BUILDDIR»/kodi-17.0~rc3+dfsg1/debian/patches/libdvdnav-* | tac | xargs 
> cat
> ls /«BUILDDIR»/kodi-17.0~rc3+dfsg1/debian/patches/libdvdnav-* | tac | xargs 
> cat | patch -R --no-backup-if-mismatch -r - -s -p1 \
>   -d libdvdnav-5-0-3 || true
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 2 out of 2 hunks ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> ls /«BUILDDIR»/kodi-17.0~rc3+dfsg1/debian/patches/libdvdread-* | tac | xargs 
> cat | patch -R --no-backup-if-mismatch -r - -s -p1 \
>   -d libdvdread-5-0-3 || true
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 2 out of 2 hunks ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 5 out of 5 hunks ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 2 out of 2 hunks ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
> Unreversed patch detected!  Ignore -R? [n] 
> Apply anyway? [n] 
> 1 out of 1 hunk ignored
--- End Message ---
--- Begin Message ---
Source: kodi
Source-Version: 2:17.0+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
kodi, 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 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated kodi 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: Thu, 09 Feb 2017 10:25:18 +0100
Source: kodi
Binary: kodi kodi-data kodi-bin kodi-eventclients-common kodi-eventclients-dev 
kodi-eventclients-wiiremote kodi-eventclients-ps3 kodi-eventclients-kodi-send 
kodi-addons-dev xbmc xbmc-bin xbmc-eventclients-common xbmc-eventclients-dev 
xbmc-eventclients-wiiremote xbmc-eventclients-ps3 xbmc-eventclients-xbmc-send 
xbmc-addons-dev
Architecture: source

Bug#848820: Random failures in test suite of snakemake [Bug#848820: snakemake: FTBFS randomly (failing tests)]

[Johannes Köster]

Thanks and sorry for the slow reply. I have finally seen the error myself. I 
think it should be fixed in commit d697f23.

Best,
Johannes



---
Dr. rer. nat. Johannes Köster
Centrum Wiskunde & Informatica
Harvard Medical School
http://johanneskoester.bitbucket.org



 Original Message 
Subject: Random failures in test suite of snakemake [Bug#848820: snakemake: 
FTBFS randomly (failing tests)]
Local Time: December 22, 2016 9:46 AM
UTC Time: December 22, 2016 8:46 AM
From: andr...@an3as.eu
To: Johannes Köster , Kevin Murray 

848...@bugs.debian.org

Hi Johannes,

the Debian Med team is packaging snakemake for Debian (thanks for this
nice tool by the way). We received a bug report that one test of the
unit test suite fails randomly (3 times out of 100 tries). The essence
of the provided build logs which are linked at the bug page[1] is the
follwing:

==
ERROR: tests.tests.test_symlink_temp
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/nose/case.py", line 198, in runTest
self.test(*self.arg)
File 
"/<>/snakemake-3.9.0+dfsg/.pybuild/pythonX.Y_3.5/build/tests/tests.py",
 line 301, in test_symlink_temp
run(dpath("test_symlink_temp"), shouldfail=True)
File 
"/<>/snakemake-3.9.0+dfsg/.pybuild/pythonX.Y_3.5/build/tests/tests.py",
 line 105, in run
rmtree(tmpdir)
File "/usr/lib/python3.5/shutil.py", line 478, in rmtree
onerror(os.rmdir, path, sys.exc_info())
File "/usr/lib/python3.5/shutil.py", line 476, in rmtree
os.rmdir(path)
OSError: [Errno 39] Directory not empty: 
'/<>/snakemake-3.9.0+dfsg/.pybuild/pythonX.Y_3.5/build/.test0k8le5n3'


but you might like to inspect the complete log at your preference.

My current course of action will be to simply disable this test for
the moment.

Kind regards

Andreas.


[1] https://bugs.debian.org/848820

- Forwarded message from Santiago Vila  -

Date: Mon, 19 Dec 2016 23:46:36 +0100 (CET)
From: Santiago Vila 
To: Debian BTS 
Subject: Bug#848820: snakemake: FTBFS randomly (failing tests)
X-Debian-PR-Message: report 848820
X-Debian-PR-Package: src:snakemake
X-Debian-PR-Keywords:
X-Debian-PR-Source: snakemake

Package: src:snakemake
Version: 3.9.0+dfsg-1
Severity: serious

Dear maintainer:

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


[...]
debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem=pybuild
dh_testdir -i -O--buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py config
running config
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/snakemake-3.9.0+dfsg'
dh_auto_build
I: pybuild base:184: /usr/bin/python3 setup.py build
running build

[... snipped ...]

2 four
2 one
2 three
2 two
9
snakemake.logging: INFO: rule one:
input: a
output: 1.a
wildcards: sample=a
snakemake.logging: INFO:
snakemake.logging: INFO: rule one:
input: b
output: 1.b
wildcards: sample=b
snakemake.logging: INFO:
snakemake.logging: INFO: 1 of 9 steps (11%) done
snakemake.logging: INFO: rule two:
input: 1.a
output: 2.a
wildcards: sample=a
snakemake.logging: INFO:
snakemake.logging: INFO: 2 of 9 steps (22%) done
snakemake.logging: INFO: rule two:
input: 1.b
output: 2.b
wildcards: sample=b
snakemake.logging: INFO:
snakemake.logging: WARNING: Removing temporary output file 1.a.
snakemake.logging: INFO: 3 of 9 steps (33%) done
snakemake.logging: ERROR: WorkflowError:
File 2.a seems to be a broken symlink.
snakemake.logging: WARNING: Waiting at most 3 seconds for missing files.
- >> end captured logging << -

--
Ran 70 tests in 36.186s

FAILED (errors=1)
Error in job two while creating output file 2.b.
MissingOutputException in line 9 of 
/<>/snakemake-3.9.0+dfsg/.pybuild/pythonX.Y_3.5/build/tests/test_symlink_temp/Snakefile:
Missing files after 3 seconds:
2.b
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/<>/snakemake-3.9.0+dfsg/.pybuild/pythonX.Y_3.5/build; python3.5 -m 
nose tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.5 returned 
exit code 13
debian/rules:16: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends. I attach three different build logs.

They happened while trying to 

Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

[Martin Haaß]

Same behavior happens here.
Is it possible that multiple search domain entries in the dhcp packet 
trigger this problem? So instead of one entry being written twice it is 
two entries being concatenated without a newline and an additional 
'search' keyword at the start of the line.


Following is a wireshark trace of our DHCP ACK. There are two search 
domain entries (Option 3) due to two name server entries.

Cheers,
 Martin
 snip 
Bootstrap Protocol (ACK)
Message type: Boot Reply (2)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0x34e7e163
Seconds elapsed: 0
Bootp flags: 0x (Unicast)
Client IP address: 0.0.0.0
Your (client) IP address: 192.168.0.43
Next server IP address: 10.49.24.25
Relay agent IP address: 0.0.0.0
Client MAC address: Dell_50:03:a7
Client hardware address padding: 
Server host name not given
Boot file name: netboot/lpxelinux.0
Magic cookie: DHCP
Option: (53) DHCP Message Type (ACK)
Option: (58) Renewal Time Value
Option: (59) Rebinding Time Value
Option: (51) IP Address Lease Time
Option: (54) DHCP Server Identifier
Option: (1) Subnet Mask
Option: (28) Broadcast Address
Option: (3) Router
Length: 4
Router: 192.168.0.6
Option: (15) Domain Name
Length: 11
Domain Name: company.local
Option: (6) Domain Name Server
Option: (28) Broadcast Address
Option: (3) Router
Length: 4
Router: 192.168.0.6
Option: (15) Domain Name
Length: 11
Domain Name: company.local
Option: (6) Domain Name Server
Option: (44) NetBIOS over TCP/IP Name Server
Option: (42) Network Time Protocol Servers
Option: (252) Private/Proxy autodiscovery
Option: (255) End
-- snap -

Bug#850229: openmpi-bin: default for oversubscription changed

[Santiago Vila]

On Thu, Feb 09, 2017 at 09:28:45AM +0100, Ansgar Burchardt wrote:
> On Thu, 2017-02-09 at 00:05 +0100, Santiago Vila wrote:
> > In either case I'm setting this to serious again because it makes
> > packages to fail on single-CPU systems, and having more than one CPU
> > is
> > definitely *not* part of the build-essential definition.
> 
> It is not, but trying to build packages below a path that includes
> whitespace or shell metacharacters is also not forbidden by the build-
> essential definition.  Or on strange filesystems not fully following
> POSIX semantics.
> 
> I think all of these are however uncommon configurations these days and
> wouldn't treat either as serious in my packages.

You are absolutely right about those two things (white space, and lack
of POSIX semantics) being uncommon, but I think they are very different
from building with only one CPU.

The non POSIX filesystem is something I already do, because I use
overlayfs by default, and the overlayfs support in the kernel is still
not perfect. When I find a package which does not build with overlayfs,
I report it as a normal bug or even wishlist, it is not a real FTBFS
bug.

Thw white space thing is not something particularly useful, because
you can avoid it at no cost (by not using spaces in the paths).

On the other side, building with more than one CPU usually cost you
twice the price. See

https://www.linode.com/pricing

for example, so it is something definitely useful, not comparable
with building in a path which includes spaces.

(For the record, I am paying for some of my autobuilders directly from my 
pocket)

Thanks.

Bug#854314: marked as done (youtube-dl: 'Signature extraction failed' on some YouTube videos)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 08:49:22 +
with message-id 
and subject line Bug#854314: fixed in youtube-dl 2017.02.07-1
has caused the Debian Bug report #854314,
regarding youtube-dl: 'Signature extraction failed' on some YouTube videos
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.)


-- 
854314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: youtube-dl
Version: 2016.12.01-1
Severity: normal

Dear Maintainer,

Today, in attempting to download videos from YouTube with youtube-dl, I
have seen some download normally and others produce errors.
(Unfortunately, this happened late enough that the release-freeze
announcement came in while I was testing it.)

Specifically, I have seen the following:

$ youtube-dl https://www.youtube.com/watch?v=4pbMUEHvoAo --verbose
[debug] System config: []
[debug] User config: ['-f', 'best']
[debug] Command-line args:
['https://www.youtube.com/watch?v=4pbMUEHvoAo', '--verbose']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.12.01
[debug] Python version 3.5.3 - Linux-4.8.0-2-amd64-x86_64-with-debian-9.0
[debug] exe versions: rtmpdump 2.4
[debug] Proxy map: {}
[youtube] 4pbMUEHvoAo: Downloading webpage
[youtube] 4pbMUEHvoAo: Downloading video info webpage
[youtube] 4pbMUEHvoAo: Extracting video information
[youtube] {43} signature length 42.43, html5 player en_US-vflkk7pUE
[youtube] 4pbMUEHvoAo: Downloading player
/yts/jsbin/player-en_US-vflkk7pUE/base.js
ERROR: Signature extraction failed: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py",
line 1005, in _decrypt_signature
video_id, player_url, s
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py",
line 919, in _extract_signature_function
errnote='Download of %s failed' % player_url)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py",
line 517, in _download_webpage
res = self._download_webpage_handle(url_or_request, video_id, note,
errnote, fatal, encoding=encoding, data=data, headers=headers, query=query)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py",
line 424, in _download_webpage_handle
urlh = self._request_webpage(url_or_request, video_id, note,
errnote, fatal, data=data, headers=headers, query=query)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py",
line 404, in _request_webpage
return self._downloader.urlopen(url_or_request)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
2000, in urlopen
req = sanitized_Request(req)
  File "/usr/lib/python3/dist-packages/youtube_dl/utils.py", line 513,
in sanitized_Request
return compat_urllib_request.Request(sanitize_url(url), *args, **kwargs)
  File "/usr/lib/python3.5/urllib/request.py", line 269, in __init__
self.full_url = url
  File "/usr/lib/python3.5/urllib/request.py", line 295, in full_url
self._parse()
  File "/usr/lib/python3.5/urllib/request.py", line 324, in _parse
raise ValueError("unknown url type: %r" % self.full_url)
ValueError: unknown url type: '/yts/jsbin/player-en_US-vflkk7pUE/base.js'
 (caused by ValueError("unknown url type:
'/yts/jsbin/player-en_US-vflkk7pUE/base.js'",)); please report this
issue on https://yt-dl.org/bug . Make sure you are using the latest
version; see  https://yt-dl.org/update  on how to update. Be sure to
call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py",
line 1005, in _decrypt_signature
video_id, player_url, s
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py",
line 919, in _extract_signature_function
errnote='Download of %s failed' % player_url)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py",
line 517, in _download_webpage
res = self._download_webpage_handle(url_or_request, video_id, note,
errnote, fatal, encoding=encoding, data=data, headers=headers, query=query)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py",
line 424, in _download_webpage_handle
urlh = self._request_webpage(url_or_request, video_id, note,
errnote, fatal, data=data, headers=headers, query=query)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py",
line 404, in _request_webpage
return self._downloader.urlopen(url_or_request)
  File 

Bug#850229: openmpi-bin: default for oversubscription changed

[Ansgar Burchardt]

On Thu, 2017-02-09 at 00:05 +0100, Santiago Vila wrote:
> In either case I'm setting this to serious again because it makes
> packages to fail on single-CPU systems, and having more than one CPU
> is
> definitely *not* part of the build-essential definition.

It is not, but trying to build packages below a path that includes
whitespace or shell metacharacters is also not forbidden by the build-
essential definition.  Or on strange filesystems not fully following
POSIX semantics.

I think all of these are however uncommon configurations these days and
wouldn't treat either as serious in my packages.

Ansgar

Bug#854659: tcsh: fails to configure

[Sven Joachim]

Control: found -1 6.20.00-5

On 2017-02-09 07:38 +0100, Sven Joachim wrote:

> Package: tcsh
> Version: 6.20.00-6
> Severity: serious
>
> There was a problem when upgrading from 6.20.00-5 (sorry for the German):
>
> ,
> | (Lese Datenbank ... 218742 Dateien und Verzeichnisse sind derzeit 
> installiert.)
> | Vorbereitung zum Entpacken von .../tcsh_6.20.00-6_i386.deb ...
> | Entpacken von tcsh (6.20.00-6) über (6.20.00-5) ...
> | /usr/bin/update-menus
> | postrm called with unknown argument `upgrade'
> | dpkg: Warnung: Unterprozess altes post-removal-Skript gab den Fehlerwert 1 
> zurück
> | dpkg: stattdessen wird Skript aus dem neuen Paket probiert ...
> | /usr/sbin/remove-shell
> | dpkg: ... sieht so aus, als hätte das geklappt.
> | Vorbereitung zum Entpacken von .../debootstrap_1.0.88_all.deb ...
> | Entpacken von debootstrap (1.0.88) über (1.0.87) ...
> | Trigger für menu (2.1.47) werden verarbeitet ...
> | tcsh (6.20.00-6) wird eingerichtet ...
> | update-alternatives: Fehler: Alternativen-Pfad /bin/tcsh existiert nicht
> | dpkg: Fehler beim Bearbeiten des Paketes tcsh (--configure):
> |  Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 
> zurück
> `
>
> The update-alternatives error happens because the postinst script is
> trying to set up the alternative before creating the /bin/tcsh symlink,
> AFAICS.

Sorry, this statement is of course wrong, /usr/bin/tcsh is a symlink to
/bin/tcsh rather than the other way around.  The real problem is that
the postrm script removes /bin/tcsh rather than the /usr/bin/tcsh
symlink.

Cheers,
   Sven

Processed: Re: Bug#854659: tcsh: fails to configure

[Debian Bug Tracking System]

Processing control commands:

> found -1 6.20.00-5
Bug #854659 [tcsh] tcsh: fails to configure
Marked as found in versions tcsh/6.20.00-5.

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

Bug#854659: tcsh: fails to configure

[Thomas Lange]

> There was a problem when upgrading from 6.20.00-5 (sorry for the German):
This is a problem in the postrm of 6.20.00-4 which is fixed in
6.20.00-5. Since I cannot fix 6.20.00-4, you should just ignore this.

-- 
regards Thomas

Bug#853282: marked as done (bitlbee: Incomplete fix for "Null pointer dereference with file transfer request from unknown contacts" issue)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 08:00:10 +
with message-id 
and subject line Bug#853282: fixed in bitlbee 3.5.1-1
has caused the Debian Bug report #853282,
regarding bitlbee: Incomplete fix for "Null pointer dereference with file 
transfer request from unknown contacts" issue
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.)


-- 
853282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bitlbee
Version: --src
Severity: important
Tags: upstream security patch

Hi

The fix applied for upstream bug https://bugs.bitlbee.org/ticket/1282
was incomplete and resulted in the followup:

https://github.com/bitlbee/bitlbee/commit/30d598ce7cd3f136ee9d7097f39fa9818a272441

Details in: http://www.openwall.com/lists/oss-security/2017/01/30/4
(which will probably result in three CVEs for bitlbee, I will update
the security tracker once assigned).

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bitlbee
Source-Version: 3.5.1-1

We believe that the bug you reported is fixed in the latest version of
bitlbee, 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 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Wilmer van der Gaast  (supplier of updated bitlbee 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: Thu, 09 Feb 2017 00:46:53 +
Source: bitlbee
Binary: bitlbee bitlbee-libpurple bitlbee-common bitlbee-dev bitlbee-plugin-otr 
bitlbee-plugin-skype skyped
Architecture: source all amd64
Version: 3.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Wilmer van der Gaast 
Changed-By: Wilmer van der Gaast 
Description:
 bitlbee- IRC to other chat networks gateway (default version)
 bitlbee-common - IRC to other chat networks gateway (common files/docs)
 bitlbee-dev - IRC to other chat networks gateway (dev files)
 bitlbee-libpurple - IRC to other chat networks gateway (using libpurple)
 bitlbee-plugin-otr - IRC to other chat networks gateway (OTR plugin)
 bitlbee-plugin-skype - IRC to other chat networks gateway (Skype plugin)
 skyped - Daemon to control Skype remotely
Closes: 853282
Changes:
 bitlbee (3.5.1-1) unstable; urgency=medium
 .
   * Crash bug fix. (Closes: #853282)
Checksums-Sha1:
 21e8232bb148e047661f7f0ce3235bb48eb9e340 2350 bitlbee_3.5.1-1.dsc
 de0767facdb7729253ae4d6ef6e3637ebd54939a 680351 bitlbee_3.5.1.orig.tar.gz
 cc7534854681ac6eaa15df6b844bfb206e6deb81 15261 bitlbee_3.5.1-1.diff.gz
 94109af731348222c14dc6dbab71645fe257ebe8 78310 bitlbee-common_3.5.1-1_all.deb
 5bed2f5993b5b209b5ba90bc1816cd65c320e318 930732 
bitlbee-dbgsym_3.5.1-1_amd64.deb
 2f521d091e28f91c543dcd35c54e77dcfa81c585 29690 bitlbee-dev_3.5.1-1_all.deb
 200945819af8b52d1d6af358974e7517ae128b06 548430 
bitlbee-libpurple-dbgsym_3.5.1-1_amd64.deb
 c9b6b654acfd5b36d31d1e2a819daf0a54cc63c8 130394 
bitlbee-libpurple_3.5.1-1_amd64.deb
 16de1a38b797af32d48614306d2f3bc70ffe33af 41584 
bitlbee-plugin-otr-dbgsym_3.5.1-1_amd64.deb
 f5d0f7a4a59931fc2a97078869fe5abc2e0cdfe5 17356 
bitlbee-plugin-otr_3.5.1-1_amd64.deb
 0a6216c00bf90f88b2e215657b4818f7c740419b 16795 bitlbee_3.5.1-1_amd64.buildinfo
 5aa829f56a775eae20c5623a8bc6cf5efd9d3535 209246 bitlbee_3.5.1-1_amd64.deb
Checksums-Sha256:
 1508b5699d400ea660e1dd4d81c8afbd91a130a5486dbb7402540315edc98b1d 2350 
bitlbee_3.5.1-1.dsc
 9636d7fd89ebb3756c13a9a3387736ca6d56ccf66ec0580d512f07b21db0fa69 680351 
bitlbee_3.5.1.orig.tar.gz
 a6fe572b6bcf4bd477368689e3134cedd53fe587670ce02881d94aca246d27b8 15261 
bitlbee_3.5.1-1.diff.gz
 e02aa589f2196221f29c2073aebd6b2a24a4c3069bd83ce0dc68e7f0d29b650f 78310 
bitlbee-common_3.5.1-1_all.deb
 a3909c3384d0dd196860d5d22939c95b144694479919140545340e3ee90acc0b 930732 
bitlbee-dbgsym_3.5.1-1_amd64.deb
 f5546224db84511928c5f5701a72719d148e5bc89b00369a14cea03ad2403e8f 29690 
bitlbee-dev_3.5.1-1_all.deb
 801428ec053862d43aa93ddf29f3d1ff3ffcd428a235141fd0d2bd9fb648faf8 548430 
bitlbee-libpurple-dbgsym_3.5.1-1_amd64.deb
 e94bf9514bb0b55923c911da93f22216fd3d1bd66f686d16bfbfec3ab5eb92f9