[01:35] <arraybolt3> What exactly is it that might trigger debuild to decide to pack the .git folder into a source tarball when building a native source package?
[01:35] <arraybolt3> I have two native packages that both use Git for version control, where the .git folder is directly in with the rest of the code, in the same subdirectory as the `debian` directory. One of them, when built, correctly excludes the .git dir, the other one incorrectly includes it, meaning I'm accidentally uploading entire Git repos when doing a package upload :P
[02:15] <sergiodj> arraybolt3: "d/source/options" probably
[02:17] <arraybolt3> what's weird is that the package that works just fine doesn't even have that file. But that does sound promising, so I'll look into it.
[02:55] <vorlon> @pilot out
[03:18] <arraybolt3> oh... I think I found the culprit.
[03:18] <arraybolt3> I have a d/source/options file in the offending repository, and it had a tarignore line in it that probably overrode the good one.
[03:18] <arraybolt3> yep, that fixed it
[05:25] <billchenchina> Still trying to draw someone's attention on snap-store-desktop.. https://bugs.launchpad.net/snap-store-desktop/+bug/2049032
[05:25] -ubottu:#ubuntu-devel- Launchpad bug 2049032 in snap-store-desktop "Backport patch to avoid traffic spikes to mirror infrastructure" [Undecided, New]
[06:30] <amurray> billchenchina: the desktop team manages that - might be worth raising over in #ubuntu-desktop
[07:03] <billchenchina> Thanks amurray!
[07:10] <damonlynch_> enr0n, thanks for pointing me in the direction of a schroot/sbuild setup! After struggling with trying to back port some Python packages from Noble to Jammy, I've realized it's very difficult to do. Working with frozen distro packages is totally different from working with Python's PyPi!
[22:36] <sudip> can anyone please retrigger a ppc64el build of hexchat in Noble..
[23:03] <jbicha> sudip: done