Re: Non-responsive package maintainer - snakeyaml

2021-09-26 Thread Stefan Bluhm
Thank you for clarifying, Fabio. And for pointing out the wrong main 
maintainer. I will get in tough with the hopefully correct main maintainer.

Best wishes,

Stefan

- Ursprüngliche Mail -
Von: "Fabio Valentini" 
An: "devel" 
Gesendet: Sonntag, 26. September 2021 19:24:36
Betreff: Re: Non-responsive package maintainer - snakeyaml

On Sun, Sep 26, 2021 at 6:45 PM Stefan Bluhm
 wrote:
>
> Hello,
>
> I am following the non-responsive package maintainer process for "snakeyaml":
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
>
> Bugzilla asking for response: 
> https://bugzilla.redhat.com/show_bug.cgi?id=2007971
>
> Bugzilla asking for snakeyaml maintenance: 
> https://bugzilla.redhat.com/show_bug.cgi?id=1993621
>
> Pagure ticket indicating that the maintainer e-mail address is not actively 
> maintained anymore: https://pagure.io/releng/issue/10309
>
> Maintainer: Please add me as contributor for EPEL packages.

Just to clarify: The "not actively maintained" email address you're
talking about here is the *private bugzilla mailing list* for the
@java-maint-sig group.
Groups also cannot be main maintainer for a package, that
responsibility *always* lies with an actual person.
So complaining about non-responsiveness to a group will not help,
because it's the wrong recipient for it.

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-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Non-responsive package maintainer - snakeyaml

2021-09-26 Thread Fabio Valentini
On Sun, Sep 26, 2021 at 6:45 PM Stefan Bluhm
 wrote:
>
> Hello,
>
> I am following the non-responsive package maintainer process for "snakeyaml":
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
>
> Bugzilla asking for response: 
> https://bugzilla.redhat.com/show_bug.cgi?id=2007971
>
> Bugzilla asking for snakeyaml maintenance: 
> https://bugzilla.redhat.com/show_bug.cgi?id=1993621
>
> Pagure ticket indicating that the maintainer e-mail address is not actively 
> maintained anymore: https://pagure.io/releng/issue/10309
>
> Maintainer: Please add me as contributor for EPEL packages.

Just to clarify: The "not actively maintained" email address you're
talking about here is the *private bugzilla mailing list* for the
@java-maint-sig group.
Groups also cannot be main maintainer for a package, that
responsibility *always* lies with an actual person.
So complaining about non-responsiveness to a group will not help,
because it's the wrong recipient for it.

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-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Non-responsive package maintainer - Ray Strode (halfline), Plymouth package

2018-10-02 Thread mcatanzaro


On Tue, Oct 2, 2018 at 1:17 AM, fedora201...@nuclearsunshine.com wrote:

Hi Ray, unfortunately in some cases it doesn't though. It's currently
completely breaking boot with amdgpu+LUKS, and before that for several
months under amdgpu it was not echoing LUKS characters to screen or
otherwise updating at all after showing the LUKS prompt, making it 
seem

that password entry was not working and the boot process had frozen.


Since this is a very common setup, surely it should be a release 
blocker bug. I would propose it using the usual blocker review process.


In fact, since this bug looks like a disaster, I'm going to do that now.


I'm not jumping up and down demanding "devote all your time to fix my
Plymouth bug(s)!" ;) (I've disabled RHGB for now on my system in any
case); rather saying that if there aren't enough resources to make 
this
level of maintenance realistic at the moment, it might be worth 
looking

at whether it's still a good idea for Plymouth to continue to be
enabled by default?


If a bug prevents booting, please propose it using the blocker review 
process. Unless it requires a really esoteric hardware setup, it's 
probably a blocker.


Michael
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer - Ray Strode (halfline), Plymouth package

2018-10-01 Thread fedora2018q2
On Mon, 2018-10-01 at 16:52 -0400, Ray Strode wrote:
> Hi,
> On Mon, Oct 1, 2018 at 4:29 PM Stephen <
> fedora201...@nuclearsunshine.com> wrote:
> > The maintainer for Plymouth, Ray Strode (halfline), is not
> > addressing
> > its bugs on RHBZ (one response all year on a single bug, accepting
> > a
> > patch), including showstopper bugs that are preventing boot
> > entirely in
> > some instances.
> 
> I'm around, but I work on a lot of stuff. plymouth doesn't get a lot
> of attention,
> since it basically works.

Hi Ray, unfortunately in some cases it doesn't though. It's currently
completely breaking boot with amdgpu+LUKS, and before that for several
months under amdgpu it was not echoing LUKS characters to screen or
otherwise updating at all after showing the LUKS prompt, making it seem
that password entry was not working and the boot process had frozen.

>  It doesn't see as much development as some
> components because other parts of the stack have been prioritized.
> 
> Having said that, Hans de Goede has taken up the mantle of improving
> the
> boot experience recently, including some changes to plymouth. So you
> should
> see some changes soon.
> 
> plymouth does get fixes for blocker issues when necessary, and i
> still give it
> some attention upstream.
> 
> It is receiving the amount resources we considered appropriate at the
> moment.

Plymouth sits in the unusual position of being simultaneously boot-
critical when enabled, and not actually necessary to the boot process
(AFAIK?)

I believe there's a fair case to be made that for a component with
these unusual characteristics to be default-enabled in Fedora, it needs
enough maintenance resources available for it to continue to work
(modulo short breakages) on at least non-esoteric hardware with which
Fedora otherwise works.

I'm not jumping up and down demanding "devote all your time to fix my
Plymouth bug(s)!" ;) (I've disabled RHGB for now on my system in any
case); rather saying that if there aren't enough resources to make this
level of maintenance realistic at the moment, it might be worth looking
at whether it's still a good idea for Plymouth to continue to be
enabled by default?

Alternatively, if a reasonably flexible blacklist is possible (or
exists?), that might be lower-maintenance, and obviously less nuclear
option than default-disabling Plymouth.

> 
> --Ray
> ___
> 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 Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer - Ray Strode (halfline), Plymouth package

2018-10-01 Thread Ray Strode
Hi,
On Mon, Oct 1, 2018 at 4:29 PM Stephen  wrote:
> The maintainer for Plymouth, Ray Strode (halfline), is not addressing
> its bugs on RHBZ (one response all year on a single bug, accepting a
> patch), including showstopper bugs that are preventing boot entirely in
> some instances.
I'm around, but I work on a lot of stuff. plymouth doesn't get a lot
of attention,
since it basically works. It doesn't see as much development as some
components because other parts of the stack have been prioritized.

Having said that, Hans de Goede has taken up the mantle of improving the
boot experience recently, including some changes to plymouth. So you should
see some changes soon.

plymouth does get fixes for blocker issues when necessary, and i still give it
some attention upstream.

It is receiving the amount resources we considered appropriate at the moment.

--Ray
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer process - backintime

2016-02-13 Thread Raphael Groner
Another problem package cicku has to react in reasonable short time for is now 
docky with FTBFS in rawhide cause of gcc6:
https://bugzilla.redhat.com/show_bug.cgi?id=1307430
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer process - backintime

2016-02-12 Thread Jeff Backus
On Fri, Feb 12, 2016 at 5:04 AM, Johannes Lips 
wrote:

> Dear all,
>
> I would like to formally send a mail requesting some feedback from cicku
> regarding the maintenance of the backintime package.
> There is one open bug, which requests an update [1] and additionally a
> trac ticket [2] was also opened, not by me.
> I can see, that with an upgrade to later versions we'll loose the
> differentiation between a KDE and Gnome GUI, but I don't see why that
> really is an issue.
> Additionally two request to become co-maintainer are unanswered so far, so
> I hope that we'll get that sorted pretty quick.
> Possibly there are some Chinese New Year festivities, so perhaps we'll
> give him some more time, but I would love to get some feedback.
>
> Johannes
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1186184
> [2] https://fedorahosted.org/fesco/ticket/1542
>

CCing Christopher.

jeff

-- 
Jeff Backus
jeff.bac...@gmail.com
http://github.com/jsbackus
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer process - backintime

2016-02-12 Thread Josh Boyer
On Fri, Feb 12, 2016 at 2:55 PM, Johannes Lips  wrote:
>> On Fri, Feb 12, 2016 at 1:48 PM, Johannes Lips 
>> >
>> You make a lot of assumptions in that statement.  People filter email
>> quite a bit and relying on bugzilla mail alone is not sufficient.
>>
>> I find it ironic that your original email said "I would like to
>> formally send a mail requesting some feedback from cicku.." but you
>> didn't bother to email him directly.  That doesn't strike me as very
>> formal.  I'm under no illusions that he is likely to respond to direct
>> contact either, but it should at least be attempted.
>>
> Why do I need to defend myself for following, perhaps not perfectly, the 
> normal procedure in these cases and additionally I offered my help 
> maintaining that package.
> I and another packager requested co-maintainership and are willing to help 
> out, so I really don't see why I need to defend myself for the willingness to 
> give up my valuable spare time.

I asked if you had sent him an email directly and instead of doing
that you waved off my question with assumptions.  I think it's
fantastic you want to pick up the packages and I fully support that.
However your attempt to follow the process is one of many lately that
don't actually follow the process and seem to want to short-circuit to
the end result.

The purpose of having a process is to follow it because we have
reasons for doing so.  Reminding people of that is part of the deal.
Conversely, if those reasons don't make sense then perhaps we need to
revise the process.  Either way, having a discussion around it isn't
an attack that you need to defend yourself against.

josh
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer process - backintime

2016-02-12 Thread Johannes Lips
> On Fri, Feb 12, 2016 at 1:48 PM, Johannes Lips  wrote:
> 
> You make a lot of assumptions in that statement.  People filter email
> quite a bit and relying on bugzilla mail alone is not sufficient.
> 
> I find it ironic that your original email said "I would like to
> formally send a mail requesting some feedback from cicku.." but you
> didn't bother to email him directly.  That doesn't strike me as very
> formal.  I'm under no illusions that he is likely to respond to direct
> contact either, but it should at least be attempted.
> 
Why do I need to defend myself for following, perhaps not perfectly, the normal 
procedure in these cases and additionally I offered my help maintaining that 
package. 
I and another packager requested co-maintainership and are willing to help out, 
so I really don't see why I need to defend myself for the willingness to give 
up my valuable spare time.
Johannes
> josh
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer process - backintime

2016-02-12 Thread Josh Boyer
On Fri, Feb 12, 2016 at 8:48 AM, Richard Shaw  wrote:
> On Fri, Feb 12, 2016 at 7:47 AM, Josh Boyer 
> wrote:
>>
>> On Fri, Feb 12, 2016 at 5:04 AM, Johannes Lips 
>> wrote:
>> > Dear all,
>> >
>> > I would like to formally send a mail requesting some feedback from cicku
>> > regarding the maintenance of the backintime package.
>>
>> Did you actually email cicku directly?  I don't see him on CC.
>
>
> He may be on another Fedora hiatus again. I have a stalled review from last
> October and have attempted to ping him both in the BZ and direct email with
> no response.

That is helpful to know.  Thank you for chiming in.

josh
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer process - backintime

2016-02-12 Thread Josh Boyer
On Fri, Feb 12, 2016 at 1:48 PM, Johannes Lips  wrote:
>> On Fri, Feb 12, 2016 at 5:04 AM, Johannes Lips 
>> >
>> Did you actually email cicku directly?  I don't see him on CC.
>>
> Well, apparently I didn't add him to this e-mail, but he should have received 
> enough notifications from bugzilla already. Additionally from someone who 
> maintains more than 200 packages in fedora, I kind of expect that he is 
> reachable within a reasonable time-frame. Otherwise it might be too much 
> hassle, if something needs to be fixed.

You make a lot of assumptions in that statement.  People filter email
quite a bit and relying on bugzilla mail alone is not sufficient.

I find it ironic that your original email said "I would like to
formally send a mail requesting some feedback from cicku.." but you
didn't bother to email him directly.  That doesn't strike me as very
formal.  I'm under no illusions that he is likely to respond to direct
contact either, but it should at least be attempted.

josh
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer process - backintime

2016-02-12 Thread Johannes Lips
> On Fri, Feb 12, 2016 at 5:04 AM, Johannes Lips  wrote:
> 
> Did you actually email cicku directly?  I don't see him on CC.
> 
Well, apparently I didn't add him to this e-mail, but he should have received 
enough notifications from bugzilla already. Additionally from someone who 
maintains more than 200 packages in fedora, I kind of expect that he is 
reachable within a reasonable time-frame. Otherwise it might be too much 
hassle, if something needs to be fixed.

Johannes
> josh
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer process - backintime

2016-02-12 Thread Richard Shaw
On Fri, Feb 12, 2016 at 7:47 AM, Josh Boyer 
wrote:

> On Fri, Feb 12, 2016 at 5:04 AM, Johannes Lips 
> wrote:
> > Dear all,
> >
> > I would like to formally send a mail requesting some feedback from cicku
> regarding the maintenance of the backintime package.
>
> Did you actually email cicku directly?  I don't see him on CC.


He may be on another Fedora hiatus again. I have a stalled review from last
October and have attempted to ping him both in the BZ and direct email with
no response.

Thanks,
Richard
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer process - backintime

2016-02-12 Thread Josh Boyer
On Fri, Feb 12, 2016 at 5:04 AM, Johannes Lips  wrote:
> Dear all,
>
> I would like to formally send a mail requesting some feedback from cicku 
> regarding the maintenance of the backintime package.

Did you actually email cicku directly?  I don't see him on CC.

josh
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Non-responsive package maintainer (affix)

2014-10-09 Thread Brandon Vincent
On Thu, Oct 9, 2014 at 1:55 AM, Jamie Nguyen  wrote:
> I think you should probably ignore the fact that Affix happens to be the
> first point of contact, and instead email "peter" or "jpo" who are the
> active maintainers.

I've notified them multiple times as well. BZ assigns the ticket to
the listed package owner which is the reason this issue probably
occurred in the first place.

Brandon Vincent
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Non-responsive package maintainer (affix)

2014-10-09 Thread Jamie Nguyen
On 09/10/14 06:28, Brandon Vincent wrote:
> Over the past month, I have tried contacting Keiran Smith (affix) in
> regards to nagios with no success [1].
> 
> Is anyone aware to his present status in regards to the Fedora Project
> or possibly have an alternative method to reach him?

Strangely, no successful builds from Affix in ~7 years of koji build
logs [1], and there are only 4 (trivial) commits from Affix in the git
history in July 2013.

I think you should probably ignore the fact that Affix happens to be the
first point of contact, and instead email "peter" or "jpo" who are the
active maintainers.

[1]
http://koji.fedoraproject.org/koji/packageinfo?buildStart=0&packageID=2593


-- 
Jamie Nguyen




signature.asc
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Non-responsive package maintainer

2012-04-05 Thread Jon Ciesla
On Thu, Apr 5, 2012 at 12:06 PM, Jon Ciesla  wrote:
> On Thu, Apr 5, 2012 at 11:21 AM, Caghan Demirci  wrote:
>>
>>   Hi Jon,
>>
>> On Thu, Apr 5, 2012 at 10:32 AM, Jon Ciesla  wrote:
>>>
>>> On Thu, Apr 5, 2012 at 9:19 AM, Caghan Demirci  wrote:
>>> >
>>> >   I would like to call your attention to the following bug:
>>> > https://bugzilla.redhat.com/show_bug.cgi?id=771262
>>> >
>>>
>>> The EL6 branch 0.5.2 and EL5 has 0.4.3 in git already, just not build,
>>> would those suffice until the maintainer updates them?
>>>
>>
>>   No, I am afraid I need at least 0.7.0.
>>   On CentOS 6, I have been using the Fedora 14 package for nautilus-python
>> for a long time
>> (http://koji.fedoraproject.org/koji/buildinfo?buildID=199753).  It works
>> perfectly.  All I had to do was to build from the source RPM.  It doesn't
>> require any modifications.  I am also quite certain that it would work on
>> CentOS 5.
>>   If someone can help me out, I would really appreciate it. I have been
>> running after this package for almost 6 months.
>
> Gotcha.  I'll take a peek.

Update for EL-6 is out, you can get the build from koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=311890

EL-5 wouldn't build with that version due to a lack of
gnome-python2-devel, I'll check it out.

-J

> -J
>
>>   Thanks!
>>
>>   -Caghan Demirci
>>    University of Delaware
>>
>>
>>
>> --
>> devel mailing list
>> devel@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/devel
>
>
>
> --
> in your fear, seek only peace
> in your fear, seek only love
>
> -d. bowie



-- 
in your fear, seek only peace
in your fear, seek only love

-d. bowie
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Non-responsive package maintainer

2012-04-05 Thread Jon Ciesla
On Thu, Apr 5, 2012 at 11:21 AM, Caghan Demirci  wrote:
>
>   Hi Jon,
>
> On Thu, Apr 5, 2012 at 10:32 AM, Jon Ciesla  wrote:
>>
>> On Thu, Apr 5, 2012 at 9:19 AM, Caghan Demirci  wrote:
>> >
>> >   I would like to call your attention to the following bug:
>> > https://bugzilla.redhat.com/show_bug.cgi?id=771262
>> >
>>
>> The EL6 branch 0.5.2 and EL5 has 0.4.3 in git already, just not build,
>> would those suffice until the maintainer updates them?
>>
>
>   No, I am afraid I need at least 0.7.0.
>   On CentOS 6, I have been using the Fedora 14 package for nautilus-python
> for a long time
> (http://koji.fedoraproject.org/koji/buildinfo?buildID=199753).  It works
> perfectly.  All I had to do was to build from the source RPM.  It doesn't
> require any modifications.  I am also quite certain that it would work on
> CentOS 5.
>   If someone can help me out, I would really appreciate it. I have been
> running after this package for almost 6 months.

Gotcha.  I'll take a peek.

-J

>   Thanks!
>
>   -Caghan Demirci
>    University of Delaware
>
>
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel



-- 
in your fear, seek only peace
in your fear, seek only love

-d. bowie
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Non-responsive package maintainer

2012-04-05 Thread Caghan Demirci
  Hi Jon,

On Thu, Apr 5, 2012 at 10:32 AM, Jon Ciesla  wrote:

> On Thu, Apr 5, 2012 at 9:19 AM, Caghan Demirci  wrote:
> >
> >   I would like to call your attention to the following bug:
> > https://bugzilla.redhat.com/show_bug.cgi?id=771262
> >
>
> The EL6 branch 0.5.2 and EL5 has 0.4.3 in git already, just not build,
> would those suffice until the maintainer updates them?
>
>
  No, I am afraid I need at least 0.7.0.
  On CentOS 6, I have been using the Fedora 14 package for nautilus-python
for a long time (http://koji.fedoraproject.org/koji/buildinfo?buildID=199753).
It works perfectly.  All I had to do was to build from the source RPM.  It
doesn't require any modifications.  I am also quite certain that it would
work on CentOS 5.
  If someone can help me out, I would really appreciate it. I have been
running after this package for almost 6 months.

  Thanks!

  -Caghan Demirci
   University of Delaware
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Non-responsive package maintainer

2012-04-05 Thread Jon Ciesla
On Thu, Apr 5, 2012 at 9:19 AM, Caghan Demirci  wrote:
>
>   Hi everyone!
>
>   I would like to call your attention to the following bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=771262
>
>   What is required is a build of a small and simple package for EPEL.
> However, I am unable to contact the maintainer for a long time, by any
> means.
>
>   Could another maintainer take care of this simple task?  If you feel up to
> it, it shouldn't take more than an hour.

The EL6 branch 0.5.2 and EL5 has 0.4.3 in git already, just not build,
would those suffice until the maintainer updates them?

-J

>   If no one wants to do it, then I am applying to co-maintain this package.
> I am certain I would be able to take good care of this task.  Could someone
> sponsor me to be a package maintainer?
>
>   Thanks and best wishes!
>
>   -Caghan Demirci
>    University of Delaware
>
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel



-- 
in your fear, seek only peace
in your fear, seek only love

-d. bowie
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel