On Mon 20 Jun 2022, at 23:50, Gareth Evans wrote:
> On Mon 20 Jun 2022, at 23:31, Gareth Evans wrote:
>> On Mon 20 Jun 2022, at 17:34, The Wanderer wrote:
>>> On 2022-06-20 at 12:01, Brian wrote:
>>>
On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
> On 2022-06-20 at 08:5
On 20/06/2022 14:55, Siard wrote:
On Mon, 20 Jun 2022 14:21 +0200, Anders Andersson wrote:
Has something changed that makes virtualbox workable again,
I have the Virtualbox 6.1.34 package for Debian 11, downloaded from
www.virtualbox.org, working fine in Debian 12 (Bookworm).
Have you succeed
On Mon 20 Jun 2022, at 23:31, Gareth Evans wrote:
> On Mon 20 Jun 2022, at 17:34, The Wanderer wrote:
>> On 2022-06-20 at 12:01, Brian wrote:
>>
>>> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
>>>
On 2022-06-20 at 08:59, Brian wrote:
>>
> The ability to print to an IPP pri
On Mon 20 Jun 2022, at 17:34, The Wanderer wrote:
> On 2022-06-20 at 12:01, Brian wrote:
>
>> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
>>
>>> On 2022-06-20 at 08:59, Brian wrote:
>
The ability to print to an IPP printer involves discovering its
URI. CUPS gets the URI vi
On Mon 20 Jun 2022 at 19:49:18 +0100, Brian wrote:
Please forget about this mai. I pressed the wrong key. Never done that
before!
> On Mon 20 Jun 2022 at 12:34:19 -0400, The Wanderer wrote:
>
> > On 2022-06-20 at 12:01, Brian wrote:
> >
> > > "...once the URIis known"? What mechaism does that?
On Mon 20 Jun 2022 at 12:34:19 -0400, The Wanderer wrote:
> On 2022-06-20 at 12:01, Brian wrote:
>
> > "...once the URIis known"? What mechaism does that? Incidentally, a
> > URI is required to query a printer for its attributes.
>
> Any of a number of mechanisms.
>
> CUPS could run discovery on
On 2022-06-20 at 12:01, Brian wrote:
> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
>
>> On 2022-06-20 at 08:59, Brian wrote:
>>> The ability to print to an IPP printer involves discovering its
>>> URI. CUPS gets the URI via avahi-daemon whether it is an
>>> on-demand or manual queu
Since i am running dozens of VM's, i can say:
Me2 am running into this regularly, when i am trying to purge old
kernels. I am seeing this so frequently, that i even wrote a script
(meant to be run inside the VM's) to clean up the mess, some apt-scripts
happen to leave behind.
But in this special ca
On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
> On 2022-06-20 at 08:59, Brian wrote:
>
> > On Sun 19 Jun 2022 at 18:01:36 -0400, The Wanderer wrote:
> >
> >> On 2022-06-19 at 15:47, Brian wrote:
>
> >>> You (or the OP) would have to say what is meant by "delete".
> >>> CUPS essentia
On Mon, 20 Jun 2022 08:58:55 -0600
"D. R. Evans" wrote:
Hello D.,
>But it failed, with the error message:
Actually; .exited, with the warning.
That is to say, it's doing what it's supposed to do.
--
Regards _
/ ) "The blindingly obvious is never immediately apparent"
On Mon, 20 Jun 2022 08:58:55 -0600
"D. R. Evans" wrote:
> So it seems reasonable to remove /lib/modules/5.10.0-11-amd64/misc/
> manually and re-execute the purge command.
Yes, go ahead and do so.
>
> But before I try that, I'm puzzled as to how this situation could
> have arisen. Has anyone el
Normally to remove an old kernel from my debian stable systems, I issue the
following command:
apt purge linux-headers--amd64
linux-headers--common linux-image--amd64
Following this recipe, which has always worked in the past, I issued:
apt purge linux-headers-5.10.0-11-amd
On Mon, 20 Jun 2022 14:21 +0200, Anders Andersson wrote:
> Has something changed that makes virtualbox workable again,
I have the Virtualbox 6.1.34 package for Debian 11, downloaded from
www.virtualbox.org, working fine in Debian 12 (Bookworm).
On 2022-06-20 at 08:59, Brian wrote:
> On Sun 19 Jun 2022 at 18:01:36 -0400, The Wanderer wrote:
>
>> On 2022-06-19 at 15:47, Brian wrote:
>>> You (or the OP) would have to say what is meant by "delete".
>>> CUPS essentially *discover* printers. It is why it exists. Is
>>> that not wanted?
>>
>
On Sun 19 Jun 2022 at 18:01:36 -0400, The Wanderer wrote:
> On 2022-06-19 at 15:47, Brian wrote:
>
> > On Sun 19 Jun 2022 at 14:54:58 -0400, The Wanderer wrote:
> >
> >> On 2022-06-19 at 14:50, Brian wrote:
>
> >>> What does being "precious" involve?
> >>
> >> I'm less certain about this, but
On Mon, 20 Jun 2022 14:21:53 +0200
Anders Andersson wrote:
Hello Anders,
>Has something changed that makes virtualbox workable again, or has it
>*always* been available in sid?
It's always(1) been available in sid. VB has still got the same issue
WRT migrating to testing; Work may still be on
On Mon, Jun 20, 2022 at 02:21:53PM +0200, Anders Andersson wrote:
> I remember when Virtualbox was removed from debian, and I remember the
> reasons. That's why I was surprised when I saw a recent message to the
> list where a user tried to install it. Searching for "virtualbox"
> indeed shows me t
I remember when Virtualbox was removed from debian, and I remember the
reasons. That's why I was surprised when I saw a recent message to the
list where a user tried to install it. Searching for "virtualbox"
indeed shows me that it is available in stretch-backports and sid:
https://packages.debian.
18 matches
Mail list logo
