Bug#1052693: live-manual-pdf: PDF manual is unreadable

2023-09-27 Thread Ralph Amissah
(i hope this is how to reply to the right place in the bugtracker, it
has been a while and recall using reportbugs? in the past).

I see the live-manual lack of pdfs bug and am jumping in somewhat
prematurely as I am making assumptions as to the likely cause without
having done any tests on Debian, and without knowing anything really
about the setup or infrastructure in place for generating live-manual
apart from the fact that sisu has been responsible for the output in
question in the bug report. The issue: "no pdfs" is somewhat familiar,
it reminds me of a previous issue on Debian that affected the ability
of sisu to produce pdfs.

The good news, since this bug report (using NixOS) I have:

- checked sisu with ruby-3.2 (and ruby-3.1) and it works

- (more specifically) checked sisu latex pdf output (against an old
reference copy of debian-live-manual sisu source markup) with ruby 3.2
and it works

The less good news:

- the tests were not on Debian but on NixOS though the program code is
the same for both distributions and has worked unchanged. (I switched
from Debian to using NixOS as my primary distribution around 2020 and
am not sure I even have a functional Debian box to log into or test
on).

- I have not programmed in ruby since 2015 (when I started my rewrite
of sisu in the programming language D)

- Since 2019 or so I use a D version of sisu that I have not shared or
decided how or whether to share.

 Back again to better news:

- The stoping of sisu genrating pdfs on Debian has happened a couple
of times before with new debian releases containing texlive packages
that rearrange the locations of latex .sty files within them. It has
(in the past) been relatively easy to fix.

./lib/sisu/texpdf_format.rb (towards the end of the file) contains
notes on steps that were taken last time to locate the .sty files
relevant to sisu and where they were to be found within Debian. Once
the relavant texlive packages are identified what needed to be done
was to make sure their dependencies were in place within ./debian for
sisu-pdf . It appears that this last needed to be done in 2019 and
2017 before that.

https://sisudoc.org/projects/sisu/log/?qt=grep=.sty
https://sisudoc.org/projects/sisu/commit/?id=55df651b572c5737ba01ac68f90d8475331a208b
https://sisudoc.org/projects/sisu/log/?h=debian=grep=tex
https://sisudoc.org/projects/sisu/commit/?h=debian=2a3350c959d83c88e498b87345b06b1f42f96df3
https://sisudoc.org/projects/sisu/commit/?h=debian=86f1de612b231a929e2d815097cdd3c4766809b9

I have no idea what texlive packaging in Debian looks like now, nor
indeed can I be certain that this (or indeed anything to do with sisu)
is the cause of the problem, (though it does seem likely to me). The
notes in the file ./lib/sisu/texpdf_format.rb should give an idea of
how to find out which texlive packages are needed as dependencies for
sisu to produce pdfs. Sisu is a ruby program that is largely
distribution agnostic, that there have been no hiccups in the
behaviour of sisu in producing pdfs on NixOS suggests, hopefully that
this is nothing major.

 If this is the cause a bug should be filed somewhere against sisu
packaging (texlive dependencies).

Given my current situation, willing to help but (for the time being at
least) using another distro, there should perhaps be another uploader
in debian, and sisu upstream should relinquish having a ./debian
(packaging) directory, which can be handled by the Debian project?

(i hope this is how to reply to the right place in the bugtracker, it
has been a while and recall using reportbug? in the past).

Greetings,
Ralph



Bug#1052693: live-manual-pdf: PDF manual is unreadable

2023-09-26 Thread Emanuele Rocca
Package: live-manual-pdf
Version: 2:20151217.2
Severity: important

Dear Maintainer,

All files under /usr/share/doc/live-manual/pdf/ seem to be broken.

Screenshot of `evince 
/usr/share/doc/live-manual/pdf/live-manual.portrait.en.a4.pdf.gz`
attached.

I've also tried decompressing the file to rule out any issues with that,
still there's no readable output in the resulting PDF.

  Emanuele