On August 13, 2015 7:52:17 AM EDT, Ludwig Nussel wrote:

Marguerite Su wrote:

...

Inspired by the thread with @tiwai in M17N list, I created this:

https://forum.suse.org.cn/leap.html

This shows packages that are in Factory but not in Leap.

The webpage generates from a ruby script from me and refreshes every 6 hours (a cron job)

So packagers please help yourselves, just take a look and see if your packages are left behind.

Hey Marguerite, thanks for the reminder! There's also https://build.opensuse.org/project/monitor/openSUSE:42:Factory-Candidates-Ch... That project contains packages that are in Factory but not 42 and builds against 42. Everything that succeeds in there should be low hanging fruits for submission to 42. Maybe it would make sense to mass file submit requests for those. So package maintainer only have to ack the requests.

cu Ludwig

Ludwig, I know I have packages in Candidates that show success, but have unsatisfiable requires statements so not all the fruit is low hanging. Ie. Success means all Buildrequires: are satisfied by :42, but says nothing about Requires: 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

Hello, Am Donnerstag, 13. August 2015 schrieb Ludwig Nussel:

Marguerite Su wrote:

...

Inspired by the thread with @tiwai in M17N list, I created this:

https://forum.suse.org.cn/leap.html

This shows packages that are in Factory but not in Leap.

Thanks a lot! Can you make a similar list for packages that are in SLE, but not in Leap, please? Or add a comment at the Leap list saying something like "also available in the SLE sources"? Background: The SLE sources come with "maintenance for free", so IMHO we should use them whenever possible. (At least if they fit - as a counter- example, I have a SR pending to update Leap to AppArmor 2.10 ;-)

Maybe it would make sense to mass file submit requests for those. So package maintainer only have to ack the requests.

If the request mentions that this comes with the expectation of maintaining this package for $time - why not? Please (first!) do the same for the SLE packages that are not in Leap yet. Regards, Christian Boltz -- Um es mal so zu sagen: Ich Kohlenstoff. Computer Silizium. Silizium gefälligst so hüpfen, wie Kohlenstoff sagt, nicht umgekehrt. [Ratti in suse-linux] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thursday 13 August 2015, 22:33:19 wrote Marguerite Su:

On Thu, Aug 13, 2015 at 9:22 PM, Christian Boltz wrote:

...

Thanks a lot!

Can you make a similar list for packages that are in SLE, but not in Leap, please? Or add a comment at the Leap list saying something like "also available in the SLE sources"?

Background: The SLE sources come with "maintenance for free", so IMHO we should use them whenever possible. (At least if they fit - as a counter- example, I have a SR pending to update Leap to AppArmor 2.10 ;-)

Hi, Christian,

Is there any osc command that shows all packages from SLE?

If there is, there'll be easy for me...

All source container? This one: osc ls -e SUSE:SLE-12:Update Please note that this will have the maintenance updates container, so you might want to skip them using | egrep -v '\.[0123456789]*$' -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org