Website: Package listing not working

Website: Package listing not working

[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 long list of zeros. Other people's package listings are 
fine, e.g.:

https://cygwin.com/packages/x86/libopenssl100/libopenssl100-1.0.1h-1
https://cygwin.com/packages/x86/texlive-collection-basic/texlive-collection-basic-20130529-1

Is this a website problem? Or have I managed to get something seriously 
wrong in building my packages? I'm using Firefox 29.0.1 under Fedora 20 
64-bit, although looking at the source code it seems as though the 
browser is rendering the pages correctly.

Dave.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Website: Package listing not working

[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
>     https://cygwin.com/packages/x86/doxygen/doxygen-1.8.7-1
>
>All I see is a long list of zeros. Other people's package listings are 
>fine, e.g.:
>
>https://cygwin.com/packages/x86/libopenssl100/libopenssl100-1.0.1h-1
>https://cygwin.com/packages/x86/texlive-collection-basic/texlive-collection-basic-20130529-1
>
>Is this a website problem? Or have I managed to get something seriously 
>wrong in building my packages? I'm using Firefox 29.0.1 under Fedora 20 
>64-bit, although looking at the source code it seems as though the 
>browser is rendering the pages correctly.

It's not a website problem.  It is apparently a problem with the "upset" script
which generates these listings.  I'm investigating.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Website: Package listing not working + cygport query

[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://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 long list of zeros. Other people's package listings are 
>>fine, e.g.:
>>
>>https://cygwin.com/packages/x86/libopenssl100/libopenssl100-1.0.1h-1
>>https://cygwin.com/packages/x86/texlive-collection-basic/texlive-collection-basic-20130529-1
>>
>>Is this a website problem? Or have I managed to get something seriously 
>>wrong in building my packages? I'm using Firefox 29.0.1 under Fedora 20 
>>64-bit, although looking at the source code it seems as though the 
>>browser is rendering the pages correctly.
>
>It's not a website problem.  It is apparently a problem with the "upset" script
>which generates these listings.  I'm investigating.

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 forgot to fix that).  So it
was just outputting a '0' size, one per line.

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 good idea to leak people's
names and groups out onto the interwebs if we can help it.  It will also
make the packages slightly smaller.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Website: Package listing not working + cygport query

[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 (#($& just realized that I forgot to fix that).  So it
>was just outputting a '0' size, one per line.

Just to be clear: This was 100% my problem.  You should have been able
to use any name you want in the tar file and my script should have been
robust enough to handle it.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Website: Package listing not working + cygport query

[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 detect the fact that the
>> parsing failed (#($& just realized that I forgot to fix that).  So it
>> was just outputting a '0' size, one per line.
> Just to be clear: This was 100% my problem.  You should have been able
> to use any name you want in the tar file and my script should have been
> robust enough to handle it.

Thanks for looking at this. These two links are working now:

https://cygwin.com/packages/x86/keepassx/keepassx-0.4.3-2
https://cygwin.com/packages/x86/doxygen/doxygen-1.8.7-1

But these still give a column of zeros:

https://cygwin.com/packages/x86/libpoco-devel/libpoco-devel-1.4.6p3-1
https://cygwin.com/packages/x86/perl-Text-CSV/perl-Text-CSV-1.32-1
https://cygwin.com/packages/x86/perl-Text-CSV_XS/perl-Text-CSV_XS-1.09-1

I've obviously managed to do something else that you weren't expecting - 
sorry!

Dave.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Website: Package listing not working + cygport query

[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 forgot to fix that).  So it
> was just outputting a '0' size, one per line.
>
> 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 good idea to leak people's
> names and groups out onto the interwebs if we can help it.  It will also
> make the packages slightly smaller.

That would undermine any legitimate specification of gid/uid.  I would 
like to see how this is handled in the Linux distros first.


Yaakov


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Website: Package listing not working + cygport query

[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 didn't detect the fact that the
>> parsing failed (#($& just realized that I forgot to fix that).  So it
>> was just outputting a '0' size, one per line.
>>
>> 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 good idea to leak people's
>> names and groups out onto the interwebs if we can help it.  It will also
>> make the packages slightly smaller.
>
>That would undermine any legitimate specification of gid/uid.  I would 
>like to see how this is handled in the Linux distros first.

I don't see how the random uid/gids of a user would ever be legitimate.
Some released rpm packages do contain (incorrectly, imo) the uid/gid of
the build system that created them but rpm does have a mechanism for
specifying ownership.  If it was really important that arbitrary
ownership must be assigned for some package then it seems like that
would be another cygport enhancement since there is no easy way for
a package maintainer to force their uid to some other value.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Website: Package listing not working + cygport query

[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 good idea to leak people's
>> names and groups out onto the interwebs if we can help it.  It will also
>> make the packages slightly smaller.

> That would undermine any legitimate specification of gid/uid.  I would 
> like to see how this is handled in the Linux distros first.

IMO, if you DO need to have specific ownership on specific files, you ought to
use postinstall scripts to amend the situation to your expectations.

P.S.
The packages I personally know use 'install' to place specific files with
specific uid/gid/access bits.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 18.06.2014, <13:30>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Website: Package listing not working + cygport query

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]

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
> >> particular problem but I don't think it's a good idea to leak people's
> >> names and groups out onto the interwebs if we can help it.  It will also
> >> make the packages slightly smaller.
> 
> > That would undermine any legitimate specification of gid/uid.  I would 
> > like to see how this is handled in the Linux distros first.
> 
> IMO, if you DO need to have specific ownership on specific files, you ought to
> use postinstall scripts to amend the situation to your expectations.
> 
> P.S.
> The packages I personally know use 'install' to place specific files with
> specific uid/gid/access bits.

Another point is, the ownership of the files in the tar file is pretty
much useless.  They reflect another system with different user accounts,
and the installer (be it rpm or our setup) use different accounts to
create the files under anyway.  Setting the uid/gid values in our tar
files to some arbitrary fixed values like 0/0 or 544/544 is fine.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]