When the following starndard debian sources in apt are activated, then “apt search jq” is successful.
“sources.list”
deb http://deb.debian.org/debian/ bookworm main non-free-firmware
deb-src http://deb.debian.org/debian/ bookworm main non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main non-free-firmware
deb-src http://security.debian.org/debian-security bookworm-security main non-free-firmware
→ adm_senftleben@srv185:/etc/apt$ sudo apt show jq Package: jq Version: 1.6-2.1 Priority: optional Section: utils Maintainer: ChangZhuo Chen (陳昌倬) <czchen@debian.org> Installed-Size: 113 kB Depends: libjq1 (= 1.6-2.1), libc6 (>= 2.4) Homepage: https://github.com/stedolan/jq Tag: implemented-in::c, role::program, works-with-format::json Download-Size: 64,9 kB APT-Sources: http://deb.debian.org/debian bookworm/main amd64 Packages Description: Leichtgewichtiger und flexibler JSON-Prozessor für die Kommandozeile
But when only using the SuSE managed apt sources list, the package is not found:
adm_senftleben@srv185:/etc/apt$ cat sources.list.d/susemanager\:channels.list
# Channels managed by SUSE Manager
# Do not edit this file, changes will be overwritten
#
deb [trusted=yes] https://srv182.linux.lab:443/rhn/manager/download debian-12-pool-amd64-uyuni/
deb [trusted=yes] https://srv182.linux.lab:443/rhn/manager/download debian-12-amd64-uyuni-client/
deb [trusted=yes] https://srv182.linux.lab:443/rhn/manager/download debian-12-amd64-main-updates-uyuni/
deb [trusted=yes] https://srv182.linux.lab:443/rhn/manager/download debian-12-amd64-main-security-uyuni/
Why?
What does apt policy jq
report for each sources.list
file?
adm_senftleben@srv184:~$ apt policy jq
jq:
Installiert: (keine)
Installationskandidat: (keine)
Versionstabelle:
adm_senftleben@srv184:~$ sudo apt search jq
[sudo] Passwort für adm_senftleben:
Sortierung… Fertig
Volltextsuche… Fertig
adm_senftleben@srv184:~$ hostnamectl
Static hostname: srv184.linux.lab
Icon name: computer-vm
Chassis: vm 🖴
Machine ID: 55aa505999fe4657bceacc899896cd22
Boot ID: 80712a0bf50e4286bd9d420b6669d4ef
Virtualization: vmware
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.1.0-30-amd64
Architecture: x86-64
Hardware Vendor: VMware, Inc.
Hardware Model: VMware Virtual Platform
Firmware Version: 6.00
I installed a test Debian 12 system using defaults and it reports
simon@debian12:~$ apt policy jq
jq:
Installed: (none)
Candidate: 1.6-2.1
Version table:
1.6-2.1 500
500 http://mirrorservice.org/sites/ftp.debian.org/debian bookworm/main amd64 Packages
Given the base and child channel labels in your original post are you perhaps using Uyuni rather than SUSE Multi-Linux Manager (previously known as SUSE Manager)?
I’m currently adding Debian 12 to my test Uyuni system but I should note that community support for Uyuni is available via GitHub Discussions at https://github.com/uyuni-project/uyuni/discussions .
Hello @smflood ,
I am using SMLM 5.02.
Thank you for the hint on the github discussions!
Thanks for confirming that you’re using SMLM - it doesn’t help that the Uyuni and SUSE Manager documentation are different, at least for Debian 12.
Anyway I added Debian 12 to my test Uyuni system and do see jq 1.6-2.1 so I’d expect the same with SMLM.