naris Posted June 30, 2016 Report Share Posted June 30, 2016 Ubuntu 16.04 will not accept the plastic repos, it complains that: W: https://www.plasticscm.com/plasticrepo/plasticscm-common/Ubuntu_14.04/./Release.gpg: Signature by key FC547B45E1BB2D5BA32CFB6A9A847BB1704CBB6B uses weak digest algorithm (SHA1)W: https://www.plasticscm.com/plasticrepo/plasticscm-latest/Ubuntu_14.04/./Release.gpg: Signature by key BEA0651E0EE3CBC4CF25092A3A8583CE515E508F uses weak digest algorithm (SHA1)E: Failed to fetch No Hash entry in Release file /var/lib/apt/lists/partial/www.plasticscm.com_plasticrepo_plasticscm-common_Ubuntu%5f14.04_._Release which is considered strong enough for security purposesE: Failed to fetch No Hash entry in Release file /var/lib/apt/lists/partial/www.plasticscm.com_plasticrepo_plasticscm-latest_Ubuntu%5f14.04_._Release which is considered strong enough for security purposesE: Some index files failed to download. They have been ignored, or old ones used instead. Update: I see now I already posted about this a while ago in installation and that I should just download the client zip file. I have done that and it works. However, it would be much better if the ubuntu package could be updated to be signed with a valid key. Having an invalid installation package will most likely turn off most people evaluating plastic on linux and prevent them from considering it Link to comment Share on other sites More sharing options...
manu Posted July 1, 2016 Report Share Posted July 1, 2016 Hi naris, it's in our roadmap to support the new apt-get version As you said, installing Plastic SCM using the binaries over an existent installation should work just fine. Link to comment Share on other sites More sharing options...
jeffpk Posted March 16, 2017 Report Share Posted March 16, 2017 So its almost a year ,later and still this issue persists. Link to comment Share on other sites More sharing options...
manu Posted March 16, 2017 Report Share Posted March 16, 2017 I'm sorry we don't have full package support for Ubuntu. We'll try to make our best to support it soon. Meanwhile remember you can upgrade your installation by just copying the new binaries into your client and server directories. Link to comment Share on other sites More sharing options...
jeffpk Posted March 16, 2017 Report Share Posted March 16, 2017 Actually im attempting a new installation, but Im stuck on needing a graphical terminal to run your admin tool right now. Is there a pure commandline way to run the server? Thanks Link to comment Share on other sites More sharing options...
calbzam Posted March 16, 2017 Report Share Posted March 16, 2017 In order to configure the server, you can run "clconfigureserver". If you want to manage users, you can run "umtool". Do you still need the admintool for a different purpose? Regards, Carlos. Link to comment Share on other sites More sharing options...
jeffpk Posted March 16, 2017 Report Share Posted March 16, 2017 No those should do fine I think... Link to comment Share on other sites More sharing options...
trx Posted April 28, 2017 Report Share Posted April 28, 2017 On 16.3.2017 at 5:46 PM, manu said: I'm sorry we don't have full package support for Ubuntu. We'll try to make our best to support it soon. Meanwhile remember you can upgrade your installation by just copying the new binaries into your client and server directories. Is there any news or time-frame when plasticSCM will support ubuntu 16.04 new apt-get version? Link to comment Share on other sites More sharing options...
manu Posted April 28, 2017 Report Share Posted April 28, 2017 Yes! It's almost ready! We expect to have it ready for next week. Link to comment Share on other sites More sharing options...
wnicholls Posted May 4, 2017 Report Share Posted May 4, 2017 Great great news. Meanwhile the instructions at https://www.plasticscm.com/plastic-for-linux/ubuntu-16.html allowed me to get gtkplastic working on Ubuntu 16.10, with a few minor issues. Of course ubuntu is now 17.04, I'm sure you'll test with that. Link to comment Share on other sites More sharing options...
manu Posted May 4, 2017 Report Share Posted May 4, 2017 Yes, we'll test it too. I know I said it would be ready for this week but we faced issues and we cannot publish it yet hopefully next week everything will be ready. Link to comment Share on other sites More sharing options...
mig Posted May 17, 2017 Report Share Posted May 17, 2017 Hello everyone! I'm really happy to inform you that we've upgraded our repositories to be compatible with Ubuntu 16.04 or later! The repository signatures now use digest algorithm SHA-256. Everything should be back to normal now. Regards, Miguel Link to comment Share on other sites More sharing options...
jonask Posted May 18, 2017 Report Share Posted May 18, 2017 It does not work for me, I get the following errors: sudo apt-get update Hit:1 http://ppa.launchpad.net/cginternals/ppa/ubuntu zesty InRelease Get:2 http://security.ubuntu.com/ubuntu zesty-security InRelease [89,2 kB] Hit:3 http://se.archive.ubuntu.com/ubuntu zesty InRelease Ign:4 https://www.plasticscm.com/plasticrepo/plasticscm-common/Ubuntu_14.04 ./ InRelease Hit:5 http://se.archive.ubuntu.com/ubuntu zesty-updates InRelease Ign:6 https://www.plasticscm.com/plasticrepo/plasticscm-latest/Ubuntu_14.04 ./ InRelease Hit:7 https://www.plasticscm.com/plasticrepo/plasticscm-common/Ubuntu_14.04 ./ Release Hit:8 https://www.plasticscm.com/plasticrepo/plasticscm-latest/Ubuntu_14.04 ./ Release Hit:9 http://se.archive.ubuntu.com/ubuntu zesty-backports InRelease Get:10 https://www.plasticscm.com/plasticrepo/plasticscm-common/Ubuntu_14.04 ./ Release.gpg [481 B] Ign:10 https://www.plasticscm.com/plasticrepo/plasticscm-common/Ubuntu_14.04 ./ Release.gpg Fetched 89,7 kB in 2s (42,4 kB/s) Reading package lists... Done W: GPG error: https://www.plasticscm.com/plasticrepo/plasticscm-common/Ubuntu_14.04 ./ Release: The following signatures were invalid: FC547B45E1BB2D5BA32CFB6A9A847BB1704CBB6B W: The repository 'https://www.plasticscm.com/plasticrepo/plasticscm-common/Ubuntu_14.04 ./ Release' is not signed. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: No Hash entry in Release file /var/lib/apt/lists/www.plasticscm.com_plasticrepo_plasticscm-common_Ubuntu%5f14.04_._Release which is considered strong enough for security purposes If I only add plasticscm-latest it works but plasticscm-common does not work at all. Edit: I am using Xubuntu 17.04. Link to comment Share on other sites More sharing options...
manu Posted May 18, 2017 Report Share Posted May 18, 2017 Sorry! Some files were not correctly uploaded to the public repository. Now you'll be able to install it correctly. Link to comment Share on other sites More sharing options...
jonask Posted May 18, 2017 Report Share Posted May 18, 2017 Thanks, now it seems to be working fine. Link to comment Share on other sites More sharing options...
manu Posted May 22, 2017 Report Share Posted May 22, 2017 Perfect! Link to comment Share on other sites More sharing options...
wnicholls Posted May 27, 2017 Report Share Posted May 27, 2017 I think I can see why "plasticscm-latest" worked for jonask and "common" did not. Neither work for me today because the keys had expired. Here's the an excerpt from running apt-key list on my machine (*buntu 17.04) pub rsa2048 2015-01-12 [SC] [expired: 2017-03-22] uid [ expired] plasticscm-common OBS Project <plasticscm-common@obs2.codicefactory.com> pub rsa2048 2015-02-13 [SC] [expired: 2017-04-23] uid [ expired] plasticscm-latest OBS Project <plasticscm-latest@obs2.codicefactory.com> Top one is a red herring. Other two dates are the two plasticscm keys. Note latest expiring later. Fix with: wget https://www.plasticscm.com/plasticrepo/plasticscm-common/Ubuntu_14.04/Release.key -O - | sudo apt-key add - wget https://www.plasticscm.com/plasticrepo/plasticscm-common/Ubuntu_14.04/Release.key -O - | sudo apt-key add - These update keys won't expire until June 2019. Link to comment Share on other sites More sharing options...
manu Posted May 29, 2017 Report Share Posted May 29, 2017 Hi! Thank you for pointing the issue with the certificates, but I'm afraid the issue with Jonas installation was a partial upload to our public repositories, it was out fault. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.