[Solved] Does you pacman / paru also looks strange after latest updates?

General system Pacman & AUR helpers
1

After latest big changes from few weeks ago, my pacman / paru looks like this:

image
image1920×403 69.7 KB

  • no Pacman animation on progress bars, just ugly hashes
  • list of packages are missing line breaks

My Pacman version is Pacman v7.1.0 - libalpm v16.0.1

Paru: paru v2.1.0 - libalpm v16.0.1

IDK what can cause this :confused:

2

Did you overwrite your pacman.conf with pacnew file?

It certainly looks like it since you no longer have the EOS repo on your list.

3

I know nothing about Paru, but pacman had an update recently and perhaps the pacman.conf.pacnew file over wrote the pacman.conf file.

My /etc/pacman.conf

/etc/pacman.conf

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

GENERAL OPTIONS

[options]

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
Architecture = auto

Pacman won’t upgrade packages listed in IgnorePkg and members of IgnoreGroup

#IgnorePkg =
#IgnoreGroup =

#NoUpgrade =
#NoExtract =

Misc options

#UseSyslog
Color
ILoveCandy
#NoProgressBar
CheckSpace
#VerbosePkgLists
ParallelDownloads = 20
DownloadUser = alpm
#DisableSandboxFilesystem
#DisableSandboxSyscalls

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.

REPOSITORIES

- 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.

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

#[core-testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

#[extra-testing]
#Include = /etc/pacman.d/mirrorlist

[extra]
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.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

An example of a custom package repository. See the pacman manpage for

tips on creating your own repositories.

#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

Color
ILoveCandy

should look like this and will probably take care of most visual things you noticed.

Pudge

EDIT:
Darn, Dalto beat me to it.

4

Thank you! It looks like

Color
ILoveCandy

helped for pacman cute animation. But I still do not know why list of packages is not being showed in one column :frowning:

5

VerbosePkgListswas the option

6

Did you also re–add the endeavouros repo and all the other numerous changes we make?

You should not just blindly overwrite config files with the pacnew versions.