Bug#563972: patch to fix fontmatrix on armel

2010-03-09 Thread Michael Casadevall
On Tue, Mar 09, 2010 at 04:58:11PM +0100, Gerfried Fuchs wrote:
>   Hi!
> 
> * Michael Casadevall  [2010-01-06 19:32:55 CET]:
> > Package: fontmatrix
> > Severity: serious
> > Tags: patch
> > Justification: no longer builds from source
> 
>  When you state "no longer" - did it build before properly? I.e. I
> wonder wether a proper found version is missing in this bugreport and
> wether the bug actually does affect the stable release (lenny).
> 
>  If not I would want to close it for lenny - unfortunately I don't have
> the arm hardware to check it there, though lenny was released with a
> version of fontmatrix that seem to have build at some point, at least
> three years ago. This is too long for a timegap for me to just close it
> and let the security team (or whoever would need to update the package
> in stable) over this issue again.
> 
>  Thanks,
> Rhonda

Lenny released with fontmatrix 0.4 which built on arm, and armel. It was later
builds that started to FTBFS, although I don't remember the first version that
started to have trouble. There's been no released (and still supported)
version of Debian that hasn't shipped with fontmatrix built on arm/armel.
Michael




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#563972: patch to fix fontmatrix on armel

2010-01-06 Thread Michael Casadevall
Package: fontmatrix
Severity: serious
Tags: patch
Justification: no longer builds from source

I've recently fixed fontmatrix to build on armel on Ubuntu, and I'm passing 
along
the patch to help recitify the FTBFS. The underlying issue is that on ARM, qreal
is typedef'ed to float versus a double so when using qMax between a double and 
a qreal,
you need to cast the call so the compiler can find the proper function.

Index: fontmatrix-0.6.0/src/fminfodisplay.cpp
===
--- fontmatrix-0.6.0.orig/src/fminfodisplay.cpp 2010-01-06 09:22:22.677196249 
-0500
+++ fontmatrix-0.6.0/src/fminfodisplay.cpp  2010-01-06 09:22:54.437193376 
-0500
@@ -152,7 +152,7 @@
GlyphToSVGHelper gtsh ( gpi->path(), tf );
svg += gtsh.getSVGPath() + "\n";
horOffset += 
gpi->data(GLYPH_DATA_HADVANCE).toDouble() * scaleFactor;
-   maxHeight = qMax ( gtsh.getRect().height(), 
maxHeight );
+   maxHeight = qMax ( 
gtsh.getRect().height(), maxHeight );
tf.translate( 
gpi->data(GLYPH_DATA_HADVANCE).toDouble()  * scaleFactor,0 );
delete gpi;
}

-- System Information:
Debian Release: squeeze/sid
  APT prefers lucid-updates
  APT policy: (500, 'lucid-updates'), (500, 'lucid-security'), (500, 'lucid')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-16-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#533428: is bug fixed? nope

2009-09-11 Thread Michael Casadevall
reassign 533428 calibre
thanks

This is a problem with calibre; sip doesn't promise stable APIs at the
moment, so calibre must be re-uploaded for each sip4/python-qt4
upload; this is a problem with any python module that also includes C
code (as there are no sonames to break libraries). There is a plan to
implement a dh_sip (or a more generic solution) to permamently resolve
this issue, but at this time, this package requires an NMU. In
addition, I spoke with Martin Pitt who was unable to reproduce the
issue; its possible the maintainer binary was built in an out-of-date
chroot that caused this issue.
Michael



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#539689: [lenny] icedove and iceowel segfaults on mipsel

2009-08-02 Thread Michael Casadevall
Package: icedove
Version: 2.0.0.22-0lenny1
Severity: serious

On a stable lenny/mipsel installation, icedove and iceowl  currently 
segfaults when executed from the commandline. Output is as follwos:

mcasadev...@genesis:~/bin$ icedove
/usr/lib/icedove/run-mozilla.sh: line 131: 17689 Segmentation fault  
"$prog" ${1+"$@"}

I'll attempt to provide a more useful backtrace and such once I have the 
system fully setup. As an additional note, iceweasel is unaffected.
Michael

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: mipsel (mips64)

Kernel: Linux 2.6.27.1-ls2f-lemote-yl-di
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages icedove depends on:
ii  debianutils2.30  Miscellaneous utilities specific t
ii  fontconfig 2.6.0-3   generic font configuration library
ii  libatk1.0-01.22.0-1  The ATK accessibility toolkit
ii  libc6  2.7-18GNU C Library: Shared libraries
ii  libcairo2  1.6.4-7   The Cairo 2D vector graphics libra
ii  libfontconfig1 2.6.0-3   generic font configuration library
ii  libfreetype6   2.3.7-2+lenny1FreeType 2 font engine, shared lib
ii  libgcc11:4.3.2-1.1   GCC support library
ii  libglib2.0-0   2.16.6-2  The GLib library of C routines
ii  libgtk2.0-02.12.12-1~lenny1  The GTK+ graphical user interface 
ii  libhunspell-1.2-0  1.2.6-1   spell checker and morphological an
ii  libjpeg62  6b-14 The Independent JPEG Group's JPEG 
ii  libnspr4-0d4.7.1-4   NetScape Portable Runtime Library
ii  libnss3-1d 3.12.0-6  Network Security Service libraries
ii  libpango1.0-0  1.20.5-5  Layout and rendering of internatio
ii  libpng12-0 1.2.27-2+lenny2   PNG library - runtime
ii  libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3
ii  libx11-6   2:1.1.5-2 X11 client-side library
ii  libxft22.1.12-3  FreeType-based font drawing librar
ii  libxinerama1   2:1.0.3-2 X11 Xinerama extension library
ii  libxrender11:0.9.4-2 X Rendering Extension client libra
ii  libxt6 1:1.0.5-3 X11 toolkit intrinsics library
ii  psmisc 22.6-1Utilities that use the proc filesy
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

icedove recommends no packages.

Versions of packages icedove suggests:
pn  icedove-gnome-support  (no description available)
pn  latex-xft-fonts(no description available)
ii  libthai0  0.1.9-4Thai language support library

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#505101: Ah, missed the previous bug ...

2008-11-09 Thread Michael Casadevall
retitle "libupsclient-dev points to /usr/lib not /lib"
thankyou

Sorry, I overlooked that the libraries in /lib are intentional. The
problem is now that the files in -dev point to /usr/lib, vs /lib
making anything that builds against libupsclient-dev crash and burn.
Michael



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#505101: libupsclient1 ends up in /lib, not /usr/lib

2008-11-09 Thread Michael Casadevall
Subject: libupsclient1 ends up in /lib, not /usr/lib
Package: libupsclient1
Severity: serious

libupsclient1 installs its shared libraries into /lib, not /usr/lib

[EMAIL PROTECTED]:/# dpkg -L libupsclient1
/lib/libupsclient.so.1.0.0

It appears all thats needed to fix is a change in the rules on 131-132
to change debian/lib to debian/usr/lib.
Michael

-- System Information:
Debian Release: lenny/sid
  APT prefers jaunty-updates
  APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500, 'jaunty')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.27-7-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#491590: Uh, SILLY is not compiled into the package

2008-10-24 Thread Michael Casadevall
found #491590 0.6.1-1
thankyou

http://buildd.debian.org/fetch.cgi?&pkg=cegui-mk2&ver=0.6.1-1&arch=amd64&stamp=1224450974&file=log
- if you check the build log, SILLY is not compiled into the cegui
package. The SILLY library isn't even packaged for Debian!!

Here's the lines from the log:

checking for SILLY... no
configure: Image loading via SILLY by OpenGL renderer disabled



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#500807: Looking at the backtrace ...

2008-10-19 Thread Michael Casadevall
I took a quick glance at the backtraces. The first problem looks like
Icedove got a piece of mail with an invalid MINE type which is
crashing Icedove, which is a bug that should be sent upstream. If you
can isolate the email thats causing that crash, that would be vastly
helpful. The second one just seems to be that Icedove stalled
downloading a large attachment; if you had left it running, it likely
would have finished (although I agree a progress bar would have been
nice).

Icedove 2.0.0.17 was just uploaded to unstable today, it may fix your
issue. If you can test with that version, it would be greatly
appreciated.
Michael



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#478717: ruby1.9/hppa problems

2008-10-15 Thread Michael Casadevall
It should be noted that in my run, the test suite completed with only
two failures.
Michael

On Wed, Oct 15, 2008 at 5:16 AM, Lucas Nussbaum
<[EMAIL PROTECTED]> wrote:
> On 15/10/08 at 04:16 -0400, Michael Casadevall wrote:
>> Working with lucas, I've successfully been able to build ruby1.9. The
>> issue is related to NPTL support in the kernel. NPTL on HPPA is
>> extremely unstable it seems, and currently causes anything that uses
>> to threads to go boom under some cirmstances. Some versions of the
>> kernel however appear to work. I had a successful build with a machine
>> with the following uname
>>
>> Linux gsyprf11 2.6.22.19 #1 SMP Sat Apr 5 18:55:33 PDT 2008 parisc64 
>> GNU/Linux
>>
>> The test suite passes successfully, although it does take an extremely
>> long time to build. cpuinfo is as follows:
>>
>> processor : 0
>> cpu family: PA-RISC 2.0
>> cpu   : PA8700 (PCX-W2)
>> cpu MHz   : 750.00
>> model : 9000/800/A500-7X
>> model name: Crescendo 750 W2
>> hversion  : 0x5e30
>> sversion  : 0x0491
>> I-cache   : 768 KB
>> D-cache   : 1536 KB (WB, direct mapped)
>> ITLB entries  : 240
>> DTLB entries  : 240 - shared with ITLB
>> bogomips  : 1495.04
>> software id   : 824930630
>>
>> processor : 1
>> cpu family: PA-RISC 2.0
>> cpu   : PA8700 (PCX-W2)
>> cpu MHz   : 750.00
>> model : 9000/800/A500-7X
>> model name: Crescendo 750 W2
>> hversion  : 0x5e30
>> sversion  : 0x0491
>> I-cache   : 768 KB
>> D-cache   : 1536 KB (WB, direct mapped)
>> ITLB entries  : 240
>> DTLB entries  : 240 - shared with ITLB
>> bogomips  : 1495.04
>> software id   : 824930630
>>
>> I uploaded the results to ~ncommander-guest/ruby1.9 on alioth. The
>> 219kb build.log is available. Built with debuild -B -b
>> Michael
>
> Following Michael's steps, I successfully built ruby1.9 on mkhppa3, one
> of Thibaut Varene's boxes, using the following kernel:
> Linux mkhppa3 2.6.22.19 #1 SMP Tue Oct 14 14:22:05 CEST 2008 parisc64
> GNU/Linux
>
> Before that, I tried to build using lenny's 2.6.26. I ran into several
> WARN_ON()s and hard locks, and never managed to build ruby1.9 on hppa
> using lenny's kernel. This kernel is clearly not ready for a release,
> but it's not my call to make...
>
> After the build, ruby's test suite mostly passed (some thread tests just
> blocked, so there's still a problem with threading on hppa). So I had to
> disable it in debian/rules. I think that the status is "good enough" for
> lenny/hppa. And this should allow to build the other missing packages
> too.
>
> Dato, is it fine if I upload those binaries to unstable? How should I
> proceed to make them migrate to testing? I think they will magically
> appear in testing since the source is already in testing, but I'm not
> sure now.
>
> Thanks a lot to Michael for hinting about 2.6.22.19 :-)
> --
> | Lucas Nussbaum
> | [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
> | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#491930: ruby1.9/hppa problems

2008-10-15 Thread Michael Casadevall
Working with lucas, I've successfully been able to build ruby1.9. The
issue is related to NPTL support in the kernel. NPTL on HPPA is
extremely unstable it seems, and currently causes anything that uses
to threads to go boom under some cirmstances. Some versions of the
kernel however appear to work. I had a successful build with a machine
with the following uname

Linux gsyprf11 2.6.22.19 #1 SMP Sat Apr 5 18:55:33 PDT 2008 parisc64 GNU/Linux

The test suite passes successfully, although it does take an extremely
long time to build. cpuinfo is as follows:

processor   : 0
cpu family  : PA-RISC 2.0
cpu : PA8700 (PCX-W2)
cpu MHz : 750.00
model   : 9000/800/A500-7X
model name  : Crescendo 750 W2
hversion: 0x5e30
sversion: 0x0491
I-cache : 768 KB
D-cache : 1536 KB (WB, direct mapped)
ITLB entries: 240
DTLB entries: 240 - shared with ITLB
bogomips: 1495.04
software id : 824930630

processor   : 1
cpu family  : PA-RISC 2.0
cpu : PA8700 (PCX-W2)
cpu MHz : 750.00
model   : 9000/800/A500-7X
model name  : Crescendo 750 W2
hversion: 0x5e30
sversion: 0x0491
I-cache : 768 KB
D-cache : 1536 KB (WB, direct mapped)
ITLB entries: 240
DTLB entries: 240 - shared with ITLB
bogomips: 1495.04
software id : 824930630

I uploaded the results to ~ncommander-guest/ruby1.9 on alioth. The
219kb build.log is available. Built with debuild -B -b
Michael

On Tue, Oct 14, 2008 at 6:47 PM, Lucas Nussbaum
<[EMAIL PROTECTED]> wrote:
> forcemerge 478717 491930
> thanks
>
> Hi,
>
> I'm merging #478717 and #491930, since they are about the same issue
> (ruby1.9's recent versions not being available on hppa).
>
> I did some tests. The last upstream revision of ruby1.9 that I could
> successfully compile was rev 11437 (Sun Dec 31 07:24:56 2006 +).
> This was just before the merge of YARV, so YARV is a good suspect.
> Unfortunately, the YARV merge was done all at once, so it's not possible
> to bissect it.
>
> Open questions:
> - is there a later version that is buildable on Debian? That would be
>  great, because if would exclude a bug in the big YARV merge. The first
>  "bad" version I could find (with the failure that is reported in this
>  bug) is rev 12544 (Fri Jun 15 03:27:33 2007 +). This is confirmed
>  by http://buildd.debian.org/build.php?arch=hppa&pkg=ruby1.9
>
> - 1.9.0.0-2 was built and uploaded, but the log is not available on
>  buildd.d.o, so it was probably a manual upload. The .changes is signed
>  by LaMont Jones <[EMAIL PROTECTED]>, and the package works fine
>  according to some basic tests. Lamont, do you remember how you
>  managed to build that package? Did you use an old system/kernel?
>
> Thank you,
> --
> | Lucas Nussbaum
> | [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
> | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#501411: Took a quick look at this

2008-10-09 Thread Michael Casadevall
Here's the relevant script section:


### Test Per Object PostLoopCallbacks

socketpair(Rdr, Wtr, AF_UNIX, SOCK_STREAM, PF_UNSPEC);
my $reader = Danga::Socket->new(\*Rdr);
my $writer = Danga::Socket->new(\*Wtr);
print "# reader: $reader\n# writer: $writer\n";
my $reader_fired = 0;
my $writer_fired = 0;
$reader->SetPostLoopCallback(sub {
my Danga::Socket $self = shift;
ok(1, "reader PLC fired");
$reader_fired++;
return $reader_fired && $writer_fired ? 0 : 1;
});
$writer->SetPostLoopCallback(sub {
my Danga::Socket $self = shift;
ok(1, "writer PLC fired");
$writer_fired++;
return $reader_fired && $writer_fired ? 0 : 1;
});
Danga::Socket->EventLoop;

I poked through the source of Danga, and didn't see anything obvious
on whats causing this behavior 
Michael

On Fri, Oct 10, 2008 at 2:23 AM, Russ Allbery <[EMAIL PROTECTED]> wrote:
> "Michael Casadevall" <[EMAIL PROTECTED]> writes:
>
>> Taking a closer look at the FTBFS, and the code, it seems the code is
>> trying to open two sockets, and then send data between both of them; I
>> misspoke when I said the internet, and should have said network
>> sockets, I'm not sure if the grid computers would prevent a socket
>> from being opened properly, looking at the test code, it is not
>> specifying a port (although that might not be necessary with
>> socketpair.
>>
>> socketpair(Rdr, Wtr, AF_UNIX, SOCK_STREAM, PF_UNSPEC);
>>
>> It's opening with the sockets with those flags. Any ideas?
>
> This is basically equivalent to pipe() but with larger buffers on many
> hosts.  If that's all the code is doing, it really should succeed.  It
> doesn't require any particular network configuration on the host.
>
> --
> Russ Allbery ([EMAIL PROTECTED])   <http://www.eyrie.org/~eagle/>
>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#501411: Took a quick look at this

2008-10-09 Thread Michael Casadevall
Taking a closer look at the FTBFS, and the code, it seems the code is
trying to open two sockets, and then send data between both of them; I
misspoke when I said the internet, and should have said network
sockets, I'm not sure if the grid computers would prevent a socket
from being opened properly, looking at the test code, it is not
specifying a port (although that might not be necessary with
socketpair.

socketpair(Rdr, Wtr, AF_UNIX, SOCK_STREAM, PF_UNSPEC);

It's opening with the sockets with those flags. Any ideas?
Michael

On Fri, Oct 10, 2008 at 1:29 AM, Luk Claes <[EMAIL PROTECTED]> wrote:
> Michael Casadevall wrote:
>> I took a quick look at this, its possible this FTBFS on the grid
>> simply because the internet isn't available. I rebuilt it a few times,
>> and it always passed. If it possible that this is just a random fluke,
>> and this bug can be closed, or at least downgraded?
>
> A package should not need the internet to get built. So if that's the
> case, closing or downgrading the bug is not an option.
>
> Cheers
>
> Luk
>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#501411: Took a quick look at this

2008-10-09 Thread Michael Casadevall
I took a quick look at this, its possible this FTBFS on the grid
simply because the internet isn't available. I rebuilt it a few times,
and it always passed. If it possible that this is just a random fluke,
and this bug can be closed, or at least downgraded?
Michael



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#500320: Patch to fix

2008-10-09 Thread Michael Casadevall
tags 500320 +patch +confirmed
thankyou

This FTBFS is easily fixable by adding intltool to the build-deps, and
makes the package buildable on i386 and amd64.

I've created an NMU, and I'll upload as a convience to you if desired:
http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=gnome-build
Michael



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#501413: Patch to correct intermittent FTBFS in test suite

2008-10-08 Thread Michael Casadevall
tags 501413 patch fixed-in-experimental fixed-upstream
thankyou

I've did done research into this bug, and I backported the fix from
the current mysql 5.0.x release. dpatch attached. I can upload this as
an NMU if you wish. The experimental version appears to be not
affected.

Here's the upstream bug
Michael

#! /bin/sh /usr/share/dpatch/dpatch-run
## 94_rpl_test_failure.dpatch by Michael Casadevall <[EMAIL PROTECTED]>
##
## DP: Bug MySQL #30209 - race condition with the rpl_packet test in some cases.
## DP: Fix backported from current MySQL test suite

@DPATCH@
diff -urNad mysql-dfsg-5.0-5.0.51a~/mysql-test/r/rpl_packet.result
mysql-dfsg-5.0-5.0.51a/mysql-test/r/rpl_packet.result
--- mysql-dfsg-5.0-5.0.51a~/mysql-test/r/rpl_packet.result  2008-01-11
10:23:41.0 -0500
+++ mysql-dfsg-5.0-5.0.51a/mysql-test/r/rpl_packet.result   2008-10-08
20:19:05.0 -0400
@@ -21,6 +21,37 @@
 START SLAVE;
 CREATE TABLe `t1` (`f1` LONGTEXT) ENGINE=MyISAM;
 INSERT INTO `t1`(`f1`) VALUES
('2048');
-SHOW STATUS LIKE 'Slave_running';
-Variable_name  Value
-Slave_running  OFF
+show slave status;
+Slave_IO_State #
+Master_Host127.0.0.1
+Master_Userroot
+Master_PortMASTER_MYPORT
+Connect_Retry  1
+Master_Log_Filemaster-bin.01
+Read_Master_Log_Pos2138
+Relay_Log_File #
+Relay_Log_Pos  #
+Relay_Master_Log_File  master-bin.01
+Slave_IO_Running   No
+Slave_SQL_Running  #
+Replicate_Do_DB
+Replicate_Ignore_DB
+Replicate_Do_Table 
+Replicate_Ignore_Table 
+Replicate_Wild_Do_Table
+Replicate_Wild_Ignore_Table
+Last_Errno 0
+Last_Error 
+Skip_Counter   0
+Exec_Master_Log_Pos2138
+Relay_Log_Space#
+Until_ConditionNone
+Until_Log_File 
+Until_Log_Pos  0
+Master_SSL_Allowed No
+Master_SSL_CA_File 
+Master_SSL_CA_Path 
+Master_SSL_Cert
+Master_SSL_Cipher  
+Master_SSL_Key 
+Seconds_Behind_Master  #
diff -urNad mysql-dfsg-5.0-5.0.51a~/mysql-test/t/rpl_packet.test
mysql-dfsg-5.0-5.0.51a/mysql-test/t/rpl_packet.test
--- mysql-dfsg-5.0-5.0.51a~/mysql-test/t/rpl_packet.test2008-01-11
10:23:21.0 -0500
+++ mysql-dfsg-5.0-5.0.51a/mysql-test/t/rpl_packet.test 2008-10-08
20:20:17.0 -0400
@@ -64,9 +64,11 @@
 INSERT INTO `t1`(`f1`) VALUES
('a

Bug#494316: Updated package

2008-10-07 Thread Michael Casadevall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I've created a NMU to handle updating this package should the original
maintainer need help with the update. The changelog is as follows:

libsmbios (2.0.3-0.1) unstable; urgency=high

  * Non-maintainer upload.
  * New upstream release for compatibility with
linux kernel 2.6.26 (Closes: #494316)
  * Changed libsmbios1 -> 2 due to soname change (ABI break)
  * Dropped libsmbiosxml1 - removed upstream (no rdepends in Debian)
  * Removed automatic libtool upgrades as it horribly, horribly, horribly
breaks the build (Closes: #491795)
  * Added symbol file for new library soname
  * Bumped standards version to 3.8.0
  * Added dependency on chrpath (used to remoth rpaths on amd64/ia64)

 -- Michael Casadevall   Tue, 07 Oct 2008 19:28:04 -0400


libsmbiosxml which was dropped had no rdepends outside of this source package

libsmbios1 has one rdepend on hal. hal builds and links correctly
against libsmbios2, it simply will require a binNMU to finish the
transition. Its confirmed to build successfully on i386 and amd64.

The 0.13.13 -> 2.0.3 package has been tested on amd64, and upgrades
without any issues from 0.13.13 to 2.0.3. the libsmbios1 package can
be removed once hal is rebuilt pending this upload.

debdiff is attached between the two versions. It should be noted that
the amount of source changes is actually relatively smaller then it
might first seem since a large amount of the changes comes from
autotools being updated, and libsmbiosxml being removed (which
accounts for 25% of the diff size alone not counting autotools
changes)

Upstream Changelog:
* Wed Jan 9 2008 Michael E Brown  - 2.0.0
- - ABI incompatible, minor API changes
- - sync up libsmbios soname with version #
- - move binaries to /usr/sbin as they are only runnable by root
- - drop libsmbiosxml lib as it was mostly unused.
- - drop autotools generated files out of git and add autogen.sh
- - drop tokenCtl binary-- pysmbios has a *much* improved version

* Wed Aug 22 2007 Michael E Brown  - 0.13.9
- - Fix a couple of failure-to-check-return on fopen. most were unit-test code
  only, but two or three were in regular code.
- - Add hinting to the memory class, so that it can intelligently close /dev/mem
  file handle when it is not needed (which is most of the time). it only
  leaves it open when it is scanning, so speed is not impacted.

Notes:
There are some other outstanding lintian issues with this package that
were not addressed, but they are at best minor, and are not within the
scope of the NMU. If the maintainer of this package however would like
to see fixes for them in addition to everything else, then I'd be glad
to help.

The watch file is currently broken (goes with above).

I have no intention to upload (nor ability, since I'm still a NM) this
package without either approval from the release team, or approval
from the maintainer. I created this updated package as a convince to
the former should it be necessary.

The package itself is available here on mentors:
http://mentors.debian.net/debian/pool/main/l/libsmbios/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org

iEYEARECAAYFAkjsKBkACgkQpblTBJ2i2ptIlQCeL223G767RX5dZkFGD2/a8FWV
2BUAoI/rw3WSjbbkehKSxi/3iZiX3S8S
=71s5
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#433716: file: File doesn't compile on Debian GNU/Hurd

2007-07-18 Thread Michael Casadevall
Package: file
Version: 4.21-1
Severity: serious
Tags: patch
Justification: no longer builds from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

File doesn't compile on Hurd due to a dependence on PIPE_BUF.
The patch uses pathconf to get _PC_PIPE_BUF which is unlimited
(-1) on Hurd.
Michael

- -- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.3.99/Hurd-0.3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages file depends on:
ii  libc0.3 2.5-11+hurd.1GNU C Library: Shared libraries
ii  libmagic1   4.21-1   File type determination library us
ii  zlib1g  1:1.2.3.3.dfsg-5 compression library - runtime

file recommends no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU)

iD8DBQFGm0PVV/FBeJ6jsZQRAtR0AJ94myWQM4de0R+uegXqiGn4BmLV4gCeM/BH
n5uqDxLXfG4lkoZZHUBzioc=
=emZJ
-END PGP SIGNATURE-
*** file-4.21/src/magic.c	2007/07/16 09:10:24	1.1
--- file-4.21/src/magic.c	2007/07/16 09:41:40
***
*** 58,63 
--- 58,68 
  #include 
  #endif
  
+ #ifndef PIPE_BUF
+ // Get the PIPE_BUF from pathconf
+ #define PIPE_BUF pathconf(".", _PC_PIPE_BUF)
+ #endif
+ 
  #include 		/* for byte swapping */
  
  #include "patchlevel.h"