From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-devhelp@lists.gentoo.org
Subject: Re: [gentoo-devhelp] dodoc vs directories
Date: Thu, 23 Feb 2012 21:56:43 +0100 [thread overview]
Message-ID: <4F46A80B.10801@gentoo.org> (raw)
In-Reply-To: <m339a6821d.fsf@carbon.jhcloos.org>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
James Cloos schrieb:
>>>>>> "TS" == Thomas Sachau <tommy@gentoo.org> writes:
>
> TS> I just tried libgit2 (dev-libs/libgit2-0.16.0) and it installs just fine
> TS> for me, so i cannot reproduce this (base version for my portage is
> TS> 2.2_alpha87), what are your versions of portage and libgit2?
>
> As I implied by saying master, -9999. libgit2 is also 0.16.0.
>
> I tried updating portage just before posting, the log says that was from
> 9997bb9c81e07 to 4a85888920244.
>
> My last successful install of libgit2 was 0.15.0 back in October, so the
> change which made portage start failing ebuilds which try to dodoc dirs
> was done sometime in the last four months.
>
> TS> P.S.: No need to cc me, i am subscribed to this list.
>
> I'm used to lkml-style etiquette; include everyone who has posted in the
> CC. It tends to be the norm on technical lists, and is what gnus does
> by default if I reply to the copy sent directly. I (now) see that this
> lists munges reply-to, so this reply honours that....
>
> -JimC
Not much i can help with, since i cannot reproduce this myself.
Maybe you ask portage maintainers on irc in #gentoo-portage or on the
related mailing list about this.
--
Thomas Sachau
Gentoo Linux Developer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 380 bytes --]
prev parent reply other threads:[~2012-02-23 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 21:46 [gentoo-devhelp] dodoc vs directories James Cloos
2012-02-18 13:40 ` Thomas Sachau
2012-02-18 17:56 ` James Cloos
2012-02-18 19:05 ` Thomas Sachau
2012-02-20 6:13 ` James Cloos
2012-02-23 20:56 ` Thomas Sachau [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=4F46A80B.10801@gentoo.org \
--to=tommy@gentoo.org \
--cc=gentoo-devhelp@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