On Lu, 16 iul 12, 14:43:54, Dan Serban wrote:
> On Mon, 16 Jul 2012 12:33:31 +0300
> Andrei POPESCU <andreimpope...@gmail.com> wrote:
> 
> My bad, the guy that made that statement is not the guy at the top of the
> page and missed that comment.  The reality is that it seems that this
> affects more than the singular nvidia driver, though that's simply google-fu
> that may have gone sideways.

I couldn't say, didn't research this as all as my system doesn't seem to 
be affected.
 
> > - wheezy is (still in) testing
> > - the issue is related to the proprietary driver
> 
> Really, the reasoning is IMHO wrong, it affects 3 levels of
> distributions. Squeeze + backports, wheezy .. and sid.  Which by its nature
> will turn off potential Debian users.  No matter who's fault it is.  Hence
> my rant.  I've put up with it so far, but it seems like now (yesterday?)
> would be a good time to get the issue resolved.
> 
> Doesn't Wheezy going into feature freeze mean that no new versions of the
> binary blob would see the light of day in wheezy?

Exactly.

> Or rather, maybe this bug should be tagged RC?
> 
> > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616308#25

I would try a gentle reminder. IMO a good argument for applying the 
workaround ASAP would be to get as much testing as possible before the 
release ;)

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic

Attachment: signature.asc
Description: Digital signature

Reply via email to