Launchpad itself

Branch always shows "Updating branch..." after upgrading to 2a

Asked by Jon Tai

I upgraded https://code.launchpad.net/~ov+server/openvista-server/mainline using the web interface and now I'm experiencing the same thing as Mario in https://answers.launchpad.net/launchpad-code/+question/112445. The branch is upgraded, but the "Updating branch..." message won't go away.

Like Mario, I've pushed a few updates after upgrading the branch, but the "Updating" message is still there. Would it be possible for a Launchpad admin to remove the "Updating" message? Or is there something I can do to resolve it myself?

Should I file a bug about this issue somewhere?

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Sergei Golubchik (sergii) said : 		#1

seem to be the same with https://code.launchpad.net/~maria-captains/maria/5.1-converting branch.
the "Updating" message is up for 6 days now

Revision history for this message
Jon Tai (jontai) said : 		#2

I think it's different -- the OpenVista Server branch initially showed the "An upgrade of this branch is in progress" message, but after a few hours that went away and was replaced with "Updating branch... Launchpad is processing new changes to this branch which will be available in a few minutes. Reload to see the changes." The Maria branch is stuck on the first message.

Revision history for this message
Sergei Golubchik (sergii) said : 		#3

ok, I'll ask a new question

Revision history for this message
Launchpad Janitor (janitor) said : 		#4

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Max Bowsher (maxb) said : 		#5

Hmm, will adding a comment un-expire this?

Revision history for this message
Tom Haddon (mthaddon) said : 		#6

Had expired unnecessarily

Revision history for this message
Tim Penhey (thumper) said : 		#7

All fixed now. The bug that caused this has been fixed and rolled out.

Can you help with this problem?

Provide an answer of your own, or ask Jon Tai for more information if necessary.

To post a message you must log in.