Automated Packit onboarding for new packages
Hello, based on a discussion after Packit talk [1] at Flock, to ease Packit onboarding [2], we are planning to automatically open pull requests with autogenerated Packit configuration file in newly created projects at src.fedoraproject.org, along with a description and instructions on how the automation works and how it can be adjusted. We want to give package maintainers the option to opt-out or to tweak the defaults (for example disabling certain jobs or adjusting default permissions). It probably makes sense to do that per maintainer, i.e. FAS username, however we would like to know what you think would be the best way to handle it - ideas are welcome. Thanks and regards, Packit team [1] https://youtu.be/fk_cndLyAx4 [2] https://packit.dev/docs/fedora-releases-guide/dist-git-onboarding -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Should we retire the mailx package?
I've opened [1], please take a look. After it is merged, I'll start the package retirement process for mailx. Thanks, Nikola [1] https://src.fedoraproject.org/rpms/s-nail/pull-request/3 -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
libcgroup SONAME bump in rawhide
I've just rebased libcgroup in rawhide and the rebase comes with a SONAME bump from libcgroup.so.2 to libcgroup.so.3. Ar far as I can tell, there are no affected packages. Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
libcgroup SONAME bump in rawhide
I'm going to rebase libcgroup in rawhide to version 2.0.1, which comes with a SONAME bump. condor appears to be the only affected package, and it will need to be rebuilt. I've done a successful test build in Copr [1]. Thanks, Nikola [1] https://copr.fedorainfracloud.org/coprs/nforro/libcgroup-2/build/3699724/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Review swap - python-specfile
On Thu, 2022-02-17 at 13:46 -0500, Ken Dreyer wrote: > Your email made me look at this upstream > (https://github.com/packit/specfile). It looks interesting! I wonder > if we could use it more broadly (like for pyrpkg). It reminds me of > https://github.com/containerbuildsystem/dockerfile-parse . > Thanks, yes, I hope it could be useful for other projects. pyrpkg doesn't interact with spec files, does it? Regards, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Review swap - python-specfile
Hello, is there anybody willing to review python-specfile [1]? I'd be happy to review a package of similar complexity in return. Thanks, Nikola [1] https://bugzilla.redhat.com/show_bug.cgi?id=2054599 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Non-responsive maintainer check for Domingo Becker (beckerde)
Hello, does anybody know how to contact Domingo Becker (FAS: beckerde)? https://bugzilla.redhat.com/show_bug.cgi?id=2005831 There is an open bugzilla for man-pages-es for about 6 months now, with no response: https://bugzilla.redhat.com/show_bug.cgi?id=1930214 Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
libcgroup 2.0 in Rawhide
Hello, I've rebased libcgroup in Rawhide to the new upstream release, libcgroup 2.0, with initial cgroupv2 support: https://github.com/libcgroup/libcgroup/releases/tag/v2.0 There are no incompatible ABI changes, SONAME of the library remains "libcgroup.so.1". This should make libcgroup relevant in Fedora once again, as cgroupv2 is the default since Fedora 31. That makes me wonder - does anybody still use libcgroup or libcgroup- tools in Fedora? Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: What is the most time consuming task for you as packager?
On Sat, 2020-12-26 at 20:39 +, Sérgio Basto wrote: > Hi, > For me the most time consuming is monkey updates packages like kde > apps, which every month or two we have a new release ( kde app > 20.04.1 20.04.2 20.08.0 , 20.12.00 etc ) > > I did some scripts to automate my builds , we got some software like > https://github.com/fedora-infra/the-new-hotness/ > but the more I do, I always some variables that are different from > project to project , we need to know the version number, we may need > to download more than one source, we may need drop patches that we > know that are already upstreamed, not all the package are build in > same branches so we need to know what branches we want update , we > may have to add buildroot-overrides, we need add build to bodhi and > fill some information , we need close bugs create made by hotness or > other users etc > > Examples of my scripts are usually in packages sources like > > https://src.fedoraproject.org/rpms/virtualbox-guest-additions/blob/master/f/update_vbox.sh > > > or (in attachment) scripts in very quick-and-dirty style Have you tried rebase-helper? [1] It won't solve everything, but you could find it useful. However particularly in case of virtualbox-guest-additions there is an issue with the extra "a" in source name. I'm open to suggestions on how to deal with that :) Regards, Nikola [1] https://github.com/rebase-helper/rebase-helper ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Searching a new home for my packages
On Thu, 2020-07-16 at 15:37 +0200, Nikola Forró wrote: > On Sat, 2020-06-13 at 13:54 +0200, Thomas Spura wrote: > > Any takers for: > > - *python-mglob* and/or *python-minimock *(instead of retiring it?) > > - *scipy* (seems to be mostly maintained by Orion/Miro now) > > I can take scipy (FAS: nforro). Hello Thomas, Any news regarding scipy? Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: ar (binutils) segfaulting in Rawhide - known bug?
On Fri, 2020-07-31 at 12:11 -0600, Jeff Law wrote: > Note the linker bug should be fixed now. So you should be able to > rebuild man-db with LTO now. Thank you, done. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: ar (binutils) segfaulting in Rawhide - known bug?
On Sat, 2020-07-25 at 01:11 -0600, Jeff Law wrote: > So at a high level ar makes a call to lrealpath. That naturally goes through > the > PLT. The PLT stub loads the value out of the GOT and jumps to it. The > problem > is the entry in the GOT is *zero* when it should be pointing to the resolver. > > Now lrealpath is provided by libiberty and a copy is in libbfd.so and the GOT > entry in libbfd.so looked right. But by the time the program has hit main, > the > GOT entry has been reset to zero. Naturally that's happening inside the > dynamic > linker (as expected, confirmed with a watchpoint). If you've ever had to > debug > ld.so, you'll know it's an insanely painful experience, but it proved > fruitful. > > The key was finding out that we were not using the libbfd.so linker map to > resolve lrealpath, instead we were using the linker map for the main program > (ar > in this case). So natrually it's time to look a bit more closely at the > symbol > table for ar. > > The main symbol table for ar it doesn't mention lrealpath. But that's just a > confusing byproduct of having two symbol tables. What matters to ld.so is the > *dynamic* symbol table. And ar has lrealpath in its dynamic symbol table. > And > here's the kicker, it's an absolute symbol with the value 0: > > A lrealpath > > A symbol in the main program takes precedence over a symbol in a DSO. So the > dynamic linker was actually doing the right thing given the input it was > provided. > > Now why (*&@#$ does ar have lrealpath as an absolute symbol? It's got to be > related to the fact that when we link ar we pull in another copy of libiberty. > In fact, ar links against libiberty twice. Once via -liberty then again > against > libiberty.a (and kindof a 3rd time indirectly via libbfd). BUt even so that > shouldn't be creating an absolute symbol. That's just weird. > > This smells like a linker bug to me. Not surprisingly if I force the system > to > use ld.gold, then I don't see the bogus absolute symbol and the resultant ar > works just fine. > > It's late and I'll dig further over the weekend, but right now this looks > like a > linker bug to me. I may turn off LTO globally or in the various instances of > binutils -- I need to sleep on that. I'm seeing the same behavior with man-db, more specifically with accessdb linking to libmandb: $ nm -D accessdb | grep xmalloc A xmalloc Obviously it segfaults, unless I disable LTO. Is there a bugzilla for that linker bug? Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Searching a new home for my packages
On Sat, 2020-06-13 at 13:54 +0200, Thomas Spura wrote: > Any takers for: > - *python-mglob* and/or *python-minimock *(instead of retiring it?) > - *scipy* (seems to be mostly maintained by Orion/Miro now) I can take scipy (FAS: nforro). Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Review Swap
On Tue, 2020-03-03 at 09:46 -0500, Breno Brand Fernandes wrote: > Hi, > > Would you want to swap reviews? > This was generated with go2rpm. > It should be easy to review. > > https://bugzilla.redhat.com/show_bug.cgi?id=1806219 Hi, I will take it. Can you review dsp [1] in return? Thanks, Nikola [1] https://bugzilla.redhat.com/show_bug.cgi?id=1808351 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: jnovy pushed to mc (master). "- just keep perl-interpreter BR because of man2hlp, (..more)"
On Tue, 2019-10-08 at 18:42 +0100, Tomasz Kłoczko wrote: > IMO above shows clearly that adding "aspell-en" in mc or aspell > dependencies does not solve issue .. at all. > Kind of mitigation of that problem should be IMO change aspell error > message (by add Fedora/any rpm based distro patch) informing that > system has missing aspell- package. This sounds reasonable, making a maintainable downstream patch could be tricky though. I'll try to come up with something. Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: jnovy pushed to mc (master). "- just keep perl-interpreter BR because of man2hlp, (..more)"
On Tue, 2019-10-08 at 12:22 +0200, Jindrich Novy wrote: > Nikola, is it intended that aspell doesn't depend on any dictionary? > E.g. aspell-en? Please see the email bellow. Hi, it seems it is intentional [1], this is probably the reason [2]. I suppose aspell could recommend aspell-en, to prevent circular dependency (assuming weak dependencies actually do prevent it). Thanks, Nikola [1] https://src.fedoraproject.org/rpms/aspell/c/405c4df7ef4bcd93103c57e3e910e2f82a045c24 [2] https://bugzilla.redhat.com/show_bug.cgi?id=485210 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: libexempi SONAME bump in rawhide
On Fri, 2019-09-06 at 14:52 +0200, Nikola Forró wrote: > exempi-2.5.1-1.fc32 is now in rawhide: > https://bodhi.fedoraproject.org/updates/FEDORA-2019-57b855fa99 And all dependent packages have been rebuilt: https://bodhi.fedoraproject.org/updates/FEDORA-2019-350d852631 https://bodhi.fedoraproject.org/updates/FEDORA-2019-aa2bdf6df4 https://bodhi.fedoraproject.org/updates/FEDORA-2019-6b01474a94 https://bodhi.fedoraproject.org/updates/FEDORA-2019-dccb151e34 https://bodhi.fedoraproject.org/updates/FEDORA-2019-1a92688779 https://bodhi.fedoraproject.org/updates/FEDORA-2019-d4f3c2351b https://bodhi.fedoraproject.org/updates/FEDORA-2019-1e7b4bbbfa Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: libexempi SONAME bump in rawhide
On Thu, 2019-09-05 at 17:40 +0200, Nikola Forró wrote: > Yes, of course. The plan is to do it tomorrow. exempi-2.5.1-1.fc32 is now in rawhide: https://bodhi.fedoraproject.org/updates/FEDORA-2019-57b855fa99 Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: libexempi SONAME bump in rawhide
On Mon, 2019-09-02 at 15:04 +, Debarshi Ray wrote: > You could apply to become a provenpackager: > https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/ > > I will vote for you. :) Thanks, but it won't be necessary, vondruch offered to help me with the rebuilds. On Tue, 2019-09-03 at 09:17 +, Wolfgang Ulbrich wrote: > Thanks for the heads-up! > > I can rebuild caja and eog when new exempi version is in rawhide. > Maybe you post that here? Yes, of course. The plan is to do it tomorrow. Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: libexempi SONAME bump in rawhide
On Fri, 2019-08-30 at 20:09 +, Debarshi Ray wrote: > Thanks for the heads-up! > > Were you looking for a go ahead to rebuild the affected packages in > Fedora proper? In that case, you have my whole hearted appreciation > for taking care of the eog and tracker-miners rebuilds. :) I would like to do that, but it would require help of a provenpackager, since I'm not one myself. Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
libexempi SONAME bump in rawhide
Hello, I'm planning to update exempi to version 2.5.1 in rawhide, and it includes a SONAME change from "libexempi.so.3" to "libexempi.so.8". Affected packages are: caja eog eom equalx nemo tellico tracker-miners I've rebuilt all of them in Copr [1] without issues, except tellico, which failed due to an unrelated bug [2]. Regards, Nikola [1] https://copr.fedorainfracloud.org/coprs/nforro/exempi/builds/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1746013 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Review Swap - netatalk and dymo-cups-drivers
On Sat, 2019-01-05 at 14:35 +, Andrew Bauer wrote: > I've got a couple of review requests in need of a reviewer: > > https://bugzilla.redhat.com/show_bug.cgi?id=1659709 Hello, I'll review dymo-cups-drivers, could you review qt5-qtpbfimageformat [1] in return? Thanks, Nikola [1] https://bugzilla.redhat.com/show_bug.cgi?id=1663492 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to use %license: with a license file ?
On Thu, 2018-12-13 at 17:51 +0100, J. Scheurich wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1653481 > > COPYING.txt must be installed with %license not %doc. > > But %License: only accepts things like GPLv3+ or am i wrong ? > > so long > MUFTI Hi, you are confusing "License" tag with "%license" directive of %files section. See Licensing Guidelines [1] for more info. Regards, Nikola [1] https://fedoraproject.org/wiki/Packaging:LicensingGuidelines ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++
On Sun, 2018-02-18 at 18:09 +0100, Igor Gnatenko wrote: > If you fixed package(s), found false positive, found missing packages in list > or anything else -- please let me know. Fixed in rawhide: aspell exempi gpxsee groff joe jpilot libcgroup libpng12 libpng15 libtiff man-db pilot-link Also fixed the following unlisted packages: libjpeg-turbo libpipeline libpng mailx uClibc Thanks, Nikola ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: /sbin/nologin in /etc/shells
Hello, I'm linking another bugzilla [1] related to this, this one is against shells(5) man page. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1218302 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
man-db-2.7.3-2.fc24 with file triggers in rawhide
Hello, I've pushed man-db with file triggers and crontab dependency dropped to rawhide. Removing cron job means that there will be no periodic cache update for user-configured manpaths. There has already been discussion about this: https://lists.fedoraproject.org/pipermail/devel/2014-Octobe r/thread.html#203357 I think the subpackage suggestion makes more sense now. Main package with file triggers fully functional and without dependency on crontabs or systemd, and subpackage providing only the periodic cache update functionality for those who need it. What do you think about it? Regards, Nikola -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Review or review swap: vim-go
Zbigniew Jędrzejewski-Szmek píše v Čt 23. 07. 2015 v 14:16 +: > Taken. > > You could take https://bugzilla.redhat.com/show_bug.cgi?id=1240116 (h > ard) > or https://bugzilla.redhat.com/show_bug.cgi?id=1245330 (easy). > Thanks. I'll take the easy one :-) Nikola -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Review or review swap: vim-go
Hello, I'm looking for someone to review vim-go [1], Go development plugin for Vim. I can review something for you in return. Regards, Nikola [1] https://bugzilla.redhat.com/show_bug.cgi?id=1245604 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
