Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 21:04
    ferventcoder commented #645
  • Jan 31 16:59
    ferventcoder commented #645
  • Jan 31 16:59
    ferventcoder labeled #645
  • Jan 31 16:55
    ferventcoder closed #645
  • Jan 31 16:50
    ferventcoder commented #645
  • Jan 31 16:50
    ferventcoder edited #646
  • Jan 31 16:50

    ferventcoder on master

    (GH-645) Add ContactAdmins view… Merge pull request #646 from de… (compare)

  • Jan 31 16:50
    ferventcoder closed #646
  • Jan 31 01:56
    ferventcoder commented #613
  • Jan 30 19:05
    designxsteph synchronize #644
  • Jan 30 19:04
    designxsteph synchronize #611
  • Jan 30 17:18
    pauby commented #643
  • Jan 30 17:18
    designxsteph edited #646
  • Jan 30 16:55
    JourneyOver commented #645
  • Jan 30 16:21
    designxsteph edited #646
  • Jan 30 15:50
    designxsteph review_requested #646
  • Jan 30 15:46
    designxsteph labeled #645
  • Jan 30 15:46
    designxsteph labeled #645
  • Jan 30 15:45
    designxsteph assigned #645
  • Jan 30 15:45
    designxsteph edited #646
Gary Ewan Park
@gep13
@boubou if you follow the links for each package, you will find that they are actually two different applications.
They derive from each other, but they are two different implementations.
I would ask that you don't use phrases like this:
do you do some check before approuve packages ?
They don't help the community in any way
If you have a problem with an individual package, speak to the maintainers.
But I would ask that you be more polite to them than you have been here.
Sébastien Boulianne
@boubou
  1. Most maintainers dont answer their emails or messages
Like the maintainer of the package windows-repair-toolbox
I requested to be a maintainer of that package many times
the maintainer never answer any tickets, issues, messages etc
If I have something to discuss, where should I write it ?
Sébastien Boulianne
@boubou
from what I see, chocolatey popularity is RAISE up a lot
there a ton of packages
Gary Ewan Park
@gep13
Regarding windows-repair-toolbox, the maintainer replied to you, but you haven't replied to him again. Do you think you can follow up there?
You could raise a PR into the repository to fix the issue.
I don't see the point in replacing the maintainer of a package when they are currently active on the site.
overag3
@overag3
Hi all, anyone to approve my package https://chocolatey.org/packages/geogebra-classic.install ? Thanks
Sébastien Boulianne
@boubou

Regarding windows-repair-toolbox, the maintainer replied to you, but you haven't replied to him again. Do you think you can follow up there?

I didnt see any notification about that!

Sébastien Boulianne
@boubou
Sry, I answered
overag3
@overag3
@mwallner Thank you ;-)
Sébastien Boulianne
@boubou
@gep13 , thx... The maintainer of windows-repair-toolbox added me as a maintainer on the package
I will push a new version now
Sébastien Boulianne
@boubou
Attempting to push windows-repair-toolbox.3.0.2.1.nupkg to https://push.chocolatey.org/
An error has occurred. It's possible the package version already exists on the repository.
yes but its rejected
how can I push another version ?
Gary Ewan Park
@gep13
@boubou is 3.0.2.2 the actual version number of the application?
If not, I would suggest that we don't move forward with that
Instead, we can unreject the package version that you do want to push
Based on the website, looks like the actual application version is 3.0.2.1
I would suggest that we unreject that package version, and then you will be able to push a package with that version number
Let me know how you would like to proceed
Sébastien Boulianne
@boubou
I tried to do a workaround
I didnt think there is a solutions
please unreject the 3.0.2.1
Blisk
@Blisk
hi, can you update open-shell to latest, please?
chtof
@chtof
Hi @blisk , not sure the maintainer of the package read regularly this gitter channel and even, it's better to send a message via the Contact Maintainers link of the Chocolatey package https://chocolatey.org/packages/open-shell/ContactOwners and/or to post a message via Disqus. This new version was released only 4 hours ago and the maintainers of the Chocoloatey community packages are volunteers, so also, you should wait a little bit (my advice is 2 or 3 days) before contacting the maintainer. If the package is not updated after 2 or 3 days, you can inform him why it's important for you to have quickly an update and maybe, he will try to find a solution to update quickly this package. Thank you for your comprehension.
Paul Broadwith
@pauby
@chefhabitat Just coming back to your response. What you've done in your example is pass package parameters to the package on the command line. What you have done is correct and should work. So I'm unsure what the issue is?
Timothy Carter
@its_me_timmy_c_twitter
If I'm hosting my own Chocolatey Server, do I handle API keys/authentication directly through that, or is that an IIS layer item?
Paul Broadwith
@pauby
@its_me_timmy_c_twitter Chocolatey Server handles that.
Just to be clear when you say Chocolatey Server you do mean Simple.Server?
Timothy Carter
@its_me_timmy_c_twitter
That's correct!
Paul Broadwith
@pauby
Then what I said is correct! :smile:
Timothy Carter
@its_me_timmy_c_twitter
@pauby Great, thank you!
Paul Broadwith
@pauby
:+1:
Sébastien Boulianne
@boubou
Hi sir
Sébastien Boulianne
@boubou
I pmed you Paul! ;)
Thanks in advance for your answer!