-upgrade command line.
Ok, I went to the bottom: it was due to phased updates not selecting my
machine for applying the update. Disabling it via -o
APT::Get::Always-Include-Phased-Updates=1 force apt-get dist-upgrade to
update anything.
I hope this can be useful for others.
Thanks.
--
Danti
pt-mark. Nothing.
Using libsystemd0 as an example, apt-cache policy shown the installed
packages with score 100, and an available update with score 500. Still,
the update was not installed until I manually specified the package on
the apt-get dist-upgrade command line.
Full disclosure: this s
On 23/09/2022 00:33, Greg Wooledge wrote:
On Fri, Sep 23, 2022 at 01:04:26AM +0200, Gionatan Danti wrote:
root@localhost:/var/log/apt# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following
On Fri, Sep 23, 2022 at 01:04:26AM +0200, Gionatan Danti wrote:
> root@localhost:/var/log/apt# apt-get dist-upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
> The following packages h
Hi all,
I have a question about apt-get dist-upgrade refusing to update some
packages:
root@localhost:/var/log/apt# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been
On Mon, 2022-02-07 at 12:45 +0530, Jaikumar Sharma wrote:
> Hi,
>
> I'm trying to upgrade my Debian 10 box (10.11) with latest security
> fixes on using command line as per below:
>
> $ sudo apt-get -o Dpkg::Options::="--force-confdef" -o
> Dpkg::Options
Hi,
I'm trying to upgrade my Debian 10 box (10.11) with latest security
fixes on using command line as per below:
$ sudo apt-get -o Dpkg::Options::="--force-confdef" -o
Dpkg::Options::="--force-confold" dist-upgrade -y --allow-
unauthenticated
above command line
Hi again!
On Wed, Oct 06, 2021 at 06:02:40PM +0200, Oleg wrote:
> > ip link show
>
> $ > ip l sh
> ...
> 2: eth0: mtu 1492 qdisc pfifo_fast master
> direct0 state UP mode DEFAULT group default qlen 1000
> link/ether 54:04:a6:a0:77:de brd ff:ff:ff:ff:ff:ff
> 3: direct0: mtu 1492 qdisc noque
Hey Dan,
On Wed, Oct 06, 2021 at 10:23:40AM -0400, Dan Ritter wrote:
> Can you tell us about networking on the host, please?
sure, I can.
> ip link show
$ > ip l sh
...
2: eth0: mtu 1492 qdisc pfifo_fast master
direct0 state UP mode DEFAULT group default qlen 1000
link/ether 54:04:a6:a0:7
heck
> the ARP tables I can find the gateway's MAC address tagged as DELAY.
>
> The general setup has worked before the dist-upgrade for years and I'm a bit
> clueless what might has been broken during the update.
Can you tell us about networking on the host, please?
ip link
y's MAC address tagged as DELAY.
The general setup has worked before the dist-upgrade for years and I'm a bit
clueless what might has been broken during the update.
Cheers
Oleg
On Ma, 29 iun 21, 22:41:10, Gareth Evans wrote:
>
> Even if I had made use of upgrade rather than dist-upgrade, presumably
> a dist-upgrade would have been indicated here (by the existence of
> packages kept back) and the same position would have resulted - ie.
> havin
But your evening run of apt-get -y dist-upgrade was unconstrained,
> > > > and so shim-signed could be removed because it was no longer being
> > > > held onto as a Depends or Recommends.
> > >
> > > Except that `apt-get dist-upgrade` doesn't do that (`
On Tue 29 Jun 2021, at 22:41, Gareth Evans wrote:
> On Tue 29 Jun 2021, at 17:11, David Wright wrote:
> > On Tue 29 Jun 2021 at 08:29:22 (+0300), Andrei POPESCU wrote:
> > > On Lu, 28 iun 21, 09:46:17, David Wright wrote:
> > > >
> > > > But your even
On Tue 29 Jun 2021, at 17:11, David Wright wrote:
> On Tue 29 Jun 2021 at 08:29:22 (+0300), Andrei POPESCU wrote:
> > On Lu, 28 iun 21, 09:46:17, David Wright wrote:
> > >
> > > But your evening run of apt-get -y dist-upgrade was unconstrained,
> > >
On Tue 29 Jun 2021 at 08:29:22 (+0300), Andrei POPESCU wrote:
> On Lu, 28 iun 21, 09:46:17, David Wright wrote:
> >
> > But your evening run of apt-get -y dist-upgrade was unconstrained,
> > and so shim-signed could be removed because it was no longer being
> >
On Lu, 28 iun 21, 09:46:17, David Wright wrote:
>
> But your evening run of apt-get -y dist-upgrade was unconstrained,
> and so shim-signed could be removed because it was no longer being
> held onto as a Depends or Recommends.
Except that `apt-get dist-upgrade` doesn't do
On Sun 27 Jun 2021 at 05:31:05 (+0100), Gareth Evans wrote:
> On Tue 22 Jun 2021, at 19:13, David Wright wrote:
> > On Tue 22 Jun 2021 at 08:59:13 (+0100), Gareth Evans wrote:
> > > A recent dist-upgrade on Buster (in a scripted cron job run at 01:00
> > > daily)
On Tue 22 Jun 2021, at 19:13, David Wright wrote:
> On Tue 22 Jun 2021 at 08:59:13 (+0100), Gareth Evans wrote:
> > A recent dist-upgrade on Buster (in a scripted cron job run at 01:00 daily)
> > failed due to apt-listbugs complaining about the boot-breaking bug in
> > shi
On Tue 22 Jun 2021 at 08:59:13 (+0100), Gareth Evans wrote:
> A recent dist-upgrade on Buster (in a scripted cron job run at 01:00 daily)
> failed due to apt-listbugs complaining about the boot-breaking bug in
> shim-signed, and pinning v1.33 in the process.
>
> https://bugs.deb
A recent dist-upgrade on Buster (in a scripted cron job run at 01:00 daily)
failed due to apt-listbugs complaining about the boot-breaking bug in
shim-signed, and pinning v1.33 in the process.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990082
The next (manual) dist-upgrade removed shim
On Mon, May 03, 2021 at 09:16:40AM -0400, Stefan Monnier wrote:
> Me, I basically only reboot in 2 cases:
> - the power went out
>
>
> Stefan
There are two difficult problems in computing: naming things, cache
invalidation, and off-by-one errors.
> I'm trying to distinguish when a system reboot is an absolute need
> and when it is absolutely safe to keep the system running/working
> after a `sudo apt-get update && sudo apt-get dist-upgrade`, once
> I have already performed a complete restart of all needed
is absolutely safe to keep the system running/working
> after a `sudo apt-get update && sudo apt-get dist-upgrade`, once
> I have already performed a complete restart of all needed services
> through `sudo needrestart' options in Debian testing.
needrestart does have some bui
.
>>
>> I'm trying to distinguish when a system reboot is an absolute need
>> and when it is absolutely safe to keep the system running/working
>> after a `sudo apt-get update && sudo apt-get dist-upgrade`, once
>> I have already performed a complete restart
stem running/working
> after a `sudo apt-get update && sudo apt-get dist-upgrade`, once
> I have already performed a complete restart of all needed services
> through `sudo needrestart' options in Debian testing.
>
In general, if the Kernel is updated, plan to Restart. Us
On Mon, 3 May 2021 at 11:42, riveravaldez wrote:
> PS: `apt-get dist-upgrade` output is translated to English
Please don't do this, because it introduces unreliable and
unreproducible communication and wastes your time.
What helps everyone is to share the reproducible *copy/paste
Hi, sorry if this is not the place to ask (and in that case please
point me in the proper direction).
I'm trying to distinguish when a system reboot is an absolute need
and when it is absolutely safe to keep the system running/working
after a `sudo apt-get update && sudo apt-get
On Fri 12 Feb 2021 at 08:02:02 -0500, Greg Wooledge wrote:
> On Fri, Feb 12, 2021 at 12:56:00PM +, pioruns2019 wrote:
> > Why You want to upgrade from buster to sid? You have enabled both sid
> > and buster-updates repositories. This won't work, unless you know what
> > you're doing.
> > I sug
On 12/02/2021 13:02, Greg Wooledge wrote:
On Fri, Feb 12, 2021 at 12:56:00PM +, pioruns2019 wrote:
Why You want to upgrade from buster to sid? You have enabled both sid
and buster-updates repositories. This won't work, unless you know what
you're doing.
I suggest to install sid from the scra
On 12/02/2021 12:22, thah...@t-online.de wrote:
# deb cdrom:[Debian GNU/Linux 10.7.0 _Buster_ - Unofficial amd64 DVD Binary-1
with firmware 20201205-11:17]/ buster contrib main non-free
#deb cdrom:[Debian GNU/Linux 10.7.0 _Buster_ - Unofficial amd64 DVD Binary-1
with firmware 20201205-11:17]/
Greg Wooledge (12021-02-12):
> If one wants to run unstable, one
> installs the current stable release, and then upgrades to sid.
That's never how I do it. And I have no problem with my method.
> The probem here is that the OP attempted to mix stable and unstab
On Fri, Feb 12, 2021 at 12:56:00PM +, pioruns2019 wrote:
> Why You want to upgrade from buster to sid? You have enabled both sid
> and buster-updates repositories. This won't work, unless you know what
> you're doing.
> I suggest to install sid from the scratch, if you want to have sid. If
> yo
On 2021-02-12 at 06:02, thah...@t-online.de wrote:
> Hello,
> I have installed 10.7 and then
> apt upgrade
> without any problems.
> However the following
> apt dist-upgrade
> failed badly and cannot be repaired with
> apt --fix-broken install
>
> Correcting
On Fri, Feb 12, 2021 at 12:02:51PM +0100, thah...@t-online.de wrote:
> The following packages have unmet dependencies:
> ffmpeg : Depends: libavcodec58 (= 7:4.1.6-1~deb10u1)
> Depends: libavformat58 (= 7:4.1.6-1~deb10u1) but 7:4.3.1-8 is installed
> Depends: libavutil56 (= 7:4.1.6-1~deb10u1) but 7:
On 12/02/2021 12:22, thah...@t-online.de wrote:
# deb cdrom:[Debian GNU/Linux 10.7.0 _Buster_ - Unofficial amd64 DVD Binary-1
with firmware 20201205-11:17]/ buster contrib main non-free
#deb cdrom:[Debian GNU/Linux 10.7.0 _Buster_ - Unofficial amd64 DVD Binary-1
with firmware 20201205-11:17]/
n-security for sid probably doesn't exist.
-Original-Nachricht-
Betreff: Re: dist-upgrade from buster fails badly
Datum: 2021-02-12T12:33:40+0100
Von: "Dan Ritter"
An: "thah...@t-online.de"
thah...@t-online.de wrote:
> Hello,
> I have installed 10.7 and
thah...@t-online.de wrote:
> Hello,
> I have installed 10.7 and then
> apt upgrade
> without any problems.
> However the following
> apt dist-upgrade
> failed badly and cannot be repaired with
> apt --fix-broken install
>
> Correcting dependencies... failed.
>
Hello,
I have installed 10.7 and then
apt upgrade
without any problems.
However the following
apt dist-upgrade
failed badly and cannot be repaired with
apt --fix-broken install
Correcting dependencies... failed.
The following packages have unmet dependencies:
ffmpeg : Depends: libavcodec58 (= 7
On Fri 18 Sep 2020 at 10:33:39 (+0100), Jonathan Dowland wrote:
> On Thu, Sep 17, 2020 at 11:01:49AM -0500, David Wright wrote:
> > It's difficult to understand your OP, and your difficulty with
> > pasting. However, to take one example,
>
> Indeed without OP's terminal output we can only guess as
On Thu, Sep 17, 2020 at 11:01:49AM -0500, David Wright wrote:
It's difficult to understand your OP, and your difficulty with
pasting. However, to take one example,
Indeed without OP's terminal output we can only guess as to why the
packages are being removed from their system,
[wicd] news
On Jo, 17 sep 20, 17:14:30, Hans wrote:
>
> The point of my message was not the deinstallation of packages at all, but
> the
> deinstallation of packages which are still usefull for people without a
> substitute or a substitude with the same ease as the uninstalled package.
Please note bullsey
On 9/17/2020 10:29 AM, Joe wrote:
On Thu, 17 Sep 2020 17:14:30 +0200
Hans wrote:
Am Donnerstag, 17. September 2020, 17:01:29 CEST schrieb Joe:
Hi Joe,
No offence. :)
And none taken. Yes, I've lost one or two applications over the years
which I was actively using. But it is rare for this t
On 9/17/2020 10:14 AM, Hans wrote:
Am Donnerstag, 17. September 2020, 17:01:29 CEST schrieb Joe:
Hi Joe,
yes I know, this is normal for unstable. I am using debian/testing, which is
close to unstable.
The point of my message was not the deinstallation of packages at all, but the
deinstallation
On Thursday, 17 September 2020 11:14:30 -04 Hans wrote:
> Am Donnerstag, 17. September 2020, 17:01:29 CEST schrieb Joe:
> Hi Joe,
>
> yes I know, this is normal for unstable. I am using debian/testing,
> which is close to unstable.
>
> The point of my message was not the deinstallation of packages
On Thu 17 Sep 2020 at 17:14:30 (+0200), Hans wrote:
> Am Donnerstag, 17. September 2020, 17:01:29 CEST schrieb Joe:
>
> yes I know, this is normal for unstable. I am using debian/testing, which is
> close to unstable.
>
> The point of my message was not the deinstallation of packages at all, bu
On Thu, 17 Sep 2020 17:14:30 +0200
Hans wrote:
> Am Donnerstag, 17. September 2020, 17:01:29 CEST schrieb Joe:
> Hi Joe,
>
> yes I know, this is normal for unstable. I am using debian/testing,
> which is close to unstable.
>
> The point of my message was not the deinstallation of packages at
>
Am Donnerstag, 17. September 2020, 17:01:29 CEST schrieb Joe:
Hi Joe,
yes I know, this is normal for unstable. I am using debian/testing, which is
close to unstable.
The point of my message was not the deinstallation of packages at all, but the
deinstallation of packages which are still useful
Unstable, the behaviour you are seeing is normal. What happens is
that a group of related packages are released as each individual
package is ready. Some of the other related packages will not be
compatible with the released ones. Some other packages depend on the
related not-released packages.
Am Donnerstag, 17. September 2020, 12:47:24 CEST schrieb Hans:
Hmm, answer myself. Looks like the output is could not be pasted into
the mail (root rights). However, think, you understood my worries. To
verify: I do not want to blame someone, my intention is more looking
in the way, unexperien
Hi folks,
of course, apt-get full-upgrade sometimes wants to deinstall some packages, but
this
here is strange. Take a look:
---
apt-get full-upgrade
Really? You want deinstall packages like wicd*, zenmap, d-rats? This looks
weired for me,
as there is no success for wicd (network-manager
On Lu, 09 dec 19, 20:27:28, riveravaldez wrote:
>
> Just to clarify: How long one could go on upgrading debian-testing
> (kernel included) without rebooting?
As long as it is acceptable for you to run the system with known
security flaws.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFrom
riveravaldez wrote:
...
> Hi, thanks a lot for the answers/info.
>
> Just to clarify: How long one could go on upgrading debian-testing
> (kernel included) without rebooting?
why would you not want to reboot? if you aren't going to
use the upgrades why are you making them? if you think there
a
On 12/4/19, songbird wrote:
> Sven Hartge wrote:
>> riveravaldez wrote:
>>
>>> Because updating the kernel requires to reboot the system -AFAIK- in
>>> many cases I would prefer to 'dist-upgrade' (all packages) except the
>>> kernel -until a mo
Sven Hartge wrote:
> riveravaldez wrote:
>
>> Because updating the kernel requires to reboot the system -AFAIK- in
>> many cases I would prefer to 'dist-upgrade' (all packages) except the
>> kernel -until a moment in which I can reboot the system-, so:
>
riveravaldez wrote:
> Because updating the kernel requires to reboot the system -AFAIK- in
> many cases I would prefer to 'dist-upgrade' (all packages) except the
> kernel -until a moment in which I can reboot the system-, so:
> 1. Is this something right/viable/accept
Because updating the kernel requires to reboot the system -AFAIK- in
many cases I would prefer to 'dist-upgrade' (all packages) except the
kernel -until a moment in which I can reboot the system-, so:
1. Is this something right/viable/acceptable to do?
2. Which would be the best/proper
st an upgrade of an existing package.
By default, "apt upgrade" will allow new packages to be installed, but
"apt-get upgrade" will not.
You can use "apt-get dist-upgrade". Or you can use
"apt-get --with-new-pkgs upgrade".
Or simply "apt upgrade&qu
gt; > Because the kernel ABI changed, and a new package has to be installed.
> > It's not just an upgrade of an existing package.
> >
> > By default, "apt upgrade" will allow new packages to be installed, but
> > "apt-get upgrade" will not.
> >
lled.
> It's not just an upgrade of an existing package.
>
> By default, "apt upgrade" will allow new packages to be installed, but
> "apt-get upgrade" will not.
>
> You can use "apt-get dist-upgrade". Or you can use
> "apt-get --with
By default, "apt upgrade" will allow new packages to be installed, but
"apt-get upgrade" will not.
You can use "apt-get dist-upgrade". Or you can use
"apt-get --with-new-pkgs upgrade". Or you can (maybe?) tweak some variable
in apt.conf to make --with-new-pkgs the default behavior.
the kernel but that states just
-
linux-latest (80+deb9u7) stretch; urgency=medium
* Update to 4.9.0-9
-- Salvatore Bonaccorso Fri, 29 Mar 2019 14:41:18 +0100
-
Not much help. :-(
So what is so special about the deb9u6 to debu9u7 upgrade that I need
dist-upgrade? W
Quoting aprekates (2019-05-01 01:21:13)
> deb http://debian-mirrors.sdinet.de/deb-multimedia stable main
Above line caused the problem: You are not running Debian but a mixture
of Debian and something else.
It is your system, and you are free to do as you like with it. But if
you want your sys
deb http://ftp.debian.org/debian stretch-backports main
deb http://debian-mirrors.sdinet.de/deb-multimedia stable main
On 30/4/19 10:17 μ.μ., Jonas Smedegaard wrote:
Quoting aprekates (2019-04-30 21:09:16)
Trying to upgrade from 9.6 i get:
$ LANG=en sudo apt-get dist-upgrade
WARNING: The
On Tue 30 Apr 2019 at 22:09:16 +0300, aprekates wrote:
> Trying to upgrade from 9.6 i get:
>
> $ LANG=en sudo apt-get dist-upgrade
>
>
> WARNING: The following packages cannot be authenticated!
> libbasicusageenvironment1 libgroupsock8 liblivemedia58
> libusageenvi
Quoting aprekates (2019-04-30 21:09:16)
> Trying to upgrade from 9.6 i get:
>
> $ LANG=en sudo apt-get dist-upgrade
>
>
> WARNING: The following packages cannot be authenticated!
> libbasicusageenvironment1 libgroupsock8 liblivemedia58
> libusageenvironment3 libvl
Trying to upgrade from 9.6 i get:
$ LANG=en sudo apt-get dist-upgrade
WARNING: The following packages cannot be authenticated!
libbasicusageenvironment1 libgroupsock8 liblivemedia58
libusageenvironment3 libvlccore9 vlc-plugin-skins2 vlc vlc-plugin-qt
vlc-l10n vlc-plugin-base vlc-data vlc
On 02/07/18 12:55 AM, Curt wrote:
On 2018-07-01, Charlie Gibbs wrote:
E: You don't have enough free space in /var/cache/apt/archives/.
apt-get autoclean doesn't help; neither does apt-get clean. When I
tried apt-get autoremove, the upgrade started, but at 99% completion it
threw the message
week to go.
>
> Back in the days of etch, it was an hour or two. Not any more.
Can you be more specific. The only case I can think of "recently" was
the dist-upgrade from lenny to squeeze where, if you were still
running the original lenny kernel, it was important to make sure tha
Charlie Gibbs wrote:
...
> Sure enough, / is full, with all the fun that that entails.
...
there are a lot of potential places to get space back:
- check /var/log
- also, see if you have old kernels that can be removed.
- your browser cache may be huge.
- downloaded files directory
On Mon, 2 Jul 2018 09:55:48 + (UTC)
Curt wrote:
> On 2018-07-02, Joe wrote:
> > On Sun, 1 Jul 2018 17:43:02 -0500
> > David Wright wrote:
> >
> >
> >>
> >> Why? If you find the cause, you can fix it. Upgrades are careful
> >> about preserving the system's integrity to run.
> >>
> >
>
On 2018-07-02, Joe wrote:
> On Sun, 1 Jul 2018 17:43:02 -0500
> David Wright wrote:
>
>
>>
>> Why? If you find the cause, you can fix it. Upgrades are careful
>> about preserving the system's integrity to run.
>>
>
> Less and less with each version.
>
> I have a wheezy: I cloned it to a spare
On Sun, 1 Jul 2018 17:43:02 -0500
David Wright wrote:
>
> Why? If you find the cause, you can fix it. Upgrades are careful
> about preserving the system's integrity to run.
>
Less and less with each version.
I have a wheezy: I cloned it to a spare desktop machine, upgraded with
some signifi
On 2018-07-01, Charlie Gibbs wrote:
>
> E: You don't have enough free space in /var/cache/apt/archives/.
>
> apt-get autoclean doesn't help; neither does apt-get clean. When I
> tried apt-get autoremove, the upgrade started, but at 99% completion it
> threw the message:
>
> Error writing to out
which compiles these programs successfully. However,
"sudo apt-get dist-upgrade" shows the message:
E: You don't have enough free space in /var/cache/apt/archives/.
apt-get autoclean doesn't help; neither does apt-get clean. When I
tried apt-get autoremove, the upgrade star
enSSL clients on my Jessie laptop (see my recent posting titled
> >> "Can't link to OpenSSL on my laptop). I've decided to upgrade it
> >> to Stretch like my desktop machine, which compiles these programs
> >> successfully. However, "sudo apt-get dist-
to OpenSSL on my laptop). I've decided to upgrade it
>> to Stretch like my desktop machine, which compiles these programs
>> successfully. However, "sudo apt-get dist-upgrade" shows the
>> message:
>>
>> E: You don't have enough free space in /v
Stretch like my desktop machine, which compiles these programs
> successfully. However, "sudo apt-get dist-upgrade" shows the
> message:
>
> E: You don't have enough free space in /var/cache/apt/archives/.
>
> apt-get autoclean doesn't help; neither does apt-g
Pros: clean system
nice fast SSD
partitions the size you want them to be
Cons: expensive, relatively slow to do.
If you can afford it, do this. If you have spinning rust in your
system now, definitely do this. It avoids all the dist-upgrade issues
and the performance impr
be purged. Even packages you use can be
purged, then reinstalled after the dist-upgrade.
If space is still a problem after thorough cleaning, specific (large) parts of
the existing installation can be upgraded, one package or package group at a
time if necessary, such as libreoffice, firmw
retch like my desktop machine,
> which compiles these programs successfully. However, "sudo apt-get
> dist-upgrade" shows the message:
>
> E: You don't have enough free space in /var/cache/apt/archives/.
>
> apt-get autoclean doesn't help; neither does apt-get
However,
"sudo apt-get dist-upgrade" shows the message:
E: You don't have enough free space in /var/cache/apt/archives/.
apt-get autoclean doesn't help; neither does apt-get clean. When I
tried apt-get autoremove, the upgrade started, but at 99% completion it
threw the
automatically
to the new format at first use. Not for me.
> just run "apt-get clean" and enjoy the extra space.
Will do, when i managed to build my packages. But as it looks now, i will
have to trash this Sid version in favor of its predecessor.
(All the effort to make vim usable
f re-installing installed packages. Is that a valid use case ?
On my Jessie it is 2.4 GB. But she has 2.5 TB of disk, not 32 GB like Sid.
Further i could need hints how to find out why dist-upgrade intentionally
inflated the i
On Fri, Sep 15, 2017 at 03:02:50PM +0200, Thomas Schmitt wrote:
Before i run apt-get commands from the web like "clean" or "autoclean",
i'd like to know for what use case Debian keeps this wealth of .deb files.
The internet mainly has the story that it grows a lot, for the purpose
of re-installin
time to give the courageous
Sid users my freshest bugs.
Filing a bug report to "findutils" is on my todo list. (Not that there
weren't enough bug mummies yet.)
> But hey, you're aware of the risks.
Mainly i am mistrusting. I made a backup of the virtual disk before
On Fri, Sep 15, 2017 at 03:02:50PM +0200, Thomas Schmitt wrote:
> When looking for the reason of the waste i got to nearly 5 GB of
> /var/cache/apt
>
> Before i run apt-get commands from the web like "clean" or "autoclean",
> i'd like to know for what use case Debian keeps this wealth of .deb fi
ase ?
On my Jessie it is 2.4 GB. But she has 2.5 TB of disk, not 32 GB like Sid.
Further i could need hints how to find out why dist-upgrade intentionally
inflated the installed Sid by 1.2 GB of installed package content.
W
On 08/10/2017 06:08 PM, Neo wrote:
> Hi folks
>
> How to get sha256 digest for jessie, without a dist-upgrade?
>
I'd use sha256sum, but if you must use openssl, the version in
jessie-security has sha256.
> $ openssl version
> OpenSSL 1.0.1t 3 May 2016&g
Hi.
On Thu, Aug 10, 2017 at 11:08:41AM +0200, Neo wrote:
> Hi folks
>
> How to get sha256 digest for jessie, without a dist-upgrade?
By using sha256sum from coreutils. Why would you ever need openssl for
that?
Reco
Hi folks
How to get sha256 digest for jessie, without a dist-upgrade?
stretch:
openssl version
OpenSSL 1.1.0f 25 May 2017
Message Digest commands (see the `dgst' command for more details)
blake2b512blake2s256gost md4
md5 rmd160
Hi all,
I performed a dist-upgrade from jessie to stretch on my desktop. It
did not went well. I manage to solve many problems except the texlive
issue. I finally remove anything tex related and try to slowly install
it back. I started with tex-common. That went well. Then with
texlive-base. That
And the problem is back :-(
--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com
13. Apr 2017 19:38 by aquar...@tutanota.de:
> I did apt-get install libgl1-nvidia-glx nvidia-kernel-dkms
> It failed:
> The following NEW packages will be installed:
> libg
I did apt-get install libgl1-nvidia-glx nvidia-kernel-dkms
It failed:
The following NEW packages will be installed:
libgl1-nvidia-glx
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/7,479 kB of archives.
After this operation, 45.8 MB of additional disk space will be
After m-a I have choosen the prepare option. It gave this output:
Getting source for kernel version: 3.16.0-4-amd64
Kernel headers available in /lib/modules/3.16.0-4-amd64/build
Creating symlink...
apt-get install build-essential
Reading package lists... Done
Building dependency tree
Readin
Am Donnerstag, 13. April 2017, 19:25:01 CEST schrieb Aquarius:
> Hans,
>
> How do I do this when in the menu:
When the ncurses GUI is started (ncurses means the ASCII-GUI), then go to and
enter the point "Prepare". This will then install all necessary packages.
> "This opens a ncurses interfac
Hans,
How do I do this when in the menu:
"This opens a ncurses interface. Check now, if all dependencies (kernel-headers
etc. ) are installed. Module-assistant does this for you."?
And can I do: "Then just install libgl1-nvidia-glx and nvidia-kernel-dkms"
with apt-get install as well?
Thanks
Additionally I saw, debian offers prebuilt nvidia-kernel-headers for 3.16
kernel. Maybe these are running for your system? I am running kernel 4.9.0-2-
*, as I am running debian testing.
Hans
Ok, maybe try my way:
When I install nvidia driver, I first check, if all depenedencies are there.
Best way, module-assistant, check, if it is installed.
Then try:
m-a
This opens a ncurses interface. Check now, if all dependencies (kernel-headers
etc. ) are installed. Module-assistant does t
Am Donnerstag, 13. April 2017, 19:00:00 CEST schrieb Aquarius:
> Are you after this info:
Yes, it is then 340 driver.
I wanted to make sure, you chose the correct driver.
> 01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT
> 525M] (rev a1) ?
>
> --
> Securely sent with Tuta
1 - 100 of 1892 matches
Mail list logo
