where to report out-of-date jigdo package references?

[Robert P. J. Day]

On Tue, 10 Mar 2009, Mail Lists wrote:

> On 03/10/2009 07:01 PM, Robert P. J. Day wrote:
>
> >> Correct.
> >   that doesn't appear to work, as rerunning the "pyjigdo" command
> > restarts *everything*, including downloading the original jigdo file.
> > and i don't see a pyjigdo option that says "resume" or something like
> > that.  am i just not seeing it?
>
>   May I suggest that you dont use jigdo - just use mock/pungi - you wont
> have this problem and will get a build with all the updates as of today.

  ok, i'll take a look at that.  i'm still interested in whether
pyjigdo should work, and how one copes with an out-of-date package in
the jigdo list.  the suggestion was to edit the .jigdo file so i'm
going to try that right away, but if anyone else is interested in
playing along, pull out your F10 DVD, install pyjigdo and see how far
you get in trying to build your own re-spin.

  is this supposed to work?  i'm just curious.

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================