From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>,
Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: MTP & Guix
Date: Sun, 24 Jun 2018 17:12:27 +0200 [thread overview]
Message-ID: <8736xcfcbo.fsf@fastmail.com> (raw)
In-Reply-To: <87k1qosdt7.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Pierre Neidhardt <ambrevar@gmail.com> writes:
>>
>>> Both Gentoo and Guix packages are outdated.
>>> 1.37 is out.
>>> GVFS has switched to Meson in the mean time.
>>> Arch is a little bit more up to date:
>>>
>>> https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/gvfs
>>>
>>> I guess the above definition could help.
>>> Anyone giving the update a shot?
>>
>> I’m already working on the upgrades to all of GNOME, including the gvfs
>> upgrade to 1.36.2.
>
> This happens on the “core-updates” branch.
Could you create a 'gnome-updates' branch for this? That makes it
easier to track the changes, and allows for building it without
rebuilding the entire world.
We might want to merge it to core-updates rather than build it on its
own regardless, but at least we have the option. What do you think?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-06-24 15:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 14:22 MTP & Guix Pierre Neidhardt
2018-06-23 17:53 ` Ricardo Wurmus
2018-06-23 17:59 ` Thompson, David
2018-06-23 18:02 ` Pierre Neidhardt
2018-06-23 18:03 ` Thompson, David
2018-06-23 19:59 ` swedebugia
2018-06-23 20:25 ` Pierre Neidhardt
2018-06-24 9:30 ` Ricardo Wurmus
2018-06-24 10:01 ` Ricardo Wurmus
2018-06-24 15:12 ` Marius Bakke [this message]
2018-06-28 13:08 ` GNOME updates (was: MTP & Guix) Ricardo Wurmus
2018-07-05 10:31 ` MTP & Guix Chris Marusich
2018-07-07 3:57 ` Maxim Cournoyer
2018-07-07 7:25 ` Pierre Neidhardt
2018-07-08 16:30 ` Maxim Cournoyer
2018-07-08 19:51 ` Pierre Neidhardt
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=8736xcfcbo.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).