Bug#974724: no useful documentation of pdfjam commands

[Norbert Preining]

t; ② “pdfjam --help” gives a *different* synopsis than “man pdfjam”. So
> the man page BNF is not even completed by the help page. The BNF on
> the man page is therefore broken.

As said, send improvements to upupstream.

> ③ “pdfjam --help” says: “PDF files (JPG and PNG files are also
> allowed)”. I see no mention of MPS files. When I try an MPS file, it’s

As said, send improvements to upupstream.

> ④ References to Microsoft’s walled garden are littered throughout the
> docs. It’s fair enough to reference
> https://github.com/DavidFirth/pdfjam/issues for bug reports since that

Get a life. Reality is that a lot of development happens on github.
I am not interested in your religious aversion against github.

> ⑤ Docs say: “For more information, including a sample configuration
> file, see https://github.com/DavidFirth/pdfjam.”
> 
> Sample configs on Debian systems should go in:

If they are not in TeX Live, they are not packaged. End of the story.

> ⑥ One of the great benefits of pdfjam is the ability to take a JPG and
> embed into a PDF without touching the JPG payload. I am not aware of
> any other tool that has that capability. Tools like ImageMagick
> “convert” a JPG to PDF in a way that transcodes the JPG, which is
> inherently lossy. So pdfjam could highlight that unique feature, if
> anything to encourage other similar PDF tool projects to improve. The
> ultimate rationale would be to relieve the pdfjam project of pressure
> to support non-LaTeX users. The exiftran tool is the only other tool
> AFAIK that can manipulate JPG files in a non-lossy way, but it cannot
> produce a PDF.

As said, send improvements to upupstream.


Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1080322: latexmk: add -parallel=N option

[Norbert Preining]

Hi Barak,

> Okay, I'll forward it upstream.

Thanks, much appreciated.

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1080322: latexmk: add -parallel=N option

[Norbert Preining]

Hi Barak,

nice idea, but not really in the scope of Debian to add new
functionality.
According to the last line of 
$ latexmk --help | tail -1
Report bugs etc to John Collins .
;-)

Best regards

Norbert

> Of course it was hallucinating. Please make its hallucination a reality!

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1079786: texlive-latex-base: buggy testpage.tex: missing \usepackage{geometry}

[Norbert Preining]

Hi

> The goal of testpage.tex is to match the output to the physical
> page size, and the default paper size must *not* be used since the
> file explicitly asks for a paper size. Hence the need for a fix.

Since this is a LaTeX base file, please sent your complaints to the
LaTeX team, they have an issue tracker.

> Note that paperconf is designed to allow a user-level default.
> However, TeX uses a system-level default only. For instance, with

Since when? I don't have paperconf available anymore, but when I wrote
the support code, there was only /etc/papersize ...

>   PAPERSIZE=a5 pdflatex 
> /usr/share/texlive/texmf-dist/tex/latex/base/testpage.tex
> 
> the generated PDF file still has the A4 page size, because A4 is still
> the system-level default for TeX.

Yes, and I explained you why. There is no setup for physical papersize
done in testfile.tex.


> Changing the paperconf default has the effect of reconfiguring the TeX
> defaults, like that:

Yes, I know.

> Said otherwise, the end user cannot choose the default for TeX
> (not even statically).

On a per user basis. Yes, because this would require format dumps
per user, which is a pain, and will break practically every system
update.

> BTW, the TeX-level configuration isn't even always consistent.
> For instance, tl-paper was giving

You can set paper size per application. No problem with me. You probably
have done that at some point.

Or, the paper code parsing for context is broken.

One of the two things.

> This is crap design.

What would be a better design?

Instead of complaining on a problem that is a problem with LaTeX core
team document, and complaining about "crap design", what about
constructive input?

And dont forget, what about copying testpage.tex, and add the 
    \usepackage{geometry}
and be happy?

Is that that hard?

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1079786: texlive-latex-base: buggy testpage.tex: missing \usepackage{geometry}

[Norbert Preining]

> \papertype=a5paper
> \doublesided=n

To quote from https://texfaq.org/FAQ-papergeom

> Knuth seems not to have considered paper size as something the TeX engine 
> needs to know about.

This is the core problem.

You **always** need to have to set a lot of parameters, see the geometry
package documentation.

None of the above commands does anything in this direction, so the
default physical paper size is used, which is set via paperconf.

What youare asking is a fix to testpage.tex, to use geometry or some
other ways to set the *physical* page size. But that is as said not the
basic assumption. You can use testpage, and then print it on the correct
page size.

> According to the TeX Live mailing-list, this is a Debian-specific
> issue.

paperconf is Debian specific, so the default physical page size setup is
Debian specific (TeX defaults to letter).

The testpage.tex itself is what it is.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1072743: texlive-extra-utils: pdfxup: --pages option fails if page range omits start or end of range

[Norbert Preining]

> Yes, I'll be happy to discuss it with upstream.
> Should I CC you?  Or just update the Debian bug as needed?

Thanks Sanjoy, much appreciated!

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1072211: texlive-base: pdflatex very slow after upgrading to texlive 2024.20240401-2

[Norbert Preining]

On Thu, 30 May 2024, J.L.G. Pallero wrote:
> After the last upgrade of texlive packages in Sid, from 2023.20240207-1 to 
> 2024.20240401-2, I found pdflatex very slow in the compilation. The same 
> documents
> compiled with the 2023.20240207-1 version were bult quicker. Is it a problem 
> on my side or is a generalbehavior?

Do you have a test document that you can share?

Also, the output of running the compile command with
pdflatex -kpathsea-debug=
might help, but that can get considerably volominous.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1071783: Bug#1071762: texlive-base: tlmgr documentation omissions, inaccuracies, and pitfalls

[Norbert Preining]

same situation.

BTW, for many years I **did** exclude tlmgr from the Debian packages,
and only on great pressure from Debian users I implemented the
"usermode" feature in tlmgr itself, and then included tlmgr in this
restricted mode in Debian.

Anyway, I am not anymore the maintainer. But I think the decisions I
made are still valid. And the documentation is all there.

If something is incorrect in the documentation of usermode or things
don't work as expected in usermode, I am open for bug reports - sent to
the TeX Live mailing list, not Debian. I will be happy to fix them.
But the behavior that is advertised in Debian is what is documented in
the manual page.

Maybe we should make the banner with the usermode warning like MUCH
BIGGER!

***
** WARNING 
***
Because you are using tlmgr as provided by Debian, tlmgr will
run in **usermode**.
Before continuing, read the section on usermode in the manual of
tlmgr, available by typing
    tlmgr help
***

But I think people will get annoyed seeing this every time.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1071762: texlive-base: tlmgr documentation omissions, inaccuracies, and pitfalls

[Norbert Preining]

Hi Manny,

All the three bugs boil down to the same:

tlmgr is NOT supported if you install it via Debian.
Only VERY REDUCED functionality is provided, as you found.

For example, tlmgr info does not work because we don't have a tlpdb
at hand.

> $ tlmgr --usermode info acro
> TLPDB: Cannot determine type of tlpdb from /home/blee/.local/share/texmf!
> tlmgr: user mode not initialized, please read the documentation!

>   $ tlmgr --usermode info acro
> /usr/bin/tlmgr: TLPDB::from_file could not initialize from: 
> https://mirror.ctan.org/systems/texlive/tlnet/tlpkg/texlive.tlpdb
> /usr/bin/tlmgr: Maybe the repository setting should be changed.
> /usr/bin/tlmgr: More info: https://tug.org/texlive/acquire.html

>   “(running on Debian, switching to user mode!)”
> 
> I took that to mean tlmgr detected a Debian system for some reason
> beyond me, and that it also switched to user mode for some other
> reason beyond me. It would be more clear if it said:

>   “(running on Debian THUS switching to user mode!)”

Yes, that is the meaning. I think this is obvious enough.,

> Users will still be astonished about why Debian implies that we can
> only run as a user, but it would at least be clear that user mode is
> an intentional consequence of being on Debian.

See above.

> $ torsocks tlmgr --usermode list
> 
> tlmgr: Local TeX Live (2022) is older than remote repository (2024).
> Cross release updates are only supported with
>   update-tlmgr-latest(.sh/.exe) --update
> See https://tug.org/texlive/upgrade.html for details.

You need to point it to the last available 2022 repository, see historic
TL releases.

> This seems to imply that users cannot list packages unless their
> texlive installation is the same version as that of the remote
> repository. That’s a bit drastic to simply get a list of packages and

Yes.

> many Debian users would not want to update the whole texlive
> installation outside of the apt manager. Ideally, apt would have

Don't use tlmgr on Debian if you are not happy with the insufficiences.

> So the sensible approach appears to be to find a mirror that matches
> the locally installed version. The PDF guide mentions this location:

Yes, see above, historic
https://www.tug.org/historic/
So for 2022 you can for example
https://pi.kwarc.info/historic/systems/texlive/2022/tlnet-final/

>   https://ctan.org/mirrors/mirmon

CTAN only carries the most recent release.

> That list of mirrors does not mention which texlive version is
> available. It seems having a version-aligned repo is critical to using

The most recent.

> planned: to gracefully downgrade the acro package and pin that older
> version. That doc suggests using apt, which is generally sensible but

No IT CANNOT.

the files are installed by root and apt.
tlmgr can do this when you run upstream TeX LIve, but NOT Debian TeX
Live.

You cannot downgrade but downgrade to older versions of Debian / TeX
Live.

There is nothing to do about this, tlmgr is the configuration management
system for TeX Live as it is provided by upstream. It conflicts with
apt/dpkg. Trying to do a few things by setting it to user mode does
not fix all the other problems.

Best regards

Norbert
(author of tlmgr, and author of the TeX Live packaging in Debian)


--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1070150: Loading of expl3.ltx **extremely** slow on emulated runs

[Norbert Preining]

Hi Max,

sorry, but I don't understand!!

On Wed, 01 May 2024, Max Chernoff wrote:
> I don't think that this is TeX-related. From a Fedora 39 x86_64 host:

Your data:

> $ podman run --arch arm64 --rm -it --pull always debian:stable /bin/bash
[...]
> real  0m52.253s


> $ podman run --arch arm64 --rm --pull always -it debian:sid /bin/bash
[...]
> real  3m52.398s

That is a 4 times increase, ok, this does a lot of things. IN
particular, apt uses fsync a lot.

But what I measured in the emails is *only* the loading of one text
file, without IO ops.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1070150: Loading of expl3.ltx **extremely** slow on emulated runs

[Norbert Preining]

Hi all,

at Debian they got a report that loading expl3.ltx when building formats
is **extremely** slow when running under emulations:

1070...@bugs.debian.org

Running fmtutil output through ts (timestamp utility from moreutils):

May 01 14:28:46 LaTeX2e <2024-06-01> pre-release-0 (develop 2024-5-1 branch)
May 01 14:28:46 (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.ltx
May 01 14:51:15 
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex)) hacks,
May 01 14:51:19 document commands, control, par, spacing, files, font 
encodings, lengths,

That is 23 **minutes** to load expl3-code.tex. Ok, the file is nearly 4k
lines, but still, 23 minutes seems to be excessive.

Any ideas?

Please keep the Cc

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1070150: texlive-latex-extra: performance regression under emulation with 2023.20240207-1

[Norbert Preining]

> When running the hook with the 2023.20240207, this step takes around 3 hours.

Ouch, that hurts.

> I'm guessing that this is related to enabling lua on aarch64 finally, but I'm
> not familiar at all with latex and how to get the smallest possible test case 
> to
> show the issue.

If you suspect lua, then could you please run (as root or via sudo)
time fmtutil-sys --byengine luatex
time fmtutil-sys --byengine luajittex
and let us see the times there?

> A way to reproduce the issue would be to install debootstrap, qemu-user-static
> and systemd-nspawn and then run apt-get install texlive-latex-extra

Sorry, no Debian system around anymore.

> On an arm64 host (VM on an original M1 Macbook Air), this is fine

Nor that.

> sudo debootstrap --arch arm64 sid sid
> sudo systemd-nspawn -D sid
> time apt-get install texlive-latex-extra -y
> 
> real 181m11.687s
> user 181m43.534s
> sys  1m5.422s
> 
> texlive-latex-recommended: 2023.20240207-1

Can you show the *actual* output?

And, maybe install moreutils and run it through ts

apt-get install texlive-latex-extra -y | ts 

That would give a hint which part is taking so much time.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1067614: texlive-latex-extra: pdfcomment docs reference the cloud instead of local files; also font option broken

[Norbert Preining]

Hi Manny,

thanks for the detailed and long report, but I fear that none of the
issues are related to Debian nor TeX Live itself either.

On Sun, 24 Mar 2024, Manny wrote:
> There is a Debian-specific bug in the manual located here:
> 
>   /usr/share/doc/texlive-doc/latex/pdfcomment/pdfcomment.pdf
> 
> Page 7 links to example.pdf here:
> 
>   http://mirror.ctan.org/macros/latex/contrib/pdfcomment/doc/example.pdf

This is what the source document does. We don't rewrite all the source
documents, nor do we compile all the pdfs, neither does TeX Live.
Thus, this is an issue that can only be fixed by upupstream.

> Apart from that minor issue, there’s a bigger problem upstream. The
> “font” option is somewhat broken. Use of the font option produces

Again, this is a problem of the original package, nothing we here at
Debian nor I over at TeX Live can deal with.

> Poppler is apparently dropping the ball on fonts, even the so-called

I wouldn't be surprised, Poppler in Debian has an nearly infinite
history of breaking APIs as well as everything else. There is a reason
we on the TeX Live side use an embedded libpoppler, since anything else
is a guarantee for breakage.

> It’s worth noting that the Debian Social Contract (DSC) and Debian
> Free Software Guidelines (DFSG) condemn discrimination. Blind people
> cannot likely get passed all those CAPTCHAs to reach the upstream bug
> tracker. One might say the upstream bug tracker is not Debian’s
> problem. OTOH, the texlive package (understandably) steers people to
> file bugs upstream because this beast has the complexity of an OS in
> itself. But at the same time there’s an infrastructural problem when
> people are being directed into those shitty upstream walled gardens
> particularly when thy are discriminatory. I don’t have the answer --
> just laying out the problem.

Sorry to hear that, but again, this is out of our reach. We cannot save
the world and all software developers.
As said, at Debian we cannot do anything to fix this.
At TeX Live, we cannot do either.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1058452: tex-common: "fmtutil failed" in post-installation script

[Norbert Preining]

> You mean the dep version tex-common or the one for texlive-formats-extra?

Since texlive-formats-extra ships the format definitions, it needs to
require the version of texlive-whatever that ships the .ini files,
so the dep should be in texlive-formats-extra, IMO.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1058452: tex-common: "fmtutil failed" in post-installation script

[Norbert Preining]

On Wed, 13 Dec 2023, =?UTF-8?Q?Preu=C3=9...@buxtehude.debian.org wrote:
> Is it fine to close the case?

Actually no, the packages should have proper dependencies that this
cannot happen.

Hilmar, please bump the minimal dep on tl-base to the required level.

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1058452: tex-common: "fmtutil failed" in post-installation script

[Norbert Preining]

The log contains

fmtutil [WARNING]: inifile pdfxmltex.ini for pdfxmltex/pdftex not found.
fmtutil [WARNING]: inifile xmltex.ini for xmltex/pdftex not found.

These seem to be missing

Norbert

-- 
PREINING Norbert  https://www.preining.info
Mercari   +    IFMGA ProGuide    +   TU Wien    +   TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Dec 12, 2023 20:09:29 Sanjoy Mahajan :

> Package: tex-common
> Version: 6.18
> Severity: normal
> X-Debbugs-Cc: none, Sanjoy Mahajan 
> 
> On recent upgrades, setting up tex-common fails with the following error
> (regenerated using 'apt install -f'):
> 
>   # apt install -f
>   Setting up tex-common (6.18) ...
>   Running mktexlsr. This may take some time... done.
>   Running mtxrun --generate. This may take some time... done.
>   Running updmap-sys. This may take some time... done.
>   Running mktexlsr /var/lib/texmf ... done.
>   Building format(s) --all.
>   This may take some time...
>   fmtutil failed. Output has been stored in
>   /tmp/fmtutil.amiyTgkU
>   Please include this file if you report a bug.
> 
>   dpkg: error processing package tex-common (--configure):
>    installed tex-common package post-installation script subprocess returned 
> error exit status 1
>   Errors were encountered while processing:
>    tex-common
>   E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> I've attached /tmp/fmtutil.amiyTgkU
> 
> The relevant lines may be its last lines:
> 
>   fmtutil [WARNING]: inifile pdfxmltex.ini for pdfxmltex/pdftex not found.
>   fmtutil [WARNING]: inifile xmltex.ini for xmltex/pdftex not found.
>   fmtutil [INFO]: disabled formats: 1
>   fmtutil [INFO]: successfully rebuilt formats: 43
>   fmtutil [INFO]: not available formats: 2
>   fmtutil [INFO]: failed to build: 2 (pdftex/pdfxmltex pdftex/xmltex)
>   fmtutil [INFO]: total formats: 48
>   fmtutil [INFO]: exiting with status 2
> 
> The exit status of 2 makes me think that it results from there being two
> unavailable formats.
> 
> p.s. This error seems different from bug #1051243 (which involved locale
> errors).
> 
> 
> -- System Information:
> Debian Release: sid
>   APT prefers unstable
>   APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
> 'testing-debug'), (500, 'stable-security'), (500, 'testing'), (500, 
> 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.5.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages tex-common depends on:
> ii  ucf  3.0043+nmu1
> 
> tex-common recommends no packages.
> 
> Versions of packages tex-common suggests:
> ii  debhelper  13.11.8
> 
> Versions of packages texlive-base depends on:
> ii  debconf [debconf-2.0]  1.5.82
> ii  libpaper-utils 1.1.29
> ii  sensible-utils 0.0.20
> ii  texlive-binaries   2023.20230311.66589-8
> ii  ucf    3.0043+nmu1
> ii  xdg-utils  1.1.3-4.1
> 
> Versions of packages texlive-base recommends:
> ii  lmodern  2.005-1
> 
> Versions of packages texlive-base suggests:
> ii  evince [postscript-viewer]    45.0-1
> ii  ghostscript [postscript-viewer]   10.02.1~dfsg-1
> ii  gv [postscript-viewer]    1:3.7.4-2+b1
> ii  mupdf [pdf-viewer]    1.23.7+ds1-1
> ii  okular [postscript-viewer]    4:23.08.1-2
> ii  perl-tk   1:804.036+dfsg1-1
> ii  xpdf [pdf-viewer] 3.04+git20220601-1+b2
> pn  xzdec 
> ii  zathura-pdf-poppler [pdf-viewer]  0.3.2-1
> ii  zathura-ps [postscript-viewer]    0.2.7-2+b2
> 
> Versions of packages texlive-binaries depends on:
> ii  libc6   2.37-13
> ii  libcairo2   1.18.0-1
> ii  libfontconfig1  2.14.2-6
> ii  libfreetype6    2.13.2+dfsg-1
> ii  libgcc-s1   13.2.0-8
> ii  libgraphite2-3  1.3.14-1
> ii  libharfbuzz0b   8.0.1-1
> ii  libicu72    72.1-4
> ii  libkpathsea6    2023.20230311.66589-8
> ii  libmpfr6    4.2.1-1
> ii  libpaper1   1.1.29
> ii  libpixman-1-0   0.42.2-1
> ii  libpng16-16 1.6.40-2
> ii  libpotrace0 1.16-2
> ii  libptexenc1 2023.20230311.66589-8
> ii  libstdc++6  13.2.0-8
> ii  libsynctex2 2023.20230311.66589-8
> ii  libtecki

Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023

[Norbert Preining]

Hi Vincent,

Since I am not using Debian, nor developing for Debian, I think I stop
arguing here. No need to discuss my opinion on that matter further.
Feel free to bring it up to the TC, or d-d, or whereever you feel is the
correct place.

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023

[Norbert Preining]

On Sun, 26 Nov 2023, Vincent Lefevre wrote:
> Could you cite documentation saying that root must not set
> arbitrary environment variables?

I never said that. But if they are set, root must be aware of the
consequences, and the envvars might have effect on how packages work.

> was actually there on purpose). But this could have been done
> really on purpose. And this would have broken the package
> installation.

root can make / ro and break installation.
root can set their own shell to fish with probably interesting
consequences.
root can do soo many things to break package installation

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023

[Norbert Preining]

On Sat, 25 Nov 2023, Vincent Lefevre wrote:
> I didn't break anything. Any user, including root, may have his own
> environment variables for his own use. This should never interfer

No. That is simply not true. Not root.

> Why not unsetting TEXINPUTS in the postinst script?

I told you this already, please read.
Because root might set TEXINPUTS on *purpose*.
How should the package installation distinguish a falsely set TEXINPUTS
from a correctly set TEXINPUTS?


Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023

[Norbert Preining]

On Fri, 24 Nov 2023, Vincent Lefevre wrote:
> The issue disappears if I remove my glyphtounicode.tex file and
> do "apt install --reinstall texlive-base".

sudo fmtutil-sys -all

would also do it.

> If I understand correctly, /var/lib/texmf/web2c/pdftex/pdflatex.fmt is
> generated by fmtutil, but its man page does not say that $TEXINPUTS is
> used.

Because, as you were told already, this is an inherent and historic TeX
variable.

And because you decided to break your system by setting up env vars as
root, without knowing their impact. That is a guaranteed recipe for
shooting yourself.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1052298: metafun broken?

[Norbert Preining]

Hi Siep,

> context --metapost --format=metafun --pdf mfun-mrun-demo.mp

That is not really a solution for other tools that run metafun as is. We have 
to be aware that we are not in a vacuum and our tools are used.

Why have the mkii files been dropped from TL2022 in the first place, was there 
an urgent reason for that?

Thanks and best regards

Norbert

-- 
PREINING Norbert  https://www.preining.info
Mercari   +    IFMGA ProGuide    +   TU Wien    +   TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Sep 23, 2023 04:45:34 Siep Kroonenberg :

> On Fri, Sep 22, 2023 at 09:49:04PM +0900, Norbert Preining wrote:
>> Hi all,
>> 
>> is metafun broken?
> 
> While testing metafun while working on inclusion of ConTeXt in
> TL2023, I successfully used command-lines such as
> 
> context --metapost --format=metafun --pdf mfun-mrun-demo.mp
> 

Bug#1052298: metafun broken?

[Norbert Preining]

Hi all,

is metafun broken?

$ mpost
This is MetaPost, version 2.02 (TeX Live 2023) (kpathsea version 6.3.5)
**\relax
(/home/norbert/tl/2023/texmf-dist/metapost/base/mpost.mp
(/home/norbert/tl/2023/texmf-dist/metapost/base/plain.mp
Preloading the plain mem file, version 1.005) )
*input metafun.mp
(/home/norbert/tl/2023/texmf-dist/metapost/context/base/common/metafun.mp
! I can't open file `metafun.mpii'.
l.6 input metafun.mpii
  
Please type another input file name: 



There is only metafun.mpiv

Any ideas?

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1052298: metafun broken?

[Norbert Preining]

On Fri, 22 Sep 2023, Zdenek Wagner wrote:
> identical. metafun.mpii is present in TL2022 but missing in TL2023.

indeed, all of
texmf-dist/metapost/context/base/mpii/
is missing in TL 2023, which means metafun does not work.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1041508: tex-common: fmutil fails to rebuild formats

[Norbert Preining]

On Sat, 02 Sep 2023, Joerg Dorchain wrote:
> Indeed.

That file is buggy:

 \HINTstream0 %main text
 \HINTstream\footins   
   \HINTsetstream\topins = %topinsert 
-prefered 0
+preferred 0
   {% 
 \HINTafter = {}
   }
   \HINTsetstream\footins =%footnotes
-prefered 255
+preferred 255
 ratio 0
   {%
 \hsize=300pt


The "prefered" needs to be changed to "preferred", then it works.

@Hilmar, that should be fixed by a new checkout, or patching the above.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1041508: tex-common: fmutil fails to rebuild formats

[Norbert Preining]

On Sat, 02 Sep 2023, Joerg Dorchain wrote:
> (hiplainpage.tex
> ! Missing { inserted.

Very strange. Works on my upstream TeX Live.

Can you show me
hiplainpage.tex
?
You can find it with
kpsewhich hiplainpage.tex
it should be in
/usr/share/texlive/texmf-dist/tex/hitex/base/hiplainpage.tex
(AFAIR)

I get proper formats build.

Thanks in advance

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1041508: tex-common: fmutil fails to rebuild formats

[Norbert Preining]

On Sat, 02 Sep 2023, Joerg Dorchain wrote:
> fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/pdftex/mltex.log

That file would be useful.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1041508: tex-common: fmutil fails to rebuild formats

[Norbert Preining]

Hi

On Sat, 02 Sep 2023, Joerg Dorchain wrote:
> > > fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/pdftex/mltex.log
> > 
> > That file would be useful.
> 
> There you are.

Sorry, copied the wrong line. That worked,
The format that failed to build was hitex AFAIR, that would be
/var/lib/texmf/web2c/hitex/hitex.log

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1038920: python3-certbot-dns-gandi: Update from Debian 11 -> 12 leaves certificate updates broken

[Norbert Preining]

> sed -i -- 's/certbot-plugin-gandi:dns/dns-gandi/g' 
> /etc/letsencrypt/renewal/*.conf

I see a few issues:

* First of all, you need to convert some - to _ since these are translated
  into python modules

* Then, does that suffice? Looking into the conf files I have, I also see lines
authenticator = dns-gandi
coming from the calls

OLD:
certbot certonly --certbot-plugin-gandi:dns-credential 
/etc/letsencrypt/gandi.ini -d DOMAIN_LIST

NEW:
certbot certonly --authenticator dns-gandi --dns-gandi-credentials 
/etc/letsencrypt/gandi.ini -d DOMAIN_LIST

Now with the above you would rewrite the config file lines
certbot-plugin-gandi:dns_credentials = ...
to
dns_gandi_credentials = ...
(Note the _ here for dns_gandi_credentials and most probably also for
dns_credentials, but I cannot check now!)

But then still the new line
authenticator = dns-gandi
is missing.

Just as food for thoughts.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1038920: python3-certbot-dns-gandi: Update from Debian 11 -> 12 leaves certificate updates broken

[Norbert Preining]

Hi Harlan,

> Thanks for letting me know.  I've spoken with upstream about this as
> well, and to see what we can do in the future to ensure something like
> this doesn't happen again. I've written up a draft preinst script that
> should rewrite the config files to remove the problem.

Great, thanks for taking action.

> Do you still have a host that's in the buggy state, or did you fix

Sorry no, the domain certificates were running out, because as I mentioned,
there was also no warning message, so I only realized it when letsencrypt
send an email that the domains run out.

So all of them are now update.

> them all with the workaround?  Because it's going to be fixed in a
> preinst, I'd like more testing (and more eyes) on it than I normally
> would, just for caution's sake.

You could still send me the code and I give it an eye ;-)

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1037358: mailman3-web: Upgrade from Debian 11 to Debian 12 broke mailman/mailman3-web

[Norbert Preining]

uot;/usr/lib/python3/dist-packages/django/db/models/query.py", line 
> > 431, in get
> > num = len(clone)
> >   ^^
> >   File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 
> > 262, in __len__
> > self._fetch_all()
> >   File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 
> > 1324, in _fetch_all
> > self._result_cache = list(self._iterable_class(self))
> >  
> >   File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 51, 
> > in __iter__
> > results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, 
> > chunk_size=self.chunk_size)
> >   
> > ^^
> >   File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", 
> > line 1175, in execute_sql
> > cursor.execute(sql, params)
> >   File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 
> > 66, in execute
> > return self._execute_with_wrappers(sql, params, many=False, 
> > executor=self._execute)
> >
> > 
> >   File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 
> > 75, in _execute_with_wrappers
> > return executor(sql, params, many, context)
> >
> >   File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 
> > 79, in _execute
> > with self.db.wrap_database_errors:
> >   File "/usr/lib/python3/dist-packages/django/db/utils.py", line 90, in 
> > __exit__
> > raise dj_exc_value.with_traceback(traceback) from exc_value
> >   File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 
> > 84, in _execute
> > return self.cursor.execute(sql, params)
> >^^^^^^^^
> >   File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", 
> > line 423, in execute
> > return Database.Cursor.execute(self, query, params)
> >
> > django.db.utils.OperationalError: no such column: 
> > hyperkitty_mailinglist.archive_rendering_mode
> 
> Erm, this one is weird, I did not meet it. What cron are you referring
> to?
> 
> The hourly tasks cron for mailman3 web runs smoothly here.

Hmm, I guess it was this one
@hourlywww-data [ -f /usr/bin/django-admin ] && flock 
-n /var/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs 
hourly

Do you have hyperkitty active?

I faintly remember (now some weeks have passed) that I had to do something
to get the new table column added:

no such column: hyperkitty_mailinglist.archive_rendering_mode

Maybe that was the source of the error, too? Not sure.
Sorry for not remembering that now.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1038920: python3-certbot-dns-gandi: Update from Debian 11 -> 12 leaves certificate updates broken

[Norbert Preining]

Package: python3-certbot-dns-gandi
Version: 1.4.3-1
Severity: serious

Dear Maintainer,

with the update of certbot and the DNS Gandi plugin, the command line
arguments for requesting a certificate have changed.

This is not taken into account during upgrade, which left all domains
that are normally being renewed via the gandi plugin broken.

Above that, no warning email was sent to the admin user about this problem.

The letsencrypt.log file contains

2023-06-18 00:49:00,298:ERROR:certbot._internal.renewal:Renewal configuration 
file /etc/letsencrypt/renewal/SOOME.DOMAIN.conf (cert: SOME.DOMAIN) produced an 
unexpected error: 'Namespace' object has no attribute 
'certbot_plugin_gandi:dns_credentials'. Skipping.
2023-06-18 00:49:00,302:DEBUG:certbot._internal.renewal:Traceback was:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/certbot/_internal/renewal.py", line 501, 
in handle_renewal_request
renewal_candidate = _reconstitute(lineage_config, renewal_file)
^^^
  File "/usr/lib/python3/dist-packages/certbot/_internal/renewal.py", line 103, 
in _reconstitute
_restore_plugin_configs(config, renewalparams)
  File "/usr/lib/python3/dist-packages/certbot/_internal/renewal.py", line 173, 
in _restore_plugin_configs
if config_item.startswith(plugin_prefix + "_") and not 
cli.set_by_cli(config_item):
   
^^^
  File "/usr/lib/python3/dist-packages/certbot/_internal/cli/__init__.py", line 
489, in set_by_cli
if not isinstance(getattr(detector, var), _Default):
  ^^
AttributeError: 'Namespace' object has no attribute 
'certbot_plugin_gandi:dns_credentials'


Solution is to run **once** per domain the correct renew line
certbot certonly --authenticator dns-gandi --dns-gandi-credentials 
/etc/letsencrypt/gandi/gandi.ini -d SOME.DOMAIN

Best regards

Norbert

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'oldstable-updates'), (500, 
'oldstable-security'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-certbot-dns-gandi depends on:
ii  certbot  2.1.0-4
ii  python3  3.11.2-1+b1
ii  python3-certbot [python3-certbot-abi-2]  2.1.0-4
ii  python3-requests 2.28.1+dfsg-1

python3-certbot-dns-gandi recommends no packages.

python3-certbot-dns-gandi suggests no packages.

-- no debconf information

Bug#985017: python3-whoosh: SyntaxWarning during package installation

[Norbert Preining]

Package: python3-whoosh
Version: 2.7.4+git6-g9134ad92-7
Followup-For: Bug #985017

Dear Maintainer,

same here, and since this module is used in mailman3-web and run every hour,
cron emails are sent out.

Thanks

Norbert

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-whoosh depends on:
ii  python3  3.11.2-1+b1

python3-whoosh recommends no packages.

Versions of packages python3-whoosh suggests:
pn  python-whoosh-doc  

-- no debconf information

Bug#1037358: mailman3-web: Upgrade from Debian 11 to Debian 12 broke mailman/mailman3-web

[Norbert Preining]

Package: mailman3-web
Version: 0+20200530-2.1
Severity: important

Dear Maintainer,

With the upgrade from Debian 11 to Debian 12 a lot of problems popped up
around mailman/web:

- /etc/mailman/mailman-web.py needs updates:

# Updates require this, should already be in Debian's package, but isn't
# See https://gitlab.com/mailman/hyperkitty/-/issues/401
DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'
# /usr/lib/python3/dist-packages/django_q/conf.py contains
# conf.py:TIMEOUT = conf.get("timeout", None)
# conf.py:RETRY = conf.get("retry", 60)
# which is broken
Q_CLUSTER = {
'timeout': 300,
'save_limit': 100,
'orm': 'default',
'retry': 360,
}

since these values are not taken into the Debian packages, although they
are necessary


- /etc/cron.d/mailman3 contains a call to gatenews which triggers errors
  and probalby should not be called in the cron script


- even with the above changes, the hourly run job fails (that is actually
  a serious bug!)

/usr/lib/python3/dist-packages/whoosh/codec/whoosh3.py:1116: SyntaxWarning: 
"is" with a literal. Did you mean "=="?
  elif fixedsize is 0:
[ERROR/MainProcess] Failed indexing 1 - 1 (retry 5/5): no such column: 
hyperkitty_mailinglist.archive_rendering_mode (pid 4974): no such column:
hyperkitty_mailinglist.archive_rendering_mode
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/django/db/models/fields/related_descriptors.py",
 line 173, in __get__
rel_obj = self.field.get_cached_value(instance)
  ^
  File "/usr/lib/python3/dist-packages/django/db/models/fields/mixins.py", line 
15, in get_cached_value
return instance._state.fields_cache[cache_name]
   
KeyError: 'mailinglist'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, 
in _execute
return self.cursor.execute(sql, params)
   
  File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", 
line 423, in execute
return Database.Cursor.execute(self, query, params)
   
sqlite3.OperationalError: no such column: 
hyperkitty_mailinglist.archive_rendering_mode

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", 
line 119, in do_update
backend.update(index, current_qs, commit=commit)
  File "/usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py", 
line 258, in update
doc = index.full_prepare(obj)
  ^^^
  File "/usr/lib/python3/dist-packages/haystack/indexes.py", line 235, in 
full_prepare
self.prepared_data = self.prepare(obj)
 ^
  File "/usr/lib/python3/dist-packages/haystack/indexes.py", line 226, in 
prepare
self.prepared_data[field.index_fieldname] = field.prepare(obj)
^^
  File "/usr/lib/python3/dist-packages/haystack/fields.py", line 236, in prepare
return self.convert(super().prepare(obj))

  File "/usr/lib/python3/dist-packages/haystack/fields.py", line 105, in prepare
values = self.resolve_attributes_lookup(current_objects, attrs)
 ^^
  File "/usr/lib/python3/dist-packages/haystack/fields.py", line 125, in 
resolve_attributes_lookup
if not hasattr(current_object, attributes[0]):
   ^^
  File 
"/usr/lib/python3/dist-packages/django/db/models/fields/related_descriptors.py",
 line 187, in __get__
rel_obj = self.get_object(instance)
  ^
  File 
"/usr/lib/python3/dist-packages/django/db/models/fields/related_descriptors.py",
 line 154, in get_object
return qs.get(self.field.get_reverse_related_filter(instance))
   ^^^
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 431, in 
get
num = len(clone)
  ^^
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 262, in 
__len__
self._fetch_all()
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 1324, 
in _fetch_all
self._result_cache = list(self._iterable_class(self))
 
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 51, in 
__iter__
results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, 
chunk_size=self.chunk_size)
  
^^
  File "/usr/lib/python3/

Bug#1035857: texlive-fonts-extra: broken font symlinks for junicode

[Norbert Preining]

> If you say the broken symlinks are not really a problem for bookworm (and

Broken symlinks in the TEXMF dirs are not a problem, since kpathsea will
ignore them.

So the worst thing is that some font is not available, that is hardly a
problem since the fonts are not generally used.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1035461: texlive-binaries: Allow install of TeXlive without SSE2

[Norbert Preining]

On Sat, 06 May 2023, =?UTF-8?Q?Preu=C3=9...@buxtehude.debian.org wrote:
> fmtutil [ERROR]: not building luajithbtex due to missing engine: luajithbtex
> fmtutil [ERROR]: not building luajittex due to missing engine: luajittex

Ah, you probably did run it manually, right?

But the tex-common postinst contains that:

# fmtutil program and common arguments
# --sys we are running in fmtutil-sys mode
# --strict  error out if a format is not build
# --no-error-...luajittex is not available on all archs
FMTUTIL="fmtutil --sys --strict 
--no-error-if-no-engine=luajittex,mfluajit,luajithbtex"

That should do it.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1035461: texlive-binaries: Allow install of TeXlive without SSE2

[Norbert Preining]

Hi Hilmar,

On Sat, 06 May 2023, =?UTF-8?Q?Preu=C3=9...@buxtehude.debian.org wrote:
> fmtutil [ERROR]: not building luajithbtex due to missing engine: luajithbtex
> fmtutil [ERROR]: not building luajittex due to missing engine: luajittex
> fmtutil [INFO]: disabled formats: 2

Hmm, is fmtutil run with
--no-error-if-no-engine=luajithbtex,luajittex,mfluajit
? That *should* give exit status 0 even if the engines are not
available.
This is what we do in TL, and that works since long, since many of the
archs we support don't have the jit variants.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1035461: texlive-binaries: Allow install of TeXlive without SSE2

[Norbert Preining]

On Wed, 03 May 2023, =?UTF-8?Q?Preu=C3=9...@buxtehude.debian.org wrote:
> > code that uses SSE2 instructions, so `texlive-binaries` was changed to
> > require `sse2-support`.

Hmm, so SSE2 is not a requirement on Debian?
How does luajit itself work on your system, how does it behave?

> As I understood the situation it is not luatex, which does not work on
> your computer, but just the luajit... variants. So I could split them
> out into a new package, which is only needed by texlive-extra-utils, b/c
> this package tries to build luajit... formats.

Or you could drop building luaJIT completely. fmtutil already ignores
errors from missing luajit* engines, so that would be an easy way.
And if Debian requires halfway decent machines, the it can be
reactived.

Also, this changes should go well with release managers, I assume.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1031949: tex-common: fmtutil fails to copy logs, installation fails

[Norbert Preining]

> that my user had set. But it still seems like a bug that postinst fails
> if the system doesn't have a certain locale. Or maybe I'm viewing this
> incorrectly?

Yes, you do ;-)

Certain programs, in this case luatex, require correct locale setup to
work. It would be nice if we could detect these problems beforehand and
warn the user with a clear message, but also this is non-trivial.

If the locale are incorrectly setup, there is not much to do but fail.

Think about: You could configure to set your shell to
/bin/IamNotThereBash
and it would of course create a lot of problems. Maintainer scripts
cannot work around all possible misconfiguration of a system.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1030622: tex-common package post-installation script subprocess returned error exit status 1

[Norbert Preining]

On Sun, 05 Feb 2023, Hilmar Preuße wrote:
> (/usr/share/texlive/texmf-dist/tex/platex/base/plcore.ltx
> ! Argument of \platexNILa has an extra }.
> 
> \par
> l.52 ...ter\expandafter\expandafter{\platexBANNER}

There was one change concerning platex since the release of the new
latex, I guess that is needed

commit 9016960eb053b949ab2b9c73c31fd8d598fd5f13
Author: Karl Berry 
Date:   Thu Dec 15 20:43:14 2022 +

platex (15dec22)

git-svn-id: svn://tug.org/texlive/trunk@65278 
c570f23f-e606-0410-a88d-b1316a301751

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1023586: texlive-extra-utils: pythontex won't find python (when on python3)

[Norbert Preining]

Hi

something is **rather** strange on your system ...


On Mon, 07 Nov 2022, Olivier Berger wrote:
> FileNotFoundError: [Errno 2] No such file or directory: 'cmd /C "@echo off & 
> call python pythontex-files-amc-compiled/py_default_default.py & if 
> errorlevel 1 exit 1"'

That is Windows CMD code and nothing even remotely related to Linux.

> This can be addressed by explicitely invoking with: 
> pythontex --interpreter python:python3

Maybe also installing
python-is-python3
or how the package name was.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1021515: tex-common: user locale settings can cause postinst to fail

[Norbert Preining]

>if LANG=C LC_ALL=C $FMTUTIL "$@" > $tempfile 2>&1 ; then 

That is indeed better, thanks. Committed.

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1021500: rssguard: Crashes randomly after refreshing feeds

[Norbert Preining]

Hi Juan

rssguard is practically orphaned in Debian due to me having been thrown
out.

I recommend using my builds from OSC:
https://build.opensuse.org/project/show/home:npreining:debian-various

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1021515: tex-common: user locale settings can cause postinst to fail

[Norbert Preining]

Hi Stuart,

thanks for testing ... indeed LC_ALL .. so something like this?
@@ -76,11 +76,14 @@ dhit_build_format ()
 tempfile=$(mktemp -p /tmp fmtutil.)
 # save LANG
 LANGSAVE=$LANG
+LCALLSAVE=$LCALLSAVE
 LANG=C
+LC_ALL=C
 printf "Building format(s) $*.\n\tThis may take some time... "
 if $FMTUTIL "$@" > $tempfile 2>&1 ; then
 rm -f $tempfile
 LANG=$LANGSAVE
+LC_ALL=$LCALLSAVE
 echo "done."
 else
 exec >&2

should do the trick I guess.

Will put it into git, and Hilmar will probably upload it at some point.

Regards

Norbert

On Mon, 10 Oct 2022, Stuart Prescott wrote:
> Setting LC_ALL=C seems to be an adequate workaround as that overrides all 
> LC_* 
> environment variables in one step.

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1021515: tex-common: user locale settings can cause postinst to fail

[Norbert Preining]

Hi Stuart,

> The postinst for tex-common is sensitive to the locale settings from the

Hmm, interesting ...

> $ luahbtex -ini   -jobname=luahbtex -progname=luahbtex luatex.ini  Unable to read environment locale: exit now.

We do set LANG=C already before running fmtutil, so I am surprised that
there is still something bad happening.


> Feeding in some environment variables to see if I could convince it to

What happens if you only feed LANG=C? Does it break?

Looking at the code, maybe we forgot to export LANG since it might not
be defined by now. As of now the code runs:

LANGSAVE=$LANG
LANG=C
printf "Building format(s) $*.\n\tThis may take some time... "
if $FMTUTIL "$@" > $tempfile 2>&1 ; then

LANG normally is already marked as export, but maybe in your particular
case it was unset, and thus not marked as to be exported.

Can you also do an experiment by adding
export LANG
to /var/lib/dpkg/info/tex-common.postinst (AFAIR, not on Debian) after
setting it to LANG=C, and see if that helps.

> $ LANG=C LANGUAGE=C LC_CTYPE=C LC_NUMERIC=C LC_TIME=C LC_COLLATE=C 
> LC_MONETARY=C LC_MESSAGES=C LC_PAPER=C LC_NAME=C LC_ADDRESS=C luahbtex -ini   
> -jobname=luahbtex -progname=luahbtex luatex.ini  bash: warning: setlocale: LC_COLLATE: cannot change locale (en_AU.UTF-8)

That is indeed strange and I cannot reproduce it.

> Installing the 'locales' package and correctly configuring it to the
> locales that were in the environment was also enough.

It should not be necessary, and in fact will create problems later on.

> particular locale required. Adding some locale overrides to the postinst
> would be better, but it might mean that users do not get error messages
> displayed to them in their preferred language.

The locale variables are set for the fmtutil run only, and none of the
programs involved is localized, so there is no change.

I am just wondering what other locale vars are necessary, back then
we thought (and it worked bakc then) that LANG is enough.

Regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1021347: fonts-texgyre: please demote fonts-texgyre-math to Recommends

[Norbert Preining]

Hi

> So, texlive-fonts-recommended recommends tex-gyre and texlive-full pulls it
> in. tex-gyre in turn contains the full set of Type1 fonts, just recommends
> the OpenType fonts (fonts-texgyre & fonts-texgyre-math). So I don't see any
> need for action here.

Ok, that looks ok.

On Thu, 06 Oct 2022, fab...@greffrath.com wrote:
> the fonts-texgyre-* packages contain only the OpenType variants of the

Which are used by luatex ... so "only" is a bit incorrect.

> LaTeX world will be completely unaffected by this.

Disagree.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1021347: fonts-texgyre: please demote fonts-texgyre-math to Recommends

[Norbert Preining]

Hi Hilmar,

> @Norbert: do you still remember why you wrote:

Not really ... I am probably most nervous about other dependencies
within TeX Live onto TeX Gyre fonts which then expects to have
the math fonts installed.

So dropping the depends to recommends or suggests is in principle fine,
but then we need to check which of the texlive-* packages depend on
texgyre and might need an additional dependency.

Hope that helps

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1017969: texlive-latex-recommended: As configured by texlive-latex-recommended, fontspec using XeLaTeX cannot find system fonts by name.

[Norbert Preining]

> % \setmainfont{TexGyreTermes}
> % \setmathfont{Tex Gyre Termes Math}

If you use the correct
\setmainfont{TeX Gyre Termes}
\setmathfont{TeX Gyre Termes Math}
(note the uppercase X in TeX, the spaces, etc) then it works.

You can check - as documented in the fontspec manual - with
otfinfo -i 
and pick the "Preferred Family", in the Math case
Preferred family:TeX Gyre Termes Math

OSFONTDIR is set to /usr/share/fonts and searched recursively, so the
fonts should be found.

Furthermore, the TeX Gyre fonts should be linked into
/usr/share/texmf/fonts, and also be found via that line.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1013942: maildir-utils: please package new upstream version 1.8

[Norbert Preining]

Hi

> Note, that the Debian Emacs team would adopt and update the package, if
> you don't like to be bothered with it anymore.

Feel free to do whatever you want with it.

BR

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#988630: NMU: onedrive: Please update to the latest version

[Norbert Preining]

Hi Bastian,

thanks, feel free to adopt it / salvage it / whatever you feel like
doing with it.

regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#988630: onedrive: Please update to the latest version

[Norbert Preining]

> Raising severity because of the unusable state.

I would recommend this:
https://github.com/abraunegg/onedrive/blob/master/docs/ubuntu-package-install.md#distribution-package-install-instructions

Up to date packages for Debian stable/testing/unstable, Ubuntu.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1009196: [Dev-luatex] Bug#1009196: texlive-binaries: Reproducible content of .fmt files

[Norbert Preining]

> not only fmt, every output  could suffer from the same problem if it

If the final output (pdf) has traces of that, it might be of concern.
But for now the discussion is about the fmt dump, which is independent
of these items.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1009196: [Dev-luatex] Bug#1009196: texlive-binaries: Reproducible content of .fmt files

[Norbert Preining]

Hi Hans, hi Roland,

thanks for your answer.

> it actually defeats one of the security properties of lua (which was
> explicitly introduced at some point: make sure that hashes have random order
> each run so that it's harder to retrieve sensitive data from mem)

Well, that is a good point to *not* implement the change.

Roland, do you have any comments? I guess the reproducability strive is
not as important as security.

So if something in this way should be done, it would need to
changes sort order if and only if FORCE_SOURCE_DATE=1 in the env
(this is what has required for tex engines to obey SOURCE_DATE_EPOCH
settings).

Roland, if you have time, please adjust the patch to work within the
above constraints.

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1009196: texlive-binaries: Reproducible content of .fmt files

[Norbert Preining]

Hi Luigi, hi all luatex devs,

here at Debian we got a bug report about reproducability of luatex
format dumps. It contains a patch to make the hyphenation exception list
sorted. (I attach the patch)

Could you please take a look whether this is still relevant for the
latest release of luatex.

Thanks

Norbert

On Fri, 08 Apr 2022, Roland Clobus wrote:
> Hello maintainers of texlive-binaries,
> 
> While working on the “reproducible builds” effort [1], I have noticed that the
> live image for Cinnamon in bookworm is no longer reproducible [2].
> 
> The attached patch ensures that the output of the function 'exception_strings'
> always uses the same order of the hyphenation exceptions.
> I've written the solution in C, perhaps someone more versed in lua could
> rewrite it more elegantly.
> (The lua manual says for the 'next' function: 'The order in which the indices
> are enumerated is not specified' [3])
> 
> With the attached patch applied, I'm able (with the help of 
> FORCE_SOURCE_DATE=1
> and SOURCE_DATE_EPOCH) to reproducibly rebuild the .fmt files, as created by
> 'fmtutil --sys --all'.
> 
> Small test case to reproduce:
> export FORCE_SOURCE_DATE=1
> export SOURCE_DATE_EPOCH=$(date +%s)
> for i in `seq 1 10`; do luahbtex -ini -jobname=luahbtex -progname=luabhtex
> luatex.ini > /dev/null; md5sum luahbtex.*; done
> 
> With kind regards,
> Roland Clobus
> 
>  [1]: https://wiki.debian.org/ReproducibleBuilds
>  [2]:
> https://jenkins.debian.net/view/live/job/reproducible_debian_live_build_cinnamon_bookworm/
>  [3]: http://www.lua.org/manual/5.4/manual.html#pdf-next
> 

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
diff --git a/texk/web2c/luatexdir/lang/texlang.c 
b/texk/web2c/luatexdir/lang/texlang.c
index ba7614ff..ccc0ec90 100644
--- a/texk/web2c/luatexdir/lang/texlang.c
+++ b/texk/web2c/luatexdir/lang/texlang.c
@@ -498,10 +498,20 @@ static char *hyphenation_exception(int exceptions, char 
*w)
 return ret;
 }
 
+char *unsorted_buffer = NULL;
+size_t *indexes = NULL;
+
+static int sort_func(const void *a, const void *b) {
+size_t ia = *(size_t*)a;
+size_t ib = *(size_t*)b;
+return strcmp(&unsorted_buffer[ia], &unsorted_buffer[ib]);
+}
+
 char *exception_strings(struct tex_language *lang)
 {
 const char *value;
 size_t size = 0, current = 0;
+size_t num_bytes = 0;
 size_t l = 0;
 char *ret = NULL;
 if (lang->exceptions == 0)
@@ -509,19 +519,42 @@ char *exception_strings(struct tex_language *lang)
 lua_checkstack(Luas, 2);
 lua_rawgeti(Luas, LUA_REGISTRYINDEX, lang->exceptions);
 if (lua_istable(Luas, -1)) {
-/*tex Iterate and join. */
+/*tex Determine required memory. */
 lua_pushnil(Luas);
 while (lua_next(Luas, -2) != 0) {
 value = lua_tolstring(Luas, -1, &l);
-if (current + 2 + l > size) {
-ret = xrealloc(ret, (unsigned) ((size + size / 5) + current + 
l + 1024));
-size = (size + size / 5) + current + l + 1024;
-}
-*(ret + current) = ' ';
-strcpy(ret + current + 1, value);
+num_bytes += l + 1;
+size++;
+lua_pop(Luas, 1);
+}
+unsorted_buffer = xmalloc(num_bytes);
+indexes = xmalloc(sizeof(size_t)*size);
+
+/*tex Fetch values. */
+current = 0;
+size = 0;
+lua_pushnil(Luas);
+while (lua_next(Luas, -2) != 0) {
+value = lua_tolstring(Luas, -1, &l);
+strcpy(unsorted_buffer + current, value);
+indexes[size++] = current;
 current += l + 1;
 lua_pop(Luas, 1);
 }
+/*tex Sort and join. */
+qsort(indexes, size, sizeof(size_t), sort_func);
+ret = xmalloc(num_bytes);
+current = 0;
+for (l = 0; l < size; l++) {
+   strcpy(ret + current, &unsorted_buffer[indexes[l]]);
+   current += strlen(&unsorted_buffer[indexes[l]]);
+   ret[current] = ' ';
+   current += 1;
+}
+ret[current - 1] = '\0';
+
+free(unsorted_buffer);
+free(indexes);
 }
 return ret;
 }

Bug#1008764: dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules directories, breaks

[Norbert Preining]

Hi Guillem,

> The script does not break the whole system, it fails quite early
> during preparations before doing any migration.

But the system remains in a broken state, induced by the original
decision of the installer/dpkg. Thus, as long as it cannot be fixed it
is a critical bug. But anyway.

> Sorry, it looks like I previously only fixed the cases of mixed tracked
> and untracked kernel module files there. I've now fixed this locally,
> which will be included in 1.21.7.

Thanks, that is much appreciated.

> You'll need to remove the shadow hierarchy before being able to run
> this again with a fixed script though.

Yes, I have done that already a few times retrying the call.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1008764: dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules directories, breaks

[Norbert Preining]

Package: dpkg
Version: 1.21.6
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: norb...@preining.info

Hi

my system was installed *after* buster and now is in the unfortunate
messed up state.

I tried to fix it as suggested by dpkg using dpkg-fsys-usrunmess, but
it fails reproducibly:
$ dpkg-fsys-usrunmess
...
D: creating shadow file = /.usrunmess/lib/modprobe.d/aliases.conf
D: creating shadow file = /.usrunmess/lib/modprobe.d/fbdev-blacklist.conf
D: creating shadow file = /.usrunmess/lib/modprobe.d/systemd.conf
D: creating shadow dir = /.usrunmess/lib/modules/5.15.15+futex+zstd+intel+wine+
error: cannot mkdir /.usrunmess/lib/modules/5.15.15+futex+zstd+intel+wine+: No 
such file or directory
$

I have my own compiled kernels.

The problem is that it seems to be a missing mkdir -p  or similar.

Wth that, I cannot convert the system.

Best

Norbert



-- Package-specific info:
This system uses merged-usr-via-aliased-dirs, going behind dpkg's
back, breaking its core assumptions. This can cause silent file
overwrites and disappearances, and its general tools misbehavior.
See .

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.17+futex+wine+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-5
ii  libc62.33-7
ii  liblzma5 5.2.5-2
ii  libselinux1  3.3-1+b2
ii  tar  1.34+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.4.3
pn  debsig-verify  

-- no debconf information

Bug#1007241: dash: reconfiguring dash does NOT reset /bin/sh to bash

[Norbert Preining]

Package: dash
Version: 0.5.11+git20210903+057cd650a4ed-7
Severity: important
X-Debbugs-Cc: norb...@preining.info

Hi

According to all documentation I could find, doing
dpkg-reconfigure dash
and selecting "No" should reset /bin/sh to be bash again.

This is not true. I have now tried it several times switching between
"Yes" and "No", and in no case, after selecting "No" was the /bin/sh
symlink reverted to bash, but always stayed at dash.

Regards

Norbert

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.13+futex+wine+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dash depends on:
ii  debconf [debconf-2.0]  1.5.79
ii  debianutils5.7-0.1
ii  dpkg   1.21.2
ii  libc6  2.33-7

dash recommends no packages.

dash suggests no packages.

-- debconf information:
* dash/sh: false

Bug#1007060: lmodern: please consider upgrading to 3.0 source format

[Norbert Preining]

tag 1007060 + wontfix
severity 1007060 wishlist
thanks

Hi

> bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
> advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)

The advantages do not really apply in this case. The packaging has been
stable since many years, despite a tried switch to 3.0 which was
reverted:

lmodern (2.004.5-5) unstable; urgency=medium

  * go back to source format 1.0, dpkg/quilt creates irrelevant
directories in case no patches are available, breaking builds
(Closes: #906762)

I would close this bug, but for now wishlist and add tag wontfix.


Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research +IFMGA Guide +TU Wien+TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1006685: kde-plasma-desktop: KDE does not display Emojis correctly

[Norbert Preining]

Hallo Max,

> I copied two files from Kubuntu's /etc/fonts/conf.avail/, 50-user.conf and
> 56-kubuntu-noto.conf and put them to Debian's /etc/fonts/conf.avail and
> ~/.config/fontconfig/conf.d/, respectively.
> 
> Then I refreshed the fonts cache using `sudo fc-cache -fv`, just as you
> suggested. For everyone landing here: **It was crucial to relogin!**

So yes, re-logging in is probably necessary indeed.

I checked the two files, the 50-user.conf should not be necessary since
this is already present in Debian, too ... if it is missing on your
side, this is surprising.

Concerning 50-kubuntu-noto.conf, this does *a hell of a lot of things*
... if you are happy with the output, then all is fine. The part that it
does right is adding the Noto emoji font to the search list at the
front. (I personally found some interesting things concerning hinting
for CJK fonts, which - as I live in Japan - is of great interest!)

> Now I have working emoji support wherever I expect it. Thank you very much!

Well, if it works and all is fine with you, that is perfect!

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research +IFMGA Guide +TU Wien+TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1006685: kde-plasma-desktop: KDE does not display Emojis correctly

[Norbert Preining]

Hi Max,

> I really tried, but I could not find a guide how to do so. I found
> https://wiki.archlinux.org/title/Font_configuration but it seems not to have a
> section to configure fallback fonts.

I used a different config file, but just found this here which indicates
that it is related to hinting:

https://bugs.freedesktop.org/show_bug.cgi?id=104542

$ cat /etc/fonts/conf.d/68-color-emoji.conf






Emoji


true


hintslight


true




$

Does that work (after sudo fc-cache -f  and relogin)?

If not, then




 
   sans-serif
   
 Noto Sans
 Noto Color Emoji
 Noto Emoji
 DejaVu Sans
   
 
 
   serif
   
 Noto Serif
 Noto Color Emoji
 Noto Emoji
 DejaVu Serif
   
 
 
  monospace
  
Noto Mono
Noto Color Emoji
Noto Emoji
DejaVu Sans Mono
   
 


Would help, too.

> So maybe this is not related to KDE directly, but I still think its an
> unfortunate situation, and fixing at would significantly improve the user
> experience? Would it make sense to file another bug report against the
> appropriate package, e.g. fontconfig?

My guess is that the fonts-noto-emoji or so should ship a fontconfig
file that activates it, best with the above.

But I am not running Debian anymore on my main machine, so cannot really
check.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research +IFMGA Guide +TU Wien+TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1006685: kde-plasma-desktop: KDE does not display Emojis correctly

[Norbert Preining]

Hi Max,

> One can reproduce it by running `echo "Heart Face Emoji 🥰"` in Konsole
> or by opening https://www.youtube.com/watch?v=YaYoJziCgto in Fireofox or
> Konqueror. The emojis will be displayed only as blank rectangles.
> 
> The problem does not occur on Ubuntu. It also does not occur when using
> Debian/Xfce and when using the Xfce-Terminal from within a Plasma

Qt has not auto-fallback, so this has to be activated for fontconfig.
I just tried it myself on Arch (I am running) and didn't see the emojis.
Then I did:
- install fonts-noto-emoji
- added configuration to /etc/fonts/local.conf (easily findable on the
  internet what is necessary)
And now emojis are properly shown in konsole, as well as other Qt based
programs.

> I tried to set a different font, but to no avail. Maybe I have not tried
> hard enough. However, I think Emojis should be displayed properly in the
> default configuration.

The problem is that:
- the default font you set is for text, and emojis are most likely not
  contained in the font you set
- the libraries in use need to deal with missing glyphs in the defined
  font, and there are several ways to do it. One is to display TOFU

This is not specific to KDE, but to fontconfig and how Debian handles
fallback fonts.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research +IFMGA Guide +TU Wien+TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1003634: texlive-latex-base: \fontseries broken: seems to be cumulative until {m} or so?

[Norbert Preining]

Hi

I don't do ping-pong of bugs here, but this is not the least related to
Debian at all, and should be brought to the respective channels (TL
mailing list, LaTeX team tracker, IRC, ...).

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research +IFMGA Guide +TU Wien+TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1001194: libnitrokey-common: nitrokey 3A not recognized - at least missing udev entries

[Norbert Preining]

Hi Szczepan

thanks again for the explanations!

> We are still working on the smart card support, which is planned next year.

Ah, now I remember reading something about smart card firmware is in the
works, that explains it. Sorry for the noise.

> will inform users about the current update procedure on the each firmware
> release.

Ok, so for now I can assume no firmware update is necessary.

> Indeed. While the hardware is final, we still work on adding features to the
> Nitrokey 3 in the coming months, specifically smart card and Password Safe
> support.

Might I ask - *how* can I use the key *now*?
Which functionality is there available at the moment, and which
application can I use?

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1001194: libnitrokey-common: nitrokey 3A not recognized - at least missing udev entries

[Norbert Preining]

Hi Szczepan

thanks for your prompt answer, much appreciated!

> Thank you for the report! New libnitrokey 3.7 with the updated udev rules
> was not yet released. We will keep in mind to do so asap.

Thanks.

> Nitrokey 3 is not supported by libnitrokey at the moment. We are currently
> working on adding more features to the former, coming from the other models.

Hmm, but also gpg does not tell me anything when I do
gpg --card-status
(hangs there for ages).

Also, the web updater didn't really work.

Is this all based on the fact that the device is so brand new?

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1001194: libnitrokey-common: nitrokey 3A not recognized - at least missing udev entries

[Norbert Preining]

Package: libnitrokey-common
Version: 3.6-0.1
Severity: important
X-Debbugs-Cc: norb...@preining.info

The current set of udev-rules does not include support for
the device 20a0:42b2 Nitrokey 3A. It seems that some lines are missing.

Furthermore, even after adding
# Nitrokey 3 NFC
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="20a0", 
ATTRS{idProduct}=="42b2", TAG+="uaccess"
from 
https://raw.githubusercontent.com/Nitrokey/libnitrokey/master/data/41-nitrokey.rules
and rebooting, the nitrokey is still not recognized.

Best

Norbert


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.6+futex+wine+zstd+intel+ (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

libnitrokey-common depends on no packages.

Versions of packages libnitrokey-common recommends:
ii  libnitrokey3  3.6-0.1

libnitrokey-common suggests no packages.

-- no debconf information

Bug#974779: Update of julia to 1.6.x

[Norbert Preining]

Hi Stéphane,

> Then, julia should be removed (from testing at least).

Agreed.

> And cantor is key because kdeedu depends on it. I see you're an uploader
> of cantor, could you remove its julia backend, please?

Unfortunately I cannot upload anything anymore, the uploader status is
incorrect.

Sorry

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#974779: Update of julia to 1.6.x

[Norbert Preining]

Hi

As far as I know, nobody is working on it, and thanks to recent events in 
debian, me neither.

That means Debian will be stuck with the current status.

I recommend installing and using the upstream provided binaries.

Best

Norbert
-- 
PREINING Norbert  https://www.preining.info
Fujitsu   + IFMGA ProGuide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Nov 30, 2021 11:12:01 Stéphane Glondu :

> On Tue, 12 Jan 2021 15:03:30 +0900 Norbert Preining
>  wrote:
>> Ok, taht is fine - I am currently working on 1.6.0-beta1 and hope that
>> it builds fine with llvm11. That would be after release, though.
> 
> What is the progress on updating Julia?
> 
> Current upstream version reported by uscan is 1.6.4.
> 
> 
> Cheers,
> 

Bug#992214: RFS: nemo-compare/5.0.1-1 [ITP] -- Context menu comparison extension for Nemo file manager

[Norbert Preining]

Hi Joshua,

please send me the details (git repo) and I will look into it.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#999451: kwin-x11: drawing windows is delayed making reading and typing tedious

[Norbert Preining]

Hi Paul,

Can you check whether
  Start compositor on startup
is selected in the Plasma settings?

Thanks

Norbert
-- 
PREINING Norbert  https://www.preining.info
Fujitsu   + IFMGA ProGuide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Nov 11, 2021 17:39:23 Paul Gevers :

> Package: kwin-x11
> Version: 4:5.23.2-1
> Severity: important
> 
> Dear maintainers,
> 
> First off, thanks for maintaining KDE in Debian, I enjoy using it.
> 
> Since a recent upgrade (after the issues we had with only half (or
> less) of the stack migrating to testing) I'm experiencing issues with
> drawing of windows. The issue is that it seems that windows
> (e.g. konsole) are only drawn after some delay or after switching back
> and forth to another window. Especially the cursor position is often
> at a different place that it shows, making typing mistakes very
> difficult to correct. Also e.g. scrolling through messages in
> Thunderbird is difficult, as the window is only properly refreshed
> after I stop scrolling, until then the window is messed up. I tried to
> make a screen shot of the situation, but it seems that also the
> screenshot tool (Spectacle) ensures that the window is properly
> refresh the moment it takes the screenshot. The issue is less of a
> problem in Emacs, as that seems to force the refresh by itself much
> more often (although I do see glitches with the cursor jumping).
> 
> I'm aware that the issue may not be with kwin, but it's the package I
> thought of first, please reassign if you think the issue is more
> likely to be elsewhere. Also please let me know if I can provide you
> with more information to help solve the issue.
> 
> My system is an up-to-date testing environment. I delayed reporting
> this issue in the hope that it was caused by other to-be-migrated
> packages from unstable, but the issue is annoying me now for more than
> a week (I estimate) and I have no clue which package from unstable I
> should be looking out for.
> 
> Paul
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages kwin-x11 depends on:
> ii  kwin-common   4:5.23.2-1
> ii  libc6 2.32-4
> ii  libepoxy0 1.5.9-2
> ii  libgcc-s1 11.2.0-10
> ii  libkf5configcore5 5.86.0-1
> ii  libkf5coreaddons5 5.86.0-1
> ii  libkf5crash5  5.86.0-1
> ii  libkf5i18n5   5.86.0-1
> ii  libkf5quickaddons5    5.86.0-1
> ii  libkf5windowsystem5   5.86.0-1
> ii  libkwaylandserver5 [libkwaylandserver5-5.23]  5.23.2-1
> ii  libkwineffects13  4:5.23.2-1
> ii  libkwinglutils13  4:5.23.2-1
> ii  libkwinxrenderutils13 4:5.23.2-1
> ii  libqt5core5a  5.15.2+dfsg-12
> ii  libqt5dbus5   5.15.2+dfsg-12
> ii  libqt5gui5    5.15.2+dfsg-12
> ii  libqt5widgets5    5.15.2+dfsg-12
> ii  libqt5x11extras5  5.15.2-2
> ii  libstdc++6    11.2.0-10
> ii  libx11-6  2:1.7.2-2+b1
> ii  libxcb-composite0 1.14-3
> ii  libxcb-keysyms1   0.4.0-1+b2
> ii  libxcb-randr0 1.14-3
> ii  libxcb-render0    1.14-3
> ii  libxcb-shape0 1.14-3
> ii  libxcb-xfixes0    1.14-3
> ii  libxcb1   1.14-3
> ii  libxi6    2:1.8-1
> 
> kwin-x11 recommends no packages.
> 
> kwin-x11 suggests no packages.
> 
> -- no debconf information

Bug#999423: powerdevil does not detect if on ac or battery

[Norbert Preining]

Hi Michael,

> Powerdevil doesn't detect If i'm on AC or not. It always shows that the
> powercord is plugged in. Doesn't matter if I unplug it or not.

Strange. It works for me.
Did you do a kernel upgrade in recent months?

There is a bug report that describes something similar:
https://bugzilla.kernel.org/show_bug.cgi?id=210425
https://gitlab.freedesktop.org/upower/upower/-/issues/126

> tlp does detect it correctly and at least sets everything else correctly.

That would point into the direction of the gitlab issue that some
signals are not sent.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#999339: plasma-workspace: Maximized windows do not move to primary display when connected

[Norbert Preining]

Hi Shai,

> Since 5.23, I've noted that this doesn't quite work. With the
> current version I've noticed further that it's the maximized
> windows, specifically, which stay on the laptop screen (which,
> when an external is connected, is the secondary display); 
> normal-sized windows behave as expected.

Can you please test 5.23.3 which I have uploaded just today. It has
several fixes included concerning exactly this problem, as far as I read
it.

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#991904: ITS: isync

[Norbert Preining]

Hi all,

since there hasn't been any response for n >= 21 days, I have uploaded
a new isync package 1.4.3-1 to DELAYED/7 queue.

The diff of the debian dirs between the last released version and the
one I uploaded is attached.

Thanks

Norbert

On Thu, 05 Aug 2021, Norbert Preining wrote:
> Package: isync
> Version: 1.3.0-2.2
> Severity: important
> X-Debbugs-Cc: Alessandro Ghedini , Nicolas Boullis 
> , Theodore Y. Ts'o , m...@qa.debian.org
> 
> Dear Nicolas, dear all,
> 
> I intend to salvage this package:
> - several new upstreams
> - no activity besides security NMUs for years
> 
> This bug reports starts the official salvage request according to
> https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
> 
> Nicolas, could you please answer here (best signed) that you either will
> ake further care of the package, or agree to the salvaging.
> 
> Thanks
> 
> Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
diff -urN isync-1.3.0/debian/changelog isync-1.4.3/debian/changelog
--- isync-1.3.0/debian/changelog	2021-06-08 04:03:56.0 +0900
+++ isync-1.4.3/debian/changelog	2021-11-09 08:45:36.0 +0900
@@ -1,3 +1,15 @@
+isync (1.4.3-1) unstable; urgency=medium
+
+  * New upstream version 1.4.3
+  * Drop patches, included upstream.
+  * Update list of installed files.
+  * Drop references to isync.
+  * Take over maintainership (Closes: #991904).
+  * Bump standards level to 4.6.0, no changes necessary.
+  * Use debhelper-compat (= 12) instead of d/compat.
+
+ -- Norbert Preining   Tue, 09 Nov 2021 08:45:36 +0900
+
 isync (1.3.0-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -urN isync-1.3.0/debian/compat isync-1.4.3/debian/compat
--- isync-1.3.0/debian/compat	2021-06-08 04:03:56.0 +0900
+++ isync-1.4.3/debian/compat	1970-01-01 09:00:00.0 +0900
@@ -1 +0,0 @@
-11
diff -urN isync-1.3.0/debian/control isync-1.4.3/debian/control
--- isync-1.3.0/debian/control	2021-06-08 04:03:56.0 +0900
+++ isync-1.4.3/debian/control	2021-11-09 08:45:36.0 +0900
@@ -1,10 +1,9 @@
 Source: isync
 Section: mail
 Priority: optional
-Maintainer: Nicolas Boullis 
-Uploaders: Theodore Y. Ts'o 
-Standards-Version: 4.2.1
-Build-Depends: debhelper (>= 11),
+Maintainer: Norbert Preining 
+Standards-Version: 4.6.0
+Build-Depends: debhelper-compat (= 12),
  libdb-dev,
  libsasl2-dev,
  libssl-dev,
@@ -24,11 +23,6 @@
  deletions and flag changes can be propagated both ways. isync is suitable
  for use in IMAP-disconnected mode.
  .
- The main application was much improved in version 1.0. Those improvements
- lead to interface changes and the application being renamed to mbsync. The
- application isync is now only a wrapper to keep compatibility with earlier
- versions.
- .
  Features:
   * Fine-grained selection of synchronization operations to perform
   * Synchronizes single mailboxes or entire mailbox collections
diff -urN isync-1.3.0/debian/isync.examples isync-1.4.3/debian/isync.examples
--- isync-1.3.0/debian/isync.examples	2021-06-08 04:03:56.0 +0900
+++ isync-1.4.3/debian/isync.examples	2021-11-09 08:45:36.0 +0900
@@ -1,2 +1 @@
 src/mbsyncrc.sample
-src/compat/isyncrc.sample
diff -urN isync-1.3.0/debian/patches/01_sni.patch isync-1.4.3/debian/patches/01_sni.patch
--- isync-1.3.0/debian/patches/01_sni.patch	2021-06-08 04:03:56.0 +0900
+++ isync-1.4.3/debian/patches/01_sni.patch	1970-01-01 09:00:00.0 +0900
@@ -1,38 +0,0 @@
-From 1086cdb8fd77a224d56033bde0825a286ba30ee2 Mon Sep 17 00:00:00 2001
-From: Vincent Bernat 
-Date: Wed, 22 Aug 2018 19:20:35 +0200
-Subject: [PATCH] use SNI when connecting with SSL
-
-imap.gmail.com doesn't accept connections without SNI anymore. Without
-this extension, it returns a self-signed certificate and mbsync is
-unable to complete:
-
-$ openssl s_client -connect imap.gmail.com:993 -noservername
-CONNECTED(0005)
-depth=0 OU = "No SNI provided; please fix your client.", CN = invalid2.invalid
-verify error:num=18:self signed certificate
-verify return:1
-depth=0 OU = "No SNI provided; please fix your client.", CN = invalid2.invalid
-verify return:1
----
-Certificate chain
- 0 s:OU = "No SNI provided; please fix your client.", CN = invalid2.invalid
-   i:OU = "No SNI provided; please fix your client.", CN = invalid2.invalid
-
-This commit configure the SSL connection to transmit the hostname
-through SNI. This has been tested with both GMail (which requires SNI)
-and Fastmail (which doesn't require SNI).

- src/socket.c | 1 +
- 1 file changed, 1 insertion(+)
-
 a/src/socket.c
-+++ b/src/socket.c
-@@ -270,

Bug#989529: ITP: neochat -- Client for Matrix chat

[Norbert Preining]

Hi Andres,

> Norbert, I'd planned to remove Spectral from sid once you uploaded Neochat.
> Do you have a timeline for when you plan to do that? Since Spectral was

Hmm, the current released version is - well - not sure how useful. I
tried it without too much success, though.

I was waiting for a new release, but somehow it isn't coming.

> released with bullseye, we should probably provide a transitional package
> that pulls in Neochat for bookworm. Once you upload Neochat I can do that as
> part of the Spectral source package, or I can remove the Spectral source
> package in advance of your upload and have you provide the spectral
> transitional package as part of Neochat. Which would you prefer?

Hmm, I guess it is better to have a spectral trans package built from
neochat than from the spectral sources.

Could you send a MR that adds the transitional package to 
salsa.debian.org:qt-kde-team/extras/neochat.git
? That would be very helpful.

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#996726: Some other questions

[Norbert Preining]

Hi Bob, hi Jérôme,

On Fri, 05 Nov 2021, Jérôme Pouiller wrote:
> Is there a way to avoid this problem happen in the future?

Yes of course:
* take a VM
* for each package in the set of Plasma, that is about 150 or so, do
  - upgrade the package and all necessary dependencies
  - reboot the vm
  - test whether Plasma works properly
Unfortunately, none of us has the time to do this.

On Fri, 05 Nov 2021, Bob Wong wrote:
>   Probably the best way is to do the rolling release. Another solution is

Not in Debian. Different discussion.

> to make each package synced downstream at the same time, but it's too hard
> to achieve.

??? Not sure what you want to say here ...

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#996726: Some other questions

[Norbert Preining]

>   After 2 weeks, the bug has finally been fixed. But I wonder why the bug
> wasn't tested out in the unstable branch and was pushed into the testing

Because on unstable everything worked. The bug happens only due to
different transition times from unstable to testing. This cannot be
tested in unstable before.

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#990821: aptly fails to run if both gnupg2 and gnupg1 are installed

[Norbert Preining]

Package: aptly
Version: 1.4.0+ds1-6
Followup-For: Bug #990821

Hi all,

conflicting with gpgv1 is *not* the correct solution.
The correct solution is to fix aptly, not conflicting with other
programs that are reasonably important.

gpg v1 is still necessary for the creation of old style keyrings when
creating distributions of verification keys.

I use both aptly and gpgv1 and this is very painful to see.

I suggest reopening this bug and working on a proper bug fix.

Thanks

Norbert



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.14.16+futex+ntfs3+zstd+intel+ (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages aptly depends on:
ii  bzip2 1.0.8-4
ii  gnupg 2.2.27-2
ii  gpgv  2.2.27-2
ii  libc6 2.32-4
ii  xz-utils  5.2.5-2

aptly recommends no packages.

Versions of packages aptly suggests:
ii  graphviz  2.42.2-5+b1

-- no debconf information

Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma

[Norbert Preining]

severity 998386 normal
retitle 998386 Plasma gets very slow when compositor is disabled on bare metal
thanks

Hi Chris,

> Indeed, turning that switch to on and restarting helps. Great!!!

Bingo.

> I cannot remeber that I ever turned it on or off.

But I guess you had, or some cosmic radiation induced bit switch did it
for you on your hard disk ;-) The default for all installations is being
on.

> However, if I turn it back to off, then the problems come back (immedeiately).
> So at least the latter seems to be a bug, right?

Not really sure. Nowadays running without compositor might not really be
possible. I don't have an opinion on that.

> In my similar kvm virtualized installtion the switch also is/was off,
> but there it seems to make no problems, even after a couple of changes and 
> restartings.

Hmm, that is indeed strange, though.
Anyway, I retitle and adjust severity of the bug for now.

I suggest that *you* create a bug report at upstream (I guess kwin?)
because I cannot reproduce it on my systems (AMD based), and upstream
devs will need detailed informations.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#998447: kstart5: --desktop option does not work anymore

[Norbert Preining]

Confirmed that the --desktop options does not really work.
Can be tested by adding a second virtual desktop and starting whatever
program with
kstart5 --desktop 2 --windowclass foobarbaz konsole
etc.

Needs to go upstream I guess.

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma

[Norbert Preining]

Hi Chris,

On Thu, 04 Nov 2021, Chris Nospam wrote:
> Today all packages of plasma 5.23 migrated to testing, and it works fine in 
> my (libvirt) vm. However, on bare metal mesa makes problems (see my bug 
> report #998386), so in fact there plasma 5.23 stays unusable.

That bug is not reproducible on any of my bare metal systems.

Can you try/check the following:
* In the Plasma Settings app, go to
Display and Monitor > Compositor
  and check whether
Enable compositor on startup
  is selected (on).
  Also the rendering backend etc is an important information.

If the above (after logout/login, or better reboot) does not help:
* Is the behaviour reproducible with a **clean** **new** user?

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#998240: Bug#954916: another breakage due to LaTeX changes?

[Norbert Preining]

Hi Joseph,

last year you helped fixing a strange lgrind.dtx file:

On Wed, 25 Mar 2020, Joseph Wright wrote:
> On 25/03/2020 11:03, Enrico Gregorio wrote:
> > > Where can we find lgrind.dtx?
> > http://mirrors.ctan.org/support/lgrind/lgrind.dtx

> The structure of the .dtx is ... unusual. It's got the \begin{document} in
> the 'input' stage and the \end{document} 'as normal'. The result is "%" ends
> up with the 'wrong' catcode, which is where the issue arises: what should be
> a comment in the .def is not any longer. It can be fixed by making the .dtx
> 'normal', i.e. moving the \begin{document} line, but I'm not sure if that is
> an acceptable fix.

You send a simple patch, and that worked all nicely till TeX Live 2021,
and now the same lgrind.dtx (patched version is attached) fails again.

The error message is comes from this part of the code:

% The meta-symbols and their meanings are:
% \begin{description}
% \item[\$] The end of a line
% \item[\^] The beginning of a line
% \item[$\backslash$d] A delimiter (space, tab, newline, start of line)
% \item[$\backslash$a] Matches any string of symbols (like `.*' in lex)
***

And the error is:
[8]
! Missing } inserted.

}
l.540 % \item[\^]
  The beginning of a line
? X


Any suggestion again? As said, it was working till Dezember 2020 ;-)

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
% \iffalse
%
% This is LGrind.DTX. This was written by:
%
% -  Van Jacobson, Lawrence Berkeley Laboratory (based on
%vgrind by Dave Presotto & William Joy of UC Berkeley),
%the original written for \TeX.
% -  Jerry Leichter of Yale University, modifications for \LaTeX.
% -  George V. Reilly of Brown University, renamed to lgrind
% -  Michael Piefel, Humboldt-University Berlin, for \LaTeXe
%and a thousand little changes
%
% \fi
% \iffalse
%% Based on Van Jacobson's ``tgrindmac'', a macro package for TeX.
%% Modified, 1987 by Jerry Leichter. Put '@' in all internal names.
%% Modified, 1991 by George Reilly. Changed name from tgrind to lgrind.
%% Modified, 1995 by Michael Piefel. Made it work with \LaTeXe.
%%  -1999Hundreds of bells and whistles. No changelog here.
%
%<*dtx>
\ProvidesFile{lgrind.dtx}
  [2002/01/28 v3.67 LGrind environment and supporting stuff]
%
%\NeedsTeXFormat{LaTeX2e}[1996/06/01]
%\ProvidesPackage{lgrind}
%  [2002/01/28 v3.67 LGrind environment and supporting stuff]
%<*driver>
\NeedsTeXFormat{LaTeX2e}[1996/06/01]
\documentclass{ltxdoc}
\CodelineIndex
\RecordChanges
\begin{document}
\DocInput{lgrind.dtx}
\end{document}
%
% \fi
%
% \newcommand{\LG}{\textsf{LGrind}}
% \newcommand{\NFSS}{\textsf{NFSS}}
% \frenchspacing
% 
% \GetFileInfo{lgrind.dtx}
% \title{The \LG{} package\thanks{This file
% has version number \fileversion, last
% revised \filedate.}}
% \author{Various Artists}
% \date{\filedate}
% \maketitle
% 
% \CheckSum{679}
% 
% \begin{abstract}
% The \LG{} package is a pretty printer for source
% code. It evolved from vgrind, supported \TeX{} (tgrind) and
% \LaTeX{} and now finally \LaTeXe, in particular \NFSS.
% \end{abstract}
% 
% \changes{v1.0}{1985/02/10}{Written}
% \changes{v2.0}{1991/09/06}{Upgrade to \LaTeX2.09}
% \changes{v3.0}{1995/09/24}{Upgrade to \LaTeXe}
% 
% \section{Introduction}
% \subsection{What is it?}
% The \LG{} package consists of three files:
% \begin{itemize}
% \item \texttt{lgrind} or \texttt{lgrind.exe} is the executable. It will
% convert an \LaTeX-File with embedded listings or a source code file
% into a lot of macro-calls.
% \item \texttt{lgrind.sty} provides the environments and macros to make
% the produced mess readable.
% \item \texttt{lgrindef} contains the information
% needed to tell keywords from comments, comments from strings \dots
% \end{itemize}
% 
% \subsection{Who is to blame?}
% \LG{} is not the work of a single one. The program is based on
% \textsf{vgrind} by Dave Presotto \& William Joy of UC Berkeley.
% 
% Van Jacobson wrote \textsf{tgrind} for \TeX. Jerry Leichter
% of Yale University modified it for \LaTeX. George V. Reilly of 
% Brown University changed the name to lgrind and added the
% program-text-within-comments and @-within-\LaTeX{} features,
% and finally
% Michael Piefel of the Humboldt-University Berlin converted it to
% work under \LaTeXe, i.\,e. with \NFSS, and improved the documentation.
%
% However, there have been many contributors who supported the development; in
% particular the range of supported languages is mainly due to them.
% Unfortunately I do not know all of them, but my thanks go to everybody.
% A special Thank You to
% Torsten Sch\"utze for his OS/2 

Bug#998148: transition: libavif

[Norbert Preining]

Hi Boyuan


> I plan to start another libavif transition as shown in the following

Great, actually it would be great going straight to 0.9.3-2 with libaom v3
support, so that writing of avif files also works.

Thanks a lot for your work on this.

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#998216: plasma-workspace: xembedsniproxy, Xorg and kwin_x11 use 100% CPU when I run two electron apps

[Norbert Preining]

>    1444 root  20   0  728616  99808  63920 R 100,0   0,6 4:13.91 Xorg

Beeehh, that is bad. And no idea what could be the reason. But it sounds
to me like some 3d/mesa stack problem, not inherently Plasma.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#996814: Missing import and export in Kaddressbook

[Norbert Preining]

Hi all,

> I think, package kdepim-addons needs libkpimaddressbookimportexport-dev as 

Confirmed. Uploading a new package in a minute. Thanks a lot!

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#998304: ITP: qalculate-qt -- Powerful and easy to use desktop calculator - Qt version

[Norbert Preining]

Package: wnpp
Severity: wishlist
Owner: Norbert Preining 
X-Debbugs-Cc: debian-de...@lists.debian.org, team+qalcul...@tracker.debian.org

* Package name: qalculate-qt
  Version : 3.21.0
  Upstream Author : Hanna Knutsson 
* URL : https://github.com/Qalculate/qalculate-qt
* License : GPL-2.0-or-later
  Programming Lang: C++
  Description : Powerful and easy to use desktop calculator - Qt version

Qalculate! is small and simple to use but with much power and versatility
underneath.  Features include customizable functions, units, arbitrary
precision, plotting, and a graphical interface that uses a one-line
fault-tolerant expression entry (although it supports optional traditional
buttons).

This package contains the Qt user interface of qalculate.

Bug#993824: transition: libqalculate

[Norbert Preining]

Hi Sebastian, hi Phil,

> > Any news regarding libqalculate20-data?

Since it has been ages without a response, I took the liberty to upload
the current status to unstable.

I am now preparing also 3.21.0

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#998216: plasma-workspace: xembedsniproxy, Xorg and kwin_x11 use 100% CPU when I run two electron apps

[Norbert Preining]

tags 998216 + unreproducible moreinfo
thanks

Hi Patrick,

> When I run two electron apps in the current plasma-workspace the UI is very 
> laggy

I am running three or more (Element, Ferdi, Signal, Telegram) and don't
see anything similar.

> - the bug was introduced by the 5.23 update of plasma-workspace (or kwin)
> - killing one of the apps resolves the problem at any time
> - it happens only using X.org, not on Wayland
> - the apps are reporting no errors and work in general, only very laggy

Very strange, nothing I see on my computer, though. CPU is eaten by
which process? Maybe IO bound?

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#998212: easytag: overwrites tags containing UTF8 data with random rubbish

[Norbert Preining]

Hi

> What kind of files / tags did you process with easytag? If these files

that were mp3, not sure about what version of tags since they were gone
afterwards. At least they displayed fine in all music players I used.
But yes, I guess it is common here in Japan that id3v1 tags are coded in
UTF8 (or even ShiftJIS).

I still consider overwriting tags when there was an error during
preparation, irrespective of the correctness of the original tags,
a serious problem. easytag should *not* write broken tags.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#998217: RM: ksysguard/4:5.21.5-2

[Norbert Preining]

Hi Paul,

> Hint added.

Thanks, much appreciated.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#998217: RM: ksysguard/4:5.21.5-2

[Norbert Preining]

Hi Paul.

> You are aware of the version skew in the KDE ecosystem in testing. On my

Yes, very much. Very painful due to the long delay via mesa - llvm.
We have tightened the deps so that doesn't happen again, but that
doesn't help current testing.

> own laptop (running testing) I had to actively remove ksysguard for the
> other packages to upgrade from unstable. I'm wondering, can we help our

Yes, that is as it supposed to be and "apt dist-upgrade" would select
this.

As discussed on IRC, there is ongoing discussion to provide Plasma 5.23
compatible version of ksysguard, which was dropped from Plasma in 5.22.
For that reason, I don't want to drop it completely from Debian with a
removal, but keep it in unstable (with an RC bug open so it doesn't
transition to testing until a compatible release is available).

> testing users to get a good update and a working KDE back?

Yes, that is my aim: The only requirement is dropping ksysguard from
testing. Then all the 5.23 can transition to testing, including the fix
for the borken upgrade from testing->unstable.

Does this answer your questions?

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#998217: RM: ksysguard/4:5.21.5-2

[Norbert Preining]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
X-Debbugs-Cc: debian-qt-...@lists.debian.org

ksysguard is not updated to 5.23, but might be in the future.
For now it blocks plasma 5.23 transition to testing.
Please remove ksysguard from testing. In case there is a new
release compatible with Plasma 5.23, it will be again uploaded.

Thanks

Norbert

Bug#998212: easytag: overwrites tags containing UTF8 data with random rubbish

[Norbert Preining]

Package: easytag
Version: 2.4.3-4+b1
Severity: critical
Justification: causes serious data loss

Hi

it seems easytag has not arrived in the 20th century, since today it
deleted all tags of 3 CD releases containing compilations of Japanese
singers on my disk. All information that contained UTF8 code has been
destroyed. Easytag complained about "Cannot recode blabla to latin1"
(not surprising, it is utf8) and happily destroyed the complete tags
saving rubbish information.

I suggest removing this program from Debian since this is a serious data
loss issue.

Thanks

Norbert

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.14.15+futex+ntfs3+zstd+intel+ (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages easytag depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-2
ii  libc62.32-4
ii  libflac8 1.3.3-2
ii  libgcc-s111.2.0-10
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.0-3
ii  libgtk-3-0   3.24.30-3
ii  libid3-3.8.3v5   3.8.3-16.3
ii  libid3tag0   0.15.1b-14
ii  libogg0  1.3.4-0.1
ii  libopus0 1.3.1-0.1
ii  libopusfile0 0.9+20170913-1.1
ii  libspeex11.2~rc1.2-1.1
ii  libstdc++6   11.2.0-10
ii  libtag1v51.12-1
ii  libvorbis0a  1.3.7-1
ii  libvorbisfile3   1.3.7-1
ii  libwavpack1  5.4.0-1

Versions of packages easytag recommends:
ii  gnome-icon-theme  3.12.0-4
pn  gvfs  
ii  yelp  41.1-1

Versions of packages easytag suggests:
pn  easytag-nautilus  

Bug#993900: kde-spectacle: AVIF not working

[Norbert Preining]

clone 993900 -1
reassign -1 libaom-dev
retitle -1 Please upload version 3 from experimental to unstable
block 993900 -1
thanks

On Thu, 28 Oct 2021, Daniel a Simona Novomeská wrote:
> In order solve this problem, is is necessary to add new libaom (version 3
> or 2) and/or rav1e to Debian. libavif doesn't work with very old versions
> of libaom.

Cloning and reassigning it accordingly.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#997873: gwenview: thumbnails not updated; sometimes thumbnails point at deleted image

[Norbert Preining]

forwarded 997873 https://bugs.kde.org/show_bug.cgi?id=61
thanks

I have forwarded it to the KDE bug tracker.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#997873: gwenview: thumbnails not updated; sometimes thumbnails point at deleted image

[Norbert Preining]

Hi Edward,

On Tue, 26 Oct 2021, Edward C. Jones wrote:
> If I replace an image with another image with the same name, the thumnail is
> not updated.  This is a well-known problem.  A work-around is to empty the KDE
> thumbnail directory.
> 
> If I replace an image with another image with the same name, when I click on a
> thumbnail, Gwenview displays the deleted image. It seems that Gwenview is
> maintaining
> a pointer to a deleted file.

I cannot reproduce *any* of the two behaviours when terminating gwenview
inbetween:

cd $(mktemp -d)
cp ~/photo1.jpg test.jpg
gwenview .
# shows the thumbnail of photo1.jpg, and opens test.jpg with the
# content of photo1.jpg
# quit gwenview
cp ~/photo2.jpg test.jpg
gwenview .
# shows the thumbnail of photo2.jpg, and opens test.jpg with the
# content of photo2.jpg


OTOH, when I keep gwenview running I see a different bevhaviour:
- thumbnail is properly updated
- actual photo is not update (still shows photo1.jpg!)

So it seems the thumbnail issue is fixed, but the display of the actual
photo not.

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#995683: latexmk: diff for NMU version 1:4.75-1

[Norbert Preining]

Control: tags 995683 + patch
Control: tags 995683 + pending

Dear maintainer,

I've prepared an NMU for latexmk (versioned as 1:4.75-1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
diff -Nru latexmk-4.75/debian/changelog latexmk-4.75/debian/changelog
--- latexmk-4.75/debian/changelog	2021-09-30 16:42:13.0 +0900
+++ latexmk-4.75/debian/changelog	2021-10-25 11:01:02.0 +0900
@@ -1,3 +1,16 @@
+latexmk (1:4.75-1) unstable; urgency=medium
+
+  [ Hilmar Preusse ]
+  * Fixes for
+I: debian-watch-uses-insecure-uri
+I: older-debian-watch-file-standard
+
+  [ Norbert Preining ]
+  * Change maintainer to the Debian TeX Task Force (Closes: #995683)
+  * Bump standards version to 4.6.0, no changes necessary.
+
+ -- Norbert Preining   Mon, 25 Oct 2021 11:01:02 +0900
+
 latexmk (1:4.75-0.1) unstable; urgency=medium
 
   * NMU
diff -Nru latexmk-4.75/debian/control latexmk-4.75/debian/control
--- latexmk-4.75/debian/control	2021-09-30 16:42:13.0 +0900
+++ latexmk-4.75/debian/control	2021-10-25 11:01:02.0 +0900
@@ -2,8 +2,10 @@
 Section: tex
 Priority: optional
 Build-Depends: debhelper-compat (= 12)
-Maintainer: OHURA Makoto 
-Standards-Version: 4.5.0
+Maintainer: Debian TeX Task Force 
+Uploaders: Hilmar Preusse ,
+   Norbert Preining 
+Standards-Version: 4.6.0
 Homepage: https://personal.psu.edu/jcc8/software/latexmk-jcc/
 Vcs-Git: https://github.com/debian-tex/latexmk.git
 Vcs-Browser: https://github.com/debian-tex/latexmk
diff -Nru latexmk-4.75/debian/watch latexmk-4.75/debian/watch
--- latexmk-4.75/debian/watch	2021-09-30 16:42:13.0 +0900
+++ latexmk-4.75/debian/watch	2021-10-25 11:01:02.0 +0900
@@ -1,8 +1,8 @@
-version=3
+version=4
 
 # In the pattern below the first digit is isolated so to have a dotted
 # version number in the debian packages, the upstream uses this dotted
 # form in the changelog but removes the dot in the file names.
-http://personal.psu.edu/~jcc8/software/latexmk/versions.html \
+https://personal.psu.edu/~jcc8/software/latexmk/versions.html \
   latexmk-([\d])([\d]+[a-z]*).zip \
   debian uupdate

Bug#996726:

[Norbert Preining]

> Hello, I am unable to downgrade the kdecoration, if I try to downgrade
> kdecoration, the apt will remove the whole kde desktop. So the only choice

You need to downgrade all packages of plasma that are from 5.23.

> for me is to upgrade. When will the new version of the kdecoration be

It is not about kdecoration, but about kwin, which is blocked by mesa,
which is blocked by llvm, so my current guess is that it will take about
1-2 weeks, hopefully.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#995445: logidee-tools: creates incorrect TeX code, breaks other packages via autopkgtests

[Norbert Preining]

Hi Raphael,

> Sorry that logidee-tools created issues for you. For the record, I have

Not really issues, therion took longer to get fixed ;-)
And it was quite interesting to find out what was the real problem.

> just requested the removal of that package since I'm no longer using
> it and in fact nobody else is using it either.

Then it is definitely a good idea to let this package go away.

Thanks a lot for letting us know, and all the best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#862727: Concerning libjasper

[Norbert Preining]

Hi

> > Would be nice to include the KDE rationale for picking jasper over

ACtually not KDE, but Qt ... (forgot about it). It is in
src:qtimageformats-opensource-src
where the support is contained, and it only supports jasper.
And all the KDE programs depend on that ...

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#862727: Concerning libjasper

[Norbert Preining]

Hi

> I do not mind having another jpeg 2000 implementation in Debian, but
> keep in mind that those low level imaging libraries have all sort of
> potential CVEs attached to them.

Agreed.

> Would be nice to include the KDE rationale for picking jasper over
> openjpeg, maybe there is a particular feature that is missing, that

Good question ... maybe I bug them about switching to openjpeg ...
but not sure what will be the outcome.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#862727: Concerning libjasper

[Norbert Preining]

Hi all,

sending everyone that discussed on the bug an email.

Since version 2.0.19 (2020-07-11) libjasper is now reasonably active
maintained and CVEs have been dealt with.

For support in some KDE/Plasma packages I have revived/made some
packaging of the current version (2.0.33, from 2021-08-01).

Adam, are you still interested in getting this back into Debian?
Any other comment?

BTW, my source package are built on OBS:
https://build.opensuse.org/package/show/home:npreining:debian-kde:other-deps/jasper

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#996736: ksysguard: Version 5-23 is not availible, but plasma-desktop depends on this (recommended)

[Norbert Preining]

reassign 996736 plasma-desktop
retitle 996736 recommends dropped ksysguard
tag 996736 + pending
thanks

On Sun, 17 Oct 2021, Achim Schaefer wrote:
> ksysguard is recommened by plasma-desktop, but there is no Version 5-23, 
> which would be required by plasma-desktop 5-23.
> Please provide an updated version

THere is none, the recommends is wrong and will be fixed in the next
upload.

The new package to be recommended is
plasma-systemmonitor

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13