* New upstream release
- Drop the usage of threading.Thread and ensure the multiprocessing.Pool
is closed after the job is complete, this greatly reduces the system
load and stops the aggressive polling multiprocessing worker pools
used (LP: #906916)
- ported to libdee API changes
- ported to libunity API changes
* debian/gwibber-service.pyinstall, debian/gwibber-service.install
- Use a .pyinstall file to handle instaling stuff so we don't have to
copy custom.py
* debian/rules
- drop the copy of custom.py, it gets installed with .pyinstall file now
* debian/control
- bump build depends for libunity-dev and libdee-dev
- renamed build dep to gtkspell-3-dev
-- Ken VanDine <email address hidden> Fri, 13 Jan 2012 12:38:23 +0100
This bug was fixed in the package gwibber - 3.3.2-0ubuntu1
---------------
gwibber (3.3.2-0ubuntu1) precise; urgency=low
* New upstream release .Pool gwibber- service. pyinstall, debian/ gwibber- service. install
- Drop the usage of threading.Thread and ensure the multiprocessing
is closed after the job is complete, this greatly reduces the system
load and stops the aggressive polling multiprocessing worker pools
used (LP: #906916)
- ported to libdee API changes
- ported to libunity API changes
* debian/
- Use a .pyinstall file to handle instaling stuff so we don't have to
copy custom.py
* debian/rules
- drop the copy of custom.py, it gets installed with .pyinstall file now
* debian/control
- bump build depends for libunity-dev and libdee-dev
- renamed build dep to gtkspell-3-dev
-- Ken VanDine <email address hidden> Fri, 13 Jan 2012 12:38:23 +0100