On Thu, Nov 03, 2022 at 10:05:57AM +0100, Petr Vaněk wrote:
> Hi,
>
> I have found improperly indented dosym call in src_install phase in
> luajit ebuilds. Following patch fixes it.
Ping
* John Helmert III schrieb am 10.11.22 um 14:19 Uhr:
> On Thu, Nov 10, 2022 at 02:10:09PM +1000, Marc Schiffbauer wrote:
> > * Sam James schrieb am 10.11.22 um 13:58 Uhr:
> > >
> > > I think we'd rename impact -> description but description would now
> > > be "description of the problem" and not "
On Thu, Nov 10, 2022 at 02:10:09PM +1000, Marc Schiffbauer wrote:
> * Sam James schrieb am 10.11.22 um 13:58 Uhr:
> >
> > I think we'd rename impact -> description but description would now
> > be "description of the problem" and not "description of the package".
>
>
> +1, but additionally havin
On Thu, Nov 10, 2022 at 04:43:01AM +0100, Michał Górny wrote:
> On Wed, 2022-11-09 at 20:27 -0600, John Helmert III wrote:
> > The first GLSA in glsa.git is GLSA-200310-03, the third GLSA of
> > October 2003. It used roughly the same format of the GLSAs we release
> > today, in 2022, making that fo
* Sam James schrieb am 10.11.22 um 13:58 Uhr:
>
> I think we'd rename impact -> description but description would now
> be "description of the problem" and not "description of the package".
+1, but additionally having the short description of the package sounds
still useful to me, as not always
> On 10 Nov 2022, at 03:43, Michał Górny wrote:
>
> On Wed, 2022-11-09 at 20:27 -0600, John Helmert III wrote:
>> The first GLSA in glsa.git is GLSA-200310-03, the third GLSA of
>> October 2003. It used roughly the same format of the GLSAs we release
>> today, in 2022, making that format almost
On Wed, 2022-11-09 at 20:27 -0600, John Helmert III wrote:
> The first GLSA in glsa.git is GLSA-200310-03, the third GLSA of
> October 2003. It used roughly the same format of the GLSAs we release
> today, in 2022, making that format almost as old as me.
>
> Somewhere along the way, it started to
The first GLSA in glsa.git is GLSA-200310-03, the third GLSA of
October 2003. It used roughly the same format of the GLSAs we release
today, in 2022, making that format almost as old as me.
Somewhere along the way, it started to become necessary to target
multiple version ranges within the same pa
Hi Michał!
I like the idea a lot, with this the automatic Ebuild generator tools
like for example Racket-Collector2 and Cargo-Ebuild could use the config
file or could base their license id matching system on such config.
On 11/9/22 17:36, Michał Górny wrote:
Hi, everyone.
TL;DR: I'd like
Hi, everyone.
TL;DR: I'd like to propose adding metadata/spdx-license.conf using
the following format:
=
where is a SPDX-2.0 license identifier, optionally followed
by "+", optionally followed by "WITH" and an exception identifier,
and is the corresponding ebuild-style LICENSE field value.
10 matches
Mail list logo
