Is this allowed? Files and libs duplicated in subpackages
by Michael Schwendt
https://bugzilla.redhat.com/1003196
Based on this suspicious output
mate-dictionary from mate-utils
provides libmatedict.so.6()(64bit)
mate-utils from mate-utils
provides libmatedict.so.6()(64bit)
required by: mate-dictionary-devel-1.6.0-7.fc20.x86_64
required by: mate-utils-devel-1.6.0-7.fc20.x86_64
I've only verified in koji that lots of files are included in both
sub-packages. Even the descriptions overlap.
And there are even more subpackages, which only contain copies of
files included in the base mate-utils package already.
Why is that done? Why aren't RPM dependencies used to have the
base-package depend on the multiple subpackages?
So far, it has always been a packaging mistake to duplicate files (and
their Provides as a consequence) in multiple subpackages.
10 years, 6 months
Summary/Minutes from today's FPC Meeting (2013-09-05 16:00 - 17:55 UTC)
by James Antill
======================
#fedora-meeting-1: fpc
======================
Meeting started by abadger1999 at 16:02:48 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-09-05/fedora-meeti...
.
Meeting summary
---------------
* %doc and %_pkgdocdir duplicate files and cause conflicts
https://fedorahosted.org/fpc/ticket/338 (abadger1999, 16:07:52)
* #336 Please clarify the General Naming Guidelines for packages
https://fedorahosted.org/fpc/ticket/336 (abadger1999, 16:36:12)
* #337 Guidelines needed for header only libraries
https://fedorahosted.org/fpc/ticket/337 (abadger1999, 16:50:11)
* #343 copylib bundling exception for qtbrowserplugin in x2goclient
https://fedorahosted.org/fpc/ticket/343 (abadger1999, 17:09:14)
* How to replace "docker" package with an entirely different package of
the same name? https://fedorahosted.org/fpc/ticket/341 (abadger1999,
17:25:25)
* LINK:
http://fedoraproject.org/wiki/Packaging:Conflicts#Conflicting_Package_Names
(abadger1999, 17:33:18)
* Proposal: Allow the wmdocker rename to omit the Provides: docker [It
will keep the Obsoletes: docker for the standard 2 fedora releases].
This means that docker.io can go in with a Provides: docker now and
be renamed to docker when the Obsoletes are removed. (Currently +4.
need more votes in ticket) (abadger1999, 17:52:45)
* https://fedorahosted.org/fpc/ticket/318 broken scriptlets
%systemd_post (abadger1999, 17:54:16)
* Add BuildRequires?: systemd to the examples (.fpc 318) passes,
(+1:5, 0:0, -1:0) (abadger1999, 17:56:10)
* Open Floor (abadger1999, 17:56:18)
Meeting ended at 18:04:18 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* abadger1999 (107)
* geppetto (58)
* tibbs|w (31)
* mattdm (28)
* racor (21)
* orionp (19)
* SmootherFrOgZ (16)
* misc (4)
* zodbot (3)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
10 years, 6 months
How to handle tests in %check
by Miroslav Suchý
Hi,
I would like to ask on your opinion on
https://bugzilla.redhat.com/show_bug.cgi?id=912960#c25
Mamoru have in spec in %check section:
ruby -Ilib:test ./test/run-test.rb || echo "Please investigate this"
I'm saying that it should not be waived this way as it waive all failure.
I'm saying that if there is no failure, it should be just:
ruby -Ilib:test ./test/run-test.rb
and if there happened some problem which need upstream attention and
could not be fixed immediatelly, it should be replaced with something like:
FILE=$(mktemp)
ruby -Ilib:test ./test/run-test.rb | tee $FILE || :
# test foo is failing, reported as http://foo/issue/1
cat $FILE | grep "4 tests, 4 assertions, 1 failures, 0 errors, 0
pendings, 0 omissions, 0 notifications
Mamoru disagree. For me it is blocker.
I would like to ask for your opinions. Which way is correct and should
it be blocker for review?
Thanks in advance.
Mirek
10 years, 6 months