building an embedded Linux distro into a RPM package
by Chuck Anderson
I originally sent this to the packaging list, but there was no
response there so I'm posting to devel now.
I've also opened a review request for the non-controversial packaging
of the "msed" utilities. Would anyone care to do a review swap?
Review Request: msed - Tools to manage the activation and use of self encrypting drives
https://bugzilla.redhat.com/show_bug.cgi?id=1245640
Thanks.
Date: Tue, 21 Jul 2015 18:48:27 -0400
From: Chuck Anderson <cra(a)WPI.EDU>
To: packaging(a)lists.fedoraproject.org
Subject: [Fedora-packaging] building an embedded Linux distro into a RPM package
Precedence: list
Reply-To: Discussion of RPM packaging standards and practices for Fedora <packaging(a)lists.fedoraproject.org>
I would like to submit a new package that provides a Pre-Boot
Authorization (PBA) image. The PBA is a "bootloader" of sorts that
prompts the user for the passphrase to unlock a Self-Encrypting Drive
(SED) using the TCG OPAL command set, and then either chainloads to
the real OS or reboots to allow the BIOS to boot the real OS. The
image gets installed to the OPAL SED as a sort of "shadow MBR/shadow
disk image" using a special command "msed" (Manage Self-Encrypting
Drive) that I also plan to submit a package for.
In my case, I've developed a tiny embedded Linux-based PBA image [1]
using Buildroot [2] and the MSED software [3]. The final image is a
MBR-partitioned disk image with VFAT filesystem containing the
specially built Linux kernel (vmlinuz), initramfs (rootfs.gz), and the
installed syslinux bootloader.
Before you ask, I can't use even a stripped-down Fedora image for this
purpose, because it must be TINY and it only exists to run a single
command (linuxpba), then reboot. My image is 4MB and could be made
even smaller. See the reasoning in [1] for why it must be so small.
[1] https://github.com/cranderson/buildroot-linuxpba
[2] http://buildroot.uclibc.org/
[3] http://www.r0m30.com/msed
Now I know there are several challenges to using the Buildroot
approach to building software for Fedora. Buildroot downloads
software from the Internet, unpacks, patches, configures, and builds
it. The build environment is built first, so gcc, uClibc, busybox,
etc. and then the packages you want to include are built in that
environment.
What is the best approach I should use that is acceptable to Fedora?
Would it be acceptable to bundle source packages, Buildroot itself,
and my Buildroot configuration into one SRPM so everything is
self-contained and can be built without requiring network
connectivity? This means I would have to bundle the source code for
gcc, the linux kernel, uClibc, busybox, etc.
Or is there some way to pull in SRPM packages that already exist in
Fedora, and use those as part of my build process so that I don't have
to bundle all the source code? Additionally, I could made separate
SRPM packages for Buildroot itself, any components needed (uClibc is
already in the distro), the Buildroot build scripts for
buildroot-linuxpba, and the actual package I need (msed).
5 years, 7 months
Systemd Preset Policy
by Sérgio Basto
Hi,
Let me see if I understand , on 2015-05-20 [1] FESCo has decided to
merge some of the policy around service units, socket units and timer
units into a single policy that treats all units that run as default the
same way.
Note: decision made 6 days before Fedora 22 Final Release.
We got some new wiki pages [2] - How to enable a service by default ?
Services are enabled or disabled by default through systemd preset files
But before that I used a script to enable services like this:
%post guest
/bin/systemctl daemon-reload >/dev/null 2>&1 || :
/bin/systemctl restart systemd-modules-load.service >/dev/null 2>&1 || :
/bin/systemctl enable vboxservice.service >/dev/null 2>&1 || :
/bin/systemctl restart vboxservice.service >/dev/null 2>&1 || :
This kind of scriptlet still works on Fedora 22 (updated), on a new
installation ?
Other wiki page shows that PackagePresets are from Fedora 18 ! [3]
And what is the best way to set a preset for a service ? that we want
enable by default, when is installed .
Note: I'm asking this because I don't saw any example on package
guidelines.
[1] https://fedorahosted.org/fpc/ticket/532
[2]
https://fedoraproject.org/wiki/Packaging:DefaultServices#Locally_running_...
[3] https://fedoraproject.org/wiki/Features/PackagePresets
Thanks,
--
Sérgio M. B.
5 years, 7 months
[POC-change] Fedora packages point of contact updates
by Nobody
Change in package status over the last 168 hours
================================================
4 packages were orphaned
------------------------
Shinobi [f22, f21] was orphaned by raphgro
Meta build system for Ninja
https://admin.fedoraproject.org/pkgdb/package/Shinobi
cclive [f23, f22, f21, master] was orphaned by cicku
Command line media stream extraction tool
https://admin.fedoraproject.org/pkgdb/package/cclive
photoprint [f23, f22, f21, master] was orphaned by mdomsch
Utility for printing digital photographs
https://admin.fedoraproject.org/pkgdb/package/photoprint
pki-ra [f22, f21] was orphaned by mharmsen
Certificate System - Registration Authority
https://admin.fedoraproject.org/pkgdb/package/pki-ra
12 packages were retired
-------------------------
MySQL-python [master] was retired by jdornak
An interface to MySQL
https://admin.fedoraproject.org/pkgdb/package/MySQL-python
Shinobi [f23, master] was retired by raphgro
Meta build system for Ninja
https://admin.fedoraproject.org/pkgdb/package/Shinobi
ardour3 [f23, master] was retired by nphilipp
Digital Audio Workstation
https://admin.fedoraproject.org/pkgdb/package/ardour3
clean [f23, master] was retired by puiterwijk
The Clean language compiler
https://admin.fedoraproject.org/pkgdb/package/clean
clean-extra-utils [f23, master] was retired by puiterwijk
A collection of extra libraries and utilities for the Clean programming language
https://admin.fedoraproject.org/pkgdb/package/clean-extra-utils
dmlite-plugins-librarian [f23, master] was retired by aalvarez
Librarian plugin for dmlite
https://admin.fedoraproject.org/pkgdb/package/dmlite-plugins-librarian
gofer [el6] was retired by jortel
A lightweight, extensible python agent
https://admin.fedoraproject.org/pkgdb/package/gofer
perl-Gtk2-SourceView [f23, master] was retired by thm
Perl wrappers for the GtkSourceView widget
https://admin.fedoraproject.org/pkgdb/package/perl-Gtk2-SourceView
pki-ra [f23, master] was retired by mharmsen
Certificate System - Registration Authority
https://admin.fedoraproject.org/pkgdb/package/pki-ra
prelink [f23, master] was retired by till
An ELF prelinking utility
https://admin.fedoraproject.org/pkgdb/package/prelink
python-rtstool [f23, master] was retired by eharney
Command-line interface for rtslib
https://admin.fedoraproject.org/pkgdb/package/python-rtstool
satyr [el6] was retired by jfilak
Tools to create anonymous, machine-friendly problem reports
https://admin.fedoraproject.org/pkgdb/package/satyr
6 packages unorphaned
---------------------
R-ALL [f21] was unorphaned by pingou
Data of T- and B-cell Acute Lymphocytic Leukemia
https://admin.fedoraproject.org/pkgdb/package/R-ALL
clean [f22] was unorphaned by till
The Clean language compiler
https://admin.fedoraproject.org/pkgdb/package/clean
elementary [f23, f22, f21, master] was unorphaned by konradm
Basic widget set that is easy to use based on EFL
https://admin.fedoraproject.org/pkgdb/package/elementary
jericho-html [f23, f22, f21, master] was unorphaned by gil
Java library allowing analysis and manipulation of parts of an HTML document
https://admin.fedoraproject.org/pkgdb/package/jericho-html
jgroups212 [f23, f22, f21, master] was unorphaned by gil
A toolkit for reliable multicast communication
https://admin.fedoraproject.org/pkgdb/package/jgroups212
jsilver [f23, f22, f21, master] was unorphaned by gil
A pure-Java implementation of Clearsilver
https://admin.fedoraproject.org/pkgdb/package/jsilver
0 packages were unretired
------------------------
5 packages were given
------------------------
aiccu [el6, epel7, el5] was given by mdomsch to pavlix
SixXS Automatic IPv6 Connectivity Client Utility
https://admin.fedoraproject.org/pkgdb/package/aiccu
golang-github-prometheus-client_golang [f23, f22, f21, el6, master] was given by jchaloup to fpokorny
Prometheus instrumentation library for Go applications
https://admin.fedoraproject.org/pkgdb/package/golang-github-prometheus-cl...
golang-github-prometheus-prometheus [f23, f22, f21, el6, master] was given by jchaloup to fpokorny
The Prometheus monitoring system and time series database
https://admin.fedoraproject.org/pkgdb/package/golang-github-prometheus-pr...
mirrormanager [f23, f22, f21, el6, master] was given by mdomsch to pingou
Fedora mirror management system
https://admin.fedoraproject.org/pkgdb/package/mirrormanager
mongo-java-driver [f23, f22, f21, master] was given by jvanalte to omajid
A Java driver for MongoDB
https://admin.fedoraproject.org/pkgdb/package/mongo-java-driver
1 packages had new branches
------------------------
perl-MooX-Log-Any had a new branches: f23, f22, f21, master, el6, epel7 for ttorling by limb
A Moose role to add support for logging via Log::Any
https://admin.fedoraproject.org/pkgdb/package/perl-MooX-Log-Any
Sources: https://github.com/pypingou/fedora-owner-change
5 years, 7 months
Re: Fedora developer portal - proof of concept
by Adam Samalik
> I think it probably makes sense to focus on http://devassistant.org/ and
> https://dapi.devassistant.org/ as the entry points to the Fedora
> developer experience...
Agree. They can start with the interesting part - coding - first.
> ...We may want to pick out particular assistants and
> highlight them (especially if we design the Fedora DA package to come
> with some assistants pre-installed), but I think it makes sense to push
> the "comprehensive" side of the story further upstream...
Exactly. We would provide information how to get it running on Fedora - like
the current Ruby guide. (They can, of course, use DevAssistant)
> ..., and have
> developers.fedoraproject.org present a more filtered view, just as the
> main Fedora repos represent a filtered view of the upstream software
> repositories.
> My rationale for that is that DA provides an abstraction layer over
> various mundane technical details - if you're using a well-maintained DA
> Assistant to automate setting up a particular kind of project, then your
> own practices can automatically adapt as recommendations change...
Good point. I didn't think about it this way.
>...If
> folks want to learn more about the details of a recommendation, they can
> dig into the implementation of the relevant assistant, but if they don't
> want to care, they don't have to.
> The DA folks are also actively working on offering good support for the
> "Container Tools" workflow coming out of Project Atomic - that's a
> Vagrant+containers based approach designed to be cross-platform for
> development purposes and cross-distro for both development and
> deployment, so adopting it for web service development means folks are
> automatically lowering the barriers to entry to contributing to and
> deploying their project. That workflow also actively encourages folks to
> clearly separate their unit testing from their behavioural testing.
> Given a default assumption that folks are willing to use DevAssistant
> (either through the GUI or through the CLI), then the following kinds of
> questions could help guide site users to appropriate assistants:
> * I want to build a web application, where do I start?
> * I want to build a command line application, where do I start?
> * I want to build a desktop GUI application, where do I start?
> * I want to build a mobile application, where do I start?
> * I want to work with the Raspberry Pi, where do I start?
> * I want to work with Arduino devices, where do I start?
> * I want to work with other embedded devices, where do I start?
> * I want to provide online documentation for my project, where do I start?
> * I want to collaborate effectively with others on my project, where do
> I start?
> That last one wouldn't be a pointer to any DA Assistants, but rather a
> pointer to resources like choosealicence.com, and a review of some of
> the available project hosting options (most notably GitLab, GitHub,
> BitBucket and FedoraHosted)
I really like the point about collaboration and choosing a license. It's
essential and I totally missed it in the initial plan.
> P.S. A note regarding the Raspberry Pi: I think this is a good example
> of a case where cross-distro development support is important, as we'd
> like to make it easy for folks to develop for the Raspberry Pi on Fedora
> while targeting both the default Raspbian image and the Fedora Pi remix,
> rather than only supporting developing for the latter.
I like the hidden message in this note: "We don't want to vendor-lock you
to Fedora. We want you to use it because it helps you, not because
you have to."
----- Original Message -----
From: "Nick Coghlan" <ncoghlan(a)redhat.com>
To: "Adam Samalik" <asamalik(a)redhat.com>, "Development discussions related to Fedora" <devel(a)lists.fedoraproject.org>
Cc: "Fedora Environment and Stacks Working Group mailing list" <env-and-stacks(a)lists.fedoraproject.org>, duffy(a)redhat.com
Sent: Monday, 27 July, 2015 6:41:40 AM
Subject: Re: Fedora developer portal - proof of concept
On 07/24/2015 07:16 PM, Adam Samalik wrote:
> Hi Nick,
>
> thanks!
>
> What I'm still missing in the current prototype is the "problem to be solved" starting point - as you pointed out at the env-and-stacks meeting. For example: I want to develop a web application. The site would give me options like Django, Flask, Ruby on Rails, PHP, Jekyll,... Or even better, something more precise like deciding the type of the web app: an application with backend and database, a static site, blog or a wiki page? The tech-specific overview would show up afterwards. Suitable tools and deployment option would show up as well. What do you think?
I think it probably makes sense to focus on http://devassistant.org/ and
https://dapi.devassistant.org/ as the entry points to the Fedora
developer experience. We may want to pick out particular assistants and
highlight them (especially if we design the Fedora DA package to come
with some assistants pre-installed), but I think it makes sense to push
the "comprehensive" side of the story further upstream, and have
developers.fedoraproject.org present a more filtered view, just as the
main Fedora repos represent a filtered view of the upstream software
repositories.
My rationale for that is that DA provides an abstraction layer over
various mundane technical details - if you're using a well-maintained DA
Assistant to automate setting up a particular kind of project, then your
own practices can automatically adapt as recommendations change. If
folks want to learn more about the details of a recommendation, they can
dig into the implementation of the relevant assistant, but if they don't
want to care, they don't have to.
The DA folks are also actively working on offering good support for the
"Container Tools" workflow coming out of Project Atomic - that's a
Vagrant+containers based approach designed to be cross-platform for
development purposes and cross-distro for both development and
deployment, so adopting it for web service development means folks are
automatically lowering the barriers to entry to contributing to and
deploying their project. That workflow also actively encourages folks to
clearly separate their unit testing from their behavioural testing.
Given a default assumption that folks are willing to use DevAssistant
(either through the GUI or through the CLI), then the following kinds of
questions could help guide site users to appropriate assistants:
* I want to build a web application, where do I start?
* I want to build a command line application, where do I start?
* I want to build a desktop GUI application, where do I start?
* I want to build a mobile application, where do I start?
* I want to work with the Raspberry Pi, where do I start?
* I want to work with Arduino devices, where do I start?
* I want to work with other embedded devices, where do I start?
* I want to provide online documentation for my project, where do I start?
* I want to collaborate effectively with others on my project, where do
I start?
That last one wouldn't be a pointer to any DA Assistants, but rather a
pointer to resources like choosealicence.com, and a review of some of
the available project hosting options (most notably GitLab, GitHub,
BitBucket and FedoraHosted)
Regards,
Nick.
P.S. A note regarding the Raspberry Pi: I think this is a good example
of a case where cross-distro development support is important, as we'd
like to make it easy for folks to develop for the Raspberry Pi on Fedora
while targeting both the default Raspbian image and the Fedora Pi remix,
rather than only supporting developing for the latter.
--
Nick Coghlan
Fedora Environments & Stacks
Red Hat Developer Experience, Brisbane
Software Development Workflow Designer & Process Architect
5 years, 7 months
[Test-Announce] Proposal to CANCEL: 2015-07-27 Fedora QA Meeting
by Adam Williamson
Hi folks! Sorry for the late notice, but I'm proposing we cancel
Monday's QA meeting. I think we covered everything in the last couple
of weeks' meetings, and it's time to get some serious testing done on
Alpha TC2 :)
I guess there'll be a blocker meeting at 1600 UTC.
If anyone can think of something urgent to discuss, please reply to
this mail and we can get together at the usual time (15:00 UTC in
#fedora-meeting).
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
5 years, 7 months
Hello :)
by Carlos Morel-Riquelme
Hello to everyone, my name is Carlos i'm from Chile and I've fedora
collaborator in QA since F20. but now i want collaborate as maintainer
package. well I've create my first review request. it's a library for
shortening of URL page.
https://bugzilla.redhat.com/show_bug.cgi?id=1246974
i would appreciate any help !!
My best regards !!!
5 years, 7 months
Self Introduction: Avram Lubkin
by Avram Lubkin
Hello, I'm Avram. I just submitted my first package, python-scandir. I've
been a system engineer working with Linux for the last 10 years. Several
years ago, in what seems like another life, I worked for Red Hat. Now I'm
an independent consultant while I work on a project I'll be releasing as
open source in the not too distant future. I cut my teeth in large
enterprises so I focus heavily on security and scalability.
In the non-computer world, I like to rock climb, hike, cook vegan food, and
do ultralight traveling.
https://bugzilla.redhat.com/show_bug.cgi?id=1245845
5 years, 7 months
New openCOLLADA built for rawhide
by Richard Shaw
I wasn't aware the openCOLLADA picked up a new dependent, libreoffice. I
was used to it just being blender!
The latest blender, 2.75 would not build with the version in Fedora so an
update was necessary.
I'm still waiting on a response from the blender maintainer on which
branches he wishes to update. I'll add openCOLLADA to a buildroot override
for the other branches. I may need the help of a provenpackager to push
everything in one update.
Thanks,
Richard
5 years, 7 months
BBS
by Byron Steele
homerun2131(a)gmail.com
5 years, 7 months