Launchpad itself

Outdated imported branches can be deleted?

Asked by snd

Those imported branches are all outdated and can be deleted?
(The branches have been moved to new locations)

https://code.launchpad.net/~vcs-imports/autoconf/main (new one is @ lp:autoconf)
https://code.launchpad.net/~vcs-imports/autogen/main (new one is @ lp:autogen)
https://code.launchpad.net/~vcs-imports/automake/main (new one is @ lp:automake)
https://code.launchpad.net/~vcs-imports/bison/head (new one is @ lp:bison)
https://code.launchpad.net/~vcs-imports/gawk/head (new one is @ lp:gawk)
https://code.launchpad.net/~vcs-imports/gimp/head (new one is @ lp:gimp)
https://code.launchpad.net/~vcs-imports/glibc/head (new one is @ lp:glibc)
https://code.launchpad.net/~vcs-imports/glibc/trunk (new one is @ lp:glibc)
https://code.launchpad.net/~vcs-imports/gnuhello/trunk (new one is @ lp:gnuhello)
https://code.launchpad.net/~vcs-imports/gnumeric/svn (new one is @ lp:gnumeric)
https://code.launchpad.net/~vcs-imports/gnupg/main (new one is @ lp:gnupg)
https://code.launchpad.net/~vcs-imports/gnutls/main (new one is @ lp:gnutls)
https://code.launchpad.net/~vcs-imports/grub/grub2-cvs (new one is @ lp:grub)
https://code.launchpad.net/~vcs-imports/guile/main (new one is @ lp:guile)
https://code.launchpad.net/~vcs-imports/libidn/main (new one is @ lp:libidn)
https://code.launchpad.net/~vcs-imports/libtasn1/main (new one is @ lp:libtasn1)
https://code.launchpad.net/~vcs-imports/lilypond/trunk (new one is @ lp:lilypond)

And these are outdated imported branches which have a new branch which can not be imported:

https://code.launchpad.net/~vcs-imports/grep/main (new one is @ https://code.launchpad.net/~rbose-vcs-imports/grep/master)
https://code.launchpad.net/~vcs-imports/parted/trunk (new one is @ https://code.launchpad.net/~rbose-vcs-imports/parted/master)

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Gavin Panella Edit question
Solved by:
Gavin Panella
Solved:
Last query:
Last reply:
Revision history for this message
Benji York (benji) said : 		#1

I believe the LOSAs are the ones that do this. Assigning to them in the hope that I'm right.

Revision history for this message
William Grant (wgrant) said : 		#2

No, any ~vcs-imports member can do it. And ~launchpad is a member.

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

However, just because they're no longer being updated, doesn't mean that they are necessarily unwanted.

Why should we delete them?

Revision history for this message
snd (dns) said : 		#4

sorry, i did not say that those branches have moved to a new location and the new ones are in the ().
so.. for me it doesn't make sense to keep the old ones.

Revision history for this message
Gavin Panella (allenap) said : 		#5

https://code.launchpad.net/~vcs-imports/gnuhello/trunk cannot be
deleted as it has 1 branch sharing revisions. If you can figure that
out I'll delete it.

Apart from that, all from the first list are now gone.

> And these are outdated imported branches which have a new branch
> which can not be imported:
>
> https://code.launchpad.net/~vcs-imports/grep/main (...)
> https://code.launchpad.net/~vcs-imports/parted/trunk (...)

What shall I do with these? In my experience stale imports are
harmful, especially when they're the development focus; it's too easy
to bzr branch lp:foo and not realise that it's ancient. My preference
would be to delete them.

Gavin.

Revision history for this message
snd (dns) said : 		#6

> https://code.launchpad.net/~vcs-imports/gnuhello/trunk cannot be
> deleted as it has 1 branch sharing revisions. If you can figure that
> out I'll delete it.

Oops sorry, yes i see (my fault) and fixed it. Now you should be able to delete it, please try again.

> Apart from that, all from the first list are now gone.

Thanks, that helps to keep this list clean: https://code.launchpad.net/gnu

>> https://code.launchpad.net/~vcs-imports/grep/main (...)
>> https://code.launchpad.net/~vcs-imports/parted/trunk (...)
>
> What shall I do with these? In my experience stale imports are
> harmful, especially when they're the development focus; it's too easy
> to bzr branch lp:foo and not realise that it's ancient. My preference
> would be to delete them.

I think so too, but i guess this is not a question for me.
Also the lp:cpio branch is outdated, the new one is at https://code.launchpad.net/~rbose-vcs-imports/cpio/master (the new branch can also not be imported, because of missing submodules (See bug #402814)).

Revision history for this message
Best Gavin Panella (allenap) said : 		#7

I've deleted https://code.launchpad.net/~vcs-imports/gnuhello/trunk.

> > What shall I do with these? In my experience stale imports are
> > harmful, especially when they're the development focus; it's too
> > easy to bzr branch lp:foo and not realise that it's ancient. My
> > preference would be to delete them.
>
> I think so too, but i guess this is not a question for me. Also the
> lp:cpio branch is outdated, the new one is at
> https://code.launchpad.net/~rbose-vcs-imports/cpio/master (the new
> branch can also not be imported, because of missing submodules (See
> bug #402814)).

I'm going to leave these for now. Ideally I'd have the time to chase
them up, but I just don't :-/ If you're able to follow-up we will of
course be happy to help when elevated privs are needed.

Btw, you're a star for your efforts to garden all the GNU projects.
I'm genuinely sorry I can't spend more time helping you out.

Revision history for this message
snd (dns) said : 		#8

Ok ok, thanks Gavin :-)

Revision history for this message
snd (dns) said : 		#9

Thanks Gavin Panella, that solved my question.