You can end up getting something like this to look at http://qa.ubuntuwire.com/uehs/no_updated.html
On Tue, Aug 5, 2008 at 3:09 PM, andres vargas (zodman) <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > http://www.debian-administration.org/articles/516 > exist a tool for do it on debian.. > > Needs something like read from the recipe the r.addArchive() > > and check for the last version > > > > Eric Lake escribió: > | The thing is how do we implement something like this. It should be > | automated someway. Maybe it could read the addArchive line in the > | recipe and check that for a new version that is higher than the > | version line.This would only have to check against the 2-devel repo > | too since we would first update there and then promote. > | > | On Tue, Aug 5, 2008 at 2:16 PM, Jack Doerner <[EMAIL PROTECTED]> > wrote: > |> I very much like the idea of a debian watch like system (I > |> periodically check my own packages, but they're not official)... > |> Perhaps packages could have a maintainer, but don't necesserely have > |> to... like assigning to distro in jira? > |> > |> Jack Doerner > |> > |> There are worse crimes than burning books > |> One of them is not reading them. > |> -Joseph Brodsky > |> > |> > |> > |> On Tue, Aug 5, 2008 at 12:55 PM, Eric Lake > <[EMAIL PROTECTED]> wrote: > |>> Is there a way that we can create a system like the debian to watch > |>> upstream for new versions being released of packages in the repo? > |>> Debian uses watch files to do this and they have a web site that shows > |>> all of the packages that are behind in version. I'm not really sure > |>> how we could do something like this with the foresight repos though. > |>> The last thing I think that we would want is for the end users to tell > |>> us that a package that they really want to use is not up to date. > |>> > |>> Also, should we create a maintainers list? Something that would assign > |>> a packager / dev to a package. Then that person is responsible for > |>> keeping the package up to date. The hard part would be if the packager > |>> ever left foresight then we would have to have a list of the packages > |>> assigned to them and reassign them to different people. > |>> > |>> -- > |>> Thanks, > |>> > |>> Eric Lake > |>> _______________________________________________ > |>> Foresight-devel mailing list > |>> Foresight-devel@lists.rpath.org > |>> http://lists.rpath.org/mailman/listinfo/foresight-devel > |>> > |> _______________________________________________ > |> Foresight-devel mailing list > |> Foresight-devel@lists.rpath.org > |> http://lists.rpath.org/mailman/listinfo/foresight-devel > |> > | > | > | > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (GNU/Linux) > > iEYEARECAAYFAkiYpVwACgkQ/HaI43/WxAEvuQCg5RfICARZnN3uAae/7jIY4lUt > iQAAoMORUZNgn/7hewrPc6IV/cGrAb45 > =qCfl > -----END PGP SIGNATURE----- > -- Thanks, Eric Lake _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
