Just upgraded a system from F22-->F23. In the process 23 packages were downgraded. dnf is quiet but apper wants to "update" to the "latest" version from the F22 repository.
I enabled F23 updates-testing and 10 of the 23 packages have updates so I allowed dnf to process those. This leaves me with apper complaining about 13. Anyway to tell apper to not look in the F22 repositories? Or must I just have to wait until those packages get their F23 updates?
maybe some old metadata
rm -rf /var/cache/yum/* rm -rf /var/cache/dnf/*
Am 05.11.2015 um 15:23 schrieb Ed Greshko:
Just upgraded a system from F22-->F23. In the process 23 packages were downgraded. dnf is quiet but apper wants to "update" to the "latest" version from the F22 repository.
I enabled F23 updates-testing and 10 of the 23 packages have updates so I allowed dnf to process those. This leaves me with apper complaining about 13. Anyway to tell apper to not look in the F22 repositories? Or must I just have to wait until those packages get their F23 updates?
On 11/05/15 22:32, Reindl Harald wrote:
maybe some old metadata
rm -rf /var/cache/yum/* rm -rf /var/cache/dnf/*
No change after doing that.
I suppose it is really a "packageKit" thing but still....
[root@acer dnf]# pkcon get-updates Getting updates [=========================] Starting [=========================] Finished [=========================] Available libkgapi-2.2.0-5.fc22.x86_64 (updates) Library to access to Google services Available libnl3-3.2.27-1.fc22.x86_64 (updates) Convenience library for kernel netlink sockets Available libnl3-cli-3.2.27-1.fc22.x86_64 (updates) Command line interface utils for libnl3 Available lv2-fabla-1.3-0.1.20150303gitcfbd4b3.fc22.x86_64 (updates) An LV2 drum sequencer Available mariadb-1:10.0.21-1.fc22.x86_64 (updates) A community developed branch of MySQL Available mariadb-common-1:10.0.21-1.fc22.x86_64 (updates) The shared files required by server and client Available mariadb-config-1:10.0.21-1.fc22.x86_64 (updates) The config files required by server and client Available mariadb-embedded-1:10.0.21-1.fc22.x86_64 (updates) MariaDB as an embeddable library Available mariadb-errmsg-1:10.0.21-1.fc22.x86_64 (updates) The error messages files required by server and embedded Available mariadb-libs-1:10.0.21-1.fc22.x86_64 (updates) The shared libraries required for MariaDB/MySQL clients Available mariadb-server-1:10.0.21-1.fc22.x86_64 (updates) The MariaDB server and related files Available mdadm-3.3.4-2.fc22.x86_64 (updates) The mdadm program controls Linux md devices (software RAID arrays) Available sos-3.2-15.fc22.noarch (fedora) A set of tools to gather troubleshooting information from a system
Am 05.11.2015 um 15:23 schrieb Ed Greshko:
Just upgraded a system from F22-->F23. In the process 23 packages were downgraded. dnf is quiet but apper wants to "update" to the "latest" version from the F22 repository.
I enabled F23 updates-testing and 10 of the 23 packages have updates so I allowed dnf to process those. This leaves me with apper complaining about 13. Anyway to tell apper to not look in the F22 repositories? Or must I just have to wait until those packages get their F23 updates?
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 Qui, 2015-11-05 at 17:26 +0100, Kevin Kofler wrote:
Ed Greshko wrote:
I suppose it is really a "packageKit" thing but still....
So use: pkcon refresh --force
pkcon refresh force (is the correct sintax)
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
On 11/06/15 00:26, Kevin Kofler wrote:
Ed Greshko wrote:
I suppose it is really a "packageKit" thing but still....
So use: pkcon refresh --force
Thanks that cleared it...
FYI, I know you didn't mean it that way but "So use" sounds sarcastic to my ears, as if it was supposed to be obvious. :-)
On Thu, Nov 5, 2015 at 5:32 PM, Reindl Harald h.reindl@thelounge.net wrote:
maybe some old metadata
rm -rf /var/cache/yum/* rm -rf /var/cache/dnf/*
Apper (PackageKit) metadata is not in these directories.
Mustafa
Am 05.11.2015 um 15:23 schrieb Ed Greshko:
Just upgraded a system from F22-->F23. In the process 23 packages were downgraded. dnf is quiet but apper wants to "update" to the "latest" version from the F22 repository.
I enabled F23 updates-testing and 10 of the 23 packages have updates so I allowed dnf to process those. This leaves me with apper complaining about 13. Anyway to tell apper to not look in the F22 repositories? Or must I just have to wait until those packages get their F23 updates?
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Am 05.11.2015 um 15:52 schrieb Mustafa Muhammad:
On Thu, Nov 5, 2015 at 5:32 PM, Reindl Harald <h.reindl@thelounge.net mailto:h.reindl@thelounge.net> wrote:
maybe some old metadata rm -rf /var/cache/yum/* rm -rf /var/cache/dnf/*Apper (PackageKit) metadata is not in these directories
one reaosn more that i don't use all the graphical crap for system updates and just use yum/dnf while remove *anything* not really needed from systems i maintain
Am 05.11.2015 um 15:58 schrieb Reindl Harald:
Am 05.11.2015 um 15:52 schrieb Mustafa Muhammad:
On Thu, Nov 5, 2015 at 5:32 PM, Reindl Harald <h.reindl@thelounge.net mailto:h.reindl@thelounge.net> wrote:
maybe some old metadata rm -rf /var/cache/yum/* rm -rf /var/cache/dnf/*Apper (PackageKit) metadata is not in these directories
one reaosn more that i don't use all the graphical crap for system updates and just use yum/dnf while remove *anything* not really needed from systems i maintain
BTW - why do we have that PackageKit crap now as dependency?
Resolving Dependencies --> Running transaction check ---> Package PackageKit.x86_64 0:1.0.10-2.fc23 will be erased --> Processing Dependency: PackageKit for package: PackageKit-Qt5-0.9.5-3.fc23.x86_64 --> Running transaction check ---> Package PackageKit-Qt5.x86_64 0:0.9.5-3.fc23 will be erased --> Processing Dependency: libpackagekitqt5.so.0()(64bit) for package: plasma-desktop-5.4.2-2.fc23.x86_64 --> Running transaction check ---> Package plasma-desktop.x86_64 0:5.4.2-2.fc23 will be erased --> Processing Dependency: plasmashell >= 5.4 for package: plasma-workspace-5.4.2-4.fc23.x86_64 --> Running transaction check ---> Package plasma-workspace.x86_64 0:5.4.2-4.fc23 will be erased --> Processing Dependency: plasma-workspace = 5.4.2-4.fc23 for package: sddm-breeze-5.4.2-4.fc23.noarch --> Processing Dependency: plasma-workspace for package: kde-print-manager-15.04.2-3.fc23.x86_64 --> Running transaction check ---> Package kde-print-manager.x86_64 0:15.04.2-3.fc23 will be erased --> Processing Dependency: kde-print-manager for package: lounge-rhsoft-workstation-23.0-5.fc23.20151105.rh.noarch --> Processing Dependency: kde-print-manager = 15.04.2-3.fc23 for package: kde-print-manager-libs-15.04.2-3.fc23.x86_64 ---> Package sddm-breeze.noarch 0:5.4.2-4.fc23 will be erased --> Running transaction check ---> Package kde-print-manager-libs.x86_64 0:15.04.2-3.fc23 will be erased ---> Package lounge-rhsoft-workstation.noarch 0:23.0-5.fc23.20151105.rh will be erased --> Processing Dependency: lounge-rhsoft-workstation for package: lounge-rhsoft-extras-23.0-1.fc23.20151105.rh.noarch --> Running transaction check ---> Package lounge-rhsoft-extras.noarch 0:23.0-1.fc23.20151105.rh will be erased --> Processing Dependency: qt3(x86-64) for package: redhat-lsb-desktop-4.1-30.fc23.x86_64 --> Running transaction check ---> Package redhat-lsb-desktop.x86_64 0:4.1-30.fc23 will be erased --> Processing Dependency: redhat-lsb-desktop(x86-64) = 4.1-30.fc23 for package: redhat-lsb-4.1-30.fc23.x86_64 --> Running transaction check ---> Package redhat-lsb.x86_64 0:4.1-30.fc23 will be erased --> Processing Dependency: lsb >= 4.0 for package: google-chrome-stable-46.0.2490.80-1.x86_64 --> Running transaction check ---> Package google-chrome-stable.x86_64 0:46.0.2490.80-1 will be erased --> Finished Dependency Resolution
On Nov 5, 2015 13:00, "Reindl Harald" h.reindl@thelounge.net wrote:
BTW - why do we have that PackageKit crap now as dependency?
Good question. I can understand how it might be incorporated as a spin default but why would it be a dependency?
Wasn't there a thread about apper having issues and it was going to be replaced by muon... but muon had issues also.
I've never had much luck with apper... It was always annoying so I disabled it long ago, and after the thread about muon, not particularly enthusiastic about giving it a try. Command line is much simpler and it works. On Nov 5, 2015 12:23, "Ed Greshko" ed.greshko@greshko.com wrote:
Just upgraded a system from F22-->F23. In the process 23 packages were downgraded. dnf is quiet but apper wants to "update" to the "latest" version from the F22 repository.
I enabled F23 updates-testing and 10 of the 23 packages have updates so I allowed dnf to process those. This leaves me with apper complaining about 13. Anyway to tell apper to not look in the F22 repositories? Or must I just have to wait until those packages get their F23 updates?
-- In reality, some people should stick to running Windows and others should stay away from computers altogether. _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
-
Ed Greshko -
Gerald B. Cox -
Germano Massullo -
Kevin Kofler -
Mustafa Muhammad -
Reindl Harald -
Sérgio Basto