<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pkgsrc/time/polclock, branch trunk</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk</id>
<link rel='self' href='https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/'/>
<updated>2021-10-26T11:24:16Z</updated>
<entry>
<title>time: Replace RMD160 checksums with BLAKE2s checksums</title>
<updated>2021-10-26T11:24:16Z</updated>
<author>
<name>nia</name>
<email>nia@pkgsrc.org</email>
</author>
<published>2021-10-26T11:24:16Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=1623dea72ed1a4ed02e9ed73c7ab2db48c0a7d52'/>
<id>urn:sha1:1623dea72ed1a4ed02e9ed73c7ab2db48c0a7d52</id>
<content type='text'>
All checksums have been double-checked against existing RMD160 and
SHA512 hashes</content>
</entry>
<entry>
<title>time: Remove SHA1 hashes for distfiles</title>
<updated>2021-10-07T15:03:53Z</updated>
<author>
<name>nia</name>
<email>nia@pkgsrc.org</email>
</author>
<published>2021-10-07T15:03:53Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=700f911091abce01438aeba15c3ee0af17eb1d66'/>
<id>urn:sha1:700f911091abce01438aeba15c3ee0af17eb1d66</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add SHA512 digests for distfiles for time category</title>
<updated>2015-11-02T23:31:35Z</updated>
<author>
<name>agc</name>
<email>agc@pkgsrc.org</email>
</author>
<published>2015-11-02T23:31:35Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=f54ed3045c725616ba5dc789bee5c25b23a66e1e'/>
<id>urn:sha1:f54ed3045c725616ba5dc789bee5c25b23a66e1e</id>
<content type='text'>
Problems found with mismatching existing digests for:
	distfiles/asclock-classic-1.0.tar.gz
	distfiles/asclock-gtk-2.1.10beta.tar.gz
	distfiles/asclock-xlib-2.0.11.tar.gz
	distfiles/emiclock-2.0.2.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.</content>
</entry>
<entry>
<title>Add patchsum for patch-polsys.c</title>
<updated>2012-12-20T22:12:59Z</updated>
<author>
<name>joerg</name>
<email>joerg@pkgsrc.org</email>
</author>
<published>2012-12-20T22:12:59Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=44492c66e024f7fbdbcddfe8e9d50557baa50b9d'/>
<id>urn:sha1:44492c66e024f7fbdbcddfe8e9d50557baa50b9d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Consistently return a value in non-void functions.</title>
<updated>2012-12-20T21:36:03Z</updated>
<author>
<name>joerg</name>
<email>joerg@pkgsrc.org</email>
</author>
<published>2012-12-20T21:36:03Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=431bd1dc6b7580a556d957f9b2b3657cbed8db99'/>
<id>urn:sha1:431bd1dc6b7580a556d957f9b2b3657cbed8db99</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days.</title>
<updated>2012-10-08T13:04:16Z</updated>
<author>
<name>asau</name>
<email>asau@pkgsrc.org</email>
</author>
<published>2012-10-08T13:04:16Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=7a48191ad0a52cfc86bcf6477e155dce1d4802ad'/>
<id>urn:sha1:7a48191ad0a52cfc86bcf6477e155dce1d4802ad</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add DESTDIR support.</title>
<updated>2008-06-12T02:14:13Z</updated>
<author>
<name>joerg</name>
<email>joerg@pkgsrc.org</email>
</author>
<published>2008-06-12T02:14:13Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=ba171a91fab519f587b027c1a2888cb6e3fce049'/>
<id>urn:sha1:ba171a91fab519f587b027c1a2888cb6e3fce049</id>
<content type='text'>
</content>
</entry>
<entry>
<title>- fine grained X11 dependencies for packages which have either USE_IMAKE</title>
<updated>2006-12-27T13:37:35Z</updated>
<author>
<name>joerg</name>
<email>joerg@pkgsrc.org</email>
</author>
<published>2006-12-27T13:37:35Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=d26cf36e5784f5b648404b8d68c21adb4398f33f'/>
<id>urn:sha1:d26cf36e5784f5b648404b8d68c21adb4398f33f</id>
<content type='text'>
  or USE_X11BASE set, but don't include mk/x11.buildlink3.mk directly or
  via buildlink3.mks
- introduce BUILDLINK_PREFIX.libXpm as alias for BUILDLINK_PREFIX.xpm
  in the !modular case
- fix some cases where the check for libX11 couldn't work at all by using
  C++ for compilation without including the proper headers

Verified using a full X11_TYPE=xorg bulk build without additional
breakage. Discussed with salo@, wiz@ and send to packages@ for feedback.</content>
</entry>
<entry>
<title>Update MASTER_SITES and/or HOMEPAGE, from Sergey Svishchev.</title>
<updated>2006-10-04T21:59:34Z</updated>
<author>
<name>wiz</name>
<email>wiz@pkgsrc.org</email>
</author>
<published>2006-10-04T21:59:34Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=7938151fe64ccdb4a6590729489aee3a565c7f41'/>
<id>urn:sha1:7938151fe64ccdb4a6590729489aee3a565c7f41</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no</title>
<updated>2006-03-04T21:28:51Z</updated>
<author>
<name>jlam</name>
<email>jlam@pkgsrc.org</email>
</author>
<published>2006-03-04T21:28:51Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=9c8b5ede437e0b7c2f7b0cdd5f8500d619968fdb'/>
<id>urn:sha1:9c8b5ede437e0b7c2f7b0cdd5f8500d619968fdb</id>
<content type='text'>
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.</content>
</entry>
</feed>
