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
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.
(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
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
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
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
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
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
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
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
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
@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
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
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
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
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
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:
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?
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 =
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
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
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.
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 '+-
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
** 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
** 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
** 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.
** 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.
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.
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
** 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.
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.
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
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
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
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
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.
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
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
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
** 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
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
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:
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
[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.
[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.
46 matches
Mail list logo