Will Thompson
Will Thompson
Seeing something similar in this configuration: - Primary display: 3200×1800 (ie 1600×900 @ 2x) - Secondary display: 1920×1080 (ie 1x) - Fedora 24 - GNOME Shell in Wayland mode Regardless...
Provide shims for well-known binaries, which can only run on the host, inside the toolbox containers
Another option could be to make podman within the container always use `--remote`. The socket for the API server appears to be visible within a toolbox container.
(I'm not a Drop developer, just a user who is seeing the same bug.) This fix works for me: ace! Here's a [minimal-ish test case](https://gist.github.com/wjt/f948c42babdd3284fd44eee38b2262c9) which raises an exception without...
The Flathub build infrastructure could do so but I don't think this is the right tool to do it.
@barthalion where's the right buildbot-y place to request this?
How do you generate the current change log? I believe there are scripts which generate news files from appdata floating around.
``` wjt@toolbox:~/src/MegaGlest/megaglest-data☭ appstream-util appdata-to-news others/appdata/megaglest.appdata.xml Version 3.13.0 ~~~~~~~~~~~~~~ Released: 2017-03-09 The MegaGlest team is proud to release v3.13.0. Notable improvements to this release include: * Multi-building select and key-binding for...
So what I am proposing is: make the appdata file the canonical source for the changelog, and generate the plain-text version at release time using `appstream-util appdata-to-news`.