version check for -updates checks against -backports

[Martin Pitt]

postgresql-common_27ubuntu2_source.changes Rejected

Rejected:
postgresql-common_27ubuntu2.dsc: Version older than that in the archive. 27ubuntu2 <= 39.1~breezy1
postgresql-common_27ubuntu2.dsc: Version older than that in the archive. 27ubuntu2 <= 39.1~breezy1

But 27ubuntu2 should be fine:

postgresql-common | 27ubuntu1 | breezy-updates | source, all
postgresql-common | 39.1~breezy1 | breezy-backports | source, all

[Celso Providelo (cprov)]

We shoud not check normal (RELEASED, UPDATES, SECURITY) uploads version against BACKPORTS.

[Martin Pitt (pitti)]

You should check the version, but exactly the other way around: {released, updates, security} should always be smaller than backports.

Reason:
 * stable should always be < unstable
 * stable-backports is always unstable~number, i. e. only minimally smaller than unstable
 * if by accident -updates/-security gets higher than -backports, then you can't backport from unstable any more

[Celso Providelo (cprov)]

Right, Martin,

I can see two different issues:

1. Keep the versions sane (growing) accross _normal_ pockets {released, updates, security}, i.e, new upload to _normal_ should be always higher than the last published version in __normal__ only, new upload to backports should be higher than the last version published in backports, which is the highest at all.

2. Keep normal pockets always smaller than the first backports release

I'm on it already, most of the code is done , need to redesign a bit of current code.

 I 'd be glad if you can provide a set of dummy packages to test the new feature and ensure the things are working ( please, make them small, maybe we can include in LP worktree)

[Celso Providelo (cprov)]

Martin,

Please, re-upload what is missing and check if the things are sane for you too.

[Martin Pitt (pitti)]

Thank you for fixing. I re-uploaded postgresql-common for breezy-updates, I'll tell you if it still doesn't work.

[Martin Pitt (pitti)]

Reopening, I still get the issue. I just received another 'Rejected' email from Soyuz.

[Celso Providelo (cprov)]

Pitti, sorry for the false announce, it is in Soyuz Mainline, will be released next rollout, 22th

[Martin Pitt (pitti)]

This seems to work now, closing.