Patrick Lauer posted on Fri, 23 Nov 2012 12:45:56 +0800 as excerpted: > On 11/20/12 21:57, Alexis Ballier wrote: >> On Fri, 16 Nov 2012 09:10:51 +0000 (UTC) >> "Patrick Lauer (patrick)" <[email protected]> wrote: >> >>> patrick 12/11/16 09:10:51 >>> >>> Modified: ChangeLog >>> Added: lyx-2.0.5.ebuild >>> Log: Bump >>> >> While the bump was fine, please read the damn metadata.xml when you >> touch a package you're not used to. Pavel has been doing a very good >> job in (proxy) maintaining lyx since years and you do not seem to have >> contacted him before doing the bump, which is a bit disrespectful for >> him IMHO. > > I disagree. A fix is a fix, a bump is a bump, no ego involved. > >> If you want to help in having things done quicker because I'm not >> always responsive enough, then please do it correctly and ask Pavel to >> CC you when he sends me instructions for lyx. > I dislike this territorialism. Why add a single point of failure to > package maintenance? (What if you or Pavel "disappear" for any reason?)
Reasonable points on both sides. At minimum a note to the maintainers (both proxy and non-gentoo-dev) would have been nice. A wait of say two (work) days minimum (a full week's probably reasonable on most packages) for a reply would have been a courtesy as well, given the maintainer may be aware of issues with the new version that need worked out. OTOH, I get as antsy as anyone when I see a new version out, yet not in- tree (or even in the testing overlay when there is one) even masked.[1] If there's no reply in a few days, then yes, I'd say go ahead and non- maintainer-bump. --- [1] I've bumped firefox to 17 here locally, as it's not even in the overlay yet, and 16.0.2 wasn't letting me in to my bank any longer, probably due to a rebuild needed. I figured I might as well try the new version since it's out instead of just rebuilding the old one only to have to build the new one in a day or two, but I had to bump locally and fix up one line on a gentoo patch to do it. Yes, I'm antsy, but not complaining altho firefox is a high enough priority and high exposure app with security issues fixed, so much longer and I COULD be, but I'm just using it as an illustration here. (IOW, FF is an app where I'd say closer to that two day minimum, even if for most apps I'd say a week. But of course it's also a complicated app, with gentoo often carrying a number of patches, so a bit of delay could be understandable... but I'd still like to see it in the mozilla overlay at least, even if it's not considered ready for the tree, even masked. That's the reason I /have/ that overlay setup in layman, after all!) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
