Bug#166180: marked as done (ITP: proxytunnel -- Punching holes in HTTP(S) proxies)
Your message dated Mon, 31 Aug 2009 14:31:48 + with message-id e1mi7va-0001ur...@ries.debian.org and subject line Bug#166180: fixed in proxytunnel 1.9.0-1 has caused the Debian Bug report #166180, regarding ITP: proxytunnel -- Punching holes in HTTP(S) proxies 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.) -- 166180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=166180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wnpp Version: N/A; reported 200210-24 Severity: wishlist Package name: proxytunnel URL: http://proxytunnel.sourceforge.net/ Neat tool to enable ssh-logins to the outside World inside a cooperate Network with http(s)-only Internet-access. Would be nice to have this as debian package. Regards Sven ---End Message--- ---BeginMessage--- Source: proxytunnel Source-Version: 1.9.0-1 We believe that the bug you reported is fixed in the latest version of proxytunnel, which is due to be installed in the Debian FTP archive: proxytunnel_1.9.0-1.diff.gz to pool/main/p/proxytunnel/proxytunnel_1.9.0-1.diff.gz proxytunnel_1.9.0-1.dsc to pool/main/p/proxytunnel/proxytunnel_1.9.0-1.dsc proxytunnel_1.9.0-1_amd64.deb to pool/main/p/proxytunnel/proxytunnel_1.9.0-1_amd64.deb proxytunnel_1.9.0.orig.tar.gz to pool/main/p/proxytunnel/proxytunnel_1.9.0.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 166...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Gilbey j...@debian.org (supplier of updated proxytunnel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 20 Aug 2009 02:10:11 +0100 Source: proxytunnel Binary: proxytunnel Architecture: source amd64 Version: 1.9.0-1 Distribution: unstable Urgency: high Maintainer: Julian Gilbey j...@debian.org Changed-By: Julian Gilbey j...@debian.org Description: proxytunnel - Create tcp tunnels trough HTTPS proxies, for using with SSH Closes: 166180 Changes: proxytunnel (1.9.0-1) unstable; urgency=high . * New upstream version * Initial official Debian release (Closes: #166180) * Rewrite encryption code to use GNUTLS instead of OpenSSL to avoid licence clash issues (code is GPL, which conflicts with OpenSSL licence) Checksums-Sha1: 3fff8807a36793fa9a2635aab3a144068af24259 1008 proxytunnel_1.9.0-1.dsc 51d816125bb9e9bca267d35f861000eb0fa9d80b 46556 proxytunnel_1.9.0.orig.tar.gz fa9157cfeff490b3455fd38d9d1f08451dce69a5 4737 proxytunnel_1.9.0-1.diff.gz c52dfff533e2b3016649f3e89cf6dbfcb20304a8 30936 proxytunnel_1.9.0-1_amd64.deb Checksums-Sha256: c494631a1499f81c873641ad0e59bc20cfa3013bf7bf1e2ebc502b2baca2fbe4 1008 proxytunnel_1.9.0-1.dsc 2ef5bbf8d81ddf291d71f865c5dab89affcc07c4cb4b3c3f23e1e9462721a6b9 46556 proxytunnel_1.9.0.orig.tar.gz fcda68dba5a2cb2fdccbb62138b192b756750fee7bd3e968c979665e53eacceb 4737 proxytunnel_1.9.0-1.diff.gz c2fcaca47e9220ad66d9899a68bf8cb23db62284ae513e5efad5f8782d4f94a9 30936 proxytunnel_1.9.0-1_amd64.deb Files: fa6491d5a066cc6b54bb070139738b77 1008 net optional proxytunnel_1.9.0-1.dsc d74472b89c3f3b3b0abf6bd809ae34c2 46556 net optional proxytunnel_1.9.0.orig.tar.gz a15837b414f105f6f1cc9ff6e91bfc97 4737 net optional proxytunnel_1.9.0-1.diff.gz 9204ae3787a72afbe5c3b6c80eb94567 30936 net optional proxytunnel_1.9.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqNTFUACgkQDU59w/205FleXACg1BV4s2NRh1FaowWsbsayeiMm nxYAn1KWKHwDQWHkymNxQkaYJc3w2G4e =eSp0 -END PGP SIGNATURE- ---End Message---
Bug#166180: marked as done (ITP: proxytunnel -- Punching holes in HTTP(S) proxies)
Your message dated Sun, 16 Mar 2008 11:59:35 -0600 with message-id [EMAIL PROTECTED] and subject line WNPP bug closing has caused the Debian Bug report #166180, regarding ITP: proxytunnel -- Punching holes in HTTP(S) proxies 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 [EMAIL PROTECTED] immediately.) -- 166180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=166180 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: wnpp Version: N/A; reported 200210-24 Severity: wishlist Package name: proxytunnel URL: http://proxytunnel.sourceforge.net/ Neat tool to enable ssh-logins to the outside World inside a cooperate Network with http(s)-only Internet-access. Would be nice to have this as debian package. Regards Sven ---End Message--- ---BeginMessage--- Hello, This is an automatic mail sent to close the ITP you have reported or are involved with. Your ITP wnpp bug is being closed because of the following reasons: - It is, as of today, older than 365 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be closing some bugs that are not intended by owners and submitters (like you) to be closed, for example if the ITP is still of your interest, or there has been some kind of activity around it. In that case, please reopen the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily reopen their bugs ;-). To re-open it, you simply have to mail [EMAIL PROTECTED] with a body text like this: reopen 166180 stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: [EMAIL PROTECTED]. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza [EMAIL PROTECTED]. ---End Message---
Bug#166180: marked as done (ITP: proxytunnel -- Punching holes in HTTP(S) proxies)
Your message dated Sat, 16 Sep 2006 11:59:35 -0600 with message-id [EMAIL PROTECTED] and subject line WNPP bug closing has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: wnpp Version: N/A; reported 200210-24 Severity: wishlist Package name: proxytunnel URL: http://proxytunnel.sourceforge.net/ Neat tool to enable ssh-logins to the outside World inside a cooperate Network with http(s)-only Internet-access. Would be nice to have this as debian package. Regards Sven ---End Message--- ---BeginMessage--- Hello, This is an automatic mail sent to close the ITP you have reported or are involved with. Your ITP wnpp bug is being closed because of the following reasons: - It is, as of today, older than 365 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be closing some bugs that are not intended by owners and submitters (like you) to be closed, for example if the ITP is still of your interest, or there has been some kind of activity around it. In that case, please reopen the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily reopen their bugs ;-). To re-open it, you simply have to mail [EMAIL PROTECTED] with a body text like this: reopen 166180 thanks bts Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: [EMAIL PROTECTED]. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza [EMAIL PROTECTED]. ---End Message---
