apt-zeroconf team mailing list archive

[jeremy austin-bardo <ausimage@xxxxxxxxxx>]

AZC team...
Jcastro, yesterday had an issue with azc running on karmic. It turns out
that there are significant changes to pyinotify
<http://trac.dbzteam.org/pyinotify/wiki/LastDevelopments>. Essentially
the namespace has been simplified and what needs to be adjusted is in
the doc string for AptWatcher.Init() in the apt module. (I am using
jaunty ATM). This change also means that either azc is only for karmic
forward or a work-around needs to be found. Also, we should double check
the class that extends pyinotify is in best current practice as well.

I am also slowly getting through the code base and finishing first round
of comments and light factoring which could use a hand with review and
improvement. I am also going to need help deciding what to do with the
cache back-end--Should it stay or be replaced with something better? I
am concerned with the reliability of using a user's local apt cache. I
want some level of guarantee that a package's origin matches. Any ideas?

-- 
jeremy austin-bardo <ausimage@xxxxxxxxxx>
Ubuntu Communty Member

Attachment: signature.asc
Description: This is a digitally signed message part