Re: guix weather exit status?

[zimoun]

Hi,

On Sat, 10 Jul 2021 at 18:06, Leo Famulari  wrote:
> On Sat, Jul 10, 2021 at 04:41:44PM +0200, Ludovic Courtès wrote:
>> I agree we could change (or rather refine) semantics to exit with
>> non-zero when overall coverage is below 100%.  In the example above, it
>> should return 0.
>
> Maybe we could distinguish between various cases like this:
>
> 0 means 100% coverage
> 1 means a substitute is available, but not from all servers
> 2 means a substitute is not available
>
> This would preserve the current meaning of 0, while still allowing `guix
> weather` to be used in scripts to "wait for a substitute".

What about two or more packages?  “guix weather foo bar” when the
package ’foo’ is available on one server and ’bar’ is not at all.  Or if
’foo’ is available on one server and ’bar’ on the other.  Etc.

We could have:

 0 100% all servers
 1 100% from one server
 2 100% from a server mix
 3 one or more substitute is missing

WDYT?

Cheers,
simon

Audacity has new administration

[Bone Baboon]

# Contents

* Audacity's new administration
* Controversial Changes to Audacity
* Audacity Forks
* Guix and Audacity

# Audacity's new administration

Audacity has new administration.  Based on these announcements Audacity
is now part of Muse Group.

May 3 2021 this announcement was made on Audacity's website


April 30 2021 this announcement was made by the new lead of audacity:

Invidious link

YouTube link


# Controversial Changes to Audacity

Muse Group has made several controversial changes to Audacity.

Three controversial changes were:

* The introduction of telemetry
  
  

* The introduction of a contributor license agreement
  

* A new privacy policy
  
  
  
  

The introduction of telemetry has been discussed here
.

# Audacity Forks

The controversial changes to Audacity by Muse Group has motivated
several Audacity forks.

One example of a fork is .
That fork gives this rational for it's existence
.
Which includes some of the links in the to the Controversial Changes to
Audacity section above.

It is probably to early to tell which if any of the Audacity forks are
going to be maintained over an extended period of time.

# Guix and Audacity

Guix packages the 2.4.2 version of Audacity.

Looking at /gnu/packages/audio.scm the source code repository Guix uses
for audacity is  which is now
controlled by Muse Group.

Based on Audacity release information
 version
2.4.2 was released on 26 June 2020.  This is before Muse Group acquired
administrative control of Audacity some time between April 30 2021 and
May 3 2021.  So no action is currently required by Guix in regards to
it's Audacity package.

The most current version of Audacity before Muse Group acquired
administrative control of Audacity was version 3.0.2 which released on
19 April 2021.

Before the next update of the version of Audacity that Guix packages it
would probably be a good idea to reassess the situation with Muse
Group's Audacity and the Audacity forks.

Re: Effectively force all GNOME users to locally compile ZFS?

[Mark H Weaver]

Hi Tobias,

Tobias Geerinckx-Rice  writes:
> Something about this virt-manager reasoning strikes me as bogus, 

According to ,
"a module covered by the GPL and a module covered by the CDDL cannot
legally be linked together."

 Regards,
   Mark

--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about .

cowsay could attract copyright and trademark enforcement action

[Bone Baboon]

cowsay has many questionable files that could attract copyright and
trademark enforcement action.  For further details see the pull
requested linked below.

Guix packages cowsay.  /gnu/packages/games.scm says that the source code
repository used is .
In that repository's CONTRIBUTING.md it says "Issues and pull requests
on that repository will be ignored.".  I submitted a pull request
.  I expect that
it will be ignored.

I have also found a fork of cowsay
 that claims to be maintained.
I have submitted a pull request to it as well.
 

It would be good to have this issue addressed upstream.  I have just
submitted these pull requests.  I will provide an update if either pull
request is merged (modified or unmodified).  If neither repository makes
any changes to address these questionable files then it may make sense
for Guix to patch the cowsay package.