Re: DSA concerns for jessie architectures
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/22/2013 07:26 PM, Martin Zobel-Helas wrote: > * sparc: no working nflog (mild concern); no stable kernels in stable > (compiling clisp for instance crashes the kernel reliably on smetana). We > need to run sparc with oldstable kernels to provide stable machines. > That's not an option for long. I think all machines except stadler and sompek are US IIIi machines. The problem with US IIIi is, that sun never published the cpu specs - they would have done it if somebody would have paid for the lawyers to look trough them before publishing. US IIi support was implemented by a student working at SUN under NDA and US IV and later was published. So I think if dropping (official) support for US IIIi CPUs would keep the port alive, we should do that. Running Debian on the more recent machines makes more sense anyway imho. The older ones are nice, but they consume a lt of power. - -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJR7DExAAoJEOs2Fxpv+UNffpcP/2Rs12KtUr1R8Fj/SUFsGTGi Qq4IyIsq6T9+0be/Q2NT+8vKhqy9eAfLIGPYfEfMP/gQUXHxqURF7452FCum5pCe PPbhpGMFL67rX9I9tdNbYGEcD6KnHksHc64PaV4FkCd5W/dvQzaVHxfP5I7TjFL2 JQVrfqYTi546kPN7kqo6YhNNC+jFRBJOxB+2RhdEddg12xU9/08/YIy865qJqXSP 0X+xBfiGu040AKUC+Ml4ZjFGKDnCOKhuuAKDYnyZLjLSFjTkE00WowKDS8JmJRLC ls89Xha2K4Sk01io+f4iermCjRsHD/GvS4mNIG5HsEQYHROdWoCFNRl4hAdGI0zZ CvFnxaJLwQ+cd0dsoFO/OkuRLTYOrjHKTniOjrWcgaOl0L6C6K4Jhyh+jpl2GmO/ sUs/K3jtUBos5Q1ojetmm/rAXjEFe3giOokosUP1DOB8fWUnYqRDYf5ODOeEucot nzl6lfvp+g2nQVQAAOqpSqxCYYhue23Mg8ZYfW1L/I8mNIvClrcSVfHAAP3URQeY eDGoyPNX6AIYiFX8J121ynfMa/TujGURfoPcQWWGFb3NyJ4/RM/FrTAAseldcIlW 2nfpRUX118LEYLQ6Jj4JQn7Ci6lL+SUgI2HfSRu/5a1aoBrEVhVF5ItUbMU6B0Vx YTnzPB7WteSULAbu90Iz =H+fH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ec3137.1020...@bzed.de
kfreebsd - open-vm-tools support
[ please CC me as I'm not subscribed! ] hi porters, after picking the "try to support kfreebsd" patches from vmware in the open-vm-tools package some time ago I thought it would be a good thing to give them a try and see if it builds fine - unfortunately it does not: https://buildd.debian.org/status/fetch.php?pkg=open-vm-tools&arch=kfreebsd-amd64&ver=2%3A9.4.6-1770165-2%2Bexp1&stamp=1408226611 Unfortunately i don't have the spare time to fix the package to build properly (fixing vmtoolsd and friends is not enough, a -module package needs to be created, too...) - but I'll happily accept pull requests and patches, sources are here: https://github.com/bzed/pkg-open-vm-tools If you'd like to work on it but you don't have access to a vmware vm to test the package please let me know. Cheers, Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53f06570.5060...@bzed.de
Re: Debian Buster release to partially drop non-systemd support
On 10/13/18 12:58 PM, Holger Levsen wrote: > On Sat, Oct 13, 2018 at 06:01:43AM +0100, Ben Hutchings wrote: >>> Has policy changed regarding support for multiple inits, or is it just that >>> no one is maintaining the shim and sysvinit-core? >> >> The latter. systemd-shim has been orphaned for over 2 years, and has >> RC bugs. sysvinit currently has two maintainers, but they've only >> ever made one upload (over a year ago). > > It seems that these facts are either largely ignored or unknown and I > wonder if some noise should be made so that interested people can pick > up the work now and not only complain later. I don't think that is only the smaller issue we are facing here. The bigger "problems" for those who do not like systemd will be: - the typical package maintainer won't test initscripts - more and more upstreams are shipping systemd services only and skip init script creation. For my packages I can state that I do not have a single machine which is not using systemd - and to be honest - I won't waste my time in writing/debugging initscripts. If there is one, I'll review it if it looks sane and then maybe ship it. And I'm saying "maybe" here, as for new packages, I will NOT shit it as active init script because I will only put stuff in my packages I have tested well enough. After using a lot of systemd now I will never go back to init scripts. Systemd comes with a steep learning curve, but one you've stated using its features you'll never go back. -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F signature.asc Description: OpenPGP digital signature
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On 4/12/19 11:01 PM, Samuel Thibault wrote: > I was hoping to do a non-official relase of Debian Hurd along Buster as > usual, but a change of archive, which means uploading packages, fixing > scripts, etc. will take a lot of time, which I simply just will not have > within the coming two-three months (I am already struggling to find time > to do what I engaged to). While I appreciate your efforts, I have to be honest and say: If there are no other people to help here, you've just proven that this architecture should be moved to ports. Nothing will stop you from releasing a hurd buster release using ports. -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On 4/12/19 11:21 PM, Samuel Thibault wrote: > Time will. I will have time later, but that'll be after the Buster > release, i.e. a *way* less coherent set of packages since a flurry > of package updates will happen, thus less usable, if installable at > all. The only alternative I have is to make the release now with the RC > bugs. There is no real difference between the normal archive and ports. Uploads will happen after buster was released. If your binary packages are built on official debian machines or the debian-ports machines does not make a big difference. -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
