uploading a newly packaged version not possible

Asked by estellnb

  I have updated bundsteg-1.2-2 to bundsteg-1.2-3 so that it should now build correctly on Ubuntu hosts. Also I have fixed some packaging issues. However when I wanted to upload the new package I got the following error:
  How can I delete an already uploaded package?

[~estellnb/ubuntu/elstel] bundsteg_1.2-3_source.changes (Rejected)
File bundsteg_1.2.orig.tar.gz already exists in packages for elstel, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
Files specified in DSC are broken or missing, skipping package unpack verification.

bundsteg (1.2-3) jammy; urgency=low

  * changed debain/rules to compile without OBS under Debian and Ubuntu
    does not reference ../SOURCES/ any more


If you don't understand why your files were rejected please send an email
to <email address hidden> for help (requires membership).

You are receiving this email because you made this upload.

Question information

English Edit question
Launchpad itself Edit question
No assignee Edit question
Last query:
Last reply:

This question was reopened

Revision history for this message
estellnb (estellnb) said :

found how to do it; thanks for your support!

Revision history for this message
estellnb (estellnb) said :
Revision history for this message
estellnb (estellnb) said :

I had successfully deleted the package and it was not more there in the web interface but now uploading has failed with the same error; please have a look!

Revision history for this message
estellnb (estellnb) said :

"Launchpad never permits reusing version numbers in the same archive, even if they have been deleted. "
It is not the same version; it is 1.2-3 instead of 1.2-2. Please see on how we can resolve that!

Revision history for this message
estellnb (estellnb) said :

I could exclude the src.tar.gz from being uploaded by modifying the changes file but now this won´t help me because the file has been deleted in the repository. Please help!!

Revision history for this message
Manfred Hampl (m-hampl) said :

"It is not the same version; it is 1.2-3 instead of 1.2-2"
The problem is the original source, which is bundsteg_1.2.orig.tar.gz in both cases.

The orig file from the previous upload (Wed, 24 Jul 2019) is still there in the moment: https://launchpad.net/~estellnb/+archive/ubuntu/elstel/+sourcefiles/bundsteg/1.2-2/bundsteg_1.2.orig.tar.gz

Revision history for this message
estellnb (estellnb) said :

Thanks, that has helped.

Revision history for this message
estellnb (estellnb) said :

I have now a similar problem with xchroot. I have changed the packaging to conform to standards as outlayed by Debian/lintian. This has required me to have two different .src.tgz files: xchroot_2.7.4.orig.tar.gz, xchroot_2.7.4.orig-website.tar.gz. The former xchroot_2.7.4.orig.tar.gz was an archive containing just the two archive files from above. However they are called the same because this is the name required by the Debian build system. Could you delete the xchroot package in a way that I can re-upload a file called xchroot_2.7.4.orig.tar.gz?

Revision history for this message
Colin Watson (cjwatson) said :

No, once you've uploaded a file to an archive then you can never replace it with a file with the same name but different contents. If you need to change the contents, you must bump the version number, even if that means that it's temporarily out of sync with the upstream version number. The convention in such cases is to use a version such as 2.7.4+repack1-1, which makes it clear that it's still really upstream 2.7.4 while changing the file names (xchroot_2.7.4+repack1.orig.tar.gz, etc.).

Can you help with this problem?

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

To post a message you must log in.