Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add update instructions to the wiki #415

Open
Alkohole opened this issue Dec 31, 2024 · 3 comments
Open

Add update instructions to the wiki #415

Alkohole opened this issue Dec 31, 2024 · 3 comments
Assignees
Labels
question Further information is requested

Comments

@Alkohole
Copy link

When attempting to update via sudo apt install, I noticed an interesting nuance: every package remains at version 1.0 regardless of the release, which prevents anything from updating. Moreover, winver outright refuses to install via apt.

Perhaps I'm being too aggressive, but I just wipe everything in the /fre directory:

for file in *.deb; do 
    pkg=$(dpkg-deb -f "$file" Package); 
    sudo apt remove -y "$pkg"; 
done

It's so strange and oddly beautiful to watch the system crumble right before your eyes :)
Next time, I should probably disable themes and decorations before removing them...

In any case, after this, the installation completes successfully on all counts.

@rozniak rozniak self-assigned this Jan 1, 2025
@rozniak rozniak added the question Further information is requested label Jan 1, 2025
@rozniak
Copy link
Owner

rozniak commented Jan 1, 2025

Mmmmm yeah I do need to come up with something for the version number, its only really cos the project is still under development that everything remains at '1.0' . It is a little annoying in cases like that with apt, I think there should be some switch or something to make it 'reinstall' with the newer package.

In regards to winver that might be because I changed the name to be in line with everything else not too long ago... from wintc-shell-winver to wintc-winver. Not something that will be done very often I think there's only one package left with the older naming scheme.

Will try to come up with a solution to the versioning problem at some point.. 🤔

@Alkohole
Copy link
Author

Alkohole commented Jan 1, 2025

Maybe instead of version numbers, use the release or build date?
For example, in the format 1.MM.DD, where the global version "1" can be incremented each year, or 1. YYMMDD, without changing the global version.

Indeed, apt install has the --reinstall option, which forces packages to reinstall, but for some reason, I forgot about it... Heh, yesterday it seemed like a "good idea" to wipe everything to install it again.

@rozniak
Copy link
Owner

rozniak commented Jan 1, 2025

That's what I am thinking of, though probably based off of the latest commit date or something... I know the project doesn't really care too much about reproducibility per se (already including timestamp in a couple packages) but package versioning should probably be reproducible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants