On Mon, Jul 17, 2023 at 19:39:30 +0300, Arthur Zamarin wrote:
> On 17/07/2023 16.50, Matt Turner wrote:
> > On Sun, Jul 16, 2023 at 2:04 PM Arthur Zamarin wrote:
> >> Now I'll speak from the point of implementer of `pkgdev bugs`. For me I
> >> think both approaches are good, but I would prefer
On Mon, Jul 17, 2023 at 4:27 PM Sam James wrote:
> > Haven't we been keeping these because we still need to decide on a
> > policy about what to do with dead acct-*/* packages?
>
> Right. https://bugs.gentoo.org/781881 is still open. Flow could ping
> the QA team and ask if it should be closed,
Matt Turner writes:
> On Mon, Jul 17, 2023 at 3:43 PM Florian Schmaus wrote:
>>
>> # Florian Schmaus (2023-07-17)
>> # Obsolete acct-* packages which became leaf packages.
>> # Removal on 2023-08-17.
>> acct-user/artifactory
>> acct-group/artifactory
>> acct-user/cinder
>> acct-group/cinder
On Mon, Jul 17, 2023 at 3:43 PM Florian Schmaus wrote:
>
> # Florian Schmaus (2023-07-17)
> # Obsolete acct-* packages which became leaf packages.
> # Removal on 2023-08-17.
> acct-user/artifactory
> acct-group/artifactory
> acct-user/cinder
> acct-group/cinder
> acct-user/glance
>
# Florian Schmaus (2023-07-17)
# Obsolete acct-* packages which became leaf packages.
# Removal on 2023-08-17.
acct-user/artifactory
acct-group/artifactory
acct-user/cinder
acct-group/cinder
acct-user/glance
acct-group/glance
acct-user/heat
acct-group/heat
acct-user/keystone
acct-group/keystone
On Mon, Jul 17, 2023 at 08:34:45PM +0300, Arthur Zamarin wrote:
> Hmm, I was thinking the opposite (maintaining it in parallel place to
> the package would be harder), but if you say so (and you help maintain
> huge clusters of packages so I believe you) then I think we don't have
> any good
On 17/07/2023 19.37, Sam James wrote:
>
> Big fan of the idea & very much in support of it. This also serves
> to give us logical groupings of packages which are closely related
> and should be bumped together.
>
>> There was some brief discussion on IRC about how to document these
>> groupings,
Matt Turner writes:
> Hello,
>
> Many of us have started using `pkgdev bugs` to file stabilization
> bugs. It works well (Thanks Arthur!) and I encourage everyone to give
> it a try.
>
> Where possible, it files one stabilization bug per package. This makes
> arch testers' jobs easier and makes
On 17/07/2023 16.50, Matt Turner wrote:
> On Sun, Jul 16, 2023 at 2:04 PM Arthur Zamarin wrote:
>> Now I'll speak from the point of implementer of `pkgdev bugs`. For me I
>> think both approaches are good, but I would prefer the latter over the
>> former. Nicer syntax, easy cache of all groups,
On Mon, Jul 17, 2023 at 12:01 PM Ulrich Mueller wrote:
>
> > On Mon, 17 Jul 2023, konsolebox wrote:
>
> >> Maybe the commit message could shortly explain why this is needed,
> >> or what problem is fixed by it?
>
> > It silences the default branch warning.
>
> Add this sentence to the commit
> On Mon, 17 Jul 2023, konsolebox wrote:
>> Maybe the commit message could shortly explain why this is needed,
>> or what problem is fixed by it?
> It silences the default branch warning.
Add this sentence to the commit message then?
> If that's unwanted, kindly just close the issue.
On Mon, Jul 17, 2023, 22:53 Ulrich Mueller, wrote:
> > On Mon, 17 Jul 2023, Matt Turner wrote:
>
> > From: konsolebox
> > Closes: https://bugs.gentoo.org/841392
> > Signed-off-by: Matt Turner
>
> Maybe the commit message could shortly explain why this is needed,
> or what problem is fixed
On Mon, Jul 17, 2023 at 10:56 AM Adrian Schollmeyer wrote:
> Am Montag, dem 17.07.2023 um 10:51 -0400 schrieb Matt Turner:
> > This works similar to cmake.eclass's ${CMAKE_VERBOSE}.
>
> Why not use MESON_VERBOSE as well? Avoids double negation in the code
> (not unset -> verbose vs. MESON_VERBOSE
On Mon, Jul 17, 2023 at 10:51 AM Matt Turner wrote:
>
> From: Jonas Rakebrandt
>
> This works similar to cmake.eclass's ${CMAKE_VERBOSE}.
... except that it's _QUIET, rather than _VERBOSE.
I've sent patches to add NINJA_VERBOSE to ninja-utils.eclass and
another to support CMAKE_VERBOSE with
Signed-off-by: Matt Turner
---
eclass/cmake.eclass | 4
1 file changed, 4 insertions(+)
diff --git a/eclass/cmake.eclass b/eclass/cmake.eclass
index d70f2cbf1fac..16b3e300ccae 100644
--- a/eclass/cmake.eclass
+++ b/eclass/cmake.eclass
@@ -651,6 +651,10 @@ cmake_build() {
ninja operates in one of three modes:
- verbose (with -v): prints build commands
- quiet (with --quiet): prints nothing
- normal: prints [XX/YY]-style build status updates
samurai works the same way, except it does not have a quiet mode.
Thus we can't simply override ninja-utils' hard-coded
Hi,
Am Montag, dem 17.07.2023 um 10:51 -0400 schrieb Matt Turner:
> This works similar to cmake.eclass's ${CMAKE_VERBOSE}.
Why not use MESON_VERBOSE as well? Avoids double negation in the code
(not unset -> verbose vs. MESON_VERBOSE == true -> verbose) and keeps
the variable naming similar to
> On Mon, 17 Jul 2023, Matt Turner wrote:
> From: konsolebox
> Closes: https://bugs.gentoo.org/841392
> Signed-off-by: Matt Turner
Maybe the commit message could shortly explain why this is needed,
or what problem is fixed by it?
signature.asc
Description: PGP signature
From: Jonas Rakebrandt
This works similar to cmake.eclass's ${CMAKE_VERBOSE}.
Closes: https://github.com/gentoo/gentoo/pull/28942
Signed-off-by: Jonas Rakebrandt
Signed-off-by: Matt Turner
---
eclass/meson.eclass | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff
From: konsolebox
Closes: https://bugs.gentoo.org/841392
Signed-off-by: Matt Turner
---
eclass/git-r3.eclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/eclass/git-r3.eclass b/eclass/git-r3.eclass
index e9fdf2ac3a42..5ac141962b12 100644
--- a/eclass/git-r3.eclass
+++
On Sun, Jul 16, 2023 at 2:04 PM Arthur Zamarin wrote:
> Now I'll speak from the point of implementer of `pkgdev bugs`. For me I
> think both approaches are good, but I would prefer the latter over the
> former. Nicer syntax, easy cache of all groups, easier to solve the
> "graph problems" in the
21 matches
Mail list logo
