Don Armstrong schreef op 2018-06-07 17:25:
On Thu, 07 Jun 2018, Albert van der Horst wrote:
Can somebody confirm that it should be possible?
It's possible.
I now tend to believe that it is possible under some circumstances
but not for this particular instance in github
You want something like (untested):
version=4
https://github.com/albertvanderhorst/ciforth/releases \
downloads/CVS_REL[\d-]+/@PACKAGE@@ANYVERSION@@ARCHIVE_EXT@ debian
uupdate
I tried it without the typo (s/downloads/download/) and spend some time
to
try ancillary formulations. None worked.
It boils down to "the 'download' directory is not accessible."
I discovered that sitting in lina-5.3.0 I can try out the watch without
uploading to mentors. I've done dozens of tryouts on one day, compared
to half a dozen over 6 months. Thank you who rewrote the documentation
of uscan!
P.S. Is there scientific proof that tools like uscan save more time
than
they cost?
They save me time.
More than it costs me? ;-(
Yep. Things would be simpler if all websites allowed you to view all
directories and their contents, but because
https://github.com/albertvanderhorst/ciforth/releases/downloads doesn't
work, it's hard for uscan to figure out what on that page could match
CVS_REL. uscan has gotten more powerful to handle some of the more
interesting ways that upstreams distribute source packages.
[I can't say that I do something particularly interesting. The source
archive contains the part of the git archive that relates to linux (as
opposed to
aaple, ms-dos, ms-windows).]
Not only doesn't the directory download disallow access, it may not even
exists,
except in github's imagination. Equally disallowed is
download/CVS_REL-5-3-0 .
"wget $X/lina-5.3.0.tar.gz " nicely downloads the file as follows:
albert@kiwi:/tmp$ wget
https://github.com/albertvanderhorst/ciforth/releases/download/CVS_REL-5-3-0/lina-5.3.0.tar.gz
--2018-06-11 14:06:47--
https://github.com/albertvanderhorst/ciforth/releases/download/CVS_REL-5-3-0/lina-5.3.0.tar.gz
Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
Connecting to github.com (github.com)|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location:
https://github-production-release-asset-2e65be.s3.amazonaws.com/78567718/088bc488-35be-11e8-87aa-e70b8066ff43?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180611%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180611T130647Z&X-Amz-Expires=300&X-Amz-Signature=2a33b7f449e869e94ec4219b0c1e2265403a950b93bfff3ace393e82594776e3&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dlina-5.3.0.tar.gz&response-content-type=application%2Foctet-stream
[following]
--2018-06-11 14:06:47--
https://github-production-release-asset-2e65be.s3.amazonaws.com/78567718/088bc488-35be-11e8-87aa-e70b8066ff43?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180611%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180611T130647Z&X-Amz-Expires=300&X-Amz-Signature=2a33b7f449e869e94ec4219b0c1e2265403a950b93bfff3ace393e82594776e3&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dlina-5.3.0.tar.gz&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com
(github-production-release-asset-2e65be.s3.amazonaws.com)...
52.216.102.131
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com
(github-production-release-asset-2e65be.s3.amazonaws.com)|52.216.102.131|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 1416480 (1.4M) [application/octet-stream]
Saving to: ‘lina-5.3.0.tar.gz’
I would be very impressed if uscan would be able to pierce
this armour.
I've reread the documentation of uscan a couple of times especially
the git-related and mangle related parts.
If uscan is somehow able to increment the version numbers from
.. CVS-REL-5-3-0/../lina-5.3.0 ..
to
.. CVS-REL-5-4-0/../lina-5.4.0 ..
in unison, I can't find it.
(that is the way I'd tackle this.)
This is possibly related in uscan's man page:
"
pagemangle=rules
Normalize the downloaded web page string. (Don't use this
unless
this is absolutely needed. Generally, g flag is required for
these
rules.)
This is handy if you wish to access Amazon AWS or Subversion
repositories in which <a href="..."> is not used.
"
I'd pursue this, but I feel it makes no sense if the pages are not
accessible at all. Or?
--
Suffering is the prerogative of the strong, the weak -- perish.
Albert van der Horst
