Commit Graph

19015 Commits

Author SHA1 Message Date
John Ericson
ca94de8c4c offrss: cc-wrapper can be relied on to export this env var 2017-06-28 18:21:05 -04:00
John Ericson
c4443d70df fbida: cc-wrapper can be relied on to export these env vars 2017-06-28 18:21:05 -04:00
John Ericson
a11426c523 ImageMagick: Don't use stdenv.cross
I'm guessing the salient aspect here is not cross compiling itself, but
just whether the host platform is MinGW, so I simplified the logic
accordingly
2017-06-28 18:20:38 -04:00
Will Dietz
a97c803b4b mendeley: ignore errors attempting to install link handler on startup
It's not critical functionality and AFAICT only fails in environments
that wouldn't benefit from "successfully" installing it anyway.

Fixes #24709
Fixes #24821
2017-06-28 17:05:11 -05:00
Robert Helgesson
fa6e946383
eclipse-plugin-jdt: 4.6.2 -> 4.7 2017-06-28 20:56:48 +02:00
Robert Helgesson
556a867186
eclipse-sdk: 4.6.2 -> 4.7 2017-06-28 20:56:48 +02:00
Robert Helgesson
0a52cc1851
eclipse-platform: 4.6.2 -> 4.7 2017-06-28 20:56:43 +02:00
Daniel Peebles
09194cafa8 Merge pull request #26937 from joachifm/lkl-4_11
lkl: 2017-03-24 -> 2017-06-27
2017-06-28 14:35:36 -04:00
Joachim Fasting
0bc3429e77
lkl: 2017-03-24 -> 2017-06-27
Now based on Linux 4.11
2017-06-28 20:14:00 +02:00
Joachim F
c7278cfc0b Merge pull request #26887 from taku0/thunderbird-bin-52.2.1
Thunderbird bin 52.2.1
2017-06-28 19:06:38 +01:00
Tim Steinbach
add90948bc
docker: 17.03.1-ce -> 17.03.2-ce 2017-06-28 12:49:59 -04:00
Shea Levy
24c59a4452 neuron: enable GUI 2017-06-28 11:59:54 -04:00
Thomas Tuegel
59f94b12f3
dropbox: 28.4.14 -> 29.4.20 2017-06-28 08:38:38 -05:00
Frederik Rietdijk
8a62a9b064 Merge pull request #26125 from volth/webkitgtk-naming
rename webkitgtk24x⇒webkitgtk24x-gtk3; webkitgtk2⇒webkitgtk24x-gtk2
2017-06-28 13:54:38 +02:00
Robert Schütz
1a7745d6ec dmensamenu: init at 1.0.0 2017-06-28 11:43:39 +02:00
Jörg Thalheim
ce88027294 jetbrains.gogland: 171.4694.35 -> 171.4694.61 2017-06-28 08:31:08 +01:00
Jörg Thalheim
f849eb2018 jetbrains.datagrip: 2017.1.4 -> 2017.1.5 2017-06-28 08:30:59 +01:00
Charles Strahan
8e73afb2e1 zoom-us: don't add mesa to the LD_LIBRARY_PATH
zoom-us was failing to launch under the proprietary nvidia drivers,
as described in the comments of #26596.

Closes #26916
2017-06-27 18:43:20 -04:00
Diego Pontoriero
5b90fa0151
terraform: 0.9.6 -> 0.9.9. 2017-06-27 15:04:11 -07:00
Karn Kallio
07dc20e436 kcachegrind : Fix build by adding missing dependencies. 2017-06-27 22:33:06 +02:00
Shea Levy
4d2597981d Partially revert "terraform: 0.9.4 -> 0.9.6."
Terraform point releases are significant changes, we need to keep old ones around

This reverts commit 6a27b46dee.
2017-06-27 16:26:07 -04:00
Karn Kallio
c710ddf7cd okteta : Fix build by adding missing dependencies. 2017-06-27 22:10:00 +02:00
Joachim F
2c30e5e754 Merge pull request #25441 from Hodapp87/draftsight
draftsight: init at 2017-SP1
2017-06-27 21:04:30 +01:00
Joachim F
bccd3feed2 Merge pull request #26450 from oxij/pkg/fix/tor-browser
firefoxPackages: tor-browser: use gtk2 by default (like tor-browser-bin does)
2017-06-27 20:41:27 +01:00
Joachim F
4e44b63892 Merge pull request #26453 from oxij/pkg/fix/ranger
ranger: add imagePreviewSupport option and make previews work out of the box
2017-06-27 20:40:57 +01:00
Karn Kallio
67e4072282 k3b : Fix build by adding missing dependencies. 2017-06-27 21:14:00 +02:00
Joachim F
c27fc66856 Merge pull request #26904 from Ma27/geogebra/make-language-configurable
geogebra: make `language` configurable
2017-06-27 16:21:00 +01:00
Joachim F
bcbf45ff1f Merge pull request #26886 from jonafato/remove-thunderbird-bin-updater
Remove old thunderbird-bin update script
2017-06-27 16:12:37 +01:00
Tim Steinbach
493ae24872 Merge pull request #26870 from lsix/update_nano
nano: 2.8.4 -> 2.8.5
2017-06-27 08:12:52 -04:00
Tim Steinbach
719b506bad Merge pull request #26803 from NeQuissimus/rkt_1_27_0
rkt: 1.26.0 -> 1.27.0
2017-06-27 08:09:40 -04:00
Michał Pałka
7b5d72ce04 xen: patch for XSAs: 216, 217, 218, 219, 220, 221, 222, and 224 (xen 4.8)
This commit contains security patches for xen 4.8. The patches
for XSA-216 applied to the kernel are omitted, as they are part of
80e0cda7ff.

XSA-216 Issue Description:

> The block interface response structure has some discontiguous fields.
> Certain backends populate the structure fields of an otherwise
> uninitialized instance of this structure on their stacks, leaking
> data through the (internal or trailing) padding field.

More: https://xenbits.xen.org/xsa/advisory-216.html

XSA-217 Issue Description:

> Domains controlling other domains are permitted to map pages owned by
> the domain being controlled.  If the controlling domain unmaps such a
> page without flushing the TLB, and if soon after the domain being
> controlled transfers this page to another PV domain (via
> GNTTABOP_transfer or, indirectly, XENMEM_exchange), and that third
> domain uses the page as a page table, the controlling domain will have
> write access to a live page table until the applicable TLB entry is
> flushed or evicted.  Note that the domain being controlled is
> necessarily HVM, while the controlling domain is PV.

More: https://xenbits.xen.org/xsa/advisory-217.html

XSA-218 Issue Description:

> We have discovered two bugs in the code unmapping grant references.
>
> * When a grant had been mapped twice by a backend domain, and then
> unmapped by two concurrent unmap calls, the frontend may be informed
> that the page had no further mappings when the first call completed rather
> than when the second call completed.
>
> * A race triggerable by an unprivileged guest could cause a grant
> maptrack entry for grants to be "freed" twice.  The ultimate effect of
> this would be for maptrack entries for a single domain to be re-used.

More: https://xenbits.xen.org/xsa/advisory-218.html

XSA-219 Issue Description:

> When using shadow paging, writes to guest pagetables must be trapped and
> emulated, so the shadows can be suitably adjusted as well.
>
> When emulating the write, Xen maps the guests pagetable(s) to make the final
> adjustment and leave the guest's view of its state consistent.
>
> However, when mapping the frame, Xen drops the page reference before
> performing the write.  This is a race window where the underlying frame can
> change ownership.
>
> One possible attack scenario is for the frame to change ownership and to be
> inserted into a PV guest's pagetables.  At that point, the emulated write will
> be an unaudited modification to the PV pagetables whose value is under guest
> control.

More: https://xenbits.xen.org/xsa/advisory-219.html

XSA-220 Issue Description:

> Memory Protection Extensions (MPX) and Protection Key (PKU) are features in
> newer processors, whose state is intended to be per-thread and context
> switched along with all other XSAVE state.
>
> Xen's vCPU context switch code would save and restore the state only
> if the guest had set the relevant XSTATE enable bits.  However,
> surprisingly, the use of these features is not dependent (PKU) or may
> not be dependent (MPX) on having the relevant XSTATE bits enabled.
>
> VMs which use MPX or PKU, and context switch the state manually rather
> than via XSAVE, will have the state leak between vCPUs (possibly,
> between vCPUs in different guests).  This in turn corrupts state in
> the destination vCPU, and hence may lead to weakened protections
>
> Experimentally, MPX appears not to make any interaction with BND*
> state if BNDCFGS.EN is set but XCR0.BND{CSR,REGS} are clear.  However,
> the SDM is not clear in this case; therefore MPX is included in this
> advisory as a precaution.

More: https://xenbits.xen.org/xsa/advisory-220.html

XSA-221 Issue Description:

> When polling event channels, in general arbitrary port numbers can be
> specified.  Specifically, there is no requirement that a polled event
> channel ports has ever been created.  When the code was generalised
> from an earlier implementation, introducing some intermediate
> pointers, a check should have been made that these intermediate
> pointers are non-NULL.  However, that check was omitted.

More: https://xenbits.xen.org/xsa/advisory-221.html

XSA-222 Issue Description:

> Certain actions require removing pages from a guest's P2M
> (Physical-to-Machine) mapping.  When large pages are in use to map
> guest pages in the 2nd-stage page tables, such a removal operation may
> incur a memory allocation (to replace a large mapping with individual
> smaller ones).  If this allocation fails, these errors are ignored by
> the callers, which would then continue and (for example) free the
> referenced page for reuse.  This leaves the guest with a mapping to a
> page it shouldn't have access to.
>
> The allocation involved comes from a separate pool of memory created
> when the domain is created; under normal operating conditions it never
> fails, but a malicious guest may be able to engineer situations where
> this pool is exhausted.

More: https://xenbits.xen.org/xsa/advisory-222.html

XSA-224 Issue Description:

> We have discovered a number of bugs in the code mapping and unmapping
> grant references.
>
> * If a grant is mapped with both the GNTMAP_device_map and
> GNTMAP_host_map flags, but unmapped only with host_map, the device_map
> portion remains but the page reference counts are lowered as though it
> had been removed. This bug can be leveraged cause a page's reference
> counts and type counts to fall to zero while retaining writeable
> mappings to the page.
>
> * Under some specific conditions, if a grant is mapped with both the
> GNTMAP_device_map and GNTMAP_host_map flags, the operation may not
> grab sufficient type counts.  When the grant is then unmapped, the
> type count will be erroneously reduced.  This bug can be leveraged
> cause a page's reference counts and type counts to fall to zero while
> retaining writeable mappings to the page.
>
> * When a grant reference is given to an MMIO region (as opposed to a
> normal guest page), if the grant is mapped with only the
> GNTMAP_device_map flag set, a mapping is created at host_addr anyway.
> This does *not* cause reference counts to change, but there will be no
> record of this mapping, so it will not be considered when reporting
> whether the grant is still in use.

More: https://xenbits.xen.org/xsa/advisory-224.html
2017-06-27 12:02:59 +00:00
Michał Pałka
9e6bfbb2f9 xen_4_8: init at 4.8.1
This commit adds the xen_4_8 package to be used instead of
xen (currently at 4.5.5):
 * Add packages xen_4_8, xen_4_8-slim and xen_4_8-light
 * Add packages qemu_xen_4_8 and qemu_xen_4_8-light to be used
   with xen_4_8-slim and xen_4_8-light respectively.
 * Add systemd to buildInputs of xen (it is required by oxenstored)
 * Adapt xen service to work with the new version of xen
 * Use xen-init-dom0 to initlilise dom0 in xen-store
 * Currently, the virtualisation.xen.stored option is ignored
   if xen 4.8 is used
2017-06-27 12:01:53 +00:00
Josef Kemetmueller
2cb5246dd8 gogs: 0.10.18 -> 0.11.19 2017-06-27 11:41:19 +00:00
Maximilian Bosch
9516bbf172
geogebra: make language configurable 2017-06-27 09:51:06 +02:00
Jon Banafato
d8e5c75f75 Remove old thunderbird-bin update script
`thunderbird-bin` appears to now use the
`maintainers/scripts/update.nix` script instead of this ruby script, so
the latter should be removed.
2017-06-26 19:54:24 -04:00
Frederik Rietdijk
9dbfd87ab6 Merge pull request #26849 from vbgl/skrooge-2.8
skrooge: 2.7.0 -> 2.8.1
2017-06-26 22:23:36 +02:00
Frederik Rietdijk
25b12febee Merge pull request #26857 from jerith666/krfb-qtx11extras
krfb: add new qtx11extras dependency
2017-06-26 22:16:28 +02:00
Vincent Laporte
ac83ef3994 glsurf: 3.3 -> 3.3.1 2017-06-26 19:24:33 +02:00
Lancelot SIX
1b792b4edf
nano: 2.8.4 -> 2.8.5
See http://lists.gnu.org/archive/html/info-gnu/2017-06/msg00012.html
for release information.
2017-06-26 11:01:55 +02:00
Nicolas Truessel
813feae594 chromium: 59.0.3071.86 -> 59.0.3071.109 2017-06-26 09:24:56 +02:00
Emmanuel Rosa
994998e475 thunderbird: 52.2.0 -> 52.2.1 2017-06-26 09:01:45 +02:00
Michał Pałka
80e0cda7ff xen: patch for XSAs: 216, 217, 218, 219, 220, 221, 222, and 224
XSA-216 Issue Description:

> The block interface response structure has some discontiguous fields.
> Certain backends populate the structure fields of an otherwise
> uninitialized instance of this structure on their stacks, leaking
> data through the (internal or trailing) padding field.

More: https://xenbits.xen.org/xsa/advisory-216.html

XSA-217 Issue Description:

> Domains controlling other domains are permitted to map pages owned by
> the domain being controlled.  If the controlling domain unmaps such a
> page without flushing the TLB, and if soon after the domain being
> controlled transfers this page to another PV domain (via
> GNTTABOP_transfer or, indirectly, XENMEM_exchange), and that third
> domain uses the page as a page table, the controlling domain will have
> write access to a live page table until the applicable TLB entry is
> flushed or evicted.  Note that the domain being controlled is
> necessarily HVM, while the controlling domain is PV.

More: https://xenbits.xen.org/xsa/advisory-217.html

XSA-218 Issue Description:

> We have discovered two bugs in the code unmapping grant references.
>
> * When a grant had been mapped twice by a backend domain, and then
> unmapped by two concurrent unmap calls, the frontend may be informed
> that the page had no further mappings when the first call completed rather
> than when the second call completed.
>
> * A race triggerable by an unprivileged guest could cause a grant
> maptrack entry for grants to be "freed" twice.  The ultimate effect of
> this would be for maptrack entries for a single domain to be re-used.

More: https://xenbits.xen.org/xsa/advisory-218.html

XSA-219 Issue Description:

> When using shadow paging, writes to guest pagetables must be trapped and
> emulated, so the shadows can be suitably adjusted as well.
>
> When emulating the write, Xen maps the guests pagetable(s) to make the final
> adjustment and leave the guest's view of its state consistent.
>
> However, when mapping the frame, Xen drops the page reference before
> performing the write.  This is a race window where the underlying frame can
> change ownership.
>
> One possible attack scenario is for the frame to change ownership and to be
> inserted into a PV guest's pagetables.  At that point, the emulated write will
> be an unaudited modification to the PV pagetables whose value is under guest
> control.

More: https://xenbits.xen.org/xsa/advisory-219.html

XSA-220 Issue Description:

> Memory Protection Extensions (MPX) and Protection Key (PKU) are features in
> newer processors, whose state is intended to be per-thread and context
> switched along with all other XSAVE state.
>
> Xen's vCPU context switch code would save and restore the state only
> if the guest had set the relevant XSTATE enable bits.  However,
> surprisingly, the use of these features is not dependent (PKU) or may
> not be dependent (MPX) on having the relevant XSTATE bits enabled.
>
> VMs which use MPX or PKU, and context switch the state manually rather
> than via XSAVE, will have the state leak between vCPUs (possibly,
> between vCPUs in different guests).  This in turn corrupts state in
> the destination vCPU, and hence may lead to weakened protections
>
> Experimentally, MPX appears not to make any interaction with BND*
> state if BNDCFGS.EN is set but XCR0.BND{CSR,REGS} are clear.  However,
> the SDM is not clear in this case; therefore MPX is included in this
> advisory as a precaution.

More: https://xenbits.xen.org/xsa/advisory-220.html

XSA-221 Issue Description:

> When polling event channels, in general arbitrary port numbers can be
> specified.  Specifically, there is no requirement that a polled event
> channel ports has ever been created.  When the code was generalised
> from an earlier implementation, introducing some intermediate
> pointers, a check should have been made that these intermediate
> pointers are non-NULL.  However, that check was omitted.

More: https://xenbits.xen.org/xsa/advisory-221.html

XSA-222 Issue Description:

> Certain actions require removing pages from a guest's P2M
> (Physical-to-Machine) mapping.  When large pages are in use to map
> guest pages in the 2nd-stage page tables, such a removal operation may
> incur a memory allocation (to replace a large mapping with individual
> smaller ones).  If this allocation fails, these errors are ignored by
> the callers, which would then continue and (for example) free the
> referenced page for reuse.  This leaves the guest with a mapping to a
> page it shouldn't have access to.
>
> The allocation involved comes from a separate pool of memory created
> when the domain is created; under normal operating conditions it never
> fails, but a malicious guest may be able to engineer situations where
> this pool is exhausted.

More: https://xenbits.xen.org/xsa/advisory-222.html

XSA-224 Issue Description:

> We have discovered a number of bugs in the code mapping and unmapping
> grant references.
>
> * If a grant is mapped with both the GNTMAP_device_map and
> GNTMAP_host_map flags, but unmapped only with host_map, the device_map
> portion remains but the page reference counts are lowered as though it
> had been removed. This bug can be leveraged cause a page's reference
> counts and type counts to fall to zero while retaining writeable
> mappings to the page.
>
> * Under some specific conditions, if a grant is mapped with both the
> GNTMAP_device_map and GNTMAP_host_map flags, the operation may not
> grab sufficient type counts.  When the grant is then unmapped, the
> type count will be erroneously reduced.  This bug can be leveraged
> cause a page's reference counts and type counts to fall to zero while
> retaining writeable mappings to the page.
>
> * When a grant reference is given to an MMIO region (as opposed to a
> normal guest page), if the grant is mapped with only the
> GNTMAP_device_map flag set, a mapping is created at host_addr anyway.
> This does *not* cause reference counts to change, but there will be no
> record of this mapping, so it will not be considered when reporting
> whether the grant is still in use.

More: https://xenbits.xen.org/xsa/advisory-224.html
2017-06-26 07:01:24 +00:00
Jörg Thalheim
7df83abe85 keepassx-community: 2.1.4 -> 2.2.0 2017-06-26 07:31:44 +01:00
Franz Pletz
3156263876
rsync: build with iconv, zlib & popt from nixpkgs
The rsync binary was previously built without iconv support which is needed
for utf-8 conversions on darwin. Fixes #26864.

Additionally rsync used to be built with bundled versions of zlib and popt
that were outdated. This decreases the size of the rsync binary by ~82KB.
2017-06-26 03:48:41 +02:00
Tim Steinbach
1a25495b63
git: 2.13.1 -> 2.13.2 2017-06-25 21:13:23 -04:00
taku0
800deb5273 thunderbird: 52.2.0 -> 52.2.1 2017-06-26 09:08:38 +09:00
taku0
22773a20e5 thunderbird-bin: 52.2.0 -> 52.2.1 2017-06-26 09:08:28 +09:00
aszlig
bd63daae03
chromium: Add installation of libGLESv2.so
The following errors occur when you start Chromium prior to this commit:

[2534:2534:0625/202928.673160:ERROR:gl_implementation.cc(246)] Failed to
load .../libexec/chromium/swiftshader/libGLESv2.so:
../libexec/chromium/swiftshader/libGLESv2.so: cannot open shared object
file: No such file or directory
[2534:2534:0625/202928.674434:ERROR:gpu_child_thread.cc(174)] Exiting
GPU process due to errors during initialization

While in theory we do not strictly need libGLESv2.so, in practice this
means that the GPU process isn't starting up at all which in turn leads
to crawling rendering performance on some sites.

So let's install all shared libraries in swiftshader.

I've tested this with the chromium.stable NixOS VM test and also locally
on my machine and the errors as well as the performance issues are gone.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2017-06-25 22:43:25 +02:00
Matt McHenry
cbb39f4382 krfb: add new qtx11extras dependency 2017-06-25 15:35:59 -04:00
Vincent Laporte
999892fd1e skrooge: 2.7.0 -> 2.8.1 2017-06-25 18:45:39 +02:00
Joachim F
90d3a0314c Merge pull request #26836 from Ma27/update/geogebra
geogebra: 5-0-361-0 -> 5-0-369-0
2017-06-25 16:35:13 +01:00
Joachim F
c235bf3e3d Merge pull request #26792 from mdorman/emacs-updates
Automated Emacs package updates
2017-06-25 15:33:19 +01:00
Roman Volosatovs
fd0f02628b
mopidy-local-sqlite: init at 1.0.0 2017-06-25 14:26:15 +02:00
Franz Pletz
ed515c8080
weechat: 1.8 -> 1.9 2017-06-25 14:03:18 +02:00
Maximilian Bosch
f5665e9ab4
geogebra: 5-0-361-0 -> 5-0-369-0 2017-06-25 12:39:30 +02:00
Jörg Thalheim
46427b77f4 Merge pull request #26690 from DIzFer/telegram-update
tdesktop: 1.0.27 -> 1.1.7
2017-06-25 11:37:21 +01:00
Jörg Thalheim
bc488d4cb5 Merge pull request #26834 from calvertvl/upgrade-calibre-to-3.1.1
calibre: 2.84.0 -> 3.1.1
2017-06-25 10:22:50 +01:00
Jörg Thalheim
f506b72308 krita: 3.1.3 -> 3.1.4 2017-06-25 10:18:45 +01:00
Jörg Thalheim
de21c43257 Merge pull request #26829 from dywedir/tiled
tiled: 0.18.2 -> 1.0.1
2017-06-25 09:48:10 +01:00
Jörg Thalheim
24e9ec3166 marble: fix src hash 2017-06-25 09:38:32 +01:00
Jörg Thalheim
f319442b77 keepassxc: fix 4.9 compatibility 2017-06-25 09:36:06 +01:00
Jörg Thalheim
ad42e5f6e5 Merge pull request #26795 from veprbl/root_6.10.00
root: 6.09.02 -> 6.10.00
2017-06-25 09:14:30 +01:00
Frederik Rietdijk
fcd5804d7f konversation: 1.6.2 -> 1.7.2 and fix build 2017-06-25 09:56:34 +02:00
Frederik Rietdijk
fdf181237b yakuake: fix build 2017-06-25 09:56:34 +02:00
Frederik Rietdijk
c7bc8b42f2 kdeconnect: fix build 2017-06-25 09:56:34 +02:00
Victor Calvert
e600317768 calibre: 2.84.0 -> 3.1.1
links-privacy patch was removed as the content server was
rewritten in calibre 3.0.

The rewrite also needed a couple more python packages.
2017-06-25 03:52:36 -04:00
Roman Volosatovs
4ebaed854f
mopidy-local-images: init at 1.0.0 2017-06-25 00:26:02 +02:00
dywedir
33e4afa172 tiled: 0.18.2 -> 1.0.1 2017-06-25 01:08:00 +03:00
Jörg Thalheim
c0303c7110 Merge pull request #26822 from 4z3/bitlbee-facebook
bitlbee-facebook: 1.1.0 -> 1.1.1
2017-06-24 20:45:18 +01:00
Der Pfirsich
2c6fbc737f spotify: 1.0.55.487.g256699aa-16 -> 1.0.57.474.gca9c9538-30 (#26794) 2017-06-24 20:41:05 +01:00
Jörg Thalheim
6741b3ac7c Merge pull request #26807 from ajevans85/crashplan-4-8-3
crashplan: 4.8.2 -> 4.8.3
2017-06-24 19:57:28 +01:00
tv
267ea50604 bitlbee-facebook: 1.1.0 -> 1.1.1 2017-06-24 20:37:32 +02:00
Dmitry Kalinkin
ada12f46dc
root: 6.09.02 -> 6.10.00
also workaround #26197
2017-06-24 13:38:25 -04:00
Yann Hodique
1be7323f5a hugo: 0.24 -> 0.24.1 2017-06-24 08:26:44 -07:00
Jörg Thalheim
40ccf99373 Merge pull request #26743 from sigma/pr/hugo-0.24
hugo: 0.23 -> 0.24
2017-06-24 16:23:52 +01:00
ajevans
76e019ad9f crashplan: 4.8.2 -> 4.8.3 2017-06-24 16:19:30 +10:00
Tim Steinbach
328617accd
rkt: 1.26.0 -> 1.27.0 2017-06-23 19:24:19 -04:00
aszlig
06271b6eba
krita: Fix build dependencies
First of all, we need a newer version of Vc, because at least version
1.1.0 is required for Krita 3.1.3.

Also, qtmultimedia and qtx11extras were missing.

Built and tested successfully on my machine.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @abbradar
2017-06-23 22:15:05 +02:00
John Ericson
afd2bdbad2 Merge pull request #26007 from obsidiansystems/cc-wrapper-prefix
Get rid of gcc-cross-wrapper
2017-06-23 11:22:34 -04:00
Michael Alan Dorman
eea95af5d1 melpa-packages: 2017-06-23
Removals:
 - todochiku - Removed from melpa
2017-06-23 11:05:12 -04:00
Michael Alan Dorman
40e17794ce melpa-stable-packages: 2017-06-23 2017-06-23 11:05:12 -04:00
Michael Alan Dorman
a10c8a97b4 org-packages: 2017-06-23 2017-06-23 11:05:12 -04:00
Michael Alan Dorman
8a714e3bb6 elpa-packages: 2017-06-23 2017-06-23 11:05:11 -04:00
Frederik Rietdijk
4f0d812abc python.pkgs.spyder: remove maintainers
since we both do not use this package anymore.
cc @bjornfor
2017-06-23 10:44:42 +02:00
Jörg Thalheim
f3b626cf4d Merge pull request #26770 from volth/jetbrains-update-script-2
jetbrains updater: use perlPackages.LWPProtocolhttps
2017-06-23 09:42:51 +01:00
aszlig
63fb845fcf
virtualbox: Rebase hardened.patch on top of 5.1.22
The merge of the version bump in
6fb9f89238 didn't take care of our patch
for the hardening mode and thus enabling VirtualBox without also
force-disabling hardening mode will result in a build error.

While the patch is largely identical with the old version, I've removed
one particular change around the following code:

    if (pFsObjState->Stat.st_mode & S_IWOTH)
        return supR3HardenedSetError3(VERR_SUPLIB_WORLD_WRITABLE, pErrInfo,
                                      "World writable: '", pszPath, "'");

In the old version of the patch we have checked whether the path is
within the Nix store and suppressed the error return if that's the case.

The reason why I did that in the first place was because we had a bunch
of symlinks which were writable.

In VirtualBox 5.1.22 the code specifically checks whether the file is a
symlink, so we can safely drop our change.

Tested via all of the "virtualbox" NixOS VM subtests and they now all
succeed.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2017-06-23 05:48:54 +02:00
Tim Steinbach
6fb9f89238 Merge pull request #25368 from bachp/virtualbox-5.1.22
virtualbox: 5.1.18 -> 5.1.22
2017-06-22 21:23:47 -04:00
John Ericson
7c754b1e3b mpg123: Modernize and fix for cross
Do not even think about configureFlags unless in cross, to avoid hash
breaking when not in cross.
2017-06-22 17:53:55 -04:00
John Ericson
502902f1c6 lynx: Fix for cross
Needed C toolchain targeting build platform
2017-06-22 17:53:55 -04:00
John Ericson
7bdacad8b3 ed: Modernize and fix for cross 2017-06-22 17:53:53 -04:00
John Ericson
8b22e497f2 vim: Modernize derivation, hopefully fixing cross 2017-06-22 17:53:53 -04:00
John Ericson
594d264205 cross stdenv adaptor: Support --host --build --target across the board
Packages get --host and --target by default, but can explicitly request
any subset to be passed as needed. See docs for more info.

rustc: Avoid hash breakage by using the old (ignored)
dontSetConfigureCross when not cross building
2017-06-22 17:52:28 -04:00
Volth
a2605322c6 fixed regexp, it did not match the last block 2017-06-22 19:16:19 +00:00
Volth
7fa29f39d1 a little simpification (use File::Slurp) 2017-06-22 19:08:19 +00:00
aszlig
1f65182272
electrum: Unify protobuf dependencies
Since 9c57f3b5c0 bumped the protobuf
version because the new upstream requires it, electrum now gets
protobuf3_0 *and* protobuf3_2 instead of just one version.

This leads to the following build errer:

Found duplicated packages in closure for dependency 'protobuf':
  protobuf 3.0.2 (...-python2.7-protobuf-3.0.2/lib/python2.7/site-packages)
  protobuf 3.2.0 (...-python2.7-protobuf-3.2.0/lib/python2.7/site-packages)

Using protobuf3_2 for keepkey and electrum fixes the build.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @np
2017-06-22 21:06:17 +02:00
Volth
00101eb7c9 jetbrains updater: use perlPackages.LWPProtocolhttps 2017-06-22 19:00:28 +00:00
Jörg Thalheim
d1eefba3a4 jetbrains: use nix-shell shebang in update script 2017-06-22 17:34:04 +01:00
Volth
1a87975910 update script for jetbrains products 2017-06-22 16:06:23 +00:00
Jörg Thalheim
c89efa3cbc Merge pull request #26753 from volth/jetbrains-update-2017.1.4
jetbrains.{ruby-mine,webstorm,datagrip,phpstorm}: 2017.1 -> 2017.1.4
2017-06-22 16:37:32 +01:00
David Izquierdo
aa2b643e4b tdesktop: 1.0.27 -> 1.1.7 2017-06-22 09:20:51 +02:00