lsegal has quit [Quit: Quit: Quit: Quit: Stack Overflow.]
roidrage has joined #rubygems
newUser1234 has joined #rubygems
newUser1234 has quit [Ping timeout: 252 seconds]
redmenace has quit [Ping timeout: 265 seconds]
redmenace has joined #rubygems
dwradcliffe has quit [Ping timeout: 276 seconds]
dwradcliffe has joined #rubygems
vStone has quit [Ping timeout: 265 seconds]
vStone has joined #rubygems
vlad_starkov has quit [Ping timeout: 265 seconds]
vlad_starkov has joined #rubygems
avdi has quit [Ping timeout: 265 seconds]
avdi has joined #rubygems
elia has quit [Quit: Computer has gone to sleep.]
bbrowning_away is now known as bbrowning
tcopeland has quit [Quit: Leaving.]
vStone has quit [Remote host closed the connection]
vStone has joined #rubygems
newUser1234 has joined #rubygems
newUser1234 has quit [Ping timeout: 245 seconds]
elia has joined #rubygems
holden247 has joined #rubygems
csfranci1 has joined #rubygems
csfrancis has quit [Ping timeout: 265 seconds]
fidothe has quit [Ping timeout: 265 seconds]
fidothe has joined #rubygems
fidothe has quit [Changing host]
fidothe has joined #rubygems
elia has quit [Quit: Computer has gone to sleep.]
elia has joined #rubygems
elia has quit [Client Quit]
josh-k has quit [Remote host closed the connection]
josh-k has joined #rubygems
kgerman has joined #rubygems
josh-k has quit [Ping timeout: 260 seconds]
huoxito has joined #rubygems
kgerman has quit [Quit: kgerman]
newUser1234 has joined #rubygems
newUser1234 has quit [Ping timeout: 240 seconds]
elia has joined #rubygems
jesser has quit [Ping timeout: 245 seconds]
jesser has joined #rubygems
Fenhl has quit [Ping timeout: 260 seconds]
samkottler has quit [Ping timeout: 260 seconds]
th2389 has quit [Ping timeout: 245 seconds]
samkottler has joined #rubygems
Fenhl has joined #rubygems
samkottler is now known as Guest4614
Fenhl is now known as Guest17356
th2389 has joined #rubygems
imslavko has quit [Ping timeout: 245 seconds]
imslavko has joined #rubygems
sj26 has quit [Ping timeout: 260 seconds]
sj26 has joined #rubygems
newUser1234 has joined #rubygems
imslavko has quit [Ping timeout: 260 seconds]
tcopeland has joined #rubygems
imslavko has joined #rubygems
jpfuentes2 has joined #rubygems
elia has quit [Quit: Computer has gone to sleep.]
hakunin_ is now known as hakunin
seanlinsley has quit [Quit: seanlinsley]
elia has joined #rubygems
elia has quit [Quit: Computer has gone to sleep.]
elia has joined #rubygems
newUser1234 has quit [Remote host closed the connection]
seanlinsley has joined #rubygems
Guest4614 is now known as samkottler
samkottler has quit [Changing host]
samkottler has joined #rubygems
havenwood has joined #rubygems
denym_ is now known as denym_OFF
tbuehlmann has quit [Quit: Leaving]
shevy has joined #rubygems
<shevy>
is there a way from within a .rb file to find out all dependencies of a gem called 'foobar'? something like: Gem.find_dependencies_of('foobar') or something
<drbrain>
I can publish them on blog.rubygems.org at release time
<drbrain>
or we can figure out a way to have them present on rubygems.org/pages/download
<drbrain>
(or both)
nirix has quit [*.net *.split]
RichardBronosky has quit [*.net *.split]
<drbrain>
aef: yeah, understood
RichardBronosky has joined #rubygems
nirix has joined #rubygems
<aef>
drbrain: great. I'll do that. the reason I'm asking is because RVM fails to verify the download for rubygems 2.2.2 because the current stable release doesn't bring a hash for it. but a newer JRuby version requires this version when installing
<aef>
drbrain: by the way: on the main page it shows that the latest RubyGems release is 2.3.0 but if you progress to the downloads page it is 2.2.2. Prerelease version on main page maybe?
sdelmore has joined #rubygems
<drbrain>
evan: ↑ it looks like the auto-update didn't auto-update the downloads page
<drbrain>
evan: the links still point to 2.2.2 on the download page, but the home page says 2.3.0
<mpapis>
aef, mostly curious, you can open a PR for rvm with the md5s
sdelmore1 has quit [Ping timeout: 240 seconds]
<aef>
mpapis: yes. I want to. but I don't have a trusted upstream source for the hash value to push
<aef>
drbrain: is there any way you could provide me with a quick SHA256 sum for 2.2.2.tgz through a trusted channel?
<drbrain>
aef: I don't have the original one I uploaded handy
<drbrain>
but I could download via HTTPS from rubygems.org and checksum it
<drbrain>
is that acceptable?
<aef>
drbrain: is that possible? the links on the downloads page are plain HTTP
<aef>
drbrain: well, it seems to be a CDN endpoint without a valid certificate for the URL
<drbrain>
ditto
<drbrain>
evan: ↑
<drbrain>
the gem serving/hosting parts I don't know much about
<drbrain>
but evan seems away at the moment
jpfuentes2 has quit [Remote host closed the connection]
jpfuentes2 has joined #rubygems
josh-k has joined #rubygems
jpfuentes2 has quit [Read error: Connection reset by peer]
jpfuentes2 has joined #rubygems
josh-k has quit [Ping timeout: 272 seconds]
nomadic has quit [*.net *.split]
josh-k has joined #rubygems
nomadic_ has joined #rubygems
jkline has quit [Quit: jkline]
bbrowning is now known as bbrowning_away
kai3x5 has joined #rubygems
<aef>
drbrain: by the way, since the RubyGems repository intrusion some years ago, did anything improve on the gem signing front?
<drbrain>
aef: there are people working on integrating TUF with rubygems
<drbrain>
yes, but it has the same problems that the built-in rubygems signing stuff has
kgerman has quit [Quit: kgerman]
<drbrain>
… both are too hard to use for people who don't know and don't want to know about maintaining their own trust networks
<aef>
drbrain: I'll look into TUF. but on the other hand I honestly believe that X.509 is by far less flexible and harder to maintain than OpenPGP systems are. I used the X.509 system for some years, I would call it almost unusable. I didn't try the OpenPGP implementation yet, but I will do so soon.
<drbrain>
agreed, but I don't feel that a PGP solution is better-enough for inclusion in rubygems
jpfuentes2 has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<aef>
drbrain: another thing: if I remember correctly, we talked some years ago and you said you think that SemVer is a good thing and that RubyGems should support it. is that correct?
<drbrain>
sounds like something I would have said
<aef>
drbrain: if I see it correctly, RubyGems doesn't support the whole versioning syntax of SemVer. are you aware of that?
<drbrain>
SemVer 2.0? yes
<drbrain>
evan experimented with implementing that, but compatibility with older RubyGems for "+" and "-" in versions is problematic
<aef>
drbrain: would be nice to see that working some day.
<drbrain>
yes, but I'm wondering if its worth the pain for users
<drbrain>
a phased introduction is difficult since support would need to be implemented perfectly while you aren't able to release gems using "+" or "-"
<drbrain>
(which means we probably wouldn't find bugs until far too late)
jkline has joined #rubygems
kai3x5 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<evan>
adding semver isn't really possible at this point.
<evan>
because we can't change the version format
<evan>
we can make it more restrictive for future versions, but not less restrictive.
<evan>
which is what + and - would require
luislavena has joined #rubygems
<drbrain>
evan: did you also check out why rubygems.org/pages/download didn't auto-update?
<evan>
no, i'll do that.
tcopeland has joined #rubygems
newUser1234 has quit [Remote host closed the connection]
x1337807x has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
x1337807x has joined #rubygems
kai3x5 has joined #rubygems
x1337807x has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]