Dear Maintainer,

I have noticed that on https://tracker.debian.org/pkg/linux the new upstream version takes ages to
update. for example now it displays "A new upstream version is available: 6.2~rc6" while on
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
and
https://kernel.org/
the latest upstream rc version is mainline:	6.2-rc7	2023-02-05

Thanks for your time in fixing this

Hello,

How long is "ages" for you?

The tracker is not responsible of detecting the new upstream releases.
It just uses information provided by UDD (Ultimate Debian Database).

But with >30000 source packages to monitor, we're not able to verify new
releases each hour. It's a process that is spread over a longer period...

I'm ccing the UDD maintainer so that he can decide whether there's
something to be made here.

Cheers,

I don't know if this is already done, but from historic release data it
might be possible to derive packages that are updated frequently and
therefore should be scanned more often.


Andreas

Like Andreas said it would be perfect if the package linux could be scanned
more often

Hi,

According to "select * from upstream where source='linux';", the last
check for Linux was on 2023-02-06 00:20:35. Unfortunately, that's not
much time before 6.2rc7 appeared.

Packages are refreshed every 72 hours. We are already hitting rate
limiting from some sources (e.g github) so I don't think that it would
be a good idea to reduce that interval.

Lucas

releases (as seen from the uscan scanner). What could be done is to
define a policy based on the number of new upstream releases uploaded to
Debian (looking at the upload_history table) over the last 1 or 2 years.

What would have to be done is:
1. add a SQL function to extract the upstream version from a debversion
postgresql type.
2. count the new upstream versions uploaded to Debian for each package.
Something like:
select source, count(distinct(extract_upstream(version))) as cnt from
upload_history where current_timestamp - interval '2 years' < date
group by source
3. Update rimporters/upstream.rb to change the policy from the static 72
hours to a variation based on the number of new upstream versions.

However that sounds low priority given that this is the first complaint
about the 72 hours delay being too long, while that importer was
introduced in 2017.

Lucas

<https://drive.google.com/file/d/11LOLY8oPyu3ehD9BHaKpZt6DvxIfs2HZ/view?usp=drivesdk>
call alert reshoot.mp4
<https://drive.google.com/file/d/11LOLY8oPyu3ehD9BHaKpZt6DvxIfs2HZ/view?usp=drivesdk>