Bug#782677: udd: scripts/update-upstream-status: should consider sepwatch
On Tue, Jun 30, 2015 at 08:15:49PM +0200, Lucas Nussbaum wrote:
> On 30/06/15 at 17:47 +0000, Bart Martens wrote:
> > > How different is mole's data schema from UDD's?
> >
> > I guess you already have access to UDD's data schema. Can you access mole.watch
> > with what you read in udd-dehs?
>
> It seems that udd-dehs doesn't keep track of both unstable and
> experimental. Some packages track different branches and different
> suites, and thus have different watch files.
Good point. I see that mole.watch contains more info than udd-dehs extracts, so
a variant of udd-dehs could extract more.
>
> Also, I'm surprised that the executable is named
> 'uscan-without-pgpsigurlmangle'. Does it mean that it doesn't check PGP
> signatures even when a signing key is provided? That sounds like a bad
> idea.
That sounds worse than it is. We've been fine without pgpsigurlmangle for many
years, and most watch files still don't have pgpsigurlmangle. Adapting
watch-worker to extract the key as well is certainly worth considering.
Regards,
Bart Martens
Reply to: