Compare commits

..

No commits in common. "443299c9068e9c3bc1be50352f12b89f47360cbf" and "99f74e83ac64adca0b6e10436c2305352a7db892" have entirely different histories.

3 changed files with 7 additions and 7 deletions

View File

@ -11,7 +11,7 @@ ci:
default_language_version: default_language_version:
node: "lts" node: "lts"
# Remember .python-version and pyproject.toml ! # Remember .python-version and pyproject.toml !
python: "3.13" python: "3.12"
ruby: ".ruby-version" ruby: ".ruby-version"
repos: repos:

View File

@ -1 +1 @@
3.13.0rc2 3.12.4

View File

@ -44,20 +44,20 @@ if hash dnf 2> /dev/null; then
# I don't know if -y does anything here either and I think this may be # I don't know if -y does anything here either and I think this may be
# useless, but I am used to it coming from apt and I think it will just # useless, but I am used to it coming from apt and I think it will just
# say nothing to do or do nothing if mirrors haven't updated. # say nothing to do or do nothing if mirrors haven't updated.
dnf check-update -y dnf -v check-update -y
# potentially unsafe first time, I am not sure if this is concern outside of Debian/Ubuntu though # potentially unsafe first time, I am not sure if this is concern outside of Debian/Ubuntu though
dnf "$@" autoremove dnf -v "$@" autoremove
# If arguments like -y are passed to the script, they become "$@" # If arguments like -y are passed to the script, they become "$@"
#dnf "$@" upgrade #dnf -v "$@" upgrade
# Doing check-update and upgrade together seems to be necessary for # Doing check-update and upgrade together seems to be necessary for
# Chromium based browsers and their repositories :shrug: # Chromium based browsers and their repositories :shrug:
dnf "$@" upgrade --refresh dnf -v "$@" upgrade --refresh
# potentially unsafe, see a few lines above and the apt-get section # potentially unsafe, see a few lines above and the apt-get section
dnf "$@" autoremove dnf -v "$@" autoremove
fi fi
# Arch Linux package management # Arch Linux package management