On 2020-01-15 20:55, David Christensen wrote:
On 2020-01-15 12:28, David Christensen wrote:
Do I build from source? If so, is there a good tutorial?
https://wiki.debian.org/SimpleBackportCreation
The tutorial says "Add sid to your sources.list". So, I added the
following lines to /etc/apt/sources.list:
deb http://ftp.us.debian.org/debian/ sid main
deb-src http://ftp.us.debian.org/debian/ sid main
Today, having completely forgotten about the backport, I ran 'apt-get
update' and 'apt-get upgrade'.
'apt-get update' produced more output that usual.
'apt-get upgrade' wanted to download and install 800+ packages. When I
approved, it failed:
<snip>
Errors were encountered while processing:
/tmp/apt-dpkg-install-ke7tUq/128-cryptsetup_2%3a2.2.2-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
So, I ran 'apt-get upgrade' again -- fewer packages, but same result:
<snip>
Reading changelogs... Done
Preconfiguring packages ...
Setting up systemd-sysv (244.1-2) ...
(Reading database ... 119008 files and directories currently
installed.)
Preparing to unpack .../cryptsetup_2%3a2.2.2-2_amd64.deb ...
Unpacking cryptsetup (2:2.2.2-2) over (2:1.7.3-4) ...
dpkg: error processing archive
/var/cache/apt/archives/cryptsetup_2%3a2.2.2-2_amd64.deb (--unpack):
trying to overwrite '/usr/sbin/luksformat', which is also in
package cryptsetup-bin 2:1.7.3-4
dpkg-deb: error: subprocess paste was killed by signal (Broken
pipe)
Errors were encountered while processing:
/var/cache/apt/archives/cryptsetup_2%3a2.2.2-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Then I remember the backport.
Rather than troubleshoot this mess, I re-imaged the drive to an image
taken prior to build the backport. 'apt-get update' and 'apt-get
upgrade' then worked as expected.
So, beware of adding things to your /etc/apt/sources.list -- you may be
in for unwelcome surprises the next time you update/ upgrade.
And, take images of your system drives regularly.
David
