Page: Previous  1, 2, 3  Next

damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 885
Reply Quote
Hi marco,

I just looked at the script and realized I moved installing of dependencies to after usage of curl after refactoring. Now the script installs curl if not there before proceeding to get gpg keyring.

Can you try again?
Back to top
drmacro
Status: Curious
Joined: 26 Jan 2020
Posts: 6
Reply Quote
I finally removed the ppa from the source list file and re-ran the script and it worked.

But, after the install, I noticed only the liquorix kernel showed in the boot menu...
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 885
Reply Quote
Maybe you uninstalled your Debian stock kernel? Also, which PPA were you using? The launchpad PPA only contains builds specifically built for each version of Ubuntu supported. Debian doesn't have a concept of a PPA so that's why there's a separate Debian prerequisite script.

You can always rerun update-grub to repopulate your grub menu, but I think that's run automatically with every kernel update. It's more likely you accidentally uninstalled the stock kernel for your distro.
Back to top
drmacro
Status: Curious
Joined: 26 Jan 2020
Posts: 6
Reply Quote
Hmm...I don't know what I would have done that would have removed any kernel.
Back to top
Mono
Status: Contributor
Joined: 21 Jun 2012
Posts: 101
Reply Quote
I am having the same problem.

:: Code ::
~$ curl https://liquorix.net/linux-liquorix.pub | sudo apt-key add -
[sudo] password for keantoken:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3171  100  3171    0     0  17715      0 --:--:-- --:--:-- --:--:-- 17715

Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK


This command required me to type in my password, but there was no terminal line telling me to do that. It simply hangs forever waiting for a password until I ctrl+c at which point it exits and says "sudo: a password is required".

Apt says curl is the latest version.

:: Code ::
E: The repository 'http://liquorix.net/debian trusty Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


:: Code ::
~$ inxi -v3
System:    Host: ronin Kernel: 5.9.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.14.3
           Distro: Debian GNU/Linux bullseye/sid
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX B350-F GAMING v: Rev X.0x serial: <superuser required>
           UEFI [Legacy]: American Megatrends v: 5220 date: 09/12/2019
CPU:       Info: Quad Core model: AMD Ryzen 5 1500X bits: 64 type: MT MCP arch: Zen rev: 1 L2 cache: 2 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 61476
           Speed: 1375 MHz min/max: 1550/3850 MHz boost: disabled Core speeds (MHz): 1: 1375 2: 1375 3: 1375 4: 1375 5: 1375
           6: 1375 7: 1375 8: 1375
Graphics:  Device-1: NVIDIA GM206 [GeForce GTX 950] vendor: eVga.com. driver: nouveau v: kernel bus ID: 08:00.0
           Display: x11 server: X.Org 1.20.10 driver: nouveau resolution: 1280x960~60Hz
           OpenGL: renderer: NV126 v: 4.3 Mesa 20.2.6 direct render: Yes
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: e000 bus ID: 03:00.0
           IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: 2c:fd:a1:c1:07:44
Drives:    Local Storage: total: 344.68 GiB used: 176.3 GiB (51.2%)
Info:      Processes: 312 Uptime: 39m Memory: 23.49 GiB used: 6.5 GiB (27.7%) Init: systemd runlevel: 5 Compilers: gcc: 10.2.1
           Packages: 4023 Shell: Bash v: 5.1.0 inxi: 3.2.01

Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 885
Reply Quote
Your issue appears to be that your liquorix.list has "trusty" as the code name. Can you show the output of inxi -r? The setup script on the liquorix.net homepage searches your repos for the most common codename and uses that for liquorix. You probably have more instances of Ubuntu "trusty" than whichever Debian repo you intended to use.

But in the meantime, you can change the code name to whatever your distro is supposed to be. From your current output, that can be bullseye (testing), or sid (unstable).
Back to top
Mono
Status: Contributor
Joined: 21 Jun 2012
Posts: 101
Reply Quote
Thanks. It looks like it's the KXStudio stuff that borked everything.

EDIT: Yes, it worked.

:: Code ::
~$ inxi -r
Repos:
  Active apt repos in: /etc/apt/sources.list
  1: deb http://httpredir.debian.org/debian/ unstable non-free contrib main
  2: deb-src http://httpredir.debian.org/debian/ unstable non-free contrib main
  3: deb https://dl.winehq.org/wine-builds/debian/ sid main
  4: deb http://deb.debian.org/debian/ sid contrib non-free main
  Active apt repos in: /etc/apt/sources.list.d/java-8-debian.list
  1: deb http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main
  2: deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main
  Active apt repos in: /etc/apt/sources.list.d/jitsi-stable.list
  1: deb https://download.jitsi.org/ stable/
  Active apt repos in: /etc/apt/sources.list.d/jitsi-unstable.list
  1: deb https://download.jitsi.org/ unstable/
  Active apt repos in: /etc/apt/sources.list.d/kxstudio-debian.gcc5.list
  1: deb http://ppa.launchpad.net/kxstudio-debian/gcc5/ubuntu/ wily main
  2: deb http://ppa.launchpad.net/kxstudio-debian/gcc5/ubuntu/ xenial main
  3: deb http://ppa.launchpad.net/kxstudio-debian/gcc5-deps/ubuntu/ xenial main
  Active apt repos in: /etc/apt/sources.list.d/kxstudio-debian.gcc5plus.list
  1: deb http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu/ xenial main
  Active apt repos in: /etc/apt/sources.list.d/kxstudio-debian.list
  1: deb [arch=amd64,i386] http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu/ lucid main
  2: deb [arch=amd64,i386] http://ppa.launchpad.net/kxstudio-debian/music/ubuntu/ lucid main
  3: deb [arch=amd64,i386] http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu/ lucid main
  4: deb [arch=amd64,i386] http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu/ lucid main
  5: deb [arch=amd64,i386] http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu/ lucid main
  Active apt repos in: /etc/apt/sources.list.d/kxstudio-debian.new.list
  1: deb http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu/ trusty main
  2: deb http://ppa.launchpad.net/kxstudio-debian/music/ubuntu/ trusty main
  3: deb http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu/ trusty main
  4: deb http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu/ trusty main
  5: deb http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu/ trusty main
  Active apt repos in: /etc/apt/sources.list.d/kxstudio-free.gcc5.list
  1: deb [arch=amd64,i386] http://kxstudio.linuxaudio.org/repo/ gcc5 free
  Active apt repos in: /etc/apt/sources.list.d/kxstudio-free.list
  1: deb [arch=amd64,i386] http://kxstudio.linuxaudio.org/repo/ stable free
  Active apt repos in: /etc/apt/sources.list.d/liquorix.list
  1: deb http://liquorix.net/debian trusty main
  2: deb-src http://liquorix.net/debian trusty main
  Active apt repos in: /etc/apt/sources.list.d/lutris.list
  1: deb http://download.opensuse.org/repositories/home:/strycore/Debian_10/ ./
  No active apt repos in: /etc/apt/sources.list.d/nilarimogard-ubuntu-webupd8-cosmic.list
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list
  1: deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main
  No active apt repos in: /etc/apt/sources.list.d/spvkgn-ubuntu-deadbeef-dev-focal.list
  Active apt repos in: /etc/apt/sources.list.d/t-5.eu.list
  1: deb https://t-5.eu/debian/ repo main

Back to top
sunrat
Status: New User - Welcome
Joined: 19 Feb 2021
Posts: 3
Location: Melbourne AU
Reply Quote
I just ran into the same issue setting up Debian Bullseye and have seen a few posts in other forums for the same. For some reason the script parses the file /etc/apt/sources.list.d/kxstudio-debian-ppas.list which although the correct file for Debian, uses the Ubuntu release name. It should actually be parsing /etc/apt/sources.list.

:: Code ::
$ find /etc/apt -type f -name '*.list' | \
    xargs grep -E '^deb' | awk '{print $3}' | \
    grep -Eo '^[a-z]+' | sort | uniq -c | sort -n | tail -n1 | \
    grep -Eo '[a-z]+$'
bionic

You could limit find to one directory depth

:: Code ::
find /etc/apt  -maxdepth 1 -type f -name '*.list' |     xargs grep -E '^deb' | awk '{print $3}' |     grep -Eo '^[a-z]+' | sort | uniq -c | sort -n | tail -n1 |     grep -Eo '[a-z]+$'
bullseye

I suggest alternatively parsing /etc/os-release where the actual release version should always be correct.

:: Code ::
awk 'NR == 1' /etc/os-release | awk '{print $3}' | sed 's/\/.*//g'
bullseye


Thanks for making Liquorix kernels btw. I've used them happily for audio production for several years but first time I've posted here.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 885
Reply Quote
Hi sunrat, glad Liquorix has worked well for you!

You're totally right that the /etc/apt/sources.list file is better to query from than descending into /etc/apt/sources.list.d. Because Debian has no concept of a PPA, the more PPAs and custom repositories added to a Debian system, the lower the probability add-liquorix-repo.sh would return the true underlying operating system. So with that in mind, I added the -maxdepth 1 as you recommended (gives us flexibility to modify again if there's another quirk).

As for /etc/os-release, I've personally never had good luck using that to identify the true underlying operating system. Especially for Debian users with long lived systems, as the system ages since the original installation, the less likely the /etc/os-release file is correct. Spins of Debian (and Ubuntu), also like to modify this file and remove information about the underlying OS. What is always correct though is the primary repositories that make up the majority of the system.

Maybe with this in mind I'll redo the detection using that logic. A good example is running apt-cache policy libc6. As long as there's an associated repository, you can determine the real operating system that probably makes up the system.

But that's for another time, lets see if restricting find to simply /etc/apt's folder is good enough for everyone.
Back to top
sunrat
Status: New User - Welcome
Joined: 19 Feb 2021
Posts: 3
Location: Melbourne AU
Reply Quote
I'm sure there will be other quirks eg. my daily system is siduction which has Debian repos in /etc/apt/sources.list.d/debian.list so the script would fail here with -maxdepth 1. :( siduction kernel config is probably closer to Liquorix than Debian so I wouldn't need Liquorix on that anyway. Works for vanilla Debian though. I thought the os-release file would be widely standard but have no idea what Ubuntu does as I never use it.
At least we worked out why it returns "bionic" when KXStudio repos are active.
Back to top
Display posts from previous:   
Page: Previous  1, 2, 3  Next
All times are GMT - 8 Hours