Re: Help to understand version tracking
On Sat, 12 Apr 2025, Santiago Vila wrote:n
> I'd like to know if there is any special way to report a bug so that
> version tracking works. See this for example:
Besides going back in time and avoiding renaming source packages with
names that cause conflicts with the earlier version of the source
package, fixing these edge cases is the only other option. You've filed
them correctly.
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=uglifyjs
>
> The top 3 bugs in the page are really the same, but they do not appear here:
>
> https://udd.debian.org/bugs/?release=sid&ftbfs=only&merged=ign&fnewerval=7&flastmodval=7&rc=1&sortby=source&sorto=asc&format=json#results
>
> Is this expected because it's a key package? (I hope not!)
Nah, this looks like a bug in version.cgi not looking up the source
package, and instead looking at the binary package instead.
Here's the wrong unredacted version graph:
https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;format=png;found=uglifyjs%2F2.8.29-8;height=;ignore_boring=0;info=1;package=src%3Auglifyjs;width=;collapse=1
The correct one would look like this:
https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;collapse=1;format=png;found=uglifyjs%2F2.8.29-8;height=;info=1;package=node-uglify;width=;ignore_boring=0
I don't know why UDD isn't showing it, but it's also not in the bugscan
RC list which is a bug. I'll try to look at it later tonight.
--
Don Armstrong https://www.donarmstrong.com
[On a trip back from collecting grass seeds in tropical bird stomachs
and being thought by the customs agents to be transporting Marijuana.]
"Anyone so square as to tell you they are transporting grass seeds is
bound to be OK"
-- Peter K. Klopfer _Seeds of Doubt_ Science 134:177 10 April 2009
Reply to: