Re: Orphaned a lot of (mostly) Go packages owned by @fpokorny

> I you want all your golang packages reassigned to eclipseo, all you need is > to tell me to do it and I'll do it. That would be great. By all means. Thank you. Also, thank you eclipseo for taking care of the packages. Jan ___ devel mailing list --

Re: Orphaned a lot of (mostly) Go packages owned by @fpokorny

Hi Robert-André, Checking the consul it looks like I need to create a ticket for all orphaned package to change their point of contact. Assuming the same holds for all other orphaned packages one ticket with request to change their PoC is more practical than creating one for each. Feel free to

Re: PSA: builds using forge macros with tags broken on rawhide

Nicolas, On 10/22/2018 10:00 AM, Nicolas Mailhot wrote: Le lundi 22 octobre 2018 à 00:31 +0200, Robert-André Mauchin a écrit : Yeah all "gosetup -q" (which is gofed default) are broken because of your commit: Well I know no such a thing, there was never any gosetup macro in the macro set,

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

On 06/30/2018 05:05 PM, Nicolas Mailhot wrote: Le samedi 30 juin 2018 à 14:22 +0200, Tomasz Torcz a écrit : BTW, kubernetes package is quite pathological. Installing it brings kubernetes-master, which contains following four binaries: -rwxr-xr-x. 3 root root 152M 04-26 11:34

Re: Spring cleaning my golang packages (orphaning now unused stuff)

On 03/12/2018 02:13 PM, Fabio Valentini wrote: On Mon, Mar 12, 2018 at 2:03 PM, Jan Chaloupka <jchal...@redhat.com> wrote: Hi Fabio, On 03/07/2018 08:29 PM, Fabio Valentini wrote: Hi everybody, I'm going to orphan some of my golang packages that were initially pulled in by syn

Re: Spring cleaning my golang packages (orphaning now unused stuff)

Hi Fabio, On 03/07/2018 08:29 PM, Fabio Valentini wrote: Hi everybody, I'm going to orphan some of my golang packages that were initially pulled in by syncthing as dependencies, but have been dropped as dependencies again (... don't ask. golang people produce dependencies like rabbits make

Re: Trying out More Go Packaging: Bugs and Questions

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

Re: Trying out More Go Packaging: Bugs and Questions

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

Re: Trying out More Go Packaging: Bugs and Questions

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

Re: Re: Re: Trying out More Go Packaging: Bugs and Questions

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

Re: Re: Trying out More Go Packaging: Bugs and Questions

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

Re: Trying out More Go Packaging: Bugs and Questions

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.

Re: Trying out More Go Packaging: Bugs and Questions

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.

BuildError: package PKGNAME not in list for tag f29-pending

Hi, anyone knows cause of the build error message? Getting the message for 70 Go packages when building for rawhide. Regards Jan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Proposed Fedora packaging guideline: More Go packaging

Hi Nicolas, before I start arguing, I appreciate all your hard work on improving the Go guidelines, spending so much time explaining reasoning behind your decision. Also appreciating the effort on making the life easier for packagers, not just in the Go land, but throughout the distribution

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

On 06/13/2017 12:38 AM, t...@fedoraproject.org wrote: In preparation for the Final Freeze on 2017-06-27 Release Engineering will retire all packages in Branched with broken dependencies and all packages depending on these. If you get this e-mail directly this affects at least one of your

Re: Orphaned Packages in branched (2016-05-18)

On 05/18/2016 11:01 PM, opensou...@till.name wrote: The following packages have broken dependencies and will be retired on 2016-05-31 (Final Freeze for Fedora 24) unless someone fixes them. If you know for sure that the package should be retired, please do so now with a proper reason:

Re: What branches are under Go pressure. Did we forget about epel7?

CC'ing packaging@ On 05/03/2016 07:02 PM, Jan Chaloupka wrote: Hi, Since F17, golang started to get attention in Fedora distribution. Long way was travelled since with currently activelly maintaining f22+ and el6 branches. The number of Go projects packaged in Fedora grown to more than 250

What branches are under Go pressure. Did we forget about epel7?

ess nights. Let's continue in the great work we have done so far. [1] https://github.com/gofed/gofed Kind regards Jan Chaloupka -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: two identical package

On 04/05/2016 12:26 AM, Ilia Gradina wrote: Thanks, but not working( output: / [ilgrad@x230 rubygem-connection-pool]$ fedpkg retire "Renamed to bar" This can be done only by maintainer with correct rights. You don't have permission to do that as the error message says.

Help with testing current kubernetes for f23

Hi, it has been a while since kubernetes was pushed to f23 stable repository. This is the first suitable build after more than half a year. Any help with testing and adding positive karmas is appreciated. Update is located here [1]. [1]

Golang packaging: now and the future

Hi guys, at the moment there is approximately 250 packages shipping projects written in go. In general, each project has its own set of dependencies and provided import paths (golang packages). As usually each package has four active branches. Thus, we are dealing with approximately 1000 spec

Re: The %license property is now supported in EPEL6

Great!!! Thanks for the good news On 01/20/2016 10:09 PM, Jason L Tibbitts III wrote: Just a note that it EPEL6 no longer requires you to include the definition of %license property; you can use it freely in your %files list as you would in EPEL7 or Fedora. It simply maps to %doc as it would

Re: packaging golang guidelines (like etcd, consul)

On 11/16/2015 11:10 AM, Muayyad AlSadi wrote: On Mon, Nov 16, 2015 at 10:28 AM, Jan Chaloupka <jchal...@redhat.com <mailto:jchal...@redhat.com>> wrote: *.src.rpm is reserved for a spec file, sources and patches. It does not provide any tarball with source codes. Or

Re: packaging golang guidelines (like etcd, consul)

consul) > > > > On Mon, Nov 02, 2015 at 09:05:09AM -0500, Matthew Miller wrote: > > > On Sun, Nov 01, 2015 at 05:44:42PM +0100, Jan Chaloupka wrote: > > > > >are there some fedora guidelines for golang apps? > > > > >are there ma

Re: no influxdb for fedora 22, but there is for 21 and 23

72->| 80->| -- devel mailing list devel@lists.fedoraproject.org <mailto:devel@lists.fedoraproject.org> https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- Jan Chaloupka -

Re: packaging golang guidelines (like etcd, consul)

On 10/30/2015 10:07 PM, Muayyad AlSadi wrote: hi, I'm on f22 and have consul and etcd from the repos ldd /usr/bin/consul linux-vdso.so.1 (0x7ffc98fa2000) liblmdb.so.0.0.0 => /lib64/liblmdb.so.0.0.0 (0x7f99bc1b5000) libpthread.so.0 => /lib64/libpthread.so.0 (0x7f99bbf99000)

Re: https://fedoraproject.org/wiki/Packaging:Guidelines some links does not work

On 10/20/2015 07:17 PM, Sérgio Basto wrote: On Ter, 2015-10-20 at 18:52 +0200, Jan Chaloupka wrote: Ok, I should read it carefully. Links are working. Does it make sense to post here a link to the fpc ticket? For me yes, what is the ticket ? https://fedorahosted.org/fesco/ticket/1483#comment

Re: https://fedoraproject.org/wiki/Packaging:Guidelines some links does not work

Ok, I should read it carefully. Links are working. Does it make sense to post here a link to the fpc ticket? On 10/20/2015 06:49 PM, Jan Chaloupka wrote: Hi, in section "Duplication of system libraries", both links to "No Bundled Libraries" and "Treatment Of Bundl

https://fedoraproject.org/wiki/Packaging:Guidelines some links does not work

Hi, in section "Duplication of system libraries", both links to "No Bundled Libraries" and "Treatment Of Bundled Libraries" do not work. Jan -- devel mailing list devel@lists.fedoraproject.org

Re: how to set/unset env variables in spec file

Hi Arnaud, I am assuming all scripts you are referring to are sourced and run in %build section. Can you be more specific which commands are you running? %build section is interpreted as a bash script so source and unset should work. Without the concrete example it is hard to guess what is

[golang packaging] new go-compilers package

Hi everyone, I would like to introduce go-compilers packages. Intro: - golang language is supported on primary and secondary architectures - at the moment we have two compilers: golang and gcc-go - on Fedora we have a partial support for debugging - go-srpm-macros packages provides basic macros

Re: can't submit updates for f22?

Happened to me as well. How many times did you repeated 'fedpkg update' before it worked? For me it takes from 1 to 3 times before it works. On 08/25/2015 06:38 AM, Kaleb KEITHLEY wrote: I must have missed some announcement? Submitting from an up to date f22 box I get: % fedpkg update

Re: Package repositories missing both a spec file and a dead.package file

Hi On 08/21/2015 07:48 PM, Viktor Jancik wrote: Using an automated script I found 65 repositories that neither have a spec file or a dead.package among Fedora package repositories on the master branch. Is this desired? Here is the list: askbot-plugin-authfas autoconf268 bwping Django14

Re: Unable to buildroot override build

Hi, with bodhi 1.0 I was able to override a build. With bodhi 2.0 I can not. What packages should I updated? I am getting: $ bodhi --buildroot-override=golang-github-coreos-go-systemd-3-1.fc23 for f23-candidate --duration=20 --notes='temp non-stable dependecy waiting for stable' Traceback

Re: Packaging golang for secondary architectures, go-srpm-macros

On 07/27/2015 10:12 AM, Vít Ondruch wrote: Dne 26.7.2015 v 14:03 Jan Chaloupka napsal(a): On 07/24/2015 03:36 PM, Vít Ondruch wrote: Dne 9.7.2015 v 11:18 Jan Chaloupka napsal(a): Recommended use in spec file: 1) To choose the correct compiler: %ifarch %{golang_arches} BuildRequires: golang

Re: Packaging golang for secondary architectures, go-srpm-macros

On 07/24/2015 03:36 PM, Vít Ondruch wrote: Dne 9.7.2015 v 11:18 Jan Chaloupka napsal(a): Recommended use in spec file: 1) To choose the correct compiler: %ifarch %{golang_arches} BuildRequires: golang %else BuildRequires: gcc-go = %{gccgo_min_vers} %endif 2) To choose the correct command

Re: [POC-change] Fedora packages point of contact updates

On 07/20/2015 06:37 PM, Vít Ondruch wrote: Dne 20.7.2015 v 12:02 nob...@fedoraproject.org napsal(a): Change in package status over the last 168 hours 0 packages were orphaned 0 packages were retired

Re: Packaging golang for secondary architectures, go-srpm-macros

On 07/09/2015 12:49 PM, Petr Pisar wrote: On 2015-07-09, Jan Chaloupka jchal...@redhat.com wrote: # Define arches for PA and SA %golang_arches %{ix86} x86_64 %{arm} [...] Recommended use in spec file: 1) To choose the correct compiler: %ifarch %{golang_arches} BuildRequires: golang %else

Packaging golang for secondary architectures, go-srpm-macros

/show_bug.cgi?id=1241156 Any feedback and questions are welcomed and appreciated. Thanks to all involved in helping us. Kind Regards Jan Chaloupka -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code

Re: Packaging golang for secondary architectures, go-srpm-macros

On 07/09/2015 03:07 PM, Dan Horák wrote: On Thu, 9 Jul 2015 10:49:01 + (UTC) Petr Pisar ppi...@redhat.com wrote: On 2015-07-09, Jan Chaloupka jchal...@redhat.com wrote: # Define arches for PA and SA %golang_arches %{ix86} x86_64 %{arm} [...] Recommended use in spec file: 1

Re: minimal requirements for subpackage named common

On 05/01/2015 01:20 AM, Adam Williamson wrote: On Tue, 2015-04-28 at 15:15 +0200, Jan Chaloupka wrote: Is there a minimum requirement what should a common package provide or is it just arbitrary? There's no real requirement. Personally 'common' is the name I'd most likely expect, with one

minimal requirements for subpackage named common

Hi, I have a package (kubernetes) which I would like to decompose into 2 subpackages A and B. Problem is A and B share some files and directories so installing both of them on the same machine results in file conflicts. Solution is to create the third package C, which provides all those

Re: minimal requirements for subpackage named common

On 04/28/2015 03:40 PM, Florian Festi wrote: On 04/28/2015 03:15 PM, Jan Chaloupka wrote: Hi, I have a package (kubernetes) which I would like to decompose into 2 subpackages A and B. Problem is A and B share some files and directories so installing both of them on the same machine results

Re: Google Code and Gitorous shutting down: update upstream URLs please

Thanks Patrick. On 03/13/2015 12:02 AM, Patrick Uiterwijk wrote: golang-googlecode-gcfg: http//code.google.com/p/gcfg golang-googlecode-go-crypto: https//code.google.com/p/go.crypto golang-googlecode-go-exp: http//code.google.com/p/go.exp golang-googlecode-gomock: http//code.google.com/p/gomock

stable pending builds, golang-googlecode-net f21

.hg90e232e2462d.fc21 Thanks Jan Chaloupka -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

el6 builds failing

Hi, an hour ago I was able to build golang-github-mitchellh-mapstructure package for el6: http://koji.fedoraproject.org/koji/packageinfo?packageID=19293 Now it fails (some of my scratch builds): http://koji.fedoraproject.org/koji/taskinfo?taskID=7894679

Re: el6 builds failing

Working now On 10/17/2014 02:50 PM, Jan Chaloupka wrote: Hi, an hour ago I was able to build golang-github-mitchellh-mapstructure package for el6: http://koji.fedoraproject.org/koji/packageinfo?packageID=19293 Now it fails (some of my scratch builds): http://koji.fedoraproject.org/koji

Re: man-db without cache update (no cron or systemd *.timer)

Forwarding Colin's response = On Wed, Oct 15, 2014 at 09:47:41AM -0500, Chris Adams wrote: Once upon a time, Jan Chaloupka jchal...@redhat.com said: there has been a discussion about if we need cache for man-db for users which use man pages or update system

Re: man-db without cache update (no cron or systemd *.timer)

On 10/16/2014 12:56 PM, Vít Ondruch wrote: Dne 16.10.2014 v 10:35 Jan Chaloupka napsal(a): Forwarding Colin's response = On Wed, Oct 15, 2014 at 09:47:41AM -0500, Chris Adams wrote: Once upon a time, Jan Chaloupka jchal...@redhat.com said: there has been

Re: man-db without cache update (no cron or systemd *.timer)

On 10/16/2014 04:49 PM, Jóhann B. Guðmundsson wrote: On 10/16/2014 01:30 PM, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Oct 16, 2014 at 10:35:13AM +0200, Jan Chaloupka wrote: Forwarding Colin's response = On Wed, Oct 15, 2014 at 09:47:41AM -0500, Chris Adams

man-db without cache update (no cron or systemd *.timer)

Hi, there has been a discussion about if we need cache for man-db for users which use man pages or update system only from time to time and thus don't need to update cache every day. man-db as it is now depends on systemd which brings another set of packages. The use case is I just want to read

Re: Non-responsive maintainer: Deji Akingunola (fas: deji)

-- Jan Chaloupka -- * Software Engineer * * ENG Base Operating Systems * * Red Hat Czech, s. r. o.* * UTC+1 (CET), jchaloup * -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct