Hello again,
On Sat, 31 Aug 2024 01:45:04 +0200
Ekaitz Zarraga wrote:
> Hi Jan,
>
>
> First, there are tags in the issue system:
>
> https://issues.guix.gnu.org/search?query=tag%3Aeasy
>
Missed this completely. Where is this documented?
>
> The issue of friendliness has been brought up in
> I'm apparently smart enough to install Guix as my daily driver distro,
> learn Emacs with Paredit and hack together packages, and then an
> email-based system filters me out...
i often feel that getting some of my (non-controversial) contributions merged
is an equivalent effort compared to cre
On Sat, 31 Aug 2024 15:05:58 +0200
Ekaitz Zarraga wrote:
> Hi,
>
> On 2024-08-31 14:05, Jan Wielkiewicz wrote:
> > Hello again,
> >
> > On Sat, 31 Aug 2024 01:45:04 +0200
> > Ekaitz Zarraga wrote:
> >
> >> Hi Jan,
> >>
> >>
> >> First, there are tags in the issue system:
> >>
> >> https://iss
Hi,
Congratulations to everyone. Great job.
I would like to (may I ?) suggest libusb v1.0.27 to be added to the list of
packages for the new core-updates team.
I know that this might be a quite large effort (3000+ will be rebuilt) but
I'm happy to help testing and maybe bug fixing simple problem
Hi
On 2024-08-31 15:44, Jan Wielkiewicz wrote:
I apologize for my emotional and not constructive reply at first, I'll
try making more constructive replies next time.
No, don't worry about it. It is a normal reaction and I'm glad you
started there because we were able to create something from
Hi again!
Over the years, consensus emerged that ‘core-updates’, as a branch where
we lump together all sorts of rebuild-the-world changes, is no longer
sustainable. Those of us who were at the Guix Days in February 2023
came to the conclusion that (correct me if I’m wrong) we should keep
branche
Jan Wielkiewicz writes:
> The issue that needs to be addressed however is the documentation, this
> page to be precise:
> https://guix.gnu.org/en/manual/devel/en/html_node/Sending-a-Patch-Series.html
> I propose turning it into numbered list of things a contributors needs
> to do in order to suc
Hello Guix!
I rebased and applied ‘core-updates’ on top of ‘master’ minutes ago with
commit b8327cb31199fb9f4ebed6c53a59601d41def5a1! 🎉
Consider contributing translations of the news entry added in that
commit.
Let’s congratulate everyone involved in this branch for more than a year (⁈)
for the
Ludovic Courtès writes:
Hi!
> Hello Guix!
>
> I rebased and applied ‘core-updates’ on top of ‘master’ minutes ago with
> commit b8327cb31199fb9f4ebed6c53a59601d41def5a1! 🎉
>
> Consider contributing translations of the news entry added in that
> commit.
>
> Let’s congratulate everyone involved in
Hi,
On 2024-08-31 14:05, Jan Wielkiewicz wrote:
Hello again,
On Sat, 31 Aug 2024 01:45:04 +0200
Ekaitz Zarraga wrote:
Hi Jan,
First, there are tags in the issue system:
https://issues.guix.gnu.org/search?query=tag%3Aeasy
Missed this completely. Where is this documented?
In the bottom
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
Hi Guix!
Congratulations to everyone who worked on the core-updates merge!
A lot of things have changed though, and I was curious about this new
message I've been getting whenever I invoke `guix`.
hint: Consider installing the `glibc-locales' package and defining
`GUIX_LOCPATH', along these
12 matches
Mail list logo
