contrib and non-free missing from parts of sources.list

sto · 2016-02-28 23:03:25

I think I have installed rc2... I downloaded it today.
how can I check the version?

sto · 2016-02-28 23:05:10

lsb_release -da
No LSB modules are available.
Distributor ID:	BunsenLabs
Description:	BunsenLabs GNU/Linux 8.3 (Hydrogen)
Release:	8.3
Codename:	bunsen-hydrogen

Last edited by sto (2016-02-28 23:08:22)

hhh · 2016-02-28 23:13:50

^Run 'apt-cache policy modemmanager'. If it's installed, you're using rc2.

sto · 2016-02-28 23:17:18

it's installed. 1.4.0-1

Horizon_Brave · 2016-02-28 23:17:31

Hhh, do you think OP's problem, and sto's problem are related? Was this an RC1 issue?

Last edited by Horizon_Brave (2016-02-28 23:18:35)

sto · 2016-02-28 23:22:29

/etc/apt/sources.list

# 

# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Bi$

# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Bi$

# Line commented out by installer because it failed to verify:
deb http://security.debian.org/ jessie/updates main contrib non-free
# Line commented out by installer because it failed to verify:
deb-src http://security.debian.org/ jessie/updates main contrib non-free
deb http://pkg.bunsenlabs.org/debian bunsen-hydrogen main
deb http://pkg.bunsenlabs.org/debian jessie-backports main
deb http://httpredir.debian.org/debian jessie-backports main contrib non-free
deb http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Debian_8.0/ /

it apt-get updates fine... but

$ sudo apt-get install owncloud-client
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:
 owncloud-client : Depends: libowncloudsync0 (= 2.1.1-1.1) but it is not going to be installed
                   Depends: libqt4-dbus (>= 4:4.5.3) but it is not installable
                   Depends: libqt4-network (>= 4:4.7.0~beta1) but it is not installable
                   Depends: libqt4-sql (>= 4:4.5.3) but it is not installable
                   Depends: libqt4-xml (>= 4:4.5.3) but it is not installable
                   Depends: libqt4-xmlpatterns (>= 4:4.5.3) but it is not installable
                   Depends: libqtkeychain0 but it is not going to be installed
                   Depends: libqtwebkit4 (>= 2.2.0) but it is not installable
                   Depends: libqt4-sql-sqlite but it is not installable
                   Depends: owncloud-client-l10n but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

apt-cache policy libqt4-sql
libqt4-sql:
  Installed: (none)
  Candidate: (none)
  Version table:

Last edited by sto (2016-02-28 23:26:04)

sto · 2016-02-28 23:27:57

well, maybe I messed up something with the sources...

but I even cannot get emacs.

sudo apt-get install emacs
[sudo] password for sto: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package emacs 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

E: Package 'emacs' has no installation candidate

hhh · 2016-02-28 23:29:29

Yeah, we can't support broken dependencies due to you adding an OpenSuse repo. Was that error really a surprise to you?

@Horizon, contrib and non-free missing is a bug that appears on some hardware (mostly just when using a VM) which we think we've solved with an edit to bl-welcome.

sto · 2016-02-28 23:33:32

ok

hhh · 2016-02-28 23:34:50

@sto, remove the OpenSuse repo, add this line to /etc/apt/sources.list and run 'sudo apt update again'...

deb http://httpredir.debian.org/debian jessie main contrib non-free

sto · 2016-02-28 23:50:33

thank you... I could install emacs.

so fine for me...

cheers
sto

johnraff · 2016-02-29 02:10:50

Re the BunsenLabs install (forgetting Suse) there are two different issues here:

1) Contrib and non-free are left out by the Debian installer when installing to a Virtual Machine (and sometimes to hardware?). https://lists.debian.org/debian-user/20 … 00616.html The latest bl-welcome script checks for this issue and fixes it if found.

2) Unfortunately, the upgrade of bunsen-welcome from the version in the RC2 (or RC1) iso causes a variable's name to change so that if the upgrade takes place while bl-welcome is running - which it very likely does - then the debian backports apt source entry is corrupted. See here, and here for workarounds.

pvsage · 2016-02-29 03:24:18

@hhh: The regression in the bl-welcome script appears to affect both RC2 and RC1. As johnraff mentioned, a "sanity check" has been added to the current bl-welcome in the repo, but until we get that into the ISO the workarounds mentioned in the above post will be necessary, unless...

@johnraff: Is it possible to add a hook to one of the main bunsenlabs metapackages so that bl-welcome is forced to exit after the initial `apt-get upgrade` and restart with the updated bl-welcome? (Not sure how it would work; thinking of something deferred to the end of the package update process that sends a `kill bl-welcome && bl-welcome`.) If it is, then the workarounds should be unnecessary.

Last edited by pvsage (2016-02-29 03:33:13)

johnraff · 2016-02-29 09:26:08

pvsage wrote:

Is it possible to add a hook to one of the main bunsenlabs metapackages so that bl-welcome is forced to exit after the initial `apt-get upgrade` and restart with the updated bl-welcome? (Not sure how it would work; thinking of something deferred to the end of the package update process that sends a `kill bl-welcome && bl-welcome`.)

Hmm...

Ah, you mean perhaps the upgrade of bunsen-welcome might be made to check for a running instance of bl-welcome and restart it?

Might be possible...

johnraff · 2016-03-01 06:36:28

What we need is a quick fix to cover the period till the next iso comes out, so that people won't break their systems when bl-welcome upgrades itself.

Maybe this will work:
*) The main script file 'bl-welcome' itself sources a number of other files in turn, one corresponding to each "page" in the script. The backports line problem comes because at the "apt-upgrade" page, while 'bl-welcome', 'check-repos', 'apt-update' and 'apt-upgrade' have already been loaded into memory, the other files are overwritten when bunsen-welcome is upgraded and the new 'add-debian-backports' is not compatible with the old 'bl-welcome', because the name of the variable holding the default url changes.

*) So, at the upgrade point, while the old 'apt-upgrade' is already loaded, the next file, 'system-tweaks' will be the new version. What we can do is drop a test in the new 'system-tweaks' file to see what 'bl-welcome' file it is being sourced by, and if it looks old, to force a restart. Since I'm already planning to put

set -o nounset

in the new 'bl-welcome' (to avoid that kind of unset-variable issue in future) then the new 'system-tweaks' can look at $- to see what shell options have been set. If nounset has not been set then it will know that 'bl-welcome' is an old version.

This code can be dropped in the start of 'system-tweaks'. (Once the new bunsen-welcome is in the iso it will no longer be necessary.)

#############
# temporary fix to avoid breaking 'add-debian-backports'
[[ $- = *u* ]] || {
    log "bw-welcome has not set -o nounset"
    say "The package 'bunsen-welcome' has been upgraded.
This script has changed, so it will have to be restarted.
Please wait a moment..." 4
    exec >/dev/tty 2>&1 # so terminalCheck() doesn't open a new terminal
    exec "$0"
}
#############

I'll test this out and if it seems to work I'll get it up to GitHub ASAP.

johnraff · 2016-03-02 03:50:58

We believe that the bug you reported is fixed in the latest version of bunsen-welcome (8.9-1)
which has been pushed to GitHub.

It should arrive in the repos soon (nobody has been very swift with this lately in spite of being so busy) and from that point new installs will experience nothing worse than bl-welcome restarting itself on its first run, just after apt-upgrade.

That's what I believe anyway...

[EDIT] It's now in the BL Apt repos and will come down with upgrades. Many thanks nobody!

Last edited by johnraff (2016-03-03 03:30:27)

Horizon_Brave · 2016-03-04 01:44:57

johnraff wrote:

What we need is a quick fix to cover the period till the next iso comes out, so that people won't break their systems when bl-welcome upgrades itself.
Maybe this will work:
*) The main script file 'bl-welcome' itself sources a number of other files in turn, one corresponding to each "page" in the script. The backports line problem comes because at the "apt-upgrade" page, while 'bl-welcome', 'check-repos', 'apt-update' and 'apt-upgrade' have already been loaded into memory, the other files are overwritten when bunsen-welcome is upgraded and the new 'add-debian-backports' is not compatible with the old 'bl-welcome', because the name of the variable holding the default url changes.
*) So, at the upgrade point, while the old 'apt-upgrade' is already loaded, the next file, 'system-tweaks' will be the new version. What we can do is drop a test in the new 'system-tweaks' file to see what 'bl-welcome' file it is being sourced by, and if it looks old, to force a restart. Since I'm already planning to put
set -o nounset
in the new 'bl-welcome' (to avoid that kind of unset-variable issue in future) then the new 'system-tweaks' can look at $- to see what shell options have been set. If nounset has not been set then it will know that 'bl-welcome' is an old version.
#############
# temporary fix to avoid breaking 'add-debian-backports'
[[ $- = *u* ]] || {
    log "bw-welcome has not set -o nounset"
    say "The package 'bunsen-welcome' has been upgraded.
This script has changed, so it will have to be restarted.
Please wait a moment..." 4
    exec >/dev/tty 2>&1 # so terminalCheck() doesn't open a new terminal
    exec "$0"
}
#############

@JohnRaff....or anyone really I'm not picky... Two questions:

1. What does the $- syntax test for in the [[ ]] parameters? Also what's the significance of matching *u* ?

2. Also in the welcome script, we set the STEP_BASIC array equal to many of the different "Pages" in the bunsen welcome suite. I noticed in the new updated welcome script, "check-repos" was put ahead of all the rest. Does the order of assigning the indexes in the array matter? Wouldn't / Couldn't we pick and chose which index to run?

Thanks!

johnraff · 2016-03-04 06:22:19

Horizon_Brave wrote:

1. What does the $- syntax test for in the [[ ]] parameters? Also what's the significance of matching *u* ?

Check man bash in the SHELL BUILTIN COMMANDS section, under "set" to find nounset and its short form -u, then PARAMETERS, under "Special Parameters" for -.

2. Also in the welcome script, we set the STEP_BASIC array equal to many of the different "Pages" in the bunsen welcome suite. I noticed in the new updated welcome script, "check-repos" was put ahead of all the rest. Does the order of assigning the indexes in the array matter?

Yes. That's the order the script will go through its tasks. Getting contrib non-free in the apt sources had to be done first.

pvsage · 2016-03-04 13:24:19

Patch works well on fresh install; well done development team! Cake will be served.

Horizon_Brave · 2016-03-04 17:52:46

johnraff wrote:

Check man bash in the SHELL BUILTIN COMMANDS section, under "set" to find nounset and its short form -u, then PARAMETERS, under "Special Parameters" for -.
Yes. That's the order the script will go through its tasks. Getting contrib non-free in the apt sources had to be done first.

You know besides the actual man page for bash (which is something that, to me, can be entirely vague) there isn't a lot documentation for the nitty gritty stuff like this..

Okay, so just to recap... The set -o nounset serves two purposes, it first tells the main bl-welcome to error out if it falls prey to the variable name change that is causing the contrib / non-free lines to be skipped.

2nd, it provides a 'hook' (more of a sanity check *just* in case..) to be applied in the next script called 'system tweaks'. The line:

[[ $- = *u* ]] || {
    log "bw-welcome has not set -o nounset"
    say "The package 'bunsen-welcome' has been upgraded.

is put into the system tweaks script. The $- checks all arguments passed to the parent or currently running script. In this case it's checking if -u or nounset was found... This is the part that threw me off as well... the || means OR. That I knew but was unclear of the usage. It means that if the first part [[ $- = *u* ]], succeeds (exit 0), then don't run the next steps. But if it fails, (there is no set -o nonuset), then make sure to run the proceeding commands. Which then alert the user that he goof'd and the welcome script is reloaded and the old one is trashed.

Sheesh...I love bash, but the syntax sometimes just drives me nuts! And this isn't even that complicated!

Thanks Jon!

#21 2016-02-28 23:03:25

Re: contrib and non-free missing from parts of sources.list

#22 2016-02-28 23:05:10

Re: contrib and non-free missing from parts of sources.list

#23 2016-02-28 23:13:50

Re: contrib and non-free missing from parts of sources.list

#24 2016-02-28 23:17:18

Re: contrib and non-free missing from parts of sources.list

#25 2016-02-28 23:17:31

Re: contrib and non-free missing from parts of sources.list

#26 2016-02-28 23:22:29

Re: contrib and non-free missing from parts of sources.list

#27 2016-02-28 23:27:57

Re: contrib and non-free missing from parts of sources.list

#28 2016-02-28 23:29:29

Re: contrib and non-free missing from parts of sources.list

#29 2016-02-28 23:33:32

Re: contrib and non-free missing from parts of sources.list

#30 2016-02-28 23:34:50

Re: contrib and non-free missing from parts of sources.list

#31 2016-02-28 23:50:33

Re: contrib and non-free missing from parts of sources.list

#32 2016-02-29 02:10:50

Re: contrib and non-free missing from parts of sources.list

#33 2016-02-29 03:24:18

Re: contrib and non-free missing from parts of sources.list

#34 2016-02-29 09:26:08

Re: contrib and non-free missing from parts of sources.list

#35 2016-03-01 06:36:28

Re: contrib and non-free missing from parts of sources.list

#36 2016-03-02 03:50:58

Re: contrib and non-free missing from parts of sources.list

#37 2016-03-04 01:44:57

Re: contrib and non-free missing from parts of sources.list

#38 2016-03-04 06:22:19

Re: contrib and non-free missing from parts of sources.list

#39 2016-03-04 13:24:19

Re: contrib and non-free missing from parts of sources.list

#40 2016-03-04 17:52:46

Re: contrib and non-free missing from parts of sources.list

Board footer