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 173105 - Review Request: xfce4-battery-plugin
Summary: Review Request: xfce4-battery-plugin
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: David Lawrence
URL: http://xfce-goodies.berlios.de/
Whiteboard:
Depends On:
Blocks: FE-ACCEPT
TreeView+ depends on / blocked
 
Reported: 2005-11-14 06:43 UTC by Christoph Wickert
Modified: 2014-09-23 11:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-12-30 20:35:26 UTC
Type: ---
Embargoed:
gwync: fedora-cvs+


Attachments (Terms of Use)

Description Christoph Wickert 2005-11-14 06:43:16 UTC
Spec Name or Url: http://home.arcor.de/christoph.wickert/fedora/extras-review/SPECS/xfce4-battery-plugin.spec
SRPM Name or Url: http://home.arcor.de/christoph.wickert/fedora/extras-review/SRPMS/xfce4-battery-plugin-0.3.0-2.fc4.src.rpm
Description: A battery monitor plugin for the Xfce panel, compatible with APM and ACPI.

- rplint is clean
- licese BSD (included)

Comment 1 Kevin Fenzi 2005-11-15 20:18:34 UTC
Good:

- rpmlint ok on both fc4/devel
- package meets naming guidelines 
- package builds fine on both fc4/devel (x86)
- no .a files. 
- source matches upstream.
- works on my fc4 laptop.

Needswork: 
- Are you sure the license is BSD? The source files have LGPL headers, but the
COPYING file looks BSD. Can you get upstream to clarify? It could be dual
LGPL/BSD or something. 

Nits:
- make might need to be 'make %{?_smp_mflags}'

I can't seem to (yet) reassign this bug to approve it, my fedorabugs group
membership might still be propigating to the cvs box.

Comment 2 Christoph Wickert 2005-11-18 02:03:48 UTC
(In reply to comment #1)
> 
> Needswork: 
> - Are you sure the license is BSD? The source files have LGPL headers, but the
> COPYING file looks BSD. Can you get upstream to clarify? It could be dual
> LGPL/BSD or something. 
I have contacted upstream but no reply by now. Styin tuned.
I will now push the GPL licensed goodies first (#173543, #173544, #173546,
#173548 - #173553), then have a closer look at the BSD ones.

> 
> Nits:
> - make might need to be 'make %{?_smp_mflags}'
D'oh. Of course, will fix that before biuld.

Comment 3 Christoph Wickert 2005-12-01 13:50:13 UTC
Reply from Upstream:
Benedikt Meurer (author of xfce4-sample-plugin) said that the COPYING (BSD) file
is only a relict from his sample plugin and since LGPL is more restrictive it
should be applied to the whole package.

Edscott Wilson Garcia (one of the programs authors) wrote:
"Yes. Libraries are LGPL, as released in such manner by their initial
author. The program source file is BSD, since that is what the initial
author (Nicholas Penwarden) thought best."

Debian ships this package as BSD
http://packages.debian.org/changelogs/pool/main/x/xfce4-battery-plugin/xfce4-battery-plugin_0.3.0-1/xfce4-battery-plugin.copyright

So should we release it LGPL? Do I have to replace the COPYING file then?

Comment 4 Kevin Fenzi 2005-12-01 17:21:14 UTC
Since the package has both LGPL (the acpi/apm lib files) and BSD (the main
battstat.c file), it should have both in the spec License... BSD and LGPL. 

I would leave the BSD liscence in the COPYING file (as it is upstream), but
perhaps add a LGPL copying file in as well? 

Then, spec can have: License: BSD and LGPL

Comment 6 Ralf Corsepius 2005-12-01 17:58:21 UTC
(In reply to comment #4)
> Since the package has both LGPL (the acpi/apm lib files) and BSD (the main
> battstat.c file), it should have both in the spec License... BSD and LGPL. 
> 
> I would leave the BSD liscence in the COPYING file (as it is upstream), but
> perhaps add a LGPL copying file in as well? 
> 
> Then, spec can have: License: BSD and LGPL

Sorry, nope. If binary package having been built from sources containing
[L]GPL'ed and other licensed source files, automatically is [L]GPL'ed as a whole.

Comment 7 Kevin Fenzi 2005-12-01 18:14:10 UTC
> Sorry, nope. If binary package having been built from sources containing
> [L]GPL'ed and other licensed source files, automatically is [L]GPL'ed 
> as a whole.

Really? Do you have a cite or other information on that? 
libxfce4util needs to be changed to only LGPL if thats the case...
also I see libcap in core has "BSD-like and LGPL".

Also if thats the case we should update the wiki to mention that in License
discussion and reviews. 

Also, Christoph: xfce4-battery-plugin is missing libxfcegui4-devel as a
BuildRequires. 

Comment 8 Christoph Wickert 2005-12-01 18:38:04 UTC
(In reply to comment #7)
> 
> Also, Christoph: xfce4-battery-plugin is missing libxfcegui4-devel as a
> BuildRequires. 

Arghh, yes. I've fixed that in the specfile but I don't want to rebuild the srpm
before the license issue is clear.



Comment 9 Christoph Wickert 2005-12-01 18:44:18 UTC
(In reply to comment #7)
> 
> Also, Christoph: xfce4-battery-plugin is missing libxfcegui4-devel as a
> BuildRequires. 

Correcting my prevouis comment #8
Nope, sorry, it's there. Both in the srpm and in the specfile on the ftp server.


Comment 10 Patrice Dumas 2005-12-01 18:54:24 UTC
(In reply to comment #7)
> > Sorry, nope. If binary package having been built from sources containing
> > [L]GPL'ed and other licensed source files, automatically is [L]GPL'ed 
> > as a whole.

More precisely the whole is redistributed under the terms of the LGPL. But the
BSD licenced files remain BSD licenced. So it is more informative to put BSD and
LGPL in the licence. The BSD copyright/licence statement is added in the %doc
section (it is the COPYING file), there is a LGPL so things are fine. 

Incidentally the
panel-plugin/libacpi.c
has a GPL header?


Comment 11 Thorsten Leemhuis 2005-12-01 19:27:24 UTC
(In reply to comment #10)
> (In reply to comment #7)
> > > Sorry, nope. If binary package having been built from sources containing
> > > [L]GPL'ed and other licensed source files, automatically is [L]GPL'ed 
> > > as a whole.
> 
> More precisely the whole is redistributed under the terms of the LGPL.

Then "License" field in the rpm spec imho should only be "LGPL" because it
stands for the whole package. Otherwise someone might get the idea that the
whole package is under a Dual-BSD/LGPL license. And thats wrong afaics.

Comment 12 Ralf Corsepius 2005-12-02 04:55:40 UTC
(In reply to comment #11)
> (In reply to comment #10)
> > (In reply to comment #7)
> > > > Sorry, nope. If binary package having been built from sources containing
> > > > [L]GPL'ed and other licensed source files, automatically is [L]GPL'ed 
> > > > as a whole.
> > 
> > More precisely the whole is redistributed under the terms of the LGPL.
> 
> Then "License" field in the rpm spec imho should only be "LGPL" because it
> stands for the whole package. Otherwise someone might get the idea that the
> whole package is under a Dual-BSD/LGPL license. And thats wrong afaics.

Exactly. Though each source file can apply different licenses, the final
application binary is being linked against files having been compiled from
LGPL'ed sources. Therefore, the final binary application is LGPL'ed, though it's
sources are licensed BSD.

=> I.e. the binary package must be shipped/relicensed under the [L]GPL.

Comment 13 Patrice Dumas 2005-12-02 09:29:17 UTC
(In reply to comment #11)

> Then "License" field in the rpm spec imho should only be "LGPL" because it
> stands for the whole package. Otherwise someone might get the idea that the
> whole package is under a Dual-BSD/LGPL license. And thats wrong afaics.

Yep, that's true. It's in fact better to avoid people thinking that's it's dual
licencing. As there are the 2 licences in %doc, it should be enough to have
somebody interested get the srpm and look at the file headers.

Comment 14 Kevin Fenzi 2005-12-09 19:26:01 UTC
ok, that all makes sense I guess... 

So, the package License should be "LGPL". 

With that fixed, I see no other blockers...
APPROVED. 

Comment 15 Christoph Wickert 2005-12-30 20:35:26 UTC
Successfully compiled on all arches and branches.

Comment 16 Mukundan Ragavan 2014-09-23 00:56:31 UTC
Package Change Request
======================
Package Name: xfce4-battery-plugin
New Branches: epel7
Owners: cwickert
InitialCC: nonamedotc

Comment 17 Gwyn Ciesla 2014-09-23 11:56:07 UTC
Git done (by process-git-requests).


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