F13 Beta Repository Problems
by Matthew Wilson
Hello,
I now have a F13 Beta install on my IGEP board (BeagleBoard clone)
with a custom-built 2.6.35.11 kernel. A big thank you to the efforts
of everyone involved in F13 on ARM.
However, at the weekend, I spotted some weird behaviour with yum.
There are lots (too many to list here) of packages that are on the
koji system but not available through the yum repo. Installing
certain packages will give a long list of unresolved dependencies; I
then found those on koji, installed them manually, and then tried
again. I appreciate that this method is less than ideal (not least
from the perspective of maintaining a consistent system).
Some of the missing RPMs are from multi-RPM packages where the rest of
the RPMs are (strangely) present in the repo. Furthermore, there are
a handful of F12 packages I had to install.
Since then, I see that someone has renamed the
/mash/beta/f13-arm-2011-02-21 directory to f13-arm-2011-02-21_hold,
further breaking yum.
What's the most useful thing I can do? If it's a known issue, I'll
sit tight until it's fixed.
Many thanks,
Matthew
11 years, 12 months
Data Issues - arm.koji.fedoraproject.org
by Chris Tyler
The arm-koji builders are temporarily offline while we fix up some data
issues on the koji hub. We're restoring some packages that went missing
yesterday evening (and working on figuring how they went missing :-)
-Chris
12 years
Re: [fedora-arm] Want to join Fedora ARM development
by Saleem Ansari
On Thu, Mar 10, 2011 at 11:48 AM, Dheeraj Kumar <dhiry2k2(a)gmail.com> wrote:
> Hi ,
>
> sorry for confusion. I have Fedora 14 installed on my x86 system, can i do
> development using fedora 14.
>
> definitely i will have a look at koji builder.
>
> Does ARM Fedora doing something in sync with beagleboard hardware?
>
Yes. Fedora can be installled on BeagleBoard.
ARM Koji itself runs one of the native builder on BeagleBoard.
http://zenit.senecac.on.ca/wiki/index.php/Fedora_ARM_Koji_Buildsystem
http://zenit.senecac.on.ca/wiki/index.php/Fedora_ARM_Secondary_Architectu...
> Thanks,
> Dheeraj
>
> On Thu, Mar 10, 2011 at 10:53 AM, tuxdna <tuxdna(a)gmail.com> wrote:
>>
>> > Thanks for replying. I have fedora 14 installed on an actual hardware.
>> > Will
>> > it not be supported to ARM development?
>> >
>>
>> Do you have Fedora 14 installed on an ARM machine?
>>
>> I doubt that since there hasn't been any release of Fedora 14 packages
>> for ARM yet.
>>
>> All the packages for Fedora are built using Koji builder. Whenever
>> someone submits
>> a package to be built using Koji, it is automatically built for i386,
>> x86_64 and PPC.
>> However this is not the case for ARM so there is an other separate
>> built server for
>> packages which need to be built for ARM architecture.
>>
>> For example, have a look at
>> http://arm.koji.fedoraproject.org/koji/
>>
>> http://arm.koji.fedoraproject.org/koji/taginfo?tagID=20
>>
>>
>> To learn more about koji, here is the link:
>> http://fedoraproject.org/wiki/PackageMaintainers/UsingKoji
>>
>> /tuxdna
>
>
12 years
arm fedora smaller rootfs
by 钟威
Hi guys, I wanted to a smaller fedora 12 rootfs for arm,but I downloaded the rootfs(rootfs-f12.tar.bz2 ) had 102MB, how can I do to make a smaller rootfs or which websit I can download.I need you help and hope all guys can help me!
Thanks and Best Regards,Wei
12 years
Want to join Fedora ARM development
by Dheeraj Kumar
Hello,
I would like to work with Fedora ARM community. Please have a look at my
profile.
www.linkedin.com/in/dhiry2k
I have been looking into the fedora ARM project from quite sometime now and
interested in working with it. Please provide me an opportunity to work.
Thanks,
Dheeraj
12 years
Re: [fedora-arm] Building Updates
by Chris Tyler
On Tue, 2011-03-08 at 07:39 -0600, Dennis Gilmore wrote:
> On Tuesday, March 08, 2011 07:18:02 AM Chris Tyler wrote:
> > There are a few options here:
> > [A] Use koji-shadow against dist-fX-updates-candidate PA (and targeting
> > dist-fX-updates-candidate SA) and use a separate process to manage the
> > tag-shadowing between PA and SA.
> >
> > [B] Watch dist-fX-updates PA for packages tagged in, and then build
> > those, targeted to dist-fX-updates on the SA. This saves a bunch of
> > package building on the SA side (though I'm not sure what the ratio is
> > between packages built and pushed to stable).
> >
> > I'm leaning towards some version of [B]. Any thoughts/comments on this
> > approach?
>
> ultimately A is the correct approach.
Why?
Doesn't this result in a number of packages being built that never see
the light of day? That seems wasteful.
-Chris
12 years
Building Updates
by Chris Tyler
(Cross-posted to arm@ and secondary@)
We're approaching the release of F13 for ARM. It's about to hit EOL on
the primary archs, so it has a short shelf life, but I'm going to use
that time to figure out the best process for building updates -- with a
goal of having the updates procedure well in hand by the time we hit F15
on ARM. (Paul Whalen, meanwhile, is going to continue to head up the
drive towards the F14/F15 ARM releases).
On the primary archs (PA), updates are built, targeted at
dist-fX-updates-candidate, then shepherded via Bodhi through a sequence
of tags:
dist-fX-updates-candidate ->
dist-fX-updates-testing-pending ->
dist-fX-updates-testing ->
dist-fX-updates-pending
dist-fX-updates
There are a few options here:
[A] Use koji-shadow against dist-fX-updates-candidate PA (and targeting
dist-fX-updates-candidate SA) and use a separate process to manage the
tag-shadowing between PA and SA.
[B] Watch dist-fX-updates PA for packages tagged in, and then build
those, targeted to dist-fX-updates on the SA. This saves a bunch of
package building on the SA side (though I'm not sure what the ratio is
between packages built and pushed to stable).
I'm leaning towards some version of [B]. Any thoughts/comments on this
approach?
-Chris
12 years
arm@lists.fedoraproject.org
by Nick Clifton
Hi Everyone,
As part of a possible solution to the problem of how to bootstrap a
hard-float ARM Fedora port, I am working on a script to create "fat"
ARM binaries. These are binaries which use the soft-float API, but
which contain a special section which holds a hard-float API
alternative. Using one of the switches supported by the script it is
possible to flip over the binaries, so that they now use the
hard-float API and contain the soft-float API hidden away inside them.
This is still a work in progress, but we thought that it would be a
good idea to post the current version of the script to the list to see
what people think, and to gather any feedback. At the moment the
script can only do simple compiling and linking. It does not yet
handle static or shared libraries, but that should come soon.
Here is an example of how the script works:
% cat float.c
double add (double a, double b) { return a + b; }
int main (void) { return (int) add (2.0, 3.0); }
% fat-gcc -c float.c
% fat-gcc float.o
% ls -l float.o a.out
-rwxrwx---. 1 nickc nickc 304778 Mar 1 17:58 a.out*
-rw-------. 1 nickc nickc 2136 Mar 1 17:58 float.o
% fat-gcc --fat-status float.o a.out
fat-gcc.sh: float.o: uses the soft API, contains a hard API
alternative
fat-gcc.sh: a.out: uses the soft API, contains a hard API alternative
% objdump -d a.out
[snip]
000081b8 <add>:
81b8: e92d4810 push {r4, fp, lr}
81bc: e28db008 add fp, sp, #8
81c0: e24dd014 sub sp, sp, #20
81c4: e50b0014 str r0, [fp, #-20]
[snip]
% fat-gcc --fat-swap a.out
% fat-gcc --fat-status float.o a.out
fat-gcc.sh: float.o: uses the soft API, contains a hard API alternative
fat-gcc.sh: a.out: uses the hard API, contains a soft API alternative
% objdump -d a.out
[snip]
000081b8 <add>:
81b8: e52db004 push {fp} ; (str fp,
[sp, #-4]!)
81bc: e28db000 add fp, sp, #0
81c0: e24dd014 sub sp, sp, #20
81c4: ed0b0b03 vstr d0, [fp, #-12]
[snip]
Cheers
Nick
12 years