[git-buildpackage] Non-standard debian folder location?

[Andy Shinn]

I am curious if there is a workflow for creating a patched version of a package when the upstream keeps the debian package configuration folder in another location? Specifically, I am trying to rebuild multiple versions of https://github.com/kamailio/kamailio and the package lives in sub-folders at https://github.com/kamailio/kamailio/tree/master/pkg/kamailio/deb.

My current workaround is to create the upstream branch per version (for example upstream/sid), copy to the debian folder, make a commit, then import. Is there any better way to go about this?
-- 
Confidentiality Notice: This email and any files transmitted with it are 
confidential and intended solely for the use of the individual or entity to 
whom they are addressed.  Additionally, this email and any files 
transmitted with it may not be disseminated, distributed or copied. Please 
notify the sender immediately by email if you have received this email by 
mistake and delete this email from your system. If you are not the intended 
recipient, you are notified that disclosing, copying, distributing or 
taking any action in reliance on the contents of this information is 
strictly prohibited. ​​ 


-- 
 
<https://go2.medallia.com/medallia-named-a-leader-2025-gartner-mq-voc.html?source=Marketing%20-%20Vanity%20URL&utm_campaign=FY26Q2_GLBL_Gartner_MQ_VoC&utm_source=employee-signature&utm_medium=image-link>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6170 bytes
Desc: not available
URL: <http://lists.sigxcpu.org/pipermail/git-buildpackage/attachments/20250625/113131e8/attachment.bin>