On June 28, 2019 5:00:00 AM EDT, Ivo De Decker wrote:
>Hi,
>
>On Thu, Jun 27, 2019 at 09:30:09AM -0400, Afif Elghraoui wrote:
>> On June 27, 2019 9:06:41 AM EDT, Afif Elghraoui
>wrote:
>> >
>> >
>> >On June 27, 2019 5:47:28 AM EDT, Ivo De Decker
>> >wrote:
>> >>Hi,
>> >>>
>> >>> So I think t
Control: reopen -1
On June 27, 2019 9:06:41 AM EDT, Afif Elghraoui wrote:
>
>
>On June 27, 2019 5:47:28 AM EDT, Ivo De Decker
>wrote:
>>Hi,
>>>
>>> So I think the two options we have is (in order of preference): 1.
>>> unblock singularity-container and let the 3.1 based version in to
>>> buster
Control: tag -1 - moreinfo
On June 25, 2019 4:16:17 PM EDT, Salvatore Bonaccorso wrote:
>Hi Paul, hi Afif,
>
[...]
>>
>> Your proposed changes very much do not align with the freeze policy,
>so
>> you're asking for an exception for a new upstream release. This
>package
>> is currently listed to
Hi Paul, hi Afif,
On Sat, Jun 08, 2019 at 09:26:06PM +0200, Paul Gevers wrote:
> Control: tags -1 moreinfo
>
> Hi Afif,
>
> On Wed, 15 May 2019 03:47:28 -0400 Afif Elghraoui wrote:
> > Please unblock package singularity-container/3.1.1+ds-1
> >
> > This package is prone to security vulnerabili
Control: tag -1 - moreinfo
Paul Gevers writes:
> On Wed, 15 May 2019 03:47:28 -0400 Afif Elghraoui wrote:
>> Please unblock package singularity-container/3.1.1+ds-1
>>
>> This package is prone to security vulnerabilities. Upstream provides
>> long-term support for selected versions to their paid
Control: tags -1 moreinfo
Hi Afif,
On Wed, 15 May 2019 03:47:28 -0400 Afif Elghraoui wrote:
> Please unblock package singularity-container/3.1.1+ds-1
>
> This package is prone to security vulnerabilities. Upstream provides
> long-term support for selected versions to their paid users, but also
6 matches
Mail list logo
