Hi,
Does anybody know what's wrong with the following watch file for my
meanwhile package?
version=3
# [0-9] because without, meanwhile-gaim-xxx also matches!
http://sf.net/meanwhile/meanwhile-([0-9].*)\.tar\.gz
Running uscan seems to work correctly:
$ uscan --verbose
-- Scannin
Hello mentors,
What's watch file? I found that my package don't have it, but I couldn't
find the description of this file.
--
Miguel Gea Milvaques <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello mentors,
What's watch file? I found that my package don't have it, but I couldn't
find the description of this file.
--
Miguel Gea Milvaques <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Vanden Berghe wrote:
| Hi,
|
| Does anybody know what's wrong with the following watch file for my
| meanwhile package?
| Newest version on remote site is 1.0.2, local version is 1.0.2
| => Package is up to date
| -- Scan finished
|
Hi Neil,
> RIGHT at the bottom is the date of the last run, 9th Jan 2006 which is
> BEFORE your last package update AFAICT. So just like me, you are
> probably still waiting for DEHS to even start working with your uploaded
> watch file for the first time!
Actually, the watch file ha
Hi
I have been trying to fix my watch file. It contains the following line:
http://heanet.dl.sourceforge.net/sourceforge/muparser/muparser_v(.*)\.tar\.gz
The problem is that the version is 1.30 but the upstream source file contains
the number v130. I have been trying to use uversionmangle to
Hi,
I've noticed that lintian produces a warning when a package has no
debian/watch file (at least when run with the -iI flags). I read the uscan(1)
manpage, as the warning suggests, but I still am not sure if I got the format
of the debian/watch file right. The manpage has this example:
Hi all,
I am building package from source downloaded here:
https://launchpad.net/invada-studio/+download
and this is file I would like to monitor by watch file:
invada-studio-plugins_0.3.1-nopkg.tar.gz
I tried this forms in watch file:
https://launchpad.net/invada-studio/+download/invada
Greetings,
I am attempting to write a watch file, but am hitting some issues. I
thought I would start with a pretty simple regex to grab the static
upstream version:
% cat debian/watch
version=3
https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/OCSNG_UNIX_SERVER-(2.1).tar.gz
Dear list (again :-)),
thank you very much for helping so far --
I have now another problem: the upstream url is something like
<http://stsdas.stsci.edu/astrolib/pywcs-1.10-4.7.tar.gz>, but the URL
<http://stsdas.stsci.edu/astrolib/> just gives some errors, preventing
the watch file
I'm again about GNOME PPP. Please, someone who knows, look at
www.gnome-ppp.org and tell me if it's possible to write a debian watch
file for it. I guess no, but maybe.
--
Dan Korostelev <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
On Thu, Oct 14, 2004 at 09:25:50AM +0200, MiguelGea wrote:
> Hello mentors,
> What's watch file? I found that my package don't have it, but I couldn't
> find the description of this file.
Short answer is man uscan
A watch file describes where the ustream tarbals can b
also sprach MiguelGea <[EMAIL PROTECTED]> [2004.10.14.0925 +0200]:
> What's watch file? I found that my package don't have it, but I couldn't
> find the description of this file.
Check out uscan(1) in the devscripts package.
--
Please do not CC me when rep
On Thu, 14 Oct 2004 09:25:50 +0200
MiguelGea <[EMAIL PROTECTED]> wrote:
> Hello mentors,
> What's watch file? I found that my package don't have it, but I couldn't
> find the description of this file.
$ more /usr/share/debhelper/dh_make/debians/watch.ex
regar
On Thu, Oct 14, 2004 at 09:25:50AM +0200, MiguelGea wrote:
> Hello mentors,
> What's watch file? I found that my package don't have it, but I couldn't
> find the description of this file.
Short answer is man uscan
A watch file describes where the ustream tarbals can b
also sprach MiguelGea <[EMAIL PROTECTED]> [2004.10.14.0925 +0200]:
> What's watch file? I found that my package don't have it, but I couldn't
> find the description of this file.
Check out uscan(1) in the devscripts package.
--
Please do not CC me when rep
On Thu, 14 Oct 2004 09:25:50 +0200
MiguelGea <[EMAIL PROTECTED]> wrote:
> Hello mentors,
> What's watch file? I found that my package don't have it, but I couldn't
> find the description of this file.
$ more /usr/share/debhelper/dh_make/debians/watch.ex
regar
I'm again about GNOME PPP. Please, someone who knows, look at
www.gnome-ppp.org and tell me if it's possible to write a debian watch
file for it. I guess no, but maybe.
--
Dan Korostelev <[EMAIL PROTECTED]>
When specifying the regexp to be used in a watch file, are backslashes
supposed to be escaped? The New Maintainer's Guide says one thing, but
the man page for uscan says another. Which is preferred/correct?
Where do I ask to get the incorrect version updated?
man uscan:
--
#
When specifying the regexp to be used in a watch file, are backslashes
supposed to be escaped? The New Maintainer's Guide says one thing, but
the man page for uscan says another. Which is preferred/correct?
Where do I ask to get the incorrect version updated?
man uscan:
--
#
Hi mentors!
I have one watch file with the following lines:
version=3
ftp://ftp.genetics.wustl.edu/pub/eddy/software/squid-(.*)\.tar\.gz
Doing an uscan --verbose, I get:
$ uscan --verbose
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile
[CC'd to mentors; please also CC replies directly to me as I'm not
subscribed to that list.]
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411425
http://www.s48.org/1.7/scheme48-1.7.tgz
http://mentors.debian.net/debian/pool/main/s/scheme48/
Regarding
> Please add a debian/watc
://mentors.debian.net/debian/pool/main/s/scheme48/
>
> Regarding
>
> > Please add a debian/watch file.
>
> ...I haven't been able to work out how to do this, because
> http://s48.org/ has a link to 1.7/download.html instead of to 1.7/ --
> this means that the naïve
On Mon, Nov 26, 2007 at 03:08:12PM +, Daniel Leidert wrote:
>>> Please add a debian/watch file.
>
> version=3
> opts=downloadurlmangle=s/([^\/]+)\/download.html$/$1\/scheme48-$1.tgz/,filenamemangle=s/([^\/]+)\/download.html/scheme48-$1.tgz/
> \
> http://s48.o
On Mon, Nov 26, 2007 at 08:30:56PM +1100, Trent W. Buck wrote:
> ...I haven't been able to work out how to do this, because
> http://s48.org/ has a link to 1.7/download.html instead of to 1.7/
Here's a version that works, using the downloadurlmangle option:
version=3
opts=downloadurlmangle=s
Am Montag, den 26.11.2007, 10:31 -0500 schrieb Eric Cooper:
> On Mon, Nov 26, 2007 at 08:30:56PM +1100, Trent W. Buck wrote:
> > ...I haven't been able to work out how to do this, because
> > http://s48.org/ has a link to 1.7/download.html instead of to 1.7/
>
> Here's a version that works, using
Hello mentors and fonts-task-force,
Lately I'm working on cleaning my packages and one of them is the
ttf-breip [0] font, which is pretty much clean except that i'm having a
lintian warning about its watch file.
The thing is that the format of the url [1] is something similar to
h
On Fri, Aug 22, 2008 at 3:36 PM, Gudjon I. Gudjonsson <[EMAIL PROTECTED]> wrote:
> I have been trying to fix my watch file. It contains the following line:
> http://heanet.dl.sourceforge.net/sourceforge/muparser/muparser_v(.*)\.tar\.gz
Please use the Debian QA redirector for sf.ne
Thanks Paul
> There is one in the uscan manual page:
>
>http://www.site.com/pub/foobar/foobar_v(\d+)_(\d+)\.tar\.gz
I had seen the example but didn't believe it would help.
Anyway, it dows and the following line does the trick :)
http://sf.net/muparser/muparser_v(\d)(\d+)\.tar\.gz debian u
On Tue, Mar 24, 2009 at 10:22:09AM +0200, Panagiotes [paggas] Mousikides wrote:
>
> If I got it correct, it means that (.*) will match the version used for the
> orig.tar.gz archive?
Correct.
--
Jonathan Wiltshire
PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52
--
"Panagiotes [paggas] Mousikides" writes:
> The manpage has this example:
>
> ftp://ftp.tex.ac.uk/tex-archive/web/c_cpp/cweb/cweb-(.*)\.tar\.gz
>
> If I got it correct, it means that (.*) will match the version used
> for the orig.tar.gz archive?
Yes. Unfortunately, I just noticed that it will
Hi mira,
On Wed, Aug 05, 2009 at 01:19:15PM +0200, Jarom?r Mike? wrote:
> I am building package from source downloaded here:
> https://launchpad.net/invada-studio/+download
>
> and this is file I would like to monitor by watch file:
> invada-studio-plugins_0.3.1-nopkg.tar.gz
&g
Sebastian Harl writes:
> You can thus use the format ' ' which will then download
> the website found at and scan it for hrefs (i.e. )
Not the website (fortunately for our bandwidth charges); just the one
document (“web page”) at the specified URL.
--
\ “I like to reminisce with peo
This time the web page contains this :
mypackage.zip - v1.01
I'm stuck with uscan getting what's inside an href.
Is there a way to get the version number, which is outside the href ?
Jérémy Lal
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe".
Dear Mentors,
I'm having some trouble at creating a watch file for the packace "preload".
The upstream tarballs are found as follows:
http://sourceforge.net/projects/preload/files/preload/0.6.4/preload-0.6.4.tar.gz
The problem lies where its parent folder changes at every releas
Is it possible to have a generic git watchfile?
How about gitorius?
thanks!
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CALkubT5CThzfpRQrTCf7mL=zfkj6fghnbpvga
Hi,
I stumbled upon another watch file problem for package visad which is
available via ftp. I considered the following watch file a good idea
opts=downloadurlmangle=s?$?/visad_src.jar?,filenamemangle=s?$?/visad_src.jar? \
ftp://ftp.ssec.wisc.edu/pub/visad-([\d\.]+)
but got the following
Hi,
the watch file of the prospective package meme[1] is reporting a new
version but fails to download the latest version (4.9.0.4). It was
working nicely with version 4.9.0.3. I just get:
$ uscan --verbose --force-download
...
3.5.1/meme_3.5.1.tar.gz
3.5.0/meme_3.5.0.tar.gz
Newest
Hi,
rel2gpx was moved to a new location
http://blog.velocarte66.fr/?q=de/node/170
I tried to adapt the watch file to
http://anonscm.debian.org/gitweb/?p=pkg-grass/rel2gpx.git;a=commitdiff;h=HEAD
but this does not work as expected. Any hint?
Kind regards
Andreas.
--
http://fam
On 17/03/14 22:21, Matt Zagrabelny wrote:
> Greetings,
>
> I am attempting to write a watch file, but am hitting some issues. I
> thought I would start with a pretty simple regex to grab the static
> upstream version:
>
> % cat debian/watch
> version=3
> https://launch
* Matt Zagrabelny , 2014-03-17, 17:21:
https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/
failed: 500 Can't connect to launchpad.net:443
I believe this is because the "ValiCert Class 2 Policy Validation
Authority" certificate, which signs the launchpad.net certificate, has
On Tue, Mar 18, 2014 at 4:32 AM, Jakub Wilk wrote:
> * Matt Zagrabelny , 2014-03-17, 17:21:
>
>> https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/
>> failed: 500 Can't connect to launchpad.net:443
>
>
> I believe this is because the "ValiCert Class 2 Policy Validation Authority"
* Matt Zagrabelny , 2014-03-18, 09:17:
As a temporary work-around, you can disable certificate verification
by setting the PERL_LWP_SSL_VERIFY_HOSTNAME environment variable to 0.
Thanks for the information, Jakub!
Things look good when run from the command line:
% PERL_LWP_SSL_VERIFY_HOSTNAME
Hi,
I wonder how I might get a watch file for code.google.com working.
For FreeDiams I tried
version=3
http://code.google.com/p/freemedforms/downloads/list \
http://freemedforms.googlecode.com/files/freediams_([.\d]+).*\.tar\.gz
but uscan does not find any matching entry - probably because
Hi,
Upstream have changed one of my package's versioning on the tarball
(http://anonscm.debian.org/cgit/collab-maint/abcmidi.git).
The last uploaded version was 20150908 and now there is an upstream
tarball with the version "2015.10.08".
The watch file was simple:
version=3
opts
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
-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
Ole Streicher writes:
> <http://www.debian.org/doc/manuals/maint-guide/dother.en.html#docs>
> | Normally with a watch file, the URL at http://sf.net/gentoo is
>
> in my case, this is http://trac.ass
Dan Korostelev wrote, On 06/28/2004 06:17 PM:
I'm again about GNOME PPP. Please, someone who knows, look at
www.gnome-ppp.org and tell me if it's possible to write a debian watch
file for it. I guess no, but maybe.
It is...
K.
--
Lucas Wall <[EM
Dan Korostelev wrote, On 06/28/2004 06:17 PM:
I'm again about GNOME PPP. Please, someone who knows, look at
www.gnome-ppp.org and tell me if it's possible to write a debian watch
file for it. I guess no, but maybe.
It is...
K.
--
Lucas Wa
My uscan man page only uses one backslash..
On Wed, Mar 13, 2002 at 03:01:32PM -0800, Ian Duggan wrote:
>
> When specifying the regexp to be used in a watch file, are backslashes
> supposed to be escaped? The New Maintainer's Guide says one thing, but
> the man page for uscan sa
Ian Duggan wrote:
>
> When specifying the regexp to be used in a watch file, are backslashes
> supposed to be escaped? The New Maintainer's Guide says one thing, but
> the man page for uscan says another. Which is preferred/correct?
Install the uscan from unstable, and do not e
On Thu, Mar 14, 2002 at 12:50:33AM -0500, Joey Hess wrote:
> Ian Duggan wrote:
> >
> > When specifying the regexp to be used in a watch file, are backslashes
> > supposed to be escaped? The New Maintainer's Guide says one thing, but
> > the man page for uscan
> And go for version 2.6.91 (which has just been uploaded) if you have
> any FTP sites; version 2.6.90 was broken for them. See uscan(1) in
> the new package for a description of the new watch file format.
>
> The new devscripts also features a funky new config file.
>
&g
On Thu, Mar 14, 2002 at 12:00:31PM -0800, Ian Duggan wrote:
> I looked on the mirrors and the latest I can find is 2.6.90. Where would
> I look to find 2.6.91? I looked in the /pool/d/devscripts/ dir on
> mirrors.kernel.org/debian and http.us.debian.org.
At the time Julian posted, it was available
On Thu, Mar 14, 2002 at 12:00:31PM -0800, Ian Duggan wrote:
>
> > And go for version 2.6.91 (which has just been uploaded) if you have
> > any FTP sites; version 2.6.90 was broken for them. See uscan(1) in
> > the new package for a description of the new watch file for
My uscan man page only uses one backslash..
On Wed, Mar 13, 2002 at 03:01:32PM -0800, Ian Duggan wrote:
>
> When specifying the regexp to be used in a watch file, are backslashes
> supposed to be escaped? The New Maintainer's Guide says one thing, but
> the man page for u
Ian Duggan wrote:
>
> When specifying the regexp to be used in a watch file, are backslashes
> supposed to be escaped? The New Maintainer's Guide says one thing, but
> the man page for uscan says another. Which is preferred/correct?
Install the uscan from unstable, and do not e
On Thu, Mar 14, 2002 at 12:50:33AM -0500, Joey Hess wrote:
> Ian Duggan wrote:
> >
> > When specifying the regexp to be used in a watch file, are backslashes
> > supposed to be escaped? The New Maintainer's Guide says one thing, but
> > the man page for uscan
> And go for version 2.6.91 (which has just been uploaded) if you have
> any FTP sites; version 2.6.90 was broken for them. See uscan(1) in
> the new package for a description of the new watch file format.
>
> The new devscripts also features a funky new config file.
>
&g
On Thu, Mar 14, 2002 at 12:00:31PM -0800, Ian Duggan wrote:
> I looked on the mirrors and the latest I can find is 2.6.90. Where would
> I look to find 2.6.91? I looked in the /pool/d/devscripts/ dir on
> mirrors.kernel.org/debian and http.us.debian.org.
At the time Julian posted, it was availabl
On Thu, Mar 14, 2002 at 12:00:31PM -0800, Ian Duggan wrote:
>
> > And go for version 2.6.91 (which has just been uploaded) if you have
> > any FTP sites; version 2.6.90 was broken for them. See uscan(1) in
> > the new package for a description of the new watch file for
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
Nelson A. de Oliveira wrote:
> Hi mentors!
>
> I have one watch file with the following lines:
>
> version=3
> ftp://ftp.genetics.wustl.edu/pub/eddy/software/squid-(.*)\.tar\.gz
>
> Doing an uscan --verbose, I get:
>
> $ uscan --verbose
> -- Scanning for watchf
Hi!
On 8/4/06, Roberto C. Sanchez <[EMAIL PROTECTED]> wrote:
> What is the correct line to get versions from a FTP directory, with
> files like
> ftp://ftp.genetics.wustl.edu/pub/eddy/software/squid-1.9g.tar.gz?
Add "debian uupdate" (without quotes) at the end of t
tl.edu/pub/eddy/software/squid-1.9g.tar.gz?
> >
> >Add "debian uupdate" (without quotes) at the end of the line in the
> >watch file.
>
> Still not :-(
>
> $ uscan --verbose
> -- Scanning for watchfiles in .
> -- Found watchfile in ./debian
> -- In
On Fri, 04 Aug 2006 16:45:42 -0300, Nelson A. de Oliveira wrote:
> I have one watch file with the following lines:
>
> version=3
> ftp://ftp.genetics.wustl.edu/pub/eddy/software/squid-(.*)\.tar\.gz
>
> Doing an uscan --verbose, I get:
[..]
> What is the correct line to ge
also sprach gregor herrmann <[EMAIL PROTECTED]> [2006.08.05.0010 +0100]:
> So I guess the watch file syntax is correct. Maybe some network
> problem at your side or at ftp.genetics.wustl.edu?
Consider passive mode on/off ?
--
Please do not send copies of list mail to me; I r
Hi!
On 8/4/06, martin f krafft <[EMAIL PROTECTED]> wrote:
> So I guess the watch file syntax is correct. Maybe some network
> problem at your side or at ftp.genetics.wustl.edu?
Consider passive mode on/off ?
Yes, it was this.
Using "uscan --pasv --verbose" with uscan f
Hello Nelson,
On Sat, 05 Aug 2006, Nelson A. de Oliveira wrote:
> On 8/4/06, martin f krafft <[EMAIL PROTECTED]> wrote:
> >> So I guess the watch file syntax is correct. Maybe some network
> >> problem at your side or at ftp.genetics.wustl.edu?
> >
> >Cons
Hi!
On 8/5/06, Kapil Hari Paranjape <[EMAIL PROTECTED]> wrote:
> But why on my system it is not working without --pasv? Everybody else
> (that answered) just used "uscan --verbose" and it worked...
> Can somebody, please, explain this to me?
2. Your network has a transparent proxy setup.
This
ing in the filename. That would be the ideal situation, and
you could then encode that in the 'debian/watch' file.
> And i don't know if i should add a lintian-override,
Rather than an override, you can simply add a 'debian/watch' file that
has (only) comments explainin
Hi,
On Tue, Jul 08, 2008 at 12:30:57AM +1000, Ben Finney wrote:
> > And i don't know if i should add a lintian-override,
>
> Rather than an override, you can simply add a 'debian/watch' file that
> has (only) comments explaining the current situation.
Hu?
> &
Patrick Schoenfeld <[EMAIL PROTECTED]> writes:
> On Tue, Jul 08, 2008 at 12:30:57AM +1000, Ben Finney wrote:
> > An empty watch file (with comments) is better than [a watch file
> > with a URL to an unversioned file].
>
> Whats your rationale for proposing to include u
On Tue, Jul 08, 2008 at 11:23:24PM +1000, Ben Finney wrote:
> Right. And the lintian message suggests exactly what I'm suggesting: a
> watch file that documents exactly why 'uscan' can't yet do its work
> for this particular package.
Seems wrong to me. The lintian tex
Patrick Schoenfeld <[EMAIL PROTECTED]> writes:
> On Tue, Jul 08, 2008 at 11:23:24PM +1000, Ben Finney wrote:
> > Right. And the lintian message suggests exactly what I'm
> > suggesting: a watch file that documents exactly why 'uscan' can't
> &
Hi,
On Wed, Jul 09, 2008 at 07:03:22PM +1000, Ben Finney wrote:
> My suggestion is that comments in the watch file are appropriate to
> document *any* reason why the package maintainer is currently unable
> to provide suitable information for 'uscan'.
Nothing against this. I
Patrick Schoenfeld <[EMAIL PROTECTED]> writes:
> Seems wrong to me. The lintian text states that a package which is
> "(...) not maintained upstream (...)" may add a commented watch file
> "(...) containing only comments to document this."
> In my opinion
Russ Allbery <[EMAIL PROTECTED]> writes:
> If the package is not maintained upstream or if upstream uses a
> distribution mechanism that cannot be meaningfully monitored by
> uscan and the Debian External Health Status project, please
> consider adding a
an decide to act upon. If you
>> add a comment in a watch file then you have a comment in a hidden place
>> for a lot of people who could potential fix the problem. They would need
>> to look *into* that specific package, which is unlikely.
>
> This is a problem that can be
Raphael Geissert wrote:
Russ Allbery wrote:
This is a problem that can be easily fixed if desired by, for instance,
having the Debian External Health Status system extract watch files
containing only comments and put the text of the comments up on the DEHS
web site.
Is that a feature request?
David L. Anselmi wrote:
> Raphael Geissert wrote:
>> Russ Allbery wrote:
>>> This is a problem that can be easily fixed if desired by, for instance,
>>> having the Debian External Health Status system extract watch files
>>> containing only comments and put the text of the comments up on the DEHS
Raphael Geissert <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>
> > having the Debian External Health Status system extract watch
> > files containing only comments and put the text of the comments up
> > on the DEHS web site.
>
> Is that a feature request? it sounds like one :)
>
> Implem
tomated in the Debian package with 'debian/rules get-orig-source',
> as per Policy 3.8.0 �§4.9
> =
Possibly related: The link provided to view the watch file
http://dehs.alioth.debian.org/wwiz_detail.php?id=11448238&type=watch>
leads to content served as UTF-8
Ben Finney wrote:
>
> Bug report: The file contents should be interpreted as UTF-8 encoding.
> Apparently it's not: the output I see at that URL today is (in part):
Fixed. htmlentities() was messing the special characters instead of making
them display properly.
Cheers,
--
Atomo64 - Raphael
Pl
provement, but now it shows the same (wrong) output as described
here:
Ben Finney <[EMAIL PROTECTED]> writes:
> Possibly related: The link provided to view the watch file
> http://dehs.alioth.debian.org/wwiz_detail.php?id=11448238&type=watch>
> leads to content served as UT
the
input is already UTF-8.
Will try to fix it next time I dig on DEHS' code.
>
> Ben Finney <[EMAIL PROTECTED]> writes:
>
>> Possibly related: The link provided to view the watch file
>>
http://dehs.alioth.debian.org/wwiz_detail.php?id=11448238&type=watch>
>>
Raphael Geissert <[EMAIL PROTECTED]> writes:
> Yeah, that's another known issue. DEHS currently treats all its
> input data as ISO-8859-1 and converts it into UTF-8 without first
> checking if the input is already UTF-8.
Since there's no way to deduce the encoding of a byte stream for
certain, an
> Od: Sebastian Harl
Hi Sebastian,
> On Wed, Aug 05, 2009 at 01:19:15PM +0200, Jarom?r Mike? wrote:
> > I am building package from source downloaded here:
> > https://launchpad.net/invada-studio/+download
> >
> > and this is file I would like to monitor by
Hi there,
I am working on the libproj4 package:
http://dl.maptools.org/dl/libproj4/
How would one write the watch file for it ?
I tried:
$ cat debian/watch
version=3
http://dl.maptools.org/dl/libproj4/ lbp4_(.*)S\.tar\.gz
It gives
$ uscan --verbose --force-download
-- Scanning for
Am Dienstag, den 29.09.2009, 23:27 +0200 schrieb Jérémy Lal:
> This time the web page contains this :
> mypackage.zip - v1.01
>
> I'm stuck with uscan getting what's inside an href.
> Is there a way to get the version number, which is outside the href ?
No. You can of course write your own proces
Daniel Leidert writes:
> Am Dienstag, den 29.09.2009, 23:27 +0200 schrieb Jérémy Lal:
> > This time the web page contains this :
> > mypackage.zip - v1.01
[…]
> […] It is probably better you try to talk to upstream to release
> archives with versions and make mypackage.zip a symlink to the lates
On Thu, Feb 9, 2012 at 2:37 PM, Daniel Martí
wrote:
> Dear Mentors,
>
> I'm having some trouble at creating a watch file for the packace "preload".
>
> The upstream tarballs are found as follows:
> http://sourceforge.net/projects/preload/files/preload/0.6.4/pre
Le Thu, Feb 09, 2012 at 08:37:58PM +0100, Daniel Martí a écrit :
>
> I'm having some trouble at creating a watch file for the packace "preload".
>
> The upstream tarballs are found as follows:
> http://sourceforge.net/projects/preload/files/preload/0.6.4/preload
Hello,
Quoting alberto fuentes (2012-07-17 00:54:32)
> Is it possible to have a generic git watchfile?
The watchfile system is designed to detect new tarballs, it is not
(yet?) capable of detecting $VCS tags. If your upstream forge offers
some way to download tarballs of the said tags, or even bet
Dear Mentors,
I'd like to ask for some advise about my debian/watch file[1].
Problem is that the current watch file is only finding upstreams nightly
builds. The latest release can be found in this[2] remote directory.
Problem is as you see that the tarball does not contain any version s
Hi,
the watch file for the mriconvert package[1] is obviosely not working because
http://lcni.uoregon.edu/~jolinda/MRIConvert/
upstream does not mind numbering its "mriconvert_sources.zip" sources.
However, there should be some chance to drain the current version from other
fil
Hi,
to enable properly downloading the volview sources I tried the following
watch file:
version=3
opts=\
dversionmangle=s/[~\+]dfsg//,\
downloadurlmangle=s/VolView-([\d\.]+)-Linux-x86_64.sh/VolViewSrc.tar.gz/,\
filenamemangle=s/VolView(-[\d\.]+)-Linux-x86_64.sh/VolViewSrc$1.tar.gz/ \
http
On Wed, Feb 13, 2013 at 04:39:11PM +0100, Andreas Tille wrote:
> the watch file of the prospective package meme[1] is reporting a new
> version but fails to download the latest version (4.9.0.4). It was
> working nicely with version 4.9.0.3. I just get:
For the reference:
opts="uv
On Wed, Feb 13, 2013 at 04:39:11PM +0100, Andreas Tille wrote:
> Hi,
>
> the watch file of the prospective package meme[1] is reporting a new
> [1] svn://svn.debian.org/debian-med/trunk/packages/meme/trunk
> version but fails to download the latest version (4.9.0.4). It was
> w
1 - 100 of 406 matches
Mail list logo
