Re: debian-installer now available in Ports
Steven Chamberlain, on mer. 12 avril 2017 13:55:08 +0100, wrote: > I expect there might be problems trying to build linux arches from a > kfreebsd host. But we should try to find out, and then maybe fix it. FWIW, I have been building hurd-i386 images from a linux box for a long time without problems. Samuel
Re: changing the java default to java7, and dropping java support for some architectures
Matthias Klose, le Mon 06 May 2013 16:22:30 +0200, a écrit : - hurd never had openjdk support, and afaik, nobody is working on that. There has been work towards this, notably by Jeremie Koenig. I don't know the status, we just have not made it a strong priority so far. Samuel -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130506143659.gf6...@type.bordeaux.inria.fr
Re: GCC-4.5 as the default for (at least some) architectures
Kurt Roeckx, le Tue 26 Apr 2011 21:28:57 +0200, a écrit : Is there a reason not to switch the remaining (release) arches (ia64, kfreebsd-*, sparc, s390)? Maybe hurd-i386 too? There's no real reason to defer hurd-i386, as it's basically like i386, and the key packages (glibc/hurd/gnumach) already use a fixed version and can be handled independently. Samuel -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110426204147.gs4...@const.famille.thibault.fr
Re: DSO linking changes for wheezy
Steve Langasek, le Tue 16 Nov 2010 09:14:40 -0800, a écrit : I don't argue that this makes --as-needed *correct* as a default, but I think it's clear how using --as-needed may benefit a distribution in terms of reducing churn when library dependencies change. We agree on the second part, but the change of behavior makes it unacceptable as default, thus making the second part void. Samuel -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101116174307.gk5...@const.bordeaux.inria.fr
Re: DSO linking changes for wheezy
Florian Weimer, le Tue 16 Nov 2010 19:49:57 +0100, a écrit : * Roland McGrath: I can't see why you think --as-needed is fundamentally wrong or unnecessary. It is fundamentally wrong because -lfoo means I demand that the initializers of libfoo.so run, whether or not I called anything in it. So it's more like static linking. 8-) ?! Initializers are called dynamically, and if you upgrade the library, the new initializers will be called (and new ones will be called as well!). I don't see what you see static here. Samuel -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101116191430.gf5...@const.famille.thibault.fr
Re: DSO linking changes for wheezy
Matt Turner, le Mon 15 Nov 2010 19:51:10 -0500, a écrit : On Mon, Nov 15, 2010 at 7:24 PM, Roger Leigh rle...@codelibre.net wrote: What's the actual problem --as-needed is trying to solve? The answer is mainly unwanted libraries being linked in as a result of using pkg-config (and various other -config variants), though there are other, lesser, culprits. The pkg-config .pc files for gtk, gnome and other libraries add in many libraries, most of which aren't typically needed. The solution: fix the .pc files! Using --as-needed is merely papering over the actual root problem. It fixes the symptoms, but it's not addressing the actual cause. The number of packages providing broken .pc files is not large, and the number breaking due to relying on this brokenness is likely just as small. I can't see why you think --as-needed is fundamentally wrong or unnecessary. Check out http://www.gentoo.org/proj/en/qa/asneeded.xml --as-needed has saved tons of time for upgrades like Cairo in Gentoo, where Cairo had been linked to glitz which is now useless and gone. Not a problem, if Cairo was properly exposing the dep. So when people upgraded Cairo, all the software that linked against it (and also unnecessarily linked against glitz) Why did it get linked against glitz? That's where the problem is. Samuel -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101116011555.gt6...@const.famille.thibault.fr
Re: Future of the s390 port
Russ Allbery, le Thu 03 Sep 2009 13:32:46 -0700, a écrit : In specific, our information security office (rightfully) considers the relationship between system and list of installed packages to be confidential data because of the potential use of such data in determining which systems to attack following a publicly announced vulnerability. Could perhaps an almost empty popcon report be considered as valid at least just for the number of installed systems? Samuel -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
