Hi Stephan, I am aware of this repository, and it should be fine for my private computer. But what's the point of releasing a stable openSuse, when relevant software sticks to their old version with their old bugs? I already use repositories for C++ compilers, for KDE and some developer tools. These repositories have a high update frequency with a higher risk of breaking. More disadvantages are: * Additional repositories have no stable version * Companies often have policies to restrict them * It's easier to say, use Leap 42.2 instead of adding a list of repos * they are less tested Asking my question in a different way: Is there a reason not to update Tex Live? What actions should I perform to promote such an update? Bye Christoph -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, Jun 08, 2016 at 02:08:59PM +0200, Ludwig Nussel wrote:

Christoph Grüninger schrieb:

...

[...] Asking my question in a different way: Is there a reason not to update Tex Live? What actions should I perform to promote such an update?

texlive may look like a bunch of harmless add-on packages but it's actually integrated quite deep in the OS as many packages rely on it for building documentation. So a new texlive version has the potential to cause collateral damage in other packages. I'm not opposed to the update and in fact I think it makes sense. Someone has to go ahead and submit from Factory to 42.2. We can put texlive in a separate staging project to see what happens. You need the support or at least agreement with the package maintainer, as well as volunteers to help fix the potential breakage.

I'm currently working on TeXLive 2016 ... nevertheless this takes time as generating the spec files isn't an easy task. Also building and testing takes some time on 6000 packages as well :) And no, I've not yet submitted to Factory nor any other repository. Also submitting to Leap needs some perl packages updates as well to get biblatex-biber-2.4 working as well. This might cause some other side effects. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

Am 08.06.2016 um 21:45 schrieb Christoph Grüninger:

Dear Werner, what about pushing TeX Live 2015 to Leap 42.2 first? If TeX Live 2016 will be ready soon enough, we might consider updating it.

Just try it in stagings as Ludwig proposed - if 2015 already turns out to be problematic, there is no point in trying with 2016. It sounded to me as you have Werner's approval for the upgrade in general. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hello Werner, merge request 400773 submits texlive 2015 to Leap 42.2. Let's see how this will work. Somewhat related, would you be so kind and enable Leap 42.2 for the Publishing:TeXLive repository? Bye Christoph -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 09.06.2016 10:30, Christoph Grüninger wrote:

Hello Werner, merge request 400773 submits texlive 2015 to Leap 42.2. Let's see how this will work.

Texlive are at least 26 more packages - the actual tex sources and fonts. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Fri, Jun 10, 2016 at 03:02:31PM +0200, Ludwig Nussel wrote:

Christoph Grüninger schrieb:

...

merge request 400773 submits texlive 2015 to Leap 42.2. Let's see how this will work.

It's in Staging:C for now: https://build.opensuse.org/project/staging_projects/openSUSE:Leap:42.2/C

As already pointed out texlive is not just one package though. Also, it needs to be decided whether to go for 2015 or the new 2016. If 2015 you need to create a separate subproject as devel project for Leap, in case you need to apply extra fixes to that branch.

The TeXLive 2016 is ready to be submitted and should build at least for Factory below Publishing:TeXLive. It would be perfect if the TL 2015 could be moved into a new project Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

On Fri, Jun 10, 2016 at 10:53:36PM +0200, Christoph Grüninger wrote:

Hi Ludwig, I see the 27 missing packages. Not sure whether they will fix the current build errors. I posted a single merge request for one more package, as I don't know how to set up a devel project.

...

As already pointed out texlive is not just one package though. Also, > it needs to be decided whether to go for 2015 or the new 2016.

I'd say let's got with 2015, unless Werner gives a go for 2016.

...

If 2015 you need to create a separate subproject as devel project for Leap, in case you need to apply extra fixes to that branch.

How do I achieve this?

Now the TL2015 is submitted to Leap 42.2 and also the new TL 2016 is in standard Publishing:TeXLive project now for OS13.2, Factory (but not for PPC as perl is broken due nothing provides perl(:MODULE_COMPAT_5.22.0)), Leap 42.1, and maybe Leap 42.2 if it will build finally :) Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr