Zypper Repo Not Set to Autorefresh (?) #12

Open
opened 2025-09-10 22:49:52 -05:00 by giteasync · 1 comment
Owner

Originally created by @FOSSProponent9436 on GitHub.

The command provided by the site to create the opensuse repo:

printf "[gitlab.com_paulcarroty_vscodium_repo]\nname=gitlab.com_paulcarroty_vscodium_repo\nbaseurl=https://download.vscodium.com/rpms/\nenabled=1\ngpgcheck=1\nrepo_gpgcheck=1\ngpgkey=https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/-/raw/master/pub.gpg\nmetadata_expire=1h" | sudo tee -a /etc/zypp/repos.d/vscodium.repo

doesn't enable autorefresh. I noticed this when looking at yast and realised that since autorefresh=1 isn't explicitly set in the config, it seems to actually not autorefresh. This means zypper dup wasn't refreshing the repo, so I wasn't getting updated versions. If the command could be updated to include autorefresh it would be great.

Originally created by @FOSSProponent9436 on GitHub. The command provided by the site to create the opensuse repo: `printf "[gitlab.com_paulcarroty_vscodium_repo]\nname=gitlab.com_paulcarroty_vscodium_repo\nbaseurl=https://download.vscodium.com/rpms/\nenabled=1\ngpgcheck=1\nrepo_gpgcheck=1\ngpgkey=https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/-/raw/master/pub.gpg\nmetadata_expire=1h" | sudo tee -a /etc/zypp/repos.d/vscodium.repo` doesn't enable autorefresh. I noticed this when looking at yast and realised that since autorefresh=1 isn't explicitly set in the config, it seems to actually not autorefresh. This means zypper dup wasn't refreshing the repo, so I wasn't getting updated versions. If the command could be updated to include autorefresh it would be great.
Author
Owner

@FOSSProponent9436 commented on GitHub:

Thought I ran the wrong command or something after seeing this was what my file looked like:

[gitlab.com_paulcarroty_vscodium_repo]
name=gitlab.com_paulcarroty_vscodium_repo
enabled=1
autorefresh=1
baseurl=https://download.vscodium.com/rpms/
type=rpm-md
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/-/raw/master/pub.gpg
keeppackages=0

but I realised that is probably yast more of the file than i expected after setting autorefresh. Still, after redoing the command yast shows that the repo is not set to autorefresh. The current config file does have metadata_expire=1h but I'm not sure if that means it autorefreshes. At least in my experience, it didn't autorefresh for me

Current config file after doing the command as shown on the website:

[gitlab.com_paulcarroty_vscodium_repo]
name=gitlab.com_paulcarroty_vscodium_repo
baseurl=https://download.vscodium.com/rpms/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/-/raw/master/pub.gpg
metadata_expire=1h
@FOSSProponent9436 commented on GitHub: Thought I ran the wrong command or something after seeing this was what my file looked like: ``` [gitlab.com_paulcarroty_vscodium_repo] name=gitlab.com_paulcarroty_vscodium_repo enabled=1 autorefresh=1 baseurl=https://download.vscodium.com/rpms/ type=rpm-md gpgcheck=1 repo_gpgcheck=1 gpgkey=https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/-/raw/master/pub.gpg keeppackages=0 ``` but I realised that is probably yast more of the file than i expected after setting autorefresh. Still, after redoing the command yast shows that the repo is not set to autorefresh. The current config file does have metadata_expire=1h but I'm not sure if that means it autorefreshes. At least in my experience, it didn't autorefresh for me Current config file after doing the command as shown on the website: ``` [gitlab.com_paulcarroty_vscodium_repo] name=gitlab.com_paulcarroty_vscodium_repo baseurl=https://download.vscodium.com/rpms/ enabled=1 gpgcheck=1 repo_gpgcheck=1 gpgkey=https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/-/raw/master/pub.gpg metadata_expire=1h ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: VSCodium/vscodium.github.io#12
No description provided.