Re: [fedora-arm] ARM test-day
On Fri, Jul 31, 2015 at 12:33 PM, Jon wrote: > Would anybody be interested to participate in a fedora-arm testing day for > the upcoming Fedora 23 release [1] ? I'll participate. -Jared ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Re: Raspberry Pi 3
On Mon, Feb 29, 2016 at 7:22 AM, Jeffrey Ollie wrote: > 64 bit processor. >From what I hear, they're still shipping it with 32-bit version of Noobs, and running it in 32-bit compatibility mode. It sounds like they're just interested in the speed bump in the newer SoC, and not in the 64-bit capabilities. -- Jared ___ arm mailing list arm@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org
[fedora-arm] Re: F23 on Wandboard Quad -- kernel doesn't start?
On Fri, Mar 4, 2016 at 10:40 AM, Derek Atkins wrote: > I guess it serves me right for not updating that script. I'm still > using 0.06 (plus some changes to support wandboard on f23). But it > still would've been nice to have at least a one-liner on the wiki :) > The wiki is just that -- a wiki. if you think something needs to be added to it, do it! -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org
Re: [fedora-arm] Hotel logistics
On Thu, Jan 12, 2012 at 3:25 AM, Jon Masters wrote: > I am here, as are Peter, and Dennis. We are having an informal gathering > around noon on Thu. If you arrive, ping me and let me know you are here. > Hotel can put you through to my room or text me +1-617-759-1337. I arrived at around 3:00am this morning. I've had a great late breakfast, and I'd be happy to catch up with you. -- Jared Smith Fedora Project Leader ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Weekly Call - WhenIsGood
On Wed, Jan 18, 2012 at 1:37 PM, Jon Masters wrote: > So far it looks like 4pm EST on a Wednesday, or 1pm on a Friday. Other > times we lose more people. Since Peter's participation is essential to > rawhide I would lean toward Thursday at the moment, which would mean > Jared couldn't make it. Can everyone have a think about whether they can > be more flexible with times? Meanwhile, I wonder if we shouldn't just go > ahead and have a call tomorrow afternoon at 4pm EST for this week? Don't let my crazy schedule hold things up -- have meetings without me and I'll try to fill in the gaps where I can. -- Jared Smith Fedora Project Leader ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] rawhide status update
On Thu, Jan 19, 2012 at 6:31 PM, Peter Robinson wrote: > I said I would give a status update on rawhide, here it is :-) Thanks for the writeup and all the hard work, Peter. That lets the rest of us know where we need to dive in and help so that we can get things working as we get closer to crunch-time here. I think we all know how important it is that we make the F17 branch deadline, so let's get to work! -- Jared Smith Fedora Project Leader ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Network not working on Devkit8000
On Mon, May 14, 2012 at 5:58 PM, Danilo Câmara wrote: > Early on boot I see this message: > Net: Net Initialization Skipped > No ethernet found. > Hit any key to stop autoboot: 0 > > I'm able to login as root but I can not bring up the network: For what little it's worth, I'm having the same problem on my BeagleBoard XM (using bconoboy's F17-hardfp images as of last week), but haven't yet had a chance to try Angstrom to see if it's a software problem or a hardware problem. I'm strongly suspecting there's something wrong with the images, but haven't had time to track down exactly where the problem lies. -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Network not working on Devkit8000
On Mon, May 14, 2012 at 6:19 PM, Robert Nelson wrote: > What "issue" are you seeing with bconoby's F17-hardfp image? (theres > no dm9000 on the beagle xm) No network. In fact, no USB devices at all (besides the root hub) are detected. -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Arm-Koji buildsystem will be down for maintenance
On Fri, Nov 16, 2012 at 2:00 PM, Chris Tyler wrote: > (Investigations into PostgreSQL being insanely brain-dead continue. > Example: query strategy for "SELECT COUNT(*) FROM FOO;" involves a > "Sequential scan over 1496312 records." Srsly?) Just curious... have you VACUUM'd the database? Are you running AUTO-VACUUM? Have you run EXPLAIN ANALYZE SELECT COUNT(*) FROM FOO? In general, once you learn a few tricks like this, it's typically much easier to figure out why PostgreSQL is choosing a particular query plan than it is with other databases. -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Arm-Koji buildsystem will be down for maintenance
On Mon, Nov 19, 2012 at 10:26 AM, Jeffrey Ollie wrote: > http://wiki.postgresql.org/wiki/Slow_Counting Ah, right... I knew this at one time in the past -- funny how my brain is failing me as I get old. Thanks for reminding me :-) -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora 17 v6hl First Compose Image
On Fri, Dec 14, 2012 at 1:43 PM, Sean Omalley wrote: > Although I got a nice ascii train picture flying by the screen... so Im not > sure im not hacked.. Is that the steam locomotive that drives by if you type "sl" instead of "ls" (and have the "sl" package installed), by chance? -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora-ARM Team Shirts
On Wed, Jan 2, 2013 at 1:50 PM, Jon Masters wrote: > I have heard from ARM that we can use the Connected Community logo on a > shirt, but there are some restrictions. These include needing to get > their approval on the incorporating design proof, which is not an > unreasonable thing for them to ask of us. Sounds great! > There might /just/ be time to > pull off some shirts, if we were to turn this around quickly. Therefore, > we will discuss this on the call today. I am copying Ruth and Robyn on > this mail so that we can get their input on any printing options we > might have at this late stage, if we had a final ready to go before next > week. I am thinking we would not print too many shirts, so we would have > various options available, including a local service. Do you need someone to spend some time working on the actual design, or do we already have a design done? I might be able to get one of the design guys at work to spend some time on this if I can give him a clear picture of what we're looking for. -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] How to increase contributions from new members of the SIG?
I'm sorry if this has been discussed in the last couple of meetings, as I wasn't able to make them (and haven't yet seen the logs of yesterday's meeting). To make a long story short, I'm looking for feedback on ways that we can make sure the Fedora ARM team continues to grow and scale and be productive as we inch closer to being a Primary Architecture in Fedora. Let me use my own experience as an example here. I've been part of the ARM SIG since almost the beginning -- I've been in many (if not most) of the weekly meetings, I have two ARM devices up and running on my workbench, and I like to pretend I know at least enough to be dangerous. I try to follow the deep dark issues the core technical group is working on, but don't always understand what they're talking about. My question is this -- what can mere mortals like myself do (from either a technical or non-technical) standpoint to help keep things moving forward. There was a time when I was able to spend a bit of time every day helping out with pushing builds in koji and trying to track down packages that won't build correctly -- is that still needed? Are there "janitor level" tasks that folks can start on to get their feet wet and start contributing? Is there specific documentation that needs to be written? Tools that need to be tested? Scripts that need to be written? I'm willing (as always) to put my time where my mouth is and help out -- please help guide me (and others in the group) in what you'd like us to do! -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] How to increase contributions from new members of the SIG?
On Thu, Jan 3, 2013 at 2:03 PM, Peter Robinson wrote: > I hope this helps, is that the sort of thing you were looking for? Yeah, those are exactly the sorts of things I was looking for. In particular, though, how do we get from "there are probably some things on the wiki that need to be fixed" to a list of items that people can take and run with? Also, do we have a defined mechanism to report packages that aren't working as expected? Bugzilla? Wiki page? Shouting in the IRC channel? -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] FOSDEM
On Tue, Jan 15, 2013 at 4:41 AM, Peter Robinson wrote:
> While FUDCon is all the current talk of the town we all know that
> FOSDEM is where all the cool kids are going to be (well Jon and myself
> at least!) :-)
I'm planning on being there, even though I haven't yet received final
travel approval from ${DAYJOB}. I'd love to hang out and work on ARM
stuff.
--
Jared Smith
___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Documentation for getting started with the ARM SIG
One of the things I brought up at FUDCon this past week was the idea of writing some documentation to help people get up to speed in the Fedora ARM efforts -- a secret decoder ring, if you will, of things they'll need to know to be successful. In an effort to help kick off that documentation, I've written up a quick outline. Nothing is carved in stone yet -- it's just a simple outline of the things I personally would like to see covered. I'm not going to write it all myself (both because I don't have the requisite knowledge, and I want to give others a chance to help out), but I'm more than willing to help get the documentation into DocBook for the Fedora Docs team to publish if people will help me flesh it out. I'll paste the working outline below, but let me point out that this is supposed to be a living document, so I've put it on an Etherpad instance so that people can add/move/edit at will while we're figuring things out. The link to the Etherpad instance is http://piratepad.net/L1jH2TLCBO So tell me -- what would you like to see covered that isn't in the outline already? Is there a section you'd be willing to adopt and help finish? Please let me know... -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora ARM weekly status meeting 2013-02-13
On Wed, Feb 13, 2013 at 11:59 AM, Paul Whalen wrote: > If there is something that you would like to discuss that isn't mentioned > please feel free to bring it up at the end of the meeting or send an email > to the list. I'll once again add the "Documentation" action item, because I think it is important. Also, can we make sure we get a status update on the installation in Phoenix? -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] fedora-arm based router-firewall
On Thu, Apr 25, 2013 at 12:07 PM, Scott Sullivan wrote: > I'm not sure if anyone in the Fedora community currently has one of these > working though. > I have an AX3 mostly working using a hacked-up kernel. I still don't have USB ports working on it, but I know Peter Robinson is going to look at mvebu support in the kernel shortly, so I'm very optimistic that things are moving in the right direction. -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] [AArch64] bootstrap update
On Thu, Apr 11, 2013 at 6:34 PM, Mark Salter wrote: > Next steps are a hosted repo so we can do the stage 4 builds with the > script used for the hard float bootstrap: > > http://arm-temp.ausil.us/pub/fedora-arm/arm-rebuild.sh > > and some better instructions to make it easier for those wanting to join > in with package building on the way to stage 5. > I get a 404 error when trying to look at that script, and I'm lost when it comes to knowing how to help out in Stage 4. I've got the Foundation Model up and running, and am happy to donate some spare CPU cycles to the effort, but could use a little help in knowing how to help out. -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Jared's long list of F15 builds
Over the past few days, I've been trying to dive in and help out in the F15 effort by resubmitting failed builds and helping to identify key packages that are failing to build. I've posted my list of packages at http://openetherpad.org/Fedora-ARM-jsmith, and will try to keep it updated, at least in the short term. The way I created my list was to take the "critical path" packages from F15 (on x86_64, because that's what I had handy), and the list of failed builds in F15 on ARM Koji over the last week, and anything that was in both lists went onto my list. It's a rough list at best, but it's a start :-) The good news is, most of the packages rebuilt just fine. There are still a dozen or so packages that need extra attention, so please look at my list and feel free to dive in and start helping. (Please mark on the website that you're working on a particular package, so that we don't step on each others' toes.) -- Jared Smith Fedora Project Leader ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Jared's long list of F15 builds
On Fri, Dec 2, 2011 at 10:48 AM, Jared K. Smith wrote: > Over the past few days, I've been trying to dive in and help out in > the F15 effort by resubmitting failed builds and helping to identify > key packages that are failing to build. I've posted my list of > packages at http://openetherpad.org/Fedora-ARM-jsmith, and will try to > keep it updated, at least in the short term. The way I created my > list was to take the "critical path" packages from F15 (on x86_64, > because that's what I had handy), and the list of failed builds in F15 > on ARM Koji over the last week, and anything that was in both lists > went onto my list. It's a rough list at best, but it's a start Just a quick status update here -- I've found that "critical path" was a bit bigger than even I had imagined (lovely dependency bloat), so after talking it over with Peter Robinson, I've decided to first concentrate on just the packages need for a minimal install. Peter supplied me with a list of packages, and I've gone through them and tried to build everything that hasn't been built yet, and identify where we are at. Here is my list of packages that are either currently building, have different versions than primary arch, or are having problems. I would especially appreciate it if some of our more knowledgeable members could spend a few minutes trying to help us get the few remaining core packages (things like coreutils and findutils) working. == Still not built == coreutils: Known issue with builders -- see pbrobinson's email to the list efibootmgr: Exclusive arch, doesn't include any ARM arches findutils: Known issue with builders -- see pbrobinson's email to the list gnupg2: *** longjmp causes uninitialized stack frame ***: ../../agent/gpg-agent terminated gpgme: checking for GNU Pth... *FAILED* grub: Is it needed? libgcc: Still no gcc built libssh2: mock fails with "Failed requesting pty" libstdc++: Still no gcc built procmail: FTBFS (since after mass rebuild for F12) pygpgme: depends on gpgme being built first == Still building == cairo appears to be currently building dash appears to be currently building dhcp appears to be currently building libcap-ng appears to be currently building logrotate appears to be currently building net-tools appears to be currently building openssh appears to be currently building openssh-server appears to be currently building pciutils-libs appears to be currently building python appears to be currently building python-libs appears to be currently building tcp_wrappers appears to be currently building vim-minimal appears to be currently building upstart appears to be currently building == Version differences == bash: ARM version (bash-4.2.10-4.fc15) does not match primary arch (bash-4.2.10-2.fc15) device-mapper: ARM version (lvm2-2.02.84-4.fc15) does not match primary arch (lvm2-2.02.84-1.fc15) device-mapper-event: ARM version (lvm2-2.02.84-4.fc15) does not match primary arch (lvm2-2.02.84-1.fc15) device-mapper-event-libs: ARM version (lvm2-2.02.84-4.fc15) does not match primary arch (lvm2-2.02.84-1.fc15) device-mapper-libs: ARM version (lvm2-2.02.84-4.fc15) does not match primary arch (lvm2-2.02.84-1.fc15) glibc: ARM version (glibc-2.14.1-2) does not match primary arch (glibc-2.13.90-9) glibc-common: ARM version (glibc-2.14.1-2) does not match primary arch (glibc-2.13.90-9) kernel: ARM version (kernel-2.6.40.4-6.fc15) does not match primary arch (kernel-2.6.38.6-26.rc1.fc15) libudev: ARM version (udev-167-6.fc15) does not match primary arch (udev-167-4.fc15) lvm2: ARM version (lvm2-2.02.84-4.fc15) does not match primary arch (lvm2-2.02.84-1.fc15) lvm2-libs: ARM version (lvm2-2.02.84-4.fc15) does not match primary arch (lvm2-2.02.84-1.fc15) m4: ARM version (m4-1.4.16-2.fc15) does not match primary arch (m4-1.4.16-1.fc15) module-init-tools: ARM version (module-init-tools-3.16-2.fc15) does not match primary arch (module-init-tools-3.12-5.fc15) nspr: ARM version (nspr-4.8.8-4.fc15) does not match primary arch (nspr-4.8.7-2.fc15) nss: ARM version (nss-3.12.10-6.fc15) does not match primary arch (nss-3.12.9-15.fc15) nss-softokn: ARM version (nss-softokn-3.12.10-4.fc15) does not match primary arch (nss-softokn-3.12.9-7.fc15) nss-softokn-freebl: ARM version (nss-softokn-3.12.10-4.fc15) does not match primary arch (nss-softokn-3.12.9-7.fc15) nss-sysinit: ARM version (nss-3.12.10-6.fc15) does not match primary arch (nss-3.12.9-15.fc15) nss-util: ARM version (nss-util-3.12.10-1.fc15) does not match primary arch (nss-util-3.12.9-2.fc15) rpm: ARM version (rpm-4.9.1.2-3.fc15.1) does not match primary arch (rpm-4.9.0-6.fc15) rpm-libs: ARM version (rpm-4.9.1.2-3.fc15.1) does not match primary arch (rpm-4.9.0-6.fc15) rpm-python: ARM version (rpm-4.9.1.2-3.fc15.1) does not match primary arch (rpm-4.9.0-6.fc15) setup: ARM version (setup-2.8.31-1.fc15) does not match primary arch (setup-2.8.31-
Re: [fedora-arm] Meeting tomorrow at 3pm UTC (10am EST)
On Wed, Dec 7, 2011 at 1:25 PM, Jon Masters wrote: > 0). Package build status (Jon? Jared?) > - How many packages are now build in Koji, which have failed. > how close are we to having the minimal install set? We're fairly close to having the minimal install set done for F15 on both v5 and v7hl. I've knocked off all of the low hanging fruit for the minimal install set (~198 packages), and am now working on the low-hanging fruit of the "critical path" package set (~570 packages). > 1). Packages that require attention > - We discussed gcc/glibc a bit so far > - Also other packages, make sure everyone knows what's needed. > - Timeline for being able to get these fixed. My list of problematic packages for the minimal installation set, along a brief explanation of why they're failing: coreutils * Known problem -- pbrobinson emailed the list about it a few days ago, with no response findutils * Known problem -- pbrobinson emailed the list about it a few days ago, with no response * May be related to http://lists.gnu.org/archive/html/bug-gnulib/2011-03/msg00308.html gcc * Who is building it, and what version? gnupg2 * Build error: *** longjmp causes uninitialized stack frame ***: ../../agent/gpg-agent terminated python * Still building There are still a long list of dependencies missing for "critical path", but that's not as vital to move on to rawhide as the minimal install set is. -- Jared Smith Fedora Project Leader ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Minutes from today's meeting
Minutes: http://meetbot.fedoraproject.org/fedora-arm/2011-12-08/fedora_arm.2011-12-08-15.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-arm/2011-12-08/fedora_arm.2011-12-08-15.00.txt Log: http://meetbot.fedoraproject.org/fedora-arm/2011-12-08/fedora_arm.2011-12-08-15.00.log.html === #fedora-arm: Fedora ARM meeting === Meeting started by jsmith at 15:00:51 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-arm/2011-12-08/fedora_arm.2011-12-08-15.00.log.html . Meeting summary --- * Dial in now! Oh, and a quick role call for those on IRC (jsmith, 15:01:30) * 0 - Package build status (pbrobinson, 15:04:30) * 0 - Package build status (pbrobinson, 15:05:26) * Item 0 - Package build status (jsmith, 15:05:29) * Agenda is posted to mailing list (jsmith, 15:06:02) * Two relevant emails are http://lists.fedoraproject.org/pipermail/arm/2011-December/002307.html and https://lists.fedoraproject.org/pipermail/arm/2011-December/002326.html (jsmith, 15:13:31) * "heavy builder channel" can be established, swap increased on builders (to at least 2GB total) (jonmasters, 15:15:55) * dgilmore and ctyler discussing whether to move off of NFS temporarily and build from SD cards (jsmith, 15:16:28) * possibility of getting builders upgraded to f15 base, and consistent versions across them (jsmith, 15:19:06) * Dennis summarizing his experiences making a hardfp F15 image (jonmasters, 15:20:42) * dgilmore working on f15 builder images, (jsmith, 15:20:45) * dgilmore fairly confident that he'll have f15 builder images soon -- and they'll be in much better shape than what we've been building on (jsmith, 15:22:20) * Item 1: Items that require attention (jsmith, 15:24:01) * coreutils, findutils, gettext are critical (jsmith, 15:24:16) * gcc useful, but not absolutely necessary at this point (jsmith, 15:24:24) * Item 2: Acceptable criteria (jsmith, 15:24:40) * What are we targeting at this point? (jsmith, 15:24:48) * gcc + coreutils + findutils + gettext are blocking pbrobinson from concentrating on rawhide (jsmith, 15:25:41) * ACTION: pbrobinson to email the list with his rawhide plans (jsmith, 15:26:21) * ACTION: plan is to build enough for "an Xfce desktop" and release that for F15 (jonmasters, 15:29:32) * we need some sort of criteria for users until we have f17 out (jsmith, 15:34:00) * raspberry pi will be shipping, and users will be encouraged to use Fedora as the base of that system (jsmith, 15:34:28) * so minimal install set + XFCE is our target (jsmith, 15:34:45) * ACTION: pbrobinson will for demo purposes at least build the sugar desktop too for the XO (jsmith, 15:35:58) * Item 3: Rawhide! (jsmith, 15:36:14) * pbrobinson had to leave the meeting -- fire alarm (jsmith, 15:36:28) * pbrobinson to build the buildroot in the order he determined for f14, to minimize unneeded rebuilds (jsmith, 15:41:30) * pbrobinson to then kick off shadow times 1000 (jsmith, 15:41:57) * After that, it won't take that much to get building rawhide doing mass building (jsmith, 15:42:17) * F17 branch from rawhide happens February 7th (jsmith, 15:44:23) * Item 4: Buildsystem improvements (jsmith, 15:44:57) * discussion regarding getting consistent version of mock on all builders (1.1.18?) (jsmith, 15:47:38) * ACTION: dgilmore to email the list with the kernel config needed for proper pty handling (jsmith, 15:48:24) * dgilmore has been working on kirkwood kernel (jsmith, 15:48:53) * dgilmore hoping to have work done by end of tomorrow (jsmith, 15:51:12) * LINK: http://fedoraproject.org/wiki/Architectures/ARM/F15_Koji_build (jonmasters, 15:52:12) * Item 5: Any other business (jsmith, 15:54:22) * discussing whether or not to keep having a weekly meeting (jsmith, 15:54:56) * AGREED: Keep the meeting, let's keep this time slot through early January, and then readdress the time (jsmith, 15:55:17) Meeting ended at 16:02:01 UTC. Action Items * pbrobinson to email the list with his rawhide plans * plan is to build enough for "an Xfce desktop" and release that for F15 * pbrobinson will for demo purposes at least build the sugar desktop too for the XO * dgilmore to email the list with the kernel config needed for proper pty handling Action Items, by person --- * dgilmore * dgilmore to email the list with the kernel config needed for proper pty handling * pbrobinson * pbrobinson to email the list with his rawhide plans * pbrobinson will for demo purposes at least build the sugar desktop too for the XO * **UNASSIGNED** * plan is to build enough for "an Xfce desktop" and release that for F15 People Present (lines said) --- * jsmith (61) * jonmasters (15) * fo
[fedora-arm] Minimal build and XFCE build status update, plus my script for checking builds
As mentioned in last week's meeting, I've been trying to focus on getting all the packages for a "minimum" build done first, and then as a next step focusing on an XFCE-based set of packages. The current list of blockers for the minimal build include: == Minimal Build Missing Packages == coreutils: needs builder updates to build findutils: needs builder updates to build gcc: Do we need a new version, or is the version from stage4 sufficient? libssh2: pbrobinson is working on this, build tests having problem allocating pty python: dgilmore and pbrobinson are working on this While waiting for the last few packages for the minimal set to get fixed up, I've started trying to knock off the low-hanging fruit of the XFCE packages. Right now, the biggest impediment to getting more of these packages built is to get xulrunner built, as most of the outstanding packages rely on it either directly or indirectly. == XFCE Build Missing Packages == biosdevname: exclusive arch, not needed control-center: needs xulrunner to build coreutils: needs builder updates to build efibootmgr: exclusive arch, not needed findutils: needs builder updates to build gcc: Do we need a new version, or is the version from stage4 sufficient? gdm: needs control-center and gnome-power-manager to build gnome-bluetooth: needs mutter-meego to build gnome-session: needs control-center to build gnome-settings-daemon: needs xulrunner and PackageKit to build grub: not needed libssh2: pbrobinson is working on this, build tests having problem allocating pty libxfce4ui: needs glade3 to build libxfcegui4: needs glade3 to build libXrandr: needs coreutils mesa: dgilmore is working on this, svga_tgsi_insn.c:3071:1: internal compiler error: in push_minipool_fix, at config/arm/arm.c:12094 ModemManager: failing to build because of pty allocation failure mousepad: needs glade3 to build NetworkManager: Needs ModemManager and gnome-bluetooth to build orage: needs xfce4-panel PackageKit: needs xulrunner to build pulseaudio: needs qt to build python: pbrobinson and dgilmore are working on this startup-notification: needs to be rebuilt for F15 Thunar: needs glade3 to build thunar-volman: needs glade3 to build xfce4-appfinder: needs glade3 to build xfce-utils: needs glade3 to build xfce4-mixer: needs glade3 to build Here's a rough set of build dependency chains to try to get the rest of these packages built. I don't presume that this list is completely accurate or definitive -- it's simply my first attempt at documenting the dependencies that I've come across while trying to build the packages above, and doing my best to group them into logical layers. Please feel free to update this list with any knowledge you might have. == XFCE build dependency chains == clutter clutter-gesture : libmx : cheese xulrunner PackageKit : control-center gnome-settings-daemon : gnome-power-manager : gdm qt : qscintilla : PyQT4 : libffado : jack-audio-connection-kit : pulseaudio : kde : l ibproxy : libxfce4ui coreutils : libXrandr xfwm4 xorg-x11-server-utils gtk+ zenity libmx : cheese xulrunner PackageKit : mutter-mbl : control-center gnome-settings-daemon : mutter-meego ModemManager dhcp dnsmasq iproute gnome-power-manager : gnome-bluetooth gdm : NetworkManager gstreamer-plugins-base geoclue : webkitgtk3 : devhelp : glade3 : libxfce4ui xfdesktop xfce4-appfinder xfce-utils xfce4-panel xfce4-session xfce4-settings xfce4-mixer xfce4-power-manager libxfcegui4 Thunar thunar-volman : orage Last but not least, I'm including a copy of my (very rough) script that I use to check to see what builds have been done and which builds have not yet been done. It takes in a list of binary packages (just the names of the packages themselves, without versions), and outputs a list of missing builds, completed builds, builds in progress, and builds with different versions than primary arch. Again, the script is rough, so feel free to post changes or updates to it. Better yet, rewrite it in Python and get it to use the Koji APIs directly, rather than calling the Koji command-line programs and scraping the output :-) -- Jared Smith Fedora Project Leader <> ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora ARM presentation at the Developer Conference in February?
On Tue, Dec 13, 2011 at 9:36 AM, Niels de Vos wrote: > I am wondering if Fedora ARM should do a talk at the upcoming conference > in Brno early next year: > - https://fedoraproject.org/wiki/DeveloperConference2012 I'll be at the conference and would be more than willing to talk, but I'm probably not the most knowledgeable person to speak on the subject. -- Jared Smith Fedora Project Leader ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] system with FXS port
On Tue, Jan 14, 2014 at 3:15 PM, Robert Moskowitz wrote: > I am looking for a arm board, supported by Fedora, with an FXS port to > work with Asterisk. I'm not aware of anything out there at this time. I have heard of people using a mini-pcie to pcie bridge to use a standard PCI-E FXS card, but that seems to me to be overkill. -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] system with FXS port
On Fri, Jan 17, 2014 at 11:05 AM, Robert Moskowitz wrote: > I was reminded that with spandsp, you can get a v32modem to function as an > fxs port. Of course this puts the burden for i/o handling on your cpu. > Use to do this lots of years ago, and really forgot those days. You *can* do this, however you're not likely to have great results. Traditionally this was done to function as an FXO port (connected to the central office), but this doesn't handle remote disconnect supervision (at least the American way of doing far-end disconnect supervision), so it's easy get stuck lines. -Jared ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Support for the TP-link TL-wn725n
On Fri, Aug 1, 2014 at 3:37 PM, Peter Robinson wrote: > If it works on mainline x86 it should work on ARM. > As far as I know, it doesn't work on mainline x86 -- there's no driver in the kernel for it yet. (I've seen kernel modules on github that supposedly support it, but I haven't been that adventurous yet.) I picked one up for a few dollars a couple of weeks ago on a whim, and I'd be happy to bring it to Flock to let anyone play around with it. -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Minimal printing problems
On Mon, Dec 1, 2014 at 4:55 PM, Robert Moskowitz wrote: > This tells that something else is needed to print from the Minimal setup > beyond cups and hplip. What might it be? This problem doesn't appear to be ARM related, so you'll probably get more help on one of the other Fedora lists, such as the test list or users list. -Jared ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Re: Fedora 33 released
On Wed, Oct 28, 2020 at 3:50 PM Jeffrey Walton wrote: > The x86_64 system upgrade went fine > (https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/). > Fedora 33 is running fine on my x86_64 test hardware. > Since this is the ARM list, I'll also report that I have Fedora 33 running just fine on a couple of aarch64 boxes under my desk at the moment as well. Thanks to everyone who helped to make F33 the best release yet for ARM hardware! -Jared ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
[fedora-arm] Re: Any update on suggested devices?
On Tue, Nov 10, 2020 at 11:30 AM Matthew Miller wrote: > At that meeting, we talked about y'all coming up with a list of specific > hardware we can order for people. > I would love to see the nVidia Jetson Nano (roughly $99 USD) or Jetson Nano 2GB (roughly $54 USD) on that list. I have to of the 4GB version, and thanks to Peter and a few other people doing lots of thankless work, they work quite well out of the box with F33. I'm also happy to volunteer to help test ARM images and the IoT spin on said hardware. -Jared ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
[fedora-arm] Re: Fedora 33 aarch64 on Helios64
On Mon, Nov 16, 2020 at 2:28 PM ITwrx wrote: > did you see my post from 11/2/2020 about my orange pi r1 hanging? do you > need a device for testing? > Just to give a bit more context -- Peter is very good at responding to threads that he has input for, so if he didn't respond, it's likely that he didn't have anything useful to add. Also, he's very overworked as it is, so switching the topic of an email thread to ask about another random board (that may or may not be supported in Fedora) is frowned upon. While Peter happens to be a subject-matter expert, this isn't the "Ask Peter Questions" list... if nobody answered your thread, it's likely that nobody knows the answer. -- Jared Smith ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
