• Bug#993805: UDD: duplicate entries for the same release

    From Mattia Rizzolo@21:1/5 to Sandro Tosi on Mon Sep 6 21:00:03 2021
    On Mon, Sep 06, 2021 at 02:19:04PM -0400, Sandro Tosi wrote:
    I noticed how some packages have duplicate entries in UDD.sources for the same
    release:

    In this case, this is not a bug.

    udd=> select source, version, release from sources where source = 'setuptools-scm' and release = 'sid';
    source | version | release
    ----------------+---------+---------
    setuptools-scm | 4.1.2-3 | sid
    setuptools-scm | 6.0.1-1 | sid


    and AFAICS there's no reason setuptools-scm/4.1.2-3 should be in sid (it was uploaded between oldstable and stable).

    setuptools-scm/4.1.2-3 is still there, because apparently
    python-setuptools-scm is still in unstable.

    Trying with `dak rm` says there is "nothing to do", so I don't know
    what's with that.

    auto-cruft/cruft-report is quite buggy when it comes to arch:all
    packages, so you should not suppose that autodecruft will work.

    Turns out, there are more than 600 pkgs in this state:

    I haven't checked them, but I'm sure all of them have one reason or the
    other.
    notably, you'll find quite a lot of them that are Extra-Source-Only, so
    you should instead use:

    udd=> select count (*) from (select source, release, count(*) from sources where release = 'sid' and extra_source_only is null group by 1, 2 having count(*) > 1) as x;
    count
    -------
    332
    (1 row)

    (I dislike how extra_source_only is nullable, because "not
    extra_source_only" matches nothing… so I need to check for the nullity
    of the field, but that's life)

    Is this something do address within UDD import process or the entries are coming
    from someplace else? if the latter, please forward this bug to the appropriate
    team/package.

    The sources table just copies whatever is in the archive.
    I'm not reassigning that just because IME random bugs assigned to
    ftp.d.o are not really handled in any way, so it's just wasted hope.
    Hopefully somebody else from debian-qa can tell why
    python-setuptools-scm is still in Packages.

    --
    regards,
    Mattia Rizzolo

    GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
    More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'`
    Debian QA page: https://qa.debian.org/developer.php?login=mattia `-

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

    iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmE2YzUACgkQCBa54Yx2 K63LOxAAo9DBUhg4e7Dpj+WyqdQv3BxKIR2+s6mLZdPferSbMUAQiMMaDmAf2EFW 4KNoO7N/OUPwfBPLpe8+13rOVfmsebUQsngkxy6M4QNLtfVUM7rjSfER2pK7uBK0 uNm67IisTfyH9lOmbTAO/MFvlcmV7Hiqj+DptzgE0iBtMvVbxTnqO6NuEVJsFscN krr/mwrbNPbY07nd880YQVwoBfNIGwvtPx352Lw0vbf/g0Odkv7E3729zYJIP9VS NdMZt7H9WRb4UH2oquvVp95nKKHNWYlClbrDwEERHB7jFHxaV9gpF7oRmrHiFooK S7VI1c1jmF/jFH49wlm0BXJsnlHvWv6JRcT4BTZPbBOKol4Cc26MglOMRvGyePvi BVCFiZqmdL3lwNb0pg14LD187iWNbsCrvKkgOn7UQ9lTzM9z3jhEdgrc1yeKLKnL bGSoKCe/8TCV3LEKt/HJNR+uuky79oZjIoTBbMObRTXd+I0DT793Sdphku2eE/w3 73jeR6dX1vVl0jxJ0sns56KnhIScOu98ZtAHgtnbedUfNKMBruz