Bug#654680: python-html2text: 3.200.1-1 breaks parsing of feeds within rss2email

2012-01-06 Thread Aaron Swartz
Yikes! Sorry, fixed in 3.200.2.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#654680: python-html2text: 3.200.1-1 breaks parsing of feeds within rss2email

2012-01-06 Thread Aaron Swartz
Here's the patch:

https://github.com/aaronsw/html2text/commit/d32885c1cd77a17625fe94299896385039373ae7

The @@ was a note to myself to check to see if anything used unescape
before I removed it. Obviously I forgot to do that.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#457318: the importance of qmail

2008-08-22 Thread Aaron Swartz
Postfix had yet another security hole the other week:
http://www.debian.org/security/2008/dsa-1629

Can't we include at least one mailer for people who care about
security? (Let alone reliability and elegance.)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#460542: logrotate spins out of control when files are missing

2008-01-13 Thread Aaron Swartz
Package: logrotate
Version: 3.7.1-3
Severity: critical
Justification: breaks unrelated software


I woke up this morning to find my webserver (lighttpd) unresponsive and 
logrotate 
using up 100% CPU. When I ran strace on logrotate I found:

rename(/service/lighttpd/logs/error.log.638155266.gz, 
/service/lighttpd/logs/error.log.638155267.gz) = -1 ENOENT (No such file or 
directory)
rename(/service/lighttpd/logs/error.log.638155265.gz, 
/service/lighttpd/logs/error.log.638155266.gz) = -1 ENOENT (No such file or 
directory)
rename(/service/lighttpd/logs/error.log.638155264.gz, 
/service/lighttpd/logs/error.log.638155265.gz) = -1 ENOENT (No such file or 
directory)
rename(/service/lighttpd/logs/error.log.638155263.gz, 
/service/lighttpd/logs/error.log.638155264.gz) = -1 ENOENT (No such file or 
directory)
rename(/service/lighttpd/logs/error.log.638155262.gz, 
/service/lighttpd/logs/error.log.638155263.gz) = -1 ENOENT (No such file or 
directory)
rename(/service/lighttpd/logs/error.log.638155261.gz, 
/service/lighttpd/logs/error.log.638155262.gz) = -1 ENOENT (No such file or 
directory)
rename(/service/lighttpd/logs/error.log.638155260.gz, 
/service/lighttpd/logs/error.log.638155261.gz) = -1 ENOENT (No such file or 
directory)
rename(/service/lighttpd/logs/error.log.638155259.gz, 
/service/lighttpd/logs/error.log.638155260.gz) = -1 ENOENT (No such file or 
directory)
rename(/service/lighttpd/logs/error.log.638155258.gz, 
/service/lighttpd/logs/error.log.638155259.gz) = -1 ENOENT (No such file or 
directory)

Apparently it had missed a lighttpd log file or something and was now 
proceeding 
to logrotate every imaginary file it could think of. (It's hard to be sure of 
exactly what's going on without looking at the code.)

I killed it and the site came back, but I thought a developer would know better 
what's going on.

I haven't changed the logrotate conf files in months and this has never 
happened 
before. The relevant config is:

/service/lighttpd/logs/*.log {
weekly
missingok
copytruncate
rotate 9
compress
notifempty
sharedscripts
postrotate
   if [ -f /var/run/lighttpd.pid ]; then \
 if [ -x /usr/sbin/invoke-rc.d ]; then \
invoke-rc.d lighttpd force-reload  /dev/null; \
 else \
/etc/init.d/lighttpd force-reload  /dev/null; \
 fi; \
   fi;
endscript
}

-- Package-specific info:
Contents of /etc/logrotate.d
total 24
-rw-r--r-- 1 root root 240 Jun 19  2007 apache2
-rw-r--r-- 1 root root  79 Sep  3  2006 aptitude
-rw-r--r-- 1 root root  69 Dec 15  2006 backupninja
-rw-r--r-- 1 root root 111 Oct 13  2006 dpkg
-rw-r--r-- 1 root root 488 Dec 18 05:11 lighttpd
-rw-r--r-- 1 root root 153 Aug 15 01:50 postgresql-common


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.29-xen
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages logrotate depends on:
ii  base-passwd3.5.11Debian base system master password
ii  cron   3.0pl1-100management of regular background p
ii  libc6  2.3.6.ds1-13etch4 GNU C Library: Shared libraries
ii  libpopt0   1.10-3lib for parsing cmdline parameters
ii  libselinux11.32-3SELinux shared libraries

Versions of packages logrotate recommends:
ii  mailx1:8.1.2-0.20050715cvs-1 A simple mail user agent

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#382838: (no subject)

2006-08-16 Thread Aaron Swartz

Aaron, could web.py work without flup installed at all? As far as I can
tell my web.py app is running as a simple CGI invoked by Apache; I have
no fastcgi installed.


web.py works without flup, but it requires using built-in web server
or something like that, since it uses flup for both CGI and FastCGI.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#382838: ImportError: from flup.server.fcgi import WSGIServer

2006-08-13 Thread Aaron Swartz

Hmm, odd, it seems like python-flup should be a requirement of python-webpy:

http://packages.debian.org/testing/python/python-flup

Very happy to see you're trying web.py, though! Hope it's been OK.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#354061: trac: installs for python2.3 but scripts use latest version

2006-02-25 Thread Aaron Swartz
 You dont have python2.3 at all?

No, of course I have 2.3; that's where the trac packages get
installed. It just doesn't execute the corresponding Python binary and
so it can't see them.



Bug#320185: rss2email: non-ASCII long header encoding patch

2005-11-09 Thread Aaron Swartz
 The patch encodes header (field body), not message body.

Oh whoops, you're right, I was misreading the last clause. That looks
pretty reasonable then.



Bug#320185: rss2email: non-ASCII long header encoding patch

2005-11-08 Thread Aaron Swartz
The latest patch seems to always QP_CORRUPT the message. Why?

See http://cr.yp.to/smtp/8bitmime.html for why this is a bad idea.



Bug#275510: #275510: URL improperly de-htmlentitied

2005-03-14 Thread Aaron Swartz
 Apparently it's http://nu.nl/deeplink_rss2/index.jsp?r=Algemeen

Yeah, so that actually says:

linkhttp://www.nu.nl/news.jsp?n=496739amp;amp;c=11/link

which once decoded becomes:

linkhttp://www.nu.nl/news.jsp?n=496739amp;c=11/link

so it looks like r2e is doing the right thing.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#275510: #275510: URL improperly de-htmlentitied

2005-03-13 Thread Aaron Swartz
 An xml dump of the feed was included in the bug report

A full one? I see only a very partial one

 (http://bugs.debian.org/275510), but AFAICS, the URL: bit comes from
 rss2email and is not data that is processed by the feed parser:
 
 else:
 message += text/plain
 content = 
 unu(content).strip() + \n\nURL: +link

yes, but link comes from feedparser


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]