Unclear license
by Johan Swensson
Hi,
I'm looking into packaging a software that provides a LICENSE file which
only contains this:
"Everyone is permitted to do anything on this program including copying,
modifying, and improving, unless you try to pretend that you wrote it.
i.e., the above copyright notice has to appear in all copies.
THE AUTHOR DISCLAIMS ANY RESPONSIBILITY WITH REGARD TO THIS SOFTWARE."
I'm trying to get upstream to clarify but in the meantime I throw out a
question here as well.
Is this a proper license we can use in Fedora? If so which license would
I put in the License: field?
10 years, 3 months
Clarification for Packaging:JavaScript#CompilationMinification
by Stanislav Ochotnicky
JavaScript Guidelines[1] about compilation/minification don't mention
source RPMs at all. Someone suggested that if we ship pre-compiled
javascript in a source rpm (even if we don't then ship it in binary
RPMs) we are not fulfilling the open source definition[2]
More specifically this part:
"The source code must be the preferred form in which a programmer would
modify the program. Deliberately obfuscated source code is not
allowed. Intermediate forms such as the output of a preprocessor or
translator are not allowed."
In essence:
Is it enough to just remove minified/obfuscated js in %prep/%build to make
sure we are not using pre-built version or do we have to remove it from
the tarball so that we don't ship such compiled versions even in SRPMs?
Above is especially important for GPL-licensed JS libraries, but even
more permissive licenses could run afoul of Fedora "Freedom" foundation
I guess.
[1] https://fedoraproject.org/wiki/Packaging:JavaScript#CompilationMinification
[2] http://opensource.org/osd-annotated
--
Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Software Engineer - Developer Experience
PGP: 7B087241
Red Hat Inc. http://cz.redhat.com
10 years, 3 months
Summary/Minutes from today's FPC Meeting (2014-01-16 17:00 - 19:00 UTC)
by James Antill
======================
#fedora-meeting-1: fpc
======================
Meeting started by abadger1999 at 17:03:12 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-16/fpc.2014-01-...
.
Meeting summary
---------------
* roll call (abadger1999, 17:03:23)
* #339 software collections in Fedora (abadger1999, 17:06:52)
* LINK: https://fedorahosted.org/fpc/ticket/339 (abadger1999,
17:07:01)
* LINK: https://fedorahosted.org/fpc/ticket/379 (abadger1999,
17:12:07)
* Proposal for language bindings to be named $language-$foo, *not*
$foo-$language (old packages grandfathered but cleanups are
welcomed) APPROVED (+1:7, 0:0, -1:0) (abadger1999, 18:08:46)
* #380 code::blocks bundling (abadger1999, 18:11:00)
* LINK: https://fedorahosted.org/fpc/ticket/381 (abadger1999,
18:14:06)
* #383 Bundled library exception request for libgsystem
(abadger1999, 18:21:28)
* LINK: https://fedorahosted.org/fpc/ticket/383 (abadger1999,
18:21:33)
* LINK: https://fedorahosted.org/fpc/ticket/382 (abadger1999,
18:29:29)
* FPC members, please add problems you see with the golang guidelines
to the ticket. We'll see if there's a way to address them
afterwards (abadger1999, 19:02:43)
Meeting ended at 19:09:29 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* abadger1999 (160)
* tibbs|w (49)
* limburgher (41)
* geppetto (28)
* RemiFedora (13)
* racor (10)
* zodbot (8)
* Rathann (8)
* SmootherFrOgZ (2)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
10 years, 3 months
Switching to a fork
by Christopher Meng
Hi,
Is there any procedure introduction or guidelines of switching an
existing package from official one to a fork?
Thanks.
--
Yours sincerely,
Christopher Meng
Noob here.
http://cicku.me
10 years, 3 months
package release tag issue snapshot pre-release or post-release
by Parag Nemade
Hi,
I generally consider font packages to have release tag as snapshot
(pre-release) tag like
Pre-Release Packages: 0.%{X}.%{alphatag}
I have seen some font upstream don't change version but keep updating
fonts either by releasing new tarballs or in their VCS. If I say specific
to google, I think some of the google fonts are in hg or in the android
source git which have not seen any tarball release yet.
But if upstream source is greater than or equal to 1.x or 1.x.x, can we
still say its a snapshot pre-release release as no tarball
available/released?
When I run following on my F20 Gnome desktop, I can see some results
where version is not < 1.x.x
rpm -qa | grep "\-0.1.*git"
Now the specific question what can be package release tag for
https://bugzilla.redhat.com/show_bug.cgi?id=1049076 ?
Thanks & Regards,
Parag
10 years, 3 months
Perl autorequires failing for git-svn
by Todd Zullinger
Hi all,
I'm trying to fix a problem with the git-svn package that causes it to
not pull in the proper perl dependencies (filed as rhbz #1026760).
(It's possible I've simply missed an important announcement, but I
didn't spot anything in the guidelines.)
It appears that the file package was changed from 5.11 in f19 to 5.14
in f20. With this change, the git-svn script reports a different type
and find-requires does not pass it to perl.req for processing.
f19:
<mock-chroot>[root@f20-64 /]# file --version
file-5.11
magic file from /etc/magic:/usr/share/misc/magic
<mock-chroot>[root@f20-64 /]# file /builddir/build/BUILD/git-1.8.4.2/git-svn
/builddir/build/BUILD/git-1.8.4.2/git-svn: Perl script, ASCII text executable
<mock-chroot>[root@f20-64 /]# /usr/lib/rpm/find-requires <<< /builddir/build/BUILD/git-1.8.4.2/git-svn
/usr/bin/perl
perl >= 0:5.008
perl(Carp)
perl(Digest::MD5)
perl(File::Basename)
perl(File::Find)
perl(File::Path)
perl(File::Spec)
perl(Getopt::Long)
perl(Git)
perl(Git::SVN)
perl(Git::SVN::Editor)
perl(Git::SVN::Fetcher)
perl(Git::SVN::Log)
perl(Git::SVN::Migration)
perl(Git::SVN::Prompt)
perl(Git::SVN::Ra)
perl(Git::SVN::Utils)
perl(IO::File)
perl(IPC::Open3)
perl(lib)
perl(Memoize)
perl(strict)
perl(Term::ReadLine)
perl(vars)
perl(warnings)
f20:
<mock-chroot>[root@f20-64 /]# file --version
file-5.14
magic file from /etc/magic:/usr/share/misc/magic
<mock-chroot>[root@f20-64 /]# file /builddir/build/BUILD/git-1.8.4.2/git-svn
/builddir/build/BUILD/git-1.8.4.2/git-svn: Perl5 module source, ASCII text
<mock-chroot>[root@f20-64 /]# /usr/lib/rpm/find-requires <<< /builddir/build/BUILD/git-1.8.4.2/git-svn
This fails because find-requires only passes the file to perl.req if
it's either a .pm file or it's in the script list, which is defined
like this:
scriptlist=`echo $filelist | xargs -r file | \
grep -E ":.* (commands|script)[, ]" | cut -d: -f1`
This is where the change in the file commands output is causing
trouble.
Any help would be much appreciated.
Thanks!
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I believe in the noble, aristocratic art of doing absolutely nothing.
And someday, I hope to be in a position where I can do even less.
10 years, 3 months
Use of %__isa_bits should be mandatory
by Marcin Juszkiewicz
Hi
I am working on porting Fedora for AArch64 architecture. This means
patching many packages and during that time I noticed lot of checks for
32/64-bit architectures.
Most common one is:
%global something 32
%ifarch x86_64 ppc64 s390
%global something 64
%endif
Which can be now replaced to simple:
%global something %{__isa_bits}
And this works fine in Fedora 19 and beyond (including RHEL 7). There
are also some other variations of 32/64-bit checks which could be converted.
Can use of %__isa_bits be somehow announced/suggested to developers?
Would cut amount of patching needed for each new architecture.
10 years, 3 months
python-sphinx generates different filenames in different architectures
by Sergio Pascual
Hello,
sphinx is very popular tool for documenting python. Among other things, it
can create
inheritance diagrams with the extension sphinx.ext.inheritance_diagram
The names of the generated files are of the form
inheritance-xxxxxxxx.png where xxxxx is a hash
But the hash is different in different architectures, such as in this
scratch build
https://koji.fedoraproject.org/koji/taskinfo?taskID=6384105
The only solution I have found so far is to make the doc subpackages arched
instead of noarch, but it seems a waste of resources.
Has anybody dealt with this sphinx problem before?
BTW, the function that generates the names is
sphinx.ext.graphviz.render_dot
and the code is
hashkey = code.encode('utf-8') + str(options) + \
str(self.builder.config.graphviz_dot) + \
str(self.builder.config.graphviz_dot_args)
fname = '%s-%s.%s' % (prefix, sha(hashkey).hexdigest(), format)
where code is the graphviz code used to generate the figure, options is the
empty list [], graphviz_dot is 'dot' and graphviz_dot_args is also the
empty list []
sha is sha1
Regards, Sergio
10 years, 3 months
