Hi Maytham, Le mardi 17 novembre 2026 00:08:11 heure normale d’Europe centrale, vous avez écrit : > Hi Fab, > > On Sun, 2026-11-15 at 20:12 +0100, Fab Stz wrote: > > Since I chose to rename the package to html-build (to conform to upstream's > > name), I created a new repo to start on fresh base: > > > > https://salsa.debian.org/bastif/html-build > > html-build is a bit generic though, IMO whatwg-html-build was a better > name.
If you don't mind, I'd prefer to stick to that, it seems to be common to use the upstream name for the package names, and I haven't found anything in the policy about that. The rust packages that are maintained in debcargo-conf [1] are prefixed by "rust-" prefix (for the source package in Debian), and for the binary package in Debian, its name is the rust package name from Cargo.toml. On the contrary, the other packages that are not maintained in debcargo-conf but in rust-team don't have that "rust-" prefix [2]. [1] https://salsa.debian.org/rust-team/debcargo-conf [2] https://salsa.debian.org/rust-team/ BTW, I think [2] would be a good location for the repo. Do you mind if I ask the rust-team if it can be moved there? > > By the way, this requires the version 0.40 of crate markup5ever_rcdom > > (package rust-markup5ever-rcdom). But it has not been uploaded to the > > archive yet. > > That's because with v0.35 the autopkgtests failed (when mixed with > > html5ever 0.40). > > You can get the deb by using the repo which is on my debusine workspace > > [1]. The snipped for apt sources is displayed there. > > So that means the crate needs to be updated before this package can be > uploaded? rust-markup5ever-rcdom 0.40 is in the archive now. It was just a matter of days. > This is only required for breaking changes according to semver (e.g. > 0.40 -> 0.41 or 1.0 -> 2.0), which is intentional so that when a crate > is updated in the archive, the rdeps are reviewed. Either way works, but > there is not really any point in ORing both. [...] > I only suggested adding autopkgtest because you had the librust-whatwg- > html-build-dev package for the crate. If nothing uses it, it would > probably be better to get rid of it and the autopkgtest altogether. It > can always be reintroduced later if some software needs the library. I suggest we keep both the librust-whatwg-html-build-dev package and not ORing the deps. That way, if anyone updates a dependency without updating html-build, then the autopkgtest will fail, inviting to remember to update html-build as well. The librust-*-dev package is anyway only used by the build systems. It is unlikely anyone installs these package, except if developing with the Debian rust registry. So there is no harm in keeping it. Actually, recently the autopkgtests of html-build were failing because html5ever was updated to 0.40 while rust-markup5ever-rcdom stayed at 0.35. Normally both packages are supposed to be updated at the same time (they are part of the same workspace). If the autopkgtests were there, it would have been noticed earlier that both had to be updated together. > [...] > > > - The binary should be installed to usr/bin/whatwg-html-build, not > > > usr/bin/html-build. > > > > Instead of renaming the binary to the name of the package (which is likely > > a requirement from the Debian Policy, but I can't find it right now), I > > preferred to rename the package from "whatwg-html-build" to "html-build" > > (in line with the name in Cargo.toml). That way there is no need to patch > > the scripts that call this binary, > > I find this ambiguousfor the same reasons as above for the package name. > Patching is not necessary since you can easily create a fake PATH that > symlinks html-build during package build, or take the cargo approach and > include a fake bin dir in the package. I don't really see the point of having both renaming from html-build to whatwg-html-build + creating a symlink with the original name to whatwg-html-build. html-build is supposed to be installed only by the build system, in order to build the HTML spec from the sources. I don't think anyone will ever use this package for anything else and install it locally. Regards Fab

