Hello, we have a TODO for "extend `propagated-inputs` with support for
multiple outputs". I try to do it for a while, but unable to find a
clear way, since add a new syntax for specify output in
propagated-inputs require changes in too many places..
Think about the intention, what we want is to a
Am Fri, Aug 25, 2023 at 03:56:56PM +0100 schrieb (:
> Zhu Zihao writes:
> > and AFIAK, Maxime Devos is working on new build system called
> > "Antioxidant", which can build rust application without cargo (Yes,
> > invoke rustc directly!), The new build system will cache the rlib
> > intermediate r
Am Freitag, dem 25.08.2023 um 08:07 + schrieb Attila Lendvai:
> i couldn't even find out which tools are used by those who are
> comfortable with the email based workflow. i looked around once, even
> in the manual, but maybe i should look again.
Users who have tried curlbash also looked at
w
On 2023-08-24 08:33, ( wrote:
Katherine Cox-Buday writes:
I can't ever seem to get the GNU style commit messages correct. I
use the
templates provided, but those don't cover all cases, and I've even
gotten
feedback in a review to change a message it created.
You do get used to
On 2023-08-25 11:31, Attila Lendvai wrote:
I feel like the advantages of a email-based workflow nowadays is more
on
the maintainer side of things (as managing large projects is easier
another thing worth pointing out here is that the harder it is to test
a submitted patchset locally, the few
Hi kiasoc5, hi Attila
Am Samstag, dem 26.08.2023 um 19:42 +0200 schrieb kias...@disroot.org:
> On 2023-08-25 11:31, Attila Lendvai wrote:
> > > I feel like the advantages of a email-based workflow nowadays is
> > > more on the maintainer side of things (as managing large projects
> > > is easier
>
Hi John,
John Kehayias writes:
> Hi Maxim,
>
> On Sun, Jul 30, 2023 at 09:50 PM, Maxim Cournoyer wrote:
>
>> Hi John,
>>
>> John Kehayias writes:
>>
>> [...]
>>
>>> I'll open a branch merge request issue later today as per new
>>> procedure for QA. Though I believe that only builds 2 branches,
> > > straight out forgotten/ignored submissions (khm). especially if
> > > it's about some hw or some sw that none of the committers care
> > > about, or could test locally (e.g. Trezor support:
> > > https://issues.guix.gnu.org/65037 that
> > > doesn't even build in master).
>
> Do you mean t
Maxime Devos writes:
> For example, naev used to work just fine, yet apparently it doesn't
> anymore: https://issues.guix.gnu.org/65390.
>
> Given that Guix has ci.guix.gnu.org, I would expect such new problems
> to be detected and resolved early, and it was detected by
> ci.guix.gnu.org, yet goi
Hi,
Csepp writes:
> The docs contain this recommended Emacs setting:
>
> @lisp
> ;; @r{Assuming the Guix checkout is in ~/src/guix.}
> (with-eval-after-load 'geiser-guile
> (add-to-list 'geiser-guile-load-path "~/src/guix"))
> @end lisp
>
> I haven't been using it for a while because I remembe
Hi Simon,
Simon Tournier writes:
> Hi,
>
> The bug tracker – or guix-devel and/or help-guix – reports several
> similar issues: “guix pull” fails and then run it again (or again and
> again and …) makes it pass. Well, part of the collection:
>
> https://issues.guix.gnu.org/issue/62830
> https:/
Hi,
Csepp writes:
[...]
> but as soon as something breaks, you are thrown into the deep end,
> having to dissect logs, bisect commit ranges, learn strace, gdb (which
> still doesn't work well on Guix)
Hm? Why GDB on Guix may be sometimes more challenging than say, on
Fedora, I only know of on
Hi,
Katherine Cox-Buday writes:
[...]
>> By the way, that's another issue. Using a TeX based document format for
>> the docs is, uuuh, maybe not the best idea. Info is a pretty okayish
>> documentation reader, but it's a relatively big barrier to entry
>> compared to what you need to know to
Hi Guix,
I would like to merge 62153. After 64173 will be merge, merging 62153
is not possible without conflict resolving with Git.
64173 introduces ‘%docker-format-options’ variable. With this variable
it's possible in 62153 to replace ‘--image-type=docker-layered’ with
‘--docker-layers=N’ opt
Hi Katherine,
Katherine Cox-Buday writes:
> On 8/24/23 12:33 AM, ( wrote:
>
>>> * We could support a managed web-based workflow
>> The problem with this is that it would not be possible without
>> changing
>> the git hosting entirely to something like Gitea. I'm personally a fan
>> of the email
Hello,
Attila Lendvai writes:
>> Now you might say that this leads to less diversity in the team of
>> committers and maintainers as you need a certain level of privilege to
>> seriously entertain the idea of dedicating that much time and effort to
>> a project and I agree, but I also think this
Hello,
宋文武 writes:
> Maxime Devos writes:
>
>> For example, naev used to work just fine, yet apparently it doesn't
>> anymore: https://issues.guix.gnu.org/65390.
>>
>> Given that Guix has ci.guix.gnu.org, I would expect such new problems
>> to be detected and resolved early, and it was detected
Hi again,
宋文武 writes:
> Maxime Devos writes:
>
>> For example, naev used to work just fine, yet apparently it doesn't
>> anymore: https://issues.guix.gnu.org/65390.
>>
>> Given that Guix has ci.guix.gnu.org, I would expect such new problems
>> to be detected and resolved early, and it was detec
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?
I'm not so sure about removing packages, personally if I'm in need of
a package that happens to be broken I find it easier to fix
19 matches
Mail list logo
