From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26903 invoked by alias); 21 Jan 2009 12:29:13 -0000 Received: (qmail 26894 invoked by uid 22791); 21 Jan 2009 12:29:12 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-ew0-f13.google.com (HELO mail-ew0-f13.google.com) (209.85.219.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 21 Jan 2009 12:29:03 +0000 Received: by ewy6 with SMTP id 6so1676534ewy.2 for ; Wed, 21 Jan 2009 04:29:00 -0800 (PST) Received: by 10.210.67.4 with SMTP id p4mr2746933eba.193.1232540939080; Wed, 21 Jan 2009 04:28:59 -0800 (PST) Received: from ?192.168.1.2? (82-171-113-142.ip.telfort.nl [82.171.113.142]) by mx.google.com with ESMTPS id b33sm15602622ika.15.2009.01.21.04.28.57 (version=SSLv3 cipher=RC4-MD5); Wed, 21 Jan 2009 04:28:58 -0800 (PST) Message-ID: <49771507.6090002@dazjorz.com> Date: Wed, 21 Jan 2009 12:58:00 -0000 From: Sjors Gielen User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Carsten Hey CC: debian-devel@lists.debian.org, debian-win32@lists.debian.org, cygwin@cygwin.com Subject: Re: Hosting the Debian/kCygwin port? References: <49751189.5050609@dazjorz.com> <20090121094825.GF15594@foghorn.stateful.de> <20090121101424.GA5034@const.bordeaux.inria.fr> <20090121101813.GH15594@foghorn.stateful.de> In-Reply-To: <20090121101813.GH15594@foghorn.stateful.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2009-01/txt/msg00631.txt.bz2 Hey, Thanks for all your answers! Carsten Hey wrote: > On Wed, Jan 21, 2009 at 11:14:24AM +0100, Samuel Thibault wrote: >> So maybe debian-win32 could just be awaken since the barring issue >> seems gone? > > This is what I would try first. I hope you are successful with this. > > Carsten I was using Cygwin 1.5 when I started working on this. I indeed noticed that in Cygwin CVS this has been fixed already. Carsten Hey wrote: > debian-cygwin.sf.net is a Debian GNU/w32 port and I see no reason to > remove the project page on Sourceforge. Although there are no > releases, there has been some work done (see > http://lists.debian.org/debian-win32/) > and this site should IMHO at least reside for historical reasons. > Maybe there is a chance to reanimate this project or at least reuse > some of the work that has been done or concepts that have been > developed. I started with the idea when I noticed this project. It had been dead for a few years, and I liked the idea and looked into it. I had some contact with the original admin. He added me to the project, created an SVN repository on my request, but refused to make me an admin, which is needed to i.e. modify the project web frontend. When I filed a project takeover, the admin removed my SVN commit access. Everything currently in SVN is mine (and that's not much, but I've got a lot more waiting here, until I can commit it somewhere.) CVS only contains the same old dpkg sources twice, and some binary builds. I'm still waiting for the admin to either accept or reject the project takeover request. I don't have a lot of hope there, he seems to be working against me. I also e-mailed the debian-ports admin, and he said the same as you: there needs to be a base system before it can be hosted there. Base system means gcc, g++, dpkg-dev, etc. For now, I will keep working on the project locally, until I can host everything I have now at Sourceforge. Once I have a base system going, I'll e-mail the debian-ports admin again. Again, thanks for your replies! Sjors -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/