This comment has been deleted

• Report

Marcus Rueckert (darix) - about 8 years ago

This would mean duplicating the whole chromium code

• Report

---

Ondřej Súkup (mimi_vx) - about 8 years ago

And this is problem?

@ryanbach maybe network:chromium subproject or better new own network:brave

• Report

Could these packages be added as links here? The package "frr" needs them:

https://build.opensuse.org/package/show/devel:libraries:c_c++/json-c https://build.opensuse.org/package/show/devel:libraries:c_c++/libyang

• Report

Andrey Karepin (EGDFree) - almost 7 years ago

maintainer

done

• Report

---

Erico Mendonca (emendonca) - almost 7 years ago

Thanks! One more is missing though: https://build.opensuse.org/package/show/devel:libraries:c_c++/rtrlib

• Report

Olaf Hering (olh) - almost 7 years ago

What variant of json-c and libyang is required by frr? The specfile is not very specific about that. Both libs are already in the base distro.

• Report

Jiri Slaby (jirislaby) - about 22 hours ago

have choice for pkgconfig(json-c): json-c-devel libjson-c-devel

Can someone add a Prefer (we build the former here now) to the prjconf?

• Report

may I please get a new project 'network:otobo' , a fork of otrs for the community. otrs 6 is EOL and no new version for community available in the near future.

• Report

Reinhard Max (rmax) - almost 6 years ago

maintainer

I am not sure the network project is the right home for high-level applications like this. I see that there are some of them packaged here (including OTRS) but IMO the purpose of the network project is to be a home for low-level networking tools and services rather than web applications that use networking rather than implementing some part of it.

Better candidates for hosting such web applications might be in the "Applications" or "server" hierarchies, but I see that there is also some unclear overlap between "network" and "server", so maybe we should define their scopes more clearly and then move packages to match that.

• Report

---

Christian Wittmer (computersalat) - almost 6 years ago

then I would vote for Application:ITS:otobo (ITS: Issue-Tracking-System)

• Report

---

Reinhard Max (rmax) - almost 6 years ago

maintainer

Sounds good to me, but I don't have the power to make it happen.

[update] But maybe Application:IssueTracker:otobo would be a more talking name. I woudn't have known immediately what ITS means.

• Report

We should enable a Leap 15.3 build target.

• Report

Eric Schirra (ecsos) - over 5 years ago

Yes it's time.

• Report

---

Reinhard Max (rmax) - over 5 years ago

maintainer

Done, and 15.2 as well.

• Report

---

Eric Schirra (ecsos) - over 5 years ago

Thank you. :-)

• Report

How about adding Leap 15.4?

• Report

Eric Schirra (ecsos) - almost 5 years ago

Isn't it already there?

• Report

---

Luigi Baldoni (alois) - almost 5 years ago

Uhhh, missed it.

• Report

---

Luigi Baldoni (alois) - almost 5 years ago

Although it could be renamed to openSUSE_Leap_15.4 for clarity.

• Report

---

Eric Schirra (ecsos) - almost 5 years ago

I would like that too. But I don't burn my fingers on it anymore. Supposedly there was a vote that the new repos should only be 15.4. If that is desired someone else can do the renaming or it should be discussed where else.

• Report

---

Lubos Kocman (lkocman-factory) - almost 5 years ago

yes the 15.4 is intentional (see the common codestream name survery post on factory from previous year).

• Report

Can someone please update sstp-client and NetworkManager-sstp. Packages in the reprository do not work with latest ppp provided.

• Report

Can someone enable Leap 15.6, please?

• Report

Can someone enable RISC-V, please?

• Report

Could we get devel:tools:building/protobuf and devel:libraries:c_c++/libyang linked to the network project? They're needed for frr.

• Report

Is it time to disable the SLES 12 repository when just under 2/3s of the packages don't build on it?

• Report

Can someone drop ppc64 from factory, please?

• Report

Please enable building against Leap 16.1 for this project:

Run osc meta prj -e network and copy the 16.0 section to 16.1

• Report

ungoogled-chromium cannot be updated at the moment, because the package is signed with an outdated key:

rpm -U ungoogled-chromium-156.0.8078.79-lp160.1.1.x86_64.rpm

error: Key 3c335b1300e006f2 (network:chromium OBS Project <network:chromium@build.opensuse.org>) expired on 2026-10-22 14:17:02

warning: ungoogled-chromium-156.0.8078.79-lp160.1.1.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 00e006f2: NOTTRUSTED

error: Key 3c335b1300e006f2 (network:chromium OBS Project <network:chromium@build.opensuse.org>) expired on 2026-10-22 14:17:02

error: Key 3c335b1300e006f2 (network:chromium OBS Project <network:chromium@build.opensuse.org>) expired on 2026-10-22 14:17:02 package ungoogled-chromium-156.0.8078.79-lp160.1.1.x86_64 does not verify: Header V3 DSA/SHA1 Signature, key ID 00e006f2: NOTTRUSTED

• Report

Olaf Hering (olh) - about 15 hours ago

The missing refresh of expired prj keys is a known bug in zypper.

The comment field in prjects/packages is not for support requests. The reason why the comment field exists at all in this instance is unclear.

• Report