Codigo fuente "Source code (tar.gz)" en Release tag v2.0.0.2 es distinto al del repositorio #6

New issue

Open

opened 2022-08-30 23:25:15 +00:00 by Visionario · 0 comments

Visionario commented

2022-08-30 23:25:15 +00:00

(Migrated from github.com)

Hacer git clone https://github.com/BOLI-Project/BolivarCoin.git y wget https://github.com/BOLI-Project/BolivarCoin/archive/refs/tags/v2.0.0.2.tar.gz no obtiene el mismo código fuente.

Al descargar ambos y ejecutar un diff -r -q BolivarCoin BolivarCoin-2.0.0.2/ se obtiene:

Only in BolivarCoin: .git
Files BolivarCoin/.gitattributes and BolivarCoin-2.0.0.2/.gitattributes differ
Only in BolivarCoin-2.0.0.2/: .travis.yml
Files BolivarCoin/Compile.sh and BolivarCoin-2.0.0.2/Compile.sh differ
Files BolivarCoin/Crear_Masternodo.md and BolivarCoin-2.0.0.2/Crear_Masternodo.md differ
Files BolivarCoin/contrib/macdeploy/background.png and BolivarCoin-2.0.0.2/contrib/macdeploy/background.png differ
Files BolivarCoin/contrib/macdeploy/background.psd and BolivarCoin-2.0.0.2/contrib/macdeploy/background.psd differ
Files BolivarCoin/contrib/macdeploy/background.tiff and BolivarCoin-2.0.0.2/contrib/macdeploy/background.tiff differ
Files BolivarCoin/contrib/macdeploy/background@2x.png and BolivarCoin-2.0.0.2/contrib/macdeploy/background@2x.png differ
Files BolivarCoin/src/chainparams.cpp and BolivarCoin-2.0.0.2/src/chainparams.cpp differ
Files BolivarCoin/src/qt/forms/modaloverlay.ui and BolivarCoin-2.0.0.2/src/qt/forms/modaloverlay.ui differ
Files BolivarCoin/src/qt/guiconstants.h and BolivarCoin-2.0.0.2/src/qt/guiconstants.h differ
Files BolivarCoin/src/qt/res/css/light.css and BolivarCoin-2.0.0.2/src/qt/res/css/light.css differ
Files BolivarCoin/src/version.h and BolivarCoin-2.0.0.2/src/version.h differ

La mayoría de las diferencias son tolerables, con la excepción de BolivarCoin/src/version.h y BolivarCoin/src/chainparams.cpp los cuales arrojan cambios de versión....

diff -r BolivarCoin/src/chainparams.cpp BolivarCoin-2.0.0.2/src/chainparams.cpp
170,173c170
<             ( 564719, uint256S("0x000000000001518bf8d58cba04c27963d41f4924f187d07db00285249eef1ab6"))
<             ( 570000, uint256S("0x0000000000059e377c644185684a8c34c5860afff9c416f5414877c7f2f2411a"))
<             ( 575000, uint256S("0x000000000001f7b984526ead4221093e3bac4dacb5ef7c6132cae67fc8083956"))
<             ( 580158, uint256S("0x000000000003dc7702445011c779f84e097b0dd3526742ab9968c07f13f45f94")),
---
>             ( 564719, uint256S("0x000000000001518bf8d58cba04c27963d41f4924f187d07db00285249eef1ab6")),

diff -r BolivarCoin/src/version.h BolivarCoin-2.0.0.2/src/version.h
13c13
< static const int PROTOCOL_VERSION = 70212;
---
> static const int PROTOCOL_VERSION = 70211;
22c22
< static const int MIN_PEER_PROTO_VERSION = 70211;
---
> static const int MIN_PEER_PROTO_VERSION = 70013;

Este último produce una incompatibilidad en la red de masternodos recibiendo un mensaje en el debug de Not capable masternode: Invalid protocol version y Invalid Masternode Status, cannot continue..

La recomendación para compilación es utilizar el método del Git Clone ya que contiene las versiones correctas del código compatible a la fecha.

SOLUCIÓN:
Se harán los ajustes para el siguiente release.

Hacer git clone `https://github.com/BOLI-Project/BolivarCoin.git` y `wget https://github.com/BOLI-Project/BolivarCoin/archive/refs/tags/v2.0.0.2.tar.gz` no obtiene el mismo código fuente. Al descargar ambos y ejecutar un `diff -r -q BolivarCoin BolivarCoin-2.0.0.2/` se obtiene: ``` Only in BolivarCoin: .git Files BolivarCoin/.gitattributes and BolivarCoin-2.0.0.2/.gitattributes differ Only in BolivarCoin-2.0.0.2/: .travis.yml Files BolivarCoin/Compile.sh and BolivarCoin-2.0.0.2/Compile.sh differ Files BolivarCoin/Crear_Masternodo.md and BolivarCoin-2.0.0.2/Crear_Masternodo.md differ Files BolivarCoin/contrib/macdeploy/background.png and BolivarCoin-2.0.0.2/contrib/macdeploy/background.png differ Files BolivarCoin/contrib/macdeploy/background.psd and BolivarCoin-2.0.0.2/contrib/macdeploy/background.psd differ Files BolivarCoin/contrib/macdeploy/background.tiff and BolivarCoin-2.0.0.2/contrib/macdeploy/background.tiff differ Files BolivarCoin/contrib/macdeploy/background@2x.png and BolivarCoin-2.0.0.2/contrib/macdeploy/background@2x.png differ Files BolivarCoin/src/chainparams.cpp and BolivarCoin-2.0.0.2/src/chainparams.cpp differ Files BolivarCoin/src/qt/forms/modaloverlay.ui and BolivarCoin-2.0.0.2/src/qt/forms/modaloverlay.ui differ Files BolivarCoin/src/qt/guiconstants.h and BolivarCoin-2.0.0.2/src/qt/guiconstants.h differ Files BolivarCoin/src/qt/res/css/light.css and BolivarCoin-2.0.0.2/src/qt/res/css/light.css differ Files BolivarCoin/src/version.h and BolivarCoin-2.0.0.2/src/version.h differ ``` La mayoría de las diferencias son tolerables, con la excepción de `BolivarCoin/src/version.h` y `BolivarCoin/src/chainparams.cpp` los cuales arrojan cambios de versión.... ``` diff -r BolivarCoin/src/chainparams.cpp BolivarCoin-2.0.0.2/src/chainparams.cpp 170,173c170 < ( 564719, uint256S("0x000000000001518bf8d58cba04c27963d41f4924f187d07db00285249eef1ab6")) < ( 570000, uint256S("0x0000000000059e377c644185684a8c34c5860afff9c416f5414877c7f2f2411a")) < ( 575000, uint256S("0x000000000001f7b984526ead4221093e3bac4dacb5ef7c6132cae67fc8083956")) < ( 580158, uint256S("0x000000000003dc7702445011c779f84e097b0dd3526742ab9968c07f13f45f94")), --- > ( 564719, uint256S("0x000000000001518bf8d58cba04c27963d41f4924f187d07db00285249eef1ab6")), ``` y ``` diff -r BolivarCoin/src/version.h BolivarCoin-2.0.0.2/src/version.h 13c13 < static const int PROTOCOL_VERSION = 70212; --- > static const int PROTOCOL_VERSION = 70211; 22c22 < static const int MIN_PEER_PROTO_VERSION = 70211; --- > static const int MIN_PEER_PROTO_VERSION = 70013; ``` Este último produce una incompatibilidad en la red de masternodos recibiendo un mensaje en el debug de _Not capable masternode: Invalid protocol version_ y _Invalid Masternode Status, cannot continue._. La recomendación para compilación es utilizar el método del Git Clone ya que contiene las versiones correctas del código compatible a la fecha. SOLUCIÓN: Se harán los ajustes para el siguiente release.