From: tuxslack <tuxslack@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: google-chrome ERROR: SHA256 mismatch for EULA
Date: Sun, 01 Oct 2023 20:33:05 +0200 [thread overview]
Message-ID: <20231001183305.pkypgJn3H3hmGPihGMBQmb-T2wdq_rQaYEe05AoD3tM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46347@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2738 bytes --]
New comment by tuxslack on void-packages repository
https://github.com/void-linux/void-packages/issues/46347#issuecomment-1742162388
Comment:
**maintainer:** Michael Aldridge <maldridge@voidlinux.org>
**homepage:** https://www.google.com/chrome/
**filename-sha256:** b3417497ae1b375962b121e0b20727c667c689cfdceacc43dd4e94cc32c63fb0
**metafile-sha256:** aa00be5f9546cae372b4eb0ae3b7665023e9fe5e0e85803d4cc5d29fdee423cf
===============================================================
cd ~/void-packages/
git pull && ./xbps-src update-sys
...
=> xbps-src: the following packages must be rebuilt and updated:
google-chrome
=> xbps-src: building google-chrome-117.0.5938.132_1 ...
=> xbps-src: updating repositories for host (x86_64)...
[*] Updating repository `https://repo-default.voidlinux.org/current/bootstrap/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/nonfree/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/debug/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/multilib/bootstrap/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/multilib/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/multilib/nonfree/x86_64-repodata' ...
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> google-chrome-117.0.5938.132_1: removing autodeps, please wait...
=> google-chrome-117.0.5938.132_1: building for x86_64...
[host] python3-html2text-2020.1.16_5: found (https://repo-default.voidlinux.org/current)
[host] python3-setuptools-68.2.2_1: found (https://repo-default.voidlinux.org/current)
[runtime] gtk+3-3.24.38_1: found (https://repo-default.voidlinux.org/current)
=> google-chrome-117.0.5938.132_1: installing host dependencies: python3-html2text-2020.1.16_5 python3-setuptools-68.2.2_1 ...
=> google-chrome-117.0.5938.132_1: running do-extract hook: 00-distfiles ...
=> google-chrome-117.0.5938.132_1: extracting distfile(s), please wait...
=> google-chrome-117.0.5938.132_1: running post_extract ...
google-chrome-eula.html: [93KB 4%] 20KB/s ETA: 00m00s
google-chrome-eula.html: [93KB 21%] 18KB/s ETA: 00m03s
google-chrome-eula.html: [93KB 59%] 27KB/s ETA: 00m01s
google-chrome-eula.html: [93KB 77%] 24KB/s ETA: 00m00s
google-chrome-eula.html: 93KB [avg rate: 31KB/s]
**=> ERROR: SHA256 mismatch for EULA:
c57f6063f0ef7f6cd0f93cc6004ba86be0df36eca92be054bbb3b424dbd7830c
=> ERROR: xbps-src: failed to build google-chrome-117.0.5938.132_1 pkg!**
next prev parent reply other threads:[~2023-10-01 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 13:59 [ISSUE] " rickalex21
2023-10-01 14:10 ` classabbyamp
2023-10-01 18:33 ` tuxslack [this message]
2023-10-01 18:50 ` [ISSUE] [CLOSED] " classabbyamp
2023-10-02 4:36 ` classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231001183305.pkypgJn3H3hmGPihGMBQmb-T2wdq_rQaYEe05AoD3tM@z \
--to=tuxslack@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).