On Mon, Apr 09, 2007 at 11:49:17PM +0200, Bernd Zeimetz wrote:
> Heya,
> > Please don't let this get into testing. Updating to a new mechanize now
> > has very likely broken zope3.
> >
>
> would it make sense to ship more than one version of mechanize, as it is
> done with python-snmp for examp
Heya,
> Please don't let this get into testing. Updating to a new mechanize now
> has very likely broken zope3.
>
would it make sense to ship more than one version of mechanize, as it is
done with python-snmp for example? Breakign zope3 would not be a good
idea, but not beeing able to use other
On Mon, Apr 09, 2007 at 11:04:33PM +0200, Bernd Zeimetz wrote:
> Heya,
> >> Could you please package the last upstream version of python-mechanize
> >> (e.g. 0.1.6b)?
> >>
> >>
> > as this is another dependency of Zenoss I'll upgrade mechanize in svn to
> > the latest upstream version so
Heya,
>> Could you please package the last upstream version of python-mechanize
>> (e.g. 0.1.6b)?
>>
>>
> as this is another dependency of Zenoss I'll upgrade mechanize in svn to the
> latest upstream version so we have somethign to test.
>
>
>
Jérémy updated it when I was writing th
Heya,
>
> Could you please package the last upstream version of python-mechanize
> (e.g. 0.1.6b)?
>
as this is another dependency of Zenoss I'll upgrade mechanize in svn to the
latest upstream version so we have somethign to test.
Cheers,
Bernd
--
Bernd Zeimetz
<[EMAIL PROTECTED]>
Package: python-mechanize
Severity: wishlist
Hello,
Could you please package the last upstream version of python-mechanize
(e.g. 0.1.6b)?
Regards,
Arnaud Fontaine
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
6 matches
Mail list logo
