Re: [Evergreen] Repositories and architectures
* Sebastian Niemeyer [01-12-16 18:01]: > Hi! > > Okay, will you inform us if the official updates ends and evergreen takes > over? > > Sebastian > > On Tuesday 29 December 2015 00:21:35 Wolfgang Rosenauer wrote: > > Hi, > > > > Am 28.12.2015 um 18:34 schrieb Ashley Anderson: > > > Hello all, and thank you tremendously for your contributions to the > > > Suse/OpenSuse projects. I have been watching the email list for about 6 > > > months now. January 2016 is just days away, and I have not heard or > > > found any updates to OpenSuse 13.1 going evergreen. I have 2 OS 13.1 > > > vms used in our production systems. I am looking for info on what is > > > needed in order to move them to an evergreen configuration. If I am > > > emailing the wrong group, my sincerest apologies. Any info would be > > > greatly appreciated. Thanks in advanced, and Happy New Years all! > > > > the plan is: You do not have to do anything. > > At some point the official updates will end and the Evergreen updates > > will arrive using the same channel. This is different to the past. > > > > > > Wolfgang > > > > ___ > > Evergreen mailing list > > Evergreen@lists.rosenauer.org > > http://lists.rosenauer.org/mailman/listinfo/evergreen > > ___ > Evergreen mailing list > Evergreen@lists.rosenauer.org > http://lists.rosenauer.org/mailman/listinfo/evergreen I believe that normally occurs on the opensuse list. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://linuxcounter.net ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Repositories and architectures
Hi! Okay, will you inform us if the official updates ends and evergreen takes over? Sebastian On Tuesday 29 December 2015 00:21:35 Wolfgang Rosenauer wrote: > Hi, > > Am 28.12.2015 um 18:34 schrieb Ashley Anderson: > > Hello all, and thank you tremendously for your contributions to the > > Suse/OpenSuse projects. I have been watching the email list for about 6 > > months now. January 2016 is just days away, and I have not heard or > > found any updates to OpenSuse 13.1 going evergreen. I have 2 OS 13.1 > > vms used in our production systems. I am looking for info on what is > > needed in order to move them to an evergreen configuration. If I am > > emailing the wrong group, my sincerest apologies. Any info would be > > greatly appreciated. Thanks in advanced, and Happy New Years all! > > the plan is: You do not have to do anything. > At some point the official updates will end and the Evergreen updates > will arrive using the same channel. This is different to the past. > > > Wolfgang > > ___ > Evergreen mailing list > Evergreen@lists.rosenauer.org > http://lists.rosenauer.org/mailman/listinfo/evergreen ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Repositories and architectures
Hi, Am 28.12.2015 um 18:34 schrieb Ashley Anderson: > Hello all, and thank you tremendously for your contributions to the > Suse/OpenSuse projects. I have been watching the email list for about 6 > months now. January 2016 is just days away, and I have not heard or > found any updates to OpenSuse 13.1 going evergreen. I have 2 OS 13.1 > vms used in our production systems. I am looking for info on what is > needed in order to move them to an evergreen configuration. If I am > emailing the wrong group, my sincerest apologies. Any info would be > greatly appreciated. Thanks in advanced, and Happy New Years all! the plan is: You do not have to do anything. At some point the official updates will end and the Evergreen updates will arrive using the same channel. This is different to the past. Wolfgang ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Repositories and architectures
Hello all, and thank you tremendously for your contributions to the
Suse/OpenSuse projects. I have been watching the email list for about 6
months now. January 2016 is just days away, and I have not heard or found
any updates to OpenSuse 13.1 going evergreen. I have 2 OS 13.1 vms used in
our production systems. I am looking for info on what is needed in order
to move them to an evergreen configuration. If I am emailing the wrong
group, my sincerest apologies. Any info would be greatly appreciated.
Thanks in advanced, and Happy New Years all!
--
Best Regards,
Ashley Anderson
ashe...@gmail.com
On Sun, Dec 6, 2015 at 4:43 PM, Axel Braun wrote:
> Hi,
>
> we have now seen several proposals, but is there an agreed path forward? I
> have seen some posts in alt.linux.suse which address the same uncertainty,
> as
> some repos seem already to disappear.
>
> Many users need packages from other than the standard repos to keep their
> systems up and running, or to maintain projects.
> So using an rsync-copy is a local workaround, that goes not really in line
> with the OBS approach, esp. in conjunction with SUSEStudio.
>
> An additional build target for Evergreen sounds to me the more pragmatic
> approach
>
> Wolfgang, as the main driver behind Evergreen, what is your opinion?
>
> Cheers
> Axel
>
> Am Dienstag, 24. November 2015, 13:28:21 schrieb Boris Manojlovic:
> > or there is maybe even third option possible, more as convenience than
> real
> > solution,
> > create "special" OBS project openSUSE:evergreen that people could set as
> > buildtarget,
> > i do not know if something like that would be even feasible on OBS.
> > As evergeen is always only one distribution, move from one to other would
> > be atomic (and a bit annoying on move from old to new one as it will
> > generate rebuilds)
> >
> > On Thu, Nov 19, 2015 at 5:25 PM, Bruno Friedmann
> wrote:
> > > On Thursday 19 November 2015 12.20:03 Sebastian M. Ernst wrote:
> > > > Hi all,
> > > >
> > > > I am currently running openSUSE 13.1 x86_64 on a few machines and
> > > > planning to keep it running with Evergreen support. Thanks a lot for
> > > > this excellent project.
> > > >
> > > > When past releases of openSUSE reached their official EOL, I noticed
> > > > that a lot of valuable openSUSE build service repositories for those
> > > > releases went offline pretty quickly without even individual mirrors
> > > > keeping a copy of them. I'd like to avoid running into problems (like
> > > > being unable to find a desired package when needed) this time, so I
> am
> > > > cloning some build service repositories I am frequently using to one
> of
> > > > my machines. This raises two questions for me.
> > > >
> > > > Would it be possible to keep copies of the latest ("final") versions
> of
> > > > the contents of build service repositories for openSUSE 13.1 at
> least on
> > > > one mirror before they disappear at download.opensuse.org?
> > >
> > > it is normally always possible to extract the package at a certain
> level
> > > from obs
> > > to make it revival.
> > > But I don't think the binaries are kept.
> > >
> > > I guess there 2 solutions, keep an rsync copy without --delete
> > > with the consequence of it.
> > >
> > > The others way would be to have a local obs, branch all the package you
> > > need
> > > and build publish them for 13.1.
> > >
> > > Now the third solution, was applied for 11.4 is to have a Evergreen
> target
> > > (or simply keep 13.1 as a build publish target) on repository.
> > >
> > > As this depend of the reposotiry maintainer decision, and also to save
> > > build power of obs Getting your needed package branched inside
> > > your own repo, could help perhap but for how long...
> > >
> > > Owning an obs instance is the most secured in long term.
> > > All depends
> > >
> > > > Using an x86_64 version of openSUSE, do I need to clone the "x86_64"
> > > > *and* the "i586"/"i686" folders of every repository or is sufficient
> to
> > > > just clone / keep copies of the "x86_64" folders? I am not sure
> whether
> > > > packages in "x86_64" folders might have any dependencies to packages
> > > > found in "i586"/"i686" folders.
> > >
> > > You should be able to keep only noarch, x86_64 and repodata folder
> > > no i586 should be necessary, when 32bits are expected normally they
> have a
> > > -32bit
> > > in x86_64 repository.
> > >
> > > But beware some non open crap (skype etc) need i586 lib and bin...
> > > So depending of what you want to run, both could be mandatory.
> > >
> > > > Best regards,
> > > > Sebastian
> > >
> > > Hope this help you to
> > >
> > > --
> > >
> > > Bruno Friedmann
> > > Ioda-Net Sàrl www.ioda-net.ch
> > >
> > > openSUSE Member & Board, fsfe fellowship
> > > GPG KEY : D5C9B751C4653227
> > > irc: tigerfoot
> > >
> > > ___
> > > Evergreen mailing list
> > > Evergreen@lists.rosenauer.org
> > > http://lists.rosenauer.org/mailman/listinfo/evergreen
>
>
Re: [Evergreen] Repositories and architectures
Hi,
we have now seen several proposals, but is there an agreed path forward? I
have seen some posts in alt.linux.suse which address the same uncertainty, as
some repos seem already to disappear.
Many users need packages from other than the standard repos to keep their
systems up and running, or to maintain projects.
So using an rsync-copy is a local workaround, that goes not really in line
with the OBS approach, esp. in conjunction with SUSEStudio.
An additional build target for Evergreen sounds to me the more pragmatic
approach
Wolfgang, as the main driver behind Evergreen, what is your opinion?
Cheers
Axel
Am Dienstag, 24. November 2015, 13:28:21 schrieb Boris Manojlovic:
> or there is maybe even third option possible, more as convenience than real
> solution,
> create "special" OBS project openSUSE:evergreen that people could set as
> buildtarget,
> i do not know if something like that would be even feasible on OBS.
> As evergeen is always only one distribution, move from one to other would
> be atomic (and a bit annoying on move from old to new one as it will
> generate rebuilds)
>
> On Thu, Nov 19, 2015 at 5:25 PM, Bruno Friedmann wrote:
> > On Thursday 19 November 2015 12.20:03 Sebastian M. Ernst wrote:
> > > Hi all,
> > >
> > > I am currently running openSUSE 13.1 x86_64 on a few machines and
> > > planning to keep it running with Evergreen support. Thanks a lot for
> > > this excellent project.
> > >
> > > When past releases of openSUSE reached their official EOL, I noticed
> > > that a lot of valuable openSUSE build service repositories for those
> > > releases went offline pretty quickly without even individual mirrors
> > > keeping a copy of them. I'd like to avoid running into problems (like
> > > being unable to find a desired package when needed) this time, so I am
> > > cloning some build service repositories I am frequently using to one of
> > > my machines. This raises two questions for me.
> > >
> > > Would it be possible to keep copies of the latest ("final") versions of
> > > the contents of build service repositories for openSUSE 13.1 at least on
> > > one mirror before they disappear at download.opensuse.org?
> >
> > it is normally always possible to extract the package at a certain level
> > from obs
> > to make it revival.
> > But I don't think the binaries are kept.
> >
> > I guess there 2 solutions, keep an rsync copy without --delete
> > with the consequence of it.
> >
> > The others way would be to have a local obs, branch all the package you
> > need
> > and build publish them for 13.1.
> >
> > Now the third solution, was applied for 11.4 is to have a Evergreen target
> > (or simply keep 13.1 as a build publish target) on repository.
> >
> > As this depend of the reposotiry maintainer decision, and also to save
> > build power of obs Getting your needed package branched inside
> > your own repo, could help perhap but for how long...
> >
> > Owning an obs instance is the most secured in long term.
> > All depends
> >
> > > Using an x86_64 version of openSUSE, do I need to clone the "x86_64"
> > > *and* the "i586"/"i686" folders of every repository or is sufficient to
> > > just clone / keep copies of the "x86_64" folders? I am not sure whether
> > > packages in "x86_64" folders might have any dependencies to packages
> > > found in "i586"/"i686" folders.
> >
> > You should be able to keep only noarch, x86_64 and repodata folder
> > no i586 should be necessary, when 32bits are expected normally they have a
> > -32bit
> > in x86_64 repository.
> >
> > But beware some non open crap (skype etc) need i586 lib and bin...
> > So depending of what you want to run, both could be mandatory.
> >
> > > Best regards,
> > > Sebastian
> >
> > Hope this help you to
> >
> > --
> >
> > Bruno Friedmann
> > Ioda-Net Sàrl www.ioda-net.ch
> >
> > openSUSE Member & Board, fsfe fellowship
> > GPG KEY : D5C9B751C4653227
> > irc: tigerfoot
> >
> > ___
> > Evergreen mailing list
> > Evergreen@lists.rosenauer.org
> > http://lists.rosenauer.org/mailman/listinfo/evergreen
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
