Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Tue, Jan 28, 2020 at 6:12 PM Stasiek Michalski wrote: > > > On Tue, Jan 28, 2020 at 23:57, Dan Čermák > wrote: > > Neal Gompa writes: > > > >> On Tue, Jan 28, 2020 at 7:27 AM Pierre-Yves Chibon > >> wrote: > >>> > >>> On Fri, Jan 10, 2020 at 09:54:59PM -0500, Neal Gompa wrote: > >>> > On

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Neal Gompa writes: > On Tue, Jan 28, 2020 at 7:27 AM Pierre-Yves Chibon > wrote: >> >> On Fri, Jan 10, 2020 at 09:54:59PM -0500, Neal Gompa wrote: >> > On Fri, Jan 10, 2020 at 11:37 AM Pierre-Yves Chibon >> > wrote: >> > > >> > > >> > > The release field would need to be set by koji ignoring

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Tue, Jan 28, 2020 at 7:27 AM Pierre-Yves Chibon wrote: > > On Fri, Jan 10, 2020 at 09:54:59PM -0500, Neal Gompa wrote: > > On Fri, Jan 10, 2020 at 11:37 AM Pierre-Yves Chibon > > wrote: > > > > > > > > > The release field would need to be set by koji ignoring whatever is in > > > the spec >

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 09:54:59PM -0500, Neal Gompa wrote: > On Fri, Jan 10, 2020 at 11:37 AM Pierre-Yves Chibon > wrote: > > > > > > The release field would need to be set by koji ignoring whatever is in the > > spec > > file. How do we want to do this? > > - Based on dates? > > - Using

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Tuesday, January 21, 2020 10:24:53 AM CET Pierre-Yves Chibon wrote: > On Tue, Jan 21, 2020 at 09:36:27AM +0100, Pavel Raiskup wrote: > > On Friday, January 10, 2020 5:36:46 PM CET Pierre-Yves Chibon wrote: > > > Do we want to drop release and changelog from our spec file? > > > > No. People

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Tue, Jan 21, 2020 at 4:39 AM Pavel Raiskup wrote: > > On Tuesday, January 21, 2020 10:20:10 AM CET Vít Ondruch wrote: > > I would expect that adding some keyword such as "[skip changelog]" (there > > are > > quite commonly used similar hints for CI nowadays [1]) would instruct the > >

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Tuesday, January 21, 2020 10:20:10 AM CET Vít Ondruch wrote: > I would expect that adding some keyword such as "[skip changelog]" (there are > quite commonly used similar hints for CI nowadays [1]) would instruct the > generator to leave the second commit out of the changelog, because it does

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 1/20/20 7:03 PM, David Cantrell wrote: On Wed, Jan 15, 2020 at 04:28:56PM +0200, Panu Matilainen wrote: On 1/15/20 3:33 PM, Vít Ondruch wrote: Dne 15. 01. 20 v 13:33 Panu Matilainen napsal(a): On 1/15/20 2:13 PM, Miroslav Suchý wrote: Dne 13. 01. 20 v 14:05 Vít Ondruch napsal(a):

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Tue, Jan 21, 2020 at 09:36:27AM +0100, Pavel Raiskup wrote: > On Friday, January 10, 2020 5:36:46 PM CET Pierre-Yves Chibon wrote: > > Do we want to drop release and changelog from our spec file? > > No. People continuously tend to forget that '%changelog' is for > end-users. Especially if

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Dne 21. 01. 20 v 9:36 Pavel Raiskup napsal(a): > On Friday, January 10, 2020 5:36:46 PM CET Pierre-Yves Chibon wrote: >> Do we want to drop release and changelog from our spec file? > No. People continuously tend to forget that '%changelog' is for > end-users. Especially if some distributions

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Friday, January 10, 2020 5:36:46 PM CET Pierre-Yves Chibon wrote: > Do we want to drop release and changelog from our spec file? No. People continuously tend to forget that '%changelog' is for end-users. Especially if some distributions already claim they can live fine without %changelog...

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Mon, Jan 20, 2020 at 05:20:08PM +0100, Nils Philippsen wrote: > On Mon, 2020-01-13 at 10:34 +0100, Petr Pisar wrote: > > (2) The new values must be larger than all historical values (across > > all historical Fedora releases). That assures than a new build won't > > become obsoleted because of

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Wed, Jan 15, 2020 at 04:28:56PM +0200, Panu Matilainen wrote: On 1/15/20 3:33 PM, Vít Ondruch wrote: Dne 15. 01. 20 v 13:33 Panu Matilainen napsal(a): On 1/15/20 2:13 PM, Miroslav Suchý wrote: Dne 13. 01. 20 v 14:05 Vít Ondruch napsal(a): %changelog %include changelog +1 As I

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Mon, Jan 13, 2020 at 08:19:36AM -0600, Richard Shaw wrote: Just catching up on this thread... How about an incremental step? (I don't know how difficult it would be to implement however)... What about separating the change log to a separate file in dist-git? Something like the traditional

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Hey Petr! On Mon, 2020-01-13 at 10:34 +0100, Petr Pisar wrote: > (2) The new values must be larger than all historical values (across > all historical Fedora releases). That assures than a new build won't > become obsoleted because of a decreased release. can you clarify what you mean with

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Tue, 2020-01-14 at 00:30 +0100, David Kaufmann wrote: > The field for bodhi I usually copy from the changelog - but to be > honest I only fill it, because it's there - I don't even really know > what it is used for, except being shown on the update page. Users can read the update text with the

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 1/15/20 3:33 PM, Vít Ondruch wrote: Dne 15. 01. 20 v 13:33 Panu Matilainen napsal(a): On 1/15/20 2:13 PM, Miroslav Suchý wrote: Dne 13. 01. 20 v 14:05 Vít Ondruch napsal(a): %changelog %include changelog +1 As I pointed out in https://pagure.io/packaging-committee/pull-request/942,

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Wed, Jan 15, 2020 at 7:10 AM Miroslav Suchý wrote: > > Dne 11. 01. 20 v 3:54 Neal Gompa napsal(a): > > * %{dist}.. > > -1 > Packages with commitish in release version are usually developers snapshot. > We already have few packages with such release in Fedora, but I would dislike > to make

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Dne 15. 01. 20 v 13:33 Panu Matilainen napsal(a): > On 1/15/20 2:13 PM, Miroslav Suchý wrote: >> Dne 13. 01. 20 v 14:05 Vít Ondruch napsal(a): >>> %changelog >>> >>> %include changelog >> >> +1 >> > > As I pointed out in > https://pagure.io/packaging-committee/pull-request/942, %include is >

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 1/15/20 2:13 PM, Miroslav Suchý wrote: Dne 13. 01. 20 v 14:05 Vít Ondruch napsal(a): %changelog %include changelog +1 As I pointed out in https://pagure.io/packaging-committee/pull-request/942, %include is nasty because it breaks the stand-alone attribute of specs. There are

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Dne 13. 01. 20 v 14:05 Vít Ondruch napsal(a): > %changelog > > %include changelog +1 -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Dne 11. 01. 20 v 3:54 Neal Gompa napsal(a): > * %{dist}.. -1 Packages with commitish in release version are usually developers snapshot. We already have few packages with such release in Fedora, but I would dislike to make this standard. -- Miroslav Suchy, RHCA Red Hat, Associate Manager

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Mon, Jan 13, 2020 at 12:20:15PM +0100, Miroslav Suchý wrote: > Dne 10. 01. 20 v 18:21 Iñaki Ucar napsal(a): > > Most of the time, I end up copying the spec changelog in the commit > > message and I don't change the update template, > > +1 > Thou, occasionaly I *delete* some of those commits

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 9:37 AM Pierre-Yves Chibon wrote: > Thus our call for input to accept or reject the idea and if the former > scope/define the system. Whatever you decide, please try it out on a small set of packages that you personally maintain for a long time. This "field testing" will

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Mon, 13 Jan 2020 at 15:23, Joe Doss wrote: > > On 1/12/20 3:19 PM, Marius Schwarz wrote: > > Am 10.01.20 um 17:36 schrieb Pierre-Yves Chibon: > >> Good Morning Everyone, > >> > >> This is not a new idea, it has been presented at flock last year and > spoken > >> about on this very list this

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 1/13/20 2:47 PM, Neal Gompa wrote: changelogs often include CVE information, especially useful when the fixes are backported rather than included as part of the regular update/release process. How could the CVE info be available in the absence of changelogs? In Fedora, this information

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 1/12/20 3:19 PM, Marius Schwarz wrote: > Am 10.01.20 um 17:36 schrieb Pierre-Yves Chibon: >> Good Morning Everyone, >> >> This is not a new idea, it has been presented at flock last year and spoken >> about on this very list this fall, so I'd like to push it a little further. >> >> Do we want

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Mon, Jan 13, 2020 at 2:02 PM Przemek Klosowski via devel wrote: > > On 1/10/20 8:14 PM, Michael Catanzaro wrote: > > On Fri, Jan 10, 2020 at 9:46 pm, Richard W.M. Jones > > wrote: > >> OpenSUSE proved years and years ago that dropping %changelog is > >> possible, easy and desirable. We

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 1/10/20 8:14 PM, Michael Catanzaro wrote: On Fri, Jan 10, 2020 at 9:46 pm, Richard W.M. Jones wrote: OpenSUSE proved years and years ago that dropping %changelog is possible, easy and desirable.  We should do that IMHO. They still have %changelog at the bottom of each spec file, but as

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Le 2020-01-13 16:20, Randy Barlow a écrit : Now, we could change the policy too to get around this, but I think "git tag" is a natural way for me to indicate "I want to build and release this commit to this Fedora release". Please do not try to infer packaged commit from src.fedoraproject.org

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Mon, 2020-01-13 at 12:28 +0100, Pierre-Yves Chibon wrote: > If I tag foo 1.0 with a first changelog entry, then koji builds 1.0-1 > with that changelog. I think it would be better if the release were part of the git tag, instead of automatically generating it. Not all packages use an integer

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Mon, Jan 13, 2020 at 08:19:36AM -0600, Richard Shaw wrote: >Just catching up on this thread... >How about an incremental step? (I don't know how difficult it would be to >implement however)... This is what Vit was suggesting which seems like a very nice idea :) >What about

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Just catching up on this thread... How about an incremental step? (I don't know how difficult it would be to implement however)... What about separating the change log to a separate file in dist-git? Something like the traditional "ChangeLog"? I like to keep my spec files in sync between

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Mon, Jan 13, 2020 at 11:28:41AM +0100, Miroslav Suchý wrote: > Dne 13. 01. 20 v 10:46 Petr Pisar napsal(a): > > No, it won't as we have competing %{version}-%{release} strings among > > multiple > > packages. E.g. perl source bundles an Encode module. And we know the module > > is updated

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Am 13.01.20 um 14:05 schrieb Vít Ondruch: > While I like the annotated tag proposal, I would really appreciate if > the first step was replacing the: (..:) > %changelog > > %include changelog > > ~~~ > > where the `changelog` file would be either available with the original > changelog content

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Mon, Jan 13, 2020 at 8:07 AM Panu Matilainen wrote: > > On 1/13/20 2:44 PM, Nicolas Mailhot via devel wrote: > > Le 2020-01-13 12:52, Florian Weimer a écrit : > > > >> I have trouble matching this claim to my experience working on > >> redhat-rpm-config. Why is it painful to use Git as it was

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Dne 13. 01. 20 v 14:05 Vít Ondruch napsal(a): > Dne 12. 01. 20 v 22:56 Miro Hrončok napsal(a): >> On 10. 01. 20 17:36, Pierre-Yves Chibon wrote: >>> Is there a different approach, e.g. by using towncrier[1] or something >>> comparable, to track changes outside the spec file? >> Is the idea of

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 1/13/20 2:44 PM, Nicolas Mailhot via devel wrote: Le 2020-01-13 12:52, Florian Weimer a écrit : I have trouble matching this claim to my experience working on redhat-rpm-config.  Why is it painful to use Git as it was designed? Because redhat-rpm-config is not "using Git as it was

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Dne 12. 01. 20 v 22:56 Miro Hrončok napsal(a): > On 10. 01. 20 17:36, Pierre-Yves Chibon wrote: >> Is there a different approach, e.g. by using towncrier[1] or something >> comparable, to track changes outside the spec file? > > Is the idea of using annotated git tags abandoned altogether? > > We

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Le 2020-01-13 12:52, Florian Weimer a écrit : I have trouble matching this claim to my experience working on redhat-rpm-config. Why is it painful to use Git as it was designed? Because redhat-rpm-config is not "using Git as it was designed". It’s using git as a centralized flat and linear

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Dne 11. 01. 20 v 4:14 Neal Gompa napsal(a): > On Fri, Jan 10, 2020 at 12:52 PM Vít Ondruch wrote: >> >> Dne 10. 01. 20 v 18:33 Fabio Valentini napsal(a): >> >> On Fri, Jan 10, 2020, 17:37 Pierre-Yves Chibon wrote: >>> Good Morning Everyone, >>> >>> This is not a new idea, it has been presented

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

* Nicolas Mailhot via devel: > Le vendredi 10 janvier 2020 à 17:36 +0100, Pierre-Yves Chibon a écrit : >> Good Morning Everyone, >> >> This is not a new idea, it has been presented at flock last year and >> spoken >> about on this very list this fall, so I'd like to push it a little >> further.

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 13. 01. 20 12:40, Jun Aruga wrote: When removing the changelog in a spec file, users (not package maintainers) using this command are disappointed? ``` $ rpm -q --changelog python3 * Tue Oct 15 2019 Miro Hrončok - 3.7.5-1 - Update to 3.7.5 ... ``` No, this would still work. It would be

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 13. 01. 20 12:28, Pierre-Yves Chibon wrote: On Sun, Jan 12, 2020 at 10:56:00PM +0100, Miro Hrončok wrote: On 10. 01. 20 17:36, Pierre-Yves Chibon wrote: Is there a different approach, e.g. by using towncrier[1] or something comparable, to track changes outside the spec file? Is the idea

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

When removing the changelog in a spec file, users (not package maintainers) using this command are disappointed? ``` $ rpm -q --changelog python3 * Tue Oct 15 2019 Miro Hrončok - 3.7.5-1 - Update to 3.7.5 ... ``` -- Jun | He - His - Him ___ devel

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Le 2020-01-13 12:07, Pierre-Yves Chibon a écrit : Hi, I don't quite see how it conflicts with it either. You may end up having foo-1.0-42 in copr and foo-1.0-32 in koji which would lead to a foo-1.0-32 (or -39) at the next build, but I'm not seeing how it's a problem per say. Correct

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Sun, Jan 12, 2020 at 10:56:00PM +0100, Miro Hrončok wrote: > On 10. 01. 20 17:36, Pierre-Yves Chibon wrote: > > Is there a different approach, e.g. by using towncrier[1] or something > > comparable, to track changes outside the spec file? > > Is the idea of using annotated git tags abandoned

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Dne 10. 01. 20 v 18:21 Iñaki Ucar napsal(a): > Most of the time, I end up copying the spec changelog in the commit > message and I don't change the update template, +1 Thou, occasionaly I *delete* some of those commits as they are unnessary in changelog. E.g.: * typo fix * revert of *

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 09:18:35PM +0100, Nicolas Mailhot via devel wrote: > Le vendredi 10 janvier 2020 à 20:53 +0100, Fabio Valentini a écrit : > > > > You can never expect our tooling to do "magic" (TM) and work "just > > right", no matter which Versions and Releases and Epochs of packages > >

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Le 2020-01-13 11:28, Miroslav Suchý a écrit : Dne 13. 01. 20 v 10:46 Petr Pisar napsal(a): No, it won't as we have competing %{version}-%{release} strings among multiple packages. E.g. perl source bundles an Encode module. And we know the module is updated frequenly on CPAN. Thus we build

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Dne 13. 01. 20 v 10:46 Petr Pisar napsal(a): > No, it won't as we have competing %{version}-%{release} strings among multiple > packages. E.g. perl source bundles an Encode module. And we know the module > is updated frequenly on CPAN. Thus we build perl-Encode-V1-R1 from perl.spec, > then we

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Le 2020-01-13 11:01, Panu Matilainen a écrit : You keep saying that, but maybe you were not involved with redhat-rpm-config back when it was that way. It was the most hideous piece of package I had ever worked with, because the model of external tarballs is just absurd and does not work at all

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 1/10/20 7:35 PM, Nicolas Mailhot via devel wrote: Dropping changelog is easy. Since we have a clean separation of spec repo (src.fedoraproject.org) and project repo (pagure, gitlab or elsewhere) the spec should just be assembled from all the src.fedoraproject.org commit messages not present

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 10:14:39PM -0500, Neal Gompa wrote: > On Fri, Jan 10, 2020 at 12:52 PM Vít Ondruch wrote: > > Dne 10. 01. 20 v 18:33 Fabio Valentini napsal(a): > > > What about "number of commits since last version update" (possibly > > > tagged in git)? That should encompass the

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 05:36:46PM +0100, Pierre-Yves Chibon wrote: > > The release field would need to be set by koji ignoring whatever is in the > spec file. How do we want to do this? > - Based on dates? > - Using an always increasing integer? > - Using the number of successful builds

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 10.01.2020 17:36, Pierre-Yves Chibon wrote: > Do we want to drop release and changelog from our spec file? YES. Changelogs can be automatically generated from Fedora Git SCM commits. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 10. 01. 20 17:36, Pierre-Yves Chibon wrote: Is there a different approach, e.g. by using towncrier[1] or something comparable, to track changes outside the spec file? Is the idea of using annotated git tags abandoned altogether? We could even create a tool that would "prefill" a template

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On 12. 01. 20 22:19, Marius Schwarz wrote: Am 10.01.20 um 17:36 schrieb Pierre-Yves Chibon: Good Morning Everyone, This is not a new idea, it has been presented at flock last year and spoken about on this very list this fall, so I'd like to push it a little further. Do we want to drop release

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Sun, Jan 12, 2020 at 4:20 PM Marius Schwarz wrote: > > Am 10.01.20 um 17:36 schrieb Pierre-Yves Chibon: > > Good Morning Everyone, > > > > This is not a new idea, it has been presented at flock last year and spoken > > about on this very list this fall, so I'd like to push it a little further.

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Am 10.01.20 um 17:36 schrieb Pierre-Yves Chibon: > Good Morning Everyone, > > This is not a new idea, it has been presented at flock last year and spoken > about on this very list this fall, so I'd like to push it a little further. > > Do we want to drop release and changelog from our spec file?

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Sun, Jan 12, 2020 at 04:38:55AM -0500, Neal Gompa wrote: > On Sun, Jan 12, 2020 at 4:03 AM Nicolas Mailhot via devel > wrote: > > > > Le samedi 11 janvier 2020 à 13:09 -0500, Neal Gompa a écrit : > > > > > > The only reason I mentioned it is because since we distro-sync > > > between > > >

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Sun, Jan 12, 2020 at 4:03 AM Nicolas Mailhot via devel wrote: > > Le samedi 11 janvier 2020 à 13:09 -0500, Neal Gompa a écrit : > > > > The only reason I mentioned it is because since we distro-sync > > between > > releases, it doesn't actually matter as much as it used to. > > rawhide does

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Le samedi 11 janvier 2020 à 13:09 -0500, Neal Gompa a écrit : > > The only reason I mentioned it is because since we distro-sync > between > releases, it doesn't actually matter as much as it used to. rawhide does not distro-sync (and some may say that rawhide does not matter, but early problem

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Sat, Jan 11, 2020 at 12:38 PM Zbigniew Jędrzejewski-Szmek wrote: > > On Fri, Jan 10, 2020 at 09:54:59PM -0500, Neal Gompa wrote: > > On Fri, Jan 10, 2020 at 11:37 AM Pierre-Yves Chibon > > wrote: > > > > > > > > > The release field would need to be set by koji ignoring whatever is in > > >

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 09:54:59PM -0500, Neal Gompa wrote: > On Fri, Jan 10, 2020 at 11:37 AM Pierre-Yves Chibon > wrote: > > > > > > The release field would need to be set by koji ignoring whatever is in the > > spec > > file. Yes, please!!! This is a relatively small step that will make so

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 12:52 PM Vít Ondruch wrote: > > > Dne 10. 01. 20 v 18:33 Fabio Valentini napsal(a): > > On Fri, Jan 10, 2020, 17:37 Pierre-Yves Chibon wrote: >> >> Good Morning Everyone, >> >> This is not a new idea, it has been presented at flock last year and spoken >> about on this

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 11:37 AM Pierre-Yves Chibon wrote: > > > The release field would need to be set by koji ignoring whatever is in the > spec > file. How do we want to do this? > - Based on dates? > - Using an always increasing integer? > - Using the number of successful builds since

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 8:20 PM Michael Catanzaro wrote: > > On Fri, Jan 10, 2020 at 9:46 pm, Richard W.M. Jones > wrote: > > OpenSUSE proved years and years ago that dropping %changelog is > > possible, easy and desirable. We should do that IMHO. > > They still have %changelog at the bottom of

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 9:46 pm, Richard W.M. Jones wrote: OpenSUSE proved years and years ago that dropping %changelog is possible, easy and desirable. We should do that IMHO. They still have %changelog at the bottom of each spec file, but as the last line of the file. The actual changelog

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 05:36:46PM +0100, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > This is not a new idea, it has been presented at flock last year and spoken > about on this very list this fall, so I'd like to push it a little further. > > Do we want to drop release and changelog

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Le vendredi 10 janvier 2020 à 20:53 +0100, Fabio Valentini a écrit : > > You can never expect our tooling to do "magic" (TM) and work "just > right", no matter which Versions and Releases and Epochs of packages > are available from third-party repos and coprs. Yes, sure, but the current way we

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 6:36 PM Nicolas Mailhot via devel wrote: > > Le vendredi 10 janvier 2020 à 17:36 +0100, Pierre-Yves Chibon a écrit : > > Good Morning Everyone, > > > > This is not a new idea, it has been presented at flock last year and > > spoken > > about on this very list this fall, so

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020 at 6:52 PM Vít Ondruch wrote: > > > Dne 10. 01. 20 v 18:33 Fabio Valentini napsal(a): > > On Fri, Jan 10, 2020, 17:37 Pierre-Yves Chibon wrote: >> >> Good Morning Everyone, >> >> This is not a new idea, it has been presented at flock last year and spoken >> about on this

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Dne 10. 01. 20 v 18:33 Fabio Valentini napsal(a): > On Fri, Jan 10, 2020, 17:37 Pierre-Yves Chibon > wrote: > > Good Morning Everyone, > > This is not a new idea, it has been presented at flock last year > and spoken > about on this very list this

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

Le vendredi 10 janvier 2020 à 17:36 +0100, Pierre-Yves Chibon a écrit : > Good Morning Everyone, > > This is not a new idea, it has been presented at flock last year and > spoken > about on this very list this fall, so I'd like to push it a little > further. > > Do we want to drop release and

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, Jan 10, 2020, 17:37 Pierre-Yves Chibon wrote: > Good Morning Everyone, > > This is not a new idea, it has been presented at flock last year and spoken > about on this very list this fall, so I'd like to push it a little further. > > Do we want to drop release and changelog from our spec

Re: What would it take to drop release and changelog from our spec files? (and do we want to?)

On Fri, 10 Jan 2020 at 17:45, Pierre-Yves Chibon wrote: > > With the changelog it becomes a little bit more tricky. > We currently have 3 changelogs in Fedora with 3 different target audience > (this > is how I understand them): > - One for the files in the git repository, meant to be

What would it take to drop release and changelog from our spec files? (and do we want to?)

Good Morning Everyone, This is not a new idea, it has been presented at flock last year and spoken about on this very list this fall, so I'd like to push it a little further. Do we want to drop release and changelog from our spec file? If we do, how would this work? The release field would need