From: Paul de Vrieze <gentoo-user@devrieze.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Breakage in the portage tree
Date: Thu, 20 Feb 2003 13:33:05 +0100 [thread overview]
Message-ID: <200302201333.13241.gentoo-user@devrieze.net> (raw)
In-Reply-To: <3611.213.206.130.130.1045741886.squirrel@mirkwood.egregious.org.uk>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 620 bytes --]
On Thursday 20 February 2003 12:51, Gareth John wrote:
> One of the ebuilds in question had a misspelt library in it's DEPENDs, and
> the other two had syntax errors - one was missing a closing brace, and the
> other had some random characers appended to the end of the file.
>
There are indeed numerous ebuilds with missing end braces. My guess is that
there is some bug in either cvs or rsync that omits them. Probably because
they are the last character in the file (there is no newline to follow)
Paul
--
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.cs.kun.nl/~pauldv
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-02-20 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 11:51 [gentoo-dev] Breakage in the portage tree Gareth John
2003-02-20 12:33 ` Paul de Vrieze [this message]
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=200302201333.13241.gentoo-user@devrieze.net \
--to=gentoo-user@devrieze.net \
--cc=gentoo-dev@gentoo.org \
/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