Thank you for your quick response. I merged your merge requests. I realized that I did not understand what I did with gbp workflow. I need to grub the basic concept and workflow with gbp buildpackage and gbp pq.
Need to separate upstream source and debian/ directory. right? Upstream source code should work with gbp pq. debian/ directory works with git. Is this outlook for gbp correct? On Sun, Sep 14, 2025 at 01:33:47PM -0700, Otto Kekäläinen wrote: > Hello! > > The package has a bunch of git commits that modify files outside the > allowed debian/ directory: [snip!] > Perhaps you ran "quilt push" at some point in time and committed it? I had never used quilt command in this reqposity. I always uses "dpkg-source --commit" command, When I want to make patch serise. [snip!] > Fix proposed in https://salsa.debian.org/debian/xfireworks/-/merge_requests/2 > > If you merge the above, I can also finalize !1 to have CI on your > package so that regressions / easily testable mistakes in the future > will be automatically detected. Thanks! I merged your merge request. > Btw, the commands I use to switch to patches applies and back to > normal Debian branch are usually: > > gbp pq import --force --time-machine=10 > gbp pq export --drop --commit > > The default gbp pq commands without these extra arguments easily cause > extra branches to be left behind or patches not getting rebases > properly. Thank you for giving advice. I read the gbp document. I didn't get typical workflow. sign... -- ====+====+====+====+====+====+====+====+====+====+====+====+====+====+ Yukiharu Yabuki (矢吹幸治) I use Debian GNU/Linux mail: [email protected] ====+====+====+====+====+====+====+====+====+====+====+====+====+====+
