On Thu, Sep 1, 2016 at 1:13 PM, Jeroen Mathon <jeroenmathonmac@gmail.com> wrote:
Random, get your shit from bitcoins site then. :p
On Thu, 1 Sep 2016, 18:13 Diego Viola via arch-general, <arch-general@archlinux.org> wrote:
On Thu, Sep 1, 2016 at 1:08 PM, D C via arch-general <arch-general@archlinux.org> wrote:
Some people don't get the concept of volunteering lol.
On Thu, Sep 1, 2016 at 12:06 PM, Jeroen Mathon via arch-general < arch-general@archlinux.org> wrote:
Some people have projects, or other things that take priority, if you have a problem then get the git version from the AUR
On Thu, 1 Sep 2016, 18:01 Diego Viola via arch-general, < arch-general@archlinux.org> wrote:
On Thu, Sep 1, 2016 at 12:53 PM, Doug Newgard <scimmia@archlinux.info> wrote:
On Thu, 1 Sep 2016 12:42:24 -0300 Diego Viola via arch-general <arch-general@archlinux.org> wrote:
> Hello, > > I flagged this package 10 days ago as out of date and I've been > trying > to contact the maintainer about it, with no response. > > https://www.archlinux.org/packages/community/x86_64/bitcoin-qt/ > > Is there any problem with updating this? Any reasons for the delay > or > lack of response? > > Thanks, > Diego
Oh no, 10 days.
Seriously?
Other packages get updated much quicker, are you just going to put the blame the users on this one too?
Diego
-- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2
mQENBFOa9oMBCACc0vf5MZEKqfyCWw3foRhYqM3zL9zmIuDpLxGZ11BM6dLvTKVG xets5b2RZX+aPUbASnLFZWqANW2d5K+O7PNkvwKk7jJGu951WQkd1HGNHqQekb3Y SC6AOIt5G4Iu3xuJdbh8vuSU0tRIU3YVKSIWFCxgdTWO3XukgNYB1ncl39x4VGPh OsQ8ErsLfVMCwO7q4eTTv89HQZEzvCI+BhMlw0bjViBeMe+4ZfYuiFJp9SyZBcTY rVkdnn5gVOeqhU1eAk4uieG1t/anGm3GQ6NVDnh/+k6in6SwSZ2jAUXQluCMmyNA aCOCz7G4kytg8qel3VvT4YuI7hFQxcg17DMnABEBAAG0HURvcmlhbiA8Y2FtZW5z Y2hpY0BnbWFpbC5jb20+iQE/BBMBAgApBQJTmvaDAhsDBQkFo5qABwsJCAcDAgEG FQgCCQoLBBYCAwECHgECF4AACgkQugwP0JaXCVNyvAf/Z9gAtGh4SSxNv0/CWFxL d5P6ikr8qGD9sVuH1QZa90zigmhAngfQyMF0DuPVnRTcVu0pwFObkvdI0/11UaSj Rdst9sPFV5b4wfLfGw4MinO9vTD7RQoLisnggaroNk98I894lvgtVWECxHYdPnW+ VJWNONAfTOUjfqPVV7B2A35N4DxkgBM0VNdqpcd0Qj6acEaGRcGBlQUyssy+NYEr 5+nS9c58eM9wqxkcaWy2axrX2vvQth5PedGjZl53gsR3cSWLpFmyryyyVi2da4rv IFLdhZaZfWyRG7y0MTnPdi8NRwBO33r2UX0W+BC8VvGBjob17EgCZT06QHGzAs9F fLkBDQRTmvaDAQgA2p9RwuEWF16nWkc+z/5Vu6KlQh9paxw1zEHlmC+r103tWby8 27BLocuD7hKqcweuu17HL0LW1iSYfhr/iXDOTiJ5LsKXtBMYAVXbhamLKNOuHTO1 qFdA55f6vtY/eMdWQ8qM+q31cLX0WYiQdsGonuIzqeIXETnmq9rx7fRaxpvv6K4Y 0u9N1NFwrpz2eOuIX/KFicoZs1tGID5OjnL2QB897za8i56oKjHFwNzZCndESc3h 78HXNzu7XMjRQHN8QvwybpWhtDanLd/3ZFvHMViZT9Zo2KAMsCgPNkqDe9SXrrEC vEYgZn0QO3Akrk1FmmzCCgMzP3F9l3czBNK7mwARAQABiQElBBgBAgAPBQJTmvaD AhsMBQkFo5qAAAoJELoMD9CWlwlTfKQH/2UsN6WgoyMGgRFm+INdAT8/ew4r30l5 mTMKuAfpLs9lbIfeRJoq2+HtKsv8MNzYYCR595tdI9kTijhD0RKKhEfacBLIZFvZ 0j5SLaR+PC7Ky+KAIXIIZnrHsFAQR21Hup0POxuWeuvs0pfcFWTnNEb6cZHzTP7J YnUA/khgamUK/uWWymKxOsgR5A/zzHrjnWgMws7vKi7Kd0gvr2t/X393iAxvfUqT IGiSx+fq/bGB8uyTuQPFpaDRNMo7k2knzQzt4idSKz89tejWyimS71QdnmPWJP84 OTnHUaGQdQamnAQqh5g3GC6XqS57apLQZx+7Y7WUpPjeX/+vQ2GtzuE= =RFjZ -----END PGP PUBLIC KEY BLOCK-----
I get the concept of volunteering just fine, I've been using Linux for as long as I remember and I actually contributed to the Linux kernel itself. Thank you very much.
Thing is, I use bitcoin-qt to get paid for work, and I'm not going to put my hard earned money on random AUR packages for this.
The reason I trust the package from the repo is that I'm hoping I can verify by signing them in some way, but there's no way I'm using some random AUR package for this.
Diego
Sorry, I didn't meant to be rude or be offensive towards the AUR, the AUR is great, but when using things like bitcoin, how can you be safe that using bitcoin-qt from the AUR is fine? What Emily suggested, actually building it myself works fine, but is there anything else I can do in order to verify my binaries if I'm using someone else's build? Diego