New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detected new upstream version but got the download URL wrong #123
Comments
It does uses the Source0 from the spec file indeed. From there, the-new-hotness asks pkgdb if the package is set for monitoring, and if so then with the only information available of the new version, pulls the spec file from the git and tries to do a rebuild. Does that clear things up? |
Yeah, @sanjayankur31, it bumps the The the hard-coded |
Yeah, that's because the version is 3.15.X, but the URL only uses 3.15 for the folder name. For example, now the new version is 3.16.0, but the URL only has 3.16 and then minor releases under there. So, I can't use %{version} in the url there :( |
Gah, but I forgot to update the URL in the spec to 3.16! /me goes to fix it. |
In this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1206962, it correctly detected that a new version was available, however it got the download URL wrong and failed to find the new source. I think it's just using the SOURCE from the spec instead of the actual file that it found here?
The text was updated successfully, but these errors were encountered: