[Bug 1181942] [NEW] Sync python-gevent 0.13.7-4 (main) from Debian unstable (main)
Public bug reported: Please sync python-gevent 0.13.7-4 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * New upstream release. * Bump Standards-Version to 3.9.3. * Remaining differences from Debian: - Use dh_python2 instead of python-support * New upstream release. * Bump Standards-Version to 3.9.3. * Remaining differences from Debian: - Use dh_python2 instead of python-support * New upstream release. * Bump Standards-Version to 3.9.3. * Remaining differences from Debian: - Use dh_python2 instead of python-support * Convert from python-support to dh_python2 - debian/control + Drop python-support from build-deps + Update dependency on python to 2.6.6-3~ - debian/rules + Call dh7 with --with=python2 * Convert from python-support to dh_python2 - debian/control + Drop python-support from build-deps + Update dependency on python to 2.6.6-3~ - debian/rules + Call dh7 with --with=python2 * Convert from python-support to dh_python2 - debian/control + Drop python-support from build-deps + Update dependency on python to 2.6.6-3~ - debian/rules + Call dh7 with --with=python2 The only Ubuntu delta is building with dh_python2, and this was done in Debian. Changelog entries since current saucy version 0.13.7-0ubuntu1: python-gevent (0.13.7-4) unstable; urgency=low * Last bits of -dbg package fix (closes: #703611). -- Laszlo Boszormenyi (GCS) g...@debian.hu Sun, 24 Mar 2013 01:18:51 +0100 python-gevent (0.13.7-3) unstable; urgency=low * Build standard documentation. -- Laszlo Boszormenyi (GCS) g...@debian.hu Fri, 22 Mar 2013 17:05:07 +0100 python-gevent (0.13.7-2) unstable; urgency=low * Fix -dbg package (closes: #703611). * Use offline intersphinx inventory instead of download it. * Remove unneeded python-support from build dependencies (closes: #703625). -- Laszlo Boszormenyi (GCS) g...@debian.hu Fri, 22 Mar 2013 09:34:15 + python-gevent (0.13.7-1) unstable; urgency=low * New upstream release. * New maintainer. * Fix all packaging problems (closes: #703187, #703368). * Switch to dh_python2 (closes: #654272). * Update Standards-Version to 3.9.4 . [ Bart Martens ba...@debian.org ] * Update debian/watch . -- Laszlo Boszormenyi (GCS) g...@debian.hu Thu, 21 Mar 2013 00:39:38 +0100 ** Affects: python-gevent (Ubuntu) Importance: Wishlist Status: New ** Changed in: python-gevent (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-gevent in Ubuntu. https://bugs.launchpad.net/bugs/1181942 Title: Sync python-gevent 0.13.7-4 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-gevent/+bug/1181942/+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 1132526] Re: invaild encoding with .kr and .xn--3e0b707e domains
Additionally, the message from the old server is misleading. precise$ whois devunt.kr | less ... ECU+0083U+0081湲B0 ECA0U+0095蹂대U+008AU+0094 UTF-8 EC U+009D몄BDU+0094EBU+0094⑸U+0090U+0098ECU+0096B4 ECU+0084U+009C鍮U+0084ECU+008AㅻU+0090U+0098怨A0 ECU+009EU+0088EC U+008A듬U+008BU+0088EBU+008BA4. EUC-KR ECU+009D몄BDU+0094EBU+0094A9 ECU+0084U+009C鍮U+0084ECU+008AㅻU+008AU+0094 oldwhois.kisa.or.krECU+0097U+0090EC U+0084U+009C ECU+0084U+009C鍮U+0084ECU+008AA4 EBU+0090 U+0098怨A0 ECU+009EU+0088ECU+008A듬U+008BU+0088EBU+008B A4. The above information is encoded with UTF-8 EUC-KR encoding WHOIS is being serviced in this URL:oldwhois.kisa.or.kr - KISA/KRNIC Whois Service - lines 42-57/57 (END) In fact, this is identical to the output if you query with -h oldwhois.kisa.or.kr; if you use -h whois.kisa.or.kr you do get correct UTF-8 output (and the same message in the footer). precise$ apt-cache policy whois whois: Installed: 5.0.15ubuntu2 Candidate: 5.0.15ubuntu2 Version table: *** 5.0.15ubuntu2 0 500 http://fi.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/1132526 Title: invaild encoding with .kr and .xn--3e0b707e domains To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/1132526/+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 1132526] Re: invaild encoding with .kr and .xn--3e0b707e domains
(iconv tells me it cannot convert from EUC-KR to UTF-8 from the old input so I'm not sure if that's actually true, but the domain should be set up to use the new, well-defined server anyway.) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/1132526 Title: invaild encoding with .kr and .xn--3e0b707e domains To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/1132526/+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 1132526] Re: invaild encoding with .kr and .xn--3e0b707e domains
Upstream 5.0.23 fixed this issue. There is no separate upstream bug report. http://ftp- master.metadata.debian.org/changelogs/main/w/whois/unstable_changelog ** Changed in: whois (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/1132526 Title: invaild encoding with .kr and .xn--3e0b707e domains To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/1132526/+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 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
I believe a DKMS package can be set up for different module sources depending on the kernel version it is being built against (using patches). Does this help you? ** Description changed: - Package ist really outdated for kernel 3.5.0 (lts backport to precise) Modules not build: vmxnet vmhgfs vmblock See build log. + + Incomplete workaround: + + This bug affects those on a hardware enablement stack only, which is the + default option on the 12.04.2 images. If do not need the hardware + enablement stack, you may downgrade to the 3.2 kernel supplied with + 12.04 and 12.04.1, and then the package should build successfully. + + See https://wiki.ubuntu.com/Kernel/LTSEnablementStack of details of the + hardware enablement stacks. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: open-vm-dkms 2011.12.20-562307-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 DKMSKernelVersion: 3.5.0-18-generic Date: Tue Nov 27 18:53:46 2012 InstallationMedia: Kubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.2) MarkForUpload: True PackageArchitecture: all PackageVersion: 2011.12.20-562307-0ubuntu1 SourcePackage: open-vm-tools Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+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 1181743] Re: package apache2.2-common 2.2.22-6ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
From log: ERROR: Module alias not properly enabled: /etc/apache2/mods-enabled/alias.load is a real file, not touching it dpkg: errore nell'elaborare apache2.2-common (--configure): il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 dpkg: problemi con le dipendenze impediscono la configurazione di apache2-mpm-worker: apache2-mpm-worker dipende da apache2.2-common (= 2.2.22-6ubuntu5); comunque: Il pacchetto apache2.2-common non è ancora configurato. -- 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/1181743 Title: package apache2.2-common 2.2.22-6ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1181743/+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 1181743] Re: package apache2.2-common 2.2.22-6ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Thank you for your report. This looks like a local configuration problem, rather than a bug in Ubuntu, so I'm marking this bug as Invalid. Specifically, it looks like you've modified /etc/apache2/mods-enabled/, and created regular files instead of symlinks in there. It looks like the maintainer script is refusing to touch your custom changes as it cannot understand them, so you will need to fix up your Apache configuration yourself. You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community 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 rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: apache2 (Ubuntu) Status: New = Invalid -- 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/1181743 Title: package apache2.2-common 2.2.22-6ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1181743/+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 1181790] Re: looking in /usr/lib/cgi-bin instead of /etc/awstats
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I cannot reproduce this on awstats 7.0~dfsg-5 on Precise.
I did:
apt-get install awstats
/usr/lib/cgi-bin/awstats.pl -config=yourdomain.ext -update
I got:
Error: SiteDomain parameter not defined in your config/domain file. You must
edit it for using this version of AWStats.
Setup ('/etc/awstats/awstats.conf' file, web server or permissions) may be
wrong.
Check config file, permissions and AWStats documentation (in 'docs' directory).
So it looks like awstats.pl is looking in /etc/awstats as expected.
strace -eopen lists the following relevant file open attempts:
open(/usr/lib/cgi-bin/awstats.yourdomain.ext.conf, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/usr/lib/cgi-bin/awstats.conf, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(yourdomain.ext, O_RDONLY)= -1 ENOENT (No such file or directory)
open(/etc/awstats/awstats.yourdomain.ext.conf, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/etc/awstats/awstats.conf, O_RDONLY) = 3
open(/etc/awstats/awstats.conf.local, O_RDONLY) = 4
I then installed apache2, and set SiteDomain to example.com in
/etc/awstats/awstate.conf.
Then:
# /usr/lib/cgi-bin/awstats.pl -config=example.com -update
Create/Update database for config /etc/awstats/awstats.conf by AWStats
version 7.0 (build 1.971)
From data in log file /var/log/apache2/access.log...
Phase 1 : First bypass old records, searching new record...
Searching new records from beginning of log file...
Jumped lines in file: 0
Parsed lines in file: 0
Found 0 dropped records,
Found 0 comments,
Found 0 blank records,
Found 0 corrupted records,
Found 0 old records,
Found 0 new qualified records.
Note that www-data cannot read /var/log/apache2/ by default. Are you
sure that your problem isn't just that you should be running awstats.pl
-update as something that can read the logs? I just used the
documentation you pointed to.
If this turns out to be a local misconfiguration, please change the bug
status to Invalid. Otherwise, please set the bug status to New after you
have responded.
** Changed in: awstats (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to awstats in Ubuntu.
https://bugs.launchpad.net/bugs/1181790
Title:
looking in /usr/lib/cgi-bin instead of /etc/awstats
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1181790/+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 1181743] Re: package apache2.2-common 2.2.22-6ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Confirmed, not a bug, solved successfully :) Thanks! Karlo 2013/5/20 Robie Basak 1181...@bugs.launchpad.net Thank you for your report. This looks like a local configuration problem, rather than a bug in Ubuntu, so I'm marking this bug as Invalid. Specifically, it looks like you've modified /etc/apache2/mods-enabled/, and created regular files instead of symlinks in there. It looks like the maintainer script is refusing to touch your custom changes as it cannot understand them, so you will need to fix up your Apache configuration yourself. You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community 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 rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: apache2 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1181743 Title: package apache2.2-common 2.2.22-6ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 Status in “apache2” package in Ubuntu: Invalid Bug description: After install, Apache stopped with this error ProblemType: Package DistroRelease: Ubuntu 13.04 Package: apache2.2-common 2.2.22-6ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat May 18 20:08:30 2013 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 MarkForUpload: True SourcePackage: apache2 Title: package apache2.2-common 2.2.22-6ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1181743/+subscriptions -- 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/1181743 Title: package apache2.2-common 2.2.22-6ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1181743/+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 1181743] Re: package apache2.2-common 2.2.22-6ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Thanks for confirming. -- 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/1181743 Title: package apache2.2-common 2.2.22-6ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1181743/+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 1160372] Re: Login is not possible
Please let me know how to install fixed binary on Ubuntu 13.04 x64? Or where to download patched binary? -- 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/1160372 Title: Login is not possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+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 1160372] Re: Login is not possible
@Pascal This update is in -proposed, and is not yet released. I expect that the SRU team will release it soon after the minimum aging period of 7 days. For early access to the proposed fix, please see https://wiki.ubuntu.com/Testing/EnableProposed and please comment on the bug if there is a problem with the fixed package. See Brian's comment #41 for more details. ** Changed in: vsftpd (Ubuntu Raring) Status: Fix Released = Fix Committed -- 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/1160372 Title: Login is not possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+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
[Blueprint servercloud-s-simplestreams] simple streams work for 13.10
Blueprint changed by Scott Moser: Work items set to: Work items: server-side - make no races: TODO server-side - expire daily builds, removing only after some wait: TODO server-side - run check-url against exported formats and scream loudly on broken: TODO server-side - import scraping of archive for netboot images: TODO maas - make maas-import-ephemeral use simplestreams data: TODO maas - make maas-import-ephemeral clean old builds: TODO maas - cron jobs for import: TODO -- simple streams work for 13.10 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-simplestreams -- 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 1181334] Re: i386 required to install amd64
node in this case was most definitely known to maas and set to amd64/generic. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1181334 Title: i386 required to install amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181334/+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
[Blueprint servercloud-s-simplestreams] simple streams work for 13.10
Blueprint changed by Scott Moser: Work items changed: Work items: server-side - make no races: TODO server-side - expire daily builds, removing only after some wait: TODO server-side - run check-url against exported formats and scream loudly on broken: TODO - server-side - import scraping of archive for netboot images: TODO + server-side - import scraping of archive for netboot/installer images: TODO + server-side - publish netboot/installer images: TODO maas - make maas-import-ephemeral use simplestreams data: TODO maas - make maas-import-ephemeral clean old builds: TODO maas - cron jobs for import: TODO + update ask ubuntu question how-do-i-know-what-ubuntu-ami-to-launch-on-ec2 [1]: TODO + blog about simplestreams query: TODO -- simple streams work for 13.10 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-simplestreams -- 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
[Blueprint servercloud-s-simplestreams] simple streams work for 13.10
Blueprint changed by Scott Moser: Work items changed: Work items: server-side - make no races: TODO server-side - expire daily builds, removing only after some wait: TODO server-side - run check-url against exported formats and scream loudly on broken: TODO server-side - import scraping of archive for netboot/installer images: TODO server-side - publish netboot/installer images: TODO maas - make maas-import-ephemeral use simplestreams data: TODO maas - make maas-import-ephemeral clean old builds: TODO maas - cron jobs for import: TODO - update ask ubuntu question how-do-i-know-what-ubuntu-ami-to-launch-on-ec2 [1]: TODO + update ask ubuntu question how-do-i-know-what-ubuntu-ami-to-launch-on-ec2: TODO blog about simplestreams query: TODO -- simple streams work for 13.10 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-simplestreams -- 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 1181777] Re: kvm: freeze a guest with a NIC PCI passthrough
Thanks for reporting this bug. In order to help me reproduce it, could you please tell us in detail how you are attaching the NIC, and what OS/release is running inside the guest? ** Changed in: qemu-kvm (Ubuntu) Importance: Undecided = High ** Changed in: qemu-kvm (Ubuntu) Status: New = 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/1181777 Title: kvm: freeze a guest with a NIC PCI passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1181777/+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 1181136] Re: Empty log file when a container is started with the API
Thanks for reporting this bug. If you do c.set_config_item(lxc.log.loglevel', '1') before starting the container, does that help? Also, if you cause an actual error during startup (i.e. specify a wrong rootfs location in the configuration), does an error then at least show up in the logfile? If not, then that should be fixed. ** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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/1181136 Title: Empty log file when a container is started with the API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1181136/+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 1182085] [NEW] document lxc.loglevel and lxc.logfile in lxc.conf manpage
Public bug reported: lxc.conf(5) manpage needs to document lxc.loglevel and lxc.logfile. Also check for any other missing lines (by crossreferencing src/lxc/confile.c). ** Affects: lxc (Ubuntu) Importance: Low Status: Triaged ** Changed in: lxc (Ubuntu) Status: New = Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided = Low -- 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/1182085 Title: document lxc.loglevel and lxc.logfile in lxc.conf manpage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1182085/+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 1004606] Re: virsh create-snapshot fails to create external snapshot (blockdev-snapshot-sync fails in json monitor)
I found a that looks better than deactivating apparmor. I found here ( http://libvirt.org/drvqemu.html#securitysvirtaa ) the information that Apparmor is „just“ used for protecting the vm host and that there is a TEMPLATE under /etc/apparmor.d/libvirt/ that can be modified. In that TEMPLATE I included one of my own rules and under /etc/apparmor.d/local/usr.sbin.libvirtd i added a similar rule. -- 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/1004606 Title: virsh create-snapshot fails to create external snapshot (blockdev- snapshot-sync fails in json monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1004606/+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
[Blueprint servercloud-s-simplestreams] simple streams work for 13.10
Blueprint changed by Scott Moser: Work items changed: Work items: server-side - make no races: TODO server-side - expire daily builds, removing only after some wait: TODO server-side - run check-url against exported formats and scream loudly on broken: TODO server-side - import scraping of archive for netboot/installer images: TODO server-side - publish netboot/installer images: TODO maas - make maas-import-ephemeral use simplestreams data: TODO maas - make maas-import-ephemeral clean old builds: TODO maas - cron jobs for import: TODO + lxc - cron job for cloud-image sync: TODO update ask ubuntu question how-do-i-know-what-ubuntu-ami-to-launch-on-ec2: TODO blog about simplestreams query: TODO -- simple streams work for 13.10 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-simplestreams -- 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 1069849] Re: Containers show expired objects
Sorry, I meant a different bug. ** Also affects: devstack Importance: Undecided Status: New ** Changed in: devstack Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to swift in Ubuntu. https://bugs.launchpad.net/bugs/1069849 Title: Containers show expired objects To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1069849/+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 1181777] Re: kvm: freeze a guest with a NIC PCI passthrough
Hello. This is the step by step history of commands. The domain w is not rinnung. # virsh list --all Id Name State -- - wshut off There are all NICs on the host system # virsh nodedev-list --tree | grep -A 18 '+- pci__00_02_0' +- pci__00_02_0 | | | +- pci__03_00_0 | | | | | +- net_eth0_2c_76_8a_4f_45_00 | | | +- pci__03_00_1 | | | | | +- net_eth1_2c_76_8a_4f_45_01 | | | +- pci__03_00_2 | | | | | +- net_eth2_2c_76_8a_4f_45_02 | | | +- pci__03_00_3 | | | +- net_eth3_2c_76_8a_4f_45_03 Dump xml for eht1 # virsh nodedev-dumpxml pci__03_00_1 device namepci__03_00_1/name parentpci__00_02_0/parent driver nametg3/name /driver capability type='pci' domain0/domain bus3/bus slot0/slot function1/function product id='0x1657'NetXtreme BCM5719 Gigabit Ethernet PCIe/product vendor id='0x14e4'Broadcom Corporation/vendor capability type='virt_functions' /capability /capability /device Add the host device # virsh edit w ... hostdev mode='subsystem' type='pci' managed='yes' source address domain='0x' bus='0x03' slot='0x00' function='0x1'/ /source /hostdev ... Dettach the NIC from host # virsh nodedev-dettach pci__03_00_1 # virsh start w The image file of guest OS is not contain a OS, this is only a RAW partition. I'm trying to boot the guest with live cd ISO. But problem is while running seabios or iPXE (IMHO). Please, see the screenshot. ** Attachment added: VNC screenshot https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1181777/+attachment/3682131/+files/Screenshot%20of%20QEMU%20%28w%29.png -- 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/1181777 Title: kvm: freeze a guest with a NIC PCI passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1181777/+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 1166649] Re: Multiple open vulnerabilities in tomcat6 in quantal and raring
Sitting too long on this patch for quantal and could not really enable the testsuite I thought I just drop it here. Even with some hints from jamespage I could not run the built in tests and didn't really had enough time to look further in it. The changes are all done as in upstream and it builds and installs fine. Didn't see any problems from basic testing. ** Patch added: lp1166649-quantal.debdiff https://bugs.launchpad.net/ubuntu/+source/tomcat6/+bug/1166649/+attachment/3682137/+files/lp1166649-quantal.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat6 in Ubuntu. https://bugs.launchpad.net/bugs/1166649 Title: Multiple open vulnerabilities in tomcat6 in quantal and raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat6/+bug/1166649/+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 1173265] Re: facter fails to run from rebuilt source package
** Description changed: + [Impact] + + SRUs and security updates are impossible without breaking the package. + + [Development Fix] + + My merge of facter 1.7 drops most of the Ubuntu delta that is now no + longer necessary. This eliminates the problem. + + [Stable Fix] + + Build-Depend on ruby1.8 specifically, instead of the ruby virtual + package. The Quantal and Raring binaries in the archive were originally + built against ruby1.8 anyway, as this is what the ruby virtual package + brought in at the time of the build. With this minimal fix, the build + doesn't change to pulling in 1.9.1 instead and thus causing breakage. + + [Test Case] + + A dep8 smoke test has been added. If the problem is fixed, the dep8 test + should pass. + + Failing this, just run facter. If you get a bunch of facts printed + out, then the problem is fixed. Note that to test this properly, you + should start by not having ruby1.9.1 installed. + + The two failure possibilities are: + + # facter + /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- facter/application (LoadError) + from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' + from /usr/bin/facter:58:in `main' + + # facter + bash: /usr/bin/facter: /usr/bin/ruby1.9.1: bad interpreter: No such file or directory + + [Regression Potential] + + The build could have accidentally changed other things apart from the + original Ruby 1.8 dependency since the original build. But since + facter on its own prints all known facts, it is easy to confidently + verify that factor's fact-detection behaviour has not changed + unexpectedly after an update. + + [Original Description] + If I rebuild 1.6.9-2ubuntu1 in a raring chroot, then when I attempt to run facter I get an error: - $ sudo dpkg -i facter_1.6.9-2ubuntu1_all.deb + $ sudo dpkg -i facter_1.6.9-2ubuntu1_all.deb (Reading database ... 77464 files and directories currently installed.) Preparing to replace facter 1.6.9-2ubuntu1 (using facter_1.6.9-2ubuntu1_all.deb) ... Unpacking replacement facter ... Setting up facter (1.6.9-2ubuntu1) ... Processing triggers for man-db ... ubuntu@raring-test:~$ facter -bash: /usr/bin/facter: /usr/bin/ruby1.9.1: bad interpreter: No such file or directory The problem is that /usr/bin/facter gets a shebang of #!/usr/bin/ruby1.9.1 after the rebuild, rather than the #!/usr/bin/ruby1.8 shebang in the binary in the archive. It looks like this might have happened after the ruby metapackage was updated to 4.9 which changed the default ruby to 1.9 from 1.8, causing the facter package build to turn out differently. It also looks like Debian's facter 1.6.10-1 rejigged some of the ruby versioning, so I suspect that the problem can be fixed in Saucy with a simple merge. But I suspect that an attempted SRU to Quantal or Raring will cause a regression unless this bug is fixed there. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/1173265 Title: facter fails to run from rebuilt source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+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 1170325] Re: Facter 1.6.X not considering Qemu/KVM virtual type
** Description changed:
+ [Impact]
+
+ facter recognises a /proc/cpuinfo CPU model of Common KVM processor as
+ a physical machine. facter is most often used with puppet, and causes
+ puppet manifests to mis-classify virtual machines of this type and apply
+ incorrect rules where the puppet manifests supplied by system
+ administrators differ on this criterion.
+
+ [Stable and Development Fix]
+
+ A cherry-pick of the upstream fix, modified to be made minimal (one
+ line). See the quilt patch for details.
+
+ [Test Case 1]
+
+ Run facter is_virtual. On a physical machine, this should say false.
+ On a virtual machine reporting in /proc/cpuinfo as QEMU Virtual CPU as
+ well as a virtual machine reporting in /proc/cpuinfo as Common KVM
+ Processor, facter is_virtual should say true.
+
+ [Test Case 2]
+
+ As a shortcut, on Quantal and Raring you can fake the /proc/cpuinfo file
+ as follows:
+
+ mkdir -p /tmp/proc/{lower,upper,combined}
+ cd /tmp/proc
+ mount -t proc none lower
+ mount -t tmpfs -o mode=755 none upper
+ mount -t overlayfs -o lowerdir=lower,upperdir=upper none combined
+ stop rsyslogd
+ stop acpid
+ umount /proc mount --bind combined /proc
+
+ Then you can edit /proc/cpuinfo and run facter to test behaviour as per
+ Test Case 1.
+
+ This is a hack and does not appear to work correctly in Precise.
+
+ [Regression Potential]
+
+ It looks like detection of other model strings in /proc/cpuinfo may have
+ regressed upstream, fixed by a later commit. It's important to test that
+ both model strings of QEMU Virtual CPU and Common KVM processor
+ detect as virtual, and that another string (eg. Other) detects as
+ physical.
+
+ [Original Description]
+
On ubuntu 12.04 LTS, the official version for the facter package is
1.6.5-ubuntu1.
ii facter 1.6.5-1ubuntu1 collect and display facts about the system
The is_virtual? method is not recognized on last version of KVM, because
of the output of /proc/cpuinfo, which does not contains “Qemu Server”
Infos.
model name : Common KVM processor
The workaround was added in the next versions of facter, and so I would
like to provide you this patch, which fixes this bug on Ubuntu 12.04
LTS.
Best regards
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/1170325
Title:
Facter 1.6.X not considering Qemu/KVM virtual type
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1170325/+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 1173265] Re: facter fails to run from rebuilt source package
** Patch added: precise.debdiff https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+attachment/3682152/+files/precise.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/1173265 Title: facter fails to run from rebuilt source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+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 1173265] Re: facter fails to run from rebuilt source package
** Patch added: quantal.debdiff https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+attachment/3682153/+files/quantal.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/1173265 Title: facter fails to run from rebuilt source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+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 1173265] Re: facter fails to run from rebuilt source package
The above debdiffs additionally contain a fix for bug 1170325 - hence the precise debdiff which doesn't actually apply to this bug itself. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/1173265 Title: facter fails to run from rebuilt source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+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 1173265] Re: facter fails to run from rebuilt source package
Attached is an updated merge against Debian facter 1.7.0-1. ** Patch added: saucy-v2.debdiff https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+attachment/3682156/+files/saucy-v2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/1173265 Title: facter fails to run from rebuilt source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+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 1173265] Re: facter fails to run from rebuilt source package
** Patch added: raring.debdiff https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+attachment/3682154/+files/raring.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/1173265 Title: facter fails to run from rebuilt source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+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 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled
davewalker - can we get this packaged for precise as well? ** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1167421 Title: Upgrading from folsom to grizzly results in all tenants/users being disabled To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1167421/+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
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO + Work items for ubuntu-13.05: + [jorge] : Highlight Places where people can contribute: TODO + Work items: - [jorge] : Highlight Places where people can contribute: TODO [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
You mean I have to revert the (/debian) DKMS files from Raring-Precise. Yeah I figured that out. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+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 1160372] Re: Login is not possible
Upgrading from 32bit 3.0.2-1ubuntu1 to 3.0.2-1ubuntu1.1 fixes this bug for me. I'm using 32bit Ubuntu 13.04. -- 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/1160372 Title: Login is not possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+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 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
Looking at my notes I have to add some stuff back to the DKMS files. Make a few changes to debian/control. My goal is to make this update the first upload as the official maintainer of the package, I just have to send e-mails to sponsors for testimonials. Timetable: a month, testimonials will probably take like a week. I just want to get the 1st Saucy proposal submitted and approved, and that will take a couple of weeks I hope you understand. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+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 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled
Joseph- The 2013.1.1 update has also been backported to precise via the Ubuntu Cloud Archive. It is currently sitting in the precise- grizzly/proposed pocket and will be released into the main, precise- grizzly/updates pocket when the corresponding 2013.1.1 update for Raring passes verification. Watch here or subscribe to Bug #1179626 to track progress. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1167421 Title: Upgrading from folsom to grizzly results in all tenants/users being disabled To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1167421/+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 1182240] [NEW] Brazilian Portuguese language errorpage directory
Public bug reported: On version 3.1.20, the Brazilian Portuguese language abbreviation is defined as pt-bz instead of pt-br in errorpage.cc. Of course this can be solved with error_default_language option in squid.conf (http://wiki.squid-cache.org/Translations), however the abbreviation pt-bz does not exist. root@vm03:~# echo $LC_NAME pt_BR root@vm03:~# egrep -e errorpage|Language /var/log/squid3/cache.log|tail -3 2013/05/20 18:08:46| errorpage.cc(293) errorTryLoadText: '/usr/share/squid3/errors/pt-bz/ERR_DNS_FAIL': (2) No such file or directory 2013/05/20 18:08:46| WARNING: Error Pages Missing Language: pt-bz 2013/05/20 18:09:06| errorpage.cc(293) errorTryLoadText: '/usr/share/squid3/errors/pt-bz/ERR_DNS_FAIL': (2) No such file or directory root@vm03:~# ls -d /usr/share/squid3/errors/pt* /usr/share/squid3/errors/pt /usr/share/squid3/errors/pt-br /usr/share/squid3/errors/pt-pt ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Tags: internationalization language translation ** Description changed: On version 3.1.20, the Brazilian Portuguese language abbreviation is defined as pt-bz instead of pt-br in errorpage.cc. Of course this can be solved with error_default_language option in squid.conf (http://wiki.squid-cache.org/Translations), however the abbreviation pt-bz does not exist. root@vm03:~# echo $LC_NAME pt_BR - root@vm03:~# egrep -e errorpage|Language /var/log/squid3/cache.log | tail -4 + root@vm03:~# egrep -e errorpage|Language /var/log/squid3/cache.log|tail -3 2013/05/20 18:08:46| errorpage.cc(293) errorTryLoadText: '/usr/share/squid3/errors/pt-bz/ERR_DNS_FAIL': (2) No such file or directory 2013/05/20 18:08:46| WARNING: Error Pages Missing Language: pt-bz 2013/05/20 18:09:06| errorpage.cc(293) errorTryLoadText: '/usr/share/squid3/errors/pt-bz/ERR_DNS_FAIL': (2) No such file or directory root@vm03:~# ls -d /usr/share/squid3/errors/pt* /usr/share/squid3/errors/pt /usr/share/squid3/errors/pt-br /usr/share/squid3/errors/pt-pt -- 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/1182240 Title: Brazilian Portuguese language errorpage directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1182240/+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 1182247] [NEW] check_ide_smart fails with i/o error
Public bug reported: It would seem that check_ide_smart is defunct on my server, giving the following results when run manually: sune@jadis:~$ sudo /usr/lib/nagios/plugins/check_ide_smart -d /dev/sda -i -n CRITICAL - SMART_ENABLE: Input/output error CRITICAL - SMART_CMD_ENABLE Normal SMART commands via smartctl show no problems. As for the list: 1) sune@jadis:~$ lsb_release -rd Description:Ubuntu 13.04 Release:13.04 2) sune@jadis:~$ apt-cache policy nagios-plugins nagios-plugins: Installed: 1.4.16-1ubuntu3 Candidate: 1.4.16-1ubuntu3 Version table: *** 1.4.16-1ubuntu3 0 500 http://dk.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status 3) Correct SMART status output 4) What I started by writing. I shall be happy to answer any and all questions and to try out any and all patches. Best regards, Sune Mølgaard ** Affects: nagios-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1182247 Title: check_ide_smart fails with i/o error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1182247/+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 1182265] [NEW] omnibus installation support is broken
Public bug reported: cloud-init fails to install the Chef client via 'omnibus' installer, support for which was added in the following change: http://bazaar.launchpad.net/~cloud-init-dev/cloud- init/trunk/revision/749 Here 'content' is a UrlRequest object, but util.write_file() dies with an exception due to a debug statement. The proposed fix is to convert the UrlReponse into a plain string and pass that to util.write_file(), which makes things work as expected. [the above copied from MP at https://code.launchpad.net/~wingc/cloud- init/fix-chef-omnibus-install/+merge/164810 . Thank you Christopher] ** Affects: cloud-init Importance: High Status: Confirmed ** Affects: cloud-init (Ubuntu) Importance: High Status: Confirmed ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init Status: New = Confirmed ** Changed in: cloud-init (Ubuntu) Status: New = Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided = High ** Changed in: cloud-init Importance: Undecided = High ** Branch linked: lp:~wingc/cloud-init/fix-chef-omnibus-install -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1182265 Title: omnibus installation support is broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1182265/+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 1182265] Re: omnibus installation support is broken
** Branch linked: lp:cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1182265 Title: omnibus installation support is broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1182265/+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 1182265] Re: omnibus installation support is broken
fixed upstream in revision 819. ** Changed in: cloud-init Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1182265 Title: omnibus installation support is broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1182265/+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 1160372] Re: Login is not possible
Confirm working vsftpd_3.0.2-1ubuntu1.1_amd64.deb. -- 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/1160372 Title: Login is not possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+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 1181334] Re: i386 required to install amd64
On Monday 20 May 2013 12:58:13 you wrote: node in this case was most definitely known to maas and set to amd64/generic. It might be something that broke recently then :( I've been installing amd64 on my own nodes without downloading i386 images. I'll try to re-create. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1181334 Title: i386 required to install amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181334/+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 1158170] Re: smbd 3.6.3 panic
[Expired for samba (Ubuntu) because there has been no activity for 60 days.] ** Changed in: samba (Ubuntu) Status: Incomplete = Expired -- 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/1158170 Title: smbd 3.6.3 panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1158170/+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 1156742] Re: Horizon layout problem on IE 10
[Expired for horizon (Ubuntu) because there has been no activity for 60 days.] ** Changed in: horizon (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1156742 Title: Horizon layout problem on IE 10 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1156742/+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
