Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
In some cases, git request-pull will emit a bogus message like this:
warn: You locally have tag1 but it does not (yet)
warn: appear to be at git://git.kernel.org/pub/scm/virt/kvm/kvm.git
warn: Do you want to push it there, perhaps?
For example:
1. create two tags (git tag -mtag1 tag1; git tag -mtag2 tag2)
2. push them to a remote repository git://example.org/foo.git
3. Do "git request-pull origin/master git://example.org/foo.git"
The output will be a request to pull "git://example.org/foo.git tags/tag2" with the above warning. The reason is a simple coding error. Here:
if ($deref && $ref eq "tags/$ARGV[2]") {
$ref is compared with "tags/tag1". However, as shown by the abbr subroutine, $ref has the format "refs/tags/tag1":
sub abbr {
my $ref = shift;
if ($ref =~ s|^refs/heads/|| || $ref =~ s|^refs/tags/|tags/|) {
return $ref;
} else {
return $ref;
}
}
Reproducer is not available so we fall back to SanityOnly.
I have added a simple test to have some basic coverage on git-request-pull:
TC#562928 /CoreOS/git/Sanity/request-pull
We'll re-schedule the suite and if all passes, we can consider this verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0735
In some cases, git request-pull will emit a bogus message like this: warn: You locally have tag1 but it does not (yet) warn: appear to be at git://git.kernel.org/pub/scm/virt/kvm/kvm.git warn: Do you want to push it there, perhaps? For example: 1. create two tags (git tag -mtag1 tag1; git tag -mtag2 tag2) 2. push them to a remote repository git://example.org/foo.git 3. Do "git request-pull origin/master git://example.org/foo.git" The output will be a request to pull "git://example.org/foo.git tags/tag2" with the above warning. The reason is a simple coding error. Here: if ($deref && $ref eq "tags/$ARGV[2]") { $ref is compared with "tags/tag1". However, as shown by the abbr subroutine, $ref has the format "refs/tags/tag1": sub abbr { my $ref = shift; if ($ref =~ s|^refs/heads/|| || $ref =~ s|^refs/tags/|tags/|) { return $ref; } else { return $ref; } }