Originally Posted by AapoRantalainen

I'm so excited about this. I'm planning something like this:

Add to /etc/apt/sources.list

Code:

deb-src http://repository.maemo.org/ fremantle/sdk free
deb-src http://repository.maemo.org/ fremantle/tools free
free
deb-src http://repository.maemo.org/community-testing/ fremantle free

deb-src http://repository.maemo.org/extras-devel fremantle free

and then:

Code:

apt-get source libhildon1
dpkg-buildpackage
-> missing bunch of stuff
apt-get install .... (from jessie) 
dpkg-buildpackage
fix-the-code

And then some other packages which 'are part of fremantle, but not yet (or anymore) in debian'.

I'm open for comments.

Originally Posted by AapoRantalainen

Another idea (which is not yet working): add your secret nokia-binaries-key to the /etc/apt/sources.list

Code:

deb http://repository.maemo.org/ fremantle/SECRET nokia-binaries

And then

Code:

apt-get install X
or
apt-get download X

where X is 'really useful but not yet liberated'-package from:
http://wiki.maemo.org/Fremantle_closed_packages

But apt-get update encounter error, because it is looking for

http://repository.maemo.org/dists/fr...naries/binary-armhf/Packages
but file on the server is
http://repository.maemo.org/dists/fr...naries/binary-armel/Packages
(verified with wget)

This armhf is not part of the deb-row, so is it resolved runtime, maybe by dpkg-architecture? So how to spoof it? (I haven't yet tested is there any possibility they could work at all)