*** This bug is a duplicate of bug 126766 ***
https://bugs.launchpad.net/bugs/126766
** This bug has been marked a duplicate of bug 126766
latest qt 4.3 backports produces visual corruption during scrolling and in
the systray
--
qt4 4.3.0-2 bug
https://bugs.launchpad.net/bugs/126951
You
fix uploaded, waiting on freeze to finish
** Also affects: qt4-x11 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qt4-x11 (Ubuntu)
Status: New = Fix Committed
--
latest qt 4.3 backports produces visual corruption during scrolling and in the
systray
It seems to me that backporting this now, without the SRU done is
exactly what the Backports are for bug fixes policy was meant prevent.
Backports is not a way to avoid doing SRUs. The SRU should be easy
enough. If you need help with it, I'll help. In the meantime, I'm
Won't Fixing this until
Iguess any git 1.5.* version would be fine. But this bug seems
abandoned. Should someone fill a new more generic bug? like just:
backport git-core 1.5
--
Please backport git-core 1:1.5.1.3-1
https://bugs.launchpad.net/bugs/111966
You received this bug notification because you are a member of
Public bug reported:
java-package in gutsy adds support for JDK 6u2 (and following updates).
consider backport the package, thanks.
Package builds cleanly in feisty pbuilder and installs okay.
** Affects: feisty-backports (upstream)
Importance: Undecided
Status: New
--
please
It doesn't work in prevu script, the following error appear:
dpkg-deb: parse error, in file
`debian/request-tracker3.6/DEBIAN/control' near line 6 package
`request-tracker3.6':
`Depends' field, reference to `rt3.6-clients': error in version:
version string is empty
The control file is using
Right. That's a consistent problem with Dapper backports.
Just to confirm, https://launchpad.net/ubuntu/+source/request-
tracker3.6/3.6.1-3 worked fine?
If so, it's better to backport from Feisty than to do a source backport
which is what's required if you have to change the package.
--
Does someone have a debdiff for the source change? Is there still an
interest in this?
--
kismet: UVF exception request for 2006-04-R1
https://bugs.launchpad.net/bugs/45551
You received this bug notification because you are a member of Ubuntu
Backporters, which is the bug contact for Dapper
** Summary changed:
- Please backport git-core 1.5
+ Please backport git-core 1.5.2.3-1 from Gutsy to Feisty
** Description changed:
Originally discussed in bug #111966 but in there I was adviced to create
a new more general bug (the original got sort of abandoned).
Reason for
Yes, the request-tracker3.6-3.6.1-3 pakage backported from feisty
works fine in our
production environment.
--
Marco Catunda
2007/7/19, Scott Kitterman [EMAIL PROTECTED]:
Right. That's a consistent problem with Dapper backports.
Just to confirm, https://launchpad.net/ubuntu/+source/request-
** Summary changed:
- Backport request-tracker3.6 from feisty
+ Please backport request-tracker3.6 3.6.1-3 from Feisty to Dapper
** Description changed:
- I would like to see request-tracker3.6 backported from feisty to dapper
+ I would like to see request-tracker3.6 backported from feisty to
11 matches
Mail list logo