Bug 6831 - Don't allow .mo files in a library (lib or lib64) subpackage
Summary: Don't allow .mo files in a library (lib or lib64) subpackage
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: RPM stack maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-20 00:06 CEST by Olav Vitters
Modified: 2016-10-15 20:17 CEST (History)
3 users (show)

See Also:
Source RPM: rpmlint
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Olav Vitters 2012-07-20 00:06:28 CEST 
Translations should not be in the same package as the .so file, because they'll conflict. This mistake was made in libsoup. It would be nice if the buildsystem would detect these cases and prevent submission.
Comment 1 Marja Van Waes 2013-08-11 19:42:08 CEST 
(In reply to Olav Vitters from comment #0)
> Translations should not be in the same package as the .so file, because
> they'll conflict. This mistake was made in libsoup. It would be nice if the
> buildsystem would detect these cases and prevent submission.

I marked the [New] bugs mail for this bug, but I don't remember why. Maybe because I was wondering whether this should be documented while this is still possible?

Is it still possible to make this mistake?

CC: (none) => marja11

Marja Van Waes 2013-08-11 19:44:47 CEST

CC: (none) => pierre-malo.denielou

Comment 2 Nicolas Vigier 2013-09-21 16:59:34 CEST 
This should probably done as a new rpmlint check.

CC: (none) => boklm
Component: BuildSystem => RPM Packages
Version: unspecified => Cauldron
Assignee: sysadmin-bugs => qa-bugs
Product: Infrastructure => Mageia
Source RPM: (none) => rpmlint

Nicolas Vigier 2013-09-21 17:12:52 CEST

Assignee: qa-bugs => bugsquad

Nicolas Vigier 2014-03-24 10:52:40 CET

CC: boklm => (none)

Samuel Verschelde 2016-10-15 20:17:09 CEST

Assignee: bugsquad => rpmstack
Note You need to log in before you can comment on or make changes to this bug.