Clojure Q&A - Recent questions tagged github

Artifacts / SHA256 updated on August 26th

Tue, 03 Oct 2023 19:38:50 +0000

Hello Clojure community

I'm one of the Java buildpacks maintainers and we recently discovered a discrepancy in the releases for this repository: https://github.com/clojure/brew-install/

The issue is that releases artifacts seem to have been republished / repushed after their initial release, effectively overwriting tags and artifacts attached to it; but since the paketo buildpack for clojure rely on SHA256 signatures to make sure the archive is the one that we expected, it basically broke them.

For example, let's take release 1.11.1.1347 as an example.

in the clojure/brew-install/ repository, we can sha256 the archive (shasum -a 256 ~/Downloads/linux-install-1.11.1.1347.sh) to 73a780bac41fc43ac624973f4f6ac4e46f293fe25aa43636b477bcc9ce2875de

Weirdly enough though, this release dates back to August 26 whereas the commit was done on May 31st

on the other hand, the Paketo team has a different sha for the same script

We believe the user named puredanger has mass-overwritten Github releases, potentially changing content of the published releases, on August 26th; the reason to think this is to look at this releases page where all older releases (<1360) were updated

We just wanted to make sure this issue was known and, if possible, would not happen frequently since it can break downstream redistribution channels, such as Paketo buildpacks. (we just updated and released to one of the latest clojure release, but users set on older versions could be impacted)

Thank you!

How do i install Clojure on my Windows OS Laptop?

Tue, 04 Oct 2022 23:04:29 +0000

I need help on how to install and use my Clojure on my Windows Operating system.

I have found a program written in Clojure on Github. I want to run it on windows, how do that please?

Mon, 11 Jan 2021 18:34:25 +0000

Hi, I have NO programming experience at all, so would appreciate any help.

I downloaded a program written in Clojure from GitHub and want to run it on my Windows 10 laptop. It was in a zipped file and I unzipped it. The folder contains many elements, including .iml and.clj files

I obtained Clojure for windows via https://clojure.org and successfully installed it.

I then tried to run the program via Windows power Shell but I can't get it to start.

Any advice on this, please?

Thank you.

No credentials found: deploying Clojars using a Github Workflow (Actions).

Tue, 21 Jan 2020 15:43:33 +0000

For some reason that I can't find, it's impossible for me to deploy Clojars using Github Actions. This is my script where I perform the action.

  - name: Deploy clojars
      run: |
        mkdir ~/.lein
        echo '{:user {} :auth {:repository-auth{#"clojars" {:username "${{ secrets.CLOJARS_USERNAME }}" :password "${{ secrets.CLOJARS_PASSWORD }}" :sign-releases false }}}}' > ~/.lein/profiles.clj
        lein deploy clojars

He's always telling me he can't find the credentials.

No credentials found for clojars
    See `lein help deploying` for how to configure credentials to avoid prompts.
    Username: LEIN IS UNABLE TO TURN OFF ECHOING, SO THE PASSWORD IS PRINTED TO THE CONSOLE
    Password: Created /home/runner/work/tadam-core/tadam-core/target/tadam-core-0.3.0.jar
    Wrote /home/runner/work/tadam-core/tadam-core/pom.xml
    Need to sign 2 files with GPG
    [1/2] Signing /home/runner/work/tadam-core/tadam-core/target/tadam-core-0.3.0.jar with GPG
    gpg: directory '/home/runner/.gnupg' created
    gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
    gpg: no default secret key: No secret key
    gpg: signing failed: No secret key
    Could not sign /home/runner/work/tadam-core/tadam-core/target/tadam-core-0.3.0.jar
    gpg: directory '/home/runner/.gnupg' created
    gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
    gpg: no default secret key: No secret key
    gpg: signing failed: No secret key
    
    
    See `lein help gpg` for how to set up gpg.
    If you don't expect people to need to verify the authorship of your jar, you
    can add `:sign-releases false` to the relevant `:deploy-repositories` entry.
    ##[error]Process completed with exit code 1.