Re: Fwd: A new version of "OCamlbuild" has been detected: "4.02.3" newer than "0.10.0", packaged as "ocaml-ocamlbuild"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 19, 2021 at 12:24:25AM +0300, Otto Urpelainen wrote:
> Kevin Fenzi kirjoitti 18.8.2021 klo 18.52:
> >On Wed, Aug 18, 2021 at 09:20:46AM -0400, Ben Beasley wrote:
> >>It looks like the project changed version schemes at some point. The 4.02.3 release was in 2015, before 0.9.0; a long list of 4.x and 3.x releases preceded it.
> >>
> >>I don’t see where it got 0.10.0 as the currently-packaged version; the actual bug (https://bugzilla.redhat.com/show_bug.cgi?id=1992935) correctly has 0.14.0.
> >>
> >>On Wed, Aug 18, 2021, at 8:52 AM, Richard W.M. Jones wrote:
> >>>This seems to have failed in some way.  Firstly it says that we're
> >>>currently packaging 0.10.0, which is not true.  The latest version of
> >>>ocamlbuild (0.14.0) is packaged.  But more seriously it seems to have
> >>>found some imaginary version (4.02.3) and I can't even see where it
> >>>got that number from.
> >
> >Can you file a issue at: https://github.com/fedora-infra/anitya/issues
> >
> >Thats the application/project that does this.
> 
> If you look at the release-monitoring.org config for OCamlbuild [1],
> you see that is has "Version scheme: RPM", so yes, 4.02.3 is a
> latter release than 0.14.0 than that. A pre-release filter is used
> to flag those 3.x and 4.x releases, I do not know if pre-releases
> should produce notifications and Bugzillas or not.
> 
> One way to hide 3.x and 4.x would be to add those to "Version
> filter" instead, that would exclude them from the fetch completely.
> But since they have already been fetched, you would also need to
> "Flag" this project and ask an admin to remove the ones that have
> already been fetched.
> 
> I do not know if it is normal to send "new version" notifications
> when the version was out years ago. Perhaps this is related to the
> fact that in release-monitoring.org, 4.02.3 says "Retrieved on
> (UTC): Date information unavailable". That sounds like an Anitya bug
> to me, because upstream GitHub has a date for this release.
> 
> [1]: https://release-monitoring.org/project/12387/

Where are you seeing 4.02.3?  I can't see that in the upstream
repository.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux