distcc: Change SRC_URI
PATCH v2 1/1 distcc: Change SRC_URI
From: Armin Kuster <[email protected]>
ERROR: distcc-3.2-r0 do_fetch: Fetcher failure: Unable to find revision d8b18df3e9dcbe4f092bed565835d3975e99432c in branch 3.2 even from upstream
ERROR: distcc-3.2-r0 do_fetch: Fetcher failure for URL: 'git://github.com/distcc/distcc.git;branch=3.2'. Unable to fetch URL from any source.
ERROR: distcc-3.2-r0 do_fetch: Function failed: base_do_fetch
[v2]
upstream deleted the branch and the hash no longer exists.
Took the git snapshot from yocto and created a copy on my github. There was no offical 3.2 release, only rc versions.
--- meta/recipes-devtools/distcc/distcc_3.2.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-devtools/distcc/distcc_3.2.bb +1 -1
@@ -14,7 +14,7 @@ PACKAGECONFIG[popt] = "--without-included-popt,--with-included-popt,popt" RRECOMMENDS_${PN} = "avahi-daemon" -SRC_URI = "git://github.com/distcc/distcc.git;branch=${PV} \ +SRC_URI = "git://github.com/akuster/distcc.git;branch=${PV} \ file://separatebuilddir.patch \ file://0001-zeroconf-Include-fcntl.h.patch \ file://default \
Signature · 1 line
2.7.4
Quoted 6 lines · Armin Kuster
From: Armin Kuster <[email protected]>
ERROR: distcc-3.2-r0
do_fetch: Fetcher failure: Unable to find revisiond8b18df3e9dcbe4f092bed565835d3975e99432cin branch 3.2 even from upstream
ERROR: distcc-3.2-r0do_fetch: Fetcher failure for URL: 'git://github.com/distcc/distcc.git;branch=3.2'. Unable to fetch URL from any source.
ERROR: distcc-3.2-r0do_fetch: Function failed:base_do_fetch
Quoted 6 lines
[v2]
upstream deleted the branch and the hash no longer exists.Took the git snapshot from yocto and created a copy on my github. There was no offical 3.2 release, only rc versions.
I think V1 was ok. Is there any difference in the 3.2-maint branch that we may not be able to use it on rocko
Quoted 26 lines
Signed-off-by Armin Kuster <[email protected]>--- meta/recipes-devtools/distcc/distcc_3.2.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)meta/recipes-devtools/distcc/distcc_3.2.bb +1
-2@@ -14,7 +14,7 @@ PACKAGECONFIG[popt] = "--without-included-popt,--with-included-popt,popt" RRECOMMENDS_${PN} = "avahi-daemon" -SRC_URI = "git://github.com/distcc/distcc.git;branch=${PV} \ +SRC_URI = "git://github.com/akuster/distcc.git;branch=${PV} \ file://separatebuilddir.patch \ file://0001-zeroconf-Include-fcntl.h.patch \ file://default \ --2.7.4
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 7 lines · Khem Raj
Quoted 6 lines · Armin Kuster
From: Armin Kuster <[email protected]>
ERROR: distcc-3.2-r0
do_fetch: Fetcher failure: Unable to find revisiond8b18df3e9dcbe4f092bed565835d3975e99432cin branch 3.2 even from upstream
ERROR: distcc-3.2-r0do_fetch: Fetcher failure for URL: 'git://github.com/distcc/distcc.git;branch=3.2'. Unable to fetch URL from any source.
ERROR: distcc-3.2-r0do_fetch: Function failed:base_do_fetch
Quoted 8 lines
Quoted 6 lines
[v2]
upstream deleted the branch and the hash no longer exists.Took the git snapshot from yocto and created a copy on my github. There was no offical 3.2 release, only rc versions.
I think V1 was ok.
It did not compile.
Quoted 2 lines
Is there any difference in the 3.2-maint branch that we may not be able to use it on rocko
Yes, the snaphot YP sources contained and 3.2-maint are not the same.
- armin
Quoted 26 lines
Quoted 26 lines
Signed-off-by Armin Kuster <[email protected]>--- meta/recipes-devtools/distcc/distcc_3.2.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)meta/recipes-devtools/distcc/distcc_3.2.bb +1
-2@@ -14,7 +14,7 @@ PACKAGECONFIG[popt] = "--without-included-popt,--with-included-popt,popt" RRECOMMENDS_${PN} = "avahi-daemon" -SRC_URI = "git://github.com/distcc/distcc.git;branch=${PV} \ +SRC_URI = "git://github.com/akuster/distcc.git;branch=${PV} \ file://separatebuilddir.patch \ file://0001-zeroconf-Include-fcntl.h.patch \ file://default \ --2.7.4
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 10 lines · Khem Raj
Quoted 9 lines · Armin Kuster
From: Armin Kuster <[email protected]>
ERROR: distcc-3.2-r0
do_fetch: Fetcher failure: Unable to find revisiond8b18df3e9dcbe4f092bed565835d3975e99432cin branch 3.2 even from upstream
ERROR: distcc-3.2-r0do_fetch: Fetcher failure for URL: 'git://github.com/distcc/distcc.git;branch=3.2'. Unable to fetch URL from any source.
ERROR: distcc-3.2-r0do_fetch: Function failed:base_do_fetch[v2]
upstream deleted the branch and the hash no longer exists.
Quoted 6 lines
Quoted 3 lines
Took the git snapshot from yocto and created a copy on my github. There was no offical 3.2 release, only rc versions.
I think V1 was ok. Is there any difference in the 3.2-maint branch that we may not be able to use it on rocko
diffstat:
INSTALL | 6 Makefile.in | 71 README.md | 62 configure.ac | 128 doc/web/man/distcc_1.html | 19 doc/web/man/index.html | 1 doc/web/man/lsdistcc_1.html | 225 include_server/basics.py | 29 include_server/basics_test.py | 28 include_server/c_extensions/distcc_pump_c_extensions_module.c | 132 include_server/c_extensions_test.py | 32 include_server/cache_basics.py | 27 include_server/compiler_defaults.py | 12 include_server/compress_files.py | 24 include_server/include_analyzer.py | 29 include_server/include_analyzer_memoizing_node.py | 48 include_server/include_analyzer_memoizing_node_test.py | 30 include_server/include_analyzer_test.py | 40 include_server/include_server.py | 134 include_server/include_server_test.py | 28 include_server/macro_eval.py | 27 include_server/macro_eval_test.py | 14 include_server/mirror_path.py | 2 include_server/mirror_path_test.py | 6 include_server/parse_command.py | 40 include_server/parse_command_test.py | 16 include_server/parse_file.py | 30 include_server/parse_file_test.py | 20 include_server/run.py | 17 include_server/setup.py | 8 include_server/statistics.py | 76 lzo/README.LZO | 123
lzo/lzoconf.h | 517 lzo/lzodefs.h | 2998 ---- lzo/minilzo.c | 7016
++--------
lzo/minilzo.h | 28 man/distcc.1 | 14 man/include_server.1 | 7 man/lsdistcc.1 | 159 packaging/RedHat/conf/clients.allow | 4 packaging/RedHat/rpm.spec | 1 pump.in | 19 src/arg.c | 3 src/backoff.c | 27 src/clirpc.c | 11 src/compile.c | 27 src/distcc.c | 15 src/distcc.h | 5 src/dotd.c | 3 src/hosts.c | 4 src/include_server_if.c | 8 src/io.c | 2 src/lsdistcc.c | 4 src/remote.c | 2 src/rpc.c | 11 src/rpc.h | 5 src/sendfile.c | 2 src/serve.c | 2 src/snprintf.h | 1 src/stats.c | 1 src/stringmap.c | 4 src/timeval.c | 7 src/timeval.h | 7 src/where.c | 15 src/zeroconf.c | 18 src/zeroconf.h | 2 test/comfychair.py | 84 test/onetest.py | 2 test/testdistcc.py | 168
Quoted 26 lines
Quoted 26 lines
Signed-off-by Armin Kuster <[email protected]>--- meta/recipes-devtools/distcc/distcc_3.2.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)meta/recipes-devtools/distcc/distcc_3.2.bb +1
-2@@ -14,7 +14,7 @@ PACKAGECONFIG[popt] = "--without-included-popt,--with-included-popt,popt" RRECOMMENDS_${PN} = "avahi-daemon" -SRC_URI = "git://github.com/distcc/distcc.git;branch=${PV} \ +SRC_URI = "git://github.com/akuster/distcc.git;branch=${PV} \ file://separatebuilddir.patch \ file://0001-zeroconf-Include-fcntl.h.patch \ file://default \ --2.7.4
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
So many questions.
What did we ship? Why doesn't it exist upstream anymore?
Shipping a fork in a personal repo sounds like a good solution for the stable branches following the principle of least surprise: they're shipping what they always did. For master/2.5 though, I'm not happy about it (but will pull this in for now to get it building again).
Ross
Quoted 126 lines · On 23 March 2018 at 14:20, akuster808 <[email protected]> wrote:
Quoted 10 lines · Khem Raj
Quoted 9 lines · Armin Kuster
From: Armin Kuster <[email protected]>
ERROR: distcc-3.2-r0
do_fetch: Fetcher failure: Unable to find revisiond8b18df3e9dcbe4f092bed565835d3975e99432cin branch 3.2 even from upstream
ERROR: distcc-3.2-r0do_fetch: Fetcher failure for URL: 'git://github.com/distcc/distcc.git;branch=3.2'. Unable to fetch URL from any source.
ERROR: distcc-3.2-r0do_fetch: Function failed:base_do_fetch[v2]
upstream deleted the branch and the hash no longer exists.Quoted 6 lines
Quoted 3 lines
Took the git snapshot from yocto and created a copy on my github. There was no offical 3.2 release, only rc versions.
I think V1 was ok. Is there any difference in the 3.2-maint branch that we may not be able to use it on rocko
diffstat:
INSTALL | 6 Makefile.in | 71 README.md | 62 configure.ac | 128 doc/web/man/distcc_1.html | 19 doc/web/man/index.html | 1 doc/web/man/lsdistcc_1.html | 225 include_server/basics.py | 29 include_server/basics_test.py | 28 include_server/c_extensions/distcc_pump_c_extensions_module.c | 132 include_server/c_extensions_test.py | 32 include_server/cache_basics.py | 27 include_server/compiler_defaults.py | 12 include_server/compress_files.py | 24 include_server/include_analyzer.py | 29 include_server/include_analyzer_memoizing_node.py | 48 include_server/include_analyzer_memoizing_node_test.py | 30 include_server/include_analyzer_test.py | 40 include_server/include_server.py | 134 include_server/include_server_test.py | 28 include_server/macro_eval.py | 27 include_server/macro_eval_test.py | 14 include_server/mirror_path.py | 2 include_server/mirror_path_test.py | 6 include_server/parse_command.py | 40 include_server/parse_command_test.py | 16 include_server/parse_file.py | 30 include_server/parse_file_test.py | 20 include_server/run.py | 17 include_server/setup.py | 8 include_server/statistics.py | 76 lzo/README.LZO | 123 lzo/lzoconf.h | 517 lzo/lzodefs.h | 2998 ---- lzo/minilzo.c | 7016 ++-------- lzo/minilzo.h | 28 man/distcc.1 | 14 man/include_server.1 | 7 man/lsdistcc.1 | 159 packaging/RedHat/conf/clients.allow | 4 packaging/RedHat/rpm.spec | 1 pump.in | 19 src/arg.c | 3 src/backoff.c | 27 src/clirpc.c | 11 src/compile.c | 27 src/distcc.c | 15 src/distcc.h | 5 src/dotd.c | 3 src/hosts.c | 4 src/include_server_if.c | 8 src/io.c | 2 src/lsdistcc.c | 4 src/remote.c | 2 src/rpc.c | 11 src/rpc.h | 5 src/sendfile.c | 2 src/serve.c | 2 src/snprintf.h | 1 src/stats.c | 1 src/stringmap.c | 4 src/timeval.c | 7 src/timeval.h | 7 src/where.c | 15 src/zeroconf.c | 18 src/zeroconf.h | 2 test/comfychair.py | 84 test/onetest.py | 2 test/testdistcc.py | 168Quoted 21 lines
Quoted 21 lines
Signed-off-by Armin Kuster <[email protected]>--- meta/recipes-devtools/distcc/distcc_3.2.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)meta/recipes-devtools/distcc/distcc_3.2.bb +1
-2@@ -14,7 +14,7 @@ PACKAGECONFIG[popt] = "--without-included-popt,--with-included-popt,popt" RRECOMMENDS_${PN} = "avahi-daemon" -SRC_URI = "git://github.com/distcc/distcc.git;branch=${PV} \ +SRC_URI = "git://github.com/akuster/distcc.git;branch=${PV} \ file://separatebuilddir.patch \ file://0001-zeroconf-Include-fcntl.h.patch \ file://default \ --2.7.4
Quoted 5 lines
Quoted 5 lines
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 9 lines · Ross
So many questions.
What did we ship? Why doesn't it exist upstream anymore?
Shipping a fork in a personal repo sounds like a good solution for the stable branches following the principle of least surprise: they're shipping what they always did. For master/2.5 though, I'm not happy about it (but will pull this in for now to get it building again).
We might yet get a functional 3.3 upgrade for master in time for 2.5?
Alex
That would be the ideal.
Ross
Quoted 15 lines · Alexander Kanavin
Quoted 10 lines · Ross
So many questions.
What did we ship? Why doesn't it exist upstream anymore?
Shipping a fork in a personal repo sounds like a good solution for the stable branches following the principle of least surprise: they're shipping what they always did. For master/2.5 though, I'm not happy about it (but will pull this in for now to get it building again).
We might yet get a functional 3.3 upgrade for master in time for 2.5?
Alex