Package Details: system76-scheduler 2.0.1-1

Git Clone URL: (read-only, click to copy)
Package Base: system76-scheduler
Description: system76 userspace scheduler
Upstream URL:
Licenses: MPL-2
Submitter: sirspudd
Maintainer: sirspudd
Last Packager: sirspudd
Votes: 9
Popularity: 2.49
First Submitted: 2022-05-06 17:37 (UTC)
Last Updated: 2023-05-11 13:23 (UTC)

Latest Comments

1 2 3 Next › Last »

gorneman commented on 2023-05-11 17:36 (UTC)

@sirspudd thanks for the update

sirspudd commented on 2023-05-11 13:25 (UTC)

@gorneman @aorth

Thanks for the heads up; I have addressed your concerns and bumped to 2.0.1


What kind of Arch specific adjustment are you anticipating?

aorth commented on 2023-05-11 12:21 (UTC)

@gorneman here's an updated PKGBUILD for v2.0.1 that I wrote. It has the changes to deps that I suggested below. I've been running it on a few machines for the past week.

gorneman commented on 2023-05-10 19:51 (UTC)

There will be an update for this package?

bushmaster commented on 2023-05-02 11:22 (UTC)

This package it's just install and run ? There is no Arch specific changes that i need to do ?

aorth commented on 2023-05-02 05:42 (UTC) (edited on 2023-05-02 06:35 (UTC) by aorth)

I don't think we should be skipping package sums. For what it's worth, when version 2.0.0 was released I remember seeing some last-minute changes in the git history. I think they might have shipped a broken 2.0.0 and force pushed that tag.

Regarding the 2.0.0 version, the RON configuration file is no longer used. Now they have migrated to a KDL config. I think we can update the PKGBUILD to back up /usr/share/system76-scheduler/config.kdl instead. See the README for the information about the new config format.

Edit: also, @yochananmarqos is correct. We only need libpipwire in depends, not pipewire. It should be in depends because it is used for build and runtime.

sirspudd commented on 2023-04-29 00:53 (UTC)

@rsa: I verified the checksum had changed again. I have now opted to SKIP the checksum. Thank you for the heads up about this issues having reared its head before, this is the first I have heard of it.

rsa commented on 2023-04-28 10:49 (UTC)

Checksum does not match for me either, I get d64a6108f6704ed5c35e1e1ca85be308cb036ee04b3291e3fe7248f5824b2b89

Is something fishy going on with github archives again?

sirspudd commented on 2023-04-26 03:06 (UTC) (edited on 2023-04-26 03:06 (UTC) by sirspudd)

@gbr: fixed

sirspudd commented on 2023-04-26 03:03 (UTC) (edited on 2023-04-26 03:06 (UTC) by sirspudd)

@gbr: deleted the file from several hours ago, now the checksum has changed