Hello,
whether I add "Packager" in a spec file or not, rpmlint complains in both
cases. One time because of hardcoding. The other time because it is
missing.
Could this please be fixed?
What I would like to see is that the buildservice-email-address also used
in the GPG key of the repository is automatically copied into the spec
(like e.g. changelog or revision).
Is this possible (thought that would not fix the hardcoding error
message) or can the name+email be added in the build command directly?
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
I tried to compile the fox1.4 package for ubuntu
and wanted to add the sources directly from the debian
server http://packages.debian.org/etch/libfox1.4
Unfortunately when adding the files by URL to my
obs package (like
http://ftp.de.debian.org/debian/pool/main/f/fox1.4/fox1.4_1.4.34.orig.tar.gz)
something went wrong, because the build process fails:
dpkg-source: error: file fox1.4_1.4.34.orig.tar.gz has md5sum
724e66b89b5451d5032165e03ff5228d instead of expected
3424b9d3f9b71e1f53e9c3822de3b76c
I checked this by downloading the file once from the debian site
and once from the obs and they have different checksums indeed.
The sizes are the same thus it is probably not a matter of
automatic gz extraction.
The diff.gz of the same package has the same problem, that's why I think
there might be something wrong with the remote upload.
Has anyone else encountered this problem?
Is there a known workaround besides down-/uploading?
Regards,
Michael
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello All-
The problem can be illustrated by trying this out:
osc co openSUSE:Factory attr
cd openSUSE:Factory/attr
quilt setup attr.spec
cd attr-2.4.39/
./configure
make
strace getfattr/getfattr /
Here is a snip from that strace:
open("/home/philips/projects/openSUSE/x86_64/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/home/philips/projects/openSUSE/x86_64", 0x7ffffec11540) = -1 ENOENT (No such file or directory)
open("/home/philips/projects/openSUSE/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/home/philips/projects/openSUSE", 0x7ffffec11540) = -1 ENOENT (No such file or directory)
open("Factory/attr/attr-2.4.39/libattr/.libs/tls/x86_64/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
open("Factory/attr/attr-2.4.39/libattr/.libs/tls/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
open("Factory/attr/attr-2.4.39/libattr/.libs/x86_64/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
Not ideal! The process is trying to load obviously non-existent
libraries. This is because libtool creates a wrapper for getfattr so it
will be executed using local libraries built in the source tree instead
of the system libraries:
# Add our own library path to LD_LIBRARY_PATH
LD_LIBRARY_PATH="/home/philips/projects/openSUSE:Factory/attr/attr-2.4.39/libattr/.libs:$LD_LIBRARY_PATH"
But it is breaking because LD_LIBRARY_PATH uses colon characters as a
separator like PATH...
I talked to the libtool maintainer about this and he said:
On 07:37 Thu 18 Dec 2008, Ralf Wildenhues wrote:
> > I have found that libtool generates temporary wrappers with improperly
> > escaped LD_LIBRARY_PATH. If the current directory path contains a colon.
> > For example /home/philips/test:directory/attr-2.4.43/
>
> Where is it documented that LD_LIBRARY_PATH is interpreted as with
> backslash escaping for colons in the names? I've never heard of that
> before.
>
> The ld.so(1) man page on my Debian testing system documents that
> LD_LIBRARY_PATH is interpreted similarly to PATH. I confirmed now that
> PATH uses this kind of colon escaping, surprisingly. I cannot find it
> documented anywhere though, certainly not in the Posix pages (but hey,
> I overlooked things before).
>
> We can think about supporting it when and where this is suitably safe to
> do so, but my gut reaction would be "don't do it when it hurts".
Ralf's first point is correct. ld doesn't accept \: as a literal colon
like PATH does. So, we will need to fix this first.
_ OR _
Instead of taking on the pain of fixing ld and all of the tools and
scripts to generate and understand slash escaped colon characters we
could stop using colon as a separator in build service project names.
Upstream maintainers are not going to be excited about fixing the colon
character problem up because the build service is probably the only
thing using it.
So, can we please use another separator? Perhaps the dash "-". This
character is well accepted and works across http/dns/sh/etc without
escaping or special consideration.
Doing nothing about this isn't an option. Many packages use this trick
to test programs as they sit in the source tree without doing a `make
install`. If we do nothing developers who are new to OBS and unaware of
the issue will waste time, as I did, trying to figure out why their
library fixes aren't working.
Thoughts?
Thanks,
Brandon
P.S. I first filed a bug against libtool here:
https://bugzilla.novell.com/show_bug.cgi?id=460044
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
The almost last gift in this year :)
we updated the tar ball of the openSUSE Build Service and the rpm packages in
openSUSE:Tools project.
Changes since 1.5 Beta 1 release are fixes for product and image creation.
Local image build support works now together with latest versions of the
build.rpm and osc.
Documentation writing for the product creation has been started on the concept
wiki page:
http://en.opensuse.org/Build_Service/Concepts/Product_Definition
tar ball is downloadable at Novell Forge:
http://forge.novell.com/modules/xfcontent/downloads.php/opensuse/1.5
Rpm packages can be download and installed easily via
http://software.opensuse.org/search?baseproject=openSUSE:Tools&q=obs
Please read the README.SETUP or README.UPDATE file to finish the install.
Susanne branched also the 1.5 tree last week in svn. This means development in
trunk is open again, but important fixes should get backported. Please drop me
a mail in addition, if you think they are important for the 1.5 Final release
in January next year.
happy new year
Your Build Service Team
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
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
Hello everybody,
Was there a change on the iChain setup? Recently (maybe for about one
week or so..) I am logged out very frequently from the OBS and Bugzilla
tracker... whereas before I could basically log in once in the morning I
have now to log in approx every hour, or maybe two hours (not using it
on a minute basis and I did not measure.. but I have to login almost
everytime I want to do something).
Dominique
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all!
I have a modified version of obs (r5507) working with kiwi imaging inside obs.
Today I updated to svn trunk. Now i see these errors:
- imaging (kiwi-image)
expansion errors:
nothing provides kiwi-filesystem:ext2
nothing provides kiwi-packagemanager:zypper
IIRC _no_ packages provide this dependencies and this is _not_ transparent for
imaging of different distros. Whats the plan here ?
Could someone please also give some feedback on:
http://en.opensuse.org/Build_Service/Concepts/CrossDevelopment/Preinclude
Best regards,
Jan-Simon
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Brandon Philips wrote:
> Of course we need to figure out how many people have dots in their
> usernames but that could be worked around somehow.
Usernames are not a problem in this case, but we have a lots of projects
that contain dot (with a good reason) like openSUSE:11.0 or
Java:jpackage-5.0
--
Best Regards / S pozdravom,
Pavol RUSNAK SUSE LINUX, s.r.o
Package Maintainer Lihovarska 1060/12
PGP 0xA6917144 19000 Praha 9, CR
prusnak[at]suse.cz http://www.suse.cz
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Good day!
Yesterday I sent some messages on IRC talking about an error on "rake
db:migrate" on 1.5rc1 packages. Solved that with some changes on
"043_add_archs.rb" and "013_add_archs.rb" files under
"/srv/www/obs/frontend/db/migrate/". Did someone of the admins saw the
messages?
It's not possible to "rake db:migrate" of webclient too, but I didn't
tried to figure It out.
The next point is the step 4.1 in
"/usr/share/doc/packages/obs-api/README.SETUP". Followed the
instructions to add openSUSE:11.1 project hosted at the openSuSE
BuildService but It failed with the folllowing message:
"Errorcode: 404
Message: repoid 'openSUSE.org:openSUSE:11.1' is illegal"
Looking inside "openSUSE.org.xml" file there is a reference to
"https://api.opensuse.org/public" which seems doesn't exist. Am I
missing some step?
There's a lot of bugs to call it an RC, isn't?
Thanks.
--
[ ]'s
Aledr - Alexandre
"OpenSource Solutions for SmallBusiness Problems"
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
just curious: Why does't "osc build" use the download.o.o packages for
11.1? For Factory it's clear, but for 11.1?
------------- 8< ------------------------
Trying upstream server for gdb (openSUSE:11.1), since it is not on download.opensuse.org.
(openSUSE:11.1) gdb-6.8.50.20081120-2.1. 100% |====================| 2.1 MB 00:00
------------- >8 -------------------------
Bernhard
--
Bernhard Walle, SUSE Linux Products GmbH, Architecture Development
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
How soon will openSUSE:10.2 standard be completely removed from OBS? It
seems that I have to mirror the project to my local_obs if I need opensuse
10.2.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org