You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Update status page has a lot of useful information about recent updates of various repositories.
However, I recently noticed the lack of updates on Repology for my packages in Hackage, so I started poking around to figure out what’s going on. E.g., for one of my packages, Yaya (on Repology), nixpkgs-unstable (which fetches from Hackage) is showing 0.6.2.0, while Hackage itself is showing 0.4.2.1.
I see on the Update status page that recent Hackage fetches have failed. Looking at the failures and poking around a bit, it seems like the last successful parse of Hackage may have been about two years ago. But, I can’t find that information on Repology.
Knowing exactly when/what was last parsed successfully would help me diagnose and fix the failure.
Relatedly, having the update information on the repository page (e.g., for Hackage) would also be helpful.
The text was updated successfully, but these errors were encountered:
sellout
changed the title
show latest _successful_ update on “Update status” page
show latest successful update on “Update status” page
Apr 23, 2024
The Update status page has a lot of useful information about recent updates of various repositories.
However, I recently noticed the lack of updates on Repology for my packages in Hackage, so I started poking around to figure out what’s going on. E.g., for one of my packages, Yaya (on Repology), nixpkgs-unstable (which fetches from Hackage) is showing 0.6.2.0, while Hackage itself is showing 0.4.2.1.
I see on the Update status page that recent Hackage fetches have failed. Looking at the failures and poking around a bit, it seems like the last successful parse of Hackage may have been about two years ago. But, I can’t find that information on Repology.
Knowing exactly when/what was last parsed successfully would help me diagnose and fix the failure.
Relatedly, having the update information on the repository page (e.g., for Hackage) would also be helpful.
The text was updated successfully, but these errors were encountered: