2008-08-31 14:40:13 |
Fabien Tassin |
description |
It's currently impossible to re-upload a package with a different src tarball after it has been deleted.
Use case:
- I prepare a new version of package "foo", upstream version "1.2.3" so I have foo_1.2.3.orig.tar.gz
- I want to publish it to a PPA as preview for testers before I push it to the repository => I call it 1.2.3-0ubuntu1~fta1
- I realize I packed the wrong tarball, I delete the package from the PPA and wait for it to disapear from the pool.
- I pack a new tarball keeping the same name and re-upload => it's rejected
I understand I can bump version name, say 1.2.3+icantpackcorrectly but then, either users of this ppa will be ahead of the repository, or i have to stick with this new tarball name for everyone. Neither options are IMHO good. |
It's currently impossible to re-upload a package with a different src tarball after it has been deleted.
Use case:
- I prepare a new version of package "foo", upstream version "1.2.3" so I have foo_1.2.3.orig.tar.gz
- I want to publish it to a PPA as preview for testers before I push it to the repository => I call it 1.2.3-0ubuntu1~fta1
- I realize I packed the wrong tarball, I delete the package from the PPA and wait for it to disappear from the pool.
- I pack a new tarball keeping the same name and re-upload => it's rejected
I understand I can bump version name, say 1.2.3+icantpackcorrectly but then, either users of this ppa will be ahead of the repository, or i have to stick with this new tarball name for everyone. Neither options are IMHO good. |
|
2008-11-18 19:56:05 |
Celso Providelo |
soyuz: statusexplanation |
|
After avoiding this issue for quite a while, I think a decision was made regarding the consistency of the history stored for PPA.
Allowing upload of different contents under the same filename is utterly bad for history consistency, I assume there is not doubt about it and the more PPAs grow (including signed repositories) the more we have to choose the path for consistency instead forgiven to use mistakes.
There are proper ways around upstream problems (or even user mistakes, for instance patching the orig tarball, suffixing the version, etc) in a way users will continue to benefit of proper history and source & binary within PPAs.
Note that I'm not saying that getting around diverging tarballs or broken version are easy, neither that they are a desirable thing. That's why it's important to think about a safe versioning path when you are maintaining a source that is available to the world.
|
|