fetchmailconf: fetchmailconf.py': [Errno 2] No such file or directory

Bug #669066 reported by James Pinkster
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
fetchmail (Debian)
Fix Released
Unknown
fetchmail (Ubuntu)
Fix Released
Undecided
Unassigned
Maverick
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: fetchmail

Description: Ubuntu 10.10
Release: 10.10

fetchmailconf:
  Installed: 6.3.17-4ubuntu1
  Candidate: 6.3.17-4ubuntu1
  Version table:
 *** 6.3.17-4ubuntu1 0
        500 http://mirror.aarnet.edu.au/pub/ubuntu/archive/ maverick/universe amd64 Packages
        100 /var/lib/dpkg/status

When first running fetchmailconf got the following error.
/usr/bin/python: can't open file '/usr/lib/python2.6/site-packages/fetchmailconf.py': [Errno 2] No such file or directory

Fixed by editing
/usr/bin/fetchmailconf
and changing
exec /usr/bin/python /usr/lib/`pyversions -d`/site-packages/fetchmailconf.py "$@"
to
exec /usr/bin/python /usr/share/pyshared/fetchmailconf.py "$@"

Revision history for this message
Matthias Andree (matthias-andree) wrote :

Caused by a bogus Ubuntu-specific patch that propagated back to Debian.
See https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/684228 - and note that this Bug (669066) should have been forwarded already.

Revision history for this message
Matthias Andree (matthias-andree) wrote :

confirmed in Debian, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603861 - please someone mark this as grave bug.

Changed in fetchmail (Ubuntu):
status: New → Confirmed
Revision history for this message
Artur Rona (ari-tczew) wrote :

Please open task on maverick - I'll process it through SRU.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package fetchmail - 6.3.18-2ubuntu1

---------------
fetchmail (6.3.18-2ubuntu1) natty; urgency=low

  * Merge from Debian unstable. Remaining changes: (LP: #685065)
    - debian/init, debian/fetchmail.postinst: don't stop fetchmail in
      runlevels [06], the default 'killall' handler should be sufficient
      because fetchmail writes are properly completed before telling the
      server it's ok to delete.
    - This upload fixes bug with wrong path. (LP: #669066, Closes: #603861)

fetchmail (6.3.18-2) unstable; urgency=low

  * Fix python module path for fetchmailconf (Closes: #603861).
 -- Artur Rona <email address hidden> Sat, 04 Dec 2010 03:07:12 +0100

Changed in fetchmail (Ubuntu):
status: Confirmed → Fix Released
Changed in fetchmail (Debian):
status: Unknown → Fix Released
Revision history for this message
Artur Rona (ari-tczew) wrote :
Revision history for this message
Artur Rona (ari-tczew) wrote :

I attached debdiff for SRU maverick. Needs a sponsor for main.

Changed in fetchmail (Ubuntu Maverick):
status: New → Confirmed
Revision history for this message
Benjamin Drung (bdrung) wrote :

Uploaded to maverick-proposed.

Changed in fetchmail (Ubuntu Maverick):
status: Confirmed → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted fetchmail into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Artur Rona (ari-tczew) wrote :

Test passed fine.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package fetchmail - 6.3.17-4ubuntu1.1

---------------
fetchmail (6.3.17-4ubuntu1.1) maverick-proposed; urgency=low

  * debian/patches/04_fetchmailconf_python2.6.patch: Fix python module
    path for fetchmailconf. Cherry-pick from natty/sid.
    (LP: #669066, Closes: #603861)
 -- Artur Rona <email address hidden> Tue, 28 Dec 2010 20:38:37 +0100

Changed in fetchmail (Ubuntu Maverick):
status: Fix Committed → Fix Released
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.