Best workflow when Arch mirrorlist is updated?

General system Pacman & AUR helpers
1

I wonder what the suggested “best” workflow is when a new Arch mirrorlist arrives with an update, i.e., pacdiff shows a fresh mirrorlist with more/updated entries?

Should we

  1. (o)verwrite from the pacnew file, then run simple-reflector?
  2. (r)emove the pacnew file, then run simple-reflector?
  3. only run simple-reflector?
  4. do nothing?

Background: I’m a little unsure how this is handled internally—does reflector pull from the local mirrorlist or does it pull a fresh copy online?

For today’s update, I let it (o)verwrite from the pacnew file (destroying my old reflector list), then immediately ran simple-reflector again. The list now looks good to me, but I’d surely like to know the suggested “best” way, and why…

Thanks for any enlightenment!

1 Like
2

Fresh copy from online.

Not best workflow, but what I use.
I have added NoExtract = etc/pacman.d/mirrorlist to pacman.conf so that the new mirror list is not copied to disk from cache.
I use sometime milcheck to check that my mirror(s) are ok. Mostly osbeck server.

3 Likes
3

Ah, good, thanks So I could actually do 1, 2, or 3 above without any negative side effects.

1 Like
4

I do 1 from your list above, but, as you say, it looks like any of 1-3 is OK.

2 Likes
5

Thanks for the help! Would have picked you both for a solution, but we can only have one, so it’ll be @EOS :wink:

1 Like
6

That’s fine, I didn’t know that it fetched a fresh mirror list.

One other advantage of 1 or 2 is that then you don’t have a stray .pacnew file lurking in your system to confuse at a later date.

1 Like
7

I have a script which run milcheck and ask if I want to update the mirrorlist (with reflector), before upgrade.

1 Like
8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.