Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: in some builds, no version information is present #3

Merged
merged 1 commit into from
Sep 17, 2017

Conversation

yrashk
Copy link
Contributor

@yrashk yrashk commented Sep 17, 2017

This causes an exception during module initialization.

In particular, NixOS builds of Awesome WM currently have version
set to "devel", where the problem was observed.

Solution: check version information in can_update_size
only if version information was matched

This causes an exception during module initialization.

In particular, NixOS builds of Awesome WM currently have version
set to "devel", where the problem was observed.

Solution: check version information in can_update_size
only if version information was matched
@coldfix coldfix merged commit 863ac08 into deficient:master Sep 17, 2017
@coldfix
Copy link
Member

coldfix commented Sep 17, 2017

Thanks!

@yrashk
Copy link
Contributor Author

yrashk commented Sep 17, 2017

For reference, I submitted a patch to NixOS to build awesome with proper versioning information: NixOS/nixpkgs#29510

@coldfix
Copy link
Member

coldfix commented Sep 18, 2017

Great :)

A bit off-topic: I was wondering if you happen to know anything concerning the following issues I had when I recently installed nixos onto a multiboot system along with windows and archlinux (if not, don't worry, I'm not trying to involve you in a debug session/support thread or anything):

  • my grub boot menu generated by nixos contains an entry for archlinux with the correct title and partition and everything, but selecting this entry actually just boots nixos. On the other hand, since having installed nixos, the grub-mkconfig command on archlinux hangs for maybe 30minutes and doesn't seem to work either. As a workaround, generating the boot menu via nixos and manually adding an archlinux menuitem using boot.loader.grub.extraEntries seems to work, but it would be nice and much more portable, if this worked correctly using the default mechanism.

  • I'm using a custom keyboard layout, based on dvorak, which I normally just copy into /usr/share/X11/xkb/symbols. However, this is not that easy on nix where it seems that one would have to packageOverride a rather involved patch to one of the basic xorg packages, as described here. However, this particular patch looks high-maintenance to me and has a chance of being outdated by future modifications of the package. Furthermore, I don't want to risk having to build all X dependent packages from source. As a workaround, I could go for setting the keyboard layout in an autostart script using setxkblayout -I /path/to/directory, but again, I'd prefer a simpler solution that works directly with the config.

I'd be happy for any ideas or hints, maybe you have experienced something similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants