iously this still fails, as only the
combination of new bouncycastle and new pgpainless works.
CC-ing release for awareness.
Chris
Control: block 1101381 by -1
On Sun, Apr 27, 2025 at 06:05:09PM +0200, Chris Hofstaedtler wrote:
> Attached is a patch that can be dropped into debian/patches, which fixes the
> FTBFS on s390x. TBH I have not tested the patch on non-s390x, but I assume
> it should be fine on little-end
35s
35s tests/test_np.py:355: AssertionError
Attached is a patch that can be dropped into debian/patches, which fixes the
FTBFS on s390x. TBH I have not tested the patch on non-s390x, but I assume
it should be fine on little-endian archs.
There are probably other ways of fixing this,
,
removing a conffile is a supported action, and maintainer scripts
must not fail in this case.
A workaround should be:
dpkg -i --reinstall ./javascript-common_*.deb
(Which should restore the missing conffiles.)
Chris
* VA [250427 15:46]:
Hi Chris,
(Thanks for putting me in CC so I'm notified as I wasn't aware someone
had closed the issue)
Le 27/04/2025 à 15:22, Chris Hofstaedtler a écrit :
| > a2query -c javascript-common
| > echo $?
I gave it above, but I'll repeat it, a2
ot a fan of keeping a "history" document
around, when we can look at the git history :-)
I've stopped installing addpart, delpart in Debian revision 2.40-1,
on my understanding that partprobe, (k)partx or a number of other
tools can be used instead.
Chris
re-installs without issue. Thus, I wonder if this should be
| considered release-critical or lowered in priority.
Best,
Chris
talk to (some?) DoQ remotes.
Thanks,
Chris
* Chris Hofstaedtler [250418 15:18]:
* Roland Clobus [250418 09:03]:
in the log with QEMU-issues, I saw this line:
`dmesg: read kernel buffer failed: Operation not permitted`
[..]
I've changed the sysctl now, and hope this is enough to make it work.
We'll see in the nex
Source: libvpx
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Source: virtualbox
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Source: thunderbird
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Source: xvidcore
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Source: loadlin
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Source: handbrake
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Source: aom
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Source: gstreamer-vaapi
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Source: gst-libav1.0
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Source: gkl
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Source: chromium
Hi,
your package seems to build-depend on yasm, which is orphaned in
Debian and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
Package: python3-sage
Hi,
your package seems to depend on yasm, which is orphaned in Debian
and upstream indicated they moved on to different projects.
Please find a replacement.
Chris
On Sat, Apr 26, 2025 at 05:32:58PM +0200, Ben Hutchings wrote:
> - This does not affect the default C and C++ toolchain
#1103592 is I think a case that does affect the default C and C++
toolchain.
king a new
username.
There is no requirement to change the username, and it's probably a
bad idea.
Chris
..]
There might very well be a bug here, but it has to occur in a better
defined environment to be "serious".
Chris
old binaries from unstable.
Indeed if the package FTBFS on a particular arch, restricting the
Architectures: field is usually best avoided, see
https://salsa.debian.org/debian/developers-reference/-/merge_requests/60/diffs
Best,
Chris
patch, even
to the version in experimental.
I will ask upstream whether they plan to fix earlier versions
themselves, otherwise I will spend more time trying to work out how to
backport this.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
ou think I should just go ahead w disabling tests for this arch for now?
Not Paul or RT, but I think it makes sense to keep the tests
failing. I believe very few people will run GUI programs on s390x,
so not having kitty there seems safe.
Chris
but at the very least this prevents migration of live-tasks 13.0.3
to testing, as the BTS now thinks the bug is not fixed in 13.0.3.
Please also see the excuses data:
https://qa.debian.org/excuses.php?package=live-tasks
Chris
on for pam.
Please provide instructions how to reproduce / test possible fixes.
Chris
e or use -U.
Chris
"sufficient" to close this topic?
Chris
upgraded systems as well)
initscripts provides hwclock.sh.
Chris
* Andrius Merkys [250422 09:27]:
Hi,
On 2025-04-19 14:09, Chris Hofstaedtler wrote:
coot's autopkgtests fail with rdkit 202503.1-2:
https://ci.debian.net/packages/c/coot/testing/amd64/60162582/
76s Traceback (most recent call last):
76s File "", line 198, in _run_modu
Source: openstack-meta-packages
Version: 0.37
Severity: serious
Control: affects -1 src:ntpsec
X-Debbugs-CC: ntp...@packages.debian.org
Per tracker.d.o:
5 binary packages have unsatisfiable dependencies:
The dependencies of openstack-toaster=0.37 cannot be satisfied in unstable on
amd64 because
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: xserver-xorg-video-trid...@packages.debian.org
Control: affects -1 + src:xserver-xorg-video-trident
#1087037 asked for removal from arm64 armel armhf mips64el ppc64el,
but riscv64 was m
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: xserver-xorg-video-t...@packages.debian.org
Control: affects -1 + src:xserver-xorg-video-tdfx
#1087036 asked for removal from arm64 armel armhf mips64el ppc64el,
but riscv64 was missed
Control: severity -1 normal
* Helmut Grohne [250421 19:12]:
Source: xserver-xorg-video-trident
xserver-xorg-video-trident fails to build from source on arm
architectures.
#1087037 removed the binaries from arm64 armel armhf mips64el
ppc64el, so this is not r-c on these archs.
Chris
.
Chris
h.service waits
for a particular interface to come up.
Another way might be to set IP_FREEBIND, possibly with an sshd
config option.
Personally I just enable the ip_nonlocal_bind sysctl on machines
where I intend to bind services (not just sshd) to specific IP
addresses.
Chris
https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/patches/0003_reproducible-build.patch 1969-12-31
16:00:00.0 -0800
--- b/debian/patches/0003_reproducible-bu
tself, i.e. separate from reproducibility, that this package ships
a pseudo Python package here. :)
Either way, patch attached that removes these after running the tests.
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `&#x
,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/patches/0001-Reproducible-build.patch 1969-12-31
16:00:00.0 -0800
--- b/debian/patches/0001-Reproducible-build.patch 2025-04-21
09:19:54.639357255
t. It won't fix the deprecation warning, but
at least it will start.
Chris
ess, s390x: Failed (not a regression)
This also holds up ruby3.3 3.3.8-1 from migrating to testing.
Please check ruby-roo's autopkgtests, f.e.:
https://ci.debian.net/packages/r/ruby-roo/testing/amd64/60182517/
https://ci.debian.net/packages/r/ruby-roo/testing/arm64/60182518/
Chris
done. Probably there's some hidden blocker which I've missed.
If so, it'd be nice to not have these bugs show up on the UDD
search for trixie.
Chris
et makes no guarantees on addresses, or even the
specific address configured in sshd.conf.
If it helps in your local setup, I'd encourage you to use a local
override file.
Chris
look at the upstream source suggests that these format
strings have indeed been changed in 2.3.0.
Chris
bugs like
https://github.com/protocolbuffers/protobuf/issues/3937 - from
2017/2018.
At the very least this should be registered with the code copy
registry and updated. IMO it would be better to use libprotobuf-dev
and libproto-c though.
Chris
Looks similar to this old protobuf problem upstream:
https://github.com/protocolbuffers/protobuf/issues/3937
ybe true from an opensnitch perspective.
But from grpc_tools.protoc perspective: the program just doesn't
work on riscv64, yet we ship it.
That seems release-critical to me.
Chris
+CC: co-maintainer, last uploader
* Demi Marie Obenour [250421 09:09]:
Upstream H2O no longer makes releases (https://github.com/h2o/h2o/3230)
and the tagged releases are therefore EOL and do not get security patches
anymore. This means that there might be upstream vulnerabilities that
affect
think uploading it is fine, at least it will pass through NEW and it
can be there for forky.
Chris
(just drive-by commenting)
On Sun, Apr 13, 2025 at 10:50:03PM +0200, Bastien Roucaries wrote:
> Le dimanche 13 avril 2025, 22:47:54 heure d’été d’Europe centrale Chris
> Hofstaedtler a écrit :
> > * Bastien Roucaries [250413 22:09]:
> > >Le dimanche 13 avril 2025, 20:55:07 heure d’été d’E
/rules:3: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess
returned exit status 2
Similar issues can be seen on armel, armhf, i386, ppc64el, s390x.
Chris
Source: rust-subversion
Version: 0.0.8-3
Tags: ftbfs
rust-subversion FTBFS everywhere except on amd64, mips64el, and
loong64.
Example log from arm64:
https://buildd.debian.org/status/fetch.php?pkg=rust-subversion&arch=arm64&ver=0.0.8-3&stamp=1744759574&raw=0
Most of the issues appear to be s
consider dropping the embedded copy over the packaged
library.
Chris
hon-313-riscv64-linux-gnu.so:
undefined symbol: _ZN6google8protobuf8internal22Release_CompareAndSwapEPVlll
The same command works on arm64, so this seems like some riscv64 problem.
Chris
ii python3-grpc-tools 1.14.1-7+b3 riscv64 Protobuf code generator for
gRPC (Python 3)
ii python3-gr
python3.13-minimal 3.13.2-3 riscv64 Minimal subset of the
Python language (version 3.13)
ii python3.13-venv3.13.2-3 riscv64 Interactive high-level
object-oriented language (pyvenv binary, version 3.13)
Installing python3-pkg-resources makes *this* error go away.
Chris
Source: kasts
Version: 25.04.0-1
Severity: serious
Tags: ftbfs
Example build log:
https://buildd.debian.org/status/fetch.php?pkg=kasts&arch=arm64&ver=25.04.0-1&stamp=1745138731&raw=0
...
-- Found KF6Kirigami:
/usr/lib/aarch64-linux-gnu/cmake/KF6Kirigami/KF6KirigamiConfig.cmake (found version
"
Source: jool
Version: 4.1.14-1
Severity: serious
Tags: ftbfs
jool FTBFS on the arch:all buildd:
https://buildd.debian.org/status/fetch.php?pkg=jool&arch=all&ver=4.1.14-1&stamp=1745079132&raw=0
dh_missing -i
dh_missing: warning: usr/bin/jool exists in debian/tmp but is not installed to anywher
Source: mtail
Version: 3.0.9-1
Severity: serious
Tags: ftbfs
mtail FTBFS on the amd64 buildds:
https://buildd.debian.org/status/fetch.php?pkg=mtail&arch=amd64&ver=3.0.9-1%2Bb6&stamp=1745010540&raw=0
...
=== RUN TestLogRotationByRename/race_simulation_enabled
log_rotation_integration_unix_t
Source: isenkram
Version: 0.67
Severity: serious
Tags: ftbfs
isenkram 0.67 FTBFS:
https://buildd.debian.org/status/fetch.php?pkg=isenkram&arch=all&ver=0.67&stamp=1745101670&raw=0
dh binary-indep --with python3 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_
Source: drumkv1
Version: 1.3.1-1
Severity: serious
X-Debbugs-CC: s...@debian.org
drumkv1 fails its autopkgtests on all architectures,
preventing migration to testing. Example on amd64:
https://ci.debian.net/packages/d/drumkv1/testing/amd64/60170722/
33s autopkgtest [23:06:40]: test simpletest
Source: vala-panel-appmenu
Version: 24.05+dfsg-2
Severity: serious
Tags: ftbfs
X-Debbugs-CC: sunwea...@debian.org
vala-panel-appmenu build-depends on libvalapanel-dev (>= 24.03)
which is available on no architectures.
Chris
Source: synthv1
Version: 1.3.1-1
Severity: serious
X-Debbugs-CC: s...@debian.org
synthv1 fails its autopkgtests on all architectures,
preventing migration to testing. Example on amd64:
https://ci.debian.net/packages/s/synthv1/testing/amd64/60170830/
44s autopkgtest [01:06:44]: test simpletest
Source: vcsh
Version: 2.0.10-0.1
Severity: serious
X-Debbugs-CC: hi...@debian.org
vcsh 2.0.10-0.1 fails its autopkgtests on all architectures,
preventing migration to testing. Example on amd64:
https://ci.debian.net/packages/v/vcsh/testing/amd64/60170831/
39s autopkgtest [01:06:39]: test comma
Hi Jelmer,
* Jelmer Vernooij [250419 18:40]:
Is this repeatable or perhaps a flaky test?
https://buildd.debian.org/status/logs.php?pkg=breezy&ver=3.3.11-1&arch=s390x
It failed three out of three attempts on the buildd. So, not just
flaky I think?
Chris
On Sat, Apr 19, 2025 at 01:27:21PM +0200, Chris Hofstaedtler wrote:
> On Sat, Apr 19, 2025 at 12:45:08AM -0400, Sergio Durigan Junior wrote:
> > On Monday, April 07 2025, Graham Inggs wrote:
> > > The recent upload of patchelf 0.18.0-1.2 FTBFS on mips64el [1]. I've
> >
Control: forwarded -1
https://git.libssh.org/projects/libssh.git/commit/?id=af10857aa3216f40c5c2e5d7116803fb03c166f9
Control: tags -1 + upstream fixed-upstream
On Tue, Apr 15, 2025 at 01:22:22AM +, Santiago Vila wrote:
> /<>/build-openssl/tests/tests_config.h:3:41: error: missing
> binary op
uby-serialport
subtle: subtle
I just uploaded a fixed ruby-eb.
I would guess the remaining ruby-* packages could either be broken
or removed. subtle appears upstream dead. libprelude also appears
upstream dead and has other open RC bugs.
Not sure whats the story with robot-testing-framework, CC'ing Nilesh
Patra.
Chris
+0200
+++ ruby-eb-2.6/debian/changelog 2025-04-19 15:25:59.0 +0200
@@ -1,3 +1,10 @@
+ruby-eb (2.6-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Apply patch from TODOROKI Shin-ichi to fix FTBFS. (Closes: #1075457)
+
+ -- Chris Hofstaedtler Sat, 19 Apr 2025 15:25:59 +0200
+
ru
Source: forensics-all
Version: 3.59
Severity: serious
Your package currently Depends: o-saft, which is to be removed from
trixie (#1102172). This is a serious bug, as your package will become
uninstallable. It will thus also removed from trixie.
19 13:54:16.0 +0200
@@ -1,3 +1,12 @@
+axc (0.3.7-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Gui-Yue ]
+ * disable -fcf-protection=full to fix FTBFS (Closes: #1101090)
+
+ -- Chris Hofstaedtler Sat, 19 Apr 2025 13:54:16 +0200
+
axc (0.3.7-2) unstable; urgency=m
Source: rust-cargo-test-support
Version: 0.3.0-1
Severity: serious
Tags: ftbfs
rust-cargo-test-support's build-depends are unavailable on all archs:
rust-cargo-test-support build-depends on missing:
- librust-git2-0.19+default-dev:amd64
rust-cargo-test-support build-depends on missing:
- librus
Source: rust-termwiz
Version: 0.22.0-2
Severity: serious
Tags: ftbfs
rust-termwiz build-depends on missing:
- librust-finl-unicode-1+default-dev:amd64 (>= 1.2-~~)
rust-termwiz build-depends on missing:
- librust-finl-unicode-1+default-dev:arm64 (>= 1.2-~~)
rust-termwiz build-depends on missing:
Source: kitty
Version: 0.40.0-1
Severity: serious
Tags: ftbfs
User: debian-s...@lists.debian.org
X-Debbugs-Cc: debian-s...@lists.debian.org
Your package previously built on s390x but now fails with various test
failures:
https://buildd.debian.org/status/fetch.php?pkg=kitty&arch=s390x&ver=0.40.0-
Source: octave-image
Version: 2.16.0-1
Severity: serious
X-Debbugs-Cc: raf...@debian.org
Your package currently fails its autopkgtests on all architectures. Note
that this prevents testing migration.
Example on amd64:
https://ci.debian.net/data/autopkgtest/testing/amd64/o/octave-image/60157626/
Source: python-djvulibre
Version: 0.9.1-1
Severity: serious
X-Debbugs-Cc: Colin Watson , debian-s...@lists.debian.org
Your package python-djvulibre fails its autopkgtests on s390x:
https://ci.debian.net/packages/p/python-djvulibre/testing/s390x/60156109/
PageJobsTestCase.test_decode
...
60s >
Source: faust
Version: 2.79.3+ds-1
Severity: serious
Tags: ftbfs
Justification: ftbfs
Your package FTBFS on mips64el because of the dwz bug #1016936. While
its likely dwz's fault, your package is affected by it, and the dwz bug
has not moved since November 2024. It seems necessary to apply a
wo
Source: python-mastodon
Version: 2.0.1-1
Severity: serious
Your package fails its autopktests on i386 and riscv64, with different
failures.
i386:
https://ci.debian.net/packages/p/python-mastodon/testing/i386/59129591/
test_entity_scheduledstatus
598s > isotime =
datetime_val.astimezone(
Source: ccache
Version: 4.11.2-1
Severity: serious
ccache's autopkgtests fail on all archs. This prevents testing migration.
Example:
https://ci.debian.net/packages/c/ccache/testing/amd64/60157589/
...
105s Running test suite profiling_gcc_10+...test.c: warning: filename
'/tmp/autopkgtest-lxc.
Source: mimalloc
Version: 3.0.3+ds-1
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: armhf
Version 3.0.1+ds-2.1 built before, but 3.0.3+ds-1 fails:
https://buildd.debian.org/status/fetch.php?pkg=mimalloc&arc
Source: python-xiaomi-ble
Version: 0.36.0-1
Severity: serious
User: debian-s...@lists.debian.org
Usertags: s390x
python-xiaomi-ble autopktests fail on s390x:
https://ci.debian.net/packages/p/python-xiaomi-ble/testing/s390x/59901553/
39s === FAILURES
Source: hyperkitty
Version: 1.3.12-3
Severity: serious
X-Debbugs-Cc: mist...@packages.debian.org
Control: affects -1 src:mistune
hyperkitty's autopkgtests fail with mistune 3.1.3-1 on all archs.
Example log:
https://ci.debian.net/packages/h/hyperkitty/testing/amd64/60157623/
338s ===
pdfsam is currently blocked by bouncycastle, which has got RC bug
#1100227, and is waiting for the maintainer to respond to the patch.
On Sat, Apr 19, 2025 at 12:45:08AM -0400, Sergio Durigan Junior wrote:
> user debian-rele...@lists.debian.org
> usertags 1102299 + bsp-2025-04-brazil
> thanks
>
> On Monday, April 07 2025, Graham Inggs wrote:
>
> > Hi Maintainer
> >
> > The recent upload of patchelf 0.18.0-1.2 FTBFS on mips64el [
Package: ftp.debian.org
X-Debbugs-Cc: lomiri-docviewer-...@packages.debian.org,
debian-m...@lists.debian.org
Control: affects -1 + src:lomiri-docviewer-app
User: ftp.debian@packages.debian.org
Usertags: remove
User: debian-m...@lists.debian.org
Usertags: mips64el
User: debian-m...@lists.debian
Source: python-tz
Version: 2025.2-1
Severity: serious
python-tz's autopkgtests fail on all archs:
https://ci.debian.net/packages/p/python-tz/testing/amd64/60158064/
29s autopkgtest [22:21:50]: test unittest: cp -r pytz/tests "$AUTOPKGTEST_TMP"
&& cd "$AUTOPKGTEST_TMP" && rm -f tests/test_docs.
Source: rust-libxml
Version: 0.3.4-1
Severity: serious
Tags: ftbfs
Justification: ftbfs
User: debian...@lists.debian.org
Usertags: i386
0.3.3-1 built on i386, but 0.3.4-1 fails:
https://buildd.debian.org/status/fetch.php?pkg=rust-libxml&arch=i386&ver=0.3.4-1&stamp=1744884797&raw=0
[libxml 0.3.4]
Source: coot
Version: 1.1.15+dfsg-1
Severity: serious
X-Debbugs-Cc: rd...@packages.debian.org
Control: affects -1 src:rdkit
coot's autopkgtests fail with rdkit 202503.1-2:
https://ci.debian.net/packages/c/coot/testing/amd64/60162582/
76s Traceback (most recent call last):
76s File "", line 1
On Wed, Apr 16, 2025 at 09:08:52PM +0200, Lucas Nussbaum wrote:
> Source: selint
> Version: 1.5.1-1
> Severity: serious
> During a rebuild of all packages in testing (trixie), your package failed
> to build on armhf.
>
Can now also be observed on the buildds:
https://buildd.debian.org/status/log
Source: breezy
Version: 3.3.11-1
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: debian-s...@lists.debian.org
User: debian-s...@lists.debian.org
Usertags: s390
breezy FTBFS on the s390x buildds:
https://buildd.debian.org/status/logs.php?pkg=breezy&ver=3.3.11-1&arch=s390x
https://
bdiff' containing this is attached.
Somewhere I have some instructions on setting up cowbuilder with qemu to
emulate an architecture, I'm going to see if I can build a cowbuilder
instance for arm64 and see if I can do a build that avoids running the
tests.
-- Chris
--
Chris K
* Mark - Syminet [250418 18:27]:
On Fri, 2025-04-18 at 17:31 +0200, Chris Hofstaedtler wrote:
If, as you say, this is configurable in /etc/login.defs, then: IMO
it would be better to send a patch describing the configurable
behaviour, and sending that upstream.
Do you know offhand if
ribing the configurable
behaviour, and sending that upstream.
For option -M, there is already some text about CREATE_HOME.
I guess it was an overseen that -d would also need some text.
Best,
Chris
ible for normal users,
which I reported upstream [1].
Could you try to allow the isotovideo user to access dmesg, and see
whether you get an out-of-memory message for QEMU?
I've changed the sysctl now, and hope this is enough to make it
work. We'll see in the next few days.
Thanks,
Chris
elf. This will
allow ping to run without extra permissions.
Chris
are also affected by this bug.
Kind Regards
Chris Sutcliff
* Mike Gabriel [250417 10:19]:
So what would be the required step for getting lomiri-docviewer-app
migrate to testing?
RM request to ftp.debian.org for lomiri-docviewer-app on mips64el?
That's certainly necessary. Not sure if it's sufficient.
Chris
Hello, Daniel
On 4/16/25 08:13, Daniel Gröber wrote:
Package: mlmmj
Version: 1.5.0-1
X-Debbugs-CC: Chris Knadle , Michael Jeanson
, Thomas Goirand , d...@darkboxed.org
Hi Chris,
I'm moving this to the BTS for visibility.
Okay that's good -- I would have opened a bug report on thi
1 - 100 of 9442 matches
Mail list logo
