Packages stuck on 2021-09-01 16:40:54 +0000 UTC
towhee /var/www/packages.gentoo.org # docker logs -n 5 -t packagesgentooorg_updater_1 2021-09-01T17:20:40.597124973Z INFO: 2021/09/01 17:20:40 update.go:60: Start updating changed metadata 2021-09-01T17:20:40.699863079Z INFO: 2021/09/01 17:20:40 update.go:80: Start updating changed package data 2021-09-01T17:20:40.795672406Z INFO: 2021/09/01 17:20:40 update.go:98: Start updating the history 2021-09-01T17:20:40.795707467Z INFO: 2021/09/01 17:20:40 commit.go:22: Start updating commits 2021-09-01T17:20:40.888845342Z INFO: 2021/09/01 17:20:40 commit.go:29: Finished updating commits The updater has not run since Sept 1.
App-emulation/docker on p.g.o needs a rebuild.
Package list is updating ok now, maintainer data should be updating soon
I think this can be closed?
still not fixed. Updated packages showing 2019 as latest at the moment
At least the changelog still shows some completely outdated commits as latest. For example: https://packages.gentoo.org/packages/app-office/calligra/changelog Commits on Apr 05, 2018 app-office/calligra: Drop 3.0.1 ed29e62 Andreas Sturmlechner committed on 5 Apr 2018 23:24:57
Works for me... It would seem several of us cannot reproduce your issue. Visiting https://packages.gentoo.org/packages/app-office/calligra/changelog displays: Commits on Jan 07, 2022 app-office/calligra: Fix build with >=poppler-22.01 767eab5 Andreas Sturmlechner committed on 7 Jan 2022 13:46:36 Please ensure the network you are using is not using a poorly configured HTTP caching proxy such as squid. If you have not done so already, please clear all browser cookies and cache from your web browser of choice and try to reload packages.g.o. Pressing F5 on most browsers issues a harder refresh/reload than simply clicking the reload button. If the public by-in-large cannot reproduce the issue, then it would be an isolated case beyond the support of our Infra team. Thank you!
(In reply to Matthew Marchese from comment #7) > Works for me... It would seem several of us cannot reproduce your issue. > > Visiting https://packages.gentoo.org/packages/app-office/calligra/changelog > displays: > > Commits on Jan 07, 2022 > app-office/calligra: Fix build with >=poppler-22.01 > 767eab5 > Andreas Sturmlechner committed on 7 Jan 2022 13:46:36 > > Please ensure the network you are using is not using a poorly configured > HTTP caching proxy such as squid. If you have not done so already, please > clear all browser cookies and cache from your web browser of choice and try > to reload packages.g.o. Pressing F5 on most browsers issues a harder > refresh/reload than simply clicking the reload button. > > If the public by-in-large cannot reproduce the issue, then it would be an > isolated case beyond the support of our Infra team. > > Thank you! This is our bad, we deployed a new version of p.g.o on Monday, so it should have been fixed then. -A
(In reply to Alec Warner from comment #8) > This is our bad, we deployed a new version of p.g.o on Monday, so it should > have been fixed then. > > -A Yeah, I'm not so sure this is actually fixed? For example, https://packages.gentoo.org/packages/updated is not showing anything more recent than net-misc/frr, dated 2022-02-02 09:35:19 +0000 UTC. So, none of the 25+ updates I've done today (including llvm/clang and friends) are visible on p.g.o as updates. Obviously, I have checked by bypassing any browser cache (and there is no local proxy-serve cache). What are other people seeing?
(In reply to Adrian Bassett from comment #9) > (In reply to Alec Warner from comment #8) > > > This is our bad, we deployed a new version of p.g.o on Monday, so it should > > have been fixed then. > > > > -A > > Yeah, I'm not so sure this is actually fixed? > > For example, https://packages.gentoo.org/packages/updated is not showing > anything more recent than net-misc/frr, dated 2022-02-02 09:35:19 +0000 UTC. > > So, none of the 25+ updates I've done today (including llvm/clang and > friends) are visible on p.g.o as updates. > > Obviously, I have checked by bypassing any browser cache (and there is no > local proxy-serve cache). > > What are other people seeing? This bug is not for "p.g.o is not working." It was broken in september. We fixed it (docker was broken.) Is there something else wrong with it? Maybe; but I want a new bug for it. -A
(In reply to Alec Warner from comment #10) > (In reply to Adrian Bassett from comment #9) > > (In reply to Alec Warner from comment #8) > > > > > This is our bad, we deployed a new version of p.g.o on Monday, so it should > > > have been fixed then. > > > > > > -A > > > > Yeah, I'm not so sure this is actually fixed? > > > > For example, https://packages.gentoo.org/packages/updated is not showing > > anything more recent than net-misc/frr, dated 2022-02-02 09:35:19 +0000 UTC. > > > > So, none of the 25+ updates I've done today (including llvm/clang and > > friends) are visible on p.g.o as updates. > > > > Obviously, I have checked by bypassing any browser cache (and there is no > > local proxy-serve cache). > > > > What are other people seeing? > > This bug is not for "p.g.o is not working." > > It was broken in september. We fixed it (docker was broken.) > > Is there something else wrong with it? Maybe; but I want a new bug for it. > > -A Currently https://packages.gentoo.org/packages/updated appears to be keeping track with https://gitweb.gentoo.org/repo/gentoo.git/log so, no, there doesn't appear to be anything wrong with p.g.o atm, at least in the sense in which my comments related to the title/subject of this bug. When I wrote my comment yesterday the former site was some 32 hours behind the latter. Perhaps something got re-started, I dunno.
