Displaying 6 results from an estimated 6 matches for "_unstable_".
2023 Oct 15
0
[RFC PATCH v2 1/7] bpf: Introduce BPF_PROG_TYPE_VNET_HASH
....is_valid_access = sk_filter_is_valid_access,
> + .convert_ctx_access = bpf_convert_ctx_access,
> + .gen_ld_abs = bpf_gen_ld_abs,
> +};
and we don't do ctx rewrites like this either.
Please see how hid-bpf and cgroup rstat are hooking up bpf
in _unstable_ way.
2012 Dec 03
0
[LLVMdev] Minimum Python Version
One of the most conservative distributions is Debian.
The python_defaults package has moved to 2.7.3 in Sid and 2.7.3~rc2-1 in
Wheezy (Debian 7.0 now on its 4th beta and soon to be release candidate
status).
I personally run Sid/Unstable in order to get general release builds of
LLVM/Clang > 2.9, never mind 3.2.
It seems reasonable to target 2.7.3 as the oldest python release.
- Marc J.
2006 Jul 05
2
Compilation of R packages
Le Mercredi 5 Juillet 2006 09:41, Dirk Eddelbuettel a ?crit?:
> Salut Vincent,
>
> On 4 July 2006 at 23:27, Vincent Goulet wrote:
> | I'm currently following your procedure suggested on R-SIG-Debian
> | (https://stat.ethz.ch/pipermail/r-sig-debian/2006-June/000095.html) to
> | compile and install the latest version of R on Kubuntu. It is my
> | understanding that I
2010 Jun 22
4
seek() and gzfile() on 32-bit R2.12.0 in linux
I have installed both 32-bit and 64-bit versions of R2.12.0 (2010-06-15
r52300) on my Ubuntu 10.04 64-bit system. I observe the following behavior
when running the examples from base::connections. There appears to be a
problem with seek() on a .gz file when using a 32-bit installation of
R2.12.0, but the problem doesn't appear in the 64-bit installation. I
realize that seek() has been
2012 Dec 01
11
[LLVMdev] Minimum Python Version
I'd like to continue the discussion about minimum Python versions from the
"Use multiprocessing instead of threading" thread in its own thread because
I feel it warrants additional discussion.
In that thread, we were discussing maintaining support for Python 2.4 and
2.5. The latest response is:
On Fri, Nov 30, 2012 at 1:40 PM, Daniel Dunbar <daniel at zuster.org> wrote:
>
2007 Nov 13
35
XEN - Broadcom issue: survey
I totally agree with Luc Boudreau about this problem.
On modern branded server they ALL use Broadcom chipset... I must admit that:
a) lot of people are experiencing the problem but can tolerate it
or
b) someone already experienced this problem and solved it
Lets'' approach the problem pragmatically... just start with a survey on
the list. ... hope we solve this issue soon.
Ivan