jiebi/CodeConvo huggingface dataset:
Change:
libjpeg_original = callPackage ../development/libraries/libjpeg { }; # also known as libturbojpeg libjpeg_turbo = callPackage ../development/libraries/libjpeg-turbo { }; <del> libjpeg_drop = callPackage ../development/libraries/libjpeg-drop { }; </del> libjpeg = libjpeg_turbo; libjreen = callPackage ../development/libraries/libjreen { };

Discussion:
the drop patches were upstreamed to libjpeg in version 9d 2020-01-12: https://abi- and are no longer maintained so the separate package can be safely removed.
will fix this
thx.
Change:
assemblyscript = callPackage ../development/compilers/assemblyscript { }; <del> authy = callPackage ../applications/misc/authy { }; </del> authz0 = callPackage ../tools/security/authz0 { }; auth0-cli = callPackage ../tools/admin/auth0-cli { };

Discussion:
Steps to reproduce the behavior: Authy, stable or unstable channel No additional context, seems like the package of one of the dependencies was taken off snap for some reason Could not run for some reason... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It seems that Twilio have deprecated the desktop apps. . Looking on it seems that they have pulled the snap from Snapcraft. It also seems that the Flatpak has been removed. See and .
Well, i suppose there is nothing that can be done. Thanks for explaining the situation to me!
I'm not sure that issue is really resolved, as I think we need to remove the package from nixpkgs as its deprecated. I believe you are the package maintainer. Should it maybe be removed?
Thanks for the tag and explanation, I had read the announcement when it came out and the apps were still available on Snapcraft. It must have been pulled after a while. It's better to remove the package now. I'll do it sometime this week.
Change:
, spandsp3 , libuuid , libvpx <ins> , cmake , dbusSupport ? true </ins> }: stdenv.mkDerivation rec { version = "2.9.0";

Discussion:
Baresip fails to build after because the baresip no longer finds librem through pkg-config. Building baresip with Cmake resolves this, but then there is a new build failure: Steps to reproduce the behavior: baresip
Sorry! I think fixes this. I developed and tested them together but wanted to take more time to be sure baresip was finding all of its dependencies. I didn't realize that merging one without the other would break things. We can either merge or else revert and
Waiting for is fine by me.
Change:
sha256 = "acc10e10909f0f956ba1b42b6c450ea0bdaaa27b3942899f65931396cfcdd36a"; }; <ins> patches = [ (fetchpatch { url = https://github.com/vstinner/faulthandler/commit/67b661e.patch; sha256 = "1nn8c9nq5qypja949hzz0n4yprsyr63wihf5g3gwrinm2nkjnnv7"; }) (fetchpatch { url = https://github.com/vstinner/faulthandler/commit/07cbb7b.patch; sha256 = "0fh6rjyjw7z1hsiy3sgdc8j9mncg1vlv3y0h4bplqyw18vq3srb3"; }) ]; </ins> meta = { description = "Dump the Python traceback"; license = stdenv.lib.licenses.bsd2;

Discussion:
python27Packages.faulthandler fails to build on the unstable channel Cc () The output shows test failures due to regular expressions not matching. E.g. It seems that the tests are expecting to see in the message, while the actual error says . If it's just that, I hope that it would be easy to fix the build. I am happy to help if given some guidance. Full output: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs:
This is an upstream issue. See similar issue Best write them that they should also accept , , etc. Then you can open a PR here that adds a patch to the derivation.
Thanks, will look into that. It probably makes sense to keep this issue open to track the upstream one though.
Note that a patch is available ( ), it may make sense to apply it (e.g. done for Fedora ) while waiting for a new release. I am still happy to try and do that.
I don't think that patch will work. It accepts but not .
Sorry, I missed that :(
I opened an upstream PR: And I applied the patch in Nixpkgs:
fyi has now been merged and a release is pending (see )... hopefully we won't need the patch after that. Thanks everyone for your work!
I removed the patches in .
Change:
sha256 = "9b47c5c3a094fa518ca88aeed35ae75834d53e4285512c61879f67a48c94ddaf"; }; propagatedBuildInputs = [ pkgs.libGLU_combined pkgs.freeglut self.pillow ]; <del> patchPhase = '' sed -i "s|util.find_library( name )|name|" OpenGL/platform/ctypesloader.py sed -i "s|'GL',|'libGL.so',|" OpenGL/platform/glx.py sed -i "s|'GLU',|'${pkgs.libGLU_combined}/lib/libGLU.so',|" OpenGL/platform/glx.py sed -i "s|'glut',|'${pkgs.freeglut}/lib/libglut.so',|" OpenGL/platform/glx.py </del> <ins> patchPhase = let ext = stdenv.hostPlatform.extensions.sharedLibrary; in '' substituteInPlace OpenGL/platform/glx.py  --replace "'GL'" "'${pkgs.libGL}/lib/libGL${ext}'"  --replace "'GLU'" "'${pkgs.libGLU}/lib/libGLU${ext}'"  --replace "'glut'" "'${pkgs.freeglut}/lib/libglut${ext}'" substituteInPlace OpenGL/platform/darwin.py  --replace "'OpenGL'" "'${pkgs.libGL}/lib/libGL${ext}'"  --replace "'GLUT'" "'${pkgs.freeglut}/lib/libglut${ext}'" </ins> ''; meta = { homepage = http://pyopengl.sourceforge.net/;

Discussion:
After upgrading from 18.03 to unstable, curabydagoma (whose package I maintain) does not work anymore, with error "Unable to load OpenGL library". I have easily narrowed it down to the pyopengl package. But I don't know what I can do to fix this error... system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: (this is a copy of the nixos-unstable branch of nixpkgs-channels).
This works for me. Do you have in your ?
Yes: ... but no in this directory... So, with a little more digging, when looking at the mesa-driver package contents (because /run/opengl-driver/lib is a symlink to ), it looks like there is something wrong with what I have in this package on unstable:
I see there have been recent changes in and also in the mesa drivers package. Maybe it is related ? My 3D hardware is the common Intel laptop chip, no nvidia, no radeon - maybe this information is important here...
By the way, is missing in all new occurrences of (version 17.3.8, from nixos-unstable), whereas it is present in all occurrences of version 17.3.6, from nixos-18.03.
This seems to work on (at least) darwin:
I'm unsure what's the rationale behind not handling the same way it is done with : but if we do, as mentioned above, it seems to work for me.
That no longer contains libGL is an intentional change introduced by . Directly link to the libraries in the and packages instead.
Okay so it is indeed a change in mesa-drivers. It may impact other packages too... I think I was having a similar problem with other packages, but I'm not sure anymore and I prefer taking care of one thing at a time. Once I have the pyopengl stuff working, I'll take a look at the other problems I had... Now that I see how it is done for pyopengl, I may make a PR to do the same on another package, if needed. Thanks
Packages Minetest and Openarena are still affected by issue.
I haven't found a better way than to reintroduce back to :
Change:
{ appimageTools , fetchurl , lib <del> , xorg , udev , wooting-udev-rules </del> , makeWrapper }: <del> appimageTools.wrapType2 rec { </del> <ins> let </ins> pname = "wootility"; version = "4.6.20"; src = fetchurl { url = "https://s3.eu-west-2.amazonaws.com/wooting-update/wootility-lekker-linux-latest/wootility-lekker-${version}.AppImage"; sha256 = "sha256-JodmF3TThPpXXx1eOnYmYAJ4x5Ylcf35bw3R++5/Buk="; }; <ins> in appimageTools.wrapType2 { inherit pname version src; </ins> extraInstallCommands = let contents = appimageTools.extract { inherit pname version src; };

Discussion:
It would be nice if the packages provided a icon. the following in your : up a graphical application launcher and search for Wootility. Please run and paste the result. <pre<samp- system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: </samp</pre
PR submitted that, among other things, adds a desktop-entry file.
Change:
description = "A library and command-line utility to manage image metadata"; platforms = platforms.all; license = licenses.gpl2Plus; <del> maintainers = [ ]; </del> <ins> maintainers = with maintainers; [ wegank ]; </ins> }; }

Discussion:
Steps to reproduce the behavior: See . Adding in fixes the build on my machine. Broken since . Please run and paste the result.
Change:
qtWrapperArgs = [ "--prefix FREI0R_PATH : ${frei0r}/lib/frei0r-1" <ins> "--prefix LADSPA_PATH : ${ladspaPlugins}/lib/ladspa" </ins> "--prefix LD_LIBRARY_PATH : ${stdenv.lib.makeLibraryPath [ jack1 SDL2 ]}" "--prefix PATH : ${mlt}/bin" ];

Discussion:
Shotcut in theory supports LADSPA plugins. However, LADSPA plugins are not found by Shotcut on NixOS version Install a bunch of LADSPA plugins (by listing them in ) Open Shotcut Add effects to a track Look for audio effects: no LADSPA plugins are shown Please run and paste the results.
cc maintainers
I tried to build shotcut and mlt with ladspa-sdk and set LADSPA_PATH, but did not manage to get the ladspa plugins working yet. ,-(
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
found out why: configure is using , which is not available, and therefore does disable ladspa. Preparing a PR.
Change:
opal = callPackage ../development/libraries/opal {}; openjpeg_1 = callPackage ../development/libraries/openjpeg/1.x.nix { }; <del> openjpeg_2_0_1 = callPackage ../development/libraries/openjpeg/2.0.1.nix { }; </del> <ins> openjpeg_2_0 = callPackage ../development/libraries/openjpeg/2.0.nix { }; </ins> openjpeg_2_1 = callPackage ../development/libraries/openjpeg/2.1.nix { }; openjpeg = openjpeg_2_1;

Discussion:
I tried building openjpeg as a dependency when using on Mac OS X, and it failed on trying to run javac. Nevertheless, its derivation seemed to define (long line follows). The package built successfully after I installed an external JDK. It seems that for some strange reason the build script is ignoring the option.
Should fix this. JPIP builds a java component, but the cmake script does not require for
Thanks for the quick reaction! I will try the fix soon!
Change:
<ins> From b009cca2026b615ef5386faa4c0230bc27c4161d Mon Sep 17 00:00:00 2001 From: Greg Hudson <ghudson@mit.edu> Date: Thu, 12 Mar 2020 00:44:10 -0400 Subject: [PATCH] Fix typo in musl build fix Commit cbdbc8d00d31344fafe00e0fdf984e04e631f7c4 checked for __GLIBC__PREREQ instead of __GLIBC_PREREQ, thus accidentally reverting the workaround introduced in commit bf5953c549a6d279977df69ffe89b2ba51460eaf.  Fix the typo. ticket: 8880 --- src/util/support/plugins.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/util/support/plugins.c b/src/util/support/plugins.c index 1644d16fd0..1ff10c354d 100644 --- a/src/util/support/plugins.c +++ b/src/util/support/plugins.c @@ -62,7 +62,7 @@ * dlopen() with RTLD_NODELETE, we weren't going to unload the plugin objects * anyway. */ -#ifdef __GLIBC__PREREQ +#ifdef __GLIBC_PREREQ #if ! __GLIBC_PREREQ(2, 25) #define dlclose(x) #endif </ins>

Discussion:
After (krb5: 1.17 -1.18) is merged, doesn't build with anymore. The error is: Since is a dependency of , this affects significant number of downstream packages. To Reproduce cc
Change:
stdenv.mkDerivation rec { pname = "most"; <del> version = "5.1.0"; </del> <ins> version = "5.2.0"; </ins> src = fetchurl { url = "https://www.jedsoft.org/releases/${pname}/${pname}-${version}.tar.gz"; <del> sha256 = "008537ns659pw2aag15imwjrxj73j26aqq90h285is6kz8gmv06v"; </del> <ins> hash = "sha256-lFWuuPgm+oOFyFDcIr8PIs+QabPDQj+6S/LG9iJtmQM="; </ins> }; <del> patches = [ # Upstream patch to fix parallel build failure ./parallel-make.patch ]; </del> outputs = [ "out" "doc" ]; makeFlags = [

Discussion:
Package name: most Latest released version: 5.2.0 <!-- Search your package here: --- Current version on the unstable channel: 5.1.0 Current version on the stable/release channel: 5.1.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
githubId = 20923; name = "Erik Timan"; }; <ins> olebedev = { email = "ole6edev@gmail.com"; github = "olebedev"; githubId = 848535; name = "Oleg Lebedev"; }; </ins> olejorgenb = { email = "olejorgenb@yahoo.no"; github = "olejorgenb";

Discussion:
Project description A CLI tool to generate a file for Buildkite on the fly. Metadata homepage URL: source URL: license: mit platforms: all (I am not sure abut this)
Change:
jsonschema = callPackage ../development/python-modules/jsonschema { }; <ins> jsonschema_3 = callPackage ../development/python-modules/jsonschema/3_x.nix { }; </ins> jsonstreams = callPackage ../development/python-modules/jsonstreams { }; json-tricks = callPackage ../development/python-modules/json-tricks { };

Discussion:
Steps to reproduce the behavior: (as of ) <details<summaryBuild Log</summary<preerror: builder for '/nix/store/8r1frbwzxwncagff57r7zz86zl2nsxbm-python3.10-jsonschema-' failed with exit code 1; last 10 log lines: For full logs, run 'nix log /nix/store/8r1frbwzxwncagff57r7zz86zl2nsxbm-python3.10-jsonschema-'. error: 1 dependencies of derivation '/nix/store/2413pkb4n4z1bj0rywpcfbi8s1yisvkg-python3.10-bravado-core-' failed to build error: 1 dependencies of derivation '/nix/store/x9h491ipp10gpp771jzfr3qyn3y6pbf9-powerdns-admin-' failed to build </pre</detailsLooks like json schema got updated to 4.13 which requires adding a patch. When , we're not patching (please excuse the pun), so it tries to apply to new patch against 3.2.0 which, of course, fails. Seems like we probably just need to override the to remove the offending patch? <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result.
, and are also broken in similar fashion.
I'll take a look later today.
I opened .
Change:
(fetchNuGet { pname = "Microsoft.CSharp"; version = "4.0.1"; sha256 = "0zxc0apx1gcx361jlq8smc9pfdgmyjh6hpka8dypc9w23nlsh6yj"; }) (fetchNuGet { pname = "Microsoft.DotNet.PlatformAbstractions"; version = "2.0.3"; sha256 = "020214swxm0hip1d9gjskrzmqzjnji7c6l5b3xcch8vp166066m9"; }) (fetchNuGet { pname = "Microsoft.Extensions.DependencyModel"; version = "2.0.3"; sha256 = "0dpyjp0hy9kkvk2dd4dclfmb10yq5avsw2a6v8nra9g6ii2p1nla"; }) <del> (fetchNuGet { pname = "Microsoft.NETCore.App.Host.linux-x64"; version = "6.0.31"; sha256 = "10s0p30qzfn9zibp1ldnqar87hqs47ni3rwqpvwx4jn3589cl9sn"; }) (fetchNuGet { pname = "Microsoft.NETCore.App.Ref"; version = "6.0.31"; sha256 = "19a4ainxj8jxij7ckglbmlnvrjxp72xfgx0r6lbglzh9dhsakwm7"; }) (fetchNuGet { pname = "Microsoft.NETCore.App.Runtime.linux-x64"; version = "6.0.31"; sha256 = "0pw2n3j6vbmbghda1cvkhi3c39a49xk0a4w059mfya017adl6kac"; }) </del> (fetchNuGet { pname = "Microsoft.NETCore.Platforms"; version = "1.0.1"; sha256 = "01al6cfxp68dscl15z7rxfw9zvhm64dncsw09a1vmdkacsa2v6lr"; }) (fetchNuGet { pname = "Microsoft.NETCore.Platforms"; version = "1.1.0"; sha256 = "08vh1r12g6ykjygq5d3vq09zylgb84l63k49jc4v8faw9g93iqqm"; }) (fetchNuGet { pname = "Microsoft.NETCore.Targets"; version = "1.0.1"; sha256 = "0ppdkwy6s9p7x9jix3v4402wb171cdiibq7js7i13nxpdky7074p"; })

Discussion:
Package name: xivlauncher Latest released version: Current version on the unstable channel: 1.0.8 Current version on the stable/release channel: 1.0.8 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
9 also released yesterday but I don't see a PR or issue for it. Quite likely there will be sever more releases as they work on fixes for the new expansion that dropped today.
9 (which is recent enough to successfully download and play Dawntrail) was merged to master yesterday, and 24.05 today; we're at the mercy of Hydra for that to show up in the release channels. Hopefully that will be fairly soon. I'll get around to 1.1.0 at some point – it fixes repair, but that's it, and I'm currently enjoying the new expansion.
Ah! I didn't see 1.0.9 got in when I search! Enjoy Dawntrail!
Change:
<ins> diff --git a/src/opencl_generate_dynamic_loader.py b/src/opencl_generate_dynamic_loader.py index 790705330..2acedbc56 100755 --- a/src/opencl_generate_dynamic_loader.py +++ b/src/opencl_generate_dynamic_loader.py @@ -134,12 +134,7 @@ static void load_opencl_dll(void) /* Names to try to load */ const char * const opencl_names[] = { -		"libOpenCL.so",		/* Linux/others, hack via "development" sub-package's symlink */ -		"OpenCL",		/* _WIN */ -		"/System/Library/Frameworks/OpenCL.framework/OpenCL", /* __APPLE__ */ -		"opencl.dll",		/* __CYGWIN__ */ -		"cygOpenCL-1.dll",	/* __CYGWIN__ */ -		"libOpenCL.so.1"	/* Linux/others, no "development" sub-package installed */ +		"@ocl_icd@/lib/libOpenCL.so"	/* NixOS */ }; for (i = 0; i < sizeof(opencl_names)/sizeof(opencl_names[0]); i++) { </ins>

Discussion:
Project description Is it possible to add OpenCL support to ? Details can be found by link below: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I tried but I'm getting a weird linker error: I have no idea what causes it. Looking at the source, it looks perfectly fine.
CC
Worked around it with . PR:
Change:
owner = "dtschump"; repo = "gmic"; rev = "v.${version}"; <del> hash = "sha256-lrIlzxXWqv046G5uRkBQnjvysaIcv+iDKxjuUEJWqcs="; </del> <ins> hash = "sha256-oEH4GlSV+642TGSJJhV4yzydh1hAQZfzwaiPAZFNQtI="; </ins> }; # TODO: build this from source

Discussion:
Steps to reproduce the behavior: gmic from There are more of those function arity errors, but just a small sample since they're the same. I'm going to assume pull in today has something to do with it. no maintainer? merged and it shows failures for gmic. gmic is used for me in GIMP and darktable. Please run and paste the result.
I will revert this preventively. There are many strange bugs happening.
Change:
}: # nixpkgs-update: no auto update <del> webcord.overrideAttrs (old: { </del> <ins> (webcord.override { inherit electron; }).overrideAttrs (old: { </ins> pname = "webcord-vencord"; patches = (old.patches or [ ]) ++ [

Discussion:
Under Wayland on Hyprland, trying to launch Webcord results in a frozen window and then a crash on startup. It doesn't matter if I launch using Ozone flags or not. Vanilla Discord package launches without issue. I did not test if Webcord launches under Xorg. Steps to reproduce the behavior: launcher or shell to launch Webcord it crash instead of starting properly. Webcord launches and works fine. I am using Hyprland's upstream flake. However, I don't see why that might be relevant, but it might be worth mentioning. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Please test with an alternative Wayland compositor, e.g., sway or river.
Unfortunately, same behavior on Sway.
Then it's safe to assume it's an electron problem. We may consider overriding the electron version. is webcord working for you two?
Works for me
I've never run into such an issue on sway. did you ensure to disable hyprland when testing sway? Also, can you try with to rule out any electron issues?
It's probably the vencord patch
Seems to be the vencord patch. Logs of are as follows, but unlike the app actually starts. Perhaps would help?
On nixos-unstable webcord-vencord launches on Xorg but does not have anything relating to vencord working on master everything works properly on Xorg
I updated to vencord 1.8.4. It's still not working. I'm running out of ideas on what the cause could be.
seems to be caused by and it's still broken on . I was able to prevent the segfault by using electron 29:
Change:
EOF chmod +x $out/bin/XMind <del> ln -s ${jre} $out/libexec/jre </del> <ins> ln -s ${jre8} $out/libexec/jre </ins> ''; meta = with lib; {

Discussion:
Building in a current git checkout of the Nixpkgs repo gives the following error:
Ping

Steps to reproduce the behavior: -env -i xmind or xmind to nixos config Please run and paste the result.
Install log when installing via is not exactly the same :
Change:
{ lib, stdenv, callPackage, fetchFromGitHub, runCommandLocal, makeWrapper, substituteAll <del> , sbcl, bash, which, perl, nettools </del> <ins> , sbcl, bash, which, perl, hostname </ins> , openssl, glucose, minisat, abc-verifier, z3, python , certifyBooks ? true } @ args:

Discussion:
The output from building the target on macOS: Note that if I hack the patch file associated with the derivation to use a extension, it builds fine.
The should be changed to a placeholder and then the placeholder should be replaced with
Change:
{ fetchurl, stdenv, coreutils, makeWrapper }: <del> let version = "1.10.8"; in </del> <ins> let version = "1.10.9"; in </ins> stdenv.mkDerivation { pname = "ant";

Discussion:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
Bumping to 1.10.9 is required. There is an additional reference for a download in for ant-contribute. That is already at the latest version so doesn't need to be bumped.
Change:
buildGoModule rec { pname = "bluetuith"; <del> version = "0.1.8"; </del> <ins> version = "0.1.9"; </ins> src = fetchFromGitHub { owner = "darkhz"; repo = pname; rev = "v${version}"; <del> sha256 = "sha256-b+J+8nxFZYJlAKOStpH7ItPqMw7inM5pss17kyX1brg="; </del> <ins> sha256 = "sha256-vdHnG0uQdy5PboIovtxl5i9xwFpjYLCZf2IGeiMcWe8="; </ins> }; <del> vendorHash = "sha256-d0O54KNGLXU8FGr1eSEp30JMWNVo91Le2MI8UnAfTuU="; </del> <ins> vendorHash = "sha256-pYVEFKLPfstWWO6ypgv7ntAaE1Wmq2XKuZC2ccMa8Vc="; </ins> ldflags = [ "-s" "-w" ];

Discussion:
Package is broken at version 0.1.8. It still worked at version 0.1.7, so I assume that is to blame. I've verified that the issue is fixed in 0.1.9, so I assume all that's needed would be to kick the bot. Not sure how to do that. No panic
Change:
<del> diff -ur OpenCSG-1.4.2-pristine/example/example.pro OpenCSG-1.4.2/example/example.pro --- OpenCSG-1.4.2-pristine/example/example.pro	2016-09-27 06:11:16.000000000 +0900 +++ OpenCSG-1.4.2/example/example.pro	2019-05-07 10:45:18.785251737 +0900 @@ -6,7 +6,9 @@ INCLUDEPATH += ../include LIBS += -L../lib -lopencsg -lGLEW -INSTALLDIR = /usr/local +isEmpty(INSTALLDIR) { +  INSTALLDIR = /usr/local +} INSTALLS += target target.path = $$INSTALLDIR/bin diff -ur OpenCSG-1.4.2-pristine/opencsg.pro OpenCSG-1.4.2/opencsg.pro --- OpenCSG-1.4.2-pristine/opencsg.pro	2016-09-27 06:11:16.000000000 +0900 +++ OpenCSG-1.4.2/opencsg.pro	2019-05-07 10:44:50.578698165 +0900 @@ -1,2 +1,3 @@ TEMPLATE = subdirs SUBDIRS  = src example +CONFIG   += ordered </del>

Discussion:
Package name: opencsg Latest released version: 1.6.0 Current version on the unstable channel: 1.4.2 Current version on the stable/release channel: 1.4.2 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: