Bug#596154: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: lsnipes |0.9.4-7 | source, alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc --- Reason --- RoQA; orphaned, dead upstream, unused -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/596154 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oth0d-0004c6...@franck.debian.org
Bug#596145: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: workman | 1.3.4-29 | source, alpha, armel, hppa, i386, mips, mipsel, powerpc, s390, sparc --- Reason --- RoQA; orphaned, unused, dead upstream, alternatives exist -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/596145 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oth12-0004h0...@franck.debian.org
Bug#593163: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: hindent |1.1.2-8 | source, all --- Reason --- RoQA; obsolete, unmaintained, dead upstream, orphaned for a long time -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 593...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/593163 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oth68-0005l0...@franck.debian.org
Bug#596146: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: wmmaiload |2.3.0-1 | source, alpha, amd64, armel, hppa, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc --- Reason --- RoQA; orphaned, unused, dead upstream -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/596146 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oth6h-0005ri...@franck.debian.org
Bug#596118: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: u++ |5.3.0-2 | source, amd64, i386, ia64 u++-doc |5.3.0-2 | all --- Reason --- RoQA; unused, orphaned, dead upstream -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/596118 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oth7s-0005me...@franck.debian.org
Bug#583597: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: bake | 1.0-14 | source, all --- Reason --- dead upstream, unused, no reverse deps -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 583...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/583597 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oth8o-0005qm...@franck.debian.org
Bug#596147: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: wmbinclock | 0.5-5 | source, alpha, amd64, armel, hppa, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc --- Reason --- RoQA; orphaned for a long time, unused, dead upstream -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/596147 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oth9i-0005ud...@franck.debian.org
Bug#596157: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: wmblob |1.0.3-3 | source, alpha, amd64, hppa, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc wmblob | 1.0.3-3+b1 | armel, ia64 --- Reason --- RoQA; orphaned for a long time, unused, dead upstream -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/596157 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1othaf-0005zl...@franck.debian.org
Bug#596158: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: anymeal | 0.30-9 | source, alpha, amd64, armel, hppa, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc --- Reason --- RoQA; orphaned, unused, not im Squeeze -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/596158 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1othc2-00066a...@franck.debian.org
Bug#596114: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: wmmisc | 1.1-5 | source, alpha, amd64, armel, hppa, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc --- Reason --- RoQA; orphaned, dead upstream, unused -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/596114 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1othea-0006bo...@franck.debian.org
tkmixer REMOVED from testing
FYI: The status of the tkmixer source package in Debian's testing distribution has changed. Previous version: 1.0-19 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for removing your package seems to be nonsense, it is probably the reporting script that got confused. Please check the actual hints file before you complain about meaningless removals. -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1otk9a-00076h...@franck.debian.org
transcriber REMOVED from testing
FYI: The status of the transcriber source package in Debian's testing distribution has changed. Previous version: 1.5.1.1-4 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for removing your package seems to be nonsense, it is probably the reporting script that got confused. Please check the actual hints file before you complain about meaningless removals. -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1otk9a-00076l...@franck.debian.org
nstx REMOVED from testing
FYI: The status of the nstx source package in Debian's testing distribution has changed. Previous version: 1.1-beta6-6 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for removing your package seems to be nonsense, it is probably the reporting script that got confused. Please check the actual hints file before you complain about meaningless removals. -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1otk9a-00076j...@franck.debian.org
Bug#254966: marked as done (nstx should pass through dns queries to a real dns server)
Your message dated with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org> and subject line nstx removed from Debian unstable has caused the Debian Bug report #254966, regarding nstx should pass through dns queries to a real dns server 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.) -- 254966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=254966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nstx Severity: wishlist Version: 1.1-beta4-1 First off, thanks for packaging (and upstream for writing) nstx. I'd actually like to suggest that the daemon be modified so that it is capable of passing through real dns requests unrelated to nstx to a real live DNS server. I'm not totally sure how this would work yet, myself, but ideally you'd have bind or similar running on some port besides 53, and packets for bind would be sent there instead of being handled by nstx. [I personally haven't walked through the details of nstx myself, so it's possible that I've missed some basic fundamental reason why this is not possible.] Don Armstrong -- There is no mechanical problem so difficult that it cannot be solved by brute strength and ignorance. -- William's Law http://www.donarmstrong.com http://rzlab.ucr.edu signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Version: 1.1-beta6-6+rm nstx has been removed from Debian unstable: http://bugs.debian.org/595988 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#259339: marked as done (nstx: return value of malloc() is never checked anywhere)
Your message dated with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org> and subject line nstx removed from Debian unstable has caused the Debian Bug report #259339, regarding nstx: return value of malloc() is never checked anywhere 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.) -- 259339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=259339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nstx Version: 1.1-beta5-2 Severity: important I did a quick grep malloc *.c in the source tree. It looks like each time malloc() is used the return value is never checked but is often used directly after that for write operations. This makes nstx very dangerous, since usually it runs as root without any authentication. The bug in http://bugs.debian.org/259079 is only one example of the resulting behaviour. In the current state, the package documentation should at least contain a big warning that nstx should be run in a chroot environment with user privileges. The latter works if the nstxd listens on an unprivileged port with incoming DNS queries redirected to this port, and with proper permissions for /dev/net/tun. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.6-mm1 Locale: LANG=C, lc_ctype=de...@euro Versions of packages nstx depends on: ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an -- no debconf information --- End Message --- --- Begin Message --- Version: 1.1-beta6-6+rm nstx has been removed from Debian unstable: http://bugs.debian.org/595988 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#274636: marked as done (tkmixer: channel Digital1 causes white noise)
Your message dated with message-id <20100909203456.4772.94194.mass-bugs-cl...@merkel.debian.org> and subject line tkmixer removed from Debian unstable has caused the Debian Bug report #274636, regarding tkmixer: channel Digital1 causes white noise 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.) -- 274636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tkmixer Version: 1.0-14 Severity: normal When starting the tkmixer the digital1 channel is allways unmuted and at full volume. lspci reports Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02) for my soundcard. The volume is set disregarding any previously saved settings, where all other channels are restored correctly. I use alsa and arts. This problem occured for many versions of tkmixer now. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: lang=en...@euro, lc_ctype=de...@euro (ignored: LC_ALL set to en...@euro) Versions of packages tkmixer depends on: ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an ii libgcc1 1:3.4.2-2GCC support library ii libstdc++5 1:3.3.4-11 The GNU Standard C++ Library v3 ii tcl8.4 8.4.6-1 Tcl (the Tool Command Language) v8 ii tk8.4 8.4.6-1 Tk toolkit for Tcl and X11, v8.4 - -- no debconf information --- End Message --- --- Begin Message --- Version: 1.0-19+rm tkmixer has been removed from Debian unstable: http://bugs.debian.org/595992 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#291482: marked as done (transcriber: feature request: slow down sound like Audacity's "change tempo")
Your message dated with message-id <20100909203525.4772.44963.mass-bugs-cl...@merkel.debian.org> and subject line transcriber removed from Debian unstable has caused the Debian Bug report #291482, regarding transcriber: feature request: slow down sound like Audacity's "change tempo" 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.) -- 291482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: transcriber Version: 1.4.6-4 Severity: wishlist transcriber is very useful software, and helps transcription of all kind of materials a lot. Yet, some people speak faster than I am able to type, and I have seen proprietary software that can make such transcriptions much easier by reducing the speed of speech without changing the pitch of the voice. I recently noticed that a similar function is included in Audacity (the free "DJ-mixer"), accessible under Effect->Change tempo, so it's neither secret nor magic, and I would be very happy if this could also be included in transcriber :-) Florian --- End Message --- --- Begin Message --- Version: 1.5.1.1-4+rm transcriber has been removed from Debian unstable: http://bugs.debian.org/595993 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#307772: marked as done (nstx: Fail to parse some DNS responses)
Your message dated with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org> and subject line nstx removed from Debian unstable has caused the Debian Bug report #307772, regarding nstx: Fail to parse some DNS responses 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.) -- 307772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=307772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nstx Version: 1.1-beta6-2.1 Severity: wishlist When testing nstx on a hotel here in Spain, the client seem to be unable to parse the DNS response packages generated by the DNS server provided on the network. I got a tcpdump documenting the packages delived. The client report this message to syslog while it is failing to parse the response: nstxcd: dns_extractpkt: record too long in an (259->24936) Any ideas how I can debug this? I'm in this hotel the next few days. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (2100, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.26-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages nstx depends on: ii adduser 3.63 Add and remove users and groups ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an -- no debconf information --- End Message --- --- Begin Message --- Version: 1.1-beta6-6+rm nstx has been removed from Debian unstable: http://bugs.debian.org/595988 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#317786: marked as done (nstx: init script doesn't report daemon start failure)
Your message dated with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org> and subject line nstx removed from Debian unstable has caused the Debian Bug report #317786, regarding nstx: init script doesn't report daemon start failure 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.) -- 317786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=317786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nstx Version:1.1-beta6-2.1 The init script for nstxcd (and maybe nstxd?) fail to report if a start action is unsuccessful. The one repeatable case I've discovered to test this is that if there is no network interface up (or default route) then it fails to start. -- Matt Taggart tagg...@debian.org --- End Message --- --- Begin Message --- Version: 1.1-beta6-6+rm nstx has been removed from Debian unstable: http://bugs.debian.org/595988 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#393339: marked as done (segfault in nstxd)
Your message dated with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org> and subject line nstx removed from Debian unstable has caused the Debian Bug report #393339, regarding segfault in nstxd 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.) -- 393339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nstx Version: 1.1-beta6-2.1 Severity: important I can reproduce this segfault: nstxd[15095]: segfault at rip +00402a1e rsp 7f8c6390 error 6 by starting nstxd and issuing any type of query to it from remote. Strace is attached. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-2-amd64 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- .''`. martin f. krafft : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems nstcd.strace.bz2 Description: Binary data signature.asc Description: Digital signature (GPG/PGP) --- End Message --- --- Begin Message --- Version: 1.1-beta6-6+rm nstx has been removed from Debian unstable: http://bugs.debian.org/595988 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#398356: marked as done (provide a way to name the interface)
Your message dated with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org> and subject line nstx removed from Debian unstable has caused the Debian Bug report #398356, regarding provide a way to name the interface 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.) -- 398356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nstx Version: 1.1-beta6-4 Severity: wishlist It would rock if nstx provided a way to (re)name the interface. For instance, on systems with OpenVPN installed, it will otherwise depend on startup order which daemon gets tun0 and which gets tun1. It would rock if nstx could just rename the tun* interface it gets to 'nstxd'. iproute can do this btw: ip link set tun0 name nstxd so this could be realised in the init.d script iff iproute were installed and nstxd would communicate which interface it actually got. A better way would be to pass the desired name to nstxd at startup and have it pass an ifreq struct with ifr_name set to the TUNSETIFF ioctl. It should then also report which interface actually got used. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-2-amd64 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- .''`. martin f. krafft : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP) --- End Message --- --- Begin Message --- Version: 1.1-beta6-6+rm nstx has been removed from Debian unstable: http://bugs.debian.org/595988 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#428529: marked as done (Starting nstx at arbitary times)
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #428529,
regarding Starting nstx at arbitary times
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.)
--
428529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nstx
Version: 1.1-beta6-4
Severity: wishlist
Tags: patch
I don't need nstxcd to run all the time. In particular, it doesn't need
to start at boot time. However, I'd like to be able to use the normal
start up mechanism to start it on demand from the command line by, e.g.,
running the following:
/etc/init.d/nstxcd start
Taking inspiration form openvpn, which allows you to start arbitary
interfaces using the form:
/etc/init.d/openvpn start vpn-name
I'd propose that /etc/init.d nstxcd take an additional argument, force,
which indicates whether to respect the start_nstxcd variable.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Versions of packages nstx depends on:
ii adduser 3.102Add and remove users and groups
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
nstx recommends no packages.
-- no debconf information
--- nstxcd.orig 2007-06-12 10:51:05.0 +0200
+++ nstxcd 2007-06-12 10:48:09.0 +0200
@@ -16,9 +16,16 @@ fi
set -e
+FORCE=$2
+
check_start_nstxcd_option() {
+# Force it to start.
+if [ "x$FORCE" = "xforce" ]; then
+return 0
+fi
+
if [ ! "$start_nstxcd" = "yes" ]; then
- echo "Not starting nstx client, disabled via /etc/default/nstx"
+ echo "Not starting, disabled via /etc/default/nstx; try $0 start force"
return 1
else
return 0
--- End Message ---
--- Begin Message ---
Version: 1.1-beta6-6+rm
nstx has been removed from Debian unstable: http://bugs.debian.org/595988
Closing its bugs with a Version higher than the last unstable upload.
More information about this script at:
http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD
--- End Message ---
Bug#467216: marked as done (nstxcd fails with IPv6 DNS resolver)
Your message dated with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org> and subject line nstx removed from Debian unstable has caused the Debian Bug report #467216, regarding nstxcd fails with IPv6 DNS resolver 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.) -- 467216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nstx Version: 1.1-beta6-4.1 Severity: normal nstxcd fails if an IPv6 address is passed as the local DNS resolver to use. Under the current setup in Debian, the first nameserver entry in /etc/resolv.conf is passed to nstxcd, so if an IPv6 resolver is configured there, it causes nstxcd to fail. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.23.12-grsec Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nstx depends on: ii adduser 3.105 add and remove users and groups ii libc6 2.7-8 GNU C Library: Shared libraries nstx recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.1-beta6-6+rm nstx has been removed from Debian unstable: http://bugs.debian.org/595988 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#468446: marked as done (Memleaks in nstxcd)
Your message dated with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org> and subject line nstx removed from Debian unstable has caused the Debian Bug report #468446, regarding Memleaks in nstxcd 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.) -- 468446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nstx Version: 1.1-beta6-4.1 Severity: important Hi, wondering why my system applet showed such a high mem usage, it turned out that nstxcd was using a huge amount of RAM. That bug might deserve a higher severity, but since I'm not sure, leaving it to important for now. Cheers, -- Cyril Brulebois -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.25-rc2-powerpc Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nstx depends on: ii adduser 3.105 add and remove users and groups ii libc6 2.7-8 GNU C Library: Shared libraries nstx recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.1-beta6-6+rm nstx has been removed from Debian unstable: http://bugs.debian.org/595988 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#477800: marked as done (tkmixer: Doesn't run (can't open /dev/mixer))
Your message dated with message-id <20100909203456.4772.94194.mass-bugs-cl...@merkel.debian.org> and subject line tkmixer removed from Debian unstable has caused the Debian Bug report #477800, regarding tkmixer: Doesn't run (can't open /dev/mixer) 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.) -- 477800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tkmixer Version: 1.0-18 Severity: important On my system, tkmixer completely fails to launch: [mo...@mole ~]$ tkmixer error opening mixer device tkmixer: No such file or directory [mo...@mole ~]$ This is because my mixer device is at /dev/sound/mixer, but tkmixer is trying to open /dev/mixer. I don't believe I've done any special configuration where this is concerned, so I would expect that this affects a large number of users. I'm running udev. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) 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 tkmixer depends on: ii libc6 2.7-10 GNU C Library: Shared libraries ii libgcc1 1:4.3.0-3 GCC support library ii libstdc++64.3.0-3The GNU Standard C++ Library v3 ii tcl8.48.4.19-1 Tcl (the Tool Command Language) v8 ii tk8.4 8.4.19-1 Tk toolkit for Tcl and X11, v8.4 - tkmixer recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.0-19+rm tkmixer has been removed from Debian unstable: http://bugs.debian.org/595992 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#515309: marked as done (nstx: init restart action not equivalent to stop+start and fails miserably)
Your message dated with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org> and subject line nstx removed from Debian unstable has caused the Debian Bug report #515309, regarding nstx: init restart action not equivalent to stop+start and fails miserably 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.) -- 515309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nstx Version: 1.1-beta6-5 Severity: important Coin, The start action has the following options handling code: if [ -n "$NSTX_IFACE" ]; then OPTIONS="-i $NSTX_IFACE $NSTX_OPTIONS $NSTX_DOMAIN" else OPTIONS="$NSTX_OPTIONS $NSTX_DOMAIN" fi but the restart action does not. I guess the start and stop actions should be handled by functions, so that restart can call them and ensure there is no inconsistancies. The consequencies of this problem is nstxd cannot bind the port and fails. This is quite inconvenient during upgrades. -- Marc Dequènes (Duck) pgpJFuD6lcydk.pgp Description: PGP Digital Signature --- End Message --- --- Begin Message --- Version: 1.1-beta6-6+rm nstx has been removed from Debian unstable: http://bugs.debian.org/595988 Closing its bugs with a Version higher than the last unstable upload. More information about this script at: http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD --- End Message ---
Bug#550401: marked as done (return value of write ignored in nstx_tuntap.c)
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #550401,
regarding return value of write ignored in nstx_tuntap.c
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.)
--
550401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nstx
Version: 1.1-beta6-5
Severity: normal
Tags: patch
Hi,
just found this when trying to build nstx on an Ubuntu system: In
nstx_tuntap.c, the return value of write (for the tuntap file descriptor) is
ignored, which means to ignore short writes or an EINTR.
Attached is a patch to fix this, would be excellent if you could include it.
Cheers,
Stefan.
-- System Information:
Debian Release: squeeze/sid
APT prefers karmic-updates
APT policy: (500, 'karmic-updates'), (500, 'karmic-security'), (500, 'karmic')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-12-generic (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
#! /bin/sh /usr/share/dpatch/dpatch-run
## fix-return-values.dpatch by
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: No description.
@DPATCH@
diff -urNad nstx-1.1-beta6~/nstx_tuntap.c nstx-1.1-beta6/nstx_tuntap.c
--- nstx-1.1-beta6~/nstx_tuntap.c 2009-10-09 21:50:53.0 +0200
+++ nstx-1.1-beta6/nstx_tuntap.c 2009-10-09 21:53:01.0 +0200
@@ -266,7 +266,20 @@
sendtun(const char *data, size_t len)
{
// printf("Sent len %d, csum %d\n", len, checksum(data, len));
- write(tfd, data, len);
+
+ size_t count;
+ ssize_t ret;
+
+ for (count = 0; count < len; count += ret) {
+ ret = write(tfd, data + count, len - count);
+
+ if (ret < 0) {
+ if (errno == EINTR) {
+continue;
+ }
+ return;
+ }
+ }
}
void
--- End Message ---
--- Begin Message ---
Version: 1.1-beta6-6+rm
nstx has been removed from Debian unstable: http://bugs.debian.org/595988
Closing its bugs with a Version higher than the last unstable upload.
More information about this script at:
http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD
--- End Message ---
Bug#553297: marked as done (nstx: Uses non-standard '_' in domain names)
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #553297,
regarding nstx: Uses non-standard '_' in domain names
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.)
--
553297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nstx
Version: 1.1-beta6-5
Severity: normal
Tags: patch upstream
Hello,
nstx uses base64 encoding, which produces '_' characters, which is not
valid in a domain name. To get more DNS server coverage, I have patched
my version into using base32, here is my (tested) patch, in case it can
be useful more broadly.
Samuel
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages nstx depends on:
ii adduser 3.111 add and remove users and groups
ii libc6 2.9-25 GNU C Library: Shared libraries
nstx recommends no packages.
nstx suggests no packages.
-- no debconf information
diff -ur nstx-1.1-beta6/nstx_encode.c
/home/samy/src/nstx-1.1-beta6/nstx_encode.c
--- nstx-1.1-beta6/nstx_encode.c2009-10-30 00:49:24.0 +0100
+++ /home/samy/src/nstx-1.1-beta6/nstx_encode.c 2009-10-29 04:24:31.0
+0100
@@ -23,9 +23,16 @@
#include
#include
+#include
+
+//#define base64
unsigned char map[] =
+#ifdef base64
"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ-_1234567890";
+#else
+ "abcdefghijklmnopqrstuvABCDEFGHIJ";
+#endif
unsigned char *revmap = NULL;
void init_revmap (void)
@@ -43,21 +50,44 @@
int i = 0, off = 1, cut = 0;
static unsigned char *buf = NULL;
+#ifdef base64
if (len % 3)
cut = 3 - len%3;
+#else
+ if (len % 5)
+ cut = 5 - len%5;
+#endif
+#ifdef base64
buf = realloc(buf, ((len+2)/3)*4+2);
+#else
+ buf = realloc(buf, ((len+4)/5)*8+2);
+#endif
buf[0] = map[cut];
while (i < len) {
- buf[off + 0] = map[(data[i] & 252) >> 2];
- buf[off + 1] = map[((data[i] & 3) << 4) | ((data[i+1] & 240) >> 4)];
- buf[off + 2] = map[((data[i+1] & 15) << 2 ) | ((data[i+2] & 192) >> 6)];
- buf[off + 3] = map[(data[i+2] & 63)];
+#ifdef base64
+ buf[off + 0] = map[(data[i] & 0xfc) >> 2];
+ buf[off + 1] = map[((data[i] & 3) << 4) | ((data[i+1] & 0xf0) >> 4)];
+ buf[off + 2] = map[((data[i+1] & 0xf) << 2 ) | ((data[i+2] & 0xc0) >>
6)];
+ buf[off + 3] = map[(data[i+2] & 0x3f)];
i += 3;
off += 4;
+#else
+ buf[off + 0] = map[(data[i] & 0xf8) >> 3];
+ buf[off + 1] = map[((data[i] & 7) << 2) | ((data[i+1] & 0xc0) >> 6)];
+ buf[off + 2] = map[((data[i+1] & 0x3e) >> 1)];
+ buf[off + 3] = map[((data[i+1] & 0x1) << 4) | ((data[i+2] & 0xf0) >> 4)];
+ buf[off + 4] = map[((data[i+2] & 0xf) << 1) | ((data[i+3] & 0x80) >> 7)];
+ buf[off + 5] = map[((data[i+3] & 0x7c) >> 2)];
+ buf[off + 6] = map[((data[i+3] & 0x3) << 3) | ((data[i+4] & 0xe0) >> 5)];
+ buf[off + 7] = map[((data[i+4] & 0x1f))];
+ i += 5;
+ off += 8;
+#endif
}
buf[off] = '\0';
+ //printf("encoded %d into %s\n", len, buf);
return buf;
}
@@ -72,14 +102,32 @@
len = strlen((char*)data);
+#ifdef base64
buf = realloc(buf, ((len+3)/4)*3);
+#else
+ buf = realloc(buf, ((len+7)/8)*5);
+#endif
+#ifdef base64
while (off+3 < len) {
- buf[i+0] = (revmap[data[off]]<<2)|((revmap[data[off+1]]&48)>>4);
+#else
+ while (off+7 < len) {
+#endif
+#ifdef base64
+ buf[i+0] = (revmap[data[off]]<<2)|((revmap[data[off+1]]&0x30)>>4);
buf[i+1] = ((revmap[data[off+1]]&15)<<4)|((revmap[data[off+2]]&60)>>2);
buf[i+2] = ((revmap[data[off+2]]&3)<<6)|(revmap[data[off+3]]);
i += 3;
off += 4;
+#else
+ buf[i+0] = (revmap[data[off]]<<3)|((revmap[data[off+1]]&0x1c)>>2);
+ buf[i+1] =
((revmap[data[off+1]]&0x3)<<6)|((revmap[data[off+2]])<<1)|((revmap[data[off+3]]&0x10)>>4);
+ buf[i+2] =
((revmap[data[off+3]]&0xf)<<4)|((revmap[data[off+4]]&0x1e)>>1);
+ buf[i+3] =
((revmap[data[off+4]]&0x1)<<7)|((revmap[data[off+5]])<<2)|((revmap[data[off+6]]&0x18)>>3);
+ buf[i+4] = ((revmap[data[off+6]]&0x7)<<5)|((revmap[data[off+7]]));
+ i += 5
Bug#553299: marked as done (nstx: Does not support cross-endianness)
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #553299,
regarding nstx: Does not support cross-endianness
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.)
--
553299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nstx
Version: 1.1-beta6-5
Severity: normal
Tags: patch upstream
My laptop is x86 and my router is Big-endian Mips. nstx doesn't work
very well in that case just because of endianness which flips the fields
of the nstxhdr structure around. The 12bit length field makes it even
more tricky.
In the attached patch, I have just increased the id size to 16 to
make it easier to just revert the fields. I don't know whether nstx
considers cross-version compatibility? In such case my patch won't be
ok, of course, and send/reception bitmagic will be needed instead.
Samuel
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages nstx depends on:
ii adduser 3.111 add and remove users and groups
ii libc6 2.9-25 GNU C Library: Shared libraries
nstx recommends no packages.
nstx suggests no packages.
-- no debconf information
--
Samuel Thibault
le y est un animal discret se logeant facilement dans un terminal
*** c has changed the topic on channel #ens-mim to ne pas jeter de cacahuetes
aux ys, svp
-+- #ens-mim - n'oubliez pas le guide -+-
diff -ur nstx-1.1-beta6/nstxfun.h /home/samy/src/nstx-1.1-beta6/nstxfun.h
--- nstx-1.1-beta6/nstxfun.h2004-06-27 23:43:34.0 +0200
+++ /home/samy/src/nstx-1.1-beta6/nstxfun.h 2009-10-29 05:49:52.0
+0100
@@ -32,11 +32,19 @@
/* nstx header */
struct nstxhdr {
+#if __BYTE_ORDER == __LITTLE_ENDIAN
unsigned char magic;
unsigned char seq:4;
- unsigned char chan:4; /* Unused yet... */
- unsigned short id:12;
- unsigned short flags:4;
+ unsigned char chan:2; /* Unused yet... */
+ unsigned char flags:2;
+ unsigned short id:16;
+#else
+ unsigned char magic;
+ unsigned char flags:2;
+ unsigned char chan:2; /* Unused yet... */
+ unsigned char seq:4;
+ unsigned short id:16;
+#endif
};
/* flags... more to come ?! */
--- End Message ---
--- Begin Message ---
Version: 1.1-beta6-6+rm
nstx has been removed from Debian unstable: http://bugs.debian.org/595988
Closing its bugs with a Version higher than the last unstable upload.
More information about this script at:
http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD
--- End Message ---
Bug#589328: marked as done (Short write in nstx_tuntap.c)
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #589328,
regarding Short write in nstx_tuntap.c
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.)
--
589328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nstx
Version: 1.1-beta6-6
Severity: normal
Tags: patch
Justification: Policy 9.3.2
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu maverick ubuntu-patch
Hello,
In ubuntu we applied the attached patch and we think you're interested
to apply it too. The purpose of this patch is to fix ignoring the return
value of a possible short write in nstx_tuntap.c. Thanks.
## fix-return-values.dpatch by
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: No description.
--- nstx-1.1-beta6~/nstx_tuntap.c 2009-10-10 13:57:50.0 +0200
+++ nstx-1.1-beta6/nstx_tuntap.c2009-10-10 13:58:17.0 +0200
@@ -266,7 +266,21 @@
sendtun(const char *data, size_t len)
{
// printf("Sent len %d, csum %d\n", len, checksum(data, len));
- write(tfd, data, len);
+
+ size_t count;
+ ssize_t ret;
+
+ for (count = 0; count < len; count += ret) {
+ ret = write(tfd, data + count, len - count);
+
+ if (ret < 0) {
+ if (errno == EINTR) {
+ ret = 0;
+ continue;
+ }
+ return;
+ }
+ }
}
void
--- End Message ---
--- Begin Message ---
Version: 1.1-beta6-6+rm
nstx has been removed from Debian unstable: http://bugs.debian.org/595988
Closing its bugs with a Version higher than the last unstable upload.
More information about this script at:
http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD
--- End Message ---
Processed: tagging 475727
Processing commands for cont...@bugs.debian.org: > tags 475727 + confirmed Bug #475727 [offlineimap] offlineimap: Aborts if the server refuses to store a message Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 475727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128408076916484.transcr...@bugs.debian.org
Bug#475727: One way to reproduce this
I think that I found one way to reproduce this in a way that would
serve for debugging purposes:
With a gmail account, if you are trying to upload to the gmail servers
an "e-mail" that is a chat of theirs, then they will refuse the upload
(tested also with mutt and icedove). The most informative message of
the programs is displayed by mutt. Icedove informs that the server
didn't like something, and offlineimap just bombs with a stack trace,
instead of having better error handling.
Regards.
P.S.: Keep me in the CC'ies.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlkti=r1qo+1hb1esi28qpsberlubphc1qtt5c=v...@mail.gmail.com
Bug#590537: offlineimap dies under many situations
Hi.
Or should I say "ping"?
Unfortunately, it seems that offlineimap is very sensitive to many
situations and dies quite frequently. I suspect that, aside from the
"die always", it may also be under some deadlock situations (or would
that be the "new" python 2.6 that is in sid)?
Apart from dying frequently, I usually have to interrupt offlineimap
when it gets my CPU usage to 100% and it stops communicating with the
network. I tried to strace it during one of those times when it was
pegging the CPU and I could see many select calls being issued, but no
progress being done.
I can give any further information, if necessary. Just let me know what.
Regards,
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlktimvkpd_chqfb-nmme5+_3sd_7pf9a6c0cejk...@mail.gmail.com
Bug#596291: offlineimap getting stuck when run with multiple threads/connections
Package: offlineimap
Severity: important
As I reported in another bug (about offlineimap dying too easily under
many circumstances), attached is what I see when I strace one of the
running threads of offlineimap when it is run with 10 connections to
initially mirror my gmail account to a local maildir.
I am not trying anymore to push the messages to the gmail server---I am
now trying to pull a fresh copy of them from there.
If there is anything that would be desired and if I can reproduce it,
then, please, let me know.
Regards,
--
Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
read(12, "", 5) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
read(12, "", 5) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
read(12, "", 5) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
read(12, "", 5) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
read(12, "", 5) = 0
futex(0xa2aa1b8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
read(12, "", 5) = 0
futex(0xa2aa1b8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
read(12, "", 5) = 0
futex(0xa2aa1b8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
read(12, "", 5) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
read(12, "", 5) = 0
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
read(12, "", 5) = 0
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0xa2aa1b8, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa317238, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0xa317238, FUTEX_WAIT_PRI
Bug#596115: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: varkon |1.18B-1 | source, alpha, amd64, hppa, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc varkon-programmer-manual |1.18B-1 | all varkon-user-manual |1.18B-1 | all --- Reason --- RoQA; orphaned, outdated, unused -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/596115 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1otgzg-0004aa...@franck.debian.org
Bug#595393: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: open.app | 0.1+20061029-3 | source open.app | 0.1+20061029-3+b1 | kfreebsd-amd64, kfreebsd-i386 open.app | 0.1+20061029-3+b2 | hurd-i386 open.app | 0.1+20061029-3+b3 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc --- Reason --- RoQA; orphaned, unused, dead upstream -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 595...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/595393 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oth04-0004tl...@franck.debian.org
Bug#596116: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: tkpaint |1.5.4-7 | source, all --- Reason --- RoQA; orphaned, unused, dead upstream, alternatives exist -- 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. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 596...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/596116 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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oth0l-0004yk...@franck.debian.org
