This fixes:
~> osc checkout
Traceback (most recent call last):
File "/usr/bin/osc", line 21, in <module>
r = babysitter.run(osccli)
File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 52, in run
return prg.main()
File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 310, in main
return self.cmd(args)
File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 333, in cmd
retval = self.onecmd(argv)
File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 449, in onecmd
return self._dispatch_cmd(handler, argv)
File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1179, in _dispatch_cmd
return handler(argv[0], opts, *args)
File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 3386, in do_checkout
m = re.match(r"obs://([^/]+)/(\S+)/([^/]+)/([A-Fa-f\d]+)\-(\S+)", args[0])
IndexError: tuple index out of range
Signed-off-by: Petr Uzel <petr.uzel(a)suse.cz>
---
osc/commandline.py | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/osc/commandline.py b/osc/commandline.py
index e0981bb..adea1cf 100644
--- a/osc/commandline.py
+++ b/osc/commandline.py
@@ -3382,6 +3382,10 @@ Please submit there instead, or use --nodevelproject to force direct submission.
else:
expand_link = True
+ if not args:
+ raise oscerr.WrongArgs('Incorrect number of arguments.\n\n' \
+ + self.get_cmd_help('checkout'))
+
# XXX: this too openSUSE-setup specific...
# FIXME: this should go into ~jw/patches/osc/osc.proj_pack_20101201.diff
# to be available to all subcommands via @cmdline.prep(proj_pack)
--
1.7.3.4
Petr
--
Petr Uzel
IRC: ptr_uzl @ freenode
peer-io.c: In function ‘tr_evbuffer_write’:
peer-io.c:285:31: error: dereferencing pointer to incomplete type
make[1]: *** [peer-io.o] Error 1
---
This one REALLY has me curious as to how it was build for the
distribution, since I have been unable to build transmission from their
source repo for some time due to something along the lines of (if not
the exact same) error I'm getting from the 11.4 package.
I have a system that seems to be fully updated to 11.4, and installed
the appropriate build-requires.
Yet another rpmbuild -bb fails with errors indicating it never should
have been buildable to a binary in the first place.
So what's going on?
----
FWIW, I also tried using the "build" command to see if that worked any
better...:
expanding package dependencies...
reqesting
dir:///Share/suse/11.4/repo/oss/suse/x86_64/rpm-4.8.0-27.1.x86_64.rpm
failed: 501 Protocol scheme 'dir' is not supported
Warning: distribution not specified, assuming 'default' (see
/usr/lib/build/configs).
downloading
zypp://Open_Suse_11.4_Update/rpm/x86_64/Mesa-7.10.2-7.3.1.x86_64.rpm ...
reqesting
dir:///Share/suse/11.4/update/rpm/x86_64/Mesa-7.10.2-7.3.1.x86_64.rpm
failed: 501 Protocol scheme 'dir' is not supported
So how does one build binary RPM's from source rpm's or am I just
getting 'lucky' in choosing broken SRPM's?
:-(
(and people want me to use the build-system to build updates for
products...um... a main reason for resisting that has been being
able to make sure I wasn't building in a 'walled garden', that
included things I didn't know about.
In it's simplest form, this merely means the build environment
seems to include things that aren't obvious to someone
building the packages on a standard 11.4 system....
As such, it doesn't seem to be a "portable" build environment...
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
to my knowledge systemd supposed to be the default init daemon in 12.1.
Doesn't it make sense to activate it now (or as early as possible) to
get at least some feedback from the people running factory?
Tim
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hey there,
I've tried to summarize the process of dropping (and reaching the
decision to drop) a package from Factory here:
http://en.opensuse.org/openSUSE:Factory_drop_policy
There is also a small howto so people know how to drop the package (and
restore it if needed).
As there is no strict rule or exact step-by-step way to decide if a package
should be dropped, the "policy" described there is rather fuzzy. I don't
think it's an issue, but if people this is not good enough, we can
improve things.
Is there anything missing on that page? Or does it look good?
Cheers,
Vincent
--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
I'm not sure how this ever passed QA, but when I try to load
'nmbd', I get:
/usr/sbin/nmbd: symbol lookup error: /usr/sbin/nmbd: undefined symbol: _talloc_realloc_array.
ldd -r shows a bunch of similar undefined symbols (shown further below).
my samba rpm is samba-3.5.7-1.17.1.x86_64.
---
In checking, I found:
lrwxrwxrwx 1 18 Jun 5 17:49 /usr/lib64/libtalloc.so.2 -> libtalloc.so.2.0.1*
-rwxr-xr-x 1 43280 Mar 1 04:21 /usr/lib64/libtalloc.so.2.0.1*
(Note: there was only libtalloc.so.2, I moved it to it's 'real version',
and created the symlink to be consistent with other libs -- to see if that
would solve the problem (it didn't)).
looking at the lib,
# readelf -s libtalloc.so.2|grep realloc
34: 0000000000000000 0 FUNC GLOBAL DEFAULT UND realloc(a)GLIBC_2.2.5 (2)
49: 0000000000007000 47 FUNC GLOBAL DEFAULT 12 _talloc_realloc_array
62: 0000000000006ff0 7 FUNC GLOBAL DEFAULT 12 talloc_realloc_fn
65: 0000000000006b80 1124 FUNC GLOBAL DEFAULT 12 _talloc_realloc
I see the symbols.
When I try to load nmbd with ldd:
Ishtar:packages/rpms/x86_64> ldd /usr/sbin/nmbd
linux-vdso.so.1 => (0x00007fffe610a000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fa6d18db000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007fa6d16c3000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fa6d14bf000)
libwbclient.so.0 => /lib64/libwbclient.so.0 (0x00007fa6d12a1000)
libpopt.so.0 => /lib64/libpopt.so.0 (0x00007fa6d1095000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007fa6d0e5f000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007fa6d0b94000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007fa6d096c000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fa6d0768000)
libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007fa6d0521000)
liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007fa6d0312000)
libz.so.1 => /lib64/libz.so.1 (0x00007fa6d00fa000)
libc.so.6 => /lib64/libc.so.6 (0x00007fa6cfd8d000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa6d1af2000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007fa6cfb84000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fa6cf981000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa6cf764000)
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007fa6cf549000)
libssl.so.1.0.0 => /lib64/libssl.so.1.0.0 (0x00007fa6cf2ed000)
libcrypto.so.1.0.0 => /lib64/libcrypto.so.1.0.0 (0x00007fa6cef3c000)
I see no reference to 'libtalloc' -- why not??
----
Note, I then tried to build the package from source and had it fail in
multiple ways -- there's no way the source could build the binary -- the
spec has error in it.
1)
It references:
vendor_tag=$( grep ^Release: ${RPM_SOURCE_DIR}/samba.spec | \...
"samba.spec" is in the "SPEC" dir along with other 'spec' files. How
could this build work on a standard system, while the source files are
in the RPM_SOURCE_DIR (sources/samba-3.5.7 on my system, sources on standard).
The spec file is NOT in the sources dir.
2) MAJOR FAIL in trying to build binaries & source packages:
Checking for unpackaged file(s): /usr/lib/rpm/check-files /usr/src/packages/BUILDROOT/samba-3.5.7-1.17.1.x86_64
error: Installed (but unpackaged) file(s) found:
/usr/share/man/man1/ad2oLschema.1.gz
/usr/share/man/man1/oLschema2ldif.1.gz
/usr/share/man/man3/ldb.3.gz
RPM build errors:
Installed (but unpackaged) file(s) found:
/usr/share/man/man1/ad2oLschema.1.gz
/usr/share/man/man1/oLschema2ldif.1.gz
/usr/share/man/man3/ldb.3.gz
----
So how could the source build if files are being left over?
Is some special rpm being used on build machines that ignores errors?
Of course none of the above explains why nmbd isn't linking with libtalloc,
which was the root problem of this mess! ;-)
(up-to-butt in alligators; meant to drain swamp?)....
So Does anyone have ideas as to what's going on? -- especially, why nmbd
isn't linking against libtalloc and how it ever got released that way?
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
All,
I'm hoping to push a computer forensic app called "log2timeline" to a
devel repo soon. And then to factory, possibly.
(it is still fairly young, so putting it in a stable repo may be pointless.)
There are a number of other computer forensic apps on OBS, but mostly
spread around in various peoples home projects. (I'd say I found at
least 20 packages related to computer forensics in my casual looking
on OBS)
For those that don't know "forensics" is the application of science to
the legal world. So one could argue these apps should just be added
to the science project, but I don't think its really a good fit.
science:forensics would be my preference, but it doesn't exist (yet).
Can anyone recommend where I should SR my package to? Should I file a
bugzilla to create science:forensics?
Thanks
Greg
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Right, I had openjdk installed but I had an application that required
Sun java which I installed using zypper.
Next I tried using update-alternatives, no worky.
Read and re-read the manpage which is very wordy but leaves me clueless.
I googled and eventually stumbled upon "update-alternatives --all" which
offered options that allowed me to select java-1_6_0-sun, but javac was
still pointing to openjdk.
"zypper in java-1_6_0-sun-devel" and automatically it righted everything.
Over the years I've found update-alternatives to be very confusing and I
wish the manpage at least had a few useful examples. I think I'll have
to find the maintainer and make suggestions as until now I've not had
any luck reading the manpage and making SWAGs (Scientific Wild Ass
Guesses - Trademark -- Amdahl Corporation).
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
On May 30th I get an update which deprecate /etc/sysconfig/sysctl
It migrate a part of configuration to /etc/sysctl.conf and create a /etc/sysctl.d ( but empty )
But it seems some of the configuration are not migrated or respected
I've that
## Type: list(yes,no,)
## Default: no
#
# Runtime-configurable parameter: use temporary IPv6 addresses
# instead of using the EUI-64 interface identifer
#
IPV6_PRIVACY="no"
Why because I really don't care about privacy. I don't need to hide me, and hate too much those temporary things.
My taste, ok :-)
but in sysctl.conf
### converted from /etc/sysconfig/sysctl at Tue, 31 May 2011 06:16:19 +0200
net.ipv4.tcp_syncookies = 1
net.ipv4.ip_forward = 0
kernel.sysrq = 1
net.ipv4.tcp_ecn = 0
Informations about
rpm -qf /etc/sysctl.conf
procps-3.2.8-34.1.x86_64
c-3po:~ # rpm -q --changelog procps-3.2.8-34.1.x86_64
* Tue May 17 2011 lnussel(a)suse.de
- load sysctls earlier (bnc#664550)
- move distro defaults to /lib/sysctl.d to avoid .rpmnew files
- enable IPv6 privacy by default (bnc#678066)
* Thu May 05 2011 jeffm(a)suse.de
- boot.sysctl: Add support for loading defaults from
/boot/sysctl.conf-$(uname -r) before loading /etc/sysctl.conf
to allow each kernel flavor to adjust defaults without
different kernel configuration options.
When I cat /lib/sysctl.d/sysctl.conf
I've found now the suse distribution defaults with privacy enabled.
and have information how to re-disable these privacy.
Can someone (Ludwig ?) can confirm that during migration the upgrade forget to manage the privacy configuration ?
If it's reproducible, I'll open a bug for that.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
Which filesystems in opensuse 11.4 and later will handle these
requirements ?
1. -larger disk volumes i.e in the 2 to 3 Terabyte range.
2. -lots of files on the disk > 150,000+
3. -will handle a system restart when system stops responding [restart
with a power off/on]
4. -have a journalled file system recovery to ensure filesystem and files
are in a healthy state after a system freeze/reboot ?
What file systems does the build service use to handle the volumes of data
and load ?
Thanks Glenn
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org