From: Marius Bakke <mbakke@fastmail.com>
To: Vagrant Cascadian <vagrant@debian.org>, guix-devel@gnu.org
Subject: Re: State of ungoogled-chromium in Guix
Date: Sun, 10 Nov 2019 23:56:57 +0100 [thread overview]
Message-ID: <87h83bjq6e.fsf@devup.no> (raw)
In-Reply-To: <875zjr4hch.fsf@yucca>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
Vagrant Cascadian <vagrant@debian.org> writes:
> On 2019-10-23, Marius Bakke wrote:
>> Version 78 of the upstream Chromium project was released yesterday, with
>> the usual amount of security fixes:
>>
>> https://chromereleases.googleblog.com/2019/10/stable-channel-update-for-desktop_22.html
>>
>> Unfortunately the 'ungoogled-chromium' variant in Guix is still stuck on
>> version 76. The reason is that we rely on Debians patches, which have
>> gone stale:
>>
>> https://salsa.debian.org/chromium-team/chromium
>
> 78.0.x was uploaded to Debian yesterday, FWIW:
>
> https://tracker.debian.org/news/1078440/accepted-chromium-780390497-1-source-into-unstable/
Thanks for the heads-up. I don't have time to proceed with the upgrade
right now, but will get on it 'eventually'. Help welcome :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2019-11-10 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 20:00 State of ungoogled-chromium in Guix Marius Bakke
2019-10-24 22:03 ` Tobias Geerinckx-Rice
2019-10-25 20:40 ` Ludovic Courtès
2019-11-03 18:46 ` Marius Bakke
2019-11-04 14:41 ` Ludovic Courtès
2019-11-10 20:16 ` Vagrant Cascadian
2019-11-10 22:56 ` Marius Bakke [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h83bjq6e.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).