Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #200314 > unrolled thread
| Started by | Default User <hunguponcontent@gmail.com> |
|---|---|
| First post | 2018-09-20 03:00 +0200 |
| Last post | 2018-09-20 10:10 +0200 |
| Articles | 12 — 6 participants |
Back to article view | Back to linux.debian.user
Unstable update ridiculousness Default User <hunguponcontent@gmail.com> - 2018-09-20 03:00 +0200
Re: Unstable update ridiculousness John Hasler <jhasler@newsguy.com> - 2018-09-20 03:10 +0200
Re: Unstable update ridiculousness Default User <hunguponcontent@gmail.com> - 2018-09-20 03:20 +0200
Re: Unstable update ridiculousness didier gaumet <didier.gaumet@gmail.com> - 2018-09-20 09:10 +0200
Re: Unstable update ridiculousness John Hasler <jhasler@newsguy.com> - 2018-09-20 15:20 +0200
Re: Unstable update ridiculousness Roberto C. Sánchez <roberto@debian.org> - 2018-09-20 15:50 +0200
Re: Unstable update ridiculousness Default User <hunguponcontent@gmail.com> - 2018-09-20 22:00 +0200
Re: Unstable update ridiculousness Ben Caradoc-Davies <ben@transient.nz> - 2018-09-21 00:40 +0200
Re: Unstable update ridiculousness Default User <hunguponcontent@gmail.com> - 2018-09-21 07:10 +0200
Re: Unstable update ridiculousness Joe <joe@jretrading.com> - 2018-09-20 10:00 +0200
Re: Unstable update ridiculousness Ben Caradoc-Davies <ben@transient.nz> - 2018-09-20 03:30 +0200
Re: Unstable update ridiculousness Joe <joe@jretrading.com> - 2018-09-20 10:10 +0200
| From | Default User <hunguponcontent@gmail.com> |
|---|---|
| Date | 2018-09-20 03:00 +0200 |
| Subject | Unstable update ridiculousness |
| Message-ID | <wzVu1-5jO-9@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hey guys, running Debian Unstable.
This is ridiculous:
-------------------------------------------------------------------------------------------
user@user:~$ sudo aptitude -Pvv update
[sudo] password for user:
Get: 1 http://ftp.us.debian.org/debian unstable InRelease [233 kB]
Get: 2 http://ftp.us.debian.org/debian unstable/main Sources.diff/Index
[27.9 kB]
Get: 3 http://ftp.us.debian.org/debian unstable/non-free Sources.diff/Index
[27.8 kB]
Get: 4 http://ftp.us.debian.org/debian unstable/main amd64
Packages.diff/Index [27.9 kB]
Get: 5 http://ftp.us.debian.org/debian unstable/main
Translation-en.diff/Index [27.9 kB]
Get: 6 http://ftp.us.debian.org/debian unstable/non-free
Translation-en.diff/Index [27.8 kB]
Get: 7 http://ftp.us.debian.org/debian unstable/main Sources
2018-09-19-2009.06.pdiff [8,517 B]
Get: 8 http://ftp.us.debian.org/debian unstable/non-free Sources
2018-09-19-2009.06.pdiff [1,611 B]
Get: 9 http://ftp.us.debian.org/debian unstable/main amd64 Packages
2018-09-19-2009.06.pdiff [20.5 kB]
Get: 10 http://ftp.us.debian.org/debian unstable/main Sources
2018-09-19-2009.06.pdiff [8,517 B]
Get: 11 http://ftp.us.debian.org/debian unstable/non-free Sources
2018-09-19-2009.06.pdiff [1,611 B]
Get: 12 http://ftp.us.debian.org/debian unstable/main Translation-en
2018-09-19-2009.06.pdiff [1,785 B]
Get: 13 http://ftp.us.debian.org/debian unstable/main Translation-en
2018-09-19-2009.06.pdiff [1,785 B]
Get: 14 http://ftp.us.debian.org/debian unstable/main amd64 Packages
2018-09-19-2009.06.pdiff [20.5 kB]
Get: 15 http://ftp.us.debian.org/debian unstable/non-free Translation-en
2018-09-19-2009.06.pdiff [5,547 B]
Get: 16 http://ftp.us.debian.org/debian unstable/non-free Translation-en
2018-09-19-2009.06.pdiff [5,547 B]
Fetched 410 kB in 3s (119 kB/s)
Current status: 0 (+0) broken, 182 (+4) upgradable, 59310 (+23) new.
user@user:~$ sudo aptitude -Pvv safe-upgrade
Resolving dependencies...
The following NEW packages will be installed:
libunwind8{a}
The following packages will be REMOVED:
libwayland-egl1-mesa{u}
The following packages will be upgraded:
adduser apt apt-transport-https apt-utils at-spi2-core binutils
binutils-common
binutils-x86-64-linux-gnu chromium chromium-common colord colord-data
cpp-8 emacsen-common
fonts-opensymbol foomatic-db-compressed-ppds gawk gcc-8-base ghostscript
gir1.2-atspi-2.0
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-gdkpixbuf-2.0
gir1.2-gst-plugins-base-1.0
gir1.2-gstreamer-1.0 gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0
gnome-sushi gstreamer1.0-gl
gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-base
gstreamer1.0-plugins-good
gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio gstreamer1.0-x hplip
hplip-data libaprutil1
libaprutil1-dbd-sqlite3 libaprutil1-ldap libapt-inst2.0 libapt-pkg5.0
libarchive-zip-perl
libatk-adaptor libatk-bridge2.0-0 libatomic1 libatspi2.0-0
libbasicusageenvironment1 libbinutils
libboost-chrono1.62.0 libboost-date-time1.62.0 libboost-filesystem1.62.0
libboost-iostreams1.62.0
libboost-locale1.62.0 libboost-regex1.62.0 libboost-system1.62.0
libboost-thread1.62.0
libcogl-common libcogl-pango20 libcogl-path20 libcogl20 libcolord2
libcolorhug2 libdom4j-java
libepoxy0 libgcc1 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin
libgdk-pixbuf2.0-common libgfortran5
libglib2.0-0 libglib2.0-bin libglib2.0-data libgnutls30 libgomp1
libgpod-common libgpod4
libgroupsock8 libgs9 libgs9-common libgstreamer-gl1.0-0
libgstreamer-plugins-bad1.0-0
libgstreamer-plugins-base1.0-0 libgstreamer1.0-0 libgupnp-1.0-4 libhpmud0
libio-socket-ssl-perl
libiw30 libjavascriptcoregtk-4.0-18 libjbig2dec0 liblivemedia64
libllvm6.0 liblouis-data
liblouis16 libnautilus-extension1a libnewt0.52 libplist3
libpulse-mainloop-glib0 libpulse0
libpulsedsp libquadmath0 libreoffice
libreoffice-avmedia-backend-gstreamer libreoffice-base
libreoffice-base-core libreoffice-base-drivers libreoffice-calc
libreoffice-common
libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
libreoffice-help-common
libreoffice-help-en-us libreoffice-impress libreoffice-java-common
libreoffice-librelogo
libreoffice-math libreoffice-nlpsolver libreoffice-ogltrans
libreoffice-report-builder
libreoffice-report-builder-bin libreoffice-script-provider-bsh
libreoffice-script-provider-js
libreoffice-script-provider-python libreoffice-sdbc-firebird
libreoffice-sdbc-hsqldb
libreoffice-sdbc-postgresql libreoffice-style-colibre
libreoffice-style-elementary
libreoffice-style-tango libreoffice-wiki-publisher libreoffice-writer
libsane-hpaio
libsdl1.2debian libsdl2-2.0-0 libsgutils2-2 libsqlite3-0 libstdc++6
libtdb1 libtevent0
libtracker-sparql-2.0-0 libusageenvironment3 libwebkit2gtk-4.0-37 lintian
linux-image-4.18.0-1-amd64 nano nautilus nautilus-data openprinting-ppds
printer-driver-hpcups
printer-driver-hpijs printer-driver-postscript-hp pulseaudio
pulseaudio-module-bluetooth
pulseaudio-utils python-gi python-gi-cairo python-lxml python-newt
python3-gi python3-gi-cairo
python3-louis python3-olefile python3-pyatspi python3-uno rsyslog
ruby-unf-ext sqlite3 uno-libs3
ure wget whiptail wireless-tools xserver-common xserver-xorg-core
xserver-xorg-legacy
xserver-xorg-video-amdgpu xserver-xorg-video-ati
xserver-xorg-video-radeon youtube-dl
182 packages upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 13.4 MB/324 MB of archives. After unpacking 7,926 kB will be
used.
Do you want to continue? [Y/n/?]
Get: 1 http://ftp.us.debian.org/debian unstable/main amd64
binutils-x86-64-linux-gnu amd64 2.31.1-6 [1,823 kB]
Get: 2 http://ftp.us.debian.org/debian unstable/main amd64 binutils-common
amd64 2.31.1-6 [2,071 kB]
Get: 3 http://ftp.us.debian.org/debian unstable/main amd64 binutils amd64
2.31.1-6 [55.9 kB]
Get: 4 http://ftp.us.debian.org/debian unstable/main amd64 libbinutils
amd64 2.31.1-6 [479 kB]
Get: 5 http://ftp.us.debian.org/debian unstable/main amd64
libgstreamer-plugins-base1.0-0 amd64 1.14.3-2 [1,935 kB]
Get: 6 http://ftp.us.debian.org/debian unstable/main amd64
libgstreamer-gl1.0-0 amd64 1.14.3-2 [1,353 kB]
Get: 7 http://ftp.us.debian.org/debian unstable/main amd64
gir1.2-gst-plugins-base-1.0 amd64 1.14.3-2 [1,287 kB]
Get: 8 http://ftp.us.debian.org/debian unstable/main amd64 gstreamer1.0-gl
amd64 1.14.3-2 [1,288 kB]
Get: 9 http://ftp.us.debian.org/debian unstable/main amd64
gstreamer1.0-plugins-base amd64 1.14.3-2 [1,790 kB]
Get: 10 http://ftp.us.debian.org/debian unstable/main amd64 gstreamer1.0-x
amd64 1.14.3-2 [1,278 kB]
Fetched 13.4 MB in 7s (1,921 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of libtracker-sparql-2.0-0 (2.0.3-3 → 2.1.4-1) <Outstanding>
b1 - #908800 - nautilus: can't use nautilus without tracker
serious bugs of apt (1.6.4 → 1.7.0~rc1) <Outstanding>
b2 - #909155 - apt-cache show multiple packages produces invalid output
serious bugs of colord (1.3.3-2 → 1.4.3-3) <Outstanding>
b3 - #908735 - colord: need to build-depend on argyll
Summary:
apt(1 bug), colord(1 bug), libtracker-sparql-2.0-0(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] n
**********************************************************************
****** Exiting with an error in order to stop the installation. ******
**********************************************************************
E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (10)
E: Failure running script /usr/sbin/apt-listbugs apt
Current status: 0 (+0) broken, 182 (+0) upgradable, 59310 (+0) new.
user@user:~$
------------------------------------------------------------------------------------------
3 bugs - 1 grave, 2 serious - in 3 packages. Holds up 182 packages total,
with no end in sight, according to the bug reports.
WTF?
And one of the packages being held up is a new kernel version! How can a
bug in another package hold up upgrading the kernel?
So, is there any way to upgrade some, or any of the packages being held up?
Even just the kernel?
At this rate, the soon there will be so many packages backed up that the
upgrade mechanism will choke, requiring a fresh install.
<anger>"Grrrr . . . "</anger>
[toc] | [next] | [standalone]
| From | John Hasler <jhasler@newsguy.com> |
|---|---|
| Date | 2018-09-20 03:10 +0200 |
| Message-ID | <wzVDH-5Ca-3@gated-at.bofh.it> |
| In reply to | #200314 |
You are running Unstable. It can be like that. -- John Hasler jhasler@newsguy.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Default User <hunguponcontent@gmail.com> |
|---|---|
| Date | 2018-09-20 03:20 +0200 |
| Message-ID | <wzVNn-5F3-3@gated-at.bofh.it> |
| In reply to | #200315 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, Sep 19, 2018 at 9:05 PM John Hasler <jhasler@newsguy.com> wrote: > You are running Unstable. It can be like that. > -- > John Hasler > jhasler@newsguy.com > Elmwood, WI USA > > 182 packages?
[toc] | [prev] | [next] | [standalone]
| From | didier gaumet <didier.gaumet@gmail.com> |
|---|---|
| Date | 2018-09-20 09:10 +0200 |
| Message-ID | <wA1g5-xf-3@gated-at.bofh.it> |
| In reply to | #200316 |
Le 20/09/2018 à 03:16, Default User a écrit :
> 182 packages?
from https://www.debian.org/releases/sid/ :
"The unstable distribution ("sid")
The code name for Debian's development distribution is "sid", aliased to
"unstable". Most of the development work that is done in Debian, is
uploaded to this distribution. This distribution will never get
released; instead, packages from it will propagate into testing and then
into a real release.
Please note that security updates for "unstable" distribution are not
managed by the security team. Hence, "unstable" does not get security
updates in a timely manner. For more information please see the Security
Team's FAQ.
"sid" is subject to massive changes and in-place library updates. This
can result in a very "unstable" system which contains packages that
cannot be installed due to missing libraries, dependencies that cannot
be fulfilled etc. Use it at your own risk!"
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <jhasler@newsguy.com> |
|---|---|
| Date | 2018-09-20 15:20 +0200 |
| Message-ID | <wA72a-3Ro-5@gated-at.bofh.it> |
| In reply to | #200326 |
didier gaumet writes: > Please note that security updates for "unstable" distribution are not > managed by the security team. Hence, "unstable" does not get security > updates in a timely manner. There is no promise of security updates to Unstable but in practice the developers upload fixes quite promptly. -- John Hasler jhasler@newsguy.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Roberto C. Sánchez <roberto@debian.org> |
|---|---|
| Date | 2018-09-20 15:50 +0200 |
| Message-ID | <wA7vb-40B-1@gated-at.bofh.it> |
| In reply to | #200335 |
On Thu, Sep 20, 2018 at 08:17:51AM -0500, John Hasler wrote: > didier gaumet writes: > > Please note that security updates for "unstable" distribution are not > > managed by the security team. Hence, "unstable" does not get security > > updates in a timely manner. > > There is no promise of security updates to Unstable but in practice the > developers upload fixes quite promptly. To be clear, *targeted* security fixes to unstable are exceptionally uncommon. What usually happens is that new upstream releases that fix security issues tend to be uploaded to unstable. This sometimes happens promptly and at other times can come with significant delay. The reason for the distinction of the targeted security fixes is that upstream may fix a reported security issue in their development repository, but it may be some weeks or months before a new upstream release is made with the fix. There are occasions where the package maintainer may cherry-pick the relevant commit(s), as is done for stable security updates. However, this is not the norm. Some upstreams actually make an effort to obfuscate which commits fix which security vulnerabilities, which makes the matter even more challenging. The point is that those who rely on timely security fixes should look elsewhere than unstable and testing. Regards, -Roberto -- Roberto C. Sánchez
[toc] | [prev] | [next] | [standalone]
| From | Default User <hunguponcontent@gmail.com> |
|---|---|
| Date | 2018-09-20 22:00 +0200 |
| Message-ID | <wAdhf-7k3-7@gated-at.bofh.it> |
| In reply to | #200337 |
[Multipart message — attachments visible in raw view] — view raw
> > > Hi guys. Thank you for your replies. Please note that I am really not familiar with either cron or (especially) with package pinning. Using advice given, using apt-listings and aptitude full-update, l was able to update everything except the 3 packages in question, which are now "pinned", with a priority of 3000. I do have both cron and anacron installed, but have never used or done anything to configure them. Note: the computer in question is not on 24/7, but is normally on part of every day. Thus anacron, per the apt-listbugs man page. If I understand correctly, a cron job has been created automatically, which will check each day automatically, and automatically in-pin the packages in question when they are eligible for upgrade. Is this correct? If not, will I have to manually delete the cron job in question and/or manually edit/delete the package pinning, once the packages in question have been upgraded? Finally, how can I verify that said cron job was created and enabled (correctly)?
[toc] | [prev] | [next] | [standalone]
| From | Ben Caradoc-Davies <ben@transient.nz> |
|---|---|
| Date | 2018-09-21 00:40 +0200 |
| Message-ID | <wAfM5-oz-1@gated-at.bofh.it> |
| In reply to | #200354 |
On 21/09/2018 07:51, Default User wrote: > Using advice given, using apt-listings and aptitude full-update, l was able > to update everything except the 3 packages in question, which are now > "pinned", with a priority of 3000. I find apt-mark hold more convenient than pinning. > I do have both cron and anacron installed, but have never used or done > anything to configure them. Note: the computer in question is not on 24/7, > but is normally on part of every day. Thus anacron, per the apt-listbugs > man page. I mask cron and anacron because I prefer manual control of all system maintenance tasks. Kind regards, -- Ben Caradoc-Davies <ben@transient.nz> Director Transient Software Limited <https://transient.nz/> New Zealand
[toc] | [prev] | [next] | [standalone]
| From | Default User <hunguponcontent@gmail.com> |
|---|---|
| Date | 2018-09-21 07:10 +0200 |
| Message-ID | <wAlRw-4h3-3@gated-at.bofh.it> |
| In reply to | #200357 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Sep 20, 2018, 18:39 Ben Caradoc-Davies <ben@transient.nz> wrote: > On 21/09/2018 07:51, Default User wrote: > > Using advice given, using apt-listings and aptitude full-update, l was > able > > to update everything except the 3 packages in question, which are now > > "pinned", with a priority of 3000. > > I find apt-mark hold more convenient than pinning. > > > I do have both cron and anacron installed, but have never used or done > > anything to configure them. Note: the computer in question is not on > 24/7, > > but is normally on part of every day. Thus anacron, per the apt-listbugs > > man page. > > I mask cron and anacron because I prefer manual control of all system > maintenance tasks. > > Kind regards, > > -- > Ben Caradoc-Davies <ben@transient.nz> > Director > Transient Software Limited <https://transient.nz/> > New Zealand > Now you tell me . . . : )
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2018-09-20 10:00 +0200 |
| Message-ID | <wA22t-Ml-1@gated-at.bofh.it> |
| In reply to | #200316 |
On Wed, 19 Sep 2018 21:16:30 -0400 Default User <hunguponcontent@gmail.com> wrote: > On Wed, Sep 19, 2018 at 9:05 PM John Hasler <jhasler@newsguy.com> > wrote: > > > You are running Unstable. It can be like that. > > -- > > John Hasler > > jhasler@newsguy.com > > Elmwood, WI USA > > > > > > 182 packages? No, three. The rest can be upgraded. I usually switch to synaptic when this happens, I find it easier to select the ones which will go. I've never got along with aptitude interactive for some reason. The same happens when some parts of a large set of packages are upgradeable and some aren't, like Qt or libreoffice. I upgrade the ones which aren't affected, and decline the offer to remove 350 packages. In fact, I often accept buggy upgrades if the problems aren't likely to affect me. I rarely use apt-cache on this machine, so I accepted that one. Failed To Build From Source is another one that doesn't worry me, because I don't. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Ben Caradoc-Davies <ben@transient.nz> |
|---|---|
| Date | 2018-09-20 03:30 +0200 |
| Message-ID | <wzVX4-5HU-1@gated-at.bofh.it> |
| In reply to | #200314 |
Read the bug reports and decide whether any of them will hurt you: On 20/09/2018 12:54, Default User wrote: > grave bugs of libtracker-sparql-2.0-0 (2.0.3-3 → 2.1.4-1) <Outstanding> > b1 - #908800 - nautilus: can't use nautilus without tracker If you use nautilus, "apt-get install tracker". > serious bugs of apt (1.6.4 → 1.7.0~rc1) <Outstanding> > b2 - #909155 - apt-cache show multiple packages produces invalid output Meh. Should be fixed. No doubt it will be fixed. But until then, I do not care. > serious bugs of colord (1.3.3-2 → 1.4.3-3) <Outstanding> > b3 - #908735 - colord: need to build-depend on argyll Only affects building this package, not end users. > Summary: > apt(1 bug), colord(1 bug), libtracker-sparql-2.0-0(1 bug) > Are you sure you want to install/upgrade the above packages? [Y/n/?/...] n At this point, instead of "n", just press "Enter". Kind regards, -- Ben Caradoc-Davies <ben@transient.nz> Director Transient Software Limited <https://transient.nz/> New Zealand
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2018-09-20 10:10 +0200 |
| Message-ID | <wA2c9-14v-1@gated-at.bofh.it> |
| In reply to | #200317 |
On Thu, 20 Sep 2018 13:26:05 +1200 Ben Caradoc-Davies <ben@transient.nz> wrote: > Read the bug reports and decide whether any of them will hurt you: > > On 20/09/2018 12:54, Default User wrote: > > grave bugs of libtracker-sparql-2.0-0 (2.0.3-3 → 2.1.4-1) > > <Outstanding> b1 - #908800 - nautilus: can't use nautilus without > > tracker > > If you use nautilus, "apt-get install tracker". > That was documented late, I never saw that that bug message until after I'd installed it, and nautilus failed to materialise when I had a client standing behind me. Fortunately, I also keep nemo installed and moved on with barely any fuss... I like nautilus, but it does have its moments. I later discovered the issue for myself on the Net. -- Joe
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web