See https://build.opensuse.org/package/files?package=lightspark&project=home%3A…
The _service:format_spec_file:lightspark.spec file uses
CMAKE_SKIP_RPATH instead of the CMAKE_BUILD_WITH_INSTALL_RPATH from
the original .spec file. It's from an old revision and I have no idea
why it appeared there when I added the "<topadd>%define _with_ffmpeg
1</topadd>" line to the _link file. If you check the date you can see
the _service file is older than the original .spec file!!
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Marcus was kind enough to add a wine-devel-32bit subpackage that is
now available in Factory. Because of this now my lmms x86-64 build has
VST support. To support it also in 12.1 I linked the wine package from
the devel project to my home repo. I even added the "ExportFilter:
^wine.*\.i586.rpm$ . x86_64" line to my prjconf, even if I guess it is
inherited from the openSUSE:12.1 prjconf. But home:RedDwarf/lmms in
openSUSE_12.1/x86_64 is still in the unresolvable state because it
can't find wine-devel-32bit.
So... what I'm doing wrong?
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
How can a package in Fedora 16 x86_64 build 32bit binaries?
In the various SuSE repos it can be done with BuildRequires:
glibc-devel-32bit. I tried BuildRequires: glibc-devel.i686, but that
does not seem to work. Installing the i686 variants of glibc,
glibc-devel and nss-softokn-freebl manually into a local x86_64 build
chroot and using osc build --no-init fixes the compile errors for me.
The project where I would like to use this feature is
home:olh:testing-xen-unstable
Olaf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
Just a little warning - I merged my rails 3.2 port into master,
creating some problems aside that you should be aware of if you
want to play with master:
- hidden projects are visible for generic cases, most routes use
check_access? though, which still works.
- api has no more user/group/role management web page. Of course you
can still create users using the console
- exception_notifier is patched out right now
- we require specific versions of all gems now. All versions needed
will be in openSUSE:Tools:Unstable - but you're free to use them
from rubyforge if you prefer. But bundle will make sure you have
them in the same version.
- we require mysql2 driver instead of mysql as OBS 2.3 - this is also
the rails recommended driver and it has much better performance. You
need to adapt your config/database.yml
- your environment.rb will need to be patched
For the later I also changed the way these development.$HOMENAME.rb
files work. In the past they were a full copy of development.rb, which
required to add all defaults there too.
Now you can overwrite all config options or CONFIG elements in a
development.$HOMENAME.rb file, but you can just leave it all out.
For reference, my file looks like this:
> CONFIG['source_host'] = "localhost"
> CONFIG['source_port'] = 5352
>
> OBSApi::Application.configure do
> config.cache_store = :memory_store
> end
The webui is still rails 2.3, but this will change soonish, fortunately
rails-3_2 and rails-2_3 are co-installable. But you need to be aware
that "rails" will most likely be 2.3, so you use rails-3_2 for stuff.
Ah, btw: rails 3 no longer has a ./script/console or a ./script/server.
This is all done by rails-3_2 now, so use e.g. "rails-3_2 server -e test"
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello All,
I'm curious to know if there's a preferred method for pushing
features/patches to packages upstream in the distribution. I created a
feature/bug request in bugzilla to which the response was basically
"patches are welcome". So I patched and tested this feature to the
app and posted the patches to the bugzilla ticket and nothing, no
response or followups. That's fine, i know people are busy and my
request may not be of much importance to others, but I do feel this
feature is valuable and it's availability will be a dependency on
another packaging modification request I plan on creating.
At this point would I be better served by branching the package in
OBS, applying my patches, and creating an SR or just wait for the
things to work there way through bugzilla? While I'd like to see this
pushed out to all supported distro releases I realize this may not be
an option, but with the 12.2 RC around the corner I'd be happy with it
making that release.
Thanks!
--
Later,
Darin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
please, what is the disk size limit of the virtual hosts in the Build
Service?
LibreOffice-3.4 build failed with the following error message:
--- cut ---
Using BUILD_ROOT=/var/cache/obs/worker/root_10/.mount
Using BUILD_ARCH=x86_64:i686:i586:i486:i386
Doing kvm build in /var/cache/obs/worker/root_10/root
build30 started "build libreoffice.spec" at Thu Mar 29 16:08:18 UTC 2012.
Building libreoffice for project 'LibreOffice:Unstable' repository 'openSUSE_12.1' arch 'x86_64' srcmd5 '8d3c3d8ce83f060f391c6862dc285cf1'
[...]
Unable to write payload
to /home/abuild/rpmbuild/RPMS/x86_64/libreoffice-debuginfo-3.5.2.2-102.1.x86_64.rpm:
[51477.804792] SysRq : Power Off
[51479.576116] Power down.
--- cut ---
It succeeded on 11.2-i586. I guess that it is because the binaries and
debuginfo packages a smaller there. Thus I think that I need to be very
close to the disk size limit.
I am going to remove debuginfo as temporary solution. I will also check
if anything crazy happens during build, e.g. too detailed logs. I wonder
what limit I need to reach ;-)
Best Regards,
Petr
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
exim used to build for RedHat_RHEL-6 in the past. Now we get by
calling:
server:mail/exim> osc build RedHat_RHEL-6 x86_64 exim.spec
...
buildinfo is broken... it says:
unresolvable: nothing provides xorg-x11-server-sdk
The same üackage sources used to built in the past.
Cheers,
Lars
--
Lars Müller [ˈlaː(r)z ˈmʏlɐ]
Samba Team
SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Hello OBS developers,
The "download" page for my packages hasn't data anymore, even when I
explicitly enable the publish flag for all repositories. Please could
you help me to understand what I did wrong?
Example: http://software.opensuse.org/download/package?project=home:cedric-vincent&p…https://build.opensuse.org/package/show?package=PRoot&project=home%3Acedric…
Thanks in advance,
Cédric.
PS: Congratulation and many thanks for this great build framework!
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
On Wed, Mar 28, 2012 at 10:45:34PM +0200, OBS osc wrote:
> From: Marcus Huewe <suse-tux(a)gmx.de>
>
> The way for determining the revision was completely "wrong".
> [...]
> - rev = show_upstream_xsrcmd5(p.apiurl, p.prjname, p.name, revision=p.rev, linkrev='base')
> - p.mark_frozen()
> - else:
> - p.update(rev, opts.server_side_source_service_files, opts.limit_size)
> - rev = p.linkinfo.xsrcmd5
> + rev = p.latest_rev(expand=True)
> print 'Expanding to rev', rev
> elif opts.unexpand_link and p.islink() and p.isexpanded():
> - p.update(rev, opts.server_side_source_service_files, opts.limit_size)
> - # XXX: calling update again is redundant (see below)
> - rev = p.rev
> + rev = show_upstream_rev(p.apiurl, p.prjname, p.name, meta=p.meta)
> print 'Unexpanding to rev', rev
That can't work if you didn't check out the latest version, but some
older rev.
Really, you can check out an expanded link (by supplying the xsrcmd5)
and then it should be possible to switch to the unexpanded view.
That's what the linkrev's lsrcmd5 is for. If you're not using it
you're doing somethink wrong ;)
Cheers,
Michael.
--
Michael Schroeder mls(a)suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org