Hi,
Vagrant has helped me to setup building the packages and putting them
into the repository, and he suggested one small change for out
GIT-Packages:
debian/source/format should be set to "3.0 (native)"
debian/changelog should have the version without the "-1" at the end.
aTc, could you please fix that for the packages you already pushed?
Thanks :)
--
Mit freundlichen Grüßen,
Michael Mrozek
-----------------------
OpenPandora GmbH
Geschäftsführer: Michael Mrozek
Schäffbräustr. 11
85049 Ingolstadt
Deutschland
Tel.: 0841 / 13 177 33
http://www.openpandora.de/
HRB 4879, Amtsgericht Ingolstadt
-----------------------
eMail: mrozek(a)openpandora.org
Hi,
based on the help Vagrant gave me, I tried to create a script to
automatically build our packages (if need be) and put them into the
repository.
What the script does is:
1. Read out GITs from a file (packages.txt, example included)
2. Clones the GIT if it doesn't exist
3. Updates the GIT if it already exists
4. Reads out the package name and builds the package if the GIT had
been updated
5. Included the built package into the repository
Could you all have a quick look at the script and let me know if you
find anything that could cause issues?
Thanks :)
--
Mit freundlichen Grüßen,
Michael Mrozek
-----------------------
OpenPandora GmbH
Geschäftsführer: Michael Mrozek
Schäffbräustr. 11
85049 Ingolstadt
Deutschland
Tel.: 0841 / 13 177 33
http://www.openpandora.de/
HRB 4879, Amtsgericht Ingolstadt
-----------------------
eMail: mrozek(a)openpandora.org
If I remember correctly,
some of you have connected a SATA drive to the OMAP5432EVM?
Does it work with the mainline 3.17 kernel or does it need additional drivers/configs/udev rules?
BR,
Nikolaus
The repository is now up and running:
http://packages.pyra-handheld.com/
To use it, add the following to the sources.list:
deb http://packages.pyra-handheld.com/debian jessie-armhf main
We have not yet setup a key to sign the packages.
And we have not yet setup the rootfs-building with all our packages and
our kernel, but that should follow soon.
--
Mit freundlichen Grüßen,
Michael Mrozek
-----------------------
OpenPandora GmbH
Geschäftsführer: Michael Mrozek
Schäffbräustr. 11
85049 Ingolstadt
Deutschland
Tel.: 0841 / 13 177 33
http://www.openpandora.de/
HRB 4879, Amtsgericht Ingolstadt
-----------------------
eMail: mrozek(a)openpandora.org
Here's a test image for ubuntu trusty.
I decided to go with that, since debian testing has been moving in and
out of a broken state for the last few weeks.
http://next.openpandora.org/ubuntu/pyra-ubuntu-trusty.tgz
It doesn't come with a full installer, it's basically just a rootfs that
needs to be placed on an sd card with a working boot partition.
(just rm *-rf/reformat an working sd card's rootfs partition, and
extract the archive to it, as root)
You can edit /pyra-ubuntu-config.sh to set up a username/password/root
password/hostname (defaults to root:root, and pyra:pyra for now)
On the first boot, it will run all the config scripts for the installed
packages (takes quite a while, same as the pandora firmware. I recommend
installing the rootfs on a usb or sata drive to speed things up), and
set up some basics (which should be handled by a dedicated
first-run-wizard later on).
You will see a few error messages, but they're not serious (it's mostly
dpkg giving an error when a package has already been configured)
The only thing going wrong in this version is nfs-common not beeing
configured properly (I just added that to the dependencies, I'll have to
dig around for a fix)
A kernel/modules aren't included, so you'll have to add those to
/lib/modules for whatever kernel you're booting (config script takes
care of running depmod), although most kernels should run fine without
modules installed (in fact, the one im using gives a lot more problems
when I tries to load the alsa modules)
What I need now is a kernel + source with working sgx modules/libs/xorg
config.
Lists of extra packages that should be installed, custom versions that
need to be compiled, or config files that need changing to get all the
hardware working are also welcome, so I can turn them into proper
packages and add them to the list of dependencies.
Currently the image is built based on these meta packages:
Package: pyra-meta-base
Depends: net-tools, nano, openssh-server, apt, apt-utils, dialog, kmod,
sudo, wpasupplicant, wireless-tools, man-db, manpages, netbase, wget,
usbutils, cpufrequtils, alsa-base, alsa-utils, less
Description: Minimal requirements for the pyra firmware (meta-package)
Package: pyra-meta-desktop-base
Depends: pyra-meta-base, xorg, desktop-base, fonts-liberation,
xfonts-terminus
Description: minimal requirements for a graphical pyra firmware
(meta-package)
Package: pyra-meta-develop
Depends: build-essential, u-boot-tools, kernel-package, libncurses5-dev,
git-buildpackage, cowbuilder, pbuilder, ccache, eatmydata, dh-make,
debhelper, multistrap
Description: Dependencies for pyra firmware and application development
(meta-package)
Package: pyra-meta-extra
Depends: ntpdate, lm-sensors, htop, tmux, hdparm, rsync, nfs-common
Description: useful, but not essential extra packages for pyra
(meta-package)
Package: pyra-meta-xfce
Depends: pyra-meta-desktop-base, xfce4, xfce4-goodies,
network-manager-gnome, slim, firefox
Description: XFCE desktop for pyra (meta-package)
pyra-meta-kde also exists, which just depends on pyra-meta-desktop-base
and kde-standard, but that isn't used for this image (and is untested)
Any ideas for additional meta packages are welcome too of course.