The newer bzr-svn needs a newer bzr, so that's the route to fix this.
Simple rebuilding is not sufficient.
--
Please consider rebuiling the package for hardy-backports
https://bugs.launchpad.net/bugs/275573
You received this bug notification because you are a member of Ubuntu
Backports Testing Te
** Changed in: kdebase-runtime (Ubuntu Hardy)
Status: Confirmed => Fix Committed
--
System Settings tries to run "qt-language-selector" when not installed
https://bugs.launchpad.net/bugs/279531
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, wh
Public bug reported:
there is a bug in the Hardy amd64 version [1]
I've just installed the version for Intrepid [2], and it works like
charm
[1]: https://bugs.launchpad.net/ubuntu/+source/clearsilver/+bug/86685
[2]: http://packages.ubuntu.com/intrepid/amd64/python-clearsilver/download
** Affect
** Attachment added: "debdiff for sphinx 0.4.2-1 backport to hardy"
http://launchpadlibrarian.net/19148902/sphinx-4.2-1%7Ehardy1.debdiff
** Changed in: hardy-backports
Status: New => Confirmed
--
please backport sphinx 0.4.2-1 from Intrepid to Hardy
https://bugs.launchpad.net/bugs/291
Public bug reported:
please backport sphinx 0.4.2-1 from Intrepid to Hardy. It build /
install / run well under an hardy chroot. This backport is needed to
Django 1.0 backport (see #267305). A little change is needed (see
debdiff attached).
** Affects: hardy-backports
Importance: Undecided
Public bug reported:
please backport jquery 1.2.3-4 from Intrepid to Hardy.
This backport is necessary for django 1.0 backport (see #267305). It build /
install / run well in an hardy chroot.
** Affects: hardy-backports
Importance: Undecided
Status: Confirmed
** Changed in: hardy-
** Attachment removed: "Transmission Backport Patch"
http://launchpadlibrarian.net/19143943/transmission.debdiff
--
Please backport Transmission 1.34 to Hardy
https://bugs.launchpad.net/bugs/282361
You received this bug notification because you are a member of Ubuntu
Backports Testing Team,
There's a pending update to Intrepid already that fixes a crash. I'd
prefer to wait on this until after that it released to -updates and then
backport that:
* debian/control: Add build-depend on dpatch
* debian/patches: 10_fix_crasher_from_upstream.dpatch (LP: #274844)
- Fixes: transmission
Thanks for the response, but I just solved my problem by upgrading to
Intrepid...
On Fri, Oct 31, 2008 at 19:55, Michael Casadevall
<[EMAIL PROTECTED]> wrote:
>
> ** Attachment added: "transmission.debdiff"
> http://launchpadlibrarian.net/19143198/transmission.debdiff
>
> --
> Please backport Tr
** Attachment removed: "transmission.debdiff"
http://launchpadlibrarian.net/19143198/transmission.debdiff
** Attachment added: "Transmission Backport Patch"
http://launchpadlibrarian.net/19143943/transmission.debdiff
--
Please backport Transmission 1.34 to Hardy
https://bugs.launchpad.n
** Attachment added: "transmission.debdiff"
http://launchpadlibrarian.net/19143198/transmission.debdiff
--
Please backport Transmission 1.34 to Hardy
https://bugs.launchpad.net/bugs/282361
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is
Ok, this was a user error bug, I didn't have updates enabled in my Hardy
chroot :-).
Here's a patch to allow transmission to be backported.
** Changed in: hardy-backports
Importance: High => Wishlist
Status: Incomplete => Triaged
--
Please backport Transmission 1.34 to Hardy
https://
Transmission 1.34 requires a newer debhelper than what's available in
Hardy, so some porting will be required. However, I'm more concerned at
the moment that the previous backport of transmission seems to be
uninstallable (it depends on a version of libpango that is newer than
whats in Hardy!). Can
gstreamer0.10-plugins-ugly has a massive amount of reverse dependencies,
and it is possible we could hose Hardy users gstreamer installations
with a bad backport. I'm not willing to risk doing such a backport since
the potential risk outweighs the potential rewards. Marking Won't Fix.
** Changed i
** Changed in: hardy-backports
Status: New => Incomplete
--
Please Backport MySQL 5.0.67 from intrepid to hardy
https://bugs.launchpad.net/bugs/284688
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to Hardy Backports.
--
If you can provide information on the segfault specifically, and
specific steps to reproduce, we can release a fix into hardy-updates to
resolve this issue. Marking Incomplete for the time being.
** Changed in: hardy-backports
Status: New => Incomplete
--
Please backport slapd 2.4.11 from
Backporting a Java runtime would be a massive change, and has a high
chance of breaking many applications. I'm unwilling to approve or even
attempt this backport without solid justification on why it is needed.
Marking Won't Fix unless there is a strong reason to risk regressions.
** Changed in:
I've just upgraded from hardy to 8.10 via the dist-upgrade and received
this problem.
I unplugged all hard disks I didn't need and then tried to install 8.10
from CD, that worked just fine... except, the whole point of the
machine is the RAID file share, so I plugged the drives back in, and it
ha
well, if i wait long enough at the intramfs screen i can type return or
exit and that seems to kick me into gdm, and then everything works as i
need it to... except, i still don't have mdadm recognizing the drives.
fdisk -l shows all the drives, but mdadm won't assemble the array, even
manually.
I'm glad work is being done on this. It is really useful that 3.0.* be
backported to Hardy. The protocol changed in 3.0.0. If a rsync >=
3.0.0 tries to talk to a rsync <= 3.0.0 at the other end the
communication can fail. I've had failures like:
2008/10/31 14:00:58 [19814] --acls requires prot
20 matches
Mail list logo
