You are not logged in.
I installed bunsenlabs from the rc1 x86 iso and noticed that contrib and non-free are missing from the main sources.list line. I.e.,
#
# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot i386 LIVE/INSTALL Binary 20150908-13:17]/ jessie contrib main non-free
# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot i386 LIVE/INSTALL Binary 20150908-13:17]/ jessie contrib main non-free
deb http://ftp.us.debian.org/debian/ jessie main
#deb-src http://ftp.us.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main contrib non-free
#deb-src http://security.debian.org/ jessie/updates main contrib non-free
# jessie-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ jessie-updates main contrib non-free
#deb-src http://ftp.us.debian.org/debian/ jessie-updates main contrib non-free
Offline
Hello kozimodo, thank you for your report
May I ask how you transferred the ISO image to the installation medium?
The incomplete line is the main jessie repository and was placed there by the Debian installer so this would probably be an upstream issue.
Can you remember which options were selected during the installation process?
EDIT: Did the sha256 checksum match for the ISO image?
Last edited by Head_on_a_Stick (2015-12-12 10:07:48)
Offline
I used dd to a thumb drive. I used a manual partition but aside from that I think I took the default options.
For both the i386 and x86_64 image, the hashes match.
Offline
I took the default options
There is a section in the installer which asks if you want to add "contrib" & "non-free" to the sources.list -- I can't remember what the default reply is.
Perhaps you inadvertently de-selected the components.
Offline
kozimodo wrote:I took the default options
There is a section in the installer which asks if you want to add "contrib" & "non-free" to the sources.list -- I can't remember what the default reply is.
Perhaps you inadvertently de-selected the components.
The Debian approach is to leave the choice of using non-free packages, or those that depend on non-free, up to the user. So I assume the default is "No".
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
So I assume the default is "No".
I would think so, yes.
Do you have a moment to test it in a VM?
OpenBSD doesn't do virtualisation 8)
Offline
I just installed bunsen in a vm and there was no point at which it asked if I wanted contrib and non-free. So contrib and non-free are enabled in jessie-updates and security jessie/updates but not the main jessie repo.
IMHO, if it's not enabled for the main repo, it shouldn't be enabled for updates or security.
Offline
I just installed bunsen in a vm and there was no point at which it asked if I wanted contrib and non-free
I think the option is in the "Advanced" installer
At any rate, this would appear to be an upstream issue -- the BunsenLabs ISO image is based on the Debian jessie live ISO.
There will be a new version of the live ISO and installer out soon (when the UEFI problems have been fixed).
Offline
We ran into this same issue in September, only when installing on a VirtualBox VM.
Unfortunately it was discussed on a private GitHub repo so I can't link to it.
It's very strange and no-one has any idea why it should happen, but if you install on real hardware the 'contrib non-free' sections of the line are in place.
I should do another VM Debian netinstall to compare with BL, but if this problem persists on VM installs then we'll have no option but to recommend people to edit their sources.list by hand I guess.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
So I installed both the i386 version and the x86_64 version on real hardware and neither contrib nor non-free were in the main deb line. It was only later that I installed it as a virtual machine to remind myself whether there was a question about contrib and non-free.
Offline
So I installed both the i386 version and the x86_64 version on real hardware and neither contrib nor non-free were in the main deb line
Right, OK.
Thank you very much for taking the time to investigate this further -- I will try installing BL later today to see if I can reproduce this.
Offline
I have just installed BunsenLabs to a USB stick using the rc1 ISO image and the contrib & non-free components were added successfully.
No questions were asked about these components during the installation (default ncurses interface selected).
Can you confirm the exact URL from which you obtained the ISO image?
If you have the time or inclination, perhaps you should try again with a freshly downloaded image.
Offline
The i386 iso is the direct download link: http://ddl.bunsenlabs.org/bl-Hydrogen-rc1-i386.iso and the sha256sum I get is: 02c0cc5f9a42bfb22f7de3981375cce159810512121590bdba8dee29b910fe2f.
The x86_64 iso is the torrent link: http://ddl.bunsenlabs.org/bl-Hydrogen-r … so.torrent and the sha256sum I get is: 35d8a22e069f98f816e6784e1d429990516174d22f76bf4c87ba2621180201dc.
In both cases I used the non-graphical install -- if you used the graphical install, that is in all likelihood the source of the difference.
Offline
In both cases I used the non-graphical install -- if you used the graphical install, that is in all likelihood the source of the difference.
No, I used the ncurses interface and I downloaded my (64 bit) image from the exact same URL
I'll try it again a few times tonight.
Offline
I've just done a bare-metal graphical install of `bl-Hydrogen-rc1-amd64.iso` from the torrent download, chose a local mirror, and get:
#
# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150909-03:19]/ jessie contrib main non-free
# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150909-03:19]/ jessie contrib main non-free
deb http://ftp.uk.debian.org/debian/ jessie main non-free contrib
#deb-src http://ftp.uk.debian.org/debian/ jessie main non-free contrib
deb http://security.debian.org/ jessie/updates main contrib non-free
#deb-src http://security.debian.org/ jessie/updates main contrib non-free
# jessie-updates, previously known as 'volatile'
deb http://ftp.uk.debian.org/debian/ jessie-updates main contrib non-free
#deb-src http://ftp.uk.debian.org/debian/ jessie-updates main contrib non-free
EDIT: same result using the ncurses Install method
EDIT2: got a new direct download of the amd-64 iso, dd'd to usb, and a bare-metal graphical install. This time I used the `httpredir` mirror and get:
deb http://httpredir.debian.org/debian/ jessie main non-free contrib
So all is still good
Last edited by damo (2015-12-14 16:59:08)
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
Could it be the same problem as with VMs? Something to do with the machine's architecture? The two computers I installed on are a very old Acer Aspire One and a newish desktop with a Gigabyte Gaming z97 mobo.
Offline
Hi all
I just installed bunsenlab x64 via usb stick on my laptop for the first time.
Two points to mention:
1. at first, the wifi has not been recognized during install, but after the first startup. fine.
2. while running the bl-welcome script (which popped up after fresh install), it could do some steps, but then failed with the error that the sources.list is not correct. I had to abort the initial welcome script. So the situation at this point:
in /etc/apt/sources.list.d/
4 files: deb-multi.list debian-jessie-backports.list bunsen-jessie-backports.list bunsen.list
apt-get update got failed because of the contrib main repos...
well, my solution: delete all lists and touch sources.list and add the official repos from the website I found (2x main) and the mentioned in this thread: http://httpredir.debian.org/debian jessie-bakcports main contrib non-free
that worked fine.
cheers
sto
Last edited by sto (2016-02-28 21:07:37)
Offline
Sto, did you install to a vm? Did you re-run the bl-welcome script successfully?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
hi Horizon
no, on a intel 4gb amd gpu laptop directly.. dev/sda6 w/o swap
the bl-welcome didn't rerun properly. It breaks after page 2 ... enableing contrib and non-free fails.
sources seem to be a mess.
well apt-get update and upgrade and dist-upgrade did well and some other installs but.
just tried to install the owncloud client by adding its standard repo for debian.
it cannot be installed due to dependenciy errors/warnings.
is it normal that root cannot run the bl-welcome? (not in the sudo group - error)
thanks for the help
cheers
Offline
rc2 is out, please try installing that instead.
I don't care what you do at home. Would you care to explain?
Online