user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
To: Jonathan Corbet <>
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: <>

Jonathan Corbet <> wrote:
> On Sun, 5 May 2019 03:39:47 +0000
> Eric Wong <> wrote:
> > Eric Wong <> 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/
from perl-TimeDate-2.30-2.el7.noarch

Btw, I also got IO/Compress/ from
(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:

> [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

      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:

  List information:

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

  git send-email \
    --in-reply-to=20190510202351.c3xrb7xzyc755vkp@dcvr \ \ \ \

* 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

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).