Jump to content

mig

Administrators
  • Content count

    79
  • Joined

  • Last visited

  • Days Won

    3

mig last won the day on September 27 2017

mig had the most liked content!

Community Reputation

4 Neutral

About mig

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2,448 profile views
  1. Hi @Ol' Nick, We released yesterday version 7.0.16.2613, which contains a fix for the issue your co-worker was experiencing. However, if you decide to install it you'll need to apply a temporary workaround to avoid a problem with visual components that we're fixing right now. You'll need to run directly the PlasticSCM app from a Terminal, executing this line:/ /Applications/PlasticSCM.app/Contents/MacOS/PlasticSCM Sorry for the inconveniences. We'll release a fix ASAP. Regards, Miguel
  2. El fix del problema con la vista de cambios pendientes en macOS fue liberado en la versión 7.0.16.2613. Sin embargo, aún es preciso un workaround temporal en macOS Mojave para solucionar un problema con componentes visuales en el que estamos trabajando mientras escribo estas líneas. Un saludo, Miguel
  3. Hi heshuimu, As I mentioned in your other thread, PlasticSCM is now operative in macOS using the workaround I detailed to get rid of the missing visual components issue. We'll let you know when this is fixed, but in the meantime that workaround should allow you to work with PlasticSCM for macOS. Regards, Miguel
  4. Hi heshuimu, I'm really sorry about this inconvenience. We detected this a few days back and we're working on it at the moment. As a workaround, you can run the PlasticSCM executable directly from a Terminal instead of double-clicking the app. Execute this at a terminal: /Applications/PlasticSCM.app/Contents/MacOS/PlasticSCM The GUI still doesn't support the Dark Theme, but this workaround will get you working if you turn on the Light Theme. We'll release a fix as soon as possible! Regards, Miguel
  5. mig

    Broken link in forum notification emails

    Hi @Wolfram, Yes, it seems to be just as you pointed out... We can't do a lot about it from our side 😔 We'll let you know if we get more info from them regarding this issue. Regards, Miguel
  6. mig

    cm fileinfo taking waaay too much time

    Hi Kris, To achieve the same results, I'd go with these two commands that will probably improve your process performance. First of all, to find out if a file is checked out you can run cm status --checkout path/to/saved/file --short That command will print out the file path if it's checked out, or will return without any output if it's not. Then, if the file isn't checked out, you can list the file locks using cm listlocks and then search the saved file path in the results. Could you please try those out and let us know the results? Thank you! Regards, Miguel
  7. mig

    New WebUI

    Hi Misieq, I'm happy to tell you that the functionality you request is already being developed! We'll add a "download" button in the file contents view (the page that appears whenever you click on a file in the file explorer). Also, we've already been notified about the main branch issue and the team is working on that as well Thanks for your feedback! Regards, Miguel
  8. mig

    New WebUI

    Hi Misieq, As you noticed, the new WebUI is in an early stage, so it ships with a really basic set of functionalities. However, adding new features is definitely in our roadmap, starting precisely with the repository browser! 😄 Please stay tuned to our release notes, I hope you'll find new interesting features soon enough. Regards, Miguel
  9. Hi Xorcist, If you want to completely remove all Plastic SCM packages, I recommend you to run this command: sudo apt-get remove --purge plasticscm-* That way you make sure all Plastic SCM packages are removed. Otherwise, removing plasticscm-complete would only remove that particular package (apt-get remove doesn't remove dependencies), which is just a metapackage to install all plasticscm-* stuff. You can then manually remove /opt/plasticscm5 and /var/lib/plasticscm, which are the directories where the binaries and database are stored. Of course, backup your data first! (Unless you explicitly want it to be gone) Is this helpful for your situation? Thanks! Regards, Miguel
  10. Hi Lorenzo, You just need to find your client configuration file, typically in %LOCALAPPDATA%\plastic4\client.conf or %PROGRAMFILES%\PlasticSCM5\client\client.conf and open it for edit. You'll find a <Language> tag with the current language value ('es' in your local machine, as you mentioned that the UI is displayed in Spanish). Just change it to 'en' and the GUI language will be English: <?xml version="1.0"?> <ClientConfigData xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Language>en</Language> <WorkspaceServer>...</WorkspaceServer> <!-- more settings --> </ClientConfigData>
  11. Hi, This issue is caused by GitHub having recently restricted inbound connection to use TLSv1.2. We've already fixed this issue and it will be published in the next release, so stay tuned! Regards, Miguel
  12. Also, could you describe us the crashes you mentioned? Is it the client crashing or the server? How do you reproduce the issue?
  13. Hi mengl, Each package manager tool uses a different syntax to install specific versions of packages. You can find detailed information about how to achieve this with apt-get here: https://askubuntu.com/questions/92019/how-to-install-specific-ubuntu-packages-with-exact-version I hope this answers your question! Regards, Miguel
  14. Hi trx, There are no current restrictions regarding reverse proxies. What you are trying to achieve is a great way to enable SSL access to the webadmin page indeed There must be something wrong, though... could you post your nginx configuration? Also, are there any messages in the Plastic SCM server log? Thank you! Regards, Miguel
  15. Hi Xorcist, As far as we know, no compatibility issues have been detected in Ubuntu 16.04+ using our 14.04 repository. Have you experienced any issues? What do you mean by red flags going up? Regards, Miguel
×