Remmina orphaned and I would like to take it.
by Philip Wyett
On Wed, 2022-01-19 at 00:26 +0000, bugzilla(a)redhat.com wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=2031376
>
> Fedora Admin user for bugzilla script actions <fedora-admin-xmlrpc(a)fedoraproject.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Assignee|pahan(a)hubbitus.info |extras-orphan@fedoraproject
> | |.org
>
>
>
> --- Comment #6 from Fedora Admin user for bugzilla script actions <
> fedora-admin-xmlrpc(a)fedoraproject.org> ---
> This package has changed maintainer in Fedora. Reassigning to the new
> maintainer of this component.
>
>
Hi all,
It seems remmina has been orphaned (see above). I already package remmina personally for RHEL and
would be happy to package and maintain it for fedora, EPEL etc.
I am already in the packagers group and would only need to be given access.
Regards
Phil
--
*** Playing the game for the games own sake. ***
WWW: https://kathenas.org
Twitter: @kathenasorg
IRC: kathenas
GPG: 724AA9B52F024C8B
2 years, 2 months
Question on adding a new package to fedora
by Philip Cameron
I am working on getting the xtrkcad program into fedora. Using
https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Proc...
I have gotten to the point of creating a bug (2040728) for a new package review.
I am not sure how the process works going forward. So far there has been no action on the bug to get it reviewed. Does it usually take a while to get the review started? Do I need to inform someone to get this going? I am just looking for information on how the process works and what I need to do.
I know fedora36 is coming up. It would be good to get it into that but if I have missed dates it can wait for f37. I am not sure what the final date was/is for new packages.
Thanks!
Phil
2 years, 2 months
Self Introduction: Malcolm Inglis (mcinglis)
by Inglis, Malcolm
Hi Fedora developers,
I’m looking to join your ranks 😊 I’ve made a<https://pagure.io/user/mcinglis/requests?type=filed&status=all> few<https://src.fedoraproject.org/user/mcinglis/requests?type=filed&status=all> PRs already, and had mistakenly skipped this important step of introducing myself.
I’m a senior software engineer on the Amazon Linux team at AWS. I’m working on the infrastructure and tooling we use for AL packaging, and on maintenance of our user-space packages. I joined the AL team in Q3 2021 with much excitement for our direction regarding AL22<https://aws.amazon.com/linux/amazon-linux-2022/> and Fedora collaboration, and am continuing to support that direction internally. I’ve been at Amazon since 2016, having worked in internal developer tools organization for the majority of that time, specifically on the massive internal build system and on enabling AWS deployments for Amazon’s developers. Prior to Amazon, I’ve worked on software for solar power system logging and control, and on CRUD web development projects. I studied software engineering and mathematics at the University of Queensland for several years.
I’ve ran Fedora (Silverblue) as my daily driver on my laptop since at least 2011, though I experiment and dual boot various other distros on other machines (big fan of Guix, Alpine and OpenBSD). Fedora’s always been my trusty workhorse, though, and I’m ashamed that it’s taken me this long to start contributing to the project that I’ve gotten so much value from. Better late than never!
I live in Newcastle, WA, USA, and have lived in the Seattle area for the past six years. I’m originally from Brisbane, Australia. I have a website<http://minglis.id.au/> that’s been gathering dust, but am hoping to get around to that soon. Outside of software which I read and nerd about perhaps too much, I love going places and doing things with my family. I enjoy reading science fiction and history. I am interested in futurism, space exploration and human-scale urban design, and appreciate good coffee and dry wine.
Excited to get to work with you all,
Malcolm.
2 years, 2 months
Big Node.js jump coming to EPEL 7
by Stephen Gallagher
Last week, I retired the `nodejs` package from EPEL 7 because it was
(I believed) stuck on Node.js 6.x due to insufficient dependency
support. Apparently, this broke a few things like uglify-js[1], so I
spent today looking into whether I could get Node.js 16.x to work (the
latest LTS release) and it turns out that I can indeed bludgeon it
into working. I have a COPR[2] with a build of Node.js 16.x for EPEL 7
available to try while I await releng unretiring[3] the package.
Please note: Node.js 16.x is a SIGNIFICANT version jump. It is very
probably that some of your Node packages may not work properly against
it. I urge anyone who is maintaining any such packages in EPEL 7 to
try them out against the aforementioned COPR prior to my building it
in EPEL proper.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2041022
[2] https://copr.fedorainfracloud.org/coprs/sgallagh/nodejs_epel7/
[3] https://pagure.io/releng/issue/10541
2 years, 2 months
Rawhide kernel crash
by edmond pilon
Has anyone tried the last kernel-5.15.0-60.fc36.
I have crashes at boot with this kernel since rc7 , with nvidia rpmfusion drivers .
I think it's because of this fedora patch : fedora: Disable fbdev drivers and use simpledrm instead .
I sent a bug report but still no answer .
2 years, 2 months
Schedule for Tuesday's FESCo Meeting (2022-01-18)
by Miro Hrončok
Following is the list of topics that will be discussed in the
FESCo meeting Tuesday at 18:00UTC in #fedora-meeting on
irc.libera.chat.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2022-01-18 18:00 UTC'
Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda
= Discussed and Voted in the Ticket =
F36 Change: LLVM 14
https://pagure.io/fesco/issue/2726
APPROVED (+7,0,-0)
F36 Change: Ruby 3.1
https://pagure.io/fesco/issue/2727
APPROVED (+8,0,-0)
F36 Change: %set_build_flags for %build, %check, and %install phases
https://pagure.io/fesco/issue/2728
APPROVED (+7,0,-0)
F36 Change: Default To Noto Fonts
https://pagure.io/fesco/issue/2729
APPROVED (+5,0,-0)
F36 Change: Hunspell Dictionary dir change
https://pagure.io/fesco/issue/2730
APPROVED (+4,0,-0)
Nonresponsive maintainer: Mike xenithorb
https://pagure.io/fesco/issue/2696
APPROVED (+2,0,-0)
Nonresponsive maintainer: Dhiru Kholia halfie
https://pagure.io/fesco/issue/2718
self APPROVED by halfie
Nonresponsive maintainer: Rüdiger Landmann rlandmann
https://pagure.io/fesco/issue/2723
APPROVED (+3,0,-0)
Unresponsive Maintainer process - hubbitus (Pavel Alexeev)
https://pagure.io/fesco/issue/2724
APPROVED 4 years ago (+6, 0, -0)
APPROVED to orphan all packages etc. (+3,0,0)
= Followups =
#2711 F36 Change: Enable fs-verity in RPM
https://pagure.io/fesco/issue/2711
#2721 F36 Change: DIGLIM
https://pagure.io/fesco/issue/2721
#2731 F36 Change: Relocate RPM database to /usr
https://pagure.io/fesco/issue/2731
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda
If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
2 years, 2 months
Request assistance getting a package (usbrelay) into Fedora
by Darryl Bond
Hello,
I maintain a small application hosted on GitHub. (https://github.com/darrylb123/usbrelay)
It allows control of USB connected electrical relays. Originally it was a simple command line application.
Over the years, it has accumulated additional features such as a python interface, and an mqtt daemon.
There is a debian package that has not been maintained for many years. We are endeavouring to fix that.
As a long term Fedora user, I would love to get it into Fedora. However I have never attempted to create an rpm package. The more I read, the more confused I am.
Questions on Issues like:
- How to clone the GitHub repository in the spec file
- should there be one package or a separate python package.
- what about the daemon/ systemd service...
Any help greatly appreciated
Darryl
2 years, 2 months