Bug#406137: ssh: upgrade causes etch dpkg to segv
severity 406137 important
thanks
On Tue, Jan 09, 2007 at 07:03:24AM +0000, Colin Watson wrote:
> tags 406137 moreinfo
> thanks
>
> On Mon, Jan 08, 2007 at 07:46:40PM -0500, Justin Pryzby wrote:
> > Package: ssh
> > Severity: grave
> > Version: 1:4.3p2-8
> >
> > pryzbyj@cetus:~$ fg
> > sudo apt-get dist-upgrade
> > Preparing to replace libtorrent9 0.10.2-1 (using .../libtorrent9_0.10.4-1_i386.deb) ...
> > Unpacking replacement libtorrent9 ...
> > Preparing to replace lm-sensors 1:2.10.0-9 (using .../lm-sensors_1%3a2.10.1-2_i386.deb) ...
> > Unpacking replacement lm-sensors ...
> > Preparing to replace pbuilder 0.159 (using .../pbuilder_0.161_all.deb) ...
> > Unpacking replacement pbuilder ...
> > Preparing to replace qiv 2.0-4.2 (using .../archives/qiv_2.0-7_i386.deb) ...
> > Unpacking replacement qiv ...
> > Preparing to replace rtorrent 0.6.2-2 (using .../rtorrent_0.6.4-1_i386.deb) ...
> > Unpacking replacement rtorrent ...
> > Preparing to replace ssh 1:4.3p2-4 (using .../ssh_1%3a4.3p2-8_all.deb) ...
> > Unpacking replacement ssh ...
> > Segmentation fault
>
> I have no hope of debugging this without further detail.
I don't know what to try; I had both openssh-{client,server}
installed, in addition to ssh. ssh was configured later when I
installed "gv", perphaps after -{client,server} were configured,
without any problem. I downgraded then upgraded ssh, again without
problem.
> There is no
> indication here that it is dpkg that's segfaulting;
Indeed, it looks as likely to have been apt (sudo apt-get
dist-upgrade). I said dpkg since I was of the (apparently mistaken)
impression that ssh twiddled maintscripts and not just conffiles (like
base-files.postinst and man-db.preinst).
> it could be
> something called from a maintainer script.
That shouldn't cause dpkg (or apt) to segv.
> Unless you can dig into this
> I will downgrade the bug soon.
I'm doing it now, as I suspect this is actually the 17th twin of
#81829.
APT people: feel free to close this bug if it adds no information not
found in the first 17 instances, or
severity 406137 normal
reassign 406137 apt
merge 81829 406137
thanks
if it does.
Justin
Reply to: