[SERVER-69746] debmirror not working Created: 15/Sep/22 Updated: 27/Oct/23 Resolved: 23/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Anurag Harsh | Assignee: | Dylan Richardson |
| Resolution: | Community Answered | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Story Points: | 3 | ||||||||
| Description |
|
We are trying to set up a debmirror.
Error |
| Comments |
| Comment by Dylan Richardson [ 21/Sep/22 ] | |
|
Hi Anurag, After looking into this, it turns out that the Codenames in our Release file do appear to be incorrect as expected by that tool. We will likely fix this eventually, but I am not sure on timeline. Just to be clear, we do not officially support debmirror, so I can't guarantee using debmirror will work (or if its output will stay consistent) once that is changed. There is a workaround that I think will function for now that I came upon - here's a sample call to debmirror that I think will work:
Note the changed section and dist parameters. This tricks debmirror into working more correctly with our Release files, even if it's a bit wrong. That being said, I cannot test this for compatibility myself because it seems that debmirror has made a change which is incompatible with our repositories for other reasons. You may have to tweak other things and/or patch the debmirror script yourself to get the outcome you're looking for. | |
| Comment by Dylan Richardson [ 20/Sep/22 ] | |
|
Hi Anurag, I have just started looking at this - I'll let you know when I have an update. | |
| Comment by Anurag Harsh [ 20/Sep/22 ] | |
|
Hi, | |
| Comment by Chris Kelly [ 16/Sep/22 ] | |
|
Hi Anurag, I found a similar ticket Christopher |