Bug#718272: Processed: reopening 718272

2021-01-27 Thread Jonas Smedegaard
close 718272
thanks

Quoting Moritz Mühlenhoff (2021-01-27 20:03:40)
> reopen 718272
> thx
> 
> Reopening. The reasons are listed in the bug log and were given by
> the upstream developers. If you want to provide it to bullseye
> stable users, get it into fasttrack.debian.net.

Thanks for sharing your interpretation of the state of this bug, and for 
suggesting how to maintain this package.

I disagree with both the interpretation and the suggestion, however.
Closing, reflecting my views on this bug as package maintainer.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature


Bug#718272: Processed: reopening 718272

2021-01-27 Thread Moritz Mühlenhoff
reopen 718272
thx

Reopening. The reasons are listed in the bug log and were given by
the upstream developers. If you want to provide it to bullseye
stable users, get it into fasttrack.debian.net.

Cheers,
Moritz



Bug#718272: Processed: reopening 718272

2021-01-07 Thread Luke Dashjr
FWIW, I brought this up at our weekly developer meeting, and there was also 
another concern about apt upgrades across softforks: It could be problematic 
to not deploy a softfork, and problematic to deploy one without the user's 
consent.

I think I recall Debian has a way for packages to interactively prompt the 
user during upgrade. Maybe if softforks were turned into a runtime option, 
that could resolve that issue. What do you think?

For reference, the meeting log:

https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2021/bitcoin-core-dev.2021-01-07-19.00.moin.txt

Luke


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
> >-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 remains consensus-compatible, including NOT
> > fixing any bugs without a proper consensus-compatibility audit.
> > 2) Backport (at least) security fixes for Debian's security support
> > period. Upstream, we generally only maintain releases for a year or so at
> > most.
>
> Thanks for your input on upstream position on this matter, Luke, and in
> particular this condensed summary.  It is helpful for Debian to make its
> decision.
>
>
>  - Jonas



Bug#718272: Processed: reopening 718272

2021-01-07 Thread Jonas Smedegaard
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-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 remains consensus-compatible, including NOT
> fixing any bugs without a proper consensus-compatibility audit.
> 2) Backport (at least) security fixes for Debian's security support period.
>Upstream, we generally only maintain releases for a year or so at most.

Thanks for your input on upstream position on this matter, Luke, and in 
particular this condensed summary.  It is helpful for Debian to make its 
decision.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature


Bug#718272: Processed: reopening 718272

2021-01-07 Thread Luke Dashjr
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 remains consensus-compatible, including NOT
fixing any bugs without a proper consensus-compatibility audit.
2) Backport (at least) security fixes for Debian's security support period.
   Upstream, we generally only maintain releases for a year or so at most.

Luke


On Thursday 07 January 2021 13:51:50 Jonas Smedegaard wrote:
> Quoting Debian Bug Tracking System (2020-12-27 19:33:02)
>
> > Processing commands for cont...@bugs.debian.org:
> > > reopen 718272
> >
> > Bug #718272 {Done: Jonas Smedegaard } [src:bitcoin]
> > upstream does not support stable releases (block migration to testing)
> > Bug reopened
> > Ignoring request to alter fixed versions of bug #718272 to the same
> > values previously set
> >
> > > thanks
> >
> > Stopping processing here.
> >
> > Please contact me if you need assistance.
>
> I consider Bitcoin suitable for release with stable Debian.
>
> If seciurity team or others disagree with that, then please elaborate on
> your concerns.
>
>
>  - Jonas