On 02/03/2025 13:49, Lorenzo wrote:
How can I tell uscan to look for a different filename for the signature?
cat ./debian/watch (not working)
version=4
opts=pgpsigurlmangle=s/runit-([.0-9]+)\.tar\.gz/sha256sum\.asc/ \
https://smarden.org/runit/install.html runit-([.0-9]+)\.tar\.gz
This seems
On 26/02/2025 13:33, Andreas Tille wrote:
version=4
https://gitlab.com/l_sim/v_sim/tags?sort=updated_desc
.*/v_sim-(\d[\d.]+)\.tar\.gz
In case it helps, for gitlab it works with plain mode and the version is
repeated in the path and file name.
This is similar to what worked for me with open
On Wednesday, February 26, 2025 11:03:34 AM MST Ahmad Khalifa wrote:
> On 26/02/2025 13:33, Andreas Tille wrote:
> > version=4
> > https://gitlab.com/l_sim/v_sim/tags?sort=updated_desc
> > .*/v_sim-(\d[\d.]+)\.tar\.gz
> In case it helps, for gitlab it works with plain mode and the version is
> repe
Am Wed, Feb 26, 2025 at 03:00:07PM +0100 schrieb Julien Plissonneau Duquène:
> But the best approach is probably to switch to mode=git as this is more
> robust and future-proof, and there is no added value in fetching and using
> the source archives when they are generated automatically from the ta
Hi Andreas,
Apparently on the Tags page the links are now generated on the fly by
some Javascript code, and what appears in the page source is mangled
like:
data-download-links="[{"text":"zip","path":"/l_sim/v_sim/-/archive/3.8.0/v_sim-3.8.0.zip"},
You could try to scan for these but that se
Hi,
after the gitlab migration of v-sim upstream I drafted a watch file
following some examples that worked for me in the past on Gitlab. I
realised these examples watch files are also failing currently. Thus
I suspect some change on Gitlab and I wonder how I could fix the
watch file[1] which
On Wed, Aug 07, 2024 at 03:52:12PM +0200, PICCA Frederic-Emmanuel wrote:
> i just need to download
>
> https://drive.switch.ch/index.php/s/WOVSIPMky2JsXsp/download
[...]
> Is it possible to ask for uncoditionnal download ?
I don't think uscan is useful for this.
--
WBR, wRAR
signature.asc
D
thanks a lot I found the solution for this one.
the other which consiste in a simple download of a file via an url
https://drive.switch.ch/index.php/s/WOVSIPMky2JsXsp/download
the downloaded file endup with this name on the disk xlib_.jar
Is uscan capable to do the job for his
this wget comm
to myself :))
it works like this
# Fiji
https://downloads.imagej.net/fiji/archive/@ANY_VERSION@/
.*/@ANY_VERSION@/fiji-linux64.zip group
now the next one :))
i just need to download
https://drive.switch.ch/index.php/s/WOVSIPMky2JsXsp/download
$ uscan --report
Use of uninitialized value in
On Wed, Aug 07, 2024 at 03:25:25PM +0200, PICCA Frederic-Emmanuel wrote:
> Hello, I am trying to write a watch file for Fiji
>
> All the version are available in this
>
> https://downloads.imagej.net/fiji/archive/@ANY_VERSION@/fiji-linux64.zip
Where is the HTML page that lists t
Hello, I am trying to write a watch file for Fiji
All the version are available in this
https://downloads.imagej.net/fiji/archive/@ANY_VERSION@/fiji-linux64.zip
I tryed with the simple
version=4
https://downloads.imagej.net/fiji/archive/@ANY_VERSION@/fiji-linux64.zip
but I end up with this
On 23.02.24 01:15, Soren Stoutner wrote:
Hello,
Try the following:
That worked fine. Many thanks!
Hilmar
opts="searchmode=plain,repack,compression=xz,repacksuffix=+ds1,dversionmangle=s/
\+ds1//, \
pgpsigurlmangle=s%$%.asc%" \
https://api.github.com/repos/silnrsi/teckit/releases \
https://g
t@any_vers...@.tar.gz
On Thursday, February 22, 2024 3:59:18 PM MST Hilmar Preuße wrote:
> Hello,
>
> I could need some help with a debian/watch file [1]. The file is mostly
> not written by me, I just replaced just some regexes to introduce the
> correct versioning scheme. When running
Hello,
I could need some help with a debian/watch file [1]. The file is mostly
not written by me, I just replaced just some regexes to introduce the
correct versioning scheme. When running "uscan -vv" it downloads
correctly upstreams tar ball, the pgp is checked and the t
Am Thu, Oct 27, 2022 at 03:25:29PM +0530 schrieb Nilesh Patra:
> I pushed something via which I get:
>
> | uscan info: Launch mk-origtargz with options:
> | --package libomp-jonathonl --version 0.0+git20211216.5228495
> --compression default --directory .. --copyright-file debian/copyright
> .
On Thu, Oct 27, 2022 at 11:37:39AM +0200, Andreas Tille wrote:
> Hi Andrius,
>
> Am Thu, Oct 27, 2022 at 12:00:59PM +0300 schrieb Andrius Merkys:
> > I have just pushed a fix. Please check if that works for you as well.
>
> Hmmm, this results in
I pushed something via which I get:
| uscan info:
Hi Andreas,
On 2022-10-27 12:37, Andreas Tille wrote:
Am Thu, Oct 27, 2022 at 12:00:59PM +0300 schrieb Andrius Merkys:
I have just pushed a fix. Please check if that works for you as well.
Hmmm, this results in
uscan info: Newest version of libomp-jonathonl on remote site is
0.0+git201812
Hi Andrius,
Am Thu, Oct 27, 2022 at 12:00:59PM +0300 schrieb Andrius Merkys:
> I have just pushed a fix. Please check if that works for you as well.
Hmmm, this results in
uscan info: Newest version of libomp-jonathonl on remote site is
0.0+git20181221.506f3e5, local version is 0.0+git20181221
l" version="0.0+git20181221.506f3e5-1" (as
seen in debian/changelog)
uscan info: package="libomp-jonathonl" version="0.0+git20181221.506f3e5" (no
epoch/revision)
uscan info: ./debian/changelog sets package="libomp-jonathonl"
version="0.0+git
l" version="0.0+git20181221.506f3e5" (no
epoch/revision)
uscan info: ./debian/changelog sets package="libomp-jonathonl"
version="0.0+git20181221.506f3e5"
uscan info: Process watch file at: debian/watch
package = libomp-jonathonl
version = 0.0+git20181221.5
Hello Andreas,
On 2022-09-29 14:54 4, Andreas Tille wrote:
I confirm this works. However, uscan does not do the usual link to
orig.tar.gz. Any idea why this is the case?
I have found this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896705
But did you have signing key from Rob Egan
Hi Juri,
Am Thu, Sep 29, 2022 at 12:38:03PM +0200 schrieb Juri Grabowski:
> maybe it can be helpfull for you. So you can get commit hash of your tag
> with bitbucket api:
> curl -s -L
> https://api.bitbucket.org/2.0/repositories/berkeleylab/metabat/refs/tags/v2.15
> |jq -C -r .target.hash
I con
Hello,
maybe it can be helpfull for you. So you can get commit hash of your tag
with bitbucket api:
curl -s -L
https://api.bitbucket.org/2.0/repositories/berkeleylab/metabat/refs/tags/v2.15
|jq -C -r .target.hash
Other way is to use more generic git mode:
cat <<'EOF'>debian/watch
version=4
o
Hi,
the watch file for metabat[1] used to work nicely until some point in
time when bitbucket replaced `v@ANY_VERSION@` by the commit ID which is
not sensibly sorting any more. Is there any trick how I can get
bitbucket pages working again?
Kind regards
Andreas.
[1] https
On Wed, 2022-04-06 at 16:26 +, Eivind Naess wrote:
> The project is using ./autogen.sh to generate the configure scripts,
> et al for the project. When I got to tag and create a release, I have
> to upload the resulting tarball with the resulting configure scripts
> embedded.
Personally I wou
Hi,
On Wed, 2022-04-06 at 16:26 +, Eivind Naess wrote:
> Using watch with git tags yields the same thing (snapshot of the
> source code, not the release tarball). I could use the GitLab API and
> fetch a JSON file, but I can't figure out to make that work with the
> wa
On 6/25/21 3:32 AM, Paul Wise wrote:
On Thu, Jun 24, 2021 at 10:01 PM Hilmar Preuße wrote:
Hi,
Sorry for late Reply!
uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/,\
...
According to [1] the entry "uversionmangle=..." should handle the case
that there could be beta/
On Thu, Jun 24, 2021 at 10:01 PM Hilmar Preuße wrote:
> uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/,\
...
> According to [1] the entry "uversionmangle=..." should handle the case
> that there could be beta/rc versions, which should be ignored. When
> doing an uscan now i
Hi,
this is the current debian/watch file for proftp, it is not in the
archive yet, just on salsa:
version=4
opts=repack,compression=gz,repacksuffix=+dfsg,dversionmangle=s/\+dfsg//,\
uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/,\
pgpsigurlmangle=s@archive/refs/tags
On Tue, Nov 17, 2020 at 02:53:10PM +0100, Mechtilde Stehmann wrote:
> version=4
> opts=\
> filenamemangle=s/.*=(.*)/$1/ \
> https://pdfbox.apache.org/download.cgi
> .*/jbig2-imageio-(\d(\.\d)*)-src\.zip&action=download
To fix the version extraction, replace (\.\d)* with (?:\.\d)* to make it
non
My last try for a watch file is
version=4
opts=\
filenamemangle=s/.*=(.*)/$1/ \
https://pdfbox.apache.org/download.cgi
.*/jbig2-imageio-(\d(\.\d)*)-src\.zip&action=download
Can someone show me whrer I'm wrong?
Kind regards
--
Mechtilde Stehmann
## Debian Developer
## PGP encry
Dear Eriberto, and Sergio,
Really thanks for your help!
Yes, "downgrade" 2019 to 0.2019, is the perfect solution for my case.
And searching for \. by force seems to be a more generic solution.
I tried both, and both work as expected.
And through this practise, I understand the syntax
Em qui., 6 de ago. de 2020 às 14:35, Eriberto Mota
escreveu:
Note that the web browser plus webmail breaked the lines after
"releases". The two last lines shown below in each rule must be put in
a single line only.
> version=4
> https://github.com/shadowsocks/v2ray-plugin/releases
> .*/archive/v
gin/tags
>
> So my question is how to ignore the old version vMMDD, and only
> detect v1.y.z as latest version for d/watch file?
>
> BTW. I already read a few posts regarding on d/watch file [1][2], but
> still didn't find a proper solution.
This did it for me
version=4
So my question is how to ignore the old version vMMDD, and only
> detect v1.y.z as latest version for d/watch file?
>
> BTW. I already read a few posts regarding on d/watch file [1][2], but
> still didn't find a proper solution.
>
> [1] https://wiki.debian.org/debian/watch
.y.z as latest version for d/watch file?
BTW. I already read a few posts regarding on d/watch file [1][2], but
still didn't find a proper solution.
[1] https://wiki.debian.org/debian/watch
[2]
http://eriberto.pro.br/blog/2013/10/07/how-to-write-a-good-debianwatch-easily/
Thank you!
C
On Wed, Feb 05, 2020 at 11:38:07AM +0100, أحمد المحمودي wrote:
> When running uscan for elinks, it tries to fetch an older version for
> elinks, I cannot understand the reason, I hope someone would help me.
You have two watch files.
> uscan info: Process watch file at: debian/watch
>
When running uscan for elinks, it tries to fetch an older version for
elinks, I cannot understand the reason, I hope someone would help me.
Both the watch file and uscan verbose report are attached.
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R
On Wed, Nov 7, 2018 at 11:48 PM PICCA Frederic-Emmanuel wrote:
> so do you think that it is possible to write a watch file for this ?
These days uscan can check pretty much any page that contains a
version number. Look at the searchmode=plain or pagemangle options. If
something more complica
Hi!
The watch file have to be something like this:
version=4
http://xds.mpimf-heidelberg.mpg.de/html_doc/downloading.html
XDS-INTEL64_Linux_x86_64.tar.gz
The [1] will help you
Cheers!
[1] https://wiki.debian.org/debian/watch
El mié., 7 de nov. de 2018 a la(s) 12:48, PICCA Frederic
Hi,
IMHO a watch file for the site you refered is impossible.
Source of both the main page and the download page don't
contain any proper URI containing version string.
uscan does regular expression matching on the source
of webpage. for detail please refer uscan(1)
On Wed, Nov 07, 2018
Hello, I would like to create a watch file for this package
http://xds.mpimf-heidelberg.mpg.de/
as explained in page a new version is when the laast line of the page change.
then we can download the binaries from here
http://xds.mpimf-heidelberg.mpg.de/html_doc/downloading.html
so do you
On Thu, Aug 2, 2018 at 8:21 PM Robert James Clay wrote:
On Thu, Aug 2, 2018 at 1:58 PM Shengjing Zhu wrote:
>> And I think using upstream http release page is much simpler for you.
> I'm inclined to agree and will look at using that site instead.
In testing with using the download
On Thu, Aug 2, 2018 at 1:58 PM Shengjing Zhu wrote:
> Not about repack, current watch file will download tarball that github
> generated, not the one upstream uploading to github release. Look at
> https://github.com/ledgersmb/LedgerSMB/releases, please be careful
> that
the archive does look to have
> been repacked (it's smaller) and so the verify fails.
Not about repack, current watch file will download tarball that github
generated, not the one upstream uploading to github release. Look at
https://github.com/ledgersmb/LedgerSMB/releases, please be caref
All,
The upstream for the ledgersmb package [1] moved from Sourceforge to GitHub
including for where new releases of the application are made available; so
the debian/watch file in the package needed to be`updated for the new
locations of the distribution archive and its detached`gpg file that
codesearch can help to find watch file examples.
>
I don't know https://codesearch.debian.net. Thanks for this tip.
> > Or is there a package in which this has already been solved?
>
> uversionmangle does the trick, see the attached watch files.
>
I could not have solv
On 07/08/2018 10:41 AM, Jörg Frings-Fürst wrote:
> Does anyone have a tip or a solution to the problem?
codesearch can help to find watch file examples.
> Or is there a package in which this has already been solved?
uversionmangle does the trick, see the attached watch files.
Kind R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
the source for ipmitool has moved to github.
Now I'm looking to get the watch file running.
Prob is that file use underline instead dots[1] (IPMITOOL_1_8_18).
The same is on gitlab for sane-backends.
Does anyone have a tip or a sol
Hello Eriberto,
On Sat, Sep 09, 2017 at 11:04:50PM -0300, Eriberto wrote:
>
> Hi Elías,
>
> You can try it:
>
> version=4
> http://sf.net/urlget/ .*stable.*/uget-([\d.]+)\.tar\.(?:bz2|gz|xz)
It works fine! Thanks a lot Eriberto! =)
Best regards,
Elías Alejandro
2017-09-09 21:47 GMT-03:00 Elías Alejandro :
>
> I'm trying to get a correct debian/watch file for my package. The
> upstream source is from sourceforge[1] but it has a white space
> in the path[2]. I'd like to get the lastest source from "uget (stable)"
> but u
Hello everyone,
I'm trying to get a correct debian/watch file for my package. The
upstream source is from sourceforge[1] but it has a white space
in the path[2]. I'd like to get the lastest source from "uget (stable)"
but under the normal case I only get the source fr
On Wed, Jun 28, 2017 at 04:56:52AM +, John Horigan wrote:
> When I upload my package contextfree to mentors.debian.net, in the QA
> information I get this:
> A watch file is present but doesn't work
> -- Scanning for watchfiles in .
> -- Found watchfile in ./debian
> -
When I upload my package contextfree to mentors.debian.net, in the QA
information I get this:
A watch file is present but doesn't work
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- Scan finished
My watch file looks like this:
version=4
options="pgpsigurlmangl
On Tue, Jan 17, 2017 at 2:47 PM, PICCA Frederic-Emmanuel wrote:
> so it seems that I have a problem with the upstream versioning
...
> the final release is tango-9.2.5a which is considered lower than
> tango-9.2.5-rcx
>
> how should I change my watch file to take this into acc
On Mon, Jan 16, 2017 at 11:01 PM, PICCA Frederic-Emmanuel wrote:
> No issues, I just wanted to know if I could have something with uscan which
> work out of the box with both URL's.
> So I would like something without the comment / uncomment trick.
uscan works out of the box with both URLs as fa
On Mon, Jan 16, 2017 at 5:34 PM, PICCA Frederic-Emmanuel wrote:
> Here my current watch content where I comment and uncomment the URL.
Just uncommenting both seems to work for me, what issue do you get?
--
bye,
pabs
https://wiki.debian.org/PaulWise
Hello,
for one of my package, I need to check at two location for new upstream release.
the official release are usually located on sourceforge.
but rc's are usually provided via their internal ftp.
This is important for me to be able to prepare experimental upload of the rc's.
so I would like t
On Wed, Jan 11, 2017 at 03:16:38PM +0100, Sascha Steinbiss wrote:
> > Any idea how to properly download the upstream source tarball with
> > uscan?
>
> could you please try:
>
> opts=filenamemangle=s/.*\.tar\.gz\?ref=ecopcr_v?(\d\S+)/ecopcr-$1\.tar\.gz/g
> \
> https://git.metabarcoding.org/obit
Hi Andreas,
[...]
> Any idea how to properly download the upstream source tarball with
> uscan?
could you please try:
opts=filenamemangle=s/.*\.tar\.gz\?ref=ecopcr_v?(\d\S+)/ecopcr-$1\.tar\.gz/g
\
https://git.metabarcoding.org/obitools/ecopcr/tags?sort=updated_desc
.*archive\.tar\.gz\?ref=ecop
Hi,
upstream of ecopcr has added release tags at my request in their
local gitlab instance. I think I adapted d/watch[1] accordingly
but when doing
uscan --verbose --force-download
it just says
uscan info:=> Package is up to date for from
https://git.metabarcoding.org/obitools/ec
Figured it out! The ':' character was literal. So now I have this working:
.*ru[tT]orrent@ANY_VERSION@@ARCHIVE_EXT@
https://wiki.debian.org/debian/watch#Common_mistakes gave me the idea
On Mon, Jan 9, 2017 at 10:13 AM, Taylor Kline wrote:
> My debian/watch file is not matching anyt
On Mon, Jan 09, 2017 at 10:13:01AM -0500, Taylor Kline wrote:
> I would think this should match the website which has hrefs such as:
> ruTorrent-3.7.zip
> rutorrent-3.6.tar.gz
It doesn't.
> rel="nofollow">ruTorrent-3.7.zip
As you can see here or by looking at the page source yourself, the href is
My debian/watch file is not matching anything, and I'm not sure why.
Here's the file:
version=4
https://dl.bintray.com/novik65/generic/ ru[tT]orrent@ANY_VERSION@@ARCHIVE_EXT
I would think this should match the website which has hrefs such as:
ruTorrent-3.7.zip
rutorrent-3.6.tar.gz
Unf
he
>>>> code from the watch file to build.
>>>
>>> Please read how gbp works.
>>> gbp uses the version from d/changelog to find the upstream tag which it
>>> then uses to recreate the orig tarball.
>>
>>
>> I have been reading t
On Sun, Dec 11, 2016 at 01:24:26AM -0700, Herminio Hernandez Jr wrote:
> > > Let me try to clarify. Did my package use the code from upstream or the
> > > code from the watch file to build.
> >
> > Please read how gbp works.
> > gbp uses the version from d/chan
On Sunday, December 11, 2016 1:20:05 PM MST Andrey Rahmatullin wrote:
> On Sun, Dec 11, 2016 at 01:16:21AM -0700, Herminio Hernandez Jr wrote:
> > Let me try to clarify. Did my package use the code from upstream or the
> > code from the watch file to build.
>
> Please read
On Sun, Dec 11, 2016 at 01:16:21AM -0700, Herminio Hernandez Jr wrote:
> Let me try to clarify. Did my package use the code from upstream or the code
> from the watch file to build.
Please read how gbp works.
gbp uses the version from d/changelog to find the upstream tag which it
then u
On Sunday, December 11, 2016 12:57:40 PM MST Andrey Rahmatullin wrote:
> On Sat, Dec 10, 2016 at 11:04:30PM -0700, Herminio Hernandez Jr wrote:
> > I have a question regarding packaging using git and the watch file in the
> > Debian directory. There is an open bug 794438 for th
On Sat, Dec 10, 2016 at 11:04:30PM -0700, Herminio Hernandez Jr wrote:
> I have a question regarding packaging using git and the watch file in the
> Debian directory. There is an open bug 794438 for the KDE Partition Manager.
> The current package is broken in Sid. In the thread it was
Dear Mentors,
I have a question regarding packaging using git and the watch file in the
Debian directory. There is an open bug 794438 for the KDE Partition Manager.
The current package is broken in Sid. In the thread it was mentioned that the
KDE Neon has a working package. When I pulled the
On Sat, Dec 03, 2016 at 04:08:21PM +, James Cowgill wrote:
> > I'd not call this a real constraint since there was no update for nearly
> > 10 years - but anyway, it would be nice to have.
>
> Seems to be the same directory as:
> ftp://ftp.sanger.ac.uk/pub/project/acedb/
Works. Thanks a lot
On 03/12/16 16:02, Andreas Tille wrote:
> On Sat, Dec 03, 2016 at 01:57:35PM -0200, Eriberto wrote:
>> 2016-12-03 13:54 GMT-02:00 Andrey Rahmatullin :
>>> Um.
>>> Maybe it's somehow linked to the fact that there is no "acedb" in the ls
>>> result at ftp://ftp.sanger.ac.uk/pub (even though cd works)
On Sat, Dec 03, 2016 at 01:57:35PM -0200, Eriberto wrote:
> 2016-12-03 13:54 GMT-02:00 Andrey Rahmatullin :
> > Um.
> > Maybe it's somehow linked to the fact that there is no "acedb" in the ls
> > result at ftp://ftp.sanger.ac.uk/pub (even though cd works).
>
> yeap!
In other words: There is no
2016-12-03 13:54 GMT-02:00 Andrey Rahmatullin :
> On Sat, Dec 03, 2016 at 04:45:47PM +0100, Andreas Tille wrote:
>> uscan info: Requesting URL:
>>ftp://ftp.sanger.ac.uk/pub/acedb/SUPPORTED/
>> uscan warn: In watch file debian/watch, reading FTP directory
>> ftp:/
On Sat, Dec 03, 2016 at 04:45:47PM +0100, Andreas Tille wrote:
> uscan info: Requesting URL:
>ftp://ftp.sanger.ac.uk/pub/acedb/SUPPORTED/
> uscan warn: In watch file debian/watch, reading FTP directory
> ftp://ftp.sanger.ac.uk/pub/acedb/SUPPORTED/ failed: 404 Can't chdir
Hi,
the source location of acedb has changed. I tried to fix the watch file as:
version=4
opts=passive \
ftp://ftp.sanger.ac.uk/pub/acedb/SUPPORTED/ACEDB-source\.([0-9.]+)\.tar\.gz
but this results in:
$ uscan --verbose
uscan info: uscan (version 2.16.10) See uscan(1) for help
uscan info
Eriberto writes:
> There are three problems here.
Thanks for taking a look!
> 1. The current FTP address is
> ftp://ftp.ncbi.nih.gov/toolbox/ncbi_tools/old/, not
> ftp://ftp.ncbi.nlm.nih.gov/toolbox/ncbi_tools/old.
Hm? Either name is valid, and I'd say the variant with .nlm is
preferred:
$
Hi Eriberto,
On Thu, Dec 01, 2016 at 11:48:12AM -0200, Eriberto wrote:
>
> https://bibiserv2.cebitec.uni-bielefeld.de/rnahybrid?id=rnahybrid_view_download
> redirects to https://bibiserv2.cebitec.uni-bielefeld.de/sessionTimeout.jsf,
> that shows the following message:
>
>
> ERROR - Session expi
Hi Eriberto,
On Thu, Dec 01, 2016 at 11:01:56AM -0200, Eriberto wrote:
>
> Please, try the folowing structure:
>
> version=4
> opts="passive,uversionmangle=s|^|6.1.|" \
> http://ftp.ncbi.nih.gov/toolbox/ncbi_tools/old/ (\d{8}[a-z]*)/
>
> I hope this help.
Thanks, this was extremly helpful (aft
Hi,
2016-12-01 10:56 GMT-02:00 Andreas Tille :
> Hi,
>
> I was trying to rewrite the watch file for rnahybrid[1] as
>
> version=4
> https://bibiserv2.cebitec.uni-bielefeld.de/rnahybrid?id=rnahybrid_view_download
> .*/downloads/RNAhybrid-(\d[.\d]+)\.tar\.gz
https://
Hi Andreas,
2016-12-01 9:15 GMT-02:00 Andreas Tille :
>
> I just noticed that there is a new upstream version of ncbi-tools6[1].
> The current d/watch file in Git[2] locks as:
>
>
> version=3
> # Too bad uscan doesn't actually honor downloadurlmangle for FT
Hi,
I was trying to rewrite the watch file for rnahybrid[1] as
version=4
https://bibiserv2.cebitec.uni-bielefeld.de/rnahybrid?id=rnahybrid_view_download
.*/downloads/RNAhybrid-(\d[.\d]+)\.tar\.gz
but I get
$ uscan --verbose
uscan info: uscan (version 2.16.8) See uscan(1) for help
uscan info
Hi,
I just noticed that there is a new upstream version of ncbi-tools6[1].
The current d/watch file in Git[2] locks as:
version=3
# Too bad uscan doesn't actually honor downloadurlmangle for FTP urls. :-/
# [would use downloadurlmangle="s|$|/ncbi.tar.gz|]
opts="uversionmangle=s|^
On Mon, Nov 14, 2016 at 9:10 PM, Andreas Tille wrote:
> I wonder how to write d/watch to catch the latest version for
> libsis-jhdf5-java which is in a directory hierarchy[1]. Currently the
> last version is 14.12.6 - but if the major version changes the directory
> changes as well. Any hint how
Hi,
I wonder how to write d/watch to catch the latest version for
libsis-jhdf5-java which is in a directory hierarchy[1]. Currently the
last version is 14.12.6 - but if the major version changes the directory
changes as well. Any hint how to safely get the latest version?
Kind regards
An
Dominik George writes:
> I wonder what of these two options is the "correct" solution for an
> upstream that is not watch'able (e.g. has no release tarballs, etc.) -
> besides making upstream have release tarballs, that is ;):
>
> a) no watch file
> b) a watch
Thanks Daniel! Thanks Sascha!
Cheers,
Eriberto
> To avoid a false impression that you ignored the watch file by
> laziness and to inform an actual status, I created three fake
> packages[1]. These packages say if there no upstream site, if there no
> release in upstream site or if the upstream site there a package but
> doesn&#
t; besides making upstream have release tarballs, that is ;):
>>
>> a) no watch file
>> b) a watch file with only comments
>>
>> In case a), lintian complains and proposes to place a watch file with a
>> comment explaining why it is otherwise empty [0].
>>
Hi Dominik,
2016-10-11 8:53 GMT-03:00 Dominik George :
>
> I wonder what of these two options is the "correct" solution for an
> upstream that is not watch'able (e.g. has no release tarballs, etc.) -
> besides making upstream have release tarballs, that is ;):
>
>
Hi,
I wonder what of these two options is the "correct" solution for an
upstream that is not watch'able (e.g. has no release tarballs, etc.) -
besides making upstream have release tarballs, that is ;):
a) no watch file
b) a watch file with only comments
In case a), lintia
Hi,
On Wed, Aug 31, 2016 at 12:51:57PM +0500, Andrey Rahmatullin wrote:
> On Wed, Aug 31, 2016 at 09:44:59AM +0200, Andreas Tille wrote:
> > I was following the Wiki[1] to get a bitbucket watch for metaphlan2[2].
> > Unfortunately uscan does not detect any match and after starring on the
> > code
autogenerated link for downloading the entire
repository
- two .txt files that have nothing to do with the release
In fact, there don't appear to be any upstream tarballs available.
However, they do appear to tag their releases, so (not tested though)
the following watch file shou
On Wed, Aug 31, 2016 at 09:44:59AM +0200, Andreas Tille wrote:
> I was following the Wiki[1] to get a bitbucket watch for metaphlan2[2].
> Unfortunately uscan does not detect any match and after starring on the
> code and trying several other regexp I failed finding the mistake.
There is no tarball
Hi,
I was following the Wiki[1] to get a bitbucket watch for metaphlan2[2].
Unfortunately uscan does not detect any match and after starring on the
code and trying several other regexp I failed finding the mistake.
Any idea how to get the watch file working and reporting 2.6.0 as latest
version
On Sat, Oct 17, 2015 at 1:03 PM, Ross Gammon wrote:
> > * Pau Garcia i Quiles , 2015-10-17, 12:19:
> >> Why are you keeping the old versioning scheme if upstream has changed
> >> to a different scheme?
>
> Jakub's simple fix works, and I have asked upstream what the intentions
> are going forwar
On 10/17/2015 12:38 PM, Jakub Wilk wrote:
> On Sat, Oct 17, 2015 at 11:55 AM, Ross Gammon wrote:
[...]
>>> The last uploaded version was 20150908 and now there is an upstream
>>> tarball with the version "2015.10.08".
>>>
>>> The watch file wa
08".
The watch file was simple:
version=3
opts=uversionmangle=s/-//g \
http://ifdo.pugmarks.com/~seymour/runabc/top.html abcMIDI-(.*)\.zip
But now a uscan --repack tells me that:
Newest version on remote site is 2015.10.08, local version is 20150908
=> remote site does not even have cur
version "2015.10.08".
>
> The watch file was simple:
> version=3
> opts=uversionmangle=s/-//g \
> http://ifdo.pugmarks.com/~seymour/runabc/top.html abcMIDI-(.*)\.zip
>
> But now a uscan --repack tells me that:
> Newest version on remote site is 2015.10.08, local ve
1 - 100 of 412 matches
Mail list logo
