[Nix-dev] imported archive lacks a signature?
What does this error mean? $ nix-copy-closure --to jefdaj@server $(type -tP labwiki) copying 166 missing paths (1820.22 MiB) to ‘jefdaj@server’... exporting path ‘/nix/store/cgddwzz9hkdgprvbymphv8yprc66zxk7-ghc-7.10.1’ exporting path ‘/nix/store/0j60852jsskjl2x3mv0a1ssrkb18hymz-haskell-old-locale-1.0.0.7’ exporting path ‘/nix/store/21k662hg1jics83kh9x2r3cfp9fd4cll-haskell-network-2.6.1.0’ error: imported archive of ‘/nix/store/cgddwzz9hkdgprvbymphv8yprc66zxk7-ghc-7.10.1’ lacks a signature I can't find anything about signatures in https://nixos.org/nixos/manual/. Thanks Jeff ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] How to add yourself as a maintainer for Haskell packages
On Fri, 28 Aug 2015, Peter Simons wrote: You have to do two things to enlist yourself as a maintainer: - Add your e-mail address to [1]. - Add your maintainer id to [2] and list all the packages you'd like to subscribe to. I like to use that service but I have about 100 packages at Hackage. Shall I them all to cabal2nix/Maintainers.hs and constantly update this list? Can I manage just all packages by hackage maintainer HenningThielemann. On the other hand there are some deprecated packages. Hm. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Next release updates
Channel has been created, it's all ready to be tested: $ nix-channel --add https://nixos.org/channels/nixos-15.09 nixos $ nixos-rebuild switch Domen On Thu, Aug 27, 2015 at 12:28 AM, Domen Kožar do...@dev.si wrote: Hi all, release-15.09 is now cut and hydra jobsets created, see http://hydra.nixos.org/jobset/nixos/release-15.09 and http://hydra.nixos.org/jobset/nixos/release-15.09-small Domen On Wed, Aug 26, 2015 at 12:00 PM, Domen Kožar do...@dev.si wrote: Hi all, yesterday staging branch was merged into master. Changes in staging reduce size of the closures for typical NixOS usage. This means the last blocker for the release was removed: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aissue+milestone%3A15.08+label%3Ablocker I'll branch off release-15.09 tonight CET and if no blockers are found, we'll have a release out in 2 weeks. Once channels are created and updated, you're all encouraged to test your non-critical installations and report findings to github issue tracker (make sure you tag issues with correct milestone and add blocker label if you think the issue is major) Domen ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Logo improvement ideas
Woops! ... I sent this directly to Tim rather than to the list: 2015-08-26 2:09 GMT+02:00 Tim Cuthbertson t...@gfxmonk.net: On Wed, Aug 26, 2015 at 2:16 AM, Cillian de Róiste cillian.deroi...@gmail.com wrote: Hi Tim, Very interesting designs! There was some talk at FOSDEM this year about brushing up the design/branding in general. I was really hoping we could get a designer on board to help with that although it fell through (but maybe you are a designer?). Unfortunately not, I just played one in high school ;). Ah, well that may be the closest we've got :D ... although I think kmicu on IRC has some design experience too. Before updating the logo, I wonder if we should step back a bit and think about what the logo should communicate. I added a stub of a page to the wiki to develop a style guide, but I haven't done much with it since: https://nixos.org/wiki/Style_Guide . Would something like that be a good place to start? It certainly might be, but I'm not really sure of the composition of folks working on Nix / NixOS - are there designer types that could help with this? Personally I do a bit of graphic design as a hobbyist (thus my interest in the logo), but don't have much to contribute outside that in terms of branding / figuring out style guides. So this is a good idea, but will only go somewhere if there are enough people wanting to contribute to it. Ah, fair enough. I think we could get help from the opensourcedesigners gang, but we don't have anyone at the moment. It would be awesome to get someone on board for this. One thing they suggest is to add a github ticket and label it design. Perhaps you could kick this off with your work on the logo and see if it catches anyone's interest? BTW, The issues with the overlapping lambdas in the current logo should be solved in this version: https://github.com/NixOS/nixos-artwork/blob/master/logo/nix-snowflake.svg I'm afraid I don't see it - this looks identical to the current logo to me. Maybe that's the point (I'm not sure what overlapping you're referring to),... Yeah, they look identical, but in the original each lambda overlaps, and there's an extra shape which masks the first lambda. In this version they are cut at the intersections. If you open the file in inkscape and ungroup the lambdas and move one, I think it will be clear ... at any rate it's just a detail. but I find it hard to spot the lambdas in this version for two reasons: - they're not separate enough. Aside from being different colours, there is no gap or other obvious distinction between each - (I think) the lack of any upright lambda makes it less likely you'd notice, as well. I'm pretty sure we can get help with the colors from http://opensourcedesign.net (I've asked them about it before, but figured we should work on the style guide first). Personally, I'm really fond of the current logo, although I would really like if we decided on a standard font (I'm a fan of Varela Round, to go with the current logo). Most of all I'd love if we could have a style guide, and have templates everyone could use for flyers, posters, t-shirts etc. I'd really love if NixOS could be themeable from configuration.nix too, but that's another story :D Yes, fonts are important too, and I haven't done too much work there other than flipping through my installed fonts to pick one which didn't look awful ;) Varela Round certainly matches the current logo's style well, although I suspect it might be better to have a font which doesn't match the logo's form quite so well (if the whole logo is made of rounded sticks, that could get a little bland). That makes perfect sense, thanks! I'm sure your sense of what doesn't look awful would already be a great improvement on what we have at the moment :D ... Myriad Pro is used a bit, and is nice but it's not Free, so that's a problem. What do you think? Perhaps we could have some kind of a video conferencing session with anyone who's interested to get the ball rolling? Yeah, collecting interested parties is certainly a good idea (although video conference might be hard to organise timezone-wise). I'm not entirely sure how to solicit that - anyone else on the mailing list interested? FWIW, I'm free on Sunday (except early morning, UTC). I could see if anyone from the opensourcedesigners would be interested in helping out too. Would that suit anyone? Naturally, it will be entirely up to the foundation to decide whether or not they are interested in adopting any suggestions we might come up with. Cheers, Cillian 2015-08-26 2:09 GMT+02:00 Tim Cuthbertson t...@gfxmonk.net: On Wed, Aug 26, 2015 at 2:16 AM, Cillian de Róiste cillian.deroi...@gmail.com wrote: Hi Tim, Very interesting designs! There was some talk at FOSDEM this year about brushing up the design/branding in general. I was really hoping we could get a designer on board to help with that although it fell through (but maybe you are a
Re: [Nix-dev] imported archive lacks a signature?
Hi Jeffrey,
$ nix-copy-closure --to jefdaj@server $(type -tP labwiki)
[...]
error: imported archive of
‘/nix/store/cgddwzz9hkdgprvbymphv8yprc66zxk7-ghc-7.10.1’ lacks a signature
to remedy that issue, create /etc/nix/signing-key.{pub,sec} as described in
https://github.com/NixOS/nix/blob/master/doc/signing.txt. Then call the
nix-copy-closure command with the --sign flag.
Best regards,
Peter
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] How to add yourself as a maintainer for Haskell packages
Fellow Haskell hackers, if you'd like your favorite Haskell packages to always compile in Nixpkgs, then you can tip the odds in your favor by becoming a package maintainer. Maintainers receive an e-mail from hydra.nixos.org every time the build status of their package changes, i.e. every time a successful build suddenly fails. This gives you the chance to respond quickly to the issue and help to fix it. You have to do two things to enlist yourself as a maintainer: - Add your e-mail address to [1]. - Add your maintainer id to [2] and list all the packages you'd like to subscribe to. I hope you'll find this feature useful, Peter [1] https://github.com/NixOS/nixpkgs/blob/master/lib/maintainers.nix. [2] https://github.com/NixOS/cabal2nix/blob/master/src/Distribution/Nixpkgs/Haskell/FromCabal/Configuration/Maintainers.hs#L12 ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] How to add yourself as a maintainer for Haskell packages
Hi Henning, I like to use that service but I have about 100 packages at Hackage. Shall I them all to cabal2nix/Maintainers.hs and constantly update this list? at the moment, this is your only option, I'm afraid. I did more or less the same thing: I cut and pasted the list of packages from [1] into the file and edited it for syntax. I realize this approach doesn't scale well, but it's all we have right now. Can I manage just all packages by hackage maintainer HenningThielemann. On the other hand there are some deprecated packages. Hm. Nothing prevents us from constructing that list of maintainers programmatically. We could turn it into a function that has access to the Hackage database so that it's possible to collect all packages that mention a certain maintainer name in their Cabal file. Would that work better for you? Best regards Peter [1] http://hackage.haskell.org/user/PeterSimons ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Problem when running some JVM librairies under NixOS
Hi everyone, I have just migrated my development workstation from ArchLinux to NixOS, and I'm facing a small issues when developing my JVM applications. The problem manifest itself with two libraries (embedded mongodb, and embedded protobuf compiler) which have in common one thing: - They extract some file in the `/tmp` folder and start an executable from the extracted files I won't show the detail of the exception here, but basically it seems like the files get deleted (file not found) before being able to start the external process. Everything was working fine on my previous distribution, and I'm trying to understand what could trigger the problem? Is there anything specific when it comes to dealing with the `/tmp` directory in Nix? Any idea how I could investigate the issue in more detail? Thanks for this great OS and for your help -- *Λ\ois* http://twitter.com/aloiscochard http://github.com/aloiscochard ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Jar files
Hi all, We don't have much of a Java presence in Nixpkgs, but I was thinking of growing it. This leads to what seems like a bit of a thorny issue: most java code is distributed in jars, which are glorified zip files. Can anyone see the problem? The one I'm afraid of is one of runtime dependencies: normally we're fine embedding other nix store paths in code, under the assumption that the literal string will show up somewhere in the resulting binary. If you zip the result, that's no longer true without smarter scanning logic. So is the solution to make our java packaging never produce any jars, and explicitly unpack any we encounter? That feels kind of gross. Alternately, we could have a post-processor that scans the unpacked zip files for store paths and then replicates them somewhere in nix-support. Also doesn't feel ideal! Are there other options? Am I misunderstanding something or is this really an issue? Thanks, Dan ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Problem when running some JVM librairies under NixOS
On Friday, August 28, 2015 14:26:22 Alois Cochard wrote: I have just migrated my development workstation from ArchLinux to NixOS, and I'm facing a small issues when developing my JVM applications. The problem manifest itself with two libraries (embedded mongodb, and embedded protobuf compiler) which have in common one thing: - They extract some file in the `/tmp` folder and start an executable from the extracted files I won't show the detail of the exception here, but basically it seems like the files get deleted (file not found) before being able to start the external process. Everything was working fine on my previous distribution, and I'm trying to understand what could trigger the problem? Is there anything specific when it comes to dealing with the `/tmp` directory in Nix? /tmp is one of the few things we're yet to lay our hands on, so it works just like in any other distro. The most likely reason is you misunderstood the error message or the error message is broken. For example, when an executable file has a broken dynamic loader link, you get a weird not found message when the file you're executing actually exists. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Problem when running some JVM librairies under NixOS
On Friday, August 28, 2015 08:58:01 Daniel Peebles wrote: Yeah, I'm pretty sure the dynamic linker is the issue here. Alois, you'll probably have to unpack the jar, patchelf it to point at the proper one, and then repack the jar. Or just have it the whole thing depend explicitly on a proper Nix store path :) In fact, setting LD_LIBRARY_PATH may be easier than this, or you could build the jar from source. On Fri, Aug 28, 2015 at 8:47 AM, phree...@yandex.ru wrote: On Friday, August 28, 2015 14:26:22 Alois Cochard wrote: I have just migrated my development workstation from ArchLinux to NixOS, and I'm facing a small issues when developing my JVM applications. The problem manifest itself with two libraries (embedded mongodb, and embedded protobuf compiler) which have in common one thing: - They extract some file in the `/tmp` folder and start an executable from the extracted files I won't show the detail of the exception here, but basically it seems like the files get deleted (file not found) before being able to start the external process. Everything was working fine on my previous distribution, and I'm trying to understand what could trigger the problem? Is there anything specific when it comes to dealing with the `/tmp` directory in Nix? /tmp is one of the few things we're yet to lay our hands on, so it works just like in any other distro. The most likely reason is you misunderstood the error message or the error message is broken. For example, when an executable file has a broken dynamic loader link, you get a weird not found message when the file you're executing actually exists. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Problem when running some JVM librairies under NixOS
Yeah, I'm pretty sure the dynamic linker is the issue here. Alois, you'll probably have to unpack the jar, patchelf it to point at the proper one, and then repack the jar. Or just have it the whole thing depend explicitly on a proper Nix store path :) On Fri, Aug 28, 2015 at 8:47 AM, phree...@yandex.ru wrote: On Friday, August 28, 2015 14:26:22 Alois Cochard wrote: I have just migrated my development workstation from ArchLinux to NixOS, and I'm facing a small issues when developing my JVM applications. The problem manifest itself with two libraries (embedded mongodb, and embedded protobuf compiler) which have in common one thing: - They extract some file in the `/tmp` folder and start an executable from the extracted files I won't show the detail of the exception here, but basically it seems like the files get deleted (file not found) before being able to start the external process. Everything was working fine on my previous distribution, and I'm trying to understand what could trigger the problem? Is there anything specific when it comes to dealing with the `/tmp` directory in Nix? /tmp is one of the few things we're yet to lay our hands on, so it works just like in any other distro. The most likely reason is you misunderstood the error message or the error message is broken. For example, when an executable file has a broken dynamic loader link, you get a weird not found message when the file you're executing actually exists. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Jar files
Nix only scans for hashes, and there's a good chance they'll be kept intact when compressing. If that's not good enough, then you'll have to make a file with references either by hand or by unpacking the jars. I don't know how often this will actually be needed - is Java retaining paths to dependencies after compilation? Dnia 28 sierpnia 2015 15:02:19 CEST, Daniel Peebles pumpkin...@gmail.com napisał(a): Hi all, We don't have much of a Java presence in Nixpkgs, but I was thinking of growing it. This leads to what seems like a bit of a thorny issue: most java code is distributed in jars, which are glorified zip files. Can anyone see the problem? The one I'm afraid of is one of runtime dependencies: normally we're fine embedding other nix store paths in code, under the assumption that the literal string will show up somewhere in the resulting binary. If you zip the result, that's no longer true without smarter scanning logic. So is the solution to make our java packaging never produce any jars, and explicitly unpack any we encounter? That feels kind of gross. Alternately, we could have a post-processor that scans the unpacked zip files for store paths and then replicates them somewhere in nix-support. Also doesn't feel ideal! Are there other options? Am I misunderstanding something or is this really an issue? Thanks, Dan ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Wysłane za pomocą K-9 Mail.___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Jar files
Hi, On 28/08/15 15:02, Daniel Peebles wrote: So is the solution to make our java packaging never produce any jars, and explicitly unpack any we encounter? The simple solution is to generate uncompressed JARs (jar -0). But that should be rarely needed since Java packages typically don't store paths to runtime dependencies (though putting the paths to JAR dependencies in JAR manifests would be a nice way to get RPATH-like behaviour!). -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixOS installation on multi-boot system with GRUB
On Thu, 27 Aug 2015, 宋文武 wrote:
I think you can:
install NixOS's GRUB to its boot partitation, then add a 'chainloader'
menu entry to your main GRUB (installed into MBR by Ubuntu).
I did this with btrfs (ext4 did't work for me):
boot.loader.grub.device = /dev/sdaX;
(sdaX is the boot or root partition)
# grub.cfg
menuentry 'NixOS' {
set root='(hd0,X)'
chainloader +1
}
install NixOS without GRUB, then add a 'configfile' menu entry to your
GRUB to load NixOS's grub.cfg.
I guess it look like:
boot.loader.grub.device = nodev;
# grub.cfg
menuentry 'NixOS' {
set root='(hd0,X)'
configfile '/boot/grub/grub.cfg';
}
I find no /boot/grub/grub.cfg on the NixOS partition, not even a 'grub'
directory. Am I supposed to write a grub.cfg myself or should
nixos-install create one for me? If the latter one, how can I make
nixos-install create a grub.cfg for me but not install a boot-loader?___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] imported archive lacks a signature?
Thanks, that works!
On Fri, 28 Aug 2015 10:45:06 +0200
Peter Simons sim...@cryp.to wrote:
Hi Jeffrey,
$ nix-copy-closure --to jefdaj@server $(type -tP labwiki)
[...]
error: imported archive of
‘/nix/store/cgddwzz9hkdgprvbymphv8yprc66zxk7-ghc-7.10.1’ lacks a signature
to remedy that issue, create /etc/nix/signing-key.{pub,sec} as described in
https://github.com/NixOS/nix/blob/master/doc/signing.txt. Then call the
nix-copy-closure command with the --sign flag.
Best regards,
Peter
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixOS installation on multi-boot system with GRUB
2015-08-28 12:38 GMT-03:00 Henning Thielemann lemm...@henning-thielemann.de:
On Thu, 27 Aug 2015, 宋文武 wrote:
I think you can:
install NixOS's GRUB to its boot partitation, then add a 'chainloader'
menu entry to your main GRUB (installed into MBR by Ubuntu).
I did this with btrfs (ext4 did't work for me):
boot.loader.grub.device = /dev/sdaX;
(sdaX is the boot or root partition)
# grub.cfg
menuentry 'NixOS' {
set root='(hd0,X)'
chainloader +1
}
install NixOS without GRUB, then add a 'configfile' menu entry to your
GRUB to load NixOS's grub.cfg.
I guess it look like:
boot.loader.grub.device = nodev;
# grub.cfg
menuentry 'NixOS' {
set root='(hd0,X)'
configfile '/boot/grub/grub.cfg';
}
I find no /boot/grub/grub.cfg on the NixOS partition, not even a 'grub'
directory. Am I supposed to write a grub.cfg myself or should nixos-install
create one for me? If the latter one, how can I make nixos-install create a
grub.cfg for me but not install a boot-loader?
Do you need NixOS controlling the boot of other OSes on your machine?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] How to use the binary cache at hydra.cryp.to for Haskell binaries
Fellow Nix'ers,
the binary cache at hydra.cryp.to has been popular with Haskell users
because it tends to have x86_64-linux binaries for haskellPackages
sooner than hydra.nixos.org or cache.nixos.org do. Now, users who follow
the nixos-unstable channel or any of the nixos-xx.yy release
channels don't need to configure access hydra.cryp.to! Using that site
makes sense only if you're building things directly from the current
head of the master branch of the Git repository. If you're one of
those, then you can configure access as follows.
In NixOS, add the following snippet to your configuration.nix file:
| nix = {
| trustedBinaryCaches = [ http://hydra.cryp.to ];
| binaryCachePublicKeys = [
| hydra.cryp.to-1:8g6Hxvnp/O//5Q1bjjMTd5RO8ztTsG8DKPOAg9ANr2g=
| ];
| };
Users of Nix on other host systems, need to edit their /etc/nix/nix.conf
file:
| trusted-binary-caches = http://hydra.cryp.to
| binary-cache-public-keys =
hydra.cryp.to-1:8g6Hxvnp/O//5Q1bjjMTd5RO8ztTsG8DKPOAg9ANr2g=
Note that the binary-cache-public-keys file will usually contain an
entry for cache.nixos.org already, so you want to *add* that key to the
one you already have.
Restart your nix-daemon and then use the command-line flags --option
extra-binary-caches http://hydra.cryp.to; every time you run
nix-build, nix-shell, or nix-env to compile Haskell packages. If
at all possible, please avoid querying the cache more often than
necessary because the machine is not particularly quick.
Alternatively, set up a cron job that pulls the binary manifest from the
server every now and then, i.e. via configuration.nix:
| services.cron.systemCronJobs = [
| 49 */3 * * * root nix-pull /dev/null
http://hydra.cryp.to/jobset/nixpkgs/haskell-updates/channel/latest/MANIFEST;
| ];
Then your machine will just know which binary packages exist on the
server even if you don't provide the extra command-line flags.
I hope this helps,
Peter
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
