| Summary: | Updating sys-libs/tevent-0.9.29 to sys-libs/tevent-0.9.31-r1 breaks samba, specifically nmbd process | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | thunderrd <rzubaly> |
| Component: | Current packages | Assignee: | Patrick Lauer <patrick> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | rzubaly, samba |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
thunderrd
2017-01-22 15:52:07 UTC
It's the same bug. Either upgrade both, tevent _and_ samba or none. Regarding your build error in samba-4.5.4, plase re-sync and try again. *** This bug has been marked as a duplicate of bug 592502 *** That is exactly what I did. tevent succeeds, and samba fails, and I can reproduce it _on_my_machine_. When tevent succeeds, and samba fails, the current install of samba-4.2.14 loses connectivity as a result. In order to restore connectivity to the existing samba version 4.2.14, I must downgrade tevent. Upgrading both FAILS, because samba chokes in the manner I described. If the samba build fail is a different bug, I will file another. Let me know what is the correct protocol. ...Well...it seems you're right. I swear to you, I resynced and tried several times [3 or 4?] over the last two days since I filed this bug, and it failed each time, exactly the same way. But, just to make sure I wasn't crazy, I tried again, just now. Only because you asked me to, Poly-C. And this time it succeeded. So *something* must be different in the tree in the last 12 hours, because that is the last time I attempted this. Anyhow, all's well that ends well, thanks. I just wish I understood what happened. Sorry for not being more verbose in my previous reply. I was in a rush. This is what happened in the samba ebuild and why I asked you to re-sync and try again: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7ad932cf204b2a7ccf65b6be853f23c4450eb732 which basically just prevents the error you've observed in samba-4.5.4 That explains it, then. Thanks for getting back to me. |