Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1231964 > unrolled thread

Bug#1094483: (was rust-async-std: FTBFS with "nocheck" profile)

Started byJonas Smedegaard <jonas@jones.dk>
First post2025-02-06 09:20 +0100
Last post2025-02-06 09:20 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1094483: (was rust-async-std: FTBFS with "nocheck" profile) Jonas Smedegaard <jonas@jones.dk> - 2025-02-06 09:20 +0100

#1231964 — Bug#1094483: (was rust-async-std: FTBFS with "nocheck" profile)

FromJonas Smedegaard <jonas@jones.dk>
Date2025-02-06 09:20 +0100
SubjectBug#1094483: (was rust-async-std: FTBFS with "nocheck" profile)
Message-ID<Kd5h8-eMts-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Quoting NoisyCoil (2025-02-06 00:25:36)
> Control: reassign -1 dh-rust
> Control: retitle -1 dh-rust: fails to build packages with profile 
> `nocheck` and <!nocheck> B-Ds
> Control: severity -1 important
> Control: affects -1 + src:rust-async-std
> 
> This is a dh-rust bug. When the build is done with the `nocheck` 
> profile, `cargo package` is still called in dh_auto_install. `cargo 
> package` expects the registry to be populated by the crate's 
> dependencies, so the build fails if d/control uses the <!nocheck> 
> qualifier for the B-Ds and these are not installed by other means. In 
> other words, the way dh-rust currently does things requires B-Ds to be 
> installed even if `nocheck` is used.
> 
> Downgrading severity to important because I couldn't find anything in 
> the policy or in https://release.debian.org/testing/rc_policy.txt to 
> suggest that packages must build with the `nocheck` profile. The 
> reported justification "Justification: fails to build from source (but 
> built successfully in the past)" is inaccurate because the packages do 
> in fact build from source with the default profile.

One way of looking at this is indeed to consider it a bug in dh-rust.

More reasonably, however, I consider it a feature request for dh-rust,
since dh-rust does not promise to support building without rust
dependencies available.  Consequently it is a bug in each and every
package using dh-rust to flag rust-related dependencies as <!nocheck>.

I noticed this some time ago and slowly began to cleanup build-
dependencies, but was too lazy to properly file related bugreports.
Thanks to you both for improving the reporting of this issue.

Arguably the bug in rust-async-std (and some 60 other packages) is
more severe, by the notion in Debian Policy §7.7 that it is optional to
declare dependencies, but if any are declared then they must be correct.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[toc] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web