On 2013-06-09 13:41, Burkhard Lück wrote:
Am Samstag, 8. Juni 2013, 15:39:20 schrieb Urs Wolfer:
Okay, everything is done now. Have fun with the migrated repositories
:)
Code in svn trunk/KDE/kdenetwork/ was replaced by a README about move
to git,
but branches/KDE/4.10/kdenetwork/ has still
You forgot to delete kopete-cryptography doc dir in extragear. I have done it:
http://websvn.kde.org/trunk/extragear/network/doc/kopete-cryptography/
On Saturday 08 June 2013 15:39:20 Urs Wolfer wrote:
Okay, everything is done now. Have fun with the migrated
repositories :)
Bye
urs
On
El Dijous, 6 de juny de 2013, a les 22:53:17, Pali Rohár va escriure:
On Thursday 06 June 2013 22:44:18 Albert Astals Cid wrote:
El Dijous, 6 de juny de 2013, a les 22:26:17, Pali Rohár va
escriure:
Hello,
all kopete repos were pushed to git.kde.org. I also enabled
hooks and
Am Samstag, 8. Juni 2013, 15:39:20 schrieb Urs Wolfer:
Okay, everything is done now. Have fun with the migrated repositories :)
Code in svn trunk/KDE/kdenetwork/ was replaced by a README about move to git,
but branches/KDE/4.10/kdenetwork/ has still the code for branch.
Code in branches
Kopete looks now also good. Thanks to everyone who has helped with the
migration work.
I should only replace (remove) things in SVN trunk, right?
Also, I have noticed one strange thing: Script Kiddy has removed
translation stuff from all .desktop files in all kdenetwork project
(e.g. [1]).
Urs,
I think we are good to go now. I believe scripty got confused because
there was still content in svn and git. Albert would know more though.
And yeah, I think replacing only on trunk is enough iirc.
BR,
Jeremy
On Fri, Jun 7, 2013 at 12:07 AM, Urs Wolfer uwol...@kde.org wrote:
Kopete
Am Freitag, 7. Juni 2013, 11:38:52 schrieb Jeremy Whiting:
Urs,
I think we are good to go now. I believe scripty got confused because
there was still content in svn and git. Albert would know more though.
And yeah, I think replacing only on trunk is enough iirc.
BR,
Jeremy
On Fri,
Hi Jeremy
Looks good, thanks a lot! :)
I have cherry-picked all standalone fixes into 4.10 branch. Everything
should build now in master and 4.10 (except Kopete, which is not online
yet).
I have also update documentation_paths and get_paths in trunk and branch
locally; I will commit these
On Thursday 06 June 2013 09.33.53 Urs Wolfer wrote:
Hi Jeremy
Looks good, thanks a lot! :)
I have cherry-picked all standalone fixes into 4.10 branch. Everything
should build now in master and 4.10 (except Kopete, which is not online
yet).
I have also update documentation_paths and
I just moved the kdeadmin and kdenetwork stuff from release-tools modules
to modules.git on master branch, next need to do something similar for
KDE/4.10 branch to package them in one tarball like I did in the past for
kdesdk and kdetoys. Anyway, the list is :
KDEAdmin {kuser,
Hello,
all kopete repos were pushed to git.kde.org. I also enabled hooks
and development sites and configured trunk i18n branch.
When you delete kdenetwork from svn, can you delete also
playground and extragear kopete paths from svn? These are
converted in git too.
svn paths:
El Dijous, 6 de juny de 2013, a les 09:33:53, Urs Wolfer va escriure:
Hi Jeremy
Looks good, thanks a lot! :)
I have cherry-picked all standalone fixes into 4.10 branch. Everything
should build now in master and 4.10 (except Kopete, which is not online
yet).
I have also update
El Dijous, 6 de juny de 2013, a les 22:26:17, Pali Rohár va escriure:
Hello,
all kopete repos were pushed to git.kde.org. I also enabled hooks
and development sites and configured trunk i18n branch.
When you delete kdenetwork from svn, can you delete also
playground and extragear kopete
On Thursday 06 June 2013 22:44:18 Albert Astals Cid wrote:
El Dijous, 6 de juny de 2013, a les 22:26:17, Pali Rohár va
escriure:
Hello,
all kopete repos were pushed to git.kde.org. I also enabled
hooks and development sites and configured trunk i18n
branch.
When you delete
Urs,
I just ran a conversion, and cloned the result and found two problems. One
is krfb git repo doesn't have kcm_krfb folder inside it. Looking at the
CMakeLists.txt it's not built anyway, but we need to find out why it's not
there at all imo.
The second problem is that kppp has many
Hmm, actually looking deeper kcm_krfb in svn is an empty folder (not sure
what it's for...)
And the differences in kppp seem weird, http://paste.kde.org/759278/ but
shouldn't affect anything from what I can see. so maybe we're good to go?
should I push this into the main git repos and we can test
Jeremy, I think you can push into the main repos. The kppp thing looks
like some SVN keyword. I think this change doesn't hurt.
Once you pushed into the main repos, you can can notify me again. Then I
will test also and cherry-pick the build fixes into the 4.10 branch.
@Pali: You can run the
Kopete git conversion scripts on dewey started.
On Wednesday 05 June 2013 21:10:10 Urs Wolfer wrote:
Jeremy, I think you can push into the main repos. The kppp
thing looks like some SVN keyword. I think this change
doesn't hurt.
Once you pushed into the main repos, you can can notify me
Urs,
Ok, kdenetwork-filesharing, kdenetwork-strigi-analyzers, kdnssd, kget,
kppp, krdc and krfb pushed, tags pushed, hooks enabled, i18n branches set
in projects.kde.org settings, and they are enabled for development.
After kopete is migrated, will you replace the svn content with a README
file
19 matches
Mail list logo
