** Also affects: libdmtx (Ubuntu)
Importance: Undecided
Status: New
--
Update libdmtx to 0.6.0
https://bugs.launchpad.net/bugs/306280
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to Hardy Backports.
--
ubuntu-backpor
mercurial | 1.0-7 | http://archive.ubuntu.com intrepid/universe
Sources
And 1.0.1-1 has just been synced:
https://edge.launchpad.net/ubuntu/+source/mercurial/1.0.1-1
--
[needs-packaging] mercurial 1.0
https://bugs.launchpad.net/bugs/223789
You received this bug notification because you are
Valentin Rocher wrote:
> When I try to backport it, I have this error :
>
> pbuilder-satisfydepends-dummy: Depends: libexempi-dev (>= 1.99.2) which
> is a virtual package.
>
> Isn't it a bit hazardous to mark this bug as confirmed thus ?
You need to backport exempi first (or alternatively remove
sefs wrote:
> I just realised these are hardy repos here
> https://launchpad.net/~pochu/+archive
>
> anything for gusty 7.10?
>
There's Gutsy packages there...
--
backport tracker 0.6.6
https://bugs.launchpad.net/bugs/175676
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Hi,
Please, backport emesene from Hardy. There's many users using the
upstream apt repo, so there's a user base out there which will benefit
from this package, and it would be better for them if they were using
the official backports.
I haven't been able to test it outside H
That's something up to the backports team.
** Changed in: wesnoth (Ubuntu)
Status: New => Invalid
--
wesnoth in gutsy-backports does not have required dependency
https://bugs.launchpad.net/bugs/209463
You received this bug notification because you are a member of Ubuntu
Backports Testing
I got good feedback from one user and it has worked fine for me.
--
backport tracker 0.6.6
https://bugs.launchpad.net/bugs/175676
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to Gutsy Backports.
--
ubuntu-backports mailing lis
Thanks Jérôme for the testing!
I've opened the Edgy request here, let's track all of them in the same
bug.
** Also affects: edgy-backports
Importance: Undecided
Status: New
** Changed in: feisty-backports
Status: New => Confirmed
** Changed in: gutsy-backports
Status: Ne
*** This bug is a duplicate of bug 173924 ***
https://bugs.launchpad.net/bugs/173924
** This bug has been marked a duplicate of bug 173924
Please backport wesnoth 1.2.8-1 from Hardy. Fixes 3 CVEs
--
Please backport wesnoth 1.2.8-1 from Hardy. Fixes 3 CVEs
https://bugs.launchpad.net/bugs/1
No need to wait, as it won't be synced, since 1.3.x is unstable.
I'd appreciate (well, not me, but backports users) a backport of 1.2.8.
Thanks
--
Please backport wesnoth 1.2.8-1 from Hardy. Fixes 3 CVEs
https://bugs.launchpad.net/bugs/173924
You received this bug notification because you are a
Public bug reported:
Please backport wesnoth 1.2.8-1 from Hardy.
edgy-backports has version 1.2.3, which is vulnerable to 3 CVEs.
https://bugs.edge.launchpad.net/bugs/cve/2007-3917
https://bugs.edge.launchpad.net/bugs/cve/2007-5742
https://bugs.edge.launchpad.net/bugs/cve/2007-6201
Thanks.
**
Public bug reported:
Please backport wesnoth 1.2.8-1 from Hardy.
feisty-backports has version 1.2.5, which is vulnerable to 3 CVEs.
https://bugs.edge.launchpad.net/bugs/cve/2007-3917
https://bugs.edge.launchpad.net/bugs/cve/2007-5742
https://bugs.edge.launchpad.net/bugs/cve/2007-6201
Thanks.
*
Just a couple of hints:
The target should be dapper-backports, instead of dapper.
In debian/changelog, the width shouldn't be bigger than 80 chars, but the line
with your name is.
The version number should be blah~dapper1 instead of -dapper1 (since
blah-dapper1 > blah > blah~dapper1). Using ~dap
It's quite easy. Check https://wiki.ubuntu.com/MOTU/Recipes/Debdiff
If you have any doubt, just ask. And if you can't do it, I'll have a
look.
Best,
Emilio
--
Please backport newer sqlite3_3.4.2 (ok with prevu)
https://bugs.launchpad.net/bugs/148493
You received this bug notification because yo
It looks like the builder needs an apt-get update ;) It's trying to get
an old version of libnspr4 (2.0.0.4) from feisty-security, and since
there's a newer version (2.0.0.6) it gets a 404 error and the build
fails.
Could you please update it (if needed) and retry the build?
Thanks,
Emilio
--
P
Public bug reported:
This has been requested in Bug #85029, and backporting tracker will fix
it in feisty.
So please, consider it.
** Affects: feisty-backports
Importance: Undecided
Status: New
--
Please backport tracker 0.6.1-0ubuntu1 from Gutsy to Feisty
https://bugs.launchpad.
*** This bug is a duplicate of bug 97096 ***
https://bugs.launchpad.net/bugs/97096
** This bug has been marked a duplicate of bug 97096
Please backport tomcat5.5 from gutsy (was: tomcat5.5 won't start b/c of
catalina.out named pipe)
--
tomcat 5.5 does not start due to catalina.out fifo
h
17 matches
Mail list logo
