Mark H Weaver writes:
> The reason I am so sensitive to this issue is that Debian included
> nonfree software in their kernels for many years, despite it being a
> widely known violation of the Debian Free Software Guidelines.
> Apparently it was deemed sufficient to make a "best effort" to comply
Gábor Boskovits writes:
> The libvirt service accepts a libvirt configuration, where you can specify
> the libvirt package in use. I guess it would be easy to provide a similar
> mechanism to give the qemu package. If qemu is an input of libvirt then
> providing a custom libvirt having the cust
Hi Mark,
> Mark H Weaver writes:
>
>> Ricardo Wurmus writes:
>>
>>> The TODO list for convenience:
>>>
>>> * There is still some data transmitted when starting the browser for the
>>> first time. It seems related to the "domain_reliability" component.
>>> * Remove remaining "Web Store" link
Le mar. 21 août 2018 à 23:43, Arne Babenhauserheide a écrit :
>
>
> Jan Nieuwenhuizen writes:
>
> > We are delighted to announce the release of GNU Mes 0.17, representing
> > 64 commits over 6 weeks.
> >
> > Mes is now an official GNU package and we have bootstrapped gcc-4.7.4
> > for x86-linux w
Amin Bandali writes:
> Nils Gillmann writes:
>
>> Please read into the chromium thread or search locally through it -
>> Marius already had some comments on ungoogled-chromium. Our chromium
>> browser is not just chromium taken from upstream. Many (maintained)
>> patches are taken and applied.
>
Ricardo Wurmus writes:
> Hi Mark,
>
>> Mark H Weaver writes:
>>
>>> Ricardo Wurmus writes:
>>>
The TODO list for convenience:
* There is still some data transmitted when starting the browser for the
first time. It seems related to the "domain_reliability" component.
Marius Bakke writes:
> Amin Bandali writes:
>
>> As for the "lagging too far behind upstream" issue, that doesn't
>> seem to be the case anymore: looking at releases on [3] and [4]
>> it looks like ungoogled-chromium's latest shipped release matches
>> the latest released chromium version. Gran
Hello Guix!
Coming soon: Guix will no longer provide its own crypto modules and will
instead depend on Guile-Gcrypt:
https://issues.guix.info/issue/32606
‘guix pull’ will happily perform the transition.
If you’re used to working on a Git checkout with “guix environment
guix”, you’ll have to a
Hi Amin,
>> The search box accepts issue numbers (for *any* bug on the GNU instance
>> of Debbugs), but it also supports a few special queries, such as
>>
>> is:open / is:pending –> only open issues
>> is:done / is:closed –> only completed issues
>> title:foo -> issues containing “f
Ricardo Wurmus writes:
> Hi Amin,
>
>>> The search box accepts issue numbers (for *any* bug on the GNU instance
>>> of Debbugs), but it also supports a few special queries, such as
>>>
>>> is:open / is:pending –> only open issues
>>> is:done / is:closed –> only completed issues
>>> t
Hi Ricardo,
> I agree. I don’t know how to present these things nicely, but I’ll play
> around with this.
>
> BTW: “submitter:who” should also work now. Like “is:…” it’s a rather
> expensive query because the result set from Debbugs has to be filtered
> locally.
Cool, thanks!
>>> - make the se
Marius Bakke writes:
> If this package gets into Guix, I think we
> should add system tests (or similar) to catch regressions in the
> unsolicited network traffic area.
That’s an excellent idea, though it may be difficult to accomplish. I
wouldn’t know how to do this reliably as the behaviour
12 matches
Mail list logo
