Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1911070 - F34FailsToInstall: orage
Summary: F34FailsToInstall: orage
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: orage
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mukundan Ragavan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F34FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2020-12-27 12:02 UTC by Miro Hrončok
Modified: 2021-01-04 23:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-04 23:04:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2020-12-27 12:02:19 UTC
Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

Your package (orage) Fails To Install in Fedora 34:

can't install orage:
  - nothing provides libxfce4panel-1.0.so.4()(64bit) needed by orage-4.12.1-16.fc33.x86_64
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.

P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors.

P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/

Thanks!

Comment 1 Mukundan Ragavan 2020-12-27 15:24:47 UTC
I think orage should be obsoleted by panel.

Kevin, what do you think?

Comment 2 Kevin Fenzi 2020-12-27 18:29:14 UTC
+1 sounds good to me.

Comment 3 Mukundan Ragavan 2020-12-27 23:29:25 UTC
Okay, I will push this to xfce4-panel git and obsolete orage from there.

We should probably retire orage. I think timedate plugin provides equivalent functionality.

Comment 4 Ian Laurie 2021-01-04 03:08:58 UTC
>I think timedate plugin provides equivalent functionality.

This is not my understanding, at least not with the current version in Rawhide.  Neither Clock nor DateTime has this functionality.  Orage comes with its own panel plugin which launches when you use orage and [of course] has orage integration.

Unless I am seriously missing something, orage is not obsolete.

Comment 5 Mukundan Ragavan 2021-01-04 09:43:53 UTC
(In reply to Ian Laurie from comment #4)
> >I think timedate plugin provides equivalent functionality.
> 
> This is not my understanding, at least not with the current version in
> Rawhide.  Neither Clock nor DateTime has this functionality.  Orage comes
> with its own panel plugin which launches when you use orage and [of course]
> has orage integration.
> 

yeah sure. it also has world clock. My point was that timedate plugin has the same clock/calendar functionality.


> Unless I am seriously missing something, orage is not obsolete.

well, as far as I know, orage is not maintained upstream anymore. The git repo (old one) had only received translation commits for a while and even that stopped in mid-2019.

Do you know if it works *with xfce 4.16*? I am not too keen on carrying too old plugins - if I can avoid it.

Comment 6 Mukundan Ragavan 2021-01-04 10:03:11 UTC
I just did a quick check (not thorough by any stretch) - orage application itself compiles against panel-2 (4.16.x). It works fine as well.

But, the panel plugin seems to fail ...

-BuildRequires:  pkgconfig(libxfce4panel-1.0) >= 4.6.0
+BuildRequires:  pkgconfig(libxfce4panel-2.0) >= 4.6.0

RPM build errors:
    File not found: /builddir/build/BUILDROOT/orage-4.12.1-16.fc33.x86_64/usr/lib64/xfce4/panel/plugins/liborageclock.so

Comment 7 Kevin Fenzi 2021-01-04 17:01:12 UTC
Thats because configure is looking for the old panel config.

"* LIBXFCE4PANEL support:     no, not building xfce panel plugin"

You can try patching configure to look for the new one, but I there is likely further issues. Might be worth a try at least. 

Ah, thats easy enough to try, so I just did. It (as expected) blows up all over the place. It needs porting to the new panel api/toolkit. 

I suppose we could drop the panel plugin and keep the rest for now?
Or just drop it all?

Comment 8 Mukundan Ragavan 2021-01-04 19:19:08 UTC
(In reply to Kevin Fenzi from comment #7)
> Thats because configure is looking for the old panel config.
> 
> "* LIBXFCE4PANEL support:     no, not building xfce panel plugin"
> 
> You can try patching configure to look for the new one, but I there is
> likely further issues. Might be worth a try at least. 
> 

I did.

> Ah, thats easy enough to try, so I just did. It (as expected) blows up all
> over the place. It needs porting to the new panel api/toolkit. 
> 

I was trying to cheat by not changing the configure.

> I suppose we could drop the panel plugin and keep the rest for now?
> Or just drop it all?

We should drop it. Orage is dead.

https://wiki.xfce.org/releng/4.14/roadmap

orage		Archived	0%, Never

I finally remembered where I saw about orage.

Comment 9 Mukundan Ragavan 2021-01-04 19:21:10 UTC
(In reply to Mukundan Ragavan from comment #8)
> (In reply to Kevin Fenzi from comment #7)

> 
> > Ah, thats easy enough to try, so I just did. It (as expected) blows up all
> > over the place. It needs porting to the new panel api/toolkit. 
> > 
> 
> I was trying to cheat by not changing the configure.
> 

i.e. tried providing "some" panel support. no dice.

Comment 10 Ian Laurie 2021-01-04 22:50:57 UTC
If upstream has killed it then it should be dropped, I hadn't realized it was dead upstream, I thought it was an easy to fix Rawhide compose issue.


Note You need to log in before you can comment on or make changes to this bug.