DevHeads.net

Postings by Ingvar Hagelund

Please test varnish-6.0.4-2.fc29

I just submitted a Bodhi update for varnish-6.0.4-2.fc29, [ <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2019-8a85a90af6" title="https://bodhi.fedoraproject.org/updates/FEDORA-2019-8a85a90af6">https://bodhi.fedoraproject.org/updates/FEDORA-2019-8a85a90af6</a> | <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2019-8a85a90af6" title="https://bodhi.fedoraproject.org/updates/FEDORA-2019-8a85a90af6">https://bodhi.fedoraproject.org/updates/FEDORA-2019-8a85a90af6</a> ]

It fixes a medium risk security update, VSV00003 aka CVE-2019-15892. Please test and add karma.

br,
Ingvar Hagelund

LD_LIBRARY_PATH vs rpath and libtool

Fedora prohibits the use of rpath, ref
<a href="https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath" title="https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath">https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath</a>

When compiling varnish with litbool, I ensure this by the usual

sed -i 's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=""|g;
s|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|g' libtool

However, during build and check, I need access to a library in the
build.

jemalloc-4.0.0 for rawhide, please test

I'm about to push jemalloc-4.0.0 for rawhide.

Native vagrant packages for Fedora

Vagrant offers scripted provisioning and deployment of virtual
instances, removing the infamous "but it works om my laptop"
obstacle. Vagrant is well-known and much used and praised in the
devops community. Its home page is <a href="http://vagrantup.com/" title="http://vagrantup.com/">http://vagrantup.com/</a>

Though VirtualBox is the current supported target, future versions of
vagrant may support other hypervizors as well, including kvm. Being in
itself free software under the MIT license, I think vagrant could be
included in fedora.

While an upstream rpm exists (putting all dependent packages in /opt)
a native fedora package of vagrant was missing.

What is varnish? (Was: Please test varnish-2.1.0-2 for F-13)

I was asked to give a short description of what varnish is.

Varnish is a state of the art, high performance http accellerator.

Please test varnish-2.1.0-2 for F-13

I think it's important that varnish-2.1.0-2.fc13 is included in F-13,
and hope that it's not too late.

It was submitted by bodhi today, and can also be downloaded from koji.

Please test the update and give feedback through bodhi.

Snipped from the bodhi update request:

Details
Upgrade to new upstream release 2.1.0. This upgrade is important
because

* The previous 2.0 series will be discontinued within the
lifetime of F-13

* 2.1.0 contains a fix for CVE-2009-2936.

Heads-up: Configuration language changes in new varnish version

varnish is a high performance http accellerator.

I'm just to tag and build the new upstream version 2.1.0 of varnish.
This new version has a change in the vcl configuration language that may
need changes to existing vcl code.

If you are using varnish, please read the release notes carefully.,
<a href="http://varnish-cache.org/wiki/changelog_2.0.6-2.1.0" title="http://varnish-cache.org/wiki/changelog_2.0.6-2.1.0">http://varnish-cache.org/wiki/changelog_2.0.6-2.1.0</a>

Ingvar

Porting amarok-1.4 to F11

As one of many, I'm the semi-happy owner of an Apple iPhone. The iPhone and the iPod Touch's media player db is well supported under Linux, using tools like libgpod, and iFuse or sshfs for access. Until recently, one could use amarok as a front end to sync content. But amarok-2.x does not (yet) support non-hardware (that is, not found by HAL) mounts.

It should be possible to make amarok-1.4 to work on F11. It is still maintained in epel, and the compilation fixes for F11 consisted of adding a few #include statements here and there. So it works - almost.