[SOLVED] Upgrading to Pacman 4.1 - various issues

tedbell · 2013-04-05 02:17:45

This may be basic but I've never encountered it before.
I just updated pacman and I now get this error:

package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory
warning: config file /etc/pacman.conf, line 19: directive 'SyncFirst' in section 'options' not recognized.
warning: config file /etc/pacman.conf, line 19: directive 'SyncFirst' in section 'options' not recognized.
package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory
package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory

package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory

here is my 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/
HoldPkg     = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst   = pacman
#XferCommand = /usr/bin/curl -C - -f %u > %o
#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
#UseDelta
#TotalDownload
CheckSpace
#VerbosePkgLists

# 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 = Optional TrustedOnly

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

#[testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist

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

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

#[community-testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist

[community]
SigLevel = PackageRequired
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]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist

[multilib]
SigLevel = PackageRequired
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

Sorry I don't have any more info.

Thanks for any help.

Last edited by jasonwryan (2013-04-05 08:19:53)

T.J.S. · 2013-04-05 02:26:24

You need to use the new "pacman.conf" file, which is under the name "pacman.conf.pacnew".

# mv /etc/pacman.conf /etc/pacman.conf.backup # just in case
# mv /etc/pacman.conf.pacnew /etc/pacman.conf

Generally you have to pay a little more attention to pacman warnings when you upgrade.

Oh, and don't forget to enable multilib in the new configuration file.

Last edited by T.J.S. (2013-04-05 02:27:53)

cfr · 2013-04-05 02:28:51

You need to compare the two and merge your customisations with the changes to the default version. Otherwise, the changes you've made will be lost.

Please see the wiki for information on how to handle *.pacsave, *.pacnew etc.

Just moving the new version into place is not usually the right thing to do.

T.J.S. · 2013-04-05 02:53:07

You're right, merging is the right thing to do in theses cases.

I was just trying to help for this specific case, where the average user has usually only changed the "multilib" line in the conf file. But yeah, it's good you mentioned the right general approach, I should have done the same.

tedbell · 2013-04-05 03:37:39

ah I see, I thought pacman.conf.pacnew was the old one...
Thanks all

binskipy2u · 2013-04-05 04:00:35

I dont know how this is solved.. i read the wiki, I don't see how it helps ...
I tried mv /etc/pacman.conf.pacnew /etc/pacman.conf
mv: cannot stat ‘/etc/pacman.conf.pacnew’: No such file or directory

i'm at a loss

i have no pacman.conf.pacnew in the /etc

I still get the same error when upgrading, when choosing to upgrade pacman >
error: failed to prepare transaction (could not satisfy dependencies)
:: package-query: requires pacman<4.1

core/pacman 4.1.0-2 (base base-devel) [installed: 4.0.3-7] <result of pacman -Ss pacman, so i do have the version Less than < 4.1

Last edited by binskipy2u (2013-04-05 04:05:25)

jasonwryan · 2013-04-05 04:43:09

How can you have run Arch for the last three years without understanding pacnews?

They will only be present *after* you successfully upgrade a package...

binskipy2u · 2013-04-05 04:48:20

I cant sucessfully upgrade at all at this time..

jasonwryan · 2013-04-05 04:54:31

Yes, you can. You are just not taking responsibility for installing unsupported packages.

That is your problem, not ours...

binskipy2u · 2013-04-05 05:15:03

what rudeness... i guess there is no real order to forums except the fake order enforced by those that i guess, were born using arch..

tedbell · 2013-04-05 05:21:23

I still get this error, any clues:

package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory

djringjr · 2013-04-05 05:38:48

I don't have a pacman.conf.pacnew

Is there a work-around for this?

Thank you,

David

T.J.S. wrote:

You need to use the new "pacman.conf" file, which is under the name "pacman.conf.pacnew".
# mv /etc/pacman.conf /etc/pacman.conf.backup # just in case
# mv /etc/pacman.conf.pacnew /etc/pacman.conf
Generally you have to pay a little more attention to pacman warnings when you upgrade.
Oh, and don't forget to enable multilib in the new configuration file.

flipper T · 2013-04-05 05:52:58

Here is a vanilla pacman.conf.pacnew for your use:

#
# /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/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -C - -f %u > %o
#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
#UseSyslog
#Color
#TotalDownload
CheckSpace
#VerbosePkgLists

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

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

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

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

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

[community]
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

proudzhu · 2013-04-05 05:57:11

tedbell wrote:

I still get this error, any clues:

package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory

Wait package-query to update.Or you can try aur/cower

Allan · 2013-04-05 05:58:52

tedbell wrote:

I still get this error, any clues:

package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory

You need to rebuild package-query (or probably use package-query-git until it is updated).

Allan · 2013-04-05 06:00:07

binskipy2u wrote:

I still get the same error when upgrading, when choosing to upgrade pacman >
error: failed to prepare transaction (could not satisfy dependencies)
:: package-query: requires pacman<4.1

Uninstall package-query, then update... It is a AUR package is it is your responsibility to handle its updates.

elkoraco · 2013-04-05 06:19:59

Allan wrote:

It is a AUR package is it is your responsibility to handle its updates.

TOO MANY ITS!

isacdaavid · 2013-04-05 06:28:39

elkoraco wrote:

Allan wrote:
It is a AUR package is it is your responsibility to handle its updates.
TOO MANY ITS!

LOL. Be patient guys, developers like Allan cannot get perfect syntax at the forums all the time, and some of us still have a way to get into the Arch Way.

Mr Green · 2013-04-05 06:49:44

Update went smoothly once I removed pacdep (pacman warned me of the problem).

@Allan there is nothing wrong with your syntax, compared to some I have read on forums...

isacdaavid · 2013-04-05 07:08:09

binskipy2u wrote:

I dont know how this is solved.. i read the wiki, I don't see how it helps ...
I tried mv /etc/pacman.conf.pacnew /etc/pacman.conf
mv: cannot stat ‘/etc/pacman.conf.pacnew’: No such file or directory
i'm at a loss
i have no pacman.conf.pacnew in the /etc
I still get the same error when upgrading, when choosing to upgrade pacman >
error: failed to prepare transaction (could not satisfy dependencies)
:: package-query: requires pacman<4.1

core/pacman 4.1.0-2 (base base-devel) [installed: 4.0.3-7] <result of pacman -Ss pacman, so i do have the version Less than < 4.1

mai
Yes, of course you have pacman < 4.1 and it won't let you upgrade since package-query requires it. Pacman's output is crystal clear.

In other words, a safe upgrade and compliance with package-query dependencies are mutually exclusive. You either remove package-query and other conflicting packages before upgrading pacman, thus you can upgrade the rest of your system; or stay with package-query/yaourt/etc which are AUR scripts that may or may not be updated soon in order to work with newest pacman.

Remember AUR packages are unofficial and they are likely to break stuff if little system maintenance and involvement is shown from your part, though I wouldn't classify this as a real breakage. package-query simply is not in perfect timing with pacman releases, and that's all you ought to know.

isacdaavid · 2013-04-05 07:18:20

tedbell wrote:

I just updated pacman and I now get this error:

package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory
warning: config file /etc/pacman.conf, line 19: directive 'SyncFirst' in section 'options' not recognized.
warning: config file /etc/pacman.conf, line 19: directive 'SyncFirst' in section 'options' not recognized.
package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory
package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory

package-query: error while loading shared libraries: libalpm.so.7: cannot open shared object file: No such file or directory

Just one question: how did you do the update? Was it a

pacman -Syuf

or whatever parameter combination containing the enforcing -f ? I guess you did so.

simendsjo · 2013-04-05 08:13:17

I get the following error when trying to upgrade pacman:

:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] Y

resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: package-query: requires pacman<4.1
:: pacman-color: requires pacman<4.1

Will this be "fixed" by just waiting until package-query ond pacman-color is updated, or do I need to do something myself?

HalosGhost · 2013-04-05 08:16:38

First, pacman 4.1 has color support, so you probably don't need pacman-color anymore. Second, the question regarding package-query has been answered several times in various threads. Please use the search function to see if someone has answered your issue before you create a new thread that may be superfluous.

All the best,

-HG

jasonwryan · 2013-04-05 08:17:21

Please learn to search before posting.

Merging with one of the other threads...

dmacblu · 2013-04-05 12:41:54

try sudo pacman -R yaourt
sudo pacman -R package-query
then sudo pacman -Syyu
then fix your /etc/pacman.conf file as suggested above then put yaourt back in (if you still want it).

Arch Linux

#1 2013-04-05 02:17:45

[SOLVED] Upgrading to Pacman 4.1 - various issues

#2 2013-04-05 02:26:24

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#3 2013-04-05 02:28:51

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#4 2013-04-05 02:53:07

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#5 2013-04-05 03:37:39

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#6 2013-04-05 04:00:35

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#7 2013-04-05 04:43:09

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#8 2013-04-05 04:48:20

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#9 2013-04-05 04:54:31

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#10 2013-04-05 05:15:03

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#11 2013-04-05 05:21:23

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#12 2013-04-05 05:38:48

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#13 2013-04-05 05:52:58

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#14 2013-04-05 05:57:11

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#15 2013-04-05 05:58:52

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#16 2013-04-05 06:00:07

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#17 2013-04-05 06:19:59

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#18 2013-04-05 06:28:39

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#19 2013-04-05 06:49:44

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#20 2013-04-05 07:08:09

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#21 2013-04-05 07:18:20

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#22 2013-04-05 08:13:17

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#23 2013-04-05 08:16:38

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#24 2013-04-05 08:17:21

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#25 2013-04-05 12:41:54

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

Board footer