Your message dated Thu, 17 Jun 2010 22:05:06 +0200
with message-id <[email protected]>
and subject line Re: Bug#580017: osmo uses gtkhtml2
has caused the Debian Bug report #580017,
regarding osmo: uses deprecated libgtkhtml2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
580017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580017
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: osmo
Version: 0.2.10-1
Severity: important
User: [email protected]
Usertags: oldlibs libgtkhtml2
osmo currently still uses libgtkhtml2, either directly or through the
Python bindings. However, libgtkhtml2 is not really maintained
upstream. After being in maintenance mode since 2005, it has not seen
any new release for 2 years now.
I’d like to remove libgtkhtml2 packages before the squeeze release.
This can only be done by getting rid of as much as possible of the
reverse dependencies.
For this to happen, the packages have to be migrated to another HTML
rendering engine. There is gtkhtml3 of course, and now there is
webkit, which is superior in terms of features and not too far from
libgtkhtml2 in terms of API.
I suggest that you migrate osmo as soon as possible to use webkit for
rendering. For most packages, which use libgtkhtml2 in a simple way,
porting should be trivial.
I’d like to add a specific note. When upstream *starts* to use something
like gtkhtml2 in 2010, that poses serious questions as to their ability
to make development choices.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “If you behave this way because you are blackmailed by someone,
`- […] I will see what I can do for you.” -- Jörg Schilling
--- End Message ---
--- Begin Message ---
Version: 0.2.10+svn898-1
this bug was fixed in the last upload, forgot to close it in changes...
--- End Message ---