Garuda-gnome-settings: local (1.5.1-1) is newer than garuda (1.5.0-1)

Issues & Assistance GNOME
1

I’ve had this problem before and posted about it, but I can’t find the post.

I am updating with garuda-update via the setup assistant.

This is the full terminal output which is relevant:

:: Starting full system upgrade...
warning: garuda-gnome-settings: local (1.5.1-1) is newer than garuda (1.5.0-1)
resolving dependencies...
looking for conflicting packages...

Packages (20) android-udev-20231104-1  garuda-welcome-1.2.5-1  git-2.42.1-1  gjs-2:1.78.0-3  iproute2-6.6.0-2
              lib32-xz-5.4.5-1  libheif-1.17.3-1  libphonenumber-1:8.13.24-1  libuv-1.47.0-1  nodejs-21.1.0-1
              papirus-icon-theme-20231101-1  protobuf-25.0-1  protobuf-c-1.4.1-5  qt6-base-6.6.0-3
              sof-firmware-2023.09.1-1  thin-provisioning-tools-1.0.7-1  ugrep-4.3.2-1  util-linux-2.39.2-2
              util-linux-libs-2.39.2-2  xz-5.4.5-1

I have found a way to address he problem at https://ostechnix.com/how-to-fix-warning-local-is-newer-than-community-error-in-arch-linux/ , but I’m sure I didn’t have to do this before.

Am I overlooking something?

My apologies for being a pain.

```text
System:
  Kernel: 6.5.9-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 clocksource: tsc
    available: hpet,acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=e0aa6bf1-e32d-48b2-a659-01e4322f83f8 rw rootflags=subvol=@ quiet quiet
    rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=31f5f81c-4fb3-4a39-893a-3e7c25a0feb6 loglevel=3 ibt=off
  Desktop: GNOME v: 45.1 tk: GTK v: 3.24.38 wm: gnome-shell dm: GDM v: 45.0.1
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X513UA_M513UA v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X513UA v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC.
    v: X513UA.312 date: 04/26/2022
Battery:
  ID-1: BAT0 charge: 32.7 Wh (83.0%) condition: 39.4/42.1 Wh (93.7%) power: 11.5 W volts: 11.8
    min: 11.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: discharging cycles: 573
CPU:
  Info: model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 2 gen: 3
    level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x68 (104) stepping: 1 microcode: 0x8608103
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 8 MiB desc: 2x4 MiB
  Speed (MHz): avg: 981 high: 1397 min/max: 400/4056 scaling: driver: amd-pstate-epp
    governor: powersave cores: 1: 400 2: 1397 3: 1397 4: 1397 5: 1397 6: 400 7: 400 8: 400 9: 1397
    10: 400 11: 1397 12: 1397 bogomips: 50307
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Lucienne vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c
    class-ID: 0300 temp: 39.0 C
  Device-2: Quanta USB2.0 HD UVC WebCam driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 3-3:3 chip-ID: 0408:30d4 class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 compositor: gnome-shell
    driver: X: loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: Samsung 0x4161 built: 2020 res: 1920x1080 dpi: 142 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: Vulkan v: 1.3.269 layers: 3 device: 0 type: integrated-gpu name: AMD Radeon Graphics
    (RADV RENOIR) driver: mesa radv v: 23.2.1-arch1.2 device-ID: 1002:164c
    surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM 16.0.6 256 bits)
    driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM 16.0.6) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASUSTeK driver: N/A
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci,
    snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.5 chip-ID: 1022:15e2
    class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  API: ALSA v: k6.5.9-zen2-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 0.3.84 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:2725 class-ID: 0280
  IF: ap0 state: up mac: <filter>
  IF-ID-1: enp3s0f3u3 state: up speed: 150 Mbps duplex: half mac: <filter>
  IF-ID-2: wlp1s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1
    mode: 1.1 bus-ID: 3-2:2 chip-ID: 8087:0032 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running rfk-block:
    hardware: no software: yes address: <filter> bt-v: 5.3 lmp-v: 12 status: discoverable: no
    pairing: no
Drives:
  Local Storage: total: 937.21 GiB used: 96.22 GiB (10.3%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVLQ512HALU-00000 size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: FXV7101Q temp: 36.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: USB 3.2Gen1 size: 460.27 GiB block-size:
    physical: 512 B logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
    tech: N/A serial: <filter> fw-rev: 1.00
Partition:
  ID-1: / raw-size: 146.49 GiB size: 146.49 GiB (100.00%) used: 8.13 GiB (5.6%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%) used: 576 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 321.45 GiB size: 321.45 GiB (100.00%) used: 12.17 GiB (3.8%) fs: btrfs
    dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-4: /var/log raw-size: 146.49 GiB size: 146.49 GiB (100.00%) used: 8.13 GiB (5.6%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 146.49 GiB size: 146.49 GiB (100.00%) used: 8.13 GiB (5.6%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3
    maj-min: 259:3
  ID-2: swap-2 type: zram size: 7.15 GiB used: 18.5 MiB (0.3%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A gpu: amdgpu temp: 40.0 C
  Fan Speeds (rpm): cpu: 2300
Info:
  Processes: 387 Uptime: 6h 39m wakeups: 2 Memory: total: 8 GiB note: est. available: 7.15 GiB
  used: 3.99 GiB (55.9%) Init: systemd v: 254 default: graphical tool: systemctl Compilers:
  gcc: 13.2.1 Packages: pm: pacman pkgs: 1371 libs: 403 tools: pamac,paru Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.31
Garuda (2.6.17-1):
  System install date:     2023-10-26
  Last full system update: 2023-11-03
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager mkinitcpio
  Windows dual boot:       No/Undetected
  Failed units:            cpupower.service 
```
2

I found out what was going on - the newer version never got deployed due to a mismatch of version in the PKGBUILD and tag (1.5.3 vs v1.5.3). Fixed that.

We have some interesting changes of the packaging repo infrastructure for the garuda repo (not chaotic-aur) coming up tomorrow - no actual changes to packages but how they are managed and deployed… :slight_smile:

3 Likes
3

:face_with_peeking_eye: Good grief… That was me again! :face_with_head_bandage:

In my defense, the Git manpages have the “v” in the examples so I thought that was the “correct” way. :sweat_smile:

3 Likes
4

You are forgiven BluishHumility, the problem is now solved :relieved:

I’m curious…

:thinking:

1 Like
5

The short explanation is there is a new repo on GitLab that holds all the PKGBUILDs for Garuda Linux:

image
image1273×1083 170 KB

Where before each PKGBUILD would be found in whatever repo it was related to, now they are in a separate repo that ties in with some automation tools. The automation helps take care of certain tasks that used to have to be done manually, like bumping versioning or kicking off a build routine when needed.

Basically @dr460nf1r3 making us all re-learn how to push commits because he’s gotta be extra. :unamused:

:joy: Just kidding! There is some new syntax to use when pushing commits (i.e., Conventional Commits) but it’s a very small ask for the rest of us. He did all the heavy lifting on this one single-handedly! In the long run, making changes to the project should be simpler and faster now.

I’m not sure if there will be an announcement for this one because it’s not a directly user-facing change (more of an infrastructure change), but @dr460nf1r3 deserves a big round of applause for managing to pull the whole thing off! :tada: :clinking_glasses: :partying_face:

And thanks for answering 1,000 questions in the team chat while the rest of us try to figure out how to use the new tooling! :face_with_hand_over_mouth:

5 Likes
6

Hahaha, good one :joy:

I certainly planned to write down a quick explanation of the whole reasoning behind the changes, since people seemed to appreciate such insights :slight_smile: This will happen tomorrow, as I’m done for today :yum:

4 Likes
7

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.