On Fri, Apr 25, 2025, at 5:19 PM, Fabian Grünbichler wrote:
> I missed that the LLVM change was *only* done for 19 (and if the rustc
> with the raised/reverted baseline would have behaved unexpectedly, I might
> have realized sooner!).
and this 19 here should of course been an 18 (hopefu
On Fri, Apr 25, 2025, at 11:56 AM, Simon McVittie wrote:
> Control: retitle -1 llvm-toolchain-19: unsoundness/miscompilations on i386
> Control: block 1095863 by -1
>
> On Thu, 13 Feb 2025 at 07:51:29 +0100, Fabian Grünbichler wrote:
>>- Debian's i386 baseline is currently
On Mon, Apr 14, 2025, at 12:54 AM, Jonas Smedegaard wrote:
> Quoting Fabian Grünbichler (2025-04-12 16:13:42)
>> On Mon, Apr 7, 2025, at 9:37 AM, Jonas Smedegaard wrote:
>> > Quoting Jonas Smedegaard (2025-04-07 09:29:04)
>> > Possibly the cause of this issue is that the
On Mon, Apr 7, 2025, at 9:37 AM, Jonas Smedegaard wrote:
> Quoting Jonas Smedegaard (2025-04-07 09:29:04)
>> Package: librust-secret-service-dev
>> Version: 4.0.0-4
>> Severity: grave
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> Builds involving this package fails to build:
>>
x for python 3.12 compat (Closes: #1074250)
+
+ -- Fabian Grünbichler Tue, 11 Mar 2025
12:51:10 +0100
+
ifupdown2 (3.0.0-1.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru ifupdown2-3.0.0/debian/patches/bug-296-python-3.12-compability.patch
ifupdown2-3.0.0/debian/patches/bu
, and
proposed a fix upstream (see linked PR, which also contains a reproducer).
the packages in trixie and bookworm-backports should probably both be
updated, the fix is rather small and targeted ;)
thanks for your consideration!
Fabian
-- System Information:
Debian Release: trixie/sid
APT
Compiling serde v1.0.217
if my guess is correct, this regeneration step via gir is supposed to
recreate the auto module (see the comment up top in the files in that
directory), which includes removing it first. the module/dir is there
in the source package, but after the build has failed, it is missing
in the working tree. the error above happens right before the real rust
part of the build starts.
is there a difference in the gir parts that might be at fault?
Fabian
Am 2025-02-27 17:55, schrieb Fabian Greffrath:
Another package with a similar issue is/was libzip-dev, which needs all
of the zipcmp, zipmerge and ziptool packages installed for its CMake
rule to work: #1094641.
I have applied the same changes that fixed the issue in libzip to the
fluidsynth
Hi there,
Am Mittwoch, dem 26.02.2025 um 21:14 +0100 schrieb Fabio Pedretti:
> Adding in CC Fabian, who recently uploaded some update fluidsynth
> packages: do you maybe have any hints?
I have also seen this when preparing the packages for dsda-doom and
woof-doom. The CMake ru
have a strong preference for A).
Please keep responses on details of A) to the corresponding release.debian.org
bug!
Fabian
0:
https://salsa.debian.org/rust-team/rust/-/blob/debian/sid/debian/patches/behaviour/d-rustc-i686-baseline.patch?ref_type=heads
1:
https://salsa.debian.org/pkg-llvm-team/l
re-adding debian-mips@ and the bug ;)
> Matthias Geiger hat am 16.01.2025 11:55 CET
> geschrieben:
> On Thu, 16 Jan 2025 11:45, Simon McVittie wrote:
> >Source: librsvg
> >Version: librsvg/2.59.2+dfsg-1
> >Severity: serious
> >Tags: ftbfs
> >Justification: fails to build from source (but built
Am Donnerstag, dem 02.01.2025 um 12:51 +0100 schrieb rny:
> /bin/sh: 1: cd: can't cd to debian/tmp/usr/share/doc/ffmpeg
Well, you changed the prefix to /usr/local yourself, right?
- Fabian
signature.asc
Description: This is a digitally signed message part
On Sat, Dec 28, 2024, at 6:38 PM, Lucas Nussbaum wrote:
> Source: rustc
> Version: 1.83.0+dfsg1-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20241228 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package fa
Control: tag -1 pending
Hello,
Bug #1087824 in openal-soft 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/games-team/openal-soft/-/commit/84e2a728d5c91f19df554
On October 25, 2024 6:29:05 PM GMT+02:00, Simon McVittie
wrote:
>On Fri, 25 Oct 2024 at 16:24:40 +0200, Matthias Geiger wrote:
>> On Fri, 25 Oct 2024 10:41, Simon McVittie wrote:
>> > I don't know Rust, but this looks to me to be more like a problem with
>> > how `cargo test` is invoking the
8527c4fcfdf1a
Thanks again!
- Fabian
signature.asc
Description: This is a digitally signed message part
touch deutex-check` before the build and be done with it.
- Fabian
Maybe the `deutex -h` output to stdout get spoiled by other build steps
running in parralel, so that it doesn't include "PNG" as an isolated
word anymore?
- Fabian
FWIW, this change made rustc's (and notmuch's, see #1077911) build
dependencies unsatisfiable. they both have/had a dependency on gdb, and
a conflict on gdb-minimal, since the latter didn't provide all the
features required.
with the reversal of provides (gdb providing gdb-minimal instead of the
o
Hi Emmanuel,
Am Freitag, dem 12.07.2024 um 17:23 -0300 schrieb Emmanuel Arias:
> Please if you have any objection or you want to do any change please
> let
> me know.
no objections, please feel free to upload asap.
Thanks,
- Fabian
signature.asc
Description: This is a digital
need to Build-Depend on shared library packages
anyway? Why not the vamp-plugin-sdk package?
- Fabian
.rs:92:21
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> gmake[4]: ***
> [CMakeFiles/_corrosion_cbindgen_rust_lib_bindings.dir/build.make:74:
> corrosion_generated/cbindgen/rust_lib/include/rust-lib.h] Error 101
> gmake[4]: Leaving directory
> &
On Tue, Apr 23, 2024 at 07:51:36AM +0200, Helmut Grohne wrote:
> Hi Matthias,
>
> On Mon, Apr 22, 2024 at 10:34:11PM +0200, Matthias Geiger wrote:
> > This is the same situation as in #1040477. This is an issue wrt how we
> > generate the semvers. I image rust-proc-macro-crate-1 would pose the sam
On Thu, Dec 07, 2023 at 01:02:58AM +, Peter Green wrote:
> On the one hand I'm not at all convinced this bug is rc, on the other
> hand I don't think shipping a four year old version of env-logger
> in the next release of Debian is a great idea.
>
> So I decided to look at the reverse dependen
On Fri, Oct 27, 2023 at 07:55:07PM +0300, Adrian Bunk wrote:
> On Fri, Oct 27, 2023 at 05:07:12PM +0200, Fabian Grünbichler wrote:
> > On Wed, Oct 18, 2023 at 02:06:48PM +0300, Adrian Bunk wrote:
> > > Package: librust-env-logger-0.7+default-dev
> > > Severity:
On Wed, Oct 18, 2023 at 02:06:48PM +0300, Adrian Bunk wrote:
> Package: librust-env-logger-0.7+default-dev
> Severity: serious
>
> https://buildd.debian.org/status/fetch.php?pkg=mdevctl&arch=arm64&ver=1.2.0-4%2Bb3&stamp=1697626199&raw=0
>
> ...
> Merged Build-Depends: ..., librust-env-logger+defa
> Peter Green hat am 13.09.2023 05:24 CEST geschrieben:
> On 12/09/2023 23:30, Faidon Liambotis wrote:
> > Control: reassign -1 rustc 1.68.2+dfsg1-1
> > Control: retitle -1 Builds invalid wasm32 binaries (1.67->1.68 regression)
> >
> > On Tue, Sep 12, 2023 at 10:56:57PM +0100, Peter Green wrote:
>
On Sat, Jul 15, 2023 at 05:07:25PM +0200, Jonas Smedegaard wrote:
> Quoting Jonas Smedegaard (2023-07-15 09:55:04)
> > Quoting Fabian Grünbichler (2023-07-12 19:53:08)
> > > The feature in question is probably not a good candidate for packaging
> > > though, given the l
Why the severity? The fonts-liberation2 package is now a transitional package
which pulls in the actual fonts-liberation package. Von meinem/meiner Galaxy
gesendet
Why the severity? The fonts-liberation2 package is now a transitional package
which pulls in the actual fonts-liberation package. Von meinem/meiner Galaxy
gesendet
Do you have the heif-gdk-pixbuf package installed? Von meinem/meiner Galaxy
gesendet
d-1.12.0/debian/changelog
b/rust-async-std-1.12.0-patched/debian/changelog
index dfa43a8..5d6258f 100644
--- a/rust-async-std-1.12.0/debian/changelog
+++ b/rust-async-std-1.12.0-patched/debian/changelog
@@ -1,3 +1,9 @@
+rust-async-std (1.12.0-12.1) unstable; urgency=medium
+
+ * Non-maintainer uploa
On Thu, Jul 06, 2023 at 04:39:08PM +0100, Peter Green wrote:
> > I'd be very interested in knowing what this self-conflict is supposed to
> > achieve.
>
> It is common upstream for there to be multiple semver-incompatible versions
> of each rust crate in use at a given time. Incompatibilities can
Control: tag -1 pending
Hello,
Bug #1040360 in openal-soft 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/games-team/openal-soft/-/commit/cb8855883f5b91dc157fd
On Fri, Apr 28, 2023 at 08:42:07PM +0100, Peter Green wrote:
> On 28/04/2023 18:58, Fabian Grünbichler wrote:
> > I see no practical issue with 2 meaning we can't have multiple semver
> > suffix packages variants of a single crate installed - having the
> > unversi
On Fri, Apr 28, 2023 at 07:58:35PM +0200, Fabian Grünbichler wrote:
> 2) if the "fork point" corresponds to the version in the soon-to-be-old
> stable release, and the semver suffix package is still in testing when
> that becomes the stable release (as then the unversioned packa
as reference, the (simplified) problematic combination:
rust-foobar in version X.Y.Z-A
ships librust-foobar-dev which provides librust-foobar-X-dev,
librust-foobar-X.Y-dev and librust-foobar-X.Y.Z-dev (all in version
X.Y.Z-A)
is what I call the "unversioned" package in the rest of this mail (it
d
Hi!
I extracted one of the failing tests and the corresponding gdb commands
so that you can more easily (and quicker) reproduce the issue:
https://salsa.debian.org/fg/rustc-gdb-1031745
instructions are contained within as well. changing the triggering
function (multiple_arguments) to either just
Package: gdb
Version: 13.1-1
Severity: serious
Control: affects -1 src:rustc
Justification: breaks unrelated software
While preparing an update to rustc 1.65 for experimental, we noticed
that the recent gdb update in sid makes rustc FTBFS by causing 5 of its
gdb-integration test cases fail.
test
close 1024724 0.63.1-3
thanks
worked-around by temporarily skipping the two failing test cases - the
cause is actually in rustc, and should be fixed with rustc >= 1.63 which
in turn requires cargo >= 0.60 and is already waiting in experimental.
Am 21.10.2022 12:36, schrieb Tj:
I require mencoder specifically to handle some old legacy format
conversion where I found ffmpeg fails despite many attempts to work
around the issues with various command-line options.
Ever considered reporting these issues to the ffmpeg project?
- Fabian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
unblock 694320 by 694308
The fonts files in fonts-urw-core35 are not built by fontforge anymore.
- Fabian
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmMUfacACgkQy+qOlwzN
p to debian-devel for
the transition?
- Fabian
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmMKexQACgkQy+qOlwzN
Wd+l3xAA2hXXT0zFjuNnsyqJT9dY6eDrH0CFG8JhI21dkBBl/DBEAov8Mxdv/a7x
kZ683Vcx+5z4oa7ig4Ik7LGmTcRLdz0F023IG84a31UuWWEnt9IeWm5sFB1A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
@Jonas: Is the file /etc/ghostscript/fontmap.d/10fonts-urw-base35.conf
[1] even necessary now that the font files are directly symlinked in
the libgs9-common package?
Cheers,
- Fabian
[1]
https://salsa.debian.org/fonts-team/fonts-urw-base35
the transition works out for you as expected, that'd be
appreciated.
Thanks!
- Fabian
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmMKCiYACgkQy+qOlwzN
Wd/wnhAAwwgzhqlgOuioHah1qrqaNeJZIasP1oQ7uPFq6wKDkKSGSMP4pvR2rNSp
GHtdh+PzCij/5ADfEl8wEB0b3kkVmKhPPH8u
ed into the package into
src:fonts-urw-base35, turn the symlinking script into a
debian/fonts-urw-base35.links file and add the autopkgtests as well.
May I add you to Uploaders?
Cheers,
- Fabian
ional dummy package. It's
already team-maintained in pkg-fonts, so I'd like to invite you to move
efforts there. Or would you rather like to keep gsfonts-x11 as a
separate package?
Cheers,
- Fabian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 28 Jul 2022 10:21:17 +0200 Fabian Greffrath
wrote:
> > Maybe now is the time?
> Indeed my plan is to tackle this issue in about four weeks.
I currently despair of the format of the fonts.scale and fonts.alias
files that are pr
> Maybe now is the time?Indeed my plan is to tackle this issue in about four
> weeks. - Fabian Von meinem/meiner Galaxy gesendet
Ursprüngliche Nachricht Von: Chris Hofstaedtler
Datum: 28.07.22 01:02 (GMT+01:00) An: Fabian Greffrath
, 977...@bugs.debian.org Cc:
Control: tag -1 pending
Hello,
Bug #1008424 in flac 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/multimedia-team/flac/-/commit/4b4c810ca7d15b436c67f458687904
Control: tag -1 pending
Hello,
Bug #1008424 in flac 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/multimedia-team/flac/-/commit/b138df45a8dda1fc569e4f3ebccda8
On May 1, 2022 7:28 pm, Peter Michael Green wrote:
>
> On 01/05/2022 14:00, Fabian Grünbichler wrote:
>> currently progress is blocked on
>> - itoa/serde_json transition (anybody working actively on that?)
>
> I just uploaded the new itoa to experimental and took a q
On April 20, 2022 11:39 am, Fabian Grünbichler wrote:
> On April 20, 2022 12:33 am, Peter Michael Green wrote:
>> Package: rust-h2
>> Version: 0.1.26-1
>> X-debbugs-cc: d...@jones.dk
>>
>> I noticed that Jonas had set a number of bugs about broken rust packag
/bugreport.cgi?bug=788791
Have you restarted your desktop session after the fonts have been
upgraded?
- Fabian
On November 12, 2021 1:11 pm, Henry-Nicolas Tourneur wrote:
>
>
> Le ven 12 nov 2021 à 10:18, Fabian Grünbichler
> a écrit :
>> On November 12, 2021 6:38 am, Peter Green wrote:
>>> Package: rust-tokio-signal
>>> Version: 0.2.7-2
>>> Severit
On November 12, 2021 6:38 am, Peter Green wrote:
> Package: rust-tokio-signal
> Version: 0.2.7-2
> Severity: serious
>
> rust-tokio-signal (build-)depends on version 0.1 of rust-futures. Upstream
> seems to
> have abandoned the project, there was an alpha release supporting futures
> 0.2, but
>
On November 12, 2021 6:47 am, peter green wrote:
> In addition to the (build-)dependency on an old version of
> rust-crossbeam-queue,
> rust-tokio-process (build-)depends on version 0.1 of rust-futures. Upstream
> seems to
> have abandoned the crate, there was an alpha release supporting futures
own to
> only the format-security warnings.
thanks for your patch! I applied it (manually, since there were some
intermediate commits) in my repository:
https://git.fkurz.net/dj1yfk/qrq/commit/834e339ab387d5cab80ca259b4826719a240ccf2
tnx & 73
Fabian, DJ1YFK
--
Fabian Kurz, DJ1YFK
On August 31, 2021 9:16 pm, Wolfgang Silbermayr wrote:
> On 8/31/21 4:25 PM, Bastian Germann wrote:
>> On Wed, 2 Dec 2020 02:46:36 + peter green wrote:
>>> > This will impact quite some other modules.
>>>
>>> I agree that the current autoremoval list looks pretty scary, so I decided
>>> to do
On May 18, 2021 8:42 pm, Moritz Muehlenhoff wrote:
> Source: rust-hyper
> Severity: grave
> Tags: security
> X-Debbugs-Cc: Debian Security Team
>
> CVE-2021-21299:
> https://github.com/hyperium/hyper/security/advisories/GHSA-6hfq-h8hq-87mf
> https://rustsec.org/advisories/RUSTSEC-2021-0020.html
troduce a potentially
disruptive change like this.
Cheers,
- Fabian
PS: Also, please note that there is a third (outdated) copy of the same
fonts available in the texlive-fonts-recommended package which the TeX
people want to keep, though, for TeX reasons I guess.
On 1/11/21 3:45 AM, Stuart Prescott wrote:
>> In any case, I've changed my upload to a QA upload now and reuploaded
>> it to Salsa and Mentors.
>
> I see bartm beat me to uploading it.
Are you sure? I didn't receive any emails about an upload, and the
tracker doesn't say anything about a recent u
upload to a QA upload now and reuploaded
it to Salsa and Mentors.
Best,
Fabian
On 1/10/21 7:11 AM, Stuart Prescott wrote:
> Hi Fabian
>
> I see you've imported the package into the Debian Science Team area on salsa.
> Since xylib is orphaned, do you intend to adopt it and mai
does not follow a naming convention that isn't
even Debian policy?
Cheers,
- Fabian
signature.asc
Description: This is a digitally signed message part
ctory, which is
quite probably wrong.
- Fabian
Package: libvte-2.91-0
Version: 0.62.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After an upgrade of libvte gnome-terminal and other software using the library
(gedit terminal plugin) doesn't work.
Where the console should be there is some transparency and a effe
Control: tag -1 pending
Hello,
Bug #957394 in jumpnbump 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/games-team/jumpnbump/-/commit/7a3a913370edb1e176a2bcd191
Control: tags -1 confirmed pending fixed-upstream
Control: forwarded -1
https://github.com/coelckers/prboom-plus/commit/29320630c9ae878e537f451f173dbf9007d6786b
> plus.wad] Error 139
are these platforms cross-built? I am asking, because one step in
building prboom-plus is to compile a helper tool called "rdatawad" and
run this to combine several graphics and sound files into a data "wad"
file needed by the engine.
- Fabian
signat
#x27;t take the filename of the output file anymore.
- Fabian
Control: reopen -1
Control: found -1 1.98-1
Hi Sven,
Am 18.04.2020 07:50, schrieb Sven Joachim:
Since chocolate-doom was there first to ship the offending file, I
assume it should be removed from crispy-doom.
I'll take care of that with the next upload, thank you!
- Fabian
ava build profile that you suggested,
but again, I'm not familiar with this technique, and from what I've heard,
there are still some problems e. g. with using "dh-sequence-javahelper
". But if somebody gave me a patch, I'd be happy to apply it.
Thanks for your help!
Fabian
Control: tag -1 pending
Hello,
Bug #946474 in fluidsynth 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/multimedia-team/fluidsynth/commit/e50669e6b61747e300842
ld be better to unpackage said package version.
> Given that 4.8.6 is ready to be packaged thanks to the work of
> Fabian Wolff, it may be good to proceed with that.
thanks for pointing this out to me.
4.8.6 is ready and uploaded, but because it introduced the new python3-z3
package,
it's sti
Control: tag -1 pending
Hello,
Bug #941559 in xvidcore 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/multimedia-team/xvidcore/commit/57faa77ceeae42d6da6f87f65
issue now but not when xvidcore_2:1.3.5-1 was uploaded?
- Fabian
[1]
https://sources.debian.org/src/xvidcore/2:1.3.5-1/src/utils/x86_asm/cpuid.asm/?hl=94#L94
[2] https://sources.debian.org/src/xvidcore/2:1.3.5-1/src/nasm.inc/#L177
I saw that there was something wrong with the CI of libmurmurhash but
didn't have the time to look into it, yet. Thanks to Matthias for the
patch and to Andreas for releasing a new version so quickly.
Best,
Fabian
Am Donnerstag, den 29.08.2019, 09:54 -0400 schrieb Hugo Lefeuvre:
> Ack, I'll NMU then. Good luck with the baby :)
Thank you! \o/
- Fabian
signature.asc
Description: This is a digitally signed message part
Dear Hugo,
Am Donnerstag, den 29.08.2019, 08:04 -0400 schrieb Hugo Lefeuvre:
> Fabian (faad2 maintainer and upstream), do you want to handle this?
> Otherwise I can NMU a second time with this patch.
please go ahead with a second NMU. I am a bit short on time currently
(home alone with th
new—and
hopefully working—version to salsa. Could you sponsor another upload? I
will take a further look at the package next week.
Have a nice weekend
Fabian
xed the symbols file in Git. Please git pull.
>
While your at it, could you also push the tags? Thanks in advance
Fabian
he three hash functions is wrong, but at least
consistently wrong. I'll look into that.
Fabian
place. Also it should deactivate unit tests on 32bit while
at it. Could you take another look at the conditional?
Best
Fabian
1:
https://salsa.debian.org/med-team/mash/commit/42bf5484376d9b3e5ae4271f7d0e998ae0daac34
or an upload.
Best
Fabian
As promised, I pushed my packaging attempt. However, I didn't manage to
create a repository under med-team, thus it is under my account [1].
Best
Fabian
1: https://salsa.debian.org/kloetzl-guest/libmurmurhash
commit it to salsa tomorrow.
The upstream project just needs a bit more polishing (documentation,
better tests) before I would call it done.
Have a nice Sunday,
Fabian
1: https://github.com/kloetzl/libmurmurhash
Control: severity -1 normal
Hi Antonio,
thanks for the report, but I fail to see how a change in vertical
spacing could justify grave severity for a font package.
- Fabian
signature.asc
Description: This is a digitally signed message part
FWIW, this was reported upstream[0], and fixed[1], and released as part
of 1.5.0a. Either backporting the relevant changes from PR 434 or
updating to 1.5.0(a) seems like a good idea.
0: https://github.com/tmux-python/tmuxp/issues/433
1: https://github.com/tmux-python/tmuxp/pull/434
2: https://gith
sense to create a libmurmurhash package and then
have all "bad" implementations link against that. I will look at some
oof the code and start a project.
Best,
Fabian
forwarded 918566 https://github.com/marbl/Mash/issues/106
thanks
/different results.)
Fabian
1:
https://github.com/marbl/Mash/blob/aabd5925e7cfc097a8d89e2d8691ac4af5b95d37/src/mash/MurmurHash3.cpp#L52
(0x204)
> uni0023 touch 0,1,2,3,18,19,20,21,22,23,24,25,26,27,28,31 x 0.25 @
> 13
> ^
> Unable to execute ttfautohint on the Hack-Regular variant set. Build
> canceled.
> make[2]: *** [Makefile:26: ttf] Error 1
I have just successfully rebuilt the package in a sid chroot
o execute ttfautohint on the Hack-Regular variant set. Build
> canceled.
Oh, but what would be the right glyph name? Maybe the fontmake maintainers
can help out here?
Cheers,
- Fabian
.
Fabian
1: https://github.com/rambaut/figtree/issues/128
Thank you for reporting. I added a fix to the repo. Will get resolved
with the next upload.
Best
Fabian
Package: tmuxinator
Version: 0.12.0-1
Severity: serious
Justification: Policy 3.5
any tmuxinator command prints the following trace:
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot
load such file -- xdg (LoadError)
from /usr/lib/ruby/2.5.0/rubygems/core_ex
fixing in theseus.
Unfortunately, fixing this will take a while longer. I first have to
figure out how to build an arm vm because I don't want to debug remotely
via the autobuilds. ☺
Best,
Fabian
Package: pcb-rnd
Version: 2.0.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Trying to launch pcb-rnd I get the following output on the terminal:
Error in lihata node /usr/share/pcb-rnd/pcb-conf.lht:119.0:Invalid numeric
value: 2.2
Error in lihata node /us
ug [1, 2]. Temporarily deactivating -ffast-math or
-Werror should help to move on, nonetheless.
Best,
Fabian
1: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86835
2: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897876
1 - 100 of 433 matches
Mail list logo
