Gpgtools Installer → 20120317

Comments and changes to this ticket

• You flagged this item as spam.
  

  Alex (via GPGTools) January 20th, 2011 @ 10:02 AM

  • State changed from “new” to “open”

  [bulk edit]

• You flagged this item as spam.
  

  Alex (via GPGTools) February 14th, 2011 @ 08:08 AM

  • State changed from “open” to “hold”

  Waiting for the other projects (in particular for GPGMail - in particular issue 107 and 103)

• You flagged this item as spam.
  

  Beat Stehrenberger February 15th, 2011 @ 11:23 AM

  Please consider suggestions in issue #44 (set to invalid)

• You flagged this item as spam.
  

  Alex (via GPGTools) February 15th, 2011 @ 05:44 PM

  • Assigned user cleared.

  That's true - issue #44 should also be considered. Thank you.

• You flagged this item as spam.
  

  Alex (via GPGTools) May 17th, 2011 @ 03:32 PM

  • Milestone cleared.
  • Importance changed from “High” to “”

• You flagged this item as spam.
  

  Alex (via GPGTools) May 18th, 2011 @ 07:30 PM

  • Assigned user set to “time2ride”

  From "anonymous":

  Update:
  System install for GPGMail 1.3.3 was much harder than for version 1.3.1.
  The installer detected that the mail bundle was installed in /L/M/B &
  requested admin privilege.
  It then deleted version 1.3.1 & quit without installing version 1.3.3

  Speculation:
  The installer detected the installation in /L/M/B & escalated to {admin}.
  It succeeded in deleting 1.3.1 from /L/M/B because I had, as {admin}
  manually placed 1.3.1 there.
  It then attempted to write 1.3.3 to {$HOME}/L/M/B, which is not read
  accessible to {admin} and failed.

  Workaround:
  I installed GPGMail 1.3.3 on a machine that did not have GPG.
  I was then able to manually move the bundle to those machines that do
  have GPG.

  Request:
  Please increase the working priority for this bug.
  Not everyone will be able to borrow a computer that does not have GPG in
  order to complete the install.

• You flagged this item as spam.
  

  Alex (via GPGTools) May 19th, 2011 @ 09:13 AM

  (from [f4353e36b181c0fdc05ad46801ab7c43e30b787a]) Installer now respects the old location of GPGMail [#36] https://github.com/GPGTools/GPGTools/commit/f4353e36b181c0fdc05ad46...

• You flagged this item as spam.
  

  Alex (via GPGTools) May 20th, 2011 @ 12:28 AM

  (from [08760176518aaab2ba3849fc6adaf0af8856a7a8]) cleanup [#36] https://github.com/GPGTools/GPGTools/commit/08760176518aaab2ba3849f...

• You flagged this item as spam.
  

  Alex (via GPGTools) June 27th, 2011 @ 12:23 AM

  • Assigned user cleared.

  see #66

• You flagged this item as spam.
  

  Alex (via GPGTools) January 1st, 2012 @ 01:40 PM

  • Assigned user set to “Alex (via GPGTools)”
  • State changed from “hold” to “open”
  • Milestone set to “20120317”
  • Importance changed from “” to “High”

  Planned for Q1/12

• You flagged this item as spam.
  

  Alex (via GPGTools) January 3rd, 2012 @ 03:50 PM

  • State changed from “open” to “fixed”

  GPGMail will work fine now with the next release.

• You flagged this item as spam.
  

  Alex (via GPGTools) March 17th, 2012 @ 02:40 PM

  • State changed from “fixed” to “released”
  • Importance changed from “High” to “Low”

  [bulk edit]