page) ] }, "prev": null, "modified": null }, { "package_id": "60fbb0a22359b4888f7ecad69bcdfcd6e70e2784", "lockfiles": { "app1_linux.lock": [ "1" ] }, "prev": null, "modified": null } ], "requires": app1_linux.lock is in each package_id. Also, the package revision prev is listed, in this case being null, because there is no locked binary in the lockfiles, but is going to be built. Note: The relative "lockfiles": { "app1_windows.lock": [ "3" ], "app2_windows.lock": [ "3" ] }, "prev": null, "modified": null } ] } Now we can see that for one package_id there are actually 2 different lockfiles

page) ] }, "prev": null, "modified": null }, { "package_id": "60fbb0a22359b4888f7ecad69bcdfcd6e70e2784", "lockfiles": { "app1_linux.lock": [ "1" ] }, "prev": null, "modified": null } ], "requires": app1_linux.lock is in each package_id. Also, the package revision prev is listed, in this case being null, because there is no locked binary in the lockfiles, but is going to be built. Note: The relative "lockfiles": { "app1_windows.lock": [ "3" ], "app2_windows.lock": [ "3" ] }, "prev": null, "modified": null } ] } Now we can see that for one package_id there are actually 2 different lockfiles

page) ] }, "prev": null, "modified": null }, { "package_id": "60fbb0a22359b4888f7ecad69bcdfcd6e70e2784", "lockfiles": { "app1_linux.lock": [ "1" ] }, "prev": null, "modified": null } ], "requires": app1_linux.lock is in each package_id. Also, the package revision prev is listed, in this case being null, because there is no locked binary in the lockfiles, but is going to be built. Note: The relative "lockfiles": { "app1_windows.lock": [ "3" ], "app2_windows.lock": [ "3" ] }, "prev": null, "modified": null } ] } Now we can see that for one package_id there are actually 2 different lockfiles

page) ] }, "prev": null, "modified": null }, { "package_id": "60fbb0a22359b4888f7ecad69bcdfcd6e70e2784", "lockfiles": { "app1_linux.lock": [ "1" ] }, "prev": null, "modified": null } ], "requires": app1_linux.lock is in each package_id. Also, the package revision prev is listed, in this case being null, because there is no locked binary in the lockfiles, but is going to be built. Note: The relative "lockfiles": { "app1_windows.lock": [ "3" ], "app2_windows.lock": [ "3" ] }, "prev": null, "modified": null } ] } Now we can see that for one package_id there are actually 2 different lockfiles

page) ] }, "prev": null, "modified": null }, { "package_id": "60fbb0a22359b4888f7ecad69bcdfcd6e70e2784", "lockfiles": { "app1_linux.lock": [ "1" ] }, "prev": null, "modified": null } ], "requires": app1_linux.lock is in each package_id. Also, the package revision prev is listed, in this case being null, because there is no locked binary in the lockfiles, but is going to be built. Note: The relative "lockfiles": { "app1_windows.lock": [ "3" ], "app2_windows.lock": [ "3" ] }, "prev": null, "modified": null } ] } Now we can see that for one package_id there are actually 2 different lockfiles

char buffer_out [256] = {0}; z_stream defstream; defstream.zalloc = Z_NULL; defstream.zfree = Z_NULL; defstream.opaque = Z_NULL; defstream.avail_in = (uInt) strlen(buffer_in); defstream.next_in = (Bytef char buffer_out [256] = {0}; z_stream defstream; defstream.zalloc = Z_NULL; defstream.zfree = Z_NULL; defstream.opaque = Z_NULL; defstream.avail_in = (uInt) strlen(buffer_in); defstream.next_in = (Bytef print(">> ${cmd} \n") def sout = new StringBuilder(), serr = new StringBuilder() def proc = cmd.execute(null, buildDir) proc.consumeProcessOutput(sout, serr) proc.waitFor() println "$sout $serr" if (proc.exitValue()

"1" ] }, "prev": null, "modified": null }, { "package_id": "60fbb0a22359b4888f7ecad69bcdfcd6e70e2784", "lockfiles": { "app1_linux.lock": [ "1" ] }, "prev": null, "modified": null } ], "requires": app1_linux.lock is in each package_id. Also, the package revision prev is listed, in this case being null, because there is no locked binary in the lockfiles, but is going to be built. Note: The relative "lockfiles": { "app1_windows.lock": [ "3" ], "app2_windows.lock": [ "3" ] }, "prev": null, "modified": null } ] } Now we can see that for one package_id there are actually 2 different lockfiles

page) ] }, "prev": null, "modified": null }, { "package_id": "60fbb0a22359b4888f7ecad69bcdfcd6e70e2784", "lockfiles": { "app1_linux.lock": [ "1" ] }, "prev": null, "modified": null } ], "requires": app1_linux.lock is in each package_id. Also, the package revision prev is listed, in this case being null, because there is no locked binary in the lockfiles, but is going to be built. Note: The relative "lockfiles": { "app1_windows.lock": [ "3" ], "app2_windows.lock": [ "3" ] }, "prev": null, "modified": null } ] } Now we can see that for one package_id there are actually 2 different lockfiles

page) ] }, "prev": null, "modified": null }, { "package_id": "60fbb0a22359b4888f7ecad69bcdfcd6e70e2784", "lockfiles": { "app1_linux.lock": [ "1" ] }, "prev": null, "modified": null } ], "requires": app1_linux.lock is in each package_id. Also, the package revision prev is listed, in this case being null, because there is no locked binary in the lockfiles, but is going to be built. Note: The relative "lockfiles": { "app1_windows.lock": [ "3" ], "app2_windows.lock": [ "3" ] }, "prev": null, "modified": null } ] } Now we can see that for one package_id there are actually 2 different lockfiles

page) ] }, "prev": null, "modified": null }, { "package_id": "60fbb0a22359b4888f7ecad69bcdfcd6e70e2784", "lockfiles": { "app1_linux.lock": [ "1" ] }, "prev": null, "modified": null } ], "requires": app1_linux.lock is in each package_id. Also, the package revision prev is listed, in this case being null, because there is no locked binary in the lockfiles, but is going to be built. Note: The relative "lockfiles": { "app1_windows.lock": [ "3" ], "app2_windows.lock": [ "3" ] }, "prev": null, "modified": null } ] } Now we can see that for one package_id there are actually 2 different lockfiles