by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 04 15:07

    agnivade on master

    [TravisCI] uploaded assets afte… (compare)

  • Jun 04 15:05

    zdroid on master

    jc: add page (#4089) (compare)

  • Jun 04 15:05
    zdroid closed #4089
  • Jun 04 13:58
    kellyjonbrazil synchronize #4089
  • Jun 04 13:45

    agnivade on master

    [TravisCI] uploaded assets afte… (compare)

  • Jun 04 13:44

    zdroid on master

    macchanger: add page (#4087) C… (compare)

  • Jun 04 13:44
    zdroid closed #4087
  • Jun 04 13:41
    zdroid synchronize #4087
  • Jun 04 11:35
    andrik labeled #4087
  • Jun 04 11:34
    andrik commented #4089
  • Jun 04 06:23
    einverne labeled #4089
  • Jun 04 04:19
    CLAassistant commented #4082
  • Jun 04 03:25
    kellyjonbrazil synchronize #4089
  • Jun 04 00:26
    kellyjonbrazil synchronize #4089
  • Jun 04 00:17
    tldr-bot commented #4089
  • Jun 04 00:16
    CLAassistant commented #4089
  • Jun 04 00:16
    CLAassistant commented #4089
  • Jun 04 00:16
    kellyjonbrazil opened #4089
  • Jun 03 14:02
    zdroid synchronize #4083
  • Jun 03 13:56
    stets review_requested #4083
Starbeamrainbowlabs
@sbrl
I'd have locked it as too heated, but spam works too
Zlatan Vasović
@zdroid
Right, that would have been better. I think I clicked the first thing that came to my mind.
Some of kolokd's comments are actually insightful (saw them in some repositories that I watch). It may just be the case kolokd is very young and impulsive.
Starbeamrainbowlabs
@sbrl
Yeah, it can be difficult in such situations - I've been there before.
Perhaps, yeah. Perhaps some comments they make we can reason with, and only delete / lock later when it gets too heated
Matthew Peveler
@MasterOdin
@sbrl @agnivade were you folks going to reach out to @felixonmars or do you want me?
Starbeamrainbowlabs
@sbrl
I thought @agnivade was going to do it
Lucas Gabriel Schneider
@schneiderl
Hello,
I've been out for a few weeks now as I was going through a lot of personal problems.
I'm now getting back to contributing to tldr and hope everyone is doing alright on this dark times we are living.
Starbeamrainbowlabs
@sbrl
No problems @schneiderl - glad you're back :D
hope you're doing better now
Agniva De Sarker
@agnivade
Oh no sorry for the confusion. Please feel free to reach out to him.
Zlatan Vasović
@zdroid
https://github.com/tldr-pages/tldr-cpp-client
Can somebody proceed to rename this to tldr-c-client as it should be named?
GitHub sets the redirects so it isn't a breaking change
Owen Voke
@owenvoke
I'm happy to do that if it's ok with everyone. :+1:
Does someone want to prepare a PR for the Brew repository change as well?
Starbeamrainbowlabs
@sbrl
Ah yeah, I remember that one. Sure, let's go ahead with that change.
I can do it too if @owenvoke doesn't
A PR to the Brew repo sounds good too
Owen Voke
@owenvoke
Also, have the font and icons changed on GitHub?
(I've renamed that repo now) :slight_smile:
Starbeamrainbowlabs
@sbrl
Yeah, I've noticed that too @owenvoke!
They look better I think
Owen Voke
@owenvoke
Not entirely sure about the brew stuff, went to make a PR but it looks like the hash for the source download isn't right. I can update it I guess, but not sure that it ever worked (I guess most people wouldn't build from source).
Fixed the hash, and opened a PR :+1:
Homebrew/homebrew-core#55357
Starbeamrainbowlabs
@sbrl
Awesome!
Looks like 3 of their checked failed though
not sure what's up with that
Owen Voke
@owenvoke
stable: sha256 changed without the version also changing; please create an issue upstream to rule out malicious circumstances and to find out why the file changed.
Ah, that's because I fixed the sha256 hash that wasn't working.
Starbeamrainbowlabs
@sbrl
Ah, I see
So it looks like merging is going to be more complicated.
Starbeamrainbowlabs
@sbrl
First! I've opened tldr-pages/.github#1
The very first PR on the .github repo
Achievement get :P
Starbeamrainbowlabs
@sbrl

Comment on that Homebrew issue:

If it isn't currently building, was the version retagged? And if so, why?

Unfortunately I don't know enough to answer
Matthew Peveler
@MasterOdin
maybe easiest thing would be to cut a release with the stuff @zdroid merged today and change the hash + version at the same time, avoid the whole problem
Starbeamrainbowlabs
@sbrl
Yeah
That sounds like a plan @MasterOdin
Zlatan Vasović
@zdroid
By the way, the C client is very far behind the other clients
It hasn't been maintained for a long while
It even has some failed-to-rename-a-directory bugs
Matthew Peveler
@MasterOdin
assuming that Felix does not respond (I'll send a bump email in a few days), the next option I suppose would be https://www.python.org/dev/peps/pep-0541/ and attempt to reclaim tldr via PyPI support
though that's another 6 week wait for them to attempt contact
Starbeamrainbowlabs
@sbrl
Right. Is there an issue open for this @MasterOdin? It's sounding like we might need one....
Matthew Peveler
@MasterOdin
Not yet, was going to give @felixonmars some more time to respond. Will also open an issue first on the tldr-python-client repo as well as that might be a way to ping them
Starbeamrainbowlabs
@sbrl
Ok, sure thing
Zlatan Vasović
@zdroid
Python client's v1.0 has just been published :tada:
Starbeamrainbowlabs
@sbrl
:tada: :confetti_ball:
Owen Voke
@owenvoke
Also, just a heads up. Homebrew/homebrew-core#55357 was merged, so now it's using the right links and can be built from source in Brew.
Starbeamrainbowlabs
@sbrl
:tada: