Re: Couldn't commit to pristine-tar - This doesn't look like a tar archive (continued)
Soren Stoutner <[email protected]>
| Newsgroups | gmane.linux.debian.devel.general |
|---|---|
| Organization | Debian |
| Message-ID | <3050711.e9J7NaK4W3@soren-desktop> |
On Tuesday, June 30, 2026 1:45:54 AM Mountain Standard Time Aryan Karamtoth wrote: > On 30/06/26 13:02, Julien Puydt wrote: > I use this command for all of my package updates. > > gbp import-orig --pristine-tar --uscan This package does not contain a gbp.conf. https://salsa.debian.org/ocaml-team/coq-hammer/-/tree/master/debian? ref_type=heads Usually when working with pristine-tar, I find it best to include a gbp.conf in the debian directory that enables --pristine-tar by default for anyone working on the package. Like this: https://salsa.debian.org/cryptocoin-team/electrum/-/blob/master/debian/ gbp.conf?ref_type=heads It is possible for users to have a local configuration file that enables --pristine-tar for any gbp command they run. But if not, a user would have to add --pristine-tar to every command, as Julien did above, or problems ensue. -- Soren Stoutner [email protected]
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmpEJdkACgkQwufLJ66w tgMabw/8C3C6QZywyvhaDkjuzJ0e/Lw3ehfWEk1rZXjsaYICZbL6g1wzBEmlznVy J7Jl45futKv+j4cJ3ptRpO5SqaswwlIZTLGqWLylebelOCB1/xTVsduNwdPakDZw lfnDQATbx9tbtV7Nia2eA+edv8PeXhRYIH+A/1/SiR2Rxbcn+PZSlFKtHqWIM2FV 4kT7rQc2OHAz68tzIcaIWWj0UcY5EDeUSEPRQBXdd1/HjsVHuPpwyOuBqIAXuTjU vhTaVFsAk4m1CFRXv9i1yAX3UIxeTQMampsk/TesTXt69SZtJWT/3c7zC84L7K1d xH5BEkxuLVFUTZUA6TbWnaOYIuvtE7w6xknR/ScPA0OfxdqiTFWct4hzZaiyoFW/ RugavSEDWPgojYzZDggYsiOlJa1gYD8vYF1oOQKCLtGuQWaz+B/GSxqBAmdTatWj lnGaAqtswWDte5OwDqe2KrZ8gM5dvZ4jejQbZy81mcs4hx5tpu8vMjUXOYzX8vjL dchZcpnNjAD2+e9QMhjqoR2mTEa5SYOs+N0K35wu5eS1NYKFZ6L0gsxuM6cYRLze R8xK5QPYyIdq3sS+tEWz0BVBLWh3m/cD4dhLYDKNmuV8nd0ll5Nl7pyWeE5WMx1I HG9JWoq2mBkqAlc7+AAZnB2J4zIZrUejfh/yb7Iz7uxYh+oEIrI= =z51u -----END PGP SIGNATURE-----