Bug#956219: Error out when DISPLAY is unset

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#956219: Error out when DISPLAY is unset

Sebastien Bacher-2
Package: webkit2gtk
Version: 2.28.0-2

The yelp package is currently failing to build, that has been fixed
upstream with that commit
https://trac.webkit.org/changeset/259380/webkit

Would it be possible to have it cherry picked for the next Debian upload?

Thanks,

Reply | Threaded
Open this post in threaded view
|

Bug#956219: Error out when DISPLAY is unset

Alberto Garcia-2
Control: tags -1 upstream fixed-upstream
Control: forwarded -1 https://bugs.webkit.org/show_bug.cgi?id=209431

On Wed, Apr 08, 2020 at 04:25:24PM +0200, Sebastien Bacher wrote:

> The yelp package is currently failing to build,
> that has been fixed upstream with that commit
> https://trac.webkit.org/changeset/259380/webkit
>
> Would it be possible to have it cherry picked for the next Debian
> upload?

Yes, this is already planned for the 2.28.1 release (which is likely
to happen soon), you can see the list of bug fixes here:

   https://trac.webkit.org/wiki/WebKitGTK/2.28.x

Berto

Reply | Threaded
Open this post in threaded view
|

Bug#956219: Error out when DISPLAY is unset

Laurent Bigonville-5
reopen 956219
severity 956219 serious
thanks

On Wed, 8 Apr 2020 16:39:09 +0200 Alberto Garcia <[hidden email]> wrote:

 > Control: tags -1 upstream fixed-upstream
 > Control: forwarded -1 https://bugs.webkit.org/show_bug.cgi?id=209431
 >
 > On Wed, Apr 08, 2020 at 04:25:24PM +0200, Sebastien Bacher wrote:
 >
 > > The yelp package is currently failing to build,
 > > that has been fixed upstream with that commit
 > > https://trac.webkit.org/changeset/259380/webkit
 > >
 > > Would it be possible to have it cherry picked for the next Debian
 > > upload?
 >
 > Yes, this is already planned for the 2.28.1 release (which is likely
 > to happen soon), you can see the list of bug fixes here:

I'm reopening this as yelp still FTBFS with 2.28.2 with the same error,
was the patch cherry-picked?