Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: Mattia Rizzolo Newsgroups: linux.debian.maint.python Subject: Re: Force pushing on salsa? Date: Tue, 11 Feb 2020 17:50:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Feb 11 16:46:44 2020 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.88 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, FVGT_m_MULTI_ODD=0.02, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .debian. - helo: .savidlin.mapreri. - helo-domain: .mapreri.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -3.5 Mail-Followup-To: debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="KR/qxknboQ7+Tpez" Content-Disposition: inline X-Info: Keep It Simple, Stupid. X-Operating-System: Linux, kernel 5.2.0-2-amd64, inside Debian GNU/Linux bullseye/sid sid. X-Message-Flag: WARNING!! Outlook sucks. A lot. User-Agent: Every email client sucks, this one just sucks less. X-Mailing-List: archive/latest/17930 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20200211164628.GG385407@mapreri.org Approved: robomod@news.nic.it Lines: 62 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 11 Feb 2020 17:46:28 +0100 X-Original-Message-ID: <20200211164628.GG385407@mapreri.org> X-Original-References: <1b950574-b5f7-0b77-61f1-b5a363d934c6@debian.org> Xref: csiph.com linux.debian.maint.python:12303 --KR/qxknboQ7+Tpez Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 11, 2020 at 11:34:23AM -0500, Louis-Philippe V=E9ronneau wrote: > Looking at a package recently, I saw some important mistakes and I was > wondering: would it be ok to force push to fix them? >=20 > More explicitly, the import of the new upstream version with > pristine-tar contains a bunch of errors due to a wrong manipulation. It > seems to me it would be "more clean" to start again and force push. >=20 > I know force pushing is normally frowned upon when working in a team > environment, but I haven't seen any mention of it in the Python Team's > policy. Let me keep frowing deeply. If pristine-tar data is corrupted, just use % pristine-tar commit ../foo_1.2.3.orig.tar.xz upstream/1.2.3 to update the data, without force-pushing. It's just one extra commit, so why would that be "less clean"?! The only thing I could *very frowingly* accept, is force-pushing a tag because you are doing it again. Having said that, I usually just append a number if I need to re-repack again an upstream tarball (+dfsg1, +dfsg2, etc). But you mentioned only pristine-tar, so I suppose that's not your case. --=20 regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=3Dmattia `- --KR/qxknboQ7+Tpez Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAl5C2mEACgkQCBa54Yx2 K62oxg//Yop3UtxQR5zrxhMSUouGEkyna4hNCJvZHmGL3j1v4HP6teUid4xSkKb5 1eVuCIfmPdIqTeWctJPl3C51hY4CnyL3+4MlFhAbdIb5+uAPw+1W59L70IROtsNE idYmBngWISdfxqMBFE613QdO0ksuDUAu7eZt4qIdwhZl5Lul+hhRenMaVO/r+krp cw2yNGZjOb4gjQEq44l1qwRvHaVpZn2zm+6RSaplzZK25K/9Wzus7TtG8JgcGqeW HP+yxD6NMNUXA7ln0ZPnfJxcNhJdXK+WNW/PB6P+MNvcmKi/mNNP84sQVNStbE4r gVdvwRxkGNaHqf0Z3of5hKCNNkfPS6Odw8M7V7sliV/dwY+B2pgSPKTkPXl0j3sX RPH6A6kOJCIskbN+SHkC9OwjsK3JWDaANcUg0aq5rAyBkJHKgE1pEGjGbcMY5KzZ ux4Sc2zvlOwh0aVpIG1Urq4ngZyWrlmiv6C1M35qkzyNQ4KVJnA2BV5dwLK9IVdu Yo5SOmEjVwG4FLUjnJGQnn75Lmfl1vx0khyhPFKYX8wFCkmb2zxpR10i6Sve0aZo 3Yxiwlmy0WOuUPwIeGet5Ee618CikaJ67Vmx1h1RfiRTBp0ywg5akMBveXcla81j 5u3ar7tMnf1a1ELvw+ojY8lEw1uToZsQUnOx5JMwDi0XtnwkIH0= =0AeX -----END PGP SIGNATURE----- --KR/qxknboQ7+Tpez--