-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing version doesn't sync with archive after migration #181
Comments
Hey, thanks for your report. You’re right that something seems off here, but your suspicion is not correct: debiman does not know about uploads or migrations, it always goes through the list of packages currently in the Debian archive. However, I think there is a bug in cache invalidation that I have now tracked down based on this timeline: This is what the Debian package tracker lists:
This is what the debiman logfiles say, annotated for clarity with the resulting state on disk:
This is the state on disk:
So the problem consists of multiple parts:
So, what can we do to fix the issue?
I’m not sure yet which path I like most. Maybe option 2 deserves a shot, and if it turns out to be too hard for some reason, we can resort to option 3. I can kick off a run with a forced full re-rendering to get the current manpage archive fixed (will take a few days to complete and propagate, though). |
Looks like this was a bit quicker than expected: the corrected version now seems to be live. |
Thanks for the detailed analysis. Some rough thoughts:
|
After dh-shell-completions 0.0.3 migrated to testing for a while (migrated on 22 Sep, problem found on 18 Oct), manpages.debian.org still has its testing version at 0.0.2. Now that 0.0.4 was uploaded and manpages.d.o version are now in sync (testing 0.0.3, unstable 0.0.4), I suspect that only uploads trigger updates, not migrations.
The text was updated successfully, but these errors were encountered: