Skip to content

office/pdfarranger: Update for current only, to version 1.13.0#391

Closed
brobr wants to merge 2 commits intoPonce:currentfrom
brobr:pdfarranger
Closed

office/pdfarranger: Update for current only, to version 1.13.0#391
brobr wants to merge 2 commits intoPonce:currentfrom
brobr:pdfarranger

Conversation

@brobr
Copy link
Copy Markdown
Contributor

@brobr brobr commented Mar 26, 2026

Hi Matteo, I have forked your repository but I can only at my end see 'current', get a sensible pull request against the default 'current', with your 'master' as 'base' it shows all the changes, I guess, between your 'master' branch and 'current'. Which I do not understand as I only do a sparse checkout on pikepdf and pdfarranger. Given that every starting repo in git is a master, I do not understand the following, obviously:

  If you want to fork/pull request do it only over master (the other branches are temporary and are always rebased on master).

Well, at least there are no pikepdf files in this request; something improved.

Ponce and others added 2 commits March 21, 2026 08:58
@github-actions
Copy link
Copy Markdown

reverse dependencies - office/pdfarranger

None

@github-actions
Copy link
Copy Markdown

✅ sbolint - office/pdfarranger ✅

pdfarranger: NOTE: pdfarranger.SlackBuild:60: SLKCFLAGS gets set, but never used.
pdfarranger: NOTE: pdfarranger.SlackBuild:61: LIBDIRSUFFIX gets set, but never used.
sbolint: pdfarranger checks out OK

@Ponce
Copy link
Copy Markdown
Owner

Ponce commented Mar 29, 2026

it's ok, make the pull request as you see fit, I have to manually apply anyway...

pushed this, thanks!

@Ponce Ponce closed this Mar 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants