[SOLVED] package upgrade fails for python2-qt

After doing
pacman -Syuv
, I get:
error: failed to commit transaction (conflicting files)
python2-qt: /usr/lib/python2.7/site-packages/PyQt4/Qt.so exists in filesystem
... snip a whole lot more...
python2-qt: /usr/share/sip/phonon/volumeslider.sip exists in filesystem
/usr/lib/python3.1/site-packages/PyQt4/Qsci.so exists in both 'qscintilla' and 'python-qscintilla'
Errors occurred, no packages were upgraded.
Any ideas what the problem can be and how to deal with it??
Thanks in advance,
Theo.
Last edited by vri (2011-01-21 10:25:13)

Similar issue here : after upgrading I get :
error: failed to commit transaction (conflicting files)
python-qscintilla: /usr/lib/python3.1/site-packages/PyQt4/Qsci.so exists in filesystem
Apparently 3 packages (qscintilla and the python and python2 bindings) install the same file. IMHO File should only be installed by qscintilla ... :-)

Similar Messages

[SOLVED]Full upgrade fails after new install

Hello,
Please note before reading that I know about the recent changes with the /lib symlink to /usr/lib and the filesystem (I read the home page).
After a fresh install, I try to upgrade the system :
pacman -Syy && pacman -Syu : it asks for pacman update, I say yes.
pacman -S pacman : fails because of glibc
pacman -S pacman --ignore glibc : fails, won't upgrade because glibc it's a dependency of pacman
pacman -Syu : say no to pacman upgrade, fails because of glibc and filesystem
pacman -Syu --ignore glibc --ignore fliesystem : upgrade almost nothing because most of the packages (~400M) need glibc
I can't upgrade anything at the end...
Thanks for any help
Last edited by John0000 (2012-07-19 14:52:17)

If either of this steps does not work (e.g. due to dependency version issues, file conflicts in /lib), refer to this G U I D E for more detailed instructions on performing this upgrade.
Did you read this guide?
There is thread about it also: https://bbs.archlinux.org/viewtopic.php?id=144620
And Allan wrote a blog entry about upgrading from core installation: http://allanmcrae.com/2012/07/updating- … e-install/
BTW as Pres suggested go with the net-install, core installation was always kind of a fallback for me and I had to do this just once because of network troubles. It just doesn't make much sense to do core installation if there is no holdback because with first pacman -Syu you'll end up downloading the same amount of data as if you would do a clean net-install, and it's faster and you probably won't get conflicts accumulated from year or so.
Last edited by masteryod (2012-07-19 14:38:38)

[solved] Upgrade failing for a package called device-mapper

Hi All,
I am using archlinux in a VirtualBox to get used to it. Now, I tried to upgrade (after a month or so) with following command
pacman -Syu
I get following errors
error: failed to commit transaction (invalid or corrupted package)
device-mapper-1.02.31-1-i686.pkg.tar.gz is invalid or corrupted
Errors occurred, no packages were upgraded
Any help is welcome.
regards,
rangalo
Last edited by rangalo (2009-04-22 09:32:48)

Hi,
Thanks for the quick response... I am given the choice to remove the package but it still complains about it being corrupted..
I also deleted it manually and running the update again gives following.
:: File device-mapper-1.02.31-1-i686.pkg.tar.gz is corrupted. Do you want to delete it? [Y/n] Y
error: failed to commit transaction (invalid or corrupted package)
device-mapper-1.02.31-1-i686.pkg.tar.gz is invalid or corrupted
Errors occurred, no packages were upgraded.
Last edited by rangalo (2009-04-21 14:32:35)

[solved] System upgrade fails - catalyst-libgl related

I've been having trouble upgrading my system over the last few days. This is what I get:
sudo powerpill -f -Syyu
:: Synchronising package databases...
catalyst 1.5K 1163.9K/s 00:00:00 [------------------------------------------------------------------------------------------] 100%
core 35.5K 135.3K/s 00:00:00 [------------------------------------------------------------------------------------------] 100%
extra 451.3K 122.7K/s 00:00:04 [------------------------------------------------------------------------------------------] 100%
community 375.4K 123.0K/s 00:00:03 [------------------------------------------------------------------------------------------] 100%
:: Starting full system upgrade...
:: Replace kernel26-firmware with core/linux-firmware? [Y/n] y
resolving dependencies...
looking for inter-conflicts...
:: xf86-input-acecad conflicts with xorg-server. Remove xorg-server? [Y/n] y
:: libgl conflicts with catalyst. Remove catalyst? [Y/n] y
error: failed to prepare transaction (could not satisfy dependencies)
:: lib32-catalyst-utils: requires catalyst>=10.5
If I try to remove lib32-catalyst-utils to do the upgrade, I get:
powerpill -R catalyst lib32-catalyst-utils
Password:
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: bin32-google-earth: requires lib32-libgl
:: lib32-mesa: requires lib32-libgl
:: mesa: requires libgl
:: mplayer: requires libgl
:: qt: requires libgl
:: stellarium: requires libgl
:: wxgtk: requires libgl
:: xorg-server: requires libgl
:: xorg-utils: requires libgl
Any thoughts?
Last edited by Henry Flower (2010-06-22 21:13:15)

Hmm. One problem solved, one to go. I'd missed the moving of the catalyst repo to the new address; updating the repo got me to
The following packages will be downloaded:
[catalyst]
catalyst-10.6-2 [16.10 MiB]
lib32-catalyst-utils-10.6-1 [7.13 MiB]
[extra]
boost-1.43.0-1 [6.97 MiB]
boost-libs-1.43.0-1 [2.23 MiB]
xorg-server-1.8.1.902-1 [1.82 MiB]
:: Number of Packages: 5
:: Total Download Size: 34.24 MiB
:: Total Installed Size: 243.51 MiB
:: Proceed with download? [Y/n] y
Unfortunately, then
:: Starting full system upgrade...
:: Replace kernel26-firmware with core/linux-firmware? [Y/n] y
resolving dependencies...
warning: dependency cycle detected:
warning: xorg-server will be installed before its catalyst dependency
looking for inter-conflicts...
warning: removing 'libgl' from target list because it conflicts with 'catalyst'
error: failed to prepare transaction (could not satisfy dependencies)
:: intel-dri: requires libgl=7.8.2
:: mach64-dri: requires libgl=7.8.2
:: mga-dri: requires libgl=7.8.2
:: r128-dri: requires libgl=7.8.2
:: savage-dri: requires libgl=7.8.2
:: sis-dri: requires libgl=7.8.2
:: tdfx-dri: requires libgl=7.8.2
I came across a similar problem with nvidia rather than catalyst: http://bbs.archlinux.org/viewtopic.php?id=99307 , but I don't know how to apply the solution there ('Uninstall the graphics drivers that you do not need') - are there any here that I don't need?
Last edited by Henry Flower (2010-06-22 20:25:43)

[Solved] Dovecot upgrade failed due to file conflicts

yaourt -Syu failed this morning do to file conflicts with dovecot. Here is the output:
:: Starting full system upgrade...
warning: iscan: local (2.15.0.3-1) is newer than archlinuxfr (2.8.0-3)
resolving dependencies...
looking for inter-conflicts...
Targets (10): libcups-1.3.10-1 cups-1.3.10-1 libmysqlclient-5.1.34-1 dovecot-1.1.14-1
ffmpegthumbnailer-1.5.0-1 mysql-clients-5.1.34-1 mysql-5.1.34-1 recordproto-1.13.2-2
renderproto-0.9.3-2 subversion-1.6.1-3
Total Download Size: 51.88 MB
Total Installed Size: 148.31 MB
Proceed with installation? [Y/n]
:: Retrieving packages from extra...
libcups-1.3.10-1-x86_64 185.2K 106.8K/s 00:00:02 [#########################################################] 100%
cups-1.3.10-1-x86_64 3.0M 121.0K/s 00:00:26 [#########################################################] 100%
libmysqlclient-5.1.... 12.2M 120.9K/s 00:01:44 [#########################################################] 100%
dovecot-1.1.14-1-x86_64 3.2M 120.2K/s 00:00:28 [#########################################################] 100%
mysql-clients-5.1.3... 278.2K 122.2K/s 00:00:02 [#########################################################] 100%
mysql-5.1.34-1-x86_64 25.9M 122.4K/s 00:03:36 [#########################################################] 100%
recordproto-1.13.2-... 4.0K 226.0K/s 00:00:00 [#########################################################] 100%
renderproto-0.9.3-2... 16.7K 86.4K/s 00:00:00 [#########################################################] 100%
subversion-1.6.1-3-... 6.9M 118.3K/s 00:01:00 [#########################################################] 100%
:: Retrieving packages from community...
ffmpegthumbnailer-1... 64.9K 119.1K/s 00:00:01 [#########################################################] 100%
checking package integrity...
(10/10) checking for file conflicts [#########################################################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
dovecot: /usr/lib/dovecot/imap exists in filesystem
dovecot: /usr/lib/dovecot/pop3 exists in filesystem
Errors occurred, no packages were upgraded.
Should I remove /usr/lib/dovecot/imap and /usr/libdovecot/pop3 and continue the upgrade, or is there a problem with a package?
Jay
Last edited by jt512 (2009-04-18 17:32:31)

Abelian wrote:
http://www.archlinux.org/news/444/
yaourt -Syuf should do it
next time don't do it again.
just pacman -Sf package and then pacman -Su

[SOLVED] jruby upgrade fails: /dev/fd error

Hi, when I try to upgrade jruby (pacaur -y jruby) I get the following error:
/dev/fd/63: line 18: syntax error: unexpected end of file
AUR Targets (1): jruby
Proceed with installation? [Y/n]
error: failed to commit transaction (conflicting files)
jruby: /opt/jruby/lib/ruby/gems/shared/cache/rake-10.0.3.gem exists in filesystem # a bunch of these for various files
Errors occurred, no packages were upgraded.
==> WARNING: Failed to install built package(s).
:: jruby cleaned
I ran pacman -Sc to clean out old packages, since the / filesystem was 97% full. Still got the same error.
as root, ls -l /dev/fd/* gives:
ls: cannot access /dev/fd/255: No such file or directory
ls: cannot access /dev/fd/3: No such file or directory
lrwx------ 1 root root 64 Feb 23 13:42 /dev/fd/0 -> /dev/pts/3
lrwx------ 1 root root 64 Feb 23 13:42 /dev/fd/1 -> /dev/pts/3
lrwx------ 1 root root 64 Feb 23 13:42 /dev/fd/2 -> /dev/pts/3
Any idea what's going on here?
Last edited by bebopson (2013-02-24 15:26:20)

This looks like a pacaur bug, due to the weird looking PKGBUILD. I guess the pacaur maintainer will have a look at it as soon as possible.
In the meantime, use makepkg (pacaur -de jruby && cd /tmp/pacaur-blabla/jruby && makepkg -si)
Edit: pacaur-git should now be working as expected.
Last edited by Spyhawk (2013-02-23 19:07:08)

[Solved] system upgrade fails with util-linux/eject conflict

I backed everything up, then deleted the fontconfig links and updated fontconfig, which worked properly. Then I did "pacman -Syu" and got this:
[root@myhost ~]# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
warning: dependency cycle detected:
warning: systemd will be installed before its dbus-core dependency
looking for inter-conflicts...
:: util-linux and eject are in conflict. Remove eject? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: util-linux and eject are in conflict
[root@myhost ~]#
Looks like two distinct problems. Note that I already have the /lib thing taken care of (turning it into a link), in a previous update. The forum searches I have done about this issue did not yield much.
Last edited by PaulBx1 (2012-10-25 19:01:28)

PaulBx1 wrote:
Upgrading that infrequently is unlikely to work well in the long term.
Hell, I thought that was upgrading frequently. One of the reasons I'm on linux is because I don't have to get upgrades every hour as on Windows. "If it ain't broke, don't fix it." I ran a hell of a lot longer on Puppy linux without upgrades. Also, I backup before every upgrade, and then have to fiddle with pacnew files and all the rest, so the result is burning half a day at least on upgrades. I sure don't want to increase the frequency of that.
Arch is a rolling release so it changes basically every day. Updating every week or two is perfectly fine, but updating every couple months brigs you at odds with what Arch is about.
One of the reasons you may not want to use Arch is when you don't want to or can't spend time on the updates.
PaulBx1 wrote:The choice of defaults should (in my opinion) be decided by the needs of the unsophisticated user (such as myself), of which there are many more than the other type. Sophisticated users can intelligently decide between "y" and "n" because they know what is going on. Unsophisticated users just cross their fingers and hope the defaults work for them.
Arch is for experienced users and pacman doesn't do e.g. cleaning up - that's left to the user. pacman can surely help with it: 'pacman 'Qdt'.
It may feel unintuitive, but that's how it is.

[Solved] pacman upgrade fail

When I try to upgrade pacman I get the following:
gordiegii@Ion-Arch ~]$ sudo pacman -S pacman
Password:
resolving dependencies...
looking for inter-conflicts...
Targets (1): pacman-4.0.3-1
Total Installed Size: 3.54 MiB
Proceed with installation? [Y/n]
(1/1) checking package integrity [###################################################] 100%
(1/1) loading package files [###################################################] 100%
(1/1) checking for file conflicts [###################################################] 100%
error: failed to commit transaction (conflicting files)
pacman: /usr/bin/cleanupdelta exists in filesystem
pacman: /usr/bin/makepkg exists in filesystem
pacman: /usr/bin/pacman exists in filesystem
pacman: /usr/bin/pacman-db-upgrade exists in filesystem
pacman: /usr/bin/pacman-key exists in filesystem
pacman: /usr/bin/pacman-optimize exists in filesystem
pacman: /usr/bin/pacsort exists in filesystem
pacman: /usr/bin/pactree exists in filesystem
pacman: /usr/bin/pkgdelta exists in filesystem
pacman: /usr/bin/rankmirrors exists in filesystem
pacman: /usr/bin/repo-add exists in filesystem
pacman: /usr/bin/repo-elephant exists in filesystem
pacman: /usr/bin/repo-remove exists in filesystem
pacman: /usr/bin/testdb exists in filesystem
pacman: /usr/bin/testpkg exists in filesystem
pacman: /usr/bin/vercmp exists in filesystem
pacman: /usr/include/alpm.h exists in filesystem
pacman: /usr/include/alpm_list.h exists in filesystem
pacman: /usr/lib/libalpm.a exists in filesystem
pacman: /usr/lib/libalpm.so exists in filesystem
pacman: /usr/lib/libalpm.so.7 exists in filesystem
pacman: /usr/share/locale/ca/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/ca/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/ca/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/cs/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/cs/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/cs/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/da/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/da/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/da/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/de/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/de/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/de/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/el/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/el/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/el/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/en_GB/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/en_GB/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/en_GB/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/es/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/es/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/es/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/fi/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/fi/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/fi/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/fr/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/fr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/fr/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/hu/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/hu/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/hu/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/it/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/it/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/it/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/kk/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/kk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/kk/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/lt/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/lt/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/lt/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/nb/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/nb/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/nb/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/pl/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/pl/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/pl/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/pt/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/pt/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/pt/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/pt_BR/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/pt_BR/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/pt_BR/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/ro/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/ro/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/ro/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/ru/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/ru/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/ru/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/sk/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/sk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/sk/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/sr/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/sr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/sr/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/sr@latin/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/sr@latin/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/sr@latin/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/sv/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/sv/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/sv/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/tr/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/tr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/tr/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/uk/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/uk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/uk/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/zh_CN/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/zh_CN/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/zh_CN/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/zh_TW/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/zh_TW/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/zh_TW/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/man/man3/libalpm.3.gz exists in filesystem
pacman: /usr/share/man/man5/PKGBUILD.5.gz exists in filesystem
pacman: /usr/share/man/man5/makepkg.conf.5.gz exists in filesystem
pacman: /usr/share/man/man5/pacman.conf.5.gz exists in filesystem
pacman: /usr/share/man/man8/makepkg.8.gz exists in filesystem
pacman: /usr/share/man/man8/pacman-key.8.gz exists in filesystem
pacman: /usr/share/man/man8/pacman.8.gz exists in filesystem
pacman: /usr/share/man/man8/pkgdelta.8.gz exists in filesystem
pacman: /usr/share/man/man8/repo-add.8.gz exists in filesystem
pacman: /usr/share/man/man8/repo-remove.8.gz exists in filesystem
pacman: /usr/share/man/man8/vercmp.8.gz exists in filesystem
pacman: /usr/share/pacman/ChangeLog.proto exists in filesystem
pacman: /usr/share/pacman/PKGBUILD-split.proto exists in filesystem
pacman: /usr/share/pacman/PKGBUILD.proto exists in filesystem
pacman: /usr/share/pacman/proto.install exists in filesystem
pacman: /usr/share/zsh/site-functions/_pacman exists in filesystem
Errors occurred, no packages were upgraded.
[gordiegii@Ion-Arch ~]$
Has anybody seen this or have any idea how to fix it?
Should I just delete all these files?
I was getting a gcc / gcc-libs error before but reinstalling gcc as per other forum help fixed that.
Last edited by GordieGii (2012-04-29 15:29:26)

@Gcool: I did a quick search and could not find anything that matched my symptoms. The only things I found that seemed to apply were the gcc / gcc-libs issue which I resolved and merging my pacman.conf.pacnew file into pacman.conf file (only two non-comments were new and they didn't seem related).
Perhaps I can't assess the applicability of a post to my symptoms.
@karol: I did -Syu, as I always do, but this time I got this:
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n]
I tried both 'Yes' and 'no' and both failed. 'No' took much longer because it had to download a couple hundred packages (I have been trying to resolve this myself for over a week and the list keeps getting longer) before failing so I switched to just pacman.
Pacman was in the list of packages and I couldn't figure out how to exclude it to see if the others would update. Reinstalling gcc worked.
[gordiegii@Ion-Arch man]$ stat -c %s $(find /var/lib/pacman/local -name "pacman-4*")/files
0
[gordiegii@Ion-Arch man]$
Please pardon my newbieness, I came from Ubuntu when GnomeBloat became too much for my Intel ATOM and am still learning the Arch way.

[Solved] Package Preparation Failed

Alright, the issue I'm having is that when I select packages during the installation I get an error, "pacman preparation failed check /dev/tty7 for errors". At first I thought it was a network problem; but, I can ping www.google.com and everything else on the network seems fine. Any help is really appreciated, thanks!
I'm trying to do a net installation on a 320gb wd SATA hdd. I can provide any other info you require as well.
Edit: I apologize, I went back to check the error and it installed fine this morning. The only thing different was that I installed over an Ubuntu partition instead of an OpenSuse one.
Last edited by Shazzam6999 (2010-05-11 16:15:54)

I get an error, "pacman preparation failed. check /dev/tty7 for errors"
did you?

Portege R400 - Firmware upgrade fails for 3G card

During the Firmwareupgrade of the embedded 3G Card(Expedite EU870D) in my Protege R400 I have a power fail. On next start I can't countinue with the upgrade. The Card don't work anymore.
The Modem and the COM Ports I can't see in the Device Manger. Is there a solution for that Mistake? Thanks for help!
Pumbkin

Why you do the firmware update?
You should do this only if the Vodafone SIM card is not working properly!
I found this info which pop ups before running a firmware upgrade!
+Cautions in the FW Update:+
+Please be sure to read this carefully before upgrading the FW.+
+1. FW Upgrade is not needed when Vodafone SIM card is working properly under customers environment. Run the FW upgrade only when Vodafone SIM card is not detected. Please note that the FW is no longer revertible to the prior state once upgraded.+
+2. This upgrade tool is applicable for the following models with built-in 3G module:+
+ Portege R400+
+ Portege R500+
+ Tecra M9+
+3. Please exit 3G communication and close the Connection Utility before running the FW upgrade.+
+4. Close all the applications before running the FW upgrade. Please DO NOT launch any application during the upgrade process.+
+5. Please make sure to use an AC adaptor to power the computer during the FW upgrade process. Power failure during the upgrade process may lead to 3G modem failures.+
+6. Please DO NOT Suspend/Hibernation/Shut Down the computer during the FW upgrade process. Doing so may lead to 3G mode+
So please firstly these points before you would try to upgrade the firmware!

[SOLVED] Pacman upgrade failed because of gcc-libs

I have the multilib version of gcc installed in my 64 bit system. Ten minutes ago I tried to upgrade with pacman -Syu and I got:
:: I seguenti pacchetti dovrebbero essere aggiornati prima :
pacman
:: Vuoi annullare l'operazione corrente
:: e aggiornare adesso questi pacchetti? [S/n]
risoluzione delle dipendenze in corso...
ricerca dei conflitti in corso...
:: gcc-libs e gcc-libs-multilib vanno in conflitto. Vuoi rimuovere gcc-libs-multilib? [s/N] n
errore: sono stati rilevati dei conflitti irrisolvibili
errore: impossibile eseguire l'operazione richiesta (dipendenze in conflitto)
:: gcc-libs e gcc-libs-multilib vanno in conflitto
It is in italian, but basically it complains about a conflict between the installed gcc-libs-multilib and the needed gcc-libs. gcc-libs-multilib provides gcc-libs, so why this kind of error? I thought my mirror could be out of sync but I get the same error also using mirrors.kernel.org.
Am I doing something wrong?
Last edited by snack (2012-02-18 17:30:59)

I did mean 'search the forums':
* https://bbs.archlinux.org/viewtopic.php?pid=1045658
* https://bbs.archlinux.org/viewtopic.php?pid=1049681
* https://bbs.archlinux.org/viewtopic.php?pid=1057624
* https://bbs.archlinux.org/viewtopic.php?pid=1054861
* https://bbs.archlinux.org/viewtopic.php?pid=1057459
* https://bbs.archlinux.org/viewtopic.php?id=134397

Firmware upgrade failed, printer now say i has firmware version 0. attention light lights up

Hey all
I had a problem printing a pdf on my mac, and then tried to upgrade my mac driver and printer firmware.
But the firmware upgrade failed for some unknown reason. And now the printer just have the ready and attentions lights on constantly.
I have tried to restart and reset the printer many times, and tried the HP firmware upgrade utility several times, with no luck. It just say it was "failed to upgrade"
Any idea what to do ??
My printer is a HP Laserjet Pro CP1025nw
Thanks
Jan

Hello Jan
It definitely sounds like the firmware update failed. Firmware is like a devices Operating System. Without it, it can't do much. This is backed by the "failed" message and that your printer reports it has version 0.
The printer will need to be serviced. Please call HP Phone Support at 1-800-474-6836.
Don't forgot to say thanks by giving "Kudos" to those that help solve your problems.
When a solution is found please mark the post that solves your issue.

Calling ALL Experts...SSIS Package keep failing in Debug Mode..SQL 2005

Hello everyone,
I just want to thank you in advance for all the help that you can give today.
I just started at a new Company, as a junior DBA, the previous person left. Before that person left he created a lot of SSIS packages and
turn them into jobs basically to refresh many different tables on the SQL server. The datas are being import from another datasource, which is why the SSIS packages was created so we can bring the datas over to SQL side. Whenever I want to create a new
SSIS Package for a new job, I always get the same failure as below...
"Error: 0xC0047062 at Data Flow Task, Source - Query [1]: System.OverflowException: Arithmetic operation resulted in an overflow.
at System.Data.Odbc.OdbcStatementHandle.RowCount(SQLLEN& rowCount)
at System.Data.Odbc.OdbcDataReader.GetRowCount()
at System.Data.Odbc.OdbcDataReader.FirstResult()
at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader, Object[] methodArguments,
SQL_API odbcApiMethod)
at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader)
at System.Data.Odbc.OdbcCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Odbc.OdbcCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PreExecute()
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPreExecute(IDTSManagedComponentWrapper90 wrapper)
Error: 0xC004701A at Data Flow Task, DTS.Pipeline: component "Source - Query" (1) failed the pre-execute phase and returned error
code 0x80131516.
Information: 0x40043009 at Data Flow Task, DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at Data Flow Task, DTS.Pipeline: "component "Destination - GLCGLDS" (103)" wrote 0 rows.
Task failed: Data Flow Task
SSIS package "SSIS_GLCGLDS_GL.dtsx" finished: Failure.
The program '[16836] SSIS_GLCGLDS_GL.dtsx: DTS' has exited with code 0 (0x0)."
All the SSIS packages are failing for me, not just the one I created, even the ones that were working
before, the ones that were created by the previous person, I just went to Start Debugging and it would failed at the same exact stage
Below are the exact steps that I do to create the SSIS Package (based on the notes from previous person)
1. right click on SSIS Package and select sql server import and export wizard and click next
2. Select data source as .Net framework Data Provide for ODBC
3. Input Datasource, and driver as: TS ODBC Multi – Tier Driver
4. Choose destination as Microsoft OlE DB Provide for SQL Server
5. Write a basic select statement.
6. Click edit Mappings
7. Here's the important part... I am ABLE to preview the DATA.
8. Click ok  next  finished
9. Click debug start debugging
10. The preparation SQL task will be green, but the Data Flow Task will failed everytime for me.
If anyone has any suggestion please let me know, b/c I have try every possible ways and out of luck, and I don't want to explain to my boss
I don't know how to do it or how the previous person does it without any failures.
TL

Below are the exact steps that I do to create the SSIS
Package (based on the notes from previous person)
1. right click on SSIS Package and select sql server import and export wizard and click
next
2. Select data source as .Net framework Data Provide for ODBC
3. Input Datasource, and driver as: TS ODBC Multi – Tier Driver
4. Choose destination as Microsoft OlE DB Provide for SQL Server
5. Write a basic select statement. (select * from tableA)
6. Click edit Mappings to modify few column with their data type
7. Next -> Here's the important part... when I clicked on Preview Data, I am ABLE to
preview the DATA.
Finished.

No package upgrades for 7 days [solved]

Hello,
I don't know if this is a problem but there hasn't been any package updates available for 7 days.
That's pretty rare for an Arch system isn't it?
I don't get any error messages only this:
Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
Changing mirrors has no effect.
Last edited by new2arch (2009-11-27 12:19:35)

new2arch wrote:
bernarcher wrote:Try another mirror. There were several upgrades since.
That did the trick. Can't believe my main three mirrors were outdated.
Thanks.
https://users.archlinux.de/~gerbra/mirrorcheck.html

[Solved] latest filesystem upgrade failed

During last system upgrade ( pacman -Syu )，when upgrading filesystem-2011.08-1,
the system hang for a while, then pacman exit with some segfault error
I tried to fix it by typing ` pacman -Syu ` again, then got another error when upgrading linux-3.0.2-1
ERROR: file not found: `/etc/modprobe.d/usb-load-ehci-first.conf'
and filesystem is not in the upgrade package list, so I tried
sudo pacman -S filesystem
but I got some file confilct error
warning: filesystem-2011.08-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
Targets (1): filesystem-2011.08-1
Total Download Size: 0.00 MB
Total Installed Size: 0.06 MB
checking package integrity...
checking for file conflicts...
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
filesystem: /etc/crypttab exists in filesystem
filesystem: /etc/fstab exists in filesystem
filesystem: /etc/group exists in filesystem
filesystem: /etc/gshadow exists in filesystem
filesystem: /etc/host.conf exists in filesystem
filesystem: /etc/hosts exists in filesystem
filesystem: /etc/issue exists in filesystem
filesystem: /etc/ld.so.conf exists in filesystem
filesystem: /etc/motd exists in filesystem
filesystem: /etc/nsswitch.conf exists in filesystem
filesystem: /etc/passwd exists in filesystem
filesystem: /etc/profile exists in filesystem
filesystem: /etc/resolv.conf exists in filesystem
filesystem: /etc/securetty exists in filesystem
filesystem: /etc/shadow exists in filesystem
filesystem: /etc/shells exists in filesystem
Errors occurred, no packages were upgraded.
after search the forum, I found a post last year
https://bbs.archlinux.org/viewtopic.php?pid=833711
I only have the file " install " in /var/lib/pacman/local/filesystem-2011.08-1/
ls -l /var/lib/pacman/local/filesystem-2011.08-1/
total 4.0K
-rw-r--r-- 1 root root 1.6K Aug 10 07:41 install
I checked another machine which also installed Arch Linux,
it's package number is filesystem-2011.04-1
ls -l /var/lib/pacman/local/filesystem-2011.04-1/
total 12
-rw-r--r-- 1 root root 287 Jul 23 12:49 desc
-rw-r--r-- 1 root root 1804 Jul 23 12:23 files
-rw-r--r-- 1 root root 1623 Apr 8 18:08 install
Should I just copy the " desc " and " files " to my computer, then run `pacman -Syu` again
or
Upgrade that machine's filesystem to 2011.08-1, then copy the files to my computer to fix it ?
( I am afraid of upgrade error again)
Thank you
Last edited by lefthaha (2011-08-20 16:38:24)

I just upgraded filesystem to 2011.08-1 on my VM
then copyed the " desc, files " under /var/lib/pacman/local/filesystem-2011.08-1/
to my computer, and reinstall filesystem and kernel
$ sudo pacman -S filesystem --dbonly
$ sudo pacman -S filesystem
Running 'pacman -S filesystem'
warning: /etc/fstab installed as /etc/fstab.pacnew
warning: /etc/group installed as /etc/group.pacnew
warning: /etc/hosts installed as /etc/hosts.pacnew
warning: /etc/passwd installed as /etc/passwd.pacnew
warning: /etc/resolv.conf installed as /etc/resolv.conf.pacnew
warning: /etc/shells installed as /etc/shells.pacnew
warning: /etc/gshadow installed as /etc/gshadow.pacnew
warning: /etc/shadow installed as /etc/shadow.pacnew
upgraded filesystem (2011.08-1 -> 2011.08-1)
$ sudo pacman -S linux
after edited /etc/fstab, reboot the computer
During booting I got some filesystem error warning
system automaticlly checked and fixed those errors on root partition and reboot again
Then I can boot into X now
in /var/log/error.log I found something similar to previous booting error
Aug 19 20:39:42 MyHost kernel: [473315.923933] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:39:42 MyHost kernel: [473315.923939] ata1.00: BMDMA stat 0x65
Aug 19 20:39:42 MyHost kernel: [473315.923944] ata1.00: failed command: READ DMA EXT
Aug 19 20:39:42 MyHost kernel: [473315.923954] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:39:42 MyHost kernel: [473315.923955] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:39:42 MyHost kernel: [473315.923960] ata1.00: status: { DRDY ERR }
Aug 19 20:39:42 MyHost kernel: [473315.923963] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473321.025032] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:40:13 MyHost kernel: [473321.025038] ata1.00: BMDMA stat 0x65
Aug 19 20:40:13 MyHost kernel: [473321.025044] ata1.00: failed command: READ DMA EXT
Aug 19 20:40:13 MyHost kernel: [473321.025053] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:40:13 MyHost kernel: [473321.025055] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:40:13 MyHost kernel: [473321.025059] ata1.00: status: { DRDY ERR }
Aug 19 20:40:13 MyHost kernel: [473321.025062] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473328.558325] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:40:13 MyHost kernel: [473328.558331] ata1.00: BMDMA stat 0x65
Aug 19 20:40:13 MyHost kernel: [473328.558337] ata1.00: failed command: READ DMA EXT
Aug 19 20:40:13 MyHost kernel: [473328.558346] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:40:13 MyHost kernel: [473328.558348] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:40:13 MyHost kernel: [473328.558352] ata1.00: status: { DRDY ERR }
Aug 19 20:40:13 MyHost kernel: [473328.558355] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473333.355772] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:40:13 MyHost kernel: [473333.355779] ata1.00: BMDMA stat 0x65
Aug 19 20:40:13 MyHost kernel: [473333.355784] ata1.00: failed command: READ DMA EXT
Aug 19 20:40:13 MyHost kernel: [473333.355794] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:40:13 MyHost kernel: [473333.355796] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:40:13 MyHost kernel: [473333.355800] ata1.00: status: { DRDY ERR }
Aug 19 20:40:13 MyHost kernel: [473333.355802] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473338.984884] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:40:13 MyHost kernel: [473338.984891] ata1.00: BMDMA stat 0x65
Aug 19 20:40:13 MyHost kernel: [473338.984896] ata1.00: failed command: READ DMA EXT
Aug 19 20:40:13 MyHost kernel: [473338.984905] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:40:13 MyHost kernel: [473338.984907] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:40:13 MyHost kernel: [473338.984911] ata1.00: status: { DRDY ERR }
Aug 19 20:40:13 MyHost kernel: [473338.984914] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473345.947035] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:40:13 MyHost kernel: [473345.947042] ata1.00: BMDMA stat 0x65
Aug 19 20:40:13 MyHost kernel: [473345.947047] ata1.00: failed command: READ DMA EXT
Aug 19 20:40:13 MyHost kernel: [473345.947056] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:40:13 MyHost kernel: [473345.947058] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:40:13 MyHost kernel: [473345.947062] ata1.00: status: { DRDY ERR }
Aug 19 20:40:13 MyHost kernel: [473345.947065] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473345.980986] end_request: I/O error, dev sda, sector 12395474
after searching on the web, I found that maybe an old harmless problem related to kernel ?
https://bbs.archlinux.org/viewtopic.php?pid=293179
also found an error in /var/log/daemon.log
Failed to activate service 'org.freedesktop.Avahi': timed out
there is already a post about it, but not having a conclusion yet
https://bbs.archlinux.org/viewtopic.php?id=124485
Every things seen to work fine now
After few more test and reboot, I would mark this post [solved]
Thanks to everyone for replying m(_ _)m
P.S.
There is still a problem when using virtualbox 4.1.2-1 after reboot, but I think that may not related to this post
If I try to upgrade kernel of the VM to 3.0.2-1 ( currently 3.0.1-1 ), will cause VirtualBox and my computer crash
generating some assert error, produce segfault when I tried to type any command in shell
unable to launch any program in X, but if I switch to tty*, I only got
INIT:Id "x" respawning too fast: disabled for 5 minutes
So I have to push the reset button to force reboot
after restore VM to previous snapshot, not having any problem so far

[SOLVED] package upgrade fails for python2-qt

Similar Messages

Maybe you are looking for