Hi,
Am Thu, Jan 27, 2022 at 11:52:26PM +0800 schrieb Shengjing Zhu:
> On Thu, Jan 27, 2022 at 8:53 PM Nilesh Patra wrote:
> > c) Port code to the version 7 of this package (which you uploaded)
>
> The port is rather straightforward. I just send the patch to upstream,
> please see
Hi
On Thu, Jan 27, 2022 at 8:53 PM Nilesh Patra wrote:
> c) Port code to the version 7 of this package (which you uploaded)
The port is rather straightforward. I just send the patch to upstream,
please see https://github.com/apptainer/apptainer/pull/182
Andreas, are you aware that singularity
Hi Nilesh,
Am Thu, Jan 27, 2022 at 06:23:08PM +0530 schrieb Nilesh Patra:
> > is not the case for the latest
> > version of golang-github-vbauerster-mpb-dev:> [...]
> > -o ./singularity
> > /build/singularity-container-3.9.4+ds1/_build/src/github.com/sylabs/singularity/cmd/singularity
>
Hi Andreas,
On 1/27/22 3:36 PM, Andreas Tille wrote:
Hi,
[...] While upgrading
golang-github-blang-semver-dev helped to get rid of some error
message inside the build log this
Great
is not the case for the latest
version of golang-github-vbauerster-mpb-dev:> [...]
-o ./singularity
Control: tags -1 help
Hi,
I pushed several changes to singularity-container Git[1] (including
changing debian/.gitlab-ci.yaml to get build logs I can link to). I
also upgraded two golang packages (golang-github-blang-semver-dev and
golang-github-vbauerster-mpb-dev) to the versions that are
Am Tue, Jan 25, 2022 at 11:24:13AM -0500 schrieb Yaroslav Halchenko:
>
> > To what branch?
>
> oh, I didn't spot that `gbp push` doesn't push not yet tagged work?
Uhhhmmm, no, its pushing at my side. Do you have some specific config
which might prevent this?
> pushed now:
>
>
> I can't see this in master branch.
> > I have started to update packaging for 3.9.4+ds1 but got stuck on
> > updating the 2nd patch which seems "too involved" for a go-ignorant me.
> > Any help would be welcomed. I have pushed update of source tree etc
> To what branch?
oh, I didn't spot
Hi Yaroslav,
Am Mon, Jan 24, 2022 at 10:11:21AM -0500 schrieb Yaroslav Halchenko:
>
> > " https://github.com/sylabs/singularity/releases \
> > - (?:.*/)?singularity-(\d[\d\.]*)\.tar\.gz
> > + (?:.*/)?singularity-ce-(\d[\d\.]*)\.tar\.gz
>
> cool -- applied
I can't see this in master branch.
Hi, Andreas!
On 1/24/22 07:24, Andreas Tille wrote:
I might have a look once I get permissions to push directly.
Access granted. I don't get email notifications when someone makes an
access request, so I rely on someone emailing the list saying "hey, I
want to join"
thanks and regards
On Mon, 24 Jan 2022, Andreas Tille wrote:
> $ apt showsrc singularity-container | grep Uploaders
> Uploaders: Dave Love , Mehdi Dogguy ,
> Yaroslav Halchenko , Afif Elghraoui ,
> Dmitry Smirnov , Benda Xu
> shows you as Uploader of singularity-container. Is there any reason you
> file this
Hi Yaroslav,
Am Mon, Jan 24, 2022 at 10:11:21AM -0500 schrieb Yaroslav Halchenko:
>
> > " https://github.com/sylabs/singularity/releases \
> > - (?:.*/)?singularity-(\d[\d\.]*)\.tar\.gz
> > + (?:.*/)?singularity-ce-(\d[\d\.]*)\.tar\.gz
>
> cool -- applied
:-)
> > Thus I'm wondering why we
Hi Yaroslav,
$ apt showsrc singularity-container | grep Uploaders
Uploaders: Dave Love , Mehdi Dogguy , Yaroslav
Halchenko , Afif Elghraoui , Dmitry
Smirnov , Benda Xu
shows you as Uploader of singularity-container. Is there any reason you
file this bug report instead of simply uploading a
Package: singularity-container
Version: 3.5.2+ds1-1
Severity: normal
Current upstream release is 3.8.3
https://github.com/sylabs/singularity/releases/tag/v3.8.3
I expect it having addressed a number (if not all) CVE issues we have opened in
debian against the package.
For thta reason marking
13 matches
Mail list logo
