I'm going to go ahead and unsubscribe ubuntu-sponsors from this bug -
branch merge requests are automatically added to the sponsorship queue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
The broken code was moved into a different file in Lucid, and the
mistyped mask was fixed as well.
This problem only affects Karmic, and only if you explicitly specify an
IP address, don't specify a netmask, and give an IP address whose first
octet is between 128 and 192 (non-inclusive)
**
** Branch linked: lp:~serge-hallyn/ubuntu/maverick/multipath-tools/fix-
crash-on-shutdown
--
multipathd segfault
https://bugs.launchpad.net/bugs/488285
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in ubuntu.
--
You could potentially work around the regex misinterpretation issue by
using some more complex combinations of grep and awk and so forth, but
there's a better reason to not use getent | grep.
If /etc/nsswitch.conf is configured with a user or group database that
doesn't support enumerating users
Oh wait...I'm supposed to un-assign it to myself? *sigh* So confusing :)
** Changed in: ubuntu
Status: New = Confirmed
** Changed in: ubuntu
Assignee: (unassigned) = Evan Broder (broder)
** Package changed: ubuntu = krb5 (Ubuntu)
** Changed in: krb5 (Ubuntu)
Assignee: Evan
Public bug reported:
Please sync kerberos-configs 2.2 (main) from Debian unstable (main)
Explanation of FeatureFreeze exception:
kerberos-configs currently includes the krb4-config package in
Ubuntu. Since Karmic contains krb5 version 1.7, which doesn't come
with krb4, it doesn't make sense to
Hmm...apparently not - I would have expected the package to fail to
install, but it seems to just provide a useless configuration. Oh well -
this can wait until Lucid.
** Changed in: kerberos-configs (Ubuntu)
Status: Incomplete = Invalid
--
FFe: Sync kerberos-configs 2.2 (main) from
This is a bug in the packages that still depend on libkrb53, not krb5
itself. root-system is one of only two that still have this problem.
** Changed in: krb5 (Ubuntu)
Status: New = Invalid
--
missing binary transition package libkrb53
https://bugs.launchpad.net/bugs/464426
You received
*** This bug is a duplicate of bug 462059 ***
https://bugs.launchpad.net/bugs/462059
** This bug has been marked a duplicate of bug 462059
libkrb53 package required instead of libkrb5-3 in Karmic
--
root-system-rootd has missing dependencies
https://bugs.launchpad.net/bugs/477315
You
This shouldn't be a problem. We're still in sync phase for Ubuntu
Lucid, so the new krb5 package will get automatically pulled in when
it hits Debian testing.
On Mon, Nov 30, 2009 at 3:25 PM, Sam Hartman hartm...@debian.org wrote:
I released 1.7+dfsg-3 to Debian unstable. That includes a fix to
I think the patch is a little extensive to be directly uploaded as a
Karmic SRU, but I'll look at pulling a SRU patch together for just the
bugfixes.
** Changed in: krb5 (Ubuntu)
Status: Confirmed = In Progress
** Changed in: krb5 (Ubuntu)
Assignee: (unassigned) = Evan Broder (broder
** Changed in: krb5 (Ubuntu)
Status: Incomplete = Invalid
--
package libkrb5-dev 1.6.dfsg.4~beta1-3 failed to install/upgrade: failed to
delete `/usr/lib/libkrb5support.so.dpkg-tmp': Read-only file system
https://bugs.launchpad.net/bugs/341432
You received this bug notification because
%7Ebeta3-1ubuntu0.1.debdiff
** Changed in: krb5 (Ubuntu)
Status: In Progress = Confirmed
** Changed in: krb5 (Ubuntu)
Assignee: Evan Broder (broder) = (unassigned)
--
Strange behavior of libkrb5 since karmic ...
https://bugs.launchpad.net/bugs/489418
You received this bug notification
** Changed in: open-vm-tools (Ubuntu)
Status: Confirmed = In Progress
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) = Evan Broder (broder)
--
should build kernel modules with dkms
https://bugs.launchpad.net/bugs/277556
You received this bug notification because you
grexk: thanks for the patch. A few nits for future reference:
- LP closers are generally of the form (LP: #nn) - you didn't have the hash
- It looks like you added a superfluous line to set SRC_VERSION in debian/rules
- Your version number was appropriate for a PPA upload, but not for
I don't see how this is a bug. Debian and Ubuntu in general try to
enable as many features of software packages as they can, almost
everything has Kerberos authentication of some form or another as a
feature, and because of how libraries and Debian dependencies work,
anything that /supports/
Here's my last debdiff rebased on top of the recent security update.
I've also dispatched builds to my PPA
(https://launchpad.net/~broder/+archive/ubuntu-tests), which should be
running shortly.
** Attachment added: krb5_1.7dfsg~beta3-1ubuntu0.2.debdiff
It sounds like the secd you're using only supports single DES. Single
DES has been deprecated for over 10 years now as a cipher, due to its
very short key length. I would highly encourage you to upgrade your
infrastructure to a more secure encryption type.
If you simply must continue using your
** Also affects: nagios3 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: nagios3 (Ubuntu Precise)
Status: New = Confirmed
** Changed in: nagios3 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of
** Description changed:
- Description: Ubuntu 12.04.2 LTS
- Release: 12.04
+ [Impact]
+ Under nagios 3.2.3 with state retention enabled, any host aliases or display
names assigned to a host would be persisted into the retention file, and would
supersede subsequent configuration changes.
Public bug reported:
I have a cluster which is using a isolated back-end network for
clustering-related communication (iSCSI, cman, CLVM, etc). Instead of
using the hostnames of the nodes for the node names, I am configuring
the nodes to all use hostname-internal. I have an /etc/hosts file on
Public bug reported:
When I shut down a node, and then boot it back up, LVM metadata
operations hang after it has rejoined the cluster.
Currently, when I'm booting up all 3 nodes in my cluster fresh, LVM
works fine.
When I shut down one of the nodes cleanly (so that the cluster remains
** Attachment added: strace of an lvchange operation on the hung cluster
http://launchpadlibrarian.net/19503053/strace-lvchange.txt
--
metadata operations hang after node outage
https://bugs.launchpad.net/bugs/295836
You received this bug notification because you are a member of Ubuntu
Bugs,
Blargh. I'm having really bad luck with my bugs vanishing as soon as I
report them.
** Changed in: redhat-cluster (Ubuntu)
Status: New = Invalid
--
fence_tool times out on joining fence group
https://bugs.launchpad.net/bugs/295092
You received this bug notification because you are a
** Description changed:
+ Binary package hint: clvm
+
When I shut down a node, and then boot it back up, LVM metadata
operations hang after it has rejoined the cluster.
Currently, when I'm booting up all 3 nodes in my cluster fresh, LVM
works fine.
When I shut down one of the
** Attachment added: stracing clvmd as another node comes back up
http://launchpadlibrarian.net/19506900/clvmd-strace.txt
--
metadata operations hang after node outage
https://bugs.launchpad.net/bugs/295836
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
Binary package hint: clvm
When I shut down a node, and then boot it back up, LVM metadata
- operations hang after it has rejoined the cluster.
+ operations hang after it has rejoined the cluster, unless I restart
+ clvmd (by sending it a SIGKILL first).
** Description changed:
- I have a cluster which is using a isolated back-end network for
- clustering-related communication (iSCSI, cman, CLVM, etc). Instead of
- using the hostnames of the nodes for the node names, I am configuring
- the nodes to all use hostname-internal. I have an /etc/hosts
This appears to be a deadlock of some sort or another in clvmd - it's
hanging on a futex call.
--
metadata operations hang after node outage
https://bugs.launchpad.net/bugs/295836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Oh - also, after this test, if I then stop cman on aperture-science,
bump the config_version field to match the other two servers, and start
cman again, it has no problems joining the cluster.
--
ccsd does not load cluster.conf from cluster
https://bugs.launchpad.net/bugs/293006
You received
** Attachment added: cluster.conf
http://launchpadlibrarian.net/19273681/cluster.conf
--
ccsd does not load cluster.conf from cluster
https://bugs.launchpad.net/bugs/293006
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
The Redhat Cluster documentation
(http://people.redhat.com/teigland/cluster2-arch.txt) suggests that,
when ccsd starts up, it should poll the cluster to find the most current
version of the cluster.conf config. So far, however, I've been unable to
trigger that behavior.
I am
Public bug reported:
The python-pyrex package currently in Jaunty hasn't been rebuilt for the
Python 2.6 transition, so it provides a python2.4-pyrexc and
python2.5-pyrexc.
A simple rebuild should fix the issue, modulo bug #342936
** Affects: pyrex (Ubuntu)
Importance: Undecided
Public bug reported:
Attempting to build the pyrex source package under Jaunty currently
results in it trying to install itself in /usr/local
This can be fixed by passing --install-layout=deb to setup.py.
** Affects: pyrex (Ubuntu)
Importance: Undecided
Status: New
--
pyrex
** Attachment added: pyrex_0.9.7.2-0.1ubuntu1.debdiff
http://launchpadlibrarian.net/23865748/pyrex_0.9.7.2-0.1ubuntu1.debdiff
--
pyrex FTBFS under Jaunty
https://bugs.launchpad.net/bugs/342936
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: pyrex_0.9.7.2-0.1ubuntu1.debdiff
http://launchpadlibrarian.net/23865752/pyrex_0.9.7.2-0.1ubuntu1.debdiff
--
Pyrex needs to be rebuilt for Python 2.6
https://bugs.launchpad.net/bugs/342937
You received this bug notification because you are a member of Ubuntu
Bugs, which
Right - the libltdl7 dependency is auto-generated at buildtime by dpkg-
shlibdeps, and the dependency is versioned based on what's available.
--
SRU: mit-scheme uninstallable on Intrepid
https://bugs.launchpad.net/bugs/341832
You received this bug notification because you are a member of Ubuntu
Here's an updated version of the SRU for Intrepid with a corrected
version number
** Attachment added: xen-3.3_3.3.0-1ubuntu7.1.debdiff
http://launchpadlibrarian.net/23083056/xen-3.3_3.3.0-1ubuntu7.1.debdiff
** Description changed:
Binary package hint: xen-utils-3.2
The xendomains
Whoops - that patch was backwards. Let's try this one instead.
** Attachment added: xen-3.3_3.3.0-1ubuntu7.1.debdiff
http://launchpadlibrarian.net/23083113/xen-3.3_3.3.0-1ubuntu7.1.debdiff
** Description changed:
Binary package hint: xen-utils-3.2
The xendomains init script has a
Martin, I've tested the version in hardy-proposed and can confirm that
it works for me (and didn't introduce any regressions on my system).
(Granted, I suspect that doesn't count for /too/ much since it is my
patch :-P, but there it is.)
--
errors in xendomains init script
What about this patch? I honestly can't come up with a good reason for
aclocal to ever /not/ be run if DEB_AUTO_UPDATE_ACLOCAL is set - like I
said on the Debian bug, this is clearly overriding the intent of the
package maintainer, and that seems wrong.
This patch will /always/ run aclocal if
Public bug reported:
Please sync zephyr 2.1.20070719.SNAPSHOT-3 (main) from Debian unstable
(main).
The improper sign extension in zwgc broke the zwgc utility in the
zephyr-clients (universe) package on amd64 systems.
Changelog since current jaunty version 2.1.20070719.SNAPSHOT-1.2:
zephyr
*** This bug is a duplicate of bug 250344 ***
https://bugs.launchpad.net/bugs/250344
** This bug has been marked a duplicate of bug 250344
Please backport trac 0.11-2 (from intrepid)
--
Please backport trac 0.11-2 to hardy
https://bugs.launchpad.net/bugs/260961
You received this bug
I've requested an SRU for Intrepid - it's being tracked in bug #341832.
The bug was ACKed by the SRU team, so hopefully it should show up in
intrepid-proposed within the next week or so (and intrepid-updates after
another week or two).
--
mit-scheme dependent package libltdl3 is not available
One of the OpenAFS developers (Chaskiel) gave us this patch to try.
We'll be testing it over the next few days on some of our machines to
see if it fixes the problem.
I should warn anyone interested in trying the patch that it has
absolutely not been tested yet, or even built.
We'll report back
Here's a patch that fixes the problem - Ubuntu can drop it once Asheesh
updates the Debian package, but it would be nice to get this fixed in
Jaunty.
Since it's a missing {build-,}dependency, I don't believe this needs a
feature freeze exception, so I'm subscribing ubuntu-universe-sponsors
I've
This hit the archive some time in the last few hours. Thanks for your
help, Iulian, Scott, and John.
** Changed in: mit-scheme (Ubuntu)
Status: Fix Committed = Fix Released
--
FeatureFreezeException: Merge mit-scheme with Debian
https://bugs.launchpad.net/bugs/339449
You received this
Public bug reported:
Binary package hint: mit-scheme
Bug #288000 (dependency on nonexistent libltdl3) and bug #217792
(AppArmor blocks mit-scheme from allocating memory near 0) apply to
Intrepid as well as Jaunty. Thanks to #288000, the package is not
installable on Intrepid, and even if it were
** Attachment added: mit-scheme_7.7.90+20090107-1ubuntu0.1.dsc
http://launchpadlibrarian.net/23783196/mit-scheme_7.7.90%2B20090107-1ubuntu0.1.dsc
--
SRU: mit-scheme uninstallable on Intrpepid
https://bugs.launchpad.net/bugs/341832
You received this bug notification because you are a member
** Attachment added: mit-scheme_7.7.90+20090107-1ubuntu0.1.diff.gz
http://launchpadlibrarian.net/23783226/mit-scheme_7.7.90%2B20090107-1ubuntu0.1.diff.gz
--
SRU: mit-scheme uninstallable on Intrpepid
https://bugs.launchpad.net/bugs/341832
You received this bug notification because you are a
** Attachment added: mit-scheme_7.7.90+20090107.orig.tar.gz
http://launchpadlibrarian.net/23783227/mit-scheme_7.7.90%2B20090107.orig.tar.gz
--
SRU: mit-scheme uninstallable on Intrpepid
https://bugs.launchpad.net/bugs/341832
You received this bug notification because you are a member of
Oh, ok, good.
That's the point of the xendomains script - when you shutdown, it saves
the guests' current state to disk (/var/lib/xen/save, I think), and when
you startup, it restores any domains that are saved into that directory.
Before it would just shut them down because of the typo that the
Yeah, when I originally created the patch it was for Xen 3.3, and I
forgot to change it for the Xen 3.2 version of the patch. It's a typo,
but the package is actually for Xen 3.2
Are you sure you don't have hardy-backports turned on? If you let apt
install the libxen3 from hardy-backports, that
I can confirm that the build in hardy-proposed fixes my bug with GSSAPI
authentication. I don't use alpine as my primary mail client, but I'll
try to test intermittently over the next few days.
--
SRU: Alpine on Hardy fails to build with GSSAPI support
https://bugs.launchpad.net/bugs/339815
You
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
libc6 integration gives way wrong error message to libc5 binaries.
https://bugs.launchpad.net/bugs/335666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
So this seems like something that would be ideal to get into an SRU, but
figuring out the minimal patch to fix the package seems non-trivial:
remus:~/src evan$ debdiff
xserver-xorg-video-ati_6.9.0+git20081003.f9826a56-0ubuntu2.1.dsc
xserver-xorg-video-ati_6.10.0-1ubuntu1.dsc | diffstat | tail
Here's a new version of the patch rebased on top of the recent security
update.
** Attachment added: openafs_1.4.7.dfsg1-6+ubuntu0.2.debdiff
http://launchpadlibrarian.net/25828644/openafs_1.4.7.dfsg1-6%2Bubuntu0.2.debdiff
--
[SRU] openafs-modules segfault after stop
Jeppe -
I think that the build currently in my PPA should fix this issue
(https://launchpad.net/~broder/+archive/ppa, see Adding a PPA to your Ubuntu
repositories on https://help.launchpad.net/Packaging/PPA for the documentation
on how to enable it). Could you test that and see if it works?
Actually, scratch that. That version apparently has no Python dependency
at all. Blargh
--
XEN depends on Python 2.5
https://bugs.launchpad.net/bugs/362691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: hardy-backports
Importance: Undecided
Status: New
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Uxorious wrote:
Looking at packages.ubuntu.org, it seems the last xen-image-* package
was in Gutsy!
You want linux-image-xen, not xen-image -
http://packages.ubuntu.com/search?keywords=linux-image-xen
--
xm crashed with Error in module()
https://bugs.launchpad.net/bugs/273283
You received
Ok - using dh_pycentral instead of dh_python seems to have fixed that.
The version currently in my PPA depends on python ( 2.7), python (=
2.6).
Debdiff attached.
** Attachment added: xen-3.3_3.3.0-1ubuntu9.1.debdiff
http://launchpadlibrarian.net/25665243/xen-3.3_3.3.0-1ubuntu9.1.debdiff
--
Ok - one last fix remains, and then we're done with this bug.
xen-3.3 3.3.0-1ubuntu7~hardy1 is currently in hardy-backports.
Backporting 3.3.0-1ubuntu7.1 from Intrepid to Hardy should be safe and
should fix the bug in backports.
** Summary changed:
- errors in xendomains init script
+
** Description changed:
was after openafs-client stop on server
ubuntu hardy
[ 99.016655] Starting AFS cache scan...found 45 non-empty cache files (2%).
[ 99.346761] NET: Registered protocol family 17
[ 101.010753] ip_tables: (C) 2000-2006 Netfilter Core Team
[
In the Hardy release, msmtp, anubis, libvmime, mailutils, and mpop
should be rebuilt once this change is uploaded, as they build-dep on
libgsasl7-dev
Also, msmtp in hardy-backports
--
[hardy] libgsasl7-dev missing dependencies on libntlm0-dev, libkrb5-dev
https://bugs.launchpad.net/bugs/348865
Here's a patch for a Hardy SRU.
** Attachment added: alpine_1.0+dfsg-3ubuntu0.2.debdiff
http://launchpadlibrarian.net/24819523/alpine_1.0%2Bdfsg-3ubuntu0.2.debdiff
--
alpine's ./configure wants Build-Depends and Depends: aspell
https://bugs.launchpad.net/bugs/340993
You received this bug
And a patch for an Intrepid SRU.
** Attachment added: alpine_2.00+dfsg-1ubuntu0.1.debdiff
http://launchpadlibrarian.net/24819529/alpine_2.00%2Bdfsg-1ubuntu0.1.debdiff
--
alpine's ./configure wants Build-Depends and Depends: aspell
https://bugs.launchpad.net/bugs/340993
You received this bug
(Marking as confirmed so the SRU team doesn't miss it)
** Summary changed:
- alpine's ./configure wants Build-Depends and Depends: aspell
+ [Hardy, Intrepid SRU] alpine wants Build-Depends and Depends: aspell
** Description changed:
Binary package hint: alpine
+
+ BUG: alpine currently is
Be careful choosing version numbers for this. The normal mechanism for
an Ubuntu security version number will result in kernel modules with a
lower version than the current modules. Something like
1.4.7.dfsg1-6+ubuntu0.1 should work for Intrepid:
priscus:~ evan$ dpkg --compare-versions
Here's a patch for Hardy that includes those two patches. There is a
build in my PPA (https://launchpad.net/~broder/+archive/ppa) with the
patch.
** Attachment added: Patch for Hardy
http://launchpadlibrarian.net/25465370/openafs_1.4.6.dfsg1-2%2Bubuntu0.1.debdiff
--
OpenAFS Security
Whoops - here's a patch for Hardy that includes the LP closer.
** Attachment removed: Patch for Hardy
http://launchpadlibrarian.net/25465370/openafs_1.4.6.dfsg1-2%2Bubuntu0.1.debdiff
** Attachment added: openafs_1.4.6.dfsg1-2+ubuntu0.1.debdiff
I've built this package in my PPA. I've also installed it and used the
new openafs-modules-source package to build the new version of the
kernel modules, which built successfully and installed successfully. I
was able to use AFS after installing the new kernel modules.
** Changed in: openafs
Here is a patch for Ubuntu Dapper. It also includes a patch for OPENAFS-
SA-2007-003 aka CVE-2007-6599 aka LP bug #180792.
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2007-6599
** Attachment added: openafs_1.4.1-2+ubuntu0.1.debdiff
I've uploaded a package with the patch I attached to my PPA, where it
built successfully. I installed it on a test Dapper machine, and was
able to build, install, and use the AFS kernel module.
** Changed in: openafs (Ubuntu Dapper)
Status: New = In Progress
--
OpenAFS Security
http://launchpadlibrarian.net/25468149/openafs_1.4.1-2%2Bubuntu0.1.debdiff
contains a patch for this vulnerability, as well as OPENAFS-SA-2009-001
and 2009-002 (bug #356861)
** Changed in: openafs (Ubuntu)
Status: Confirmed = In Progress
--
SA 2007-003: Denial of service in OpenAFS
Here are the portions of upstream changelog for 1.4.8 - 1.4.10 that are
relevant for Linux:
Linux:
- Support for Linux through kernel 2.6.29 and prereleases of 2.6.30.
- Corrected support for some Linux VM system functionality.
- Dynamic vcache pool allocation on Linux to address issues with
Here is the build log of 1.4.10 from my PPA. The only change from the
1.4.10 package in Debian was the addition of the PPA changelog entry.
** Attachment added:
buildlog_ubuntu-jaunty-amd64.openafs_1.4.10+dfsg1-1~broder1.txt
Here is a log of the install of 1.4.10 from my PPA, as well as some
quick testing.
I uninstalled the package and then installed it again, so I didn't get
the normal debconf prompts this time. There are two high priority
prompts - one for what your home cell is, and one for how large your AFS
** Summary changed:
- OpenAFS Security Advisories 2009-001 and 2009-002
+ [FinalFreezeException] OpenAFS Security Advisories 2009-001 and 2009-002
** Description changed:
+ We're requesting a final freeze exception for this package in Jaunty to
+ sync version 1.4.10+dfsg1-1 from Debian.
+
+
Here is the full list of deltas that were included in 1.4.10.
** Attachment added: openafs-1.4.10_alldeltas.txt
http://launchpadlibrarian.net/25495186/openafs-1.4.10_alldeltas.txt
--
[FinalFreezeException] OpenAFS Security Advisories 2009-001 and 2009-002
** Summary changed:
- [FinalFreezeException] OpenAFS Security Advisories 2009-001 and 2009-002
+ OpenAFS Security Advisories 2009-001 and 2009-002
** Description changed:
- We're requesting a final freeze exception for this package in Jaunty to
- sync version 1.4.10+dfsg1-1 from Debian.
+ To
Running Xen 3.3 from backports was never an issue. The issue was turning
on backports, but still wanting to run Xen 3.2.
--
libxen3 in hardy-backports breaks Xen 3.2
https://bugs.launchpad.net/bugs/297077
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hmm...didn't quite get the indentation on that last one. Should have looked
more like this (hopefully?):
--- openafs-1.4.1.orig/src/afs/afs_cell.c
+++ openafs-1.4.1/src/afs/afs_cell.c
@@ -708,8 +708,7 @@
tc-vlport = AFS_VLPORT;
RWLOCK_INIT(tc-lock, cell lock);
newc = 1;
-
Here's a new patch for Dapper that includes the OPENAFS-SA-2007-001
patch. I don't have easy access to a Dapper machine (I have to install a
VM when I need one), so I don't know when I'll be able to test this, but
the added patch is pretty simple:
--- openafs-1.4.1.orig/src/afs/afs_cell.c
+++
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here are new debdiffs for Dapper, Hardy, and Intrepid - I wanted to
add the openafs-client.NEWS changes for Dapper and Intrepid to make
sure that people were notified to rebuild their kernel modules.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9
Well, I don't think many people are running Xen hosts on Intrepid, since
there isn't a dom0-capable kernel. However, I hacked a test VM together
using the Hardy kernel.
Since I'm already running in a VM, I can only do fairly limited testing,
but I was able to install a VM using xen-tools, boot it
You have to be using a kernel that's dom0 capable to use Xen. Are you?
Intrepid and Jaunty don't ship a dom0 kernel, so you'll either have to
build your own or grab the -xen kernel from Hardy.
What does `uname -r` say?
** Changed in: xen-3.3 (Ubuntu)
Status: New = Invalid
--
xm crashed
Jeppe -
I think it should basically just work to duplicate your sources.list with
entries for hardy instead of intrepid/jaunty and do `aptitude install
linux-image-xen`, but I'm not entirely sure.
When Ubuntu stopped supporting Xen, the official patchset for a dom0
kernel was for 2.6.18, and
It's really unfortunate that this was discovered so late in the release
process. The attached debdiff might fix the issue, but I really have no
idea what the implications of switching to Python 2.6 will be.
I'm working on a build with that patch in my PPA
After some discussion with Steve Langasek on IRC, he suggested that
we're really too close to release to be considering non-trivial changes
like this where we don't fully understand the implications, so I'm going
to start working on this as an SRU.
Here's a new patch targetted at a post-release
As far as I know, anybody who's using Ubuntu as a Xen host is running
Hardy instead of the latest release. Note that running Ubuntu as a Xen
guest should work fine using the -generic or -server kernels, so long as
you're running a Xen 3.3 host.
I will note that since Lenny just released recently,
Here's a patch for an SRU that includes STABLE14-cbr-free-what-you-
alloc-20090325 and STABLE14-shutdown-vcache-avoid-null-deref-20090324 -
both seem to cause similar symptoms at shutdown, and it seems that both
fixes are needed sometimes.
The version number in the SRU (1.4.7.dfsg1-6+ubuntu0.1)
Whoops - here's a patch that includes the LP closer.
** Attachment added: openafs_1.4.7.dfsg1-6+ubuntu0.1.debdiff
http://launchpadlibrarian.net/24511582/openafs_1.4.7.dfsg1-6%2Bubuntu0.1.debdiff
** Summary changed:
- openafs-modules 1.4.8 segfault after stop
+ [SRU] openafs-modules segfault
(Marking as confirmed so it doesn't get ignored - I can't retarget it
correctly :-P)
** Changed in: openafs (Ubuntu)
Status: Fix Released = Confirmed
** Description changed:
Impact: This bug causes kernel oopses and hangs at shutdown.
Development: The two deltas being incorporated
Public bug reported:
Binary package hint: mit-scheme
The mit-scheme package has been uninstallable since Intrepid, due to
some bad auto-generated dependencies (LP bug #288000).
It also hasn't worked without some hacking around AppArmor since at
least Hardy (LP bug #217792).
Re-syncing the
Here is the upstream changelog, build log, install log, and log of some
quick functionality tests.
- Evan
** Attachment added: changelog
http://launchpadlibrarian.net/23600462/changelog
** Attachment added: build-log
http://launchpadlibrarian.net/23600463/build-log
** Attachment added:
Blargh. I tried to submit the source package by e-mail so it should show
up in a single comment, but Launchpad seems to be unwilling to let me do
that, so here we go one file at a time instead.
** Attachment added: mit-scheme_7.7.90+20090107-1ubuntu1.dsc
** Attachment added: mit-scheme_7.7.90+20090107-1ubuntu1.diff.gz
http://launchpadlibrarian.net/23600562/mit-scheme_7.7.90%2B20090107-1ubuntu1.diff.gz
--
FeatureFreezeException: Merge mit-scheme with Debian
https://bugs.launchpad.net/bugs/339449
You received this bug notification because you
** Attachment added: mit-scheme_7.7.90+20090107.orig.tar.gz
http://launchpadlibrarian.net/23600586/mit-scheme_7.7.90%2B20090107.orig.tar.gz
--
FeatureFreezeException: Merge mit-scheme with Debian
https://bugs.launchpad.net/bugs/339449
You received this bug notification because you are a
** Attachment added: mit-scheme_7.7.90+20090107-1ubuntu1_i386.deb
http://launchpadlibrarian.net/23600591/mit-scheme_7.7.90%2B20090107-1ubuntu1_i386.deb
--
FeatureFreezeException: Merge mit-scheme with Debian
https://bugs.launchpad.net/bugs/339449
You received this bug notification because
1 - 100 of 972 matches
Mail list logo
