How does Arch migration affect a new install of EOS?

I guess the Subject says it all: For a new install of EOS, is there anything related to the Archlinux migration that changes the installation process or anything required after installation is complete?

The system should update all packages during install. I’m not sure if it fetches the default config files during install or not.

So, the only thing that might be necessary is to handle the /etc/pacman.conf.pacnew file. But since it’s a new install, you should just overwrite it with the latest one i.e.

# mv /etc/pacman.conf.pacnew /etc/pacman.conf

if it’s not handled by the installer already.

I am not a liveISO or Calamares expert, but

  1. an online install should be fine
  2. an offline install might have a problem until the next ISO comes out ?

Maybe someone more up on the liveISO could shed some light on # 2?


I just spun up a VM of an Online install using the EndeavourOS_Cassini_Nova-03-2023_R1.iso and tried i3wm. It installed fine as far as I can tell, but since I’m just learning i3 I’m not sure.

That will definitely not be a good idea. It would remove the endeavouros repo. Although, I don’t think there will be a pacnew file after installation in this case.

You will need to make the pacman.conf changes the same as with an existing install. Or you can just download the file and overwrite the one on your install.

I think that pacman.conf comes from the ISO for both offline and online installs so it should be the same in both cases.


Thanks, I was not sure about this.


1 Like

Ah, I forgot that the .pacnew comes directly from Arch, and so no endeavouros repo there.

1 Like

after my test install of EOS-i3wm my /etc/pacman.conf is below and I have no pacman.conf.pacnew.

# /etc/pacman.conf
# See the pacman.conf(5) manpage for option and repository directives

# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta    = 0.7
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
ParallelDownloads = 5

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.

#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

SigLevel = PackageRequired
Include = /etc/pacman.d/endeavouros-mirrorlist

#Include = /etc/pacman.d/mirrorlist

Include = /etc/pacman.d/mirrorlist

Include = /etc/pacman.d/mirrorlist

#Include = /etc/pacman.d/mirrorlist

Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#Include = /etc/pacman.d/mirrorlist

Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

So it’s still got the [community] repo

1 Like

Yes exactly, you need to replace or update it just like you would on an existing install.

So just comment out the [community] include??

This is the final config file you want on a new install.


it’s problematic, because the package update could see the endeavouros repo as part of a manual modification. If it does not, it will remove the endeavouros repo, too.
If the later is the case, I would say a new set of ISO’s would be necessary to include the new pacman.conf.


That would be the best solution i guess?

Can confirm that the pacman.conf file is pulling from the iso’s version instead of online when using the online installer (using the 03_2023_R1 iso). Will there be a new ISO release to address this new pacman update?

what happens when you update without modifying it? Do you get a pacman.conf.pacnew?

You should not get a pacnew. In an online install you will get the current version of pacman but the older pacman.conf.

It doesn’t let me upgrade since it’s the online installer, it already automatically installs the latest version of pacman.

I think that doesn’t make it better. Either the community repo’s get disabled, which then triggers errors because the still configured repo can’t be found - leading to necessary manual intervention although the installation was done after the migration. Or another pacman update is released before that which then leads to the possible creation of a pacnew file and still manual intervention necessary, although the installation took place after the migration.

Yes, it is a problem that we need to fix.


I just want to make sure I’m doing this right. I have a working EOS-Plasma system and my yay -Syu updates work correctly. All I did was edit /etc/pacman.conf and comment out the community section. Community-testing was already commented out.

Up until this point I had not modified pacman.conf so I have the EOS repositories as they were on original install.

So is that all I do?