Hello,
I just noticed that on the systems I have marked as disabled I have files
called ...rpm. They are 4 or 5 versions back. How do I get them removed?
Thanks,
--
Boyd Gerber <gerberb(a)zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
I had errors about not using mkdir -p from rpmlint. Now I get in Package
python-postfix-policyd-spf (Project home:gerberb)
...
+ cd /usr/src/packages/BUILD
+ cd pypolicyd-spf-0.7.1
+ mkdir /var/tmp/python-policyd-spf-0.7.1-15.1-build/usr
+ mkdir /var/tmp/python-policyd-spf-0.7.1-15.1-build/usr/lib
+ mkdir /var/tmp/python-policyd-spf-0.7.1-15.1-build/usr/lib/policyd-spf
+ mkdir
/var/tmp/python-policyd-spf-0.7.1-15.1-build/var/lib/policyd-spf/config
mkdir: cannot create directory
`/var/tmp/python-policyd-spf-0.7.1-15.1-build/var/lib/policyd-spf/config':
No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.66337 (%install)
what can I do?
Thanks for any ideas.
--
Boyd Gerber <gerberb(a)zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I'm currently helping the ACE developers (C++ communication framework plus
an ORB based on it, see http://www.cs.wustl.edu/~schmidt/ACE.html for
details) to use the OBS as their primary source for installable packages
(primarily getting the spec in shape for SuSE/Novell). In the end they
intend to build packages for every distribution that the OBS supports, thus
integrate the work of various packaging teams.
The work is currently done in home:jwillemsen but when things are working,
we would like to move it to a more pominent place and thus I'd like to
create the toplevel project ACE.
Philipp
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I'm using the KDE4.1 from KDE:KDE4:Factory:Desktop - but some
packages (for example kmail) from this repo doesn't have a debuginfo
package. And because kmail is much less stable, than kmail from KDE3,
I'd like to fill out some bug reports to developers.
Somebody knows, where's the problem?
Regards
MV
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I'm using the KDE4.1 from KDE:KDE4:Factory:Desktop - but some of
packages (for example kmail) doesn't have a debuginfo package. And
because kmail seems to be less stable, than kmail from KDE3, I'd like to
fill out some bug reports to developer.
Somebody knows, where's the problem?
Regards
MV
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Alexey Eremenko wrote:
> Michal Marek wrote:
>> Alexey Eremenko napsal(a):
>> > Now I'm thinking of way to build _big_ repository, which will contain
>> > lots of packages that openSUSE Factory lacks.
> ...
>> > I have few possible ideas here:
>> > 1. Convince community to integrate stable third-party packages into
>> > openSUSE Factory
>> > 2. Convince community to make a big, united third-party repository
>> > 3. Build third-party repo myself in openSUSE build service
>> > 4. Build third-party repo myself in private server
>> >
>> > I really believe that #1 is best idea, but due to opposition I don't know.
>> > Perhaps I will need to evaluate other options.
>> What about going for #2 initially and gradually integrating packages
>> matching certain criteria (popularity, maintainability, etc) into Factory?
>
> I agree with #2, but this means we will need to setup
> "factory-candidate-packages" repository/Build service project.
>
> I need permission, so this will allow me to start moving packages into there.
Ask for permission on the buildservice list (again :)).
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
My main reason to get the PPC build service running is KDE4.1. But for
the past couple of days, I get an error, when I try to install it on
x86, which is a kind of discouraging to start the compiles:
bigone:~ # cat conflicts.txt
#### YaST2 conflicts list - generated 2008-08-11 10:15:14 ####
nothing provides kdebase4-workspace = 4.1.60 needed by
kdebase4-session-4.1.60-17.6.i586
[ ] do not install kdebase4-session-4.1.60-17.6.i586
#### YaST2 conflicts list END ###
Bye,
CzP
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
present: abauer, rlihm, tpatzig, lrupp, mrueckert, poeml, adrian
* Status meeting
* Internal Build Service Roadmap adjustment
* Product Definition API
Status:
=======
abauer:
* worked on hermes to improve messages to be sent.
-> attach diffs support
rlihm:
* Worked on concepts for project monitor pages for improved overview
and filtering.
* prepare OBS survey
-> http://en.opensuse.org/Build_Service/WebClientIdeas
tpatzig:
* Worked on starship, improve filter handling. Can be scripted
to modify rules via api.
lrupp:
* created internal tools for filtering project build results on command line
* created internal tool for greping via log files
-> discussion how to consolidate this.
mrueckert:
* started to work on schemas for product definition.
poeml:
* fixed memleak in apache for download.opensuse.org.
adrian:
* OBS talk on LWE San Francisco.
* small bug fixes and improvements for kiwi in backend code.
* trying to get full ftp tree in OBS, this needs some more packages
successfully built.
Internal Build Service Roadmap adjustment:
==========================================
We are slightly behind our schedule, we plan to finish two weeks later now.
This means to have a system ready to produce products at 15th September.
Product Definition:
===================
AI: adrian copy product definition to opensuse.org wiki
done: http://en.opensuse.org/Build_Service/Concepts/Product_Definition
AI: adrian implement product to kiwi converter and support in backend.
AI: mrueckert submit product definition xml and dtd to svn
AI: poeml evaluate if bs_worker is reusable in osc to allow local building
Later: AI: mls introduce versioning for product definition handling (prjconf,
pattern and meta files)
AI: mls allow submission request for this kind of data
-------------------------------------------------------
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
Piotr Pokora ha scritto:
> G. Massera writes:
>
> Hi!
>
>
>>> Maybe I missed some important part of docs, but how one is able to
>>> install debian files with apt-get?
>>> As an example:
>>> http://download.opensuse.org/repositories/home:/midgardproject:/midgard19-d…
>>>
>>>
>>>
>> Very Simple... put the following line inside the apt/sources.list
>> deb
>> http://download.opensuse.org/repositories/home:/midgardproject:/midgard19-d…
>> Debian_Etch/
>>
>
> It doesn't work for i386 when amd64 path is defined in Packages file.
> And doesn't work for amd64 systems when i386 path is defined.
>
> http://ftp5.gwdg.de/pub/opensuse/repositories/home:/midgardproject:/midgard…
>
> There should be Packages file per architecture.
>
> Piotras
>
>
>
>
Yes... you are right.
I've never notice this problem.
I think that the error is in the BuildService, in particulare in the way
the Packages files is created (I suppose using dpkg-scanpackages
command)... and the place where it is stored.
I think that the developers of BuildService should be compliant to the
"Automatic Repository" defined in the following official documentation
for Debian-like distribution:
http://www.debian.org/doc/manuals/repository-howto/repository-howto.en.html
There are, of course, various way to arrange directory, but for me a
good solution can be:
- root repository (
http://download.opensuse.org/repositories/home:/midgardproject:/midgard19-d…
)
|--main
|-- binary-i386
|-- binary-amd64
|-- source
And the Packages files must be created inside each sub-directory of main
(binary-i386, binary-amd64, source) has the official documentaion of
Debian require for apt-repositories.
Ciao,
Gianluca
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi
People who folow MonoOSC story and are interested by this new tool,
can find a first beta release here :
http://download.opensuse.org/repositories/home:/surfzoid/ this
rellease is ready to produce RPM and folow building result, in the
next day i will complete and generate the XML/Chm/Html doc of the
library, from now feedback will be really welcome, thank's.
--
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