Re: Staging branch

2020-12-28 Thread Efraim Flashner
On Wed, Dec 23, 2020 at 05:46:25PM -0500, Leo Famulari wrote:
> On Wed, Dec 23, 2020 at 12:27:22AM -0500, Leo Famulari wrote:
> > ... and reply with any problems.
> 
> The package kwidgetsaddons fails its test suite like this:
> 
> --
> * Start testing of KColumnResizerTest *
> Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 7.5.0), unknown unknown
> PASS   : KColumnResizerTest::initTestCase()
> QWARN  : KColumnResizerTest::test(forms) This plugin does not support 
> propagateSizeHints()
> PASS   : KColumnResizerTest::test(forms)
> QWARN  : KColumnResizerTest::test(grids) This plugin does not support 
> propagateSizeHints()
> PASS   : KColumnResizerTest::test(grids)
> QWARN  : KColumnResizerTest::test(grid-and-form) This plugin does not support 
> propagateSizeHints()
> FAIL!  : KColumnResizerTest::test(grid-and-form) Compared values are not the 
> same
>Actual   (widget1->x()): 145
>Expected (widget2x): 161
>Loc: 
> [/tmp/guix-build-kwidgetsaddons-5.70.0.drv-0/kwidgetsaddons-5.70.0/autotests/kcolumnresizertest.cpp(83)]
> PASS   : KColumnResizerTest::cleanupTestCase()
> Totals: 4 passed, 1 failed, 0 skipped, 0 blacklisted, 18ms
> * Finished testing of KColumnResizerTest *
> 
> 
> 95% tests passed, 1 tests failed out of 19
> 
> Total Test time (real) =   8.27 sec
> 
> The following tests FAILED:
>19 - kwidgetsaddons-kcolumnresizertest (Failed)
> Errors while running CTest
> make: *** [Makefile:110: test] Error 8
> 
> Test suite failed, dumping logs.
> --
> 
> I tried using the newer version of this package (5.71) but it fails due
> to incompatibilities with the rest of the KDE frameworks.
> 
> Any ideas?
> 

I got the same error while trying to build my profile.

I also got a transient test-suite error while building tuir, but it
passed after the 5th try.

-- 
Efraim Flashner  אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted


signature.asc
Description: PGP signature


Re: Commit Access

2020-12-28 Thread Amin Bandali
Hello,

Leo Prikler writes:

> Hello everyone,
>
> earlier today, I was granted commit access to the repository [1].
[...]

Welcome, Leo!


signature.asc
Description: PGP signature


Re: Commit Access

2020-12-28 Thread Tobias Geerinckx-Rice

Leo,

Leo Prikler 写道:
earlier today, I was granted commit access to the repository 
[1].  This
message is signed with the key I will use for signing my 
commits.  It

should have the following info:


Excellent news.  Welcome!

Kind regards,

T G-R


signature.asc
Description: PGP signature


Commit Access

2020-12-28 Thread Leo Prikler
Hello everyone,

earlier today, I was granted commit access to the repository [1].  This
message is signed with the key I will use for signing my commits.  It
should have the following info:

pub   rsa4096 2020-12-16 [SC]
  ACC23BA059F7CCF408F043AD442A84B8C70E2F87
uid   [ultimate] Leo Prikler 

You can also grab it directly from Guix [2] or my Savannah page [3].

I'm looking forward to working with all of you.  Please take care of
me.

Regards,
Leo

[1] 
http://git.savannah.gnu.org/cgit/guix.git/commit/?id=98471d578679e25fd9c28097ea017aa4035ae8dd
[2] 
http://git.savannah.gnu.org/cgit/guix.git/tree/leoprikler-C70E2F87.key?h=keyring
[3] https://savannah.gnu.org/users/leoprikler 


signature.asc
Description: This is a digitally signed message part


Move LV2 plugins to dedicated module?

2020-12-28 Thread Ricardo Wurmus
Hi Guix,

we have a whole bunch of LV2 audio plugins.  We don’t have a naming
convention for them (there’s no guarantee the name includes “lv2”) and
we seem to be adding these packages to (gnu packages audio) or (gnu
packages music).

What do you think about moving them all to a new module?  And what do
you think about finding a naming convention, such as beginning the
package name with “lv2-”?

-- 
Ricardo