"Could not be uploaded correctly" error after fixing deps

Asked by stsp on 2019-02-25

I built the package on launchpad, but the build
was bad because of the missing deps.
I rebuilt the deps (also in LP), and tried to
rebuild the original package again, but LP says
"Could not be uploaded correctly".
I deleted the previous build in PPA, but that
didn't fix the problem.

There are other instances of this problem:
https://askubuntu.com/questions/510438/how-to-replace-files-in-ppa-after-unsuccessful-build
so it really affects many people.
It would be good if the package deletion allows
to re-upload a new one.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
stsp
Solved:
2019-02-25
Last query:
2019-02-25
Last reply:
2019-02-25
stsp (stsp-0) said : #1

I built the package on launchpad, but the build
was bad because of the missing deps.
I rebuilt the deps (also in LP), and tried to
rebuild the original package again, but LP says
"Could not be uploaded correctly".
I deleted the previous build in PPA, but that
didn't fix the problem.

There are other instances of this problem:
https://askubuntu.com/questions/510438/how-to-replace-files-in-ppa-after-unsuccessful-build
so it really affects many people.
It would be good if the package deletion allows
to re-upload a new one.

William Grant (wgrant) said : #2

It is not, and will never be, possible to upload a different package with the same version string. You'd end up with two binaries with the same version but different contents, which confuses apt and users.

You need to cause the version to differ, e.g. by committing to a branch whose revision is included in the version, or by including the build timestamp in the version.

stsp (stsp-0) said : #3

> You'd end up with two binaries with the same version but different contents, which confuses apt

Even when I explicitly delete the previous one?

William Grant (wgrant) said : #4

What if that version was already installed on clients?

stsp (stsp-0) said : #5

> What if that version was already installed on clients?

Well, there are many possible fixes, one being
that LP could just add a numerical suffix that will
mean the build number. And its very simple to
implement.
I just suppose that "this will never change" attitude
is not going to help because people will keep reporting
this. As it really affects their work-flow.
So why not to consider some fix instead,
does the incremental suffix work as the one?

William Grant (wgrant) said : #6

It's not possible to add a simple incrementing numerical suffix, but you can achieve a similar effect by adding the {time} variable to your version template. See https://help.launchpad.net/Packaging/SourceBuilds/Recipes for other options.

stsp (stsp-0) said : #7

Yes, thanks, I'll give {time} a try.