On Thursday 07 January 2021 18:24:39 Jonas Smedegaard wrote:
> Quoting Luke Dashjr (2021-01-07 18:26:43)
>
> > We (upstream) already elaborated many years ago, copied here:
> >
> > http://luke.dashjr.org/tmp/code/20130723-linux-distribution-packaging-and
> >-bitco
We (upstream) already elaborated many years ago, copied here:
http://luke.dashjr.org/tmp/code/20130723-linux-distribution-packaging-and-bitcoin.md.asc
At a minimum, to be safe, Debian would need to:
1) Either:
1a) Build with the bundled LevelDB statically linked.
1b) Guarantee LevelDB package
The severity is wrong on this. The first one is a very minor issue (only the
admin can trigger it), and the second one is not a bug at all.
On Wednesday 06 June 2018 21:01:42 Moritz Muehlenhoff wrote:
> Package: bfgminer
> Severity: grave
> Tags: security
>
>
On Friday 03 November 2017 1:27:24 PM Jonas Smedegaard wrote:
> Quoting Luke Dashjr (2017-11-03 11:25:23)
>
> > On Friday 03 November 2017 9:10:37 AM you wrote:
> >> I believe Bitcoin is now stable enough for stable release.
> >
> > Things have only gotte
On Friday 03 November 2017 9:10:37 AM you wrote:
> I believe Bitcoin is now stable enough for stable release.
Things have only gotten less stable upstream since 2013...
What is the plan for getting security and protocol change updates backported
to Debian stable?
Luke
BFGMiner should work just fine with the git version of libblkmaker, and
doesn't require libblkmaker to work correctly in many common cases.
The simplest solution would be to simply bump libblkmaker.
Package: installation-reports
Severity: minor
Dear Maintainer,
* What led up to the situation?
Chose the CPU burnin option of the installer, and chose 10 minutes runtime.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Let it run the full 10 minutes.
*
I, too, would like to see CURVE support in Debian's libzmq3. Honestly, I don't
see how it's useful without it - everything is cleartext!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Thursday, July 03, 2014 1:43:08 PM Folkert van Heusden wrote:
I try to mine at btcguild. I use the command-line they suggest (apart from
the --api* of course):
/usr/bin/bfgminer --syslog -o stratum+tcp://eu-stratum.btcguild.com:
-u flok_1 -p 123 -S erupter:all --api-listen
On Wednesday, June 25, 2014 6:53:57 PM Scott Howard wrote:
On Wed, Jun 25, 2014 at 2:50 PM, Scott Howard showard...@gmail.com wrote:
Thank you, Chris. I think you articulated the situation well and the
options.
one more thing: debian is discussion dropping libdb (the db the node,
but not
On Monday, June 16, 2014 1:14:44 PM Dmitry Smirnov wrote:
Bad news: I had a look at tarball which includes ccan-upstream/* files and
I must say that I dramatically underestimated the mess which is there.
There are so many files and licenses but also tarballs with
who-knows-what. IMHO packaging
On Sunday, June 15, 2014 8:50:55 PM Dmitry Smirnov wrote:
On Sun, 15 Jun 2014 19:43:27 Luke Dashjr wrote:
That's under the ccan-upstream/ path I mentioned. I'm not sure why it's
failing there, though, since the file is included in all the txz files.
:/
-rw-rw-r-- luke-jr/luke-jr 11804
On Sunday, June 15, 2014 9:05:13 PM Vagrant Cascadian wrote:
On Sun, Jun 15, 2014 at 06:52:47PM +1000, Dmitry Smirnov wrote:
On Sun, 15 Jun 2014 00:55:04 Vagrant Cascadian wrote:
I didn't need to do any changes to the packaging, other than adding an
updated debian/changelog with the new
Sounds like a straightforward fix to cast the memmove to (void) as well.
As I cannot reproduce this warning/error myself, can you confirm this fix is
correct?
From abccbc643c893726a0dd3aa6d7c7f8a9fd4c38bf Mon Sep 17 00:00:00 2001
From: Luke Dashjr luke-jr+...@utopios.org
Date: Sun, 18 May 2014 21
14 matches
Mail list logo
