5:45 p.m.
Hi all,
In two weeks we will be entering the F22 Final Freeze. At that point,
Fedora release engineering retires any packages that still have broken
dependencies in the F22 tree.
Based on today's Branched report [1], we still have a number of unfixed
packages with broken dependencies (package maintainers BCC'd to this
email). Anything not fixed by 2015-05-11 from the list below is going to
be automatically retired:
Package (co)maintainers
========================================================
Sprog mjakubicek
aeskulap ankursinha, mrceresa, susmit
aunit landgraf
aws landgraf
bro fab, mildew
crystal bnemec, chitlesh
dnssec-check hardaker
dsqlite jouty
florist landgraf
gcc-python-plugin dmalcolm, jakub
gl3n cicku, bioinfornatics
gnatcoll landgraf
kde-style-skulpture jreznik
leksah petersen, haskell-sig
matreshka landgraf
newsx rathann, itamarjp
nifti2dicom dvratil
oozie rrati, coolsvap, moceap
opensips ivaxer, peter
python-sippy peter
quarticurve-kwin-theme kkofler
rss-glx nphilipp, cheese
rubygem-rugged tdawson
spring-maps-default gilboa
syntastic bioinfornatics, praiskup
tango bioinfornatics, cicku
templates_parser oenone, landgraf
vdr-streamdev heffer
vdr-vnsiserver3 bubeck
xavante timn
These are all leaf packages; no other package depends on them.
I've excluded odb-2.3.0-11.fc22, openchange-2.2-6.fc22,
rubygem-moped-1.5.2-5.fc22, zeromq-ada-2.1.0-17.24032011git.fc22 from
the list above; they all have fixes in updates-testing and just need
karma in Bodhi to go to stable.
[1] https://lists.fedoraproject.org/pipermail/devel/2015-April/210201.html
--
Kalev
8:22 p.m.
Kalev Lember wrote:
quarticurve-kwin-theme kkofler
This one can just go away, it would need to be ported to KWin 5 and I
probably won't be doing that port. (The KWin 4 version already renders worse
than intended on all current 4.x releases and I don't have much time to
spend on fixing that ancient codebase up. Quarticurve is a port of the
KDE/Qt version of the venerable old Bluecurve.)
Kevin Kofler
4:42 a.m.
On 04/28/2015 03:22 AM, Kevin Kofler wrote:
Kalev Lember wrote:
> quarticurve-kwin-theme kkofler
This one can just go away, it would need to be ported to KWin 5 and I
probably won't be doing that port. (The KWin 4 version already renders worse
than intended on all current 4.x releases and I don't have much time to
spend on fixing that ancient codebase up. Quarticurve is a port of the
KDE/Qt version of the venerable old Bluecurve.)
Thanks Kevin -- can you retire the package yourself in that case, so
that it drops off the broken deps report?
--
Kalev
3:16 a.m.
Dne 28.4.2015 v 00:45 Kalev Lember napsal(a):
rubygem-rugged tdawson
I am not maintainer of this, but please do not remove this. Rugged was
broken by unannounced libgit2 update and there is still not official
release fixing the compatibility. Removing this rubygem will mean just
more work for everybody involved.
Vít
4:35 a.m.
On 04/28/2015 10:16 AM, Vít Ondruch wrote:
Dne 28.4.2015 v 00:45 Kalev Lember napsal(a):
> rubygem-rugged tdawson
>
I am not maintainer of this, but please do not remove this. Rugged was
broken by unannounced libgit2 update and there is still not official
release fixing the compatibility. Removing this rubygem will mean just
more work for everybody involved.
libgit2 is at 0.22.2 and looks like there's a matching new Rugged
release at https://rubygems.org/gems/rugged/versions/0.22.1b1 and the
package just needs updating. I am not sure what's up with the
maintainer, but maybe you could help them out by comaintaining
rubygem-rugged?
When it comes to shipping F22, I don't think it makes sense to include a
package that is so horribly broken that it cannot even be installed. But
if you guys are actively working on fixing it, I am sure we can try and
convince releng to give it a few more days before blocking so that it
can be pulled in through the freeze through the FE process:
https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
Also, please note that Fedora policies allow adding new packages in the
updates repo, so even if something gets dropped now, it can always be
fixed and shipped in the updates repo at a later date.
--
Hope this helps,
Kalev
9:52 a.m.
Dne 28.4.2015 v 11:35 Kalev Lember napsal(a):
On 04/28/2015 10:16 AM, Vít Ondruch wrote:
> Dne 28.4.2015 v 00:45 Kalev Lember napsal(a):
>> rubygem-rugged tdawson
>>
> I am not maintainer of this, but please do not remove this. Rugged was
> broken by unannounced libgit2 update and there is still not official
> release fixing the compatibility. Removing this rubygem will mean just
> more work for everybody involved.
libgit2 is at 0.22.2 and looks like there's a matching new Rugged
release at https://rubygems.org/gems/rugged/versions/0.22.1b1 and the
package just needs updating. I am not sure what's up with the
maintainer, but maybe you could help them out by comaintaining
rubygem-rugged?
If you take a look on version history [1], you'll notice that the "b"
in version stands for beta. I have not checked with upstream what is the
plan, though.
[1] https://rubygems.org/gems/rugged/versions
When it comes to shipping F22, I don't think it makes sense to include a
package that is so horribly broken that it cannot even be installed. But
if you guys are actively working on fixing it, I am sure we can try and
convince releng to give it a few more days before blocking so that it
can be pulled in through the freeze through the FE process:
https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
Also, please note that Fedora policies allow adding new packages in the
updates repo, so even if something gets dropped now, it can always be
fixed and shipped in the updates repo at a later date.
Which means re-review ...
Vít
9:46 a.m.
Vít Ondruch wrote on 04/28/2015 11:52 PM:
Dne 28.4.2015 v 11:35 Kalev Lember napsal(a):
> On 04/28/2015 10:16 AM, Vít Ondruch wrote:
>> Dne 28.4.2015 v 00:45 Kalev Lember napsal(a):
>>> rubygem-rugged tdawson
>>>
>> I am not maintainer of this, but please do not remove this. Rugged was
>> broken by unannounced libgit2 update and there is still not official
>> release fixing the compatibility. Removing this rubygem will mean just
>> more work for everybody involved.
> libgit2 is at 0.22.2 and looks like there's a matching new Rugged
> release at https://rubygems.org/gems/rugged/versions/0.22.1b1 and the
> package just needs updating. I am not sure what's up with the
> maintainer, but maybe you could help them out by comaintaining
> rubygem-rugged?
If you take a look on version history [1], you'll notice that the "b"
in version stands for beta. I have not checked with upstream what is the
plan, though.
[1] https://rubygems.org/gems/rugged/versions
But this is branched as "maint/v0.22", and I think using this beta
is much preferable than to keep broken deps, thought?
By the way, I am not a maintainer of rubygem-rugged, either, and
I don't use rubygem-rugged (currently). Anyway I want to know
how the current maintainer think of the current status.
If the current maintainer has no interest on this package,
maybe it is better to get this retired.
>
> When it comes to shipping F22, I don't think it makes sense to include a
> package that is so horribly broken that it cannot even be installed. But
> if you guys are actively working on fixing it, I am sure we can try and
> convince releng to give it a few more days before blocking so that it
> can be pulled in through the freeze through the FE process:
> https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
>
> Also, please note that Fedora policies allow adding new packages in the
> updates repo, so even if something gets dropped now, it can always be
> fixed and shipped in the updates repo at a later date.
>
Which means re-review ...
Vít
Regards,
Mamoru
10:29 p.m.
On Mon, May 4, 2015 at 8:46 AM, Mamoru TASAKA <mtasaka(a)fedoraproject.org> wrote:
By the way, I am not a maintainer of rubygem-rugged, either, and
I don't use rubygem-rugged (currently). Anyway I want to know
how the current maintainer think of the current status.
If the current maintainer has no interest on this package,
maybe it is better to get this retired.
This package is in the dep chain for Gitlab so I'd really like to see
it stay in Fedora, personally.
I've applied for co-maintainership in pkgdb and I've updated
https://bugzilla.redhat.com/1166414 with a patch to get the package
building again for F22 and Rawhide.
- Ken
3:02 p.m.
On Mon, May 4, 2015 at 9:29 PM, Ken Dreyer <ktdreyer(a)ktdreyer.com> wrote:
On Mon, May 4, 2015 at 8:46 AM, Mamoru TASAKA
<mtasaka(a)fedoraproject.org> wrote:
> By the way, I am not a maintainer of rubygem-rugged, either, and
> I don't use rubygem-rugged (currently). Anyway I want to know
> how the current maintainer think of the current status.
> If the current maintainer has no interest on this package,
> maybe it is better to get this retired.
This package is in the dep chain for Gitlab so I'd really like to see
it stay in Fedora, personally.
I've applied for co-maintainership in pkgdb and I've updated
https://bugzilla.redhat.com/1166414 with a patch to get the package
building again for F22 and Rawhide.
Here's the update that fixes the broken dependency with libgit2:
https://admin.fedoraproject.org/updates/rubygem-rugged-0.22.1-0.1.b1.fc22
Thanks Peter Robinson, Peter Smith, and Pete Walter for providing
karma in Bodhi. You guys rock.
Do I need to do something with https://bugzilla.redhat.com/1166414 to
nominate it for a F22 freeze exception, or it'll be fine as-is?
- Ken
3:42 p.m.
On Tue, 2015-05-05 at 14:02 -0600, Ken Dreyer wrote:
On Mon, May 4, 2015 at 9:29 PM, Ken Dreyer
<ktdreyer(a)ktdreyer.com>
wrote:
> On Mon, May 4, 2015 at 8:46 AM, Mamoru TASAKA <
> mtasaka(a)fedoraproject.org> wrote:
> > By the way, I am not a maintainer of rubygem-rugged, either, and
> > I don't use rubygem-rugged (currently). Anyway I want to know
> > how the current maintainer think of the current status.
> > If the current maintainer has no interest on this package,
> > maybe it is better to get this retired.
>
> This package is in the dep chain for Gitlab so I'd really like to
> see
> it stay in Fedora, personally.
>
> I've applied for co-maintainership in pkgdb and I've updated
> https://bugzilla.redhat.com/1166414 with a patch to get the package
> building again for F22 and Rawhide.
Here's the update that fixes the broken dependency with libgit2:
https://admin.fedoraproject.org/updates/rubygem-rugged-0.22.1
-0.1.b1.fc22
Thanks Peter Robinson, Peter Smith, and Pete Walter for providing
karma in Bodhi. You guys rock.
Do I need to do something with https://bugzilla.redhat.com/1166414 to
nominate it for a F22 freeze exception, or it'll be fine as-is?
Final Freeze is 2015-05-12. Until then updates can be pushed stable
once they meet the usual karma/time requirements. These dates are in
the calendar system:
https://fedorapeople.org/groups/schedule/f-22/f-22-devel-tasks.html
it's really a good idea to keep that link handy.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
5:20 a.m.
On Tue, 2015-04-28 at 00:45 +0200, Kalev Lember wrote:
aeskulap ankursinha, mrceresa, susmit
I'm aware of this one. Was caused by an update in one of the libraries
aeskulap depends on. The problem is that aeskulap is quite an old
piece of software and hasn't been updated in a while. I'll try to see
if I can fix it, but I don't know much about the library so I can't
guarantee I'll succeed :/
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
http://fedoraproject.org/wiki/User:Ankursinha
5:51 a.m.
Kalev Lember <kalevlember(a)gmail.com> wrote:
In two weeks we will be entering the F22 Final Freeze. At that
point,
Fedora release engineering retires any packages that still have broken
dependencies in the F22 tree.
Do you mean that they'll be retired entirely, or just removed from the
F22 branch?
Package (co)maintainers
========================================================
aunit landgraf
aws landgraf
florist landgraf
gnatcoll landgraf
matreshka landgraf
templates_parser oenone, landgraf
I'm trying to get permission to help with these. Most of them look like
they just need to be rebuilt or can be fixed fairly easily.
Björn Persson
5:58 a.m.
On 04/28/2015 12:51 PM, Björn Persson wrote:
Kalev Lember <kalevlember(a)gmail.com> wrote:
> In two weeks we will be entering the F22 Final Freeze. At that point,
> Fedora release engineering retires any packages that still have broken
> dependencies in the F22 tree.
Do you mean that they'll be retired entirely, or just removed from the
F22 branch?
Both F22 and rawhide.
> Package (co)maintainers
> ========================================================
> aunit landgraf
> aws landgraf
> florist landgraf
> gnatcoll landgraf
> matreshka landgraf
> templates_parser oenone, landgraf
I'm trying to get permission to help with these. Most of them look like
they just need to be rebuilt or can be fixed fairly easily.
Excellent, thanks Björn.
--
Kalev
11:44 a.m.
On Tuesday, April 28, 2015 12:58:01 PM Kalev Lember wrote:
On 04/28/2015 12:51 PM, Björn Persson wrote:
> Kalev Lember <kalevlember(a)gmail.com> wrote:
>> In two weeks we will be entering the F22 Final Freeze. At that point,
>> Fedora release engineering retires any packages that still have broken
>> dependencies in the F22 tree.
>
> Do you mean that they'll be retired entirely, or just removed from the
> F22 branch?
Both F22 and rawhide.
That is they will be retired for f22 and up and removed from
the distro for
those and newer releases. So they will not be removed from the currently
active releases.
Dennis
4:15 p.m.
On Tue, Apr 28, 2015 at 11:51 AM, Björn Persson <Bjorn(a)xn--rombobjrn-67a.se> wrote:
Kalev Lember <kalevlember(a)gmail.com> wrote:
> In two weeks we will be entering the F22 Final Freeze. At that point,
> Fedora release engineering retires any packages that still have broken
> dependencies in the F22 tree.
Do you mean that they'll be retired entirely, or just removed from the
F22 branch?
> Package (co)maintainers
> ========================================================
> aunit landgraf
> aws landgraf
> florist landgraf
> gnatcoll landgraf
> matreshka landgraf
> templates_parser oenone, landgraf
I'm trying to get permission to help with these. Most of them look like
they just need to be rebuilt or can be fixed fairly easily.
I tried to rebuild some of the ada packages but they fail when linking
with libgnat5.1 (I think that's it, basically the new libgnat) so I
think there's more needed than just a rebuild, but happy to help push
fixes if it helps.
Peter
5:15 a.m.
Peter Robinson wrote:
On Tue, Apr 28, 2015 at 11:51 AM, Björn Persson
<Bjorn(a)xn--rombobjrn-67a.se>
wrote:
> Kalev Lember <kalevlember(a)gmail.com> wrote:
>> Package (co)maintainers
>> ========================================================
>> aunit landgraf
>> aws landgraf
>> florist landgraf
>> gnatcoll landgraf
>> matreshka landgraf
>> templates_parser oenone, landgraf
>
> I'm trying to get permission to help with these. Most of them look
> like they just need to be rebuilt or can be fixed fairly easily.
I tried to rebuild some of the ada packages but they fail when linking
with libgnat5.1 (I think that's it, basically the new libgnat) so I
think there's more needed than just a rebuild, but happy to help push
fixes if it helps.
Oh I see, there was an update of GPRbuild stuck in testing which Koji
doesn't use. That's why builds worked for me on malkin.scrye.com. I'm
not allowed to submit it as a buildroot override but I gave it a karma
point so it's on its way to stable now.
Meanwhile, there is a successfully built aunit-2013-8.fc22 in Koji.
Perhaps a privileged person could get that through Bodhi? I don't know
why Pavel hasn't submitted it, but it's not likely to be worse than an
uninstallable package.
Björn Persson
5:30 a.m.
On Wed, Apr 29, 2015 at 11:15 AM, Björn Persson <Bjorn(a)xn--rombobjrn-67a.se> wrote:
Peter Robinson wrote:
> On Tue, Apr 28, 2015 at 11:51 AM, Björn Persson <Bjorn(a)xn--rombobjrn-67a.se>
> wrote:
> > Kalev Lember <kalevlember(a)gmail.com> wrote:
> >> Package (co)maintainers
> >> ========================================================
> >> aunit landgraf
> >> aws landgraf
> >> florist landgraf
> >> gnatcoll landgraf
> >> matreshka landgraf
> >> templates_parser oenone, landgraf
> >
> > I'm trying to get permission to help with these. Most of them look
> > like they just need to be rebuilt or can be fixed fairly easily.
>
> I tried to rebuild some of the ada packages but they fail when linking
> with libgnat5.1 (I think that's it, basically the new libgnat) so I
> think there's more needed than just a rebuild, but happy to help push
> fixes if it helps.
Oh I see, there was an update of GPRbuild stuck in testing which Koji
doesn't use. That's why builds worked for me on malkin.scrye.com. I'm
not allowed to submit it as a buildroot override but I gave it a karma
point so it's on its way to stable now.
I'll have a look at it all now.
Meanwhile, there is a successfully built aunit-2013-8.fc22 in Koji.
Perhaps a privileged person could get that through Bodhi? I don't know
why Pavel hasn't submitted it, but it's not likely to be worse than an
uninstallable package.
I'll review that now too.
Peter
8:41 a.m.
> > Kalev Lember <kalevlember(a)gmail.com> wrote:
> >> Package (co)maintainers
> >> ========================================================
> >> aunit landgraf
> >> aws landgraf
> >> florist landgraf
> >> gnatcoll landgraf
> >> matreshka landgraf
> >> templates_parser oenone, landgraf
> >
> > I'm trying to get permission to help with these. Most of them look
> > like they just need to be rebuilt or can be fixed fairly easily.
>
> I tried to rebuild some of the ada packages but they fail when linking
> with libgnat5.1 (I think that's it, basically the new libgnat) so I
> think there's more needed than just a rebuild, but happy to help push
> fixes if it helps.
Oh I see, there was an update of GPRbuild stuck in testing which Koji
doesn't use. That's why builds worked for me on malkin.scrye.com. I'm
not allowed to submit it as a buildroot override but I gave it a karma
point so it's on its way to stable now.
I've dealt with that, pretty much all are rebuilt now. I'm having issues with:
aws
gnatcoll
matreshka
All of which have issues other than gnat 5. If you could have a look
at those and if you need help getting them built/submitted reach out
to me on email/IRC and I'll help get the the fixes built/landed. All
the dependencies are in the f22-override for the next day or so.
Meanwhile, there is a successfully built aunit-2013-8.fc22 in Koji.
Perhaps a privileged person could get that through Bodhi? I don't know
why Pavel hasn't submitted it, but it's not likely to be worse than an
uninstallable package.
I rebuilt everything else and submitted them as an update [1] to bodhi
so we should have the majority of the gnat5 dependants on their way to
stable now, please test and provide karma.
[1]
https://admin.fedoraproject.org/updates/aunit-2013-9.fc22,florist-2011-17...
7:30 a.m.
Peter Robinson <pbrobinson(a)gmail.com> wrote:
I'm having issues with:
aws
gnatcoll
matreshka
All of which have issues other than gnat 5. If you could have a look
at those and if you need help getting them built/submitted reach out
to me on email/IRC and I'll help get the the fixes built/landed. All
the dependencies are in the f22-override for the next day or so.
Thanks to the override of Templates Parser I could figure out the
problem with AWS. When I tried to scratch-build the fix the override had
already expired, but I think this patch should fix it.
Björn Persson
8:26 a.m.
On Thu, Apr 30, 2015 at 1:30 PM, Björn Persson <Bjorn(a)xn--rombobjrn-67a.se> wrote:
Peter Robinson <pbrobinson(a)gmail.com> wrote:
> I'm having issues with:
> aws
> gnatcoll
> matreshka
>
> All of which have issues other than gnat 5. If you could have a look
> at those and if you need help getting them built/submitted reach out
> to me on email/IRC and I'll help get the the fixes built/landed. All
> the dependencies are in the f22-override for the next day or so.
Thanks to the override of Templates Parser I could figure out the
problem with AWS. When I tried to scratch-build the fix the override had
already expired, but I think this patch should fix it.
That built, update submitted, just gnatcoll and matreshka to go.
P
4:13 p.m.
Peter Robinson wrote:
That built, update submitted, just gnatcoll and matreshka to go.
OK, here we go:
· one patch to Gnatcoll for GCC 5
· one patch to Matreshka for GCC 5
· another patch to build Matreshka in spite of bug 1151793
· one fix to GPRbuild that is needed before Matreshka can be built
· and a better workaround for the libgnat version issue that really
should get in before the release.
Björn Persson
9:48 a.m.
On Sat, May 2, 2015 at 10:13 PM, Björn Persson <Bjorn(a)xn--rombobjrn-67a.se> wrote:
Peter Robinson wrote:
> That built, update submitted, just gnatcoll and matreshka to go.
OK, here we go:
· one patch to Gnatcoll for GCC 5
· one patch to Matreshka for GCC 5
· another patch to build Matreshka in spite of bug 1151793
· one fix to GPRbuild that is needed before Matreshka can be built
· and a better workaround for the libgnat version issue that really
should get in before the release.
All of those are now built, also fixed up rawhide too
4:39 p.m.
Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Sat, May 2, 2015 at 10:13 PM, Björn Persson
<Bjorn(a)xn--rombobjrn-67a.se> wrote:
> OK, here we go:
> · one patch to Gnatcoll for GCC 5
> · one patch to Matreshka for GCC 5
> · another patch to build Matreshka in spite of bug 1151793
> · one fix to GPRbuild that is needed before Matreshka can be built
> · and a better workaround for the libgnat version issue that really
> should get in before the release.
All of those are now built, also fixed up rawhide too
Thanks for all your help. I don't yet see the fixed GPRbuild in Bodhi
though. Did you mean to submit that?
Björn Persson
4:49 p.m.
On Mon, May 4, 2015 at 10:39 PM, Björn Persson <Bjorn(a)xn--rombobjrn-67a.se> wrote:
Peter Robinson <pbrobinson(a)gmail.com> wrote:
> On Sat, May 2, 2015 at 10:13 PM, Björn Persson <Bjorn(a)xn--rombobjrn-67a.se> wrote:
> > OK, here we go:
> > · one patch to Gnatcoll for GCC 5
> > · one patch to Matreshka for GCC 5
> > · another patch to build Matreshka in spite of bug 1151793
> > · one fix to GPRbuild that is needed before Matreshka can be built
> > · and a better workaround for the libgnat version issue that really
> > should get in before the release.
>
> All of those are now built, also fixed up rawhide too
Thanks for all your help. I don't yet see the fixed GPRbuild in Bodhi
though. Did you mean to submit that?
Oops, gprbuild-2014-5.fc22 added now
7:09 a.m.
oozie rrati, coolsvap, moceap
This break occurred because of a very late change (April 22) to enable
building/running the hadoop ecosystem on ARM. A dependency broke during
that set of changes and will need to be looked at. I don't think this
package should be retired if it is not able to be fixed by the requested
date. It is only broken on ARM. If this isn't fixed soon then the
packages should just revert to not building on ARM.
Rob
9:19 a.m.
On Tue, Apr 28, 2015 at 1:09 PM, Robert Rati <rrati(a)redhat.com> wrote:
> oozie rrati, coolsvap, moceap
This break occurred because of a very late change (April 22) to enable
building/running the hadoop ecosystem on ARM. A dependency broke during
that set of changes and will need to be looked at. I don't think this
package should be retired if it is not able to be fixed by the requested
date. It is only broken on ARM. If this isn't fixed soon then the packages
should just revert to not building on ARM.
Actually that change didn't break it, but it can't currently rebuilt
because pig is FTBFS on all architectures, AFAICT it's due to a hbase
rebase [1]
[1] https://kojipkgs.fedoraproject.org//work/tasks/6065/9536065/build.log
12:44 p.m.
The broken oozie dep is only on the arm architecture. There were no
previous builds of oozie/pig/etc on arm prior to this change so there
were no F21 arm packages to fall back on. From my perspective the
change to enable building/running on arm is the cause of the issue for
oozie (but not pig).
hbase hasn't been rebased since the 0.98.3 that was in F21 afaik so I'm
not sure why you say that is the root of the problem. From the pig logs
hbase 0.98.3-3 is installed but the resolution fails in the pig build.
pig hasn't been built since F21 so it's possible something in xmvn
changed in F22 that is causing resolutions problems in the pig build.
The root cause of the pig FTBFS seems to be a resolution problem for
hbase in the pig build.
IMO this was a rather significant change to enable this late in the
release cycle.
Rob
On 04/28/2015 10:19 AM, Peter Robinson wrote:
On Tue, Apr 28, 2015 at 1:09 PM, Robert Rati <rrati(a)redhat.com>
wrote:
>> oozie rrati, coolsvap, moceap
>
>
> This break occurred because of a very late change (April 22) to enable
> building/running the hadoop ecosystem on ARM. A dependency broke during
> that set of changes and will need to be looked at. I don't think this
> package should be retired if it is not able to be fixed by the requested
> date. It is only broken on ARM. If this isn't fixed soon then the packages
> should just revert to not building on ARM.
Actually that change didn't break it, but it can't currently rebuilt
because pig is FTBFS on all architectures, AFAICT it's due to a hbase
rebase [1]
[1] https://kojipkgs.fedoraproject.org//work/tasks/6065/9536065/build.log
4:24 a.m.
leksah petersen, haskell-sig
Yes, this needs 8 new dependencies which I haven't
had time to post reviews for yet:
https://bugzilla.redhat.com/show_bug.cgi?id=1074907#c18
leksah is a Haskell IDE - I don't use it myself or
know many people who do, but if someone is willing
to help get the reviews done quickly I am happy
to keep it alive in Fedora, otherwise maybe it can go
to Copr.
Cheers, Jens
4:51 a.m.
On Tuesday, 28 April 2015 at 00:45, Kalev Lember wrote:
Hi all,
In two weeks we will be entering the F22 Final Freeze. At that point,
Fedora release engineering retires any packages that still have broken
dependencies in the F22 tree.
Based on today's Branched report [1], we still have a number of unfixed
packages with broken dependencies (package maintainers BCC'd to this
email). Anything not fixed by 2015-05-11 from the list below is going to
be automatically retired:
Package (co)maintainers
========================================================
[...]
newsx rathann, itamarjp
Broken dep caused by INN update.
Fixed in https://admin.fedoraproject.org/updates/FEDORA-2015-7024.
Regards,
--
Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu
"Faith manages."
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
3276
days inactive
3284
days old
29 comments
14 participants
participants (14)
-
Adam Williamson -
Ankur Sinha -
Björn Persson -
Dennis Gilmore -
Dominik 'Rathann' Mierzejewski -
Jens-Ulrik Petersen -
Kalev Lember -
Ken Dreyer -
Kevin Kofler -
Mamoru TASAKA -
Peter Lemenkov -
Peter Robinson -
Robert Rati -
Vít Ondruch