Bug 1005550 - arched rpm ships HUGE noarch data
Summary: arched rpm ships HUGE noarch data
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wordnet
Version: 22
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Björn 'besser82' Esser
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-08 09:57 UTC by Björn 'besser82' Esser
Modified: 2018-04-11 10:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:58:35 UTC
Type: Bug


Attachments (Terms of Use)
suggested patch (1.99 KB, patch)
2015-02-03 14:07 UTC, Matěj Cepl
no flags Details | Diff

Description Björn 'besser82' Esser 2013-09-08 09:57:23 UTC
Description of problem:

  The arched wordnet-3.0-19.$arch rpm ships ~ 40 MBytes of noarch data located
  inside %{_datadir}/%{name}%{version}.


Version-Release number of selected component (if applicable):

  wordnet-3.0-19.fc*


How reproducible:

  100%


Steps to Reproduce:

  1. rpmls wordnet
  2. there you go.  ;)


Actual results:

  rpmls reveals ~ 40 MBytes of noarch data inside the arched package.


Expected results:

  This data should live inside some wordnet-data.noarch pkg.


Proposed Solution:

  Create a noarch subpkg for the data and add

    Requires: wordnet-data = %{version}-%{release}

  to wordnet.$arch pkg.  ;)

  Don't forget to add %doc LICENSE or such to data-subpkg, so it shouldn't
  require arched main-pkg, because there are some other apps or libs around
  which use this data, but don't need the wordnet-libs.

Comment 1 Björn 'besser82' Esser 2013-12-11 13:17:06 UTC
Three monthes no reply on this.  :(  If nobody cares, I'll take of it during next week.

Comment 2 Rahul Sundaram 2013-12-12 23:15:48 UTC
I have dropped a offline mail to Steve.  He was shifting his job/place recently so might not have time to attend to this.

Comment 3 steve 2013-12-13 04:24:13 UTC
Hello,

I'm sorry about the non-responsiveness. Yeah, for a while now, I haven't been able to do justice to any of the packages for which I am a maintainer. I've orphaned this package in the packagedb. If besser82 wants to take it, he should go ahead else I'll announce the orphaning on fedora-devel (I'm assuming that this is the correct way to orphan a package - I did a quick search for on the wiki and the closest thing I could find was the Notes for Maintainers section at https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers )

cheers,
- steve

Comment 4 Fedora Admin XMLRPC Client 2013-12-13 09:13:15 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Björn 'besser82' Esser 2013-12-13 09:18:17 UTC
Hi Steve!

(In reply to steve from comment #3)
> I'm sorry about the non-responsiveness. Yeah, for a while now, I haven't
> been able to do justice to any of the packages for which I am a maintainer.

no problem.  ;)  At least you gave a reply.  :D


> I've orphaned this package in the packagedb. If besser82 wants to take it,

Just taken master, F20, F19 and el6.  F18 and el5 branch is still owned by for some reason.  If you want to orphan them, too, I'd be glad to take them.


Cheers,
  Björn

Comment 6 steve 2013-12-17 09:32:55 UTC
Hey Björn

(In reply to Björn "besser82" Esser from comment #5)
> 
> > I've orphaned this package in the packagedb. If besser82 wants to take it,
> 
> Just taken master, F20, F19 and el6.  F18 and el5 branch is still owned by
> for some reason.  If you want to orphan them, too, I'd be glad to take them.
> 

Done ! Thanks for taking over this. I use wordnet frequently so hope you do a better job than I did ;-)

cheers,
- steve

Comment 7 Fedora End Of Life 2015-01-09 19:46:21 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Matěj Cepl 2015-02-03 14:07:53 UTC
Created attachment 987593 [details]
suggested patch

This is just a drive-by fix. What do you think?

Builds in Koji (http://koji.fedoraproject.org/koji/taskinfo?taskID=8809440)

Comment 9 Jaroslav Reznik 2015-03-03 15:03:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 10 Fedora End Of Life 2016-07-19 18:58:35 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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