maemo.org - Talk - Easy Debian Fremantle Beta Testing

maemo.org - Talk (https://talk.maemo.org/index.php)

- Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)

- - Easy Debian Fremantle Beta Testing (https://talk.maemo.org/showthread.php?t=34550)

Re: Easy Debian Fremantle Beta Testing

Just a request, not a demand:
If you create images based on mine, could you please NOT put "sulu" in the file name?

I've had some requests for help with "my" images, but since I usually don't try other images I don't really know what's going on there.
If YOU create an image, then it is YOU who deserves the credit (and needs to take the blame ;) ). So people should first turn to you if they need help.
I'll happily help out if I can, but I don't like to stand in the first line in these cases.

Thanks!

Re: Easy Debian Fremantle Beta Testing

I certainly don't think I contributed enough to call it mine, but it is fine by me to rename it. I haven't seen any posts about problems or questions about the image. I can only assume it is working without issues then...

Will remove the mediafire link this weekend so there is only one 'official' link to the file from qole.

Re: Easy Debian Fremantle Beta Testing

What is the passwords for user and root in debian_jessie2sulu_armhf.img?

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by baranovskiykonstantin (Post 1516081)

What is the passwords for user and root in debian_jessie2sulu_armhf.img?

If t-b didn't change the passwords, then they should be "user" and "root".

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by sulu (Post 1516099)

If t-b didn't change the passwords, then they should be "user" and "root".

I tried to use them. They are not correct.

Re: Easy Debian Fremantle Beta Testing

As far as I know I haven't changed any passwords - because I didn't need them. I used debian chroot for root access (no pw needed) and also user can be accessed without pw.

Can't test right now due to a recent re-install.

Re: Easy Debian Fremantle Beta Testing

It happens when I use terminal from lxde session. When debian chroot are used password not needed, it is true.

P.S.

Ok,user just not setup. Password must be set with

Code:

$ sudo passwd user

from debian chroot and to add it to sudoers with

Code:

$ sudo visudo

Re: Easy Debian Fremantle Beta Testing

Hello,

First of all I would like to say thanks for the images and the effort put in this.

I have a little problem coming from my side and I would need a little bit of help.

I already used Easy Debian on my previous N900 without any real issue, but today I tried to set it up on my second N900 on which I have made some significant changes.
So I will detail here the changes I made on my second N900 (and are related somehow to Easy Debian) and the error message I get when I try to launch an image.

First the error is :

Code:

~ $ debbie

Starting Debian shell...

Chroot dir specified: /.debian

No image file or partition specified.

ls: /home/user/MyDocs/debian*.img*: No such file or directory

/.debian has a qmount already!

/media/mmc1/debian_jessie2sulu_armhf.img already mounted on /.debian...

Everything set up, running chroot...

chroot: can't execute 'su': Exec format error

So apparently a problem with su.

The changes I've made to the second N900 (basically I wanted for the root password to be required for becoming root) :

Code:

/etc/sudoers.d/01sudo

user ALL = PASSWD: /usr/sbin/gainroot



/home/user/.profile

alias su='root'

I also had to change /etc/sudoers.d/chroot.sudoers from

Code:

Defaults env_keep+=GTK_MODULES

user ALL = NOPASSWD: ALL

Code:

Defaults env_keep+=GTK_MODULES

user ALL = NOPASSWD: /sbin/debian

so that the root password is required when using su (or root) command, but even without changing the chroot.sudoers file it still gives the error.

How can I correct this without giving away the security put in place (root password required to become root)?
Should I put something else in /etc/sudoers.d/chroot.sudoers?

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by Malakai (Post 1518142)

I already used Easy Debian on my previous N900 without any real issue, but today I tried to set it up on my second N900 on which I have made some significant changes.
So I will detail here the changes I made on my second N900 (and are related somehow to Easy Debian) and the error message I get when I try to launch an image.

First the error is :

Code:

chroot: can't execute 'su': Exec format error

I've got the same error after installing a back-up image (created with BackupMenu) on a 2nd N900 I am using.
Everything works fine except Easy Debian. Not sure if it is a "su problem", the "Exec format error" part of the error seems to point to a kernel incompatibility.

Haven't had a lot of time to investigate the problem and interested in a solution as well.

Re: Easy Debian Fremantle Beta Testing

Are your N900s running kernel power? The armhf images need it.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by sulu (Post 1518265)

Are your N900s running kernel power? The armhf images need it.

Yes, I think that is the problem as well. I think kernel power was not copied from the original N900 using backup menu so probably needs to be (re-)installed or fixed. Haven't got access to the backup N900 right now, so cannot do a uname -r to check.

Last time I used the backup N900 I checked the application manager and I only had the option to un-install kernel power so it appeared to be installed. Didn't check the kernel version then.

Maybe I need to do a re-install.

apt-get install --reinstall -y kernel-power kernel-power-flasher

Will give it a try tomorrow.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by sulu (Post 1518265)

Are your N900s running kernel power? The armhf images need it.

No kernel power for me on my second N900.
Will look into this next days as I don't have time right now.
We will see if it works after installing kernel power.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by t-b (Post 1518271)

apt-get install --reinstall -y kernel-power kernel-power-flasher

Will give it a try tomorrow.

I can confirm this worked. Backup menu is not copying the kernel (seems kinda obvious in hindsight) but using the reinstall option works fine.

Re: Easy Debian Fremantle Beta Testing

Just had time to try this, and I also confirm that once kernel power installed the armhf image works.

Thanks.

Re: Easy Debian Fremantle Beta Testing

Hey,

I seem to have some trouble to upgrade debian_jessie2sulu_armhf image.
At first when I did a "apt-get update && apt-get upgrade" I had an error of this kind (translating to English, so the error message could be different but the idea is the same) :

Code:

dpkg : unrecoverable fatal error, abandon

group crontab unknown in the permissions file (statoverride)

E: Sub-process /usr/bin/dpkg returned an error code (2)

So after some research I did as root :

Code:

mv /var/lib/dpkg/statoverride /var/lib/dpkg/statoverride.bak

And the problem seemed to be solved, but now I have a second error about libc6_2.19-18+deb8u6_armhf.deb :

Code:

WARNING: this version of the GNU libc requires kernel version 2.6.32 or later. Please upgrade your kernel before installing glibc.

The installation of a 2.6 kernel _could_ ask you to install a new libc first, this is NOT a bug, and should *NOT* be reported. In that case, please add lenny sources to your /etc/apt/sources.list and run:

apt-get install -t lenny linux-image-2.6

Then reboot into this new kernel, and proceed with your upgrade

Should I do that? From what I know the Debian image is using the Maemo kernel (?) so I can't really upgrade that (true?). How to solve this, because I can't upgrade the system and can't install new packages.

Has anyone any idea?

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by Malakai (Post 1518994)

And the problem seemed to be solved, but now I have a second error about libc6_2.19-18+deb8u6_armhf.deb :

Version of libc in the image is created by sulu and is version glibc_2.19-18+deb8u4. glibc is updated in the repo but it is not compatible with the kernel that is why we needed sulu to create a compatible version before.
For now I suggest to ignore the update and put the package on hold (I probably should have done that in the image..).

Changes are mentioned below - not sure if the updates are really needed.
https://launchpad.net/debian/+source...2.19-18+deb8u6

Re: Easy Debian Fremantle Beta Testing

What a coincidence!
Just this week I tried to create a first Stretch image, and took the chance to also build some new glibc packages for Jessie. [1]

As for Stretch, I have bad news. Stretch comes with glibc 2.24 and some essential software in Stretch makes it mandatory to ship at least 2.23. I managed to build 2.23 for kernel 2.6.28, but actually running that build on the Maemo kernel immediately causes a segfault.
So unless someone (certainly not me) plans to either bring a more recent kernel to Maemo (at least 2.6.32, preferably 3.2 or newer), or restores glibc's ability to run on kernel 2.6.28 just for us, Jessie will be the last Easy Debian release ever.

[1] http://www38.zippyshare.com/v/TToYMdN7/file.html

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by t-b (Post 1518996)

Even when putting the package on hold I can't seem to install new packages ; I get a dependency error for the following packages : libc6-dbg, libc6-dev, libc6-pic.

And when I want to install vim I get :

Code:

vim : Depends: vim-runtime (= 2:7.4.488-7) but it is not going to be installed

Depends: libgpm2 (>= 1.20.4) but it is not going to be installed



E: Unmet dependencies. Try 'apt-get -f install'  with no packages (or specify a solution).

What should I do now?

Quote:

Originally Posted by sulu (Post 1518997)

What a coincidence!
Just this week I tried to create a first Stretch image, and took the chance to also build some new glibc packages for Jessie. [1]

[1] http://www38.zippyshare.com/v/TToYMdN7/file.html

Sorry to ask a maybe basic question, but what should I do with that package? Or maybe should I ask where to uncompress it?

Quote:

Originally Posted by sulu (Post 1518997)

As for Stretch, I have bad news. Stretch comes with glibc 2.24 and some essential software in Stretch makes it mandatory to ship at least 2.23. I managed to build 2.23 for kernel 2.6.28, but actually running that build on the Maemo kernel immediately causes a segfault.
So unless someone (certainly not me) plans to either bring a more recent kernel to Maemo (at least 2.6.32, preferably 3.2 or newer), or restores glibc's ability to run on kernel 2.6.28 just for us, Jessie will be the last Easy Debian release ever.

Too sad... this will mean the end of an up to date Debian system on our N900... really waiting for the Neo900 now.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by Malakai (Post 1519079)

Even when putting the package on hold I can't seem to install new packages ; I get a dependency error for the following packages : libc6-dbg, libc6-dev, libc6-pic.

Can you post this output please:

Code:

dpkg -l | grep libc

I suspect that some of the packages you want to install depend on the libc6 packages you mentioned. Those are not installed by default and once they get an update from Debian my patched packages won't be compatible anymore.
That's why I upload update archives from time to time. These archives include the full set of patched glibc packages so you can manually install (dpkg -i) them.

Quote:

Originally Posted by Malakai (Post 1519079)

And when I want to install vim I get :

Code:

vim : Depends: vim-runtime (= 2:7.4.488-7) but it is not going to be installed

Depends: libgpm2 (>= 1.20.4) but it is not going to be installed



E: Unmet dependencies. Try 'apt-get -f install'  with no packages (or specify a solution).

What should I do now?

What happens if you run apt-get -f install ?

Quote:

Originally Posted by Malakai (Post 1519079)

Too sad... this will mean the end of an up to date Debian system on our N900...

Well, it was always just a matter of time. Back then I was actually quite surprised that I got Jessie to run at all.
I think in the grand scheme of things we just have to realize that the N900 is a legacy device now, not because it is slow but because its software is basically unmaintainable, and we're hitting increasingly harder walls as time goes on.

The only thing I can offer now is to try to build Jessie backports on demand for software that is available in Stretch.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by sulu (Post 1519184)

Can you post this output please:

Code:

dpkg -l | grep libc

Code:

ii  glibc-doc                          2.19-18+deb8u4                    all          GNU C Library: Documentation

ii  glibc-source                       2.19-18+deb8u4                    all          GNU C Library: sources

ii  libc-bin                           2.19-18+deb8u6                    armhf        GNU C Library: Binaries

iU  libc-dev-bin                       2.19-18+deb8u6                    armhf        GNU C Library: Development binaries

ii  libc6:armhf                        2.19-18+deb8u4                    armhf        GNU C Library: Shared libraries

iU  libc6-dbg:armhf                    2.19-18+deb8u6                    armhf        GNU C Library: detached debugging symbols

iU  libc6-dev:armhf                    2.19-18+deb8u6                    armhf        GNU C Library: Development Libraries and Header Files

iU  libc6-pic:armhf                    2.19-18+deb8u6                    armhf        GNU C Library: PIC archive library

ii  libcairo2:armhf                    1.14.0-2.1+deb8u1                 armhf        Cairo 2D vector graphics library

ii  libcap-ng0:armhf                   0.7.4-2                           armhf        An alternate POSIX capabilities library

ii  libcap2:armhf                      1:2.24-8                          armhf        POSIX 1003.1e capabilities (library)

ii  libcap2-bin                        1:2.24-8                          armhf        POSIX 1003.1e capabilities (utilities)

ii  libcdparanoia0:armhf               3.10.2+debian-11                  armhf        audio extraction tool for sampling CDs (library)

ii  libcomerr2:armhf                   1.42.12-1.1                       armhf        common error description library

ii  libcroco3:armhf                    0.6.8-3+b1                        armhf        Cascading Style Sheet (CSS) parsing and manipulation toolkit

ii  libcryptsetup4:armhf               2:1.6.6-5                         armhf        disk encryption support - shared library

ii  libcups2:armhf                     1.7.5-11+deb8u1                   armhf        Common UNIX Printing System(tm) - Core library

ii  libcurl3-gnutls:armhf              7.38.0-4+deb8u3                   armhf        easy-to-use client-side URL transfer library (GnuTLS flavour)

ii  liblocale-gettext-perl             1.05-8+b1                         armhf        module using libc functions for internationalization in Perl

iU  linux-libc-dev:armhf               3.16.36-1+deb8u1                  armhf        Linux support headers for userspace development

Quote:

Originally Posted by sulu (Post 1519184)

What happens if you run apt-get -f install ?

Code:

dpkg: error processing archive /var/cache/apt/archives/libc6_2.19-18+deb8u6_armhf.deb (--unpack) :

subprocess new pre-installation script returned error exit status 1

Errors were encountered while processing:  

/var/cache/apt/archives/libc6_2.19-18+deb8u6_armhf.deb

E: Sub-process /usr/bin/dpkg returned an error code (1)

Should I install the archive you provided with dpkg -i?

Re: Easy Debian Fremantle Beta Testing

I see you have mixed glibc packages (notice the deb8u4/deb8u6 in your output!).
Where are the deb8u6 packages from? If they are from the official Debian repo then I'd be puzzled that your ED works at all.

Quote:

Originally Posted by Malakai (Post 1519200)

Should I install the archive you provided with dpkg -i?

The archive contains Debian packages. Please try to install these packages with dpkg -i !
The easiest way would be to unpack the archive to an empty directory and then run dpkg -i *.deb in that directory. It will install some packages you don't need but that's only some MB. Maybe afterwards you'll have to run apt-get -f install again.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by sulu (Post 1519209)

Yes, they are from the official Debian repo (didn't touch that part yet, wanted to install vim first and then look to change them but only to find a closer repo to my location, knowing that now it is in Netherlands).
I try to always use the official repos and add another repo only if really needed.
After getting in the chroot I did an apt-get update && apt-get upgrade which got me in this state (I always try to get the system up to date before installing additional packages).

Quote:

Originally Posted by sulu (Post 1519209)

Ok, will try that as soon as possible.

Thanks.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by Malakai (Post 1519269)

I try to always use the official repos and add another repo only if really needed.

That is a very wise approch - except for when you want to run a recent Debian on a kernel from the stone age. ;)

In Easy Debian Jessie (and only here) please avoid any packages from the Debian repo that are build from the glibc source package! [1]
In principle the same is true for pulseaudio, but installing that from Debian will only result in broken sound in the chroot, not in a completely broken chroot.

[1] https://packages.debian.org/source/jessie/glibc

Re: Easy Debian Fremantle Beta Testing

So, I did a dpkg -i *.deb and some packages installed without any issue but the result was :

Code:

dpkg: dependency problems prevent configuration of libc6-dev:armhf:

 libc6-dev:armhf depends on linux-libc-dev; however:

  Package linux-libc-dev:armhf is not configured yet.



...



dpkg: error processing libc6-dev:armhf (--install):

 dependency problems - leaving unconfigured



...



Errors were encountered while processing:

libc6-dev:armhf

And when I try to do an apt-get install vim I get :

Code:

FATAL: kernel too old

Segmentation fault

FATAL: kernel too old

Segmentation fault

dpkg: error processing libc-bin (--configure):

subprocess new pre-installation script returned error exit status 139

Errors were encountered while processing:

dbus

dbus-x11

libc-bin

E: Sub-process /usr/bin/dpkg returned an error code (1)

So I decided to use nano, but when trying to install other packages it works (still giving some errors, but the package installs and is usable), which is related to what you said in your previous post about packages build from the glibc source package.

My first usage of Easy Debian is for web browsing, as some websites don't work at all with Maemo's browser, so I decided to install midori and surf. Those installed without any issue and they are technically working, but frankly it is not the user experience I expect on a mobile device.

All in all, thank you for keeping this alive as much as you can.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by sulu (Post 1519290)

In Easy Debian Jessie (and only here) please avoid any packages from the Debian repo that are build from the glibc source package! [1]

[1] https://packages.debian.org/source/jessie/glibc

Quite a long list...

I already did an
echo "libc6 hold" | dpkg --set-selections
and
echo "libc6-dev hold" | dpkg --set-selections

in my current Easy Debian image but that doesn't seem to be enough then.
What is the best approach to put everything from this list that shouldn't be updated on-hold?

Re: Easy Debian Fremantle Beta Testing

I'm trying to add printer via cups web interface, but no local printers are listed...

lsusb output from maemo:
Bus 001 Device 042: ID 03f0:0604 Hewlett-Packard DeskJet 840c
Bus 001 Device 001: ID 1d6b:0002

lsusb from debian chroot:
libudev: udev_has_devtmpfs: name_to_handle_at on /dev: Function not implemented

I could not find any useful info on google and I really don't want to cram up my rootfs with cups (>60MB!)

Ideas?

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by t-b (Post 1519431)

Not sure if 100% correct, but holding these packages worked for me:

glibc-doc
glibc-source
libc-bin
libc-dev-bin
libc6
libc6-dbg
libc6-dev
libc6-pic
libpulse0
linux-libc-dev
locales-all
pulseaudio
xkb-data

Re: Easy Debian Fremantle Beta Testing

Anybody have patched glibc for latest Ubuntu? I would like to try kwin with xwayland on sailfish but ancient kernel stops me.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by sulu (Post 1446540)

1)
As mentioned in [2] we need to patch glibc to accept Fremantle's 2.6.28 kernel. You'll need an armhf/armel system running at least kernel 2.6.32 to do all this, so doing it on the N900 itself is no longer an option.
I did all of this on my Cubieboard2, which took about 6 hours. Once you have an image running you can create new patched glibc packages on the N900 (if the watchdog doesn't kill it).
I would strongly advise against using qemu, at least if you're over 40 and want it done before you retire.
If you need newer glibc packages and can't create them on your own drop me a note and I'll build them. But it may take a week or so.

a)
On a Debian Jessie armhf (or armel) system get the glibc sources

Code:

apt-get source glibc

b)
change into the created folder and apply the following changes:

This is what dpkg-source recorded of my changes:

Code:

Description: decrease min kernel version to 2.6.28 for Fremantle compatibility



--- glibc-2.19.orig/ports/sysdeps/unix/sysv/linux/tile/configure

+++ glibc-2.19/ports/sysdeps/unix/sysv/linux/tile/configure

@@ -1,4 +1,4 @@

 # This file is generated from configure.ac by Autoconf.  DO NOT EDIT!

  # Local configure fragment for sysdeps/unix/sysv/linux/tile.



-arch_minimum_kernel=2.6.32

+arch_minimum_kernel=2.6.28

--- glibc-2.19.orig/ports/sysdeps/unix/sysv/linux/tile/configure.ac

+++ glibc-2.19/ports/sysdeps/unix/sysv/linux/tile/configure.ac

@@ -1,4 +1,4 @@

 GLIBC_PROVIDES dnl See aclocal.m4 in the top level source directory.

 # Local configure fragment for sysdeps/unix/sysv/linux/tile.



-arch_minimum_kernel=2.6.32

+arch_minimum_kernel=2.6.28

Additionally the testsuite checks have to be ignored during the package generation because some of them will fail:

Code:

# diff -u libc6/glibc-2.19/debian/testsuite-checking/compare.sh.orig libc6/glibc-2.19/debian/testsuite-checking/compare.sh

--- libc6/glibc-2.19/debian/testsuite-checking/compare.sh.orig        2014-11-09 14:43:46.809977508 +0000

+++ libc6/glibc-2.19/debian/testsuite-checking/compare.sh

@@ -41,5 +41,5 @@

 

 rm -f $expected $results

 # This would be a lovely place to exit 0 if you wanted to disable hard failures

-#exit 0

+exit 0

 exit $rv

c)
We need to tell dpkg that we changed the sources:

Code:

dpkg-source --commit

This will ask you to specify a name for the patch (chose whatever you like) and bring up the standard editor to provide a description for it.

d)
Now you can build the packages

Code:

debuild -us -uc

I found out that these instructions almost work still, in addition to the above changes, I also had to change these files:

Code:

--- debian/debhelper.in/libc.preinst.orig       2017-10-08 11:32:18.123876676 +0200

+++ debian/debhelper.in/libc.preinst    2017-10-08 11:33:07.583800072 +0200

@@ -357,11 +357,11 @@

         # sanity checking for the appropriate kernel on each architecture.

         kernel_ver=`uname -r`

 

-        # The GNU libc requires a >= 2.6.32 kernel, found in squeeze/lucid/RHEL6

-        if linux_compare_versions "$kernel_ver" lt 2.6.32

+        # The GNU libc requires a >= 2.6.28 kernel, found in squeeze/lucid/RHEL6

+        if linux_compare_versions "$kernel_ver" lt 2.6.28

         then

             echo WARNING: this version of the GNU libc requires kernel version

-            echo 2.6.32 or later.  Please upgrade your kernel before installing

+            echo 2.6.28 or later.  Please upgrade your kernel before installing

             echo glibc.

             kernel26_help



--- debian/sysdeps/linux.mk.orig        2017-10-08 11:32:00.903903345 +0200

+++ debian/sysdeps/linux.mk     2017-10-08 11:32:39.073844230 +0200

@@ -1,5 +1,5 @@

 # When changing this, make sure to update debian/debhelper.in/libc.preinst!

-MIN_KERNEL_SUPPORTED := 2.6.32

+MIN_KERNEL_SUPPORTED := 2.6.28

in both files you need to change "2.6.32" into "2.6.28". Then you can build, and have firefox/iceweasel version 45.9.0esr-1~deb8u1

Oh, I'm doing the build on a Raspberry3, and it took close to 6 hours, so it's nice getting it right the first time.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by elros34 (Post 1523183)

Anybody have patched glibc for latest Ubuntu? I would like to try kwin with xwayland on sailfish but ancient kernel stops me.

My approach won't work on whatever you consider "latest Ubuntu".
It only works up to glibc 2.22 and Xenial already comes with 2.23.
If someone has a working solution I'd be interested too, because then also Debian Stretch would become an option again.

@klausade:
Indeed you're right. Sorry for the inconvenience! I neglected to document these steps because dpkg-source didn't record them.
Nice to see, someone is actually checking what I've been doing!
I'll update the instructions.

Re: Easy Debian Fremantle Beta Testing

It was half year ago :)
I was able to compile 2.23 and I use it with ubuntu 17.04 on 3.0 kernel.
I only changed MIN_KERNEL_SUPPORTED in debian/sysdeps/linux.mk

Re: Easy Debian Fremantle Beta Testing

fyi:
I just built Netsurf 3.7 for Easy Debian Jessie/armhf and it seems to work fine. So I uploaded an archive of the Debian packages. [1] As always, please feel free to host and share this archive as it will undoubtedly vanish at some point.

Code:

$ md5sum netsurf_3.7_ed_sulu.tar

2d789e49980b19fe8369d7511ee12c9a  netsurf_3.7_ed_sulu.tar

I also tried to backport zulucrypt from Buster. but while the build process worked smoothly, actually mounting volumes fails with this error message:

Code:

ERROR: Insufficient privilege to mount the device with given options

Unfortunately the code is ambiguous about throwing this message [2] and I did not bother to investigate further. The same packages fail mounting a truecrypt volume with a different error message in their build environment (Jessie chroot on Stretch host on my Cubieboard2), while a parallel amd64 build works fine in a Jessie/amd64 chroot. So I don't know whether to blame the Maemo kernel, the architecture or something entirely different.

[1] http://www86.zippyshare.com/v/0wxbdbue/file.html
[2] https://github.com/mhogomchungu/zulu.../open_volume.c

Re: Easy Debian Fremantle Beta Testing

Just some quick tip (and it's probably not even new in this thread - in fact I'm pretty sure it's at least mentioned somewhere in the early 100 pages):

I just installed Marble in ED and stumbled upon the problem of not being able to create waypoints for routing, because that requires a right-click, which doesn't work for KDE applications via ED's default way of tap&hold.

So I installed xdotool and added these five lines to my .config/openbox/lxde-rc.xml:

Code:

$ diff lxde-rc.xml.orig  lxde-rc.xml

--- lxde-rc.xml.orig

+++ lxde-rc.xml

@@ -501,6 +501,11 @@

       </mousebind>

     </context>

     <context name="Client">

+      <mousebind button="S-mod5-Left" action="Click">

+        <action name="Execute">                                                  

+          <command>xdotool click 3</command>                                             

+        </action>

+      </mousebind>

       <mousebind button="Left" action="Press">

         <action name="Focus"/>

         <action name="Raise"/>

This allows me to perform a right-click by holding down Shift+Mod5 (the blue arrow key) and tapping the screen.

It should work in pretty much any application. At least it does in Marble, Netsurf and Pcmanfm (although in the latter two also tap&hold works).
For reasons I don't really care to dig into, it doesn't work in Lxterm.

Re: Easy Debian Fremantle Beta Testing

Just a quick reminder, which are the packages that one should definitely not update in the ED chroot?

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by sicelo (Post 1551368)

Just a quick reminder, which are the packages that one should definitely not update in the ED chroot?

The packages built from the glibc sources are critical. [1] Don't update those without applying the changes that make them compatible with kernel 2.6.28! [2] Otherwise ED won't start.
(btw: This is also the showstopper that prevented me from updating ED to Stretch. glibc has seen a major rewrite between the versions in Jessie and Stretch, and I've never figured out if or how support for kernel 2.6.28 can be patched in again.)

The pulseaudio packages [3], while not being critical for the system to run, need to be rebuilt to use the protocol version of Maemo's old pulseaudio version. [2] Otherwise you'll have no sound in ED.

[1] https://packages.debian.org/source/jessie/glibc
[2] http://talk.maemo.org/showpost.php?p...postcount=3138
[3] https://packages.debian.org/source/jessie/pulseaudio

Re: Easy Debian Fremantle Beta Testing

About two weeks ago I found out, that there is a new version 7 of the Midori webbrowser, which has even made it into Debian testing.
Since then I've been trying to backport it to Jessie for Easy Debian, and I finally made it, but it turned out to require quite some backporting. This means that it's not quite as straight-forward as just installing a .deb package and be done with it. So I recommend you to read this post carefully before installing Midori.

For those of you who still want to get started right way, here's an archive that includes the minimal set of packages required:

https://www12.zippyshare.com/v/1MX3Eec9/file.html

Code:

$ md5sum midori_install.tar

4c53872cbee58e573dfa268dc91a726c  midori_install.tar

It has the following content:

Code:

# find .

.

./install_midori.sh

./stretch

./stretch/wayland

./stretch/wayland/libwayland-cursor0_1.12.0-1+deb9u1_armhf.deb

./stretch/wayland/libwayland-client0_1.12.0-1+deb9u1_armhf.deb

./stretch/glib2.0

./stretch/glib2.0/libglib2.0-0_2.50.3-2_armhf.deb

./sulu

./sulu/pango1.0

./sulu/pango1.0/libpangoft2-1.0-0_1.40.5-1_armhf.deb

./sulu/pango1.0/libthai0_0.1.26-1_armhf.deb

./sulu/pango1.0/libpango-1.0-0_1.40.5-1_armhf.deb

./sulu/pango1.0/libpangocairo-1.0-0_1.40.5-1_armhf.deb

./sulu/midori

./sulu/midori/midori_7.0-2_armhf.deb

./sulu/gtk+3.0

./sulu/gtk+3.0/libgtk-3-common_3.22.11-1_all.deb

./sulu/gtk+3.0/libgtk-3-0_3.22.11-1_armhf.deb

./sulu/atk1.0

./sulu/atk1.0/libatk1.0-0_2.22.0-1_armhf.deb

./sulu/atk1.0/libatk1.0-data_2.22.0-1_all.deb

The stretch subdirectory contains dependencies of this Midori backport straight from Debian Stretch, which only have dependencies on packages in jessie or jessie-backports.
The sulu subdirectory contains packages that I backported from stretch and stretch-backports, which also only depend on packages in jessie or jessie-backports.
For clarity, the names of the subdirectories are the names of the respective debian source packages.
The install_midori.sh script installs the dependencies from jessie and jessie-backports and then installs the packages in this archive:

Code:

# cat install_midori.sh 

#!/bin/bash



apt-get install libjavascriptcoregtk-4.0-18 libpeas-1.0-0 libepoxy0 libgcr-ui-3-1 adwaita-icon-theme

apt-get install -t jessie-backports libwebkit2gtk-4.0-37

dpkg -i */*/*.deb

So, provided you already have midori 5 installed from jessie, and have jessie-backports in your sources.list, in theory you could just unpack the archive, cd into the midori_install directory and run the script to install midori.

HOWEVER, you might already have other packages installed, that depend on packages which are also built from the same source packages I backported. This will create a conflict because my packages, originating from stretch and stretch-backports, have higher version numbers than the ones from jessie on your system. This situation might also occur later, if you install further packages from Debian, so after installing this midori backport you should be very attentive when installing ANY new packages, because you'll technically be running a release mix.
Therefore, rather than executing this script blindly, I recommend you to use it as an instruction manual, and are especially careful when running the last dpkg line.

For example, you might encounter the following situation, when trying to install nautilus:

Code:

# apt-get install -s nautilus

Reading package lists... Done

Building dependency tree

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:



The following packages have unmet dependencies:

 nautilus : Depends: libgail-3-0 (>= 3.0.0) but it is not going to be installed

E: Unable to correct problems, you have held broken packages.

This is, because libgail-3-0 is built from the gtk+3.0 source package and depends on libgtk-3-0, which needs to have exactly the same version. apt however tries to install libgail-3-0 (3.14.5-1+deb8u1) from jessie, but you have already installed libgtk-3-0 (3.22.11-1) from my backports. So you'd need libgail-3-0 (3.22.11-1), which is not available in jessie.

In case you need additional packages (and in case you want to build packages based on mine) you'll find ALL the packages I backported (and needed for my backports) in this archive:

https://www69.zippyshare.com/v/ZSC2PFBQ/file.html

Code:

$ md5sum midori_build.tar 

94d68aad9352eae06be8b47c57388061  midori_build.tar

Content:

Code:

# find .

.

./atk1.0

./atk1.0/libatk1.0-dev_2.22.0-1_armhf.deb

./atk1.0/libatk1.0-data_2.22.0-1_all.deb

./atk1.0/gir1.2-atk-1.0_2.22.0-1_armhf.deb

./atk1.0/libatk1.0-0_2.22.0-1_armhf.deb

./atk1.0/libatk1.0-doc_2.22.0-1_all.deb

./atk1.0/libatk1.0-udeb_2.22.0-1_armhf.udeb

./_wayland-protocols

./_wayland-protocols/wayland-protocols_1.7-1_all.deb

./pygobject

./pygobject/python-gi-cairo_3.22.0-2_armhf.deb

./pygobject/python3-gi-dbg_3.22.0-2_armhf.deb

./pygobject/python3-gi-cairo_3.22.0-2_armhf.deb

./pygobject/python-gobject-dbg_3.22.0-2_all.deb

./pygobject/python-gi_3.22.0-2_armhf.deb

./pygobject/python3-gi_3.22.0-2_armhf.deb

./pygobject/python-gobject-dev_3.22.0-2_all.deb

./pygobject/python-gi-dbg_3.22.0-2_armhf.deb

./pygobject/python-gi-dev_3.22.0-2_armhf.deb

./pygobject/python-gobject_3.22.0-2_all.deb

./_autoreconf

./_autoreconf/dh-autoreconf_17~bpo9+1_all.deb

./_wayland

./_wayland/libwayland-client0_1.12.0-1+deb9u1_armhf.deb

./_wayland/libwayland-bin_1.12.0-1+deb9u1_armhf.deb

./_wayland/libwayland-server0_1.12.0-1+deb9u1_armhf.deb

./_wayland/libwayland-dev_1.12.0-1+deb9u1_armhf.deb

./_wayland/libwayland-cursor0_1.12.0-1+deb9u1_armhf.deb

./gtk+3.0

./gtk+3.0/libgtk-3-dev_3.22.11-1_armhf.deb

./gtk+3.0/libgtk-3-0-udeb_3.22.11-1_armhf.udeb

./gtk+3.0/libgail-3-dev_3.22.11-1_armhf.deb

./gtk+3.0/gir1.2-gtk-3.0_3.22.11-1_armhf.deb

./gtk+3.0/libgtk-3-0_3.22.11-1_armhf.deb

./gtk+3.0/libgtk-3-common_3.22.11-1_all.deb

./gtk+3.0/libgail-3-doc_3.22.11-1_all.deb

./gtk+3.0/libgail-3-0_3.22.11-1_armhf.deb

./gtk+3.0/libgtk-3-bin_3.22.11-1_armhf.deb

./gtk+3.0/gtk-3-examples_3.22.11-1_armhf.deb

./gtk+3.0/gtk-update-icon-cache_3.22.11-1_armhf.deb

./gtk+3.0/libgtk-3-doc_3.22.11-1_all.deb

./libuv1

./libuv1/libuv1-dev_1.18.0-3~bpo9+1_armhf.deb

./libuv1/libuv1_1.18.0-3~bpo9+1_armhf.deb

./midori

./midori/midori-dbgsym_7.0-2_armhf.deb

./midori/midori_7.0-2_armhf.deb

./_glib2.0

./_glib2.0/libglib2.0-dev_2.50.3-2_armhf.deb

./_glib2.0/libglib2.0-0_2.50.3-2_armhf.deb

./_glib2.0/libglib2.0-bin_2.50.3-2_armhf.deb

./_glib2.0/libglib2.0-data_2.50.3-2_all.deb

./_libthai

./_libthai/libthai-data_0.1.26-1_all.deb

./_libthai/libthai0_0.1.26-1_armhf.deb

./debhelper

./debhelper/dh-systemd_12~bpo9+1_all.deb

./debhelper/debhelper_12~bpo9+1_all.deb

./gobject-introspection

./gobject-introspection/libgirepository1.0-doc_1.50.0-1_all.deb

./gobject-introspection/libgirepository-1.0-1_1.50.0-1_armhf.deb

./gobject-introspection/gir1.2-glib-2.0_1.50.0-1_armhf.deb

./gobject-introspection/gobject-introspection_1.50.0-1_armhf.deb

./gobject-introspection/libgirepository1.0-dev_1.50.0-1_armhf.deb

./gobject-introspection/gir1.2-freedesktop_1.50.0-1_armhf.deb

./cmake

./cmake/cmake-qt-gui_3.13.2-1~bpo9+1_armhf.deb

./cmake/cmake-curses-gui_3.13.2-1~bpo9+1_armhf.deb

./cmake/cmake-data_3.13.2-1~bpo9+1_all.deb

./cmake/cmake_3.13.2-1~bpo9+1_armhf.deb

./cmake/cmake-doc_3.13.2-1~bpo9+1_all.deb

./pango1.0

./pango1.0/libpangoxft-1.0-0_1.40.5-1_armhf.deb

./pango1.0/libpangocairo-1.0-0_1.40.5-1_armhf.deb

./pango1.0/libpango1.0-0_1.40.5-1_armhf.deb

./pango1.0/pango1.0-tests_1.40.5-1_armhf.deb

./pango1.0/libpango1.0-doc_1.40.5-1_all.deb

./pango1.0/libpango1.0-udeb_1.40.5-1_armhf.udeb

./pango1.0/libpango-1.0-0_1.40.5-1_armhf.deb

./pango1.0/libpangoft2-1.0-0_1.40.5-1_armhf.deb

./pango1.0/gir1.2-pango-1.0_1.40.5-1_armhf.deb

./pango1.0/libpango1.0-dev_1.40.5-1_armhf.deb

./vala

./vala/libvala-0.34-dev_0.34.7-1_armhf.deb

./vala/valac_0.34.7-1_armhf.deb

./vala/valac-0.34-vapi_0.34.7-1_all.deb

./vala/libvala-0.34-0_0.34.7-1_armhf.deb

./vala/vala-0.34-doc_0.34.7-1_all.deb

Again, the subdirectories are the names of the respective source packages. Subdirectories starting with an underscore come directly from stretch or stretch-backports. Subdirectories without an underscore were backported by me.
As you can see, in in the gtk+3.0 subdirectory there is libgail-3-0_3.22.11-1_armhf.deb, which you would need in the afore-mentioned nautilus example.

In case you want to reproduce my backport, here are some hints:

dependency tree:

Code:

+midori 7 (sid)

\*cmake 3.13 (stretch-backports)

 \+libuv1 1.18 (stretch-backports)

\*debhelper 12 (stretch-backports)

 \_autoreconf 17 (stretch-backports)

\+libgtk-3-0 3.22 (stretch)

 \+atk1.0 2.22 (stretch)

 \_glib2.0 2.50 (stretch)

 \+pango1.0 1.40 (stretch)

 \*pygobject 3.22 (stretch)

  \+gobject-introspection 1.50 (stretch)

 \_wayland 1.12 (stretch)

 \_wayland-protocols 1.7 (stretch)

\+vala 0.34 (stretch)

legend:
+ "clean" backport
* "dirty" backport (see remarks)
_ not backported, just installed from Debian

remarks:

cmake:
testsuite disabled

Code:

diff debian/rules.orig debian/rules 

55c55

<         dh_auto_test --buildsystem=cmake -- -j1 ARGS="-E CTestTestUpload --timeout 5000"

---

>         dh_auto_test --buildsystem=cmake -- -j1 ARGS="-N -E CTestTestUpload --timeout 5000"

debhelper:
disable compression because it is not defined in dh10 (jessie-backports)
disable version check and hard-code version because for some reason $version is empty under dh10
(chicken-and-egg problem, rebuilding dh12 with dh12 works without hacks)

Code:

diff /lib/Debian/Debhelper/Dh_Lib.pm.built_with_dh9 /lib/Debian/Debhelper/Dh_Lib.pm

1037c1037

<                         #compression => 0,

---

>                         compression => 0,

1044,1046c1044,1046

<                 #if (not defined($version) or not $version->is_valid) {

<                 #        error("changelog parse failure; invalid or missing version");

<                 #}

---

>                 if (not defined($version) or not $version->is_valid) {

>                         error("changelog parse failure; invalid or missing version");

>                 }

1048c1048

<                 $dh{VERSION} = "12~bpo9+1";

---

>                 $dh{VERSION} = $pkg_version{$cache_key} = $version->as_string;

glib2.0:
taken straight from stretch because backport to jessie as root fails due to #770193 [1] and backporting as regular user fails due to some other error I don't remember
fortunately dependencioes check out

pygobject:
ignore testsuite

Code:

diff debian/rules.orig debian/rules

10c10

< TESTSUITE_FAIL_CMD=exit 1

---

> TESTSUITE_FAIL_CMD=exit 0

webkit2gtk:
backport of newer versions fails due to newer gcc required, which I haven't been able to backport
in other words:
The webkit version this midori build is based on is outdated. DON'T USE THIS BROWSER FOR SECURITY-CRITICAL TASKS! [2]

known problems:
1. Midori only starts within Easy Debian's LXDE desktop, but not directly in Maemo via debbie. This is the gdb output, I don't know what to make of it:

Code:

gdb) run

Starting program: /usr/bin/midori 

[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]

[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]

[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".

[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]

[New Thread 0x45e06260 (LWP 12138)]



(midori:12135): Gtk-WARNING **: Locale not supported by C library.

        Using the fallback 'C' locale.

Gtk-Message: Failed to load module "libgtkstylus.so"

[New Thread 0x469ff260 (LWP 12140)]

[New Thread 0x471ff260 (LWP 12141)]

[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]

[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]

[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]

[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]

[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]

[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]



Program received signal SIGSEGV, Segmentation fault.

0x439f1f78 in XIFreeDeviceInfo () from /usr/lib/arm-linux-gnueabihf/libXi.so.6

2. The scroll bars don't render properly. They still seem to work fine though.

3. Because Midori is now based on Gtk+3, Easy Debian's default right-click method of "tap&hold" doesn't work here. You'll have to resort to something like the modifier solution I posted earlier. [3]

btw:
Since it was clear pretty soon, that this backport wouldn't be a piece of cake, I also tried to backport Midori 6 instead of Midori 7. Version 6 however, wasn't any easier to backport, so I returned to version 7.

Because Midori is also available as a snap package, I also tried to backport the snapd package from Debian stretch, to enable Easy Debian to handle hopefully arbitrary snap packages. I succeeded in doing so, and first tests of it under a jessie chroot on my Cubieboard 2 running stretch looked promising, but it didn't actually work on the N900. I'm not sure, but I believe this is due to Maemo's kernel being too old for apparmor, which is required by snap.

And as always:
Please mirror these archives!

[1] https://bugs.debian.org/cgi-bin/bugr...cgi?bug=770193
[2] https://blogs.gnome.org/mcatanzaro/2...urity-updates/
[3] http://talk.maemo.org/showthread.php...&page=328#3273

Re: Easy Debian Fremantle Beta Testing

fyi:
Since Jessie is archived now, you'll have to adapt your sources.list in case you want to install additional software in Easy Debian:

Code:

# cat /etc/apt/sources.list

deb http://archive.debian.org/debian/ jessie main

deb http://archive.debian.org/debian/ jessie-backports main

If, like me, you have backports enabled, you'll also need to tell apt to ignore validity timestamps:

Code:

# cat /etc/apt/apt.conf

Acquire::Check-Valid-Until "0";

Happy dead-horse riding!

Re: Easy Debian Fremantle Beta Testing

Here's a build of netsurf 3.9 based on a backport of openssl 1.1 (from buster), that should support TLS 1.3 (see screenshot*):

https://transfer.sh/PEg06/netsurf-3....ed_sulu.tar.gz **

Code:

$ md5sum netsurf-3.9_openssl-1.1.1c_ed_sulu.tar.gz

925e1fe7f40034a2f4e874c815e55be2  netsurf-3.9_openssl-1.1.1c_ed_sulu.tar.gz

Building netsurf was easy, but of course I also needed to backport openssl. That wasn't too hard either, but it has a side effect:
netsurf uses curl as a backend, and you need your netsurf and curl to use the same openssl version. So I had to backport curl as well, which was a bit tricky, because autoconf had introduced a new option called "runstatedir" in the meantime. I neeed to patch that option out of the source package.

As a consequence the archive linked above contains these packages:

Code:

libcurl4_7.64.0-4_armhf.deb

libssl1.1_1.1.1c-1_armhf.deb

netsurf_3.9-1_all.deb

netsurf-common_3.9-1_all.deb

netsurf-gtk_3.9-1_armhf.deb

You'll need to install all of them.*** The libcurl4 package might cause some trouble though. Vanilla Jessie has libcurl3, which libcurl4 conflicts with.**** I added the "Provides: libcurl3" tag to my libcurl4 package, so from a formal POV the change in name shouldn't cause any trouble as long as another program doesn't require a specific version of libcurl3.
But the truth is, I don't know what will actually happen. This libcurl4 package has the potential to break ANY other program that uses curl.*****

For completeness, here's another archive that includes all the packages I backported during this build:

https://transfer.sh/tGxRo/netsurf-3....ackages.tar.gz

Code:

$ md5sum netsurf-3.9_openssl-1.1.1c_ed_sulu_all_packages.tar.gz

a80bf6235e53c3fa76edd90afac62332  netsurf-3.9_openssl-1.1.1c_ed_sulu_all_packages.tar.gz

Code:

$ ls -1 *

curl:

curl_7.64.0-4_armhf.deb

curl-dbgsym_7.64.0-4_armhf.deb

libcurl3-gnutls_7.64.0-4_armhf.deb

libcurl3-gnutls-dbgsym_7.64.0-4_armhf.deb

libcurl3-nss_7.64.0-4_armhf.deb

libcurl3-nss-dbgsym_7.64.0-4_armhf.deb

libcurl4_7.64.0-4_armhf.deb

libcurl4-dbgsym_7.64.0-4_armhf.deb

libcurl4-doc_7.64.0-4_all.deb

libcurl4-gnutls-dev_7.64.0-4_armhf.deb

libcurl4-nss-dev_7.64.0-4_armhf.deb

libcurl4-openssl-dev_7.64.0-4_armhf.deb



netsurf:

netsurf_3.9-1_all.deb

netsurf-common_3.9-1_all.deb

netsurf-fb_3.9-1_armhf.deb

netsurf-fb-dbgsym_3.9-1_armhf.deb

netsurf-gtk_3.9-1_armhf.deb

netsurf-gtk-dbgsym_3.9-1_armhf.deb



openssl:

libssl1.1_1.1.1c-1_armhf.deb

libssl1.1-dbgsym_1.1.1c-1_armhf.deb

libssl-dev_1.1.1c-1_armhf.deb

libssl-doc_1.1.1c-1_all.deb

openssl_1.1.1c-1_armhf.deb

openssl-dbgsym_1.1.1c-1_armhf.deb

*) Whoever decided to make Ctrl + Shift + P the screenshot hotkey deserves to be tarred and feathered! How am I supposed to hit those three keys without breaking my fingers? ;)
**) Since zippyshare has blocked users from some parts of the world (including Germany), I needed to find another file host.
transfer.sh looks kind of nice, but they seem to delete files after 14 days if I got that correctly.
***) Strictly spoken, you don't need netsurf_3.9-1_all.deb at all.
****) In parts, they ship the same files.
*****) Which you might not even be aware of, because it's happening in the background.******
******) These stars are getting out of hand. :eek:

Re: Easy Debian Fremantle Beta Testing

Can we get this fast tracked to extras-testing?
(edit)Just noticed is for easy-debian...
I will have to try to rehabilitate my old Debian install as the repos for it have been gone for a long time. maybe we should look to host at *.maemo.org like the other repos.

Re: Easy Debian Fremantle Beta Testing

Quote:

Originally Posted by biketool (Post 1559187)

I will have to try to rehabilitate my old Debian install as the repos for it have been gone for a long time. maybe we should look to host at *.maemo.org like the other repos.

I don't understand. Everything you need is still available:
Easy Debian is in the Extras repo [1], you can find Jessie/armhf images at qole.org [2] and kernel-power (which you'll need for armhf) is also available in Extras.

[1] http://repository.maemo.org/
[2] http://qole.org/files/