[yast-devel] SVN -> Git: Report
Hi, I've checked the current status of our testing Git repository, you can see the changes here: http://bit.ly/zsVW6I Summary: * Several repos have got additional branch * yast-dbus-client has been fixed (branches, tags, commits) * yast-dbus-server has been fixed (branches, tags, commits) * yast-extra-packages - broken (not used anymore?) * yast-libyui has been fixed (branches, tags, commits) * yast-modules - broken (not used anymore?) * yast-ncurses-pkg - broken * yast-network - broken * yast-nfs-client - broken * yast-nfs-server - broken * yast-nis-client - broken * yast-nis-server - broken * ... and all following modules (sorted alphabetically) Thanks in advance for fixing the import filters Bye Lukas -- Lukas Ocilka, Appliances Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 03/05/2012 03:49 PM, Lukas Ocilka wrote:
Hi,
I've checked the current status of our testing Git repository, you can see the changes here:
Summary: * Several repos have got additional branch * yast-dbus-client has been fixed (branches, tags, commits) * yast-dbus-server has been fixed (branches, tags, commits) * yast-extra-packages - broken (not used anymore?) * yast-libyui has been fixed (branches, tags, commits) * yast-modules - broken (not used anymore?) * yast-ncurses-pkg - broken * yast-network - broken * yast-nfs-client - broken * yast-nfs-server - broken * yast-nis-client - broken * yast-nis-server - broken * ... and all following modules (sorted alphabetically)
Thanks in advance for fixing the import filters
Any news? Repos seems to be still broken. Bye Lukas -- Lukas Ocilka, Appliances Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Ping. Any news here? Lukas On 03/09/2012 09:47 AM, Lukas Ocilka wrote:
On 03/05/2012 03:49 PM, Lukas Ocilka wrote:
Hi,
I've checked the current status of our testing Git repository, you can see the changes here:
Summary: * Several repos have got additional branch * yast-dbus-client has been fixed (branches, tags, commits) * yast-dbus-server has been fixed (branches, tags, commits) * yast-extra-packages - broken (not used anymore?) * yast-libyui has been fixed (branches, tags, commits) * yast-modules - broken (not used anymore?) * yast-ncurses-pkg - broken * yast-network - broken * yast-nfs-client - broken * yast-nfs-server - broken * yast-nis-client - broken * yast-nis-server - broken * ... and all following modules (sorted alphabetically)
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 03/21/2012 02:18 PM, Lukas Ocilka wrote:
Ping. Any news here?
Bernhard, Daniel, Do you have your patched tools and configuration of the migration accessible anywhere, e.g., at GitHub? I was told that you might be fully booked for some time now - which means that either someone else has to step in and take the project over or it has to wait some time now... Thanks in advance Lukas -- Lukas Ocilka, Appliances Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 26.03.2012 16:39, schrieb Lukas Ocilka:
On 03/21/2012 02:18 PM, Lukas Ocilka wrote:
Ping. Any news here?
Bernhard, Daniel,
Do you have your patched tools and configuration of the migration accessible anywhere, e.g., at GitHub? I was told that you might be fully booked for some time now - which means that either someone else has to step in and take the project over or it has to wait some time now...
Thanks in advance Lukas
I just pushed our latest changes to http://git.suse.de/yast-svn-migration I think, the only module that is failing conversion in the latest version is qt-pkg (which has a complicated history going through qt and qt4 modules) but I had got it converted with an earlier version, so we would just need to find the working one (and maybe add special rules to ymodule.pm). To run the conversion, you also need the svn-all-fast-export from http://w3.suse.de/~bwiedemann/svn/ which has one patch added. To test your setup, you do "make regtest" which tries to convert the registration module. Ciao Bernhard M. - -- (o_ //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9whhIACgkQSTYLOx37oWS9BQCfYZPdOdjkFm0Up/gAZmPOUOhM hyAAoL7ad83cHffbWAmaRboVQv204O5+ =LU9O -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Hi, I was thinking about the migration from SVN to Git and I came to a conclusion that I'd really love to use GitHub my work instead of SVN. For purpose, I (personally as a developer) care about modules I still maintain. And as we'd like to move from SVN to GitHub module by module anyway, I propose to start moving them right now - if there is a module that can be converted and moved, let's do it now and don't wait for other ones. Such module would have a new DISCONTINUED file in SVN linking to the project at GitHub. We'd have to create this file in every active branch. I'd maybe added a non-standard note to *.changes file too. --- DISCONTINUED --- Development and maintenance of this project has been discontinued in this SVN. We have moved the project to GitHub: https://github.com/yast/module_name --- DISCONTINUED --- Bye Lukas -- Lukas Ocilka, Appliances Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/24/2012 01:12 PM, Lukas Ocilka wrote:
Hi,
I was thinking about the migration from SVN to Git and I came to a conclusion that I'd really love to use GitHub my work instead of SVN. For purpose, I (personally as a developer) care about modules I still maintain.
And as we'd like to move from SVN to GitHub module by module anyway, I propose to start moving them right now - if there is a module that can be converted and moved, let's do it now and don't wait for other ones. Such module would have a new DISCONTINUED file in SVN linking to the project at GitHub. We'd have to create this file in every active branch. I'd maybe added a non-standard note to *.changes file too.
--- DISCONTINUED --- Development and maintenance of this project has been discontinued in this SVN. We have moved the project to GitHub: https://github.com/yast/module_name --- DISCONTINUED ---
Bye Lukas
Hi, if you have modules that had no changes since 2012-02-28, you can git clone http://www3.zq1.de/bernhard/linux/yast/yast-MODULE.git/ right now If you had changes, we would need a newer SVN-dump, but Daniel who did this dump last time is on vacation until 2012-05-06 Ciao Bernhard M. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+WljEACgkQSTYLOx37oWSK1QCgnXIDg5xCbY0XVPC3/g+MW4q5 5q8AoMl6PU5S0RSvLX1pfZklvMsjZ0wN =RX6R -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tuesday 24 April 2012 14:01:53 Bernhard M. Wiedemann wrote:
And as we'd like to move from SVN to GitHub module by module anyway, I propose to start moving them right now - if there is a module that can be converted and moved, let's do it now and don't wait for other ones.
if you have modules that had no changes since 2012-02-28, you can git clone http://www3.zq1.de/bernhard/linux/yast/yast-MODULE.git/ right now
If you had changes, we would need a newer SVN-dump, but Daniel who did this dump last time is on vacation until 2012-05-06
As there were commits since Feburary, I'd recommend to do another full run with a new SVN dump and our current filter set. All successful modules can migrate. The others will remain until they are fixed and migrated manually. IIRC it was something between 3 and 5 repos failing during our latest test. Anyhow, in order not lose any commits you need to announce the date and time for this to all developers as all SVN commits after the latest dump will not be in the git repo and thus would be lost. Ciao, Daniel -- J. Daniel Schmidt <jdsn@suse.de> SUSE LINUX Products GmbH Research & Development Maxfeldstr. 5 HRB 16746 (AG Nürnberg) D-90409 Nürnberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 7.5.2012 15:56, J. Daniel Schmidt napsal(a):
On Tuesday 24 April 2012 14:01:53 Bernhard M. Wiedemann wrote:
And as we'd like to move from SVN to GitHub module by module anyway, I propose to start moving them right now - if there is a module that can be converted and moved, let's do it now and don't wait for other ones.
if you have modules that had no changes since 2012-02-28, you can git clone http://www3.zq1.de/bernhard/linux/yast/yast-MODULE.git/ right now
If you had changes, we would need a newer SVN-dump, but Daniel who did this dump last time is on vacation until 2012-05-06
As there were commits since Feburary, I'd recommend to do another full run with a new SVN dump and our current filter set.
All successful modules can migrate. The others will remain until they are fixed and migrated manually. IIRC it was something between 3 and 5 repos failing during our latest test.
Anyhow, in order not lose any commits you need to announce the date and time for this to all developers as all SVN commits after the latest dump will not be in the git repo and thus would be lost.
To prevent this, turn the repo to read-only mode before creating the dump. I can assist with this. With the commit logs being sent to a mailing list, it should be easy to spot accidental commits to wrong repostory after partial migration. Jiri -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wednesday 09 May 2012 07:43:56 Jiri Srain wrote:
Anyhow, in order not lose any commits you need to announce the date and time for this to all developers as all SVN commits after the latest dump will not be in the git repo and thus would be lost.
To prevent this, turn the repo to read-only mode before creating the dump. I can assist with this.
The problem is not switching the repo to read-only mode. I know how to do that. The issue is to have the date and time announced when it will happen. We should not silently switch it to read-only mode. Ciao, Daniel -- J. Daniel Schmidt <jdsn@suse.de> SUSE LINUX Products GmbH Research & Development Maxfeldstr. 5 HRB 16746 (AG Nürnberg) D-90409 Nürnberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 9.5.2012 11:32, J. Daniel Schmidt napsal(a):
On Wednesday 09 May 2012 07:43:56 Jiri Srain wrote:
Anyhow, in order not lose any commits you need to announce the date and time for this to all developers as all SVN commits after the latest dump will not be in the git repo and thus would be lost.
To prevent this, turn the repo to read-only mode before creating the dump. I can assist with this.
The problem is not switching the repo to read-only mode. I know how to do that. The issue is to have the date and time announced when it will happen. We should not silently switch it to read-only mode.
Yes, of course. What I wanted to point out that just announcement is not enough and there will always be someone who forgets about it :-) Jiri -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 09.05.2012 11:32, J. Daniel Schmidt wrote:
The problem is not switching the repo to read-only mode. I know how to do that. The issue is to have the date and time announced when it will happen. We should not silently switch it to read-only mode.
I had a customer asking for that already because he uses github and wants to contribute fixes/documentation If you need some test, you can start with autoyast and yast2-transfer :) I'd love to see autoyast there - the sooner the better :) -- ciao, Uwe Gansert SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Home: http://www.suse.de/~ug - Blog: http://suse.gansert.net -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 05/09/2012 12:50 PM, Uwe Gansert wrote:
On 09.05.2012 11:32, J. Daniel Schmidt wrote:
The problem is not switching the repo to read-only mode. I know how to do that. The issue is to have the date and time announced when it will happen. We should not silently switch it to read-only mode.
I had a customer asking for that already because he uses github and wants to contribute fixes/documentation If you need some test, you can start with autoyast and yast2-transfer :) I'd love to see autoyast there - the sooner the better :)
I've checked the current status and it's really way better than it was month ago, see: https://github.com/kobliha/yast_svn_2_git_check/blob/master/last.log Bye Lukas -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (5)
-
Bernhard M. Wiedemann -
J. Daniel Schmidt -
Jiri Srain -
Lukas Ocilka -
Uwe Gansert