I needed to downgrade the xorg-x11* packages on an F23 Vbox based system so I can get the drivers to run in full-screen. I would like to have apper not tell me that 14 packages are available for update. I can exclude them so dnf doesn't touch them. I could hide Software Updates from the systray so it would be less annoying and just use dnf...but would like to be visually notified of updates. I thought creating a /etc/yum.conf with an exclude line would do the trick...but no.
Any ideas?
Ed Greshko wrote:
I needed to downgrade the xorg-x11* packages on an F23 Vbox based system so I can get the drivers to run in full-screen. I would like to have apper not tell me that 14 packages are available for update. I can exclude them so dnf doesn't touch them. I could hide Software Updates from the systray so it would be less annoying and just use dnf...but would like to be visually notified of updates. I thought creating a /etc/yum.conf with an exclude line would do the trick...but no.
Any ideas?
Try putting the exclude into the .repo files, those are supposed to be honored by all the tools.
Kevin Kofler
Am 07.11.2015 um 13:53 schrieb Kevin Kofler:
Ed Greshko wrote:
I needed to downgrade the xorg-x11* packages on an F23 Vbox based system so I can get the drivers to run in full-screen. I would like to have apper not tell me that 14 packages are available for update. I can exclude them so dnf doesn't touch them. I could hide Software Updates from the systray so it would be less annoying and just use dnf...but would like to be visually notified of updates. I thought creating a /etc/yum.conf with an exclude line would do the trick...but no.
Any ideas?
Try putting the exclude into the .repo files, those are supposed to be honored by all the tools
on F23 it's pretty sure /etc/dnf/dnf.conf and not yum.conf
one reason more that it was completly insane not finish the dnf development (actually it's alpha or beta software) and rename it back to yum with all the same configuration paths instead dig around where things are moved now
Am 07.11.2015 um 14:44 schrieb Kevin Kofler:
Reindl Harald wrote:
on F23 it's pretty sure /etc/dnf/dnf.conf and not yum.conf
dnf.conf is also ignored by PackageKit. The only config files that are really read by all tools are the .repo files.
ok, i am going out to puke deep from my heart....
On Sáb, 2015-11-07 at 14:44 +0100, Kevin Kofler wrote:
Reindl Harald wrote:
on F23 it's pretty sure /etc/dnf/dnf.conf and not yum.conf
dnf.conf is also ignored by PackageKit. The only config files that are really read by all tools are the .repo files.
https://bugzilla.redhat.com/show_bug.cgi?id=1256108
On 11/07/15 22:10, Sérgio Basto wrote:
On Sáb, 2015-11-07 at 14:44 +0100, Kevin Kofler wrote:
Reindl Harald wrote:
on F23 it's pretty sure /etc/dnf/dnf.conf and not yum.conf
dnf.conf is also ignored by PackageKit. The only config files that are really read by all tools are the .repo files.
Thanks for the link.
On 11/07/15 21:11, Reindl Harald wrote:
Am 07.11.2015 um 13:53 schrieb Kevin Kofler:
Ed Greshko wrote:
I needed to downgrade the xorg-x11* packages on an F23 Vbox based system so I can get the drivers to run in full-screen. I would like to have apper not tell me that 14 packages are available for update. I can exclude them so dnf doesn't touch them. I could hide Software Updates from the systray so it would be less annoying and just use dnf...but would like to be visually notified of updates. I thought creating a /etc/yum.conf with an exclude line would do the trick...but no.
Any ideas?
Try putting the exclude into the .repo files, those are supposed to be honored by all the tools
on F23 it's pretty sure /etc/dnf/dnf.conf and not yum.conf
I think my run on sentence may have confused folks. I did put the exclude in the dnf.conf to silence dnf from trying to upgrade. It had no effect on apper. Now I have the exclude in all the enabled repos and still no joy. :-(
Ed Greshko wrote:
I think my run on sentence may have confused folks. I did put the exclude in the dnf.conf to silence dnf from trying to upgrade. It had no effect on apper. Now I have the exclude in all the enabled repos and still no joy. :-(
That's an outright PackageKit or libhif bug then. :-( There is no excuse for not honoring the exclude lines in the .repo files.
Kevin Kofler
On 11/08/15 01:02, Kevin Kofler wrote:
Ed Greshko wrote:
I think my run on sentence may have confused folks. I did put the exclude in the dnf.conf to silence dnf from trying to upgrade. It had no effect on apper. Now I have the exclude in all the enabled repos and still no joy. :-(
That's an outright PackageKit or libhif bug then. :-( There is no excuse for not honoring the exclude lines in the .repo files.
I suppose the good news is "it isn't a plasma bug". :-) :-)
Ed Greshko wrote:
On 11/07/15 21:11, Reindl Harald wrote:
Am 07.11.2015 um 13:53 schrieb Kevin Kofler:
Ed Greshko wrote:
I needed to downgrade the xorg-x11* packages on an F23 Vbox based system so I can get the drivers to run in full-screen. I would like to have apper not tell me that 14 packages are available for update. I can exclude them so dnf doesn't touch them. I could hide Software Updates from the systray so it would be less annoying and just use dnf...but would like to be visually notified of updates. I thought creating a /etc/yum.conf with an exclude line would do the trick...but no.
Any ideas?
Try putting the exclude into the .repo files, those are supposed to be honored by all the tools
on F23 it's pretty sure /etc/dnf/dnf.conf and not yum.conf
I think my run on sentence may have confused folks. I did put the exclude in the dnf.conf to silence dnf from trying to upgrade. It had no effect on apper. Now I have the exclude in all the enabled repos and still no joy. :-(
I just tested this and it worked for me. *However*, I did force a metadata refresh after making the change.
pkcon refresh force
try that ^^ ?
-- Rex
On 11/08/15 06:50, Rex Dieter wrote:
I just tested this and it worked for me. *However*, I did force a metadata refresh after making the change.
pkcon refresh force
try that ^^ ?
Yes, I did that after being "schooled" in the "apper after upgrade thread".
No joy....
Ed Greshko wrote:
On 11/08/15 06:50, Rex Dieter wrote:
I just tested this and it worked for me. *However*, I did force a metadata refresh after making the change.
pkcon refresh force
try that ^^ ?
Yes, I did that after being "schooled" in the "apper after upgrade thread".
OK, can you post *exactly* what you're trying, so that I can duplicate things?
What I did, was downgrade kgamma-5.4.3 (from kde-testing) to kgamma-5.4.2 (updates) with:
dnf downgrade kgamma
Then, I edited /etc/yum.repos.d/kde.repo
[kde-testing] ... exclude=kgamma
and after refreshing, neither pk-plasma-updates or apper reports that as an update anymore.
When I remove the exclude=kgamma
apper reports it as available again.
-- Rex
On 11/08/15 07:01, Rex Dieter wrote:
Ed Greshko wrote:
On 11/08/15 06:50, Rex Dieter wrote:
I just tested this and it worked for me. *However*, I did force a metadata refresh after making the change.
pkcon refresh force
try that ^^ ?
Yes, I did that after being "schooled" in the "apper after upgrade thread".
OK, can you post *exactly* what you're trying, so that I can duplicate things?
Sure....
dnf --showduplicates --allowerasing --releasever=22 downgrade xorg-x11-server-Xorg
edited all the enabled fedora repos so ...
[root@localhost yum.repos.d]# grep excl *repo fedora.repo:exclude=xorg-x11* fedora-updates.repo:exclude=xorg-x11* fedora-updates-testing.repo:exclude=xorg-x11*
[root@localhost yum.repos.d]# pkcon refresh force
And apper reports 14 packages available for upgrade
Ed Greshko wrote:
On 11/08/15 07:01, Rex Dieter wrote:
Ed Greshko wrote:
On 11/08/15 06:50, Rex Dieter wrote:
I just tested this and it worked for me. *However*, I did force a metadata refresh after making the change.
pkcon refresh force
try that ^^ ?
Yes, I did that after being "schooled" in the "apper after upgrade thread".
OK, can you post *exactly* what you're trying, so that I can duplicate things?
Sure....
dnf --showduplicates --allowerasing --releasever=22 downgrade xorg-x11-server-Xorg
edited all the enabled fedora repos so ...
[root@localhost yum.repos.d]# grep excl *repo fedora.repo:exclude=xorg-x11* fedora-updates.repo:exclude=xorg-x11* fedora-updates-testing.repo:exclude=xorg-x11*
Where you put the exclude lines in those files is important too, they must by in the [fedora] [fedora-updates] [fedora-updates-testing] sections respectively (not in -debuginfo or -sources)
-- Rex
On 11/08/15 07:28, Rex Dieter wrote:
Ed Greshko wrote:
On 11/08/15 07:01, Rex Dieter wrote:
Ed Greshko wrote:
On 11/08/15 06:50, Rex Dieter wrote:
I just tested this and it worked for me. *However*, I did force a metadata refresh after making the change.
pkcon refresh force
try that ^^ ?
Yes, I did that after being "schooled" in the "apper after upgrade thread".
OK, can you post *exactly* what you're trying, so that I can duplicate things?
Sure....
dnf --showduplicates --allowerasing --releasever=22 downgrade xorg-x11-server-Xorg
edited all the enabled fedora repos so ...
[root@localhost yum.repos.d]# grep excl *repo fedora.repo:exclude=xorg-x11* fedora-updates.repo:exclude=xorg-x11* fedora-updates-testing.repo:exclude=xorg-x11*
Where you put the exclude lines in those files is important too, they must by in the [fedora] [fedora-updates] [fedora-updates-testing] sections respectively (not in -debuginfo or -sources)
Of course... As I said, the "enabled" repos....
[fedora] name=Fedora $releasever - $basearch failovermethod=priority exclude=xorg-x11* #baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/E verything/$basearch/os/ metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=... basearch enabled=1 <------------------These...... metadata_expire=28d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch skip_if_unavailable=False
[updates] name=Fedora $releasever - $basearch - Updates failovermethod=priority exclude=xorg-x11* #baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$b asearch/ metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releas ever&arch=$basearch enabled=1 gpgcheck=1 metadata_expire=6h gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch skip_if_unavailable=False
[updates-testing] name=Fedora $releasever - $basearch - Test Updates failovermethod=priority exclude=xorg-x11* #baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/testing/$relea sever/$basearch/ metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f$release ver&arch=$basearch enabled=0 gpgcheck=1 metadata_expire=6h gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch skip_if_unavailable=False
On 11/08/15 07:33, Rex Dieter wrote:
Ed Greshko wrote:
Of course... As I said, the "enabled" repos....
OK, lastly, does yum or dnf see this updates too or not?
Either way, something wierd is going on.
I did edit dnf.conf .... (which I sort of mentioned in my original message)
[root@localhost dnf]# cat dnf.conf [main] gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=true exclude=xorg-x11*
[root@localhost dnf]# dnf --refresh check-update Fedora 23 - x86_64 2.1 MB/s | 43 MB 00:20 Fedora 23 - x86_64 - Updates 1.4 MB/s | 4.9 MB 00:03 Last metadata expiration check performed 0:00:06 ago on Sun Nov 8 07:37:24 2015. [root@localhost dnf]#
Ed Greshko wrote:
On 11/08/15 07:33, Rex Dieter wrote:
Ed Greshko wrote:
Of course... As I said, the "enabled" repos....
OK, lastly, does yum or dnf see this updates too or not?
Either way, something wierd is going on.
I did edit dnf.conf .... (which I sort of mentioned in my original message)
Please remove the exclude from dnf.conf and retest (it should not be needed if in .repo files). I'm curious if it dnf behavior is the same as pk or not wrt to exclude= in .repo files only.
-- Rex
On 11/08/15 07:41, Rex Dieter wrote:
Ed Greshko wrote:
On 11/08/15 07:33, Rex Dieter wrote:
Ed Greshko wrote:
Of course... As I said, the "enabled" repos....
OK, lastly, does yum or dnf see this updates too or not?
Either way, something wierd is going on.
I did edit dnf.conf .... (which I sort of mentioned in my original message)
Please remove the exclude from dnf.conf and retest (it should not be needed if in .repo files). I'm curious if it dnf behavior is the same as pk or not wrt to exclude= in .repo files only.
[root@localhost dnf]# cat dnf.conf [main] gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=true [root@localhost dnf]#
root@localhost dnf]# dnf clean all Cleaning repos: updates fedora Cleaning up Everything [root@localhost dnf]# dnf --refresh check-update Fedora 23 - x86_64 - Updates 1.7 MB/s | 4.9 MB 00:02 Fedora 23 - x86_64 2.0 MB/s | 43 MB 00:21 Last metadata expiration check performed 0:00:34 ago on Sun Nov 8 07:45:02 2015. [root@localhost dnf]#
Ed Greshko wrote:
edited all the enabled fedora repos so ...
[root@localhost yum.repos.d]# grep excl *repo fedora.repo:exclude=xorg-x11* fedora-updates.repo:exclude=xorg-x11* fedora-updates-testing.repo:exclude=xorg-x11*
I guess the wildcards don't work, you probably have to list the packages individually (comma-separated).
Kevin Kofler
Am 08.11.2015 um 00:33 schrieb Kevin Kofler:
Ed Greshko wrote:
edited all the enabled fedora repos so ...
[root@localhost yum.repos.d]# grep excl *repo fedora.repo:exclude=xorg-x11* fedora-updates.repo:exclude=xorg-x11* fedora-updates-testing.repo:exclude=xorg-x11*
I guess the wildcards don't work, you probably have to list the packages individually (comma-separated)
than it is a bug in apper because for YUM wildcards are working
[root@buildserver:~]$ cat /etc/yum.repos.d/fedora.repo [fedora] name=Fedora $releasever - $basearch failovermethod=priority #baseurl=https://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Eve... mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=... enabled=1 metadata_expire=1d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch exclude=*.i686,up-imapproxy,open-vm-tools,phpMyAdmin,trafficserver,roundcubemail,gmime,gmime-devel,mariadb*,php-mysqlnd,php-pdo,php-pear,php-posix,mod_ssl,httpd,httpd-devel,php-opcache,php-enchant,php-dba,php-embedded,php-interbase,php-intl,php-mssql,php-odbc,php-pgsql,php-pspell,php-recode,php-snmp,php,php-bcmath,php-cli,php-common,php-devel,php-gd,php-imap,php-ldap,php-mbstring,php-mcrypt,php-mysql,php-pdo,php-pecl-apc,php-pecl-bbcode,php-pecl-crack,php-pecl-geoip,php-pecl-id3,php-pecl-imagick,php-pecl-mailparse,php-pecl-mysqlnd_qc,php-pecl-ssh2,php-pecl-uploadprogress,php-pecl-xdebug,php-process,php-soap,php-suhosin,php-tidy,php-xml,php-xmlrpc,dbmail*,httpd,postfix*,dovecot*,mod_security,GeoIP*,lame*,ffmpeg,x264,x264-libs,x264-devel,vnstat,netatalk [root@buildserver:~]$
On 11/08/15 07:33, Kevin Kofler wrote:
Ed Greshko wrote:
edited all the enabled fedora repos so ...
[root@localhost yum.repos.d]# grep excl *repo fedora.repo:exclude=xorg-x11* fedora-updates.repo:exclude=xorg-x11* fedora-updates-testing.repo:exclude=xorg-x11*
I guess the wildcards don't work, you probably have to list the packages individually (comma-separated).
Nope.... Used...
exclude=xorg-x11-drv-intel,xorg-x11-drv-openchrome,xorg-x11-drv-ati,xorg-x11-server-Xorg,xorg-x11-drv-qxl,xorg-x11-drv-fbdev,xorg-x11-drv-vmmouse,xorg-x11-drv-evdev,xorg-x11-drv-vesa,xorg-x11-drv-libinput,xorg-x11-drv-wacom,xorg-x11-server-common,xorg-x11-drv-vmware,xorg-x11-drv-nouveau,xorg-x11-drv-synaptics
and, of course, refresh force.... still apper reports 14 packages to update.
On 11/07/15 20:53, Kevin Kofler wrote:
Ed Greshko wrote:
I needed to downgrade the xorg-x11* packages on an F23 Vbox based system so I can get the drivers to run in full-screen. I would like to have apper not tell me that 14 packages are available for update. I can exclude them so dnf doesn't touch them. I could hide Software Updates from the systray so it would be less annoying and just use dnf...but would like to be visually notified of updates. I thought creating a /etc/yum.conf with an exclude line would do the trick...but no.
Any ideas?
Try putting the exclude into the .repo files, those are supposed to be honored by all the tools.
That didn't help. :-(