Kdesupport from SVN and taglib

[Alessandro Sivieri]

Hi everyone,

it has been a while since I saw for the first time the following error:

svn: URL 'svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin' of existing directory 'taglib/admin' does not match expected URL 'svn://anonsvn.kde.org/home/kde/trunk/kdesupport/taglib/admin'

when trying to update kdesupport from SVN (using kdesvn-build), and it has never been solved, I mean, as of today I still obtain it; do you know what may be the cause?

--
Sivieri Alessandro
alessandro.sivieri@...
http://www.chimera-bellerofonte.eu/
http://www.poul.org/

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

On Monday 09 November 2009 17:48:22 Alessandro Sivieri wrote:

> Hi everyone,
>
> it has been a while since I saw for the first time the following error:
>
> svn: URL 'svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin'
> of existing directory 'taglib/admin' does not match expected URL 'svn://
> anonsvn.kde.org/home/kde/trunk/kdesupport/taglib/admin'
>
> when trying to update kdesupport from SVN (using kdesvn-build), and it has
> never been solved, I mean, as of today I still obtain it; do you know what
> may be the cause?
>

Doesn't removing taglib/admin and svn up'ing again solve the problem? I
remember having some problems with taglib a few months ago, and doing this has
solved everything.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[Shaun Reich]

On Mon, Nov 9, 2009 at 8:02 PM, Raphael Kubo da Costa <kubito@...> wrote:

> On Monday 09 November 2009 17:48:22 Alessandro Sivieri wrote:
>> Hi everyone,
>>
>> it has been a while since I saw for the first time the following error:
>>
>> svn: URL 'svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin'
>> of existing directory 'taglib/admin' does not match expected URL 'svn://
>> anonsvn.kde.org/home/kde/trunk/kdesupport/taglib/admin'
>>
>> when trying to update kdesupport from SVN (using kdesvn-build), and it has
>> never been solved, I mean, as of today I still obtain it; do you know what
>> may be the cause?
>>
> Doesn't removing taglib/admin and svn up'ing again solve the problem? I
> remember having some problems with taglib a few months ago, and doing this has
> solved everything.
>
>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>

Those were compilation errors, I had the same problem, in that aspect.
He's talking about just this svn error, which I (think) I remember
seeing. No idea what they mean.


--
KDE Developer,
Shaun Reich
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[Parker Coates]

On Mon, Nov 9, 2009 at 15:18, Shaun Reich wrote:

> On Mon, Nov 9, 2009 at 8:02 PM, Raphael Kubo da Costa wrote:
>> On Monday 09 November 2009 17:48:22 Alessandro Sivieri wrote:
>>> Hi everyone,
>>>
>>> it has been a while since I saw for the first time the following error:
>>>
>>> svn: URL 'svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin'
>>> of existing directory 'taglib/admin' does not match expected URL 'svn://
>>> anonsvn.kde.org/home/kde/trunk/kdesupport/taglib/admin'
>>>
>>> when trying to update kdesupport from SVN (using kdesvn-build), and it has
>>> never been solved, I mean, as of today I still obtain it; do you know what
>>> may be the cause?
>>>
>> Doesn't removing taglib/admin and svn up'ing again solve the problem? I
>> remember having some problems with taglib a few months ago, and doing this has
>> solved everything.
>>
>>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>>
>
> Those were compilation errors, I had the same problem, in that aspect.
> He's talking about just this svn error, which I (think) I remember
> seeing. No idea what they mean.

I too encountered this. I had to delete the entire taglib directory
and "svn up" again. No idea what the problem was, though.

Parker
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[Alessandro Sivieri]

Yes, deleting the taglib directory and svn updating it solved the problem; the same problem also happened with kdelibs and the oxygen directory; maybe it is related on how kdesvn-build downloads the snapshots before launching svn update, but I don't know exactly how this works, so I cannot tell if this is the real problem.

--
Sivieri Alessandro
alessandro.sivieri@...
http://www.chimera-bellerofonte.eu/
http://www.poul.org/

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

On Tuesday 10 November 2009 06:50:33 Alessandro Sivieri wrote:
> Yes, deleting the taglib directory and svn updating it solved the problem;
> the same problem also happened with kdelibs and the oxygen directory; maybe
> it is related on how kdesvn-build downloads the snapshots before launching
> svn update, but I don't know exactly how this works, so I cannot tell if
> this is the real problem.

I'm pretty sure it's related more to when the initial checkout of kdesupport
was performed.  The snapshots themselves are just the standard KDE snapshots
(although I'm not sure if anyone uses them except through kdesvn-build
anymore)

Regards,
 - Michael Pyne


 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[Ian Wadham]

On Tue, 10 Nov 2009 10:50:33 pm Alessandro Sivieri wrote:
> Yes, deleting the taglib directory and svn updating it solved the problem;
> the same problem also happened with kdelibs and the oxygen directory; maybe
> it is related on how kdesvn-build downloads the snapshots before launching
> svn update, but I don't know exactly how this works, so I cannot tell if
> this is the real problem.

I struck both problems yesterday (with oxygen and taglib) and have never
been anywhere near kdesvn-build.  I was updating kdelibs, kdepimlibs and
kdebase trunk which I had at a revision from about the time of KDE 4.3
release (in July/August).  I also found I had to update kdesupport because
of kdepimlibs requiring akonadi, hence I ran into the taglib problem.  I am
using the cs, cb, cmakekde recipes to update my copy of KDE trunk.

In each case (oxygen and taglib) SVN was complaining about adding a
directory that was already present in the working copy.  I think this may
happen when the repository has a directory that was SVN deleted and
then SVN added again later.  Maybe the SVN client does not have the
ability to rm -rf the obsolete directory in the working copy before trying
to SVN add the new version.  Anyway doing the rm -rf manually and
then SVN update, solved both problems for me.

Cheers, Ian W.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<