threads / discuss / 38559

could not verify object error

Subject: could not verify object error

## tl;dr

2 messages between Feb 12, 2015 and Feb 13, 2015.

replies: 1people: 2as markdown or json

Daniel Devlin· Feb 12, 2015, 12:32 UTC · lore
Hi there,

I have been running: repo = Rugged::Config.global type = "commit" tagname = "v99.99.2" username = repo["user.name"] email = repo["user.email"] message = "this is the message for the annotated tag" tag_contents = "object f849f9e28c7f36a826d4b451efb16516c0c3acc2\ntype #{type}\ntag # {tagname}\ntagger #{username} <#{email}> #{Time.new.to_i} +0000\n\n#{message}" #puts tag_contents #puts "****************************" #puts command executecommand = "printf \"#{tag_contents}\" | git mktag"

Open3.popen3(executecommand) do |stdin, stdout, stderr, wait_thr|
  exit_stats = wait_thr.value
  errors = stderr.readlines
  puts "Errors are #{errors}"
  unless exit_stats.success?
    raise Exception, 'There was an error encountered'
  end
  signature_file_sha = stdout.readline.chomp
  puts "signature sha is #{signature_file_sha}"
end

on my local machine and it runs successfully. I have tried to run it on a vm with git 2.0.4 but keep getting char 7 could not verify object error message. Any suggestions as to why would be greatly appreciated.

Thanks, Daniel

Jeff King· Feb 13, 2015, 09:56 UTC · re: Daniel Devlin · lore

Re: could not verify object error

On Thu, Feb 12, 2015 at 12:32:45PM +0000, Daniel Devlin wrote:
Show 8 quoted lines
> tag_contents = 
> "object f849f9e28c7f36a826d4b451efb16516c0c3acc2\ntype #{type}\ntag #
> {tagname}\ntagger #{username} <#{email}> #{Time.new.to_i} +0000\n\n#{message}"
> [...]
> executecommand = "printf \"#{tag_contents}\" | git mktag"
> [...]
> I have tried to run it on a vm with git 2.0.4 but keep 
> getting char 7 could not verify object error message. 

Do you have object f849f9e28c... in the repository where you are running mktag? If so, is it a commit object, as you are putting in the type field? What does:

  git cat-file -t f849f9e28c7f36a826d4b451efb16516c0c3acc2
show?
-Peff

← back to recent threads