Gregor Herrmann: Debian MountainCamp, Innsbruck, 16 18 May 2025

- location: it-syndikat hackspace (tschamlerstra e 3, innsbruck, austria)
- dates: 16 18 May 2025
(-Werror=implicit-function-declaration)
in debian, it didn't
build any more & received an RC bug.
because I sometimes like challenges, I had a look at it & cobbled together
a patch. as I hardly speak any C, I sent my notes to the bug report
& (implictly) asked for help. & went out to meet a
friend.
when I came home, I found an email from ntyni, sent less than 2 hours
after my mail, where he friendly pointed out the issues with my patch
& sent a corrected version.
all I needed to do was to adjust the patch & upload the package. one
more bug fixed, one less task for us, & elbrus can concentrate on more
important tasks :)dpt(1)
wrapper script.
in the last years I got the impression that not all team members are aware
of all the useful tools, & that some more promotion might be called for.
& last week I was in the mood for creating a short demo video to
showcase how I use some dpt(1)
subcommands when updating a
package to a new upstream release. (even though I prefer text over videos
myself :))
probably not a cinematographic masterpiece but as the feedback of a few
viewers has been positive, I'm posting it here as well:
(direct
link as planets ignore iframes )
Dealing with the void during MiniDebConf Online #1
Between 28 and 31 May this year, we set out to create our first ever online MiniDebConf for Debian. Many people have been meaning to do something similar for a long time, but it just didn t work out yet. With many of us being in lock down due to COVID-19, and with the strong possibility looming that DebConf20 might have had to become an online event, we rushed towards organising the first ever Online MiniDebConf and put together some form of usable video stack for it.
I could go into all kinds of details on the above, but this post is about a bug that lead to a pretty nifty feature for DebConf20. The tool that we use to capture Jitsi calls is called Jibri (Jitsi Broadcasting Infrustructure). It had a bug (well, bug for us, but it s an upstream feature) where Jibri would hang up after 30s of complete silence, because it would assume that the call has ended and that the worker can be freed up again. This would result in the stream being ended at the end of every talk, so before the next talk, someone would have to remember to press play again in their media player or on the video player on the stream page. Hrmph.
Easy solution on the morning that the conference starts? I was testing a Debian Live image the night before in a KVM and thought that I might as well just start a Jitsi call from there and keep a steady stream of silence so that Jibri doesn t hang up.
It worked! But the black screen and silence on stream was a bit eery. Because this event was so experimental in nature, and because we were on such an incredibly tight timeline, we opted not to seek sponsors for this event, so there was no sponsors loop that we d usually stream during a DebConf event. Then I thought Ah! I could just show the schedule! .
DebConf20 Moves Online For DebConf, we usually show a sponsors loop in between sessions. It s great that we give our sponsors visibility here, but in reality people see the sponsors loop and think Talk over! and then they look away. It s also completely silent and doesn t provide any additional useful information. I was wondering how I could take our lessons from MDCO#1 and integrate our new tricks with the sponsors loop. That is, add the schedule, time, some space to type announcements on the screen and also add some loopable music to it. I used OBS before in making my videos, and like the flexibility it provides when working with scenes and sources. A scene is what you would think of as a screen or a document with its own collection of sources or elements. For example, a scene might contain sources such as a logo, clock, video, image, etc. A scene can also contain another scene. This is useful if you want to contain a banner or play some background music that is shared between scenes.
The Loopy Loop Music The two mini albums that mostly played during the first few days were just a copy and paste from the MDCO#1 music, which was:
For shoutout tracks, that were later used in the loop too (because it became a bit monotonous), most of the tracks came from freepd.com:README
file in the package long description (#17).
send-later
functionality. [...]
py3versions -i
in autopkgtests and debian/rules
files. (#954763)py3versions -s
is used without a python3-all
dependency. (#954763)possible-missing-colon-in-closes
to also check for semicolons used in place of colons. (#954484)YYYYMMDD-1
) without a 0~
suffix. (#953036)duplicate-short-description
or duplicate-long-description
if they contain substitution variables. (#947168)Standards-Version
when uploading to the backports repository. [...]Checksums-Sha256
fields. (#954798)DEBIAN/md5sums
control files in udebs. (#954803)<!nocheck>
annotations; some packages are required to build successfully. (#954338)debian-rules-uses-installed-python-versions
tag. [...]CONTRIBUTING.md
file. [...]debian/changelog
entry. [...]debian-installer
component to allow all arguments from sources.list
files (such as [check-valid-until=no]
) in order that we can test the reproducibility of the installer images on the Reproducible Builds own testing infrastructure. (#13)
/bin/dash
and /bin/bash
), cloudkitty (due to a default value being taken from the number of CPUs on the build machine), font-manager (embedding the value of @abs_top_srcdir@
into the resulting binary), gucharmap (due to embedding the absolute build path when generating a comment in a header file), infernal (timestamps are injected into a Python example, which should not be shipped anyway), ndisc6 (embeds the value of CFLAGS
into the binary without sanitising any absolute build paths), node-nodedbi (embedded timestamp in binary) & pmemkv (does not respect SOURCE_DATE_EPOCH
when populating a YEAR
variable).
calendar.monthrange
Python method. [...]
138
to Debian:
readelf
. (#93)dumppdf
from the python3-pdfminer
if we do not see any other differences from pdftext
, etc. (#92).rdx
files directly as the get_member
method will return a file even if the file is missing. [...]--help
output or in the package long description. [...]--list-debian-substvars
when we want them for debian/tests/control
generation. [...]upstream-metadata-in-native-source
as "we" are upstream. [...]RequiredToolNotFound.get_package
method's functionality as it is only used once. [...]py36 = [..]
" argument in the pyproject.toml
file. [...]POST
method in the web-based scheduler as not only should HTTP GET requests be idempotent but this will allow many future improvements in the user interface. [...][...][...]
glibc
(CVE-2020-1751), jackson-databind
, libbsd
(CVE-2019-20367), libvirt
(CVE-2019-20485), netkit-telnet
& netkit-telnet-ssl
(CVE-2020-10188), pdfresurrect
(CVE-2020-9549) & shiro
(CVE-2020-1957), etc.
xtrlock
versions 2.8+deb9u1
(#949112) and 2.8+deb10u1
(#949113) was accepted to the Debian jessie and buster distributions.
snprintf(3)
.
twisted
to prevent a large number of HTTP request splitting vulnerabilities in Twisted, a Python event-based framework for building various types of internet applications.
libbsd
, a library of functions commonly available on BSD systems but not on others such as GNU.
2.2.11-1
& 3.0.4-1
) New upstream security releases. (#953102)
6.0~rc1-3
Install OpenSSL when running the testsuite as it is required for generating test certificates.6.0~rc2-1
New upstream beta release.2.13
) Add a warning that X11 does not support grabbing events under the Wayland display server protocol. (#953319)
20.0.4-4
) Ensure that the Python 3.x gunicorn
binary package replaces the now-legacy gunicorn3
that was removed in 19.9.0-2
upon installation. I also backported this version to buster-backports. (#953883)
0.14.1-1
) New upstream release.
1.00-7
) Fix build failures under Python 3.8. (#954287)
1.6.0-1
New upstream release.1.6.1-1
New upstream release.1.6.2-1
New upstream security release. (#954808)1.6-2
, 1.6-3
& 1.6-4
) Fix various build failures on kFreeBSD architectures.
4.0.24-1
) New upstream release.
2.4-6
) Remove a vague "pigeon holes" metaphor from package description.
pyptlib
package be removed from the archive (#953429) as well as uploading onionbalance (0.1.8-6
) to fix test failures under Pytest 3.x (#953535) and a new upstream release of nautilus-wipe.
Finally, I sponsored an upload of bilibop (0.6.1
) on behalf of Yann Amar.
stretch
release
happened without many RC bug fixes from me; in practice, the
auto-removals
are faster & more convenient.
what I nevertheless did in the last months was to fix RC bugs in
pkg-perl
packages (it still surprises me how fast rotting &
constantly moving code is); prepare RC bug fixes for jessie (also for
pkg-perl
packages); & in the last weeks provide patches
& carry out NMUs for perl packages as part of the ongoing perl
5.26
transition.
Next.