Hi,
openSUSE:10.2 is not maintained since quite some time, so I will remove the
repositories of it today.
As usual, it is still accessable via DISCONTINUED: workspace, but it should be
not used anymore if you care about your security ;)
bye
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi
some time ago I wrote a patch for storing osc credentials in Gnome
keyring instead of ~/.oscrc. It uses keyring only if available
otherwise it falls back to using configuration file.
Any comments on committing this into svn?
The patch is available in bugzilla:
https://bugzilla.novell.com/show_bug.cgi?id=460540
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
Is it possible to get libelf0 copied over to devel:libraries:c_c++ (or
to somewhere more appropriate). I'd like to have it in a place that has
build targets for more than just Factory, (esp SLE_10).
Thanks!
Donavan
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
When building locally in a qemu/chroot and debugging I find I want to edit the
files in the chroot from my desktop gui editor but they're all owned by 399:399.
This pair of patches allows me to set the uid:gid to match my local user and
eases this process.
usage is:
build --build-abuild-id uid:gid
or more usually:
osc build --build-abuild-id 500:500
osc also accepts (and extends the default) .oscrc settings:
build-abuild-id = 500:500
It only supports numeric ids.
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
Hi,
poeml@batavia510 ~ % osc rdelete home:poeml:branches:Subversion
Traceback (most recent call last):
File "/suse/poeml/bin/osc", line 12, in <module>
r = babysitter.run(osccli)
File "/suse/poeml/osc-trunk/osc/babysitter.py", line 38, in run
return prg.main()
File "/suse/poeml/osc-trunk/osc/cmdln.py", line 255, in main
return self.cmd(args)
File "/suse/poeml/osc-trunk/osc/cmdln.py", line 278, in cmd
retval = self.onecmd(argv)
File "/suse/poeml/osc-trunk/osc/cmdln.py", line 394, in onecmd
return self._dispatch_cmd(handler, argv)
File "/suse/poeml/osc-trunk/osc/cmdln.py", line 1084, in _dispatch_cmd
return handler(argv[0], opts, *args)
File "/suse/poeml/osc-trunk/osc/commandline.py", line 1001, in do_rdelete
elif len(meta_get_packagelist(conf.config['apiurl'], prj)) >= 1 and not opts.force:
File "/suse/poeml/osc-trunk/osc/core.py", line 1625, in meta_get_packagelist
f = http_GET(u)
File "/suse/poeml/osc-trunk/osc/core.py", line 1552, in http_GET
def http_GET(*args, **kwargs): return http_request('GET', *args, **kwargs)
File "/suse/poeml/osc-trunk/osc/core.py", line 1542, in http_request
fd = urllib2.urlopen(req, data=data, timeout=timeout)
TypeError: urlopen() got an unexpected keyword argument 'timeout'
[1] 9270 exit 1 osc rdelete home:poeml:branches:Subversion
the timeout argument to urllib2.urlopen was introduced with Python 2.6,
as it seems.
One way to work around would be to set socket.setdefaulttimeout(timeout);
possibly only for certain commands; or globally if it doesn't have negative
effects.
What do you think?
Peter
--
"WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH
Research & Development
Hi,
I have seen some good updates for OSC, but I am still missing good proxy
support. Most of the day I am behind a corporate proxy server and this
prevents me from using OSC.
I can use the webclient (http://build.opensuse.org) or MonoOSC, but both
are lacking the ability the submitreq commands.
I have checked the internet for the proxy support for OSC and what I
found is that this will be a though job as that Python support for
proxies is not that great. An alternative would be of course to create
the submitreq possibility within the webclient or in MonoOSC (depending
if there are api's for it).
Thanks
Regards
Raymond
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
On 08/05/09 12:29, Petit Eric wrote:
> osc provide folowing submitreq features, wich one are you interested :
>
> osc submitreq create [-m TEXT]
> osc submitreq create [-m TEXT] SOURCEPRJ SOURCEPKG DESTPRJ [DESTPKG]
For this one I have send you the osc -H output already.
> osc submitreq list [PRJ [PKG]]
This one you already indicated the required information.
> osc submitreq log ID
> osc submitreq show [-d] ID
> osc submitreq accept [-m TEXT] ID
> osc submitreq decline [-m TEXT] ID
> osc submitreq delete [-m TEXT] ID
> osc submitreq revoke [-m TEXT] ID
For these I will send you the required output, so that you can include
it in MonoOSC.
Regards
Raymond
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
On 08/05/09 11:35, Petit Eric wrote:
> You confirm, MonoOSC work behind a proxy ? i never test it or had
> feedback of it :-)
I can confirm that MonoOSC is working fine behind a proxy. The initial
issues that I had with it, was purely due to being unknown to the
MonoOSC interface.
> I don't know wath you mean by submitreq, can you give me more details
> and as you say, if API support it, i can easy add this, also if you
It concerns the command : osc submitreq create -m"text.."
<SOURCEPROJECT> <PACKAGE> <TARGETPROJECT>
This command will create a request to include the changes made in the
<SOURCEPROJECT> to the <PACKAGE> in the <TARGETPROJECT>. You have more
subcommands of osc submitreq, like list, revoke, accept, etc.
I will see if I can find anything on that website you gave me before
with regards to the available api's.
Regards
Raymond
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
[eric@SurfzoidPC tmp]$ sudo urpmi ./osc-0.117-9.1.x86_64.rpm
Following pkg will be installed to satisfies dependency
Paquetage Version Révision Arch
(média « Contrib »)
python-urlgrabber 3.0.0 2mdv2009.1 noarch
(ligne de commande)
osc 0.117 9.1 x86_64
un espace additionnel de 1Mo sera utilisé.
280Ko de paquets seront récupérés.
Procéder à l'installation des 2 paquetages ? (O/n) o
$MIRRORLIST:
media/contrib/release/python-urlgrabber-3.0.0-2mdv2009.1.noarch.rpm
attention: ./osc-0.117-9.1.x86_64.rpm: Entête V3 DSA signature: NOKEY,
key ID eefefde9
The following pkg have an invalid signature:
./osc-0.117-9.1.x86_64.rpm: Signature incorrecte (NOT OK (no key):
./osc-0.117-9.1.x86_64.rpm: Entête V3 DSA signature: NOKEY, key ID
eefefde9)
would you like to continue the install ? (o/N) o
installation de ./osc-0.117-9.1.x86_64.rpm
/var/cache/urpmi/rpms/python-urlgrabber-3.0.0-2mdv2009.1.noarch.rpm
Préparation ...
#########################################################################################
1/2: python-urlgrabber
#########################################################################################
2/2: osc
#########################################################################################
[eric@SurfzoidPC tmp]$ osc
Traceback (most recent call last):
File "/usr/bin/osc", line 7, in <module>
from osc import commandline
ImportError: No module named osc
[eric@SurfzoidPC tmp]$
--
Cordially.
Small Eric Quotations of the days:
---------------------------------------------------------------------------
If one day one reproaches you that your work is not a work of
professional, say you that:
Amateurs built the arch of Noah, and professionals the Titanic.
---------------------------------------------------------------------------
Few people are done for independence, it is the privilege of the powerful ones.
---------------------------------------------------------------------------
No key was wounded during the drafting of this message.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I want to create a package for openSUSE 11.1 that requires Qt >= 4.5,
and so I say in the BuildRequires entry. That means I must compile it
against the version from KDE:Qt, but there are other packages in the
repo, and I would prefer that they use the official Qt packages.
Using
<repository name="openSUSE_11.1">
<path project="KDE:Qt" repository="openSUSE_11.1"/>
<path project="openSUSE:11.1" repository="standard"/>
<arch>x86_64</arch>
<arch>i586</arch>
</repository>
all the packages will use the version from KDE:Qt.
So I though that using
<repository name="openSUSE_11.1">
<path project="openSUSE:11.1" repository="standard"/>
<path project="KDE:Qt" repository="openSUSE_11.1"/>
<arch>x86_64</arch>
<arch>i586</arch>
</repository>
packages that BuildRequire "libqt-devel" would use the one from
openSUSE:11.1, and the ones that BuildRequire "libqt-devel >= 4.5.0"
would use the one from KDE:Qt.
But at practice what I get with the second option is an expansion
error complaining about the lack of "libqt-devel >= 4.5.0".
...well, it isn't missing, it just should continue searching. Bug or
something unfixable given the internal working of the OBS?
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org