Etch was released at beginning of 2007 which makes it about 3 years old. Adding release freeze means that software has ~3.5 year now.
I know that for Maemo5 it is fresh new stuff (as there are pre-Etch components in rootfs) but I hope that at least Maemo6 will finally be rebased to something more fresh (Lenny for example).
I think that answers my query as to why you would port from Etch!
Since Lenny already has components for the armel architecture, I would expect Maemo 6 to be based on that.
Maybe I am missing something here, but Debian Lenny has armel packages. I have used the lenny repository on the N900 to install a few things e.g. Nano, Aircrack, and macchanger. I guess there may be more packages in your repository :/
Actually rebuilding them against the same root/libraries as are on the device is far cleaner and less likely to have conflicts.
This is known to have the correct path, so you don't have to (and shouldn't) change anything.
Sorry, no.
As I posted above the program manager fails in adding that catalog.
Did anyone get it working?
If I try apt-get update with that catalog apt-get complains about an parse error (see above).
As I understand it dist and component must be set in a catalog.
...and the corresponding direcories must exist on the repository server.
Or you leave component/dist empty and put the repo in the root dir.
Could you post the URL of the binary packages?
I couldn't find them under http://obra.freemoe.org
Some are under sources (?!) but not all.
If I try apt-get update with that catalog apt-get complains about an parse error (see above).
As I understand it dist and component must be set in a catalog.
...and the corresponding direcories must exist on the repository server.
Or you leave component/dist empty and put the repo in the root dir.
Could you post the URL of the binary packages?
I couldn't find them under http://obra.freemoe.org
Some are under sources (?!) but not all.
I've the same issues as asys3 here, throws an error when installling.
I was able to reproduce it now. (Note if you actually say what the exact error is, it helps.)
I just added a trailing "/" to the URL and it works as before.
(That said, I do have a pretty crappy directory layout for all this--it really wasn't meant to be a main repo, but just a first dumping ground of the builds.)
