*** This bug is a duplicate of bug 1009536 ***
https://bugs.launchpad.net/bugs/1009536
Hello Dave, or anyone else affected,
Accepted boinc into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/boinc/7.0.27+dfsg-
5ubuntu0.12.04.1 in a few
*** This bug is a duplicate of bug 1009536 ***
https://bugs.launchpad.net/bugs/1009536
** This bug has been marked a duplicate of bug 1009536
Ubuntu 12.04/7.0.24/ Seti@home
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Hi. Repository versions 7.0.24, (I assume 7.0.25) and 7.0.26 have a
- known bug which affects users with various hardware running Ubuntu
- 12.04. The bug makes the boinc software unable to process any work-
- units.
+ Hi. Repository version 7.0.24...precise has a known
** Description changed:
Hi. Repository version 7.0.24...precise has a known bug which affects
users running Ubuntu 12.04. The bug makes the boinc software unable to
process any work-units for some projects.
This is a known bug by a growing group of Seti@Home Boinc users running
Items marked with an [X] have been confirmed/tested.
* precise:
[X] Package builds without modification
[X ] boinc-manager installs cleanly and runs
[ ] boinc-dbg installs cleanly and runs***seemed to install cleanly,
unaware how to run it.
[ ] boinc-cgi-stripchart installs cleanly and runs
I've tested the SRU package from Micah's ppa: (7.0.24+dfsg-
1ubuntu0.1~ubuntu12.04.1~ppa1 boinc package), and it seems fine.
I do not see the computation error bug, or any other issues so far.
(I'll mention again I do not use a GPU for crunching so I cannot speak
for that)
I haven't had time to
I think it's funny that after we decide to get the fix into quantal for
a backport to precise, then they go the route of an SRU fix. LOL
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
I don't wanna beat a dead horse, but can someone update here if/when
apt-get install boinc will install the working 7.0.27 in Precise?
thanks. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Hi Dave a bug has been opened against backport [1]
please test ppa [2] and tell which of test case from bug 1000492 works :)
thanks
[1] https://bugs.launchpad.net/precise-backports/+bug/1000492
[2] https://launchpad.net/~micahg/+archive/sru-test/
--
You received this bug notification
** Changed in: boinc (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
7.0.24 computation error bug
To manage notifications about this bug
** Bug watch added: Debian Bug tracker #672328
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672328
** Also affects: boinc (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672328
Importance: Unknown
Status: Unknown
--
You received this bug notification because
the fix in Quantal is released, the package will be in Quantal as soon
as the synced version is published in the repos (should be very soon).
I'll get to work on backporting this to Precise, so the people who are
having this problem in Precise can have a (fixed) version. But someone
should check
Thomas I'll check it out. Is there a link or somewhere I can see the
repository package status, like when I was checking Locutus' PPA waiting
for builds to finish?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirmed with MOTUs and the archives that the version from Debian is
imported already.
You can just install it in Quantal.
The Bad patch is in the package, so the package'll need ubuntu-only
changes, I'll work with the MOTUs on that, but I'll need a summary of
why that patch is bad (i dont
Check, though, to see if the bad patch is still a troublemaker, if it
is, file a bug specific for that patch's removal with the summary, i
think i can get the ubuntu-only changes to be sponsored if there's a
linked bug.
--
You received this bug notification because you are a member of Ubuntu
Actually, on further checks, the package correctly builds in Quantal
with the trouble-patch included.
LocutusOfBorg: Do me a favor and pull a copy of the package as it exists
in Quantal, and see if it builds. Since it (so far) builds correctly
with the 'parse_issues.patch' patch you referenced
well whichever patches are enabled or not, I am not getting the
computation error in Quantal-64 (virtual box). Crunching away at a unit
right now.
I can gladly report. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
Original-Nachricht
Datum: Sun, 13 May 2012 16:54:19 -
Von: Thomas Ward tew...@trekweb.org
An: steffen_moel...@gmx.de
Betreff: [Bug 991179] Re: 7.0.24 computation error bug
I confirmed with MOTUs and the archives that the version from Debian is
imported already
Steffen, the patch reported to have the problem, the
'parse_issues.patch' exists in the Quantal package, and the Debian
package (I dissected the package myself, its still there).
Backporting to older than Precise may be a tiny bit difficult, but
before I help out wiht the backports to Oneiric and
Just for clarification. I believe that patch Thomas refers to was believed
to be causing issues building the package for Ubuntu.
The patch found to cause the computation error was
moreinformativeappstart.patch or something like that.
On May 13, 2012 3:25 PM, Thomas Ward tew...@trekweb.org wrote:
That was the confusion, because Locutus referred to a different patch.
On May 13, 2012, at 3:31 PM, Dave xclusive...@gmail.com wrote:
Just for clarification. I believe that patch Thomas refers to was believed
to be causing issues building the package for Ubuntu.
The patch found to cause the
repository .. and that apparently just
builds.
Cheers,
Steffen
Original-Nachricht
Datum: Sun, 13 May 2012 20:45:54 -
Von: Thomas Ward tew...@trekweb.org
An: steffen_moel...@gmx.de
Betreff: Re: [Bug 991179] Re: 7.0.24 computation error bug
That was the confusion
Sorry for misunderstanding I wasn't so clear.
This bug is triggered (as Dave said) by moreinformative... patch.
This patch has been removed upstream so no changes ubuntu1 is needed.
I personally DON'T want to diverge brances of boinc from debian to
ubuntu, the collaboration between those distros
This bug was fixed in the package boinc - 7.0.27+dfsg-3
---
boinc (7.0.27+dfsg-3) unstable; urgency=low
* Now truly reconstituting compatibility with SETI
(Closes: #672328, lp: #991179).
* builds with gcc 4.7 (Closes: #671999)
Thanks to Matthias Klose for his patch, had
Hello, yes, and I had one report from Debian in the meantime, too, who
had already confirmed this version to be fine with him (and SETI).
Cheers, Steffen
debian/changelog for the version being synced to quantal (notice where
it closes this bug, which is number 991179):
boinc (7.0.27+dfsg-3)
Hi guys. Thanks for the verify Steffen.
Thomas if you update here when a repository change happens for Quantal:
I have got my server's virtual machines up and running today (since my
server's change to 12.04) and I installed a Qualtal-desktop-64, so I can
test the updated quantal-64 boinc when it
Boinc 7.0.27+dfsg-0 building in quantal.
https://code.launchpad.net/~costamagnagianfranco/+archive/boinc
So I think we are ready for a SRU just now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The MOTU SRU team isn't going to support an SRU in this case (because of
a version change, according to the MOTUs I spoke to yesterday). They
are more likely to be willing to support a sync to Quantal for the
Debian version of the package, and then a backport of that to Precise
(the repository
Isn't this last build the debian package? Or does it not count because
it's GIT?
At least if we get the package in Quantal, its a start I guess.
But don't be surprised if people keep saying things like:
I encountered the bug and was quite unhappy with it... I gave up on
Ubuntu/Kubuntu and moved
Sorry for that, I have not the power of Master Of The Universe, so I
can't help for that.
The only thing you can do is to help in downloading the official package or use
my ppa
https://code.launchpad.net/~costamagnagianfranco/+archive/boinc
I'll try to keep it up to date and bug free.
--
You
It's not your fault locutus. You have been more than helpful, and we
figured out an issue. There is nothing more you can do. :-)
I just get mad at those flamers on my end of the net. I'm defensive of
Ubuntu vs other distros because I feel it has the most support...
Anyways I'll keep the Ubuntu
I tryed to be menber of bug squad, but I wasn't ready. now I'm learning
a little bit, and one day, maybe after my master degree I'll try to
apply again for bugquad and maybe for the official boinc ppa here... But
now I have to do my master thesis and the time is always a problem :) I
need a 25
Dave: no problem, happy to help where I can.
All: I'm testing whether the package would build with a direct sync from
Debian, and then am testing the backport locally, i'll help get the sync
request and backport requests done for ya.
--
You received this bug notification because you are a
Sync request from Debian Sid to Quantal for 7.0.27+dfsg-3 (in Debian):
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/998195
Once this goes through, i'll look into getting this backported to
precise-backports
--
You received this bug notification because you are a member of Ubuntu
Bugs,
And it's verified that package doesn't have the bad patch enabled?
On May 11, 2012 3:20 PM, Thomas Ward tew...@trekweb.org wrote:
Sync request from Debian Sid to Quantal for 7.0.27+dfsg-3 (in Debian):
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/998195
Once this goes through, i'll
Dave: that will need testing, but afaict the changelog for the version
in Debian closes this bug here.
lemme get you an excerpt.
(also, assigned to myself since i'm working on the sync request and the
backport, which will ultimately close this bug)
debian/changelog for the version being synced
bah, IRC lingo.
afaict should be as far as i can tell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
7.0.24 computation error bug
To manage notifications about this bug go to:
** Changed in: boinc (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
7.0.24 computation error bug
To manage notifications about this bug
On 05/10/2012 06:48 AM, Rocky37 wrote:
Just checked for updates and was surprised to find 7.0.27
Many thanks to you all for this wonderful fix -- Hugs to all
Hey, great! Nice to see you happy. Thanks also from my side to
Lotus, Dave and the folks behind the PPA build demons.
Is it
On 05/10/2012 06:19 AM, Thomas Ward wrote:
7.0.26 isn't in Debian, so I'd have to poke around with the MOTUs to get
that into Quantal, if not take the source and repackage it for quantal-
proposed.
Once Locutus can confirm whether or not 7.0.27 builds in Quantal, I'll
go poke the MOTUs. I
Steffen:
Referring back to my earlier comment regarding SRU, to update the
Precise package (and get the updated version into the precise-updates
repository), an SRU request would need filing. I went and talked with
one of the SRU team, and they would want a version to exist in the
current
Correction: I won't bother them until at leat Sunday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
7.0.24 computation error bug
To manage notifications about this bug go to:
Well, I can't really comment on thatbecause I haven't been able to get
12.04 Release to install on such a system. The desktop installer panics right
away, the alternate installer panics on first boot after its done.
Its supposed to be my Windows desktop, but I had envisioned virtualizing
Between you and I, I agree 7.0.27 should be in Precise.
But the process for updating stable versions is complex, in that unless
the fixes also exist in the latest development version, they will rarely
push the stable release update.
I ran into this with six other packages, so I speak from
damn it, that email was addressed directly, stupid reply button.
Anyways, I'm poking the MOTUs or SRU people to comment on this bug, and
Im going to beat my email client.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
also: minor correction: six should say several, my email client doesn't
like the word 'several' for some reason.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
7.0.24 computation error
It seems like there is a plan here kind-of.
-Steffen compiles 7.0.27 without the patch affecting ubuntu.
-Locutus figures out how to get it to build for quantal.
-It gets put in as quantal's boinc package.
-We then file the SRU, and push this to Precise with good cause.
Am I missing anything?
On
I'm going to let the SRU team and/or MOTUs comment here, i've asked them
to outline the procedures on this bug, they'll give you a working plan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
New Updates:
It may be prudent to deal with the Quantal side first.
The issue on Quantal is that 7.0.27 has an issue of FTBFS (Fails to
build from Source). It may be prudent to talk to the MOTUs and see
whether they'd support a sync to Quantal with the FTBFS included, and
then backport from
NOTE: Comment #110 The thing doesnt like Debian bug numbers.
This link refers to that Debian bug: http://bugs.debian.org/671999
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
7.0.24
I'm reallly trying to figure out how to free up a machine for
quantal. I may be able to, but I'll only be able to test i386.
There's also virtualbox, but I don't think that's sufficient for
testing...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello,
On 05/10/2012 04:05 PM, Thomas Ward wrote:
New Updates:
It may be prudent to deal with the Quantal side first.
The issue on Quantal is that 7.0.27 has an issue of FTBFS (Fails to
build from Source). It may be prudent to talk to the MOTUs and see
whether they'd support a sync to
9:32 AM
To: benjg...@yahoo.com
Subject: [Bug 991179] Re: 7.0.24 computation error bug
I'm reallly trying to figure out how to free up a machine for
quantal. I may be able to, but I'll only be able to test i386.
There's also virtualbox, but I don't think that's sufficient for
testing...
--
You
Steffen: I'll point the MOTUs to here, eventually, but because of UDS,
I'm going to give them a break until next week :P
Dave: I use VBox images to test backports and even builds, its a valid
method to test package builds, and its acceptable for testing of
backports and updates (especially
Since we should have a few days while things get sorted out here, I
guess I'll throw a Quantal virtual machine on my server in the meantime.
:-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
On 05/10/2012 04:49 PM, Ben Giacalone wrote:
Just tried to run your 7.27 on Dell 630 laptop which had no problem
before 12.04 upgrade and I get computation error on all work units for
Seti@home.
Hi Ben,
somewhere in this thread there is hidden a pointer to
I just installed 7.0.27+dfsg-0~827~precise1 onto a Dell 630 laptop which
had been running fine until 12.04 LTS upgrade. I am still getting
computation error on (9) work units that just downloaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ben I'm wondering if it's possible you ended up with double files or
just a borked install..
you should apt-get remove boinc, apt-get autoremove, and then
install boinc again. You are the first to have this error with that
package you are using.
--
You received this bug notification because you
Hello,
On 05/10/2012 05:16 PM, Ben Giacalone wrote:
I just installed 7.0.27+dfsg-0~827~precise1 onto a Dell 630 laptop which
had been running fine until 12.04 LTS upgrade. I am still getting
computation error on (9) work units that just downloaded.
This is unexpected. I presume this is the
Hi Steffen, I repeat, your latest boinc doesn't build from source.
https://launchpadlibrarian.net/104761349/buildlog.txt.gz
I'll try to branch it and build without this patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Locutus, I see your changing packages around in that PPA, is there going
to be that proven to work 7.0.27 in a ppa, because people are already
coming back on my end about the bug being back, with the version
currently in ppa:costamagnagianfranco/boinc
--
You received this bug notification
(Unfortunately I have to go to make some money, so) I won't be able to
test anything out right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
7.0.24 computation error bug
To
I'd recommend you pull something out of my book in terms of your PPA(s):
create a staging PPA for you to test your builds in, and then when you
have a working one, you upload to the deployment PPA (the PPA the public
should use).
I find it useful for when you are constantly messing with packages
I know this, but what I'm doing is only to package 7.0.27 from Steffen's
git, since it has disabled the patch causing this bug, so this update
shouldn't trigger this bug anymore, it should be working and Steffen has
confirmed this too.
So I'm just updating the package in my ppa because this
And BTW the 7.0.27 hasn't been published right now, so any people
experiencing this bug has a different bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
7.0.24 computation error bug
-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Dave
Sent: Thursday, May 10, 2012 10:25 AM
To: benjg...@yahoo.com
Subject: [Bug 991179] Re: 7.0.24 computation error bug
Ben I'm wondering if it's possible you ended up with double files or
just a borked install..
you
@ Locutus.
I can gladly confirm 7.0.27+dfsg-0~829~precise1 does not have our bug.
I am running some units right now (i386)
:-)
I'll let you know about am64, but we already know our bug is not
architecture dependent.
--
You received this bug notification because you are a member of Ubuntu
On 05/08/2012 07:12 PM, Dave wrote:
Seti@home is down for its Tuesdsay maintenance. Should be up in a few
hours.
If your next build goes through Locutus I'll test it as soon as the
project comes online.
Good luck.
Docking@Home was also affected.
Cheers,
Steffen
--
You received this bug
On 05/09/2012 03:12 AM, Dave wrote:
Indeed. The am64 also has the bug. So that patch is definitely still an
issue with 7.0.27, at least with Ubuntu.
This is not expected. Have many thanks for identifying that.
Steffen
--
You received this bug notification because you are a member of Ubuntu
On 05/08/2012 11:56 PM, Dave wrote:
So I don't wanna push anyone here, but can't we just put a 7.0.24
without the bad patch into the Ubuntu repository while we play with
the 7.0.27?
7.0.24 is bad for many reasons, especially for an incompatibility with
decent NVidia cards, no, please jump to
Happy to help, Steffen.
@Locutus, I see you put a new build in.
the i386 works great. (I'll report on the am64 within a few hours, I see it's
building now)
hoping if the am64 works as well, perhaps we'll see these packages in
the precise repository?
--
You received this bug notification
** Branch linked: lp:~costamagnagianfranco/+junk/boinc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
7.0.24 computation error bug
To manage notifications about this bug go to:
The Precise repos can't be updated without an SRU. SRU(s) are not
always approved.
Any new versions uploaded for the repositories will end up in Quantal,
unless an SRU is filed to get an update pushed to the precise-updates
repository (which you will need enabled to get those updated softwares)
As I said in my previous comment (#80 on this bug), the Precise
repositories will not be updated with any updated packages without an
SRU (Stable Release Update) being filed. That is outlined here:
https://wiki.ubuntu.com/StableReleaseUpdates. Any updates pushed to the
package at this point will
Well. I'd hope an Sru would be approved considering you currently have a
boinc package that doesn't work for one of the most used projects and at
least one other.
On May 9, 2012 1:45 PM, Thomas Ward tew...@trekweb.org wrote:
The Precise repos can't be updated without an SRU. SRU(s) are not
Hi Thomas, what I'm asking is to simply remove the patch and release for
precise, this boinc doesn't build in quantal, probably due to another
debian patch, I'm looking into it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
LocutusOfBorg: I will research as well, but an SRU would need to be
filed for any updates to Precise, and the Packaging-Specific notes for
this bug (see comment 81) apply: the package name would change.
Considering this is in Universe, I can poke the MOTUs to help out in
getting the SRU through,
Its too bad this bug didn't show in 12.04 before its final release,
otherwise I would have reported it before 12.04 got locked. But for
whatever reason it worked fine until 12.04 was final and I reinstalled
boinc, it was only then that the bug showed
On May 9, 2012 2:55 PM, Thomas Ward
@Locutus, the am64 works also. Just in case your curious.
that 7.0.27 is running on a i386 machine of mine, and on a am64, running
well on both with S@H.
Thanks Locutus for the work you put in trying all these builds out. I'm
going to keep that working 7.0.27 on both of my boxes until I hear
Thanks for your help Dave, I think your help is not needed anymore, now
we have to wait for some MOTU decision, to drop this version or other.
BTW for everyone affected by this bug I'm publishing this package in my boinc
development ppa too
LocutusOfBorg:
Dave:
Does 7.0.27 work and build on Precise and Quantal? If that fixes this
bug, then a sync request can (probably) be done for Quantal to get
7.0.27 from Debian Sid, and then either a backport or an SRU can be done
to get that into Precise (if and only if it builds and runs
I can't/won't test for Quantal
But I do know Locutus has been unable to get 7.0.27 to build for it here
at launchpad... He/I think it's probably due to another Debian patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
oh and again @thomas, this 7.0.27 that Locutus compiled without the
problem patch, works fine in Precise for both i386 and am64. (I do not
use a GPU for crunching, so I can't speak for that half of it.)
and @Locutus, thanks for putting the working 7.0.27 into it's own
repository. Some people will
Importance: Medium, as per the following criteria by BugSquad member
trekcaptainusa-tw:
given that the program is non-core, and given the bug affects 11
people, and given that it impacts the functionality of the non-core
program in a significant manner, I believe it should be Medium. (from
Dave: It's irrelevant if it builds in Precise or not, the SRU team (I
checked with them) won't apply a Stable Release Update to Precise unless
there's no other alternative, given that their methodology usually
states that whatever update is occurring *should* build (and ideally
exist) in latest
Well, that's Locutus' department. :-)
I hope it gets figured out why it wont build for quantal. I'll bet the
source would, but when all those patches get thrown in... well you get
the idea.
When it does get figured out and will build for quantal, I hope the
update is applied. 12.04 is a LTS and
And one more thing to consider, Locutus has mentioned. The version in
the Ubuntu repository need not change from 7.0.24 (though it would be
preferred just due to the fixes in the source), 7.0.24 could be kept,
and made to work, just by compiling without the ONE pad patch that's
breaking it... Just
Dave: did Locutus test that on Quantal as well, with the building and
running? that fix would need applied in quantal before its SRU'd (the
same thing I said in comment #92 about the SRU stuff still applies, even
to this kind of fix you've mentioned)
--
You received this bug notification
He'll have to comment in the AM, but yes I believe they all built in
quantal without the bad patch, except the 7.0.27
So perhaps he can try to build the 7.0.26 (without the bad patch), and
push that for quantal, so that it can end up in Precise?
--
You received this bug notification because you
7.0.26 isn't in Debian, so I'd have to poke around with the MOTUs to get
that into Quantal, if not take the source and repackage it for quantal-
proposed.
Once Locutus can confirm whether or not 7.0.27 builds in Quantal, I'll
go poke the MOTUs. I should point out, though, that since 7.0.26 is
Just checked for updates and was surprised to find 7.0.27
Many thanks to you all for this wonderful fix -- Hugs to all
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991179
Title:
7.0.24
Well, my bug #985622 was reported against 12.04 beta 2.
On 05/09/2012 02:12 PM, Dave wrote:
Its too bad this bug didn't show in 12.04 before its final release,
otherwise I would have reported it before 12.04 got locked. But for
whatever reason it worked fine until 12.04 was final and I
Unfortunately sometimes I have to sleep :)
I'm building right now 7.0.27 with the patch parse_issues.patch disabled,
since it doesn't build with it included (and as far as I can tell the patch has
no problem), I have already filled a bug against bzr.
With a little luck the package will build
On 05/07/2012 05:24 PM, Dave wrote:
MoreInformativeAppStartFailure.patch is the culprit of the computation
error issue. :-)
I'm relieved that that one worked. .
Please update to 7.0.27. I have the client working and that patch is in.
Steffen
--
You received this bug notification
According to this [1] which is based on your git [2] the patch isn't included,
I see a
#convinceDavid# MoreInformativeAppStartFailure.patch
which is clearly commented.
I thought this patch was included upstream but I cannot find any
reference in the source code files.
Is this the right git?
On 05/08/2012 10:30 AM, LocutusOfBorg wrote:
Unfortunately sometimes I have to sleep :)
I'm building right now 7.0.27 with the patch parse_issues.patch disabled,
since it doesn't build with it included (and as far as I can tell the patch
has no problem), I have already filled a bug against
On 05/08/2012 11:02 AM, LocutusOfBorg wrote:
According to this [1] which is based on your git [2] the patch isn't
included, I see a
#convinceDavid# MoreInformativeAppStartFailure.patch
which is clearly commented.
Right. I had not pushed. Sorry for that.
I thought this patch was included
Seti@home is down for its Tuesdsay maintenance. Should be up in a few
hours.
If your next build goes through Locutus I'll test it as soon as the
project comes online.
Good luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Steffen and Dave.
7.0.27 will be available in a few minutes for i386 and a 3-4 hours for
amd64.
I build it without parse_issues.patch since this patch has something
wrong that make build fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
OT Steffen your .27 boinc doesn't build on quantal quetzal release, while .24
does, but now I have no time to look at which patch could be wrong, we are in
the initial developing stadium, so there's time to make it work :)
/OT
--
You received this bug notification because you are a member of
1 - 100 of 173 matches
Mail list logo
