On Sat, Jul 7, 2018 at 5:29 PM Martin Vaeth wrote:
>
> Rich Freeman wrote:
> > On Sat, Jul 7, 2018 at 1:34 AM Martin Vaeth wrote:
> >>
> >> Biggest issue is that git signature happens by the developer who
> >> last commited which means that in practice you need dozens/hundreds
> >> of keys.
> >
Rich Freeman wrote:
> On Sat, Jul 7, 2018 at 1:51 AM Martin Vaeth wrote:
>> Davyd McColl wrote:
>>
>> > I ask because prior to the GitHub incident, I didn't have signature
>> > verification enabled
>>
>> Currently, it is not practical to change this, see my other posting.
>
> You clearly don't u
Rich Freeman wrote:
> On Sat, Jul 7, 2018 at 1:34 AM Martin Vaeth wrote:
>>
>> Biggest issue is that git signature happens by the developer who
>> last commited which means that in practice you need dozens/hundreds
>> of keys.
>
> This is untrue. [...]
> It will, of course, not work on the regula
On Sat, 7 Jul 2018 21:51:31 +0300
Franz Fellner wrote:
> It's not automatically doing magic but using things specified in the
> profile. In this case look at ${PORTDIR}/profile/base/package.use
> Setting PYTHON_SINGLE_TARGET (which is expanded to those USEFlags) in your
> make.conf will shadow th
It's not automatically doing magic but using things specified in the
profile. In this case look at ${PORTDIR}/profile/base/package.use
Setting PYTHON_SINGLE_TARGET (which is expanded to those USEFlags) in your
make.conf will shadow those from the profile and spit out an error.
2018-07-07 21:45 GMT
The package you're referring to have only support of python2 interpreters
(python2_7 (CPython) and pypy (not the pypy3)).
It seems, by default (if neither of PYTHON_SINGLE_TARGET is set), portage
tries to do the "magic" (well, in my opinion, it opposes to the Gentoo
Philosophy, and it should th
Hello,
I have a question considering PYTHON_SINGLE_TARGET because it seems to behave
inconsistently on my system and I cannot find any documentation about it, that
would
guide me in the right direction how to fix it.
Running emerge --info I see the following (I'm on ~amd64):
... PYTHON_SINGLE_TARG
On Sat, Jul 7, 2018 at 1:34 AM Martin Vaeth wrote:
>
> Rich Freeman wrote:
> >
> > Biggest issue with git signature verification is that right now it
> > will still do a full pull/checkout before verifying
>
> Biggest issue is that git signature happens by the developer who
> last commited which
On Sat, Jul 7, 2018 at 1:51 AM Martin Vaeth wrote:
>
> Davyd McColl wrote:
>
> > I ask because prior to the GitHub incident, I didn't have signature
> > verification enabled
>
> Currently, it is not practical to change this, see my other posting.
>
You clearly don't understand what it actually c
9 matches
Mail list logo
