Remove Qt4 from sysadmin/repo-metadata

[Marius P]

Hello,

If it is OK. I would want to remove Qt4 and KDE version 4 from
sysadmin/repo-metadata.
The first step that I want to do: delete
sysadmin/repo-metadata/dependencies/dependency-data-latest-qt4 and
sysadmin/repo-metadata/dependencies/dependency-data-stable-qt4.

May I do this?

Thanks.

Re: Copying po/docbook files to repositories nightly

[Johannes Zarl-Zierl]

Hi Albert,

Thanks for the change !

Am Sonntag, 2. Oktober 2022, 07:51:04 CEST schrieb Albert Astals Cid:
> Nothing broke but at least it seems the po files did not get commited to
> these projects (maybe there are some more problematic repots, please check
> yours if it's not part of KDE Gear, KDE Framworks or Plasma, those are the
> ones i did check more thoroughly and fix if found something)
> 
> digikam
> gcompris
> kaffeine
> kbibtex
> kphotoalbum
> kst-plot
> rkward
> skrooge
> trojita
> ubiquity-slideshow-neon
> 
> Because it is ignoring the po folder at the .gitignore file level, please
> don't do that anymore.

I'm not sure why kphotoalbum is listed here - the "Sync po/docbooks with svn" 
commit did land in our repo and po is not listed in our .gitignore.

> > > This is a heads up, as a developer there's nothing you need to do, at
> > > most
> > > remove the po/ folder from .gitignore if for some reason it is there.

Should I add "ki18n_install(po)" to my CMakeLists.txt?

Cheers,
  Johannes

No, l10n data did not moved to git (was Re: l10n data move from svn to git)

[Luigi Toscano]

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

[Luigi Toscano]

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

[Thomas Baumgart]

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

[Tobias Leupold]

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

Re: Moving CI to Qt 6.4

[Kai Uwe Broulik]

That was quick, Christophe, thanks!

https://invent.kde.org/frameworks/kio/-/commit/75c48fcf018116aacc30c362a4cde37ea9262164

Cheers
Kai Uwe

Am 02.10.22 um 11:56 schrieb Ben Cooksley:

Hi all,

As part of recent updates to the CI system i've been revising our Qt 6 
image to move it to Qt 6.4.


This has shown alas that KIO fails to build from source: 
https://invent.kde.org/sysadmin/ci-management/-/jobs/505902 



Can someone please take a look?

Thanks,
Ben

Moving CI to Qt 6.4

[Ben Cooksley]

Hi all,

As part of recent updates to the CI system i've been revising our Qt 6
image to move it to Qt 6.4.

This has shown alas that KIO fails to build from source:
https://invent.kde.org/sysadmin/ci-management/-/jobs/505902

Can someone please take a look?

Thanks,
Ben

Re: Copying po/docbook files to repositories nightly

[Johnny Jazeix]

Le dim. 2 oct. 2022 à 07:51, Albert Astals Cid  a écrit :

> El diumenge, 2 d’octubre de 2022, a les 7:37:26 (CEST), Albert Astals Cid
> va
> escriure:
> > El divendres, 2 de setembre de 2022, a les 23:24:21 (CEST), Albert Astals
> > Cid
> > va escriure:
> > > As you may know, translations for apps don't live in the same place as
> the
> > > code for the apps themselves.
> > >
> > > This greatly benefits translators but is not awesome for the release
> > > management side of things since it means that for each release we need
> to
> > > not forget to copy the appropriate files to the appropriate place,
> makes
> > > tagging somewhat harder, etc.
> > >
> > > For a while now we have been running an "experimental"
> copy-po-qm-docbook-
> > > back-to-repository in a number of "select" repositories and it seems to
> > > have worked quite well, you can seem one example in
> > > https://invent.kde.org/plasma-mobile/alligator/-/commits/master/po
> > >
> > > The idea is to enable this for all repositories.
> >
> > This has now been enabled for master branch and according to scripty logs
> > all seems to have worked.
> >
> > Please inspect your repositories and make sure the po files are there
> where
> > they should and nothing broke.
>
> Nothing broke but at least it seems the po files did not get commited to
> these
> projects (maybe there are some more problematic repots, please check yours
> if
> it's not part of KDE Gear, KDE Framworks or Plasma, those are the ones i
> did
> check more thoroughly and fix if found something)
>
> digikam
> gcompris
> kaffeine
> kbibtex
> kphotoalbum
> kst-plot
> rkward
> skrooge
> trojita
> ubiquity-slideshow-neon
>
> Because it is ignoring the po folder at the .gitignore file level, please
> don't
> do that anymore.
>
> Cheers,
>   Albert
>
>
I've fixed it for GCompris and its website.

Thanks,

Johnny


> >
> > Also please make sure you adapt your releasing scripts if you release
> from
> > master.
> >
> > Cheers,
> >   Albert
> >
> > > This is a heads up, as a developer there's nothing you need to do, at
> most
> > > remove the po/ folder from .gitignore if for some reason it is there.
> > >
> > > If you're a packager you will need to make sure your scripts don't try
> to
> > > copy po/qm/docbook files anymore when doing a release once this is
> > > activated.
> > >
> > > My plan would be to enable this scripts over Akademy so we have the
> high
> > > bandwidth there to fix things if needed.
> > >
> > > Opinions? Comments?
> > >
> > > Cheers,
> > >
> > >   Albert
>
>
>
>
>