[Solved] Sources list for Stretch?

isosceles · 2015-09-05 19:24:21

I would like to move to stretch. Do I literally replace every instance of 'jessie' with 'stretch'? I thought I should leave the line about the cdrom alone. Look okay?

# 

# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150711-01:57]/ jessie contrib main non-free

deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150711-01:57]/ jessie contrib main non-free

deb http://ftp.us.debian.org/debian/ stretch main non-free contrib
#deb-src http://ftp.us.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

# stretch-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
#deb-src http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free

# added by bl-welcome
# Multimedia repository
deb http://www.deb-multimedia.org stretch main non-free

[Solved] I'm going to research backports so as to avoid breaking my system as I've done in the past.

Last edited by isosceles (2015-09-06 04:58:42)

Sector11 · 2015-09-05 19:33:35

First of I would comment out the cdrom line completely. Jessie and stretch are not compatible.

Be ready for borkage IE Make a really good backup!

Before upgrading a few things.

comment out cdrom lines
install apt-listbugs
sudo apt-get update ; sudo apt-get upgrade
change sources list from jessie to stretch
sudo apt-get update ; sudo apt-get dist-upgrade

and be prepared to put apps on hold/unhold (my aliases) :

### HOLD UNHOLD AUTO MANUAL ###
alias hld='echo "alias hld = sudo apt-mark hold app_name app_name" ; sudo apt-mark hold'
alias unhld='echo "alias unhld = sudo apt-mark unhold app_name app_name" ; sudo apt-mark unhold'
alias shld='echo "alias shld = apt-mark showhold" ; apt-mark showhold'
alias auto='echo "sudo apt-mark auto app_name app_name" ; sudo apt-mark auto'
alias manu='echo "sudo apt-mark manual app_name app_name" ; sudo apt-mark manual'

05 Sep 15 | 16:34:37 ~
$ sho apt-listbugs
alias sho = aptitude show filename
Package: apt-listbugs
State: installed
Automatically installed: no
Version: 0.1.16
Priority: optional
Section: admin
Maintainer: Francesco Poli (wintermute) <invernomuto@paranoici.org>
Architecture: all
Uncompressed Size: 532 k
Depends: ruby | ruby-interpreter, ruby-debian (>= 0.3.3), apt (>= 0.9.11), ruby-gettext (>= 3.0.2),
ruby-xmlparser, ruby-soap4r, ruby-unicode
Recommends: ruby-httpclient (>= 2.1.5.2-1)
Suggests: reportbug, debianutils (>= 2.0) | www-browser | w3m
Breaks: libapt-pkg4.12 (< 0.9.11), libapt-pkg4.12 (< 0.9.11)
Description: tool which lists critical bugs before each APT installation
apt-listbugs is a tool which retrieves bug reports from the Debian Bug Tracking System and lists them.
Especially, it is intended to be invoked before each installation/upgrade by APT in order to check whether the
installation/upgrade is safe.
Many developers and users prefer the unstable version of Debian for its new features and packages. APT, the
usual upgrade tool, can break your system by installing a buggy package.
apt-listbugs lists critical bug reports from the Debian Bug Tracking System. Run it from within the APT
session, in order to see whether an installation or upgrade is known to be unsafe.
Homepage: http://alioth.debian.org/projects/apt-listbugs/

05 Sep 15 | 16:34:54 ~
$

Head_on_a_Stick · 2015-09-05 19:35:11

^ Looks fine but you should comment out the CDROM line -- is APT not throwing out error messages about that?

Be sure to use:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

Rather than the `aptitude` equivalent.
https://www.debian.org/doc/manuals/debi … de_literal
http://bugs.debian.org/411280

EDIT: Ninja'd by S11...

Fast typing there SecMod!

Sector11 · 2015-09-05 20:05:10

Head_on_a_Stick wrote:

EDIT: Ninja'd by S11...
Fast typing there SecMod!

Now that's a first in all my years of computing. feels ... ummm ... strange

paxmark1 · 2015-09-05 20:21:40

b.t.w. Sept 6 gcc++ hits testing should be smoother and shorter than it was in sid.

https://lists.debian.org/debian-devel/2 … 00148.html

https://lists.debian.org/debian-release … 00241.html

isosceles · 2015-09-05 23:06:11

Thanks for the tips. FYI the cdrom line is included in sources.list by default after an install from the alpha2 iso.

Head_on_a_Stick wrote:

^ Looks fine but you should comment out the CDROM line -- is APT not throwing out error messages about that?

Nope, hadn't heard any complaints from APT, and I haven't actually used the hypothetical stretch sources.list I posted. I feared the bork.

Sector11 wrote:

Be ready for borkage

At this point my system is well backed up because I just installed fresh. But, I have to say I wasn't expecting *too* much borkage beyond minor and temporary bugs, because my research had suggested it was oh so safe! Maybe I should hold off because I don't even know about the alias business you mentioned.

Maybe I should just deal with backports. I've avoided this because I never figured out how it works... for example, if I install a backported package from testing how do I prevent it from being reverted at apt-get upgrade? Or what if I want to revert to a stable version of a package; do I have to do something special? I worry about having to remember too much CLI syntax. Is managing backports actually really easy or should I just stick to safe and outdated stable packages? This issue is so important to me that I've considered switching to Ubuntu for some more current package access, but I really would rather stay with BL since it's so practical and beautiful. I probably could not pull the Ubuntu trigger.

EDIT: TL:DR: What's less hassle for a user who knows minimal command line and system stuff, the risks of stretch or managing backports?

Last edited by isosceles (2015-09-05 23:09:31)

Head_on_a_Stick · 2015-09-05 23:20:53

isosceles wrote:

backports

^ This.

In respect of b0rkage in Debian Testing it's not *if*, it's *when* -- if you don't want your system to be disrupted with gratuitous random breakage then use Debian Stable.

As paxmark1 points out, stretch is just about to transition to GCC version 5 -- it won't be as bad as it was in sid but there will still be trouble; mainly uninstallable packages but you could break your entire desktop if you accept a `dist-upgrade` without checking the output carefully.

Read the "Using Debian" link in my signature (recursively) to get an idea of the differences between the Debian versions.

isosceles · 2015-09-06 04:55:23

Head_on_a_Stick wrote:

isosceles wrote:
backports
^ This.
In respect of b0rkage...
Read the "Using Debian" link

I take your word for it. I'm sticking with stable and will research backports more.

CrunchBang Linux

SEARCH

#1 2015-09-05 19:24:21

[Solved] Sources list for Stretch?

#2 2015-09-05 19:33:35

Re: [Solved] Sources list for Stretch?

#3 2015-09-05 19:35:11

Re: [Solved] Sources list for Stretch?

#4 2015-09-05 20:05:10

Re: [Solved] Sources list for Stretch?

#5 2015-09-05 20:21:40

Re: [Solved] Sources list for Stretch?

#6 2015-09-05 23:06:11

Re: [Solved] Sources list for Stretch?

#7 2015-09-05 23:20:53

Re: [Solved] Sources list for Stretch?

#8 2015-09-06 04:55:23

Re: [Solved] Sources list for Stretch?

Board footer