Hi,
I checked a bit more:
stable source: no use of versioned python in upstream
oldstable source: "/usr/bin/env python2.3" used by upstream.
(But patched via dpatch)
So nothing like previous upgrade hang or package from other source can
not be the likely reason....
On Fri, Jul 08, 2011 at 03:03:14PM -0600, Bdale Garbee wrote:
> On Fri, 8 Jul 2011 23:21:41 +0900, Osamu Aoki <os...@debian.org> wrote:
> > I do not see the bug reported in my local Debian package which I
> > downloaded from the Debian archive as described below.
>
> I just downloaded a fresh copy of the 4.20.2-1 package and unpacked it,
> and I agree and confirm that the /usr/bin/getmail script has the correct,
> version-less invocation of /usr/bin/python at the top.
Good to hear.
> While I have no memory of it, I am forced to conclude that I must have
> hacked on the script myself to work around a problem at some point in
> the past. Perhaps my default python version at the time was broken? I
> really don't know.
Maybe you might have found issues with python 3.0 when testing and put
those there to avoid it. Did you played with python 3 as
/usr/bin/python?
> In any case, my apologies for the confusion.
No problem.
I think python3 transition is one thing we need to keep an eye on:-)
Osamu
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
