Mailinglist Archive: opensuse (882 mails)

< Previous Next >
Re: [opensuse] Blackberry phone backup
  • From: "Brian K. White" <brian@xxxxxxxxx>
  • Date: Fri, 17 Dec 2010 14:28:49 -0500
  • Message-id: <4D0BB9F1.9000108@xxxxxxxxx>
On 12/17/2010 3:02 AM, Peter Nikolic wrote:
On Friday 17 Dec 2010 06:52:51 Bin Li wrote:
Peter,

What's the packages' name? Where can I find it? Thanks a lot!


On Tue, Dec 14, 2010 at 9:42 AM, Peter Nikolic

<p.nikolic1@xxxxxxxxxxxxxx> wrote:
Hi ..

If anyone is interested i have built the barry package for blackberry
phones on opensuse 11.3 x86_64 it is 5 rpm's right now but works ..

Pete .

--
Powered by openSUSE 11.3 (x86_64) Kernel: 2.6.34.7-0.5-desktop
KDE Development Platform: 4.4.4 (KDE 4.4.4) "release 3"
01:40 up 5 days 9:23, 6 users, load average: 0.97, 0.91, 1.50
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Hi ..

At the moment i nave nowhere to host it this may be sorted monday evening
watch this space ..

Cheers Pete .


Just put it in the build service. It builds the rpms and hosts the compiled rpms and srpms for download and will do so for all current versions of opensuse and all platforms for each version. All free.

The hard part was working out the .spec files which you've now done, so the remaining steps to put that in the build service is very little.

10 minute howto:
Register and log in here:
https://build.opensuse.org/

There are a few one-time-only steps that I can't describe exactly because I've already done them but basically it's just filling in a name & description for your default home project. This isn't "barry" btw. A project may have any number of packages in it. You can create a sub-project called barry if you want and put all the barry packages in there but it's not necessary. You can just put the barry packages directly in your home project.

Get all the source files and .spec from a source rpm onto your pc so that you can upload them via web browser later.

Go to "My Projects"
home:pnikolic

Repositories (it's a tab on top, you start off in the Overview tab):
Add repositories
Select the main opensuse ones and the suse ones if you want. any others and it may get complicated getting them to work.
Back at the Repositories view, under Repository Flags, ensure the top-left cell of build, use-for-build, and publish tables is a gear with a green checkmark. Click the cell to toggle through the enable/disable options if they're not all enabled already by default.


Packages:
Add a new package
Fill in name & description (same as in the .spec)
Save
It will then jump you to that package

Source files:
Add file
Local file: choose file,
select one of the source files from the srpm
Leave the other twoe fields empty
Save changes
The file uploads to the build service and appears in the source files list.

Repeat the Add file/upload uploading all source files and the .spec for that package.
By "all source files" I mean just what's referenced in the .spec
Usually this is a .tar.bz2 containing the main app source, and a few patches or other related files. And the .spec itself you also upload the same way.

At that point the build service will schedule the package to be built.
Now you just wait and check the build status once in a while.
Depending on how busy the build servers are it can take a while for the packages to get built and for the results to get published to the download servers. Usually it all happens within 15 minutes.

The only difficulty is that the build service is a slightly different environment than running rpmbuild on a regular server, and it's a little stricter about certain things so the package may fail to build in the build service, and you have to do a little work resolving whatever the error was. Usually it's pretty easy to make the suggested adjustment if you have a package that does build on a regular server as a starting point.

--
bkw
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >