You are not logged in.

#1 2021-03-08 04:22:20

horo
Member
Registered: 2016-03-13
Posts: 47

Apt-get not able to locate packages

Setting up a new laptop and ran into issues getting Lithium on. I had to use a minimal Arch install to set up the ESP and get GRUB loaded, since the Lithium installer couldn't get that to work, or see my wifi hardware

I eventually managed to get things going, add backports to the source.list and bunesn.list files, used apt-get to install ver. 5.10 of the kernel and went and dled a more upto date version of my cards firmware.

Now the problems.

1) BL-Welcome script does not run and throws an error-

lboo@newbie:~$ bl-welcome 
Error: This script should be run only on Debian Buster.

2) some packages work, like when i got the kernel, most others do not-

lboo@newbie:~$ sudo apt-get install mpv
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mpv : Depends: libssh-4 (>= 0.8.0) but it is not installable
       Recommends: mesa-vdpau-drivers but it is not installable or
                   nvidia-vdpau-driver but it is not going to be installed or
                   nvidia-driver-binary but it is not installable or
                   nvidia-current but it is not installable or
                   vdpau-driver
E: Unable to correct problems, you have held broken packages.

and since i know someone will ask-

lboo@newbie:~$ sudo apt-get update
Hit:1 https://deb.debian.org/debian-security buster/updates InRelease
Get:2 https://deb.debian.org/debian buster-backports InRelease [46.7 kB]
Hit:3 http://eu.pkg.bunsenlabs.org/debian lithium InRelease                    
Hit:4 http://eu.pkg.bunsenlabs.org/debian buster-backports InRelease
Fetched 46.7 kB in 1s (33.5 kB/s)
Reading package lists... Done

even tried commenting out the backports but that changed nothing.

Offline

#2 2021-03-08 04:33:55

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 7,851
Website

Re: Apt-get not able to locate packages

horo wrote:

I had to use a minimal Arch install to set up the ESP and get GRUB loaded...

1) BL-Welcome script does not run and throws an error-

lboo@newbie:~$ bl-welcome 
Error: This script should be run only on Debian Buster.

So, is this an Arch system or a Debian system?
BunsenLabs is only for Debian.


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#3 2021-03-08 05:23:12

horo
Member
Registered: 2016-03-13
Posts: 47

Re: Apt-get not able to locate packages

Arch is on a small separate partition to manage the ESP and boot loader.
Lithium was installed using the live usb, but a minimal install since the machine did not have internet access at the time.
At boot, GRUB has multiple entries to switch between Arch, Lithium with default 4.19 kernel and Lithium 5.10 kernel

lboo@newbie:~$ uname -a
Linux newbie 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64 GNU/Linux
lboo@newbie:~$ cat /etc/os-release 
ANSI_COLOR="0;34"
BUG_REPORT_URL="https://forums.bunsenlabs.org/viewforum.php?id=14"
HOME_URL="https://www.bunsenlabs.org"
ID="bunsenlabs"
ID_LIKE="debian"
NAME="BunsenLabs GNU/Linux"
PRETTY_NAME="BunsenLabs GNU/Linux 10.5 (Lithium)"
PRIVACY_POLICY_URL="https://www.bunsenlabs.org/legal.html"
SUPPORT_URL="https://forums.bunsenlabs.org"
VERSION="10.5 (Lithium)"
VERSION_ID="10.5"

edit:
/dev/mmcblk0p3 is the Arch partition it is not currently mounted though I wounder if things are trying to point to it for some reason.

lboo@newbie:~$ lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0      179:0    0 58.2G  0 disk 
├─mmcblk0p1  179:1    0  512M  0 part /boot/efi
├─mmcblk0p2  179:2    0    1G  0 part [SWAP]
├─mmcblk0p3  179:3    0    5G  0 part 
├─mmcblk0p4  179:4    0   20G  0 part /
└─mmcblk0p5  179:5    0 31.8G  0 part /home
mmcblk0boot0 179:256  0    4M  1 disk 
mmcblk0boot1 179:512  0    4M  1 disk 

Last edited by horo (2021-03-08 05:27:47)

Offline

#4 2021-03-08 06:09:31

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 7,851
Website

Re: Apt-get not able to locate packages

OK I think this is because you don't have all the Debian repositories enabled in your apt sources. This happens when an install is done without network access because the Debian Installer needs it to set up apt.

Easily fixed though, check the reference: https://forums.bunsenlabs.org/viewtopic.php?id=6915 adjust your sources and redo

sudo apt update
sudo apt upgrade

If your troubles persist please post again. smile


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#5 2021-03-08 06:44:44

horo
Member
Registered: 2016-03-13
Posts: 47

Re: Apt-get not able to locate packages

Partial success.
I edited my source files as per link and updated and upgraded, then reboot
Bl-Welcome kicked on when I logged in and was doing fine till it actually ran apt-get

 -----------------------------[ page 15 of 16 ]------------------------------

  INSTALL PACKAGES
  ----------------
  
  This script will now execute some deferred actions.
  
  These packages will be installed:
   bunsen-meta-bluetooth
   bunsen-meta-java
   bunsen-meta-vcs
  
  
  Would you like to perform these actions? [Y/n] 

  Updating apt data...
Hit:1 https://deb.debian.org/debian buster InRelease
Hit:2 https://deb.debian.org/debian-security buster/updates InRelease
Hit:4 https://deb.debian.org/debian buster-updates InRelease
Hit:5 https://deb.debian.org/debian buster-backports InRelease
Hit:3 http://eu.pkg.bunsenlabs.org/debian lithium InRelease
Hit:6 http://eu.pkg.bunsenlabs.org/debian buster-backports InRelease
Reading package lists...
  Finished update
  Installing packages...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 bunsen-meta-bluetooth : Depends: bluez but it is not going to be installed
                         Depends: blueman but it is not going to be installed
                         Depends: pulseaudio-module-bluetooth but it is not going to be installed
  
  There were problems installing bunsen-meta-bluetooth bunsen-meta-java 
  bunsen-meta-vcs
  
  Press "d" for details (q to quit) d


ERROR MESSAGE:
E: Unable to correct problems, you have held broken packages.
------------------------------------
  
  Would you like to quit now, or continue anyway?
  (Be careful!)
  Enter "q" to quit, "c" to continue:
  

edit:
I did have success installing mpv which had previously failed to load. Could I be missing some other repos?

lboo@newbie:~$ ls /etc/apt/sources.list.d/
bunsen-buster-backports.list  bunsen.list  debian-buster-backports.list
lboo@newbie:~$ cat /etc/apt/sources.list
# 

# deb cdrom:[Debian GNU/Linux 10 _Lithium_ - Snapshot amd64 LIVE/INSTALL Binary 20210130-13:51]/ buster contrib main non-free

#deb cdrom:[Debian GNU/Linux 10 _Lithium_ - Snapshot amd64 LIVE/INSTALL Binary 20210130-13:51]/ buster contrib main non-free

deb https://deb.debian.org/debian buster main non-free contrib
# deb-src https://deb.debian.org/debian buster main non-free contrib

## Debian security updates
deb https://deb.debian.org/debian-security buster/updates main contrib non-free

# buster-updates, previously known as 'volatile'
deb https://deb.debian.org/debian buster-updates main contrib non-free
# deb-src https://deb.debian.org/debian buster-updates main contrib non-free
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
lboo@newbie:~$ cat /etc/apt/sources.list.d/*
deb https://pkg.bunsenlabs.org/debian buster-backports main
deb http://pkg.bunsenlabs.org/debian lithium main
#deb http://pkg.bunsenlabs.org/debian buster-backports main
# Debian backports
deb https://deb.debian.org/debian buster-backports main contrib non-free
lboo@newbie:~$ 

Last edited by horo (2021-03-08 06:58:11)

Offline

#6 2021-03-08 08:28:00

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 7,851
Website

Re: Apt-get not able to locate packages

You seem to have the correct repositories enabled.

Let's take 'bluez' - could you post the output of 'apt-cache policy bluez'?
And also 'aptitude why-not bluez'?

Maybe the other two packages 'blueman' 'pulseaudio-module-bluetooth' too?

And one more: 'apt-cache policy' to see all the enabled repos.


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#7 2021-03-08 15:24:11

horo
Member
Registered: 2016-03-13
Posts: 47

Re: Apt-get not able to locate packages

here are the out puts-

lboo@newbie:~$ apt-cache policy bluez
bluez:
  Installed: (none)
  Candidate: 5.50-1.2~deb10u1
  Version table:
     5.54-1~bpo10+1 100
        100 https://deb.debian.org/debian buster-backports/main amd64 Packages
     5.50-1.2~deb10u1 500
        500 https://deb.debian.org/debian buster/main amd64 Packages
        500 https://deb.debian.org/debian-security buster/updates/main amd64 Packages

lboo@newbie:~$ aptitude why-not bluez
Not currently installed
The candidate version 5.50-1.2~deb10u1 has priority optional
No dependencies require to remove bluez

lboo@newbie:~$ apt-cache policy blueman
blueman:
  Installed: (none)
  Candidate: 2.0.8-1+deb10u1
  Version table:
     2.0.8-1+deb10u1 500
        500 https://deb.debian.org/debian buster/main amd64 Packages
        500 https://deb.debian.org/debian-security buster/updates/main amd64 Packages

lboo@newbie:~$ aptitude why-not blueman
Not currently installed
The candidate version 2.0.8-1+deb10u1 has priority optional
No dependencies require to remove blueman

lboo@newbie:~$ apt-cache policy pulseaudio-module-bluetooth 
pulseaudio-module-bluetooth:
  Installed: (none)
  Candidate: 12.2-4+deb10u1
  Version table:
     13.0-3~bpo10+1 100
        100 https://deb.debian.org/debian buster-backports/main amd64 Packages
     12.2-4+deb10u1 500
        500 https://deb.debian.org/debian buster/main amd64 Packages

lboo@newbie:~$ aptitude why-not pulseaudio-module-bluetooth 
Not currently installed
The candidate version 12.2-4+deb10u1 has priority optional
No dependencies require to remove pulseaudio-module-bluetooth

lboo@newbie:~$ apt-cache policy 
Package files:
 100 /var/lib/dpkg/status
     release a=now
 100 https://deb.debian.org/debian buster-backports/non-free amd64 Packages
     release o=Debian Backports,a=buster-backports,n=buster-backports,l=Debian Backports,c=non-free,b=amd64
     origin deb.debian.org
 100 https://deb.debian.org/debian buster-backports/contrib amd64 Packages
     release o=Debian Backports,a=buster-backports,n=buster-backports,l=Debian Backports,c=contrib,b=amd64
     origin deb.debian.org
 100 https://deb.debian.org/debian buster-backports/main amd64 Packages
     release o=Debian Backports,a=buster-backports,n=buster-backports,l=Debian Backports,c=main,b=amd64
     origin deb.debian.org
 500 http://pkg.bunsenlabs.org/debian lithium/main amd64 Packages
     release o=bunsenlabs,a=lithium,n=lithium,l=bunsenlabs,c=main,b=amd64
     origin pkg.bunsenlabs.org
 100 https://pkg.bunsenlabs.org/debian buster-backports/main amd64 Packages
     release o=bunsenlabs,a=buster-backports,n=buster-backports,l=bunsenlabs,c=main,b=amd64
     origin pkg.bunsenlabs.org
 500 https://deb.debian.org/debian buster-updates/non-free amd64 Packages
     release o=Debian,a=stable-updates,n=buster-updates,l=Debian,c=non-free,b=amd64
     origin deb.debian.org
 500 https://deb.debian.org/debian buster-updates/main amd64 Packages
     release o=Debian,a=stable-updates,n=buster-updates,l=Debian,c=main,b=amd64
     origin deb.debian.org
 500 https://deb.debian.org/debian-security buster/updates/non-free amd64 Packages
     release v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=non-free,b=amd64
     origin deb.debian.org
 500 https://deb.debian.org/debian-security buster/updates/main amd64 Packages
     release v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=main,b=amd64
     origin deb.debian.org
 500 https://deb.debian.org/debian buster/contrib amd64 Packages
     release v=10.8,o=Debian,a=stable,n=buster,l=Debian,c=contrib,b=amd64
     origin deb.debian.org
 500 https://deb.debian.org/debian buster/non-free amd64 Packages
     release v=10.8,o=Debian,a=stable,n=buster,l=Debian,c=non-free,b=amd64
     origin deb.debian.org
 500 https://deb.debian.org/debian buster/main amd64 Packages
     release v=10.8,o=Debian,a=stable,n=buster,l=Debian,c=main,b=amd64
     origin deb.debian.org
Pinned packages:
lboo@newbie:~$ 

Offline

#8 2021-03-10 04:51:54

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 7,851
Website

Re: Apt-get not able to locate packages

Thanks!
I can't see anything wrong in that - your 'apt-cache policy' looks the same as mine.

The only tentative idea I have left is that one of the dependencies of the packages about to be installed has a higher version number than the standard Debian repository, and Debian can't provide a compatible  package to go with bluez etc. Something that came in with the Arch install? It might be necessary to uninstall something and reinstall it from the Debian repo, but before we go that far, let's try:

'bl-welcome'
once more, to make sure the issue hasn't fixed itself.
If that still fails at the installing bunsen-meta-* stage, then:

sudo apt install bunsen-meta-bluetooth

If that works, then there might be something wrong with bunsen-welcome. neutral
If it fails, try:

sudo apt-get -o Debug::pkgProblemResolver=yes install bunsen-meta-bluetooth

and hope that there's something useful in the terminal messages.

Or, try the same command replacing bunsen-meta-bluetooth with one of the problem packages: bluez, blueman or pulseaudio-module-bluetooth

Related topic, with some ways of getting more info:
https://unix.stackexchange.com/question … ency-issue


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#9 2021-03-10 16:29:46

horo
Member
Registered: 2016-03-13
Posts: 47

Re: Apt-get not able to locate packages

Here is the output from the suggested actions-

 -----------------------------[ page 11 of 15 ]------------------------------

  INSTALL PACKAGES
  ----------------
  
  This script will now execute some deferred actions.
  
  These packages will be installed:
   bunsen-meta-bluetooth
  
  
  Would you like to perform these actions? [Y/n] 

  Updating apt data...
Hit:1 https://deb.debian.org/debian buster InRelease
Hit:3 https://deb.debian.org/debian-security buster/updates InRelease
Hit:4 https://deb.debian.org/debian buster-updates InRelease
Hit:5 https://deb.debian.org/debian buster-backports InRelease
Hit:2 http://eu.pkg.bunsenlabs.org/debian lithium InRelease
Hit:6 https://eu.pkg.bunsenlabs.org/debian buster-backports InRelease
Reading package lists...
  Finished update
  Installing packages...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 bunsen-meta-bluetooth : Depends: bluez but it is not going to be installed
                         Depends: blueman but it is not going to be installed
                         Depends: pulseaudio-module-bluetooth but it is not going to be installed
  
  There were problems installing bunsen-meta-bluetooth
  
  Press "d" for details (q to quit) qlboo@newbie:~$ sudo apt install bunsen-meta-bluetooth 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 bunsen-meta-bluetooth : Depends: bluez but it is not going to be installed
                         Depends: blueman but it is not going to be installed
                         Depends: pulseaudio-module-bluetooth but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
lboo@newbie:~$ sudo apt-get -o Debug::pkgProblemResolver=yes install bunsen-meta-bluetooth 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 2
Starting 2 pkgProblemResolver with broken count: 2
Investigating (0) bunsen-meta-bluetooth:amd64 < none -> 10.2.1-1 @un puN Ib >
Broken bunsen-meta-bluetooth:amd64 Depends on pulseaudio-module-bluetooth:amd64 < none | 12.2-4+deb10u1 @un uH >
  Considering pulseaudio-module-bluetooth:amd64 2 as a solution to bunsen-meta-bluetooth:amd64 9999
    Reinst Failed early because of libpulse0:amd64
  Considering pulseaudio-module-bluetooth:amd64 2 as a solution to bunsen-meta-bluetooth:amd64 9999
Investigating (0) bluez:amd64 < none -> 5.50-1.2~deb10u1 @un uN Ib >
Broken bluez:amd64 Depends on libdw1:amd64 < none | 0.176-1.1 @un uH > (>= 0.127)
  Considering libdw1:amd64 0 as a solution to bluez:amd64 1
  Holding Back bluez:amd64 rather than change libdw1:amd64
Investigating (0) blueman:amd64 < none -> 2.0.8-1+deb10u1 @un uN Ib >
Broken blueman:amd64 Depends on bluez:amd64 < none | 5.50-1.2~deb10u1 @un uH > (>= 4.61)
  Considering bluez:amd64 1 as a solution to blueman:amd64 0
  Holding Back blueman:amd64 rather than change bluez:amd64
Investigating (1) bunsen-meta-bluetooth:amd64 < none -> 10.2.1-1 @un puN Ib >
Broken bunsen-meta-bluetooth:amd64 Depends on bluez:amd64 < none | 5.50-1.2~deb10u1 @un uH >
  Considering bluez:amd64 1 as a solution to bunsen-meta-bluetooth:amd64 9999
    Reinst Failed early because of libelf1:amd64
    Reinst Failed because of libdw1:amd64
  Considering bluez:amd64 1 as a solution to bunsen-meta-bluetooth:amd64 9999
Broken bunsen-meta-bluetooth:amd64 Depends on blueman:amd64 < none | 2.0.8-1+deb10u1 @un uH >
  Considering blueman:amd64 0 as a solution to bunsen-meta-bluetooth:amd64 9999
    Reinst Failed because of bluez:amd64
Broken bunsen-meta-bluetooth:amd64 Depends on pulseaudio-module-bluetooth:amd64 < none | 12.2-4+deb10u1 @un uH >
  Considering pulseaudio-module-bluetooth:amd64 2 as a solution to bunsen-meta-bluetooth:amd64 9999
  Considering pulseaudio-module-bluetooth:amd64 2 as a solution to bunsen-meta-bluetooth:amd64 9999
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 bunsen-meta-bluetooth : Depends: bluez but it is not going to be installed
                         Depends: blueman but it is not going to be installed
                         Depends: pulseaudio-module-bluetooth but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
lboo@newbie:~$ sudo apt-get -o Debug::pkgProblemResolver=yes install bluez
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) bluez:amd64 < none -> 5.50-1.2~deb10u1 @un puN Ib >
Broken bluez:amd64 Depends on libdw1:amd64 < none | 0.176-1.1 @un uH > (>= 0.127)
  Considering libdw1:amd64 0 as a solution to bluez:amd64 9999
    Reinst Failed early because of libelf1:amd64
  Considering libdw1:amd64 0 as a solution to bluez:amd64 9999
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 bluez : Depends: libdw1 (>= 0.127) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
lboo@newbie:~$ sudo apt-get -o Debug::pkgProblemResolver=yes install blueman
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) bluez:amd64 < none -> 5.50-1.2~deb10u1 @un uN Ib >
Broken bluez:amd64 Depends on libdw1:amd64 < none | 0.176-1.1 @un uH > (>= 0.127)
  Considering libdw1:amd64 0 as a solution to bluez:amd64 0
  Holding Back bluez:amd64 rather than change libdw1:amd64
Investigating (1) blueman:amd64 < none -> 2.0.8-1+deb10u1 @un puN Ib >
Broken blueman:amd64 Depends on bluez:amd64 < none | 5.50-1.2~deb10u1 @un uH > (>= 4.61)
  Considering bluez:amd64 0 as a solution to blueman:amd64 9999
    Reinst Failed early because of libelf1:amd64
    Reinst Failed because of libdw1:amd64
  Considering bluez:amd64 0 as a solution to blueman:amd64 9999
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 blueman : Depends: bluez (>= 4.61) but it is not going to be installed
           Recommends: pulseaudio-module-bluetooth but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
lboo@newbie:~$ 

so a whole lota 'nope' I'll read the linked topic later and get back with my findings.

Things I have tried- Bluez says it's missing libdw1, so i tried to manually install that from debian.pkgs.org. I was given an error code by the package installer and was told to get libelf1(=0.176-1.1). I manual retrieved that package and was thrown an error that a later version was already installed. I have not been able to locate this package on my system, but tbh I've never really got how

locate

and

find

work, so I might be using them wrong.
I was thinking things might be pointing to my Arch install, but am not sure how to confirm this.

edit::
oh yea, apt-cache policy

lboo@newbie:~$ apt-cache policy libelf1
libelf1:
  Installed: 0.183-1~bpo10+1
  Candidate: 0.183-1~bpo10+1
  Version table:
 *** 0.183-1~bpo10+1 100
        100 [url]https://deb.debian.org/debian[/url] buster-backports/main amd64 Packages
        100 /var/lib/dpkg/status
     0.176-1.1 500
        500 [url]https://deb.debian.org/debian[/url] buster/main amd64 Packages
lboo@newbie:~$ 

Last edited by horo (2021-03-10 16:37:22)

Offline

#10 2021-03-11 08:29:29

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 7,851
Website

Re: Apt-get not able to locate packages

OK things are starting to become clear.
You seem to have installed something from buster-backports which pulled in the backport version of libelf1 (0.183-1~bpo10+1)
But the regular version of libdw1 (0.176-1.1) needs a specific version of libelf1: 0.176-1.1
(Run 'apt show libdw1' to see that dependency: "Depends: libelf1 (= 0.176-1.1)" )

Since you have libelf 0.183-1~bpo10+1 then regular libdw1 cannot be installed. This is the sort of problem that installing backports can sometimes bring, unfortunately.

I guess you had some necessary backport (card's firmware?) which pulled in libelf1 0.183-1~bpo10+1?

First trick that might fix this would be to install the backport version of libdw1 (0.183-1~bpo10+1) which should be happy with your backported libelf1. Bluez should be OK with that version of libdw1 because its dependency is on any version >=  0.127.

So (as long as you're OK with this further non-standardization of your system) try:

sudo apt install -t buster-backports libdw1

And then go back and see if bl-welcome, or just installing the bluetooth metapackage, now runs OK. If that fixes it, great! It's possible you've got some other backported library which will then stick things up though...

horo wrote:

I have not been able to locate this package on my system, but tbh I've never really got how
locate
and
find
work, so I might be using them wrong.

Locate and find are great tools for finding files on your system, but for looking for packages there are different ones, eg:
'apt-cache policy <package>' (what version of <package> is installed - if any - and what versions are available from your enabled repositories)
'apt show <package>' (general info, in particular its dependencies)
'aptitude why-not <package>' (show possible conflicts, though not exhaustively)
'dpkg -L <package>' (show all the files installed by <package> on your system)
'dpkg -S <file>' (search for <file> in the installed packages)

Of course there are others!


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#11 2021-03-11 16:05:14

horo
Member
Registered: 2016-03-13
Posts: 47

Re: Apt-get not able to locate packages

Thank you! Looks like that got me going. Getting libdw1 from backports allowed me to install bluez and blueman packages, but i also had t run

sudo apt install -t buster-backports pulsaudio-module-bluetooth

to overcome a similar error
I re-ran bl-welcome and everthing installed this time with no error messages.
While I have your attention, is there a difference between 'apt' 'apt-get' and 'aptitude'? Are they different front ends to the same thing or different programs?
Is there anthign wrong in me writing a bunch of aliases to give them a more uniform command syntax.

Offline

#12 2021-03-11 18:18:34

damo
....moderator....
Registered: 2015-08-20
Posts: 6,572

Re: Apt-get not able to locate packages

I use a whole load of aliases for regular apt-get commands.


Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#13 2021-03-11 20:50:48

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 973

Re: Apt-get not able to locate packages

horo wrote:

is there a difference between 'apt' 'apt-get' and 'aptitude'? Are they different front ends to the same thing or different programs?

Apt is an newer tool than apt-get. Apt shows a meter for install process. It is not yet stable enough to ber used in scripts. In scripts apt-get should be used.

For further reading, see:
https://itsfoss.com/apt-vs-apt-get-difference/
https://www.tecmint.com/difference-betw … -aptitude/

Aptitude when "called solo", wil respond with an ncurserbased ui. Handy when you do not have X and need an ui to apt. Aptitude is sometimes beter to resolve dependecies than apt.

Is there anthign wrong in me writing a bunch of aliases to give them a more uniform command syntax.

Did not understand.


// Regards rbh

Offline

#14 2021-03-12 02:03:36

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 7,851
Website

Re: Apt-get not able to locate packages

horo wrote:

is there a difference between 'apt' 'apt-get' and 'aptitude'? Are they different front ends to the same thing or different programs?

Yes to both.
All work with apt and dpkg which are the Debian package handling software. 'apt' the command is a front-end to apt and dpkg. Likewise aptitude. 'apt-get' and 'apt-cache' are the more detailed and specific front-ends to apt.
So "apt" the command and "apt" the software suite are two different things unfortunately.

These days 'apt' is a good first choice for general package operations, but sometimes aptitude has some extra features you can use (see rbh's link), and as rbh says, 'apt-get' and 'apt-cache' are better for scripts because their behaviour is expected not to change too much in the future.


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#15 2021-03-12 14:11:43

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 973

Re: Apt-get not able to locate packages

johnraff wrote:

So "apt" the command and "apt" the software suite are two different things unfortunately.

Saw that Debian Handbook uses APT in uppercase, when talking about the infrastructure, tools and the deb database. Imagine that is better to avoid confusion:

APT (the abbreviation of "Advanced Packaging Tool") is a group of programs that allows the execution of higher-level modifications to the system: installing or removing a package (while keeping dependencies satisfied), updating and upgrading the system, listing the available packages, etc.

https://debian-handbook.info/browse/bus … ystem.html

apt-get' and 'apt-cache' are better for scripts because their behaviour is expected not to change too much in the future.

Yeah, that i better explanation.


// Regards rbh

Offline

Board footer

Powered by FluxBB