* Martin-Éric Racine [Mon, 18 Aug 2008 21:08:12 +0300]:
> On Mon, Aug 18, 2008 at 9:03 PM, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> > * Martin-Éric Racine [Sun, 17 Aug 2008 00:59:46 +0300]:
> >> Well, whatever. I could create a 2.10.1-1lenny1, just for the sake of
> >> reverting those changes
On Mon, Aug 18, 2008 at 9:03 PM, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> * Martin-Éric Racine [Sun, 17 Aug 2008 00:59:46 +0300]:
>
>> Well, whatever. I could create a 2.10.1-1lenny1, just for the sake of
>> reverting those changes and even though reverting them is pointless,
>> then push that s
* Martin-Éric Racine [Sun, 17 Aug 2008 00:59:46 +0300]:
> Well, whatever. I could create a 2.10.1-1lenny1, just for the sake of
> reverting those changes and even though reverting them is pointless,
> then push that somewhere else. lenny-update-proposed?
Uploading to unstable is preferred.
--
On Sat, Aug 16, 2008 at 10:37 PM, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> * Martin-Éric Racine [Sat, 16 Aug 2008 22:01:50 +0300]:
>
>> On 8/16/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
>> > Dude, the guidelines say "changes for release goals, if they're not
>> > invasive", not "not invasive
* Martin-Éric Racine [Sat, 16 Aug 2008 22:01:50 +0300]:
> On 8/16/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> > Dude, the guidelines say "changes for release goals, if they're not
> > invasive", not "not invasive changes, for $whatever they are".
> I still haven't heard in what way this chang
On 8/16/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> Dude, the guidelines say "changes for release goals, if they're not
> invasive", not "not invasive changes, for $whatever they are".
I still haven't heard in what way this change constitutes something
invasive. It's a simple two-liner and its
* Martin-Éric Racine [Sat, 16 Aug 2008 18:02:06 +0300]:
> On 8/16/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> > * Martin-Éric Racine [Sat, 16 Aug 2008 10:21:11 +0300]:
> > > Actually, now is precisely the right time to do this. It had been
> > > requested for a long time, but I had postponed
On 8/16/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> * Martin-Éric Racine [Sat, 16 Aug 2008 10:21:11 +0300]:
>
>
> > Actually, now is precisely the right time to do this. It had been
> > requested for a long time, but I had postponed doing this until Lenny
> > would be close to release, so as
* Martin-Éric Racine [Sat, 16 Aug 2008 10:21:11 +0300]:
> Actually, now is precisely the right time to do this. It had been
> requested for a long time, but I had postponed doing this until Lenny
> would be close to release, so as to avoid breaking backportability.
> Now that Lenny is about to bec
On 8/16/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> * Martin-Éric Racine [Fri, 15 Aug 2008 15:25:09 +0300]:
>
>
> > On 8/15/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> > > * Martin-Éric Racine [Thu, 14 Aug 2008 11:30:31 +0300]:
>
>
> > > > Upstream is making a minor bugfix release (2.10.1
* Martin-Éric Racine [Fri, 15 Aug 2008 15:25:09 +0300]:
> On 8/15/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> > * Martin-Éric Racine [Thu, 14 Aug 2008 11:30:31 +0300]:
> > > Upstream is making a minor bugfix release (2.10.1) to address this
> > > issue and another one, tomorrow. If it's ok
On 8/15/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> * Martin-Éric Racine [Thu, 14 Aug 2008 11:30:31 +0300]:
>
>
> > Upstream is making a minor bugfix release (2.10.1) to address this
> > issue and another one, tomorrow. If it's okay, I'd rather package and
> > upload that to unstable, rather
* Martin-Éric Racine [Thu, 14 Aug 2008 11:30:31 +0300]:
> Upstream is making a minor bugfix release (2.10.1) to address this
> issue and another one, tomorrow. If it's okay, I'd rather package and
> upload that to unstable, rather than hand-pick patches.
If the minor issue has minor code changes
On 8/9/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> * Martin-Éric Racine [Sat, 09 Aug 2008 10:03:56 +0300]:
>
>
> > On 8/7/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> > > * Martin-Éric Racine [Wed, 06 Aug 2008 17:53:31 +0300]:
> > > > 1) Release a patched GEODE 2.10.0 package
>
> > > This
* Martin-Éric Racine [Sat, 09 Aug 2008 10:03:56 +0300]:
> On 8/7/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> > * Martin-Éric Racine [Wed, 06 Aug 2008 17:53:31 +0300]:
> > > 2) Wait until the GEODE 2.12.0 including that fix is released
> > No, this is not possible at all. Zero chances.
> > >
On 8/7/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> * Martin-Éric Racine [Wed, 06 Aug 2008 17:53:31 +0300]:
> > 2) Wait until the GEODE 2.12.0 including that fix is released
>
> No, this is not possible at all. Zero chances.
>
> > 1) Release a patched GEODE 2.10.0 package
>
> This would be acce
* Martin-Éric Racine [Wed, 06 Aug 2008 17:53:31 +0300]:
> Greetings,
Hello,
> 2) Wait until the GEODE 2.12.0 including that fix is released
> (mid-September, according to upstream milestone) and package that for
> Lenny.
No, this is not possible at all. Zero chances.
> 1) Release a patched GEO
Greetings,
A bug has been found that only affects some of the hardware supported
by xserver-xorg-video-geode and causes a hardware freeze during X
launch, because of a hard-coded value in the DDC probing code. It only
affects GX2 variants of the Geode; LX variants are not affected.
Upstream is aw
18 matches
Mail list logo
