Re: [Nix-dev] nvidia proprietary / i7 notebook - does not start

[Cillian de Róiste]

Sorry for replying off-list (I suggested trying bumblebee).

Just to check, did you enable intel (alone) in the videoDrivers (I think
that's necessary, please correct me if I'm wrong). Do you have BIOS/EFI
options to use only the nvidia GPU? Is using nouveau an option for you? You
could also try nouveau as the bumblebee driver.

I'd love to know what ubuntu does.

2017-05-10 21:50 GMT+02:00 Marc Weber :

> The Ubuntu disk doesn't habe bumblbee installed.
> Activating it on nixos makes X fail with no devices found even though I
> added BusID. Stopping BumblBee starting X manually I get the same
> results 8x8 size ..
>
> So I wonder whether I need it at all
>
> Marc Weber
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

[Nix-commits] [NixOS/nixpkgs] e3938c: drumkv1: 0.8.0 -> 0.8.1

[Cillian de Róiste]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: e3938c8e318b3ba76be735e0eb1652b640fb8d65
  
https://github.com/NixOS/nixpkgs/commit/e3938c8e318b3ba76be735e0eb1652b640fb8d65
  Author: Cillian de Róiste 
  Date:   2017-03-25 (Sat, 25 Mar 2017)

  Changed paths:
M pkgs/applications/audio/drumkv1/default.nix

  Log Message:
  ---
  drumkv1: 0.8.0 -> 0.8.1


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 65593e: drumgizmo: 0.9.11 -> 0.9.12

[Cillian de Róiste]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 65593e64c480493555ae21050a422e4c7ff9c7ea
  
https://github.com/NixOS/nixpkgs/commit/65593e64c480493555ae21050a422e4c7ff9c7ea
  Author: Cillian de Róiste 
  Date:   2017-03-25 (Sat, 25 Mar 2017)

  Changed paths:
M pkgs/applications/audio/drumgizmo/default.nix

  Log Message:
  ---
  drumgizmo: 0.9.11 -> 0.9.12


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 23c1d1: puremapping: update 1.01 -> 20160130

[Cillian de Róiste]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 23c1d17e9d555a2855fc000e3458e05c0991832f
  
https://github.com/NixOS/nixpkgs/commit/23c1d17e9d555a2855fc000e3458e05c0991832f
  Author: Cillian de Róiste 
  Date:   2016-07-17 (Sun, 17 Jul 2016)

  Changed paths:
M pkgs/applications/audio/pd-plugins/puremapping/default.nix

  Log Message:
  ---
  puremapping: update 1.01 -> 20160130


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] d07884: update puredata

[Cillian de Róiste]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: d078844ca62c669468b818fbe59b8ac6c5d2aab3
  
https://github.com/NixOS/nixpkgs/commit/d078844ca62c669468b818fbe59b8ac6c5d2aab3
  Author: Bart Brouns 
  Date:   2016-07-17 (Sun, 17 Jul 2016)

  Changed paths:
M pkgs/applications/audio/puredata/default.nix

  Log Message:
  ---
  update puredata


  Commit: 5431ffee4c5de99ab583686b0e13b22183d17adf
  
https://github.com/NixOS/nixpkgs/commit/5431ffee4c5de99ab583686b0e13b22183d17adf
  Author: Cillian de Róiste 
  Date:   2016-07-17 (Sun, 17 Jul 2016)

  Changed paths:
M pkgs/applications/audio/puredata/default.nix

  Log Message:
  ---
  puredata: fix url

Downloads have been moved from sourceforge to msp.ucsd.edu


Compare: https://github.com/NixOS/nixpkgs/compare/336786addc53...5431ffee4c5d___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Redesign of documentation

[Cillian de Róiste]

2016-02-17 6:58 GMT+01:00 stewart mackenzie :
> I can't find the link, but a few nixers made something called nix-cloud.
> That was fun and informative for learning the nix expression language.

Yes indeed, qknight and friends made http://nixcloud.io/tour (web
based, interactive tutorial on nix, the language) and of course
Lethalman's Nix pills series is another excellent resource for
learning how nix works:
http://lethalman.blogspot.ie/search/label/nixpills
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Munich NixOS Sprint: 12th & 13th December

[Cillian de Róiste]

Hi,

This is an email from Robin (globin), which is temporarily stuck in
the mailing list approval queue. So, don't be surprised if you get it
twice :D

…

We had our first Munich NixOS Meetup last week and decided to sprint
on the weekend of December 12 & 13
to get stuff done help us get over not being able to attend NixCon.

Currently planned projects are:
 * nginx/wpa_supplicant/php config abstraction
 * meta information completion
 * hydra channel fixing
 * packaging introduction

The sprint will take place at the Mayflower office near Isartor in the
centre of Munich.

There is a meetup page up at
http://www.meetup.com/Munich-NixOS-Meetup/events/227019580/.

If you have any questions feel free to contact us! If you'd need
accommodation we can possibly help or at least give more information.

Cheers
Robin (globin), Franz (fpletz), Tristan (fadenb)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

[Cillian de Róiste]

2015-11-19 16:57 GMT+01:00 Profpatsch :
> On 15-11-19 02:56am, Roger Qiu wrote:
>> Can the manual be made as a gitbook with the chapters fleshed out better
>> and made more user friendly? One  part of the manual can be very fact
>> based, another part can be story based. Kind of like the difference between
>> documentation vs api documentation vs tutorials. I often find myself across
>> 3 to 4 different blog posts, the arch and gentoo wiki, the nixos manual,
>> the wiki and github issues because the up to date relevant information is
>> everywhere.
>
> May I humbly suggest http://stevelosh.com/blog/2013/09/teach-dont-tell/ as
> a general documentation writing template?

I'm a big fan of https://jacobian.org/writing/great-documentation/

I think it gives a really nice overview of the three main kinds of
documentation:
* step-by-step tutorials,
* overviews and topical guides to the various conceptual areas of your
project, and
* low-level, deep-dive reference material.

It also has some nice ideas such as creating an initial tutorial: "a
new user should be able to experience success within thirty minutes"

Cheers,
Cillian

-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
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

[Cillian de Róiste]

Woops! ... I sent this directly to Tim rather than to the list:


2015-08-26 2:09 GMT+02:00 Tim Cuthbertson :
> On Wed, Aug 26, 2015 at 2:16 AM, Cillian de Róiste
>  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 entir

Re: [Nix-dev] Logo improvement ideas

[Cillian de Róiste]

Perhaps we should also have separate (but related) logos for each of
the NixOS projects: Nix, NixOS, NixOps, etc. to help people understand
how they fit together.

2015-08-25 18:16 GMT+02:00 Cillian de Róiste :
> 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?). 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?
>
> 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 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
>
> 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?
>
> Cheers,
> Cillian
>
>
> 2015-08-25 7:25 GMT+02:00 Tim Cuthbertson :
>> Nicolas,
>>
>> You raise a very good point about the print-appropriate colours. On
>> reflection, I think the blues I've chosen are possibly among the worst
>> for print reproduction ;)
>>
>> Regarding the gradient, I think it's common enough to have a
>> full-color digital logo (including gradients / shading), with a flat
>> colour version for print.
>>
>> So I've added a "print options" file, with what I think are more
>> print-appropriate colours. TBH I don't have much experience here - I
>> used CMYK colour selector, but outside that I'm not quite sure how to
>> make sure a colour is good for printers - should I be looking at
>> pantone colours or something?
>>
>> It's also testing against different backgrounds, and in different
>> shapes (i.e circular sticker, popular for laptops). I'm not sure if
>> it's bad form to put your wordmark inside your logo, but it's
>> otherwise quite awkward to put a big circular thing _and_ some
>> additional text into an outer circle.
>>
>> https://github.com/gfxmonk/nixos-logo-ideas/blob/master/exports/logo-print-options.png
>>
>> To be honest, the print works well enough we could drop the gradient
>> version if we want to keep it simple. But I do still prefer it myself.
>>
>> Cheers,
>>  - Tim.
>>
>> On Tue, Aug 25, 2015 at 5:36 AM, Nicolas Pierron
>>  wrote:
>>> Thanks Tim,
>>>
>>> I think we definitely need a new logo, for at least 2 reasons:
>>>  - The overlap of the lambda does not render correctly in all software.
>>>  - The colors are not industrial printers friendly.
>>>
>>> All your proposal are well addressing the first issue, by removing the
>>> overlap and adding extra transparency between the lambdas.
>>>
>>> On the other hand, the gradient might be worse than the current status
>>> about making the image easy to print (CYMK).  I think we would be
>>> printing more and more t-shirts / goodies in the future, and this is a
>>> critical issue that we have to solve with the current logo.
>>>
>>> Also, a-part from the shape of the logo, I think it would be
>>> interesting to see how well the colors of the lambda might render with
>>> various background colors.  The goal is not to choose a different
>>> background color, but to make sure that the lambda's color are still
>>> good, even if printed on black t-shirts.
>>>
>>> Personal opinion:
>>> shape:
>>>  - "slant" does not feels good and straight, as I would expect from our 
>>> image.
>>>  - "hex", "circle", "straight" are fine.
>>>  - "straight" lambdas' left arm seems t

Re: [Nix-dev] Logo improvement ideas

[Cillian de Róiste]

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?). 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?

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 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

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?

Cheers,
Cillian


2015-08-25 7:25 GMT+02:00 Tim Cuthbertson :
> Nicolas,
>
> You raise a very good point about the print-appropriate colours. On
> reflection, I think the blues I've chosen are possibly among the worst
> for print reproduction ;)
>
> Regarding the gradient, I think it's common enough to have a
> full-color digital logo (including gradients / shading), with a flat
> colour version for print.
>
> So I've added a "print options" file, with what I think are more
> print-appropriate colours. TBH I don't have much experience here - I
> used CMYK colour selector, but outside that I'm not quite sure how to
> make sure a colour is good for printers - should I be looking at
> pantone colours or something?
>
> It's also testing against different backgrounds, and in different
> shapes (i.e circular sticker, popular for laptops). I'm not sure if
> it's bad form to put your wordmark inside your logo, but it's
> otherwise quite awkward to put a big circular thing _and_ some
> additional text into an outer circle.
>
> https://github.com/gfxmonk/nixos-logo-ideas/blob/master/exports/logo-print-options.png
>
> To be honest, the print works well enough we could drop the gradient
> version if we want to keep it simple. But I do still prefer it myself.
>
> Cheers,
>  - Tim.
>
> On Tue, Aug 25, 2015 at 5:36 AM, Nicolas Pierron
>  wrote:
>> Thanks Tim,
>>
>> I think we definitely need a new logo, for at least 2 reasons:
>>  - The overlap of the lambda does not render correctly in all software.
>>  - The colors are not industrial printers friendly.
>>
>> All your proposal are well addressing the first issue, by removing the
>> overlap and adding extra transparency between the lambdas.
>>
>> On the other hand, the gradient might be worse than the current status
>> about making the image easy to print (CYMK).  I think we would be
>> printing more and more t-shirts / goodies in the future, and this is a
>> critical issue that we have to solve with the current logo.
>>
>> Also, a-part from the shape of the logo, I think it would be
>> interesting to see how well the colors of the lambda might render with
>> various background colors.  The goal is not to choose a different
>> background color, but to make sure that the lambda's color are still
>> good, even if printed on black t-shirts.
>>
>> Personal opinion:
>> shape:
>>  - "slant" does not feels good and straight, as I would expect from our 
>> image.
>>  - "hex", "circle", "straight" are fine.
>>  - "straight" lambdas' left arm seems to be too-long.
>>
>> color:
>>  - "none" removes the charm, of having something a bit different.
>>  - "half" and "feature" sound both good.
>>  - "feature" sounds interesting, and makes the lambda too obvious, but
>> "half" sounds warmer/more solid than "feature".
>>
>>
>> On Mon, Aug 24, 2015 at 7:58 PM, Joachim Schiele  wrote:
>>> looks great!
>>>
>>>
>>> On 24.08.2015 05:14, Tim Cuthbertson wrote:
 Hello all,

 I'm a big fan of Nix / NixOS, but I've long felt that the logo could
 do with a bit of work. So I toyed about a bit with inkscape, and came
 up with a few ideas:

 https://github.com/gfxmonk/nixos-logo-ideas/tree/master/exports

 They mostly keep to the existing logo structure, but with some changes:

  - Make the lines wider, and remove the rounded caps. The existing
 logo feels too thin, as if it's made of lines rather than shapes. This
 feels fragile, particularly when scaled down.

  - Made the lambda structure more obvious. To be honest, it wasn't
>>>

Re: [Nix-dev] [(private) Meetup] I'm traveling through Europe, maybe I can meet some nixers?

[Cillian de Róiste]

Hi Matthias,

That sounds like fun! Let me know if you'll be passing through Munich,
maybe we can arrange something in advance.

Cheers,
Cillian

2015-07-07 20:57 GMT+02:00 Matthias Beyer :
> Hi Nixers!
>
> So, it happens that I will travel through Europe in August and
> September. Actually, I will travel by bike from Donau-Eschingen (where
> the Donau originates) to the Black Sea, if I get so far.
>
> Maybe I can meet some nixers while traveling? Would be a pleasure to
> meet some of you for a drink or something, if we can arrange that!
>
> Contact me!
>
> Besides: I'd love to attend at a nixos meetp, NixConn anyone? :-P
>
> --
> Mit freundlichen Grüßen,
> Kind regards,
> Matthias Beyer
>
> Proudly sent with mutt.
> Happily signed with gnupg.
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] How to build PHP with xdebug support

[Cillian de Róiste]

Hi Paul,

I've enabled it like this:
https://gitlab.com/goibhnix/configurations/blob/master/users/cillian-work.nix#L264

But I haven't used this configuration in a while so I'm not 100% sure
if it's still valid.

Cheers,
Cillian

2015-05-13 10:28 GMT+02:00 Paul Koerbitz :
> So I have found a workaround just after posting to this list: I am now
> using a php.ini file from my home directory and have $PHPRC set to
> this ini file. I've simply hardcoded the paths to xdebug in this
> php.ini file.
>
> This workaround works for me know, but I'm still interested if there
> is a more elegant solution.
>
> cheers
> Paul
>
> On Wed, May 13, 2015 at 9:52 AM, Paul Koerbitz  
> wrote:
>> Hi there,
>>
>> I am struggeling a bit trying to install PHP so that it supports
>> xdebug. I can install both php and xdebug, but I don't understand how
>> I can teach PHP about the xdebug extension.
>>
>> I have tried to override the PHP deriviation (by placing my own
>> modified deriviation under ~/.nixpkgs/php/) and modifying it's install
>> phase as follows:
>>
>> ```
>>   installPhase = ''
>> unset installPhase; installPhase;
>> cp php.ini-production $iniFile
>>
>> # Now Let's build xdebug if flag has been given
>> # TODO I think there are better paths than the given below
>> PATH=$PATH:$out/bin
>> tar xfz $xdebug_src;
>> cd xdebug*
>> phpize
>> ./configure --prefix=$out
>> make
>> ensureDir $out/lib; cp modules/xdebug.so $out/lib
>> cat >> $out/etc/php.ini << EOF
>> zend_extension="$out/lib/xdebug.so"
>> zend_extension_ts="$out/lib/xdebug.so"
>> zend_extension_debug="$out/lib/xdebug.so"
>> xdebug.remote_enable=true
>> xdebug.remote_host=127.0.0.1
>> xdebug.remote_port=9000
>> xdebug.remote_handler=dbgp
>> xdebug.profiler_enable=0
>> xdebug.profiler_output_dir="/tmp/xdebug"
>> xdebug.remote_mode=req
>> max_execution_time = 300
>> date.timezone = UTC
>>   EOF
>>   '';
>> ```
>>
>> (I have stolen this from
>> https://github.com/jimpick/nixos-upstream-svn-nixpkgs/blob/master/pkgs/development/interpreters/php_configurable/default.nix)
>>
>> However, the xdebug build included in the install phase breaks for
>> some reason I haven't figured out yet.
>>
>> Is this a reasonable avenue to pursue or is there a simple better way
>> to get xdebug-enabled php on nixos?
>>
>> thank you
>> Paul
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Customizing calibre PYTHONPATH to support plugins...

[Cillian de Róiste]

Hi Michael,

I think the following would work:

calibrePython = pkgs.python27Full.buildEnv.override { extraLibs =
[ pkgs.python27Packages.pycrypto ]; };
myCalibre = pkgs.calibre.override { python = calibrePython; };

Cheers,
Cillian


2015-02-28 20:47 GMT+01:00 Michael Alan Dorman :
> On Sat, Feb 28, 2015, at 10:35 AM, Bjørn Forsman wrote:
>
> Maybe propagatedBuildInputs works?
>
> Hi, Bjørn,
>
> I should have mentioned that I tried that as well, to no avail---and it
> seems to me that that would only apply if, say, I were trying to build a new
> expression for the plugin (which I might do eventually, but for the moment
> is out of scope) and that needed to access calibre's dependencies...
>
> Mike.
>
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Announcing New Ruby Support

[Cillian de Róiste]

2015-02-11 0:50 GMT+01:00 Wout Mertens :
> rb_enc_raise seems to be a ruby 2.0 thing and you're using 1.9.3. Some mixup
> somewhere?
> https://bugs.ruby-lang.org/issues/5650 was when it was added to 2.0 3 years
> ago...

Thanks! That definitely helped. Our default ruby is 1.9 (which seems
to match Ubuntu and Debian), so I tried to build jekyll with ruby_2_2
but it failed with the following error:

building /nix/store/96pwrdy5jzdz8rgcnb5anfmyy65lg9iw-jekyll-0.20.0
installing
You are trying to install in deployment mode after changing
your Gemfile. Run `bundle install` elsewhere and add the
updated Gemfile.lock to version control.

If this is a development machine, remove the Gemfile freeze
by running `bundle install --no-deployment`.

You have added to the Gemfile:
* test-unit

The Gemfile contains the line: gem 'test-unit' if RUBY_PLATFORM =~
/cygwin/ || RUBY_VERSION.start_with?("2.2")
so I tried with ruby_2_1_3 instead. The build finished successfully,
but I didn't end up with a `jekyll` in ./result/bin:

$ ls ./result/bin
bayes.rb  cucumber  launchy  maruku
posix-spawn-benchmark  rdiscount  redcarpet  ri
convert_to_should_syntax  htmldiff  ldiffmarutex  rake
  rdoc   rg summarize.rb

Here's the build log: http://nixpaste.noip.me/NKlLS4G-

Any idea what I can try next?

Cheers,
Cillian


-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Announcing New Ruby Support

[Cillian de Róiste]

2015-02-10 19:25 GMT+01:00 Cillian de Róiste :
>
> Hi!
>
> I thought I'd try to package jekyll, but I've run into some trouble...
>
> 2015-01-22 5:29 GMT+01:00 Charles Strahan :
>>
>> To use the new system, first create (or copy over) a Gemfile describing the
>> required gems.
>
>
> I grabbed the Gemfile from the github repo:
> $ wget https://raw.githubusercontent.com/jekyll/jekyll/master/Gemfile
>
>
>> Next, create a Gemfile.lock by running `bundler package --no-install` in the
>> containing directory (this also creates two folders - vendor and .bundle -
>> which you'll want to delete before committing).
>
>
> I had first installed pkgs.bundler, which got me version 1.7.9, which doesn't 
> have the --no-install option which seems to have been added in 1.8. I then 
> installed pkgs.bundler_HEAD which also reports the version to be 1.7.9 but 
> does have the --no-install option. However, I got stuck on the next step:
>
> $ bundler package --no-install
> There are no gemspecs at /home/goibhniu/ruby/jekyll.

The second line has the word "gemspec", I commented it out and was
able to get further

I ran `bundler package --no-install --path vendor/bundle` which
successfully created lockfile.

>> Now, you'll need to dump the lockfile as a Nix expression. To do so, use 
>> Bundix
>> in the target directory:
>>
>>   $(nix-build '' -A bundix)/bin/bundix

To avoid rebuilding the world I checked out 317d78d and tried to
install bundix from there. I had to patch the hash for bundix and
bundler [1], but then I was able to install bundix and create the
gemset.nix \o/

>>
>> That will drop a gemset.nix file in your current directory, which describes 
>> the
>> sources for all of the gems and their respective SHAs.
>>
>> Finally, you'll need to use bundlerEnv to build the gems. The following 
>> example
>> is how we package the sup mail reader:


I copied the example nix expression, changed the name and added it to
all-packages.nix to build it. All went quite well until I got the
following error:

...
Installing liquid 3.0.1

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

/nix/store/wdjnbdyrvsfbg245qyp3r7qwhlhxzd1c-ruby-1.9.3-p547/bin/ruby
-r ./siteconf20150210-115-km0s7e.rb extconf.rb
creating Makefile

make  clean
building clean-static
building clean

make
building lexer.o
compiling lexer.c
lexer.c: In function 'lex_one':
lexer.c:143:5: error: implicit declaration of function
'rb_enc_raise' [-Werror=implicit-function-declaration]
 rb_enc_raise(utf8_encoding, cLiquidSyntaxError, "Unexpected
character %c", c);

IIUC it fails to find some ruby header file. Any tips on how to proceed?

Cheers,
Cillian


Patches [1]:

diff --git a/pkgs/development/interpreters/ruby/bundix/gemset.nix
b/pkgs/development/interpreters/ruby/bundix/gemset.nix
index a2c633f..a3e732c 100644
--- a/pkgs/development/interpreters/ruby/bundix/gemset.nix
+++ b/pkgs/development/interpreters/ruby/bundix/gemset.nix
@@ -6,7 +6,7 @@
   url = "https://github.com/cstrahan/bundix.git";;
   rev = "5df25b11b5b86e636754d54c2a8859c7c6ec78c7";
   fetchSubmodules = false;
-  sha256 = "0334jsavpzkikcs7wrx7a3r0ilvr5vsnqd34lhc58b8cgvgll47p";
+  sha256 = "1iqx12y777v8gszggj25x0xcf6lzllx58lmv53x6zy3jmvfh4siv";
 };
 dependencies = [
   "thor"
diff --git a/pkgs/development/interpreters/ruby/bundler-head.nix
b/pkgs/development/interpreters/ruby/bundler-head.nix
index 2e8cfc8..43a5961 100644
--- a/pkgs/development/interpreters/ruby/bundler-head.nix
+++ b/pkgs/development/interpreters/ruby/bundler-head.nix
@@ -5,7 +5,7 @@ buildRubyGem {
   src = fetchgit {
 url = "https://github.com/bundler/bundler.git";;
 rev = "a2343c9eabf5403d8ffcbca4dea33d18a60fc157";
-sha256 = "1l4r55n1wzr817l225l6pm97li1mxg9icd8s51cpfihh91nkdz68";
+sha256 = "1fywz0m3bb0fmcikhqbw9iaw67k29srwi8dllq6ni1cbm1xfyj46";
 leaveDotGit = true;
   };
   dontPatchShebangs = true;


-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Announcing New Ruby Support

[Cillian de Róiste]

Hi!

I thought I'd try to package jekyll, but I've run into some trouble...

2015-01-22 5:29 GMT+01:00 Charles Strahan :

> To use the new system, first create (or copy over) a Gemfile describing the
> required gems.
>

I grabbed the Gemfile from the github repo:
$ wget https://raw.githubusercontent.com/jekyll/jekyll/master/Gemfile

Next, create a Gemfile.lock by running `bundler package --no-install` in the
> containing directory (this also creates two folders - vendor and .bundle -
> which you'll want to delete before committing).
>

I had first installed pkgs.bundler, which got me version 1.7.9, which
doesn't have the --no-install option which seems to have been added in 1.8.
I then installed pkgs.bundler_HEAD which also reports the version to be
1.7.9 but does have the --no-install option. However, I got stuck on the
next step:

$ bundler package --no-install
There are no gemspecs at /home/goibhniu/ruby/jekyll.

I'm afraid I know very little about ruby or gems etc., so any help/pointers
would be appreciated.

Thanks!
Cillian


Now, you'll need to dump the lockfile as a Nix expression. To do so, use
> Bundix
> in the target directory:
>
>   $(nix-build '' -A bundix)/bin/bundix
>
> That will drop a gemset.nix file in your current directory, which
> describes the
> sources for all of the gems and their respective SHAs.
>
> Finally, you'll need to use bundlerEnv to build the gems. The following
> example
> is how we package the sup mail reader:
>
>   { stdenv, lib, bundlerEnv, gpgme, ruby, ncurses, writeText, zlib, xapian
>   , pkgconfig, which }:
>
>   bundlerEnv {
> name = "sup-0.20.0";
>
> inherit ruby;
> gemfile = ./Gemfile;
> lockfile = ./Gemfile.lock;
> gemset = ./gemset.nix;
>
> # This is implicit:
> #
> #   gemConfig = defaultGemConfig;
> #
> # You could just as well do the following:
> #
> #   gemConfig.ncursesw = spec: {
> # buildInputs = [ ncurses ];
> # buildFlags = [
> #   "--with-cflags=-I${ncurses}/include"
> #   "--with-ldflags=-L${ncurses}/lib"
> # ];
> #   };
> #
> # Where `spec` is the attributes of the corresponding gem,
> # in case you wanted to make something predicated on version,
> # for example.
> #
> # See default-gem-config.nix for more examples.
>
> meta = with lib; {
>   description = "A curses threads-with-tags style email client";
>   homepage= http://supmua.org;
>   license = with licenses; gpl2;
>   maintainers = with maintainers; [ cstrahan lovek323 ];
>   platforms   = platforms.unix;
> };
>   }
>
> And that's all there is to it!
>
> Enjoy,
>
> -Charles
>
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>


-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Call for participation at the Augsburger Linux-Infotag 2015 (Germany)

[Cillian de Róiste]

Hi,

2015-01-05 6:10 GMT+00:00 aszlig :
> Good morning,
>
> On Mon, Jan 05, 2015 at 01:22:53AM +0100, Ingo Blechschmidt wrote:
>> The deadline for applications is 2015-01-18.
>
> Great, so are any other Nixers interested in attending this? I think I'm
> pretty bad in doing speeches, so I'd appreciate if someone who is more
> experienced in doing talks would happen to be around.

This sounds like a really nice conference! I'd also like to get
involved. I'm happy to help out with a booth and a workshop, and I
would quite like to give a presentation (in English) but I also lack
experience with this.

Cheers,
Cillian

-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] after rebuild, grub says "error: symbol 'grub_term_highlight_color' not found"

[Cillian de Róiste]

Thanks for posting this James! I ran into the same thing today.
Luckily, I was able to work around it by changing the order of my
disks in BIOS.

On Wed, Sep 17, 2014 at 7:39 AM, James Cook  wrote:
> On 16 September 2014 21:11, James Cook  wrote:
>> Hi all,
>>
>> After updating from approximately 9cbc2165 (Aug 23) to b079eef31 (Sep
>> 16), instead of booting, my system gave the error message in the
>> subject.  It seems the same as
>> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977 and I
>> fixed it with the same solution (booting from a USB stick, sudo
>> grub-install --boot-directory=/mnt//boot /dev/sdX).
>>
>> I haven't seen this problem when updating in the past, so I am
>> guessing it is a bug.  Maybe we should wait and see if anyone else
>> sees it before devoting any energy to it though; in any case, it is
>> fixed for me for now.  (I'm not sure how to go about debugging it, but
>> I'll send another e-mail if I see the same problem again next time I
>> update.)
>>
>> James
>
> Okay, it looks like this was caused by /dev/sda and /dev/sdb changing
> places.  I guess I should be doing it by UUID or something.
>
> (I found the following errors at the end of nixos-rebuild's output; I
> guess I missed them before.)
>
> /nix/store/wkmf1mhwkjspdr1myhyalgyc7882q1k7-grub-2.02-git-1de3a4/sbin/grub-install:
> warning: this GPT partition label contains no BIOS Boot Partition;
> embedding won't be possible.
> /nix/store/wkmf1mhwkjspdr1myhyalgyc7882q1k7-grub-2.02-git-1de3a4/sbin/grub-install:
> error: embedding is not possible, but this is required for cross-disk
> install.
> /nix/store/pmashz5671fadjfyxaxf6r0bcz5839m4-install-grub.pl:
> installation of GRUB on /dev/sda failed
> warning: error(s) occured while switching to the new configuration
>
> James
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] configurations repository

[Cillian de Róiste]

On Tue, Nov 4, 2014 at 11:20 PM, Michael Raskin <7c6f4...@mail.ru> wrote:
>>That's awesome idea. But I think we have to add lots of comments to this
>>examples (that help a lot while using live code). Or maybe just provide
>>some ideal configs with comments and other without them.
>
> I think we need to throw some live configs like we had in SVN:
> https://nixos.org/websvn/nix/configurations/trunk/
>
> and then 1) there is an incentive to commit real configs when people ask
> questions, 2) we can add some ideal configs, maybe in a tutorial/
> subdirectory.

+1

I have learned (and borrowed) a lot from your configs in particular
Michael. Having some ideal configs would also be great. It should even
be pretty easy to add generic configurations which would be equivalent
to task specific distros that could simply be added to imports e.g. a
high security config or a pro-audio workstation config. Of course, the
ability to mix and match these in NixOS would be far superior to
running a separate distro for each task.



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Need help with virtualenv and python2.6

[Cillian de Róiste]

On Tue, Sep 16, 2014 at 12:23 AM, Cillian de Róiste
 wrote:
> Hi Jascha,
>
> I wonder how you have python2.7 stuff in the traceback. It seems to
> work fine for me:
>
> $ nix-shell -p python26Packages.virtualenv -p python26
>
> [nix-shell:~]$ virtualenv --python=python2.6 venv2.6test/
> Already using interpreter
> /nix/store/awjf2yn2gfsg0ai9klnpa29a1yx0g8wa-python-2.6.9/bin/python2.6
> New python executable in venv2.6test/bin/python2.6
> Also creating executable in venv2.6test/bin/python
> Installing setuptools, pip...done.
>
> [nix-shell:~]$ venv2.6test/bin/python
> Python 2.6.9 (unknown, Aug 12 2014, 14:10:05)
> [GCC 4.8.3] on linux3
> Type "help", "copyright", "credits" or "license" for more information.
>>>>

Also, when I run nix-shell as in your example:

$ nix-shell -p pythonPackages.virtualenvwrapper -p python26 -p
python27Packages.pip

[nix-shell:~]$ virtualenv --python=python2.6 venv2.6test2
Running virtualenv with interpreter
/nix/store/awjf2yn2gfsg0ai9klnpa29a1yx0g8wa-python-2.6.9/bin/python2.6
New python executable in venv2.6test2/bin/python2.6
Also creating executable in venv2.6test2/bin/python
Installing setuptools, pip...done.

[nix-shell:~]$ venv2.6test2/bin/python
Python 2.6.9 (unknown, Aug 12 2014, 14:10:05)
[GCC 4.8.3] on linux3
Type "help", "copyright", "credits" or "license" for more information.
>>>

>
> On Tue, Sep 16, 2014 at 12:02 AM, Jascha Geerds  wrote:
>> Any update on this topic? Same traceback occurs with vanilla virtualenv
>> (and not virtualenvwrapper).
>>
>> --
>>   Jascha Geerds
>>   j...@ekby.de
>> ___
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
>
> --
> NixOS: The Purely Functional Linux Distribution
> http://nixos.org



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Need help with virtualenv and python2.6

[Cillian de Róiste]

Hi Jascha,

I wonder how you have python2.7 stuff in the traceback. It seems to
work fine for me:

$ nix-shell -p python26Packages.virtualenv -p python26

[nix-shell:~]$ virtualenv --python=python2.6 venv2.6test/
Already using interpreter
/nix/store/awjf2yn2gfsg0ai9klnpa29a1yx0g8wa-python-2.6.9/bin/python2.6
New python executable in venv2.6test/bin/python2.6
Also creating executable in venv2.6test/bin/python
Installing setuptools, pip...done.

[nix-shell:~]$ venv2.6test/bin/python
Python 2.6.9 (unknown, Aug 12 2014, 14:10:05)
[GCC 4.8.3] on linux3
Type "help", "copyright", "credits" or "license" for more information.
>>>

On Tue, Sep 16, 2014 at 12:02 AM, Jascha Geerds  wrote:
> Any update on this topic? Same traceback occurs with vanilla virtualenv
> (and not virtualenvwrapper).
>
> --
>   Jascha Geerds
>   j...@ekby.de
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] DevOps sprint at gocept/FlyingCircus

[Cillian de Róiste]

Hi,

This is very exciting news indeed! I'll definitely attend the full
sprint (I'll register on meetup later). Looking forward to it!

Cheers,
Cillian


On Mon, Sep 8, 2014 at 11:06 AM, Rok Garbas  wrote:
> i think i'll be only able to come for fri/sat maybe i can come for later on
> thu but not 100%.
>
>
> --
> Rok Garbas - http://www.garbas.si
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] processing: new package

[Cillian de Róiste]

Hi,

It's the same package. I didn't notice the patch on the mailing list
and added graphic/processing myself yesterday. ewemoa (on IRC) pointed
out that it is useful to keep the processing_java script so I can
incorporate that. Were there any other parts of your expression that
you'd like to keep John?

Cheers,
Cillian


On Sun, Aug 31, 2014 at 1:00 PM, Peter Simons  wrote:
> Hi,
>
> how does this patch relate to pkgs/applications/graphics/processing?
>
> As it is now, the patch cannot be applied because both of these packages
> use the same attribute "processing" in all-packages.nix.
>
> Best regards,
> Peter
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Is xdebug working for you?

[Cillian de Róiste]

I've used xdebug recently, but I did need to update the paths in my config:

https://gitorious.org/goibhnix/configurations/commit/c84a8c4f3b642bd1deb0b3606a122bff6e9520a1

On Fri, Aug 15, 2014 at 4:18 PM, Marc Weber  wrote:
> Is anybody using xdebug?
>
> The change making PECL build it broke it for me.
> This code http://dpaste.com/2HEZVNG still works fine.
>
> Maybe I have to configure it in a different way when it gets build by
> PECL?
>
> Marc Weber
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOS on MacBook dual boot

[Cillian de Róiste]

Hi Alexey,

Try removing the quotes:

boot.extraModulePackages = [ config.boot.kernelPackages.broadcom-sta ];

I guess there's a problem with nixos-generate-config.

Cheers,
Cillian


On Wed, Aug 13, 2014 at 9:08 AM, Alexey Muranov
 wrote:
> On 12 août 2014, at 22:27, Paul Colomiets  wrote:
>
>> You don't need another EFI
>> partition, nixos should put it's own kernel into existing EFI
>> partition, just mount it as /boot.
>
> Should i mount it before running `nixos-generate-config`? If so, should i 
> mount it at /boot or at /mnt/boot?
>
> I have tried just the following sequence of commands:
>
> # swapon /dev/disk/by-lablel/swap
> # mount /dev/disk/bt-label/nixos /mnt
> # nixos-generate-config --root /mnt
> # nixos-install
>
> It failed with the messages:
>
> building the system configuration...
> error: while evaluating the attribute `buildCommand' of the derivation
> `nixos-14.04.291.a4ac76b' at
> /mnt-nixpkgs/nixos/modules/system/activation/top-level.nix:100:7:
> [...]
> The option value `boot.extraModulePackages' in
> `/etc/nixos/hardware-configuration.nix' is not a list of paths.
>
> I checked my hardware-configuration.nix, there i had
>
> boot.extraModulePackages = [ "config.boot.kernelPackages.broadcom-sta" ];
>
> The `fileSystems` option had a single element:
>
> fileSystems."/" =
>   { device = "/dev/sda5";
> fsType = "ext4";
>   }
>
> What is wrong?
>
> Alexey.
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] thermald.nix

[Cillian de Róiste]

Hi Thomas,

Thanks for your contributions! It would be easier for maintainers to
review and accept them if you used github pull requests. Could you do
that instead of sending them as attachments?

Cheers,
Cillian

On Sun, Aug 3, 2014 at 11:20 PM, Thomas Strobel  wrote:
> Hi,
>
> maybe someone interested in pushing the .nix file for thermald online?
> It's maybe not the latest version, and the systemd integration is quite
> basic, but it works. It might benefit from a change in the kernel's
> default configuration, though.
>
> Best wishes,
> Thomas
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nixos basic Qs

[Cillian de Róiste]

On Thu, Jul 31, 2014 at 10:45 PM, Ben B  wrote:
...
> - the 'locate' command doesn't work.  According to google I should run
> updatedb to make it work, however that gives me a 'readonly filesystem' error.

It also bears mentioning that after enabling the locate service, you
can manually update the database at any time using: `systemctl start
update-locatedb`

Cheers,
Cillian
-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Using python27 impurely on nixos

[Cillian de Róiste]

On Fri, Jul 18, 2014 at 8:23 AM, Cody Goodman
 wrote:
> I have a python project for the first time since I started using
> nixos. I would like to simply use this example:
>
>
> https://nixos.org/wiki/Howto_develop_software_on_nixos#Example_4:_Python_Web_Development_Nixos_Container
>
>environment = {
>  systemPackages = with pkgs; [
>git
>libxml2
>libxslt
>libzip
>python27Full
>python27Packages.virtualenv
>stdenv
>zlib
>  ];
>
>  pathsToLink = [ "/include" ];
>
>  shellInit =
># help pip to find libz.so when building lxml
>export LIBRARY_PATH=/var/run/current-system/sw/lib
># ditto for header files, e.g. sqlite
>export C_INCLUDE_PATH=/var/run/current-system/sw/include
>  ;
>};
>
> However I'm not sure where to put this code. It also seems like a few
> lines are missing at the top. Should this be named? I have no idea how
> to use this to get an impure pip-installable environment. Can anyone
> help?

There are a few different ways to use containers:
http://nixos.org/nixos/manual/#ch-containers so you should be able to
plug this in to the relevant environment section.

I use this configuration myself regularly, so let me know if you run
into trouble.

Good luck!
Cillian

-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Hi, I'm new!

[Cillian de Róiste]

Hi Matthias,

Feel free to ask questions on the mailing list, and on the #nixos
channel on freenode (http://webchat.freenode.net/?channels=#nixos) but
it's worth mentioning too that the manual and academic papers have a
wealth of information, so, you will probably find most questions you
have are already answered there in great depth.

Welcome aboard!
Cillian


On Sun, Jun 29, 2014 at 11:01 AM, Matthias Beyer  wrote:
> Hi,
>
> I don't know if this is wanted on this list (isn't there a users-list
> somewhere?), but I want to introduce myself before sending my bunch of
> questions!
>
> I'm a 22 year old CS student from south germany. I heard from nixos
> the first time at UnFUCK[0], a conference at my university, I
> organized myself. ATM I'm an Archlinux user (been for ~7 years), but
> within the next year I want to build a Tower-PC and I'm heavily
> thinking about nixos for it.
>
> For me, nixos is the first _real_ approach to solve the
> dependency-hell problem.
>
> Is it appropriate to send my questions to this ML? I guess I will send
> them in seperate mails if you ACK this, as some of them may lead to
> longer discussuions (who knows).
>
> So, ... Hi nixos ML! Ask me anything.
>
> [0]: unfuck.eu
>
> --
> Mit freundlichen Grüßen,
> Kind regards,
> Matthias Beyer
>
> Proudly sent with mutt.
> Happily signed with gnupg.
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>



-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] rebuild impact factor

[Cillian de Róiste]

On Tue, Jun 24, 2014 at 10:01 AM, Ludovic Courtès  wrote:
> Florian Friesdorf  skribis:
>
>> it would be nice if github would show a "rebuild impact factor"?
>
> In the old days, Nicolas Pierron wrote a script that attempted to
> compute that factor, maintainers/scripts/rebuild-amount.sh.

I never noticed this script before (it looks very useful!), but I've
been following the manual steps listed on
https://nixos.org/wiki/Contributing#How_to_verify_that_you_didn.27t_break_a_dependency_or_the_evaluation_by_accident_.3F
as a sanity check, which includes a step to rebuild everything
affected by the change.

I guess it would be a bit lame, but we could use Travis to calculate
the amount of rebuilds required. I discussed the possibility of using
monitor.nixos.org to calculate this for pull requests with Evgeny
(phreedom) on IRC before, but he felt it would be too expensive, and
(IIRC) a bit out of scope for the monitor project (which I have been
missing greatly for the past number of weeks, I hope it gets well
soon!).

Cheers,
Cillian

-- 
NixOS: The Purely Functional Linux Distribution
http://nixos.org
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] nixos-rebuild switch fails with grub errro

[Cillian de Róiste]

Hi,

I think you missed the section in the manual about using gummiboot
(1.2.1. UEFI Installation).

Cheers,
Cillian

On Wed, Jun 18, 2014 at 12:19 PM, Cody Goodman
 wrote:
> After following usb/efi install instructions I get this error:
>
> $ nixos-rebuild switch
> building Nix...
> building the system configuration...
> updating Grub 2 menu...
> installing the GRUB 2 boot loader on /dev/sda...
> source_dir doesn't exist. Please specify --target or --directory
> /nix/store/bv72ysa59y67hvpl5czxi429wrn5n98h-install-grub.pl:
> installation of GRUB on /dev/sda failed
>
> Here is information I thought was relevant. If I missed anything let
> me know and I'll include it.
>
> my nix configuration:
>
> # Edit this configuration file to define what should be installed on
> # your system.  Help is available in the configuration.nix(5) man page
> # and in the NixOS manual (accessible by running ‘nixos-help’).
>
> { config, pkgs, ... }:
>
> {
>   imports =
> [ # Include the results of the hardware scan.
>   ./hardware-configuration.nix
> ];
>
>   # Use the GRUB 2 boot loader.
>   boot.loader.grub.enable = true;
>   boot.loader.grub.version = 2;
>   # Define on which hard drive you want to install Grub.
>   boot.loader.grub.device = "/dev/sda";
>
>   nixpkgs.config.allowUnfree = true;
>
>
>   networking.hostName = "cody-nixos"; # Define your hostname.
>   networking.wireless.enable = true;  # Enables wireless.
>
>   # Select internationalisation properties.
>   # i18n = {
>   #   consoleFont = "lat9w-16";
>   #   consoleKeyMap = "us";
>   #   defaultLocale = "en_US.UTF-8";
>   # };
>
>   # List services that you want to enable:
>
>   # Enable the OpenSSH daemon.
>   # services.openssh.enable = true;
>
>   # Enable CUPS to print documents.
>   # services.printing.enable = true;
>
>   # Enable the X11 windowing system.
>   services.xserver.enable = true;
>   services.xserver.autorun = true;
>   services.xserver.synaptics.enable = true;
>   services.xserver.synaptics.twoFingerScroll = true;
>   services.xserver.videoDrivers = ["nvidia"];
>   services.xserver.layout = "us";
>   services.xserver.xkbOptions = "ctrl:swapcaps";
>
>   # Enable xmonad
>   services.xserver.windowManager.xmonad.enable = true;
>   services.xserver.windowManager.default = "xmonad";
>   services.xserver.desktopManager.default = "none";
>
>   # Enable the KDE Desktop Environment.
>   # services.xserver.displayManager.kdm.enable = true;
>   # services.xserver.desktopManager.kde4.enable = true;
>
>  environment.systemPackages = with pkgs; [
>  bumblebee
>
>  dmenu
>  haskellPlatform
>  haskellPackages.xmobar
>  haskellPackages.xmonadContrib
>  haskellPackages.xmonadExtras
>  trayer
>
>  rxvt_unicode
>  vim
>  emacs
>  git
>
>  firefox
>  # icedove
>
>  # utilities
>  xclip
>  #virtualbox
>  ];
>  users.extraUsers.cody =
>  { createHome = true;
>home = "/home/cody";
>description = "Cody Goodman";
>extraGroups = [ "wheel" ];
>useDefaultShell = true;
>  };
> }
>
>
> hardware-configuration.nix:
>
> # Do not modify this file!  It was generated by ‘nixos-generate-config’
> # and may be overwritten by future invocations.  Please make changes
> # to /etc/nixos/configuration.nix instead.
> { config, pkgs, ... }:
>
> {
>   imports =
> [ 
> ];
>
>   boot.initrd.availableKernelModules = [ "xhci_hcd" "ehci_pci" "ahci"
> "usb_storage" ];
>   boot.kernelModules = [ "kvm-intel" ];
>   boot.extraModulePackages = [ ];
>
>   fileSystems."/" =
> { device = "/dev/sda9";
>   fsType = "ext4";
> };
>
>   swapDevices =[ ];
>
>   nix.maxJobs = 4;
> }
>
> partition information:
>
> Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 4096 bytes
> I/O size (minimum/optimal): 4096 bytes / 4096 bytes
> Disklabel type: gpt
> Disk identifier: 7F6EA309-1BAB-4D4A-9090-5F8ED70708C7
>
> DeviceStart  End   Size Type
> /dev/sda1  2048   616447   300M EFI System
> /dev/sda2616448  2459647   900M Windows recovery environment
> /dev/sda3   2459648  2721791   128M Microsoft reserved
> /dev/sda4   2721792325502975 153.9G Microsoft basic data
> /dev/sda5 518346752783972351 126.7G Microsoft basic data
> /dev/sda6 32550297651834675192G Microsoft basic data
> /dev/sda7 944291840   1219860479 131.4G Microsoft basic data
> /dev/sda81219860480   1234509823 7G Linux swap
> /dev/sda91234509824   1464227839 109.6G Linux filesystem
> /dev/sda10   1464227840   1465149134 449.9M EFI System
> /dev/sda11783972352944291839  76.5G Microsoft basic data
>
>
> Disk /dev/sdb: 14.9 GiB, 16026435072 bytes, 31301631 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 

Re: [Nix-dev] Restructuring of the Wiki

[Cillian de Róiste]

For reference, here's the discussion from the last time the topic of
changing wiki platform came up, last year:
http://lists.science.uu.nl/pipermail/nix-dev/2013-March/010800.html
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Wx and Erlang

[Cillian de Róiste]

Hi,

You can put the following in your configuration.nix:

nixpkgs.config.packageOverrides = pkgs: {
  erlang_wx = erlang.override { wxSupport = true; };
};

I notice that `man configuration.nix` mentions packageOverrides is
described in the nixpkgs documentation, but I don't see it there.
Here's an example of something similar from the wiki:
https://nixos.org/wiki/How_to_enable_subpixel_rendering_in_freetype

Cheers,
Cillian

On Thu, May 1, 2014 at 4:57 AM, Strahinja Popovic  wrote:
> Hi,
>
> Graphical debugger for erlang is not working for me, giving following
> message:
>
> ERROR: Could not find 'wxe_driver.so' in:
> /nix/store/qwrw86k079q2klczqcfb38abgib19hfx-erlang-15B03/lib/erlang/lib/wx-0.99.2/priv
>
> In SVN revision 34372, cillian has added wxSupport to erlang, and I believe
> that this mostly would solve my problem.
> I have tried to enable this with  'nix-env --set-flag wxSupport true
> erlang',
> but this was a long-shot, and it didn't work.
>
> How should I set this?
>
> Best,
> Strahinja
>
> ___
> 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] Problems installing NixOS with btrfs from a USB stick

[Cillian de Róiste]

Hi!

On Sun, Apr 13, 2014 at 11:05 AM, Thomas Strobel  wrote:
> Hi there,
>
> I was running into problems when trying to install NixOS with btrfs from
> a USB stick. I downloaded the current .iso and used unetbootin to create
> a bootable USB drive from it.
>
> Unfortunately, the resulting installation environment did not allow to
> use mkfs.btrfs as it could not decide on the mounting status of my
> partition. It seemed as if unetbootin prepared the system in a way that
> prevented mkfs.btrfs from working.
>
> Did anyone else experience that problem?
>
> If so, then my question is if the .iso files could be changed in a way
> that allows to prepare the USB stick with a simple dd-command, e.g. like
> Debian or GRML ISOs do, and that keeps mkft.btrfs working?

You could try installing syslinux and using isohybrid to create a
hybrid bootable image which you can dd onto a USB stick:

isohybrid filename.iso

http://www.syslinux.org/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE

I'm not sure if that will help with the btrfs issue, but it would be
good to know if it worked.

Good luck!
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] nix-shell NetworkManager

[Cillian de Róiste]

Hi,

I don't know the answer to your question, but just in case you overlooked
it, your user needs to be a member of the networkmanager group to be able
to use NetworkManager.

Cheers,
Cillian


On Sun, Feb 16, 2014 at 8:08 PM, Sergey Mironov  wrote:

> 2014-02-16 22:44 GMT+04:00 Sergey Mironov :
> > Hi! I tried debug a nasty NetworkManager "(32) insufficient
> > privileges" problem by building my own hacked version of the package.
> > I called nix-shell and tried to build the sources. Both patchPhase and
> > configurePhase run without problems, but buildPhase stoppes with an
> > error saying
> >
> >
> /nix/store/k4bh0a5rffwa9xhxfzld1fvr0z628klz-dbus-glib-0.100.2/include/dbus-1.0/dbus/dbus-glib.h:28:30:
> > fatal error: dbus/dbus-shared.h: No such file or directory
> >
> >
> > That is strange because nix-shell set the NIX_CFLAGS_COMPILE variable
> > correctly (it contains
> > -I/nix/store/k4bh0a5rffwa9xhxfzld1fvr0z628klz-dbus-glib-0.100.2/include
> > -I/nix/store/mv8dsy1q29ph6hdk6c96f252ww89z27m-dbus-libs-1.6.14/include
> > among others)
> >
> > What may go wrong? Who are in charge of reading the NIX_CFLAGS_COMPILE?
> >
> > Regards,
> > Sergey
>
> I think I need to clarify my previous letter: In order to hack
> NetworkManager, I start nix-shell and then call the pases directly,
> like
> $ patchPahse
> $ configurePhase
> $ buildPhase
> ...
>
> /nix/store/k4bh0a5rffwa9xhxfzld1fvr0z628klz-dbus-glib-0.100.2/include/dbus-1.0/dbus/dbus-glib.h:28:30:
> fatal error: dbus/dbus-shared.h: No such file or directory
> $ echo $NIX_CFLAGS_COMPILE
> -Ithis -Ithat
> -I/nix/store/k4bh0a5rffwa9xhxfzld1fvr0z628klz-dbus-glib-0.100.2/include
> ...
>
> Regards,
> Sergey
> ___
> 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] xmlstarlet version update

[Cillian de Róiste]

Applied, thanks!


On Tue, Feb 11, 2014 at 4:35 PM, Karn Kallio wrote:

>
> Patch to advance xmlstarlet to latest version 1.5.0.
>
> ___
> 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] FOSDEM: any plans for Saturday evening?

[Cillian de Róiste]

It looks like we have 4-6 people interested. That's great! I guess we don't
really need to make a reservation, just go to a part of town with a lot of
restaurants, but if anyone has a suggestion for a restaurant or bar all the
better.

The talks should be finished by 19:00 so why don't we meet up at the main
infodesk shortly afterwards and take it from there?:
https://fosdem.org/2014/practical/transportation/



On Thu, Jan 23, 2014 at 4:00 PM, Bas van Dijk  wrote:

> That would be really nice! Count me in.
>
> Bas
>
> On 22 January 2014 13:50, Cillian de Róiste 
> wrote:
> > Hi,
> >
> > Since there will be quite a few NixOS and Guix folks at FOSDEM it would
> be
> > great to meet up. Is there some interest in arranging dinner / drinks on
> > Saturday evening?
> >
> > Cheers,
> > Cillian
> >
> > ___
> > 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 mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Complete configuration

[Cillian de Róiste]

Hi Jeremy,

To reproduce the system you just need to copy the configuration and use the
same revision of nixpkgs. You can see that at the end of `nixos-version`.

Cheers,
Cillian



On Mon, Jan 27, 2014 at 10:05 AM, Peter Simons  wrote:

> Hi Jeremy,
>
> you might like the 'nixos-option' command.
>
> Take care
> 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] Google Talk Plugin and X11 packages obsolete

[Cillian de Róiste]

Hi Raahul,

I think you just need to put firefoxWrapper into systemPackages, you can
also put the other packages in there and get rid of x11Packages.

Cheers,
Cillian


On Fri, Jan 24, 2014 at 2:26 PM, Raahul Kumar wrote:

> Hi,
>
> My Gtalk plugin doesn't work in Firefox. What settings do I need to add?
> My config file is below.
> I also get a warming about x11Packages being obsolete. What do I replace
> that with?
>
>
>
> # Edit this configuration file to define what should be installed on
> # your system.  Help is available in the configuration.nix(5) man page
> # and in the NixOS manual (accessible by running ‘nixos-help’).
>
> { config, pkgs, ... }:
>
>
> {
>   imports =
> [ # Include the results of the hardware scan.
>   ./hardware-configuration.nix
> ];
>
>
>
>   # Use the GRUB 2 boot loader.
>   boot.loader.grub.enable = true;
>   boot.loader.grub.version = 2;
>   # Define on which hard drive you want to install Grub.
>boot.loader.grub.device = "/dev/sda";
>
>networking.hostName = "Zangetsu"; # Define your hostname.
>   # networking.wireless.enable = true;  # Enables wireless.
>
>   # Select internationalisation properties.
>   # i18n = {
>   #   consoleFont = "lat9w-16";
>   #   consoleKeyMap = "us";
>   #   defaultLocale = "en_US.UTF-8";
>   # };
>
>   # List services that you want to enable:
>
>   # Enable the OpenSSH daemon.
>   # services.openssh.enable = true;
>
>   environment = {
> systemPackages = with pkgs; [
>   emacs
>   mercurial
>   irssi
>   gitFull
>   file
>   xz
>   openldap
>   gnupg
>   gnumake
>   clang
>   ncurses
>   wget
>   jdk
>   unzip
>   ant
>   manpages
>   posix_man_pages
>   patchelf
>   python
>   gdb
>   openssl
>   subversion
>   cmake
> ];
>
> x11Packages = with pkgs; [
>   firefox
>   thunderbird
>   pidgin
>   libreoffice
>   qemu_kvm
>   dwm
>   dmenu
>   evince
> ];
>   };
>
>   time.timeZone = "Australia/Brisbane";
>
>
>   # Enable CUPS to print documents.
>   services.printing.enable = true;
>
>   nixpkgs.config.firefox.enableGoogleTalkPlugin = true;
>
>   # Enable the X11 windowing system.
>services.xserver.enable = true;
>services.xserver.layout = "us";
>services.xserver.xkbOptions = "eurosign:e";
>
>   # Enable the KDE Desktop Environment.
>services.xserver.displayManager.kdm.enable = true;
>services.xserver.desktopManager.kde4.enable = true;
> }
>
>
> ___
> 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] Testing with nixpkgs and nixos for a degree thesis

[Cillian de Róiste]

Hi Luigi,

That sounds like a very interesting thesis and nix should do very well
according to your criteria. I had a quick look at some of the failures and
suspect they could be easily solved, e.g. bfast can't find bzlib.h but
adding bzip2 to the build inputs should fix that. I'm sure we could fix the
rest of the issues too, and it would be nice to have the extra packages in
nixpkgs since you've already done to work to package and test them. It
would be great if you could open a pull request with the working packages,
and then also ask for help with the problematic ones individually. I hope
that's not too much effort. If you want to quickly work through the issues
it might be best to ask on the IRC channel #nixos on freenode.

Good luck!
Cillian



On Fri, Jan 24, 2014 at 12:48 AM, Luigi Viscardi <
luigi.visca...@studenti.unimi.it> wrote:

> Hi,
>
> I am Luigi Viscardi I am developing a degree thesis in Computer Science at
> the University of Milan.
> At this link you can see the thesis proposal, carried out under the
> project "Cloudbiolinux"
>
> *https://groups.google.com/d/msg/cloudbiolinux/xpEWSS6iC54/4qSt30UB56oJ
>  *
>
> A part of this work is to compare different solutions to the problems of
> "versioning" and "reproducibility".
> To do this, I did some testing with the package "nixpkgs" and others in
> the  "nixos" environment,
> to understand how they work and what are their potential.
> Some of these tests have been completed successfully, but some others have
> failed.
>
> On the attachment you can see the tests, the results and some comments.
> Could you give me a help to try to solve the problems occurring?
>
> Thanks for any suggestions,
> Luigi Viscardi
>
>
>
>
> ___
> 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] FOSDEM: any plans for Saturday evening?

[Cillian de Róiste]

Hi,

Since there will be quite a few NixOS and Guix folks at FOSDEM it would be
great to meet up. Is there some interest in arranging dinner / drinks on
Saturday evening?

Cheers,
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] dconf build problem

[Cillian de Róiste]

"checking for pkg-config... no" looks suspicious, try adding pkgconfig as a
buildInput


On Wed, Dec 11, 2013 at 2:35 PM, Roelof Wobben  wrote:

> Hello,
>
> When I try to port Dcon to Nixos  I see this error :
>
> checking for gcc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... none
> checking for valac...
> /nix/store/90ig8w0fmm39pk5n5154h1rva02h8nsq-vala-0.19.0/bin/valac
> checking whether
> /nix/store/90ig8w0fmm39pk5n5154h1rva02h8nsq-vala-0.19.0/bin/valac is at
> least version 0.17.0... yes
> checking for ranlib... ranlib
> checking for xsltproc...
> /nix/store/az650mkm365nrjawxpycq71xj3f1yzqy-libxslt-1.1.27/bin/xsltproc
> checking for glib-compile-resources... no
> checking for pkg-config... no
> ./configure: line 4375: --variable: command not found
> configure: error: glib-compile-schemas not found.
> builder for `/nix/store/m7y21fxm446zk0gfkdrnl64bjbbzsnhk-dconf-0.18.0.drv'
> failed with exit code 1
> error: build of
> `/nix/store/m7y21fxm446zk0gfkdrnl64bjbbzsnhk-dconf-0.18.0.drv' failed
>
>
> I have this derivation :
>
> { stdenv, fetchurl, makeWrapper, cinnamon-desktop, glib, libxslt, vala}:
>
> let
>   version = "0.18.0";
> in
> stdenv.mkDerivation rec {
>   name = "dconf-${version}";
>
>   src = fetchurl {
> url = "http://download.gnome.org/sources/dconf/0.18/${name}.tar.xz";;
> sha256 =
> "109b1bc6078690af1ed88cb144ef5c5aee7304769d8bdc82ed48c3696f10c955";
>   };
>
>
>   buildInputs = [
> makeWrapper libxslt vala
> ];
>
>   preBuild = "patchShebangs ./scripts";
>
>
>   postInstall  = ''
> ${glib}/bin/glib-compile-schemas $out/share/glib-2.0/schemas/
> rm $out/share/icons/hicolor/icon-theme.cache
>
> for f in "$out"/bin/*; do
>   wrapProgram "$f" --prefix XDG_DATA_DIRS :
> "$out/share:${cinnamon-desktop}/share"
> done
>   '';
>
>   meta = {
> homepage = "http://live.gnome.org/dconf";;
> description = "A low level configuration system" ;
>
> platforms = stdenv.lib.platforms.linux;
> maintainers = [ stdenv.lib.maintainers.roelof ];
>   };
> }
>
> Roelof
>
> ___
> 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] called without required argument `cinnamon-settings-daemon'

[Cillian de Róiste]

cinnamon-setttings-daemon =
../desktops/cinnamon/cinnamon-settings-daemon.nix { } ;

setttings should only have two "t"s


On Thu, Dec 5, 2013 at 2:13 PM, Roelof Wobben  wrote:

> hello,
>
> I have this derivation :
>
> { stdenv, fetchurl, pkgconfig, autoreconfHook, glib, gettext, gnome_common,
> intltool, systemd, libxslt, gtk3, libnotify, cinnamon-desktop, gnome-menus,
> libxml2, upower, cinnamon-settings-daemon }:
>
> let
>   version = "2.0.9";
> in
> stdenv.mkDerivation {
>   name = "cinnamon-control-center-${version}";
>
>   src = fetchurl {
> url = "
> http://github.com/linuxmint/cinnamon-control-center/archive/${version}.tar.gz
> ";
> sha256 = "0kivqdgsf8w257j2ja6fap0dpvljcnb9gphr3knp7y6ma2d1gfv3";  };
>
>   configureFlags = "--enable-systemd --disable-update-mimedb " ;
>
>   patches = [ ./region.patch];
>
>   buildInputs = [
> pkgconfig autoreconfHook
> glib gettext gnome_common
> intltool systemd libxslt
> gtk3 libnotify cinnamon-desktop
> gnome-menus libxml2 upower
> cinnamon-settings-daemon
> ];
>
>   preBuild = "patchShebangs ./scripts";
>
>
>  meta = {
> homepage = "http://cinnamon.linuxmint.com";;
> description = "the cinnamon control center " ;
>
> platforms = stdenv.lib.platforms.linux;
> maintainers = [ stdenv.lib.maintainers.roelof ];
>   };
> }
>
> And I have this in my all-packages.nix:
>
>  cinnamon = recurseIntoAttrs rec{
> callPackage=pkgs.newScope pkgs.cinnamon;
> inherit (gnome3) gnome_common ;
> cinnamon-control-center = callPackage
> ../desktops/cinnamon/cinnamon-control-center.nix{ };
> cinnamon-desktop = callPackage
> ../desktops/cinnamon/cinnamon-desktop.nix { };
> gnome-menus = callPackage ../desktops/cinnamon/gnome-menus.nix { } ;
> cinnamon-setttings-daemon =
> ../desktops/cinnamon/cinnamon-settings-daemon.nix { } ;
>  };
>
>
> But stIl I see this error :
>
> error: an anonymous function at
> `/home/roelof/nixpkgs/pkgs/desktops/cinnamon/cinnamon-control-center.nix:1:1'
> called without required argument `cinnamon-settings-daemon'
> (use `--show-trace' to show detailed location information)
>
>
> Roelof
>
> ___
> 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] gnome-menus

[Cillian de Róiste]

It mustn't be packaged yet.

$ nix-env -qaP | grep menus
nixos.pkgs.gnome.gnome_menus
gnome-menus-2.30.5



On Wed, Dec 4, 2013 at 2:30 PM, Roelof Wobben  wrote:

> When I changed it to this :
>
> inherit (gnome3) gnome_common gnome_menus ;
>
> Then I see this message:
>
> error: attribute `gnome_menus' missing
>
> Roelof
>
> --
> Date: Wed, 4 Dec 2013 14:23:40 +0100
> Subject: Re: [Nix-dev] gnome-menus
> From: cillian.deroi...@gmail.com
> To: rwob...@hotmail.com
> CC: nix-dev@lists.science.uu.nl
>
>
> It'd probably unrelated, but shouldn't you be inheriting from gnome3
> rather than gnome?
>
> On Wed, Dec 4, 2013 at 2:12 PM, Roelof Wobben  wrote:
>
>
>
> > Date: Wed, 4 Dec 2013 13:59:17 +0100
> > Subject: Re: [Nix-dev] gnome-menus
> > From: math...@bluescreen303.nl
> > To: rwob...@hotmail.com
> > CC: nix-dev@lists.science.uu.nl
>
> >
> > inherit it from gnome2 or gnome3
> >
>
> Oke,  I changed my derivation to this :
>
> { stdenv, fetchurl, pkgconfig, autoreconfHook, glib, gettext,
> gnome_common, intltool, libxslt,
> gtk3, cinnamon-desktop, libnotify, gnome_menus }:
>
> let
>   version = "2.0.9";
> in
> stdenv.mkDerivation {
>   name = "cinnamon-control-center-${version}";
>
>   src = fetchurl {
> url = "
> http://github.com/linuxmint/cinnamon-control-center/archive/${version}.tar.gz
> ";
> sha256 = "0kivqdgsf8w257j2ja6fap0dpvljcnb9gphr3knp7y6ma2d1gfv3";
>   };
>
>
>   configureFlags = "--enable-systemd --disable-update-mimedb " ;
>
>   patches = [ ./region.patch];
>
>   buildInputs = [
> pkgconfig autoreconfHook
> glib gettext gnome_common
> intltool libxslt
> gtk3  cinnamon-desktop libnotify
> gnome_menus
> ];
>
>   preBuild = "patchShebangs ./scripts";
>
>
>  meta = {
> homepage = "http://cinnamon.linuxmint.com";;
> description = "the cinnamon settings daemon " ;
>
> platforms = stdenv.lib.platforms.linux;
> maintainers = [ stdenv.lib.maintainers.roelof ];
>   };
> }
>
> and all-packages to this :
>
>  cinnamon = recurseIntoAttrs rec{
> callPackage=pkgs.newScope pkgs.cinnamon;
> inherit (gnome) gnome_common gnome_menus ;
> cinnamon-control-center = callPackage
> ../desktops/cinnamon/cinnamon-control-center.nix{ };
> cinnamon-desktop = callPackage
> ../desktops/cinnamon/cinnamon-desktop.nix { } ;
>  };
>
>
> But still this error :
>
> hecking for pkg-config...
> /nix/store/sjg0j92drrip1pch65srsxa9jw0zq4g6-pkg-config-0.23/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for LIBCINNAMON_CONTROL_CENTER... yes
> checking for LIBLANGUAGE... yes
> checking for LIBSHORTCUTS... yes
> checking for SHELL... configure: error: Package requirements (gtk+-3.0 >=
> 3.4.2
>  glib-2.0 >= 2.31.0
>  gthread-2.0
>  gio-2.0
>  gio-unix-2.0
>  cinnamon-desktop >= 1.0.0
>  libnotify >= 0.7.3 libgnome-menu-3.0 gio-unix-2.0 x11) were not met:
>
> No package 'libgnome-menu-3.0' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables SHELL_CFLAGS
> and SHELL_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> Roelof
>
>
>
> ___
> 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 mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] gnome-menus

[Cillian de Róiste]

It'd probably unrelated, but shouldn't you be inheriting from gnome3 rather
than gnome?

On Wed, Dec 4, 2013 at 2:12 PM, Roelof Wobben  wrote:

>
>
> > Date: Wed, 4 Dec 2013 13:59:17 +0100
> > Subject: Re: [Nix-dev] gnome-menus
> > From: math...@bluescreen303.nl
> > To: rwob...@hotmail.com
> > CC: nix-dev@lists.science.uu.nl
>
> >
> > inherit it from gnome2 or gnome3
> >
>
> Oke,  I changed my derivation to this :
>
> { stdenv, fetchurl, pkgconfig, autoreconfHook, glib, gettext,
> gnome_common, intltool, libxslt,
> gtk3, cinnamon-desktop, libnotify, gnome_menus }:
>
> let
>   version = "2.0.9";
> in
> stdenv.mkDerivation {
>   name = "cinnamon-control-center-${version}";
>
>   src = fetchurl {
> url = "
> http://github.com/linuxmint/cinnamon-control-center/archive/${version}.tar.gz
> ";
> sha256 = "0kivqdgsf8w257j2ja6fap0dpvljcnb9gphr3knp7y6ma2d1gfv3";
>   };
>
>
>   configureFlags = "--enable-systemd --disable-update-mimedb " ;
>
>   patches = [ ./region.patch];
>
>   buildInputs = [
> pkgconfig autoreconfHook
> glib gettext gnome_common
> intltool libxslt
> gtk3  cinnamon-desktop libnotify
> gnome_menus
> ];
>
>   preBuild = "patchShebangs ./scripts";
>
>
>  meta = {
> homepage = "http://cinnamon.linuxmint.com";;
> description = "the cinnamon settings daemon " ;
>
> platforms = stdenv.lib.platforms.linux;
> maintainers = [ stdenv.lib.maintainers.roelof ];
>   };
> }
>
> and all-packages to this :
>
>  cinnamon = recurseIntoAttrs rec{
> callPackage=pkgs.newScope pkgs.cinnamon;
> inherit (gnome) gnome_common gnome_menus ;
> cinnamon-control-center = callPackage
> ../desktops/cinnamon/cinnamon-control-center.nix{ };
> cinnamon-desktop = callPackage
> ../desktops/cinnamon/cinnamon-desktop.nix { } ;
>  };
>
>
> But still this error :
>
> hecking for pkg-config...
> /nix/store/sjg0j92drrip1pch65srsxa9jw0zq4g6-pkg-config-0.23/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for LIBCINNAMON_CONTROL_CENTER... yes
> checking for LIBLANGUAGE... yes
> checking for LIBSHORTCUTS... yes
> checking for SHELL... configure: error: Package requirements (gtk+-3.0 >=
> 3.4.2
>  glib-2.0 >= 2.31.0
>  gthread-2.0
>  gio-2.0
>  gio-unix-2.0
>  cinnamon-desktop >= 1.0.0
>  libnotify >= 0.7.3 libgnome-menu-3.0 gio-unix-2.0 x11) were not met:
>
> No package 'libgnome-menu-3.0' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables SHELL_CFLAGS
> and SHELL_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> Roelof
>
>
>
> ___
> 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] what is the best way to keep my box up-to-date

[Cillian de Róiste]

Hi Roelof,

`nixos-rebuild switch --upgrade` will update your system.

https://nixos.org/wiki/Create_and_debug_nix_packages has some handy tips on
how to work on new packages and take advantage of the binaries available in
the channel.

Cheers,
Cillian


On Fri, Nov 22, 2013 at 5:13 PM, Roelof Wobben  wrote:

> Hello,
>
> the first question is how I can take care that my NixOS up-to-date.
>
> Second question : what is the best way to keep the pkgs directory
> up-to-date.
> So I know that when Im  porting something I will be with the latest
> software.
>
> Roelof
> ___
> 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] Wiki spam

[Cillian de Róiste]

On Wed, Nov 13, 2013 at 4:12 PM, Eelco Dolstra
wrote:

> Hi all,
>
> I've done another purge of spam pages / accounts on the wiki [1].  Let's
> try to
> keep it spam-free this time :-)  If you care about making/keeping the wiki
> useful and want to help, please let me know and I can give you access
> rights to
> block spammers and all that.
>

This is great, thanks! I would love to join the fight against spam, my wiki
user is: Goibhniu



> I've also enabled the spam blacklist extension
> (http://www.mediawiki.org/wiki/Extension:SpamBlacklist), which might help
> a bit.
>
> [1] Mostly done by deleting almost all pages that had no incoming links.
> Hopefully I didn't delete any legitimate content :-)  Please make sure
> that when
> you add a page, it is linked from another article.  Otherwise it may get
> nuked
> in the future.
>
> --
> 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
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] google-talk-plugin is broken?

[Cillian de Róiste]

Hi Kirill,

I think the path error is bogus, it's working fine here, can it be that you
just need to update?

Cheers,
Cillian


On Sat, Aug 31, 2013 at 11:21 AM, Kirill Elagin  wrote:

> Here is Chromium console output:
>
> ~~~
> [000:000] Browser XEmbed support present: 1
> [000:000] Browser toolkit is Gtk2.
> [000:001] Using Gtk2 toolkit
> [000:202] Starting client channel.
> [000:203] Warning(clientchannel.cc:436): Unreadable or no port file.
>  Could not initiate GoogleTalkPlugin connection
> [000:203] Warning(clientchannel.cc:411): Could not initiate
> GoogleTalkPlugin connection
> [000:203] GoogleTalkPlugin not running. Starting new process...
> [000:203] Warning(optionsfile.cc:47): Load: Could not open file, err=2
> [000:203] Warning(pluginutils.cc:251): Failed to get GoogleTalkPlugin
> path. Trying default.
> [000:207] Started GoogleTalkPlugin,
> path=/opt/google/talkplugin/GoogleTalkPlugin
> [000:207] Waiting for GoogleTalkPlugin to start...
> [000:686] Starting client channel.
> [000:686] Warning(clientchannel.cc:436): Unreadable or no port file.
>  Could not initiate GoogleTalkPlugin connection
> [000:686] Warning(clientchannel.cc:411): Could not initiate
> GoogleTalkPlugin connection
> [000:687] GoogleTalkPlugin not running. Starting new process...
> [000:687] Warning(optionsfile.cc:47): Load: Could not open file, err=2
> [000:687] Warning(pluginutils.cc:251): Failed to get GoogleTalkPlugin
> path. Trying default.
> [000:696] Started GoogleTalkPlugin,
> path=/opt/google/talkplugin/GoogleTalkPlugin
> [000:696] Waiting for GoogleTalkPlugin to start...
> [001:213] Attempting to connect to GoogleTalkPlugin...
> [001:213] Warning(clientchannel.cc:436): Unreadable or no port file.
>  Could not initiate GoogleTalkPlugin connection
> [001:213] Warning(clientchannel.cc:411): Could not initiate
> GoogleTalkPlugin connection
> [001:213] Waiting for GoogleTalkPlugin to start...
> [001:718] Attempting to connect to GoogleTalkPlugin...
> [001:718] Warning(clientchannel.cc:436): Unreadable or no port file.
>  Could not initiate GoogleTalkPlugin connection
> [001:718] Warning(clientchannel.cc:411): Could not initiate
> GoogleTalkPlugin connection
> [001:718] Waiting for GoogleTalkPlugin to start...
> [002:219] Attempting to connect to GoogleTalkPlugin...
> [002:219] Warning(clientchannel.cc:436): Unreadable or no port file.
>  Could not initiate GoogleTalkPlugin connection
> [002:219] Warning(clientchannel.cc:411): Could not initiate
> GoogleTalkPlugin connection
> 
> ~~~
>
> The path is obviously wrong…
>
>
> --
> Кирилл Елагин
>
> ___
> 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] Plone Development on Nix is getting quite nice!

[Cillian de Róiste]

Hi,

Thanks to the work Rok Garbas has been doing on generating python packages
I noticed it is now possible to use a combination of Nix and a standard
buildout.cfg for Plone development with a small patch to buildout. I've
added instructions to the wiki for anyone who's interested:

https://nixos.org/wiki/Plone_development#How_to_use_myEnvFun_and_buildout-nix_to_create_a_plone_development_environment

Although this wouldn't be a suitable way to deploy Plone, as a development
environment it already provides many advantages over a plain old buildout
setup. You can re-use python modules which have already been packaged in
nix, which speeds up initial installation greatly (e.g. Python c modules
such as ZODB3 are already compiled). These can also effectively be shared
between multiple development environments, but, unlike a typical egg cache
they can be garbage collected when no longer needed. Since they are in the
store, you also know that they haven't been modified, however, if you do
want to modify an egg, you can replace the symlink in ./eggs with a copy of
the egg and add debugging statements there etc. There is also no need to
bootstrap buildout or set up a virtualenv, since buildout-nix is packaged
in nix and myEnvFun provides isolation. Required eggs which aren't
available in the environment will be downloaded and installed, and other
typical buildout development scripts should all work as normal.

I've only used this to install and run a vanilla Plone 4.3.1 instance so
far, so there may well be complications with more advanced configurations.
It would be interesting to hear if anyone else tries it out, or has any
feedback about it.

You'll notice some addition version pinnings in the buildout.cfg, I'm not
sure why they're required, but without them buildout failed with version
conflict errors.

Cheers,
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] wiki and utf-8 characters

[Cillian de Róiste]

On Sun, Mar 24, 2013 at 11:24 AM, Lluís Batlle i Rossell
 wrote:
> On Sun, Mar 24, 2013 at 09:54:09AM +0200, phree...@yandex.ru wrote:
>> On Воскресенье 24 марта 2013 01:22:25 Marc Weber wrote:
>>
>> > > Not everybody is a developer
>> >
>> > Right - so if people are not familiar with github, do you think people 
>> > could
>> > be told to just send their contributions to the mailinglist - because - we
>> > want to review them
>> > - adding it to a git wiki and pushing is fast for developpers
>> >
>> > As alternative those people could just be told to  use the bug tracker.
>> >
>> > If we want to lower barrier for contirbution, what about adding a comment
>> > section people can write anything to ? See php.net/any-php-function - works
>> > great.
>> > We then can review the comments and change the wiki
>>
>> For casual contributors, we could provide ikiwiki instance and pull from it
>> periodically. I guess it can also be set up so that someone is notified when
>> there's a new commit. Thus for people who want to see the latest 
>> official/vetted
>> documentation, we have 1 branch/repo, and for people who want to edit/see
>> staging area, we have another. Could this be a viable workflow?
>
> FWIW, I dislike ikiwiki for its perlness and overengineering. Long ago I used
> it, and I regret that. :)

Another popular wiki with a git backend is http://gitit.net/ which
happens to be written in haskell and is already in nixpkgs (as is
ikiwiki). It looks quite nice, can anyone vouch for it?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] wiki and utf-8 characters

[Cillian de Róiste]

On Sat, Mar 23, 2013 at 12:24 PM, Joachim Schiele  wrote:
> http://muse-sequencer.org/index.php?title=Special:UserLogin&returnto=Manual%3ASpecial+pages&type=signup
>
> i've fixed it like this on muse-sequencer.org and ppl need to ask on the
> ml for a new account

I guess we could also set up a separate repo on github just for the
wiki and be very liberal about giving out write access and admin
rights for it. That would solve the issue of requiring write access to
either the nixpkgs or nixos repos in order to be able to contribute to
the wiki. For people concerned about github lock-in, this would
however still be make it more convenient for people with github
accounts to contribute. I guess there is nothing stopping people from
hosting their repos elsewhere and being merged as necessary.

More people seem to be familiar with ikiwiki than the github wiki
system (gollum). Should we go with ikiwiki then? Is someone willing
and able to maintain an instance of that on nixos.org?

> On 03/23/2013 12:03 PM, Marc Weber wrote:
>> For completness: I think that protecting the "create new user" feature
>> by htaccess, and documenting it (even with password) on the wiki would
>> be enough to keep spam bots away.
>>
>> That can be done without updating media wiki should not take much time
>> either.

That sounds like a great idea regardless of whether we stick with
Mediawiki or not.

Is it possible/easy to delete content from every contributor who isn't
on a whitelist, or is there some other convenient way to clean it up?
Is there anything I can do to help?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] wiki and utf-8 characters

[Cillian de Róiste]

On Tue, Mar 19, 2013 at 7:05 PM, Rok Garbas  wrote:
> Quoting Vladimír Čunát (2013-03-19 18:03:36)
>> On 03/19/2013 05:15 PM, Marc Weber wrote:
>> > Does anybody has more experience with utf-8 and nixos's mediawiki?
>>
>> Just tried, doesn't work well. It's garbled when saved, not just on
>> display. But > http-equiv="Content-Type"> looks good.
>>
>> Speaking of nix wiki... there's quite a steady in-flow of **spam**
>> articles (e.g. today I see certainly more than fifty new pages in its
>> feed). It would be good to add some captcha for user creation and then
>> clean up registered spammers and spam posts.
>>
>
> maybe moving to github's wiki. i really hate those textareas. also we dont 
> need
> to worry about spam and spammers anymore.

The current installation of mediawiki is also missing a lot of the
usual features, and I can imagine it's not so much fun to maintain.
FWIW I would also be happy to contribute content to a github wiki (or
similar system). I believe it would be possible to run the github wiki
engine (gollum) on the nixos.org server, in case anyone has
reservations about being locked into github. Does anyone have any
objections or reservations about using a github wiki, or better
suggestions? Should we set one up to try it out?

Cheers,
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] wicd broken after stdenv-updates

[Cillian de Róiste]

On Wed, Mar 13, 2013 at 9:04 PM, Vladimír Čunát  wrote:
> On 03/13/2013 08:50 PM, Bjørn Forsman wrote:
>>
>> I'm no python (or nixos) expert, but someone on IRC said they have
>>
>> PYTHONPATH=$HOME/.nix-profile/lib/python2.7/site-packages/:/run/current-system/sw/lib/python2.7/site-packages.
>> I tried it myself and it works.
>>
>> Why isn't PYTHONPATH set to this by default? Or is this the bug - that
>> PYTHONPATH no longer is set?
>
>
> This should certainly be set in the python script itself, otherwise it would
> be quite an impurity. However, updating stdenv itself IMHO shouldn't have
> changed such a thing, but there were many updates in that branch.

This error is related to a pull request I opened before the
stdenv-updates merge, but which I hadn't tested with wicd. I updated
pygobject to 2.28 to fix an error in MyPaint. I didn't notice that
this release of pygobject moved the gobject folder, hence the import
error.

I think I've fixed the PYTHONPATH which is set in the wicd expression
so that the wicd tools can now import gobject successfully, however,
it's still not working. I've added a ticket to keep track of it:

https://github.com/NixOS/nixpkgs/issues/379

Cheers,
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] hplip network support is disabled: why?

[Cillian de Róiste]

Hi,

I guess the more important part is line 31: "--disable-network-build".
I'd try removing it and, based on the comment, adding net_snmp as a
buildInput would probably help too.

Good luck!
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Problem with ATI graphics card

[Cillian de Róiste]

On Tue, Jul 31, 2012 at 11:23 AM, Marco Maggesi  wrote:
> Hi,
>
> I'm trying to reinstall nixos on an my desktop computer (after an HD
> replacement due to a bad corruption).
> The installation process goes smoothly, but after reboot (during Stage 2)
> the screen become unreadable (a set of randomly distributed coloured
> pixels).
>
> This happens under various different configurations:
> - with my old configuration.nix
> - with a brand new configuration.nix created by the installation scripts
> - with xserver enabled and disabled
>
> When booted from the installation/rescue CD the graphics card works
> normally, either in text mode and with x11.
>
> Here is the line of output of lspci that describe the graphics card:
>
> 01:00.0 VGA compatible controller: ATI Technologies Inc RV610 video device
> [Radeon HD 2400 PRO]
>
> What could I do?

I guess it's missing the firmware, there is a work around:
https://github.com/NixOS/nixos/issues/6

Cheers,
Cillian

> Thanks,
> Marco
>
> ___
> 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] Python bindings to librsvg or gnome-desktop

[Cillian de Róiste]

On Tue, Jun 19, 2012 at 10:51 AM, Alexander Foremny
 wrote:
> Hello,
>
> I am trying to create a Nix expression for solfege [1] and got it
> building fine using the  Nix expression available as Gist [2].
> However, running the application fails with the following error,
> cryptographic hashes replaced by dots.
>
>> Traceback (most recent call last):
>>   File "/nix/store/...-solfege-3.20.4/share/solfege/solfege/startup.py", 
>> line 159, in start_gui
>> solfege.win = w = MainWin(options, datadir)
>>   File "/nix/store/...-solfege-3.20.4/share/solfege/solfege/mainwin.py", 
>> line 119, in __init__
>> stock.SolfegeIconFactory(self, datadir)
>>   File "/nix/store/...-solfege-3.20.4/share/solfege/solfege/stock.py", line 
>> 71, in __init__
>> self.add_icons(d)
>>   File "/nix/store/...-solfege-3.20.4/share/solfege/solfege/stock.py", line 
>> 33, in add_icons
>> iconset = 
>> gtk.IconSet(gtk.gdk.pixbuf_new_from_file(os.path.join(self.datadir, 
>> filename)))
>> glib.GError: Couldn't recognize the image file format for file 
>> '/nix/store/..-solfege-3.20.4/share/solfege/graphics/solfege.svg'
>
> This issue has been addressed [3] and appears to be an issue not
> caused by solfege but by a missing python dependency [4]. It is solved
> by making solfege depend on python-rsvg. However, I cannot find this
> package in Nixpkgs. Further research revealed that this binding is now
> part of the Python bindings to Gnome [5]. As observable in the current
> NIx expression I added the dependency gnome_python hoping this would
> solve the problem. However, it does not.
>
> Is it correct that gnome_python are the Python bindings to Gnome
> Desktop which should contain pyrsvg? If not, is pyrsvg already
> packaged? If not, where can I find the sources of python-gnome-desktop
> and where would be a good place to place a Nix expression for this?
>
> Or could it be the case that this functionality should be supplied by
> pygtk, but this (optional?) feature is disabled due to missing
> dependencies?

I ran into the same issue trying to package key-mon [1], your
debugging helped a lot. I've packaged python-rsvg, and I had to change
python-gnome so that python-rsvg could be built and I also needed to
enable the librsvg pixbuf-loader (previously disabled):

https://github.com/cillianderoiste/nixpkgs-goibhniu/tree/python-rsvg

This should work with solfege too since I got exactly the same error,
but you'll need to wrap it with something like:

wrapProgram $out/bin/solfege --prefix GDK_PIXBUF_MODULE_FILE :
${librsvg}/lib/gdk-pixbuf/loaders.cache

Since I use buildPythonPackage for key-mon, this results in a wrapper
which wraps another wrapper. It all seems to work fine though.

One concern is that if you wrap a program as described, then it will
only be able to open svg files and not other formats. If this is a
problem, the loaders.cache file could be concatenated with the
gdk-pixbuf loaders.cache [2] and then that could then be used as the
GDK_PIXBUF_MODULE_FILE. I bet there are smarter, nixian ways to do
such a thing!

On a typical distro these loaders are added to a global directory like
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/ then gdk-pixbuf-query-loaders
is used to update /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache when a
new loader is added. In the case of pygtk (and presumably for gtk in
general [3]) gtk.gdk.pixbuf_new_from_file uses this file to find the
loaders for the various formats.

These changes would cause a massive rebuild (1110 packages, based on
comparing the drv-paths), so I won't even add them as a pull request
yet. It would be great to hear if there are more elegant ways to
approach this.

All the best,
Cillian

[1] http://code.google.com/p/key-mon/
[2] e.g. 
/nix/store/fimfm5ybk2m7iklsm78b84v7sy8flvgw-gdk-pixbuf-2.24.1/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
[3] http://developer.gnome.org/gdk-pixbuf/stable/gdk-pixbuf-query-loaders.html

> [1] http://solfege.org
> [2] https://gist.github.com/2953069
> [3] http://code.google.com/p/solfege/issues/detail?id=255
> [4] https://bugs.launchpad.net/ubuntu/+source/solfege/+bug/1004485
> [5] http://www.rittau.org/blog/20060418-00
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] PYTHONPATH and eggs

[Cillian de Róiste]

On Fri, Jul 27, 2012 at 1:42 PM, Florian Friesdorf  wrote:
> On Fri, 27 Jul 2012 13:29:03 +0200, Mathijs Kwik  
> wrote:
>> That's strange then :)
>>
>> I disabled the test too, but the problem remains.
>> Just to be clear, it's a warning, not an error:
>>
>> % bup meta
>> Warning: Linux xattr support missing; install python-pyxattr.
>> Warning: POSIX ACL support missing; install python-pylibacl.
>> usage: bup meta --create [OPTION ...] 
>>or: bup meta --extract [OPTION ...]
>>or: bup meta --start-extract [OPTION ...]
>>or: bup meta --finish-extract [OPTION ...]
>
> sorry - I have the same - was looking out for python import errors.
>
>> How can I debug this further?
>
> % 
> /nix/store/5qmz5wc596kl7rywx56phyl2gb0052w7-python-2.7.3/lib/python2.7/pdb.py 
> .nix-profile/bin/bup
> Traceback (most recent call last):
>   File 
> "/nix/store/5qmz5wc596kl7rywx56phyl2gb0052w7-python-2.7.3/lib/python2.7/pdb.py",
>  line 1314, in main
> pdb._runscript(mainpyfile)
>   File 
> "/nix/store/5qmz5wc596kl7rywx56phyl2gb0052w7-python-2.7.3/lib/python2.7/pdb.py",
>  line 1233, in _runscript
> self.run(statement)
>   File 
> "/nix/store/5qmz5wc596kl7rywx56phyl2gb0052w7-python-2.7.3/lib/python2.7/bdb.py",
>  line 387, in run
> exec cmd in globals, locals
>   File "", line 1, in 
>   File ".nix-profile/bin/bup", line 2
> export 
> PYTHONPATH=/nix/store/ixp90035n4xrr6y4kcvcb36cd6rpcz0a-python-pyxattr-0.5.1/lib/python2.7/site-packages:/nix/store/kczagr8sv3yx355jy63byv7i7jngbx9v-python-pylibacl-0.5.1/lib/python2.7/site-packages:/nix/store/5qmz5wc596kl7rywx56phyl2gb0052w7-python-2.7.3/lib/python2.7/site-packages:/nix/store/93lbhnm76wlkmq7r0z8lwk3g9ch76hjp-git-1.7.11/lib/python2.7/site-packages${PYTHONPATH:+:}$PYTHONPATH
> ^
> SyntaxError: invalid syntax
> Uncaught exception. Entering post mortem debugging
> Running 'cont' or 'step' will restart the program
>> (1)()
> (Pdb)
>
> So the wrapper actually is not good.

If I understand correctly, you've run pdb on the wrapper, which is a
shell script, rather than the wrapped python code, is that right?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] How can we test changes before pushing them to master?

[Cillian de Róiste]

On Tue, Jul 24, 2012 at 9:46 PM, Eelco Dolstra
 wrote:
> Hi,
>
> On 24/07/12 14:34, Cillian de Róiste wrote:
>
>> Perhaps other people already have similar scripts or workflows or
>> ideas of how we could go about this?
>
> Maybe something like:
>
> $ nix-env -f . -qaP \* --drv-path | sort > l1
> (...modify package...)
> $ nix-env -f . -qaP \* --drv-path | sort > l2
> $ changed=$(diff l1 l2 | awk '{print $2}' | sort | uniq)
> $ nix-build $(for i in $changed; do echo -A $i; done)

Thanks! This works very well. I've added it to the wiki:
https://nixos.org/wiki/Contributing

Cheers,
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] How can we test changes before pushing them to master?

[Cillian de Róiste]

Hi,

Over the last weekend in Munich Florian, Joachim and I planned to make
some invasive changes. Before opening a pull request we wanted to test
that we didn't break anything. We tried a variety of approaches, many
of which were discussed on IRC and on the mailing list but we still
haven't quite reached that goal.

We are looking for a way to tell Nix to build every available package
(not just the ones currently installed on the system) which depend in
any way on a particular change. Some recent examples where this would
also have been handy are the boost and ffmpeg upgrades. In our case we
want to see what happens when we change the buildPythonPackage
function. For example, we have no reason to test that haskell packages
build successfully, but we do want to test that mesa builds
successfully.

We have a nix expression which can return the attribute set of all
packages which directly depend on some particular input. This is
pretty useful, but we haven't figured out yet how to generate that
attribute set recursively and efficiently (see email from Florian
"extending release-lib and how to cache in nix").

We did try maintainers/scripts/rebuild-amount.sh but couldn't manage
to get any output from it. We also tried running the nix-instantiate
command which is run by that script (see email from Florian: "reverse
dependencies") but it dies as soon as it finds any expression that it
can't evaluate.

Perhaps other people already have similar scripts or workflows or
ideas of how we could go about this?

Cheers,
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nix Hackfest 22-26th August (was Tentative NIx Hackfest in Augsburg (or Munich): July 6th-9th)

[Cillian de Róiste]

On Mon, Jul 9, 2012 at 1:44 PM, Florian Friesdorf  wrote:
> On Mon, 09 Jul 2012 13:36:50 +0200, Florian Friesdorf  
> wrote:
>> On Mon, 09 Jul 2012 12:47:39 +0200, "mail.lastlog.de"  
>> wrote:
>> > Sounds great
>>
>> updated wiki
>
> this one: https://nixos.org/wiki/Nix_Hackfest:_2012-07_20th_to_22nd
>
> Also I announced the hackfest to CCC-Munich. Whenever I was talking
> there about nix, a couple of people where interested...

Excellent! If anyone is considering coming from outside Munich and
needs a hand with accommodation or anything, I'd be happy to help. It
will take place in our office which is very near to the main train
station (Landwehrstrasse).

>> > ----- Original message -
>> > > On Mon, 9 Jul 2012 00:11:46 +0200, Cillian de Róiste
>> > >  wrote:
>> > > > Hi,
>> > > >
>> > > > I've added a wiki page for this one too:
>> > > > https://nixos.org/wiki/Nix_Hackfest:_2012-07_20th_to_22nd
>> > > >
>> > > >
>> > > > On 07/03/2012 05:46 PM, Florian Friesdorf wrote:
>> > > >
>> > > > (Snip)
>> > > >
>> > > > > I'm currently on EuroPython in Florence and could ask if somebody
>> > > > > would host us.
>> > > >
>> > > > Did you happen to meet anyone else who would be interested in joining
>> > > > or hosting this?
>> > >
>> > > Lightning talk slots were all full - apart from that I did not find
>> > > anybody interested.
>> > >
>> > > So I'd say Munich 20-22 it is?
>> > >
>> > > --
>> > > Florian Friesdorf 
>> > > GPG FPR: 7A13 5EEE 1421 9FC2 108D   BAAF 38F8 99A3 0C45 F083
>> > > Jabber/XMPP: f...@chaoflow.net
>> > > IRC: chaoflow on freenode,ircnet,blafasel,OFTC
>> >
>> Non-text part: text/html
>>
>> --
>> Florian Friesdorf 
>>   GPG FPR: 7A13 5EEE 1421 9FC2 108D  BAAF 38F8 99A3 0C45 F083
>> Jabber/XMPP: f...@chaoflow.net
>> IRC: chaoflow on freenode,ircnet,blafasel,OFTC
>
> --
> Florian Friesdorf 
>   GPG FPR: 7A13 5EEE 1421 9FC2 108D  BAAF 38F8 99A3 0C45 F083
> Jabber/XMPP: f...@chaoflow.net
> IRC: chaoflow on freenode,ircnet,blafasel,OFTC
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nix Hackfest 22-26th August (was Tentative NIx Hackfest in Augsburg (or Munich): July 6th-9th)

[Cillian de Róiste]

Hi,

I've added a wiki page for this one too:
https://nixos.org/wiki/Nix_Hackfest:_2012-07_20th_to_22nd


On 07/03/2012 05:46 PM, Florian Friesdorf wrote:

(Snip)

> I'm currently on EuroPython in Florence and could ask if somebody would
> host us.

Did you happen to meet anyone else who would be interested in joining
or hosting this?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nix Hackfest 22-26th August (was Tentative NIx Hackfest in Augsburg (or Munich): July 6th-9th)

[Cillian de Róiste]

On Tue, Jul 3, 2012 at 5:46 PM, Florian Friesdorf  wrote:
> On Sun, 1 Jul 2012 20:20:14 +0200, Cillian de Róiste 
>  wrote:
>> Hi,
>>
>> Following some discussion on IRC it looks like it would be much better
>> to push this forward a bit. A five day session from 22-26th August is
>> the new proposal, probably still in Munich or Augsburg.
>>
>> As before, please fill in your topic of interest here:
>>
>> https://nixos.org/wiki/Nix_Hackfest:_2012-08_22nd_to_26th_Augsburg
>>
>> Let's try to nail this down in the next week or two so that people can
>> arrange accommodation, transport, time off work etc.
>
> On irc with goibhniu the idea came up to have another
> sprint/hackathon/hackfest, 20.-22. July for example in:
>
> 1 Florence
> 2 Northern italy seaside
> 3 or Munich
>
> Who would be up for that and where? aszlig, qknight, garbas, goibhniu,
> (first time I could spell your nickname without looking it up ;),
> anybody else?

I'm definitely up for it. Munich would be my first preference, but as
long as I can get to the location by night train I'm happy.

--
goibhniu

> I'm currently on EuroPython in Florence and could ask if somebody would
> host us.
>
> regards
> florian
> --
> Florian Friesdorf 
>   GPG FPR: 7A13 5EEE 1421 9FC2 108D  BAAF 38F8 99A3 0C45 F083
> Jabber/XMPP: f...@chaoflow.net
> IRC: chaoflow on freenode,ircnet,blafasel,OFTC
>
> ___
> 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] [Nix-commits] [NixOS/nixpkgs] f823b6: Fix compilation error when using boost 1.5 by pinn...

[Cillian de Róiste]

On Mon, Jul 2, 2012 at 7:28 PM, Lluís Batlle i Rossell  wrote:
> On Sun, Jul 01, 2012 at 09:14:10PM -0700, Cillian de Róiste wrote:
>>   Branch: refs/heads/master
>>   Home:   https://github.com/NixOS/nixpkgs
>>   Commit: f823b6230d7bec7906bdc969d0cb64cc806c997c
>>   
>> https://github.com/NixOS/nixpkgs/commit/f823b6230d7bec7906bdc969d0cb64cc806c997c
>>   Author: Cillian de Róiste 
>>   Date:   2012-07-01 (Sun, 01 Jul 2012)
>>
>>   Changed paths:
>> M pkgs/top-level/all-packages.nix
>>
>>   Log Message:
>>   ---
>>   Fix compilation error when using boost 1.5 by pinning the boost version to 
>> 1.49
>
> Could you please write, the next time, for what package you fix the error? :)

Thanks for the feedback, I assumed the diff would appear beside the
commit message. I will be more explicit in the future. (It was Ardour
3 beta, for anyone casually reading).

> This boost update broke some other programs. Peter said that he wanted to
> remove 1.49 due to some boost upstream decision. How should we proceed? Use a
> boost older than 1.49?

I opened a ticket about this:
https://github.com/NixOS/nixpkgs/pull/29

IIUC Peter only wanted to remove these versions of boost because we're
not using them https://github.com/NixOS/nixpkgs/pull/27 (perhaps there
is more to it, this is the only reference to it that I noticed) so
Eelco decided to keep boost 1.49 since it now has a use.

Cheers,
goibhniu
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Nix Hackfest 22-26th August (was Tentative NIx Hackfest in Augsburg (or Munich): July 6th-9th)

[Cillian de Róiste]

Hi,

Following some discussion on IRC it looks like it would be much better
to push this forward a bit. A five day session from 22-26th August is
the new proposal, probably still in Munich or Augsburg.

As before, please fill in your topic of interest here:

https://nixos.org/wiki/Nix_Hackfest:_2012-08_22nd_to_26th_Augsburg

Let's try to nail this down in the next week or two so that people can
arrange accommodation, transport, time off work etc.

Cheers,
goibhniu
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Fwd: Improving the Developer Experience in the Nix Community

[Cillian de Róiste]

On Fri, Jun 29, 2012 at 4:50 PM, Bryce L Nordgren  wrote:
> -- Forwarded message --
> From: Bryce L Nordgren 
> Date: Fri, Jun 29, 2012 at 4:48 PM
> Subject: Re: [Nix-dev] Improving the Developer Experience in the Nix
> Community
> To: 7c6f4...@mail.ru
>
>
> On Fri, Jun 29, 2012 at 4:41 PM, Michael Raskin <7c6f4...@mail.ru> wrote:
>>
>> It does look that currently it is unattainable as such on some
>> questions. Consensus is good when it is feasible, but with some amount
>> of differences it is too much to ask for.
>
>
> Consensus as the only operating rule excludes Nix from the workplace. Nearly
> all workplaces have nonnegotiable policies, and it's likely that these will
> not be compatible. So there must always be an adaptation layer between a
> more or less generic distribution and the specific policies on site. The
> adaption layer is bidirectional: the distribution should be prepared to
> accept and de-specialize contributions from any particular environment, just
> as each participant must be prepared to specialize the generic distribution
> to their needs.
>
> An important part of Consensus is recognizing when it doesn't apply.

The consensus process sounds very interesting to me. I can't think of
any particular cases which would infringe on a workplace policy
personally. If I understand correctly, the idea is that you vote
against (block) things you feel strongly should not happen, so it's
just the opposite of a normal voting process where you vote in favor
of a proposal. With the normal voting process a decision can be
accepted even if some people are strongly against it. With the
consensus process everybody doesn't have to agree or think that the
solution is the best possible one, it just needs to be the case that
nobody is strongly against it.

Whether someone has the right to vote with either system is difficult
to determine, and a single blocker is more powerful than a single
voter so that may make it tricky to apply. I can see why it makes
sense for members to be physically present at a meeting to work out
differences of opinion. I wouldn't rule it out as an optional decision
making process just yet though.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Tentative NIx Hackfest in Augsburg (or Munich): July 6th-9th

[Cillian de Róiste]

Hi,

Since there are a few Nixers around the Munich area (or passing
through) we have been discussing the idea on IRC of getting together
for a few days to work on some Nix stuff.

Nothing has been confirmed yet but we were thinking of July 7-9th in
Augsburg. Naturally, people are also welcome to attend remotely, and
we'll try to ensure we have webcams etc. available to include people
as much as possible.

I've added a brief page to the wiki which we could use for planning:
https://nixos.org/wiki/Nix_Hackfest:_2012-07_Augsburg

Feel free to add your nick/name and topic of interest along with a
description of a topic you would particularly like to work on (and to
propose more hackfests!).

If people are interested in Nix and want to drop in to see what it's
about, get help packaging something or perhaps to do some wiki
gardening or other constructive tasks which aren't particularly
programming related, that would also be wonderful!

Cheers,
goibhniu
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] gimp 2.8

[Cillian de Róiste]

On Tue, Jun 5, 2012 at 4:20 PM, Rok Garbas  wrote:
> Quoting Cillian de Róiste (2012-06-04 19:52:40)
>>Committed, cheers!
>>
>
> would be ok if you rename gimp_2_8_0 into gimp28 or gimp_28. kinda doesn't 
> make
> sense to keep bugfix part of version number. at least thats how i see others
> did it in all-packages.nix.

Thanks for pointing that out, it makes sense. I believe gimp_2_8 is
the preferred variant, although as you say, there are plenty of
examples without any underscores.

> you can also safely update babl and gegl (no need for gegl_0_2_0 and
> babl_0_1_10) its only used by cinepaint which i checked and it working with
> updated versions.

I don't use GIMP regularly myself so I'm inclined to let the 2.8
version sit there for a while before making it the default, and I'd
also keep 2.6 available at least until the plugins have been updated.
Does the 2.6 version also work with the new gegl and babl?

I'm not exactly sure of the workflow we'll be using with github, but I
guess you can submit pull requests there and we can continue the
discussion there as comments on the pull request (if we need to), and
then someone in the NixOS org can accept that pull request. I am quite
interested to see how that works out. Perhaps you have some advice
from your experience with the plone collective -> github migration ..
but that's another topic.

Cheers,
Cillian

> --
> Rok Garbas - http://www.garbas.si
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] gimp 2.8

[Cillian de Róiste]

Committed, cheers!

On Mon, Jun 4, 2012 at 2:43 PM, Rok Garbas  wrote:
> Quoting Cillian de Róiste (2012-06-04 11:13:13)
>>Hi Rok,
>>
>>Thanks for the patch! I've been looking forward to trying 2.8 but was
>>too lazy to try to update the expression myself. Unless someone beats
>>me to it I will apply the patch this evening. To avoid any breakage (I
>>guess the plugins won't work) I'll first add it as a separate package
>>instead of replacing 2.6.
>>
>
> +1 ... not sure i'll have time to do this myself this evening
> i havent looked at the plugins yet but that would be logical next step
>
>
>>I notice you changed some of the formatting but it doesn't actually
>>match the conventions:
>>http://hydra.nixos.org/job/nixpkgs/trunk/tarball/latest/download-by-type/doc/manual#chap-conventions
>>
>>I believe this is the preferred style:
>>{ stdenv, fetchurl, pkgconfig, gtk, freetype , fontconfig
>>, libart_lgpl, libtiff, libjpeg, libpng, libexif, zlib, perl
>>, perlXMLParser, python, pygtk, gettext, xlibs, intltool, babl
>>, gegl
>>}:
>>
>>buildInputs =
>>  [ pkgconfig gtk freetype fontconfig libart_lgpl libtiff libjpeg
>>    libpng libexif zlib perl perlXMLParser python pygtk gettext
>>    intltool babl gegl
>>  ];
>>
>
> will be more careful with formatting in the future.
>
> anybody knows some vim addon which can format like this? :)
> currently i use:
>    map W :%s/\s\+$//:let @/=''
>
> --
> Rok Garbas - http://www.garbas.si
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Creating .asoundrc or other files within configuration.nix?

[Cillian de Róiste]

On Sun, Jun 3, 2012 at 8:47 AM, Marc Weber  wrote:
> Excerpts from Sol Reynolds's message of Sun Jun 03 08:01:36 +0200 2012:
>> I'm trying to figure out if it's possible to create an .asoundrc
>> from configuration.nix.  Any advice if this is a futile quest?
>
> Well there is /etc/skel/ which let's you add files which will be copied
> to each home directory.
>
> Its important to think about whether you need symlinks or files.
> files can be edited by users - symlinks to /etc/skel will always
> represent current generation contents ..
>
> That's all which comes to my mind.
>
> Maybe alsa* tools already read a global configuration first ( I forgot)
> or can be patched to do so.

Yes, indeed. nixos/modules/config/pulseaudio.nix creates
/etc/asound.conf to configure ALSA applications to use PulseAudio.
This might be a good starting point. It would be useful to be able to
write a custom one so you could determine the default sound card to
use etc.

Cheers,
Cillian

>
> Marc Weber
> ___
> 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] gimp 2.8

[Cillian de Róiste]

Hi Rok,

Thanks for the patch! I've been looking forward to trying 2.8 but was
too lazy to try to update the expression myself. Unless someone beats
me to it I will apply the patch this evening. To avoid any breakage (I
guess the plugins won't work) I'll first add it as a separate package
instead of replacing 2.6.

I notice you changed some of the formatting but it doesn't actually
match the conventions:
http://hydra.nixos.org/job/nixpkgs/trunk/tarball/latest/download-by-type/doc/manual#chap-conventions

I believe this is the preferred style:
{ stdenv, fetchurl, pkgconfig, gtk, freetype , fontconfig
, libart_lgpl, libtiff, libjpeg, libpng, libexif, zlib, perl
, perlXMLParser, python, pygtk, gettext, xlibs, intltool, babl
, gegl
}:

buildInputs =
  [ pkgconfig gtk freetype fontconfig libart_lgpl libtiff libjpeg
libpng libexif zlib perl perlXMLParser python pygtk gettext
intltool babl gegl
  ];

I hope that helps, cheers!
Cillian

On Mon, Jun 4, 2012 at 12:49 AM, Rok Garbas  wrote:
> i've managed to upgrade gimp to version 2.8.0 (see patch). i'm not reaaly a 
> big
> user of gimp but i've been using it for whole day now and it looks like
> everything i clicked worked.
>
> maybe somebody who's more hardcore gimp user can give below patch a try or if
> there's nobody really using it we can as well as just commit it.
>
> https://gist.github.com/2865295
>
> --
> Rok Garbas - http://www.garbas.si
> ___
> 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] new font ttf-bitstream-vera-for-powerline

[Cillian de Róiste]

On Fri, Jun 1, 2012 at 5:01 PM, Rok Garbas  wrote:
>
> this font is patched ttf bitstream vera font, but patched for use of Powerline
> (vim addon, https://github.com/Lokaltog/vim-powerline).
>
> https://gist.github.com/2852729

Is this a bit dodgy?

https://github.com/Lokaltog/vim-powerline/wiki/Patched-fonts
"Because of possible licensing issues fonts will never be included in
the main Powerline code repo. This page consists of user-contributed
patched fonts for use with Powerline."

Perhaps we also can't distribute this?

Cheers,
Cillian

>
>
> --
> Rok Garbas - http://www.garbas.si
> ___
> 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] update for weechat

[Cillian de Róiste]

I've applied the patch, tested and committed. Thanks!

On Fri, Jun 1, 2012 at 4:51 PM, Rok Garbas  wrote:
> can somebody update weechat... https://gist.github.com/2841720
>
> --
> Rok Garbas - http://www.garbas.si
> ___
> 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] What kills my xserver?

[Cillian de Róiste]

On Thu, May 10, 2012 at 12:05 AM, Arie Middelkoop  wrote:
> On 09/05/12 18:41, Cillian de Róiste wrote:
>>
>> For what it's worth, I have the same symptoms although I have not
>> investigated it at all. I am using the ati videoDriver (the Free one).
>> I'd be happy to collect some information if it helps to debug. I had
>> always assumed that a fresh ~/.kde would solve it but never bothered
>> to try.
>
>
> One of the many steps that I tried is a fresh ~/.kde, and I can confirm that
> this does not help in resolving the issue.
>
> Actually, I recall that the Nixos manual mentions that it's possible to test
> your system in a virtual machine. I wonder if this could help in ruling out
> hardware issues. Virtualized hardware is hopefully more deterministic among
> different systems than real hardware...

That's a nice idea, I ran some tests based on the instructions here a
while back: http://nixos.org/wiki/NixOS_VM_tests

If it fails in the VM then it looks like it is indeed a hardware
issue. AFAIK Eelco is using KDE with the nvidia driver and can logout
and restart without any problems from the KDE menu.
I guess it's also worth testing the vesa video driver.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] What kills my xserver?

[Cillian de Róiste]

Hi Arie,

On Wed, May 9, 2012 at 2:25 PM, Arie Middelkoop  wrote:
> Hi Nixos-ers,
>
> I've never been able to reboot my machine from inside a KDE session in
> combination with KDM. Also, a logout takes excessively long (10
> seconds). Lately, I investigated the crime scene, found some good leads,
> but now I'm stuck.

...

For what it's worth, I have the same symptoms although I have not
investigated it at all. I am using the ati videoDriver (the Free one).
I'd be happy to collect some information if it helps to debug. I had
always assumed that a fresh ~/.kde would solve it but never bothered
to try.

Cheers,
Cillian (goibhniu)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] reviewboard

[Cillian de Róiste]

Hi,

It looks very useful. I just thought I'd mention that I was confused
by the form question:

"Base Directory: The absolute path in the repository the diff was generated in."

It is happy with "/nixpkgs/trunk" for relative patches created in
/etc/nixos/nixpkgs

Thanks!
Cillian

On Fri, Mar 16, 2012 at 5:24 PM, Yury G.  Kudryashov
 wrote:
> Ludovic Courtès wrote:
>
>> Hi,
>>
>> "Yury G.  Kudryashov"  skribis:
>>
>>> I've set up a reviewboard at http://reviewboard.loegria.net/
>>
>> What is it,
> http://reviewboard.org
>> and what would it be used for?
> Not loosing incoming patches while we're using svn for nixos and nixpkgs.
> --
> Yury G. Kudryashov,
> mailto: ur...@mccme.ru
>
> ___
> 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] Nix(OS) on upcoming sprints/events

[Cillian de Róiste]

On Sat, Feb 18, 2012 at 12:46 AM, Florian Friesdorf  wrote:
> On Tue, 31 Jan 2012 14:37:02 +0100, Florian Friesdorf  
> wrote:
>> (..)
>> My goals would be:
>>
>> - achieving pureness for python packages
>
> Attached is a patchset to achieve pureness for python packages and
> handle dependencies via pth files. While I'm still working on some
> issues it would be great to get feedback on it.
>
> @Cillian: I used your distutils.cfg idea to create a offline version of
> distutils used only during installations. An installed setuptools is
> then able again to download things.
>
> Also available via github:
> https://github.com/chaoflow/nixpkgs/tree/python

This looks great!

I have one question about:
0002-pth-file-with-deps-only-current-package-s-scripts-no.patch

If you remove a package does
$out/lib/${python.libPrefix}/site-packages/"{easy-install.pth,${name}.pth}
get left behind?

My understanding of Nix is still a little hazy, but I wonder if
${python.libPrefix}/site-packages should be managed by Nix (maybe it
is already?). Every time a new python package is installed a new
output for site-packages could be created in the store which contains
the relevant .pth files for all the installed modules.

Perhaps I have misunderstood .. is that already taken care of?

Cheers,
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nix(OS) on upcoming sprints/events

[Cillian de Róiste]

On Tue, Feb 7, 2012 at 11:10 AM, Marc Weber  wrote:
> Excerpts from Cillian de Róiste's message of Tue Feb 07 11:07:14 +0100 2012:
>> I just want to add that I also want to help to make this happen, most
> Can you also talk about the way(s) you propose / like most?

I don't have a strong opinion about it at all. I'm happy to try out a
number of options at the sprint, or to just pick any option and see
where it takes us. Of course, I would like to build on the work which
has already been done.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nix(OS) on upcoming sprints/events

[Cillian de Róiste]

Hi,

I just want to add that I also want to help to make this happen, most
especially to replace most of what zc.buildout does with nix for Plone
installations. I hope to have some time at the Plone Konferenz sprint
25th-26th Feb (although I may need to help out with the conference
itself) otherwise I will certainly have time in March and will be
available any weekend for sprinting.

Incidentally, I have rebuilt my system using the distutils.cfg patch
which should prevent easy_install from resolving dependencies on its
own. I still need to verify that it does work as expected (by adding a
module which does not include required dependencies as buildInputs).

Cheers,
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] python packages and dependencies

[Cillian de Róiste]

On Wed, Sep 21, 2011 at 10:09 PM, Peter Simons  wrote:
> Hi Florian,
>
>  > buildPythonPackage happily fetches all dependency of a package defined in
>  > setup.py. The dependencies in there are not necessarily fixed to a
>  > specific version. Therefore, it's not guaranteed that one and the same
>  > nix expression produces the same derivation. How is this handled?
>
> I have noticed that, too, and I'm not about that "feature" either. I assume
> that there is a way (command-line flag) to tell 'distutils' to disable
> network access? Does anyone know how to do that?

Florian and I were discussing this again the other day and found that
there is a convenient way to do this (patch attached), by setting
allow_hosts=None in a system distutils.cfg. It's interesting that this
will not effect a virtualenv which means that someone could still use
easy_install from a virtualenv and dependencies would be resolved in
the usual way. I have tested the equivalent setup.cfg file and it has
the desired effect, but I didn't test the patch enough yet to verify
that it works as expected. Just to be clear, the builder doesn't need
to call easy_install explicitly for this setting to be applied, it is
also used when running e.g. `python setup.py test` in a package which
imports setuputils, which would otherwise download and install the
requirements.

http://packages.python.org/distribute/easy_install.html#restricting-downloads-with-allow-hosts

Cheers,
Cillian


distutils.patch
Description: Binary data
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] [nix-dev] oxygen gtk theming

[Cillian de Róiste]

2012/1/14 Александр Цамутали :
> Sergey Mironov  writes:
>
>> Hi. I've installed oxygen-gtk theme and tried to switch it on by linking
>>
>> [ierton@pokemon:~]$ ls -l .gtkrc-2.0.mine
>> lrwxrwxrwx 1 ierton users 64 Янв 13 13:55 .gtkrc-2.0.mine -> /var/run/
>> current-system/sw/share/themes/oxygen-gtk/gtk-2.0/gtkrc
>>
>> (.gtkrc-2.0.mine is included from .gtkrc-2.0)
>>
>> It works, partly. Now all my gtk apps issue a warning
>>
>> /nix/store/nb08bx0r8hj14l9gf7xprv1kb0vy1w2m-wicd-1.7.1-beta2/share/gtk/
>> gui.py:152: GtkWarning: Unable to locate theme engine in module_path:
>> "oxygen-gtk",
>>
>> and some parts of interface look ugly.
>>
>> Well, I am not a gtk expert. Lxappearance app (not in tree, i've installed it
>> locally) didn't help - it couldn't detect the presence of  oxygen theme in my
>> system. Does anybody know a better  way of setting things up?
>
> I tried the same with murrine a long time ago with the same result. It
> seems we need to patch GTK+ to help it find paths to theme engines for
> ex. from environment variable.

It's not ideal/pure, but this is how I do it for KDE:
https://nixos.org/wiki/Enable_GTK_themes_in_KDE
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] [Nix-commits] SVN commit: nix - r31256 - nixpkgs/trunk/pkgs/os-specific/linux/firmware/rt2860

[Cillian de Róiste]

2012/1/4 Cillian de Róiste :
> 2012/1/3 Lluís Batlle i Rossell :
>> On Tue, Jan 03, 2012 at 10:02:36PM +, Cillian de Roiste wrote:
>>> Author: cillian
>>> Date: Tue Jan  3 22:02:34 2012
>>> New Revision: 31256
>>> URL: https://nixos.org/websvn/nix/?rev=31256&sc=1
>>>
>>> Log:
>>> Ralink firmware is no longer available directly from ralinktech.com, it is 
>>> now available from git.kernel.org. I've used the debian svn repo here 
>>> instead for convenience
>>
>> What if we made an expression for all those ralink? the rt73 expression would
>> have that very similar builder too.
>
> That would be great. I notice that other distros package them all
> together: http://packages.debian.org/wheezy/firmware-ralink
> Should we do it like that, or is there some value in keeping each one 
> separate?

I've added a single expression to provide all the ralink firmware
(r31365). I don't know if it's lazy to include them all like that. The
other rt* firmware expressions are currently broken, I'll remove them
in a week in favor of ralink_fw if there are no objections.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] [Nix-commits] SVN commit: nix - r31256 - nixpkgs/trunk/pkgs/os-specific/linux/firmware/rt2860

[Cillian de Róiste]

2012/1/3 Lluís Batlle i Rossell :
> On Tue, Jan 03, 2012 at 10:02:36PM +, Cillian de Roiste wrote:
>> Author: cillian
>> Date: Tue Jan  3 22:02:34 2012
>> New Revision: 31256
>> URL: https://nixos.org/websvn/nix/?rev=31256&sc=1
>>
>> Log:
>> Ralink firmware is no longer available directly from ralinktech.com, it is 
>> now available from git.kernel.org. I've used the debian svn repo here 
>> instead for convenience
>
> What if we made an expression for all those ralink? the rt73 expression would
> have that very similar builder too.

That would be great. I notice that other distros package them all
together: http://packages.debian.org/wheezy/firmware-ralink
Should we do it like that, or is there some value in keeping each one separate?


> ___
> 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] Emacs 23.3 incompatible with svn 1.7 (vc-svn.el)

[Cillian de Róiste]

Oops! I didn't mean to hit the send button, I intended to to add a patch
instead! Anyway, maybe it is of interest to someone :)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Emacs 23.3 incompatible with svn 1.7 (vc-svn.el)

[Cillian de Róiste]

Hi,

The version of vc-svn bundled with Emacs 23.3 doesn't support svn 1.7.
I guess it would be odd to add a patch to the Emacs expression to
update this file but you can also just grab a more recent version and

http://bzr.savannah.gnu.org/lh/emacs/trunk/download/cyd%40stupidchicken.com-20110212011253-gu3a312crz5d6hl1/vcsvn.el-20091113204419-o5vbwnq5f7feedwu-2575/vc-svn.el
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] CFQ I/O scheduler can't boot my system

[Cillian de Róiste]

On Wed, Sep 14, 2011 at 4:09 PM, Eelco Dolstra  wrote:
> Hi,
>
> On 09/07/2011 06:27 PM, Peter Simons wrote:
>
>>   >>>  This should be fixed now (r29027, tested with Linux 2.6.35).
>>   >>>
>>   >>>   I still get this hang unless I set elevator=noop at boot. Using
>>   >>  linuxPackages_2_6_39.
>>   >>
>>   >
>>   >  I also ran into this issue today with both linuxPackages_2_6_39 and
>>   >  linuxPackages_2_6_38_ati
>>
>> same here ... my system doesn't boot using the latest configuration.
>
> Do you (and others with this problem) have the boot.initrd.kernelModules
> option set in configuration.nix?  If so, what's the value?

It was set as follows during installation (in hardware-configuration.nix):
boot.initrd.kernelModules = [ "ahci" "ohci_hcd" "ehci_hcd"
"pata_atiixp" "xhci" "usb_storage" "usbhid" ];

Thanks,
Cillian
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev