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
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
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
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
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
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
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
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
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.
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!
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:
>
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.
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 ")
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
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
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
16 matches
Mail list logo
