Your message dated Mon, 6 Sep 2021 20:51:37 +0200 with message-id <YTZjOTP/p55voevX@mapreri.org> and subject line Re: Bug#993805: UDD: duplicate entries for the same release has caused the Debian Bug report #993805, regarding UDD: duplicate entries for the same release to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 993805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993805 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: UDD: duplicate entries for the same release
- From: Sandro Tosi <morph@debian.org>
- Date: Mon, 06 Sep 2021 14:19:04 -0400
- Message-id: <[🔎] 163095234468.1323578.17550783724769569314.reportbug@zion.matrix.int>
Package: qa.debian.org Severity: normal X-Debbugs-Cc: morph@debian.org Hello, I noticed how some packages have duplicate entries in UDD.sources for the same release: 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). Turns out, there are more than 600 pkgs in this state: udd=> select count (*) from (select source, release, count(*) from sources where release = 'sid' group by 1, 2 having count(*) > 1) as x; count ------- 602 (1 row) 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. Regards, Sandro
--- End Message ---
--- Begin Message ---
- To: Sandro Tosi <morph@debian.org>, 993805-close@bugs.debian.org
- Subject: Re: Bug#993805: UDD: duplicate entries for the same release
- From: Mattia Rizzolo <mattia@debian.org>
- Date: Mon, 6 Sep 2021 20:51:37 +0200
- Message-id: <YTZjOTP/p55voevX@mapreri.org>
- In-reply-to: <[🔎] 163095234468.1323578.17550783724769569314.reportbug@zion.matrix.int>
- References: <[🔎] 163095234468.1323578.17550783724769569314.reportbug@zion.matrix.int>
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 `-Attachment: signature.asc
Description: PGP signature
--- End Message ---