Package Details: pandoc-crossref-bin 0.3.24.a-1

Git Clone URL: https://aur.archlinux.org/pandoc-crossref-bin.git (read-only, click to copy)
Package Base: pandoc-crossref-bin
Description: Pandoc filter for cross-references - executable only
Upstream URL: https://github.com/lierdakil/pandoc-crossref/
Keywords: crossref pandoc
Licenses: GPL-2.0-or-later
Conflicts: pandoc-crossref
Provides: pandoc-crossref
Submitter: eNV25
Maintainer: eNV25 (a821)
Last Packager: a821
Votes: 10
Popularity: 0.20
First Submitted: 2022-02-03 15:11 (UTC)
Last Updated: 2026-05-18 07:31 (UTC)

Dependencies (1)

Required by (3)

Sources (2)

Latest Comments

1 2 Next › Last »

a821 commented on 2025-03-12 17:10 (UTC)

Sadly, it seems upstream have been a bit slow with the recompilation. You can see for yourself here: https://github.com/lierdakil/pandoc-crossref/releases

I have no control whatsoever on the releases; you can try to raise an issue on their Github repo. I would also suggest to use the official pandoc-crossref which seems to be up-to-date: https://archlinux.org/packages/extra/x86_64/pandoc-crossref/

chandra commented on 2025-03-12 16:51 (UTC)

When will a newer pandoc-crossref be available?

chandra commented on 2025-02-11 08:20 (UTC)

Thanks for the explanation, @a821. I can wait.

a821 commented on 2025-02-11 08:13 (UTC)

@chandra: pandoc and pandoc-crossref are not compiled at the same time by their developers. It usually takes a week for pandoc-crossref to be updated, so please be patient (I cannot do anything about it). For the moment, you could downgrade pandoc-bin.

chandra commented on 2025-02-11 07:10 (UTC)

pandoc-bin 3.6.3 is now available at https://aur.archlinux.org/packages/pandoc-bin.

Could pandoc-crossref-bin be compiled against this version/release please? Thanks.

eNV25 commented on 2022-03-05 04:48 (UTC)

Fixed

shirshendu commented on 2022-03-04 10:20 (UTC) (edited on 2022-03-04 10:27 (UTC) by shirshendu)

Tried to install pandoc-crossref in Manjaro 21.2.4; pandoc-crossref-0.3.12.2a.tar.xz fails check. Probably the sha512sum should be updated.

~ ❯ yay -S pandoc-crossref-bin
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  pandoc-crossref-bin-0.3.12.2a-1

:: (1/1) Downloaded PKGBUILD: pandoc-crossref-bin
  1 pandoc-crossref-bin              (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: (1/1) Parsing SRCINFO: pandoc-crossref-bin
==> Making package: pandoc-crossref-bin 0.3.12.2a-1 (Friday 04 March 2022 03:49:33 PM)
==> Retrieving sources...
  -> Downloading pandoc-crossref-0.3.12.2a.tar.xz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   665  100   665    0     0   1036      0 --:--:-- --:--:-- --:--:--  1035
100 6784k  100 6784k    0     0  1187k      0  0:00:05  0:00:05 --:--:-- 1632k
==> Validating source files with sha256sums...
    pandoc-crossref-0.3.12.2a.tar.xz ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: pandoc-crossref-bin 
         context: exit status 1 


==> Making package: pandoc-crossref-bin 0.3.12.2a-1 (Friday 04 March 2022 03:49:41 PM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found pandoc-crossref-0.3.12.2a.tar.xz
==> Validating source files with sha256sums...
    pandoc-crossref-0.3.12.2a.tar.xz ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error making: pandoc-crossref-bin

eNV25 commented on 2022-02-05 05:03 (UTC)

I don't think I can make it depends=(pandoc), but I can probably make it depends=("pandoc>=${_pandoc_pkgver}"). pandoc-crossref's binary releases are compiled for specific versions of pandoc. The current version of community/pandoc is 2.14.2 but aur/pandoc-bin is 2.17.0.1. Do you think it should use '>=' or '='?

If you want to use pandoc-crossref with community/pandoc you should probably use community/pandoc-crossref. If you want to use a custom pandoc you should probably compile pandoc-crossref yourself. Maybe aur/pandoc-crossref can be made?

I got the following warning message when I tried to use aur/pandoc-crossref-bin with community/pandoc:

$ pandoc -F pandoc-crossref <(curl -sSL https://raw.githubusercontent.com/lierdakil/pandoc-crossref/master/docs/demo/demo.md) -o demo.html
[WARNING] Could not deduce format from file extension 
  Defaulting to markdown
WARNING: pandoc-crossref was compiled with pandoc 2.17.0.1 but is being run through 2.14.2. This is not supported. Strange things may (and likely will) happen silently.

alerque commented on 2022-02-03 20:57 (UTC)

Can you please change the dependencies on this to be depends=(pandoc)? It is quite likely that people than want this -bin also want that one, but there are also other options. For example I have a Pandoc fork that also has AUR packages that provide pandoc that would work. The same goes for pandoc-git which would also work.

alerque commented on 2022-02-03 12:22 (UTC)

That "history" is useless, I'm sorry but Jason should know better than that how the AUR works.

I don't know what the actual history is but it probably revolves around duplicates and somebody's choice of which direction to merge. Note that the official packages have also changed names from being prefixed with Haskell to dropping said prefix, so this was probably done at a time when they matched.

I suggest reviving the "plain" name which does make more sense. You can do so by cloning the git repo, replacing the contents with this PKGBUILD (after renaming the pkgname of course), then uploading it as a new commit. Once the new commit comes across the AUR page for it should revive. Then you can file a merge request to have this package merged into that one (which will bring votes and comments as such). Lastly once the merge is done you should bump the pkgrel and add provides/conflicts/replaces for this old name and remove them what is now the canonical name.

1 2 Next › Last »