GCompris and xo-1
by Leonardo Rojas
Hello
First of all, sorry if my english its not very goods since its not my native
languaje. I need to modify some GCompris activies and install them on a xo-1
with
Build number:852 Sugar: 0.84.16 Firmware : Q2E45
because the teachers dont like all the activities as they are, there are
some activities that are easy to modify because i can do the changes with
gcompris administration, like GCompris MissingLetter, but for the others i
need to recompile them. I made changes on several, like MemoryEnumerate,
AlgebraGuesscount, Babymatch and others, then i run gcompris, and all the
changes are there, the activities work as intended but when i try to install
them on the xo, they dont start, i dont even get the
Cannot find cached 0sugar-launch implementation. or another error (i know a
workaround for the 0sugar-launch imlmentation error, i get this error with
version 13 of activities mostly, all version 12 activities run perfect in
the xo
the icon appears then afther a while the activitie close, i tried using the
./bundleit.sh and using setup.py, tried using GCompris 9.5 then Gcompris
9.3 (modifying the source files from the activities that come in that
GCompris version)
So my question is, someone knows how to compile and install a modified
GCompris activity in this xo?, really need help plz, im suposed to have them
installed and working on the xo next week.
sorry for the inconvenience
thx, bye
13 years, 2 months
localpkg helper script for fedpkg
by Martin Langhoff
If you are using or experimenting with fedpkg, I am putting some
simple helper bits in an accessory "localpkg" python script (at
http://dev.laptop.org/git/users/martin/localpkg or
git://dev.laptop.org/users/martin/localpkg ).
It currently has some helpers that allow me to build straight from a
git checkout. Useful for tiny, non-upstream codebases that pack their
own spec file.
Uses git-describe so it will build a properly named rpm if you are on
a named tag. Otherwise it builds with a version name that includes the
commit hash.
localpkg --help
usage: locakpkg [-h] [--path PATH] [-v] [-q]
{setver,git-source,help,publish-xs} ...
Local Packaging utility
optional arguments:
-h, --help show this help message and exit
--path PATH Directory to interact with instead of current dir
-v Run with verbose debug output
-q Run quietly only displaying errors
Targets:
{setver,git-source,help,publish-xs}
help Show usage
setver Set the version in spec from git describe
git-source Get the source for current HEAD from local git, and
update sources file
publish-xs Publish RPMs to XS repo
How do I use it?
- hack on the source
- commit. it is safe to ignore version change in spec file
- fixup the version in spec to match git-describe
$ localpkg setver
- get tarball from git, update 'sources' file
$ localpkg git-source
- build the rpms, locally or on koji - here I request a local build
$ fedpkg local
- copy to the right spots
$ localpkg publish-xs
These things are fairly "local" -- hence no fedpkg patches of interest
I suspect.
cheers,
m
--
martin.langhoff(a)gmail.com
martin(a)laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
13 years, 3 months
Status of bios-crypto packaging?
by Martin Langhoff
Daniel, list,
what's the status of this? I had prepared a rough spec long ago (which
I use for the XS), but we have a couple of issues
- Desire to split off the 'audited' version of libtomcrypt -- the
split in itself is worthy, but ISTR we lost steam pushing it upstream
due to pushback on the 'audited' part? Do we have our package for
that?
- A pile of scripts used in XS that see a lot of churn -- I'm happy
to split those off to a -tools or -scripts subpackage.
cheers,
m
--
martin.langhoff(a)gmail.com
martin(a)laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
13 years, 3 months
Brief (and early) ode to fedpkg
by Martin Langhoff
I was a git hacker, so the noise around fedpkg drew my attention. Now
that I'm working on preparing some patched and custom RPMs for OLPC's
XS, I am starting to use it, and I have to say, it rocks.
Haven't heard other OLPC'ers talk about it... if you're not using it,
it's worth a good shot.
What's so good? With the old CVS, it was hard to prep a 'forked' spec,
say adding 2 patches to it, and track Fedora's CVS. And the Fedora
specs relied on a 'common' set of scripts that were pulled from CVS
too, so if you put the spec in git, it wouldn't build.
Many olpc packages ended up with odd and disparate makefiles to make
building them "easier". That's ended up being a drag, each package has
its own build infra, and they all differ from Fedora's.
Fedpkg has consolidated Fedora's common stuff into its code, so all
you need is a git checkout with a spec file and some patches right
there. And it'll build your stuff, locally, via koji, whatever.
Real Nice.
And it's a much smoother path to get the packaging itself into Fedora
(or EPEL, as it's more likely with my stuff).
cheers,
m
--
martin.langhoff(a)gmail.com
martin(a)laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
13 years, 3 months
Re: Brief (and early) ode to fedpkg
by Bernie Innocenti
On Mon, 2011-01-24 at 16:46 -0800, Jesse Keating wrote:
> That's a bit of a struggle, as there are times when you want something
> in the scm changelog that isn't really appropriate for the rpm
> changelog, like fixing a typo in the specfile between build attempts.
> We do provide the clog facility so that one can re-use the spec
> changelog for the SCM changelog when appropriate. I've also explored a
> bit using a %include directive to include contents from a changelog
> file, one that might be auto-generated from source control, but I didn't
> go very far with it.
>
> Basically I view the scm changelog as data that is relevant and
> important to your fellow maintainers, where as the rpm changelog is
> data that is relevant and important to the rpm consumers. While there
> is some overlap, they are not the same consumers.
The old KDE 1.0 CVS repository used a sophisticated commit hook which
would interpret tags in the comments such as CVSSILENT, CVSFEATURE or
CVSSECURITY to suppress the notification email or add more recipients on
cc.
Couldn't we do something similar for suppressing entries we don't want
to see in the package changelog?
Besides: the changelog feature of rpm always stroke me as something
so... gross! It is part of the package metadata, but due to size
considerations it's not really part of the primary repodata. For
multi-package specs, you end up with multiple copies of the same
changelog in the rpm database. Moreover, RPM-based distributions use
different incompatible formats for %changelog! Not to mention that the %
changelog section is where you get 90% of the merge conflicts when
porting changes between branches.
By contrast, .deb packages simply include a compressed text
file: /usr/share/doc/$PKG/changelog.gz. Why couldn't we switch to
something similar and thus remove a lot of complexity from the rpm
toolchain? (the package changelog is maintained manually, but Debian
doesn't have a distro-wide package VCS).
I'm just throwing around a bunch of ideas to think about... simplifying
the fedora packaging workflow is an important goal, imho.
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
13 years, 3 months
Rafael Ortiz te ha dejado un mensaje...
by Sammy
Rafael Ortiz te ha dejado un mensaje...
El mensaje y la persona que lo envió solo te será mostrado a ti y borrarlo en cualquier momento. Puedes responder a través del sistema de intercambio de mensajes. Para descubrir quién te escribió, sigue el siguiente link:
http://us1.badoo.com/01142074967/in/ht6Yv8pju5U/?lang_id=7
Más gente que también te está esperando:
Rubendario (Bogotá, Colombia)
Miryam (Bogotá, Colombia)
Camilo (Bogotá, Colombia)
http://us1.badoo.com/01142074967/in/ht6Yv8pju5U/?lang_id=7
Si al pulsar el enlace de este mensaje no funciona, copia y pégalo en la barra de tu navegador.
Este email es parte del procedimiento del sistema para el envío de mensajes enviados por Rafael Ortiz. Si has recibido este mensaje por error, ignora este email. Tras un corto periodo de tiempo, será eliminado del sistema.
¡Divértete!
El equipo de Badoo
Has recibido este email porque un usuario de Badoo te ha dejado un mensaje en Badoo. Este mensaje es automático. Las respuestas a este mensaje no estan controladas y no serán contestadas. Si no quieres recibir más mensajes de Badoo, háznoslo saber:
http://us1.badoo.com/impersonation.phtml?lang_id=7&mail_code=21&email=fed...
13 years, 3 months