Skip to content
Snippets Groups Projects

issues: i386-baseline incompatibility for some Rust packages

Closed James Addison requested to merge (removed):bug-973414/known-issue-release-note into master

Document i386 architecture baseline incompatibility for some Rust packages (non-upgrade-specific issue)

Preview screenshot of the resulting HTML displayed in a browser:

image

Ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973414#191 (I didn't attend the meeting mentioned, but figured I'd offer to provide the supporting documentation)

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • There's also #1033065 on i386 baseline problems.

    Specifics are essential here; a warning that some software will fail on some hardware isn't much help. This might also be a good place to put a notice saying "if you use Debian on i386, have you considered joining the i386-porters team to ensure it continues to exist as a release architecture?"

  • Author Contributor

    Ok, yep. I've taken the wrong approach with these edits. The release notes should instead be updated to say that the baseline itself has been adjusted (in other words: to indicate that some systems have dropped below the previous i386 baseline).

  • closed

  • Yes, we need to document that the baseline effectively bumped. We should have a text similar to the previous one (stretch?).

  • Author Contributor

    Agreed; that looks like 1ff4c306 to me.

    Unless someone else is already planning to write this up, I'll draft-write some text and suggest that to #1033065 (and cc i386-porters?) to gather suggestions / consensus.

  • I was more thinking of 4877901a and follow-up commits.

  • Author Contributor

    Ok, thank you. After some more thought, I think I've been getting a large enough proportion of the details incorrect re: i386 to step away from attempting further documentation suggestions, at least for a while.

    (I don't think I'm short on opinions.. but those aren't necessarily useful (and maybe counterproductive) compared to active involvement and motivation in the arch/port)

Please register or sign in to reply
Loading