The following Fedora EPEL 7 Security updates need testing:
Age URL
175 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3835d39d1a
unrtf-0.21.9-8.el7
126 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-f9d6ff695a
bibutils-6.6-1.el7 ghc-hs-bibutils-6.6.0.0-1.el7
On Sat, 2018-12-01 at 10:12 -0500, Nico Kadel-Garcia wrote:
> On Sat, Dec 1, 2018 at 6:59 AM Frank Crawford
> wrote:
>
> On Sat, 2018-12-01 at 11:38 +, Zbigniew Jędrzejewski-Szmek wrote:
>
> On Sat, Dec 01, 2018 at 10:14:14PM +1100, Frank Crawford wrote:
>
> On Fri, 2018-11-30 at 14:15
On Sat, Dec 1, 2018 at 10:24 AM Stephen John Smoogen wrote:
>
> On Sat, 1 Dec 2018 at 08:50, Nico Kadel-Garcia wrote:
> >
> > Folks, hi.
> >
> > Planning for a specific delay for a specific reason is one thing. But
> > the same design philosophy reasons that apply to Fedora 31 have
> > applied
On Friday, 30 November 2018 at 14:15, Miro Hrončok wrote:
> 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:
>
On Mon, 26 Nov 2018 at 14:44, Tom Callaway wrote:
>
> Just checking in on this again, still need this update to build Chromium
> for EPEL7.
>
Sorry for the delay.. I spent some time looking for a new repository
tree and it turns out they put it in the regular ones.
So everyone needing newer
https://bugzilla.redhat.com/show_bug.cgi?id=1652477
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In
On Tue, Nov 27, 2018 at 7:59 AM Owen Taylor wrote:
>
> A lot of discussion about improving the compose process seem to end up
> with a "reality check" - that ideas have already been tried but don't
> work because of requirements a) b) c) d). You can't have the pony, but
> maybe if a lot of effort
On 11/29/18 10:08 AM, Igor Gnatenko wrote:
And it's in rawhide.
FYI: Kodi links against 'tinyxml' and not 'tinyxml2'.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
No missing expected images.
Failed openQA tests: 16/142 (x86_64), 3/24 (i386), 1/2 (arm)
New failures (same test did not fail in Rawhide-20181130.n.0):
ID: 314638 Test: x86_64 Server-dvd-iso realmd_join_sssd
URL: https://openqa.fedoraproject.org/tests/314638
ID: 314641 Test: x86_64
On Sat, 1 Dec 2018 at 08:50, Nico Kadel-Garcia wrote:
>
> Folks, hi.
>
> Planning for a specific delay for a specific reason is one thing. But
> the same design philosophy reasons that apply to Fedora 31 have
> applied to almost every other Fedora releases, and changing to an
> annual cycle is
On Sat, Dec 1, 2018 at 6:59 AM Frank Crawford wrote:
>
> On Sat, 2018-12-01 at 11:38 +, Zbigniew Jędrzejewski-Szmek wrote:
>
> On Sat, Dec 01, 2018 at 10:14:14PM +1100, Frank Crawford wrote:
>
> On Fri, 2018-11-30 at 14:15 +0100, Miro Hrončok wrote:
>
>
> Anyone know why this was orphaned?
Folks, hi.
Planning for a specific delay for a specific reason is one thing. But
the same design philosophy reasons that apply to Fedora 31 have
applied to almost every other Fedora releases, and changing to an
annual cycle is going to drive people *nuts* when updates for their
particular
OLD: Fedora-Rawhide-20181130.n.0
NEW: Fedora-Rawhide-20181201.n.0
= SUMMARY =
Added images:2
Dropped images: 5
Added packages: 11
Dropped packages:0
Upgraded packages: 64
Downgraded packages: 0
Size of added packages: 1.46 MiB
Size of dropped packages:0 B
On Sat, 2018-12-01 at 11:38 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Sat, Dec 01, 2018 at 10:14:14PM +1100, Frank Crawford wrote:
> On Fri, 2018-11-30 at 14:15 +0100, Miro Hrončok wrote:
>
> Anyone know why this was orphaned? There doesn't seem to be any
> message about it.
>
> s3cmd
On Sat, Dec 01, 2018 at 10:14:14PM +1100, Frank Crawford wrote:
> On Fri, 2018-11-30 at 14:15 +0100, Miro Hrončok wrote:
>
> Anyone know why this was orphaned? There doesn't seem to be any
> message about it.
>
> > s3cmd orphan 0 weeks ago
>
> If no one has any idea I'm willing to take it on.
On Fri, 2018-11-30 at 14:15 +0100, Miro Hrončok wrote:
Anyone know why this was orphaned? There doesn't seem to be any
message about it.
> s3cmd orphan 0 weeks ago
If no one has any idea I'm willing to take it on.
Regards
Frank
___
devel mailing
16 matches
Mail list logo