text:
nixos/system/boot/initrd-openvpn: New openvpn options for initrd

The module in this commit adds new options that allows the integration of an OpenVPN client into the initrd.
Motivation for this change
The main motivation for this change is the ability to remotely unlock LUKS containers on hosts that are behind a restrictive firewall, but are able to connect to other hosts. Using a VPN connection allows that host to tunnel into a network that might be reachable by external devices (either by providing a public IPv4/6 address or by connecting into a private VPN).
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

I like this - I don't have a need for it, but it looks like the right thing to do.
The only thing that concerns me is stuff that messes around with initrd without a test. Something basic would be fine as long as we are sure that enabling this doesn't break booting.

I'll have a look into writing a test and will add it as soon as it is ready.

Would it make sense to squash the two commits, as they both just add tests (and one commit consumes the other one)?

This is cool! I'm still a bit -1 on this though. While we don't have any formal criteria for inclusion/exclusion of features, I think this is a use case specific and rare enough that it will only be used by you and might be better off in your personal config than in nixpkgs.

I support this.
I think the usecase is not too niche.
Imagine the following usecase:
You want to run a homeserver with encrypted disks
Your ISP does not give you a public IP
Your homeserver reboots/looses power
You are currently not at home
Now you need a possibility to connect to the homeserver and unlock the disks.
Assuming you have another server which has a public IP address you can connect to it via VPN and use it as a jump server to enter the password

I'm also a big fan of this PR, sadly I couldn't test it because of general busyness. Codewise it looks good to me.

@Amarandus, can you get someone else to test it as well (again due it messing with the boot process) to make sure all is good? Maybe a post on https://discourse.nixos.org if you don't have anyone at hand to try it out?

So, I finally got time to update this PR and squashed the commits together.

I removed most options as they were unnecessary (adding additional files like certificates should be possible with boot.initrd.secrets directly, as the internal-attribute was removed recently there. Alternatively, you can inline them into the configuration)

Besides enable, there is only the option configuration, which expects a file path as a string (similar to boot.initrd.network.ssh.hostKeys)
Configuration is now always handled by boot.initrd.secrets, so there is only one place which decides whether files get into the store or not (depends on the bootloader)
It is not expected anymore to add iproute /bin/ip to the config - it will be appended automatically

The test now uses the python test infrastructure

First test: Checks whether booting with an invalid config breaks
Second test: Checks whether a valid configuration really works

authors: Amarandus CRTified Lassulus duhirsch lheckemann peterhoeg


text:
fix bind broken build

When building bind with
nix-shell --pure -I nixpkgs=/path-to/nixpkgs -p bind

I get configure output error:
configure: error: found libjson include but not library.

This PR allows it to build again. I do not know if this is the correct way to resolve the issue, but it builds it on my machine.
cc/ @viric @peti

I'm unable to reproduce that problem (tried on master 883ee4dd72). It's saying
checking for json library... no

I would expect the problem is that your builds aren't chrooted, so the script picks up some stuff from /usr/*. Well, maybe we should have the json support anyway?

@vcunat I think that's likely to be the case! My output gives yes for the json library check. I'm going to close this, but if the maintainers @viric or @peti think it's good to include json support, this is available for merging.

What exactly does it mean for bind to have JSON support? What kind of functionality would that enable?

I don't use bind but I did a little searching to see what JSON support might mean. It looks like the statistics server can use it to return JSON results:
ftp://ftp.isc.org/isc/bind9/cur/9.10/doc/arm/Bv9ARM.pdf
https://www.isc.org/blogs/bind-9-10-statistics-troubleshooting-and-zone-configuration/
"JSON is significantly faster than XML, but is not supported yet on Windows."

My impression is that we should build BIND with --without-json or something like that to prevent it from picking up the library from an impure location. Or, alternatively, we might be able to replace /usr-based search paths in the configure script with non-sense to make sure those kind of tests always fail.

source: gharchive/pull-request

authors: peti ryantm vcunat

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
ttygif init at 1.4.0

Motivation for this change
add ttygif to nixpkgs
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@GrahamcOfBorg build ttygif

@matthewbauer I not sure if I did this right. I set the platform to platforms.linux. Does this work or did you have something else in mind?

that works

@GrahamcOfBorg build ttygif

authors: jonringer moaxcp


text:
utsushi: 3.59.2 -> master

Motivation for this change
Update.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@GrahamcOfBorg build utsushi

@GrahamcOfBorg build utsushi

There still is an issue in the package, that needs to be fixed either through a patch in this PR or through a new release - so please don't merge yet.

@GrahamcOfBorg build utsushi

@Lassulus This could finally be ready for merge. Can you remove the Draft status?

Uh you could do that yourself, but master is not really a released version. We really prefer stable released versions upstream. But if you really want to bump this to an unreleased git rev. Then the correct version number would be "unstable-2020-11-11" (the date of the pinned commit)

We had a discussion about this already. Epson releases with version numbers, however, they almost never fix things. There is a community repo which incorporates loads of fixes, but said community repo does not have releases at all, yet. I would opt for the community repo, I'm immediately aware of at least two bugs which are fixed by doing so.
I adjusted the version number accordingly, thank you for that hint @Lassulus  :smile:


text:
yafaray-core: 3.3.0 -> 3.4.1

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/YafaRay/Core/releases.
meta.description for yafaray-core is: "A free, open source raytracer"
meta.homepage for yafaray-core is: "http://www.yafaray.org"
Updates performed:

Version update
Quoted meta.homepage for RFC 45

Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.4.1 with grep in /nix/store/xd6mp574kgx9d0sn0rr4vv80kchjdcyc-yafaray-core-3.4.1

directory tree listing: https://gist.github.com/3a026c81064f63ff464b1f1e206b7a6c

du listing: https://gist.github.com/14b6d614db64b11e3456516c82241a7a

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
yafaray-core

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xd6mp574kgx9d0sn0rr4vv80kchjdcyc-yafaray-core-3.4.1 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A yafaray-core https://github.com/r-ryantm/nixpkgs/archive/fe72fe28d7503ad8888ef418f36090a3c8bfdd17.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xd6mp574kgx9d0sn0rr4vv80kchjdcyc-yafaray-core-3.4.1
ls -la /nix/store/xd6mp574kgx9d0sn0rr4vv80kchjdcyc-yafaray-core-3.4.1/bin

cc @Hodapp87 for testing.

Result of nixpkgs-review pr 84795 1

1 package built:
- yafaray-core

authors: bhipple r-ryantm


text:
ocamlPackages.x509: 0.11.1 → 0.11.2

Motivation for this change
https://github.com/mirleft/ocaml-x509/releases/tag/v0.11.2
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build ocamlPackages.x509 jackline ocamlPackages.irmin-unix

authors: anmonteiro vbgl


text:
qtstyleplugin-kvantum-qt4: 0.15.2 -> 0.15.3

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tsujan/Kvantum/releases.
meta.description for qtstyleplugin-kvantum-qt4 is: "SVG-based Qt4 theme engine"
meta.homepage for qtstyleplugin-kvantum-qt4 is: "https://github.com/tsujan/Kvantum"
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/3e0fd4b112a5c2d37cd54e2e2b2fcbef

du listing: https://gist.github.com/cf548a1c46932c63368765196ef7a340

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
qtstyleplugin-kvantum-qt4

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xglklgwqkqklmdazkz7vkjwr0a2af60q-qtstyleplugin-kvantum-qt4-0.15.3 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A qtstyleplugin-kvantum-qt4 https://github.com/r-ryantm/nixpkgs/archive/a353657b275906df780bb0a98d8884a7fd7984c5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xglklgwqkqklmdazkz7vkjwr0a2af60q-qtstyleplugin-kvantum-qt4-0.15.3
ls -la /nix/store/xglklgwqkqklmdazkz7vkjwr0a2af60q-qtstyleplugin-kvantum-qt4-0.15.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:
- qtstyleplugin-kvantum-qt4

Maintainer pings
cc @bugworm for testing.

The bot has built all dependent packages and the changelog looks good.


text:
cde-gtk-theme: small adjustments

Motivation for this change

Don't build on Hydra, its just a packed theme
Rename derivation from "cde-motif-theme" to "cdetheme", because theme folder name is "cdetheme", so there will be less confusion
I.e. user need to set "cdetheme" in their gtkrc, so lets name the derivation the same

    [Settings]
    gtk-theme-name=cdetheme

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/186

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/205

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/221

@romildo Thank you!

authors: gnidorah nixos-discourse


text:
Add all Iosevka build plans, including Aile, Etoile, and Sparkle

Motivation for this change
This adds all of the Iosevka variants.
I know it's a lot of copy-paste code in all-packages.nix, but I think if we want top-level packages (maybe we don't) then we need to do this, or have some attrset merge at the bottom of the file. We also could, if we wanted, generate this list by looking at build-plans.toml in the Iosekva source.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I see two separate questions here:

Should the variants all live as top-level packages, or should it be iosevka.default, iosevka.aile, etc. The awkward one is the default Iosevka one. Another option is leaving that as top-level iosevka, and then having a iosevkaVariants attrset containing all the other ones.
Should the variants be hardcoded or dynamically generated? I would classify even using an update script to generate the variants as hard-coded. Dynamically generating would be passing the TOML in some way in nix code in order to define the iosevka attrset.

#101132 might be of interest to you.

Oh, exciting! I do have to say, I don't love the interface of passing in the variant as a string when we know there are only a few variants we'll accept, but if I can come up with a better interface I'll submit a new PR.

The list of variants is subject to change over time. Some have been removed (IIRC), while some (such as the variable width ones) have been added.

That's pretty fair.


text:
numactl: 2.0.13 -> 2.0.14

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/numactl/numactl/releases.
meta.description for numactl is: "Library and tools for non-uniform memory access (NUMA) machines"
meta.homepage for numactl is: "https://github.com/numactl/numactl"
meta.changelog for numactl is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.0.14 with grep in /nix/store/3nijk82kyddk0929ndhrmis3vcakqy0q-numactl-2.0.14

directory tree listing: https://gist.github.com/1bdf9537999c5ae370260b370d4a0867

du listing: https://gist.github.com/1c423c65b2137d908bd44dfc0be613f4

Rebuild report (if merged into master) (click to expand)

4262 total rebuild path(s)

1717 package rebuild(s)

1637 x86_64-linux rebuild(s)
1402 i686-linux rebuild(s)
7 x86_64-darwin rebuild(s)
1216 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
DisnixWebService
MIDIVisualizer
abiword
acoustidFingerprinter
adapta-gtk-theme
adoptopenjdk-icedtea-web
aegisub
ahoviewer
airtame
akonadi
akregator
alchemy
alda
aldor
alephone
almanah
alpine-make-vm-image
amarok
amarok-kf5
ammonite
ammonite_2_12
ammonite_2_13
anki
ankisyncd
apache-directory-studio
apache-flex-sdk
apktool
apostrophe
aqemu
aravis
arc-theme
ardour
arduino
arduino-core
areca
arx-libertatis
asc-key-to-qr-code-gif
asciidoc-full
asciidoc-full-with-plugins
asciidoctorj
aspectj
astroid
astrolabe-generator
asymptote
atlassian-cli
attract-mode
audacious
audaciousQt5
audacity
audio-recorder

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3nijk82kyddk0929ndhrmis3vcakqy0q-numactl-2.0.14 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A numactl https://github.com/r-ryantm/nixpkgs/archive/9015f06673d9c2c549bfe1e0cf9f6d0fe0c1bd75.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3nijk82kyddk0929ndhrmis3vcakqy0q-numactl-2.0.14
ls -la /nix/store/3nijk82kyddk0929ndhrmis3vcakqy0q-numactl-2.0.14/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings

@GrahamcOfBorg build openmpi openmolcas

@GrahamcOfBorg build numatop slurm

authors: markuskowa r-ryantm


text:
Configuration level to define when to not serialize the Optional property (undefined)

This was achieved in NewtonSoft.Json through DefaultContractResolver. At the time of implementation, System.Text.Json does not have anything equivalent.
People have logged following issue.
https://github.com/dotnet/runtime/issues/31257
Microsoft's potential equivalent, need to test out.
https://github.com/dotnet/runtime/issues/63686
Part of change in:
https://github.com/dotnet/runtime/issues/36785

.net 8 change in coming.
https://github.com/dotnet/runtime/issues/71967

https://github.com/dotnet/runtime/blob/256bf67b969c56f8b3e87c506eb613cce36e778f/src/libraries/System.Text.Json/src/System/Text/Json/Serialization/Metadata/JsonPropertyInfo.cs

source: gharchive/issue

repo: Nness/Optional


text:
🛑 libreddit libreddit.domain.glass is down

In 40b8741, libreddit libreddit.domain.glass (https://libreddit.domain.glass) was down:

HTTP code: 503
Response time: 138 ms

Resolved: libreddit libreddit.domain.glass is back up in a099bac.

repo: NoPlagiarism/services-personal-upptime


text:
🛑 BreezeWiki breezewiki.hyperreal.coffee is down

In bc6e78f, BreezeWiki breezewiki.hyperreal.coffee (https://breezewiki.hyperreal.coffee) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BreezeWiki breezewiki.hyperreal.coffee is back up in 69cc021 after 1 hour, 14 minutes.


text:
🛑 libreddit l.opnxng.com is down

In b696224, libreddit l.opnxng.com (https://l.opnxng.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: libreddit l.opnxng.com is back up in 2259ffd after 5 minutes.


text:
🛑 libreddit snoo.habedieeh.re is down

In 4cb9591, libreddit snoo.habedieeh.re (https://snoo.habedieeh.re) was down:

HTTP code: 0
Response time: 0 ms

Resolved: libreddit snoo.habedieeh.re is back up in ecfd67e.


text:
Implement Basescan algorithm

replacing bootstrap and MORE_POINTS

What is meant by basescan? Can you give a quick synopsis of its benefits over bootstrap/more_points?

MORE_POINTS adds bogus points which are reported by the API, this was nice when you still want to find something, but is in my opinion only burning hashes
--bootstrap does one scan of the entire area, basescan does the same as bootstrap, but only that it scans every point once within every quarter of an hour (this should garantee that it will find every point)

Very nice, even includes visualization of basescan points. Will give it a try tomorrow.

I will at some point try and redo this in a different way as scanning large areas with only a few workers (rural areas) is kind of a problem

I Updated it and it should be working,
but I get a huge amount of  Nothing seen by [...]. Speed [<5]
and Empty altitude response for [...], falling back to random.
Maybe there is someone else who would like to debug this,
I may but I'd guess not before easter

According to what I read, this is removing the Bounds check. Was that intentional ?

no it does not remove the bounds check, it has only not been updated to the current version of bounds check, I'll update it if I find some time, but there are other things I'm currently working on so this won't be to soon

authors: evenly-epic-mule j16sdiz nehcney

repo: Noctem/Monocle


text:
nodeos-init musl command not found

I've got that error with Arch Linux
Compiling init
make: x86_64-nodeos-linux-musl-gcc: Kommando nicht gefunden
<eingebaut>: die Regel für Ziel „init.o“ scheiterte
make: *** [init.o] Fehler 127
rmdir: konnte '/home/philipp/Dokumente/github/NodeOS/node_modules/nodeos-barebones/build/nocona' nicht entfernen: Datei oder Verzeichnis nicht gefunden

Try to install nodeos-barebones again ?!

I just cloned the repo and got  this

Does this stil apply on master?

I get errors but not this one

I get errors but not this one

Can you post them? If you have some bizarre problems, maybe you would clone the NodeOS repo again and start over after saving your changes somewhere...

> genfatfs@1.0.1 install /home/philipp/Dokumente/NodeOS/node_modules/nodeos-rootfs/node_modules/genfatfs
> prebuild-install -d https://github.com/NodeOS/genfatfs/releases/download/v{version}/{platform}-{arch}.tar.gz || npm run build

> nodeos-rootfs@1.0.0-RC2.1 install /home/philipp/Dokumente/NodeOS/node_modules/nodeos-rootfs
> scripts/install

     fetch : https://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-6.03.tar.gz
  progress : [====================] 100% 0.0s

npm ERR! Linux 4.6.2-1-ARCH
npm ERR! argv "/home/philipp/.nvm/versions/node/v4.4.2/bin/node" "/home/philipp/.nvm/versions/node/v4.4.2/bin/npm" "i"
npm ERR! node v4.4.2
npm ERR! npm  v2.15.0
npm ERR! path /home/philipp/Dokumente/NodeOS/node_modules/nodeos-usersfs/node_modules/nodeos-nodejs/node_modules/nodeos-cross-toolchain/bin/addr2line
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/home/philipp/Dokumente/NodeOS/node_modules/nodeos-usersfs/node_modules/nodeos-nodejs/node_modules/nodeos-cross-toolchain/bin/addr2line'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     /home/philipp/Dokumente/NodeOS/npm-debug.log

Yeah, well... I've deprecated npm2 since now dependencies on npm3 has a deterministic flowchart :-P Upgrade to Node.js >= 5.0.0 or npm >= 3.0.0 and you should go :-)

install process with node 5.12.0 seems to be fine but i get another error that dont is displayed
0 info it worked if it ends with ok
1 verbose cli [ '/home/philipp/.nvm/versions/node/v5.12.0/bin/node',
1 verbose cli   '/home/philipp/.nvm/versions/node/v5.12.0/bin/npm',
1 verbose cli   'start' ]
2 info using npm@3.8.6
3 info using node@v5.12.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle NodeOS@1.0.0-RC2~prestart: NodeOS@1.0.0-RC2
6 silly lifecycle NodeOS@1.0.0-RC2~prestart: no script for prestart, continuing
7 info lifecycle NodeOS@1.0.0-RC2~start: NodeOS@1.0.0-RC2
8 verbose lifecycle NodeOS@1.0.0-RC2~start: unsafe-perm in lifecycle true
9 verbose lifecycle NodeOS@1.0.0-RC2~start: PATH: /home/philipp/.nvm/versions/node/v5.12.0/lib/node_modules/npm/bin/node-gyp-bin:/home/philipp/Dokumente/NodeOS/node_modules/.bin:/home/philipp/.nvm/versions/node/v5.12.0/bin:/home/philipp/.nvm/versions/node/v5.12.0/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
10 verbose lifecycle NodeOS@1.0.0-RC2~start: CWD: /home/philipp/Dokumente/NodeOS
11 silly lifecycle NodeOS@1.0.0-RC2~start: Args: [ '-c', 'scripts/start' ]
12 silly lifecycle NodeOS@1.0.0-RC2~start: Returned: code: 1  signal: null
13 info lifecycle NodeOS@1.0.0-RC2~start: Failed to exec start script
14 verbose stack Error: NodeOS@1.0.0-RC2 start: `scripts/start`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/home/philipp/.nvm/versions/node/v5.12.0/lib/node_modules/npm/lib/utils/lifecycle.js:239:16)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at EventEmitter.emit (events.js:185:7)
14 verbose stack     at ChildProcess.<anonymous> (/home/philipp/.nvm/versions/node/v5.12.0/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at ChildProcess.emit (events.js:185:7)
14 verbose stack     at maybeClose (internal/child_process.js:850:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid NodeOS@1.0.0-RC2
16 verbose cwd /home/philipp/Dokumente/NodeOS
17 error Linux 4.6.2-1-ARCH
18 error argv "/home/philipp/.nvm/versions/node/v5.12.0/bin/node" "/home/philipp/.nvm/versions/node/v5.12.0/bin/npm" "start"
19 error node v5.12.0
20 error npm  v3.8.6
21 error code ELIFECYCLE
22 error NodeOS@1.0.0-RC2 start: `scripts/start`
22 error Exit status 1
23 error Failed at the NodeOS@1.0.0-RC2 start script 'scripts/start'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the NodeOS package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     scripts/start
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs NodeOS
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls NodeOS
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Also i tried to install with 6.2.1 and got very strange errors

Have you executed npm run build after npm install? Now dependencies downloading and build process are splitted due how npm3 works. Yes, I forgot to add it to the docs, sorry... :-(

Thats maybe the key to the thing

Thats maybe the key to the thing

Check it. If it works, could you be able to update the readme?

@piranna got this after npm start
→ npm start                                                           [fb487d9]

> NodeOS@1.0.0-RC2 start /home/philipp/Dokumente/NodeOS
> scripts/start

qemu-system-x86_64: error while loading shared libraries: libcurl-gnutls.so.4: cannot open shared object file: No such file or directory

You need to install the shared library. Exec sudo bin/install-dependencies :-)
I've tried to build a static version of qemu, but libsdl needed for the framebuffer is giving problems... :-( I would remove it and allow only a text interface and maybe use the VNC interface for graphic one, but this would require a VNC client to access it... What do you think?

I dont have any idea for what the framebuffer is for and whats a vnc interface is, ive never worked on this low level but id like to know what it is

Framebuffer is a simple way to paint graphics on the screen, for example the small Tux penguin on boot is paint using framebuffer by the kernel itself. VNC is a protocol for remote graphic sessions like TeamViewer or RemoteDesktop, so using it we would not need to use SDL to paint a "real" screen.

@luii if you want a bit more, the framebuffer represents the byte storage of a graphic display, like a monitor. You interact with it via shared memory and alter it's contents much like an RGB image file.

I think the best option would be to remove SDL support and use by default only a text interface on the same terminal it's executed, and the ones that want to use a graphic interface, then they use a VNC viewer. Thoughs?

I updated to npm@3  (.10.6)
I tried npm run build
I treid bin/install-dependancies (no dpkg; am also on arch)
[root@tower2 NodeOS]# npm3 install nodeos-barebones
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
NodeOS@1.0.0-RC2 /home/d3x0r/work/NodeOS
├── UNMET PEER DEPENDENCY nodeos-barebones@1.0.0-RC2.3 (git://github.com/nodeos/nodeos-barebones.git#36e886e120ed54569b99aeb2630ac300634b7084)
├── UNMET PEER DEPENDENCY nodeos-initramfs@1.0.0-RC2.4 (git://github.com/nodeos/nodeos-initramfs.git#1f48f4150cc62a83c8c73c6a4ad86b8856091452)
└─┬ nodeos-usersfs@1.0.0-RC2 (git://github.com/nodeos/nodeos-usersfs.git#1d20cad02ce8466a7b99922857161388de087d99)
├── bin-getty@0.0.0  extraneous (git://github.com/nodeos/node-bin-getty.git#d8346f15860de4f5b6cc534217429a00016e5793)
├── bin-ifconfig@0.0.0  extraneous (git://github.com/nodeos/ifconfig.git#f07ccd16f4ad8b4c47c2880aad75179d99390ab7)
├── bin-ip@0.0.0  extraneous (git://github.com/nodeos/ip.git#f0e685493db31ca9117b93245d8a8e85478b476c)
└── bin-nsh@0.4.0  extraneous (git://github.com/piranna/nsh.git#51d8131d34d1f78937e54dc33b5e954718212632)
npm WARN nodeos-rootfs@1.0.0-RC2.0 requires a peer of nodeos-barebones@1.0.0-RC2.2 but none was installed.
npm WARN nodeos-rootfs@1.0.0-RC2.0 requires a peer of nodeos-initramfs@1.0.0-RC2.3 but none was installed.
was also that version og gcc- not found.

What's exactly the problem do you have?
El 3/9/2016 5:22, "d3x0r" notifications@github.com escribió:

I updated to npm@3 (.10.6)
I tried npm run build
I treid bin/install-dependancies (no dpkg; am also on arch)
[root@tower2 NodeOS]# npm3 install nodeos-barebones
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or
higher to avoid a RegExp DoS issue
NodeOS@1.0.0-RC2 /home/d3x0r/work/NodeOS
├── UNMET PEER DEPENDENCY nodeos-barebones@1.0.0-RC2.3 (git://
github.com/nodeos/nodeos-barebones.git#36e886e120ed54569b99aeb2630ac3
00634b7084)
├── UNMET PEER DEPENDENCY nodeos-initramfs@1.0.0-RC2.4 (git://
github.com/nodeos/nodeos-initramfs.git#1f48f4150cc62a83c8c73c6a4ad86b
8856091452)
└─┬ nodeos-usersfs@1.0.0-RC2 (git://github.com/nodeos/nodeos-usersfs.git#
1d20cad02ce8466a7b99922857161388de087d99)
├── bin-getty@0.0.0 extraneous (git://github.com/nodeos/node-
bin-getty.git#d8346f15860de4f5b6cc534217429a00016e5793)
├── bin-ifconfig@0.0.0 extraneous (git://github.com/nodeos/ifconfig.git#
f07ccd16f4ad8b4c47c2880aad75179d99390ab7)
├── bin-ip@0.0.0 extraneous (git://github.com/nodeos/ip.git#
f0e685493db31ca9117b93245d8a8e85478b476c)
└── bin-nsh@0.4.0 extraneous (git://github.com/piranna/nsh.git#
51d8131d34d1f78937e54dc33b5e954718212632)
npm WARN nodeos-rootfs@1.0.0-RC2.0 requires a peer of
nodeos-barebones@1.0.0-RC2.2 but none was installed.
npm WARN nodeos-rootfs@1.0.0-RC2.0 requires a peer of
nodeos-initramfs@1.0.0-RC2.3 but none was installed.
was also that version og gcc- not found.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/248#issuecomment-244523633, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfviSiiG6vVuMX8A_mdmPgR8B-VcEZks5qmOf3gaJpZM4IxQNv
.

"What's exactly the problem do you have?"
UNMET PEER DEPENDENCY nodeos-barebones@1.0.0-RC2.3 (git://github.com/nodeos/nodeos-barebones.git#36e886e120ed54569b99aeb2630ac300634b7084)
├── UNMET PEER DEPENDENCY nodeos-initramfs@1.0.0-RC2.4 (git://github.com/nodeos/nodeos-initramfs.git#1f48f4150cc62a83c8c73c6a4ad86b8856091452)
-or-
x86_64-nodeos-linux-musl-gcc: Command not found

Unmeet dependencies are not the problem, you should be doing it wrong in
other place. I can't be able to test NodeOS building in Arch linux so you
are alone here, but I can help you and accept pull-requests to support it.
El 3/9/2016 6:12, "d3x0r" notifications@github.com escribió:

"What's exactly the problem do you have?"
UNMET PEER DEPENDENCY nodeos-barebones@1.0.0-RC2.3 (git://
github.com/nodeos/nodeos-barebones.git#36e886e120ed54569b99aeb2630ac3
00634b7084)
├── UNMET PEER DEPENDENCY nodeos-initramfs@1.0.0-RC2.4 (git://
github.com/nodeos/nodeos-initramfs.git#1f48f4150cc62a83c8c73c6a4ad86b
8856091452)
-or-
x86_64-nodeos-linux-musl-gcc: Command not found
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/248#issuecomment-244525400, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvii1rjTdzwlhoYWsJte0vbNVyPriks5qmPOVgaJpZM4IxQNv
.

how about some hints to diagnose why it is failing?
why I can't npm3 install  or npm3 install ndoeos-barebones ? always fails.

@d3x0r Is 0.10.6 your node version ? If so, could you update that to a newer ? I ran into some problems (on arch too) when I tried building nodeOS with 'very old' versions of node

No Node 6.5.0 is my node version.
npm 3 has a sub-version of .10.6     (3.10.6)

@d3x0r Im using Arch too, please install the following Prerequisites and Dependencies from this page

bin/installDependencies should be updated to detect Arch linux and install
the correct dependencies...
El 3/9/2016 9:37, "Philipp Czarnetzki" notifications@github.com escribió:

@d3x0r https://github.com/d3x0r Im using Arch too, please install the
following Prerequisites and Dependencies from this page
https://github.com/NodeOS/NodeOS/wiki/Building-From-Source#step-2-arch-linux-dependencies
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/248#issuecomment-244532547, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvr3eFIat9Rprwd__-V67UTpwV4zcks5qmSO1gaJpZM4IxQNv
.

We could use something like https://github.com/arve0/system-install
El 3/9/2016 9:44, "piranna@gmail.com" piranna@gmail.com escribió:

bin/installDependencies should be updated to detect Arch linux and install
the correct dependencies...
El 3/9/2016 9:37, "Philipp Czarnetzki" notifications@github.com
escribió:

@d3x0r https://github.com/d3x0r Im using Arch too, please install the
following Prerequisites and Dependencies from this page
https://github.com/NodeOS/NodeOS/wiki/Building-From-Source#step-2-arch-linux-dependencies
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/248#issuecomment-244532547, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvr3eFIat9Rprwd__-V67UTpwV4zcks5qmSO1gaJpZM4IxQNv
.

[root@tower2 b]# pacman -S gcc texinfo python2 bc pixman lib32-pixman cdrkit cpio autoconf automake sdl
warning: gcc-6.1.1-5 is up to date -- reinstalling
warning: texinfo-6.1-4 is up to date -- reinstalling
warning: python2-2.7.12-1 is up to date -- reinstalling
warning: pixman-0.34.0-1 is up to date -- reinstalling
error: target not found: lib32-pixman
warning: cpio-2.12-3 is up to date -- reinstalling
warning: autoconf-2.69-3 is up to date -- reinstalling
warning: automake-1.15-1 is up to date -- reinstalling
warning: sdl-1.2.15-7 is up to date -- reinstalling
No help.

Did some more digging, and in node_modules there are things like nodeos-barebones (with a few small files)
Unfortunatly in nodeos-cross-toolchain this error shows up....
In file included from /home/d3x0r/work/NodeOS/node_modules/nodeos-barebones/node_modules/nodeos-cross-toolchain/deps/gcc/gcc/cp/except.c:1023:0:
cfns.gperf: In function 'const char* libc_name_p(const char*, unsigned int)':
cfns.gperf:101:1: error: 'const char* libc_name_p(const char*, unsigned int)' redeclared inline with 'gnu_inline' attribute
cfns.gperf:26:14: note: 'const char* libc_name_p(const char*, unsigned int)' previously declared here
cfns.gperf: At global scope:
cfns.gperf:26:14: warning: inline function 'const char* libc_name_p(const char*, unsigned int)' used but never defined
make[2]: *** [Makefile:1065: cp/except.o] Error 1
make[2]: *** Waiting for unfinished jobs....

which if I take the error literally and a search I find
https://github.com/mxe/mxe/issues/1361
but then the nodeos-cross-toolchain disappears :(  so I can't really see what version of GCC it is that's failing... the previous issue has a fix from 19 days ago; but doesn't matter if it's not gcc 4.8/9 something

What version of Node js/npm and gcc are you using on your system?
El 4/9/2016 23:29, "d3x0r" notifications@github.com escribió:

Did some more digging, and in node_modules there are things like
nodeos-barebones (with a few small files)
Unfortunatly in nodeos-cross-toolchain this error shows up....
In file included from /home/d3x0r/work/NodeOS/node_modules/nodeos-barebones/node_modules/nodeos-cross-toolchain/deps/gcc/gcc/cp/except.c:1023:0:
cfns.gperf: In function 'const char* libc_name_p(const char*, unsigned int)':
cfns.gperf:101:1: error: 'const char* libc_name_p(const char*, unsigned int)' redeclared inline with 'gnu_inline' attribute
cfns.gperf:26:14: note: 'const char* libc_name_p(const char*, unsigned int)' previously declared here
cfns.gperf: At global scope:
cfns.gperf:26:14: warning: inline function 'const char* libc_name_p(const char*, unsigned int)' used but never defined
make[2]: *** [Makefile:1065: cp/except.o] Error 1
make[2]: *** Waiting for unfinished jobs....
which if I take the error literally and a search I find
mxe/mxe#1361 https://github.com/mxe/mxe/issues/1361
but then the nodeos-cross-toolchain disappears :( so I can't really see
what version of GCC it is that's failing... the previous issue has a fix
from 19 days ago; but doesn't matter if it's not gcc 4.8/9 something
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/248#issuecomment-244629881, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvuhJBzY2VyBuj9cz_sFfThAhzQIyks5qmzg_gaJpZM4IxQNv
.

[root@tower2 ~]# npm -v
3.10.6
[root@tower2 ~]# node -v
v6.5.0
[root@tower2 ~]# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --disable-multilib --disable-werror --enable-checking=release
Thread model: posix
gcc version 6.1.1 20160802 (GCC)

Seems to be a problem in the version of gcc of Arch, try using an older
one. Reference build environment is Ubuntu, and nodeos-cross-compiler
generates a gcc 5.3.0 toolchain.
El 5/9/2016 7:53, "d3x0r" notifications@github.com escribió:

[root@tower2 ~]# npm -v
3.10.6
[root@tower2 ~]# node -v
v6.5.0
[root@tower2 ~]# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --disable-multilib --disable-werror --enable-checking=release
Thread model: posix
gcc version 6.1.1 20160802 (GCC)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/248#issuecomment-244663780, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvgTmp2ts_-1A5iJDRnK5rTqc17uxks5qm65EgaJpZM4IxQNv
.

Any update on this? @luii and @d3x0r, are you still having problems with Arch, or we can close this?

I recently updated
npm -v
3.10.7
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/6.2.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --disable-multilib --disable-werror --enable-checking=release
Thread model: posix
gcc version 6.2.1 20160830 (GCC)
cd node_modules/nodeos-cross-toolchain
scripts/prebuild
scripts/build

And it still fails.
I updated scripts/prebuild to download 5.4.0 gcc but still use the 5.3.0 patch....
bin/build doesn't like running twice in a row with a partial build ... it doesn't re-extract linux headers somehow?
[root@tower2 nodeos-cross-toolchain]# scripts/build
Compiling musl
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/musl/configure: unknown option --silent
checking for C compiler...
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/musl/configure: cannot find a C compiler

I am getting a TON of these warnings; maybe a patch could help; mabye it's expanding multiple levels of macros...
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/gcc/config/elfos.h:170:24: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
       fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",  \
                        ^
In file included from ./tm.h:51:0,
                 from /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/gcc/ddg.c:25:
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/gcc/defaults.h:126:24: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
       fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",  \
                        ^

Got a lot further.... but I suspect the patch has silently failed.
In file included from /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/libgcc2.c:27:0:
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/../gcc/tsystem.h:87:19: fatal error: stdio.h: No such file or directory
compilation terminated.
make[2]: *** [Makefile:466: _muldi3.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/libgcc2.c:27:0:
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/../gcc/tsystem.h:87:19: fatal error: stdio.h: No such file or directory
compilation terminated.
make[2]: *** [Makefile:466: _negdi2.o] Error 1
In file included from /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/libgcc2.c:27:0:
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/../gcc/tsystem.h:87:19: fatal error: stdio.h: No such file or directory
compilation terminated.
make[2]: *** [Makefile:466: _lshrdi3.o] Error 1
make[1]: *** [Makefile:13307: all-target-libgcc] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:881: all] Error 2
+ exit 52
+ err 52
+ rmStep /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/build/nocona/gcc_final
+ rm -rf /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/build/nocona/gcc_final
+ exit 52

I haven't used Arch before so I don't know what could be happening, sorry
:-(
El 11/9/2016 10:43 PM, "d3x0r" notifications@github.com escribió:

I recently updated
npm -v
3.10.7
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/6.2.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr
--libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --enable-libmpx --with-system-zlib --with-isl
--enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu
--disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object
--enable-linker-build-id --enable-lto --enable-plugin
--enable-install-libiberty --with-linker-hash-style=gnu
--enable-gnu-indirect-function --disable-multilib --disable-werror
--enable-checking=release
Thread model: posix
gcc version 6.2.1 20160830 (GCC)
cd node_modules/nodeos-cross-toolchain
scripts/prebuild
scripts/build
And it still fails.
I updated scripts/prebuild to download 5.4.0 gcc but still use the 5.3.0
patch....
bin/build doesn't like running twice in a row with a partial build ... it
doesn't re-extract linux headers somehow?
[root@tower2 nodeos-cross-toolchain]# scripts/build
Compiling musl
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/musl/configure: unknown option --silent
checking for C compiler...
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/musl/configure: cannot find a C compiler
I am getting a TON of these warnings; maybe a patch could help; mabye it's
expanding multiple levels of macros...
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/gcc/config/elfos.h:170:24: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",
^
In file included from ./tm.h:51:0,
from /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/gcc/ddg.c:25:
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/gcc/defaults.h:126:24: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",
^
Got a lot further.... but I suspect the patch has silently failed.
In file included from /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/libgcc2.c:27:0:
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/../gcc/tsystem.h:87:19: fatal error: stdio.h: No such file or directory
compilation terminated.
make[2]: *** [Makefile:466: _muldi3.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/libgcc2.c:27:0:
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/../gcc/tsystem.h:87:19: fatal error: stdio.h: No such file or directory
compilation terminated.
make[2]: *** [Makefile:466: _negdi2.o] Error 1
In file included from /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/libgcc2.c:27:0:
/home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/deps/gcc/libgcc/../gcc/tsystem.h:87:19: fatal error: stdio.h: No such file or directory
compilation terminated.
make[2]: *** [Makefile:466: _lshrdi3.o] Error 1
make[1]: *** [Makefile:13307: all-target-libgcc] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:881: all] Error 2

exit 52
err 52
rmStep /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/build/nocona/gcc_final
rm -rf /home/d3x0r/work/NodeOS/node_modules/nodeos-cross-toolchain/build/nocona/gcc_final
exit 52

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/248#issuecomment-246203353, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvokYIqi258J3JHrts3yN6IPMriDLks5qpGgCgaJpZM4IxQNv
.

I cant reproduce these errors with Arch
I got a lot of warnings but the build finished.
Successfully built Layer-3 image 'usersfs'

> NodeOS@1.0.0-RC2 postbuild /home/philipp/Dokumente/github/NodeOS
> scripts/postbuild

------------------------------------------
Success!
You just built a custom NodeOS image
------------------------------------------

- Interactively run your image with:
    npm start

λ philipp [Dokumente/github/NodeOS] at  master ✔
→ npm start                                                                                [6aede62]

> NodeOS@1.0.0-RC2 start /home/philipp/Dokumente/github/NodeOS
> scripts/start

qemu-system-x86_64: cannot initialize crypto: Unable to initialize gcrypt

→ gcc -v                                                                                [6aede62]
Es werden eingebaute Spezifikationen verwendet.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/lto-wrapper
Ziel: x86_64-pc-linux-gnu
Konfiguriert mit: /build/gcc-multilib/src/gcc/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release
Thread-Modell: posix
gcc-Version 6.1.1 20160707 (GCC)

λ philipp [Dokumente/github/NodeOS] at  master ✔
→ npm -v                                                                                [6aede62]
3.10.3

λ philipp [Dokumente/github/NodeOS] at  master ✔
→ node -v                                                                                [6aede62]
v6.5.0

Was that a new tree - a fresh clone from the git repo and then npm install?

@d3x0r, can you be able to download a fresh install and try again?

Yes, after hearing that news, I did.
unforutnatly
npm install fails on genext2fs
configure.in:10: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.  For more info, see:
configure.in:10: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.in:13: installing './compile'
configure.in:10: installing './install-sh'
configure.in:10: installing './missing'
Makefile.am: error: required file './README' not found
Makefile.am: installing './depcomp'
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
parallel-tests: installing './test-driver'
*** automake failed :(

and genext2fs hasn't changed in 9 years....

Can you provide the full error output? That doesn't makes sense...
El 12/9/2016 19:37, "d3x0r" notifications@github.com escribió:

Yes, after hearing that news, I did.
unforutnatly
npm install fails on genext2fs
configure.in:10: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.  For more info, see:configure.in:10: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocationconfigure.in:13: installing './compile'configure.in:10: installing './install-sh'configure.in:10: installing './missing'
Makefile.am: error: required file './README' not found
Makefile.am: installing './depcomp'
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
parallel-tests: installing './test-driver'
*** automake failed :(
and genext2fs hasn't changed in 9 years....
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/248#issuecomment-246428091, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvtwZPL5matwZekxeCj1u35a-7GqCks5qpY3dgaJpZM4IxQNv
.

And unfortunatly when it fails, it evaporates so I can't go poke at it...
err.txt
The end of that says I should have info in npm-debug.log but I don't see one of those.

found npm-debug.log and attached it to last message

It's strange that it doesn't download a prebuild image of genext2fs, but more strange that that autoconf failed. Try to download genext2fs and compile it locally with npm install on your machine, to see where's the problem.

I did start a new project and just did npm install genext2fs, and it fails to build
Makefile.am automagically requires README....
http://stackoverflow.com/questions/15013672/use-autotools-with-readme-md
Which there's options to work around.
After it had installed everything in test/node_modules/genext2fx  I had gone into that directory and did a 'touch README' and it finished.
The other version I had modified the Makefile.am to have 'AUTOMAKE_OPTIONS = foreign'  and that also built successfully.
Both of those modifications are outside the scope of this project unfortunately :)
autoconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.

	autoconf-2.69.tar.gz	2012-04-24 23:17	1.8M

And autoconf hasn't changed in 5 years... so I don't know how it has built on anyone elses system?  Unless there was a canned binary?

@d3x0r im also using autoconf 2.69

automake is the thing that's actually thowing the README error

@d3x0r automake is also 1.15 i really dont know why it throws this error on your system

I don't know too, i have revised it and the README file is already on the
Github repo... Could you be able to exec 'npm install genext2fs
--no-scripts' and tell us if it's available there?
El 13/9/2016 19:23, "Philipp Czarnetzki" notifications@github.com
escribió:

@d3x0r https://github.com/d3x0r automake is also 1.15 i really dont
know why it throws this error on your system
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/248#issuecomment-246756973, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvkXBp15s9CS1b0wDk2pLVt7o5zFdks5qptwEgaJpZM4IxQNv
.

Still fails...
tracked down the npm package.jon for genext2fs...
 cat ~/.npm/genext2fs/1.4.1-0/package/package.json
{"name":"genext2fs","version":"1.4.1-0","description":"ext2 filesystem generator for embedded systems","bin":{"genext2fs":"genext2fs"},"main":"index.js","scripts":{"BigRedButton":"scripts/BigRedButton","build":"scripts/build","install":"prebuild-install -d https://github.com/NodeOS/genext2fs/releases/download/v{version}/{platform}-{arch}.tar.gz || npm run build","start":"./genext2fs","test":"./test.sh"},"repository":{"type":"git","url":"git+https://github.com/NodeOS/genext2fs.git"},"keywords":["ext2","ext3","ext4","filesystem","image"],"author":{"name":"Xavier Bestel","email":"xavier.bestel@free.fr"},"license":"GPL-2.0","bugs":{"url":"https://github.com/NodeOS/genext2fs/issues"},"homepage":"https://github.com/NodeOS/genext2fs#readme","dependencies":{"prebuild-install":"1.0.2"},"devDependencies":{"prebuild":"^4.2.2"},"contributors":[{"name":"Xavier Bestel","email":"xavier.bestel@free.fr"}],"gitHead":"c9a96b7a34cecdb81ace5e51e417b51a0a740275","_id":"genext2fs@1.4.1-0","_shasum":"bd002532151538adfdc29995cd83e281b2c3887b","_from":"genext2fs@latest","_npmVersion":"3.9.3","_nodeVersion":"6.2.1","_npmUser":{"name":"piranna","email":"piranna@gmail.com"},"dist":{"shasum":"bd002532151538adfdc29995cd83e281b2c3887b","tarball":"https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz"},"maintainers":[{"name":"piranna","email":"piranna@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/genext2fs-1.4.1-0.tgz_1466686621501_0.9280801126733422"},"directories":{},"_resolved":"https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz","readme":"ERROR: No README data found!"}

"tarball":"https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz"
That tarball does not have README.
[root@tower2 makeextfs]# wget https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz
--2016-09-14 10:39:47--  https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz
Resolving registry.npmjs.org (registry.npmjs.org)... 151.101.40.162
Connecting to registry.npmjs.org (registry.npmjs.org)|151.101.40.162|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 93170 (91K) [application/octet-stream]
Saving to: ‘genext2fs-1.4.1-0.tgz’

genext2fs-1.4.1-0.tgz            100%[=======================================================>]  90.99K  --.-KB/s    in 0.07s

2016-09-14 10:39:47 (1.34 MB/s) - ‘genext2fs-1.4.1-0.tgz’ saved [93170/93170]

[root@tower2 makeextfs]# ls
genext2fs-1.4.1-0.tgz  nm  node_modules  npm-debug.log
[root@tower2 makeextfs]# tar -zxf genext2fs-1.4.1-0.tgz
[root@tower2 makeextfs]# ls
genext2fs-1.4.1-0.tgz  nm  node_modules  npm-debug.log  package
[root@tower2 makeextfs]# cd package/
[root@tower2 package]# ls
AUTHORS     clean.sh      debian            genext2fs.8  INSTALL      NEWS          scripts        test.sh
autogen.sh  configure.in  device_table.txt  genext2fs.c  m4           package.json  test-gen.lib   TODO
ChangeLog   COPYING       genext2fs         index.js     Makefile.am  README.md     test-mount.sh
[root@tower2 package]#

So it seems that would be the reason... since it was working correctly with
prebuild, probably I didn't paid more atention to that.
El 14/9/2016 19:42, "d3x0r" notifications@github.com escribió:

Still fails...
tracked down the npm package.jon for genext2fs...
cat ~/.npm/genext2fs/1.4.1-0/package/package.json
{"name":"genext2fs","version":"1.4.1-0","description":"ext2 filesystem generator for embedded systems","bin":{"genext2fs":"genext2fs"},"main":"index.js","scripts":{"BigRedButton":"scripts/BigRedButton","build":"scripts/build","install":"prebuild-install -d https://github.com/NodeOS/genext2fs/releases/download/v{version}/{platform}-{arch}.tar.gz || npm run build","start":"./genext2fs","test":"./test.sh"},"repository":{"type":"git","url":"git+https://github.com/NodeOS/genext2fs.git"},"keywords":["ext2","ext3","ext4","filesystem","image"],"author":{"name":"Xavier Bestel","email":"xavier.bestel@free.fr"},"license":"GPL-2.0","bugs":{"url":"https://github.com/NodeOS/genext2fs/issues"},"homepage":"https://github.com/NodeOS/genext2fs#readme","dependencies":{"prebuild-install":"1.0.2"},"devDependencies":{"prebuild":"^4.2.2"},"contributors":[{"name":"Xavier Bestel","email":"xavier.bestel@free.fr"}],"gitHead":"c9a96b7a34cecdb81ace5e51e417b51a0a740275","_id":"genext2fs@1.4.1-0","_shasum":"bd002532151538adfdc29995cd83e281b2c3887b","_from":"genext2fs@latest","_npmVersion":"3.9.3","_nodeVersion":"6.2.1","_npmUser":{"name":"piranna","email":"piranna@gmail.com"},"dist":{"shasum":"bd002532151538adfdc29995cd83e281b2c3887b","tarball":"https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz"},"maintainers":[{"name":"piranna","email":"piranna@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/genext2fs-1.4.1-0.tgz_1466686621501_0.9280801126733422"},"directories":{},"_resolved":"https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz","readme":"ERROR: No README data found!"}
"tarball":"https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz"
That tarball does not have README.
[root@tower2 makeextfs]# wget https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz
--2016-09-14 https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz--2016-09-14 10:39:47--  https://registry.npmjs.org/genext2fs/-/genext2fs-1.4.1-0.tgz
Resolving registry.npmjs.org (registry.npmjs.org)... 151.101.40.162
Connecting to registry.npmjs.org (registry.npmjs.org)|151.101.40.162|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 93170 (91K) [application/octet-stream]
Saving to: ‘genext2fs-1.4.1-0.tgz’
genext2fs-1.4.1-0.tgz            100%[=======================================================>]  90.99K  --.-KB/s    in 0.07s
2016-09-14 10:39:47 (1.34 MB/s) - ‘genext2fs-1.4.1-0.tgz’ saved [93170/93170]
[root@tower2 makeextfs]# ls
genext2fs-1.4.1-0.tgz  nm  node_modules  npm-debug.log
[root@tower2 makeextfs]# tar -zxf genext2fs-1.4.1-0.tgz
[root@tower2 makeextfs]# ls
genext2fs-1.4.1-0.tgz  nm  node_modules  npm-debug.log  package
[root@tower2 makeextfs]# cd package/
[root@tower2 package]# ls
AUTHORS     clean.sh      debian            genext2fs.8  INSTALL      NEWS          scripts        test.sh
autogen.sh configure.in  device_table.txt  genext2fs.c  m4           package.json  test-gen.lib   TODO
ChangeLog   COPYING       genext2fs         index.js     Makefile.am README.md test-mount.sh
[root@tower2 package]#
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/248#issuecomment-247095894, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvpoJuacL1JBGT0b-RTgQFI9Z3zNfks5qqDIXgaJpZM4IxQNv
.

@d3x0r do you still have these errors from 2 years ago? I've just reinstalled Arch and it works like a charm just like before.

Haven't tried in a bit...

Would be good to know because we have some dead issues that are already resolved

Finally got back around to checking... did a
#git pull
#npm install .
#npm run build

Success!
You just built a custom NodeOS image

#npm start
(#pacman -S libcurl-gnutls)
#npm start  # ... and get an X window from qemu :)

works for me :)

repo: NodeOS/NodeOS


text:
Face-lift the node-os.com website?

Hi! We have a lot of front-end developers lurking around NodeOS and as nice as the website is, it could certainly be more polished and more responsive.
I'm suggesting we give the website a nice face-lift and polish it off as we welcome people to our shiny 1.0.0-RC2 release! If needed, I'd love to lead the creation of the new page, and involve all our talented front-end designers that I know sit around here lurking waiting for the renderer noGUI to be ready (on which @coretool has been making some excellent progress! Kudos to you man!)
Interested to hear what you guys have to say!

I was going to assign it to you, but I've seen you have done it already :-P

Yay! Okay, is the website hosted on github pages?

Yay! Okay, is the website hosted on github pages?

Yep :-)

Okie dokie! I'll get to work then! Time to awake those slumbering front-end dev's

@piranna can I would tag it as a blog post but I'd like people to see the RC2 post, so we can tag the website thread tomorrow?

@piranna can I would tag it as a blog post but I'd like people to see the RC2 post, so we can tag the website thread tomorrow?

Yes, let's wait some days.


text:
Approvals List error with Rejected Reviews/Approvals

Badge Approvals or Reviews that have been rejected by Unit Council, don't save the 'Presented' date to clear them from the pending approvals list.
Would it be possible to have a checkbox that is enabled by default that hides badges listed as Rejected?

@wilsteady
Nice idea,
Will see what I can do.

Fixed in v1.42
Added Show Rejected checkbox

authors: NomisNostab wilsteady

repo: NomisNostab/Topo-Blazor


text:
Optimize parser by using nested parser state

When parsing a nested array in chunks efficiently, the parser state
(continuation data) needs to be a nested structure. The parser is
restructured.
Fixes https://github.com/wooga/eredis/issues/127

LGTM, how is the cprof runs as in wooga#127 (comment) turning out with this change?

Erlang/OTP 23 [erts-11.1.8] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1]

Eshell V11.1.8  (abort with ^G)
1> {ok, E} = eredis:start_link().
{ok,<0.233.0>}
2> eredis:q(E,["FLUSHDB"]).
{ok,<<"OK">>}
3> A = binary:copy(<<"a">>, 10000000).
<<"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"...>>
4> eredis:q(E,["HSET", "h", "1", A]).
{ok,<<"1">>}
5> cprof:start(), R=eredis:q(E, ["HGETALL", "h"], 100000), cprof:pause(),R.
{ok,[<<"1">>,
     <<"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"...>>]}
6> cprof:analyse(eredis_parser).
{eredis_parser,20571,
               [{{eredis_parser,do_parse,2},6860},
                {{eredis_parser,return,2},6854},
                {{eredis_parser,parse,2},6854},
                {{eredis_parser,split_by_newline,2},3}]}
7> cprof:stop().
15886
8> timer:tc(fun() -> eredis:q(E, ["HGETALL", "h"], 100000) end).
{21970,
 {ok,[<<"1">>,
      <<"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"...>>]}}
9> timer:tc(fun() -> eredis:q(E, ["HGET", "h", "1"]) end).
{20421,
 {ok,<<"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"...>>}}

Compared to wooga/eredis, there are fewer function calls and is faster also for the fast example. Tests done on my laptop. Times in microseconds.

Command
wooga/eredis
This PR

HGET h 1
25117
20421

HGETALL h
9429598
21970

repo: Nordix/eredis


text:
DO NOT MERGE - Instructive only

Integration tests fixes
@sainap Helpfully pointed out that I'd left these in a bad state.  Here are some fixes to get it going.
@sainap @Sullux I know that you are both taking these on to productionize.  Thank you!  These are offered simply for the purpose of addressing that they were left in a bad state and in apology for that.

Thanks for looking into this.

opened to update the commit set, closing again to avoid review

authors: erikerikson sainap

repo: Nordstrom/serverless-artillery

license_source: bigquery


text:
Questions to add on env/social justice

Add to step 1: Have you shared your design priorities with your supply chain?
In order to meet your goals, your supply chain may need to make changes as well.
Add to step 1: What is your plan for transparent communication about your product and materials?
For step 1, make a section on stakeholder communication?
Add to step 3: Will the materials and manufacturing related to your product create equal opportunities and fair labor conditions (such as fair salary/wage, safe working conditions, freedom of association and collective bargaining)?
Add to steps 3-5: Have you considered impacts to the community where your product will be made, used and/or disposed?
How will your product contribute to or hinder local economic development in the areas it is produced, used and disposed?

Have you considered impacts to the community where your product will be made, used and/or disposed? - already covered in other Qs in step 3.
All others added.

repo: NorthwestGreenChemistry/PrISM


text:
Very minor update to readme - it referenced that .NET Core SDK 2.1 wa…

…s a pre-requisite when the project has already been updated to 3.1 - corrected accordingly ;) - fixes #101

Thanks! Fixes #102
@all-contributors please add @cmjchrisjones  for doc

authors: NotMyself cmjchrisjones

repo: NotMyself/DotNetCoreKoans

license: mit


text:
Separated Catppuccin themes

Catppuccin has 4 separate themes so I separated them
I also made the theme buttons not go past 75% of the screen :+1:

Awesome work! Thank you!

authors: NotNeelPatel ketexon

repo: NotNeelPatel/WallpaperThemeConverter


text:
Obay the Law in the space

In conjunction with removing the "Abiding by UK Law" Rule I think this is better covered by an example within this rule that says obaying the law in the space is part of respecting the space.

I suggest that this pull request is merged with PR 16, since they are effectivey the same proposal. https://github.com/NottingHack/rules/pull/16
Chris, are you capable of the relevant git magic?

Merged into Delete entire rule "Abiding by UK Law"

repo: NottingHack/rules


text:
Several iOS improvements

Dramatic performance improvements (~960ms to ~30ms); also submitted as #23.
Load model once.
Update output as generation takes place.
Report ms/token when done.

@NouamaneTazi you can merge it if you want, and we can work on model download in a new PR, if necessary.


text:
@javax.ejb.Singleton annotated Beans are not injected as EJBs

Hi,
i am testing BeanTest with my project and the project fails to inject an EJB that is annotated. with @Singleton
e.g.
@Startup @Singleton
public class CacheManagerBean {
}
I guess the BeanTestExtension class needs to be extended to check for the @Singleton annotation as well (not only for Stateless and MessageDriven).

Yes, that should do it. Care to create a pull request? The corresponding scope would be @ApplicationScoped

The implementation of this feature won't support multi-threading access because the TransactionalInterceptor is not thread-safe. That should be done in a another issue / feature request.
The implementation will just provide access to Singletn (with @ApplicationScoped) via the getBean() method.

authors: andywuest carlosbarragan

repo: NovaTecConsulting/BeanTest


text:
"Contact owners" link should not appear on a package details page when there are no owners

Describe the bug
A package details page for a package without any owners still shows the "Contact owners" link on the right. It is unclear what will happen when the message is sent.
To Reproduce
Steps to reproduce the behavior:

Find a package with no owners (example)
Look at its package details page
See the "Contact owners" link on the right

Expected behavior
No "Contact owners" link.
Screenshots

When you click the "Contact owners" link you get a very clear notification:

I think this experience is much clearer then hiding the button.

repo: NuGet/NuGetGallery


text:
Installation instructions for NUKE

Hi everyone! I'm basically following up on another recent proposal to extend the installation instruction tabs.
Proposal
NUKE provides a nuke :add-package <package-id> [package-version] command via our global tool, which allows installing packages to the build project. The command works from any directory of a repository built with NUKE, thus covering more situations compared to the conventional dotnet add command. More importantly, though, it automatically determines how a package should be installed, which is either as PackageReference (regular libraries) or PackageDownload (tool packages). The latter is a great feature (thanks once more @nkolev92), because it allows a build to reference tools without messing with references (implicit ExcludeAssets), and works with tools in different versions (PackageReference wouldn't allow that even with ExcludeAssets).
We would like to display this command as installation instructions under a separate "NUKE" tab. Today, users naturally use PackageReference instead of PackageDownload, which often completely breaks the compilation of the build project, and overall is a sub-optimal approach.
Listing Criteria
Regarding if we meet the criteria, here are my comments:

Signification adoption in .NET community: currently at 1.4M total downloads and around 1k downloads per day for the main package
Actively maintained and updated: the project is continuously maintained for the last 4 years (since its creation), and as mentioned below used by a wide range of companies and projects
Security compliance: We have repeatable builds. Publish signed packages. Have a package prefix reservation. And 2FA for NuGet.org!

Background
NUKE is a build automation system, which is created with the idea to integrate with other .NET tools natively. That means it uses regular C# projects for the build implementation and thus comes with IDE integration out-of-the-box, including navigation, refactoring, and debugging. It is well adopted with almost 1k downloads per day, and many companies and projects are actively using or transitioning to it (e.g. OctopusDeploy, JetBrains, AvaloniaUI, ASP.NET Boilerplate, CsvHelper, FluentAssertions, HotChocolate).

We and our users would really appreciate if this proposal would be accepted! 🙏

Visual proposal
Here is an example of how that could look like

Hey everyone,
First off, thanks so much for writing a proposal to add the NUKE DSL instructions to NuGet.org! From an initial review, we believe that NUKE meets majority of the requirements set via https://github.com/NuGet/NuGetGallery/issues/4510#issuecomment-324422213. There is one requirement that we aren't too sure of given the unfamiliarity of NUKE, and that's the presence of a User Agent in the client tooling to understand package download usage from NUKE compared to other client tooling. We are hopeful that it's possible to add a custom NUKE user agent to the NuGet APIs you're using such as:

UserAgent.CreateUserAgentString()
UserAgent.SetUserAgentString()

Examples: https://github.com/NuGet/NuGet.Client/search?q=useragent
(We can help further if there's good places to hook into)
This would help us understand what client is downloading a package & would help in the long-term with the ecosystem being more data-driven! You can see this example of what I mean by that:
https://www.nuget.org/stats/packages/Microsoft.EntityFrameworkCore?groupby=Version&groupby=ClientName
Additionally we look at the usage of the tooling in various .NET projects. I think that is mostly covered by your proposal with an expanded list here: https://github.com/nuke-build/nuke#users.
We'd ask that before we can approve a contribution from the NUKE project to add these instructions, that a custom user agent is added to the tooling. Once that is completed(if it's feasible), we can move forward with a contribution to add the instructions & merge when initial data comes in.
In the meantime, we are also encouraging the use of our new proposal process. This helps us go through the rounds of the various considerations made & gives people in the community an opportunity to bring up questions & feedback prior to it being accepted. If there's time to create a quick proposal & send a PR to nuget/home, that would be wonderful.
In short:

Significant adoption in .NET community ✔⚠(Addition of user agent for long-term ecosystem data)
Actively maintained and updated ✔
Security compliance ✔

Action Items for NUKE project maintainers 📋:

Investigate the inclusion of custom user agent into NUKE tooling to report the NUKE client in package statistics.
Creation of a NuGet proposal to provide the community a place to discuss & be accepted if no major objections/considerations.
Consideration for NUKE tab instruction contribution for NuGet packages & .NET tools (If applicable) - See: https://github.com/NuGet/NuGetGallery/pull/8434 & https://github.com/NuGet/NuGetGallery/pull/8440 for recent examples.

If this all sounds reasonable, then we'll review the proposal in the next couple weeks while awaiting the investigation of the user agent inclusion. Please let me know if there are any questions, comments, or feedback to these initial considerations. We're trying to make these considerations as transparent as possible & still have a ways to formally document them.
Note: We're trying our best to not change any requirements, but rather to improve our processes. As you may imagine, the requirements list in 2017 still reflects the considerations, but we want to ensure the long-term success by being data-driven and learning from recent contributions as well.

@JonDouglas generally speaking NUKE doesn't act as a dedicated NuGet client. It fully operates on either dotnet CLI or the Microsoft.Build package, which makes it transparent, up-to-date, and most of all integrated with all the developer tools that exist. If you need a user agent, it probably could be added in some way, but I'm gonna say it would be rather artificial:

At design-time, a build author can add a package with the mentioned command nuke :add-package <package-id>. This simply adds the PackageReference item to the csproj file using Microsoft.Build infrastructure, and then performs a dotnet restore on the build project which triggers the download to the global NuGet cache. It is only converted to PackageDownload if the package contains a ./tools directory. Providing a user-agent would require replacing the dotnet CLI call, which implies more maintenance, but – yes – doable.
At build-time, the build project is restored and built with dotnet build. I'm afraid requiring a user-agent at this moment could imply breaking the minimal bootstrapping mechanism of NUKE, which is particularly something that users have benefited from because it is resilient to any upstream changes and hence less fragile. It could be possible by making a second roundtrip to NuGet.org, but I guess it's not in the interest of anyone to download packages twice.

Is it possible by any chance to set a different user-agent from outside? For instance with an MSBuild property /p:NuGetUserAgent=.. or as an environment variable NUGET_USER_AGENT ? From a quick glance there is no such thing, but maybe it could be added? A similar approach already exists with NUGET_PACKAGES for instance.
I hope it's clear that this proposal is laid out for more efficient and correct package consumption, and I'd appreciate it if we can find a solution to this without degrading the existing native integration with .NET tools.

Thanks for the quick response!
We figured that might be the situation, but wanted to bring it up for feasibility & consideration. To my knowledge, no such property or ENV variable exists but could be something we break-off separate to this proposal to be considered for the future to not disrupt the native integration while also reporting the client use.
Let's move forward with the other action items to keep the momentum.
Thanks!

Just to clarify, the only other action you need me to approach is to create the proposal according to the new process ?

@matkoch Yes that's correct. The contribution PR can wait until the proposal PR is reviewed & accepted by the community & NuGet.

I think we can close this. Follow-up is linked above.

reopening as per this comment: https://github.com/NuGet/Home/issues/10784#issuecomment-824239843

@zivkan sorry i did not know :) should i update my original post maybe to only link the new spec?

@matkoch, this change is now live on PROD. Thanks again for your hard work here!

@joelverhagen wasn't hard actually :) Thanks for your assistance!

authors: JonDouglas joelverhagen matkoch totollygeek zivkan


text:
[UI] Add new themes for Alert component

Adding the new themes to the alert component, this PR only changes CSS files, actual usage of the component will be in future PR's.
Light theme
Danger

Warning

Success

Info

Dark theme
Danger

Warning

Success

Info

Addresses https://github.com/NuGet/NuGetGallery/issues/9862

@martinrrm Warning should be yellow (bright or dim depending on the base theme) and not orange-ish! It'll be difficult to see at a glance. When I glanced at this page, I thought both colors were the same. And no, I do not have any issues with recognising colors.

@Nirmal4G Hi! Thanks for your feedback, right now we are trying to stick with Fluent UI color tokens, nevertheless I agree with you, specially in the Light Theme is hard to distinguish the difference. This is another option we can use.
Also, I loved your idea for the info to be Info color, let me double check that with the designers/team
This is a possible alternative for the colors.

How about this one for the warning? GitHub uses it.

Dark Theme Warning Color
Light Theme Warning Color

@Nirmal4G Let me check with designers, I don't think we should be using colors from other products given that there is a well-documented color theme for the components we are using.

@martinrrm Yeah. That's just for visual reference. Adjust the color to match NuGet branding. It would not be far off, IMO.


text:
Is there a way to create NUPKG files without using Microsoft.NET.Sdk?

I'd like to know if it's possible to create a CSPROJ file which outputs a .nupkg file, but doesn't use the Microsoft.NET.Sdk project type.  In my case, I'd like to create a nupkg but there's no code to compile.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 31da7408-981b-cc54-1791-ca39dbdbc091
Version Independent ID: 2060c9e8-7f2e-5da1-ee19-d196f38339fe
Content: Create a NuGet package using MSBuild
Content Source: docs/create-packages/creating-a-package-msbuild.md
Product: nuget
GitHub Login: @JonDouglas
Microsoft Alias: jodou

Related: https://github.com/NuGet/Home/issues/4254
At the moment, this scenario would be limited until the above is addressed. Thus I'm going to close this for now.

authors: JonDouglas mike-christensen


text:
[WIP] Abstract workings so that we can add other client(such as AzureDevOps)

First of all, i love the idea of NuKeeper and i feel very excited about it! This is my attempt to make the solution more generic so that we can easily add new client such as AzureDevOps or bitbucket.
The proposed solution structure will look like this:

NuKeeper(Contains the command and the DI for registering the different clients)
NuKeeper.Abstract (Contains the abstractionlayer for the Engine, the Configuration and some other shared code)
NuKeeper.Github(Contains github implementation)
NuKeeper.AzureDevOps(Contains AzureDevOps implementation)
And the rest of the already existing parts

To let code function the same way for differenct clients i've extracted interfaces and used Githubs Octokit as a reference. I've used sharedcode where i can and made an implementation for Github specifically. So far everything builds but it doesn't work yet. I'm still working on getting the Github functionality back and would like to advance from there on to add AzureDevops.
The progress of this PR is:

[x] Successful build with new project styles and abstraction layer
[ ] Verify that all the same functionality that the package now has still works
[ ] Update tests

This is WIP, please let me know what you think!

This is related to #336
I haven't had time to look at this yet, I am away from home this weekend. Will do so when  can.
But it is in general a good idea to go in this direction of abstracting out github and generalising to other systems, hopefully in small steps.

So, a general design comment around things in NuKeeper.Abstract such as interface IPullRequest and class GithubBranch : Branch, IBranch
We're going to have to get this working well, and the plan (here)[https://github.com/NuKeeperDotNet/NuKeeper/issues/336#issuecomment-416992498] was to instead use Nukeeper's own types that "have only the few fields that we need".
We are aware that the Octokit types are not ideal to use inside NuKeeper - the biggest symptom of that is tests where creating an Ocotkit object requires over 30 args to the constructor (!).  At some stage this might be changed to use github's graphQL API, and retrieve "only the few fields that we need".
But it seems odd to me to use Interfaces and inheritance to solve this issue. Ideally I'd like to see all backends work on a common set of internal DTOs, that don't need interfaces or base classes. This does depend of the functionality being more or less equivalent so that common data types make sense.

Big PRs with lots of changes and also merge conflicts are my least favourite kind :(
There must be ways to slice this up into things that can be merged today, e.g. introduce just the "abstractions" project. Or just the "github" project.
I am happy with a PR that doesn't make a visible difference in itself; I think we have reasonable idea of where you are going.

I would like to close this so that we can keep PR's smaller as @AnthonySteele mentions. That doesn't mean that i'm throwing away the progress that's been made. This PR can be kept as a reference towards a more abstract solution which enables more clients. I'll raise a issue with steps that i see so we can make a list of small PR's towards a good solution.

authors: AnthonySteele MarcBruins

repo: NuKeeperDotNet/NuKeeper


text:
Throw exception for missing dependencies

:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
feature
:arrow_heading_down: What is the current behavior?
Missing packages are silently ignored when inspecting:
$ nuget inspect
Found 61 packages
Found 61 packages in use, 14 distinct, in 16 projects.
coverlet.msbuild, LibGit2Sharp, McMaster.Extensions.CommandLineUtils, Microsoft.CodeAnalysis.FxCopAnalyzers, Microsoft.NET.Test.Sdk, Newtonsoft.Json, NSubstitute, NuGet.CommandLine, NuGet.Protocol, NUnit, NUnit3TestAdapter, Octokit, SimpleInjector, System.Text.Encoding.CodePages
Found 0 possible updates
Found no package updates

C:\Program Files\dotnet\dotnet.exe (process 14792) exited with code 0.

:new: What is the new behavior (if this is a feature change)?
An error is returned if there were missing packages during inspection.
$ nuget inspect
Found 61 packages
Found 61 packages in use, 14 distinct, in 16 projects.
coverlet.msbuild, LibGit2Sharp, McMaster.Extensions.CommandLineUtils, Microsoft.CodeAnalysis.FxCopAnalyzers, Microsoft.NET.Test.Sdk, Newtonsoft.Json, NSubstitute, NuGet.CommandLine, NuGet.Protocol, NUnit, NUnit3TestAdapter, Octokit, SimpleInjector, System.Text.Encoding.CodePages
Could not find package coverlet.msbuild.2.7.0 in these sources: file:///C:/Program Files (x86)/Microsoft SDKs/NuGetPackages/, https://dotnet.myget.org/F/roslyn/api/v3/index.json

C:\Program Files\dotnet\dotnet.exe (process 17888) exited with code -1.

:boom: Does this PR introduce a breaking change?
Yes / no. inspect would silently ignore the problem. However update would fail, as a Nuget restore would also fail for missing packages. I think this is desirable, as inspect should handle situations where packages are missing.
:bug: Recommendations for testing
Add a non-existing package reference.
:memo: Links to relevant issues/docs
:thinking: Checklist before submitting

[ ] All projects build
[ ] Relevant documentation was updated

This fails some tests, due to the change in behaviour. I can change the tests to the new behaviour, but first wanted to know if you'd be willing to take this change?

Why auto-close the PR?

This a a good change, can you rebase please?

I wonder if we want to log all of the missing / unreachable packages.

I can rebase the PR. Anything else that you want me to look into?

Why auto-close the PR?

Ping @MarcBruins @AnthonySteele

Sorry but can you rebase again? After that i'll  merge it in

Sorry but can you rebase again? After that i'll  merge it in

Happy to oblige! I've rebased the project and updated the relevant tests.

Please go over the tests as I've updated them to match the expected behaviour (throwing an error for missing packages instead of silently ignoring the package).
There's a test that keeps failing: ShouldFilterOutNonDotnetRepository. I'm not sure how my PR is affecting that test, please advice.
Finally there's the Windows build that fails to build. I don't think my changes are related to that build failure, please advice.

Happy to oblige! I've rebased the project and updated the relevant tests.

Please go over the tests as I've updated them to match the expected behaviour (throwing an error for missing packages instead of silently ignoring the package).
There's a test that keeps failing: ShouldFilterOutNonDotnetRepository. I'm not sure how my PR is affecting that test, please advice.
Finally there's the Windows build that fails to build. I don't think my changes are related to that build failure, please advice.

@MarcBruins can you give some pointers?

@MarcBruins can you give some pointers?

Still waiting for feedback…

Still waiting for feedback…

@Bouke can you please rebase the branch on the latest master?

@msallin sure, I just did.

@skolima fine with this? Then I will merge it.

@msallin I'm offline for the night, I'll have a look tomorrow, if that's ok. I have free time tomorrow.

@msallin I'm offline for the night, I'll have a look tomorrow, if that's ok. I have free time tomorrow.

Sure! Enjoy!

I'm only concerned how this interacts with #311 and #466 . NuKeeper should currently skip unversioned packages (yes, I know those went away now, but the tag without a version is still valid, even if unwise) and should skip packages with ranges specified (also not a particularly good idea when using any automated dependency upgrader, but hey). I realise both of those are quite niche corner cases, but I'm still not keen on breaking them. I haven't re-tested those interactions yet.

@skolima Are there any unit tests covering those cases?
Conceptually I expect a missing package to be something different from an unversioned package. So we should be able to tell the two apart and only throw in the first case.

@skolima Is my contribution in vain?

authors: AnthonySteele Bouke MarcBruins msallin skolima


text:
Missing data files for apkutils

Adding apkutils to my project results in a non-functioning onefile build.
Nuitka installed with poetry, using version 1.6.3.
poetry show nuitka:
 name         : nuitka
 version      : 1.6.3
 description  : Python compiler with full language support and CPython compatibility

dependencies
 - ordered-set >=4.1.

poetry env info:
 Virtualenv
Python:         3.11.1
Implementation: CPython
Path:           C:\Users\XXX\AppData\Local\pypoetry\Cache\virtualenvs\XXX-py3.11
Executable:     C:\Users\XXX\AppData\Local\pypoetry\Cache\virtualenvs\XXX-py3.11\Scripts\python.exe
Valid:          True

System
Platform:   win32
OS:         nt
Python:     3.11.1
Path:       C:\python311
Executable: C:\python311\python.exe

Non-working dependency list:
[tool.poetry.dependencies]
python = "^3.10"
pymemuc = "^0.4.2"
wmi = { version = "^1.5.1", markers = "sys_platform == 'win32'" }
numpy = "^1.24.3"
pillow = "^9.5.0"
requests = "^2.31.0"
nltk = "^3.8.1"
pysimplegui = "^4.60.5"
psutil = "^5.9.5"
apkutils = "^1.5.0"

Working dependency list:
[tool.poetry.dependencies]
python = "^3.10"
pymemuc = "^0.4.2"
wmi = { version = "^1.5.1", markers = "sys_platform == 'win32'" }
numpy = "^1.24.3"
pillow = "^9.5.0"
requests = "^2.31.0"
nltk = "^3.8.1"
pysimplegui = "^4.60.5"
psutil = "^5.9.5"

apkutils depends on:
[tool.poetry.dependencies]
Pygments = "^2.12.0"
beautifulsoup4 = "^4.10.0"
click = "^8.0.3"
cryptography = "^35.0.0"
lxml = "^4.6.4"
pyelftools = "^0.27"
pyftype = "^1.2.4"
python = ">=3.8"
colorlog = "^6.7.0"

This is the script I use to build my onefile:
[tool.poe.tasks.build-dist]
shell = """
poetry run nuitka src/main.py \
  --onefile \
  --enable-plugin=tk-inter \
  --enable-plugin=pylint-warnings \
  --disable-console \
  --windows-uac-admin \
  --prefer-source-code \
  --assume-yes-for-downloads \
  --report=build\\report-$Env:tagname.xml \
  --output-dir=build \
  --output-filename=XXX-$Env:tagname
"""
interpreter = "pwsh"

Here's a gist with build reports from with and without apkutils

caused by a missing XML in the package:
Traceback (most recent call last):
  ...
  File "C:\XXX\AppData\Local\Temp\ON8510~1\apkutils\__init__.py", line 1, in <module apkutils>
  File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "C:\XXX\AppData\Local\Temp\ON8510~1\apkutils\apk.py", line 14, in <module apkutils.apk>
  File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "C:\XXX\AppData\Local\Temp\ON8510~1\apkutils\axml\__init__.py", line 12, in <module apkutils.axml>
  File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "C:\XXX\AppData\Local\Temp\ON8510~1\apkutils\axml\public.py", line 22, in <module apkutils.axml.public>
Exception: need to copy the sdk/platforms/android-?/data/res/values/public.xml here

Fixed with a custom package config
- module-name: "apkutils.axml"
  data-files:
    patterns:
      - "public.xml"

This also happens with two other very similar packages, pyaxmlparser and androguard, both with the same missing XML file.

Very glad you made it, I will be on the road today and merge later today or tomorrow, for inclusion in the next hotfix.

Part of the 1.6.4 hotfix release I just made.

authors: kayhayen martinmiglio

repo: Nuitka/Nuitka


text:
[PySide6] Can't initialize module QtWebChannel when using UPX

Reproduce code:
import sys

from PySide6.QtCore import QUrl
from PySide6.QtWebEngineWidgets import QWebEngineView
from PySide6.QtWidgets import QApplication

if __name__ == "__main__":
    app = QApplication(sys.argv)
    view = QWebEngineView()
    view.load(QUrl("https://www.bing.com"))
    view.show()
    sys.exit(app.exec())

When using UPX, the packaged program does not run:
nuitka --standalone --mingw64 --plugin-enable=pyside6,upx --output-dir=dist --upx-binary=D:/Program/upx-4.0.2-win64 browser.py

Normal packing can work. UPX works and packages PySide6 without PySide6.QtWebEngineWidgets:
nuitka --standalone --mingw64 --plugin-enable=pyside6 --output-dir=dist browser.py
# no error

I can't confirm if it's a UPX issue or a PySide6 packaging plugin issue:
SystemError: PyModule_AddObjectRef() must be called with an exception raised if value is NULL
Fatal Python error: can't initialize module QtWebChannel
Python runtime state: initialized

Current thread 0x00006db0 (most recent call first):
  File "<frozen importlib._bootstrap>", line 688 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1006 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1027 in _find_and_load
  File "<frozen importlib._bootstrap>", line 688 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1006 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1027 in _find_and_load
  File "<frozen importlib._bootstrap>", line 688 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1006 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1027 in _find_and_load

Extension modules: xxsubtype, shiboken6.Shiboken, PySide6.QtCore, PySide6.QtGui, PySide6.QtWidgets, PySide6.QtNetwork, PySide6.QtPrintSupport (total: 7)

PS:
OS: Windows 11

PySide6                        6.5.1.1
PySide6-Addons                 6.5.1.1
PySide6-Essentials             6.5.1.1

Nuitka 1.7.5
Commercial: None
Python: 3.10.10 (tags/v3.10.10:aad5f6a, Feb  7 2023, 17:20:36) [MSC v.1929 64 bit (AMD64)]
Flavor: CPython Official
Executable: D:\Program\Python3.10\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
Version C compiler: C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\bin\Hostx64\x64\cl.exe (cl 14.3).

For onefile, we do not compress it with upx I think. For standalone it would make sense. The way to find out if this is an UPX issue, you compress it manually in your Python installation, and if it fails to run, we know.

Closing for lack of feedback.

authors: Sun-ZhenXing kayhayen


text:
Master

from master merged to main

new app was added and then merged it to main branch too :)

repo: NurulloSalaydinov/Vue-Js


text:
Request: custom event

Is there any way you could add a custom cancellable event for when a power is triggered?

Yes, it is planned at next major release (3.6). But..be patient now

authors: Librazy facemywrath

repo: NyaaCat/RPGitems-reloaded