[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

unblock boinc/7.0.34+dfsg-2 (was: Bug#685248: unblock: boinc/7.0.33-1 and boinc-app-seti/6.12~svn1385-1)



Hi,

Is there any progress for this unblock request?

boinc is in NEW, and we've responded to FTP Masters' (Luca and Ansgar) request by doing some fixes, updating boinc to 7.0.34+dfsg-2 which conforms to FTP Masters' requirement. Now we (FTP Masters and BOINC team) are waiting for you comment on our unblock request.

unblock boinc/7.0.34+dfsg-2

Cheers,

Guo Yixuan

On Sun, 19 Aug 2012 03:27:08, Steffen Möller wrote:
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package boinc and boinc-app-seti

Right. Why do I want the two packages to be in unstable. Hm. Firstly,
I think the two belong together. The BOINC Debian packages allow everyone
to inspect what they run on their machines contacting external servers.
And the same for those otherwise uninspectable apps from third parties.
Boinc-app-seti is the boinc application with far the widest distribution
across platforms. The packages are iconic for what Debian can achieve
for platform compatibility.

The previous (nicely working) version of SETI was removed when BOINC
was removed because MySQL had been removed (the dependency to it has
now been removed together with the boinc-server-maker binary package)
and the fglrx was not in Wheezy (dependency removed together with the
boinc-ati-opencl package). So, please allow SETI back in. It was removed
albeit being innocent in the first place. We were nice to the package in
the meantime, kept the orig.tar.gz.  We now also gave it the opportunity
to link against the shared library that the boinc-client kindly provides.
With BOINC back in, and me having my key back in the keyring, we saw
builds on PowerPC to fail because of altivec being detected but no
underlying library to support it being available. New upload needed -
this one. The PowerPC issues came together with upstream saying they had
issues with the home-built SETI clients, which has now been resolved
again. We then thought that together with the fix for the PowerPC we
should go for the only slightly changed upstream version.

Kibi was kindly allowing BOINC 7.0.27 in, which had ben stalled in
unstable, also because of the PowerPC platform albeit for a very different
reason, long before the freeze. With much hooray this transition was
announced to our Ubuntu downstreamers who were already using 7.0.33 (from
our git repository ! ) actively in their PPA and they are happy with it.
They wanted to keep all those latest changes that upstream has addressed in
..28-.33 and would not want to go back to .27. Saying it would have fixed
many of the issues their Ubuntu early adopters have found.

boinc took a dive on popcon
http://qa.debian.org/popcon.php?package=boinc
when the package was removed from testing. This was very sad to
see. 7.0.27 gave it just a small kick back .. wishfully interpreting
the graph .. That version gave some serious bit of compatibility for
GPU computing that .24 did not yet have. 7.0.33 is especially good for
many smallish bit with the user interface, so the Ubuntu folks, which
is rather detectable for the regular user.  7.0.27 does not yet
provide the libboinc-app which the scientific apps like SETI link
against. Previous versions of the scientific apps, like the ones that
one would receive through the boinc-client from the respective external
project server, were all linked statically. I had considerably disliked
that static linking for a long time and am very happy to know this now
gone. Please let this development swap over to Wheezy.

The more ambitious boinc-server-maker we finally came to accept that
it is not up to the standard for being part of the stable release.
We'll continue maintaining that for experimental and hope for some
success stories on those for Wheezy+1.

Cheers,

Steffen

unblock boinc/7.0.33-1
unblock boinc-app-seti/6.12~svn1385-1


Reply to: