Reputation
3,088
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
3 16 53
Impact
~320k people reached

1d
awarded  Notable Question
Apr
24
awarded  Revival
Apr
24
revised Why will the C++ Library not disable, GCC
added 220 characters in body
Apr
24
revised Why will the C++ Library not disable, GCC
added 163 characters in body
Apr
24
revised Why will the C++ Library not disable, GCC
formatting
Apr
24
answered Why will the C++ Library not disable, GCC
Apr
24
accepted Bypass GPG signature checks only for a single repository
Apr
24
comment Bypass GPG signature checks only for a single repository
thanks a bunch. This was exactly what I was looking for. I trust 1.0.1ubuntu2.7 will have that feature already, given its version number.
Apr
22
comment Bypass GPG signature checks only for a single repository
@Celada: reprepo was my pick so far.
Apr
22
comment Bypass GPG signature checks only for a single repository
@Celada: this is a repository for local use only. Who would be able to access it. Use case: a host with guest containers. Both host and containers will have access. No public access planned. But I guess I'll hold out for an answer a bit longer and go for the otherwise inevitable (signing).
Apr
22
comment Bypass GPG signature checks only for a single repository
@Celada: is that an opinion (that it's "strictly better") or is there a rationale for your statement? I'm asking, because so far I cannot see a reason how this would improve security or any other aspect. The only time when this would be somewhat beneficial, would be if I ever intended to publish my repo after all, no?
Apr
22
asked Bypass GPG signature checks only for a single repository
Apr
21
reviewed Approve Sticky bit and users with sudo permission
Apr
17
awarded  Popular Question
Apr
13
revised Why gmake fails if vpath points to current directory
added 247 characters in body
Apr
13
answered Why gmake fails if vpath points to current directory
Apr
13
comment Why gmake fails if vpath points to current directory
The edit helped. I can now not only reproduce the problem but also see the issue.
Apr
13
comment Why gmake fails if vpath points to current directory
You are completely missing the point. I tried on my system the following: diff <(make -npf makefile1) <(make -npf makefile2)|grep -E '^[+-]#' ... only difference VPATH=. versus VPATH=./. ... now guess what? They are identical. In short: your question lacks enough information to even attempt to answer it.
Apr
13
comment Why gmake fails if vpath points to current directory
@gena2x: yeah, your question is also not an easy case as you ask why something doesn't work and expect us to infer what your actual problem is. It would make more sense if you gave us the root problem, then what you tried (we have that) and then perhaps what you expect to see. Your question is like "why does that hammer not work for fastening this screw?" when your question should be "how can I fasten that screw?" ;) You don't even give the working and non-working version, because puzzle pieces are missing to reproduce this on any given machine. You don't give those.
Apr
13
comment Why gmake fails if vpath points to current directory
Create 1 file with what you deem functional and one as reproduced above. Then call diff -u <(make -npf makefile1) <(make -npf makefile2) ...