#78 [RFE] Verify the origin of the git checkout before to operate
Opened 7 years ago by kwizart. Modified a year ago

Since there are now several alternate rpkg frontends, users need to use the appropriate frontend for a given checkout. For example we don't want fedpkg to be used by any other 3rd party repository infra, and the other way.

If the wrong frontend is used, more likely that the build will fails at a later point, but it would be nice not to catch the error earlier, so the contributors get advertised earlier and do not expect any infrastructure issue.


There are cases where you actually want the "wrong" frontend: for example you may want to use mockbuild to build your package for different system.

hum , fedpkg srpm in kffmpegthumbnailer directory , should say fedora proper don't have kffmpegthumbnailer , because it is in RPMFusion , rfpkg srpm in fedora proper package directory, should have the same warning .
I'm not seeing use fedpkg for use in other system , maybe just send build to koji ... but is a case much less used . Should warning at least .

At Red Hat, we have some internal packages that can not be in Fedora. Since many developers run Fedora, we want to provide builds of these packages for them. The repos are managed with rhpkg, but to create Fedora builds we want to call fedpkg mockbuild in a clone from internal dist-git. Admittedly, this is very rare.

I fully agree a warning would be great here: the user should be aware that something unusual is going on and errors are to be expected.

fedora proper don't have kffmpegthumbnailer

This may be related to issue https://pagure.io/fedpkg/issue/37 and dist-git issue https://github.com/release-engineering/dist-git/issues/8 . After these two issues get fixed, I think it should be easy to tell that.

Meanwhile, I also agree with giving a warning here at this moment, if a different frontend client is used in a checkout from different dist-git.

This issue has been unresolved for more than a year, and is going to be closed within a week if no further action is taken. If you feel this is in error, please contact me.
This is a cleaning process suggested by Jay Greguske. Copy of this ticket was already closed in JIRA tracker.

This issue still not fixed , so shouldn't be closed iMO

Well, I disagree: this issue can be closed.

Despite I don't expect running a rfpkg clone with fedpkg will not make sense, I can imagine some use cases where a fedpkg clone can be used with rfpkg.

if frontends want to enforce a check, maybe it can be done at the frontend level.

I sometimes run fedpkg srpm && mock something , on 3rd repos and the error is not friendly

fedpkg srpm

Downloading mock-rpmfusion-free-30.1.tar.bz2

################################################################## 100.0%

Remove downloaded invalid file /home/sergio/rpmfusion/new/mock-rpmfusion-free/mock-rpmfusion-free-30.1.tar.bz2
Could not execute srpm: Server returned status code 404

and the error is not friendly

agreed, I ran into this problem today and some better error message would be useful

Login to comment on this ticket.

Metadata