Bug 2274458 - latexmk 4.84 compiles only if pdf not exists
Summary: latexmk 4.84 compiles only if pdf not exists
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: latexmk
Version: 39
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-11 07:24 UTC by henrik
Modified: 2024-04-20 00:36 UTC (History)
3 users (show)

Fixed In Version: latexmk-4.85-1.fc39 latexmk-4.85-1.fc38 latexmk-4.85-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-19 01:17:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description henrik 2024-04-11 07:24:19 UTC
I upgraded today from 4.97 to 4.84 and all my documents are not compiling anymore. 
I tested also simple documents (without bibtex and co.) and it only compiles 
if the pdf does not exist. I did a rollback and now is working again. 

Reproducible: Always

Steps to Reproduce:
1. compile document first time
2. change document 
3. compile again -> fails

Comment 1 Ben Beasley 2024-04-11 11:51:03 UTC
The announcement[1] for latexmk 4.85 says:

This is a reversion to a previous version, since v. 4.84 has a serious bug,
which is triggered for example, when the output directory is specified by an
absolute pathname.

The CHANGES file in the source says:

From v. 4.84 to 4.85
  Correct bug that if $out_dir and $out2_dir referred to the same
    directory, but latexmk didn't detect that, then the subroutine copy
    reported an error, and latexmk treated that incorrectly as a fatal
    error.

That doesn’t sound exactly like what you are describing, but I still wonder if it might be related. Would it be possible for you to test latexmk 4.85 and see if that fixes the bug you’ve reported here?

- F39: sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-b3398ef7ee
- F38: sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-52f8251592

[1] https://ctan.org/ctan-ann/id/mailman.7807.1712174697.3764.ctan-ann@ctan.org

Comment 2 henrik 2024-04-11 11:56:51 UTC
Hey,
I tested and 4.85 works fine. Thanks for the quick response.
Best Henrik

Comment 3 Ben Beasley 2024-04-11 14:44:57 UTC
(In reply to henrik from comment #2)
> Hey,
> I tested and 4.85 works fine. Thanks for the quick response.
> Best Henrik

Thanks! Glad to hear it.

Comment 4 Fedora Update System 2024-04-11 14:45:31 UTC
FEDORA-2024-b3398ef7ee (latexmk-4.85-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-b3398ef7ee

Comment 5 Fedora Update System 2024-04-11 14:46:13 UTC
FEDORA-2024-52f8251592 (latexmk-4.85-1.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-52f8251592

Comment 6 Fedora Update System 2024-04-11 14:46:25 UTC
FEDORA-EPEL-2024-cfb5ea1dbf (latexmk-4.85-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-cfb5ea1dbf

Comment 7 Fedora Update System 2024-04-12 02:13:28 UTC
FEDORA-EPEL-2024-cfb5ea1dbf has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-cfb5ea1dbf

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2024-04-19 01:17:39 UTC
FEDORA-2024-b3398ef7ee (latexmk-4.85-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2024-04-19 02:52:36 UTC
FEDORA-2024-52f8251592 (latexmk-4.85-1.fc38) has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2024-04-20 00:36:17 UTC
FEDORA-EPEL-2024-cfb5ea1dbf (latexmk-4.85-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.