[06:42] <sosodank> hey there. i'm an upstream software author and also a debian maintainer, and i package my own stuff for debian. during one of these long debian freeze periods, does ubuntu accept new versions of packages that it pulls down from debian?
[06:42] <sosodank> i.e. i'm uploading new versions to debian unstable, but i don't believe that flows to ubuntu via any mechanism
[06:43] <sosodank> i'd like ubuntu's dev channel to be getting new versions...is there any way to do that (without being an ubuntu developer)?
[06:44] <sosodank> or is that a meaningless question, and there is no real ubuntu dev channel during debian freeze, at least one any users run
[07:35] <JanC> https://wiki.ubuntu.com/SyncRequestProcess might be useful
[07:35] <JanC> sosodank: ^
[07:38] <JanC> maybe https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers also
[07:55] <sosodank> ohhhhhhhhh and this can pull down from sid, great, yeah that's exactly what i need
[07:55] <sosodank> ok sorry i had used it once before, but it was to work around ubuntu freeze
[07:55] <sosodank> awesome. debian freeze is almost over, but i'll remember this, thanks!
[08:00] <mitya57> sosodank: Until August 19 (Debian Import Freeze), packages from sid are synced automatically unless they were modified in Ubuntu.
[08:01] <mitya57> Check https://launchpad.net/ubuntu/+source/SOURCE_PKG_NAME to see if your upload has already been synced into Ubuntu.
[10:22] <sosodank> oh hey, there it is in impish
[10:23] <sosodank> alright, well apologies for thoroughly wasting everyone's time
[10:23] <sosodank> and appreciate the pointers to docs i ought have been more familiar with
[12:41] <TJ-> before I hit the shell/manual track, is there existing tooling/workflow to speed up rebasing a package on latest upstream (git)? e.g., starting from upstream, dropping in the last ./debian/ directory, and figuring out which ./debian/patches/ are still required, which need modifications, which can be dropped ?
[12:47] <TJ-> Got 220 patches to work though!
[12:48] <rbasak> You might find "gbp pq" helpful
[12:48] <rbasak> Collapse the quilt patches into git, then use git rebase. Then you get git's conflict resolution to sort out the patch set against the new upstream
[12:48] <rbasak> And finally, when done, export them back out into quilt
[12:50] <TJ-> rbasak: that looks promising - reading up on it. I'm forward-porting the patches from grub 2.04 to upstream 2.06 :)
[12:51] <rbasak> TJ-: grub2 packaging in Debian uses git-dpm I think
[12:51] <rbasak> Which is another way of using git to manage the patchset
[12:51] <TJ-> there's shortcuts for patches from upstream via checking their git commit IDs
[12:51] <rbasak> You might find it easier to integrate with that
[12:52] <TJ-> rbasak: yes, it does, I've been figuring git-dpm out too but not discovered a semi-automated way to do the initial "what needs fixing" analysis
[16:40] <cjwatson> TJ-: with git-dpm you just rebase on upstream and let git do a lot of the hard work.  Certainly don't do it by copying debian directories around by hand - that's going about things the hard way
[16:40] <cjwatson> git will automatically drop patches that are trivially already applied and such
[16:41] <cjwatson> I expect to be doing this for unstable after bullseye releases, and then stepping up the task of looking for a new maintainer
[16:44] <TJ-> cjwatson: thanks for the advice. I'm doing this to get the TFTP support for grub.cfg-$MACADDRESS mostly
[16:45] <cjwatson> You could also find an upstream patch and cherry-pick it, which will likely be quite a lot less work if you just have a particular goal like that in mind
[16:45] <cjwatson> or patches
[16:45] <TJ-> I did think of that, but seeing so many new goodies in upstream, I thought its worth doing this properly :)
[16:46] <TJ-> plus I can finally get around to working my own stand-alone patches into it :)