<div dir="ltr"><div>I would be for this, The following packages tend to get fixes in versions not as patches to old version.</div><div><br></div><div>bitcoind/bitcoin-qt (at least this is how it looks on the forum)</div><div>BFGminer</div><div>CGminer.</div><div><br></div><div>As, I will be making minepeon into a native package it's patches can be rolled at proper Debian subversions. I think the original developer may have let it stand for a short time. I do not know what his plan is so I may have to take on more development of it to get it where I want.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 11, 2014 at 8:34 AM, Scott Howard <span dir="ltr"><<a href="mailto:showard314@gmail.com" target="_blank">showard314@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello bitcoin team, please see the discussion on debian-devel that is<br>
very related to many of the discussion on this list. The start of the<br>
thread is included below, and is archived here:<br>
<a href="https://lists.debian.org/debian-devel/2014/11/msg00406.html" target="_blank">https://lists.debian.org/debian-devel/2014/11/msg00406.html</a><br>
<br>
In short, backports may be enabled by default in Jessie. That means<br>
that we can, in theory, deliberately block packages from being in<br>
Jessie, maintain them in jessie-backports so they are always<br>
up-to-date. This is especially important for mining software (to<br>
support new hardware) and bitcoin clients that need the most<br>
up-to-date versions (armory and bitcoind/bitcoin-qt).<br>
<br>
Please follow that discussion if you are interested. I think the<br>
bitcoin package is in a good position either way, armory should follow<br>
closely to see what the consensus is, and the mining software<br>
(bfgminer/cgminer) should also watch closely. I think minepeon is in<br>
the process of being packaged, that too will be affected by this.<br>
<br>
If we decide to maintain bitcoin packages is such a way, we probably<br>
will need to document this carefully and make sure the team is ready<br>
for continued maintenance of all packages, possibly recruit some more<br>
people to help out as well as look for other packages that would be<br>
good to maintain under the same umbrella. It would also be possible to<br>
create a "cryptocurrency OS" that is a debian pure blend [1], if<br>
someone was so inclined, that would perpetually be up-to-date and<br>
cover the whole cryptocurrency ecosystem.<br>
<br>
Regards,<br>
Scott<br>
<br>
[1] <a href="https://wiki.debian.org/DebianPureBlends" target="_blank">https://wiki.debian.org/DebianPureBlends</a><br>
<br>
On Tue, Nov 11, 2014 at 8:30 AM, Rebecca N. Palmer<br>
<<a href="mailto:rebecca_palmer@zoho.com">rebecca_palmer@zoho.com</a>> wrote:<br>
> It has been recently stated [0-1] that backports is enabled by default in<br>
> Jessie.<br>
><br>
> 1. Does that mean that if pkgX is in jessie-backports but not jessie,<br>
> "apt-get install pkgX" will install it from -backports?<br>
><br>
> 2. If so, when (if ever) is it appropriate to deliberately invoke that<br>
> behaviour by removing pkgX from jessie?<br>
> Possible candidates:<br>
> a. Packages that work closely with hardware, where old versions don't work<br>
> with new hardware (example: beignet)<br>
> b. Packages that implement fast-evolving file formats or network protocols,<br>
> where you need the same version as the people you are communicating with<br>
> (possible example: jscommunicator [2])<br>
> c. Packages that are generally rapidly improving, and are typically used<br>
> where this improvement is more important than stability<br>
><br>
> The advantage of doing so (over having both the old version in jessie and<br>
> the new one in jessie-backports) is that non-technical users (who may not<br>
> know that backports exists) get the new version they probably want; the<br>
> disadvantage is that users who explicitly want stability can no longer<br>
> choose it (except by pinning or using <a href="http://snapshot.debian.org" target="_blank">snapshot.debian.org</a>, which also block<br>
> security updates of that package).<br>
><br>
> In the long run it may be a better idea to have these packages suggest<br>
> upgrading to -backports in their "this hardware/protocol version/option not<br>
> supported" error message, or on startup if there is no easy way to identify<br>
> attempts to use the newer features, but it is too late to do this for<br>
> jessie.<br>
><br>
> (Release team have already ruled that a. (#767961) and b. (#768933) are not<br>
> valid reasons for freeze exceptions; I guess this would also forbid stable<br>
> updates)<br>
><br>
> [0] <a href="https://lists.debian.org/debian-devel/2014/11/msg00339.html" target="_blank">https://lists.debian.org/debian-devel/2014/11/msg00339.html</a><br>
> [1] My own sources.list has<br>
> # jessie-backports, previously on <a href="http://backports.debian.org" target="_blank">backports.debian.org</a><br>
> # Line commented out by installer because it failed to verify:<br>
> #deb <a href="http://ftp.uk.debian.org/debian/" target="_blank">http://ftp.uk.debian.org/debian/</a> jessie-backports main<br>
> but <a href="https://lists.debian.org/debian-user/2014/09/msg01174.html" target="_blank">https://lists.debian.org/debian-user/2014/09/msg01174.html</a> reports<br>
> getting one with that line uncommented<br>
> [2] <a href="https://lists.debian.org/debian-release/2014/11/msg00866.html" target="_blank">https://lists.debian.org/debian-release/2014/11/msg00866.html</a><br>
><br>
><br>
> --<br>
> To UNSUBSCRIBE, email to <a href="mailto:debian-devel-REQUEST@lists.debian.org">debian-devel-REQUEST@lists.debian.org</a><br>
> with a subject of "unsubscribe". Trouble? Contact<br>
> <a href="mailto:listmaster@lists.debian.org">listmaster@lists.debian.org</a><br>
> Archive: <a href="https://lists.debian.org/54620F78.4040501@zoho.com" target="_blank">https://lists.debian.org/54620F78.4040501@zoho.com</a><br>
><br>
<br>
_______________________________________________<br>
Pkg-bitcoin-devel mailing list<br>
<a href="mailto:Pkg-bitcoin-devel@lists.alioth.debian.org">Pkg-bitcoin-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-bitcoin-devel" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-bitcoin-devel</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div> </div><div>Shawn L. Djernes<br>SD Consulting LLC<br><a href="mailto:sdjernes@gmail.com" target="_blank">sdjernes@gmail.com</a><br>402.345.7734 | 402.350.6973 Cell</div><div>Fax: 888.297.6310</div><div> </div><div>Apple Certified Consultant</div><div>Special Deals:</div><div><a href="http://www.anrdoezrs.net/click-6259053-11031064" target="_blank">iPad with Retina Display. From $499.</a></div></div></div>
</div>