<Begasus[m]>
completed! :) grabbing opencv_python3.10-4.8.0-3-x86_64.hpkg and moving it to /Opslag/haikuports/packages/opencv_python3.10-4.8.0-3-x86_64.hpkg
<Begasus[m]>
hi erysdren (@_oftc_erysdren:matrix.org) :)
<OscarL>
Hey there erysdren! Nice to read you :-)
<OscarL>
Begasus[m]: noice!
<Begasus[m]>
lol
<Begasus[m]>
your noise :P
<Begasus[m]>
noice(?)
<OscarL>
Begasus[m]: just my silly attempt at saing "nice" in one of those odd accents used on the Brittish Islands.
* OscarL
may have watched one or too many movies from those places.
SLema has quit [Ping timeout: 480 seconds]
<Begasus[m]>
:D
<Begasus[m]>
k, maybe something is off on my end ... I'm getting the breeze icons for AbiWord, but just launched the one from the depot on 32bit and that still shows the gtk icons
<OscarL>
erysdren: oh, btw... congrats on the new job!
<Begasus[m]>
well, Haiku icons more likely
<erysdren>
thank you!!
<OscarL>
may it be rewarding in not only monetary sense, but also as a creative outlet! (one can dream :-D)
<Begasus[m]>
yeah, same from here erysdren (@_oftc_erysdren:matrix.org) :) nice to be able to work from home too I guess
<erysdren>
:P
<erysdren>
it's been neat so far (1week in) because i'm working on a codebase i'm already fairly familiar with (idTech 2 based)
<erysdren>
so there isnt much "training" to be done.
<Begasus[m]>
doesn't always have to be a rough road :)
<nekobot>
• korli (90318af3): openssl3: bump version
<TurBoss>
hurray
<Begasus[m]>
party? :)
<scanty>
hello to all my haiku friends :-)
<B2IA>
(AGMS) Hi scanty.
<scanty>
hey there B2IA (AGMS), how's your project going, please re-link me
<scanty>
the z80 project
<Begasus[m]>
howdy scanty :)
<scanty>
hi Begasus[m], abiword looking good!
<B2IA>
(AGMS) It hasn't done much, been busy with other things in September, including a tire blowout / crash that pretty much wrecked my car, fortunately just a few scrapes, no major injuries.
<Begasus[m]>
weird thing it looks different on this install scanty :)
<scanty>
B2IA (AGMS): i'm sorry to hear that, but i'm glad you are OK, and that's the most important
<B2IA>
(AGMS) Yup, the car's crumple zones worked, didn't need the airbag. Going sideways also bled off a lot of speed!
<Begasus[m]>
yeah, even uninstalled GTK3/adwaita_icon_theme ... still the same from pulling the depot packages
<scanty>
B2IA (AGMS): car totaled?
<B2IA>
(AGMS) My next Z80 thing is to fiddle with the Z88DK build system to add a relocating loader, so the program can load as usual after the 4K or 8K boot ROM, then turn off the ROM (revealing RAM), and move the code (including C runtime) to the beginning of memory, then start running. Gets me an extra 4K of memory!
<scanty>
wow cool!
<B2IA>
(AGMS) Side panels and driver's door dented (bounced off a truck bumper), front shattered into little bits of plastic (concrete barrier). Probably totaled, insurance mechanics are evaluating it.
<scanty>
4K goes a long way on old sytems
<scanty>
B2IA (AGMS): gotcha... glad you weren't injured, and it seems like your car saved you.
<B2IA>
(AGMS) Especially when I want to add things to my NthPongWars game, each powerup or other thing takes a few KB of code.
<scanty>
i'm hoping OscarL's peek/poke driver will work with my PCI parallel port so i can start working on a NES demo that i have wanted to write for a very long time.
bbjimmy has quit [Quit: Vision[]: i've been blurred!]
<scanty>
not sure what it will be yet, but we'll see
<B2IA>
(AGMS) Scanty, the hard part is doing all the boring bits to get code running, displaying things, etc. If you can survive that, then the fun part (or at least the part with more interactive feedback) of the game code begins!
<scanty>
indeed. it's hard to get started when you have to write a bunch of "boiler plate" code
<scanty>
once things are running, it should be more fun and rewarding, as you mentioned
AD_Haiku_onPC has joined #haiku
<B2IA>
(AGMS) That's the frustrating part about getting into gameplay and having the game becoming more fun, then running out of memory and having to go back to boilerplate for a while.
bbjimmy has joined #haiku
<scanty>
memory can be an issue, especially if you're working in C. my NES dev cart has 32K of program rom, and 8K chr rom (for graphics), certainly enough to write a simple demo
<B2IA>
(AGMS) It doesn't help that the C compiler is somewhat verbose in code generation. I had to hand code the routines for doing fractional integer math.
<scanty>
you'll probably wind up rewriting some code from C to ASM for more space
<scanty>
compilers can do funny things on "low end" systems
<B2IA>
(AGMS) Well, hopefully an extra 10K of RAM will let me finish the game, well, except for network play :-)
<scanty>
B2IA (AGMS): i was looking at some of the code, and i found the following really cute:
<scanty>
ld hl,0
<scanty>
add hl, sp; /* No actual move sp to hl instruction, but can add it. */
<scanty>
it's a tad "RISC"y
<AmyMalik>
chatty compiler
<scanty>
netplay would be really cool
<B2IA>
(AGMS) Yup, like I think I mentioned last time, https://clrhome.org/table/ is your friend for Z80 opcode picking.
<scanty>
yes, that is an awesome tool, i kind of want to do it for 6502
<B2IA>
(AGMS) I just used the folding paper card that came with the KIM-1, listing all the codes.
<nekobot>
• Begasus (1439cfa8): opencv, try to fix OOM for 32bit, no need for a revbump (#13041)
<scanty>
haha nice!
<scanty>
i have two 6502 books i used for reference, as well as a lot of C64 docs
<scanty>
use for reference*
<B2IA>
(AGMS) Nice chatting, but I should get back to painting the cottage siding before tonight's rain and cold weather the rest of the week.
<scanty>
nice chatting, indeed B2IA (AGMS), glad you are safe and all in once piece. will be watching your project progress.
<christech>
brb
christech has quit [Quit: Vision[]: i've been blurred!]
christech has joined #haiku
scanty has quit [Quit: Vision[]: i've been blurred!]
scanty has joined #haiku
<Begasus[m]>
closing down here, cu peeps!
<scanty>
hi guys, i am having problem with git
<scanty>
OpenSSL version mismatch. Built against 3050003f, you have 30500040
<scanty>
fatal: Could not read from remote repository.
scanty has quit [Quit: Vision[]: i've been blurred!]
<Halamix2>
scanty: sounds a bit like git was compiled with a different openSSl shared library in mind than what you have installed
<Halamix2>
and/or ssh or whatever is used by the git itself
scanty has joined #haiku
dostoevsky has quit [Remote host closed the connection]
<Halamix2>
scanty: ah, I chose perfect time to sent these two messages for you to be unable to see them, sorry
<scanty>
haha
<scanty>
can you resend?
<Halamix2>
scanty: sounds a bit like git was compiled with a different openSSl shared library in mind than what you have installed ; and/or ssh or whatever is used by the git itself
<scanty>
yeah, it seems like i need a new version of git, i guess?
<Halamix2>
or openssl, or both, yeah
<scanty>
well, i just installed the latest openssl this morning
<scanty>
and now i see git is broken, and i have no idea how to fix it.
<Halamix2>
maybe updating git will just work, 2.50.1-1 should be the latest for r1beta5
<scanty>
i'm on nightly
<scanty>
i have 2.50.1
<scanty>
i did a pkgman install git and it says i have latest version.,
<Halamix2>
Oh, I have the same issue on r1beta5, all possible updates installed; probably Git (or ssh) might need to be recompiled against the latest openSSL. Pulling repos through https works, so maybe it's ssh package issue, I don;t know if git uses ssh directly or through a library trom the ssh package
<Halamix2>
I'm not knowledgeable enough; I've added a comment to the issue
<scanty>
thanks.
scanty has quit [Quit: Vision[]: i've been blurred!]
flag has joined #haiku
flag_ has quit [Ping timeout: 480 seconds]
<Halamix2>
Was anyone working on Golang for the last ~year?
OscarL has joined #haiku
<OscarL>
bah... too late, scanty's gone already :-(
<OscarL>
in any case (perhaps might help Halamix2[m]?): after updating openssl, the older .hpkg should still remain on the system (on one of the "state" folders under /system/packages/administrative/)
<OscarL>
"query -a openssl*.hpkg" should reveal it, and then one should just be able to do: "pkgman install <path to that older openssl .hpkg file>" to install that previous version.
<Halamix2>
Yeah, I see the files, I guess that's a hotfix
dodo75 has quit [Quit: Vision[]: i've been blurred!]
dodo75 has joined #haiku
HaikuUser has joined #haiku
HaikuUser is now known as scanty
<scanty>
hey guys, just rebooted and the bootloader cannot find my Haiku drive
<scanty>
what can i do?
<scanty>
i'm on a live CD right now, and i can mount the disk no problem, and all my files are threre\
<scanty>
anyone?
<OscarL>
hey there scanty.
<OscarL>
system stopped booting after your last round of updates? (running nightly, right?
<scanty>
yes
<scanty>
it can't find a boot volume
<OscarL>
If so... you should be able to select a previous system state too boot, from the boot menu (either hold down SHIFT if using BIOS, or smash the spacebar if using UEFI, during POST).
<scanty>
i tried the spacebar smasher, and it doesn't have any previous states available
<OscarL>
ouch.
<scanty>
yeah, i don't know what to do
<OscarL>
Well, if you can see the state folder under /system/packages/administrative/...
<OscarL>
you could try to "manually install" those older packages back.
<OscarL>
I had done so in the past at least twice (as you... while running from a "live" media).
<scanty>
ok,i can see the states
<OscarL>
did you do anything else besides just updating the system and rebooting before it became unbootable?
<scanty>
nope, i just uninstalled some openssl and ssh packages
<scanty>
and then i couldn't boot anymore
<scanty>
should i install BootManager on the drive?
<OscarL>
mmm, not sure uninstalling openssl is even possible without also uninstalling other important stuff.
<scanty>
well, i reinstalled them
<scanty>
and then rebooted, and poof, gone.
<OscarL>
I assume you tried re-installing the older openssl3 package (the ones before the last update broke your git/ssh) ?
<scanty>
yes
<OscarL>
alright. dunno what could have broken the boot process in that case... oh well... before proceeding...
<OscarL>
could you past online (say, via https://bpa.st), the list of contents on your latests "state" folders (to see what packages have changed)
<OscarL>
Ideally, we should get back to the state "just before the initial update that broke things".
<scanty>
i have a million state files in there.
<OscarL>
they are time-stamped.
<scanty>
yes
<OscarL>
so just look for stuff with today's date.
<scanty>
i have four states with today's date
<OscarL>
(incidentally.... your slow boot times might be due to having way too many state folders there)
<scanty>
interesting, but that's not important right now.... have to get bootin'
<OscarL>
scanty: alright... if you can, please post the content list of all four (along with their timestamps)
<scanty>
ok, one sec i have to reboot.
scanty has quit [Quit: Vision[]: i've been blurred!]
HaikuUser has joined #haiku
HaikuUser is now known as scanthy
scanthy is now known as scanty
<scanty>
ok back up, OscarL, still there?
<OscarL>
yup-
<OscarL>
just to avoid possible confusions going forward...
<OscarL>
we better not confuse "/system/packages/" from the currently running system, from the one you want to fix.
<OscarL>
your, now not booting system... how it is named/mounted on your current boot instance?
<OscarL>
(ie: we don't care for "/boot/system/packages/", but we'll be doing stuff on "/FooBar/system/packages/")
<scanty>
ok, it looks like the disk mounts as "Haiku1"
<scanty>
if i goto system/packages i don't see those states i did before
<OscarL>
from an actuall CD boot... "/boot/ system/packages/administrative" should indeed no have "state" folders (read-only media).
<scanty>
ah OK, now i see them
<scanty>
/Haiku1/system/packages/administrative
<OscarL>
if the "CD" boot is from a USB-pendrive, one *may* have something there, but surelly way less than on your older (HDD) system install.
<OscarL>
alright.
<OscarL>
just wanted to point that out, because if we're gonna manually mess around with .hpkg... we better place them on the right folder/drive :-P
<scanty>
OK
<OscarL>
sort states by date, get a list of content for the four entries for today's date, and paste them online if you can.
<OscarL>
(that way we'll have an exact record of what .hpkg "movements" had happened today on that system, and we can try to revert them properly).
<scanty>
there's a million packages in there
<scanty>
do you want a list of states in "administrative", or something else?
<OscarL>
under "administrative/".... you say you have millions of "state-<timestamp>" folders... I'm just interested on the ones with today's date.
<scanty>
but yes, like i said, there's a million packages in each state
zardshard has quit [Ping timeout: 480 seconds]
<OscarL>
in each of the 4 last folders?
<scanty>
oh, ok i see now that each date does not have a million packages
<scanty>
i will take a screenshot of the four windows
<scanty>
hold on one sec
rodolphoeck_ has joined #haiku
<OscarL>
only case where a state folder would have "a million files" is when switching from beta5 to nigthly or viceversa, or after updating a system after a *long* time of not doing so.
DKnoto_W2 has joined #haiku
HaikuUser has joined #haiku
<OscarL>
(well... not exactly the only cases, more like... "in normal cases")
HaikuUser2 has joined #haiku
rodolphoeck has quit [Ping timeout: 480 seconds]
_whitelogger has joined #haiku
DKnoto_W has quit [Ping timeout: 480 seconds]
shann_ has joined #haiku
<OscarL>
np. give me sec while I try to figure things out a bit :-)
<scanty>
OK, i will be here :-)
arti_ has joined #haiku
_whitelogger_ has quit [Remote host closed the connection]
arti_ has quit []
shann has quit [Read error: Connection reset by peer]
arti_ has joined #haiku
mmu_man has joined #haiku
arti has quit [Ping timeout: 480 seconds]
<OscarL>
alright...
<OscarL>
scanty: we have 5 states. first 4 look normal (they might have a broken ssh, but nothing boot-breaking).
<OscarL>
has 503 packages in there... do you see any "haiku-*.hpkg" in there (and also... how many package do you actually see under /Haiku1/system/packages/ ?)
<scanty>
/Haiku1/system/packages has got 37 items
<OscarL>
heh, as I've suspected...
<OscarL>
one of your attempst to uninstall openssl or something like that... basically uninstalled your whole system :-D
<OscarL>
fix shouldn't be too hard.
HaikuUser has quit [Remote host closed the connection]
HaikuUser2 has quit [Remote host closed the connection]
<scanty>
haiku-r1~beta5_hrev59055-1-x86_64.hpkg
<scanty>
really?
<scanty>
is it fixable?
<OscarL>
that haiku*..hkpg is under the state_2025-10-06_13:26:56 forlder right?
<scanty>
yes
<OscarL>
yes, should be easy to fix.
<scanty>
great! i hope we can get to the bottom of this!
<OscarL>
I'm just trying to confirm things before giving to the easy steps.
<scanty>
surely ;-)
<OscarL>
alright..., what *I* would do is:
<OscarL>
1- copy into "/Haiku1/system/packages/" all the .hpkg files under the state folder "state_2025-10-06_13:26:56".
<OscarL>
2- remove the file "/Haiku1//system/packages/administrative/activated-packages"
<scanty>
OK, so copy in those 503 items into /Haiku1/system/packages ?
<OscarL>
yes.
<scanty>
ok, 1sec
<scanty>
mmkay, it will be a minute or two
<scanty>
copying now
<OscarL>
alright, if you happened to copy also the "activated-packages" file.. remove it from /Haiku1/system/packages once the copy is finished.
<OscarL>
(it is of no use there)
<scanty>
ok, done
<scanty>
removed that file
<OscarL>
steo 2 complete too? (remove the file "/Haiku1//system/packages/administrative/activated-packages")
<OscarL>
*step
<scanty>
yes, removed the activated-packages file
<OscarL>
3- reboot while crossing fingers.
<scanty>
hmm, OK, be back in a few minutes... recall my system takes a long time to boot!
<scanty>
wish me luck!
<OscarL>
will try fixing that next!
<OscarL>
good luck!
scanty has quit [Quit: Vision[]: i've been blurred!]
zardshard has joined #haiku
HaikuUser has joined #haiku
HaikuUser is now known as scanty
<scanty>
OK... progress... system boots, but seems to get stuck on the "rocket ship"
<scanty>
OscarL
<OscarL>
mmm
<OscarL>
tried using some of the boot options?, maybe one of the "on-screen debugging info", to see if it makes clear where the problem might be?
<scanty>
how do i get to the boot options?
<scanty>
i tried space bar smashing, but that leads to a blank screen
<OscarL>
alternatively... from your currently booted system, mount "/Haiku1"... and post /Haiku1/var/log/syslog" online.
<scanty>
OK, one sec
<OscarL>
scanty: boot options should be accessable from the boot menu, the one you get into via spacebar or holding SHIFT. given that you get upto the rocket, you *should* be able to get into the boot menu without problems, I think.
<scanty>
I don't have a /var directory on /Haiku1
<OscarL>
(just in case, remove all other media to make sure you're using the boot loader from the hard disk, and not the one from the CD)
<scanty>
oh here it s.
<OscarL>
scanty: from a Terminal, run:
<scanty>
is*
<OscarL>
"query -a syslog"
<scanty>
i found var in system directory, do you want me to post it
<scanty>
(the syslog)
<OscarL>
the one under /boot/ is of no use (as that's from your current running system).
<OscarL>
we need the one from the failed attempt to boot (from the HDD).
<scanty>
yes, i found it
<OscarL>
alright, if you have the one from the HDD, yes, post that on bpa.st or somewhere similar, please.
<OscarL>
I wonder if you have either a missing package (not seeing how, given the screenshot you posted with the state folders), or if you have some "extra" package that we need to remove :-D
<OscarL>
let's see.
<scanty>
OK
Aedil has quit [Quit: leaving]
<OscarL>
other than some runtime_loader errors, not seeing much there. and even so... those errors seems from a previous boot while using one of the firefox derived browsers.
<OscarL>
try getting into the boot options, and select: "Enable on screen debug output" and "Disable on screen paging"
<OscarL>
then continue normal booting, with any luck, you'll be able to see where it gets stuck.
<OscarL>
(might want to remove that syslog file from /Haiku1/, so we might get a clean new one)
<scanty>
OK
<OscarL>
(might not be saved, if boot fails, though)
<scanty>
brb again
scanty has quit [Quit: Vision[]: i've been blurred!]
chilledfrogs has quit [Quit: connection reset by purr]
<OscarL>
yeah, that syslog is from when whatever scanty tried... ended up uninstalling 502 package :-D
diver has quit [Quit: Leaving.]
scanty has joined #haiku
<scanty>
success!
<scanty>
i was able to boot to an activation state from yesterday
<christech>
nice
<scanty>
OscarL: thank you so much for your help!
<OscarL>
very good. glad it worked!
<scanty>
me too!
<scanty>
going to wait a few days to upgrade, and maybe the ssh problems will be solved
<scanty>
ssh currently works afaict
jmairboeck has quit [Quit: Konversation terminated!]
<OscarL>
scanty: regarding your slow boot times... maybe it is time to remove some of the bazillion state folders (leaving only there, say... the ones from this week, just in case).
<scanty>
OK, will do. i did notice that when i couldn't boot before, the boot time itself seemed like it would have been much faster
chilledfrogs has joined #haiku
<scanty>
ok cool, git works too!
<scanty>
just did a push to test, and it wroked
<scanty>
worked*
<OscarL>
also, it should be possible to make the current state you booted into the "default one"... just copy the .hpkg from the proper "yesterday state" into /system/packages/, remove "/system/packages/administrative/activated-packages")
<OscarL>
you might need to scan /system/packages/* for .hpkg files of the same name, but different version (say... you may have two different openssl3*.hpkg packages there... remove the ones not presen on the "yesterday state that boots".
<scanty>
hold, on, one thing at a time!
<OscarL>
after that, try rebooting without selecting a different state, if it works. NICE, if not... well, you can go back to your currently working "state from yesterday).
<scanty>
copy which hpkg to where?
<OscarL>
you said you were able to boot by selecting a previous state, right?
<scanty>
yes, i just don't remember what goes where
<OscarL>
k.
<OscarL>
first thing...
<OscarL>
let's try to figure out exactly which state folder you booted from.
<scanty>
ok
<OscarL>
should be one of the /boot/system/packages/administrative/state_2025-10-05... ones, I guess?
<scanty>
ok, 1 sec
<scanty>
sorry i'm slow!
<OscarL>
meh... I'm slower :-D
<scanty>
shit, i don't remember what state it was.
<scanty>
have to reboot again, sorry
<OscarL>
np
<scanty>
brb
scanty has quit [Quit: Vision[]: i've been blurred!]
scanty has joined #haiku
<scanty>
OK, OscarL, i found the package activation state
<OscarL>
good.
<scanty>
let's make it the default
<scanty>
tell me what to do
<OscarL>
what I would do is... copy all the .hpkg from that state (/boot/system/administrative/state_<the-one-that-works>/) into /boot/system/packages/
<scanty>
all righty, one sec
<OscarL>
then we might need to remove some newer .hkpg that might be interfering (I'm guessing you'll be seeing at least two versions of openssl3 there)
<scanty>
ok, so going from /boot/system/packages/administrative/state_2025-10-05_20:37:21 into /boot/system/packages ?
<scanty>
it's only 9 items
<OscarL>
scanty: assuming that's the one you're currently booted from, then yes.
<scanty>
ok
<OscarL>
(remember, no need to copy the "activated-packages" file, only the .hpkg ones)
<scanty>
ok, did that and then a window came up with "Package changes"
<scanty>
should i make the changes?
<OscarL>
ah, forgot about that one... it happens because we're altering the "/boot/" /system/packages unlike before, where we were booted from a different install.
<OscarL>
scanty: I can't exactly recall, but I guess you can say "yes" there.
<scanty>
OK
<OscarL>
we would be removing the resulting /boot/system/packages/administrative/activated-packages file before rebooting, anyway.
<scanty>
OK, made the changes
<scanty>
suppose i should reboot now?
<OscarL>
not yet.
<OscarL>
first lets check a few things...
<scanty>
hmm hold on got an alert
<scanty>
"failed to commit transaction: The to be activated package "haiku-r1~beta_5_hreve59055-1-x86_64. hpkg" does already exist
<OscarL>
yeah, makes sense.
<scanty>
same thing happened with zlib
<OscarL>
right.. disregard them all, will need to compare things manually anyway.
<scanty>
ok
<scanty>
ready for next step
<OscarL>
"open /boot/system/packages" and "/boot/system/packages/administrative/state_2025-10-05_20:37:21"
<scanty>
mmkay one sec
<scanty>
ok, they are both open
<OscarL>
first thing would be... make sure the 9 .hpkg from the "state" folder are indeed copied into the former
<scanty>
ok let me check
<scanty>
everythign seems to be in there, however there are two makefile engines
<scanty>
one from 59053 and 59055
<scanty>
same with webpositive
<OscarL>
I see. can you upload "/boot/system/packages/administrative/state_2025-10-05_20:37:21/activated-packages" into bpa.st ?
<scanty>
yes, you just want me to do an "ls"
<scanty>
?
<OscarL>
I need the actual ""/boot/system/packages/administrative/state_2025-10-05_20:37:21/activated-packages", and an ls -l of /boot/system/packages/
<OscarL>
will make searching for "extra" packages much easier (once we sort both lists and use diff on them)
<scanty>
ok, 1 sec
<OscarL>
scanty: the idea is... only leave in /boot/system/packages/ the ones that are listed inside "/boot/system/packages/administrative/state_2025-10-05_20:37:21/activated-packages", and removing any extras.
<OscarL>
after that, removing "/boot/system/packages/administrative/activated-package" and a reboot should be enough to fix your boot.
* OscarL
wishes "activated-packages" files were saved already alphabetically sorted.
Slimey has joined #haiku
<OscarL>
scanty: can you upload "/boot/system/packages/administrative/state_2025-10-05_20:37:21/activated-packages" too? (or open it and copy/paste its content into bpa.st)
<scanty>
they are both there
<scanty>
;oh wait
<scanty>
you're right, hold on
<Slimey>
hello i am attempting to boot haiku from a flash drive with an iso i have used dd to write to the drive and it is hanging on the hakiu logo with none of the icons changing
<scanty>
OscarL: pretty sure 59055 is the one that didn't boot.
<scanty>
59053 works
<scanty>
(that's what i'm on now)
<OscarL>
scanty: so I would remove from /boot/system/packages/ : all the haiku*beta5_hrev59055*.hpkg files, and also makefile_engine-r1~beta5_hrev59055-1-any.hpkg
<OscarL>
scanty: webpositive-r1~beta5_hrev59055-1-x86_64.hpkg needs to go too.
<OscarL>
scanty: also remove "openssl3-3.5.4-1-x86_64.hpkg" from /boot/system/packages/ (otherwise it will get used on the next boot)
<scanty>
ok, so basically i'm removing any 59055 stuff
<scanty>
?
<OscarL>
yes. but do not reboot just yet... I think you'll be missing two .hpkg files in /boot/system/packages yet
<scanty>
ok, let me delete those, hold on
<scanty>
ok removed all the 59055 stuff as well as openssl
<OscarL>
"openssl3-3.5.3-1-x86_64.hpkg" and "gcr-3.41.1-3-x86_64.hpkg" are the only two packages listed in the "activated-packages" (that allowed you to boot), that are missing from the /boot/system/packages list...
<OscarL>
so.... you will need to use "query" to find them, and copy them into /boot/system/packages
<OscarL>
scanty: then only need to do is: remove /boot/system/packages/administrative/activated-packages, and reboot while doing a little praying :-D
<scanty>
ok, done... reboot & pray?
<OscarL>
(you should still be able to boot into the "state_2025-10-05_20:37:21" if it doesn't works as expected)
<OscarL>
scanty: yes. good luck!
<scanty>
OK, brb hopefully!
scanty has quit [Quit: Vision[]: i've been blurred!]
scanty has joined #haiku
<scanty>
OscarL: you are a star!
<scanty>
i owe you a beer, at the least :-)
<OscarL>
:-D
<scanty>
thank you sooooo much!
<OscarL>
glad it worked.!
<scanty>
couldn't have done it without you
<scanty>
me too!
<OscarL>
now... time for a clean up?
<OscarL>
did you already removed old(er) state folders?
<scanty>
i have not
<scanty>
i suppose i can
<scanty>
i have a million states in there haha
<OscarL>
you may want to double check that current boot can be rebooted before doing so, but if that indeed works...
<OscarL>
I guess you could just nuke /boot/system/packages/administrative/* :-D
<OscarL>
at the very least, it will make easier to see what changes on the next updates :-D
<scanty>
i have states going back to 2023!
<OscarL>
you have some very old packages under /system/packages too, sadly pkgman doesn't yet offers a proper clean up option.
<scanty>
that would be a great feature.
<OscarL>
so manual intervention will be needed., if you care enough.
<scanty>
i'm going to nuke all the old states from 2023, and 2024
<scanty>
ok, got rid of a lot of states, let's see if i can boot any faster
* scanty
boot & pray, brb
scanty has quit [Quit: Vision[]: i've been blurred!]
scanty has joined #haiku
<scanty>
hooray!
<scanty>
OscarL: you saved my day :-)
<OscarL>
:-)
<scanty>
booting is still slow, but that doesn't matter... what matters is that it works :-)
<scanty>
brb
scanty has quit []
scanty has joined #haiku
<scanty>
ok, everything looks good.
<gordonjcp>
scanty: you got it working?
<scanty>
yep :-)
<gordonjcp>
cool :-)
<scanty>
indeed. not exactly how i wanted to spend today, but thing happen sometimes.
<scanty>
things*
<scanty>
can't believe how a package or two could break things so badly.
<scanty>
going out for a smoke, brb
<OscarL>
for when scanty comes back: the following packages under your /boot/system/packages look to me like they can be unistalled (but pay attention to what "pkgman uninstall" has to say about each, just in case). https://bpa.st/QYPQ
<OscarL>
scanty: to be fair... judging by the syslog you posted earlier... I'm almost 100% sure that pkgman/HaikuDepot had issued a warning about it going to uninstall 502 packages before doing so :-D
<OscarL>
(one tends to be too quick to hit "yes", though... been there)
<OscarL>
bbl.
OscarL has quit []
nipos has left #haiku [Error from remote client]
nipos has joined #haiku
<Slimey>
OscarL no joy, just freezes
<bjorkintosh>
why does it just freeze?
<bjorkintosh>
what makes it not keep going?
<bjorkintosh>
what does it want?
<bjorkintosh>
network resource?
<Slimey>
none of the safe mode shift or space keyboard options work
<gordonjcp>
Slimey: when you hold down shift as you boot it up, you don't see a text-mode menu?
<gordonjcp>
okay, so for whatever reason, it's not reading the keyboard
<gordonjcp>
are you pressing shift before it shows anything of the icons?
<Slimey>
yes
<Slimey>
i tried an external usb keyboard also
<gordonjcp>
Slimey: what hardware is this on?
<Slimey>
latitude 7400
Habbie has quit [Remote host closed the connection]
<gordonjcp>
okay, not a million miles from my Thinkpad T430
OscarL has joined #haiku
<gordonjcp>
bit newer, but not by a hell of a lot
<OscarL>
Slimey, gordonjcp: pressing SHIFT does not works for UEFI boot. need to "spam" the spacebar instead.
<gordonjcp>
Slimey: have you got anything "odd" set in your BIOS, for things like USB devices
<gordonjcp>
OscarL: ah okay
<gordonjcp>
does it need to be UEFI?
<OscarL>
Slimey: if you can't get into the boot menu options... not much you can do then, other than open a ticket over dev.haiku-os.org with details of what you tried and hardware specs, but without more debug info... doubt much can be done.
<gordonjcp>
Slimey: can you try it with normal BIOS instead of UEFI?
<OscarL>
if you manage to get into the boot menu options... try enabling the on-screen debugging info options, so you can see where exactly halts.
<OscarL>
other than that, as gordonjcp says, see if using BIOS/CSM/Legacy might help, or try different USB ports for the boot drive (some BIOS/UEFI are very picky).
<OscarL>
I have one machine that refuses to boot Haiku from USB, but will more than happily boot it from HDD (had to take out the drive, and install it on a different computer first, of course :-D)
HaikuUser has joined #haiku
HaikuUser has quit []
<OscarL>
gotta bolt. Laterz!
OscarL has quit []
e1z07567351 has joined #haiku
e1z07567351 is now known as e1z0
<swiftbanana[m]>
Fun you talk about a Dell Latitude that won’t boot to Haiku, I just tried to install it to my Dell Precision m4600, and in BIOS mode it boots fine but in UEFI it’s an instant reboot
<swiftbanana[m]>
(Which is a problem since the other OSes on the drive are installed in UEFI/GPT and I do not want to reinstall everything in BIOS/MBR)