Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: New primary mirror (Read 5203 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: New primary mirror

Reply #60
We provide quality packages with nothing to hide! Joking aside, package mirrors don't really need https, the content is public.

I disagree.
Package injection via MITM is not that difficult.
With https, it is.


Re: New primary mirror

Reply #62
So for completeness sake, a simplified how-to reset your pacman's keys:

1a. Reinstall keyrings including the latest keys:

sudo pacman -Sy gnupg archlinux-keyring artix-keyring --force

1b. If step 1a doesn't work, do only step 2 and go back to step 1a. Otherwise proceed to step 2.

2. Remove old (and possibly broken) keys by entering this command:

sudo rm -r /etc/pacman.d/gnupg

3. Initialize the pacman keyring:

sudo pacman-key --init

4. Load the signature keys:

sudo pacman-key --populate archlinux artix

5. Clear out the software packages downloaded during the aborted installation (optional):

sudo pacman -Sc

6. Carry on.

sudo pacman -Syyuu


This is failing and I don't know why

Code: [Select]
[flatbush ~]# pacman -Sy gnupg archlinux-keyring artix-keyring --force
:: Synchronizing package databases...
 system is up to date
 world is up to date
 galaxy is up to date
 extra is up to date
 community is up to date
 multilib is up to date
warning: gnupg-2.2.6-1 is up to date -- reinstalling
warning: archlinux-keyring-20180404-1 is up to date -- reinstalling
warning: artix-keyring-20171114-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (3) archlinux-keyring-20180404-1  artix-keyring-20171114-1  gnupg-2.2.6-1

Total Download Size:    2.74 MiB
Total Installed Size:  10.37 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n]
:: Retrieving packages...
 gnupg-2.2.6-1-x86_64                 2.1 MiB   103M/s 00:00 [################################] 100%
 archlinux-keyring-20180404-1-any   668.2 KiB  0.00B/s 00:00 [################################] 100%
 artix-keyring-20171114-1-any        38.8 KiB  0.00B/s 00:00 [################################] 100%
(3/3) checking keys in keyring                               [################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: key "1247D995F165BBAC" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

Re: New primary mirror

Reply #63
You should run these three commands

Code: [Select]
 sudo pacman -S artix-keyring
 sudo pacman-key --populate artix
 sudo pacman-key --lsign-key 78C9C713EAD7BEC69087447332E21894258C6105


Re: New primary mirror

Reply #65
You should run these three commands

Code: [Select]
 sudo pacman -S artix-keyring
 sudo pacman-key --populate artix
 sudo pacman-key --lsign-key 78C9C713EAD7BEC69087447332E21894258C6105


Yes - I  tried that before I posted

Code: [Select]
[flatbush ~]# pacman -S artix-keyring
warning: artix-keyring-20171114-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) artix-keyring-20171114-1

Total Download Size:   0.04 MiB
Total Installed Size:  0.08 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
 artix-keyring-20171114-1-any        38.8 KiB  0.00B/s 00:00 [################################] 100%
(1/1) checking keys in keyring                               [################################] 100%
(1/1) checking package integrity                             [################################] 100%
error: artix-keyring: signature from "Artix Buildbot <buildbot@artixlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/artix-keyring-20171114-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] Y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.


Re: New primary mirror

Reply #66
Code: [Select]
error: alsa-tools: signature from "Anatol Pomozov <anatol.pomozov@gmail.com>" is unknown trust
:: File /var/cache/pacman/pkg/alsa-tools-1.1.6-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]

I am lost as to the problem here.

Re: New primary mirror

Reply #67
Due to our primary mirror gone offline for a while, there are problems with the seconday mirrors. Please use our primary mirror (http://mirror1.artixlinux.org) until the secondary ones start syncing again.


It is my mirror though, I think I synced it by hand

Code: [Select]
it is not working anyway
[flatbush ~]# pacman -S artix-keyring
warning: artix-keyring-20171114-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) artix-keyring-20171114-1

Total Installed Size:  0.08 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                               [################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: key "1247D995F165BBAC" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (could not find or read file)
Errors occurred, no packages were upgraded.


Re: New primary mirror

Reply #68
Hi, I've just updated the mirrorlist from 20180417-1 to 20180421-1. Unfortunately, the content of the /etc/pacman.d/mirrorlist.pacnew file starts with the following header again:
Code: [Select]
##
## Artix Linux repository mirrorlist
## Generated on 2017-10-21
##
Is there a reason not to update the Generated on date? Should not the developers care about the date, why bother presenting it at all? It's only misleading. Thanks in advance for feedback.

Re: New primary mirror

Reply #69
Just edit it and put your own date on it, but that is the list of the latest 7 mirrors.  If you remember the past couple of weeks the primary mirror was lost, so there was an update with 1 mirror less, then a new server was found and it was added again, and during the process 2 more mirrors were found, that's all.

Here you can replace it with this one:

Code: [Select]
##
## Artix Linux repository mirrorlist
## Generated on 2018-04-23
##

# Artix mirrors

Server = https://mirror.clarkson.edu/artix-linux/repos/$repo/os/$arch
Server = https://ftp.sh.cvut.cz/artix-linux/$repo/os/$arch
Server = http://artix.wheaton.edu/repos/$repo/os/$arch
Server = http://mirror.strits.dk/artix-linux/repos/$repo/os/$arch
Server = https://mirrors.dotsrc.org/artix-linux/repos/$repo/os/$arch
Server = https://www.uex.dk/public/artix/$repo/os/$arch
Server = http://mirror1.artixlinux.org/repos/$repo/os/$arch

Re: New primary mirror

Reply #70
Here I am at another system that hasn't seen an update since last week.

Note the difference of mirror1 against that on top:  
Code: [Select]
Server = http://mirror1.artixlinux.org/artix-linux/repos/$repo/os/$arch

This no longer works with /artix-linux and the rest of the repositories have not synched since before this because I get pkgs that are newer than the current mirrors left from last week.  Nothing to do it says.  Not even a new mirrorlist.
I bet now that I will copy my own post of mirrorlist it will get plenty of updating.  So the rest of the mirrors are more than 4 days old?


Re: New primary mirror

Reply #71
Just edit it and put your own date on it

Thanks for your thought. Yet, it does not answer my question at all.

Never mind, the developers changed the date within the file accordingly and there is no need for the users to tinker with it anymore (other than changing the order of the servers, of course.)