Re: Can anyone contact Gérard Milmeister (gemi)?
On Tue, 2010-07-06 at 10:13 +0800, Chen Lei wrote: > Hi FESCo, > > Can we orphan his packages now? I'd like to take scons, I don't think > waiting more time will be helpful. Hi, I am still alive. I had always hoped to find the time to resume work on the packages, however it turned out that circumstances do not allow me any leisure anymore for serious participation (at least for now). So I would be glad if people take over packages, especially those that require some work. I will try to follow the mailing-list for the next days. Regards and sorry for the trouble, Gérard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Plan for tomorrow's FESCo meeting (2010-07-06 at 19:30UTC)
Following is the list of topics that will be discussed in the FESCo meeting tomorrow at 19:30UTC (3:30pm EDT) in #fedora-meeting on irc.freenode.net. = Followups = #topic #351 Create a policy for updates - status report on implementation https://fedorahosted.org/fesco/ticket/351 #topic #382 Implementing Stable Release Vision https://fedorahosted.org/fesco/ticket/382 #topic #387 compile list of supported CPUs and reacto to recent loss of support for Geode LX on F13 https://fedorahosted.org/fesco/ticket/387 = New business = #topic #412 Non-responsive maintainer (ixs); request fast-track orphaning of libsndfile #topic #409 Feature Request: GNUstep #topic #411 Cheese non responsive #topic #413 F14Feature: http://fedoraproject.org/wiki/Features/Go_Programming #topic #414 F14Feature: http://fedoraproject.org/wiki/Features/D_Programming = Fedora Engineering Services tickets = https://fedorahosted.org/fedora-engineering-services/report/6 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Can anyone contact Gérard Milmeister (gemi)?
2010/6/18 Chen Lei : > Hi all, > > Following the process > > https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers > > Is someone able to get in touch with Gérard Milmeister.(gemi) > > I can't find any activity of him from koji and bugzilla in the past > eight months, I also got no response from him after sending a private > mail a month ago. > > See https://bugzilla.redhat.com/show_bug.cgi?id=530565 for more details. > > > Regards, > Chen Lei > Hi FESCo, Can we orphan his packages now? I'd like to take scons, I don't think waiting more time will be helpful. Regards, Chen Lei -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning perl-TermReadKey
Once upon a time, Stepan Kasal said: > I have orphaned perl-TermReadKey, for Fedora 11-devel, EPEL 4,5. > > Anyone interested, please take it. I use this on both Fedora and RHEL, so I'll take it. It looks like psabata has taken it in current Fedora, so I guess I'll just grab it for EPEL. -- Chris Adams Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
heads up libchamplain 0.6 headed to rawhide
Subject says it all. Cheers, Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer fast track procedure for libsndfile
This seems to be happening a lot lately regarding maintainers and/or co-maintainers losing interest in their projects somewhere along the line and just stopping development without any warning and notification to other members who may be interested. I am wondering, is the process efficient enough for other willing developers to take over development of unplanned orphaned and unmaintained code from unresponsive developers/maintainers and co-maintainers? Regards -- Chris Jones Photographic Imaging Professional and Graphic Designer ABN: 98 317 740 240 Photo Resolutions - Photo Printing, Editing and Restorations Web: http://photoresolutions.freehostia.com Email: or Fedora Design Suite Developer and Co-Maintainer Email: -- GnuPG v1.4.10 (GNU/Linux) Public Key Fingerprint: 6915 0761 5754 D091 99F4 5384 BA37 FD5D 34F9 F115 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer fast track procedure for libsndfile
On Mon, Jul 5, 2010 at 6:17 PM, Michel Alexandre Salim wrote: > Hi all, > > I'm initiating a fast track procedure for libsndfile -- a security bug > has been reported for over a year, and there has been no response from > maintainer We made many attempts to reach him last year. See: https://www.redhat.com/archives/fedora-devel-list/2009-November/msg00102.html I asked for comaintainership on Fedora branches about 10 months ago, and didn't hear back until now. My request is still open. I ended up updating the Fedora packages, and hence closing the security bugs with my proven powers. I didn't touch the EPEL package since 1- I don't even know if the force is strong enough with my proven powers in the EPEL arena. 2- I am basically not much interested in EPEL. Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Non-responsive maintainer fast track procedure for libsndfile
Hi all, I'm initiating a fast track procedure for libsndfile -- a security bug has been reported for over a year, and there has been no response from maintainer: https://bugzilla.redhat.com/show_bug.cgi?id=488364 Here is the fesco ticket: https://fedorahosted.org/fesco/ticket/412 Regards, -- Michel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 607982] Uninitialized warnings on $magnitude
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=607982 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Number-Compare-0.01-15 |perl-Number-Compare-0.01-15 |.fc13 |.fc12 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 607982] Uninitialized warnings on $magnitude
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=607982 --- Comment #7 from Fedora Update System 2010-07-05 18:05:13 EDT --- perl-Number-Compare-0.01-15.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 607982] Uninitialized warnings on $magnitude
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=607982 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-Number-Compare-0.01-15 ||.fc13 Resolution||ERRATA -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 607982] Uninitialized warnings on $magnitude
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=607982 --- Comment #6 from Fedora Update System 2010-07-05 18:04:13 EDT --- perl-Number-Compare-0.01-15.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: concept of package "ownership"
On Mon, 2010-07-05 at 13:30 -0700, Adam Williamson wrote: > In practice, packages still have maintainers who are recognized for > practical reasons and generally you would check with the listed > maintainer of a package before making a change to it. (But, hey, if they > don't reply in a day or two, it's fair game!) > > This generally works out pretty well, and helps out with the problem of > having quite a small set of maintainers for an extremely large set of > packages. I was often in the situation where I happened to notice a > small issue with 'someone else's' package and could just go ahead and > fix it, instead of having to go through the bureaucracy of filing a bug > report and waiting for them to do it. I should add that obviously it works best if you exercise common sense about what to change. I'd never go into someone else's package and change their whitespace preferences or variable naming scheme or whatever to match my own preferences just so I'd have an easier time looking at their .spec file. Obviously it works best if you follow a minimal approach of changing just what's necessary to address the practical issue you're fixing. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: webkitgtk abi bump
libproxy is done too 2010/7/5 Simon Wesp : > Am Freitag, den 02.07.2010, 10:36 -0400 schrieb Matthias Clasen: >> surf > done, thank you for this info! > > -- > Mit freundlichen Grüßen aus dem schönen Hainzell > Simon Wesp > > http://www.fedoraproject.org/wiki/SimonWesp > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: concept of package "ownership"
On Fri, 2010-07-02 at 03:18 +0200, Kevin Kofler wrote: > I think we need to get rid of the concept of ownership entirely, that'd also > make orphaned or de-facto orphaned packages less of a problem. You see a > problem, you fix it. Who cares whether the package has an active maintainer > or not? I think there's a reasonable middle ground here. Mandriva has a very open ACL policy. Anyone with commit access to a repository has commit access to every package in that repository, so any MDV maintainer can change any package in contrib, and anyone who maintains a package in main - which, practically speaking, is a lot of people including many non-staff - can change any package in main. There's a very small list of restricted packages to which this doesn't apply; I think that's pretty much just kernel and glibc or something very minimal like that. In practice, packages still have maintainers who are recognized for practical reasons and generally you would check with the listed maintainer of a package before making a change to it. (But, hey, if they don't reply in a day or two, it's fair game!) This generally works out pretty well, and helps out with the problem of having quite a small set of maintainers for an extremely large set of packages. I was often in the situation where I happened to notice a small issue with 'someone else's' package and could just go ahead and fix it, instead of having to go through the bureaucracy of filing a bug report and waiting for them to do it. It's rarely the case that someone makes a really stupid change and causes friction. I'd say the system works more often than it doesn't, and it'd probably be good for Fedora too to - as Dave proposes - explicitly _not_ have a concept of ownership, and be more liberal about non-maintainers touching packages. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: who is Petr Pisar from redhat ?
On Fri, 2010-07-02 at 18:18 +0200, Ralf Corsepius wrote: > What would do if "John Doe" would apply for proven packager and write > access to 1500 packages? > > Seriously, you'd likely tell him he's nuts. Suggesting what you think would 'likely' happen seems a weak argument. Can you cite an *actual* case of someone not-RH having a legitimate reason to be allowed modification access to a large set of packages, applying for such access, and being denied it? If not, your allegations seem rather unfounded. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: who is Petr Pisar from redhat ?
On Fri, 2010-07-02 at 21:58 +1000, Dave Airlie wrote: > On Fri, 2010-07-02 at 13:55 +0200, Léon Keijser wrote: > > On Fri, 2010-07-02 at 11:34 +0200, Michael Schwendt wrote: > > > On Fri, 02 Jul 2010 13:07:45 +0530, Rahul wrote: > > > > > > > IMO, there is absolutely nothing wrong with anyone > > > > with commit access updating packages in Rawhide > > > > > > Of course there is. There ought to be prior communication about such plans > > > to upgrade a package. The primary package maintainer may have good reasons > > > for not upgrading the package. Just ask! > > > > I think you are spot-on with this comment. There probably wouldn't be > > such a discussion if the (proven)packager simply stated his intentions > > to the package maintainer. > > > > That doesn't really scale, on a single package basis yeah maybe, if I > have to bump 10 or 15 packages after a mass rebuild it get ugly quick. > > You get mails from CVS, its all in version control, if you disagree with > what they did, back it out, state in the spec what they did wrong. Or you can act pre-emptively. Mandriva's opensync packages have (still had, actually) a paragraph-long comment at the start explicitly explaining why no-one should 'helpfully' bump them to the 'newer' version available upstream, as this newer version in fact is completely useless. I added this after a similar situation happened (someone else 'helpfully' bumped the packages, which I was intentionally leaving at the older version). We can argue over who should have the burden to notify whom and so forth, but practically speaking, whether you think you 'ought' to or not, if you don't want other people touching 'your' packages, there's ways you can help this happen. This is better than trying to fix the change retrospectively; it's quite hard to revert a package after someone bumps it, and tends to involve the use of an Epoch (urgh). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: webkitgtk abi bump
Am Freitag, den 02.07.2010, 10:36 -0400 schrieb Matthias Clasen: > surf done, thank you for this info! -- Mit freundlichen Grüßen aus dem schönen Hainzell Simon Wesp http://www.fedoraproject.org/wiki/SimonWesp signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Request to take gnustep-make
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, because I saw, that the current maintainer of gnustep-make hast orphaned this package, I would like to take over this package. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkwyNkUACgkQZLAIBz9lVu9D+QQA3ynS2j+rOVnotRZ2PWkrn/fc 5O4gySTuD4pAMMmwF7yYHnXUT5Clw9EDNV6o1mJXE9LOFcoI3Afqbiu3rfd6CRUr LK8pP3UvqhSnTPnozE34k9UvNMG8QC7HTXn7/Ob7RYZYZiNBL6c0WjyPRrFV54ei KYcbdvTsHfUmgTi8vj0= =f+gD -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Orphaning engine_pkcs11, Passing libp11 to Kalev Lember
I have not been keeping up with my package ownership responsibilities and Kalev Lember contacted me about libp11. He has graciously offered to step up and take over maintainership of libp11, but engine_pkcs11 is still looking for a maintainer if anyone is interested. Thanks to Kalev, and the rest of the Fedora Community. -Matt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rpms/perl-Class-Accessor/EL-6 perl-Class-Accessor.spec, 1.16, 1.17 sources, 1.8, 1.9
Author: spot
Update of /cvs/pkgs/rpms/perl-Class-Accessor/EL-6
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv10355
Modified Files:
perl-Class-Accessor.spec sources
Log Message:
sync with RHEL
Index: perl-Class-Accessor.spec
===
RCS file: /cvs/pkgs/rpms/perl-Class-Accessor/EL-6/perl-Class-Accessor.spec,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -p -r1.16 -r1.17
--- perl-Class-Accessor.spec30 Apr 2010 07:13:42 - 1.16
+++ perl-Class-Accessor.spec5 Jul 2010 16:44:03 - 1.17
@@ -1,6 +1,6 @@
Name: perl-Class-Accessor
-Version:0.34
-Release:3%{?dist}
+Version:0.31
+Release:6%{?dist}
Summary:Automated accessor generation
Group: Development/Libraries
License:GPL+ or Artistic
@@ -43,15 +43,6 @@ rm -rf $RPM_BUILD_ROOT
%changelog
-* Fri Apr 30 2010 Marcela Maslanova - 0.34-3
-- Mass rebuild with perl-5.12.0
-
-* Mon Dec 7 2009 Stepan Kasal - 0.34-2
-- rebuild against perl 5.10.1
-
-* Mon Oct 5 2009 Stepan Kasal - 0.34-1
-- new upstream version
-
* Sat Jul 25 2009 Fedora Release Engineering
- 0.31-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-Class-Accessor/EL-6/sources,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -p -r1.8 -r1.9
--- sources 5 Oct 2009 16:29:24 - 1.8
+++ sources 5 Jul 2010 16:44:03 - 1.9
@@ -1 +1 @@
-0d9640d237a13276145f7e44b4855b89 Class-Accessor-0.34.tar.gz
+d13df2381878ccdb847c23ab6af7e4fa Class-Accessor-0.31.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
rpms/perl-Class-Accessor/EL-5 perl-Class-Accessor.spec, 1.8, 1.9 sources, 1.7, 1.8
Author: spot
Update of /cvs/pkgs/rpms/perl-Class-Accessor/EL-5
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv7710
Modified Files:
perl-Class-Accessor.spec sources
Log Message:
0.34
Index: perl-Class-Accessor.spec
===
RCS file: /cvs/pkgs/rpms/perl-Class-Accessor/EL-5/perl-Class-Accessor.spec,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -p -r1.8 -r1.9
--- perl-Class-Accessor.spec24 Aug 2007 19:22:20 - 1.8
+++ perl-Class-Accessor.spec5 Jul 2010 16:26:49 - 1.9
@@ -1,6 +1,6 @@
Name: perl-Class-Accessor
-Version:0.31
-Release:1%{?dist}
+Version:0.34
+Release:3%{?dist}
Summary:Automated accessor generation
Group: Development/Libraries
License:GPL+ or Artistic
@@ -9,7 +9,7 @@ Source0:http://search.cpan.org/C
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
-BuildRequires: perl >= 1:5.6.1
+BuildRequires: perl >= 1:5.6.1, perl(Test::More)
Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo $version))
%description
@@ -43,6 +43,30 @@ rm -rf $RPM_BUILD_ROOT
%changelog
+* Fri Apr 30 2010 Marcela Maslanova - 0.34-3
+- Mass rebuild with perl-5.12.0
+
+* Mon Dec 7 2009 Stepan Kasal - 0.34-2
+- rebuild against perl 5.10.1
+
+* Mon Oct 5 2009 Stepan Kasal - 0.34-1
+- new upstream version
+
+* Sat Jul 25 2009 Fedora Release Engineering
- 0.31-6
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild
+
+* Thu Feb 26 2009 Fedora Release Engineering
- 0.31-5
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild
+
+* Wed Feb 27 2008 Tom "spot" Callaway - 0.31-4
+- Rebuild for perl 5.10 (again)
+
+* Tue Jan 15 2008 Tom "spot" Callaway 0.31-3
+- rebuild for new perl
+
+* Fri Aug 24 2007 Tom "spot" Callaway 0.31-2
+- license fix
+
* Fri Jul 27 2007 Tom "spot" Callaway 0.31-1
- update for 0.31, hooray for performance patches
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-Class-Accessor/EL-5/sources,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -p -r1.7 -r1.8
--- sources 27 Jul 2007 20:23:52 - 1.7
+++ sources 5 Jul 2010 16:26:49 - 1.8
@@ -1 +1 @@
-d13df2381878ccdb847c23ab6af7e4fa Class-Accessor-0.31.tar.gz
+0d9640d237a13276145f7e44b4855b89 Class-Accessor-0.34.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: CVS connection time-outs
On Mon, Jul 05, 2010 at 06:06:53PM +0200, Patrick MONNERAT wrote: > On Mon, 2010-07-05 at 18:00 +0300, Manuel Wolfshant wrote: > > > I faced similar problems while doing performing several updates to a > > couple of packages, starting Friday evening and during the night to > > Saturday (EET) > > Thanks for the info. I have to say that under the current conditions, > the common/cvs-import.sh script is unusable. The Fedora Infrastructure issue tracker can be accessed here to report a problem: https://fedorahosted.org/fedora-infrastructure Regards Till pgpwjaDPhTo7d.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: CVS connection time-outs
On Mon, 2010-07-05 at 18:00 +0300, Manuel Wolfshant wrote: > I faced similar problems while doing performing several updates to a > couple of packages, starting Friday evening and during the night to > Saturday (EET) Thanks for the info. I have to say that under the current conditions, the common/cvs-import.sh script is unusable. I'm in CET and I wonder where the problem comes along the internet path. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: CVS connection time-outs
On Mon, Jul 5, 2010 at 10:54 AM, Patrick MONNERAT wrote: > > I'm currently trying to perform the initial CVS import of a package that has > quite a bunch of patches with ./common/cvs-import.sh. > > All my attempts (for more than one hour!) were unsuccessful because at least > one of the connection to cvs.fedoraproject.org from the script results in a > connection time-out error. > > ssh: connect to host cvs.fedoraproject.org port 22: Connection timed out > cvs [add aborted]: end of file from server (consult above messages if any) > > Web connections to koji (with FF) seem also affected. > > Is the server heavily loaded now ? Does anyone has the same problem ? Or do > I have to investigate on my side (other connections around here are not > fast, but satisfactory) ? > This happens to me rather frequently when I do a "make new-sources". I recommend committing all the files one by one. Large uploads have a bigger tendency to time out and fail. Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: About Zope SIG mailing list and progress report
On Sun, Jul 04, 2010 at 07:13:00PM +0800, Robin 'cheese' Lee wrote: > Sorry for my late joining. > > A Zope specific mailing list may not be in urgent need by now. We can > just use this mailing list, which is for Python packaging in general. > The traffic of this mailing list is low and some of our decisions for > Zope packagine may affect wider Python packaging practices. > Sounds good to me (one of the current python packagers that reads this list :-). > > And I am still considering a Fedora enhancement for > distribute(setuptools) and distutils. > If you have some concrete ideas here, let me know (and upstream for distribute if applicable). -Toshio pgpPjXlVeVRX6.pgp Description: PGP signature ___ python-devel mailing list python-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/python-devel
Re: CVS connection time-outs
On 07/05/2010 05:54 PM, Patrick MONNERAT wrote: I'm currently trying to perform the initial CVS import of a package that has quite a bunch of patches with ./common/cvs-import.sh. All my attempts (for more than one hour!) were unsuccessful because at least one of the connection to cvs.fedoraproject.org from the script results in a connection time-out error. ssh: connect to host cvs.fedoraproject.org port 22: Connection timed out cvs [add aborted]: end of file from server (consult above messages if any) Web connections to koji (with FF) seem also affected. Is the server heavily loaded now ? Does anyone has the same problem ? I faced similar problems while doing performing several updates to a couple of packages, starting Friday evening and during the night to Saturday (EET) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
CVS connection time-outs
I'm currently trying to perform the initial CVS import of a package that has quite a bunch of patches with ./common/cvs-import.sh. All my attempts (for more than one hour!) were unsuccessful because at least one of the connection to cvs.fedoraproject.org from the script results in a connection time-out error. ssh: connect to host cvs.fedoraproject.org port 22: Connection timed out cvs [add aborted]: end of file from server (consult above messages if any) Web connections to koji (with FF) seem also affected. Is the server heavily loaded now ? Does anyone has the same problem ? Or do I have to investigate on my side (other connections around here are not fast, but satisfactory) ? Thanks in advance for info Regards, Patrick -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: concept of package "ownership"
On Sat, 2010-07-03 at 03:34 +0200, Kevin Kofler wrote: > Ralf Corsepius wrote: > > We need groups, with "grouped privileges/acls" etc. It's essentially > > what e.g. the "perl-sig" originally was meant to be. > > Yes, group ACLs are definitely needed, but in addition to that technical > feature, we also need to make sure that the SIG actually gets commit access > to ALL packages related to the SIG. ALL perl-* packages should be > committable to by the Perl SIG. That's what a SIG is for. And it'd have > prevented this whole "why were X and Y added as maintainers to my perl-* > packages" fiasco, it would just have been the SIG's decision to add the > people to the SIG and this should automatically give commit access to all > perl-* packages. > > Similarly, all packages using Qt should be committable to by the KDE SIG > etc. AIUI, a SIG are more people than those who actually work on related packages as maintainers, or are competent and responsible enough to not break things in the process of updating packages with which they're not familiar (otherwise they'd be (co-)maintainers, wouldn't they?). If we ever get group ACLs, I think we should have $SIG-packager groups, consisting of SIG members who fulfill the above, who get that kind of access. Nils -- Nils Philippsen "Those who would give up Essential Liberty to purchase Red Hat a little Temporary Safety, deserve neither Liberty n...@redhat.com nor Safety." -- Benjamin Franklin, 1759 PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20100705 changes
Compose started at Mon Jul 5 08:15:11 UTC 2010 Broken deps for i386 -- BackupPC-3.1.0-14.fc14.noarch requires perl-suidperl 1:anerley-0.2.14-1.fc14.i686 requires libmx-1.0.so.0 1:anjuta-2.30.0.0-2.fc14.i686 requires libgladeui-1.so.9 1:anjuta-2.30.0.0-2.fc14.i686 requires libwebkit-1.0.so.2 awn-extras-applets-0.4.0-17.fc14.i686 requires libwebkit-1.0.so.2 dates-0.4.11-3.fc14.i686 requires libedataserver-1.2.so.11 deskbar-applet-2.30.0-1.1.fc14.i686 requires libedataserver-1.2.so.12 eclipse-checkstyle-4.0.1-14.fc12.noarch requires checkstyle-optional = 0:4.1 eclipse-checkstyle-4.0.1-14.fc12.noarch requires checkstyle = 0:4.1 empathy-2.31.3-2.fc14.i686 requires libwebkit-1.0.so.2 epiphany-2.31.3-1.fc14.i686 requires libwebkit-1.0.so.2 evolution-rss-0.1.9-7.20100525git.fc14.i686 requires libwebkit-1.0.so.2 2:gimp-help-browser-2.6.9-4.fc14.i686 requires libwebkit-1.0.so.2 gmpc-0.19.1-3.fc14.i686 requires libwebkit-1.0.so.2 gnome-bluetooth-moblin-2.90.0-1.fc14.i686 requires libmx-1.0.so.0 gnome-chemistry-utils-gnumeric-0.12.1-1.fc14.i686 requires libspreadsheet-1.10.0.so gnome-phone-manager-0.65-6.fc14.i686 requires libgnome-bluetooth.so.7 gnucash-2.3.13-1.fc14.i686 requires libwebkit-1.0.so.2 kst-fits-1.8.0-7.fc14.i686 requires cfitsio = 0:3.240 lekhonee-gnome-0.11-2.fc14.i686 requires libwebkit-1.0.so.2 libpeas-0.5.1-1.fc14.i686 requires libgdk_pixbuf-3.0.so.0 libpeas-devel-0.5.1-1.fc14.i686 requires libgdk_pixbuf-3.0.so.0 libproxy-webkit-0.4.0-1.fc14.i686 requires libwebkit-1.0.so.2 1:liferea-1.6.3-1.fc14.i686 requires libwebkit-1.0.so.2 maven2-plugin-checkstyle-2.0.8-3.fc12.noarch requires checkstyle-optional >= 0:4.1 merkaartor-0.16.1-1.fc13.i686 requires libexiv2.so.6 midori-0.2.6-1.fc14.i686 requires libwebkit-1.0.so.2 mingw32-OpenSceneGraph-2.8.2-4.fc14.noarch requires mingw32(libpng-3.dll) moblin-panel-applications-0.1.28-1.fc14.i686 requires libmx-1.0.so.0 moblin-panel-pasteboard-0.0.6-1.fc14.i686 requires libmx-1.0.so.0 moblin-panel-people-0.1.13-1.fc14.i686 requires libmx-1.0.so.0 moblin-panel-status-0.1.21-2.fc14.i686 requires libmx-1.0.so.0 mutter-moblin-0.75.16-2.fc14.i686 requires libmx-1.0.so.0 perl-DBI-Dumper-2.01-8.fc12.i686 requires perl(:MODULE_COMPAT_5.10.0) perl-Data-Alias-1.07-6.fc13.i686 requires perl(:MODULE_COMPAT_5.10.1) perl-Pugs-Compiler-Rule-0.37-4.fc13.noarch requires perl(:MODULE_COMPAT_5.10.1) perl-Test-AutoBuild-1.2.2-9.fc12.i686 requires perl(:MODULE_COMPAT_5.10.0) plexus-containers-component-annotations-javadoc-1.0-0.1.a34.7.fc12.noarch requires jakarta-commons-logging-javadoc poker3d-1.1.36-17.fc12.i686 requires libosgUtil.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgVolume.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgManipulator.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgAnimation.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgFX.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgGA.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgText.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgViewer.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgSim.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgParticle.so.55 poker3d-1.1.36-17.fc12.i686 requires libosg.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgDB.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgShadow.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgTerrain.so.55 poker3d-1.1.36-17.fc12.i686 requires libosgWidget.so.55 python3-beaker-1.5.3-4.fc14.noarch requires python3-paste pywebkitgtk-1.1.6-3.fc14.i686 requires libwebkit-1.0.so.2 qtgpsc-0.2.3-6.fc12.i686 requires libgps.so.18 seed-2.31.1-1.fc14.i686 requires libwebkit-1.0.so.2 shotwell-0.5.2-1.fc14.i686 requires libwebkit-1.0.so.2 skyviewer-1.0.0-4.fc14.i686 requires libQGLViewer.so.2.3.5 spacewalk-certs-tools-1.1.1-1.fc14.noarch requires spacewalk-backend-libs >= 0:0.8.28 surf-0.4.1-1.fc14.i686 requires libwebkit-1.0.so.2 themonospot-gui-qt-0.1.3-6.fc14.i686 requires mono(qt-dotnet) = 0:4.5.0.0 themonospot-gui-qt-0.1.3-6.fc14.i686 requires libqyotoshared.so.1 vfrnav-0.4-1.fc13.i686 requires libgps.so.18 vifir-0.4-2.fc14.i686 requires libpoppler-glib.so.4 vifir-0.4-2.fc14.i686 requires libgps.so.18 viking-0.9.91-3.fc13.i686 requires libgps.so.18 xcf-pixbuf-loader-0.0.1-3.8af913d1.fc14.i686 requires /usr/lib/gtk-2.0/2.10.0/loaders xenner-0.48-1.fc14.i386 requires libxenguest.so.3.4 Broken deps for x86_64 ---
Broken dependencies: perl-Pugs-Compiler-Rule
perl-Pugs-Compiler-Rule has broken dependencies in the rawhide tree: On x86_64: perl-Pugs-Compiler-Rule-0.37-4.fc13.noarch requires perl(:MODULE_COMPAT_5.10.1) On i386: perl-Pugs-Compiler-Rule-0.37-4.fc13.noarch requires perl(:MODULE_COMPAT_5.10.1) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Data-Alias
perl-Data-Alias has broken dependencies in the rawhide tree: On x86_64: perl-Data-Alias-1.07-6.fc13.x86_64 requires perl(:MODULE_COMPAT_5.10.1) On i386: perl-Data-Alias-1.07-6.fc13.i686 requires perl(:MODULE_COMPAT_5.10.1) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-DBI-Dumper
perl-DBI-Dumper has broken dependencies in the rawhide tree: On x86_64: perl-DBI-Dumper-2.01-8.fc12.x86_64 requires perl(:MODULE_COMPAT_5.10.0) On i386: perl-DBI-Dumper-2.01-8.fc12.i686 requires perl(:MODULE_COMPAT_5.10.0) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: webkitgtk abi bump
On Fri, 2010-07-02 at 10:36 -0400, Matthias Clasen wrote: > gimp-help-browser rebuilt gimp -- Nils Philippsen "Those who would give up Essential Liberty to purchase Red Hat a little Temporary Safety, deserve neither Liberty n...@redhat.com nor Safety." -- Benjamin Franklin, 1759 PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: cheese ?
On Mon, Jul 05, 2010 at 12:30:19PM +0100, Mark Chappell wrote: > http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers > > It takes three weeks which can be frustrating, the initial "can we > push this update to testing" might count as the initial ticket > creation, dropping it down to 2 weeks from here... You can use the "fast track procedure" here, imho, because "the maintainer has been non responsive for a long time, but the above procedure has never been completed": http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers#Fast_Track_procedure Afaics there have been several tries to contact him already: https://bugzilla.redhat.com/show_bug.cgi?id=585817#c4 But it would be better to collect all these contact attempts in the FESCo ticket. Regards Till pgpc52HaUyM3g.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: cheese ?
On 5 July 2010 12:33, Pierre-Yves wrote: > If we include the absence of reaction in this review: > https://bugzilla.redhat.com/show_bug.cgi?id=585817 > (last comment on Mai 08th) then we are over these 3 weeks. Yeah, just depends if pinging on those tickets is sufficient. In which case "After another 7 days (now 3 weeks total), the reporter posts a formal request to the fedora-devel list with the bug link, indicating all reasonable efforts have been made to contact the maintainer have failed and that they wish to take over the package." Someone from FESCo will hopefully respond to this email thread... Mark -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: cheese ?
On Mon, Jul 05, 2010 at 12:30:19PM +0100, Mark Chappell wrote: > http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers > > It takes three weeks which can be frustrating, the initial "can we > push this update to testing" might count as the initial ticket > creation, dropping it down to 2 weeks from here... No, it might not, at least that's not my reading of the policy. If you want to have the policy changed, you should submit to FESCo a revision of the policy (rewritten in good english, something like: the days count starts from the first time the maintainer didn't answer requests, and not the time of filling the comment starting the non-responsive maintainer procedure. -- Pat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: cheese ?
On Mon, 2010-07-05 at 12:30 +0100, Mark Chappell wrote: > http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers > > It takes three weeks which can be frustrating, the initial "can we > push this update to testing" might count as the initial ticket > creation, dropping it down to 2 weeks from here... If we include the absence of reaction in this review: https://bugzilla.redhat.com/show_bug.cgi?id=585817 (last comment on Mai 08th) then we are over these 3 weeks. Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: cheese ?
http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers It takes three weeks which can be frustrating, the initial "can we push this update to testing" might count as the initial ticket creation, dropping it down to 2 weeks from here... Mark -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Package Review Stats for last week ending 4th July
Top two FAS account holders who have completed reviewing "Package review" components on bugzilla for last week ending 4th July were Mark Chappell and Emmanuel Seyman. Mark Chappell : 5 https://bugzilla.redhat.com/show_bug.cgi?id=607875 perl-Net-IMAP-Simple-SSL https://bugzilla.redhat.com/show_bug.cgi?id=607876 perl-Net-IMAP-Simple https://bugzilla.redhat.com/show_bug.cgi?id=607877 perl-XML-FeedPP https://bugzilla.redhat.com/show_bug.cgi?id=602598 perl-Proc-WaitStat https://bugzilla.redhat.com/show_bug.cgi?id=607878 perl-XML-TreePP Emmanuel Seyman : 4 https://bugzilla.redhat.com/show_bug.cgi?id=604659 perl-Test-EOL https://bugzilla.redhat.com/show_bug.cgi?id=581324 perl-IO-Handle-Util https://bugzilla.redhat.com/show_bug.cgi?id=607355 perl-Directory-Queue https://bugzilla.redhat.com/show_bug.cgi?id=608405 perl-Config-GitLike Magnus Tuominen : 3 https://bugzilla.redhat.com/show_bug.cgi?id=592388 vor https://bugzilla.redhat.com/show_bug.cgi?id=593804 plasma-runner-events https://bugzilla.redhat.com/show_bug.cgi?id=604695 generatorrunner Parag AN(पराग) : 3 https://bugzilla.redhat.com/show_bug.cgi?id=609348 perl-Catalyst-Controller-ActionRole https://bugzilla.redhat.com/show_bug.cgi?id=609352 perl-Catalyst-Plugin-Unicode-Encoding https://bugzilla.redhat.com/show_bug.cgi?id=609350 perl-Catalyst-View-Component-SubInclude Pravin Satpute : 3 https://bugzilla.redhat.com/show_bug.cgi?id=603632 typemade-josefinsansstd-light-fonts https://bugzilla.redhat.com/show_bug.cgi?id=603629 cf-sorts-mill-goudy-fonts https://bugzilla.redhat.com/show_bug.cgi?id=603633 scholarsfonts-cardo-fonts Mamoru Tasaka : 2 https://bugzilla.redhat.com/show_bug.cgi?id=605610 rubygem-chronic https://bugzilla.redhat.com/show_bug.cgi?id=606714 eekboard Stanislav Ochotnicky : 2 https://bugzilla.redhat.com/show_bug.cgi?id=527306 jericho-html https://bugzilla.redhat.com/show_bug.cgi?id=607385 felix-osgi-foundation Adel Gadllah : 1 https://bugzilla.redhat.com/show_bug.cgi?id=610211 unique3 David Tardon : 1 https://bugzilla.redhat.com/show_bug.cgi?id=539471 libserializer Jussi Lehtola : 1 https://bugzilla.redhat.com/show_bug.cgi?id=608206 zn_poly Kalev Lember : 1 https://bugzilla.redhat.com/show_bug.cgi?id=595638 qwit Adam Miller : 1 https://bugzilla.redhat.com/show_bug.cgi?id=609728 sparsehash Jens Petersen : 1 https://bugzilla.redhat.com/show_bug.cgi?id=546376 ghc-chalmers-lava2000 Ankur Sinha : 1 https://bugzilla.redhat.com/show_bug.cgi?id=609320 grimmer-proggy-tinysz-fonts Stephen Gallagher : 1 https://bugzilla.redhat.com/show_bug.cgi?id=609165 perl-GPS-OID Chen Lei : 1 https://bugzilla.redhat.com/show_bug.cgi?id=608141 atkmm Total reviews modified: 31 Merge Reviews: 0 Review Requests: 31 This report by generated by bzReviewReport.py. The source is available at: https://fedorahosted.org/triage/browser/scripts/bzReviewReport.py Please submit patches or bug reports at: https://fedorahosted.org/triage/ -- Rakesh Pandit https://fedoraproject.org/wiki/User:Rakesh freedom, friends, features, first -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Fedora-r-devel-list] Review Request: R-GenomicRanges
On Thu, 2010-07-01 at 11:16 +0200, Pierre-Yves wrote: > Hi, > > If someone could have a look at this review I would be pleased. I need > it to update R-BSgenome which is needed for R-hgu95av2probe. > > https://bugzilla.redhat.com/show_bug.cgi?id=609079 > No taker ? Pierre ___ r-devel mailing list r-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/r-devel
Re: Non responsive maintainer: cheese ?
On Mon, 2010-06-28 at 09:22 +0200, Pierre-Yves wrote: > Dear all, > > Does someone know how to contact Cheese ? > https://admin.fedoraproject.org/pkgdb/users/packages/cheese > > I have tried to join him by the bugzilla: > https://bugzilla.redhat.com/show_bug.cgi?id=585817 > > > He has two packages in updates-testing: > https://bugzilla.redhat.com/show_bug.cgi?id=584966 > https://admin.fedoraproject.org/updates/search/R-bitops > > https://bugzilla.redhat.com/show_bug.cgi?id=584974 > https://admin.fedoraproject.org/updates/search/R-combinat > > I am willing to take over these two packages. I am still interested by these packages and nobody has reacted for a week on how to contact Cheese. What would be the next step ? A ticket of the Trac of Fesco ? Thanks, Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rfc: give koji diff capabilities
Thomas Spura wrote: > I don't see a benefit of that... When a build fails, it kills all > other current builds of other architectures, so you need to check that > architecture, that fails first and the diff would not contain the error. Even just comparing successful builds can be useful, e.g. to make sure that a new version isn't introducing new BRs. That said, in addition to the noise already mentioned by the OP, the smp_mflags make such diffs less than helpful, there will be moved lines all over the make phase. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
