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
> > > 
> > > <pre>
> > > %buildsys_name  Your name
> > > %buildsys_email Your email
> > > </pre>
> > > 
> > > in ~/.rpmmacros
> > 
> > What about having one macro called %buildsys_packager instead of two?
> > You're always using them together, anyway. It'd be similar to the
> > existing %packager macro, too.
> This is now done in the latest code refresh and in the test copr
> https://src.fedoraproject.org/fork/nim/rpms/redhat-rpm-config/c/bc4e6a79355f3a2b73abeea7e5c0e1f53b09579e?branch=forge-with-patches-auto-call-auto-changelog-auto-srpm-bump
> https://copr.fedorainfracloud.org/coprs/nim/refactoring-forge-patches-auto-call-bump-changelog-fonts/builds/
> I fleshed out the change page a little too
> https://fedoraproject.org/wiki/Changes/rpm_level_auto_release_and_changelog_bumping

So I finally carved out a few minutes to look at this, but... 

seems to not exist? Is that some copr issue?

Looking in the src.rpms I see some of the files I want to look at are
oddly empty? 

➜  ~ od -c rpmbuild/SOURCES/buildsys.conf
0000000                                                      \n

Is that because it's the 'before' src.rpm without the version
information injected yet? Might be nice for these files to have a small
doc block at the top? Or at least the wiki page could explain each file,
whats in it and whats the format for it. 

I really dislike having a second commit to say 'yes, this build was the
last one'. Could you generate that info in advance and just commit it
before the build? ie, do your update/changes, test it, then run
something 'fedpkg build'? that just fills the things and lets you commit
them than requests the build?

I'm sure there's a ton more here... but thats what I had time for today. 


Attachment: signature.asc
Description: PGP signature

devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 

Reply via email to