Archive for category sabayon linux
I’m not a python developer myself at all, but I was just curious about the great codebase that Fabio wrote and documented.
Knowing I have the repository database on my hard disc I figured it should be simple to let it list the last 100 changed packages.
This is how its done:
#!/usr/bin/python # -*- coding: iso-8859-1 -*- from entropy.client.interfaces import Client import time client = Client() repo = client.open_repository("sabayonlinux.org") cur = repo._cursor().execute for row in repo._cursor().execute('SELECT `extrainfo`.`datecreation`,`baseinfo`.`atom` FROM `baseinfo`,`extrainfo` WHERE `baseinfo`.`idpackage` = `extrainfo`.`idpackage` ORDER BY `extrainfo`.`datecreation` DESC LIMIT 100'): my_time = float(row) human_time = time.strftime("%a, %d %b %Y %H:%M:%S +0000", time.localtime(my_time)) print human_time,' ',row client.shutdown()
If you want to know about the table layout, visually, you can use dev-db/sqlitebrowser
The database is located here:
For the record I want to explain how to get 5.2 (as soon its out) can be installed successfully on a macbook 5.2 .
I take it one knows about refit, if not RTFM.
The first thing todo when booting the LiveDVD is edit the boot parameters and append: maxcpus=1 . Otherwise the kernel will panic (acpi issue).
Alternatively you can just disable all acpi but this will not do any good for day2day usage of the macbook.
Ok we start installer and we create 1 partition /dev/sda3 I used ext4, works just fine.
In the installer you need to check a box for advanced grub options and
select to NOT install it in MBR but in /dev/sda3 instead.
Personally I think this step actually is a bit buggy because after a
succesfull installation and syncing partition tables in refit you will
get a message that there is no operating system found if you try to
boot the linux partition. This is because it seems that grub2 actually
didn’t install there at all.
To fix this I booted live again to manually install grub here are the
excact steps todo it:
open a terminal, become root
– mkdir sabayon && mount /dev/sda3 sabayon
– mount -o bind /proc sabayon/proc
– chroot sabayon
– grub2-install /dev/sda3 –force (I guess its this step where it went /dev/null during installation process)
– equo update && equo install grub (this will auto generate the shiny
sabayon grub2 theme and detect the kernels)
Now reboot and there it is. Keep in mind that you still might need to append the maxcpus=1 flag to your line, to perm edit that line you can have a look in /boot/grub/grub.cfg
This version will eventually never make it in the main repositories.
It can have some bugs and crashes. If you want to give it a try just do with limbo attached equo install kde-meta.
Incase you get a masked package remember that you can unmask packages like this:
echo “media-libs/gluon-9999” >> /etc/entropy/packages/package.unmask
(this post was written in Blogilo, a program that ships with KDE 4.4)
You use your Sabayon Desktop to your taste and you kinda always want to install the same thing when you freshly install Sabayon. Taken this idea there are sets you can create yourself or use the provided ones from entropy.
- Make sure you have latest entropy version on branch 4
- equo hop 5
- equo update
- equo upgrade
At this point of writing it feels like the branch is fairly in shape enough. I’ve added KDE 4.3 RC2 from kde-testing overlay to work towards the final KDE 4.3 release.
- Do I realise that I’m about to download 800 – 1000 packages and I have enough free disc space to survive that operation.
- It’s important, since its a binary tree, that you complete equo upgrade (or what we used to call equo world)
- I’m not sure when the migration tools will be implemented but since we jumped to Python 2.6 you need to check eselect python list and see if its set to this.
- You will most likely need to equo install gcc and run gcc-config and set it to the latest gcc version
- You need to run binutils-config to manauly select a profile.
- The lowest kernel is a 2.26.30 you need to check with eselect kernel if its set to it and maybe manualy add the entry in /boot/grub/grub.conf
- Right now there is no new artwork available in branch 5 so it will kinda look the same.
About 3 weeks ago i started work on branch 5 for Sabayon 5 and i must say that i made good progress! So i hear you ask, what it means a “branch” well let me try to explain how it all works.
As you might already know, Sabayon Linux is based on Gentoo Linux.
Now in Italy we have this huge computer that hosts basically 2 enormous Gentoo installs, we call these “chroots”. It’s 2 chroots because we support 2 architectures amd64 and x86. So as you might guessed, yes all packaging that goes into entropy is done twice. These 2 chroots form one branch.
How i do it? Well I simply login the Italian server and connect to one of the chroots. When I log in to a chroot ( yes its the chroot command, but we saved them in screen sessions to get access to them quickly ) I use all the commands any Gentoo user would. I operate my make.conf, package.use and package.mask files to have my enormous tree compiled to be best performing for a great amount of machines and people. Day to day i check for relevant packages that we want to have updated in e.g. Entropy. When i’m done emerging those updates and their depends i use tools written by Fabio Erculiani aka “Lxnay” to create packages. This is done fully automatically and there is nothing difficult about that really. So once its all packaged and i did my quality checks its all ready to get pushed out to the people as I say. From the server in Italy things get uploaded to the distribution server from where everything, again automatically, gets spread to servers world wide. Pretty cool huh?
So we have these chroots I’m working on day 2 day and at a certain point there are some important updates that require allot of packages to be recompiled. Think of a new python version, new xorg version and some other lower-level stuff like the compiler itself.
At some point it just makes sense to stop doing the day 2 day updates, copy the whole thing and from the copy do the important updates and the heavy recompiling. This new copy would be the new branch. Does it mean that the previous branch is closed? Well basicly from my side it is, i only do updates on it when there are security risks involved, we are Linux and we want to keep people safe. The goal is to keep the old branch available to users for at least a year. This will give them the time to migrate to the new branch. (By either installing a new DVD release or use equo hop to jump into the new branch.) So yeah, its possible to keep on working on the same system and just hop into the new branch.
When a new branch is created and the first disc is released there are already newer updates almost everyday. At some point it would be enough to trigger like 300 updates after a new install on a users pc. This can be even within 6 weeks or so. At some point we create a new snapshot which is basically as much as : Take Release 1, equo upgrade it to the latest available packages, put is all on a disc.
So yeah, we are a true rolling distribution!