Hi Yaroslav,
$ apt showsrc singularity-container | grep Uploaders
Uploaders: Dave Love <f...@gnu.org>, Mehdi Dogguy <me...@debian.org>, Yaroslav
Halchenko <deb...@onerussian.com>, Afif Elghraoui <a...@debian.org>, Dmitry
Smirnov <only...@debian.org>, Benda Xu <o...@debian.org>
shows you as Uploader of singularity-container. Is there any reason you
file this bug report instead of simply uploading a new version of this
package?
When doing so I'd recommend the following patch:
diff --git a/debian/watch b/debian/watch
index 140951c..e4f994d 100644
--- a/debian/watch
+++ b/debian/watch
@@ -6,4 +6,4 @@ repacksuffix=+ds1,\
repack,compression=xz,\
dversionmangle=s{[+~](dfsg|ds)\d*}{},\
" https://github.com/sylabs/singularity/releases \
- (?:.*/)?singularity-(\d[\d\.]*)\.tar\.gz
+ (?:.*/)?singularity-ce-(\d[\d\.]*)\.tar\.gz
I admit I've never used singularity before but this might change in the
near future. Thus I'm wondering why we have 4 open bugs with CVE
numbers and are lagging several versions behind upstream. May be there
is a good reason to stick to the outdated security problematic version
which I simply do not understand?
Kind regards
Andreas.
--
http://fam-tille.de
