Your message dated Sat, 6 Apr 2013 00:46:12 +0100 with message-id <CAPQ4b8=2+-x4vdyg1ue6zpxj6ppd2stk+opncrnzl9qadt_...@mail.gmail.com> and subject line Closing orphan (obsolete?) bugs in gtkhtml3.8 has caused the Debian Bug report #200740, regarding gtkhtml3.0: Invalid comments in generated HTML? 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.) -- 200740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=200740 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gtkhtml3.0 Version: 3.0.4-3 Severity: normal Hello, I've noticed a strange behavior in HTML mails generated by evolution: - the DOCTYPE definition is not well accepted by the w3c HTML validator (missing URL to the DTD?) - Extra tags for GtkHTML, which look like <!--+GtkHTML:<DATA class="ClueFlow" key="orig" value="0"> produce a problem in both w3m and lynx: the comment is not properly closed (AFAIK, by looking at the w3m specs), and the whole message disappears in the comment... Writing the comment with a terminal --> fixes the problem for w3m and lynx. As I'm not a HTML expert, I'm only guessing that these are actual problems. Best regards. Frédéric -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux amazon 2.4.18 #2 Wed Apr 3 12:08:30 CEST 2002 i686 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages gtkhtml3.0 depends on: ii bonobo-activation 1:2.2.2-1 Bonobo Activation Framework ii libart-2.0-2 2.3.12-1 Library of functions for 2D graphi ii libatk1.0-0 1.2.4-1 The ATK accessibility toolkit ii libbonobo-activation4 1:2.2.2-1 Bonobo Activation Framework -- run ii libbonobo2-0 2.2.3-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.2.2-1 The Bonobo UI library ii libc6 2.3.1-16 GNU C Library: Shared libraries an ii libgal2.0-3 1.99.7-1 G App Libs (run time library) ii libgconf2-4 2.2.1-1 GNOME configuration database syste ii libglade2-0 2.0.1-3 Library to load .glade files at ru ii libglib2.0-0 2.2.2-1 The GLib library of C routines ii libgnome2-0 2.2.0.1-2 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.2.0.2-1 A powerful object-oriented display ii libgnomeprint2.2-0 2.2.1.2-1 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.2.1.2-1 The GNOME 2.2 print architecture U ii libgnomeui-0 2.2.0.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.2.5-2 The GNOME virtual file-system libr ii libgtk2.0-0 2.2.1-6 The GTK+ graphical user interface ii libgtkhtml3.0-2 3.0.5-1 HTML rendering/editing library - r ii liblinc1 1:1.1.0-1 library to simplify creating netwo ii liborbit2 1:2.6.1-1 Libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.2.1-3 Layout and rendering of internatio ii libxml2 2.5.7-1 GNOME XML library ii xlibs 4.2.1-6 X Window System client libraries ii zlib1g 1:1.1.4-11 compression library - runtime -- no debconf information
--- End Message ---
--- Begin Message ---Hello, (If you want my assistance, make sure that you include my address explicitly when replying, otherwise I will not receive the e-mail). Thanks for the bug reports and your interest in improving Debian. Sorry that the bugs were unattended for so long. I'm just doing some cleanup / bug triaging, but I am not involved with this package. gtkhtml3.8 was removed from the archives more than 3 years ago: http://packages.qa.debian.org/g/gtkhtml3.8/news/20091217T163921Z.html As a consequence that the package is not in the archives, the bugs are orphan now, so unlikely to be fixed (or indeed, noticed). So I think that the bugs should be closed now, doing it. Please reopen (or create a new bug reports) and assign to the relevant package versions if the reasons that caused you to report the problem are still present. (I saw that at least some of them still are present in the bugtracker upstream, but actually not acted upon for many years as well...). Cheers. -- Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
