Update bodhi Notes?
by Neal Becker
I pushed a release to updates-testing, but I'd like to update the Notes for this
release. How should I do this?
11 years, 10 months
Problem pairing mouse with F17
by Digimer
Hi all,
I've installed F17 x86_64 on my Thinkpad T400s and have not been able
to pair my razer orochi bluetooth mouse. When I put my F16 x86_64 HDD
back in and boot, the mouse works fine over bluetooth.
When I put the mouse into pairing mode, the bluetooth applet sees the
mouse. However, when I click on it and try to pair, it simply says
"failed" and I have the option to try again.
This is what is shown in syslog;
============
Jun 3 22:20:27 lework bluetoothd[770]: bluetoothd[770]: Discovery
session 0x7f0ab7114aa0 with :1.142 activated
Jun 3 22:20:27 lework bluetoothd[770]: Discovery session 0x7f0ab7114aa0
with :1.142 activated
Jun 3 22:20:31 lework bluetoothd[770]: bluetoothd[770]: Stopping discovery
Jun 3 22:20:31 lework bluetoothd[770]: Stopping discovery
Jun 3 22:20:32 lework udevd[525]: specified group 'plugdev' unknown
Jun 3 22:20:32 lework dbus-daemon[837]: dbus[837]: [system] Rejected
send message, 3 matched rules; type="method_return", sender=":1.142"
(uid=1000 pid=13040 comm="bluetooth-wizard ") interface="(unset)"
member="(unset)" error name="(unset)" requested_reply="0"
destination=":1.0" (uid=0 pid=770 comm="/usr/sbin/bluetoothd -n ")
Jun 3 22:20:32 lework dbus[837]: [system] Rejected send message, 3
matched rules; type="method_return", sender=":1.142" (uid=1000 pid=13040
comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error
name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=770
comm="/usr/sbin/bluetoothd -n ")
Jun 3 22:21:56 lework udevd[525]: specified group 'plugdev' unknown
Jun 3 22:21:56 lework bluetoothd[770]: bluetoothd[770]: Refusing input
device connect: No such file or directory (2)
Jun 3 22:21:56 lework bluetoothd[770]: bluetoothd[770]: Refusing
connection from 00:02:76:20:8B:21: setup in progress
Jun 3 22:21:56 lework bluetoothd[770]: Refusing input device connect:
No such file or directory (2)
Jun 3 22:21:56 lework bluetoothd[770]: Refusing connection from
00:02:76:20:8B:21: setup in progress
Jun 3 22:22:01 lework udevd[525]: specified group 'plugdev' unknown
Jun 3 22:22:01 lework bluetoothd[770]: bluetoothd[770]: Discovery
session 0x7f0ab711d790 with :1.142 activated
Jun 3 22:22:01 lework bluetoothd[770]: Discovery session 0x7f0ab711d790
with :1.142 activated
============
I can confirm that selinux is disabled (as sestatus shows 'disabled').
Any idea what I should next?
Thanks.
--
Digimer
Papers and Projects: https://alteeve.com
11 years, 10 months
Orphaning ncpfs
by Vitezslav Crhonek
Hi all,
I'm orphaning ncpfs package (utilities for the ncpfs filesystem,
a NetWare client for Linux). I don't have a access to NetWare and
time to maintain the package. Ncpfs is pretty old, but it's still
used. Written in C, upstream is not interested in it anymore.
There are five opened bugs, two of them are security related.
I can offer SRPM for Mars (Martin Stovers NetWare-Emulator [1])
as a small gift:) - it may be useful.
If anyone is willing to maintain the package, feel free to take it.
[1] http://www.compu-art.de/mars_nwe/
Best regards,
Vitezslav Crhonek
11 years, 10 months
fix common misspellings -- mostly mechanically
by Jim Meyering
Even in mature projects full of nit-picky reviewers, it seems there
are always a few misspelled words in comments, documentation, etc.
Here's a recipe for correcting those. Hook this up as a
"make check" dependent rule to prevent recurrence.
First, get this http://github.com/lyda/misspell-check
and install its misspellings script.
Then, (presuming you use git for VC), run this to
see what you might want to change[*]:
git ls-files|misspellings -f -|perl -nl \
-e '/^(.*?)\[(\d+)\]: (\w+) -> "(.*?)"$/ or next;' \
-e '($file,$n,$l,$r)=($1,$2,$3,$4); $q="'\''"; $r=~s/$q/$q\\$q$q/g;'\
-e 'print "sed -i $q${n}s!$l!$r!$q $file"'
It massages the misspellings output into sed -i invocations.
Here are the ones from autoconf/master:
sed -i '104s!Stange!Strange!' AUTHORS
sed -i '175s!Propogate!Propagate!' ChangeLog.1
sed -i '673s!occurences!occurrences!' ChangeLog.2
sed -i '6973s!Accomodate!Accommodate!' ChangeLog.3
If you look at the AUTHORS file, you see that the first is a false
positive: we don't want to change the name of a contributor.
However, the three remaining commands fix legitimate spelling errors,
albeit only in ChangeLog files.
Remember that this is a naive tool. Be sure to review each
change carefully, and *in context*. It has no clue about the
boundaries between code and comments. For example, you must
be careful that it does not change grammar tokens or variable
names like "THRU" or "UPTO" to THROUGH or "UP TO".
Jim
[*] The misspellings script appears to be intended to do some
of this itself, but so far, it hasn't worked for me.
Note that for a typo like "cant", you'll be presented with this
sed command:
sed -i '16s!cant!cannot","can not","can'\''t!' m4/nullsort.m4
While the perl filter was careful to escape the single quote in the RHS
of the substitution, it will not choose which of those three
alternatives to use. Search for "," in the list of sed commands
to identify ones with more than one alternative spelling.
For each of those, you must manually select the word that you prefer.
Once you've done that, you can save the sed commands to a file, say
K, and apply their changes with "bash K".
11 years, 10 months
Self Introduction
by Alexey I. Froloff
Hi,
I am the new Fedora Package Collection Maintainer. I'm from
Russia, my name is Alexey, but people call me "raorn" (begins
with small letter "r").
I was Packager in ALT Linux distro for about eight years, my
interests are IPv6, OpenFlow, Vim, zsh, mutt, ruby and
WindowMaker. I'm familiar with git and rpm stuff, if you wish,
you may take a look at my ALT Linux packages here:
http://git.altlinux.org/people/raorn/packages/?o=age
I've been working with several upstreams, like zsh, Vim,
WindowMaker, ndisc6 and recently got my first patch merged into
Linux kernel ;-)
I am switching to Fedora as my primary desktop platform, but I am
missing some applications. Andreas Bierfert (awjb), who's
WindowMaker package finally made me chose Fedora, agreed to be my
sponsor. For now I'll be packaging bunch of WindowMaker applets
and one day I'd like to resurrect wdm (WINGs Display Manager). I
am also big fan of IPv6, running little IPv6-only network with
dual-stack router, my setup is described here -
http://blog.raorn.name/2012/02/ipv6-only-lan-with-dual-stack-openwrt.html
In the Internet I am using nickname "raorn" (IRC, twitter) or,
for 6-letters-or-longer-nickname-required sites I use "sir.raorn"
(gmail, facebook).
My public gpg key attached.
P.S. I am also an Old Fart and will take part in most of the
local flamewars ;-)
--
Regards, --
Sir Raorn. --- http://thousandsofhate.blogspot.com/
11 years, 10 months
Reporting a bug on several components - rpath issue
by Nicolas Chauvet
Hi,
I was trying to check if packages on my system has defined a rpath (1)
, I've made a little script:
# for f in $(ls /usr/lib64/*.so.* ) ; do chrpath ${f} &>/dev/null;
RETVAL=$?; if [ ! $RETVAL == 2 ] ; then chrpath ${f} ; rpm -qf ${f} ;
echo "" ; fi; done
This script reported around 70 rpath on my system related to nearly 20
different components.
For the record, rpmdev-setuptree adds a rpm macro for a local RPM
packaging environment:
%__arch_install_post /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot
So that's prevent rpmbuild to build a package using rpath with success.
This is not defined in the fedora buildsys by default. (nor autoqa ?...)
Now I would like to know how to massively report a bug for each
related component ? (at least those that define an rpath in /usr/lib64
from a library in the same directory).
Is there any experience doing such bugreport ?
For the root cause of the rpath issue on lib64 system is related to a
non-upstreamed patch (2) from libtool that prevents (most of the time)
the detection of the lib64 sub-directory to be in the default search
path of the system linker. Project generated from an upstream version
of libtool are likely to generate such issue.
Nicolas (kwizart)
(1) http://fedoraproject.org/wiki/Packaging:Guidelines#Beware_of_Rpath
(2) http://pkgs.fedoraproject.org/gitweb/?p=libtool.git;a=blob_plain;f=libtoo...
11 years, 10 months
How can we make security updates faster?
by Paul Wouters
Hi,
I've recently had release updates to two packages with CVE issues in
then. A few weeks ago, pidgin-otr needed a lot of me prodding people
to try it and give karma to get the security update out. Right now, my
socat CVE security releases sits in all four branches with no karma after
four days.
Is there something we can do to make these security updates move faster?
Perhaps a new mailinglist that just announces the security releases, to
remind people to test them and give karma.
Perhaps a gui app for people running post latest full release fedora
installs that checks if some software you are using is in need of karma?
Perhaps push security releases within 3 days if no -1 karma has been
received?
Push updates to stable when a certain download/install ratio has been
seen with no -1 karma?
Any other thoughts?
Paul
11 years, 10 months