openSUSE Web November 2015

web@lists.opensuse.org

3 participants
2 discussions

[opensuse-web] Re: [Evergreen] Repositories and architectures
by Bruno Friedmann 19 Nov '15

19 Nov '15

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 -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

1 0

[opensuse-web] New layout for software.opensuse.org
by Ancor Gonzalez Sosa 12 Nov '15

12 Nov '15

Since the leap to Leap (I couldn't resist), the frontpage of software.opensuse.org looked a bit misleading: - With only 2 ISOs to download, the javascript based accordion was simply too much. - The "alternative versions" section was also quite a non-sense - two Javascript-powered links just to end up in a link to the wiki. - References to the "type of computer" or mentioning 32 bits in the help text didn't help much either So, as you can see, I redid the layout a little bit https://software.opensuse.org/421 For old versions, the old layout is still used https://software.opensuse.org/132/ I kept the changes to a minimal with the intention of not adding or changing any string in order not to break translations. But I think it's time to go one step further. I think we need a new layout with: - Rephrased/updated text for several sections. Like this https://bugzilla.suse.com/show_bug.cgi?id=953927 - A clear indication that the official images are 64 bits only - Reasonably prominent links (with the corresponding short explanations) to the unofficial ports[1] and to the derivatives. https://github.com/openSUSE/software-o-o/issues/39 - A layout that works better in languages with long strings. For example, the current layout looks slightly broken in Spanish. I'm not talking about a visual redesign (I know some people is already trying to tweak the CSS to make it more consistent with the landing page). I'm talking about rearranging the elements and phrasing everything in a better way, so we are more consistent with the current reality. Contributions are welcome as pull requests, but also as text snippets, mock-ups, sketches or simply lists of things to take into account. Thanks. [1] Maintained unofficial ports are aarc64 and ppc64le at the moment, maybe 32bit in the future is somebody steps up. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

openSUSE Web November 2015