Re: [ACTION REQUIRED] Retiring long-term FTBFS packages for Fedora 20
Hi TIll, The maintainer of package python-pylons is a zombie. I just realized that I'm on CC list but not co. I'd like to take it. Thanks. -- 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: Self Introduction
On Tue, 2013-08-20 at 11:42 +0800, Christopher Meng wrote: > Where is your package? I do not have one. I am hoping to assist in packaging if required. thank you. > signature.asc Description: This is a digitally signed message part -- 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: Self Introduction
Where is your package? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Self Introduction
Hi guys, Following the set of guidelines provided at: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Install_the_client_tools_.28Koji.29_and_set_up_your_certificate I would like to introduce myself. My names are Onuonga Frankie. my page on the fedora system is :https://fedoraproject.org/wiki/User:Onuonga I am in my final year at the university. I am taking a bachelors in computer science and mathematics. My major is advanced computer architecture which involves: signal processing, systems programming, parallel programming, simulation and modeling. I am joining the list to assist in packaging. I do not have any specific one yet but would like to get my hands dirty with what I am given. my Key fingerprint is :DAA5 8A30 CDF7 E90A 52C2 AF87 3D95 6592 7DB5 43E6 thank you. -- Frankie Onuonga -- 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: Mass Rebuild botched up my EVR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 19 Aug 2013 19:29:08 -0400 (EDT)
Paul Wouters wrote:
>
> Hi,
>
> I just noticed the mass rebuild on Aug 3 botched up my EVR for
> libreswan:
>
> Release: %{?prever:0.}1%{?prever:.%{prever}}%{?dist}.1
>
> It should have been:
>
> Release: %{?prever:0.}2%{?prever:.%{prever}}%{?dist}
>
> The previous version was:
>
> Release: %{?prever:0.}1%{?prever:.%{prever}}%{?dist}
>
> How can we prevent this from happening again?
rpmdev-bumpspec is the tool that is used to bump the spec files for
mass rebuild. your use of macros in the release is a bit odd and likely
confused it. I suggest you keep it simple.
Dennis
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlISzd8ACgkQkSxm47BaWfc0XgCfVP87MzwPqh12GkFwlKHQMSmD
dmEAn0z6S1hHCcfyBnucSP0JOGD1+n/F
=OWp4
-END PGP 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: Mass Rebuild botched up my EVR
On Mon, 2013-08-19 at 19:29 -0400, Paul Wouters wrote:
> Hi,
>
> I just noticed the mass rebuild on Aug 3 botched up my EVR for
> libreswan:
>
> Release: %{?prever:0.}1%{?prever:.%{prever}}%{?dist}.1
>
> It should have been:
>
> Release: %{?prever:0.}2%{?prever:.%{prever}}%{?dist}
>
> The previous version was:
>
> Release: %{?prever:0.}1%{?prever:.%{prever}}%{?dist}
>
> How can we prevent this from happening again?
>
> Paul
If this isn't expected behaviour, I'd suggest filing a bug against
rpmdevtools which contains the rpmdev-bumpspec tool. I think this is
used in the mass rebuilds script.
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:Ankursinha
Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG
signature.asc
Description: This is a digitally signed message part
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Retiring and blocking the following mate packages
Hi. These packages were obsoleted in MATE 1.6 along with the migration to gsettings. libmate libmateui libmatecanvas libmatecomponent libatecomponentui libmatenotify mate-conf (compiz no longer relies on mate-conf) mate-conf-editor mate-doc-utils (to be retired in F21 with MATE 1.8) mate-keyring (to be retired in F21 with MATE 1.8 and will use gnome-keyring) mate-mime-data mate-vfs Regarding mate-bluetooth we may take Kalev's advice and just create an applet or use the XFC E applet which is currently still premature. I have my own opinions on what should be done besides what I've already stated the main one. Just FYI Thanks, Dan -- 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: [ACTION REQUIRED] Retiring long-term FTBFS packages for Fedora 20
Don't retire my package, I have no time to fix them in this week, will check them at least from next Monday. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Mass Rebuild botched up my EVR
Hi,
I just noticed the mass rebuild on Aug 3 botched up my EVR for
libreswan:
Release: %{?prever:0.}1%{?prever:.%{prever}}%{?dist}.1
It should have been:
Release: %{?prever:0.}2%{?prever:.%{prever}}%{?dist}
The previous version was:
Release: %{?prever:0.}1%{?prever:.%{prever}}%{?dist}
How can we prevent this from happening again?
Paul
--
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: BlueZ Status in Fedora.
The whole reason why the bluez5 package was proposed as a separate one was so that we didn't have to cater for every desktop under the sun that's included in Fedora. bluez5 would conflict with bluez. If you had both MATE and GNOME installed, you wouldn't be able to upgrade to the latest version of GNOME as it would require bluez5 and the installed MATE bluez (4.x). That was the main idea, and would have avoided breaking all the desktops. At the end of the day, if somebody pushes bluez 5.x in the old bluez package, and it ends up breaking other things, I'm fine with it as well. Other desktops will need to follow up and make sure they get the porting in updates or admit that they don't have the manpower to keep up with that particular feature. - Original Message - > Am Tue, 13 Aug 2013 08:34:53 + > schrieb devel-requ...@lists.fedoraproject.org: > > > Message: 13 > > Date: Tue, 13 Aug 2013 01:03:20 +0200 > > From: Kalev Lember > > To: devel@lists.fedoraproject.org > > Subject: Re: BlueZ Status in Fedora. > > Message-ID: <520969b8.1030...@gmail.com> > > Content-Type: text/plain; charset=UTF-8 > > > > On 08/02/2013 10:15 AM, Jaroslav Reznik wrote: > > > Let me know - I'd like to have this one as a Change if it's going to F20 > > > > I have been coordinating with various people and looks like all teams > > are go. NetworkManager and PulseAudio changes are slightly lagging > > behind, but it's probably best if we move forward and try to integrate > > everything together in Rawhide before branching F20. > > > > I've cleaned up the feature page and marked it as ready for wrangler: > > > > https://fedoraproject.org/wiki/Changes/Bluez5 > > > > Sorry it's coming so late -- I didn't feel comfortable submitting it > > earlier knowing how much of the upstream development was still in flux. > > > mate-bluetooth doesn't support bluez5, and upstream doesn't have started to > port it. > I don't expect that is is ready before f20 alpha or beata. > So it would be very nice not to push bluez5 into f20. > Also Cristofph Wickert asked me to clean up runtime dependencies for > mate-bluetooth to avoid that xfce/lxde user don't have to be install to many > mate packages if they want to use mate-bluetooth. > It seems there is a plan that xfce/lxde also want to be use mate-bluetooth. > (maybe) > > So f21 is Ok as goal, but f20 is definitely to early for mate. > > Thank you > Wolfgang > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- 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: A closer look: Obsolete but still included packages
On Tue, 20 Aug 2013, Michael Schwendt wrote: For openswan, the openswan-doc subpackage is not obsoleted, just the base package is. # repoquery --whatobsoletes openswan libreswan-0:3.3-1.fc19.x86_64 That's strange, because openswan is a dead.package. :-/ I'll fix that. Paul -- 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: BlueZ Status in Fedora.
On Sun, Aug 18, 2013 at 09:48:46PM -0700, Richard Vickery wrote: > Instead of shipping it, is there a problem with giving it to those on > the developer list and letting us iron out the kinks? Sure, that's what already happens. If you want to help, this thread contains a multitude of pointers where to start. Lars -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[389-devel] Please review: Ticket #47486 compiler warnings in adminutil, admin, dsgw
https://fedorahosted.org/389/attachment/ticket/47486/0002-fix-compiler-warnings.patch https://fedorahosted.org/389/attachment/ticket/47486/0002-fix-compiler-warnings.2.patch https://fedorahosted.org/389/attachment/ticket/47486/0002-fix-compiler-warnings.3.patch -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
[389-devel] Please review: Ticket #47486 compiler warnings in adminutil, admin, dsgw
-- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: A closer look: Obsolete but still included packages
On Tue, Aug 20, 2013 at 12:17:50AM +0200, Michael Schwendt wrote: > # repoquery --whatobsoletes openswan > libreswan-0:3.3-1.fc19.x86_64 > > That's strange, because openswan is a dead.package. :-/ FYI: openswan is now blocked for Fedora 20. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
A closer look: Obsolete but still included packages
Comments at the bottom. First the src.rpms in Rawhide, which are completely obsolete because all built binary rpms are obsoleted. Those should get retired properly: All builds obsoleted: - chktex classads detex drupal6-drush ff-utils gpp4 ibus-table-array30 jadetex jaxen-bootstrap joystick kdirstat latexdiff mate-conf mate-conf-editor metapost-metauml nss-myhostname pdfbook pdfjam ps2eps python-cryptsetup python-lvm python-quantumclient rdate seahorse-plugins tetex-IEEEtran xmltex zeitgeist-datahub Only obsolete subpackage(s): lzma ['lzma'] 2 left openswan ['openswan'] 1 left ruby-gnome2 ['ruby-gtksourceview2', 'ruby-gtksourceview2-devel'] 24 left yum-utils ['yum-plugin-security'] 27 left In this second list, the obsolete binary rpm names are in brackets, and the number of remaining subpackage rpms is appended. # repoquery --whatobsoletes lzma xz-lzma-compat-0:5.1.2-4alpha.fc19.x86_64 The lzma-libs and lzma-devel subpackages are not obsoleted, just the base package is. Package "scotch" is the only one that depends on lzma-libs. For openswan, the openswan-doc subpackage is not obsoleted, just the base package is. # repoquery --whatobsoletes openswan libreswan-0:3.3-1.fc19.x86_64 That's strange, because openswan is a dead.package. :-/ -- 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: [ACTION REQUIRED] Retiring long-term FTBFS packages for Fedora 20
On Mon, Aug 19, 2013 at 10:51:34PM +0100, Peter Robinson wrote: > No they can't, the sync of blocked/new packages is synced over all > secondary arches. They could likely be untagged so they don't show up in > the list. Tagging is also synced, therefore it is more complicated. There is now a ticket for this: https://fedorahosted.org/rel-eng/ticket/5729 -- 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: [ACTION REQUIRED] Retiring long-term FTBFS packages for Fedora 20
On Mon, Aug 19, 2013 at 10:41 PM, Till Maas wrote: > On Mon, Aug 19, 2013 at 11:21:38PM +0200, Dan Horák wrote: > > On Mon, 19 Aug 2013 23:05:32 +0200 > > Till Maas wrote: > > > > > The following packages did not build for two releases and will be > > > retired around 2013-08-26 unless someone rebuilds them or announces to > > > actively working on fixing them. > > > > > > Note: If you received this mail directly you (co)maintain one of the > > > affected packages or a package that depends on one. > > > > > > Package(co)maintainers > > > > === > > > libvpdemunson, hegdevasant, fkocina, lnykryn, > > > rrakus, jskala > > > lsvpd emunson, hegdevasant, fkocina, lnykryn, > > > wolfy, rrakus, jskala > > > > these 2 are ppc/ppc64 specific and actively maintained, so they should > > be whitelisted, because they won't have new builds in primary koji > > There is no whitelist, but they could be blocked in primary koji I > guess. > No they can't, the sync of blocked/new packages is synced over all secondary arches. They could likely be untagged so they don't show up in the list. Peter -- 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: [ACTION REQUIRED] Retiring long-term FTBFS packages for Fedora 20
On Mon, Aug 19, 2013 at 11:21:38PM +0200, Dan Horák wrote: > On Mon, 19 Aug 2013 23:05:32 +0200 > Till Maas wrote: > > > The following packages did not build for two releases and will be > > retired around 2013-08-26 unless someone rebuilds them or announces to > > actively working on fixing them. > > > > Note: If you received this mail directly you (co)maintain one of the > > affected packages or a package that depends on one. > > > > Package(co)maintainers > > === > > libvpdemunson, hegdevasant, fkocina, lnykryn, > > rrakus, jskala > > lsvpd emunson, hegdevasant, fkocina, lnykryn, > > wolfy, rrakus, jskala > > these 2 are ppc/ppc64 specific and actively maintained, so they should > be whitelisted, because they won't have new builds in primary koji There is no whitelist, but they could be blocked in primary koji I guess. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[389-devel] Please review: Ticket #47403 DSGW authentication issue
https://fedorahosted.org/389/attachment/ticket/47403/0001-Ticket-47403-DSGW-authentication-issue.patch -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: [ACTION REQUIRED] Retiring packages for Fedora 20 v2
On Mon, Aug 19, 2013 at 9:16 PM, Till Maas wrote: > The following packages have been retired: > > alsa-oss > firmware-extract > firstboot > gkrellm-timestamp > guiloader > justmoon > lybniz > mars-sim > miau > openstack-tempo > osgal > python3-cherrypy > vblade > > Because alsa-oss was retired, mumble needs to be rebuild without OSS > support (just removing the BR failed in a scratch build because > libspeechd.h cannot be found, maybe this is an unrelated bug) > I've fixed the issue with building mumble and I'll be pushing the fix to rawhide shortly. Peter -- 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: [ACTION REQUIRED] Retiring long-term FTBFS packages for Fedora 20
On Mon, 19 Aug 2013 23:05:32 +0200 Till Maas wrote: > The following packages did not build for two releases and will be > retired around 2013-08-26 unless someone rebuilds them or announces to > actively working on fixing them. > > Note: If you received this mail directly you (co)maintain one of the > affected packages or a package that depends on one. > > Package(co)maintainers > === > libvpdemunson, hegdevasant, fkocina, lnykryn, > rrakus, jskala > lsvpd emunson, hegdevasant, fkocina, lnykryn, > wolfy, rrakus, jskala these 2 are ppc/ppc64 specific and actively maintained, so they should be whitelisted, because they won't have new builds in primary koji Dan -- 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: Heads-up: Obsolete but still included packages
On Mon, 19 Aug 2013 21:45:09 +0100, Peter Robinson wrote: > > yum-utils > > > > I don't think yum-utils should be on that list given that it appears to be > actively maintained and not obsoleted. All these src.rpms build _something_ that is obsoleted by something else. For yum-utils, it's the yum-plugin-security subpackage, which is obsoleted by yum. The closer look at it: yum obsoletes yum-plugin-security < 1.1.32 with yum-utils being at 1.1.31. If yum-utils were bumped to 1.1.32, the Obsoletes would not be high enough anymore, and yum-plugin-security would become installable again. Certainly something that's not right. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[ACTION REQUIRED] Retiring long-term FTBFS packages for Fedora 20
The following packages did not build for two releases and will be retired around 2013-08-26 unless someone rebuilds them or announces to actively working on fixing them. Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Package(co)maintainers === curry gemi, oliver eclipse-phpeclipsembooth, swagiaal libgarmin fab libvpdemunson, hegdevasant, fkocina, lnykryn, rrakus, jskala lsvpd emunson, hegdevasant, fkocina, lnykryn, wolfy, rrakus, jskala mod_mono chkr nautilus-sendto-trac mbooth open-cobols4504kr petitboot dwmw2, tbreeds, jwboyer python-pylons kylev, cicku simulavr ndim smart athimm, scop synce-connector awjb tango-icon-theme cwickert tango-icon-theme-extras cwickert The following packages require above mentioned FTBS packages: Depending on: python-pylons python-repoze-what-pylons (maintained by: spot, lmacken) python-repoze-what-pylons requires python-pylons = 1.0-4.fc17 Depending on: smart PackageKit (maintained by: rhughes, rdieter, stefw, jcm, rnorwood, lmacken, rhughes, timlau, tuxbrewr) PackageKit-smart requires smart = 1.3.1-68.fc17 fedora-package-config-smart (maintained by: athimm, scop) fedora-package-config-smart requires smart = 1.3.1-68.fc17 Depending on: synce-connector synce-gnome (maintained by: awjb) synce-gnome requires odccm = 0.15.2-5.fc17 synce-kpm (maintained by: awjb) synce-kpm requires odccm = 0.15.2-5.fc17 Depending on: tango-icon-theme gnome-theme-curvylooks (maintained by: pgordon) gnome-theme-curvylooks requires tango-icon-theme = 0.8.90-6.fc17 Affected (co)maintainers athimm: smart awjb: synce-connector chkr: mod_mono cicku: python-pylons cwickert: tango-icon-theme-extras, tango-icon-theme dwmw2: petitboot emunson: lsvpd, libvpd fab: libgarmin fkocina: lsvpd, libvpd gemi: curry hegdevasant: lsvpd, libvpd jcm: smart jskala: lsvpd, libvpd jwboyer: petitboot kylev: python-pylons lmacken: python-pylons, smart lnykryn: lsvpd, libvpd mbooth: nautilus-sendto-trac, eclipse-phpeclipse ndim: simulavr oliver: curry pgordon: tango-icon-theme rdieter: smart rhughes: smart rnorwood: smart rrakus: lsvpd, libvpd s4504kr: open-cobol scop: smart spot: python-pylons stefw: smart swagiaal: eclipse-phpeclipse tbreeds: petitboot timlau: smart tuxbrewr: smart wolfy: lsvpd The script creating this output is run and developed by Fedora Release Engineering. Please report issues at its trac instance: https://fedorahosted.org/rel-eng/ The sources of this script can be found at: https://git.fedorahosted.org/cgit/releng/tree/scripts/find-unblocked-orphans.py -- 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: Heads-up: Obsolete but still included packages
> yum-utils > I don't think yum-utils should be on that list given that it appears to be actively maintained and not obsoleted. Peter > zeitgeist-datahub > > [...] > > chktex-1.6.4-12.fc19.src.rpm > classads-1.0.8-7.fc20.src.rpm > detex-2.8-6.fc20.src.rpm > drupal6-drush-4.1-7.fc20.src.rpm > ff-utils-2.4.21-7.fc19.src.rpm > gpp4-1.3.1-5.fc20.src.rpm > ibus-table-array30-1.2.0.20090729-6.fc20.src.rpm > jadetex-3.13-14.fc19.src.rpm > jaxen-bootstrap-1.1-8.2.fc20.src.rpm > joystick-1.2.15-30.fc20.src.rpm > kdirstat-2.5.3-17.fc20.src.rpm > latexdiff-1.0.2-4.fc20.src.rpm > lzma-4.32.7-10.fc20.src.rpm > mate-conf-1.4.0-23.fc20.src.rpm > mate-conf-editor-1.4.0-3.fc19.src.rpm > metapost-metauml-0.2.5-12.fc20.src.rpm > nss-myhostname-0.3-5.fc20.src.rpm > openswan-2.6.38-11.fc19.src.rpm > pdfbook-20070930-10.fc20.src.rpm > pdfjam-2.08-4.fc18.src.rpm > ps2eps-1.68-7.fc20.src.rpm > python-cryptsetup-0.1.4-6.fc20.src.rpm > python-lvm-1.9.2-3.fc20.src.rpm > python-quantumclient-2.2.1-4.fc20.src.rpm > rdate-1.4-24.fc20.src.rpm > ruby-gnome2-0.90.4-2.fc20.1.src.rpm > seahorse-plugins-2.91.6-0.5.git1e35fd9.fc18.src.rpm > tetex-IEEEtran-1.7.1-8.fc20.src.rpm > xmltex-20020625-21.fc20.src.rpm > yum-utils-1.1.31-17.fc20.src.rpm > zeitgeist-datahub-0.9.5-3.fc20.src.rpm > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > -- 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: Heads-up: Obsolete but still included packages
On Mon, 19 Aug 2013 22:30:03 +0200, Michael Schwendt wrote: > > If there are no objections, I can just retire all of them. Okay, I object! Some of them are sub-packages. Obsolete, but still being built! For example, yum-plugin-security from yum-utils, obsoleted by yum. That's really odd. -- 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: Heads-up: Obsolete but still included packages
> If there are no objections, I can just retire all of them. The src.rpm names: chktex classads detex drupal6-drush ff-utils gpp4 ibus-table-array30 jadetex jaxen-bootstrap joystick kdirstat latexdiff lzma mate-conf mate-conf-editor metapost-metauml nss-myhostname openswan pdfbook pdfjam ps2eps python-cryptsetup python-lvm python-quantumclient rdate ruby-gnome2 seahorse-plugins tetex-IEEEtran xmltex yum-utils zeitgeist-datahub [...] chktex-1.6.4-12.fc19.src.rpm classads-1.0.8-7.fc20.src.rpm detex-2.8-6.fc20.src.rpm drupal6-drush-4.1-7.fc20.src.rpm ff-utils-2.4.21-7.fc19.src.rpm gpp4-1.3.1-5.fc20.src.rpm ibus-table-array30-1.2.0.20090729-6.fc20.src.rpm jadetex-3.13-14.fc19.src.rpm jaxen-bootstrap-1.1-8.2.fc20.src.rpm joystick-1.2.15-30.fc20.src.rpm kdirstat-2.5.3-17.fc20.src.rpm latexdiff-1.0.2-4.fc20.src.rpm lzma-4.32.7-10.fc20.src.rpm mate-conf-1.4.0-23.fc20.src.rpm mate-conf-editor-1.4.0-3.fc19.src.rpm metapost-metauml-0.2.5-12.fc20.src.rpm nss-myhostname-0.3-5.fc20.src.rpm openswan-2.6.38-11.fc19.src.rpm pdfbook-20070930-10.fc20.src.rpm pdfjam-2.08-4.fc18.src.rpm ps2eps-1.68-7.fc20.src.rpm python-cryptsetup-0.1.4-6.fc20.src.rpm python-lvm-1.9.2-3.fc20.src.rpm python-quantumclient-2.2.1-4.fc20.src.rpm rdate-1.4-24.fc20.src.rpm ruby-gnome2-0.90.4-2.fc20.1.src.rpm seahorse-plugins-2.91.6-0.5.git1e35fd9.fc18.src.rpm tetex-IEEEtran-1.7.1-8.fc20.src.rpm xmltex-20020625-21.fc20.src.rpm yum-utils-1.1.31-17.fc20.src.rpm zeitgeist-datahub-0.9.5-3.fc20.src.rpm -- 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: Why is AHCI built-in?
On 08/19/2013 01:48 PM, Peter Robinson wrote: > Ultimately if there's missing features you should communicate with the > author of the patch as to why they're not upstream and then you'd not > have to care about whether its built in or a module. Heh. I kind of doubt that the AHCI driver maintainers are interested in adding hardware-specific LED triggers. > Probably on the kernel list if anywhere, I vaguely remember reading > about it. Pointed to the discussion (back in 2008!) by a co-worker. I didn't even know that Fedora had its own kernel list. (I wrongly assumed that this change post-dated the RHEL 6 branch, since AHCI is still a module in RHEL 6.) Thanks for the info! -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- 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: [ACTION REQUIRED] Retiring packages for Fedora 20 v2
The following packages have been retired: alsa-oss firmware-extract firstboot gkrellm-timestamp guiloader justmoon lybniz mars-sim miau openstack-tempo osgal python3-cherrypy vblade Because alsa-oss was retired, mumble needs to be rebuild without OSS support (just removing the BR failed in a scratch build because libspeechd.h cannot be found, maybe this is an unrelated bug) modplugtools needs to be changed to not ship modplugplay anymore, but modplug123 should still work. I will soon post a follow-up message regarding FTBFS packages. Regards Till -- 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: Heads-up: Obsolete but still included packages
On Mon, 19 Aug 2013 21:34:52 +0200, Till Maas wrote: > > > > > https://admin.fedoraproject.org/pkgdb/acls/name/latexdiff > > > > > > Let me rephrase: It is not orphaned/retired/deprecated in pkgdb and > > > there is no dead.package in GIT and it is not blocked in koji. > > > > Right, and yet it's obsoleted by texlive-latexdiff, so no one could > > ever install it or use it. > > > > So, all the above steps should be done on it, or if there's some actual > > reason it's useful, texlive-latexdiff would have to be modified to not > > obsolete it so anyone could actually install or use it. > > Yes, I agree. But it is hard do deduct this from the original mail. :-) Sorry, if we use completely different terminology. :-( With "obsolete" I mean there's an RPM "Obsoletes" tag somewhere for the package. With "retiring" I refer to the package EOL process (e.g. the fedpkg command is "retire". My message also refers to that. -- 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: Heads-up: Obsolete but still included packages
On Mon, Aug 19, 2013 at 10:44:02AM +0200, Michael Schwendt wrote: > A couple of obsolete packages is still included in Rawhide. Usually > that means a package has not been retired yet or has been retired > incompletely: > > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > > In some cases, the dead package is only missing the koji block request > in Fedora rel-eng trac. In other cases, the package has not even been > marked a "dead.package" in git yet: If there are no objections, I can just retire all of them. Regards Till -- 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: Heads-up: Obsolete but still included packages
On Mon, Aug 19, 2013 at 01:25:36PM -0600, Kevin Fenzi wrote: > On Mon, 19 Aug 2013 21:22:49 +0200 > Till Maas wrote: > > > On Mon, Aug 19, 2013 at 07:55:26PM +0100, Peter Robinson wrote: > > > On 19 Aug 2013 19:51, "Till Maas" wrote: > > > > > > How did you create the list? At least this one seems to be a false > > > > positive, because it is not retired: > > > > > > Isn't that what he says in the first sentence... Orphaned but not > > > properly retired? > > > > > > > https://admin.fedoraproject.org/pkgdb/acls/name/latexdiff > > > > Let me rephrase: It is not orphaned/retired/deprecated in pkgdb and > > there is no dead.package in GIT and it is not blocked in koji. > > Right, and yet it's obsoleted by texlive-latexdiff, so no one could > ever install it or use it. > > So, all the above steps should be done on it, or if there's some actual > reason it's useful, texlive-latexdiff would have to be modified to not > obsolete it so anyone could actually install or use it. Yes, I agree. But it is hard do deduct this from the original mail. :-) Regards Till -- 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: Heads-up: Obsolete but still included packages
On Mon, 19 Aug 2013 21:22:49 +0200 Till Maas wrote: > On Mon, Aug 19, 2013 at 07:55:26PM +0100, Peter Robinson wrote: > > On 19 Aug 2013 19:51, "Till Maas" wrote: > > > > How did you create the list? At least this one seems to be a false > > > positive, because it is not retired: > > > > Isn't that what he says in the first sentence... Orphaned but not > > properly retired? > > > > > https://admin.fedoraproject.org/pkgdb/acls/name/latexdiff > > Let me rephrase: It is not orphaned/retired/deprecated in pkgdb and > there is no dead.package in GIT and it is not blocked in koji. Right, and yet it's obsoleted by texlive-latexdiff, so no one could ever install it or use it. So, all the above steps should be done on it, or if there's some actual reason it's useful, texlive-latexdiff would have to be modified to not obsolete it so anyone could actually install or use it. kevin signature.asc Description: PGP 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: Heads-up: Obsolete but still included packages
On Mon, Aug 19, 2013 at 07:55:26PM +0100, Peter Robinson wrote: > On 19 Aug 2013 19:51, "Till Maas" wrote: > > How did you create the list? At least this one seems to be a false > > positive, because it is not retired: > > Isn't that what he says in the first sentence... Orphaned but not properly > retired? > > > https://admin.fedoraproject.org/pkgdb/acls/name/latexdiff Let me rephrase: It is not orphaned/retired/deprecated in pkgdb and there is no dead.package in GIT and it is not blocked in koji. Regards Till -- 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: Heads-up: Obsolete but still included packages
On 19 Aug 2013 19:51, "Till Maas" wrote:
>
> Hi,
>
> On Mon, Aug 19, 2013 at 10:44:02AM +0200, Michael Schwendt wrote:
> > A couple of obsolete packages is still included in Rawhide. Usually
> > that means a package has not been retired yet or has been retired
> > incompletely:
> >
> > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> >
> > In some cases, the dead package is only missing the koji block request
> > in Fedora rel-eng trac. In other cases, the package has not even been
> > marked a "dead.package" in git yet:
>
> > Obsolete ('latexdiff', 'noarch', '0', '1.0.2', '4.fc20')
>
> How did you create the list? At least this one seems to be a false
> positive, because it is not retired:
Isn't that what he says in the first sentence... Orphaned but not properly
retired?
> https://admin.fedoraproject.org/pkgdb/acls/name/latexdiff
>
> Regards
> Till
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
--
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: Heads-up: Obsolete but still included packages
Hi,
On Mon, Aug 19, 2013 at 10:44:02AM +0200, Michael Schwendt wrote:
> A couple of obsolete packages is still included in Rawhide. Usually
> that means a package has not been retired yet or has been retired
> incompletely:
>
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
>
> In some cases, the dead package is only missing the koji block request
> in Fedora rel-eng trac. In other cases, the package has not even been
> marked a "dead.package" in git yet:
> Obsolete ('latexdiff', 'noarch', '0', '1.0.2', '4.fc20')
How did you create the list? At least this one seems to be a false
positive, because it is not retired:
https://admin.fedoraproject.org/pkgdb/acls/name/latexdiff
Regards
Till
--
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: Why is AHCI built-in?
On 19 Aug 2013 19:40, "Ian Pilcher" wrote: > > On 08/19/2013 01:19 PM, Kyle McMartin wrote: > > because it's commonly used and found on basically every machine now. > > there are many advantages to having it built in that outweigh the cons. > > A couple of questions: > > - What are the advantages of having the driver built-in, as compared to > simply ensuring that it's always included in the initramfs? Easy support for the most commonly used options, things like the IP and the Intel sata driver are built in as well for similar means. Ultimately if there's missing features you should communicate with the author of the patch as to why they're not upstream and then you'd not have to care about whether its built in or a module. > - Was this change discussed anywhere? Probably on the kernel list if anywhere, I vaguely remember reading about it. Peter -- 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: Why is AHCI built-in?
On Mon, Aug 19, 2013 at 01:35:16PM -0500, Ian Pilcher wrote: > On 08/19/2013 01:19 PM, Kyle McMartin wrote: > > because it's commonly used and found on basically every machine now. > > there are many advantages to having it built in that outweigh the cons. > > A couple of questions: > > - What are the advantages of having the driver built-in, as compared to > simply ensuring that it's always included in the initramfs? > performance, you'll take fewer tlb misses. > - Was this change discussed anywhere? > among the fedora kernel team at plumbers conf in 2008. --kyle -- 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: Why is AHCI built-in?
On 08/19/2013 01:19 PM, Kyle McMartin wrote: > because it's commonly used and found on basically every machine now. > there are many advantages to having it built in that outweigh the cons. A couple of questions: - What are the advantages of having the driver built-in, as compared to simply ensuring that it's always included in the initramfs? - Was this change discussed anywhere? Thanks! -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- 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: Why is AHCI built-in?
On Mon, Aug 19, 2013 at 01:16:03PM -0500, Ian Pilcher wrote: > Somewhere along the line, the AHCI driver was changed from a module to > being built-in to the kernel. This is a major PITA for anyone who wants > to use a different/customized version of this driver. (I want to > rebuild it with LED triggers for the disk LEDs on my NAS.) > > I haven't been able to find anything in git or BZ about why this was > done, probably because searching on "ahci" and "module" in Bugzilla > isn't exactly productive. > because it's commonly used and found on basically every machine now. there are many advantages to having it built in that outweigh the cons. --kyle -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Why is AHCI built-in?
Somewhere along the line, the AHCI driver was changed from a module to being built-in to the kernel. This is a major PITA for anyone who wants to use a different/customized version of this driver. (I want to rebuild it with LED triggers for the disk LEDs on my NAS.) I haven't been able to find anything in git or BZ about why this was done, probably because searching on "ahci" and "module" in Bugzilla isn't exactly productive. Any pointers? TIA -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- 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: BlueZ Status in Fedora.
On Mon, Aug 19, 2013 at 08:55:01AM -0700, Adam Williamson wrote: > Have you tried Bluetooth on our major desktop environments in F19? :P > > (I kid, I kid, it mostly works well. But still, I have to pair my mouse > every damn time I want to use it, for instance.) Oh, is https://bugzilla.redhat.com/show_bug.cgi?id=716479 still the case? -- Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML) -- 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: BlueZ Status in Fedora.
On Sun, 2013-08-18 at 14:28 -0700, Ryan Rix wrote: > It sounds like BlueZ5 is not ready for Fedora, betwen the "early alpha" XFCE > code, and shipping git BlueDevil, mate and cinnamon don't appear to work with > it ... We're not even at Alpha TC1 yet, remember. It's not unusual for stuff roadmapped for F20 Final to be in a fairly early stage at this point. (Plus what mclasen pointed out about only blocking on GNOME and KDE). > Basically we ship Fedora 20 in a state where one only of our major desktop > environments supports bluetooth in a stable fashion? That seems kind of like > a > disaster waiting to happen. Have you tried Bluetooth on our major desktop environments in F19? :P (I kid, I kid, it mostly works well. But still, I have to pair my mouse every damn time I want to use it, for instance.) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- 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: BlueZ Status in Fedora.
On 19/08/2013 4:31 PM, "Richard Vickery" wrote: > > On Sun, Aug 18, 2013 at 8:03 PM, Matthew Garrett wrote: > > On Sun, Aug 18, 2013 at 02:28:34PM -0700, Ryan Rix wrote: > > > >> Basically we ship Fedora 20 in a state where one only of our major desktop > >> environments supports bluetooth in a stable fashion? That seems kind of like a > >> disaster waiting to happen. > > > > The current release blocking desktops are Gnome and KDE. If those are > > broken then F20 doesn't ship - if they're working, it ships. It'd be > > unfortunate to ship a release that doesn't support the non-blocking > > desktops, but (right now) it's fundamentally up to them to provide the > > development effort to ensure that they have a full feature set. > > > > -- > > Matthew Garrett | mj...@srcf.ucam.org > > -- > > Instead of shipping it, is there a problem with giving it to those on > the developer list and letting us iron out the kinks? > I do not really understand what you mean here /Andreas > -- > Richard > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- 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: promoting to package co-maintainers?
On Mon, 19 Aug 2013 07:35:03 -0400 "Kaleb S. KEITHLEY" wrote: > > Flock is over. How about some action on my ticket? > > Or reject the ticket and tell me why! Sorry for the delay. I went and processed all the back packager-sponsor tickets. Looks like mrunge already added those two folks to packager by the time I got there tho. So, they should be in and can request acls, etc. Sorry again about the delay... kevin -- > > > > Original Message > Subject: promoting to package co-maintainers? > Date: Mon, 12 Aug 2013 08:31:13 -0400 > From: Kaleb S. KEITHLEY > To: Development discussions related to Fedora > > > Hi > > On 7 Aug I opened a trac ticket (as per > https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer) > > to request that two colleagues be > promoted to the packager group so that I can grant them the commit ACL > for the glusterfs package. They both work full time on GlusterFS. > > I have not heard anything in response to the trac ticket and I'm > curious about what the normal amount of time is for action a ticket > like this. > > Thanks, > signature.asc Description: PGP 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: bug filed against "distribution"
Am 19.08.2013 16:37, schrieb Kevin Fenzi: > On Sat, 17 Aug 2013 20:20:33 +0200 > Reindl Harald wrote: > >> because it happens *regulary* and not from time to time >> and not depending on package/maintainer and that is >> a wrong behavior which should be made clear insinde >> the distribution > > So, you are proposing a addition to the package maintainer > responsibilities page? > > (I am not sure this will "solve" the issue, but would give you > somewhere to point people). > > Perhaps: > > "Try and solve bugs or issues for the release against which they were > reported, or if that is impractical note to bug reporters why their bug > cannot be fixed in that release" > > Thoughts? sounds good! 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: BlueZ Status in Fedora.
On Sun, Aug 18, 2013 at 8:03 PM, Matthew Garrett wrote: > On Sun, Aug 18, 2013 at 02:28:34PM -0700, Ryan Rix wrote: > >> Basically we ship Fedora 20 in a state where one only of our major desktop >> environments supports bluetooth in a stable fashion? That seems kind of like >> a >> disaster waiting to happen. > > The current release blocking desktops are Gnome and KDE. If those are > broken then F20 doesn't ship - if they're working, it ships. It'd be > unfortunate to ship a release that doesn't support the non-blocking > desktops, but (right now) it's fundamentally up to them to provide the > development effort to ensure that they have a full feature set. > > -- > Matthew Garrett | mj...@srcf.ucam.org > -- Instead of shipping it, is there a problem with giving it to those on the developer list and letting us iron out the kinks? -- Richard -- 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: bug filed against "distribution"
On Sat, 17 Aug 2013 20:20:33 +0200 Reindl Harald wrote: > becuase it happens *regualary* and not from time to time > and not depending on package/maintainer and that is > a wron gbehavior which should be made clear insinde > the distribution So, you are proposing a addition to the package maintainer responsibilities page? (I am not sure this will "solve" the issue, but would give you somewhere to point people). Perhaps: "Try and solve bugs or issues for the release against which they were reported, or if that is impractical note to bug reporters why their bug cannot be fixed in that release" Thoughts? kevin signature.asc Description: PGP 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
[Owner-change] Fedora packages ownership change
Change in ownership over the last 168 hours === 5 packages were orphaned python-xklavier [EL-6] was orphaned by pbrobinson Python bindings for libxklavier https://admin.fedoraproject.org/pkgdb/acls/name/python-xklavier vblade [EL-5,EL-6,devel,f18,f19] was orphaned by ausil Virtual EtherDrive (R) blade daemon https://admin.fedoraproject.org/pkgdb/acls/name/vblade mikmod [EL-6] was orphaned by pbrobinson Music module player https://admin.fedoraproject.org/pkgdb/acls/name/mikmod miau [EL-5,EL-6,devel,f18,f19] was orphaned by ausil Full-featured IRC bouncer https://admin.fedoraproject.org/pkgdb/acls/name/miau alsa-oss [devel,f18,f19] was orphaned by ausil Advanced Linux Sound Architecture (ALSA) wrapper for OSS https://admin.fedoraproject.org/pkgdb/acls/name/alsa-oss 44 packages unorphaned -- cicku unorphaned : bwm-ng [EL-6,devel,f18,f19] filiperossetunorphaned : clusterssh [devel,f18,f19] jkastnerunorphaned : conserver [devel,f18,f19] fab unorphaned : examiner [devel,f19] cicku unorphaned : aoetools [EL-6,devel,f18,f19] jmlich unorphaned : less [devel,f18,f19] mbooth unorphaned : XmlSchema [devel,f18,f19] cicku unorphaned : graphviz [devel,f18,f19] mmilata unorphaned : linuxdoc-tools [devel] mizdebskunorphaned : joda-convert [devel,f18,f19] gil unorphaned : apache-commons-ognl [devel] frixxon unorphaned : drehatlas-warender-bibliothek-fonts [devel,f18] cicku unorphaned : ngrep [EL-6,devel,f18,f19] mizdebskunorphaned : jakarta-commons-httpclient [devel,f18,f19] lkundrakunorphaned : dissy [devel,devel,devel] mizdebskunorphaned : avalon-framework [devel,f18,f19] cicku unorphaned : libdnet [EL-6,devel,f18,f19] mizdebskunorphaned : aopalliance [devel,f18,f19] cicku unorphaned : scanssh [devel,f18,f19] cicku unorphaned : derelict [devel,f18,f19] mizdebskunorphaned : xom [devel,f18,f19] mbooth unorphaned : bluecove [devel,f19] cicku unorphaned : dayplanner [devel,f18,f19] cicku unorphaned : txt2rss [devel,f18,f19] cicku unorphaned : gl3n [devel,f18,f19] cicku unorphaned : perl-X11-Protocol [EL-6,devel,f18,f19] mizdebskunorphaned : avalon-logkit [devel,f18,f19] mbooth unorphaned : java-uuid-generator [EL-6,devel,f18,f19] mizdebskunorphaned : apache-parent [devel,f18,f19] vicodan unorphaned : libgnomecups [devel,f18,f19] mizdebskunorphaned : bcel [devel,f18,f19] mizdebskunorphaned : bsf [devel,f18,f19] mizdebskunorphaned : xalan-j2 [devel,f18,f19] dchen unorphaned : zanata-python-client [EL-5,EL-6,devel,f18,f19] cicku unorphaned : libstatgrab [EL-6,devel,f18,f19] cicku unorphaned : rblcheck [devel,f18,f19] mizdebskunorphaned : tagsoup [devel,f18,f19] rdieter unorphaned : libpng12 [devel] cicku unorphaned : cal3d [EL-5,EL-6,devel,f18,f19] cicku unorphaned : httrack [devel,f18,f19] cheeselee unorphaned : banner [EL-5,EL-6,devel,f18,f19] mbooth unorphaned : derby [EL-5,EL-6,devel,f18,f19] mbooth unorphaned : ezmorph [devel,f18,f19] mizdebskunorphaned : javassist [devel,f18,f19] 5 packages were retired rhevsh [devel] was retired by mmahut A command-line interface to Red Hat Enterprise Virtualization https://admin.fedoraproject.org/pkgdb/acls/name/rhevsh pypolicyd-spf [EL-5] was retired by bojan SPF Policy Server for Postfix (Python implementation) https://admin.fedoraproject.org/pkgdb/acls/name/pypolicyd-spf jbossws-native [devel] was retired by goldmann JBossWS Native https://admin.fedoraproject.org/pkgdb/acls/name/jbossws-native rdate [devel] was retired by hhorak Tool for getting the date/time from a remote machine https://admin.fedoraproject.org/pkgdb/acls/name/rdate gpointing-device-settings [devel,f18,f19] was retired by vicodan Configuration tool for pointing devices https://admin.fedoraproject.org/pkgdb/acls/name/gpointing-device-settings 176 packages changed owner -- mmaslanogave to jplesnik : perl-Dancer [f18,f19] mmaslanogave to jplesnik : perl-Test-Pod [f18,f19] mmaslanogave to jplesnik : perl-Tie-Simple [f18,f19] mmaslanogave to jplesnik : perl-XML-Dumper [f18,f19] mmaslanogave to jplesnik : perl-Data-TreeDumper [f18,f19] mmaslanogave to jplesnik : perl-Debug-Client [f18,f19] mmaslanogave to jplesnik : perl-Module-Extract [f18,f19] mmaslanogave to jplesnik : perl-Archive-Tar [f18,f19] mmaslanogave to jplesnik : perl-Test-Compile [f1
[Bug 998212] perl-Time-HiRes-1.9726 is available
https://bugzilla.redhat.com/show_bug.cgi?id=998212 Petr Šabata changed: What|Removed |Added Assignee|ppi...@redhat.com |psab...@redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=qlAdV0S5z8&a=cc_unsubscribe -- 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: F20 Self Contained Change: Ruby on Rails 4.0
Hi, I am happy to announce that Ruby on Rails 4.0 has landed in Fedora Rawhide[1]. If you have any packages that depends on Rails, it's a good time to test them. Note: Some dependent RubyGems were updated afterwards to support the newest version of Rails[2], some not. Regards Josef [1] https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_4.0 [2] https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_4.0#Dependencies -- 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: mass rebuild update
On 08/19/2013 02:25 PM, drago01 wrote: On Mon, Aug 19, 2013 at 2:21 PM, Jaroslav Reznik wrote: - Original Message - On 08/19/2013 01:32 PM, drago01 wrote: On Mon, Aug 19, 2013 at 1:28 PM, Jaroslav Reznik wrote: - Original Message - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I have merged perl info f20 and started the mass rebuild. Hi! A friendly reminder - "Branch Fedora 20 from Rawhide" is planned tomorrow (2013-08-20) and "Alpha Change Deadline" is also pretty soon as Dennis pointed out (2013-09-03). Please postpone this. IMO, this is much too early. Also take into account what time of year it is: Summer Holidays (at least in Europe). Well, the reason why it was scheduled so early (and already postponed by two weeks) are other holidays - we have to avoid hitting December, when everyone is on vacations :(. One week = Thanksgivings, two weeks = Christmas... But what has the branch date to do with the mass rebuild? I mean can't people fix stuff after alpha (before beta) unless the package not working is an alpha blocker? After branching, new "features"/"breakdowns" will be introduced into rawhide causing further instabilities and FTBFSes to rawhide. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Broken dependencies: perl-MIME-Lite-HTML
perl-MIME-Lite-HTML has broken dependencies in the rawhide tree: On x86_64: perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) On i386: perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) On armhfp: perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.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
Broken dependencies: perl-Encode-JP-Mobile
perl-Encode-JP-Mobile has broken dependencies in the rawhide tree: On x86_64: perl-Encode-JP-Mobile-0.30-2.fc19.x86_64 requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Encode-JP-Mobile-0.30-2.fc19.i686 requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Encode-JP-Mobile-0.30-2.fc19.armv7hl requires perl(:MODULE_COMPAT_5.16.2) 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: slic3r
slic3r has broken dependencies in the rawhide tree: On x86_64: slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3) On i386: slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3) On armhfp: slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3) 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-ParseUtil-Domain
perl-ParseUtil-Domain has broken dependencies in the rawhide tree: On x86_64: perl-ParseUtil-Domain-2.22-3.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-ParseUtil-Domain-2.22-3.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-ParseUtil-Domain-2.22-3.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) 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-MooseX-TrackDirty-Attributes
perl-MooseX-TrackDirty-Attributes has broken dependencies in the rawhide tree: On x86_64: perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) 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: mass rebuild update
On 08/19/2013 02:21 PM, Jaroslav Reznik wrote: - Original Message - On 08/19/2013 01:32 PM, drago01 wrote: On Mon, Aug 19, 2013 at 1:28 PM, Jaroslav Reznik wrote: - Original Message - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I have merged perl info f20 and started the mass rebuild. Hi! A friendly reminder - "Branch Fedora 20 from Rawhide" is planned tomorrow (2013-08-20) and "Alpha Change Deadline" is also pretty soon as Dennis pointed out (2013-09-03). Please postpone this. IMO, this is much too early. Also take into account what time of year it is: Summer Holidays (at least in Europe). Well, the reason why it was scheduled so early (and already postponed by two weeks) are other holidays - we have to avoid hitting December, when everyone is on vacations :(. One week = Thanksgivings, two weeks = Christmas... Well, ... many people are on vacation > 2 weeks around this time of year - probably most them in August ;) ... as I feel, this time, the changes introduced into Fedora were too ambitious with some of the having been introduced too late. Notably the docdir changes, texinfo-5.x, perl-5.18 and the texlive mess (interestingly, the impact of the arm having been introduced is comparatively low) As a consequence of this, I don't see an alternative to further postponing. Ralf -- 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: mass rebuild update
On Mon, Aug 19, 2013 at 2:21 PM, Jaroslav Reznik wrote: > - Original Message - >> On 08/19/2013 01:32 PM, drago01 wrote: >> > On Mon, Aug 19, 2013 at 1:28 PM, Jaroslav Reznik >> > wrote: >> >> - Original Message - >> >>> -BEGIN PGP SIGNED MESSAGE- >> >>> Hash: SHA1 >> >>> >> >>> Hi all, >> >>> >> >>> I have merged perl info f20 and started the mass rebuild. >> >> >> >> Hi! >> >> A friendly reminder - "Branch Fedora 20 from Rawhide" is planned >> >> tomorrow (2013-08-20) and "Alpha Change Deadline" is also pretty soon >> >> as Dennis pointed out (2013-09-03). >> Please postpone this. IMO, this is much too early. >> >> Also take into account what time of year it is: Summer Holidays (at >> least in Europe). > > Well, > the reason why it was scheduled so early (and already postponed by two > weeks) are other holidays - we have to avoid hitting December, when > everyone is on vacations :(. One week = Thanksgivings, two weeks = > Christmas... But what has the branch date to do with the mass rebuild? I mean can't people fix stuff after alpha (before beta) unless the package not working is an alpha blocker? -- 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: mass rebuild update
- Original Message - > On 08/19/2013 01:32 PM, drago01 wrote: > > On Mon, Aug 19, 2013 at 1:28 PM, Jaroslav Reznik > > wrote: > >> - Original Message - > >>> -BEGIN PGP SIGNED MESSAGE- > >>> Hash: SHA1 > >>> > >>> Hi all, > >>> > >>> I have merged perl info f20 and started the mass rebuild. > >> > >> Hi! > >> A friendly reminder - "Branch Fedora 20 from Rawhide" is planned > >> tomorrow (2013-08-20) and "Alpha Change Deadline" is also pretty soon > >> as Dennis pointed out (2013-09-03). > Please postpone this. IMO, this is much too early. > > Also take into account what time of year it is: Summer Holidays (at > least in Europe). Well, the reason why it was scheduled so early (and already postponed by two weeks) are other holidays - we have to avoid hitting December, when everyone is on vacations :(. One week = Thanksgivings, two weeks = Christmas... Jaroslav > Many people have been on vacation and some still are (Around here, > summer holidays end early/mid September). > > >> Looking on the current list [1], > >> there are still quite a few failing packages - so please, take a look > >> on your packages ;-). > >> > >> Jaroslav > >> > >> /me has two build failures too... > >> > >> [1] http://ausil.fedorapeople.org/f20-failed.html > > > > I don't have any packages on that list but wouldn't it make sense to > > keep the build logs a bit longer? > > ACK. this would have been very helpful. > > > That way people have to fire off a build just to see the error logs > > which isn't really the most efficient workflow. > Exactly. Having worked though many of them recently, lack of the > build.logs isn't very helpful. > > Ralf > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- 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: mass rebuild update
在 2013-8-19 PM7:49，"Ralf Corsepius" 写道： > Please postpone this. IMO, this is much too early. > > Also take into account what time of year it is: Summer Holidays (at least in Europe). > > Many people have been on vacation and some still are (Around here, summer holidays end early/mid September). +1 -- 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: mass rebuild update
On 08/19/2013 01:32 PM, drago01 wrote: On Mon, Aug 19, 2013 at 1:28 PM, Jaroslav Reznik wrote: - Original Message - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I have merged perl info f20 and started the mass rebuild. Hi! A friendly reminder - "Branch Fedora 20 from Rawhide" is planned tomorrow (2013-08-20) and "Alpha Change Deadline" is also pretty soon as Dennis pointed out (2013-09-03). Please postpone this. IMO, this is much too early. Also take into account what time of year it is: Summer Holidays (at least in Europe). Many people have been on vacation and some still are (Around here, summer holidays end early/mid September). Looking on the current list [1], there are still quite a few failing packages - so please, take a look on your packages ;-). Jaroslav /me has two build failures too... [1] http://ausil.fedorapeople.org/f20-failed.html I don't have any packages on that list but wouldn't it make sense to keep the build logs a bit longer? ACK. this would have been very helpful. That way people have to fire off a build just to see the error logs which isn't really the most efficient workflow. Exactly. Having worked though many of them recently, lack of the build.logs isn't very helpful. Ralf -- 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: Suggestion: bmap files and bmaptool
On Sun, 2013-08-18 at 16:43 +0100, Pádraig Brady wrote: > You definitely need the fsync before doing the fiemap. > We saw this on certain file systems including ext4 when adding > fiemap support (efficient reading of holes) to cp. > This is a bug in the fiemap interface IMHO in that it returns > fairly useless data unless FIEMAP_FLAG_SYNC is specified. > For a general utility like cp, we couldn't sync each file before copying > (even only large files), so we restrict fiemap usage to files that > have a different disk usage than apparent size and so probably contain holes. I see, thanks a lot for suggestion. Just to make it clear, this is more like working around file-system bugs, which, as I guess, were present in early days of FIEMAP. I'll look into adding FIEMAP_FLAG_SYNC to Fiemap.py in bmap-tools, thanks! -- Best Regards, Artem Bityutskiy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fwd: promoting to package co-maintainers?
Flock is over. How about some action on my ticket? Or reject the ticket and tell me why! Original Message Subject: promoting to package co-maintainers? Date: Mon, 12 Aug 2013 08:31:13 -0400 From: Kaleb S. KEITHLEY To: Development discussions related to Fedora Hi On 7 Aug I opened a trac ticket (as per https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer) to request that two colleagues be promoted to the packager group so that I can grant them the commit ACL for the glusterfs package. They both work full time on GlusterFS. I have not heard anything in response to the trac ticket and I'm curious about what the normal amount of time is for action a ticket like this. Thanks, -- Kaleb -- 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: Suggestion: bmap files and bmaptool
On Sat, 2013-08-17 at 17:09 +0100, Richard W.M. Jones wrote: > On Thu, Aug 15, 2013 at 12:34:26PM -0500, Eric Sandeen wrote: > > But then there's the issue of transporting these sparse files > > around. We have had the same problem in the past with large e2image > > metadata image files, which may be terabytes in length, with only > > gigabytes or megabytes of real data. e2image _itself_ creates a > > sparse file, but bzipping it or rsyncing it still processes > > terabytes of zeros, and loses all notion of sparseness. > > xz preserves sparseness. We use it for preserving and compressing > virt-sparsify'd images. Right, this is a good solution for the problem area of just saving the sparseness and later restoring it. The problem area for bmaptool is a bit wider. 1. There are large images which are inherently sparse 2. They are distributed via ftp/http/etc servers How do we enable the users flashing these images a) very quickly b) easily c) without breaking the old way of flashing (dd) For the first part, we exploit the sparseness information, which is saved in the bmap file. For the second part, we implement stream-reading directly from the remote service, stream-decompressing on-the fly, and flashing in parallel. This rules out the "xz saves sparseness" design. For the third part, we keep the sparseness information in a separate file which makes it entirely optional. -- Best Regards, Artem Bityutskiy -- 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: mass rebuild update
On Mon, Aug 19, 2013 at 1:28 PM, Jaroslav Reznik wrote: > - Original Message - >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi all, >> >> I have merged perl info f20 and started the mass rebuild. > > Hi! > A friendly reminder - "Branch Fedora 20 from Rawhide" is planned > tomorrow (2013-08-20) and "Alpha Change Deadline" is also pretty soon > as Dennis pointed out (2013-09-03). Looking on the current list [1], > there are still quite a few failing packages - so please, take a look > on your packages ;-). > > Jaroslav > > /me has two build failures too... > > [1] http://ausil.fedorapeople.org/f20-failed.html I don't have any packages on that list but wouldn't it make sense to keep the build logs a bit longer? That way people have to fire off a build just to see the error logs which isn't really the most efficient workflow. We should keep the logs for the most recent build attempt until a newer build obsoletes them. Dennis? -- 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: mass rebuild update
- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all, > > I have merged perl info f20 and started the mass rebuild. Hi! A friendly reminder - "Branch Fedora 20 from Rawhide" is planned tomorrow (2013-08-20) and "Alpha Change Deadline" is also pretty soon as Dennis pointed out (2013-09-03). Looking on the current list [1], there are still quite a few failing packages - so please, take a look on your packages ;-). Jaroslav /me has two build failures too... [1] http://ausil.fedorapeople.org/f20-failed.html > You can see the current list of failures[1] and list to be built[2]. > Both lists are updated every 5 minutes. at the end of the initial run > though we will file bugs for all FTBFS. Please be sure to get on top of > FTBFS quickly as there is not a lot of time before Alpha Change > deadline. > > Dennis > > [1] http://ausil.fedorapeople.org/f20-failed.html > [2]http://ausil.fedorapeople.org/f20-needsbuilt.html > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.19 (GNU/Linux) > > iEYEARECAAYFAlH8kA4ACgkQkSxm47BaWffI3ACfQksbRVmtFfabJFyBWfdLqyP/ > 6ZoAoKv8IAILjC48kJSXNkGvtCJB/Bis > =pTaW > -END PGP SIGNATURE- > ___ > devel-announce mailing list > devel-annou...@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- 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: Suggestion: bmap files and bmaptool
On Fri, 2013-08-16 at 09:51 -0500, Eric Sandeen wrote: > by single file I meant a _single_ file, not the original file and a mapping > file. :) Oh, sorry, OK. > I realize that you have a fully-fledged set of tools, and you're not looking > for new directions, but I was thinking about encoding mapping info & file data > into a single file, with a tool to extract it again. That way there's nothing > to get out of sync. Well, I do wish to know about alternatives, or the better ways to do it, of course. > Actually, now that I think about it qemu-img can do that already: > (sorry, I'm getting a little off topic here, bear with me) > > # truncate --size=1g fsfile > # mkfs.ext4 fsfile > # cp fsfile --sparse=never fsfile.copy > > // fsfile is sparse; the copy is not. > > # du -hc fsfile* > 49M fsfile > 1.0G fsfile.copy > > # qemu-img convert -f raw -O qcow fsfile.copy fsfile.qcow > > // the qcow image now contains only data+mapping info, > // no zero ranges: > # du -h fsfile.qcow > 832K fsfile.qcow > > // and can be re-extracted into a sparse file > > # qemu-img convert -O raw fsfile.qcow fsfile.copy2 > # du -hc fsfile.copy2 > 352K fsfile.copy2 So from 49M down to 352K, sparseness increased by 48M? Where it came from? Must be that this command turned zero blocks into gaps. Like the zeroed out inode tables, etc. > Ok, sorry for that diversion, but that's cool - the tool I want > already exists, and I hadn't realized it. :) Exactly this usage is not good enough for flashing purposes, because when flashing to a block device you have to flash the zeroes, you cannot skip them as you do for holes. But I am sure the qcow tools can save sparseness without turning zeroes into gaps, or at least this should not be too difficult to implement this. But in case of bmaptool I chose to keep the sparseness information in a separate file because I wanted to make sure the bmap is optional. Those who use Windows/Mac or do not want to install any additional tools could still use the old method of throwing the entire image to the target block device. Another goal I had is to make the additional bmap file to be a human-readable text file. But yes, having all in one file does have its own advantages. -- Best Regards, Artem Bityutskiy -- 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: looking for sponsor
Hello, I would like to ask again for somebody to sponsor me and help me finish review and packaging of gimp-separate+. Thank you in advance. Peter On 08/05/2013 10:22 PM, Peter Hanecak wrote: > Hello, > > after initial slow progress I'm now looking for a sponsor to finish the > review process and packaging of gimp-separate+: > > https://bugzilla.redhat.com/show_bug.cgi?id=913289 > > > Thank you in advance for help. > > Sincerely > > Peter > > > > On 02/20/2013 10:26 PM, Peter Hanecak wrote: >> Hello, >> >> I've been asked by Luya Tshimbalanga to >> maintain the gimp-separate+ package for official Fedora project so that >> it can be included in Design Suite Livemedia. >> >> Having read some introductory information, I would now like to introduce >> myself with few short facts: >> >> - I'm using Linux (at start Red Hat, later Fedora) since roughly 1997. >> >> - To ease the maintenance of my systems, I'm creating RPM packages "just >> for myself" since 1998 - this one seems to be the oldest one: >> >> http://hany.sk/~hany/RPM/doors1/jserv-doc-0.9.11-2.i386.html >> >> - I'm supporter of Free and Open Source Software and small-scale >> contributor, more recently broadening it with participation in Open Data >> initiatives. >> >> - Now, Luya's invite finally pushed me to come closer to the Fedora project. >> >> - I'm earning a living by doing software development and related >> consulting work. >> >> - I'm married with two children. >> >> >> I'm looking forward for future cooperation. And I would also like to >> thank in advance to all which will help me to get through initial stages >> of first package submission >> (https://bugzilla.redhat.com/show_bug.cgi?id=913289). >> >> Sincerely >> >> Peter >> >> >> > > > -- Peter Hanecak http://hany.sk/~hany/ GnuPG: http://hany.sk/~hany/gpg/CCB496F1.txt 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: Merging accounts on ask.fedoraproject.org
On Fri, Aug 16, 2013 at 09:05:34PM +1000, Ankur Sinha wrote: > You should be able to click on your profile and then use the "manage > login methods" to merge your logins etc. That works just fine in my case, thanks! -- Later, Lukas "lzap" Zapletal irc: lzap #theforeman -- 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: [Java package] add_to_maven_depmap macro issue
On 08/18/2013 07:03 AM, Ankur Sinha wrote: > Hi, > > One of my packages: dcm4che-test fails to build for rawhide currently. > There's a bug filed here[1]. The build.log seems to fail on the > "add_to_maven_depmap" macro. I think it doesn't find it at all[2]. Could > someone please tell me if I'm missing a BR or if the macros have > changed[3]? > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=992114 > [2] http://ankursinha.fedorapeople.org/dcm4che-build.log > [3] > http://fedoraproject.org/wiki/Java/JPPMavenReadme#Packages_adding_their_own_depmaps %add_to_maven_depmap has been obsolete for long time and it was recently removed. See my announcements on java-devel [1,2]. -- Mikolaj Izdebski IRC: mizdebsk [1] https://lists.fedoraproject.org/pipermail/java-devel/2013-July/004834.html [2] https://lists.fedoraproject.org/pipermail/java-devel/2013-July/004863.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Builds using latex2html gets stuck infinitely (#994883)
Hello, can someone please check this latex2html bug [1]? I've reported it many times on this list on a different thread but somehow it went unnoticed. I know user jnovy has left Redhat, but the package is still owned by him [2] and is blocking my builds since the beginning of August. Shouldn't the package be orphaned? Thanks, --Simone [1] https://bugzilla.redhat.com/show_bug.cgi?id=994883 [2] https://admin.fedoraproject.org/pkgdb/acls/name/latex2html -- You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson). http://xkcd.com/229/ http://negativo17.org/ -- 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: Scala package owner unresponsive
On Sun, 18 Aug 2013 21:41:52 -0600, Jerry James wrote: > On Sun, Aug 18, 2013 at 9:35 PM, Will Benton wrote: > > (1) As far as I can tell, the package for Scala 2.9.2 on F19 (2.9.2-2) has > > broken dependencies; I can't install it via yum on my new F19 install. Is > > this the case for anyone else? If so, wouldn't it be best to have a > > working Scala 2.9 package in F19 and introduce 2.10 in a later release? > > Version 2.9.2-4 was built for F-18, but was never built for F-19 or > F-20. The changelog entries for -3 and -4 say: > > * Wed Jan 23 2013 Jochen Schmitt - 2.9.2-4 > - Fix multiuser issues with fsc on /tmp/scala-devel directory (#903160) > > * Sun Nov 25 2012 Jochen Schmitt 2.9.2-3 > - Fix OSGI dependency issue Well, the builds failed: http://koji.fedoraproject.org/koji/packageinfo?packageID=6830 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Heads-up: Obsolete but still included packages
A couple of obsolete packages is still included in Rawhide. Usually
that means a package has not been retired yet or has been retired
incompletely:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
In some cases, the dead package is only missing the koji block request
in Fedora rel-eng trac. In other cases, the package has not even been
marked a "dead.package" in git yet:
Obsolete ('chktex', 'i686', '0', '1.6.4', '12.fc19')
Obsolete ('classads-devel', 'i686', '0', '1.0.8', '7.fc20')
Obsolete ('classads', 'i686', '0', '1.0.8', '7.fc20')
Obsolete ('classads-static', 'i686', '0', '1.0.8', '7.fc20')
Obsolete ('detex', 'i686', '0', '2.8', '6.fc20')
Obsolete ('drupal6-drush', 'noarch', '0', '4.1', '7.fc20')
Obsolete ('ff-utils', 'i686', '0', '2.4.21', '7.fc19')
Obsolete ('gpp4-devel', 'i686', '0', '1.3.1', '5.fc20')
Obsolete ('gpp4', 'i686', '0', '1.3.1', '5.fc20')
Obsolete ('ibus-table-array30', 'noarch', '0', '1.2.0.20090729', '6.fc20')
Obsolete ('jadetex', 'noarch', '0', '3.13', '14.fc19')
Obsolete ('jaxen-bootstrap', 'noarch', '0', '1.1', '8.2.fc20')
Obsolete ('joystick', 'i686', '0', '1.2.15', '30.fc20')
Obsolete ('kdirstat', 'i686', '0', '2.5.3', '17.fc20')
Obsolete ('latexdiff', 'noarch', '0', '1.0.2', '4.fc20')
Obsolete ('lzma', 'i686', '0', '4.32.7', '10.fc20')
Obsolete ('mate-conf-devel', 'i686', '0', '1.4.0', '23.fc20')
Obsolete ('mate-conf-editor', 'i686', '0', '1.4.0', '3.fc19')
Obsolete ('mate-conf-gtk', 'i686', '0', '1.4.0', '23.fc20')
Obsolete ('mate-conf', 'i686', '0', '1.4.0', '23.fc20')
Obsolete ('metapost-metauml', 'noarch', '0', '0.2.5', '12.fc20')
Obsolete ('nss-myhostname', 'i686', '0', '0.3', '5.fc20')
Obsolete ('openswan', 'i686', '0', '2.6.38', '11.fc19')
Obsolete ('pdfbook', 'i686', '0', '20070930', '10.fc20')
Obsolete ('pdfjam', 'noarch', '0', '2.08', '4.fc18')
Obsolete ('ps2eps', 'i686', '0', '1.68', '7.fc20')
Obsolete ('python-cryptsetup', 'i686', '0', '0.1.4', '6.fc20')
Obsolete ('python-lvm', 'i686', '0', '1.9.2', '3.fc20')
Obsolete ('python-quantumclient', 'noarch', '2', '2.2.1', '4.fc20')
Obsolete ('ruby-gtksourceview2-devel', 'i686', '0', '0.90.4', '2.fc20.1')
Obsolete ('ruby-gtksourceview2', 'i686', '0', '0.90.4', '2.fc20.1')
Obsolete ('seahorse-plugins', 'i686', '0', '2.91.6', '0.5.git1e35fd9.fc18')
Obsolete ('tetex-IEEEtran', 'noarch', '0', '1.7.1', '8.fc20')
Obsolete ('xmltex', 'noarch', '0', '20020625', '21.fc20')
Obsolete ('yum-plugin-security', 'noarch', '0', '1.1.31', '17.fc20')
Obsolete ('zeitgeist-datahub', 'i686', '0', '0.9.5', '3.fc20')
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 992666] perl-Language-Expr: FTBFS in rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=992666 --- Comment #3 from Paul Howarth --- It still doesn't work with the new Regexp::Grammars 1.031 either. Looks like we might have to wait for Perl 5.18.2. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=nM8g5dc41l&a=cc_unsubscribe -- 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: Schedule for Wednesday's FESCo Meeting (2013-08-14)
On 16. 8. 2013 at 15:20:57, Bill Nottingham wrote: > Matthias Clasen (mcla...@redhat.com) said: > > On Fri, 2013-08-16 at 08:42 +0200, Jan Zelený wrote: > > > Actually no, the system is all hacked up and works in a super-abusive > > > way, see https://bugzilla.redhat.com/show_bug.cgi?id=979083 > > > > That bug is really an illustration why it is just wrong to keep > > information about the update history in a semi-private 'db' that only > > yum gets to access. > > > > This information belongs into the journal. We have the change to fix > > that in the dnf transition. > > As long as the journal is rotated out at arbitrary times due to space > reasons, I really really don't think the information belongs there. Agreed. This information doesn't belong to journal and we have no intentions to put it there. > It should still be in a public db for other things to use, though. We already have a plan to extract the db-handling code from dnf to an external library. That should make the situation more developer friendly. Thanks Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
