Hello .*,

I noticed a little weirdness when uploading a package for multiple
suites, in my case for "bullseye-backports" and
"buster-backports-sloppy".

Reference is https://mentors.debian.net/package/radsecproxy/

I uploaded version 1.9.0-1~bpo10+1 first and then 1.9.0-1~bpo11+1
second.

The latter seems to have superseded the first, with the first still
being in the interface but somehow only "half". For example the URL to
the DSC does not work and the URL in the RFS template is only "https://mentors.debian.netNone".

Simple fix is of course to just delete and reupload 1.9.0-1~bpo10+1 but
I think I happen to stumble upon an edge-case bug in the mentors backend
here.

Grüße,
Sven.

--
Sigmentation fault. Core dumped.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Sven,

On 2021/08/26 02:41 PM, Sven Hartge wrote:

I noticed a little weirdness when uploading a package for multiple
suites, in my case for "bullseye-backports" and
"buster-backports-sloppy".

Reference is https://mentors.debian.net/package/radsecproxy/

I uploaded version 1.9.0-1~bpo10+1 first and then 1.9.0-1~bpo11+1
second.

The latter seems to have superseded the first, with the first still
being in the interface but somehow only "half". For example the URL to
the DSC does not work and the URL in the RFS template is only "https://mentors.debian.netNone".

Simple fix is of course to just delete and reupload 1.9.0-1~bpo10+1 but
I think I happen to stumble upon an edge-case bug in the mentors backend here.

That's definitively a bug cause by a corner case in mentors. Here is the explanation:

Mentors differs from Debian official archive in which it allow
multiple upload of the same version+distribution, allowing people to
overwrite they upload until they are satisfied with it.

While mentors keeps track of each upload, the source repository simply
cannot store multiple version of the same file. Therefore before
installing the uploaded files to the repository any previous version of
a file will be uninstalled from it.

In theory, this shouldn't prevent people from retrieving sources package
from the repository of the same package, for two different
distributions and versions. For instance, uploading tmux/2.0-1 for
unstable and tmux/1.9-1+deb11u1 (let's say for a security fix) for
stable. Both live in different distributions, without any files
overlapping and the repository is happy to serve both.

Your use case is specific in which there is a overlap of the orig.tar,
which both distributions use. Because of that, and even if the
distribution differs and the file has the same checksum, the repository detected a new upload of the orig.tar and removed the previous upload
that was using it.

That's why the dsc of the first upload disappeared and the link doesn't
show up.

I'm not sure we can come up with a sound technical solution for this
issue, given that the repository replacing uploads is an actual feature.
I'll dig up the topic a little more to see if we can come up with
something.

I'll keep you posted.

--
Baptiste Beauplat - lyknode

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQt4kiVMTxdp/CJ4U4XSUsQeV3XMwUCYSf2fAAKCRAXSUsQeV3X M163APwPqYsgQWYmZNlpJ5lMOwactstfrQx3prpODYo2eV67VgEA2WtyUbsCRO5i Z3dfD86XeZw0xMxomR9M15ne4Mp5Cgw=
=You/
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Sven,

On 2021/08/26 10:15 PM, Baptiste Beauplat wrote:

On 2021/08/26 02:41 PM, Sven Hartge wrote:

I noticed a little weirdness when uploading a package for multiple
suites, in my case for "bullseye-backports" and
"buster-backports-sloppy".

That should be fixed now. We changed the behavior of the repository so
files can be shared between uploads as long as they have the same
content (checksum).

You can upload two version sharing the same orig and it will work fine.

Note that, shared files have the same restriction as other files. If the content changes, all uploads using the previous version of that file
will be removed from the repository to keep consistency. The dsc link
for removed repository files should not appear in the package page.

Best,

--
Baptiste Beauplat - lyknode

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQt4kiVMTxdp/CJ4U4XSUsQeV3XMwUCYSucdwAKCRAXSUsQeV3X MwaQAQDU7tU5qoTPduNvzuk074ezCxAlP2bqW1gcAI7huzuv7gD/STeBgcuWVtuX QS8Yu28sC9sIROQlSmdPOb1yQe+HpwU=
=OIbe
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 29.08.21 16:40, Baptiste Beauplat wrote:

On 2021/08/26 10:15 PM, Baptiste Beauplat wrote:

On 2021/08/26 02:41 PM, Sven Hartge wrote:

I noticed a little weirdness when uploading a package for multiple
suites, in my case for "bullseye-backports" and
"buster-backports-sloppy".

That should be fixed now. We changed the behavior of the repository so
files can be shared between uploads as long as they have the same
content (checksum).

You can upload two version sharing the same orig and it will work fine.

Note that, shared files have the same restriction as other files. If the content changes, all uploads using the previous version of that file
will be removed from the repository to keep consistency. The dsc link
for removed repository files should not appear in the package page.

Very nice, thank you.

That will make it substantially more easy to upload backports or
security updates if they share the same upstream version without needing
to do them in a piecemeal fashion.

Grüße,
Sven.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)