From: Natanael Olaiz <nolaiz@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] eclass history
Date: Mon, 16 Apr 2012 12:37:48 +0200 [thread overview]
Message-ID: <CAP=gXz572uNA2Kuafs0u=OhWP7iweAtLOXQf+OqT1+oXN89cnA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
Hi,
Since the last updates, every update I have more and more problems with
ebuilds that I use from an authenticated https server.
For instance: the first time subversion asks to accept the certificate...
but since a time ago the subversion fetch eclass function is non
interactive at all, so it fails -have to do the checkout by hand- ; the
UUID have some kind of problem that after the first checkout make every
update to make a new checkout, etc.....
I want to debug this, because for me (that have to work with this) is a
real PITA.... My question is : where I can see the history of the eclasses?
Some time ago all worked perfect! But with the rsync I have no idea what is
going on, I don't know the history (and all local changes are lost each
--rsync...)
Thanks in advance,
Natanael
[-- Attachment #2: Type: text/html, Size: 838 bytes --]
next reply other threads:[~2012-04-16 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 10:37 Natanael Olaiz [this message]
2012-04-16 10:43 ` [gentoo-dev] eclass history Dirkjan Ochtman
2012-04-16 10:53 ` Natanael Olaiz
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='CAP=gXz572uNA2Kuafs0u=OhWP7iweAtLOXQf+OqT1+oXN89cnA@mail.gmail.com' \
--to=nolaiz@gmail.com \
--cc=gentoo-dev@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