On 05/11/16 04:45, Kent Fredric wrote:
> On Fri, 4 Nov 2016 23:09:07 -0400
> Mike Gilbert wrote:
>
>> On Fri, Nov 4, 2016 at 9:36 PM, Jonas Stein wrote:
>> [...]
>>>
>> [...]
>>> Yes, that is a good idea.
>>>
>>> cat googlecode-shutdown.txt | cut -f1 -d":" | xargs equery meta -mH |
>>> gr
On Fri, 4 Nov 2016 23:09:07 -0400
Mike Gilbert wrote:
> On Fri, Nov 4, 2016 at 9:36 PM, Jonas Stein wrote:
> [...]
> >
> [...]
> >
> > Yes, that is a good idea.
> >
> > cat googlecode-shutdown.txt | cut -f1 -d":" | xargs equery meta -mH |
> > grep "\@" | sort | uniq | sed "s/@/__/g"
> >
On Thu, 27 Oct 2016 10:25:39 -0400
Rich Freeman wrote:
> It would be nice if standards like USB incorporated some kind of GUID.
> I ended up having to write a udev rule for a pl2303 RS232 adapter to
> tie it to a specific USB port precisely so that I could have more than
> one and know which one
On Fri, Nov 4, 2016 at 9:36 PM, Jonas Stein wrote:
>>> If you maintain one of these packages, please fix the SRC_URI and
>>> HOMEPAGE variables.
>
>> It would probably be better if the output included the maintainer.
>
> Yes, that is a good idea.
>
> cat googlecode-shutdown.txt | cut -f1 -d":" | x
>> If you maintain one of these packages, please fix the SRC_URI and
>> HOMEPAGE variables.
> It would probably be better if the output included the maintainer.
Yes, that is a good idea.
cat googlecode-shutdown.txt | cut -f1 -d":" | xargs equery meta -mH |
grep "\@" | sort | uniq | sed "s/@/__/g
On 05/11/16 01:20, Rich Freeman wrote:
> On Fri, Nov 4, 2016 at 8:30 PM, M. J. Everitt wrote:
>> Apologies, getting ahead of myself here .. there must be a portage
>> utility, but I've forgotten which one interrogates metadata .. I'll
>> defer to a more authoritative source ...
>>
> There might be
> Apologies, getting ahead of myself here .. there must be a portage
> utility, but I've forgotten which one interrogates metadata .. I'll
> defer to a more authoritative source ...
You can try to fetch the maintainers per package with
equery meta -mH foo/bar
Best,
--
Jonas
On Fri, Nov 4, 2016 at 8:30 PM, M. J. Everitt wrote:
> Apologies, getting ahead of myself here .. there must be a portage
> utility, but I've forgotten which one interrogates metadata .. I'll
> defer to a more authoritative source ...
>
There might be a command line utility if you're doing things
On 05/11/16 00:23, M. J. Everitt wrote:
> On 05/11/16 00:20, Rich Freeman wrote:
>> On Fri, Nov 4, 2016 at 7:54 PM, Jonas Stein wrote:
>>> If you maintain one of these packages, please fix the SRC_URI and
>>> HOMEPAGE variables.
>>>
>> It would probably be better if the output included the maintai
On 05/11/16 00:20, Rich Freeman wrote:
> On Fri, Nov 4, 2016 at 7:54 PM, Jonas Stein wrote:
>> If you maintain one of these packages, please fix the SRC_URI and
>> HOMEPAGE variables.
>>
> It would probably be better if the output included the maintainer.
> Hopefully this isn't using anything depr
On Fri, Nov 4, 2016 at 7:54 PM, Jonas Stein wrote:
>
> If you maintain one of these packages, please fix the SRC_URI and
> HOMEPAGE variables.
>
It would probably be better if the output included the maintainer.
Hopefully this isn't using anything deprecated, but you should be able
to steal from
Dear all,
Google announced in 2015 to close the "Google Code" repositories [1].
They will provide the repositories in read only state till end of 2016.
Today we have still 524 ebuilds with SRC_URI=*googlecode* in the tree
[2] and should get these fixed before end of 2016.
If you maintain one of
On piątek, 4 listopada 2016 20:58:23 CET James Le Cuirot wrote:
> On Fri, 4 Nov 2016 13:37:42 +0100
>
> Alexis Ballier wrote:
> > On Fri, 4 Nov 2016 12:33:37 +
> >
> > James Le Cuirot wrote:
> > > On Fri, 4 Nov 2016 13:20:16 +0100
> > >
> > > Alexis Ballier wrote:
> > > > On Thu, 3 Nov 2
On Fri, 4 Nov 2016 13:37:42 +0100
Alexis Ballier wrote:
> On Fri, 4 Nov 2016 12:33:37 +
> James Le Cuirot wrote:
>
> > On Fri, 4 Nov 2016 13:20:16 +0100
> > Alexis Ballier wrote:
> >
> > > On Thu, 3 Nov 2016 00:52:17 +0100
> > > Maciej Mrozowski wrote:
> > >
> > > > From: Maciej
On 04/11/16 11:55, Maciej Mrozowski wrote:
> On czwartek, 3 listopada 2016 07:31:10 CET Michał Górny wrote:
>> On Thu, 3 Nov 2016 00:52:16 +0100
>>
>> Maciej Mrozowski wrote:
>>> From: Maciej Mrozowski
>>>
>>> ---
>>>
>>> eclass/cmake-utils.eclass | 54
>>> ++---
On Fri, 4 Nov 2016 12:33:37 +
James Le Cuirot wrote:
> On Fri, 4 Nov 2016 13:20:16 +0100
> Alexis Ballier wrote:
>
> > On Thu, 3 Nov 2016 00:52:17 +0100
> > Maciej Mrozowski wrote:
> >
> > > From: Maciej Mrozowski
> > >
> > > ---
> > > eclass/cmake-utils.eclass | 6 +++---
> > > 1 f
On Fri, 4 Nov 2016 13:20:16 +0100
Alexis Ballier wrote:
> On Thu, 3 Nov 2016 00:52:17 +0100
> Maciej Mrozowski wrote:
>
> > From: Maciej Mrozowski
> >
> > ---
> > eclass/cmake-utils.eclass | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/eclass/cmake-uti
On Thu, 3 Nov 2016 00:52:17 +0100
Maciej Mrozowski wrote:
> From: Maciej Mrozowski
>
> ---
> eclass/cmake-utils.eclass | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/eclass/cmake-utils.eclass b/eclass/cmake-utils.eclass
> index 88d2163..23cc094 100644
> --- a/
On Fri, 4 Nov 2016 10:24:28 +0100
Ulrich Mueller wrote:
> I would assume to be high enough, even if you use multiples of
> 100 to label the slot. Or do you expect having more than 100 slots for
> Perl?
Well, the desire is for the -r (or similar) part correspond to
something representative o
> On Fri, 4 Nov 2016, Kent Fredric wrote:
>> 1. Revision number must be no longer than :
>> 1a. to make <=X-r reliable,
>> 1b. to prevent pathological uses of revision as date.
> I think most the arguments you've made for this stem from subjective
> and social problems, not technical
> On Fri, 4 Nov 2016, Kristian Fiskerstrand wrote:
> On 11/03/2016 05:11 PM, Michał Górny wrote:
>> == Policy changes? ==
>> I think that the following new policies could make sense:
>>
>> 1. Revision number must be no longer than :
> You likely mean "no higher than ", longer than wo
On Thu, 3 Nov 2016 17:11:22 +0100
Michał Górny wrote:
> 1. Revision number must be no longer than :
> 1a. to make <=X-r reliable,
> 1b. to prevent pathological uses of revision as date.
I think most the arguments you've made for this stem from subjective
and social problems, not technica
On 11/03/2016 05:11 PM, Michał Górny wrote:
> == Policy changes? ==
> I think that the following new policies could make sense:
>
> 1. Revision number must be no longer than :
You likely mean "no higher than ", longer than would give large values
> 1a. to make <=X-r reliable,
> 1b. t
# Johannes Huber (04 Nov 2016)
# Masked for reomval in 30 days. Superseded by kde-plasma/plasma-nm.
# Only support for deprecated Plasma 4. Exported to kde-sunset overlay.
kde-misc/networkmanagement
--
Johannes Huber (johu)
Gentoo Linux Developer / KDE Team
GPG Key ID FDF4F788
signature.asc
De
24 matches
Mail list logo
