Bug#492933: releaseforge: reportbug fails to upload to SourceForge; may be fixed in new upstream

2008-08-02 Thread Roberto C . Sánchez
On Sat, Aug 02, 2008 at 02:38:58AM -0300, Asheesh Laroia wrote: Just tested them. (side note: new bug in 1.3: It double-lists a few projects of mine.) Yes, I saw that as well. The release 1.3 gives me this error: 2008-08-01 22:35:24,827 - ERROR - sfcomm - (-5, 'No address associated

Bug#492933: releaseforge: reportbug fails to upload to SourceForge; may be fixed in new upstream

2008-08-01 Thread Roberto C . Sánchez
On Tue, Jul 29, 2008 at 05:36:07PM -0700, Asheesh Laroia wrote: Package: releaseforge Version: 1.1-4 Severity: normal Asheesh, I have prepared packages of the new upstream release (1.3) of ReleaseForge. Would it be possible for you to test them out for me? You can obtain them here:

Bug#492933: releaseforge: reportbug fails to upload to SourceForge; may be fixed in new upstream

2008-08-01 Thread Asheesh Laroia
On Sat, 2 Aug 2008, Roberto C. Sánchez wrote: On Tue, Jul 29, 2008 at 05:36:07PM -0700, Asheesh Laroia wrote: Package: releaseforge Version: 1.1-4 Severity: normal Asheesh, I have prepared packages of the new upstream release (1.3) of ReleaseForge. Would it be possible for you to test

Bug#492933: releaseforge: reportbug fails to upload to SourceForge; may be fixed in new upstream

2008-07-29 Thread Asheesh Laroia
Package: releaseforge Version: 1.1-4 Severity: normal When creating a new release, I get this message: 2008-07-29 17:34:31,768 - ERROR - sfcomm - 'liblicense-0.8.tar.gz' Traceback (most recent call last): File /var/lib/python-support/python2.5/ReleaseForge/sfcomm.py, line 451, in