Notifications on dependency retirement

[Julien Enselme]

Hi,

I discovered this morning that a package I co-maintain was retired
(ccnet [1]) because one of its dependency was retired (libzdb [2]). I
learned it only because we have an open bug on it that change assigner
because of this fact. I'll call this notification thanks to luck.

Is there a way to be notified as soon as a dependency is orphaned so
the (co-)maintainer can take action as soon as possible?

I think the usual way is to send a notification message to devel but it
relies on sending/reading the mail (I personally forgot ccnet relied on
libzdb). In this case, I can't find one. But I may have missed it.

Could this simply be because I am only a watcher and committer (neither
POC nor admin) of this package or should we find a way to improve this?

Regards,

[1] https://admin.fedoraproject.org/pkgdb/package/rpms/ccnet/
[2] https://admin.fedoraproject.org/pkgdb/package/rpms/libzdb/
-- 
Julien Enselme
http://www.jujens.eu/

[Parag Nemade]

On Wed, Oct 19, 2016 at 5:04 PM, Julien Enselme <jujens(a)jujens.eu&gt; wrote:
>  Hi,
>
>  I discovered this morning that a package I co-maintain was retired
>  (ccnet [1]) because one of its dependency was retired (libzdb [2]). I
>  learned it only because we have an open bug on it that change assigner
>  because of this fact. I'll call this notification thanks to luck.
>
>  Is there a way to be notified as soon as a dependency is orphaned so
>  the (co-)maintainer can take action as soon as possible?
>
>  I think the usual way is to send a notification message to devel but it
>  relies on sending/reading the mail (I personally forgot ccnet relied on
>  libzdb). In this case, I can't find one. But I may have missed it.
>
>  Could this simply be because I am only a watcher and committer (neither
>  POC nor admin) of this package or should we find a way to improve this? 
Keep watching devel list for "Orphaned Packages in <branch>" emails.
The latest one[1] shows that libzdb is in orphaned state since last 15
weeks.

Regards,
Parag.

[1]
https://lists.fedoraproject.org/archives/list/[e-mail].o...

[Julien Enselme]

On Wed, 2016-10-19 at 17:21 +0530, Parag Nemade wrote:
>  On Wed, Oct 19, 2016 at 5:04 PM, Julien Enselme
> <jujens(a)jujens.eu&gt;
>  wrote:
>  > 
>  > Hi,
>  > 
>  > I discovered this morning that a package I co-maintain was retired
>  > (ccnet [1]) because one of its dependency was retired (libzdb [2]).
>  > I
>  > learned it only because we have an open bug on it that change
>  > assigner
>  > because of this fact. I'll call this notification thanks to luck.
>  > 
>  > Is there a way to be notified as soon as a dependency is orphaned
>  > so
>  > the (co-)maintainer can take action as soon as possible?
>  > 
>  > I think the usual way is to send a notification message to devel
>  > but it
>  > relies on sending/reading the mail (I personally forgot ccnet
>  > relied on
>  > libzdb). In this case, I can't find one. But I may have missed it.
>  > 
>  > Could this simply be because I am only a watcher and committer
>  > (neither
>  > POC nor admin) of this package or should we find a way to improve
>  > this?
>  
>  Keep watching devel list for "Orphaned Packages in <branch>" emails.
>  The latest one[1] shows that libzdb is in orphaned state since last
>  15
>  weeks.
>  
>  Regards,
>  Parag.
>  
>  [1]
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  ct.org/thread/UKET6ZEQY2YPLZ2XZUGRGGQBYV73YLXL/ 
Thanks for the link. I didn't use to pay much attention to these
emails. I'll be more careful in the future.

Regards,
-- 
Julien Enselme
http://www.jujens.eu/

[Christopher]

On Wed, Oct 19, 2016, 08:51 Julien Enselme <jujens(a)jujens.eu&gt; wrote:

>  On Wed, 2016-10-19 at 17:21 +0530, Parag Nemade wrote:
>  > On Wed, Oct 19, 2016 at 5:04 PM, Julien Enselme <jujens(a)jujens.eu&gt;
>  > wrote:
>  > >
>  > > Hi,
>  > >
>  > > I discovered this morning that a package I co-maintain was retired
>  > > (ccnet [1]) because one of its dependency was retired (libzdb [2]).
>  > > I
>  > > learned it only because we have an open bug on it that change
>  > > assigner
>  > > because of this fact. I'll call this notification thanks to luck.
>  > >
>  > > Is there a way to be notified as soon as a dependency is orphaned
>  > > so
>  > > the (co-)maintainer can take action as soon as possible?
>  > >
>  > > I think the usual way is to send a notification message to devel
>  > > but it
>  > > relies on sending/reading the mail (I personally forgot ccnet
>  > > relied on
>  > > libzdb). In this case, I can't find one. But I may have missed it.
>  > >
>  > > Could this simply be because I am only a watcher and committer
>  > > (neither
>  > > POC nor admin) of this package or should we find a way to improve
>  > > this?
>  >
>  > Keep watching devel list for "Orphaned Packages in <branch>"
> emails.
>  > The latest one[1] shows that libzdb is in orphaned state since last
>  > 15
>  > weeks.
>  >
>  > Regards,
>  > Parag.
>  >
>  > [1]
>  > https://lists.fedoraproject.org/archives/list/[e-mail]
>  > ct.org/thread/UKET6ZEQY2YPLZ2XZUGRGGQBYV73YLXL/
>
>  Thanks for the link. I didn't use to pay much attention to these
>  emails. I'll be more careful in the future.
>  
There's a lot of noise on this list, and those emails are information
overload. The fact that a particular package is affected is easily
overlooked. It'd be nice if a notice could be shown in pkgdb to indicate
that a particular package has dependencies in a problematic state. It'd
also be nice if each package has its own list or notification feeds.

[Till Maas]

On Wed, Oct 19, 2016 at 03:59:41PM +0000, Christopher wrote:
>  On Wed, Oct 19, 2016, 08:51 Julien Enselme <jujens(a)jujens.eu&gt;
> wrote:
>  > Thanks for the link. I didn't use to pay much attention to these
>  > emails. I'll be more careful in the future.
>  >
>  
>  There's a lot of noise on this list, and those emails are information
>  overload. The fact that a particular package is affected is easily
>  overlooked. It'd be nice if a notice could be shown in pkgdb to indicate
>  that a particular package has dependencies in a problematic state. It'd
>  also be nice if each package has its own list or notification feeds. 
I might get to send smaller e-mails to each person eventually, but in
the meantime the e-mails are not only sent to the list but also to each
affected (co)maintainer individually. Therefore getting the e-mail
directly is indicates that one will be affected by the retirement and
searching for ones FAS name in the e-mail shows which package needs to
be adopted.

Kind regards
Till

[Julien Enselme]

On Thu, 2016-10-20 at 22:39 +0200, Till Maas wrote:
>  On Wed, Oct 19, 2016 at 03:59:41PM +0000, Christopher wrote:
>  > 
>  > On Wed, Oct 19, 2016, 08:51 Julien Enselme <jujens(a)jujens.eu&gt;
>  > wrote:
>  > > 
>  > > Thanks for the link. I didn't use to pay much attention to these
>  > > emails. I'll be more careful in the future.
>  > > 
>  > 
>  > There's a lot of noise on this list, and those emails are
>  > information
>  > overload. The fact that a particular package is affected is easily
>  > overlooked. It'd be nice if a notice could be shown in pkgdb to
>  > indicate
>  > that a particular package has dependencies in a problematic state.
>  > It'd
>  > also be nice if each package has its own list or notification
>  > feeds.
>  
>  I might get to send smaller e-mails to each person eventually, but in
>  the meantime the e-mails are not only sent to the list but also to
>  each
>  affected (co)maintainer individually. 
I guess that in this case you mean the (co)maintainer of the retired
package not its dependencies. Can I ask what permissions on the package
are required to get these mails?

What I find strange here is that I am a (co)maintainer for ccnet (watch
& commit permissions only) but I didn't get these mails.

>  Therefore getting the e-mail
>  directly is indicates that one will be affected by the retirement and
>  searching for ones FAS name in the e-mail shows which package needs
>  to
>  be adopted.
>  
>  Kind regards
>  Till 
Regards,
-- 
Julien Enselme
http://www.jujens.eu/

[Till Maas]

On Fri, Oct 21, 2016 at 11:51:25AM +0200, Julien Enselme wrote:

>  I guess that in this case you mean the (co)maintainer of the retired
>  package not its dependencies. Can I ask what permissions on the package
>  are required to get these mails?
>  
>  What I find strange here is that I am a (co)maintainer for ccnet (watch
>  & commit permissions only) but I didn't get these mails. 
Any permission suffices, however it took a while since I sent the last
e-mail till I got to retire the packages. You should have gotten at
least the e-mail "Orphaned Packages in rawhide (2016-09-08)" and several
before it. Can you please properly check you mailbox? The e-mail
mentions your FAS username therefore I am pretty sure that there was a
mail sent to you, but I do not have any logs to check it.

Kind regards
Till

[Julien Enselme]

On Fri, 2016-10-21 at 19:48 +0200, Till Maas wrote:
>  On Fri, Oct 21, 2016 at 11:51:25AM +0200, Julien Enselme wrote:
>  
>  > 
>  > I guess that in this case you mean the (co)maintainer of the
>  > retired
>  > package not its dependencies. Can I ask what permissions on the
>  > package
>  > are required to get these mails?
>  > 
>  > What I find strange here is that I am a (co)maintainer for ccnet
>  > (watch
>  > & commit permissions only) but I didn't get these mails.
>  
>  Any permission suffices,  
Good to know.

>  however it took a while since I sent the last
>  e-mail till I got to retire the packages. You should have gotten at
>  least the e-mail "Orphaned Packages in rawhide (2016-09-08)" and
>  several
>  before it. Can you please properly check you mailbox? The e-mail
>  mentions your FAS username therefore I am pretty sure that there was
>  a
>  mail sent to you, but I do not have any logs to check it. 
I have received multiple version of these emails (2016-09-08, 2016-10-
18 and a few before that). I'll be more careful in the future.

>  
>  Kind regards
>  Till 
Thanks for the packages. I am getting them back into fedora. I should
be able to push them back at the beginning of next week!

Regards,
-- 
Julien Enselme
http://www.jujens.eu/

[Till Maas]

On Wed, Oct 19, 2016 at 01:34:18PM +0200, Julien Enselme wrote:

>  I discovered this morning that a package I co-maintain was retired
>  (ccnet [1]) because one of its dependency was retired (libzdb [2]). I
>  learned it only because we have an open bug on it that change assigner
>  because of this fact. I'll call this notification thanks to luck. 
>  [1] https://admin.fedoraproject.org/pkgdb/package/rpms/ccnet/
>  [2] https://admin.fedoraproject.org/pkgdb/package/rpms/libzdb/ 
If you want to maintain these packages, I can unretire them for you and
set you as main admin easily within two weeks of the retirement.

Kind regards
Till

[Julien Enselme]

On Thu, 2016-10-20 at 22:42 +0200, Till Maas wrote:
>  
>  On Wed, Oct 19, 2016 at 01:34:18PM +0200, Julien Enselme wrote:
>  
>  > 
>  > 
>  > I discovered this morning that a package I co-maintain was retired
>  > (ccnet [1]) because one of its dependency was retired (libzdb [2]).
>  > I
>  > learned it only because we have an open bug on it that change
>  > assigner
>  > because of this fact. I'll call this notification thanks to luck.
>  
>  > 
>  > 
>  > [1] https://admin.fedoraproject.org/pkgdb/package/rpms/ccnet/
>  > [2] https://admin.fedoraproject.org/pkgdb/package/rpms/libzdb/
>  
>  If you want to maintain these packages, I can unretire them for you
>  and
>  set you as main admin easily within two weeks of the retirement.
>  
>  Kind regards
>  Till 
That would be great! I'll also need two packages retired because ccnet
was:

seafile: https://admin.fedoraproject.org/pkgdb/package/rpms/seafile/
seafile-client:
https://admin.fedoraproject.org/pkgdb/package/rpms/seafile-client/

Regards,
-- 
Julien Enselme
http://www.jujens.eu/