| 1 |
* Harry Putnam (reader@×××××××.com) [14.06.09 19:46]: |
| 2 |
> Sebastian Günther <samson@××××××××××××××××.de> writes: |
| 3 |
> |
| 4 |
> > * Harry Putnam (reader@×××××××.com) [12.06.09 16:41]: |
| 5 |
> >> |
| 6 |
> >> There is a patch offered but still one would think using standard |
| 7 |
> >> emerge on a package that is outside the `~' daredevil stage and is not |
| 8 |
> >> masked, it should `just work' [tm]. |
| 9 |
> >> |
| 10 |
> >> |
| 11 |
> > |
| 12 |
> > When I read the bug rightfully, procmail did not build with glibc |
| 13 |
> > 2.10.1, which is *not* stable yet, especially because of a lot packages |
| 14 |
> > which don't build cleanly with it at the moment. |
| 15 |
> > |
| 16 |
> > So if you'd use the stable glibc it would build fine. There is no need |
| 17 |
> > to mark procmail in any way. ~x86 should be able to apply patches on |
| 18 |
> > their own, or wait until the patch arrives in tree. |
| 19 |
> |
| 20 |
> Probably should use only stable but never have in over 5 yrs. |
| 21 |
> Probably much to the dismay of this list. |
| 22 |
> |
| 23 |
> But even then, when a package is known in advance NOT to install with |
| 24 |
> current ~x86 tools, seems there would be some way to let user know |
| 25 |
> that. |
| 26 |
> |
| 27 |
|
| 28 |
First of all the bug is fixed, and a working patch was there 1 day after |
| 29 |
the opening. I call this a fast response... |
| 30 |
|
| 31 |
For ~x86 this is a working solution, and if you use ~x86: b.g.o *is* the |
| 32 |
users information system and applying patches should be no problem. |
| 33 |
|
| 34 |
> Since you've said it is because of glibc... and this is a known bug |
| 35 |
> seems there might be a way to flag or mark procmail as incompatible |
| 36 |
> with it. |
| 37 |
> |
| 38 |
|
| 39 |
The problem with glibc is, that you only find issues when you recompile |
| 40 |
your whole world, which is not needed in most cases. And most of the |
| 41 |
errors with glibc-2.10.1 result from wrong castings, which is only a |
| 42 |
compile time issue not a run issue. |
| 43 |
|
| 44 |
And all these problems are upstream, so you can patch for yourself in |
| 45 |
gentoo, but the cleaner solution is to wait for upstream to include the |
| 46 |
patch there. And release a new version, when they do too... |
| 47 |
|
| 48 |
Sebastian |
| 49 |
|
| 50 |
-- |
| 51 |
" Religion ist das Opium des Volkes. " | _ ASCII ribbon campaign |
| 52 |
Karl Marx | ( ) against HTML e-mail |
| 53 |
SEB@STI@N GÜNTHER | X against M$ attachments |
| 54 |
mailto:samson@××××××××××××××××.de | / \ www.asciiribbon.org |
Archives