On Sat, 2021-12-04 at 10:47 +0100, Fabian Groffen wrote:
>
> Now, if you would make a supported claim that all terminals we install
> use a black background by default, your change becomes more valid.
>
>
For one, when you're working through the handbook to install Gentoo,
you're doing it on a
On Tue, 2021-10-05 at 17:13 +0200, Michał Górny wrote:
>
> > 2. What happens to the LTS branch when the next EAPI is released?
> >
>
> I haven't really thought about it. Are you suggesting that we could
> bump 'master' Portage to newer EAPI earlier or...?
>
I just mean that, a priori, the
On Tue, 2021-10-05 at 10:31 +0200, Michał Górny wrote:
> Hi, everyone.
>
> I've been thinking about this for some time already, and the recent
> FILESDIR mess seems to confirm it: I'd like to start a more stable LTS
> branch of Portage.
>
I think this is healthy for most software projects, but
-by: Michael Orlitzky
---
repoman/lib/repoman/modules/linechecks/deprecated/inherit.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/repoman/lib/repoman/modules/linechecks/deprecated/inherit.py
b/repoman/lib/repoman/modules/linechecks/deprecated/inherit.py
index 60410347b..5848a0c37 100644
Le 17/06/2020 à 08:15, Michał Górny a écrit :
On Tue, 2020-06-16 at 23:07 +, Michael Lienhardt wrote:
Dear all,
My bad for not noticing it sooner, but when there is a dependency like
">=sys-fs/udev-208-r1:0/0[static-libs?]" (that occurs in
virtual/libgudev-215-r3),
Le 17/06/2020 à 10:35, Ulrich Mueller a écrit :
On Wed, 17 Jun 2020, Michael Lienhardt wrote:
But maybe, "error" here in the PMS mean "the cpvs without the use flag
does not match that dependency and a warning should be raised to
improve compatibility in the future". In
On 6/17/20 1:25 AM, Zac Medico wrote:
> On 6/16/20 7:47 PM, Michael Lienhardt wrote:
>>
>>
>> On 6/16/20 11:59 PM, Zac Medico wrote:
>>> On 6/16/20 6:38 PM, Michael Lienhardt wrote:
>>>> With the first version of DEPEND, emerge succee
On 6/16/20 11:59 PM, Zac Medico wrote:
> On 6/16/20 6:38 PM, Michael Lienhardt wrote:
>> With the first version of DEPEND, emerge succeed:
>> # emerge -pv app-misc/dummy-master
>>
>> These are the packages that would be merged, in order:
>>
>> Calculat
On 6/16/20 9:31 PM, Zac Medico wrote:
> On 6/16/20 11:07 PM, Michael Lienhardt wrote:
>> I'm sorry, my client didn't allow to send plain text email anymore...
>>
>> So, here is my original email.
>>
>> Dear all,
>>
>> My bad for not noticing i
ild
has EAPI=6).
So it seems to me that this current behavior of emerge should be considered an
error, no? Or the PMS should be updated?
This is related to the tool I'm working on: should my tool allow this behavior,
or fail like it is currently doing (I guess the former)?
Best,
Michael
On 6/
can be put back
into an eclass, and its consumers updated one-at-a-time.
Bug: https://bugs.gentoo.org/489542
Bug: https://bugs.gentoo.org/637824
Signed-off-by: Michael Orlitzky
---
repoman/lib/repoman/modules/linechecks/deprecated/inherit.py | 1 +
1 file changed, 1 insertion(+)
diff --git
On 4/26/20 3:25 PM, Ulrich Mueller wrote:
>>>>>> On Sun, 26 Apr 2020, Michael Orlitzky wrote:
>
>> Fuel for the fire:
>
>> * https://www.nongnu.org/lzip/lzip_benchmark.html
>> * https://www.nongnu.org/lzip/xz_inadequate.html
>
> Yep. That's
On 4/26/20 12:55 PM, Matt Turner wrote:
> Bug: https://bugs.gentoo.org/715108
> Signed-off-by: Matt Turner
> ---
> Strawman patch. Bikeshed away.
>
Fuel for the fire:
* https://www.nongnu.org/lzip/lzip_benchmark.html
* https://www.nongnu.org/lzip/xz_inadequate.html
veloper
to add a "=" sign (simplicity is very important)? Or for another reason?
Many thanks!
Michael
detect all
implementation dependency breakage.
Again, there's something I probably don't see: why was slot operators chosen
(among other possibilities) as a mechanism to trigger recompilation?
I'm very grateful to you all for the time you take to read and answer my
questions.
Best,
Michael
dependency breakage?
You have far more experience than me on this, and it would be nice for me to
know what I'm up against.
Many thanks!
Michael
e on how to achieve
it?
Among these two solutions, I prefer the first one: we stay at the level of
package dependencies (and it looks simpler to implement).
However, it is maybe easier/better to use the second approach, I don't know.
Do you have some suggestions?
Thanks!
Michael
ays checks if it is used by
another package: this means that installed packages' dependencies are never
broken.
Many thanks!
Michael
On 21/02/20 05:29, Matt Turner wrote:
> I found the original code to be nearly incomprehensible. Instead of
> populating a dict of potential binpkgs to remove and then removing from
> the to-be-removed list, just selectively add to-be-removed packages.
>
> Signed-off-by: Matt Turner
> ---
> I
On 06/01/20 06:38, Zac Medico wrote:
> Example output for maven-bin-3.6.2 (bug 704618):
>
> * QA Notice: Unresolved soname dependencies:
> *
> */usr/share/maven-bin-3.6/lib/jansi-native/freebsd32/libjansi.so:
> libc.so.7 libutil.so.9
> *
On 02/01/20 18:57, Matt Turner wrote:
> Signed-off-by: Matt Turner
> ---
> pym/gentoolkit/eclean/cli.py| 4 ++--
> pym/gentoolkit/eclean/search.py | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/pym/gentoolkit/eclean/cli.py b/pym/gentoolkit/eclean/cli.py
> index
On 18/12/19 17:36, Joakim Tjernlund wrote:
> On Wed, 2019-12-18 at 11:22 -0500, Mike Gilbert wrote:
>> CAUTION: This email originated from outside of the organization. Do not
>> click links or open attachments unless you recognize the sender and know the
>> content is safe.
>>
>>
>> On Thu, Dec
On 13/12/19 20:36, Michał Górny wrote [excerpted]:
>
> Is this really an argument for or *against* it? Developers are entirely
> capable of keeping seds that do nothing for years, as well as patches
> that -- while apparently applying correctly -- are entirely meaningless.
I think there is some
On 13/12/19 21:59, Michał Górny wrote:
> On Fri, 2019-12-13 at 21:56 +0000, Michael 'veremitz' Everitt wrote:
>> On 13/12/19 21:42, Michał Górny wrote:
>>> On Fri, 2019-12-13 at 16:37 -0500, Mike Gilbert wrote:
>>>> On Fri, Dec 13, 2019 at 3:36 PM Michał Górny
with, say, -F10 & display big fat 'red' warning
and QA notice
4) Fail and abort
Regards,
veremitz/Michael.
signature.asc
Description: OpenPGP digital signature
On 12/13/19 9:28 AM, Fabian Groffen wrote:
>
> We are providing those patches, maybe. In reality very often the
> patches originate from somewhere else though. And you don't want to
> have to respin all of those just because. At least that's what I feel.
>
Just because... the context
On 12/12/19 3:15 PM, Ulrich Mueller wrote:
>
> It was also suggested that we add -F0 in EAPI 8, but that would break
> the build in those cases that are producing extra output now. I don't
> think that would be preferable.
It would only break the build for the maintainer, who would then
On 11/27/19 2:17 PM, Michał Górny wrote:
>
> To achieve that, attempt to apply each patch with -F0 --dry-run first.
> If this succeeds, just silently apply the patch for real. If it
> doesn't, output an explicit eqawarn that the patch does not apply
> cleanly and retry with the default fuzz
On 13/11/19 19:07, Zac Medico wrote:
> On 11/8/19 9:09 AM, Joakim Tjernlund wrote:
>> On Fri, 2019-11-08 at 01:57 +0100, Joakim Tjernlund wrote:
>>> I am looking for a way to seed emerge with an older pkg db so emerge can
>>> calculate
>>> which packages needs to be rebuild/upgraded in order to
On 03/11/19 21:37, Michał Górny wrote:
> On Sun, 2019-11-03 at 15:26 -0600, William Hubbs wrote:
>>
>> You being a qa member doesn't have a lot to do with this mgorny. you
>> know there was no official policy when I posted this, and as far as I
>> know there is not one now.
>>
> That is a really
On 10/10/19 03:57, Kent Fredric wrote:
> On Wed, 9 Oct 2019 19:45:34 -0700
> Zac Medico wrote:
>
>> I'd prefer to disable --autounmask by default and include warnings about
>> harmful behavior in the documentation.
> I think autounmasks behaviour with regards to USE flags is useful,
> (heh), its
On 8/30/19 10:34 AM, michael.lienha...@laposte.net wrote:
>
> All comments/suggestions are welcomed.
>
Since no one else has said it yet (?), I think this approach is really
cool and I'm glad someone is working on it.
Modeling difficult computations as abstract optimization problems is a
the rest
- start reading portage's bug tracker and continue reading its code
- extend pdepa with other kind of relevant analysis
All comments/suggestions are welcomed.
Best,
Michael
On 7/25/19 4:29 PM, Michał Górny wrote:
>>
>> * In the md5-cache entry, maybe use a common prefix like EXT_ for the
>> extra keys in order to distinguish them from normal keys.
>
> Yeah, I was thinking of something like '__ext_foo', or '__ext[foo]'.
>
What are the pros/cons of this? The names
version REQUIRED_USE="^^ ( consolekit, elogind systemd )"
In practice however, this was not a problem, as some dependencies of polkit
deep in the tree did require one of ( systemd consolekit ) to be set.
If you want, I can implement a test that check if this optimization is a
problem in practice.
Checking the issue shouldn't be too difficult (I think I just need to check
that all REQUIRED_USE and *DEPEND are equivalent for a SLOT).
Best,
Michael
such that
the latest corresponding cpv could be installed, while the previous version
could be).
Is it really the default behavior of emerge, and if yes, is there a way to make
emerge consider all matching cpv for an atom?
Thank you!
Michael
On 09/17/2018 02:52 AM, Michał Górny wrote:
>
> --- a/bin/ebuild-helpers/fowners
> +++ b/bin/ebuild-helpers/fowners
> ...
> + eqawarn "This is unsupported. Please use 'chmod' when you need
> to work on files"
This one should be 'chown' instead of 'chmod'.
(Calling chown on the live
On 09/04/2018 01:53 PM, Michał Górny wrote:
> + # TODO: do we need it? gconf installs empty dir there but that's
> + # all
> + root
FWIW, we should not allow this.
On 08/07/2018 01:34 PM, Zac Medico wrote:
>
> Why not use ${ED%/} instead of ${D%/} here, so that the output is the
> same regardless of ${EPREFIX}?
>
We want to show where the executable was actually installed, and
generally that includes EPREFIX. For example, I'd want to see
System executables that are writable by a non-root user pose a
security risk. Anyone who can write to an executable can change its
behavior. If that executable is later run with elevated privileges
(say, by root, when the machine starts), then the non-root user can
escalate his own privileges to
System executables that are not owned by root pose a security
risk. The owner of the executable is free to modify it at any time;
so, for example, he can change a daemon's behavior to make it
malicious before the next time the service is started (usually by
root).
On a "normal" system, the
Changes in v3:
* Undo the setguid exception from v2, and add a comment explaining why.
* Add line breaks for readability in two comments.
* Try to put back the leading "/" in the output list.
* Remove a superfluous comment mentioning the "prefix."
Michael Orlitzky (
On 07/29/2018 09:16 PM, Ulrich Mueller wrote:
>
> Staying with the man:man example, how would anybody become the "man"
> user, in the first place? That user has /bin/false as a shell and no
> valid password.
One way would be to exploit a process that's running as the "man" user.
Ostensibly such
.
Michael Orlitzky (2):
bin/install-qa-check.d: add new 90bad-bin-owner QA check.
bin/install-qa-check.d: add new 90bad-bin-group-write QA check.
bin/install-qa-check.d/90bad-bin-group-write | 49
bin/install-qa-check.d/90bad-bin-owner | 47
System executables that are not owned by root pose a security
risk. The owner of the executable is free to modify it at any time;
so, for example, he can change a daemon's behavior to make it
malicious before the next time the service is started (usually by
root).
On a "normal" system, there is
System executables that are writable by a non-root user pose a
security risk. Anyone who can write to an executable can change its
behavior. If that executable is later run with elevated privileges
(say, by root, when the machine starts), then the non-root user can
escalate his own privileges to
On 07/29/2018 03:43 PM, Ulrich Mueller wrote:
>
>> On a "normal" system, there is no good reason why the superuser should
>> not own every system executable. This commit adds a new install-time
>> check that reports any such binaries with a QA warning. To avoid false
>> positives, non-"normal"
On 07/29/2018 03:43 PM, Ulrich Mueller wrote:
>
> Shouldn't this check for setuid binaries like /usr/bin/mandb (which is
> owned by man:man)? I think these are legitimate usage case.
>
In general, yeah. I think we should be skeptical of setuid/gid
executables, but this isn't the right place to
System executables that are writable by a non-root user pose a
security risk. Anyone who can write to an executable can change its
behavior. If that executable is later run with elevated privileges
(say, by root, when the machine starts), then the non-root user can
escalate his own privileges to
Discussed and implemented in,
https://bugs.gentoo.org/629398
Michael Orlitzky (2):
bin/install-qa-check.d: add new 90bad-bin-owner QA check.
bin/install-qa-check.d: add new 90bad-bin-group-write QA check.
bin/install-qa-check.d/90bad-bin-group-write | 40
bin
System executables that are not owned by root pose a security
risk. The owner of the executable is free to modify it at any time;
so, for example, he can change a daemon's behavior to make it
malicious before the next time the service is started (usually by
root).
On a "normal" system, there is
Many thanks.
I should definitively read this document, that is far more precise that
anything I have found on the wiki or on devmanual.
Il 06/02/2018 00:05, Zac Medico ha scritto:
On 02/05/2018 02:46 PM, Michael Lienhardt wrote:
Is the IUSE_IMPLICIT variable in the make.defaults also changed
Is the IUSE_IMPLICIT variable in the make.defaults also changed into
IUSE_EFFECTIVE?
I'm sorry if this question was already discussed/answered somewhere else.
Michael
Il 04/02/2018 14:40, Michał Górny ha scritto:
Rename the iuse_implicit variable used in USE_EXPAND handling to
iuse_effective
On 01/30/2018 02:23 AM, Michał Górny wrote:
> Warn about empty directories installed to /var
Why only warn about /var, considering that FEATURES=strict-keepdir will
delete the others? People will probably assume that if their package
throws no warnings, it's strict-keepdir-safe.
On 01/25/2018 10:11 AM, Michał Górny wrote:
> W dniu czw, 25.01.2018 o godzinie 10∶07 +0100, użytkownik Michael
> Haubenwallner napisał:
>> Hi,
>>
>> ${Subject} ringing a bell here:
>>
>> dev-db/oracle-instantclient is fetch restricted. As a binary package
Since ::gentoo is the only repository governed by the PMS, can't we make
repoman do this? The problem with requiring "repoman --force" for an
in-place dependency change is that repoman generally won't have access
to the unedited ebuild; but for ::gentoo, we can probably hack something
together in
Hi,
${Subject} ringing a bell here:
dev-db/oracle-instantclient is fetch restricted. As a binary package with
multiple USE options there's a bunch of files to download - even for
multiple archs when multilib is active.
So in pkg_nofetch() I'm telling the user whether a file to download is
---
man/ebuild.5 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/man/ebuild.5 b/man/ebuild.5
index 42a0599fe..28e9582d1 100644
--- a/man/ebuild.5
+++ b/man/ebuild.5
@@ -1271,7 +1271,8 @@ Creates directories inside of ${ED}.
.br
.BR 'dodir\ /usr/lib/apache'
creates
by "is (non)empty."
Michael Orlitzky (2):
man/ebuild.5: document that dodir is for nonempty directories.
man/ebuild.5: document the rationale for using keepdir over dodir.
man/ebuild.5 | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
--
2.13.6
---
man/ebuild.5 | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/man/ebuild.5 b/man/ebuild.5
index 28e9582d1..8784a14ee 100644
--- a/man/ebuild.5
+++ b/man/ebuild.5
@@ -1285,8 +1285,9 @@ Sets the root (\fIDESTTREE\fR) for other functions like
\fBdobin\fR,
The default
The main barrier to proper keepdir usage is that nobody knows what
it's for. These two commits update the ebuild (5) man page with an
explanation, namely that empty directories are undefined by the PMS.
Michael Orlitzky (2):
man/ebuild.5: document that dodir is for nonempty directories.
man
---
man/ebuild.5 | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/man/ebuild.5 b/man/ebuild.5
index 9dd969b03..5e2fdbcf5 100644
--- a/man/ebuild.5
+++ b/man/ebuild.5
@@ -1285,8 +1285,9 @@ Sets the root (\fIDESTTREE\fR) for other functions like
\fBdobin\fR,
The default
---
man/ebuild.5 | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/man/ebuild.5 b/man/ebuild.5
index 42a0599fe..9dd969b03 100644
--- a/man/ebuild.5
+++ b/man/ebuild.5
@@ -1267,11 +1267,12 @@ that this expression does \fBNOT\fR use the offset
prefix.
runs sed on
On 01/10/2018 03:55 PM, Zac Medico wrote:
>>
>> This is going to break a lot of packages whose build systems create e.g.
>> /var/lib/foo and do nothing with it immediately. The ebuild should be
>> calling keepdir on those paths, but how would anyone know that?
>
> If we consider that portage
On 01/10/2018 03:13 PM, Michał Górny wrote:
> Remove empty directories in install-qa-check phase in order to prevent
> Portage from installing them, and therefore from developers relying
> on them being installed.
This is going to break a lot of packages whose build systems create e.g.
Dear Alexander,
Many thanks for the advices.
I started few discussions on the forum and will go to FOSDEM.
I'll see where it will go.
Best,
Michael
Il 16/12/2017 14:39, Alexander Berntsen ha scritto:
On 13/12/17 02:52, michael.lienha...@laposte.net wrote:
But maybe there are things we can do
repository, you could directly ask me
Does anyone have suggestions on that topic?
Again, many thanks.
I really hope that with everyone's feedback, suggestions, and help, we could
make something useful from this prototype.
Michael Lienhardt
PS: I forgot in my previous mail to talk about the other
or missed.
Best Regards,
Michael Lienhardt
PS: list of uninstallable packages:
dev-java/jruby-1.7.12
media-video/nvidia-settings-340.58
dev-ruby/bitescript-0.0.9
dev-java/spring-core-3.2.4
app-i18n/ibus-table-code-1.2.0.20100305
dev-ruby/weakling-0.0.4
sci-libs/ogdi-3.1.5-r1
dev-java/jcs-2.0
On 03/05/2017 02:12 PM, Zac Medico wrote:
>
> Incorrect.
>
> ...
>
> Incorrect.
>
I see my mistakes, but maintain that this is confusing =)
>
> The --with-bdeps-auto option results in desirable behavior by default,
> and it's also backward compatible with existing --with-bdeps and
>
On 03/05/2017 03:40 AM, Zac Medico wrote:
>
> A new --with-bdeps-auto= option is provided, making it possible to
> enable or disable the program logic that causes --with-bdeps to be
> automatically enabled. Use --with-bdeps-auto=n to prevent --with-bdeps
> from being automatically enabled
On 02/01/2017 04:03 PM, Michał Górny wrote:
>> SLOT="0"
>> -IUSE="build doc epydoc +ipc linguas_ru selinux xattr"
>> +IUSE="build doc epydoc +ipc linguas_ru native-extensions selinux
>> xattr"
>
> Wouldn't it be better to enable it by default?
>
Please don't enshrine personal preferences into
On 05/11/2016 12:33 PM, Brian Dolbec wrote:
>
> I'll work on adding this check to repoman after I finish getting some
> in progress changes done so the new repoman code can be released.
>
I took a look at the new code and it was really easy to get something
working. I added a new QA category,
that are not so easy to fix will stand out once the trivial ones
are. Perhaps in EAPI-$next, the warning can become an error.
Michael Orlitzky (1):
Add a test case for PMS-compliant usage of the ROOT variable.
ebuild-test/root-var-usage/metadata.xml| 24 ++
ebuild-test/root-var
On a fresh amd64 stage3 a user is presented with fourteen news items to
read, and three[1][2][3] of these are directly related to Portage.
In order to improve the out-of-box experience, please review them for
relevance and consider removing or restricting any that are not.
1:
This documents shell globs in INSTALL_MASK and warns about filenames
containing spaces. I also added a few more comments to the code after
I figured out what it was going.
Michael Orlitzky (2):
bin/misc-functions.sh: Elaborate on some comments in install_mask().
man/make.conf.5: Document
---
bin/misc-functions.sh | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/bin/misc-functions.sh b/bin/misc-functions.sh
index 9b79351..c2ff70a 100755
--- a/bin/misc-functions.sh
+++ b/bin/misc-functions.sh
@@ -261,20 +261,30 @@ install_mask() {
shift
X-Gentoo-Bug: 554084
X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=554084
---
bin/phase-helpers.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/bin/phase-helpers.sh b/bin/phase-helpers.sh
index efd2cfa..b446060 100644
--- a/bin/phase-helpers.sh
+++
X-Gentoo-Bug: 554084
X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=554084
---
bin/phase-helpers.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/bin/phase-helpers.sh b/bin/phase-helpers.sh
index efd2cfa..bf3ae1f 100644
--- a/bin/phase-helpers.sh
+++
On 04/26/2015 11:14 PM, Zac Medico wrote:
This requires the EBUILD_FORCE_TEST code from dyn_test to execute
before USE is declared readonly.
X-Gentoo-Bug: 325009
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=325009
---
--- a/bin/ebuild.sh
+++ b/bin/ebuild.sh
@@ -1,5 +1,5 @@
On 04/21/2015 01:28 PM, Zac Medico wrote:
The docs for INSTALL_MASK (man 5 make.conf) don't mention that globs
will work. It's expecting a space delimited list of file names. Does
it really take a space-delimited list of globs instead? If so, how does
that reconcile with the fact that * could
On 04/21/2015 05:48 AM, Duncan wrote:
Well, I don't use INSTALL_MASK myself, so I don't have a real-world
use-case for you. However, it's clear that the code will expand shell
globs, so I preserved that behavior for compatibility.
I do, with shell globs, tho I didn't bother checking the
On 12/17/2014 05:32 PM, Brian Dolbec wrote:
Only code changes I see to portage, pkgcore (I know nothing about
paludis) are to look for the glsa's in the 2 possible locations. The
standalone glsa repo, failing that, backup to the gentoo tree.
Could we ship a GLSA overlay enabled by
Fixes: 6dafdc288976 (Remove __eqalog __eqawarnlog)
---
bin/install-qa-check.d/90world-writable | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/bin/install-qa-check.d/90world-writable
b/bin/install-qa-check.d/90world-writable
index 2b435ac..1fb2a8f 100644
---
On 27/10/14 07:05, Zac Medico wrote:
On 10/26/2014 12:31 PM, Michael Palimaka wrote:
On 26/10/14 07:57, Zac Medico wrote:
On 10/25/2014 01:32 PM, Zac Medico wrote:
On 10/25/2014 01:26 PM, Michał Górny wrote:
Dnia 2014-10-25, o godz. 12:53:15
Zac Medico zmed...@gentoo.org napisał
Present the list of offending files newline-delimitered for consistency
with other checks.
---
bin/install-qa-check.d/05double-D | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/bin/install-qa-check.d/05double-D
b/bin/install-qa-check.d/05double-D
index 1634afd..7d958f1
Use eqawarn instead of __vecho for visibility.
Present the list of offending files newline-delimitered for consistency
with other checks.
---
bin/install-qa-check.d/90world-writable | 28 +---
1 file changed, 21 insertions(+), 7 deletions(-)
diff --git
On 26/10/14 07:57, Zac Medico wrote:
On 10/25/2014 01:32 PM, Zac Medico wrote:
On 10/25/2014 01:26 PM, Michał Górny wrote:
Dnia 2014-10-25, o godz. 12:53:15
Zac Medico zmed...@gentoo.org napisał(a):
On 10/25/2014 09:15 AM, Michael Palimaka wrote:
+eqalog() {
+ local tag=$1 x
+ shift
Present the list of offending files newline-delimitered for consistency
with other checks.
---
bin/install-qa-check.d/05double-D | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/bin/install-qa-check.d/05double-D
b/bin/install-qa-check.d/05double-D
index 1634afd..84fcc89
These functions are to be used for creating a log of QA violations in a
machine-readable format.
Stored in ${T]/qa.log, the log consists of one entry per line in the
following format: violation-tag data
For example:
deprecated-directory /usr/man
deprecated-directory /usr/info
world-writable
Use eqawarn instead of __vecho for visibility.
Present the list of offending files newline-delimitered for consistency
with other checks.
---
bin/install-qa-check.d/90world-writable | 28 +---
1 file changed, 21 insertions(+), 7 deletions(-)
diff --git
On 26/10/14 07:00, Zac Medico wrote:
On 10/25/2014 12:54 PM, Zac Medico wrote:
On 10/25/2014 12:53 PM, Zac Medico wrote:
On 10/25/2014 09:15 AM, Michael Palimaka wrote:
+eqalog() {
+ local tag=$1 x
+ shift
+ for x in $@ ; do
+ echo ${tag} ${x} ${T}/qa.log
+ done
On 07/08/2014 07:11 PM, Sebastian Luther wrote:
Am 08.07.2014 18:58, schrieb Michael Haubenwallner:
Hello fellow Portage developers,
attached portage patch draft aims to allow for easy distributing eclasses to
be tested by
multiple tinderboxes on various architectures, without being active
and for the eclass: to live in tree-or-overlay/eclass/testing/
Thoughts? (even for var-naming, manpage yes/no/wording, ...)
Thank you!
/haubi/
From 2ddc1db0f1c15873e2476fbf5ba0352464c8725a Mon Sep 17 00:00:00 2001
From: Michael Haubenwallner ha...@gentoo.org
Date: Tue, 8 Jul 2014 17:48:54 +0200
Subject
Am 2014-07-08 19:11, schrieb Sebastian Luther:
Am 08.07.2014 18:58, schrieb Michael Haubenwallner:
Hello fellow Portage developers,
attached portage patch draft aims to allow for easy distributing eclasses to
be tested by
multiple tinderboxes on various architectures, without being active
---
pym/repoman/checks.py | 10 --
1 file changed, 10 deletions(-)
diff --git a/pym/repoman/checks.py b/pym/repoman/checks.py
index 8032b28..abb9545 100644
--- a/pym/repoman/checks.py
+++ b/pym/repoman/checks.py
@@ -385,19 +385,9 @@ class InheritDeprecated(LineCheck):
I WTF'ed on this for a long time before I noticed that the docs for
has were sort-of contained in hasv. Might as well give has its own.
From 423123cc2ea429c06914ef858a6fdb86c0c6d30b Mon Sep 17 00:00:00 2001
From: Michael Orlitzky m...@gentoo.org
Date: Wed, 22 Jan 2014 16:18:23 -0500
Subject
On 05/11/2012 06:39 PM, Mike Frysinger wrote:
+multijob_child_init() {
+ trap 'echo ${BASHPID} $? '${mj_control_fd} EXIT
+ trap 'exit 1' INT TERM
+}
Just wondering why $! in parent isn't used anywhere, even not for some
integrity check if the child's BASHPID actually was forked by
out?
Thank you!
/haubi/
--
Michael Haubenwallner
Gentoo on a different level
ebuild.sh: WORKDIR: ${WORKDIR} 2
@@
Any idea?
Thank you!
/haubi/
--
Michael Haubenwallner
Gentoo on a different level
WARNING: One or more repositories have missing repo_name entries:
/big5tk/local/prefix-overlay/profiles/repo_name
/big5tk/local/gentoo-x86/profiles/repo_name
NOTE
enable/disable information from make.conf, however the
other keys, such as those representing the env or package.use do not.
How can I get this information?
Thanks,
Michael
1 - 100 of 115 matches
Mail list logo