On June 18, 2025 5:28:25 PM GMT+02:00, Samuel Thibault
wrote:
>Hello,
>
>Fabian Grünbichler, le mer. 18 juin 2025 17:01:55 +0200, a ecrit:
>> full debdiff dropping R³ attachted as well.
>>
>[...]
>> only set it in debian/rules via chown u+s
>
>This part s
currently),
but should actually fail the build.
I also noticed that the setuid binaries are not setuid in the udebs, which
might be worthy of a separate fix - but I don't know anything about hurd, so
I'll leave that to you :)
thanks for your consideration,
Fabian
-- System Informati
Package: libdpkg-perl
Version: 1.22.20
Severity: minor
X-Debbugs-Cc: f.gruenbich...@proxmox.com
Hi!
Building a packge using
Rules-Requires-Root: debhelper/upstream-make-install
using sbuild will print a warning about $keywords_base being
uninitialized:
Use of uninitialized value $keywords_bas
minutes.
right, unfortunately, grub-invaders strictly requires a legay BIOS
system to start properly.
However, there is an alterative way to start it by using qemu which I
have pointed out in the README.Debian file.
- Fabian
On Sun, Jun 1, 2025, at 4:34 PM, наб wrote:
> Source: rust-b3sum
> Severity: minor
> Control: affects -1 src:rust-blake3
>
> Dear Maintainer,
>
> src:rust-blake3 consists of the whole upstream BLAKE3 distribution,
> incl. b3sum;
it does not - that's only the case in upstreams git repository/cargo
On Sun, Jun 1, 2025, at 4:29 PM, наб wrote:
> Source: rust-blake3
> Severity: wishlist
>
> Dear Maintainer,
>
> Upstream distributes libblake3 in c/,
> this should be easily buildable with dh_auto_build --sourcedir c &c.
>
> Please distribute this. A quick DCS query
>
> http://codesearch.debian.
On May 27, 2025 7:58 pm, Thomas Lange wrote:
> Hi,
>
> this bug also affects more packages that are not in the reverse dependency.
> Several packages call dhclient and sometimes with options that are
> only available for the isc dhcp client, like -lf ,-pf, -sf
>
> Following packages may be affect
On Fri, May 30, 2025, at 11:13 PM, Stefan Monnier wrote:
>>>I just confirmed now that downgrading to the version of `sqv` in
>>>Debian stable (which also downgraded `apt` and `apt-utils`) brings the
>>>system back to a usable state.
>>
>> The architecture baseline for i386 was raised.
>
> According
Package: wnpp
Followup-For: Bug #1038942
X-Debbugs-Cc: magic...@legoutdulibre.com
RustDesk current version is now 1.4.0.
A Debian/Ubuntu package is available here for x86-64 (64-bit) and AArch64
(ARM64):
https://github.com/rustdesk/rustdesk/releases/tag/1.4.0
There is also a changelog there.
S
t needs to be
rebuilt to pick up the fix. I've (manually) verified such a rebuilt package
fixes the referenced bug.
Thanks!
Fabian
ease cycle.
- Fabian
On Wed, 21 May 2025 22:23:04 +0200 "Andrea Pappacoda" wrote:
> Package: fragments
> Version: 3.0.1-8
> Severity: serious
>
> Hi!
>
> It seems that the fragments package is currently completely unusable, as
> it doesn't work even when no transmission-daemon is running system-wide.
>
> At the ti
ix the issue? That'd be the default buffer size on Windows.
Thanks!
- Fabian
signature.asc
Description: This is a digitally signed message part
On May 21, 2025 7:03:03 PM GMT+02:00, Andrey Feofilaktov
wrote:
>The diff I've shown before is a result of the build on a clean trixie machine.
>
>You show the diff in rust-glib, that is not the problem I pointed out.
Like I said - for me the rust-glib build (with a freshly re-built
librust-
On Wed, May 21, 2025, at 5:43 PM, Andrey Feofilaktov wrote:
> Hey Matthias,
>
> I tried to reproduce it, and it is true that on a raw trixie it is not
> reproducible as is.
>
> However, it would be if librust-gobject-sys-dev would have been built
> from source that is uploaded. That does not seem
adding the line
OTHER_OPTS='-z8192'
to /etc/default/fluidsynth help with this issue?
Cheers,
- Fabian
-1,3 +1,27 @@
+rust-rustix (0.38.37-4) unstable; urgency=medium
+
+ * Team upload.
+ * Package rustix 0.38.37 from crates.io using debcargo 2.7.8
+ * one more vdso test fix
+
+ -- Fabian Grünbichler Wed, 14 May 2025
16:37:22 +0200
+
+rust-rustix (0.38.37-3) unstable; urgency=medium
+
+ * T
On May 13, 2025 5:08:42 AM GMT+02:00, Peter Green wrote:
>Package: rust-rustix
>Version: 0.38.37-2
>Severity: serious
>
>The autopkgtests for rust-rustix are failing on i386.
>
>> 1337s backend::vdso::test_vdso stdout
>> 1337s 1337s thread 'backend::vdso::test_vdso' panicked at
>> sr
On Fri, May 2, 2025, at 1:16 PM, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
>
> On 2025-04-24 08:20:50 +0200, Fabian Grünbichler wrote:
>> On Thu, Apr 24, 2025 at 07:29:27AM +0200, Fabian Grünbichler wrote:
>> > On Thu, Apr 24, 2025, at 2:13 AM, Peter Green wr
control: found -1 0.13.0-2
Am Dienstag, dem 29.04.2025 um 10:40 +0200 schrieb okgomdjgbmoij:
> It should be a recommends so that you aren't forced to install the
> debian engine. They are a zillion forks of the engine.
I see, I'll change this.
- Fabian
signature.asc
Descri
control: tags -1 +upstream
control: forwarded -1 https://github.com/freedoom/freedoom/issues/1500
On Sat, Apr 26, 2025, at 4:19 PM, Helmut Grohne wrote:
> On Sat, Apr 26, 2025 at 10:55:57AM +0200, Paul Gevers wrote:
>> Control: tags -1 moreinfo
>
> I intentionally leave moreinfo in place as I hope for a better answer
> from Fabian.
>
>> Which set are we talking a
Control: tags -1 - moreinfo
On Sat, Apr 26, 2025, at 10:55 AM, Paul Gevers wrote:
> Control: tags -1 moreinfo
>
> Hi,
>
> On 25-04-2025 17:28, Fabian Grünbichler wrote:
>> I agree with that in principle, but would still like RT's input on that given
>> the amount
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: ru...@packages.debian.org, debian-r...@lists.debian.org,
debian@fabian.gruenbichler.email
Control: affects -1 + src:rustc
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package rustc
[ Reason ]
The update
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 Wed, Apr 23, 2025, at 9:44 PM, Helmut Grohne wrote:
> Hi Fabian,
>
> On Wed, Apr 23, 2025 at 08:21:48PM +0200, Fabian Grünbichler wrote:
>> [ Reason ]
>> until the version desired to be unblocked, debcargo defaulted to generating
>> packages shipping executables (&
upstream released 1.31 today, which solves this issue by
downgrading the log level of the problematic messages.
it also contains (only) one other targeted fix, so I'd
recommend upgrading to that version for Trixie :)
thanks!
On Thu, Apr 24, 2025 at 07:29:27AM +0200, Fabian Grünbichler wrote:
> On Thu, Apr 24, 2025, at 2:13 AM, Peter Green wrote:
> >>
> >> If preferred, a variant of the proposed changes with a default of "no"
> >> would
> >> also be possible
> &g
On Thu, Apr 24, 2025, at 2:13 AM, Peter Green wrote:
>>
>> If preferred, a variant of the proposed changes with a default of "no" would
>> also be possible
>
> I think the default (for bin packages) should be not to generate a multi-arch:
> field at all.
>
> This is behaviorally equivalent to mult
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: rust-debca...@packages.debian.org, debian-r...@lists.debian.org,
debian@fabian.gruenbichler.email
Control: affects -1 + src:rust-debcargo
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package rust-debcargo
On Wed, Apr 16, 2025, at 8:50 PM, Matt Corallo wrote:
> On 4/14/25 2:15 PM, Fabian Grünbichler wrote:
>>>> That's not really possible/in scope for Debian..
>>>
>>> I don't see why? Debian already ships libstd-rust-dev-windows as well
>>> as gcc p
On Thu, 17 Apr 2025 08:49:16 +0200 Paul Gevers wrote:
> Control: severity -1 important
> Control: block -1 by 1095862
>
> On Mon, 14 Apr 2025 13:41:30 +0200 Lucas Nussbaum wrote:
> > Source: rust-wide
>
> > > cargo:warning=Compiling optimized code on Debian non-SSE2 i686
> > > architecture l
On Sun, Apr 13, 2025, at 9:45 PM, Matt Corallo wrote:
> On 4/7/25 3:47 PM, Fabian Grünbichler wrote:
>> That's bookworm, the version with the fix came later, Trixie/did ship the
>> Cargo.lock file:
>
> Ha, apologies, I'd filed this against the wrong version. Glad i
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
> Lucas Nussbaum hat am 14.04.2025 14:36 CEST geschrieben:
>
>
> Hi Sebastian,
>
> On 14/04/25 at 11:54 +, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> >
> > > severity 1103109 important
> > Bug #1103109 [src:rust-imagepipe] rust-imagepipe: FT
: 12.04.25 19:03 (GMT+07:00) An: Debian
Bug Tracking System Betreff: Bug#1102742: eureka: it
looks like eureka could be rebuilt against fltk1.4 Source: eurekaVersion:
2.0.2-1Severity: normalX-Debbugs-Cc: Stephen Kitt , Fabian
Greffrath I've seen the new Fltk1.4 support Wayland.And I
: 12.04.25 19:03 (GMT+07:00) An: Debian
Bug Tracking System Betreff: Bug#1102742: eureka: it
looks like eureka could be rebuilt against fltk1.4 Source: eurekaVersion:
2.0.2-1Severity: normalX-Debbugs-Cc: Stephen Kitt , Fabian
Greffrath I've seen the new Fltk1.4 support Wayland.And I
Package: libknet1t64
Version: 1.30-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: debian@fabian.gruenbichler.email
Hi!
libknet1 1.30 contains a patch that attempts to detect certain invalid network
setups[0]. unfortunately, it also triggers on some (somewhat) valid ones, with
no option to select
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:
>>
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: ru...@packages.debian.org, debian-r...@lists.debian.org,
debian@fabian.gruenbichler.email
Control: affects -1 + src:rustc
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package rustc
[ Reason ]
See https:/
On April 7, 2025 8:57:56 PM GMT+02:00, Matt Corallo
wrote:
>
>
>On 4/7/25 2:13 PM, Fabian Grünbichler wrote:
>> Version: 1.82.0+dfsg1-1
>>
>> On Mon, Apr 7, 2025, at 3:31 PM, Matt Corallo wrote:
>>> Package: src:rustc
>>> Version: 1.63.0+dfsg1
nd I'll update
that page.
Thanks,
Fabian
I wonder what reasons people still have nowadays to install packages from
dmo?Von meinem/meiner Galaxy gesendet
Ursprüngliche Nachricht Von: jman Datum:
05.04.25 23:03 (GMT+01:00) An: sub...@bugs.debian.org Betreff: Bug#1102164:
libavcodec: build version 61.19.101 incompatibl
I wonder what reasons people still have nowadays to install packages from
dmo?Von meinem/meiner Galaxy gesendet
Ursprüngliche Nachricht Von: jman Datum:
05.04.25 23:03 (GMT+01:00) An: sub...@bugs.debian.org Betreff: Bug#1102164:
libavcodec: build version 61.19.101 incompatibl
v1 are already gone anyway.
- Fabian
signature.asc
Description: This is a digitally signed message part
t-debcargo (2.7.8-3) unstable; urgency=medium
+
+ * Package debcargo 2.7.8 from crates.io using debcargo 2.7.8
+ * Uplaod to unstable
+
+ -- Fabian Grünbichler Fri, 04 Apr 2025
19:17:48 +0200
+
+rust-debcargo (2.7.8-2) experimental; urgency=medium
+
+ * Package debcargo 2.7.8 from crates.io u
th RC severity against it requesting the fonts to be rebuilt from
sources, but tag that bug with trixie-ignore.
Cheers,
- Fabian
On Fri, Mar 28, 2025, at 1:48 AM, Jordan Justen wrote:
> I guess it is starting to look like libgit2 1.9 is not going to make
> it in for the next release.
@pochu - any input on that? if we postpone this transition to forky, I'd likely
prepare an update of rustc 1.85.1 soon (small regression foll
On March 28, 2025 1:48:39 AM GMT+01:00, Jordan Justen
wrote:
>On 2025-03-16 23:57:33, Fabian Grünbichler wrote:
>> still open on the rust side:
>> - rust-sequoia-git (currently being updated for other reasons,
>> compat change committed to git so that the next upload s
re of uploading and any follow-up work needed.
Fabian
On Sat, 13 Jul 2024 23:14:42 + =?UTF-8?Q?Daniel_Martin?=
wrote:
> OTHER_OPTS='-z8192'
Increasing the buffer size from 64 to 8192 is probably a bit drastic.
The default value for Windows is 512. Would that work for you as well?
- Fabian
signature.asc
Description: This i
On Thu, Mar 13, 2025, at 9:43 PM, Fabian Grünbichler wrote:
> On Thu, Mar 13, 2025, at 5:59 PM, Timo Röhling wrote:
>> Hi,
>>
>> * Emilio Pozuelo Monfort [2025-03-13 16:18]:
>>>How are the API breaks in this release? Did you rebuild the rdeps
>>>agains
Am Donnerstag, dem 13.03.2025 um 11:58 +0100 schrieb Sebastian
Ramacher:
> The -extra meta package is there to help users to get the
> -extra variants where they exist. But
Could you reveal the second half of the last sentence, please?
- Fabian
signature.asc
Description: This is a dig
On Thu, Mar 13, 2025, at 5:59 PM, Timo Röhling wrote:
> Hi,
>
> * Emilio Pozuelo Monfort [2025-03-13 16:18]:
>>How are the API breaks in this release? Did you rebuild the rdeps
>>against the new version? I'm all for updating libgit2, but only if it
>>doesn't break half the rdeps.
> There are thr
Am 2025-03-13 11:58, schrieb Sebastian Ramacher:
Please don't. I don't think that we should support this use case in the
archive.
Hmkay.
The -extra meta package is there to help users to get the
-extra variants where they exist. But
Now it got interesting... ;)
- Fabian
Am 2025-03-11 15:46, schrieb Martin-Éric Racine:
Welcome. Has there been any progress on this?
Nope, but I'd volunteer to work on this.
What name scheme do you suggest for the packages, libav*-nonextra or
libav*-regular or anything else?
- Fabian
Is there any specific reason why this package doesn't follow the usual "Debian
unstable first, then merge to Ubuntu" development cycle? - FabianOn Sat, 1 Mar
2025 17:38:43 +0100 Till Kamppeter wrote:> It should
be easy, just porting over the current Ubuntu package, >
3.24.4+dfsg0-0ubuntu4.> >
wrote:
> The options as I see them, *including* the options that I would personally
> prefer to rule out, are:
>
> - Status quo: don't change anything. As Fabian says, Rust code on i386
> will sometimes be miscompiled and might crash.
I can live with this, provided we ra
control: tags -1 forwarded https://github.com/FluidSynth/fluidsynth/pull/1499
signature.asc
Description: This is a digitally signed message part
!
thanks,
Fabian
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64
Kernel: Linux 6.12.17-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (cha
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
upstream.
https://github.com/FluidSynth/fluidsynth
Thanks!
- Fabian
Am Freitag, dem 07.03.2025 um 20:22 + schrieb Bjarni Ingi Gislason:
> Package: fluidsynth
> Version: 2.4.3+dfsg-4
> Severity: minor
> Tags: patch
>
> * What led up to the situation?
>
> Che
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
aware of to decide whether to go ahead
(and potentially overshoot the toolchain freeze migration-wise for a few
days) or not.
thanks,
Fabian
t repo (similar to how "-b branch" is optionally allowed to
specify a non default branch)..
Maybe reassign to debcheckout? ;)
Regards,
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
Am Freitag, dem 21.02.2025 um 12:23 +0100 schrieb Emilio Pozuelo
Monfort:
> The transition just started; it's not closed with the package upload.
Sorry, I'm not involved into library transitions that often. ;)
- Fabian
signature.asc
Description: This is a digitally signed message part
ay succeed, or fail later due to an actual
issue (flac related or not).
It seems that both build failures are triggered by an attempt to run
python in the schroot.
In any case, given the good results so far, we can go ahead with this.
Does this mean I my upload 1.5.0+ds-2 to unstable now?
- Fabian
here:
https://people.debian.org/~fabian/buildlogs/
Cheers,
- Fabian
ne to the new flac package. That's gmerlin-encoders, which
apparently fails to detect the new flac version and thus does not build its
plug, which is then missing from the packaging.
Woudl you like me to include the build logs here?
Cheers,
- Fabian
signature.asc
Description: This
x27;t check myself)?
I asked to know if any of the tools used to generate the variable font
were known to produce irreproducible results. This does't seem to be the
case, though :/
- Fabian
from the FLAC transition?
Cheers,
- Fabian
Am 2025-02-18 20:06, schrieb Paul Gevers:
The upload of 0.303.1-3 changed the state of fonts-cantarell on the
reproducibility project infrastructure from being reproducible to being
not reproducible.
Ouch! Any idea what may be the root cause of this regression?
- Fabian
Am 2025-02-18 10:42, schrieb Emilio Pozuelo Monfort:
Do the rdeps build fine against the new version?
From the API changes, I expect yes. Is there any reasonable/automated
way how I can test all of its rdeps?
- Fabian
iph.org/flac/api/group__porting__1__4__3__to__1__5__0.html
Thanks!
Cheers,
- Fabian
Ben file:
title = "flac";
is_affected = .depends ~ "libflac++10" | .depends ~ "libflac12t64" | .depends ~
"libflac++11" | .depends ~ "libflac14";
is_good = .depends ~ &q
Thanks!
- Fabian
On Sun, Feb 16, 2025 at 12:15:31PM +0100, Guillem Jover wrote:
> Package: dh-cargo
> Version: 31
> Severity: normal
> Tags: patch
>
> Hi!
>
> Prompted by a discussion about lintian warnings about
> Static-Built-Using usage (via Holger Levsen), I realized that dh-cargo
> was most probably not usin
Unstable/Testing now.
Will do so, thank you!
- Fabian
signature.asc
Description: This is a digitally signed message part
On Thu, Feb 13, 2025 at 05:41:12PM +0100, Samuel Thibault wrote:
> Simon McVittie, le jeu. 13 févr. 2025 16:32:30 +, a ecrit:
> > The options as I see them, *including* the options that I would personally
> > prefer to rule out, are:
> >
> > - Status quo: don't
On Thu, Feb 13, 2025 at 12:35:51PM +0100, Matthias Klose wrote:
> I don't think such changes should be made a few weeks before a freeze, or if
> that change should be made at all. This is a discussion that should be made
> during the freeze and then implemented at the start of the next release
> cy
On Thu, Feb 13, 2025 at 11:37:53AM +0100, Samuel Thibault wrote:
> Fabian Grünbichler, le jeu. 13 févr. 2025 10:39:00 +0100, a ecrit:
> > On Thu, Feb 13, 2025 at 09:24:02AM +0100, Samuel Thibault wrote:
> > > Fabian Grünbichler, le jeu. 13 févr. 2025 08:11:14 +0100, a ecri
On Thu, Feb 13, 2025 at 09:24:02AM +0100, Samuel Thibault wrote:
> Hello,
>
> Fabian Grünbichler, le jeu. 13 févr. 2025 08:11:14 +0100, a ecrit:
> > A mixed approach (raising the baseline to allow LLVM and rustc to bump
> > their targets, but keeping GCC's default targe
On Tue, 4 Feb 2025 23:10:15 +0100 Samuel Thibault wrote:
> Samuel Thibault, le mar. 04 févr. 2025 12:09:57 +0100, a ecrit:
> > Paul Gevers, le mer. 26 avril 2023 22:09:53 +0200, a ecrit:
> > > We discussed this during the Release Team IRC meeting [1]
> > > http://meetbot.debian.net/debian-release/
heory, LLVM as well, but I will of course defer to the respective
team's opinion on that) for Trixie after all. Any further input that
might help get this unstuck highly appreciated.
I am sorry that this came up this late in the release cycle, and that I
didn't push faster between November an
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
l prepare a package and upoad it to experimental for the time
being.
Thanks!
- Fabian
signature.asc
Description: This is a digitally signed message part
e/blob/2e5bbdc933e125332ee0cdc6d74dabf1f90bb0f4/fontforge/plugin.c#L288
- Fabian
signature.asc
Description: This is a digitally signed message part
Am 2025-02-04 12:54, schrieb Amr Ibrahim:
Could a variable font be built?
Sure! The question is rather if we want the variable font to replace the
static ones or if we want it in addition to the static fonts?
- Fabian
dency.
without this package installed, the following warning appears during
the build with the most current fontforge package:
```
Core python package 'pkg_resources' not found: Cannot discover plugins
```
This sounded severe enough to me to justify the Build-Depends.
Cheers,
g and outdated advice on this way), just to end up
with the exact same conclusion: install the steam-devices package.
Thanks!
- Fabian
ge is already installed.
But, to be honest, if you already share your computer hardware and
access at the system console with a malicious user, there may be way
more obvious ways to get attacked than through the steam-devices
package, right?
Cheers,
- Fabian
!
- Fabian
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.10-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=d
Package: libsdl2-2.0-0
Version: 2.30.11+dfsg-1
Severity: wishlist
Hi,
for the same reason outlined in #1094934.
Also applies to libsdl3-0, btw.
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd
On Mon, Jan 27, 2025, at 11:34 AM, Emilio Pozuelo Monfort wrote:
> On 04/10/2024 15:04, Fabian Grünbichler wrote:
>> Depending on how the freeze timeline looks like, I see a few options:
>> - freeze date for toolchain/key packages is after 2025-02-20, such that a
>> regula
Hi Jeremy,
Am Sonntag, dem 19.01.2025 um 15:21 -0500 schrieb Jeremy Bícha:
> We had talked earlier about possibly packaging the new GNOME default
> font as a separate binary package from source fonts-inter.
isn't this rather an ITP or RFP than a wishlist bug for fonts-inter?
On January 22, 2025 9:35 am, Fabian Grünbichler wrote:
> On January 22, 2025 9:00 am, Fabian Grünbichler wrote:
>> On September 20, 2024 7:05 pm, Thomas Lamprecht wrote:
>>> Package: libtemplate-perl
>>> Version: 2.27-1
>>> Severity: wishlist
>>>
On January 22, 2025 9:00 am, Fabian Grünbichler wrote:
> On September 20, 2024 7:05 pm, Thomas Lamprecht wrote:
>> Package: libtemplate-perl
>> Version: 2.27-1
>> Severity: wishlist
>> X-Debbugs-Cc: Benj. Mako Hill
>>
>> Dear Maintainer,
>>
&g
1 - 100 of 2178 matches
Mail list logo
