Re: curious when certain patches might become part of a release
13.02.2015 21:38, Benjamin Connelly пишет: The bug wasn't specific to FreeBSD (or the FreeBSD port.) It's apparently fixed by 31262a892ba7 and 80ed82a93c1a Of course it is not a port bug. I minded you can ask port maintainer to include those patches into the port.
Re: curious when certain patches might become part of a release
> >>> We ran in to this same problem others discussed in this thread: > >>> > >>> http://dovecot.org/list/dovecot/2014-November/098927.html > >>> > >>> and have also applied the patches (31262a892ba7 and 80ed82a93c1a) and it > >>> seems to have stopped the panics. We usually just use the FreeBSD ports > >>> tree to install software, so I'm looking forward to the time when we can > >>> go back to that. Will those patches be part of the next release? > >> > >> you have to ask this question the FreeBSD maintainer of the Dovecot > >> package. > > > > But the FreeBSD ports tree is up to the latest 2.2.15 -- yet we were > > still experiencing the panics, and had to apply those patches. So I'm > > wondering more about what version release of Dovecot itself will include > > those mbox sync patches. . . > > > > Ben > > > Do you mind to open a PR in the FreeBSD Bugzilla? Sorry, I think my naive question about the Dovecot development process has lead us astray. The bug wasn't specific to FreeBSD (or the FreeBSD port.) It's apparently fixed by 31262a892ba7 and 80ed82a93c1a so I was just wondering how Dovecot development works: should we expect these patches to be a part of 2.3 when it's released? Or might they appear in a 2.2.16 or somesuch? Benjamin
Re: curious when certain patches might become part of a release
13.02.2015 20:24, Benjamin Connelly пишет: We ran in to this same problem others discussed in this thread: http://dovecot.org/list/dovecot/2014-November/098927.html and have also applied the patches (31262a892ba7 and 80ed82a93c1a) and it seems to have stopped the panics. We usually just use the FreeBSD ports tree to install software, so I'm looking forward to the time when we can go back to that. Will those patches be part of the next release? you have to ask this question the FreeBSD maintainer of the Dovecot package. But the FreeBSD ports tree is up to the latest 2.2.15 -- yet we were still experiencing the panics, and had to apply those patches. So I'm wondering more about what version release of Dovecot itself will include those mbox sync patches. . . Ben Do you mind to open a PR in the FreeBSD Bugzilla? -- Alexander
Re: curious when certain patches might become part of a release
> > We ran in to this same problem others discussed in this thread: > > > > http://dovecot.org/list/dovecot/2014-November/098927.html > > > > and have also applied the patches (31262a892ba7 and 80ed82a93c1a) and it > > seems to have stopped the panics. We usually just use the FreeBSD ports > > tree to install software, so I'm looking forward to the time when we can > > go back to that. Will those patches be part of the next release? > > you have to ask this question the FreeBSD maintainer of the Dovecot > package. But the FreeBSD ports tree is up to the latest 2.2.15 -- yet we were still experiencing the panics, and had to apply those patches. So I'm wondering more about what version release of Dovecot itself will include those mbox sync patches. . . Ben
Re: curious when certain patches might become part of a release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Feb 2015, Benjamin Connelly wrote: We ran in to this same problem others discussed in this thread: http://dovecot.org/list/dovecot/2014-November/098927.html and have also applied the patches (31262a892ba7 and 80ed82a93c1a) and it seems to have stopped the panics. We usually just use the FreeBSD ports tree to install software, so I'm looking forward to the time when we can go back to that. Will those patches be part of the next release? you have to ask this question the FreeBSD maintainer of the Dovecot package. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEVAwUBVN2mPnz1H7kL/d9rAQINMgf/Wq77+rLBCt9MbLwpItAga1aJH20hmaW+ 15+82sQ4/wGAR81RARiFR1hftz29Rdc/p4ZtOvNg2uE9VWpKUnRg/5DJA/ey3n26 Ns1mt7Qfn4V+ed1S7YYkJp4+MMqEDt+lMdCpau7koabU55S+thqUdsGBXBEGQgYe ElWnnb4p9TJEM5c2zRrI0D3M0yAXxCaG8qfPPYVc3vKXQq7siss42w/MBstmbBgY N48N18vqYNuSRdwjXlKzV1wSzodTEtnTsUTmMbngxl//kmyyyNhv5+xVh/EGj5IE jsFbrw0vZhg/vdAPZQUeeBRrdnid5BgVp4Pfdxs5SyhMbCZUkQzsKA== =2qFL -END PGP SIGNATURE-
