On Fri, 2025-12-05 at 14:46 +0500, Andrey Rakhmatullin wrote: > On Fri, Dec 05, 2025 at 03:00:25PM +0530, jvk wrote: > > > > I was able to make a playwirght project under my name space on > > > > salsa > > > > debian and i think have managed to get it in the format the > > > > debian > > > > needs with the 1.56.0 version. > > > > > > It looks like you've manually made the "New upstream version > > > 1.56.0+ds" > > > commit and included generated files in it. This commit should be > > > done > > > by > > > gbp import-orig instead. > > I seriously cant understand what you mean, this is not helping. > > I mean that simply using gbp import --orig, like you guides tell you, > wouldn't produce the repo you linked, so you must have done something > else. If you want help with this you can explain what did you do with > details. okay so i deleted the old repo and made a new one https://salsa.debian.org/jvk_here/python-playwright/
These are the exact command which i executed cd maintain_playwright/ 732 gbp clone https://salsa.debian.org/jvk_here/python-playwright.git 733 ls 734 cd python-playwright/ 736 gbp import-orig --uscan 737 cd .. 738 tree 740 clear 741 tree -L 1 742 cd python-playwright/ 743 dch -i this is the updated changelog jvk@debian :~/maintain_playwright/python-playwright$ cat debian/changelog python-playwright (1.56.0+ds-1) UNRELEASED; urgency=medium * Non-maintainer upload. * New upstream release -- JVK <[email protected]> Fri, 05 Dec 2025 15:33:48 +0530 python-playwright (1.55.0+ds-2) unstable; urgency=medium * Fix debian/copyright. -- Roland Mas <[email protected]> Wed, 29 Oct 2025 16:20:31 +0100 python-playwright (1.55.0+ds-1) unstable; urgency=medium [ Andreas Tille ] * Initial packaging. [ Roland Mas ] * Build on Andreas's work, many thanks. * New upstream release. -- Roland Mas <[email protected]> Wed, 22 Oct 2025 12:27:30 +0200 744 gbp import-orig 745 git push 746 history what i think is the next steps-> gbp-source (will make .dsc .changes and .tar.gz file) then sbuild -d unreleased <whatever name>.dsc will test it? if error emerges gbs pq import git checkout patch-queue/debian (changes wd) fix code git commit gbp pq export (will this push the commits?) > > > Ig it was you how told me to use git. > > I told you to use git push instead of gbp push, because gbp push is > not ouu hmm sorry > suitable for your needs. Not sure if you mean that you decided to not > use > any of the gbp tools instead. > > > And what you are telling is not written in any workflow ,why? > > I don't think this is true but you can elaborate. like you told i have manully push things , i didn't find it anywhere
