Launchpad itself

OOPS-1962H228 : Project page vanished for svn imported project libindi-bugfix

Asked by Paweł T. Jochym

I have got libindi-bugfix project and its branch mirroring the development on sourceforge.
It was working fine for a day or so but after some time the project page vanished and the links
on the upstream branch page leed to the OOPS-1962H228 page.

Just go to:

https://code.launchpad.net/~jochym/libindi-bugfix/upstream

scroll down and click on the link to project page.

Consequently, I cannot get the project loaded with groundcontrol
anymore - it was working fine just a few hours ago.
The branch is still there and working.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Curtis Hovey
Solved:
Last query:
Last reply:
Revision history for this message
Paweł T. Jochym (jochym) said : 		#1

I have realized that the project was probably deactivated for some reason.
But I have searched high and low for the relevant mail about deactivation
and found nothing. So please, someone contact me again about it, if this is
indeed the case.

Revision history for this message
Curtis Hovey (sinzui) said : 		#2

I deactivated https://launchpad.net/libindi-bugfix and sent you an email. A bug fix is not appropriate for a project because it cannot be shared. Communities share project code and bugs.

https://launchpad.net/libindi is already registered. Push your branch to:
    bzr push lp:~jochym/libindi/upstream

Revision history for this message
Paweł T. Jochym (jochym) said : 		#3

Did not get the message (which address did you used?).
I think you are right, BUT i still think that it will be good to have upstream
code properly mirrored in the lp. I have a proposition:

I am wondering if it would not be a better idea to move the code
to existing project libindi (there is no code there, just PPA
with packages). The project is owned by Jasem Mutlaq who seems to be
an (semi?) official maintainer of the debian/ubuntu packaging of libindi.
I just want to fix it to work with my (quite typical) hardware.
For this I need the read-only access to the code anyway - I'll branch off it
to work on bugs. I have registered the project just to have the current
upstream code to branch off.

Can you do this move? It would be much better that way and beneficial for all parties.
I do not care about ownership of the project - Jasem is probably a better person to do it anyway.

So in essence: Could you move the mirrored branch to project libindi keeping the mirroring?
I'll adjust all my branches and work to this change.

Revision history for this message
Best Curtis Hovey (sinzui) said : 		#4

I believe the semi-automated script send email fom sinzui at canonical dot com.

Yes the mirrored code (and all releated branches) does belong with that project. No one wants to hunt for it. I am sure you would have been pleased if the code was already setup before your bug fix.

I disabled your import branch and setup a new import and linked it to <https://launchpad.net/libindi/trunk>. You push you other branches to lp:~jochym/libindi/[branch-name]

Revision history for this message
Paweł T. Jochym (jochym) said : 		#5

Great!
This is just what I wished for.
I was searching for the code there before starting this whole mess with private import.
Sorry for making a little mess. I should probably go by different route.

Thanks for swift and helpful action!

Revision history for this message
Paweł T. Jochym (jochym) said : 		#6

Thanks Curtis Hovey, that solved my question.