Hi David,
I have added versions.xml and set project_id in the config.xml.
https://lhcathome.cern.ch/lhcathome/versions.xml
Please let me know if there is anything else.
Cheers,
Laurence
On 13.01.2018 20:53, David Anderson wrote:
Laurence:
Yes. Testing instructions are here:
https
On 11/01/18 23:18, David Anderson wrote:
Most server software releases would involve changes to the DB structure
and would therefore be backward incompatible.
I would not class this as backward incompatibility.
___
boinc_dev mailing list
avoid adding too many semantics to them. The basic major.minor.patch
semantics will lead to divergence of version number between the client
and the server. This would be an argument for having them in separate
repositories. But practically it does not matter.
Cheers,
Laurence
_
before they can
switch. I would be happy with only the COM_OFF version being released
from now on and RNA world can stick with the old version until they have
evaluated the new version.
Cheers,
Laurence
On 10/01/18 17:44, David Anderson wrote:
What's the COM vs. non-COM tradeoff? Why
test this we need a production project with latest server code.
SETI@home is close to having this.
We'll start testing 7.10 at that point.
-- David
On 1/10/2018 5:33 AM, Laurence wrote:
> Are there any plans to start the 7.10 client release?
>
> Cheers,
>
he
official repository for these files? We can of course do the builds
ourself and provide the binaries but are not sure if that is acceptable.
Cheers,
Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mail
Are there any plans to start the 7.10 client release?
Cheers,
Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter
has already been done, I would recommend
building on that. For example I think you can install the build
dependencies with following command.
sudo apt-get build-dep boinc-client
Building from the deb-src will also add a few patches.
Cheers,
Laurence
Hi Kathryn,
Why are you trying to build from source? It should already be available
for Raspian.
Cheers,
Laurence
On 16/11/17 20:28, Kathryn Marks wrote:
Hi all
I'm having a difficult time building the client on Raspian. The OS is
fully updated everyday.
I've solved previous errors
Hi Charlie,
I don't see a 7.8.4 tag in git.
Cheers,
Laurence
On 10/11/17 23:27, Charlie Fenton wrote:
I have built BOINC 7.8.4 for the Mac and uploaded it to
<http://boinc.berkeley.edu/dl>. This fixes the calculation of GPU memory when
running under OS 10.13 High Sierra.
Hi Vitalii
On 05/11/17 14:19, Vitalii Koshura wrote:
What do you think, guys?
I think this is a good idea. I would also like to see the client-server
RPC documented and tested.
Cheers,
Laurence
___
boinc_dev mailing list
boinc_dev
first but at that time the risk
of VirtualBox 5.2 acting bad and tasks returning bad science results
seemed low enough.
I just wanted to make sure you weren't waisting your time. Using either
project is fine and no need to ask for permission.
Cheers,
Laurence
this
way while we wait for the changes to be included upstream. Until these
changes are included upstream, we will be using the fork.
Cheers,
Laurence
On 06/11/17 14:52, Jacob Klein wrote:
Hi Laurence,
2 things.
1) I usually only do RNA World tasks (which rarely have VMs
available
wrapper, we spent 2 months debugging it!
The issues you hit is that port 9618 is blocked for out going traffic on
your machine.
http://lhcathome.web.cern.ch/test4theory/my-firewall-complaining-which-ports-does-project-use
Cheers,
Laurence
___
boinc_
Hi,
Please note that v7.8 has not yet been released so v7.8.3 is still in
development. The PPA is a way that we can test on Linux before the
official release.
Cheers,
Laurence
On 23/10/17 10:49, TarotApprentice wrote:
I think the advice by Laurence needs to be changed:
--- Quoted
-manager
Test reports can be sent to the alpha testing project and bugs can be
reported to the Fedora or Debian bug trackers respectively.
Regards,
Laurence
On 16/10/17 00:49, David Anderson wrote:
7.8.3 has 90% test coverage and it looks good.
Any objections to releasing it?
-- David
the presentation that we are not that far from this goal.
Cheers,
Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your
r individual distributions, for several
years now.
Laurence is the release manager for Linux, I suspect he knows about
all of that. :-)
No I didn't, so thanks. Only stepped forward after the September workshop.
But even if the distro package maintainers release these versions,
they also
Thanks, I did not know about this. Is this documented anywhere? How are
the results collected? I notice that there is an absence for the Linux
operating system but as 3/4 of the resources are from Windows user, the
Windows client is obviously more important.
Laurence
On 16/10/17 10:47
can
skip 7.8.3 for Linux and release 7.8.4.
Cheers,
Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email
Hi David,
The build is failing on Fedora 28 and requires this fix which is already
waiting to be merged.
https://github.com/BOINC/boinc/pull/2092
Regards,
Laurence
On 13/10/17 23:20, Laurence Field wrote:
[This sender failed our fraud detection checks and may not be who they
appear
on 4 Feb 2015, it should have really been fixed upstream for this release.
https://github.com/BOINC/boinc/issues/1187
@LocutusOfBorg (Gianfranco Costamagna) is the Debian packager and
@Germano0 (Germano Massullo) is a Fedora packager.
Regards,
Laurence
On 06/10/17 08:50, David Anderson wrote
Hi Richard,
Thanks for the clarification. I see that the branch is in fact
client_release/7/7.8 so it is now clear to me that 7.8.3 refers to the tag.
Thanks,
Laurence
On 06/10/17 12:20, Richard Haselgrove wrote:
Commit a3b75f4 is the only difference between the two possible source
should I test?
Regards,
Laurence
On 06/10/17 08:50, David Anderson wrote:
The 7.8.3 client is now being tested.
This is a release candidate, so please test soon and thoroughly.
The changes since 7.8.2.:
- fixed bug where slot directories aren't cleaned out
- fixed possible buffer overflow when
et any other Linux distributions but support the FHS should help
those too.
Regards,
Laurence
Note: Here are the Fedora Packaging Guidelines
<https://fedoraproject.org/wiki/Packaging:Guidelines>.
___
boinc_dev mailing list
boinc_dev@ssl.
.
Cheers,
Laurence
On 22/08/17 15:43, Steffen Möller wrote:
Hello,
We cannot distribute the BOINC server package in Debian since it is not
allowed to have code redundancy between packages of the distribution,
and be it for the source packages, so we cannot have the server and
client releases
contributors,
then there will be no one to take on these roles. I have already pointed
out some for the issues in a mail that I sent June 2nd.
Cheers,
Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo
.
Cheers,
Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
Hi Oliver,
On 08/08/17 10:22, Oliver Bock wrote:
On 08/08/17 10:12 , Laurence wrote:
My comment was referring to
maintaining the release so creating the major.minor branch right after
publishing.
Does that mean you want to publish a release based on (build from)
master and only then create
On 08/08/17 10:03, Jason Groothuis wrote:
The old way is about control. The new way is about freedom.
Do the developers work directly for the project or are they autonomous
but wish to collaborate?
___
boinc_dev mailing list
Hi Oliver,
There are two different scenarios, validating the code before the
release and maintaining the release. My comment was referring to
maintaining the release so creating the major.minor branch right after
publishing.
Cheers,
Laurence
On 08/08/17 09:36, Oliver Bock wrote:
Hi
HI Oliver,
On 07/08/17 09:55, Oliver Bock wrote:
As Laurence pointed out: release branches are to stabilize
and fix releases.
This is not what I intended to communicate. When the master (which
should be stable) has the required features and been tested, a release
is made and a branch
. I don't
think we need to target any other platform but please let me know if
there are others.
Cheers,
Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit
Hi David,
You can also modify the command prompt to show which branch you are in.
https://coderwall.com/p/fasnya/add-git-branch-name-to-bash-prompt
This is useful, even when not doing releases.
Cheers,
Laurence
On 04/08/17 21:17, David Anderson wrote:
Having the branch in a separate
everything?
This means that if github disappeared tomorrow, we could recreate the
repository from anyone's local copy?
Cheers,
Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
Hi,
On 04/08/17 11:52, Laurence wrote:
We should be targeting at least Debian and Fedora. I am in the
processes of doing this.
Sorry for joining this conversation late.
For Fedora we were taking the code from the following URL
https://github.com/BOINC/boinc/archive/client_release/7.6
testing again.
We should be targeting at least Debian and Fedora. I am in the processes
of doing this.
Cheers,
Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe
. If the bandwidth reduces while the job is running, it is handled the
same way as having no network.
It should be fairly easy to do the same thing in BOINC.
Cheers,
Laurence
On 01/04/17 00:32, David Anderson wrote:
Laurence:
That would be great.
What are the additional features?
Where can I look
and recent VirtualBox versions so these issues that you report
need to be fixed or handled.
Cheers,
Laurence
On 31/03/17 01:53, Samuel Foster wrote:
Hi Everyone,
I recently made a post<https://boinc.berkeley.edu/dev/forum_thread.php?id=11538> on
the Boinc message boards about some
releases including the server
should be versioned, and bugs/features should be developed on branches.
Cheers,
Laurence
On 29/03/17 13:22, Richard Haselgrove wrote:
I'm talking about the information visible to volunteers outside the core
project staff. Small science projects don't have
GNAL, NULL,
0) = 80
clone(child_stack=0,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7f2e19cf8cd0) = 25434
exit_group(0) = ?
+++ exited with 0 +++
The log message is fine but no processes are left once it has exited.
Any
41 matches
Mail list logo
