You are not logged in.
Reminder: adding ppa's or other sources is likely to break your system. But you can keep the pieces
![]()
So is the implicit message here that if I did so and I have issues, then there is no point in trying to "back out"? And that for all practical purposes, it is time to do a wipe?
Also, is there a place to find out if something simply won't work, very likely, on BL, reasonably? For instance, PostgreDB? Or MongoDB? Or Django? Or whatever are the latest Web frameworks, GIS tools, and databases, etc?
Roland Shield
n00b 2.x
ass.clown@perchslayer.com | "...'ere I am, J.H."
Offline
damo wrote:Reminder: adding ppa's or other sources is likely to break your system. But you can keep the pieces
![]()
So is the implicit message here that if I did so and I have issues, then there is no point in trying to "back out"? And that for all practical purposes, it is time to do a wipe?
Also, is there a place to find out if something simply won't work, very likely, on BL, reasonably? For instance, PostgreDB? Or MongoDB? Or Django? Or whatever are the latest Web frameworks, GIS tools, and databases, etc?
Most if not all of these have repositories for Debian jessie – PostgreSQL definitely has, I don't work with the others. If it works on jessie, just use those repositories.
Ubuntu Xenial PPAs won't work if the binaries in there require different or patched library versions, but for the most part, Xenial is accidentally binary-compatible with jessie so unless things break they're gonna work. But you get to keep the pieces if there are dependency problems.
Offline
damo wrote:Reminder: adding ppa's or other sources is likely to break your system. But you can keep the pieces
![]()
So is the implicit message here that if I did so and I have issues, then there is no point in trying to "back out"? And that for all practical purposes, it is time to do a wipe?
YES, that's what it means.
and we appreciate your honesty.
you wouldn't believe how many people break their system this way and don't admit to having done exactly that.
Also, is there a place to find out if something simply won't work, very likely, on BL, reasonably? For instance, PostgreDB? Or MongoDB? Or Django? Or whatever are the latest Web frameworks, GIS tools, and databases, etc?
Offline
New to Linux...thanks for indicating general theme related to repository...GoldsteinBruce
Offline
How-to automatically find your quickest local mirror: https://forums.bunsenlabs.org/viewtopic.php?id=2889
...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 )
Offline
^ Good point. I've added it to the OP
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
I have carefully linked to all the sources and I am still getting the following:
Get:53 http://httpredir.debian.org jessie/main amd64 Packages [6,776 kB]
Get:54 http://httpredir.debian.org jessie/contrib amd64 Packages [50.2 kB]
Get:55 http://httpredir.debian.org jessie/main i386 Packages [6,779 kB]
Get:56 http://httpredir.debian.org jessie/contrib i386 Packages [49.5 kB]
Get:57 http://httpredir.debian.org jessie/contrib Translation-en [38.5 kB]
Get:58 http://httpredir.debian.org jessie/main Translation-en [4,582 kB]
Err http://ppa.launchpad.net bunsen-hydrogen/main amd64 Packages
404 Not Found [IP: 78.47.156.207 80]
Err http://ppa.launchpad.net bunsen-hydrogen/main i386 Packages
404 Not Found [IP: 78.47.156.207 80]
Ign http://ppa.launchpad.net bunsen-hydrogen/main Translation-en_US
Ign http://ppa.launchpad.net bunsen-hydrogen/main Translation-en
Ign http://repo.mongodb.org jessie/mongodb-org/3.2/main Translation-en_US
Ign http://repo.mongodb.org jessie/mongodb-org/3.2/main Translation-en
Err http://apt.postgresql.org bunsen-hydrogen-pgdg/main amd64 Packages
404 Not Found [IP: 174.143.35.246 80]
Err http://apt.postgresql.org bunsen-hydrogen-pgdg/main i386 Packages
404 Not Found [IP: 174.143.35.246 80]
Ign http://apt.postgresql.org bunsen-hydrogen-pgdg/main Translation-en_US
Ign http://apt.postgresql.org bunsen-hydrogen-pgdg/main Translation-en
Hit http://toolbelt.heroku.com ./ Packages
Get:59 http://pkg.bunsenlabs.org bunsen-hydrogen/main amd64 Packages [9,923 B]
Get:60 http://pkg.bunsenlabs.org bunsen-hydrogen/main i386 Packages [9,926 B]
Ign http://pkg.bunsenlabs.org bunsen-hydrogen/main Translation-en_US
Ign http://pkg.bunsenlabs.org bunsen-hydrogen/main Translation-en
Ign http://toolbelt.heroku.com ./ Translation-en_US
Ign http://toolbelt.heroku.com ./ Translation-en
Fetched 18.3 MB in 4min 9s (73.3 kB/s)
W: GPG error: http://qgis.org jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 073D307A618E5811
W: There is no public key available for the following key IDs:
8B48AD6246925553
W: GPG error: http://cran.cnr.berkeley.edu jessie-cran3/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 06F90DE5381BA480
W: There is no public key available for the following key IDs:
8B48AD6246925553
W: GPG error: http://cran.rstudio.com lenny-cran/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 06F90DE5381BA480
W: There is no public key available for the following key IDs:
8B48AD6246925553
W: GPG error: http://pkg.bunsenlabs.org bunsen-hydrogen InRelease: The following signatures were invalid: KEYEXPIRED 1468162041 KEYEXPIRED 1468162041 KEYEXPIRED 1468162041
W: There is no public key available for the following key IDs:
8B48AD6246925553
W: Failed to fetch http://rodeo-deb.yhat.com/dists/rodeo/InRelease Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)
W: Failed to fetch http://us.debian.org/debian/dists/jessie/Release.gpg Something wicked happened resolving 'us.debian.org:http' (-5 - No address associated with hostname)
W: Failed to fetch http://us.debian.org/debian/dists/jessie/main/binary-amd64/Packages Something wicked happened resolving 'us.debian.org:http' (-5 - No address associated with hostname)
W: Failed to fetch http://us.debian.org/debian/dists/jessie/main/binary-i386/Packages Something wicked happened resolving 'us.debian.org:http' (-5 - No address associated with hostname)
W: Failed to fetch http://us.debian.org/debian/dists/jessie/main/i18n/Translation-en_US Something wicked happened resolving 'us.debian.org:http' (-5 - No address associated with hostname)
W: Failed to fetch http://us.debian.org/debian/dists/jessie/main/i18n/Translation-en Something wicked happened resolving 'us.debian.org:http' (-5 - No address associated with hostname)
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)
W: Failed to fetch http://ppa.launchpad.net/linuxgndu/sqlitebrowser/ubuntu/dists/bunsen-hydrogen/main/binary-amd64/Packages 404 Not Found [IP: 78.47.156.207 80]
W: Failed to fetch http://ppa.launchpad.net/linuxgndu/sqlitebrowser/ubuntu/dists/bunsen-hydrogen/main/binary-i386/Packages 404 Not Found [IP: 78.47.156.207 80]
W: Failed to fetch http://apt.postgresql.org/pub/repos/apt/dists/bunsen-hydrogen-pgdg/main/binary-amd64/Packages 404 Not Found [IP: 174.143.35.246 80]
W: Failed to fetch http://apt.postgresql.org/pub/repos/apt/dists/bunsen-hydrogen-pgdg/main/binary-i386/Packages 404 Not Found [IP: 174.143.35.246 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
I see that there is mention of public keys not found, etc. Does this basically mean that my system is hosed?
Roland Shield
n00b 2.x
ass.clown@perchslayer.com | "...'ere I am, J.H."
Offline
I have carefully linked to all the sources and I am still getting the following:
Err http://ppa.launchpad.net bunsen-hydrogen/main amd64 Packages 404 Not Found [IP: 78.47.156.207 80] Err http://ppa.launchpad.net bunsen-hydrogen/main i386 Packages 404 Not Found [IP: 78.47.156.207 80] Err http://apt.postgresql.org bunsen-hydrogen-pgdg/main amd64 Packages 404 Not Found [IP: 174.143.35.246 80] Err http://apt.postgresql.org bunsen-hydrogen-pgdg/main i386 Packages 404 Not Found [IP: 174.143.35.246 80] Hit http://toolbelt.heroku.com ./
I see that there is mention of public keys not found, etc. Does this basically mean that my system is hosed?
yes, but not because of the public keys, you self-confessed ass-clown.
Offline
^ Great, now I have to clean coffee off my laptop screen...
@ass.clownperchslayer: please post the output of:
apt-cache policy
Which software have you installed from non-Debian repositories?
I can see a (failed) attempt to add some PPAs, have you read https://wiki.debian.org/DontBreakDebian … nkenDebian?
Offline
Mainly an Ubuntu user musing. If backports are enabled, shouldn't the newest program version automatically appear in Synaptic? I am a bit confused also by the need to be explicit with apt when backports are enabled. If you enabled backports, can't one assume that it is because the user wants newer software to be available in general? Particularly considering Debian's reputation for keeping programs in testing until they are almost Jurassic?
Offline
If you enabled backports, can't one assume that it is because the user wants newer software to be available in general?
Backports are pinned at 100 by default, which means that users have to specifically request that a particular package be installed from the backports repositories. This is Debian policy. As the Debian Backports site says:
Backports cannot be tested as extensively as Debian stable, and backports are provided on an as-is basis, with risk of incompatibilities with other components in Debian stable. Use with care!
It is therefore recommended to only select single backported packages that fit your needs, and not use all available backports.
If backports got standard 500 pinning then next time you did an 'apt-get upgrade' all your packages would be upgraded to the backports version (if there was one available). This is not likely to be a Good Thing, and defeats the purpose of running Debian Stable.
...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 )
Offline
What is this "Synaptic" of which you speak? 8o
Have you tried
apt-cache policy $package
This will show all available versions (and their APT pin values).
https://www.debian.org/doc/manuals/debi … ommandline
If you enabled backports, can't one assume that it is because the user wants newer software to be available in general?
No, not at all.
BunsenLabs is a poor choice for those who always want shiny new sh...tuff because we are based on Debian stable, please see https://wiki.debian.org/DontBreakDebian … f_Syndrome
Offline
If you want more new software and lose stability, suppose it is better to use another distribution based on testing.
lenovo thinkpad t420s
Offline
If you want more new software and lose stability, suppose it is better to use another distribution based on testing.
Or if you are adventurous you can point the Debian repo in the sources list to Testing and upgrade to Testing. At this point my brief testing in a VM indicates it can be done fairly easily.
Real Men Use Linux
Offline
Or if you are adventurous you can point the Debian repo in the sources list to Testing and upgrade to Testing. At this point my brief testing in a VM indicates it can be done fairly easily.
Please don't advise that our users break their systems.
@all, please *do not* follow this advice unless you like fixing broken boxen.
Offline
At this point my brief testing in a VM indicates it can be done fairly easily.
famous last words ]:D
Offline
^
One is put in mind of the skydiver who's parachute has broken and as he plummets to his death he just keeps repeating to himself:
So far, so good...
Offline
So /etc/apt/sources.list.d/bunsen.list takes the place of the base debian repository, rather than just supplementing it? I tried visiting https://pkg.bunsenlabs.org/ to learn more but it gives me a 403 access denied.
I just installed bunsenlabs from the latest iso minutes ago. Some of the updates initiated by the bl-welcome script failed, so I opened my sources.list and was surprised to see it only contains:
#
# deb cdrom:[Debian GNU/Linux 9.6 _Helium_ - Snapshot amd64 LIVE/INSTALL Binary 20181113-17:01]/ stretch contrib main non-free
#deb cdrom:[Debian GNU/Linux 9.6 _Helium_ - Snapshot amd64 LIVE/INSTALL Binary 20181113-17:01]/ stretch contrib main non-free
## Debian security updates
deb https://deb.debian.org/debian-security stretch/updates main contrib non-free
No base, only security, and no "volatile" as in the top post. Apart from that my bunsen.list, bunsen-stretch-backports.list, and debian-stretch-backports.list all look correct as in the top post.
Thanks for helping out a newbie.
Offline
The bunsen.list file supplements the sources.list file from Debian.
You should have or need to create or add something similar to this...
In /etc/apt/sources.list, something like...
deb https://deb.debian.org/debian stretch main non-free contrib
# deb-src https://deb.debian.org/debian stretch main non-free contrib
deb http://security.debian.org stretch/updates main contrib non-free
# deb-src http://security.debian.org stretch/updates main contrib non-free
And in /etc/apt/sources.list.d/bunsen.list...
deb https://pkg.bunsenlabs.org/debian helium main
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Thanks hhh. My bunsen.list matches that exactly. Any idea why my sources.list got borked on a fresh install?
Offline