On 01/06/12 05:26, Olivier Crête wrote:
[snip]
> The only thing I see them sacrificing is loose coupling, they provide
> more functionality than any other init system, more correctness
> (seriously, did you ever read most init scripts out there?), more well
> defined behavior (all systemd systems b
On 01/07/15 06:24, William Hubbs wrote:
> All,
>
> Many packages have been masked in the tree for months - years with no
> signs of fixes.
>
> I am particularly concerned about packages with known security
> vulnerabilities staying in the main tree masked. If people want to keep
> using those pac
On 01/16/15 23:26, hasufell wrote:
> Patrick Lauer (patrick):
>> patrick 15/01/16 04:16:55
>>
>> Modified: ChangeLog
>> Added:libuv-1.2.1.ebuild
>> Log:
>> Bump
>>
>
> I expect people to ask me for revi
On Friday 16 January 2015 18:29:08 hasufell wrote:
> Patrick Lauer:
> > On 01/16/15 23:26, hasufell wrote:
> >> Patrick Lauer (patrick):
> >>> patrick 15/01/16 04:16:55
> >>>
> >>> Modified: ChangeLog
> >>>
Here's a random unsorted list of things that it would make sense to be upset
about. Some issues that people have successfully ignored for a few years ...
In no way exhaustive list, feel free to remember a dozen things I forgot ;)
(If you suggest other things please try to offer constructive criti
On Saturday 17 January 2015 13:44:21 Dirkjan Ochtman wrote:
> On Sat, Jan 17, 2015 at 12:35 PM, Patrick Lauer wrote:
> > * AutoRepoman catches issues, but no one but me seems to care
> >
> > Fix: Remind people of
> > http://packages.gentooexperimental.org
On Saturday 17 January 2015 14:32:03 Ciaran McCreesh wrote:
> On Sat, 17 Jan 2015 21:03:30 +0800
>
> Patrick Lauer wrote:
> > Last time I tested paludis it was slower
>
> You've yet to do a like-for-like comparison...
Hello hostile upstream.
It was as "like f
On Saturday 17 January 2015 14:45:51 Ciaran McCreesh wrote:
> On Sat, 17 Jan 2015 17:39:29 +0300
>
> Andrew Savchenko wrote:
> > There is some progress here. In portage-2.2.15 profile based
> > optimizations are included (see bugs 529660, 530010). On my
> > hardware (Athlon-XP, 2200 MHz and Intel
On Saturday 17 January 2015 15:03:05 Ciaran McCreesh wrote:
> On Sat, 17 Jan 2015 22:58:33 +0800
>
> Patrick Lauer wrote:
> > On Saturday 17 January 2015 14:32:03 Ciaran McCreesh wrote:
> > > On Sat, 17 Jan 2015 21:03:30 +0800
> > >
> > > Patrick Lauer
On Saturday 17 January 2015 14:00:34 William Hubbs wrote:
> On Sat, Jan 17, 2015 at 01:44:21PM +0100, Dirkjan Ochtman wrote:
> > On Sat, Jan 17, 2015 at 12:35 PM, Patrick Lauer
wrote:
> > > * Stage3 archives are too fat
> > >
> > > See https://bu
On Saturday 17 January 2015 13:12:56 Zac Medico wrote:
> On 01/17/2015 03:35 AM, Patrick Lauer wrote:
> > * Portage is too slow
> >
> > On 'small' hardware emerge -upNDv @world can take enough time
> > to make updates prohibitive - on an 800Mhz machi
On Saturday 17 January 2015 17:25:15 hasufell wrote:
> Patrick Lauer:
> > On Friday 16 January 2015 18:29:08 hasufell wrote:
> >> Patrick Lauer:
> >>> On 01/16/15 23:26, hasufell wrote:
> >>>> Patrick Lauer (patrick):
> >>>>
On Sunday 18 January 2015 21:44:05 Michał Górny wrote:
> Hello,
>
> I would like to commit the following flags as cpu_flags_x86_desc.
> The list combines global USE flags with some local USE flags I've been
> able to find.
>
>
> 3dnow - Use the 3DNow! instruction set
> 3dnowext - Use the Enhance
On 01/19/15 17:47, Jeroen Roovers wrote:
> On Sat, 17 Jan 2015 19:35:09 +0800
> Patrick Lauer wrote:
>
>> * AutoRepoman catches on average maybe 2 user-visible breakages.
>> Mostly removing stable on HPPA ;)
>> Fix: Make repoman faster (tree-wide scans ta
On Friday 06 February 2015 06:28:27 Jory A. Pratt wrote:
> As many of you are aware we are using esr ( extended service releases
> ) for stable. We will remove all versions prior to 31.x in 7 days. If
> you are needing an older version please let us know and we will try to
> accommodate all users a
On Monday 16 February 2015 06:13:10 Mike Frysinger wrote:
> On Mon, Feb 16, 2015 at 1:16 AM, Alec Warner wrote:
> > On Sun, Feb 15, 2015 at 8:05 PM, Mike Frysinger wrote:
> >> On Wed, Dec 31, 2014 at 12:21 AM, Patrick Lauer (patrick)
> >>
> >> wrote:
Right now repoman is relatively permissive - it whines about many things, but
treats many issues as warning.
The result is that many ebuilds get committed with 'minor' cosmetic issues
which then someone more OCD than the original committer cleans up, making
pretty much everyone involved more un
On Wednesday 18 February 2015 18:43:59 hasufell wrote:
> Is there a communication problem?
>
> I don't remember getting either:
> * a bug report
> * a ping
> * a review request
>
> Did I miss something?
Yes.
Why is this package metadata missing the python herd for no reason?
Also
Why are you
On Thursday 19 February 2015 00:48:18 hasufell wrote:
> Patrick Lauer:
> > Why is this package metadata missing the python herd for no reason?
>
> Because the python herd doesn't currently maintain the package, nor did
> they ask me to be co-maintainers.
>
So you put a
On Thursday 19 February 2015 10:07:30 Kristian Fiskerstrand wrote:
> On 02/19/2015 09:57 AM, Markos Chandras wrote:
> > On 02/19/15 06:10, Mike Gilbert wrote:
> > What saddens me the most is that these pointless threads are
> > becoming sort of a habit not because the reporter is really
> > offende
On Thursday 19 February 2015 12:31:27 Alexis Ballier wrote:
> On Wed, 18 Feb 2015 22:48:27 +0100
>
> Michał Górny wrote:
> > Dnia 2015-02-18, o godz. 16:11:53
> >
> > "Mike Frysinger (vapier)" napisał(a):
> > > vapier 15/02/18 16:11:53
> > >
> > > Modified: fcaps.eclass
> >
On Saturday 18 April 2015 11:15:56 hasufell wrote:
> On 04/17/2015 07:15 PM, Rich Freeman wrote:
> > On Fri, Apr 17, 2015 at 10:41 AM, Alexander Berntsen
> >
> > wrote:
> >> On 17/04/15 16:33, Andrew Savchenko wrote:
> >>> The problem is double effort: previously one developer effort was
> >>> ne
On 05/19/15 05:13, Tim Harder wrote:
> Here are some packages that I've dropped (or will drop) myself as
> primary maintainer from. Many of them (e.g. protobuf*) could really use
> some more collaborative non-maintainer update method but no one has
> gotten around to finalizing, documenting, and im
On 06/06/15 09:26, Justin Lecher (jlec) wrote:
> Hi everyone,
>
> Can we get an agreement on how we are indenting metadata.xml?
>
> I like to properly format and indent metadata.xml, but without having
> an agreement or policy on the indention, I make unhappy by choosing
> the wrong.
>
> The two
On Sunday 05 July 2015 13:46:10 William Hubbs wrote:
> On Sun, Jul 05, 2015 at 09:05:59AM +0300, Andrew Savchenko wrote:
> > On Sat, 4 Jul 2015 20:20:23 +0200 Peter Stuge wrote:
> > > It's important that the review flow is well-understood and efficient.
> >
> > This is impossible in our case due t
On 07/07/15 01:27, Ciaran McCreesh wrote:
> On Mon, 06 Jul 2015 13:04:35 -0400
> Michael Orlitzky wrote:
>> I would love my commits to be reviewed, but I usually don't feel like
>> reviewing anyone else's. That's... not uncommon.
>
> Well, you could at least get your commits reviewed by an automa
On Sunday 19 July 2015 02:05:21 Patrice Clement wrote:
> Saturday 18 Jul 2015 15:36:01, NP-Hardass wrote :
> I fancy your idea a lot. We ought to do it for complete newbies who are new
> to Gentoo but would like to give the distribution a shot nonetheless. I
> fondly remember my first attempt who t
On Sunday 02 August 2015 22:22:28 Ciaran McCreesh wrote:
> On Sun, 02 Aug 2015 17:14:47 -0400
>
> NP-Hardass wrote:
> > ^^ has the pleasant side effect of being easier to read, as a user.
> > The user receives a message saying "at-most-one-of" instead of some
> > convoluted other expression that
On Monday 03 August 2015 00:34:51 Ben de Groot wrote:
> Recently some team members of the Qt project have adopted these ebuild
> policies: https://wiki.gentoo.org/wiki/Project:Qt/Policies
>
> I have an issue with the policy adopted under "Requires one of two Qt
> versions". In my opinion, in the c
On Sunday 09 August 2015 08:06:53 Anthony G. Basile wrote:
> Hi everyone,
>
> I hate to be a nag, but please read
> https://wiki.gentoo.org/wiki/Gentoo_git_workflow. In particular, commit
> messages. I'm seeing lots of cvs style messages going in and without
> history it will be hard to figure o
On 08/12/15 22:38, William Hubbs wrote:
> I always wondered why pkg_pretend never caught on.
Because, in a way, it triggers at the wrong point of the merge.
emerge -pv fnurk => dependencies look ok
emerge fnurk => pkg_pretend bails out ... eh?!
(This would be a little bit confusing, if not act
On 10/09/15 17:42, Davide Pesavento wrote:
> On Fri, Oct 9, 2015 at 5:35 PM, hasufell wrote:
>> On 10/08/2015 11:04 PM, Richard Farina wrote:
>>
>> +all_ruby_prepare() {
>> + [ -f Gemfile.lock ] && rm Gemfile.lock
>> missing "|| die" afais, should probably be
>>
>> [ -f Gemfile.lock ] && { r
On 10/10/15 14:25, hasufell wrote:
> On 10/10/2015 02:24 PM, Fabian Groffen wrote:
>> On 10-10-2015 14:19:44 +0200, hasufell wrote:
+RDEPEND="
+ !libressl? ( dev-libs/openssl:0 )
+ libressl? ( dev-libs/libressl )
+ sys-libs/zlib
+ net-libs/http-parser
>>> Please order
Ahoi,
I'm getting mildly very irritated with the lack of easily accessible
ChangeLogs for our packages.
Apparently updating them stopped some time in August, so now there are
some outdated ChangeLogs that don't really serve any purpose, and the
easiest way for users to figure out why something ch
On 11/01/2015 01:53 PM, Rich Freeman wrote:
> On Sun, Nov 1, 2015 at 7:33 AM, Мисбах-Соловьёв Вадим wrote:
>> And why don't just only generate them on rsync mirrors, but remove them from
>> git repo (like was planned initially, AFAIRC)?
>>
> That is in fact how it works. Or, at least how it is
On 11/01/2015 02:24 PM, hasufell wrote:
> On 11/01/2015 01:16 PM, Patrick Lauer wrote:
>> Ahoi,
>>
>> I'm getting mildly very irritated with the lack of easily accessible
>> ChangeLogs for our packages.
>>
>> Apparently updating them stopped some time
On 11/02/2015 02:56 AM, Rich Freeman wrote:
> On Sun, Nov 1, 2015 at 8:22 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>> I know if I were still on rsync (or webrsync), I'd be raising hell about
>> the lack of
>> changelogs well before now
> Perhaps rather than raising hell you'd do better to raise
On 11/02/2015 03:04 AM, Michael Orlitzky wrote:
> On 11/01/2015 08:22 PM, Duncan wrote:
>> Personally, I'd love the primary sync method to be git, and the primary
>> change logs conveyed via native git log methods, but in ordered to do
>> that, all those rsync mirrors need to switch to git mirr
On 11/03/2015 02:52 AM, Matt Turner wrote:
>
> So you are telling me that people using github and the switch that took
> place has absolutely nothing to do with the changelogs going dead?
> You keep saying GitHub. Github is not relevant to this discussion.
>
> Yes, the ChangeLogs stopped being up
On 11/11/2015 03:51 AM, Mike Frysinger wrote:
> On 10 Nov 2015 18:53, Mike Frysinger wrote:
>> i randomly stumbled across an ebuild that was using ^^ to make a variable
>> uppercase. this is new to bash-4.0 and thus invalid for EAPI=[0-5]. only
>> the fresh EAPI=6 permits it since we bumped the
On 11/18/2015 01:01 PM, Rich Freeman wrote:
> On Wed, Nov 18, 2015 at 6:12 AM, Alexander Berntsen
> wrote:
>> When I do QA in projects I'm involved with (at least outside of
>> Gentoo), we don't do it live on end-user systems. I'll leave the
>> details as an exercise for the Gentoo developer.
>
On 12/02/2015 08:38 AM, Anthony G. Basile wrote:
> On 12/2/15 2:06 AM, Michał Górny wrote:
>> So you're saying we should write a whole eclass to do:
>>
>> append-cppflags -std=c++11
>>
>> ?
>>
> I think you mean append-cxxflags. Anyhow, I had an off list discussion
> with David Klaftenegger ab
On 12/03/2015 06:36 PM, William Hubbs wrote:
> All,
>
> I would like opinions on what is considered the public api of librc.
>
> 1) All definitions in rc.h, even though they are not formally documented
> in man pages.
Yes.
The header *is* the public API.
>
> 2) the definitions in rc.h which are d
Broken breakage
tl;dr: Stuff is broken, and no one seems to care
In August the git "migration" happened, moving our main repository from
old stupid cvs to modern shiny git.
Well, migration is not the word I'd use, because this was an untested
forced migration that is now, months later, still
Oh hey. We're in the future. Let's try to commit something to
repo/gentoo.git!
So apparently we're signing things with gpg now, so let's read the
official documentation.
The [1] wiki seems to be the canonical location for such things.
Oh dear. The layout is VERY broken. See [2]. Which redirects t
On 12/13/2015 06:36 PM, Patrick Lauer wrote:
> So apparently we're signing things with gpg now
And a related question:
How would I actually verify the signatures in a meaningful way?
... and why is that not default then.
On 12/13/2015 07:50 PM, Andrew Savchenko wrote:
> Hi,
>
> On Sun, 13 Dec 2015 18:38:55 +0100 Patrick Lauer wrote:
>> On 12/13/2015 06:36 PM, Patrick Lauer wrote:
>>> So apparently we're signing things with gpg now
>> And a related question:
>>
>>
On 12/14/2015 04:00 AM, Brian Dolbec wrote:
> On Sun, 13 Dec 2015 22:20:01 +0300
> Andrew Savchenko wrote:
>
>> Hi,
>>
>> On Sun, 13 Dec 2015 18:36:51 +0100 Patrick Lauer wrote:
>>> Oh hey. We're in the future. Let's try to commit something to
&g
On 12/14/2015 02:58 PM, Rich Freeman wrote:
> On Mon, Dec 14, 2015 at 5:48 AM, Peter Stuge wrote:
>> The key point to remember is that it is NOT neccessary to be part of
>> the team in order to contribute solutions. You *first* contribute
>> solutions and only *then* have a chance of becoming pa
On 12/21/2015 04:21 AM, Ryan Hill wrote:
> On Sun, 13 Dec 2015 19:00:45 -0800
> Brian Dolbec wrote:
>
>
>> But, one of the biggest things keeping me from doing more work on it
>> when I do have some time, is the fact that barely any of the devs seem
>> to care (other than the OP, who just seems
On 12/22/2015 01:08 PM, Rich Freeman wrote:
>> Or just point people at a random email, because that's about as good as
>> documentation.
> Thank you for writing up a guide/outline.
>
> You appear to hate mediawiki, but you do realize that you could
> probably copy/paste that email into the box an
On 12/22/2015 02:14 PM, Rich Freeman wrote:
> On Tue, Dec 22, 2015 at 7:53 AM, Patrick Lauer wrote:
>> I'd replace gkeys-gen with a ~10-line shell script ... if I had some
>> motivation to dig through some old experiments of mine where I managed
>> to set all paramete
On 12/22/2015 03:04 PM, Rich Freeman wrote:
> On Tue, Dec 22, 2015 at 8:31 AM, Patrick Lauer wrote:
>>> Do you want to see this fixed?
>>> Are you willing to do the fixing yourself?
>> I don't have infinite time, and wasting a day documenting things that
>&
On 01/24/2016 11:49 AM, M. J. Everitt wrote:
> On 24/01/16 10:39, Amadeusz Żołnowski wrote:
>> Alex Brandt writes:
>>> * app-backup/rdiff-backup
>> Wasn't it meant for removal?
>>
>> -- Amadeusz Żołnowski
> Looks fine on p.g.o stable too. Upstream site is present.
>
Inactive upstream, known d
On 10/28/24 16:21, Michał Górny wrote:
Are you actually going to maintain all these new packages, or just dump
and effectively abandon them, as usual?
Hmm, that's actually good advice.
But most of those are very low maintenance, and I wanted to maintain them.
Thanks for your input,
Patrick
Hello everyone,
I've just returned from the pgconf.eu conference, and this has motivated
me to try to improve the packaging situation for all things PostgreSQL
in Gentoo.
Right now everything just goes into dev-db/ category. That's not
inherently wrong, but it feels a bit overloaded to me. S
401 - 456 of 456 matches
Mail list logo
