#2855 closed enhancement (fixed)
bash-4.2 patch 8
| Reported by: | aztec | Owned by: | Matthew Burgess |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Book | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
The current Bash patch in LFS contains patches 1-7. There's now also a patch 8: http://lists.gnu.org/archive/html/bug-bash/2011-03/msg00142.html
Change History (6)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
I am against including *any* patches from bash upstream unless the patch is security related.
You can't only include security related patches on bash, as a working sh is a requirement to build mostly anything.
I know there is 38 patches for 4.0, 10 for 4.1 and already 8 for 4.2. Would you qualify 4.2p1, 4.2p3 or 4.2p4 of security patches or FTBS fix for other packages?
It is basically asking us to continuously update to the latest development version.
Wrong. Bash development model is not to accumulate patches until the next version. Patches are made following bugs report.
comment:3 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 13 years ago
| Type: | task → enhancement |
|---|
Note:
See TracTickets
for help on using tickets.
I am against including *any* patches from bash upstream unless the patch is security related. It is basically asking us to continuously update to the latest development version. We don't do that for any other package.