rpmbuild error for typhoon
by Ranjan Maitra
Hi,
I was trying to build a Fedora 22 rpm for typhoon:
https://sites.google.com/site/typhoonweatherapp/home
modifying a python-based spec file of mine, but I have run into problems.
Here is the spec file:
$ fpaste typhoon.spec
Uploading (1.1KiB)...
http://ur1.ca/n3vhs -> http://paste.fedoraproject.org/243565/75271614
And here are the errors:
$ rpmbuild -bb typhoon.spec
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.t0ahW1
+ umask 022
+ cd /home/maitra/rpmbuild/BUILD
+ cd /home/maitra/rpmbuild/BUILD
+ rm -rf typhoon-0.8.9.4
+ /usr/bin/bzip2 -dc /home/maitra/rpmbuild/SOURCES/typhoon-0.8.9.4.tar.bz2
+ /usr/bin/tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd typhoon-0.8.9.4
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.cn6iYb
+ umask 022
+ cd /home/maitra/rpmbuild/BUILD
+ cd typhoon-0.8.9.4
+ /usr/bin/python setup.py install -O1 --skip-build --root /home/maitra/rpmbuild/BUILDROOT/typhoon-0.8.9.4-1.fc22.x86_64
Unable to init server: Could not connect: Connection refused
running install
running install_lib
warning: install_lib: 'build/lib' does not exist -- no Python modules to install
running install_scripts
error: cannot copy tree 'build/scripts-2.7': not a directory
error: Bad exit status from /var/tmp/rpm-tmp.cn6iYb (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.cn6iYb (%build)
Any suggestions on how to fix these?
Many thanks and 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.
____________________________________________________________
Can't remember your password? Do you need a strong and secure password?
Use Password manager! It stores your passwords & protects your account.
Check it out at http://mysecurelogon.com/manager
8 years, 9 months
source iso
by JD
I noticed that since 21, source iso's are not provided, only
individual package sources under SRPMS.
8 years, 9 months
Fedora21/22 grub doesn't recognize my raid1/LVM partitions
by John Wright
I have 2 500G hard drives partitioned with a few 'normal' partitions
for /boot, swap, etc but mostly in a raid 1 array, which is divided
into several LVM partitions. For many Fedora releases, I have done
fresh installs, preserving the /home LVM partition, and rotating the
root partition among several 30-40G LVM partitions for /. This has
always worked splendidly until Fedora 21/22. Recently I decided that
it was time to move up to Fedora 22, and with failing that, to
Fedora 21. I have tried several Fedora 22 and Fedora 21.
live install disks (desktop, server) and the server isos. With the
live disks, the installer doesn't see my existing LVM partitions,
so I can't try to install into them. With the 21 and 22 server
isos, the installer sees the LVM partitions and appears to proceed
normally, but the final reboot boots into a grub rescue shell, and
the only partition visible to this shell is my /boot partition. I
also tried the Fedora 22 netinstall iso, which also ultimately
resulted in reboot into the grub rescue shell.
I have googled several variations of 'grub doesn't recognize LVM
partitions' without turning up anything helpful.
Have there been changes to the LVM software that might result in
an incompatibility between grub and older LVM versions?
Best,
-jmw-
8 years, 9 months
unable to open file with kwrite and kate
by Maurizio Marini
If I click on open into kate or kwrite toolbar, cursor start to roteate and
then stop, without opening selection file popup; kwrite and kate loose focus
and it is impossible to re-focus on them
Upper right X on cornetr does not close windows
kill -9 does
-m
8 years, 9 months
fedora 22: KDE Application Launcher treeview
by Maurizio Marini
I am very disappointed, after more than 15 upgrade of Fedora w/out reinstalling,
22 is a messy:
1. claws addressbook tab completion when selecting recipients does not work
2. changing from one window application to another cause a screen flickering
3. look and feel is very different by previous release
I will ask on each mailing list, but in the meantime, please help me with KDE
Apllication Launcher: I have ever used it in a tree-view manner, classic view
now I am not able to find where reset it to this view
-m
8 years, 9 months
Enter your password to unlock your keyring
by JD
I tried to report a bug via abrt.
It refused my original password, and my current password.
I have had only 2 passwords. I changed from original to
current more than 2 weeks ago.
So, how can I get around this?
8 years, 9 months
telnet session closing with ^]
by Maurizio Marini
When I use telnet inside Konsole,
to close telnet:
Escape character is '^]'
once upon a time, pressing
Contr and ]
closed telnet session, now it enlarge fonts, sadly.
I have searched into
Konsole/Settings/Edit currente Profile.../Keyboard
Kde Menu/Settings/System settings/Shortcuts and Gestures
but I haven't found anything relevant
please help, to close a telnet session I have to open a 2^ console and kill -9
telnet pid
Ugly
-m
8 years, 9 months
Building FF from source
by JD
Hi All,
has anyone built FF from source RPM?
I tried, and it requires much older versions of things.
Why is that?
8 years, 9 months
F22 Atomic networking failure in OpenStack (A regression from F21!)
by Erik Swanson (eriswans)
So, in an OpenStack environment I'm trying to use, F22 Atomic can't get an IP/routing info, but F21 Atomic *can*.
The first sign that something's up is a non-trivial pause on "A start job is running for Network Manager Wait Online", followed by cloud-init failing:
[ 36.377396] cloud-init[721]: 2015-07-09 20:48:49,254 - util.py[WARNING]: Route info failed: Unexpected error while running command.
The complete boot log of the F22 failure is here: http://pastie.org/private/1qikbe1hu328ajszohq5a
What's interesting is that F21 Atomic comes up fine, in a completely identical environment. A boot log of F21 succeeding is here: http://pastie.org/private/ogopev1kbrf5y3lyahhqba
The instances are identical in absolutely every way, except for the image. I have repeated the same result multiple times: F21 always comes up successfully, F22 always fails.
Is this something I should file in a bug report? Is there any way I can get any more debug info on what's happening with F22? (Please keep in mind that because it never brings its networking up, it won't see any user-data scripts I try to inject, nor can I log in to its console.)
—
Erik Swanson
8 years, 9 months