On Fri, Oct 29, 2004 at 10:45:PM, Christopher Faylor wrote:
>On Fri, Oct 29, 2004 at 06:09:34PM -0400, Buchbinder, Barry (NIH/NIAID)
wrote:
>>Out of curiosity, why is the policy to remove a package just because
>>the maintainer has abandoned it? If there are no outstanding problems,
>>what would
Reini Urban wrote:
It happens i.e. often for me when using the generic-build-script, if
invoking with install or reconf which does rm -rf .build / .inst and
having an explorer shell open in one of the (sub)directories to be
removed from the script -> it seems to hang and it is always rm.
Using the
David A. Cobb schrieb:
Gerrit P. Haase wrote:
David A. Cobb wrote:
++rm.exe< getting 98% of the CPU time and not making any
progress. Watching the handles display, I see an open handle on what
must be the first *.deb file found so I'm pretty sure of the "no
progress -= stuck!" diagnosis.
I
Gerrit P. Haase wrote:
David A. Cobb wrote:
++rm.exe< getting 98% of the CPU time and not making any
progress. Watching the handles display, I see an open handle on what
must be the first *.deb file found so I'm pretty sure of the "no
progress -= stuck!" diagnosis.
If there is a Windows p
On Fri, Oct 29, 2004 at 06:09:34PM -0400, Buchbinder, Barry (NIH/NIAID) wrote:
>Out of curiosity, why is the policy to remove a package just because the
>maintainer has abandoned it? If there are no outstanding problems, what
>would be the harm of leaving it in until a problem emerges?
Out of cur
Buchbinder, Barry (NIH/NIAID) schrieb:
At Friday, October 29, 2004 1:28 PM, Christopher Faylor wrote:
Since Robert Collins is no longer actively involved with the Cygwin
community, this package is now unmaintained.
If no one wants to claim it within the next week or so, I'll probably
remove it from
At Friday, October 29, 2004 1:28 PM, Christopher Faylor wrote:
> Since Robert Collins is no longer actively involved with the Cygwin
> community, this package is now unmaintained.
>
> If no one wants to claim it within the next week or so, I'll probably
> remove it from the distribution.
>
> cgf
David A. Cobb wrote:
++rm.exe< getting 98% of the CPU time and not making any
progress. Watching the handles display, I see an open handle on what
must be the first *.deb file found so I'm pretty sure of the "no
progress -= stuck!" diagnosis.
If there is a Windows process which has a handl
On Fri, Oct 29, 2004 at 11:54:27AM -0600, Mark Paulus wrote:
>My company is apparently working on getting my
>assignment worked out, so if/when they do, I would
>be interested in taking on this package.
You don't need an assignment to maintain a package. That's just for
making changes to the cyg
My company is apparently working on getting my
assignment worked out, so if/when they do, I would
be interested in taking on this package.
On Fri, 29 Oct 2004 13:27:35 -0400, Christopher Faylor wrote:
>On Fri, Oct 29, 2004 at 01:07:23PM -0400, David A. Cobb wrote:
>>Getting tired of loading disk
David A. Cobb schrieb:
Getting tired of loading disks, I structured a local mirror of the
Debian directory structure and tried running Cygwin
dpkg-scanpackages. I expected it to take a while, so I wasn't
surprised - I just went and make some more coffee. But after 20
minutes I suspected something
On Fri, Oct 29, 2004 at 01:07:23PM -0400, David A. Cobb wrote:
>Getting tired of loading disks, I structured a local mirror of the
>Debian directory structure and tried running Cygwin
>dpkg-scanpackages. I expected it to take a while, so I wasn't
>surprised - I just went and make some more coffee.
Getting tired of loading disks, I structured a local mirror of the
Debian directory structure and tried running Cygwin
dpkg-scanpackages. I expected it to take a while, so I wasn't
surprised - I just went and make some more coffee. But after 20
minutes I suspected something was wrong and fired up
13 matches
Mail list logo
