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)

Similar Messages

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)

[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)

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

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)

Build pacman occurs test error on other architecture (sh4)

I was trying to build Archlinux on sh4 cpu by cross-compile.
But, I found it is very difficult for me.
So, I changed to another method, build it on sh4 directly (slow cpu & 256M ram).
After build several library, I've compiled pacman.
There are three unexpected fail when I run 'make check'.
How could I let it pass all test?
BTW, my sh4 environment is still messy, there contains STLinux,fedora,home-made packages.
Only a few library which is build following the PKGBUILD steps.
One of the bad thing, it is still bash 3.0.
Unexpected Passes:
Failed:
[FAIL] mode001 Rules: OK = 1 FAIL = 2 SKIP = 0
Check the mode of default files in a package
[FAIL] sign001 Rules: OK = 0 FAIL = 1 SKIP = 0
Add a bogus signature to a package DB
[FAIL] sync200 Rules: OK = 0 FAIL = 1 SKIP = 0
Synchronize the local database
Total = 264
Pass = 247 ( 93.56%)
Expected Fail = 14 ( 5.30%)
Unexpected Pass = 0 ( 0.00%)
Fail = 3 ( 1.14%)
================================================================================
Running 'sign001'
Add a bogus signature to a package DB
==> Generating test environment
==> Running test
==> Checking rules
[FAIL] PACMAN_RETCODE=0
==> Test result
FAIL
================================================================================
Running 'sync200'
Synchronize the local database
==> Generating test environment
==> Running test
==> Checking rules
[FAIL] PACMAN_RETCODE=0
==> Test result
FAIL

I suggest you follow this up on the pacman-dev list. I suspect that no-one has tried this before...
Provide the configure command and output, and the /tmp/tmp???????/var/log/pactest.log file after running the pactest manually. This should work...:
/pactest.py -p ../../src/pacman/pacman -t tests/ldconfig001.py --keep-root -d 2

[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-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)

Kdemod removed from pacman.conf but not from /var/lib/pacman

Hello all
I have been using kdemod repository for some time.
Since I use Gnome I have removed all my kde/qt applications and I have removed kdemod repository from pacman.conf
Is it normal to still have kdemod into /var/lib/pacman ?
Can I safely remove /var/lib/pacman/kdemod (not /var/lib/pacman of course) ?
Why pacman does not remove it when syncing if no more present in pacman.conf ?
Is it a bug ? a feature ?
Thank you for your help !
Cheers,
Chicha.

shining wrote:I think this has little interest, since the repo will be downloaded again on next -Sy anyway.
It's probably neither a bug, nor a feature, rather the lack of a feature, because checking that
some folders in /var/lib/pacman/ doesn't match a section in pacman.conf would require extra code.
Ooops I thought I checked for this hehe.
Are you sure pacman downloads the whole database everytime?
I just did an update:
yaourt -Sy
:: Synchronizing package databases...
testing is up to date
current is up to date
extra 270.5K 299.4K/s 00:00:01 [##################################################] 100%
community 291.4K 302.8K/s 00:00:01 [################################################] 100%
compiz-fusion is up to date
local database is up to date
If a repo is uptodate it doesn't download the database, so pacman must check that somehow.
Also, it show that to sync extra, 270.5K was transferred, is that the entire extra repo?
When I check the size of /var/lib/pacman/extra it's 5.7 Megs. Maybe the repo is compressed,
transferred, and then decompressed on each sync.
If that's the case, as you say my argument doesn't hold much water

[svn:bz-4.0.0_fixes] 20651: Some MBean tests needed flex.management. jmx stuff in the allow classes list for the class deserialization validator so adding it in on BlazeDS 4 .0.0_fixes.

Revision: 20651
Revision: 20651
Author:   [email protected]
Date:     2011-03-07 12:21:11 -0800 (Mon, 07 Mar 2011)
Log Message:
Some MBean tests needed flex.management.jmx stuff in the allow classes list for the class deserialization validator so adding it in on BlazeDS 4.0.0_fixes.
Modified Paths:
    blazeds/branches/4.0.0_fixes/qa/apps/qa-regress/WEB-INF/flex/services-config.mods.validat ors.xml

Thank you very much!
I cant believe this little comment has been so helpful!
But yes it is:
I explain, despite my efforts to find, googled it, forums, faqs, etc...
no where it mentionned the manifest.fm file is... INSIDE the .jar!
Your comment "a zip" made me attempt to open it with winrar, and I found a manifest.fm file inside!
So far I was editing the one at the "source" of my project and rebuilding it with netbeans.
I am going to try that now.
Actually.... :( no its mentionning my main class!
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.0
Created-By: 10.0-b19 (Sun Microsystems Inc.)
Main-class: courseworkjava3d.Simple3D
Class-Path:
X-COMMENT: Main-Class will be added automatically by buildWell I have no problems uploading you the .jar, it is for a coursework it is not a private project or whatever:
http://www.uploading.com/files/CM2LKWYU/BetaCourseworkJava3d_Final.jar.html
Oh and I felt on your comment "dont ask us" as if I was suppose to know... i'm a beginner, I did not know that! And I tried to give you so many infos so you dont lose your time if you want to help, especially as after my own research I found many, many results for this "main class" and I tried a few solutions!
Edited by: CupofTea on Apr 13, 2008 3:28 AM

[svn:bz-trunk] 20650: Some MBean tests needed flex.management. jmx stuff in the allow classes list for the class deserialization validator so adding it in on BlazeDS trunk .

Revision: 20650
Revision: 20650
Author:   [email protected]
Date:     2011-03-07 12:20:03 -0800 (Mon, 07 Mar 2011)
Log Message:
Some MBean tests needed flex.management.jmx stuff in the allow classes list for the class deserialization validator so adding it in on BlazeDS trunk.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/services-config.mods.validators.xml

Thank you very much!
I cant believe this little comment has been so helpful!
But yes it is:
I explain, despite my efforts to find, googled it, forums, faqs, etc...
no where it mentionned the manifest.fm file is... INSIDE the .jar!
Your comment "a zip" made me attempt to open it with winrar, and I found a manifest.fm file inside!
So far I was editing the one at the "source" of my project and rebuilding it with netbeans.
I am going to try that now.
Actually.... :( no its mentionning my main class!
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.0
Created-By: 10.0-b19 (Sun Microsystems Inc.)
Main-class: courseworkjava3d.Simple3D
Class-Path:
X-COMMENT: Main-Class will be added automatically by buildWell I have no problems uploading you the .jar, it is for a coursework it is not a private project or whatever:
http://www.uploading.com/files/CM2LKWYU/BetaCourseworkJava3d_Final.jar.html
Oh and I felt on your comment "dont ask us" as if I was suppose to know... i'm a beginner, I did not know that! And I tried to give you so many infos so you dont lose your time if you want to help, especially as after my own research I found many, many results for this "main class" and I tried a few solutions!
Edited by: CupofTea on Apr 13, 2008 3:28 AM

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

Similar Messages

Maybe you are looking for