Re: Looking for contact with Daniel Veillard libxml2 maintainer

On 23 January 2018 at 17:04, wrote: [..] >> Strange only is that looks like this bug already is known more than year! > > > Looks like two years... I followed the chain of links in the Red Hat bugs, > which claim this is already reported as >

Re: Looking for contact with Daniel Veillard libxml2 maintainer

On Tue, Jan 23, 2018 at 10:45 AM, Tomasz Kłoczko wrote: Strange only is that looks like this bug already is known more than year! Looks like two years... I followed the chain of links in the Red Hat bugs, which claim this is already reported as

Re: Looking for contact with Daniel Veillard libxml2 maintainer

On 23 January 2018 at 16:24, Tomasz Kłoczko wrote: > On 23 January 2018 at 15:59, wrote: > [..] >> That said... has the patch been proposed for inclusion upstream? It looks >> like Nick Wellnhofer is taking care of libxml2 upstream these days, so

Re: Looking for contact with Daniel Veillard libxml2 maintainer

On 23 January 2018 at 15:59, wrote: [..] > That said... has the patch been proposed for inclusion upstream? It looks > like Nick Wellnhofer is taking care of libxml2 upstream these days, so it > shouldn't need to wait for Daniel. I see you only included a link to a >

Re: Looking for contact with Daniel Veillard libxml2 maintainer

On Tue, Jan 23, 2018 at 9:07 AM, Tomasz Kłoczko wrote: If it will be no new actions to the end of this week I'm going to raise FESCo ticket to takeover at least libxml2. Yes, libxml2 is security-critical; we can't wait this long to apply security patches. The Fedora

Re: Looking for contact with Daniel Veillard libxml2 maintainer

On 16 January 2018 at 18:01, Tomasz Kłoczko wrote: [..] > >> https://bugzilla.redhat.com/show_bug.cgi?id=1529121 > > > > I think you should find a new maintainer for libxml2, and libxslt, and > > xmlsec1 > > because right now I have little time, and since Fedora

Re: Looking for contact with Daniel Veillard libxml2 maintainer

On Tue, 16 Jan 2018 18:13:40 +0100, Daniel Veillard wrote: > > https://src.fedoraproject.org/rpms/libxml2/pull-requests > > Page not found (404) It loads fine here and shows five pull requests. A temporary 404 would be a Fedora infrastructure problem to report somewhere.

Re: Looking for contact with Daniel Veillard libxml2 maintainer

On 16 January 2018 at 17:13, Daniel Veillard wrote: [..] >> https://src.fedoraproject.org/rpms/libxml2/pull-requests > > Page not found (404) https://src.fedoraproject.org/rpms/libxml2 -> Pull Requests tab > With the message: > > The requested URL was not found on the

Re: Looking for contact with Daniel Veillard libxml2 maintainer

On Tue, Jan 16, 2018 at 02:27:15PM +, Tomasz Kłoczko wrote: > On 16 January 2018 at 14:14, Daniel Veillard wrote: > > On Tue, Jan 16, 2018 at 01:33:28PM +, Tomasz Kłoczko wrote: > >> Hi, > >> > >> I'm trying to follow procedure described on > >>

Re: Looking for contact with Daniel Veillard libxml2 maintainer

On 16 January 2018 at 14:14, Daniel Veillard wrote: > On Tue, Jan 16, 2018 at 01:33:28PM +, Tomasz Kłoczko wrote: >> Hi, >> >> I'm trying to follow procedure described on >> https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers >> >> Daniel seems is

Re: Looking for contact with Daniel Veillard libxml2 maintainer

On Tue, Jan 16, 2018 at 01:33:28PM +, Tomasz Kłoczko wrote: > Hi, > > I'm trying to follow procedure described on > https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers > > Daniel seems is not responding for quite long time. Really ? > In case of the tickets which

Looking for contact with Daniel Veillard libxml2 maintainer

Hi, I'm trying to follow procedure described on https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers Daniel seems is not responding for quite long time. In case of the tickets which I've created it is almost 3 weeks. However I see in git unreplied pull request for more