From: Tomas Volf <~@wolfsden.cz>
To: Leo Famulari <leo@famulari.name>
Cc: 70324@debbugs.gnu.org
Subject: bug#70324: After upgrade of linux-libre, linux-libre-documentation fails to build
Date: Thu, 11 Apr 2024 16:42:27 +0200 [thread overview]
Message-ID: <Zhf201svFeMkRenZ@ws> (raw)
In-Reply-To: <ZhdVK4WDqH42Ph2l@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 2098 bytes --]
On 2024-04-10 23:12:43 -0400, Leo Famulari wrote:
> On Wed, Apr 10, 2024 at 05:05:15PM +0200, Tomas Volf wrote:
> > linux-libre-documentation is broken again:
> >
> > starting phase `build'
> > Traceback (most recent call last):
> > File "/tmp/guix-build-linux-libre-documentation-6.8.4.drv-0/linux-6.8.4/./tools/net/ynl/ynl-gen-rst.py", line 26, in <module>
> > import yaml
> > ModuleNotFoundError: No module named 'yaml'
>
> It looks like the package depends on pyyaml now. I wonder if that's
> intentional. Did you search the upstream bug tracker to look for more
> info?
I did (now) and the search gives nothing. However I suspect the commit in
question would be a304fa1d10fcb974c117d391e5b4d34c2baa9a62:
docs: Makefile: Add dependency to $(YNL_INDEX) for targets other than htmldocs
Based on the diff:
+htmldocs texinfodocs latexdocs epubdocs xmldocs: $(YNL_INDEX)
+
+htmldocs:
I would assume it is the texinfodocs triggering the YNL_INDEX for us. This
snippet from the commit message:
If one of other targets such as latexdocs or epubdocs is built
without building htmldocs, missing .rst files can cause additional
WARNINGs from sphinx-build as follow:
Seems to indicate it is intentional.
>
> > How are these not caught in the CI?
>
> What do you mean? The CI server did register the build failure:
>
> https://ci.guix.gnu.org/build/3863875/details
>
> As well as many other build failures in the kernel packages:
>
> https://ci.guix.gnu.org/eval/1228559
Right, I should have written the question differently. I am curious how this
got onto the master. Given the point 9. in (guix)Submitting Patches, and the
fact the QA should run on every patch before it is accepted, I was surprised
that the broken build of dependent package was committed.
Since this was second time in past ~two months the linux-libre-documentation
package on master was broken, I was curious if it is special in some way.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-11 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 15:05 bug#70324: After upgrade of linux-libre, linux-libre-documentation fails to build Tomas Volf
2024-04-10 23:44 ` Rostislav Svoboda
2024-04-11 3:12 ` Leo Famulari
2024-04-11 14:42 ` Tomas Volf [this message]
2024-04-11 14:55 ` Leo Famulari
2024-04-11 19:18 ` Leo Famulari
2024-04-13 19:18 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zhf201svFeMkRenZ@ws \
--to=~@wolfsden.cz \
--cc=70324@debbugs.gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.