- User Since
- May 5 2017, 8:22 PM (66 w, 3 d)
I may very well be wrong but, I believe the reason this package has sat in the backlog for so long is that WireGuard is headed towards inclusion in the Kernel which would likely mean that we wouldn't need to package it separately for the Solus Repository.
Sun, Aug 12
@sunnyflunk thank you for fixing this very nit picky issue! Means a lot!
Fri, Aug 10
Sorry, I don't mean the actual package but, specifically this revision isn't showing up in the Phabracator atom repository. The last listed commit is 1.28.2.
Is there any reason this patch isn't showing up in the atom repository?
Sat, Aug 4
Mon, Jul 23
Sun, Jul 22
Thu, Jul 19
Tue, Jul 17
- Updated license to comply with SPDX 3.0
- Replaced %installroot% with $installdir and %version% with $version.
Mon, Jul 16
Jul 11 2018
Hey debug, just letting you know that version 1.28.1 has come out since you submitted this patch. Also, I would change the version from '1.28.0' to 1.28.0.
Jun 29 2018
Jun 20 2018
- Updated description to fix new line mess and updated source to mirror
- Removed .desktop file as one is now provided within the source code
- updated GPL-3.0 license to comply with SPDX 3.0
- Update LGPL license to comply with SPDX 3.0
Jun 19 2018
- Updated license to comply with SPDX 3.0
No problem, thanks for the licensing update. I actually read up on this a couple of days ago after seeing it discussed in IRC. I'll have this rebuilt and submitted in just a minute :)
Sorry about that, missed it when I updated the license.
- Rebuild to update pspec licenses
I used ./autogen.sh rather than %autogen while building because their script does not understand prefix=usr and fails when using %autogen.
Jun 18 2018
Jun 15 2018
Jun 14 2018
Jun 4 2018
@JoshStrobl I'd be happy to maintain this package.
May 30 2018
May 25 2018
Apr 30 2018
Apr 28 2018
- Fixed licenses and removed unnecessary build dependency
Apr 5 2018
- Downgraded release number from 10 to 9 so that it will be continuous from the last release.
Apr 3 2018
Apr 2 2018
This was still present for me in 1.4.4 after upgrading from 22.214.171.124179 until I deleted the configuration files and signed in again.
Mar 24 2018
Mar 9 2018
Mar 8 2018
Sorry about that weird formatting. Is there any reason that would be caused by the updatePackage script?
fixed install section formatting
Mar 3 2018
Thanks for the help! Sorry about the format of the description before.
Update to 1.1.10 and LGPL-2.1-or-later
Feb 19 2018
There are still errors when trying to build this application from source. However, I have submitted an update (D2334) using the pre-compiled .deb so that people can continue using mailspring while these upstream issues are worked out. Thanks everyone for your patience!
Sorry about the long changelog I wasn't sure if I should summarize it or not. Thanks for letting me know :)
Hi there, I just submitted the updated version D2326.
Feb 6 2018
The issue appears to occur because npm is unable to install a specific dependency (babel-preset-electron) from the author's git repository. I'm currently following the reported bug on github. Sorry for the long wait and thanks for your patience.
Jan 26 2018
There aren't necessarily any functionality drawbacks of using the snap. Currently, snaps don't yet support system themes which makes them often look very out of place. It's really just a personal decision. You are able to install both at the same time however, they won't use the same settings/accounts because a snap runs in a sandbox environment.
Jan 17 2018
Jan 14 2018
I can confirm this issue with my brother printer (HL-L2340DW). Also if it helps, this appears to only be a Solus issue as I tested Fedora and was able to print normally.
@JoshStrobl Reported the bug upstream.
Hi everyone, it appears that the latest version of nodejs (8.9.4) fails to download some of the required assets for mailspring when running npm.
npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha1-QFUCsAfzGcP0cXXER0UnMA8qta0= integrity checksum failed when using sha1: wanted sha1-QFUCsAfzGcP0cXXER0UnMA8qta0= but got sha512-zr6QQnzLt3Ja0t0XI8gws2kn7zV2p0l/D3kreNvS6hFZhVU5g+uY/30l42jbgt0XGcNBEmBDGJR71J692V92tA==. (260 bytes) npm WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
I just rebuilt mailspring locally against nodejs (8.9.3) and the app opens without any problems. Is there anyway that for a short term fix mailspring can be built against 8.9.3 instead of 8.9.4? How would I specify that in the package.yml file? For a long term fix, I'll make sure to publish this issue upstream. Also has anybody else reported errors with nodejs and npm? (Is this affecting other builds?)