-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Download area cannot be listed anymore #1493
Comments
Hi Marc, How does the Debian check work to see if there is an update? Or in other words, what does it need to detect it? |
Quack Michael, The tool checks a specific page (currently https://downloads.cisofy.com/lynis/), detect the links in the page and filter them to get the various versions available, get the associated asc files too. The tool which is called It would be possible to use the Github release page instead but the asc files are missing and the signature check would not be possible anymore. \_o< |
Thanks, I did not know how Debian do this check. FreeBSD has a similar tool (portswatch) and they simply try to find a new version, instead of reading the directory listing. I have reverted a few things, so that the directory index is available for the newer packages. I might make a small change soon to look things a bit prettier, but then the directory structure for the main path should remain. Is the type of listing that uscan scans something you manage as a package maintainer in the watch file? |
It can read from any page, not just directory listings I think. I wonder how FreeBSD do it. I can parametrize the URL and pattern matching but there is not listing type. It seems any kind of http or ftp URL is fine. I cannot trigger a check but I can run the tool locally and it works again now, thanks:
|
Perfect. That is very useful for testing if we alter the page. I was thinking, an option could be the replace the page and only list the link to the latest version (and the signature). Can you share the definition that does the check? The one that does the check at downloads.cisofy.com. Or if possible, the full configuration file. Then I can use that later to test and confirm that I don't break things ;-) FreeBSD does it by checking the "next" version to show up. So if 3.1.1 is the current one, they check for 3.1.2, 3.2.0, and 4.0.0. |
As things work now, closing this issue. Feel free to add details if needed. |
@mboelen uscan reads various package configuration files, not just its own configuration, so you need to clone the whole The check is interesting but in my experience I think that would mean to test de shitload of versions. Sometimes upstream decide to go with 3.1.1.1, or skip a version because of some error during the release steps or because of a last minute fix, or would change the version scheme entirely… I don't think uscan folks would like to implement such approach. Thanks for sharing anyway. Thanks again for the fix. |
Quack,
I understand you're doing that on purpose but that's causing problems to update the Debian package. It's not possible anymore to monitor newly available versions and I am not going to do that manually. I considered using the Github repo instead but the releases are not signed. Could you consider publishing the signature file alongside the tarball on Github?
Regards.
\_o<
The text was updated successfully, but these errors were encountered: