From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] google-chrome ERROR: SHA256 mismatch for EULA
Date: Sun, 01 Oct 2023 20:50:06 +0200 [thread overview]
Message-ID: <20231001185006.iCNGI1ZKkUFxHUX4jdaeGRcfGkkORPgrcukbnDNbVkc@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: 622 bytes --]
Closed issue by rickalex21 on void-packages repository
https://github.com/void-linux/void-packages/issues/46347
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.13_1 x86_64 AuthenticAMD uptodate rFFFFF
### Package(s) Affected
google-chrome-115.0.5790.110_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
no
### Expected behaviour
Expected to upgrade google-chrome.
### Actual behaviour
=> ERROR: SHA256 mismatch for EULA:
c57f6063f0ef7f6cd0f93cc6004ba86be0df36eca92be054bbb3b424dbd7830c
### Steps to reproduce
xbps-src pkg google-chrome
next prev parent reply other threads:[~2023-10-01 18:50 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
2023-10-01 18:50 ` classabbyamp [this message]
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=20231001185006.iCNGI1ZKkUFxHUX4jdaeGRcfGkkORPgrcukbnDNbVkc@z \
--to=classabbyamp@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).