Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (9)
to SailfishOS by biketool - 11 hrs, 22 mins ago -
[Announce] coderus unrestricted system-ui (297)
to MeeGo / Harmattan by nieldk - 6 days, 16 hrs ago - more...
|
2017-12-13
, 22:57
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#3272
|
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.
I also tried to backport zulucrypt from Buster. but while the build process worked smoothly, actually mounting volumes fails with this error message:
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
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
Code:
ERROR: Insufficient privilege to mount the device with given options
[1] http://www86.zippyshare.com/v/0wxbdbue/file.html
[2] https://github.com/mhogomchungu/zulu.../open_volume.c
|
|
2018-01-24
, 22:41
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#3273
|
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:
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.
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"/>
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.
|
|
2018-12-02
, 14:32
|
|
Community Council |
Posts: 686 |
Thanked: 1,237 times |
Joined on Sep 2010
@ Mbabane
|
#3274
|
Just a quick reminder, which are the packages that one should definitely not update in the ED chroot?
__________________
RX-51
RX-51
| The Following 3 Users Say Thank You to sicelo For This Useful Post: | ||
|
|
2018-12-02
, 19:57
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#3275
|
Originally Posted by sicelo
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.
Just a quick reminder, which are the packages that one should definitely not update in the ED chroot?
(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
|
|
2019-03-03
, 13:31
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#3276
|
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
It has the following content:
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:
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:
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
Content:
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:
legend:
+ "clean" backport
* "dirty" backport (see remarks)
_ not backported, just installed from Debian
remarks:
cmake:
testsuite disabled
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)
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
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:
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
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
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 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
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.
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
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
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)
+ "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"
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;
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
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
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
| The Following 9 Users Say Thank You to sulu For This Useful Post: | ||
|
|
2019-05-20
, 20:42
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#3277
|
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:
If, like me, you have backports enabled, you'll also need to tell apt to ignore validity timestamps:
Happy dead-horse riding!
Last edited by sulu; 2019-05-21 at 05:13. Reason: typo
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
Code:
# cat /etc/apt/apt.conf Acquire::Check-Valid-Until "0";
Last edited by sulu; 2019-05-21 at 05:13. Reason: typo
| The Following 9 Users Say Thank You to sulu For This Useful Post: | ||
|
|
2019-08-17
, 08:54
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#3278
|
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 **
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:
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
*) 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.
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
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
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.
|
|
2019-08-17
, 19:39
|
|
Posts: 1,427 |
Thanked: 2,626 times |
Joined on Jan 2011
@ Touring
|
#3279
|
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.
Last edited by biketool; 2019-08-17 at 19:44.
(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.
Last edited by biketool; 2019-08-17 at 19:44.
| The Following User Says Thank You to biketool For This Useful Post: | ||
|
|
2019-08-17
, 20:43
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#3280
|
Originally Posted by biketool
I don't understand. Everything you need is still available:
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.
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/
 |
| Tags |
| beta, debian, easy debian, extras-devel, fremantle, i <3 qole, squeeze |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 00:21.
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