Pacman-color depends on pacman 3.2

the title says it all, a user has to remove pacman-color in order to update to pacman 3.3.
EDIT 1:
hmm, I found that the AUR page on pacman-color has been updated and it says that it is compatible with the latest pacman 3.3 so I will try to install it again.
http://aur.archlinux.org/packages.php?ID=11827
EDIT 2:
I double checked and when using yaourt, it still thinks that pacman-color depends on pacman 3.2
EDIT 3:
confirmed yaourt is up to date, still having the same problem.
EDIT 4:
via #archlinux IRC I discovered that my configuration of yaourt was the heart of the problem, more precisely my using the archlinuxfr repository which is now out of date rather than going straight to the AUR.
I have since remedied this though, and also found that there is someone developing another program similar in function to yaourt since it is no longer being maintained, see the comments section here for more details.
http://aur.archlinux.org/packages.php?ID=11827
Last edited by panzeroceania (2009-08-05 21:40:41)

i had the same problem. i did:
$ sudo pacman -Syu
:: Synchronizing package databases...
core 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)
:: pacman-color: requires pacman=3.2.2
$ sudo pacman -R pacman-color
checking dependencies...
warning: /etc/pacman.d/color.conf saved as /etc/pacman.d/color.conf.pacsave
(1/1) removing pacman-color [#########################################################] 100%
$ sudo pacman -Syu
:: Synchronizing package databases...
core 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...
Targets (2): libfetch-2.25-1 pacman-3.3.0-3
Total Download Size: 0.61 MB
Total Installed Size: 2.05 MB
Proceed with installation? [Y/n]
y
(2/2) upgrading pacman [#########################################################] 100%
ryan ~ $ emerge pacman-color
resolving dependencies...
looking for inter-conflicts...
Targets (1): pacman-color-3.3.0-1
Total Download Size: 0.03 MB
Total Installed Size: 0.07 MB
Proceed with installation? [Y/n]
y
(1/1) installing pacman-color [#########################################################] 100%
Last edited by FlamingZebra90 (2009-08-27 17:07:09)

Similar Messages

Pacman upgrade fails because of unsatisfied pacman-color dependency *

Hello, my most recent attempt to run pacman -Suy results in pacman trying to update itslef and failing:
:: Synchronizing package databases...
core 35.4K 500.1K/s 00:00:00
[#####################] 100%
extra 453.0K 2.2M/s 00:00:00
[#####################] 100%
community 377.2K 2.2M/s 00: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...
error: failed to prepare transaction (could not satisfy dependencies)
:: pacman-color: requires pacman=3.3.3
Any idea how to fix this?
Last edited by .:B:. (2010-06-28 20:26:09)

There are a couple of threads about this.
1.Uninstall pacman-color
2. pacman -Syu
3. Reinstall pacman-color
4. Put the kettle on...
#edit too much detail...
Last edited by jasonwryan (2010-06-28 19:48:50)

Pacman-color(-testing) needs to depend on "pacman=${pkgver}"?

Hey,
So I've been thinking about this for some time now and I'd be interested in hearing other people's opinions about this. So my package pacman-color-testing currently depends on "pacman=${pkgver}" - meaning it requires the same version of pacman as the package itself - but the thing is: does it really need to?
I imagine keeping the pacman dependency in a single major version wouldn't produce any problems, eg. the current pacman-color(-testing) of 3.4.x would require this: depends=('pacman>=3.4' 'pacman<3.5'). This would also make updating easier.
At least the pacman change log here doesn't really show any "behavior compromising" changes between bug fix releases for pacman-color(-testing): http://projects.archlinux.org/pacman.git/tree/NEWS
But then what's other people's stance on this?
Last edited by algorythm (2011-03-08 15:53:21)

I assume you don't mean "sure, why wouldn't pacman-color* need to depend on "pacman=${pkgver}"" .
Last edited by algorythm (2011-03-09 14:05:12)

[SOLVED ]makepkg asking for pacman-color binary

After upgrading pacman to 4.1 I'm getting this error every time I run makepkg:
/usr/bin/makepkg -s -i
==> ERROR: Cannot find the pacman-color binary required for dependency operations.
Even if I try to use --nocolor:
/usr/bin/makepkg --nocolor -s -i
==> ERROR: Cannot find the pacman-color binary required for dependency operations.
I've tried enabling and disabling color options in both makepkg.conf and pacman.conf, and the error is still there.
Any clue on what could be going on and how to solve it?
Thank you in advance
Last edited by ethail (2013-04-01 23:01:32)

echo $PACMAN
pacman-color
I guess I've forgotten to edit some file that I changed when using pacman-color-testing from the AUR.
EDIT: Indeed, I forgot to edit my .zprofile that used to export PACMAN as pacman-color. Solved now
Thank you, Allan
Last edited by ethail (2013-04-01 23:02:14)

Yaourt suddenly asking for root password, pacman-color [NEVERMIND]

So just a few days ago I started getting the following whenever I try to install something from yaourt:
==> Continue building boxee-source ? [Y/n]
==> --------------------------------------
==>
==> Building and installing package
==> Install or build missing dependencies for boxee-source:
Password: <just to see what's up I type the wrong password...>
su: incorrect password
Password:
bash: pacman-color: command not found
Any ideas why yaourt is invoking su and trying to invoke pacman-color? I can't install anything from aur using yaourt anymore, it always ends up failing:
Password:
bash: pacman-color: command not found
==> WARNING: Your packages are saved in /tmp/yaourt-tmp-mgalgs/
==> WARNING: Following packages have not been installed:
db4.5
==> WARNING: Dependencies have been installed before the failure
==> Restart building python24 ? [y/N]
==> ---------------------------------
==>
==> WARNING: Following packages have not been installed:
python24
==> WARNING: Dependencies have been installed before the failure
==> Restart building boxee-source ? [y/N]
==> -------------------------------------
==>
==> WARNING: Following packages have not been installed:
boxee-source
(I'm showing boxee-source here, but the same thing happens with any aur package...)
thanks!
Last edited by mitch_feaster (2011-03-22 15:39:32)

Ouch, guess I'll just run along then... I don't remember enabling testing but I'll have to double-check.
su is being invoked before pacman, which is why I've done nothing more with it than try (unsuccessfully) to install it with yaourt... But I'll just be getting off y'all's front lawn now...

[Solved] pacman-color failed to install missing dependencies

Just upgraded my AUR packages and I get this error:
:: Starting AUR upgrade...
:: perl-class-load-xs 0.04-2 -> 0.06-1
AUR Targets (1): perl-class-load-xs
Proceed with installation? [Y/n] y
:: Edit perl-class-load-xs PKGBUILD? [Y/n] n
:: Building perl-class-load-xs package...
==> Making package: perl-class-load-xs 0.06-1 (Sat Nov 3 09:14:38 PDT 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
error: target not found: perl-test-without-module
==> ERROR: 'pacman-color' failed to install missing dependencies.
:: perl-class-load-xs cleaned
Any help appreciated.
Last edited by lagagnon (2012-11-04 03:07:33)

perl-test-without-module is in the AUR.
edit: build the package yourself in makepkg or use an aur helper.
Last edited by SS4 (2012-11-03 16:41:55)

[SOLVED] pacman-color base text is black

I would like the 'base' text (normal stuff, like the text telling you repos are up to date) in pacman-color to be grey, as I am going to be using a terminal emulator with a black background. Unfortunately, pacman-color seems bent on using a black font for its text. I can change most colors in /etc/pacman.d/color.conf, but not that. I tried adding a new line, 'Black = white' or similar, but it complains it doesn't know 'Black'.
Any help? Thanks!
Last edited by Ranguvar (2008-10-28 01:58:03)

Doesn't work
EDIT: Got it working, but I have no clue how. Just randomly started. Go figure. In case someone else comes along with the same problem, I think the fix happened when editing my .Xdefaults... here's part of mine to try and see if something fixes it.
xterm*background: black
xterm*foreground: light grey
xterm*cursorColor: navy
xterm*pointerColor: white
xterm*pointerColorBackground: black
xterm*faceName: Terminus
xterm*faceSize: 13
Last edited by Ranguvar (2008-10-28 01:57:54)

[SOLVED]yaourt fail pacman/-color when upgrade sudo to version 1.8.0-1

same sudoers:
with sudo-1.8.0-1:
[sl1pkn07@SpinFlo ~]$ yaourt -Syu
Contraseña:
You are not allowed to launch pacman-color with sudo
Please enter root password
with sudo-1.7.4.p6-1
[sl1pkn07@SpinFlo ~]$ yaourt -Syu
Contraseña:
:: Sincronizando las bases de datos de paquetes...
is pacman-color/pacman blacklisted?
greetings
EDIT: change title
Last edited by sl1pkn07 (2013-01-31 02:48:12)

sl1pkn07 wrote:
yes. pacman color/pacman works with sudo. but when using with yaourt, fails
[sl1pkn07@SpinFlo scripts]$ sudo pacman -Syu
Contraseña:
:: Sincronizando las bases de datos de paquetes...
^C
Interrupt signal received
[sl1pkn07@SpinFlo scripts]$ sudo pacman-color -Syu
:: Sincronizando las bases de datos de paquetes...
^C
Interrupt signal received
[sl1pkn07@SpinFlo scripts]$ yaourt -Syu
You are not allowed to launch pacman with sudo
Please enter root password
Contraseña:
[sl1pkn07@SpinFlo scripts]$ sudo nano /etc/yaourtrc (change between pacman and pacman-color)
[sl1pkn07@SpinFlo scripts]$ yaourt -Syu
You are not allowed to launch pacman-color with sudo
Please enter root password
Contraseña:
[sl1pkn07@SpinFlo scripts]$
it's the same for me too.. sudo pacman ok.. but yaourt ask for root password...

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

Pacman-color - ftp problems

Trying to get pacman-color installed but I'm having problems with things just grinding to a halt attempting to access ftp://ftp.archlinux.org/other/pacman/.... (which is the address in the PKGBUILD
Is there anything I can do to get around this?

Make sure the IP address you are getting for ftp.archlinux.org is 209.85.41.144 and not 209.85.41.145 which is currently broken.

So do you use pacman or something else like pacman-color/yaourt/tupac

I'm very sorry if this is not the place for such topic
Do you use the original pacman or modifications like pacman-color/yaourt/tupac/something-else?
I personally use pacman, thinking of trying yaourt maybe.

I only use pacman. In the past I've experimented with yaourt but never really liked it. I also tried powerpill but found that it was not useful often enough to keep around, because most of my pacman downloads are tiny.
EDIT: I'm such a flip-flop. I am now using both yaourt and powerpill again, in combination with a custom script found here.
Last edited by fflarex (2009-02-24 16:07:42)

AnyGantt: How to set different bar color depending on data value.

Need to have different colors for bars in a gantt resource chart.
The color depends on certain data value not included in the visible part of the chart, so it must be provided 'extra' for the chart in some way without beeing visible.
Have studied some examples but cannot figure out the mechanism for this, and the procedure to implement it.
Any ideas?
Apex 4.2.2
Regards
Per.

Hi Per,
You mention "+Among the samples I can see that it has been implemented, but not how.+" - in the Information region below the chart that Tony referred to (https://apex.oracle.com/pls/apex/f?p=36648:50) that I've stated the following:
"The elements of the Timeline region have been customized via the Chart Attributes page, using the following settings: *Custom Colors*: #000000,#00FF00,#0033FF"
So that's how I applied custom colours to that particular chart. However, that declarative option won't meet your requirements, where the colours you wish to apply are dependent on data not included in the chart series query. You mention "+Now, if I add another column to the statement I get a yellow error message telling that the statement is not valid.+". It is not possible to simply add an additional column to the chart series query. Each supported chart type expects the associated chart series query to use specific syntax - see About Creating SQL Queries for Charts in Chapter 10 of the APEX User's Guide, http://docs.oracle.com/cd/E37097_01/doc/doc.42/e35125/bldapp_chrt.htm#BCEIJJID.
So to answer your question "+How to add the new value if not providing another column to the graph?+", if you wish to customise your chart to that extent, then you will need to use custom XML. Depending on what exactly you're trying to achieve, this may require the generation of custom data for your chart. If you edit your chart, and take a look at the Custom XML region, you'll notice a substitution string, #DATA#, towards the end of the XML. When a chart is rendered, we use the chart series query to generate the necessary XML to represent the data on the chart, replacing the string #DATA# with the actual XML. The format of the data XML generated for gantt charts uses a bar style called "defaultStyle", and this handles the default appearance of the bars in the timeline region e.g.
<period resource_id="1" start="2009.03.21 00.00.00" end="2009.09.21 00.00.00" style="defaultStyle"/>You'll see that the 'style="defaultStyle" ' attribute of the data corresponds to a segment of XML outlining what that style is e.g.
<period_style name="defaultStyle">Now take a look at the Bar Style in Resource Project example in the AnyChart online documentation http://www.anychart.com/products/anygantt/docs/users-guide/bar-style.html#bar-style-application-resource-project. In that particular example, a number of different bar styles are used i.e.
<periods>
<period resource_id="server_1" start="2008.07.07" end="2008.07.8" style="Working" />
<period resource_id="server_1" start="2008.07.8" end="2008.07.12" style="Maintance" />If you need to add a different bar style to particular rows of data on your chart, then you'll need to add new bar style XML for each colour you wish to use in the Custom XML on the Chart Attributes page, and then you'll also need to generate the data XML yourself, applying the necessary bar style to the relevant row of data. I've got an example of how custom data can be generated for a Resource Gantt here e.g. https://apex.oracle.com/pls/apex/f?p=36648:73 but keep in mind that particular example doesn't demo adding different styles to the data...but it can certainly give you an idea of what's entailed in the generation of custom data for your chart.
I hope this helps.
Regards,
Hilary

Changing colors depending on output variable

Hi there,
I am pretty new to LabVIEW, using it for my dissertation at university. I looked for similar questions on this and other forums but can't seem to find an answer.
What I'm trying to do is change the color of a graphic depending on the value of another variable. I'm calculating the temperatures inside a gas turbine, and would like to represent the temperature changes graphically for better understanding. So I have output values for different temperatures, which change with mass flow rate of fuel into the engine. How can I make a graphic change it's colors depending on the value of temperature?
Thanks a lot,
Fabian

Do you mean something like this ? Run the VI and change the value of Thermometer.
Attachments:
Change BG of chart.vi ‏16 KB

Pacman-defrag [obsolete - use pacman-optimize]

After dp's discovery of a simple way to speed up pacman which can be found here I've come up with this little program. It should be pretty safe because it checks for a running instance of pacman before executing and locks pacman (2>/tmp/pacman.lck) during use so it won't corrupt files. I threw in the other options because I thought they might be usefull. A log will be created as needed in the /var/log directory as pacman-defrag.log.
Move the file into /usr/bin/ , chown it root, and chmod 755.
file and sums can also be found here
#!/bin/bash
## CHANGE THESE VALUES ONLY IF THE PROGRAM COMPLAINS TO ##
###### SHOULD BE UNIQUE AN MUST NOT EXIST ALREADY! ########
newtemp="/var/lib/new_temp/"
oldtemp="/var/lib/old_temp/"
ver='1.5'
RED="33[1;31m"
NORMAL="33[0;39m"
log="/var/log/pacman-defrag.log"
d=`date +"[%b %d %H:%M %Y]"`
smes="Successful database defrag."
fmes="ERROR: Unsuccessful database defrag, pacman lock detected."
wuser="You must be root user to run this program."
screenlog="New log file created as /var/log/pacman-defrag.log"
notargetmes="ERROR: Unsuccessful database defrag, database directory did not exist."
newtmpexistsmes="ERROR: Unsuccessful database defrag, temp target $newtemp already exists."
oldtmpexistsmes="ERROR: Unsuccessful database defrag, temp target $oldtemp already exists."
badmd5mes="ERROR: Unsuccessful database defrag, md5sums did not match. Old database restored."
usage() {
echo " pacman-defrag $ver"
echo
echo " pacman-defrag is a utility that safely defrags database"
echo " files in /var/lib/pacman for Arch Linux's package manager,"
echo " 'pacman'."
echo
echo " A log file will automatically created and can be found in"
echo " /var/log/ as 'pacman-defrag.log'."
echo
echo " usage: $0 [options]"
echo
echo " {-h --help}"
echo
echo " {-v --version}"
echo
echo " {-d --defrag} Defrags database safely by checking for"
echo " locks created by pacman while locking"
echo " itself from it so both can't run together."
echo " This should be your default option."
echo
echo " {-f --force} Force the defrag ignoring pacman lock. If"
echo " no lock is found, one will be created to"
echo " protect pacman. BE CAREFULL WITH THIS!"
echo
echo " {-r --rforce} Same as force except the lock will be"
echo " removed after use."
echo
exit 0
version() {
echo "version $ver"
exit 0
idcheck(){
[ `id -u` -ne 0 ] && {
echo "$wuser"
exit 1
check(){
if [ ! -d /var/lib/pacman ]; then
echo "Error: database directory does not exist."
echo "aborting."
smes=$notargetmes
logger
exit 1
fi
if [ -d $newtemp ]; then
echo "Error: $newtemp already exists. Please reset newtemp= near the top of"
echo "this script to a unique directory that does not already exist."
echo "aborting."
smes=$newtmpexistsmes
logger
exit 1
fi
if [ -d $oldtemp ]; then
echo "Error: $oldtemp already exists. Please reset oldtemp= near the top of"
echo "this script to a unique directory that does not already exist."
echo "aborting."
smes=$oldtmpexistsmes
logger
exit 1
fi
movecopy(){
echo
cd /var/lib
tar -cf old.tar pacman/
md5sum old.tar | sort > old.sums
cp -rp pacman/ $newtemp
mv -f pacman/ $oldtemp
mv -f $newtemp pacman/
echo -e "checking integrity... c"
tar -cf new.tar pacman/
md5sum new.tar | sort > new.sums
olddb=`cat old.sums | cut -d' ' -f 1`
newdb=`cat new.sums | cut -d' ' -f 1`
echo $olddb > olddb.sums
echo $newdb > newdb.sums
diff olddb.sums newdb.sums
if [ $? -ne 0 ]; then
echo "FAILED."
echo -e "restoring old databases... c"
rm -r pacman/
mv -f $oldtemp pacman/
smes=$badmd5mes
else
echo "OK."
##### UNCOMMENT TO SEE SUMS ####
#echo $olddb
#echo $newdb
echo -e "completing defrag... c"
rm -r $oldtemp
fi
rm -f old.tar
rm -f new.tar
rm -f old.sums
rm -f new.sums
rm -f olddb.sums
rm -f newdb.sums
logger() {
if [ -f $log ]; then
echo -e "Logging event... c"
echo -n "$d " >> $log
echo "$smes" >> $log
echo "done."
else
echo -n "$d " >> $log
echo "$smes" >> $log
echo "$screenlog"
fi
exit 0
defrag() {
idcheck
check
if [ -f "/tmp/pacman.lck" ]; then
echo -e "${RED}Pacman lock detected!${NORMAL}"
echo "If you are sure pacman is not being used, run this program again using -r."
echo "aborting."
smes=$fmes
else
2>/tmp/pacman.lck
movecopy
rm -f /tmp/pacman.lck
echo "done."
fi
logger
force() {
idcheck
check
if [ -f "/tmp/pacman.lck" ]; then
movecopy
else
2>/tmp/pacman.lck
movecopy
rm -f /tmp/pacman.lck
fi
logger
rforce() {
idcheck
check
if [ -f "/tmp/pacman.lck" ]; then
movecopy
rm -f /tmp/pacman.lck
else
2>/tmp/pacman.lck
movecopy
rm -f /tmp/pacman.lck
fi
echo "done."
logger
case $1 in
-h | --help) usage ;;
-d | --defrag) defrag ;;
-v | --version) version ;;
-f | --force) force ;;
-r | --rforce) rforce ;;
*) usage
exit 0
esac
# end of file

IceRAM wrote:The script has probably cached into memory all pacman files, that's why pacman is so responsitive. Try searching using pacman after a reboot. Compare times then.
After reboot it's still improved.
To start with, your pacman db is going to be around a similar spot on the hard drive. but over time as it changes, packages come and go and whatever, it gradually gets spread across the hard drive, with latter things ending up as far as the other end of the hard drive.
this causes the hard drive's head to have to whip back and forth between platters and all around the place.
the idea of this, is that it makes a copy, which is generally all together, or close together, so then the hard drives head doesnt have to go nuts everywhere, and it does make a difference
iphitus

Hi accidentally overwrote new pacman.conf with /etc/pacman.conf.pacnew

Hi
I accidentally overwrote etc/pacman.conf with the old /etc/pacman.conf.pacnew.
Pacman now appears to work but disregards the signing of packages.
Is there an copy of the pacman.conf from the upgrade around so I can merge
the two files. perhaps pacman.conf~, but no I think this is overwritten too.
Regardz
El Zorro

Hi Trilby,
it may be the mouldy oldy one as there is no reference to "SigLevel = Never" it does not seem to exist only "Architecture = auto"
Here is the current /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
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
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs
Trilby wrote:
The pacnew version includes everything for package signing. All you will have lost is any personal changes you have made.
The package signing lines are, however, commented out except for the "SigLevel = Never" line. Just read the instructions within the comments and uncomment the appropriate SigLevel line (and comment the "Never" line).
Last edited by elzorro (2012-01-21 06:31:50)

Pacman-color depends on pacman 3.2

Similar Messages

Maybe you are looking for