Michael and I all agree that the experimental
package is the only viable candidate for Wheezy. But you will lose that
option if you do not upload it very, very soon. The freeze happens in
the next few days.
Ron
--
To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org
with a subject
, is not in my usual
definition of wisdom, and the crux of my disagreement with the
crusade that Chris has embarked on here.
Since he didn't bother to wait for Josh and I to discuss that
further, now we're here ...
Sorry,
Ron
--
To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org
with a subject
On Thu, Jul 19, 2012 at 12:55:59PM +0100, Ian Jackson wrote:
Ron writes (Re: #682010 re celt and mumble referred to the TC):
You understand this is a fairly arbitrary 'daily' snapshot of an
experimental research codec, from ~2.5 years ago, that nobody has
looked at since that day
with problems as they come up.
Since Ron is listed as co-maintainer for mumble do you feel you have
the authority to do this ? I imagine Ron would object, so you would
in any case need a TC ruling to arbitrate between you.
*sigh* Why would you imagine this?
I already told you I have
.
There may be some way that people can build their own from source or
override the 'security' feature on their windows machine to install
one from someone else, but someone who actually uses windows will
probably have to answer that if you need more details.
Ron
[We might want to avoid cc'ing
On Fri, Jul 20, 2012 at 08:14:48AM -0400, Chris Knadle wrote:
On Friday, July 20, 2012 07:54:21, Ian Jackson wrote:
Chris Knadle writes (Re: Bug#682010: re celt and mumble referred to the
TC):
On Thursday, July 19, 2012 19:07:52, Ron wrote:
...
What we'd like to do
On Fri, Jul 20, 2012 at 08:49:54AM -0400, Chris Knadle wrote:
On Friday, July 20, 2012 08:32:01, Ron wrote:
On Fri, Jul 20, 2012 at 08:14:48AM -0400, Chris Knadle wrote:
On Friday, July 20, 2012 07:54:21, Ian Jackson wrote:
[…]
How will this interact with mumble in other distros, who
On Fri, Jul 20, 2012 at 03:25:00PM +0100, Ian Jackson wrote:
Ron writes (Bug#682010: re celt and mumble referred to the TC):
Making a binary release for windows users is bottlenecked behind Thorvald
too
right now. The problem goes something like this:
This is not relevant
sure the mumble servers
can communicate with?
* Involved parties
** chris.kna...@coredump.us, Ron r...@debian.org, 682...@bugs.debian.org,
Nicos Gollan gt...@spearhead.de, Thorvald Natvig thorv...@natvig.com
The above is my current understanding of this bug. Please correct
anything
of the
dependency from ices2 to roaraudio.
I have seen this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676541
and the package changelog:
* Stop build-depending on libroar-dev or suggesting roaraudio-server.
Requested by Ron Lee.
But I don't seem to be able to find
On Fri, Jul 20, 2012 at 02:48:07PM -0700, Don Armstrong wrote:
I've updated the summary with the suggested changes (at the end).
On Sat, 21 Jul 2012, Ron wrote:
I think that's roughly right. If there's anything more people need
clarified or answered, just ask.
[...]
And I'm still
...
That was an exchange from today, which I only saw just now.
Like this wasn't complicated enough already,
Ron :/
--
To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120721013556.gv18
On Sat, Jul 21, 2012 at 03:46:34PM -0400, Chris Knadle wrote:
The issue I have now is that The Plan that Ron and Thorvald have come up with
Will Not Work, depending what the _goal_ is. If the goal is to be able to
interoperate with the existing *server* base [which was exactly why this came
On Mon, Jul 23, 2012 at 03:38:44PM +0100, Ian Jackson wrote:
Ron writes (Bug#682010: [mumble] Communication failures due to CELT codec
library removal):
That point is currently still true. Every existing client has the ability
to *decode* speex if speex packets arrive.
The only thing
the risks and tells me they are happy doing that, then I'm happy
to make that happen with no further delay.
Is there anything I've still missed?
Cheers,
Ron
--
To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Mon, Jul 23, 2012 at 02:38:19PM -0400, Chris Knadle wrote:
On Monday, July 23, 2012 13:16:55, Ron wrote:
On Mon, Jul 23, 2012 at 03:38:44PM +0100, Ian Jackson wrote:
[…]
Maybe that is true for the gamers, but when I asked I didn't get
any confirmation that this was what the problem
On Tue, Jul 24, 2012 at 01:17:10PM +0100, Ian Jackson wrote:
Ron writes (Re: Bug#682010: [mumble] Communication failures due to CELT
codec library removal):
My primary concern is with the fact we would be shipping very complicated
code, that only about 3 people in the world really
On Tue, Jul 24, 2012 at 06:25:04PM +0100, Ian Jackson wrote:
Ron writes (Bug#682010: [mumble] Communication failures due to CELT codec
library removal):
I understand your line of thinking there, and for 99% of the code in the
world, I'd be in complete agreement. I'm not someone who
thorough testing of this code told me that
they thought it wasn't ...
rra Backing up a little bit: Assume that we all decide that it's
okay to reintroduce celt. Do we actually have someone who is
willing to do the work of reintroducing celt into the archive?
I mean, is Ron
for Jessie. It's definitely desirable
to have this on a stable system, since the lock-step requirement of
m-a makes it rather more painful to keep this all working on an
unstable system where packages are changing rapidly (and because
stable deps are kind of an important thing too :)
Cheers,
Ron
,
at this late stage of the Jessie release.
Ron
--
To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141122162145.gu29...@hex.shelbyville.oz
On Sat, Nov 22, 2014 at 08:51:41PM +, Dimitri John Ledkov wrote:
On 22 November 2014 at 16:21, Ron r...@debian.org wrote:
Dimitri wrote:
Thus multiarch cross tooling is not so relevant for fresh bootstraps,
and/or targeting non-debian architectures, or otherwise incomplete
systems
On Tue, Nov 08, 2016 at 02:52:29PM +, Ian Jackson wrote:
> Ron writes ("Bug#841294: Overrule maintainer of "global" to package a new
> upstream version"):
> > I think you missed the bit about "comprehending the problem and building
> > consensus o
On Mon, Nov 07, 2016 at 12:09:21PM -0800, Nikolaus Rath wrote:
> On Nov 07 2016, Ron <r...@debian.org> wrote:
>
> > I've taken the time to repeat this all again now, because regardless
> > of how it got here, I actually have some faith in the new face of the
> &
On Thu, Nov 03, 2016 at 09:20:30AM +0100, Philip Hands wrote:
> Ron <r...@debian.org> writes:
> >
> > I can try to clarify that if there's a question in your mind that
> > you don't think I touched on there.
>
> The question that remains is what you actually inten
On Sun, Nov 06, 2016 at 05:09:56PM -0800, Nikolaus Rath wrote:
> On Nov 06 2016, Ron <r...@debian.org> wrote:
> > On Thu, Nov 03, 2016 at 09:20:30AM +0100, Philip Hands wrote:
> >> Ron <r...@debian.org> writes:
> >> >
> >> > I can
On Sat, Oct 22, 2016 at 05:41:54PM +0200, Vincent Bernat wrote:
> ❦ 22 octobre 2016 14:44 +1030, Ron <r...@debian.org> :
>
> > It seems fair to assume that you aren't seriously asking them to
> > endorse the idea of chmod 777 as an acceptable interface for
> > dis
On Sun, Oct 23, 2016 at 08:48:53PM +0200, Tollef Fog Heen wrote:
> ]] Ron
>
> > I'm appalled at the status quo. My concern is that we don't make
> > that even worse with uninformed decisions. In the absence of good
> > information, sometimes the best thing to do is b
On Tue, Oct 25, 2016 at 09:03:40AM +0200, Philip Hands wrote:
> Ron <r...@debian.org> writes:
>
> ...
> > That's basically why "just nuke htags now" is starting to look like
> > a viable, and even sensible, option. But it's tricky to know who
> >
istance is what makes a river crooked, so if
we don't want this to end up as some sort of bug infested billabong
spreading disease to the people who use it, then we will need some
better answers than just "blindly package and upload a new upstream
version" - because the minimal work needed to do just that is not the
actual problem here.
Cheers,
Ron
of us have important things
to do. So if you don't have anything actually useful to contribute,
then please just go away and leave this to the adults to discuss in
a mature and sensible fashion.
Thank you.
Ron
decade after its upstream declared it an
obsolete solution, when kms finally made it impossible to keep it
working - so I don't underestimate what some people might cling to.
Cheers,
Ron
ould be fixed in sid now though.
Good bug reports are the foundation for getting things fixed, so
thanks for setting a good example there.
Cheers,
Ron
satisfying or technically astute rationale, if that's all it boils
down to. I'd like to have something a bit more substantial and fair
than that to offer the people who'd get burned without notice by this.
Cheers,
Ron
e that this is the most
> reasonable
> outcome, given the current situation. This means that global gets updated to
> the
> latest version, with a NEWS message stating that htags functionality has been
> removed and that users that care about htags should install global5 instead.
>
>
On Mon, Dec 05, 2016 at 10:13:05PM +0100, Philip Hands wrote:
> Ron <r...@debian.org> writes:
>
> > I'm not insisting that's what we should do. But it's certainly an
> > option, and it dodges the bullet of having to say "Sucks to be you"
> > without
On Thu, Dec 08, 2016 at 02:39:44PM +0100, Vincent Bernat wrote:
> ❦ 8 décembre 2016 23:32 +1030, Ron <r...@debian.org> :
>
> > One is whatever it is that the third-party ggtags wrapper needs, which
> > aiui is what Vincent and Punit are most annoyed about. But I don't
&
On Thu, Dec 08, 2016 at 03:41:14PM +0100, Vincent Bernat wrote:
> ❦ 9 décembre 2016 00:32 +1030, Ron <r...@debian.org> :
>
> > How much am I supposed to hound you when you give a non-answer?
>
> Maybe assume good faith and tell me that the answer doesn't fit yo
On Thu, Dec 08, 2016 at 06:24:32PM +0100, Didier 'OdyX' Raboud wrote:
> Le jeudi, 8 décembre 2016, 18.14:12 h CET Tollef Fog Heen a écrit :
> > Using open like in the code snippet above is pretty much inexcusable in
> > this day and age.
>
> Fair enough, thanks for the
feel like goldilocks, first I'm bad because I didn't respond enough,
now I'm bad because I respond too much.
But apparently, I should have actually said just a little more in this
one too, to explain to you how perl works :) So I'll do that now!
> Le jeudi, 8 décembre 2016, 23.32:44 h CET
On Fri, Dec 09, 2016 at 11:58:02AM +0100, Didier 'OdyX' Raboud wrote:
> Le vendredi, 9 décembre 2016, 04.55:20 h CET Ron a écrit :
> > > If you haven't yet, I urge you to use our standard interface to report
> > > such
> > > bugs; please make sure issues like this on
On Fri, Dec 09, 2016 at 05:13:48PM +0100, Didier 'OdyX' Raboud wrote:
>
> What I see as fundamental difference here was your use of #196762 as a single
> point of contact for the problem you were facing with groff 1.19, in which
> you
> explained, commented and followed up on what the problem
Hi Sam,
On Wed, Nov 30, 2016 at 11:39:08AM -0500, Sam Hartman wrote:
> >>>>> "Ron" == Ron <r...@debian.org> writes:
>
> Ron> Hi OdyX,
>
> Ron> On Wed, Nov 16, 2016 at 03:23:47PM +0100, Didier 'OdyX' Raboud wrote:
> >> Hi
43 matches
Mail list logo
