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#12489 - gajim-0.12-1 doesn't installed because of file conflicts

Attached to Project: Arch Linux
Opened by Eric Belanger (Snowman) - Thursday, 18 December 2008, 02:05 GMT
Last edited by Douglas Soares de Andrade (dsa) - Monday, 02 February 2009, 02:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Douglas Soares de Andrade (dsa)
Architecture All
Severity Medium
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

(3/3) checking for file conflicts [---------------------------------------------------------------] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
gajim: /usr/share/gajim/src/advanced.pyo exists in filesystem
gajim: /usr/share/gajim/src/cell_renderer_image.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/GnuPG.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/GnuPGInterface.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/__init__.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/config.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/connection.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/gajim.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/helpers.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/i18n.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/logger.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/optparser.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/sleepy.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/socks5.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/__init__.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/auth.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/browser.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/client.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/debug.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/dispatcher.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/features.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/filetransfer.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/protocol.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/roster.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/simplexml.pyo exists in filesystem
gajim: /usr/share/gajim/src/common/xmpp/transports.pyo exists in filesystem
gajim: /usr/share/gajim/src/config.pyo exists in filesystem
gajim: /usr/share/gajim/src/dialogs.pyo exists in filesystem
gajim: /usr/share/gajim/src/filetransfers_window.pyo exists in filesystem
gajim: /usr/share/gajim/src/gajim.pyo exists in filesystem
gajim: /usr/share/gajim/src/gajim_themes_window.pyo exists in filesystem
gajim: /usr/share/gajim/src/gtkgui_helpers.pyo exists in filesystem
gajim: /usr/share/gajim/src/history_window.pyo exists in filesystem
gajim: /usr/share/gajim/src/remote_control.pyo exists in filesystem
gajim: /usr/share/gajim/src/roster_window.pyo exists in filesystem
gajim: /usr/share/gajim/src/systray.pyo exists in filesystem
gajim: /usr/share/gajim/src/tooltips.pyo exists in filesystem
gajim: /usr/share/gajim/src/vcard.pyo exists in filesystem
Errors occurred, no packages were upgraded.

I don't know if they are supposed to be in the package. At least they weren't in the old one.
This task depends upon

Closed by  Douglas Soares de Andrade (dsa)
Monday, 02 February 2009, 02:20 GMT
Reason for closing:  Fixed
Comment by Eric Belanger (Snowman) - Thursday, 18 December 2008, 02:11 GMT
BTW, you should use optdepends and remove the .install file.
Comment by Allan McRae (Allan) - Thursday, 18 December 2008, 08:34 GMT
You might want to add pyopenssl as an optdep too (for secure connections). It is currently in [community].
Comment by Jan de Groot (JGC) - Thursday, 18 December 2008, 10:17 GMT
You can force-overwrite these files, as they're compiled versions of the .py files in the package. I think we should have a python policy to handle precompiled python objects, as we get quite some bugs about these issues.
Comment by Timm (gummibaerchen) - Thursday, 18 December 2008, 13:46 GMT
I wanted to create a new bug for this, but as Allan said already, pyopenssl should be a dependency now.

I didn't knew before the python built-in SSL was unsecure, but there was some discussion about it over at gajim.org, and not it spits a warning when pyopenssl is not installed.

Loading...