Re: Orphaned my Ruby packages (Jekyll + dependencies)
Sad day indeed, but the situation is indeed a tough one. I also switched to bundler for similar reasons and pain for my jekyll sites. Thanks so much for your service Fabio! I don't have time/bandwidth to take over completely, but I could offer some assistance/backup if somebody else takes primary on them. Ben Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Saturday, February 13, 2021 12:29 PM, Fabio Valentini wrote: > Hi everybody, > > With a heavy heart, I have orphaned all my Ruby packages today. > > - rubygem-jekyll > - rubygem-jekyll-asciidoc (official, optional AsciiDoc support) > - rubygem-jekyll-feed (dep of the default theme) > - rubygem-jekyll-sass-converter (jekyll dep) > - rubygem-jekyll-seo-tag (dep of the default theme) > - rubygem-jekyll-toc (unofficial table of contents plugin) > - rubygem-jekyll-watch (jekyll dep) > - rubygem-kramdown-parser-gfm (kramdown support for GitHub-flavored > markdown) > - rubygem-kramdown-syntax-coderay (coderay syntax highlighting support) > - rubygem-liquid (jekyll dep, templating engine) > - rubygem-minima (jekyll default theme) > - rubygem-minitest-profile (test dependency for some of the other gems) > - rubygem-rouge (jekyll dep, default syntax highlighter, "compatible" > with pygments) > > - rubygem-ruby-progressbar > - rubygem-sassc (wrapper for C libsass, "official" successor of the > pure-ruby sass gem) > > - rubygem-stringex > - rubygem-tomlrb (optional jekyll dep, for TOML config file support in > addition to YAML) > > I originally took them or packaged them because I used Jekyll, but for > some time now, I have used bundler to manage the gems for my Jekyll > pages (because not all gems I needed were available on Fedora anyway, > and mixing and matching doesn't work well). > > There are some known issues with the packages: > > - Some of them are failing to build on Fedora 34 due to changes in > Ruby 3.0 (jekyll, jekyll-feed, liquid, stringex, tomlrb). > > - Jekyll test suite is failing due to changes in kramdown 2.2.0. > - Two of them are outdated (jekyll, tomlrb). jekyll 4.2.0 requires > tomlrb 2.0, but jekyll cannot be updated to 4.2.0 unless > terminal-table is updated to 2.0). > > Jekyll and liquid have some non-upstreamable downstream patches which > I used to maintain here: https://pagure.io/group/jekyll-fedora > > I have pushed the working patches I have for jekyll 4.2.0 there, and > submitted two final PRs for tomlrb and jekyll with the changes I had > prepared locally: > > - https://src.fedoraproject.org/rpms/rubygem-tomlrb/pull-request/2 > - https://src.fedoraproject.org/rpms/rubygem-jekyll/pull-request/6 > > The PRs are blocked by other missing updates for now. > > Big thanks to everybody who helped me with maintaining my Ruby > packages over the years. > Fabio > > > 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: Guidance on new package
Thanks Andy, that's helpful. Re: Matthew, at this point I only need one spec file version per Fedora/CentOS/RHEL version (mostly depends on which version of gcc is installed in the target distro), IOW it's totally fine for only one version to be available. With this package in the past they made a backwards incompatible change and major version bump that would break a lot of scripts. If that should happen again it *may* be a case where having a compat package or something makes sense. It's nothing like openssl was lol, but something I'm thinking about. It would be fairly trivial to just keep a single version in Fedora proper and then provide compat packages in a COPR repo too for the corner cases that might exist. Ben Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Tuesday, December 29, 2020 3:38 PM, Matthew Miller wrote: > On Tue, Dec 29, 2020 at 09:19:17PM +0000, FreedomBen via devel wrote: > > > rpmlint complains (which I fully expected from reading the packaging > > guidelines) about my spec file being named "pick-v4.0.0.spec" instead of > > "pick.spec". > > What's the best way to manage spec files for different versions? git tags > > in the repo? directories with version info? something else? > > Do you have a case where you want to support multiple versions of the > package at the same time? > > > --- > > Matthew Miller > mat...@fedoraproject.org > Fedora Project Leader > > 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 ___ 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: Guidance on new package
rpmlint complains (which I fully expected from reading the packaging guidelines) about my spec file being named "pick-v4.0.0.spec" instead of "pick.spec". What's the best way to manage spec files for different versions? git tags in the repo? directories with version info? something else? Ben Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐ Original Message ‐‐‐ On Monday, December 28, 2020 1:53 PM, Andy Mender wrote: > On Mon, 28 Dec 2020 at 21:12, FreedomBen via devel > wrote: > >> Hi all, >> >> I've read a crap ton of pages now about package creation/maintenance but >> feel like I'm missing stuff and spinning wheels so I wanted to ask. The >> process seems pretty muddled :-D >> >> I've got an RPM package I maintain called "pick" (I'm already working with >> the upstream project and have their blessing/encouragement to do this). It's >> a reasonably successful project that really should be in the official repos. >> Here's the upstream: https://github.com/mptre/pick >> >> Here's an example spec file I use. I have a scrip that generates these >> automa6tically based on the version available upstream: example spec file: >> https://github.com/FreedomBen/pick-rpm/blob/master/spec-files/pick-v4.0.0.spec >> >> The build of my build is this script >> (https://github.com/FreedomBen/pick-rpm/blob/master/build.sh) plus the >> Dockerfile (https://github.com/FreedomBen/pick-rpm/blob/master/Dockerfile). >> That's probably not relevant for what we're doing here, just wanted to share >> in case it's useful for somebody evaluating me ;-) >> >> I have a COPR repo now for "pick" here: >> https://copr.fedorainfracloud.org/coprs/freedomben/pick/: >> >> All my scripts I use to build RPMs are here. Basically I just use podman to >> crank out all versions. There's a script to generate a stand alone spec file >> as well (which is where the one above came from): >> https://github.com/freedomben/pick-rpm >> >> I want to get this package included in Fedora proper. I've never been a >> Fedora maintainer before but I'm a long time Fedora user and programmer and >> generally pretty good at stuff kind of guy. I'm mostly familiar with >> packaging guidelines, though I'm not an expert on the various macros (yet). >> >> Is there someone who can guide me on what to do next? Or who will sponsor me? >> >> Thanks in advance, >> >> Ben > > Hello Ben! > > I see "pick" is available on quite some platforms! :) > The simplest approach would be to submit a request to add your package to > Fedora at: https://bugzilla.redhat.com/ > Here are the links I usually use for reference: > - On becoming a packager: > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=PackageMaintainers/Join > - Packaging Guidelines: > https://docs.fedoraproject.org/en-US/packaging-guidelines/ > - An in-depth guide to RPM packaging (slightly outdated, but still useful): > http://ftp.rpm.org/max-rpm/ > - On getting sponsored: > https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group > > You're already on the right track with your SPEC file from what I saw. What > I'd recommend is the following: > 1. Read through the above docs to make sure you have all the necessary tools > like "fedora-review", "rpmlint", "mock" and "rpmbuild". > 2. Generate a RPM and SRPM of your package and check it with the above tools > to make sure it's clean. > 3. Submit a review request to https://bugzilla.redhat.com/ and mark your > request as blocking the FE-NEEDSPONSOR tracker so that people are aware that > sponsorship is required. Be sure to link the SPEC file, a SRPM generated via > "rpmbuild" and a successful Koji scratch build (not mandatory, but it helps). > 4. Wait for someone to pick up your request and join us ;). > > Cheers, > Andy___ 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
Guidance on new package
Hi all, I've read a crap ton of pages now about package creation/maintenance but feel like I'm missing stuff and spinning wheels so I wanted to ask. The process seems pretty muddled :-D I've got an RPM package I maintain called "pick" (I'm already working with the upstream project and have their blessing/encouragement to do this). It's a reasonably successful project that really should be in the official repos. Here's the upstream: https://github.com/mptre/pick Here's an example spec file I use. I have a scrip that generates these automa6tically based on the version available upstream: example spec file: https://github.com/FreedomBen/pick-rpm/blob/master/spec-files/pick-v4.0.0.spec The build of my build is this script (https://github.com/FreedomBen/pick-rpm/blob/master/build.sh) plus the Dockerfile (https://github.com/FreedomBen/pick-rpm/blob/master/Dockerfile). That's probably not relevant for what we're doing here, just wanted to share in case it's useful for somebody evaluating me ;-) I have a COPR repo now for "pick" here: https://copr.fedorainfracloud.org/coprs/freedomben/pick/: All my scripts I use to build RPMs are here. Basically I just use podman to crank out all versions. There's a script to generate a stand alone spec file as well (which is where the one above came from): https://github.com/freedomben/pick-rpm I want to get this package included in Fedora proper. I've never been a Fedora maintainer before but I'm a long time Fedora user and programmer and generally pretty good at stuff kind of guy. I'm mostly familiar with packaging guidelines, though I'm not an expert on the various macros (yet). Is there someone who can guide me on what to do next? Or who will sponsor me? Thanks in advance, Ben___ 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
Self introduction: Ben Porter
Hi all, My name is Ben Porter. I've been a Fedora user since the Gnome 2 days (Fedora 13). I used to distro hop a lot but always ended up back on Fedora due to a high level of alignment on philosophy between myself and the Fedora Project. I did have a sordid love affair with Arch for a few years on my personal laptop/desktop (although after about 6 months on Arch I came crawling back to "Beefy Miracle" when an X update trashed my system at the worst possible time. After that Fedora ran my work machine always). Around 2016 I nuked and paved the last remaining non-Fedora machine. My background is in primarily software development all over the tech stack. C/C++, Ruby, JavaScript, Elixir, Go, and a few others. I've always been kind of a backend/infrastructure kind of guy but working at various startups I've had to wear hats. I'm a security nerd too. I did my masters in Cyber-security and typically specialize in security aspects of whatever product I'm working with. I did an associates in electrical engineering and worked as a hardware tech for a few years while getting a CS degree so I have an interest in hardware too. My current day job is as an architect for Red Hat doing OpenShift stuff. That includes a lot of automation, some development, and lots of architecture planning. After many years of thinking about it, I'm finally getting involved in Fedora. I maintain a couple of RPM packages, one of which I want to get included in the repos because it belongs there (source is here: https://github.com/FreedomBen/pick-rpm). I expect to have to change stuff to make it work with Fedora's automated system but currently I just use Podman to crank out the builds. Besides maintaining that rpm package, I'm pretty open to helping out with other stuff time permitting. Here's my github if you want to look at some stuff I've done: https://github.com/freedomben Anyway, I'm excited to be here and hopeful that I can do something to improve the best distro there is. If you need help with something hit me up and we can chat about it to see if I'd be a good fit. Looking forward to "meeting" you, Ben___ 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
