-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Christoph Berg wrote:
Cc'ing me in mails like that makes it a bit earlier for me to actually spot the mail. I only found it now when browsing the hobbitmon-devel list archives...
Hopefully that means you wanted me to CC you on this :)
Right. The reason I had decided not to apply this patch to the Debian package is that it is just a big blob. There are some separate patches for individual features/bugfixes, but it also includes random other fixes. It is also not versioned. There is no real way to track which particular bug is fixed in what instance.
The publically available svn repository is a big step forward as now there's a way to see the diffs and log messages for changes. I am working on uploading a new svn snapshot to the experimental branch of Debian, but have some lose ends left before the next upload.
The next Debian release (5.0, Lenny) will release with the current 4.2.0 packages. Of course, there will be backports of future packages for Lenny.
Might I suggest the standard Debian practice should be applied? ie, if it is a bug-fix patch or security patch, then it should be applied and a new version released. If it is a feature add/improvement, then it should be added to the version for testing.
I understand right now it is probably difficult to get updated packages in for the Lenny release, but perhaps after Lenny is released you could upload this package for Lenny with all the bug-fix allinone patches applied?
Mostly, I would like to see the new version 5.2.2 released in Lenny, but it is too late for that now :(
Regards, Adam
Adam Goryachev Website Managers www.websitemanagers.com.au -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkkbsp8ACgkQGyoxogrTyiVNXwCdEpXydQxPK3evV9Qg7Vt1Gvb6 ROUAn0zZPJWaw/3eSSmQTiW9qSU8c/3A =ng+C -----END PGP SIGNATURE-----