screenshot
https://disk.yandex.ru/d/-ynMOlrHFSu48Q … ii-32-.png

YYY wrote:

I will try write simple instruction how build for himself from ubuntu-16.04-ppa

How about https://wiki.debian.org/CreatePackageFromPPA?

Yes.
But with chromium has problem.

Chromium-i386 build only with amd64 kernel and need use chroot to i366 system from amd64 system. On hdd need 20Gb free space

I did so:

$ mount -t proc proc /chroot/proc/
$ mount -t sysfs sys /chroot/sys/
$ mount -o bind /dev/ /chroot/dev/
$ chroot /chroot/

in chroot i add string to chroot /etc/fstab string

none /dev/shm tmpfs rw,nosuid,nodev,noexec 0 0

and
$ mount /dev/shm

need some library from ubuntu 16.04 : llvm-8, clang-8 and ko

and i change in file build/toolchain/linux/BUILD.gn string "x64" to "x86"

clang_toolchain("clang_x64") {
  # Output linker map files for binary size analysis.
  enable_linker_map = true

  toolchain_args = {
    current_cpu = "x86"
    current_os = "linux"
  }
}

And rebuild as
dpkg-buildpackage -rfakeroot -b -ai386 --target-arch i386

I will try write simple instruction how build for himself from ubuntu-16.04-ppa

How about https://wiki.debian.org/CreatePackageFromPPA?

Why not upgrade to beowulf or chimaera then?

ASCII lifetime to june 2022. Maybe summer i try upgrade to beowulf

Yes. It not good for security. I will try write simple instruction how build for himself from ubuntu-16.04-ppa

i use lxdm from lxde project

I long time use Devuan ASCII 32-bit
But chromium package in repo very old (v73 = 2019)

Why not upgrade to beowulf or chimaera then? They have v90.0.4430.212 currently and it will be kept relatively up to date.

I don't think people should trust your links. If you want to engender trust then perhaps use an independent build service such as https://build.opensuse.org/ instead — that shows the build process for each hosted package, unlike your random download links.

The OBS only has options for Debian but the packages should be binary-compatible with the appropriate Devuan release.

Note that ~/.profile won't be read for LightDM.

Reference and potential solution: https://bugs.debian.org/cgi-bin/bugrepo … bug=752129

I long time use Devuan ASCII 32-bit
But chromium package in repo very old (v73 = 2019)

I simply tryed rebuild packages from ubuntu 16.04 ppa
https://launchpad.net/ubuntu/xenial/+so … um-browser
and it work for me
https://i.ibb.co/JQmS7g1/chromium-90.png

I only rebuild on devuan-ascii 32-bit and not rename ubuntu packages
v84
https://disk.yandex.ru/d/75bH7m9RltaCxg
v87
https://disk.yandex.ru/d/EJusWl6e260Kyg
v90
https://disk.yandex.ru/d/4Z4vsnafozlJ8g

I find only problem with API Keys window
https://www.chromium.org/developers/how-tos/api-keys/
But exists solution
https://stackoverflow.com/questions/212 … m-portable
https://gist.github.com/cvan/44a6d60457 … b104f9dcc4

I think it must work with debian 9 stretch and ko