Arch Linux

garyvdm

Member

Registered: 2011-09-22

Posts: 7

Help for dealing with conflicting files (header and pkg-config files)

Hi all.

I'm trying to make a PKGBUILD for Barry Warsaw's python 3 port of dbus-python[1][2].

Following  Python Package Guidelines, I decided to name the pkg "python-dbus", even though the upstream is called "dbus-python" and the old python 2 package is called "dbus-python". Is this ok?

So this is my starting point: https://aur.archlinux.org/packages.php?ID=54635

This work fine if you don't have dbus-python installed, but if you do have dbus-python installed, there are conflicting files. These are:

error: failed to commit transaction (conflicting files)
python-dbus-bzr: /usr/include/dbus-1.0/dbus/dbus-python.h exists in filesystem
python-dbus-bzr: /usr/lib/pkgconfig/dbus-python.pc exists in filesystem
python-dbus-bzr: /usr/share/doc/dbus-python/API_CHANGES.txt exists in filesystem
python-dbus-bzr: /usr/share/doc/dbus-python/HACKING.txt exists in filesystem
python-dbus-bzr: /usr/share/doc/dbus-python/NEWS exists in filesystem
python-dbus-bzr: /usr/share/doc/dbus-python/README exists in filesystem
python-dbus-bzr: /usr/share/doc/dbus-python/TODO exists in filesystem
python-dbus-bzr: /usr/share/doc/dbus-python/tutorial.txt exists in filesystem

I was able to move the doc files easily by adding  --docdir=/usr/share/doc/python-dbus to the ./configure line.

for theses files:
/usr/include/dbus-1.0/dbus/dbus-python.h
/usr/lib/pkgconfig/dbus-python.pc

I'm not sure what to do. I'm not sure what they are used for, and so I'm not sure if it is ok to move them.

Does anyone have advice for me on how to move forward?

Gary

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,849

Re: Help for dealing with conflicting files (header and pkg-config files)

Python-dbus i also the name barry warsaw uses, so should be ok.

The main question appears to be whether this package should replace dbus-python or coexist with it.

If python-dbus-bzr is intended to replace the functionality of dbus-python, the conflicts are normal and you should add a conflicts line to the pkgbuild.

In case you want them to coexist, the changes are needed.

Given that the source uses the same paths/filenames as dbus-python, it does look like this package must replace dbus-python.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky