[SOLVED] Upgrading to Pacman 4.1 - various issues

hokasch · 2013-04-09 20:34:40

Sure, because you have a repo enabled which a provides a package-query package.

If a system update conflicts with an unsupported package (as in "not in the official repos"), you will need to rebuild that package with an updated PKGBUILD which resolves the conflict. Either fix the PKGBUILD yourself, or wait for it to be updated in AUR. In the mean time, either hold back on the system update or remove the offending package.

Instead of removing the unsupported package, you can also explicitly install the new package in question from the repos and skip dependency checks (better not use this with -Syu), then update everything, rebuild and install the unsupported package.

Its really that simple.

cfr · 2013-04-09 21:18:10

fulafisken wrote:

This solution worked for me, no need to remove packages:
pacman -Syy
pacman -S package-query
answer no to "upgrade pacman first?"
pacman -S pacman
pacman -Syu

I don't suppose this matters in this case but in general this is not a good strategy as it involves doing the equivalent of pacman -Syy <some-package> and that could easily break things if you are not careful. It would be safer, in general, to remove the package temporarily, upgrade and reinstall. (If that proves difficult, it would be best to do nothing until you can investigate further e.g. if pacman wants to remove half your system along with <some-package>, best to wait on advice/further research.)

Convergence · 2013-04-11 02:14:13

A short story:
One time my google search went recursive. I encountered some pacman error, so I did the logical thing... I googled it. The first link google presented was here on the forums, and it seemed perfectly relevant. The only response to the question was a link that I clicked, which was to a sarcastic "let me google that for you" site, which brought be right back to my initial search! Being tired, I almost clicked the first link google presented to me, then I said slowly and stupidly, "hey.... wait a minute!"

micer · 2013-04-21 08:33:34

Hi guys!

I also had similar problem with updates, so I removed package-query and yaourt and then I was able to update. The problem is I now can't install yaourt or package-query.

sudo pacman -S yaourt
error: target not found: yaourt

I moved pacman.conf.pacnew to pacman.conf before. Should I change something in my pacman.conf file?

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

WorMzy · 2013-04-21 08:37:24

No, you should visit the AUR and learn to makepkg.

Daerun · 2013-04-21 09:56:28

Both yaourt and package-query ar not official packages, they both are to be manually downloaded from AUR.

micer · 2013-04-21 12:40:27

Ok it works now, what an easy solution. Thanks WorMzy and Daerun!

nadman10 · 2013-04-25 17:34:58

debdj wrote:

At times I wonder why some people use arch -_-
Is it because it's cool telling people 'Hey! I use arch', just like the case for some people about bt? Weird.

I can't wait until you post a question in the forum so I can throw this in your face.

jasonwryan · 2013-04-25 21:43:50

nadman10 wrote:

debdj wrote:
At times I wonder why some people use arch -_-
Is it because it's cool telling people 'Hey! I use arch', just like the case for some people about bt? Weird.
I can't wait until you post a question in the forum so I can throw this in your face.

That is uncalled for, please refrain from personal slights:
https://wiki.archlinux.org/index.php/Fo … ther_Users

theodoreward · 2013-05-14 19:52:25

jasonwryan wrote:

theodoreward wrote:
I didn't even realize I had yaourt installed.
Then you are not running Arch but one of the derivatives like Archbang or Manjaro; which is the very reason they are not supported here...

No, I had simply installed yaourt for something at some point and forgot about it, because I use packer fronted by my own scripts.

Aginor · 2014-03-27 19:53:50

flipper T wrote:

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

You, sir, are a life saver. So I'm a total rookie on Linux and whilst fumbling around trying to install Adobe Reader, I uncommented multilib at the bottom. I couldn't use pacman -U whatsoever after that, which certainly made learning how to use the AUR difficult. After commenting it back out, everything works fine now

jasonwryan · 2014-03-27 20:13:06

Please don't necrobump old threads, especially with an empty post: https://wiki.archlinux.org/index.php/Fo … Bumping.27

Closing

Arch Linux

#51 2013-04-09 20:34:40

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

#52 2013-04-09 21:18:10

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

#53 2013-04-11 02:14:13

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

#54 2013-04-21 08:33:34

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

#55 2013-04-21 08:37:24

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

#56 2013-04-21 09:56:28

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

#57 2013-04-21 12:40:27

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

#58 2013-04-25 17:34:58

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

#59 2013-04-25 21:43:50

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

#60 2013-05-14 19:52:25

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

#61 2014-03-27 19:53:50

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

#62 2014-03-27 20:13:06

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

Board footer