Re: Orphaning my packages: elvish, git-delta & dependencies
Hau idatzi du Felix Wang (topa...@outlook.com) erabiltzaileak (2024 api. 22(a), al. (03:57)): > > I'd like to take elvish package, Current package golang-github-elves-elvish should be replaced by a new one[1], set correct Obsoletes tag and retired. The name and goipath are not correct anymore.a > and I filed a review request of golang-pkg-nimblebun-lsp, which it is a > dependency of elvish. > I would be grateful If you can take the review, or I can do the review swap > if am familiar the knowledge with it. > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2276326 Approved. [1] https://download.copr.fedorainfracloud.org/results/mikelo2/elvish/fedora-rawhide-x86_64/07333485-elvish/elvish.spec plus the Obsoletes should be OK for the review. -- ___ 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: Orphaning my packages: elvish, git-delta & dependencies
Hau idatzi du Janet Black (uhh...@gmail.com) erabiltzaileak (2024 api. 19(a), or. (21:06)): > > Hi, I do not have the time to contribute packages to Fedora these days. Thanks for your work Janet. > I am orphaning the following packages under my maintainership: > - golang-github-elves-elvish I can't take it and not an user of elvish, but if someone wants to jump in I've created a copr with updated spec (and required extra dep) to help anyone interested. https://copr.fedorainfracloud.org/coprs/mikelo2/elvish/ > - golang-github-xiaq-persistent Not needed by newer elvish versions. --- Mikel -- ___ 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: Issues with pytest and python-pytest-postgresql
Hi Lumir, Hau idatzi du Lumír Balhar (lbal...@redhat.com) erabiltzaileak (2024 api. 4(a), og. (09:57)): > > It might look like simple bump but you are upgrading from 4.1.1 to 6.0.0 > and there are some breaking changes between those releases. By "simple bump" I meant no other changes in the spec. I agree with you the update is not that "simple". > The error message looks like the plugin is loaded twice for some reason > and the second try to register the same CLI option fails. %pytest macro > sets PYTHONPATH so it's possible that the plugin is first loaded from > buildroot and then from the current working directory or vice-versa. I > also see some settings for pytest in pyproject.toml you might want to > take a look. I found how to fix and it's a mix of what you suggest and pytest params. I had to add "-p no:postgresql" to %pytest to avoid loading the installed module, but also had to do changes in the pyproject.toml file. I documented in the commit I pushed: https://src.fedoraproject.org/rpms/python-pytest-postgresql/c/4756bd60d23908b86f81ca25d551fa22835c83ac?branch=rawhide Best regards, Mikel -- ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Issues with pytest and python-pytest-postgresql
Hi all,
I'm trying to update python-pytest-postgresql (simple bump) and during
the %check phase I find the following error:
+ /usr/bin/pytest --postgresql-exec=/usr/bin/pg_ctl -k 'not docker' --no-cov
(...)
File
"/builddir/build/BUILDROOT/python-pytest-postgresql-6.0.0-1.fc41.x86_64/usr/lib/python3.12/site-packages/pytest_postgresql/plugin.py",
line 67, in pytest_addoption
parser.addoption(
File "/usr/lib/python3.12/site-packages/_pytest/config/argparsing.py",
line 104, in addoption
self._anonymous.addoption(*opts, **attrs)
File "/usr/lib/python3.12/site-packages/_pytest/config/argparsing.py",
line 385, in addoption
raise ValueError("option names %s already added" % conflict)
ValueError: option names {'--postgresql-exec'} already added
What I found is that once the postgresql plugin is loaded it conflicts
with the tests of the module.
Any advice on how to solve this issue?
Best regards,
Mikel
--
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: xz backdoor
Hi, I'm seeing weird things. For whatever reason Source for xz was changed 2 months ago[1] to use GH releases instead of tukaani.org site. The XZ page[2] has a note stating: "Note: GitHub automatically includes two archives Source code (zip) and Source code (tar.gz) in the releases. These archives cannot be disabled and should be ignored." And they wayback WayBackMachine[3] doesn't have previous versions. Do we know if GH release tarballs are safe? @richard, do you remember why you had to change the source for the tarball? Regards, Mikel [1] https://src.fedoraproject.org/rpms/xz/c/0c09a6280b4a0c4fd7a9fc742c09469c95ff431f?branch=f40 [2] https://xz.tukaani.org/ [3] https://web.archive.org/web/20240119212251/https://xz.tukaani.org/ Hau idatzi du Kevin Kofler via devel (devel@lists.fedoraproject.org) erabiltzaileak (2024 mar. 29(a), or. (19:01)): > > Hi, > > wow: https://www.openwall.com/lists/oss-security/2024/ > > I think at this point we clearly cannot trust xz upstream anymore and should > probably fork the project. > > Kevin Kofler > -- > ___ > 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 -- ___ 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: List of long term FTBFS packages to be retired in February
Hau idatzi du Miro Hrončok (mhron...@redhat.com) erabiltzaileak (2024 ots. 3(a), lr. (18:18)): > > > Package (co)maintainers > > golang-github-gatherstars-com-jwz eclipseo, go-sig > golang-github-jhillyerd-enmime eclipseo, go-sig > golang-gopkg-square-jose-2 alexsaezm, go-sig > golang-opentelemetry-otel-0.20 alexsaezm, go-sig Fixed these. > golang-github-pierrre-compare eclipseo, go-sig Obsoleted by updating golang-github-pierrre-geohash Mikel -- ___ 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: Unretiring keepass
ouch, ignore my email, I misread between keepassx(.org) and keepass(.info) projects. Keepass project upstream is still active and maintained Sorry, Mikel Hau idatzi du Mikel Olasagasti (mi...@olasagasti.info) erabiltzaileak (2023 abe. 1(a), or. (11:15)): > > Hi Julian, > > Hau idatzi du Julian Sikorski (beleg...@gmail.com) erabiltzaileak > (2023 aza. 21(a), ar. (10:56)): > > > > Hi list, > > > > as the CVE (which was not even a problem with keepass in the first > > place) leading to keepass retirement has been resolved in the meantime, > > I would like to unretire the package. I have submitted a re-review already: > > KeePassX project announced development stopped two years ago and > suggest to switch to KeePassXC: > > https://www.keepassx.org/index.html%3Fp=636.html > > I understand that changing to a new app can break some workflows[1], > but I feel (re)adding a security tool to Fedora that has been > deprecated by the owners it's a bad idea and a risk for users. If > something doesn't work with KeePassXC report upstream. > > Kind regards, > Mikel > > [1] https://xkcd.com/1172/ -- ___ 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: Unretiring keepass
Hi Julian, Hau idatzi du Julian Sikorski (beleg...@gmail.com) erabiltzaileak (2023 aza. 21(a), ar. (10:56)): > > Hi list, > > as the CVE (which was not even a problem with keepass in the first > place) leading to keepass retirement has been resolved in the meantime, > I would like to unretire the package. I have submitted a re-review already: KeePassX project announced development stopped two years ago and suggest to switch to KeePassXC: https://www.keepassx.org/index.html%3Fp=636.html I understand that changing to a new app can break some workflows[1], but I feel (re)adding a security tool to Fedora that has been deprecated by the owners it's a bad idea and a risk for users. If something doesn't work with KeePassXC report upstream. Kind regards, Mikel [1] https://xkcd.com/1172/ -- ___ 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: Inactive packages removed from packager group
Hi all, Hau idatzi du Kevin Fenzi (ke...@scrye.com) erabiltzaileak (2023 aza. 18(a), lr. (21:09)): > > rpms/golang-github-kurin-blazer > rpms/golang-github-minio > rpms/golang-rsc-pdf Took these as are required by other packages I maintain. > rpms/ed > rpms/multitail I was already co-admin, taking ownership. > rpms/restic I was updating this package as part of go-sig, taking ownership to track it better. Regards, Mikel -- ___ 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
Missing notifications
Hi, I'm not receiving mails from some updates like koschei build status or src.f.o commits. Has something changed in this regard or is it the mail service having issues again? Kind regards, Mikel -- ___ 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: Review of Matrix Go packages
Hi Kai, I'll take care of them. Regards, Mikel Hau idatzi du Kai A. Hiller (v02...@gmail.com) erabiltzaileak (2023 aza. 18(a), lr. (09:48)): > > Hello, > > I’m currently adding Go-based parts of the Matrix ecosystem to Fedora. For > that I need reviews of quite a few, but mostly small and auto-generated > packages. Help is appreciated, please tell me what you need from me in return. > > List of package dependencies and bugzilla links: > > golang-maunium-mautrix (#2250408) > ├ golang-mau-zeroconfig (#2249896) > ├ golang-mau-util (#2249878) > ├ golang-maunium-mauflag (#2249890) > ├ golang-maunium-maulogger-2 (#2249894) > │ ├ golang-github-tidwall-sjson (#2249874) > │ │ ├ golang-github-tidwall-gjson (#2249873) > │ │ │ ├ golang-github-tidwall-match (#2249868) > ├ golang-github-matrix-org-gomatrixserverlib (#2250315) > │ ├ golang-gopkg-macaroon-2 (#2250314) > │ ├ golang-github-matrix-org-util (#2250311) > │ ├ golang-github-matrix-org-gomatrix (#2250312) > │ ├ golang-github-tidwall-sjson > > Best wishes > Kai > > -- > ___ > 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 -- ___ 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: orphaning prometheus* and some other golang packages
Hi Mark, Hau idatzi du Mark E. Fuller (ful...@fedoraproject.org) erabiltzaileak (2023 urr. 7(a), lr. (12:22)): > > Hi all, > > I picked up a number of prometheus packages (see below) a few months > back during the golang scramble after an unresponsive maintainer. > I don't have the time or the interest (or the technical chops) to > maintain them. > > Obviously these are important packages, so at this time I am announcing > my intention to orphan them. > Unless I hear from someone who would like to actively collaborate on > their maintenance, I'm going to orphan them in approximately one week: Thanks for alerting us in advance. > golang-github-prometheus > golang-github-prometheus-node-exporter > golang-github-prometheus-exporter-toolkit > golang-github-prometheus-community-runit > > golang-opentelemetry-otel > golang-google-grpc If you can add me as co-admin, I can have a look to all of them. Kind regards, Mikel ___ 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: Intent to orphan vpnc
Hi Christian, Hau idatzi du Christian Krause (c...@fedoraproject.org) erabiltzaileak (2023 ira. 6(a), az. (00:08)): > > There is no active upstream for vpnc. However, according to the bug reports > for NetworkManager-vpnc, there might be still a few users. It seems there is an active fork available: https://github.com/streambinder/vpnc/ I checked and Arch for example is using the source in that repo for the package: https://archlinux.org/packages/extra/x86_64/vpnc/ Just noting in case someone steps in to maintain the package. Regards, Mikel ___ 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: packager-dashboard not updating koschei build status
Thanks František, works fine now! Hau idatzi du Frantisek Zatloukal (fzatl...@redhat.com) erabiltzaileak (2023 uzt. 25(a), ar. (18:59)): > > Hey, > > Thanks for raising the issue. It has been addressed and all the dashboards > should now contain up2date data from koschei. > > Longer answer: The problem was the enablement of EPEL 9 Next in koschei, > oraculum (the backend for the Packager Dashboard) isn't ready for these kinds > of releases and I had to add filtering of it: > https://pagure.io/fedora-qa/oraculum/c/aba10ef932ba894c2000851f4028f4402d6bbcdc?branch=master > . > > On Tue, Jul 25, 2023 at 12:54 AM Mikel Olasagasti > wrote: >> >> Hi all, >> >> I've multiple reports of FTBFS in the packager-dashboard, but I can >> see many of the packages are being built fine in koschei/koji. >> >> Is there a known issue on refreshing koschei data? >> >> Kind regards, >> Mikel >> ___ >> 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 > > > > -- > > Best regards / S pozdravem, > > František Zatloukal > Senior Quality Engineer > Red Hat ___ 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
packager-dashboard not updating koschei build status
Hi all, I've multiple reports of FTBFS in the packager-dashboard, but I can see many of the packages are being built fine in koschei/koji. Is there a known issue on refreshing koschei data? Kind regards, Mikel ___ 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: List of long term FTBFS packages to be retired in August
Hau idatzi du Fabio Valentini (decatho...@gmail.com) erabiltzaileak (2023 uzt. 13(a), og. (14:27)): > > On Wed, Jul 12, 2023 at 1:01 PM Mikel Olasagasti > wrote: > > > > Hau idatzi du Fabio Valentini (decatho...@gmail.com) erabiltzaileak > > (2023 uzt. 12(a), az. (11:53)): > > > > > > On Tue, Jul 11, 2023 at 10:06 PM Mikel Olasagasti > > > wrote: > > > > > > > > > > (snip) > > > > > > > > > > > > golang-github-moby-spdystreamgo-sig, mikelo2 > > > > > > > > Builds fine in Koschei and no BZ > > > > > > > > > golang-github-openapi-validate alexsaezm, go-sig > > > > > > > > Builds fine in Koschei and no BZ > > > > > > This is usually an indication that the package fails to even produce a > > > valid SRPM file (i.e. "fedpkg srpm" fails). > > > In this case, mass rebuild will skip it, no FTBFS bug will be filed, > > > and koschei will keep using the last "known good" SRPM from koji. > > > > Both packages work for me. I'm doing the following: > > > > $ fedpkg clone golang-github-moby-spdystream > > $ cd golang-github-moby-spdystream > > $ fedpkg srpm > > $ mock -r fedora-rawhide-x86_64 > > /tmp/golang-github-openapi-validate/golang-github-openapi-validate-0.20.1-5.fc39.src.rpm > > If that is indeed the case, then the missing f38 build was likely > caused by a hiccup during the f38 mass rebuild. > To get the package off the "long term FTBFS retirements" list, all > that would be needed is to run "fedpkg build". Thanks, Fabio. I realized that packages were not built for rawhide, f38 and f37. I built the packages for rawhide and f38, I hope it's enough to be out of the list. Regards, Mikel ___ 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: non-responsive maintainer check for anthr76
Hi Mark, Anthony announced a hiatus a couple of months ago: https://lists.fedoraproject.org/archives/list/gol...@lists.fedoraproject.org/thread/5NUXD4CESPDXKV6NQL2QDQAZP4BTQF2I/ As go-sig has permissions I guess you can continue updating the package once unretired. Regards, Mikel Hau idatzi du Mark E. Fuller (mark.e.ful...@gmx.de) erabiltzaileak (2023 uzt. 14(a), or. (18:03)): > > https://bugzilla.redhat.com/show_bug.cgi?id=964 > > This email is part of the non-responsive maintainer procedure for > anthr76, following > https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/. > > Please respond if you are still active in Fedora and want to maintain > golang-github-google-renameio-2. > > Please see the request for unretirement at > https://bugzilla.redhat.com/show_bug.cgi?id=2219084 > > ___ > 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 ___ 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: List of long term FTBFS packages to be retired in August
Hau idatzi du Fabio Valentini (decatho...@gmail.com) erabiltzaileak (2023 uzt. 12(a), az. (11:53)): > > On Tue, Jul 11, 2023 at 10:06 PM Mikel Olasagasti > wrote: > > > > (snip) > > > > > > golang-github-moby-spdystreamgo-sig, mikelo2 > > > > Builds fine in Koschei and no BZ > > > > > golang-github-openapi-validate alexsaezm, go-sig > > > > Builds fine in Koschei and no BZ > > This is usually an indication that the package fails to even produce a > valid SRPM file (i.e. "fedpkg srpm" fails). > In this case, mass rebuild will skip it, no FTBFS bug will be filed, > and koschei will keep using the last "known good" SRPM from koji. Both packages work for me. I'm doing the following: $ fedpkg clone golang-github-moby-spdystream $ cd golang-github-moby-spdystream $ fedpkg srpm $ mock -r fedora-rawhide-x86_64 /tmp/golang-github-openapi-validate/golang-github-openapi-validate-0.20.1-5.fc39.src.rpm Mikel ___ 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: List of long term FTBFS packages to be retired in August
Hi, Hau idatzi du Miro Hrončok (mhron...@redhat.com) erabiltzaileak (2023 uzt. 11(a), ar. (15:07)): > > golang-code-cloudfoundry-bytefmt go-sig, mikelo2 Fixed > golang-github-aliyun-cli bdperkin, go-sig Fixed > golang-github-d2g-dhcp4clientalexsaezm, go-sig Fixed > golang-github-dennwc-varint alexsaezm, go-sig Fixed > golang-github-macaron-inject go-sig, mikelo2 Fixed > golang-github-moby-spdystreamgo-sig, mikelo2 Builds fine in Koschei and no BZ > golang-github-openapi-validate alexsaezm, go-sig Builds fine in Koschei and no BZ > golang-github-rogpeppe-charset go-sig, mikelo2 Fixed > golang-github-yvasiyarov-metrics alexsaezm, go-sig Fixed > golang-gopkg-tomb-1 go-sig, mikelo2 Fixed > golang-gopkg-validator-2 alexsaezm, go-sig To retire after uber-tally doesn't depend anymore. Will check after dep refreshes. -- Mikel ___ 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
go-sig status
Hi all, This mail is just a heads up on go-sig delicate current status. After a "non-responsive" process for one of the go-sig members[1], a lot of go-sig packages become orphans. This maintainer has been working for years creating hundreds of packages and updating them. The orphaning process caused that ~2100/~2300 go-sig packages to be affected directly or indirectly. The current number is 1633/2373 packages affected. The list of currently affected packages can easily be checked using package-dashboard[2] and clicking on the 'orphan' (little person) button at the top right. IIUC in little more than 4 weeks all those orphaned packages will be retired and that can cause massive impact. Indirectly affected packages include docker (moby-engine), containerd, rclone, restic or gopass to name a few. Some packages might be key for some people, some might just disappear without causing major noise. I adopted ~100 packages needed by packages I maintain and I'm in the process to update them. More hands will be needed to take the rest and/or review new deps required by the updates. And that's it. As this may create some bad press if some of those packages vanish, I just wanted to alert devel-list. Kind regards, Mikel [1] https://pagure.io/fesco/issue/2999 [2] https://packager-dashboard.fedoraproject.org/dashboard?groups=go-sig ___ 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
packager dashboard - orphan data refresh
Hi all, Currently the packager dashboard for go-sig group[1] shows 1995/2371 packages impacted by orphans after the non-responsive process concluded for eclipseo. Some (many?) of the packages have been adopted already, but the orphan related information has not been updated, iiuc, in the last +48 hours. This complicates tracking of what is missing to take care of. - How often does the orphan data get refreshed? - Would it be possible to trigger an update asap? Kind regards, Mikel [1] https://packager-dashboard.fedoraproject.org/dashboard?groups=go-sig ___ 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
untagging golang-github-nats-io-jwt from rawhide
Hi all, TL;DR: Would it be possible to untag golang-github-nats-io-jwt-2.4.1-1.fc39[1] from rawhide? Some days ago golang-github-nats-io-jwt was bumped from 1.2.2 version to 2.4.1. The new version doesn't provide "golang(github.com/nats-io/jwt)" and is causing a dependency chain issue making it difficult to build or update packages in rawhide. There are a few hundred packages affected. Fixing the dependency chain will require updating several packages, including the NATS stack, and importing new required packages. This process will take some days/weeks. If the build[1] can be untagged from rawhide and previous version restored the dependency chain problem should be solved, allowing maintainers of other packages to work while the NATS upgrade is prepared. Kind regards, Mikel [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=2208544 ___ 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: Question regarding setuptools automatic discovery (pyproject.toml)
Hi Sandro, Hau idatzi du Sandro (li...@penguinpee.nl) erabiltzaileak (2023 eka. 4(a), ig. (01:55)): > > Hi, > > I ran into a build failure for a Python package that dropped setup.py in > the latest update and uses pyproject.toml for metadata and setuptools. > > The build failed due to 'error: Installed (but unpackaged) file(s) > found' [1]. However, all the erroneously installed modules should be > excluded by default, if I understand the setuptools automatic discovery > documentation [2] correctly. They are listed in > 'FlatLayoutPackageFinder.DEFAULT_EXCLUDE'. In this case 'docs', > 'scripts' and 'test'. > > Since this is still beta when using pyproject.toml, I was wondering if > someone else has come across this misbehavior. Or, maybe, it's something > I failed to spot in pyproject.toml, that's causing it. > > I can make it work by adding a 'include = ["palettable"]' in the > tool.setuptools.packages.find table [3]. But I'd like a second opinion > before submitting a PR upstream. I ran to the same problem updating pg_activity last week. After a conversation with upstream[1] and exploring different options they preferred to remove packages.find. Regards, Mikel [1] https://github.com/dalibo/pg_activity/pull/378 ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Old stalled bodhi updates
Hi all, There are currently 157 updates in testing or pending status in Bodhi that were created before 2023: https://bodhi.fedoraproject.org/updates/?search=_before=2023=pending=testing=1 There are 7 Fedora updates, 6 for Fedora-37 and one in pending->testing status for Fedora-35. The rest are for EPEL-7 and EPEL-8, mostly from before 2022, so I guess as those releases are still active the updates are not auto-closed. Can those old updates be unpushed? If so, who should take care of it? Kind regards, Mikel ___ 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
pipenv / pipfile support in pyproject-rpm-macros
Hi team, I maintain a package, python-mirakuru[1], and the spec file uses pyproject-rpm-macros. With the latest release, 2.5.0, the project migrated[2] from using requirements.txt files to use pipenv/Pipfile to declare dependencies. I found that after bumping the version in the spec it fails during the %check phase as some dependencies are missing. I can easily workaround by declaring missing BuildRequires, but I wonder if there is an automagic way to support pipenv with pyproject-rpm-macros to avoid manually having to define BRs. Kind regards, Mikel Olasagasti [1] https://src.fedoraproject.org/rpms/python-mirakuru [2] https://github.com/ClearcodeHQ/mirakuru/pull/622/files ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Rpmautospec howto do a rebuild for something
Hi Sérgio, Hau idatzi du Sérgio Basto (ser...@serjux.com) erabiltzaileak (2023 urt. 2, al. (13:40)): > > I need rebuild a package that is using rpmautospec , how I can rebuild > the package and increase relversion ? git commit --allow-empty -m "Rebuild because of X" ___ 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: Fedora SCM requests on the weekend
Hi Kevin, Hau idatzi du Kevin Fenzi (ke...@scrye.com) erabiltzaileak (2022 uzt. 9, lr. (20:11)): > > On Fri, Jul 08, 2022 at 01:02:15PM -, Mukundan Ragavan wrote: > > > On Sun, Jul 03, 2022 at 12:11:40PM +0200, Fabio Valentini wrote: > > > > > > That said, until then I can try and run things on weekends. > > > > Is there a formal process to volunteer to hold the keys to the kingdom? > > Yes. Basically one of the existing group members nominates someone, and > all the existing group members vote on adding them. > > However, at this point we are close to automating it, so not sure it's > worth adding more folks. We could though if it isn't automated soon... Any updates on this front? Is there a ticket I can track? Regards, Mikel ___ 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: Orphaned packages looking for new maintainers
Hau idatzi du Miro Hrončok (mhron...@redhat.com) erabiltzaileak (2022 ira. 26, al. (11:28)): > > golang-github-gofrs-flock go-sig, orphan 0 weeks ago I took this one and also added eclipseo as co-admin. Mikel ___ 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: Donate 1 minute of your time to test upgrades from F36 to F37
Hau idatzi du Miroslav Suchý (msu...@redhat.com) erabiltzaileak (2022 ira. 12, al. (15:00)): > > Do you want to make Fedora 37 better? Please spend 1 minute of your time and > try to run: > > # Run this only if you use default Fedora modules > # next time you run any DNF command default modules will be enabled again > sudo dnf module reset '*' > > dnf --releasever=37 --setopt=module_platform_id=platform:f37 \ > --enablerepo=updates-testing \ > $(rpm -q fedora-repos-modular >/dev/null && echo > --enablerepo=updates-testing-modular) \ > --assumeno distro-sync Error: Problem: package gnome-books-40.0-4.fc36.x86_64 requires libgnome-desktop-3.so.19()(64bit), but none of the providers can be installed - gnome-desktop3-42.4-1.fc36.x86_64 does not belong to a distupgrade repository - problem with installed package gnome-books-40.0-4.fc36.x86_64 I see package has been retired. https://src.fedoraproject.org/rpms/gnome-books How should I proceed? ___ 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: fedora-review of m3u8 fails
Hau idatzi du Martin Gansser (martin.gans...@gmail.com) erabiltzaileak (2022 abu. 9, ar. (14:37)): > > Hi, > > fedora-review of m3u8 fails with the following error message: > > Building target platforms: x86_64 > Building for target x86_64 > setting SOURCE_DATE_EPOCH=1659916800 > Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.g2rRRB > + umask 022 > + cd /builddir/build/BUILD > + cd /builddir/build/BUILD > + rm -rf m3u8-3.1.0 > + /usr/lib/rpm/rpmuncompress -x -v/builddir/build/SOURCES/m3u8-3.1.0.tar.gz > rpmuncompress: -v/builddir/build/SOURCES/m3u8-3.1.0.tar.gz: unknown option > error: Bad exit status from /var/tmp/rpm-tmp.g2rRRB (%prep) Works for me using the src.rpm + fedora-review-0.8.0-1.fc36.noarch, there is a space between -v and /builddir/ in my case. $ fedora-review -n python-m3u8 $ grep -A1 rpmuncompress review-python-m3u8/results/build.log + /usr/lib/rpm/rpmuncompress -x -v /builddir/build/SOURCES/m3u8-3.1.0.tar.gz /usr/bin/gzip -dc '/builddir/build/SOURCES/m3u8-3.1.0.tar.gz' | /usr/bin/tar -xvvof - Which version of fedora-review and mock are you using? It might be another thing, but first thing to check. Kind regards, Mikel ___ 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: How to add epel9 branch to my package's git clone?
Hi Barry, Hau idatzi du Barry Scott (ba...@barrys-emacs.org) erabiltzaileak (2022 abu. 7, ig. (10:40)): > > I want to build my packages for epel9. But that branch is not setup in git. > > https://src.fedoraproject.org/rpms/python-pycxx > > How do I add epel9? You need to request the branch to be created by using fedpkg: fedpkg request-branch epel9 or fedpkg request-branch --repo python-pycxx epel9 Kind regards, Mikel ___ 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: Self Introduction: mczernek
Hi Marek! Welcome to Fedora! Hau idatzi du Marek Czernek (mczer...@redhat.com) erabiltzaileak (2022 uzt. 17, ig. (10:09)): > > I work as a developer for Red Hat training. As part of our work, we write > both code and > a lot of English text, which means we want to have linters for both :). > Several of my colleagues > started using Vale, and so I thought I'd package it for Fedora to make the > installation > on RPM systems easier. That's great, this kind of efforts make everyone's life easier. > Hope I'll be able to contribute to the Fedora ecosystem :). > You can see my RPM proposal at > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2107888 I did a fast review of the .spec, feel free to contact me directly if you have any question. I'm available on RH's gchat. Kind regards, Mikel ___ 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: Help with go spec file
Hi Mark, Hau idatzi du Mark E. Fuller (ful...@fedoraproject.org) erabiltzaileak (2022 eka. 3, or. (17:52)): > > Hi all, > > I'm fairly new to go and am looking to make a spec file and build > jsonnet (https://github.com/google/go-jsonnet/, https://jsonnet.org/). go-jsonnet is already packaged: https://src.fedoraproject.org/rpms/golang-github-google-jsonnet/ If you want to update or extend it, feel free to open a pull request. > 1) What is the preferred way to ignore (or remove) unnecessary > BUILD.bazel files? There is one in cmd/ which is obviously not a > buildable command, and so this results in an error in the naive use case. You can remove the files in the %prep section for example. > 2) How should nested folders in cmd/ be built? Here, again, the basic > template throws an error since cmd/internal contains no *.go files, only > a BUILD.bezel file and a nested cmd directory. Look at the spec file of the already packaged version. If something is missing you can add following the example. Kind regards, Mikel ___ 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: adeza - Alfredo Deza
Hi all, I tried to contact Alfredo by email using his RH's address, but got no answer from him nor a bounce from the server. It seems he has not been an employee since 2020. Checking with fedora_active_user: Last login in FAS: adeza 2019-12-16 ERROR:active-user:No such user: 'adeza' Opened a non-responsive check BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2087212 Does anyone know how to contact Alfredo by other means? Kind regards, Mikel Olasagasti (mikelo2) ___ 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: bodhi update in a crazy state
Hi Richard, Can you try to unpush from testing and then re-push? https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JF2PBQCZOL6MTWQUXEV3GJ7REGL2ITL3/ Kind regards, Mikel Hau idatzi du Richard W.M. Jones (rjo...@redhat.com) erabiltzaileak (2022 mai. 12, og. (09:36)): > > > https://bodhi.fedoraproject.org/updates/FEDORA-2022-3a7569aa77 > > Every day it tries to push it to stable, every day that fails. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > nbdkit - Flexible, fast NBD server with plugins > https://gitlab.com/nbdkit/nbdkit > ___ > 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 ___ 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: Strange messages in Bodhi (ejected from push?)
Hi Ron, Hau idatzi du Ron Olson (tachokni...@gmail.com) erabiltzaileak (2022 mai. 9, al. (22:15)): > > Hi all- > > I got several strange messages on my update here: > > https://bodhi.fedoraproject.org/updates/FEDORA-2022-bf60d68bdc > > The (multiple) messages suggest the update was ejected, but I tested an > install on a fresh image of 35 and 5.6.1 installed fine. Did I do something > wrong? Can you try with: koji tag-build f36-updates-candidate swift-lang-5.6-1.fc36 This has been reported in the past and there was a bug report that is marked as fixed: https://pagure.io/releng/issue/10590 Kind regards, Mikel ___ 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: Non-responsive maintainer check: rkarsten - Karsten Hopp
Karsten responded, closing the non-responsive check BZ. Hau idatzi du Mikel Olasagasti (mi...@olasagasti.info) erabiltzaileak (2022 mai. 5, og. (14:53)): > > Hi all, > > I tried to contact Karsten twice by email, but got no answer from him. > > Checking with fedora_active_user: > > Last login in FAS: >karsten 2020-11-19 > > Last action on koji: >Fri, 25 Mar 2022 tag_package_owners entry created by humaton [still active] > > Last package update on bodhi: >2020-10-21 13:02:09 on package libcap-2.44-1.fc34 > > Opened a non-responsive check BZ: > > https://bugzilla.redhat.com/show_bug.cgi?id=2082128 > > Does anyone know how to contact Karsten by other means? > > Kind regards, > Mikel Olasagasti (mikelo2) ___ 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: rkarsten - Karsten Hopp
Hi all, I tried to contact Karsten twice by email, but got no answer from him. Checking with fedora_active_user: Last login in FAS: karsten 2020-11-19 Last action on koji: Fri, 25 Mar 2022 tag_package_owners entry created by humaton [still active] Last package update on bodhi: 2020-10-21 13:02:09 on package libcap-2.44-1.fc34 Opened a non-responsive check BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2082128 Does anyone know how to contact Karsten by other means? Kind regards, Mikel Olasagasti (mikelo2) ___ 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: ryansb - Ryan Brown
Hi all, I tried to contact moreutils-maintainers and got the following error for Ryan: (expanded from ): host mx2.redhat.com[10.11.203.6] said: 550 5.1.1 : Recipient address rejected: User unknown in local recipient table (in reply Checking with fedora_active_user: Last login in FAS: ryansb 2016-12-13 Last action on koji: Fri, 25 Mar 2022 tag_package_owners entry created by humaton [still active] Last package update on bodhi: 2016-01-25 17:50:52 on package openstack-heat-2015.1.2-2.fc23 Opened a non-responsive check BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2082125 If someone knows how to contact Ryan, please, let me know. Kind regards, Mikel Olasagasti (mikelo2) ___ 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
Intent to unretire subfinder
Hi all, I created all the required review BZs[1] with the idea to unretire subfinder[2]. dnsx tool will be packaged as required dependency. This effort will also bring back chaos-client named as golang-github-projectdiscovery-chaos-client[3], as I was not able to identify that it was packaged in the past under the name of chaos-client[4]. I realized about it by trying to add it to release-monitoring with the package name I defined for it. Kind regards, Mikel Olasagasti (mikelo2) [1] https://bugzilla.redhat.com/buglist.cgi?bug_id=2081284_id_type=anddependson=tvp_id=12589311# [2] https://src.fedoraproject.org/rpms/subfinder [3] https://src.fedoraproject.org/rpms/golang-github-projectdiscovery-chaos-client [4] https://src.fedoraproject.org/rpms/chaos-client ___ 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: Help with packaging golang binary: resolving dependencies
Hi Mark,
Hau idatzi du Mark E. Fuller (ful...@fedoraproject.org) erabiltzaileak
(2022 api. 23, lr. (20:06)):
>
> Hi all,
>
> I'm looking to submit a first golang package for review, but I'm running
> into some confusion as to whether there's a way to download/import all
> the linked source dependencies without having to package all of those
> projects, too.
>
> To make this more concrete:
>
> My spec is at
> https://download.copr.fedorainfracloud.org/results/fuller/test-builds/fedora-rawhide-x86_64/04306641-golang-github-task/task.spec
>
> There are three other sources on which it depends, none of which are
> already packaged for Fedora, so the build log
> (https://download.copr.fedorainfracloud.org/results/fuller/test-builds/fedora-rawhide-x86_64/04306641-golang-github-task/builder-live.log.gz)
> shows:
>
> No matching package to install: 'golang(github.com/go-task/slim-sprig)'
> No matching package to install: 'golang(github.com/mattn/go-zglob)'
> No matching package to install: 'golang(github.com/radovskyb/watcher)'
> Not all dependencies satisfied
> Error: Some packages could not be found.
>
> Copr build error: Build failed
>
>
> I tried also explicitly adding the other repos as sources, but this
> didn't seem to fix the problem either, i.e.:
>
> ...
> Source0:%{gosource}
> Source1:https://github.com/go-task/slim-sprig/archive/master.tar.gz
> Source2:
> https://github.com/radovskyb/watcher/archive/refs/tags/v1.0.7.tar.gz
> Source3:https://github.com/mattn/go-zglob/archive/master.tar.gz
> ...
You need to create a package for each of the dependencies first and
you need to submit them first for review. The Source method you're
trying to use won't work.
You can use `go2rpm -r $name` to create the specs for each of the
packages easily and adapt in case of need.
As you're using copr, create a package for each dependency and you
should be able to build the final package once everything is ready.
Kind regards,
Mikel
___
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: Package downgrades on upgrade from F35 to F36 + categorized list
Hau idatzi du Fabio Valentini (decatho...@gmail.com) erabiltzaileak (2022 mar. 18, or. (14:33)): > > Hi all, > > - gojq-0:0.12.7-1.fc35 > gojq-0:0.12.6-2.fc36 > Version 0.12.7 was built for F35+, but no bodhi update for F36 was submitted. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6c128bd588 > - libtree-ldd-0:3.1.0-1.fc35 > libtree-ldd-0:3.0.2-2.fc36 > Version 3.1.0 was built for F36, but no bodhi update was submitted. https://bodhi.fedoraproject.org/updates/FEDORA-2022-76757d3be2 ___ 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 request: Go packages required by Hugo
Hi Mike, If you're not in a hurry I can review them in the upcoming days. Kind regards, Mikel Hau idatzi du W. Michael Petullo (m...@flyn.org) erabiltzaileak (2022 mar. 9, az. (04:40)): > > I would like to update Fedora's Hugo package, but the recent versions > depend on Go packages not yet in Fedora. I have submitted review requests > for each of these: > > https://bugzilla.redhat.com/show_bug.cgi?id=1998878 > https://bugzilla.redhat.com/show_bug.cgi?id=2031226 > https://bugzilla.redhat.com/show_bug.cgi?id=2031239 > https://bugzilla.redhat.com/show_bug.cgi?id=2031582 > https://bugzilla.redhat.com/show_bug.cgi?id=2031583 > https://bugzilla.redhat.com/show_bug.cgi?id=2031584 > https://bugzilla.redhat.com/show_bug.cgi?id=2031585 > https://bugzilla.redhat.com/show_bug.cgi?id=2060710 > https://bugzilla.redhat.com/show_bug.cgi?id=2060711 > > Additionally, I submitted a pull request for > golang-github-frankban-quicktest, which is also required by Hugo: > > https://src.fedoraproject.org/rpms/golang-github-frankban-quicktest/pull-request/1 > > Would anyone be interested in reviewing these? > > This is all summarized at: > > https://bugzilla.redhat.com/show_bug.cgi?id=1930952 > > -- > Mike > > :wq > ___ > 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 ___ 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: debug_package when using go_generate_buildrequires
Hi Fabio, Hau idatzi du Fabio Valentini (decatho...@gmail.com) erabiltzaileak (2021 abe. 10, or. (23:46)): > > On Fri, Dec 10, 2021 at 4:25 AM Maxwell G via devel > wrote: > > > > I am forwarding this to devel@, because I am reviewing this package and > > would also like a response. > > > > Thanks, > > Maxwell > > I remember a similar problem. Can you try adding an empty %build scriptlet? It did not work for me. Mikel ___ 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
License change: linode-cli
Hi all, Just updated linode-cli to use the new v4 client that changed the license to BSD. Kind regards, Mikel Olasagasti (mikelo2) ___ 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: Calling on all Thinkpad T490 users...
Hau idatzi du Chris Murphy (li...@colorremedies.com) erabiltzaileak (2021 aza. 23, ar. (20:39)): > > On Tue, Nov 23, 2021 at 2:26 PM Mikel Olasagasti > wrote: > > > > HI Chris, > > > > Hau idatzi du Chris Murphy (li...@colorremedies.com) erabiltzaileak > > (2021 aza. 23, ar. (20:20)): > > > > > > Hi, > > > > > > Question: > > > Do you have a T490 laptop successfully booting Fedora 34 or 35? And > > > did it get Fedora by upgrade or clean install? > > > > I've a T490s that started with F31 and I've been updating releases to > > F35 without issues. > > What do you get for > > dmesg | grep 'DMI:' $ dmesg |grep "DMI:" [0.00] DMI: LENOVO 20NYS41L02/20NYS41L02, BIOS N2JET93W (1.71 ) 11/04/2020 ___ 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: Calling on all Thinkpad T490 users...
HI Chris, Hau idatzi du Chris Murphy (li...@colorremedies.com) erabiltzaileak (2021 aza. 23, ar. (20:20)): > > Hi, > > Question: > Do you have a T490 laptop successfully booting Fedora 34 or 35? And > did it get Fedora by upgrade or clean install? I've a T490s that started with F31 and I've been updating releases to F35 without issues. -- Mikel ___ 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: [RFC] PyDrive2 and dependency backporting
Hi all, Hau idatzi du Mikel Olasagasti (mi...@olasagasti.info) erabiltzaileak (2021 aza. 10, az. (11:34)): > My plan would be: > > 1) Notify maintainers of those 5 packages about > python3-google-api-client update. > 2) Backport python3-google-auth-httplib2 and python3-google-api-client > to F35 and F34. > 3) Add PyDrive2 to F35 and F34. > 4) Ask deja-dup maintainers to switch to PyDrive2. > 5) Deprecate PyDrive in rawhide. Adding Obsolete to PyDrive2 may not > be required?. I sent two mails to the maintainers of affected packages. fence-agents maintainer confirmed that works with 2.30 and python3-certbot-dns-google maintainer confirmed upstream is testing with 2.20 so it should safe with a later release. Unless the other maintainers say something, tomorrow I'll create a side-tag for steps 2, 3 and 4. Kind regards, Mikel Olasagasti (mikelo2) ___ 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: Ownership of orphaned package perl-WebService-Dropbox
Hi Martin, You need to follow the steps described in "Claiming Ownership of a Retired Package" https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming Kind regards, Mikel Olasagasti Hau idatzi du Martin Gansser (marti...@fedoraproject.org) erabiltzaileak (2021 aza. 12, or. (10:59)): > > Hi, > > I want to take ownership of perl-WebService-Dropbox it's needed by shutter > for rawhide. > > https://bugzilla.redhat.com/show_bug.cgi?id=2022634 > https://src.fedoraproject.org/rpms/perl-WebService-Dropbox > > What have I to do ? > > Regards > Martin > ___ > 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 ___ 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
[RFC] PyDrive2 and dependency backporting
Hi all, tl;dr: Backups with deja-dup to GDrive require PyDrive2 that requires some dep updates not available in F35 or F34 The backup software deja-dup[1] can backup to Google Drive using PyDrive. PyDrive has been archived[2] by Google and PyDrive2[3] is an active fork. There is a bug in PyDrive causing issues[4][5][6] to backup to GDrive that PyDrive2 has solved. deja-dup is ready to work with PyDrive2. PyDrive2 is now available in rawhide[7], after updating some deps[8][9] and I would like to backport these to F35 and, if possible also, F34 without breaking something. I created a copr repo[10] and some users reported that it is working fine for them in F34. Only deja-dup depends on PyDrive: # dnf repoquery --disablerepo="*" --enablerepo=rawhide --whatrequires "python3-PyDrive" deja-dup-0:42.8-1.fc36.x86_64 PyDrive2 requires google-api-python-client that requires google-auth-httplib2. Only google-api-python-client depends on google-auth-httplib2: # dnf repoquery --disablerepo="*" --enablerepo=rawhide --whatrequires "python3-google-auth-httplib2" python3-google-api-client-2:2.29.0-1.fc36.noarch But more packages depend on google-api-python-client: # dnf repoquery --disablerepo="*" --enablerepo=rawhide --whatrequires "python3-google-api-client" fence-agents-gce-0:4.10.0-3.fc35.noarch goobook-0:3.5-4.fc35.noarch nodepool-0:3.13.1-1.fc36.noarch python3-PyDrive-0:1.3.1-18.fc35.noarch python3-certbot-dns-google-0:1.20.0-1.fc36.noarch Current release for python3-google-api-client in Fedora 35 and 34 is 1.6.7. Version 2.0.0 was released in 2021-03[11] and the only breaking change is the deprecation of python2 and <3.6[12]. We've 2.29 in rawhide and I would like to backport it to F35 and F34 releases based in the following facts: a) google-api-python-client's upgrading guide[13] states that version 2.x is compatible with 1.x: "Existing code written for earlier versions of this library will not require updating.". b) Package dependencies: - fence-agents-gce: it doesn't require a specific version. https://github.com/ClusterLabs/fence-agents/blob/master/agents/gce/fence_gce.py - goobook: google-api-python-client >=1.7.12 https://gitlab.com/goobook/goobook/-/blob/master/setup.py#L39 - nodepool: google-api-python-client https://opendev.org/zuul/nodepool/src/branch/master/requirements.txt#L20 - python3-certbot-dns-google: google-api-python-client >= 1.5.5 https://github.com/certbot/certbot/blob/master/certbot-dns-google/setup.py#L10 My plan would be: 1) Notify maintainers of those 5 packages about python3-google-api-client update. 2) Backport python3-google-auth-httplib2 and python3-google-api-client to F35 and F34. 3) Add PyDrive2 to F35 and F34. 4) Ask deja-dup maintainers to switch to PyDrive2. 5) Deprecate PyDrive in rawhide. Adding Obsolete to PyDrive2 may not be required?. @fedora-devel: what do you think? Should I do something else? Should this be backported only to F35? Kind regards, Mikel Olasagasti [1] https://src.fedoraproject.org/rpms/deja-dup/ [2] https://github.com/googlearchive/PyDrive/commit/42022f9a1c48f435438fce74ad4032ec9f34cfd1 [3] https://github.com/iterative/PyDrive2 [4] https://bugzilla.redhat.com/show_bug.cgi?id=1882028 [5] https://bugzilla.redhat.com/show_bug.cgi?id=2015282 [6] https://bugzilla.redhat.com/show_bug.cgi?id=1830874 [7] https://bodhi.fedoraproject.org/updates/FEDORA-2021-048f1421fe [8] https://src.fedoraproject.org/rpms/google-api-python-client/pull-request/3 [9] https://src.fedoraproject.org/rpms/google-auth-httplib2/pull-request/1 [10] https://copr.fedorainfracloud.org/coprs/mikelo2/PyDrive2/ [11] https://github.com/googleapis/google-api-python-client/releases/tag/v2.0.0 [12] https://github.com/googleapis/google-api-python-client/pull/961 [13] https://github.com/googleapis/google-api-python-client/blob/main/UPGRADING.md ___ 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: Fedora 35 - gedit
Hi Mischa, Hau idatzi du Michael J. Baars (mjbaars1977.fedora.de...@gmail.com) erabiltzaileak (2021 aza. 9, ar. (10:14)): > > Hi All, > > I've been working with Fedora for years now, and I just installed the newest > Fedora Workstation 35 on one of my computers. > > Since I use gedit a lot for editing source codes, gedit was one of the first > programs I tried to launch. Now, there I get into trouble. After opening a few > source files and trying to start off where I left, I noticed that the mouse > pointer (and the line number) often does not end up where I clicked the mouse > when > trying to position the cursor (for cutting and pasting for example). This is > the very first time that I experience this problem. This happened to me also with Fedora 34. I switched to gnome-text-editor's flatpak as gedit replacement and, although is not a complete replacement, it has some nice features. Kind regards, Mikel ___ 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: Woah! [Thanks, Nest sponsors]
I was expecting some nice stickers too, but after your email, I was intrigued. I just opened the package and woah! Thanks everyone that made it possible! Mikel Hau idatzi du Michael J Gruber (m...@fedoraproject.org) erabiltzaileak (2021 urr. 12, ar. (15:29)): > > Today that special package for Nest participants arrived here. > Back then I thought: "Nice, a few stickers." Today, after opening the > package, I thought: "Woah!". [ No spoilers here ;) ] > > So, thanks to anyone who made possible Nest as well as this form of community > appreciation! > > [posting it here where I learned about Nest; feel free to redirect] > ___ > 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 ___ 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
Packager mail bounce: pgier
Hi, I contacted the maintainers of a golang package using $package-maintain...@fedoraproject.org and got a bounce response from an email that I understand is part of go-sig: ext-mx.corp.redhat.com[10.4.204.10] said: 554 5.7.1 : Recipient address rejected: Access denied (in reply to RCPT TO command) I've checked RH's Rover/LDAP and it seems Paul doesn't continue at Red Hat. I've checked activity with fedora-active-user and last FAS login was on 2019-04. Following the "Non-responsive maintainer policy" I filled https://bugzilla.redhat.com/show_bug.cgi?id=2011992 - As his mail doesn't work, should I still wait for a week to open the FESCo ticket? Kind regards, Mikel ___ 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 happened with sevctl?
Hi Fabio, Hau idatzi du Fabio Valentini (decatho...@gmail.com) erabiltzaileak (2021 ira. 8, az. (11:56)): > > I just noticed that the packages for the sevctl utility were orphaned. > Its addition to Fedora was widely publicized at the time, because we > were the first (?) distribution to include tools for working with AMD > SEV. It looks like ckuehl left Red Hat (?), and their packages were > orphaned as a result of that? I alerted a peer at Red Hat that works with those technologies. Lets see what happens. Kind regards, Mikel ___ 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
Unretiring python-port-for package
Hi all, A new release of pg_activity[1] has a dep on new package python-pytest-postgresql[2] that requires retired python-port-for[3] and new package python-mirakuru. Kind regards, Mikel [1] https://bugzilla.redhat.com/show_bug.cgi?id=1990722 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1991138 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1991096 [4] https://bugzilla.redhat.com/show_bug.cgi?id=1991135 ___ 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: Fedora elections voting now open
Hi Silvia, Hau idatzi du Silvia Sánchez (bhkoh...@gmail.com) erabiltzaileak (2021 mai. 27, og. (19:19)): > > > I tried to login to vote but I get a 400 error when I try. Had the same problem. I was able to workaround by login in bodhi[1] and returning to the voting page. Mikel [1] https://bodhi.fedoraproject.org/ ___ 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: Orphaning several packages
Hi Rick, Hau idatzi du Rick Elrod (codebl...@elrod.me) erabiltzaileak (2021 mai. 27, og. (13:53)): > - httpie (http CLI client) I can take this one, but I see Miro just? took ownership. Miro, if you're interested add me, mikelo2, as co-maintainer. I can take care of EPEL if needed. Kind regards, Mikel ___ 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: Orphaned packages looking for new maintainers
Hi all, Hau idatzi du Miro Hrončok (mhron...@redhat.com) erabiltzaileak (2021 mar. 8, al. (11:54)): > pg_activity orphan 2 weeks ago > pg_toporphan 2 weeks ago took these two. Kind regards, Mikel ___ 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
How to update to epel8-playground?
Hi all, This might be documented somewhere, but I was not able to find it. I've for example this package that has epel8-playground branch created[1] and I can `fedpkg build`[2], but when trying to `fedpkg update` I get the following error: Could not execute update: Could not generate update request: Cannot find release associated with build: endlessh-1.1-2.epel8.playground, tags: ['epel8-playground'] A copy of the filled in template is saved as bodhi.template.last I could publish the package for Fedora and EPEL-7 and EPEL-8. Am I doing something wrong or do I miss something? Kind regards, Mikel [1] https://src.fedoraproject.org/rpms/endlessh/tree/epel8-playground [2] https://koji.fedoraproject.org/koji/buildinfo?buildID=1655917 ___ 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 requests: virt-backup & chunkfs
Hau idatzi du Richard Shaw (hobbes1...@gmail.com) erabiltzaileak (2020 abe. 5, lr. (17:47)): > > Two pretty simple review requests. Reviewed & approved ___ 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
Non-responsive maintainer check: macermak
Hi all, In accordance with [1] this is a non-responsive maintainer check for Marek Cermak / macermak. Non-responsive bug: https://bugzilla.redhat.com/show_bug.cgi?id=1885788 Unactioned bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1618559 2018-08 Does anyone know how to contact Marek? Regards, Mikel [1] https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ ___ 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
