I usually set and recommend a country mirrors pool to avoid this.
Nevertheless, on help threads on the French forum, I often see users who set a specific mirror, trying to optimize speed.
When checking https://launchpad.net/ubuntu/+archivemirrors I observe that "up to date" is not the majority and that some lag up to one week
Why is this? Isn't the mirroring process automated?
When checking two twin installs, same sources, same server, same location, sometimes updates are not the same or don't happen at the same time.
My understanding of this is that its linked to phased updates.
In history.log, I can see that type of line :
Commandline: aptdaemon role='role-commit-packages' sender=':1.72'
From one install to the other, the sender will be different (i.e sender='1.77')
My assumption there is that this sender ID difference is a marker for phased updates.
Am I correct or does it have a totally different meaning?
Some PPAs like the defunct getdeb or nilarimogard (or even proposed) may bring a lot of specific versions when one recklessly runs an update/upgrade with those activated.
Thus, removing the PPA or the repository might not be sufficient to get rid of these experimental versions.
Once I only activate official repositories, how can I CLI get a list of packages which version is higher than the official repositories one ?
On software updates, we can choose country pools or specific servers, when checking servers on https://launchpad.net/ubuntu/+archivemirrors we can see that some are up-to-date, while others are lagging. If we choose a country, will update address only the up-to-date (or less lagging) mirrors ?
gksudo seeming to be somehow depreciated since 2017 as I see on the french forum documentation, is there an environment and version agnostic best practice allowing to use gedit as root?
(excluding vim, nano or tee: the use case being a GUI amendment of sources.list for instance)
My researchs brought me these proposals, are they equivalent or to be rejected :
pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY gedit
gedit admin:///path/to/document
sudo -i gedit
sudo -H gedit
Any other ?
I observe that removing a ppa with Software & Updates or with :
sudo add-apt-repository --remove ppa:xxx/yyy
merely empties the file one wants to remove and leaves an empty theuglyppa.list file in /etc/apt/sources.list.d/
(same with ppa-purge) Why is this ? This seem quite illogical to keep such residue especially for newbies who won't know that they should add :
sudo rm /etc/apt/sources.list.d/theuglyppa.list*
to their cleaning procedure. Where should this odd behaviour be reported as a bug ? As I consider this as a bug, unless somebody tells me what brilliant logic justifies such leftovers.