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 paths from svn? These are > converted in git too. > > svn paths: > /trunk/playground/network/kopete/ > /trunk/extragear/network/kopete-cryptography/ > /trunk/extragear/network/kopete-scripting/ > > new git projects: > https://projects.kde.org/projects/kde/kdenetwork/kopete > https://projects.kde.org/projects/playground/network/kopete-pimpresence > https://projects.kde.org/projects/playground/network/kopete-scripting > https://projects.kde.org/projects/playground/network/kopete-sharemydesktop > https://projects.kde.org/projects/playground/network/kopete-thinklight > https://projects.kde.org/projects/playground/network/kopete-whiteboard > > Plugins cryptography, smpppdcs, motionautoaway and javascript > are in main kopete repository.
So main kopete gained a few plugins? Hope not in the KDE/4.10 branch, right? Cheers, Albert > > 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 get_paths in trunk > > and branch locally; I will commit these change once Kopete is > > also online. > > > > SVN is looked now, so we do not need to hurry with removing > > it. I can do that in some days. > > > > Bye > > urs > > > > On 2013-06-05 23:37, Jeremy Whiting wrote: > > > 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 [1] > > > settings, and they are enabled for development. > > > After kopete is migrated, will you replace the svn content > > > with a README file as that sysadmin mail said? rather than > > > me putting one in each app's folder. > > > > > > BR, > > > > > > Jeremy > > > > > > On Wed, Jun 5, 2013 at 1:25 PM, Pali Rohár > > > <pali.ro...@gmail.com> > > > > > > wrote: > > >> 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 > > >>> again. Then I will test also and cherry-pick the build > > >>> fixes into the 4.10 branch. > > >>> > > >>> @Pali: You can run the conversion for Kopete now also. > > >>> > > >>> @all: Please do not commit anything which is not related > > >>> to the conversion at this time! > > >>> > > >>> I have opened a sysadmin ticket for looking SVN repos > > >>> until Git repos on projects.kde.org [1] look okay and we > > >>> can remove them in SVN. > > >>> > > >>> Bye > > >>> urs > > >>> > > >>> On 2013-06-05 18:58, Jeremy Whiting wrote: > > >>> > 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/ [2] [2] 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 there? Rerun the conversion if > > >>> > needed, etc. > > >>> > > > >>> > BR, > > >>> > Jeremy > > >>> > > > >>> > On Wed, Jun 5, 2013 at 10:52 AM, Jeremy Whiting > > >>> > <jpwhit...@kde.org> > > >>> > > > >>> > wrote: > > >>> >> 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 differences > > >>> >> between svn master and git master, not sure why, but > > >>> >> I'll look into it this evening. We need these to be > > >>> >> working and right before we remove from svn. > > >>> >> > > >>> >> thanks, > > >>> >> Jeremy > > >>> >> > > >>> >> On Wed, Jun 5, 2013 at 5:03 AM, Raphael Kubo da Costa > > >>> >> > > >>> >> <rak...@freebsd.org> wrote: > > >>> >>> Urs Wolfer <uwol...@kde.org> writes: > > >>> >>>> kdenetwork will get migrated to Git in the next days > > >>> >>>> (between > > >>> >>> > > >>> >>> June 5th > > >>> >>> > > >>> >>>> and June 11th). Please do not commit anything into > > >>> >>>> SVN anymore. > > >>> >>> > > >>> >>> Also, > > >>> >>> > > >>> >>>> please wait with any Git commits until further > > >>> >>>> notice. > > >>> >>> > > >>> >>> Sorry if I've missed this being discussed somewhere > > >>> >>> else, but doesn't it > > >>> >>> make sense to ask the sysadmins to svn lock kdenetwork > > >>> >>> to prevent people > > >>> >>> from committing? > > >>> >>> _______________________________________________ > > >>> >>> Kde-scm-interest mailing list > > >>> >>> kde-scm-inter...@kde.org > > >>> >>> https://mail.kde.org/mailman/listinfo/kde-scm-interest > > >>> >>> [3] > > >> > > >> [1] > > >> > > >>> > Links: > > >>> > ------ > > >>> > [1] > > >>> > https://mail.kde.org/mailman/listinfo/kde-scm-interest > > >>> > [3] [2] http://paste.kde.org/759278/ [2] > > >> > > >> -- > > >> Pali Rohár > > >> pali.ro...@gmail.com > > > > > > Links: > > > ------ > > > [1] http://projects.kde.org > > > [2] http://paste.kde.org/759278/ > > > [3] https://mail.kde.org/mailman/listinfo/kde-scm-interest _______________________________________________ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team