Date: Mon, 8 Jan 2018 19:56:02 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Miroslav Lachman <000.fbsd@quip.cz>, Michael Grimm <trashcan@ellael.org>, freebsd-ports@freebsd.org Subject: Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd Message-ID: <5A536A62.4030807@grosbein.net> In-Reply-To: <5A5351F0.7050804@quip.cz> References: <76627A89-D7E9-4010-910B-5F25886E7E7E@ellael.org> <5A523873.2050001@quip.cz> <5A524855.2040901@grosbein.net> <5A5284CC.9050400@quip.cz> <5A528749.9070308@grosbein.net> <5A528A87.4050908@quip.cz> <5A528D36.4020409@grosbein.net> <5A5351F0.7050804@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
08.01.2018 18:11, Miroslav Lachman wrote: >>> PRs are false alibi. Some of my PRs are open for more than 10 years. >> >> So were mine when I could not commit fixes myself. This is not excuse to be lazy and not make another one. >> >>> For all erroneous port there must be will on maintainer and committer side. >>> And if "they" think this is not a bug >> >> If we have written policy (and we have in this case), and upgrade really break things, >> sane committer will not think "this is not a bug". >> >> Again, do you have a PR with "how-to-repeat" scenario and a patch, >> so I could take it? > > OK, let's move on. I can open PR if you are willing to help and commit some fixes. But can we first talk Relevant discussion should better take place in the PR itself so it's not lost and easier to point to when asking corresponding parties, f.e. portmgr@ You may open PR without patch too, you know. But it needs clear description of the problem and "how-to-repeat".
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5A536A62.4030807>