packaging golang guidelines (like etcd, consul)
by Muayyad AlSadi
hi,
I'm on f22 and have consul and etcd from the repos
ldd /usr/bin/consul
linux-vdso.so.1 (0x00007ffc98fa2000)
liblmdb.so.0.0.0 => /lib64/liblmdb.so.0.0.0 (0x00007f99bc1b5000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f99bbf99000)
libc.so.6 => /lib64/libc.so.6 (0x00007f99bbbd8000)
/lib64/ld-linux-x86-64.so.2 (0x0000562f58dbf000)
ldd /usr/bin/etcd
not a dynamic executable
I found that when CGO_ENABLED=0 it would be statically linked
the dynamic one like consul above is not actually dynamically linked
(because of the size)
are there some fedora guidelines for golang apps?
are there macros and helpers for rpm?
8 years, 5 months
Looking for someone to take over Asterisk and related packages
by Jeffrey Ollie
So, after almost 10 years, it's time to find someone else to take over the
Asterisk packages. If you're interested, reply to the list. I'd prefer if
someone with proven packaging skills would step up - Asterisk has several
security-related releases a year in addition to several bug-fix releases so
this isn't the package to get started with.
--
Jeff Ollie
8 years, 5 months
[HEADS UP] Upcoming soname change for libtirpc
by Steve Dickson
Hello,
Well place sources tell me in the upcoming
libtirpc release the soname will be changing
due to some API changes.
The API changes will make the Linux version
more compatible with litbirpc implementations
Obviously this change will just go in rawhide
but how do I
1) request the build rpm go be added to the build root?
2) find and rebuild all the dependencies?
3) anything else I need to do?
tia,
steved.
8 years, 5 months
Self Introduction: Randy Barlow
by Randy Barlow
Hello!
I would like to become a Fedora package maintainer. I've long been a
proponent of Free Software, and have been a Fedora user for about three
years now (Gentoo before that, and Red Hat before that). I work at Red
Hat as a contributor to the Pulp project:
http://pulp.readthedocs.org/
I've been contributing to Fedora by running alphas, betas, and rawhide
and trying to file quality bug reports with Fedora and upstream projects
so that bugs can get fixed before they get released to the stable
Fedoras. I've enjoyed this work, and want to get more involved so I
decided to pursue becoming a package maintainer.
I've filed a request to add a new package called ari-backup:
https://bugzilla.redhat.com/show_bug.cgi?id=1269609
ari-backup is a simple wrapper around rdiff-backup that allows admins to
describe their backup jobs in simple Python files. It adds the ability
to manage LVM or ZFS snapshots so that the backups can be crash
consistent. I am one of the contributors to ari-backup.
Let me know if there is anything I can or should do to aide in the
review process. I look forward to participating even more in Fedora!
8 years, 5 months
Ownership of /usr/lib/rpm/fileattrs
by Orion Poplawski
Various packages now install files into /usr/lib/rpm/fileattrs for use when
building rpms. Currently that directory is owned by:
rpm-build-4.13.0-0.rc1.4.fc23.x86_64
javapackages-tools-4.6.0-6.fc23.noarch
Of the various packages on my machine that install files there:
gstreamer1-1.6.0-2.fc23.x86_64
javapackages-tools-4.6.0-6.fc23.noarch
kde-settings-23-7.fc23.noarch
nodejs-0.10.36-4.fc23.x86_64
perl-generators-1.06-1.fc23.noarch
python3-cups-1.9.72-2.fc23.x86_64
redhat-rpm-config-36-1.fc23.noarch
rpm-build-4.13.0-0.rc1.4.fc23.x86_64
rpm-mpi-hooks-3-2.fc23.noarch
only rpm-mpi-hooks requires rpm-build for directory ownership, while
javapackages-tools takes the route of owning the directory. However, I'd
rather rpm-mpi-hooks not require rpm-build as it's not really necessary other
than for this directory. The simple thing I think would be for rpm to own the
directory. Does that seem reasonable?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 http://www.nwra.com
8 years, 5 months
