qrcode: 0-unstable-2024-06-05 -> 0-unstable-2024-07-18#329417
Conversation
|
Result of 1 package built:
|
|
I think it's broken It's, in my machine, generating a qrcode with inverted colors Fix: qsantos/qrcode#8 |
|
I guess the question is whether «terminal» means terminal emulator with light or dark background? I mostly encounter default-light-background ones, and there the QR code is in the black-on-white… (In any case I think we currently have a version with the same behaviour before and after the update) |
|
@ofborg eval (the failure was transient) |
I added the feature so it seems that it's my fault. Maybe that could be a flag that allow the user to invert the colors. At first I am assuming that everyone is using dark terminals because out of the box AFAIK it's true with everything but xterm. And who uses xterm by option lol |
|
Well, it is also default for *rxvt and mlterm. And light mode with brightness way down is the way to go! (At least if text on paper is also a thing that happens from time to time) Inversion switch would be nice, of course (upstream). |
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for qrcode is: Small QR-code tool
meta.homepage for qrcode is: https://github.com/qsantos/qrcode
Updates performed
To inspect upstream changes
Impact
Checks done
passthru.tests, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-reviewrun on x86_64-linux 11 package built:
Maintainer pings
cc @7c6f434c @lucasew for testing.