On Wed, 2010-06-23 at 08:40 -0400, Jason Tishler wrote:
> > I presume you will handle pushing the patches upstream?
>
> Yes, but I might need assistance with (i.e., justifying) some of your
> patches.
Feel free to ask me on the list, or CC me on the bug tracker as
necessary.
> > BTW, ready for p
Cary,
On Wed, Jun 23, 2010 at 07:17:08AM -0700, Cary R. wrote:
> --- On Wed, 6/23/10, Jason Tishler wrote:
> > On Mon, Jun 21, 2010 at 08:11:37PM -0500, Yaakov (Cygwin/X)
> > wrote:
> >
> > > BTW, ready for python3 yet? ;-)
> >
> > No, not really, but I will try to get around to it.
>
> I'm assu
--- On Wed, 6/23/10, Jason Tishler wrote:
> On Mon, Jun 21, 2010 at 08:11:37PM -0500, Yaakov (Cygwin/X)
> wrote:
>
> > BTW, ready for python3 yet? ;-)
>
> No, not really, but I will try to get around to it.
I'm assuming by the emoticon that this is a joke. Many of the
packages do not currentl
Yaakov,
On Mon, Jun 21, 2010 at 08:11:37PM -0500, Yaakov (Cygwin/X) wrote:
> On Mon, 2010-06-21 at 13:42 -0400, Jason Tishler wrote:
> > On Sun, Jun 20, 2010 at 10:41:50PM -0500, Yaakov (Cygwin/X) wrote:
> > > With Jari's packages updated, I think we're close enough that we
> > > should go ahead w
On Mon, 2010-06-21 at 13:42 -0400, Jason Tishler wrote:
> On Sun, Jun 20, 2010 at 10:41:50PM -0500, Yaakov (Cygwin/X) wrote:
> > With Jari's packages updated, I think we're close enough that we
> > should go ahead with the 2.6 upload ASAP.
>
> Done.
>
> Thanks for your help with cygport and your
Yaakov,
On Sun, Jun 20, 2010 at 10:41:50PM -0500, Yaakov (Cygwin/X) wrote:
> On Sat, 2010-06-12 at 21:09 -0400, Jason Tishler wrote:
> > Well, it's more "about" than "on," but I'm ready to release Python
> > 2.6.5-2 and promote it to current.
>
> With Jari's packages updated, I think we're close
On Sat, 2010-06-12 at 21:09 -0400, Jason Tishler wrote:
> Well, it's more "about" than "on," but I'm ready to release Python
> 2.6.5-2 and promote it to current.
With Jari's packages updated, I think we're close enough that we should
go ahead with the 2.6 upload ASAP. Once you upload 2.6.5-2 as s
Jari,
On Tue, Jun 15, 2010 at 04:39:20PM +0300, Jari Aalto wrote:
> I'm working on it and it is really puzzling as the 2.5 install works
> just fine, but installing 2.6 gets to the point fo breakage.
>
> Once I get environment set up, it will be fast to upgrade packages.
How did you resolve your
Corinna Vinschen writes:
> On Jun 13 23:30, Yaakov S wrote:
>> On Sat, 2010-06-12 at 21:09 -0400, Jason Tishler wrote:
>> > Well, it's more "about" than "on," but I'm ready to release Python
>> > 2.6.5-2 and promote it to current.
>> >
>> > However, AFAICT, most of the above packages have not be
On Mon, 2010-06-14 at 14:00 +0200, Corinna Vinschen wrote:
> Which is 10 days ago, unfortunately. Can nobody help him to fix this
> problem?
Besides that it was already *after* the due date. But it's hard to fix
a problem that you can't reproduce.
> NMU?
http://wiki.debian.org/NonMaintainerUpl
On Jun 13 23:30, Yaakov S wrote:
> On Sat, 2010-06-12 at 21:09 -0400, Jason Tishler wrote:
> > Well, it's more "about" than "on," but I'm ready to release Python
> > 2.6.5-2 and promote it to current.
> >
> > However, AFAICT, most of the above packages have not been rebuilt
> > against Python 2.6.
2010/6/14 Yaakov (Cygwin/X):
> On Sat, 2010-06-12 at 21:09 -0400, Jason Tishler wrote:
>> Well, it's more "about" than "on," but I'm ready to release Python
>> 2.6.5-2 and promote it to current.
>>
>> However, AFAICT, most of the above packages have not been rebuilt
>> against Python 2.6.5-1. Shou
On Sat, 2010-06-12 at 21:09 -0400, Jason Tishler wrote:
> Well, it's more "about" than "on," but I'm ready to release Python
> 2.6.5-2 and promote it to current.
>
> However, AFAICT, most of the above packages have not been rebuilt
> against Python 2.6.5-1. Should I release and promote Python 2.6
On Tue, Jun 01, 2010 at 02:51:13PM -0500, Yaakov (Cygwin/X) wrote:
> Today being 01 June, the due date for Python 2.6:
> On Fri, Apr 30, 2010 at 09:24:36AM -0400, Jason Tishler wrote:
> > I will update Cygwin to make 2.6.5-1 (or later) current on or about
> > June 1, 2010.
Well, it's more "about"
"Yaakov (Cygwin/X)"
> Today being 01 June, the due date for Python 2.6:
>> Jari Aalto:
>> > bzr
>> > codeville
>> > getmail
>> > mercurial
>> > offlineimap
>> > planet
>> > python-crypto
>> > python-feedparser
>> > python-paramiko
>> > spambayes
>> > stgit
>> > tailor
>> > urlgrabber
> Yaakov writes:
> Today being 01 June, the due date for Python 2.6:
> On 2010-05-17 03:54, Yaakov (Cygwin/X) wrote:
>> Jari Aalto:
>> > bzr
>> > codeville
>> > getmail
>> > mercurial
>> > offlineimap
>> > planet
>> > python-crypto
>> > python-feedp
Today being 01 June, the due date for Python 2.6:
On 2010-05-17 03:54, Yaakov (Cygwin/X) wrote:
Jari Aalto:
> bzr
> codeville
> getmail
> mercurial
> offlineimap
> planet
> python-crypto
> python-feedparser
> python-paramiko
> spambayes
> stgit
> tailor
> urlgrabber
Jan Nieuwenhuiz
Ping? One week left. Has anyone been working on this?
On 2010-05-17 03:54, Yaakov (Cygwin/X) wrote:
Here are the other packages grouped by maintainer:
Jari Aalto:
> archivemail
> bzr
> codeville
> flawfinder
> getmail
> mercurial
> offlineimap
> planet
> python-crypto
> python-feedp
Here are the other packages grouped by maintainer:
Jari Aalto:
> archivemail
> bzr
> codeville
> flawfinder
> getmail
> mercurial
> offlineimap
> planet
> python-crypto
> python-feedparser
> python-paramiko
> spambayes
> stgit
> tailor
> urlgrabber
> webcheck
Eric Blake:
> asciidoc
Jan Nieuwenh
19 matches
Mail list logo
