Release 0.15 on OBS does not contain all changes from GH release 0.15

openSUSE / openSUSEway

dotfiles for Sway on openSUSE

MIT License

82 stars 17 forks source link

Release 0.15 on OBS does not contain all changes from GH release 0.15 #99

Closed FilippoBonazziSUSE closed 1 year ago

FilippoBonazziSUSE commented 1 year ago

Hi, I just noticed that the current 0.15 release tarball on OBS does not contain all changes from the 0.15 tagged release on Github. At least .config/alacritty/alacritty.yml is different (still contains old content), possibly other files as well. I'm not sure how this happened.

I'm going to fix this by submitting a SR on OBS adding a _service file which uses the obs_scm service. This way we can always be sure that we're pulling all GH changes.

FilippoBonazziSUSE commented 1 year ago

Fix submitted in https://build.opensuse.org/request/show/1062433

jubalh commented 1 year ago

https://build.opensuse.org/request/show/1062433 accepted

FilippoBonazziSUSE commented 1 year ago

I checked again and now the same OBS tarball is fine. What the hell did I see the first time around?? I'm sure I saw the outdated alacritty config, as I still had the visible warning in my terminal in a VM. Maybe the VM was not updated as I thought it was?

Anyway this change should be just a net improvement regardless.