On Fri, 12 Jun 2020 10:36:20 +0900
A_Man_Without_Clue wrote:
> On 6/8/20 2:23 AM, Seeds Notoneofmy wrote:
> > Well, as the subject suggests, I'm a bit fed up with the logic
> > behind how installed programs are sorted out in the Applications
> > menu.
> >
> > The need to go hunt down an installe
have you tried Alt+F2 (brings up a search menu X-D)
On 6/12/20 10:31 AM, Joe wrote:
> On Fri, 12 Jun 2020 10:36:20 +0900
> A_Man_Without_Clue wrote:
>
>> On 6/8/20 2:23 AM, Seeds Notoneofmy wrote:
>>> Well, as the subject suggests, I'm a bit fed up with the logic
>>> behind how installed programs
On Thu, Jun 11, 2020 at 08:52:10PM -0500, David Wright wrote:
If you were preserving the disk contents (imagine there were
proprietary encryption software on it), and performed a "read test"
or ran badblocks on it, would that be sufficient to test the disk's
performance, as it's merely reading th
Hi, on buster, I'm having a problem using the wiki instructions
https://wiki.debian.org/SimpleBackportCreation
specifically the 3 steps under the subheading
"Add source package entries for the testing distribution"
Although in my case I am seeking to obtain the source package
from unstable, not tes
The next step in the instructions also does not work for me
(on buster):
# mk-build-deps --install --remove
Usage:
mk-build-deps --help|--version
mk-build-deps [options] control file | package name ...
#
I thought those instructions are intended for a person
who is running stable and wan
Hi.
On Fri, Jun 12, 2020 at 10:02:12PM +1000, David wrote:
> Per step 1, I add a temporary unstable deb-src line so that my
> /etc/apt/sources.list becomes (comments removed, see last line):
...
> deb-src http://approx:/debian/ unstable main contrib non-free
For "apt source" to work y
On Fri, Jun 12, 2020 at 11:23:27PM +1000, David wrote:
> The next step in the instructions also does not work for me
> (on buster):
>
> # mk-build-deps --install --remove
> Usage:
> mk-build-deps --help|--version
>
> mk-build-deps [options] control file | package name ...
In your case it
Hi,
My email below got a DKIM issue. This is not the first time for me on this ML
so I'm trying to debug the situation with my email provider.
Does someone on this list mind forwarding to me (as an attachment please, not
inline) his/her own specimen of my original email below please? I need
he
On Fri, Jun 12, 2020 at 03:48:42PM +0200, l0f...@tuta.io wrote:
My email below got a DKIM issue.
It validated fine here, not a debian list issue.
On Fri, Jun 12, 2020 at 04:40:22PM +0300, Reco wrote:
> For "apt source" to work you need to add two lines:
>
> deb http://approx:/debian/ unstable main contrib non-free
> deb-src http://approx:/debian/ unstable main contrib non-free
Incorrect. Do *not* add a "deb" line for unstable
Hi.
On Fri, Jun 12, 2020 at 11:15:26AM -0400, Greg Wooledge wrote:
> On Fri, Jun 12, 2020 at 04:40:22PM +0300, Reco wrote:
> > For "apt source" to work you need to add two lines:
> >
> > deb http://approx:/debian/ unstable main contrib non-free
> > deb-src http://approx:/debia
On Vi, 12 iun 20, 22:02:12, David wrote:
>
> But step 3 fails:
> $ apt source -t unstable cgdb
> Reading package lists... Done
> E: The value 'unstable' is invalid for APT::Default-Release as such a
> release is not available in the sources
> E: Unable to find a source package for
> $ apt source -
On Fri, Jun 12, 2020 at 06:27:45PM +0300, Reco wrote:
> > Do *not* add a "deb" line for unstable to a stable
> > system. Only add the "deb-src" line.
>
> And that one too (a hint - it does not).
It does not *what*? What the hell are you talking about?
What it does is add UNSTABLE BINARY PACKA
Hi.
On Fri, Jun 12, 2020 at 12:02:11PM -0400, Greg Wooledge wrote:
> On Fri, Jun 12, 2020 at 06:27:45PM +0300, Reco wrote:
> > > Do *not* add a "deb" line for unstable to a stable
> > > system. Only add the "deb-src" line.
> >
> > And that one too (a hint - it does not).
>
> It does no
On Fri, Jun 12, 2020 at 07:15:20PM +0300, Reco wrote:
> > unicorn:~$ host approx
> > Host approx not found: 3(NXDOMAIN)
>
> LOL. Sober up first, then learn how to use apt.
unicorn:~$ man sources.list | grep approx
unicorn:~$ man apt | grep approx
unicorn:~$ man apt-get | grep approx
unicorn:~$
On Fri, Jun 12, 2020 at 09:52:57AM -0400, Michael Stone wrote:
On Fri, Jun 12, 2020 at 03:48:42PM +0200, l0f...@tuta.io wrote:
My email below got a DKIM issue.
It validated fine here, not a debian list issue.
For the record, I looked at the wrong email. The right one did fail DKIM
validatio
On Fri, Jun 12, 2020 at 12:33:02PM -0400, Greg Wooledge wrote:
> On Fri, Jun 12, 2020 at 07:15:20PM +0300, Reco wrote:
> > > unicorn:~$ host approx
> > > Host approx not found: 3(NXDOMAIN)
> >
> > LOL. Sober up first, then learn how to use apt.
Ugh.
> unicorn:~$ man sources.list | grep approx
>
On Fri, Jun 12, 2020 at 12:33:02PM -0400, Greg Wooledge wrote:
> On Fri, Jun 12, 2020 at 07:15:20PM +0300, Reco wrote:
> > > unicorn:~$ host approx
> > > Host approx not found: 3(NXDOMAIN)
> >
> > LOL. Sober up first, then learn how to use apt.
>
> unicorn:~$ man sources.list | grep approx
> unic
I now have a workaround for my problem with the Teac W5000U DVD drive
and 64 bit computer. Was somewhat hard to find, but I obtained a USB
controller card new enough to be PCI express but old enough not to
support USB 3.0. So far, have not suffered any more controller resets.
The card uses the eh
Calm down Greg and after that have a look at
https://packages.debian.org/sid/approx
Thanks.
Steve
Le 12-06-2020, à 12:33:02 -0400, Greg Wooledge a écrit :
On Fri, Jun 12, 2020 at 07:15:20PM +0300, Reco wrote:
> unicorn:~$ host approx
> Host approx not found: 3(NXDOMAIN)
LOL. Sober up fir
Hi.
On Fri, Jun 12, 2020 at 06:38:09PM +0200, to...@tuxteam.de wrote:
> On Fri, Jun 12, 2020 at 12:33:02PM -0400, Greg Wooledge wrote:
> > On Fri, Jun 12, 2020 at 07:15:20PM +0300, Reco wrote:
> > > > unicorn:~$ host approx
> > > > Host approx not found: 3(NXDOMAIN)
> > >
> > > LOL. Sober
On Fri, Jun 12, 2020 at 07:42:22PM +0300, Reco wrote:
[...]
> They say that one can prove anything by creative usage of quoting, and
> yours is a fine example of it. Here's better one:
Sorry. I wasn't trying to "prove" anything. Much less to make you or
anyone look bad.
[...]
> > Hey, folks. C
On Fri, Jun 12, 2020 at 06:38:09PM +0200, to...@tuxteam.de wrote:
> apt show approx will help. It's an APT proxy/cache (I'm more familiar
> with apt-cacher-ng though)
Oh, that actually looks useful. (Also, you actually gave *useful
information*, that was not simply "do research on this half a wor
On Fri, Jun 12, 2020 at 12:59:47PM -0400, Greg Wooledge wrote:
> After the compiling, it started running a test suite. One of the
> tests failed. So, this particular package might not have been as
> good a choice as I had hoped, for a simple demonstration of the
> process.
I was too pessimistic.
On Fri, Jun 12, 2020 at 12:59:47PM -0400, Greg Wooledge wrote:
> On Fri, Jun 12, 2020 at 06:38:09PM +0200, to...@tuxteam.de wrote:
> > apt show approx will help. It's an APT proxy/cache (I'm more familiar
> > with apt-cacher-ng though)
>
> Oh, that actually looks useful [...]
It sure is. I've pla
> > DO NOT add a "deb" line for unstable!
> >
> > I will keep repeating that as many times as it takes. Because it's
> > freaking IMPORTANT.
>
> Just a hint: it'd be more empowering for your interlocutors if you
> didn't just tell "don't do that" but rather what happens if they
> do (my guess is
On Fri, Jun 12, 2020 at 01:32:52PM -0400, Greg Wooledge wrote:
> My first message was quite polite.
>
> https://lists.debian.org/debian-user/2020/06/msg00426.html
Your first message was factually incorrect *and* rude.
I merely showed where you've mistaken.
> My second message went into details
On Fri, Jun 12, 2020 at 12:36:29PM -0400, Michael Stone wrote:
On Fri, Jun 12, 2020 at 09:52:57AM -0400, Michael Stone wrote:
On Fri, Jun 12, 2020 at 03:48:42PM +0200, l0f...@tuta.io wrote:
My email below got a DKIM issue.
It validated fine here, not a debian list issue.
For the record, I l
Hi,
12 juin 2020 à 22:16 de mst...@debian.org:
> More information from the OP, it looks like the message sent to the list was
> base64 encoded html. So I'm guessing that the list software autoconverted
> that to plain text--which would mean there's no way to preserve a valid DKIM
> signature.
Hi.
On Fri, Jun 12, 2020 at 04:16:23PM -0400, Michael Stone wrote:
> On Fri, Jun 12, 2020 at 12:36:29PM -0400, Michael Stone wrote:
> > On Fri, Jun 12, 2020 at 09:52:57AM -0400, Michael Stone wrote:
> > > On Fri, Jun 12, 2020 at 03:48:42PM +0200, l0f...@tuta.io wrote:
> > > > My email belo
On Fri, Jun 12, 2020 at 11:32:20PM +0300, Reco wrote:
Hi.
On Fri, Jun 12, 2020 at 04:16:23PM -0400, Michael Stone wrote:
On Fri, Jun 12, 2020 at 12:36:29PM -0400, Michael Stone wrote:
> On Fri, Jun 12, 2020 at 09:52:57AM -0400, Michael Stone wrote:
> > On Fri, Jun 12, 2020 at 03:48:42PM
Hi Reco,
12 juin 2020 à 22:32 de recovery...@enotuniq.net:
> Removing Content-Type (and maybe Content-Transfer-Encoding) from OP's
> DKIM policy should do the trick, although it can has certain undesirable
> side-effects if MTA in question is used for other purposes.
>
Thanks, I will submit this
On Fri, Jun 12, 2020 at 10:45:13PM +0200, l0f...@tuta.io wrote:
> Hi Reco,
>
> 12 juin 2020 à 22:32 de recovery...@enotuniq.net:
>
> > Removing Content-Type (and maybe Content-Transfer-Encoding) from OP's
> > DKIM policy should do the trick, although it can has certain undesirable
> > side-effect
On Fri, Jun 12, 2020 at 11:53:40PM +0300, Reco wrote:
No, the body is not interesting at all here.
What I'm interested in is the result of DKIM check, and that's might be
written in e-mail headers. Or not.
dkim=fail (2048-bit key) reason="fail (body has been altered)"
On 6/11/20 1:24 AM, Dominique Dumont wrote:
On mercredi 10 juin 2020 19:53:53 CEST Gary L. Roach wrote:
The sequence of events on boot up are Bios screen, Debian Window with OS
selection, Boot up sequence, login/password ( Xorg not running), startx
-> error window. So to answer your question, th
Matthew Campbell wrote:
> I hope I don't create a fight with this.
It's really much more rare than your recent experience would
suggest.
> I booted the Debian netinst disc and installed Linux on /dev/sdb1 as the root
> partition. My computer is old. The system BIOS does not see this hard drive,
On 13/6/20 10:58 am, Matthew Campbell wrote:
I hope I don't create a fight with this.
I booted the Debian netinst disc and installed Linux on /dev/sdb1 as
the root partition. My computer is old. The system BIOS does not see
this hard drive, nor does Grub, but the Linux kernel does. I'm runni
On Fri 12 Jun 2020 at 14:22:03 (-0700), Gary L. Roach wrote:
> On 6/11/20 1:24 AM, Dominique Dumont wrote:
> > On mercredi 10 juin 2020 19:53:53 CEST Gary L. Roach wrote:
> > > The sequence of events on boot up are Bios screen, Debian Window with OS
> > > selection, Boot up sequence, login/password
Hello sir
I need full commands for 2020.2 gnu/linux rolling kali tty1
Hi, first thank-you to everyone who replied for taking an interest in
assisting me and improving Debian guides. I feel very lucky to have access
to you folks here with expertise and experience plus the goodwill to help
someone without expecting anything in return.
I will summarise and respond to a
Matthew Campbell wrote:
> I booted the Debian netinst disc and installed Linux on /dev/sdb1 as the
> root partition. My computer is old. The system BIOS does not see this hard
> drive, nor does Grub, but the Linux kernel does. I'm running the
> 4.19.0-9-686-pae kernel, #1 SMP Debian 4.19.118-2 and
ROHIT SONI wrote:
> I need full commands for 2020.2 gnu/linux rolling kali tty1
I need 100,- €
On 2020-06-12 17:58, Matthew Campbell wrote:
I hope I don't create a fight with this.
I booted the Debian netinst disc and installed Linux on /dev/sdb1 as the root partition. My computer is old.
Computer make and model? Processor? RAM module quantity, size, and
slot? HDD makes, models, in
43 matches
Mail list logo
