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
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
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
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
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
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
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
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
>
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
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
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
> >
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
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
>
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
On Mon, Oct 30, 2023 at 09:30:57AM +0900, Marc Dequènes wrote:
> Quack,
>
> Sorry for the lag, I really lacked time and energy recently but I'll try to
> upload a fix soon.
>
> On 2023-10-07 04:09, Jeremy Bícha wrote:
> > No, greetd needs to build itself correctly regardless of whether there
> >
On Fri, Sep 08, 2023 at 06:50:22PM +, Jelmer Vernooij wrote:
> Package: debcargo
> Severity: wishlist
>
> I've packaged a few Python packages that include rust code. Since they're
> python packages, I can't just use debcargo. However, it would be great if I
> somehow use debcargo to extract
On Tue, Nov 14, 2023 at 10:25:51AM +0100, Jonas Smedegaard wrote:
> Source: rust-hyper
> Version: 0.14.25-2
> Severity: normal
> Tags: upstream
>
> Please separately most likely separately rather than upgrading, due to
> not yet stable) newer upstream branch v1.0 (even if only available as
>
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
On Mon, 17 Dec 2018 16:51:53 +0100 Fabian =?utf-8?Q?Gr=C3=BCnbichler?= wrote:
> any feedback on this? I am waiting to rebase the debhelper MR making use
> of this functionality until there is some kind of indication that it
> might be accepted here ;)
FWIW, I rebased both the
On July 25, 2023 10:51 pm, Timo Lindfors wrote:
> Hi,
>
> just for your information, upstream has recently accepted the following
> patch:
>
> http://git.savannah.gnu.org/cgit/tar.git/commit/?id=5461025569c2d946fb31b79f16f60e923bbd79f9
and accordingly, this is now fixed upstream in v1.35 :)
On Fri, Nov 03, 2023 at 03:24:07PM +0100, Eduard Bloch wrote:
> Hallo,
> * Fabian Grünbichler [Fri, Nov 03 2023, 01:57:08PM]:
> > > Eduard Bloch hat am 03.11.2023 13:46 CET geschrieben:
> > >
> > >
> > > Hallo,
> > > * Fabian Grünbichler [Fri, No
> Eduard Bloch hat am 03.11.2023 13:46 CET geschrieben:
>
>
> Hallo,
> * Fabian Grünbichler [Fri, Nov 03 2023, 12:32:50PM]:
>
> > > the version of Cargo seriously needs an update. Because the word is
> > > moving and the old version performs increasingly
> Eduard Bloch hat am 02.11.2023 09:54 CET geschrieben:
>
>
> severity 1042859 important
> thanks
>
> Hallo,
> * Mike Hommey [Wed, Aug 02 2023, 06:37:08AM]:
>
> > 0.66 is the version of cargo that goes alongside rustc 1.65.
> > 0.67 is the version of cargo that goes alongside rustc 1.66.
>
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=arm64=1.2.0-4%2Bb3=1697626199=0
>
> ...
> Merged Build-Depends: ..., librust-env-logger+default-dev,
> ...
>
Source: rustc
Severity: wishlist
X-Debbugs-Cc: debian-r...@lists.debian.org
as discussed in the last rust team meeting, we'd like to merge the
packaging of src:rustc and src:cargo. this bug report is filed to have a
place for discussing potential objections and collect input.
a bit of background
Package: dh-cargo
Version: 30
Severity: wishlist
X-Debbugs-Cc: debian@fabian.gruenbichler.email
See https://wiki.debian.org/StaticLinking and
https://lists.debian.org/debian-legal/2023/09/msg3.html
dh-cargo-built-using currently sets Built-Using for "source-left" licenses, and
> 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 Tue, Aug 8 2023 at 06:22:28 PM -04:00:00, Andres Salomon
> wrote:
> > Package: src:rustc
> > Version: 1.66.0+dfsg1-1
> > Severity: wishlist
> >
> > Chromium's new rust build requirements include the need for
> > /usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/libprofiler_builtins-*.rlib.
> >
Package: wnpp
Severity: wishlist
Owner: Fabian Grünbichler
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-r...@lists.debian.org,
debian@fabian.gruenbichler.email
* Package name: rust-xtr
* Version : 0.1.9
* Upstream Contact: Olivier Goffart
* URL : https
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
ebian/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 upload.
+
+ --
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
Package: apt
Version: 2.6.1
Severity: minor
Dear Maintainer,
with the recent change of long changelogs being truncated automatically, and
the full version of such truncated changelogs always being fetched by
`apt[-get] changelog`, there is no way anymore to use `apt changelog` to just
display
with sequoia being released with base64 0.21 support, I will start
preparing updates for the crates below (at least those maintained by the
Rust team - coordinating with team members as necessary, of course).
I haven't decided yet whether uploading to experimental is the way to
go, or whether
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
> > unversioned
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
On Thu, Apr 13, 2023 at 05:21:50PM +0100, Peter Green wrote:
> On 13/04/2023 15:31, Peter Green wrote:
>
> > I've filed a bug with sequoia upstream. I haven't investigated the other
> > packages at this time.
>
> I just did a quick test of sniffglue, ron and ureq, sniffglue and ron were
> all
Package: gdb
Version: 13.1-2
Severity: important
Control: affects -1 src:rustc
basically a follow-up to #1031946 - there are at least two more rustc
test cases that fail with gdb 13.1 (but used to work with gdb 12.1),
this time only affecting mipsel.
I extracted the test cases in the existing
Package: gdb
Version: 13.1-1
Severity: normal
Control: affects -1 src:rustc
After the fix for #1031745 (thanks for the fast turnaround!), there
still is one test case (unsized.rs) that fails with gdb 13.1 (both -1
and -2), but didn't with 12.1.
I updated the reproducer repo[0], broken and good
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
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
On Wed, Feb 15, 2023 at 02:28:51PM +0100, Vincent Lefevre wrote:
> On 2023-02-07 11:40:54 +0100, Fabian Grünbichler wrote:
> > rustc will be updated in experimental once 1.64 builds are done on all
> > release architectures. first to 1.65, then to 1.66.1, then to
On Tue, Feb 07, 2023 at 10:39:28AM +0100, xevilstar wrote:
> Package: rust-all
> Severity: important
> X-Debbugs-Cc: vmxevils...@gmail.com
>
> Dear Maintainer,
>
> We need to upgrade Rust to 1.66.1 to receive new language features and also
> help the desktop team to track the newer version of
/changelog 2023-01-14 09:38:46.0 +0100
@@ -1,3 +1,11 @@
+rustc (1.63.0+dfsg1-2) UNRELEASED; urgency=medium
+
+ [ Fabian Grünbichler ]
+ * fix compiler_builtins linkage on arm(el)
+ * add compiler_builtins sync fallbacks for arm(el)
+
+ -- Fabian Gruenbichler Sat, 14 Jan 2023
09:38:46 +0100
Package: rustc
Version: 1.63.0+dfsg1-1
Severity: important
X-Debbugs-Cc: pkg-rust-maintain...@alioth-lists.debian.net
rustc fails to (successfully) link crates using parts of
std::sync::atomic, e.g. the following code in (lib) crate bar:
--8<-
use std::sync::atomic::AtomicU32;
use
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: rust-debca...@packages.debian.org,
pkg-rust-maintain...@alioth-lists.debian.net
Control: affects -1 + src:rust-debcargo
Please unblock package rust-debcargo
[ Reason ]
This
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: rust-futures-cpup...@packages.debian.org,
pkg-rust-maintain...@alioth-lists.debian.net
Control: affects -1 + src:rust-futures-cpupool
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: rust-tokio-...@packages.debian.org,
pkg-rust-maintain...@alioth-lists.debian.net
Control: affects -1 + src:rust-tokio-tcp
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: rust-bufstr...@packages.debian.org
X-Debbugs-Cc: pkg-rust-maintain...@alioth-lists.debian.net
Control: affects -1 + src:rust-bufstream
I am not sure how fast this upgrade makes sense - there is barely
anything depending on 0.20 since it's been out less than two weeks,
including sccache, which only has the dependency bumped in git[0].
if sccache releases before base64 is upgraded in Debian, the change looks
fairly mechanical and
> Peter Green hat am 13.12.2022 18:04 CET geschrieben:
>
>
> Sylvestre Ledru wrote:
> > clap should be updated to 4. I just didn't find the time to do it (if you
> > want to give it a try ;)
>
> I just took a look at this.
>
> The new version of clap depends on new versions of clap_derive
> Hello there,
>
> two years ago, Ximin stated that rustup cannot enter Debian until either
>
> - https://github.com/rust-lang/rustup/issues/835 OR
> - https://salsa.debian.org/rust-team/debcargo/-/merge_requests/22
>
> is fixed. The thing is that the first issue was closed in between. Is
>
1.61.0 should be in unstable by now and is still waiting for some
non-amd64 fixes before we will proceed to 1.62.0. rustc needs to be
updated release by release as there are no guarantees that release N-X
where X > 1 is able to build release N.
my plan is to proceed with the next releases one
On August 21, 2022 11:24 am, Uli Schlachter wrote:
> Package: cargo
> Version: 0.57.0-7+b1
> Severity: important
> Tags: upstream
> X-Debbugs-Cc: psyc...@znc.in
>
> Hi,
>
> recently I tried to update some dependencies of a crate and cargo e.g.
> claimed that libc 0.2.126 is the newest version,
On August 18, 2022 11:42 pm, Sylvestre Ledru wrote:
> Source: rustc
> Severity: important
>
> Dear Maintainer,
>
> As part of the effort to limit the number of llvm packages in the
> archive, it would be great if you could upgrade to -14.
shouldn't be a problem, we can do that for 1.61 or 1.62.
On August 7, 2022 9:01 pm, Peter Michael Green wrote:
> Package: debcargo
> Version: 2.5.0-3
>
> Alexander Kjäll was working on packaging wl-clipboard-rs when he ran
> into an autopkgtest failure.
>> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
>> debian cargo
On August 3, 2022 11:57 am, Christian Marillat wrote:
> On 03 août 2022 09:54, Fabian Grünbichler wrote:
>
> [...]
>
>> works for me here (both the unversioned command and the versioned
>> command fetch the same current upstream version)
>>
>> but there is a
On August 4, 2022 12:43 am, Arnaud Ferraris wrote:
>
> Hi,
>
> On Tue, 21 Jun 2022 11:56:43 +0200 =?UTF-8?B?RnLDqWTDqXJpYw==?= Bonnard
> wrote:
>> Hi Sylvestre,
>> at first, I thought it may be a squeekboard coding issue too, but the fact
>> that the
>> same code breaks with rustc 1.59 and
On August 3, 2022 9:24 am, Christian Marillat wrote:
> [...]
> But debcargo deosn't find these new sources :
>
> debcargo package paste
> debcargo failed: Could not create source directory rust-paste-1.0.7
>
> debcargo package smallvec
> debcargo failed: Could not create source directory
On August 2, 2022 10:16 pm, Maxime Devos wrote:
> On 02-08-2022 20:41, Geert Stappers wrote:
>
>> Date: Tue, 2 Aug 2022 19:18:46 +0200, From: Maxime Devos
>>> In Guix, I've noticed that rust-vergen embeds build timestamps. There is
>>> also
>>> a work-around available:
Source: libgit2
Version: 1.4.3+dfsg.1-1
Severity: important
Tags: patch
X-Debbugs-Cc: f.gruenbich...@proxmox.com
Hi!
libgit2 1.3 was built with SSH support enabled (by default). upstream
switched the default with 1.4, it would be appreciated if it could be
explicitly enabled (again) for the
On July 18, 2022 4:22 pm, Daniel Kahn Gillmor wrote:
> Hi Fabian--
>
> On Mon 2022-07-18 14:50:50 +0200, Fabian Grünbichler wrote:
>> note that the rerun line upstream refers to the vendored copy of the
>> curl library which is contained as a git submodule (and directory,
On July 15, 2022 10:59 pm, Daniel Kahn Gillmor wrote:
> Package: librust-curl-sys-dev
> Version: 0.4.49-1
> Control: affects -1 src:rust-debcargo librust-curl-dev
>
> There's a build loop between librust-curl-dev and librust-curl-sys-dev
> in debian: when i "cargo build" anything that depends on
On May 17, 2022 5:25 pm, Peter Green wrote:
> Package: dh-cargo
>
> rust-libc is currently blocked from migrating to testing by an autopkgtest
> regression
> in rust-rpassword.
>
>> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
>> '/usr/bin/cargo', '-Zavoid-dev-deps',
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
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
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 packages as
> blockers of 900928, so I decided to take a look at some of them. I fixed up
> bytemuck,
it should work if you explicitly allow it, see
debcargo.conf.toml.example[0]:
# Whether to allow prerelease deps, by rewriting these to the released version.
# This should only be enabled for certain crates if really necessary, and first
# you should check that they can actually build when
according to one of our downstream users
(https://bugzilla.proxmox.com/show_bug.cgi?id=2333)
> the problem is fixed by git commit
> https://github.com/samba-team/samba/commit/47466691ccb9f73677dc43de3206e365f2daf611.
> samba release 4.10.13+ should contain this fix
so bullseye should already
On February 9, 2022 12:54 am, Mike Hommey wrote:
> Package: rustc
> Version: 1.56.0+dfsg1-2
> Severity: important
>
> Dear Maintainer,
>
> Firefox 97 requires rustc 1.57 (released 2 months ago), which is not yet
> available in unstable.
see
Package: tar
Version: 1.34+dfsg-1
Severity: normal
Tags: patch
X-Debbugs-Cc: f.gruenbich...@proxmox.com
filed upstream (with similar patch): http://savannah.gnu.org/bugs/?61934
ACL entries store references to numeric uids/gids. on platforms that have
libacl, use `acl_to_any_text` to generate ACL
On Thu, Jan 06, 2022 at 10:18:23AM +, Ben Dooks wrote:
> Package: linux-image-5.15.0-2-amd64
> Version: 5.15.5-2
>
> Dmesg output when mmc card is inserted:
>
>
> [137854.880467] mmc0: cannot verify signal voltage switch
> [137855.004774] mmc0: new ultra high speed SDR104 SDHC card at
On Tue, Nov 30, 2021 at 08:18:56PM +0100, Ben Hutchings wrote:
> On Tue, 2021-11-30 at 11:01 +0100, Fabian Grünbichler wrote:
> [...]
> > possibly interesting in that context (I asked/posted the link in
> > #debian-kernel a few days ago as well) - these BTF sections now actua
On November 30, 2021 12:57 am, Ben Hutchings wrote:
> On Sun, 07 Nov 2021 03:52:13 +0200 Bohdan Horbeshko
> wrote:
>> Package: linux-image-5.14.0-2-amd64
>> Severity: minor
>>
>> Dear Maintainer,
>>
>> the Installed-Size of the package has occasionally grown up to 375 MB,
>> which is about 30%
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
On September 13, 2021 7:39 pm, Arnaud Rebillout wrote:
> Package: debhelper
> Version: 13.5.1
> Severity: normal
> X-Debbugs-Cc: ni...@thykier.net
>
> Dear Maintainer,
>
> First let me give a bit of context:
>
> I was putting some work on the docker.io package. Right now docker.io
> depends on
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
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
On January 27, 2021 2:22 pm, Amy Kos wrote:
> Hi,
>
> raising severity, due to several high impact security vulnerabilities fixed
> in Firefox 85.
>
> https://www.mozilla.org/en-US/security/advisories/mfsa2021-03/
IMHO we'd need a freeze exception from the RT to update cargo at this
point in
On November 28, 2020 12:41 pm, Jan Niehusmann wrote:
> Hi,
>
> On Thu, Mar 12, 2020 at 11:07:08AM +0100, Fabian Grünbichler wrote:
>> I am not sure whether we want to work around it in cargo (by defaulting
>> to that location, for example), but this is related to
>>
On April 24, 2019 6:27 pm, Dan Nicholson wrote:
> Source: libgit2
> Version: 0.27.7+dfsg.1-0.1
> Severity: important
> Tags: patch
>
> When libgit2 is built with mbedTLS, it tries to determine the trusted
> certificate location at build time. Unless openssl and ca-certificates are
> installed,
On March 12, 2020 12:06 am, Daniel Kahn Gillmor wrote:
> Package: cargo
> Version: 0.40.0-3
>
> Starting from an empty ~/.cargo, by default on the powerpc platform,
> cargo fails to find the right X.509 certificates to validate an https
> connection to github.com.
>
> But if i explicitly point
On February 18, 2020 11:06 am, Michael Biebl wrote:
> Am 18.02.2020 um 01:21 schrieb Peter B:
>> Package: systemd
>> Version: 244-3
>> Severity: normal
>>
>>
>>
>> -- Package-specific info:
>>
>> ZFS filesystems can be mounted through fstab, the zpool needs to be
>> imported before the mount.
Package: wnpp
Severity: wishlist
Owner: Fabian Grünbichler
* Package name: cargo-deny
Version : 0.6.4
Upstream Author : Jake Shadle
* URL : https://github.com/EmbarkStudios/cargo-deny
* License : MIT or Apache-2.0
Programming Lang: Rust
Description
Package: wnpp
Severity: wishlist
Owner: Fabian Grünbichler
* Package name: cargo-lock
Version : 4.0.1
Upstream Author : Tony Arcieri
* URL : https://github.com/rustsec/cargo-lock
* License : Apache-2.0 or MIT
Programming Lang: Rust
Description : Self
On January 28, 2020 11:38 am, Patrick Matthäi wrote:
> Package: wnpp
> Severity: wishlist
>
> * Package name: rust-tokio-sync
> Version : 0.1.7
> Upstream Author : Carl Lerche
> * URL : https://crates.io/crates/tokio-sync
> * License : MIT
> Programming
On January 28, 2020 11:30 am, Patrick Matthäi wrote:
> Package: wnpp
> Severity: wishlist
>
> * Package name: rust-async-trait
> Version : 0.1.22
> Upstream Author : David Tolnay
> * URL : https://github.com/dtolnay/async-trait
> * License : MIT OR Apache-2.0
On September 11, 2019 3:45:45 PM UTC, Daniel Kahn Gillmor
wrote:
>Over on https://bugs.debian.org/939845, On Wed 2019-09-11 00:26:18
>-0400, Matthew Gabeler-Lee wrote:
>> Having a system update disable a network interface and fail to
>restore it is
>> ... bad. Luckily I wasn't accessing the
Hello perl maintainers :)
I opened up a MR on salsa[1] to include the patches from upstream's bug
tracker that enable IPv6 support by switching to IO::Socket::IP - it
would be great if somebody can take a look at them and upload the -2
package ;)
Kind Regards,
Fabian
1:
Package: wnpp
Severity: wishlist
* Package name: kanshi
Version : 0.2.1
Upstream Author : emersion
* URL : https://github.com/emersion/kanshi
* License : MIT
Programming Lang: Rust
Description : Dynamic display configuration manager
Kanshi uses a
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:
the original reporter did not mention it explicitly (although the kernel
version already indicates it ;)) - the original occurrence of this issue
was on a Debian derivative (Proxmox Virtual Environment), which does not
use Debian's kernel (and thus neither the same AppArmor LSM code nor
AppArmor
also see [0,1] for related discussions elsewhere.
0: https://github.com/lxc/lxc/issues/2778
1: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248
any feedback on this? I am waiting to rebase the debhelper MR making use
of this functionality until there is some kind of indication that it
might be accepted here ;)
On Wed, Nov 14, 2018 at 04:55:03PM -0500, Daniel Kahn Gillmor wrote:
> a) is there a risk that we could somehow have the wireguard kernel
> module loaded, but *not* have wireguard.ko available for finding via
> modinfo -F ? If that's the case, then it looks like the postinst
> script
1 - 100 of 169 matches
Mail list logo
