Package: texlive-luatex
Version: 2023.20231007-1
Severity: important
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
I recently updated zlib1g:amd64 (1:1.2.13.dfsg-3, 1:1.3.dfsg-2) in unstable.
lualatex immediately stopped working, with the error:
[schwarzgerat](0) $ lualatex
PANIC:
i've uploaded 6.200, and it has entered unstable. this bug can be closed.
Package: fonts-sil-gentiumplus
Version: 6.101-1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
Gentium Plus v6.200 was released 2023-02-01.
I'd really like to be able to use U+2227/U+2228 from this great font, among
other recent changes.
Please package the new version
Package: plocate
Version: 1.1.18-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
* What led up to the situation?
I've been using plocate for many months on all my machines without problems.
Recently, I get a coredump on any search, on all the machines
Source: doctest
Version: 2.4.9~ds-1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
Hello! My package notcurses depends on doctest. doctest 2.4.9 was released with
some issues that led to FTBFS without patchery. Thankfully, 2.4.10 has these
fixed. Hopefully it's possible
the cause of this output is the following line in /etc/pam.d/sshd:
# In Debian 4.0 (etch), locale-related environment variables were moved to
# /etc/default/locale, so read that as well.
sessionrequired pam_env.so user_readenv=1 envfile=/etc/default/locale
i'm guessing from the
Package: wnpp
Severity: wishlist
Owner: nick black
X-Debbugs-Cc: debian-de...@lists.debian.org, dankamong...@gmail.com
* Package name: libcpucycles
Version : 20230105
Upstream Contact: Daniel J. Bernstein
* URL : https://cpucycles.cr.yp.to/download.html
* License
https://github.com/dankamongmen/notcurses/issues/2693
thanks! i'll fix this upstream and report here.
Package: libcpuset1
Version: 1.0-6+b1
Severity: minor
Tags: upstream
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
The cpuset.3 man page references bootcpuset.8 and bootcpuset.conf.5. Neither of
these man pages appear to exist in any package.
-- System Information:
Debian Release:
I
assist you in any way at the moment?
--
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.
signature.asc
Description: PGP signature
i'm pretty sure that the corruption issues leading to the
nodelalloc option were considered largely remedied by the
"auto_da_alloc" capability introduced (and enabled by default)
in 2.6.30? how would nodelalloc equal the performance of
delalloc? nodelalloc was all about reliability for programs
Version: 0.7.4-2
close 1021639
i'm stupid. /usr/local strikes again. sorry!
signature.asc
Description: PGP signature
Package: wayfire
Version: 0.7.4-2
Severity: important
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
I installed wayfire 0.7.4-2, and attempted to run wayfire. It refused to start,
due to an undefined symbol. Prior to this, it printed several diagnostics, so
I'm guessing this symbol is
Package: fritzing
Version: 0.9.6+dfsg-2+b1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
Version 0.9.10 of fritzing was released 2022-05-22. It includes a beta
simulator, a powerful new addition to fritzing. It would be great to have it in
Debian. If you need assistance
Package: prometheus-mqtt-exporter
Version: 0.1.4-2+b9
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
I was attempting to determine why promtheus-mqtt-exporter as packaged in Debian
wasn't honoring the MQTT2PROM_MQTT_USER and _PASSWORD variables defined in a
systemd
Package: prometheus
Version: 2.24.1+ds-1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
I run prometheus on a Libre Computer Potato SBC, lacking an RTC,
collecting from prometheus-node-exporter on my workstation. In the
default configuration, prometheus fills logs with
thanks for the report. i'll look into it ASAP! it seems it ought
be pretty simple to fix.
i'm running into this thanks to zoneminder (it looks like some
packages which were depending on rsyslogd|system-log-daemon, ala
the aforementioned nullmailer, no longer do). looking at
/var/lib/dpkg/info/systemd.postinst, it appears that persistent
journal in auto-mode *is* enabled by default on
Package: libcpuset1
Version: 1.0-6
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
CPUSET.3 claims
"For additional documentation on cpusets, and for details of the all
the other, advanced, routines, see
/usr/share/doc/packages/libcpuset/libcpuset.html
wait...even the most recent of these logs shows that it is
testing notcurses 3.0.4, which indeed had this timing problem on
input, which was fixed in notcurses 3.0.5:
Get:1 http://deb.debian.org/debian testing/main notcurses 3.0.4+dfsg.1-1 (dsc)
[3,148 B]
i'm tracking this upstream at
https://github.com/dankamongmen/notcurses/issues/2645
i'm pretty sure raspberry pi is armhf, so i ought be able to dig
that one RPi4 i've got up and explore this. if we can reproduce
the problem interactively, it ought fall pretty quickly.
note that armhf is a 32-bit arm7 machine, unlike arm64 which is
arm8. might be time to revisit some assumptions unconsciously
made involving processor width.
> However, I don't think that adding lmodern to the package Depends is the
> right solution, as that would lead to parts of tex (admittely, a small
> part, but still) having to be installed on the system, which is not
> required by pandoc itself.
> The right solution, I believe, is to add lmodern
.
+Closes: #1005778
+
+ -- Nick Black Mon, 28 Feb 2022 10:12:41 -0500
+
pypandoc (1.7.2+ds0-1) unstable; urgency=medium
* New upstream release.
diff -Nru pypandoc-1.7.2+ds0/debian/control pypandoc-1.7.2+ds0/debian/control
--- pypandoc-1.7.2+ds0/debian/control 2021-12-29 05:19:10.0 -0500
hi, notcurses maintainer here. if you're going to proceed with this, the thing
to do is mark notcurses as depending on zlib instead of libdeflate on this
architecture, and build with `-DUSE_LIBDEFLATE=off`. the only differences ought
be performance-related.
ahh, rereading your original ITP, i see you know all about the
fdo situation. good deal =]. i just killed my fork, and am going
to submit a PR to Aetf's fork.
signature.asc
Description: PGP signature
also, there is a kmscon repo under the auspices of the
freedesktop.org organization. i talked to the original author
about removing that if he wasn't going to be taking the project
forward, but it didn't go anywhere. if someone's really picking
kmscon up, they might want to go talk to the fdo
indeed, the cursor location report fix is only on a branch. i'll
go ahead and submit it to this other fork, and rebase mine off
of theirs. thank you likewise for bringing this to my attention!
i'm glad to see kmscon getting some love.
i'm the maintainer and upstream author of Notcurses, and
if the other fork is more active, i'm happy to fold my changes
into it, but they definitely ought go in there. the most
important thing i recall doing was fixing the cursor location
report to use the proper order for coordinates.
--
nick black -=- https://www.nick-black.com
to make an apple pie
Package: mutrace
Version: 0.2.0-3.4+b2
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
Trying to use mutrace with the -d option fails:
[schwarzgerat](1) $ mutrace -d ls
ls: symbol lookup error: /usr/lib/mutrace/libmutrace-backtrace-symbols.so:
undefined symbol:
Package: stterm
Version: 0.8.4-1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
I'm the developer of Notcurses, a TUI library. I ran into a bug with st
on Debian Unstable, where the OSC4 palette query resulted in a
diagnostic and emitted garbage characters:
notcurses 3.0.4+dfsg.1-1 ought be migrating to testing soon, and
if there is any love in this world, it will resolve the
continued failures. the most recent i see is from today, still
using notcurses 3.0.3.
i added several similar unit tests to the notcurses suite, and
managed to reproduce the
exciting results! i wrapped up a similar invocation and threw it
into my notcurses drone CI, and there i fail exactly as i do
within the debian CI (i.e. we never terminate, though we don't
soak the CPU).
https://drone.dsscaw.com:4443/dankamongmen/notcurses/10240/1/2
i ought now be able to
alright, i might have found the root cause. when we declare EOF,
we're not necessarily setting the input poll fd high. as a
result, if the EOF comes at the end of an input burst, and we
rely on such notifications, we miss it.
https://github.com/dankamongmen/notcurses/issues/2521 has more
details.
wait, i just might have reproduced a failure. it doesn't look
like our failure in autopkgtests, but this is an assert()
blowing up, and i'm not certain we build with those. if not,
maybe we're hitting a case that locks up. let's hope so!
this would once again presumably be a notcurses fix.
the
further investigation: i uploaded -4 with a change to simply
redirect input from /dev/null, rather than echoing 'blockdev -v'
into the process. the result was pretty much the exact same: we
don't see the input show up, and we get a time out. of course,
attempting to reproduce this locally leads to
this is addressed in more detail at
https://github.com/dankamongmen/notcurses/issues/2519.
i expect to have this fixed within the hour. sorry for the
annoyance.
reopen 1003009
i added -DBUILD_FFI_LIBRARY=off with the intention of no longer
building these three shared objects. looking at it now, however,
this CMake variable doesn't actually seem to guard their
building and installation, and thus it will not have the desired
effect. i'm fixing this
thanks, this ought be fixed in an hour or two.
> No, only in unstable [1]. Testing should still work.
hrmm, i'm a bit confused about how this works then. i can only
upload into unstable, and it then needs to pass autopkgtests to
get into testing. oh, i guess those autopkgtests are being run
in the "testing" context? if so, that makes sense.
I see that growlight's autopkgtests are disabled in testing
right now due to the timeout. Can we please remove that, so I
can try something?
I noticed just now in the growlight testing logs that we have
output of the form e.g.:
xvda14 -> ../../devices/vbd-51712/block/xvda/xvda14
Package: wnpp
Severity: wishlist
Owner: "Nick Black (Public gmail account)"
X-Debbugs-Cc: debian-de...@lists.debian.org, dankamong...@gmail.com
Package name: openfec
Version : 1.4.2.4
Upstream Author : Victor Gaydov et al
URL : http://www.example.org/
awesome. i've got one now, but it needs some prettification.
expect it soon.
i can happily report that notcurses 3.0.2+dfsg.1-3 is passing
autopkgtests, after resolving the issue at
https://github.com/dankamongmen/notcurses/issues/2505
signature.asc
Description: PGP signature
Package: pipewire
Version: 0.3.42-1
Severity: wishlist
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
I see in the changelog "disble roc module, at least for now", but I was
hoping to use this module for synchronized audio.
Ahh, I see libroc isn't yet packaged in Debian. Were I to
well, we don't yet know whether this "took", since 3.0.2 shows
regressions across the board in autopkgtests.
i've set up the upstream bug to track this, and am on it:
https://github.com/dankamongmen/notcurses/issues/2505
thus far i've been able to run down that it's the "box" demo
that's
well, as i noted above, this use case certainly isn't the
standard way growlight will be used (although it's a valid one,
and one worth fixing -- this was a valuable exercise, and i
appreciate autopkgtests spotting this regression!). so it's not
very important to users...but at the same time, it
if i don't need the versioned dep, there is -- so far as i can
tell -- no reason to upload a new growlight at all, unless i
need do so to retrigger the autopkgtests and allow a transition
to testing.
(sorry for my ignorance--i'm still applying for DD)
signature.asc
Description: PGP signature
> I don't think you need the versioned depends really. Or did I miss
> something?
well, if you have an older version of notcurses, you're going to
run into this growlight problem, so "solving" this problem for
Debian would seem to me to require the versioned dep? i'm sure
you're much more
not that i expect you to have run extensive benchmarks or
anything, but how do you feel this compares to libdeflate? the
few comparisons i've seen suggest that they are (or at least
were) pretty much a wash, performance-wise.
Control: reopen -1
oh no! =[ well, at least this can be my primary focus now that
notcurses iii is out. i believe i've already provided
https://github.com/dankamongmen/growlight/issues/153, but that's
the tracking issue upstream.
attempts to reproduce this locally have thus far been less than
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: dankamong...@gmail.com
Hello transition team!
Notcurses has bumped the SOVERSION from 2 to 3 as of its 3.0.0 release,
reflecting a changed ABI and API both.
The only
i can happily report that the FTPmasters accepted notcurses
3.0.0 into experimental today, and thus the transition bringing
it into unstable ought begin. once that hits, i'll be landing on
this with both feet.
signature.asc
Description: PGP signature
ought i upload a -4 with a changelog entry marking the bug
closed? i didn't mark it closed in the changelog because i
explicitly wanted the bug left open.
sorry for any confusion -- i'm certainly not trying to work
around this issue in the long term by reducing testing =]. i
just know that it's
you are correct in all of your assumptions =].
signature.asc
Description: PGP signature
Thanks for the heads-up. I believe/hope that this is the same issue that
affected our ARM MacOS builds and Alpine i686/ARMHF builds through the 3.0.0
release, and which has been fixed in the 3.0.1 release:
https://github.com/dankamongmen/notcurses/issues/2420
3.0.0 is currently in the NEW
i went ahead and uploaded growlight 1.2.38 to experimental last
evening. it doesn't build now, of course, due to a dep on
missing libnotcurses3. i've asked my Application Manager (i'm
currently applying for DD status) to sponsor an upload of the
latter to experimental+NEW, so that i can begin the
Thanks. I actually just cut growlight 1.2.38 literally forty
minutes ago, and have prepared it for upload. Unfortunately,
it's dependent on the new libnotcurses3, which needs to get
through NEW. I'm not yet a DD, so I'm hoping my Application
Manager will be willing to sponsor an upload of
> Wouldn't really be happy about an NMU. A patch is clearly preferred.
> But feel free to submit that patch as a Merge Request on Salsa
> including an appropriate debian/changelog entry in the same commit.
> (Please also post the link to the MR in this bug report. TIA!)
> I'll include it then in
Package: libgpm-dev
Version: 1.20.7-9
Followup-For: Bug #939540
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
I'm going to go ahead and prepare a suitable pkg-config file for libgpm,
and submit it to you. This is part of my DD application (AM: sramacher),
so performing an NMU is also
i'm not sure whether the "forwarded" tag applies in this case,
but i've created an upstream bug (i am the upstream author) at
https://github.com/dankamongmen/growlight/issues/153.
signature.asc
Description: PGP signature
Package: growlight
Version: 1.2.37-2
Tags: upstream
Yep, I'm looking into it. For whatever reason, it's not exiting
despite input having ended. I've tried reproducing this failure
locally, but have not yet been able. I hope to fix it for
1.2.38.
--
nick black -=- https://www.nick-black.com
Source: libsixel
Version: 1.8.6-2
Followup-For: Bug #990798
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
Hi. I'm the maintainer of the new fork of libsixel at libsixel/libsixel on
GitHub. I've been maintaining it for several months now.
I see you merged my PR on salsa:
I've made the recommended change. We were still seeing
intermittent, unrelated failures after doing so, and thus I
removed the test back in July. I can no longer reproduce these
failures, so I've just uploaded 2.3.13+dfsg.1-2 with the
offending test enabled anew. Let's see how it goes.
The
Package: kbd
Version: 2.3.0-3
Severity: normal
Tags: patch upstream
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
The resizecons.8 man page refers to disalloc.8, which no longer exists. It
ought reference deallocvt.8. I've created a merge request at
hey there achim! i was wondering if you'd had any chance to
retry with a newer growlight, ideally the 1.2.31 currently in
unstable. i'd love to get this knocked out before bullseye. if
you have the time, could you give it another try?
if it fails again, valgrind output would be a true boon. i can
hurrah, it would appear that 1.2.31 is running successfully on
the autopkgtest servers (all show as passed save ppc64el, which
shows as passed here:
https://ci.debian.net/packages/g/growlight/testing/ppc64el/).
ok, the good news is that with 1.2.30, we're no longer seeing
the segfault. the bad news is that we error out due to an
inability to load up notcurses without a TERM variable.
the proper fix for this is to avoid using notcurses in any case
where we're not connected to a tty. i can get this done
alright, with 1.2.30 (1.2.29 was never released), we pass the
autopkgtests, huzzah.
not so fast! while this does indeed fix the segfault when run
without TERM, i still get an autopkgtest failure, this one
tracked down to stdout being redirected =[. so i'm gonna address
that as well. how embarrassing.
Here's the upstream bug: https://github.com/dankamongmen/growlight/issues/139
Here's the (obvious, trivial) fix:
https://github.com/dankamongmen/growlight/commit/297f487a8be84441ff75a22b5fa63305931cae70
A real brown-bagger =[.
I'm going to cut 1.2.29 and upload it to unstable. If I ought
prepare
Alright, I've got it locked down to the absence of a TERM
environment variable in the autopkgtest environment. If I run
the same command outside of autopkgtest, after running
`unset TERM`, i get the exact same failure.
So, this failure is IMHO definitely worth fixing, and I intend
to do so now,
I can now reproduce this locally, and expect to have a fix this
evening. I've looked over the rules for the Soft Freeze, and
understand that it'll be acceptable to cut a new upstream
release (I'm the upstream author) with this fix only (there have
been no other changes since this release), upload
Thanks for the heads-up; glad I've got those autopkgtests. Looking into this
now with the hope of fixing it ASAP.
ok, i took a closer look at things, and realize you don't need a
new *backend*, but a new *gui frontend*. alas, my suggestion
would be of no help in this case. good luck finding a new
upstream author! =]
hat it is both
faster and higher quality than timg--if your experiments
contradict mine, please do let me know (as the upstream author
of Notcurses)!
--
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.
I can confirm that glibc 2.31-7 returns correct values from wcwidth() for
Unicode 13 sextants.
Thanks a lot!
> The PR downgrades also the dependency on libxtables, which is
> definitely not something we want. And even for libatm1, what is the
> issue exactly? It's just one library, why is it a problem if, with
> recommends enabled, it gets installed?
> TC loses functionality without it.
the only loss is
Package: iproute2
Version: 5.10.0-1
Severity: wishlist
Tags: patch
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
[ A patch has been provided for this bug at
https://salsa.debian.org/debian/iproute2/-/merge_requests/4 ]
Recommends "should list packages that would be found together with
Package: libc6
Version: 2.31-6
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
Unstable currently contains GNU libc 2.31. I assume that this is the version
expected to go into Bullseye. If 2.32 is intended, please ignore this bug.
2.32 added Unicode 13 support, including
it looks like 1.2.24-1 has fixed at least the amd64
autopkgtests. i'm waiting on the other architectures, but it
looks like we'll be able to close this.
signature.asc
Description: PGP signature
of issues. I
expect 1.2.24 to fix this, but won't be sure until it runs.
--
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.
I've found one problem that would lead to a SIGABRT on shutdown,
which might or might not include a message about an assertion
failure. This was an issue in the underlying Notcurses library,
which will be fixed in 2.0.9 and 2.1.0. I think there's at least
one other kind of failure on shutdown,
retitle 974888 segfaults sometimes on shutdown
OK Axel, I've done some significant work on growlight this past
week, and we're up to 1.2.22-1 in unstable. I've unearthed a
disturbing number of bugs during that time, and fixed a solid
dozen.
I can reproduce the segfault when shutting down on
With 1.2.22-1, we've got e.g.:
Processing triggers for libc-bin (2.31-4) ...
(Reading database ... 14094 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [06:16:57]: test blockdev-nonroot: echo "blockdev -v" |
growlight-readline --notroot
autopkgtest
), ncplane_options_symbol, __func__, 1))->x));
@@ -1635,7 +1635,7 @@
{
ncplane_options nopts = {
.y = yoff,
-#if NOTCURSES_2_0_5
+#if NOTCURSES_2
.x = xoff,
#else
.horiz = {
[schwarzgerat](0) $
--
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you n
I have replied to #975082 with the patch, as requested.
signature.asc
Description: PGP signature
I'll send the patch to #975082 as soon as I successfully pbuild
with it, thanks Sebastian.
signature.asc
Description: PGP signature
ed snd. I think this is a much worse option,
but I'm willing to take the hit if it makes things easier for
you -- I've caused you enough problems :(.
--
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.
signature.asc
Description: PGP signature
first off, sorry about that. it was in the NEWS, but it really
did come at an inconvenient time, and probably wasn't the best
call. this is an API change but *not* an ABI change[0].
* 2.0.7 (2020-11-21)
* The `horiz` union of `ncplane_options` has been discarded; the `int x`
within has been
Thanks for the report. I was aware of the autopkgtest failures,
but didn't realize that a failure there prevented migration. This
failure seems a property of the autopkgtest environment, and
has thus proved difficult to debug without a release. The
upcoming 1.2.21 release has added diagnostics to
On Sat, 21 Nov 2020 09:10:37 +0100 Sebastian Ramacher
wrote:
> Control: tags -1 + confirmed
Nevermind, I see that the "confirmed" tag is a sufficient litmus. Thanks!
Uploading now =].
On Sat, 21 Nov 2020 09:10:37 +0100 Sebastian Ramacher
wrote:
> With that fixed, please go ahead with the upload to unstable.
Thanks Sebastian! May I assume you're speaking on behalf of Release Team?
If so, I will proceed with the upload directly.
I will get with upstream and submit a patch to bring them up to speed with
the 2.0 api. At that point, the package ought be buildable in unstable
against libnotcurses1, and will also build from libnotcurses2. Thanks for
the heads-up!
--
nick black
to make an apple pie from scratch, one need
thank you so much for the report! i resolved several issues in
the 1.2.19 release that hit Unstable today, though i'm not sure
that this is one of them -- i'll be able to do a closer analysis
this evening. it is also possible that this is related to
DBTS #974888. sorry for the annoyance and
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: dankamong...@gmail.com, pk...@debian.org
I am the upstream author and Debian Maintainer of notcurses. The 2.0.0 release
included an soname bump to 2, though there were
> That would have been sufficient for the file conflict, but I assumed
> that the forgotten soname bump makes lib*1 (>= 2) not neccessarily
> broken, but at least undesired versions.
makes sense. thanks for the explanation, and thanks once again
for the bug report and your well-known vigilance!
The segfault at shutdown has been resolved.
See: https://github.com/dankamongmen/growlight/issues/106
This fix will be in 1.2.19, which I am about to cut.
I've just uploaded 2.0.4+dfsg.1-3, which I believe fixes this
issue. It ought be available within a few hours. I believe that
the version constraints could have been tightened to (>= 2.0.4),
but I didn't see this as adding particularly much value. Thanks
as always for filing these bugs, Andreas!
1 - 100 of 260 matches
Mail list logo
