Re: List of packages which should probably be Architecture: all
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all again, I just wrote, another, script which downloads the i386 and amd64 'versions' of the packages listed by the script which checks for empty Build-/Depends and compares the md5sums (from control.tar.gz) of both packages. Before I post the results I'd like to clarify that I've noticed that some of the files which differ from arch i386 to arch amd64 are for example the compressed Debian package changelog and similar compressed files. Does anyone has any idea how this could happen? zdiff'ing those files demonstrates that the files are identical. Note that this is the raw output of the script, packages which MUST be arch all (debian-installer is excluded, because of technical reasons) are listed below the list. 2vcard: Files amd64/md5sums and i386/md5sums differ biosquid-dev: Files amd64/md5sums and i386/md5sums differ busybox-static: Files amd64/md5sums and i386/md5sums differ centerim-common: Files amd64/md5sums and i386/md5sums differ Processing cgilib...diff: amd64/md5sums: No such file or directory diff: i386/md5sums: No such file or directory cgilib: chasen-cannadic: Files amd64/md5sums and i386/md5sums differ Processing check... cvm-dev: Files amd64/md5sums and i386/md5sums differ dar-static: Files amd64/md5sums and i386/md5sums differ dballe-common: Files amd64/md5sums and i386/md5sums differ dietlibc-dev: Files amd64/md5sums and i386/md5sums differ drac-dev: Files amd64/md5sums and i386/md5sums differ dvdbackup-dbg: Files amd64/md5sums and i386/md5sums differ e2fsck-static: Files amd64/md5sums and i386/md5sums differ espeak-data: Files amd64/md5sums and i386/md5sums differ etl-dev: Files amd64/md5sums and i386/md5sums differ exim4-dev: Files amd64/md5sums and i386/md5sums differ expectk-tk8.3: Files amd64/md5sums and i386/md5sums differ fgetty: Files amd64/md5sums and i386/md5sums differ fnord: Files amd64/md5sums and i386/md5sums differ freeradius-dbg: Files amd64/md5sums and i386/md5sums differ gcc-3.3-base: Files amd64/md5sums and i386/md5sums differ gcc-3.4-base: Files amd64/md5sums and i386/md5sums differ gcc-4.1-base: Files amd64/md5sums and i386/md5sums differ gcc-4.2-base: Files amd64/md5sums and i386/md5sums differ gcc-4.3-base: Files amd64/md5sums and i386/md5sums differ gcj-4.1-base: Files amd64/md5sums and i386/md5sums differ gcj-4.2-base: Files amd64/md5sums and i386/md5sums differ gftp-common: Files amd64/md5sums and i386/md5sums differ gnat-4.1-base: Files amd64/md5sums and i386/md5sums differ gnat-4.2-base: Files amd64/md5sums and i386/md5sums differ gnu-efi: Files amd64/md5sums and i386/md5sums differ gnustep-common: Files amd64/md5sums and i386/md5sums differ gnustep-make-ogo: Files amd64/md5sums and i386/md5sums differ grub _MUST_ be Architecture: all! identical files: amd64/md5sums i386/md5sums grub-invaders: Files amd64/md5sums and i386/md5sums differ gstreamer0.10-gnonlin-dev: Files amd64/md5sums and i386/md5sums differ hol88-library _MUST_ be Architecture: all! identical files: amd64/md5sums i386/md5sums icewm-common: Files amd64/md5sums and i386/md5sums differ inn2-dev: Files amd64/md5sums and i386/md5sums differ integrit: Files amd64/md5sums and i386/md5sums differ iproute-dev: Files amd64/md5sums and i386/md5sums differ iptables-dev: Files amd64/md5sums and i386/md5sums differ kadu-dev: Files amd64/md5sums and i386/md5sums differ kannel-dev: Files amd64/md5sums and i386/md5sums differ Processing lde... libacovea-dev: Files amd64/md5sums and i386/md5sums differ libagg-dev: Files amd64/md5sums and i386/md5sums differ libaio1: Files amd64/md5sums and i386/md5sums differ libajax5-dev: Files amd64/md5sums and i386/md5sums differ libantlr-dev: Files amd64/md5sums and i386/md5sums differ libatomic-ops-dev: Files amd64/md5sums and i386/md5sums differ libavahi-common-data: Files amd64/md5sums and i386/md5sums differ libbakery-2.3-common: Files amd64/md5sums and i386/md5sums differ libbitcollider-dev: Files amd64/md5sums and i386/md5sums differ libcegui-mk2-doc: Files amd64/md5sums and i386/md5sums differ libchewing3-data: Files amd64/md5sums and i386/md5sums differ libcnf-dev: Files amd64/md5sums and i386/md5sums differ libcurl3-dbg: Files amd64/md5sums and i386/md5sums differ libcwnn-dev: Files amd64/md5sums and i386/md5sums differ libdaemons-ruby1.8: Files amd64/md5sums and i386/md5sums differ libdballe-bufrex-doc: Files amd64/md5sums and i386/md5sums differ libdballe-core-doc: Files amd64/md5sums and i386/md5sums differ libdballe-db-doc: Files amd64/md5sums and i386/md5sums differ libdballe-msg-doc: Files amd64/md5sums and i386/md5sums differ libdds-dev: Files amd64/md5sums and i386/md5sums differ libdiscover1-pic: Files amd64/md5sums and i386/md5sums differ libdts-dev: Files amd64/md5sums and i386/md5sums differ libdvb-dev: Files amd64/md5sums and i386/md5sums differ libflake-dev: Files amd64/md5sums and i386/md5sums differ libgcj-common: Files amd64/md5sums and i386/md5sums differ libgeomview-dev: Files amd64/md5sums
Re: List of packages which should probably be Architecture: all
On 11/01/2008, Raphael Geissert wrote: > Note that this is the raw output of the script, packages which MUST be > arch all (debian-installer is excluded, because of technical reasons) > are listed below the list. *MUST*, ahah. > And here's the list of packages which after comparing the md5sum files > show no reason why they aren't arch all: > > Grub Maintainers <[EMAIL PROTECTED]> >grub Again, there is a very good reason: | /usr/sbin/grub: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.1, dynamically linked (uses shared libs), stripped > Camm Maguire <[EMAIL PROTECTED]> >hol88-library So, again, *how* do you find it possible to list this package as MUST be Architecture: all, while it has things like that inside? | … cut … | /usr/lib/hol88-2.02.19940316/Library/pair/basic_ml.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped | /usr/lib/hol88-2.02.19940316/Library/pair/both1_ml.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped | usr/lib/hol88-2.02.19940316/Library/pair/both2_ml.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped | … cut … > Robert Millan <[EMAIL PROTECTED]> >grub (U) Again… > Masahito Omote <[EMAIL PROTECTED]> >libuim-data Sounds reasonable. > Otavio Salvador <[EMAIL PROTECTED]> >grub (U) > Jason Thomas <[EMAIL PROTECTED]> >grub (U) Again… > As usually, feedback is welcome. Reiterating… -- Cyril Brulebois pgpeKtkuFhZHz.pgp Description: PGP signature
Re: List of packages which should probably be Architecture: all
Cyril Brulebois wrote: > On 11/01/2008, Raphael Geissert wrote: >> Note that this is the raw output of the script, packages which MUST be >> arch all (debian-installer is excluded, because of technical reasons) >> are listed below the list. > > *MUST*, ahah. Sorry, that is more like a "s/MUST/REALLY SHOULD" (strong should? :) > >> And here's the list of packages which after comparing the md5sum files >> show no reason why they aren't arch all: >> >> Grub Maintainers <[EMAIL PROTECTED]> >>grub > > Again, there is a very good reason: > | /usr/sbin/grub: ELF 32-bit LSB executable, Intel 80386, version 1 > | (SYSV), for GNU/Linux 2.6.1, dynamically linked (uses shared libs), > | stripped > >> Camm Maguire <[EMAIL PROTECTED]> >>hol88-library > > So, again, *how* do you find it possible to list this package as MUST be > Architecture: all, while it has things like that inside? > | … cut … > | /usr/lib/hol88-2.02.19940316/Library/pair/basic_ml.o: ELF 32-bit LSB > | relocatable, Intel 80386, version 1 (SYSV), not stripped > | /usr/lib/hol88-2.02.19940316/Library/pair/both1_ml.o: ELF 32-bit LSB > | relocatable, Intel 80386, version 1 (SYSV), not stripped > | usr/lib/hol88-2.02.19940316/Library/pair/both2_ml.o: ELF 32-bit LSB > | relocatable, Intel 80386, version 1 (SYSV), not stripped … cut … > There "MUST" be something wrong with the package then, how is that i386's and amd64's md5sum are exactly the same? >> Robert Millan <[EMAIL PROTECTED]> >>grub (U) > > Again… Did you notice the "(U)"? ;) > >> Masahito Omote <[EMAIL PROTECTED]> >>libuim-data > > Sounds reasonable. > >> Otavio Salvador <[EMAIL PROTECTED]> >>grub (U) >> Jason Thomas <[EMAIL PROTECTED]> >>grub (U) > > Again… > >> As usually, feedback is welcome. > > Reiterating… > Should probably compare i386 and something like armel next time. I'm, again, sorry for those false positives (didn't expect them by comparing md5sums of two different architectures). Cheers, Raphael Geissert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: List of packages which should probably be Architecture: all
On 11/01/2008, Raphael Geissert wrote:
> There "MUST" be something wrong with the package then, how is that
> i386's and amd64's md5sum are exactly the same?
I don't see this that way. There *might* be a problem in your script or
so.
,---[ let's check ]---
| [EMAIL PROTECTED]:/tmp/grub$ wget -q
http://ftp.de.debian.org/debian/pool/main/g/grub/grub_0.97-29_i386.deb
| [EMAIL PROTECTED]:/tmp/grub$ wget -q
http://ftp.de.debian.org/debian/pool/main/g/grub/grub_0.97-29_amd64.deb
| [EMAIL PROTECTED]:/tmp/grub$ for i in amd64 i386; do ar x grub_0.97-29_$i.deb
control.tar.gz; tar xfz control.tar.gz; mv control control.$i; mv md5sums
md5sums.$i; rm control.tar.gz; done
| [EMAIL PROTECTED]:/tmp/grub$ diff -u md5sums.* | diffstat
| md5sums.i386 | 72
+--
| 1 file changed, 36 insertions(+), 36 deletions(-)
`---
Note that the i386 package has the following additional Depends line,
compared to the amd64 one.
| +Depends: libc6 (>= 2.5-5), libncurses5 (>= 5.4-5)
I guess your scripts are somehow assuming that if one has an empty
Depends line, the other has an empty line as well, or something similar.
Back to grub: Unfortunately, there's no amd64 log (source upload along
with the built binaries…), but it might be that ${shlibs:Depends}
weren't computed correctly or so, so that the Depends line was left
empty.
Indeed, checking a cowbuilder build log:
| dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
In an amd64 chroot, looking closer:
| $ file debian/grub/usr/bin/mbchk
| usr/bin/mbchk:ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
for GNU/Linux 2.6.8, statically linked, stripped
That's also the case for the other binaries, so it results apparently
(I'm no grub maintainer at all) correctly in an empty Depends: line.
> Did you notice the "(U)"? ;)
Yes. I actually expected somehow that you could have noticed that it was
about “grub”.
> I'm, again, sorry for those false positives (didn't expect them by
> comparing md5sums of two different architectures).
I'm not blaming because of false positives. I'd expect more common
sense. Either grub is architecture-dependent, being a low-level stuff,
probably written in C (I know, that might sound like a cliché, but…), or
it is just made out of supercowpowered architecture-independent shell
scripts, but then one might wonder a bit. Seen where it belongs in a
boot sequence?
Reviewing such a short list takes some minutes (to compare with the time
you spent on setting up these scripts), using the main measure when it
comes to being “Architecture: all” or “Architecture: any”: its *content*
(but you know that, I've been repeating this from the very beginning).
--
Cyril Brulebois
pgpepixF2jE2I.pgp
Description: PGP signature
