Bug 266326 - [patch] net-mgmt/rubygem-riemann-client: Update to 1.0.1
Summary: [patch] net-mgmt/rubygem-riemann-client: Update to 1.0.1
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Dave Cottlehuber
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-09 20:52 UTC by Romain Tartière
Modified: 2022-09-11 12:27 UTC (History)
0 users

See Also:

Attachments
Update to 1.0.1 (4.85 KB, patch)
2022-09-09 20:52 UTC, Romain Tartière 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Romain Tartière freebsd_committer freebsd_triage 2022-09-09 20:52:43 UTC 
Created attachment 236462 [details]
Update to 1.0.1

Hey dch@!

riemann ruby client was updated ;-)
Comment 1 commit-hook freebsd_committer freebsd_triage 2022-09-11 12:25:40 UTC 
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=dbfcc3a1b034e9a217df24a42715db1a18e7fb79

commit dbfcc3a1b034e9a217df24a42715db1a18e7fb79
Author:     Romain Tartière <romain@FreeBSD.org>
AuthorDate: 2022-09-11 12:11:59 +0000
Commit:     Dave Cottlehuber <dch@FreeBSD.org>
CommitDate: 2022-09-11 12:23:06 +0000

    net-mgmt/rubygem-riemann-client: Update to 1.0.1

    ChangeLog: https://github.com/riemann/riemann-ruby-client/blob/main/CHANGELOG.md#101-2022-06-25

    PR:             266326
    Tested by:      romain
    Sponsored by:   SkunkWerks, GmbH

 net-mgmt/rubygem-riemann-client/Makefile           |  6 +--
 net-mgmt/rubygem-riemann-client/distinfo           |  6 +--
 .../patch-lib_riemann_client_tcp__socket.rb (gone) | 48 ----------------------
 .../files/patch-riemann-client.gemspec (gone)      | 11 -----
 4 files changed, 5 insertions(+), 66 deletions(-)
Comment 2 Dave Cottlehuber freebsd_committer freebsd_triage 2022-09-11 12:27:45 UTC 
merci! do you want to pick up ownership of these ports? I see you're active in upstream. If so, just update maintainer for them, I'm ok.