Your message dated Wed, 01 Jan 2025 07:33:58 +
with message-id
and subject line Bug#1090793: fixed in bittwist 4.7+ds-2
has caused the Debian Bug report #1090793,
regarding src:bittwist: fails to migrate to testing for too long
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 1 Jan 2025 14:11:25 +0800
with message-id <51c98746-e00c-4eb6-8b03-dddb7c078...@debian.org>
and subject line Re: mdbook: FTBFS: build-dependency not installable:
librust-pulldown-cmark-escape-0.10+simd-dev
has caused the Debian Bug report #1091061,
regarding mdbook: FTBFS:
Hello James.
Okay, yes, I have the code in mumble-server.preinst slated for removal.
It looks like I can remove the whole file.
Thanks, I'll get this fixed.
-- Chris
Chris Knadle
chris.kna...@coredump.us
On 12/31/24 11:10, James Valleroy via Pkg-voip-maintainers wrote:
It looks like ther
Arnaud,
Could you prepare uploads of rust-libphosh-sys and rust-libphosh for
the new phosh to allow the new phosh to migrate?
Thank you,
Jeremy Bícha
Processing commands for cont...@bugs.debian.org:
> severity 1091218 serious
Bug #1091218 [src:rust-if-watch] rust-if-watch: Upcoming env_logger update to
v0.11
Severity set to 'serious' from 'normal'
> severity 1091219 serious
Bug #1091219 [src:rust-isahc] rust-isahc: Upcoming update to env_logge
Hi. I did a debbisect and this is what I found:
bisection finished successfully
last good timestamp: 20241224T143635Z
first bad timestamp: 20241224T203807Z
the following packages differ between the last good and first bad timestamp:
libopenzwave1.6-dev 1.6.1914+ds-1.2 -> 1.6.1914+ds2-1
li
Hey.
Did some debugging for an hour now, finding out that it works again
when changing in src/audio/ffmpeg_audio_processor_swresample.h the
following functions as given below:
void SetInputChannelLayout(AVChannelLayout *channel_layout) {
av_opt_set_chlayout(m_swr_ctx, "in_
Your message dated Wed, 1 Jan 2025 02:53:16 +0100
with message-id
and subject line Re: Bug#1060403: closed by Debian FTP Masters
(reply to gregor herrmann
) (Bug#1060403: fixed in libxml-hash-xs-perl 0.58-1)
has caused the Debian Bug report #1060403,
regarding libxml-hash-xs-perl: FTBFS on s390
On Wed, 2025-01-01 at 01:42 +0100, Sebastian Ramacher wrote:
> That's some sort of incompatibility with ffmpeg 7.0. But since
> upstream
> does not appear to be very active at the moment, at the worst case we
> will need to drop fpcalc.
I did some poor man's debugging, changed the call to av_log_s
Control: forwarded -1 https://github.com/acoustid/chromaprint/issues/142
Control: tags -1 upstream
On 2025-01-01 01:24:16 +0100, Christoph Anton Mitterer wrote:
> Package: libchromaprint-tools
> Version: 1.5.1-6
> Severity: grave
> Justification: renders package unusable
>
> Hey.
>
> I tried var
Processing control commands:
> forwarded -1 https://github.com/acoustid/chromaprint/issues/142
Bug #1091825 [libchromaprint-tools] libchromaprint-tools: fpcalc broken
(`ERROR: Could not create an audio converter instance (Invalid argument)`)
Set Bug forwarded-to-address to
'https://github.com/ac
Package: libchromaprint-tools
Version: 1.5.1-6
Severity: grave
Justification: renders package unusable
Hey.
I tried various files (WAV, FLAC, Opus), for all calculation fails with:
$ fpcalc *.opus
ERROR: Could not create an audio converter instance (Invalid argument)
Similarly, picard, when it i
Your message dated Wed, 01 Jan 2025 00:21:05 +
with message-id
and subject line Bug#1082338: fixed in yarsync 0.2.1-4
has caused the Debian Bug report #1082338,
regarding yarsync FTBFS with Python 3.13
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
On Mon, Dec 16, 2024 at 05:51:03PM +, Santiago Vila wrote:
> > dists = sorted(
> (d.metadata["Name"] for d in distributions()), key=len,
> reverse=True
> )
> E TypeError: object of type 'NoneType' has no len()
I've filed https://github.com/napar
Your message dated Wed, 01 Jan 2025 00:06:29 +
with message-id
and subject line Bug#1075629: fixed in vte 1:0.28.2-7
has caused the Debian Bug report #1075629,
regarding vte: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Tue, 31 Dec 2024 23:49:32 +
with message-id
and subject line Bug#1076908: fixed in pympress 1.8.5-2
has caused the Debian Bug report #1076908,
regarding pympress: FTBFS: Handler
for event 'builder-inited' threw an exception (exception: cannot unpack
non-iterable NoneType
Control: tag -1 pending
Hello,
Bug #1076908 in pympress reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/packages/pympress/-/commit/52842157982b36f4b
Processing control commands:
> tag -1 pending
Bug #1076908 [src:pympress] pympress: FTBFS: Handler for event 'builder-inited' threw an exception (exception:
cannot unpack non-iterable NoneType object)
Added tag(s) pending.
--
1076908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076908
D
Processing control commands:
> forwarded -1 https://github.com/ponyorm/pony/issues/729
Bug #1056435 [src:ponyorm] ponyorm's autopkg tests fail with Python 3.12
Changed Bug forwarded-to-address to
'https://github.com/ponyorm/pony/issues/729' from
'https://github.com/ponyorm/pony/issues/703'.
--
Control: forwarded -1 https://github.com/ponyorm/pony/issues/729
On Mon, Sep 02, 2024 at 05:08:11PM +0100, Colin Watson wrote:
> This looks like https://github.com/ponyorm/pony/issues/704. Does the
> latest upstream release (0.7.19) fare any better?
While 0.7.19 looks mostly OK on 3.12, it's bro
Processing control commands:
> tag -1 pending
Bug #1091125 [src:u-boot] u-boot: FTBFS:
scripts/dtc/pylibfdt/libfdt_wrap.c:5581:17: error: too few arguments to
function ‘SWIG_Python_AppendOutput’
Added tag(s) pending.
--
1091125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091125
Debian
Control: tag -1 pending
Hello,
Bug #1091125 in u-boot reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian/u-boot/-/commit/28c781ec718225393e7a55e0e964f42b2f7
Your message dated Tue, 31 Dec 2024 22:07:22 +
with message-id
and subject line Bug#1091580: fixed in libqalculate 5.4.0.1-2
has caused the Debian Bug report #1091580,
regarding kalk: FTBFS on i386: make: *** [debian/rules:6: binary] Error 2
to be marked as done.
This means that you claim tha
>From a preliminary investigation, it looks like this is being caused by
a maven-resolver version that's too old. The class mentioned,
NoopNamedLockFactory, doesn't appear to have been added until 1.7.0,
while Debian has 1.6.3.
I also noticed that pomegranate-clojure-java might also need a
mave
Your message dated Tue, 31 Dec 2024 19:27:02 +
with message-id
and subject line Bug#1089729: fixed in phpldapadmin 1.2.6.7-2
has caused the Debian Bug report #1089729,
regarding phpldapadmin: autopkgtest failure with php8.4
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 31 Dec 2024 19:21:12 +
with message-id
and subject line Bug#1090898: fixed in fast5 0.6.5-9
has caused the Debian Bug report #1090898,
regarding fast5: autopkgtest regressions with HDF5 1.14
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Tue, 31 Dec 2024 19:20:14 +
with message-id
and subject line Bug#1082047: fixed in audioread 3.0.1-2
has caused the Debian Bug report #1082047,
regarding audioread: FTBFS: E ModuleNotFoundError: No module named 'aifc'
to be marked as done.
This means that you claim that the
Your message dated Tue, 31 Dec 2024 19:20:14 +
with message-id
and subject line Bug#1082047: fixed in audioread 3.0.1-2
has caused the Debian Bug report #1082047,
regarding FTBFS with Python 3.13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Tue, 31 Dec 2024 19:20:14 +
with message-id
and subject line Bug#1082047: fixed in audioread 3.0.1-2
has caused the Debian Bug report #1082047,
regarding audioread: removal of Python standard libraries in Python 3.13
to be marked as done.
This means that you claim that the
Hello Jonas,
On Tue, 31 Dec 2024 16:59, Jonas Smedegaard wrote:
>Hi Manos,
>
>Thanks for caring about this downstream packaging of your project!
Always! Debian has been my distro since I was a young child learning
about computers and it will forever be in my heart :)
>
>Quoting Manos Pitsidian
Processing control commands:
> tags -1 patch
Bug #1075634 [src:wcc] wcc: ftbfs with GCC-14
Added tag(s) patch.
--
1075634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
--
On Wed, Jul 03, 2024 at 12:47:54PM +, Matthias Klose wrote:
> Package: src:wcc
> Version: 0.0.2+dfsg-4.4
> Severity: important
> Tags: sid trixie
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-14
>
> [This bug is targeted to the upcoming trixie release]
>
Control: severity -1 important
Control: merge -1 1080433
Thanks for reporting this bug. It has been reported before on another
architecture.
Merging.
-rt
Hi.
My apologies. I didn't read the original bug report from Lucas Nussbaum.
I detected that this package FTBFS, there was a closed FTBFS bug, so I reopened.
When Lucas tried to build it, the dependencies could not be installed.
Now they can, but the build still fails, this time with a differen
Processing control commands:
> severity -1 important
Bug #1091011 [src:golang-github-coreos-pkg] golang-github-coreos-pkg: FTBFS:
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8
github.com/coreos/pkg/capnslog github.com/coreos/pkg/cryptoutil
github.com/coreos/pkg/dlopen
Package: src:openzwave-controlpanel
Version: 1.6~git20200306.4b8a39d-1
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[ Note: This error looks that it might be some kind of Makefile bug,
so I'm adding this p
Package: src:golang-github-caarlos0-env
Version: 11.3.1-1
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules cle
Package: src:btm
Version: 0.10.2+20241128-1
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
failures:
utils::strings
Package: src:consensuscore
Version: 1.1.1+dfsg-7
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
SWIG_LIB=/usr/share/swig/
Package: src:node-luxon
Version: 3.4.4-2
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
(Note: This error looks that it may happen specifically on 31 December (today),
so if you try to reproduce it tomorrow an
Control: tag -1 pending
Hello,
Bug #1082047 in audioread reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/packages/audioread/-/commit/927b4d09eb5d517
Processing control commands:
> tag -1 pending
Bug #1082047 [src:audioread] FTBFS with Python 3.13
Bug #1084639 [src:audioread] audioread: removal of Python standard libraries in
Python 3.13
Bug #1090092 [src:audioread] audioread: FTBFS: E ModuleNotFoundError: No module
named 'aifc'
Added tag(s)
Processing commands for cont...@bugs.debian.org:
> reopen 1091061
Bug #1091061 {Done: Blair Noctis } [src:mdbook] mdbook: FTBFS:
build-dependency not installable: librust-pulldown-cmark-escape-0.10+simd-dev
Bug reopened
Ignoring request to alter fixed versions of bug #1091061 to the same values
reopen 1091061
thanks
Blair Noctis wrote:
it's due to pulldown-cmark{,-escape} being out of sync, not mdbook itself.
The error is like this:
error: failed to select a version for the requirement `pulldown-cmark = "^0.9"`
candidate versions found which didn't match: 0.10.3
So you are relying
Processing commands for cont...@bugs.debian.org:
> found 1091452 phoc/0.44.0-2
Bug #1091452 [phoc] Prevent testing migration
Marked as found in versions phoc/0.44.0-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1091452: https://bugs.debian.org/cgi-bin/bugrepo
Processing commands for cont...@bugs.debian.org:
> notfound 1091452 phoc/0.44~rc1-1
Bug #1091452 [phoc] Prevent testing migration
No longer marked as found in versions phoc/0.44~rc1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1091452: https://bugs.debian.or
Processing commands for cont...@bugs.debian.org:
> tags 1086477 ftbfs
Bug #1086477 [src:massif-visualizer] massif-visualizer: kdiagram transition
Added tag(s) ftbfs.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1086477: https://bugs.debian.org/cgi-bin/
Your message dated Tue, 31 Dec 2024 17:12:28 +
with message-id
and subject line Bug#1090752: fixed in slim 1.4.1-2
has caused the Debian Bug report #1090752,
regarding slim: moves the systemd unit back to /lib (DEP17)
to be marked as done.
This means that you claim that the problem has been d
Your message dated Tue, 31 Dec 2024 16:58:50 +
with message-id
and subject line Bug#1075409: fixed in pyliblo 0.16.2-1
has caused the Debian Bug report #1075409,
regarding pyliblo: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
severity 1091578 important
tags 1091578 unreproducible
thanks
Greetings, and thanks for your report! I just built the package
successfully in a freshly updated chroot on barriere. The build here
seems to have been on a machine with limited memory and with a peculiar
kernel oom policy -- GCL will
Processing commands for cont...@bugs.debian.org:
> severity 1091578 important
Bug #1091578 [src:maxima] maxima: FTBFS on i386: dpkg-buildpackage: error:
debian/rules build subprocess returned exit status 2
Severity set to 'important' from 'serious'
> tags 1091578 unreproducible
Bug #1091578 [src:
Processing control commands:
> fixed -1 xarray-safe-rcm/2024.11.0-1
Bug #1091801 [src:xarray-safe-rcm] xarray-safe-rcm: autopkgtest failure with
python-xarray 2024.11.0
Marked as fixed in versions xarray-safe-rcm/2024.11.0-1.
> close -1
Bug #1091801 [src:xarray-safe-rcm] xarray-safe-rcm: autopkgt
Source: xarray-safe-rcm
Version: 2024.02.0-1
Severity: serious
Tags: ftbfs
Justification: makes the package in question unusable or mostly so
Control: fixed -1 xarray-safe-rcm/2024.11.0-1
Control: close -1
Dear Maintainer,
The version of your package in testing FTBFS with python-xarray 2024.11.0,
Your message dated Tue, 31 Dec 2024 16:34:55 +
with message-id
and subject line Bug#1091258: fixed in gnushogi 1.5~git20140725-2.2
has caused the Debian Bug report #1091258,
regarding gnushogi: FTBFS on armhf: ../../gnushogi/book.c:905:32: error:
passing argument 1 of ‘time’ from incompatible
Your message dated Tue, 31 Dec 2024 16:35:05 +
with message-id
and subject line Bug#1090805: fixed in
golang-github-containers-gvisor-tap-vsocks 0.8.1-1
has caused the Debian Bug report #1090805,
regarding golang-github-containers-gvisor-tap-vsocks: tests calls home?
to be marked as done.
Th
It looks like there was a duplication of handling of the file being moved in
the package:
1. Using mv_conffile:
https://salsa.debian.org/pkg-voip-team/mumble/-/blob/debian/debian/mumble-server.maintscript?ref_type=heads
2. Custom code in mumble-server.preinst:
https://salsa.debian.org/pkg-voip-
Package: mumble-server
Version: 1.5.517-2.1
Severity: serious
Justification: Appendix 5.1
X-Debbugs-Cc: jvalle...@mailbox.org
Dear Maintainer,
* What led up to the situation?
On a clean image of Debian bookworm (debian/bookworm64 vagrant box), I
installed mumble-server 1.3.4-4. I did not ma
I am uploading a NMU to fix this.
The debdiff is attached.diff -Nru gnushogi-1.5~git20140725/debian/changelog
gnushogi-1.5~git20140725/debian/changelog
--- gnushogi-1.5~git20140725/debian/changelog 2023-08-10 21:39:21.0
+
+++ gnushogi-1.5~git20140725/debian/changelog 2024-12-31 1
Hi,
I'm re-assigning this bug to libqalculate-dev based on the high similarity with
#1077798 .
Moreover, diffoscope-ing between libqalculate-dev_5.3.0-1_i386.deb and
libqalculate-dev_5.4.0.1-1_i386.deb :
│ │ ├── ./usr/lib/i386-linux-gnu/pkgconfig/libqalculate.pc
│ │ │ @@ -1,12 +1,12 @@
│ │ │
Processing control commands:
> notfound 1077937 systemd-resolved/257.1-4
Bug #1077937 [avahi-daemon,systemd-resolved] avahi-daemon: WARNING: Detected
another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is
thus not recommended.
The source systemd-resolved and version 257.
Control: notfound 1077937 systemd-resolved/257.1-4
Control: reassign 1077937 avahi-daemon
As already mentioned, it is not acceptable to break my package (sd-
resolved) for the benefit of avoiding to ship a static config snippet
in another, as it's beyond trivial to do so, has zero negative
consequ
Processing commands for cont...@bugs.debian.org:
> tags 1077937 + sid trixie
Bug #1077937 [avahi-daemon,systemd-resolved] avahi-daemon: WARNING: Detected
another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is
thus not recommended.
Added tag(s) sid and trixie.
> thanks
St
Processing commands for cont...@bugs.debian.org:
> reassign 1091580 libqalculate-dev
Bug #1091580 [src:kalk] kalk: FTBFS on i386: make: *** [debian/rules:6: binary]
Error 2
Bug reassigned from package 'src:kalk' to 'libqalculate-dev'.
No longer marked as found in versions kalk/24.08.3-1.
Ignoring
Processing commands for cont...@bugs.debian.org:
> reassign 1077937 avahi-daemon,systemd-resolved
Bug #1077937 [avahi-daemon] avahi-daemon: WARNING: Detected another IPv4 mDNS
stack running on this host. This makes mDNS unreliable and is thus not
recommended.
Bug reassigned from package 'avahi-d
Hi Manos,
Thanks for caring about this downstream packaging of your project!
Quoting Manos Pitsidianakis (2024-12-31 13:50:01)
> I'm not familiar with the semantics here, is the Severity "serious"
> because it failed the entire build?
Yes (I didn't file this bug, but agree with its severity)
Hi Tony,
Le 2024-12-30 21:57, tony mancill a écrit :
Adding the missing B-D on libmaven-resolver-1.6-java resolves the FTBFS
for trixie. However, the build will still fail on unstable due to
libmaven3-core-java pulling in libmaven-resolver-java (1.9.x).
This can probably be solved with a bit
Hello,
(I'm the maintainer for upstream meli)
On Sun, 22 Dec 2024 11:29, Lucas Nussbaum wrote:
>Source: meli
>Version: 0.8.10+dfsg-1
>Severity: serious
I'm not familiar with the semantics here, is the Severity "serious"
because it failed the entire build?
Technically speaking this is a fail
On Wed, 03 Jul 2024 12:22:51 + Matthias Klose wrote:
Package: src:beav
Version: 1:1.40-18.4
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for
Processing commands for cont...@bugs.debian.org:
> close 1090207 1.7.1-1
Bug #1090207 [src:davfs2] davfs2: FTBFS: configure: error: could not find neon
Marked as fixed in versions davfs2/1.7.1-1.
Bug #1090207 [src:davfs2] davfs2: FTBFS: configure: error: could not find neon
Marked Bug as done
> th
close 1090207 1.7.1-1
thanks
--
Sebastian Ramacher
Processing commands for cont...@bugs.debian.org:
> forwarded 1091082 https://github.com/hikikomori82/osifont/issues/23
Bug #1091082 [fonts-osifont] fonts-osifont: debian/copyright is inaccurate
Set Bug forwarded-to-address to
'https://github.com/hikikomori82/osifont/issues/23'.
> thanks
Stopping
Your message dated Tue, 31 Dec 2024 11:19:19 +
with message-id
and subject line Bug#1091553: fixed in phoc 0.44.0-2
has caused the Debian Bug report #1091553,
regarding phoc: migrate to wlroots 0.18
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 31 Dec 2024 10:34:34 +
with message-id
and subject line Bug#1091354: fixed in gcc-15 15-20241231-1
has caused the Debian Bug report #1091354,
regarding lib32stdc++6-15-dbg, libstdc++6-15-dbg and libx32stdc++6-15-dbg have
an undeclared file conflict
to be marked as
I believe this is solved upstream
https://pagure.io/certmonger/c/a144529ce829ae6bed8607743c065c529ee5bf87?branch=master
As also seen in another issue - https://pagure.io/certmonger/issue/282
So all is needed is simply update Debian repo to pull in changes and make a
new package. Debian Tracker al
Source: uw-imap
Version: 8:2007f~dfsg-7
Severity: serious
It appears uw-imap upstream is long gone. It also appears that the
source is basically pre-Sys4, and will break again and again with
newer gcc versions.
If there was an active maintainer, this might be okay, but
apparently this is also not
Source: hyprland
Version: 0.41.2+ds-1.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
trying to build hyprland in unstable yields:
Install main build dependencies (apt-based resolver)
-
Processing commands for cont...@bugs.debian.org:
> reopen 1091452
Bug #1091452 {Done: Guido Günther } [phoc] Prevent testing
migration
Bug reopened
Ignoring request to alter fixed versions of bug #1091452 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if
Your message dated Tue, 31 Dec 2024 10:22:16 +
with message-id
and subject line Bug#1075612: fixed in uw-imap 8:2007f~dfsg-7.1
has caused the Debian Bug report #1075612,
regarding uw-imap: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 31 Dec 2024 10:05:51 +
with message-id
and subject line Bug#1090004: fixed in gcc-14-cross 8
has caused the Debian Bug report #1090004,
regarding gcc-14-cross: FTBFS with make 4.4.1
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Tue, 31 Dec 2024 10:06:00 +
with message-id
and subject line Bug#1089263: fixed in gcc-14-cross-ports 9
has caused the Debian Bug report #1089263,
regarding gcc-14-cross-ports: FTBFS with make 4.4.1
to be marked as done.
This means that you claim that the problem has been d
Checking the package again, the fonts with the license flavours are
generated during build and the license is applied at build time [1].
However, that means that the source of the font (osifont.sfd) has a unspecified
license.
osifont-italic.sfd, OTOH, has a copyright specified:
Copyright: Crea
Processing commands for cont...@bugs.debian.org:
> clone 1090833 -2
Bug #1090833 {Done: Tobias Frost } [freecad] freecad: ships
possibly non-free font ASME Y14.5
Bug 1090833 cloned as bug 1091771
> severity -2 normal
Bug #1091771 {Done: Tobias Frost } [freecad] freecad: ships
possibly non-free f
Your message dated Tue, 31 Dec 2024 08:36:50 +
with message-id
and subject line Bug#1090134: fixed in python-chameleon 4.5.4-2
has caused the Debian Bug report #1090134,
regarding python-chameleon: FTBFS: ERROR: Invalid value `None` in
intersphinx_mapping['https://docs.python.org/']. Expected
Hello everyone,
just adding some notes before this package gets autoremoved due to these
two RC bugs.
On Thu, Oct 31, 2024 at 06:01:17AM +0100, Patrick Franz wrote:
> We have updated kdiagram to version 3.0.1 in experimental. The biggest change
> is the port from Qt 5 to Qt 6, i.e. kdiagram 3.0.1
84 matches
Mail list logo
