-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 11 Dec 2006 11:23:09 -0500 Vivek Khera <[EMAIL PROTECTED]> wrote:
> It seems that the change log on freshports for the databases/slony1 > port shows that someone somewhere is confused as to who's the > maintainer of the port. The Makefile clearly shows it is still me. Sorry, it was definietly my fault. I thought its a maintainer-timeout case. It was my mistake and I hope you forgive me for this mistake. > > On 23 Nov 2006, an update was issued to upgrade the 1.1.5 version to > 1.2.0 which had known errors in it which cause data loss. Somehow > it was applied. A few days later a manual patch was added to work > around that. The initial update indicates that whomever submitted > the port was either claiming to be or was assumed to be the > maintainer. For this update of 1.2.0 gives a pr show here http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/105575 here is my mistake thats commit is after 7 days not 14 days. This is my mistake right. After this commit, I received a private email with a bugfix. Description of the problem: http://gborg.postgresql.org/project/slony1/bugs/bugupdate.php?1591 Then I committed a fix for this problem. Yes without approval from maintainer then i forgot to double check the maintainer mail. > Then on 8 Dec 2006, another update was issued and applied, to 1.2.1. Yes here telling me the self People with a patch of 1.2.1, i check this on my tinderbox this build fine and committed this. Yes I looked not yet on more maintainer mail. > > Today I saw in my email a patch to correct some error in the pkg- > plist file, which is how I noticed that someone had updated the > slony1 port. > > This is not how it is supposed to work. I should have gotten these > notices on *every* PR submitted with a patch against this port. > There is no reason that 1.2.0 should have *ever* hit the ports tree > as it was broken out of the gate. This is one of the reason ports > have maintainers: to ensure broken things don't get thrown into the > collection. > > If the committers are not going to follow the rules, then why should > anyone bother to be a maintainer? I could say this is all my fault a concatenation of stupid mistakes :( I hope you forgive me for this mistake. - - Martin - -- Martin Wilke | irc.unixfreunde.de #bsd [EMAIL PROTECTED] | [EMAIL PROTECTED] FreeBSD Committer | Power to Serve -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFfZnJPrCIFpjWZiwRAk+6AJ9yu1Cb2CpO9tBNkEsI+5EbC+kBQACfUY/Y jb2MtcMsi3jM89HoKbm63bM= =G8dt -----END PGP SIGNATURE-----
_______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"