Re: FYI: daily images borked; cause not yet known

2010-02-24 Thread Colin Watson
On Tue, Feb 23, 2010 at 02:30:11PM +0100, Frans Pop wrote:
 On Tuesday 23 February 2010, Frans Pop wrote:
  Hmmm. If I compare the MANIFEST.udebs from testing and my build the only
  thing that jumps out is:
  -   libfribidi0-udeb 0.10.9-1+b1 amd64
  +   libfribidi0-udeb 0.19.2-1 amd64
 
 Confirmed and bug filed (#571044).

It's possible (and arguably sane, on the basis of defence in depth at
least) to work around this in newt.  See:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570581

-- 
Colin Watson   [cjwat...@debian.org]


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100224112832.ga5...@master.debian.org



Re: [Debian-hebrew-package] Bug#571044: FYI: daily images borked; cause not yet known

2010-02-24 Thread Frans Pop
On Wednesday 24 February 2010, أحمد المحمودي wrote:
 So, after reading #570581, is this actually a fribidi or a newt bug ?

It can probably be argued that it's both :-)

In newt for not initializing and in fribidi for not terminating.


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201002241403.46094.elen...@planet.nl



Re: [Debian-hebrew-package] Bug#571044: FYI: daily images borked; cause not yet known

2010-02-24 Thread أحمد المحمودي
Hello,

On Wed, Feb 24, 2010 at 11:28:32AM +, Colin Watson wrote:
 It's possible (and arguably sane, on the basis of defence in depth at
 least) to work around this in newt.  See:
 
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570581
---end quoted text---

I tried Ubuntu's patch right now, and the issue got fixed indeed.

So, after reading #570581, is this actually a fribidi or a newt bug ?

-- 
 ‎أحمد المحمودي (Ahmed El-Mahmoudy)
  Digital design engineer
 GPG KeyID: 0xEDDDA1B7
 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100224125330.gb5...@ants.dhis.net



Re: [Debian-hebrew-package] Bug#571044: FYI: daily images borked; cause not yet known

2010-02-24 Thread Colin Watson
On Wed, Feb 24, 2010 at 02:03:44PM +0100, Frans Pop wrote:
 On Wednesday 24 February 2010, أحمد المحمودي wrote:
  So, after reading #570581, is this actually a fribidi or a newt bug ?
 
 It can probably be argued that it's both :-)
 
 In newt for not initializing and in fribidi for not terminating.

Yes, I think that's my feeling.  Fixing either renders the other one no
longer release-critical, I think.

-- 
Colin Watson   [cjwat...@debian.org]


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100224140048.gq4...@riva.ucam.org



Re: FYI: daily images borked; cause not yet known

2010-02-23 Thread Frans Pop
On Tuesday 23 February 2010, Frans Pop wrote:
 Hmmm. If I compare the MANIFEST.udebs from testing and my build the only
 thing that jumps out is:
 -   libfribidi0-udeb 0.10.9-1+b1 amd64
 +   libfribidi0-udeb 0.19.2-1 amd64

Confirmed and bug filed (#571044).


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201002231430.12306.elen...@planet.nl



FYI: daily images borked; cause not yet known

2010-02-22 Thread Frans Pop
Looks like syslinux has a regression:
http://people.debian.org/~fjp/tmp/d-i/daily-borked1.png

There's also something wrong with the newt frontend:
http://people.debian.org/~fjp/tmp/d-i/daily-borked2.png
http://people.debian.org/~fjp/tmp/d-i/daily-borked3.png

I also saw that a few days ago with another local build, so it's not from 
today's uploads. There have been no new versions of newt and slang, so I'm 
not sure what the cause could be.

Hmmm. If I compare the MANIFEST.udebs from testing and my build the only 
thing that jumps out is:
-   libfribidi0-udeb 0.10.9-1+b1 amd64
+   libfribidi0-udeb 0.19.2-1 amd64

And that looks like a very likely candidate for this breakage.

I'll verify and file bugs.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201002230059.05640.elen...@planet.nl