Package Details: linux-rt-bfq-docs 5.6.10.rt5-9

Git Clone URL: (read-only, click to copy)
Package Base: linux-rt-bfq
Description: Documentation for the Linux RT-BFQ-dev kernel
Upstream URL:
Licenses: GPL2
Submitter: sir_lucjan
Maintainer: sir_lucjan
Last Packager: sir_lucjan
Votes: 15
Popularity: 1.69
First Submitted: 2015-06-12 16:19
Last Updated: 2020-05-18 15:00

Required by (0)

Sources (15)

Pinned Comments

sir_lucjan commented on 2019-10-07 11:43

Some patches for BFQ conflict with patches for BFQ-dev.

To use linux-rt-bfq smoothly apply bfq-reverts before bfq-dev patch. Otherwise the kernel will not compile.

sir_lucjan commented on 2018-01-11 22:32

linux-rt-bfq git version:


Latest Comments

1 2 3 4 5 6 ... Next › Last »

sir_lucjan commented on 2020-05-19 20:27


Never compile kernels with such crap tools. Makepkg never causes any problems - as long as PKGBUILD and the sources are okay.

sir_lucjan commented on 2020-05-18 23:51

Unfortunately, no.

teetest commented on 2020-05-18 23:43

Stuck in Stripping build tools... Have you guys ever seen this situation?


makepkg by hand. Not use aur helpers

Turbo commented on 2020-04-07 13:52

@sir_lucjan it' ok with with a previous version of python-sphinx.

sir_lucjan commented on 2020-04-07 12:31

I've reported:

colinjmatt commented on 2020-04-07 12:11

Downgrading to python-sphinx-2.4.4-1 has allowed me to compile successfully. As you confirmed, the issue here seems to be with python-sphinx-3.0.0-1.

sir_lucjan commented on 2020-04-07 11:32

OK, but this has nothing to do with the kernel version - sphinx 2.X worked properly and yesterday I built kernel 5.6.2. 99% of the problem is with sphinx 3.0

colinjmatt commented on 2020-04-07 11:21

I was able to compile the last 5.4 kernel version you released before this 5.6 version.

sir_lucjan commented on 2020-04-07 11:11

Oh, I see. The problem is probably with sphinx version 3.0 - I didn't manage to update it. Can you check if there is a problem with version 5.4/5.5?

sir_lucjan commented on 2020-04-07 11:09

I've been building a 5.6 kernel since the first release and I haven't experienced this error. I will try to do something about it, but it will be extremely difficult if it doesn't happen with me.