Debian stable ships 7.0.27, backported is 7.0.65. There is a deadline for a stable point release upcoming next week for which there could be an update, if we really want this to happen. The version distributed via backport.debian.org I could update any time.
Steffen > Gesendet: Dienstag, 28. Januar 2014 um 21:08 Uhr > Von: "Rom Walton" <[email protected]> > An: "Steffen Möller" <[email protected]>, "Jon Sonntag" > <[email protected]> > Cc: "BOINC Developers Mailing List @berkeley.edu" <[email protected]> > Betreff: RE: [boinc_dev] GLIBC 2.15 required for BOINC Manager? > > At this point, our builds are built against Ubuntu Precise Pangolin(12.04) > and use whatever version of libc it does. > > I figured I would have to setup a new build machine to support wxWidgets 3.0 > for the BOINC 7.3/7.4. > > Does Debian stable include a recent version of BOINC? > > ----- Rom > > -----Original Message----- > From: boinc_dev [mailto:[email protected]] On Behalf Of > "Steffen Möller" > Sent: Sunday, January 26, 2014 5:36 AM > To: Jon Sonntag > Cc: BOINC Developers Mailing List @berkeley.edu > Subject: Re: [boinc_dev] GLIBC 2.15 required for BOINC Manager? > > Hi Jon, > > > Debian 7.3 (stable) uses glibc v2.13, Debian Jessie (testing) uses > > v2.17, and Debian Sid (unstable) uses v2.18 so it looks like they've > > changed their minds. However, at present, the only way to run the > > current BOINC client on the current Debian version is to use either the > > "testing" or "unstable" > > sources. > > If I got this right, then you are saying that the binaries provided for Linux > by Berkeley are not usable for the stable Debian release, right? > Hm. I had accepted the message from past postings to some BOINC mailing list > that Debian's BOINC packages we are providing is not usable for everyone, and > my latest upload to backports.debian.org is (admittedly) a while ago. > But from my side I would not mind if the Berkeley developers left the support > for Debian stable to the Debian people - just, I personally do not run stable > and it is tedious for me to test it all, so I am not too keen on frequent > updates. > > > That, or download and compile your own BOINC client. I don't think > > most end users can or are willing to do that. I don't care too much if > > the latest BOINC version doesn't work since I usually wait until a few > > others identify all the issues with the current version so I can > > decide whether to upgrade. That is, unless BOINC keeps nagging me to > > use a version that I know won't run every single time I launch the > > BOINC manager. That gets to be really annoying.) > > Hm. This is exactly the spirit that backports.debian.org should help everyone > with. > > > Yeah, I know Debian isn't as popular as it once was. In fact, since > > only RHEL, OpenSUSE, and Ubuntu are supported by nVidia and AMD's GPU > > toolkits, why not switch the official BOINC server VM's (and > > instruction on the wiki > > pages) to one of those? Then the same VM image can be used to build > > and test client apps as well as run the server. > > The NVidia packages shipping with Debian work nicely. Concerning support, > with Valve's StreamOS distribution deriving directly from Debian, I have some > good confidence that a continued bet on Debian is a good one. > > > I'd be happy to help with > > Same here. > > Cheers, > > Steffen > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
