On Wed, Sep 4, 2019 at 2:46 PM Jan Kratochvil <jan.kratochvil@xxxxxxxxxx> wrote: > > On Mon, 02 Sep 2019 23:33:32 +0200, Richard W.M. Jones wrote: > > On Sun, Sep 01, 2019 at 09:33:29PM +0200, Jan Kratochvil wrote: > > > Fix stack overflow in: `inotifytools_replace_filename` > > > https://bugzilla.redhat.com/show_bug.cgi?id=1741472 > > > > > > Not sure how to fix this crashing bug. Upstream is dead while Fedora package > > > maintainer requires to upstream the fix first. A Catch 22. > > > > > > Debian has the crasher fixed by an off-trunk simple patch, Fedora cannot? > > > > I would start by pulling in the Debian fix into the Fedora package. > > This is what I tried in the Bug above and I failed. So I have submitted > a request to become co-maintainer with no response so far. > > (Besides that the Debian fix compared to my fix is a hack, not properly coded > from programming point of view. But I agree the Debian fix does work.) > > > > Then talk to the Debian folk and see if you can set up a simple git > > repo on one of the many free hosting services to collect these patches > > "upstream". > > There is already upstream but its maintainer does not respond. So do you mean > to make a new upstream? Is it really required to push 2 characters of a fix to > Fedora package? This isn't required, no. That being said, if this package is abandoned upstream then it probably makes sense to contact the Debian maintainer and establish a fork where our projects can at least share patches. If upstream comes back to life, we can merge them back together then. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
