Processing of gcc-4.4_4.4.5-15_amd64.changes
gcc-4.4_4.4.5-15_amd64.changes uploaded successfully to localhost along with the files: gcc-4.4_4.4.5-15.dsc gcc-4.4_4.4.5-15.diff.gz gcc-4.4-source_4.4.5-15_all.deb libstdc++6-4.4-doc_4.4.5-15_all.deb gcc-4.4-locales_4.4.5-15_all.deb gcc-4.4-base_4.4.5-15_amd64.deb cpp-4.4_4.4.5-15_amd64.deb protoize_4.4.5-15_amd64.deb libmudflap0-4.4-dev_4.4.5-15_amd64.deb gobjc++-4.4-multilib_4.4.5-15_amd64.deb gobjc++-4.4_4.4.5-15_amd64.deb gobjc-4.4-multilib_4.4.5-15_amd64.deb gobjc-4.4_4.4.5-15_amd64.deb g++-4.4-multilib_4.4.5-15_amd64.deb g++-4.4_4.4.5-15_amd64.deb lib32stdc++6-4.4-dbg_4.4.5-15_amd64.deb libstdc++6-4.4-dev_4.4.5-15_amd64.deb libstdc++6-4.4-pic_4.4.5-15_amd64.deb libstdc++6-4.4-dbg_4.4.5-15_amd64.deb gfortran-4.4-multilib_4.4.5-15_amd64.deb gfortran-4.4_4.4.5-15_amd64.deb gcc-4.4-multilib_4.4.5-15_amd64.deb gcc-4.4_4.4.5-15_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q4sbu-0004yi...@franck.debian.org
gcc-4.4_4.4.5-15_amd64.changes ACCEPTED into unstable
Accepted: cpp-4.4_4.4.5-15_amd64.deb to main/g/gcc-4.4/cpp-4.4_4.4.5-15_amd64.deb g++-4.4-multilib_4.4.5-15_amd64.deb to main/g/gcc-4.4/g++-4.4-multilib_4.4.5-15_amd64.deb g++-4.4_4.4.5-15_amd64.deb to main/g/gcc-4.4/g++-4.4_4.4.5-15_amd64.deb gcc-4.4-base_4.4.5-15_amd64.deb to main/g/gcc-4.4/gcc-4.4-base_4.4.5-15_amd64.deb gcc-4.4-locales_4.4.5-15_all.deb to main/g/gcc-4.4/gcc-4.4-locales_4.4.5-15_all.deb gcc-4.4-multilib_4.4.5-15_amd64.deb to main/g/gcc-4.4/gcc-4.4-multilib_4.4.5-15_amd64.deb gcc-4.4-source_4.4.5-15_all.deb to main/g/gcc-4.4/gcc-4.4-source_4.4.5-15_all.deb gcc-4.4_4.4.5-15.diff.gz to main/g/gcc-4.4/gcc-4.4_4.4.5-15.diff.gz gcc-4.4_4.4.5-15.dsc to main/g/gcc-4.4/gcc-4.4_4.4.5-15.dsc gcc-4.4_4.4.5-15_amd64.deb to main/g/gcc-4.4/gcc-4.4_4.4.5-15_amd64.deb gfortran-4.4-multilib_4.4.5-15_amd64.deb to main/g/gcc-4.4/gfortran-4.4-multilib_4.4.5-15_amd64.deb gfortran-4.4_4.4.5-15_amd64.deb to main/g/gcc-4.4/gfortran-4.4_4.4.5-15_amd64.deb gobjc++-4.4-multilib_4.4.5-15_amd64.deb to main/g/gcc-4.4/gobjc++-4.4-multilib_4.4.5-15_amd64.deb gobjc++-4.4_4.4.5-15_amd64.deb to main/g/gcc-4.4/gobjc++-4.4_4.4.5-15_amd64.deb gobjc-4.4-multilib_4.4.5-15_amd64.deb to main/g/gcc-4.4/gobjc-4.4-multilib_4.4.5-15_amd64.deb gobjc-4.4_4.4.5-15_amd64.deb to main/g/gcc-4.4/gobjc-4.4_4.4.5-15_amd64.deb lib32stdc++6-4.4-dbg_4.4.5-15_amd64.deb to main/g/gcc-4.4/lib32stdc++6-4.4-dbg_4.4.5-15_amd64.deb libmudflap0-4.4-dev_4.4.5-15_amd64.deb to main/g/gcc-4.4/libmudflap0-4.4-dev_4.4.5-15_amd64.deb libstdc++6-4.4-dbg_4.4.5-15_amd64.deb to main/g/gcc-4.4/libstdc++6-4.4-dbg_4.4.5-15_amd64.deb libstdc++6-4.4-dev_4.4.5-15_amd64.deb to main/g/gcc-4.4/libstdc++6-4.4-dev_4.4.5-15_amd64.deb libstdc++6-4.4-doc_4.4.5-15_all.deb to main/g/gcc-4.4/libstdc++6-4.4-doc_4.4.5-15_all.deb libstdc++6-4.4-pic_4.4.5-15_amd64.deb to main/g/gcc-4.4/libstdc++6-4.4-pic_4.4.5-15_amd64.deb protoize_4.4.5-15_amd64.deb to main/g/gcc-4.4/protoize_4.4.5-15_amd64.deb Override entries for your package: cpp-4.4_4.4.5-15_amd64.deb - optional interpreters g++-4.4-multilib_4.4.5-15_amd64.deb - optional devel g++-4.4_4.4.5-15_amd64.deb - optional devel gcc-4.4-base_4.4.5-15_amd64.deb - required libs gcc-4.4-locales_4.4.5-15_all.deb - optional devel gcc-4.4-multilib_4.4.5-15_amd64.deb - optional devel gcc-4.4-source_4.4.5-15_all.deb - optional devel gcc-4.4_4.4.5-15.dsc - source devel gcc-4.4_4.4.5-15_amd64.deb - optional devel gfortran-4.4-multilib_4.4.5-15_amd64.deb - optional devel gfortran-4.4_4.4.5-15_amd64.deb - optional devel gobjc++-4.4-multilib_4.4.5-15_amd64.deb - optional devel gobjc++-4.4_4.4.5-15_amd64.deb - optional devel gobjc-4.4-multilib_4.4.5-15_amd64.deb - optional devel gobjc-4.4_4.4.5-15_amd64.deb - optional devel lib32stdc++6-4.4-dbg_4.4.5-15_amd64.deb - extra debug libmudflap0-4.4-dev_4.4.5-15_amd64.deb - optional libdevel libstdc++6-4.4-dbg_4.4.5-15_amd64.deb - extra debug libstdc++6-4.4-dev_4.4.5-15_amd64.deb - optional libdevel libstdc++6-4.4-doc_4.4.5-15_all.deb - optional doc libstdc++6-4.4-pic_4.4.5-15_amd64.deb - extra libdevel protoize_4.4.5-15_amd64.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q4sf7-0005xi...@franck.debian.org
Bug#583837: marked as done (gdc-4.1: "circular initialization dependency" depending on link order)
Your message dated Wed, 30 Mar 2011 11:06:44 + with message-id and subject line Bug#620116: Removed package(s) from unstable has caused the Debian Bug report #583837, regarding gdc-4.1: "circular initialization dependency" depending on link order to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 583837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdc-4.1 Version: 0.25-4.1.2-23.2 Severity: normal Torus Trooper (0.22.dfsg1-4) fails to start with this error message depending on the order in which the object files were linked: "Error: circular initialization dependency with module abagames.tt.shape" This command produces a working binary: gdc -o torus-trooper src/abagames/tt/camera.o src/abagames/tt/boot.o \ src/abagames/tt/barrage.o src/abagames/tt/bullettarget.o \ src/abagames/tt/replay.o src/abagames/tt/ship.o src/abagames/tt/particle.o \ src/abagames/tt/tunnel.o src/abagames/tt/enemy.o \ src/abagames/tt/bulletactor.o src/abagames/tt/gamemanager.o \ src/abagames/tt/screen.o src/abagames/tt/title.o \ src/abagames/tt/stagemanager.o src/abagames/tt/bulletactorpool.o \ src/abagames/tt/shot.o src/abagames/tt/prefmanager.o \ src/abagames/tt/bulletimpl.o src/abagames/tt/letter.o \ src/abagames/tt/soundmanager.o src/abagames/tt/floatletter.o \ src/abagames/tt/shape.o src/abagames/util/actor.o src/abagames/util/rand.o \ src/abagames/util/sdl/input.o src/abagames/util/sdl/sound.o \ src/abagames/util/sdl/pad.o src/abagames/util/sdl/screen3d.o \ src/abagames/util/sdl/mainloop.o src/abagames/util/sdl/gamemanager.o \ src/abagames/util/sdl/screen.o src/abagames/util/sdl/recordablepad.o \ src/abagames/util/sdl/luminous.o src/abagames/util/sdl/sdlexception.o \ src/abagames/util/sdl/displaylist.o src/abagames/util/sdl/texture.o \ src/abagames/util/iterator.o src/abagames/util/bulletml/bullet.o \ src/abagames/util/bulletml/bulletsmanager.o src/abagames/util/tokenizer.o \ src/abagames/util/prefmanager.o src/abagames/util/vector.o \ src/abagames/util/logger.o import/SDL_video.o import/SDL_mixer.o \ -lbulletml -lSDL -lGL -lGLU -lSDL_mixer And this command produces a broken binary: gdc -o torus-trooper src/abagames/tt/bulletactorpool.o src/abagames/tt/boot.o \ src/abagames/tt/soundmanager.o src/abagames/tt/prefmanager.o \ src/abagames/tt/title.o src/abagames/tt/shot.o src/abagames/tt/screen.o \ src/abagames/tt/bulletimpl.o src/abagames/tt/enemy.o \ src/abagames/tt/stagemanager.o src/abagames/tt/bulletactor.o \ src/abagames/tt/camera.o src/abagames/tt/particle.o src/abagames/tt/shape.o \ src/abagames/tt/replay.o src/abagames/tt/tunnel.o src/abagames/tt/letter.o \ src/abagames/tt/barrage.o src/abagames/tt/ship.o \ src/abagames/tt/gamemanager.o src/abagames/tt/bullettarget.o \ src/abagames/tt/floatletter.o src/abagames/util/logger.o \ src/abagames/util/bulletml/bulletsmanager.o \ src/abagames/util/bulletml/bullet.o src/abagames/util/actor.o \ src/abagames/util/prefmanager.o src/abagames/util/sdl/texture.o \ src/abagames/util/sdl/screen.o src/abagames/util/sdl/input.o \ src/abagames/util/sdl/recordablepad.o src/abagames/util/sdl/sdlexception.o \ src/abagames/util/sdl/pad.o src/abagames/util/sdl/mainloop.o \ src/abagames/util/sdl/sound.o src/abagames/util/sdl/luminous.o \ src/abagames/util/sdl/gamemanager.o src/abagames/util/sdl/displaylist.o \ src/abagames/util/sdl/screen3d.o src/abagames/util/vector.o \ src/abagames/util/iterator.o src/abagames/util/rand.o \ src/abagames/util/tokenizer.o import/SDL_video.o import/SDL_mixer.o \ -lbulletml -lSDL -lGL -lGLU -lSDL_mixer I don't know how to reduce this testcase (leaving out files obviously causes a failed link), but hopefully this information is useful to somebody with knowledge of the compiler. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdc-4.1 depends on: ii g++-4.1 4.1.2-25The GNU C++ compiler ii gcc-4.1-base 4.1.2-25The GNU Compiler Collection (base ii libc62.9-6 GNU C Library: Shared libraries ii libgcc1 1:4.3.3-5 GCC support library ii libphobos-4.1-dev0.25-4.1.2-23.2 The phobos D standard library ii libstdc++6 4.3.3-5
Bug#620116: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: gdc-4.3 | 1:1.060-4.3.5-2 | source, alpha, amd64, armel, hppa, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc libphobos-4.3-dev | 1:1.060-4.3.5-2 | alpha, amd64, armel, hppa, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc --- Reason --- ROM; obsolete -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close Bugs which have been reported against this package automatically. But please check all old bugs, if they where closed correctly or should have been re-assign to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 620...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/620116 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q4tet-0002cb...@franck.debian.org
Bug#620116: Removed package(s) from unstable
Version: 1:1.060-4.3.5-2+rm Dear submitter, as the package gdc-4.3 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/620116 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q4tea-0002e9...@franck.debian.org
Bug#620116: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-4.3 |4.3.5-4 | hppa cpp-4.3 |4.3.5-5 | alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc g++-4.3 |4.3.5-4 | hppa g++-4.3 |4.3.5-5 | alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc g++-4.3-multilib |4.3.5-5 | amd64, i386, kfreebsd-amd64, mips, mipsel, powerpc, s390, sparc g++-4.3-spu |4.3.5-5 | powerpc gcc-4.3 |4.3.5-4 | source, hppa gcc-4.3 |4.3.5-5 | source, alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc gcc-4.3-base |4.3.5-4 | hppa gcc-4.3-base |4.3.5-5 | alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc gcc-4.3-hppa64 |4.3.5-4 | hppa gcc-4.3-locales |4.3.5-4 | all gcc-4.3-locales |4.3.5-5 | all gcc-4.3-multilib |4.3.5-5 | amd64, i386, kfreebsd-amd64, mips, mipsel, powerpc, s390, sparc gcc-4.3-source |4.3.5-4 | all gcc-4.3-source |4.3.5-5 | all gcc-4.3-spu |4.3.5-5 | powerpc gfortran-4.3 |4.3.5-4 | hppa gfortran-4.3 |4.3.5-5 | alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc gfortran-4.3-multilib |4.3.5-5 | amd64, i386, kfreebsd-amd64, mips, mipsel, powerpc, s390, sparc gfortran-4.3-spu |4.3.5-5 | powerpc gobjc++-4.3 |4.3.5-4 | hppa gobjc++-4.3 |4.3.5-5 | alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc gobjc++-4.3-multilib |4.3.5-5 | amd64, i386, kfreebsd-amd64, mips, mipsel, powerpc, s390, sparc gobjc-4.3 |4.3.5-4 | hppa gobjc-4.3 |4.3.5-5 | alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc gobjc-4.3-multilib |4.3.5-5 | amd64, i386, kfreebsd-amd64, mips, mipsel, powerpc, s390, sparc lib32stdc++6-4.3-dbg |4.3.5-5 | amd64, kfreebsd-amd64 lib64stdc++6-4.3-dbg |4.3.5-5 | i386, mips, mipsel, powerpc, s390, sparc libmudflap0-4.3-dev |4.3.5-4 | hppa libmudflap0-4.3-dev |4.3.5-5 | alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc libn32stdc++6-4.3-dbg |4.3.5-5 | mips, mipsel libstdc++6-4.3-dbg |4.3.5-4 | hppa libstdc++6-4.3-dbg |4.3.5-5 | alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc libstdc++6-4.3-dev |4.3.5-4 | hppa libstdc++6-4.3-dev |4.3.5-5 | alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc libstdc++6-4.3-doc |4.3.5-4 | all libstdc++6-4.3-doc |4.3.5-5 | all libstdc++6-4.3-pic |4.3.5-4 | hppa libstdc++6-4.3-pic |4.3.5-5 | alpha, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc --- Reason --- ROM; obsolete -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close Bugs which have been reported against this package automatically. But please check all old bugs, if they where closed correctly or should have been re-assign to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 620...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/620116 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q4tg2-0002ox...@franck.debian.org
Processing of gcc-4.3_4.3.5-5_hppa.changes
gcc-4.3_4.3.5-5_hppa.changes uploaded successfully to localhost along with the files: gcc-4.3-base_4.3.5-5_hppa.deb cpp-4.3_4.3.5-5_hppa.deb libmudflap0-4.3-dev_4.3.5-5_hppa.deb gobjc++-4.3_4.3.5-5_hppa.deb gobjc-4.3_4.3.5-5_hppa.deb g++-4.3_4.3.5-5_hppa.deb libstdc++6-4.3-dev_4.3.5-5_hppa.deb libstdc++6-4.3-pic_4.3.5-5_hppa.deb libstdc++6-4.3-dbg_4.3.5-5_hppa.deb gfortran-4.3_4.3.5-5_hppa.deb gcc-4.3_4.3.5-5_hppa.deb gcc-4.3-hppa64_4.3.5-5_hppa.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q4w1z-0003ut...@franck.debian.org
gcc-4.6-plugin-dev has gengtype but no gtype.state
Hello All,
The gcc-4.6-plugin-dev package (from experimental?) 4.6.0-2 has the gengtype
program installed as /usr/lib/gcc/x86_64-linux-gnu/4.6/gengtype but lacks
the gtype.state file needed to run it.
It should have the file gcc/gtype.state from the build directory of gcc 4.6
copied at some appropriate place.
By the way, I am interested: how is gengttype installed in the
gcc-4.6-plugin-dev package? I am the GCC (upstream) guy who improved
gengtype, and as far as I know the gcc/Makefile.in rule to install it was
missing in (GCC FSF) 4.6.0...
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basilestarynkevitchnet mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110330142454.ga22...@ours.starynkevitch.net
gcc-4.3_4.3.5-5_hppa.changes REJECTED
Reject Reasons: no source found for gcc-4.3 4.3.5-5 (cpp-4.3_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (gcc-4.3-base_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (gcc-4.3-hppa64_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (gobjc++-4.3_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (gcc-4.3_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (libstdc++6-4.3-dev_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (libmudflap0-4.3-dev_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (gfortran-4.3_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (libstdc++6-4.3-dbg_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (g++-4.3_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (libstdc++6-4.3-pic_4.3.5-5_hppa.deb). no source found for gcc-4.3 4.3.5-5 (gobjc-4.3_4.3.5-5_hppa.deb). === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q4whz-qs...@franck.debian.org
Results for 4.4.5 (Debian 4.4.5-15) testsuite on x86_64-pc-linux-gnu
LAST_UPDATED: Sun Mar 13 18:10:06 UTC 2011 (revision 170923) Target: x86_64-linux-gnu gcc version 4.4.5 (Debian 4.4.5-15) Native configuration is x86_64-pc-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/graphite/pr39447.C (test for excess errors) === g++ Summary for unix === # of expected passes19995 # of unexpected failures1 # of expected failures 159 # of unsupported tests 254 Running target unix/-fstack-protector FAIL: g++.dg/graphite/pr39447.C (test for excess errors) === g++ Summary for unix/-fstack-protector === # of expected passes19995 # of unexpected failures1 # of expected failures 159 # of unsupported tests 254 Running target unix/-m32 === g++ Summary for unix/-m32 === # of expected passes20315 # of expected failures 159 # of unsupported tests 102 === g++ Summary === # of expected passes60305 # of unexpected failures2 # of expected failures 477 # of unsupported tests 610 /scratch/packages/gcc/4.4/gcc-4.4-4.4.5/build/gcc/testsuite/g++/../../g++ version 4.4.5 (Debian 4.4.5-15) === gcc tests === Running target unix FAIL: gcc.dg/tree-prof/bb-reorg.c compilation, -fprofile-use -D_PROFILE_USE UNRESOLVED: gcc.dg/tree-prof/bb-reorg.c execution,-fprofile-use -D_PROFILE_USE FAIL: gcc.dg/tree-prof/pr34999.c compilation, -fprofile-use -D_PROFILE_USE UNRESOLVED: gcc.dg/tree-prof/pr34999.c execution,-fprofile-use -D_PROFILE_USE === gcc Summary for unix === # of expected passes58115 # of unexpected failures2 # of expected failures 192 # of unresolved testcases 2 # of unsupported tests 743 Running target unix/-fstack-protector WARNING: program timed out. FAIL: gcc.c-torture/compile/limits-blockid.c -O0 (test for excess errors) FAIL: gcc.dg/tree-prof/bb-reorg.c compilation, -fprofile-use -D_PROFILE_USE UNRESOLVED: gcc.dg/tree-prof/bb-reorg.c execution,-fprofile-use -D_PROFILE_USE FAIL: gcc.dg/tree-prof/pr34999.c compilation, -fprofile-use -D_PROFILE_USE UNRESOLVED: gcc.dg/tree-prof/pr34999.c execution,-fprofile-use -D_PROFILE_USE === gcc Summary for unix/-fstack-protector === # of expected passes58114 # of unexpected failures3 # of expected failures 192 # of unresolved testcases 2 # of unsupported tests 743 Running target unix/-m32 === gcc Summary for unix/-m32 === # of expected passes58471 # of expected failures 193 # of unsupported tests 456 === gcc Summary === # of expected passes174700 # of unexpected failures5 # of expected failures 577 # of unresolved testcases 4 # of unsupported tests 1942 /scratch/packages/gcc/4.4/gcc-4.4-4.4.5/build/gcc/xgcc version 4.4.5 (Debian 4.4.5-15) === gfortran tests === Running target unix === gfortran Summary for unix === # of expected passes30516 # of expected failures 13 # of unsupported tests 44 Running target unix/-fstack-protector === gfortran Summary for unix/-fstack-protector === # of expected passes30516 # of expected failures 13 # of unsupported tests 44 Running target unix/-m32 === gfortran Summary for unix/-m32 === # of expected passes30387 # of expected failures 13 # of unsupported tests 105 === gfortran Summary === # of expected passes91419 # of expected failures 39 # of unsupported tests 193 /scratch/packages/gcc/4.4/gcc-4.4-4.4.5/build/gcc/testsuite/gfortran/../../gfortran version 4.4.5 (Debian 4.4.5-15) === obj-c++ tests === Running target unix XPASS: obj-c++.dg/comp-types-10.mm (test for excess errors) UNRESOLVED: obj-c++.dg/lookup-2.mm compilation failed to produce executable UNRESOLVED: obj-c++.dg/try-catch-2.mm compilation failed to produce executable UNRESOLVED: obj-c++.dg/try-catch-9.mm compilation failed to produce executable === obj-c++ Summary for unix === # of expected passes425 # of unexpected successes 1 # of expected failures 20 # of unresolved testcases 3 # of unsupported tests 13 Running target unix/-fstack-protector XPASS: obj-c++.dg/comp-types-10.mm (test for excess errors) UNRESOLVED: obj-c++.dg/lookup-2.mm compilation failed to produce executable UNRESOLVED: obj-c++.dg/try-catch-2.mm compilation failed to produce executable UNRESOLVED: obj-c++.dg/try-catch-9.mm compilation failed to produce executable === obj-c++ Summary for unix/-fstack-protector === # of expected passes425 # of unexpected su
Results for 4.5.2 (Debian 4.5.2-8) testsuite on x86_64-pc-linux-gnu
LAST_UPDATED: Tue Mar 29 17:53:55 UTC 2011 (revision 171685) Target: x86_64-linux-gnu gcc version 4.5.2 (Debian 4.5.2-8) Native configuration is x86_64-pc-linux-gnu === g++ tests === Running target unix UNRESOLVED: attribute_plugin.c compilation, -I. -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../libcpp/include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../intl -DIN_GCC -fPIC -shared UNRESOLVED: pragma_plugin.c compilation, -I. -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../libcpp/include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../intl -DIN_GCC -fPIC -shared UNRESOLVED: selfassign.c compilation, -I. -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../libcpp/include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../intl -O -DIN_GCC -fPIC -shared UNRESOLVED: dumb_plugin.c compilation, -I. -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../libcpp/include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../intl -DIN_GCC -fPIC -shared UNRESOLVED: header_plugin.c compilation, -I. -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../libcpp/include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../intl -DIN_GCC -fPIC -shared === g++ Summary for unix === # of expected passes23040 # of expected failures 153 # of unresolved testcases 5 # of unsupported tests 303 Running target unix/-fstack-protector UNRESOLVED: attribute_plugin.c compilation, -I. -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../libcpp/include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../intl -DIN_GCC -fPIC -shared UNRESOLVED: pragma_plugin.c compilation, -I. -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../libcpp/include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../intl -DIN_GCC -fPIC -shared UNRESOLVED: selfassign.c compilation, -I. -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../libcpp/include -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../intl -O -DIN_GCC -fPIC -shared UNRESOLVED: dumb_plugin.c compilation, -I. -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/build/gcc/testsuite/g++/../../../gcc -I/scratch/packages/gcc/4.5/gcc-4.5-4.5.2/src/gcc/testsuite/../../include -I/scratch/packages
Re: sh4 architecture into Wheezy
On 30.03.2011 07:05, Nobuhiro Iwamatsu wrote: > - ArchiveQualification of sh4 > http://wiki.debian.org/ArchiveQualification/sh4 > > How do you think about including sh4 in the next release? "Toolchain was supported by CodeSourcery" so it's not supported anymore? If this is correct, then this is a no-go for the port. Besides this, who will care about the toolchain for this port within Debian? I'm not keen on having another mips like maintained architecture. Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d937848.7070...@debian.org
Re: sh4 architecture into Wheezy
On 11-03-30 02:36 PM, Matthias Klose wrote: On 30.03.2011 07:05, Nobuhiro Iwamatsu wrote: - ArchiveQualification of sh4 http://wiki.debian.org/ArchiveQualification/sh4 How do you think about including sh4 in the next release? "Toolchain was supported by CodeSourcery" so it's not supported anymore? If this is correct, then this is a no-go for the port. Besides this, who will care about the toolchain for this port within Debian? I'm not keen on having another mips like maintained architecture. I've cleaned up the wiki a bit. The GNU toolchain supports SH4. However, CodeSourcery produces a version of the GNU toolchain as well. This toolchain is obtained separately by the user should they desire to use it. Changes in the CodeSourcery toolchain do eventually get pushed upstream to the FSF GNU toolchain. Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d9381b9.6010...@naoi.ca
Re: sh4 architecture into Wheezy
On 30.03.2011 21:17, Bill Traynor wrote: > On 11-03-30 02:36 PM, Matthias Klose wrote: >> On 30.03.2011 07:05, Nobuhiro Iwamatsu wrote: >>> - ArchiveQualification of sh4 >>>http://wiki.debian.org/ArchiveQualification/sh4 >>> >>> How do you think about including sh4 in the next release? >> "Toolchain was supported by CodeSourcery" >> >> so it's not supported anymore? If this is correct, then this is a no-go for >> the >> port. Besides this, who will care about the toolchain for this port within >> Debian? I'm not keen on having another mips like maintained architecture. > > I've cleaned up the wiki a bit. The GNU toolchain supports SH4. However, > CodeSourcery produces a version of the GNU toolchain as well. This toolchain > is > obtained separately by the user should they desire to use it. this is not an option for Debian. > Changes in the > CodeSourcery toolchain do eventually get pushed upstream to the FSF GNU > toolchain. yes, CS does this, but there may be a delay, and in some cases you may only see these changes submitted when the FSF GCC is in stage1. Assuming that GCC 4.6 and binutils 2.22 are targeted for wheezy, who will care about sh4 specific issues in the toolchain for wheezy? Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d938926.9070...@debian.org
Re: sh4 architecture into Wheezy
On 11-03-30 03:48 PM, Matthias Klose wrote: On 30.03.2011 21:17, Bill Traynor wrote: On 11-03-30 02:36 PM, Matthias Klose wrote: On 30.03.2011 07:05, Nobuhiro Iwamatsu wrote: - ArchiveQualification of sh4 http://wiki.debian.org/ArchiveQualification/sh4 How do you think about including sh4 in the next release? "Toolchain was supported by CodeSourcery" so it's not supported anymore? If this is correct, then this is a no-go for the port. Besides this, who will care about the toolchain for this port within Debian? I'm not keen on having another mips like maintained architecture. I've cleaned up the wiki a bit. The GNU toolchain supports SH4. However, CodeSourcery produces a version of the GNU toolchain as well. This toolchain is obtained separately by the user should they desire to use it. this is not an option for Debian. I don't mean that the CodeSourcery toolchain should be included in Debian. I'm merely stating that the user can install whatever toolchain post distribution install. I'll just remove the CodeSourcery reference altogether. Changes in the CodeSourcery toolchain do eventually get pushed upstream to the FSF GNU toolchain. yes, CS does this, but there may be a delay, and in some cases you may only see these changes submitted when the FSF GCC is in stage1. Assuming that GCC 4.6 and binutils 2.22 are targeted for wheezy, who will care about sh4 specific issues in the toolchain for wheezy? I'm not sure, but will find out. Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d939fba.9090...@naoi.ca
Bug#620190: /usr/bin/rebuild-gcj-db: line 58: gcj-dbtool-4.5: command not found
Package: libgcj-common Version: 1:4.4.5-6 Severity: important As title says. This makes libecj-java-gcj uninstallable and causes FTBFS on mule. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-1-amd64 (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 Versions of packages libgcj-common depends on: ii python2.6.6-12 interactive high-level object-orie libgcj-common recommends no packages. libgcj-common suggests no packages. -- no debconf information -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/ "Faith means not wanting to know what is true." -- Nietzsche -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110330220123.ga11...@miguel.cc
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 620190 + libecj-java-gcj src:mule Bug #620190 [libgcj-common] /usr/bin/rebuild-gcj-db: line 58: gcj-dbtool-4.5: command not found Added indication that 620190 affects libecj-java-gcj and src:mule > thanks Stopping processing here. Please contact me if you need assistance. -- 620190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130152317111837.transcr...@bugs.debian.org
Re: sh4 architecture into Wheezy
Hi,
2011/3/31 Matthias Klose :
> On 30.03.2011 21:17, Bill Traynor wrote:
>> On 11-03-30 02:36 PM, Matthias Klose wrote:
>>> On 30.03.2011 07:05, Nobuhiro Iwamatsu wrote:
- ArchiveQualification of sh4
http://wiki.debian.org/ArchiveQualification/sh4
How do you think about including sh4 in the next release?
>>> "Toolchain was supported by CodeSourcery"
>>>
>>> so it's not supported anymore? If this is correct, then this is a no-go for
>>> the
>>> port. Besides this, who will care about the toolchain for this port within
>>> Debian? I'm not keen on having another mips like maintained architecture.
>>
>> I've cleaned up the wiki a bit. The GNU toolchain supports SH4. However,
>> CodeSourcery produces a version of the GNU toolchain as well. This
>> toolchain is
>> obtained separately by the user should they desire to use it.
>
> this is not an option for Debian.
>
>> Changes in the
>> CodeSourcery toolchain do eventually get pushed upstream to the FSF GNU
>> toolchain.
>
> yes, CS does this, but there may be a delay, and in some cases you may only
> see
> these changes submitted when the FSF GCC is in stage1.
>
> Assuming that GCC 4.6 and binutils 2.22 are targeted for wheezy, who will care
> about sh4 specific issues in the toolchain for wheezy?
>
Yohii-san and I mainly.
It is difficult to solve a problem of GCC to me. But gcc/sh maintainer
supported a problem.
There is maintainers of sh4(sh). Kaz kojima and other.
I was helped how many times by them.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlktikzo+dhk3quxoqb1iszxgnpf40h4taturifz...@mail.gmail.com
Re: sh4 architecture into Wheezy
On Wed, 2011-03-30 at 21:48 +0200, Matthias Klose wrote: > On 30.03.2011 21:17, Bill Traynor wrote: > > On 11-03-30 02:36 PM, Matthias Klose wrote: > >> On 30.03.2011 07:05, Nobuhiro Iwamatsu wrote: > >>> - ArchiveQualification of sh4 > >>>http://wiki.debian.org/ArchiveQualification/sh4 > >>> > >>> How do you think about including sh4 in the next release? > >> "Toolchain was supported by CodeSourcery" > >> > >> so it's not supported anymore? If this is correct, then this is a no-go > >> for the > >> port. Besides this, who will care about the toolchain for this port within > >> Debian? I'm not keen on having another mips like maintained architecture. > > > > I've cleaned up the wiki a bit. The GNU toolchain supports SH4. However, > > CodeSourcery produces a version of the GNU toolchain as well. This > > toolchain is > > obtained separately by the user should they desire to use it. > > this is not an option for Debian. > > > Changes in the > > CodeSourcery toolchain do eventually get pushed upstream to the FSF GNU > > toolchain. > > yes, CS does this, but there may be a delay, and in some cases you may only > see > these changes submitted when the FSF GCC is in stage1. > > Assuming that GCC 4.6 and binutils 2.22 are targeted for wheezy, who will care > about sh4 specific issues in the toolchain for wheezy? Hi, Kaz Kojima provides regular testresults for GCC on sh4-linux : 4.7: http://gcc.gnu.org/ml/gcc-testresults/2011-03/msg02619.html 4.6: http://gcc.gnu.org/ml/gcc-testresults/2011-03/msg01500.html He also seems active fixing bugs on this platform, eg: http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01213.html He commited about two patch a month on average according to gcc/ChangeLog for 2009-2011. Renesas donated an SH4 board to the GCC Compile Farm project (1). This donation has not been made public yet since I'm waiting for wheezy and full 512MB RAM support (current lenny based release I tested supports only 128MB due to kernel issues), but it should be soon and so the sh4-linux platform will be available for all upstream free software developpers in case the need arises. I will try native GCC bootstrap on it. Note: I'm no SH4 expert and I don't know personally Kaz Kojima, just looking at my inbox archives :). Sincerely, Laurent (1) http://gcc.gnu.org/wiki/CompileFarm -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301528668.11098.1008.camel@pc2.unassigned-domain
