Re: Properly obsoleting old subpackages

2009-04-13 Thread Adeodato Simó
+ Mikhail Gusarov (Tue, 14 Apr 2009 00:59:48 +0700): > AS> You should just stop building them, and the old versions will get > AS> removed from the archive semi-automatically. > Ok, I will just drop the -dbg package. Given it depends on > python-pyinotify (= ${binary:Version}), will it be remov

Re: Properly obsoleting old subpackages

2009-04-13 Thread Mikhail Gusarov
Twas brillig at 19:52:53 13.04.2009 UTC+02 when d...@net.com.org.es did gyre and gimble: >> What is the proper way to handle this change? Should I >> conflict/replace those old packgaes in new python-pyinotify? AS> You should just stop building them, and the old versions will get AS> remove

Re: Properly obsoleting old subpackages

2009-04-13 Thread Adeodato Simó
+ Mikhail Gusarov (Mon, 13 Apr 2009 17:42:06 +0700): > Hi, Hello, Mikhail. > I've got source package (pyinotify) with 3 binary packages built from > it: python-pyinotify, python-pyinotify-dbg and python-pyinotify-doc. > In new upstream release author dropped the binary module (hence there is >

Properly obsoleting old subpackages

2009-04-13 Thread Mikhail Gusarov
Hi, I've got source package (pyinotify) with 3 binary packages built from it: python-pyinotify, python-pyinotify-dbg and python-pyinotify-doc. In new upstream release author dropped the binary module (hence there is no need for python-pyinotify-dbg) and moved all documentation to wiki (so python-