add-apt-repository crashed with IOError in save()

[Erik Johansson-Evegård]

Traceback (most recent call last):
  File "/usr/bin/add-apt-repository", line 65, in <module>
    if not sp.add_source_from_line(line):
  File "/usr/lib/python2.6/dist-packages/softwareproperties/SoftwareProperties.py", line 639, in add_source_from_line
    self.set_modified_sourceslist()
  File "/usr/lib/python2.6/dist-packages/softwareproperties/SoftwareProperties.py", line 425, in set_modified_sourceslist
    self.save_sourceslist()
  File "/usr/lib/python2.6/dist-packages/softwareproperties/SoftwareProperties.py", line 589, in save_sourceslist
    self.sourceslist.save()
  File "/usr/lib/python2.6/dist-packages/aptsources/sourceslist.py", line 367, in save
    files[source.file] = open(source.file, "w")
IOError: [Errno 2] No such file or directory: u'/etc/apt/sources.list.d//ricotz-testing-maverick.list'

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: python-software-properties 0.76
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Tue Aug 17 11:05:10 2010
ExecutablePath: /usr/bin/add-apt-repository
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/add-apt-repository ppa:ricotz/testing
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:ricotz/testing']
SourcePackage: software-properties
Title: add-apt-repository crashed with IOError in save()
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #624966, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.