Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Johannes Obermayr
Am Freitag, 24. Februar 2017, 19:15:27 CET schrieb Stefan Seyfried: > Am 24.02.2017 um 11:15 schrieb Richard Brown: > > openSUSE would be happy to take everything we can to help reduce that > > burden upon Packman > > Easy: just build the stuff you think packman should build for you on > your own.

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Stefan Seyfried
Am 24.02.2017 um 11:15 schrieb Richard Brown: > openSUSE would be happy to take everything we can to help reduce that > burden upon Packman Easy: just build the stuff you think packman should build for you on your own. Then packman people can do what they want. Interesting software. Multimedia. W

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Stefan Seyfried
Hi all, Am 24.02.2017 um 10:29 schrieb Stefan Botter: > Hi Tomáš, (and of course all other list subscribers), > > thank you for your reply. > > On Thu, 23 Feb 2017 22:03:28 +0100 > Tomáš Chvátal wrote: >> I completely agree that the conflicts should be discussed here. The >> only >> person

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Olaf Hering
Am Fri, 24 Feb 2017 17:15:35 +0100 schrieb Bjørn Lie : > That is quite correct, and if possible: Could we get a "publish" > filter in place for all packages that "comes out" of > gstreamer-plugins-bad and gstreamer-plugins-ugly? That would be both bad and ugly. -1 from me. > The only 2 binaries

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Bjørn Lie
fr., 24.02.2017 kl. 16.20 +0100, skrev Olaf Hering: > > There is probably no need to replace the entire gstreamer stack > anymore. This is still done in 42.1 for historical reasons, > everything > else rebuilds just the bad/ugly plugins from the base distro. > > > > Olaf > That is quite corre

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Olaf Hering
Am Thu, 23 Feb 2017 21:23:42 +0100 schrieb Stefan Botter : > So here is my wish to start a discussion about the way packages in > PMBS will be maintained and moderated, and find a consensus. This > includes also the question, if PMBS's packages should be reduced to > the subset of full-featured pa

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Luigi Baldoni
On Friday, 24 February 2017 Olaf Hering wrote: > >What would be a proper replacement for full mplayer/mencoder > >functionality? > > I do not know the answer to that. > Not sure what the benefit of MPlayer is today. Not many I think. The npapi plugin that interfaced it with firefox has been delet

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Manfred Hollstein
On Fri, 24 Feb 2017, 14:48:14 +0100, Olaf Hering wrote: > Am Fri, 24 Feb 2017 11:45:42 +0100 > schrieb Manfred Hollstein : > > > What would be a proper replacement for full mplayer/mencoder > > functionality? > > I do not know the answer to that. > Not sure what the benefit of MPlayer is today.

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Olaf Hering
Am Fri, 24 Feb 2017 11:45:42 +0100 schrieb Manfred Hollstein : > What would be a proper replacement for full mplayer/mencoder > functionality? I do not know the answer to that. Not sure what the benefit of MPlayer is today. Olaf pgpsPFA1QohPG.pgp Description: Digitale Signatur von OpenPGP

Re: [packman] Kodi 16 but addons in 17

2017-02-24 Diskussionsfäden Manfred Hollstein
On Fri, 24 Feb 2017, 12:35:04 +0100, Sagi Ben-Akiva wrote: > kodi-17.0 and it's binary addons were published in packman repo. Thanks a lot, will try it as soon as they appear on the mirrors! > Sagi. Cheers. l8er manfred signature.asc Description: PGP signature

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Carlos E. R.
On 2017-02-24 12:09, Martin Pluskal wrote: > My overall goal with packman, at least for Essential project would be > to have only things that are not suitable for openSUSE there, > everything else should be in main distributions (Tumbleweed and via > maintenace updates in Leap) - and achieving this

Re: [packman] Kodi 16 but addons in 17

2017-02-24 Diskussionsfäden Sagi Ben-Akiva
kodi-17.0 and it's binary addons were published in packman repo. Sagi. On Thu, Feb 23, 2017 at 4:13 PM, Martin Pluskal wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thu, 2017-02-23 at 14:49 +0100, Manfred Hollstein wrote: > > thanks for you explanation! I just added a commen

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Martin Pluskal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2017-02-24 at 11:49 +0100, Tomáš Chvátal wrote: > 2017-02-24 10:29 GMT+01:00 Stefan Botter : > > > Tomáš Chvátal wrote: > > >  I completely agree that the conflicts should be discussed here. > > > The > > >  only > > > person I had to revok

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Martin Pluskal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2017-02-24 at 11:09 +0100, Manfred Hollstein wrote: > Indeed! Another example why the current approach to rely on some > packages being provided by Factory first is kodi-17. It got build by > some fellow packager here in PMBS with an libcec v

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Tomáš Chvátal
2017-02-24 10:29 GMT+01:00 Stefan Botter : > Tomáš Chvátal wrote: > > I completely agree that the conflicts should be discussed here. The > > only > > person I had to revoke rights I emailed right away explaining the > > situation because he was blindly reverting all the changes we did > > with

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Manfred Hollstein
Moin, On Fri, 24 Feb 2017, 11:36:11 +0100, Olaf Hering wrote: > Am Fri, 24 Feb 2017 11:09:42 +0100 > schrieb Manfred Hollstein : > > > Indeed! Another example why the current approach to rely on some > > packages being provided by Factory first is kodi-17. > > This is more an issue with the work

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Olaf Hering
Am Fri, 24 Feb 2017 11:09:42 +0100 schrieb Manfred Hollstein : > Indeed! Another example why the current approach to rely on some > packages being provided by Factory first is kodi-17. This is more an issue with the workflow. Using 'osc bco Multimedia kodi' would have shown the issue right away.

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Richard Brown
On 24 February 2017 at 10:29, Stefan Botter wrote: > And here again is the misunderstanding. Packman is not just there to > provide the same packages as openSUSE, only fully working ones. Packman > is a repository to host interesting software, which is elsewhere not > found. Or crippled. Or old.

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Manfred Hollstein
Hi there, first of all I'd like to heartfully thank you, Stefan, to start this discussion. It happened too often during the past months (actually since TW arrived), that software cannot be installed due to the reasons you explained very clearly. On Fri, 24 Feb 2017, 10:29:16 +0100, Stefan Botter

Re: [packman] PMBS - quo vadis?

2017-02-24 Diskussionsfäden Stefan Botter
Hi Tomáš, (and of course all other list subscribers), thank you for your reply. On Thu, 23 Feb 2017 22:03:28 +0100 Tomáš Chvátal wrote: > I completely agree that the conflicts should be discussed here. The > only > person I had to revoke rights I emailed right away explaining the > situation