On Tue, Feb 28, 2023 at 10:20:20PM +, Keith Bainbridge wrote:
> +1
> --
>
>
> All the best
>
> Keith Bainbridge
>
> keith.bainbridge.3...@gmail.com
> 0447 667 468
>
> Sent from my Android tablet, Please excuse my brevity..
Still enough time to advertise products, still.
Cheers
-
t
On Mon, Feb 27, 2023 at 4:09 AM davidson wrote:
>
> On Sun, 26 Feb 2023 Albretch Mueller wrote:
> > Basically, I am trying to download all packages that are part of the
> > installation dependencies of a given one into a directory of my
> > choosing to then install packages on an unexposed machine
On Wed, 01 Mar 2023 00:11:39 +0300
skazka wrote:
> Unsubscribe
That is not how you do it.
Instead look at the headers for any email from the list (CTL-h on many
mail readers), and locate the header "List-Unsubscribe:". That will
give you at least one way to unsubscribe. In my mail reader, simpl
+1
--
All the best
Keith Bainbridge
keith.bainbridge.3...@gmail.com
0447 667 468
Sent from my Android tablet, Please excuse my brevity..
On 28 February 2023 20:21:40 UTC, Tixy wrote:
>On Tue, 2023-02-28 at 14:52 -0500, Greg Wooledge wrote:
>> On Tue, Feb 28, 2023 at 06:32:27PM +, Ti
For the future:
https://www.debian.org/MailingLists/unsubscribe
may help anyone. This is a page on which you should be able to unsubscribe
from any Debian lists.
You will potentially then be sent a confirmation email to confirm you
want to unsubscribe.
All best, as ever,
Andy Cater
On Wed,
Unsubscribe
debian-user-digest-requ...@lists.debian.org 1 марта 2023 г. 00:07:50 написал:
Content-Type: text/plain
debian-user-digest Digest Volume 2023 : Issue 163
Today's Topics:
Re: unbound and fetchmail (was: Re: [ Christoph Brinkhaus ]
Re: Debian 11 upg
On Tue, Feb 28, 2023 at 4:03 PM Brian wrote:
>
> On Tue 28 Feb 2023 at 15:35:43 -0500, Jeffrey Walton wrote:
>
> > On Tue, Feb 28, 2023 at 2:53 PM Greg Wooledge wrote:
> > >
> > > On Tue, Feb 28, 2023 at 06:32:27PM +, Tixy wrote:
> > > > On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterwort
On Tue 28 Feb 2023 at 15:35:43 -0500, Jeffrey Walton wrote:
> On Tue, Feb 28, 2023 at 2:53 PM Greg Wooledge wrote:
> >
> > On Tue, Feb 28, 2023 at 06:32:27PM +, Tixy wrote:
> > > On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
> > > [...]
> > > > All I did was modify /etc/apt/
On Tue, Feb 28, 2023 at 2:53 PM Greg Wooledge wrote:
>
> On Tue, Feb 28, 2023 at 06:32:27PM +, Tixy wrote:
> > On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
> > [...]
> > > All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> > > I ran apt update and a
On Tue, 2023-02-28 at 14:52 -0500, Greg Wooledge wrote:
> On Tue, Feb 28, 2023 at 06:32:27PM +, Tixy wrote:
> > On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
> > [...]
> > > All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> > > I ran apt update and a
On Tue, Feb 28, 2023 at 06:32:27PM +, Tixy wrote:
> On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
> [...]
> > All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> > I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
> > and that
On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
[...]
> All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
> and that probably would have worked better.
It would have. If you looke
On Tue, Feb 28, 2023 at 1:17 PM Timothy M Butterworth
wrote:
> [...]
> All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then I
> ran apt update and apt upgrade. I guess I could have run apt full-upgrade and
> that probably would have worked better.
Yeah, you were supposed
On Tue, Feb 28, 2023 at 7:24 AM local10 wrote:
> Feb 28, 2023, 09:04 by timothy.m.butterwo...@gmail.com:
>
> > I just updated my media center PC from Debian Bullseye to Debian
> Bookworm. The upgrade went alright. I initially had to download almost 2GB
> of 1640 packages. Around 600 failed to upg
On Tue, 2023-02-28 at 16:05 +0100, daven...@tuxfamily.org wrote:
>
> It's the systemd-style so-called "predictable" interfaces names.
> Replacing the older the eth0, wlan0, and so on…
>
> ens-something (annoying name made of multiple letters and digits) is the
> new name for eth0
Or eno for eth
On 2023-02-28 05:27, David Wright wrote:
On Thu 23 Feb 2023 at 11:23:30 (+0100), daven...@tuxfamily.org wrote:
On 2023-02-23 02:59, cono...@panix.com wrote:
[…]
On the newer work laptop on the other hand, there is that eth0 block,
there's is no eth0 interface on my system (there's enp.* and en
Feb 28, 2023, 12:24 by loca...@tutanota.com:
> Feb 28, 2023, 09:04 by timothy.m.butterwo...@gmail.com:
>
>> I just updated my media center PC from Debian Bullseye to Debian Bookworm.
>> The upgrade went alright. I initially had to download almost 2GB of 1640
>> packages. Around 600 failed to upg
Feb 28, 2023, 09:04 by timothy.m.butterwo...@gmail.com:
> I just updated my media center PC from Debian Bullseye to Debian Bookworm.
> The upgrade went alright. I initially had to download almost 2GB of 1640
> packages. Around 600 failed to upgrade and I had to manually install them in
> small
Am Sun, Feb 26, 2023 at 01:21:07PM -0600 schrieb David Wright:
Hello David and Max,
> On Sun 26 Feb 2023 at 19:08:01 (+0100), Christoph Brinkhaus wrote:
> > Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin:
> > > On 25/02/2023 19:49, Christoph Brinkhaus wrote:
> > > > Now there are no
Wen't good for me on a laptop some months ago
On 2/28/23, Timothy M Butterworth wrote:
> All,
>
> I just updated my media center PC from Debian Bullseye to Debian Bookworm.
> The upgrade went alright. I initially had to download almost 2GB of 1640
> packages. Around 600 failed to upgrade and I ha
All,
I just updated my media center PC from Debian Bullseye to Debian Bookworm.
The upgrade went alright. I initially had to download almost 2GB of 1640
packages. Around 600 failed to upgrade and I had to manually install them
in small chunks to fix the dependencies. Other than that the upgrade we
Disconnect an reconnect the cable fixed it.
On 28.02.23 09:26, basti wrote:
I didn't change anything in /etc/default/grub but even if there is no
usbserial_pl2303.mod in core image it should work when the system was
booted.
The cable should be OK, I have test it before I upgrade the system.
I didn't change anything in /etc/default/grub but even if there is no
usbserial_pl2303.mod in core image it should work when the system was
booted.
The cable should be OK, I have test it before I upgrade the system.
On 28.02.23 00:24, David Wright wrote:
On Mon 27 Feb 2023 at 14:06:08 (+0100)
23 matches
Mail list logo
