8MB of Fedora System Updates as opposed to application updates, right
> from the first boot of F34 after a fresh install, and that calculation
> of how many updates are available never changes irrespective of how many
> updates are applied by dnf and how often. I've had F34 installed in t
em Updates as opposed to application updates, right
from the first boot of F34 after a fresh install, and that calculation
of how many updates are available never changes irrespective of how many
updates are applied by dnf and how often. I've had F34 installed in the
vm for probably aroun
On 2021-06-27 7:59 p.m., Stephen Morris wrote:
On 28/6/21 10:12, Samuel Sieb wrote:
On 2021-06-27 4:12 p.m., Stephen Morris wrote:
On 27/6/21 22:43, Ed Greshko wrote:
On 27/06/2021 20:34, Stephen Morris wrote:
While we are on the topic of updates with dnf, I have noticed that
when dnf goes
was performed and
immediately followed by a need
for another update. I do my updates with "dnf --refresh update".
The only thing I've seen is when packageKit is telling me there
are updates but when dnf
runs it says no updates are available. I attribute that to
packageKit using differe
PackageKit uses libdnf. libdnf is the core library for dnf,PackageKit
and rpm-ostree.
You should generally get the same results using either dnf or PackageKit.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send
On 28/6/21 10:12, Samuel Sieb wrote:
On 2021-06-27 4:12 p.m., Stephen Morris wrote:
On 27/6/21 22:43, Ed Greshko wrote:
On 27/06/2021 20:34, Stephen Morris wrote:
While we are on the topic of updates with dnf, I have noticed that
when dnf goes to a mirror to find an update, if it can't find
On 28/6/21 09:43, Ed Greshko wrote:
On 28/06/2021 07:06, Stephen Morris wrote:
On 28/6/21 05:01, Samuel Sieb wrote:
On 2021-06-27 4:28 a.m., Ed Greshko wrote:
On 27/06/2021 16:31, Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think
upgraded 1311 packages
by a need
for another update. I do my updates with "dnf --refresh update".
The only thing I've seen is when packageKit is telling me there are updates but
when dnf
runs it says no updates are available. I attribute that to packageKit using
different mirrors than
dnf.
I hadn't realise
On 2021-06-27 4:12 p.m., Stephen Morris wrote:
On 27/6/21 22:43, Ed Greshko wrote:
On 27/06/2021 20:34, Stephen Morris wrote:
While we are on the topic of updates with dnf, I have noticed that
when dnf goes to a mirror to find an update, if it can't find the
package it produces a 404 error
updates with "dnf --refresh update".
The only thing I've seen is when packageKit is telling me there are
updates but when dnf
runs it says no updates are available. I attribute that to
packageKit using different mirrors than
dnf.
I hadn't realised Discover was using Packagekit. If i
On 28/06/2021 07:12, Stephen Morris wrote:
On 27/6/21 22:43, Ed Greshko wrote:
On 27/06/2021 20:34, Stephen Morris wrote:
I hadn't realised Discover was using Packagekit. If it is using different
mirrors to dnf and they indicate they have updates over and above what dnf has
applied, does
On 28/06/2021 07:06, Stephen Morris wrote:
On 28/6/21 05:01, Samuel Sieb wrote:
On 2021-06-27 4:28 a.m., Ed Greshko wrote:
On 27/06/2021 16:31, Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages.
After the update finished I rebooted
On 28/6/21 04:59, Samuel Sieb wrote:
On 2021-06-27 5:34 a.m., Stephen Morris wrote:
On 27/6/21 22:23, Ed Greshko wrote:
I have not had a situation where an update was performed and
immediately followed by a need
for another update. I do my updates with "dnf --refresh update".
The
On 27/6/21 22:52, Ed Greshko wrote:
On 27/06/2021 20:45, Ed Greshko wrote:
On 27/06/2021 20:43, Ed Greshko wrote:
On 27/06/2021 20:34, Stephen Morris wrote:
I hadn't realised Discover was using Packagekit. If it is using
different mirrors to dnf and they indicate they have updates over
On 27/6/21 22:43, Ed Greshko wrote:
On 27/06/2021 20:34, Stephen Morris wrote:
I hadn't realised Discover was using Packagekit. If it is using
different mirrors to dnf and they indicate they have updates over and
above what dnf has applied, does that mean dnf will catch up
On 28/6/21 05:01, Samuel Sieb wrote:
On 2021-06-27 4:28 a.m., Ed Greshko wrote:
On 27/06/2021 16:31, Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think
upgraded 1311 packages. After the update finished I rebooted F34 and
then ran discovery and it was still
On 2021-06-27 4:28 a.m., Ed Greshko wrote:
On 27/06/2021 16:31, Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think upgraded
1311 packages. After the update finished I rebooted F34 and then ran
discovery and it was still telling me there was 628 MB of F34
On 2021-06-27 5:34 a.m., Stephen Morris wrote:
On 27/6/21 22:23, Ed Greshko wrote:
I have not had a situation where an update was performed and
immediately followed by a need
for another update. I do my updates with "dnf --refresh update".
The only thing I've seen is when
On 27/06/2021 20:45, Ed Greshko wrote:
On 27/06/2021 20:43, Ed Greshko wrote:
On 27/06/2021 20:34, Stephen Morris wrote:
I hadn't realised Discover was using Packagekit. If it is using different
mirrors to dnf and they indicate they have updates over and above what dnf has
applied, does
On 27/06/2021 20:43, Ed Greshko wrote:
On 27/06/2021 20:34, Stephen Morris wrote:
I hadn't realised Discover was using Packagekit. If it is using different
mirrors to dnf and they indicate they have updates over and above what dnf has
applied, does that mean dnf will catch up
On 27/06/2021 20:34, Stephen Morris wrote:
I hadn't realised Discover was using Packagekit. If it is using different
mirrors to dnf and they indicate they have updates over and above what dnf has
applied, does that mean dnf will catch up, or are they updates that dnf will
never put on because
On 27/6/21 22:30, Ed Greshko wrote:
On 27/06/2021 20:24, Stephen Morris wrote:
On 27/6/21 21:28, Ed Greshko wrote:
On 27/06/2021 16:31, Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think
upgraded 1311 packages. After the update finished I rebooted F34
On 27/6/21 22:23, Ed Greshko wrote:
On 27/06/2021 20:00, Patrick O'Callaghan wrote:
On Sun, 2021-06-27 at 18:31 +1000, Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think
upgraded
1311 packages. After the update finished I rebooted F34 and then ran
On 27/06/2021 20:24, Stephen Morris wrote:
On 27/6/21 21:28, Ed Greshko wrote:
On 27/06/2021 16:31, Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages.
After the update finished I rebooted F34 and then ran discovery and it was still
On 27/6/21 21:28, Ed Greshko wrote:
On 27/06/2021 16:31, Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think upgraded
1311 packages. After the update finished I rebooted F34 and then ran
discovery and it was still telling me there was 628 MB of F34
Platform
On 27/06/2021 20:00, Patrick O'Callaghan wrote:
On Sun, 2021-06-27 at 18:31 +1000, Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think
upgraded
1311 packages. After the update finished I rebooted F34 and then ran
discovery and it was still telling me
On Sun, 2021-06-27 at 18:31 +1000, Stephen Morris wrote:
> Hi,
> I have just done a sudo dnf upgrade on F34 which I think
> upgraded
> 1311 packages. After the update finished I rebooted F34 and then ran
> discovery and it was still telling me there was 628 MB of F34
> P
On 27/06/2021 16:31, Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages.
After the update finished I rebooted F34 and then ran discovery and it was still telling
me there was 628 MB of F34 Platform updates to put on, which I did put
On 27/06/2021 16:53, Samuel Sieb wrote:
On 2021-06-27 1:31 a.m., Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages.
After the update finished I rebooted F34 and then ran discovery and it was still telling
me there was 628 MB of F34
On 2021-06-27 1:31 a.m., Stephen Morris wrote:
Hi,
I have just done a sudo dnf upgrade on F34 which I think upgraded
1311 packages. After the update finished I rebooted F34 and then ran
discovery and it was still telling me there was 628 MB of F34 Platform
updates to put on, which I did
Hi,
I have just done a sudo dnf upgrade on F34 which I think upgraded
1311 packages. After the update finished I rebooted F34 and then ran
discovery and it was still telling me there was 628 MB of F34 Platform
updates to put on, which I did put on. Why is dnf not installing all
updates
On 5/22/21 7:40 PM, Scott Beamer wrote:
I'm having problems with DNF tonight.
Errors during downloading metadata for repository 'updates-testing'
e.g. Downloading successful, but checksum doesn't match. and Curl error
(23): Failed writing received data to disk/application for https
On 5/22/21 8:54 PM, Scott Beamer wrote:
Right after I posted, the problem seems to have resolved itself.
Never mind. :)
Glad to see that, but it's still a good idea to remember my suggestion
if/when it happens again.
___
users mailing list --
On 5/22/21 7:49 PM, Joe Zeff wrote:
On 5/22/21 8:40 PM, Scott Beamer wrote:
I'm having problems with DNF tonight.
Errors during downloading metadata for repository 'updates-testing'
e.g. Downloading successful, but checksum doesn't match. and Curl
error (23): Failed writing received data
On 5/22/21 8:40 PM, Scott Beamer wrote:
I'm having problems with DNF tonight.
Errors during downloading metadata for repository 'updates-testing'
e.g. Downloading successful, but checksum doesn't match. and Curl error
(23): Failed writing received data to disk/application for https
Greetings,
I'm having problems with DNF tonight.
Errors during downloading metadata for repository 'updates-testing'
e.g. Downloading successful, but checksum doesn't match. and Curl error
(23): Failed writing received data to disk/application for https://...
Any suggestions?
Pastebin
Hi.
Can You recommend a plugin, or a shell/prel/python wrapper for dnf
checks in Nagios? Is there a widely accepted one? I'm finding only
plugins for older yum versions, which, according to readmes, may not
work with dnf.
I would really like if it would use cache and do not "dnf update&q
On 5/5/21 10:02 AM, sbob wrote:
Invalid configuration value: failovermethod=priority in
/etc/yum.repos.d/pgdg-fedora-all.repo; Configuration: OptionBinding with
id "failovermethod" does not exist
https://bugzilla.redhat.com/show_bug.cgi?id=1653831
Tell the upstream provider of the file that
Remove failovermethod from /etc/yum.repos.d/pgdg-fedora-all.repo?
---
Best regards, Alex
‐‐‐ Original Message ‐‐‐
On Wednesday, May 5th, 2021 at 19:02, sbob wrote:
> All;
>
> I get this when I run dnf (search, update, etc):
>
> Invalid configuration value: failover
All;
I get this when I run dnf (search, update, etc):
Invalid configuration value: failovermethod=priority in
/etc/yum.repos.d/pgdg-fedora-all.repo; Configuration: OptionBinding with
id "failovermethod" does not exist
Thoughts?
___
ist of problems?
Yes, it was.
dnf sees the .fc34 package, but then claims no knowledge of "selinux-policy
= 34.3-1.fc34".
I see selinux-policy-34.3-1.fc34.noarch.rpm in updates, and with specifying
--allowerasing results in my local packages getting uninstalled, and the
selinux-policy upd
.fc33.20210503063931.x86_64
- libcxxbase-selinux-0.23.0.20210503-1.fc33.20210503063931.x86_64 does
not belong to a distupgrade repository
- nothing provides selinux-policy >= 34.3-1.fc34 needed by
libcxxbase-selinux-0.23.0.20210503-1.fc34.x86_64
Is that the complete list of problems?
dnf sees the .f
-0.23.0.20210503-1.fc33.20210503063931.x86_64 does not
belong to a distupgrade repository
- nothing provides selinux-policy >= 34.3-1.fc34 needed by
libcxxbase-selinux-0.23.0.20210503-1.fc34.x86_64
dnf sees the .fc34 package, but then claims no knowledge of "selinux-policy
= 34.3-1.fc34&q
On 3/31/21 11:30 PM, Qiyu Yan wrote:
Just now during a routine update using `dnf update` my desktop process
gnome-shell crashed.
Afterwards, I checked dnf history and /var/log/dnf.log to see if any
inconsistency is present. dnf.log didn't report the last transaction
as completed, but `dnf
Hi! folks,
Just now during a routine update using `dnf update` my desktop process
gnome-shell crashed.
Afterwards, I checked dnf history and /var/log/dnf.log to see if any
inconsistency is present. dnf.log didn't report the last transaction
as completed, but `dnf history info last` report
When updating the kernel, dnf tries to use dkms to add my NVIDIA
drivers, For some reason it tries to use 390.129 instead of the current
390.141 driver. The manual install works.
/var/lib/dkms/nvidia:
total used in directory 20 available 57.5 GiB
drwxr-xr-x. 5 root root 4096 Mar 12 23:44
On 8 Mar 2021 at 6:12, Michael D. Setzer II via user
wrote:
To: users@lists.fedoraproject.org
Date sent: Mon, 08 Mar 2021 06:12:15 +1000
Subject:dnf update of wine shows error??
Priority: normal
Send reply to: Community
010c:err:process:exec_process failed to load
L"C:\\windows\\syswow64\\rundll32.exe" error c018
wine: configuration in L"H:\\.wine" has been updated.
Just ran dnf update and it installed updates to wine.
Then ran wine notepad to test, and noticed
On Wed, Jan 20, 2021 at 4:27 PM Kostas Sfakiotakis
wrote:
>
> Or a brain -damaged SELINUX is screwing up the /var/ partition because
> of an imaginary threat
> ( a threat that it only exists in it's own twisted mind or whatever
> equivalent it has ) and in so
> doing it fills up the entire /var
On 1/20/21 3:26 PM, Kostas Sfakiotakis wrote:
Στις 20/1/21 2:18 μ.μ., ο/η George N. White III έγραψε:
There is a good chance the storage device is failing. Make sure you have
backups.
Or a brain -damaged SELINUX is screwing up the /var/ partition because
of an imaginary threat
( a threat
wrote:
>> dnf info sendmail
>> error: SELECT hnum, idx FROM 'Providename' WHERE key=?: 11:
database
>> disk image is malformed
>> error: SELECT hnum, idx FROM 'Providename' WHERE key=?: 11:
database
>> disk image is malformed
&
On Tue, 19 Jan 2021 at 19:28, Kostas Sfakiotakis
wrote:
>
> Στις 19/1/21 11:09 μ.μ., ο/η Garry T. Williams έγραψε:
> > On Tuesday, January 19, 2021 3:15:59 PM EST Kostas Sfakiotakis wrote:
> >>dnf info sendmail
> >> error: SELECT hnum, idx FROM 'Providen
Στις 19/1/21 11:09 μ.μ., ο/η Garry T. Williams έγραψε:
On Tuesday, January 19, 2021 3:15:59 PM EST Kostas Sfakiotakis wrote:
dnf info sendmail
error: SELECT hnum, idx FROM 'Providename' WHERE key=?: 11: database
disk image is malformed
error: SELECT hnum, idx FROM 'Providename' WHERE key
On Tuesday, January 19, 2021 3:15:59 PM EST Kostas Sfakiotakis wrote:
> dnf info sendmail
> error: SELECT hnum, idx FROM 'Providename' WHERE key=?: 11: database
> disk image is malformed
> error: SELECT hnum, idx FROM 'Providename' WHERE key=?: 11: database
> disk image is mal
Greetings ,
I tried to run the command bellow and i was unsuccessful . Well dnf
clean all doesn't work either . Does anyone have any
clue as to what the messages below mean and what might have caused it ??
More importantly how do i rectify this situation ??
dnf info sendmail
error
> Am 17.01.2021 um 01:02 schrieb Samuel Sieb :
>
> On 1/16/21 5:31 AM, Richard Shaw wrote:
>> So as far as I can remember I haven't done anything custom here but...
>> Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
>> cockpit-dashboard < 233 provided by
On 1/16/21 5:31 AM, Richard Shaw wrote:
So as far as I can remember I haven't done anything custom here but...
Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
- cannot install the best update
On 1/16/21 3:12 PM, Peter Boy wrote:
Am 16.01.2021 um 23:07 schrieb Samuel Sieb :
That is strange. This is what I get:
# dnf install cockpit
According your list you don’t have cockpit-dashboard installed, which is the
culprit
Oops, you're right! I missed that. However:
# dnf install
> Am 16.01.2021 um 23:07 schrieb Samuel Sieb :
>
> That is strange. This is what I get:
>
> # dnf install cockpit
> Last metadata expiration check: 3:19:39 ago on Sat 16 Jan 2021 07:45:05 AM
> PST.
&g
for a few days, thinking the mirrors were out of
sync, I
did the same thing to get around the problem :-(
That is strange. This is what I get:
# dnf install cockpit
Last metadata expiration check: 3:19:39 ago on Sat 16 Jan 2021 07:45:05
AM PST.
Dependencies resolved
On Sat, Jan 16, 2021 at 03:49:41PM +0100, Peter Boy wrote:
> >
> > Is it me or a packaging problem?
>
>
> I had the same problem on several servers. I just removed dashboard - not the
> best solution but the quickest.
After hitting the problem for a few days, thinking the mirrors were out of
On 1/16/21 5:31 AM, Richard Shaw wrote:
So as far as I can remember I haven't done anything custom here but...
Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
Looks like this is the missing piece.
> Am 16.01.2021 um 14:31 schrieb Richard Shaw :
>
> So as far as I can remember I haven't done anything custom here but...
>
> Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
> cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
> - cannot install the
So as far as I can remember I haven't done anything custom here but...
Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
- cannot install the best update candidate for package
On Thu, Jan 07, 2021 at 01:06:07PM -0600, David wrote:
> The wiki page that I was referring to ( I think ) was somewhere linked to
> this:
>
> https://fedoraproject.org/wiki/Differences_to_Ubuntu#Package_Management
You can see that page is marked as {old} at the top. We're generally moving
away
Thank you all.
That was very helpful.
Clearly, I have a whole lot more to learn about Fedora, dnf, systemd, mesa,
the kernel, Gnome 40, wayland, xwayland, etc.
The wiki page that I was referring to ( I think ) was somewhere linked to
this:
https://fedoraproject.org/wiki/Differences_to_Ubuntu
On Wed, Jan 06, 2021 at 07:01:06PM -0600, David wrote:
> The Fedora wiki page “dnf vs. apt” needs some tender-loving-care, or TLC.
Do you mean this doc?
https://docs.fedoraproject.org/en-US/quick-docs/dnf-vs-apt/
--
Matthew Miller
Fedora Project Lea
On Wed, Jan 06, 2021 at 07:01:06PM -0600, David wrote:
> I am just curious if the Fedora Wiki on dnf is the best source of info on
> the current state of dnf.
Probably the best place is the upstream DNF docs:
https://dnf.readthedocs.io/en/latest/
--
Matthew Miller
Fedora Project
I am just curious if the Fedora Wiki on dnf is the best source of info on
the current state of dnf.
I see on YouTube all the Debian / Ubuntu-fanboys criticizing dnf.
The other sources of info on the web about dnf seem to be at least prior to
2018.
I do not yet know enough to help update those
On 12/31/20 4:52 AM, Ed Greshko wrote:
On 31/12/2020 20:41, Neal Becker wrote:
I'm not very familiar with restorecon and it's options, what might be
the command?
sudo restorecon -R /var/lib/rpm
Use "-Rv" if you want to see if it makes any changes.
ns just fine.
Could be that the selinux labels are wrong, and cron and the dnf
subprocesses can’t read the files. A ‘restorecon’ on the directory probably
will fix that
—
Jonathan Billings
I'm not very familiar with restorecon and it's options, what might be the
command?
sud
On Wed, Dec 30, 2020 at 7:44 PM Jonathan Billings
wrote:
> On Dec 30, 2020, at 13:49, Neal Becker wrote:
> >
> > Thanks for the suggestion,
> >
> > No, rpm -qa runs just fine.
>
> Could be that the selinux labels are wrong, and cron and the dnf
&g
On Dec 30, 2020, at 13:49, Neal Becker wrote:
>
> Thanks for the suggestion,
>
> No, rpm -qa runs just fine.
Could be that the selinux labels are wrong, and cron and the dnf subprocesses
can’t read the files. A ‘restorecon’ on the directory probably will fix that
—
Jonat
Thanks for the suggestion,
No, rpm -qa runs just fine.
On Wed, Dec 30, 2020 at 11:45 AM Jorge Fábregas
wrote:
> On 12/30/20 12:18 PM, Neal Becker wrote:
> > Dec 30 11:01:29 nbecker8 dnf[1421142]: Error: Error: rpmdb open failed
>
> Do you get errors when you perform: rpm
On 12/30/20 12:18 PM, Neal Becker wrote:
> Dec 30 11:01:29 nbecker8 dnf[1421142]: Error: Error: rpmdb open failed
Do you get errors when you perform: rpm -qa ??? If so, this could be a
corrupted RPM database.
If so try Method #1 listed here:
https://www.cyberciti.biz/tips/rebuilding-corrup
Any idea how to debug this?
Dec 30 11:01:29 nbecker8 systemd[1]: Starting dnf makecache...
Dec 30 11:01:29 nbecker8 dnf[1421142]: error: rpmdb: BDB0113 Thread/process
2496606/140314318812864 failed: BDB1507 Thread died in Berkeley DB library
Dec 30 11:01:29 nbecker8 dnf[1421142]: error: db5 error
< snip >
That is a fallacy. As soon as cpu-x would be installed again, the problem
would return, since nothing has changed, and as long as the incompatible
test update of libcpuid remains available, you cannot update that package
since it would break dependencies. The way forward would be to
On Tue, 29 Dec 2020 19:00:30 +0200, Kostas Sfakiotakis wrote:
> [root@Orion ~]# dnf repoquery --whatrequires libcpuid
>
> Last metadata expiration check: 0:52:55 ago on Tue 29 Dec 2020 06:01:13
> PM EET.
> cpu-x-0:4.0.1-5.fc33.x86_64
> i-nex-0:7.6.1-4.fc33.x86_64
> i-nex-
On Tue, 29 Dec 2020 18:46:05 +0200, Kostas Sfakiotakis wrote:
> root@Orion ~]# dnf repoquery --whatrequires cpu-x
>
> Last metadata expiration check: 0:07:22 ago on Tue 29 Dec 2020 06:01:13
> PM EET.
> cpu-x-data-0:4.0.1-5.fc33.noarch
That query isn't helpful, because it doesn'
The cpu-x package is installed already. You cannot exclude it. Erasing
and reinstalling it would not avoid dependency breakage as long as the
incompatible libcpuid pkg is offered in the repos.
[root@Orion ~]# dnf repoquery --whatrequires libcpuid
Last metadata expiration check: 0:52:55
< snip >
Well that's the problem . I am not able to exclude cpu-x . No matter
how i try to syntax the dnf command , cpu-x doesn't get excluded and
the whole update fails . The only "solution" that comes to mind is
delete the cpu-x package , perf
updates-testing repository offers an
> > incompatible upgrade to libcpuid-0.5.0, which breaks existing
> > dependencies. You may choose to ignore (= exclude) that package,
> > and of course, you will not be able to install anything that strictly
> > requires this newer but incompat
. I am not able to exclude cpu-x . No matter
how i try to syntax the dnf command , cpu-x doesn't get excluded and
the whole update fails . The only "solution" that comes to mind is
delete the cpu-x package , perform the upgrades and then reinstall or
abandon the cpu-x package for
On Mon, 28 Dec 2020 19:57:05 +0200, Kostas Sfakiotakis wrote:
> Error:
> Problem: problem with installed package cpu-x-4.0.1-5.fc33.x86_64
> - cannot install the best update candidate for package
> cpu-x-4.0.1-5.fc33.x86_64
> - package cpu-x-4.0.1-5.fc33.x86_64 requires
With an exclude
[root@f32k ~]# dnf check-update --exclude=firefox
Last metadata expiration check: 2:22:01 ago on Mon 28 Dec 2020
07:08:30 PM CST.
kernel.x86_64 5.9.16-100.fc32 updates
kernel-core.x86_64 5.9.16-100.fc32 updates
kernel-modules.x86_64
ption will not work as well ) ??
> >>
> >> dnf upgrade --best --allowerasing --exclude=cpu-x-4.0.1-5.fc33.x86_64
> >
> > Have you tried just
> >
> > dnf upgrade --best --allowerasing --exclude=cpu-x
>
> Yes it will not work either . Also
>
>
On 28/12/2020 20:07, Kostas Sfakiotakis wrote:
Στις 28/12/20 2:36 π.μ., ο/η Ed Greshko έγραψε:
On 28/12/2020 08:05, Kostas Sfakiotakis wrote:
Can someone please tell me the correct syntax of the exclude option ( the -x
option will not work as well ) ??
dnf upgrade --best --allowerasing
Στις 28/12/20 2:36 π.μ., ο/η Ed Greshko έγραψε:
On 28/12/2020 08:05, Kostas Sfakiotakis wrote:
Can someone please tell me the correct syntax of the exclude option (
the -x option will not work as well ) ??
dnf upgrade --best --allowerasing --exclude=cpu-x-4.0.1-5.fc33.x86_64
Have you
On 28/12/2020 08:05, Kostas Sfakiotakis wrote:
Can someone please tell me the correct syntax of the exclude option ( the -x
option will not work as well ) ??
dnf upgrade --best --allowerasing --exclude=cpu-x-4.0.1-5.fc33.x86_64
Have you tried just
dnf upgrade --best --allowerasing
Can someone please tell me the correct syntax of the exclude option (
the -x option will not work as well ) ??
dnf upgrade --best --allowerasing --exclude=cpu-x-4.0.1-5.fc33.x86_64
___
users mailing list -- users@lists.fedoraproject.org
for all updates you'll need to put the
> "exclude" statement in
> /etc/dnf/dnf.conf
>
> man dnf.conf
>
You are not doing to believe this but after excluding the packages, the
update does not give any errors upfront.
There still are problems like the display server c
On 16/12/2020 17:22, Sreyan Chakravarty wrote:
Will it be excluded just for this update or will it be excluded for
all future updates as well.
Just the one update.
If you want to exclude the packages for all updates you'll need to put the
"exclude" statement in
/etc/dnf/dnf
ilto:ed.gres...@greshko.com>> wrote:
> >>>>>>
> >>>>>>
> >>>>>> In the bugzilla you wrote:
> >>>>>>
> >>>>>> How reproducible:
> >>>>>> Always when I update.
> >&
:
On Tue, 15 Dec 2020, 1:12 pm Ed Greshko, mailto:ed.gres...@greshko.com>> wrote:
In the bugzilla you wrote:
How reproducible:
Always when I update.
Steps to Reproduce:
1. Open terminal.
2. sudo dnf update -y
3. Reboot.
How many times have you att
y wrote:
> > >>>
> > >>>
> > >>> On Tue, 15 Dec 2020, 1:12 pm Ed Greshko, > >>> <mailto:ed.gres...@greshko.com>> wrote:
> > >>>
> > >>>
> > >>> In the bugzilla you wrote:
> > >&
m Ed Greshko, >>> <mailto:ed.gres...@greshko.com>> wrote:
> >>>
> >>>
> >>> In the bugzilla you wrote:
> >>>
> >>> How reproducible:
> >>> Always when I update.
> >>>
> >>
update.
Steps to Reproduce:
1. Open terminal.
2. sudo dnf update -y
3. Reboot.
How many times have you attempted the update?
I ask since I've looked over the list of packages updated and it seems I
have all of those which are
related to plasma and have no tr
1. Open terminal.
2. sudo dnf update -y
3. Reboot.
How many times have you attempted the update?
I ask since I've looked over the list of packages updated and it
seems I have all of those which are
related to plasma and have no troubles. With multiple systems
having bee
> > How reproducible:
> > Always when I update.
> >
> > Steps to Reproduce:
> > 1. Open terminal.
> > 2. sudo dnf update -y
> > 3. Reboot.
> >
> > How many times have you attempted the update?
> >
> >
On 15/12/2020 16:24, Sreyan Chakravarty wrote:
On Tue, 15 Dec 2020, 1:12 pm Ed Greshko, mailto:ed.gres...@greshko.com>> wrote:
In the bugzilla you wrote:
How reproducible:
Always when I update.
Steps to Reproduce:
1. Open terminal.
2. sudo dnf update -y
401 - 500 of 2266 matches
Mail list logo
