public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: H <agents-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Installing new tarball over old?
Date: Sat, 20 May 2023 15:31:42 -0400	[thread overview]
Message-ID: <108b5469-1015-c99a-d9fb-707a37783255@meddatainc.com> (raw)
In-Reply-To: <3FA2FEE1-20E9-40BA-B6C1-A39F49EE2EB1-FcZObrvlYduBUy7/sJONFg@public.gmane.org>

On 05/19/2023 08:49 PM, H wrote:
> Oh, maybe I should just open the tarball, see which files it contains and delete them from the installation? Or is there a simpler way? 

Once I did the above, it was easy to see what had been installed and remove those files.

However, after installing the most recent release 3.1.2 I find that I cannot run it on my computer which is running CentOS 7. It complains:

-bash: /usr/local/bin/pandoc: cannot execute binary file

Does this release require some additional components I need to install as well? As noted previously, pandoc 2.19.2 ran fine.


  parent reply	other threads:[~2023-05-20 19:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 18:56 H
     [not found] ` <3ce85797-6037-9c37-1234-a583227a5f2c-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-17  5:28   ` ThomasH
     [not found]     ` <0670a3f2-69f7-4a91-b6b5-145511c273ebn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-17 20:52       ` H
     [not found]         ` <f1db6da5-7788-7288-3397-5d8f45cebfbb-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-19  7:34           ` ThomasH
     [not found]             ` <828651d0-3853-4d7a-a7c5-f0157a979737n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-20  0:43               ` H
     [not found]                 ` <4A09BC61-8F5C-4AD9-A703-3089E51EEE58-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-20  0:49                   ` H
     [not found]                     ` <3FA2FEE1-20E9-40BA-B6C1-A39F49EE2EB1-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-20  1:05                       ` John Gabriele
2023-05-20 19:31                       ` H [this message]
     [not found]                         ` <108b5469-1015-c99a-d9fb-707a37783255-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-20 22:58                           ` John MacFarlane
     [not found]                             ` <77D4EA6A-C0B5-41F2-B320-215958C215E8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-05-21  0:24                               ` H
2023-05-20  0:44   ` John Gabriele
  -- strict thread matches above, loose matches on Subject: below --
2023-05-16  1:39 H

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

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

  git send-email \
    --in-reply-to=108b5469-1015-c99a-d9fb-707a37783255@meddatainc.com \
    --to=agents-fczobrvlydubuy7/sjonfg@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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 NNTP newsgroup(s).