[SOLVED] aMule becomes SVN package

I like the idea, I've been compiling a Git for some time now and this would make things much easier.
some questions..
Is the stable release still going to feature?
if so, shouldn't this be named amule-svn?
How often is it going to be updated?
cheers
Last edited by gav616 (2010-10-15 21:43:05)

dartfira wrote:
After updated to the last SVN version i've that problem.
ArchLinux 2010.05 32bit
Kernel: 2.6.33.4
aMule SVN compiled with wxGTK2 v2.8.11 (Snapshot: rev. 10313-1)
I tries to start aMule from terminal then
Quote
[dartfira@myhost ~]$ amule
2010-10-14 09:47:26: Initialising aMule SVN compiled with wxGTK2 v2.8.11 (Snapshot: rev. 10310)
2010-10-14 09:47:26: Checking if there is an instance already running...
2010-10-14 09:47:26: No other instances are running.
2010-10-14 09:47:27: ListenSocket: Ok.
2010-10-14 09:47:27: Caricamento file incompleto da: /home/dartfira/Mule/Temp
2010-10-14 09:47:27: Tutti i PartFile caricati.
amule: xcb_io.c:140: dequeue_pending_request: Asserzione `req == dpy->xcb->pending_requests' fallita.
Abortito
not a place to report package bugs, please see http://forum.amule.org/

Similar Messages

Xfce4 packages to be replaced by xfce4-svn packages??

Dear Arch fellow users,
since a few days it seems impossible to to an pacman -Suy upgrade on my Arch i686 box with xfce4. It gives me the following result:
pacman -Suy
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies... done.
looking for inter-conflicts...
:: libxfce4util-svn conflicts with libxfce4util. Remove libxfce4util? [Y/n] y
:: libxfcegui4-svn conflicts with libxfcegui4. Remove libxfcegui4? [Y/n] y
:: libxfce4mcs-svn conflicts with libxfce4mcs. Remove libxfce4mcs? [Y/n] y
:: exo-svn conflicts with exo. Remove exo? [Y/n] y
:: xfce4-panel-svn conflicts with xfce4-panel. Remove xfce4-panel? [Y/n] y
:: thunar-svn conflicts with thunar. Remove thunar? [Y/n] y
done.
error: failed to prepare transaction (could not satisfy dependencies)
:: libxfcegui4 requires mousepad
:: libxfcegui4 requires xfce-mcs-manager
:: libxfcegui4 requires xfce-mcs-plugins
:: libxfcegui4 requires xfce-utils
:: libxfcegui4 requires xfce4-appfinder
:: libxfce4mcs requires xfce-mcs-manager
:: libxfce4mcs requires xfce-mcs-plugins
:: libxfce4mcs requires xfce-utils
:: xfce4-panel requires xfce4-mixer
:: xfce4-panel requires verve-plugin
:: xfce4-panel requires xfce4-battery-plugin
:: xfce4-panel requires xfce4-clipman-plugin
:: xfce4-panel requires xfce4-cpufreq-plugin
:: xfce4-panel requires xfce4-cpugraph-plugin
:: xfce4-panel requires xfce4-datetime-plugin
:: xfce4-panel requires xfce4-dict-plugin
:: xfce4-panel requires xfce4-diskperf-plugin
:: xfce4-panel requires xfce4-eyes-plugin
:: xfce4-panel requires xfce4-fsguard-plugin
:: xfce4-panel requires xfce4-genmon-plugin
:: xfce4-panel requires xfce4-mailwatch-plugin
:: xfce4-panel requires xfce4-messenger-plugin
:: xfce4-panel requires xfce4-mount-plugin
:: xfce4-panel requires xfce4-mpc-plugin
:: xfce4-panel requires xfce4-netload-plugin
:: xfce4-panel requires xfce4-notes-plugin
:: xfce4-panel requires xfce4-quicklauncher-plugin
:: xfce4-panel requires xfce4-screenshooter-plugin
:: xfce4-panel requires xfce4-sensors-plugin
:: xfce4-panel requires xfce4-smartbookmark-plugin
:: xfce4-panel requires xfce4-systemload-plugin
:: xfce4-panel requires xfce4-timer-plugin
:: xfce4-panel requires xfce4-wavelan-plugin
:: xfce4-panel requires xfce4-weather-plugin
:: xfce4-panel requires xfce4-xfapplet-plugin
:: xfce4-panel requires xfce4-xkb-plugin
:: xfce4-panel requires xfce4-xmms-plugin
:: thunar requires squeeze
:: thunar requires xfdesktop
:: thunar requires thunar-archive-plugin
:: thunar requires thunar-media-tags-plugin
:: thunar requires thunar-volman
Is this a temporary phenomenon, or are we supposed to switch to xfce4-svn? If yes, is xfce4-svn stable enough for a reliable workhorse?
And additionally how could one upgrade to xfce4-svn since I get an error message error: failed to prepare transaction (could not satisfy dependencies)
I hope someone will help me out. Just a week a ago I gathered sufficient courage to turn my bloated and slowly running Ubuntu laptop (for professional use) into revitalized Arch box

Thanks for your quick replies guys!
I think you could successfully participate in the contest "the members who are responding faster than their shadows.....":D
Cerebral you might be right. Also I few days ago I followed the advice of Tardo in the following thread http://bbs.archlinux.org/viewtopic.php?id=34566 and I installed the xfburn-svn-25797-1-i686.pkg.tar.gz in my quest for a to get a lightweight burner with pacman -U. How do I get rid of it? Just pacman -R xfburn-svn-25797-1-i686.pkg.tar.gz ?? I installed that package since neither graveman (hangs) nor hacburn (can not detect my device) are working. I like k3b but not the bunch and MBs of dependencies.
I will review the AUR and ABS wiki page on how to get rid of the xfburn-svn package....:P
Thanks again for your quick responses!;)

Desktop folder has become a "package" mac os x v 10.7.2

My Desktop folder has become a "package"; each time I click this "folder" it launchs the aplication "Terminal".

Lynn, try to relax. There is nothing about the upgrade itself that would cause those problems.
In here, you'll find tons of problems, it is the ER for 10.7 problems. Most users upgrade with no issues at all and don't ever come here.
Usually, problems are pre-exisisting and are exacerbated by the update process. I know that isn't what you want to hear but it's true. Did you run Disk Utility > Repair Disk before updating?
Have you tried starting up in Safe Mode and test?
Do you have any existing backup? Are they WD drives?
There are new items on the Dock in 10.7 and if you don't want them just drag them off and "poof" them.

[SOLVED] How to download package source files ? they become HTML

Hi. dumb one I'm afraid. I don't want to install ABS.
OK, so I'm not talking about AUR here, rather simply going to:
http://www.archlinux.org/packages/
Over on the right under, Package Actions
Source Files / View Changes
I click Source Files, i right click on the list of files amd get html downloaded and not the source files.
I like to build things myself on ocassion.
how to get files without using ABS!?
thank you!
Last edited by yvonney (2012-03-19 16:09:19)

You don't have to check out the whole abs tree:
* https://wiki.archlinux.org/index.php/Dw … s_with_ABS
* https://wiki.archlinux.org/index.php/Ar … d_ABS_tree
[karol@black ~]$ sudo abs community/dwm
==> Starting ABS sync...
receiving file list ... done
community/
community/dwm/
community/dwm/PKGBUILD
community/dwm/config.h
community/dwm/dwm.desktop
community/dwm/dwm.install
sent 172 bytes received 7885 bytes 2302.00 bytes/sec
total size is 7523 speedup is 0.93
[karol@black ~]$ du -sh /var/abs/
40K /var/abs/
The installed size of abs package is 120,00 KiB (on my 32-bit Arch).
The files it pulls (e.g. for dwm) are the same you can get manually, so abs is as minimal as it gets.
You call 'under 5 gigs' ultra-minimal. My full (and IMHO a bit bloated) system is about 3 GB.
Last edited by karol (2012-03-19 13:45:55)

[SOLVED]How to search package name only when using yaourt

I often install a AUR package by yaourt term, but it does not only search terms in package name but also package description, since there are so much packages in AUR, it produce many pages of items, and it can not support more to page one screenful at a time, It
become difficult to get the right choice,
Thank you in advance!
Last edited by netawater (2013-06-14 00:47:06)

Hey, that's one thing I actually know how to do with regexes! All package descriptions have some spaces at their beginning, the package names themselves have not, so you can just use inverted grepping like so:
$ pacman -Ss test | grep -v '^ '
core/perl 5.10.1-5 (base)
extra/fprint_demo 0.4-2 (fprint)
extra/ghc 6.12.1-2
extra/haskell-hunit 1.2.2.1-1
extra/haskell-quickcheck 2.1.0.3-1
extra/junit 4.7-1
extra/kdesdk-kpartloader 4.4.0-1 (kde kdesdk)
extra/libxtst 1.1.0-1
extra/memtest86+ 4.00-1
extra/mono-tools 2.6.1-1
extra/openoffice-base 3.2.0-1
extra/openoffice-base-beta 3.2.0_ooo320_m12-1
extra/perl-test-pod 1.41-1
extra/python-nose 0.11.1-1
extra/qemu-kvm 0.12.2-1
extra/testdisk 6.11.3-2
extra/unarj 2.63a-2
extra/xbill 2.1-6
xyne-any/reflector 5.0-2
community/buildbot 0.7.11p3-1
community/cppunit 1.12.1-1
community/cxxtest 3.10.1-3
community/dsniff 2.4b1-15
community/gtk-aurora-engine 1.5.1-1
community/gtkperf 0.40-3
community/java-jdom 1.1.1-1
community/lib32-libxtst 1.1.0-1 (lib32)
community/perl-test-base 0.59-1
community/perl-test-deep 0.106-1
community/perl-test-differences 0.500-1
community/perl-test-exception 0.29-1
community/perl-test-manifest 1.23-1
community/perl-test-mockobject 1.09-1
community/perl-test-nowarnings 1.01-1
community/perl-test-tester 0.107-1
community/perl-test-warn 0.21-2
community/phoronix-test-suite 2.4.0-1
community/pmtools 20100123-1
community/reflector 5.0-2
community/stress 1.0.0-2
community/typespeed 0.6.5-2
arch-games/mangler-snapshot 1.1.20100116-3
arch-games/ultimatestunts 0.7.5.1-1
This still shows the repos and the versions (nothing cut wouldn't be able to handle though). It works fine with pacman as you just saw, I can't guarantee for yaourt as I don't have it installed.
Edit: Hm… I just realized that this still displays the results where 'test' only occured in the package description. Give me some time to figure this out.
Edit 2: Another grep for 'test' would solve it:
$ pacman -Ss test | grep -v '^ ' | grep test
extra/memtest86+ 4.00-1
extra/perl-test-pod 1.41-1
extra/testdisk 6.11.3-2
community/cxxtest 3.10.1-3
community/perl-test-base 0.59-1
community/perl-test-deep 0.106-1
community/perl-test-differences 0.500-1
community/perl-test-exception 0.29-1
community/perl-test-manifest 1.23-1
community/perl-test-mockobject 1.09-1
community/perl-test-nowarnings 1.01-1
community/perl-test-tester 0.107-1
community/perl-test-warn 0.21-2
community/phoronix-test-suite 2.4.0-1
arch-games/ultimatestunts 0.7.5.1-1
Still, it's not that pretty to write the same thing twice. If you really want to do it like this, I suggest you make it a function in your ~/.${SHELL}rc.
Last edited by Runiq (2010-02-27 08:36:11)

How to solve problem with Installer Package for itunes

Hi! I'm attempting to upadte itunes so I can get the latest software for my iphone. It's a 3GS. Every time when ready to instal it says I have a problem with the installer package - something is missing. What can I do to solve this?

Repair your Apple software update.
Go to START/ALL PROGRAMS/Apple Software Update. If it offers you a newer version of Apple Software Update, do it but Deselect any other software offered at the same time. Once done, try another iTunes install
If you don't find ASU, go to Control Panel:
START > CONTROL PANEL >
Add n Remove Programs(XP)
Programs n Features(Win7/Vista)
highlight ASU and click CHANGE then REPAIR,

How to solve this error 'This package is using an app name that hasn't been reserved for this app: "Matest"

i already reserved app name as Ma_Test. But only one error showing "This package is using an app name that hasn't been reserved for this app: "Matest". how to solve?

Hello,
You need to make sure both names match exactly

[SOLVED] Make Pacman cache packages installed with -U

When installing a package with -U, pacman doesn't cache packages as it does when installing with -S. Is there a way to change this behavior?
I read somewhere that specifying the package's full path and prepending "file://", as in "pacman -U file://path/to/package.pkg.tar.xz", but this often complains of an "invalid or corrupted package (PGP signature)".
How can I make pacman always copy installed packages to the cache?
MOD EDIT: change 'closed' to 'solved' in title to avoid confusion
Last edited by fukawi2 (2013-07-06 13:09:21)

You can't. This has been discussed on the bugtracker several times.
https://bugs.archlinux.org/task/35699
https://bugs.archlinux.org/task/31243
https://bugs.archlinux.org/task/15143
https://bugs.archlinux.org/task/18012
If you're building the packages yourself with makepkg, you can set PKGDEST to your cache in makepkg.conf. Otherwise you could write a small pacman wrapper that copies the package after installing it.

[SOLVED] Confused about development packages

To build an embedded linux image using minifs utility, I need to install some development packages. The packages listed in the tutorial are named for Debian based distros, with the "-dev" suffix. Some of the listed packages are: libz-dev, libelf-dev, libelfg0-dev, libncurses-dev, etc.
I can't find these packages, and I'm a bit confused. I have read that these packages in Arch Linux have different suffixes denpending on the origin (-cvs, -git, etc.), but I can't find any packages with that suffixes. For example for ncurses:
$ pacman -Ss ncurses
core/ncurses 5.9-3 [instalado]
System V Release 4.0 curses emulation library
extra/cmus 2.4.3-1
A very feature-rich ncurses-based music player
extra/finch 2.10.1-1
A ncurses-based messaging client
extra/moc 20110528-5
An ncurses console audio player with support for the mp3, ogg, and wave
formats
extra/naim 0.11.8.3.2-2
An ncurses AOL Instant Messenger and IRC client.
extra/ncmpc 0.20-1
A ncurses (command line) interface for MPD
community/echat 0.04beta1-3
vypress compatible ncurses chat (can work without server)
community/ekg2 0.3.1-2
ncurses based Jabber, Gadu-Gadu, Tlen and IRC client
community/ncdu 1.8-1
Disk usage analyzer with an ncurses interface
community/rtorrent 0.8.9-2
Ncurses BitTorrent client based on libTorrent
community/ruby-ncurses 1.3.1-3
Module for interactive text console applications (ncurses)
community/sniffit 0.3.7.beta-11
very good packet sniffer for unix with ncurses interactive mode.
community/vifm 0.7.2-1
Ncurses based file manager with vi like keybindings
community/yacpi 3.0.1-3
ncurses-based acpi monitor.
No ncurses-cvs, ncurses-git, ncurses-svn or the like is found. How can I find development packages?
Last edited by doragasu (2012-03-09 22:38:03)

doragasu wrote:So in Arch, packages include not only binaries + resources, they also include header files? If I install for example ncurses, also header files for ncurses get installed?
headers, pkg-config, everything in one package, that is required for a compilation. we keep stuff simple
Last edited by wonder (2012-03-09 22:37:46)

Does anyone have a gmpc-svn package for me?

I'm trying to build gmpc-svn but the current configure script is broken.
Who's got a recent package for gmpc-svn I can download? Thanks a lot in advance.

Check the AUR for gmpc-plugins-svn!
When I first ran gmpc-svn, I got a cool track listing of the current album under "Information" but that doesn't work anymore. Any ideas?
[edit]
Found it: gmpc shouldn't be in mini or playlist mode. Just regular gmpc.
[/edit]

[SOLVED] python2-parted (debian package)

Would really appreciate it if you could bring this to Arch. I've tried
deb2targz but got confused about the proper Arch directory structure. I
don't know enough about Python to do it justice.
Download: http://packages.ubuntu.com/quantal/python-parted
Wasted a day trying to line up the deps for Arch Linux ARM to virtualize,
these Debian packages are getting in the way, to put it mildly.
Last edited by atweiden (2013-03-27 20:17:21)

I did see pyparted, but after investigating python-parted
on packages.ubuntu.com, it appeared that python-parted depends upon
pyparted, which in Ubuntu land means who knows how or where or in
what weird ways Ubuntu expects python-parted to be there. In any case,
linaro-image-tools fails for a plethora of reasons and there's no way
I can ascertain whether pyparted made a difference.
Words of advice, If you're trying to follow the MDN guide to virtualize
ARM, you have to virtualize Ubuntu first.
I'm marking this thread solved: I bought a development board.

[SOLVED] First crack at packaging

After the first instance ever on Arch where a (admittedly very new) program has to be done by source, and not on the AUR. It got me wanting to know how to package things, although nothing so complex as the program I'm after yet, I want to crawl before walking.
I decided to have a crack at a smaller program - so chose a rouge like game I hadn't yet seen in the AUR - not that it matters even if it was.
I paste the PKGBUILD I made for it below - it's not finished, but the instructions to make and build the package are there:
I took a lot of "inspiration" from the ASCIIPortal PKGBUILD because, like this game "AQuestTooFar", in the source, there is no "make install" part of the process, only a "make" and then an executable is made that you run straight from wherever the source and everything was downloaded to. Theres also no Package() part. But it works and makes a package nonetheless. However after intallation with pacman, I get an error when I try and launch it from terminal, about not being able to load one of the files in the "Data" folder, which I've checked it included and is present in my package.
Hopefully some of you would be able to offer any feedback and advice, and any thoughts on this error. I'm a complete newb to doing things from source and then packaging them - Oh package managers, how you spoil us =].
Cheers,
Ben.
# Maintainer: Ben Ward <[email protected]>
pkgname=AQuestTooFar
pkgver=1.3
pkgrel=1
pkgdesc="A rouge-like dungeon crawling game, using text."
arch=(any)
url="http://www.randomstuff.org.uk/~geoffrey/roguelikes/aquesttoofar.html"
license=()
depends=()
makedepends=('')
optdepends=('')
source=(http://www.randomstuff.org.uk/~geoffrey/roguelikes/AQuestTooFar1.3-091010.zip)
md5sums=('68545729914de7c7549b8d5ece13f061') #generate with 'makepkg -g'
build() {
cd "${srcdir}/AQuestTooFar1.3-091010"
make
install -d $pkgdir/opt/AQuestTooFar
install -D AQuestTooFar $pkgdir/opt/AQuestTooFar/
install -D readme.txt $pkgdir/usr/share/doc/AQuestTooFar/README
cp -r Build Data $pkgdir/opt/AQuestTooFar
mkdir $pkgdir/usr/bin
ln -s $pkgdir/opt/AQuestTooFar/AQuestTooFar $pkgdir/usr/bin/AQuestTooFar
chmod -x $pkgdir/opt/AQuestTooFar/*/*
Last edited by Ben9250 (2011-03-06 15:09:44)

Ben9250 wrote:Is there a certain situation then when ('any') is ok to be used or should one always try to put either i686 or x86_64 or both?
Yes, for example if your build only contains python code, then it runs on every platform which python runs on. That's when you can put arch=(any) into the PKGBUILD, because it runs everywhere.
Ben9250 wrote:
"install -Dm755 ${_realname} $pkgdir/opt/${_realname}/${_realname}"
"install -Dm644 readme.txt ${pkgdir}/usr/share/doc/${_realname}/README"
With these such lines, the -Dm755 part for example, it looks to me as though this is setting permissions, rather in a chmod kindof manner?
It's always good to set the permissions directly. Only that way you can be sure that the permissions will be right.
Ben9250 wrote:
for i in Data/*;do install -Dm644 "$i" ${pkgdir}/opt/${_realname}/"$i";done
This line is a loop, which loops around for every file in the Data folder, and copies them to the opt directory, essentially getting rid of the cp line?
Unfortunately something like install -Dm644 Data/* ${pkgdir}/opt/${_realname}/ doesn't work, so I solved it with a loop. But this line is basically doing the same as
cp -r Data/* ${pkgdir}/opt/${_realname}/
chmod 644 ${pkgdir}/opt/${_realname}/Data/*
but as I wrote before, the PKGBUILD I posted is how I would do it and I don't like to use cp in a build function, it's a matter of personal taste I guess.
Ben9250 wrote:
echo "#!/bin/sh - forgive me but I don't know about this line, echo is something to do with printing things, and theres someting going on with a shebang and sh, so something to do with bash?
"cd /opt/${_realname}"
"./${_realname}" > ${pkgdir}/usr/bin/${_realname}"
"chmod +x ${pkgdir}/usr/bin/${_realname}"
This looks to me like the answer to the softlinking?
Yes. If you use a softlink in /usr/bin which directs to /opt/${_realname}, it's kind of like the binary file is in /usr/bin. The binary expects the data directory in the same directory, but it's in /opt/${_realname}. That's why the ln -s method doesn't work. The shell script however first does cd into /opt/${_realname} and then executes the binary. That way everything's fine, because the data directory is in the same directory.
Last edited by Army (2011-03-04 13:18:30)

[SOLVED] Cannot install any package thru pacman

I cannot install any package thru pacman
when i try to install the package with pacman -S,
I started getting error when my sytem crashed and i have to forcefully switch off my laptop through power button
after that when i install anything from pacman i got following error:
[tan@ARCH ~]$ sudo pacman -S shotwell
Password:
warning: shotwell-0.9.3-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets (1): shotwell-0.9.3-1
Total Download Size: 0.00 MB
Total Installed Size: 9.12 MB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [##########] 100%
(1/1) checking for file conflicts [##########] 100%
(1/1) upgrading shotwell [##########] 100%
ldconfig: File /usr/lib/libgexiv2.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgexiv2.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgexiv2.so is empty, not checked.
ldconfig: File /usr/lib/libraw.so is empty, not checked.
ldconfig: File /usr/lib/libraw.so.2 is empty, not checked.
ldconfig: File /usr/lib/libraw_r.so.2 is empty, not checked.
ldconfig: File /usr/lib/libraw.so.2.0.1 is empty, not checked.
ldconfig: File /usr/lib/libraw_r.so is empty, not checked.
ldconfig: File /usr/lib/libraw_r.so.2.0.1 is empty, not checked.
Thanks in advance
Last edited by tan (2011-05-29 05:45:28)

Thank God, everything is fixed now:
First, I deleted all these files, then i follows the following procedure
1. For libgexiv2 file i upgraded 'xorg-server, xorg-xinit, xorg-utils, xorg-server-utils' from pacman
# pacman -S xorg-server xorg-xinit xorg-utils xorg-server-utils
2. For libraw file i upgraded 'libraw' from pacman
# pacman -S libraw
There will be some conflicting files
After deleting some conflicting files it solves the problem and restore all the 'lib' file.

[solved] (yaourt) zoneminder-svn problem

Hello,
I'm trying to build zoneminder-svn through yaourt and I am failing to build ffmpeg-svn (dep).
The error I get after issuing "yaourt -S zoneminder-svn" is as follows:
loading package data...
error: './ffmpeg-svn-18717-1-i686.pkg.tar.gz': cannot open package file
=> WARNING: Your package is saved in /tmp/yaourt-tmp-root/ffmpeg-svn-18717-1-i686.pkg.tar.gz
cp: cannot stat `../ffmpeg-svn-18717-1-i686.pkg.tar.gz': No such file or directory
=> WARNING: Unable to copy ffmpeg-svn-1-i686.pkg.tar.gz to /tmp/yaourt-tmp-root / directory
I know I shouldn't be building this as root but it was just to check it wasnt anything permission problem based
Misc. details about my target system:
uname -a
Linux CHIAKI 2.6.30-ARCH #1 PREMPT Sat Jul 4 11:13:08 UTC 2009 i686 Intel(R) Pentium(R) 4 CPU 2.66GHz GenuineIntel GNU/Linux
Thanks in advance!
Mike
Last edited by DrMikeDuke (2009-07-13 12:40:32)

djszapi wrote:However it works for me, Have you tried it without from svn, just with zoneminder package from AUR? Can that work ? I don't like version controlled package, if a non version controlled is available.
alas no, this does not help
Anyone?
tried running it again as just "yaourt -S zoneminder"
==> Tidying install...
-> Compressing man pages...
-> Stripping debugging symbols from binaries and libraries...
==> Creating package...
-> Generating .PKGINFO file...
-> Compressing package...
==> Finished making: ffmpeg-svn 19416-1 i686 (Mon Jul 13 04:01:20 WST 2009)
==> Continue installing ffmpeg-svn? [Y/n]
==> [v]iew package contents [c]heck package with namcap
==> ----------------------------------------------
==>y
loading package data...
error: './ffmpeg-svn-18717-1-i686.pkg.tar.gz': cannot open package file
==> WARNING: Your package is saved in /tmp/yaourt-tmp-root/ffmpeg-svn-18717-1-i686.pkg.tar.gz
cp: cannot stat `./ffmpeg-svn-18717-1-i686.pkg.tar.gz': No such file or directory
==> WARNING: Unable to copy ffmpeg-svn-1-i686.pkg.tar.gz to /tmp/yaourt-tmp-root/ directory
If you like this package, please install aurvote
and vote for its inclusion/keeping in [community]
[root@CHIAKI mike]#
Last edited by DrMikeDuke (2009-07-12 22:00:06)

[SOLVED] Pacman not updating packages

When I try to upgrade using
pacman -Syu
I get this:
error: failed to commit transaction (conflicting files)
pam: /sbin/mkhomedir_helper exists in filesystem
pam: /sbin/pam_tally exists in filesystem
pam: /sbin/pam_tally2 exists in filesystem
pam: /sbin/pam_timestamp_check exists in filesystem
pam: /sbin/unix_chkpwd exists in filesystem
pam: /sbin/unix_update exists in filesystem
pam: /usr/include/security/_pam_compat.h exists in filesystem
pam: /usr/include/security/_pam_macros.h exists in filesystem
pam: /usr/include/security/_pam_types.h exists in filesystem
pam: /usr/include/security/pam_appl.h exists in filesystem
pam: /usr/include/security/pam_client.h exists in filesystem
pam: /usr/include/security/pam_ext.h exists in filesystem
pam: /usr/include/security/pam_filter.h exists in filesystem
pam: /usr/include/security/pam_misc.h exists in filesystem
pam: /usr/include/security/pam_modules.h exists in filesystem
pam: /usr/include/security/pam_modutil.h exists in filesystem
pam: /usr/lib/libpam.so exists in filesystem
pam: /usr/lib/libpam.so.0 exists in filesystem
pam: /usr/lib/libpam.so.0.83.1 exists in filesystem
pam: /usr/lib/libpam_misc.so exists in filesystem
pam: /usr/lib/libpam_misc.so.0 exists in filesystem
pam: /usr/lib/libpam_misc.so.0.82.0 exists in filesystem
pam: /usr/lib/libpamc.so exists in filesystem
pam: /usr/lib/libpamc.so.0 exists in filesystem
pam: /usr/lib/libpamc.so.0.82.1 exists in filesystem
pam: /usr/lib/security/pam_access.so exists in filesystem
pam: /usr/lib/security/pam_cracklib.so exists in filesystem
pam: /usr/lib/security/pam_debug.so exists in filesystem
pam: /usr/lib/security/pam_deny.so exists in filesystem
pam: /usr/lib/security/pam_echo.so exists in filesystem
pam: /usr/lib/security/pam_env.so exists in filesystem
pam: /usr/lib/security/pam_exec.so exists in filesystem
pam: /usr/lib/security/pam_faildelay.so exists in filesystem
pam: /usr/lib/security/pam_filter.so exists in filesystem
pam: /usr/lib/security/pam_filter/upperLOWER exists in filesystem
pam: /usr/lib/security/pam_ftp.so exists in filesystem
pam: /usr/lib/security/pam_group.so exists in filesystem
pam: /usr/lib/security/pam_issue.so exists in filesystem
pam: /usr/lib/security/pam_keyinit.so exists in filesystem
pam: /usr/lib/security/pam_lastlog.so exists in filesystem
pam: /usr/lib/security/pam_limits.so exists in filesystem
pam: /usr/lib/security/pam_listfile.so exists in filesystem
pam: /usr/lib/security/pam_localuser.so exists in filesystem
pam: /usr/lib/security/pam_loginuid.so exists in filesystem
pam: /usr/lib/security/pam_mail.so exists in filesystem
pam: /usr/lib/security/pam_mkhomedir.so exists in filesystem
pam: /usr/lib/security/pam_motd.so exists in filesystem
pam: /usr/lib/security/pam_namespace.so exists in filesystem
pam: /usr/lib/security/pam_nologin.so exists in filesystem
pam: /usr/lib/security/pam_permit.so exists in filesystem
pam: /usr/lib/security/pam_pwhistory.so exists in filesystem
pam: /usr/lib/security/pam_rhosts.so exists in filesystem
pam: /usr/lib/security/pam_rootok.so exists in filesystem
pam: /usr/lib/security/pam_securetty.so exists in filesystem
pam: /usr/lib/security/pam_shells.so exists in filesystem
pam: /usr/lib/security/pam_stress.so exists in filesystem
pam: /usr/lib/security/pam_succeed_if.so exists in filesystem
pam: /usr/lib/security/pam_tally.so exists in filesystem
pam: /usr/lib/security/pam_tally2.so exists in filesystem
pam: /usr/lib/security/pam_time.so exists in filesystem
pam: /usr/lib/security/pam_timestamp.so exists in filesystem
pam: /usr/lib/security/pam_umask.so exists in filesystem
pam: /usr/lib/security/pam_unix.so exists in filesystem
pam: /usr/lib/security/pam_userdb.so exists in filesystem
pam: /usr/lib/security/pam_warn.so exists in filesystem
pam: /usr/lib/security/pam_wheel.so exists in filesystem
pam: /usr/lib/security/pam_xauth.so exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_ADG.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_ADG.txt exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_MWG.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_MWG.txt exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_SAG.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_SAG.txt exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-author.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-copyright.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-example.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-files.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-glossary.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-interface-by-app-expected.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-interface-of-app-expected.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-interface-programming-notes.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-interface.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-introduction-description.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-introduction-synopsis.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-introduction.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-libpam-functions.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-libpam_misc.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-overview.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-porting.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security-conv-function.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security-library-calls.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security-resources.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security-service-name.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security-user-identity.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-see-also.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/draft-morgan-pam-current.txt exists in filesystem
pam: /usr/share/doc/Linux-PAM/index.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-author.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-copyright.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-example.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-by-module-item.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-by-module-other.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-by-module.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module-acct.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module-auth.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module-chauthtok.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module-overview.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module-session.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-introduction-description.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-introduction-synopsis.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-introduction.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-also.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-options.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-programming-libs.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-programming-sec.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-programming-syslog.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-programming.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/rfc86.0.txt exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-author.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-configuration-directory.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-configuration-example.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-configuration-file.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-configuration.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-copyright.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-introduction.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-module-reference.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-overview.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_access.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_cracklib.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_debug.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_deny.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_echo.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_env.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_exec.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_faildelay.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_filter.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_ftp.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_group.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_issue.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_keyinit.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_lastlog.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_limits.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_listfile.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_localuser.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_loginuid.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_mail.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_mkhomedir.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_motd.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_namespace.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_nologin.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_permit.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_pwhistory.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_rhosts.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_rootok.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_securetty.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_selinux.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_shells.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_succeed_if.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_tally.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_tally2.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_time.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_timestamp.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_umask.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_unix.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_userdb.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_warn.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_wheel.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_xauth.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-security-issues-other.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-security-issues-wrong.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-security-issues.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-see-also.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-text-conventions.html exists in filesystem
pam: /usr/share/locale/ar/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/as/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/bn_IN/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ca/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/cs/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/da/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/de/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/es/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/fi/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/fr/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/gu/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/he/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/hi/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/hu/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/it/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ja/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/kk/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/km/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/kn/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ko/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ml/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/mr/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ms/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/nb/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/nl/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/or/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/pa/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/pl/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/pt/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/pt_BR/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ru/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/si/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/sk/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/sr/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/sr@latin/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/sv/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ta/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/te/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/tr/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/uk/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/vi/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/zh_CN/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/zh_TW/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/zu/LC_MESSAGES/Linux-PAM.mo exists in filesystem
Errors occurred, no packages were upgraded.
I tried googling up something but I can't find anything.
What should I do? Thanks
EDIT: Solved. Sorry for spamming the forum like this before trying with pacman man pages.
I just did
pacman -Syu -f
and it worked.
Last edited by TheGatorade (2013-02-07 14:42:17)

That might have solved that particular problem, but you may have more. Getting that amount of 'exists in filesystem' errors in one go suggests to me that your pacman database has been corrupted. Read this if you get more problems like this: https://wiki.archlinux.org/index.php/Ho … l_database
You should avoid using the -f flag, it could result in a broken system.

[SOLVED] aMule becomes SVN package

Similar Messages

Maybe you are looking for