On 08.01.2020 22:16, Mikle Kolyada wrote:
> These are up for grabs due to the crypto@ project being disbanded.
Going over the list once more, I'll also take
> app-crypt/nasty
> dev-libs/npth
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
On 08.01.2020 22:16, Mikle Kolyada wrote:
> These are up for grabs due to the crypto@ project being disbanded.
>
> app-eselect/eselect-pinentry
I'll take this as well.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109
n them with me.
I can join on
>> app-crypt/gpgme
>> dev-libs/libassuan
>> dev-libs/libgpg-error
>> dev-libs/libksba
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
emerge --unmerge consolekit
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
al packages.
>
> [1] https://docs.syncthing.net/advanced/folder-uselargeblocks.html
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 4/30/19 7:32 PM, Matthew Thode wrote:
> One thing that may help is to have multiple levels of control defined.
Indeed, this distinction is interesting.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED F
y a reasonable person, which the author of the article doesn't
sound like, but the article doesn't provide sufficient information for
third parties to judge per se.
I guess a more interesting question is why communication is increasingly
fragmented across multiple chat systems; it reminds me of
entoo and causing a
negative reputation as in the article in this thread. One some level
that actually goes to trademark infringement that should be of interest
to the foundation, but the issue is broader than that.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
team runs it', '8 Gentoo developers have admin
> rights', 'i.e. it is sanctioned by the project itself'. I was suggested
> that if it's not official, we should close it instead.
If that is how it is perceived I'd be in favor of outright closing it at
it is
controlled by Gentoo. But this is where you get into semantic discussions.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 4/30/19 6:04 PM, Kristian Fiskerstrand wrote:
> On 4/30/19 9:05 AM, Cynede wrote:
>> Right, alike reddit, twitter, facebook and other PR channels. It's
>> "official" because it's controlled by PR Gentoo team,
>
> No, that does not make anything officia
g, but its not an official communication channel
for Gentoo.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
not FTP+expect.
default-key is exactly for config file, for other operations you use
-u/--local-user
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
and
certainly something expected not to happen from a Gentoo Dev to begin
with (for primary key material at least)
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
interactive mode?
Quite frankly I'd expect a Gentoo Developer to be able to manage the gpg
interface.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
stinct signing
subkey, this is one of the expected results of it to begin with.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
the catalyst seed chroots I am building/updating.
Its just a a quick way to propagate this wrapper on multiple computers;
# cat /usr/local/bin/emerge_time.sh
#!/bin/bash
if [[ $# < 1 ]]; then
echo "Usage: ${0} ";
exit;
fi
qlop -tHvg "$1"
--
Kristian Fi
6 seconds
util-linux-2.32-r4: Sun Jul 15 15:51:21 2018: 50 seconds
util-linux-2.33-r1: Sun Jan 6 20:53:29 2019: 46 seconds
util-linux-2.33-r1: Thu Feb 21 22:16:25 2019: 53 seconds
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 51
On 11/27/18 9:07 PM, William Hubbs wrote:
> All,
> I just picked a random msg to reply to on the thread.
>
> Here is the updated AUTHORS file I would like to commit.
>
> William
Lets put it on agenda for next council meeting and let the discussion go
until then.
--
Kri
en reported. There is a difference
here, and on some level that is up to maintainer privilege to evaluate
the difference.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 9/10/18 11:31 PM, Rich Freeman wrote:
> For more critical packages (like the example of zfs) whether it
> compiles and installs isn't 1/10th as important as whether it eats my
> data...
exactly
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
On 9/10/18 11:21 PM, Kristian Fiskerstrand wrote:
> On 9/10/18 11:19 PM, Chí-Thanh Christopher Nguyễn wrote:
>> It is indeed an insurmountable task to write code that is warning-free
>> from the beginning across architectures, compiler versions, etc. But
>> that is not t
rries for build system (autotools re-generation that
might make it unsupported upstream etc) ?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 9/10/18 11:04 PM, Kristian Fiskerstrand wrote:
> On 9/10/18 11:01 PM, Mike Gilbert wrote:
>
>> It's quite a bit harder for a user to remove -Werror from the build
>> system, assuming they can even interpret the error output.
>>
>
> Sure, but at some poin
That it wasn't caught before being stabilized on several arches was
indeed bad, but that likely says more about our stabilization procedures
than the quality of the underlying package's upstream choices.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
On 9/10/18 10:56 PM, Kristian Fiskerstrand wrote:
> On 9/10/18 10:51 PM, Matt Turner wrote:
>> Consider again the bug that started this. The maintainer had not built
>> this configuration. None of the arch teams had built this
>> configuration until I did for the last archite
thing installed on the system, if not for
> Werror preventing the code from building.
one way to look at it though, is that it is a valuable upstream
contribution that this configuration produces the error, so Gentoo is
contributing to upstream development because of it.
--
Kristian Fisk
nd RESTRICT="!test? ( test )" in plenty of ebuilds,
disabling the test phase if the use flag is unset altogether.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
onger proper description
can be written in the body of the commit message instead. Potentially
mixed in with multiple commits for different logical changes etc etc.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B
On 07/18/2018 11:55 AM, Ulrich Mueller wrote:
> I therefore suggest the following scheme:
The full scheme looks good to me
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Descript
'd say
cache is out of the question, whether it is /var/lib or /var/db doesn't
matter too much to me, but it needs to be announced properly ahead of
time to adjust LVM2 volumes etc etc if impacting existing systems... I'd
mostly argue any such change should only affect new systems
--
r field).
Sounds like a good thing, go for it!
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
s we
go along we need to have proper key rollover procedures so this should
never happen including backup keys.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
On 07/08/2018 08:10 PM, Rich Freeman wrote:
> Again, the current portage support for git verification doesn't check
> any developer keys.
right, so why would it be material for a news item improving the status
quo for those synching using the official rsync method?
--
Kristian F
ght not have published a revocation certificate.
the git sync method will need a way to distinguish this for end-users,
but the proper rsync synchronization will be able to trust the data at
the point we say it is OK.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
f
let others answer that. In any case, the point itself (requiring
> SHA-2 digest) makes sense. The RiseUp standard requires all self-
> signatures to be SHA-2, and I was planning on verifying that as well.
>
no, SHA256 in this context is already default, and it doesn't impac
ease wait for something that benefits
most users, just to give alternatives to a few using non-default sync
mechanism. Securing git distribution is a whole different ballpark.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA
w default.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
ng it from LDAP
and as such block access to push etc, so it actually is more important
for other aspects of the ecosystem than for us.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
D
consuming / difficult that it is a problem
to do it once a year? What do you do when certifying/signing other's UIDs?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
ers to add a dedicated RSA signing key for Gentoo if necessary
> (especially, since someone using ECC could be considered an advanced
> GnuPG user).
If the primary key is ECC, clients not supporting it won't be able to
use the key material even if the signing subkey is RSA.
>
> U
On 07/05/2018 01:22 AM, Kristian Fiskerstrand wrote:
> that said, I'm not aware of any curves defined with a lower security
> margin than this for OpenPGP in general. The known curves in the
> ecosystem are
known in the ecosystem being the union of rfc4880bis draft and rfc6637
t;\x2b\x24\x03\x03\x02\x08\x01\x01\x0d" -> 512(* brainpoolP512r1 *)
| "\x2b\x81\x04\x00\x0a" -> 256(* secp256k1 *)
| "\x2b\x06\x01\x04\x01\xda\x47\x0f\x01" -> 256(* Ed25519 *)
| _ -> failwith "Unknown OID"
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 07/04/2018 11:43 PM, Kristian Fiskerstrand wrote:
> On 07/04/2018 11:28 PM, Michał Górny wrote:
>> W dniu śro, 04.07.2018 o godzinie 23∶12 +0200, użytkownik Ulrich Mueller
>> napisał:
>>>>>>>> On Wed, 04 Jul 2018, Michał Górny wrote:
>>>&g
.
>
As I understand ulm's concern, the issue is with the max 1 year in
combination with this, e.g it effectively prohibits extended a subkey
expiring 2018-12-31 to 2019-12-31 two weeks before, since that exceeds
one year maximum
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hk
On 07/04/2018 12:59 PM, Michał Górny wrote:
>
> Or maybe even make a separate point about having a separate signing
> subkey?
>
Right, that is likely also easier to understand.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 30
On 07/04/2018 12:54 PM, Michał Górny wrote:
> W dniu śro, 04.07.2018 o godzinie 12∶35 +0200, użytkownik Kristian
> Fiskerstrand napisał:
>> On 07/04/2018 12:23 PM, Michał Górny wrote:
>>> -2. Root key and signing subkey of EITHER:
>>> +2. Root key and a dedicated
On 07/04/2018 12:23 PM, Michał Górny wrote:
> -2. Root key and signing subkey of EITHER:
> +2. Root key and a dedicated signing subkey, both of EITHER:
"dedicated" here might be misread to be gentoo-specific, which doesn't
really make much sense.
--
Kristian Fiskerst
On 07/04/2018 11:09 AM, Michał Górny wrote:
> I honestly don't think Gentoo is the distribution where we let people
> stay with obsolete versions for 'smaller footprint'.
1.4 isn't obsolete, it is still maintained as separate branch upstream.
--
Kristian Fiskerstrand
prefer 1.4 for its smaller
footprint etc. If we conclude that the git repo is internal and not to
be exposed to end-users per se, but distribution happens in curated git
or rsync I agree it is not an issue.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr
e wouldn't want to accept
them for various reasons.
There are good reasons these are not provided in the regular interface
of gnupg, but requires --expert
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3E
is less
of a concern now than back in the day.
But there aren't really very strong arguments in favor of ecc, and in
the case of quantum computation there less protection offered from ecc
due to smaller key sizes.
We also keep gnupg 1.4 in tree that does not, and will not, support ecc.
--
I would expect as much. But my primary argument would be key management
related, it is simply impossible to present a raw copy of our repo to end-users
and have them verify each commit
Original message From: William Hubbs
Date: 7/3/18 17:39 (GMT+01:00) To: gentoo-dev@lists.ge
For example, let's say a MITM that removes new version of some packages
> and related GLSAs in order to force the user to stay at vulnerable
> version.
>
right, just to point out, this is already covered in the metamanifest
signing scheme, but wouldn't be in a separate fil
engineering keys for distribution to end-users.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
d directory signature-based
> ACLs that I think you were hinting at before. So, sure, if you want to
> call for an abolition of rsync, maybe I'd follow you in that direction
> instead of the one here I'm proposing.
>
>
picking a semi-random post to respond to, but the ke
ng required.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
Plus signing emails is a pain if you don't use an MUA that has this
> feature, and the web-based ones which do aren't very good.
>
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
RC. Most discussion should anyways happen on
-project ML, whereby the -dev ML is technical in nature. So there isn't
any real restriction being imposed here.
Most contributions should happen via patches on b.g.o
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyserv
note that the whitelisting approach allows for
those opposing to start a project for -dev ML moderation that is similar
to editbugs and proxy maintenance as we currently have in the project.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 03/22/2018 12:56 AM, Chí-Thanh Christopher Nguyễn wrote:
> Kristian Fiskerstrand schrieb:
>
>> Switching to mailman might have some good merits on its own, but as I
>> understand it it isn't necessary for the proposal at hand, that can be
>> solved using access c
is going to be fun,
> but them the breaks.
Switching to mailman might have some good merits on its own, but as I
understand it it isn't necessary for the proposal at hand, that can be
solved using access control lists in mlmmj-process?
--
Kristian Fiskerstrand
OpenPGP keyblock reacha
ouncil meetings on the matter where it was clearly put on the agenda.
The bug in question is just a technical matter of implementing a final
decision.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
alias g-dev-whitelist)
>
This was not put in effect on 23 January 2018, however I have now
requested infra to put it in place in [bug 650964]. Users wishing
posting permissions are encouraged to find a mentor and register in [bug
644070]
References:
[bug 650964] https://bugs.gentoo.org/
On 02/13/2018 11:47 AM, Michael Palimaka wrote:
> On 02/12/2018 08:59 AM, Kristian Fiskerstrand wrote:
>> # Kristian Fiskerstrand (11 Feb 2018)
>> # Lastrite: app-crypt/monkeysign . Please use caff from
>> # app-crypt/signing-party instead. Removal in 30 days.
>>
# Kristian Fiskerstrand (11 Feb 2018)
# Lastrite: app-crypt/monkeysign . Please use caff from
# app-crypt/signing-party instead. Removal in 30 days.
# Bug: #647352
app-crypt/monkeysign
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109
On 02/06/2018 03:36 PM, Ulrich Mueller wrote:
>>>>>> On Tue, 6 Feb 2018, Kristian Fiskerstrand wrote:
>> More generally though, should we start requiring more verbose commit
>> messages for eclasses to make it easier to trace changes in our git
>> repo direc
epo
directly without reaching out to bugs? At least including summaries of
the respective bugs as a short description?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digi
t is presented to
be. It doesn't mean never install gnutls, but just not preferring it in
cases where there are other providers of ssl/tls, that the global
description already indicate.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
ons a bit. Make sure to mention both SSL and TLS
> to avoid confusion. Inform about the necessity of enabling USE=ssl
> in both implementation flags, and replace 'might' with 'if present'.
>
+1 / Reviewed-By
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://poo
FO:root:Valid OpenPGP signature found: INFO:root:- primary key:
> 1234567890ABCDEF1234567890ABCDEF12345678 INFO:root:- subkey:
> FEDCBA0987654321FEDCBA0987654321FEDCBA09
>
> The primary key printed must match 'Gentoo Portage Snapshot Signing
> Key' on the site. Please make
On 01/16/2018 03:45 PM, Aaron W. Swenson wrote:
> Given the situation, we have a choice: Remove GnuCash altogether, or
> press ahead with recommending a version upstream considers unstable.
Or 3, discuss with upstream to see if they can release an updated
version as stable branch.
--
Kr
That said, I agree with the overall premise of discussion, and stability
guarantees for the stable keywords, have anyone been in contact with
upstream and discussed the issue of getting a stable release branch not
based on the old webkit?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable
item is
correct approach, seems like an elog could satisfy this
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
es / auto-upgrades schema, maybe it should be stated explicitly
early on?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
mentioned already in https://bugs.gentoo.org/540006#c15
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
(although that doesn't exclude the possibility
of getting feed of all messages, which is already part of git repository)
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: O
On 01/05/2018 11:47 PM, Kristian Fiskerstrand wrote:
> On 01/05/2018 11:40 PM, Alec Warner wrote:
>>> I might sound like a broken CD here, but why define the expiration as
>>> part of the news format instead of specifying it in the package manager
>>> as a user defin
ility on the part of the user base.
There are rather big differences e.g between a server upgrade pattern
and a desktop system, how would you account for that in the expire date?
in particular for non security relevant upgrades, e.g profile changes?
--
Kristian Fiskerstrand
OpenPGP keyblock re
as a user defined variable? Various use cases requires different
treatment, so leaving it up to user seems more relevant to me, and we
could allow information to be presented as part of stages to give a hint
for what dates to look for?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks
On 01/03/2018 03:13 PM, Kristian Fiskerstrand wrote:
> On 01/03/2018 02:45 PM, Ciaran McCreesh wrote:
>> On Wed, 3 Jan 2018 12:23:33 +0100
>> Kristian Fiskerstrand wrote:
>>> Do we necessarily need to do even that? A package manager could have a
>>> feature
On 01/03/2018 02:45 PM, Ciaran McCreesh wrote:
> On Wed, 3 Jan 2018 12:23:33 +0100
> Kristian Fiskerstrand wrote:
>> Do we necessarily need to do even that? A package manager could have a
>> feature to mask based on other heuristics without changing the format,
>> e.g al
ed on other heuristics without changing the format,
e.g all messages from before X, presumably with a switch to show older.
I'm thinking along the lines of only show those published within last 12
months by default, configurable by make.conf variable.
--
Kristian Fiskerstrand
OpenPGP keybloc
userland policy (but even they fail from time to
time). For rest of the applications, even if we add tools to help
automate part of the stabilization, I'd very much oppose it being
automated without being initiated / acked by the maintainer.
--
Kristian Fiskerstrand
OpenPGP keyblock re
the dependency hell from it). That said,
you can have a stable chroot, or just use a VM for testing etc.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
ng it up doesn't add
additional value to the discussion. So again, please reduce the volume
of such posts.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 12/05/2017 11:41 PM, Kristian Fiskerstrand wrote:
> On 12/05/2017 11:37 PM, Rich Freeman wrote:
>> Honestly, I'm not really a big fan of even on-topic posts from people
>> who have caused a lot of harm to others in private. I'm not sure
>> which is the less
y any kind of abuse of other members?
We do not, but that presumes actual abuse has been demonstrated.
"spamming the mailing list", where the posts are regarding Gentoo, isn't
automatically abuse because some people are uncomfortable about the
information being presented, or
On 12/05/2017 11:25 PM, Rich Freeman wrote:
> On Tue, Dec 5, 2017 at 5:19 PM, Kristian Fiskerstrand wrote:
>> On 12/05/2017 11:12 PM, Rich Freeman wrote:
>>> On Tue, Dec 5, 2017 at 4:16 PM, Daniel Campbell wrote:
>>>> I think the plan to split mailing lis
is doesn't seem relevant to the matter of splitting the lists, and
would certainly be a matter for comrel.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 12/04/2017 10:36 PM, William L. Thomson Jr. wrote:
> Sorry last one, directed to Alec, but all should read.
I hope you really mean that, we've all heard you complaining about this
too many times already.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers
On 10/10/2017 09:16 PM, Andreas K. Huettel wrote:
> emerge -e world
we should use "@world" for sets to be consistent with recommendations to
users here.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8
ergo Propter Hoc
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
gnatures of MetaManifests in Portage.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
ues of wiki review and editing is a reasonable
argument, but we probably don't want to rush a change again.
Maybe we should start by defining a set of criteria / RFP for how we
would like the GLEP process to be and the format required?
--
Kristian Fiskerstrand
OpenPGP keyblock
even know what the proposed changes
> are you should also visit the link.
This violates the gentoo social contract, please keep the discussion on
the mailing list
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED
e, plugins, fonts,
most drivers, non-critical features)", so I'd say it is appropriate
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 08/15/2017 11:33 AM, tom...@gentoo.org wrote:
> Quoting Kristian Fiskerstrand (2017-08-15 10:37:39)
>> On 08/15/2017 12:29 AM, Rich Freeman wrote:
>>> On Mon, Aug 14, 2017 at 5:55 PM, Michał Górny wrote:
>>>> On pon, 2017-08-14 at 21:58 +0200, Thomas Beierlein wro
se. clientonly = noserver.
Can the "minimum"-use flag be utilized here?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
ldpkg-exclude "virtual/* sys-kernel/*-sources dev-perl/*
>> perl-core/*"
> Something like this would NOT be desirable. It would have to be done on
> every system.
It would have to be set on every binhost, not every client system.. that
said, I prefer env approach as it is e
1 - 100 of 358 matches
Mail list logo
