Updating repository Error [Solved]

[bidral]

Hello, I am facing this error message for several hours today. So I can not update my system to 23.2.

Code: Select all

E: The repository 'http://mx-pkg.mirror.net.in/MX-Linux/mx/repo bookworm Release' does not have a Release file.
W: Updating from such a repository can't be done securely, and is therefore disabled by default.
W: See apt-secure(8) manpage for repository creation and user configuration details.

How could I fix this?
I am on MX Linux KDE 23.1

Thanks a lot

[Eadwine Rose]

Please share your full Quick System Info, found in the menu. Copy for forum, paste in a reply.. thanks.

[bidral]

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 info: plank wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.1_KDE_x64
    Libretto October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: LENOVO product: 82VG v: IdeaPad 1 15AMN7 serial: <superuser required>
    Chassis: type: 10 v: IdeaPad 1 15AMN7 serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: No DPK serial: <superuser required> UEFI: LENOVO v: KSCN28WW
    date: 09/01/2023
Battery:
  ID-1: BAT1 charge: 42.8 Wh (100.0%) condition: 42.8/42.0 Wh (102.0%) volts: 12.9 min: 11.4
    model: LGES L21L3PF0 type: Li-poly serial: <filter> status: full cycles: 8
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter>
    charge: 50% (should be ignored) rechargeable: yes status: N/A
CPU:
  Info: model: AMD Ryzen 3 7320U 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: 0xA0 (160) stepping: 0 microcode: 0x8A00008
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 2246 high: 3893 min/max: 900/6375 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1218 2: 1730 3: 1488 4: 1100 5: 1935 6: 3893
    7: 3885 8: 2725 bogomips: 38327
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection
  Type: spec_rstack_overflow mitigation: safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: always-on, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Mendocino vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: eDP-1
    empty: DP-1,DP-2,HDMI-A-1 bus-ID: 04:00.0 chip-ID: 1002:1506 class-ID: 0300 temp: 39.0 C
  Device-2: Syntek Integrated Camera type: USB driver: uvcvideo bus-ID: 5-1:2 chip-ID: 174f:2465
    class-ID: fe01 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP model: BOE Display 0x0aed built: 2018 res: 1920x1080 hz: 60
    dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon Graphics (raphael_mendocino LLVM
    15.0.6 DRM 3.49 6.1.0-13-amd64) direct-render: Yes
Audio:
  Device-1: AMD Rembrandt Radeon High Definition Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 04:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: snd_pci_acp6x v: kernel
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 04:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 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: Realtek vendor: Lenovo driver: rtw89_8852be v: N/A modules: wl,rtw_8852be pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:b852 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-2:2 chip-ID: 0bda:4853
    class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 3 state: down bt-service: N/A rfk-block: hardware: no
    software: yes address: <filter>
  Info: acl-mtu: 1021:6 sco-mtu: 255:12 link-policy: rswitch hold sniff park
    link-mode: peripheral accept
Drives:
  Local Storage: total: 476.94 GiB used: 125.6 GiB (26.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: solidgm model: SSDPFINW512GZL size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: C02C temp: 27.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 48.24 GiB size: 47.18 GiB (97.81%) used: 8.38 GiB (17.8%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 16.3 MiB (5.4%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 191.29 GiB size: 187.22 GiB (97.88%) used: 13.65 GiB (7.3%) fs: ext4
    dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 3.72 GiB used: 4.2 MiB (0.1%) priority: -2
    dev: /dev/nvme0n1p5 maj-min: 259:5
Sensors:
  System Temperatures: cpu: 43.8 C mobo: N/A gpu: amdgpu temp: 38.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2447 libs: 1350 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/librewolf.list
    1: deb [arch=amd64] http://deb.librewolf.net bookworm main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mx-pkg.mirror.net.in/MX-Linux/mx/repo/ bookworm main non-free
    2: deb http://mx-pkg.mirror.net.in/MX-Linux/mx/repo/ bookworm ahs
Info:
  Processes: 267 Uptime: 46m wakeups: 10 Memory: 5.52 GiB used: 3.37 GiB (61.0%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[j2mcgreg]

You can use Repo Manager in MX Tools to switch your main repository to one of:
-- Alblasserdam, The Netherlands

-- Milan, Italy

--Salt Lake City, Utah, USA

-- Los Angeles, California, USA

All of these are owned / operated by the MX Team. Make the switch, log out / in or reboot and then try your updates again.

[bidral]

Thanks a lot. It's working.

[hebelwirkung]

You can use Repo Manager in MX Tools to switch your main repository to one of:
-- Alblasserdam, The Netherlands

-- Milan, Italy

--Salt Lake City, Utah, USA

-- Los Angeles, California, USA

All of these are owned / operated by the MX Team. Make the switch, log out / in or reboot and then try your updates again.

Just to say that in my experience, there's no need for logging out or rebooting after a change of repositories. A simple sudo apt update refreshes the list and - if the repo chosen is working - offers all available updates.

[Eadwine Rose]

Yep.. no need to logout or things like that. The change is almost immediate.

[j2mcgreg]

Yep.. no need to logout or things like that. The change is almost immediate.

Then why is a user presented with this:

Your new selection will take effect the next time sources are updated.

after clicking on OK to approve the repo change? That seems to mean that some user action is needed (like a log out / in) to complete the process.

[Eadwine Rose]

"next time sources are updated" to me always meant you need to run the updater thingie again. After a little bit, won't work right off. I get presented with that lock thing then, so..

But I have never logged out or rebooted for this.

[DukeComposed]

Then why is a user presented with this:

Your new selection will take effect the next time sources are updated.

after clicking on OK to approve the repo change? That seems to mean that some user action is needed (like a log out / in) to complete the process.

I used to have to edit my apt sources constantly when I used Linux Mint because one mirror or another would be offline or inaccessible. Typically after editing the list of sources, I needed to run "apt-get update" again in order for it to pick up the new endpoint. Otherwise, it would keep using the old, cached location.