[Bug 1503286] Re: ISST-LTE: Boot of Ubuntu15.10 lpar fails: "mounting /dev/sdn2 on /root failed: Device or resource busy" [multipath]

[Breno Leitão]

** 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:
  ISST-LTE: Boot of Ubuntu15.10 lpar fails: "mounting /dev/sdn2 on /root
  failed: Device or resource busy" [multipath]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1503286/+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 1487010] Re: please upload new package to reenable go's race detector on wily

[Michael Hudson-Doyle]

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 for this, please apply.

Will do thanks.

> However these are blockers:
>
>  - an upstream version of "229396" is huge, possibly not monotonous (is
> that a git commit ref?), and hard to make higher if this is more  like a
> git commit hash than a monotonously increasing number.

It's a subversion revision number. I guess 0.0+svn229396 would be
better?

>  - There is also no indication where the orig.tar.gz came from -- this
> should either come from a documented upstream release tarball URL,
> usually with debian/watch; or should get a "debian/rules get-orig-
> source" rule or at least some debian/README.Source that documents how to
> get it or any newer version.

Ah yes, fair points.

>
> ** Patch added: "packaging fixes"
>
> https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1487010/+attachment/4485683/+files/go-race-detector-runtime.packagingfixes.debdiff
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1487010
>
> Title:
>   please upload new package to reenable go's race detector on wily
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1487010/+subscriptions

-- 
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/1487010

Title:
  please upload new package to reenable go's race detector on wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1487010/+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 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

[Jamie Strandboge]

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, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+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 525674] Re: apt-check hangs, preventing login via SSH

[Michael Vogt]

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 (used in xfce iirc) will 
depend on this file, it uses inotify to know reliable when apt was finished.

-- 
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/525674

Title:
  apt-check hangs, preventing login via SSH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+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 1500916] Re: [needs-packaging] 1.24.6 is not packaged in Vivid

[Curtis Hovey]

** 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 Vivid do not get a downgrade that looses
  bug fixes.
  
  See bug 1481556 for the history of placing juju-core 1.24.6 into Wily.
  
  Fixing this bug fixes bug 1497087
  
  [SRU Information]
  
  juju-core has a stable release exception in 
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including 
for major version
  updates.
  
  [Vivid Fix]
  
  [sinzui] Prepare source package, and diffs: DONE
  [rbasak] Review package: DONE
  
  [Pre-QA tasks]
  
  [rbasak] Upload to vivid (vivid-proposed): DONE
  
  [QA Status]
  
  Since there are multiple verifications required, they are listed here as a 
work
  item whiteboard status type thing rather than try and track them in a single
  tag. Please do not mark verification-done or remove block-proposed until all
  following items have passed. If any of these items fail, this bug should be
  marked verification-failed immediately.
  
  [sinzui] Upstream release process complete: DONE
  [sinzui] Upstream QA test against Vivid: DONE
  
  Manual tests required:
  
  [sinzui] Test juju-quickstart against vivid-proposed: DONE
  [sinzui] Test juju-deployer against vivid-proposed: DONE
- [sinzui] Test client and cloud server upgrade from main/updates: TODO
+ [sinzui] Test client and cloud server upgrade from main/updates: DONE
  [sinzui] Test client manual bootstrap and add-machine: DONE

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1500916

Title:
  [needs-packaging] 1.24.6 is not packaged in Vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1500916/+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 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

[Jamie Strandboge]

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 the list). For example, the
archive build of juju should use golang-go.crypto-dev, but juju source
package may contain code.google.com/p/go.crypto if
code.google.com/p/go.crypto is needed for some other non-archive build.

If both are legitimately needed (and there should be justification for
that) to support different clients, then the archive build should use
golang-go.crypto-dev from the archive and embed
code.google.com/p/go.crypto (justification being, all archive builds
should use golang-go.crypto-dev and only juju needs
code.google.com/p/go.crypto).

I need someone can go through that list in comment 68 and comment on it.
Then anything that should be broken out of the juju source (ie, it is
not juju-specific) should be into golang-*-dev packages and the archive
build should use them and any other existing golang-*-dev packages from
the archive.

-- 
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, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+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 1500916] Re: [needs-packaging] 1.24.6 is not packaged in Vivid

[Curtis Hovey]

** 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 Vivid do not get a downgrade that looses
  bug fixes.
  
  See bug 1481556 for the history of placing juju-core 1.24.6 into Wily.
  
  Fixing this bug fixes bug 1497087
  
  [SRU Information]
  
  juju-core has a stable release exception in 
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including 
for major version
  updates.
  
  [Vivid Fix]
  
  [sinzui] Prepare source package, and diffs: DONE
  [rbasak] Review package: DONE
  
  [Pre-QA tasks]
  
  [rbasak] Upload to vivid (vivid-proposed): DONE
  
  [QA Status]
  
  Since there are multiple verifications required, they are listed here as a 
work
  item whiteboard status type thing rather than try and track them in a single
  tag. Please do not mark verification-done or remove block-proposed until all
  following items have passed. If any of these items fail, this bug should be
  marked verification-failed immediately.
  
  [sinzui] Upstream release process complete: DONE
  [sinzui] Upstream QA test against Vivid: DONE
  
  Manual tests required:
  
  [sinzui] Test juju-quickstart against vivid-proposed: DONE
- [sinzui] Test juju-deployer against vivid-proposed: TODO
+ [sinzui] Test juju-deployer against vivid-proposed: DONE
  [sinzui] Test client and cloud server upgrade from main/updates: TODO
  [sinzui] Test client manual bootstrap and add-machine: TODO

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1500916

Title:
  [needs-packaging] 1.24.6 is not packaged in Vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1500916/+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 1500916] Re: [needs-packaging] 1.24.6 is not packaged in Vivid

[Curtis Hovey]

** 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 Vivid do not get a downgrade that looses
  bug fixes.
  
  See bug 1481556 for the history of placing juju-core 1.24.6 into Wily.
  
  Fixing this bug fixes bug 1497087
  
  [SRU Information]
  
  juju-core has a stable release exception in 
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including 
for major version
  updates.
  
  [Vivid Fix]
  
  [sinzui] Prepare source package, and diffs: DONE
  [rbasak] Review package: DONE
  
  [Pre-QA tasks]
  
  [rbasak] Upload to vivid (vivid-proposed): DONE
  
  [QA Status]
  
  Since there are multiple verifications required, they are listed here as a 
work
  item whiteboard status type thing rather than try and track them in a single
  tag. Please do not mark verification-done or remove block-proposed until all
  following items have passed. If any of these items fail, this bug should be
  marked verification-failed immediately.
  
  [sinzui] Upstream release process complete: DONE
  [sinzui] Upstream QA test against Vivid: DONE
  
  Manual tests required:
  
  [sinzui] Test juju-quickstart against vivid-proposed: DONE
  [sinzui] Test juju-deployer against vivid-proposed: DONE
  [sinzui] Test client and cloud server upgrade from main/updates: TODO
- [sinzui] Test client manual bootstrap and add-machine: TODO
+ [sinzui] Test client manual bootstrap and add-machine: DONE

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1500916

Title:
  [needs-packaging] 1.24.6 is not packaged in Vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1500916/+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 525674] Re: apt-check hangs, preventing login via SSH

[ChristianEhrhardt]

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.
https://bugs.launchpad.net/bugs/525674

Title:
  apt-check hangs, preventing login via SSH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+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 1081952] Re: squid 3.1.19 external_acl_type fail

[Tiago Stürmer Daitx]

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 3.1.19 external_acl_type fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1081952/+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 1409639] Re: juju needs to support systemd for >= vivid

[Curtis Hovey]

** 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.
https://bugs.launchpad.net/bugs/1409639

Title:
  juju needs to support systemd for >= vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1409639/+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 1500916] Re: [needs-packaging] 1.24.6 is not packaged in Vivid

[Curtis Hovey]

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 currently has). Upgrades of clients and environments from
juju 1.22.1 to 1.24.6 work without need of configuration changes. Vivid
juju 1.24.6 can manually provision environments and add-machines.

** 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 juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1500916

Title:
  [needs-packaging] 1.24.6 is not packaged in Vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1500916/+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 1500683] Re: By default DNSSEC is enabled with automatic keys

[Mike Pontillo]

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 rules?)

There are three possible values for the BIND dnssec-validation option:
'yes', 'no', and 'auto'.

By saying "enabled with automatic keys", we just mean the default value
of "dnssec-validation auto;" in the BIND configuration file.

See also: http://users.isc.org/~jreed/dnssec-guide/dnssec-guide.html
#dnssec-validation-explained

-- 
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/1500683

Title:
  By default DNSSEC is enabled with automatic keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1500683/+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 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer

[Simon Quigley]

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 development cycle.

** Changed in: openssh (Ubuntu)
   Status: Triaged => Invalid

-- 
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/708493

Title:
  Can't login anymore: Read from socket failed: Connection reset by peer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/708493/+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 1487010] Re: please upload new package to reenable go's race detector on wily

[Martin Pitt]

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) => golang-race-detector-runtime
(Ubuntu)

-- 
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/1487010

Title:
  please upload new package to reenable go's race detector on wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-race-detector-runtime/+bug/1487010/+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 1487010] Re: please upload new package to reenable go's race detector on wily

[Michael Hudson-Doyle]

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) Added a get-orig-source target and used it to repack the orig tarball (I 
verified that the file contents are the same as the previous version)

Thanks again for the reviews, feels close now?

-- 
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/1487010

Title:
  please upload new package to reenable go's race detector on wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1487010/+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 1245604] Re: "killall -u snmp" in a pre-install step kills any running snmpd

[Bug Watch Updater]

** 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 running snmpd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1245604/+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 1503929] [NEW] trusty-updates qemu-slof network boot breaks subsequent OpenFirmware operations

[William Grant]

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 performs a TFTP download (even if it
connects but fails, eg. because the file doesn't exist, but not if it
fails to DHCP or connect at all) causes a subsequent "boot cdrom" to
fail. http://paste.ubuntu.com/12710600/ has examples to reproduce the
good and bad cases, no manual DHCP/TFTP setup required.

Other manifestations of memory corruption include a TFTP-booted GRUB
working fine except that the MAC address that GRUB uses for its own TFTP
operations has its last octet replaced with 0xd1. This was originally
noticed when MAAS failed to boot KVM instances, as it assumed the MAC
that GRUB used matched the one that Linux knew about.

Both cases are fixed by using a qemu-slof built with gcc 4.9 instead of
the 4.8-built archive version.

A tcpdump excerpt covering the final TFTP packet loading GRUB itself,
and the first ARP from within GRUB:

  04:01:23.536384 52:54:00:55:40:13 (oui Unknown) > 52:54:00:17:ed:f1 (oui 
Unknown), ethertype IPv4 (0x0800), length 60: 10.10.0.107.2001 > 
10.10.0.2.38623: UDP, length 4
  04:01:23.876989 52:54:00:55:40:d1 (oui Unknown) > Broadcast, ethertype ARP 
(0x0806), length 60: Request who-has 10.10.0.2 tell 10.10.0.107, length 46

** Affects: slof (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: slof (Ubuntu Trusty)
 Importance: High
 Status: Triaged

** Also affects: slof (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: slof (Ubuntu)
   Status: New => Invalid

** Changed in: slof (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: slof (Ubuntu Trusty)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to slof in Ubuntu.
https://bugs.launchpad.net/bugs/1503929

Title:
  trusty-updates qemu-slof network boot breaks subsequent OpenFirmware
  operations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/slof/+bug/1503929/+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 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup

[Brian Murray]

I've gone ahead and manually retraced the crash file.

StacktraceAddressSignature: 
/usr/sbin/automount:11:/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so+1bbcb:/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so+1bc48:/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so+1c50c:/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so+1df87:/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so+e56a:/usr/sbin/automount+15db6:/usr/sbin/automount+166e7:/usr/sbin/automount+172b1:/usr/lib/x86_64-linux-gnu/autofs/lookup_file.so+a253:/usr/sbin/automount+16701:/usr/sbin/automount+17323:/usr/sbin/automount+29378:/usr/sbin/automount+b42e:/usr/sbin/automount+256ac:/lib/x86_64-linux-gnu/libpthread-2.21.so+76aa
StacktraceSource:
 #0  0x7fedfa228bcb in ?? () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 #1  0x7fedfa228c48 in ?? () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 #2  0x7fedfa22950c in ?? () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 #3  0x7fedfa22af87 in defaults_get_ldap_timeout () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 #4  0x7fedfa21b56a in lookup_init () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 #5  0x5626d6cdfdb6 in open_lookup ()
 #6  0x5626d6ce06e7 in ?? ()
 #7  0x5626d6ce12b1 in lookup_nss_read_master ()
 #8  0x7fedfaabb253 in lookup_read_master () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_file.so
 #9  0x5626d6ce0701 in ?? ()
 #10 0x5626d6ce1323 in lookup_nss_read_master ()
 #11 0x5626d6cf3378 in master_read_master ()
 #12 0x5626d6cd542e in main ()
 #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
   [Error: pthread_cond_wait.S was not found in source tree]
 #1  0x5626d6cef6ac in ?? ()
 #2  0x7fedfdf756aa in start_thread (arg=0x7fedfe3ac700) at 
pthread_create.c:333
   [Error: pthread_create.c was not found in source tree]
 #3  0x7fedfd6d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
   [Error: clone.S was not found in source tree]
 #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
   [Error: pthread_cond_wait.S was not found in source tree]
 #1  0x5626d6ce4773 in ?? ()
 #2  0x7fedfdf756aa in start_thread (arg=0x7fedfe38a700) at 
pthread_create.c:333
   [Error: pthread_create.c was not found in source tree]
 #3  0x7fedfd6d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
   [Error: clone.S was not found in source tree]
 #0  0x7fedfa228bcb in ?? () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 #1  0x7fedfa228c48 in ?? () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 #2  0x7fedfa22950c in ?? () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 #3  0x7fedfa22af87 in defaults_get_ldap_timeout () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 #4  0x7fedfa21b56a in lookup_init () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 #5  0x5626d6cdfdb6 in open_lookup ()
 #6  0x5626d6ce06e7 in ?? ()
 #7  0x5626d6ce12b1 in lookup_nss_read_master ()
 #8  0x7fedfaabb253 in lookup_read_master () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_file.so
 #9  0x5626d6ce0701 in ?? ()
 #10 0x5626d6ce1323 in lookup_nss_read_master ()
 #11 0x5626d6cf3378 in master_read_master ()
 #12 0x5626d6cd542e in main ()
StacktraceTop:
 ?? () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 ?? () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 ?? () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 defaults_get_ldap_timeout () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
 lookup_init () from 
/mnt/sec-machines/apport-retrace/usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so


** Changed in: autofs (Ubuntu)
   Status: Incomplete => New

-- 
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 to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+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 1500916] Re: [needs-packaging] 1.24.6 is not packaged in Vivid

[Curtis Hovey]

** 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 Vivid do not get a downgrade that looses
  bug fixes.
  
  See bug 1481556 for the history of placing juju-core 1.24.6 into Wily.
  
  Fixing this bug fixes bug 1497087
  
  [SRU Information]
  
  juju-core has a stable release exception in 
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including 
for major version
  updates.
  
  [Vivid Fix]
  
  [sinzui] Prepare source package, and diffs: DONE
  [rbasak] Review package: DONE
  
  [Pre-QA tasks]
  
  [rbasak] Upload to vivid (vivid-proposed): DONE
  
  [QA Status]
  
  Since there are multiple verifications required, they are listed here as a 
work
  item whiteboard status type thing rather than try and track them in a single
  tag. Please do not mark verification-done or remove block-proposed until all
  following items have passed. If any of these items fail, this bug should be
  marked verification-failed immediately.
  
  [sinzui] Upstream release process complete: DONE
  [sinzui] Upstream QA test against Vivid: DONE
  
  Manual tests required:
  
- [sinzui] Test juju-quickstart against vivid-proposed: TODO
+ [sinzui] Test juju-quickstart against vivid-proposed: DONE
  [sinzui] Test juju-deployer against vivid-proposed: TODO
  [sinzui] Test client and cloud server upgrade from main/updates: TODO
  [sinzui] Test client manual bootstrap and add-machine: TODO

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1500916

Title:
  [needs-packaging] 1.24.6 is not packaged in Vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1500916/+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 1457957] Re: puppet uses upstart for service status checks in vivid

[Hadmut Danisch]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+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 1503608] Re: package mysql-server-5.6 5.6.19-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fe

[Apport retracing service]

** 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:
  usr/share/mysql/errmsg-utf8.txt] 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/1503608/+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] [NEW] systemd: spamassassin not starting after upgrading to 15.04

[Sorin Sbârnea]

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 spamassassin.service
● spamassassin.service - Perl-based spam filter using text analysis
   Loaded: loaded (/lib/systemd/system/spamassassin.service; disabled; vendor 
preset: enabled)
   Active: inactive (dead)
root@atlas:/var/log# systemctl enable spamassassin.service
Synchronizing state for spamassassin.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d spamassassin defaults
Executing /usr/sbin/update-rc.d spamassassin enable
root@atlas:/var/log# systemctl status -l spamassassin.service
● spamassassin.service - Perl-based spam filter using text analysis
   Loaded: loaded (/lib/systemd/system/spamassassin.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead)

** Affects: spamassassin (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: systemd-boot

-- 
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 1471237] Re: Mongo causes juju to fail: bad record MAC

[Robie Basak]

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

Title:
  Mongo causes juju to fail: bad record MAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1471237/+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 1501812] Re: package irqbalance 1.0.6-3ubuntu1 failed to install/upgrade: package irqbalance is not ready for configuration cannot configure (current status `half-installed')

[Robie Basak]

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 get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or 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: irqbalance (Ubuntu)
   Status: New => Incomplete

-- 
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/1501812

Title:
  package irqbalance 1.0.6-3ubuntu1 failed to install/upgrade: package
  irqbalance is not ready for configuration  cannot configure (current
  status `half-installed')

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1501812/+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 1245604] Re: "killall -u snmp" in a pre-install step kills any running snmpd

[Graham Clinch]

** 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 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 running snmpd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1245604/+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 1501286] Re: package mysql-server-5.6 5.6.25-0ubuntu0.15.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Robie Basak]

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 get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or 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: mysql-5.6 (Ubuntu)
   Status: New => Incomplete

-- 
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/1501286

Title:
  package mysql-server-5.6 5.6.25-0ubuntu0.15.04.1 failed to
  install/upgrade: sub-processo script post-installation instalado
  retornou estado de saída de erro 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1501286/+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 1501294] Re: Unable to use vsftpd with PAM MySql

[Robie Basak]

*** 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 Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/1501294

Title:
  Unable to use vsftpd with PAM MySql

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1501294/+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 898124] Re: Missing Files for Apache2::SizeLimit in libapache2-mod-perl2 (2.0.5-2 oneiric 2.0.5-5 precise)

[Oliver Flimm]

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 (LTS)...

So all there is to do is include liblinux-pid-perl as a dependency to
fix this issue starting with utopic.

Nevertheless in the meantime I abandoned apache2/mod_perl for my webapp
in favor of PSGI/starman, so fixing this bug no longer affects me.

-- 
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/898124

Title:
  Missing Files for Apache2::SizeLimit in libapache2-mod-perl2 (2.0.5-2
  oneiric 2.0.5-5 precise)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-perl2/+bug/898124/+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 1501687] Re: package spamassassin 3.4.0-6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Robie Basak]

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
Ubuntu to not have gpg installed.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or 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: spamassassin (Ubuntu)
   Status: New => Incomplete

-- 
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/1501687

Title:
  package spamassassin 3.4.0-6 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1501687/+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 1501625] Re: package php5-cli 5.6.4+dfsg-4ubuntu6.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4

[Robie Basak]

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 get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or 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: php5 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1501625

Title:
  package php5-cli 5.6.4+dfsg-4ubuntu6.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1501625/+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 1501644] Re: package squid3 3.3.8-1ubuntu14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Robie Basak]

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 get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or 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: squid3 (Ubuntu)
   Status: New => 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/1501644

Title:
  package squid3 3.3.8-1ubuntu14 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1501644/+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 1501552] Re: package apache2 2.4.7-1ubuntu4.7 [origin: Ubuntu] failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Robie Basak]

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 get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or 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: apache2 (Ubuntu)
   Status: New => Incomplete

-- 
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/1501552

Title:
  package apache2 2.4.7-1ubuntu4.7 [origin: Ubuntu] 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/apache2/+bug/1501552/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

[Robie Basak]

** 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.
https://bugs.launchpad.net/bugs/120

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1501217] Re: apt-get removing squid-deb-proxy-client leaves a stale config file

[Robie Basak]

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 the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

Once done, please change the bug status back to New.

** Changed in: squid-deb-proxy (Ubuntu)
   Status: New => Incomplete

-- 
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/1501217

Title:
  apt-get removing squid-deb-proxy-client leaves a stale config file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1458323] Re: Asterisk crashes with default install because of pjsip

[Robie Basak]

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 => High

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1458323

Title:
  Asterisk crashes with default install because of pjsip

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1458323/+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 1501136] Re: php5-mysqlnd should provide php5-mysql

[Robie Basak]

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 (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1501136

Title:
  php5-mysqlnd should provide php5-mysql

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1501136/+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 1496210] Re: multipath-tools lacks the default settings for IBM 2810XIV storage system

[bugproxy]

** 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 for IBM 2810XIV storage
  system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1496210/+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 1503608] [NEW] package mysql-server-5.6 5.6.19-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den

[Gerrit Addiks]

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 everytime i try to
use it. When i try to start the mysql server manually (sudo service
mysql start), it gives me "start: Job failed to start" and nothing else.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: mysql-server-5.6 5.6.19-0ubuntu0.14.04.1 [modified: 
usr/share/mysql/errmsg-utf8.txt]
Uname: Linux 3.19.8-031908-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
Date: Wed Oct  7 11:10:01 2015
DuplicateSignature: package:mysql-server-5.6:5.6.19-0ubuntu0.14.04.1 [modified: 
usr/share/mysql/errmsg-utf8.txt]:Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 1 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
InstallationDate: Installed on 2014-02-20 (593 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: mysql-5.6
SystemImageInfo: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'system-image-cli'
Title: package mysql-server-5.6 5.6.19-0ubuntu0.14.04.1 [modified: 
usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to trusty on 2014-02-21 (592 days ago)

** Affects: mysql-5.6 (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.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1503608

Title:
  package mysql-server-5.6 5.6.19-0ubuntu0.14.04.1 [modified:
  usr/share/mysql/errmsg-utf8.txt] 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/1503608/+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 1500683] Re: DNSSEC should be disabled in MAAS by default

[Robie Basak]

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 default
+ By default DNSSEC is enabled with automatic keys

-- 
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/1500683

Title:
  By default DNSSEC is enabled with automatic keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1500683/+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 1245604] Re: "killall -u snmp" in a pre-install step kills any running snmpd

[Launchpad Bug Tracker]

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.
https://bugs.launchpad.net/bugs/1245604

Title:
  "killall -u snmp" in a pre-install step kills any running snmpd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1245604/+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 898124] [NEW] Missing Files for Apache2::SizeLimit in libapache2-mod-perl2 (2.0.5-2 oneiric 2.0.5-5 precise)

[Launchpad Bug Tracker]

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 included in the package, but not the other
two upon which the included file depends.

Possible solutions

1) Remove all Apache-SizeLimit related files so its possible to build
and create/install a separate libapache2-sizelimit-perl package

2) Include all Apache-SizeLimit related files. This would result in a
new dependency to the Perl Linux::pid-Module and the creation/addition
of this package to Ubuntu.

Regards

Oliver

** Affects: libapache2-mod-perl2 (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: libapache2-mod-perl2 (Ubuntu Precise)
 Importance: Medium
 Status: Triaged

** Affects: libapache2-mod-perl2 (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: bitesize
-- 
Missing Files for Apache2::SizeLimit in libapache2-mod-perl2 (2.0.5-2 oneiric 
2.0.5-5 precise)
https://bugs.launchpad.net/bugs/898124
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to the bug report.

-- 
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 898124] Re: Missing Files for Apache2::SizeLimit in libapache2-mod-perl2 (2.0.5-2 oneiric 2.0.5-5 precise)

[Robie Basak]

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: Unknown

** Tags added: bitesize

** Changed in: libapache2-mod-perl2 (Ubuntu)
   Status: Triaged => Fix Released

** Also affects: libapache2-mod-perl2 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: libapache2-mod-perl2 (Ubuntu Precise)
   Status: New => Triaged

** Changed in: libapache2-mod-perl2 (Ubuntu Precise)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libapache2-mod-perl2 in Ubuntu.
https://bugs.launchpad.net/bugs/898124

Title:
  Missing Files for Apache2::SizeLimit in libapache2-mod-perl2 (2.0.5-2
  oneiric 2.0.5-5 precise)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-perl2/+bug/898124/+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 1313133] Re: sa-compile error on ubuntu 14.04 LTS upgrade

[Robie Basak]

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, but doesn't? Otherwise it isn't clear that this isn't just a
configuration change after which spamassassin couldn't be expected to
work anyway.

Once done, please change the bug status back to New. Thanks!

** Changed in: spamassassin (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/1313133

Title:
  sa-compile error on ubuntu 14.04 LTS upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1313133/+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 1500684] Re: update to 5.6.20 for security fixes

[Robie Basak]

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). Volunteers can contribute an update via
https://wiki.ubuntu.com/SponsorshipProcess

** Changed in: mysql-5.6 (Ubuntu)
   Status: New => Fix Released

** Also affects: mysql-5.6 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Tags added: upgrade-software-version

** Changed in: mysql-5.6 (Ubuntu Trusty)
   Status: New => Triaged

-- 
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/1500684

Title:
  update to 5.6.20 for security fixes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500684/+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 1496210] Comment bridged from LTC Bugzilla

[bugproxy]

--- 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
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1496210

Title:
  multipath-tools lacks the default settings for IBM 2810XIV storage
  system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1496210/+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 1503674] [NEW] depends on iptables instead of nftables

[Hadmut Danisch]

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?


regards

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: docker.io (not installed)
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Oct  7 14:11:26 2015
InstallationDate: Installed on 2015-09-03 (33 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
SourcePackage: docker.io
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: docker.io (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to docker.io in Ubuntu.
https://bugs.launchpad.net/bugs/1503674

Title:
  depends on iptables instead of nftables

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1503674/+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 1500127] Re: package bacula-director-mysql 5.2.6+dfsg-9.1ubuntu4 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Robie Basak]

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 get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or 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: bacula (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1500127

Title:
  package bacula-director-mysql 5.2.6+dfsg-9.1ubuntu4 failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1500127/+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 1500360] Re: package clamav-daemon 0.98.7+dfsg-0ubuntu0.15.04.1 failed to install/upgrade: podproces instalovaný pre-removal skript vrátil chybový status 1

[Robie Basak]

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 get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or 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: clamav (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1500360

Title:
  package clamav-daemon 0.98.7+dfsg-0ubuntu0.15.04.1 failed to
  install/upgrade: podproces instalovaný pre-removal skript vrátil
  chybový status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1500360/+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 1500428] Re: package mysql-server-5.6 (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1

[Robie Basak]

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)
   Status: New => Invalid

-- 
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/1500428

Title:
  package mysql-server-5.6 (not installed) failed to install/upgrade: le
  sous-processus nouveau script pre-installation a retourné une erreur
  de sortie d'état 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500428/+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 525674] Re: apt-check hangs, preventing login via SSH

[Martin Pitt]

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 2>/dev/null || true

or

  [ ! -r /var/lib/update-notifier/updates-available ] || cat /var/lib
/update-notifier/updates-available

if you prefer that. This would be simpler IMHO.

 - changelog should point out that data/update-motd-updates-available
now runs in the background, to avoid blocking "apt-get update"
unnecessarily long.

These are just nitpicks, this looks fine by and large. Thanks for
working on this!

-- 
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/525674

Title:
  apt-check hangs, preventing login via SSH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+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 1503698] [NEW] FTBFS due to broken unit tests

[Łukasz Zemczak]

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
rootdir: /«PKGBUILDDIR», inifile: 
collected 493 items / 1 errors

tests/test_00_xmldsig.py ..
tests/test_01_xmlenc.py ..
tests/test_02_saml.py 
..
tests/test_03_saml2.py .
tests/test_04_samlp.py 
tests/test_05_md.py ..
tests/test_10_time_util.py .
tests/test_12_s_utils.py ..
tests/test_13_validate.py ...
tests/test_19_attribute_converter.py .
tests/test_20_assertion.py 
tests/test_22_mdie.py .
tests/test_30_mdstore.py ...
tests/test_30_mdstore_old.py ...
tests/test_31_config.py 
tests/test_32_cache.py ..
tests/test_33_identifier.py ..
tests/test_34_population.py 
tests/test_37_entity_categories.py ..
tests/test_40_sigver.py ...
tests/test_41_response.py ..FF
tests/test_42_enc.py 
tests/test_43_soap.py ..
tests/test_44_authnresp.py 
tests/test_50_server.py 
tests/test_51_client.py ...
tests/test_60_sp.py ss
tests/test_62_vo.py 
tests/test_63_ecp.py .
tests/test_64_artifact.py ...
tests/test_65_authn_query.py ..
tests/test_66_name_id_mapping.py ..
tests/test_67_manage_name_id.py ..
tests/test_68_assertion_id.py .
tests/test_69_discovery.py .
tests/test_70_redirect_signing.py .
tests/test_72_eptid.py ..
tests/test_75_mongodb.py .F
tests/test_76_metadata_in_mdb.py .
tests/test_77_authn_context.py ..
tests/test_81_certificates.py 
tests/test_88_nsprefix.py ..
(...)

[1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-
rebuild-20151001-wily.html

** Affects: python-pysaml2 (Ubuntu)
 Importance: Undecided
 Assignee: Łukasz Zemczak (sil2100)
 Status: In Progress


** Tags: ftbfs

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-pysaml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1503698

Title:
  FTBFS due to broken unit tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pysaml2/+bug/1503698/+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 1342412] Re: ssh-copy-id hangs when using ControlMaster auto

[Robie Basak]

** 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 Description]
+ 
  On ubuntu 14.04 amd 64, running openssh-client  1:6.6p1-2ubuntu2, when using 
in ~/ssh/config
-   ControlMaster   auto
+   ControlMaster   auto
  
  If you open an ssh connection to an host, and after try to run ssh-copy-id on 
the same host, trying to reuse the already opened connection, ssh-copy-id hangs.
  If you press CTRL-D, the script goes on, without installing any key.
  
  It seems that the script hangs at lines
-  REMOTE_VERSION=$(ssh -v -o PreferredAuthentications=',' "$@" 2>&1 |
-   sed -ne 's/.*remote software version //p')
+  REMOTE_VERSION=$(ssh -v -o PreferredAuthentications=',' "$@" 2>&1 |
+   sed -ne 's/.*remote software version //p')
  
  Found another bug report here: http://www.gossamer-
  threads.com/lists/openssh/bugs/57363
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 16 01:15:34 2014
  InstallationDate: Installed on 2013-10-12 (276 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  RelatedPackageVersions:
-  ssh-askpass   N/A
-  libpam-sshN/A
-  keychain  N/A
-  ssh-askpass-gnome 1:6.6p1-2ubuntu2
+  ssh-askpass   N/A
+  libpam-sshN/A
+  keychain  N/A
+  ssh-askpass-gnome 1:6.6p1-2ubuntu2
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2014-06-10 (35 days ago)
  modified.conffile..etc.ssh.ssh.config: [modified]
  mtime.conffile..etc.ssh.ssh.config: 2014-06-19T17:39:06.965908

-- 
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/1342412

Title:
  ssh-copy-id hangs when using ControlMaster auto

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1342412/+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 1500428] Re: package mysql-server-5.6 (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1

[Jean Claveau]

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 :
 
https://zhxq.io/how-to-solve-mariadb-plugin-unix_socket-is-not-loaded-problem-after-upgrade-to-ubuntu-15-04/

-- 
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/1500428

Title:
  package mysql-server-5.6 (not installed) failed to install/upgrade: le
  sous-processus nouveau script pre-installation a retourné une erreur
  de sortie d'état 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500428/+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 1447142] Re: systemd: ntpdate is started too soon (before the network)

[Robie Basak]

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 is relatively small.

> Perhaps, but timesyncd is not activated by default.

Ah. I had forgotten before, but now I remember that I was told that
timesyncd is automatically deactivated if ntp is installed.

> While timesyncd is probably a fine alternative to ntp, this is a bug
in ntp and Ubuntu would be a better system with this bug fixed (or ntp
removed and timesyncd activated by default).

Actually ntp isn't installed by default, and thus I believe that
timesyncd is activated by default, but isn't on your system because ntp
is installed.

I accept that prior to Vivid timesyncd wasn't an option, so it was
perfectly reasonable for users to install ntp manually, and then after
upgrade if this is broken then that is a bug.

But I think the breakage is just the suboptimal attempt to sync time at
boot, right? If time with ntp stays synced later without issues, then
I'll set Importance to Low on this basis. If I'm wrong in my
understanding then we can change this.

** Changed in: ntp (Ubuntu)
   Importance: High => Low

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1447142

Title:
  systemd: ntpdate is started too soon (before the network)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1447142/+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 1501217] Re: apt-get removing squid-deb-proxy-client leaves a stale config file

[Marius Gedminas]

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 in: squid-deb-proxy (Ubuntu)
   Status: Incomplete => New

-- 
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/1501217

Title:
  apt-get removing squid-deb-proxy-client leaves a stale config file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1501217] Re: apt-get removing squid-deb-proxy-client leaves a stale config file

[Marius Gedminas]

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 to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1501217

Title:
  apt-get removing squid-deb-proxy-client leaves a stale config file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1499931] Re: package php5-common 5.5.9+dfsg-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Robie Basak]

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 get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or 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: php5 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1499931

Title:
  package php5-common 5.5.9+dfsg-1ubuntu4.12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1499931/+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 1498952] Re: package python-beautifulsoup 3.2.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Robie Basak]

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 indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or 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: beautifulsoup (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to beautifulsoup in Ubuntu.
https://bugs.launchpad.net/bugs/1498952

Title:
  package python-beautifulsoup 3.2.1-1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/beautifulsoup/+bug/1498952/+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 1500006] Re: irqbalance crashes when CPUs are taken offline manually

[Robie Basak]

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 offline manually

** Changed in: irqbalance (Ubuntu)
   Importance: Undecided => Low

-- 
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/156

Title:
  irqbalance crashes when CPUs are taken offline manually

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/156/+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 1497108] Re: Long paths are not handled correctly when deleting partition mappings

[Robie Basak]

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.
https://bugs.launchpad.net/bugs/1497108

Title:
  Long paths are not handled correctly when deleting partition mappings

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1497108/+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 525674] Re: apt-check hangs, preventing login via SSH

[ChristianEhrhardt]

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 APT::Update::Post-Invoke-Success to update the cached file 
(thanks mvo and pitti for that good IRC discussion)
- removed one level of indirection (apt hook -> stamp file -> on pam login 
check stamp -> update) to the more separate
  (apt hook -> update cached info) (on pam login -> print cached info)
- while the chance of a concurrent update is now (almost) impossible it keeps 
the atomic cache update and cleanup to be sure

It was working find in all my builds and tests on wily.
Attaching for review ...

** Patch removed: "Fix for wily"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+attachment/4486127/+files/wily_package.debdiff

** Patch removed: "Fix for upstream"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+attachment/4486128/+files/upstream_package.debdiff

-- 
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/525674

Title:
  apt-check hangs, preventing login via SSH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+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 1447142] Re: systemd: ntpdate is started too soon (before the network)

[Laurent Bonnaud]

> 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, but timesyncd is not activated by default.  I had to type this
command to activate it:

# timedatectl set-ntp true

While timesyncd is probably a fine alternative to ntp, this is a bug in
ntp and Ubuntu would be a better system with this bug fixed (or ntp
removed and timesyncd activated by default).

> Is the time on your system actually falling out of sync, or is the problem 
> just the noise of
the error message?

Time is fine on my system, but the noise of the error messages is a
problem in itself.


** Changed in: ntp (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1447142

Title:
  systemd: ntpdate is started too soon (before the network)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1447142/+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 525674] Re: apt-check hangs, preventing login via SSH

[ChristianEhrhardt]

** 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 bug report.
https://bugs.launchpad.net/bugs/525674

Title:
  apt-check hangs, preventing login via SSH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+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 1471237] Re: Mongo causes juju to fail: bad record MAC

[Curtis Hovey]

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 -test.timeout=1800s ./...

-- 
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

Title:
  Mongo causes juju to fail: bad record MAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1471237/+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 1477225] Re: ceph-radosgw restart fails

[Chris J Arges]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ceph (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Changed in: ceph (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1477225/+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 1477225] Re: ceph-radosgw restart fails

[David Britton]

** 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:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1477225/+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 1475247] Re: ceph-disk-prepare --zap-disk hang

[Chris J Arges]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ceph (Ubuntu Trusty)
   Status: Fix Released => Fix Committed

** Changed in: ceph (Ubuntu Vivid)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

-- 
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/1475247

Title:
  ceph-disk-prepare --zap-disk hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+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 1503779] [NEW] package spamassassin 3.4.0-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[nono]

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 3.13.0-65.106-lowlatency 3.13.11-ckt26
Uname: Linux 3.13.0-65-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
Date: Wed Oct  7 18:57:49 2015
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2015-06-29 (100 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: spamassassin
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
Title: package spamassassin 3.4.0-1ubuntu2.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: spamassassin (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

-- 
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/1503779

Title:
  package spamassassin 3.4.0-1ubuntu2.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1503779/+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 1503698] Re: FTBFS due to broken unit tests

[Łukasz Zemczak]

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 Ubuntu.
https://bugs.launchpad.net/bugs/1503698

Title:
  FTBFS due to broken unit tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pysaml2/+bug/1503698/+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 304393] Re: cups: 127.0.0.1:631 - Address already in use.

[D J Gardner]

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 took a lot of debugging before I stumbled upon the article above, and I've 
been using linux since it came on two floppies. The problem has been noted in 
redhat, suse, even BSD.

I propose a solution: rpcbind should NOT assign random ports, it should assign 
random *unallocated* ports (i.e. it should
make a list of things listed in /etc/services and avoid those ports.)

-- 
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 use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+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 639712] Re: PCI Pass Through via libvirt cannot remap IRQ's

[Chris J Arges]

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 => Incomplete

** Changed in: qemu-kvm (Ubuntu)
   Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/639712

Title:
  PCI Pass Through via libvirt cannot remap IRQ's

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/639712/+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 457092] Re: starting a VM with an SDL display hangs virtmanager and virsh

[Stefan Bader]

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 this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/457092

Title:
  starting a VM with an SDL display hangs virtmanager and virsh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/457092/+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 1488453] Re: Package postinst always fail on first install when using systemd

[Chris J Arges]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: openhpi (Ubuntu Vivid)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openhpi/+bug/1488453/+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 1448650] Re: rpc.server do not consume messages after message acknowledge failure

[Chris J Arges]

** 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 consume messages after message acknowledge failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.messaging/+bug/1448650/+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 1454273] Re: irqbalance should not run in container

[Launchpad Bug Tracker]

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.
https://bugs.launchpad.net/bugs/1454273

Title:
  irqbalance should not run in container - add systemd unit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1454273/+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 1454273] Re: irqbalance should not run in container - add systemd unit

[Bryan Quigley]

** 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 is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1454273

Title:
  irqbalance should not run in container - add systemd unit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1454273/+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 1497087] Re: updates from trusty to vivid will fail when juju-core is installed

[Chris J Arges]

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.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1497087

Title:
  updates from trusty to vivid will fail when juju-core is installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1497087/+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 1488453] Re: Package postinst always fail on first install when using systemd

[Launchpad Bug Tracker]

** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openhpi/+bug/1488453/+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 1451537] Re: python-greenlet fails to build in trusty with updated python 2.7.9

[Chris J Arges]

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 package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: python-greenlet (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: python-greenlet (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: python-greenlet (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: python-greenlet (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
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 updated python 2.7.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-greenlet/+bug/1451537/+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 1454273] Re: irqbalance should not run in container

[Bryan Quigley]

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 /lib/systemd/system/irqbalance.service
change path to env in service file
sudo systemctl enable irqbalance.service
reboot

Note, this doesn't actually do anything for a container, but I thought
it's worth mentioning that a systemd unit exists upstream.

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1454273/+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 1500916] Re: [needs-packaging] 1.24.6 is not packaged in Vivid

[Chris J Arges]

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.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: juju-core (Ubuntu Vivid)
   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.
https://bugs.launchpad.net/bugs/1500916

Title:
  [needs-packaging] 1.24.6 is not packaged in Vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1500916/+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 1451537] Re: python-greenlet fails to build in trusty with updated python 2.7.9

[Launchpad Bug Tracker]

** 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 updated python 2.7.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-greenlet/+bug/1451537/+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 1454273] Re: irqbalance should not run in container - add systemd unit

[Bryan Quigley]

** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1454273/+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 1503330] Re: New upstream bugfix release 1.1.4 (LXC MRE)

[Chris J Arges]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: lxc (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Tags added: verification-needed

** Changed in: lxc (Ubuntu)
   Status: New => Invalid

** Changed in: lxc (Ubuntu Vivid)
   Status: New => Fix Committed

-- 
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/1503330

Title:
  New upstream bugfix release 1.1.4 (LXC MRE)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1503330/+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 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup

[Brian Murray]

** 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 to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+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 1500916] Re: [needs-packaging] 1.24.6 is not packaged in Vivid

[Curtis Hovey]

** 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 Vivid do not get a downgrade that looses
  bug fixes.
  
  See bug 1481556 for the history of placing juju-core 1.24.6 into Wily.
  
  Fixing this bug fixes bug 1497087
  
  [SRU Information]
  
  juju-core has a stable release exception in 
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including 
for major version
  updates.
  
  [Vivid Fix]
  
  [sinzui] Prepare source package, and diffs: DONE
  [rbasak] Review package: DONE
  
  [Pre-QA tasks]
  
  [rbasak] Upload to vivid (vivid-proposed): DONE
  
  [QA Status]
  
  Since there are multiple verifications required, they are listed here as a 
work
  item whiteboard status type thing rather than try and track them in a single
  tag. Please do not mark verification-done or remove block-proposed until all
  following items have passed. If any of these items fail, this bug should be
  marked verification-failed immediately.
  
  [sinzui] Upstream release process complete: DONE
- [sinzui] Upstream QA test against Vivid: TODO
+ [sinzui] Upstream QA test against Vivid: DONE
  
  Manual tests required:
  
  [sinzui] Test juju-quickstart against wily-proposed: TODO
  [sinzui] Test juju-deployer against wily-proposed: TODO
  [sinzui] Test client and cloud server upgrade from main/updates: TODO
  [sinzui] Test client manual bootstrap and add-machine: TODO

** 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 Vivid do not get a downgrade that looses
  bug fixes.
  
  See bug 1481556 for the history of placing juju-core 1.24.6 into Wily.
  
  Fixing this bug fixes bug 1497087
  
  [SRU Information]
  
  juju-core has a stable release exception in 
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including 
for major version
  updates.
  
  [Vivid Fix]
  
  [sinzui] Prepare source package, and diffs: DONE
  [rbasak] Review package: DONE
  
  [Pre-QA tasks]
  
  [rbasak] Upload to vivid (vivid-proposed): DONE
  
  [QA Status]
  
  Since there are multiple verifications required, they are listed here as a 
work
  item whiteboard status type thing rather than try and track them in a single
  tag. Please do not mark verification-done or remove block-proposed until all
  following items have passed. If any of these items fail, this bug should be
  marked verification-failed immediately.
  
  [sinzui] Upstream release process complete: DONE
  [sinzui] Upstream QA test against Vivid: DONE
  
  Manual tests required:
  
- [sinzui] Test juju-quickstart against wily-proposed: TODO
- [sinzui] Test juju-deployer against wily-proposed: TODO
+ [sinzui] Test juju-quickstart against vivid-proposed: TODO
+ [sinzui] Test juju-deployer against vivid-proposed: TODO
  [sinzui] Test client and cloud server upgrade from main/updates: TODO
  [sinzui] Test client manual bootstrap and add-machine: TODO

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1500916

Title:
  [needs-packaging] 1.24.6 is not packaged in Vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1500916/+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 1500916] Re: [needs-packaging] 1.24.6 is not packaged in Vivid

[Curtis Hovey]

** 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 Vivid do not get a downgrade that looses
  bug fixes.
  
  See bug 1481556 for the history of placing juju-core 1.24.6 into Wily.
  
  Fixing this bug fixes bug 1497087
  
  [SRU Information]
  
  juju-core has a stable release exception in 
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including 
for major version
  updates.
  
  [Vivid Fix]
  
  [sinzui] Prepare source package, and diffs: DONE
- [rbasak] Review package: TODO
+ [rbasak] Review package: DONE
  
  [Pre-QA tasks]
  
- [rbasak] Upload to vivid (vivid-proposed): TODO
+ [rbasak] Upload to vivid (vivid-proposed): DONE
  
  [QA Status]
  
  Since there are multiple verifications required, they are listed here as a 
work
  item whiteboard status type thing rather than try and track them in a single
  tag. Please do not mark verification-done or remove block-proposed until all
  following items have passed. If any of these items fail, this bug should be
  marked verification-failed immediately.
  
  [sinzui] Upstream release process complete: DONE
  [sinzui] Upstream QA test against Vivid: TODO
  
  Manual tests required:
  
  [sinzui] Test juju-quickstart against wily-proposed: TODO
  [sinzui] Test juju-deployer against wily-proposed: TODO
  [sinzui] Test client and cloud server upgrade from main/updates: TODO
  [sinzui] Test client manual bootstrap and add-machine: TODO

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1500916

Title:
  [needs-packaging] 1.24.6 is not packaged in Vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1500916/+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 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

[Alexis Bruemmer]

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 dependencies change between minor release
(for example there were 14 package dependency changes from 1.24 to 1.25)

* SRU team: juju-core already has a release exception. For packages that
are being broken out that were formerly part of the juju-core package
and that the juju team will now maintain, can those just be given a
release exception?

Yes, those should also be given a release exception.  Many of these are
central to keeping ubuntu current with existing clouds.  For Juju to
actually work, if the dependent packages are being split out, every
single one of them will need to be included in the release exception.

* Ubuntu Archive team: juju-core will likely need a PPU for members of
the juju team when it goes to main. Can we extend the acl to include the
packages that are being broken out that they are going to maintain?

Yes, to deliver a fix to juju core, we need to fix the dependencies at
the same time.  This will be done by the same person, so yes to
extending the acls to those packages.

* MIR team: for the packages that are being broken out, I propose that
they don't get extended MIR review, but rather simply the packaging
review to make sure they are following the Go standards as outlined in
the MIRteam document

Yes, agreed.

* juju team (/security team): the juju team has said that they would
like coordination of security updates for juju-core and golang-*-dev
packages for which they maintain. I propose the security team maintains
a list of packages and when we triage a CVE against a package in that
list, we file a bug for the juju team to fix, and sponsor their uploads
(like for other Canonical upstreams). juju team-- does that address your
concerns?

Yes, we will own fixing security bugs for juju, and dependent libraries
that we control or can patch.

-- 
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, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+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 304393] Re: cups: 127.0.0.1:631 - Address already in use.

[D J Gardner]

** 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 use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+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 1503698] Re: FTBFS due to broken unit tests

[Łukasz Zemczak]

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 that still.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-pysaml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1503698

Title:
  FTBFS due to broken unit tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pysaml2/+bug/1503698/+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 1422046] Re: cinder backup-list is always listing all tenants's bug for admin

[OpenStack Infra]

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 
Date:   Fri Sep 25 17:23:06 2015 +0200

Do not list cinder backups as admin with cinderclient<1.4.0

Due to the following bug:
https://bugs.launchpad.net/python-cinderclient/+bug/1422046
We do not attempt to list cinder backups as admin if cinderclient's version 
is
lower than 1.4.0

Change-Id: I570971391cff80e1d6a484c330e80f901f5210b3
Closes-Bug: #1422046


** Changed in: ospurge
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cinderclient in Ubuntu.
https://bugs.launchpad.net/bugs/1422046

Title:
  cinder backup-list is always listing all tenants's bug for admin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ospurge/+bug/1422046/+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