Quoting Markus Triska (2026-10-06 21:00:14) > Jonas Smedegaard <[email protected]> writes: > > > Where do you see that? > > For the packages I mentioned, please see the merged commits here: > > https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/1232 > https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/1233 > https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/1431 > https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/1459 > > Michael has successfully produced these packages and they are merged.
Ah, I was puzzled that you wrote "merged" but I realize now that you are referring to a Rust team process, not the Debian process that both I and the Rust team share. So to revisit your question, now that I realize my misunderstanding its framing: > If possible, please consider updating the TODO file accordingly, so > that everyone interested sees accurately where work is now still > needed. The TODO file reflects what is in Debian, not what is queued internally in the Rust team for eventual acceptance into Debian. So no, I will not update the TODO file, because I need that file to reflect the reality that I am in, in order for my workflow to function (the TODO file serves not only to inform but also to hint which crates need to be pulled in for preliminary building the draft package). My remarks about ITP bugreports still stand: They seem to serve the purpose that you are asking about: help everyone interested in helping out know, which pending tasks are in the works and which are still could need someone lending a hand. Because I will not reinvent the wheel of ITP bugtracking within that TODO file. > > Anyway, thanks a lot for mentioning those packages, because thanks to > > your recent nudging in private conversations I seriously considered > > taking on the taks of packaging some of those packages needed for > > scryer prolog - which would have been a waste of my time, because it > > I hope Michael can successfully complete the work you started! In case > you still want to help, please consider one of the remaining packages. Sorry if it was unclear: I was talking about a hypothetical - there is no duplicate work that Michael or anyone else need to complete, and I am still devoted to maintaining Scryer prolog itself, so no need for Michael to take over that either (but I am open to collaborative maintenance if Michael and/or others are interested in helping out). Kind regards, and sorry for the confusion, - 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
signature.asc
Description: signature
