What's the status of this getting into lucid-updates?
--
[SRU] multipath + libvirtd eats away more memory over time
https://bugs.launchpad.net/bugs/571093
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
What's the status of this getting into lucid-updates?
--
[SRU] multipath + libvirtd eats away more memory over time
https://bugs.launchpad.net/bugs/571093
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug still exists on Karmic with the most recent kernel installed as
well as on the current version of Lucid, as mentioned above by GuyR.
Jun 17 22:34:40 chirashi kernel: [ 470.887650] CONFIG_NF_CT_ACCT is deprecated
and will be removed soon. Please useJun 17 22:34:40 chirashi kernel: [
Marked as new since the requested information was provided earlier.
--
config_nf_ct_acct deprecated (Intrepid Karmic kernel)
https://bugs.launchpad.net/bugs/296024
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Lucid is out, what is the status of this bug? Looking at the changelog
it doesn't look like this was fixed before release.
--
--firstboot option broken in 0.12.2-0ubuntu3
https://bugs.launchpad.net/bugs/536942
You received this bug notification because you are a member of Ubuntu
Server Team,
Lucid is out, what is the status of this bug? Looking at the changelog
it doesn't look like this was fixed before release.
--
--firstboot option broken in 0.12.2-0ubuntu3
https://bugs.launchpad.net/bugs/536942
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: opennebula
Please update the OpenNebula packages to the current stable version.
Thank you.
** Affects: opennebula (Ubuntu)
Importance: Undecided
Status: New
--
New upstream release (1.4)
https://bugs.launchpad.net/bugs/510904
You
Steps 1, 2, and 3 are now in the bug description as well.
** Description changed:
- On a fresh install of Intrepid Server drbd is not started on system
- boot. However, manually running /etc/init.d/drbd start works fine. I
- noticed that the startup link in /etc/rc2.d/ is missing. After running
Steps 1, 2, and 3 are now in the bug description as well.
** Description changed:
- On a fresh install of Intrepid Server drbd is not started on system
- boot. However, manually running /etc/init.d/drbd start works fine. I
- noticed that the startup link in /etc/rc2.d/ is missing. After running
I see the fixed package is in the current development version of Ubunut
(jaunty). Will a fixed package be rolled out to intrepid (or intrepid-
updates or intrepid-backports)?
--
drbd doesn't start on boot
https://bugs.launchpad.net/bugs/282876
You received this bug notification because you are a
I see the fixed package is in the current development version of Ubunut
(jaunty). Will a fixed package be rolled out to intrepid (or intrepid-
updates or intrepid-backports)?
--
drbd doesn't start on boot
https://bugs.launchpad.net/bugs/282876
You received this bug notification because you are a
As usual, I've made the patched packages available via my company's apt
repository.
Add these lines to your /etc/apt/sources.list:
deb http://packages.devsuki.com/ubuntu/ intrepid main
deb-src http://packages.devsuki.com/ubuntu/ intrepid main
Grab the public signing key:
$ wget
As usual, I've made the patched packages available via my company's apt
repository.
Add these lines to your /etc/apt/sources.list:
deb http://packages.devsuki.com/ubuntu/ intrepid main
deb-src http://packages.devsuki.com/ubuntu/ intrepid main
Grab the public signing key:
$ wget
the LSB headers from this
script as they are breaking the expected function of update-rc.d.
.:. brainsik
--
drbd doesn't start on boot
https://bugs.launchpad.net/bugs/282876
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in ubuntu
Patched. I decided to just change the start/stop lines to match the
update-rc.d defaults.
Debdiff attached.
** Attachment added: Bugfix.
http://launchpadlibrarian.net/20236785/drbd8_8.2.6-2ubuntu2.debdiff
--
drbd doesn't start on boot
https://bugs.launchpad.net/bugs/282876
You received
the LSB headers from this
script as they are breaking the expected function of update-rc.d.
.:. brainsik
--
drbd doesn't start on boot
https://bugs.launchpad.net/bugs/282876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Patched. I decided to just change the start/stop lines to match the
update-rc.d defaults.
Debdiff attached.
** Attachment added: Bugfix.
http://launchpadlibrarian.net/20236785/drbd8_8.2.6-2ubuntu2.debdiff
--
drbd doesn't start on boot
https://bugs.launchpad.net/bugs/282876
You received
Dunno. I stopped using the Ubuntu packages when it became clear no one
cared about the patch I made. The process of:
1) fix bug
2) make debdiff according to MOTU/SRU wiki page
3) join #ubuntu-motu IRC channel and bug people until someone actually does
something with debdiff
is not working for
If you want, you can grab the release I just rolled out. It is the
latest revision (revision 49) of lp:trac-bzr. It also includes a patch
get rid of this _get_weave bug.
You can get via apt:
# DevSuki packages (backports, fixes, etc.)
deb http://packages.devsuki.com/ubuntu/ hardy main
deb-src
Tried it, and now I get a different error:
AttributeError: 'KnitPackRepository' object has no attribute
'get_revision_graph'
--
Does not work with bzr 1.6
https://bugs.launchpad.net/bugs/263300
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Do you know if this was actually tested for Gutsy - Hardy? Or if this
was fixed for Feisty - Gutsy? Why has this bug been closed?
--
Could not install the upgrades: Errors on libstonith0 and libpils0
https://bugs.launchpad.net/bugs/174154
You received this bug notification because you are a
All I can say is I haven't experienced it in any of the kernels shipped
since this one. Whether it still happens in this particular kernel, I do
not know, I left it a while ago.
--
Oops: 0002 [#1] (Process ntpd)
https://bugs.launchpad.net/bugs/69751
You received this bug notification because you
This shows Apache listening on 80 and 443 and that `/etc/init.d/apache2
stop` works just fine:
# netstat -tlnp | grep apache
tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN
1632/apache2
tcp0 0 0.0.0.0:443 0.0.0.0:*
I did some more research and my guess is that what's happening is you
may have long-lived connections to your apache processes that are
preventing them from dying in a timely manner. If you are hosting large
downloads I think this would happen. Haven't tested. For my sites, I
prefer the
It's unclear what you want me to try. In the report above it shows I was
doing the following export:
export http_proxy=172.16.1.1:
What exactly do you want me to try?
Also, the next time I'll be doing this is when I go from gutsy - hardy.
I've already upgraded all of the machines here
Re: traceback -- I believe that's all the output I received. I doubt I
would have truncated it myself.
--
do-release-upgrade gives Traceback when using a proxy
https://bugs.launchpad.net/bugs/162996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
It's not an issue for me in that I figured out how to finish the upgrade
process after upgrade-manager bails out. I had to hack around this on
all machines with heartbeat installed. However, this bug is still a
serious problem: anyone who does a feisty - gusty upgrade with
heartbeat installed will
mostly irrelevant [2].
I'm not going to fix and reupload this.
.:. brainsik
p.s. The fix you want is to a single word in the changelog version. It
probably took the same amount of time to reject the package and post a
comment as it would have taken to edit the patch and accept the package.
[1
I ended up quickly porting the old Filesystem resource from heartbeat 1
and am using that for now. I'll use that until I see a patch for the OCF
script. I'm wary of posting my ported file since it's a bit hackish and
is certainly not a solution to the real problem.
--
Filesystem resource script
Public bug reported:
Setting up apparmor-utils (2.1+993-0ubuntu3) ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.22-14-server
Errors were encountered while
** Attachment added: apt-autoinst-fixup.log
http://launchpadlibrarian.net/10746999/apt-autoinst-fixup.log
--
Could not install the upgrades: Errors on libstonith0 and libpils0
https://bugs.launchpad.net/bugs/174154
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: apt.log
http://launchpadlibrarian.net/10747001/apt.log
--
Could not install the upgrades: Errors on libstonith0 and libpils0
https://bugs.launchpad.net/bugs/174154
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: main_pre_req.log
http://launchpadlibrarian.net/10747003/main_pre_req.log
--
Could not install the upgrades: Errors on libstonith0 and libpils0
https://bugs.launchpad.net/bugs/174154
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
** Attachment added: main.log
http://launchpadlibrarian.net/10747002/main.log
--
Could not install the upgrades: Errors on libstonith0 and libpils0
https://bugs.launchpad.net/bugs/174154
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
Binary package hint: heartbeat-2
When upgrading from feisty to gutsy, the new heartbeat fails to start
because the Filesystem resource script that comes with it is broken:
ResourceManager[6887]: 2007/12/05_07:03:48 info: Running
/etc/ha.d/resource.d/Filesystem /dev/drbd0
updated debdiff to be applied against recent security release.
** Attachment added: zabbix_1.4.1-2ubuntu0.2.debdiff
http://launchpadlibrarian.net/10641868/zabbix_1.4.1-2ubuntu0.2.debdiff
--
db_type is set to MYSQL even when using zabbix-server-pgsql
https://bugs.launchpad.net/bugs/161083
Since my security patch was accepted and released the zabbix version got
bumped. Here is a new debdiff applied against the current release.
** Attachment added: zabbix_1.4.1-2ubuntu0.2.debdiff
http://launchpadlibrarian.net/10626183/zabbix_1.4.1-2ubuntu0.2.debdiff
--
zabbix 1.4.1-2 hardcoded
Public bug reported:
Binary package hint: update-manager-core
Trying to upgrade some machines deep inside a network. I have to use an
HTTP proxy so do-release-upgrade can get do it's network thing. This is
what happens:
# export http_proxy=172.16.1.1:
# do-release-upgrade
Checking for a
Attached is a debdiff which solves this problem. I added postgresql-8.2
as a preferred alternative to postgresql-8.1. Either will be used if
they are already installed.
** Attachment added: zabbix_1.4.1-2ubuntu0.1.debdiff
Public bug reported:
Discussion of this bug can be found in Debian's bug tracker:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435609
The problem is zabbix-frontend-php uses priority medium to ask the
user which kind of DB they are using but by default Ubuntu debconf only
asks questions of
The debdiff is attached. I tested the package and it works great.
There were no instructions for how to build the debdiff on the page you
provided above. I had to assume it should be run against the .dsc files
as the other methods didn't provide useful info.
$ debdiff zabbix_1.4.1-2.dsc
debdiff attached. It's in the spirit of the Debian fix: checks for /etc
/dbconfig-common/zabbix-server-{my,pg}sql files and sets db_type
accordingly. It falls back to previous behaviour if those files don't
exist.
This fixes the problem if the frontend and server packages are installed
on the
I've also been bit by this. The package page on Gutsy
http://packages.ubuntu.com/gutsy/mail/maildrop says maildrop depends
on courier-authlib *except* for amd64. Ralf's initial report above shows
he is using an amd64 package, as am I. Why is this marked as not a
dependency for amd64 systems?
For
FWIW, my zabbix source packages can be found here:
deb-src http://packages.devsuki.com/ubuntu/ edgy main
--
1.1.4 has critical postgres bug
https://launchpad.net/bugs/99219
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Version 1.1.4 has a bug which makes it impossible to create a host
linked to a template. Aside from making it impossible to follow the
Zabbix tutorial, not being able to link to templates makes using Zabbix
EXTREMELY difficult as you would have to manually setup all of the
new debdiff
* changed the change description.
* incremented the version NMU style (adding .1) and appended ~prop1 per the
MOTU/SRU page.
** Attachment added: debdiff for proposed drbd0.7 package
http://librarian.launchpad.net/6373724/drbd0.7_0.7.20-1.1%7Eprop1.debdiff
--
[SRU] change of
new debdiff
* fixed spelling :-)
** Attachment added: debdiff for proposed drbd0.7 package
http://librarian.launchpad.net/6385419/drbd0.7_0.7.20-1.1%7Eprop1.debdiff
--
[SRU] change of /bin/sh to dash in edgy breaks drbd0.7-module-source build
https://launchpad.net/bugs/68481
--
attaching debdiff
** Attachment added: ~prop1 debdiff
http://librarian.launchpad.net/6331257/drbd0.7_0.7.20-1%7Eprop1.debdiff
--
change of /bin/sh to dash in edgy breaks drbd0.7-module-source build
https://launchpad.net/bugs/68481
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This also breaks the drbd0.7-module-source package so that it's
compilation fails.
I suppose this is the perogative of the DASH author(s), but it breaks
the -e option convention used by both the BASH builtin as well as the
/bin/echo program.
--
dash echo -e echoes -e
Public bug reported:
Binary package hint: drbd0.7-module-source
With the change from BASH to DASH for /bin/sh, the DRBD Makefile breaks
in two places.
In the first change, the dash builtin echo command does not understand
'-e', instead printing it out. Removing '-e' fixes this as the dash
*** This bug is a duplicate of bug 68481 ***
** This bug has been marked a duplicate of bug 68481
change of /bin/sh to dash in edgy breaks drbd0.7-module-source build
--
(edgy) drbd0.7-module-source: module will not compile
https://launchpad.net/bugs/76677
--
ubuntu-bugs mailing list
This patch shows how to fix the bashisms in the Makefile.
** Attachment added: Removes bashisms
http://librarian.launchpad.net/5502797/drbd0.7-module-source.patch
--
change of /bin/sh to dash in edgy breaks drbd0.7-module-source build
https://launchpad.net/bugs/68481
--
ubuntu-bugs
I propose this be an SRU.
The bug renders this package unusable since you can't actually build the
module. It does not appear to be fixed in feisty. I attached a patch to
remove the bashisms causing the broken behaviour.
--
change of /bin/sh to dash in edgy breaks drbd0.7-module-source build
Here's an example of how removing libjpeg62 breaks python-imaging. The
main problem is libjpeg62 was a dependency in dapper, but is not in
edgy, so upgrading via aptitude causes libjpeg62 to be removed as
unused. This broke the web app running on the server being upgraded.
Without libpq4, the python-psycopg module can't even be imported:
suki2:~$ python
Python 2.4.4c1 (#2, Oct 11 2006, 21:51:02)
[GCC 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)] on linux2
Type help, copyright, credits or license for more information.
import psycopg
suki2:~$ sudo dpkg -r
Public bug reported:
There are no dependencies on the following packages:
libc6, libfreetype6, libjpeg62, zlib1g
These are all critical to the function of this package. This bug is very
similar to the one i posted about python-psycopg. It's like the dapper
package python2.4-imaging was moved to
Public bug reported:
Ubuntu edgy changed /bin/sh from bash (in dapper) to dash. With this
change, the let keyword is no longer understood and the cron package
fails to execute a valid sleep command:
/etc/cron.daily/apticron:
/etc/cron.daily/apticron: 6: let: not found
sleep: missing operand
Try
Public bug reported:
Package: python-psycopg
Version: 1.1.21-7
Severity: grave
Justification: renders package unusable
It seems there are a couple of serious missing dependencies: libc6 and
libpq4. Though libc6 will already be availble due to other package
dependencies, libpq4 may not.
This
Public bug reported:
Here is the reportbug bug I sent in. It's unclear whether or not
reportbug should be used to report bugs, even though it ships standard.
Package: linux-image-2.6.15-27-server
Version: 2.6.15-27.48
Severity: important
ntpd made the kernel oops last night. the kernel reports
59 matches
Mail list logo
