antiX-bullseye-a2-runit_x64-full.iso available

[Member calciumsodium]

Helpful

Up

0

::

Continuing from the previous thread, I used the command

$ sudo apt install wine32 wine wine64

I am attaching the whole output after this command. Please see attachment labeled “output”

Any ideas on how to proceed? Thanks.

[Forum Admin anticapitalista]

Helpful

Up

0

::

First of all, update the kernel(s).
kernel-updates2

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member calciumsodium]

Helpful

Up

0

::

I found out that the a2-runit toy experiment comes preinstalled with

linux-image-4.9.261-antix.1-amd64-smp (full-legacy kernel)
linux-image-5.10.22-antix.1-amd64-smp (full)

The 5.10.22 kernel with install wine correctly.
The 4.9.261 kernel will NOT install wine.

Is it because of the 261 is greater than 255? And 22 is less than 255? See the 255 error in the previous thread.

[Member ModdIt]

Helpful

Up

0

::

For devs,
please do not take “a2-runit toy experiment”, a skidoo comment to be considered disparaging
from Moddit side.

I have used a2 since its release more often than my installed 19,4 stable.
“Thoroughly Enjoying” the experience.

I hope the experiment will be built on and end up as a future alternate init release.

[Anonymous]

Helpful

Up

0

::

dpkg: error processing archive /var/cache/apt/archives/libc6_2.31-11_amd64.deb (–unpack):
new libc6:amd64 package pre-installation script subprocess returned error exit status 1

FWIW, beginning about I week ago, I began seeing the identical “libc6 unpacking error” error when using the sysv version of the antiX21 alpha. Although the content of the debian repositories is now “frozen” in preparation for the upcoming release, obviously the suite is not yet “stable” and we should expect temporary hiccups like this “libc6 issue”.

[Member calciumsodium]

Helpful

Up

0

::

Hi,
I will call this development “a2-runit” instead of a2-runit toy experiment from now on.

I did the following experiment. Please bear with me as I try to explain.
I did a fresh install of antiX19.3 and updated the kernel to 4.9.261-antix.1-amd64-smp, the same kernel as the legacy kernel in a2-runit.
Then I did the following command:
$sudo apt install wine wine32 wine64

Interestingly, wine would NOT install, and gave me the following error message, which is the same error message that I received when trying to install wine on a2-runit using the legacy kernel. It must be the 4.9.261-antix.1-amd64-smp kernel that is not allowing the wine install. The a2-runit development may be fine.

Fetched 86.4 MB in 19s (4,607 kB/s)
Extracting templates from packages: 100%
Preconfiguring packages …
(Reading database … 178671 files and directories currently installed.)
Preparing to unpack …/0-libpam-elogind_246.10-2.0antix1_amd64.deb …
Unpacking libpam-elogind:amd64 (246.10-2.0antix1) over (243.7-1.0antix1) …
Preparing to unpack …/1-eudev_246%3a3.2.9.1.0antix4_amd64.deb …
Unpacking eudev (246:3.2.9.1.0antix4) over (232:3.2.9.1) …
Preparing to unpack …/2-libeudev-dev_246%3a3.2.9.1.0antix4_amd64.deb …
Unpacking libeudev-dev:amd64 (246:3.2.9.1.0antix4) over (232:3.2.9.1) …
Preparing to unpack …/3-libeudev1_246%3a3.2.9.1.0antix4_amd64.deb …
Unpacking libeudev1:amd64 (246:3.2.9.1.0antix4) over (232:3.2.9.1) …
Preparing to unpack …/4-elogind_246.10-2.0antix1_amd64.deb …
Unpacking elogind (246.10-2.0antix1) over (243.7-1.0antix1) …
Preparing to unpack …/5-libelogind0_246.10-2.0antix1_amd64.deb …
Unpacking libelogind0:amd64 (246.10-2.0antix1) over (243.7-1.0antix1) …
Preparing to unpack …/6-libp11-kit0_0.23.15-2+deb10u1_amd64.deb …
Unpacking libp11-kit0:amd64 (0.23.15-2+deb10u1) over (0.23.15-2) …
Selecting previously unselected package libp11-kit0:i386.
Preparing to unpack …/7-libp11-kit0_0.23.15-2+deb10u1_i386.deb …
Unpacking libp11-kit0:i386 (0.23.15-2+deb10u1) …
Setting up libp11-kit0:amd64 (0.23.15-2+deb10u1) …
Selecting previously unselected package libc6:i386.
(Reading database … 178677 files and directories currently installed.)
Preparing to unpack …/libc6_2.28-10_i386.deb …
ERROR: Your kernel version indicates a revision number
of 255 or greater. Glibc has a number of built in
assumptions that this revision number is less than 255.
If you\’ve built your own kernel, please make sure that any
custom version numbers are appended to the upstream
kernel number with a dash or some other delimiter.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.28-10_i386.deb (–unpack):
new libc6:i386 package pre-installation script subprocess returned error exit status 1
Selecting previously unselected package libgcc1:i386.
Preparing to unpack …/libgcc1_1%3a8.3.0-6_i386.deb …
Unpacking libgcc1:i386 (1:8.3.0-6) …
Selecting previously unselected package gcc-8-base:i386.
Preparing to unpack …/gcc-8-base_8.3.0-6_i386.deb …
Unpacking gcc-8-base:i386 (8.3.0-6) …
Errors were encountered while processing:
/var/cache/apt/archives/libc6_2.28-10_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[Forum Admin anticapitalista]

Helpful

Up

0

::

Update to the latest 4.9.264kernel

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Anonymous]

Helpful

Up

0

::

“a2-runit toy experiment”, a skidoo comment to be considered disparaging

Nothing to “consider” ~~ it was a frank statment, an unemotional assessment. Onboard documentation does not yet exist. No method of service (daemon) management is provided… so “toy comma experiment” is a more reasonable nutshell description than “alpha”.

[Member calciumsodium]

Helpful

Up

0

::

Per @anticapitalista suggestion,

I did a fresh install of antiX 19.3 and updated to 4.9.264-antix.1-amd64-smp.
Again, I tried sudo apt install wine wine32 wine64.

Again, I get the same 255 error message below. Is there a way to overcome this 255 error?

As a further bit of information. My main OS is antiX 19.1 but I have updated my kernel to 4.9.264-antix.1-amd64-smp.
Upon a fresh install of 19.1, which has the 4.9.200 kernel, I would install wine and then update to the latest kernel. Wine works on the latest 4.9.264 kernel. You just have to install it before updating the kernel. The problem is that 4.9.261 or 4.9.264 or some later version, which would end up in the antiX bullseye, is too high of a kernel to install wine, unless the developers of wine will update it to the latest kernel. Does this make sense?

Fetched 86.4 MB in 25s (3,408 kB/s)
Extracting templates from packages: 100%
Preconfiguring packages …
(Reading database … 177366 files and directories currently installed.)
Preparing to unpack …/0-libpam-elogind_246.10-2.0antix1_amd64.deb …
Unpacking libpam-elogind:amd64 (246.10-2.0antix1) over (243.7-1.0antix1) …
Preparing to unpack …/1-eudev_246%3a3.2.9.1.0antix4_amd64.deb …
Unpacking eudev (246:3.2.9.1.0antix4) over (232:3.2.9.1) …
Preparing to unpack …/2-libeudev-dev_246%3a3.2.9.1.0antix4_amd64.deb …
Unpacking libeudev-dev:amd64 (246:3.2.9.1.0antix4) over (232:3.2.9.1) …
Preparing to unpack …/3-libeudev1_246%3a3.2.9.1.0antix4_amd64.deb …
Unpacking libeudev1:amd64 (246:3.2.9.1.0antix4) over (232:3.2.9.1) …
Preparing to unpack …/4-elogind_246.10-2.0antix1_amd64.deb …
Unpacking elogind (246.10-2.0antix1) over (243.7-1.0antix1) …
Preparing to unpack …/5-libelogind0_246.10-2.0antix1_amd64.deb …
Unpacking libelogind0:amd64 (246.10-2.0antix1) over (243.7-1.0antix1) …
Preparing to unpack …/6-libp11-kit0_0.23.15-2+deb10u1_amd64.deb …
Unpacking libp11-kit0:amd64 (0.23.15-2+deb10u1) over (0.23.15-2) …
Selecting previously unselected package libp11-kit0:i386.
Preparing to unpack …/7-libp11-kit0_0.23.15-2+deb10u1_i386.deb …
Unpacking libp11-kit0:i386 (0.23.15-2+deb10u1) …
Setting up libp11-kit0:amd64 (0.23.15-2+deb10u1) …
Selecting previously unselected package libc6:i386.
(Reading database … 177372 files and directories currently installed.)
Preparing to unpack …/libc6_2.28-10_i386.deb …
ERROR: Your kernel version indicates a revision number
of 255 or greater. Glibc has a number of built in
assumptions that this revision number is less than 255.
If you\’ve built your own kernel, please make sure that any
custom version numbers are appended to the upstream
kernel number with a dash or some other delimiter.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.28-10_i386.deb (–unpack):
new libc6:i386 package pre-installation script subprocess returned error exit status 1
Selecting previously unselected package libgcc1:i386.
Preparing to unpack …/libgcc1_1%3a8.3.0-6_i386.deb …
Unpacking libgcc1:i386 (1:8.3.0-6) …
Selecting previously unselected package gcc-8-base:i386.
Preparing to unpack …/gcc-8-base_8.3.0-6_i386.deb …
Unpacking gcc-8-base:i386 (8.3.0-6) …
Errors were encountered while processing:
/var/cache/apt/archives/libc6_2.28-10_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[Member calciumsodium]

Helpful

Up

0

::

Kodi 19.0 works good using a2-runit with the 5.10.22-antix.1-amd64-smp kernel.

[Forum Admin Dave]

Helpful

Up

0

::

@ calciumsodium;
Looking at the preinstall script from the debian package, it seems to be failing at one of the kernel checks by the error.
Here is the command that is run to retrieve the revision number.
uname -r | sed 's/\([0-9]*\.\)\{1,2\}\([0-9]*\)\(.*\)/\2/'
What does it output for you if you run it in terminal?

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member calciumsodium]

Helpful

Up

0

::

Hi @Dave,
Regarding the 255 error.
I reproduced it again and got the output that you suggested.
From the live USB of the a2-runit, I chose the legacy kernel boot option.
I did sudo apt update.
I did sudo apt wine wine32 wine64

Here is the relevant output:
Fetched 101 MB in 17s (5,869 kB/s)
Extracting templates from packages: 100%
Preconfiguring packages …
(Reading database … 175307 files and directories currently installed.)
Preparing to unpack …/libc6_2.31-11_amd64.deb …
ERROR: Your kernel version indicates a revision number
of 255 or greater. Glibc has a number of built in
assumptions that this revision number is less than 255.
If you\’ve built your own kernel, please make sure that any
custom version numbers are appended to the upstream
kernel number with a dash or some other delimiter.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.31-11_amd64.deb (–unpack):
new libc6:amd64 package pre-installation script subprocess returned error exit status 1
Selecting previously unselected package libc6:i386.
Preparing to unpack …/libc6_2.31-11_i386.deb …
De-configuring libc6:amd64 (2.31-10) …
ERROR: Your kernel version indicates a revision number
of 255 or greater. Glibc has a number of built in
assumptions that this revision number is less than 255.
If you\’ve built your own kernel, please make sure that any
custom version numbers are appended to the upstream
kernel number with a dash or some other delimiter.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.31-11_i386.deb (–unpack):
new libc6:i386 package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/libc6_2.31-11_amd64.deb
/var/cache/apt/archives/libc6_2.31-11_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
demo@antix1:~
$ uname -r | sed ‘s/\([0-9]*\.\)\{1,2\}\([0-9]*\)\(.*\)/\2/’
261
demo@antix1:~
$ uname -r
4.9.261-antix.1-amd64-smp
demo@antix1:~
$

[Member calciumsodium]

Helpful

Up

0

::

Hi @Dave,
I repeated the other experiment as well and got the output.
From the live USB of the a2-runit, I chose the full boot option (not the legacy kernel option).
I did sudo apt update.
I did sudo apt wine wine32 wine64

Lots of output.
Here is the relevant output:

Setting up libwine:i386 (5.0.3-3) …
Setting up wine32:i386 (5.0.3-3) …
Processing triggers for man-db (2.9.4-2) …
Processing triggers for dbus (1.12.20-2) …
Processing triggers for initramfs-tools (0.139) …
update-initramfs: Generating /boot/initrd.img-5.10.22-antix.1-amd64-smp
cryptsetup: ERROR: Couldn’t resolve device overlay
cryptsetup: WARNING: Couldn’t determine root device
I: The initramfs will attempt to resume from /dev/sda3
I: (UUID=468658bc-0a91-40df-a70a-af6d735d2001)
I: Set the RESUME variable to override this.
Processing triggers for hicolor-icon-theme (0.17-2) …
Processing triggers for libc-bin (2.31-10) …
Processing triggers for wine (5.0.3-3) …
demo@antix1:~
$ uname -r | sed ‘s/\([0-9]*\.\)\{1,2\}\([0-9]*\)\(.*\)/\2/’
sed: -e expression #1, char 1: unknown command: `�’
demo@antix1:~
$ uname -r | sed ‘s/\([0-9]*\.\)\{1,2\}\([0-9]*\)\(.*\)/\2/’
sed: -e expression #1, char 1: unknown command: `�’
demo@antix1:~
$ uname -r | sed ‘s/\([0-9]*\.\)\{1,2\}\([0-9]*\)\(.*\)/\2/’
22
demo@antix1:~
$ uname -r
5.10.22-antix.1-amd64-smp
demo@antix1:~

[Forum Admin Dave]

Helpful

Up

0

::

OK I understand what is meant by the kernel is to high now.
So I guess that glibc has a some assumptions that set an 8 bit count limit on revision numbers. Therefor to make glibc install it would need to be renamed from 4.9.261-antix.1-amd64-smp to something like 4.9.255+(261)-antix.1-amd64-smp as reported by uname to trick the count limit. I think the deb versioning could remain the same however.
Anti may know better about packing the antiX kernels to see if that is possible to rename the kernel in such a way.
`

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member calciumsodium]

Helpful

Up

0

::

Hi @Dave,
Thanks for understanding. The error says 255 or greater, so I think it may have to be 254 or less, say 250 to be safe.
So 4.9.264-antix.1-amd64-smp to something like 4.9.250+(264)-antix.1-amd64-smp.
I hope this helps. I can test this out, or any of the members, if it was created.

[Author]

Posts