On jeudi 8 mars 2018 16:37:57 CET Jan Chaloupka wrote:
> On 03/07/2018 04:07 PM, Jan Chaloupka wrote:
> >
> > Saying that, I will prepare new builds of gofed so the new spec files
> > are generated with the new macros.
>
>
> F27 gofed build:
>
On 03/07/2018 04:07 PM, Jan Chaloupka wrote:
On 03/07/2018 04:02 PM, Jan Chaloupka wrote:
On 03/07/2018 03:50 PM, Robert-André Mauchin wrote:
On mardi 6 mars 2018 12:47:40 CET Jan Chaloupka wrote:
Hi Robert-André,
thank you for your patience and all comments pointing out pieces that
Le mercredi 07 mars 2018 à 16:35 +0100, Nicolas Mailhot a écrit :
> Le mercredi 07 mars 2018 à 16:02 +0100, Jan Chaloupka a écrit :
>
> Hi,
>
> > Nicolas, can you more elaborate on that? I don't see any more reason
> > why we should block folks from relying on the new macros.
>
> IMHO they're
Le mercredi 07 mars 2018 à 16:02 +0100, Jan Chaloupka a écrit :
Hi,
> Nicolas, can you more elaborate on that? I don't see any more reason
> why we should block folks from relying on the new macros.
IMHO they're solid enough to be used in production both for binary
packages and -devel packages
On 03/07/2018 04:02 PM, Jan Chaloupka wrote:
On 03/07/2018 03:50 PM, Robert-André Mauchin wrote:
On mardi 6 mars 2018 12:47:40 CET Jan Chaloupka wrote:
Hi Robert-André,
thank you for your patience and all comments pointing out pieces that
are not working as expected.
Introduction of new
On 03/07/2018 03:50 PM, Robert-André Mauchin wrote:
On mardi 6 mars 2018 12:47:40 CET Jan Chaloupka wrote:
Hi Robert-André,
thank you for your patience and all comments pointing out pieces that
are not working as expected.
Introduction of new macros is a time-consuming process and it
On mardi 6 mars 2018 12:47:40 CET Jan Chaloupka wrote:
> Hi Robert-André,
>
> thank you for your patience and all comments pointing out pieces that
> are not working as expected.
> Introduction of new macros is a time-consuming process and it requires
> resilience so we keep up till the state
>
Hi Athos,
hope everything is fine and you have better things to do than spending
much time updating the Go spec files :)
Anything you need and/or anything that could help you to minimize your
packaging time, please, let us know :).
On 03/04/2018 08:20 PM, Nicolas Mailhot wrote:
Le samedi
On 02/27/2018 07:22 PM, Nicolas Mailhot wrote:
Le mardi 27 février 2018 à 18:34 +0100, Robert-André Mauchin a écrit :
How do we test this? I installedtho go-srpm-macros from Rawhide but it
doesn't seem to have the required macros?
Yes in rawhide go-compilers and go-srpm-macros are in an
Hi Fabio,
thank you for staying with us in the Go packaging world and for sharing
any difficulty or problem you encounter with.
I created github repository [1] where you can report all issues wrt.
macros used in Go packaging.
We are currently in a process of iterating over all the macros.
Hi Robert-André,
thank you for your patience and all comments pointing out pieces that
are not working as expected.
Introduction of new macros is a time-consuming process and it requires
resilience so we keep up till the state
where the macros are generally usable for a lot of our use cases.
Le samedi 03 mars 2018 à 11:47 -0300, Athos Ribeiro a écrit :
>
> Are there any intentions to push the macros into f28? I really liked
> the
> improvements in the spec file sizes, but porting too many packages now
> and keep them updated in both f28 and rawhide (making the branches
> completely
On Tue, Feb 27, 2018 at 07:22:42PM +0100, Nicolas Mailhot wrote:
> Le mardi 27 février 2018 à 18:34 +0100, Robert-André Mauchin a écrit :
> >
> >
> > How do we test this? I installedtho go-srpm-macros from Rawhide but it
> > doesn't seem to have the required macros?
>
> Yes in rawhide
On mardi 27 février 2018 19:39:47 CET you wrote:
> > 6) When I finally got the macros right enough for %prep, %build, and
> > %install to proceed, the build failed due to missing debuginfo files (and
> > warnings about duplicate files) - well, it's a source-only library
> > package,
> > how do I
On mardi 27 février 2018 15:49:44 CET Fabio Valentini wrote:
> Hi everybody,
>
> I've been following the (long overdue) improvements concerning go packaging
> in fedora, and since I saw that packages are starting to make use of the
> new mechanisms, I wanted to finally check it out and started
Le mardi 27 février 2018 à 18:34 +0100, Robert-André Mauchin a écrit :
>
>
> How do we test this? I installedtho go-srpm-macros from Rawhide but it
> doesn't seem to have the required macros?
Yes in rawhide go-compilers and go-srpm-macros are in an intermediary
not fully tested/integrated
On mardi 27 février 2018 16:03:36 CET Nicolas Mailhot wrote:
> Le 2018-02-27 15:49, Fabio Valentini a écrit :
>
> Hi Fabio,
>
> Thanks a lot for testing, we need more input to produce great Go
> packaging tooling.
>
>
> > I've been following the (long overdue) improvements concerning go
> >
Le 2018-02-27 15:49, Fabio Valentini a écrit :
Hi
I'll answer in more detail since I have a little more time now
2) Additionally, I wasn't able to figure out why I have to set both
"%gobaseipath" and "%provider_prefix".
That's one of the changes Jan made I don't understand either. It's
Le 2018-02-27 15:49, Fabio Valentini a écrit :
Hi Fabio,
Thanks a lot for testing, we need more input to produce great Go
packaging tooling.
I've been following the (long overdue) improvements concerning go
packaging in fedora, and since I saw that packages are starting to
make use of the
19 matches
Mail list logo
