Launchpad itself

bazaar branch not getting created

Asked by Blake GH

We've been using Launchpad for 10+ years. There seems to be an issue right now with the Bazaar branch creation phase of the process. Would someone be able to look into this for us?

We have configured a series branch and pointed at the new branch. We've clicked on "Import Now" - which is showing it's process but it has yet to have created the bazaar branch.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Blake GH
Solved:
Last query:
Last reply:
Revision history for this message
Blake GH (bmagic) said : 		#1

Our LP branch is stuck with this message:

Updating branch...

Launchpad is processing new changes to this branch which will be available in a few minutes. Reload to see the changes.

It's been 5 days

Revision history for this message
Galen Charlton (gmc) said : 		#2

In particular, the branch Blake is referring to is https://code.launchpad.net/~evergreen-bugs/evergreen/rel_3_13

However, other branches in our project exist in but are not getting updated with recent commits:

https://code.launchpad.net/~evergreen-bugs/evergreen/rel_3_12
https://code.launchpad.net/~evergreen-bugs/evergreen/rel_3_11

Revision history for this message
Guruprasad (lgp171188) said : 		#3

Hi Blake and Galen, this is a known issue with the 'code import to bzr' feature where the actual code import succeeds but the bzr branch scanning errors out for various reasons. Other users have already reported this issue a few times. We are investigating and will post an update once we identify and fix the issue.

Revision history for this message
Blake GH (bmagic) said : 		#4

Looks like bug 708918 is the same

Guruprasad - Let us know what you find! We're in a release cycle at the moment. We're going to have to release without these translations. Hopefully it can be addressed soon.

Revision history for this message
Guruprasad (lgp171188) said : 		#5

I have made some progress today in investigating and fixing this issue. I hope to share the good news soon.

Revision history for this message
Guruprasad (lgp171188) said : 		#6

Hi Blake,

> Looks like bug 708918 is the same

This bug doesn't have anything related to this issue, from what I can see. Did you intend to mention a different bug?

Revision history for this message
Blake GH (bmagic) said : 		#7

Guruprasad - LP didn't link my bug number correctly. Here's the full link: https://answers.launchpad.net/launchpad/+question/708918

Revision history for this message
Guruprasad (lgp171188) said : 		#8

Hi Blake,

> Guruprasad - LP didn't link my bug number correctly. Here's the full link: https://answers.launchpad.net/launchpad/+question/708918

Thanks for sharing the correct link. This one is a question and not a bug - those are separate entities in Launchpad with different meanings. I will unlink the wrongly linked bug now.

Revision history for this message
Guruprasad (lgp171188) said : 		#9

I checked https://code.launchpad.net/~evergreen-bugs/evergreen/rel_3_13 and see that the code import is working now after my attempted fixes yesterday and there is a bazaar branch with the latest changes in that branch. So does this allow you to release a new version with the translations?

I also see that the https://code.launchpad.net/~evergreen-bugs/evergreen/rel_3_12 branch and the https://code.launchpad.net/~evergreen-bugs/evergreen/rel_3_11 branch are still stuck and not showing the latest changes. I will continue my investigation and try to get those fixed soon.

Revision history for this message
Galen Charlton (gmc) said : 		#10

Thank you for getting rel_3_13 fixed; that should be enough to get our release done.

Blake: I've gone ahead and set up the translation export branch (https://code.launchpad.net/~evergreen-bugs/evergreen/translation-export-3.13), though you'll either need to wait for the daily automatic sync from Launchpad translations or do a manual export from https://translations.launchpad.net/evergreen/3.13/+translations.

Revision history for this message
Blake GH (bmagic) said : 		#11

Thank Galen! Thanks Guruprasad! Just in the nick of time.

Revision history for this message
Guruprasad (lgp171188) said (last edit ): 		#12

Hi Blake and Galen, I noticed that there are new commits in the rel_3_11 branch upstream and those have now been pulled into https://code.launchpad.net/~evergreen-bugs/evergreen/rel_3_11. This mirrored branch now has no errors.

So a workaround for this issue appears to be that whenever the upstream branch of the mirrored branch gets updated from now onwards, that should fix the stuck branch.

Edit: I see that the other mentioned branches have gotten updated for the same reason. Are there any other branches under https://code.launchpad.net/~evergreen-bugs/ that are still stuck?

Revision history for this message
Blake GH (bmagic) said : 		#13

Guruprasad,

It seems that you've taken care of the outstanding issues that we were seeing. Hopefully it continues to flow through bazaar. 3.11 is the oldest branch that we still support. And we're almost finished with our current release cycle. We will cross this bridge again during our next release cycle. If the LP bazaar repo doesn't work, we'll open a new ticket here!

Thank you for all of your help! Five stars!

Revision history for this message
Blake GH (bmagic) said : 		#14

Guruprasad,

It seems that you've taken care of the outstanding issues that we were seeing. Hopefully it continues to flow through bazaar. 3.11 is the oldest branch that we still support. And we're almost finished with our current release cycle. We will cross this bridge again during our next release cycle. If the LP bazaar repo doesn't work, we'll open a new ticket here!

Thank you for all of your help! Five stars!