Your message dated Sun, 27 Oct 2013 07:57:05 +1030
with message-id <[email protected]>
and subject line Re: Bug#727207: opus: Please add a watch file
has caused the Debian Bug report #727207,
regarding opus: Please add a watch file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
727207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727207
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libopus0
Version: 1.1~beta-3
Severity: normal
Tags: patch
Hi,
please add a watch file. Attached is a patch that adds a watch file only for
stable release. I can provide a watch file that also report alpha and beta
releases if you want.
>From ce89267ad4ad974b0b87947ac8ccd7f9c08ca35e Mon Sep 17 00:00:00 2001
From: Benjamin Drung <[email protected]>
Date: Wed, 23 Oct 2013 14:05:58 +0200
Subject: [PATCH] Add a watch file for stable releases.
---
debian/watch | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 debian/watch
diff --git a/debian/watch b/debian/watch
new file mode 100644
index 0000000..25b1ad6
--- /dev/null
+++ b/debian/watch
@@ -0,0 +1,2 @@
+version=3
+http://www.opus-codec.org/downloads/ (?:|.*/)opus-(\d[\d\.]*)\.tar\.(?:xz|bz2|gz)
--
1.8.3.2
--- End Message ---
--- Begin Message ---
Hi,
On Wed, Oct 23, 2013 at 02:09:57PM +0200, Benjamin Drung wrote:
> Package: libopus0
> Version: 1.1~beta-3
> Severity: normal
> Tags: patch
>
> Hi,
>
> please add a watch file. Attached is a patch that adds a watch file only for
> stable release. I can provide a watch file that also report alpha and beta
> releases if you want.
Thanks for the patch, but a watch file isn't really going to be a lot of
value in this one. We pull releases directly out of git, and sometimes
pull them from between tags, or cherry pick other commits, when there's
a compelling reason to - and I'm in close contact with upstream, so it's
not like releases happen that I'm not aware of.
Cheers,
Ron
--- End Message ---
