Re: RFC: BugURL in packages

2018-02-16 Thread Jason L Tibbitts III
So basically, koji has a list of macros (hardcoded in koji/__init__.py) which unfortunately carries the comment: #XXX - this needs to be configurable Those get turned into config_opts['macros']['%_foo']['whatever'] directives in the generated mock config. Some of those macros (%vendor, %pack

Re: RFC: BugURL in packages

2018-02-16 Thread Jason L Tibbitts III
Or you can just add this: config_opts['macros']['%bugurl'] = 'http://bugz.fedoraproject.org/%name' to the mock site-defaults.cfg on the builders. For some reason I thought that we couldn't depend on %name to be stable in the case of subpackages but it appears to not matter. - J< __

Re: RFC: BugURL in packages

2018-02-16 Thread Kevin Fenzi
On 02/16/2018 02:48 PM, Jason L Tibbitts III wrote: > Or you can just add this: > > config_opts['macros']['%bugurl'] = 'http://bugz.fedoraproject.org/%name' > > to the mock site-defaults.cfg on the builders. For some reason I > thought that we couldn't depend on %name to be stable in the case of

Re: [HEADS UP] Replacing %post/%postun -p /sbin/ldconfig

2018-02-16 Thread Remi Collet
Le 16/02/2018 à 15:18, Mark Wielaard a écrit : > I had to tweak it a little though so the spec could still be build > older RHEL or Fedora (I reuse the spec to build on RHEL and with SCL). > Maybe something like the following is better for people who have a spec > file they might reuse on systems

Re: Removal of BuildRoot

2018-02-16 Thread Pierre-Yves Chibon
On Fri, Feb 16, 2018 at 06:48:17PM +, Tom Hughes wrote: > On 16/02/18 18:26, David Sommerseth wrote: > > > But my "worst" example was probably the openvpn package I'm now in charge > > for > > (and I am a core upstream developer for that project as well). But it > > didn't > > take that muc

Re: Removal of BuildRoot

2018-02-16 Thread Pavel Raiskup
On Friday, February 16, 2018 7:48:17 PM CET Tom Hughes wrote: > On 16/02/18 18:26, David Sommerseth wrote: > > > But my "worst" example was probably the openvpn package I'm now in charge > > for > > (and I am a core upstream developer for that project as well). But it > > didn't > > take that m

<    1   2