Compose started at Mon Oct 1 09:15:21 UTC 2012
Broken deps for x86_64
--
[almanah]
almanah-0.8.0-7.fc18.x86_64 requires libedataserverui-3.0.so.3()(64bit)
almanah-0.8.0-7.fc18.x86_64 requires libedataserver-1.2.so.16()(64bit)
Compose started at Mon Oct 1 08:15:11 UTC 2012
Broken deps for x86_64
--
[almanah]
almanah-0.8.0-7.fc18.x86_64 requires libedataserverui-3.0.so.3()(64bit)
almanah-0.8.0-7.fc18.x86_64 requires libedataserver-1.2.so.16()(64bit)
Hi all,
This is a formal request required by the procedure in case of absence of
the original maintainer to take over the package. This is step #5:
https://fedoraproject.org/wiki/Package_maintainer_policy#What_to_do_if_a_maintainer_is_absent
I asked to become a gradle package co-maintainer bu
A file has been added to the lookaside cache for perl-PerlIO-utf8_strict:
2e5b13efe6dfd7748e44e47f6dedb1da PerlIO-utf8_strict-0.002.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedorapr
commit fa4ae7f6a56afcc38a9ff205e6190ca16a8f42cd
Author: Petr Písař
Date: Mon Oct 1 17:07:35 2012 +0200
Import
.gitignore |1 +
perl-PerlIO-utf8_strict.spec | 53 ++
sources |1 +
3 files changed, 55 i
Hello,
I am running Fedora 17 on x86_64.
I wanted to build bluetooth kernel module for f17 so I could use it under f17.
I did this:
download kernel-3.3.4-5.fc17.src.rpm.
ran:
rpm -ivh kernel-3.3.4-5.fc17.src.rpm
rpmbuild -bp /root/rpmbuild/SPECS/kernel.spec
It went well.
Then , I went to /root/r
Hi,
Update:
I found a workaround:
adding
EXTRAVERSION = -5.fc17.x86_64
in the Makefile.
But shouldn't it be so when applying the src.rpm
without any change from me ?
rgs,
Kevin
On Mon, Oct 1, 2012 at 6:32 PM, Kevin Wilson wrote:
> Hello,
> I am running Fedora 17 on x86_64.
> I wanted to build b
On Mon, Oct 1, 2012 at 1:05 PM, Kevin Wilson wrote:
> Hi,
> Update:
> I found a workaround:
> adding
> EXTRAVERSION = -5.fc17.x86_64
> in the Makefile.
>
> But shouldn't it be so when applying the src.rpm
> without any change from me ?
No, because you only used RPM to expand the source, then you
On Sun, Sep 30, 2012 at 10:09:33AM +0200, Andreas Tunek wrote:
> The latest couple of F18 live images I have tried have not been efi
> bootable. Is this something known or something I should report in bugzilla?
> If so, under what component?
What, exactly, happens? How are you trying to boot them?