Re: Jigdo search still broken.
- To: Philip Hands <firstname.lastname@example.org>
- Cc: Richard Atterer <email@example.com>, Steve McIntyre <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com
- Subject: Re: Jigdo search still broken.
- From: Simon Paillard <firstname.lastname@example.org>
- Date: Thu, 11 Nov 2010 20:01:35 +0100
- Message-id: <20101111190135.GR14352@glenfiddich.ikibiki.org>
- Mail-followup-to: Philip Hands <email@example.com>, Richard Atterer <firstname.lastname@example.org>, Steve McIntyre <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- In-reply-to: <email@example.com>
- References: <20101004134756.GA3032@newton> <20101006132942.GD14924@einval.com> <20101006213344.GA24095@meeep.lan> <firstname.lastname@example.org>
As we've just got another report about jigdo search, I wonder if there are
updates about moving this service to get it operationnal.
FYI this is tracked by #589477.
On Thu, Oct 07, 2010 at 02:26:30PM +0100, Philip Hands wrote:
> On Wed, 6 Oct 2010 23:33:45 +0200, Richard Atterer <email@example.com> wrote:
> > On Wed, Oct 06, 2010 at 02:29:42PM +0100, Steve McIntyre wrote:
> > > On Mon, Oct 04, 2010 at 03:47:56PM +0200, thorres wrote:
> > > >the search for packages inside the jigdo files still does not work an
> > > >and leads to a 404 error.
> > > >(http://atterer.org/jigdo/jigdo-search.php?q=foo)
> > >
> > > ACK. We should move that content onto a proper Debian service.
> > > Richard, can you help with that?
> > Hi - sorry that the search went offline, it happened when I moved servers
> > and I never fixed it. But this should have been on a Debian server in the
> > first place...
> > The setup consists of a cron job to mirror .jigdo files (which could be
> > omitted if we set this up on cdimage) and a PHP file. Is PHP OK for Debian
> > machines? IIRC perl was preferred...
> Hi Richard,
> You could run it on free.hands.com (where you already have an account),
> which for the moment has PHP on it. I now have that on a VM and would
> at some point want to shift the PHP stuff onto a separate VM, so if we
> do that it would be wise to come up with a URL that would survive being
> shifted onto a new machine at some point. That could of course be done
> by having nginx on free proxy through to the new machine.
> If it's more practical to do it elsewhere, that's great, but thought I'd
> mention this option as it seems likely to be the least effort.