From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mdbook-toc: Fix mdbook warning
Date: Thu, 22 Feb 2024 21:21:02 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48882@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]
There is a new pull request by meator against master on the void-packages repository
https://github.com/meator/void-packages mdbook-toc
https://github.com/void-linux/void-packages/pull/48882
mdbook-toc: Fix mdbook warning
mdbook complains that mdbook-toc was built against mdbook version 0.4.36 which is outdated now:
```
Warning: The mdbook-toc preprocessor was built against version 0.4.36 of mdbook, but we're being called from version 0.4.37
```
There are probably more elegant and future proof ways to solve this (one of which is just ignoring the warning because it's a warning and not an error), but bumping mdbook-toc fixes it too.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/48882.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mdbook-toc-48882.patch --]
[-- Type: text/x-diff, Size: 800 bytes --]
From 15778ab81946a325800eec2143f2740b2b905204 Mon Sep 17 00:00:00 2001
From: meator <meator.dev@gmail.com>
Date: Thu, 22 Feb 2024 21:17:19 +0100
Subject: [PATCH] mdbook-toc: Fix mdbook warning
mdbook complains that mdbook-toc was built against mdbook version 0.4.36
which is outdated now.
---
srcpkgs/mdbook-toc/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/mdbook-toc/template b/srcpkgs/mdbook-toc/template
index fa8e3e7885742e..bebc57233028b3 100644
--- a/srcpkgs/mdbook-toc/template
+++ b/srcpkgs/mdbook-toc/template
@@ -1,7 +1,7 @@
# Template file for 'mdbook-toc'
pkgname=mdbook-toc
version=0.14.2
-revision=1
+revision=2
build_style=cargo
short_desc="Preprocessor for mdbook to add inline TOC support"
maintainer="Orphaned <orphan@voidlinux.org>"
next reply other threads:[~2024-02-22 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 20:21 meator [this message]
2024-02-22 20:25 ` meator
2024-02-22 20:25 ` [PR PATCH] [Closed]: " meator
2024-02-22 20:29 ` classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48882@inbox.vuxu.org \
--to=meator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).