Gentoo Archives: gentoo-dev

From: Patrick Lauer <patrick@g.o>
To: Alexis Ballier <aballier@g.o>
Cc: gentoo-dev@l.g.o, Pavel Sanda <sanda@×××.org>
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-office/lyx: lyx-2.0.5.ebuild ChangeLog
Date: Sun, 25 Nov 2012 06:55:34
Message-Id: 50B1C0CA.1070104@gentoo.org
In Reply to: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-office/lyx: lyx-2.0.5.ebuild ChangeLog by Alexis Ballier
1 On 11/23/12 21:17, Alexis Ballier wrote:
2 > On Fri, 23 Nov 2012 12:45:56 +0800
3 > Patrick Lauer <patrick@g.o> wrote:
4 >
5 >> On 11/20/12 21:57, Alexis Ballier wrote:
6 >>> On Fri, 16 Nov 2012 09:10:51 +0000 (UTC)
7 >>> "Patrick Lauer (patrick)" <patrick@g.o> wrote:
8 >>>
9 >>>> patrick 12/11/16 09:10:51
10 >>>>
11 >>>> Modified: ChangeLog
12 >>>> Added: lyx-2.0.5.ebuild
13 >>>> Log:
14 >>>> Bump
15 >>>>
16 >>>
17 >>>
18 >>>
19 >>> While the bump was fine, please read the damn metadata.xml when you
20 >>> touch a package you're not used to. Pavel has been doing a very good
21 >>> job in (proxy) maintaining lyx since years and you do not seem to
22 >>> have contacted him before doing the bump, which is a bit
23 >>> disrespectful for him IMHO.
24 >>
25 >> I disagree. A fix is a fix, a bump is a bump, no ego involved.
26 >
27 > And respect is respect. It's not because you woke up someday in a
28 > special mood that a 4+ years perfectly working workflow will change...
29 >
30 >>
31 >>> If you want to help in having things done quicker because I'm not
32 >>> always responsive enough, then please do it correctly and ask Pavel
33 >>> to CC you when he sends me instructions for lyx.
34 >> I dislike this territorialism. Why add a single point of failure to
35 >> package maintenance? (What if you or Pavel "disappear" for any
36 >> reason?)
37 >
38 > Ask those who invented maintainers. Take your point to the council. So
39 > far these are the rules, follow them or leave it.
40 >
41 > As for the single point of failure, Pavel being part of upstream sends
42 > me the ebuilds _before_ the actual release. That is not what I call a
43 > failure. The proposal to also be a proxy still stands, but if you
44 > continue with this provocative behavior I'm not sure I want to work
45 > with you...
46 >
47 > A.
48 >
49
50 "provocative"
51
52 Aaaargh.
53
54 With that kind of agression from *your* side I might just ignore your
55 input because you're really annoying me.
56
57 As for packages, all my packages are "Do what you want", with an
58 optional "feel free to notify me if you change something"...

Replies