dist.upgradepath FAILED for FEDORA-2016-302f840ecf

dist.upgradepath FAILED for FEDORA-2016-302f840ecf https://taskotron.fedoraproject.org/artifacts/all/07ae3c38-bdda-11e6-8c44-525400120b80/task_output/FEDORA-2016-302f840ecf.log ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To

dist.upgradepath FAILED for perl-DBD-MySQL-4.039-2.fc24

dist.upgradepath FAILED for perl-DBD-MySQL-4.039-2.fc24 https://taskotron.fedoraproject.org/artifacts/all/07ae3c38-bdda-11e6-8c44-525400120b80/task_output/perl-DBD-MySQL-4.039-2.fc24.log ___ perl-devel mailing list --

[Bug 1403038] perl-iCal-Parser-1.21 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1403038 --- Comment #4 from Fedora Update System --- perl-iCal-Parser-1.21-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-93431904d1 -- You are receiving this mail

[Bug 1403038] perl-iCal-Parser-1.21 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1403038 --- Comment #3 from Fedora Update System --- perl-iCal-Parser-1.21-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-aaf3ae8ea6 -- You are receiving this mail

[Bug 1403038] perl-iCal-Parser-1.21 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1403038 --- Comment #2 from Fedora Update System --- perl-iCal-Parser-1.21-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-0cc7e7d71e -- You are receiving this mail

ppisar pushed to perl-iCal-Parser (f23). "Mandatory Perl build-requires added "

From 9cd186e931840a95152f5d378f18bfe59add9332 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Fri, 24 Jun 2016 10:00:45 +0200 Subject: Mandatory Perl build-requires added ---

ppisar pushed to perl-iCal-Parser (f23). "1.21 bump"

From ab265fca07de82c9c53fde6daeb2800672312190 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Fri, 9 Dec 2016 07:25:55 +0100 Subject: 1.21 bump --- .gitignore| 1 + .rpmlint | 2 ++ perl-iCal-Parser.spec | 7 +-- sources

ppisar pushed to perl-iCal-Parser (f24). "1.21 bump"

From 4739ca583ee25c433b4401734149d6afb38737e0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Fri, 9 Dec 2016 07:25:55 +0100 Subject: 1.21 bump --- .gitignore| 1 + .rpmlint | 2 ++ perl-iCal-Parser.spec | 7 +-- sources

ppisar pushed to perl-iCal-Parser (f24). "Mandatory Perl build-requires added "

From 486ee8f95cbaea2f274dfcc3090811590b8f53ed Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Fri, 24 Jun 2016 10:00:45 +0200 Subject: Mandatory Perl build-requires added ---

ppisar pushed to perl-iCal-Parser (f25). "1.21 bump"

From 6a76f314ece5fd83fdf24b7bc810d10217810420 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Fri, 9 Dec 2016 07:25:55 +0100 Subject: 1.21 bump --- .gitignore| 1 + .rpmlint | 2 ++ perl-iCal-Parser.spec | 9 ++--- sources

[Bug 1403038] perl-iCal-Parser-1.21 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1403038 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In

ppisar pushed to perl-iCal-Parser (master). "1.21 bump"

From 6a76f314ece5fd83fdf24b7bc810d10217810420 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Fri, 9 Dec 2016 07:25:55 +0100 Subject: 1.21 bump --- .gitignore| 1 + .rpmlint | 2 ++ perl-iCal-Parser.spec | 9 ++--- sources

ppisar uploaded iCal-Parser-1.21.tar.gz for perl-iCal-Parser

a6368ce23da9155e783ed39fea25bbd5 iCal-Parser-1.21.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-iCal-Parser/iCal-Parser-1.21.tar.gz/md5/a6368ce23da9155e783ed39fea25bbd5/iCal-Parser-1.21.tar.gz ___ perl-devel mailing list --

[Bug 1402816] perl-Math-BigInt-1.999804 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1402816 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In

ppisar pushed to perl-Math-BigInt (master). "1.999804 bump"

From 05ee05c25256c6a66a4e15daf152b013f28b9166 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Fri, 9 Dec 2016 06:59:21 +0100 Subject: 1.999804 bump --- .gitignore| 1 + perl-Math-BigInt.spec | 5 - sources | 2 +- 3 files

ppisar uploaded Math-BigInt-1.999804.tar.gz for perl-Math-BigInt

73cd663591645a1589845103001bab60 Math-BigInt-1.999804.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Math-BigInt/Math-BigInt-1.999804.tar.gz/md5/73cd663591645a1589845103001bab60/Math-BigInt-1.999804.tar.gz ___ perl-devel mailing list

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 9:07 PM, Kevin Kofler wrote: > However, I also do not see why we cannot just do such big updates through > the regular update process rather than in a big .1 drop. The KDE SIG has > experience with pushing big grouped updates that look a lot like a

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

Matthew Miller wrote: > Option 1: Big batched update > > 1. Release F26 according to schedule > https://fedoraproject.org/wiki/Releases/26/Schedule > > 2. At the beginning of October, stop pushing non-security updates > from updates-testing to updates > > 3. Bigger updates

Re: Call to retire gstreamer-0.10

Michael Cronenworth wrote: > Last month there were a handful of security vulnerabilities disclosed[1] > and upstream no longer maintains the 0.10 series. While we could patch and > update our Fedora packages this is a perfect opportunity to retire it. You will need to address the vulnerabilities

Re: mutter broken in Rawhide

Samuel Sieb wrote: > You keep making this point, but I haven't seen any explanation for it. > Why is it necessary to have Rawhide broken in order to do development? > Don't you develop locally and then push the result when it's functional? No (at least not for the typical packaging "development"

Re: mutter broken in Rawhide

Adam Williamson wrote: > But it does depend on several other things that went through the libldb > / libtdb complex. KDE images failed to compose and KDE package sets > failed to install just like Server and Workstation. (KDE is in fact > still broken even now ldb and tdb have been fixed, but

[EPEL-devel] Fedora EPEL 7 updates-testing report

The following Fedora EPEL 7 Security updates need testing: Age URL 641 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087 dokuwiki-0-0.24.20140929c.el7 403 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f mcollective-2.8.4-1.el7 122

[EPEL-devel] Fedora EPEL 5 updates-testing report

The following Fedora EPEL 5 Security updates need testing: Age URL 760 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-3849 sblim-sfcb-1.3.8-2.el5 403 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-edbea40516 mcollective-2.8.4-1.el5 375

[EPEL-devel] Fedora EPEL 6 updates-testing report

The following Fedora EPEL 6 Security updates need testing: Age URL 519 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031 python-virtualenv-12.0.7-1.el6 513 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168 rubygem-crack-0.3.2-2.el6 445

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On 9 Dec 2016 14:02, "Stephen John Smoogen" wrote: On 8 December 2016 at 21:56, Peter Robinson wrote: > On Thu, Dec 8, 2016 at 8:13 PM, Adam Williamson > wrote: >> On Thu, 2016-12-08 at 09:17 -0500, Matthew Miller wrote: >>>

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On 8 December 2016 at 21:56, Peter Robinson wrote: > On Thu, Dec 8, 2016 at 8:13 PM, Adam Williamson > wrote: >> On Thu, 2016-12-08 at 09:17 -0500, Matthew Miller wrote: >>> Trying to make this idea a little more concrete. Here's two suggestions

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 8:38 PM, Adam Williamson wrote: > On Thu, 2016-12-08 at 13:33 -0700, Chris Murphy wrote: >> I think that ignores that we're pretty much always slipping, and they >> aren't in fact 6 month cycles. > > Well, since 22 we've got a lot closer to being

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 8:13 PM, Adam Williamson wrote: > On Thu, 2016-12-08 at 09:17 -0500, Matthew Miller wrote: >> Trying to make this idea a little more concrete. Here's two suggestions >> for how it might work. These are strawman ideas -- please provide >>

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 6:59 PM, Matthew Miller wrote: > On Thu, Dec 08, 2016 at 07:41:13PM +0100, drago01 wrote: >> Which problem are you trying to solve with those proposals? > > From my *other* other mail: > > * predictable calendar dates, to help with long-term

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016, at 01:26 PM, Dennis Gilmore wrote: > > I would like to see us stop pushing non security updates to updates from > updates-testing entirely and do it in monthly batches instead. we would push > daily security fixes and updates-testing. However this would make atomic >

[389-devel] Please review patch 1: fix memory leaks

https://fedorahosted.org/389/ticket/49066 https://fedorahosted.org/389/attachment/ticket/49066/0001-Ticket-49066-Memory-leaks-in-server.patch -- Sincerely, William Brown Software Engineer Red Hat, Brisbane signature.asc Description: This is a digitally signed message part

Re: Some preliminary Fedora 25 stats — and future release scheduling

On 8 December 2016 at 20:00, Peter Robinson wrote: > On Fri, Dec 9, 2016 at 12:39 AM, Stephen John Smoogen > wrote: >> On 8 December 2016 at 19:30, Peter Robinson wrote: >>> On Mon, Dec 5, 2016 at 2:47 PM, Matthew Miller

Re: Some preliminary Fedora 25 stats — and future release scheduling

On Fri, Dec 9, 2016 at 12:39 AM, Stephen John Smoogen wrote: > On 8 December 2016 at 19:30, Peter Robinson wrote: >> On Mon, Dec 5, 2016 at 2:47 PM, Matthew Miller >> wrote: >>> The stats I get are about a week behind, which

Re: Some preliminary Fedora 25 stats — and future release scheduling

On Mon, Dec 5, 2016 at 9:26 PM, Matthew Miller wrote: > On Mon, Dec 05, 2016 at 01:43:58PM -0700, Chris Murphy wrote: >> I'm not sure it's much harder to do without modularity. Right now >> Fedora could do a Fedora 26 release without any conventional release >> media for

Re: Some preliminary Fedora 25 stats — and future release scheduling

On 8 December 2016 at 19:30, Peter Robinson wrote: > On Mon, Dec 5, 2016 at 2:47 PM, Matthew Miller > wrote: >> The stats I get are about a week behind, which means I now have >> information about the first week of the Fedora 25 release. See the

Re: Some preliminary Fedora 25 stats — and future release scheduling

On Tue, Dec 6, 2016 at 9:11 AM, Daniel P. Berrange wrote: > On Mon, Dec 05, 2016 at 06:41:27PM -0700, Chris Murphy wrote: >> On Mon, Dec 5, 2016 at 5:03 PM, Michael Catanzaro >> wrote: >> > On Mon, 2016-12-05 at 16:10 -0500, Matthew Miller wrote: >> >>

Re: Some preliminary Fedora 25 stats — and future release scheduling

On Mon, Dec 5, 2016 at 2:47 PM, Matthew Miller wrote: > The stats I get are about a week behind, which means I now have > information about the first week of the Fedora 25 release. See the > graph here: > >

[Bug 1401740] perl-Text-Reflow-1.16 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1401740 Upstream Release Monitoring changed: What|Removed |Added

Re: Some preliminary Fedora 25 stats — and future release scheduling

On Tue, Dec 6, 2016 at 8:15 PM, Matthew Miller wrote: > On Tue, Dec 06, 2016 at 09:00:35AM -0500, Kamil Paral wrote: >> With my QA hat on, I believe using decimal releases (integers, >> characters or anything else) is a bad idea. The reason is that people >> don't

[Bug 1403038] New: perl-iCal-Parser-1.21 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1403038 Bug ID: 1403038 Summary: perl-iCal-Parser-1.21 is available Product: Fedora Version: rawhide Component: perl-iCal-Parser Keywords: FutureFeature, Triaged Assignee:

Re: octave 4.2 update in rawhide

On 12/07/2016 12:39 AM, Vascom wrote: > Thanks for your work. You're welcome, and thanks. > Hope we will see Octave 4.2 in f24, f25 too. Nope. Perhaps someday in https://copr.fedorainfracloud.org/coprs/g/scitech/octave/ though. > ср, 7 дек. 2016 г. в 8:51, Orion Poplawski

Re: octave 4.2 update in rawhide

On 12/06/2016 10:51 PM, Orion Poplawski wrote: > The hdf5 update prompted me to (perhaps too hastily) update octave to 4.2 in > rawhide as well. This unfortunately has led to the need to rework the octave > package build/install macros. I have what I hope is a fix building now >

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 2:05 PM, Stephen John Smoogen wrote: > On 8 December 2016 at 15:31, Matthew Miller wrote: > >>> > * maximum PR and user growth >>> How is less PR (only one event per year) instead of two lead into >>> "maximum PR" ? >> >> Two

[Bug 1397222] perl-No-Worries-1.4 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1397222 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-No-Worries-1.4-1.fc25

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On 8 December 2016 at 15:31, Matthew Miller wrote: >> > * maximum PR and user growth >> How is less PR (only one event per year) instead of two lead into >> "maximum PR" ? > > Two releases a year ends up barely being an "event", so it's hard to > drum up new

[Bug 1397222] perl-No-Worries-1.4 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1397222 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-No-Worries-1.4-1.fc25

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 1:38 PM, Adam Williamson wrote: > On Thu, 2016-12-08 at 13:33 -0700, Chris Murphy wrote: >> I think that ignores that we're pretty much always slipping, and they >> aren't in fact 6 month cycles. > > Well, since 22 we've got a lot closer to being

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, 2016-12-08 at 13:37 -0700, Chris Murphy wrote: > On Thu, Dec 8, 2016 at 1:34 PM, Adam Williamson > wrote: > > On Thu, 2016-12-08 at 13:29 -0700, Chris Murphy wrote: > > > How much time-effort is put > > > into creating testing qualifying and releasing images? >

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, 2016-12-08 at 13:33 -0700, Chris Murphy wrote: > I think that ignores that we're pretty much always slipping, and they > aren't in fact 6 month cycles. Well, since 22 we've got a lot closer to being back to May/November. We've had: 22: May 23: November 24: June 25: November so we've

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 08, 2016 at 01:33:41PM -0700, Chris Murphy wrote: > I think that ignores that we're pretty much always slipping, and they > aren't in fact 6 month cycles. There's always pressure to get the fall > release done on time to avoid hitting end of year holiday season, and > we have actually

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 1:34 PM, Adam Williamson wrote: > On Thu, 2016-12-08 at 13:29 -0700, Chris Murphy wrote: >> How much time-effort is put >> into creating testing qualifying and releasing images? > > On this note... > >

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, 2016-12-08 at 13:29 -0700, Chris Murphy wrote: > How much time-effort is put > into creating testing qualifying and releasing images? On this note... https://openqa.stg.fedoraproject.org/tests/overview?distri=fedora=24=FedoraRespin-24-20161206=1 -- Adam Williamson Fedora QA Community

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 1:20 PM, drago01 wrote: > > Well I am trying to understand what you are trying to do before > thinking of solutions. > I think the 6 months cycle worked pretty well so far so I'd rather > only change it for good reasons. I think that ignores that we're

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 08, 2016 at 09:20:50PM +0100, drago01 wrote: > >> Which problem are you trying to solve with those proposals? > > From my *other* other mail: > > * predictable calendar dates, to help with long-term planning > Longer cycles are not necessarily mean no slips. I wasn't referring to

pghmcfc pushed to perl-Array-Compare (perl-Array-Compare-2.12.2-1.fc26). "Update to 2.12.2 (..more)"

From b6415fb23f92681f82e1a5dc6f9503a1f4b52f93 Mon Sep 17 00:00:00 2001 From: Paul Howarth Date: Thu, 8 Dec 2016 20:22:21 + Subject: Update to 2.12.2 - New upstream release 2.12.2 - Packaging changes --- .gitignore | 1 + perl-Array-Compare.spec | 12

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 1:18 PM, Chris Murphy wrote: > On Thu, Dec 8, 2016 at 1:13 PM, Adam Williamson > wrote: >> On Thu, 2016-12-08 at 09:17 -0500, Matthew Miller wrote: >>> Trying to make this idea a little more concrete. Here's two

pghmcfc pushed to perl-Array-Compare (master). "Update to 2.12.2 (..more)"

From b6415fb23f92681f82e1a5dc6f9503a1f4b52f93 Mon Sep 17 00:00:00 2001 From: Paul Howarth Date: Thu, 8 Dec 2016 20:22:21 + Subject: Update to 2.12.2 - New upstream release 2.12.2 - Packaging changes --- .gitignore | 1 + perl-Array-Compare.spec | 12

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 7:59 PM, Matthew Miller wrote: > On Thu, Dec 08, 2016 at 07:41:13PM +0100, drago01 wrote: >> Which problem are you trying to solve with those proposals? > > From my *other* other mail: > > * predictable calendar dates, to help with long-term

pghmcfc uploaded Array-Compare-v2.12.2.tar.gz for perl-Array-Compare

a666fe1be9867d52bd18f8773b160087 Array-Compare-v2.12.2.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Array-Compare/Array-Compare-v2.12.2.tar.gz/md5/a666fe1be9867d52bd18f8773b160087/Array-Compare-v2.12.2.tar.gz ___ perl-devel mailing

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 1:13 PM, Adam Williamson wrote: > On Thu, 2016-12-08 at 09:17 -0500, Matthew Miller wrote: >> Trying to make this idea a little more concrete. Here's two suggestions >> for how it might work. These are strawman ideas -- please provide >>

[Bug 1397222] perl-No-Worries-1.4 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1397222 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-No-Worries-1.4-1.fc25

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, 2016-12-08 at 09:17 -0500, Matthew Miller wrote: > Trying to make this idea a little more concrete. Here's two suggestions > for how it might work. These are strawman ideas -- please provide > alternates, poke holes, etc. And particularly from a QA and rel-eng > point of view. Both of

Copr random troubles?

I'm fighting with copr errors. https://copr.fedorainfracloud.org/coprs/mschwendt/audacious-next/build/486157/ Sometimes it fails for i386, then for x86_64. Once for an rsync error. The I resubmitted, and it failed with something else. Is it this? DEBUG util.py:421: Failed to synchronize

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On 12/08/2016 02:06 PM, Stephen John Smoogen wrote: What basis and factual data would you want to see? Not being clear here means that what ever anyone can provide can be dismissed as not being real data or basis. Something that says "this is better" other than because Spot thought it up one

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On 8 December 2016 at 15:01, Michael Cronenworth wrote: > On 12/08/2016 12:26 PM, Dennis Gilmore wrote: >> >> I would like to see us stop pushing non security updates to updates from >> updates-testing entirely and do it in monthly batches instead. > > > Where did this concept

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

* Michael Cronenworth [08/12/2016 14:01] : > > Where did this concept originate from? This is a very old proposal that Spot made at the very first Flock way back in 2013. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On 12/08/2016 12:26 PM, Dennis Gilmore wrote: I would like to see us stop pushing non security updates to updates from updates-testing entirely and do it in monthly batches instead. Where did this concept originate from? What basis and factual data backs up this proposal?

Re: Looking for co-maintainers - texstudio

> Hi Johannes, > > as I'm experienced with Qt related stuff (member of KDE SIG too) and > also use TeXStudio as my default TeX editor all day, I requested commit > access now :) You're hired! ;-) > > Greetings, > Christian > > > On 12/08/2016 05:36 PM, Johannes Lips wrote:

[Bug 1402614] perl-CBOR-XS-1.6 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1402614 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA

Re: Fedora captive portal page changed output :(

On jueves, 8 de diciembre de 2016 12:22:30 PM CST Michael Catanzaro wrote: > On Thu, 2016-12-08 at 10:50 -0600, Dennis Gilmore wrote: > > android gives you a tls error and offers to go to the page ina > > browser where > > you can ignore the error manually. I think we should do the same as > >

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 08, 2016 at 07:45:55PM +0100, Christian Dersch wrote: > What do you expect from monthly batches? I *really* don't like things > like "patchdays". Besides security fixes there are also other situations > like small but annoying bugs… IMHO the current model with updates repo > works

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 08, 2016 at 07:41:13PM +0100, drago01 wrote: > Which problem are you trying to solve with those proposals? From my *other* other mail: * predictable calendar dates, to help with long-term planning * not being on a hamster wheel which routinely bursts into flame * maintaining

Re: Call to retire gstreamer-0.10

On Thu, 2016-12-08 at 14:24 +0100, Dominik 'Rathann' Mierzejewski wrote: > One important example is the Citrix Receiver for Linux[1], which > depends on > gstreamer-0.10: > $ rpm -qR ICAClient|grep gst > libgstapp-0.10.so.0()(64bit) > libgstbase-0.10.so.0()(64bit) >

Re: Schedule for Friday's FESCo Meeting (2016-12-09)

On Thu, Dec 8, 2016 at 11:46 AM, Adam Miller wrote: > Following is the list of topics that will be discussed in the > FESCo meeting Friday at 16:00UTC in #fedora-meeting on > irc.freenode.net. > > To convert UTC to your local time, take a look at >

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On 12/08/2016 07:26 PM, Dennis Gilmore wrote: > I would like to see us stop pushing non security updates to updates from > updates-testing entirely and do it in monthly batches instead. we would push > daily security fixes and updates-testing. However this would make atomic > host > 2 week

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 3:17 PM, Matthew Miller wrote: > Trying to make this idea a little more concrete. Here's two suggestions > for how it might work. These are strawman ideas -- please provide > alternates, poke holes, etc. And particularly from a QA and rel-eng >

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 08, 2016 at 01:30:33PM -0500, Ben Cotton wrote: > I'd like to build on this a little bit. I'm concerned that we've gone > straight to discussing the "how" without a clear picture of the "why". A fair point - I didn't mean to jump ahead, but sometimes things are easier to talk about if

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 08, 2016 at 12:26:21PM -0600, Dennis Gilmore wrote: > I would like to see us stop pushing non security updates to updates > from updates-testing entirely and do it in monthly batches instead. > we would push daily security fixes and updates-testing. Also part of Spot's suggestion -

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On Thu, Dec 8, 2016 at 12:40 PM, Przemek Klosowski wrote: > So, my TL;DR message is, think carefully what aspects are important > (technical? organizational? marketing?), what constituencies are involved in > each, what changes are desirable, how to measure their

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On jueves, 8 de diciembre de 2016 9:17:14 AM CST Matthew Miller wrote: > Trying to make this idea a little more concrete. Here's two suggestions > for how it might work. These are strawman ideas -- please provide > alternates, poke holes, etc. And particularly from a QA and rel-eng > point of

Re: Call to retire gstreamer-0.10

On Wed, Dec 07, 2016 at 10:47:12PM -0600, Michael Cronenworth wrote: > On 12/07/2016 05:07 PM, Sérgio Basto wrote: > > gstreamermm-1.4.3-1.fc25 looks like already use gstreamer1 > >subtitleeditor-0.53.0-1.fc25 also already use gstreamer1 > > > > That's good! My initial list was run from Fedora

Re: Fedora captive portal page changed output :(

On Thu, 2016-12-08 at 10:50 -0600, Dennis Gilmore wrote: > android gives you a tls error and offers to go to the page ina > browser where  > you can ignore the error manually. I think we should do the same as > android > > Dennis What's the benefit of directing the user to a browser...?

[Bug 1397222] perl-No-Worries-1.4 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1397222 Fedora Update System changed: What|Removed |Added Status|ON_QA

Re: Fedora Rawhide-20161208.n.0 compose check report

On Thu, 2016-12-08 at 09:43 -0800, Adam Williamson wrote: > After that, it never reaches 'Started NFS server and services' (which > is nfs-server.service) as it should. Will file a bug on this. Looks like this is: https://bugzilla.redhat.com/show_bug.cgi?id=1402490 an SELinux denial caused by

Re: future of official optical media support in Fedora

On jueves, 8 de diciembre de 2016 8:44:19 AM CST Thomas Gilliard wrote: > On 12/08/2016 08:22 AM, Dennis Gilmore wrote: > > On miércoles, 7 de diciembre de 2016 1:56:32 PM CST Mike Pinkerton wrote: > >> On 6 Dec 2016, at 09:43, Kamil Paral wrote: > > > > [1] https://boot.fedoraproject.org/ > >

Re: Fedora Rawhide-20161208.n.0 compose check report

On Thu, 2016-12-08 at 15:25 +, Fedora compose checker wrote: > Missing expected images: > > Workstation live i386 > Kde live x86_64 > Workstation live x86_64 > Kde live i386 > > Failed openQA tests: 10/79 (x86_64), 2/15 (i386), 1/2 (arm) > > New failures (same test did not fail in

Re: Two more concrete ideas for what a once-yearly+update schedule would look like

On 12/08/2016 11:10 AM, Matthew Miller wrote: It's my plan to explore different ideas to continue to make Fedora more successful as measured by user and contributor growth, contributor return on effort, and fulfillment of our mission. Your stated goals are quite high level, so I would like to

Re: installing RPMs on NFS filesystems

On lunes, 5 de diciembre de 2016 11:44:14 AM CST Dave Love wrote: > den...@ausil.us writes: > > Without filesystem capabilities, many things will not work. Ping as a > > user for instance. Lots of setuid binaries switched to using > > filesystem capabilities rather than setuid and require it to

Re: GSequencer upstream wants to package for fedora

On Thu, Dec 08, 2016 at 05:13:24PM +0100, Michael Schwendt wrote: > On Thu, 8 Dec 2016 15:21:21 +0100, Joël Krähemann wrote: > > > My name is Joël Krähemann. I maintain Advanced Gtk+ Sequencer and I'd > > like to provide it in fedora. Linux is my OS of choice since 2001. > > Along the time I have

Re: future of official optical media support in Fedora

On Thu, Dec 8, 2016 at 11:22 AM, Dennis Gilmore wrote: > On miércoles, 7 de diciembre de 2016 1:56:32 PM CST Mike Pinkerton wrote: >> On 6 Dec 2016, at 09:43, Kamil Paral wrote: >> > Which images to cover, that's the heart of the discussion. If you >> > look into our test matrix

Re: Schedule for Friday's FESCo Meeting (2016-12-09)

On 12/08/2016 11:46 AM, Adam Miller wrote: > Following is the list of topics that will be discussed in the > FESCo meeting Friday at 16:00UTC in #fedora-meeting on > irc.freenode.net. > > To convert UTC to your local time, take a look at > http://fedoraproject.org/wiki/UTCHowto > > or run: >

Re: Looking for co-maintainers - texstudio

Hi Johannes, as I'm experienced with Qt related stuff (member of KDE SIG too) and also use TeXStudio as my default TeX editor all day, I requested commit access now :) Greetings, Christian On 12/08/2016 05:36 PM, Johannes Lips wrote: Dear list, I would like to invite packagers with Qt

Re: Fedora captive portal page changed output :(

On lunes, 5 de diciembre de 2016 8:31:41 AM CST Michael Catanzaro wrote: > On Mon, 2016-12-05 at 09:05 -0500, Paul Wouters wrote: > > That is incorrect in my experience. When I go to coffee shops, my > > iphone > > shows the portal page, but my laptop shows the TLS cert invalid > > thing. > > Oh

Schedule for Friday's FESCo Meeting (2016-12-09)

Following is the list of topics that will be discussed in the FESCo meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-12-09 16:00 UTC' Links to all issues below

Re: future of official optical media support in Fedora

On 12/08/2016 08:22 AM, Dennis Gilmore wrote: On miércoles, 7 de diciembre de 2016 1:56:32 PM CST Mike Pinkerton wrote: On 6 Dec 2016, at 09:43, Kamil Paral wrote: Which images to cover, that's the heart of the discussion. If you look into our test matrix again, we currently block on 6 of

Re: Some preliminary Fedora 25 stats — and future release scheduling

On lunes, 5 de diciembre de 2016 9:47:43 AM CST Matthew Miller wrote: > The stats I get are about a week behind, which means I now have > information about the first week of the Fedora 25 release. See the > graph here: > > https://mattdm.fedorapeople.org/stats/fedora-os-select-2016-11-22.png > >

Looking for co-maintainers - texstudio

Dear list, I would like to invite packagers with Qt experience to become co-maintainer on the texstudio package. I am pretty occupied with my day job and won't have time to delve into all details of Qt linking, which are currently not working properly, when building the package for fedora >24.

Re: future of official optical media support in Fedora

On miércoles, 7 de diciembre de 2016 1:56:32 PM CST Mike Pinkerton wrote: > On 6 Dec 2016, at 09:43, Kamil Paral wrote: > > Which images to cover, that's the heart of the discussion. If you > > look into our test matrix again, we currently block on 6 of them: > > * Workstation Live + netinst > > *

Re: GSequencer upstream wants to package for fedora

On Thu, 8 Dec 2016 15:21:21 +0100, Joël Krähemann wrote: > My name is Joël Krähemann. I maintain Advanced Gtk+ Sequencer and I'd > like to provide it in fedora. Linux is my OS of choice since 2001. > Along the time I have used many distributions like debian, linux from > scratch, SUSE, fedora and

Re: Call to retire gstreamer-0.10

On 2016-12-07, Michael Cronenworth wrote: > perl-GStreamer > perl-GStreamer-Interfaces No problem. We have perl-GStreamer1 as a binding for the new API and no other package uses these two. -- Petr ___ devel mailing list --

  1   2   >