Your message dated Sat, 10 Dec 2016 17:46:47 +0000
with message-id <[email protected]>
and subject line Bug#847672: Removed package(s) from unstable
has caused the Debian Bug report #614495,
regarding pymsnt: no error reporting
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.)
--
614495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614495
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pymsnt
Version: 0.11.3-5
Severity: important
If pymsnt fails to bind to the file transfer port, e.g.:
<ftJabberPort>8010</ftJabberPort>
then it just does not start. It does not log any error to
/var/log/pymsnt/error.log, nor does it complain on standard
output. This makes it very hard to find out why it's not
starting (going though reams of strace(1) output is how I
found my problem, namely Psi had bound the port already).
Please add relevant error messages when a condition prevents
pymsnt from starting.
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-vserver-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash
Versions of packages pymsnt depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii python 2.6.6-3+squeeze5 interactive high-level object-orie
ii python-central 0.6.16+nmu1 register and build utility for Pyt
ii python-crypto 2.1.0-2 cryptographic algorithms and proto
ii python-openssl 0.10-1 Python wrapper around the OpenSSL
ii python-twisted 10.1.0-3 Event-based framework for internet
Versions of packages pymsnt recommends:
ii python-imaging 1.1.7-2 Python Imaging Library
Versions of packages pymsnt suggests:
ii jabber 1.6.1.1-5 Transitional package for jabber re
ii jabberd14 [jabber] 1.6.1.1-5+b1 Instant messaging server using the
-- Configuration Files:
/etc/pymsnt.conf.xml changed:
<pymsnt>
<!-- This file contains options to be configured by the server administrator.
-->
<!-- Please read through all the options in this file -->
<!-- The JabberID of the transport -->
<jid>msn.rutschle.net</jid>
<!-- The public IP or DNS name of the machine the transport is running on -->
<!-- This is needed for file transfer!! This is also used as the IP address for
outgoing connections -->
<host>192.168.0.250</host>
<!-- The component JID of the transport. Unless you're doing clustering, leave
this alone -->
<!-- <compjid>msn1</compjid> -->
<!-- The name of the transport in the service discovery list. -->
<!-- <discoName>MSN Transport</discoName> -->
<!-- The Twisted reactor to choose. Pick poll or epoll on Linux, kqueue on BSD.
Or leave as default (best found) -->
<!-- <reactor>poll</reactor> -->
<!-- The IP address of the main Jabber server to connect to -->
<mainServer>127.0.0.1</mainServer>
<!-- The TCP port to connect to the Jabber server on (this is the default for
Jabberd2) -->
<port>5557</port>
<!-- The authentication token to use when connecting to the Jabber server -->
<secret>theBigMSNSecret</secret>
<!-- Use Jabber.com's XCP component protocol extensions. -->
<!-- <useXCP/> -->
<!-- The default language to use -->
<lang>en</lang>
<!-- The website of the Jabber service -->
<website>http://www.rutschle.net</website>
<!-- Comment out the following options to disable them, or uncomment them to
enable them -->
<!-- Send email notification messages to users -->
<mailNotifications/>
<!-- Send greeting on login -->
<sessionGreeting>You have just started a session with PyMSNt</sessionGreeting>
<!-- Send message on successful registration -->
<registerMessage>You have successfully registered with PyMSNt</registerMessage>
<!-- Allow users to register with this transport -->
<allowRegister/>
<!-- Get all avatars. If this is set to true then avatars are grabbed for all
your contacts immediately. If false then avatars are only grabbed when you're
in a chat with a contact -->
<getAllAvatars/>
<!-- The amount of time a user has to join a groupchat they are invited to
before the transport makes them leave the room. (MSN protocol requires
autojoining of groupchats) -->
<!-- <groupchatTimeout>120</groupchatTimeout> -->
<!-- File transfer settings -->
<!-- The maximum size of a file transfer (in bytes). For unlimited, comment
out, or set to 0 -->
<ftSizeLimit>524288</ftSizeLimit>
<!-- The maximum rate for file transfer (in bytes). For unlimited, comment out,
or set to 0 -->
<ftRateLimit>2048</ftRateLimit>
<!-- Please give the port to listen for Jabber socks5 transfers on. -->
<ftJabberPort>8010</ftJabberPort>
<!-- Please give the port to listen for HTTP GETs here (Used in old-style OOB
file transfers. Best to leave this disabled unless you know you need it.) -->
<!--<ftOOBPort>8011</ftOOBPort>-->
<!-- Please give the root URL the transport should send to clients. (You can
use an Apache reverse proxy to put this on your ordinary website) -->
<!-- Eg, the transport will listen on port 8011 for HTTP GETs to
/RANDOM_FILE.ext. You can set apache to forward any requests to
http://yourhost.com:80/msn/files/RANDOM_FILE.ext to
http://yourhost.com:8011/RANDOM_FILE.ext. This saves you from opening extra
ports. -->
<!--<ftOOBRoot>http://host.com/msn/files/</ftOOBRoot>-->
<!-- You can choose which users you wish to have as administrators. These users
can perform some tasks with Ad-Hoc commands that others cannot -->
<!--<admins>
<jid>[email protected]</jid>
</admins>-->
<!-- Log settings -->
<!-- The logging level
0 -> No logging
1 -> Log tracebacks
2 -> Log tracebacks, warnings and errors
3 -> Log all sorts of informational (mostly useless stuff)
4 -> Log the MSN protocol code sent
-->
<debugLevel>2</debugLevel>
</pymsnt>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.11.3+hg224-1+rm
Dear submitter,
as the package pymsnt 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 https://bugs.debian.org/847672
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
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
