Usenet

Usenet

[Emanuel Berg]

Hello party people! Since the last time you heard from
me I lost some friends. Well, hell. Now I'm even more
disillusioned about the whole state of the pitch dark
computer industry. It is unbelievable that the kids
today use more advanced stuff and with more skill than
the supposedly professional people who make their
living out of it. Can you imagine the NHL stars still
playing with wood, while the kids outside your
residence play with composite sticks (say 50% graphite
with 50% fiberglass) when they shoot the puck and
crash your car window? On the third hand, I always
said the pro athletes were a bunch of spoilt kids, so
I suppose they have it together there as well as with
computers. Anyway this was a parenthesis. In another
group, I just read and posted the following. It would
be interesting to hear if it is a correct assessment
of the situation. If it is, it is yet another example
of how supreme technology don't mean nada, unless
picked up and carried by dedicated people. Or even by
a bunch of spoilt kids.

    Usenet died, not RSB. It's a shame about Usenet.

Usenet is about as alive as RSB and at points
more alive.

I get RSB from nntp.aioe.org which is a real Usenet,
NNTP server. As we all see, it is very operational. (I
also get rec.bicycles.tech from them and that group is
very active at that, with 272 messages since last
I checked.)

For all the other stuff that would once have been
Usenet, and now are mailing lists, I use Emacs Gnus
and Gmane which turn it all into Usenet in all
essence, at least in terms of the interface. Here are
a couple of examples:

    gmane.comp.graphics.gnuplot.user
    gmane.comp.shells.zsh.user
    gmane.emacs.erc.general
    gmane.emacs.gnus.general
    gmane.emacs.gnus.user

While this seems to work very well for technology and
in particular computer technology, I never found
people really doing it with my other interests. (The
bicycle group is perhaps the exception that proves the
rule, however obviously that is technology too.)

With boxing there is RSB but the problem is if there
are ~ten people writing, at best traffic will be very
low, and at worse cabin fever will set in...

I always thought of Usenet as virtually what I have
today in terms of technology (with Emacs Gnus and
Gmane), *but* including many other aspects of life as
well. And that, I never did find and I doubt
it exists.

-- 
underground experts united .... http://user.it.uu.se/~embe8573
Emacs Gnus Blogomatic ......... http://user.it.uu.se/~embe8573/blogomatic
                   - so far: 25 Blogomatic articles -                   

Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent

[Nicky Chorley]

Hi all,

I'm running Emacs 25.3.1 on Slackware Linux 14.2 and `M-x
package-refresh-contents` is giving the following error:

Failed to verify signature archive-contents.sig:
Bad signature from 474F05837FBDEF9B GNU ELPA Signing Agent
<elpasign@elpa.gnu.org>
Command output:
gpg: Signature made Fri 08 Feb 2019 10:15:04 PM GMT using DSA key ID 7FBDEF9B
gpg: BAD signature from "GNU ELPA Signing Agent <elpasign@elpa.gnu.org>"

I don't recall changing anything in my config recently. Just to see if
that was causing a problem, I did remove my config (.emacs and
.emacs.d), but the problem persisted.

Any ideas about what's causing this?

Thanks,

Nicky Chorley

Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent

[Robert Pluim]

Nicky Chorley <nick.chorley@gmail.com> writes:

> Hi all,
>
> I'm running Emacs 25.3.1 on Slackware Linux 14.2 and `M-x
> package-refresh-contents` is giving the following error:
>
> Failed to verify signature archive-contents.sig:
> Bad signature from 474F05837FBDEF9B GNU ELPA Signing Agent
> <elpasign@elpa.gnu.org>
> Command output:
> gpg: Signature made Fri 08 Feb 2019 10:15:04 PM GMT using DSA key ID 7FBDEF9B
> gpg: BAD signature from "GNU ELPA Signing Agent <elpasign@elpa.gnu.org>"
>
> I don't recall changing anything in my config recently. Just to see if
> that was causing a problem, I did remove my config (.emacs and
> .emacs.d), but the problem persisted.
>
> Any ideas about what's causing this?

My crystal ball says youʼre using http to download the archives. Try
switching to https.

If that solves it you have a broken proxy somewhere between you and
the package archive server.

Robert

Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent

[Stefan Monnier]

> I'm running Emacs 25.3.1 on Slackware Linux 14.2 and `M-x
> package-refresh-contents` is giving the following error:
>
> Failed to verify signature archive-contents.sig:

FWIW, the build scripts on elpa.gnu.org can occasionally end up with
a stale .sig for a short amount of time (known problem that we should
fix, obviously, but not high enough on the todo list), so maybe you just
got unlucky.

In any case, please report those problems via `M-x report-emacs-bug`.


        Stefan

Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent

[Nicky Chorley]

I tried switching to HTTPS for the GNU ELPA repository as well, but
that didn't help either and I'm still getting the error. Again, just
clearing my .emacs.d doesn't help. Is there another cache somewhere
that I should try clearing, or does anyone have any other suggestions?

Best,

Nicky

On Sat, 9 Feb 2019 at 08:46, Nicky Chorley <nick.chorley@gmail.com> wrote:
>
> Hi all,
>
> I'm running Emacs 25.3.1 on Slackware Linux 14.2 and `M-x
> package-refresh-contents` is giving the following error:
>
> Failed to verify signature archive-contents.sig:
> Bad signature from 474F05837FBDEF9B GNU ELPA Signing Agent
> <elpasign@elpa.gnu.org>
> Command output:
> gpg: Signature made Fri 08 Feb 2019 10:15:04 PM GMT using DSA key ID 7FBDEF9B
> gpg: BAD signature from "GNU ELPA Signing Agent <elpasign@elpa.gnu.org>"
>
> I don't recall changing anything in my config recently. Just to see if
> that was causing a problem, I did remove my config (.emacs and
> .emacs.d), but the problem persisted.
>
> Any ideas about what's causing this?
>
> Thanks,
>
> Nicky Chorley

Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent

[Jude DaShiell]

I had problems with that earlier too.
It was because I didn't have the latest tls package installed.
This didn't used to be necessary but now appears necessary.

On Sat, 9 Mar 2019, Nicky Chorley wrote:

> Date: Sat, 9 Mar 2019 01:52:18
> From: Nicky Chorley <nick.chorley@gmail.com>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Unable to use `package-refresh-contents`: Bad signature from GNU
>     ELPA Signing Agent
>
> I tried switching to HTTPS for the GNU ELPA repository as well, but
> that didn't help either and I'm still getting the error. Again, just
> clearing my .emacs.d doesn't help. Is there another cache somewhere
> that I should try clearing, or does anyone have any other suggestions?
>
> Best,
>
> Nicky
>
> On Sat, 9 Feb 2019 at 08:46, Nicky Chorley <nick.chorley@gmail.com> wrote:
> >
> > Hi all,
> >
> > I'm running Emacs 25.3.1 on Slackware Linux 14.2 and `M-x
> > package-refresh-contents` is giving the following error:
> >
> > Failed to verify signature archive-contents.sig:
> > Bad signature from 474F05837FBDEF9B GNU ELPA Signing Agent
> > <elpasign@elpa.gnu.org>
> > Command output:
> > gpg: Signature made Fri 08 Feb 2019 10:15:04 PM GMT using DSA key ID 7FBDEF9B
> > gpg: BAD signature from "GNU ELPA Signing Agent <elpasign@elpa.gnu.org>"
> >
> > I don't recall changing anything in my config recently. Just to see if
> > that was causing a problem, I did remove my config (.emacs and
> > .emacs.d), but the problem persisted.
> >
> > Any ideas about what's causing this?
> >
> > Thanks,
> >
> > Nicky Chorley
>
>

-- 

Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent

[Stefan Monnier]

> It was because I didn't have the latest tls package installed.
> This didn't used to be necessary but now appears necessary.

I don't know of any `tls.el` package other than a very old one that
should be considered deprecated nowadays (and still comes bundled with
Emacs in `lisp/obsolete/tls.el`).  The SSL/TLS handling in Emacs
nowadays is handled by the libgnutls code, so it doesn't require any
Elisp package.  If that doesn't work well for you please `M-x
report-emacs-bug`.


        Stefan

Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent

[Jude DaShiell]

I should have been more transparent, the tls package I installed came
from the slint repository not any part of emacs.

On Sat, 9 Mar 2019, Stefan Monnier wrote:

> Date: Sat, 9 Mar 2019 15:15:56
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Unable to use `package-refresh-contents`: Bad signature from GNU
>     ELPA Signing Agent
>
> > It was because I didn't have the latest tls package installed.
> > This didn't used to be necessary but now appears necessary.
>
> I don't know of any `tls.el` package other than a very old one that
> should be considered deprecated nowadays (and still comes bundled with
> Emacs in `lisp/obsolete/tls.el`).  The SSL/TLS handling in Emacs
> nowadays is handled by the libgnutls code, so it doesn't require any
> Elisp package.  If that doesn't work well for you please `M-x
> report-emacs-bug`.
>
>
>         Stefan
>
>
>

-- 

usenet

[qqk8]

Don't look this. I'm newbie and I don't know English and how to use usenet.

Re: usenet

[Emanuel Berg]

qqk8 wrote:

> Don't look this. I'm newbie and I don't know
> English and how to use usenet.

Priviet!

First, your English is good enough. Second,
this isn't Usenet. There were once a thriving
Usenet group called gnu.emacs.help (which still
exists) - actually, there were/are many
Emacs-related groups on Usenet. However I would
not recommend them to anyone.

Now there is a mailing list
(help-gnu-emacs@gnu.org) and with Gmane, you
can access it thru gmane.emacs.help *as if it
was a Usenet newsgroup*!

The reason for all this is, in terms of
technology Usenet is great, but the people just
got worse and worse. When all that remains are
insults and off-topic chatter the reasonable
people moved away, which of course just made
the Usenet situation worse. Now, there are so
many spammers and flamers and people who tell
their personal senile stories over and over so
Usenet has really ceased to be useful, despite
its name.

Some groups are better than other, but this is
the general trend, and it is a broad one.
Since very, very few new people come to Usenet,
the situation isn't likely to improve - on the
contrary.

Also, even if you are are person who aren't
like "them" - if you spend too much time with
them, that's who you will be, sooner or later,
no matter how strong you are. It is inevitable.

If you want to try the real deal, i.e. the old
and still existing Usenet, be very wary when
entering a group. What is the mood here?
Is this really a place I like? And don't for
a minute think that *you* can influence the
rest of the gang by being
polite/professional/whatever. Just leave at the
first insult! It is not going to get better -
on the contrary...

That is why most people prefer the mailing list
(listbot) approach. But if you are attracted to
the Usenet interface/architecture, check out
Gmane, which I like to call Usenet 2.0 or
"Usenet Reloaded". It is the best of both
worlds :)

-- 
underground experts united
http://user.it.uu.se/~embe8573

Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent

[Nicky Chorley]

Well, I upgraded GnuTLS to 3.6.7 (the latest in Slackware's repos),
but nothing changed. I also tried building the latest version of Emacs
(26.2) just to see if it made a difference, but it didn't.

I also realised that my version of GnuPG 2 is quite old, but don't
know what else is using that. So, I just tried
package-refresh-contents on Emacs 26.2 on a Fedora 30 install (albeit
inside a Docker container), which has a much newer version of GnuPG 2
(2.2.13). The same problem occurred.

This is extremely frustrating!

On Sat, 9 Mar 2019 at 07:57, Jude DaShiell <jdashiel@panix.com> wrote:
>
> I had problems with that earlier too.
> It was because I didn't have the latest tls package installed.
> This didn't used to be necessary but now appears necessary.
>
> On Sat, 9 Mar 2019, Nicky Chorley wrote:
>
> > Date: Sat, 9 Mar 2019 01:52:18
> > From: Nicky Chorley <nick.chorley@gmail.com>
> > To: help-gnu-emacs@gnu.org
> > Subject: Re: Unable to use `package-refresh-contents`: Bad signature from GNU
> >     ELPA Signing Agent
> >
> > I tried switching to HTTPS for the GNU ELPA repository as well, but
> > that didn't help either and I'm still getting the error. Again, just
> > clearing my .emacs.d doesn't help. Is there another cache somewhere
> > that I should try clearing, or does anyone have any other suggestions?
> >
> > Best,
> >
> > Nicky
> >
> > On Sat, 9 Feb 2019 at 08:46, Nicky Chorley <nick.chorley@gmail.com> wrote:
> > >
> > > Hi all,
> > >
> > > I'm running Emacs 25.3.1 on Slackware Linux 14.2 and `M-x
> > > package-refresh-contents` is giving the following error:
> > >
> > > Failed to verify signature archive-contents.sig:
> > > Bad signature from 474F05837FBDEF9B GNU ELPA Signing Agent
> > > <elpasign@elpa.gnu.org>
> > > Command output:
> > > gpg: Signature made Fri 08 Feb 2019 10:15:04 PM GMT using DSA key ID 7FBDEF9B
> > > gpg: BAD signature from "GNU ELPA Signing Agent <elpasign@elpa.gnu.org>"
> > >
> > > I don't recall changing anything in my config recently. Just to see if
> > > that was causing a problem, I did remove my config (.emacs and
> > > .emacs.d), but the problem persisted.
> > >
> > > Any ideas about what's causing this?
> > >
> > > Thanks,
> > >
> > > Nicky Chorley
> >
> >
>
> --
>

Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent

[Van L]

Nicky Chorley <nick.chorley@gmail.com> writes:

￨ Well, I upgraded GnuTLS to 3.6.7 (the latest in Slackware's repos),
￨ but nothing changed. I also tried building the latest version of Emacs
￨ (26.2) just to see if it made a difference, but it didn't.
￨
￨ I also realised that my version of GnuPG 2 is quite old, but don't
￨ know what else is using that. So, I just tried
￨ package-refresh-contents on Emacs 26.2 on a Fedora 30 install (albeit
￨ inside a Docker container), which has a much newer version of GnuPG 2
￨ (2.2.13). The same problem occurred.
￨
￨ This is extremely frustrating!

Is the 'gnu-elpa-keyring-update' package any help?

The blurb says,

--8<---------------cut here---------------start------------->8---
This package updates the GPG keys used by the ELPA package manager
(a.k.a `package.el') to verify authenticity of packages downloaded
from the GNU ELPA archive.
--8<---------------cut here---------------end--------------->8---



-- 
© 2019 Van L
gpg using EEF2 37E9 3840 0D5D 9183  251E 9830 384E 9683 B835
           "you have to be Albert Einstein to figure it out" - Donald J. Trump