[sles-beta] php disappeared in beta6?

Thu May 15 05:25:15 MDT 2014

Hello Matthias,

I understand the approach to get possibilities to have 10zears of
support and also to be able to migrate to newer versions of software so
to have more flexibility.

As of our way we deliver software to the customers, we have the absolute
need to have installation medias keeping the whole process offline. So
from what I understand, I can get packages via SMT to be installed on a
SLES connected to the SMT. Will there be any kind of Addon Medias, Will
there be a way to include software packages in a default installation
without playing disc jockey? How will the patch/update process be done?
One offline Iso per channel?

I will not talk about any upgrade from SLES11 to SLES12 issues, which
will only be possible with a internet (or at least SMT) enabled server?

What, if the customer is located somewhere "close to nowhere", without
SMT and without propper internet?

Again, this issue came up WITHOUT any message before it was detected by
the BETA testers. What was the original plan of SUSE to make an official
announcement of these changes (as with KDE)?

Please give me answers to my concerns!

Rgds
Klaus

Am 15.05.2014 13:06, schrieb Matthias G. Eckermann:
> Hello all,
>
> On 2014-05-15 T 10:17 +0000 urs.frey at post.ch wrote:
>
>> YES I am behind an SMT, the only allowed contact
>> to NCC and possible repository sources so far.  So
>> when modules are only available online and SMT on
>> SLES11-SP3 can't see them, there is no test
>> possibility.  SMT for SLE-12 shall be ready
>> someday after release of SLES12 and there is also
>> a change from NCC to SCC.  I wonder how all this
>> will work
>
> SMT 11 SP3 will (get an update) and be able to mirror
> SUSE Linux Enterprise 12 related repositories, and
> yes, this certainly includes the Modules.
>
> In other words: if you have a way to work with
> maintenance updates provided by SUSE in a structured
> way, you will also be able to work with Modules.
>
> Others already sent more details on the benefits of
> Modules for keeping SLES "fresh" and attractive.
>
> HTH -
>       MgE
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Pieter Hollants
>> Gesendet: Thursday, May 15, 2014 11:47 AM
>> An: Matthias G. Eckermann; Beddingfield, Allen; sles-beta at lists.suse.com; tee at sgi.com
>> Betreff: Re: [sles-beta] php disappeared in beta6?
>>
>> There are environments that do not have online access for security reasons. So whatever the module concept is exactly, be sure it works with addon ISOs, too.
>>
>> -----Ursprüngliche Nachricht-----
>> Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Matthias G. Eckermann
>> Gesendet: Mittwoch, 14. Mai 2014 23:14
>> An: Beddingfield, Allen; sles-beta at lists.suse.com; tee at sgi.com
>> Betreff: Re: [sles-beta] php disappeared in beta6?
>>
>> On 2014-05-14 T 15:55 +0000 Beddingfield, Allen wrote:
>>
>>> I can confirm this as an issue, too.  We definitely require that PHP
>>> be included, since we are hosting our web infrastructure on SLES.
>>
>> PHP is not on the "ISO" anymore, but in a "module", which is only delivered online.
>>
>> To get PHP, please register your system during installation and chose the "Web & Scripting" module.
>>
>> More on the "Modules" concept I will explain in one of the next beta calls.
>>
>> so long -
>>      MgE
>>
>>> From: sles-beta-bounces at lists.suse.com
>>> [sles-beta-bounces at lists.suse.com] on behalf of Tony Ernst
>>> [tee at sgi.com]
>>> Sent: Wednesday, May 14, 2014 10:35 AM
>>> To: sles-beta at lists.suse.com
>>> Subject: [sles-beta] php disappeared in beta6?
>>>
>>> Sles12 beta5 had php (php5) rpms. They seem to have disappeared in beta6.
>>> Was that intentional? Oddly enough, the php5-devel and the pcp .src
>>> rpm are still in the beta6 SDK.
>>
>> --
>> Matthias G. Eckermann     Senior Product Manager   SUSE® Linux Enterprise
>> Phone: +49 30 44315731    Mobile: +49 179 2949448    E-Mail: mge at suse.com
>> SUSE LINUX Products GmbH  Maxfeldstraße 5          90409 Nürnberg Germany
>> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________
>> sles-beta mailing list
>> sles-beta at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/sles-beta
>>
>> DFS Deutsche Flugsicherung GmbH
>> Am DFS-Campus
>> D - 63225 Langen
>>
>> Tel.: +49-(0)6103-707-0
>>
>> Sitz der Gesellschaft: Langen/Hessen
>> Zuständiges Registergericht: AG Offenbach am Main, HRB 34977
>> Vorsitzender des Aufsichtsrates: Michael Odenwald
>> Geschäftsführer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann
>>
>> Internet: http://www.dfs.de
>> Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <http://www.dfs.de/dfs/public_key.asc>
>> _______________________________________________
>> sles-beta mailing list
>> sles-beta at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/sles-beta
>

--
Klaus Gmeinwieser
T +49 (0)8121 72 4358 F +49 (0)8121 72 3173
E klaus.gmeinwieser at oce.com W www.oce.com

Océ Printing Systems GmbH & Co. KG • A Canon Group Company
P.O. Box 1260 • 85581 Poing
Siemensallee 2 • 85586 Poing • Germany

Océ enables its customers to manage their documents efficiently and
effectively by offering
innovative print and document management products and services for
professional
environments.

Océ Printing Systems GmbH & Co. KG
The company is a limited partnership with its registered office in Poing
– Trade Register HRA 100955 (Amtsgericht München) – WEEE-Reg.-No. DE 888
05 443

General Partner: Océ Printing Systems Geschäftsführungsgesellschaft mbH
Registered Office: Poing – Trade Register HRB 206480 (Amtsgericht München)
Executive Officer: André Mittelsteiner
This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation.