pagure

#4745 fedpkg should not suggest bad PRs
Opened by rharwood. Modified

Open
Close Issue

On non-rawhide push:

rharwood@seton:~/krb5.fedora/f32$ fedpkg push
Total 0 (delta 0), reusado 0 (delta 0)
remote: Emitting a message to the fedmsg bus.
remote: * Publishing information for 2 commits
remote: No handlers could be found for logger "pagure.lib.notify"
remote: Sending to redis to log activity and send commit notification emails
remote: * Publishing information for 2 commits
remote:   - to fedmsg
remote: 
remote: Create a pull-request for f32
remote:    https://src.fedoraproject.org/rpms/krb5/diff/master..f32
remote: 
To ssh://pkgs.fedoraproject.org/rpms/krb5
   dd3e136..48a220a  f32 -> f32

There are two problems in this case, I think:

  1. It doesn't make sense to make a PR from a branched release onto rawhide. Fedora supposes that changes will land in rawhide first.
  2. This was in fact fast-forwarding the f32 branch to match master (so any PR would have been a no-op).

Deleted.
Sorry about the noise, I got confused by the title and though this was reported against fedpkg.
Edited by lsedlar

@lsedlar this is a ticket on the pagure issue tracker, so this is fine ;-)

Thanks though!
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.