<zimbatm>
it automatically adds labels to issues and users can now select between bug reports and packaging requests
<zimbatm>
we can also add feature requests later if we want
__monty__ has joined #nixos-dev
orivej has joined #nixos-dev
FRidh has quit [Quit: Konversation terminated!]
tilpner has quit [Quit: WeeChat 2.4]
avn has quit [Read error: Connection reset by peer]
orivej has quit [Ping timeout: 268 seconds]
tilpner has joined #nixos-dev
<worldofpeace>
#64984 âšī¸ I think it's absolutely essential for 19.09 that no user has this problem
<{^_^}>
https://github.com/NixOS/nixpkgs/issues/64984 (by emmanuelrosa, 4 hours ago, open): qutebrowser: This application failed to start because no Qt platform plugin could be initialized.
<gchristensen>
do we have a handle no a solution?
<gchristensen>
on a*
<worldofpeace>
pretty sure just add wrapQtAppsHook to nativeBuildInputs to basically every application that needs it
<gchristensen>
is there a way we can test for this problem automatically?
<worldofpeace>
Pretty much that error at runtime
<gchristensen>
so, like, run every executable from every package and see if it emits that error?
<worldofpeace>
think so
<gchristensen>
it depends on system state, right?
<gchristensen>
I'm somewhat wondering what would it take for me to do this :P
<worldofpeace>
yes the environment, the unwrapped applications could for example inherit the wrapped env from plasma5 and "work"
<worldofpeace>
I wouldn't start though until #64720 is complete
<gchristensen>
would a basic construct like: start a NixOS VM with xserver and the "xterm" "desktop manager" enabled, execute each binary from a given package, kill them after a couple seconds, search output for "failed to start because ..." ... suffice?
<gchristensen>
would a basic construct like: start a NixOS VM with xserver and the "xterm" "desktop manager" enabled, execute each binary from a given package, kill them after a couple seconds, search output for "failed to start because ..." ... destroy the VM. repeat for each package. suffice?
<worldofpeace>
I thought of writing a test like that yesterday even
<gchristensen>
that would be awesome!
<gchristensen>
if you'd like to collaborate, I can get hardware for such experiments =)
<worldofpeace>
I'd hope it would be simple like that, Qt isn't exactly my wheelhouse since I'm maintaining the gtk side of things. But we sure could try
<gchristensen>
sounds great :) I know almost nothing about Qt, but if some effort and a lot of CPUs can help make (almost) no user experience that problem again, I am on board
<samueldr>
worldofpeace, gchristensen, #47552 has a testable repro
<worldofpeace>
So I'm thinking, would it be easier to just identify what applications are qt ones with nix and just filter that out? It should just be fine then to add the setup-hook to all of them
<gchristensen>
could only do programs where `qt` is in a store path of its dependencies
<clever>
gchristensen: there was a package somewhere, that basically checked for foo in $PATH, and if it was found, enabled support for foo
<worldofpeace>
yeah I think libQt5Core
<clever>
gchristensen: except, store path hashes .....
<clever>
so, it would randomly enable support for something, and fail to build
Jackneill has quit [Remote host closed the connection]
justan0theruser is now known as justanotheruser
{^_^} has quit [Ping timeout: 276 seconds]
<arianvp>
where in the nix store are signatures stored?
<arianvp>
in the sqlite db?
<thoughtpolice>
arianvp: Yes. You can see the schema yourself with `nix run nixpkgs.sqlite -c sqlite3 /nix/var/nix/db/db.sqlite ".schema" | less` (run as `root`)
<thoughtpolice>
`sqlite3 /nix/var/nix/db/db.sqlite "SELECT sigs FROM ValidPaths WHERE sigs != \"\""`
orivej has quit [Ping timeout: 248 seconds]
FRidh has quit [Quit: Konversation terminated!]
arianvp has quit [Quit: WeeChat 2.4]
arianvp has joined #nixos-dev
psyanticy has quit [Quit: Connection closed for inactivity]
<arianvp>
where are signatures stored for /nix/store?