On 6/2/23 19:50, Ralph Bromley wrote:
This is a stupid bonehead idea, libreoffice is just too big to reliably run in
flatpak.
Plus what about java integration, guess the languagetool plugin wont work now
and I will have to use its stupud online version where you havwe to pay to add
words.
Oh
ould imagine that taking over maintenance of it is not an easy endeavor.
>
> Taking into consideration the circumstances explained in replies later, I can
> understand that hands were tied. Yet, the decision to stop shipping
> LibreOffice is one that affects future RHEL releases and Red Hat's cust
> Am 03.06.2023 um 05:11 schrieb Ralph Bromley :
>
> Look its not like I have not tried libreoffice as a flat but as of now it
> looks out of place, I can't even see the icons even when I use the default
> adwaita or breeze themes.
> How is this an improvement?
> I wanted to leave ubuntu
Look its not like I have not tried libreoffice as a flat but as of now it looks
out of place, I can't even see the icons even when I use the default adwaita or
breeze themes.
How is this an improvement?
I wanted to leave ubuntu because of crap like this, where they forced snaps
down my throat
This is a stupid bonehead idea, libreoffice is just too big to reliably run in
flatpak.
Plus what about java integration, guess the languagetool plugin wont work now
and I will have to use its stupud online version where you havwe to pay to add
words.
Oh well, back to debian.
lained in replies later,
I can understand that hands were tied. Yet, the decision to stop
shipping LibreOffice is one that affects future RHEL releases and Red
Hat's customers. Yet, the decision to orphan the LibreOffice stack of
packages affects a much larger group of users.
What will we ship i
tied. Yet, the decision to stop
shipping LibreOffice is one that affects future RHEL releases and Red
Hat's customers. Yet, the decision to orphan the LibreOffice stack of
packages affects a much larger group of users.
What will we ship in Fedora if we were to follow in Red Hat's footsteps
gt;> Package maintenance changes have never gone through change proposals.
> >>
> >
> > I am sorry, but this was made into a drama by the way this was
> executed. Surprise is the opposite of engagement and dropping a ton of
> packages and their dependencies and then announcing
On Fri, Jun 02, 2023 at 01:55:30AM +0200, Sandro wrote:
> However, it surprises me that for a package, that is part of the
> deliverables of Fedora releases, no coordination effort was made to
> transition the package from Red Hat maintenance to Fedora
> maintenance. I would even go as far as that
ckage maintenance changes have never gone through change proposals.
> >>
> >
> > I am sorry, but this was made into a drama by the way this was
> executed. Surprise is the opposite of engagement and dropping a ton of
> packages and their dependencies and then announcing
sorry, but this was made into a drama by the way this was executed.
> Surprise is the opposite of engagement and dropping a ton of packages and
> their dependencies and then announcing it is absolute surprise.
>
> This isn't just package maintenance. This is a major change in what is
dropping a ton of packages and
their dependencies and then announcing it is absolute surprise.
This isn't just package maintenance. This is a major change in what is
expected to be included in the next workstation editions with the removal
of expected functionality. If the packages are not picked up w
RPMS have recently been orphaned, and
I thought it would be good to explain the reasons
behind this.
The Red Hat Display Systems team (the team behind most of Red Hat’s desktop
efforts) has maintained the LibreOffice packages in Fedora for years as part of
our work to support LibreOffice for Red
Terry,
> I appreciate and am empathetic to all of those carrying the burden of this
> and the thousands of other RPM packages. As a users of Fedora + RPM Fusion +
> Cinnamon Desktop as my daily laptop driver since 2011, I love Fedora and am a
> heavy user of Flatpacks. So t
I appreciate and am empathetic to all of those carrying the burden of this
and the thousands of other RPM packages. As a users of Fedora + RPM
Fusion + Cinnamon Desktop as my daily laptop driver since 2011, I love
Fedora and am a heavy user of Flatpacks. So thank you all.
That said, I
Lets not make this a drama.
Package maintenance changes have never gone through change proposals.
> However, it surprises me that for a package, that is part of the
deliverables of Fedora releases, no coordination effort was made to
transition the package from Red Hat maintenance to Fedora
> Il 02/06/23 01:55, Sandro ha scritto:
> I'm having a bad feeling about Fedora future lately, seeing all these RH
> withdrawals from the project.
That escalated quickly, yes. More worryingly: It escalated non-openly and
non-collaboratively.
> I hope to be wrong. But could Fedora survive the
Damn thats a long list.
On 6/2/23 01:21, Kevin Kofler via devel wrote:
Gwyn Ciesla via devel wrote:
I've taken ownership of libreoffice for the time being, at least to keep
the lights on.
Also of the many dependencies?
As far as I can tell, from the list in the orphaned package report, all
Il 02/06/23 01:55, Sandro ha scritto:
>
> However, it surprises me that for a package, that is part of the
> deliverables of Fedora releases, no coordination effort was made to
> transition the package from Red Hat maintenance to Fedora maintenance. I
> would even go as far as that this should
I can help co-maintaining and I think I can bring another co-maintainer.
We've been creating custom libreoffice packages for a project so, we can
bring a little experience
El jue, 1 jun 2023 a las 14:17, Gwyn Ciesla via devel (<
devel@lists.fedoraproject.org>) escribió:
> I've taken
some arguments for preferring
native RPM packages over Flatpak packages. I'm not going to re-iterate
these. They can be looked up in the archive [1].
However, it surprises me that for a package, that is part of the
deliverables of Fedora releases, no coordination effort was made to
transition
Gwyn Ciesla via devel wrote:
> I've taken ownership of libreoffice for the time being, at least to keep
> the lights on.
Also of the many dependencies?
As far as I can tell, from the list in the orphaned package report, all
these are part of the LibreOffice stack:
> flute
Yes, sorry about that meant now of course
On Thu, Jun 1, 2023, 6:45 PM Demi Marie Obenour
wrote:
> On 6/1/23 15:59, Christian Schaller wrote:
> > On Thu, Jun 1, 2023 at 2:36 PM Demi Marie Obenour >
> > wrote:
> >> Why is a Flatpak a better choice for LibreOffice?
> >
> > There are a lot of
On 6/1/23 15:59, Christian Schaller wrote:
> On Thu, Jun 1, 2023 at 2:36 PM Demi Marie Obenour
> wrote:
>> Why is a Flatpak a better choice for LibreOffice?
>
> There are a lot of ways to answer this, but from any upstream the advantage
> of Flatpak is that it means package once and then deploy
t;
> The Red Hat Display Systems team (the team behind most of Red Hat’s desktop
> efforts) has maintained the LibreOffice packages in Fedora for years as part
> of our work to support LibreOffice for Red Hat Enterprise Linux. We are
> adjusting our engineering priorities for RHEL
On Thu, Jun 1, 2023 at 2:36 PM Demi Marie Obenour
wrote:
>
>
> Why is a Flatpak a better choice for LibreOffice?
> --
> Sincerely,
> Demi Marie Obenour (she/her/hers)
>
There are a lot of ways to answer this, but from any upstream the advantage
of Flatpak is that it means package once and then
sktop
> efforts) has maintained the LibreOffice packages in Fedora for years as part
> of our work to support LibreOffice for Red Hat Enterprise Linux. We are
> adjusting our engineering priorities for RHEL for Workstations and focusing
> on gaps in Wayland, building out HDR su
Hey,
as you've probably seen, the LibreOffice RPMS have recently been orphaned, and
I thought it would be good to explain the reasons
behind this.
The Red Hat Display Systems team (the team behind most of Red Hat’s desktop
efforts) has maintained the LibreOffice packages in Fedora for years
Hi all,
I'm planning to do another round of removals of unused Rust crates -
at first. focusing only on compat packages which are no longer useful
since they have no remaining dependent packages in Rawhide.
This includes the gtk-rs v0.16 / gtk4-rs v0.5 compat packages:
- rust-atk0.16
- rust-atk
On Fri, May 26, 2023 at 10:10 PM Matthew Miller
wrote:
>
> On Thu, May 18, 2023 at 01:12:00PM +0200, Florian Weimer wrote:
> > I think this will make quite a few packages FTBFS on i686 because they
> > require pandoc at build time. It's not that many—I count ~75 that
>
On Thu, May 18, 2023 at 01:12:00PM +0200, Florian Weimer wrote:
> I think this will make quite a few packages FTBFS on i686 because they
> require pandoc at build time. It's not that many—I count ~75 that
Is there any reason to build docs for i686 packages? (With or without some
clev
Thanks, Florian, very good point.
On Thu, May 18, 2023 at 7:12 PM Florian Weimer wrote:
> I think this will make quite a few packages FTBFS on i686 because they
> require pandoc at build time. It's not that many—I count ~75 that
> build-depend on something pandoc-ish without a
* Jens-Ulrik Petersen:
> We have been building i386 packages for ghc and Haskell for a long
> time, but I think it is time to stop for Fedora 39. So as part of F39
> Haskell updates, I plan to disable 32bit ix86 builds across all the
> packages: I doubt anyone is still using them anyw
0, Miro Hrončok wrote:
> > The following packages are orphaned and will be retired when they
> > are orphaned for six weeks, unless someone adopts them. If you know
> > for sure
> > that the package should be retired, please do so now with a proper
&
ing packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know
> for sure
> that the package should be retired, please do so now with a proper
> reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
We have been building i386 packages for ghc and Haskell for a long time,
but I think it is time to stop for Fedora 39. So as part of F39 Haskell
updates, I plan to disable 32bit ix86 builds across all the packages: I
doubt anyone is still using them anyway.
Jens
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
.
--- Original Message ---
On Monday, May 15th, 2023 at 6:45 AM, Miro Hrončok wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please
On 15. 05. 23 15:09, Sandro wrote:
oclock orphan 107 weeks ago
I don't know how that got into the list. From what I understood [1] the package
was already orphaned and has recently been unretired after passing a re-review.
Due to the
On 15-05-2023 13:45, Miro Hrončok wrote:
Maelstrom
I took Maelstrom.
oclockorphan 107 weeks ago
I don't know how that got into the list. From what I understood [1] the
package was already orphaned and has recently been unretired after
On 15. 05. 23 14:40, Sérgio Basto wrote:
On Mon, 2023-05-15 at 14:31 +0200, Sandro wrote:
On 15-05-2023 14:25, Miro Hrončok wrote:
On 15. 05. 23 14:14, Sérgio Basto wrote:
Hi,
I see a lot of new packages , can we have a report what users
have been
removed ? please
I have no idea what you ask
On Mon, 2023-05-15 at 14:31 +0200, Sandro wrote:
> On 15-05-2023 14:25, Miro Hrončok wrote:
> > On 15. 05. 23 14:14, Sérgio Basto wrote:
> > > Hi,
> > > I see a lot of new packages , can we have a report what users
> > > have been
> > > removed
On 15-05-2023 14:25, Miro Hrončok wrote:
On 15. 05. 23 14:14, Sérgio Basto wrote:
Hi,
I see a lot of new packages , can we have a report what users have been
removed ? please
I have no idea what you ask for, sorry. What do you mean by "what users
have been removed"?
I think he's
On 15. 05. 23 14:14, Sérgio Basto wrote:
Hi,
I see a lot of new packages , can we have a report what users have been
removed ? please
I have no idea what you ask for, sorry. What do you mean by "what users have
been removed"?
--
Miro Hrončok
--
Phone: +420777974800
IRC
Hi,
I see a lot of new packages , can we have a report what users have been
removed ? please
Thank you
On Mon, 2023-05-15 at 13:45 +0200, Miro Hrončok wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopt
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
I'd like to take this two packages reviews and will review them in the next one
or two days.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
Hello,
I need help getting the following two Python packages reviewed – they
are dependencies of matrix-synapse:
* python-immutabledict
<https://bugzilla.redhat.com/show_bug.cgi?id=2182063>
* python-hiredis <https://bugzilla.redhat.com/show_bug.cgi?id=2182814>
Please let
https://bugzilla.redhat.com/show_bug.cgi?id=2063919
Jitka Plesnikova changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from
On Mon, May 01, 2023 at 10:26:27PM +0200, Miro Hrončok wrote:
ruby-augeas brandfbb, ignatenkobrain,0 weeks ago
orphan
Taken
___
devel mailing list -- devel@lists.fedoraproject.org
To
On Tue, May 02, 2023 at 12:24:35PM +0200, Miro Hrončok wrote:
> On 02. 05. 23 11:59, Richard W.M. Jones wrote:
> >However I think there is a problem in your script because there is no
> >direct dependency from qemu to ucs-miscfixed-opentype-fonts. Instead
> >what seems to be happening is that a
On 02. 05. 23 11:59, Richard W.M. Jones wrote:
However I think there is a problem in your script because there is no
direct dependency from qemu to ucs-miscfixed-opentype-fonts. Instead
what seems to be happening is that a binary subpackage of brltty
called brltty-xw does requires
S username and follow the dependency chain.
>
> So the one which appeared to break all the virt packages is
> 'ucs-miscfixed-fonts' which generates the single binary package
> 'ucs-miscfixed-opentype-fonts'.
>
> However I think there is a problem in your script because there is
On Mon, May 01, 2023 at 10:26:27PM +0200, Miro Hrončok wrote:
> Full report available at:
> https://churchyard.fedorapeople.org/orphans-2023-05-01.txt
> grep it for your FAS username and follow the dependency chain.
So the one which appeared to break all the virt packages is
'ucs-miscfi
I have adopted:
imapfilter
Will push an update shortly.
-- Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
I've taken the following:
mingw-gstreamer1
mingw-gstreamer1-plugins-base
python-flask-login
I'd also pick up the following if the gtk maintainers are not interested:
gtksourceviewmm3
Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
On 04-04-2023 09:45, Miro Hrončok wrote:
libunibreak orphan 3 weeks ago
I've taken libunibreak since coolreader depends on it. Will update to
latest release as time permits.
-- Sandro
___
devel
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
angé
> > > wrote:
> > > >
> > > > On Sun, Feb 20, 2022 at 10:13:18PM +0100, Sandro Mani wrote:
> > > > > Hi
> > > > >
> > > > > Following recent discussions and to reduce the maintenance burden, I'm
> > > > > planning to sta
On 06-03-2023 23:19, Miro Hrončok wrote:
python-managesieveorphan 0 weeks ago
I've taken managesieve.
-- Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
On Sat, 2023-03-04 at 02:25 +0100, Fabio Valentini wrote:
> On Sat, Mar 4, 2023, 02:21 Adam Williamson
> wrote:
>
> > On Fri, 2023-03-03 at 15:31 -0800, Adam Williamson wrote:
> > >
> > > Interestingly, this is only the case for the F38 update. Check the F39
> > > update:
> > >
On Sat, Mar 4, 2023, 02:21 Adam Williamson
wrote:
> On Fri, 2023-03-03 at 15:31 -0800, Adam Williamson wrote:
> >
> > Interestingly, this is only the case for the F38 update. Check the F39
> > update:
> > https://bodhi.fedoraproject.org/updates/FEDORA-2023-23789cd657
> >
> > it's *only* in
On Fri, 2023-03-03 at 15:31 -0800, Adam Williamson wrote:
>
> Interestingly, this is only the case for the F38 update. Check the F39
> update:
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-23789cd657
>
> it's *only* in @critical-path-build, it's not in @core or the kde,
> gnome or server
.
Thanks for the answer. I think it's:
# dnf install @critical-path-build
...
Installing group/module packages:
redhat-rpm-config
...
Installing dependencies:
pyproject-srpm-macros
...
So the question is: Are there test that test building RPM packages? If not, why
is @critical-path-buil
hat causes it to be in those groups? I
> > suspect it's something in the dep chain of pyproject-srpm-macros , but
> > at a quick glance I can't figure out what. If anyone has a good dep
> > visualizer they can throw at the problem it'd help, I guess.
>
> Thanks for the answer
spect it's something in the dep chain of pyproject-srpm-macros , but
at a quick glance I can't figure out what. If anyone has a good dep
visualizer they can throw at the problem it'd help, I guess.
Thanks for the answer. I think it's:
# dnf install @critical-path-build
...
Installing group/module package
On Fri, 2023-03-03 at 18:37 +0100, Miro Hrončok wrote:
> Hello,
> I've noticed in
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-f34afe57a9
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-a61dbc3c1d
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-a61dbc3c1d
>
> That the
Hello,
I've noticed in
https://bodhi.fedoraproject.org/updates/FEDORA-2023-f34afe57a9
https://bodhi.fedoraproject.org/updates/FEDORA-2023-a61dbc3c1d
https://bodhi.fedoraproject.org/updates/FEDORA-2023-a61dbc3c1d
That the update is marked as critpath (which is probably correct because
On Wed, Mar 01, 2023 at 01:58:05PM +, Richard W.M. Jones wrote:
> On Wed, Mar 01, 2023 at 01:45:11PM +, Daniel P. Berrangé wrote:
> > Our goal is to strongly encourage the use of integrated mingw packaging,
> > but still allow native package maintainers the discretion to opt-out of
> >
On Wed, Mar 01, 2023 at 01:45:11PM +, Daniel P. Berrangé wrote:
> Our goal is to strongly encourage the use of integrated mingw packaging,
> but still allow native package maintainers the discretion to opt-out of
> this if they feel strongly against handling mingw themselves. The keys
> terms
On Wed, Mar 1, 2023 at 7:45 AM Daniel P. Berrangé
wrote:
>
> Fast forward 6 months and evidentally no one else was enthusiastic about
> updating the MinGW packaging guidelines, so I've taken on that task myself
> :-)
>
Thanks for volunteering! I converted one of my packages bu
00, Sandro Mani wrote:
> > > > Hi
> > > >
> > > > Following recent discussions and to reduce the maintenance burden, I'm
> > > > planning to start merging native and mingw packages. Initially, I'll be
> > > > looking at these packages where I maintai
Btw, this is how I define my repo in the kickstart file:
repo --name=MyBaseRepo --baseurl=file:///home/itsme/rpmbuild/RPMS/$basearch
I have never had this issue before, even as recently as a week ago.
Thanks!
On Sunday, February 26, 2023 at 09:52:07 PM CST, Globe Trotter via devel
>
> And now, nothing from the local repo come in.
I guess that dnf doesn't know about the refreshed metadata/packages.
Have you tried running `dnf clean all` as the user that runs the
script?
___
devel mailing list -- devel@lists.fedoraproject.org
T
OK, I tried createrepo_c . but I get the same error.
Here is what I tried:
createrepo_c --update .
And now, nothing from the local repo come in.
Suggestions?
On Sunday, February 26, 2023 at 09:27:13 PM CST, Alexander Ploumistos
wrote:
On Mon, Feb 27, 2023 at 4:15 AM Globe
Alexander Ploumistos wrote:
> On Mon, Feb 27, 2023 at 4:15 AM Globe Trotter via devel
> wrote:
>> I wonder if anyone has any suggestions on how to get
>> around this problem. I create my local repo using
>>
>> createrepo .
>>
>> inside my RPMS/x86_64 directory.
>
> Is there a specific reason you
On Mon, Feb 27, 2023 at 4:15 AM Globe Trotter via devel
wrote:
> I wonder if anyone has any suggestions on how to get around this problem. I
> create my local repo using
>
> createrepo .
>
> inside my RPMS/x86_64 directory.
Is there a specific reason you are not using createrepo_c? Does that
:03 AM CST, Globe Trotter via devel
wrote:
Hello,
I was using livecd-creator, and I get the following for local recently rebuilt
packages, but not for those built a few weeks ago.
Specifically, I get:
Package "wbar-2.3.4-2.fc37.x86_64" from local repository "MyBaseRepo&
.. in case of parcellite, there's clearly active upstream working towards new
release 1.2.2 - so I fail to see any reason to think about orphan :)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
> lxsession-edit, lxpolkit is now built from lxsession.src.rpm, so no need for
> these
> anymore.
> parcellite is not in LXDE spin, LXDE spin uses clipit, so I did not take this.
Okay. Well, we should retire properly lxsession-edit and lxpolkit then. I've
taken both. As well, parcellite is
Hello,
I was using livecd-creator, and I get the following for local recently rebuilt
packages, but not for those built a few weeks ago.
Specifically, I get:
Package "wbar-2.3.4-2.fc37.x86_64" from local repository "MyBaseRepo" has
incorrect checksum
Error creat
Raphael Groner wrote on 2023/02/23 6:11:
Hi,
why are those packages orphan? lxsession-edit, lxpolkit and parcellite? Is LXDE
spin officially dead, what's current maintainer or do we still need mentioned
packages as additional option?
lxsession-edit, lxpolkit is now built from
> Think LXDE is pretty much dead and LXqt is much more alive as it seems now
That does not answer my question. Again: Who takes responsible for LXDE spin,
as we still have in Fedora officially?
___
devel mailing list -- devel@lists.fedoraproject.org
To
Hey!
Think LXDE is pretty much dead and LXqt is much more alive as it seems now
On 2/22/23, Raphael Groner wrote:
> Hi,
>
> why are those packages orphan? lxsession-edit, lxpolkit and parcellite? Is
> LXDE spin officially dead, what's current maintainer or do we still need
> men
Hi,
why are those packages orphan? lxsession-edit, lxpolkit and parcellite? Is LXDE
spin officially dead, what's current maintainer or do we still need mentioned
packages as additional option?
Regards, Raphael
___
devel mailing list -- devel
On Tue, 21 Feb 2023 at 12:40, Joseph Christopher Sible
wrote:
> Hello,
>
>
>
> I have a RHEL 9 system running PHP 8.1 from the Red Hat AppStream module.
> I tried to install php-sodium and php-pecl-imagick from EPEL 9 on it, but
> DNF gave an error that basically said tho
Hello,
I have a RHEL 9 system running PHP 8.1 from the Red Hat AppStream module. I
tried to install php-sodium and php-pecl-imagick from EPEL 9 on it, but DNF
gave an error that basically said those packages only work with PHP 8.0. Would
it be possible to provide versions of those packages
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
On 20-02-2023 08:39, Miro Hrončok wrote:
maildirproc orphan 0 weeks ago
Taken. I may have some personal use case for it.
-- Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note
the following code after find_package(cmocka):
if (TARGET cmocka::cmocka)
set(CMOCKA_LIBRARY cmocka::cmocka)
endif()
I did some repoquery and the following packages which use cmake and libcmocka
might need fixing:
drpm
freecell-solver
libavtp
libssh (maintained by me)
libyang
netdata
The only packages that would be retired are orphaned for 5 weeks already and
will be retired in (less than) a week. I decided not to bother with them
individually and let them be retired naturally.
https://bugzilla.redhat.com/buglist.cgi?bug_id=2140817,2140818,2140819
--
Miro Hrončok
--
Phone
On 11. 02. 23 14:02, Susi Lehtola wrote:
Hi,
it has so far taken two weeks of waiting to get the long-awaited libQGLViewer
update in Fedora. Since this is a soname bump, per Fedora policy the update will
take another week before it can be built in rawhide; the libQGLViewer maintainer
has now
701 - 800 of 13319 matches
Mail list logo
