The rest are text files (or gnu message catalogs) and should generally be grep'able and traceable in text form. Some of the compressed archives may also be obviously harmless, but I haven't tested, yet.
I also wonder how many of them don't actually end up in the binary package and could be dropped from a dfsg-tarball. Is there an easy way to find out?
I believe the relevant files that need looking into are (please add others if you think this list is incomplete)
./eurofile/ src/wuauth/ sigfix. c areacode. dat firmware/ eicon_firm. tgz pc_eu_ca. bin loadpg. bin pc_1t_ca. bin examples/ beep.msg. example examples/ standard. msg.example examples/ timeout. msg.example firmware/ bip1120. btl tools/zone/ at/1024/ zred.bz2 tools/zone/ at/pta/ zoneall. pta.bz2 tools/zone/ at/pta/ zred.pta. bz2 tools/zone/ at/1001/ zred.bz2 tools/zone/ at/1004/ zred.bz2 tools/zone/ at/1007/ zred.bz2 tools/zone/ at/1066/ zred.bz2 tools/zone/ at/uta/ zred.uta. bz2 tools/zone/ nl/kpn/ zred.bz2 tools/zone/ nl/kpn/ zoneall. bz2 tools/zone/ de/01033/ zred.dtag. bz2 tools/zone/ de/01033/ zneu.de9. bz2 tools/zone/ de/01033/ Verzonung. dat.bz2 tools/telrate/ *.{jpg, gif}
./areacode/
./eicon/
./icn/firmware/
./icn/firmware/
./icn/firmware/
./hisax/ISAR.BIN
./vbox/
./vbox/
./vbox/
./act2000/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
./isdnlog/
The rest are text files (or gnu message catalogs) and should generally be grep'able and traceable in text form. Some of the compressed archives may also be obviously harmless, but I haven't tested, yet.
I also wonder how many of them don't actually end up in the binary package and could be dropped from a dfsg-tarball. Is there an easy way to find out?