-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade(package): Bump electron-builder 19.9.1 -> 19.40.0 #1905
Conversation
This currently fails for deb packages due to
|
This introduces a massive chunk of changes to |
This isn't actually even working for deb packages atm; and I haven't gotten it to work so far, let alone figured out what exactly is causing fpm to explode |
48623d9
to
c94dd10
Compare
@@ -12,6 +12,10 @@ RUN echo "deb http://archive.ubuntu.com/ubuntu precise-backports main restricted | |||
RUN echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list | |||
<% } %> | |||
|
|||
# Workaround: Install a newer version of `tar` to make fpm in electron-builder work again | |||
RUN echo "deb http://ftp.de.debian.org/debian wheezy main contrib non-free" >> /etc/apt/sources.list |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we just use http://ftp.debian.org/
as in the previous lines, rather than selecting the de
-specific subdomain?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
@@ -43,6 +47,10 @@ RUN apt-get update \ | |||
zip \ | |||
rpm | |||
|
|||
# Workaround: Install a newer version of `tar` to make fpm in electron-builder work again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO these two 'Workaround' blocks should only be run in the architecture == 'i686'
and architecture == 'x86_64'
Dockerfiles - they're not needed in the architecture == 'armv7hf'
Dockerfile as that uses a newer base-image and so the workaroud would actually downgrade the version of tar
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something like
<% if (architecture == 'i686' || architecture == 'x86_64') { %>
...
<% } %>
should do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
c94dd10
to
918f7eb
Compare
@@ -14,7 +14,7 @@ RUN echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/so | |||
|
|||
# Install dependencies | |||
RUN apt-get update \ | |||
&& apt-get install -y \ | |||
&& apt-get install --force-yes -y \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this really needed at this point?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope not anymore, removed
@@ -43,6 +43,12 @@ RUN apt-get update \ | |||
zip \ | |||
rpm | |||
|
|||
# Workaround: Install a newer version of `tar` to make fpm in electron-builder work again | |||
RUN echo "deb http://ftp.de.debian.org/debian wheezy main contrib non-free" >> /etc/apt/sources.list |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we don't need the non-free
. We can also try to remove contrib
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, libacl1
is on main
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Is the new
to the Makefile, and then list EDIT: Hah, I guess the latest commit nullifies this comment ;-) |
918f7eb
to
de6849d
Compare
# Workaround: Install a newer version of `tar` to make fpm in electron-builder work again | ||
RUN echo "deb http://ftp.debian.org/debian wheezy main" >> /etc/apt/sources.list | ||
RUN echo "deb http://ftp.debian.org/debian wheezy-backports main" >> /etc/apt/sources.list | ||
RUN apt-get install --force-yes -y -t wheezy libacl1 && \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, you need an apt-get update
between modifying sources.list
and running apt-get install
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...and perhaps this should be done in a single-step RUN
command (just like the compiler-install step below), rather than as separate RUN
commands?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking more:
RUN echo -e "deb http://ftp.debian.org/debian wheezy main\ndeb http://ftp.debian.org/debian wheezy-backports main" >> /etc/apt/sources.list && \
apt-get update && apt-get install --force-yes -y -t wheezy libacl1 && \
apt-get install --force-yes -y -t wheezy-backports tar
But it probably makes little difference here.
Is it worth adding a note to the commit message about why we've put so much effort into upgrading |
@jhermsmeier Even though DMGs build fine, I get weird ABI issues when running this particular |
@jviotti out of curiosity, did you also try EDIT: Now that we've "solved" npm-shrinkwrapping, I wonder if electron-builder is going to become our new nemesis? ;-) |
I'm getting the same weird ABI error on 19.49.0.
…On Fri, Dec 15, 2017 at 05:49:21PM -0800, Andrew Scheller wrote:
@jviotti out of curiosity, did you also try `19.49.0` ?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#1905 (comment)
--
Juan Cruz Viotti
Software Engineer
|
Have you filed an upstream bug? ;) |
@jviotti can you post the relevant log of that ABI error? |
@jhermsmeier The CI services are showing the exact error I get: https://travis-ci.org/resin-io/etcher/jobs/312464338#L2132 |
@lurch See electron-userland/electron-builder#2260. Apparently the solution is:
|
Oh, I see – that's because the module's been compiled against Electron's ABI, while being invoked by Node during the build step. One way to get around this would be to use the Node version corresponding to Electron's Node (v7.9.0 in Electron v1.7.9), but that's not something we want to do I think (our build process should ideally be fairly independent of Node version). I'll downgrade electron-builder to 19.40.0 for now then. |
Change-Type: patch
Change-Type: patch
Change-Type: patch
ced6036
to
64a5ab2
Compare
...which says "The rabin dependency was added as part of commit 1dc2e49, so 19.36.0 onward exhibit this issue. (19.35.1 works)" ?? |
@lurch Yeah, but that version hangs on High Sierra with 100% CPU usage when building the DMG :( 19.40.0 works like a charm from all sides. I say lets upgrade to that, and let |
Ah, I missed that comment :D |
Change-Type: patch
Connects To: #1914