From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Website: Package listing not working + cygport query
Date: Tue, 17 Jun 2014 15:32:00 -0000 [thread overview]
Message-ID: <20140617153200.GA6910@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20140617143111.GF7138@ednor.casa.cgf.cx>
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
next prev parent reply other threads:[~2014-06-17 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 18:19 Website: Package listing not working David Stacey
2014-06-17 14:31 ` Christopher Faylor
2014-06-17 15:32 ` Christopher Faylor [this message]
2014-06-17 15:40 ` Website: Package listing not working + cygport query Christopher Faylor
2014-06-17 18:29 ` David Stacey
2014-06-18 5:04 ` Yaakov Selkowitz
2014-06-18 5:35 ` Christopher Faylor
2014-06-18 9:35 ` Andrey Repin
2014-06-18 10:16 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140617153200.GA6910@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).