On Tue, Aug 05, 2025 at 01:34:19PM +0100, Julian Gilbey wrote:
> On Tue, Aug 05, 2025 at 12:34:59PM +0200, Fabian Grünbichler wrote:
> > [...]
> > > That's good to know. I also doubt there's much local reliance on
> > > those, given how little they'
On Tue, Aug 05, 2025 at 09:54:35AM +0100, Julian Gilbey wrote:
> On Tue, Aug 05, 2025 at 12:48:58AM +0200, Guillem Jover wrote:
> > > I would therefore propose changing the Static-Built-Using field to use
> > > *binary* packages and versions rather than *source* packages and
> > > versions to fix t
On August 4, 2025 3:55:56 PM GMT+02:00, Chris Hofstaedtler
wrote:
>On Mon, Aug 04, 2025 at 02:40:07PM +0100, Julian Gilbey wrote:
>> Hi!
>> > +::
>> > +
>> > +Built-Using: rust-pulsectl-rs (= 0.3.2-1+b1)
>> > +Static-Built-Using: rust-gtk4 (= 0.7.3-3), rust-pulsectl-rs (=
>> > 0.3.2-1
On July 31, 2025 10:40 pm, Bernhard Schmidt wrote:
> On 27/03/25 02:14 PM, Fabian Grünbichler wrote:
>
> Hi,
>
>> would it be okay for you if I imported the current version in the
>> archive to salsa (in a namespace of your choice?) and prepare an upload
>> with the
Control: tags -1 patch
verified that the attached patch makes the postinst handle this
situation gracefully
From 62a2a00f3e32614b4d3251150149a66ad8e2d2f1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?=
Date: Thu, 31 Jul 2025 09:39:33 +0200
Subject: [PATCH] systemd-boot: fix p
Package: systemd-boot
Version: 257.7-1
Severity: normal
X-Debbugs-Cc: f.gruenbich...@proxmox.com
Hi!
on a system with systemd-boot-efi installed (and not it's signed counterpart),
but shim-signed installed, systemd-boot's postinst will fail every other time
if the ESP is not mounted.
I used rein
Control: tags -1 pending
On Sat, 26 Jul 2025 08:49:05 +0200 Fiona Ebner wrote:
> Control: tags -1 patch
>
> Hi,
>
> I submitted a merge request to address the issue:
> https://salsa.debian.org/linux-blocks-team/targetcli-fb/-/merge_requests/12
>
> However, I noticed that the Salsa repository d
On July 25, 2025 11:15:45 AM GMT+02:00, Bastian Blank wrote:
>Package: rustc
>Version: 1.85.0+dfsg3-1
>Severity: normal
>X-Debbugs-Cc: wa...@debian.org
>
>rustc currently depends on gcc and binutils. This means it wants the
>native compiler and will break if a cross compiler for this arch is
>alr
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: targetcli...@packages.debian.org, f.eb...@proxmox.com,
debian@fabian.gruenbichler.email
Control: affects -1 + src:targetcli-fb
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package targetcli-fb
[ Reason ]
On Tue, 29 Apr 2025 09:53:53 +0200 John Paul Adrian Glaubitz
wrote:
> Hello Jing,
>
> On Tue, 2025-04-29 at 07:33 +, Jing Luo wrote:
> > rustc now FTBFS on powerpc. This is a regression because it was successfully
> > built on powerpc for version 1.85.0+dfsg1-1. I can reproduce this on my
>
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
Source: hurd
Version: 1:0.9.git20250420-1
Severity: wishlist
Tags: patch
X-Debbugs-Cc: debian@fabian.gruenbichler.email
Hi!
while looking through the archive for unrelated reasons, I noticed src:hurd is
the only package using Rules-Requires-Root: debhelper/upstream-make-install
the resulting wra
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
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: release.debian.org
Severity: normal
X-Debbugs-Cc: fragme...@packages.debian.org, debian-r...@lists.debian.org,
debian@fabian.gruenbichler.email
Control: affects -1 + src:fragments
User: release.debian@packages.debian.org
Usertags: binnmu
nmu fragments_3.0.1-8 . ANY . unstable . -m "R
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
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
-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
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 about, can you create a list? (Pl
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
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
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
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
Hi Julien,
would it be okay for you if I imported the current version in the
archive to salsa (in a namespace of your choice?) and prepare an upload
with the update to 3.9.0 (and maybe do a bit of housekeeping)? If so,
would you like to review it before I go ahead?
I'm a DD so I can take care of
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
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
dear release team,
I would appreciate some indication/answer which of the options below we will
target for Trixie. I did a rebuild of all immediate rdeps of rustc with the
baseline raised there (well, with the two patches lowering it dropped ;)).
out of the 3222 packages rebuilt, there were 82 bu
Package: ifupdown2
Version: 3.0.0-1.3
Severity: wishlist
X-Debbugs-Cc: f.gruenbich...@proxmox.com
hi!
with trixie approaching fast, it would be nice to get a somewhat current
version of ifupdown2 in Debian. having a git repo on salsa would also be
appreciated in case you want to collaborate!
tha
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
Subject: zvol sync/flush regression in 2.2.7+
Package: zfs-dkms
X-Debbugs-Cc: f.gruenbich...@proxmox.com
Version: 2.2.7-1
Severity: grave
Forwarded: https://github.com/openzfs/zfs/pull/17131
Tags: upstream patch
hi!
zfs 2.2.7 and later do not honor all kinds of sync writes/flush requests
properly
On Thu, Mar 6, 2025, at 9:45 PM, Jeremy Bícha wrote:
> Source: papers
> Version: 48~beta-3
> Severity: serious
> Tags: ftbfs trixie sid
> X-Debbugs-CC: debian-r...@lists.debian.org
>
> Papers now fails to build. Because the build succeeds in Ubuntu 25.04
> which is generally very similar to Debian
On Thu, Mar 06, 2025 at 05:21:38PM +0100, Timo Röhling wrote:
> Package: release.debian.org
> Severity: normal
> X-Debbugs-Cc: libg...@packages.debian.org, ruby-rug...@packages.debian.org,
> python-pyg...@packages.debian.org, ca...@packages.debian.org
> Control: affects -1 + src:libgit2
> User: re
On March 6, 2025 3:38:42 PM GMT+01:00, Santiago Vila wrote:
>Package: src:rust-rebuildctl
>Version: 0.22.1-1
>
>Dear maintainer:
>
>The following command does not work:
>
>$ debcheckout rust-rebuildctl
>declared git repository at
>https://salsa.debian.org/rust-team/debcargo-conf.git [src/rebu
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
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 change anything. As Fabian says,
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/
Package: release.debian.org
Severity: important
X-Debbugs-Cc: debian-r...@lists.debian.org, sylves...@debian.org,
d...@debian.org
Hi!
This is prompted by #1095862 (RC-bug on LLVM/rustc for
unsoundness/miscompilations on current Debian i386, because LLVM and
thus rustc don't support Debian's i386
Source: rustc
Version: 1.84.0+dfsg1-1
Severity: serious
Tags: upstream
Justification: Policy 2.2.1
X-Debbugs-Cc: debian-r...@lists.debian.org, sylves...@debian.org
Filing this bug to have a record in BTS - I'll file a separate one for
release.debian.org about the broader baseline question.
This i
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
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
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,
>
> As talked a bit over a week ago I'm filing a wishlist request for a
> newer Template Toolkit package. Some background
Source: wasmedge
Version: 0.14.1+dfsg-3
Severity: normal
X-Debbugs-Cc: debian-r...@lists.debian.org, debian@fabian.gruenbichler.email
Hi!
wasmedge's capi-wasi-env autopkgtest uses the wasm-wasi Rust target, which has
been deprecated for a while upstream and finally removed with rustc 1.84.0. This
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
Control: tags -1 +wontfix
> Simon Richter hat am 13.01.2025 11:05 CET geschrieben:
>
>
> Package: librust-zmq-dev
> Version: 0.9.2-3
> Severity: minor
> X-Debbugs-Cc: s...@debian.org
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi,
>
> this package is identical across architect
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
Hi!
as discussed on IRC, I'd like to help with multipath-tools and related packages
like open-iscsi, at least for the Trixie cycle. We are using these downstream
in a Debian derivative (Proxmox VE).
I've already requested access to the corresponding team and opened an MR for
updating multipath
> Daniel Baumann hat am 13.12.2024 10:18 CET geschrieben:
> Hi,
>
> On 12/13/24 10:01, Fabian Grünbichler wrote:
> > yes, Blair is:
> >
> > https://salsa.debian.org/rust-team/debcargo-conf/-/issues/78
> > https://tracker.debian.org/news/1582226/accep
> Daniel Baumann hat am 13.12.2024 08:53 CET geschrieben:
> Hi,
>
> is there any news, is someone working on this?
yes, Blair is:
https://salsa.debian.org/rust-team/debcargo-conf/-/issues/78
https://tracker.debian.org/news/1582226/accepted-rust-hyper-141-1exp1-source-into-experimental/
seems
Control: notfound -1 rustc/1.82.0+dfsg1-2
Control: found -1 libgit2/1.8.4+ds-2
Control: reassign -1 libgit2/1.8.4+ds-2
Control: severity -1 grave
Control: merge -1 1088281
Control: affects 1088281 rustc
On Tue, Nov 26, 2024, at 6:29 PM, Justus Winter wrote:
> Package: cargo
> Version: 1.82.0+dfsg1
Control: severity -1 normal
On Mon, Nov 18, 2024, at 11:26 PM, Mike Hommey wrote:
> Package: cargo
> Version: 1.82.0+dfsg1-1
> Severity: important
>
> Dear Maintainer,
>
> firefox-esr currently FTBFSes on mipsel64 with the following error
> printed out by cargo:
>
> error: failed to acquire jobse
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
gix 0.64 should be on its way to the archive now! cargo upstream is still at
0.64 atm, so this will remain the packaged version for at least the next ~6
weeks or so. please holler if there's anything needed other than a full update
of the whole gix-* stack (i.e., if a backport of a compatible up
On October 15, 2024 6:14:00 PM GMT+02:00, Jonas Smedegaard
wrote:
>Please upgrade to, or separately provide, newer branch v0.66.
0.64 will hit unstable sometime next week I hope (waiting for the base64
transition to migrate first). I am not planning to upgrade beyond the version
that rust-c
Package: release.debian.org
Severity: wishlist
X-Debbugs-Cc: debian-r...@lists.debian.org
Hi!
I briefly asked about this a while back on IRC, and thought I had already filed
this formal request/report, but it seems I failed to actually do that..
Some background information:
The Rust toolchain (
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
On August 2, 2024 10:56:36 AM GMT+02:00, Gianfranco Costamagna
wrote:
>control: tags -1 moreinfo
>
>> BTW what's the difference with wasi-libc package ?
>
>yeah, looks like the same idea and code, and yet another fork
>
>This branch is 289 commits ahead of, 138 commits behind
>WebAssembly/was
On Thu, Jul 11, 2024 at 06:06:21PM GMT, Jonas Smedegaard wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Jonas Smedegaard
> X-Debbugs-Cc: debian-de...@lists.debian.org, build-common team
>
Hi!
(all of what follows is my personal opinion and not coordinated with
other members of the Rust p
Source: corrosion
Version: 0.4.7-1
Severity: serious
Tags: ftbfs upstream patch
Justification: fails to build from source (but built successfully in the past)
hi!
rustc in version 1.79 and later doesn't allow dashes in lib names
anymore. corrosion's test cases executed as part of the build and la
On May 9, 2024 11:28:06 PM GMT+02:00, Joseph Carter
wrote:
>This bug should've been closed at some point in the past but has reappeared in
>the newer version:
>
>cargo 1.70.0+dfsg2-1
>rustc 1.70.0+dfsg2-1
>.
>rustc recommends cargo >= 0.71.0~~ and cargo < 0.72.0~~ … The expected
>solution t
On Mon, 08 Jun 2020 19:16:27 -0400 Harlan Lieberman-Berg wrote:
> Package: cargo
> Version: 0.43.1-3
> Severity: wishlist
>
> Hello fellow Rustaceans!
>
> Because cargo has a direct dependency on OpenSSL, it seems logical that we
> should switch the priority of openssl and gnutls so Cargo, at le
On Sat, Apr 27, 2024 at 05:40:49PM +0800, Maytham Alsudany wrote:
> Hi everyone,
>
> Thanks for your input and suggestions. I've attached an updated patch with
> several changes, including improving making the description of the field more
> specific, adding another example that is not Go/Rust rel
On Fri, Apr 19, 2024 at 07:59:19AM +0100, Sean Whitton wrote:
> Hello Go and Rust packagers,
>
> On Thu 18 Apr 2024 at 11:29pm +03, Maytham Alsudany wrote:
>
> > With the increasing amount of programs in Debian that Build-Depend and
> > statically link with Golang and Rust libraries, it's importa
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 Tue, Apr 23, 2024 at 06:32:04AM +0900, Mike Hommey wrote:
> On Mon, Apr 22, 2024 at 10:24:09PM +0200, Fabian Grünbichler wrote:
> > Hi Wesley, Yaroslav, Carsten and Mike,
>
> Hi Fabian,
>
> Let me start by thanking you for the work going into packaging rustc.
>
> &
On Fri, 29 Mar 2024 11:14:44 -0400 Wesley Schwengle
wrote:
> Package: rustc
> Version: 1.70.0+dfsg1-9
> Severity: wishlist
> X-Debbugs-Cc: wes...@schwengle.net
>
> Dear Maintainer,
>
>
> I was trying to build a rust package from source when I noticed they use
> traits. Async traits are support
On Mon, 16 Jan 2023 15:08:52 + Julian Gilbey wrote:
> Package: rustc
> Version: 1.63.0+dfsg1-1
> Severity: normal
>
> This version of rustc in unstable and testing says:
> Recommends: cargo (>= 0.64.0~~), cargo (<< 0.65.0~~), llvm-14
> but the version of cargo now in unstable and testing is 0
On Mon, 15 Apr 2024 16:12:43 +0800 WANG Rui wrote:
> Source: rustc
> Version: 1.70.0+dfsg1-9
> Severity: normal
>
> Dear Maintainer,
>
> I am the maintainer for the Rust LoongArch target, and I am reporting a build
> failure issue with `rustc` on LoongArch64. I am seeking your assistance in
> ad
On Sun, Mar 17, 2024 at 06:53:34AM +0100, Emanuele Rocca wrote:
>
> On 2024-03-16 04:21, Emanuele Rocca wrote:
> > With libcurl3t64-gnutls cargo can now be rebootstrapped on armhf
>
> And on armel too. Fixed armhf/armel packages uploaded.
>
> > Fabian: it seems that cargo's build-depend on git c
On Thu, Mar 14, 2024 at 10:03:57PM -0700, Otto Kekäläinen wrote:
> Hi!
>
> Is anyone perhaps planning to fix cargo?
>
> For example curl isn't building on armel/armhf now and numerous packages
> that depend of curl are not building on armel/armhf.
>
> Thanks in advance to the person who steps up
On Tue, Mar 12, 2024 at 05:55:59PM +0100, Emanuele Rocca wrote:
> [ debian-rust added to CC ]
>
> Hi,
>
> On 2024-03-12 11:03, Simon McVittie wrote:
> > In the medium term, cargo needs re-bootstrapping on the affected
> > architectures (armel and armhf, plus a bunch of -ports architectures
> > wh
On Wed, 31 Jan 2024 00:14:50 +0100 Matthias Geiger wrote:
> please consider providing a librust-librsvg2-dev package. This should
> just install the rust source files under
> /usr/share/cargo/registry/librsvg2-VERSION. This will be needed by
> loupe/glycin to load svgs (other crates also started d
On Thu, 13 Oct 2022 12:42:59 +0100 Christopher Obbard
wrote:
> Package: rustc
> Version: 1.61.0+dfsg1-2
> Severity: normal
>
> Dear Maintainer,
>
> When following the bootstrapping process in d/README.source, it only
> seems to generate a tarball with the amd64 binaries despite the variable
> u
On Fri, 8 Dec 2023 15:52:30 + Huw Jones wrote:
> Hi,
>
> Is there anything I can do to help resolve this issue?
>
> Kind regards,
> Huw
FWIW, this also affects plain "gbp import-orig" with component tar
balls, and the patch from this bug fixes the issue for me when applied
on top of 0.9.33
1 - 100 of 254 matches
Mail list logo
