search

sillsdev / ptx2pdf

XeTeX based macro package for typesetting USFM formatted (Paratext output) scripture files
21 stars 7 forks source link

E: Internal Error, No file name for python3-ptxprint:amd64 #931

Closed KimB2017 closed 5 months ago

KimB2017 commented 7 months ago

I'm getting this error each time I install/update any packages in Synaptic, Wasta 20.04. The PTXPrint version that gives this error is 2.4.4, and I have been using this same version heavily with no apparent problems. I have tried reinstalling PTXPrint with no change in this error message... but I haven't wanted to uninstall it because I am on a tight schedule. I went to /var/cache/apt/archives and deleted the .deb file, thinking it would download again, but the installer files must be stored somewhere else because the package does not get redownloaded.

Should I be concerned, and is there anything I can do about it? Thanks!

mhosken commented 7 months ago

I'm suspicious that the 20.04 distribution is a bit messed up at the moment. We will try to sort it out.

On Thu, 30 Nov 2023, 12:22 Kim Blewett, @.***> wrote:

I'm getting this error each time I install/update any packages in Synaptic, Wasta 20.04. The PTXPrint version that gives this error is 2.4.4, and I have been using this same version heavily with no apparent problems. I have tried reinstalling PTXPrint with no change in this error message... but I haven't wanted to uninstall it because I am on a tight schedule. I went to /var/cache/apt/archives and deleted the .deb file, thinking it would download again, but the installer files must be stored somewhere else because the package does not get redownloaded.

Should I be concerned, and is there anything I can do about it? Thanks!

— Reply to this email directly, view it on GitHub https://github.com/sillsdev/ptx2pdf/issues/931, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLMO3IRU7332UNR3JWDXG3YHB27TAVCNFSM6AAAAABABC6IXGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYTQNJVGAYTKMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

markpenny commented 5 months ago

@KimB2017 Did this issue resolve itself in the end, or is there still something to be done? If all is well, please close the issue yourself. Ta!

KimB2017 commented 5 months ago

Yes, sorry... I figured you had fixed in the next update after this one.