genext2fs - generates completely broken images on s390

[Debian Bug Importer]

Automatically imported from Debian bug report #266039 http://bugs.debian.org/266039

[Joey Hess (joeyh)]

# Automatically generated email from bts, devscripts version 2.8
tags 266039 d-i

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #266039 http://bugs.debian.org/266039

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 16 Aug 2004 14:41:39 +0200
From: Bastian Blank <email address hidden>
To: <email address hidden>
Subject: genext2fs - generates completely broken images on s390

--17pEHd4RhPHOinZp
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: genext2fs
Version: 1.3-7
Severity: grave

genext2fs generates completely broken images on s390.

| $ genext2fs -d ./tmp/generic/tree -b 5876 -r 0 ./tmp/generic/initrd
| $ fsck.ext2 tmp/generic/initrd =20
| e2fsck 1.35 (28-Feb-2004)
| Note: if there is several inode or block bitmap blocks
| which require relocation, or one part of the inode table
| which must be moved, you may wish to try running e2fsck
| with the '-b 5881' option first. The problem may lie only
| with the primary block group descriptor, and the backup
| block group descriptor may be OK.
|=20
| Block bitmap for group 0 is not in group. (block 50331648)
| Relocate<y>? cancelled!
|=20
| Inode bitmap for group 0 is not in group. (block 67108864)
| Relocate<y>? cancelled!
|=20
| Inode table for group 0 is not in group. (block 83886080)
| WARNING: SEVERE DATA LOSS POSSIBLE.
| Relocate<y>? cancelled!
|=20
| Filesystem did not have a UUID; generating one.
|=20
| $ dumpe2fs tmp/generic/initrd
| dumpe2fs 1.35 (28-Feb-2004)
| Filesystem volume name: <none>
| Last mounted on: <not available>
| Filesystem UUID: <none>
| Filesystem magic number: 0xEF53
| Filesystem revision #: 0 (original)
| Filesystem features: (none)
| Default mount options: (none)
| Filesystem state: clean with errors
| Errors behavior: Unknown (continue)
| Filesystem OS type: Linux
| Inode count: 736
| Block count: 5876
| Reserved block count: 0
| Free blocks: 712
| Free inodes: 435
| First block: 1
| Block size: 1024
| Fragment size: 1024
| Blocks per group: 5880
| Fragments per group: 5880
| Inodes per group: 736
| Inode blocks per group: 92
| Last mount time: n/a
| Last write time: Mon Aug 16 14:37:59 2004
| Mount count: 0
| Maximum mount count: 20
| Last checked: Thu Jan 1 01:00:00 1970
| Check interval: 0 (<none>)
| Reserved blocks uid: 0 (user root)
| Reserved blocks gid: 0 (group root)
| ext2fs_read_bb_inode: Attempt to read block from filesystem resulted in s=
hort read=20
|=20
| Group 0: (Blocks 1-5875)
| Primary superblock at 1, Group descriptors at 2-2
| Block bitmap at 50331648 ([phone]), Inode bitmap at 67108864 (+671088=
63)
| Inode table at 83886080-83886171 ([phone])
| 51202 free blocks, 45825 free inodes, 16896 directories
|=20
| dumpe2fs: tmp/generic/initrd: error reading bitmaps: Can't read an block =
bitmap

This breaks d-i on s390.

Bastian

--=20
Conquest is easy. Control is not.
  -- Kirk, "Mirror, Mirror", stardate unknown

--17pEHd4RhPHOinZp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEG...

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Mon, 16 Aug 2004 14:56:55 +0100
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: tagging 266039

# Automatically generated email from bts, devscripts version 2.8
tags 266039 d-i

[Fabio Massimo Di Nitto (fabbione)]

we don't support s390

[Finn Thain (ft01)]

Hi Bastian,

I don't have an s390 to test on unfortunately, so would you please try
a couple of tests to help me isolate this problem.

- does compiling genext2fs generate any warnings?

- does the following generate fsck errors (apart from the lost+found not
present warning, and the missing volume UUID)?

$ genext2fs -b 5876 -r 0 /tmp/whatever
$ fsck.ext2 /tmp/whatever

I tried this on my celeron, it works ok for me. If it works for you, I may
need the contents of the directory you were storing on the image using "-d
./tmp/generic/tree", if possible. If it works for you, there is a good
chance that the absurd positions of the bitmaps and inode tables in your
bug report are caused by the group descriptor getting hosed.

Regards,

Finn Thain

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 17 Aug 2004 23:38:38 +1000 (EST)
From: Finn Thain <email address hidden>
To: Bastian Blank <email address hidden>
cc: David Kimdon <email address hidden>, <email address hidden>
Subject: Re: genext2fs - generates completely broken images on s390

Hi Bastian,

I don't have an s390 to test on unfortunately, so would you please try
a couple of tests to help me isolate this problem.

- does compiling genext2fs generate any warnings?

- does the following generate fsck errors (apart from the lost+found not
present warning, and the missing volume UUID)?

$ genext2fs -b 5876 -r 0 /tmp/whatever
$ fsck.ext2 /tmp/whatever

I tried this on my celeron, it works ok for me. If it works for you, I may
need the contents of the directory you were storing on the image using "-d
./tmp/generic/tree", if possible. If it works for you, there is a good
chance that the absurd positions of the bitmaps and inode tables in your
bug report are caused by the group descriptor getting hosed.

Regards,

Finn Thain

[Bastian Blank (waldi)]

On Tue, Aug 17, 2004 at 11:38:38PM +1000, Finn Thain wrote:
> I don't have an s390 to test on unfortunately, so would you please try
> a couple of tests to help me isolate this problem.

You have, ask http://db.debian.org/ for the developer machines.

> - does compiling genext2fs generate any warnings?

Ask http://buildd.debian.org/.

> - does the following generate fsck errors (apart from the lost+found not
> present warning, and the missing volume UUID)?
>
> $ genext2fs -b 5876 -r 0 /tmp/whatever
> $ fsck.ext2 /tmp/whatever

| $ genext2fs -b 5876 -r 0 /tmp/whatever
| $ fsck.ext2 /tmp/whatever
| e2fsck 1.35 (28-Feb-2004)
| Note: if there is several inode or block bitmap blocks
| which require relocation, or one part of the inode table
| which must be moved, you may wish to try running e2fsck
| with the '-b 5881' option first. The problem may lie only
| with the primary block group descriptor, and the backup
| block group descriptor may be OK.
|
| Block bitmap for group 0 is not in group. (block 50331648)
| Relocate<y>? cancelled!
|
| Inode bitmap for group 0 is not in group. (block 67108864)
| Relocate<y>? cancelled!
|
| Inode table for group 0 is not in group. (block 83886080)
| WARNING: SEVERE DATA LOSS POSSIBLE.
| Relocate<y>? cancelled!
|
| Filesystem did not have a UUID; generating one.

> I tried this on my celeron, it works ok for me.

You tried it on a 32bit little-endian machine. I try it on a
64bit/31bit big-endian machine.

Bastian

--
Actual war is a very messy business. Very, very messy business.
  -- Kirk, "A Taste of Armageddon", stardate 3193.0

[Finn Thain (ft01)]

On Tue, 17 Aug 2004, Bastian Blank wrote:

> On Tue, Aug 17, 2004 at 11:38:38PM +1000, Finn Thain wrote:
> > I don't have an s390 to test on unfortunately, so would you please try
> > a couple of tests to help me isolate this problem.
>
> You have, ask http://db.debian.org/ for the developer machines.

Cool. David, what's the procedure for obtaining access to raptor?

> > - does compiling genext2fs generate any warnings?
>
> Ask http://buildd.debian.org/.

Very nice. I had no idea that site existed. Interesting to note that make
check fails, but that is not suprising -- it fails where fsck succeeds on
my machines. I'd better look at that too.

> > - does the following generate fsck errors (apart from the lost+found not
> > present warning, and the missing volume UUID)?
> >
> > $ genext2fs -b 5876 -r 0 /tmp/whatever
> > $ fsck.ext2 /tmp/whatever
>
> | $ genext2fs -b 5876 -r 0 /tmp/whatever
> | $ fsck.ext2 /tmp/whatever
> | e2fsck 1.35 (28-Feb-2004)
> | Note: if there is several inode or block bitmap blocks
> | which require relocation, or one part of the inode table
> | which must be moved, you may wish to try running e2fsck
> | with the '-b 5881' option first. The problem may lie only
> | with the primary block group descriptor, and the backup
> | block group descriptor may be OK.
> |
> | Block bitmap for group 0 is not in group. (block 50331648)
> | Relocate<y>? cancelled!
> |
> | Inode bitmap for group 0 is not in group. (block 67108864)
> | Relocate<y>? cancelled!
> |
> | Inode table for group 0 is not in group. (block 83886080)
> | WARNING: SEVERE DATA LOSS POSSIBLE.
> | Relocate<y>? cancelled!
> |
> | Filesystem did not have a UUID; generating one.
>
> > I tried this on my celeron, it works ok for me.
>
> You tried it on a 32bit little-endian machine. I try it on a
> 64bit/31bit big-endian machine.

I also tested on my alpha (64-bit little endian) and it works ...
interesting.

Looks like I'm gonna need that s390 account. Thanks for your help.

-F

> Bastian
>
>

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 17 Aug 2004 19:13:46 +0200
From: Bastian Blank <email address hidden>
To: Finn Thain <email address hidden>
Cc: David Kimdon <email address hidden>, <email address hidden>
Subject: Re: genext2fs - generates completely broken images on s390

--7DO5AaGCk89r4vaK
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 17, 2004 at 11:38:38PM +1000, Finn Thain wrote:
> I don't have an s390 to test on unfortunately, so would you please try
> a couple of tests to help me isolate this problem.

You have, ask http://db.debian.org/ for the developer machines.

> - does compiling genext2fs generate any warnings?

Ask http://buildd.debian.org/.

> - does the following generate fsck errors (apart from the lost+found not
> present warning, and the missing volume UUID)?
>=20
> $ genext2fs -b 5876 -r 0 /tmp/whatever
> $ fsck.ext2 /tmp/whatever

| $ genext2fs -b 5876 -r 0 /tmp/whatever
| $ fsck.ext2 /tmp/whatever
| e2fsck 1.35 (28-Feb-2004)
| Note: if there is several inode or block bitmap blocks
| which require relocation, or one part of the inode table
| which must be moved, you may wish to try running e2fsck
| with the '-b 5881' option first. The problem may lie only
| with the primary block group descriptor, and the backup
| block group descriptor may be OK.
|=20
| Block bitmap for group 0 is not in group. (block 50331648)
| Relocate<y>? cancelled!
|=20
| Inode bitmap for group 0 is not in group. (block 67108864)
| Relocate<y>? cancelled!
|=20
| Inode table for group 0 is not in group. (block 83886080)
| WARNING: SEVERE DATA LOSS POSSIBLE.
| Relocate<y>? cancelled!
|=20
| Filesystem did not have a UUID; generating one.

> I tried this on my celeron, it works ok for me.

You tried it on a 32bit little-endian machine. I try it on a
64bit/31bit big-endian machine.

Bastian

--=20
Actual war is a very messy business. Very, very messy business.
  -- Kirk, "A Taste of Armageddon", stardate 3193.0

--7DO5AaGCk89r4vaK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iEYEARECAAYFAkEiPMoACgkQnw66O/MvCNEuhACeONdGN2Qb23nqCyDExnjywHg8
wB4An3t065XfqaSSK8LDGem3spWO2tYt
=qPHe
-----END PGP SIGNATURE-----

--7DO5AaGCk89r4vaK--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 18 Aug 2004 03:40:18 +1000 (EST)
From: Finn Thain <email address hidden>
To: Bastian Blank <email address hidden>, David Kimdon <email address hidden>
cc: <email address hidden>
Subject: Re: genext2fs - generates completely broken images on s390

On Tue, 17 Aug 2004, Bastian Blank wrote:

> On Tue, Aug 17, 2004 at 11:38:38PM +1000, Finn Thain wrote:
> > I don't have an s390 to test on unfortunately, so would you please try
> > a couple of tests to help me isolate this problem.
>
> You have, ask http://db.debian.org/ for the developer machines.

Cool. David, what's the procedure for obtaining access to raptor?

> > - does compiling genext2fs generate any warnings?
>
> Ask http://buildd.debian.org/.

Very nice. I had no idea that site existed. Interesting to note that make
check fails, but that is not suprising -- it fails where fsck succeeds on
my machines. I'd better look at that too.

> > - does the following generate fsck errors (apart from the lost+found not
> > present warning, and the missing volume UUID)?
> >
> > $ genext2fs -b 5876 -r 0 /tmp/whatever
> > $ fsck.ext2 /tmp/whatever
>
> | $ genext2fs -b 5876 -r 0 /tmp/whatever
> | $ fsck.ext2 /tmp/whatever
> | e2fsck 1.35 (28-Feb-2004)
> | Note: if there is several inode or block bitmap blocks
> | which require relocation, or one part of the inode table
> | which must be moved, you may wish to try running e2fsck
> | with the '-b 5881' option first. The problem may lie only
> | with the primary block group descriptor, and the backup
> | block group descriptor may be OK.
> |
> | Block bitmap for group 0 is not in group. (block 50331648)
> | Relocate<y>? cancelled!
> |
> | Inode bitmap for group 0 is not in group. (block 67108864)
> | Relocate<y>? cancelled!
> |
> | Inode table for group 0 is not in group. (block 83886080)
> | WARNING: SEVERE DATA LOSS POSSIBLE.
> | Relocate<y>? cancelled!
> |
> | Filesystem did not have a UUID; generating one.
>
> > I tried this on my celeron, it works ok for me.
>
> You tried it on a 32bit little-endian machine. I try it on a
> 64bit/31bit big-endian machine.

I also tested on my alpha (64-bit little endian) and it works ...
interesting.

Looks like I'm gonna need that s390 account. Thanks for your help.

-F

> Bastian
>
>

[Finn Thain (ft01)]

Attached is a patch for the make check failure. This s390 bug is one bug
that make check should be able to detect (unless of course it is an e2fsck
bug ;)

David, would it be possible to release this patch to the build servers in
order that the build logs may tell us whether the s390 endianness bug also
afflicts the 32-bit big-endian arch's?

(As I mentioned, this bug doesn't afflict my little-endian 64-bit Alpha,
nor my little-endian 32-bit x86.)

-F

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 18 Aug 2004 14:31:07 +1000 (EST)
From: Finn Thain <email address hidden>
To: David Kimdon <email address hidden>
cc: <email address hidden>
Subject: Re: genext2fs - generates completely broken images on s390

--852659206-1225187162-1092803467=:23567
Content-Type: TEXT/PLAIN; charset=US-ASCII

Attached is a patch for the make check failure. This s390 bug is one bug
that make check should be able to detect (unless of course it is an e2fsck
bug ;)

David, would it be possible to release this patch to the build servers in
order that the build logs may tell us whether the s390 endianness bug also
afflicts the 32-bit big-endian arch's?

(As I mentioned, this bug doesn't afflict my little-endian 64-bit Alpha,
nor my little-endian 32-bit x86.)

-F
--852659206-1225187162-1092803467=:23567
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="genext2fs-1.3-7-fix-make-check.patch"
Content-Transfer-Encoding: BASE64
Content-ID: <email address hidden>
Content-Description:
Content-Disposition: attachment; filename="genext2fs-1.3-7-fix-make-check.patch"

LS0tIGdlbmV4dDJmcy0xLjMub3JpZy9NYWtlZmlsZS5vcmlnCTIwMDQtMDgt
MTggMTQ6MDA6NDIuMDAwMDAwMDAwICsxMDAwDQorKysgZ2VuZXh0MmZzLTEu
My5vcmlnL01ha2VmaWxlCTIwMDQtMDgtMTggMTQ6MDA6NTIuMDAwMDAwMDAw
ICsxMDAwDQpAQCAtMTgsNyArMTgsNyBAQA0KIAkuL2dlbmV4dDJmcyAtYiA0
MDk2IC1kIHRlc3QgZXh0Mi5pbWcNCiAJDQogCW1kNT1gbWQ1c3VtIGV4dDIu
aW1nIHwgY3V0IC1mIDEgLWQgIiAiYDsgXA0KLQlpZiBbICIkJG1kNSIgIT0g
ImE3MzZmY2U2ZDQ1ZWEzNjMxYjAxZmQ3YjhmNjIzMTMxIiBdIDsgdGhlbiBc
DQorCWlmIFsgIiQkbWQ1IiAhPSAiZDA0OGQ4NmMzODFhNGFkMzYxYzk2NTJm
ODZiMWViYTkiIF0gOyB0aGVuIFwNCiAJCWVjaG8gInRlc3QgZmFpbGVkLiI7
IFwNCiAJZWxzZSBcDQogCQllY2hvICJ0ZXN0IHN1Y2NlZWRlZC4iOyBcDQo=

--852659206-1225187162-1092803467=:23567--

[Finn Thain (ft01)]

> David, would it be possible to release this patch to the build servers in
> order that the build logs may tell us whether the s390 endianness bug also
> afflicts the 32-bit big-endian arch's?

Belay that -- I've just been informed that it does affect them.

-F

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 19 Aug 2004 19:29:03 +1000 (EST)
From: Finn Thain <email address hidden>
To: David Kimdon <email address hidden>
cc: <email address hidden>
Subject: Re: genext2fs - generates completely broken images on s390

> David, would it be possible to release this patch to the build servers in
> order that the build logs may tell us whether the s390 endianness bug also
> afflicts the 32-bit big-endian arch's?

Belay that -- I've just been informed that it does affect them.

-F

[Finn Thain (ft01)]

I've attached the fix, tested on ppc, debian m68k, alpha and i686. Turns
out that the group descriptor byte swapping code was not being run on the
last group due to miscalculation of the number of groups.

The patch includes an improved make check fix. Please disregard the
previous patch I sent for make check. Make check should now pass in a BSD
user land (works on Mac OS X).

Thanks to Wouter Verhelst for providing a big-endian box for testing.

-F

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 21 Aug 2004 18:10:36 +1000 (EST)
From: Finn Thain <email address hidden>
To: David Kimdon <email address hidden>
cc: <email address hidden>

--852659206-761411136-1093075836=:10722
Content-Type: TEXT/PLAIN; charset=US-ASCII

I've attached the fix, tested on ppc, debian m68k, alpha and i686. Turns
out that the group descriptor byte swapping code was not being run on the
last group due to miscalculation of the number of groups.

The patch includes an improved make check fix. Please disregard the
previous patch I sent for make check. Make check should now pass in a BSD
user land (works on Mac OS X).

Thanks to Wouter Verhelst for providing a big-endian box for testing.

-F
--852659206-761411136-1093075836=:10722
Content-Type: TEXT/PLAIN; charset=US-ASCII;
 name="genext2fs_1.3-7-big-endian-and-make-check-fixes.diff"
Content-Transfer-Encoding: BASE64
Content-ID: <email address hidden>
Content-Description:
Content-Disposition: attachment; filename="genext2fs_1.3-7-big-endian-and-make-check-fixes.diff"

ZGlmZiAtTnVyIGdlbmV4dDJmcy0xLjMub3JpZy1vcmlnL01ha2VmaWxlIGdl
bmV4dDJmcy0xLjMub3JpZy9NYWtlZmlsZQ0KLS0tIGdlbmV4dDJmcy0xLjMu
b3JpZy1vcmlnL01ha2VmaWxlCVNhdCBBdWcgMjEgMTc6MTY6NTIgMjAwNA0K
KysrIGdlbmV4dDJmcy0xLjMub3JpZy9NYWtlZmlsZQlTYXQgQXVnIDIxIDE3
OjMwOjM1IDIwMDQNCkBAIC0xNywxMCArMTcsMTYgQEANCiAJZGQgaWY9L2Rl
di96ZXJvIG9mPXRlc3QvemVybyBjb3VudD0xDQogCS4vZ2VuZXh0MmZzIC1i
IDQwOTYgLWQgdGVzdCBleHQyLmltZw0KIAkNCi0JbWQ1PWBtZDVzdW0gZXh0
Mi5pbWcgfCBjdXQgLWYgMSAtZCAiICJgOyBcDQotCWlmIFsgIiQkbWQ1IiAh
PSAiYTczNmZjZTZkNDVlYTM2MzFiMDFmZDdiOGY2MjMxMzEiIF0gOyB0aGVu
IFwNCi0JCWVjaG8gInRlc3QgZmFpbGVkLiI7IFwNCi0JZWxzZSBcDQorCW1k
NV9jb3JyZWN0PWQwNDhkODZjMzgxYTRhZDM2MWM5NjUyZjg2YjFlYmE5OyBc
DQorCW1kNV90ZXN0ZWQ9YG1kNXN1bSBleHQyLmltZyAyPi9kZXYvbnVsbCB8
IGN1dCAtZiAxIC1kICIgImA7IFwNCisJaWYgWyAiJCRtZDVfdGVzdGVkIiA9
ICIkJG1kNV9jb3JyZWN0IiBdIDsgdGhlbiBcDQogCQllY2hvICJ0ZXN0IHN1
Y2NlZWRlZC4iOyBcDQorCWVsc2UgXA0KKwkJbWQ1X3Rlc3RlZD1gbWQ1IGV4
dDIuaW1nIDI+L2Rldi9udWxsIHwgY3V0IC1mIDQgLWQgIiAiYDsgXA0KKwkJ
aWYgWyAiJCRtZDVfdGVzdGVkIiA9ICIkJG1kNV9jb3JyZWN0IiBdIDsgdGhl
biBcDQorCQkJZWNobyAidGVzdCBzdWNjZWVkZWQuIjsgXA0KKwkJZWxzZSBc
DQorCQkJZWNobyAidGVzdCBmYWlsZWQuIjsgXA0KKwkJZmkgXA0KIAlmaQ0K
IAkNCmRpZmYgLU51ciBnZW5leHQyZnMtMS4zLm9yaWctb3JpZy9nZW5leHQy
ZnMuYyBnZW5leHQyZnMtMS4zLm9yaWcvZ2VuZXh0MmZzLmMNCi0tLSBnZW5l
eHQyZnMtMS4zLm9yaWctb3JpZy9nZW5leHQyZnMuYwlTYXQgQXVnIDIxIDE3
OjE2OjUyIDIwMDQNCisrKyBnZW5leHQyZnMtMS4zLm9yaWcvZ2VuZXh0MmZz
LmMJU2F0IEF1ZyAyMSAxNjo1OTo1OSAyMDA0DQpAQCAtMTY0LDcgKzE2NCw3
IEBADQogLyogRGVmaW5lcyBmb3IgYWNjZXNzaW5nIGdyb3VwIGRldGFpbHMg
Ki8NCiANCiAvLyBOdW1iZXIgb2YgZ3JvdXBzIGluIHRoZSBmaWxlc3lzdGVt
DQotI2RlZmluZSBHUlBfTkJHUk9VUFMoZnMpICggKChmcyktPnNiLnNfYmxv
Y2tzX2NvdW50LTEpLyhmcyktPnNiLnNfYmxvY2tzX3Blcl9ncm91cCApDQor
I2RlZmluZSBHUlBfTkJHUk9VUFMoZnMpICggKChmcyktPnNiLnNfYmxvY2tz
X2NvdW50KyhmcyktPnNiLnNfYmxvY2tzX3Blcl9ncm91cC0xKS8oZnMpLT5z
Yi5zX2Jsb2Nrc19wZXJfZ3JvdXAgKQ0KIA0KIC8vIEdldCBncm91cCBibG9j
ayBiaXRtYXAgKGJibSkgZ2l2ZW4gdGhlIGdyb3VwIG51bWJlcg0KICNkZWZp
bmUgR1JQX0dFVF9HUk9VUF9CQk0oZnMsZ3JwKSAoIGdldF9ibGsoKGZzKSwo
ZnMpLT5nZFsoZ3JwKV0uYmdfYmxvY2tfYml0bWFwKSApDQo=

--8526...

[Thomas Hood (jdthood-yahoo)]

tags 266039 patch

[Debian Bug Importer (debzilla)]

Message-Id: <20040823171905.C330910D680@localhost>
Date: Mon, 23 Aug 2004 19:19:05 +0200 (CEST)
From: <email address hidden> (Thomas Hood)
To: <email address hidden>
Subject: tagging 266039

tags 266039 patch

[Joshua Kwan (joshk)]

tag 266039 + fixed

quit

This message was generated automatically in response to a
non-maintainer upload. The .changes file follows.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 24 Aug 2004 19:09:01 -0700
Source: genext2fs
Binary: genext2fs
Architecture: source sparc
Version: 1.3-7.1
Distribution: unstable
Urgency: high
Maintainer: David Kimdon <email address hidden>
Changed-By: Joshua Kwan <email address hidden>
Description:
 genext2fs - ext2 filesystem generator for embedded systems
Closes: 266039
Changes:
 genext2fs (1.3-7.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Apply patch from Finn Thain to fix byteswapping code issues that broke
     d-i on several arches. Thanks. (Closes: #266039)
Files:
 56e3463f13456bad14f08b6d437dca3a 1259 admin optional genext2fs_1.3-7.1.dsc
 c01903e9035b52ad5a99fc85d689397a 10162 admin optional genext2fs_1.3-7.1.diff.gz
 c955b7d83907a58b4d95b51905aa625b 17800 admin optional genext2fs_1.3-7.1_sparc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: http://triplehelix.org/~joshk/pubkey_gpg.asc

iQIVAwUBQSv1fKOILr94RG8mAQIu1BAAtn9V4aPpTqyiRkK2VSpe7nnbhIrpL1Qf
kW8Ah4J/IR5sWWf/p65WAKk39swjZxSrn7KzWt5tJuK1zZLTIXvjtER54phspdCF
dVI2QZsExZ+yeKYV9mOc+hvEwQKzSwJlQXx8l/nNfvnby1hAtKWxL5m1q2RUmQYR
9RzZdSzpvSE3Qtecxqmx/ShZxdJMJNDQvSWNP+/yihfWUKBW9YFDYq2reY1QvGqM
HHyoK05RW+fn/Sjfn/qJuHOcZNC1blzrkRCTgqpO8mzneT4bUj8Wt7+pIawI+tgE
fxXLH9sHF9d8iaJocqanMY1yKDMdcefMKSeVKU8g2p4CeoxRWqVXbPhK1H7kVYWx
A+NvJV0EFWuMgN/bywJjckjopsDZ2OZpX9lD80tyuPufaYp/oSkQiYu4IPMaoHhN
hL1Z8wtmzWcUZcfHN6ey1l1dmZLiv/GFfo4OqXbw1RaqFh/D+ACC79N5Z8rzGkC5
dL5FHG6/w3zWCYSBOfGpgkO3jtXnI2UWBp/MboOFSl800D30db17qY5Dkuy/afx6
jLISs8Rx634mX/+Io9KAQfPxQKGwmhTYEGOIMXTc5YqIBqsLivLv2iWlrYtCejKY
BYfyDxZLgD7WRx1rDELkXhi318n8R+NFgFZFt94is03VtOWXx9DtBxjxwyl3DeIi
Uq1NvEnGBCM=
=5o/A
-----END PGP SIGNATURE-----

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Tue, 24 Aug 2004 23:47:05 -0400
From: Joshua Kwan <email address hidden>
To: <email address hidden>
Cc: Joshua Kwan <email address hidden>, David Kimdon <email address hidden>
Subject: Fixed in NMU of genext2fs 1.3-7.1

tag 266039 + fixed

quit

This message was generated automatically in response to a
non-maintainer upload. The .changes file follows.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 24 Aug 2004 19:09:01 -0700
Source: genext2fs
Binary: genext2fs
Architecture: source sparc
Version: 1.3-7.1
Distribution: unstable
Urgency: high
Maintainer: David Kimdon <email address hidden>
Changed-By: Joshua Kwan <email address hidden>
Description:
 genext2fs - ext2 filesystem generator for embedded systems
Closes: 266039
Changes:
 genext2fs (1.3-7.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Apply patch from Finn Thain to fix byteswapping code issues that broke
     d-i on several arches. Thanks. (Closes: #266039)
Files:
 56e3463f13456bad14f08b6d437dca3a 1259 admin optional genext2fs_1.3-7.1.dsc
 c01903e9035b52ad5a99fc85d689397a 10162 admin optional genext2fs_1.3-7.1.diff.gz
 c955b7d83907a58b4d95b51905aa625b 17800 admin optional genext2fs_1.3-7.1_sparc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: http://triplehelix.org/~joshk/pubkey_gpg.asc

iQIVAwUBQSv1fKOILr94RG8mAQIu1BAAtn9V4aPpTqyiRkK2VSpe7nnbhIrpL1Qf
kW8Ah4J/IR5sWWf/p65WAKk39swjZxSrn7KzWt5tJuK1zZLTIXvjtER54phspdCF
dVI2QZsExZ+yeKYV9mOc+hvEwQKzSwJlQXx8l/nNfvnby1hAtKWxL5m1q2RUmQYR
9RzZdSzpvSE3Qtecxqmx/ShZxdJMJNDQvSWNP+/yihfWUKBW9YFDYq2reY1QvGqM
HHyoK05RW+fn/Sjfn/qJuHOcZNC1blzrkRCTgqpO8mzneT4bUj8Wt7+pIawI+tgE
fxXLH9sHF9d8iaJocqanMY1yKDMdcefMKSeVKU8g2p4CeoxRWqVXbPhK1H7kVYWx
A+NvJV0EFWuMgN/bywJjckjopsDZ2OZpX9lD80tyuPufaYp/oSkQiYu4IPMaoHhN
hL1Z8wtmzWcUZcfHN6ey1l1dmZLiv/GFfo4OqXbw1RaqFh/D+ACC79N5Z8rzGkC5
dL5FHG6/w3zWCYSBOfGpgkO3jtXnI2UWBp/MboOFSl800D30db17qY5Dkuy/afx6
jLISs8Rx634mX/+Io9KAQfPxQKGwmhTYEGOIMXTc5YqIBqsLivLv2iWlrYtCejKY
BYfyDxZLgD7WRx1rDELkXhi318n8R+NFgFZFt94is03VtOWXx9DtBxjxwyl3DeIi
Uq1NvEnGBCM=
=5o/A
-----END PGP SIGNATURE-----

[David Kimdon (dwhedon)]

This bug can be closed.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 29 Nov 2005 13:48:02 -0800
From: David Kimdon <email address hidden>
To: <email address hidden>
Subject: ack NMU (genext2fs - generates completely broken images on s390)

This bug can be closed.