Description of problem:

I'm not entirely sure _where_ this issue lives, so I'm filing it against the command that broke for me. The problem, and the fix, may well live with a different component.

The switch to `fedpkg prep` / `fedpkg local` extracting and building package sources inside a `${name}-${version}-build/${name}-${version}/` subdirectory broke the `fedpkg patch` command, which (as implemented in pyrpkg) expects there to be a top-level `${name}-${version}` directory next to the spec file.

Version-Release number of selected component (if applicable):
fedpkg-1.45-5.fc41.noarch


How reproducible:
100%

Steps to Reproduce:
Start with a fedpkg clone of any package (let's use fedpkg itself...)
1. fedpkg clone fedpkg
2. cd fedpkg
3. fedpkg --release f41 prep  # creates the directory fedpkg-1.45-build/fedpkg-1.45/
4. fedpkg patch my_fix_suffix  # (it doesn't matter that there are no
                                 files with that suffix, we won't get that far)

Actual results:
Could not execute patch: Expanded source dir not found!


Expected results:
fedpkg looks for files with the suffix .my_fix_suffix and creates a patch


Additional info:

The relevant part of the pyrpkg code is in
/usr/lib/python3.13/site-packages/pyrpkg/__init__.py

With python3-rpkg-1.67-5.fc41.noarch it's on lines 2158-2162,
inside def patch(self, suffix, rediff=False):

        # See if there is a source dir to diff in
        if not os.path.isdir(os.path.join(self.path,
                                          '%s-%s' % (self.repo_name,
                                                     self.ver))):
            raise rpkgError('Expanded source dir not found!')