pkgsrc-Changes archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: CVS commit: pkgsrc/doc

On Mon, 20 Aug 2012 23:34:10 +0900, Christos Zoulas 
<> wrote:

If they were released at the same time, my guess is that they would contain
the same security fixes. Do you mean that you prefer to keep tracking 1.6?

* I'm not in a position to determine whether 1.6 is preferred or not.
* maintainer might know the update stopper.
* adam@ asked about 1.8.2 just before your update:
* your commit message included no particular reason for switching to 1.8,
  and not approved by the maintainer.
* your commit message to docs/CHANGES-2012 mentions "security fixes",
  it may the reason why to do urgent update, but you don't know about it.
* and your packaging is broken, fixed by the maintainer:

* When updating a package, commmit log should contains summary of the changes.
  It is documented in the pkgsrc guide 21.5.
  If you don't know the changes, you probably don't know the reason why you
  need to update the package.
* When updating a package, especially switching to new release branch,
  you should approved by the maintainer if exists.
* When developing the pkgsrc, you should set PKG_DEVELOPER=yes,
  and it will tell you what is broken about your packaging before the commit.

OBATA Akio /

Home | Main Index | Thread Index | Old Index