Bug#1086876: ITP: rust-hstr -- string type optimized for hash operations
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-hstr Version : 0.2.12 Upstream Contact: 강동윤 * URL : https://github.com/dudykr/ddbase * License : Apache-2.0 Programming Lang: Rust Description : string type optimized for hash operations hstr is a high-performance string interning library for Rust. This crate is intended for the compilers or build tools like a bundler, written in Rust. This package is needed by swc (bug#991761). It will be maintained in the collaborative debian section of salsa, at <https://salsa.debian.org/debian/rust-hstr>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcr8XsMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh24IP/ROB18dSt7oQXWhXvA5/ZvWxscwgaOueVmZVmbC9 wRWyufufbqm3j/tgHcSEcOm809svSS2D9OG1l1xL28eLemPSkZF8tzWb01G1GlZC Wb39rTRXuLm66ArpmtbCq46FjIzcjC45kBJufO8IKrhgJKDnjEVGK9aNWP4Ti9qF i5szWJ9dY2K5wjJNgiBQQHKo46PVXaNanXlJ2mLarWLyoB0M/fCW0vUkEpxduZUv 2pYJgidA4CJPV0jPUFlyOiAsBmohTCCQMy+XDJAF++GTMQtLUgv+nZaQ6in2A9pe h4NbwqeuT75AI/AUj9PB6jzgmcMWUu6DZDnjCMUvCr5zMR0PO/DiwdP9s+9mdz8j 4OUnajE3U97E4/hUsQfi8ErWnqwwT25Z66ZqUsTEjXv7j0sO8AWmQ7y6a8teFZPp vZmXb4pdEzw8tUibFHwnSzkapHwAk9WyStVAo2B9C7fVDIxp/O1xNZv2769erm+f 0iX5PuqyqisYl5GOoKD9TIbpO6r06+0LtB/UcqmGX68ZlfnE2zf2vskIiRJOY3cn 1UdG1v9TVeiq2ftt1W/s3uv214HV+K3EEgU2vdrxdETGFmJ4EB39ajGiX46XVyVF CZDpADBxHdQXZropz1lsDaBzdDnF9GGEBTfJPDBVp5FQt536K33LK5mMrrGz+DBi e3vB =257D -END PGP SIGNATURE-
Bug#1086871: ITP: rust-auto-impl -- auto-traits for pointers and closures
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-auto-impl Version : 1.2.0 Upstream Contact: https://github.com/auto-impl-rs/auto_impl/issues * URL : https://github.com/auto-impl-rs/auto_impl * License : Apache-2.0 or Expat Programming Lang: Rust Description : auto-traits for pointers and closures auto_impl is a proc-macro attribute for automatically implementing a trait for references, some common smart pointers and closures. This package is needed by swc (bug#991761). It will be maintained in the collaborative debian section of salsa, at <https://salsa.debian.org/debian/rust-auto-impl>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcr1gUMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhfsUP/2A+4B/kH65D5htz31BhudST0POEsQpOfKqT/ShS NhWIqJgbthNs1AN/7Avj+QDttUYrABDBs9UcZi+3fKlS2p3LssoqtMaw2HxfGUvz STINnwIyJz+4ErDKTYrap2IcYC7S/9NvCEzQa6gBLEaHe/OWLLb6GMjcDEfTdTBX zdZDuHBZvcxNjC5RL4SRwzJZqp6uwuxwDRSrHfb9GcDJUALXY0wyQGqmV+tIS7vF sHaxMiPQyWolr8UDCP6W3u3WqO8khrDk7HtrflHcz17j0HPRUXWsGnzuCIM3j5WT WHkOI92NBGPEtn+5hle4WZWDOJ+WiGpfhvNA2wZeFv2Dt0XVLuvrZ5MINU5NnNPD FyabATh7qCPPguG0cQLUNfFdSjTbthmxhzhgzx5aenWrHkG88PtlZTlY/3IOgMHO Cl7VGniS7Z4sVL/vfUadia+bVYmHmE0UmUNYvhkVI6MUADAeoQTpLchn5qemZ8rP sT8moagjQMy61KwHy0xuSWsWPSWAU5EN7/ZQmCBQL4XsLBjLngIsw9WGhgKlN0hB fw+O2DAa5nYjkfNY1aaA7CF0IHX01yazuhpa5mUyeygvRKrXuw5nRCO8AoOoP/GI tGkVevJTBiKjuPSkCpANtRvMvwNgWNfzL7RbTYUaLS82O7eTtINPmc2RHzIYyIAl drUQ =yKi7 -END PGP SIGNATURE-
Bug#1086863: ITP: rust-swc-core -- speedy web compiler - Rust source code
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-swc-core Version : 5.0.2 Upstream Contact: 강동윤 * URL : https://github.com/swc-project/swc * License : Apache-2.0 or Expat Programming Lang: Rust Description : speedy web compiler - Rust source code swc is a typescript / javascript transpiler. It consumes JavaScript or TypeScript files written in one version of these languages and emits javascript code which can be executed on JavaScript engines that are not yet supporting latest features. . swc is written in Rust, and is an order a magnitude faster than similar projects written in JavaScript. This package is needed by swc (bug#991761). It will be maintained in the collaborative debian section of salsa, at <https://salsa.debian.org/debian/rust-swc-core>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcrr40MHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh58wP/R97R8gbjqfRXFMtXjEPUsHKrNk0bKQsPcEx29Mj g5priaxhvwwVLedQxYTrgQL1YYhxYMBPCz98R1Zjm2/E5CzSqU/4x/Wh58N4oO+G eooym3TyeCwgWRi67dXBvN1z9FDOdTWmPxk26vECj1DrTz4chDuPmVC+FqMkVbbw F+WovOFwGxz8N8JRH91BY4OR0a8Gj2U0XzljL1thr+ZjGdMDJ9y33WtDhMB3BxQX ZpeuP1GtURxslx8zyQX9J0te0tVE3yFvJrvkRi0+4TrnekvuOBUEI7+VBTVj0uTq IBCaC5SR4o7GehgSbNY3OKHxebAxpnucKZV1Sd+hB1olmEfABNPaaY9b92Y++wQM CAc8uC1RdVklCQ2dOItDe7AdbNs5TH8C3dgONrivMeJgOmci7JWkupTnYZ98VsLq ALFl+ptO/7kTNCSa/xWVFERpbR/nvxA0DUwb3GpfQNv7IoHrNvD1v7mrRE6jSvn1 9klxnc9gGeMZ3UMUWx4vd0MjfEWng93b3ryO86Ee/hLSjADTo5faf45XGsBAYMkE Z3I+hrC8ciHygOjOvbSEGwKAdf18FKUE7xMtna9WJKX18gmnNvSPLE4NG1q1UI4U /AQ03MnPKoZlC7axZmno3XBnEmFSmLsGjZieEP12gw3+D5U0Dwm+YGNEx7wkX+av dmYd =vsM1 -END PGP SIGNATURE-
Bug#1062222: ITP: gooseberry -- CLI tool to generate a wiki from Hypothesis annotations
Release 0.10.1 succesfully builds as an unofficial draft package, embedding 10 crates (8 missing, 2 ahead) which needs to be packaged before this can officially enter Debian. The built binary runs and works fine. Main task now is to package the remaining missing Rust crates. Here's how you can help: As user running Debian, you can test this draft package: Either build it yourself from source, or if you want to test the binary that I've built then tell by posting to this bugreport and I will share that. As developer (any developer: you need not be official member of Debian!) you can join the Debian Rust team and help package these missing crates: https://salsa.debian.org/debian/gooseberry/-/blob/debian/latest/debian/TODO - Jonas signature.asc Description: signature
Bug#976052: ITP: zola -- static site generator
Release 0.19.2 succesfully builds as an unofficial draft package, embedding 44 crates (31 missing, 1 incomplete, 4 outdated, 8 ahead) which needs to be packaged before this can officially enter Debian. The built binary runs and works fine (except for features depending on JavaScript components as mentioned it the TODO file). Main task now is to package the remaining missing Rust crates and JavaScript components. Here's how you can help: As user running Debian, you can test this draft package: Either build it yourself from source or tell (by posting to this bugreport) if you prefer testing the binary that I've built - then I will share that. As developer (any developer: you need not be official member of Debian!) you can join the Debian Rust team and help package these missing crates: https://salsa.debian.org/debian/zola/-/blob/debian/latest/debian/TODO - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1086507: please upgrade to v0.37
Source: rust-quick-xml Version: 0.36.1-2 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As subject says, please upgrade to v0.37. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcjkVcMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhkyMP/R+wAh+/H7o1j7Q2gaT8bvHaRibCOjLvMX0ew8VH FJsE/UatgP97RgToNFpui9+nRb3fdSxp1iPJV1X/8psFqKBYd+0Y9C+7Mg2NuznF ZrNAcPehi8PkspV6B5FDvjEwqTuuqeyp5YSC510BhQqkcg47uHDu6CMvpTdQ8YGV aiNYUA5dHYXt3dAL8h4elZSvGVIr8B9YKhwFZZRMRonlf3SUvVaCKuTjyM9sn0bk seUkMSZpn4V9+n2h5IFjyeosjnicz8qHVLJugbpF3bxtX3mR8Gio4tfuz1w9WViV BgbqugU14/jRK2LxKgUPDV3F0urYkT63HY0kvGXRo/96AKyjsgmBHVJxU+Af2XL6 m1lHwHWaao0dfZavTHTzIwMKIzuGthJV63ffshobf7rkpgnGxHugZKjeU0zO9Chi 9gJN8OId5hgMkgrnN2G4KJ3122ykgomsZAhwJ1623IwUBVp60i7J3Gh6F0Nr7JRr FD+SVl4f7lf0pphzQAp4/ADRD2WAe8UJLdugBm2Oc/m0YeU+02oAVkczlGyL+o3y 4zGXG6RDo8BJnI3Yv8418cFPyd7umwtLLSW4LhYEu3UyxiW335BqZMt0bA6+k5BR tjtqQBkAywbL1vozfVzxJE/Go43ysRMeF6iAzfSj53GLtPqkoBZC4JYZbDavEmJk vmrb =vFe2 -END PGP SIGNATURE-
Bug#1081265: does not support ELL 0.69
Quoting Matthieu Baerts (2024-10-26 18:50:10) > On 26/10/2024 17:01, Jonas Smedegaard wrote: > > Quoting Matthieu Baerts (2024-10-26 15:39:47) > >> I was able to install the new version (0.12-5) on Debian Sid, but it > >> is currently not possible to install the previous one (0.12-4) > >> because of the break in libell0. And on Debian testing, it is not > >> possible to install the new version, because it depends on the last > >> version of libell0 :) > >> > >>>> I then sent the new version to Debian Mentors. > >>>> > >>>> https://mentors.debian.net/package/mptcpd/ > >>>> > >>>> Do you think you could sponsor this small update please? If not, I > >>>> understand, I can ask someone else. > >>> > >>> I don't do sponsoring - because I find it awkward how exactly the > >>> responsibility is then split. > >>> > >>> What I prefer instead is long-term collaboration: Would you like to > >>> have me on board as a co-maintainer of the mptcpd package in Debian? > >> > >> Yes, good idea! I'm totally fine with that! > >> > >> How can I do that? By adding your name to the "Maintainer" (without > >> 's'?) field in debian/control file? It looks like it can only have one > >> person / team, no? > >> > >> https://www.debian.org/doc/debian-policy/ch-controlfields.html > >> > >> Or should I use the Uploaders field? They mention the > >> "co-maintainers" term there. Or do we need to create a team just for > >> that? > >> > >> (Also, should I modify the current version on Salsa and re-tag?) > > > > First things first: Regarding the "I"'s in the above, only if you want > > to learn and therefore want us to take it slow. Otherwise you just lean > > back now that you have something that seems to work from your end of > > builds-and-seems-to-function-as-intended, and then I take over and > > polish the package hinting and formally release it - unless there are > > some bits that puzzles me, then I ask you. > > I'm really open to learn, but I don't know how long things will take. > What I mean is that, if it can help, a version 0.13 is supposed to be > released soon, including the two patches included here. Here, I prepared > a new bug-fix version (0.12-5) to unblock the issue with ELL 0.69, and > to be able to install mptcpd again on Sid before any auto-removal. > > I guess it is best not to "block" this version. But there is nothing > that urgent here either, but that would be good to have this bug-fix > version released before the 5 of November: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084302 I have released the package, almost as you left it. Technically the "deadline" of November 5th could be postponed by simply posting to that bugreport, but no need for that when you have fixed the issue, only complicated by my stubborn approach to releasing the fix. > > What I prefer is to keep relatively formal conversations in bugreports, > > and more casual chatter on matrix/irc. I am @jonas:matrix.jones.dk in > > case you wanna chat on matrix. > > I'm matttbe on IRC (Libera.chat and OFTC). You can find me on #mptcp on > Libera.chat for example. But I can check Matrix if IRC is an issue. I am old enough to use irc and be sceptical about other platforms, but young (or just stupid?) to find irc clunky to manage. I self-holst mail and other services (including a matrix node) but have stopped running an irc proxy, now relying on matrix.org gateways - and unfortunately such gateway is blocked by Libera: https://libera.chat/guides/matrix So I cannot easily join you at Libera, but you need not mess with Matrix as I hang out on OFTC as well (via a Matrix bridge). Since I expect most of out chatter about Debian packaging rather that mptcpd project, I suggest we just hang out at my favorite spot used for misc. smaller projects I am involved in: Please join channel #tinker at OFTC. - 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
Bug#1081265: does not support ELL 0.69
Quoting Matthieu Baerts (2024-10-26 18:56:51) > On 26/10/2024 18:24, Jonas Smedegaard wrote: > > Quoting Jonas Smedegaard (2024-10-26 17:01:57) > >> [...] you just lean back now [and] I take over > > > > The git contains only 10 git commits, and seems to smell badly of > > sponsor promotion (regardless of legitimacy of the mission of said > > sponsor). > > Sorry, I'm not sure what you are talking about. Never mind - not sure how, but I totally messed up initially cloning the git repo. There is no problem after all. - 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
Bug#1073626: biboumi: diff for NMU version 9.0-5.1
Quoting Michael Biebl (2024-10-27 20:47:22) > Control: found -1 9.0+20231006-1 > Control: severity -1 serious > > Hi > > > On Thu, 11 Jul 2024 14:34:14 +0200 Chris Hofstaedtler > wrote: > > Control: tags 1073626 + pending > > > > > > Dear maintainer, > > > > I've prepared an NMU for biboumi (versioned as 9.0-5.1) and > > uploaded it to DELAYED/7. Please feel free to tell me if I > > should delay it longer. > Unfortunately the latest maintainer upload 9.0+20231006-1 did not > incorporate the changes from the 9.0-5.1 NMU. > > Thus reopening and bumping the severity to serious to prevent testing > migration. Shipping files in an aliased location is nowadays an RC bug. Whoops, sorry - indeed, I totally missed that. Thanks for spotting and blocking migration, I will fix that shortly. - 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
Bug#1073959: [Pkg-matrix-maintainers] Bug#1073959: QT_QUICK_CONTROLS_STYLE= nheko works for me
Quoting Marco Mattiolo (2024-10-27 10:06:19) > Hi Jonas, > sorry for nit-picking: > > > > > This file is from the package 'mobile-tweaks-common', so this bug > needs to be > > > marked of interest to the DebianOnMobile team: > > > https://salsa.debian.org/DebianOnMobile-team/mobile-tweaks > > > to decide how to handle it (e.g. add an appropriate dependence). > > > > > > $ aptitude search breeze |grep kde > > > p kde-style-breeze - Widget style for Qt and KDE Software > > > p kde-style-breeze-dbgsym - debug symbols for kde-style-breeze > > > p qml-module-org-kde-qqc2breezestyle - Breeze inspired QQC2 Style > > > p qml-module-org-kde-qqc2breezestyle-dbgsym - debug symbols for > qml-module-org-kde-qqc2breezestyle > > > $ > > > > This, however, is quite enlightening: You use a non-Debian package which > > messes with the environment. > > The problem comes from that setting inside mobile-tweaks-common (that is in > Debian) indeed, for non-PlasmaMobile systems. Agreed, the problem is not in nheko use of Qt, but elsewhere in the system imposing a different use of Qt, which is broken: The imposed style evidently lacks support for all uses of Qt, which means it is broken to impose that style globally on the system. If mobile-tweaks-common is in Debian, then please do file a bugreport against that package. > For Plasma mobile systems, the QT_QUICK_CONTROLS_STYLE variable is set inside > the upstream source code > (link [1] in my July, 5th mail) of plasma-mobile, that is a Debian package. > I do not see how the DebianOnMobile team could fix this until the Debian > Qt/KDE team finally uploads > the 6.x version of src:qqc2-breeze-style to sid... in theory, I could patch > plasma-mobile in order to > avoid setting that style variable, but I do not want to do that because it > would break a lot of other apps' UI. > > The root cause here is nheko being a Qt6 app and reaching sid way earlier > then the rest of Qt6-based ecosystem did. Jonas, you were too fast ;) > The proper solution here is that the entire Plasma6 ecosystem gets into sid, > but there's still no clear view when this will happen. No, the root cause is not nheko: Nheko works fine when an only partly supported Qt style is not imposed globally on the system it runs on. It is not a bug in nheko to use Qt6 out of sync of KDE. Please move the discussion about other parts of the system to those parts of the system - e.g. KDE discussions are irrelevant for nheko, as is globally-for-mobile-setup. > > I will close this bug, as I don't believe it is a bug in nheko, but a > > configuration issue on the affected systems. > > > > Thanks a lot to everyone contributing to hunting down this issue, > > > > - Jonas > > > > As I already wrote in the past, it was clear this situation not to be related > to a bug *in* nheko. > I'm sorry that your package was felt like broken by the users, and that a lot > of users complaining about nheko > in Mobian channel were redirected to this bug report. Sorry again for the > noise! > > The bug is ok to be closed, let's just hope Plasma6 will get in sid soon... No need for apology - until it was clarified where the cause of this bug was, it was appropriate to track it as tied to nheko. - 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
Bug#1086095: please update to v4.7
Source: picocli Version: 4.6.2-2 Severity: wishlist Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Please consider updating this nice library to v4.7, as that contains many bugfixes and some minor neat features as well. - Jonas -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcdPGMMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhFV8QAIlP+SYBTgnitrGGY+FwHZTKq3wDFkiYwKSKhz8k yjtYPVFW8JxT3B1cQNH6JZJCHrpY6bmF/vp67M8dmIKrjkiUr9iOCKTFGTfUc1cR zXtc9486Xl9Qcrff8sMKK60+8sITd3fip6d8NjlSZxh88WyGQODCZtbAUBYNKnXy scetaEWM/5YAnJ8KRVF974JOUnCqx6ThRfrrA2/v1I/RwriAapaBRuqY8rkTFkTL YmGBWUMzIkpv/6vAhs8vtu0VklbIu1F+8AOkgfYi/NxkB7pkNq/oxdTWyuBCF2ob TNmapd5vGqAtY98tgAzjwgFFzhvgk9sHeFKpLCRzCxF3IG13XYO+WZqeOCbk9xiX d8egqFgXd2cpQH5EU0aD7nJE2UfRQAWHcX4TV86ldTZiZHwCvHEXeu+dwG3dKBL1 kAf5xzYnMCQod8588HiXCKDerBTeE6uZH65QQOObKrIadTy8cEhcG/02x1M7+y/J Oe1i9AEGDSCj6ldeUIU9MoH8q+wZd43pg9USraNJkvKWyGG7jIbyqPPqXXGZIh2R jIN+CqFSZXc1l8Fcx00mdGZeI4TNv8crnAh5rfVy9DLqNdm8gikIU7Yf6/6OZ1sv 3UijYf+0IpqS1P0lvJhuZ6Vt3AwjwWcpOCO6k8eNd3FSKssndYy7epOx+5u5Tbxl vFm/ =QS80 -END PGP SIGNATURE-
Bug#1081265: does not support ELL 0.69
Quoting Jonas Smedegaard (2024-10-26 17:01:57) > [...] you just lean back now [and] I take over The git contains only 10 git commits, and seems to smell badly of sponsor promotion (regardless of legitimacy of the mission of said sponsor). That is a problem narrowly for this release because the git lacks a pristine-tar branch, but more generally it is socially a problem that history has been ditched. I guess it was not done on purpose. Do you have any knowledge of past source tracking? I have experience in reconstructing a git for packaging purposes, which can be a bit tricky to get right - but I need something to work with... - 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
Bug#1081265: does not support ELL 0.69
Quoting Matthieu Baerts (2024-10-26 15:39:47) > I was able to install the new version (0.12-5) on Debian Sid, but it > is currently not possible to install the previous one (0.12-4) > because of the break in libell0. And on Debian testing, it is not > possible to install the new version, because it depends on the last > version of libell0 :) > > >> I then sent the new version to Debian Mentors. > >> > >> https://mentors.debian.net/package/mptcpd/ > >> > >> Do you think you could sponsor this small update please? If not, I > >> understand, I can ask someone else. > > > > I don't do sponsoring - because I find it awkward how exactly the > > responsibility is then split. > > > > What I prefer instead is long-term collaboration: Would you like to > > have me on board as a co-maintainer of the mptcpd package in Debian? > > Yes, good idea! I'm totally fine with that! > > How can I do that? By adding your name to the "Maintainer" (without > 's'?) field in debian/control file? It looks like it can only have one > person / team, no? > > https://www.debian.org/doc/debian-policy/ch-controlfields.html > > Or should I use the Uploaders field? They mention the > "co-maintainers" term there. Or do we need to create a team just for > that? > > (Also, should I modify the current version on Salsa and re-tag?) First things first: Regarding the "I"'s in the above, only if you want to learn and therefore want us to take it slow. Otherwise you just lean back now that you have something that seems to work from your end of builds-and-seems-to-function-as-intended, and then I take over and polish the package hinting and formally release it - unless there are some bits that puzzles me, then I ask you. Regarding your guesses/suggestions: Uploader field (but I can do it), and no, we don't need any formal team structure (unless we want to). What I prefer is to keep relatively formal conversations in bugreports, and more casual chatter on matrix/irc. I am @jonas:matrix.jones.dk in case you wanna chat on matrix. > (BTW, talking about Salsa, it looks like you didn't push the last > version of ell: I can find the 0.69-1, but not the 0.69-2) Oh, indeed. Corrected now. > > I have zero experience with mptcp as a protocol, but have glanced > > at it curiously over the years. I also have no experience with the > > codebase of the mptpd project. What I can offer is experience with > > packaging, and - as you've noticed already - trust and access to > > releasing final packages to Debian. > > That's good, what I'm missing is this experience with packaging :-) > > Also, I think it makes sense to have an experimented extra person > involved on the packaging side, to avoid having the same person > changing the code, and pushing it directly to Debian! I do consider myself "experimented", but I suspect there are multiple meanings of that words, and also I think you meant to write experienced :-P Sounds like you have given me a green light to add myself as uploader, so I will do that now. Please do shout if you want me to hold back - including if you want us to do it more closely together, as a learning experience. Looking forward to our collaboration, - 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
Bug#1081265: does not support ELL 0.69
Hi Matthieu, Quoting Matthieu Baerts (2024-10-26 14:01:08) > On 10/09/2024 08:40, Jonas Smedegaard wrote: > > Sorry, I messed up: libell dropped a few symbols with release 0.69, > > and I sloppily assumed it was old obsolete ones unused anywhere - > > without thoroughly checking that assumption. > > > > Affected packages are iwd (maintained by me, and fixed upstream > > already so required just a rebuild) and mptcpd, where I've reported > > the issue: https://github.com/multipath-tcp/mptcpd/issues/302 > > Thank you for the bug report! > > Sorry, I thought the bug was fixed with the patch mentioned on the > GitHub issue, and I thought you were going to take it to quickly fix > this build issue. I thought so too, but then life kicked in: I am currently doing a late-in-life bachelor, and that swallows all my focus in waves of time. So no, apology not accepted, because that was on me ;-) > That's OK, I now took some time to create a new release for mptcpd on > Debian including this patch, and that's when I found out there was > another issue caused by ell 0.69. I sent a fix to the mptcpd repo, and > included this second patch in a new mptcpd bug-fix release. That sounds great! > I pushed my modifications to Salsa: > > https://salsa.debian.org/debian/mptcpd > > Everything looks OK there, except the piuparts job: > > https://salsa.debian.org/debian/mptcpd/-/jobs/6488504 > > But I think this is because the previous version cannot be installed > with the latest version of ell, and that's expected, right? Correct: I added a "Breaks:" hint in newest libell* package, against older releases of libmptcpd* - which seems to be what you are asking for confirmation on. > I then sent the new version to Debian Mentors. > > https://mentors.debian.net/package/mptcpd/ > > Do you think you could sponsor this small update please? If not, I > understand, I can ask someone else. I don't do sponsoring - because I find it awkward how exactly the responsibility is then split. What I prefer instead is long-term collaboration: Would you like to have me on board as a co-maintainer of the mptcpd package in Debian? I have zero experience with mptcp as a protocol, but have glanced at it curiously over the years. I also have no experience with the codebase of the mptpd project. What I can offer is experience with packaging, and - as you've noticed already - trust and access to releasing final packages to Debian. - 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
Bug#1024683: ITP: hx -- modal CLI text editor Helix
A development snapshot from 2024-10-23 builds as an unofficial draft package, embedding 2 crates (1 missing, 1 outdated) which needs to be packaged before this can officially enter Debian. The built binary runs and works fine. Main task now is to package the remaining missing Rust crates. Here's how you can help: As user running Debian, you can test this draft package: Either build it yourself from source, or if you want to test the binary that I've built then tell by posting to this bugreport and I will share that. As developer (any developer: you need not be official member of Debian!) you can join the Debian Rust team and help package these missing crates: https://salsa.debian.org/debian/hx/-/blob/debian/latest/debian/TODO - 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
Bug#1086069: please update to v1.12
Source: rust-unicode-segmentation Version: 1.11.0-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v1.12. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmccpQAMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh4E8P+wWrf9OFJT7o4MLtFN2aRJsGIKzyD8YNkVgoyCGu AtNT0X4hEsG++8AxVz9IeH9181wze8ojAXhOz2Ja1yp/JnVb+nPi+BBsvVJNT/hT MefiwpOTTOHtCDJ0R5twf/rb8uZ3nodOTHSJU9DxgO56HEEwU0Gan1r+zdgfa/VQ Pq9nWIdKXFexLNg0bWIJlzfHUxc+P1ikvekdjMLgOPfc03JEcIG/NJFiG6XChory CSaMpnfUj1YFbhSOY0D5w2rvoxk1CrsSitTjmSA2+CXKbpGhgubYSJx6BrMUOLfP lym5uaBDRtI9PqtYzWJpTrh8pu6VF7PziNcFBBUmB81qhjigtwjGgt+5upCEN/Uh FaMUBtKdimPOiEfL6s6/rYRyahDS1AULAs7M44WP3fB+w+H5xaVKf++6oY4HTxCE Izg9iiOvzBN+8zLN0xmi7Up+98WLYBFLCoFxP7oveClVKH5w1kI9/bk4461Khark Gtbr0uKwv1nXVhEBcZyM62hnJ7RbqqTetlEb98xNqogMeq2dLvVog4EBqez7RSVs uetwvnwbpjxLxpC/iEmLeINfVaUpuXQJqgeb9c6WrO4+Kl8kO0GRaaSYNC4sbiNl T/fTP07/SuzJ1rWfzUjYZUeNArybHn0BWh/xUMqlAi/E/RYbGgNa1dwtCZYOo6DF dwdB =jWyK -END PGP SIGNATURE-
Bug#1086071: please update to v0.2.161
Source: rust-libc Version: 0.2.159-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v0.2.161. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmccqToMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh6skP/0bg6Cp12gd+P62/exWq4xsCaa6PEX08DQ/ZMmX7 wxLCkPbHSYssql4Csj2oQZan5vFkRmEEj77Z0qxnU5EEwa4TUPPNVLMSspZ2Ojp+ 9LbLxXPf9rzst/3a1o5CRI2yz6ygZmIUSmThIA5HFrcNmSmD7dCeDe7VOXL2OAgQ oXwYHcyc31x3Y526yD13ZvWtHMNDqM837wnAA+QDbqBagcvj/T8k6Qvigw7Kzs+f PYAlCz7cq09KBKafQfXKmT2xdINbtGSyBWFowDBxzJP/cMpLA1YGaSBCSpa2DrKm hJQMjdiPFLV86RiYeJCqPI1sGkefvESe3yrmd9NGaCsC699ztL2vh/nHzC5QMAlE 29zk9L2vfXc8U2B21NvnyqcPKIX1Nn8iIdYPoe3kB+Jb6v7mfcQbjrLrPR0Hm6Xw InROqO4fKQfIJD2kDLIE3PSPZqYtiDEcBid7Q7Of14kgQXUFg9ZDevmw6remIkmG 7wIqTit85++qXvo3hYmNhidt4W2LSqvJvGdhZzc9h9TUjB8elHJUfSOHbs3GyaU8 4u0w0apWFw15TfdSq4KZn0Sl2IgjkIM2gHVRrA6V+87ivCQ6DeMkYs2DtA6zgYTr JZxhiLMIFnrJNcbokXmJBqOFoEwLvKpndVr2/L6Rzon7Flyz0EUNUpqRrIMbs29x SF1h =/DIi -END PGP SIGNATURE-
Bug#1086070: please update to v1.0.132
Source: rust-serde-json Version: 1.0.128-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v1.0.132. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmccqEUMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhbtYQAI8NHPb+WsMxN3rtSUqPr8loKR4Gd/D0/CXWXg06 ASj7sGLmimfvtWAC/bFsq+6Va07zmWyzK89EAE1zHb271Q60Y/prdBnwPo5C7sim 6xEsyKNm8n9xXo+bYrNH5yzJEUWoiYYE+xWqkP+1yHcA9VqoXJg5eBVj38voarEc xpYD9rYN+iq4V3NL/Ib/dFGz345tDSiIaLa7wH+37U0DWxobcZsBHSEhG3Zk/u7b L0fFDfOsgJWUTKCN4cFMoDc0yfH+kSK1yh9z8iQvpb9MD7TUqAWgp21M8XmKGOrG uq/OZiVXnLgm0l6DErmoOM35o1HHmuL+VexnsmppDahAEjuD+fGDXRloxathMw2T RHODjCXJEcQ7R4VgWCIlQTn/1sTN981dcWd1MmogO3ptTHJvN2KDO4t91S+zaX46 7KAuR9YpP1cQENzNt5G52CaXzn+YFXBFdGdHTFrpK0HjbM6KLmRAd+C7fyNiDzuA sG7AqlQyMdrSogi7Umz+yaBb0059d/lrzY0PIOipy4/5WIOnRfZl2OM/ucMIKQMl gLNzlAdeMSynRq7idTMh+vcQd4yFAlkRoIv3/DPt/4ds24O9oaTykWp7dwyGqddc PUgVOQxc8knXhXQvAAQmTwQ8tZv8yPRAcThL6VwbhWazsWJrUr1w6jfkc4hKnR+K MpoD =BFZ+ -END PGP SIGNATURE-
Bug#1086067: please upgrade to v0.7
Source: rust-fern Version: 0.6.2-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to newer branch v0.7. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcco6YMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhm6EP/3lH9KztlB3ie/IFTi8qz+HoWOHvIoQvmRHzIO+T B2aBfacvGTLkKA0x7nEX3L05K0OxLu42WqR7pyG7QvugYERgljfsvs2xvfwkCcHi CeVSkO2xm0KdAAG/ZinCb7AlbmP4Ojd4Lw6NFhJlCeliXtkbgQE+A4EMjX3jZ0SS neDp3XaJ4HpU8VlU5axLpIek5aRqD/8jU4Xd5rs8crKwptwNWJJBycH4lbKqE79G qq1K06IcjRxCDJ8SoDlKjcCjttjtRzqR2wBYo9SHxBd1NggyRxTKj4A7W1MNll6S mU4UeUMyW5a1jtgJvs7kFCz5w9z7oRC0piVyKBKD8VrxvA4oINvCgvEitF+4EsXK WvKEuad6g1nfDLsPs2r4RfRiQSH8L65eFzSbuNttKVZjfhClpGfbttxeaedaKa2I lEbTBtqUp+dKMI7D+uVZ69Baa5MKU4Fe7zBMmEKzcqrBhprhuT0WSriDPKH3jiLO 3VZ4r7AQGH7N1d3qfV4zcQ9QOyr7cDMvagP/Ij7oaovKuqxsa9ZFb8XBmN5x8C+S B9eyzLq189jF3st9lc7/Vkybb5+vICqVYi6+K22IotF8+FPOnkv3maIUR45UEtGu Qb7p/cLszJ8UqeMw3yl9Mj5Vf/VRVFhXP0CPLb0xNEKbJAuXw/nNcvx4/8/vAdGG z7yl =tteg -END PGP SIGNATURE-
Bug#1073786: ITP: rudof -- CLI tool to process RDF with ShEx, SHACL or DCTAP
Release 0.1.35 succesfully builds as an unofficial draft package, embedding 3 crates (2 missing, 1 outdated) which needs to be packaged before this can officially enter Debian. The built binary runs and works fine. Main task now is to package the remaining missing Rust crates. Here's how you can help: As user running Debian, you can test this draft package: Either build it yourself from source or tell (by posting to this bugreport) if you prefer testing the binary that I've built - then I will share that. As developer (any developer: you need not be official member of Debian!) you can join the Debian Rust team and help package these missing crates: https://salsa.debian.org/debian/rdfsx/-/blob/debian/latest/debian/TODO - 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
Bug#1085942: librust-lazy-regex-dev: Provide the librust-lazy-regex+$feature-dev packages
Quoting noisyc...@tutanota.com (2024-10-23 20:28:04) > > SemVer explicitly do not support stability across major releases, which > > implies that no stability is promised about a feature having same API > > across major releases. > > Are you talking about the availability/unavailability of certain features? If > yes, all of debcargo-conf's packages involved in the 2->3 transition depend > on the default feature, so it would be enough to Provide > librust-lazy-regex+default-dev. If not I'd appreciate it if you could > elaborate on > > > Individual packages are still free to not care about SemVer but then need > > to fully admit that by depending on the core crate, without features. > > It may be my inexperience talking, but it is unclear to me how features are > involved here. How does "depending on the core crate, without features" > equate to fully admitting that a package does not care about SemVer (if not > for the availability/unavailability of features)? I don't understand what > features add to this, logically. a) "lazy-regex v2" represent an API. b) "lazy-regex v2 feature 'default'" represent a subset of a) c) "lazy-regex v3 represents a *different* API. d) "lazy-regex v3 feature 'default'" represents a subset of b) Since a) and c) are different, b) and d) are also different: They are subsets of different APIs. It is normal for a Debian package to provide and depend on API or ABI. It is technically possible to offer or depend on some open-ended ranges of APIs/ABIs, e.g. "the subset called 'default' of any API from v2 to eternity". I am arguing that if the Rust team wants to bind to "whatever API lazy-regex throws at it for any arbitrary major version of the crate", then I will not take part of that nonsense, but also I don't see that I am stopping you from such practice: Simply declare an equally nonsense dependency *without* including feature - e.g. like this: Depends: librust-lazy-regex-dev (>= 2) Hope that helps, - 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
Bug#1085942: librust-lazy-regex-dev: Provide the librust-lazy-regex+$feature-dev packages
Hi NoisyCoil, Quoting NoisyCoil (2024-10-23 18:28:02) > Could you please add the librust-lazy-regex+$feature-dev packages to > librust-lazy-regex-dev's Provides in experimental? In order to > complete the lazy-regex 2->3 transition [1] we would be able to only > touch two packages (modulo unrelated changes) [2] if you did. At this > time, the package only provides the librust-lazy-regex-3+$feature-dev > packages, preventing its usage as a build dependency (hence the > important severity) to packages whose Cargo.toml has a versioned > dependency of the form 'lazy-regex = ">=2.x"'. A patch is in > attachment. I dislike that approach. SemVer explicitly do not support stability across major releases, which implies that no stability is promised about a feature having same API across major releases. I find it bad to encourage SemVer-breakage by offering non-SemVer virtual packages. Individual packages are still free to not care about SemVer but then need to fully admit that by depending on the core crate, without features. Kind regards, - 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
Bug#1085871: RFP: cyme -- list system USB buses and devices
Quoting Jonas Smedegaard (2024-10-23 11:54:53) > Quoting Martin (2024-10-23 09:22:22) > > Package: wnpp > > Severity: wishlist > > > > * Package name: cyme > > Version : 2.0.0 > > Upstream Author : John Whittington > > * URL or Web page : https://github.com/tuna-f1sh/cyme/ > > * License : GPL-3 > > Programming lang: Rust > > Description : list system USB buses and devices > > > > A modern lsusb that attempts to maintain compatibility with, but also > > add new features. Profiles system USB buses and the devices on those > > buses, including full device descriptors. > > Looks great, and in fact I just spent a few hours preparing a release, My draft packaging, fully working if problematic crate either gets packaged or embedded (both requiring free license) is here: https://salsa.debian.org/debian/cyme > but unfortunately it depends on a non-free licensed library: > https://github.com/lienching/pci-ids.rs/blob/main/LICENSE Licensing issue now reported upstream: https://github.com/tuna-f1sh/cyme/issues/49 - 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
Bug#1085871: RFP: cyme -- list system USB buses and devices
Quoting Martin (2024-10-23 09:22:22) > Package: wnpp > Severity: wishlist > > * Package name: cyme > Version : 2.0.0 > Upstream Author : John Whittington > * URL or Web page : https://github.com/tuna-f1sh/cyme/ > * License : GPL-3 > Programming lang: Rust > Description : list system USB buses and devices > > A modern lsusb that attempts to maintain compatibility with, but also > add new features. Profiles system USB buses and the devices on those > buses, including full device descriptors. Looks great, and in fact I just spent a few hours preparing a release, but unfortunately it depends on a non-free licensed library: https://github.com/lienching/pci-ids.rs/blob/main/LICENSE - 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
Bug#1085158: [Pkg-rust-maintainers] Bug#1085158: please upgrade to v0.66
Quoting Fabian Grünbichler (2024-10-22 19:38:58) > gix 0.64 should be on its way to the archive now! cargo upstream is still at > 0.64 atm, so this will remain the packaged version for at least the next ~6 > weeks or so. please holler if there's anything needed other than a full > update of the whole gix-* stack (i.e., if a backport of a compatible upstream > change unblocks something on your end). Great! - 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
Bug#1085463: [pkg-uWSGI-devel] Bug#1085463: Bug#1085463: uwsgi-plugin-mongo: Depends on legacy mongodb driver which should go away
Quoting Alexandre Rossi (2024-10-20 10:50:29) > > Your package (build-)depends on mongo-cxx-driver-legacy, which clearly > > should go away. > > > > Please either stop (build-)depending on mongo-cxx-driver-legacy, or if > > your package is not useful anymore, file for RM of your package. > > Looking at popcon (4) and the fact that the obvious replacement buildep > builds from src:mongo-cxx-driver is in experimental, I guess I'll file > for RM in a few weeks unless advised otherwise. Agreed -> no need to wait, go ahead and file for removal now. - 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
Bug#1085015: rust-rustls: Please upgrade to 0.23
Quoting Blair Noctis (2024-10-18 10:56:11) > On 13/10/2024 16:17, Jonas Smedegaard wrote: > (...) > > What I intend on doing is to not (only) bump the version, but for a > > while maintain dual branches of the crate rustls, to not force all > > reverse dependencies to all change at once. Possibly it turns out that > > there is no benefit - maybe the entanglement is so large that in > > practice all or most packages effectively need to migrate at once > > anyway, but I suspect that there is wiggle room, and I would like to > > explore that. > > > > More detailed (since you asked for that in bug#1084138), my plan is...: > > > > 1. release src:rust-rustls v0.23 to experimental > > 2. release new src:rust-rustls-0.21 to (experimental and then) unstable > > 3. upgrade packages to use src:rust-rustls v0.23 in experimental > > 4. move src:rust-rustls v0.23 to unstable if 3) seems fruitful > > 5. deprecate src:rust-rustls-0.21 when no longer viable to maintain > > > > Time will tell the pace of each step, and whether it stalls at 3). > > Thanks for the details ;) So my worry mostly lies in 2 and 5, which mean a NEW > package and its RM in rather fast succession. For large transitions with > multiple packages needing such maneuvers, I fear this would be a burden for > FTP > masters. It won't be "in fast succession" if package dependencies are complex, as is expected for rustls. Ftp-masters should not be avoided at all cost - out-of-control migration is a too high cost to pay! - 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
Bug#1084596: python-pyrdfa: removal of Python standard libraries in Python 3.13
Control: severity -1 minor Quoting Louis-Philippe Véronneau (2024-10-07 18:17:32) > Source: python-pyrdfa > Severity: important > User: debian-pyt...@lists.debian.org > Usertags: pep-594-deprecation-313 > > Dear maintainer(s), > > Python 3.13 removes a large amount of so called 'dead battery' libraries > from the standard library. As such, code that imports these libraries > will no longer work in Python 3.13, which is the targeted version for > Trixie. > > The following removed libraries were found in this package: > > cgi: scripts/CGI_RDFa.py:22 > cgitb: scripts/CGI_RDFa.py:23 > > See this link for more details: > https://peps.python.org/pep-0594/#deprecated-modules Thanks for reporting. The removed libraries are used only in example code, however. lowering severity accoringly. - 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
Bug#1085211: please upgrade to v0.29
Source: rust-nix Version: 0.27.1-5 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to, or separately provide, branch v0.29. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcPwlcMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhISkP/R2X62lOImRUUe7FHhw2WNA4Q9vro9dJpWBqTUZQ vRx33cNw0AjgZxsbJbcD1yhdBfRuSZ1myrBF0Z5NL3alN7dHI0W+Fl0uIsHffrJ9 AKU9uJ50rlTbgWwCI23WiGXH1msgdzYKJUpD2lVFkgQplinFO5CP+iQ7lY/kAQYe 50LOxUu1KtW1+YY8IwalyVzSK6z8PnWFlWTKhpoWU2JlIgIe2aft/4izmEUEw8BW w19tHtWiW7Gy6sOT4Lk3GURrcn5jubVsSw98ADHDmobbxdqRlKhYPt7JUyxulq0k OkPk//sODWGRkaiqZpJNurti1wbQD0vpHscnpdTZn9SOjt5FgLl8QOT0owVldFkc a0EQyk65vU1bRqDCgHb4ubHl4PPUhX4ul8K5Tl4JLUgdCcVo+bJU7D6dk/a9QOtT ILfgzXda/OoII1EAue2hcPTSLH1ADEHUPxeJ1nGHHtn2++kAaJzS2kFGRpDk88kV EBKLBkudAQ80cDwTe5C4vQ4zEa17YHO0LXKmGbth+4oAKgKbia7fTtJM2ib6bV4j +mOPvkfPO1jf7FrHA5TYxJxhVRhh1hdTzDY+SMkwWiT5pnfNCyrVSY0jQQmfiZkU H7N1K9MXfn67bBnvsZFlvKVlfwsZiWIQsGh5rUdNNmBsjL9TkCcNWUTWkbH4M5DV 9KSs =SGIK -END PGP SIGNATURE-
Bug#1085203: please update to v1.40
Source: rust-tokio Version: 1.39.3-3 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v1.40. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcPhBEMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhOHEP+wYlIncnmSh9QZ0/K/RJ6yv29Wj6RwKCkOJT7KP1 M07kKx4nD3j3sbR57bFCtIP5hJCUCsS37YaK5H0ysSsiuosodq3EcJqOvG3L12GF aUW0e9ETCEj2AHqttW+S8GRNmaYCFSLhatR/IMFfPH031h+8CS4SScxX/ZpxjR9W hLW2a7lW8l+bYn2C+jQJknRXjsOuJqn4JEzGJM8XFK7Ck2IhLXq9Q39zN7ob2RXn yisPWngjZy7cDdB2047FfPOh6/ZLe62Amk8heHzpdXRoa/TYjG+axSrXiUG89gSG SIS7xF1l2l90Ur+S3YV+x6WyBV7Mc0+AwHl1+n7ERJAlvJcIic488moPi8pcKPhr w9Tje/y5ZmDSq14CIogXVNxdpR48UH/8EXU3kRcm2F5Aq4ew5Q+Hk8yZGmxjkOdi zWu7naf9iIzO4H4bd9S5s/k3n0oW2mlqHwu1IPXPrVGspB4eSL8GIIaOHoyHD9On 1CCJg/JbvnMbD2i0Llbv4b/IgNMfILjROF15xy2aUV1MZwI+JxMVKG/Fe7hQr6mu 8WUHY7ds0/y5CJZbBN5CsYEK+oqBG/aVccd5bpA/skNnSr4m3OL9euVYWKxg/hau +3oWXWP+x3YLklcJLeOnEUcONeVRqVn23TJFzMlvbjNy/kA4BiMaYNkqJ5HuwMbF AGkQ =C0WC -END PGP SIGNATURE-
Bug#1085202: please update to v1.0.64
Source: rust-thiserror Version: 1.0.59-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v1.0.64. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcPg5YMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhmVwP/jkAzxlNDvQuijs1NebtqcQsVCsVPYh5PkDste6J lsqdodVoNn0vNX6vSIpvpIGm+AFgPOLWbarGMFqiLp4ZPDQiRhKCPmk55mqyC14p Gd9aZyEBymlmMMqcQRp/K3NsCHC1BHmLyhfoYhqMEduowvJEduVd/5TteQ4VKsKK KIRdktC+9fSrenEV6HDyvpQR2Af5uXckpe0BR7tb5eHNVNU2GA/WzZBxBcs5Xfkr 8bgtFEHRqX0AyOhJYOX4o0BPtSp9iFsALLs0+ldAUEplaWSFEo9DKZjx1mnNHols hpLJArmiFSTrMFftrXNU0xNAB+DsiGO5JybleOYxhNL1o1sd7mtvX3swxW45IzMC 8piDQO2PJlSgrnmopNLTZD+JcCebbaOfkVwc8YTPQ6Q7pBZ5vfKW8l6ECJ0eKkVx eMJ156slS4rFLppXwMM0c4dJH1JV63Z+fwhd1BMLjbZPv9CRH6YPuFH3tOKJaxb5 TNNElgHEsLKFrGKQvm25L+ECIiwdXry893feQmiqIS2O+25UAjZ/+VAtWcpTtEPj m2HZuLedk5ncNXGNa3KKktFwteXOJ8s1qlF+8+M/EaqGUQeA8gjW57WMXnS9On91 k53PnLZ9JLVlKLnReMy8vwX/qrls81uKb/j/PsGulZ9ryGhD3Fcf3KpIFxoSU86w Iwkq =bebO -END PGP SIGNATURE-
Bug#1085201: please upgrade to v0.4
Source: rust-terminal-size Version: 0.3.0-2 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to, or separately provide, branch v0.4. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcPg2wMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhUuYP/jzQgGsu/+CWWogtemJd9N6H8fRwLr+Pjd9gtlzC BvYQJ/F3PmsLWmIzUOAz1hR23foKY324AV8fxJaDWNCreSwwtpNCe+ICIZiN6d1Z gcJkKt26rhZb6YupRsxZ2p0aLG4IX+IJ0ewTNKPHIqzThBUNv+xLfvkCt8dPukGd JJryBfvLbUcI6YRE9ch0JfNw/xiC+se/0oNIUrbE64va9LFJI/qZuahrl4oPpa/S aB4TYbyW7Nd39d6aB/e+xDf9a/nh8xsz0eCd8L94yvf/mXrEfM98wnkcfGnEySo5 jIQLxD4fZcHQpgnYyO68kxSH/0oztI7Htw8lax9S730SSMd/Hqxn7NwV0LqYpGxM Q1Og1NoNXZHnOfB2MkGACvJqJBs3CWAHrko9W1rcouECe7PCdw5CH0ZfMjSSC6WR 1KVktVlUAxyp5XZqeXdNE/yFpK/X7k9DsSnekiw9aikDqUieC+oZkM1CtVeTy/mS JIAGdZo0P6R92CU/p3cOnxU8yrUq24MQw7C5Mx/WwhvPSefcpVvYhr6+kU7ys6LR YFk8VIf8d9lTpuk70sBUsjNuR5FYK8HphSeUnWFS1fY1PPXEtFtJcCSWPZuvJUJJ 6aIo1IVXMvpmdPCnOEyqGsAcCmNH8FdCZzpd35BTIla2RMwLGFtWmjkKrBpV6QNT Wcbf =1SCL -END PGP SIGNATURE-
Bug#1085200: please update to v1.11
Source: rust-regex Version: 1.10.6-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v1.11. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcPgyIMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhUSQP/27UBS2051WVB7g5xIDp0JZzHxOADxENXxViqxB6 ykEVlyibyzvOjlvhBzDo+9VNqTUjLDkZ3U/q1Vjx3XapnUOOTGLingK7ZkXWOg+k waoZgiZitip/m0MrPDVFYv/yUpS0RQC6lHY20/ECn6/h3/kZ54s77jBqDkH5k8Ea ngUGXWj9oh8kAIaM5Labx0UCyy9nuvXD3Zhhm2kKfDHKjijzEvcJ1TQ1sA5zH/xT agLxceSVnD/vajJ5vKky61oSIOymzyVno3pafIzD2FCLcC2ly9dE6Qj3H7Q5b9i0 Kq+qf2VNlsuc6CiArFFjnHOPJhlyZ8ILFaHi3OdKrYdOqJ4AqXt7N+UcwowO3S5g d16wkSpMy69VARTJYwkn23q8D9zjjvZQWiPmz+5Q+VGUBjCAFPl90+RcaGPjX3OJ dL2uPXFNJFYrRub1XHZtos8alg2/ZFiIXNcvGTFSTqq+YqCmGlcOlDl8wBpPkS7c CGFm9UmRCkzA97KNbO9Dl/6Zj2pwzYOAztVtKUCPQYKOjG5040ck1PuBLaASY3kL g47sSShh1xPXqIciFBOnpGxdarqjnhrVkSIeBUYKc+JxJnyUdh7W24Jj5Xbfmy0G CZWHQ44pXb/HSB8VC/kXo3TrTtz1KAPbEAMHToDejJL1krOLUjxWDCj9sQRzvUwy aoGM =PMWC -END PGP SIGNATURE-
Bug#1085198: please update to v4.5.19
Source: rust-clap Version: 4.5.16-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v4.5.19. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcPgWEMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhiBUQAJpw5rHVDUx/nXdiz38sCYqXlR3+vmUVnqM1TCJd Vi/4v+h/CvWSacfMzkbMx+ibrQ26jmctboC40U5EcHHCHfgRxuTwiCoKV/zmm0yB L/sCM9GE8AiXpJ3jkNxNq5ibQh3wfGQDhyzHxOM9qmTo2e2pHHWlWOF2JkMr6BTr idbuo9I9oCaD395Po04g47tdwG8jDXWQ80+yZv0/Fw05z7yjscHDLgEKnDsaXEVI fwFu748OyjFD3bgeAzj6VnQJ36QkXXS8bHHQ7Y+/38uK0Nk+OetHHV52mY71LhkB k0yfPqQj/kQBpy21iFVEu1BFTo4MzrtNG5RxfaT9MPrCCGHNLHjnuhWaz4U5e9ZY m4cY/Vl/XncDysAO1UEmAalsTofqGnp4WAeiXyxvW53yftzajNL11iJY5IDtpRMh v3mRrpgD8MPY5FyZlk5SCrZ/RCeXVb9HxlHVs5ID+Pffji/r4OZQHxpV+Sj2Us3Z OZKbbSJ700Al6xqyTZVhDSzfB7A3f11GmxCNEw80EUOh6KzNpS5RHRYMArbBWAfQ H6wK/a3/+BlfjsTa+Zq879L+EaysAGXIyeyOfhA7SmNrQUZZNtAluRgtlomk12GP rwLeVRUph+VkVedgxjbXjYg2jGOXh0GgH7lg10FJFwa8+Kxxgvj3+6ROPSzWVrt6 Y7Xn =99Gv -END PGP SIGNATURE-
Bug#1085199: please update to v4.5.32
Source: rust-clap-complete Version: 4.5.18-2 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v4.5.32. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcPgYkMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhgwUP/AzrQtmRhcy59P7JSOHI74kBoPEtUaG0vGmk7MWF AJ9kKTDz0yy+poubY1LysNIRyVOojR6G5AVijtNpPDEP20MzhdFMmZTwsSBx9+U/ 0ApDNU6+OnE/AosGNm+UOQrp8qQ/q6UlEcHdWiCUzSUDq4p34DoiNV/i1P1cLl+p i28BLmYRhbD1glT7kQM0qTYAX5E027b5doxO5f7kTHzvvBwj+K+OSYvimup6MgBS M/sP9e6MNcgEZDU1sGzl6pFqhPm+mEDdAynP0G+M7V/zc61pX9RHZDjw3BUcSRXb JS+kJsatcTFfFJR+IApA49aP3eOkIU4uR6AqoUHYwcc45vkloffhxEWv3ivREIY9 49L9rurk4jRClZNUUH3XLhtQVnXcS33APW6KIl/Wp+Ch2JJoxljJ7/KunClYmTa9 0qGxJ6CJnTobNEE1IIqTi4y5H4u0O34tgdrmJC9CUaHguXNDiIZUQDJrRDqLY0pG JQdWKi9f+qDZPnxZulPExuvGWtPSLxxnbTtE4QNlVelOyYxhvQ/d9wS5vYTWYIAH FrCCz8WJqpLyVWG7Xn4XVWXsccTzmwc7gBnLc8RXzSLmnrO3WNtXyhBOjAA39DEV 7df4zG1GeoBTumGEozkVRjFFCpE5thqyHbrpZg7+BW466R59tE0Pz63LoQrOSwEU a2cB =jIts -END PGP SIGNATURE-
Bug#1085197: please update to v0.1.83
Source: rust-async-trait Version: 0.1.81-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v0.1.83. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcPgLsMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhgZ8P/R7BJgmMBQ4QfG+04/T0qM7Ee7dpLpJ/MPlclqNp p7zJb2KcUf9RPlPeJp5oa6srKbt4HMOXK07xyfjOvnZ5lJUAX++wOr0L1qVFKirc zRrllRBlT+YPMp12KfcBscqVhl7JzyhNkFTi6w+i3xKaNCnpU0V2O5qIh46xS4qn 6YSqemaMPozMrYqDd5RPW6J/WbUKnm+1D317l6uF3mj9Ju5wuOKmZ1A03rXPXURi HzoUPj+5Oe22MFJIKFF8yWjFWD1nbGjDfGgWVZHdczrhdFrH8ZJ7XRKoNyZZ6eqg DaRnN6F/ZYFsJpIhqSAc61hIN+5/kbycVw8uGTLX5QfOEcw1eytw5pgkNVT+8F4f e03a++aQUAQOJ4HkG2NHvFqU8/aP6wqCNtvfsCNqcbY3EjKwCyYiNDSaJS+76Nsw lLVcgQyLmw35f5Atbw11cv1vXmHzxL8nOQUBoFjmFr3+XU6KDnz0jDJsYUiE/p4U 7H0/HqqC7l51b0MMhwD68RWGcLzUF2ZlyJxMsH2OWJoxGqF2FuReR8oM44NEdjF4 8wa/oBCCF9SwKBMFJWI1Lv9vkl/matGmPmxGfUezlSwsfftJchHtp7TRJXCH9icS iGMNub3UHrkUVoiQKXKwoHOBz9WKEYibw7MZcJcjBGEIkStSWo1jEvmUfWlGYNLZ VyEP =tRtO -END PGP SIGNATURE-
Bug#1024683: ITP: helix - efficient console-based modal text editor
20.07 snapshot from 2024-10-11 succesfully builds as an unofficial draft package, when embedding 2 crates (1 missing, 1 outdated) which needs to be packaged before this can officially enter Debian. The built binary runs and works fine. Main task now is to package the remaining missing Rust crate. Here's how you can help: As user running Debian, you can test this draft package: Either build it yourself from source, or if you want to test the binary that I've built then tell by posting to this bugreport and I will share that. As developer (any developer: you need not be official member of Debian!) you can join the Debian Rust team and help package these missing crates: https://salsa.debian.org/debian/hx/-/blob/debian/latest/debian/TODO - 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
Bug#1085172: please update to v0.3.31
Source: rust-futures-executor Version: 0.3.30-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v0.3.31. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcOq9AMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhVREP/j1R+jSibOXsg8Vlau+5cOvjwMI/xPmGV11XPvst eo3iVBQhPvHNv2IjV254REGpBvzaK9rjlh3yaNyuFvZ2Wv5SCuq1hlvC5SLJGlyB dPoVvmRUgx7A+GqWQLBkOFyaAW2dmSbkxPUwbBWMnybdaZwjSjPtbh+mVkHTKVy7 EAcmavJ3QY3pDWrCpta34Y2yRtbgA0aINMVQAT2nnnWTQc6N6LQQBZjlgLgjWfYK i8rsxVHD17mnS8ha8GuKK5JraDEb1IegmOy0jgw5Nyy/OtQ/09Up3JlS96XeMb5y YOF3jByx3TCQKPEyRKlouzsPwGYYy1mNehY10N7UnLbzGtHBlTA/Qh0MEsrM68dP NzBCRjuYO3G7tO0p8Zsou4MZxJfeWhksk2UZ/utx+8wHz/PU7XFn+HY+hedbEGAB dnZzMZlsjbKTOmhMkfGoZM3AMVOZvHPYGEQ1EQmvqIYwfH/DU5wNtHUsjau/3Qnm imOyWKp4N82r1kGrpR1VgBovgeWzGsNhEtwcBgoEGGcsGb0QIB8W+WCgFoiNOxkS F20EGr9oABBbHa9QnWYxfmfhCGgIsKcP0NpFf+18/EopIGYT0mPGghK0WwNaNicv VwY/onFuKMel0nlESx16ssq+UkiwLSrnxLIZGc4nhGG631H46mVLGeVaOR8hd6Rx VpUE =Ixln -END PGP SIGNATURE-
Bug#1085170: please upgrade to v0.28
Source: rust-crossterm Version: 0.27.0-4 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to, or separately provide, branch v0.28. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcOptYMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhxrEP/0dTtwPrV4sfd+aFa92MDJay8Kw17RMZoLY7+x7Y IvrCQMKRsQLbzBWj43rMtdHGt4VRO0PSHJ9UvUegnb4K7+u/EiGv1uDRPaTqYfdE Vpa5gQCFvdA6eV3I7dFr1EXD96vDKfOKehMxwDT+MyfHi4k6tQ866HiMFUvG6RGp yA71fM9IrqttjSdTWIv1RLb023TKTf4QHCruSTAy4BrzGew15hXb8kZ/F27Nb1DI hSE0PqtYgX+g9giJAnCAYfJzyEod6RI1kbOq1qTUVcNJMt+Zp1YXI48pw4TeYv5t 7Z2A7L2nB9sJuFnodaefU17fNzQFf2HDCdJv0C0BYxBIicCYxYtmfyaaqoua/Py0 2jPUNlMnFiDZAFJTNlxaR8Q8Ce+D9gP0sYOgTy3OKyxJ3ra5SgYcUE41PYcdXn3b R/l8it2XBRlz0GTZgI7zS/4pjiuBZzQMp6ZYMgzCq68w29wY9wwtCMN1BfEedcfq wEY9ucCJIXoYkyBmncfNkfbV3ywG4sxGazmg0W8akh0+xCaO0nsIv4lb3MpDLrg+ q3fnsM/7Yy1ngLiZ6CXI+ZxiMhOdfhSpFhirFTbOsIbQuDkHsvXde2oEinY5S2kz w/nSvEHcQOPt4sd5+UfiwBAXPFWySe9RXiVtTKU1CVRGR6zes44kHiaK0MObTxtq sqzi =UKqg -END PGP SIGNATURE-
Bug#1085158: [Pkg-rust-maintainers] Bug#1085158: please upgrade to v0.66
Quoting Fabian Grünbichler (2024-10-15 18:25:49) > > > On October 15, 2024 6:14:00 PM GMT+02:00, Jonas Smedegaard > wrote: > >Please upgrade to, or separately provide, newer branch v0.66. > > 0.64 will hit unstable sometime next week I hope (waiting for the base64 > transition to migrate first). I am not planning to upgrade beyond the version > that rust-cargo needs at any given point in time, and packaging two versions > of gix is not really feasible given the number of involved crates. 0.66 might > not make the cut before the freeze, depending on when/how fast cargo upstream > updates.. Thanks! > may I ask what you need the newer version for? Does it absolutely require > 0.66, or would 0.65 or 0.64 potentially work as well? Sure. I need it for Helix (bug#1024683). Build has succeeded with a patch to use 0.62 in the past, and most likely will with 0.63 as well. I guess it will work with 0.64 as well but it is quite likely that some breakage due to my patching might go unnoticed. - 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
Bug#1085166: please update to v1.20
Source: rust-once-cell Version: 1.19.0-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v1.20. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcOnrAMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhZxkP/2JufMkSYTRJZRgYXA3gKOWNC6G89Pb8Y6YBMvoy eii9fy7vShHrUryHCw8Rxahxk6fuReUfFTbhnC2i0U7CicvqeIFa8rhGRdyStQvs OVcjGGdIWKABGQtSBJ73Uiad9KdD3yzPdpS+NvhnYHqFtOsQsKJb/FiW5GXwQMrW 52GR8EbeIab2EMB60boQgYukrD2asCzWThAHFIRFo2hu4v3+Jv2aQNGECmVl6Mv/ sp6RBQas71Yse5kXk8Xt2uJTp8lH2nIeBI5nge2zGQDbgtnaZCH40yH2+IJFQySs bq69a8aDcWR6C2DxaeDnYaXZatADSNTFvk3jRGp/VTHosbCcDjUK8h1SG822or8j zyOg1acshXpDgjwM3nxjClnNX7EYNShh/jEflMr0xEPghW/J+51lGoEYjNoLBE8q wasBxmrFvcQY9h51s8QjFlcSc8v+Z/BjrPHJ4ZBmZobUJTwKGpznozzo+yxt14Mc MGLFiAfZgetgSCl69SopvT+fZI4qWAxv9TGfSbzVyKlRp1g6QwkL+Mc3FeRqtjeW tGAHOL8OZrAV47+0IvFHkv0n8LaZUQDeiZeEuUyY+pkEZXg3JcPnwTSsBtq1gQyz tMW7ZloPy27I3KlBH689ICgZhS5ggbuMwFWuEXb71Lg+8vSmnmTpWmJZ5EWHiCLi naAe =p7+m -END PGP SIGNATURE-
Bug#1085164: please update to v5.3.0
Source: rust-open Version: 5.2.0-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v5.3.0. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcOmxUMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhRi4P/2NOqswSCgMJ573BIEs2fmueVdsvkOVg5ZDH0TrA GYZwfjGrrpZmbSHlHH0KGwndm6MZavpUhPI4KkcWnzcSwzDNEYAVkxDiz8jKcekD LCxghuY2dVdePvVuU9kgKxf54zghcnSXUMqtfI/CQKZiXoFjNznCRG2c9G7OR1By +LVROOUOrVMf7nY3YT2QKDfNfrapnBi8y8wMTqWF1Fi9oysB8S6mjCCjH72qhRvk u3TkwBlsWIKebvUcXeVVEkk/U0l2QAbg+v8JTlfeaVWNSQbAhYImMA2LGc8mJCke tevDDbejvl4IQ67KD3UFFlF4ttbpg1lEmRcD/8i0Da4ojZLAptYPHShg0jFwdN9+ j06BAPfDaxlgqpxo5FHSNsglLscSXtOH+R3c85GDDR5spzLB86TdFjwu+RjjqyEI O0r12jctkWID+TtMZxwLT5P/rnBvi++RUx+9unSyDVeLXFlF1Vb0HLXLRPxGRess fq/kEB81zhpQGhGIFTE0Ef5Kr/D3oZwRhigoIOjVi7PQUan6t2h367wVTrIdQu7u mz1ldNb9VRFQoMRvVKfmjG0JTfKbhOxQ65RssKwhR/BgqWeoB60ReoFFJ1DzFkZ9 Disi3OREXdMhDtbrTdD+lgAZK4K+nL7T02mENh6LjK2zwtX0sSj5xV9fRdmN3/p8 sUus =hSfe -END PGP SIGNATURE-
Bug#1085159: please update to v0.1.7
Source: rust-imara-diff Version: 0.1.5-2 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to v0.1.7. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcOlX4MHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhwDsQAJljFg7oBrajQX1g+/SQdVJKi7wGuWM9aMwPziaM 4BKHmuoQzmnWRT5u9r42Oq26Fdj8rKnlCAzt0IyBpNPlz7vwaiUeAoKrHoh9sCs+ 1v2wKXH7vthdUdxw4GRV5QWlrZ0kr4Yplph41wnLCAhNCiI8vse5nbvwPVt+KsT8 e4YYjU+oth4aqtbyAA4RA4BA2cep7U0U/joBfPM2v32zPxbJ5kkzWc4a1QTp2xeY NoJKvcBc8tLcdFnOntzLNEeFPqf4PplwWGHD7im5rMC1gOSQ2ZvclKmHIqj/Xf3c hTfsloqDBhzCNomYPh/kDpW+QsQRspy/fx49Y8hOx488GJ/727J7t3KldBj+S9xL erxtT/OJOYZ9Tgjr2USexfZhQbRSYuZ1ZDdjVBjt4PRIDxelnpM1EjNnCiFpzFK5 k4LVp9Hofgd2Lr+HRNR++7oL++tlEEdy6fIUx8b54BZ1Ika0TjkvIFuh4KZ3EdIp usaItTFOsAXf11ujqwhp5Gs7HmvA6oIcQ2jI0ZqeZdYrYWvN1RF9MPAv4JbNalFq TWPCJOxo4CaSk8DhaKtRwPvmtLm18dFMkgWYhJXOU/z3unDVleyDU+isMfhgW0Uy HOhA9KpqMYpsRf2g7O2BOL8jhd8MIp1MtZcac+uJ4f924Hx6ViKAVdKWFMM5T9t2 lUQj =wo5B -END PGP SIGNATURE-
Bug#1085158: please upgrade to v0.66
Source: rust-gix Version: 0.63.0-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to, or separately provide, newer branch v0.66. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcOlMgMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhH3AP/irYj48NPPMIU5Y3lVIjJLKfpioEx1djausJgqBS vtSHZMg/y1adEU01qUWJ974ryjOqBJzR7njH2X1uj0n2zMbMBUFZtOxI7OACueiS hTuwv+TfGwJZgZPZBIyt8CT9v7nud/g9DNSlUnjiDMEVKIRQW6qeeatAOL2LxsmX m1Kiq/EaOi5u9Baexbv8bIdrrnLvm0UjWS3pLiaLk/D3bjovHAeoHyncVBaQ7YAG afXbyG4BzSdUZLbB4cCDIah2TR9QulSrWYwvvWEB00Rnz5Qtx/3Tp1dO9nzGyYzJ naJQt9cZ5d9tffy0KckWazjilvrrl3SSTK78NgbmhvsePrITUMFZluxEkVPBueBd e+aCsLfxuqLdO+XbPuFQI2Cc4G5QljNPHeYiImCmM9HDBLXA56j9a8sIkpik3WOe W56kYhTsTHLyNBo5XywPy0WGHMCIp9vGz4/klYMJMkIdeaBFq+Ml9dQF81OiwY9M kyFT7P/DRr2W3c6krh9Zs8yPUDcpyeQSXzwSzqmJMvbFH5Gp4O7z0LObgrX4Cyh+ dihsFyO+Am00pXYOvGhM0Ecatdma43X6EL7G8+2pyYG81WeO2+pvnHoWPvzHhzHG Ya0zSulFOPMRlby6tD5GtXm508F2+xu3BtJ3FF0KRmlrXSL3wz+Sbo4BniiyRo/D WoFq =DkDE -END PGP SIGNATURE-
Bug#1081499: Proceeding with removal of rust-microformats
Quoting Helmut Grohne (2024-10-15 15:46:09) > Hi Jonas, > > On Tue, Oct 15, 2024 at 11:25:46AM +0200, Jonas Smedegaard wrote: > > Quoting Helmut Grohne (2024-10-14 19:08:19) > > > Dear rust-microformats maintainer and ftp team, > > > > > > a month has passed since filing a suggestion to remove rust-microformats > > > from Debian. It was suggested for removal due to not being part of > > > bookworm > > > nor trixie and having accumulated a long-standing RC bug. > > > * #1050087: rust-microformats: Fails to build > > >Last modified: 1 year, 1 month > > > > > > > > > Since the suggestion bug was neither closed nor tagged in a month, silent > > > consent to proceed with removal is assumed. > > > > Please only drop package in unstable, and please wait a few more days to > > allow me to issue a release targeted experimental. > > > > I am still working on getting this package into shape, but the newest > > progress is waiting from additional dependencies (notibly swc which is > > pending but a large beast). > > > > I cannot release targeted experimental right now, due to the perl > > transition. > > Effectively, you state here that you are working on fixing #1050087 and > that doing so depends on other packages being changed. Would you take > the extra step and mailing this status update to #1050087? Yes, I will follow up on bug#1050087, and tag related bugs. > Would you > also be able reference other bugs in other packages that are > prerequisite to making progress? (e.g. the perl transition bug) And > then, please just close this removal bug. No, I still find it relevant for bug#1050087 to not block work in unstable, and I therefore find this removal bug still relevant, except specific to the package in unstable. So I will not close the bugreport but do instead request reframing it to the narrower scope of only removing the package **in unstable**. rust-microformats now exists in experimental. The entanglement of debhelper dependencies being uninstallable at certain moments during the perl transition - which I doubt anyone has tracked as bugreports - is now in the past, and I do not plan on filing/tagging any bugreport related to that. Please go ahead and drop **unstable** rust-microformats (because the package now exists in its still broken form in experimental, where it should have been all along). - 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
Bug#1081499: Proceeding with removal of rust-microformats
Quoting Helmut Grohne (2024-10-14 19:08:19) > Dear rust-microformats maintainer and ftp team, > > a month has passed since filing a suggestion to remove rust-microformats > from Debian. It was suggested for removal due to not being part of bookworm > nor trixie and having accumulated a long-standing RC bug. > * #1050087: rust-microformats: Fails to build >Last modified: 1 year, 1 month > > > Since the suggestion bug was neither closed nor tagged in a month, silent > consent to proceed with removal is assumed. Please only drop package in unstable, and please wait a few more days to allow me to issue a release targeted experimental. I am still working on getting this package into shape, but the newest progress is waiting from additional dependencies (notibly swc which is pending but a large beast). I cannot release targeted experimental right now, due to the perl transition. - 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
Bug#1085135: pandoc can't be installed (Unsatisfied dependencies)
Quoting Sylvestre Ledru (2024-10-15 09:22:03) > apt install pandoc > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > Unsatisfied dependencies: > pandoc : Depends: pandoc-data (< 3.1.3.~) but 3.1.11.1-2 is to be installed > Error: Unable to correct problems, you have held broken packages. Cannot build now due to an ongoing perl transition, but intend on doing so as soon as that has sufficiently progressed. Thanks for reporting this, Sylvestre, - 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
Bug#1085015: rust-rustls: Please upgrade to 0.23
Quoting Blair Noctis (2024-10-13 09:53:33) > Source: rust-rustls > Version: 0.21.12-5 > Severity: wishlist > X-Debbugs-Cc: n...@debian.org > > Might be a bit involved as it's closely related to the http or Web stack. > (http > and other base crates, clients like reqwest, servers like axum, etc.) Thanks for reporting this issue, thereby opening a conversation on how to best approach it. Because agreed, this is potentially complex, due to entanglement of multiple related projects deeply embedded in the Rust ecosystem. What I intend on doing is to not (only) bump the version, but for a while maintain dual branches of the crate rustls, to not force all reverse dependencies to all change at once. Possibly it turns out that there is no benefit - maybe the entanglement is so large that in practice all or most packages effectively need to migrate at once anyway, but I suspect that there is wiggle room, and I would like to explore that. More detailed (since you asked for that in bug#1084138), my plan is...: 1. release src:rust-rustls v0.23 to experimental 2. release new src:rust-rustls-0.21 to (experimental and then) unstable 3. upgrade packages to use src:rust-rustls v0.23 in experimental 4. move src:rust-rustls v0.23 to unstable if 3) seems fruitful 5. deprecate src:rust-rustls-0.21 when no longer viable to maintain Time will tell the pace of each step, and whether it stalls at 3). - 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
Bug#1081319: rust-leptonica-sys
Quoting Jeff Breidenbach (2024-10-13 02:48:27) > The Rust bindings for Leptonica appear unhappy after the leptonlib > transition; perhaps they need to be regenerated? The specific > complaint seems to be "test bindgen_test_layout_max_align_t ... FAILED". I > am unfamiliar with Rust and unsure how to proceed. > > https://ci.debian.net/packages/r/rust-leptonica-sys/testing/i386/52950971/#S7 Thanks for nudging! It did occur to me that "hmm, this probably affects Rust bindings too", but then I forgot about it again, so your reminder is much appreciated. - 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
Bug#1084138: rust-axum: Please update to 0.7
Quoting Blair Noctis (2024-10-12 18:40:03) > On 13/10/2024 00:23, Jonas Smedegaard wrote: > > Quoting Blair Noctis (2024-10-12 17:34:58) > (...) > >> Well, not only. rustls & friends also need an update, which is a > >> non-trivial > >> transition by itself, needing some careful planning and work. Or we could > >> downgrade and wait until the day comes.. > > > > As I see it, updating rust-rustls is only non-trivial if done > > all-at-once, which I find a very bad approach (as I do for base64 as > > well, in case anyone cares for my opinion). > > > > What I expect to be trivial is to introduce a newer branch that other > > packages can then begin depending on at their own pace, and then when > > sensible drop the older branch. > > Could you elaborate a bit on the "branch"? Like, a versioned package (e.g. > rustls-0.21 vs rustls 0.23)? That'd mean NEW travels each time a transition > happens. FTP masters are quite fast these days, but I don't really want to > increase their load. Yes, but I prefer to do so at a bugreport filed against src:rust-rustls, since this conversation is drifting too far away from the issue on topic for this bugreport. - 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
Bug#1084138: rust-axum: Please update to 0.7
Quoting Blair Noctis (2024-10-12 17:34:58) > On 07/10/2024 22:00, Blair Noctis wrote: > > On 06/10/2024 02:33, Jonas Smedegaard wrote: > >> Quoting Blair Noctis (2024-10-05 17:09:43) > >>> As a transition for rust-base64 0.21 to 0.22 is underway, it might be a > >>> good > >>> time to update axum, which is affected and needs adaption anyway. > > (...) > >>> Please kindly consider an update. Thanks. > >> > >> I seem to recall attempting such upgrade a while ago, and giving up due > >> to intimate ties with http v0.2 -> v1. > > > > Whoops, then I guess better just throw off the http stack transition. > > Well, not only. rustls & friends also need an update, which is a non-trivial > transition by itself, needing some careful planning and work. Or we could > downgrade and wait until the day comes.. As I see it, updating rust-rustls is only non-trivial if done all-at-once, which I find a very bad approach (as I do for base64 as well, in case anyone cares for my opinion). What I expect to be trivial is to introduce a newer branch that other packages can then begin depending on at their own pace, and then when sensible drop the older branch. I have not gotten around to doing that yet, though. Until I find the time for that, like the many not-updated-to-newest-shiniest-release crate in Debian, other packages need to deal with older code through patching. For inspiration, here are some patches I maintain for downgrading from rustls v0.23 to v0.21: https://salsa.debian.org/debian/rust-imap-client/-/blob/debian/latest/debian/patches/2001_rustls.patch https://salsa.debian.org/debian/rust-oxhttp/-/blob/debian/latest/debian/patches/2002_rustls.patch https://salsa.debian.org/debian/rust-ureq/-/blob/debian/latest/debian/patches/2001_rustls.patch As noted in the DEP3 headers of those patches, they often derive from a reversal of upstream git commits, and I typically bootstrap a patch with `git log -p $NEW..$OLD`. Hope that helps. If you want to discuss rustls further, then please file a bugreport against rust-rustls. I am happy to repost this comment to such bugreport that others in (and outside) Debian can easily and intuitively locate and participate with as well. I am not, however, in the mood for discussing it at some internal Rust team notes tied to some Rust team: The issue is not internal to the Rust team, it relates to Debian. - 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
Bug#996464: ITP: atomic-data-rust -- graph database server to share Atomic Data on the web
Release 0.40.0 succesfully builds as an unofficial draft package, when embedding 63 crates (60 missing, 1 outdated, 2 ahead) which needs to be packaged before this can officially enter Debian. Runs but needs to point to external web assets until those are packaged. Main tasks now are to package NodeJS parts of the package and dependent npm packages for that, and to continue packaging of the remaining missing Rust crates. Here's how you can help: As user running Debian, you can test this draft package: Either build it yourself from source, or if you want to test the binary that I've built then tell by posting to this bugreport and I will share that. As developer (any developer: you need not be official member of Debian!) you can join the Debian Rust team and help package these missing crates: https://salsa.debian.org/debian/atomic-data-rust/-/blob/debian/latest/debian/TODO - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1073786: ITP: rudof -- CLI tool to process RDF with ShEx, SHACL or DCTAP
Release 0.1.30 draft 1 needs embedding 4 crates (3 missing, 1 outdated); works fine, lightly tested. Main task now is to package the remaining missing Rust crates. Here's how you can help: As user running Debian, you can test this draft package: Either build it yourself from source or tell (by posting to this bugreport) if you prefer testing the binary that I've built - then I will share that. As developer (any developer: you need not be official member of Debian!) you can join the Debian Rust team and help package these missing crates: https://salsa.debian.org/debian/rdfsx/-/blob/debian/latest/debian/TODO - 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
Bug#1051238: ITP: biome - formatter and linter for web languages
1.9.0 draft 3 needs embedding 18 crates (18 missing); built binary is totally untested Main task now is packaging remaining missing Rust crates. Here's how you can help: As user running Debian, you can test this draft package: Either build it yourself from source or tell (by posting to this bugreport) if you prefer testing the binary that I've built - then I will share that. As developer (any developer: you need not be official member of Debian!) you can join the Debian Rust team and help package these missing crates: https://salsa.debian.org/debian/biome/-/blob/debian/latest/debian/TODO -- * 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
Bug#1084227: please upgrade to 3.1.4
Package: pandoc Version: 3.1.3+ds-3+b1 Severity: important Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to 3.1.4, which should be possible now thanks to bug#1056063 being solved. - Jonas -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcDBD4MHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh8EEP/0NMaypiBroGxVcXallTAGv0XXJ9seLuijIpLw5U 9iz2L3sfrOJ+YIQ/K+/o9URsFwAfhuB8oozQEdn7bzcyYpPrZnpMH18HhJRk6sM9 gqPjaNtFwIZznlRXqIbm05piTho0t1L04et9HNdHDWeqYPEdlQ68PtS4C6xR/EA9 8c8FAWPFc+Ku0Ry5TRio3qgstkrvxDT5wko/gMb8P7aoD6xKKRF2tBMHOxokGavT dWxyzTJnArfCOxxrqnDiGGGEoq9Q3D3J7ANex8iXyJTX1IWmpakxZEwyk9oK9PtR SiFR+zVDEEDUiMvLu2pa0gy5SFYimA9+BeVla0JBkKRC1GtZXvekocWSpxYRkOHr jSFeu8+jqBS0xGbEtkrEhsVICot8wS5QFAOBDB8klGzhaJsniWufqU1/YMXANT5T q31eEcg42O6a6iLMnv0vNMbcMC0zIdGQVWFFQRw+87TaQQNxmO+4wG8FcgRuvU6I kRUh9Uix149JfDUOrr/4gUMdXW84GeAFMhY/F4afwFz8cl4Lnzcj6tnyOlfF3Gx6 ldzV+KpQqnXEYpr91hoLcIZSeV+UGowxKtuGeUW+okniqP7yIuKWV7pXbXfEBsWX B1T4eBRqPdQ4vtK/hfNS9Rd2bMQhW5K+dfO3CAWwpsinxeZ8dVpPMhyLYRZQBt4Y IgRW =C5sT -END PGP SIGNATURE-
Bug#1084138: rust-axum: Please update to 0.7
Quoting Blair Noctis (2024-10-05 17:09:43) > As a transition for rust-base64 0.21 to 0.22 is underway, it might be a good > time to update axum, which is affected and needs adaption anyway. > > A codesearch.d.n search shows axum is a dependency of > > - Your package: rust-tonic > - Jelmer's package: ognibuild, which currently FTBFS anyway > - My packages: atuin, which was patched to use older axum, so this update > would > actually remove a patch; and mdbook, which was patched to replace warp with > axum, and can be adapted accordingly. > > Please kindly consider an update. Thanks. I seem to recall attempting such upgrade a while ago, and giving up due to intimate ties with http v0.2 -> v1. You are most welcome whipping up a patch - I would love a newer axum. - 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
Bug#1081900: rust-curve25519-dalek: autopkgtests failures: merlin unavailable
Quoting Blair Noctis (2024-10-03 15:38:19) > On Sun, 15 Sep 2024 16:16:59 -0400 =?UTF-8?Q?Jeremy_B=C3=ADcha?= > wrote: > > Source: rust-curve25519-dalek > > Version: 4.1.3+20240618+dfsg-7 > > Severity: serious > > > > rust-curve25519-dalek is unable to migrate to testing because its > > autopkgtests are failing. > > > > error: no matching package named `merlin` found > > > > https://qa.debian.org/excuses.php?package=rust-curve25519-dalek > Looks like the fix for #1081176 only removed Provides and tests in > d/tests/control, but didn't comment out the feature and dep in Cargo.toml. > Here's a quick patch: Silly me. Thanks for spelling out my glaring mistake. Much appreciated! - 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
Bug#1084081: please urgently update to v0.1.14 - v0.1.13 causes real problems e.g. for git-delta
retitle -1 rust-unicode-width - please update to v0.1.14 thanks Quoting Jonas Smedegaard (2024-10-04 19:15:37) > v0.1.13 arguably broke its own API, as discussed here: > https://github.com/unicode-rs/unicode-width/issues/55 > > The change causes panic in git-delta. Oh - sorry to the alarm bells - git-delta panics in test, not in running code. Still, would be quite nice to have this fixed and get git-delta working properly - and other consumers as well, I assume: The effect of the bug in running code is most likely, as I understand it, wrongly computed line lengths causing e.g. staircasing of some multi-line console drawing e.g. involving ratatui. - 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
Bug#1084081: please urgently update to v0.1.14 - v0.1.13 causes real problems e.g. for git-delta
Source: rust-unicode-width Version: 0.1.13-3 Severity: important Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 v0.1.13 arguably broke its own API, as discussed here: https://github.com/unicode-rs/unicode-width/issues/55 The change causes panic in git-delta. The API breakage has been reverted in v0.1.14. Please update to v0.1.14 (and be cautious about later upgrade to v0.2 as that reintroduces the seemingly minor but important change, so require close attention for all consuming crates - not the loose patching that we (or at least I) commonly apply. - Jonas -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmcAIrUMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhQUkP/2ZSN7YWfZj4DuMaoPKPnb8GI1nUHhDeGAoJuuyn xRgQaHZHBsiGoCnbhl305NdSlXs87oYLLDU3EbuOxcIeC/Sy54URAXybx1MktvTh Rw1SUG4NnUZpWJJTriT0AqhrQok3KdhnFvAx58UputgA3ynIZU4hd7jFSOaudsx6 Q9q5dr/pIFiX0V6+we8AIYjsW/9x6ZYyxX2lG6miT8soCF+MO4Xt0WWJ0z586UKu /973x93kcUgTwAfHkty7/CvcXkroXue85JoAAfEoSJUWWgqJGVscnfhlhq1z9nbq B8VSZesWqggbdLD/b5GaHC0Ji0j/20wCLFgYjoSN/WkTuatviNo7NLzBpyz6z3JZ sSakT9TiqzZV6OSBcEUapmSRFc2s2MlTkkdyGMOhwGEhRna1lGVJ8bG958D2hgFG qiQudFh+hNfWJd2Cj/c+MuR9viSiYqIbZjkAq+sxn4ATTFqAasca990APJ2WNbBl RglET17zdiIq2+CStcydvzQ6tLd1lL7PRP2Em7EKguL/KWiduXsVZyyw9Ued5UIr QX2qH5GQ8E1BcgBy7/b99hCSytvdzq3H8gPCUGUlx2YjW89hRWamlShc+xdKjo/7 CB/Fk4Myb/89i5To1mjOpUfRnmca2cy8tXXIq/Q6S8K3tBiEaYWcOxa8euItsJEz 4lu1 =Wp2M -END PGP SIGNATURE-
Bug#1056068: RFH: resvg -- SVG rendering library (command-line utility)
Quoting Andrej Shadura (2024-10-04 10:47:19) > On Thu, 3 Oct 2024, at 23:31, Jonas Smedegaard wrote: > > I realize that I am a bad fit for teamwork here, and step back from > > this collaboration. > > Is this because of synapse? No. Related, but more the other way around: Main reason my work on helping out with resvg got stalled was that I kept hesitating, because I was uncertain how careful I should document my changes to the project. We have varying packaging styles and I wanted to both respect that and at the same time improve on things, so wanted it both clear to follow and also (hopefully) easy to revert parts not appreciated. With synapse I made a brain fart (when my own service began failing to handle attachments I noticed that the Debian package was 6 months behind upstream releases, and I wrongly equated that with the package being in a similar limbo as resvg - clearly it is not) and worked on it for 10 hours, giving much less thought to documenting my changes, with a result that was problematic at the core. My bad handling of synapse made me realize that I have difficulty collaborating with you, and I didn't want to be blocking progress by others. > > For the record, I have a strong interest in this package being well > > maintained in Debian, so if at some point it might be considered to let > > go of the package (or, as was recently potentially brought up, "gutting" > > it by dropping executables and maintaining only library parts), then > > don't consider this an indication of lack of interest. On the > > contrary, I would be more than happy to take over maintenance rather > > than see the package wither away. > > If you have time and energy, please do take it over. I won’t have either for > this package for the coming months at least. Ok, I will take over resvg. Hope we can find ways to collaborate in the future, - 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
Bug#1083294: btm: upcoming nvml-wrapper update
Quoting Matthias Geiger (2024-10-04 09:23:06) > I intend to update nvml-wrapper to 0.10 soon. btm 0.10.x wants that > anyway so this should be straightforward to apply. I won't bother > uploading this to experimental since those are just two crates and the > only consumer is btm which isn't in testing anyway. Thanks for the heads up - I agree with your assessment. - 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
Bug#1056068: RFH: resvg -- SVG rendering library (command-line utility)
Quoting Andrej Shadura (2023-11-16 18:19:47) > Hello, > > On 16/11/2023 18:14, Jonas Smedegaard wrote: > > Upstream project consist of multiple crates released in sync - which is > > a pattern that is only inefficiently handled by the Rust team (by > > needlessly packaging each individual crate as a separate Debian source > > package). > > > > Unless you particularly are asking the Rust team for help here, then I > > can offer to help: I have experience with handling this type of Rust > > source code structure, and would be happy for this opportunity to > > collaborate more closely with you, Andrej. > > Yes, I’m aware of that, that’s why I packaged it separately from the > debcargo-conf-managed packages. Nevertheless, the dependencies can be > managed using debcargo-conf workflow (and that’s what I did when I still > had energy to spend on this package). > > In any case, I’ll be happy with any help that can be had with this > package, whether it’s updating/packaging build dependencies as separate > packages or by following the debcargo-conf workflow, and from anyone — > you, Jonas, included :) I realize that I am a bad fit for teamwork here, and step back from this collaboration. Sorry for having given false hope, and for dragging it on for so long. I wish the best for the future of this package. For the record, I have a strong interest in this package being well maintained in Debian, so if at some point it might be considered to let go of the package (or, as was recently potentially brought up, "gutting" it by dropping executables and maintaining only library parts), then don't consider this an indication of lack of interest. On the contrary, I would be more than happy to take over maintenance rather than see the package wither away. Kind regards, - 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
Bug#1060874: rust-which: please upgrade to branch v5
Quoting Peter Green (2024-10-03 19:04:58) > > Please upgrade to branch v5. > > I think it probablly makes more sense to go straight to version > 6. I've uploaded that to experimental, can you prepare an update > to precious. > > upstream changelog analysis: > > nothing that looks too massive/scary, just msrv/dependency > bumps and some slight changes to errors. > > preliminary rdep analysis: > > precious: >Jonas's package, upstream still on version 4 Preparing a relase of precious now, that relaxes build-dependency for crate which. Thanks! - 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
Bug#1083195: ITP: rust-ulid -- ULID implementation
Quoting Antonio Russo (2024-10-03 14:23:34) > On 10/2/24 15:25, Jonas Smedegaard wrote: > > Package: wnpp > > Severity: wishlist > > Owner: Jonas Smedegaard > > X-Debbugs-Cc: debian-de...@lists.debian.org [...] > I packaged this is in [1]. I'm not sure what the status of rust-team actually > getting the package out is. > > Feel free to salvage as much or as little of that MR as you'd like! Thanks for sharing, but not really helpful now: The package is in NEW. What would have been helpful was if you had filed an ITP, to communicate your work (to Debian, not only within the Rust team) _before_ I initiated similar duplicate work. Kind regards, - 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
Bug#1083195: ITP: rust-ulid -- ULID implementation
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-ulid Version : 0.1.3 Upstream Contact: Dylan Hart * URL : https://github.com/dylanhart/ulid-rs * License : Expat Programming Lang: Rust Description : ULID implementation ulid is a Rust implementation of Universally Unique Lexicographically Sortable Identifiers (ULID). . This package contains the source for the Rust ulid crate, for use with cargo. This package is needed for recent releases of matrix-synapse, fractal (bug#900928), atomic-server (bug#996464) and iamb (bug#1061425). It will be maintained in the collaborative debian section of Salsa, at <https://salsa.debian.org/debian/rust-ulid>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmb9umQMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh3wgP/2KZJGtUdNDSiVFAhGnURXQcpJ6RObdJBfjDdm8U DpOsSukz66cT2fqw1nEYy7m2/Sg+kE5TYa9eb9uSpVmnDsC+POZNCaSfT8REQQtR liLEeUoCoPtzPM40PFqp/ZUhTeuD2KUjxLHoQDAgeVxs0gLG3bLW3O83QhJyZ1iD jA0R+NE8xmrXFhKb2iTqr2Tdkd2VJm4tUeMHnSaTvonA844fh1ySMzU5b6J9jAit 4YSvpGNZn8SZP10zs50uDzJyXBAI04S0hK5OJrDG+A274BSrNfB3eQ4vL3vyzyvV tUjzGxFfNGRAt1N0f5CyajS/S9Pwkn/wr4ijVMePLR18I46PxinVV2ASDPMe3/PE qAAQs7ipWiUcCryGgZ+xn9HhxJ+SHc9yW3TahtPCPB7R3g4iBE3OfvkxbZUxzgpv a6//+Q0q8c5DQw0/Qip09ABvzbFhFMYwTRT4Z6SedkpLevlem7Zla8ETwNo9LwDm 1w8HSW8UdZD01KTUpaAWdx5ldgRxgF9SxnknH4+X1WJdztRiKA0q4DIzDCOB7+NS OvDq2GW/UJnQyuM7LM7Xs584LWTJ9j4SKnAj7pO9hUVWyTOOz5lFn6sA7CQfXV+h 2yex7z5VlUZLckRD4ftZppmaQW85nOaxDLuhlRaWc2HuU7//gG9MQjWKNkG9dj4d PZIU =AnGH -END PGP SIGNATURE-
Bug#1082981: ITP: rust-hashbag -- unordered multiset using a hash bag
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-hashbag Version : 0.1.12 Upstream Contact: Jon Gjengset * URL : https://github.com/jonhoo/hashbag * License : Apache-2.0 or Expat Programming Lang: Rust Description : unordered multiset using a hash bag HashBag provides an unordered multiset/bag implementation backed by HashMap. . A bag, unlike a set, allows duplicate values, and keeps track of how many duplicates each value holds. This type of collection is often referred to as an unordered multiset (see also C++'s std::unordered_multiset). This package is needed for Rudof (bug#1073786). It will be maintained in the collaborative debian section of Salsa, at <https://salsa.debian.org/debian/rust-hashbag>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmb5SpEMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhoKQP/R5rtzUou76Z1b8p5QXjxwSj2uj+DdyEnzDC+W5K E2IYP/M3zBsowbfpoZVuXfQPruvtFRNekIXeiTwuHC4exewXLpTSv/dzyO6aVWZF aDNvzobJqJAbhAQAUtx7RGg8OAAj031J4JNEfSIWb2bdnWWHP1D3Npg61fbUMWdI WMAYkMqb17y1jm3JVTR4kLdS0MMcwpnGiPzBQ79Z1dGy1huDQTo6tzJv9ly4k8ZX seTzD+bOSt1EWEpyZz4kZbnhj/Uon7cPks1SGbM+Czf5zNxLB4vs72WgLKELNm6u aBVz4bgbK8KKg53UjiY75+S1TzZBPX5u+tuN2UkzFW840tScrEbHmlyhOiAX3aqR Ym48QBhFlnlhc27IKokcI0he4cI5jmXHCJnraEpQsFb7KqDRPEGZa/zTJIz86SPF 6T8kl5dgUwEwAvyKmbLdDv7zHSe/x4mlEuRMuBGckkyFamhd5UNAiG7QhyRqTk/F HvKzemS1GpOymR0GNgxdsGOxY2pLzp73Adjg0GrV7lNPNRp98bNSytpduj+FoIxP lV0yrzm/UOc8mxN0u2uvLl3jTBMCvV6BZc4wsiyi+zoq+5/vIMJFSdRpKdr6rwJh oKyoRluwF28KScQ3AryS3u7yTRM3sbIri4jFoZIGRPIK/o/BPMkqw4qiSWaa69G4 Px2o =Yapt -END PGP SIGNATURE-
Bug#1082967: please upgrade to v0.23
Source: rust-tree-sitter Version: 0.20.10-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to, or separately provide, upstream branch v0.23. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmb5IdgMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh81kP/3jMQnZ1Tzw2/qpIDwVuzqDMJnxk/GJIr83dSDvW OfVOfzCXkFiKCL9yKfbcPZi+ZPVGvb/OITUMZCzZvWFs0QmvyLLjBrjyKZZnC3rg vccW+FCu84M870+KlkUbze9oh5b18plkMdaZFbGOdUhbozu3b3kxJeec4oSszuvk 0WhfARn4wwc7wPvH/3VOXQXvjxVwqIthDpE+HpUadoP6mwoDx/XiqoQ79ZoM+sTr PCaNmzkpirchkykQuIBssa/K0654eVgKaCpWp+4DXjywTgAjfnR/Tpc5kMACqCMr lhAaeyd2j/ByiW1esotdST7zDmkPFvPnplu5M5FM5R1ZPP6H6NDGhfWVbIwJ20yE d7+YwOWLLfrLjsl1uabKjPrMnFbtxBUn5V9Imo4F4AyXZbIu9bWHNlcYdjuuRCQa gy8+TYrk/rNfIgAJJ9NaHueBzzg3dBZlfVLBnnBbOgIR0YASgQylDMAkABeDjuQD Rl7AsxqHwAikwf8HOImCGk7S/6iY2xDsy2iC5UG5jxrs/Yjz+MElt7DnD8LKSNGO ns7Q+cjrzlLOX+tplHrbE2y00FVqTXXz0DjHimY4m5pPVv7Ms0mnrX7yIPdmUYFF 3fqDjWpnDdezcx/qv6oUsLM2X0tZrpb3d4GFTZL6cVwCwtEPTljQpupYpd/c0BeL O7xB =zhp4 -END PGP SIGNATURE-
Bug#1079848: Proceeding with removal of spdx-licenses
Quoting Helmut Grohne (2024-09-28 12:32:48) > Control: severity 1079848 normal > Control: retitle 1079848 RM: spdx-licenses -- RoQA; rc-buggy > Control: reassign 1079848 ftp.debian.org > Control: affects 1079848 + src:spdx-licenses > > Dear spdx-licenses maintainer and ftp team, > > a month has passed since filing a suggestion to remove spdx-licenses > from Debian. It was suggested for removal due to not being part of bookworm > nor trixie and having accumulated a long-standing RC bug. > * #975120: spdx-licenses: upstream source is not true source >Last modified: 3 years > > > Since the suggestion bug was neither closed nor tagged in a month, silent > consent to proceed with removal is assumed. > > Kind regards > > A tool for automatically removing packages from unstable > > This bug reply has been automatically sent with little human intervention. > If the filing is unclear or in error, don't hesitate to contact > Helmut Grohne for assistance. Please drop spdx-licenses only from unstable, not experimental (uploaded just now): I still have an interest in this, but progress is *very* slow and I agree that it should not block any development in unstable. Sorry for the late response to the bugreport. - 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
Bug#1058667: abiword: diff for NMU version 3.0.5~dfsg-3.4
Quoting Gianfranco Costamagna (2024-09-27 16:11:16) > Control: tags 1058667 + patch > Control: tags 1058667 + pending > > > Dear maintainer, > > I've prepared an NMU for abiword (versioned as 3.0.5~dfsg-3.4) and > uploaded it to DELAYED/15. Please feel free to tell me if I > should delay it longer. On the contrary: Please feel free to (re)upload without delay. Thanks, - 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
Bug#1082660: impossible to install: depends on missing librust-time-0.3+wasm-bindgen-dev
Package: librust-cookie-store-dev Version: 0.21.0-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 librust-cookie-store-dev 0.21.0-1 depends on librust-time-0.3+wasm-bindgen-dev which is unavailable in sid. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbyg1MMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhpcEQAIz6lMvQ+3MFO6Jx9pNsWpeFRYSfovtTYLEW2flZ dFU8+WF2kfysCWaDWgaMltNHsBPFBUGIijOJrkTjKrOpy40HoTyfBi4Fia5xSMg/ v6c0V0iFoxDuYyThfFHs/1Yl17EIoWvIJedH1ZSa9d95k9LPUGG1A85uM0XitenA kjfx3izp2oH5uFMXuXw94lkAXgt4x7wyulX1WrNNmWi9t23GO/CuZ8Dq5078j/lu VvOPCAPtydKqFWHP6gPERrexsgklumygoL0/IWTWpS4m9uaJcbdyOHxAYun36rZe uEjXE+pV+T0eMZJeX14rAV/7hH340sB3NrGlgijpBvmO+ValwTMEY+hvI/sJhX4o jEBnV06Hdnj63swvE5MEXMKmeSx8HxBmLODeViLb6dmusDQEv249DrSxagTbfFvA D/9VMvWJ25h4W/1ALlwq8e3PsfqoPnUyyVIb7E7JYBhQiQj2G5t6Gt9QFlD4Ypad OW9JGavjOc6gJsK2OFe/0BeMvQ38IwAJ6ZXE9xbj3x9rfBqNi/kN+82q1FtEPQqU 38mYB2UTxWbschEPt3OALsKSLLAhqzt7EnKIgit6fvQbzbbaCNJE93z6b8Ib1t+L P7Rgsxd8fGYhIYJJlIZJGJX/5xnsOKYr74undYbqZxjM6ykBsVxxnDYDIhSgdfz3 cOyj =yB+A -END PGP SIGNATURE-
Bug#1056068: RFH: resvg -- SVG rendering library (command-line utility)
Quoting noisyc...@tutanota.com (2024-09-21 23:06:42) > > If you never offered to maintain resvg then how did this conversation > > emerge? Did I try to bend your words, when all you initially said was > > "whoops" and informing me that it was a bleep on the radar soon gone? > > If that's the case then I apologize for the confusion I have caused: > > Please simply continue correcting your mistake, no need to elaborate on > >all the possible ways *others* than yourself can handle the package > > onwards. > > What I was trying to say initially was: I made a mistake and I can back off, > but given the work I already did, including the binaries and completing the > packaging is very easy (I already kinda did it at this point), so if anyone > is interested in actually maintaining the binaries (I am not) they can just > stick their names on it and have resvg+usvg back in Debian with little > effort. Unless Jonas wants to complete the packaging, in which case he should > have precedence anyway since he expressed interest in doing this for quite a > while. > > > I kindly ask you to *maintain* what you choose to maintain in Debian. > > > I do not like it if you maintain without fully maintaining, regardless > > of the amount. > > > [I] am confused why you uploaded at all > > As I'm sure you know, even if you may disagree, it is within the Rust Team's > packaging policy to only build the library and not the binaries. This is not > considered to be "not fully maintaining". I agree that it's preferable to > build everything available in the source however (especially if the binaries > were already in Debian and not totally new!), this is why I insisted from the > start that it would be nice if someone could use my work and upload the > binaries too. When you said you were not specifically interested in the > package I took it literally and thought that if no one was interested in > building the whole package, then only uploading the libraries (which on the > contrary are very much needed) would be enough. I apologize for the > misunderstanding. WTF? No, I was unaware of this additional deviation from Debian. Thanks for bringing it to my attention. Knowing that, it makes better sense that you can be talking about the option to taking over a package while not even caring to mention that if doing so, you will be ditching the executable part of it. > You saying you are interested in having the whole resvg in Debian is enough for me, I'll take care of whatever is left in NEW. Thanks. - 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
Bug#1082544: please upgrade to v0.22
Source: rust-tree-sitter Version: 0.20.10-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to, or separately provide, branch v0.22. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbvMO0MHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhHM4P/R2NJP9uEUR5OOHGugGZGSMHTOr6a+j93NviY1UO V2BzIIyTtMj2Bc14cInhMOuY4p8XKBZU1XqNBiCqjiaIzRhqYYOPzvhwNTqS4/Ki wRsAweIKsJTW0wQ8fA7EMdJx0J4oaI8k4691D4eTDBdrCOYNo0khhVVJXu2RGKHc Zg8zjcXeyuaYNZbZWDhd1SSXXA35F18jV1s9yztCrbGMIaMUIUUmUMex5N3vTMH4 v0q6dUilIwYLMIaLkgnfThfozlJrrCRlw06YVCLdBpxahY6yqX2VfD6g35TrCf/c giwnImxLkyNFzvkNDSQ1H1a/9UW/2APNozVON0QYigZqLAfel/G76kmKPJwlUETR 11zWlUyyAG3vOHcOP71T6N4bcDDwx9YYCnsxNV9WB6mIzVRhbZMNnn9pw53TVvNf 2xZnS2c/J4wwLtLMP3bC02MBZzf3pX14v03a4iE2iUGjAkbk0L2/ym4URfMucfJB MnXTYkRIeBW1BPvGXNVCS2qXnrJj3akDfmzLBNAuxGrKXatHX9IkiXV53PFe6Gay sFWknXDqGDuMyqUq5kwOVMF5koL9EtN4OqcFJzb5LCfnphzCFZYOzKc32Spvzsgk Tyr+mDwjoZEemb+vSukN19o+r2/1x6M6nhY9oaT60oNHO8CO+Uima3VA4IEcNujq NaZc =Sc6x -END PGP SIGNATURE-
Bug#1056068: RFH: resvg -- SVG rendering library (command-line utility)
Quoting noisyc...@tutanota.com (2024-09-21 21:59:50)
> Jonas, you must have missed one piece of my first email, which I report below:
>
> > Jonas, I apologize for the duplicated work. Since you've been working on
> > this
> > for a long time I am more than willing to step down from {u,re}svg once the
> > sources are rejected. I am no user of resvg and I am not interested in
> > maintaining it other than to provide the rust library.
>
> ("once the sources are rejected" to me reads as "when the sources are
> rejected", not "if", because I'd still expect rejection for the reasons I
> explained). So I agree with you, and I said it from the first time: I am more
> than willing to back off. No reason to do otherwise.
>
> Then I wrote:
>
> > if someone from the Rust Team (in cc) wanted to maintain resvg we could
> > also remove src:resvg from unstable and go forward with my (sponsored)
> > uploads. I am ok with both solutions, but I would like Jonas to have the
> > final
> > word on this given his longstanding interest in resvg.
>
> Meaning if no one from the Team is interested, provided that you still are,
> I'd rather not go forward with the uploads. If rejection is not automatic and
> I'll have to get in touch with the FTPMasters, then I will. The reason why I
> pinged you in private about this thread earlier today is precisely because
> the FTPMasters are going forward with my NEW uploads and I need an answer as
> soon as possible so I know what to do.
>
> But then you answered
>
> > I have no special interest in maintaining these packages
>
> from which I gathered... you're not interested? So if you're not interested,
> I'm not interested, no one from the Team showed up to signal interest, the
> package was removed from testing... then why should I want to re-upload the
> binaries? No issue with the long-term maintenance of the libraries, which I
> do need as a dependency, but the binaries?
>
> This being said, if you are going to maintain resvg+usvg in whatever form you
> like, then thank you as it will mean less work for me. Please confirm you're
> going to do so, this way I know how to deal with the packages in NEW.
I have an interest in resvg staying in Debian.
I have no special interest in me being the person ensuring that resvg
stays in Debian.
If you take over maintenance of resvg, and you do that by only caring
for the library, and adding back the executable and its man page only if
someone else does the work for you, then I would rather add resvg as
package number 663 in the horribly long list of packages I have taken
responsibility for.
What is the short version of the above 3 sentences? That I prefer to
maintain resvg or that I prefer to not maintain resvg?
I kindly ask you to *maintain* what you choose to maintain in Debian.
I highly appreciate that you maintain packages in Debian, regardless of
the amount.
I do not like it if you maintain without fully maintaining, regardless
of the amount. Then I prefer to pile more onto my own list. But no, I
really do not prefer to maintain more packages.
If you uploaded by accident, and don't want to maintain what you
uploaded, then I (am confused why you uploaded at all, and) want you to
simply say "whoops" and correct your mistake. Not offer to maintain the
package if you are not really willing to do that.
If you never offered to maintain resvg then how did this conversation
emerge? Did I try to bend your words, when all you initially said was
"whoops" and informing me that it was a bleep on the radar soon gone?
If that's the case then I apologize for the confusion I have caused:
Please simply continue correcting your mistake, no need to elaborate on
all the possible ways *others* than yourself can handle the package
onwards.
Thanks,
- 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
Bug#1056068: RFH: resvg -- SVG rendering library (command-line utility)
Quoting noisyc...@tutanota.com (2024-09-21 20:36:55) > > Introduction of a binary package in another source package is not a reason > > for rejection, as I understand it: That sounds like the only way to, well, > > doing > > exactly that: Move a binary package to being maintained in another source > > package. > > Sure, but I would expect at least removal of the older source package from > unstable first, or explicit consent from the previous maintainer to the > overtake. > > > So please go ahead and take over maintenance of these packages (if also > > ok with the previous maintainer, Andrej Shadura, obviously), just make > > sure that you take over all of it, not only the library parts. > > I pushed the changes to debcargo-conf's current packaging of usvg/resvg > needed to build the binaries to my personal repo: > https://salsa.debian.org/NoisyCoil/debcargo-conf/-/commits/usvg-resvg. As far > as the binaries are concerned, packaging-wise, only the manpages are missing > (and proper d/changelog entries). C-library packages are not included as they > are not built by neither package (nor they could be within debcargo-conf > IIUC). Still, as I've already expressed in my last emails, I am not > interested in maintaining the binaries. If Andrej, or tarzeau (both in cc), > or really anyone else, is interested in doing so, they can just signal their > interest and I'll add them to the Uploaders, add the manpages and re-upload > the packages (again, through to my sponsor). Otherwise I see no value in > re-uploading packages no-one is actually interested in maintaining, all the > more if they were already removed from testing. N, no no - that's not how we are playing this! Either you take over and you *maintain* the project, or you back off. Doing a one-off release of the easy part - the library only, and then instead of stepping up and doing the rest you argue that falling out of testing is an indication that it is irrelevant? Come on - grow up! I take back my endorsement. Please clean up the mess you did with your accidental one-off relase, and let people that care for long-term and proper maintenance handle it. Or do the right thing and *care* for the package! The whole thing. - 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
Bug#1082521: nmu: mptcpd_0.12-4
Package: release.debian.org Severity: normal X-Debbugs-Cc: mpt...@packages.debian.org Control: affects -1 + src:mptcpd User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 nmu mptcpd_0.12-4 . ANY . unstable . -m "relink against libell" ell restructured its API slightly, which requires a rebuild of its dependencies. There is no SONAME bump, since upstream treats the API as unstable, and Debian has only two reverse dependencies (iwd and mptcpd) which are handled manually. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbu2SsMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhTf0P/3qclMNyhDWG5ZghtY7/P3b2IdRq50D6ZrjlOmiu 5wTi+99SWXLJtdkXZu26piECxgTo3F8gtd9AhdyuwOQKDevpAv9r96HDWJArqdkz MLoe26OB5HNmv5E1M/mPECAZS2K1jqp+jLM4eudZXNMsxeeUq/Qw9KT/vXIIFvca H4TG08IXAHOlwRd66k9JiFteQmcFEdNf4Q44ucTfAxzQHSEJluopfBmtNEyly1Qq rxpQF8oWszUL0HEecUAWJZbaN9oiu/YEqf0LM8cRthRicrCTMdchA/sUVDCN7iYo OrJfASiJm3O7MA2K1E7e8xfJakeq0I0P1ohQFRZ1ON6w7iTI3Os25IOsLR2X/8Ns HNRg9eTctRXqobNyU7Czy1bSKSWocqJhIQWI3IWNEZrHRASsIfbJ7NFLfkHKUZWL qo/7z5+mk/f+bFj3hk5/bScY6t6sws557LsojNbjhCFnf+WCkgVWij9GA/baCxi0 +Ifjqv+GnM/XfAiy+FlWb3NuAYZ1MOjqwICWYgssolx8fboZ4dJX48ZN4Q4on5h4 LA4EaUZumQNWlPcrNX+M0XVp0PHxh78utOwwX4YbkftKiZgtdYbMxGLqNujOsu7e he9AK89TvuUB0C33mwyD772NXFOPXYXW/t+QJ+qBGWVizdr5uJ3MUR9NmxobMLo+ /pQi =yDJq -END PGP SIGNATURE-
Bug#1056068: RFH: resvg -- SVG rendering library (command-line utility)
Hi NoisyCoil (and Andrej),
> Right now src:rust-usvg and src:rust-resvg are in NEW and will
> probably be rejected since they build librust-{u,re}svg-dev, which
> albeit having been removed from testing are still in unstable.
Introduction of a binary package in another source package is not a
reason for rejection, as I understand it: That sounds like the only way
to, well, doing exactly that: Move a binary package to being maintained
in another source package.
While I don't expect the package to be rejected, please do anyway
immediately upload an update to your packages which provides also the
executables, to avoid bothering ftpmasters twice with a NEW processing.
Yes, I have invested quite some time into packaging these, but my time
has been mainly in building from true source (not from pre-generated
not-preferred-form-for-editing assets distributed via crates.io), and
composing a sensible migration path from previous maintenance to that
(in my opinion) ideal packaging style. I have no special interest in
maintaining these packages, however, and if your packaging style is
different then there is no need for the work I have spent time on.
So please go ahead and take over maintenance of these packages (if also
ok with the previous maintainer, Andrej Shadura, obviously), just make
sure that you take over all of it, not only the library parts.
- 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
Bug#1081747: meli: encrypting mail fails
Quoting Matthias Geiger (2024-09-20 20:31:01) > On Sat, 14 Sep 2024 14:52, Matthias Geiger wrote: > >Package: meli > >Version: 0.8.7+20240912+dfsg-1 > >Severity: important > >X-Debbugs-Cc: werdah...@debian.org > > > >-BEGIN PGP SIGNED MESSAGE- > >Hash: SHA256 > > > >Hi, > >decrypting mail now works. However, I can't send signed mail: > > > >"gpgme: Call to sign() with zero keys" > > > >The config file looks like this: > > > >[pgp] > >auto_sign = true > >auto_verify_signatures = true > >sign_key = "ECBEDBB607B9B2BE" > > > >best, > > > >werdahias > > > Hi Jonas, > > upstream fixed this with this PR [0]. > > Please consider cherrypicking this into Debian. Ah, I saw that commit and wondered if it was related to this report of yours. Let me give it a try. Thanks! - 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
Bug#1082133: please upgrade to branch v4
Source: rust-termion Version: 1.5.6-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to, or separately provide, newer upstream branch v4. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbrCPUMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh2DUP/R7mSG5xEonI5R2cquz1Ops659RYaNyUrlYnuyTR EdqBy8VdYhca2xOrQm0BOycStfO4C7JHcPxP41+SdmTeg/N/qv8YUtyrAegJULm6 4DbFE+ub2qZPC1DS4KMB95Ez7D8n+WGkzbQMN9zonAfC1ixH7dqWq3FhyBgEYyZb onGgBvjNrR+DrbxiJrI81uqAIO+iPn807Ue8cnYEVCd4uq8R1arjD57ziyfaBUBU yi0iE+dYQEBXJWN/tvpewNDmK/z7XmS4O73CGuV3woeynQsTcxVLZSoeFs5pFOgQ SK7PCMi0IetI4mRiWzthhsWLB2ZtJ/ZIGyKzA6aEqPVh9tuPCvwzaQdGylXO8Xv2 TcXeB+/pcHHyaNqdeJVJn9EyOjdVg9+iwNjbJsCmv1TgaHpzd0kEE49Ov8710acF yHd781R0losz68w7EGCe1Rc7TKkO337bg0pABRfRinNuvdwi+c3LUHiUykUXR5HF f1VRBM/+kx1XdcW6R6FgratkRXb7iuAS1G/JkDOPmK7eo6DgE3VqbPNBsqBlHRrX q0YmwZ9JTAxoidowQFYLF5JIVTEEKiES47APGN3R59U/fsC9I/W9MvM9fFedvrtL RrabXpXo/bvpvM5Jx6VAJ/Fv4XklX3XYnTsjytlWA/elk4vSD5KpQcSfv1p3kYCV 69tS =Ifz5 -END PGP SIGNATURE-
Bug#1081784: ITP: rust-human-panic -- panic messages for humans
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-human-panic Version : 2.0.1 Upstream Contact: Yoshua Wuyts * URL : https://github.com/rust-cli/human-panic * License : Apache-2.0 or Expat Programming Lang: Rust Description : panic messages for humans human-panic provides panic messages for humans. It handles panics by calling std::panic::set_hook to make errors nice for humans. This package is needed for sdml (bug#1064145). It will be maintained in the collaborative debian section of salsa, at <https://salsa.debian.org/debian/rust-human-panic>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbl1IsMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh3ZEP/0rH8DTzCr2nrg/Zcr46Z5CV5XXq24X9bygqPcFh yBazr3DNtxX9AoiE2GjDVWSVJ2MRyZ12UXKUuUqDijsI+9Mz4ZsC/qjPz9NznADJ caYEIw4tpDcm97S9BIZslrUN/kIOIZUtVV5n5oUow+oahKt3wyXcYxpd+MrSoxaR OvbI0Q/TT+EF9Z3H5pmBDPKQB+4DNg/MzQLX90l6Us7blAEa1qerdM6AkCJQ4SLr GDA+sFDBQ838kCwi+PHUj+0UwsyC6saanWNT+2scTfSs2y3dAiNWr6JX/DQm6t7n 3eJn1hMYyrJ3TUQuI1GRJ6/u1eAsuwcYB7RUztq6a/ELDmxwtLKekeNBmnIvQQgE CGDkIgHPmMbsLq6t7bCzsGO6OLVUUAnGbVRZ8qA/ncLRKkMxPNMTYL0W1CAqpFLG QKHlGcjsh/IsVGHwvV6eod0uC0tNllXLxmotL0Prh6bmjSr5izj6qkkjtAINJIHI /Lj1EoTVChRZbL5xO16XnKS5y6RV8oUOm4pGaa/kppPVOXOh5ppX6WirxuSQ4rcs bX9ugsNG1tOztoYNZynbYk3c7H6+c59tBftNMtO8qc7QUqj/Rlm+OYFQkwSQfh0o BIpNXpZgC8FvVt+8/xEaqOCalKwzaIqRJij0yWf7Qu75B1kDdwxqUj1waxX+NOrB ZSJV =vmrm -END PGP SIGNATURE-
Bug#1081778: ITP: rust-search-path -- very simple search path file finder
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-search-path Version : 0.1.4 Upstream Contact: Simon Johnston * URL : https://github.com/johnstonskj/rust-search_path * License : Expat Programming Lang: Rust Description : very simple search path file finder The SearchPath type allows for the finding of files using a series of search directories. This is akin to the mechanism a shell uses to find executables using the PATH environment variable. It can be constructed with a search path from an environment variable, from a string, or from a list of either string or Path/PathBuf values. Typically the find methods return the first matching file or directory, but the find_all method specifically collects and returns a list of all matching paths. This package is needed for sdml (bug#1064145). It will be maintained in the collaborative debian section of salsa, at <https://salsa.debian.org/debian/rust-search-path>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmblz/QMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhpN8P/Ru/THrY44pLbeM1rPOPKe+jzK7Sq1HLgK/VHPM8 dTKRjEDob8u1iTyNM7RoMR3ugS/BIrOfs41ZUlhSadNypMklXStOXQnZAjlVSLQ0 5NypokqncF4Aqk/C/d+UCR6vN0TZ1Th89jzLtG4tBpZ5a/zdXMBpH1Ffi+HbzCfx wkKyBherm/kz+P4K56NYg22f+cYZex+JcnoaOa4Nsq94ehOkB50tZ+WYndNVyuU4 +RnzYlaV9NOOvJXfXIwClQn3ZDmjpYQnh6u2Ov3yE+umyfSIZqRPDmGQKixNcBHT cic8SMAjpUPg0VSKorj10D10M7KY8ne7sN+wSsfBlmLUGgtrQA4/d5hne927wzzQ 0+maosbG4I+L+n/+skE8n2j0DCZop1FdD+HEloR+R6fY6RcY98Z2099+ELcsC7W9 eukQJYwhahdmbbmwHDW0th5J0PZaRm3bMQmJU+H5dSB/8rnvpCxu9fQ9fH74EPFp ckcRDt8NAwf6Q2QEMO8ABLooTkW4UilYDaZ7SD6OAsBnIQPWj40VFjD0lNWFMnPL HD0lovFwHE4P2Bmfqs5WzlJ2LlwDUnSBS8iygAstVi2b7EBGwXy/jVqWYp8CsczB D1iRuWEVjVKAPd4Bjj0O7cz3l/+hXiIp6KPqUNEMb9arBPTzkrbyLBg4kb0YASs0 c0yb =XgXO -END PGP SIGNATURE-
Bug#1081775: ITP: rust-text-trees -- simple textual output for tree-like structures
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-text-trees Version : 0.1.2 Upstream Contact: Simon Johnston * URL : https://github.com/johnstonskj/rust-text_trees * License : Expat Programming Lang: Rust Description : simple textual output for tree-like structures text-trees will output a tree structure in text. Similar to the ascii_tree crate, however it is more flexible in its formatting options. This package is needed for sdml (bug#1064145). It will be maintained in the collaborative debian section of salsa, at <https://salsa.debian.org/debian/rust-text-trees>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbly/IMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhRiUQAKAWIsg113ukHTH4q7HaxjsO0UthslF7EF3Dgkqw OZFNjvnGRVDF3THORALuAoXkEezXY8DlnUHjbJwVP7p+hiJXqh8tRT70g35+JEHD CeG0XmMjIYm/Dpne7wCloBtKo25kuUeQ2QG6+YMhQdaWJ2paMQgPJGWnbpzFmBgW 5kX2fYZheAw8CmUhIcDE0IWvSblXS2zvkuWzX3ZmRL0uIuYXd2dWP3CUkRzcnjiT TbRZlwv563zaESLUwJjbZZicoI9MXhkLOgTfBwXjC/pPkyeeNQJTZvDD/sZ9+Vrw fmW9sApXkIjHjLnaK2z0DBJLPdGHsWitUr5LGqEtqddwKnzfValTfeNXpfE3cFyB MMtODozHivOB0WiCLz6rZhY2nF5u6MjCUoGQ1RNhpZk1kYQ1C2jKS8LiYLiX82NQ vGyLtB7fdFUmqEW+Rm5TLnAlnlYm8IX63474j6Sq57TEJ1px06HDwMuksqzBMntt vHEzTUQv/CjO03e2x8J6QcynnHH0gY/2rT6T5rpLQ3ZC9zCMGE6gQMadT3bF19tQ eRTZKPQSdV6w59Gjm7QjP7FqK9039AuQV3ve7pORxMIcEC29tvyKjSjEie8bqmV4 /JfMaYV2gl0mHx1NnXqmudvT32jsIfLLszDGbhU0GlLFWzlBL8IkIYHgSrJkVHUD 99w/ =gBvl -END PGP SIGNATURE-
Bug#1081755: ITP: rust-serde-qs -- querystrings for Serde
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-serde-qs Version : 0.13.0 Upstream Contact: Sam Scott * URL : https://github.com/samscott89/serde_qs * License : Apache-2.0 or Expat Programming Lang: Rust Description : querystrings for Serde serde_qs is is a Rust library for serialising to and deserialising from querystrings. It is designed to extend serde_urlencoded when using nested parameters, similar to those used by qs for Node, and commonly used by Ruby on Rails via Rack. This package is needed for rust-indieweb (bug#1081745). It will be maintained in the collaborative debian section of salsa, at <https://salsa.debian.org/debian/rust-serde-qs>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmblny0MHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhpoEP/i8wMr6UrBbTglrr8DAaC40+qYf6rWVeGYopVCVw fBCLxm1F8SpXY+heZlfKD2gyRxMo+gUNjLWWaQ9+mKanoGRtl56MXZlgcOJHcn8E XQYG8nAO/nCPNZmIG4NV9qX3r8OClLc4Hk/dI81+ZYkxV/Ep5sfQ1fqjOTk0fEJp QOC5/y/CiAiGmLhAZ3ISgyIf3xxENsCom+uF5jajOShiigFeXCWtc1d4Xk9oKqUS tKsJddmT0l+waSyCoGhc//dI4dpB713vfq+5+KAcAKfPKfciOlLRy0POb/zTwy+T tYxG/1pIztCZ1Dg9EMefypsXw7B7ZH2vxy4fhzUCwje0BSMSH6lfsufq3CKKJpC6 mBN7R7dxYGlqsUhrnjHtmEOiGUyzQIwKVSBQSuNrv4zRvyeeE1/L1pQyPcv8g0al aDt+P0MDQgHnprc7PbGPYGslxcKpspUA0mmOrIJIozk7Ohpx8JuyuB+hBgYFLBgO Loa0aY1ZgaFg9c7XXQrVxy4spB4wRMKvGZb6B0CcEB6c1HUrN4jOOL1+bKYn44L0 pMFOlrI2LEOgZ2cyJlKlaOBkjOJxbNGp6pKZDMxT+Pgu0HVb73cE0aSozDm/LBQZ 56yWRVXLd/iADtXSNllzvkLJtxhuUpfNOWnGey7MnGMHIoxtCV/tufyjfnklWlVR ja4P =RTI0 -END PGP SIGNATURE-
Bug#1081745: ITP: rust-indieweb -- utilities for working with the IndieWeb
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-indieweb Version : 0.4.5 Upstream Contact: Jacky Alciné * URL : https://indieweb.org/Rust#Library * License : AGPL-3 Programming Lang: Rust Description : utilities for working with the IndieWeb The indieweb library provides a collection of tools to work with the IndieWeb in your Rust applications: * IndieAuth supporting <https://indieauth.spec.indieweb.org/20201126/> * Webmention support <https://www.w3.org/TR/webmention/> This package will be maintained in the collaborative debian section of salsa, at <https://salsa.debian.org/debian/rust-indieweb>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmblgeoMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhx2UP/1MkhAZari/PzpaOoVteDfr/1/Cwub2sD1+jTOmI nkHFaXoA4c/+hqaWGjYhuffCCkmAtsnhY3p/1O2efmi4J2wda9gaDLaRh8C9zIFH JmQL3Ey0IRk4odOAOKTUhWcXcBqVsKc9g0KSFbZ1Cl5VFtL41ZiVaO20LZa3nhtM owtP8aN6ARx/Yd9PiiWDTsMYxpzTAsgS/0UmpJnoPFq4AWCmy5VvQbX5rJjjVRMS 5ztx5IhkPtaS34m50+9zFOdvDG7WwEsn/PUNMbxwv4aHH/quknfhun3MAF26CGeL 8fLITlseiuD77XK5K6B9TlHO5KveDAt82Pfp0UzlbHem5fKaO+5NH9vYWMzBxsoi 56la2XR7sES3AMF598jWPzfK+KOyrgkcBASNhbKNz9qibcgx9Uj8r+Yy9Y1iJGx4 Y3PRL0dO0vZMCyLi7t27A3RNz9vD0BOKrwe8VsBrRiWJsRKkENUfA620pMIdQZwm bJFFraJtbbrg0IUDDc6hXCF7nbp6N75BE26U7vZCHvmbnmTzwF1imyEplL2NMbVI YBAh6a19eMgKMXQGiYzgYeanDXfECf5vKAP8/nJBCzFvQ1kyWgDFrM9Bps0JtM4X SXcDCCl6C1Tf5NsRj/24XohqI8ejtp+4vwS3Q91Su9GExbH5POkThjzDTrSVb+Qm TN2V =hu5f -END PGP SIGNATURE-
Bug#1081511: ITP: rust-yamux -- multiplexer over reliable, ordered connections
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-yamux Version : 0.13.3 Upstream Contact: Parity Technologies * URL : https://github.com/paritytech/yamux * License : Apache-2.0 or Expat Programming Lang: Rust Description : multiplexer over reliable, ordered connections Yamux is a stream multiplexer over reliable, ordered connections such as TCP/IP. This package is needed for rust-libp2p (bug#1059908). It will be maintained in the collaborative debian section of Salsa, at <https://salsa.debian.org/debian/rust-yamux>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbisKoMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhKXIP/3Qql3BvS7iBaTIMOUqiv0yxBFOQH2eyl6+Guxus gjCLF0fcST7g6Is2XsWsiuFAwKrICx0zTQA4KbJTyXzxN8MZdoOC8pvzlHlLcrBu oJvtSF6jN0BA23XVoG9wFdbapIpBtnBZcE7BvXzlQTPkkE2qxor7LVvgde2YS9pZ NHle5guPu1nhKf7jtSeqP0jg+wk19JqQlJExrDyM3P+0/BFDQlNMP6kbH5iWMgPG MDVRrdxq4b8HqV5mZBgOoA4qlp1Fr/0lQoZX+v8NsAgtlnQRWduMScMM6TWMZjOZ 53avF1apsdGzCPXv5+/6Kdv0MRdPMJ2Lk97RKftaBn3CJTceppl8wQoca+NZwJAH GAfoJDAMNmWbwszF2YMnUpjcrq6deO1jj3Wc0o/YIpMU2Qv/PBVZ0s2vqn6p/409 mSqTmsjft9IHMBKqf+tGmOX3dkkBU8gtUVSHLqWNfyjLNb/t2/5bK7tU6mnw0sB1 AMotGlI0quweLvyZWZMmDeTeFyB4wZQ3+/HgmlJnqHIOvGmur5uQaX45LIG7NkpI 9n2k2889sHdUGQAs0BdTfd3Pc48BglNrIgbYHE5ERkMJhvLwPorWbqajaQVhZXaM rVLsRTFhKpkexoFuDaOosiWrP8QCza3qHIYBx3X+GNFmPKicd5pac/Al8XxQrASH M76w =Yris -END PGP SIGNATURE-
Bug#1081507: feature bilock broken: requires patched-away feature unstable
Package: librust-futures-util-dev Version: 0.3.30-1 Severity: important Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The feature bilock depend on feature unstable which is patcjed away. Apparently the patched away feature depends on similar feature for several related crates, which are *not* patched away. Please fix feature bilock, by dropping/reducing the patch. While at it, please consider enabling bilock and unstable for the crate futures as well - those features seem tightly related. If unstable was patched away due to requiring nightly rust, then I suspect those related packages should be patched as well. Also, please document (more clearly) the purpose of patches, e.g. using DEP-3 patch headers. - Jonas -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbilYkMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhnjYP/Rirvm3SNwEgiuLbrizk3n6MWfixTnG2ykBfZPBX 7Ogy78XpK53oDt6A+hTcyZEuUZNN4WInnvWLwT4u9DqV1vUDrj4j17GIesRyik+E ddMq/LxYlSYfcBcuZCPwBxQi6Amd1rorxBu7Eae1cRX/GC2J9Tt6wH18hhp3Bbpl 9TK7yUxcVrYvY7EFQ5sFKHdZdUFRXw4z172+MEMf75aNgleH7d03ebk5zjVXf1/M 39LmtiYF1X6vViy/fidlTVedsI90CdSxMFigHysUagINujbuu7YZaqmuZK97sqww JLrURLsrGNksZiMk2LcjdivxCNxjd16q5sTrxBHc9/qe4v5mceqI7VWLT5P+tEF2 l+GP7ljm7vFV/RAo5CawaefrSpuKEOgEh3Qb44R/XyhwV8q4pHHKZFOgqwSKEMGl d9STYxLcf676EbPdMhqyTaFvn/4C+NfsL8QcpQXF5yIIcSbpqmDRZb9dCeNR4guW JuhdmaJDmoR9cSxodUCriz7wrcT9q/7e1basx9deKLK0JgYqd9k0fFAVi34JZ4u1 F+dKwTURYLho1sNh+OOFkJsKs7v7Zi7R+lj5Vbr5PFaLE/1OdsFXWgy+mOA/xXSL xCi8AW70fDFKbJILShyDyVKxKogc7e2dEBEuONlGJ1Us9Ovi1FBY3OCa9mPMBgbW 7maq =kJD4 -END PGP SIGNATURE-
Bug#1081472: ITP: rust-clio -- library for parsing CLI file names
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-clio Version : 0.3.5 Upstream Contact: AJ Bagwell * URL : https://github.com/aj-bagwell/clio * License : Expat Programming Lang: Rust Description : library for parsing CLI file names clio is a rust library for parsing CLI file names. . It implements the standard unix conventions of when the file name is "-" then sending the data to stdin/stdout as appropriate. With the "clap-parse" feature it also adds a bunch of useful filters to validate paths from command line parameters, e.g. it exists or is/isn't a directory. This package is needed by sdml (bug#1064145). It will be maintained in the collaborative debian section of Salsa, at <https://salsa.debian.org/debian/rust-clio>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbiAZwMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhtM8P/iHUhDOJ5fgJxLLQ6pBATcgubpkTedpgywbNXwqV tbfTzXEK8jBFAFBQKeMy8WgRJYKhr1r1DixeSWNxfy8YZ/u3JOrzUVxKtsOnQQlu PYtf4/1Y6SLA898XFEhHbW0DmCgvszOrCfgzVdDcNQD/552F37hf+64/e6VEa3Ac 3aI+QXxUz+4EdNiSZ5CwwLdqmh6/YLpivgqKp6wYgHrWdjMCz+CRpZPzZVxI0/0v nO2osVuy/hPjqZrM5McdtZYiBVeUvOQ0i+NuzYNlG01o1pfVsxXu/8qerO4JW3md 2qgXRJZ2QVk6e9b+/lceTkz88XNNLr0i0wGBmLvjAEeTKXBzJ1nMJMt+bYi112rO qXVpIO96AmLQ3Eao36yhJymgOtI0T+lGjsmw7a6wTWtXehC0rC6iNehQ2Yu7/CKy 6IYKaugYoK8uyEJlKt5ull8ssTTtlATTkMDP1JQptjK33fXV13bPM5EslLqABR+8 ZG/xlxlIWJC8TaJihIQjJ2Sd0+o5cFrWL0exPfaarYsV/n4mt9GAc9vBTVFKbdEY M73/s9UAr8aKAQC7J4qr2osN827VLZAlQyaVMtRQgfZOB5yr2l88i8UwWYZOZEpr mQSUlcShnoO+KXRqsGsjhIWaHYRse8+ATs4C69MfULBOeqpdv/UfMWFbBEIRoLew eAak =r8eG -END PGP SIGNATURE-
Bug#1081349: ITP: rust-mail-send -- e-mail delivery library
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-mail-send Version : 0.4.9 Upstream Contact: Stalwart Labs Ltd. * URL : https://github.com/stalwartlabs/mail-send * License : Apache-2.0 or Expat Programming Lang: Rust Description : e-mail delivery library mail-send is a Rust library to build, sign and send e-mail messages via SMTP. This package is needed for himalaya (bug#1000161). It will be maintained in the collaborative debian section of Salsa, at <https://salsa.debian.org/debian/rust-mail-send>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbgtNMMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh4IwP/Ra29TvIcBndhtkT9YabxhpRhJz9HB3Lr/4CaxTZ lgjG1eYBYGP1Ps7hz0QO+S56pwGFv4plOWni3VmoxIVKXBh4vwqEqXoLCswR3HfF iKayHbB/My3Lw/60PlrMR9MZYJG5AVihOKkqR14FMQDMFiTGhUgQqonGChgNbf4x gmehB0orckyXD5LyaO3tYqZ65PTKN7XUmQToprFbI7WJZ6tNDwv2HaQXQnr5LdaB v5zXxwpOw92Br1cNfck0rMsu6Hw+crUUw6IWul4SRILti8fpIsU8VIPyzXV2Yhsy i91XXojRNy5jfcEMk7trA785Ev568IPzA7p89qKyZoBHTjscvjfeMCoaXVz2uAv7 Zp2RwlVb3pyxibNO9NpHQaPF/XCs5U1KWOOwYeu1iAZGohYHUDuUSCyUr9slgRgb QeXyraQv2IcyqQ9ubJKatXlmqUXS4psxeWAMeUfWpZC3oBzBZUyd/Raim2DyJN5E gz0FpNP0/8MR88ngvJBUPYy3J6t6usInnuAAprGaXSPXu8IxbJMegntZfwIvnia4 pEAsJrqs7iPeIhSU3uqmbULRwipfx6uB1os4YHBrOJ4HrVBoSZW2dvrNKmJIrjTA G2bZEt41f6BPN+c5jsATDF3WE7Os2nbyJ3ac/4YCbm4eeWCEQ0T+UETHo1AZddrg AmI2 =6La7 -END PGP SIGNATURE-
Bug#1081344: ITP: rust-imap-client -- library to manage IMAP clients
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-imap-client Version : 0.1.4 Upstream Contact: soywod * URL : https://github.com/soywod/imap-client * License : Expat Programming Lang: Rust Description : library to manage IMAP clients imap-client is a Rust library to manage IMAP clients. This package is needed for himalaya (bug#1000161). It will be maintained in the collaborative debian section of Salsa, at <https://salsa.debian.org/debian/rust-imap-client>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbgr34MHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh1ucP/i9U9n0g1eLJknOxAJzVTXc/65WKrjwOUhsTSDZa mvprAvquvHfVNUVLqnIVpNPKdqXxACHwQ23fIcDLXhVX+x8cxBn1c9uid4AExCfd WzEgDOpHgl4I/6o1diNmBRe9OxuGlOl7hUFPq3Lb/vE8jTa1yxNejP1fIeTIGfC6 f8QhF1ozSNPj185DGZaY7LpJK2inCEtNWtJFJMZs1FTdU/yj2D56ZsFsDSkcXFMN o6/+Y2mxJ6HM7YymPho0jb2hKaG95huVgtD/nf5RySReGl969Tpg4r3CGk1GXS66 K3IMa4xXj4QQSHoshPj2QFkblvrflLIm4mspB0HuP85/fN5qKBxDFEa6IzHme8Vg FYUDOHwA8zmu0eot1PbVrTHHiocxxYiZ3+DjXWwE3n7N2jRLeof49hZ42JMUTc7B ayUZ6pFjyDqS3dgX0SBLTUnwVIG2WMXMGb0kPREBcEXUMcqKwSeZyEPSRX6SPWoQ bERa9t0OKhRuUjjtFbIYvHGgUgCmDP13FJ+5H706bLpfQ1CtYPhpXCfkQU/Jm2UM sWD6mrwsMIGCg1Lb/nxh5OW0af+8Dtz/rYcE1K2TamP5Yj9IAjtNorSRMz6BBKV4 SdEj3D6AYWebTg0UEtyN8OqmKxm2hKgk+mX4Ybul11/ulIu3sS2fACF3FjNOkKxU 7DRw =jvXa -END PGP SIGNATURE-
Bug#1081335: ITP: rust-imap-next -- thin abstraction over IMAP protocol flows
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-imap-next Version : 0.2.0 Upstream Contact: Damian Poddebniak * URL : https://github.com/duesee/imap-next * License : Apache-2.0 or Expat Programming Lang: Rust Description : thin abstraction over IMAP protocol flows imap-next is a thin sans I/O abstraction over IMAP's distinct protocol flows. These are literal handling, AUTHENTICATE, and IDLE. This package is needed for himalaya (bug#1000161). It will be maintained in the collaborative debian section of Salsa, at <https://salsa.debian.org/debian/rust-imap-next>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbgn2AMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh+OUP/2d0y1dphsLoq/rZB1hnPS4u7ZWk0bPhznP2ENXd PLm5w06FGytbXJL/TElHo8lkAosKLPOF0EbRxV+Z6jFbFmyJz+f/JRKbYDNEZSeB eCo27f09wiYmfutjJKhtP3Bm27s/pzN5z9V0eKkft1nAwptQgef2ENJDG/B4y+Vd TJMe+XhQYnBbYbBpnNthiywUGQ0/zKR2rKArKtjYctk2ZX2t6pA8tm6a5gmiwzGh nLWU2TOQarwAVXsaiHn/gP5KupZ6mFazYpjYjHs7pIVWIFkj5/n/6uOZukHTD08k r9U3PPuHvHYTi4u+PeoPco5gSeRzC3MrikiP6rrWVHzYeqwsj3Wpo84ico5wqtXY Z1sX/ofe6tatHd8+cWaDVUIjKH1hLpx9uIWaO8RyKZU5XFXrHghlx4kGDbYqE2No fDxc62CEz7M9og34HyUtlYgu3jQn0dVPtXgurCQxX1ea0tPT/TCUCbGFdvtzvoOP lmTQ3MuCGN1Lwv1unyj1a5xloZjIOOIeGmw2yZb+3WpJ72l1q4UZBR+h+dtZrg1/ ijWX2Witn/ADWnoVw/J+SPbOK8cQNlbkt4azHDykKNI+bsz+ciERkAtXlOYAy3/V 8io6VCBKyyOVnTC/zha9FHr5qB4Uc1j7PvfaVAVGYcPvJgtWvZ0rR6vFEDc/oTHi gCNw =0Rkq -END PGP SIGNATURE-
Bug#1081332: ITP: rust-smtp-proto -- SMTP protocol parser
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-smtp-proto Version : 0.1.5 Upstream Contact: Stalwart Labs * URL : https://github.com/stalwartlabs/smtp-proto * License : Apache-2.0 or Expat Programming Lang: Rust Description : SMTP protocol parser smtp-proto is a fast SMTP/LMTP parser for Rust that supports all registered SMTP service extensions. This package is needed for himalaya (bug#1000161). It will be maintained in the collaborative debian section of Salsa, at <https://salsa.debian.org/debian/rust-smtp-proto>- -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbgm8kMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh3QgP/1AMFQGoc+1uuIE6VNGST5yo3YLpKhRKDzHoV78L MNBhxvG1MVYQLWiEFZFTPUHt6qpdGVUa1SdiZIEsiU7542RnyMvO9zdpvGiBHR3R BOTupvsbeiytzekRHA/oUsdKwwklErzXf9MeaNGVgMuYD6QE9ihM73/+663JQTF7 R5w+vQ1ZLpmeZyuY6I21Sn2A0kdad0AQgwMStzq/WajY+n4kaxQOzdHmKRQq9Ni0 d0QJa38UAh3at7/pIHRbdvjGjzK2yzUlYwVTcnXXupRZ76FJTCtE8eAmenaSTbsZ xMiGrGqCg1f1/Bi9fYvn/Pbx7vlOhKh60ZQUazbt9Rc4cjarXs3+efltNhKE3VJH dynAyT7wT+NJUEnIwZx+zdpi9jHtHVfKYKyE+aHWzD4V9hGsWDtyEDCWl/xdvCPg YcuoT/346tgC6DFrs+5nVg6ydJeIqQZFpEEhFFK0nalZKo6EiCKi5dbaWSZSU6D1 YVEmwJ4YCNQKSCv5iiAWkr4UcjB7h14JJlB7CfWuD6S8DJKNtw0sVZTH7zjv0467 THEjdyz5HfJZAaPwgFDBYOtcdwsqwxyEqofURIWEoCMob/QTR+YOnFjzYTW064p1 HU1Y8jUyKtfs8qic05bEX2P0Nmg0onm70hfgu6Kuw23721gR2K6a2Gwne7zQ6uiR Lg2O =JlwT -END PGP SIGNATURE-
Bug#1081252: affects 1081252
Quoting Jochen Sprickerhof (2024-09-10 18:13:02) > * Jonas Smedegaard [2024-09-10 17:26]: > >Problem in that is that upstream do not use a Soname, so it would either > >result in maintaining a slight fork, or involve convincing upstream to > >care more strongly about backwards compatibility than they do now, and > >maintain a Soname. > > I would argue that it is worth doing that as it will probably happen > again. > > >What I am exploring now (after the damage is done) is if the one other > >package depending on ell can be patched to work with this change, and > >then move on without Soname for now. > > > >I have now learned that a) I cannot trust upstream in only dropping > >obsolete symbols, and b) even the removal of unused symbols cause > >linking to fail. > > How did you check that it is unused? I looked in git log when the two symbols wer removed, knowing that they were no longer needed for release 2.21. > It does not look like to me: > > $ mmdebstrap --variant=essential --include=iwd,binutils > --chrooted-customize-hook='objdump -CT /usr/libexec/iwd | grep > l_genl_attr_next' testing /dev/null > [..] > DF *UND* (ELL_0.10) l_genl_attr_next That's a smart way to check. I will sure use that in the future. Thanks! - 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
Bug#1081318: ITP: turtlefmt -- auto formatter for RDF Turtle
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: turtlefmt Version : 0.1.1 Upstream Contact: 2022 Helsing GmbH * URL : https://github.com/helsing-ai/turtlefmt * License : Apache-2.0 Programming Lang: Rust Description : auto formatter for RDF Turtle turtlefmt is an auto formatter for RDF Turtle. . For now, it... * validates that the file is valid * maintains consistent indentation and line jumps * normalises string and IRI escapes to reduce their number as much as possible * enforces the use of `"` instead of `'` in literals * uses literals short notation for booleans, integers, decimals and doubles when it keeps the lexical representation unchanged * uses `a` for `rdf:type` where possible . Resource Description Framework (RDF) is a standard model for data interchange on the Web. This package with be maintained in the collaborative debian section of Salsa, at <https://salsa.debian.org/debian/turtlefmt>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbgiY0MHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhYR4P/3KcRjPWSrCAozUkq96UOSxStreL2NB1rEOum0gD vpakDnelSPSnS85S4CevgozmzpcxSK6gcuauJof1WkBSeepBZA0Vf1xcqHQeZaa+ 5+YbN2KxfY3CcdOuXlh2+Ry8SpCpO5yiuyprsF0rzq4zgOjrJyABGXRW2Wl/CJAC qa7L0poB85aLOSwD31owyPkDmXkJXDZYvQR5KZXFBCmfyii/lScxOozH7+JDK9Sr Li84eok7T4rlKS1qGODcY+K5XxmUPUrULMi8AAbGdHfI9ZjIdzfBBcDaVU5BdslH oNpp0tyHrtMawgoLqvKXhz3fezHDrSBwihUgmgKUvWlBto2b9R+ETYYN4zKqIb20 2nt+RgT1xkpaqpBCuxJmyzrqZdJC9XwRdPAtP0zvle5I/UUpLMlb7oFNQeHaTysZ UbwfK24h9nEtoOaCfC9qQ7SShsUkX9HGVF7qs8I4am4qPZg6dpJT6z//qN5m4xP7 Ie1zZT3jf6smGBrLqDKSe4VoQHiaZ5ZvaJgs21upBv60pYl2n1AYm+yO3Ya2X0t6 pgrjoNsJgAaBvfxydCN34xHWHoDvTCE3dSlyQn0SjKhr5TuBPCZbsf51HrDymhU2 3t2WhlVLM/ZL9GH/vrh8ekuzhaHmoMVCY/f3kxKcvJ3i59y6fN9RjO4+0r4EToWu E2SG =8aZ/ -END PGP SIGNATURE-
Bug#1081252: affects 1081252
Hi Jochen, Quoting Jochen Sprickerhof (2024-09-10 11:38:04) from the ell (0.69-1) changelog: > > [ Jonas Smedegaard ] > * update symbols: drop 2 symbols, add 6 symbols > > That sounds like you should bump the Soname and do a proper transition. Yes, I should have (past tense), that is the ideal approach. Problem in that is that upstream do not use a Soname, so it would either result in maintaining a slight fork, or involve convincing upstream to care more strongly about backwards compatibility than they do now, and maintain a Soname. What I am exploring now (after the damage is done) is if the one other package depending on ell can be patched to work with this change, and then move on without Soname for now. I have now learned that a) I cannot trust upstream in only dropping obsolete symbols, and b) even the removal of unused symbols cause linking to fail. - 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
Bug#1081265: does not support ELL 0.69
Source: mptcpd Version: 0.12-4 Severity: important Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 - -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Sorry, I messed up: libell dropped a few symbols with release 0.69, and I sloppily assumed it was old obsolete ones unused anywhere - without thoroughly checking that assumption. Affected packages are iwd (maintained by me, and fixed upstream already so required just a rebuild) and mptcpd, where I've reported the issue: https://github.com/multipath-tcp/mptcpd/issues/302 Now, for the Debian use of libell, I see multiple ways forward now: a) I revert libell to version 0.68 (i.e. with 0.69+really0.68) and halt progress on libell and iwd until mptcpd supports 0.69. b) I revert libell to version 0.68 (i.e. with 0.69+really0.68) and reintroduce libell 0.69 under a new Debian-specific API, which can then enter unstable but can only migrate to testing when also supported by mptcpd. c) Someone says "pfff, that's easy peasy to patch in mptcpd", releases mptcpd in Debian with that patch, and also forwards the fix upstream. Anyone feel like the hero for doing c), saving me from rolling back the mess I've caused here? - Jonas - -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbf6AcMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhHNoQAJURF8aEBP15UgB756woFFdNf2dox9AYssZepuS8 ImUty55pdZ6IjsPwpcUDeNKsyjWufZA4zjMNRYlehwMI2xYx9eYMvFqt87XET7mY Tcj4Q1EsFcTqbUxLXrIC8VYEf2Z8BzWSRBaInPmyS85jvTmEu5S1icsa9WEYGMVC yvczm6uZVf9Eap3oPs9Xvzpbz5bQVhM4TW/TPlQDkc1FNQtbq/Fdom/5zC92xNI4 n4Mt7rNHEfxOMy1T8obkfygVu6zpW8u+AnUPRejEOQPg+JFxWa5ABBsB69cd8P8Z ZzivOYS08HzYRo6OYitJIaC3Oz1Lc3inIeaE2RBiGbx7nifmuEAK4ToMmuF5Pjd5 9HTciFa96G9F6lynHoxUcyHmLhy/CZLQIY7I+99UJZTYkwTqfCWtyW2hDpUd2rj0 ngByXpnq27tK7FJSTaWQ7f5zHx6aRdP4O5pSXh2gnzrSyzVwydR6GFyyVjLnWdwk H+a0mWR6kFavmKPPOF2EV/IkGMxR7wfOHNEwfjKpk/En2bGWb+uQST9Qbn4GL9wi KYOS2Zfeb/orcOk6nTC3lzda2ixqy0qYg0c1edNWWCVEDFUW2qA3QlNIN+FeZ51Z x2vlTiFFpJHvS9LFhDdRHHqYJU7i7eaetejJw0Wtr1PUuSvsOUkpeN5kWvMYuyiJ 3yH9 =00Ml - -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbf6ccMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhDC0QAIgQFA31UeNU2Qv7+4iuZtny1kjmhibqGaOwUQxx PHmrOrDsOMEopXQUq4MwmAup+H6hMkQUSFktV8WI0okzesmS37LuGERotxOmRQAN LsjJzrRfHbp94Ki0cr3lE3QRVbQ+7VJIBBWyep5zT3LRBzOjcT86Lir4sH+gt6j5 o0ws+0b2WjgzHwGDx97oj00xTpICu/smaunzEI6CS6yw9WMsFFFzBSkxot+ZQMxI BZeL5KhHFu1LOoXJZ27as5uxrw3Lp6BXRgOuSUMF3TeARc+A2FwCd16j1WIaEpwg bpqfzvz6Phj3bX0zzOnSIZpYgRmICCflFhb99s44LsPjxjCFrxonohSKXNCIYSE0 kkHxYlJ/9RwxIfv5BMICLADwQAAyEYuxbr+TRUS6Pg/wpbMb7KsvRRUpgzQayMyi F6Y2uTYO4Pi94fCDDyzizsfs2XD6xmbE6omvqBsRl92MWSkMzoQfI3zABUz1LohY gKRZZUkl1k6ahENMuBGUia+p5xtpzyoHAdyr8qTrc/zFK7dGm0GOMfXlkHyk+lQe RdJ38y5WiECF/RrZG9HO/tNWEXHJqq4MIwEzGlBGVsorr7YXrr97AJtin290vYfB H6d7vhV3Fdc6LrkhIHIXKOpwNpbDSZRkp9zFnWs+CrICrXy1EIeExtCTmmr4RF/u Y8QN =1E2p -END PGP SIGNATURE-
Bug#1081043: ITP: rust-notify-rust -- show desktop notifications
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-notify-rust Version : 4.11.1 Upstream Contact: Hendrik Sollich * URL : https://github.com/hoodie/notify-rust * License : Apache-2.0 or Expat Programming Lang: Rust Description : show desktop notifications notify-rust is a library for displaying desktop notifications. This package is needed for himalaya (bug#1000161), iamb (bug#1061425) and meli (bug#1001084). It will be maintained in the collaborative Debian section of Salsa, at <https://salsa.debian.org/debian/rust-notify-rust>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbcYKQMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhrF8P/2mbk14tvxFhLiKYQgVL0apXxJvM3q9i7vCKNP2E UmIHGpqxAM5j8r+icXfNnIGucd6WazCKj/LTqDmg+LsTmtbH+BeapSJ+elgzW5zE IH0xMfXDm/YX7CZ11T/9FNWksXuwGoT1iqHDrablHN4XLVyOZNtK4LvT1b5hi4eu /cRE5DoF7mu+w6v3n4GhU8Ezum7eT1K5Kvd6QQf4E09PPP0lp/y1Pbco0Rxq4goE MbemdxHvZ1gZiLzo9LRqn4Z8S89TvlLZNWkymiaaWscYRmSX7KcHnK7e34eQC/PN sHU0LqKeGbugGlB5PHcPgW5hFWP4e9erOccMVmyWvNBzrt0vdMAv1sxoftlxpoxo ZXYUr51Hn/7zul37hfZ6rOMaWl7u8KW34/tbkm1Slng6jZs6LtypzpQsdZat7CyV n/v/qSW0SNgRWjM3Vu6+IeVa75zZfurtYmdIetvdISGr9KaI14ZsSnohFP6Zy16L 9G500fE92o4dnvGEID/vpuGJD/p5FPB0M8VJyWBA2qjysIQs4TXbGbYtSFmdIb7f WOtksjYSJoMJ9qrqsn3L6Ewxn8r9szZrJRvCJ0S/ZcD5zouWOECtyYmFjIrAIWkH ivsuaF7WiohxS65TsJGCgpZIR+FygBBlrLvvZi/gqOd2TAEupwICNR0AhjZbATUe YWeU =6E2/ -END PGP SIGNATURE-
Bug#1081036: ITP: rust-inquiry -- interactive prompts on terminals
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-inquiry Version : 0.6.2 Upstream Contact: Mikael Mello * URL : https://github.com/mikaelmello/inquire * License : Expat Programming Lang: Rust Description : interactive prompts on terminals inquire is a library for building interactive prompts on terminals. . It provides several different prompts in order to interactively ask the user for information via the CLI. With inquire, you can use: * Text to get text input from the user, with _built-in autocompletion support * Editor to get longer text inputs by opening a text editor for the user * DateSelect to get a date input from the user, selected via an _interactive calendar * Select to ask the user to select one option from a given list * MultiSelect to ask the user to select an arbitrary number of options from a given list * Confirm for simple yes/no confirmation prompts * CustomType for text prompts that you would like to parse to a custom type, such as numbers or UUIDs * Password for secretive text prompts This package is needed for himalaya (bug#1000161) and radicle (bug#1073266). It will be maintained in the collaborative Debian section of Salsa, at <https://salsa.debian.org/debian/rust-inquire>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbcMOwMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEh7q8QAKmijrIoSe6K8hTDEJLzSef/oj+Bq5EglMPMr77N VCk/zlillfoX3h2AM2TwIzl0xrKzoD4jg2r6BOiv+/B9gLGaistA9eTNoA8z0pEt RD6pmKSVrJVIV/PB3tyLkA37me3JMXc5QiCR8KEO0MT9WxrrUoxV8e4TUwIOSy5N /1lcGXmT/FzJAFmA9JC3LXJdBXxBAhGb1TMoQ3zY7JjcxFfCjs3jDiSBAPjkHHX1 80SCottet6eSVB22YzdU9DuDAIbBT0BIVQUVeQ0FndbbJwwd2Icq9duoP7EwMNH6 np91e4uM8hiA2ENyR1tN/tTvsaUDKDHRbv2kw25BCoRnIv6mF4n2waMVUSqR0/E1 DBknGijTZxHSC7pQBnlvnZuK7dXQKag08I9TykimX/3EeRNBeWDnd4tB/perztQA bf8vL1Y6z/GYcuxiBvC49cElDgf++AVDfZI4l1QeWmgnTW72zttDX9WTY9gCKQLm ICGPbqtFoR9iguKqTVGIBenOZVe6Xj2kt2GIHQTb80Eo8oWVeEnVHIsw3PMl2i5X BHcbvmbPgqfhwFE4Qqtl2LpoQua9af+w+YZS5R4Q48G+ODJNUDPozX8l0jPJAs2C dGPfDkqoonQEeckK+Ttrk9hv3rfw9IstD03K3wwhTLLAwW5kqi+DjVY0J5/ktxYF IcYI =A3t+ -END PGP SIGNATURE-
Bug#1031046: Backport to bookworm
Quoting José Miguel Gonçalves (2024-09-06 18:38:28) > On 06/09/24 17:27, Jonas Smedegaard wrote: > > Please subscribe to our mailinglist and discuss more there, and please > > join our Salsa team - see details athttps://wiki.debian.org/Teams/VoIP/ > > I'm a long time subscriber from your mailinglist... and I've just > applied for a Salsa account. Nice. Then let's move the conversation to the mailinglist. - 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
Bug#1081004: ITP: rust-async-fn-stream -- lightweight implementation of async-stream without macros
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-async-fn-stream Version : 0.2.2 Upstream Contact: Dmitrii Kalianov * URL : https://github.com/dmitryvk/async-fn-stream * License : Expat Programming Lang: Rust Description : lightweight implementation of async-stream without macros async-fn-stream is a version of async-stream without macros. This crate provides generic implementations of Stream trait. Stream is an asynchronous version of std::iter::Iterator. This package is needed for meli (bug#1001084). It will be maintained in the collaborative Debian section of Salsa, at <https://salsa.debian.org/debian/rust-async-fn-stream>. -BEGIN PGP SIGNATURE- iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbbMAgMHGRyQGpvbmVz LmRrAAoJECx8MUbBoAEhDCUQAJKw/A5QwqLt1CAGizAXxhLpfFkMnCupsaljLYJt ZolaJiamKTtf6xVclpSVWP/hcG5e4PJrx//r//ORHURv10Gftm1RHyxTD7r4dy8D Oj3E4oE03HUtF/buWlHQfgc0nJvWpQG4ToWsaI8K2bCFnSO0zE/68UIhIvQPt5bz Fdg0Wk210WdhZ7/UzOIriSPtHGF796tWhCqClMY23lkNGiXHOmIfURIZChmI6qKP w4y+lgSDbCPm6nA/bQ6w2cyvoPQWg7gZKuatwCtyoZLb0s3SwMRUqxNoqNaADVDe p4869b8tZNUXTFussm2LWCrGHcQGWDF0Zg4/6qVFEVv0v9hq26vVjxxzcqwieWap vV8IE1OrorOj5gatE3Nck6B9qEwk6Z/jScyO8rqMseo1yeSdDSZ7n5L5oXRGGls4 CdPZ4FcIliQVHDBTp3jmH9ZVkOk845MpELzoSRGswaMM1OleS0xlXDMhalBXodUq MEQqVQ2xcfS5eH6ZsmHHw4Tly0MmRifdQGKu+qWOcjcXBDbrk21/WzaaMiEe5l7I XfSbZfXACC4uOXjskNaMQPxAC0c6oiICWm4JA/8nf9FxXfJ0cpKrvfQF5rhx9WlZ xGVsb30cFdsJz8zQ9ymoLJJIn8tI0KG/DlwqmWeh3Sk7gyhgvxfG3Pkmf6FX86tU 1nL3 =uOOZ -END PGP SIGNATURE-
Bug#1031046: Backport to bookworm
Quoting José Miguel Gonçalves (2024-09-06 18:11:57) > On 06/09/24 16:35, Jonas Smedegaard wrote: > > I can do the task of releasing patches-applied updates, so you need not > > be an official Debian developer to help. All you need is dedication to > > keep an eye on stable and oldstable branches of Debian, and the ability > > to*try* to apply patches. If you notice a needed patch, try to apply > > it, and that fails, then we are a team, and you can ask me to try as > > well - and you can shout out to Debian developers at large on the > > debian-devel mailinglist as well. > > > > This bugreport is about the lack of helping hands. > > I could volunteer to help, but I could not give dedicate too much time > to it, because there is not much spare time on my side. Great! Noone in Debian has promised any specific amount of dedication - time will tell if the actual time invested is adequate. > I've no problems in patching, compiling, and making packages for Debian, > but would have problems to find the appropriate patches for old Asterisk > releases and would probably would not have the skills to test if the > patches are really doing what they are supposed to do. Your skill set sounds perfectly helpful! > If you are fine with those restrictions, please count with me... just > tell me were to start :-) Please subscribe to our mailinglist and discuss more there, and please join our Salsa team - see details at https://wiki.debian.org/Teams/VoIP/ - 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
Bug#1031046: Backport to bookworm
Quoting José Miguel Gonçalves (2024-09-06 16:37:28) > I was thinking that it would be possible to go directly from unstable to > backports. Quoting from https://backports.debian.org/: "(In a few cases, > usually for security updates, backports are also created from the Debian > unstable distribution.)". What makes sense to me is to interpret that passage as "...for cases where the package in unstable is less buggy than the one in testing", which does not fit here. What makes sense to me is to pour all possible attention into getting Asterisk acceptable for testing, and only *then* consider if there is leftover energy to also offer a backport. Hint hint: I expect to easily be able to handle the task of backporting in addition to keeping Asterisk up-to-date in unstable. What is needed is someone volunteering the time to look after the Asterisk package that is boringly sitting in stable or oldstable and occationally needing a security patch applied. I can do the task of releasing patches-applied updates, so you need not be an official Debian developer to help. All you need is dedication to keep an eye on stable and oldstable branches of Debian, and the ability to *try* to apply patches. If you notice a needed patch, try to apply it, and that fails, then we are a team, and you can ask me to try as well - and you can shout out to Debian developers at large on the debian-devel mailinglist as well. This bugreport is about the lack of helping hands. Please consider helping out. Thanks for nice words about the work already done, but really what is needed here is help. Kind regards, - 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
