Re: GNU Guix 0.8.2 released

2015-05-14 Thread Andy Tai
   *** The ‘define-gexp-compiler’ form allows (guix gexp) to be extended
>
>   *** New ‘local-file’ constructor exported by (guix gexp)
>
>   ** Noteworthy bug fixes
>
>   *** Profiles created with ‘guix package -p’ as indirect GC roots
>
>   Before that they were made permanent GC roots–i.e., uncollectable.
>
>   *** ‘guix package’ distinguishes downgrades from upgrades
>
>   *** Handle HTTP redirects to relative URI references
>   (<http://bugs.gnu.org/19840>)
>
>   *** Downloads now honor the ‘http_proxy’ environment variable
>   (<http://bugs.gnu.org/20402>)
>
>   *** ‘--no-*’ options are now always correctly handled
>   (<http://lists.gnu.org/archive/html/guix-devel/2015-02/msg00702.html
> >)
>
>   *** SLiM no longer leaks open file descriptors
>
>   *** Don't compare  objects with 'equal?'
>   (<http://bugs.gnu.org/20037>)
>
>   *** x86_64 and i686 bootstrap binaries updated (<
> http://bugs.gnu.org/19780>)
>
>   *** ‘find-files’ no longer follows symlinks (<http://bugs.gnu.org/20081
> >)
>
>   *** libc message catalog (‘libc.mo’) is now installed
>
>   *** libstdc++ has appropriate RUNPATH (<http://bugs.gnu.org/20358>)
>
>   *** ‘dhcp-client-service’ now correctly tracks dhclient’s PID
>
>   ** Native language support
>
>   *** New translations: da (Danish)
>
>   *** Updated translations: eo
>
> Please report bugs to bug-g...@gnu.org.
> Join guix-devel@gnu.org and #guix on Freenode for discussions.
>
> Thanks to everyone who contributed to this release:
>
> 11  Alex Kost
>  1  Alex Sassmannshausen
>  4  Alexander I.Grafov (Axel)
>134  Andreas Enge
> 22  Andy Wingo
>  3  Christopher Allan Webber
>  3  Cyril Roelandt
>  5  David Hashe
> 41  David Thompson
>365  Eric Bavier
> 37  Federico Beffa
> 12  Jason Self
>460  Ludovic Courtès
>  3  Manolis Ragkousis
>182  Mark H Weaver
>  2  Mathieu Lirzin
> 16  Paul van der Walt
>  1  Pierre-Antoine Rault
>175  Ricardo Wurmus
>  1  Taylan Ulrich B
> 90  Taylan Ulrich Bayırlı/Kammer
> 28  Tomáš Čech
>  1  nebuli
>146  宋文武
>
> Ludovic, on behalf of the Guix team.
>
> --
> If you have a working or partly working program that you'd like
> to offer to the GNU project as a GNU package, see
> https://www.gnu.org/help/evaluation.html.
>



-- 
Andy Tai, a...@atai.org, Skype: licheng.tai
Year 2015 民國104年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能


Tom Lord passing

2022-07-19 Thread Andy Tai
Thomas Lord was an early (or the first?) maintainer of guile

from https://berkeleydailyplanet.com/issue/2022-06-26/article/49837

Obituaries

Thomas Lord
1966-2022

Trina Pundurs
Monday June 27, 2022 - 05:21:00 PM

Thomas Lord was born April 26, 1966 in Pittsburgh, Pennsylvania, where
he lived until the age of 10 when his family relocated to western
Massachusetts.

He graduated from Phillips Academy Andover in 1984.

He attended Johns Hopkins University and Carnegie Mellon University,
and in 1987 began his career as a software engineer at Carnegie
Mellon, working on the Andrew Project.

During this time he became interested in the free software movement
(http://www.gnu.org/philosophy/philosophy.html) and thereafter
dedicated himself to developing and supporting free software (aka
libre software or open source). He worked as an employee of the Free
Software Foundation, developing for the GNU Project, for several years
in the early 1990s.

In 1995 he first moved to Berkeley and began spending time in People’s
Park, a place and a society that held great meaning for him.

He returned to Pittsburgh PA in 1998, then came back to the Bay Area
in 2001 and relocated permanently to Berkeley in 2004.

In 2007 he married Trina Pundurs, his life partner since 1992.

Upon settling in Berkeley, he began engaging with city politics and
policymaking. His interest led him to contribute to the Berkeley Daily
Planet, and his work with Planet editor Becky O’Malley drew him
further into city and regional issues, especially housing,
displacement, and homelessness. In 2016 he was appointed by
then-Councilmember Cheryl Davila to serve on the City Housing Advisory
Commission.

In 2018 he was profoundly moved by a news report about scientists
weeping in the aisles at COP 24, where the IPCC presented its Special
Report on the impact of global warming of 1.5° C (“IPCC SR15”). Upon
studying SR15, and following the work of Greta Thunberg, he became a
tireless advocate of speaking the truth about the climate emergency
and treating it as an actual emergency.

In addition to his climate and housing activism, he spent several
years volunteering with students at Longfellow Middle School as part
of the Writer Coach Connection program.

He died unexpectedly this week of a massive brain hemorrhage.

Thomas is survived by his wife Trina Pundurs, mother Luanna
Pierannunzi, uncle Christopher Lord, aunt Sharlene Jones, and many
cousins and extended family.



Re: Tom Lord passing

2022-07-19 Thread Andy Tai
sorry... the mail was meant to go to another mailing list...

Tom Lord had no direct relation to guix

On Tue, Jul 19, 2022 at 4:30 PM Andy Tai  wrote:
>
> Thomas Lord was an early (or the first?) maintainer of guile
>
> from https://berkeleydailyplanet.com/issue/2022-06-26/article/49837
>
> Obituaries
>
> Thomas Lord
> 1966-2022



Fwd: question on setting up guix.scm for project development

2022-11-14 Thread Andy Tai
Hi, guix allows setting up an environment containing all the
dependencies for development of a package; this can be done via a
guix.scm file containing the package definition.

My question is, if I am developing a package which has dependencies
with newer versions than what is available in the guix repo, how can I
use the guix.scm file to bring in the new version of the dependencies?
 As an example:

Say  my package "my-package" has dependencies d1, d2, d3
where d2 in the current guix package repo is at version 0.1.2 but I
need a later release version 0.1.4; so I tried something like this:

guix.scm---
(use-modules (guix packages)
   )

(define-public d2-0.1.4
   (package
   (name "d2")
   (version "0.1.4")

   ...
)


(define-public my-package
   (package
  (name "my-package")
  (version "0.1")
 ...


 (input (list d1 d2-0.1.4 d3...)

))

my-package

---end guix.scm---


and if I use

guix shell -f -d ./guix.scm

this does not seem to generate an environment that contains the new
dependency, that is d2 version 0.1.4

I wonder how can this made to work?  Ideally no need to create a
private channel or such..  Thanks for info on this.



Re: Fwd: question on setting up guix.scm for project development

2022-11-15 Thread Andy Tai
Hi, thanks.

guix shell -D -f guix.scm

did work for me I did not see d2 0.1.4 from


guix package --list-installed
or
guix package --list-available
but

pkg-config --modversion d2

did show 0.1.4   So it is there, in this guix shell.

Thanks for all the replies to this question.

On Mon, Nov 14, 2022 at 10:15 PM Julien Lepiller  wrote:

> I think you got it right, I've used thas in the past. Maybe your cli
> options are out of order? Instead of -f -d, try -D -f. Do you even have d1
> or d3 in your current shell? Could they come from outside?
>
> Le 14 novembre 2022 19:41:58 GMT+01:00, Andy Tai  a écrit :
>>
>>
>> guix.scm---
>> (use-modules (guix packages)
>>)
>>
>> (define-public d2-0.1.4
>>(package
>>(name "d2")
>>(version "0.1.4")
>>
>>...
>> )
>>
>>
>> (define-public my-package
>>(package
>>   (name "my-package")
>>   (version "0.1")
>>  ...
>>
>>
>>  (input (list d1 d2-0.1.4 d3...)
>> 
>> ))
>>
>> my-package
>>
>> ---end guix.scm---
>>
>>


package update patches and "core-update" branch

2022-11-24 Thread Andy Tai
Hi, I sent in some patches for package updates for guix which got
merged; thanks for that. The review comments ask for future patches to
indicate if they should be for the core update branch.

Curious is there any guideline on when, and what type of, patches
should target core-update? Thanks



Package update patch review

2022-12-24 Thread Andy Tai
Hi, Merry Christmas!  A question, how to call attention to package
definition update patches that may have been waiting for review for some
time in the issue tracker/debug database? Some may have responses to prev
review comments.  Basically some kind of "ping" for such patches hanging
there.  Thanks


adding motif to guix

2023-01-08 Thread Andy Tai
Hi, motif was a major component of Unix for many years and it would be
good to add the (now free software) motif to GNU Guix.  Can package
reviewers take a look of the patch in this issue

https://issues.guix.gnu.org/59092

Thanks



Re: adding motif to guix

2023-01-08 Thread Andy Tai
It should be; openmotif was just some kind of marketing term

Although guix has some existing packages using lesstif, the now dead
early motif clone (as free software) and I don't know if emacs may be
using that...

On Sun, Jan 8, 2023 at 4:15 PM Eric Brown  wrote:
>
> Andy Tai  writes:
>
> > Hi, motif was a major component of Unix for many years and it would be
> > good to add the (now free software) motif to GNU Guix.  Can package
> > reviewers take a look of the patch in this issue
> >
> > https://issues.guix.gnu.org/59092
> >
> > Thanks
>
> Hello Andy:
>
> By chance is this the same as `openmotif' that is found in the likes of
> Debian, also referenced by programs such as GNU Emacs (--with-x-toolkit)
> ?
>
> Thanks,
> Eric



/bin/sh in package definitions

2023-01-13 Thread Andy Tai
Hi, currently package definitions often need to patch references to
/bin/sh as common in package sources or makefiles to make it refer to
the actual bash shell used in Guix in /gnu/store/... somewhere.

question 1:   is there a way, to simulate /bin/sh using container or
some such set up so the actual shell used by Guix can appear as
/bin/sh in the package build process?  (sorry if this is a wild
question)

question 2: (if question 1 is not possible) in guile, how to replace
only occurrences of /bin/sh, not substring "/bin/sh" in some strings
like /usr/bin/shsomethingsomethng, in the "patch" stage of package
building?



Guix QA: trigger rebuild

2023-01-21 Thread Andy Tai
Hi,  if Guix QA shows a patch build is failing and an updated patch
has been sent, how to trigger the build to be restarted? Thanks for
info



Guix QA: trigger rebuild

2023-01-21 Thread Andy Tai
Hi,  if Guix QA shows a patch build is failing and an updated patch
has been sent, how to trigger the build to be restarted? Thanks for
info



no (package definition) patch merged since Jan 2?

2023-01-25 Thread Andy Tai
Hi, by looking at

https://issues.guix.gnu.org/search?query=is%3Aclosed

no patch issues as listed in the issue tracker processed since Jan 2...
not sure if this is something Guix maintainers should be concerned about.



Re: Translation files .gmo and packaging

2023-01-26 Thread Andy Tai
Hi, I wonder how is this different from the common practice of
projects using GNU autotools, which the project in question is also
one, that the Makefile.in was generated from Makefile.am, but the
tarball may contain the "generated" Makefile.in and configure and Guix
won't bother to re-generate these two files.

In addition, git is a late comer to the free software world and tar
ball releases have been the preferred form of "sources" from the days
before git; whether git repo for the sources exists would not have
mattered, if the canonical source of the project source code is the
official release tarball.


> Date: Thu, 26 Jan 2023 12:39:30 +0100
> From: Simon Tournier 
> To: guix-devel@gnu.org
> Subject: Translation files .gmo and packaging
> Message-ID: <86h6wdsex9@gmail.com>
> Content-Type: text/plain
>
> Hi,
>
> The submission patch#61010 [1] relies on the release archive:
>
> https://github.com/ice-wm/icewm/releases/download/3.3.0/icewm-3.3.0.tar.lz
>
> and this archive contains the generated .gmo files.  However, these
> files are not in the archive:
>
> https://github.com/ice-wm/icewm/archive/refs/tags/3.3.1.tar.gz
>
> neither in the Git repository:
>
> https://github.com/ice-wm/icewm/tree/3.3.0/po
>
>
> The question is:
>
> What is the usual way to deal with these generated files?  Can we
> distribute them although it is not the Guix project that generates them
> from source?
>
> >From my understanding, the package should generate these files if
> possible and not rely on already generated ones.
>
> 1: 
>
> Cheers,
> simon
>
>



guix package updates review: app team?

2023-01-27 Thread Andy Tai
Hi, currently Guix has teams of reviewers for different types of
packages.   For example, changes to R packages and emacs seem to be
reviewed quickly.  However, recently, patches for updating more
general application packages (octave, for example) seem to be reviewed
and processed very slowly.

As a GNU/Linux distribution the update speed of applications impact
the perception of the community on a distribution, and thus it is
beneficial if packages update can be processed quickly to keep Guix
"up to date" so to speak.  Hope Guix maintainers can give some thought
to this and let more volunteers participate in package review process
to allow package updates more quickly.   As packages are usually at
the end of the dependency chain (they depend on other libraries or
components more than the other way around) updating packages shall
take less review effort.



Re: guix package updates review: app team?

2023-01-27 Thread Andy Tai
last paragraph shall be

As application packages are usually at
the end of the dependency chain (they depend on other libraries or
components more than the other way around) updating application packages shall
take less review effort.

On Fri, Jan 27, 2023 at 2:19 PM Andy Tai  wrote:
>
> Hi, currently Guix has teams of reviewers for different types of
> packages.   For example, changes to R packages and emacs seem to be
> reviewed quickly.  However, recently, patches for updating more
> general application packages (octave, for example) seem to be reviewed
> and processed very slowly.
>
> As a GNU/Linux distribution the update speed of applications impact
> the perception of the community on a distribution, and thus it is
> beneficial if packages update can be processed quickly to keep Guix
> "up to date" so to speak.  Hope Guix maintainers can give some thought
> to this and let more volunteers participate in package review process
> to allow package updates more quickly.   As packages are usually at
> the end of the dependency chain (they depend on other libraries or
> components more than the other way around) updating packages shall
> take less review effort.



-- 
Andy Tai, a...@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat: andytai1010
Year 2023 民國112年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能



Re: Guix QA: trigger rebuild

2023-01-28 Thread Andy Tai
to answer this question: Guix QA can re-start a build if patch with
new version like [PATCH V2] sent tot eh issue email address og debbugs

On Sat, Jan 21, 2023 at 12:30 PM Andy Tai  wrote:
>
> Hi,  if Guix QA shows a patch build is failing and an updated patch
> has been sent, how to trigger the build to be restarted? Thanks for
> info



typo in Guix QA web page

2023-01-29 Thread Andy Tai
For example:

https://qa.guix.gnu.org/issue/61134

Yet to process revivion, job queued

revivion probably is revision



cuirass manual not found

2023-01-29 Thread Andy Tai
on the cuirass web page,

https://guix.gnu.org/cuirass/

the link to the cuirass manual, https://guix.gnu.org/cuirass/manual/,
leads to a 404 not found error



Guix QA issue: "null"patch

2023-02-01 Thread Andy Tai
Hi, I run into a Guix QA issue. Simon encourages me to report Guix QA
issues so I send email here; not sure if there is other channel for
such issues.

In https://qa.guix.gnu.org/issue/61130

I just sent a v2 patch for that Guix issue and Guix QA now shows

"null" for the patch field and it is not clear if it can recognize the
v2 patch and build using that.

Thanks for whoever working on Guix QA to take a look of this problem.



Re: adding motif to guix

2023-02-11 Thread Andy Tai
For these interested, this issue/patch adds emacs using motif to Guix

https://issues.guix.gnu.org/61421

Please review... etc.

On Sun, Jan 8, 2023 at 7:01 PM Eric Brown  wrote:
> My interest in this package is because
> openmotif is the best of the X window managers that do not suffer from
> a rather infamous and longstanding GTK bug which will bring down Emacs.
>



guix git build error

2023-03-07 Thread Andy Tai
Just check out origin/master of guix git HEAD,

make error:

Compiling Scheme modules...
  GEN  etc/openrc/guix-daemon
[  0%] LOAD guix.scm
  GEN  etc/gnu-store.mount
  GEN  etc/guix-daemon.service
  GEN  etc/guix-publish.service
  GEN  etc/guix-gc.service
  GEN  etc/init.d/guix-daemon
./doc/guix-cookbook.fr.texi:652: @pxref reference to nonexistent node `A
Scheme Crash Course'
./doc/guix-cookbook.fr.texi:3370: @ref reference to nonexistent node
`Reproducible profiles'
  GEN  etc/guix-daemon.conf
  GEN  etc/guix-publish.conf
make[2]: *** [Makefile:5300: doc/guix-cookbook.fr.info] Error 1
make[2]: *** Waiting for unfinished jobs
./doc/guix-cookbook.sk.texi:634: @pxref reference to nonexistent node
`A Scheme Crash Course'
./doc/guix-cookbook.sk.texi:3256: @ref reference to nonexistent node
`Reproducible profiles'
./doc/guix-cookbook.ko.texi:624: @pxref reference to nonexistent node
`A Scheme Crash Course'
make[2]: *** [Makefile:5388: doc/guix-cookbook.sk.info] Error 1



This did not happen before (as far as what I have seen)



Re: guix git build error

2023-03-07 Thread Andy Tai
On Tue, Mar 7, 2023 at 10:47 PM Julien Lepiller  wrote:
> I'm afraid I'm unable to reproduce your error. You could try cleaning
> the translated texi files to make sure you get the most up-to-date ones:
>
> rm doc/*.texi
> git checkout doc
> Does that help?


This fixed it. Thanks!



Guix QA: build status "unknown"

2023-03-23 Thread Andy Tai
I don't know if it is just me, but Guix QA recently seems to always
show build status unknown when what really happens was the build
succeeds on both x86-64 and aarch64 but on other platforms it was in
"scheduled" state but the scheduled build never actually got run.   In
any case thanks to the reviewers/committers some of my patches got
reviewed and committed in this state.

It is just the build status is misleading.   If just x86-64 and
aarch64 builds are used to determine if a patch builds successfully
then the badge should reflect such.



patch to fix build failure

2023-05-05 Thread Andy Tai
Hi, just observation on some aspect of current guix packages, as seen
from doing guix package -u

(I know all guix work is done by volunteers, so this is not a
complaint but just reporting on state of things)
after the core-update branch merge to main, there are some build
breakages, not unexpected.

I run into a build failure on python-pyopengl-accelerate which
prevents guix package -u from proceeding.  I posted a patch to upgrade
python-pyopengl to the next version, which is sufficient to fix this
build failure.   The patch is in the issue tracker waiting for Guix QA
to schedule it for build check...

but I don't know if there is a chicken and egg problem, that Guix QA
does not seem to schedule recent patches to the main branch for
builds, and then the committers may not look at the patches which have
not passed Guix QA, so things are not moving. (My observation, sorry
if not accurate description)

Again, thanks for all the people working on Guix, including the people
maintaining Guix QA, highly appreciated.

Just curious if there is any thing that is possible to improve the situation.



Guix QA: 13482 packages waiting for Hurd target to build for a package addition patch

2023-05-11 Thread Andy Tai
funny issue with Guix QA:

https://qa.guix.gnu.org/issue/63184

shows  13482 packages waiting to build for a package addition patch
for target i586-gnu
That shall make no sense.   The package is Linux kernel specific, as well.



ping on a main branch build failure and fix

2023-05-24 Thread Andy Tai
Hi, this bug (a build failure of a package in current main branch)

https://issues.guix.gnu.org/63526

has an attached patch fixing the failure.  Can it be reviewed and
merged if no issue found? Please take a look. Thanks



ping on a build fix for a build failure (main branch)

2023-05-30 Thread Andy Tai
Hi, following previous comments (thanks) I have submitted a patch to
correctly fix a build failure due to compiler warnings, instead of
avoiding not building tests, on this Guix bug issue:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63526

Please review the patch (which shall be a simple and low risk fix).  Thanks!



Re: ping on a build fix for a build failure (main branch)

2023-06-09 Thread Andy Tai
I did contact upstream, no response

On Fri, Jun 9, 2023 at 4:07 AM Andreas Enge  wrote:
>
> Hello Andy,
>
> Am Tue, May 30, 2023 at 10:54:20AM -0700 schrieb Andy Tai:
> > Hi, following previous comments (thanks) I have submitted a patch to
> > correctly fix a build failure due to compiler warnings, instead of
> > avoiding not building tests, on this Guix bug issue:
> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63526
> > Please review the patch (which shall be a simple and low risk fix).  Thanks!
>
> I have reworked a bit the punctuation of the commit message, shortened
> the patch file name and pushed. By this I am closing the two corresponding
> bug reports (it would have been enough to send a second version of the
> patch to the first bug).
>
> Did you contact upstream? Looking at the test, it looked wrong before and
> after your patch...
> if (len < token->data.character.len) {
>hubbub_token t = { 0 };
>t.type = HUBBUB_TOKEN_CHARACTER;
>t.data.character.ptr += len;
>t.data.character.len -= len;
> ...
> Adding to a previously undefined, now 0 pointer .ptr raised a warning
> for a reason, I think; and it looks like the t.data maybe should be
> token->data. But it is quite possible that this branch is not even
> reached by the test.
>
> Andreas
>


-- 
Andy Tai, a...@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat: andytai1010
Year 2023 民國112年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能



"Speeding up Guix with a local caching substitution server"

2023-06-09 Thread Andy Tai
This may be interesting to guix people

https://www.futurile.net/2023/05/01/guix-publish-caching-substitution-server/



package definition question: installation into system directory

2023-06-23 Thread Andy Tai
Hi, I was trying to create a package definition for xrdp.
when testing the package build, its fails at installation step:

libtool: install:
/gnu/store/a5i8avx826brw5grn3n4qv40g514505c-coreutils-9.1/bin/install
-c .libs/xrdp-sesman
/gnu/store/6rfpjdc3vcsfw3yi1cr42g81pd1lw63l-xrdp-0.9.22.1/sbin/xrdp-sesman
 /gnu/store/a5i8avx826brw5grn3n4qv40g514505c-coreutils-9.1/bin/mkdir
-p '/etc/xrdp'
/gnu/store/a5i8avx826brw5grn3n4qv40g514505c-coreutils-9.1/bin/mkdir:
cannot create directory ‘/etc/xrdp’: Permission denied
make[3]: *** [Makefile:690: install-dist_sesmansysconfDATA] Error 1


clearly it was trying to install (some PAM related file) into /etc
which fails.  Curious how should such scenario be handled? Thanks



package definition question: installation into system directory

2023-06-25 Thread Andy Tai
Hi, I was trying to create a package definition for xrdp.
when testing the package build, its fails at installation step:

libtool: install:
/gnu/store/a5i8avx826brw5grn3n4qv40g514505c-coreutils-9.1/bin/install
-c .libs/xrdp-sesman
/gnu/store/6rfpjdc3vcsfw3yi1cr42g81pd1lw63l-xrdp-0.9.22.1/sbin/xrdp-sesman
 /gnu/store/a5i8avx826brw5grn3n4qv40g514505c-coreutils-9.1/bin/mkdir
-p '/etc/xrdp'
/gnu/store/a5i8avx826brw5grn3n4qv40g514505c-coreutils-9.1/bin/mkdir:
cannot create directory ‘/etc/xrdp’: Permission denied
make[3]: *** [Makefile:690: install-dist_sesmansysconfDATA] Error 1


clearly it was trying to install (some PAM related file) into /etc
which fails.  Curious how should such scenario be handled? Thanks



pending mate upgrade patches to 1.26

2023-06-26 Thread Andy Tai
Hi, I submitted patches to update the Mate desktop to 1.26.

The state of them is that there are two prerequisites that have passed
Guix QA check:

https://issues.guix.gnu.org/64001
https://issues.guix.gnu.org/64012

and the mate upgrade patches are in
https://issues.guix.gnu.org/64084

which Guix QA cannot build-check for now because the first two
dependencies are not merged.

These issues are properly marked in debbugs with "block" relationship.

This may not be clear from looking at the patch issues themselves so I
post a message here. Thanks for reviews and git commits if no issues



guidelines for package names (namespaces?)

2023-07-03 Thread Andy Tai
Hi, in Guix there seems no guidelines for package  names/namespaces
although there are conventions like Python packages prefixed with
python-...  (good).  However, this does not cover cases like Gnome
applications. For example, I submitted the original definition for
(the GNOME terminal package) terminator, and later I tried to rename
that gnome-terminator but that was rejected by reviewers.

Or GNU Guix maintainers may want to consider some type of name space
support in the package name space because I think name collisions will
be more and more likely as more packages are submitted for inclusion
in Guix.



Re: A Forum for Guix Users

2023-07-14 Thread Andy Tai
forums are not good because they are not as transparent as mailing
lists--you can search the guix mailing lists with Google, Bing or
whatever search engine you use, for example. Forum? probably not

Maybe an editable (wiki) site for FAQ will be good for sharing common
questions/answers.



openshot patch: Guix QA shows 14000 rebuilds

2023-07-20 Thread Andy Tai
This is a bug report on Guix QA:
I submitted a patch updating Openshot to the latest version.  As
Openshot is an app, it should have few, if any, packages depending on
it.  but Guix QA seems confused and was rebuilding 14000 packages:

https://qa.guix.gnu.org/issue/64722

This is probably a problem for Guix QA and deserves a look. Thanks



Re: pending mate upgrade patches to 1.26

2023-07-24 Thread Andy Tai
Hi, these patches have been merged by Mr. Song (iyzs...@envs.net) . He
worked to get these built without the two extra patches. Thanks

On Mon, Jul 24, 2023 at 12:54 AM Andreas Enge  wrote:

> Hello Andy,
>
> Am Mon, Jun 26, 2023 at 12:09:41PM -0700 schrieb Andy Tai:
> > The state of them is that there are two prerequisites that have passed
> > Guix QA check:
> > https://issues.guix.gnu.org/64001
>
> I had a quick look at this patch, but am a bit confused. If I read it
> correctly, it updates tzdata (which causes a lot of rebuilds, and without
> updating python-pytz as stipulated by a comment in the code of tzdata),
> and then it creates a new variable tzdata-next which looks to be the same.
>
> Would the good approach not be to update tzdata and python-pytz, and to
> copy the old version into tzdata-for-tests?
>
> It is quite possible I am misunderstanding something, and in any case I
> would like to defer to someone more knowledgeable about the core packages.
>
> Andreas
>
>

-- 
Andy Tai, a...@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat:
andytai1010
Year 2023 民國112年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能


conda (python) build failure and patches

2023-07-24 Thread Andy Tai
Hi, conda (of python world) package in Guix is not building on Guix
right now, and there are patches in this bug report to fix that

https://issues.guix.gnu.org/63277

Hope these can get reviewed and merged.

(How these interact with the Python team branch?   Also needs that
team to consider)



poetry: python-poetry?

2023-07-26 Thread Andy Tai
curious poetry is not named python-poetry in Guix as following
convention of most python packages



Re: bug#65391: People need to report failing builds even

2023-08-27 Thread Andy Tai
On 2023-08-27 02:13, 宋文武 wrote:
> Maybe we can automatically report the failures as bugs, say every 7
> days, and remove a package if it still fail to build in 90 days?

Hi, maybe build failures should be limited to certain platforms that
can cause this treatment, such as (32-bit) x86, x86-64 and arm-64, so
build failures on other platforms would not make a package removed if
build failure not fixed

The reason is that most people do not have arm32, PowerPC or Risc-V
hardware so these platforms may be more likely to suffer build
failures and for most people x86 and 64-bit arm platforms are what
they use.  Build failures on the less common platforms can be fixed if
there are people with resources and interests, and wanting to fix them



package definition question: referring to source files of another package?

2023-09-02 Thread Andy Tai
Hi, this is a question for writing package definition.

In some scenarios package A may refer to source files in package B.
The question is,
1. How to reference source directory of package B from within
definition of package A?
2. can we even assume sources of Package B is available?   Normally if
package B is an input (dependency) for package A, guix would ensure
its installation directory is available, but not necessarily the
source.  So is there something that has to be done to ensure Package B
sources are somewhere?

Thanks for info on these.



Re: package definition question: referring to source files of another package?

2023-09-04 Thread Andy Tai
Thanks. this is the pattern that seems to work, posted here for reference:
(define-public tensorflow-lite
  (package
(name "tensorflow-lite")
 ...
(arguments
 `(#:configure-flags

   (list ...
(string-append "-Dgemmlowp_SOURCE_DIR=" (assoc-ref
%build-inputs "gemmlowp-src"))
...

(inputs
 `(
   ("gemmlowp-src"
  ,(package-source gemmlowp))
...

where A is tensorflow-lite and B is gemmlowp

On Sat, Sep 2, 2023 at 9:18 PM Liliana Marie Prikler
 wrote:
> Am Samstag, dem 02.09.2023 um 20:35 -0700 schrieb Andy Tai:
> > In some scenarios package A may refer to source files in package B.
> > The question is,
> > 1. How to reference source directory of package B from within
> > definition of package A?
> You can use (package-source B) both within source and inputs.  The only
> caveat here is that A and B should best be located in the same file;
> things break badly if they are split and introduce cyclic references.
> Note that the and part is more likely than you think, since the thunked
> nature of inputs normally makes them harmless.
>
> Cheers



Re: Replacing Mumi+Debbugs?

2023-09-05 Thread Andy Tai
FSF IT seems to have an instance of sourcehut running

sourcehut.gnu.org

or they are working on it.

Maxim Cournoyer  writes:
> I'd be sad to loose at least two good things from Debbugs:
>
> 1. It's hosted by the GNU/FSF for us.  It always work, and the rare
> times it doesn't, the folks in #savannah are hard at work resolving the
> problems. While hosting sourcehut is probably not too difficult, keeping
> it up to date (Go...) and running would be yet another weigh on our
> meager sysadmin team.



guix build from git failure: missing sections in German, French, etc. doc translations?

2023-09-08 Thread Andy Tai
Checking out the latest origin/master head, building guix fails:

make[2]: Entering directory '/share/software/guix/guix.git/po/packages'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/share/software/guix/guix.git/po/packages'
make[2]: Entering directory '/share/software/guix/guix.git'
  MAKEINFO doc/guix.info
  MAKEINFO doc/guix.de.info
  MAKEINFO doc/guix.fr.info
  MAKEINFO doc/guix.es.info
  MAKEINFO doc/guix.pt_BR.info
contributing.pt_BR.texi:1338: @menu reference to nonexistent node
`Configuring Git'
contributing.pt_BR.texi:1339: @menu reference to nonexistent node
`Sending a Patch Series'
contributing.de.texi:1447: @menu reference to nonexistent node `Configuring Git'
contributing.de.texi:1448: @menu reference to nonexistent node
`Sending a Patch Series'
contributing.fr.texi:1389: @menu reference to nonexistent node `Configuring Git'
contributing.fr.texi:1390: @menu reference to nonexistent node
`Sending a Patch Series'
make[2]: *** [Makefile:4969: doc/guix.de.info] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: *** [Makefile:5099: doc/guix.fr.info] Error 1
make[2]: *** [Makefile:5164: doc/guix.pt_BR.info] Error 1


the script I used to build guix from git is attached


guix_git_build.sh
Description: application/shellscript


guix QA "fails to process revision"

2023-09-19 Thread Andy Tai
For a submitted patch, if Guix QA "fails to process revision" as in this log
https://data.qa.guix.gnu.org/job/49399

[ 32/ 40] compiling... 60.0% of 20 filesmadvise failed: Cannot allocate memory
builder for `/gnu/store/j3hy5gymlfrdrhm8aj2brnsa2pix16n2-guix-home.drv'
failed due to signal 11 (Segmentation fault)
@ build-failed /gnu/store/j3hy5gymlfrdrhm8aj2brnsa2pix16n2-guix-home.drv
- 1 builder for
`/gnu/store/j3hy5gymlfrdrhm8aj2brnsa2pix16n2-guix-home.drv' failed due
to signal 11 (Segmentation fault)
cannot build derivation
`/gnu/store/yh45c2z642xv2m752i3mj4lahj7q4qxm-guix-cli.drv': 1
dependencies couldn't be built
...

what can be done about it?



Re: The e(macs)lephant in the room and the Guix Bang

2023-09-20 Thread Andy Tai
Hi, for some reason emacs has become the elephant in the room of the
discussion on contributing to guix.

Regardless of one's opinion of emacs, I just want to add that this is
itself strange.  I have contributed some (package definition) patches
to guix, all without using emacs.

I am not an emacs user, so emacs is not necessary for contributing to guix.
For what it's worth, the emacs-motif package in Guix was my addition.
I don't use it myself.



"Parameterized Packages: The Project Completion Update"

2023-09-20 Thread Andy Tai
Not seen mentioned on this mailing list  yet, so probably of interest:
GSOC project's final report:
https://blog.lispy.tech/parameterized-packages-the-project-completion-update.html



guix QA "fails to process revision"

2023-09-20 Thread Andy Tai
For a submitted patch, if Guix QA "fails to process revision" as in this log
https://data.qa.guix.gnu.org/job/49399

[ 32/ 40] compiling... 60.0% of 20 filesmadvise failed: Cannot allocate memory
builder for `/gnu/store/j3hy5gymlfrdrhm8aj2brnsa2pix16n2-guix-home.drv'
failed due to signal 11 (Segmentation fault)
@ build-failed /gnu/store/j3hy5gymlfrdrhm8aj2brnsa2pix16n2-guix-home.drv
- 1 builder for
`/gnu/store/j3hy5gymlfrdrhm8aj2brnsa2pix16n2-guix-home.drv' failed due
to signal 11 (Segmentation fault)
cannot build derivation
`/gnu/store/yh45c2z642xv2m752i3mj4lahj7q4qxm-guix-cli.drv': 1
dependencies couldn't be built
...

what can be done about it?



is core-updates still a thing?

2023-09-24 Thread Andy Tai
Hi, curious if core-updates still a thing?There seems a branch by
that name and the manual still says patches causing large number of
rebuilds should go to core-updates, at least for these not aiming at a
specific feature branch.



bootstrapping scenario for a package

2021-12-20 Thread Andy Tai
Hi, I was trying to update mono to the current release version.  The
build step as documented actually says to download a minimal C#
compiler from the mono site which is then used to compile the rest of
the source to build the full system.   I looked and did not find the
source of this minimal compiler--so it is a black box in a way.

In free software it is ideal to build everything from source.   I
wonder how is such a package handled in Guix?   What is the strategy
for bootstrapping?   Thanks


(msg sent to help-guix first but this list may be more appropriate)



"Guix Makes Bitcoin Core Development More Trustless"

2022-03-09 Thread Andy Tai
may be of interest to people here...
https://bitcoinmagazine.com/technical/guix-makes-bitcoin-core-development-trustless



Re: "Parameterized Packages: The Project Completion Update"

2023-10-02 Thread Andy Tai
no, not  my effort.  I just pointed out that report.  credit to the
real author Sarthak Shah

On Mon, Oct 2, 2023 at 1:13 PM Munyoki Kilyungi  wrote:
>
> Andy Tai  aliandika:
>
> > Not seen mentioned on this mailing list  yet, so probably of interest:
> > GSOC project's final report:
> > https://blog.lispy.tech/parameterized-packages-the-project-completion-update.html
> >
>
> Thanks for the effort!



Guix QA "Unable to apply patches"

2023-10-06 Thread Andy Tai
Hi, for one of my package patches, Guix QA shows

"Unable to apply patches"

in https://qa.guix.gnu.org/issue/63095

even though I double checked the patch applies cleanly on the current
head of the master branch.

Guix QA shows no hint as what the failure is (no log, etc.)   Curious
how to investigate the problem?



Re: Guix-devel Digest, Vol 124, Issue 28

2023-10-12 Thread Andy Tai
Chris, what would you suggest the best way to increase visibility of
revisions or recent patches to "old" issues in Debbugs so they can get
covered by Guix QA?

On Wed, Oct 11, 2023 at 9:01 AM  wrote:
> Date: Tue, 10 Oct 2023 18:02:43 +0100
> From: Christopher Baines 
> To: Andy Tai 
> Subject: Re: Guix QA "Unable to apply patches"
>
> Andy Tai  writes:
> > Hi, for one of my package patches, Guix QA shows
> > "Unable to apply patches"
> > in https://qa.guix.gnu.org/issue/63095
> The reason why QA hasn't looked at this issue is that it's too old. To
> avoid resource problems, QA only currently looks at a fixed number of
> recent issues. The limiting factor is currently data service storage
> space.
>
> Unfortunately none of that is very helpful in getting this patch looked
> at though.



How to send revision patches to old issues in DEBBUGS so Guix QA can look at them?

2023-10-14 Thread Andy Tai
Hi, per Chris's recent comments, Guix QA only looks at (a window of)
recently created issues due to storage space limitations, which is
understandable.

However, if I have update (package definition) patches to not very
recent issues, such as some stale issues sitting there for some time,
Guix QA does not pick these revisions up.  Then these revisions will
not be reviewed and would not be merged.

Ideally, Guix QA should look at recent patch submissions to the
guix-patches mailing list but not sure if that is easy to implement.

Then what is the best way to make recent patches to old issues covered
by Guix QA?  I tried to create new issues and then merge old issues
into the new ones but that is probably not a good way to go or good
thing to do.



Re: How to send revision patches to old issues in DEBBUGS so Guix QA can look at them?

2023-10-16 Thread Andy Tai
Maxim, I know about this.  Problem is Guix QA does not look at old issues

On Mon, Oct 16, 2023 at 8:36 AM Maxim Cournoyer
 wrote:
>
> Hi Andy,
>
> Andy Tai  writes:
>
> > Hi, per Chris's recent comments, Guix QA only looks at (a window of)
> > recently created issues due to storage space limitations, which is
> > understandable.
> >
> > However, if I have update (package definition) patches to not very
> > recent issues, such as some stale issues sitting there for some time,
> > Guix QA does not pick these revisions up.  Then these revisions will
> > not be reviewed and would not be merged.
> >
> > Ideally, Guix QA should look at recent patch submissions to the
> > guix-patches mailing list but not sure if that is easy to implement.
>
> After rebasing the old series locally, you can send it to the *same bug
> ID* with a bumped version (e.g. git send-email -v2
> ... --to=nn...@debbugs.gnu.org).
>



core-updates?

2023-11-20 Thread Andy Tai
Hi, I hope core-updates is the mean for some patches to get merged; I
have a two-line addition patch that may cause rebuilds of 10K packages
but I would think asking for a feature branch for such a patch is
overkill.  so I sent it to target core-updates and hope this can be a
quicker way for it to get in.



"random check" approach to Guix QA?

2023-11-20 Thread Andy Tai
Hi, currently Guix QA tries to rebuild all dependent packages impacted
by a change (in majority of cases updates to a new version of a
package).  When there are a large number of dependent packages like
say 500 or 1000 or more, rebuilding all that takes a long time and
often the rebuild cannot complete, leaving the patch submission
dangling with no results.

For some things where safety is important, for example import food
safety, the regulatory authority may use random check or random
sampling as a way to check for safety, in case that there is no
resource to physically check every package.

Can the same approach be borrowed here, so when there is large number
of impacted packages from a patch, say larger than 200, Guix QA just
randomly select a subset sample out of these packages and build them,
and in case of (new) failures ask the submitter to fix the (new)
failure? And repeat this as needed.   This way patches can go thru the
QA process more quickly.



role of core-updates

2023-11-26 Thread Andy Tai
Hi, hope Guix maintainers can clarify the role of the now core-updates
branch; the current documentation does not specify the core-updates
branch as a thing but there are clearly interests and uses of this
branch for package updates not belonging to a feature branch like
gnome and it is useful for, say, updating to the GNU make package
which would have caused world rebuild.  Thanks



issues.guix.gnu.org seems stop updating

2023-12-08 Thread Andy Tai
https://issues.guix.gnu.org/recent, for example, only shows issues up to Dec 6.

Not sure if this is due to some data services stopping running or such...



Western US mirroring?

2023-12-09 Thread Andy Tai
Hi, just an idea:

The GNU Guix project currently has a substitution server mirror in the
East coast of the US.

No mirror in the Western US.

The OSU Open Source Lib (https://osuosl.org/) offers hosting resources
to FOSS projects...
https://osuosl.org/services/

Maybe the GNU Guix project can request hosting service from them, to
have a substitution mirror, for example, so more resources can be
available for downloading of artifacts for Guix users...

Maybe this can be expanded later to have more services for Guix and
other GNU projects in the West coast of the US, in cooperation with
the FSF IT?

Wonder if the idea is OK.



Re: Western US mirroring?

2023-12-11 Thread Andy Tai
Hi, if the GNU Guix project agrees I can try to get the ball rolling
by applying, but I need OK from Guix maintainers so this can be an
request on the behalf of the Guix project.  Or the Guix maintainers
can go ahead and do it.  Let me know.

On Sat, Dec 9, 2023 at 11:18 PM Julien Lepiller  wrote:
>
> Sounds like a great idea!
>
> Le 10 décembre 2023 02:19:16 GMT+01:00, Andy Tai  a écrit :
> >The GNU Guix project currently has a substitution server mirror in the
> >East coast of the US.
> >
> >No mirror in the Western US.
> >
> >The OSU Open Source Lib (https://osuosl.org/) offers hosting resources
> >to FOSS projects...
> >https://osuosl.org/services/
>



Re: Western US mirroring?

2023-12-11 Thread Andy Tai
Hi, if so you would be the best person for it. if guix maintainers authorize.

On Mon, Dec 11, 2023 at 10:01 AM Tobias Geerinckx-Rice  wrote:
>
> [+CC the -maintainers alias for good measure]
>
> I can't speak for the collective but enthousiastic +1 from me.
>
> OSU should already have me on file as representing Guix (for the POWER9 VM) 
> so let me know if I can expedite anything.
>
> Kind regards,
>
> T G-R
>
> Sent on the go.  Excuse or enjoy my brevity.



-- 
Andy Tai, a...@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat: andytai1010
Year 2023 民國112年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能



Re: Western US mirroring?

2023-12-11 Thread Andy Tai
Fine. I can take this.

On Mon, Dec 11, 2023 at 10:40 AM Tobias Geerinckx-Rice  wrote:
>
> I'm happy to assist but not currently available to be volunteered into 
> leading the effort, sorry.
>
> Kind regards,
>
> T G-R
>
> Sent on the go.  Excuse or enjoy my brevity.



status of (future of) Guix QA

2023-12-22 Thread Andy Tai
Curious of the status of the future of Guix QA as package definition
contributors rely on it for updating packages (sending patches to get
accepted/committed) in guix...



Re: Guix Days: Patch flow discussion

2024-02-05 Thread Andy Tai
Hi, this is a sugestion on guix patches:

Other GNU/Linux distributions often have fixed maintainers (or
packagers) for specific packages.
While that model may not apply directly to the Guix project as anyone
can send in patches for anything in the git repo, maybe one thing the
Guix project can do is to recognize if someone has sent in patches for
specific projects many times in the past, then that means the person
has knowledge, interest, familiarity and expertise about this package
and the reviewers can spend minimal time of his/her future patches for
the same package(s).

Thus this creates kind of pseudo package maintainer in Guix, reducing
workload of reviewers and speeding up package update.

Guix can have a text file in the Guix repo recording say someone who
is "responsible" or is a "pseudo packager" for specific packages,
which the committers can refer to to allow quick processing of
patches.  This does not mean the person responsible for certain
package has git commit access but just to allow a quick path for patch
processing by the commiters of certain patches from the familiar
person.

Of course others can still send in patches for these packages already
with pseudo packagers.



Re: Guix Days: Patch flow discussion

2024-02-05 Thread Andy Tai
What I proposed is in terms of the scope of a single package. The
teams cover much larger and broader scope, like Gnome or Python.

On Mon, Feb 5, 2024 at 12:50 PM Clément Lassieur  wrote:
> On Mon, Feb 05 2024, Andy Tai wrote:
> > Thus this creates kind of pseudo package maintainer in Guix, reducing
> > workload of reviewers and speeding up package update.
> We have exactly this:
> https://git.savannah.gnu.org/cgit/guix.git/tree/etc/teams.scm
>
> And it's even better: those people automatically receive an email if you
> use git-send-email to send a patch about their associated files.



setting up a channel for pending package update patches

2024-03-02 Thread Andy Tai
Hi, curious if anyone has done such a task: setting up a channel for
the pending patches for package definitions.

Since pending patches for package updates take long time to process
and merge. I wonder if anyone has set up a channel that contains the
patches applied on top of the Guix git repo so such a channel would
bring the pending changes to end users who use this channel before the
official Guix git repo is updated (applying the package definition
patches).

This is not about a permanent fork of the Guix repo or a special
channel like guix games for some specific types of packages like say
games.

Better yet, if anyone has set up a substitution server for this update
channel, info on that would be even better.

This is assuming some risks, such as update patches may have errors,
that may break things

Curious if anyone's experience in doing this, any issues running such
setup, etc.



Flox: Nix-based portable virtual environments

2024-03-15 Thread Andy Tai
reference: https://lwn.net/Articles/965584/ "Mitchell: Today we
launched Flox 1.0"

Is this just something a guix pack already is equivalent to, on top of
the stock GNU/Linux container? Or Flox may have some additional
feature that a Guix equivalent can be useful?



David Wilson to keynote LibrePlanet (FSF Conference), to start soon

2024-05-04 Thread Andy Tai
>From FSf's web sote:

"The Neptune Room is 100% remote this year and can be viewed through
our Galène instance at https://galene.fsf.org. Enter a username of
your choice and any password will do. "



Re: Third-parties are back to upstream

2024-05-05 Thread Andy Tai
Hi, do you mean the changes will take place in next release (not the
current release 0.6)?   This is not apparent from the context. Thanks
for clarification

On Sat, May 4, 2024 at 9:01 AM  wrote:
>
> Message: 1
> Date: Sat, 04 May 2024 13:00:22 +0900
> From: Nala Ginrut 
> To: "arta...@gnu.org" 
> Hi folks!
> I've removed intergrated guile-redis & guile-json in Artanis, and tweaked the
> interfaces, so folks may install their prefered version from upstream.
>
> Artanis become more lightweight now.
> And this will also alleviate the pain of the packagers.
>
> The CI tests are passed.
> https://gitlab.com/hardenedlinux/artanis/-/pipelines/1278224717
>
> The default tested versions in CI are:
> guile-json-4.7.3
> guile-redis-2.2.0
>
> Tests and comments are welcome!
>
> Best regards.



Re: Third-parties are back to upstream

2024-05-10 Thread Andy Tai
Because Guix has no concept of package maintainers and anyone can send
a patch to update a package, please make sure after the next release
you check the pending patches for your package to do what you
suggested regrading the 3rd party directory and retaining the two .scm
files.  If I send the updated patch I will try to do what you
suggested.  Please do check then.

On Sun, May 5, 2024 at 8:18 PM Nala Ginrut  wrote:
>
>
> Hi Tai!
> It should be in the next release, but it's already in the vanilla code.
> In case anyone try to test the develop branch with Guix.
>
> Best regards.
>
>
> > On Sat, May 4, 2024 at 9:01 AM  wrote:
> >>
> >> Message: 1
> >> Date: Sat, 04 May 2024 13:00:22 +0900
> >> From: Nala Ginrut 
> >> To: "arta...@gnu.org" 
> >> Hi folks!
> >> I've removed intergrated guile-redis & guile-json in Artanis, and tweaked 
> >> the
> >> interfaces, so folks may install their prefered version from upstream.
> >>
> >> Artanis become more lightweight now.
> >> And this will also alleviate the pain of the packagers.



Guix QA "An error occurred"

2024-06-03 Thread Andy Tai
currently if I click on the QA button of the issues UI for Guix the QA
page would show

An error occurred

Sorry about that!

wrong-type-arg



package submission, unit test failures on Guix QA... policies?

2024-06-07 Thread Andy Tai
Hi, I have a patch submission that builds fine (in the GNU Guix sense,
that is, unit tests run and pass) locally but fails on Guix QA due to
unit tests failing.

I suspect that the failures are due to the build machine (or machines)
as plain x86-64 PC (fine as build server(s)) does not have exotic
hardware units like GPU that the package in question is meant to use.

This may become more common as GPU and NPU applications become more popular.

Curious how shall such cases be handled?  Maybe reviewers can build
and run the patch to verify the patch works, so the Guix QA failure
can be overridden?



same package name for unrelated packages

2024-06-16 Thread Andy Tai
in GNU Guix today:

$ guix show volk
name: volk
version: 3.0.0
outputs:
+ out: everything
systems: x86_64-linux i686-linux
dependencies: boost@1.80.0 python-mako@1.2.2 python-wrapper@3.10.7
location: gnu/packages/engineering.scm:1381:2
homepage: https://www.libvolk.org/
license: ASL 2.0, LGPL 3+
synopsis: Vector-Optimized Library of Kernels
description: VOLK (Vector-Optimized Library of Kernels) contains procedures with
+ machine-specific optimizations for mathematical functions.  It also provides a
+ machine-independent interface to select the best such procedures to
use on a given system.

name: volk
version: 1.3.280.0
outputs:
+ out: everything
systems: x86_64-linux i686-linux
dependencies: vulkan-headers@1.3.280.0
location: gnu/packages/vulkan.scm:565:2
homepage: https://github.com/zeux/volk
license: Expat
synopsis: Meta loader for Vulkan API
description: Volk is a meta-loader for Vulkan.  It allows you to
dynamically load entrypoints
+ required to use Vulkan without linking the Vulkan loader.
Additionally, volk simplifies the
+ use of Vulkan extensions by automatically loading all associated
entrypoints.  Finally, volk
+ enables loading Vulkan entrypoints directly from the driver which
can increase performance by
+ skipping loader dispatch overhead.


One would assume this can break things



issues.guix.gnu.org certificate expired

2024-06-16 Thread Andy Tai
trying to connect to is using Firefox, Firefox says:


Did Not Connect: Potential Security Issue

Firefox detected an issue and did not continue to issues.guix.gnu.org.
The website is either misconfigured or your computer clock is set to
the wrong time.

It’s likely the website’s certificate is expired, which prevents
Firefox from connecting securely.

The issue is most likely with the website, and there is nothing you
can do to resolve it. You can notify the website’s administrator about
the problem.



Re: Next Steps For the Software Heritage Problem

2024-06-18 Thread Andy Tai
What is the role of GNU Guix in this? If Guix is mainly a referral
mechanism like web page links to the actual contents, the real problem
is not Guix but the use of free software which can be obtained  via
other mechanisms directly anyway to train LLMs if Guix is not in the
loop?



Re: Next Steps For the Software Heritage Problem (Dale Mellor)

2024-06-20 Thread Andy Tai
> Date: Wed, 19 Jun 2024 09:36:29 +0100
> From: Dale Mellor 
> I use Guix as a tool to develop my own projects, private and
> personal for reasons I'm keeping to myself.  As part of that I write package
> definitions for them, and use the Guix machinery to build and test.  I 
> *cannot*
> have Guix just giving my code away to anybody, that is just fundamentally 
> wrong.
>
If you release software as free software, you are giving away
software, to anybody and everybody.

>   We need to ask what is Guix?  A free operating system, a framework for
> developing free operating systems, or a more generic tool for software
> development and deployment?  If the latter it *cannot* do nefarious things
> without explicit consent.

Guix is a free operating system _and_ a generic tool for software
development and deployment.   It makes no sense to say it does nefarious things
without explicit consent.  Just like you cannot try to prohibit GNU
Make from being  used to do nefarious things like building malware.
You cannot place usage restriction on free software.

>
>   I think at least there should be a /restricted/ license type available to
> package definitions, and the system absolutely should not give source code 
> away
> from packages which use this (of course, they won't get into the official
> distribution, but that's fine).
>
How can you restrict others from posting links to your content, as
what essentially package definitions in Guix are.

>   More broadly, I think they should just stop inter-operating with SH.  Just
> walk away.
>
> Dale



update Mate Desktop to 1.28

2024-07-04 Thread Andy Tai
Hi, in this patch series
https://issues.guix.gnu.org/71781

I sent would upgrade Mate to 1.28.  Hope someone with commit access
can review the patch series.  Keep desktop environments up to date is
good for GNU Guix.



packaging: what to do about these requiring systemd?

2024-07-07 Thread Andy Tai
Some packages require systemd; some may provide configure stage
options to disable systemd support which can be supplied by the
package definitions in Guix.  But for these that do not make systemd
support configurable, what is the general approach to make such
packages available in GNU Guix?



Re: packaging: what to do about these requiring systemd?

2024-07-08 Thread Andy Tai
There are now cases of packages linking to Systemd, not just checking
for installing init scripts.
should these be considered bugs of such packages (and we shall ask the
package authors to make systemd optional)?

On Mon, Jul 8, 2024 at 4:45 AM Ricardo Wurmus  wrote:
>
> Andy Tai  writes:
>
> > Some packages require systemd;
>
> Some of these packages are perfectly happy with elogind.  Others only
> check to decide what files to install (systemd unit files or those for
> another init system).
>
> --
> Ricardo



-- 
Andy Tai, a...@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat: andytai1010
Year 2024 民國113年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能



Re: Request for assistance maintaining LibreWolf

2024-08-17 Thread Andy Tai
I wonder how scalable this approach is, if many "package maintainers"
each have their own channel for the packages they are maintaining, and
made available this way.   I would guess to use this approach the Guix
users have to do "guix package -u --allow-collision"

> Date: Sat, 17 Aug 2024 12:43:11 -0700
> From: Ian Eure 
> Whatever the state of Guix proper, you can always find the current
> version of LibreWolf in my personal channel[1], though I don’t
> have a public substitute server, so long build times will await
> you if you choose this route.



fix for Tensorflow Lite build

2024-08-30 Thread Andy Tai
Hi, in this bug-guix issue
https://issues.guix.gnu.org/72747

I sent patch to fix the Tensorflow Lite build.  Guix QA seems not able
to pick up patch in bug-guix issues (unlike guix-patches issues)

So please committers, please review the patch and merge as the build
for package is broken.  Thanks

(not sure what else to do to call attention to patch in bug reports
other than bothering guix-devel)



core-update scope

2024-08-31 Thread Andy Tai
Hi, shall changes to non-core packages like ffmpeg still be in the
scope of core-updates?

ffmpeg, for example, is no where near the core of the GNU system like
glibc, but still it is widely dependent upon.   But it would make no
sense to have a ffmpeg-team because it is used by packages over wide
areas, KDE, GNOME and others.   It is not well defined in a package
realm like GNOME packages.

The last core-update branch was used to update ffmpeg.  This seems to
still better to be true or to remain the same, no?



upgrade to new version of packages with lots of dependencies--installing new versions along first?

2024-09-06 Thread Andy Tai
Hi, this is nothing new and clearly has been the case for a number of
packages in Guix.

For packages that have not of dependencies (say 300 or more) updating
to new versions have been increasingly difficult, as lots of rebuilds
needed and Guix QA is really overwhelmed  (it seems).

For other reasons like API compatibility some such packages exist in a
state of multiple versions, with old versions sticking around to
satisfy other packages depending on them. Example: samba and
samba-next

Maybe this can be generalized for packages with lots of dependencies,
say for any package A with 300 (or 1000) dependencies, when upgrading
to a new version, add that as A-next so existing A is not touched.
Then A-next can be added without any dependencies, and Guix QA just
needs to check if A-next builds.   Then people working on any package
depending on A can move that package to depending on A-next later
independently.   This avoid triggering world rebuilds.  And A's
dependents migrate at their own flow.

Or a feature branch can still be used for these migrating dependencies
but A-next can be added to master first and made available, without
waiting for a feature branch to be merged

Is this workable idea?



Re: Guix (and Guile's) promise, and how to (hopefully) get there

2024-10-26 Thread Andy Tai
With due respect, I disagree with that.

Guix recent years has seen growing interests and contributions, so
many patches that the they are not reviewed or processed in a timely
manner.   This is with affiliation with GNU.  I contributed to Guix
because it is GNU.

In fact I just contact the FSF about contribution to Guix with small
donations periodically. I am in the US and financially contribution to
the FSF is tax deductible and the FSF has a better track record of
efficient use of contributions than most other non profits (as
regulated by the US Government Internal Revenue Service).  Financially
many free software nonproifts are having issues (per recent article in
lwn.net) and the FSF is in better shape than these (with questions on
their abilities to raise income and expenses) in that article.  So it
is not clear where the FSF lost its financial capital.

So my observation is inconsistent with what Juliana wrote in this part.

On Sat, Oct 26, 2024 Juliana Sims wrote:
>
> ...Guix should break with GNU and the FSF. Moreso the FSF, but the two
> are irrevocably intertwined in the public conscious -- which is the
> primary reason Guix needs to break away. To avoid relitigating what has
> been litigated more than sufficiently already, the FSF made a bad
> political move that has destroyed its social capital and, as a
> side-effect, its financial capital as well. Even if it can help us with
> funding, it shouldn't.
>
> I think so. As I noted above, if we break with GNU, I am highly
> confident we will see an uptick in new contributors, at least some of
> whom can help there.



status of guixrus

2024-09-27 Thread Andy Tai
Hi, guixrus (https://lists.sr.ht/~whereiseveryone/guixrus) was
intended as a place where package definitions updates can be quicker
while patches are waiting in review for the guix git.  Curious if that
is still the intended for this purpose (no such activities recently)?

another comment related to it: its web site https://whereis.みんな/
seems to use Japanese characters (?)  If possible can a site name in
ASCII be provided as well as those Japanese characters sometimes
confuse clients. Thanks



Re: Third-parties are back to upstream

2024-12-02 Thread Andy Tai
OK I guess I will need to update my patch for this.

On Mon, Dec 2, 2024 at 1:02 AM Nala Ginrut  wrote:
> Hi Andy Tai and Guix folks!
> Recently Artanis-1.0.0 has released, I think there's still a thing to
> notice for Aarch64.
> You may need to pass --build=aarch64-unknown-linux-gnu to ./configure
> for Aarch64.
> Here's the related link:
> https://gitlab.com/hardenedlinux/artanis/-/issues/115#note_2054372084