April 2020 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] Upgraded Redmine on progress.opensuse.org
by Estu Fardani 17 Apr '20

17 Apr '20

Hi openSUSE Community, We have been using Redmine as a ticketing system for a very long time. The previous server had Redmine 2.4.5 from 2014 installed on an old SLE 11 SP4 server. And finally we have successfully migrated to a newer Redmine version. Currently running Redmine 3.4.12 on a brand new server with Leap 15.1. This is a long awaited step in a long, long journey. Much time was spent fixing broken plugins, configuration and the database to match the new Redmine version. And we have a new theme to make it look fresh [1]. Thank you to all people who helped this migration run smoothly. Estu [1] https://progress.opensuse.org/ -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1

[opensuse-project] Re: Name for the new openSUSE release (was: [opensuse-factory] The community)
by Carlos E. R. 15 Apr '20

15 Apr '20

On 14/04/2020 15.53, Johannes Kastl wrote: > On 14.04.20 at 15:20 Gerald Pfeifer wrote: > >>> As an aside, Jump is an awful name, since it's a way too common of a >>> word in the English language to build any reasonable branding around it. >> >> Isn't Jump more like $JUMP, its actual name to be determined? > > We should decide on a sensible name very soon, otherwise Jump will be mentioned > in dozens of places already... :-( I think it is a very bad idea to change names, Yet another Time. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

7 9

[opensuse-project] Help needed for features for Leap 15.2
by ddemaio 14 Apr '20

14 Apr '20

Hi all, Thank you for those who added their input for Features for openSUSE Leap 15.2 on the wiki page - https://en.opensuse.org/Features_15.2 There are more features I will be adding. If you have an features you would like to add, please consider adding it. I'm sure more people in the community will probably has a better idea for some of the features that will be in 15.2, so it would be good if you could help. v/r Doug -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Re: Bringing Leap and SUSE Linux Enterprise closer together - a proposal
by PGNet Dev 11 Apr '20

11 Apr '20

i'm (re-, re-re-)reading up on these^ just-announced CloserTogether/NewLeap/Jump plans. given current plans, I'm trying to get a sense for whether we end up with more/less 'flexibility'. i know the question's been/being asked; i don't yet fully understand the answer. i realize the plans are in flux. here's my use-case. for opensuse-based production, none of the current releases -- out of the box -- meet my requirements. instead, currently, use a stable Leap core, with add'l repos -- devel or my own -- as needed. that approach is bumping into evermore significant limitations. particularly around 'base' tech'y. e.g., i use Kernel:Stable on Leap, with a rebuilt base:System Dracut, and the firmware upgrades that install along with it. i've switched to systemd-networkd rather than wicked for network mgmt. PRE-jump plans, Leap 15.2 remains stuck at Systemd v234 -- as that's the stable SLE-15* release. Afaict, it STAYS at that version for the entire 15x lifetime; unless/until there's a security-mandated update. with wireguard now native in-kernel, i'd like to use systemd-networkd's native WG support. but that's NOT available until systemd v>= 237; TW, of course, is at 244/245 already. does this CloserTogether "future" make it more, or less, likely that the 'Jump' release will have the flexibility to swap/enable version upgrades of key/core components -- in this case, systemd? or does Jump continue to stay stuck on old versions, leaving TW as the only choice of released version for newer base/core tech? yes, i can DIY my own opensuse systemd pkgs for Leap. working on it. going less well atm than hoped :-/ far simpler to use a distro that provides that flexibility (do that currently with Arch, and in-house LFS). prefer to have an option for a suse-based solution. is Jump it? -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

5 6

Re: [opensuse-factory] Re: [opensuse-project] Bringing Leap and SUSE Linux Enterprise closer together - a proposal
by Stasiek Michalski 09 Apr '20

09 Apr '20

On Thu, Apr 9, 2020 at 15:22, Michal Suchánek <msuchanek(a)suse.de> wrote: > On Thu, Apr 09, 2020 at 03:14:50PM +0200, Stasiek Michalski wrote: >> I will drill this part, since it's the most interesting to me. If we >> shared 100% of binaries we would have SLE, not Jump in the >> repositories, >> so I assume we are gonna diverge somewhere. Which package will have >> a >> dependency on branding-openSUSE and distribution-logos-openSUSE-Leap > None. > > AFAICT you have dependencies on branding and distribution-logos and > whichever package is in the repository provides those. The SLE > branding > packages will not get imported into the Jump/Leap repository so you > will > get the Leap branding. Repositories themselves don't have that power, and currently there are Recommends/Requires in product package and BuildRequires in installation-images to fulfill those branding requirements for various Tumbleweed based flavours (Tumbleweed, MicroOS and Kubic) and Leap. LCP [Stasiek] https://lcp.world -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1

[opensuse-project] Update on openSUSE + LibreOffice Conference
by ddemaio 03 Apr '20

03 Apr '20

Hi all, Here is a quick update about where we stand with the planned conference in October. Organizers of the openSUSE + LibreOffice Conference <https://events.opensuse.org/conferences/oSLO> had a meeting this week to discuss various topics surrounding COVID19 and how it may affect the conference and planning for it. At this point, it is uncertain what restrictions governments may keep in place in the coming months. While October is some months away, there are many aspects we are considering as to how to run the openSUSE + LibreOffice Conference. Travel restrictions, flights, hotel and venue availability, event capacity and our community members’ ability to attend the conference are all factors we are considering. We hope to make a decision about the conference at the latest by mid-June. In these difficult times, we want to assure our communities that we are actively engaged in a good outcome for all members, sponsors and interested parties involved with a successful openSUSE + LibreOffice Conference. We are looking at alternatives for the conference like possibly doing a virtual conference and exploring what tools might help us to achieve this should we decide it’s a viable option. Please remember that the Call for Papers is open and people can submit their talks until July 21 at events.opensuse.org. We are moving forward, assuming the conference will take place as planned from Oct. 13 - 16 and will keep our communities informed of any decisions we make regarding the plans for the conference and any alternatives options like a virtual conference. Stay safe, healthy and strong during these hard times and we hope to see all of you later this year; celebrating together our anniversary under much better circumstances! v/r Doug -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0