This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients benjamin.peterson, doko, georg.brandl, larry, matrixise, ned.deily, vstinner
Date 2017-07-25.23:38:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501025928.75.0.921697811894.issue31036@psf.upfronthosting.co.za>
In-reply-to
Content
If we provide a prebuilt Misc/NEWS in tarball, if Makefile doesn't need blurb if Misc/NEWS already exists, doko's issue is fixed: Debian package builder will not need blurb anymore (PR 2874).


> If the upstream patches are extracted from GitHub PRs, then they'd presumably have files in Misc/NEWS.d.  You could just ignore them.

If a vendor don't want to rely on blurb, I think that it's acceptable tradeoff.

Usually, each backported change is documented in a vendor specific changelog anyway.

Maybe tomorrow, some Linux vendors will start using blurb, but I suggest to work step by step, and first focus on the Python 3.5 "regression" fixed by PR 2874.

--

> But you could run "blurb split", breaking Misc/NEWS into constituent files in Misc/NEWS.d, and then "blurb merge", rebuilding Misc/NEWS from those constituent files in Misc/NEWS.d.

I'm not following you. If you want to rebuild Misc/NEWS, why not just removing Misc/NEWS and then run blurb merge?

I expect that in a tarball, Misc/NEWS and Misc/NEWS.d contain exactly the same entries.
History
Date User Action Args
2017-07-25 23:38:48vstinnersetrecipients: + vstinner, georg.brandl, doko, larry, benjamin.peterson, ned.deily, matrixise
2017-07-25 23:38:48vstinnersetmessageid: <1501025928.75.0.921697811894.issue31036@psf.upfronthosting.co.za>
2017-07-25 23:38:48vstinnerlinkissue31036 messages
2017-07-25 23:38:48vstinnercreate