looks like the bug is caused by incomplete translation
i have Ubuntu 12.04 with russian localization
if i enter "yes" i got the same "Job not run" message
but if i answer in russian ("да") it works fine
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/1480411
Title:
rm -r * fails to delete directories when using ov
I don't quite get the point underlying Serge's preceding comment, so
I'll describe the problem I'm experiencing with lxc and see whether
Serge classifies it as a bug.
On an ubuntu-vivid (amd64) host, create an unprivileged vivid container named
'vivid',
lxc-create -n vivid -t download -- -d ub
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /pro
** Description changed:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2
22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
- 1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
+ 1. /proc//fdinfo/ reports wrong
apport information
** Tags added: apparmor apport-collected third-party-packages uec-images
** Description changed:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2
22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499891/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499894/+files/UdevDb.txt
--
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/150746
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499890/+files/ProcCpuinfo.txt
--
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/
apport information
** Attachment added: "lxcsyslog.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499923/+files/lxcsyslog.txt
--
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
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499889/+files/Lspci.txt
--
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/1507463
apport information
** Attachment added: "KernLog.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499888/+files/KernLog.txt
--
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/150
apport information
** Attachment added: "lxc-net.default.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499897/+files/lxc-net.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499886/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499895/+files/UdevLog.txt
--
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/150
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499887/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499896/+files/WifiSyslog.txt
--
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/bu
apport information
** Attachment added: "lxc.default.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499898/+files/lxc.default.txt
--
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/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499892/+files/ProcModules.txt
--
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/
apport information
** Attachment added: "RelatedPackageVersions.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499893/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https
** Description changed:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2
22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc
I retested using lxc-1.1.4 from the lxc-stable ppa
(https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-stable) which I
added to a fresh vm image from the daily-builds, https://cloud-
images.ubuntu.com/trusty/current.
"lxc-start -n trusty_overlay" fails as before, with the same error
message,
E
I retested using lxc-1.1.4 from the lxc-stable ppa
(https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-stable), which I
added to a fresh VM image from the Trusty daily-builds, https://cloud-
images.ubuntu.com/trusty/current.
"lxc-start -n trusty_overlay" fails as before, with the same error
mes
Chris, it would be of interest to see whether you can reproduce the
underlying kernel bug using this script,
#!/bin/bash
fatal() { echo "error: $@"; exit 1; }
echo -e "testing for overlayfs kernel bug in kernels <= 3.17.";
echo -e "(This script does not work for the newer version of overlayfs in
The following lxc commit introduced safe_mount(), which passes fd's as
arguments to mount(),
CVE-2015-1335: Protect container mounts against symlinks
https://github.com/lxc/lxc/commit/6de26af93d3dd87c8b21a42fdf20f30fa1c1948d
Here is the relevant part of the commit, which creates a file descripto
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: lxc (Ubuntu)
Status: Incomplete => Confirmed
--
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/1507
Related bug #1347746 : Overlayfs breaks /proc/self/exe link
--
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/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.
I encountered a similar problem when upgrading a container from 13.04 to
13.10.
The problem was that the listed dependencies for ubuntu-release-
upgrader-core were not sufficient.
The solution was to install python-apt. (Even that was a bit difficult;
I had to manually create an empty file,
/etc
This bug does still affect lxc on Ubuntu Trusty when using the 3.13
kernel in conjunction with the latest daily-build of lxc,
1.1.5+master~20151110-0623-0ubuntu1~trusty (from the lxc-daily ppa,
https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/daily).
** Also affects: lxc (Ubuntu)
Importance:
This bug does still affect lxc when using kernel 3.18 or above in
conjunction with the latest daily-build of lxc,
1.1.5+master~20151110-0623-0ubuntu1~trusty (from the lxc-daily ppa,
https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/daily).
** Also affects: lxc (Ubuntu)
Importance: Undecided
This bug does still affect lxc (as per comment #5) when using kernel
3.18 or above in conjunction with the latest daily-build of lxc,
1.1.5+master~20151110-0623-0ubuntu1~trusty (from the lxc-daily ppa,
https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/daily).
--
You received this bug notification
@Serge,
Thanks for the clarification; I'll revert the status to un-marked.
** No longer affects: lxc (Ubuntu)
--
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/1480411
Title:
rm -r * fa
** No longer affects: lxc (Ubuntu)
--
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/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
To manage notification
I can no longer reproduce this bug, following the release of fixes for
bugs #1531747, #1534961 and #1535150 .
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Problem 1:3.7-1 nbd-server_1:3.7-1_i386.deb ubuntu trusty
authorization file:
192.168.3.28
In syslog:
connect from 192.168.3.28, assigned file is /opt/ltsp/images/i386.img
Client '192.168.3.28' is not authorized to access
Child exited with 1
--
You received this bug notification because you are
It appears that this problem affects me as well.
I have Intrepid Ibex 2.6.27-7-generic kernel. Since upgrade to Intrepid, I
cannot access samba folders.
My samba server is 2.0 (shipped with OpenWrt). I am mounting with simple fstab
line:
//asus-router/torrents /mnt/torrents smbfs
user,usern
I have the same bug too
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To manage notifications about
* Ubuntu 14.04.4 + Openstack Liberty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To manage notifi
Thanks Barry! The patch did the fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/1014257
Title:
MySQL monitoring fails when used with Percona or MariaDB
To manage notif
Hi Jacek,
Thanks for reporting the bug and providing us with the fix.
I prepared a debdiff (attached) and will be looking for sponsorship.
** Patch added: "lp-1416039.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1416039/+attachment/4333549/+files/lp-1416039.debdiff
--
You
** Changed in: squid3 (Ubuntu)
Assignee: (unassigned) => Oleg Strikov (strikov)
--
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/1416039
Title:
Broken apparmor profile
To man
I prepared a debdiff for vivid (attached) and currently looking for sponsorship.
My repro case can be found here: http://pastebin.ubuntu.com/10527246/
** Patch added: "lp-1336742-vivid.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1336742/+attachment/4334428/+files/lp-1336742-
Updated package has been pushed to vivid-proposed.
Feel free to try it.
--
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/1336742
Title:
Caching responses with "Vary" header
To manage no
I prepared debdiff for vivid-release (attached) and currently looking
for sponsorship.
** Patch added: "lp-1424508-released.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+attachment/4335137/+files/lp-1424508-released.debdiff
--
You received this bug notification beca
I prepared debdiff for vivid-proposed (attached) and currently looking
for sponsorship.
** Patch added: "lp-1424508-proposed.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+attachment/4335136/+files/lp-1424508-proposed.debdiff
--
You received this bug notification bec
My reprocase can be found here: http://paste.ubuntu.com/10538557/
--
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/1424508
Title:
upstartism in the maintainer script
To manage notificat
Thanks for pointing that.
Done.
** Patch added: "lp-1424508-proposed-1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+attachment/4335313/+files/lp-1424508-proposed-1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
Public bug reported:
I'm trying to use LXC on my openstack instance which runs vivid daily:
$ sudo apt-get install lxc -y
$ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache
--stream=daily --release=vivid
$ sudo lxc-start --name vivid --logfile=lxc.log
lxc-start: lxc_start.c: main:
Hi Serge,
Many thanks for looking at the bug.
Here is information you requested.
ubuntu@vivid-lxc-bug:~$ uname -a
Linux vivid-lxc-bug 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:03 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@vivid-lxc-bug:~$ sudo aa-status
apparmor module is loaded.
6 p
It seems that this bug consists of many partially independent bugs.
I found at least two:
(1)
openjdk in vivid has SSLv3 disable but tests try to use it and get 'protocol is
disabled or cipher suites are inappropriate'
as a warkaround you may enable sslv3 back by commenting the following line in
They have updated certs in trunk:
http://mail-archives.apache.org/mod_mbox/tomcat-dev/201502.mbox/%3c20150228182330.eaaabac0...@hades.apache.org%3E
We may just pick them up.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report
Some part of bugs disappear when I put updated certs (with expiration date in
2017) from here:
https://github.com/apache/tomcat/test/org/apache/tomcat/util/net/{localhost-cert.pem,
localhost-copy1.jks, localhost.jks, localhost-key.pem}
--
You received this bug notification because you are a mem
** Changed in: tomcat7 (Ubuntu Vivid)
Status: Confirmed => Fix Released
--
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/1432715
Title:
tomcat7 ftbfs in vivd (test failures)
To m
Shell script which reproduces the issue: http://pastebin.ubuntu.com/10712595/
Please run this script only on a disposable instance in the cloud because it
creates and adds ultimately trusted certificate to the target machine.
I was able to reproduce the issue on precise (12.04) and trusty (14.04)
/mysql.service
After running this command you (theoretically) should be able to purge and
install the package w/o any issue.
Please let us now if it helps you or not.
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Oleg Strikov (strikov)
--
You received this bug notification beca
** Changed in: openldap (Ubuntu Precise)
Status: New => In Progress
** Changed in: openldap (Ubuntu Trusty)
Status: New => In Progress
** Changed in: openldap (Ubuntu Precise)
Assignee: (unassigned) => Oleg Strikov (strikov)
** Changed in: openldap (Ubun
'I was able to reproduce the issue with upgrading the package (second part of
the bug):'
should be
'I was able to reproduce the issue with REMOVING the package (second part of
the bug):'
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Hi Argenis,
Today I tried to upgrade from 5.6.23-1~exp1~ubuntu4 to 5.6.23-1~exp1~ubuntu5
and reproduce the issue you observed.
Here is what I found:
Upgrade from ~ubuntu4 to ~ubuntu5 runs smoothly.
Mysql service starts after upgrade and automatically starts after reboot.
I can't reproduce the fa
I plan to change the status of this bug to Won't Fix and here is the
explanation for this decision. We can theoretically fix this issue in
mysql package. In the postrm handler we need to check if this
problematic symlink exists and remove it before passing control to deb-
systemd-helper. I don't th
Public bug reported:
While working on mysql-5.6 package we met unusual (maybe even partially
incorrect) Alias option in systemd unit config:
Alias=mysql.service
It is unusual because mysql.service is the original name of the service which
can be found inside /lib/systemd/system/<...> This Alias
Tag block-proposed has been removed to be able to update the package in vivid.
We don't plan to update trusty package with 1.22.0 for now.
I'll post an update to this bug when we make decision on package update in
trusty.
** Tags removed: block-proposed
--
You received this bug notification bec
Juju 1.22.0 can't provision instances which run vivid because it doesn't
support systemd. Systemd support has been introduced in Juju 1.23 and we
plan to package this release when it becomes stable (now in beta).
However, I think that having 1.22 in vivid is much better than having
Juju 1.20 (what
I plan to change the status of this bug for 12.04 (precise) and 14.04 (trusty)
to Won't Fix.
In this comment I want to explain why I came to this decision.
This bug had CVE-2013-4449 linked to it. I don't think that this CVE is
relevant because the patch proposed in this bug doesn't resolve the
Hi Harry,
Thanks for the input.
Could you add more information on this please:
> silently switch from a slapd that used openssl to gnutls
I just looked through the launchpad package archive and it looks like we never
had openldap linked against openssl in 12.04 and 14.04. First version of
openld
** Project changed: juju-core => juju-core (Ubuntu)
--
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/1444037
Title:
juju-core 1.22.1 is not packaged in Ubuntu
To manage notificatio
** Changed in: juju-core (Ubuntu)
Assignee: Curtis Hovey (sinzui) => (unassigned)
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) => Oleg Strikov (strikov)
** Changed in: juju-core (Ubuntu Trusty)
Assignee: (unassigned) => Oleg Strikov (strikov)
--
You received
Removing 'block-proposed' flag to allow juju 1.22.1 to go into Vivid.
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in
Here is the changelog for the package I'm asking SRU for:
juju-core (1.22.1-0ubuntu0.14.04.1) trusty; urgency=medium
* New upstream release (LP: #1444037).
* Packaging changes required by the new release and cherry-picked from Vivid:
- d/tests/fake-future.sh: New ability to generate fake
Public bug reported:
We're now in a position to have 1.23.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general production use.
Debdiff attached.
[SRU]
[Impact]
Bug shows up when user tries to upgrade any previous version of clamav
to the version which is currently available inside vivid repo. Apt
crashes with the following error message:
/var/lib/dpkg/info/clamav-daemon.postinst: 626:
/var/lib/dpkg/info/clamav-daemon.
Verification done. Logs: http://pastebin.ubuntu.com/10880409/
** 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 the bug report.
https://bugs.launchpad.net/bugs/1438745
Thanks Curtis! Adding 'verification-done' tag based on your comments.
** 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
There was a typo in the message #8 from Curtis. Juju 1.22.1 has been certified
not 1.20.1.
strikov, oops, yes, I do mean *1.22.1*
--
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/144
Hi Curtis,
To my understanding juju-1.22.1 is not in -updates yet not because we
don't want this but because it needs to be in -proposed for 7 days
before reaching -updates. This is a standard practice for SRUs. I expect
to see it landed into -updates until the end of this week. If juju team
wants
Execution of blockdev --rereadpt simply issues a call to
ioctl(BLKRRPART) which forces kernel to re-initialize its metadata.
Kernel adds information about newly created partition here:
http://lxr.linux.no/#linux+v3.19.1/block/partition-generic.c#L269 You
can see a call to kobject_uevent() which put
Adding verification-failed based on #14
** Tags removed: verification-done
** Tags added: verification-failed
--
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/1444037
Title:
juju-c
Public bug reported:
While trying to run openstack-nova/libvirt on arm64 machine we got the
following error:
2014-04-02 16:08:11.140+: 1227: error : qemuProcessWaitForMonitor:1915 :
internal error: process exited while connecting to monitor: libvirt: error :
cannot execute binary /usr/bin
Public bug reported:
ubuntu@mw01-02:~$ juju --version
1.18.1-trusty-armhf
ubuntu@mw01-02:~$ uname -a
Linux mw01-02 3.13.0-24-generic-lpae #46-Ubuntu SMP Thu Apr 10 21:01:14 UTC
2014 armv7l armv7l armv7l GNU/Linux
ubuntu@mw01-02:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DIS
Public bug reported:
ubuntu@mw01-02:~$ juju --version
1.18.1-trusty-armhf
ubuntu@mw01-02:~$ uname -a
Linux mw01-02 3.13.0-24-generic-lpae #46-Ubuntu SMP Thu Apr 10 21:01:14 UTC
2014 armv7l armv7l armv7l GNU/Linux
ubuntu@mw01-02:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DIS
** Description changed:
+ ubuntu@mw01-02:~$ juju --version
+ 1.18.1-trusty-armhf
+
ubuntu@mw01-02:~$ uname -a
Linux mw01-02 3.13.0-24-generic-lpae #46-Ubuntu SMP Thu Apr 10 21:01:14 UTC
2014 armv7l armv7l armv7l GNU/Linux
- ubuntu@mw01-02:~$ cat /etc/lsb-release
+ ubuntu@mw01-02:~$ cat /
This bug prevents juju/local from running on armhf.
I'm getting 'confused by armhf' while trying to deploy the node because juju
uses ubuntu-cloud template internally.
Does it make sense to change importance to the higher level taking this fact
into account?
--
You received this bug notificatio
One more note. As Jean-Baptiste Lallement stated even if you manually add armhf
to the script it doesn't help much because there are no description for armhf
images in both:
https://cloud-images.ubuntu.com/query/saucy/server/daily.current.txt
https://cloud-images.ubuntu.com/query/saucy/server/rel
This was fixed by smoser and pushed to trunk.
Here is a diff if you're interested: https://pastebin.canonical.com/99718/
--
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/1159818
Title:
Al
Public bug reported:
I had to do some source code changes to be able to run Horizon on trusty.
Here is a list of change in a form of error message followed by solution.
Can we update the package to be able to run it just from the box?
==
Which software also has this problem?
04 июня 2014 г. 11:51 пользователь "Joel" написал:
> Not here, still seeing the same problem, and not just with vsftpd:
>
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04 LTS
> Release:14.04
> Codename: tru
3.13.0-29 kernel doesn't fix this bug.
*WBR, Lomakin Oleg*
--
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/1313450
Title:
Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 o
86 matches
Mail list logo
