Hi,
On Fri, Jun 16, 2023 at 22:01:54 +0200, Oneric wrote:
> Hi!
>
> I’ve been considering taking over this package (if I can
> find a sponsor) now that it can be utilised by libass.
>
> On Sat, 8 Jan 2022 20:42:54 +0100 Nils König wrote:
> > Thus I believe it would b
personal use before, so there might be some things I missed and not caught by
lintian, or just superior alternative approaches I don't know about.
Nonetheless I'm hoping the patches are helpful in getting the package back in
sync with upstream.
Cheers
Nils König
-- System Informa
t should apply
without conflicts.
A minimal sample failing to be processed in unpatched Bullseye,
but working with the patch, can be found further below.
Cheers,
Nils König
minimal input file
##
\begin{filecontents}{\jobname.bib}
@misc{beamer,
url = {https://ctan.
n I requested the backtrace, whose entirety can be found a few lines below.
I hope this helps in locating and fixing the issue (and backporting the fix to
Bullseye). If you need any more information or something tested I'd be happy
to help.
Cheers
Nils König
#0 __GI_raise (sig=s
s worked in
> practice since the very first standalone libass release.
>
> [Full text with a list of all fixes:
> https://github.com/libass/libass/releases/tag/0.15.1 ]
Cheers
Nils König
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (500, 'unst
Sorry it took me so long to come back to this.
And also sorry for the lengthy reply.
On Fri, Jan 15, 2021 at 09:27:30 +, Chris Knadle wrote:
> Is the system with this issue running systemd?
Yes, the affected system does run systemd.
> Which method of creating an SSL cert is being used?
cert
I must correct myself.
As I ofc only remembered after sending the bug report, I did already change
the initscript once before to start as root (so it can read the root-owned ssl
certs once on startup, before dropping privileges)
So in the default config, the --user switches shouldn't be a probl
Package: mumble-server
Version: 1.3.0~git20190125.440b173+dfsg-2
Severity: normal
Hi,
currently /etc/init.d/mumble-server stop doesn't does not stop the murmurd
and "restart" spawns an additional instance of mumble-server, leading to
various problems. I'd assume "force-reload" is similarly affect
mal" setup and also added a patch to check the name of the actual pid 1
process, which should work for an openrc+sysv configuration.
I'm not sure what to do with openrc+s6 (and I never used both in conjunction)
or
if this even matters.
Regards
Nils König
(Below information generated wi
On Sat, Jul 18, 2020 at 18:53:34 +0200, Benno Schulenberg wrote:
>
> Op 13-07-2020 om 01:56 schreef Nils König:
> > Basically, I imagined this just like:
> >
> >> If nano were to handle a BOM properly, it must remove a BOM whenever
> >> a file is read, and
On Sun, Jul 12, 2020 at 20:04:31 +0200, Benno Schulenberg wrote:
> Op 12-07-2020 om 16:26 schreef Nils König:
> > FWIW I would have expected leading BOM/NoBOM to be an option when saving
> > with
> > ^O (like DOS/Mac-Format) and by default keep status quo.
>
> No
Hello Benno,
thanks for your quick reply.
On Sun, Jul 12, 2020 at 13:15:41 +0200, Benno Schulenberg wrote:
> Ideally, a UTF-8 file should not contain a Byte Order Mark. What if
> I concatenate several files together? Then the result might contain
> BOMs embedded in the text.
>
> As far as I kn
Package: nano
Version: 3.2-3
Severity: normal
Dear Maintainer,
when editing a UTF8 file in nano that contains a BOM (efbbbf) and inserting a
character at the beginning, the BOM bytes will move after the inserted
character. This can lead to breakages when such a file is being parsed by a
progra
libc6 2.28-10
doxygen 1.8.13-10
texlive 2018.20190227-2
Either dropping patch 0004-Disable-PDF-documentation or adding
confflags += --disable-doxygen-pdf
confflags += --disable-doxygen-ps
to debian/rules resolved this for me.
Regards
Nils König
---
[…]
Generating file index...
Generating
14 matches
Mail list logo
