3:41 p.m.
I thought I disabled dnfdragona from doing its 3? hour check for
anything new. But whenever I do a "dnf update" I see it starting with a
message like:
Last metadata expiration check: 1:46:14 ago on Wed 10 May 2023 02:52:06
PM EDT.
How do I stop this?
thanks
3:47 p.m.
On 05/10/2023 02:41 PM, Robert Moskowitz wrote:
I thought I disabled dnfdragona from doing its 3? hour check for
anything new. But whenever I do a "dnf update" I see it starting with a
message like:
Last metadata expiration check: 1:46:14 ago on Wed 10 May 2023 02:52:06
PM EDT.
How do I stop this?
sudo dnf remove dnfdragona should do the trick.
4 p.m.
On Wed, May 10, 2023 at 04:41:29PM -0400, Robert Moskowitz wrote:
I thought I disabled dnfdragona from doing its 3? hour check for
anything
new. But whenever I do a "dnf update" I see it starting with a message
like:
Last metadata expiration check: 1:46:14 ago on Wed 10 May 2023 02:52:06 PM
EDT.
How do I stop this?
Might be the dnf timer?
systemctl status dnf-makecache.timer
and disable with:
systemctl disable dnf-makecache.timer
kevin
10:12 p.m.
On 5/10/23 17:00, Kevin Fenzi wrote:
On Wed, May 10, 2023 at 04:41:29PM -0400, Robert Moskowitz wrote:
> I thought I disabled dnfdragona from doing its 3? hour check for anything
> new. But whenever I do a "dnf update" I see it starting with a message
> like:
>
> Last metadata expiration check: 1:46:14 ago on Wed 10 May 2023 02:52:06 PM
> EDT.
>
> How do I stop this?
Might be the dnf timer?
systemctl status dnf-makecache.timer
● dnf-makecache.timer - dnf makecache --timer
Loaded: loaded (/usr/lib/systemd/system/dnf-makecache.timer;
enabled; pres>
Active: active (waiting) since Thu 2023-05-04 08:35:42 EDT; 6 days ago
Trigger: Wed 2023-05-10 23:31:31 EDT; 20min left
Triggers: ● dnf-makecache.service
yep that is it.
and disable with:
systemctl disable dnf-makecache.timer
Removed "/etc/systemd/system/timers.target.wants/dnf-makecache.timer".
thanks!
kevin
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
4:43 a.m.
On Wed, 2023-05-10 at 16:41 -0400, Robert Moskowitz wrote:
I thought I disabled dnfdragona from doing its 3? hour check for
anything new. But whenever I do a "dnf update" I see it starting with a
message like:
If you don't use dnf-dragora you don't need it installed. I always
disabled it, then finally decided to remove it the other day.
I didn't want its interrupting notices, and never used to it to install
anything. I always did a "dnf update" on the command line at a time of
my own choosing.
--
uname -rsvp
Linux 3.10.0-1160.88.1.el7.x86_64 #1 SMP Tue Mar 7 15:41:52 UTC 2023 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
4:56 a.m.
On Thu, 2023-05-11 at 19:13 +0930, Tim via users wrote:
On Wed, 2023-05-10 at 16:41 -0400, Robert Moskowitz wrote:
> I thought I disabled dnfdragona from doing its 3? hour check for
> anything new. But whenever I do a "dnf update" I see it starting
> with a
> message like:
If you don't use dnf-dragora you don't need it installed. I always
disabled it, then finally decided to remove it the other day.
I didn't want its interrupting notices, and never used to it to
install
anything. I always did a "dnf update" on the command line at a time
of my own choosing.
Same here.
poc
12:08 p.m.
On 5/11/23 05:56, Patrick O'Callaghan wrote:
On Thu, 2023-05-11 at 19:13 +0930, Tim via users wrote:
> On Wed, 2023-05-10 at 16:41 -0400, Robert Moskowitz wrote:
>> I thought I disabled dnfdragona from doing its 3? hour check for
>> anything new. But whenever I do a "dnf update" I see it starting
>> with a
>> message like:
> If you don't use dnf-dragora you don't need it installed. I always
> disabled it, then finally decided to remove it the other day.
>
> I didn't want its interrupting notices, and never used to it to
> install
> anything. I always did a "dnf update" on the command line at a time
> of my own choosing.
Same here.
Looks like I am going to have to just uninstall dhf-dragora.
Even after
systemctl disable dnf-makecache.timer
Still got
dnf update
Last metadata expiration check: 0:18:17 ago on Fri 12 May 2023 12:45:30
PM EDT.
ARGH!!! wasting cycles and bandwidth for what?
12:20 p.m.
On 5/12/23 10:08, Robert Moskowitz wrote:
On 5/11/23 05:56, Patrick O'Callaghan wrote:
> On Thu, 2023-05-11 at 19:13 +0930, Tim via users wrote:
>> On Wed, 2023-05-10 at 16:41 -0400, Robert Moskowitz wrote:
>>> I thought I disabled dnfdragona from doing its 3? hour check for
>>> anything new. But whenever I do a "dnf update" I see it starting
>>> with a
>>> message like:
>> If you don't use dnf-dragora you don't need it installed. I always
>> disabled it, then finally decided to remove it the other day.
>>
>> I didn't want its interrupting notices, and never used to it to
>> install
>> anything. I always did a "dnf update" on the command line at a time
>> of my own choosing.
> Same here.
Looks like I am going to have to just uninstall dhf-dragora.
Even after
systemctl disable dnf-makecache.timer
Still got
dnf update
Last metadata expiration check: 0:18:17 ago on Fri 12 May 2023 12:45:30
PM EDT.
Look in the logs to see what's triggering that.
4:08 p.m.
On 5/12/23 13:20, Samuel Sieb wrote:
On 5/12/23 10:08, Robert Moskowitz wrote:
>
>
> On 5/11/23 05:56, Patrick O'Callaghan wrote:
>> On Thu, 2023-05-11 at 19:13 +0930, Tim via users wrote:
>>> On Wed, 2023-05-10 at 16:41 -0400, Robert Moskowitz wrote:
>>>> I thought I disabled dnfdragona from doing its 3? hour check for
>>>> anything new. But whenever I do a "dnf update" I see it
starting
>>>> with a
>>>> message like:
>>> If you don't use dnf-dragora you don't need it installed. I always
>>> disabled it, then finally decided to remove it the other day.
>>>
>>> I didn't want its interrupting notices, and never used to it to
>>> install
>>> anything. I always did a "dnf update" on the command line at a
time
>>> of my own choosing.
>> Same here.
>
> Looks like I am going to have to just uninstall dhf-dragora.
>
> Even after
>
> systemctl disable dnf-makecache.timer
>
> Still got
>
> dnf update
> Last metadata expiration check: 0:18:17 ago on Fri 12 May 2023
> 12:45:30 PM EDT.
Look in the logs to see what's triggering that.
unless I am looking in the wrong log, I am not seeing what is the trigger:
# tail dnf.log -n20
2023-05-12T16:25:47-0400 DEBUG reviving: 'updates' can be revived -
metalink checksums match.
2023-05-12T16:25:49-0400 DEBUG updates: using metadata from Fri 12 May
2023 12:04:00 AM EDT.
2023-05-12T16:25:49-0400 DEBUG countme: no event for updates-modular:
window already counted
2023-05-12T16:25:49-0400 DEBUG reviving: 'updates-modular' can be
revived - metalink checksums match.
2023-05-12T16:25:49-0400 DEBUG updates-modular: using metadata from Tue
20 Feb 2018 02:18:14 PM EST.
2023-05-12T16:25:49-0400 DEBUG reviving: 'rpmfusion-free' can be revived
- metalink checksums match.
2023-05-12T16:25:49-0400 DEBUG rpmfusion-free: using metadata from Fri
14 Apr 2023 07:37:11 AM EDT.
2023-05-12T16:25:50-0400 DEBUG reviving: failed for
'rpmfusion-free-updates', mismatched sha256 sum.
2023-05-12T16:25:50-0400 DEBUG repo: downloading from remote:
rpmfusion-free-updates
2023-05-12T16:25:52-0400 DEBUG rpmfusion-free-updates: using metadata
from Fri 12 May 2023 02:06:31 PM EDT.
2023-05-12T16:25:52-0400 DEBUG reviving: 'rpmfusion-nonfree' can be
revived - metalink checksums match.
2023-05-12T16:25:52-0400 DEBUG rpmfusion-nonfree: using metadata from
Fri 14 Apr 2023 08:02:51 AM EDT.
2023-05-12T16:25:52-0400 DEBUG reviving: 'rpmfusion-nonfree-updates' can
be revived - metalink checksums match.
2023-05-12T16:25:52-0400 DEBUG rpmfusion-nonfree-updates: using metadata
from Sun 07 May 2023 06:10:36 PM EDT.
2023-05-12T16:25:52-0400 DEBUG User-Agent: constructed: 'libdnf (Fedora
Linux 38; generic; Linux.x86_64)'
2023-05-12T16:25:53-0400 DDEBUG timer: sack setup: 10695 ms
2023-05-12T16:25:53-0400 DEBUG Completion plugin: Generating completion
cache...
2023-05-12T16:25:56-0400 INFO Metadata cache created.
2023-05-12T16:25:56-0400 DDEBUG Cleaning up.
2023-05-12T16:25:56-0400 DDEBUG Plugins were unloaded.
4:12 p.m.
On 5/12/23 14:08, Robert Moskowitz wrote:
On 5/12/23 13:20, Samuel Sieb wrote:
> On 5/12/23 10:08, Robert Moskowitz wrote:
>>
>>
>> On 5/11/23 05:56, Patrick O'Callaghan wrote:
>>> On Thu, 2023-05-11 at 19:13 +0930, Tim via users wrote:
>>>> On Wed, 2023-05-10 at 16:41 -0400, Robert Moskowitz wrote:
>>>>> I thought I disabled dnfdragona from doing its 3? hour check for
>>>>> anything new. But whenever I do a "dnf update" I see it
starting
>>>>> with a
>>>>> message like:
>>>> If you don't use dnf-dragora you don't need it installed. I
always
>>>> disabled it, then finally decided to remove it the other day.
>>>>
>>>> I didn't want its interrupting notices, and never used to it to
>>>> install
>>>> anything. I always did a "dnf update" on the command line at a
time
>>>> of my own choosing.
>>> Same here.
>>
>> Looks like I am going to have to just uninstall dhf-dragora.
>>
>> Even after
>>
>> systemctl disable dnf-makecache.timer
>>
>> Still got
>>
>> dnf update
>> Last metadata expiration check: 0:18:17 ago on Fri 12 May 2023
>> 12:45:30 PM EDT.
>
> Look in the logs to see what's triggering that.
unless I am looking in the wrong log, I am not seeing what is the trigger:
# tail dnf.log -n20
That's the wrong log. The dnf log won't tell you what started dnf. You
need to look in the journal.
7:36 p.m.
On Fri, 2023-05-12 at 13:08 -0400, Robert Moskowitz wrote:
Looks like I am going to have to just uninstall dhf-dragora.
Even after
systemctl disable dnf-makecache.timer
Still got
dnf update
Last metadata expiration check: 0:18:17 ago on Fri 12 May 2023 12:45:30
PM EDT.
ARGH!!! wasting cycles and bandwidth for what?
So your command line tool responds quicker? Mostly it'll parse the
prefetched data, rather than have to get all the metadata when you run
it. Unless, I'm guessing, it decides that too much time has passed
since it downloaded metadata and when you ran the dnf tool.
I removed dnf-dragora, and dnf-makecache.timer still exists. They're
different things.
dnf-dragora is that task bar thing that pops up telling you there's
packages available to update, and you can fire off the updates from it,
and a GUI tool for installing packages. I removed it, I don't use them
at all.
dnf-makecache.timer simply keeps the dnf metadata refreshed (which
probably isn't essential). It's a part of the main dnf RPM, so I don't
think you can get rid of it. Try masking it if you want.
--
NB: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
The following system info data is generated fresh for each post:
uname -rsvp
Linux 6.2.14-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Mon May 1 00:54:35
UTC 2023 x86_64
7:10 a.m.
On 5/11/23 05:43, Tim via users wrote:
On Wed, 2023-05-10 at 16:41 -0400, Robert Moskowitz wrote:
> I thought I disabled dnfdragona from doing its 3? hour check for
> anything new. But whenever I do a "dnf update" I see it starting with a
> message like:
If you don't use dnf-dragora you don't need it installed. I always
disabled it, then finally decided to remove it the other day.
I didn't want its interrupting notices, and never used to it to install
anything. I always did a "dnf update" on the command line at a time of
my own choosing.
Good points. It seems to come with the base install.
Joe Zeff also said to uninstall. Just might do that and add it in to my
general setup steps.
385
days inactive
388
days old
11 comments
6 participants
participants (6)
-
Joe Zeff -
Kevin Fenzi -
Patrick O'Callaghan -
Robert Moskowitz -
Samuel Sieb -
Tim