Mailinglist Archive: opensuse-buildservice (262 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] Re: Import build service packages into git
- From: Adrian Schröter <adrian@xxxxxxx>
- Date: Fri, 21 Aug 2009 11:56:25 +0200
- Message-id: <200908211156.25689.adrian@xxxxxxx>
Am Freitag, 21. August 2009 11:22:52 schrieb Andreas Gruenbacher:
An example, you have a package kernel-source in project Kernel:HEAD and in
openSUSE:11.1:Update:SECRET
Kernel:HEAD is public readable, but the openSUSE:11.1:Update:SECRET project
contains a non-public security fix.
The backend should avoid for one to store the data double, so it should share
data between both projects.
But it must not be possible to access to change sets of :SECRET project via
Kernel:HEAD.
Yes, that is also not yet implemented in the current backend. (and source
links, aggregates and repo dependencies are another problem with this).
bye
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
On Friday 21 August 2009 10:18:35 Adrian Schröter wrote:...
Yes, but when you share these objects, can you avoid that some of them do
not become visible ?
Huh? What do you mean?
An example, you have a package kernel-source in project Kernel:HEAD and in
openSUSE:11.1:Update:SECRET
Kernel:HEAD is public readable, but the openSUSE:11.1:Update:SECRET project
contains a non-public security fix.
The backend should avoid for one to store the data double, so it should share
data between both projects.
But it must not be possible to access to change sets of :SECRET project via
Kernel:HEAD.
Yes, that is also not yet implemented in the current backend. (and source
links, aggregates and repo dependencies are another problem with this).
bye
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |