Package Details: smartgit 20.2.4-1

Package Actions

• View PKGBUILD / View Changes

Dependencies (4)

Smartgit, Ainring. SmartGit is a Git client with support for several hosting providers, e.g. Bitbucket and GitHub. It runs on Linux, macOS and Windows. SmartGit does not recognize that the system Git/SSH wants to. Unread, SmartGit & Smartcards (Yubikeys, 2FA) Hi Michael, This is expected behavior. SmartGit does not.

• desktop-file-utils(desktop-file-utils-git)
• git(git-git)
• gtk3(gtk3-cosy, gtk3-adwaita-3-32-git, gtk3-git, gtk3-ubuntu, gtk3-no_deadkeys_underline, gtk3-classic, gtk3-patched-filechooser-icon-view, gtk3-typeahead)
• mercurial(mercurial-hg, mercurial-stable-hg)(optional) – hg repositories support

Pierrre commented on 2020-08-17 13:32

alyst commented on 2020-08-17 13:06

I've updated GTK requirement to gtk3 and dropped java-runtime dependency.Let me know if you have troubles with the package.

paro commented on 2020-08-15 13:47

The java-runtime requirement seems useless in my opinion too.Also, why is gtk2 still needed? Shouldn't it be an optional dependency for retro-compatibility?For me, smartgit works fine with gtk3 only (and their embedded jre).

Pierrre commented on 2020-04-07 14:00

How to sync gmail contacts with outlook. @alyst same comment about the java requirement.This package requires java-rutntime, but it's not useful because Smartgit already provides a JRE.Actually, even if you install java-runtime, Smatgit will still continue to use his own JRE.Maybe there is an option to run Smartgit with the system JRE, but I don't know it.Anyway, Martgit runs just fine with the embedded JRE.AFAIK last time I checked, there was some incompatibility with the latest JRE, that's why they embed a JRE.

Could you remove the java-runtime requirement please ?

alyst commented on 2019-09-16 12:50

Note that currently there's a discrepancy between the checksum of .tar.gz that you download and the checksum that is reported on syntevo.com (that's why I was postponing the update to 19.1.3). I hope it's just some minor glitch :)

kmvan commented on 2019-09-16 02:25

leo.lolcat commented on 2019-08-20 13:52

cknoblauch commented on 2019-08-19 19:30

Best compact suvs 2013. I fixed the file falidation error by removing the /tmp/pamac-build/smartgit directory. The package was then redownloaded and installed correctly.

alyst commented on 2019-08-19 09:37

@leo.lolcat Unfortunately, failed checksums is a frequent situation for smartgit. Recently Syntevo started to silently update smartgit package without bumping the version number. So it's not a MITM attack or anything like that, just the new package build (e.g. in this case it was build #14173 -> build #14176 upgrade).

afsn commented on 2019-08-18 13:50

Error on check sha1sums (v19.1.1).

Solved:Edit PKGBUILD and change the first sha1sums value to: 2bde6ba14d69918139e8d1246aa5d1e9a4546977

Single Sign-On (SSO) in Repository

You can access the Repository providers that use authentication protocol for single sign-on (SSO) by authenticating through an identity provider (IdP).SSO helps you maintain control of your identity and contributions, while giving organizations a centralized and secure way of controlling access to their resources on Repository. The flow diagram below shows the steps used for authenticating the user.

Smartgit Tutorial

• User tries to Login into repository providers like GitHub, Bitbucket, SmartGit, etc.
• The Repository sends the request to the miniOrange Identity Provider for authenticating the user. miniOrange supports different authentication protocols - SAML, Oauth, OIDC, WS-Fed and many more. The SSO tool requests an encrypted token from the Identity Provider.
• Identity Provider intercepts the request and sends a response to the repository provider after authenticating the user credentials.
• The encrypted authentication token generated from the Identity Provider allows the user to login in a repository provider. The user gets logged in and can access the repository contents.

Single Sign-On (SSO) in SmartGit

miniOrange helps you to log in into SmartGit application. SmartGit supports Oauth authentication protocol for Signle Sign-On with the identity providers. User will put on his app IdP credentials and will be authenticated to access the repository.

• The user tries to Login into the SmartGit desktop application using Identity Provider credentials.
• SmartGit sends a request to the repository provider.
• Repository Provider intercepts the request and then forwards it to the Identity Provider through API calls.
• Identity Provider sends a response to the repository provider after authenticating the user credentials. It generates the authentication token which is required for SSO.
• The repository provider reads the response and forwards it to the SmartGit.
• The authentication token generated allows the user to login into the SmartGit application.

GitHub Enterprise Integration

Authenticating to a GitHub Enterprise instance is slightly different than to github.com due to the nature of OAuth. Basically you have two options:

• using Personal Access Tokens: this approach can be performed by an individual user without needing administrative rights for the GitHub Enterprise instance. It's recommended if only a small number of your GitHub Enterprise users are using SmartGit
• configuring a Developer Application: this approach requires administrative rights for the GitHub Enterprise instance and changes to the SmartGit System Properties (which can be done on an administrative level for all users, too). It's recommended if you have a large number of SmartGit users.

Personal Access Token

Personal access tokens are working for GitHub Enterprise as well as for github.com. To create a personal access token, go to your Account settings and select Personal Access Tokens. Invoke Generate New Token, enter SmartGit for the Token Description and for Select scopes select the repo scope and the read:org scope.

After confirming with Generate Token, you will see the new token in your list of tokens. Copy the token to the clipboard and paste it into the Token field of SmartGit's GitHub configuration dialog.

Developer Application

To use SmartGit's OAuth authentication with your GitHub Enterprise instance, SmartGit has to be configured as Developer Application in your GitHub Enterprise instance. This can be done by every GitHub Enterprise user, from the Personal Settings, OAuth Applications, Developer Applications.

You have to provide an Application name, a Homepage URL and the Authorization callback URL to which GitHub Enterprise will redirect during authentication and pass the generated token to.

Smartgit Portable

Smartgit Mac Os

GitHub will automatically create a Client ID and a Client Secret which have to be passed to SmartGit using system properties smartgit.github.enterprise.oauth.id and smartgit.github.enterprise.oauth.secret. For the example application from the screenshot, this would be: