2021-10-26 12:20:11 by Nia Alarie | Files touched by this commit (3016) |
Log message:
archivers: Replace RMD160 checksums with BLAKE2s checksums
All checksums have been double-checked against existing RMD160 and
SHA512 hashes
Could not be committed due to merge conflict:
devel/py-traitlets/distinfo
The following distfiles were unfetchable (note: some may be only fetched
conditionally):
./devel/pvs/distinfo pvs-3.2-solaris.tgz
./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip
|
2021-10-07 15:44:44 by Nia Alarie | Files touched by this commit (3017) |
Log message:
devel: Remove SHA1 hashes for distfiles
|
2021-06-14 17:12:03 by Takahiro Kambe | Files touched by this commit (2) | |
Log message:
devel/ruby-kgio: update to 2.11.4
kgio 2.11.4 / 2021-05-25 23:24 UTC
This release fixes compatibility with GC.compact on Ruby 3.x.
Thanks to Ngan Pham for the patch and Aaron Patterson for the
feedback:
\
https://yhbt.net/kgio-public/CAAvYYt5Z5f2rMuXO5DMpR1-6uRvu_gXKDvqcyoZ+oNcLiTH39g@mail.gmail.com/T/
kgio remains obsolete and deprecated, and it's primary dependent
will be updated to not depend on it in the future.
|
2020-01-23 14:35:45 by Makoto Fujiwara | Files touched by this commit (1) |
Log message:
regen. I hope I'm not wrong
|
2020-01-16 16:33:29 by Takahiro Kambe | Files touched by this commit (1) | |
Log message:
devel/ruby-kgio: update to 2.11.3
Update ruby-kgio to 2.11.3.
* Update HOMEPAGE.
=== kgio 2.11.3 / 2020-01-08 09:25 UTC
Some doc and warning fixes for newer Rubies.
We're no longer on bogomips.org since it's due
for expiry and I can't pay extortionists for a .org, so
s/bogomips.org/yhbt.net/ for now, and be prepared to move again
when extortionists move onto the .net TLD.
pkg.mk: use --local to "gem install"
pkg.mk: use dark216 theme for Earth Day 2019
test: fix warnings with RUBYOPT=-w
tests: fix unused variable warnings from newer Rubies
test_connect_fd_leak: do not close socket if non-existent
test_syssend: avoid warning on cleanup
build: remove olddoc from the gemspec
doc: remove private email and outdated gmane archives
doc: move from bogomips.org/kgio to yhbt.net/kgio
|
2018-03-13 18:00:51 by Takahiro Kambe | Files touched by this commit (2) | |
Log message:
devel/ruby-kgio: update to 2.11.2
=== kgio 2.11.2 - fix Ruby 2.5 compatibility for accept_class / 2018-01-30 21:11 UTC
This release fixes a bug affecting the Rainbows! web server
which uses Kgio.accept_class:
\
https://bogomips.org/rainbows-public/CANp6QoJXRbPLqmOPpG7XmZBc+oYqLWCcq1ipvOyNEQPXDEwx9Q@mail.gmail.com/
* accept: avoid passing unnecessary arg to rb_funcall
=== kgio 2.11.1 - fix Ruby 2.5.0dev compatibility / 2017-12-15 19:40 UTC
This release fixes compatibility with Ruby 2.5.0 preview and
release candidates (and thus should be ready for 2.5.0 final)
on some platforms. At least clang 5.0.0 on OpenBSD is affected.
Thanks to Jeremy Evans for the fix.
There's also minor documentation updates since 2.11.0
|
2017-09-04 20:08:31 by Thomas Klausner | Files touched by this commit (163) |
Log message:
Follow some redirects.
|
2017-03-12 15:38:18 by Takahiro Kambe | Files touched by this commit (3) | |
Log message:
Update ruby-kgio to 2.11.0.
=== kgio 2.11.0 - reverting 2.10.0 breakage / 2016-12-16 22:56 UTC
Mainly this release reverts back to kgio 2.9.3 behavior by
supporting "autopush" functionality in the C extension.
Removing this feature in 2.10.0 was a monumental mistake(*) on
my part which caused a performance regression for ONE known user
of kgio on the deprecated (but supported) Rainbows! server.
This release does not affect known users outside of Rainbows!,
but we may have unknown users, too.
The attempt at a pure Ruby version of autopush had flaws and
regressions in real-world testing, so that was abandoned.
So yeah, kgio will be supported indefinitely even in the face
of internal changes to MRI, but I strongly discourage its use
for new projects.
Users who only support Ruby 2.3 (and later) are encouraged to
use `exception: false` with all *_nonblock methods.
4 changes since 2.10.0:
resurrect Kgio.autopush support in pure Ruby [REVERTED]
reinstate the original (and dangerous) autopush in C
TODO: update with Ruby 2.3 status
test: increase test data sizes to fill socket buffers
(*) - as was making this a separate project, at all
|
2015-11-03 04:29:40 by Alistair G. Crooks | Files touched by this commit (1995) |
Log message:
Add SHA512 digests for distfiles for devel category
Issues found with existing distfiles:
distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
distfiles/fortran-utils-1.1.tar.gz
distfiles/ivykis-0.39.tar.gz
distfiles/enum-1.11.tar.gz
distfiles/pvs-3.2-libraries.tgz
distfiles/pvs-3.2-linux.tgz
distfiles/pvs-3.2-solaris.tgz
distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.
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.
|
2015-10-04 14:17:04 by Takahiro Kambe | Files touched by this commit (3) | |
Log message:
Update ruby-kgio to 2.10.0.
=== kgio 2.10.0 - slimming down... / 2015-09-06 08:12 UTC
The largely-unused autopush functionality is now a no-op.
Existing applications will probably not notice, and are
better off using MSG_MORE anyways if they're on Linux.
Our poll(2) wrapper now uses rb_hash_clear if available,
reducing global method cache dependence.
shortlog of changes since 2.9.3:
README: remove reference to Rainbows!
writev: update comment on preserving errno
poll: avoid rb_funcall for rb_hash_clear
minor doc updates
remove autopush support and make it a no-op
HACKING: update URL for Message-ID lookup
|