- Package:
- src:rust-hstr
- Source:
- src:rust-hstr
- Submitter:
- Jeremy Bícha
- Date:
- 2026-01-01 11:07:02 UTC
- Severity:
- normal
- Tags:
The source package rust-hstr builds the binary package librust-is-macro-dev for Architecture:all with version 0.3.7+0+20250106-2 The source package rust-is-macro builds the binary package librust-is-macro-dev for Architecture:any with version 0.3.6-1 . Because rust-hstr appeared in Debian after rust-is-macro with a higher version number, Debian has automatically removed the older version built by rust-is-macro from Unstable. Because rust-hstr has failing autopkgtests, it is unable to migrate to Testing. Therefore, the version built by rust-is-macro is in Testing. $ rmadison -u debian librust-is-macro-dev librust-is-macro-dev | 0.3.6-1 | testing | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x librust-is-macro-dev | 0.3.7+0+20250106-2 | unstable | all I am filing separate RC bugs against both source packages because I don't know which source package should provide librust-is-macro-dev. Thank you, Jeremy Bícha
Quoting Jeremy Bícha (2025-04-06 21:07:42) I messed up and didn't notice that rust-is-macro was already packaged independently, when I packaged the upstream source project that it is a part of. It is not correct that rust-is-macro is gone from unstable however: https://packages.debian.org/source/unstable/rust-is-macro In my understanding, what is happening is instead, that some package views only show the newest version when multiple are available. I apologize for my inadvertent hijack and the mess that it has caused. If the current maintainer of rust-is-macro wants me to, I will gladly hand back the maintenance of that package. I see two ways to solve this issue: a) rust-is-macro is simply dropped, or b) rust-is-macro gets upgraded to a version newer than what is now virtually provided by rust-hstr, and then the virtually provided binary packages librust-is-macro*-dev are dropped from rust-hstr. I have now lowered the severity of this bugreport, so as to permit a) to happen. To repeat, I will gladly do the second part of b) if the maintainer of rust-is-macro prefer that option: They will then need to do first part of b). Kind regards, - Jonas
Quoting Jeremy Bícha (2025-04-06 21:07:42) Apparently this issue is fixed by now: $ rmadison -u debian librust-is-macro-dev librust-is-macro-dev | 0.3.7+0+20250327-1 | stable | all librust-is-macro-dev | 0.3.7+0+20250327-1 | testing | all librust-is-macro-dev | 0.3.7+0+20250327-1 | unstable | all librust-is-macro-dev | 0.3.7+0+20250621-2 | new | all - Jonas