You are not logged in.

#1 2021-10-28 12:19:03

rbh
Moderator
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,295

Package bunsen-user-setup

Hi!

Just for the fun of it, i ran command "apt policy bunsen*".

Noticed this output:

bunsen-user-setup:
  Installed: (none)
  Candidate: (none)
  Version table:

Trying to install it, returns:

Package bunsen-user-setup is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

This was a Lithium system, upgraded to Beryllium.

Same behavior on a Lithium and Helium system!


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#2 2021-10-28 14:36:14

sleekmason
zoom
Registered: 2018-05-22
Posts: 651
Website

Re: Package bunsen-user-setup

Maybe not used or removed during late install? What would/does the Bunsen version do?

apt policy user* shows: (for lithium)

user-setup:
  Installed: 1.81
  Candidate: 1.81
  Version table:
 *** 1.81 500
        500 https://deb.debian.org/debian buster/main amd64 Packages
        100 /var/lib/dpkg/status

Last edited by sleekmason (2021-10-28 14:36:55)

Offline

#3 2021-10-29 02:27:45

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,424
Website

Re: Package bunsen-user-setup

There is no longer a BL package called bunsen-user-setup - it is indeed obsolete, as the install message suggested. (user-setup is a quite different package smile)
Apt policy output showed no candidate version either. (bunsen-lock is another such case.) These entries come up because apt or dpkg data is remaining from earlier systems, or maybe because some current packages refer to them, eg bunsen-utilities:

Conflicts: bunsen-lock, bunsen-user-setup

That entry makes sure that those obsolete packages, if still installed, are removed when installing the current bunsen-utilities.

---
BTW It's best to put quotes around the policy command argument if it contains a *:

apt-cache policy 'bunsen*'

Otherwise the shell will first look in your home directory for files whose name begins with bunsen:

john@lithium:~$ apt policy bunsen*
N: Unable to locate package bunsen-dev.asc
N: Couldn't find any package by glob 'bunsen-dev.asc'
N: Couldn't find any package by regex 'bunsen-dev.asc'
N: Unable to locate package bunsen-dev.asc-old
N: Couldn't find any package by glob 'bunsen-dev.asc-old'
N: Couldn't find any package by regex 'bunsen-dev.asc-old'

Last edited by johnraff (2021-10-29 02:29:37)


...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

Board footer

Powered by FluxBB