Re: Announcement: pagure release 5.14.1 available
> On 05/24/2024 5:03 PM CEST Sérgio Basto wrote: > > > On Fri, 2024-05-24 at 16:55 +0200, Dominik Wombacher wrote: > > [4] https://src.fedoraproject.org/rpms/pagure > > good news and thanks, I want to test in my local machine, to do that I > need the package updated, please add some builds . > I finished the PR in parallel [1]. Builds and updates are submitted for the different branches. But keep in mind: 100% functionality on current Fedora and EL versions will be given with the major release 6.0. This intermediate 5.14.1 release is meant for everyone that has 5.13.3 already running to benefit from bug and security fixes. To do a new deployment I suggest EL8 with a hotfix [2] that is used be the Fedora Infra Team. Dom [1] https://src.fedoraproject.org/rpms/pagure/pull-request/8 [2] https://pagure.io/pagure/issue/5473#comment-912299 -- The Wombelix Post https://dominik.wombacher.cc -- ___ 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
Announcement: pagure release 5.14.1 available
Hi everyone, it's been a while and because of increasing requests and important security fixes we release pagure version 5.14.1 today! The release is build based on version 5.13.3 with 59 backports: - 13 features, 34 fixes, 4 security fixes and 8 improvements of the documentation. Checkout the changelog [1] for a full list with a brief description and links to the related pull request. I want to thank everyone who contributed [2] to pagure and made this release possible! You can download the source [3] and soon the update will arrive in the Fedora package [4] too. Please keep in mind that 5.14.1 doesn't contain breaking changes and is sort of an intermediate release. This means that the code base still contains python 2 code for example. That we still have some tech-dept and failing unit tests. Also it will most likely not run without issues on latest operating system and python versions. But where ever you run 5.13.3 today, then 5.14.1 will run on that system too :) All this will be addressed with the upcoming major release 6.0. This release will need a bit more time, so stay tuned for updates on that! Dom [1] https://pagure.io/pagure/blob/6b06ac585529c3087364a5ebe4fb9d7c20e3c872/f/doc/changelog.rst [2] https://pagure.io/pagure/blob/6b06ac585529c3087364a5ebe4fb9d7c20e3c872/f/doc/contributors.rst [3] https://pagure.io/pagure/releases [4] https://src.fedoraproject.org/rpms/pagure -- The Wombelix Post https://dominik.wombacher.cc -- ___ 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: Spec file using github repo - not tarball
> On 05/21/2024 5:54 PM CEST Tom Hughes via devel > wrote: > > The automatic tar ball URLs on github just do a git archive and are > separate to uploaded release artifacts. Just use a URL like: > >https://github.com/OWNER/PROJECT/archive/REVISION/NAME.tar.gz > > where tag can be any tag or head or commit hash. More here: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/#_commit_revision > I know that, but as shared, upstream has a .gitattributes [1] defined that sets export-ignore [2] for a majority of the repo content, including /tests/. They upload the same archive to the releases as they are generated by GitHub ad-hoc. So in both cases the files are missing and can't retrieved without a git clone. Dom [1] https://github.com/guzzle/guzzle/blob/7.8/.gitattributes [2] https://git-scm.com/docs/gitattributes#_export_ignore -- The Wombelix Post https://dominik.wombacher.cc -- ___ 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: Spec file using github repo - not tarball
> On 05/08/2024 10:38 PM CEST Tom Hughes via devel > wrote: > > > On 08/05/2024 21:36, Kenneth Goldman wrote: > > > Is it possible for a .spec file to clone a github.com repo rather than > > download a tarball? Can someone link to a working example? > > No, but github can give you a tar ball for any ref you want so why > would you need/want to? > I have a case were upstream excludes the test suite from the export [1]. But I want the tests to be part of the package build to validate that everything is fine. So this requires a bit of local git clone and create an own archive file. I can't just grab the archive from the GitHub release in that case. So that's a use-case were I could think of why git clone defined in a spec file would be handy. Dom [1] https://github.com/guzzle/guzzle/blob/7.8/.gitattributes -- The Wombelix Post https://dominik.wombacher.cc -- ___ 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: Intention to take over orphaned packages: php-aws-sdk3, php-ralouphie-getallheaders, php-guzzlehttp-guzzle6
> On 05/13/2024 12:29 PM CEST Remi Collet wrote: > > As I said, because of bundled libraries > OK, I work on packaging the AWS C libs right now that would otherwise bundled. So that problem should be solved / solvable in a couple of weeks. I would then like to give php-awscrt a try based on your existing work if that's fine for you. > > And also lack or PHP reviewers > I already have tons of packages waiting for review for months > Make sense, maybe we can help each other here? Happy to do some reviews and you might able to work on mine that coming up? :) Dom -- The Wombelix Post https://dominik.wombacher.cc -- ___ 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: calendar.fp.o pointing to obsolete IRC for meetings
On 5/3/24 8:00 PM, Kevin Fenzi wrote: > > So, help would definitely be welcome fixing the matrix/irc issues in the > code, and then we could look at mass updating it. > I briefly looked into it, can be an easy fix. I put a comment into the open issue for matrix support in fedocal: https://pagure.io/fedocal/issue/213 I suggest to label it as easyfix/good-first-issue and maybe someone is interested and has the time to work on it :) > Or perhaps we should be looking at retiring fedocal, but would probibly > want an open source alternative we could use or deploy. Are there other use-cases that are not covered by fedocal but urgently required? If the main pain points are minor issue like the matrix url support in the meeting location, I would suggest to fix the current code. That's then still much less time consuming compared to replacing it with something else. Dom -- The Wombelix Post https://dominik.wombacher.cc -- ___ 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
Looking for a Reviewer to un-retire php-psr-http-client
Hi everyone, I'm looking for help with my review request [1] for php-psr-http-client [2] as part of the process to un-retire [3] the package. It's a dependency of my work to update php-guzzlehttp-guzzle [4] to v7.x [5]. Which is required to keep php-aws-sdk3 [6] alive and up-to-date. Thanks in advance! Dom [1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2277764 [2] https://src.fedoraproject.org/rpms/php-psr-http-client [3] https://pagure.io/releng/issue/12089 [4] https://src.fedoraproject.org/rpms/php-guzzlehttp-guzzle [5] https://src.fedoraproject.org/fork/wombelix/rpms/php-guzzlehttp-guzzle/tree/feat_upgrade_to_7.8.1 [6] https://src.fedoraproject.org/rpms/php-aws-sdk3 -- The Wombelix Post https://dominik.wombacher.cc -- ___ 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
Self Introduction: Dominik Wombacher
Hey everyone, I met a few people already on Events, during the Job or by contributing to Pagure, Uyuni and some other projects. But I didn't properly introduced myself on the Fedora devel list, so here we go. My nickname for most accounts, including FAS, is wombelix, you can also call me Dom. I live in Germany and work as Sr. Partner Solutions Architect at AWS. I would describe myself as Open Source Enthusiast and Contributor, Dog Person and Passionate Engineer. I'm in IT my whole life and on/off contributor to different open source projects since a couple of years. Doing hands-on tech and devel stuff is what I enjoy most. Give me problems to solve so I can go down the rabbit hole of troubleshooting and debugging. Let me put some code and a fix together. That's how to make my happy. I had it on my bucket list for quite a while to do some packaging and learn some of the Spec magic. I finally got started and work on my first Fedora package. I'm looking for a Reviewer and Sponsor: https://bugzilla.redhat.com/show_bug.cgi?id=2274150 My intention is to work on a couple more AWS related packages and to see if there are some orphaned packages that are interesting. Dom -- The Wombelix Post https://dominik.wombacher.cc -- ___ 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
