I got the RC1 ISOs and the BiArch Add-on ISO, then used rug to add factory as a service, so now I can see where to get Postgres, Tomcat, and all the other goodies I need. What will be the proper way to do this when the final release is out? I understand factory to be bleeding-edge releases that are in a constant state of flux; suppose you download SUSE a few months after release and want to add those packages? Is there a place where they will be available as they were at release time? Don't get me wrong, I'll be buying the commercial release as I have every time since 5.3, but I'm sure the question will come up in our local users group. -- Glenn Holmer (Linux registered user #16682) "I love virtuosity. I love danger." -Pierre Boulez, 2005
Glenn Holmer
I got the RC1 ISOs and the BiArch Add-on ISO, then used rug to add factory as a service, so now I can see where to get Postgres, Tomcat, and all the other goodies I need.
What will be the proper way to do this when the final release is out? I understand factory to be bleeding-edge releases that are in a constant state of flux; suppose you download SUSE a few months after release and want to add those packages? Is there a place where they will be available as they were at release time?
Once The final release is out, I'll basically do on the server: cp -a factory SL-10.1 Note: We will master RC2 and later RCs from the 10.1 tree which until final release will contain exact the same sources - but build separatly... Therefore it's not a cp - but we will make a tree with all those RPMs.
Don't get me wrong, I'll be buying the commercial release as I have every time since 5.3, but I'm sure the question will come up in our local users group.
;-) Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Thu, Apr 13, 2006 at 02:08:59PM +0200, Andreas Jaeger wrote:
Once The final release is out, I'll basically do on the server:
cp -a factory SL-10.1
Note: We will master RC2 and later RCs from the 10.1 tree which until final release will contain exact the same sources - but build separatly... Therefore it's not a cp - but we will make a tree with all those RPMs.
If you could do this at the right time as hardlinks to the factory tree that would be really smart. In that case all mirror servers that have the factory tree could sync without any extra file to transfer saving about 30GB net transfer per mirror server. Suppose Eberhard would agree with me here. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
Hi, On Thu, 13 Apr 2006, Robert Schiele wrote:
On Thu, Apr 13, 2006 at 02:08:59PM +0200, Andreas Jaeger wrote:
Once The final release is out, I'll basically do on the server:
cp -a factory SL-10.1
Note: We will master RC2 and later RCs from the 10.1 tree which until final release will contain exact the same sources - but build separatly... Therefore it's not a cp - but we will make a tree with all those RPMs.
If you could do this at the right time as hardlinks to the factory tree that would be really smart. In that case all mirror servers that have the factory tree could sync without any extra file to transfer saving about 30GB net transfer per mirror server.
Suppose Eberhard would agree with me here.
A good idea, but it would need a reminder shortly before it happens for those who are rsyncing in parts (like me: the main process has factory and each beta/rc excluded, and those parts get synced separately one after the other, with factory splitted further into 3 sequences). Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
Robert Schiele
On Thu, Apr 13, 2006 at 02:08:59PM +0200, Andreas Jaeger wrote:
Once The final release is out, I'll basically do on the server:
cp -a factory SL-10.1
Note: We will master RC2 and later RCs from the 10.1 tree which until final release will contain exact the same sources - but build separatly... Therefore it's not a cp - but we will make a tree with all those RPMs.
If you could do this at the right time as hardlinks to the factory tree that would be really smart. In that case all mirror servers that have the factory
Factory and our 10.1 tree are not hardlinked, they are internally different. So, it's not possible to do this. I tried to persuade our build guys to sync factory and 10.1 so that it would be hardlinks - but then we would need to sync after the release of 10.1 factory completely :-(
tree could sync without any extra file to transfer saving about 30GB net transfer per mirror server.
Suppose Eberhard would agree with me here.
Everybody would - but it does not fit into the way we work, where we have separate 10.1 and "FACTORY" trees - even if those have the same sources, just are build separately, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hello, Andreas Jaeger wrote:
Everybody would - but it does not fit into the way we work, where we have separate 10.1 and "FACTORY" trees - even if those have the same sources, just are build separately,
And where is factory now? Is it already roughly equal to RC1? Will be there another sync before next week? Bye, CzP
Peter Czanik
Hello,
Andreas Jaeger wrote:
Everybody would - but it does not fit into the way we work, where we have separate 10.1 and "FACTORY" trees - even if those have the same sources, just are build separately,
And where is factory now? Is it already roughly equal to RC1? Will be there another sync before next week? Bye,
It is equal to RC1 now - and next sync will happen on monday, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hello, Andreas Jaeger wrote:
And where is factory now? Is it already roughly equal to RC1? Will be there another sync before next week? Bye,
It is equal to RC1 now - and next sync will happen on monday,
Just one more question: the fixes provided for the CDs have larger version numbers, than found in factory. Does it mean, that factory should also be updated with those rpms? Bye, CzP
Peter Czanik
Hello,
Andreas Jaeger wrote:
And where is factory now? Is it already roughly equal to RC1? Will be there another sync before next week? Bye,
It is equal to RC1 now - and next sync will happen on monday,
Just one more question: the fixes provided for the CDs have larger version numbers, than found in factory. Does it mean, that factory should also be updated with those rpms? Bye,
Yes, please! Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Thu, Apr 13, 2006 at 08:45:36PM +0200, Andreas Jaeger wrote:
Robert Schiele
writes: If you could do this at the right time as hardlinks to the factory tree that would be really smart. In that case all mirror servers that have the factory
Factory and our 10.1 tree are not hardlinked, they are internally different. So, it's not possible to do this. I tried to persuade our build guys to sync factory and 10.1 so that it would be hardlinks - but then we would need to sync after the release of 10.1 factory completely :-(
tree could sync without any extra file to transfer saving about 30GB net transfer per mirror server.
Suppose Eberhard would agree with me here.
Everybody would - but it does not fit into the way we work, where we have separate 10.1 and "FACTORY" trees - even if those have the same sources, just are build separately,
You may want to explain what exactly is the reason that you build everything twice from the same sources at all. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
Hello, Robert Schiele wrote:
Everybody would - but it does not fit into the way we work, where we have separate 10.1 and "FACTORY" trees - even if those have the same sources, just are build separately,
You may want to explain what exactly is the reason that you build everything twice from the same sources at all.
I guess, the answer is here: https://bugzilla.novell.com/show_bug.cgi?id=151930#c9 Factory has far more packages, than what goes on the CD/DVD. Bye, CzP
On Thu, Apr 13, 2006 at 10:10:34PM +0200, Peter Czanik wrote:
Robert Schiele wrote:
You may want to explain what exactly is the reason that you build everything twice from the same sources at all.
I guess, the answer is here: https://bugzilla.novell.com/show_bug.cgi?id=151930#c9 Factory has far more packages, than what goes on the CD/DVD. Bye,
Quite unlikely that this is a reason. You don't have to build packages twice just because you don't ship some of them on a specific media set. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
Robert Schiele
You may want to explain what exactly is the reason that you build everything twice from the same sources at all.
At one point of time we will put 10.1 into "maintenance" and only fix bugs there - and add newer packages only to the other tree. So, we have prepared for this one already to be ready at the day we release 10.1, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Fri, Apr 14, 2006 at 07:55:30AM +0200, Andreas Jaeger wrote:
Robert Schiele
writes: You may want to explain what exactly is the reason that you build everything twice from the same sources at all.
At one point of time we will put 10.1 into "maintenance" and only fix bugs there - and add newer packages only to the other tree.
Ah, and this point in time is before the 10.1 final release? Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
Robert Schiele
On Fri, Apr 14, 2006 at 07:55:30AM +0200, Andreas Jaeger wrote:
Robert Schiele
writes: You may want to explain what exactly is the reason that you build everything twice from the same sources at all.
At one point of time we will put 10.1 into "maintenance" and only fix bugs there - and add newer packages only to the other tree.
Ah, and this point in time is before the 10.1 final release?
No - but we have to prepare for it and want to master from that tree... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Mon, Apr 17, 2006 at 11:46:35AM +0200, Andreas Jaeger wrote:
No - but we have to prepare for it and want to master from that tree...
In that case it would be useful if you publicly stated the point in time when factory is at the point that will become the final release. Every mirror admin that likes to do so could then make a frozen copy somewhere which he can use as a base for the final tree at release time. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
participants (5)
-
Andreas Jaeger
-
Eberhard Moenkeberg
-
Glenn Holmer
-
Peter Czanik
-
Robert Schiele