Yesterday I emerged subversion with USE='apache-2' emerge subversion today
after a regular emerge --sync ; emerge -auD world I got myself in an
interesting situation:
[EMAIL PROTECTED] ~ # emerge -auD world
These are the packages that I would merge, in order:
Calculating world dependencies
On Sat, 22 Jan 2005 12:47:18 +0200 Stoian Ivanov [EMAIL PROTECTED]
wrote:
| Yesterday I emerged subversion with USE='apache-2' emerge subversion
First, use package.use, not USE on the commandline. Second, you probably
want apache2, not apache-2.
--
Ciaran McCreesh : Gentoo Developer (Vim,
tumbleweed portage # emerge =sys-devel/autoconf-2.58
it looks like it did it
tumbleweed portage # emerge -p subversion
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N] dev-lang/swig-1.3.19
[blocks B ] =sys-devel/autoconf-2.58* (from
It is autoconf-2.58* that is blocked. You need to install a different
version of autoconf.
--
Jeremy Maitin-Shepard
--
[EMAIL PROTECTED] mailing list
Right. Call my grasshopper.
Jeremy Maitin-Shepard wrote:
It is autoconf-2.58* that is blocked. You need to install a different
version of autoconf.
--
[EMAIL PROTECTED] mailing list
On Sat, 17 Jan 2004 13:43, Andrew Cowie wrote:
On Sat, 2004-01-17 at 03:09, Kurt Guenther wrote:
I see that there is an ebuild for subversion, but it is masked. Does
anybody know what is up here? How do I find out status, etc?
You'd do well to pop into #svn on freenode and lurk and
I see that there is an ebuild for subversion, but it is masked. Does
anybody know what is up here? How do I find out status, etc?
--Kurt
--
[EMAIL PROTECTED] mailing list
On Fri, 16 Jan 2004 11:39:12 -0500 Kurt Guenther
[EMAIL PROTECTED] wrote:
| I see that there is an ebuild for subversion, but it is masked. Does
| anybody know what is up here? How do I find out status, etc?
It's marked as ~x86, which means it's not been heavily tested. If you've
done lots of
On Sat, 2004-01-17 at 03:09, Kurt Guenther wrote:
I see that there is an ebuild for subversion, but it is masked. Does
anybody know what is up here? How do I find out status, etc?
You'd do well to pop into #svn on freenode and lurk and listen for a
while. From them, for example, I found out
Today I upgrade subversion from 0.27.0 to 0.28.0 and get this kind of
version error. Other operations give the same result. The db4_recover or
svnadmin recover doesn't help.
Ideas?
TIA
Alcino
svn commit
svn: Unsupported repository version
svn: Commit failed (details follow):
svn: OPTIONS
Forget that never mind... :(
After a successful (or at least an apparently success) commit,
I get this:
svn log
svn: Berkeley DB error
svn: PROPFIND request failed on '/svn/repos/bin'
svn:
Berkeley DB error while opening environment for filesystem
/home/svn/repos/db:
DB_RUNRECOVERY: Fatal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 02 September 2003 21:55, Alcino Dall Igna Junior wrote:
Forget that never mind... :(
After a successful (or at least an apparently success) commit,
I get this:
svn log
svn: Berkeley DB error
svn: PROPFIND request failed on
Yes, I delete the old and recreate a new repository, but I think that
should have a better way to do this.
In a fast scan in subversion site I find nothing.
As far as I can see, I will downgrade and wait.
T.
Alcino
On Tue, 2003-09-02 at 17:59, Mike Williams wrote:
-BEGIN PGP SIGNED
On Tue, 2003-09-02 at 15:43, Alcino Dall Igna Junior wrote:
Today I upgrade subversion from 0.27.0 to 0.28.0 and get this kind of
version error. Other operations give the same result. The db4_recover or
svnadmin recover doesn't help.
Ideas?
Hi,
At issue is that the 0.28.0 release of
Hey all,
Is there anyone out there who uses the new subversion ebuilds in portage?
I've used subversion heavily since November, but I never used the
gentoo-provided ebuilds because they were so out of date, and Berkeley 4.0.14
seemed to do weird stuff whenever I tried to emerge it.
On my
15 matches
Mail list logo
