Re: 7->8: inexplicable difficulty discovering available package versions
On 04/02/17 07:30, David Christensen wrote: On 02/03/17 11:04, Felix Miata wrote: I just did an apt-get dist-upgrade to reach Jessie 8.7 from Wheezy. I am of the opinion that attempting an in-place major version upgrade of an operating system or a service is folly. Perhaps - and yet, one of the requirements for Debian packages is that you should be able to do in-place upgrades in reasonable safety, and that if there are any substantial caveats to such an action when going from oldstable to stable, they need to be documented in the release notes.
Re: 7->8: inexplicable difficulty discovering available package versions
On 04-02-2017 05:30, David Christensen wrote: > I am of the opinion that attempting an in-place major version upgrade > of an operating system or a service is folly. The only reliable > method is to do a fresh install on another computer, and then migrate. Whatever works for you. But keep in mind that debian does support in place upgrades and offers support for that. I and many others have done that successfully several times. -- What one fool can do, another can. -- Ancient Simian Proverb Eduardo M KALINOWSKI edua...@kalinowski.com.br
Re: 7->8: inexplicable difficulty discovering available package versions
David Christensen composed on 2017-02-03 23:30 (UTC-0800): Felix Miata wrote: I just did an apt-get dist-upgrade to reach Jessie 8.7 from Wheezy. I am of the opinion that attempting an in-place major version upgrade of an operating system or a service is folly. The only reliable method is to do a fresh install on another computer, and then migrate. That sounds pretty much the opposite of the recommended installation method forSid - install prior release or unstable, then upgrade it to Sid. This means you need at least three computers -- one that you are migrating off, one that you are migrating onto, and one (or more) for everything else you need to keep operational while you do the migration. Mobile racks and spare drives will help immensely. I have lots of functioning computers, and a fair sized stash of extra HDs. All except one machine are multiboot. Installations average >10 per machine. I find upgrades are generally less painful that all the re-customization that fresh installs entail (especially when Zypper is the available upgrade tool). Clone partition, apply new UUID and label, reconfigure bootloader, fstab and sources, then upgrade. If there's a major malfunction, just re-clone and start over, not that big a deal. YMMV. :-D -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: 7->8: inexplicable difficulty discovering available package versions
On 02/03/17 11:04, Felix Miata wrote: I just did an apt-get dist-upgrade to reach Jessie 8.7 from Wheezy. I am of the opinion that attempting an in-place major version upgrade of an operating system or a service is folly. The only reliable method is to do a fresh install on another computer, and then migrate. This means you need at least three computers -- one that you are migrating off, one that you are migrating onto, and one (or more) for everything else you need to keep operational while you do the migration. Mobile racks and spare drives will help immensely. David
Re: 7->8: inexplicable difficulty discovering available package versions
Sven Joachim composed on 2017-02-03 20:54 (UTC+0100): Thank you for your response! On 2017-02-03 14:04 -0500, Felix Miata wrote: I just did an apt-get dist-upgrade to reach Jessie 8.7 from Wheezy. It's still using 3.16 kernel and Xorg server 1.12.4. apt-cache search linux-image shows me the various kernel versions to choose from backports, but apt-cache search xserver-xorg-core produces a short list with no versions. What am I doing wrong to not have been upgraded to Jessie's Xorg server version, and why doesn't apt-cache search give any version info? My hunch is that you don't actually have an entry for jessie in your sources.list, but only one for jessie-backports. That is not going to work well. String heezy is totally absent from it: deb http://mirrors.kernel.org/debian/ jessie main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb http://mirrors.kernel.org/debian/ jessie-updates main contrib non-free deb http://httpredir.debian.org/debian jessie-backports main contrib non-free deb http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14 deb-src http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14 Also, apt-get update produces a BADSIG GPG error for jessie-backports. How does one go about cleaning that up? Does this still happen after upgrading the debian-archive-keyring to the jessie version? I fixed GPG and Xorg version problems by simply doing 'aptitude dist-upgrade'. :-p I still am vexed by attempts to discover versions of packages available from repos. :-( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: 7->8: inexplicable difficulty discovering available package versions
On 2017-02-03 14:04 -0500, Felix Miata wrote: > I just did an apt-get dist-upgrade to reach Jessie 8.7 from > Wheezy. It's still using 3.16 kernel and Xorg server 1.12.4. apt-cache > search linux-image shows me the various kernel versions to choose from > backports, but apt-cache search xserver-xorg-core produces a short > list with no versions. What am I doing wrong to not have been upgraded > to Jessie's Xorg server version, and why doesn't apt-cache search give > any version info? My hunch is that you don't actually have an entry for jessie in your sources.list, but only one for jessie-backports. That is not going to work well. > Also, apt-get update produces a BADSIG GPG error for > jessie-backports. How does one go about cleaning that up? Does this still happen after upgrading the debian-archive-keyring to the jessie version? Cheers, Sven
7->8: inexplicable difficulty discovering available package versions
I just did an apt-get dist-upgrade to reach Jessie 8.7 from Wheezy. It's still using 3.16 kernel and Xorg server 1.12.4. apt-cache search linux-image shows me the various kernel versions to choose from backports, but apt-cache search xserver-xorg-core produces a short list with no versions. What am I doing wrong to not have been upgraded to Jessie's Xorg server version, and why doesn't apt-cache search give any version info? Also, apt-get update produces a BADSIG GPG error for jessie-backports. How does one go about cleaning that up? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ /etc/apt/trusted.gpg pub 4096R/F5CFC95C 2014-06-08 uid QuickBuild Trinity Desktop Environment pub 1024D/6BF18B15 2000-08-08 uid Leo Molluid [jpeg image of size 7696] uid Leo Moll uid Leo Moll uid Leo Moll uid Leo Moll uid [jpeg image of size 3113] uid [jpeg image of size 3267] sub 3072g/80DA337D 2000-08-08 pub 4096R/A04BE668 2014-06-21 uid Slávek Banko uid Slavek Banko uid Miloslav Banko sub 4096R/D3FD324D 2014-06-21 /etc/apt/trusted.gpg.d//debian-archive-jessie-automatic.gpg --- pub 4096R/2B90D010 2014-11-21 [expires: 2022-11-19] uid Debian Archive Automatic Signing Key (8/jessie) /etc/apt/trusted.gpg.d//debian-archive-jessie-security-automatic.gpg pub 4096R/C857C906 2014-11-21 [expires: 2022-11-19] uid Debian Security Archive Automatic Signing Key (8/jessie) /etc/apt/trusted.gpg.d//debian-archive-jessie-stable.gpg pub 4096R/518E17E1 2013-08-17 [expires: 2021-08-15] uid Jessie Stable Release Key /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg pub 4096R/473041FA 2010-08-27 [expires: 2018-03-05] uid Debian Archive Automatic Signing Key (6.0/squeeze) /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg - pub 4096R/B98321F9 2010-08-07 [expires: 2017-08-05] uid Squeeze Stable Release Key /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --- pub 4096R/46925553 2012-04-27 [expires: 2020-04-25] uid Debian Archive Automatic Signing Key (7.0/wheezy) /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg pub 4096R/65FFB764 2012-05-08 [expires: 2019-05-07] uid Wheezy Stable Release Key System:Host: big31 Kernel: 3.16.0-0.bpo.4-amd64 x86_64 (64 bit) Console: tty 3 Distro: Debian GNU/Linux 8 Machine: Mobo: TAR model: G31-M7 TE Bios: American Megatrends v: 080014 date: 02/01/2010 CPU: Dual core Intel Core2 Duo E7600 (-MCP-) cache: 3072 KB Clock Speeds: 1: 3053 MHz 2: 3053 MHz Graphics: Card: NVIDIA GT218 [GeForce 210] Display Server: X.org 1.12.4 driver: nouveau tty size: 180x56 Advanced Data: N/A for root out of X Audio: Card-1 Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel Card-2 NVIDIA High Definition Audio Controller driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k3.16.0-0.bpo.4-amd64 Network: Card: Realtek RTL8169 PCI Gigabit Ethernet Controller driver: r8169 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:0a:cd:26:d3:8d Drives:HDD Total Size: 500.1GB (4.9% used) ID-1: /dev/sda model: Hitachi_HCS5C105 size: 500.1GB Partition: ID-1: / size: 5.4G used: 2.1G (41%) fs: ext4 dev: /dev/sda15 ID-2: /home size: 4.3G used: 875M (21%) fs: ext3 dev: /dev/sda9 ID-3: swap-1 size: 2.17GB used: 0.00GB (0%) fs: swap dev: /dev/sda7 Sensors: None detected - is lm-sensors installed and configured? Repos: Active apt sources in file: /etc/apt/sources.list deb http://mirrors.kernel.org/debian/ jessie main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb