Hi all,
Some people on this list and in general did not take the switch from KDE4 to Plasma 5 desktop easy way.
For those who prefer older workspace, or just see plasma 5 as unstable, which potentially includes me, I've created copr repository to maintain KDE4 for F22.
If you can, please test it in real life and report issues. I have tested in on default KDE-live install, resulting in one bug report already.
I can't promise continuity, but I will try my best.
Regards, Piotr
On Wednesday 21 October 2015 09:18:12 Rex Dieter wrote:
Can you please give a link to the copr?
Haha ... silly me :D
Obviously I can :
https://copr.fedoraproject.org/coprs/peem/kde4-fedora/
Regards, Piotr
On Qua, 2015-10-21 at 15:12 +0100, Piotr Gbyliczek wrote:
Hi all,
Some people on this list and in general did not take the switch from KDE4 to Plasma 5 desktop easy way.
For those who prefer older workspace, or just see plasma 5 as unstable, which potentially includes me, I've created copr repository to maintain KDE4 for F22.
I'm planing the same but for F23 , many thanks,
What it takes put kde4 in F23 ?
And why we haven't both kdes (kde 4 and kde 5 ) in same release ? what is the problem ?
Thanks
If you can, please test it in real life and report issues. I have tested in on default KDE-live install, resulting in one bug report already.
I can't promise continuity, but I will try my best.
Regards, Piotr _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On Wednesday 21 October 2015 15:26:55 Sérgio Basto wrote:
For those who prefer older workspace, or just see plasma 5 as unstable, which potentially includes me, I've created copr repository to maintain KDE4 for F22.
I'm planing the same but for F23 , many thanks,
Have a look at my repo, it does contain F23 packages as I plan to maintain it until plasma 5 is not stable or until there is demand. Haven't had time to test it on Rawhide yet.
What it takes put kde4 in F23 ?
Rebuild RPMs from modified specs ?
And why we haven't both kdes (kde 4 and kde 5 ) in same release ? what is the problem ?
They virtually same thing, so how would you go on updating it ? kde4 obsoletes plasma5 and plasma5 obsoletes kde4.... That won't work in same repo...
Regards, Piotr
On Qua, 2015-10-21 at 15:32 +0100, Piotr Gbyliczek wrote:
On Wednesday 21 October 2015 15:26:55 Sérgio Basto wrote:
For those who prefer older workspace, or just see plasma 5 as unstable, which potentially includes me, I've created copr repository to maintain KDE4 for F22.
I'm planing the same but for F23 , many thanks,
Have a look at my repo, it does contain F23 packages as I plan to maintain it until plasma 5 is not stable or until there is demand. Haven't had time to test it on Rawhide yet.
What it takes put kde4 in F23 ?
Rebuild RPMs from modified specs ?
Hi, could you document this a little more , I see Package URL: https://github.com/piotr-gbyliczek/kde4-fedora/raw/master/SRPMS/kde-workspac...
but https://github.com/piotr-gbyliczek is empty ,
could follow your hacks on github would be great !
And why we haven't both kdes (kde 4 and kde 5 ) in same release ? what is the problem ?
They virtually same thing, so how would you go on updating it ? kde4 obsoletes plasma5 and plasma5 obsoletes kde4.... That won't work in same repo...
Regards, Piotr
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On Wednesday 21 October 2015 15:47:37 Sérgio Basto wrote:
Hi, could you document this a little more , I see Package URL:
https://github.com/piotr-gbyliczek/kde4-fedora/raw/master/SRPMS/kde-workspa ce-4.11.22-3.fc22.src.rpm
but https://github.com/piotr-gbyliczek is empty ,
could follow your hacks on github would be great !
Ah, yes ... I've deleted github repo today, moved it to bitbucket
https://bitbucket.org/peemhq/kde4-fedora/src
I've changed issue tracker URL in copr, haven't rebuild RPMs yet using new location.
Feel free to look at spec files, that is about only thing there :)
As well, please test F23 packages, it may be better to combine efforts rather than creating another repo for F23. I'm open to other people helping.
Regards, Piotr
On Qua, 2015-10-21 at 16:21 +0100, Piotr Gbyliczek wrote:
On Wednesday 21 October 2015 15:47:37 Sérgio Basto wrote:
Hi, could you document this a little more , I see Package URL:
https://github.com/piotr-gbyliczek/kde4-fedora/raw/master/SRPMS/kde-workspa ce-4.11.22-3.fc22.src.rpm
but https://github.com/piotr-gbyliczek is empty ,
could follow your hacks on github would be great !
Ah, yes ... I've deleted github repo today, moved it to bitbucket
https://bitbucket.org/peemhq/kde4-fedora/src
I've changed issue tracker URL in copr, haven't rebuild RPMs yet using new location.
Feel free to look at spec files, that is about only thing there :)
As well, please test F23 packages, it may be better to combine efforts rather than creating another repo for F23. I'm open to other people helping.
Wow! It works very well in F23 , I can enable 3D on a vm of Virtualbox, (thing that not work with plasma 5) but we need obsolete more things etc . - 3:kdeplasma-addons-4.14.3-2.fc23.x86_64 is obsoleted by 3:kdeplasma-addons-4.14.3-2.fc23.x86_64 ! - could not find requested component: folderview - kde-style-oxygen-3:4.11.22-3.fc23.x86_64 conflicts with file from package qt4-style-oxygen-5.4.2-1.fc23.x86_64 ( dnf remove qt4-style-oxygen-5.4.2-1.fc23.x86_64 solve it ) - kde-workspace-3:4.11.22-3.fc23.x86_64 conflicts with file from package plasma-desktop-doc-5.4.2-2.fc23.noarch (dnf remove plasma-desktop-doc solve it) - /usr/share/doc/HTML/en/kinfocenter/kinfocenter.png from install of kde-workspace-3:4.11.22-3.fc23.x86_64 (dnf remove kinfocenter solve it) - Error: nothing provides pykde4(x86-64) >= 4.14.11 needed by plasma-scriptengine-python-3:4.11.22-3.fc23.x86_64 - ksysguard have a conflict libksysguard-common ( don't have the logs...)
but I think I will use it with F23
Many thanks,
Sérgio Basto wrote:
- 3:kdeplasma-addons-4.14.3-2.fc23.x86_64 is obsoleted by
3:kdeplasma-addons-4.14.3-2.fc23.x86_64 !
It Obsoletes itself? Or did you get something wrong?
- could not find requested component: folderview
Missing Requires: kde-plasma-folderview somewhere. And this comes from the kde-baseapps SRPM, you may have to rebuild it too, probably with bumped Epoch to bypass Obsoletes from Plasma 5.
- kde-style-oxygen-3:4.11.22-3.fc23.x86_64 conflicts with file from
package qt4-style-oxygen-5.4.2-1.fc23.x86_64 ( dnf remove qt4-style-oxygen-5.4.2-1.fc23.x86_64 solve it )
Missing Obsoletes.
- kde-workspace-3:4.11.22-3.fc23.x86_64 conflicts with file from package
plasma-desktop-doc-5.4.2-2.fc23.noarch (dnf remove plasma-desktop-doc solve it)
Missing Obsoletes.
- /usr/share/doc/HTML/en/kinfocenter/kinfocenter.png from install of
kde-workspace-3:4.11.22-3.fc23.x86_64 (dnf remove kinfocenter solve it)
Missing Obsoletes.
- Error: nothing provides pykde4(x86-64) >= 4.14.11 needed by
plasma-scriptengine-python-3:4.11.22-3.fc23.x86_64
Wrong versioned Requires, should require only the version of pykde4 that is actually available.
- ksysguard have a conflict libksysguard-common ( don't have the
logs...)
You will either want to rebuild libksysguard without the files from: https://bugzilla.redhat.com/show_bug.cgi?id=1185851 or you might be able to just add Obsoletes for libksysguard, libksysguard-common and libksysguard-devel, if no KF5 application other than Plasma 5 itself needs them.
Kevin Kofler
Thanks for enabling this repo, tomorrow morning i will try them for a fresh F22 install in my testing laptop.
I would like to also help to maintain this repo, but i just "jumped" to Fedora 5 months ago and i dont know how to help, at least for now, i will try to help by testing.
Hernán El oct. 22, 2015 10:15 PM, "Kevin Kofler" kevin.kofler@chello.at escribió:
Sérgio Basto wrote:
- 3:kdeplasma-addons-4.14.3-2.fc23.x86_64 is obsoleted by
3:kdeplasma-addons-4.14.3-2.fc23.x86_64 !
It Obsoletes itself? Or did you get something wrong?
- could not find requested component: folderview
Missing Requires: kde-plasma-folderview somewhere. And this comes from the kde-baseapps SRPM, you may have to rebuild it too, probably with bumped Epoch to bypass Obsoletes from Plasma 5.
- kde-style-oxygen-3:4.11.22-3.fc23.x86_64 conflicts with file from
package qt4-style-oxygen-5.4.2-1.fc23.x86_64 ( dnf remove qt4-style-oxygen-5.4.2-1.fc23.x86_64 solve it )
Missing Obsoletes.
- kde-workspace-3:4.11.22-3.fc23.x86_64 conflicts with file from package
plasma-desktop-doc-5.4.2-2.fc23.noarch (dnf remove plasma-desktop-doc solve it)
Missing Obsoletes.
- /usr/share/doc/HTML/en/kinfocenter/kinfocenter.png from install of
kde-workspace-3:4.11.22-3.fc23.x86_64 (dnf remove kinfocenter solve it)
Missing Obsoletes.
- Error: nothing provides pykde4(x86-64) >= 4.14.11 needed by
plasma-scriptengine-python-3:4.11.22-3.fc23.x86_64
Wrong versioned Requires, should require only the version of pykde4 that is actually available.
- ksysguard have a conflict libksysguard-common ( don't have the
logs...)
You will either want to rebuild libksysguard without the files from: https://bugzilla.redhat.com/show_bug.cgi?id=1185851 or you might be able to just add Obsoletes for libksysguard, libksysguard-common and libksysguard-devel, if no KF5 application other than Plasma 5 itself needs them.
Kevin Kofler
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Hi,
Great feedback ! Actually, I had no time to spin up a VM with F23 yet to do any testing, that is exactly why I have asked for testing it.
I'll work on bits from F22 that I know I need to fix, as per issue tracker. I consider that issue a minor, as there is a workaround for the conflicts. It would be nice to have it install even smoother though.
I will put this info about F23 in tracker as a second issue, and will try to work on fixing it as soon as I have bit more time for it.
Could you please next time fill issue in issue tracker, not only discuss it here ? Information is good, and very helpful for me to iron out the repo issues, but I may miss it.
Regards, Piotr
On Thursday 22 October 2015 23:32:38 Hernán Ramírez wrote:
Thanks for enabling this repo, tomorrow morning i will try them for a fresh F22 install in my testing laptop.
I would like to also help to maintain this repo, but i just "jumped" to Fedora 5 months ago and i dont know how to help, at least for now, i will try to help by testing.
For now I think best option would be to just use it and leave feedback in issue tracker (contact button on corp repo page) for anything I have missed.
You can also get the spec files from git, make changes, and then feed back to the repo. I'll then approve them after testing, and here we go :D
Just to make it clear, with two specs in repo, it is not too hard to maintain it right now. There few more specs that will result from my testing, and from discussion above between Sergio and Kevin, but that should be fine too.
However, regardless if you want to learn a bit more about specs, or know everything about them and see issues straight away, I will accept all the help and try to include any suggestions, whether it will be in form of git pull request, new issue in rebo tracker or in email to this list.
Regards, Piotr
Hi,
On Qua, 2015-10-21 at 16:21 +0100, Piotr Gbyliczek wrote:
Ah, yes ... I've deleted github repo today, moved it to bitbucket
Personal question why you move to bitbucket ?
Hi all,
For those of you interested in this, I did not dropped off the grid (well, I did, but I'm back) and just did some work on the repo[1].
I've updated install info and sorted out packages a bit (thanks Rex, Kevin and Sergio), so on F22 it installs mostly via "dnf upgrade" (ksysguard being exception, workaround in repo description).
Let me know if there's anything more in repo that needs to be pulled along (we can group it or add meta package), or what else from outside repo may be needed for smooth operations.
I've just missed F23 release, but seems that apart from ksysguard, it is installable on F23 too. Again, please test that it works and what may be missing as I haven't tested operations side of things for that version.
If you decide to take it for a spin, remember that until obsoletes/requirements/conflicts are not sorted via spec files, I'm not changing release variable. That means version from today won't be picked up to upgrade on machine that had older installed. it may require removing all packages from my copr repo manually from the system. VM based testing is strongly suggested.
[1] : https://copr.fedoraproject.org/coprs/peem/kde4-fedora/
Regards, Piotr
Am 06.11.2015 um 16:43 schrieb Piotr Gbyliczek:
If you decide to take it for a spin, remember that until obsoletes/requirements/conflicts are not sorted via spec files, I'm not changing release variable. That means version from today won't be picked up to upgrade on machine that had older installed. it may require removing all packages from my copr repo manually from the system. VM based testing is strongly suggested
hence i modified the %dist tag on all my buildmachines so that it contains the build-day because i got tired of edit the release tag additionally to the version or because i decided to re-organize subpackages here and there
[builduser@buildserver:~]$ cat .rpmmacros %_topdir %(echo $HOME)/rpmbuild %__arch_install_post /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot
%fedora 22 %dist .fc%fedora.%(echo $(/bin/date +%Y%m%d)).rh %packager Reindl Harald %vendor thelounge interactive design %php_api .php55 %_smp_mflags -j10 %_include_minidebuginfo 0 %_binary_payload w1.gzdio %_source_payload w1.gzdio %__global_ldflags -Wl,-z,now -Wl,-z,relro,-z,noexecstack
%configure \ CFLAGS="${CFLAGS:-%optflags}"; export CFLAGS; \ CXXFLAGS="${CXXFLAGS:-%optflags}"; export CXXFLAGS; \ FFLAGS="${FFLAGS:-%optflags -I%_fmoddir}"; export FFLAGS; \ FCFLAGS="${FCFLAGS:-%optflags -I%_fmoddir}"; export FCFLAGS; \ LDFLAGS="${LDFLAGS:-%__global_ldflags}"; export LDFLAGS; \ ./configure \\ --host=x86_64-redhat-linux \\ --build=x86_64-redhat-linux \\ --target=x86_64-redhat-linux \\ --program-prefix=%{?_program_prefix} \\ --disable-dependency-tracking \\ --prefix=%{_prefix} \\ --exec-prefix=%{_exec_prefix} \\ --bindir=%{_bindir} \\ --sbindir=%{_sbindir} \\ --sysconfdir=%{_sysconfdir} \\ --datadir=%{_datadir} \\ --includedir=%{_includedir} \\ --libdir=%{_libdir} \\ --libexecdir=%{_libexecdir} \\ --localstatedir=%{_localstatedir} \\ --sharedstatedir=%{_sharedstatedir} \\ --mandir=%{_mandir} \\ --infodir=%{_infodir}
On Friday 06 November 2015 16:47:32 Reindl Harald wrote:
hence i modified the %dist tag on all my buildmachines so that it contains the build-day because i got tired of edit the release tag additionally to the version or because i decided to re-organize subpackages here and there
I would love too, but I'm building using copr, so don't think I have any control over this aspect. Not unless I'll build my own copr/koji system.
Good idea, though.
Regards, Piotr
On Friday 06 November 2015 15:43:44 Piotr Gbyliczek wrote:
If you decide to take it for a spin, remember that until obsoletes/requirements/conflicts are not sorted via spec files, I'm not changing release variable. That means version from today won't be picked up to upgrade on machine that had older installed. it may require removing all packages from my copr repo manually from the system. VM based testing is strongly suggested.
Actually, as Rex suggested to me, this is not very helpful. In addition, repo seems to be near end of the alpha stage. Therefore I will start bumping up release.
Current packages will be rebuild with bumped release today, maybe tomorrow, so whoever wants to test or use it, may hold on for a moment longer for better upgrade experience.
Regards, Piotr
On Sex, 2015-11-06 at 16:05 +0000, Piotr Gbyliczek wrote:
On Friday 06 November 2015 15:43:44 Piotr Gbyliczek wrote:
If you decide to take it for a spin, remember that until obsoletes/requirements/conflicts are not sorted via spec files, I'm not changing release variable. That means version from today won't be picked up to upgrade on machine that had older installed. it may require removing all packages from my copr repo manually from the system. VM based testing is strongly suggested.
We just need do :
dnf disto-sync
Actually, as Rex suggested to me, this is not very helpful. In addition, repo seems to be near end of the alpha stage. Therefore I will start bumping up release.
Current packages will be rebuild with bumped release today, maybe tomorrow, so whoever wants to test or use it, may hold on for a moment longer for better upgrade experience.
I was going to ask the same question, I saw that you already build base apps , I had install it 2 days ago from yours copr repo , as is working very well .
Thanks for doing this , I'd love help you and keep this as non-official release , because I'm going upgrade my laptop to F23 but with KDE4 .
Regards, Piotr
Best regards,
On Friday 06 November 2015 16:30:39 Sérgio Basto wrote:
I was going to ask the same question, I saw that you already build base apps , I had install it 2 days ago from yours copr repo , as is working very well .
Good to hear that.
Thanks for doing this , I'd love help you and keep this as non-official release , because I'm going upgrade my laptop to F23 but with KDE4 .
As previously, testing and reporting would be most helpful in my opinion.
You can as well git pull the repo, make changes in existing or add new specs (there's no point submitting rpms, but you can as well), and submit it back with pull request. I'll check the changes and send it to copr builders if approved.
Regards
On Sex, 2015-11-06 at 16:05 +0000, Piotr Gbyliczek wrote:
Current packages will be rebuild with bumped release today, maybe tomorrow, so whoever wants to test or use it, may hold on for a moment longer for better upgrade experience.
Now I'm getting this problem :
nothing provides colord-kde < 0.4 needed by kde-workspace-3:4.11.22-4.fc23.x86_64.
repoquery colord-kde --show-duplicates colord-kde-0:0.4.0-2.20150519git.fc23.x86_64 colord-kde-3:0.3.0-6.fc23.x86_64 colord-kde-3:0.3.0-7.fc23.x86_64
seems lower than 0.4 doesn't work , so maybe colord-kde=3
Sérgio Basto wrote:
On Sex, 2015-11-06 at 16:05 +0000, Piotr Gbyliczek wrote:
Current packages will be rebuild with bumped release today, maybe tomorrow, so whoever wants to test or use it, may hold on for a moment longer for better upgrade experience.
Now I'm getting this problem :
nothing provides colord-kde < 0.4 needed by kde-workspace-3:4.11.22-4.fc23.x86_64.
repoquery colord-kde --show-duplicates colord-kde-0:0.4.0-2.20150519git.fc23.x86_64 colord-kde-3:0.3.0-6.fc23.x86_64 colord-kde-3:0.3.0-7.fc23.x86_64
seems lower than 0.4 doesn't work , so maybe colord-kde=3
You need to use Requires: colord-kde >= 3:0 now, to match the bumped Epoch.
Kevin Kofler
Sérgio Basto wrote:
On Sex, 2015-11-06 at 16:05 +0000, Piotr Gbyliczek wrote:
Current packages will be rebuild with bumped release today, maybe tomorrow, so whoever wants to test or use it, may hold on for a moment longer for better upgrade experience.
Now I'm getting this problem :
nothing provides colord-kde < 0.4 needed by kde-workspace-3:4.11.22-4.fc23.x86_64.
repoquery colord-kde --show-duplicates colord-kde-0:0.4.0-2.20150519git.fc23.x86_64 colord-kde-3:0.3.0-6.fc23.x86_64 colord-kde-3:0.3.0-7.fc23.x86_64
seems lower than 0.4 doesn't work , so maybe colord-kde=3
I recommended on irc to make a new parallel-installable colord-kde4 and then depend on that
-- Rex
-
Hernán Ramírez -
Kevin Kofler -
Piotr Gbyliczek -
Reindl Harald -
Rex Dieter -
Sérgio Basto