** Patch added: "squid3_3.3.8-1ubuntu6.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+attachment/4493997/+files/squid3_3.3.8-1ubuntu6.4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in
** Patch added: "squid3_3.1.19-1ubuntu3.12.04.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+attachment/4493998/+files/squid3_3.1.19-1ubuntu3.12.04.4.debdiff
** Tags removed: needs-upstream-report
** Tags added: patch precise trusty
--
You received this bug
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
The fix is the following:
$ git describe --contains 6f30b7e37a8239f9d27db626a1d3427bc7951908
v4.0-rc1~1^2
I thought this was going to be queued up for stable, but doesn't look like
that happened.
If this still affects you in 3.13, 3.16, I can backport this patch. Let me know.
--
You received
** Summary changed:
- squid3 logrotate fails when squid is not running
+ [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
Michael Terry [2015-10-13 17:33 -]:
> That seems more packaging-friendly than requiring a bunch of one-line
> dep8 tests to trigger a rebuild test. Especially if we have to add a
> delta to get it.
autodep8 can "synthesize" a debian/tests/control for a group of
related packages. It already
On Tue, Oct 13, 2015 at 05:33:37PM -, Michael Terry wrote:
> Though in this respect, golang isn't so different than C libraries, where
> an unexpected API update or library bug can cause ftbfs in
> reverse-depends.
It is different, because:
- reverse-dependencies don't have to be rebuilt
** Description changed:
[Impact]
Squid 3.1.19-1ubuntu3.12.04.3 on Precise and 3.3.8-1ubuntu6.3 on Trusty
do not clean up its PID file, causing logrotate to spit out an error
each night when cron runs it.
The underlying issue here is that the upstart script does not wait long
Public bug reported:
1. Description: Ubuntu 15.04
Release:15.04
2. init:
Installed: 1.22ubuntu11
Candidate: 1.22ubuntu11
Version table:
*** 1.22ubuntu11 0
500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
3. Expected the
** Description changed:
- Squid3 on Precise does not clean up its PID file, causing logrotate to
- spit out an error each night when cron runs it. This is on a server where
- we want squid3 installed and ready to go but not running by default.
+ [Impact]
- 0 root@rackspace:/etc/mysql#start
@Li Chengyuan, thank you for the clarification. So just formally I will
mark the Precise task of this report as invalid (since the qemu in
Precise is actually a different source package and also not affected as
far as I can tell). I will need to figure out how to ensure this fix is
also pulled
You have been subscribed to a public bug by Robie Basak (racb):
The systemd service generated from /etc/init.d/apache2 via systemd-sysv-
generator contains the line
RemainAfterExit=yes
causing systemd to ignore crashes of the service. In order to reproduce
this, add a non-existing address to
The attachment "lpstat-return-number-of-jobs.patch" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user
stub@aargh:~$ sudo systemctl status lxc
● lxc.service - LXC Container Initialization and Autoboot Code
Loaded: loaded (/lib/systemd/system/lxc.service; enabled; vendor preset:
enabled)
Active: active (exited) since Mon 2015-10-12 16:57:31 ICT; 20h ago
Process: 1190
** Changed in: qemu (Ubuntu Vivid)
Status: New => In Progress
** Changed in: qemu (Ubuntu Trusty)
Status: New => In Progress
** Changed in: qemu (Ubuntu Trusty)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: qemu (Ubuntu Vivid)
Assignee: (unassigned) =>
This bug was fixed in the package heat - 1:5.0.0~rc2-0ubuntu1
---
heat (1:5.0.0~rc2-0ubuntu1) wily; urgency=medium
* New upstream release candidate for OpenStack Liberty.
* Don't clean heat.egg-info ensuring that non-py resources actually
get installed (LP: #1505444).
--
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1488962
Title:
systemd does not notice when apache2 service fails
To manage notifications about this bug
Public bug reported:
Ubuntu release: 14.04.3 LTS
munin-plugins-core version: 2.0.19-3
The returned job count is always zero because a variable assignment is
missing from the script.
** Affects: munin (Ubuntu)
Importance: Undecided
Status: New
** Patch added:
You have been subscribed to a public bug by Robie Basak (racb):
Ubuntu release: 14.04.3 LTS
munin-plugins-core version: 2.0.19-3
The returned job count is always zero because a variable assignment is
missing from the script.
** Affects: munin (Ubuntu)
Importance: Undecided
Status:
You have been subscribed to a public bug by Robie Basak (racb):
wily dist-upgrade caused this failure.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: nut-client 2.7.1-1ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
That might be something we want to SRU, if somebody is interested it
would be useful to have a testcase description (see
https://wiki.ubuntu.com/StableReleaseUpdates)
** Changed in: samba (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
That's fixed in the current version in vivid, that might be something we
want to backport to trusty, if somebody is interested it would be useful
to have a testcase description (see
https://wiki.ubuntu.com/StableReleaseUpdates)
** Changed in: samba (Ubuntu)
Status: Triaged => Fix Released
That's fixed in the current version
** Changed in: samba (Ubuntu)
Importance: Undecided => High
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
Thanks. I can see this in 4.11-0ubuntu1 in Trusty and a slightly changed
but similar typo in 4.18-0ubuntu1 in Wily.
** Also affects: pollen (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: pollen (Ubuntu)
Status: New => Triaged
** Changed in: pollen (Ubuntu)
That might be something we want to backport to trusty, if somebody is
interested it would be useful to have a testcase description (see
https://wiki.ubuntu.com/StableReleaseUpdates)
** Changed in: samba (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification
Jeffrey,
Thank you for working on this.
The debdiff looks good but will need to wait until the SRU in bug
1445914 has cleared before it can be uploaded. Can I suggest though that
the message in debian/changelog be made more appropriate for Ubuntu
users and developers, rather than a blanket copy
The new version is in vivid and wily
** Bug watch added: Samba Bugzilla #9570
https://bugzilla.samba.org/show_bug.cgi?id=9570
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=9570
Importance: Unknown
Status: Unknown
** Changed in: samba (Ubuntu)
Thanks, is that fixed in newer upstream version?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1388091
Title:
winbindd does not provide geocs to libnss_winbind in ad configuration
** Also affects: apache2 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: apache2 (Ubuntu)
Status: New => Fix Released
** Changed in: apache2 (Ubuntu Trusty)
Status: New => Triaged
** Changed in: apache2 (Ubuntu Trusty)
Importance: Undecided => Medium
Public bug reported:
Which leads to empty machine names see
https://bugzilla.samba.org/show_bug.cgi?id=10896, that's fixed in the
current version but we should SRU the fix
* Impact
Some samba machines have no names
* Test Case
- install samba
- edit smb.conf and set netbios name =
duplicate
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1505588
Title:
netbios name truncating doesn't work
To manage notifications about this bug go to:
Public bug reported:
Which leads to empty machine names see
https://bugzilla.samba.org/show_bug.cgi?id=10896, that's fixed in the
current version but we should SRU the fix
* Impact
Some samba machines have no names
* Test Case
- install samba
- edit smb.conf and set netbios name =
You have been subscribed to a public bug by Robie Basak (racb):
ubuntu@keeton:~$ lsb_release -rc
Release:14.04
Codename: trusty
ubuntu@keeton:~$ dpkg-query -W pollen
pollen 4.11-0ubuntu1
ubuntu@keeton:~$ _
pollen does not start on boot, due to an error in the upstart config:
You have been subscribed to a public bug by Robie Basak (racb):
If configured to do so, strongSwan will cache CRLs to /etc/ipsec.d/crls
but AppArmor blocks the creation of the file. Here is the relevant
syslog line:
kernel: [400994.988829] audit: type=1400 audit(1444649911.842:37):
That might be something we want to backport to trusty, if somebody is
interested it would be useful to have a testcase description (see
https://wiki.ubuntu.com/StableReleaseUpdates)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba
** Changed in: apache2 (Ubuntu)
Importance: Undecided => Medium
--
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/1488962
Title:
systemd does not notice when apache2 service fails
To
@stub - ok so yours all look ok.
--
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/1490110
Title:
package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
installed
** Changed in: strongswan (Ubuntu)
Importance: Undecided => Medium
--
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/1505222
Title:
strongSwan AppArmor prevents CRL caching
To manage
Erk, sorry -- wrong bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core, juju-mongodb, gccgo, golang
To manage notifications
Hi,
I'm hoping to fix this with a cgmanager patch to tasks to escape
'init.scope'. I don't want the list of escapable cgroups to keep
growing, so we'll need to come up with something better long-term.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
@Steve: I just tried this on current wily-proposed with
http://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#obconf :
/etc/apt/preferences.d/01autopkgtest
Package: obconf
Pin: release a=wily-proposed
Pin-Priority: 900
Package: *
Pin: release a=wily
I think implementing autodep8 for go packages is a must.
http://anonscm.debian.org/cgit/collab-maint/autodep8.git/tree/README.md
At least to build the reverse dependencies so that new uploads are
blocked in -proposed until all build failures are resolved.
--
You received this bug notification
Public bug reported:
As per the wily test-rebuild [1], it seems that the latest python-
glance-store is failing due to broken unit tests. Seems relatively easy
to fix. Part of the log:
==
FAIL:
*** This bug is a duplicate of bug 545830 ***
https://bugs.launchpad.net/bugs/545830
** This bug has been marked a duplicate of bug 545830
403 error when using a non-cached repository
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
apt-cacher-ng has its own avahi support now and works happily with
squid-deb-proxy-client for discovery.
--
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/529897
Title:
Please
Patch has been provided
** Changed in: multipath-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1503286
Title:
ISST-LTE:
> The workaround is to apt-get purge squid-deb-proxy-client.
That is not a workaround, that is the proper "fix".
Squid-deb-proxy-client is essentially simply a package that installs a
configuration snippet /etc/apt/apt.conf.d/30autoproxy so that any call
to the network will be proxied to a local
** Summary changed:
- systemd 226-2 (debian sid) breaks lxc-attach
+ systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach
** Package changed: systemd (Ubuntu) => lxcfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
I get the following error when running the discovery script on the
command line.
$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection
refused
Public bug reported:
Running "openstack help" to display help (version 1.7.0) shows available
commands until it reaches commands for sahara:
dataprocessing data source create Creates data source
dataprocessing data source delete Delete data source
dataprocessing data source list Lists
** Changed in: landscape/release-29
Status: Fix Committed => Fix Released
** Changed in: landscape
Status: Fix Committed => Fix Released
** Changed in: landscape
Milestone: 15.08 => 15.07
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This bug happens to me to when upgrading from 15.04 to willy vsftp
3.0.2-20ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/1486007
Title:
package vsftpd 3.0.2-18ubuntu1
I'm going to leave this as incomplete until we have a recipe for how to
reproduce.
--
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/1490110
Title:
package lxc 1.1.3-0ubuntu1 failed to
** Changed in: golang-go.crypto (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
On Tue, 2015-10-13 at 11:00 +, Robie Basak wrote:
> Fix -D[efined] or [d] variables lifetime across restarts. This
> fixes incorrect processing of configuration files on reload (LP:
> #1504354).
>
> If you let me know that you're happy with that text then I can just
> change it when I upload
Since Robie suggested that it is a local config problem:
$ diff -u vsftpd.conf.dpkg-old vsftpd.conf
--- vsftpd.conf.dpkg-old2015-02-20 15:52:29.406670979 +0100
+++ vsftpd.conf 2015-03-05 17:18:21.0 +0100
@@ -11,7 +11,7 @@
#
# Run standalone? vsftpd can run either from an inetd
Public bug reported:
steps to reproduce:
# echo GIBBERISH >> /etc/nginx/nginx.conf
# service nginx restart
* Restarting nginx nginx [fail]
# echo $?
0
very nasty when combined with ansible/other configuration management
tools: broken conffiles come unnoticed.
ProblemType: Bug
Uploaded to wily, as well as backports in ppa:pollen/ppa.
** Changed in: pollen (Ubuntu)
Status: Triaged => Fix Committed
--
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/1505473
** Branch linked: lp:pollen
--
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/1505473
Title:
pollen does not start on boot
To manage notifications about this bug go to:
golang-github-bmizerany-assert is mostly good, but needs a tiny fix:
- debian/control should have Built-Using: ${misc:Built-Using} on the
golang-github-bmizerany-assert-dev package
** Changed in: golang-github-bmizerany-assert (Ubuntu)
Status: New => Incomplete
--
You received this bug
Doko, I just noticed your comment about dep8 tests. I agree that some
sort of mechanism to avoid ftbfs would be good. Though in this respect,
golang isn't so different than C libraries, where an unexpected API
update or library bug can cause ftbfs in reverse-depends. We use dep8
tests as best
** Branch linked: lp:ubuntu/wily-proposed/pollen
--
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/1505473
Title:
pollen does not start on boot
To manage notifications about this bug go
*** This bug is a duplicate of bug 1413555 ***
https://bugs.launchpad.net/bugs/1413555
** This bug has been marked a duplicate of bug 1413555
init script fails with error code 0 when configuration test doesn't pass
--
You received this bug notification because you are a member of Ubuntu
golang-github-bmizerany-pat is good; approved.
** Changed in: golang-github-bmizerany-pat (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
golang-check.v1 looks good; approved.
** Changed in: golang-check.v1 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
Thank you for reporting this bug to Ubuntu.
I've tried recreating this bug on an up-to-date version of wily and
cloud-archive:liberty-proposed, and was unable to recreate. Please
upgrade to the latest version and re-test. If the bug is still
reproducible, please let us know.
** Changed in:
** Changed in: neutron
Status: Incomplete => Won't Fix
--
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/1236439
Title:
switch to use hostnames like nova breaks upgrades of
Doh, I forgot to add the package version. I'm using 1.7.0-1~cloud0 from
the Liberty staging PPA. No updates available.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-openstackclient in Ubuntu.
** Changed in: snapcraft
Status: New => Invalid
--
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/1501651
Title:
ARM chroot issues: fatal error: rt_sigaction failure
To manage
golang-go.net-dev build-depends on golang-x-text-dev (which didn't have
a MIR section here -- I've added a bug task for it now anyway).
But golang-x-text isn't ready yet:
- It is ftbfs due to test failures. That should be looked at.
- It needs a team bug subscriber.
** Changed in: golang-x-text
** Changed in: glance/kilo
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
https://bugs.launchpad.net/bugs/1447215
Title:
Schema Missing kernel_id, ramdisk_id causes
dh-golang is fine; approved.
** Changed in: dh-golang (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
golang-go.net-dev though looks good, approved. There is an oddity in
Debian around it being removed from testing [1], but that appears to be
a mistake? I don't see any bugs filed against it, there was no removal
hint, and the package tracker is giving inconsistent statuses/versions.
In any case,
golang-juju-loggo needs some fixes:
- It's missing Built-Using: ${misc:Built-Using}
- Its name is wrong [1]. It should be golang-github-juju-loggo and
golang-github-juju-loggo-dev. We should fix in Ubuntu so that if it's ever
packaged in Debian, we'll be aligned.
[1]
golang-go-dbus has one blocking problem and I've got a few minor concerns:
- Needs to use Built-Using
- It's about to be removed from Debian testing due to its dependency on
golang-gocheck. Not an immediate problem for us, but since we want to port
away from gocheck anyway, maybe we can help
Doko, I did some of the leafier modules here. I figure you'd be the
best person for some of the core ones. If you're too loaded, bounce
back to me.
** Changed in: golang (Ubuntu)
Status: Incomplete => New
** Changed in: golang (Ubuntu)
Assignee: (unassigned) => Matthias Klose
** Also affects: golang-x-text (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-go.net-dev in Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core,
This bug was fixed in the package pollen - 4.20-0ubuntu1
---
pollen (4.20-0ubuntu1) wily; urgency=medium
* debian/pollen.upstart: LP: #1505473
- remove typo in the upstart config which was preventing the service from
starting
* rebuild the packages for upload
-- Dustin
** Changed in: nova/kilo
Status: New => Fix Released
--
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
Public bug reported:
There seem to be a conflict between the package python-networkx and
python3-networkx
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: python-networkx (not installed)
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
*** This bug is a duplicate of bug 1413555 ***
https://bugs.launchpad.net/bugs/1413555
NACK on the patch.
The proposed patch is not the correct approach to fix this or the master
bug. Debian has fixes, I'll dig them up.
--
You received this bug notification because you are a member of
Is this still open against the 14.04.1 LTS kernel?
Thanks
--
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/1292234
Title:
qcow2 image corruption on non-extent filesystems (ext3)
To
82 matches
Mail list logo
