Re: BUG: rpmbuild -ta cogito-0.12.tar.gz fails
Chris Wright wrote: * John Ellson ([EMAIL PROTECTED]) wrote: rpmbuild -ta cogito-0.12.tar.gz fails because cogito.spec.in refers to .bz2 in its Source: line, instead of to .gz. Just grab the .bz2, or the SRPM http://kernel.org/pub/software/scm/cogito/RPMS (still mirroring, I just uploaded it a bit ago) But: cd cogito cg-update make dist rpmbuild -ta cogito-0.12.tar.gz still doesn't work.Do you have a different process for generating the initial cogito-0.12-1src.rpm ? This is obviously a trivial patch. Do I need prior approval to send patches to this group? What is the the significance of Signed-off-by: Is there a FAQ I should read? No approval needed. Signed-off-by is in reference to the Developer's Certificate of Origin 1.1 (see item 11 in the Linux kernel's source file Documentation/SubmittingPatches). Thanks. Thats what I was looking for. John - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: BUG: rpmbuild -ta cogito-0.12.tar.gz fails
Chris Wright wrote: * John Ellson ([EMAIL PROTECTED]) wrote: But: cd cogito cg-update make dist rpmbuild -ta cogito-0.12.tar.gz still doesn't work.Do you have a different process for generating the initial cogito-0.12-1src.rpm ? I start from the bz2 from kernel.org. thanks, -chris So now I have to ask, where does that come from if its not created by make dist ? Is what I'm asking to do in the above sequence somehow unreasonable? Would it be any loss if the Source: line in cogito.spec.in refered to the .gz instead of the .bz2 such that the above sequence works for those of us that like to build rpms directly from the git tree? Alternatively, perhaps make dist could generate the .bz2 instead? John - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
BUG: cg-clone accepts '_' in git_ssh: URI's, but cg-push does not.
BUG: cg-clone accepts '_' in git+ssh: URI's, but cg-push does not. I suggest '_' be added to the allowed character table in send-pack.c John - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: BUG: cg-clone accepts '_' in git_ssh: URI's, but cg-push does not.
Horst von Brand wrote: John Ellson [EMAIL PROTECTED] wrote: BUG: cg-clone accepts '_' in git+ssh: URI's, but cg-push does not. Right. '_' is illegal in domain names... OK, but its legal in the path part of URI's, I believe, and I'm more bothered by the assymetry between cg-clone and cg-push. It allowed me to clone a project but not to push updates back. I was experimenting with git+ssh between two machines locally using: git+ssh://ontap/home/ellson/FIX/Linux.x86_64/build/cogito/.git John - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
BUG: rpmbuild -ta cogito-0.12.tar.gz fails
rpmbuild -ta cogito-0.12.tar.gz fails because cogito.spec.in refers to .bz2 in its Source: line, instead of to .gz. This is obviously a trivial patch. Do I need prior approval to send patches to this group? What is the the significance of Signed-off-by: Is there a FAQ I should read? John - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
