Opened 9 years ago
Closed 9 years ago
#6847 closed defect (fixed)
update valgrind patch
Reported by: | Owned by: | Pierre Labastie | |
---|---|---|---|
Priority: | normal | Milestone: | 7.8 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
Update the valgrind patch for glibc-2.22.
Probably s/21/22/ in the patch will be enough but the patch needs to also be renamed to valgrind-3.10.1-glibc_2.22-1.patch
Change History (6)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | assigned → new |
comment:4 by , 9 years ago
Status: | new → assigned |
---|
comment:5 by , 9 years ago
I was in a hurry when I made the first patch, but I found that adding:
-e 's/2\.20)/2.2[0-9])/'
to the sed command is enough.
Note:
See TracTickets
for help on using tickets.
I'm starting to think that better than being interested by BLFS, I should be interested by systemd, to report what is wrong there. I am still using 2.21, and would find new things when building in the freeze:
Although I have filtered out whatever comes from there in yahoo, I can be quite sure that this ticket has been originated from systemd. They are never capable of getting a systemd up to date book, so the solution is keeping an eye in BLFS, point the problems, when copying it, and pose as the smart ones.
Well, it seems that I don't need to worry about freeze and rebuild packages for tagging by then, because plenty of people will be doing that.