From: Chema Alonso <nimiux@gentoo.org>
To: gentoo-lisp@lists.gentoo.org
Subject: Re: [gentoo-lisp] Stabilization of last versions of sbcl and asdf on amd64
Date: Wed, 11 Dec 2013 15:02:21 +0100 [thread overview]
Message-ID: <20131211140217.GA8049@filladhoo> (raw)
In-Reply-To: <alpine.LFD.2.03.1312101721140.12439@star.inp.nsk.su>
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
On Tue, Dec 10, 2013 at 05:23:29PM +0700, grozin@gentoo.org wrote:
> On Tue, 10 Dec 2013, Chema Alonso wrote:
> > I tested it on an stable amd64 system, no problems found apart from some
> > 'cosmetic' warnings found by repoman:
> >
> > ebuild.minorsyn 12
> > dev-lisp/sbcl/sbcl-1.0.55-r1.ebuild: Ebuild contains leading spaces on line: 50
> > dev-lisp/sbcl/sbcl-1.0.55-r1.ebuild: Ebuild contains leading spaces on line: 62
> > dev-lisp/sbcl/sbcl-1.0.55-r2.ebuild: Ebuild contains leading spaces on line: 51
> > dev-lisp/sbcl/sbcl-1.0.55-r2.ebuild: Ebuild contains leading spaces on line: 64
> > dev-lisp/sbcl/sbcl-1.1.10.ebuild: Ebuild contains leading spaces on line: 57
> > dev-lisp/sbcl/sbcl-1.1.10.ebuild: Ebuild contains leading spaces on line: 70
> > dev-lisp/sbcl/sbcl-1.1.11.ebuild: Ebuild contains leading spaces on line: 57
> > dev-lisp/sbcl/sbcl-1.1.11.ebuild: Ebuild contains leading spaces on line: 70
> > dev-lisp/sbcl/sbcl-1.1.12.ebuild: Ebuild contains leading spaces on line: 57
> > dev-lisp/sbcl/sbcl-1.1.12.ebuild: Ebuild contains leading spaces on line: 70
> > dev-lisp/sbcl/sbcl-1.1.14.ebuild: Ebuild contains leading spaces on line: 56
> > dev-lisp/sbcl/sbcl-1.1.14.ebuild: Ebuild contains leading spaces on line: 69
> >
> > These are easy to fix though =)
> >
> > Will you take care of them?
> These lines are not in the ebuilds proper, but in lisp code embedded into
> ebuilds. I think it makes no sense to fix them.
>
> Andrey
>
Changing them to tabs makes the warnings go away and respects the look
of the lisp code.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-12-11 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 15:33 [gentoo-lisp] Stabilization of last versions of sbcl and asdf on amd64 Chema Alonso
2013-12-09 19:11 ` grozin
2013-12-10 9:26 ` Chema Alonso
2013-12-10 9:54 ` Ulrich Mueller
2013-12-10 10:23 ` grozin
2013-12-11 14:02 ` Chema Alonso [this message]
2013-12-11 14:21 ` Ulrich Mueller
2013-12-11 20:33 ` grozin
2013-12-11 20:05 ` Chema Alonso
2013-12-11 20:31 ` grozin
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=20131211140217.GA8049@filladhoo \
--to=nimiux@gentoo.org \
--cc=gentoo-lisp@lists.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