Continuing to look at packages I maintain I see calc in $subject has no build results and no listed missing dependencies. Why? https://build.opensuse.org/package/show/openSUSE:42:Factory-Candidates-Check... Fyi: it has no dependencies outside of libc, so it should definitely build for 42. Thanks Greg -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi, just my few cents since I'm not doing release management. Am 09.08.2015 um 15:19 schrieb greg.freemyer@gmail.com:

I just took a look through $subject and there is a lot packages there that apparently have not yet made it to Leap.

As packages are SR'ed to Leap, are they removed from $subject?

I would expect that.

These are a few I was surprised to see in the long list of candidates.

Amanda Bluedevil Encfs PhpMyAdmin Spec-cleaner Wireshark

As I understood from the different explanation mails: coolo has chosen a small subset of packages to begin with. That is from SLE12 as well as from Tumbleweed/Factory. Now users, developers and especially maintainers are asked to walk through their packages and check if they are already in 42.1 - if yes, then check if they are taken from the source which makes most sense * if yes, nothing to be done - if not, submit it to openSUSE:42 to get it in

Anyway, I'm concerned that as a user I will have to have dozens of extra OBS repos in order to have the broad selection packages I'm used to.

I know I've been resisting submitting most of my packages to Leap because they are dynamic and I want users to be using the latest version.

So yes, you thought about it. Every maintainer should make that decision. (BTW, how can I get a list of packages from Factory where I'm the "maintainer"? My "user" page seems to be somehow incomplete. Not sure if I get everything where I'm meant to be in charge ;-))

The spec-cleaner and wireshark maintainers may have the same concern.

The bonus is: Do not check only your packages but also check others you are interested in and find to be needed in Leap. If those are in SLE12 I would just propose to submit them since they already have some kind of maintenance guarantee (as I understand it). If they are in Factory, the maintainer is the person to contact and ask for inclusion. Please note that this is my current understanding only and I might have interpreted something wrong. In any case getting a sane package list for Leap is probably one of the important things to figure out _now_ and trusting in all package maintainers reacting themselves according to your expectations is probably a bit risky.

Do we need a new repo: Leap:42-dynamic where version updates are allowed? Then rapidly changing packages can be SR'ed there.

Why would we need an extra repo for that? Updating packages is already an option for previous releases. For so called "leaf" packages this could be an option as well. I guess there were not many people complaining about spec-cleaner or wireshark updates. The question might be if the extra process to provide real maintenance updates is the right choice for some of the packages. In the past we had a "contrib" repo for distribution releases which was pretty much obsolete by the more free upgrade policies of later openSUSE releases. Do we need such an collective repo again where packages can be updated without any big process? I cannot answer that right now at least. It depends how big the final package set of Leap will be. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org