Launchpad itself

Package failed to build after moving it to another PPA

Asked by Thomas

Hello,
I have the following problem:
1/ I have set up a personal PPA
Se here: https://launchpad.net/~thomas.moulard/+archive/ppa
2/ I have uploaded a package
3/ The lpia package is built successfully.
See here: https://launchpad.net/~thomas.moulard/+archive/ppa/+build/982905
4/ I realize it is not what I want and create a team and a PPA in its team.
See here: https://launchpad.net/~roboptim/+archive/ppa
5/ I copy the /source/ package from my personal PPA to the team PPA and delete
 the package in m personal PPA.
6/ lpia fails to build now (but AMD64 is fine because it was not previously built).
See: https://launchpad.net/~roboptim/+archive/ppa/+build/982959

Is it possible to either:
A/ get rid of the current .deb and force the rebuild
B/ link the previously built .deb to my new PPA?

Thank you.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Julian Edwards Edit question
Solved by:
Thomas
Solved:
Last query:
Last reply:
Whiteboard:
20090504 bac: assigning to julian
Revision history for this message
Celso Providelo (cprov) said : 		#1

I see you have already workarounded the problem by uploading new versions to the right PPA.

Anyway, apparently on step 5, when you copied the source to the new PPA you also choose to copy the binaries (at that time only the lpia binaries).

In this circumstance the lpia-build in the new PPA should not be created, which would have avoided the failed-to-upload build. By some reason, possibly a race-condition during the copy procedure, the unwanted build was created.

There is only one possibility in this case, ignore the failed-to-build build because the binaries it was supposed to generate are already there.

Thanks for reporting the issue, let me know if that's the way things happened in fact.

Revision history for this message
Thomas (thomas.moulard) said : 		#2

I think I selected "Rebuild the copied sources" in the copy options.
Of course there is always some chance I selected the other one by mistake.
Is there some way to check that (some copy log somewhere)?

BTW, I've seen that the two lpia packages building process was on the same
builder. As I ordered the copy to be done soon after the first one finished
(maybe around 30min after the build), would it be possible that it triggers
a conflict because of some files remaining from the first build?

Revision history for this message
Celso Providelo (cprov) said : 		#3

Yes, there is a 'copy log' and that's where I've found all the information I gave you. The lpia binaries were published in the new PPA at the exact same time the source was (12:46 UTC).

The fact that the new build was processed by the same builders is unrelated to this problem (the xen image is restored from scratch before every job).

Revision history for this message
Thomas (thomas.moulard) said : 		#4

Ok, my bad.
Thanks for your help!