vel@lists.fedoraproject.org> wrote:
> Hello.
>
> According to non-responsive maintainer procedure for tchaikov, I'm
> asking here if anyone know how to reach out for the maintainer.
>
> RHBZ ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1778081
>
> --
> Sincerely,
> V
Hello.
According to non-responsive maintainer procedure for tchaikov, I'm
asking here if anyone know how to reach out for the maintainer.
RHBZ ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1778081
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1782622
This bug is part of the non-responsive maintainer procedure for
davidcl, following
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
.
Many of your packages are FTBFS in rawhide, including
https://bugzilla.redhat.com/show_bug.cgi?id=1778701
Xavier Bachelot changed:
What|Removed |Added
Status|NEW |CLOSED
Resolution|---
Xavier Bachelot writes:
> As offered in the bug, I can help with maintaining
> perl-Crypt-OpenSSL-X509. My FAS username is xavierb.
> I'll reassign the EL8 branch bug to me and take care of it. I'll also
> take care of updating to the recently released 1.813 in master.
1.813 is complete on
On 02/12/2019 19:15, Wes Hardaker wrote:
Xavier Bachelot writes:
I've tried to get in touch with Wes Hardaker about
perl-Crypt-OpenSSL-X509 for 2 months. The bug was left untouched, even
after setting need-info flag. I've also tried to reach to him by
direct mail.
Hi, and sorry both.
I've
Xavier Bachelot writes:
> I've tried to get in touch with Wes Hardaker about
> perl-Crypt-OpenSSL-X509 for 2 months. The bug was left untouched, even
> after setting need-info flag. I've also tried to reach to him by
> direct mail.
Hi, and sorry both.
I've been swamped lately and haven't had
https://bugzilla.redhat.com/show_bug.cgi?id=1778701
Wes Hardaker changed:
What|Removed |Added
Doc Type|--- |If docs needed, set a value
---
> Anyone knows how to contact him ?
>
> Here's the non-responsive maintainer bug :
> https://bugzilla.redhat.com/show_bug.cgi?id=1778699
>
> The following bugs are assigned to him:
> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED=iarnell%40gmail.com_t
bug was left untouched, even after setting
> need-info flag. I've also tried to reach to him by direct mail.
>
> Anyone knows how to contact him ?
>
> Here's the non-responsive maintainer bug :
> https://bugzilla.redhat.com/show_bug.cgi?id=1778699
>
> The following
to reach to him by direct mail.
>
> Anyone knows how to contact him ?
>
> Here's the non-responsive maintainer bug :
> https://bugzilla.redhat.com/show_bug.cgi?id=1778698
>
> The following bugs are assigned to him:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW
Hi,
I've tried to get in touch with Ian Arnell about perl-Crypt-Rijndael for
almost 2 months. The bug was left untouched, even after setting
need-info flag. I've also tried to reach to him by direct mail.
Anyone knows how to contact him ?
Here's the non-responsive maintainer bug :
https
https://bugzilla.redhat.com/show_bug.cgi?id=1778699
Xavier Bachelot changed:
What|Removed |Added
Assignee|mkre...@gmail.com |iarn...@gmail.com
Doc
Hi,
I've tried to get in touch with Matias Kreder about perl-Crypt-Rijndael
for almost 2 months. The bug was left untouched, even after setting
need-info flag. I've also tried to reach to him by direct mail.
Anyone knows how to contact him ?
Here's the non-responsive maintainer bug :
https
Hi,
I've tried to get in touch with Wes Hardaker about
perl-Crypt-OpenSSL-X509 for 2 months. The bug was left untouched, even
after setting need-info flag. I've also tried to reach to him by direct
mail.
Anyone knows how to contact him ?
Here's the non-responsive maintainer bug :
https
https://bugzilla.redhat.com/show_bug.cgi?id=1778701
Bug ID: 1778701
Summary: Non-responsive maintainer check for hardaker
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component
https://bugzilla.redhat.com/show_bug.cgi?id=1778699
Bug ID: 1778699
Summary: Non-responsive maintainer check for iarnell
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: perl
https://bugzilla.redhat.com/show_bug.cgi?id=1778698
Bug ID: 1778698
Summary: Non-responsive maintainer check for delete
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: perl
On 15. 11. 19 20:50, Fernando Nasser wrote:
As for guava, it would be important to determine which other of our
packages depend on it. It was probably with Hui for being used by maven
or some of its plugins, but we should make sure there aren't any other
users of that package. Woul'd you be
On 2019-11-14 5:03 a.m., Fabio Valentini wrote:
> Hi everybody,
Hi Fabio,
All the maven-*-plugin packages were related to the mvn command we used
to maintain in Fedora to build Maven-based software.
It was a modified maven that would use RPMs to provide the dependent
artifacts. We initially
Hi everybody,
Following the policy for non-responsive package maintainers [0], I'm
asking here if anybody knows how to contact huwang. Hui, if you're
still interested in maintaining your packages, please respond.
Some of their packages are broken on fedora 31+ due to retired Java
dependencies,
Hi everybody,
Following the policy for non-responsive package maintainers [0], I'm
asking here if anybody knows how to contact dwalluck. David, if you're
reading this, and are still interested in maintaining hamcrest, please
respond.
His one package (hamcrest) is pretty outdated, and this is
Hi everybody,
Following the policy for non-responsive package maintainers [0], I'm
asking here if anybody knows how to contact weli. Weinan, if you're
still interested in maintaining your packages, please respond.
Some of his packages are broken on fedora 31+ due to retired Java
dependencies,
Hi everybody,
Following the policy for non-responsive package maintainers [0], I'm
asking here if anybody knows how to contact rfenkhuber. Roman, if
you're still interested in maintaining your packages, please respond.
Some of his packages are broken on fedora 31+ due to retired Java
Hi,
I'm sending this e-mail according to non-responsive maintainer policy
with link to created issue in bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1765093
This maintainer has also two other issues on him:
https://bugzilla.redhat.com/show_bug.cgi?id=1605696
https
Hello,
In accordance with Fedora's non-responsive maintainer policy, I'm
sending this message in attempt to contact Jamie Nguyen (jamielinux).
Required non-responsive maintainer bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1760898
Open unaddressed bugs (219 in total):
https
Andreas Bierfert writes:
> On Thu, 2019-10-10 at 14:23 -0400, Robbie Harwood wrote:
>> Hello,
>>
>> In accordance with Fedora non-responsive maintainer policy, I'm
>> sending this message in attempt to contact Andreas Bierfert (awjb).
>>
>> Required
... and that's the wrong list. My bad.
Thanks,
--Robbie
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Hello,
In accordance with Fedora non-responsive maintainer policy, I'm sending
this message in attempt to contact Andreas Bierfert (awjb).
Required non-responsive maintainer bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1760528
Open unaddressed bugs (53 in total):
https://bugzilla.redhat.com
A new non-responsive maintainer policy has been approved [1].
This announcement is a bit late because it took a while to update the
documentation and add all the necessary templates in bugzilla.
The new policy is at [2] (diff [3]).
tl;dr:
When a maintainer is not responding to bug reports
On Thu, Sep 26, 2019 at 06:59:37AM -0500, Richard Shaw wrote:
> On Thu, Sep 26, 2019 at 6:35 AM Zbigniew Jędrzejewski-Szmek <
> zbys...@in.waw.pl> wrote:
>
> >
> > The process is streamlined to require fewer steps from the reporter
> > and to provide quicker access to the package.
> > FESCo takes
On Thu, Sep 26, 2019 at 6:35 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
>
> The process is streamlined to require fewer steps from the reporter
> and to provide quicker access to the package.
> FESCo takes care of the weekly reminders through the bug on its tracker.
> It is
A new non-responsive maintainer policy has been approved [1].
This announcement is a bit late because it took a while to update the
documentation and add all the necessary templates in bugzilla.
The new policy is at [2] (diff [3]).
tl;dr:
When a maintainer is not responding to bug reports
Jenkins in a container is begging for container churn with artifacts and logs.
Jenkins *slaves* are another story,
Sent from my iPhone
> On Aug 29, 2019, at 9:38 PM, John Harris wrote:
>
>> On Thursday, August 29, 2019 11:11:43 AM MST Fabio Valentini wrote:
>> On Thu, Aug 29, 2019 at 7:51 PM
On Fri, Aug 30, 2019 at 12:54 AM Michal Srb wrote:
> /me sending the email second time as the first attempt bounced back to me
>
> Hi Greg,
>
> Thanks for bringing this to my attention. The package is, unfortunately,
> broken in all supported Fedora releases. The version of the package is the
>
/me sending the email second time as the first attempt bounced back to me
Hi Greg,
Thanks for bringing this to my attention. The package is, unfortunately,
broken in all supported Fedora releases. The version of the package is the
last stable release from 1.x branch, but upstream is now (and has
On Thursday, August 29, 2019 11:11:43 AM MST Fabio Valentini wrote:
> On Thu, Aug 29, 2019 at 7:51 PM Greg Hellings
> wrote:
> >
> >
> > The jenkins pacakge is fearfully out of date and seems unmaintained. Does
> > anyone know how to get in touch with the maintainer(s) of the package?
>
> >
> >
>
On Thu, Aug 29, 2019 at 7:51 PM Greg Hellings wrote:
>
> The jenkins pacakge is fearfully out of date and seems unmaintained. Does
> anyone know how to get in touch with the maintainer(s) of the package?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1560603
It's not only out of date, but also
The jenkins pacakge is fearfully out of date and seems unmaintained. Does
anyone know how to get in touch with the maintainer(s) of the package?
https://bugzilla.redhat.com/show_bug.cgi?id=1560603
--Greg
___
devel mailing list --
Replied on https://pagure.io/fesco/issue/2212
من: Vitaly Zaitsev via devel
تم الإرسال: 20/ذو الحجة/1440 11:27 ص
إلى: devel@lists.fedoraproject.org
نسخة: Vitaly Zaitsev
الموضوع: Non-responsive maintainer Mosaab Alzoubi
Hello all.
According to non-responsive
Hello all.
According to non-responsive maintainer procedure for moceap, I'm asking
here if anyone know how to reach out for the maintainer.
RHBZ ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1740611
RHBZ ticket with countdown:
https://bugzilla.redhat.com/show_bug.cgi?id=1733802
> What is certain is that I won't have time to proverbially sit down (on
> my standing desk) and track bugs down, either as a reporter or as a
> maintainer. Same thing for my stalled review requests I was hoping to
> get done much sooner.
I may be back on track in a couple weeks actually, I may
Hello,
does anybody know how to contact Gaël Chamoulaud (gchamoul)?
* https://src.fedoraproject.org/rpms/facter/pull-request/4
* https://bugzilla.redhat.com/show_bug.cgi?id=1733765
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
Hi,
> By following the process, all of your packages will get orphaned.
> If that is your desire, shall we do it directly?
That part, please don't :)
The reason why I'm encouraging people to become co-maintainers is
because I won't be unavailable forever, but longer than the orphan
grace
Hi,
does anyone know how to reach out for the maintainer of nagstamon? There's a
FTBFS bug [1] since ages without any response so far.
It would be bad to see this useful package go away from Fedora.
Regards, Raphael
[25.07.19 07:23] whoowns nagstamon
[25.07.19 07:23] owner: jaur; admin:
On 24. 07. 19 18:51, Dridi Boukelmoune wrote:
Greetings fellow package maintainers,
I'm starting the non-responsive maintainer process on myself because
the time I can dedicate to Fedora will significantly drop for the next
3 months. It wasn't that much to begin with...
I don't think I
Greetings fellow package maintainers,
I'm starting the non-responsive maintainer process on myself because
the time I can dedicate to Fedora will significantly drop for the next
3 months. It wasn't that much to begin with...
I don't think I will be able to follow up on anything, especially
ohhh, i'm alive, sorry, i'll repply soon
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
with the non-responsive maintainer process.
Thanks,
Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code
Hello!
According to Non-responsive Maintainer Policy I'm asking the maintainer
to respond and resolve issues with package zimlib.
RHBZ ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1690432
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org
On Tue, Mar 12, 2019 at 11:11:01AM +0100, Miro Hrončok wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1659737
>
> Anyone knows how to contact the maintainer?
FWIW we've dropped the python-guestfs (ie. Python 2) bindings in
Fedora 31, and I believe that will stop imagefactory from even
On 12. 03. 19 13:44, Chris Lalancette wrote:
Sorry for not responding earlier.
I'm not really involved with imagefactory at all, though I am still the
maintainer of Oz. As Daniel pointed out, you'll want to start with Ian Mcleod
for that package (he can point you in the right direction).
Dne 12. 03. 19 v 11:11 Miro Hrončok napsal(a):
> https://bugzilla.redhat.com/show_bug.cgi?id=1659737
>
> Anyone knows how to contact the maintainer?
>
Last time I was in contact with Chris was via his email:
clalance...@gmail.com
He is still active from time to time:
On Tue, Mar 12, 2019 at 10:12 AM Miro Hrončok wrote:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1659737
>
> Anyone knows how to contact the maintainer?
He is occasionally active, he still has an active github account, you
can probably get hold of him via contact details there.
On Tue, Mar 12, 2019 at 11:11:01AM +0100, Miro Hrončok wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1659737
>
> Anyone knows how to contact the maintainer?
According to git history Chris hasn't touched that package in dist-git
since the very first import in 2011, so is likely the wrong
https://bugzilla.redhat.com/show_bug.cgi?id=1659737
Anyone knows how to contact the maintainer?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On Mon, Feb 25, 2019 at 1:32 PM Barry Scott wrote:
>
>
>
> > On 25 Feb 2019, at 13:07, Stephen Gallagher wrote:
> >
> > On Tue, Feb 19, 2019 at 1:59 PM Barry Scott wrote:
> >
> >> Just heard about this. I'm the author of pysvn.
> >>libmodulemd
> >> I'd be willing to maintain the fedora package
> On 25 Feb 2019, at 13:07, Stephen Gallagher wrote:
>
> On Tue, Feb 19, 2019 at 1:59 PM Barry Scott wrote:
>
>> Just heard about this. I'm the author of pysvn.
>>
>> I'd be willing to maintain the fedora package of
>> pysvn. What do you need me to do?
>>
>> I am an active user and
On Tue, Feb 19, 2019 at 1:59 PM Barry Scott wrote:
> Just heard about this. I'm the author of pysvn.
>
> I'd be willing to maintain the fedora package of
> pysvn. What do you need me to do?
>
> I am an active user and developer on Fedora and I create and maintain
> a numbers of RPMs in my work
Hello all,
according to the policy [1], I am starting a non-responsive maintainer
process to be able to update dependency of one of my packages. I filled
a bug several months ago and explicitly asked for ans answer last week
[2] without any response.
Cedric (in cc) does not look active in Fedora
On Fri, Feb 22, 2019 at 2:19 PM Rick Elrod wrote:
> I'm here, I'm here. ;)
>
> Richard, would it be okay if I add you as a committer/comaintainer on
> that package? As you can tell, I have not had time to properly
> maintain it of late.
>
That'll work. Thanks!
Richard
I'm here, I'm here. ;)
Richard, would it be okay if I add you as a committer/comaintainer on
that package? As you can tell, I have not had time to properly
maintain it of late.
Rick
On Fri, Feb 22, 2019 at 11:26 AM Richard Shaw wrote:
>
> Is anyone able to contact Rick? A BZ ticket[1] has not
Is anyone able to contact Rick? A BZ ticket[1] has not gotten a response
from some time.
Use fedora-active-user it looks like he's logged in recently but all other
activity has been from last year:
$ ./fedora_active_user.py --user codeblock --email rel...@redhat.com
Last login in FAS:
On 19. 02. 19 20:00, Barry Scott wrote:
Sorry this was supposed to go only to Kevin.
Actually, it's perfect that this went to devel.
Everybody knows what's going on.
The true spirit of open source and open collaboration. Please, keep doing this.
Good luck with packaging, Barry!
--
Miro
Sorry this was supposed to go only to Kevin.
Barry
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List
>>>
>>>> I've been maintaining this for several years since the main admin
>>>> (ravenoak) vanished from Fedora. I don't use it anymore (and most of
>>>> the world has long since switched to git...) and it has yet again
>>>> failed to rebuild during
>>> (ravenoak) vanished from Fedora. I don't use it anymore (and most of
>>> the world has long since switched to git...) and it has yet again
>>> failed to rebuild during the mass rebuild.
>>>
>>> I'm initiating the Non-Responsive Maintainer process for rave
From https://pagure.io/fesco/issue/2067:
> From discussing with folks at IBM it appears Vicky is no longer
> working on tss2, and her contact address bounces.
If anyone knows the new address, please let her know.
Zbyszek
___
devel mailing list --
>> the world has long since switched to git...) and it has yet again
>> failed to rebuild during the mass rebuild.
>>
>> I'm initiating the Non-Responsive Maintainer process for ravenoak so
>> the main admin will be cleared. If anyone wants to take it over, I'll
>>
Hello everybody,
Due this claim, I built this request many times after this req:
https://src.fedoraproject.org/rpms/goldendict/pull-request/1
https://koji.fedoraproject.org/koji/buildinfo?buildID=1182366
https://koji.fedoraproject.org/koji/buildinfo?buildID=1182362
And the problem from Koji
rebuild during the mass rebuild.
>
> I'm initiating the Non-Responsive Maintainer process for ravenoak so
> the main admin will be cleared. If anyone wants to take it over, I'll
> happily make them a comaintainer on request.
No one seems to be jumping at taking this over, so I'm pro
I've been maintaining this for several years since the main admin
(ravenoak) vanished from Fedora. I don't use it anymore (and most of
the world has long since switched to git...) and it has yet again
failed to rebuild during the mass rebuild.
I'm initiating the Non-Responsive Maintainer process
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
According Non-responsive Maintainer Policy I'm asking the maintainer
to respond second time and resolve issues with package goldendict.
RHBZ tickets: https://bugzilla.redhat.com/show_bug.cgi?id=1667084 and
https://bugzilla.redhat.com
Does anybody know how to contact him?
The last activity dates 2010.
I didn't follow procedure fully yet, but I'm 99% sure that there will
be no reply in bugzilla.
But I'm starting it now: https://bugzilla.redhat.com/show_bug.cgi?id=1650661
___
devel
> On 1. Oct 2018, at 12:00, Emmanuel Seyman wrote:
>
> * Joseph D. Wagner [01/10/2018 02:47] :
>>
>> Per policy for non-responsive maintainers
>> (https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers)
>
> Folks, when you're asking us if anyone knows how to contact the
* Joseph D. Wagner [01/10/2018 02:47] :
>
> Per policy for non-responsive maintainers
> (https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers)
Folks, when you're asking us if anyone knows how to contact the maintainer,
you might want to consider actually giving us his name
Per policy for non-responsive maintainers
(https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers)
There has been an outstanding update request since March 24, 2018.
https://bugzilla.redhat.com/show_bug.cgi?id=1560212
Joseph D. Wagner
Hi Peter,
I could help to co-maintain the package of pyvmomi in case of an orphaning
process. Maybe it's faster to let a provenpackager apply your patch to bump to
version 6.7, it should be API compatible as VMware promises.
We should also try to ask on the special python mailing list.
Regards,
Does anyone know how to contact Michael Rice, maintainer of the package
python-pyvmomi? He hasn't made any commits since the package was first
released.
https://bugzilla.redhat.com/show_bug.cgi?id=1493946
--
Peter Oliver
___
devel mailing list --
Dne 17.9.2018 v 09:48 Haïkel napsal(a):
> Le lun. 17 sept. 2018 à 08:12, Mattia Verga a écrit
> :
>>> Le dim. 16 sept. 2018 à 11:27, Fabio Valentini >> a écrit :
>>>
>>>
>>> The policy mention that you have to try contacting the maintainer
>>> *first*, you never sent me an email or pinged me
Le lun. 17 sept. 2018 à 08:12, Mattia Verga a écrit :
>
> > Le dim. 16 sept. 2018 à 11:27, Fabio Valentini > a écrit :
> >
> >
> > The policy mention that you have to try contacting the maintainer
> > *first*, you never sent me an email or pinged me on irc.
> > I don't like this kind of
> Le dim. 16 sept. 2018 à 11:27, Fabio Valentini écrit :
>
>
> The policy mention that you have to try contacting the maintainer
> *first*, you never sent me an email or pinged me on irc.
> I don't like this kind of passive-aggressive approach, had you
> contacted me, we would have sorted this
On 16.9.2018 21:43, Rex Dieter wrote:
Miro Hrončok wrote:
On 16.9.2018 14:42, Haïkel wrote:
The policy mention that you have to try contacting the maintainer
*first*,
As a side note, where exactly does it mention that? (Note that it comes
as a reasonable thing to do, but I don't see it in
Rex Dieter wrote:
> Miro Hrončok wrote:
>
>> On 16.9.2018 14:42, Haïkel wrote:
>>> The policy mention that you have to try contacting the maintainer
>>> *first*,
>>
>> As a side note, where exactly does it mention that? (Note that it comes
>> as a reasonable thing to do, but I don't see it in
Miro Hrončok wrote:
> On 16.9.2018 14:42, Haïkel wrote:
>> The policy mention that you have to try contacting the maintainer
>> *first*,
>
> As a side note, where exactly does it mention that? (Note that it comes
> as a reasonable thing to do, but I don't see it in the policy.)
It does
On 16.9.2018 14:42, Haïkel wrote:
The policy mention that you have to try contacting the maintainer
*first*,
As a side note, where exactly does it mention that? (Note that it comes
as a reasonable thing to do, but I don't see it in the policy.)
I think we should actually make this the step
deprecate that.
> Does anybody know how to contact Haïkel Guémar (hguemar), or has heard
> from him recently? According to fedora-active-user, he is - somewhat -
> active? If not, I will continue the non-responsive maintainer process
> according to the Policy.
>
> Fabio
The pol
to fedora-active-user, he is - somewhat -
active? If not, I will continue the non-responsive maintainer process
according to the Policy.
Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le
On 23.8.2018 07:32, Joseph D. Wagner wrote:
It hasn't been updated in over a year, and it's updates are sorely needed.
Trying to get updated before the beta freeze.
https://bugzilla.redhat.com/show_bug.cgi?id=1462583
See also https://bugzilla.redhat.com/show_bug.cgi?id=1610474
--
Miro
To work on this does one need to be sponsored ? If no & if the maintainer
doesn't repsond i can start work immediately tomorrow.
Recently began packaging would love to work on this.
On Thu, 23 Aug 2018, 12:23 Joseph D. Wagner, wrote:
> It hasn't been updated in almost a year, and it's updates
It hasn't been updated in almost a year, and it's updates are sorely
needed.
Trying to get updated before the beta freeze.
https://bugzilla.redhat.com/show_bug.cgi?id=1508227
Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
It hasn't been updated in over a year, and it's updates are sorely needed.
Trying to get updated before the beta freeze.
https://bugzilla.redhat.com/show_bug.cgi?id=1462583
Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To
Hi,
Per Non-Responsive Maintainer policy, I'm attempting to contact Pavel
Alexeev (hubbitus). I have not gotten a response to a pull request or bug
report for DivFix++ package.
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1599541
Thanks,
Scott
Hi,
Per Non-Responsive Maintainer policy, I'm attempting to contact Pavel
Cahyna (pcahyna). I have not gotten a response to a pull request or bug
report.
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1599538
Thanks,
Scott
___
devel mailing
s I don't get news from him. And
>> when I say "ages" I mean "years".
>> Hope everything is okay on his side.
>>
>>
>>
>>
>> On 27 July 2018 at 13:21, Vascom wrote:
>>
>>> Hello!
>>>
>>> According
n his side.
>
>
>
>
> On 27 July 2018 at 13:21, Vascom wrote:
>
>> Hello!
>>
>> According Non-responsive Maintainer Policy I'm asking the maintainer
>> to respond and resolve FTBFS issues with package kio-gdrive.
>>
>> RHBZ : https://b
I know Wolnei Junior but it's been ages I don't get news from him. And
when I say "ages" I mean "years".
Hope everything is okay on his side.
On 27 July 2018 at 13:21, Vascom wrote:
> Hello!
>
> According Non-responsive Maintainer Policy I'm asking the mainta
Hello!
According Non-responsive Maintainer Policy I'm asking the maintainer
to respond and resolve FTBFS issues with package kio-gdrive.
RHBZ : https://bugzilla.redhat.com/show_bug.cgi?id=1601422
--
Best regards,
Vasiliy Glazov
___
devel mailing list
On Sunday, 22 July 2018 at 19:00, Vitaly Zaitsev wrote:
> Hello!
>
> According Non-responsive Maintainer Policy I'm asking the maintainer
> to respond and resolve issues with packages spdlog and json.
>
> RHBZ (spdlog): https://bugzilla.redhat.com/show_bug.cgi?id=1468817
>
Hi Vitaly,
According to the team calendar he is on his PTO since Thursday. He should
be back tomorrow I guess :).
On Sun, Jul 22, 2018 at 7:01 PM Vitaly Zaitsev
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello!
>
> According Non-responsive Maintainer
401 - 500 of 879 matches
Mail list logo
