[SOLVED] Problem doing update

mt_arch_user · 2023-10-19 20:37:37

I have always used sudo pacman -Syu to do an update and have had no problems.

Today, I entered that command it instead of getting the usual list of files to be updated (upgraded) and answering Y to implement this process, I get:

[bart@ASU-X99 ~]$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
:: Starting full system upgrade...
:: Replace attica with extra/attica5? [Y/n] n
:: Replace baloo with extra/baloo5? [Y/n] n
:: Replace bluez-qt with extra/bluez-qt5? [Y/n] n

followed by a long list of files requiring a Y/n prompt. I entered CTRL-C to stop the process.
As this is the first time I've seen this reaction, I'm concerned that something is not right. I don't want to blow up the whole system, so I'm asking about it here.

Has something been changed? Do I have a problem? What should I do?

Last edited by mt_arch_user (2023-10-23 09:26:15)

dogknowsnx · 2023-10-19 21:06:49

Not a KDE user myself, but if you search for the packages mentioned above on the "Packages" page, you will see that the KDE-Unstable repo is currently populated, implementing Qt6, so there's been a renaming of Qt5 package versions to make for a smooth transition...

Trilby · 2023-10-19 21:18:42

The default / suggested response to those questions was Yes, why did you explicitly enter 'n' for them?

mt_arch_user · 2023-10-19 21:51:55

Trilby wrote:

The default / suggested response to those questions was Yes, why did you explicitly enter 'n' for them?

Because I didn't trust the process, so I took the path of not allowing the change to be made.

mt_arch_user · 2023-10-19 22:08:37

dogknowsnx wrote:

Not a KDE user myself, but if you search for the packages mentioned above on the "Packages" page, you will see that the KDE-Unstable repo is currently populated, implementing Qt6, so there's been a renaming of Qt5 package versions to make for a smooth transition...

Do I understand that the changes are basically changes to the file names, and because it says core is up to date and extra is up to date there will be no changes to the files themselves, only the names will be changed? If so, I should allow this process to proceed?

dogknowsnx · 2023-10-19 22:19:11

Please post the complete log for the attempted update and your pacman.conf, if still in doubt how to proceed.

Trilby · 2023-10-19 22:36:22

mt_arch_user wrote:

it says core is up to date and extra is up to date there will be no changes to the files themselves

core and extra are referring to the databases, not packages / files. Files will always be changed in updates - that's the point of the update, to get new versions of packages / files.

mt_arch_user wrote:

I should allow this process to proceed?

Yes.

mt_arch_user · 2023-10-20 00:29:21

dogknowsnx wrote:

Please post the complete log for the attempted update and your pacman.conf, if still in doubt how to proceed.

Here is

/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 = 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`.

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

#[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

And,

 /log/log/pacman

is huge, going back just about two years. As far as I can tell, based on date and time of entries, the relevant entries the started and cancelled latest

-Syu

attempts.

[2023-10-19T14:05:44-0600] [PACMAN] Running 'pacman -Syu'
[2023-10-19T14:05:44-0600] [PACMAN] synchronizing package lists
[2023-10-19T14:05:45-0600] [PACMAN] starting full system upgrade

As I said, I cancelled the operation, so I am not surprised there are only three lines!

Last edited by mt_arch_user (2023-10-20 00:44:49)

dakota · 2023-10-20 00:55:51

You edited out a lot of useful information.

Your last successful, full-system upgrade, was about 3 weeks ago, followed by several partial upgrades.
Then several abandonded upgrades starting yesterday (or the day before?).

I think everything looks okay. I would go ahead and accept the defaults for all those questions, like Trilby suggested.

Cheers,

mt_arch_user · 2023-10-20 02:56:05

OK. Here I go.

Thanks to all! I just wasn't sure. This was the first time I have seen that reaction from pacman. Thought I'd check.

mt_arch_user · 2023-10-20 03:50:46

All went well! I was actually astounded by the amount of ... ah... stuff that went on during that process! Without even a warning message!

Again, a big thank you for the replies, the help I got on this forum!

Before I mark this thread as solved, is there a place where I can voice my pleasure, or appreciation to the developers who are responsible for creating what has to be a horrendously complex process?

dogknowsnx · 2023-10-21 11:45:22

mt_arch_user wrote:

Before I mark this thread as solved, is there a place where I can voice my pleasure, or appreciation to the developers

I'm pretty sure @Allan got the message, since he seems to be reading all topics that have the words "pacman" or "update" in the title...

Arch Linux

#1 2023-10-19 20:37:37

[SOLVED] Problem doing update

#2 2023-10-19 21:06:49

Re: [SOLVED] Problem doing update

#3 2023-10-19 21:18:42

Re: [SOLVED] Problem doing update

#4 2023-10-19 21:51:55

Re: [SOLVED] Problem doing update

#5 2023-10-19 22:08:37

Re: [SOLVED] Problem doing update

#6 2023-10-19 22:19:11

Re: [SOLVED] Problem doing update

#7 2023-10-19 22:36:22

Re: [SOLVED] Problem doing update

#8 2023-10-20 00:29:21

Re: [SOLVED] Problem doing update

#9 2023-10-20 00:55:51

Re: [SOLVED] Problem doing update

#10 2023-10-20 02:56:05

Re: [SOLVED] Problem doing update

#11 2023-10-20 03:50:46

Re: [SOLVED] Problem doing update

#12 2023-10-21 11:45:22

Re: [SOLVED] Problem doing update

Board footer