On Thu, Nov 10, 2022 at 09:49:27PM +0100, Jonas Stein wrote:
> On 10/11/2022 03:27, 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
On Thu, Nov 10, 2022 at 10:55:03PM +0200, Mart Raudsepp wrote:
> Ühel kenal päeval, N, 10.11.2022 kell 22:07, kirjutas Jaco Kroon:
> > > Like glsa-check?
> > We currently use that, but it really just says which GLSAs are
> > applicable to the system, it doesn't tell me net-misc/asterisk-
> > 16.0.
Ühel kenal päeval, N, 10.11.2022 kell 22:07, kirjutas Jaco Kroon:
> > Like glsa-check?
> We currently use that, but it really just says which GLSAs are
> applicable to the system, it doesn't tell me net-misc/asterisk-
> 16.0.1:16
> - we've got ways of working from the glsa-check output to that.
On 10/11/2022 03:27, 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.
IFF we change the format, we should not invent a new standar
Hi,
On 2022/11/10 16:24, John Helmert III wrote:
On Thu, Nov 10, 2022 at 10:43:55AM +0200, Jaco Kroon wrote:
Hi,
On 2022/11/10 06:13, John Helmert III wrote:
- Drop synopsis and description fields. These fields contain the same
information and will be superceded by the existing impact
On Thu, Nov 10, 2022 at 10:43:55AM +0200, Jaco Kroon wrote:
> Hi,
>
> On 2022/11/10 06:13, John Helmert III wrote:
> >>> - Drop synopsis and description fields. These fields contain the same
> >>> information and will be superceded by the existing impact field.
> >> Well, I'm not saying "no"
On 10/11/2022 12:38, Anna wrote:
On 2022-11-10 12:29, Andrew Ammerlaan wrote:
diff --git a/eclass/docs.eclass b/eclass/docs.eclass
index 611485c227f..f7a82939a53 100644
--- a/eclass/docs.eclass
+++ b/eclass/docs.eclass
@@ -207,16 +207,15 @@ sphinx_deps() {
}
# @FUNCTION: sphinx_compile
-#
On 2022-11-10 12:29, Andrew Ammerlaan wrote:
> diff --git a/eclass/docs.eclass b/eclass/docs.eclass
> index 611485c227f..f7a82939a53 100644
> --- a/eclass/docs.eclass
> +++ b/eclass/docs.eclass
> @@ -207,16 +207,15 @@ sphinx_deps() {
> }
>
> # @FUNCTION: sphinx_compile
> -# @INTERNAL
> # @DE
diff --git
a/dev-python/mkdocs-git-revision-date-localized-plugin/mkdocs-git-revision-date-localized-plugin-1.1.0.ebuild
b/dev-python/mkdocs-git-revision-date-localized-plugin/mkdocs-git-revision-date-localized-plugin-1.1.0.ebuild
index 38f0810143e..9c5d2c4bf0c 100644
---
a/dev-python/mkdocs-gi
diff --git a/eclass/docs.eclass b/eclass/docs.eclass
index 611485c227f..f7a82939a53 100644
--- a/eclass/docs.eclass
+++ b/eclass/docs.eclass
@@ -207,16 +207,15 @@ sphinx_deps() {
}
# @FUNCTION: sphinx_compile
-# @INTERNAL
# @DESCRIPTION:
# Calls sphinx to build docs.
-#
-# If you overwrite py
Hi all,
This first patch allows for using multiple documentation builders in one
ebuild. This is a use case I initially hadn't considered, but has now
already shown up twice (in the form of doxygen + python? ( sphinx )).
Simply moving where we define default values of some variables is enough
Hi Sam,
On 2022/11/10 12:19, Sam James wrote:
One could thus also link GLSA issues to specific USE flags, taking asterisk again, let's say the problem is with
the http web server having a buffer overflow in the http basic authenticator, then if that embedded server isn't
even compiled in, how
> On 10 Nov 2022, at 08:43, Jaco Kroon wrote:
>
> Hi,
>
> On 2022/11/10 06:13, John Helmert III wrote:
- Drop synopsis and description fields. These fields contain the same
information and will be superceded by the existing impact field.
>>> Well, I'm not saying "no" but it feels
Hi,
On 2022/11/10 11:40, Matthew Smith wrote:
Hi,
On 10/11/2022 08:43, Jaco Kroon wrote:
A mechanism to QUERY which installed packages are affected by known
GLSA's would also be tremendously helpful.
You can use glsa-check for this, which comes with portage:
https://wiki.gentoo.org/wiki/Po
Hi,
On 10/11/2022 08:43, Jaco Kroon wrote:
A mechanism to QUERY which installed packages are affected by known
GLSA's would also be tremendously helpful.
You can use glsa-check for this, which comes with portage:
https://wiki.gentoo.org/wiki/Portage#glsa-check
Thanks,
Matthew
Hi,
On 2022/11/10 06:13, John Helmert III wrote:
- Drop synopsis and description fields. These fields contain the same
information and will be superceded by the existing impact field.
Well, I'm not saying "no" but it feels a bit weird reading a GLSA that
doesn't say a word what the proble
16 matches
Mail list logo
