Hey, > Am 13.08.24 um 21:40 schrieb Bruce Steedman: > > I'm new to Debian Backports so apologies in advance for any faux pas. > I'm new to the role of the backports team delegates, so bear with me if I'm > asking stupid questions in return as well. :) > > I'd like to see rust-all (rustc + dev tools) backported as the stable > > version does not allow me to build Firefox (1.67+ required). I'll be > > happy to create and maintain the backport package myself if necessary. > > Are you sure this is the only build dependency that would need to be > backported in order to build Firefox? > > Also, why do you want to backport it? Apparently the version available in > bookworm seems to be fairly well maintained (i.e. in sync with trixie) via > security uploads. > > That being said, I am a bit reluctant to allow a newer rust toolchain to > enter backports. Wouldn't that defeat the purpose of backports? In general - speaking also as an ftpmaster - I am a bit more relaxed. Rust is one of those statically compiled languages. That means that uploads to backports have a much lower chance to break anything in stable. Therefore I would be fine with those backports.
However, you should ensure that the rust team is also fine with those uploads and don't see any problems with such a backport. > > > I've applied for an RT account and would like to know the next step - > > create an RT ticket? I read that I need a sponsor so all feedback > > gratefully received. If you want to maintain them without a sponsor: yes. We need a ticket. You already have to be in the uploaders (https://ftp-master.debian.org/dm.txt) list for those packages you plan to maintain (if you are a DM). This is something we don't do, this has to be to done by the regular uploaders. DM's are also not allowed to upload to NEW, that means that the first upload needs sponsoring. Hope that helps. Alexander
signature.asc
Description: PGP signature
