You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can have a source package named MyApp-1.0 building MyApp_1.0.0.deb, and MyApp-1.1 building MyApp_1.1.0.deb. I want the user use the latest one by default, but keep the old version there just in case something in the new version is broken and I can't fix it in time in the new version, so it's always an option for rolling-back.
Now I want to backport something to 1.0.0, it will be 1.0.1 or 1.0.0-1, whatever, I want it supersedes 1.0.0.deb but does not touch 1.1.0.deb. On Ubuntu PPA, this is quite simple: I just release the 1.0.1 or 1.0.0-1 package with the same source package name MyApp-1.0 rather than MyApp-1.0.1.
So if I use the official reprepro, I can't have multiple versions, even if they come from different source packages.
If I use this fork, I have to manually remove the superseded versions.
I would suggest make use of negative Limit value.
1 means keeping only one version of a binary package
-1 can mean keeping only one version of a binary package from each source package.
The text was updated successfully, but these errors were encountered:
I'm not familiar with the code of either official reprepro or this fork. By looking at the commit history I suppose this is the only place Limit is checked. ca260b7
So I think the solution should be simple:
change } else if (target->distribution->limit > 0) { to } else if (target->distribution->limit != 0) { and then handle the negative case in the branch body, to sort and group by source package name (maybe the interface needs to change to provide source package info as well), and blah blah.
I'm not yet ready to fulfill the request by myself right now but I will do it when I have some spare time. Any comment or suggestion is welcomed.
Imagine how Ubuntu PPA works:
I can have a source package named
MyApp-1.0
buildingMyApp_1.0.0.deb
, andMyApp-1.1
buildingMyApp_1.1.0.deb
. I want the user use the latest one by default, but keep the old version there just in case something in the new version is broken and I can't fix it in time in the new version, so it's always an option for rolling-back.Now I want to backport something to
1.0.0
, it will be1.0.1
or1.0.0-1
, whatever, I want it supersedes1.0.0.deb
but does not touch1.1.0.deb
. On Ubuntu PPA, this is quite simple: I just release the1.0.1
or1.0.0-1
package with the same source package nameMyApp-1.0
rather thanMyApp-1.0.1
.So if I use the official reprepro, I can't have multiple versions, even if they come from different source packages.
If I use this fork, I have to manually remove the superseded versions.
I would suggest make use of negative
Limit
value.1
means keeping only one version of a binary package-1
can mean keeping only one version of a binary package from each source package.The text was updated successfully, but these errors were encountered: