Hello all,
I would like to submit a change proposal for the unresponsive package
maintainer policy.
The policy now says [1] "/File a bug against the package in Bugzilla
asking for the maintainer to respond. This bug should list the
outstanding issues they need to address. This is a must./"
I
Compose started at Sat Dec 7 07:15:02 UTC 2013
Broken deps for armhfp
--
[avro]
avro-mapred-1.7.5-1.fc20.noarch requires hadoop-mapreduce
avro-mapred-1.7.5-1.fc20.noarch requires hadoop-client
[blueman]
blueman-1.23-7
On Sat, Dec 07, 2013 at 11:44:47AM +0100, Mattia Verga wrote:
> Hello all,
> I think this kind of bug should not be filled against the single
> package, but something like against infrastructure. Also it should
> block all bugs assigned to that user.
>
> This can be useful if a user maintains sev
Hello,
We have an open bug [1] becouse the primary mantainer of the scala
package shows no response for open bugs.
Unfortunately, the original bug reporter seems to lost the inerest
to finish the none-responsive maintainer process.
So I would like to ask, if it ok to reassign the bug to myself w
Tried to yum update and the systemd packages are not signed.
=
PackageArch Version
Repository
* Brian Millett [07/12/2013 07:51] :
>
> Tried to yum update and the systemd packages are not signed.
https://lists.fedoraproject.org/pipermail/test-announce/2013-December/000832.html
Emmanuel
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/de
Il 07/12/2013 13:20, Jochen Schmitt ha scritto:
What should happens, if the reporter of the nune-responsive maintainer
bug only want to takeover a single package, but the unresponsive
maintainer owns several packages? But I can imagine, that there may be
helpful to use the none-responsive maint
Sorry for any confusion, Jochen. The next step in the process is notifying
fedora-devel, which it appears we're doing now.
Jochen, would your preferred resolution be to be the primary maintainer (with
one or more co-maintainers)?
best,
wb
- Original Message -
> From: "Jochen Schmitt"
On Sat, Dec 07, 2013 at 09:56:47AM -0500, Will Benton wrote:
> Sorry for any confusion, Jochen. The next step in the process is notifying
> fedora-devel, which it appears we're doing now.
>
> Jochen, would your preferred resolution be to be the primary maintainer (with
> one or more co-maintain
Michael scherer wrote:
> That's already part of the life of packagers. For example, suddenly, gcc
> decide to be stricter and suddenly, some VCS written in C++ decide to not
> compile anymore, so you have to spend 1 full day just to make it compile.
> ( of course, totally fictious example that didn
10 matches
Mail list logo
