Re: l10n data move from svn to git
On Mon, Oct 3, 2022 at 6:37 PM Albert Astals Cid wrote: > I'll let Harald answer if any modification needs to be done to the releaseme > process or not. There is no pressing need, it works as-is. But we are certainly at a point where we can rethink the workflow a bit and center it around gitlab more. Thoughts welcome. HS
Re: l10n data move from svn to git
Am Montag, 3. Oktober 2022, 18:37:34 CEST schrieb Albert Astals Cid: > El diumenge, 2 d’octubre de 2022, a les 14:06:58 (CEST), Thomas Baumgart va > > escriure: > > Hi all, > > > > On Sonntag, 2. Oktober 2022 13:42:16 CEST Tobias Leupold wrote: > > > Hi all :-) > > > > > > So a few hours ago, a new "po" folder appeared in KGeoTag, KPhotoAlbum > > > and > > > most probably everywhere. Apparently, the translations data is now not > > > hosted on some svn repo anymore, but right indside the respective > > > project? Which seems to be reasonable to me. > > > > > > I only have one question, after screwing up the last release of KGeoTag > > > and > > > KPhotoAlbum (which lacked all translations, due to tarme.rb not having > > > been > > > updated yet, and me having been the probably only misadventurer to make > > > a > > > release in the exact timeframe where the problem existed): > > > > > > Is there something I have to take care of in another way I had to do > > > before > > > when I do the next release using tarme.rb? > > > > A short description of the process would be wonderful. The last time I did > > a KMyMoney release, I ran into the problem, that tarme.rb requires a newer > > Ruby version than my distro (stock opensuse leap 15.4) currently supports. > > I simply reverted back to the last one working and kept going. Of course, > > that will not be working when there are changes coming up regarding the > > po subdir. > > > > > Sorry for this possibly redundant question, but once burnt, twice shy > > > ;-) > > > > I feel with you. Thus any hint/link is very welcome also from my side. I > > have to admit that I did not closely follow the latest changes due to time > > constraints. > > Unrelated to your actual question, but you should add ki18n_install(po) to > your base CMakeLists.txt, releaseme was doing that for you, but you should > really have it in your repo, for example for people that build from source. Kindly, Christophe Giboudeaux already did that, also for KPhotoAlbum and possibly other projects. Thanks :-) > I'll let Harald answer if any modification needs to be done to the releaseme > process or not. That would be nice, and surely also relevant for others! > Cheers, > Albert > > > Cheers Thomas
Re: l10n data move from svn to git
El diumenge, 2 d’octubre de 2022, a les 14:06:58 (CEST), Thomas Baumgart va escriure: > Hi all, > > On Sonntag, 2. Oktober 2022 13:42:16 CEST Tobias Leupold wrote: > > Hi all :-) > > > > So a few hours ago, a new "po" folder appeared in KGeoTag, KPhotoAlbum and > > most probably everywhere. Apparently, the translations data is now not > > hosted on some svn repo anymore, but right indside the respective > > project? Which seems to be reasonable to me. > > > > I only have one question, after screwing up the last release of KGeoTag > > and > > KPhotoAlbum (which lacked all translations, due to tarme.rb not having > > been > > updated yet, and me having been the probably only misadventurer to make a > > release in the exact timeframe where the problem existed): > > > > Is there something I have to take care of in another way I had to do > > before > > when I do the next release using tarme.rb? > > A short description of the process would be wonderful. The last time I did > a KMyMoney release, I ran into the problem, that tarme.rb requires a newer > Ruby version than my distro (stock opensuse leap 15.4) currently supports. I > simply reverted back to the last one working and kept going. Of course, > that will not be working when there are changes coming up regarding the po > subdir. > > Sorry for this possibly redundant question, but once burnt, twice shy ;-) > > I feel with you. Thus any hint/link is very welcome also from my side. I > have to admit that I did not closely follow the latest changes due to time > constraints. Unrelated to your actual question, but you should add ki18n_install(po) to your base CMakeLists.txt, releaseme was doing that for you, but you should really have it in your repo, for example for people that build from source. I'll let Harald answer if any modification needs to be done to the releaseme process or not. Cheers, Albert > > Cheers Thomas
No, l10n data did not moved to git (was Re: l10n data move from svn to git)
Tobias Leupold ha scritto: > Hi all :-) > > So a few hours ago, a new "po" folder appeared in KGeoTag, KPhotoAlbum and > most probably everywhere. Apparently, the translations data is now not hosted > on some svn repo anymore, but right indside the respective project? Which > seems to be reasonable to me. Subject fixed for the people who looks at the archives. -- Luigi
Re: l10n data move from svn to git
Tobias Leupold ha scritto: > Hi all :-) > > So a few hours ago, a new "po" folder appeared in KGeoTag, KPhotoAlbum and > most probably everywhere. Apparently, the translations data is now not hosted > on some svn repo anymore, but right indside the respective project? Which > seems to be reasonable to me. No, it's everything as before, those file are only a convenient copy, which is overwritten every time. The release script(s) need(s) to be fixed to not fetch the translations anymore. https://mail.kde.org/pipermail/kde-devel/2022-October/001371.html -- Luigi
Re: l10n data move from svn to git
Hi all, On Sonntag, 2. Oktober 2022 13:42:16 CEST Tobias Leupold wrote: > Hi all :-) > > So a few hours ago, a new "po" folder appeared in KGeoTag, KPhotoAlbum and > most probably everywhere. Apparently, the translations data is now not hosted > on some svn repo anymore, but right indside the respective project? Which > seems to be reasonable to me. > > I only have one question, after screwing up the last release of KGeoTag and > KPhotoAlbum (which lacked all translations, due to tarme.rb not having been > updated yet, and me having been the probably only misadventurer to make a > release in the exact timeframe where the problem existed): > > Is there something I have to take care of in another way I had to do before > when I do the next release using tarme.rb? A short description of the process would be wonderful. The last time I did a KMyMoney release, I ran into the problem, that tarme.rb requires a newer Ruby version than my distro (stock opensuse leap 15.4) currently supports. I simply reverted back to the last one working and kept going. Of course, that will not be working when there are changes coming up regarding the po subdir. > Sorry for this possibly redundant question, but once burnt, twice shy ;-) I feel with you. Thus any hint/link is very welcome also from my side. I have to admit that I did not closely follow the latest changes due to time constraints. Cheers Thomas -- Regards Thomas Baumgart - If you're watching an Apple store being robbed, does that make you an iWitness? - unknown source - signature.asc Description: This is a digitally signed message part.
l10n data move from svn to git
Hi all :-) So a few hours ago, a new "po" folder appeared in KGeoTag, KPhotoAlbum and most probably everywhere. Apparently, the translations data is now not hosted on some svn repo anymore, but right indside the respective project? Which seems to be reasonable to me. I only have one question, after screwing up the last release of KGeoTag and KPhotoAlbum (which lacked all translations, due to tarme.rb not having been updated yet, and me having been the probably only misadventurer to make a release in the exact timeframe where the problem existed): Is there something I have to take care of in another way I had to do before when I do the next release using tarme.rb? Sorry for this possibly redundant question, but once burnt, twice shy ;-) Cheers, Tobias
