#archlinux32 | Logs for 2022-12-27

[05:39:39] -!- epony has quit [Read error: Connection reset by peer]
[06:13:04] -!- epony has joined #archlinux32
[09:55:23] -!- GNUtoo_ has quit [Ping timeout: 255 seconds]
[09:56:45] -!- GNUtoo has joined #archlinux32
[13:39:30] <KitsuWhooa> libneon depends on libssl 1.1/libcrypto 1.1
[13:39:35] <KitsuWhooa> sounds like it needs a rebuild
[14:35:50] <bill-auger> KitsuWhooa: just install openssl-1.1 - probably many packages will require openssl-1.1 for some time to come
[14:35:50] <bill-auger> "Required By (336)" https://www.archlinux32.org
[14:35:55] <phrik> Title: Arch Linux 32 - openssl-1.1 1.1.1.s-2.2 (i686) (at www.archlinux32.org)
[14:36:48] <KitsuWhooa> Isn't it a bad idea to run an out of date openssl? :p
[14:36:56] <KitsuWhooa> or is it still being maintained
[14:38:20] <bill-auger> you do not have any choice - arch made this decision to migrate gradually - all arch users wil be running the same versions
[14:43:25] <KitsuWhooa> I'm confused why it was removed then
[14:43:52] <KitsuWhooa> surely if I install libneon upstream it won't tell me that libssl 1.1 is missing, right?
[14:44:07] <bill-auger> nothin was removed openssl was simply renamed, then upgraded
[14:44:58] <KitsuWhooa> then the packages should depend on the renamed openssl package
[14:45:18] <bill-auger> probably the only other option was to wait until all openssl-1.1 dependents are patched/rebuilt for openssl-3 - in that way, openssl-1.1 would remain as the only openssl version on the system, until all were ready to roll together
[14:46:36] <KitsuWhooa> yes but if I pacman -S neon, it's not bringing in openssl 1.1
[14:46:41] <KitsuWhooa> on arch32
[14:46:55] <KitsuWhooa> surely this doesn't happen on upstream arch...
[14:47:42] <bill-auger> right, that is the main problem i worked around - my solution wsa to make pacman depend on openssl-1.1 - that way no users would notice this probelm
[14:51:29] <KitsuWhooa> https://archlinux.org
[14:51:31] <phrik> Title: Arch Linux - neon 0.32.4-2 (x86_64) (at archlinux.org)
[14:51:41] <KitsuWhooa> says it links to libssl.so.3
[14:52:46] <bill-auger> that means rch rebuilt/upgraded neon
[14:52:59] <bill-auger> so arch32 will do the same soon
[14:53:13] <KitsuWhooa> and that's what I requested :p
[14:53:44] -!- GNUtoo has quit [Ping timeout: 255 seconds]
[14:54:38] <bill-auger> ok, but in this case, you did not need to - arch32 will generally follow whatever arch has done
[14:55:31] -!- GNUtoo has joined #archlinux32
[14:56:03] <bill-auger> just ya know , maybe not on the same day
[15:00:12] <bill-auger> frankly, were lucky arch still works at all on these old machines - most upstreams are not stewarding 32bit support very well, or at all
[15:01:15] <bill-auger> just an example, there is a bug in firefox 108 - it will not build on any arch other than 64bit little-endian - the interesting point is that mozilla apparently did not notice the failure - users had to report the bug
[15:02:12] <bill-auger> youd think that mozilla has build servers, canary builds, whatever, that would immeditely indicate a build failure acroos multiple arxhes
[15:03:14] <bill-auger> apparently, they do not even try to build to 32bit ever ?
[15:05:38] <bill-auger> or if they do, they have no hesitation to release a version that does not support 32bit computers
[16:29:08] -!- GNUtoo has quit [Ping timeout: 255 seconds]
[16:44:48] -!- GNUtoo has joined #archlinux32
[17:22:41] -!- GNUtoo has quit [Ping timeout: 255 seconds]
[17:23:11] -!- GNUtoo has joined #archlinux32
[19:24:58] -!- epony has quit [Ping timeout: 268 seconds]
[20:34:42] -!- epony has joined #archlinux32
[21:03:06] -!- bill-auger has quit [Remote host closed the connection]
[21:03:31] -!- bill-auger has joined #archlinux32
[22:41:17] -!- GNUtoo has quit [Remote host closed the connection]
[22:41:53] -!- GNUtoo has joined #archlinux32