Urs Thuermann wrote:
> Now, it seems pip3 isn't able to remove packages from that old
> directory. Is it safe to just rm -r /usr/local/lib/python3.4?
yes it is more or less safe - it depends how you let it install - perhaps
there is also something under /usr/local/bin
regards
On 12/01/2017 08:54 PM, David Christensen wrote:
On 12/01/17 10:50, Dan Norton wrote:
Maybe this is the wrong forum, but please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem
is it will not boot normally. Network booting has been disabled in
th
On 12/01/17 10:50, Dan Norton wrote:
Maybe this is the wrong forum, but please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem is
it will not boot normally. Network booting has been disabled in the
NVRAM setup. After POST there is a one-liner whic
Thanks! I missed that email on that page. I think we can discuss this in
the community with them here (forwarding here to them).
Best,
Hörmet
He who is worthy to receive his days and nights is worthy to receive all
else from you (and me).
On 01.12.2017 22:19, Michael Biebl wrote:
>
> I think it might be useful to open a (wishlist) bug report against the
> linux package to not add the recommends when building for stretch-backports
>
Isn't AppArmor required in buster and also required in stretch-backports
linux-image? Of course AppArm
Dan Norton composed on 2017-12-01 16:23 (UTC-0500):
> The PC is simply not seeing the 1T sda, which is the only disk. It's not
> even getting as far as the mbr/grub. The PC appears to be no more than 5
> years old, based on the BIOS date, but it may be old enough to have a
> flaky UEFI. Should
On 12/01/2017 02:29 PM, Pascal Hambourg wrote:
Le 01/12/2017 à 19:57, Greg Wooledge a écrit :
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
Disklabel type: gpt
Apparently, BIOS does not see a bootable device. In the dim past, fdisk
could set a partition as "active", which was i
Jonathan Dowland wrote:
> Non-the-less, it's not something that many people will have attempted,
> and there are quite likely to be things that might slip through the net.
> Not just things within the Debian ecosystem: a machine running Lenny was
> presumably installed in or around 2009, so there'
Marc Auslander wrote:
> The installer manual is silent about installing in an existing raid
> partition. I could follow my nose but wondered if there is any advice
> you can provide.
Does this help https://wiki.debian.org/DebianInstaller/SoftwareRaidRoot
regards
Hi,
Dan Norton wrote:
> # fdisk -l
> ...
> Disklabel type: gpt
> In the dim past, fdisk
> could set a partition as "active", which was its euphemism for "bootable".
I guess, this applies only to MBR partition tables, not to GPT as on your
disk.
As Pascal stated, there is a bit defined in GPT to
Le 01/12/2017 à 19:57, Greg Wooledge a écrit :
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
Disklabel type: gpt
Apparently, BIOS does not see a bootable device. In the dim past, fdisk
could set a partition as "active", which was its euphemism for "bootable".
However now:
GPT
On Fri, Dec 01, 2017 at 01:57:37PM -0500, Greg Wooledge wrote:
> On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
> > Disklabel type: gpt
>
> > Apparently, BIOS does not see a bootable device. In the dim past, fdisk
> > could set a partition as "active", which was its euphemism for "boo
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
> Disklabel type: gpt
> Apparently, BIOS does not see a bootable device. In the dim past, fdisk
> could set a partition as "active", which was its euphemism for "bootable".
> However now:
GPT disk labels don't have active/bootable partit
Maybe this is the wrong forum, but please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem is
it will not boot normally. Network booting has been disabled in the
NVRAM setup. After POST there is a one-liner which says it can not find
disk. It can b
Am 01.12.2017 um 15:40 schrieb to...@tuxteam.de:
> On Fri, Dec 01, 2017 at 03:30:50PM +0100, solitone wrote:
>> On 01/12/17 15:22, Jonathan Dowland wrote:
>>> AppArmor is not enabled in current
>>> stable [...]
>
>> I have stretch, and didn't requested it manually, but was installed
>> with the la
On Friday, December 1, 2017 3:24:47 PM -03 Urs Thuermann wrote:
> On a machine running Debian stretch I have installed python3, which is
> currently python3.5. Nothing of python3.4 is present.
>
> But in /usr/local/lib/python3.4/dist-packages/ a number of packages is
> still installed. Probably,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Dec 01, 2017 at 03:30:50PM +0100, solitone wrote:
> On 01/12/17 15:22, Jonathan Dowland wrote:
> >AppArmor is not enabled in current
> >stable [...]
> I have stretch, and didn't requested it manually, but was installed
> with the latest kernel
On a machine running Debian stretch I have installed python3, which is
currently python3.5. Nothing of python3.4 is present.
But in /usr/local/lib/python3.4/dist-packages/ a number of packages is
still installed. Probably, these have been installed using pip3 when
python3.4 was current.
Now, it
On 01/12/17 15:22, Jonathan Dowland wrote:
AppArmor is not enabled in current
stable, so you should only hit this bug if you are using stable's
thunderbird on a testing/sid system, or manually enabling AppArmor
yourself on stable.
I have stretch, and didn't requested it manually, but was instal
On Wed, Nov 29, 2017 at 08:06:10PM +0100, deloptes wrote:
The release and upgrade notes are sufficient they state upgrade to next
release and then to next release.
Non-the-less, it's not something that many people will have attempted,
and there are quite likely to be things that might slip thro
On Thu, Nov 30, 2017 at 11:57:41AM +0100, solitone wrote:
It's a known bug, which is marked as solved since it has been solved
in the latest version of thunderbird (1:52.4.0-2~exp1):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855346#135
My question is--when will be this version come to s
On Thu, Nov 30, 2017 at 10:48:26PM -0500, Hörmetjan Yiltiz wrote:
However, I think we should be consistent in the text, text's color, and the
graphs. The current set of colors doesn't look impressive as the blueish
green and cyan look quite close. Maybe we can do better [2]?
You raise great poi
22 matches
Mail list logo
