public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Yury German <blueknight@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] app-text/htmltidy: Maintainer Request
Date: Mon, 6 Jun 2016 10:55:48 -0400	[thread overview]
Message-ID: <64e75ec6-d1a1-188d-52db-db3eba51518b@gentoo.org> (raw)
In-Reply-To: <CAGDaZ_ruMtT-N3vc-u+ofc=gyvMJ8OgTT-1Cf1qPpLLfZSXCEA@mail.gmail.com>

Well a few things need to happen:

1. app-text/tidy-html5 - Need to go Stabl
2. dep and rdep need to be migrated to tidy-html5 and tested.

Since Patrice (monsieurp) is the maintainer of tidy-html5, do you want
to become maintainer of htmltidy temporarily to help kill it and move to
tidy-html5?


On 6/6/16 10:41 AM, Raymond Jennings wrote:
> If tidy-html5 can take care of anything htmltidy can, then we can boot
> the latter as obsolete anyhow.  Are there any backwards compatibility
> issues if we just punt it and let tidy-html5 take over?
> 
> On Mon, Jun 6, 2016 at 7:15 AM, Yury German <blueknight@gentoo.org
> <mailto:blueknight@gentoo.org>> wrote:
> 
> 
> 
>     On 6/5/16 8:02 PM, Patrice Clement wrote:
>     > Sunday 05 Jun 2016 19:39:26, Yury German wrote :
>     >> app-text/htmltidy currently has no maintainers. It has a vulnerability
>     >> [Security Bug] filed against it. And a number of other [package depend
>     >> on it]. Is nyone willing to pick it up?
>     >>
>     >> [Secuity Bug]
>     >> https://bugs.gentoo.org/show_bug.cgi?id=561452
>     >>
>     >> [package depend on it]
>     >> https://qa-reports.gentoo.org/output/genrdeps/dindex/app-text/htmltidy
>     >> https://qa-reports.gentoo.org/output/genrdeps/rindex/app-text/htmltidy
> 
>     > Don't bother. Have a look at [1], [2] & [3] to find out why.
>     >
>     > tl;dr
>     >
>     > htmltidy has got to be culled at some point since it's now considered obsolete
>     > after tidy-html5 entered the tree a little while ago. It's roughly the same
>     > codebase yet it's HTML 5 compliant. Yay!
>     >
>     > I've been maintaining the latter since its inclusion in the Portage tree but
>     > would definitely need help to remove the former. I didn't swap htmltidy for
>     > tidy-html5 cause they're two different projects. As you can see from the links
>     > above, htmltidy has a gazillion deps.
>     >
>     > [1]: http://tidy.sourceforge.net/
>     > [2]: http://www.html-tidy.org/
>     > [3]: https://github.com/htacg/tidy-html5
>     >
> 
>     This is all agreed, but unless someone is driving this it will never get
>     removed from tree. The security patch is one thing, but cleaning it up
>     and switching to tidy-html5 is why we need a maintainer so that we can
>     get rid of the dependencies otherwise it will sit there unsecured for
>     the next 5 years.
> 
> 
> 


  reply	other threads:[~2016-06-06 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-05 23:39 [gentoo-dev] app-text/htmltidy: Maintainer Request Yury German
2016-06-06  0:02 ` Patrice Clement
2016-06-06 14:15   ` Yury German
2016-06-06 14:41     ` Raymond Jennings
2016-06-06 14:55       ` Yury German [this message]
2016-06-06 15:07         ` Raymond Jennings
2016-06-07 21:44         ` Michael Orlitzky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=64e75ec6-d1a1-188d-52db-db3eba51518b@gentoo.org \
    --to=blueknight@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox