Re: Future of GNU/kFreeBSD in the debian-ports archive
On Mon, 2023-05-29 at 18:11 +0200, Aurelien Jarno wrote: > I would like to emphasize that packages will still be available on > snapshot.d.o for anyone interested in reviving the port. And the new port docs mention the potential procedures involved: https://wiki.debian.org/PortsDocs/New -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Future of GNU/kFreeBSD in the debian-ports archive
If and when GNU/kFreeBSD is dropped from debian-ports, is it ok to drop packaging overrides for the architecture from packages in Unstable? Thank you, Jeremy Bícha
Re: Future of GNU/kFreeBSD in the debian-ports archive
On Mon, May 29, 2023 at 06:11:15PM +0200, Aurelien Jarno wrote: > Over the past year, GNU/kFreeBSD hasn't seen any significant > development. After reaching out to various individuals involved, it > seems unlikely that the situation will change in the foreseeable future. > Here are some statistics that support this observation: > > - The last buildd upload for kfreebsd-amd64 and kfreebsd-i386 was over a > year ago. > - There have been no porter uploads for kfreebsd-i386 in the past year. > - In the last year, only 11 porter uploads for kfreebsd-amd64 have been > recorded, with the most recent one occurring over two months ago. > - Only approximately 30% of the packages on these architectures are > up-to-date. - kfreebsd has not been bootstrappable in a while and I removed it from rebootstrap QA in June 2020 after a while of pings. I did not receive complaints since and no interest in bootstrapping it again. - tar FTBFS on kfreebsd-amd64 since 2016. It is bd-uninstallable since 2022. - I hope that Matthias Klose replies as he was hinting at the maintenance cost in gcc. > With my ports-master hat, I think it is time to consider the removal of > both the kfreebsd-amd64 and kfreebsd-i386 architectures from the > debian-ports archive. I would like to emphasize that packages will still > be available on snapshot.d.o for anyone interested in reviving the port. I concur. Like Jessica, working with kfreebsd was an interesting adventure to me. I have good memories of having worked with Steven Chamberlain before Jessica, thanks. > In any case, I am waiting for feedback, and I will wait for at least a > month before taking any action. I appreciate your careful way of doing this. Helmut
Re: Future of GNU/kFreeBSD in the debian-ports archive
On 29 May 2023, at 17:11, Aurelien Jarno wrote: > > Dear GNU/kFreeBSD porters, > > Over the past year, GNU/kFreeBSD hasn't seen any significant > development. After reaching out to various individuals involved, it > seems unlikely that the situation will change in the foreseeable future. > Here are some statistics that support this observation: > > - The last buildd upload for kfreebsd-amd64 and kfreebsd-i386 was over a > year ago. > - There have been no porter uploads for kfreebsd-i386 in the past year. > - In the last year, only 11 porter uploads for kfreebsd-amd64 have been > recorded, with the most recent one occurring over two months ago. > - Only approximately 30% of the packages on these architectures are > up-to-date. > > With my ports-master hat, I think it is time to consider the removal of > both the kfreebsd-amd64 and kfreebsd-i386 architectures from the > debian-ports archive. I would like to emphasize that packages will still > be available on snapshot.d.o for anyone interested in reviving the port. > > In any case, I am waiting for feedback, and I will wait for at least a > month before taking any action. Hi Aurelien, As discussed on IRC, and as the most recent primary porter, it’s time to finally let it die. GNU/kFreeBSD was an interesting experiment but things like the lack of upstreamed glibc patches made it a lot of work to keep up-to-date, and even a few years ago when I was able to actively maintain the port it was still suffering from an outdated glibc and requiring ugly workarounds as a result. It tried to be the best of both worlds, but these days at least anyone would be better served with one of the other. Thanks to all those who maintained it before me, and those that helped whilst I was doing so, whether providing patches or machines. Regards, Jess
Future of GNU/kFreeBSD in the debian-ports archive
Dear GNU/kFreeBSD porters, Over the past year, GNU/kFreeBSD hasn't seen any significant development. After reaching out to various individuals involved, it seems unlikely that the situation will change in the foreseeable future. Here are some statistics that support this observation: - The last buildd upload for kfreebsd-amd64 and kfreebsd-i386 was over a year ago. - There have been no porter uploads for kfreebsd-i386 in the past year. - In the last year, only 11 porter uploads for kfreebsd-amd64 have been recorded, with the most recent one occurring over two months ago. - Only approximately 30% of the packages on these architectures are up-to-date. With my ports-master hat, I think it is time to consider the removal of both the kfreebsd-amd64 and kfreebsd-i386 architectures from the debian-ports archive. I would like to emphasize that packages will still be available on snapshot.d.o for anyone interested in reviving the port. In any case, I am waiting for feedback, and I will wait for at least a month before taking any action. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net signature.asc Description: PGP signature
Bug#1036926: ITP: lxd-ui -- A browser interface for LXD
Package: wnpp Severity: wishlist Owner: Mathias Gibbens X-Debbugs-CC: debian-devel@lists.debian.org * Package name: lxd-ui Version : 0.0~git20230526.416dc86 Upstream Author : Canonical * URL : https://github.com/canonical/lxd-ui * License : GPL-3 Programming Lang: HTML, JavaScript, TypeScript Description : A browser interface for LXD LXD-UI is a browser frontend for LXD. It enables easy and accessible container and virtual machine management. Targets small and large scale private clouds. Canonical is working on a web-based GUI for LXD that would be useful to have available in Debian. There's another third-party project (LXDWARE's lxd-dashboard) as well -- I haven't directly compared the two projects in too much depth, but I would expect Canonical's version to likely end up the best integrated and supported. signature.asc Description: This is a digitally signed message part
Bug#1036925: ITP: python3-pylxd -- Python module for LXD
Package: wnpp Severity: wishlist Owner: Mathias Gibbens X-Debbugs-CC: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org * Package name: python3-pylxd Version : 2.3.1 Upstream Author : Canonical * URL : https://github.com/lxc/pylxd * License : Apache-2.0 Programming Lang: Python Description : Python module for LXD A Python library for interacting with the LXD REST API. I'm planning to package the python bindings for LXD. I think it would make sense to team-maintain it under the Python Team umbrella. signature.asc Description: This is a digitally signed message part
Bug#1036924: ITP: obfuscate -- Censor private information from images
Package: wnpp Severity: wishlist Owner: Matthias Geiger X-Debbugs-Cc: debian-devel@lists.debian.org, pkg-gnome-maintain...@lists.alioth.debian.org, matthias.geiger1...@tutanota.de -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: obfuscate Version : 0.0.9 Upstream Contact: Bilal Elmoussaoui * URL : https://apps.gnome.org/app/com.belmoussaoui.Obfuscate/ * License : GPL-3+ Programming Lang: Rust Description : Censor private information from images I intend to package obfuscate. It's a neat little program to censor private information from images. This is useful if you hace to send sensitive information to gouvernments for instance. As of now it is missing two rust libraries I already prepared and a subsequent update of the gtk-rs stack. This package will be maintained under the GNOME teams' umbrella. thanks, werdahias -BEGIN PGP SIGNATURE- iQJUBAEBCgA+FiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmR0rqggHG1hdHRoaWFz LmdlaWdlcjEwMjRAdHV0YW5vdGEuZGUACgkQGL0QaztsVHWwvw//XU+O1bTIvziV QUlYaORwPo2tuzOls0spbsrZuZG3pt71cvRzK3SlorBTIXXXQAMTgjV8r4PkvaXY w2b7HL0Y76HjXOZyrBMcs/vmSvt5xS4IxCMsiAs+yxI9OO98j9sn4kszsCC842ge uwogrpn4odGlajWke5P1OZUAJ//FsboRnQrQI8RYFEhxGeARNYw1a046l/ocbWEB zwVrpc6X7wDgG/x64UfLUchPybAUetKpXMuFLNgkeFzScuQaX7hTg+yNOVD9D+By 51CGYGEkx3vxIRGnScA+dtG52hPh7I5qsOm8aTWF7TLd98dLVgvFCZum3cqBGQ+H YsMch/ak9sLnqtgYj7fOa+Oxc7E0ydz+FTdGa3uJpghNPAvLpymKf2xk0HIbq+ao 9+e+e9RhTqJw6HW7gcww4i8ybX25nnb0AD+dVAv2CYt+FBo9xnnulrUVVljk9dng hRQ5C129RmtBoXp1LVy/65vEDisuxJLSbTsc3LCyLx2mcI6HOwO2Fkl1RvOfK0O7 TAEGTMPUSoGcq4Ii2+SEiauTvl906znIxDr88OzeQz4oFi6U/JE/Kg/4v9698jKE FkzLb6pTCgjkChPEB2h2ZHHSc78ZSYoAOTNkepDqc2dQoT93gIF6msu6AOdqf5V5 04JGpkBBnytVHSjYbwhuEquO1ENWSaA= =WUh6 -END PGP SIGNATURE-