Arch Linux

cutuchiqueno

Member

Registered: 2013-07-06

Posts: 70

[SOLVED] dependency in haskell-core prevent system from being updated

I use the haskell-core repository provided by the arch haskell project. For 4 days now I get an error message when I try to update packages with pacman -Syu.

Fehler: Konnte den Vorgang nicht vorbereiten (Kann Abhängigkeiten nicht erfüllen)
:: haskell-pcre-heavy: benötigt haskell-semigroups=0.16.2.2_0-83

(Error: Could not prepare the process (Could not fulfill dependencies) # something like this

As a workaround for some time to see if this is fixed somehow in the next days I tried to put each of them and both together to IgnorePkg in /ect/pacman.conf. However, this did not change anything and I can still not update my system.

Is this problem really a problem of the haskell-core repository or not?

How can I omit these packages being updated so that I can at least update the rest of the packages since IgnorePkg does not seem to work.

Thx

Last edited by cutuchiqueno (2015-10-13 08:23:37)

giuscri

Member

From: Milan, Italy

Registered: 2013-08-19

Posts: 21

Re: [SOLVED] dependency in haskell-core prevent system from being updated

Would you mind to post the entire /etc/pacman.conf?

ayekat

Member

Registered: 2011-01-17

Posts: 1,591

Re: [SOLVED] dependency in haskell-core prevent system from being updated

What's the output of

pacman -Ss haskell-pcre-heavy
pacman -Ss haskell-semigroups

?

---

pkgs │ hacks │ cfg │ blag

cutuchiqueno

Member

Registered: 2013-07-06

Posts: 70

Re: [SOLVED] dependency in haskell-core prevent system from being updated

Would you mind to post the entire /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/
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    = haskell-pcre-heavy haskell-semigroups
#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

[haskell-core]
Server = http://xsounds.org/~haskell/core/$arch

# [haskell-happstack]
# Server = http://noaxiom.org/$repo/$arch

[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

[infinality-bundle]
Server = http://bohoomil.com/repo/$arch

[infinality-bundle-multilib]
Server = http://bohoomil.com/repo/multilib/$arch

[infinality-bundle-fonts]
Server = http://bohoomil.com/repo/fonts

What's the output of

 
$ pacman -Ss haskell-pcre-heavy

no output

$ pacman -Ss haskell-semigroups
haskell-core/haskell-semigroups 0.17.0.1_0-1 [Installiert: 0.16.2.2_0-83]
Anything that associates

so yes haskell-pcre-heavy needs haskell-semigroups 0.16.2.2_0-83 which is installed but would probably being updated to 0.17.01._0-1 during the update process why dependency would break. Normally these conflicts are handled very well during update processes. I don't know what is going wron in this case.

However I managed to at least get an update of non haskell-core packages by putting haskell-* to IgnorePkg in pacman.conf. Still the main problem remains intransparent to me.

Last edited by cutuchiqueno (2015-09-16 14:49:53)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,798

Re: [SOLVED] dependency in haskell-core prevent system from being updated

The pcre-heavy package has been removed from the repo and no other package has been updated to provide the missing package, that's why it can't resolve the conflict (and why -Ss turns up no results)

Last edited by V1del (2015-09-16 15:09:30)

cutuchiqueno

Member

Registered: 2013-07-06

Posts: 70

Re: [SOLVED] dependency in haskell-core prevent system from being updated

In the end I uninstalled and re-installed all packages that created an unresolvable dependency chain and afterwards this specific dependency that caused the problem was away.