What's this now...
linus@fecusia F-12]$ make update
* Wed Feb 2 2010 Linus Walleij <triad(a)df.lth.se> 1.0.2-1
- New upstream version, lots of bug fixes.
Creating a new update for libmtp-1.0.2-1.fc12
Internal Server Error)
Traceback (most recent call last):
File "/usr/bin/bodhi", line 153, in main
data = bodhi.save(**update_args)
File "/usr/lib/python2.6/site-packages/fedora/client/bodhi.py", line
111, in save
line 316, in send_request
req_params = req_params, auth_params = auth_params)
line 292, in send_request
raise ServerError(url, http_status, msg)
500, Internal Server Error)
make: *** [bodhi] Fel 255
Not my fault I hope...
Is there some infrastructure list where this stuff should go or is devel OK?
As per http://fedoraproject.org/wiki/PackageMaintainers/CompsXml I'm
wondering if a OpenOffice.org-development group makes sense for Comps ?
I see that openoffice.org-testtools and openoffice.org-pyuno are listed
at the moment in comps under Office/Productivity. Both of those are
targeted at development for or with OOo and so best listed elsewhere.
Other related packages, currently unlisted, such as the sdk, the rhino
and beanshell scripting integration packages and so on could be lumped
in there then.
Looking at the build logs for F-12, e.g.:
we seem to have things set up to run configure as:
Which, according to my reading of the autoconf manual means:
* Build on a i386-redhat-linux-gnu
* Create code that runs on i386-redhat-linux-gnu
* Build a cross tool chain that targets i686-redhat-linux-gnu
and really doesn't make sense. I'm pretty sure we want to pass
i686-redhat-linux-gnu for --host, and we don't need to specify --target.
or the info pages which have different text and are a bit clearer.
In fact, we really could just specify --build, I think and have
that go for all three.
Am I missing something here? This is causing GLib to build using slow
fallbacks for atomic operations, and likely causes other problems as
On FC12 I found this:
# ls /usr/bin/.*.hmac
# rpm -qf /usr/bin/.*.hmac
Could somebody provide some insight what these files are (I guess some
checksums) and why they are being installed to /usr/bin?
Packaging bug ?
I have removed the libtool archives from the imlib2-* packages. I don't
think they're are required by any other package, but I might be wrong.
If you maintain a package depending on imlib2 and it's subpackages, please
verify this change is OK for you.
Thanks and regards.
I recently took over as owner of the scm-commits list. There were a
number of CVS commits that got moderated during the mailing list
migration due to a misconfiguration of the list. I went ahead and
released all of them, so a bunch of commits from Jan 10 will show up
on the scm-commits list. Sorry for the noise, but I figured it better
to preserve them than silently throw them away.
I do herewith request to take over the package "mumble", currently owned by igjurisk.
The maintainer seems to be unresponsive and all previous attempts of contact have failed.
According to the policy for non-responsive package maintainers, this request has to be approved
by at least one FESco member.
Bug 552351 - Non-responsive package maintainer of Mumble