Bitcoin Forum

Alternate cryptocurrencies => Altcoin Discussion => Topic started by: flyx on January 11, 2020, 12:06:57 PM



Title: some errors for cloning
Post by: flyx on January 11, 2020, 12:06:57 PM
Hello Masters
I tried to clone coin and using debian for windows necessaries , but when it try to use below command i see some errors :
Code:
user1@debian:~/gitian-builder$ bin/make-base-vm --lxc --arch i386 --suite precise
I: Target architecture can be executed
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
E: Release signed by unknown key (key id 40976EAF437D05B5)
   The specified keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg may be incorrect or out of date.
   You can find the latest Debian release key at https://ftp-master.debian.org/keys.html

Please guide me how to fix this error


Title: Re: some errors for cloning
Post by: DaveF on January 11, 2020, 01:28:40 PM
Try:

Code:
sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 40976EAF437D05B5 

-Dave


Title: Re: some errors for cloning
Post by: flyx on January 11, 2020, 02:07:33 PM
I tied to command that line but problem exists still :

Code:
user1@debian:~$ sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 40976EAF437D05B5
Executing: /tmp/apt-key-gpghome.SWBRpi8hzc/gpg.1.sh --recv-keys --keyserver keyserver.ubuntu.com 40976EAF437D05B5
gpg: key 40976EAF437D05B5: 60 signatures not checked due to missing keys
gpg: key 40976EAF437D05B5: "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
user1@debian:~$ cd gitian-builder
user1@debian:~/gitian-builder$ bin/make-base-vm --lxc --arch i386 --suite precise
I: Target architecture can be executed
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
E: Release signed by unknown key (key id 40976EAF437D05B5)
   The specified keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg may be incorrect or out of date.
   You can find the latest Debian release key at https://ftp-master.debian.org/keys.html


Title: Re: some errors for cloning
Post by: DaCryptoRaccoon on January 11, 2020, 04:04:09 PM
The error is :

E: Release signed by unknown key (key id 40976EAF437D05B5)
   The specified keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg may be incorrect or out of date.

Go here

Code:
/usr/share/keyrings/ubuntu-archive-keyring.gpg 
and check the key is not a revoked key if it is remove it and update to one of the latest signing key found at the link below.

Code:
https://ftp-master.debian.org/keys.html


Title: Re: some errors for cloning
Post by: flyx on January 12, 2020, 08:52:09 AM
The error is :

E: Release signed by unknown key (key id 40976EAF437D05B5)
   The specified keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg may be incorrect or out of date.

Go here

Code:
/usr/share/keyrings/ubuntu-archive-keyring.gpg 
and check the key is not a revoked key if it is remove it and update to one of the latest signing key found at the link below.

Code:
https://ftp-master.debian.org/keys.html


I tried
Code:
wget http://archive.ubuntu.com/ubuntu/project/ubuntu-archive-keyring.gpg -O- | sudo apt-key add -

to update keys , but i still got same error
can you please tell me what commands i have to use

Thanks


Title: Re: some errors for cloning
Post by: DaveF on January 12, 2020, 01:50:22 PM
Try:

Code:
gpg --keyserver subkeys.pgp.net --recv 40976EAF437D05B5

If that does not work try (you might have to sudo):

Code:
apt-get install debian-keyring

and then try the gpg command again.

If not then I have no idea, it worked to install the key on my test VM so if it's not working for yours it is probably a system issue and not a build issue.

-Dave




Title: Re: some errors for cloning
Post by: flyx on January 12, 2020, 02:16:46 PM
I use second command on root access and it worked and then i tried to first command line on user account and i got below errors :

Code:
user1@debian:~$ gpg --keyserver subkeys.pgp.net --recv 40976EAF437D05B5
gpg: keyserver receive failed: Connection timed out
user1@debian:~$ gpg --keyserver subkeys.pgp.net --recv
user1@debian:~$ cd gitian-builder
user1@debian:~/gitian-builder$ gpg --keyserver subkeys.pgp.net --recv 40976EAF437D05B5

gpg: keyserver receive failed: Connection timed out
user1@debian:~/gitian-builder$
user1@debian:~/gitian-builder$ bin/make-base-vm --lxc --arch i386 --suite precise
[sudo] password for user1:
I: Target architecture can be executed
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
E: Release signed by unknown key (key id 40976EAF437D05B5)
   The specified keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg may be incorrect or out of date.
   You can find the latest Debian release key at https://ftp-master.debian.org/keys.html
user1@debian:~/gitian-builder$ cd /usr/share/keyrings/u
-bash: cd: /usr/share/keyrings/u: No such file or directory
user1@debian:~/gitian-builder$ cd /usr/share/keyrings/
user1@debian:/usr/share/keyrings$ gpg --keyserver subkeys.pgp.net --recv 40976EAF437D05B5
gpg: keyserver receive failed: Connection timed out
user1@debian:/usr/share/keyrings$



Title: Re: some errors for cloning
Post by: flyx on January 12, 2020, 03:00:12 PM
I tried to import kets from https://ftp-master.debian.org/keys.html and used below way :

began from root
Code:
root@debian:/usr/share# cd keyrings
root@debian:/usr/share/keyrings# ls
debian-archive-buster-automatic.gpg
debian-archive-buster-security-automatic.gpg
debian-archive-buster-stable.gpg
debian-archive-jessie-automatic.gpg
debian-archive-jessie-security-automatic.gpg
debian-archive-jessie-stable.gpg
debian-archive-keyring.gpg
debian-archive-removed-keys.gpg
debian-archive-stretch-automatic.gpg
debian-archive-stretch-security-automatic.gpg
debian-archive-stretch-stable.gpg
debian-keyring.gpg
debian-maintainers.gpg
debian-nonupload.gpg
debian-role-keys.gpg
ubuntu-archive-keyring.gpg
ubuntu-archive-removed-keys.gpg
ubuntu-cloud-keyring.gpg
ubuntu-cloud-removed-keys.gpg
ubuntu-cloudimage-keyring.gpg
ubuntu-cloudimage-removed-keys.gpg
ubuntu-dbgsym-keyring.gpg
ubuntu-dbgsym-removed-keys.gpg
ubuntu-keyring-2012-archive.gpg
ubuntu-keyring-2012-cdimage.gpg
ubuntu-keyring-2012-cloud-archive.gpg
ubuntu-keyring-2016-dbgsym.gpg
ubuntu-keyring-2018-archive.gpg
ubuntu-master-keyring.gpg
root@debian:/usr/share/keyrings# mv debian-archive-keyring.gpg test.gpg
root@debian:/usr/share/keyrings# ls
debian-archive-buster-automatic.gpg
debian-archive-buster-security-automatic.gpg
debian-archive-buster-stable.gpg
debian-archive-jessie-automatic.gpg
debian-archive-jessie-security-automatic.gpg
debian-archive-jessie-stable.gpg
debian-archive-removed-keys.gpg
debian-archive-stretch-automatic.gpg
debian-archive-stretch-security-automatic.gpg
debian-archive-stretch-stable.gpg
debian-keyring.gpg
debian-maintainers.gpg
debian-nonupload.gpg
debian-role-keys.gpg
test.gpg
ubuntu-archive-keyring.gpg
ubuntu-archive-removed-keys.gpg
ubuntu-cloud-keyring.gpg
ubuntu-cloud-removed-keys.gpg
ubuntu-cloudimage-keyring.gpg
ubuntu-cloudimage-removed-keys.gpg
ubuntu-dbgsym-keyring.gpg
ubuntu-dbgsym-removed-keys.gpg
ubuntu-keyring-2012-archive.gpg
ubuntu-keyring-2012-cdimage.gpg
ubuntu-keyring-2012-cloud-archive.gpg
ubuntu-keyring-2016-dbgsym.gpg
ubuntu-keyring-2018-archive.gpg
ubuntu-master-keyring.gpg
root@debian:/usr/share/keyrings# wget https://ftp-master.debian.org/keys/archive-key-10.asc
--2020-01-12 09:51:54--  https://ftp-master.debian.org/keys/archive-key-10.asc
Resolving ftp-master.debian.org (ftp-master.debian.org)... 138.16.160.17
Connecting to ftp-master.debian.org (ftp-master.debian.org)|138.16.160.17|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 11093 (11K) [text/plain]
Saving to: 'archive-key-10.asc'

archive-key-10.asc  100%[===================>]  10.83K  22.6KB/s    in 0.5s

2020-01-12 09:51:59 (22.6 KB/s) - 'archive-key-10.asc' saved [11093/11093]

root@debian:/usr/share/keyrings# ls
archive-key-10.asc
debian-archive-buster-automatic.gpg
debian-archive-buster-security-automatic.gpg
debian-archive-buster-stable.gpg
debian-archive-jessie-automatic.gpg
debian-archive-jessie-security-automatic.gpg
debian-archive-jessie-stable.gpg
debian-archive-removed-keys.gpg
debian-archive-stretch-automatic.gpg
debian-archive-stretch-security-automatic.gpg
debian-archive-stretch-stable.gpg
debian-keyring.gpg
debian-maintainers.gpg
debian-nonupload.gpg
debian-role-keys.gpg
test.gpg
ubuntu-archive-keyring.gpg
ubuntu-archive-removed-keys.gpg
ubuntu-cloud-keyring.gpg
ubuntu-cloud-removed-keys.gpg
ubuntu-cloudimage-keyring.gpg
ubuntu-cloudimage-removed-keys.gpg
ubuntu-dbgsym-keyring.gpg
ubuntu-dbgsym-removed-keys.gpg
ubuntu-keyring-2012-archive.gpg
ubuntu-keyring-2012-cdimage.gpg
ubuntu-keyring-2012-cloud-archive.gpg
ubuntu-keyring-2016-dbgsym.gpg
ubuntu-keyring-2018-archive.gpg
ubuntu-master-keyring.gpg
root@debian:/usr/share/keyrings# mv archive-key-10.asc
mv: missing destination file operand after 'archive-key-10.asc'
Try 'mv --help' for more information.
root@debian:/usr/share/keyrings# gpg --dearmor archive-key-10.asc
root@debian:/usr/share/keyrings# ls
archive-key-10.asc
archive-key-10.asc.gpg
debian-archive-buster-automatic.gpg
debian-archive-buster-security-automatic.gpg
debian-archive-buster-stable.gpg
debian-archive-jessie-automatic.gpg
debian-archive-jessie-security-automatic.gpg
debian-archive-jessie-stable.gpg
debian-archive-removed-keys.gpg
debian-archive-stretch-automatic.gpg
debian-archive-stretch-security-automatic.gpg
debian-archive-stretch-stable.gpg
debian-keyring.gpg
debian-maintainers.gpg
debian-nonupload.gpg
debian-role-keys.gpg
test.gpg
ubuntu-archive-keyring.gpg
ubuntu-archive-removed-keys.gpg
ubuntu-cloud-keyring.gpg
ubuntu-cloud-removed-keys.gpg
ubuntu-cloudimage-keyring.gpg
ubuntu-cloudimage-removed-keys.gpg
ubuntu-dbgsym-keyring.gpg
ubuntu-dbgsym-removed-keys.gpg
ubuntu-keyring-2012-archive.gpg
ubuntu-keyring-2012-cdimage.gpg
ubuntu-keyring-2012-cloud-archive.gpg
ubuntu-keyring-2016-dbgsym.gpg
ubuntu-keyring-2018-archive.gpg
ubuntu-master-keyring.gpg
root@debian:/usr/share/keyrings# archive-key-10.asc.gpg
-bash: archive-key-10.asc.gpg: command not found
root@debian:/usr/share/keyrings# mv archive-key-10.asc.gpg
mv: missing destination file operand after 'archive-key-10.asc.gpg'
Try 'mv --help' for more information.
root@debian:/usr/share/keyrings# mv archive-key-10.asc.gpg ubuntu-archive-keyring.gpg
root@debian:/usr/share/keyrings# ls
archive-key-10.asc
debian-archive-buster-automatic.gpg
debian-archive-buster-security-automatic.gpg
debian-archive-buster-stable.gpg
debian-archive-jessie-automatic.gpg
debian-archive-jessie-security-automatic.gpg
debian-archive-jessie-stable.gpg
debian-archive-removed-keys.gpg
debian-archive-stretch-automatic.gpg
debian-archive-stretch-security-automatic.gpg
debian-archive-stretch-stable.gpg
debian-keyring.gpg
debian-maintainers.gpg
debian-nonupload.gpg
debian-role-keys.gpg
test.gpg
ubuntu-archive-keyring.gpg
ubuntu-archive-removed-keys.gpg
ubuntu-cloud-keyring.gpg
ubuntu-cloud-removed-keys.gpg
ubuntu-cloudimage-keyring.gpg
ubuntu-cloudimage-removed-keys.gpg
ubuntu-dbgsym-keyring.gpg
ubuntu-dbgsym-removed-keys.gpg
ubuntu-keyring-2012-archive.gpg
ubuntu-keyring-2012-cdimage.gpg
ubuntu-keyring-2012-cloud-archive.gpg
ubuntu-keyring-2016-dbgsym.gpg
ubuntu-keyring-2018-archive.gpg
ubuntu-master-keyring.gpg
root@debian:/usr/share/keyrings#

and then back to user account :
Code:
user1@debian:~$ cd gitian-builder
user1@debian:~/gitian-builder$ bin/make-base-vm --lxc --arch i386 --suite precise
[sudo] password for user1:
I: Target architecture can be executed
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
E: Release signed by unknown key (key id 40976EAF437D05B5)
   The specified keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg may be incorrect or out of date.
   You can find the latest Debian release key at https://ftp-master.debian.org/keys.html

 :'( :'( :'(


Title: Re: some errors for cloning
Post by: DaveF on January 12, 2020, 03:09:17 PM
I use second command on root access and it worked and then i tried to first command line on user account and i got below errors :


Quote
user1@debian:~/gitian-builder$ gpg --keyserver subkeys.pgp.net --recv 40976EAF437D05B5

gpg: keyserver receive failed: Connection timed out

For some reason you can't connect to subkeys.pgp.net try using

Code:
gpg --keyserver keyserver.ubuntu.com --recv 40976EAF437D05B5

I just did another test and it did work. I might have subkeys.pgp.ne pointed to something else but the last line just did work on a VM that is clean and on a separate network then most of my other stuff.

Is what you are working on a local PC, a local VM or something in the cloud?

-Dave


Title: Re: some errors for cloning
Post by: flyx on January 12, 2020, 03:40:17 PM
I use second command on root access and it worked and then i tried to first command line on user account and i got below errors :


Quote
user1@debian:~/gitian-builder$ gpg --keyserver subkeys.pgp.net --recv 40976EAF437D05B5

gpg: keyserver receive failed: Connection timed out

For some reason you can't connect to subkeys.pgp.net try using

Code:
gpg --keyserver keyserver.ubuntu.com --recv 40976EAF437D05B5

I just did another test and it did work. I might have subkeys.pgp.ne pointed to something else but the last line just did work on a VM that is clean and on a separate network then most of my other stuff.

Is what you are working on a local PC, a local VM or something in the cloud?

-Dave

I work on local pc (Virtualbox machine )

Code:
user1@debian:~/gitian-builder$ gpg --keyserver keyserver.ubuntu.com --recv 40976EAF437D05B5
gpg: key 40976EAF437D05B5: 60 signatures not checked due to missing keys
gpg: key 40976EAF437D05B5: public key "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1
Code:
user1@debian:~/gitian-builder$ bin/make-base-vm --lxc --arch amd64 --suite precise
[sudo] password for user1:
I: Target architecture can be executed
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
E: Release signed by unknown key (key id 40976EAF437D05B5)
   The specified keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg may be incorrect or out of date.
   You can find the latest Debian release key at https://ftp-master.debian.org/keys.html



Title: Re: some errors for cloning
Post by: DaveF on January 12, 2020, 04:30:17 PM
I am out of ideas, you might be better off posting in on a Debain forum / looking for help there.
Other members here might be able to help you but at this point I have no clue :(

-Dave


Title: Re: some errors for cloning
Post by: flyx on January 13, 2020, 06:23:50 AM
I am out of ideas, you might be better off posting in on a Debain forum / looking for help there.
Other members here might be able to help you but at this point I have no clue :(

-Dave

 :(


Title: Re: some errors for cloning
Post by: flyx on January 13, 2020, 07:37:08 AM
Is there anyway to import keys manual ?
Dont you think maybe a port is blocked?


Title: Re: some errors for cloning
Post by: DaveF on January 13, 2020, 12:02:27 PM
The key was imported, if you look at the output that flyx posted:

Quote
Code:
user1@debian:~/gitian-builder$ gpg --keyserver keyserver.ubuntu.com --recv 40976EAF437D05B5
gpg: key 40976EAF437D05B5: 60 signatures not checked due to missing keys
gpg: key 40976EAF437D05B5: public key "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1

Unless debian does something different then most other linux systems it's there. Which was why I have no idea.

-Dave


Title: Re: some errors for cloning
Post by: flyx on January 13, 2020, 01:29:54 PM
The key was imported, if you look at the output that flyx posted:

Quote
Code:
user1@debian:~/gitian-builder$ gpg --keyserver keyserver.ubuntu.com --recv 40976EAF437D05B5
gpg: key 40976EAF437D05B5: 60 signatures not checked due to missing keys
gpg: key 40976EAF437D05B5: public key "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1

Unless debian does something different then most other linux systems it's there. Which was why I have no idea.

-Dave

If key is impoted so why i receive out of date key message!
Code:
user1@debian:~/gitian-builder$ bin/make-base-vm --lxc --arch amd64 --suite precise
I: Target architecture can be executed
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
E: Release signed by unknown key (key id 40976EAF437D05B5)
   The specified keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg may be incorrect or out of date.
   You can find the latest Debian release key at https://ftp-master.debian.org/keys.html

I posted this issue on a debian forum someone answered maybe it's fail because system is debian but it suggest ubuntu key!

I'm using Debian 10 and ubuntu 16.04 , Which version of debian you recommend ?

Thanks


Title: Re: some errors for cloning
Post by: flyx on January 16, 2020, 07:04:16 AM
I reinstalled Debian with 8.55 ver , and now it seems all success full
But i see wrong URL at the last step , How can i correct this URL ??

Thanks

Code:
fatal: repository 'https://github.com/funcoin-project/funcoin.git/' not found
./bin/gbuild:23:in `system!': failed to run cd inputs/funcoin && git fetch --update-head-ok https://github.com/funcoin-project/funcoin.git +refs/tags/*:refs/tags/* +refs/heads/*:refs/heads/* (RuntimeError)
        from ./bin/gbuild:302:in `block in <main>'
        from ./bin/gbuild:288:in `each'
        from ./bin/gbuild:288:in `<main>'


Title: Re: some errors for cloning
Post by: flyx on January 16, 2020, 08:29:55 AM
I reinstalled Debian with 8.55 ver , and now it seems all success full
But i see wrong URL at the last step , How can i correct this URL ??

Thanks

Code:
fatal: repository 'https://github.com/funcoin-project/funcoin.git/' not found
./bin/gbuild:23:in `system!': failed to run cd inputs/funcoin && git fetch --update-head-ok https://github.com/funcoin-project/funcoin.git +refs/tags/*:refs/tags/* +refs/heads/*:refs/heads/* (RuntimeError)
        from ./bin/gbuild:302:in `block in <main>'
        from ./bin/gbuild:288:in `each'
        from ./bin/gbuild:288:in `<main>'
[/quote

I did edit gitian-win32.yml file  by nano command , if it was a correct way! , after running builder i got below errors :

Code:
user1@debian:~/gitian-builder$ ./bin/gbuild --commit test1=v0.8 ../test1/contrib/gitian-descriptors/gitian-win32.yml
Initialized empty Git repository in /home/user1/gitian-builder/inputs/test1/.git/
remote: Enumerating objects: 656, done.
remote: Counting objects: 100% (656/656), done.
remote: Compressing objects: 100% (562/562), done.
remote: Total 656 (delta 73), reused 656 (delta 73), pack-reused 0
Receiving objects: 100% (656/656), 4.28 MiB | 187.00 KiB/s, done.
Resolving deltas: 100% (73/73), done.
From https://github.com/mahyar-cpu/test1
 * [new branch]      master     -> master
error: pathspec 'v0.8' did not match any file(s) known to git.
./bin/gbuild:23:in `system!': failed to run cd inputs/test1 && git checkout -q v0.8 (RuntimeError)
        from ./bin/gbuild:303:in `block in <main>'
        from ./bin/gbuild:288:in `each'
        from ./bin/gbuild:288:in `<main>'
user1@debian:~/gitian-builder$


Title: Re: some errors for cloning
Post by: DaCryptoRaccoon on January 16, 2020, 06:54:51 PM
Off topic a bit but your not planning on building an altcoin from that youtube guide by any chance?
 
Just I noticed the funcoin git there that guide is outdated now and the code base used has some bugs and exploits now.

Feel free to PM me if your looking for something more up-to-date to follow.





Title: Re: some errors for cloning
Post by: flyx on January 17, 2020, 07:08:27 AM
Off topic a bit but your not planning on building an altcoin from that youtube guide by any chance?
 
Just I noticed the funcoin git there that guide is outdated now and the code base used has some bugs and exploits now.

Feel free to PM me if your looking for something more up-to-date to follow.





You are right , i'm learning from youtube , I sent you PM
Thanks


Title: Re: some errors for cloning
Post by: flyx on January 17, 2020, 11:35:11 AM
I edited clone and then cloning it again , on new version i see below error :

Do you know how to fix it

Code:
[code]user1@debian:~/gitian-builder$ ./bin/gbuild --commit funcoin=v0.1 ../funcoin/contrib/gitian-descriptors/gitian-win32.yml
remote: Enumerating objects: 656, done.
remote: Counting objects: 100% (656/656), done.
remote: Compressing objects: 100% (562/562), done.
remote: Total 656 (delta 73), reused 656 (delta 73), pack-reused 0
Receiving objects: 100% (656/656), 4.28 MiB | 212.00 KiB/s, done.
Resolving deltas: 100% (73/73), done.
From https://github.com/mahyar-cpu/funcoin
 * [new branch]      master     -> master
error: pathspec 'v0.1' did not match any file(s) known to git.
./bin/gbuild:23:in `system!': failed to run cd inputs/funcoin && git checkout -q v0.1 (RuntimeError)
        from ./bin/gbuild:303:in `block in <main>'
        from ./bin/gbuild:288:in `each'
        from ./bin/gbuild:288:in `<main>'
[/code]


Title: Re: some errors for cloning
Post by: DaCryptoRaccoon on January 17, 2020, 11:53:14 AM
I edited clone and then cloning it again , on new version i see below error :

Do you know how to fix it

Code:
[code]user1@debian:~/gitian-builder$ ./bin/gbuild --commit funcoin=v0.1 ../funcoin/contrib/gitian-descriptors/gitian-win32.yml
remote: Enumerating objects: 656, done.
remote: Counting objects: 100% (656/656), done.
remote: Compressing objects: 100% (562/562), done.
remote: Total 656 (delta 73), reused 656 (delta 73), pack-reused 0
Receiving objects: 100% (656/656), 4.28 MiB | 212.00 KiB/s, done.
Resolving deltas: 100% (73/73), done.
From https://github.com/mahyar-cpu/funcoin
 * [new branch]      master     -> master
error: pathspec 'v0.1' did not match any file(s) known to git.
./bin/gbuild:23:in `system!': failed to run cd inputs/funcoin && git checkout -q v0.1 (RuntimeError)
        from ./bin/gbuild:303:in `block in <main>'
        from ./bin/gbuild:288:in `each'
        from ./bin/gbuild:288:in `<main>'
[/code]

I would just forget about trying to clone funcoin it's a waste of time to be honest not only is the codebase so out of date the methods being used in the guide are out of date.

As a experiment it's fine but I would not release this if you make one also you cannot just clone a later repo and use the same guidelines as the codebase for Litecoin and Bitcoin have both changed drastically since this time and as such make a lot of what's in the guide outdated



Title: Re: some errors for cloning
Post by: flyx on January 17, 2020, 06:17:22 PM
So what clone course you recommend me for learning


Title: Re: some errors for cloning
Post by: flyx on January 19, 2020, 01:33:08 PM
Hello my friends
i began to cloning a pos coin , it seems they have little difference than mineable coins , as they have makefile.unix but pos coins have makefile.am .. I tried to compile coin by beloow command as it was correct on litecoin but i got error here :
Code:
 mahyar@mahyar-VirtualBox:~/Desktop/salva/src$ make -f makefile.am
make: makefile.am: No such file or directory

How can i compile a POS coin ?


Title: Re: some errors for cloning
Post by: flyx on January 27, 2020, 07:13:04 AM
I passed make command

when i try to edit Dnsseeds for cloning pivx , i receive some errors

I change below DNSseed to what when i want test it on VM :
vSeeds.push_back(CDNSSeedData(?));

Can someone guide me ?