unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org, Raghav Gururajan <rg@raghavgururajan.name>
Subject: Re: GNOME 3.34 in GNU Guix and security
Date: Fri, 19 Mar 2021 10:13:48 +0100	[thread overview]
Message-ID: <871rcbijzn.fsf@yamatai> (raw)
In-Reply-To: <20210318223215.382fda54@scratchpost.org>

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]


Danny Milosavljevic <dannym@scratchpost.org> skribis:

> Hello,
>
> core-updates is still in a pretty bad state.
>
> [...]
>
> A short summary of what is at least broken:
>
> [...]
> (2) Source files have been in-place replaced upstream with a lot of packages (see my bug report about the topic).  fldigi has such a problem but can just be updated.  This is easy to see by just building without substitutes--and it doesn't do anyone any good for me to file individual bug reports for each and every one of those
> [...]

Concerning the disappearing source tarballs of older fldigi versions on
the official website, it has been fixed on master
(65e9f13116edc58836cdbd1da60bfb81a3d58c82), but core-updates hasn't
merged that in yet.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2021-03-19  9:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  3:19 GNOME 3.34 in GNU Guix and security Léo Le Bouter
2021-03-11  8:08 ` Ricardo Wurmus
2021-03-11  8:23   ` Raghav Gururajan
2021-03-11  9:11     ` Ricardo Wurmus
2021-03-11  9:17       ` Raghav Gururajan
2021-03-18 21:32     ` Danny Milosavljevic
2021-03-19  0:10       ` Ricardo Wurmus
2021-03-19  9:13       ` Guillaume Le Vaillant [this message]
2021-03-11  8:24   ` Jonathan Brielmaier
2021-03-11  8:18 ` Mark H Weaver
2021-03-11  8:28   ` Léo Le Bouter

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=871rcbijzn.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=rg@raghavgururajan.name \
    /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).