Pacman update & pacman-color

Since there is a pacman update in [testing], I had to remove pacman-color and shaman (since they needed pacman<3.3).
I had aliases for pacman->pacman-color and I got rid of them. So when I source ~/.zshrc without the alias it says:
zsh: command not found: pacman-color
When I run pacman.
My current solution is to symlink /usr/bin/pacman-color to /usr/bin/pacman, but is there a better way?

Strange - although I don't run zsh, so I'm guessing it's strange
Given that your aliases were *all* in .zshrc and you removed them all
and 'source ~/,zshrc' is a valid command in zsh then something is odd.
I take it you ran your aliases as your normal user. Try logging in as root
and running pacman.
Deej

Similar Messages

[SOLVED]Pacman update fails

Hi,
Yesterday everything was working great but today it isn't anymore.
The problem
I did
pacman -Syu
Output:
sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
archlinuxfr is up to date
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n]
So i choose Y and i get this:
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: package-query: requires pacman<3.5
:: pacman-color: requires pacman=3.4.3
What does this mean and how can I solve this?
As described here: https://bbs.archlinux.org/viewtopic.php?pid=907659
I removed yaourt but this didn't solve the problem
Thanks in advance!
Last edited by tgoossens (2011-03-24 12:11:46)

I had this same problem, and I went through the instructions as posted, but it must have removed pacman in the process. Now, I cannot update anything. I went through the stickied topic on pacman but it didn't work. I found some instructions on downloading pacman and installing it manually, but now every time I run the pacman command I get:
pacman: error while loading shared libraries: libalpm.so.6: cannot open shared object file: No such file or directory
I googled that and none of those instructions work for me. Is there a way I can save my system?
Edit: And now my laptop has the same error preventing me from updating Pacman, what should I do to resolve that one? I would think that something in the repositories needs to be fixed and this is probably a bug, considering the home page doesn't say anything about it.
Edit 2: I did the following
sudo mv /usr/lib/liblzma.so /usr/lib/liblzma.so.0
And now pacman works, but it cannot find a single mirror that I have set up, it says "error retrieving file" on everything.
Edit 3: Nevermind, I give up. I'm going to wipe and reformat my computer. This is RIDICULOUS. I hope the same problem doesn't happen to my laptop, what is the *official* way to fix the "package-query: requires pacman<3.5" problem?
Last edited by jlacroix (2011-03-24 14:23:20)

[Solved] Makepkg aborting after last pacman update

Hi all,
firing makepkg yields:
$ makepkg
==> ERROR: An unknown error has occurred. Exiting...
And therefore this happens also when I try building packages of the AUR with yaourt.
The problem showed up with last pacman update.
What I am I doing wrong?
Thanks for you patience,
Davide
Last edited by flakedave (2010-06-23 22:46:39)

Yeah, version and help are fine.
$ cat /etc/makepkg.conf
# /etc/makepkg.conf
# SOURCE ACQUISITION
#-- The download utilities that makepkg should use to acquire sources
# Format: 'protocol::agent'
DLAGENTS=('ftp::/usr/bin/wget -c --passive-ftp -t 3 --waitretry=3 -O %o %u'
'http::/usr/bin/wget -c -t 3 --waitretry=3 -O %o %u'
'https::/usr/bin/wget -c -t 3 --waitretry=3 --no-check-certificate -O %o %u'
'rsync::/usr/bin/rsync -z %u %o'
'scp::/usr/bin/scp -C %u %o')
# Other common tools:
# /usr/bin/snarf
# /usr/bin/lftpget -c
# /usr/bin/curl
# ARCHITECTURE, COMPILE FLAGS
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"
#-- Exclusive: will only run on x86_64
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe"
CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe"
LDFLAGS="-Wl,--hash-style=gnu -Wl,--as-needed"
#-- Make Flags: change this for DistCC/SMP systems
#MAKEFLAGS="-j2"
# BUILD ENVIRONMENT
# Defaults: BUILDENV=(fakeroot !distcc color !ccache)
# A negated environment option will do the opposite of the comments below.
#-- fakeroot: Allow building packages as a non-root user
#-- distcc: Use the Distributed C/C++/ObjC compiler
#-- color: Colorize output messages
#-- ccache: Use ccache to cache compilation
BUILDENV=(fakeroot !distcc color !ccache)
#-- If using DistCC, your MAKEFLAGS will also need modification. In addition,
#-- specify a space-delimited list of hosts running in the DistCC cluster.
#DISTCC_HOSTS=""
# GLOBAL PACKAGE OPTIONS
# These are default values for the options=() settings
# Default: OPTIONS=(strip docs libtool emptydirs zipman purge)
# A negated option will do the opposite of the comments below.
#-- strip: Strip symbols from binaries/libraries in STRIP_DIRS
#-- docs: Save doc directories specified by DOC_DIRS
#-- libtool: Leave libtool (.la) files in packages
#-- emptydirs: Leave empty directories in packages
#-- zipman: Compress manual (man and info) pages in MAN_DIRS with gzip
#-- purge: Remove files specified by PURGE_TARGETS
OPTIONS=(strip docs libtool emptydirs zipman purge)
#-- File integrity checks to use. Valid: md5, sha1, sha256, sha384, sha512
INTEGRITY_CHECK=(md5)
#-- Options to be used when stripping binaries. See `man strip' for details.
STRIP_BINARIES="--strip-all"
#-- Options to be used when stripping shared libraries. See `man strip' for details.
STRIP_SHARED="--strip-unneeded"
#-- Options to be used when stripping static libraries. See `man strip' for details.
STRIP_STATIC="--strip-debug"
#-- Manual (man and info) directories to compress (if zipman is specified)
MAN_DIRS=({usr{,/local}{,/share},opt/*}/{man,info})
#-- Doc directories to remove (if !docs is specified)
DOC_DIRS=(usr/{,local/}{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc})
#-- Directories to be searched for the strip option (if strip is specified)
STRIP_DIRS=(bin lib sbin usr/{bin,lib,sbin,local/{bin,lib,sbin}} opt/*/{bin,lib,sbin})
#-- Files to be removed from all packages (if purge is specified)
PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod)
# PACKAGE OUTPUT
# Default: put built package and cached source in build directory
#-- Destination: specify a fixed directory where all packages will be placed
#PKGDEST=/home/packages
#-- Source cache: specify a fixed directory where source files will be cached
#SRCDEST=/home/sources
#-- Source packages: specify a fixed directory where all src packages will be placed
#SRCPKGDEST=/home/srcpackages
#-- Packager: name/email of the person or organization building packages
#PACKAGER="John Doe <[email protected]>"
# EXTENSION DEFAULTS
# WARNING: Do NOT modify these variables unless you know what you are
# doing.
PKGEXT='.pkg.tar.xz'
SRCEXT='.src.tar.gz'
# vim: set ft=sh ts=2 sw=2 et:

Howto: Pacman Updates on your Awesome3 bar

So in my boredom one day, I decided to add a textbox to my Awesome wibox bar (formerly referred to as a statusbar) that displayed the number of updates available for my system. I see many users getting this info from Conky, but I wanted to get better acquainted with LUA and the rc.lua awesome syntax.
This guide assumes the user has a fresh Awesome installation with a default rc.lua file.
Thanks to Xyne for the pacman perl scripts (Shown later).
What you will need:
Awesome 3.4 (pacman version)
perl
Files you will need:
pacman-updates: Necessary to provide the user-readable output to awesome-client
#! /usr/bin/perl
## script by Xyne
## output format tweaked slightly
## http://bbs.archlinux.org/viewtopic.php?id=57291
use strict;
use warnings;
my $n = (`pacman -Qu | wc -l`);
chomp ($n);
if ($n == 0)
print "\" [ No new packages ] \""
elsif ($n == 1)
print "\" [ 1 new package ] \""
else
print "\" [ $n new packages ] \""
pacman-updater: A basic way of keeping your pacman package list refreshed.
#! /bin/bash
# Script to update pacman database
# Will be put in /etc/cron.hourly
pacman -Sy 1>/dev/null 2>&1
pacman-widget: Executes the pacman-updates script and passes it to awesome-client for display
#! /bin/bash
## Script to update awesome-client widget with pacman package information
## Script belongs in /etc/cron.hourly
echo mytextbox.text = `perl /path/to/script/pacman-updates` | awesome-client
Place the files in the script folder of your choice. Then, ensure all files have adequate permissions so that they can be executed. (chmod)
Open your rc.lua file with your favorite text editor. Create a textbox widget by adding the following:
mytextbox = widget({ type = "textbox", name = "mytextbox" })
mytextbox.text = " [ Pacman Updates ] "
Now that the code for created the widget has been added, we need to add the widget to the existing wibox. Find the section of your rc.lua file that looks like this:
-- Create the wibox
mywibox[s] = awful.wibox({ position = "top", screen = s })
-- Add widgets to the wibox - order matters
mywibox[s].widgets = {
mylauncher,
mytaglist[s],
mypromptbox[s],
layout = awful.widget.layout.horizontal.leftright
mylayoutbox[s],
mytextclock,
s == 1 and mysystray or nil,
mytasklist[s],
layout = awful.widget.layout.horizontal.rightleft
end
Add the line "mytextbox," underneath the default textclock widget:
-- Create the wibox
mywibox[s] = awful.wibox({ position = "top", screen = s })
-- Add widgets to the wibox - order matters
mywibox[s].widgets = {
mylauncher,
mytaglist[s],
mypromptbox[s],
layout = awful.widget.layout.horizontal.leftright
mylayoutbox[s],
mytextclock,
mytextbox,
s == 1 and mysystray or nil,
mytasklist[s],
layout = awful.widget.layout.horizontal.rightleft
end
Copy pacman-updater and pacman-widget scripts into your /etc/cron.hourly folder:
sudo cp pacman-updater /etc/cron.hourly
If everything went smoothly, you should see package information updated hourly on your wibox in the top right corner, such as:
I hope this guide has proven useful. Please post if you see any errors or could suggest improvements, as I will update the guide.
Thanks
Last edited by trann (2009-11-05 20:03:45)

Oh cool, I never realized that vicious was basically an upgraded wicked. I had an old rc.lua that used wicked, and when they got rid of wicked no sooner than I made a config using it; I just moved on to another WM rather than try to read about and choose between vicious, obvious and bashets. If I had spent 5 secs learning that my old config would've worked for what I was doing simply by replacing the word 'wicked' with the word 'vicious' everywhere, I might have not been so distraught.
But yes, thanks for the snippet using vicious. It works great. I modified it a little (I didn't feel like being informed when there were 0 updates, only when there were some):
local pacupdates = widget({type="textbox"})
vicious.register(pacupdates,vicious.widgets.pacman,
function (widget, args)
if args[1] == 0 then
return ''
else
return ' <span color="red">'..args[1]..' Updates</span> '
end
end)
You obviously have to require("vicious") somewhere and put pacupdates in your mywibox[s].widgets (or some other bar, I suppose), but it is quite simple.
I suppose I could make that better by adding in an 'else if args[1] == 1 then return ' <span color="white">'..args[1]..' Update</span> ' or something, so it doesn't say "Updates" when there is only one. I suppose there is an else if in lua, but I haven't read that programming in lua thing yet, as I was planning on using xmonad instead of awesome, but seem to be experiencing some difficulties with the multi-screen setup on my tower and xmonad.
Right now, I'm thinking maybe I'll use xmonad on the laptop and awesome on the desktop, just so I have a good reason to tinker in both programming languages.
Works great and doesn't require any weird background stuff or cron.

Recommended pacman updates conky script?

Hi,
I have been trying some of the conky pacman updates scripts on the forum/wiki.
So far they either say my system is up to date when in fact pacman -Syu shows otherwise, or they fail to give any info at all.
Can anybody recommend a conky script that is working at this moment in time?:/
Last edited by ancleessen4 (2010-03-03 15:29:45)

Sure-heavily plagiairized from either arch or ubuntu threads...a work in progress...;)
If I find it back I will honour the original author...
# Create own window instead of using desktop (required in nautilus)
own_window yes
own_window_hints undecorated,below,skip_taskbar
own_window_type override
own_window_colour brown
own_window_transparent yes
own_window_hints below
background no
maximum_width 200
# Use double buffering (reduces flicker, may not work for everyone)
double_buffer yes
# fiddle with window
use_spacer right
# Update interval in seconds
update_interval 1
# Minimum size of text area
minimum_size 350 5
# Draw shades?
draw_shades yes
draw_borders no
# Stippled borders?
# stippled_borders 8
# window.border_inner_margin 4
border_width 2
# Default colors and also border colors, grey90 == #e5e5e5
default_color white
default_shade_color black
default_outline_color white
# Text alignment, other possible values are commented
#alignment top_left
alignment top_right
#alignment bottom_left
#alignment bottom_right
# Gap between borders of screen and text
gap_x 10
gap_y 30
# Text stuff
draw_outline no # amplifies text if yes
uppercase no # set to yes if you want all text to be in uppercase
override_utf8_locale no
use_xft yes
xftfont Terminus:size=9
#xftfont Sans:size=8
xftalpha 0.8
text_buffer_size 768
# Force UTF8? note that UTF8 support required XFT
override_utf8_locale yes
color1 333333
color2 cccccc
color3 ddaa00
########## BEGIN FORMATTED DISPLAY ##########
TEXT
${font :size=15}${color red}${alignc}${execi 6000 hostname}${font}${color }
${font :size=8}${alignc}${color lightgrey}$kernel${font}${color }
${hr 1}
${color slate grey}UpTime: ${alignr}${color lightgrey}$uptime${color }
${font StyleBats:size=17}k${font Terminus:size=12} CPU ${font}${hr 2}
${color slate grey}CPU:${color } ${cpu cpu0}% ${cpu cpu1}% ${alignr}${color }$loadavg
${alignc}${cpugraph cpu0 20,90 000000 ffffff} ${cpugraph cpu1 20,90 000000 ffffff}
${color slate grey}cpu0: ${alignr}${color lightgrey}${execi 5 sensors | grep "Core 0" | cut -d "+" -f2 | cut -c1-2}C${color }
${color slate grey}cpu1: ${alignr}${color lightgrey}${execi 5 sensors | grep "Core 1" | cut -d "+" -f2 | cut -c1-2}C${color }
${color slate grey}sda: ${alignr}${color lightgrey}${execi 30 hddtemp /dev/sda | cut -c 31-33}C
${color slate grey}Processes: ${color }${alignr}$processes
${color slate grey}Running: ${color }${alignr}$running_processes
${color slate grey}Top CPU:
${color #ddaa00} ${top name 1}${alignr}${top_mem cpu 1}
${color lightgrey} ${top name 2}${alignr}${top cpu 2}
${color lightgrey} ${top name 3}${alignr}${top cpu 3}
${color lightgrey} ${top name 4}${alignr}${top cpu 4}
${color lightgrey} ${top name 5}${alignr}${top cpu 5}
${color lightgrey} ${top name 6}${alignr}${top cpu 6}
${font StyleBats:size=17}M${font Terminus:size=12} MEMORY ${font}${hr 2}
${color slate grey}RAM: ${alignr}${membar 5,100}
${color slate grey}SWAP: ${alignr}${swapbar 5,100}
${color slate grey}ROOT: ${alignr}${fs_bar 5,100 /}
${color slate grey}HOME: ${alignr}${fs_bar 5,100 /home}
${color slate grey}Top Memory:
${color #ddaa00} ${top_mem name 1}${alignr}${top_mem mem 1}
${color lightgrey} ${top_mem name 2}${alignr}${top_mem mem 2}
${color lightgrey} ${top_mem name 3}${alignr}${top_mem mem 3}
${font StyleBats:size=17}5${font Terminus:size=12} NETWORK ${font}${hr 2}
${color slate grey}Local IP: ${alignr}${color }${addr eth0}
${color slate grey}Public IP: ${alignr}${color }${execi 450 ~/.scripts/externip.sh}
${color}Up: ${color }${upspeed eth0} k/s
${alignc}${upspeedgraph eth0 20,170 000000 ffffff}
${color}Down: ${color }${downspeed eth0}k/s${color}
${alignc}${downspeedgraph eth0 20,170 000000 ffffff}
${font StyleBats:size=17}v${font Terminus:size=12} UPDATES ${font}${hr 2}
${execpi 60 /home/neil/.scripts/pacman-update}${color}
${execpi 3600 paconky /home/neil/.scripts/repos.paconky}
${execpi 3600 paconky /home/neil/.scripts/aur.paconky}
${voffset 900}
Current screen grab;
http://neilhoughton.com/wp-content/uplo … nshot3.png

[SOLVED] After pacman update, system no longer boots

Updated pacman packages, and half-way through the upgrade proces fails (it mentions not being able to find package-control). Upon investigating, I notice no programs are working. I ls /usr/bin and it is empty! In a panic, I restart the machine, and it no longer boots up.
My boot is on sda3 and /root is sda5.
When bash starts up, it loads the kernel fine, and then after a second it panics and exclaims: "No init found. Try passing init=bootarg".
I load up my trusty Arch livecd and fsck the partitions. Fsck claims both partitions are clean. I am able to mount them and examine the file structure: all files look like they are there. I then try to chroot the mounted partition (sda5, my /root), and get the error that "/bin/bash" is not found, even though it is there in the correct directory. Not sure what to do now.
My grub entry, which has always worked fine prior to this:
legacy_kernel '/linux344-ck' 'acpi_osi=Linux' 'root=/dev/sda5' 'rootfstype=ext4' 'init=/sbin/init' 'pcie_aspm=force' 'acpi_backlight=vendor' 'i915.i915_enable_rc6=1' 'i915.i915_enable_fbc=1' 'i915.lvds_downclock=1' 'ipv6.disable=1' 'i915.semaphores=1' 'modprobe.blacklist=bluetooth,uvcvideo' 'ro'
legacy_initrd '/initramfs-linux-fallback.img' '/initramfs-linux-fallback.img'
UPDATE: solved issue. I didn't read the news. Upgrading via pacman broke my system because of this. Now I know! System is running smooth again.
Last edited by corruptz0r (2012-07-15 20:26:53)

Huh. I guess the problem was a couple of stale and crusty {,f}getty .service files, and an obsolete slim.service file I created a while back.
Removing them fixed my problem, although tty1 still shows boot messages (not a problem, and may not even be "new" behaviour)
Cheers Tomegun.

[solved]gcc broken after pacman update - libcloog-isl.2.so

Hi,
After a pacman update my gcc broke. When compiling it gives this error:
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/cc1: error while loading shared libraries: libcloog-isl.so.2: cannot open shared object file: No such file or directory
gcc -v output:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /build/src/gcc-4.6-20111223/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --enable-gnu-unique-object --enable-linker-build-id --with-ppl --enable-cloog-backend=isl --enable-lto --enable-gold --enable-ld=default --enable-plugin --with-plugin-ld=ld.gold --enable-multilib --disable-libssp --disable-libstdcxx-pch --enable-checking=release --with-fpmath=sse
Thread model: posix
gcc version 4.6.2 20111223 (prerelease) (GCC)
and ls /usr/lib/*cloog* output:
/usr/lib/libcloog-isl.a /usr/lib/libcloog-isl.so /usr/lib/libcloog-isl.so.3 /usr/lib/libcloog-isl.so.3.0.0
uname -a:
Linux willem-arch 3.2.4-1-ARCH #1 SMP PREEMPT Sat Feb 4 10:53:01 CET 2012 x86_64 Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz GenuineIntel GNU/Linux
How can I fix this? I already tried installen cloog with pacman but that doesn't help.
edit:
I solved the problem. There was an issue with my pacman.conf. Multilib wasn't properly enabled after the pacman4 transition.
Last edited by pientertje (2012-02-08 09:47:25)

I'm using multilib.
@Allan
more fully than pacman -Syu? Or is my mirror not up to date?
edit:
I solved the problem. There was an issue with my pacman.conf. Multilib wasn't properly enabled after the pacman4 transition.
Last edited by pientertje (2012-02-08 09:46:40)

[Solved] errors with keys after pacman update?

Hi,
I installed pacman 4.0.1-4, but now this is what happens when I try and update.
Proceed with installation? [Y/n] Y
(28/28) checking package integrity [######################] 100%
error: binutils-multilib: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is unknown trust
error: libcap-ng: signature from "Ionut Biru <[email protected]>" is unknown trust
error: cifs-utils: signature from "Tobias Powalowski <[email protected]>" is unknown trust
error: cmake: signature from "Dave Reisner <[email protected]>" is unknown trust
error: colord: signature from "Ionut Biru <[email protected]>" is unknown trust
error: lib32-glibc: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is unknown trust
error: lib32-gcc-libs: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is unknown trust
error: gcc-libs-multilib: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is unknown trust
error: gcc-multilib: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is unknown trust
error: perl: key "6D1655C14CE1C13E" is unknown
error: key "6D1655C14CE1C13E" could not be looked up remotely
error: openssl: signature from "Pierre Schmitz <[email protected]>" is unknown trust
error: git: signature from "Dan McGee <[email protected]>" is unknown trust
error: gpgme: signature from "Dave Reisner <[email protected]>" is unknown trust
error: gvfs: signature from "Dave Reisner <[email protected]>" is unknown trust
error: inetutils: key "FCF2CB179205AC90" is unknown
:: Import PGP key 9205AC90, "Eric Belanger <[email protected]>", created 2011-04-19? [Y/n] Y
error: key "Eric Belanger <[email protected]>" could not be imported
error: intltool: key "FCF2CB179205AC90" is unknown
:: Import PGP key 9205AC90, "Eric Belanger <[email protected]>", created 2011-04-19? [Y/n] ^C
Interrupt signal received
When pacman updated it suggested that I run this command,
sudo pacman-key --init
I know that usually I would say yes to a key and pacman should remember it, but what are all the errors?
Last edited by mich04 (2012-01-20 17:19:26)

# /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
HoldPkg = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#XferCommand = /usr/bin/curl -C - -f %u > %o
#CleanMethod = KeepInstalled
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options (all disabled by default)
#UseSyslog
#ShowSize
#UseDelta
#TotalDownload
#CheckSpace
# 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]
#Server = file:///home/custompkgs
Here it is.

[SOLVED] Compiz crashes Gnome after pacman update

Hardware: Nvidia NVS 3100M, latest drivers 260.19.36
Software: latest pacman -Suy
On startup, right after the login, X (or Gnome?) crashes and I see the login screen again.
After I disable compiz, I am able to use Gnome desktop.
When I start compiz via fusion-icon, it crashes everything again.
Has anyone seen this?
Any clues?
==== Update =====
I solved this by re-installing the same nvidia driver I had. During install it detected that the original installation "has been altered".
Last edited by softtower (2011-02-16 22:09:49)

That's a scary thought: what if I'm the only one with this problem... :-)
Let me answer your questions guys (and thank you for replying).
First of all, I don't have anything monitor-related in my xorg.conf.d directory. Here is what I have there:
t510 ~: ll /etc/X11/xorg.conf.d/
total 20K
-rw-r--r-- 1 root root 1.1K Aug 24 06:45 10-evdev.conf
-rw-r--r-- 1 root root 377 Jun 21 2010 10-quirks.conf
-rw-r--r-- 1 root root 443 Nov 13 10:36 10-synaptics.conf
-rw-r--r-- 1 root root 267 Nov 19 03:48 10-synaptics.conf.pacnew
-rw-r--r-- 1 root root 107 Sep 2 19:39 20-nouveau.conf
Second, I do pacman updates maybe once a month. So I had 600+ MB of downloads and something like a hundred packages, including xorg itself. However, I do know that the kernel and nvidia's proprietary driver are both latest and haven't changed.
If I delete xorg.conf, arch will try to look for noveau open-source driver and will fail because I do not have it installed: it doesn't manage power well to be used on a laptop.
Looking into Xorg.log I see this:
[ 102.032] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[ 102.032] (EE) NVIDIA(0): log file that the GLX module has been loaded in your X
[ 102.032] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
[ 102.032] (EE) NVIDIA(0): you continue to encounter problems, Please try
[ 102.032] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
[ 102.582] (II) NVIDIA(0): NVIDIA GPU NVS 3100M (GT218) at PCI:1:0:0 (GPU-0)
I will try to reinstall the same nvidia driver I have to see what happens.

Alsa not working anymore after pacman update

I had problems with my sound in arch linux. But then I uninstall pulseaudio and then my sound worked.
However, two weeks ago I performed an pacman update and now the sound isn't working anymore.
I provide my configuration data. I did all the obvious stuff like unmute, aplay -L etc. and checking sound with root account.
Can someone help with this problem?
[root@st]# aplay -D sysdefault *.wav
## ==> NO SOUND
# lspci | grep "Audio"
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1)
## aplay -L
aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
sysdefault:CARD=PCH
HDA Intel PCH, ALC269VC Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
Front speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=NVidia,DEV=0
HDA NVidia, HDMI 0
HDMI Audio Output
hdmi:CARD=NVidia,DEV=1
HDA NVidia, HDMI 1
HDMI Audio Output
hdmi:CARD=NVidia,DEV=2
HDA NVidia, HDMI 2
HDMI Audio Output
## cat /etc/asound.conf
pcm.!default {
type hw
card 0
ctl.!default {
type hw
card 0
## cat /proc/asound/modules
0 snd_hda_intel
1 snd_hda_intel
## lsmod | grep snd
snd_hda_codec_hdmi 30098 1
snd_hda_codec_realtek 39515 1
snd_hda_intel 36904 0
snd_hda_codec 149569 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep 6340 1 snd_hda_codec
snd_pcm 77709 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 7242 2 snd_pcm,snd_hda_intel
snd_timer 18726 1 snd_pcm
snd 59173 7 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 5450 1 snd
## ls /dev/snd/
by-path controlC0 controlC1 hwC0D0 hwC1D0 pcmC0D0c pcmC0D0p pcmC1D3p pcmC1D7p pcmC1D
Last edited by stevebach (2013-11-26 23:12:02)

type hw
Remove your ill-advised /etc/asound.conf - it's bypassing dmix.
To make the correct soundcard the default, there's various methods - google it.

KDEMod 3.5: problems after pacman update

I did a pacman update of KDEMod 3.5, and now, several things don't work anymore:
-there's no desktop background, it's just black
-there's no icons on the desktop: as mentioned above, it's just black (so I think the component that displays wallpaper and icons doesn't work)
-when just starting KDE, there's a "report crash" window (I don't know which the thing that crashes is, it just shows the crash window and I can click it away)
-when choosing "lock session" in the start menu, nothing happens. It used to show screensaver and require password to continue, now it does nothing at all
-maybe some other things I didn't discover yet are also broken...
How can I fix all this? I'd like my system to work properly, like it used to. KDEMod 3.5 appears to have some difficulties after pacman updates these days...
Thanks.
Last edited by aardwolf (2009-08-17 16:37:21)

Hmm, I just realized that the wallpaper is a jpeg, and it could be related to the fix I did in my previous post: http://bbs.archlinux.org/viewtopic.php?id=78076
Are they going to fix those jpeg issues soon? I think this is something vital.
EDIT: FYI: this fixed it: tar -C / -zxvf /var/cache/pacman/pkg/libjpeg-6b-6-i686.pkg.tar.gz usr/lib/libjpeg.so.62 usr/lib/libjpeg.so.62.0.0
Last edited by aardwolf (2009-08-17 16:43:14)

[SOLVED] pacman update fails: gcc requires gcc-libs=4.7.0-3

Hi
I ran pacman -Syu this morning and there's an update to pacman to install first, so I say yes but it fails like this:
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
:: 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)
:: gcc: requires gcc-libs=4.7.0-3
But I have gcc-libs 4.7.0-3 installed:
pacman -Qs gcc-libs
local/gcc-libs 4.7.0-3 (base)
Runtime libraries shipped by GCC
So what's going on?
Last edited by useradded (2012-04-11 08:08:09)

How might that break pacman? Assuming databases are current, is running
pacman -S pacman
followed by
pacman -Syu
different from what pacman itself is trying to do?
Is the message that pacman should be updated first just wrong?
So is this what you should do?
$ pacman -Syu
Recent ML chatter: linux(2)
:: Synchronizing package databases...
core 101.8 KiB 480K/s 00:00 [########################################] 100%
extra 1385.2 KiB 832K/s 00:02 [########################################] 100%
community 1636.1 KiB 810K/s 00:02 [########################################] 100%
multilib 86.4 KiB 522K/s 00:00 [########################################] 100%
:: 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...
:: gcc-libs and gcc-libs-multilib are in conflict. Remove gcc-libs-multilib? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: gcc-multilib: requires gcc-libs-multilib=4.7.0-3
No pacnew files to update.
$ pacman -Syu
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] N
I thought that itself might break pacman, which is why I updated pacman on its own. So I obviously don't get how it works...
Plus, why did you say "Or, just..." which suggests it is an alternative method rather than a better one...?
Last edited by cfr (2012-04-11 22:49:15)

Update Pacman?

My apologies if this is extremely simple; I'm used to darwin ports on a UNIX box. I'm attempting to install Apache, PHP, & MySQL on my ARMv6h Raspberry PI.
Seems like this should do the trick -
pacman -S apache php php-apache mysql
However pacman is still looking for older versions of files that aren't present on the main mirrors. ie: apache v. 2.2.22 instead of v. 2.2.23, etc... As expected, I'm generating a ton of 404s.
http://us.mirror.archlinuxarm.org/armv6h/ is the first on my mirror list.
Is there a way to self-update pacman as in mac ports? Or is pacman supposed to automatically sync with an online directory to get file/version names?
Thank You!
wv

WorMzy wrote:
You need to ask here: http://archlinuxarm.org/
ARM isn't supported here.
Indeed. Closing...
https://wiki.archlinux.org/index.php/Fo … pport_ONLY

Fast Pacman Update Checker for bash/zsh

I saw some fancy notifiers using Desktop Notification or the systray on this forum, but nothing suitable for my arch server.
The following snippet check for updates once a day, whenever you spawn a new shell.
#!/bin/bash
# add this to your bashrc/zshrc
function _current_epoch {
echo "$(($(date +%s) / 60 / 60 / 24))"
function _check_updates {
flock -n 9 || return # one concurrent update process at the time
local ignored_pkgs="^linux"
#local updates=`wc -l < /var/log/pacman-updates.log`
local updates=`grep -Ev $ignored_pkgs /var/log/pacman-updates.log | wc -l`
if [ $updates -gt 0 ]; then
echo -n "There are $updates updates. Upgrade? (y/n) [n] "
read line
if [ "$line" = Y ] || [ "$line" = y ]; then
yaourt -Syu --aur
pacman -Qu | sudo tee /var/log/pacman-updates.log >/dev/null
fi
fi
echo "$(_current_epoch)" > $HOME/.pacman-update
) 9> ~/.pacman-update.lck
if [[ $- == *i* ]] && # only interactive shells
[ -e /var/log/pacman-updates.log ] && # only after first update
[ ! -e /var/lib/pacman/db.lck ]; then # not if pacman is running
if [ -e .pacman-update ]; then
read last_epoch < $HOME/.pacman-update
if [[ -n "$last_epoch" ]]; then
if [ $(($(_current_epoch) - $last_epoch)) -ge 1 ]; then
_check_updates
fi
fi
unset last_epoch
else
_check_updates
fi
fi
To keep my package cache up to date I use a systemd.timer unit.
It prefetchs all new packages without installing them or touching the database
#/etc/systemd/timer-daily.timer
[Unit]
Description=Daily Timer
[Timer]
OnBootSec=10min
OnUnitActiveSec=1d
Unit=timer-daily.target
[Install]
WantedBy=basic.target
#/etc/systemd/timer-daily.target
[Unit]
Description=Daily Timer Target
StopWhenUnneeded=yes
#/etc/systemd/timer-daily.target.wants/pacman-update.service
[Unit]
Description=Update pacman's package cache
[Service]
Type=oneshot
Nice=19
IOSchedulingClass=2
IOSchedulingPriority=7
Environment=CHECKUPDATE_DB=/var/lib/pacman/checkupdate
ExecStartPre=/bin/sh -c "/usr/bin/checkupdates > /var/log/pacman-updates.log"
ExecStart=/usr/bin/pacman --sync --upgrades --downloadonly --noconfirm --dbpath=/var/lib/pacman/checkupdate
Have fun.
UPDATE
Use the safer checkupdates script, so it will not touch the sync database, which prevents dangerous partial system upgrades
UPDATE 2
Do not check for updates if pacman is running. Use Type=oneshot to prevent timeout.
Last edited by Mic92 (2013-07-20 05:04:33)

Tip, look into pacaur philosophy.
Shell helpers seem strange to mix with automation. My habit at shell is to enter pacaur -Syu and say no to the updates unless/until I want what I see, or the update list gets big. In that case I plan a restaurant break to coincide with my manual update.
Autoupdates can run at a particular time like early AM before working hours, when nightowls finally sleep but before morning office rush.

(paid support) Pacman Update GUI

Below the project description. If you are interested in doing this programming job, please email/pm me.
If there are questions, please reply to this post.
Pacman Update GUI
Archlinux (http://www.archlinux.org/) uses the pacman package manager. A number of GUI applications to control this package manager exist (http://wiki.archlinux.org/index.php/Pac … _Frontends), but none suit our needs.
For this project you will need to design and implement two independent GTK+ applications: an Update Manager and an Update Applet. The Update Manager must be an application that guides the user through updating the system. The Update Applet must be an application which shows a systray icon. This application will check for updates once in a while and notify the user if there are updates.
Both applications must be internationalized/localized and written in C, C++ or Python. The applications should have as little dependencies as possible. The applications must include installation scripts. The applications must be installed in compiled form. Any configuration needed for these tools should be systemwide. We do not need a gui for configuration.
Update Manager
The Update Manager must be an application that guides the user through the steps of updating the system with as little effort and as little user interaction as possible. You are expected to first define the minimal amount of steps required, design the application and then implement the application (gui and internals).
There are two possibilities for this applications:
1. You develop it from scratch.
2. You modify the gnome update manager (used in eg ubuntu) to work with pacman.
We will rely on your expertise to decide which approach is best.
Update Applet
The Update Applet provides a systray icon which checks for system updates in regular intervals. The applet should have a tooltip showing the update status, and a context menu with a few options, such as "Check for updates now", "About" and "start Update Manager". You are expected to design and implement the application.

I don't get why you should allow your users to update their OS(that is their GUI, their kernel, xorg, libc and other _core_ functionality). These components are already quite "great" and shouldn't need upgrading if that is your worry. Only in the case of some new device coming out and the kernel or xorg need to support it i can see the problem. This should happen very rarely though. I mean, why should you allow your OS to be upgraded by some lowly non-tech users. I don't know of many workplaces which allow their users to upgrade their windows versions for example...
You could always upgrade the OS every X years if needed.
If the boss wants his emplyees to be able to download whichever apps/games they want then ofcourse you could allow this, but this should only be allowed if said apps/games doesn't drag in new versions of xorg, kernel versions or other core functionality or its dependencies.
Just blacklist these in pacman.conf and make the file unwritable for the users...
This way you only need external repo for apps which doesn't install without user intervention.
Here i define "core functionality" as all the code responsible for giving a "working computer" as defined by the boss and you if he's not very IT. If you are worried about security and this is why you want a constantly updating machine then just connect all the machines to a router/firewall before they are allowed onto the net. That one could be an arch machine...
Also I haven't tried xfce in a long while but you should watch against giving "windows users/mac users" anything which isn't glitzy and full-featured, because if the users doesn't think the OS have all the functionality they "need" and they don't think it looks fancy enough they have a tendency to go back to whatever OS they came from or try to "upgrade" their own os... which might spell problems for you.
You know, never underestimate the ingeniousness of an idiot.
Just my 5 cents.
Last edited by test1000 (2010-06-25 00:13:42)

Pacman update & pacman-color

Similar Messages

Maybe you are looking for