[Bug 1504923] Re: package unixodbc 2.2.14p2-5ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unixodbc in Ubuntu. https://bugs.launchpad.net/bugs/1504923 Title: package unixodbc 2.2.14p2-5ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unixodbc/+bug/1504923/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed
To completely rule out that it's not the python3.4 regression in trusty- proposed (bug 1500768) or the (really unrelated) udev fix in bug 1470399 I instead ran it with --apt-pocket=proposed --setup-commands 'apt-get update; apt-get -y install linux-generic' instead of the -U /--apt-upgrade switch, so that it only runs against the new kernel, but nothing else in -proposed. @Stéphane: It would be really useful if the test suite could detect failures of lxc-start, and show its output on failures. Such quiet /forever-hanging tests without any timeouts are both unnecessarily hard to detect, as well as put quite a burden on the infrastructure as they just hang around for 2:50 hours until the autopkgtest timeout kicks in. ** Summary changed: - lxc-test-ubuntu hangs forever in trusty-proposed + lxc-test-ubuntu hangs forever in trusty-proposed: AppArmor denies /dev/ptmx mounting ** Summary changed: - lxc-test-ubuntu hangs forever in trusty-proposed: AppArmor denies /dev/ptmx mounting + lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: lxc (Ubuntu) Status: New => Invalid ** Tags added: regression-proposed -- 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/1504781 Title: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1503611] Re: systemd: spamassassin not starting after upgrading to 15.04
After 14.10 to 15.04 upgrade, with amavis so spamassassin is installed, but spamd shouldn't be running IIRC, root is receiving /etc/cron.daily output. /etc/cron.daily/spamassassin: Job for spamassassin.service invalid. invoke-rc.d: initscript spamassassin, action "reload" failed. Here, I've $ grep '^[^#]' /etc/default/spamassassin ENABLED=0 OPTIONS="--create-prefs --max-children 5 --helper-home-dir" PIDFILE="/var/run/spamd.pid" CRON=1 $ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774380 looks related. ** Changed in: spamassassin (Ubuntu) Status: New => Confirmed ** Bug watch added: Debian Bug tracker #774380 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774380 -- 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/1503611 Title: systemd: spamassassin not starting after upgrading to 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1503611/+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 1504781] Re: lxc: test suites failing on trusty
Running lxc test against trusty-release in the CI production environment still works fine (against kernel -65). I do get the hang with running against -proposed, under otherwise the exact same circumstances. The dist-upgrade to -proposed does the following: The following NEW packages will be installed: linux-headers-3.13.0-66 linux-headers-3.13.0-66-generic linux-image-3.13.0-66-generic The following packages will be upgraded: apport grub-common grub-pc grub-pc-bin grub2-common libpam-systemd libpython3.4-minimal libpython3.4-stdlib libsystemd-daemon0 libsystemd-login0 libudev1 linux-headers-generic linux-headers-virtual linux-image-virtual linux-virtual ntpdate python3-apport python3-problem-report python3.4 python3.4-minimal systemd-services udev I obviously hangs in lxc-test-ubuntu. I wonder if that's the first test which actually uses a bootstrapped full ubuntu image, not just a simple busybox one? When it hangs, the following test related processes are running: lxc-dns+ 3298 0.0 0.0 28204 956 ?S09:07 0:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative root 12758 0.0 0.0 4440 656 ?S09:11 0:00 /bin/sh /usr/bin/lxc-test-ubuntu root 31374 0.0 0.0 34724 1348 ?Ss 09:13 0:00 /usr/lib/x86_64-linux-gnu/lxc/lxc-monitord /var/lib/lxc 5 root 31426 0.0 0.0 34712 1504 ?S09:13 0:00 lxc-wait -n 4a5f2adb-d593-4837-8698-f5455e95729e -s RUNNING $ sudo lxc-ls -f NAME STATEIPV4 IPV6 AUTOSTART 4a5f2adb-d593-4837-8698-f5455e95729e STOPPED - - NO so it seems the container never starts up? /var/lib/lxc/4a5f2adb-d593-4837-8698-f5455e95729e/rootfs/ looks like a normal rootfs, and /var/lib/lxc/4a5f2adb-d593-4837-8698-f5455e95729e/config exists too. However, dmesg contains [ 352.395653] type=1400 audit(1444554813.144:26): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="/usr/bin /lxc-start" name="/dev/ptmx" pid=31390 comm="lxc-start" srcname="/dev/pts/ptmx" flags="rw, bind" and when I try to start it, I indeed get root@adt:~# lxc-start -n 4a5f2adb-d593-4837-8698-f5455e95729e -F lxc-start: conf.c: setup_pts: 1772 Permission denied - mount failed '/dev/pts/ptmx'->'/dev/ptmx' lxc-start: conf.c: lxc_setup: 4230 failed to setup the new pts instance lxc-start: start.c: do_start: 688 failed to setup the container lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2 lxc-start: start.c: __lxc_start: 1080 failed to spawn '4a5f2adb-d593-4837-8698-f5455e95729e' lxc-start: lxc_start.c: main: 342 The container failed to start. lxc-start: lxc_start.c: main: 346 Additional information can be obtained by setting the --logfile and --logpriority options. and the same apparmor error repeated. So this surely does look like some lxc/kernel/apparmor related change to me, and I'd hold back that kernel until this gets examined more closely. ** Summary changed: - lxc: test suites failing on trusty + lxc-test-ubuntu hangs forever in trusty-proposed -- 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/1504781 Title: lxc-test-ubuntu hangs forever in trusty-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1504781/+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 1504923] [NEW] package unixodbc 2.2.14p2-5ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: I can not install soft for MP3 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: unixodbc 2.2.14p2-5ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.15 Architecture: i386 Date: Sun Oct 11 12:03:23 2015 DuplicateSignature: package:unixodbc:2.2.14p2-5ubuntu5:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-10-09 (2 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: unixodbc Title: package unixodbc 2.2.14p2-5ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2015-10-09 (1 days ago) ** Affects: unixodbc (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unixodbc in Ubuntu. https://bugs.launchpad.net/bugs/1504923 Title: package unixodbc 2.2.14p2-5ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unixodbc/+bug/1504923/+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 1504781] Re: lxc: test suites failing on trusty
> or a failure to reach the cloud image server. The tests work on wily and vivid, so in principle they can talk to the cloud image server or linuxcontainers.org. It might of course be that later LXC versions got some proxy fixes or something such. However, the tests in trusty also worked until October 6th and started failing from October 7th on (http://autopkgtest.ubuntu.com/packages/l/lxc/trusty/amd64/). There was no change in autopkgtest or autopkgtest-cloud, or a re-roll of the infrastructure then. The main difference in http://autopkgtest.ubuntu.com/data/packages/trusty/amd64/l/lxc/20151007_063858@.log is indeed kernel -65 to -66. Anyway, I'll investigate this more closely and follow up here. -- 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/1504781 Title: lxc: test suites failing on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1504781/+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 1504781] Re: lxc: test suites failing on trusty
Keeping notes: I did a local QEMU run against trusty release and trusty- proposed: adt-run lxc -s --- qemu /srv/vm/adt-trusty-amd64-cloud.img adt-run --apt-pocket=proposed -U lxc -s --- qemu /srv/vm/adt-trusty-amd64-cloud.img They both fail for the same reason: five tests fail due to "ERROR: Unable to fetch GPG key from keyserver." -- presumably because the test has some special magic with "Running in the Canonical CI environment" which doesn't apply to my laptop where no proxy is in use. The test doesn't hang there, but that doesn't say that much as the test apparently behaves rather different in local qemu vs. Canonical cloud with proxy. -- 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/1504781 Title: lxc: test suites failing on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1504781/+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 1457517] Re: Unable to boot from volume when flavor disk too small
** Also affects: nova/kilo Importance: Undecided Status: New ** Changed in: nova/kilo Milestone: None => 2015.1.2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1457517 Title: Unable to boot from volume when flavor disk too small To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1457517/+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 1485380] Re: package mysql-server-5.6 5.6.25-0ubuntu0.15.04.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
affects me too after upgrading from Lubuntu 15.04 to 15.10. Tried to reinstall the package because with "systemd-analyze" I get the answer: "boot not yet finished. Try later". In fact, the boot finishes after 20 min. I traced the problem back to mysql.service. Consequently, I tried to re - install mysql-server-5.6.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1485380 Title: package mysql-server-5.6 5.6.25-0ubuntu0.15.04.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1485380/+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 1470056] Re: openstack-dashboard-ubuntu-theme dpkg error on Ubuntu 15.04
Hi Marc Are you still seeing this issue? I can't reproduce an install failure on a fresh 15.04 install - but its entirely possible its due to something else in your install conflicting with the dashboard as the install scripts have to collect and compress static assets such as css and fonts. It would also be helpful to get the actual error message rather than the failure at the end of the install transaction - this would have happened during the configuration step of openstack-dashboard-ubuntu-theme ** Changed in: horizon (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1470056 Title: openstack-dashboard-ubuntu-theme dpkg error on Ubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1470056/+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 1480542] Re: FTBFS: murano-dashboard dependencies have different version numbers in Debian and Ubuntu
Now that the newer murano dashboard is in wily, this is resolved. Marking Fix released. ** Changed in: horizon (Ubuntu) Status: New => Invalid ** Changed in: murano-dashboard (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1480542 Title: FTBFS: murano-dashboard dependencies have different version numbers in Debian and Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1480542/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting
What I don't get is why the other tests aren't failing too, they all start containers too and so should hit the exact same failure. Why one of the last tests is the one hanging just doesn't make sense to me. Anyway, looks like there's a way for us to reproduce this and look into it. It may well be a kernel/apparmor regression after all. -- 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/1504781 Title: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1501772] Re: Metadata proxy process errors with binary user_data
Reviewed: https://review.openstack.org/233136 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=118a76fd651c19ad098cdee9d0a122a00ddc4e3b Submitter: Jenkins Branch:stable/kilo commit 118a76fd651c19ad098cdee9d0a122a00ddc4e3b Author: Ihar HrachyshkaDate: Thu Oct 1 17:13:25 2015 +0200 metadata: don't crash proxy on non-unicode user data We attempt to log every successful metadata response with LOG.debug. But as per oslo.log docs [1], we should make sure that what we pass into the library is unicode. Http.request returns a tuple of Response object and a string, which is bytes in Python 2.x [2]. That's why we need to convert the response content to unicode before passing it into oslo.log. To achieve it, we utilize encodeutils.safe_decode with 'replace' errors handling strategy, so that we don't get exceptions on input that does not conform unicode. For the unit test case, we pass a string that is not expected to convert to unicode with errors='strict' strategy or similar, and check that we still don't crash. While at it, we remove a check for the number of log calls being triggered, because it's something that we should avoid validating in test cases, and it cannot trigger a real bug. The mock that was used to count the number would also hide the bug that we try to reproduce. Note that the bug does not require debug to be set because the crash occurs before oslo.log machinery decides it should not log the message. [1]: http://docs.openstack.org/developer/oslo.log/usage.html#no-more-implicit-conversion-to-unicode-str [2]: http://bitworking.org/projects/httplib2/doc/html/libhttplib2.html#httplib2.Http.request Conflicts: neutron/agent/metadata/namespace_proxy.py neutron/tests/unit/agent/metadata/test_namespace_proxy.py Closes-Bug: #1501772 Change-Id: I6a32c40ff117fae43913386134c8981539697ce8 (cherry picked from commit 80e3d9be4923ecad17377b1d15c8392b8a43dac6) ** Tags added: in-stable-kilo -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1501772 Title: Metadata proxy process errors with binary user_data To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1501772/+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 1505001] [NEW] walinuxagent lacks upstart support for wily
Public bug reported: The current version of walinuxagent in wily lacks support for an upstart job. It should suoport both upstart and systemd. ** Affects: walinuxagent (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1505001 Title: walinuxagent lacks upstart support for wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1505001/+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 1505001] Re: walinuxagent lacks upstart support for wily
The update from 2.0.14 to 2.1.1 in Wily dropped the upstart job and assumes systemd. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1505001 Title: walinuxagent lacks upstart support for wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1505001/+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 1504496] Re: package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Maybe, it's kinda hard to tell as the needed information isn't present in either bug report. -- 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/1504496 Title: package lxc 1.1.4-0ubuntu0.1 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/lxc/+bug/1504496/+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 1445914] Re: Secure web socket proxy does not work in Apache 2.4.7
** Changed in: apache2 (Ubuntu Trusty) Importance: Undecided => Medium ** Tags removed: verification-needed ** Tags added: trusty verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1445914 Title: Secure web socket proxy does not work in Apache 2.4.7 To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1445914/+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 1484268] Re: MAAS not auto-detecting/auto-entering credentials for HP Proliant ML310E G8 V2 server
** Changed in: maas Importance: Undecided => Medium ** Changed in: maas (Ubuntu) Importance: Undecided => Medium -- 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/1484268 Title: MAAS not auto-detecting/auto-entering credentials for HP Proliant ML310E G8 V2 server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1484268/+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 1486865] Re: Sync rrdtool 1.5.4-5 (main) from Debian unstable (main)
Hi "The Wily Werewolf (pre-release freeze)" now has version 1.5.4-5. Am I correct in assuming this bug can be closed, now? https://bugs.launchpad.net/ubuntu/+source/rrdtool -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rrdtool in Ubuntu. https://bugs.launchpad.net/bugs/1486865 Title: [FFE] Sync rrdtool 1.5.4-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rrdtool/+bug/1486865/+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 1505001] Re: walinuxagent lacks upstart support for wily
This bug was fixed in the package walinuxagent - 2.1.1-0ubuntu2 --- walinuxagent (2.1.1-0ubuntu2) wily; urgency=medium * Add support for upstart or systemd (LP: #1505001). -- Ben HowardFri, 09 Oct 2015 13:23:39 -0600 ** Changed in: walinuxagent (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1505001 Title: walinuxagent lacks upstart support for wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1505001/+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 1504200] Re: libecap2 FTBFS due to gcc5 transition
squid3_ 3.3.8-1ubuntu16 resolves this for Squid ** Changed in: squid3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1504200 Title: libecap2 FTBFS due to gcc5 transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1504200/+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 1329015] Re: getdeb repository not work
Is there a way to allow any redirect that squid gets from allowed host? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1329015 Title: getdeb repository not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1329015/+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 1467050] Re: package tomcat7 7.0.56-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for tomcat7 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tomcat7 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1467050 Title: package tomcat7 7.0.56-2 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/tomcat7/+bug/1467050/+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