EOL kcm-gtk/xsettings-kde for f24+ ?
by Rex Dieter
Given that upstream uses kde-gtk-config now, any objection to EOL'ing kcm-
gtk/xsettings-kde for f24+ ?
Plan (probably) would be for f24+ builds of kde-gtk-config to Obsoletes:
those other items for an upgrade path.
Any comment or objection?
-- Rex
8 years
Recent problem enabling kde-redhat repo
by Peter G.
For years, I have been using the kdeforge.repo file,
but since a while, I have been having
difficulties/impossibility to get anything.
I spent the last hour trying to muddle through the
various repo files and I am unable to determine which
is the one to use: kde.repo, kdeforge.repo, kde-
redhat.repo, etc.
Also, and this is where the problem seems to lie, some
of these repo files refer to the mirrorlist at:
http://apt.kde-redhat.org/apt/kde-redhat/fedora/mirrors-stable|testing|un...
while other of these repo files refer to the location
of the mirrorlist at:
http://apt.kde-redhat.org/apt/kde-redhat/fedora/23/x86_64/[stable/mirrors|
testing/mirrors|unstable/mirrors]
No matter which combination I seem to try, dnf hangs
for ages and then returns and error:
Failed to synchronize cache for repo 'kde-unstable'
from...
Cannot download, all mirrors were already tried
without success, disabling.
So, how do I get this working? Which is the correct
repo file and which is the correct location of the
mirror list?
8 years
Language Pack broken?
by Florian Sievert
Hi there,
I am currently on kf5 5.21, plasma 5.5 and qt 5.6 from the testing
repos. I just noticed that the i18n from dolphin seems to be broken as
the "general" menu from it is in english, while the rest is German. I
just noticed that the packages are marked by dnf when trying to perform
an update. I am not sure why these packages seems to fail upgrading, so
any ideas? Not sure if I am stuck on some weird package combination or
might be a general issue with the language packs.
Best regards,
Florian
[root@phobos ~]# LC_ALL=C dnf update --enablerepo=kde-unstable
--enablerepo=kde-testing
Failed to synchronize cache for repo 'kde-unstable', disabling.
0% [
] --- B/s | 0 B --:-- ETA
Last metadata expiration check: 0:02:48 ago on Sat Apr 16 20:36:20 2016.
Dependencies resolved.
==================================================================================================================================================================================
Package
Arch
Version
Repository Size
==================================================================================================================================================================================
Skipping packages with broken dependencies:
kde-l10n
noarch
15.12.3-5.fc23
updates 9.2 k
kde-l10n-de
noarch
15.12.3-5.fc23
updates 34 M
ksnapshot
x86_64
15.08.3-4.fc23
updates 613 k
Transaction Summary
==================================================================================================================================================================================
Skip 3 Packages
Nothing to do.
Complete!
[root@phobos ~]# LC_ALL=C dnf repoquery --requires kde-l10n
Last metadata expiration check: 1:47:54 ago on Sat Apr 16 18:52:18 2016.
kde-filesystem
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
[root@phobos ~]# dnf info kde-filesystem
Letzte Prüfung auf abgelaufene Metadaten: vor 1:48:06 am Sat Apr 16
18:52:18 2016.
Installierte Pakete
Name : kde-filesystem
Arch : x86_64
Epoch : 0
Version : 4
Release : 52.fc23
Größe : 3.9 k
Paketquelle : @System
Aus Paketqu : @commandline
Zusammenfas : KDE filesystem layout
Lizenz : Public Domain
Beschreibun : This package provides some directories that are
required/used by KDE.
8 years
Re: Re: Libunity / Chrome/Chromium Download notifications
by Gerald B. Cox
Oops, forgot to add distribution...
On Sun, Apr 17, 2016 at 8:08 AM, Gerald B. Cox <gbcox(a)bzb.us> wrote:
>
> On Sun, Apr 17, 2016 at 1:13 AM, Colin J Thomson <
> colin.thomson(a)g6avk.co.uk> wrote:
>
>>
>> I don't see that bug, I guess because that bug appears on Chromium 51
>> which is
>> the unstable branch.
>>
>> Test it with Chromium 50 (stable)
>>
>
> Yes, see my previous message about
> https://bugs.chromium.org/p/chromium/issues/detail?id=604171
> where I talk about Chrome stable and unstable branches.
>
> It's a bit of alphabet (pun intended) soup, but there is no concept of
> stable, beta or unstable in Chromium... that
> only applies to Chrome.
>
> Chrome 51 is getting ready to move to the beta branch, most likely next
> week - so hopefully this can be
> resolved before it hits stable (which will be around the first week of
> June).
>
> The problem of course is that many people do not run Chrome unstable, and
> of those that do, the subset that use
> libunity is less than that - so not many people have encountered this
> yet. Anyone who encounters this, please
> star the bug.
>
> I started running unstable due to the previous bug regarding status area
> icons in plasma that made it into stable. You
> can really complain if you don't help test.
>
>
8 years
libunity testing
by Gerald B. Cox
Rex,
Thanks for putting libunity out on copr for F23 testing... but unless I am
mistaken, to really test out the functionality I also need plasma-workspace
5.6 - and looks like that is only available for F24+.
Do you have a timeframe when plama-workspace 5.6 will be out in the testing
repo for F23? Not trying to rush you... I'm sure you have other things
with a higher priority.... just asking.
For those of you who don't know what this is all about:
http://blog.broulik.de/2016/01/on-being-more-convenient/
8 years
