That did the trick. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to Hardy Backports.
https://bugs.launchpad.net/bugs/551655
Title:
open-whois.org is cybersquatted and its rules should be removed from
Spamassassin
Great, thanks for the update.
** Changed in: lucid-backports
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/686590
Title:
dkms fails to identify
Package b/i/r on Lucid. Test builds are in
https://launchpad.net/~broder/+archive/backports-tests
** Changed in: lucid-backports
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://b
This can be closed. My problem stemmed from a misleading error message
from DKMS when trying to build the nvidia wrapper myself. It complains
about kernel source not being installed (even when it is) when what it
really wants is the kernel headers package.
--
You received this bug notification
Err, sorry. I'm going to move the discussion to bug 631960, since bug
631740 looks to be a duplicate of that bug.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/684286
Title:
Please b
As a rule, backports should be used to add features, not fix bugs. We
have the SRU process for fixing bugs (see
https://wiki.ubuntu.com/StableReleaseUpdates).
I'm going to close this bug, and then we can continue the discussion of
starting the SRU process back on bug 631740.
** Changed in: lucid-
Can you provide a bit more information as to what's going wrong? What
version of nvidia-current are you using, where are you getting it from,
etc.?
lucid-backports doesn't currently have a version of nvidia-currently, so
it seems like this isn't really a backports-related issue. But if there
is cu
Package b/i/r on Lucid and Maverick.
(Test build in https://launchpad.net/~broder/+archive/backports-tests)
** Changed in: lucid-backports
Status: New => Confirmed
** Changed in: maverick-backports
Status: New => Confirmed
--
You received this bug notification because you are a m
** Also affects: maverick-backports
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/689068
Title:
Please backport bitlbee 3.0.1-1 from Natty
Package has no rdepends, and all build-deps are available in Lucid.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/689064
Title:
Please backport znc 0.096 from Maverick to Lucid
--
The specific versioned dependency for openssl is generated when the
package is built. Since we rebuild packages when we backport them, znc
would be built against the correct version of openssl.
However, we only backport packages that are already in the Ubuntu
archive. Since version 0.096 is not ye
** Summary changed:
- Please backport bitlbee 3.0.1 from Natty to Lucid, Maverick
+ Please backport bitlbee 3.0.1-1 from Natty to Lucid, Maverick
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.n
** Changed in: lucid-backports
Status: New => Confirmed
** Changed in: lucid-backports
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/535459
Titl
Package has no rdepends, and all build-deps are available in both Lucid
and Maverick.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/689068
Title:
Please backport bitlbee 3.0.1 from N
I'm going to reformat this bug slightly. Version 3.0.1 of bitlbee is
only in Natty, not Maverick. In order to maintain a clean upgrade path
from Lucid to Maverick, we will need to backport bitlbee from Natty to
both Lucid and Maverick.
** Description changed:
- The version of bitlbee supplied in
Upgrading the local openssl and libssl was trivial - just grabbed the
packages from natty.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/689064
Title:
Please backport ZNC 0.096 to Lu
Public bug reported:
The version of bitlbee supplied in natty/maverick installs on lucid
without modification or dependancy issues.
This references two packages: bitlbee_3.0.1 and bitlbee-common_3.0.1
** Affects: lucid-backports
Importance: Undecided
Status: New
--
You received t
Public bug reported:
0.096 would be nice, but if not possible natty/maverick has 0.092.
ZNC 0.092 from natty almost works, but it is built against a different
build of openSSL (0.9.8m, lucid has 0.9.8k). libares shipped with lucid
works.
http://en.znc.in/wiki/ZNC
** Affects: lucid-backports
This package works fine on my server (amd64). It will become the
official backports?
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/611520
Title:
[test-pkg-a] Please, backport nginx 0
19 matches
Mail list logo
