Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #275085
| From | Richard Owlett <rowlett@access.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Synaptic problem(s) |
| Date | 2024-12-01 11:50 +0100 |
| Message-ID | <JOPGy-cYeN-9@gated-at.bofh.it> (permalink) |
| References | <JNNdL-celA-7@gated-at.bofh.it> <JOe4h-cy2G-21@gated-at.bofh.it> <JOtG1-cKIZ-1@gated-at.bofh.it> <JOwXf-cMz8-17@gated-at.bofh.it> <JOxgB-cMV9-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 11/30/24 9:00 AM, Greg Wooledge wrote: > On Sat, Nov 30, 2024 at 14:45:01 +0000, Joe wrote: >> I don't know if it helps, but the current ghostscript on my Deb 12 is >> version 12u6, not 12u5. >> >> What happens when you try: >> >> apt upgrade ghostscript > > "apt upgrade" does not take a package name as an argument. It tries > to upgrade *all* of the packages you have. > > To upgrade a single package, use "install" instead. > > apt update > apt install ghostscript > > However, in Richard's case, the package is in state iU (Unpacked), > which indicates that something failed during the installation, > around the Unpacking step. > > The first thing I would've checked is "df". Make sure there are no > file systems running out of space. > > If the file systems were fine, then I would've done > > dpkg --configure -a > > to retry whatever failed during or after the Unpacking step. If > that fails, then you should see a message telling you why. Reporting > that message would be an important detail when bringing the issue to > the mailing list. > > If that command does nothing at all (because the package isn't ready > for configuration), then I might try removing it, or I might try > "apt update; apt install ghostscript" depending on which one I feel is > more likely to work at that moment. > > In terminal mode as root I did "apt update" which concluded:= > Fetched 62.1 MB in 30s (2,070 kB/s) > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > 77 packages can be upgraded. Run 'apt list --upgradable' to see them. > N: Repository 'http://deb.debian.org/debian bookworm InRelease' changed its 'Version' value from '12.7' to '12.8' also > root@debian12:/home/richard# df > Filesystem 1K-blocks Used Available Use% Mounted on > udev 1899716 0 1899716 0% /dev > tmpfs 386696 1540 385156 1% /run > /dev/sda9 23315280 14930176 7175404 68% / > tmpfs 1933464 488 1932976 1% /dev/shm > tmpfs 5120 8 5112 1% /run/lock > /dev/sda6 14348168 24 13597456 1% /Bible > /dev/sda8 65873764 53583092 8918864 86% /Deb9Home > tmpfs 386692 72 386620 1% /run/user/1000 Then > root@debian12:/home/richard# apt --fix-broken install > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Correcting dependencies... Done > The following additional packages will be installed: > ghostscript libgs10 libgs10-common > The following packages will be upgraded: > ghostscript libgs10 libgs10-common > 3 upgraded, 0 newly installed, 0 to remove and 74 not upgraded. > 1 not fully installed or removed. > Need to get 3,111 kB of archives. > After this operation, 0 B of additional disk space will be used. > Do you want to continue? [Y/n] y > Get:1 http://security.debian.org/debian-security bookworm-security/main amd64 ghostscript amd64 10.0.0~dfsg-11+deb12u6 [57.5 kB] > Get:2 http://security.debian.org/debian-security bookworm-security/main amd64 libgs10 amd64 10.0.0~dfsg-11+deb12u6 [2,467 kB] > Get:3 http://security.debian.org/debian-security bookworm-security/main amd64 libgs10-common all 10.0.0~dfsg-11+deb12u6 [587 kB] > Fetched 3,111 kB in 1s (2,268 kB/s) > Reading changelogs... Done > (Reading database ... 180583 files and directories currently installed.) > Preparing to unpack .../ghostscript_10.0.0~dfsg-11+deb12u6_amd64.deb ... > Unpacking ghostscript (10.0.0~dfsg-11+deb12u6) over (10.0.0~dfsg-11+deb12u5) ... > Preparing to unpack .../libgs10_10.0.0~dfsg-11+deb12u6_amd64.deb ... > Unpacking libgs10:amd64 (10.0.0~dfsg-11+deb12u6) over (10.0.0~dfsg-11+deb12u4) ... > Preparing to unpack .../libgs10-common_10.0.0~dfsg-11+deb12u6_all.deb ... > Unpacking libgs10-common (10.0.0~dfsg-11+deb12u6) over (10.0.0~dfsg-11+deb12u4) ... > Setting up libgs10-common (10.0.0~dfsg-11+deb12u6) ... > Setting up libgs10:amd64 (10.0.0~dfsg-11+deb12u6) ... > Setting up ghostscript (10.0.0~dfsg-11+deb12u6) ... > Processing triggers for libc-bin (2.36-9+deb12u8) ... > Processing triggers for man-db (2.11.2-2) ... > root@debian12:/home/richard# All seems well so far. "dpkg -l | grep -v '^ii ' " reported no problems. Closed terminal and launched Synaptic. No errors *OR* warnings :} Thanks to all. What should I do next ( /etc/debian_version reports 12.7)?
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Synaptic problem(s) Richard Owlett <rowlett@access.net> - 2024-11-28 15:00 +0100
Re: Synaptic problem(s) "Andrew M.A. Cater" <amacater@einval.com> - 2024-11-28 20:10 +0100
Re: Synaptic problem(s) David Wright <deblis@lionunicorn.co.uk> - 2024-11-29 19:40 +0100
Re: Synaptic problem(s) Joe <joe@jretrading.com> - 2024-11-29 20:40 +0100
Re: Synaptic problem(s) Richard Owlett <rowlett@access.net> - 2024-11-30 12:20 +0100
Re: Synaptic problem(s) Joe <joe@jretrading.com> - 2024-11-30 15:50 +0100
Re: Synaptic problem(s) Greg Wooledge <greg@wooledge.org> - 2024-11-30 16:10 +0100
Re: Synaptic problem(s) Joe <joe@jretrading.com> - 2024-11-30 17:20 +0100
Re: Synaptic problem(s) Richard Owlett <rowlett@access.net> - 2024-12-01 11:50 +0100
Re: Synaptic problem(s) "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-01 13:20 +0100
Re: Synaptic problem(s) Richard Owlett <rowlett@access.net> - 2024-12-02 14:10 +0100
csiph-web