** Changed in: multipath-tools (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 multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1503286
Title:
On 6 October 2015 at 22:34, Martin Pitt wrote:
> debian/control was a bit messed up -- the Source: stanza can't have a
> "Description:" field. Also, short description shouldn't end with a dot.
> It should also add the LP bug ref to debian/changelog. Attaching a
> debdiff
Thanks! What about the embedded code copes question in comments #68 and
#69.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core, juju-mongodb, gccgo,
Thanks for working on this! Diff looks good (pitti pointed some minor
things out already).
One more thing, please keep the part:
"DPkg::Post-Invoke {"if [ -d /var/lib/update-notifier ]; then touch
/var/lib/update-notifier/dpkg-run-stamp; fi; "
the part of update-notifier that displays a icon
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
I of course meant 'copies' in that last comment.
To clarify what I'm thinking about wrt to juju embedded copies> the
source package can ship various embedded code copies but the archive
build should use archive golang-*-dev packages whenever possible and
where it makes sense (see comment #68 for
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
FYI - After a discussion I'll likely revamp the patches for wily and upstream
the next days.
Until then we will also decide if this is worth SRUs for trusty/vivid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Apologies, the right status was Incomplete.
** Changed in: squid3 (Ubuntu)
Status: Invalid => Incomplete
--
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/1081952
Title:
squid
** Changed in: juju-core (Ubuntu Vivid)
Status: In Progress => Fix Committed
** Changed in: juju-core (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
I certify that juju 1.24.6 is suitable for local charm development and
testing using both trusty and vivid containers. Users of vivid juju
1.24.6 can create new environments in private and public clouds. Vivid
juju 1.24.6 can maintain environments back to 1.18.1 (including 1.22.1
which vivid
Yes, that seems to be the argument. I would like to understand why it
seems to be that many environments are set up with a forwarder that does
not support DNSSEC. (is this by choice? is it a particular vendor, or
old DNS server which does not forward the queries properly?
misconfigured firewall
Sorry folks, but as part of the bug clean up ahead of 16.04 LTS I'm
marking this as invalid because it affects an Ubuntu release which is
now unsupported. If you can still recreate this bug in a supported
release please do open a new bug and we can triage it for consideration
in the 16.04 LTS
Thanks, looks good now! I uploaded this with dropping the subversion
build dependency again, as it's only needed for get-orig-source, not the
actual build.
** Changed in: golang (Ubuntu)
Status: In Progress => Fix Committed
** Package changed: golang (Ubuntu) =>
Uploaded a new version to http://people.canonical.com/~mwh/go-race-
detector-runtime/ with the following changes:
1) Applied your debdiff
2) Changed the package name to golang-race-detector-runtime for consistency
with, well, golang
3) Changed the upstream version number to 0.0+svn229396
4)
** Changed in: net-snmp (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/1245604
Title:
"killall -u snmp" in a pre-install step kills any
Public bug reported:
qemu-slof 20140630+dfsg-1ubuntu1~14.04 from trusty-updates appears to
corrupt memory during some network boot operations, while 20140630+dfsg-
1ubuntu1 (utopic, identical source, but built with gcc 4.9 rather than
trusty's 4.8) works fine.
For example, a "boot net" that
I've gone ahead and manually retraced the crash file.
StacktraceAddressSignature:
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
I also ran into that problem on 15.10 beta.
--
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/1457957
Title:
puppet uses upstart for service status checks in vivid
To manage
** Tags removed: need-duplicate-check
--
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/1503608
Title:
package mysql-server-5.6 5.6.19-0ubuntu0.14.04.1 [modified:
Public bug reported:
After upgrading Ubuntu from LTS to 15.04, spamassassin daemon does not
start anymore because it does not have a proper systemd configuration.
Attempts to enable it using `systemctl enable spamassassin` do also
fail.
root@atlas:/var/log# systemctl status -l
Need a reproducer for the mongodb packaging task please.
** Changed in: mongodb (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1471237
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
** Bug watch added: Debian Bug tracker #781257
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781257
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781257
Importance: Unknown
Status: Unknown
** Package changed: debian => net-snmp (Debian)
--
You
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
*** This bug is a duplicate of bug 1348972 ***
https://bugs.launchpad.net/bugs/1348972
** This bug has been marked a duplicate of bug 1348972
Default address space limit is too small for some PAM modules
--
You received this bug notification because you are a member of Ubuntu
Server
As far as I can see at least in wiley
Apache/SizeLimit.pm
Apache/SizeLimit/Core.pm
Apache2/SizeLimit.pm
are now all included. From utopic on even the liblinux-pid-perl is
included as a package, but is still not listed as a dependency in
libapache2-mod-perl - but no liblinux-pid-perl for trusty
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
Specifically, ubuntu-minimal depends on gpg, so it is not supported in
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
** Changed in: openvpn (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 1501217
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and
Setting Importance to High as this seems to be quite important in not
breaking this, but I need to spend my time working on packages in main
and this package is in universe. Is there anyone who can help with
looking after asterisk in Ubuntu?
** Changed in: asterisk (Ubuntu)
Importance: Medium
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Ubuntu's PHP packaging is mostly derived from Debian. Does this affect
Debian as well? If so, there should be a bug filed in Debian for this
issue.
** Tags added: needs-upstream-report
** Changed in: php5
** Tags removed: severity-critical
** Tags added: severity-medium
--
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/1496210
Title:
multipath-tools lacks the default settings
Public bug reported:
I just tried to install mysql-server-5.6, it asked for root-password
twice and then said it could not set the root password, then dpkg failed
to start mysql (invoke-rc.d: initscript mysql, action "start" failed.).
Now apt wants to finish the broken mysql-installation
So it sounds like the bug is really that DNSSEC is enabled with
automatic keys (note that I don't actually know what that means) and the
reporter thinks that it shouldn't be because of his use case where this
default breaks things?
** Summary changed:
- DNSSEC should be disabled in MAAS by
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: net-snmp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
You have been subscribed to a public bug by Robie Basak (racb):
There is an inconsistency in the libapache2-mod-perl2 (2.0.5-2) package
in oneiric. Apache2::SizeLimit consists of
Apache/SizeLimit.pm
Apache/SizeLimit/Core.pm
Apache2/SizeLimit.pm
plus manpages.
Only Apache2/SizeLimit.pm is
The Debian bug was fixed in 2.0.7-1 and Trusty is on
2.0.8+httpd24-r1449661-6ubuntu2, so presumably this has been fixed and
now affects Precise only.
** Also affects: libapache2-mod-perl2 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661370
Importance: Unknown
Status:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It sounds like this happens after local changes involving hardening,
then? Could you please narrow it down to a specific series of steps
after which spamassassin/sa-compile would reasonably be expected to
work,
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This affects Trusty only since Vivid has 5.6.24, so marking Fix Released
and creating a Trusty task.
In Trusty MySQL 5.6 is in universe and is community support only (it was
a preview; 5.5 remains in main).
--- Comment From mauri...@br.ibm.com 2015-10-07 11:30 EDT---
Lowering priority.
We're already customizing multipath.conf anyway, and this shouldn't get in the
way of other, more serious ship bugs for Canonical.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Hi,
I had a fresh 15.10 beta install and have thrown out iptables in favour
of nftables.
Unfortunately, apt removed the docker.io package as well, since it
depends on iptables.
Shouldn't docker.io be able to deal solely with nftables without the
need for iptables?
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Thank you for your report.
Automatic migration from MariaDB 10.0 to MySQL 5.6 is currently not
supported, so sorry that this isn't something that we can fix right now.
You will need to fix your database manually.
** Tags added: mysql-packaging-policy
** Changed in: mysql-5.6 (Ubuntu)
Thanks Christian! Some remarks:
- The introduction of data/get-motd-updates-available seems like an
unnecessary indirection to me. Instead of checking the executability of
that and run it, debian/90-updates-available could just directly do
cat /var/lib/update-notifier/updates-available
Public bug reported:
In the wily test-rebuild [1] python-pysaml2 seems to fail to build due
to multiple errors and failures in the unit tests. The log:
= test session starts ==
platform linux2 -- Python 2.7.10 -- py-1.4.30 -- pytest-2.7.2
** Description changed:
+ [Workaround]
+
+ ssh -O exit hostname # this will kill all ssh connection to that host
+ ssh-copy-id username@hostname # now it works because it's the first connection
+ # continue using ssh as normal.
+
+ Thanks to Ruben Laguna (ecerulm) in comment 7.
+
+ [Original
Actually I found the way to fix it :
+ I had to remove whatever (sorry i don't remember) lock file in /var/...
+ force apt-get install
+ Launch mysql in safe mode
+ remove the plugins defined in the user table
+ restart mysql
The last steps are here :
Laurent,
Thank you for your reply.
> I guess that Ubuntu systems with ntp installed would boot a little
faster if ntp was not doing useless work by getting started before the
network is fully up.
That's reasonable, though then this bug should be of low importance I
think, as the impact to users
Same output if I do
sudo apt-get install squid-deb-proxy-client
apport-collect 1501217
I may have filed it against the wrong package? But
apt-cache show squid-deb-proxy-client|grep Source
Source: squid-deb-proxy
so huh? bug in apport?
I'm using Ubuntu 14.04 LTS.
** Changed
apport-collect says
Package squid-deb-proxy not installed and no hook available,
ignoring
*** Updating problem report
No additional information collected.
because of course.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
Specifically installing python-beautifulsoup works for me on Trusty.
If
Importance: Low since this is an unusual user configuration which I
don't think is likely to affect many users.
It might be worth testing the latest upstream release and reporting
upstream if it is affected.
** Summary changed:
- irqbalance crashes
+ irqbalance crashes when CPUs are taken
What is the task for multipath-tools here for, please?
** Changed in: multipath-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Here the bigger, but more architecturally complete solution for
wily (which is actually identical at this time).
Summary:
- move the actual updating part out of the pam based trigger completely (avoids
slowdown)
- pam based motd now only prints the cached info (if existing)
- hook into apt with
> Can you explain why this is actually a problem please?
I guess that Ubuntu systems with ntp installed would boot a little
faster if ntp was not doing useless work by getting started before the
network is fully up.
> Won't timesyncd suffice on a desktop that uses NetworkManager now?
Perhaps,
** Patch added: "Enhanced fix for Wily and Upstream"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+attachment/4487279/+files/wily_and_dev_package.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the
Looking at
http://reports.vapour.ws/releases/issue/559694bd749a5660bd8b8f07
running the unit tests with the race option is best at triggering a bad record
mac, though running in lxc might also be a factor. Unpack the juju-core tarfile
cd src/github.com/juju/juju
go test -race
Hello Andreas, or anyone else affected,
Accepted ceph into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ceph/0.80.10-0ubuntu1.14.04.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags removed: landscape-release-29
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1477225
Title:
ceph-radosgw restart fails
To manage notifications about this bug go to:
Hello Adam, or anyone else affected,
Accepted ceph into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ceph/0.80.10-0ubuntu1.14.04.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
package spamassassin 3.4.0-1ubuntu2.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status
2
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: spamassassin 3.4.0-1ubuntu2.1
ProcVersionSignature: Ubuntu
Looks like we can get this fixed without pulling in the new upstream
version with this:
https://github.com/rohe/pysaml2/commit/5035a58137f7ba5ad79e4e52703b789b2a726955
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-pysaml2 in
Re: #32
Cups and other processes expect to be able to assign their configured ports,
But rpcbind / portmap etc. assign ports randomly.
e.g.: http://www.linuxproblem.org/art_13.html
This bug has just hit me, with a deadline to print and no way to reboot the
computer without losing work.
It
I was able to assign a PCI device to a VM via PCI pass through/vt-d with
Wily/4.2 after adding 'intel_iommu=on' to the kernel cmdline. Can you please
re-test with this option and the latest kernel to see if this works now?
Thanks
** Changed in: libvirt (Ubuntu)
Status: Triaged =>
Reading the comments this sounds like it might have been an issue in the
Jaunty/9.04 version of virt-manager but fixed in Karmic/9.10. Jaunty
would be no longer supported, so I close this as fix-released.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Released
--
You received
Hello Anders, or anyone else affected,
Accepted openhpi into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openhpi/2.14.1-1.3ubuntu2.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: oslo.messaging (Ubuntu Utopic)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1448650
Title:
rpc.server do not
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: irqbalance (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
** Summary changed:
- irqbalance should not run in container
+ irqbalance should not run in container - add systemd unit
** Tags added: systemd-boot
** Tags removed: systemd-boot
** Tags added: systemd
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Hello Seth, or anyone else affected,
Accepted juju-core into vivid-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/1.24.6-0ubuntu1~15.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Branch linked: lp:ubuntu/vivid-proposed/openhpi
--
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/1488453
Title:
Package postinst always fail on first install when using systemd
To
Hello Matthias, or anyone else affected,
Accepted python-greenlet into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/python-
greenlet/0.4.2-1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
There is a systemd unit here -
https://github.com/Irqbalance/irqbalance/tree/master/misc
In my tests it no longer shows up in systemd-analyze blame (saves 300ms -
500ms), but still runs, to try:
sudo cp misc/irqbalance.env /etc/default/irqbalance.env
sudo cp misc/irqbalance.service
Hello Curtis, or anyone else affected,
Accepted juju-core into vivid-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/1.24.6-0ubuntu1~15.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Branch linked: lp:ubuntu/trusty-proposed/python-greenlet
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-greenlet in Ubuntu.
https://bugs.launchpad.net/bugs/1451537
Title:
python-greenlet fails to build in trusty with
** Tags removed: systemd
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1454273
Title:
irqbalance should not run in container - add systemd unit
To
Hello Stéphane, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.1.4-0ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1503034
Title:
Autofs 5.1.1-1ubuntu2 crashes with segfault on startup
To manage notifications about this bug go
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
Response to James' inquiries in comment #67:
* juju team: can you comment on the package breakdown? For items
requiring further discussion, it might be worthwhile understanding how
often you are updating the embedded package (useful for the SRU
question, below)
On average 50% of the package
** Also affects: rpcbind (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rpcbind in Ubuntu.
https://bugs.launchpad.net/bugs/304393
Title:
cups: 127.0.0.1:631 - Address already in
At least parts of the failures are due to the new pymongo, which for
instance deprecated the 'Connection' object. Looking if we can easily
distro-patch it to work. Debian also doesn't have it changed for the new
pymongo. Maybe we could sync python-pysaml2 3.0.0-1 from experimental?
Looking into
Reviewed: https://review.openstack.org/227911
Committed:
https://git.openstack.org/cgit/stackforge/ospurge/commit/?id=b97992d5099ce8aa9371a5b78461d11faacbea5a
Submitter: Jenkins
Branch:master
commit b97992d5099ce8aa9371a5b78461d11faacbea5a
Author: Yves-Gwenael Bourhis
92 matches
Mail list logo