> On Mon, 18 Dec 2017, Michał Górny wrote:
> Display-If-Keyword: ~amd64
Only keyword names [1] allowed there.
> multilib layout, and require explicit migration as described below. They
> are considered experimental at the moment, and have a fair risk
Your line wrapping has room for improvem
13.12.2017 21:20, Lucas Ramage пишет:
> What about running a stable chroot? Are there any tools that can be
> used to automate this process?
Try gentoo-chrootiez[1], it is written by our fellow gentoo developer -
slyfox. And it is damn simple to use.
[1] - https://github.com/trofi/gentoo-chroot
On Thu, 14 Dec 2017 16:04:17 -0600
R0b0t1 wrote:
> Can you be specific? Human memory is biased towards negative
> experiences. If it's hard to actually describe the multitude of issues
> that mixed systems cause then it is very likely mixed systems do not
> cause many issues.
We have mixed syste
W dniu wto, 19.12.2017 o godzinie 09∶08 +0100, użytkownik Ulrich Mueller
napisał:
> > > > > > On Mon, 18 Dec 2017, Michał Górny wrote:
> > Display-If-Keyword: ~amd64
>
> Only keyword names [1] allowed there.
Fixed already. Though I'm thinking that it'd probably be better to use
Display-If-Profile
On 12/17/17 19:39, Mike Gilbert wrote:
> On Sun, Dec 17, 2017 at 8:21 AM, Michał Górny wrote:
>> Hello, everyone.
>>
>> It's my pleasure to announce that with a majority vote the QA team has
>> accepted a new policy. The accepted wording is:
>>
>> Total size of 'files' subdirectory of a package
On Tue, Dec 19, 2017 at 2:33 PM, Patrick Lauer wrote:
> On 12/17/17 19:39, Mike Gilbert wrote:
>> On Sun, Dec 17, 2017 at 8:21 AM, Michał Górny wrote:
>>> Hello, everyone.
>>>
>>> It's my pleasure to announce that with a majority vote the QA team has
>>> accepted a new policy. The accepted wordin
On 2017-12-17 14:21, Michał Górny wrote:
> Total size of 'files' subdirectory of a package should not be larger
> than 32 KiB. If the package needs more auxiliary files, they should
> be put into SRC_URI e.g. via tarballs.
I don’t have any strong opinions about this either way.
However, wha
On Tue, Dec 19, 2017 at 3:33 PM, Patrick Lauer wrote:
> On 12/17/17 19:39, Mike Gilbert wrote:
>> On Sun, Dec 17, 2017 at 8:21 AM, Michał Górny wrote:
>>> Hello, everyone.
>>>
>>> It's my pleasure to announce that with a majority vote the QA team has
>>> accepted a new policy. The accepted wordin
And it would be nice to also recall the overlays, which can also use repoman
(and/or mgorny's travis hook for that), but at the same time have no
possibility to self-host the patches...
// well, I personally would prefer that repoman had an option to "ignore" some
(specified as an argument) of
On Tuesday, December 19, 2017 3:44:26 PM EST R0b0t1 wrote:
> How easy is it to move patches to Gentoo infrastructure if the patches
> are not provided by upstream? I am slightly uncomfortable with
> everything being pushed to websites like GitHub by default.
How are patches different from other di
# Patrice Clement (19 Dec 2017)
# A slightly better syntax file for PAM configuration files is shipped with Vim
# since version 8.0. The one we package is old and out of date.
# Masked for removal in 30 days. See bug 578278.
app-vim/pam-syntax
--
Patrice Clement
Gentoo Linux developer
http://www
On 2017-12-19 21:44, R0b0t1 wrote:
> How easy is it to move patches to Gentoo infrastructure if the patches
> are not provided by upstream? I am slightly uncomfortable with
> everything being pushed to websites like GitHub by default.
Don't get me wrong but this a *dev* mailing list. Your statemen
On Tue, Dec 19, 2017 at 4:14 PM, Elvis Pranskevichus wrote:
> On Tuesday, December 19, 2017 3:44:26 PM EST R0b0t1 wrote:
>> How easy is it to move patches to Gentoo infrastructure if the patches
>> are not provided by upstream? I am slightly uncomfortable with
>> everything being pushed to website
13 matches
Mail list logo
