Comment by ~colemickens on ~whynothugo/shotman
I would "close" this but I don't see a way for me to do so.
Comment by ~colemickens on ~whynothugo/shotman
Yeah, I'm sorry, this is a upstream nixpkgs change to how the rust builder consumes cargo. I think there is a more appropriate fix on my side.
sorry for the noise.
Ticket created by ~colemickens on ~whynothugo/shotman
Hi, I package tip release of some Wayland packages in nixpkgs-wayland.
One of those is shotman.
However, this morning updates for shotman are blocked by this:
│ > configuring │ │ > no configure script, doing nothing │ │ > building │ │ > source = "git+https://github.com/Smithay/client-toolkit.git#327f9cd791d8810fe7324ee1ddd48adaf3592ca4" │ │ > │ │ > ERROR: The Cargo.lock contains git dependencies │ │ > │ │ > This is currently not supported in the fixed-output derivation fetcher. │ │ > Use cargoLock.lockFile / importCargoLock instead.
It seems that you're using a tagged release, is it possible to avoid the git dependency, by chance?
Thanks!
Ticket created by ~colemickens on ~sircmpwn/builds.sr.ht
Currently,
builds.sr.ht
advertises a build badge which show a "build status" (via SVG) for a given tag. The value is based on the status of the most recent non-cancelled job that contains that tag.It would be helpful to have a way to query for this same information, directly, via the API.
As a workaround, one can query all of a user's jobs and filter based on its tags:
TOKEN="$(gopass ...)" BUILD_HOST="https://build.sr.ht" TAG="nixpkgs-wayland" curl \ -H "Authorization:token ${TOKEN}" \ -H "Content-Type: application/json" -X GET \ "${BUILD_HOST}/api/jobs" > /tmp/data jq -r "[.results[] | select(.tags==\"${TAG}\" and .status!=\"running\")][0] | .status" /tmp/data
(note the example spits out just the status field, but otherwise would've returned the full job object)
Also, a note to document something else that tripped me up, the "tags" array that the API accepts is misleading, note that the order matters and forms a "path", as returned by the jobs api: the "tags" field is a string, not array. For example, if you specify
tags:["tag1","tag2"]
in the POST, you will gettags: "tag1/tag2"
in the subsequent GET to query the job status.
REPORTED
RESOLVED DUPLICATEComment by ~colemickens on ~sircmpwn/builds.sr.ht
Sorry, this is a dupe of #259 (https://todo.sr.ht/~sircmpwn/builds.sr.ht/259).
Ticket created by ~colemickens on ~sircmpwn/builds.sr.ht
I have queued builds that I'd like to cancel, but I can't cancel them (at least, not from the UI).
Comment by ~colemickens on ~scoopta/wlrobs
I'm testing with https://github.com/obsproject/obs-studio/pull/2484 but I was also able to reproduce with xcb-obs and the plugin with screencopy, which I also know worked a few weeks ago.
Thanks!
Ticket created by ~colemickens on ~scoopta/wlrobs
It seems like maybe there were some changes in wlroots related to screencopy.
I had to delete my OBS config and recreate with a DMAbuf screen capture to get anything working. Adding a screencopy capture to the scene breaks OBS and requires again deleting the config.
Comment by ~colemickens on ~scoopta/wofi
I would argue that "riot" is still closer to "Riot", but passing
--insensitive
does also "fix" it. Thanks.