<cruxbot>
[opt.git/3.7]: thunderbird-bin: updated to version 115.1.1
<cruxbot>
[opt.git/3.7]: rsyslog: updated to version 8.2308.0
<cruxbot>
[contrib.git/3.7]: python3-maturin: updated to version 1.2.1
<cruxbot>
[contrib.git/3.7]: nginx: updated to version 1.25.2
ppetrov^ has joined #crux
G-Unit4 has joined #crux
ppetrov^ has quit [Quit: Leaving]
lavaball has joined #crux
<cruxbot>
[opt.git/3.7]: krb5: update to 1.21.2
<cruxbot>
[opt.git/3.7]: conky: update to 1.19.4
ppetrov^ has joined #crux
<cruxbot>
[core.git/3.7]: kbd: update to 2.6.2
<cruxbot>
[core.git/3.7]: python3-setuptools: update to 68.1.0
G-Unit4 has quit [Quit: Quit]
stoffepojken has quit [Quit: ZNC 1.8.2 - https://znc.in]
stoffepojken has joined #crux
groovy3shoes has joined #crux
lavaball has quit [*.net *.split]
groovy2shoes has quit [*.net *.split]
aardo has quit [*.net *.split]
lavaball has joined #crux
aardo has joined #crux
ppetrov^ has quit [Quit: Leaving]
ppetrov^ has joined #crux
dim44 has joined #crux
<dim44>
In the documentation for upgrading it says to "Finish the upgrade by Installing a Bootloader, and then you should be able to login to your upgraded CRUX system after rebooting."
<dim44>
Do I need to reinstall the bootloader, or just to configure it for the new kernel? Also does the /boot partition need to be mounted when executing the "setup" script?
<ukky>
Are you upgrading from older to newer CRUX version? Are you switching from other Linux distro to CRUX?
<dim44>
ukky: I'm upgrading from CRUX 3.6
<ukky>
then you don't need to re-install your bootloader, just change command line if you use newer kernel
<ukky>
No need to mount /boot partition to run 'setup'
<dim44>
ukky: Thanks. Also after I execute the setup script successfully, can I just do a "prt-get sysup" to recompile everything including the contrib packages that I've got installed?
<dim44>
I mean after chrooting into the the mounted root tree
<ukky>
Yes, you can do 'prt-get sysup' from chroot before a reboot.
<SiFuh_>
Hmm, wonder bootloader ;-)
dim44 has left #crux [Leaving]
z3bra has quit [Remote host closed the connection]
dim44 has joined #crux
groovy3shoes has quit [Ping timeout: 248 seconds]
groovy2shoes has joined #crux
dim44 has quit [Remote host closed the connection]
dim44 has joined #crux
wgs has joined #crux
wgs has quit [Remote host closed the connection]
z3bra has joined #crux
<cruxbot>
[contrib.git/3.7]: python3-maturin: updated to version 1.2.2
<cruxbot>
[contrib.git/3.7]: bind: updated to version 9.18.18
z3bra has quit [Remote host closed the connection]
z3bra has joined #crux
z3bra has quit [Remote host closed the connection]
z3bra has joined #crux
z3bra has quit [Remote host closed the connection]
z3bra has joined #crux
z3bra has quit [Remote host closed the connection]
z3bra has joined #crux
z3bra has quit [Remote host closed the connection]
z3bra has joined #crux
jue has joined #crux
jue has quit [Changing host]
jue has joined #crux
<cruxbot>
[opt.git/3.7]: python3-mysqlclient: update to 2.2.0
<cruxbot>
[opt.git/3.7]: python3-mysql: renamed to python3-mysqlclient
<cruxbot>
[opt.git/3.7]: samba: fix dependencies
<cruxbot>
[opt.git/3.7]: php: update to 8.2.9
<cruxbot>
[opt.git/3.7]: mozjs78: dropped
lavaball has quit [Remote host closed the connection]
<dim44>
I'm doing a Crux update from 3.6 to 3.7. Everything is being done in a chroot. After executing the install script and chrooting into the updated system I tried running sysup. Output is in the following pastebin
<dim44>
and libcrypto. bsdtar doesn't work so I can't recompile openssl.
<SiFuh_>
Did you do a revdep by any chance?
<dim44>
It's all in a chroot and I am backed up btw
<dim44>
Nope will look into it
<SiFuh_>
Seems your system is broken
<SiFuh_>
Openssl is from core
<SiFuh_>
libcrypto is also from OpenSSL which is from core
<dim44>
Ok but where was the mistake? What do I do differently?
<SiFuh_>
I'd check curl with revdep
<SiFuh_>
revdep -vvv curl
<SiFuh_>
But I'd check revdep on the entire system if core is broken.
<SiFuh_>
Then rebuild all the ports in core that are broken, such as curl
<dim44>
revdep is still running, probably all packages are broken
<SiFuh_>
You technically only need core
<dim44>
But why did they break with the sysup?
<SiFuh_>
Once that is done, you are home sweet home to fix any other issues
<SiFuh_>
No idea, just saying what I see from your paste
<SiFuh_>
sysup doesn't do rebuilds of every port it requires that is why we have revdep
<dim44>
Wait, the /etc/os-release file is still VERSION="3.6". Could that have anything to do with it.
<SiFuh_>
OS release is from the port core/filesystem
<SiFuh_>
Should be 3.7 if you updated
<SiFuh_>
Did you change the contents of /etc/ports/core.rsync to 3.7?
<dim44>
That's probably it
<SiFuh_>
And opt and contrib and compat* and xorg
<SiFuh_>
Haha
<dim44>
Okay I'll just load a backup and redo it.
<SiFuh_>
If you wish, but CRUX is fixable if you have the time
<dim44>
Is there anything else that I should change after running the setup script? Was editing /etc/ports/core.rsync in the upgrade guide?
<dim44>
I will into just using the ports from the upgrade iso and pkgadd them over the malfunctioning ones
<dim44>
*I will look into
<SiFuh_>
Oh and rejmerge exists also
<SiFuh_>
dim44: Never upgraded in my life. I just fresh install because I like to start fresh. Always backup though, just like you did
<dim44>
Alright curl works!
<SiFuh_>
Cool
<SiFuh_>
farkuhar: The above. Is there a comprehensive installation guide based only on upgrading yet?
<dim44>
I doun the problem. The old filesystem core package got installed with sysup. But after removing filesystem I cannot install the 3.7.3 one even with -f and -uf
<dim44>
*found
<SiFuh_>
Yeah, you should have changed the etc/ports/*.rsync files to 3.7
<farkuhar>
dim44: your pkgadd.conf might be protecting the existing files under /etc from being overwritten when ports are updated.
<dim44>
It is! And there are a lot of files here, including the correct ports/*.rsync files
<jaeger>
That's where 'rejmerge' comes in
<dim44>
jaeger: Is there manpage for it?
<jaeger>
There is. There's also a note about it in the "Upgrading a Package" section of the handbook, 5.2.2
<jaeger>
Maybe it should be specifically added/called out in the main upgrade section...
<farkuhar>
Not directly relevant to dim44's upgrade situation, but this discussion reminds me of a question that popped up on the mailing list some years ago ... do the pre- and post-install scripts get executed when installing packages from the booted ISO (before chrooting)?
<dim44>
jaeger: Nice didn't know about it, I'll do a diff on the pkg/rejected folder to see the files that got rejected on the upgrade specifically and clean up the folder with rejmerge afterwards
<farkuhar>
Skimming through the setup script, it appears that pkgadd gets called, but not the pre-install or post-install script for selected ports. But we deploy 'runscripts yes' as the default in the CRUX 3.7 release, so maybe some logic should be added to ensure that install scripts do run, on a clean install.
ppetrov^ has quit [Quit: Leaving]
<farkuhar>
A few months ago I was investigating the broken combination of 'prt-get --install-root=$ROOT' and 'runscripts yes'. I eventually committed a few changes to my prt-get fork that seem to address the problem, but I haven't tested those changes to the same extent as dim44 has tested 'pkgadd -r $ROOT' today.
darfo has quit [Remote host closed the connection]
darfo has joined #crux
<jaeger>
farkuhar: pkgutils/pkgadd doesn't know anything about prt-get's runscripts option, if that makes it more clear... so no, no scripts are happening during setup. In the past if wasn't a requirement since no ports on the ISO had pre- or post-install scripts
<jaeger>
Would require the aforementioned separate logic, or to use prt-get in some fashion
<farkuhar>
I'm surprised the thread didn't generate more discussion beyond Xavier's reply, because the change Xavier suggested would not have any effect until Tom Armistead ran 'prt-get update' on an outdated port.
tilman has quit [Ping timeout: 245 seconds]
tilman has joined #crux
<jaeger>
I think there was a time when no ISO ports had runscripts but maybe I was wrong