unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mike <michael@rmrco.com>
To: libc-alpha@sourceware.org
Subject: C-kermit fails
Date: Fri, 24 Jul 2020 09:29:02 -0700	[thread overview]
Message-ID: <10CAD3CD-0170-4182-A920-EE825EBAF6B0@rmrco.com> (raw)

Hi,

I normally install kermit on my Linux Ubuntu PC with the command
  sudo apt-get install ckermit

Now I get the message "E: Package 'ckermit' has no installation candidate"

Has something changed?

I sent this messagee to the C-kermit developer, Frank da Cruz (fdc@columbia.edu) and he said the following:
--------------
Apparently glibc was changed in a way that broke C-Kermit,
so the reaction of Linux packagers was to remove C-Kermit
from their distribution.  Somebody else wrote me about
this earlier today concerning Debian:

Debian's "solution" to the problem was to drop the package
after the initial bug was filed, without contacting
upstream about it at all(!), hence presumably why this is
news to you. I've done some digging, and it appears glibc
is to blame (they removed an interface in 2.28). This
patch from gentoo, which also apparently didn't think
about telling you (sigh) appears to fix it:

https://685096.bugs.gentoo.org/attachment.cgi?id=589698

I have verified that it compiles now. 

The right thing to do would be to encourage the glibc
people to put back the symbol that they deleted.  Because
if this change broke C-Kermit, it's likely to have broken
a lot more applications.
--------------------

This is all above my skill level. Can someone out there help me? This is a critical need.

—————————————
R. Michael Reynolds, mobile/text: 631-374-2537  michael@rmrco.com
Remote Measurements & Research Co.,  214 Euclid Ave., Seattle WA 98122
—————————————


             reply	other threads:[~2020-07-24 16:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 16:29 Mike [this message]
2020-07-24 16:33 ` C-kermit fails Florian Weimer
2020-07-24 17:36 ` Zack Weinberg
2020-07-24 18:47   ` Paul Eggert
2020-07-24 19:41     ` Frank da Cruz
2020-07-24 19:45       ` Frank da Cruz
2020-07-24 20:05       ` Zack Weinberg
2020-07-27  8:10         ` Florian Weimer via Libc-alpha
2020-07-24 21:07       ` Paul Eggert
2020-07-24 23:45         ` Frank da Cruz
2020-07-25  1:59           ` Paul Eggert
2020-07-31 12:41           ` Maciej W. Rozycki
2020-07-31 18:22             ` Frank da Cruz
2020-07-31 20:23               ` Paul Eggert
2020-08-01  0:17                 ` Frank da Cruz
2020-08-01  8:07                   ` Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=10CAD3CD-0170-4182-A920-EE825EBAF6B0@rmrco.com \
    --to=michael@rmrco.com \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).