Re: Rapid release for security updates

I totally agree with Jared, just becuase oyu don't see the logic doesn't mean it needs repealed. Corey W Sheldon Freelance IT Consultant, Multi-Discipline Tutor (p) 310.909.7672 G+: LinkedIn: Github:

Re: Rapid release for security updates

On Tue, May 19, 2015 at 8:20 AM, Kevin Kofler wrote: > The "update stability policies" enforced by Bodhi simply need to be > repealed. > I completely disagree... the checks and balances that are in place are there for a reason, and aren't too difficult to satisfy in the case of a security update

Orphaned Packages in rawhide (2015-05-19)

The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If y

Re: F23 System Wide Change: Mono 4

On Tue, May 19, 2015 at 2:36 AM, Peter Robinson wrote: > On Mon, May 18, 2015 at 4:52 AM, Moez Roy wrote: >> Mono is updated in Rawhide. Can a proven-packager run a script to >> rebuild all the packages that require mono. > > Most of these are now built, sadly because all the bits needed weren't

Re: Rapid release for security updates

Martin Stransky wrote: > is there any mechanism how to speed up release of critical security > fixes by Fedora update system? > > For instance Firefox packages are released *week* after official Mozilla > release which is really bad. > > Any idea here? The "update stability policies" enforced by

Fedora 22 Final Release Readiness Meeting :: Thursday, May 21, 19:00 UTC

Fedora 22 Final Release Readiness Meeting. date: 2015-05-21 place: irc.freenode.net in #fedora-meeting-2 time: 19:00 UTC (3 PM EDT, 12 noon PDT, 21:00 CEST) This Thursday, May 21, we will meet to make sure we are coordinated and ready for the Final release of Fedora 22 on Tuesday, May 26, 2015. P

Re: simplestreams json or index.asc for deliverables in the new list-of-deliverables?

On 05/18/2015 07:44 PM, Matthew Miller wrote: That way, we'd have a standardized way for applications to find and download/launch/whatever various Fedora images. This is a definite need (see https://fedorahosted.org/cloud/ticket/93) and rather than inventing a new wheel, maybe we could see if we

F-22 Branched report: 20150519 changes

Compose started at Tue May 19 07:15:03 UTC 2015 Broken deps for armhfp -- [xorg-x11-drivers] xorg-x11-drivers-7.7-13.fc22.armv7hl requires xorg-x11-drv-void Broken deps for i386 --

Re: simplestreams json or index.asc for deliverables in the new list-of-deliverables?

On 19/05/15 09:05 -0400, Fabian Deutsch wrote: - Original Message - On Mon, 18.05.15 19:44, Matthew Miller (mat...@fedoraproject.org) wrote: > FESCo Ticket #1427 > formalizes the list of deliverables for each Fedora release. Cool. > > Let's g

Re: Rapid release for security updates

On Tue, May 19, 2015 at 9:24 AM, Martin Stransky wrote: > On 05/19/2015 03:17 PM, Michael Cronenworth wrote: >> >> On 05/19/2015 04:12 AM, drago01 wrote: >>> >>> Why does it take so long? Most firefox uipdates get enough karma >>> before they end up in testing. >>> In that case they should be pick

Re: Rapid release for security updates

On 05/19/2015 11:12 AM, drago01 wrote: On Tue, May 19, 2015 at 10:38 AM, Martin Stransky wrote: Hi guys, is there any mechanism how to speed up release of critical security fixes by Fedora update system? For instance Firefox packages are released *week* after official Mozilla release which is

Re: Rapid release for security updates

On 05/19/2015 03:17 PM, Michael Cronenworth wrote: On 05/19/2015 04:12 AM, drago01 wrote: Why does it take so long? Most firefox uipdates get enough karma before they end up in testing. In that case they should be picked up by the next push (which is still a manual process afaik; so no idea how

Re: Rapid release for security updates

On 05/19/2015 04:12 AM, drago01 wrote: Why does it take so long? Most firefox uipdates get enough karma before they end up in testing. In that case they should be picked up by the next push (which is still a manual process afaik; so no idea how often it happens). Firefox 38.0 entered and exited

Re: simplestreams json or index.asc for deliverables in the new list-of-deliverables?

- Original Message - > On Mon, 18.05.15 19:44, Matthew Miller (mat...@fedoraproject.org) wrote: > > > FESCo Ticket #1427 > > formalizes the list of deliverables for each Fedora release. Cool. > > > > Let's go a step beyond this and make a machi

Re: simplestreams json or index.asc for deliverables in the new list-of-deliverables?

On Mon, 18.05.15 19:44, Matthew Miller (mat...@fedoraproject.org) wrote: > FESCo Ticket #1427 > formalizes the list of deliverables for each Fedora release. Cool. > > Let's go a step beyond this and make a machine-readable list, at least > of image-bas

rawhide report: 20150519 changes

Compose started at Tue May 19 05:15:03 UTC 2015 Broken deps for i386 -- [InsightToolkit] InsightToolkit-4.7.1-4.fc23.i686 requires libhdf5_cpp.so.9 InsightToolkit-4.7.1-4.fc23.i686 requires libhdf5.so.9 [OpenTK] OpenTK-

Fedora 22 Final Go/No-Go Meeting, Thursday, May 21 @ 17:00 UTC

Join us on irc.freenode.net in #fedora-meeting-2 for this important meeting, wherein we shall determine the readiness of the Fedora 22. Thursday, May 21, 2015 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST) "Before each public release Development, QA and Release Engineering meet to determine if the r

Re: F23 System Wide Change: Mono 4

On Mon, May 18, 2015 at 4:52 AM, Moez Roy wrote: > Mono is updated in Rawhide. Can a proven-packager run a script to > rebuild all the packages that require mono. Most of these are now built, sadly because all the bits needed weren't actually committed it wasn't as simple as running a script. Th

Re: Rapid release for security updates

On Tue, May 19, 2015 at 10:38 AM, Martin Stransky wrote: > Hi guys, > > is there any mechanism how to speed up release of critical security fixes by > Fedora update system? > > For instance Firefox packages are released *week* after official Mozilla > release which is really bad. > > Any idea here

Re: F23 System Wide Change: Mono 4

Hello Neal, > So we won't have mono stuff working for F22 then? I have installed a fresh Fedora 21, and then upgraded to F22 according to https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_21_-.3E_Fedora_22_.28not_yet_released.29 I then did dnf install mono-core. rpm -qa | grep m

Re: Rapid release for security updates

Am 19.05.2015 um 10:38 schrieb Martin Stransky: Hi guys, is there any mechanism how to speed up release of critical security fixes by Fedora update system? For instance Firefox packages are released *week* after official Mozilla release which is really bad. Any idea here? and that is *real

Re: simplestreams json or index.asc for deliverables in the new list-of-deliverables?

- Original Message - > FESCo Ticket #1427 > formalizes the list of deliverables for each Fedora release. Cool. > > Let's go a step beyond this and make a machine-readable list, at least > of image-based deliverables. One approach would be to use

Rapid release for security updates

Hi guys, is there any mechanism how to speed up release of critical security fixes by Fedora update system? For instance Firefox packages are released *week* after official Mozilla release which is really bad. Any idea here? ma. -- devel mailing list devel@lists.fedoraproject.org https://a