Le dimanche 19 juillet 2020 à 10:39 -0700, Kevin Fenzi a écrit :
> On Mon, Jul 13, 2020 at 10:17:11AM +0200, Nicolas Mailhot via devel
> wrote:
> > Tough it is a litteral key = value file with no fancy formatting
> > nor
> > even ini-like sections, and a handful of variables. Very boring
> > KISS
On Mon, Jul 13, 2020 at 10:17:11AM +0200, Nicolas Mailhot via devel wrote:
> Le dimanche 12 juillet 2020 à 13:07 -0700, Kevin Fenzi a écrit :
> > On Sun, Jul 05, 2020 at 02:15:23PM +0200, Nicolas Mailhot via devel
> > wrote:
> > >
> > > This is now done in the latest code refresh and in the test
On Thu, 2020-07-02 at 16:31 +, Nicolas Mailhot via devel wrote:
>
> Le July 2, 2020 2:47:49 PM UTC, Vitaly Zaitsev via devel <
> devel@lists.fedoraproject.org> a écrit :
> > On 02.07.2020 11:27, Nicolas Mailhot wrote:
> > > Why? Koji schedules a build. The build registers its own build
> > >
Le dimanche 12 juillet 2020 à 13:07 -0700, Kevin Fenzi a écrit :
> On Sun, Jul 05, 2020 at 02:15:23PM +0200, Nicolas Mailhot via devel
> wrote:
> >
> > This is now done in the latest code refresh and in the test copr
> >
On Sun, Jul 12, 2020, at 4:07 PM, Kevin Fenzi wrote:
> On Sun, Jul 05, 2020 at 02:15:23PM +0200, Nicolas Mailhot via devel wrote:
> > Le mercredi 01 juillet 2020 à 12:27 +0200, Dominik 'Rathann'
> > Mierzejewski a écrit :
> > >
> > > > To get beautiful changelogs, you also need to add
> > > >
>
On Sun, Jul 05, 2020 at 02:15:23PM +0200, Nicolas Mailhot via devel wrote:
> Le mercredi 01 juillet 2020 à 12:27 +0200, Dominik 'Rathann'
> Mierzejewski a écrit :
> >
> > > To get beautiful changelogs, you also need to add
> > >
> > >
> > > %buildsys_name Your name
> > > %buildsys_email Your
Le mercredi 01 juillet 2020 à 12:27 +0200, Dominik 'Rathann'
Mierzejewski a écrit :
>
> > To get beautiful changelogs, you also need to add
> >
> >
> > %buildsys_name Your name
> > %buildsys_email Your email
> >
> >
> > in ~/.rpmmacros
>
> What about having one macro called
On Thu, Jul 02, 2020 at 03:44:51PM +0200, Nicolas Mailhot via devel wrote:
> Le 2020-07-02 15:11, Kamil Dudka a écrit :
> >On Thursday, July 2, 2020 1:02:05 PM CEST Nicolas Mailhot via
> >devel wrote:
> >>If there is buy-in, it will be implemented by goodwill people.
> >>If there
> >>is no buy-in,
Le 2020-07-02 15:11, Kamil Dudka a écrit :
On Thursday, July 2, 2020 1:02:05 PM CEST Nicolas Mailhot via devel
wrote:
If there is buy-in, it will be implemented by goodwill people. If
there
is no buy-in, it won’t, normal community development process. Put
yourself in the category you want to
Le July 2, 2020 2:47:49 PM UTC, Vitaly Zaitsev via devel
a écrit :
>On 02.07.2020 11:27, Nicolas Mailhot wrote:
>> Why? Koji schedules a build. The build registers its own build date
>in
>> the produced packages. Koji decides to keep and commit the result, or
>> drop it (scratch build, failed
On 02.07.2020 11:27, Nicolas Mailhot wrote:
> Why? Koji schedules a build. The build registers its own build date in
> the produced packages. Koji decides to keep and commit the result, or
> drop it (scratch build, failed side tag, whatever). Koji is still in
> charge, the bumping is just
On Thursday, July 2, 2020 1:02:05 PM CEST Nicolas Mailhot via devel wrote:
> If there is buy-in, it will be implemented by goodwill people. If there
> is no buy-in, it won’t, normal community development process. Put
> yourself in the category you want to be in, your choice, not mine.
I believe
Le 2020-07-02 12:42, Igor Raits a écrit :
So who is going to implement necessary changes in mock and koji for
this proposal to be complete?
If there is buy-in, it will be implemented by goodwill people. If there
is no buy-in, it won’t, normal community development process. Put
yourself in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 2020-07-02 at 12:20 +0200, Nicolas Mailhot via devel wrote:
> Le 2020-07-02 11:59, Florian Weimer a écrit :
> > * Nicolas Mailhot via devel:
> >
> > > Le 2020-07-02 09:59, Vitaly Zaitsev via devel a écrit :
> > > > On 02.07.2020 07:35,
Le 2020-07-02 11:59, Florian Weimer a écrit :
* Nicolas Mailhot via devel:
Le 2020-07-02 09:59, Vitaly Zaitsev via devel a écrit :
On 02.07.2020 07:35, Nicolas Mailhot via devel wrote:
The detached changelog is just one more file in SRPM sources, which
is
modified by rpmbuild at `%build`
* Nicolas Mailhot via devel:
> Le 2020-07-02 09:59, Vitaly Zaitsev via devel a écrit :
>> On 02.07.2020 07:35, Nicolas Mailhot via devel wrote:
>>> The detached changelog is just one more file in SRPM sources, which is
>>> modified by rpmbuild at `%build` time with other files rpmbuild
>>>
Le 2020-07-02 11:38, Igor Raits a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 2020-07-02 at 11:27 +0200, Nicolas Mailhot via devel wrote:
Le 2020-07-02 09:59, Vitaly Zaitsev via devel a écrit :
> On 02.07.2020 07:35, Nicolas Mailhot via devel wrote:
> > The detached
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 2020-07-02 at 11:27 +0200, Nicolas Mailhot via devel wrote:
> Le 2020-07-02 09:59, Vitaly Zaitsev via devel a écrit :
> > On 02.07.2020 07:35, Nicolas Mailhot via devel wrote:
> > > The detached changelog is just one more file in SRPM
Le 2020-07-02 11:17, Nicolas Mailhot via devel a écrit :
This may seem a bit complex and convoluted, but that’s because
autobumping
https://fedoraproject.org/wiki/Changes/rpm_level_auto_release_and_changelog_bumping
is a small addition over the big %auto_macros change.
Le 2020-07-02 09:59, Vitaly Zaitsev via devel a écrit :
On 02.07.2020 07:35, Nicolas Mailhot via devel wrote:
The detached changelog is just one more file in SRPM sources, which is
modified by rpmbuild at `%build` time with other files rpmbuild
modifies.
I don't like that. %changelog should
* Nicolas Mailhot:
> Le 2020-07-02 09:52, Florian Weimer a écrit :
>> * Nicolas Mailhot via devel:
>>
How do I let rpm generate the changelog automatically?
>>>
>>> This feature is not changelog generation, just changelog bumping on
>>> build events. You still need some other method to put
Le 2020-07-02 09:52, Florian Weimer a écrit :
* Nicolas Mailhot via devel:
How do I let rpm generate the changelog automatically?
This feature is not changelog generation, just changelog bumping on
build events. You still need some other method to put non-build events
in the changelog.
On 02.07.2020 07:35, Nicolas Mailhot via devel wrote:
> The detached changelog is just one more file in SRPM sources, which is
> modified by rpmbuild at `%build` time with other files rpmbuild
> modifies.
I don't like that. %changelog should be generated automatically on Koji
side.
--
* Nicolas Mailhot via devel:
>> How do I let rpm generate the changelog automatically?
>
> This feature is not changelog generation, just changelog bumping on
> build events. You still need some other method to put non-build events
> in the changelog.
What is “changelog bumping”? Why is it
Le mercredi 01 juillet 2020 à 23:48 +0200, Dan Čermák a écrit :
> Hi Nicolas,
Hi Dan
> This is a system-wide change because all packages build with
> > redhat-rpm-config, but it only concerns packages that opted to use
> > this part of redhat-rpm-config (auto framework).
> >
> > The change will
Hi Nicolas,
Ben Cotton writes:
> https://fedoraproject.org/wiki/Changes/rpm_level_auto_release_and_changelog_bumping
>
> == Summary ==
>
> redhat-rpm-config will be updated so users of the auto framework get
> automated release and changelog bumping.
>
> == Owner ==
>
> * Name: [[User:nim|
On Tuesday, 30 June 2020 at 21:19, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/rpm_level_auto_release_and_changelog_bumping
>
> == Summary ==
>
> redhat-rpm-config will be updated so users of the auto framework get
> automated release and changelog bumping.
>
> == Owner ==
>
> *
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, 2020-06-30 at 15:19 -0400, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/rpm_level_auto_release_and_changelog_bumping
>
> == Summary ==
>
> redhat-rpm-config will be updated so users of the auto framework get
> automated
28 matches
Mail list logo
