Date: Sun, 10 Jul 2022 22:34:02 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 265138] www/chromium: Multiple versions of 103.0.5060.114 distfile. Message-ID: <bug-265138-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265138 Bug ID: 265138 Summary: www/chromium: Multiple versions of 103.0.5060.114 distfile. Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: chromium@FreeBSD.org Reporter: peterj@FreeBSD.org Assignee: chromium@FreeBSD.org Flags: maintainer-feedback?(chromium@FreeBSD.org) Whilst trying to upgrade to 103.0.5060.114, I noticed that the fetch from https://commondatastorage.googleapis.com/chromium-browser-official/ failed = the distfiles checksum, though the alternate fetch from https://nerd.hu/distfil= es/ matched. Since the former is the "official" site and should be the more se= cure of the two sites, I believe this is worth reporting. Having unpacked the .tar.xz files from both locations, there are no actual source differences (though there are a number of changed .pyc files). There are, however, a significant number of files that have been added to or remo= ved from the third_party trees in the two versions. I suspect that the distribution has been re-rolled for some reason, though = I'm not familiar enough with the Chromium build process to know why that may ha= ve occurred. I retrieved the following file from the googleapis.com site: server% l chromium-103.0.5060.114.tar.xz=20 -rw-r--r-- 1 peter wheel 1470895580 10 Jul 19:28 chromium-103.0.5060.114.tar.xz server% sha256 chromium-103.0.5060.114.tar.xz=20 SHA256 (chromium-103.0.5060.114.tar.xz) =3D 77683510f03b947332461b03954488474d95e49992efc11908f4bd8045635965 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265138-7788>