Giter VIP home page Giter VIP logo

get-o-o's Introduction

Get openSUSE

Website promoting the openSUSE distribution development effort, explaining what the distributions do, who they are for and link to useful places to get information about the distributions.

How to build?

bundle install --path vendor/bundle
bundle exec rake
bundle exec jekyll build

Resulting site will be in _site directory.

How to serve locally?

bundle install --path vendor/bundle
bundle exec rake
bundle exec jekyll serve

Visit http://127.0.0.1:4000/ in your browser.

Configuring openSUSE releases

The file _data/releases.yml is used by the distributions to render the right template (leap-$version). Please make sure that (leap-$version) has a corresponding template in _data/.

---
- version: 42.3
  order: 2
  releases:
  - date: '2017-07-08 00:00:00'
    state: 'RC'
  - date: '2017-07-26 00:00:00'
    state: 'Stable'
  - date: '2019-07-01 00:00:00 UTC'
    state: 'EOL'
- version: 42.2
  order: 1
  releases:
  - date: '2016-11-16 00:00:00'
    state: 'Stable'
  - date: '2018-01-26 00:00:00 UTC'
    state: 'EOL'
- version: 42.1
  order: 0
  releases:
  - date: '2016-11-16 00:00:00'
    state: 'Stable'
  - date: '2017-01-17 00:00:00 UTC'
    state: 'EOL'

get-o-o's People

Contributors

akshat5302 avatar alexminton avatar alkastner avatar apinter avatar arifpedia avatar badarotti avatar belphegor-belbel avatar cboltz avatar cchalu avatar cho2 avatar danchev avatar ddemaio avatar dependabot[bot] avatar elchevive avatar embar- avatar ggardet avatar hayyan71 avatar hellcp avatar hramrach avatar jlp avatar krisfremen avatar lkocman avatar monstorix avatar norwayfun avatar ramaxlo avatar skriesch avatar stacheldrahtje avatar super7ramp avatar weblate avatar wsxy162 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

get-o-o's Issues

[openSUSE Leap 15.4] cfengine-masterfiles version mismatch and python dependency problem

Hello,

when trying to get cfengine running with the packages from the Main Repositories I run into the following dependency problem:

ostest-lab-011:~ # zypper install --no-recommends cfengine cfengine-masterfiles
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides '/usr/bin/python' needed by the to be installed cfengine-masterfiles-3.15.3-bp154.1.3.noarch
 Solution 1: do not install cfengine-masterfiles-3.15.3-bp154.1.3.noarch
 Solution 2: break cfengine-masterfiles-3.15.3-bp154.1.3.noarch by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c/d/?] (c): 2
Resolving dependencies...
Resolving package dependencies...

The following 3 NEW packages are going to be installed:
  cfengine cfengine-masterfiles libpromises3

3 new packages to install.
Overall download size: 1.0 MiB. Already cached: 0 B. After the operation, additional 3.2 MiB will be used.
Continue? [y/n/v/...? shows all options] (y): y
Retrieving package libpromises3-3.17.0-bp154.1.3.x86_64                                                                    (1/3), 457.1 KiB (  1.2 MiB unpacked)
Retrieving: libpromises3-3.17.0-bp154.1.3.x86_64.rpm .....................................................................................................[done]
Retrieving package cfengine-3.17.0-bp154.1.3.x86_64                                                                        (2/3), 423.1 KiB (  1.1 MiB unpacked)
Retrieving: cfengine-3.17.0-bp154.1.3.x86_64.rpm .........................................................................................................[done]
Retrieving package cfengine-masterfiles-3.15.3-bp154.1.3.noarch                                                            (3/3), 177.7 KiB (896.1 KiB unpacked)
Retrieving: cfengine-masterfiles-3.15.3-bp154.1.3.noarch.rpm .............................................................................................[done]

Checking for file conflicts: .............................................................................................................................[done]
(1/3) Installing: libpromises3-3.17.0-bp154.1.3.x86_64 ...................................................................................................[done]
(2/3) Installing: cfengine-3.17.0-bp154.1.3.x86_64 .......................................................................................................[done]
(3/3) Installing: cfengine-masterfiles-3.15.3-bp154.1.3.noarch ...........................................................................................[done]

Could you please have a look into that and solve the dependency for cfengine-masterfiles package?

There is also a version mismatch between the two packages cfengine and cfengine-masterfiles:

ostest-lab-011:~ # zypper info cfengine cfengine-masterfiles | egrep "Repo|Name|Version|Arch|Vendor|---"
---------------------------------
Repository     : Main Repository
Name           : cfengine
Version        : 3.17.0-bp154.1.3
Arch           : x86_64
Vendor         : openSUSE
---------------------------------------------
Repository     : Main Repository
Name           : cfengine-masterfiles
Version        : 3.15.3-bp154.1.3
Arch           : noarch
Vendor         : openSUSE

I would expect both packages to have at least the same minor version 3.17 in that case...

Maybe you can align/fix that too?

Thanks a lot for that!

Image for server

We need a good representation of server page with an image that can be used as a background in a few places

JeOS rename to Minimal was Live images and JeOS are too hidden

The live images and JeOS are very well hidden and can only be reached by clicking a link in text after "Can't find what you are looking for?", which is a wording used on other web sites to redirect to support pages.

Please fix this, otherwise they're pretty much wasted effort.

Tumbleweed ports not marked as such

Tumbleweed ports are not (quite) as well supported and updated as the main architectures.
While users generally shouldn't notice a big difference, there has to be at least some indication of that.

For live images, there are warnings for even less reasons.

ISO download hashes don't match on Leap 15.2

I tried downloading both the NET and DVD install ISOs for Leap 15.2, and the hashes published don't match the hashes generated locally. I've tried downloading the files multiple time, and each time I get the same hash from both my image writing software, and the fciv utility for SHA1, but that hash I keep getting does not match the hash published on the site.

Also, the website explicitly says:
"For each ISO, we offer a checksum file with the corresponding SHA256 sum. "

However, the text files downloaded by clicking "Checksum" under each download type only contains a SHA1 checksum.

Edit: Never mind. The hash is labelled in the text file as SHA-1, but the hash is actually the SHA256.

Leap Micro overview overstates it's case

"Leap Micro is the Host OS that you were looking for."

Ahem? what about MicroOS?

Imagine we changed the openSUSE MicroOS Overview to say "The Host & Desktop OS that you were looking for". How unfair would that be to Leap, Tumbleweed, and Leap Micro?

Please, if we''re going to stay a community without parts of the project splitting off, lets not allow new efforts to overstate their role or function in the Project as a whole.

Leap Micro is not the host OS that everyone is looking for, just as the Tumbleweed page doesn't say it's the best traditional OS, or the Leap page doesn't say it's the best traditional OS.

Please change the Leap Micro page to state what Leap Micro actually is..

Consider pitching MicroOS for desktop use case

Why limit MicroOS for server-only use cases? I think there's a definite trend for a read-only btrfs root filesystem for general, regular users (not developers). In fact, I would not recommend anything else anymore. What is missing in the desktop section is a clear case for regular users (office, creatives, gamers, etc.) who simply want an innovative, up-to-date, secure and reliable system.

Replace stable with fixed for Leap

Since we want to nail in the point that Tumbleweed and Leap are stable, we should use fixed as the word to describe Leap's release schedule

Consider package manager comparison chart

More technically-oriented users look at the package manager first when deciding upon a new distribution. I would find it particularly helpful to have a quick overview over major features and differentiating criteria between package managers of major distributions such as Arch, Alpine, Debian, Fedora, and Void.

Wrong ISO name in SHA256 checksum files

Whe trying to verify my downloaded image of Leap 15.3 I got the following error:

$ sha256sum -c openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256
sha256sum: openSUSE-Leap-15.3-DVD-x86_64.iso: No such file or directory
openSUSE-Leap-15.3-DVD-x86_64.iso: FAILED open or read
sha256sum: WARNING: 1 listed file could not be read

The content of this file is the following:

$ cat openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256
0deae0b74953acd951150ae9567e098d450f2ae91b2d0c0a610b9d934f91c7b1  openSUSE-Leap-15.3-DVD-x86_64.iso

The name of the mentioned ISO in the checksum file is not matching the actual filename of the ISO. There is a -Current missing at the end of the filename in the checksum file. When adjusting it, the check succeeds:

$ cat openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256
0deae0b74953acd951150ae9567e098d450f2ae91b2d0c0a610b9d934f91c7b1  openSUSE-Leap-15.3-DVD-x86_64-Current.iso

$ sha256sum -c openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256
openSUSE-Leap-15.3-DVD-x86_64-Current.iso: OK
sha256sum -c openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256  20.57s user 1.46s system 99% cpu 22.083 total

This should also be the case of the other Leap images.

Build get-o-o in OBS

We would like build get-o-o in https://build.opensuse.org/project/users/openSUSE:infrastructure:software.opensuse.org
Any volunteer for packaging the sofware? This would then unblock automated deployments via salt.

We have a cron-based building in VM at this moment @hellcp can provide more information.

Ideally it would be build as software-o-o (osc service takes care of all rubygems and generates source tarball and changes file)
https://build.opensuse.org/package/show/openSUSE:infrastructure:software.opensuse.org/software_opensuse_org

Tumebleweed Download error

openSUSE.Tumbleweed.-.Get.openSUSE.-.Google.Chrome.2021-03-13.11-54-31.mp4

Unable to download offline iso file

Support for RTL languages.

Hi,
Is it possible to fix the pages to properly display RTL languages?
I translated the site to Arabic and the translation is now online. Aside from the obvious aligning issues, if the string contains both English and Arabic words the order of the words & sentences gets all mangled up.
Thanks for all the great work.

[openSUSE Leap 15.4] missing rpm metadata of package pam

Hello,

it seems that some relevant metadata of the package pam is missing:

ostest-lab-011:~ # rpm -qf /var/log/tallylog
file /var/log/tallylog is not owned by any package
ostest-lab-011:~ # zypper search --provides /var/log/tallylog
Loading repository data...
Reading installed packages...
No matching items found.

/var/log/tallylog seems to be the default logfile of pam module pam_tally2, i figured out...

Could you please have a look into this and fix the package accordingly?

Thanks a lot!

Consider introducing release terminology (point and rolling release)

I didn't find specific release terminology anywhere on the new website to guide new users. Many end-users will make their choice dependent on whether a distribution is a point release or a rolling release. I am a firm believer that the rolling release model is the future, architecturally as well as philosophically, and I think it would be good for the openSUSE project to indicate this trend somewhere on the website.

Wrong LiveUSB/LiveCD page

Contrary to what is stated in several paragraphs on the page, LiveCDs are in fact installable.

There are also various remains of gettext calls visible:

They cannot be used to install or upgrade Tumbleweed. Please use the _('Tumbleweed installation media') instead.

Link: https://software.opensuse.org/distributions/tumbleweed/unsupported

Also, the URL is IMO wrong. If the URL refers to "unsupported", it should list all unsupported media and not just live USBs, which the title implies. It should be https://software.opensuse.org/distributions/tumbleweed/liveusbs or similiar instead.

google-chrome blocks downloads from get-o-o

Reproducer (tested on Tumbleweed, originally reported by users not running openSUSE):

  • install google-chrome from official repos
  • Go to get.opensuse.org
  • Leap -> Testing
  • Click on x86_64 network image download

Result: Nothing happens. Download is not initiated

Works on Chromium. Google-chrome has no problem directly downloading image from download.opensuse.org

Mark releases as EOL

Despite 15.1 and 15.2 being considered EOL by the project, that's not reflected in releases.yml, that should be corrected

Long term agreement on handling Leap 15.X image respins (QuaterlyUpdates)

Hello team

regarding https://bugzilla.suse.com/show_bug.cgi?id=1196672

Fixed in 94b1127
and 51d19c8

In general the reason behind -N release suffix this is that image has always different checksum and we wanted to avoid referencing same downloadable with different checksum. Therefore Autobuild team recommended to have -N respin in the filename.

Regarding symlinks

We do have redundant symlinks -Media and -Current. In fact the -Current could be dropped and we could use just -Media as if we have to touch it it doesn't make any sense.

So the link could look as following:
openSUSE-Leap-15.3-N-{NET,DVD}-${ARCH}-Media.iso

I'd then always create a PR to sync the get-o-o with new symlinks. It's not an atomic operation as on one side we have to wait for cronjob to update get-o-o and on the other side we have to wait for TTM and OBS to finish the syncing of images, and once images are at ftp-stage, only then we can trigger following to sync data on prod by following:

./publish_distro publish_leap153.config --force

Thoughts? We will soon update the image again with -3 (for QuaterlyUpdate 2) so it would be nice to have the transaction discussed and organized. Thank you!

add containers tab

openSUSE Leap 15.0 also builds official docker images along the live images in openSUSE:Leap:15.0:Images. It's not some home grown images someone build somewhere so it's worth to also put that on the official software.o.o site.

How I don't know exactly as it's not a download. The images in the official project get released to dockerhub after testing. So one would just execute "docker pull opensuse/leap". Ie the web site would have tell to run this command. Maybe add another tab next to Installation and Live called "Containers" and add the instructions there?

Unstable color for LeapMicro

Hello,

I'm running the latest master locally and seems like I'm experiencing different background/header color for leapmicro_testing locally and also on production.

localvsprod

Typo on Kubic page

In the first sentence of the description of openSUSE Kubic, the word "Kubernetes" is repeated:

"Certified Kubernetes Kubernetes is an open-source system for automating deployment, scaling, and management of containerised applications."

Make the downloads take up less space

The downloads section is the main content on the distributions site, we need to make it easier for people to make the choices about what to download, which means we need to take up less space with the downloads section and more space with general info

Add some points about gaming to Tumbleweed

We have had complaints from gaming community that we don't do enough to tell people Leap might be too old for gaming, so we should make it clear that Tumbleweed is for gamers

Consider removing distinction between live and installation .ISO

I find the distinction between separate live and installation .ISOs obsolete in a modern operating system context. Many distributions with an explicit focus on usability have given up on this distinction and offer one installation medium which simultaneously functions as a live installer with persistant mode capabilities (e.g. changes made during the live run such as entering a WiFi password should be preserved after installation) to reduce post-installation setup time.

Let's offer "top" combustion script as part of the download experience for Micro

I would love to show "interactive" popup perhaps we could start with something similar to the Hey "Leap 15.4 RC is avilable" which would point user to get a combustion script for the machine.

As a second step we could substitute password by whatever user types, so user doesn't have to even touch the file.
I understand that Thorsten team was supposed to work on some sort of generator for this. Not sure if there is anything available.

We could start with template from @sysrich's [microos wiki page ]https://en.opensuse.org/Portal:MicroOS/Combustion#More_complex_configuration_example and then scripts done by adathor https://code.opensuse.org/adathor/combustion-dotconf/

@sysrich @hellcp thoughts?

get-o-o: Leap 15.3 appliance and live download links

Leap 15.3 seems to be changing the way how appliance and live images are published.
The live images are currently broken.

This is a task to agree on the destination, and adjust get-o-o links so they work properly.

Adrian confirmed that we'd like to have only one publish dir for all :Images (not /Images - dvd5 etc). Which would be publishable (unfrozen) even after GA.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.