On 13/03/22 21:15, gene heskett wrote:
they are the last seacrate drives I'll own... Ever.
Lots of brands seem to go through bad patches. Even just bad batches.
For stuff I care about, I use RAID1 (mdraid), on NAS drives, from mixed
manufacturers. So I'll have a pair consisting of a Seagate I
On Mon, Mar 14, 2022 at 05:23:02PM -0700, Cousin Stanley wrote:
> Dan Ritter wrote:
>
> >
> > Not having Built-Using is just like not having dependencies.
>
> Thanks for the explanation.
>
> I can understand the need for the Built-Using list
> for the developers that need it.
No, it
Cousin Stanley wrote:
> Reading this newsgroup earlier today
> someone mentioned the hugo package
> for static site generation.
>
> I was curious about the package
> so I tried
>
> $ apt-cache show hugo
...
i have been building hugo on my Debian system for
quite a while
On Mon, Mar 14, 2022 at 05:37:30PM -0700, Cousin Stanley wrote:
> David Wright wrote:
>
> > How about:
> >
> > $ apt-cache show hugo | grep -v '^Built-Using:'
> >
> > which you could wrap into a function.
> >
>
> I don't mind the Built-Using list at all
> for reasonable sized lists and I
David Wright wrote:
> How about:
>
> $ apt-cache show hugo | grep -v '^Built-Using:'
>
> which you could wrap into a function.
>
I don't mind the Built-Using list at all
for reasonable sized lists and I wouldn't
care to remove it altogether.
I can use your suggestion to remove it
Dan Ritter wrote:
>
> Not having Built-Using is just like not having dependencies.
Thanks for the explanation.
I can understand the need for the Built-Using list
for the developers that need it.
In cases such as that for the l o n g list
returned for golang built packages like
On Mon 14 Mar 2022 at 16:33:42 (-0700), Cousin Stanley wrote:
> Andy Smith wrote:
> >
> > So this information is needed for the developers and packagers,
> > but I suppose you could argue that it is information overload
> > for the casual user of "apt show".
>
> It seems to be information
Andy Smith wrote:
>
> So this information is needed for the developers and packagers,
> but I suppose you could argue that it is information overload
> for the casual user of "apt show".
It seems to be information overload for me pesonally.
Perhaps a link to the relevant golang list
On Monday, 14 March 2022 17:10:10 EDT Andy Smith wrote:
> Gene,
>
> I just don't know where to start with finding relevant bits to quote
> from your text.
>
> I find it unlikely that several of the drives you have bought should
> all be failed and dead. I'm concerned that you're prematurely
> jum
Cousin Stanley wrote:
> Reading this newsgroup earlier today
> someone mentioned the hugo package
> for static site generation.
>
> I was curious about the package
> so I tried
>
> $ apt-cache show hugo
>
> The usual package information was returned
> along with, in my
Gene,
I just don't know where to start with finding relevant bits to quote
from your text.
I find it unlikely that several of the drives you have bought should
all be failed and dead. I'm concerned that you're prematurely
jumping to conclusions and junking them.
It's normal for the device nodes
Hello,
On Mon, Mar 14, 2022 at 12:53:21PM -0700, Cousin Stanley wrote:
> $ apt-cache show hugo
>
> The usual package information was returned
> along with, in my opinion, an unsightly mess
> entailing a long string of 88 entries
> naming individual golang packages
> following Buil
Reading this newsgroup earlier today
someone mentioned the hugo package
for static site generation.
I was curious about the package
so I tried
$ apt-cache show hugo
The usual package information was returned
along with, in my opinion, an unsightly mess
entailing a lon
On Mon, Mar 14, 2022, 2:21 PM Marco Möller <
ta...@debianlists.mobilxpress.net> wrote:
> On 14.03.22 18:28, Anssi Saari wrote:
> > Marco Möller writes:
> >
> >> I am not sure if I understood your answer. Is it a suggestion of what
> >> should be of importance, or is it the confirmation that Wayla
On 14.03.22 18:28, Anssi Saari wrote:
Marco Möller writes:
I am not sure if I understood your answer. Is it a suggestion of what
should be of importance, or is it the confirmation that Wayland is
capable to configure clipboard access restrictive like this?
Um, I thought a question mark is a
ps: sorry, on a Debian Sid system for sure.
Le lun. 14 mars 2022 à 19:41, Patrice Duroux a
écrit :
>
> Hi,
>
> Since some versions ago, apt/dpkg(?) is stopping its process (upgrade
> here) whatever the packaging trouble it is facing. But in some cases, it
> may leave the system more broken than
Hi,
Since some versions ago, apt/dpkg(?) is stopping its process (upgrade here)
whatever the packaging trouble it is facing. But in some cases, it may
leave the system more broken than it would become just by 'skipping' the
troubling package.
For instance, in the upgrading transaction list were so
Marco Möller writes:
> I am not sure if I understood your answer. Is it a suggestion of what
> should be of importance, or is it the confirmation that Wayland is
> capable to configure clipboard access restrictive like this?
Um, I thought a question mark is a fairly common indication of a
questi
On 14.03.22 16:23, Anssi Saari wrote:
Nicholas Geovanis writes:
Isn't it all about X by design to not be able to safely protect a
running X applications to snoop on other running X applications,
something like the content of a window cannot safely kept private?
Well, what about somethi
Nicholas Geovanis writes:
> Isn't it all about X by design to not be able to safely protect a
> running X applications to snoop on other running X applications,
> something like the content of a window cannot safely kept private?
Well, what about something basic like allowing only specific
David Wright wrote:
I was casting round for a simple way to run iwd + resolvconf +
systemd-networkd as replacement.
I run a similar setup, with iwd, systemd-networkd and systemd-resolved.
This has been working without problems on my host for for quite a while
now.
Make a copy of your /etc/reso
21 matches
Mail list logo
