[Bug 2222] New: Review request: libactp - Adaptive Clearing Tool Path Library
by RPM Fusion Bugzilla
https://bugzilla.rpmfusion.org/show_bug.cgi?id=2222
Bug #: 2222
Summary: Review request: libactp - Adaptive Clearing Tool Path
Library
Classification: Unclassified
Product: Package Reviews
Version: Current
Platform: All
OS/Version: GNU/Linux
Status: NEW
Severity: normal
Priority: P5
Component: Review Request
AssignedTo: rpmfusion-package-review(a)rpmfusion.org
ReportedBy: SpikeFedora(a)gmail.com
CC: rpmfusion-package-review(a)rpmfusion.org
Blocks: 2
Spec URL:
http://spike.fedorapeople.org/libactp/libactp.spec
SRPM URL:
http://spike.fedorapeople.org/libactp/libactp-0.0.2-0.1.20111219giteb97a6...
Description:
The libactp (Adaptive Clearing Tool Path Library) is an implementation of the
GPL'ed algorithm demonstrated in FreeSteel as a set of C library functions
Why this package is not eligible to be included in Fedora:
"Some software is not functional or useful without the presence of external
code dependencies in the runtime operating system environment. When those
external code dependencies are non-free, legally unacceptable, or binary-only
[...], then the dependent software is not acceptable for inclusion in
Fedora"[1]
Since atm only HeeksCNC uses this lib and HeeksCNC depends on OCE
(HeeksCNC->HeeksCAD-devel->OCE-devel), which is considered non-free, I assume
the term "not useful" applies here.
[1] http://fedoraproject.org/wiki/Packaging:Guidelines
rpmlint output:
SPECS/libactp.spec: W: invalid-url Source0: libactp-svnHEAD.tar.bz2
libactp.src: W: invalid-url Source0: libactp-svnHEAD.tar.bz2
1 packages and 1 specfiles checked; 0 errors, 2 warnings.
Upstream doesn't provide a release package tarball.
Careful: I usually don't do any python packaging. Here be dragons!
--
Configure bugmail: https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
6 years, 2 months
[Bug 2363] New: jitsi - Open Source Video Calls and Chat
by RPM Fusion Bugzilla
https://bugzilla.rpmfusion.org/show_bug.cgi?id=2363
Bug #: 2363
Summary: jitsi - Open Source Video Calls and Chat
Classification: Unclassified
Product: Package Reviews
Version: Current
Platform: All
OS/Version: GNU/Linux
Status: NEW
Severity: normal
Priority: P5
Component: Review Request
AssignedTo: rpmfusion-package-review(a)rpmfusion.org
ReportedBy: fedora(a)marionline.it
CC: rpmfusion-package-review(a)rpmfusion.org
SPEC: http://marionline.fedorapeople.org/packages/SPECS/jitsi.spec
SRPMS:
http://marionline.fedorapeople.org/packages/SRPMS/jitsi-1.1-1.nightly.bui...
Description:
Jitsi (previously SIP Communicator) is an audio/video and chat communicator
that supports protocols such as SIP, XMPP/Jabber, AIM/ICQ, Windows Live, Yahoo!
and many other useful features.
Why here:
This package cannot be shipped into official fedora repository because upstream
use ffmpeg library.
Rpmlint:
jitsi.src: W: invalid-url Source4: portaudio-hotplug-r1838.tar.gz
jitsi.src: W: invalid-url Source3: jdic-r1736.tar.gz
jitsi.x86_64: W: devel-file-in-non-devel-package
/usr/lib64/portaudio-hotplug-r1838/libportaudio.a
jitsi.x86_64: W: devel-file-in-non-devel-package
/usr/include/portaudio-hotplug-r1838/portaudio.h
jitsi.x86_64: W: devel-file-in-non-devel-package
/usr/lib64/portaudio-hotplug-r1838/pkgconfig/portaudio-2.0.pc
jitsi.x86_64: W: devel-file-in-non-devel-package
/usr/include/portaudio-hotplug-r1838/pa_linux_alsa.h
jitsi.x86_64: W: no-manual-page-for-binary jitsi
4 packages and 0 specfiles checked; 0 errors, 7 warnings.
I think jdic and portaudio branch hotplug for now is useful just for jitsi so I
include them directly in this package. There are not official releases of this
two packages, I checkout the code from svn repository.
This is not my first RPM package. I just open another review request here for
another SIP software, homer:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=2237
--
Configure bugmail: https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
6 years, 2 months
nVidia howto question or solution
by Sérgio Basto
Hello,
After on IRC another fellow, had problems on install nVidia drives on
first installation and reboot, I also had a similar problem that make
me think. And I think I found the issue, instead try blacklist nouveau
on boot we should run:
dracut -f /boot/initramfs-$(uname -r).img $(uname -r)
xorg-x11-drv-nvidia package have blacklist-nouveau.conf [1] but just
install a new kernel nouveau enter in blacklist isn't it ? , so after
installing nVidia drives (for the first time) we should also run dracut
to generate initramfs without nouveau module isn't it ? anyway like
blacklist-nouveau.conf text says.
Conclusion we should/need update https://rpmfusion.org/Howto/nVidia
Best regards,
[1]
https://pkgs.rpmfusion.org/cgit/nonfree/xorg-x11-drv-nvidia.git/tree/bl
acklist-nouveau.conf
--
Sérgio M. B.
6 years, 2 months
Access to the Rpmfusion repositories
by Antonio Trande
Hi all.
I can't checkout a package's GIT module:
$ rfpkg clone free/lives
Deprecation warning: kojiconfig is deprecated. Instead, kojiprofile
should be used.
Cloning into 'lives'...
ssh: Could not resolve hostname # my fas username# https: Name or
service not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Command '['git', 'clone', 'ssh://# My FAS
username#
https://fedoraproject.org/wiki/Infrastructure/Kerberossagitter@pkgs.rpmfu...',
'--origin', 'origin']' returned non-zero exit status 128
--
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x5E212EE1D35568BE
GPG key server: https://keys.fedoraproject.org/
6 years, 2 months
[Bug 4441] New: Review request: discord - All-in-one voice and text
chat for gamers
by RPM Fusion Bugzilla
https://bugzilla.rpmfusion.org/show_bug.cgi?id=4441
Bug ID: 4441
Summary: Review request: discord - All-in-one voice and text
chat for gamers
Product: Package Reviews
Version: Current
Hardware: x86_64
OS: GNU/Linux
Status: NEW
Severity: enhancement
Priority: P1
Component: Review Request
Assignee: rpmfusion-package-review(a)rpmfusion.org
Reporter: seancallaway(a)gmail.com
CC: rpmfusion-package-review(a)rpmfusion.org
SPEC URL: https://seansblag.com/software/discord/discord.spec
SRPM URL: https://seansblag.com/software/discord/discord-0.0.1-1.fc25.src.rpm
DESCRIPTION:
Discord is a free-of-cost proprietary VoIP application designed for gaming
communities.
WHY NOT IN FEDORA?
Discord is a proprietary application *and* relies on nonfree libraries (such as
ffmpeg), which the developer has bundled into the application.
RPMLINT OUTPUT (SRPM):
discord.src: W: spelling-error Summary(en_US) gamers -> gamer, games, tamers
discord.src: W: invalid-license Proprietary
1 packages and 0 specfiles checked; 0 errors, 2 warnings.
RPMLINT OUTPUT (RPM):
discord.x86_64: W: spelling-error Summary(en_US) gamers -> gamer, games, tamers
discord.x86_64: W: invalid-license Proprietary
discord.x86_64: W: binaryinfo-readelf-failed
/usr/lib64/discord/resources/bootstrap/discord_voice.zip readelf: Error: Not an
ELF file - it has the wrong magic bytes at the start
discord.x86_64: E: binary-or-shlib-defines-rpath /usr/lib64/discord/Discord
['$ORIGIN', '$ORIGIN/lib/']
discord.x86_64: W: binaryinfo-readelf-failed
/usr/lib64/discord/resources/bootstrap/discord_toaster.zip readelf: Error: Not
an ELF file - it has the wrong magic bytes at the start
discord.x86_64: W: binaryinfo-readelf-failed
/usr/lib64/discord/resources/bootstrap/discord_utils.zip readelf: Error: Not an
ELF file - it has the wrong magic bytes at the start
discord.x86_64: W: no-documentation
discord.x86_64: W: no-manual-page-for-binary Discord
discord.x86_64: W: desktopfile-without-binary
/usr/share/applications/discord.desktop /usr/bin/Discord
JUSTIFICATIONS FOR ERRORS AND WARNINGS:
* spelling-error: gamers is the proper plural of gamer.
* invalid-license: rpmlint doesn't seem to support nonfree licenses
* binaryinfo-readelf-failed: It's right. There's aren't ELF binaries, as
they're ZIP files. Not sure how to remove this error, but am more than willing
to do something to fix this.
* binary-or-shlib-defines-rpath: The developer has built their proprietary
binary to use bundled libraries. It's not ideal, but it's what they've done. I
can try to convince them to just include those libs as a requirement in their
Linux release.
* no-documentation and no-manual-page-for-binary: No documentation is provided
for Discord outside of their website.
* desktopfile-without-binary: /usr/bin/Discord is a symlink to
/usr/lib64/discord/Discord due to the bundled libraries.
NOTES:
This is my first RPMFusion package (and first desktop application package), but
not my first package. I package re2c and openvpn-auth-ldap for EPEL.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
6 years, 2 months
Re: [x264] Update x264 to 0.152 and switch asm compiler from yasm
to nasm
by Sérgio Basto
On Sat, 2017-12-30 at 20:50 +0000, Sérgio Basto wrote:
> On Sat, 2017-12-30 at 21:47 +0100, Dominik 'Rathann' Mierzejewski
> wrote:
> > Hi, Sérgio.
> >
> > On Saturday, 30 December 2017 at 20:09, Sérgio M. Basto wrote:
> > [...]
> > > diff --git a/x264.spec b/x264.spec
> > > index 8534184..0aae91f 100644
> > > --- a/x264.spec
> > > +++ b/x264.spec
> >
> > [...]
> > > @@ -30,8 +30,8 @@
> > >
> > > Summary: H264/AVC video streams encoder
> > > Name: x264
> > > -Version: 0.%{api}
> > > -Release: 22%{?gver}%{?_with_bootstrap:_bootstrap}%{?dist}
> > > +Version: 0.152
> > > +Release: 1%{?dist}
> >
> > Is there a good reason why you changed the macro usage into a
> > literal
> > number?
>
> No, my / rpmdev-bumpspec mistake , going to fix now.
> Thanks
The mass rebuild is finished , I had many unexpected problems ...
Happy new year
>
> > Regards,
> > Dominik
--
Sérgio M. B.
6 years, 3 months
x264 and x265 soname bump ?
by Sérgio Basto
Hello,
x264 finally bumped to 0.152 with the asm compiler change .
x265 we got a new version 2.6 from 29-Nov-2017
Should or may I update it and do one mass rebuild of dependencies ?
Cheers,
--
Sérgio M. B.
6 years, 3 months
