From: Eric Wong <e@80x24.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: meta@public-inbox.org
Subject: Re: Date::Parse RPM dependency? [was: fix Date::Parse dependency for Debian]
Date: Fri, 10 May 2019 20:23:51 +0000 [thread overview]
Message-ID: <20190510202351.c3xrb7xzyc755vkp@dcvr> (raw)
In-Reply-To: <20190510095349.60799aeb@lwn.net>
Jonathan Corbet <corbet@lwn.net> wrote:
> On Sun, 5 May 2019 03:39:47 +0000
> Eric Wong <e@80x24.org> wrote:
>
> > Eric Wong <e@80x24.org> wrote:
> > > -* Date::Parse deb: libdatetime-perl
> > > +* Date::Parse deb: libtimedate-perl
> > > rpm: perl-Time-ParseDate
> >
> > Btw, I think the RPM should be perl-TimeDate (current is 2.30),
> > there; too. It's also p5-TimeDate on the FreeBSD I'm setting up.
>
> I actually have both on the system I'm running. Would have to dig in to
> see which one (or possibly both) is really necessary.
Thanks for the response. On my CentOS 7 chroot, I got Date/Parse.pm
from perl-TimeDate-2.30-2.el7.noarch
Btw, I also got IO/Compress/Gzip.pm from
perl-IO-Compress-2.061-2.el7.noarch;
(not perl-PerlIO-gzip, which seems to be for "IO Layers" and
AFAIK not commonly used)
I've only managed to use rinse 3.4 successfully to get CentOS 7
going, but CentOS 7 seems to lack Xapian Perl bindings
(Search::Xapian module) :<
rinse seems to misconfigure yum on the postinstall for Fedora-28;
(or maybe Fedora 28 is too old?).
29 and 30 are both missing so I filed a bug about it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928679
> [I'm way behind in all things public-inbox, been overwhelmed by
> other things. I do intend to start paying more attention in the near
> future...]
No worries. I'm way behind on most things, too :x
prev parent reply other threads:[~2019-05-10 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 11:44 [PATCH] INSTALL: fix Date::Parse dependency for Debian Eric Wong
2019-05-05 3:39 ` Date::Parse RPM dependency? [was: fix Date::Parse dependency for Debian] Eric Wong
2019-05-10 15:53 ` Jonathan Corbet
2019-05-10 20:23 ` Eric Wong [this message]
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190510202351.c3xrb7xzyc755vkp@dcvr \
--to=e@80x24.org \
--cc=corbet@lwn.net \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).