Hi, On Mon, 17 Feb 2025, Santiago Ruano Rincón wrote: > Other than to take into account recent activity, I think it is important > to look for possible reasons for not packaging the version reported by > uscan, before filing a bug report.
I actually see it the other way. When a new upstream release has not been packaged into Debian one month after its release, as a user, I'd like to know why. Having a bug report open would allow the maintainer to comment and leave some explanation, whatever it is. It could be that he has no time and would gladly accept help. It could be that this is not an LTS release and he will only package LTS releases. Or it could be that it's just a minor release and he intends to update the package just once a couple of months before the release. Or the new upstream release requires a new dependency that we don't have yet, and he's waiting on that, etc. So provided that we don't spam maintainers with "new upstream release" bug reports hours after the upstream release, and that we don't open new bug reports for as long as the former one has not been closed (but instead update the existing bug with the new information), then I would be pretty much in favor of automating the creation of such bug reports. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hert...@debian.org> ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS
signature.asc
Description: PGP signature
