On Tue, 3 Aug 2021 13:32:40 -0400, Hendrik wrote in message
<20210803173240.qrlp2elbnda6cwee@???>:

> On Tue, Aug 03, 2021 at 06:13:15PM +0200, Arnt Karlsen wrote:
> > On Tue, 3 Aug 2021 10:05:39 -0400, Hendrik wrote in message
> > <20210803140539.4kor7lhfljf7to7b@???>:
> >

> > > On Tue, Aug 03, 2021 at 02:33:08PM +0200, Arnt Karlsen wrote:  
> > > > On Tue, 3 Aug 2021 06:49:33 -0400, Hendrik wrote in message 
> > > > <20210803104933.5ics6nomqyctr6kr@???>:    

> > > > >

> > > > > (I wasn't worried about postgresql failing; as far as I know,
> > > > > I don't use it.)    

> > > >

> > > > ..you probably use(d) some service built upon it and/or some
> > > > front end of it.  Welcome to the club. ;o)    

> > >
> > > Still not worried. If there is such a service, I can sort it out
> > > later; perhaps with the instructions I got long ago during the
> > > upgrade for migrating data bases to the new version.
> > >
> > > What does worry me is that the upgrade froze while /var/lib/dpkg
> > > is locked, and I cannot resume it.
> >
> > ..is it hung dead, or can you kill it?
> > If you kill it, kill everything else that needs dpkg etc
> > lock files, before you remove those lock files.
> > Once they are gone, you should be able to resume your
> > upgrade with your standard tricks.
> >
> > > I need to know how to resume the upgrade and get to the end.
> >
> > ..tried apt-get's --fix-broken (or -f ) option?
> > Or dpkg --configure -a ?
>
> These did most of the work.
>
> Turns out I hadn't killd all the processes involved in relevant locks.
> Discovered lslocks by a google search. Good I had another computer
> to use for this.
>
> After this I apt-get --fix-broken told me to dpkg --configure -a
> After that, I could resume upgrading using apt-get.
>
> this time it succeeded in stopping ans starting postgres.

..2 options, throw in an "exit 0" line in the offending install(?)
script and fix postgresql later, or carry on your agony your way.

..my occational workaround, is cheat out apt (or dpkg), adding
an "exit 0" line below any line acting up in any of the relevant
control-the-package script in /var/lib/dpkg/info/$PACKAGENAME.*,
for e.g. zsh, those are: root@d44:~# ll /var/lib/dpkg/info/zsh.*
-rw-r--r-- 1 root root 2569 Apr 27 2020 /var/lib/dpkg/info/zsh.list
-rw-r--r-- 1 root root 3483 Feb 5 2019 /var/lib/dpkg/info/zsh.md5sums
-rwxr-xr-x 1 root root 949 Feb 5 2019 /var/lib/dpkg/info/zsh.postinst
-rwxr-xr-x 1 root root 356 Feb 5 2019 /var/lib/dpkg/info/zsh.postrm
-rwxr-xr-x 1 root root 178 Feb 5 2019 /var/lib/dpkg/info/zsh.preinst
-rwxr-xr-x 1 root root 178 Feb 5 2019 /var/lib/dpkg/info/zsh.prerm

..easier, and disappears on the next upgrade. ;o)

--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.