rss2email doesn't work properly on jaunty

Bug #338759 reported by Richard Verwayen
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rss2email (Ubuntu)
Fix Released
Undecided
Unassigned
Declined for Jaunty by Christian Reis
Karmic
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: rss2email

When running rss2email, I get a bunch of warnings and even errors

System is running Jaunty (updated from Dapper with any new release)

richard@server:~$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

richard@server:~$ apt-cache policy rss2email
rss2email:
  Installed: 1:2.62-3
  Candidate: 1:2.62-3
  Version table:
 *** 1:2.62-3 0
        500 http://nl.archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status
richard@server:~$

Packages that might be relevant:
ii python-feedparser 4.1-12 Universal Feed Parser for Python
ii python2.4 2.4.6-1ubuntu2 An interactive high-level object-oriented la
ii python2.4-minimal 2.4.6-1ubuntu2 A minimal subset of the Python language (ver
ii python2.6 2.6.1-1ubuntu1 An interactive high-level object-oriented la
ii python2.6-minimal 2.6.1-1ubuntu1 A minimal subset of the Python language (ver
ii python3-minimal 3.0.1-0ubuntu2 A minimal subset of the Python language (def
ii python3.0 3.0.1-0ubuntu5 An interactive high-level object-oriented la
ii python3.0-minimal 3.0.1-0ubuntu5 A minimal subset of the Python language (ver

Expected behaviour:
rss2email should read feeds and send them as emails.

Behaviour shown:
Adding new feeds to the list works, but throws a bunch of warnings.
Running r2e to fetch feeds does bail out with the following error:

r2e RUN (does not work)

richard@server:~$ r2e run
/usr/share/rss2email/rss2email.py:222: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import cPickle as pickle, md5, time, os, traceback, urllib2, sys, types
/usr/share/rss2email/rss2email.py:233: DeprecationWarning: the mimify module is deprecated; use the email package instead
  import mimify; from StringIO import StringIO as SIO; mimify.CHARSET = 'utf-8'
/usr/share/rss2email/rss2email.py:188: DeprecationWarning: os.popen2 is deprecated. Use the subprocess module.
  i, o = os.popen2(["/usr/sbin/sendmail", recipient])
sendmail: fatal: Recipient addresses must be specified on the command line or via the -t option

Fatal error: sendmail exited with code 19200
richard@server:~$

r2e ADD (works)

richard@server:~$ r2e add http://planet.ubuntulinux.org/rss20.xml
/usr/share/rss2email/rss2email.py:222: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import cPickle as pickle, md5, time, os, traceback, urllib2, sys, types
/usr/share/rss2email/rss2email.py:233: DeprecationWarning: the mimify module is deprecated; use the email package instead
  import mimify; from StringIO import StringIO as SIO; mimify.CHARSET = 'utf-8'
richard@server:~$

r2e LIST (works)

richard@server:~$ r2e list
/usr/share/rss2email/rss2email.py:222: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import cPickle as pickle, md5, time, os, traceback, urllib2, sys, types
/usr/share/rss2email/rss2email.py:233: DeprecationWarning: the mimify module is deprecated; use the email package instead
  import mimify; from StringIO import StringIO as SIO; mimify.CHARSET = 'utf-8'
default email: ys76()ubuntu.com
1: http://planet.ubuntulinux.org/rss20.xml (default: ys76()ubuntu.com)
richard@server:~$

r2e DELETE (works)

richard@server:~$ r2e delete 1
/usr/share/rss2email/rss2email.py:222: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import cPickle as pickle, md5, time, os, traceback, urllib2, sys, types
/usr/share/rss2email/rss2email.py:233: DeprecationWarning: the mimify module is deprecated; use the email package instead
  import mimify; from StringIO import StringIO as SIO; mimify.CHARSET = 'utf-8'
W: deleting feed http://planet.ubuntulinux.org/rss20.xml
richard@server:~$

Revision history for this message
Lindsey Smith (lindsey-smith) wrote :

The deprecation warnings have been fixed in v2.65, see:
http://rss2email.infogami.com/blog/

I would like more information on the error though as I've never seen that happen before. I tested on Hardy and Hardy LTS and it worked as expected. I do see that it looks as if your target email address was "ys76()ubuntu.com" rather than "<email address hidden>", which would definitely cause problems.

Revision history for this message
Richard Verwayen (ys76) wrote : Re: [Bug 338759] Re: rss2email doesn't work properly on jaunty

On Fri, Mar 06, 2009 at 07:08:44PM -0000, Lindsey Smith wrote:
> The deprecation warnings have been fixed in v2.65, see:
> http://rss2email.infogami.com/blog/
>
> I would like more information on the error though as I've never seen
> that happen before. I tested on Hardy and Hardy LTS and it worked as
> expected. I do see that it looks as if your target email address was
> "ys76()ubuntu.com" rather than "<email address hidden>", which would definitely
> cause problems.
Just redacted the email...

It was running fine on hardy, but stopped working on jaunty (I am not
sure, whether it was related to the install of python v3)

Best regards

Richard

Revision history for this message
Lindsey Smith (lindsey-smith) wrote :

Hmm, that's good to know. I'm upgrading one of my hardy boxes to
intrepid, which seems to have the same version of postfix as jaunty.
Maybe I can get python 3 on it as well.

On Fri, Mar 6, 2009 at 11:26 AM, Richard Verwayen <email address hidden> wrote:
>
> On Fri, Mar 06, 2009 at 07:08:44PM -0000, Lindsey Smith wrote:
>> The deprecation warnings have been fixed in v2.65, see:
>> http://rss2email.infogami.com/blog/
>>
>> I would like more information on the error though as I've never seen
>> that happen before. I tested on Hardy and Hardy LTS and it worked as
>> expected. I do see that it looks as if your target email address was
>> "ys76()ubuntu.com" rather than "<email address hidden>", which would definitely
>> cause problems.
> Just redacted the email...
>
> It was running fine on hardy, but stopped working on jaunty (I am not
> sure, whether it was related to the install of python v3)
>
> Best regards
>
> Richard
>
> --
> rss2email doesn't work properly on jaunty
> https://bugs.launchpad.net/bugs/338759
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Lindsey Smith (lindsey-smith) wrote :

On second reading, current versions of rss2email will be incompatible
with Python v3.x so if it can run at all, it was using Python v2.x.

On Fri, Mar 6, 2009 at 11:26 AM, Richard Verwayen <email address hidden> wrote:
>
> On Fri, Mar 06, 2009 at 07:08:44PM -0000, Lindsey Smith wrote:
>> The deprecation warnings have been fixed in v2.65, see:
>> http://rss2email.infogami.com/blog/
>>
>> I would like more information on the error though as I've never seen
>> that happen before. I tested on Hardy and Hardy LTS and it worked as
>> expected. I do see that it looks as if your target email address was
>> "ys76()ubuntu.com" rather than "<email address hidden>", which would definitely
>> cause problems.
> Just redacted the email...
>
> It was running fine on hardy, but stopped working on jaunty (I am not
> sure, whether it was related to the install of python v3)
>
> Best regards
>
> Richard
>
> --
> rss2email doesn't work properly on jaunty
> https://bugs.launchpad.net/bugs/338759
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Tanel Külaots (mou) wrote :

Seems like this bug is a result of http://bugs.python.org/issue5329
Python 2.6 does not accept sequence as argument for os.open2. Changing line 188 in rss2email.py from
i, o = os.popen2(["/usr/sbin/sendmail", recipient])
to
i, o = os.popen2("/usr/sbin/sendmail " + recipient)
fixed it for me.

Ubuntu Jaunty
rss2email.py version 2.62
python version 2.6.1

Revision history for this message
Nato (nato-launchpad) wrote :

r2e run stopped working on upgrading from intrpid to jaunty as described.

Tanel Külaots workaround makes it work perfectly (although the deprecation warnings still come up).

Thanks!

Revision history for this message
Paul Sinnett (paul-sinnett) wrote :

Fix worked for me too

Revision history for this message
Lindsey Smith (lindsey-smith) wrote :

As noted above, this is fixed in the upstream v2.65 release and appears to be fixed (including deprecation warnings) in the karmic repository.

http://changelogs.ubuntu.com/changelogs/pool/universe/r/rss2email/rss2email_2.65-1/changelog

Christian Reis (kiko)
Changed in rss2email (Ubuntu):
status: New → Confirmed
Revision history for this message
Christian Reis (kiko) wrote :

And since that version is already included in jaunty as well I think this is no longer a Jaunty issue. If you find that not to be true let me know. The DeprecationWarnings remain, btw.

Changed in rss2email (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Christian Reis (kiko) wrote :

Actually, I just double-checked and that's not exactly true; while it is indeed fixed in Karmic no backport has been done for Jaunty.

Changed in rss2email (Ubuntu):
status: Fix Released → Invalid
status: Invalid → Confirmed
Christian Reis (kiko)
Changed in rss2email (Ubuntu):
status: Confirmed → New
status: New → Confirmed
Revision history for this message
Adam Collard (adam-collard) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Lucid Lynx. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information.

Changed in rss2email (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Karmic has long since stopped to receive any updates. Marking the Karmic task for this ticket as "Won't Fix".

Changed in rss2email (Ubuntu Karmic):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.