Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Jared K. Smith]

On Mon, Jun 12, 2017 at 6:38 PM,  wrote:

> asterisk   jsmith, gtjoseph, itamarjp,83 weeks ago
>lbazan, russellb
>
>
I'm actively working on fixing up Asterisk -- it took a while to get
systemd support back into dahdi-tools and get it unorphaned.  Now, I'm
running into a problem where Asterisk won't build on s390x.  See
https://koji.fedoraproject.org/koji/taskinfo?taskID=20012396.  That, in
turn, is probably going to mean pulling in a newer version of pjproject,
which has it's own issues on non x86_64 arches (see
https://koji.fedoraproject.org/koji/taskinfo?taskID=20014157).

I'm hoping to get this all sorted out in the next few days.

--
Jared Smith
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Petr Pisar]

On 2017-06-13, Petr Pisar  wrote:
> On 2017-06-13, Pavel Raiskup  wrote:
>>> vim-syntastic  praiskup   38
>>> weeks ago  
>>
>> Please don't remove this set of vim-syntastic* packages, there's
>> nothing to do about this.  Once we have fixed release engineering
>> processes [1] that allow me to ExcludeArch/ExclusiveArch particular
>> **sub**packages, I'll do so.  Thanks!
>>
>> [1] https://pagure.io/pungi-fedora/issue/87
>>
> perl-Alien-ROOT is the same case .
> The package is fine, but releng scripts cannot deal with it.
>
I made the package architecture specific. But I'm not happy with it.

-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Pavel Raiskup]

On Friday, June 16, 2017 12:23:58 AM CEST Jason L Tibbitts III wrote:
> > "PR" == Pavel Raiskup  writes:
> 
> PR> But I would be OK with this solution - if this idea was baked into
> PR> guidelines first.  Is it realistic to ratify new guidelines
> PR> paragraph for this issue before F26?
> 
> The packaging committee can certainly get guideline changes implemented
> pretty quickly when there's consensus.  But honestly I don't believe
> this isn't for FPC to change, and I wouldn't anticipate FPC making any
> alterations in this area without buy-in from FESCo and release
> engineering first.

Uh, what a long-shot, tiring issue for me!  Giving it the last chance [1].
If I can help to FPC/rel-eng with fixing guidelines/processes, let me
know.

If there's some packager volunteering for the maintenance of
vim-syntastic, please ping me.  I'll otherwise move the package to copr
(for mostly personal usecase) once the package is "garbage collected".
Thanks for understanding.

[1] https://pagure.io/packaging-committee/issue/691

Pavel

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Jason L Tibbitts III]

> "PR" == Pavel Raiskup  writes:

PR> But I would be OK with this solution - if this idea was baked into
PR> guidelines first.  Is it realistic to ratify new guidelines
PR> paragraph for this issue before F26?

The packaging committee can certainly get guideline changes implemented
pretty quickly when there's consensus.  But honestly I don't believe
this isn't for FPC to change, and I wouldn't anticipate FPC making any
alterations in this area without buy-in from FESCo and release
engineering first.

 - J<
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Pavel Raiskup]

On Wednesday, June 14, 2017 11:38:38 PM CEST Till Maas wrote:
> On Wed, Jun 14, 2017 at 04:20:25PM +0200, Pavel Raiskup wrote:
> > On Tuesday, June 13, 2017 2:26:33 PM CEST Petr Pisar wrote:
> > > On 2017-06-13, Pavel Raiskup  wrote:
> > > >> vim-syntastic  praiskup   38
> > > >> weeks ago  
> > > >
> > > > Please don't remove this set of vim-syntastic* packages, there's
> > > > nothing to do about this.  Once we have fixed release engineering
> > > > processes [1] that allow me to ExcludeArch/ExclusiveArch particular
> > > > **sub**packages, I'll do so.  Thanks!
> > > >
> > > > [1] https://pagure.io/pungi-fedora/issue/87
> > > >
> > > perl-Alien-ROOT is the same case .
> > > The package is fine, but releng scripts cannot deal with it.
> > 
> > It is really unfortunate...
> > 
> > ... so because only one particular subpackage (which otherwise perfectly
> > working, noarch thingy) can't have satisfied dependencies on only one of
> > many supported architectures -> are going to drop the entire package (all
> > subpackages) from Fedora, I mean entirely?
> > 
> > Till, what's the action plan for this?  Will you update the
> > removal-candidate-list somehow?
> 
> Given the current limitations of our tooling I understand that the
> corect thing to do would be to:
> 
> 1) make vim-syntastic a not-noarch package
> 2) Use %ifarch/%ifnarch conditionals to enable/disable subpackages depending 
> on the
> arches they are properly supported/not-supported.
> 
> Unfortunately this means extra work for you but it seems to be the work
> that is required for packaging vim-syntastic and providing a user
> experience without any broken dependencies in our stable release.
> I agree that it would be nicer to be able to just make the package
> noarch and just do not ship the subpackages that are not supported on
> the respective arch but I do not see how we will get there until the F26
> final release.

Meh, it wouldn't hurt anyone if we shipped not-installable "leaf" noarch
package, based on "whitelist" e.g. (only untill we have a fix for the tooling).

But I would be OK with this solution - if this idea was baked into guidelines
first.  Is it realistic to ratify new guidelines paragraph for this issue before
F26?

That's because (a) switching 'noarch' to arch-specific package is really
cumbersome and misleading, and some people might refuse to even think about it
(as I did, I considered this unacceptable at the beginning).  (b) Also we need
to have some banner for the people who take care of the tooling -- when you say
in guidelines that the noarch->arch-dependent switch is temporary hack, somebody
might be motivated enough to fix the issue finally.

Pavel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Till Maas]

On Wed, Jun 14, 2017 at 04:20:25PM +0200, Pavel Raiskup wrote:
> On Tuesday, June 13, 2017 2:26:33 PM CEST Petr Pisar wrote:
> > On 2017-06-13, Pavel Raiskup  wrote:
> > >> vim-syntastic  praiskup   38
> > >> weeks ago  
> > >
> > > Please don't remove this set of vim-syntastic* packages, there's
> > > nothing to do about this.  Once we have fixed release engineering
> > > processes [1] that allow me to ExcludeArch/ExclusiveArch particular
> > > **sub**packages, I'll do so.  Thanks!
> > >
> > > [1] https://pagure.io/pungi-fedora/issue/87
> > >
> > perl-Alien-ROOT is the same case .
> > The package is fine, but releng scripts cannot deal with it.
> 
> It is really unfortunate...
> 
> ... so because only one particular subpackage (which otherwise perfectly
> working, noarch thingy) can't have satisfied dependencies on only one of
> many supported architectures -> are going to drop the entire package (all
> subpackages) from Fedora, I mean entirely?
> 
> Till, what's the action plan for this?  Will you update the
> removal-candidate-list somehow?

Given the current limitations of our tooling I understand that the
corect thing to do would be to:

1) make vim-syntastic a not-noarch package
2) Use %ifarch/%ifnarch conditionals to enable/disable subpackages depending on 
the
arches they are properly supported/not-supported.

Unfortunately this means extra work for you but it seems to be the work
that is required for packaging vim-syntastic and providing a user
experience without any broken dependencies in our stable release.
I agree that it would be nicer to be able to just make the package
noarch and just do not ship the subpackages that are not supported on
the respective arch but I do not see how we will get there until the F26
final release.


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Pavel Raiskup]

On Tuesday, June 13, 2017 2:26:33 PM CEST Petr Pisar wrote:
> On 2017-06-13, Pavel Raiskup  wrote:
> >> vim-syntastic  praiskup   38
> >> weeks ago  
> >
> > Please don't remove this set of vim-syntastic* packages, there's
> > nothing to do about this.  Once we have fixed release engineering
> > processes [1] that allow me to ExcludeArch/ExclusiveArch particular
> > **sub**packages, I'll do so.  Thanks!
> >
> > [1] https://pagure.io/pungi-fedora/issue/87
> >
> perl-Alien-ROOT is the same case .
> The package is fine, but releng scripts cannot deal with it.

It is really unfortunate...

... so because only one particular subpackage (which otherwise perfectly
working, noarch thingy) can't have satisfied dependencies on only one of
many supported architectures -> are going to drop the entire package (all
subpackages) from Fedora, I mean entirely?

Till, what's the action plan for this?  Will you update the
removal-candidate-list somehow?

Pavel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Michael Schwendt]

On Mon, 12 Jun 2017 22:38:11 + (UTC), till fedoraproject org wrote:

> eflspot, dchen, sereinit  114 weeks ago 

>   audacious-plugins (maintained by: mschwendt, atkac, danfruehauf)
>   audacious-plugins-jack-3.8.2-2.fc26.i686 requires libjack.so.0

> mschwendt: efl

???

Big head scratcher here again.

Can anything be done to make this report more clear, please?
Why the heck am I listed for "efl"?

Seems it's only at the end of a depchain and affecting libjack:

>   jack-audio-connection-kit (maintained by: bsjones, nphilipp, oget)
>   jack-audio-connection-kit-1.9.10-8.fc26.i686 requires 
> libffado.so.2

>   libffado (maintained by: bsjones, nphilipp)
>   ffado-2.3.0-2.fc26.i686 requires libdbus-c++-1.so.0

> Depending on: efl (104), status change: 2015-04-02 (114 weeks ago)
>   dbus-c++ (maintained by: drago01)
>   dbus-c++-0.9.0-13.fc26.src requires ecore-devel = 1.19.0-4.fc26
>   dbus-c++-ecore-0.9.0-13.fc26.i686 requires
>   libecore.so.1, libefl.so.1
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Till Maas]

On Mon, Jun 12, 2017 at 04:12:04PM -0700, Adam Williamson wrote:

> Oh, I see the problem now, though it doesn't explain the '73 weeks
> ago':

The 73 weeks relates to the state in pkgdb and I should have removed it
from the report. It is not useful here. :-/

> 
> [os-autoinst]
> os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.armv7hl 
> requires openvswitch
> [os-autoinst]
> os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.ppc64 requires 
> openvswitch
> 
> so the problem is that the current stable openvswitch was not built for
> two arches; the openvswitch package currently in updates-testing *is*
> built for those arches, however. It seems pointless to send out an
> update that disables the subpackage for two arches for a few days until
> openvswitch is pushed stable.

As long as all updates are stable for the Final Freeze to fix the broken
deps there should be no problem.

> Perhaps the proliferation of arches in primary Koji might cause a
> rethink of how this automatic retirement works? It wouldn't seem to be
> a good idea to automatically retire this package (which is in fact
> quite important, and under active maintenance) on this basis.

It sounds like several broken deps will be resolved, soon, so there will
be a different picture. Since we only do up to two cleanups a year for
broken deps, it would a good chance to at least add proper
ExcludeArch/ExclusiveArch tags to packages that we cannot fix for the
Final Freeze. If this is not possible I am sure we will find a solution
that does not require to retire well-maintained packages.

Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Till Maas]

On Tue, Jun 13, 2017 at 11:52:05AM +1000, Peter Hutterer wrote:
> On Mon, Jun 12, 2017 at 03:47:48PM -0700, Josh Stone wrote:
> > On 06/12/2017 03:38 PM, t...@fedoraproject.org wrote:
> > > lldb   airlied, daveisfera,   71 weeks 
> > > ago  
> > >jankratochvil, jvcelak,
> > >   
> > >siddharths, tstellar   
> > >   
> > 
> > Where does that 71 weeks come from?  The lldb-3.9.1-4.fc26 reported
> > below was just in March, not to mention lldb-4.0.0-1.fc26 on May 12.
> 
> not to mention that this lldb issue breaks rust which in turn breaks meson
> which in turn breaks anything using meson. I'm going out on a limb here and
> assume that packages using rust and meson are not necessarily EOL'd :)

lldb seems to be broken on aarch64, i686, x86_64 and armv7hl because of
unsatisfied dependencies for clang and llvm-libs. But I guess it will be
fixed once
https://bodhi.fedoraproject.org/updates/FEDORA-2017-10971fa7a7
will be properly in F26 stable.

Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Till Maas]

On Mon, Jun 12, 2017 at 03:47:48PM -0700, Josh Stone wrote:
> On 06/12/2017 03:38 PM, t...@fedoraproject.org wrote:
> > lldb   airlied, daveisfera,   71 weeks ago  
> >jankratochvil, jvcelak,  
> >siddharths, tstellar 
> 
> Where does that 71 weeks come from?  The lldb-3.9.1-4.fc26 reported
> below was just in March, not to mention lldb-4.0.0-1.fc26 on May 12.

Sorry for the confusion. The status change is an artifact from using the
script for finding long-time orphaned packages and states the time for
the last owner change in pkgdb. For this report it would be better if I
removed it.

Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Rex Dieter]

Guido Aulisi wrote:

>  So a dependency on a subpackage is affecting the entire package,
> is this true?

Yes

-- Rex
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Guido Aulisi]

Il giorno mar, 13/06/2017 alle 19.12 +0200, Till Maas ha scritto:
> On Tue, Jun 13, 2017 at 11:14:37AM +0200, Guido Aulisi wrote:
> 
> > This is going to break all audio applications in Fedora, because
> > jack-
> > audio-connection-kit is affected, but I cannot see a dependency on
> > efl,
> > I've got jack installed with no efl and only libffado, if I try to
> > install ffado I get no efl, so I cannot understand where the
> > dependency
> > on efl is.
> 
> The subpackage dbus-c++-ecore of dbus-c++ depends on libefl.so.1 and
> libffado depends on dbus-c++. However, I understood that efl is being
> fixed with the next stable push so you probably do not have to worry
> about this one.

This I can't understand, libffado depends on dbus-c++, but dbus-c++
itself does not depend on libefl.so.1, only its subpackage dbus-c++-
ecore. So a dependency on a subpackage is affecting the entire package,
is this true? It looks strange to me, but maybe I'm wrong.
I know efl is being fixed, so I'm really not worried about this issue,
only a little bit curious about dependencies.

signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Adam Williamson]

On Tue, 2017-06-13 at 01:50 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Jun 13, 2017 at 12:20:36AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Mon, Jun 12, 2017 at 04:12:04PM -0700, Adam Williamson wrote:
> > > On Mon, 2017-06-12 at 16:06 -0700, Adam Williamson wrote:
> > > > On Mon, 2017-06-12 at 22:38 +, t...@fedoraproject.org wrote:
> > > > > os-autoinstadamwill   73 
> > > > > weeks ago  
> > > > 
> > > > Uh. What? I built this for fc26 in April. That's not 73 weeks ago. And
> > > > 'dnf install os-autoinst' does not report any broken dependencies.
> > > > 
> > > > https://koji.fedoraproject.org/koji/buildinfo?buildID=878719
> > > > https://bodhi.fedoraproject.org/updates/FEDORA-2017-2a2d78207d
> > > 
> > > Oh, I see the problem now, though it doesn't explain the '73 weeks
> > > ago':
> > > 
> > > [os-autoinst]
> > > os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.armv7hl 
> > > requires openvswitch
> > > [os-autoinst]
> > > os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.ppc64 
> > > requires openvswitch
> > 
> > Where did you find this information? I tried to find out what is
> > wrong with efl, and it install just fine on F26 here, and it was part
> > of an update that went to stable 3 days ago.
> 
> Found it:
> https://taskotron.fedoraproject.org/artifacts/all/382ff930-4d3d-11e7-a421-5254008e42f6/task_output/efl-1.19.0-4.fc26.x86_64.log

Actually, I got it from the report emails that are sent to test@ and
devel@ with every compose: "Fedora 26 compose report" and "Fedora
rawhide compose report". Each one includes a full repoclosure check for
each arch.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Till Maas]

On Tue, Jun 13, 2017 at 11:14:37AM +0200, Guido Aulisi wrote:

> This is going to break all audio applications in Fedora, because jack-
> audio-connection-kit is affected, but I cannot see a dependency on efl,
> I've got jack installed with no efl and only libffado, if I try to
> install ffado I get no efl, so I cannot understand where the dependency
> on efl is.

The subpackage dbus-c++-ecore of dbus-c++ depends on libefl.so.1 and
libffado depends on dbus-c++. However, I understood that efl is being
fixed with the next stable push so you probably do not have to worry
about this one.

Kind regards
Till


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Tom Callaway]

On 06/12/2017 06:38 PM, t...@fedoraproject.org wrote:
> In preparation for the Final Freeze on 2017-06-27 Release
> Engineering will retire all packages in Branched with broken dependencies and
> all packages depending on these. If you get this e-mail directly this affects
> at least one of your packages. Please fix the broken dependency as soon as
> possible.  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

> spot: python-repoze-who-plugins-sa, AcetoneISO, efl

AcetoneISO and efl are not currently broken, as far as I can see:

https://bodhi.fedoraproject.org/updates/FEDORA-2017-2c6432f719
https://bodhi.fedoraproject.org/updates/FEDORA-2017-9dcc8be30a

I just fixed the build for python-repoze-who-plugins-sa:

https://bodhi.fedoraproject.org/updates/python-repoze-who-plugins-sa-1.0.1-14.20160106gite1a36c5.fc26

~tom
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Jan Chaloupka]

On 06/13/2017 12:38 AM, t...@fedoraproject.org wrote:

In preparation for the Final Freeze on 2017-06-27 Release
Engineering will retire all packages in Branched with broken dependencies and
all packages depending on these. If you get this e-mail directly this affects
at least one of your packages. Please fix the broken dependency as soon as
possible.  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

   Package(co)maintainers  Status Change
===
AcetoneISO spot   160 weeks ago
OmegaT olea, mtasaka  160 weeks ago
RackTables coec   160 weeks ago
Raysebhtml, jussilehtola  160 weeks ago
YafaRayluya, slaanesh 15 weeks ago
asterisk   jsmith, gtjoseph, itamarjp,83 weeks ago
lbazan, russellb
atomicapp  vpavlin, golang-sig,   103 weeks ago
jchaloup, lalatendu
ayttm  mintojoseph160 weeks ago
banshee-community-extensions   chkr, elsupergomez 160 weeks ago
beacon satyak 160 weeks ago
compat-gcc-34  jakub  160 weeks ago
consul fpokorny, golang-sig,  74 weeks ago
jchaloup, sspreitz
eclipse-avrvladimirk, akurtakov   160 weeks ago
eflspot, dchen, sereinit  114 weeks ago
elemental  rhl27 weeks ago
erlang-riak_pipe   peter, erlang-sig  160 weeks ago
etcd   jchaloup, avesh, cypret,   110 weeks ago
eparis, golang-sig,
gscrivano, jcajka, lsm5,
peter, walters


I don't see anything broken here. From Koji:

etcd-3.1.9-1.fc26 
 	jchaloup 
 	2017-06-12 
16:15:16 	complete
etcd-3.1.9-1.fc27 
 	jchaloup 
 	2017-06-11 
09:41:08 	complete



Any way to figure out what dependencies are exactly broken?


fedora-dockerfiles adimania, lsm5, scollier   130 weeks ago
floppy-support bruno  160 weeks ago
fusionforgebeuc, nerville 136 weeks ago
gcc-python-plugin  dmalcolm, jakub160 weeks ago
gearmand   ktdreyer, blakegardner 160 weeks ago
getdp  ignatenkobrain, group  80 weeks ago
::neuro-sig, smani
gif2pngsundaram   160 weeks ago
git-annex  mathstuf, haskell-sig  160 weeks ago
gofed  jchaloup, fale, golang-sig 115 weeks ago
golang-github-docker-go-   jchaloup   65 weeks ago
connections
golang-github-docker-  fpokorny, eparis, jchaloup,95 weeks ago
libcontainer   lsm5, vbatts
golang-github-fsouza-go-   fpokorny, eparis, golang-  95 weeks ago
dockerclient   sig, jchaloup, lsm5,
maxamillion
golang-github-gonum-matrix fpokorny, jchaloup 86 weeks ago
golang-github-kubernetes-  fpokorny, jchaloup 86 weeks ago
heapster
golang-github-mistifyio-go-jchaloup   57 weeks ago
zfs
golang-github-samalba- fpokorny, golang-sig,  97 weeks ago
dockerclient   jchaloup
golang-googlecode-go-exp   fpokorny, golang-sig,  97 weeks ago
jchaloup, lsm5, vbatts
grass  devrim, neteler, oliver,   160 weeks ago
pertusus, rezso, volter
gyachi sundaram, ghosler  160 weeks ago
homerunjmarrero   160 weeks ago
iwhd   meyering, clalance, zaitcev160 weeks ago
java-gnome abo160 weeks ago
kf5-libkface   rdieter70 weeks ago
ledger radford, jamielinux160 weeks ago
libsmbios  mebrown, gunnersrini,  

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Zbigniew Jędrzejewski-Szmek]

On Mon, Jun 12, 2017 at 09:22:57PM -0600, Jerry James wrote:
> On Mon, Jun 12, 2017 at 7:58 PM, Zbigniew Jędrzejewski-Szmek
>  wrote:
> > Till, it'd be great if this kind of scary e-mail, affecting quite a
> > lot of packagers, would contain more details, hints, etc. It seems
> > people are confused ;)
> 
> Yes, I'm confused, too.  This report lists jacknativeclient.  I've
> just done a search on my email: I've received exactly zero emails
> about problems with this package.  (I counted twice.)  There are no
> bugs filed on this package.  It was built successfully just back in
> February.  Koji shows zero failed builds.  What exactly is the problem
> with it?

It probably depends on jack, and jack depends on efl, and efl depends
on tslib, and tslib had a botched so-name in the i686 build. This will
be fixed when tslib which is in updated will go stable. So probably
the best option would be to provide positive karma on
https://bodhi.fedoraproject.org/updates/FEDORA-2017-240bb678f2 if
you are a user of those packages.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Petr Pisar]

On 2017-06-13, Pavel Raiskup  wrote:
>> vim-syntastic  praiskup   38
>> weeks ago  
>
> Please don't remove this set of vim-syntastic* packages, there's
> nothing to do about this.  Once we have fixed release engineering
> processes [1] that allow me to ExcludeArch/ExclusiveArch particular
> **sub**packages, I'll do so.  Thanks!
>
> [1] https://pagure.io/pungi-fedora/issue/87
>
perl-Alien-ROOT is the same case .
The package is fine, but releng scripts cannot deal with it.

-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Kalev Lember]

On 06/13/2017 12:47 AM, Josh Stone wrote:
> On 06/12/2017 03:38 PM, t...@fedoraproject.org wrote:
>> lldb   airlied, daveisfera,   71 weeks ago  
>>jankratochvil, jvcelak,  
>>siddharths, tstellar 
> 
> Where does that 71 weeks come from?  The lldb-3.9.1-4.fc26 reported
> below was just in March, not to mention lldb-4.0.0-1.fc26 on May 12.
> 
>> Depending on: lldb (21), status change: 2016-01-27 (71 weeks ago)
>>  rust (maintained by: group::rust-sig, ignatenkobrain, jistone, ttorling)
>>  rust-lldb-1.17.0-1.fc26.i686 requires lldb = 3.9.1-4.fc26, 
>> python-lldb = 3.9.1-4.fc26
>>
>>  cargo (maintained by: group::rust-sig, ignatenkobrain, jistone, 
>> ttorling)
>>  cargo-0.18.0-1.fc26.i686 requires rust = 1.17.0-1.fc26
>>  cargo-0.18.0-1.fc26.src requires rust = 1.17.0-1.fc26
> 
> If it comes down to it, I'll just remove the rust-lldb subpackage, but I
> don't see what the actual problem is...

I think the llvm dep should already be fixed and nothing needs to be
done here. Looks like the report was generated using the latest
available F26 compose at that time; the next compose should pick up the
new lldb-4.0.0-1.fc26 build.

-- 
Kalev
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Guido Aulisi]

Il giorno mar, 13/06/2017 alle 11.11 +0100, Peter Robinson ha scritto:
> I'm not sure how all those people can be co-maintainers of efl. I'm
> not sure how that's meant to be interpreted but given some of the
> other responses I think this script as bit rotted some what.
> 
> Peter

I think these are (co)maintainers of other packages affected by efl
problems, I am one of these, but IMHO dependencies are not well
computed here.

> > Affected (co)maintainers
> > alexl: efl
> > ankursinha: lldb, efl
> > atkac: efl
> > bpepple: efl
> > bsjones: efl
> > caillon: efl
> > caolanm: efl
> > chkr: efl, banshee-community-extensions
> > cicku: efl
> > company: lldb, efl
> > cwickert: efl
> > danfruehauf: efl
> > dchen: efl
> > design-sw: efl
> > drago01: efl
> > dtimms: efl
> > dwrobel: efl
> > filiperosset: efl
> > greghellings: efl
> > group::gnome-sig: libsmbios, efl
> > hobbes1069: efl
> > ignatenkobrain: lldb, efl, getdp
> > imntreal: efl
> > jankratochvil: lldb, efl
> > jjames: efl
> > jkraehemann: efl
> > jnovy: efl
> > john2583: efl
> > johnp: efl
> > jvlomax: efl
> > jwrdegoede: efl
> > kkofler: efl
> > konradm: lldb, efl
> > kvolny: efl
> > kwizart: efl
> > lennart: efl
> > limb: lldb, efl
> > lkundrak: efl
> > lorenzosu: efl
> > luya: YafaRay, efl
> > mbarnes: python-etcd, efl, etcd
> > mbooth: efl
> > mcrha: efl
> > moezroy: efl
> > mschwendt: efl
> > mtasaka: OmegaT, efl, sslogger
> > muep: efl
> > nando: efl
> > nobrakal: efl
> > nonamedotc: efl
> > nphilipp: efl
> > nucleo: efl
> > oget: efl
> > pbrobinson: efl
> > perex: efl
> > pfj: efl
> > pwalter: lldb, efl
> > rakesh: efl
> > rdieter: efl, kf5-libkface
> > rhughes: libsmbios, efl
> > roma: efl
> > rrankin: efl
> > rstrode: efl
> > s4504kr: efl
> > salimma: efl
> > sereinit: efl
> > sergiomb: efl
> > slaanesh: YafaRay, efl, mesos
> > smani: efl, getdp
> > spot: python-repoze-who-plugins-sa, AcetoneISO, efl
> > ssp: efl
> > tartina: efl
> > thm: efl
> > thomasj: efl
> > tikro: efl
> > uraeus: efl
> > verdurin: efl
> > vicodan: libsmbios, efl, python-repoze-who-plugins-sa
> > wtaymans: lldb, efl
> > xiphmont: efl
> > zbyszek: efl


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Peter Robinson]

I'm not sure how all those people can be co-maintainers of efl. I'm
not sure how that's meant to be interpreted but given some of the
other responses I think this script as bit rotted some what.

Peter

> Affected (co)maintainers

> alexl: efl
> ankursinha: lldb, efl
> atkac: efl
> bpepple: efl
> bsjones: efl
> caillon: efl
> caolanm: efl
> chkr: efl, banshee-community-extensions
> cicku: efl
> company: lldb, efl
> cwickert: efl
> danfruehauf: efl
> dchen: efl
> design-sw: efl
> drago01: efl
> dtimms: efl
> dwrobel: efl
> filiperosset: efl
> greghellings: efl
> group::gnome-sig: libsmbios, efl
> hobbes1069: efl
> ignatenkobrain: lldb, efl, getdp
> imntreal: efl
> jankratochvil: lldb, efl
> jjames: efl
> jkraehemann: efl
> jnovy: efl
> john2583: efl
> johnp: efl
> jvlomax: efl
> jwrdegoede: efl
> kkofler: efl
> konradm: lldb, efl
> kvolny: efl
> kwizart: efl
> lennart: efl
> limb: lldb, efl
> lkundrak: efl
> lorenzosu: efl
> luya: YafaRay, efl
> mbarnes: python-etcd, efl, etcd
> mbooth: efl
> mcrha: efl
> moezroy: efl
> mschwendt: efl
> mtasaka: OmegaT, efl, sslogger
> muep: efl
> nando: efl
> nobrakal: efl
> nonamedotc: efl
> nphilipp: efl
> nucleo: efl
> oget: efl
> pbrobinson: efl
> perex: efl
> pfj: efl
> pwalter: lldb, efl
> rakesh: efl
> rdieter: efl, kf5-libkface
> rhughes: libsmbios, efl
> roma: efl
> rrankin: efl
> rstrode: efl
> s4504kr: efl
> salimma: efl
> sereinit: efl
> sergiomb: efl
> slaanesh: YafaRay, efl, mesos
> smani: efl, getdp
> spot: python-repoze-who-plugins-sa, AcetoneISO, efl
> ssp: efl
> tartina: efl
> thm: efl
> thomasj: efl
> tikro: efl
> uraeus: efl
> verdurin: efl
> vicodan: libsmbios, efl, python-repoze-who-plugins-sa
> wtaymans: lldb, efl
> xiphmont: efl
> zbyszek: efl
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Haïkel]

2017-06-13 0:38 GMT+02:00  :
> In preparation for the Final Freeze on 2017-06-27 Release
> Engineering will retire all packages in Branched with broken dependencies and
> all packages depending on these. If you get this e-mail directly this affects
> at least one of your packages. Please fix the broken dependency as soon as
> possible.  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
>
>   Package(co)maintainers  Status Change
> ===
> AcetoneISO spot   160 weeks ago
> OmegaT olea, mtasaka  160 weeks ago
> RackTables coec   160 weeks ago
> Raysebhtml, jussilehtola  160 weeks ago
> YafaRayluya, slaanesh 15 weeks ago
> asterisk   jsmith, gtjoseph, itamarjp,83 weeks ago
>lbazan, russellb
> atomicapp  vpavlin, golang-sig,   103 weeks ago
>jchaloup, lalatendu
> ayttm  mintojoseph160 weeks ago
> banshee-community-extensions   chkr, elsupergomez 160 weeks ago
> beacon satyak 160 weeks ago
> compat-gcc-34  jakub  160 weeks ago
> consul fpokorny, golang-sig,  74 weeks ago
>jchaloup, sspreitz
> eclipse-avrvladimirk, akurtakov   160 weeks ago
> eflspot, dchen, sereinit  114 weeks ago
> elemental  rhl27 weeks ago
> erlang-riak_pipe   peter, erlang-sig  160 weeks ago
> etcd   jchaloup, avesh, cypret,   110 weeks ago
>eparis, golang-sig,
>gscrivano, jcajka, lsm5,
>peter, walters
> fedora-dockerfiles adimania, lsm5, scollier   130 weeks ago
> floppy-support bruno  160 weeks ago
> fusionforgebeuc, nerville 136 weeks ago
> gcc-python-plugin  dmalcolm, jakub160 weeks ago
> gearmand   ktdreyer, blakegardner 160 weeks ago
> getdp  ignatenkobrain, group  80 weeks ago
>::neuro-sig, smani
> gif2pngsundaram   160 weeks ago
> git-annex  mathstuf, haskell-sig  160 weeks ago
> gofed  jchaloup, fale, golang-sig 115 weeks ago
> golang-github-docker-go-   jchaloup   65 weeks ago
> connections
> golang-github-docker-  fpokorny, eparis, jchaloup,95 weeks ago
> libcontainer   lsm5, vbatts
> golang-github-fsouza-go-   fpokorny, eparis, golang-  95 weeks ago
> dockerclient   sig, jchaloup, lsm5,
>maxamillion
> golang-github-gonum-matrix fpokorny, jchaloup 86 weeks ago
> golang-github-kubernetes-  fpokorny, jchaloup 86 weeks ago
> heapster
> golang-github-mistifyio-go-jchaloup   57 weeks ago
> zfs
> golang-github-samalba- fpokorny, golang-sig,  97 weeks ago
> dockerclient   jchaloup
> golang-googlecode-go-exp   fpokorny, golang-sig,  97 weeks ago
>jchaloup, lsm5, vbatts
> grass  devrim, neteler, oliver,   160 weeks ago
>pertusus, rezso, volter
> gyachi sundaram, ghosler  160 weeks ago
> homerunjmarrero   160 weeks ago
> iwhd   meyering, clalance, zaitcev160 weeks ago
> java-gnome abo160 weeks ago
> kf5-libkface   rdieter70 weeks ago
> ledger radford, jamielinux160 weeks ago
> libsmbios  mebrown, gunnersrini,  33 weeks ago
>praveenp
> lldb   airlied, daveisfera,   71 weeks ago
>jankratochvil, jvcelak,
>siddharths, tstellar
> meshlabbrouhaha   160 weeks ago
> mesos  

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Christian Dersch]

On 06/13/2017 12:38 AM, t...@fedoraproject.org wrote:
> thunderbird-enigmail   lupinix75 weeks ago  
>

Should be fixed now, new build submitted for updates-testing.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Guido Aulisi]

Il giorno lun, 12/06/2017 alle 22.38 +, t...@fedoraproject.org ha
scritto:
> In preparation for the Final Freeze on 2017-06-27 Release
> Engineering will retire all packages in Branched with broken
> dependencies and
> all packages depending on these. If you get this e-mail directly this
> affects
> at least one of your packages. Please fix the broken dependency as
> soon as
> possible.  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
> 
This is going to break all audio applications in Fedora, because jack-
audio-connection-kit is affected, but I cannot see a dependency on efl,
I've got jack installed with no efl and only libffado, if I try to
install ffado I get no efl, so I cannot understand where the dependency
on efl is.

signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Pavel Raiskup]

On Tuesday, June 13, 2017 12:38:11 AM CEST t...@fedoraproject.org wrote:
> In preparation for the Final Freeze on 2017-06-27 Release
> Engineering will retire all packages in Branched with broken dependencies and
> all packages depending on these. If you get this e-mail directly this affects
> at least one of your packages. Please fix the broken dependency as soon as
> possible.
...
> vim-syntastic  praiskup   38 weeks ago  

Please don't remove this set of vim-syntastic* packages, there's nothing to do
about this.  Once we have fixed release engineering processes [1] that allow me
to ExcludeArch/ExclusiveArch particular **sub**packages, I'll do so.  Thanks!

[1] https://pagure.io/pungi-fedora/issue/87

Pavel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Jerry James]

On Mon, Jun 12, 2017 at 7:58 PM, Zbigniew Jędrzejewski-Szmek
 wrote:
> Till, it'd be great if this kind of scary e-mail, affecting quite a
> lot of packagers, would contain more details, hints, etc. It seems
> people are confused ;)

Yes, I'm confused, too.  This report lists jacknativeclient.  I've
just done a search on my email: I've received exactly zero emails
about problems with this package.  (I counted twice.)  There are no
bugs filed on this package.  It was built successfully just back in
February.  Koji shows zero failed builds.  What exactly is the problem
with it?
-- 
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Zbigniew Jędrzejewski-Szmek]

On Tue, Jun 13, 2017 at 01:50:38AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Jun 13, 2017 at 12:20:36AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Mon, Jun 12, 2017 at 04:12:04PM -0700, Adam Williamson wrote:
> > > On Mon, 2017-06-12 at 16:06 -0700, Adam Williamson wrote:
> > > > On Mon, 2017-06-12 at 22:38 +, t...@fedoraproject.org wrote:
> > > > > os-autoinstadamwill   73 
> > > > > weeks ago  
> > > > 
> > > > Uh. What? I built this for fc26 in April. That's not 73 weeks ago. And
> > > > 'dnf install os-autoinst' does not report any broken dependencies.
> > > > 
> > > > https://koji.fedoraproject.org/koji/buildinfo?buildID=878719
> > > > https://bodhi.fedoraproject.org/updates/FEDORA-2017-2a2d78207d
> > > 
> > > Oh, I see the problem now, though it doesn't explain the '73 weeks
> > > ago':
> > > 
> > > [os-autoinst]
> > > os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.armv7hl 
> > > requires openvswitch
> > > [os-autoinst]
> > > os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.ppc64 
> > > requires openvswitch
> > 
> > Where did you find this information? I tried to find out what is
> > wrong with efl, and it install just fine on F26 here, and it was part
> > of an update that went to stable 3 days ago.
> 
> Found it:
> https://taskotron.fedoraproject.org/artifacts/all/382ff930-4d3d-11e7-a421-5254008e42f6/task_output/efl-1.19.0-4.fc26.x86_64.log

[sorry for posting so many times]

This doesn't really explain anything, because tslib.i686 is available,
and provides libts.so.0. Ah, OK, the update that fixes the .so name
is in updates-testing, and I have updates-testing enabled.

Till, it'd be great if this kind of scary e-mail, affecting quite a
lot of packagers, would contain more details, hints, etc. It seems
people are confused ;)

Also, I think it'd make sense to filter out stuff that is fixed
by updates in the pipeline.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Peter Hutterer]

On Mon, Jun 12, 2017 at 03:47:48PM -0700, Josh Stone wrote:
> On 06/12/2017 03:38 PM, t...@fedoraproject.org wrote:
> > lldb   airlied, daveisfera,   71 weeks ago  
> >jankratochvil, jvcelak,  
> >siddharths, tstellar 
> 
> Where does that 71 weeks come from?  The lldb-3.9.1-4.fc26 reported
> below was just in March, not to mention lldb-4.0.0-1.fc26 on May 12.

not to mention that this lldb issue breaks rust which in turn breaks meson
which in turn breaks anything using meson. I'm going out on a limb here and
assume that packages using rust and meson are not necessarily EOL'd :)

Cheers,
   Peter
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Zbigniew Jędrzejewski-Szmek]

On Tue, Jun 13, 2017 at 12:20:36AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Jun 12, 2017 at 04:12:04PM -0700, Adam Williamson wrote:
> > On Mon, 2017-06-12 at 16:06 -0700, Adam Williamson wrote:
> > > On Mon, 2017-06-12 at 22:38 +, t...@fedoraproject.org wrote:
> > > > os-autoinstadamwill   73 weeks 
> > > > ago  
> > > 
> > > Uh. What? I built this for fc26 in April. That's not 73 weeks ago. And
> > > 'dnf install os-autoinst' does not report any broken dependencies.
> > > 
> > > https://koji.fedoraproject.org/koji/buildinfo?buildID=878719
> > > https://bodhi.fedoraproject.org/updates/FEDORA-2017-2a2d78207d
> > 
> > Oh, I see the problem now, though it doesn't explain the '73 weeks
> > ago':
> > 
> > [os-autoinst]
> > os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.armv7hl 
> > requires openvswitch
> > [os-autoinst]
> > os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.ppc64 
> > requires openvswitch
> 
> Where did you find this information? I tried to find out what is
> wrong with efl, and it install just fine on F26 here, and it was part
> of an update that went to stable 3 days ago.

Found it:
https://taskotron.fedoraproject.org/artifacts/all/382ff930-4d3d-11e7-a421-5254008e42f6/task_output/efl-1.19.0-4.fc26.x86_64.log

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Zbigniew Jędrzejewski-Szmek]

On Mon, Jun 12, 2017 at 04:12:04PM -0700, Adam Williamson wrote:
> On Mon, 2017-06-12 at 16:06 -0700, Adam Williamson wrote:
> > On Mon, 2017-06-12 at 22:38 +, t...@fedoraproject.org wrote:
> > > os-autoinstadamwill   73 weeks 
> > > ago  
> > 
> > Uh. What? I built this for fc26 in April. That's not 73 weeks ago. And
> > 'dnf install os-autoinst' does not report any broken dependencies.
> > 
> > https://koji.fedoraproject.org/koji/buildinfo?buildID=878719
> > https://bodhi.fedoraproject.org/updates/FEDORA-2017-2a2d78207d
> 
> Oh, I see the problem now, though it doesn't explain the '73 weeks
> ago':
> 
> [os-autoinst]
> os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.armv7hl 
> requires openvswitch
> [os-autoinst]
> os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.ppc64 requires 
> openvswitch

Where did you find this information? I tried to find out what is
wrong with efl, and it install just fine on F26 here, and it was part
of an update that went to stable 3 days ago.

Zbyszek

> so the problem is that the current stable openvswitch was not built for
> two arches; the openvswitch package currently in updates-testing *is*
> built for those arches, however. It seems pointless to send out an
> update that disables the subpackage for two arches for a few days until
> openvswitch is pushed stable.
> 
> Perhaps the proliferation of arches in primary Koji might cause a
> rethink of how this automatic retirement works? It wouldn't seem to be
> a good idea to automatically retire this package (which is in fact
> quite important, and under active maintenance) on this basis.
> -- 
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Adam Williamson]

On Mon, 2017-06-12 at 16:06 -0700, Adam Williamson wrote:
> On Mon, 2017-06-12 at 22:38 +, t...@fedoraproject.org wrote:
> > os-autoinstadamwill   73 weeks ago  
> 
> Uh. What? I built this for fc26 in April. That's not 73 weeks ago. And
> 'dnf install os-autoinst' does not report any broken dependencies.
> 
> https://koji.fedoraproject.org/koji/buildinfo?buildID=878719
> https://bodhi.fedoraproject.org/updates/FEDORA-2017-2a2d78207d

Oh, I see the problem now, though it doesn't explain the '73 weeks
ago':

[os-autoinst]
os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.armv7hl requires 
openvswitch
[os-autoinst]
os-autoinst-openvswitch-4.4-18.20170410git97928a2.fc26.ppc64 requires 
openvswitch

so the problem is that the current stable openvswitch was not built for
two arches; the openvswitch package currently in updates-testing *is*
built for those arches, however. It seems pointless to send out an
update that disables the subpackage for two arches for a few days until
openvswitch is pushed stable.

Perhaps the proliferation of arches in primary Koji might cause a
rethink of how this automatic retirement works? It wouldn't seem to be
a good idea to automatically retire this package (which is in fact
quite important, and under active maintenance) on this basis.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Adam Williamson]

On Mon, 2017-06-12 at 22:38 +, t...@fedoraproject.org wrote:
> os-autoinstadamwill   73 weeks ago  

Uh. What? I built this for fc26 in April. That's not 73 weeks ago. And
'dnf install os-autoinst' does not report any broken dependencies.

https://koji.fedoraproject.org/koji/buildinfo?buildID=878719
https://bodhi.fedoraproject.org/updates/FEDORA-2017-2a2d78207d
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

[Josh Stone]

On 06/12/2017 03:38 PM, t...@fedoraproject.org wrote:
> lldb   airlied, daveisfera,   71 weeks ago  
>jankratochvil, jvcelak,  
>siddharths, tstellar 

Where does that 71 weeks come from?  The lldb-3.9.1-4.fc26 reported
below was just in March, not to mention lldb-4.0.0-1.fc26 on May 12.

> Depending on: lldb (21), status change: 2016-01-27 (71 weeks ago)
>   rust (maintained by: group::rust-sig, ignatenkobrain, jistone, ttorling)
>   rust-lldb-1.17.0-1.fc26.i686 requires lldb = 3.9.1-4.fc26, 
> python-lldb = 3.9.1-4.fc26
> 
>   cargo (maintained by: group::rust-sig, ignatenkobrain, jistone, 
> ttorling)
>   cargo-0.18.0-1.fc26.i686 requires rust = 1.17.0-1.fc26
>   cargo-0.18.0-1.fc26.src requires rust = 1.17.0-1.fc26

If it comes down to it, I'll just remove the rust-lldb subpackage, but I
don't see what the actual problem is...
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Retiring Packages with Broken Dependencies in branched (2017-06-12)

[till]

In preparation for the Final Freeze on 2017-06-27 Release
Engineering will retire all packages in Branched with broken dependencies and
all packages depending on these. If you get this e-mail directly this affects
at least one of your packages. Please fix the broken dependency as soon as
possible.  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

  Package(co)maintainers  Status Change 
===
AcetoneISO spot   160 weeks ago 
OmegaT olea, mtasaka  160 weeks ago 
RackTables coec   160 weeks ago 
Raysebhtml, jussilehtola  160 weeks ago 
YafaRayluya, slaanesh 15 weeks ago  
asterisk   jsmith, gtjoseph, itamarjp,83 weeks ago  
   lbazan, russellb 
atomicapp  vpavlin, golang-sig,   103 weeks ago 
   jchaloup, lalatendu  
ayttm  mintojoseph160 weeks ago 
banshee-community-extensions   chkr, elsupergomez 160 weeks ago 
beacon satyak 160 weeks ago 
compat-gcc-34  jakub  160 weeks ago 
consul fpokorny, golang-sig,  74 weeks ago  
   jchaloup, sspreitz   
eclipse-avrvladimirk, akurtakov   160 weeks ago 
eflspot, dchen, sereinit  114 weeks ago 
elemental  rhl27 weeks ago  
erlang-riak_pipe   peter, erlang-sig  160 weeks ago 
etcd   jchaloup, avesh, cypret,   110 weeks ago 
   eparis, golang-sig,  
   gscrivano, jcajka, lsm5, 
   peter, walters   
fedora-dockerfiles adimania, lsm5, scollier   130 weeks ago 
floppy-support bruno  160 weeks ago 
fusionforgebeuc, nerville 136 weeks ago 
gcc-python-plugin  dmalcolm, jakub160 weeks ago 
gearmand   ktdreyer, blakegardner 160 weeks ago 
getdp  ignatenkobrain, group  80 weeks ago  
   ::neuro-sig, smani   
gif2pngsundaram   160 weeks ago 
git-annex  mathstuf, haskell-sig  160 weeks ago 
gofed  jchaloup, fale, golang-sig 115 weeks ago 
golang-github-docker-go-   jchaloup   65 weeks ago  
connections 
golang-github-docker-  fpokorny, eparis, jchaloup,95 weeks ago  
libcontainer   lsm5, vbatts 
golang-github-fsouza-go-   fpokorny, eparis, golang-  95 weeks ago  
dockerclient   sig, jchaloup, lsm5, 
   maxamillion  
golang-github-gonum-matrix fpokorny, jchaloup 86 weeks ago  
golang-github-kubernetes-  fpokorny, jchaloup 86 weeks ago  
heapster
golang-github-mistifyio-go-jchaloup   57 weeks ago  
zfs 
golang-github-samalba- fpokorny, golang-sig,  97 weeks ago  
dockerclient   jchaloup 
golang-googlecode-go-exp   fpokorny, golang-sig,  97 weeks ago  
   jchaloup, lsm5, vbatts   
grass  devrim, neteler, oliver,   160 weeks ago 
   pertusus, rezso, volter  
gyachi sundaram, ghosler  160 weeks ago 
homerunjmarrero   160 weeks ago 
iwhd   meyering, clalance, zaitcev160 weeks ago 
java-gnome abo160 weeks ago 
kf5-libkface   rdieter70 weeks ago  
ledger radford, jamielinux160 

Retiring Packages with Broken Dependencies in branched (2017-06-12)

[till]

In preparation for the Final Freeze on 2017-06-27 Release
Engineering will retire all packages in Branched with broken dependencies and
all packages depending on these. If you get this e-mail directly this affects
at least one of your packages. Please fix the broken dependency as soon as
possible.  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

  Package(co)maintainers  Status Change 
===
AcetoneISO spot   160 weeks ago 
OmegaT olea, mtasaka  160 weeks ago 
RackTables coec   160 weeks ago 
Raysebhtml, jussilehtola  160 weeks ago 
YafaRayluya, slaanesh 15 weeks ago  
asterisk   jsmith, gtjoseph, itamarjp,83 weeks ago  
   lbazan, russellb 
atomicapp  vpavlin, golang-sig,   103 weeks ago 
   jchaloup, lalatendu  
ayttm  mintojoseph160 weeks ago 
banshee-community-extensions   chkr, elsupergomez 160 weeks ago 
beacon satyak 160 weeks ago 
compat-gcc-34  jakub  160 weeks ago 
consul fpokorny, golang-sig,  74 weeks ago  
   jchaloup, sspreitz   
eclipse-avrvladimirk, akurtakov   160 weeks ago 
eflspot, dchen, sereinit  114 weeks ago 
elemental  rhl27 weeks ago  
erlang-riak_pipe   peter, erlang-sig  160 weeks ago 
etcd   jchaloup, avesh, cypret,   110 weeks ago 
   eparis, golang-sig,  
   gscrivano, jcajka, lsm5, 
   peter, walters   
fedora-dockerfiles adimania, lsm5, scollier   130 weeks ago 
floppy-support bruno  160 weeks ago 
fusionforgebeuc, nerville 136 weeks ago 
gcc-python-plugin  dmalcolm, jakub160 weeks ago 
gearmand   ktdreyer, blakegardner 160 weeks ago 
getdp  ignatenkobrain, group  80 weeks ago  
   ::neuro-sig, smani   
gif2pngsundaram   160 weeks ago 
git-annex  mathstuf, haskell-sig  160 weeks ago 
gofed  jchaloup, fale, golang-sig 115 weeks ago 
golang-github-docker-go-   jchaloup   65 weeks ago  
connections 
golang-github-docker-  fpokorny, eparis, jchaloup,95 weeks ago  
libcontainer   lsm5, vbatts 
golang-github-fsouza-go-   fpokorny, eparis, golang-  95 weeks ago  
dockerclient   sig, jchaloup, lsm5, 
   maxamillion  
golang-github-gonum-matrix fpokorny, jchaloup 86 weeks ago  
golang-github-kubernetes-  fpokorny, jchaloup 86 weeks ago  
heapster
golang-github-mistifyio-go-jchaloup   57 weeks ago  
zfs 
golang-github-samalba- fpokorny, golang-sig,  97 weeks ago  
dockerclient   jchaloup 
golang-googlecode-go-exp   fpokorny, golang-sig,  97 weeks ago  
   jchaloup, lsm5, vbatts   
grass  devrim, neteler, oliver,   160 weeks ago 
   pertusus, rezso, volter  
gyachi sundaram, ghosler  160 weeks ago 
homerunjmarrero   160 weeks ago 
iwhd   meyering, clalance, zaitcev160 weeks ago 
java-gnome abo160 weeks ago 
kf5-libkface   rdieter70 weeks ago  
ledger radford, jamielinux160