Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses

2012-01-21 Thread Ion-Mihai Tetcu
On Thu, 19 Jan 2012 19:00:04 +0100 Thomas Zander wrote: > > But the takeaway is that we can't expect the PR submitters, or even > > port maintainers, to get anything right.  It sure makes life easier > > when they do, but we can't take it for granted. > > As committers, we are that QA step. > > A

Fwd: Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses

2012-01-17 Thread Michael Scheidell
update (1.0.r20111218) conflicts with devel/ncurses Date: Tue, 17 Jan 2012 16:21:42 +0100 From: To: , , , Synopsis: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses Responsible-Changed-From-To: ehaupt->scheidell Responsible-Changed-By: ehaupt Responsi

Re: Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses

2012-01-17 Thread Thomas Zander
On Tue, Jan 17, 2012 at 16:35, Michael Scheidell wrote: > tell me you want me to revert this patch, and do a portepoch. > the solution would be for the submitter to work with the maintainer on a > solution, or am I supposed to fix this without reversing this? Let's all calm down first :-) Please

Re: Fwd: Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses

2012-01-19 Thread Mark Linimon
On Tue, Jan 17, 2012 at 10:35:12AM -0500, Michael Scheidell wrote: > the solution would be for the submitter to work with the maintainer > on a solution, or am I supposed to fix this without reversing this? In general each of us, as committers, is responsible for whatever side- effects of the chan

Re: Fwd: Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses

2012-01-19 Thread Michael Scheidell
On 1/19/12 12:04 PM, Mark Linimon wrote: So if there's breakage, then it needs to be first understood, then dealt with. If there is no other way than the horrible backout/PORTEPOCH dance, then so be it. But the takeaway is that we can't expect the PR submitters, or even port maintainers, to g

Re: Fwd: Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses

2012-01-19 Thread Thomas Zander
On Thu, Jan 19, 2012 at 18:04, Mark Linimon wrote: > So if there's breakage, then it needs to be first understood, then > dealt with.  If there is no other way than the horrible backout/PORTEPOCH > dance, then so be it. That's correct. However I think that in this situation there was no need to

Re: Fwd: Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses

2012-01-19 Thread Matthew Seaman
On 19/01/2012 18:00, Thomas Zander wrote: > It was not the first temporary build problem that one of > the 15k ports has and it certainly won't be the last. 23k Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard

Re: Fwd: Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses

2012-01-19 Thread Thomas Zander
On Thu, Jan 19, 2012 at 19:03, Matthew Seaman wrote: > On 19/01/2012 18:00, Thomas Zander wrote: >>  It was not the first temporary build problem that one of >> the 15k ports has and it certainly won't be the last. > > 23k Sorry, I must have lost count some time in 2005 or so :-) Riggs _