[Bug 489564] Review Request: Blueman - Bluetooth Manager

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=489564





--- Comment #9 from Christian Krause <chkr at plauener.de>  2009-03-12 17:55:45 EDT ---
Hi,

(In reply to comment #7)
> The reason why the upstream tar package and the one I use are different is
> because Upstream won't compile on Fedora 10. There's a bug that prevents it
> from detecting PyGTK. Bug was fixed and will be part of 1.03, so hopefully, I
> won't need any patches for 1.03. 

Yeah, but the patch must not be manually added to the tarball. It is sufficient
that it is delivered in the src.rpm. If you just copy the upstream tarball into
SOURCES and rebuild the src.rpm file using the existing spec file, then
everything is OK:

I've just checked, whether your patch and spec files works also with the
upstream tarball - it does. ;-) :

- the package builds
- the patch is included (automatically) in the src.rpm
- the src.rpm includes the upstream tarball

> Blueman and I never required dbus-python-devel, but I added it to the build
> reqs anyways. 

The dbus-python-devel requirement was revealed by the mock build. ;-)

> I'll be running some mock tests. I hope to compile this for x86_64 and ppc
> soon. 

If you cannot build the package e.g. for a different architecture, you can use
koji, fedora's build system - you'll find more information here:
http://fedoraproject.org/wiki/PackageMaintainers/UsingKoji

You can use a command line like this to get e.g. a src.rpm built in koji:
koji build --scratch dist-f11 SRPMS/blueman-1.02-5.fc10.src.rpm

The output is then something like this:
https://koji.fedoraproject.org/koji/taskinfo?taskID=1238728

Regards,
Christian

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.