Re: Website: Package listing not working + cygport query

2014-06-18 Thread Corinna Vinschen
On Jun 18 13:34, Andrey Repin wrote: > Greetings, Yaakov Selkowitz! > > >> Yaakov, wouldn't it make sense not to just use 0/0 as user/group when > >> generating packages with cygport by forcing --owner=0, --group=0 to the > >> tar command? I'm not suggesting that this is the right way to fix this

Re: Website: Package listing not working + cygport query

2014-06-18 Thread Andrey Repin
Greetings, Yaakov Selkowitz! >> Yaakov, wouldn't it make sense not to just use 0/0 as user/group when >> generating packages with cygport by forcing --owner=0, --group=0 to the >> tar command? I'm not suggesting that this is the right way to fix this >> particular problem but I don't think it's a

Re: Website: Package listing not working + cygport query

2014-06-17 Thread Christopher Faylor
On Wed, Jun 18, 2014 at 12:04:29AM -0500, Yaakov Selkowitz wrote: >On 2014-06-17 10:32, Christopher Faylor wrote: >> I'm surprised that I haven't seen this before: The name that you used to >> generate your packages was "David Stacey/None". My parser wasn't >> expecting a name with a space and I d

Re: Website: Package listing not working + cygport query

2014-06-17 Thread Yaakov Selkowitz
On 2014-06-17 10:32, Christopher Faylor wrote: I'm surprised that I haven't seen this before: The name that you used to generate your packages was "David Stacey/None". My parser wasn't expecting a name with a space and I didn't detect the fact that the parsing failed (#($& just realized that I f

Re: Website: Package listing not working + cygport query

2014-06-17 Thread David Stacey
On 17/06/14 16:39, Christopher Faylor wrote: On Tue, Jun 17, 2014 at 11:32:00AM -0400, Christopher Faylor wrote: I'm surprised that I haven't seen this before: The name that you used to generate your packages was "David Stacey/None". My parser wasn't expecting a name with a space and I didn't d

Re: Website: Package listing not working + cygport query

2014-06-17 Thread Christopher Faylor
On Tue, Jun 17, 2014 at 11:32:00AM -0400, Christopher Faylor wrote: >I'm surprised that I haven't seen this before: The name that you used to >generate your packages was "David Stacey/None". My parser wasn't >expecting a name with a space and I didn't detect the fact that the >parsing failed (#($&

Re: Website: Package listing not working + cygport query

2014-06-17 Thread Christopher Faylor
On Tue, Jun 17, 2014 at 10:31:11AM -0400, Christopher Faylor wrote: >On Mon, Jun 09, 2014 at 07:19:04PM +0100, David Stacey wrote: >>On the cygwin.com website, none of my packages display their contents >>correctly, e.g.: >> >> https://cygwin.com/packages/x86/keepassx/keepassx-0.4.3-2 >>https:

Re: Website: Package listing not working

2014-06-17 Thread Christopher Faylor
On Mon, Jun 09, 2014 at 07:19:04PM +0100, David Stacey wrote: >On the cygwin.com website, none of my packages display their contents >correctly, e.g.: > > https://cygwin.com/packages/x86/keepassx/keepassx-0.4.3-2 >https://cygwin.com/packages/x86/libpoco-devel/libpoco-devel-1.4.6p3-1 > http

Website: Package listing not working

2014-06-09 Thread David Stacey
On the cygwin.com website, none of my packages display their contents correctly, e.g.: https://cygwin.com/packages/x86/keepassx/keepassx-0.4.3-2 https://cygwin.com/packages/x86/libpoco-devel/libpoco-devel-1.4.6p3-1 https://cygwin.com/packages/x86/doxygen/doxygen-1.8.7-1 All I see is a l