Debian Bug report logs - #694963
upstart: Upstart can´t handle auto entry in network/interfaces

version graph

Package: upstart; Maintainer for upstart is Steve Langasek <vorlon@debian.org>; Source for upstart is src:upstart (PTS, buildd, popcon).

Reported by: Peschae <peschae@yahoo.com>

Date: Sun, 2 Dec 2012 18:30:09 UTC

Severity: important

Tags: moreinfo, unreproducible

Found in version upstart/1.6-2

Fixed in version 1.11-5+rm

Done: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to debian-bugs-dist@lists.debian.org, peschae@yahoo.com, Steve Langasek <vorlon@debian.org>:
Bug#694963; Package upstart. (Sun, 02 Dec 2012 18:30:11 GMT) (full text, mbox, link).

Acknowledgement sent to Peschae <peschae@yahoo.com>:
New Bug report received and forwarded. Copy sent to peschae@yahoo.com, Steve Langasek <vorlon@debian.org>. (Sun, 02 Dec 2012 18:30:11 GMT) (full text, mbox, link).

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Peschae <peschae@yahoo.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: upstart: Upstart can´t handle auto entry in network/interfaces
Date: Sun, 02 Dec 2012 19:30:11 +0100
Package: upstart
Version: 1.6-2
Severity: important
Tags: d-is 

Dear Maintainer,
upstart can´t handle auto entry in /etc/network/interfaces. With this entry, it waits long time for the network to start 
without success.
allow-hotplug wlan0 is not an optin on every computer. At least this one here (Asus notebook P53E) brings up the wlan0 only 
with the auto option, not with allow-hotplug.

auto wlan0
iface wlan0 inet dhcp

My workaround: I deleted the entries and use the network-manager instead.


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4.4 (SMP w/4 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages upstart depends on:
ii  ifupdown        0.7.5
ii  initscripts     2.88dsf-34
ii  libc6           2.13-37
ii  libdbus-1-3     1.6.8-1
ii  libjson0        0.10-1.1
ii  libnih-dbus1    1.0.3-4
ii  libnih1         1.0.3-4
ii  libselinux1     2.1.9-5
ii  libudev0        175-7.1
ii  mountall        2.45
ii  sysv-rc         2.88dsf-34
ii  sysvinit-utils  2.88dsf-34
ii  udev            175-7.1

upstart recommends no packages.

Versions of packages upstart suggests:
pn  bash-completion  <none>
pn  graphviz         <none>
ii  python           2.7.3~rc2-1

-- no debconf information

Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#694963; Package upstart. (Sun, 02 Dec 2012 18:45:05 GMT) (full text, mbox, link).

Acknowledgement sent to Steve Langasek <vorlon@debian.org>:
Extra info received and forwarded to list. (Sun, 02 Dec 2012 18:45:05 GMT) (full text, mbox, link).

Message #10 received at 694963@bugs.debian.org (full text, mbox, reply):

From: Steve Langasek <vorlon@debian.org>
To: Peschae <peschae@yahoo.com>, 694963@bugs.debian.org
Subject: Re: Bug#694963: upstart: Upstart can´t handle auto entry in network/interfaces
Date: Sun, 2 Dec 2012 10:43:27 -0800
[Message part 1 (text/plain, inline)]
tags 694963 = moreinfo unreproducible
thanks

Hi there,

On Sun, Dec 02, 2012 at 07:30:11PM +0100, Peschae wrote:
> upstart can´t handle auto entry in /etc/network/interfaces. With this
> entry, it waits long time for the network to start without success. 
> allow-hotplug wlan0 is not an optin on every computer.  At least this one
> here (Asus notebook P53E) brings up the wlan0 only with the auto option,
> not with allow-hotplug.

> auto wlan0
> iface wlan0 inet dhcp

I'm afraid this report doesn't make any sense to me.  Currently, the
/etc/init/network-interface.conf job (which is part of the ifupdown package)
calls ifup *only* for 'auto' interfaces:

  exec ifup --allow auto $INTERFACE

It does *not* handle interfaces that are marked 'allow-hotplug', which I
know is an issue given the default /etc/network/interfaces as set up by the
installer, but that does not appear to be the issue you're reporting.  You
seem to be saying that the network is not started when using 'auto'.  Can
you please clarify?  Can you also attach the /etc/network/interfaces file
that you see problems with, and post the output of the command 'initctl list
| grep network-interface'?

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

[signature.asc (application/pgp-signature, inline)]

Added tag(s) unreproducible and moreinfo. Request was from Steve Langasek <vorlon@debian.org> to control@bugs.debian.org. (Sun, 02 Dec 2012 18:45:07 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#694963; Package upstart. (Mon, 03 Dec 2012 21:21:06 GMT) (full text, mbox, link).

Acknowledgement sent to Peter <peschae@yahoo.com>:
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>. (Mon, 03 Dec 2012 21:21:06 GMT) (full text, mbox, link).

Message #17 received at 694963@bugs.debian.org (full text, mbox, reply):

From: Peter <peschae@yahoo.com>
To: Steve Langasek <vorlon@debian.org>, "694963@bugs.debian.org" <694963@bugs.debian.org>
Subject: Re: Bug#694963: upstart: Upstart can´t handle auto entry in network/interfaces
Date: Mon, 3 Dec 2012 12:19:57 -0800 (PST)
[Message part 1 (text/plain, inline)]
The file /etc/network/interfaces looked like
auto lo
iface lo inet loopback
Hello

auto wlan0
iface wlan0 inet dhcp
wpa-ssid xy
wpa-psk xyz

that worked fine so far ... then I made the update

(part of aptitude log attached)

after the update and also the update of upstart (testing to unstable) cause of boot problems the computer waits a long time
with this verbose messages:
init: startpar-bridge (networking--started) stae changed from stopping to killed
... from killed to post-stop
... from post-stop to waiting
init: handling stopped event

initctl list shows:
network-interface (lo) start/running
network-interface (eth0) start/running
network-interface (wlan0) start/running
network-interface-security (network-interface/eth0) start/running

network-interface-security (network-interface/wlan0) start/running
network-interface-security (network-interface/lo) start/running
network-interface-security (networking) start/running
network-inferface-container stop/waiting

a manual start of wlan0 works fine 
the entry allow-hotplug doen´t work on THIS computer


Sorry about the confusion with allow-hotplug. On another computer I use allow-hotplug instead of auto and that works.

Regards

Peter


________________________________
 From: Steve Langasek <vorlon@debian.org>
To: Peschae <peschae@yahoo.com>; 694963@bugs.debian.org 
Sent: Sunday, December 2, 2012 7:43 PM
Subject: Re: Bug#694963: upstart: Upstart can´t handle auto entry in network/interfaces
 
tags 694963 = moreinfo unreproducible
thanks

Hi there,

On Sun, Dec 02, 2012 at 07:30:11PM +0100, Peschae wrote:
> upstart can´t handle auto entry in /etc/network/interfaces. With this
> entry, it waits long time for the network to start without success. 
> allow-hotplug wlan0 is not an optin on every computer.  At least this one
> here (Asus notebook P53E) brings up the wlan0 only with the auto option,
> not with allow-hotplug.

> auto wlan0
> iface wlan0 inet dhcp

I'm afraid this report doesn't make any sense to me.  Currently, the
/etc/init/network-interface.conf job (which is part of the ifupdown package)
calls ifup *only* for 'auto' interfaces:

  exec ifup --allow auto $INTERFACE

It does *not* handle interfaces that are marked 'allow-hotplug', which I
know is an issue given the default /etc/network/interfaces as set up by the
installer, but that does not appear to be the issue you're reporting.  You
seem to be saying that the network is not started when using 'auto'.  Can
you please clarify?  Can you also attach the /etc/network/interfaces file
that you see problems with, and post the output of the command 'initctl list
| grep network-interface'?

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                    vorlon@debian.org
[Message part 2 (text/html, inline)]
[updates (application/octet-stream, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#694963; Package upstart. (Tue, 04 Dec 2012 02:15:04 GMT) (full text, mbox, link).

Acknowledgement sent to Steve Langasek <vorlon@debian.org>:
Extra info received and forwarded to list. (Tue, 04 Dec 2012 02:15:04 GMT) (full text, mbox, link).

Message #22 received at 694963@bugs.debian.org (full text, mbox, reply):

From: Steve Langasek <vorlon@debian.org>
To: Peter <peschae@yahoo.com>, 694963@bugs.debian.org
Subject: Re: Bug#694963: upstart: Upstart can´t handle auto entry in network/interfaces
Date: Mon, 3 Dec 2012 18:10:57 -0800
[Message part 1 (text/plain, inline)]
On Mon, Dec 03, 2012 at 12:19:57PM -0800, Peter wrote:
> The file /etc/network/interfaces looked like
> auto lo
> iface lo inet loopback
> Hello

> auto wlan0
> iface wlan0 inet dhcp
> wpa-ssid xy
> wpa-psk xyz

Ok, this all looks reasonable and is expected to work.

> after the update and also the update of upstart (testing to unstable)
> cause of boot problems the computer waits a long time with this verbose
> messages:
> init: startpar-bridge (networking--started) state changed from stopping to killed
> ... from killed to post-stop
> ... from post-stop to waiting
> init: handling stopped event

These messages are also normal.

> initctl list shows:
> network-interface (lo) start/running
> network-interface (eth0) start/running
> network-interface (wlan0) start/running
> network-interface-security (network-interface/eth0) start/running
> 
> network-interface-security (network-interface/wlan0) start/running
> network-interface-security (network-interface/lo) start/running
> network-interface-security (networking) start/running
> network-inferface-container stop/waiting

And this shows that, as far as upstart is concerned, all of the interfaces
have been configured.

After booting the system, and without manually starting any interfaces,
please gather:

 - all /var/log/upstart/network/interface-*.log files present on the system
 - the output of 'ls -l /run/network'
 - the output of 'ifconfig'
 - the file /run/network/ifstate

... and forward this information to the bug report.

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

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#694963; Package upstart. (Tue, 04 Dec 2012 20:09:07 GMT) (full text, mbox, link).

Acknowledgement sent to Peter <peschae@yahoo.com>:
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>. (Tue, 04 Dec 2012 20:09:07 GMT) (full text, mbox, link).

Message #27 received at 694963@bugs.debian.org (full text, mbox, reply):

From: Peter <peschae@yahoo.com>
To: "694963@bugs.debian.org" <694963@bugs.debian.org>
Subject: information
Date: Tue, 4 Dec 2012 12:06:48 -0800 (PST)
[Message part 1 (text/plain, inline)]
Hi, here´s the additional information:


After booting the system, and without manually starting any interfaces,
please gather:

- all /var/log/upstart/network/interface-*.log files present on the system
- the output of 'ls -l /run/network'
- the output of 'ifconfig'
- the file /run/network/ifstate

... and forward this information to the bug report.

Thanks,

var/log/upstart/interface-wlan0.log:

Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
send_packet: Network is down
No DHCPOFFERS received.
Trying recorded lease 192.168.1.36
connect: Network is unreachable
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
send_packet: Network is down
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
send_packet: Network is down
No DHCPOFFERS received.
Trying recorded lease 192.168.1.36
connect: Network is unreachable
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
send_packet: Network is down
No DHCPOFFERS received.
Trying recorded lease 192.168.1.36
connect: Network is unreachable
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
send_packet: Network is down
No DHCPOFFERS received.
Trying recorded lease 192.168.1.36
connect: Network is unreachable
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
send_packet: Network is down
No DHCPOFFERS received.
Trying recorded lease 192.168.1.36
connect: Network is unreachable
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
send_packet: Network is down
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
send_packet: Network is down
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
send_packet: Network is down
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
Trying recorded lease 192.168.1.36
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
Trying recorded lease 192.168.1.36
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.
Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file system
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

can't create /var/lib/dhcp/dhclient.wlan0.leases: Read-only file system
Listening on LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   LPF/wlan0/74:2f:68:d9:dd:3b
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.

ls -l /run/network:
insgesamt 4
-rw-r--r-- 1 root root 6 Dez  4 20:36 ifstate
-rw-r--r-- 1 root root 0 Dez  4 20:35 ifup.lo

ifconfig:
eth0      Link encap:Ethernet  Hardware Adresse 54:04:a6:25:66:f1  
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:42 

lo        Link encap:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metrik:1
          RX packets:64 errors:0 dropped:0 overruns:0 frame:0
          TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:3200 (3.1 KiB)  TX bytes:3200 (3.1 KiB)

wlan0     Link encap:Ethernet  Hardware Adresse 74:2f:68:d9:dd:3b  
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

/run/network/ifstate:
lo=lo
Regards
Peter

[Message part 2 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#694963; Package upstart. (Sat, 29 Mar 2014 03:39:04 GMT) (full text, mbox, link).

Acknowledgement sent to Cameron Norman <camerontnorman@gmail.com>:
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>. (Sat, 29 Mar 2014 03:39:05 GMT) (full text, mbox, link).

Message #32 received at 694963@bugs.debian.org (full text, mbox, reply):

From: Cameron Norman <camerontnorman@gmail.com>
To: 694963@bugs.debian.org
Subject: Upstart: network-interface tries to bring up the net device before the filesystem is rw
Date: Sat, 29 Mar 2014 03:28:13 -0007
[Message part 1 (text/plain, inline)]
> Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only file 
system

Since Upstart does not have native state, wait-for-state is going to 
need to be used for this. I have attached a modified network-interface 
job and another helper job that should fix this.

[Message part 2 (text/html, inline)]
[network-interface.conf (text/plain, attachment)]
[ifupdown.conf (text/plain, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#694963; Package upstart. (Sat, 29 Mar 2014 05:27:04 GMT) (full text, mbox, link).

Acknowledgement sent to Steve Langasek <vorlon@debian.org>:
Extra info received and forwarded to list. (Sat, 29 Mar 2014 05:27:04 GMT) (full text, mbox, link).

Message #37 received at 694963@bugs.debian.org (full text, mbox, reply):

From: Steve Langasek <vorlon@debian.org>
To: Cameron Norman <camerontnorman@gmail.com>, 694963@bugs.debian.org
Subject: Re: Bug#694963: Upstart: network-interface tries to bring up the net device before the filesystem is rw
Date: Fri, 28 Mar 2014 22:25:32 -0700
[Message part 1 (text/plain, inline)]
On Sat, Mar 29, 2014 at 03:28:13AM -0007, Cameron Norman wrote:
> > Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only
> file system

> Since Upstart does not have native state, wait-for-state is going to
> need to be used for this. I have attached a modified
> network-interface job and another helper job that should fix this.

That's not a correct fix.  If the problem is that wpa_supplicant can't run
until the full filesystem is up, that's a bug in wpa_supplicant.  It needs
to be fixed to use /run, like other network-related packages do.

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

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#694963; Package upstart. (Sat, 29 Mar 2014 16:45:15 GMT) (full text, mbox, link).

Acknowledgement sent to Cameron Norman <camerontnorman@gmail.com>:
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>. (Sat, 29 Mar 2014 16:45:15 GMT) (full text, mbox, link).

Message #42 received at 694963@bugs.debian.org (full text, mbox, reply):

From: Cameron Norman <camerontnorman@gmail.com>
To: Steve Langasek <vorlon@debian.org>
Cc: 694963@bugs.debian.org
Subject: Re: Bug#694963: Upstart: network-interface tries to bring up the net device before the filesystem is rw
Date: Sat, 29 Mar 2014 16:34:28 -0007
[Message part 1 (text/plain, inline)]
El Fri, 28 de Mar 2014 a las 10:25 PM, Steve Langasek 
<vorlon@debian.org> escribió:
> On Sat, Mar 29, 2014 at 03:28:13AM -0007, Cameron Norman wrote:
>>  > Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only
>>  file system
>> 
>>  Since Upstart does not have native state, wait-for-state is going to
>>  need to be used for this. I have attached a modified
>>  network-interface job and another helper job that should fix this.
>> 
> That's not a correct fix.  If the problem is that wpa_supplicant 
> can't run
> until the full filesystem is up, that's a bug in wpa_supplicant.  It 
> needs
> to be fixed to use /run, like other network-related packages do.
> 

Whoops that would have hung NFS boots for sure. I guess it could still 
work as a workaround if local-filesystems is used instead of 
filesystem, but the error would still occur if /usr is mounted on NFS. 
wpa_supplicant already has a bug for this, and it seems to require 
three libs in /usr. There has been no word on it since it was filed in 
2009, so that is unsatisfactory.

Thanks for the heads up,
--
Cameron Norman

[Message part 2 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#694963; Package upstart. (Sat, 29 Mar 2014 23:09:04 GMT) (full text, mbox, link).

Acknowledgement sent to Cameron Norman <camerontnorman@gmail.com>:
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>. (Sat, 29 Mar 2014 23:09:04 GMT) (full text, mbox, link).

Message #47 received at 694963@bugs.debian.org (full text, mbox, reply):

From: Cameron Norman <camerontnorman@gmail.com>
To: Steve Langasek <vorlon@debian.org>
Cc: 694963@bugs.debian.org
Subject: Re: Bug#694963: Upstart: network-interface tries to bring up the net device before the filesystem is rw
Date: Sat, 29 Mar 2014 22:59:37 -0007
[Message part 1 (text/plain, inline)]
El Fri, 28 de Mar 2014 a las 10:25 PM, Steve Langasek 
<vorlon@debian.org> escribió:
> On Sat, Mar 29, 2014 at 03:28:13AM -0007, Cameron Norman wrote:
>>  > Failed to connect to wpa_supplicant - wpa_ctrl_open: Read-only
>>  file system
>> 
>>  Since Upstart does not have native state, wait-for-state is going to
>>  need to be used for this. I have attached a modified
>>  network-interface job and another helper job that should fix this.
>> 
> That's not a correct fix.  If the problem is that wpa_supplicant 
> can't run
> until the full filesystem is up, that's a bug in wpa_supplicant.  It 
> needs
> to be fixed to use /run, like other network-related packages do.
> 

It seems to be more than that. wpa_supplicant requires a few libraries 
in /usr as well. Furthermore, it does not make much sense to mount 
stuff like /usr over wifi, so waiting until at least local filesystems 
are up to bring up wireless interfaces is acceptable, I think. I have 
attached the further modified network-interface job as well as a 
wpa_supplicant job. This one only delays wireless interfaces, not 
loopback or wired interfaces.

Best regards,
--
Cameron Norman

[Message part 2 (text/html, inline)]
[network-interface.conf (text/plain, attachment)]
[wpa_supplicant.conf (text/plain, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#694963; Package upstart. (Sat, 29 Mar 2014 23:24:15 GMT) (full text, mbox, link).

Acknowledgement sent to Steve Langasek <vorlon@debian.org>:
Extra info received and forwarded to list. (Sat, 29 Mar 2014 23:24:15 GMT) (full text, mbox, link).

Message #52 received at 694963@bugs.debian.org (full text, mbox, reply):

From: Steve Langasek <vorlon@debian.org>
To: Cameron Norman <camerontnorman@gmail.com>
Cc: 694963@bugs.debian.org
Subject: Re: Bug#694963: Upstart: network-interface tries to bring up the net device before the filesystem is rw
Date: Sat, 29 Mar 2014 16:21:23 -0700
[Message part 1 (text/plain, inline)]
On Sat, Mar 29, 2014 at 10:59:37PM -0007, Cameron Norman wrote:

> It seems to be more than that. wpa_supplicant requires a few
> libraries in /usr as well. Furthermore, it does not make much sense
> to mount stuff like /usr over wifi, so waiting until at least local
> filesystems are up to bring up wireless interfaces is acceptable, I
> think. I have attached the further modified network-interface job as
> well as a wpa_supplicant job. This one only delays wireless
> interfaces, not loopback or wired interfaces.

The path forward on /usr is to ensure /usr is mounted from the initramfs.

We should not commit halfway measures to the upstart jobs that complicate
the boot sequence and encode assumptions about network device names.

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

[signature.asc (application/pgp-signature, inline)]

Reply sent to Debian FTP Masters <ftpmaster@ftp-master.debian.org>:
You have taken responsibility. (Mon, 11 Jan 2016 05:30:10 GMT) (full text, mbox, link).

Notification sent to Peschae <peschae@yahoo.com>:
Bug acknowledged by developer. (Mon, 11 Jan 2016 05:30:10 GMT) (full text, mbox, link).

Message #57 received at 694963-done@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
To: 541141-done@bugs.debian.org,582745-done@bugs.debian.org,593348-done@bugs.debian.org,694963-done@bugs.debian.org,711630-done@bugs.debian.org,712763-done@bugs.debian.org,713135-done@bugs.debian.org,732122-done@bugs.debian.org,732123-done@bugs.debian.org,732124-done@bugs.debian.org,732125-done@bugs.debian.org,732126-done@bugs.debian.org,732127-done@bugs.debian.org,732128-done@bugs.debian.org,732130-done@bugs.debian.org,732132-done@bugs.debian.org,732179-done@bugs.debian.org,732756-done@bugs.debian.org,732946-done@bugs.debian.org,732980-done@bugs.debian.org,733287-done@bugs.debian.org,733739-done@bugs.debian.org,733741-done@bugs.debian.org,735853-done@bugs.debian.org,736611-done@bugs.debian.org,737757-done@bugs.debian.org,751649-done@bugs.debian.org,766121-done@bugs.debian.org,770014-done@bugs.debian.org,774450-done@bugs.debian.org,789524-done@bugs.debian.org,
Cc: upstart@packages.debian.org, upstart@packages.qa.debian.org
Subject: Bug#808289: Removed package(s) from unstable
Date: Mon, 11 Jan 2016 05:26:57 +0000
Version: 1.11-5+rm

Dear submitter,

as the package upstart has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/808289

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Mon, 08 Feb 2016 07:41:07 GMT) (full text, mbox, link).

Send a report that this bug log contains spam.

Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Fri Jan 12 07:02:37 2018; Machine Name: buxtehude

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.