GNU bug report logs - #42473
[PATCH] gnu: zrythm: Update to 0.8.694.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 42473 in the body.
You can then email your comments to 42473 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Alexandros Theodotou <alex <at> zrythm.org>
To: Guix patches <guix-patches <at> gnu.org>
Subject: [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Wed, 22 Jul 2020 09:34:45 +0100

[Message part 1 (text/plain, inline)]

Hi,

This is actually 2 patches. The first updates libcyaml and the 2nd
Zrythm. Note that I (Zrythm author) have added a trademark policy to
Zrythm that says modified versions that include the trademarks require
permission (as discussed on IRC with a few people):
https://www.zrythm.org/en/trademarks.html

I am not 100% sure if patching the xdg-open path counts as a modified
version, but in any case this email is signed using the same key used
to sign the release, so it can be interpreted as "written permission"
to redistribute this.

The FSDG allows trademarks from what I understand:
```
Trademarks are associated with some software. For example, the name of
a program may be trademarked, or its interface may display a
trademarked logo. Often, the use of these marks will be controlled in
some way; in particular, developers are commonly asked to remove
references to the trademark from the software when they modify it.

In extreme cases, these restrictions may effectively render the program
nonfree. It is unfair for someone to ask you to remove a trademark from
modified code if that trademark is scattered all throughout the
original source. As long as the practical requirements are reasonable,
however, free system distributions may include these programs, either
with or without the trademarks.

Similarly, the distribution itself may hold particular trademarks. It
is not a problem if modification requires removal of these trademarks,
as long as they can readily be removed without losing functionality.

However, it is unacceptable to use trademarks to restrict verbatim
copying and redistribution of the whole distribution, or any part.
```

And Zrythm now has a meson option for easily changing the program name,
if you  would prefer to rename it to something else (Z-Daw for
example). Changing the logo is also very trivial, and I plan to add
freely licensed replacements in future releases to make it even easier
to replace.

So it is up to the maintainers to decide if they want to keep Zrythm as
it is or rename it. Either way, I am happy with either decision,
although I would prefer if you were OK with keeping the "Zrythm" name
(as long as there's no patches to remove/add functionality or links to
the Zrythm website or things like that).

Thanks,
Alex

[0002-gnu-zrythm-Update-to-0.8.694.patch (text/x-patch, attachment)]

[0001-gnu-libcyaml-Update-to-1.1.0.patch (text/x-patch, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 42473 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Alexandros Theodotou <alex <at> zrythm.org>
Cc: 42473 <at> debbugs.gnu.org, GNU Guix maintainers <guix-maintainers <at> gnu.org>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Thu, 23 Jul 2020 00:16:23 +0200

Hi Alexandros,

Alexandros Theodotou <alex <at> zrythm.org> skribis:

> This is actually 2 patches. The first updates libcyaml and the 2nd
> Zrythm. Note that I (Zrythm author) have added a trademark policy to
> Zrythm that says modified versions that include the trademarks require
> permission (as discussed on IRC with a few people):
> https://www.zrythm.org/en/trademarks.html
>
> I am not 100% sure if patching the xdg-open path counts as a modified
> version, but in any case this email is signed using the same key used
> to sign the release, so it can be interpreted as "written permission"
> to redistribute this.

OK.  Perhaps right above the ‘name’ field of the package, you could add
a link to the trademark policy above and state that Guix has a written
permission to use it, with a link to your message?  That way we’ll have
an audit trail.

> The FSDG allows trademarks from what I understand:

Your interpretation seems correct to me.

> So it is up to the maintainers to decide if they want to keep Zrythm as
> it is or rename it. Either way, I am happy with either decision,
> although I would prefer if you were OK with keeping the "Zrythm" name
> (as long as there's no patches to remove/add functionality or links to
> the Zrythm website or things like that).

I don’t see any reason not to keep “Zrythm” as things stand.

Thoughts anyone?  (Cc: maintainers.)

Apart from that, the patches LGTM!

Thank you,
Ludo’.

Message #11 received at 42473 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: Alexandros Theodotou <alex <at> zrythm.org>, 42473 <at> debbugs.gnu.org,
 GNU Guix maintainers <guix-maintainers <at> gnu.org>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Wed, 22 Jul 2020 23:06:18 -0400

Hello,

Ludovic Courtès <ludo <at> gnu.org> writes:

> Hi Alexandros,
>
> Alexandros Theodotou <alex <at> zrythm.org> skribis:
>
>> This is actually 2 patches. The first updates libcyaml and the 2nd
>> Zrythm. Note that I (Zrythm author) have added a trademark policy to
>> Zrythm that says modified versions that include the trademarks require
>> permission (as discussed on IRC with a few people):
>> https://www.zrythm.org/en/trademarks.html
>>
>> I am not 100% sure if patching the xdg-open path counts as a modified
>> version, but in any case this email is signed using the same key used
>> to sign the release, so it can be interpreted as "written permission"
>> to redistribute this.
>
> OK.  Perhaps right above the ‘name’ field of the package, you could add
> a link to the trademark policy above and state that Guix has a written
> permission to use it, with a link to your message?  That way we’ll have
> an audit trail.

That's a good idea.

>> The FSDG allows trademarks from what I understand:
>
> Your interpretation seems correct to me.

To me as well.

>> So it is up to the maintainers to decide if they want to keep Zrythm as
>> it is or rename it. Either way, I am happy with either decision,
>> although I would prefer if you were OK with keeping the "Zrythm" name
>> (as long as there's no patches to remove/add functionality or links to
>> the Zrythm website or things like that).
>
> I don’t see any reason not to keep “Zrythm” as things stand.
>
> Thoughts anyone?  (Cc: maintainers.)

I wish the trademark restrictions were relaxed to include the right for
modifications made solely with the goal of
building/packaging/integrating the software with a free software
distribution.  This would make things hassle free and extra clear.

That said, I'm not opposed to include Zrythm as things stands, if other
maintainers are OK with it.

Maxim

Message #14 received at 42473 <at> debbugs.gnu.org (full text, mbox):

From: Alexandros Theodotou <alex <at> zrythm.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, Ludovic
 Courtès <ludo <at> gnu.org>
Cc: 42473 <at> debbugs.gnu.org, GNU Guix maintainers <guix-maintainers <at> gnu.org>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Sun, 26 Jul 2020 11:16:28 +0100

[Message part 1 (text/plain, inline)]

Hi,

Thanks for the feedback!

Attaching the updated patch.

Thanks,
Alex

On Wed, 2020-07-22 at 23:06 -0400, Maxim Cournoyer wrote:
> Hello,
> 
> Ludovic Courtès <ludo <at> gnu.org> writes:
> 
> > Hi Alexandros,
> > 
> > Alexandros Theodotou <alex <at> zrythm.org> skribis:
> > 
> > > This is actually 2 patches. The first updates libcyaml and the
> > > 2nd
> > > Zrythm. Note that I (Zrythm author) have added a trademark policy
> > > to
> > > Zrythm that says modified versions that include the trademarks
> > > require
> > > permission (as discussed on IRC with a few people):
> > > https://www.zrythm.org/en/trademarks.html
> > > 
> > > I am not 100% sure if patching the xdg-open path counts as a
> > > modified
> > > version, but in any case this email is signed using the same key
> > > used
> > > to sign the release, so it can be interpreted as "written
> > > permission"
> > > to redistribute this.
> > 
> > OK.  Perhaps right above the ‘name’ field of the package, you could
> > add
> > a link to the trademark policy above and state that Guix has a
> > written
> > permission to use it, with a link to your message?  That way we’ll
> > have
> > an audit trail.
> 
> That's a good idea.
> 
> > > The FSDG allows trademarks from what I understand:
> > 
> > Your interpretation seems correct to me.
> 
> To me as well.
> 
> > > So it is up to the maintainers to decide if they want to keep
> > > Zrythm as
> > > it is or rename it. Either way, I am happy with either decision,
> > > although I would prefer if you were OK with keeping the "Zrythm"
> > > name
> > > (as long as there's no patches to remove/add functionality or
> > > links to
> > > the Zrythm website or things like that).
> > 
> > I don’t see any reason not to keep “Zrythm” as things stand.
> > 
> > Thoughts anyone?  (Cc: maintainers.)
> 
> I wish the trademark restrictions were relaxed to include the right
> for
> modifications made solely with the goal of
> building/packaging/integrating the software with a free software
> distribution.  This would make things hassle free and extra clear.
> 
> That said, I'm not opposed to include Zrythm as things stands, if
> other
> maintainers are OK with it.
> 
> Maxim

[0002-gnu-zrythm-Update-to-0.8.694.patch (text/x-patch, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #17 received at 42473 <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: Alexandros Theodotou <alex <at> zrythm.org>
Cc: Ludovic Courtès <ludo <at> gnu.org>,
 42473 <at> debbugs.gnu.org, GNU Guix maintainers <guix-maintainers <at> gnu.org>,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Sun, 26 Jul 2020 19:08:08 +0200

[Message part 1 (text/plain, inline)]

Alexandros,

Thanks for discussing this!

+ ;; Zrythm contains trademarks and comes with a trademark policy 
found in
+ ;; TRADMARKS.md inside the release distribution.
    ^^^^^^^^^

Typo.

                                                   Guix has 
                                                   written
+ ;; permission to use the Zrythm trademarks:
+ ;; https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42473

So does everyone else.

This implies that Guix has some special right but AFAICT the 
linked URL does not grant a single exception to ‘unmodified 
copies’.  What's the intention behind this hunk?

Does the permission to ‘use the […] trademarks’ mean that we can 
now use them however we want?  Presumably not, but then Guix 
doesn't need any ‘written permission’ at all.  Your policy applies 
to everyone.

I'd love to see a trademark policy that doesn't mention Guix (or 
*anyone*) by name but gives us (and *anyone*) the freedom to do 
what we want to do: responsibly but independently maintain & 
redistribute a well-integrated, CVE-free ZRythm package.  I'm 
aware that I might be hoping for too much :-)

Kind regards,

T G-R

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 42473 <at> debbugs.gnu.org (full text, mbox):

From: Alexandros Theodotou <alex <at> zrythm.org>
To: Tobias Geerinckx-Rice <me <at> tobias.gr>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 42473 <at> debbugs.gnu.org,
 GNU Guix maintainers <guix-maintainers <at> gnu.org>,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Sun, 26 Jul 2020 20:26:32 +0100

[Message part 1 (text/plain, inline)]

Hi,

On Sun, 2020-07-26 at 19:08 +0200, Tobias Geerinckx-Rice wrote:

> So does everyone else.
> 
> This implies that Guix has some special right but AFAICT the 
> linked URL does not grant a single exception to ‘unmodified 
> copies’.  What's the intention behind this hunk? 
>  
> Does the permission to ‘use the […] trademarks’ mean that we can 
> now use them however we want?  Presumably not, but then Guix 
> doesn't need any ‘written permission’ at all.  Your policy applies 
> to everyone.

Let me propose this instead, which is much clearer and gives a lot of
freedom to Guix for further modifications:

```
Guix, as released by the GNU project on 
http://git.savannah.gnu.org/cgit/guix.git, has permission to include
this Zrythm release (cryptographically signed by Alexandros Theodotou)
in its package repositories with any modifications necessary to
integrate Zrythm into Guix, provided that those modifications do not
change any of the intended functionalities of Zrythm or any text or
media presented to the user by the Zrythm user interface (including,
but not limited to URLs, images and message prompts). Alexandros
Theodotou reserves the right to revoke this trademark permission if the
current guidelines are not met, subject to Alexandros Theodotou's sole
discretion.
```

I can add this to the TRADEMARKS.md file (along with permissions for
other distros in the future) and re-release in a couple of days, and as
long as this permission notice is present in future releases, Guix will
have permission to make any of the above changes. The last sentence is
just a failsafe/safeguard for me and seems like it's standard in all
trademark permissions.

What do you think?

> 
> I'd love to see a trademark policy that doesn't mention Guix (or 
> *anyone*) by name but gives us (and *anyone*) the freedom to do 
> what we want to do: responsibly but independently maintain & 
> redistribute a well-integrated, CVE-free ZRythm package.  I'm 
> aware that I might be hoping for too much :-)

While I wish I could do that as well, there are no other similar
examples to follow afaik and IANAL so I don't know how to put that
wording in legal terms that cannot be abused (giving permission to
*anyone* to do things with a trademark beyond what basic trademark law
allows does not sound like a good idea), besides giving specific
permission to trusted projects like GNU Guix, so I try to stay on the
safe side.

Thanks,
Alex

[signature.asc (application/pgp-signature, inline)]

Message #23 received at 42473 <at> debbugs.gnu.org (full text, mbox):

From: Leo Prikler <leo.prikler <at> student.tugraz.at>
To: Alexandros Theodotou <alex <at> zrythm.org>, Tobias Geerinckx-Rice
 <me <at> tobias.gr>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 42473 <at> debbugs.gnu.org,
 GNU Guix maintainers <guix-maintainers <at> gnu.org>,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Mon, 27 Jul 2020 00:51:47 +0200

Am Sonntag, den 26.07.2020, 20:26 +0100 schrieb Alexandros Theodotou:
> > I'd love to see a trademark policy that doesn't mention Guix (or 
> > *anyone*) by name but gives us (and *anyone*) the freedom to do 
> > what we want to do: responsibly but independently maintain & 
> > redistribute a well-integrated, CVE-free ZRythm package.  I'm 
> > aware that I might be hoping for too much :-)
> 
> While I wish I could do that as well, there are no other similar
> examples to follow afaik and IANAL so I don't know how to put that
> wording in legal terms that cannot be abused (giving permission to
> *anyone* to do things with a trademark beyond what basic trademark
> law
> allows does not sound like a good idea), besides giving specific
> permission to trusted projects like GNU Guix, so I try to stay on the
> safe side.
IANAL either, but instead of
```
You may distribute unaltered copies of Zrythm that include the Zrythm
trademarks without express permission from Alexandros Theodotou.
```
and
```
However, if you make any changes to Zrythm, you may not redistribute
that product using any Zrythm trademark without Alexandros Theodotou’s
prior written consent.
```
you should write something like
```
You may distribute unaltered copies of Zrythm that include the Zrythm
trademarks without express permission from Alexandros Theodotou.
You may further distribute altered copies of Zrythm that include the
Zrythm trademarks, provided that alterations solely serve the purposes
of:
- porting Zrythm to a platform or free software distribution not
already supported by Zrythm as-is, OR
- fixing a bug in Zrythm, that has already been acknowledged by
Alexandros Theodotou or [a bigger authority, e.g. there's a CVE], OR
- ...
In any case, you must preserve [bla bla bla], also you must provide (a
link to)? the original sources.  If you make any other changes, you may
not redistribute that product...
```

Roughly meaning: If it already works on Ubuntu, you shan't patch it to
make it work on Ubuntu.  If it doesn't work on Gentoo, you can patch it
until it works on Gentoo and no further.  If Alexandros Theodotou has a
bugfix for something already published in Git, but you need to backport
that fix, you can do it.  If there's a CVE you can patch it.  If any of
those patches goes beyond integration/bugfixing, that's a violation.  I
personally believe, that this should be clear enough in most cases, but
it needs slightly better legalese.

Regards, Leo

Message #26 received at 42473 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Alexandros Theodotou <alex <at> zrythm.org>
Cc: Tobias Geerinckx-Rice <me <at> tobias.gr>, 42473 <at> debbugs.gnu.org,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 GNU Guix maintainers <guix-maintainers <at> gnu.org>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Thu, 10 Sep 2020 12:22:50 +0200

Hi Alexandros!

AIUI, the FSDG-distro exemption at
<https://www.zrythm.org/en/trademarks.html> applies to the latest
release (and presumably foreseeable releases as well):

  You may further distribute altered copies of Zrythm that include the
  Zrythm trademarks, provided that alterations solely serve the purposes
  of:

  • porting Zrythm to a free system distribution currently approved by
    the Free Software Foundation at
    https://www.gnu.org/distros/free-distros.html, OR

  • fixing a bug in Zrythm that has already been acknowledged by
    Alexandros Theodotou or CVE (https://cve.mitre.org/)

(I personally think wording that also includes Debian and Fedora, for
instance, would be welcome, but it’s beyond the scope of this issue.)

There haven’t been further comments on this issue from fellow
co-maintainers so I would suggest that you post a patch updating to the
latest release and I’ll gladly apply it.

Thanks in advance, and apologies for the delay!

Ludo’.

Message #29 received at 42473 <at> debbugs.gnu.org (full text, mbox):

From: Alexandros Theodotou <alex <at> zrythm.org>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: Tobias Geerinckx-Rice <me <at> tobias.gr>, 42473 <at> debbugs.gnu.org,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 GNU Guix maintainers <guix-maintainers <at> gnu.org>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Thu, 10 Sep 2020 14:16:31 +0100

[Message part 1 (text/plain, inline)]

Hi Ludo,

> (I personally think wording that also includes Debian and Fedora, for
> instance, would be welcome, but it’s beyond the scope of this issue.)

Indeed, would be a good idea to add the "major" distros. Will add them
soon.

> There haven’t been further comments on this issue from fellow
> co-maintainers so I would suggest that you post a patch updating to
> the
> latest release and I’ll gladly apply it.

Attaching the 4 patches required to update zrythm to 0.8.911 (including
a new dependency: reproc, and updated dependencies: libaudec &
libcyaml).

For libaudec, mp3 handling is done via the embedded tinymp3 library now
(which could perhaps be packaged in the future and add an option to use
a system version) so ffmpeg is no longer necessary (same for zrythm).

For zrythm, I moved some dependencies from native-inputs to inputs
since they are better suited there (I was initially misunderstanding
what "native-inputs" meant when I first submitted it). Zstd is now also
a dependency (used to compress/decompress project files).

There are a few more updates I want to make to add support for optional
features but I will do that in future patches. Let's just get the
latest version working first.

Thanks,
Alex

On Thu, 2020-09-10 at 12:22 +0200, Ludovic Courtès wrote:
> Hi Alexandros!
> 
> AIUI, the FSDG-distro exemption at
> <https://www.zrythm.org/en/trademarks.html> applies to the latest
> release (and presumably foreseeable releases as well):
> 
>   You may further distribute altered copies of Zrythm that include
> the
>   Zrythm trademarks, provided that alterations solely serve the
> purposes
>   of:
> 
>   • porting Zrythm to a free system distribution currently approved
> by
>     the Free Software Foundation at
>     https://www.gnu.org/distros/free-distros.html, OR
> 
>   • fixing a bug in Zrythm that has already been acknowledged by
>     Alexandros Theodotou or CVE (https://cve.mitre.org/)
> 
> (I personally think wording that also includes Debian and Fedora, for
> instance, would be welcome, but it’s beyond the scope of this issue.)
> 
> There haven’t been further comments on this issue from fellow
> co-maintainers so I would suggest that you post a patch updating to
> the
> latest release and I’ll gladly apply it.
> 
> Thanks in advance, and apologies for the delay!
> 
> Ludo’.

[0004-gnu-zrythm-Update-to-0.8.911.patch (text/x-patch, attachment)]

[0003-gnu-libaudec-Update-to-0.2.3.patch (text/x-patch, attachment)]

[0002-gnu-libcyaml-Update-to-1.1.0.patch (text/x-patch, attachment)]

[0001-gnu-Add-reproc.patch (text/x-patch, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 42473 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Alexandros Theodotou <alex <at> zrythm.org>
Cc: Tobias Geerinckx-Rice <me <at> tobias.gr>, 42473 <at> debbugs.gnu.org,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 GNU Guix maintainers <guix-maintainers <at> gnu.org>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Fri, 11 Sep 2020 17:36:56 +0200

Hi,

Alexandros Theodotou <alex <at> zrythm.org> skribis:

> From 315b2618d2a95a950790d2a0bba05747b880505a Mon Sep 17 00:00:00 2001
> From: Alexandros Theodotou <alex <at> zrythm.org>
> Date: Thu, 10 Sep 2020 14:03:20 +0100
> Subject: [PATCH 4/4] gnu: zrythm: Update to 0.8.911.
>
> * gnu/packages/music.scm (zrythm): Update to 0.8.911.

This requires Meson 0.55 so it doesn’t work on master.

Could you add Meson 0.55 and have zrythm use it?

> From 10df2f9e6d8e533fc4df9ec067ef88468d788034 Mon Sep 17 00:00:00 2001
> From: Alexandros Theodotou <alex <at> zrythm.org>
> Date: Thu, 10 Sep 2020 13:49:51 +0100
> Subject: [PATCH 2/4] gnu: libcyaml: Update to 1.1.0.
>
> * gnu/packages/web.scm (libcyaml): Update to 1.1.0.
> ---
>  gnu/packages/web.scm | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/gnu/packages/web.scm b/gnu/packages/web.scm
> index b674019b8f..01f8a6bfc2 100644
> --- a/gnu/packages/web.scm
> +++ b/gnu/packages/web.scm
> @@ -5027,6 +5027,7 @@ written in C.  It is developed as part of the NetSurf project.")
>    (package
>      (name "libcyaml")
>      (version "1.0.1")
> +    (version "1.1.0")
>      (source
>       (origin
>         (method git-fetch)
> @@ -5036,6 +5037,7 @@ written in C.  It is developed as part of the NetSurf project.")
>         (file-name (git-file-name name version))
>         (sha256
>          (base32 "0h5ydyqdl8kzh526np3jsi0pm7ks16nh1hjkdsjcd6pacw7y6i6z"))))
> +        (base32 "1al5cbild3qimm59rmaj3i8m57qhinwshz7r67p7fqsccijrz71b"))))

This one is obviously broken.  I tried to redo it by hand, but then
zrythm would fail to build.

> From 62dbf6ea03a35300be72e220732c9fd7de2a5e60 Mon Sep 17 00:00:00 2001
> From: Alexandros Theodotou <alex <at> zrythm.org>
> Date: Thu, 10 Sep 2020 13:45:25 +0100
> Subject: [PATCH 1/4] gnu: Add reproc.
>
> * gnu/packages/cpp.scm (reproc): New variable.

Applied!

Could you resend the other 3 patches, making sure everything works on
master?

TIA!

Ludo’.

Message #35 received at 42473 <at> debbugs.gnu.org (full text, mbox):

From: Alexandros Theodotou <alex <at> zrythm.org>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: Tobias Geerinckx-Rice <me <at> tobias.gr>, 42473 <at> debbugs.gnu.org,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 GNU Guix maintainers <guix-maintainers <at> gnu.org>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Fri, 11 Sep 2020 17:52:35 +0100

[Message part 1 (text/plain, inline)]

Hi,

On Fri, 2020-09-11 at 17:36 +0200, Ludovic Courtès wrote:
> This requires Meson 0.55 so it doesn’t work on master.
> 
> Could you add Meson 0.55 and have zrythm use it?

Done. Not sure exactly what you expect but I added an additional
meson55 package and used it like #:meson ,meson55. Feel free to edit it
accordingly.

> > diff --git a/gnu/packages/web.scm b/gnu/packages/web.scm
> > index b674019b8f..01f8a6bfc2 100644
> > --- a/gnu/packages/web.scm
> > +++ b/gnu/packages/web.scm
> > @@ -5027,6 +5027,7 @@ written in C.  It is developed as part of the
> > NetSurf project.")
> >    (package
> >      (name "libcyaml")
> >      (version "1.0.1")
> > +    (version "1.1.0")
> >      (source
> >       (origin
> >         (method git-fetch)
> > @@ -5036,6 +5037,7 @@ written in C.  It is developed as part of the
> > NetSurf project.")
> >         (file-name (git-file-name name version))
> >         (sha256
> >          (base32
> > "0h5ydyqdl8kzh526np3jsi0pm7ks16nh1hjkdsjcd6pacw7y6i6z"))))
> > +        (base32
> > "1al5cbild3qimm59rmaj3i8m57qhinwshz7r67p7fqsccijrz71b"))))
> 
> This one is obviously broken.  I tried to redo it by hand, but then
> zrythm would fail to build.

Err, gitg miss, I only selected the additions to stage. Fixed.

> Could you resend the other 3 patches, making sure everything works on
> master?

Please find them attached.

Thanks,
Alex

[0004-gnu-zrythm-Update-to-0.8.911.patch (text/x-patch, attachment)]

[0003-gnu-libaudec-Update-to-0.2.3.patch (text/x-patch, attachment)]

[0002-gnu-libcyaml-Update-to-1.1.0.patch (text/x-patch, attachment)]

[0001-gnu-Add-meson55.patch (text/x-patch, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #40 received at 42473-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Alexandros Theodotou <alex <at> zrythm.org>
Cc: Tobias Geerinckx-Rice <me <at> tobias.gr>, 42473-done <at> debbugs.gnu.org,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 GNU Guix maintainers <guix-maintainers <at> gnu.org>
Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Sun, 13 Sep 2020 23:37:36 +0200

Hi,

Alexandros Theodotou <alex <at> zrythm.org> skribis:

> On Fri, 2020-09-11 at 17:36 +0200, Ludovic Courtès wrote:
>> This requires Meson 0.55 so it doesn’t work on master.
>> 
>> Could you add Meson 0.55 and have zrythm use it?
>
> Done. Not sure exactly what you expect but I added an additional
> meson55 package and used it like #:meson ,meson55. Feel free to edit it
> accordingly.
>
>> > diff --git a/gnu/packages/web.scm b/gnu/packages/web.scm
>> > index b674019b8f..01f8a6bfc2 100644
>> > --- a/gnu/packages/web.scm
>> > +++ b/gnu/packages/web.scm
>> > @@ -5027,6 +5027,7 @@ written in C.  It is developed as part of the
>> > NetSurf project.")
>> >    (package
>> >      (name "libcyaml")
>> >      (version "1.0.1")
>> > +    (version "1.1.0")
>> >      (source
>> >       (origin
>> >         (method git-fetch)
>> > @@ -5036,6 +5037,7 @@ written in C.  It is developed as part of the
>> > NetSurf project.")
>> >         (file-name (git-file-name name version))
>> >         (sha256
>> >          (base32
>> > "0h5ydyqdl8kzh526np3jsi0pm7ks16nh1hjkdsjcd6pacw7y6i6z"))))
>> > +        (base32
>> > "1al5cbild3qimm59rmaj3i8m57qhinwshz7r67p7fqsccijrz71b"))))
>> 
>> This one is obviously broken.  I tried to redo it by hand, but then
>> zrythm would fail to build.
>
> Err, gitg miss, I only selected the additions to stage. Fixed.
>
>> Could you resend the other 3 patches, making sure everything works on
>> master?
>
> Please find them attached.

Applied with the following tweaks:

  • Renamed Meson variable to ‘meson-0.55’.

  • Replaced libcyaml upgrade with my own version since I got a
    different hash than the one your patch had.  If you still have a
    different version, please check whether there are differences.

Thanks!

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.