Re: build broken packages handling
Hi Andy, Answers below. Le 29 mars 2021 16:02:37 GMT-04:00, Andy Tai a écrit : >Two questions: > >1. When submitting an updated package definition, is there an easy >way to check if other packages may be broken by this update? Right >now it is easy to check if a package builds with updated package >definition; but it is not easy to see if committing it will break >others. I can't check right now, but I think the contributing section in the manual describes this. You might want to have a look :) To list leaf packages that are affected by a change (and the number of packages affected, including non-leaf), you can use guix refresh: guix refresh -l foo Will tell you which leaf packages are affected if you modify foo. Build them all if the number is low. If the number of dependents is high enough to qualify for staging or core-updates, then checking only some of them is ok. > >2. If a package is not building in guix, should a bug be filed against >it? Ot there is a way, a CI web interface or something that shows all >existing packages whose builds are broken? Yes, if the package is important to you, please file a bug report with details about the failing build, to bug-guix. Don't bother upstream :) We have ci.guix.gnu.org, which is our build farm. You can use the search box to look for failing builds. If you manage to fix some of them, definitely send a patch! > >Thanks
build broken packages handling
Two questions: 1. When submitting an updated package definition, is there an easy way to check if other packages may be broken by this update? Right now it is easy to check if a package builds with updated package definition; but it is not easy to see if committing it will break others. 2. If a package is not building in guix, should a bug be filed against it? Ot there is a way, a CI web interface or something that shows all existing packages whose builds are broken? Thanks -- Andy Tai, a...@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat: andytai1010 Year 2021 民國110年 自動的精神力是信仰與覺悟 自動的行為力是勞動與技能
Re: guix pull errors
On Mon, Mar 29, 2021 at 05:23:44PM +, Ekaitz Zarraga wrote: > Before the `reconfigure` I had a 10 days old system. > Now it seems to work fine. > > I had a hard time make it upgrade tbh, it was like stuck all the time with > the same error. > > So it was just a network issue and it is fixed now, right? Basically! Let us know if it happens again.
Re: Starting Sway a Wayland window manager
On 2021-03-29, Bone Baboon wrote: > When I run `dbus-run-session sway` on virtual terminal 1 sway does not > start and I get this output: > > ``` > localhost dbus-daemon[380]: [system] Rejected send message, 2 matched rules; > type="method_call", sender=":1.24" (uid=1000 pid=26112 comm="sway ") > interface="org.freedesktop.login1.Session" member="SetType" error > name="(unset)" requested_reply="0" destination="org.freedesktop.login1" > (uid=0 pid=381 comm="/gnu/store/jdk3r1gs4d36n3aj9fscsvwwc9prnrzp-elogin") v > [backend/backend.c:303] Failed to open any DRM device ^ I think this is your fundamental problem. There's no DRM device available (at least to your user). Are there devices in /dev/dri/, and are they writeable by your user? live well, vagrant signature.asc Description: PGP signature
Re: Starting Sway a Wayland window manager
On Sat, 27 Mar 2021 20:43:49 -0400 Bone Baboon wrote: > I have installed Sway a Wayland window manager. > > I have copied the `gnu/store/-sway-1.5.1/etc/sway/config` to > `~/.sway/config`. > > When I run `sway` or `sudo sway` on virtual terminal 1 it outputs > "XDG_RUNTIME_DIR is not set in the environment. Aborting.". `man > sway` and `sway --help` does not mention `XDG_RUNTIME_DIR`. An > suggestions on how to deal with this error? > Run it with dbus-run-session sway. Do **not** run it as root. Generally speaking, don't randomly run things as root.
Re: guix pull errors
Before the `reconfigure` I had a 10 days old system. Now it seems to work fine. I had a hard time make it upgrade tbh, it was like stuck all the time with the same error. So it was just a network issue and it is fixed now, right? Great! Good to know, thanks!
Re: guix pull errors
On Sun, Mar 28, 2021 at 11:02:13PM +, Ekaitz Zarraga wrote: > Hi, > > I'm getting tons of guix pull errors these days. > They look like they are related with network issues because they > disappear if I insist (many times) and they appear in different > packages. > > They look like this: > > ``` > guix/ui.scm:2164:12: In procedure run-guix-command: > Bad Read-Header-Line header: # > > substitution of /gnu/store/c39c4jhgg1pq3sw083pcmp42gba05kr2-evince-3.36.5 > failed > ``` > > I'm finding them all the time. > > I think they are very cryptic... Maybe we can do something > about that. Have you updated your guix-daemon recently? This looks like some recent bugs that have been fixed.
Re: Two more computers unable to start X with GDM
On Mon, Mar 29, 2021 at 10:32:49AM -0400, Gary Johnson wrote: > I've always had good luck using linux-libre with Intel integrated > graphics controllers. Agreed, Intel is the way to go for free graphics drivers.
Re: Two more computers unable to start X with GDM
Yasuaki Kudo writes: > I read a little bit about the current state of video cards, etc - man > this seems like an uphill battle😅 Basically no manufacture > sympathizes with the concept of total transparency. > > I was just thinking what the practical end-game of this might be - do > you think at some point there will be an FPGA+power+various I/O ports > kit that can be totally programmed to provide CPU and video > acceleration? Something like that might be the only way to end this > nonsense😅 There is this: https://www.crowdsupply.com/libre-risc-v/m-class/updates They are still working on it, but that website hasn't seen updates in a while. They have another website that they update more often. > > Then the battle will be proprietary vs free software rather than > hardware. But then again, I don't know what kind of nasty patents > there might be... > > -Yasu > >> On Mar 28, 2021, at 03:25, Leo Famulari wrote: >> >> On Sat, Mar 27, 2021 at 10:14:05AM -0400, Bone Baboon wrote: >>> X server worked fine with this NVIDIA GeForce FX 5200 GPU when Debian >>> was installed on this computer. It also looks like Debian uses a >>> deblobbed kernal based on this Wikipedia article. >>> https://en.wikipedia.org/wiki/Binary_blob >> >> The Guix kernel (linux-libre) and the Debian kernel (Linux) have >> different hardware support and, in general, Linux supports more hardware >> than linux-libre. >> -- Joshua Branson (joshuaBPMan in #guix) Sent from Emacs and Gnus https://gnucode.me https://video.hardlimit.com/accounts/joshua_branson/video-channels https://propernaming.org "You can have whatever you want, as long as you help enough other people get what they want." - Zig Ziglar
Re: Starting Sway a Wayland window manager
Bone Baboon writes: > Joshua Branson writes: > >> I also just realized that sway started for me when I changed >> %base-services to %desktop-services. > > If I reconfigure the system with `%desktop-services`: > > ``` > (services %desktop-services) > ``` > > When I run `sway` on virtual terminal 1 sway does not start and I get > this output: > > ``` > localhost dbus-daemon[380]: [system] Rejected send message, 2 matched > rules; type="method_call", sender=":1.24" (uid=1000 pid=26112 > comm="sway ") interface="org.freedesktop.login1.Session" > member="SetType" error name="(unset)" requested_reply="0" > destination="org.freedesktop.login1" (uid=0 pid=381 > comm="/gnu/store/jdk3r1gs4d36n3aj9fscsvwwc9prnrzp-elogin") > [backend/backend.c:303] Failed to open any DRM device > [sway/server.c:49] Unable to create backend > ``` > > When I run `sudo sway` it outputs "XDG_RUNTIME_DIR is not set in the > environment. Aborting.". hmmm, maybe this will help. Here's my current guix config: https://notabug.org/jbranso/guix-config/src/master/sway.scm -- Joshua Branson (joshuaBPMan in #guix) Sent from Emacs and Gnus https://gnucode.me https://video.hardlimit.com/accounts/joshua_branson/video-channels https://propernaming.org "You can have whatever you want, as long as you help enough other people get what they want." - Zig Ziglar
Re: Two more computers unable to start X with GDM
Yasuaki Kudo writes: > I read a little bit about the current state of video cards, etc - man > this seems like an uphill battle😅 Basically no manufacture > sympathizes with the concept of total transparency. I've always had good luck using linux-libre with Intel integrated graphics controllers. > I was just thinking what the practical end-game of this might be - do > you think at some point there will be an FPGA+power+various I/O ports > kit that can be totally programmed to provide CPU and video > acceleration? Something like that might be the only way to end this > nonsense😅 I like to buy my laptops from ThinkPenguin. All of the computers they sell work out of the box with linux-libre. I'm, of course, running Guix System on one of their laptops right now. https://www.thinkpenguin.com/ Happy hacking, Gary -- GPG Key ID: 7BC158ED Use `gpg --search-keys lambdatronic' to find me Protect yourself from surveillance: https://emailselfdefense.fsf.org === () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Why is HTML email a security nightmare? See https://useplaintext.email/ Please avoid sending me MS-Office attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: Starting Sway a Wayland window manager
Joshua Branson writes: > I also just realized that sway started for me when I changed > %base-services to %desktop-services. If I reconfigure the system with `%desktop-services`: ``` (services %desktop-services) ``` When I run `sway` on virtual terminal 1 sway does not start and I get this output: ``` localhost dbus-daemon[380]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.24" (uid=1000 pid=26112 comm="sway ") interface="org.freedesktop.login1.Session" member="SetType" error name="(unset)" requested_reply="0" destination="org.freedesktop.login1" (uid=0 pid=381 comm="/gnu/store/jdk3r1gs4d36n3aj9fscsvwwc9prnrzp-elogin") [backend/backend.c:303] Failed to open any DRM device [sway/server.c:49] Unable to create backend ``` When I run `sudo sway` it outputs "XDG_RUNTIME_DIR is not set in the environment. Aborting.".
Re: Starting Sway a Wayland window manager
Joshua Branson writes: >> What package includes `dbus-run-session`? I do not have it installed on >> my system? > > I think it's dbus? I honestly don't remember... The `dbus` package does provide `dbus-run-session`. When I run `dbus-run-session sway` on virtual terminal 1 sway does not start and I get this output: ``` localhost dbus-daemon[380]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.24" (uid=1000 pid=26112 comm="sway ") interface="org.freedesktop.login1.Session" member="SetType" error name="(unset)" requested_reply="0" destination="org.freedesktop.login1" (uid=0 pid=381 comm="/gnu/store/jdk3r1gs4d36n3aj9fscsvwwc9prnrzp-elogin") [backend/backend.c:303] Failed to open any DRM device [sway/server.c:49] Unable to create backend ``` When I run `sudo dbus-run-session sway` it outputs "XDG_RUNTIME_DIR is not set in the environment. Aborting.".
Re: Blender freezes i3wm
Weirdly enough, yesterday I sculpted for 2h in a row and everything went well. After that, I opened the model I worked on and it freezed my screen again, but this time some buttons of other screens started to appear on top of the frozen window. Very weird. Anyway, this looks like it's impossible to debug so I'm going to act as it didn't happen.
Re: Two more computers unable to start X with GDM
I read a little bit about the current state of video cards, etc - man this seems like an uphill battle😅 Basically no manufacture sympathizes with the concept of total transparency. I was just thinking what the practical end-game of this might be - do you think at some point there will be an FPGA+power+various I/O ports kit that can be totally programmed to provide CPU and video acceleration? Something like that might be the only way to end this nonsense😅 Then the battle will be proprietary vs free software rather than hardware. But then again, I don't know what kind of nasty patents there might be... -Yasu > On Mar 28, 2021, at 03:25, Leo Famulari wrote: > > On Sat, Mar 27, 2021 at 10:14:05AM -0400, Bone Baboon wrote: >> X server worked fine with this NVIDIA GeForce FX 5200 GPU when Debian >> was installed on this computer. It also looks like Debian uses a >> deblobbed kernal based on this Wikipedia article. >> https://en.wikipedia.org/wiki/Binary_blob > > The Guix kernel (linux-libre) and the Debian kernel (Linux) have > different hardware support and, in general, Linux supports more hardware > than linux-libre. >
Re: Single-board-computer approach: don't make an installer, make the install?
Hey Joshua, > I believe that these issues have been closed. I suppose we could write > a blog post, if you believe that would be worth while. Yes they were indeed. It would be nice but it's not on my list right now. I you feel like writing it, I would happily review it :). Thanks, Mathieu
