I'd like to update the gpsd package to the latest version 2.94. If
there will be no objections, probably sometimes next week.
Unfortunately, there were non-trivial API changes since version 2.39
that break most of the dependent packages. The first version with the
new API (2.90) was released more than a year ago, so I think the
upstreams had enough time to make necessary changes and we shouldn't
wait any longer.
Packages that currently use libgps.so.18:
Here is a gpsd srpm in case anyone wants to start preparing patches
i did a desktop-file-validate on all .desktop files in the current
rawhide distro (note rpmfusion too).
here is the result of only the errors grepped from a complete check:
p.s. if someone needs help fixing an entry ask away.
He Rui wrote:
> Test cases have been designed to cover common circumstances, including low
> /boot space status.
Why does the "too low /boot space to install" testcase (which is actually
the common case when upgrading from F12 or F11) still require manually
removing excess kernels, 6 months after this issue became initially known?
Preupgrade should do this automatically. After the upgrade, ALL the old
kernels will be removed anyway, so I don't see how it hurts to remove all
except the running one right away.
I tried to set the following in ~/.rpmmacros:
and when I did rpmbuild -bc hello.spec, it shows:
$ rpmbuild --showrc | grep cc
rpmlib(ConcurrentAccess) = 4.1-1
-14: __cc /path/to/compiler-gcc
-14: __cpp gcc -E
But, when I use rpmbuild -bc hello.spec, the configure script still
takes cc as /usr/bin/gcc from /usr/lib/rpm/macros. Why is it so?
Only when I do something like, CC=/path/to/compiler-gcc rpmbuild -bc
hello.spec, does the new CC used for building the package. Why isn't
~/.rpmmacros overriding the default macros?
Appreciate any inputs,
I have an application I am working on that requires a config file in
the users home directory. This file is .asoundrc (alsa sound config) I
need to write a script that does 5 things.
1 ) check if the file is installed already (go to step 2 else go to
2 ) install the file if it is not there (go to step 4)
3 ) Open the file and check for parameters. (go to step 4 else go to
4 ) If parameters are missing then append them to the file. (go to step 5)
5 ) If all checks out launch the application (end)
I've gotten all but step 3 and step 4 to work so far but I don't know
how to tell bash to check for the needed parameters in an existing file
and if not there append them. I don't want to just open for append
because then it will just create a massive file over time as they are
added each time the program is run and I don't want to overwrite the
users file if it already exists, thus breaking something else the user
may have installed.
Also, is there a way to check the users sound device? I have it hard
coded right now for sound device 0. It would be nice if it could prompt
for device number in case the user has more than one device or if for
some other reason the device number is not 0.
Hopefully this makes sense to someone it's hard getting these thoughts
from inside my gray matter to paper.