build.opensuse.org has been unavailable for hours now. Will we ever get the
authentication stable? autobuild never gave me a Bad Gateway
Anders
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
When I start up xchat on a clean install of M1 I see these messages ;
xchat
Traceback (most recent call last):
File "/usr/lib64/python2.7/site.py", line 62, in <module>
import os
File "/usr/lib64/python2.7/os.py", line 398, in <module>
import UserDict
File "/usr/lib64/python2.7/UserDict.py", line 83, in <module>
import _abcoll
File "/usr/lib64/python2.7/_abcoll.py", line 11, in <module>
from abc import ABCMeta, abstractmethod
File "/usr/lib64/python2.7/abc.py", line 8, in <module>
from _weakrefset import WeakSet
File "/usr/lib64/python2.7/_weakrefset.py", line 5, in <module>
from _weakref import ref
ImportError: No module named _weakref
Regards,
Roelof
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
Does factory works with Gnome3 or still with Gnome2
Roelof --
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
see $SUBJECT
Apparently the BS does not retrigger the build after libusb-1_0 did
finish, so libusb-compat stays in "failed" state-
--
Stefan Seyfried
"Dispatch war rocket Ajax to bring back his body!"
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
Can the timings for factory-publish be shortned any ?
The reason I ask is because of the time lag beteen factory-publish's ?
Latest date of files of files published[1]: 02-Jun-2011
Todays date: 07-Jun-2011
5 days seems a long time between factory publish's.
- Could the publish be refreshed say 2 times a week ?
- Could the factory publish/refresh be automated somehow e.g via a crontab
and script to do the job putting out new updates/removing old
files/refreshing metadata ?
Glenn
[1] http://download.opensuse.org/factory/repo/oss/suse/x86_64/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
I think the network installer isn't very efficient with bandwidth
usage: http://img69.imageshack.us/img69/5331/networkinstallbandwidth.png
I think the install time could be cut down significantly. On an
average broadband connection (6mbps) there's nowhere near maximum
utilization.
--
Med Vennlig Hilsen,
A. Helge Joakimsen
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
I just finished publishing the new, up-to-date syslog-ng FAQ. I wonder,
where I should publish URLs, so openSUSE users could easily find it. I
already published it on the openSUSE forum, as many of the questions
come up also in openSUSE related discussions. Could I also put it in the
syslog-ng rpm package description, or that's not the right place for it?
It's available at http://www.balabit.com/wiki/syslog-ng-faq
Bye,
--
Peter Czanik (CzP) <czanik(a)balabit.hu>
BalaBit IT Security / syslog-ng upstream
http://czanik.blogs.balabit.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
I was just wondering what are the most recommended packages to test?
Packages in 12.1 M1? Factory?
I think it frowned upon to test and submit bug reports on Factory packages...
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
Working on OpenNebula. The upstream source provides a script to start a
daemon. With a couple of patches I turned the script into an init script
that keeps rpmlint quiet. In the package I put the patched script into
/etc/init.d.
The problem I now have is that I do not want to run the daemon as root.
The implication would be that root would have to have password less
login enabled on all nodes that are part of the cloud. Is there a way to
run the daemon as a specific user? The package also creates a user
account for the cloud administrator and the daemon should run as this
user. Should I try something like "sudo -u USERNAME PATH_TO_DAEMON" in
the init script or are there better/other ways to get his done. The user
does not have a password, thus the account cannot login interactively.
Help is appreciated.
Thanks,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
rschweikert(a)novell.com
rschweikert(a)ca.ibm.com
781-464-8147
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Greg Freemyer wrote:
> Linda,
>
> Have you tried building locally just like factory does?
>
> By that I mean:
>
>> cd ~��� � � � � � � � � � � � � � � � � � � #or wherever you want the
> source package
>> mkdir obs; cd obs;� � � � � � � � �� #you are now in your new working dir
>> osc co openSUSE:Factory transmission� #now you have the source as OBS
> has it
----
No...*ahem*...
I have:
Username: username
Password:
done
Failed to reach a server:
Tunnel connection failed: 403 Forbidden
-----
On a different note....an additional problem I found in my build env...
I have files in "/usr/local/*.
(um, users are allowed to use /usr/local, no?)....
Moving /usr/local aside allowed transmission to build.
Just guessing, but maybe when building system rpm's, "/usr/local/" shouldn't be used as part of the path for anything?
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org