From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-18.9 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 34DF11F461 for ; Tue, 9 Apr 2024 19:59:56 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=google.com header.i=@google.com header.a=rsa-sha256 header.s=20230601 header.b=ICuhQOvk; dkim-atps=neutral Received: by mail-pl1-x62c.google.com with SMTP id d9443c01a7336-1e411e339b8so20060605ad.3 for ; Tue, 09 Apr 2024 12:59:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1712692794; x=1713297594; darn=public-inbox.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=0cQUyOIvlITFvFOODJeHv599LPuiVGF7yhjLJDTLoIU=; b=ICuhQOvks+g8z9hJdqRWyyE2NQd4LBJ70tn4puC9n0Yz+2+R4HiQCWzhwPCqjt/ySF +gr04s0Y2L1CpvTRAyKUV+gTtW3LpdwnOmAK6y/VGqBD83X59Fh8eUi/5AkODbxKoF4Q dLXzJY1LpFARgVr573kLt9NMbF/2Tzrj9XXdLahk2juh9G6lEhopziIW+ttIhFESNvVh URsyjnWzrRBcuNVJkzV/eLQaIqfLsuABhS944jJ4R1442sEEXCQwqMYTrgdRQPomJjgV sM9jJJalcAebOKzo2KQS18mbqbpCph5cOB16YdHmPlOeRbETogo4ZhksQU40yB67yHvg WCLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712692794; x=1713297594; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=0cQUyOIvlITFvFOODJeHv599LPuiVGF7yhjLJDTLoIU=; b=FExioZ7WrGwd+RF7+wfQ5/BVQXe0zXSlqCCPYh0NVK9OdW6qEE4kw+KmADyfALG0uk 6H2KWNc03zmtPndcwJzEMH+6ARAj86MSkgm5f07KkN9+ac+6L8VxMILFMDoVpL2WtX4y zuACvitKBnVS3tekAyWtH3SY03T9b/Udt63aokI/vsht9DQYOfJ3+G2s8xzovv6tynXI UAXT9htOlEpA5765Xax2sXQJsoP7MBCgtlm3S78OwVYvvevgnGDWFrNAjqemg4NlnoaR vg7LRwomWWW5HlC78JAMkxBR55D/oYFbC7YtsJCar6dBfHxkCwOrZECNDFdH3/RicDsH cWSA== X-Gm-Message-State: AOJu0YyUbBPVUT8T7ZeNa5DWKOqgXyOKVIp7aJDYxX5PxuPcgYRbfjpk Qa4NTNR1jRDnTTZwLPcsrrCHoS5nwp34qIiQ413vv+DxWywcC6No8rYS5jymTJbVqt7k1CZRw6u 01Q== X-Google-Smtp-Source: AGHT+IHnaNdseMkky8rNZkfF09N4rV0CIXKPVCeeZfkluRUjyLzlWmW4X6t/iGAd/lBpntbwkOmBkQ== X-Received: by 2002:a17:902:d58a:b0:1e2:c1fd:7bc9 with SMTP id k10-20020a170902d58a00b001e2c1fd7bc9mr928196plh.8.1712692793941; Tue, 09 Apr 2024 12:59:53 -0700 (PDT) Received: from google.com ([2620:15c:2d3:204:4457:b729:59d8:3a21]) by smtp.gmail.com with ESMTPSA id q3-20020a17090311c300b001e28d7329e6sm9291373plh.91.2024.04.09.12.59.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 09 Apr 2024 12:59:53 -0700 (PDT) Date: Tue, 9 Apr 2024 12:59:48 -0700 From: Josh Steadmon To: Eric Wong Cc: meta@public-inbox.org Subject: Re: v1.9.0 : `ls-search' is not an lei command Message-ID: References: <20240404195504.M179771@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240404195504.M179771@dcvr> List-Id: On 2024.04.04 19:55, Eric Wong wrote: > Josh Steadmon wrote: > > Hello all, > > > > I recently had to reinstall my work machine, and after doing so I now > > get an error when running `lei ls-search`: > > > > `ls-search' is not an lei command > > > > This happens with both version 1.9.0-1+build1 of the Debian "lei" > > package, and with version 1.9.0 of the Nix "public-inbox" package. > > Are you sure the `lei' in $PATH is pointed to the right > installation? > > `lei sucks' should give diagnostic info (or similarly broken if > the lei-daemon is running on an uninstalled version). Thanks for the pointer to `lei sucks'. It reported that lei was for some reason trying to load packages from a prior attempt at installing public-inbox from source, even after deleting the relevant directory. I'm not sure how that happened, since I installed via apt and AFAICT there's nothing in my environment that would tell Perl to look in that location. In any case, `apt-get purge lei` followed by a reinstall worked after deleting the old source directory. Thanks again!