Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34076 - Fallo para instalar Skype por conflicto de dependencias

Attached to Project: Arch Linux
Opened by Julio Cesar Campos (1a2bc3d4) - Thursday, 28 February 2013, 16:18 GMT
Last edited by Pierre Schmitz (Pierre) - Thursday, 28 February 2013, 23:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:Al querer instalar Skype, falla la instalacion por que no cumple una dependencia. Pide qt y yo tengo qt4 (como resultado de una actualizacion del sistema, yo uso testing)


Additional info:
* package version(s) community/skype 4.1.0.20-3

* config and/or log files etc.


Steps to reproduce:

[root@arch julio]# pacman -S skype
resolviendo dependencias...
verificando conflictos...
:: qt y qt4 están en conflicto. ¿Quitar qt4? [s/N] n
error: se han detectado paquetes con conflictos no resolvibles
error: error al preparar la transacción (dependencias en conflicto)
:: qt y qt4 están en conflicto
[root@arch julio]#

This task depends upon

Closed by  Pierre Schmitz (Pierre)
Thursday, 28 February 2013, 23:46 GMT
Reason for closing:  None
Additional comments about closing:  Ich kann das nicht lesen.
Comment by Jorge Barroso (jorge_barroso) - Thursday, 28 February 2013, 16:25 GMT
Deja de usar testing y haz pacman -Syuu, luego prueba de nuevo
Si no, dile que si

Bite pierre: He had a problem installing skype because he had dependencies problem with qt/qt4, so he has activated community-testing repo (he already had testing activated) and then he could update skype correctly)
Comment by Gustavo Alvarez (sl1pkn07) - Thursday, 28 February 2013, 16:37 GMT Comment by Julio Cesar Campos (1a2bc3d4) - Thursday, 28 February 2013, 17:09 GMT
Gracias Gustavo, listo ya todo arreglado, me imagino que no corro mas riesgo con Community-testing activado que con solo testing.
Pude instalar tambien unetbootin.
Comment by Gustavo Alvarez (sl1pkn07) - Thursday, 28 February 2013, 17:28 GMT
es preferible que si tienes community-testing activado también tengas testing, ya que en el caso del cambio qt a qt4 abarca ambos repositorios a la vez, aparte de que si tienes paquetes en AUR con el mismo problema, tienes que editarlos uno a uno para adaptarlos
Comment by Ionut Biru (wonder) - Thursday, 28 February 2013, 17:37 GMT
please use english to report bugs.

Loading...