[Bug 1412962] Re: Pacemaker (stonith) can seg fault in Trusty and Utopic after following message: Source ID XX was not found when attempting to remove it
Hi Rafael, with the last version I did not get any crashes. Also the error messages from crm_abort are gone. I tested it on both my testing cluster and the production system. Many Thanks! Peter -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1412962 Title: Pacemaker (stonith) can seg fault in Trusty and Utopic after following message: Source ID XX was not found when attempting to remove it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1412962/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414887] [NEW] dns query from localnetwork are blocked
Public bug reported: Hi, I followed the following to config dnsmasq as DHCP and DNS server http://sfxpt.wordpress.com/2013/11/30/dnsmasq-installation- configuration-5/ It works well till Ubuntu 13.10. However, with Ubuntu 14.10, the dns query from localnetwork will always timeout. The configurations are exactly the same, What could be the problem? >From within localnetwork: ~~~ $ dig google.ca ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> google.ca ;; global options: +cmd ;; connection timed out; no servers could be reached dig @192.168.2.100 maroon ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> @192.168.2.100 maroon ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached ~~~ On the DNS sever itself: ~~~ $ dig google.ca @127.0.0.1 ... ;; ANSWER SECTION: google.ca. 299 IN A 173.194.43.111 ... ;; Query time: 50 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) $ dig @192.168.2.100 maroon ... ;; ANSWER SECTION: maroon. 0 IN A 192.168.2.100 ;; Query time: 1 msec ;; SERVER: 192.168.2.100#53(192.168.2.100) ... ~~~ This is the debug output from dnsmasq log: ~~~ Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.119 Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.120 *** DEBUG 2015-01-01 13:26:21-05:00 DEBUG *** Jan 1 13:27:42 maroon dnsmasq[2833]: query[A] maroon from 192.168.2.100 Jan 1 13:27:42 maroon dnsmasq[2833]: /etc/dnsmasq.hosts maroon is 192.168.2.100 *** DEBUG 2015-01-01 13:28:19-05:00 DEBUG *** ~~~ All other dns queries from localnetwork did not generate any log entries. So, because the local dns query work, I think something is blocking the dnsmasq from sending the dns query results back to localnetwork. What could it be? I didn't limit the dnsmasq listen address: ~~~ $ grep listen-address /etc/dnsmasq.conf /etc/dnsmasq.d/* /etc/dnsmasq.conf:#listen-address= ~~~ My /etc/hosts.deny and hosts.allow files are untouched either, and I can ping my DNS server, and ssh into its IP address as well. So I think the blocking is only at the DNS level since other access are just fine. It is not because of iptables rules either: $ sudo iptables-save | wc 0 0 0 I've installed dnsmasq on two different machines, one being freshly installed today, and both of them are showing exactly the same symptom. Again, it only happens to Ubuntu 14.10. It was working well till Ubuntu 13.10 before. I've run out of all the possibilities. What could be the problem? Thanks $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic $ apt-cache policy dnsmasq dnsmasq: Installed: 2.71-1 Candidate: 2.71-1 Version table: *** 2.71-1 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, - I following the following to config dnsmasq as DHCP and DNS server + I followed the following to config dnsmasq as DHCP and DNS server http://sfxpt.wordpress.com/2013/11/30/dnsmasq-installation- configuration-5/ - It works well till Ubuntu 13.10. However, with Ubuntu 14.10, the dns - query from localnetwork will always timeout. The configurations are - exactly the same, What could be the problem? + It works well till Ubuntu 13.10. However, with Ubuntu 14.10, the dns + query from localnetwork will always timeout. The configurations are + exactly the same, What could be the problem? From within localnetwork: ~~~ $ dig google.ca ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> google.ca ;; global options: +cmd ;; connection timed out; no servers could be reached dig @192.168.2.100 maroon ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> @192.168.2.100 maroon ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached ~~~ On the DNS sever itself: ~~~ $ dig google.ca @127.0.0.1 ... ;; ANSWER SECTION: google.ca. 299 IN A 173.194.43.111 ... ;; Query time: 50 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) $ dig @192.168.2.100 maroon ... ;; ANSWER SECTION: maroon. 0 IN A 192.168.2.100 ;; Query time: 1 msec ;; SERVER: 192.168.2.100#53(192.168.2.100) ... ~~~ This is the debug output from dnsmasq log: ~~~ Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.119 Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.120 - *** DEBUG 2015-01-01 13:26:21-05:00 DEBUG *** + *** DEBUG 2015-01-01 13:26:21-05:00 DEBUG *** Jan 1 13:27:42 maroon dnsmasq[2833]: query[A] maroon from 192.168.2.100 - Jan 1 13:27:42 maroon dnsmasq[2833]: /etc/dnsmasq.hosts maroon is + Jan 1 13:27:42 maroon dnsmasq[2833]: /etc/dnsmasq.hosts maroon is 192.168.2.100 - *** DEBUG 201
Re: [Bug 1413826] Re: bind9 dependency problem
Thanks you very much Robbie , I'm new to Ubuntu and this is my first time to use this kind of support, again a lot of thanks for your time. On Mon, Jan 26, 2015 at 5:45 PM, Robie Basak <1413...@bugs.launchpad.net> wrote: > Thank you for your report. > > This looks like a local configuration problem, rather than a bug in > Ubuntu. > > You can find pointers to get help for this sort of problem here: > http://www.ubuntu.com/support/community > > Since we use this bug tracker to track bugs in Ubuntu, rather than > configuration problems, I'm marking this bug as Invalid. This helps us > to focus on fixing bugs in Ubuntu. > > If you believe that this is really a bug, then you may find it helpful > to read "How to report bugs effectively" > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem, > explain why you believe this is a bug in Ubuntu rather than a problem > specific to your system, and then change the bug status back to New. > > > ** Changed in: bind9 (Ubuntu) >Status: New => Triaged > > ** Changed in: bind9 (Ubuntu) >Status: Triaged => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1413826 > > Title: > bind9 dependency problem > > Status in bind9 package in Ubuntu: > Invalid > > Bug description: > cannot complete update packages' process. > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: bind9 1:9.9.5.dfsg-3ubuntu0.1 > ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 > Uname: Linux 3.13.0-41-generic i686 > ApportVersion: 2.14.1-0ubuntu3.6 > Architecture: i386 > CurrentDesktop: Unity > Date: Fri Jan 23 08:25:24 2015 > InstallationDate: Installed on 2014-06-01 (235 days ago) > InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release i386 > (20140416.2) > ProcEnviron: >LANGUAGE=en_US:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > RelatedPackageVersions: >bind9utils 1:9.9.5.dfsg-3ubuntu0.1 >apparmor 2.8.95~2430-0ubuntu5.1 > SourcePackage: bind9 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1413826/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1413826 Title: bind9 dependency problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1413826/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414816] Re: [Ubuntu 15.04] librtas package update
Would probably make sense to check the archive before filing bugs: librtas | 1.3.13-1~14.04 | trusty-proposed | source librtas | 1.3.13-1~14.10 | utopic-proposed | source librtas | 1.3.13-1| vivid | source This was uploaded 11 days before the bug was filed. ** Changed in: librtas (Ubuntu) Status: New => Fix Released ** Changed in: librtas (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Adam Conrad (adconrad) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to librtas in Ubuntu. https://bugs.launchpad.net/bugs/1414816 Title: [Ubuntu 15.04] librtas package update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librtas/+bug/1414816/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1402657] Re: etckeeper doesn't commit. Missing executable permissions on /etc/etckeeper/commit.d/50vcs-commit
If someone wanted to silently and efficiently deactivate etckeeper history tracking with the least action, this would be the best thing to do. Was hit by this also. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1402657 Title: etckeeper doesn't commit. Missing executable permissions on /etc/etckeeper/commit.d/50vcs-commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1402657/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414816] Re: [Ubuntu 15.04] librtas package update
** Package changed: ubuntu => librtas (Ubuntu) ** Changed in: librtas (Ubuntu) Assignee: (unassigned) => Taco Screen team (taco-screen-team) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to librtas in Ubuntu. https://bugs.launchpad.net/bugs/1414816 Title: [Ubuntu 15.04] librtas package update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librtas/+bug/1414816/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414771] Re: Can not clone lxc container with lvm backingstore after ubuntu update
May be related to https://github.com/lxc/lxc/issues/406 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1414771 Title: Can not clone lxc container with lvm backingstore after ubuntu update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1414771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414816] [NEW] [Ubuntu 15.04] librtas package update
You have been subscribed to a public bug: Current upstream version: http://sourceforge.net/projects/librtas/files/librtas-1.3.13.tar.gz/download -Vasant Changelog for librtas-1.3.13 === commit 1d54a4a346f9111e1326dfdec756fd78360add42 Author: Nathan Fontenot Date: Fri Oct 17 10:18:40 2014 -0400 When we pass _hi and _lo 32bits of a 64bit value, we should convert the host endian value carefully. i.e, X_hi = htobe32(BITS32_HI(X)) X_lo = htobe32(BITS32_LO(X)) and not : X_hi = BITS32_HI(htobe64(X)) NOTE: This patch is untested, but I believe this patch is good to have than the current faulty conversion. This patch fixes all such occurrences in librtas. Signed-off-by: Suzuki K. Poulose commit e5541e1a5c83ce47cc492abcd7343d65763dcefe Author: Nathan Fontenot Date: Fri Oct 17 10:17:28 2014 -0400 Use rpm macros for standard paths Signed-off-by: Suzuki K. Poulose commit 8ef7f827e28e3cd284f6be5686a987786be7502d Author: Nathan Fontenot Date: Fri Oct 17 10:16:16 2014 -0400 This patch fixes the conversion of args for paltform-dump call. platform dump passes 64bit values as, a pair of 32bit values. val_hi and val_lo. So when we convert a value 'X' to 32bit hi and lo values in BE, we should follow the below approach : X_hi = htobe32(BITS32_HI(X)) X_lo = htobe32(BITS32_LO(X)) and NOT X_tmp = htobe64(X); X_hi = BITS32_HI(X_tmp), X_lo = BITS32_LO(X_tmp) This patch has been tested with rtas_errd/extract_platdump to retrieve a dump from FSP. Signed-off-by: Suzuki K. Poulose commit 52263814c46210b51e564748050299620726dfd1 Author: Nathan Fontenot Date: Fri Oct 17 10:12:54 2014 -0400 Fix LE parsing of SRC/FRU events Signed-off-by: Thomas L Falcon Signed-off-by: Suzuki K. Poulose commit ac0a91d2730740cd279d80ccd4c83b0a04827d1d Author: Nathan Fontenot Date: Fri Oct 17 10:10:29 2014 -0400 LE Support for SRC/FRU events Signed-off-by: Nathan Fontenot Above mentioned changes are required to make rtas_errd (Platform Error Logging) daemon to work properly. -Vasant ** Affects: librtas (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-118489 severity-high targetmilestone-inin1504 -- [Ubuntu 15.04] librtas package update https://bugs.launchpad.net/bugs/1414816 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to librtas in Ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1368815] Re: qemu-img convert intermittently corrupts output images
** Changed in: cinder Assignee: (unassigned) => Tony Breeds (o-tony) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1368815 Title: qemu-img convert intermittently corrupts output images To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1368815/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1368815] Re: qemu-img convert intermittently corrupts output images
** Changed in: cinder Status: In Progress => Triaged ** Changed in: cinder Assignee: Tony Breeds (o-tony) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1368815 Title: qemu-img convert intermittently corrupts output images To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1368815/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414771] [NEW] Can not clone lxc container with lvm backingstore after ubuntu update
Public bug reported: lxc-clone -s -K -M -H -o debian7 -n debian7-bak lxc_container: bdev.c: mount_unknown_fs: 209 failed to determine fs type for '/dev/vg/debian7' lxc_container: bdev.c: detect_fs: 320 failed mounting /dev/vg/debian7 onto /container/debian7/debian7 to detect fstype lxc_container: bdev.c: detect_fs: 298 child exited early - fstype not found lxc_container: bdev.c: bdev_copy: 3090 failed getting pathnames for cloned storage: /dev/vg/debian7 lxc_container: lxccontainer.c: copy_storage: 2489 Error copying storage clone failed Aptitude LOG [AKTUALISIERUNG] landscape-common:amd64 14.01-0ubuntu3 -> 14.12-0ubuntu0.14.04 [AKTUALISIERUNG] libelf1:amd64 0.158-0ubuntu5.1 -> 0.158-0ubuntu5.2 [AKTUALISIERUNG] libevent-2.0-5:amd64 2.0.21-stable-1ubuntu1 -> 2.0.21-stable-1ubuntu1.14.04.1 [AKTUALISIERUNG] liblxc1:amd64 1.0.6-0ubuntu0.1 -> 1.0.7-0ubuntu0.1 [AKTUALISIERUNG] libmysqlclient18:amd64 5.5.40-0ubuntu0.14.04.1 -> 5.5.41-0ubuntu0.14.04.1 [AKTUALISIERUNG] lxc:amd64 1.0.6-0ubuntu0.1 -> 1.0.7-0ubuntu0.1 [AKTUALISIERUNG] lxc-templates:amd64 1.0.6-0ubuntu0.1 -> 1.0.7-0ubuntu0.1 [AKTUALISIERUNG] mysql-common:amd64 5.5.40-0ubuntu0.14.04.1 -> 5.5.41-0ubuntu0.14.04.1 [AKTUALISIERUNG] python-apt:amd64 0.9.3.5 -> 0.9.3.5ubuntu1 [AKTUALISIERUNG] python-apt-common:amd64 0.9.3.5 -> 0.9.3.5ubuntu1 [AKTUALISIERUNG] python3-apt:amd64 0.9.3.5 -> 0.9.3.5ubuntu1 [AKTUALISIERUNG] python3-lxc:amd64 1.0.6-0ubuntu0.1 -> 1.0.7-0ubuntu0.1 Trusty update 3.13.0-44-generic #73-Ubuntu SMP ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1414771 Title: Can not clone lxc container with lvm backingstore after ubuntu update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1414771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1412962] Re: Pacemaker (stonith) can seg fault in Trusty and Utopic after following message: Source ID XX was not found when attempting to remove it
Hello Peter, Could you test version ~2 ? I'm uploading it to the PPA right now. I backported some other fixes regarding the same issue. Waiting on your feedback. Thanks for reporting!!! Rafael Tinoco -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1412962 Title: Pacemaker (stonith) can seg fault in Trusty and Utopic after following message: Source ID XX was not found when attempting to remove it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1412962/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1350947] Re: apparmor: no working rule to allow making a mount private
This fix is contained in the latest lxc in vivid now. ** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1350947 Title: apparmor: no working rule to allow making a mount private To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1350947/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
With latest lxc and lxcfs this works now, both system and session containers with systemd, with systemd on the host. ** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released ** Changed in: lxc (Ubuntu Trusty) Assignee: (unassigned) => Stéphane Graber (stgraber) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1412962] Re: Pacemaker (stonith) can seg fault in Trusty and Utopic after following message: Source ID XX was not found when attempting to remove it
Hello Peter, Downloading the core dump to analyze it... tks for uploading it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1412962 Title: Pacemaker (stonith) can seg fault in Trusty and Utopic after following message: Source ID XX was not found when attempting to remove it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1412962/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1413343] Re: lxc-create debug output is broken or useless
Sorry, I don't quite understand your questions. What do you mean by "running under the root"? What is "the problem" at this point? If you're getting an error creating unprivileged containers (which are created/started without becoming the root user), see "Basic unprivileged usage" at https://help.ubuntu.com/stable/serverguide/lxc.html. You just need to create ~/.config/lxc/default.conf with a default userid mapping, and grant yourself the right to connect network interfaces to lxcbr0 using the file /etc/lxc/lxc-usernet. As for a 'default template', I believe the download template is now the most commonly used. You can just do sudo lxc-create -n b1 -t download to be interactively queried as to the distribution/release/architecture. In comment #2 I showed how to create a container using the most reason Ubuntu LTS (14.04 trusty tahr) as the guest OS. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1413343 Title: lxc-create debug output is broken or useless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413343/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1413922] Re: lxc unprivileged containers broken
*** This bug is a duplicate of bug 1413927 *** https://bugs.launchpad.net/bugs/1413927 ** This bug has been marked a duplicate of bug 1413927 user lxc containers fail to start under systemd: login name=systemd cgroup is not owned by user -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1413922 Title: lxc unprivileged containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1401198] Re: package spamassassin 3.4.0-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: spamassassin (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1401198 Title: package spamassassin 3.4.0-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1401198/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414684] [NEW] bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)
Public bug reported: The security update of bsd-mailx (8.1.2-0.2006cvs-1ubuntu0.1 on Ubuntu 12.04) removes bsd-mailx's support for specifying sendmail options after "--" on the commandline. This breaks any script that supplies classic sendmail options like -F or -f on the mail commandline. A prominent example is Bootmail, which calls mailx in the following way: print_mail_text | sed -e "s/[^[:print:]]//g" | rootsign | mail -s "$subject" "$recipients" -- -F "Bootmail" -f "$FROM_MAIL" Here the options -F and -f are used to set the From: header in the resulting mail message. This is now broken and results in error messages like these in /var/log/mail.log (on systems that run Postfix): Jan 26 16:20:09 example01 postfix/error[31885]: 4351640CB7: to=<-f...@web01.example.com>, orig_to=<-F>, relay=none, delay=0.16, delays=0.12/0/0/0.05, dsn=5.1.3, status=bounced (bad address syntax) Is this change going to stay for good? In that case we need to report a bug against the Bootmail package (and probably quite a few others) to change the mail commandline to use the "-a" commandline switch for specifying additional mail headers. I find it disconcerting that a security update completely removes functionality that has been available and expected for many years without providing a proper compatibility layer. Is this really the way to do this? ** Affects: bsd-mailx (Ubuntu) Importance: Undecided Status: New ** Description changed: - The security update of bsd-mailx (8.1.2-0.2006cvs-1ubuntu0.1) - removes bsd-mailx's support for specifying sendmail options after "--" - on the commandline. + The security update of bsd-mailx (8.1.2-0.2006cvs-1ubuntu0.1 on + Ubuntu 12.04) removes bsd-mailx's support for specifying sendmail + options after "--" on the commandline. This breaks any script that supplies classic sendmail options like -F or -f on the mail commandline. A prominent example is Bootmail, which calls mailx in the following way: print_mail_text | sed -e "s/[^[:print:]]//g" | rootsign | mail -s "$subject" "$recipients" -- -F "Bootmail" -f "$FROM_MAIL" Here the options -F and -f are used to set the From: header in the resulting mail message. This is now broken and results in error messages like these in /var/log/mail.log (on systems that run Postfix): Jan 26 16:20:09 example01 postfix/error[31885]: 4351640CB7: to=<-f...@web01.example.com>, orig_to=<-F>, relay=none, delay=0.16, delays=0.12/0/0/0.05, dsn=5.1.3, status=bounced (bad address syntax) Is this change going to stay for good? In that case we need to report a bug against the Bootmail package (and probably quite a few others) to change the mail commandline to use the "-a" commandline switch for specifying additional mail headers. I find it disconcerting that a security update completely removes functionality that has been available and expected for many years without providing a proper compatibility layer. Is this really the way to do this? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs.launchpad.net/bugs/1414684 Title: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414678] [NEW] package mysql-server-5.5 5.5.41-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: subprocess installed post-installation script returned error
Public bug reported: Never have been able to install mysql. Changing mysql requires removing most of KDE due to dependancies. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: mysql-server-5.5 5.5.41-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Jan 26 10:26:30 2015 DuplicateSignature: package:mysql-server-5.5:5.5.41-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt]:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-08-15 (164 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Logs.var.log.daemon.log: Logs.var.log.mysql.error.log: MySQLConf.etc.mysql.conf.d..keepme: MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['mysql_upgrade_info', 'ib_logfile0', 'mysql-bin.08', 'QRCards', 'ibdata1', 'mysql-bin.04', 'error.log', 'slow.log', 'mysql-bin.06', 'mysql-bin.09', 'mysql-bin.10', 'mysql-bin.02', 'mysql-bin.05', 'paul-desktop.err', 'mysql-bin.11', 'mysql-bin.07', 'debian-5.5.flag', 'mysql-bin.12', 'mysql-bin.index', 'mysql', 'ib_logfile1', 'performance_schema', 'mysql-bin.03', 'mysql-bin.01'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=f8d89217-df1e-4938-afa6-26e494cf3344 ro quiet splash SourcePackage: mysql-5.5 Title: package mysql-server-5.5 5.5.41-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1414678 Title: package mysql-server-5.5 5.5.41-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1414678/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'
I had this same problem today and we changed the MTU to 1500 on the remote server we were trying to connect to and everything worked straight afterwards. I was trying to do a simple git clone user@domain:group/repo.git. >From the local server I was connecting from to do the clone it would always hang at debug1: SSH2_MSG_KEXINIT sent and then time out. Remote Server: openssh-server: Installed: 1:6.6p1-2ubuntu2 Candidate: 1:6.6p1-2ubuntu2 Version table: *** 1:6.6p1-2ubuntu2 0 500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.6p1-2ubuntu1 0 500 http://za.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Local Server (Gentoo): * net-misc/openssh Latest version available: 6.7_p1 Latest version installed: 6.7_p1 Size of files: 1344 KiB Homepage: http://www.openssh.org/ Description: Port of OpenBSD's free SSH release License: BSD GPL-2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1254085 Title: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1368815] Change abandoned on cinder (master)
Change abandoned by Mike Perez (thin...@gmail.com) on branch: master Review: https://review.openstack.org/143575 Reason: 1 month, no update. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1368815 Title: qemu-img convert intermittently corrupts output images To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1368815/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1414153] Re: qemu should not enable KSM on nested guests
There's nothing preventing nested guests architectually IIUC. I don't know that anyone has implemented it yet but seems reasonable to thing ahead and avoid x86isms where possible. On Sat, Jan 24, 2015 at 3:27 PM, Chris J Arges <1414...@bugs.launchpad.net> wrote: > Ryan, > I don't think Power8/kvm nor ARM/kvm allow for nested guests, so do we > need to worry about in those cases? > --chris > > -- > You received this bug notification because you are subscribed to qemu in > Ubuntu. > https://bugs.launchpad.net/bugs/1414153 > > Title: > qemu should not enable KSM on nested guests > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1414153/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1414153 Title: qemu should not enable KSM on nested guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1414153/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414153] Re: qemu should not enable KSM on nested guests
I'll look for a more agnostic solution. We most likely don't want to run KSM in L1 by default in any guest not just one that will host nested VMs. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1414153 Title: qemu should not enable KSM on nested guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1414153/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1391322] Comment bridged from LTC Bugzilla
--- Comment From ferse...@br.ibm.com 2015-01-26 14:49 EDT--- I have just verified and the packages can be found in proposed for both 14.04 and 14.10. So it looks good for both repositories. Thus we are now just awaiting for the final testing by the RAS team. trusty: # apt-cache madison libofdt-dev libofdt1 librtas-dev librtas1 librtasevent-dev librtasevent1 libofdt-dev | 1.3.13-1~14.04 | http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el Packages librtas | 1.3.13-1~14.04 | http://archive.ubuntu.com/ubuntu/ trusty-proposed/main Sources libofdt1 | 1.3.13-1~14.04 | http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el Packages librtas | 1.3.13-1~14.04 | http://archive.ubuntu.com/ubuntu/ trusty-proposed/main Sources librtas-dev | 1.3.13-1~14.04 | http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el Packages librtas | 1.3.13-1~14.04 | http://archive.ubuntu.com/ubuntu/ trusty-proposed/main Sources librtas1 | 1.3.13-1~14.04 | http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el Packages librtas | 1.3.13-1~14.04 | http://archive.ubuntu.com/ubuntu/ trusty-proposed/main Sources librtasevent-dev | 1.3.13-1~14.04 | http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el Packages librtas | 1.3.13-1~14.04 | http://archive.ubuntu.com/ubuntu/ trusty-proposed/main Sources librtasevent1 | 1.3.13-1~14.04 | http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el Packages librtas | 1.3.13-1~14.04 | http://archive.ubuntu.com/ubuntu/ trusty-proposed/main Sources # apt-get install libofdt-dev libofdt1 librtas-dev librtas1 librtasevent-dev librtasevent1 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: libofdt-dev libofdt1 librtas-dev librtas1 librtasevent-dev librtasevent1 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 132 kB of archives. After this operation, 792 kB of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main librtas1 ppc64el 1.3.13-1~14.04 [22.2 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main librtasevent1 ppc64el 1.3.13-1~14.04 [27.4 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main libofdt1 ppc64el 1.3.13-1~14.04 [11.8 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main libofdt-dev ppc64el 1.3.13-1~14.04 [10.6 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main librtas-dev ppc64el 1.3.13-1~14.04 [23.5 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main librtasevent-dev ppc64el 1.3.13-1~14.04 [36.4 kB] Fetched 132 kB in 2s (47.2 kB/s) Selecting previously unselected package librtas1. (Reading database ... 46789 files and directories currently installed.) Preparing to unpack .../librtas1_1.3.13-1~14.04_ppc64el.deb ... Unpacking librtas1 (1.3.13-1~14.04) ... Selecting previously unselected package librtasevent1. Preparing to unpack .../librtasevent1_1.3.13-1~14.04_ppc64el.deb ... Unpacking librtasevent1 (1.3.13-1~14.04) ... Selecting previously unselected package libofdt1. Preparing to unpack .../libofdt1_1.3.13-1~14.04_ppc64el.deb ... Unpacking libofdt1 (1.3.13-1~14.04) ... Selecting previously unselected package libofdt-dev. Preparing to unpack .../libofdt-dev_1.3.13-1~14.04_ppc64el.deb ... Unpacking libofdt-dev (1.3.13-1~14.04) ... Selecting previously unselected package librtas-dev. Preparing to unpack .../librtas-dev_1.3.13-1~14.04_ppc64el.deb ... Unpacking librtas-dev (1.3.13-1~14.04) ... Selecting previously unselected package librtasevent-dev. Preparing to unpack .../librtasevent-dev_1.3.13-1~14.04_ppc64el.deb ... Unpacking librtasevent-dev (1.3.13-1~14.04) ... Setting up librtas1 (1.3.13-1~14.04) ... Setting up librtasevent1 (1.3.13-1~14.04) ... Setting up libofdt1 (1.3.13-1~14.04) ... Setting up libofdt-dev (1.3.13-1~14.04) ... Setting up librtas-dev (1.3.13-1~14.04) ... Setting up librtasevent-dev (1.3.13-1~14.04) ... Processing triggers for libc-bin (2.19-0ubuntu6.5) ... utopic: # apt-cache madison libofdt-dev libofdt1 librtas-dev librtas1 librtasevent-dev librtasevent1 libofdt-dev | 1.3.13-1~14.10 | http://ports.ubuntu.com/ubuntu-ports/ utopic-proposed/main ppc64el Packages librtas | 1.3.13-1~14.10 | http://archive.ubuntu.com/ubuntu/ utopic-proposed/main Sources libofdt1 | 1.3.13-1~14.10 | http://ports.ubuntu.com/ubuntu-ports/ utopic-proposed/main ppc64el Packages librtas | 1.3.13-1~14.10 | http://archive.ubuntu.com/ubuntu/ utopic-proposed/main Sources librtas-dev | 1.3.13-1~14.10 | http://ports.ubuntu.com/ubuntu-ports/ utopic-proposed/main ppc64el Packages librtas | 1.3.13-1~14.10 | http://archive.ubuntu.com/ubuntu/ utopic-proposed/main Sources librtas1 | 1.3.13-1~14.10 | http://ports.ubuntu.com/ubuntu-ports/ utopic-proposed/main ppc64el Packages librtas | 1.3.13-1~14.10 | http://archive.ubuntu.com/ubuntu/ utopic-proposed/main Sources libr
[Bug 1411177] Re: `make package` fails (Patch 02-pserv-config.patch does not apply)
** Changed in: maas (Ubuntu) Status: New => Fix Committed ** No longer affects: maas -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1411177 Title: `make package` fails (Patch 02-pserv-config.patch does not apply) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1411177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1391322] Re: [ubuntu- 14.10] librtas: fixes for LE support
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to librtas in Ubuntu. https://bugs.launchpad.net/bugs/1391322 Title: [ubuntu- 14.10] librtas: fixes for LE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librtas/+bug/1391322/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1413826] Re: bind9 dependency problem
Thank you for your report. This looks like a local configuration problem, rather than a bug in Ubuntu. You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu. If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: bind9 (Ubuntu) Status: New => Triaged ** Changed in: bind9 (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1413826 Title: bind9 dependency problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1413826/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1413826] Re: bind9 dependency problem
>From log: Jan 23 08:16:06 kmsubuntu named[6624]: loading configuration from '/etc/bind/named.conf' Jan 23 08:16:06 kmsubuntu named[6624]: /etc/bind/named.conf.options:16: missing ';' before '}' Jan 23 08:16:06 kmsubuntu named[6624]: loading configuration: failure Jan 23 08:16:06 kmsubuntu named[6624]: exiting (due to fatal error) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1413826 Title: bind9 dependency problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1413826/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1388300] Re: Sync pep8 1.5.7-2 (main) from Debian unstable (main)
Liam independently investigated and asked me to sync this package over the weekend. I just verified this and found this bug, so closing this bug also at the same time. I can't mark you both as the sponsoree, so I've named Liam as he initally led me here. I hope that's OK, Jackson. Did you mean to have subscribed ~ubuntu-sponsors? Anyway, done now. ** Changed in: pep8 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pep8 in Ubuntu. https://bugs.launchpad.net/bugs/1388300 Title: Sync pep8 1.5.7-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pep8/+bug/1388300/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs