On Thu, Feb 3, 2022 at 1:15 PM Petr Pisar <ppi...@redhat.com> wrote:

> V Thu, Feb 03, 2022 at 12:13:11PM +0000, Ian McInerney via devel napsal(a):
> > I am trying to install a bodhi update that was pushed to testing last
> night
> > (https://bodhi.fedoraproject.org/updates/FEDORA-2022-20f36a8b0e), and I
> am
> > using the DNF line it gives me but seeing this string instead:
> >
> > $ sudo dnf upgrade --enablerepo=updates-testing
> > --advisory=FEDORA-2022-20f36a8b0e
> > Last metadata expiration check: 0:01:49 ago on Thu 03 Feb 2022 12:07:31
> GMT.
> > No security updates needed, but 642 updates available
> > Dependencies resolved.
> > Nothing to do.
> > Complete!
> >
> > In previous times I installed from updates-testing it has worked and
> never
> > said there were no security updates available. Why is DNF refusing to
> > install it this time?
> >
> It works for me. Isn't your mirror stalled? Check Repo-updated time stamp
> in:
>
> # dnf repolist --repo=updates-testing -v
> Loaded plugins: builddep, changelog, config-manager, copr, debug,
> debuginfo-install, download, generate_completion_cache, groups-manager,
> needs-restarting, playground, repoclosure, repodiff, repograph, repomanage,
> reposync
> DNF version: 4.9.0
> cachedir: /var/cache/dnf
> Last metadata expiration check: 0:02:06 ago on Thu 03 Feb 2022 02:11:08 PM
> CET.
> Repo-id            : updates-testing
> Repo-name          : Fedora 35 - x86_64 - Test Updates
> Repo-revision      : 1643848757
> Repo-updated       : Thu 03 Feb 2022 02:13:00 AM CET
> Repo-pkgs          : 12,484
> Repo-available-pkgs: 12,484
> Repo-size          : 19 G
> Repo-metalink      :
> https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f35&arch=x86_64
>   Updated          : Thu 03 Feb 2022 02:11:08 PM CET
> Repo-baseurl       : rsync://
> ftp.fi.muni.cz/pub/linux/fedora/linux/updates/testing/35/Everything/x86_64/
> (54 more)
> Repo-expire        : 21,600 second(s) (last: Thu 03 Feb 2022 02:11:08 PM
> CET)
> Repo-filename      : /etc/yum.repos.d/fedora-updates-testing.repo
> Total packages: 12,484
>
> -- Petr
>

I guess it was a mirror caching issue. I tried again just now and it picked
up the update just fine. I didn't think the updates-testing repo was
mirrored though, but it is very annoying that the mirror sync and the push
to updates-testing apparently aren't synchronized, leading to a large lag
there.

-Ian
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to