Bug#920024: Doesn't parse package architectures correctly when any-amd64 is used (etc.)
On Mon, 21 Jan 2019, Steve McIntyre wrote: > I've just been looking at the details for sbsigntool > (https://tracker.debian.org/pkg/sbsigntool) It looks like the tracker > code is confused by the architecture list for sbsigntool: > > Architecture: any-amd64 any-i386 arm64 armhf > > and is just showing > > arch: arm64 armhf > > which is quite confusing! Yeah, the data model includes a list of architectures by source package and the parsing keeps only entries which are real architectures, the architecture wildcards are just not handled. Extract from distro_tracker/core/retrieve_data.py: # Convert the parsed data into corresponding model instances if 'architectures' in entry: # Map the list of architecture names to their objects # Discards any unknown architectures. entry['architectures'] = Architecture.objects.filter( name__in=entry['architectures']) I think we don't have any code in the tracker to handle architecture wildcard and try to do any mapping or expansion. Given the data model, that's we should aim to do here. Creating all the possible wildcards would be wrong, instead we want to process the list of architectures that the tracker knows of and see whether it matches the wildcards listed in the source package field. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Bug#920024: Doesn't parse package architectures correctly when any-amd64 is used (etc.)
Package: tracker.debian.org Severity: normal Hi folks, Thanks for the great service on tracker. It really makes my life easier when doing Debian work! I've just been looking at the details for sbsigntool (https://tracker.debian.org/pkg/sbsigntool) It looks like the tracker code is confused by the architecture list for sbsigntool: Architecture: any-amd64 any-i386 arm64 armhf and is just showing arch: arm64 armhf which is quite confusing! -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Processed: Re: Bug#917025: tracker.debian.org: 0 new commits since last upload
Processing control commands: > reassign -1 tracker.debian.org Bug #917025 [qa.debian.org] tracker.debian.org: 0 new commits since last upload Bug reassigned from package 'qa.debian.org' to 'tracker.debian.org'. Ignoring request to alter found versions of bug #917025 to the same values previously set Ignoring request to alter fixed versions of bug #917025 to the same values previously set -- 917025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#910987: Bug#917025: tracker.debian.org: 0 new commits since last upload
Control: reassign -1 tracker.debian.org Re: Mattia Rizzolo 2018-12-21 <20181221211515.gn19...@mapreri.org> > > Not sure if this is a duplicate of #910987, but I see the problem. > > Not quite. However, it's not a problem coming from tracker, rather by > the data source it uses. It's somewhat related because in both bugs, the wording used by the tracker is the problem. In #910987, the information is technically correct, but the wording is a little bit too aggressive in suggesting that A Upload Is Needed Now. > > -->8-- > > action needed > > 0 new commits since last upload, time to upload? normal > > vcswatch reports that this package seems to have a new changelog entry > > (version 1:5.25.2-2, distribution unstable) and new commits in its VCS. > > You should consider whether it's time to make an upload. > > > > Here are the relevant commit messages: > > > > None > > > > Created: 2018-12-21 Last update: 2018-12-21 15:05 > > -->8--- > > > > Latest commit is 727f110b (tagged then, after several minutes, > > everything was pushed to the public repo _before_ upload to > > the debian archive was done). The problem here is that the tracker is interpreting the information from vcswatch wrongly. The "commits since last tag" information should only be used when the status is "COMMITS". And even when done correctly, it should rather be saying "eventually this package should be uploaded", and not "time to upload?" which seems to suggest that this should happen "now". Christoph
Processed: Re: Bug#917025: tracker.debian.org: 0 new commits since last upload
Processing control commands: > reassign -1 tracker.debian.org Bug #910987 [tracker.debian.org] tracker.debian.org: Request to upload too eager when a new commit is seen Ignoring request to reassign bug #910987 to the same package -- 910987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
