god [2015-05-02 23:19 -]:
Is there some detailed notes on why upstart is still used for user
sessions instead of systemd? Is it just lack of time or there are some
technical reasons not to switch to systemd here as well?
Mostly just lack of time/engineers, and not changing too many
Thanks.
** Changed in: bind9 (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1450300
Title:
following ubuntu documentation and caching
** Changed in: devstack
Status: New = Invalid
** Changed in: heat
Status: New = Invalid
** Changed in: heat (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to heat in Ubuntu.
Public bug reported:
just doing the aptitude install trove-api, error during installation.
2015-05-04 00:23:33.722 30339 TRACE root OperationalError:
(OperationalError) unable to open database file None None
Probably it requires a database configuration, to start. Have a prompt
for the db
FAir enouigh, I suspect this is a bad interaction between bind and the
firewall.
--
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/1450300
Title:
following ubuntu documentation and
bug can be closed.
--
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/1450300
Title:
following ubuntu documentation and caching server will not work
To manage notifications about this
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-trove in Ubuntu.
https://bugs.launchpad.net/bugs/1451273
Title:
package trove-common 2015.1~rc1-0ubuntu2 failed to install/upgrade:
Attempting to recover by: aptitude install smbclient samba-common
Resulted in:
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up samba-common (2:4.1.6+dfsg-1ubuntu2.14.04.7) ...
rmdir: failed to remove
The packages list of ubuntu-archive of kilo:
http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/kilo_versions.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Quoting Serge Hallyn
Perhaps after a (reasonably long) timeout we should assume
it is dead, hard-kill the container (in this case the owner of the
command socket), and continue.
I'm seeing this behaviour happen in Vivid although in my case the
stuck container is perfectly responsive and is
Correction, I meant to say I'm seeing this behaviour happen in Trusty
not Vivid.
--
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/1377973
Title:
lxc-destroy/lxc-stop gets stuck
To
Public bug reported:
Running do-release-upgrade - system generated a bug report
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: samba-common 2:4.1.6+dfsg-1ubuntu2.14.04.7
ProcVersionSignature: Ubuntu 3.2.0-80.116-generic-pae 3.2.68
Uname: Linux 3.2.0-80-generic-pae i686
ApportVersion:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1451322
Title:
upgrade 10.04 to 14.04 failed - package samba-common 2:4.1.6+dfsg-
** Tags removed: need-duplicate-check
--
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/1451167
Title:
package spamassassin 3.4.0-1ubuntu2.1 failed to install/upgrade:
Support for this version has ended
** Changed in: python2.6 (Ubuntu)
Status: Triaged = Invalid
--
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/357067
Title:
javascript
Huh, interesting - docs still say that the cloud images are *made* using
this tool, is that no longer true? Is there some replacement?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
Public bug reported:
When using OpenSSH to access a remote server, the local user's locale
environment variables are always sent to the remote server, because the
default installation has /etc/ssh/ssh_config configured with SendEnv
LANG LC_*
This often makes no sense, as the local user likely
# 22 works perfectly for me on 14.10 and makes all KDEPIM snappier:
I have another solution:
- 1st i run update:
sudo aptitude update
when it is done then:
sudo aptitude purge mysql-server-core-5.6 mysql-client-core-5.6
aptitute will tell it has many dependencies, many packages will be removed
Public bug reported:
Machine is configured without IPv6,
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: spamassassin 3.4.0-1ubuntu2.1
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic i686
ApportVersion: 2.14.1-0ubuntu3.10
AptOrdering:
It would be much better to replace it with systemd-timesyncd calls and
drop ntpdate dependency altogether.
--
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/583994
Title:
Consider
** Changed in: tftp-hpa (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tftp-hpa in Ubuntu.
https://bugs.launchpad.net/bugs/1448500
Title:
tftp-hpa doesn't accept IPv4 connections
To manage
Public bug reported:
Perhaps this is an upgrade issue, perhaps it is a installation issue.
In either case, there should be more information about upgrading lxc.
After upgrading to Ubuntu 15.04, my container no longer started.
After upgrading, I had to remove the following line from the config
22 matches
Mail list logo