*** This bug is a duplicate of bug 127014 ***
https://bugs.launchpad.net/bugs/127014
** This bug has been marked a duplicate of bug 127014
Please backport git-core 1.5.2.3-1 from Gutsy to Feisty
--
Please backport git-core 1:1.5.1.3-1
https://bugs.launchpad.net/bugs/111966
You received th
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 Ubun
git-1.5.2.3 builds on Feisty.
--
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 Ubuntu
Backporters, which is the registrant for Feisty Backports.
--
ubuntu-backports mailing list
ubuntu-backports@lists.u
Version 1:1.5.2.2-1 does not build in Feisty:
*** t3400-rebase.sh ***
* FAIL 1: prepare repository with topic branch, then rebase against master
echo First > A &&
git-update-index --add A &&
git-commit -m "Add A." &&
git checkout -b my-topic-branch &&
the bug has been changed to unconfirmed because there is 1.5.2 version
to backport, the current gutsy is 1.5.2.2 and the bug has to be updated,
either confirming that this version should backported or not
--
Please backport git-core 1:1.5.1.3-1
https://bugs.launchpad.net/bugs/111966
You received
Can't change the subject to be like "Backport git-core".
However, the bug is not assigned anymore and the status is unconfirmed.
Do you really have to change the status if there's a slight mismatch in
topic (in a minor problem like this). Also the 1.5.2 is discussed in
comments and approved for ba
current gutsy version is 1.5.2.1, could you update the request?
** Changed in: feisty-backports (upstream)
Status: In Progress => Unconfirmed
--
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 Ubunt
Approved for backporting
** Changed in: feisty-backports (upstream)
Status: Confirmed => In Progress
--
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 Ubuntu
Backporters, which is the registrant fo
1.5.2 has hit Gutsy repos, backports compile fine on my computer
--
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 Ubuntu
Backporters, which is the registrant for Feisty Backports.
--
ubuntu-backports ma
1,5,2-1 build from Debian sources works fine on my two Feisty systems.
Had no issues what so ever building those packages
--
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 Ubuntu
Backporters, which is the
b/i/(dontknow how to test) under prevu
+1 feisty
** Changed in: feisty-backports (upstream)
Status: Unconfirmed => Confirmed
--
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 Ubuntu
Backporters, wh
11 matches
Mail list logo