If you've got something going, go ahead with it with my blessing =]. I just
want the tool in Debian.
nick black
to make an apple pie from scratch, one need first invent a universe.
On Sun, May 4, 2025, 1:18 PM Daniel Baumann wrote:
> Hi Nick,
>
> I just saw your ITP afte
i believe that i've fixed this upstream. currently 3.0.13 looks
good on all architectures, including s390x and all arms:
https://ci.debian.net/packages/n/notcurses/
unless someone thinks otherwise, i'd like to close this as fixed
in 3.0.13.
signature.asc
Description: PGP signature
building `notcurses-tester` requires three things to be true:
* `USE_CXX` must be ON
* `BUILD_TESTING` must be ON
* `USE_DOCTEST` must be ON
`notcurses-tester` is installed no matter what, and indeed, it
should be built and installed even if tests aren't being
immediately run. Yet it appears
ok, here's what's up: `BUILD_TESTING` is defined by CTest, so
as you speculated, `notcurses-tester` is indeed being built
during the testing stage (but only when said stage is actually
run). so i think we can fix this right now by adding
`BUILD_TESTING=ON` to the cmake arguments in the configur
> The only logical explanation I can think for a "missing files"
> error in dh_install when DEB_BUILD_OPTIONS=nocheck is that
> the ctest call is the one creating some of the files
> that dh_install reports as missing later.
I'm pretty certain that this is due to the
`-DBUILD_TESTING:BOOL=OFF` be
Looking at Santiago's build log, I confirm that we're emitting
-DBUILD_TESTING:BOOL=OFF
the full text is:
dh binary --buildsystem=cmake -B /<>/build
dh_testdir -O--buildsystem=cmake
-O-B/<>/notcurses-3.0.13\+dfsg/build
dh_update_autotools_config -O--buildsystem=cmake
-O-B/<>/notcurses-
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: zig-defa...@packages.debian.org, dankamong...@gmail.com
Control: affects -1 + src:zig-default
User: ftp.debian@packages.debian.org
Usertags: remove
zig-default should be zig-defaults, like all the other [foo]-defaults packages.
this change
Package: wnpp
Severity: wishlist
Owner: Nick Black
X-Debbugs-Cc: debian-de...@lists.debian.org, dankamong...@gmail.com
* Package name: icann-rdap
Version : 0.0.21
Upstream Contact: Andrew Newton
* URL : https://github.com/icann/icann-rdap/wiki
* License : MIT
i've got a deb up. if people want to try it out, use:
deb http://dsscaw.com/repos/apt/debian unstable main
deb-src http://dsscaw.com/repos/apt/debian unstable main
or download it directly:
https://www.dsscaw.com/repos/apt/debian/pool/main/g/ghostty/
building it from source will require the zig-
Package: liquidctl
Version: 1.14.0-1
Severity: important
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
Earlier this evening, I upgraded python3-pil 10.4.0-1.1 -> 11.1.0-1. Since
then, liquidctl exits immediately with an ImportError:
[schwarzgerat](0) $ liquidctl
Traceback (most recent ca
thanks for the thorough reply, Niels! that all sounds good.
signature.asc
Description: PGP signature
Package: debhelper
Version: 13.24.1
Severity: wishlist
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
I hope to have the zig programming language in unstable soon; I'm uploading it
to NEW now. I'll then be packaging some zig applications. Right now, I'm
hardcoding the necessary dh override
we're now running the compiler's unit tests as part of our
build. i've renamed zig zig0.13, and am installing it so that
multiple versions can coexist. i've created a new native
package, zig-default, which deps on zig0.13 and installs
toplevel symlinks. i've submitted a MR for the minisign support
i've got an MR out at
https://salsa.debian.org/debian/devscripts/-/merge_requests/463
if someone wants me to mail it here or whatever, i can do that
too. not sure how y'all prefer to handle your bugs.
if you've got packaging dependent on zig, or want to help beta
test zig on debian, there are packages available here:
https://salsa.debian.org/nickblack/zig/-/jobs/6923961/artifacts/download
alternatively, you can add the apt source:
deb http://dsscaw.com/repos/apt/debian unstable main
i'll p
block 1092863 by 995670
block 1091469 by 995670
thanks
ahhh fair enough bartm@ i had thought #995670 archived
(1) we no longer have any lintian diagnostics beyond spelling errors ✅
(2) i've replaced these with $(DEBIAN_TARGET_HOST) ✅
(3) we no longer ship msdos-stub.bin ✅
(4) man page has been (minimally) improved ✅
(5) let's just track what upstream is doing for now
(6) this is ongoing but not a blocker
(
i have submitted https://github.com/ziglang/zig/pull/22489
upstream to eliminate msdos-stub.bin. i'll make a quilt patch
from this and we ought be good.
> (3) there's a second binary file involved (beyond zig1.wasm):
> msdos-stub.bin. unlike the WASM, there does not appear to be any
> way to build this from sources available in the source package,
> so it will probably have to come out. it's only used in the COFF
> linking code, so that capability
some notes/progress:
(1) we are now building a zig binary deb on amd64 that passes
most lintian checks, and appears to contain a working zig.
most recent lintian check output:
$ lintian --suppress-tags "${SALSA_CI_LINTIAN_SUPPRESS_TAGS}" --display-info
--pedantic ${SALS
i've been working on this afresh using zig 0.13.0.
here's the status:
1) zig source is signed with minisign, which is not supported
by uscan. i'm working on adding that support in #1092818.
2) i throw out all vendored code of which i'm aware. this
massively simplifies the copyright sit
Package: wnpp
Severity: wishlist
Owner: nick black
X-Debbugs-Cc: debian-de...@lists.debian.org, dankamong...@gmail.com
* Package name: zig
Version : 0.13.0
Upstream Contact: Andrew Kelley
* URL : https://ziglang.org/
* License : MIT
Programming Lang: C
looking at
https://salsa.debian.org/debian/devscripts/-/merge_requests/460
i see the necessity of ensuring this code works in stable,
testing, etc. environments. that's a good thing to consider,
though it doesn't seem to obviously cause any problems for this
work?
btw, this work is ongoing in
https://salsa.debian.org/nickblack/devscripts/-/commits/nickblack/uscan-minisign
i'm slowly rememebering my perl from twenty-five years ago, but
things are moving forward reasonably enough.
> thanks for your bug report. Do you have any numbers on how many are "some"?
> 10? 100? 1000?
i know of precisely one, which is not yet packaged.
there is not great demand.
however, i'm almost done with the changes, and they're not very
intrusive. i've also updated the documentation, and intend
Package: lintian
Version: 2.121.1
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
I overrode dh_auto_test, and started getting a 'override_dh_auto_test-does-not-
check-DEB_BUILD_OPTIONS' I-level lintian diagnostic. With debhelper 13, this is
not necessary, see debhelper-com
Package: devscripts
Version: 2.24.10
Severity: wishlist
Tags: patch
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
some upstreams use minisign, derived from OpenBSD's signify, for tarball
verification. see my mail to debian-devel:
https://lists.debian.org/debian-devel/2025/01/msg00178.htm
so is this still relevant? i'm a bit surprised that notcurses
would have regressed since 3.0.9 on this. oh, you reported this
against 3.0.7. so this has been fixed by the introduction of
3.0.9+ into the archive, right? let me know if not--i'm going to
mark this as closed by 3.0.9.
retitle 1091469 ITP: ghostty -- Ghostty is a fast, feature-rich, and
cross-platform terminal emulator that uses platform-native UI and GPU
acceleration.
owner 1091469 !
thanks
signature.asc
Description: PGP signature
i've just released v3.0.10 of notcurses, which fixes this
upstream. i'll package it up ASAP (almost certainly today), and
it ought close this bug.
Package: texlive-latex-base
Version: 2024.20240401-3
Severity: normal
Tags: upstream
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
Beginning sometime this year, using Hebrew with babel in LuaTeX results in
positioning errors.
2023.20240207-1 worked properly, but one of the three 2024 upd
confirmed. this is a known issue with a fix present on the
notcurses main. i need to cut a new release ASAP including that
fix. until then, i can patch the debian package. there's
actually a fedora patch for the same problem:
https://src.fedoraproject.org/rpms/notcurses/c/70d807ff48579d92e580c7e
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: unpro
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 wh
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 o
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 to
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 comm
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: bookw
Can 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 tha
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 use
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 u
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 overrid
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 err
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 ne
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 t
tests.
+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
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 peopl
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 kmscon
con
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
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: _sch_istab
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:
https://gith
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 loc
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 resolve
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 br
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 upstream
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.
a
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
Partitio
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 package
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 failin
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 wa
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 knowledg
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
suc
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 rever
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 no
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 queu
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 t
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 notcurses
> 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 th
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 desi
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.ni
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:
https://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 upstrea
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
https://salsa.debian.org/debian/kbd/-/m
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
1 - 100 of 293 matches
Mail list logo
