rpmbuild error (wbar) on F24
by Ranjan Maitra
Hi,
I have a local rpm that I have created using wbar. The spec file is here:
https://paste.fedoraproject.org/384973/14669508
I have successfully created this rpm up to Fedora 23. But have been unable to do so this time around in F24.
I get the following errors:
....
cc1plus: all warnings being treated as errors
Makefile:551: recipe for target 'wbar-Main.o' failed
make[2]: *** [wbar-Main.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/maitra/rpmbuild/BUILD/wbar-2.3.4/src'
Makefile:404: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/maitra/rpmbuild/BUILD/wbar-2.3.4'
Makefile:345: recipe for target 'all' failed
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.qtyTEY (%build)
I was wondering what is going wrong here. I am not very familiar with spec files, but have successfully built rpms by looking at other spec files. Btw, here is the source code for wbar:
https://code.google.com/archive/p/wbar/downloads
This not being my own software, I would be willing to submit this to fedora (when it works and if I can get sponsors) but for that, my rpm needs to get created.
Thanks again!
Best wishes,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
____________________________________________________________
FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop!
Check it out at http://www.inbox.com/earth
7 years, 9 months
Brasero: can't choose a directory.
by William Mattison
I'm using Fedora-23, last patched last Thursday, 6/23.
Last Friday, I was trying to back up some directory trees to DVD. I
launched Brasero, and chose "New Data Project". The result should have
been a list of the directories and files at the home or root level. The
file list area was blank. When I try "Project" -> "Open", a populated
file browser shows up. I can navigate the file system successfully, but
I can't find a way to select a directory for copying to the DVD.
This all worked in March in F-22, when I backed up before upgrading to
F-23. What am I doing wrong? Or what have I not done that I need to do?
Thank-you in advance for your help.
Bill.
7 years, 9 months
Re: looking for a BASH tool
by Tom Killian
Once upon a time, SternData <subscribed-lists(a)sterndata.com> said:
> Years ago, I used a tool called CED and PCED on DOS systems. I could
> type in "abc" and press an up-arrow and it would walk back through my
> stack of DOS commands showing only those with "abc" in them.
>
> There's *got* to be a similar tool for bash, but my google-fu is weak
today.
In addition to keyboard shortcuts...
history | grep abc | less
If what you're looking for came from a different, now closed, terminal
window, try
grep $HISTFILE abc | less
7 years, 9 months
3.6.x version necessary before upgrading to 4.0
by Gianluca Cecchi
Hello,
is there any requirement to update at latest 3.6.x version the engine
before upgrading to 4.0? Or could I have for example 3.6.3 and directly
upgrade to 4.0?
Do you test upgrade only from latest previous version or what?
And what about nodes in case they start as plain CentOS 7.x in 3.6.x?
Thanks,
Gianluca
7 years, 9 months
dual screen settings lost after dnf update
by Gary Stainburn
I have a F23 system (upgraded from F22 a while since) with two screens.
The two screens were configured correctly with the mouse moving off the right
side of the left screen and appearing on the left side of the right screen,
giving one desktop spread across the two monitors.
I've done a 'dnf update' and now both screens are showing the same content.
I know in the past I used to control this through xrandr and a bash script,
but I haven't had to use that in ages. I thought all settings were now in
KDE.
However, Google etc. points me to kscreen inside "system settings" but I can't
find where to change this setting.
Can anyone help please?
7 years, 9 months
Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
by David Dembrow
Date: Sun, 26 Jun 2016 11:41:21 -0400
From: "Mark C. Allman"<mcallman(a)allmanpc.com>
Subject: Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
To:users@lists.fedoraproject.org
Message-ID:<2f2ce2bd-5601-811c-6024-2aa8da6a7e83(a)allmanpc.com>
Content-Type: text/plain; charset=utf-8
On 06/26/2016 10:21 AM, David Dembrow wrote:
> After completing the fedora 24 upgrade on a fedora 23 system there was
> no graphical login and the system appeared to be running in console
> mode (run level 3).
>
> I have always used KDE as the display manager and desktop. I noticed
> a similar problem posted but none of its recommendations were
> appropriate for my system.
>
> I found the graphical.target set as the default (systemctl
> get-default). Then I noticed the graphical.target expects to have a
> display-manager.service but the display-manager.service file was
> missing. from the /etc/systemd/system directory.
>
> I copied the /etc/systemd/system/display-manager.service file from a
> fedora 23 system and enabled the service (systemctl enable
> display-manager.service). Started the service (systemctl start
> display-manager.service) and poof the graphical kde login manager and
> desktop returned.
>
> Should this get posted as a bug or is the kde login manager expected
> to disappear with wayland?
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct:http://fedoraproject.org/code-of-conduct
> Guidelines:http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away:http://ask.fedoraproject.org
It's now the sddm.service. I had the same problem. We all need the usual
"dnf install sddm, systemctl enable sddm; systemctl start sddm."
After I looked at a display-manager.service instance on one of my
remaining F23 systems I remembered that sddm was on the way:
[me@rigel ~]$ cat /etc/systemd/system/display-manager.service
[Unit]
Description=Simple Desktop Display Manager
Documentation=man:sddm(1) man:sddm.conf(5)
Conflicts=getty(a)tty1.service
After=systemd-user-sessions.servicegetty(a)tty1.service
plymouth-quit.service
[Service]
ExecStart=/usr/bin/sddm
Restart=always
#PrivateTmp=yes
[Install]
Alias=display-manager.service
It worked for me but that doesn't mean it solves the problem for everyone.
-- Mark C. Allman
-- Founder, See How You Ski,www.seehowyouski.com
-- Sr. Project Manager, Allman Professional Consulting,www.allmanpc.com
-- Twitter: @allmanpc
Mr Allman,
Thanks for the reply. I did not have sddm installed, I did have kdm (but without a link to display-manager). I can use sddm if that is going to be the future, but I still prefer kdm - and with some advice from this list I can correctly use either one.
Regards,
---d.dembrow
7 years, 9 months
Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
by David Dembrow
Date: Sun, 26 Jun 2016 22:37:30 +0800
From: Ed Greshko<ed.greshko(a)greshko.com>
Subject: Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
To:users@lists.fedoraproject.org
Message-ID:<e943f66d-26d3-3eef-ce4d-58ff5806fe3a(a)greshko.com>
Content-Type: text/plain; charset=utf-8
On 06/26/16 22:21, David Dembrow wrote:
> After completing the fedora 24 upgrade on a fedora 23 system there was no graphical
> login and the system appeared to be running in console mode (run level 3).
>
> I have always used KDE as the display manager and desktop. I noticed a similar problem
> posted but none of its recommendations were appropriate for my system.
>
> I found the graphical.target set as the default (systemctl get-default). Then I noticed
> the graphical.target expects to have a display-manager.service but the
> display-manager.service file was missing. from the /etc/systemd/system directory.
>
> I copied the /etc/systemd/system/display-manager.service file from a fedora 23 system
> and enabled the service (systemctl enable display-manager.service). Started the service
> (systemctl start display-manager.service) and poof the graphical kde login manager and
> desktop returned.
Well, first of all, /etc/systemd/system/display-manager.service should*not* be a file,
but a symbolic link.
It should either link to /usr/lib/systemd/system/sddm.service or
/usr/lib/systemd/system/kdm.service if you are using kdm.
What does "systemctl status display-manager" return?
Mr Greshko,
Thanks very much for the correction. I did not look for symbolic links and I did not have sddm installed on my system. I did have a kdm.service file and enabling kdm creates the link as expected. I can use sddm if that is going to be the future, but I still prefer kdm - and with some advice from this list I can correctly use either one.
The systemctl status display-manager command returns the following (before I added the display-manager.service file):
[] display-manager.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
Regards,
---d.dembrow
7 years, 9 months
No Graphical Login After Fedora 24 Upgrade From Fedora 23
by David Dembrow
After completing the fedora 24 upgrade on a fedora 23 system there was
no graphical login and the system appeared to be running in console mode
(run level 3).
I have always used KDE as the display manager and desktop. I noticed a
similar problem posted but none of its recommendations were appropriate
for my system.
I found the graphical.target set as the default (systemctl
get-default). Then I noticed the graphical.target expects to have a
display-manager.service but the display-manager.service file was
missing. from the /etc/systemd/system directory.
I copied the /etc/systemd/system/display-manager.service file from a
fedora 23 system and enabled the service (systemctl enable
display-manager.service). Started the service (systemctl start
display-manager.service) and poof the graphical kde login manager and
desktop returned.
Should this get posted as a bug or is the kde login manager expected to
disappear with wayland?
7 years, 9 months
pcregrep question
by bruce
Hi.
I'm embarrassed to say I can't resolve this. So, my mind has gone blank!
I've got a test file, with the following lines. Basically, I want a
grep/regex to traverse the multiple lines to return the lines.
ll_=urllib.quote_plus(simplejson.dumps(b2))+"\n"
pathchildcount_filep.write(ll_)
I've tried a number of attempts.. I thought something similar to the
following should work. (but no luck)
pcregrep -Mi ".+urllib.quote_plus(simplejson.dumps(b2))(.+\n).+path" foo.py
The test file actually has the "\n" chars as text but the regex/grep can
ignore it, to focus on getting the two lines..
In the case of the example, both lines start at the beginning of the line.
Thanks
(no laffing!!)
7 years, 9 months
Re: compile XV?
by William Mattison
Good afternoon,
> I know its not been updated in years, but this is still a must have
for me. I just upgraded > to fedora 24 (64bit)
> and Im trying to compile it from source because the rpms Ive found
are either broke or > dont work right.
[... snip ...]
> any ideas?
I like "xv" also, especially for colorizing weather satellite imagery.
When I wanted to add it to my Fedora system in July 2013 (F-18 at that
time), Ed Greshko pointed me to this rpm:
> > xv is in the rpmfusion repositories.
> >
> > xv-3.10a.jumbopatch.20070520-18.fc18.1.x86_64 : Visualisateur sous
X pour
> > : quasiment tous les
types d'images
> > Repo : rpmfusion-nonfree-updates
> > Matched from:
> > Filename : /usr/bin/xv
I don't recall having any problems with it. I'm at F-23 now, and it
still works. My only suggestion is to try the rpm that Ed pointed me
to. The full Fedora users group discussion on this starts here:
https://lists.fedoraproject.org/pipermail/users/2013-July/437341.html
Two more general notes on "xv"...
1. I personally would like to see this tool supported again.
2. A new color standard "Rec. 2020" has been adopted. Eventually,
monitors will become available that can display the full range of colors
that this new standard encodes. That range of colors is substantially
larger than the sRGB that most of today's monitors can display. xv, the
gimp, and everything else that involves color will need updating to
properly handle and display colors encoded according the new standard.
I suspect the same is true of Fedora itself, and quite possibly the
Linux kernel. I hope the appropriate people are on top of this!
Bill.
7 years, 9 months
