On Sat, 15 Aug 2015 08:12:42 +0200 Paweł Hajdan, Jr. wrote:
> On 8/15/15 3:16 AM, Ian Stakenvicius wrote:
> > Secondly, though, conversion to EAPI5 is not actually trivial, there
> > are a couple of things, 'usex' related for instance, that also need
> > to be taken care of. If it was just a matte
On 8/15/15 3:16 AM, Ian Stakenvicius wrote:
> Secondly, though, conversion to EAPI5 is not actually trivial, there
> are a couple of things, 'usex' related for instance, that also need
> to be taken care of. If it was just a matter of running a sed -e
> 's/^EAPI=4/EAPI=5/' on all in-tree ebuilds t
On 8/15/15 7:35 AM, Michał Górny wrote:
> Dnia 2015-08-15, o godz. 00:05:57
> Johannes Huber napisał(a):
>> if we want to attract more contributors we should consider to have one
>> supported EAPI (latest). EAPI 4 is the last not marked as deprecated
>> (< EAPI 5). The move in ebuilds from EAPI 4
Dnia 2015-08-15, o godz. 00:05:57
Johannes Huber napisał(a):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hello Gentoos Penguins,
>
> if we want to attract more contributors we should consider to have one
> supported EAPI (latest). EAPI 4 is the last not marked as deprecated
> (< EAP
On 08/14/15 07:15, Rich Freeman wrote:
> On Fri, Aug 14, 2015 at 2:01 AM, Michał Górny wrote:
>>
>> Don't ask me. I was against keeping the official listings in MediaWiki,
>> I already complained that we can't list developers who are refusing to
>> create a Wiki account and that we lack any proper
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/08/15 06:43 PM, Johannes Huber wrote:
>
>
> Am 08/15/15 um 00:19 schrieb Andrew Savchenko:
>> Hi,
>
>> While I have no objections about EAPI 4 deprecation (except
>> concerns mentioned above), I see no strong need for this also.
>> Just dec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 08/15/15 um 00:19 schrieb Andrew Savchenko:
> Hi,
>
> While I have no objections about EAPI 4 deprecation (except
> concerns mentioned above), I see no strong need for this also. Just
> declare EAPI 5 as recommended. Having legacy support for
Hi,
On Sat, 15 Aug 2015 00:05:57 +0200 Johannes Huber wrote:
> if we want to attract more contributors we should consider to have one
> supported EAPI (latest). EAPI 4 is the last not marked as deprecated
> (< EAPI 5). The move in ebuilds from EAPI 4 to EAPI 5 is very simple
> replacing the declar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Gentoos Penguins,
if we want to attract more contributors we should consider to have one
supported EAPI (latest). EAPI 4 is the last not marked as deprecated
(< EAPI 5). The move in ebuilds from EAPI 4 to EAPI 5 is very simple
replacing the de
On 08/10/2015 05:09 PM, Rich Freeman wrote:
> On Mon, Aug 10, 2015 at 11:04 AM, Mike Gilbert wrote:
>>
>> Expanding on this: the rsync master creates the following
>> files/directories under metatdata. On my own system, I like to symlink
>> them to locations outside my repo so that related portage
On Fri, Aug 14, 2015, at 15:04 CDT, Andrew Savchenko wrote:
> On Thu, 13 Aug 2015 19:19:10 +0800 Ben de Groot wrote:
>> I vote for a simple
>>
>> Bug: 333531
>
> +1
>
> Of course, for external bugs (e.g. in other projects) full URI
> should be used.
+1
signature.asc
Description: PGP signatur
On Thu, 13 Aug 2015 19:19:10 +0800 Ben de Groot wrote:
> I vote for a simple
>
> Bug: 333531
+1
Of course, for external bugs (e.g. in other projects) full URI
should be used.
Best regards,
Andrew Savchenko
pgpwvJxv7YOQ_.pgp
Description: PGP signature
On 08/14/2015 04:21 AM, Daniel Campbell (zlg) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/13/2015 06:29 PM, wireless wrote:
On 08/13/2015 05:28 PM, Duncan wrote:
wireless posted on Thu, 13 Aug 2015 08:33:13 -0500 as excerpted:
On 08/12/2015 09:52 PM, Mike Frysinger wrote:
O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/14/2015 04:54 PM, Rich Freeman wrote:
> On Fri, Aug 14, 2015 at 8:45 AM, Kristian Fiskerstrand
> wrote:
>>
>>>
>>> 2. The question is why manifests are modified for rsync. In
>>> git manifests are thin (only distfiles are there), in rsync
>>
On Fri, Aug 14, 2015 at 8:45 AM, Kristian Fiskerstrand wrote:
>
>>
>> 2. The question is why manifests are modified for rsync. In git
>> manifests are thin (only distfiles are there), in rsync they also
>> contain checksums for ebuilds and files dir content. Do we really
>> need this? These manife
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/08/15 07:56 AM, Andrew Savchenko wrote:
> 2. The question is why manifests are modified for rsync. In git
> manifests are thin (only distfiles are there), in rsync they
> also contain checksums for ebuilds and files dir content. Do we
> really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/08/15 07:16 AM, hasufell wrote:
> On 08/14/2015 01:10 PM, Andrew Savchenko wrote:
>> On Fri, 14 Aug 2015 02:11:09 -0700 Daniel Campbell (zlg)
>> wrote:
>>> I honestly don't see the point of this when `git log` or even
>>> `git diff` or standard
> They will be OpenPGP signed by a releng key during thickening and
> portage will auto-verify it using gkeys once things are in place. As
> such checksum for ebuilds and other files certainly needs to be part
> of the manifest, otherwise it can open up for malicious alterations of
> these files.
On Thu, Aug 13, 2015 at 8:33 PM, Mike Frysinger wrote:
> On 13 Aug 2015 17:18, Mike Gilbert wrote:
>> On Wed, Aug 12, 2015 at 11:17 PM, Mike Frysinger wrote:
>> > +If you are stuck with DSA keys, you can re-enable support locally by
>> > +updating your sshd_config file with a line like so:
>> > +
On 2015-08-13 08:13, Rich Freeman wrote:
> On Thu, Aug 13, 2015 at 7:19 AM, Ben de Groot wrote:
> > I vote for a simple
> >
> > Bug: 333531
> >
> > If it is going to be any longer than that, then you need to make sure
> > it is part of the commit message template magic. Because I'm surely
> > not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/14/2015 01:56 PM, Andrew Savchenko wrote:
..
>
> 2. The question is why manifests are modified for rsync. In git
> manifests are thin (only distfiles are there), in rsync they also
> contain checksums for ebuilds and files dir content. Do
Dnia 2015-08-14, o godz. 11:34:06
Michał Górny napisał(a):
> # Michał Górny (14 Aug 2015)
> # net-libs/adns never had any Gentoo maintainer. Mostly dead upstream
> # since 2006 (short activity in 2014). Does not respect nsswitch.conf or
> # /etc/hosts. The current version does not support IPv6.
On Fri, 14 Aug 2015 13:16:47 +0200 hasufell wrote:
> On 08/14/2015 01:10 PM, Andrew Savchenko wrote:
> > On Fri, 14 Aug 2015 02:11:09 -0700 Daniel Campbell (zlg) wrote:
> >> I honestly don't see the point of this when `git log` or even `git
> >> diff` or standard `diff` will tell you if what's in y
On 08/14/2015 01:10 PM, Andrew Savchenko wrote:
> On Fri, 14 Aug 2015 02:11:09 -0700 Daniel Campbell (zlg) wrote:
>> I honestly don't see the point of this when `git log` or even `git
>> diff` or standard `diff` will tell you if what's in your overlay
>> differs from the source. With some bash magi
On Fri, Aug 14, 2015 at 2:01 AM, Michał Górny wrote:
>
> Don't ask me. I was against keeping the official listings in MediaWiki,
> I already complained that we can't list developers who are refusing to
> create a Wiki account and that we lack any proper API to access those
> listings.
>
Agree wit
On Fri, 14 Aug 2015 02:11:09 -0700 Daniel Campbell (zlg) wrote:
> I honestly don't see the point of this when `git log` or even `git
> diff` or standard `diff` will tell you if what's in your overlay
> differs from the source. With some bash magic it could even be
> automated. The point of that 'fe
Daniel Campbell (zlg) posted on Fri, 14 Aug 2015 02:21:21 -0700 as
excerpted:
> tldr .gitignore just applies to the Gentoo repository, not an entire
> Gentoo system.
Thanks. That's exactly why I was confused when /opt and other out-of-repo
locations were mentioned, but I think you explained it
# Michał Górny (14 Aug 2015)
# net-libs/adns never had any Gentoo maintainer. Mostly dead upstream
# since 2006 (short activity in 2014). Does not respect nsswitch.conf or
# /etc/hosts. The current version does not support IPv6. net-dns/c-ares
# is a suggested replacement. Removal in 30 days.
# ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/13/2015 06:29 PM, wireless wrote:
> On 08/13/2015 05:28 PM, Duncan wrote:
>> wireless posted on Thu, 13 Aug 2015 08:33:13 -0500 as excerpted:
>>
>>> On 08/12/2015 09:52 PM, Mike Frysinger wrote:
On 12 Aug 2015 18:27, Brian Dolbec wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/13/2015 12:43 PM, Robin H. Johnson wrote:
> On Thu, Aug 13, 2015 at 10:36:16AM -0500, William Hubbs wrote:
>> I understood the usefulness of this line to some when we were
>> using CVS since it expanded into the ebuild revision, date, etc.
>>
On Wed, Aug 12, 2015 at 3:47 PM, Mike Frysinger wrote:
> On 12 Aug 2015 15:20, Leno Hou wrote:
> > 2. How to control endian difference via profiles ? i.e. *How to get
> > ppc64le as a full stage/profile along side ppc64* ?
> > Could you give me in detail ?
>
> you probably want to create a
31 matches
Mail list logo
