| 2010-12-02 15:22:27 |
Matthias Andree |
description |
Binary package hint: fetchmail
Greetings,
the 01_fetchmailconf patch to the fetchmail package is bogus and will break as newer Python versions are imported, because it hardcodes paths that have changed in Debian (to use dist-packages), upstream reference http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603861
If automake cannot figure out the proper pythondir from Python, the actual defect (in Python or automake or autoconf) should then be fixed where it actually is, and not sidestepped in fetchmail by hardcoding paths that are bound to change.
I've checked https://launchpad.net/ubuntu/+source/fetchmail/6.3.18-1ubuntu1 and been looking at the fetchmail_6.3.18-1ubuntu1.debian.tar.gz tarball.
AGAIN: DO NOT PATCH @pythondir@ AWAY TO HARDOCD PATHS, but make sure that autoconf + python's libraries work properly. |
Binary package hint: fetchmail
Greetings,
the 01_fetchmailconf patch to the fetchmail package is bogus and will break as newer Python versions are imported, because it hardcodes paths that have changed in Debian (to use dist-packages), upstream reference http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603861
If automake cannot figure out the proper pythondir from Python, the actual defect (in Python or automake or autoconf) should then be fixed where it actually is, and not sidestepped in fetchmail by hardcoding paths that are bound to change.
I've checked https://launchpad.net/ubuntu/+source/fetchmail/6.3.18-1ubuntu1 and been looking at the fetchmail_6.3.18-1ubuntu1.debian.tar.gz tarball.
AGAIN: DO NOT PATCH @pythondir@ AWAY TO HARDOCD PATHS, but make sure that autoconf + python's libraries work properly.
See also: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/669066 |
|
| 2010-12-02 15:22:57 |
Matthias Andree |
description |
Binary package hint: fetchmail
Greetings,
the 01_fetchmailconf patch to the fetchmail package is bogus and will break as newer Python versions are imported, because it hardcodes paths that have changed in Debian (to use dist-packages), upstream reference http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603861
If automake cannot figure out the proper pythondir from Python, the actual defect (in Python or automake or autoconf) should then be fixed where it actually is, and not sidestepped in fetchmail by hardcoding paths that are bound to change.
I've checked https://launchpad.net/ubuntu/+source/fetchmail/6.3.18-1ubuntu1 and been looking at the fetchmail_6.3.18-1ubuntu1.debian.tar.gz tarball.
AGAIN: DO NOT PATCH @pythondir@ AWAY TO HARDOCD PATHS, but make sure that autoconf + python's libraries work properly.
See also: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/669066 |
Binary package hint: fetchmail
Greetings,
the 01_fetchmailconf patch to the fetchmail package is bogus and will break as newer Python versions are imported, because it hardcodes paths that have changed in Debian (to use dist-packages), upstream reference http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603861
If automake cannot figure out the proper pythondir from Python, the actual defect (in Python or automake or autoconf) should then be fixed where it actually is, and not sidestepped in fetchmail by hardcoding paths that are bound to change.
I've checked https://launchpad.net/ubuntu/+source/fetchmail/6.3.18-1ubuntu1 and been looking at the fetchmail_6.3.18-1ubuntu1.debian.tar.gz tarball.
AGAIN: DO NOT PATCH @pythondir@ AWAY TO HARDCODE PATHS, but make sure that autoconf + python's libraries work properly.
See also: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/669066
(not yet sure if that's a duplicate, so not marking as such) |
|
