Re: xfce-weather-plugin stopped working
On 11/05/2011 06:11 AM, Chris Adams wrote: Once upon a time, Heiko Adamsfedora-upda...@heiko-adams.de said: yesterday in the afternoon the xfce-weather-plugin suddenly stopped working and allways displays No Data. Trying to switch my location or update my fedora 16 against updates-testing also didn't solve that problem. Does it use The Weather Channel (weather.com) as its data source? They cut off the old free API and now charge for the new one. Hi, http://developer.yahoo.com/weather/ is this perhaps an alternative? Perhaps we could collect weather services and then choose the service which makes it easiest to port the plugin. Johannes -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 heads up: gnome-shell for everyone!
On 05.11.2011 01:09, Bojan Smojver wrote: Ian Malone ibmalone at gmail.com writes: This is essentially giving up. It's frustrating to be stuck on overview mode on a four core machine while gnome-shell is doing /something/ but you don't know what. If it worked fluidly it would be okay. For me, it goes further than that. I do not want overview mode - ever. Fast, slow - in any shape or form. It reduces visibility of my desktop in normal use, introduces kitchen sink approach to doing something else, attacks me with unnecessary animations when I never asked for them etc. It's just silliness that should be dropped. Just look at all the extensions that sprung up: - extension to have apps menu on the top bar - extension to switch workspaces from the top bar - extension to have constant dash Essentially, extensions to have Gnome 2. PS. Yes, overview _still_ looks great on YouTube. :-) Yet look at all the happy users of default Gnome 3! I am one of them and I went directly from the tilling-WM Xmonad to gnome 3! So you can't say it's only for absolute noobs :). I installed it and it took about a week to get used to it so that I stopped thinking why the heck did they do it but instead started to understand the new Concepts. Today after about a Year of usage I have to say that its the best user interface that I ever used so far! The only negative points that I still don't get is the removal of the power of button (without config to change it). But yes there is an extension to add it again! So just because the rants are much more visible don't think it is the majority! ;) enaut -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: xfce-weather-plugin stopped working
On 11/05/2011 09:36 AM, Johannes Lips wrote: On 11/05/2011 06:11 AM, Chris Adams wrote: Once upon a time, Heiko Adamsfedora-upda...@heiko-adams.de said: yesterday in the afternoon the xfce-weather-plugin suddenly stopped working and allways displays No Data. Trying to switch my location or update my fedora 16 against updates-testing also didn't solve that problem. Does it use The Weather Channel (weather.com) as its data source? They cut off the old free API and now charge for the new one. Hi, http://developer.yahoo.com/weather/ is this perhaps an alternative? Perhaps we could collect weather services and then choose the service which makes it easiest to port the plugin. Johannes http://blog.programmableweb.com/2010/02/08/googles-secret-weather-api/ Just another one. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: reporting bugs
On 5 November 2011 00:50, Orion Poplawski or...@cora.nwra.com wrote: On 11/04/2011 05:39 PM, Ian Malone wrote: On 4 November 2011 17:23, Kevin Koflerkevin.kof...@chello.at wrote: Ian Malone wrote: If I filed every bug in the distro in upstream I'd have a dozen different bugzilla accounts by now. So what? Maintainers are not messengers, they have other work to do than forwarding the bugs you're too lazy to file directly at the right place. Is there any point in me reporting any bug in Fedora bugzilla ever then? Sure, but understand that it may not be as effective as reporting upstream. I think it is useful for tracking purposes and for other Fedora users to find (and why I hate the closed-upstream approach). Sometimes it really is a bug in the Fedora package or in interaction with Fedora libraries. Absolutely agree, which is why my first response is to file in Fedora. Additionally Fedora will have a particular version of a given package, the maintainer hopefully knows more than me about differences and the current development of their packages, part of the role must be to facilitate communication with upstream. If there's one person reporting a bug they know nothing about then telling them to go upstream is fine, if five people have reported bugs in Fedora then it's probably necessary to take a larger role in coordinating with upstream. Unless Fedora believes that the maintainer's responsibility stops at getting the package built successfully there is a communication element to the role. This includes things they can do without ever looking at code, like knowing about how the upstream for their package does things or knowing particular people to contact. But many (most) Fedora packagers are over worked or do this in their very limited free time and are almost certainly not as experienced with the code as the upstream maintainers. I don't expect a maintainer to fix a bug, I don't really expect them to post it upstream either if it's just me reporting it, but there did used to be at least a triage process. Yes, I have dozens of accounts in upstream issue trackers. No big deal. I want the issues I'm running up against fixed as soon as possible and filing upstream I've found is the most effective means. Filing in both is even better. But I won't call you lazy if you don't :) Thank you, I did object to being called lazy on the basis I don't first file every bug I see in the upstream. Package maintainers don't have a monopoly on being busy or having other commitments, but they have volunteered to take on some responsibility. What would be nice would be the ability to forward bugs upstream from within bugzilla. Having dozens of accounts you hardly ever use becomes a maintenance issue: details like the last few times I reported gnome bugs directly I had to reset my password because I kept getting caught out by its length limits being different from most others or trying to sign up for a bugzilla account and finding your email is already registered, things like this are unnecessary overhead for everyone. -- imalone -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Self Introduction
Hi! I've been a happy Fedora user for some years, but now I'd like to give some contribution to the project. I'm going to package gnome-shell-extension-weather (URL: https://github.com/simon04/gnome-shell-extension-weather), an useful extension for Gnome Shell to display weather information, which I think deserves to be included in the official repositories. I've filed a review request in Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=751537. Please review the package and let me know if it's OK. Best regards, Odysseus -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20111105 changes
Compose started at Sat Nov 5 08:15:12 UTC 2011 Broken deps for x86_64 -- 4ti2-1.3.2-7.fc17.1.x86_64 requires libgmp.so.3()(64bit) 1:anerley-0.3.0-5.fc17.i686 requires libedataserver-1.2.so.15 1:anerley-0.3.0-5.fc17.i686 requires libcamel-1.2.so.29 1:anerley-0.3.0-5.fc17.x86_64 requires libedataserver-1.2.so.15()(64bit) 1:anerley-0.3.0-5.fc17.x86_64 requires libcamel-1.2.so.29()(64bit) comoonics-cdsl-py-0.2-18.noarch requires comoonics-base-py comoonics-cluster-py-0.1-24.noarch requires comoonics-base-py contextkit-0.5.15-2.fc15.i686 requires libcdb.so.1 contextkit-0.5.15-2.fc15.x86_64 requires libcdb.so.1()(64bit) couchdb-1.0.3-2.fc16.x86_64 requires libicuuc.so.46()(64bit) couchdb-1.0.3-2.fc16.x86_64 requires libicui18n.so.46()(64bit) couchdb-1.0.3-2.fc16.x86_64 requires libicudata.so.46()(64bit) curry-0.9.11-7.fc12.x86_64 requires libgmp.so.3()(64bit) dh-make-0.55-3.fc15.noarch requires debhelper dogtag-pki-9.0.0-8.fc17.noarch requires pki-console = 0:9.0.5 ease-0.4-9.fc17.i686 requires libpoppler.so.18 ease-0.4-9.fc17.i686 requires libclutter-gtk-0.10.so.0 ease-0.4-9.fc17.x86_64 requires libpoppler.so.18()(64bit) ease-0.4-9.fc17.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) ease-devel-0.4-9.fc17.i686 requires pkgconfig(clutter-gtk-0.10) ease-devel-0.4-9.fc17.x86_64 requires pkgconfig(clutter-gtk-0.10) emacs-spice-mode-1.2.25-5.fc15.noarch requires gwave evolution-couchdb-0.5.91-4.fc17.x86_64 requires libedataserver-1.2.so.15()(64bit) evolution-couchdb-0.5.91-4.fc17.x86_64 requires libedata-cal-1.2.so.13()(64bit) evolution-couchdb-0.5.91-4.fc17.x86_64 requires libedata-book-1.2.so.11()(64bit) evolution-couchdb-0.5.91-4.fc17.x86_64 requires libecal-1.2.so.10()(64bit) evolution-couchdb-0.5.91-4.fc17.x86_64 requires libcamel-provider-1.2.so.29()(64bit) evolution-couchdb-0.5.91-4.fc17.x86_64 requires libcamel-1.2.so.29()(64bit) fldigi-3.21.7-1.fc16.x86_64 requires libfltk_images.so.1.1()(64bit) fldigi-3.21.7-1.fc16.x86_64 requires libfltk.so.1.1()(64bit) gcc-python2-debug-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17 gcc-python2-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17 gcc-python3-debug-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17 gcc-python3-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17 1:geda-gattrib-1.6.2-2.fc16.x86_64 requires libgmp.so.3()(64bit) 1:geda-gnetlist-1.6.2-2.fc16.x86_64 requires libgmp.so.3()(64bit) 1:geda-gschem-1.6.2-2.fc16.x86_64 requires libgmp.so.3()(64bit) 1:geda-gsymcheck-1.6.2-2.fc16.x86_64 requires libgmp.so.3()(64bit) 1:geda-utils-1.6.2-2.fc16.x86_64 requires libgmp.so.3()(64bit) genius-1.0.12-2.fc15.x86_64 requires libgmp.so.3()(64bit) gnatcoll-2011-5.fc17.i686 requires libgmp.so.3 gnatcoll-2011-5.fc17.x86_64 requires libgmp.so.3()(64bit) gnome-genius-1.0.12-2.fc15.x86_64 requires libgmp.so.3()(64bit) gnome-phone-manager-0.66-6.fc17.x86_64 requires libedataserver-1.2.so.15()(64bit) gnome-phone-manager-0.66-6.fc17.x86_64 requires libcamel-1.2.so.29()(64bit) gnome-phone-manager-telepathy-0.66-6.fc17.x86_64 requires libedataserver-1.2.so.15()(64bit) gnome-phone-manager-telepathy-0.66-6.fc17.x86_64 requires libcamel-1.2.so.29()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotdconduit.so.3()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotdcm.so.4()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotd.so.5()(64bit) gphpedit-0.9.95-0.2.20090209snap.fc15.x86_64 requires libgtkhtml-2.so.0()(64bit) gpx-viewer-0.2.0-3.fc14.x86_64 requires libgdl-1.so.3()(64bit) gpx-viewer-0.2.0-3.fc14.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) gpx-viewer-0.2.0-3.fc14.x86_64 requires libchamplain-gtk-0.6.so.0()(64bit) gpx-viewer-0.2.0-3.fc14.x86_64 requires libchamplain-0.6.so.0()(64bit) gscribble-0.1.2-1.fc16.noarch requires gnome-python2-gtkhtml2 gstreamer-java-swt-1.5-1.fc16.x86_64 requires libswt3-gtk2 gummi-0.5.8-5.fc17.x86_64 requires libpoppler.so.18()(64bit) hosts3d-1.13-2.fc15.x86_64 requires libglfw.so.2.6()(64bit) hosts3d-sampler-1.13-2.fc15.x86_64 requires libglfw.so.2.6()(64bit) inkscape-0.48.1-9.fc17.x86_64 requires libpoppler.so.18()(64bit) inkscape-view-0.48.1-9.fc17.x86_64 requires libpoppler.so.18()(64bit) intellij-idea-9.0.1.94.399-12.fc15.x86_64 requires commons-collections kde-partitionmanager-1.0.3-2.fc15.x86_64 requires libparted.so.0()(64bit) 1:libgeda-1.6.2-2.fc16.i686 requires libgmp.so.3
Re: F17 heads up: gnome-shell for everyone!
w at googlemail.com writes: Yet look at all the happy users of default Gnome 3! I am one of them and I went directly from the tilling-WM Xmonad to gnome 3! So you can't say it's only for absolute noobs :). I installed it and it took about a week to get used to it so that I stopped thinking why the heck did they do it but instead started to understand the new Concepts. Today after about a Year of usage I have to say that its the best user interface that I ever used so far! The only negative points that I still don't get is the removal of the power of button (without config to change it). But yes there is an extension to add it again! So just because the rants are much more visible don't think it is the majority! ;) Please. What would you think of the system that when you click on FF starts FF, Evo and Gimp? I think you would say the system is broken. Right now, if I want to start an app, the shell gives me zoom out, search, expose, workspaces, dash and apps, followed by zoom in. WTF? Seriously? I am glad that you can take a lot of pain, but when things don't make sense, they don't make sense. No rant - just facts. -- Bojan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 heads up: gnome-shell for everyone!
On Sat, 2011-11-05 at 13:40 +, Bojan Smojver wrote: w at googlemail.com writes: Yet look at all the happy users of default Gnome 3! I am one of them [... snip ...] Please. What would you think of the system that when you click on FF starts FF, Evo and Gimp? I think you would say the system is broken. Right now, if I want to start an app, the shell gives me zoom out, search, expose, workspaces, dash and apps, followed by zoom in. WTF? Seriously? Right now, if I want to start an app, I just hit alt+f2, type the first few letters, hit tab and then enter. No zoom, no search, no expose, no workspaces, no dash. Just see it that way: you have one powerful interface to do advanced stuff (reorganizing windows, editing your favorites, searching,...) and a few simple keyboard shortcuts to do those same actions faster: - alt+f2 to run an app - ctrl+alt+arrow up/down to change workspace Etc... Nothing broken here. Just convenience, efficiency and adaptation to my workflows, whether I'm trying to be productive or just relaxing. I am glad that you can take a lot of pain, He wrote he was happy with Gnome 3, which doesn't tell me he is capable of taking a lot of pain, rather that he is enjoying this environment. And so am I. In fact, I'm taking a lot of pain when I have to go back to Gnome 2, which I used to love before I moved to Gnome 3. It's obvious that Gnome 3 doesn't work for you. Just use something else then, no one is forcing you to « take that pain ». At least two alternatives have been suggested already in this thread, so pick the one that works for you, and be happy with it, while others are happy with something else. -- Mathieu -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 heads up: gnome-shell for everyone!
Dne 5.11.2011 00:39, Ian Malone napsal(a): Is there any point in me reporting any bug in Fedora bugzilla ever then? Of course, there are plenty of bugs caused by our packaging or moments when one programs stomps on the other one's toes. See https://bugzilla.redhat.com/page.cgi?id=fields.html#upstream: “We only keep bug open on redhat.com to track our immediate short-term TODO items, or issues with our patches/packaging, or because the upstream package in question has poor bug tracking.” Matěj -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Package picolisp
Hi Alex, On Fri, Nov 4, 2011 at 10:26 PM, Alexander Burger a...@software-lab.de wrote: Hi all, I have a question to package maintainers. I'm the upstream developer of PicoLisp, and would like to see it included in the Fedora wishlist. Currently, PicoLisp is available in OpenWRT and the Debian family of distributions. Is anybody interested to maintain it as a package in Fedora? If so, I'm willing to assist. I would suggest the same layout as in Debian. I'm willing to package PicoLisp. Any assistance is highly appreciated. Cheers, - Alex -- Alexander Burger Software Lab. / 7fach GmbH Bahnhofstr. 24a, D-86462 Langweid http://twitter.com/Regenaxer a...@software-lab.de +49 8230 5060 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Best Regards, Kalpa Pathum Welivitigoda http://about.me/callkalpa -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Review(s) swap - sugar activities
Hello, Folloing are few sugar activities that I have packaged. They need to be reviewed. Anyone interested in reviewing them all, some or one? https://bugzilla.redhat.com/show_bug.cgi?id=741494 https://bugzilla.redhat.com/show_bug.cgi?id=744864 https://bugzilla.redhat.com/show_bug.cgi?id=749812 https://bugzilla.redhat.com/show_bug.cgi?id=739263 -- Best Regards, Kalpa Pathum Welivitigoda http://fedoraproject.org/wiki/User:Callkalpa http://about.me/callkalpa -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
The link to the review request in the first message is wrong. Here's the correct one: https://bugzilla.redhat.com/show_bug.cgi?id=751537 Waiting anxiously for your reviews... ;-) 2011/11/5 Mattia Meneguzzo hal8...@hotmail.it Hi! I've been a happy Fedora user for some years, but now I'd like to give some contribution to the project. I'm going to package *gnome-shell-extension-weather* (URL: https://github.com/simon04/gnome-shell-extension-weather)https://github.com/simon04/gnome-shell-extension-weather, an useful extension for Gnome Shell to display weather information, which I think deserves to be included in the official repositories. I've filed a review request in Bugzilla: https://bugzilla.redhat.com/** show_bug.cgi?id=751537https://bugzilla.redhat.com/show_bug.cgi?id=751537. Please review the package and let me know if it's OK. Best regards, Odysseus -- 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: unsure for wich component file bugreport
Am 04.11.2011 18:17, schrieb Michal Schmidt: On 11/04/2011 06:00 PM, Reindl Harald wrote: well, everytime i come in contact with anything from apple i could throw something out of the window beginning with the systemctl ACTION service instead systemctl SERVICE action while i laughed over years about apples order of this in their systemadmin and got this now on linux too You can keep using service $SERVICE $action in the meantime this seems to work really on my first F15 install apache did not start and the wrapper said always OK, maybe we can drop the wrapper-line and get bash-autocompletion for systemd-units and /sbin/service to make it as useable as before my intention for this paragraph was to make clear that i do not like things made by apple for users who are not really interested in computers flooding linux over the long and results in that peopole who HATE apple systems and decided to use linux because they do not like windows too are getting frustrated more and more signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: reporting bugs
Am 05.11.2011 01:50, schrieb Orion Poplawski: On 11/04/2011 05:39 PM, Ian Malone wrote: On 4 November 2011 17:23, Kevin Koflerkevin.kof...@chello.at wrote: Ian Malone wrote: If I filed every bug in the distro in upstream I'd have a dozen different bugzilla accounts by now. So what? Maintainers are not messengers, they have other work to do than forwarding the bugs you're too lazy to file directly at the right place. Is there any point in me reporting any bug in Fedora bugzilla ever then? yes - because most maintainers are having bugzilla-accounts upstream and reading the uptream-mailing-lists and are much more cooperative as the KDE SIG, especially Kevin Kofler if you than report a bundle of new introduced bugs upstream you are told in the case of KDE yous hould file for every piece a seperate bugreport guys this is not the way you can act with users treat them report exactly where and how you like it, a few peopole will do, most will never again report any bug and stop testing packages and later if there are too few testers maintainers are whining why? signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Heads up: libpng bumped to 1.5.x in rawhide
The list of packages that need to be rebuilt is attached. I'm not too sure about ordering dependencies, but I do know that gd and libsexy need to be rebuilt before some of the others. Some of these packages will require source code changes. See yesterday's discussion for hints about where to find patches. (Sorry for not being more verbose, but I've got to leave shortly. If you need help, ask me off-list.) regards, tom lane (orphan) amide (orphan) assogiate (orphan) emerald (orphan) gconf-cleaner (orphan) geda-gattrib (orphan) geda-gnetlist (orphan) geda-gschem (orphan) geda-gsymcheck (orphan) geda-utils (orphan) giggle (orphan) gpx-viewer (orphan) grfcodec (orphan) libgeda (orphan) python-gpod (orphan) slim (orphan) xfce4-dict-plugin (orphan) xfce4-screenshooter-plugin abo java-gnome abompard grisbi adalloz pan adamwill bamf adamwill libindicator adrian bwbar adrian fbida adrian gmpc adrian grip adrian sopwith affix cssed agoode gkrellm-weather agoode nip2 agoode vips ajax wayland alexlan mapnik als fpm2 ankursinha aeskulap ankursinha xmedcon athimm nx athimm synaptic athimm vtk avesh NetworkManager-openswan awjb WindowMaker awjb airsnort awjb aterm awjb dillo awjb dosbox awjb fbdesk awjb gimmix awjb multisync awjb perl-Tk awjb qiv awjb rxvt-unicode awjb synce-software-manager awjb synce-trayicon balajig8 thunarx-python behdad libgnomeprintui22 behdad vte belegdol gnome-chemistry-utils bellet FlightGear-Atlas berrange autobuild-applet berrange entangle berrange gtk-vnc berrange virt-viewer bjohnson goocanvas bjohnson pygoocanvas bogado puzzles bogado raw-thumbnailer bouska gtkperf bpepple nautilus-image-converter bpepple telepathy-stream-engine bpostle enblend bpostle hugin bpostle libpano12 bpostle libpano13 bpostle vigra brouhaha free42 bruno gdk-pixbuf bruno ggz-gtk-client bruno gnubik bruno greyhounds bruno lordsawar bruno sirius bsjones guitarix bsjones gx_head bsjones jamin bsjones lv2-ll-plugins bsjones phat buc dvdisaster buc gnome-translate buc gtk-gnutella buc mail-notification buc xawtv cagney libgconf-java cagney libglade-java cagney libgnome-java cagney libgtk-java cagney libvte-java caillon drwright caillon gnome-hearts caillon xchat candyz gcin caolanm libwmf caolanm planner carllibpst ghemical cassmodiah fife cassmodiah florence cassmodiah gnaughty cassmodiah surf cheese teg chitlesh fped chitlesh gerbv chitlesh kshutdown chitlesh linsmith chitlesh pcb chitlesh pikloops chkr f-spot chkr gnome-do chkr gthumb chkr nall company cairo company gstreamer-plugins-bad-free company gstreamer-plugins-good corsepiu k3d cosimoc the-board cweyl perl-Gnome2 cweyl perl-Gnome2-Canvas cweyl perl-Gnome2-Print cweyl perl-Gtk2-GladeXML cweyl perl-Gtk2-Notify cweyl perl-Gtk2-Sexy cweyl perl-Gtk2-Spell cweyl perl-Gtk2-TrayIcon cwickert beldi cwickert fbpanel cwickert glista cwickert gnome-applet-alarm-clock cwickert gpicview cwickert gpp cwickert grsync cwickert gtkhash cwickert gtrayicon cwickert gwget cwickert gxmessage cwickert ignuit cwickert leafpad cwickert libxfce4ui cwickert lilyterm cwickert lostirc cwickert lxappearance cwickert lxdm cwickert lxinput cwickert lxlauncher cwickert lxmusic cwickert lxpanel cwickert lxpolkit cwickert lxrandr cwickert lxsession cwickert lxsession-edit cwickert lxshortcut cwickert lxtask cwickert lxterminal cwickert mypaint cwickert osmo cwickert parcellite cwickert parole cwickert pnmixer cwickert regexxer cwickert remmina cwickert ristretto cwickert sakura cwickert termit cwickert thunar-media-tags-plugin cwickert thunar-vfs cwickert tumbler cwickert viewnior cwickert volumeicon cwickert xarchiver cwickert xfbib cwickert xfburn cwickert xfce4-battery-plugin cwickert xfce4-cellmodem-plugin cwickert xfce4-clipman-plugin cwickert xfce4-cpugraph-plugin cwickert xfce4-datetime-plugin cwickert xfce4-dict cwickert xfce4-diskperf-plugin cwickert xfce4-eyes-plugin cwickert xfce4-fsguard-plugin cwickert xfce4-genmon-plugin cwickert xfce4-mailwatch-plugin cwickert xfce4-modemlights-plugin cwickert xfce4-mount-plugin cwickert xfce4-mpc-plugin cwickert xfce4-netload-plugin cwickert xfce4-notes-plugin cwickert xfce4-notifyd cwickert xfce4-places-plugin cwickert xfce4-power-manager cwickert xfce4-quicklauncher-plugin cwickert xfce4-radio-plugin cwickert xfce4-screenshooter cwickert xfce4-sensors-plugin cwickert xfce4-smartbookmark-plugin cwickert xfce4-systemload-plugin cwickert xfce4-taskmanager cwickert xfce4-timer-plugin cwickert xfce4-verve-plugin cwickert xfce4-volumed cwickert xfce4-wavelan-plugin cwickert xfce4-weather-plugin cwickert xfce4-websearch-plugin cwickert xfce4-xfswitch-plugin cwickert xfce4-xkb-plugin cwickert xfmpc cwickert xpad davidcornette lv2-EQ10Q-plugins davidcornette lv2-invada-plugins davidz dasher davidz
Re: [Test-Announce] Fedora 16 Final Release Declared GOLD!
On Sat, Nov 5, 2011 at 5:22 AM, Adam Williamson awill...@redhat.com wrote: There are various 'hot topics' exposed during the F16 cycle that we'll likely expand the matrix to cover better in F17 - bootloader location issues, EFI issues, USB installer issues (when we first drew up the installation tests, using USB sticks for installation was very rare, and I think you couldn't actually write non-live images to USB at all), and Last night I used livecd-iso-to-disk to write the rc5 64 bit DVD install iso to an 8 GiB usbkey - which I am planning to test this evening to install to a desktop i.e. the usbkey will be my install (source) medium. I have used this method for several years - and not had a failure yet - I will report if there are any problems when I do this install for f16 -- mike c -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Package picolisp
Hello All, I am not a techie or a geek :) But I would like to learn about that(have a little experience though :) ), Kalpa and Alex, you guys like to take me to the boat? On Sat, Nov 5, 2011 at 9:07 PM, Kalpa Welivitigoda callka...@gmail.comwrote: Hi Alex, On Fri, Nov 4, 2011 at 10:26 PM, Alexander Burger a...@software-lab.de wrote: Hi all, I have a question to package maintainers. I'm the upstream developer of PicoLisp, and would like to see it included in the Fedora wishlist. Currently, PicoLisp is available in OpenWRT and the Debian family of distributions. Is anybody interested to maintain it as a package in Fedora? If so, I'm willing to assist. I would suggest the same layout as in Debian. I'm willing to package PicoLisp. Any assistance is highly appreciated. Cheers, - Alex -- Alexander Burger Software Lab. / 7fach GmbH Bahnhofstr. 24a, D-86462 Langweid http://twitter.com/Regenaxer a...@software-lab.de +49 8230 5060 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Best Regards, Kalpa Pathum Welivitigoda http://about.me/callkalpa -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Regards, *Buddhike Chandradeepa Kurera(bckurera)* Fedora Ambassador Sri Lanka Event Liaison - Design Team *Email*: bckur...@fedoraproject.org | *IRC*: bckurera * * -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
This is my first time as a contributor to run into this. Do I simply need to increment by release by 1 (or .1?) and build? Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Package picolisp
On Sat, Nov 5, 2011 at 10:49 PM, Buddhika Kurera bckur...@fedoraproject.org wrote: Hello All, I am not a techie or a geek :) But I would like to learn about that(have a little experience though :) ), Kalpa and Alex, you guys like to take me to the boat? yeah sure, http://fedoraproject.org/wiki/Category:Package_Maintainers is a good point to start On Sat, Nov 5, 2011 at 9:07 PM, Kalpa Welivitigoda callka...@gmail.com wrote: Hi Alex, On Fri, Nov 4, 2011 at 10:26 PM, Alexander Burger a...@software-lab.de wrote: Hi all, I have a question to package maintainers. I'm the upstream developer of PicoLisp, and would like to see it included in the Fedora wishlist. Currently, PicoLisp is available in OpenWRT and the Debian family of distributions. Is anybody interested to maintain it as a package in Fedora? If so, I'm willing to assist. I would suggest the same layout as in Debian. I'm willing to package PicoLisp. Any assistance is highly appreciated. Cheers, - Alex -- Alexander Burger Software Lab. / 7fach GmbH Bahnhofstr. 24a, D-86462 Langweid http://twitter.com/Regenaxer a...@software-lab.de +49 8230 5060 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Best Regards, Kalpa Pathum Welivitigoda http://about.me/callkalpa -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Regards, Buddhike Chandradeepa Kurera(bckurera) Fedora Ambassador Sri Lanka Event Liaison - Design Team Email: bckur...@fedoraproject.org | IRC: bckurera -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Best Regards, Kalpa Pathum Welivitigoda http://fedoraproject.org/wiki/User:Callkalpa http://about.me/callkalpa -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
If it is a new version from upstream then the release will be 1 but if you are updating the SPEC file you would increment the release number. On Sat, Nov 5, 2011 at 12:20 PM, Richard Shaw hobbes1...@gmail.com wrote: This is my first time as a contributor to run into this. Do I simply need to increment by release by 1 (or .1?) and build? Thanks, Richard -- 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: Package picolisp
On Sat, Nov 5, 2011 at 10:56 PM, Buddhika Kurera bckur...@fedoraproject.org wrote: Yes I have started from that and followed a classroom from Rahul too. I think I am good to start, so join me with you :) yeah proceed according to the guideline. Will do it for F17 hureeey :) :) Alex and Kalpa this is going to be my first real package work. Congrats bckurera! congrats! On Sat, Nov 5, 2011 at 10:52 PM, Kalpa Pathum Welivitigoda callka...@fedoraproject.org wrote: On Sat, Nov 5, 2011 at 10:49 PM, Buddhika Kurera bckur...@fedoraproject.org wrote: Hello All, I am not a techie or a geek :) But I would like to learn about that(have a little experience though :) ), Kalpa and Alex, you guys like to take me to the boat? yeah sure, http://fedoraproject.org/wiki/Category:Package_Maintainers is a good point to start On Sat, Nov 5, 2011 at 9:07 PM, Kalpa Welivitigoda callka...@gmail.com wrote: Hi Alex, On Fri, Nov 4, 2011 at 10:26 PM, Alexander Burger a...@software-lab.de wrote: Hi all, I have a question to package maintainers. I'm the upstream developer of PicoLisp, and would like to see it included in the Fedora wishlist. Currently, PicoLisp is available in OpenWRT and the Debian family of distributions. Is anybody interested to maintain it as a package in Fedora? If so, I'm willing to assist. I would suggest the same layout as in Debian. I'm willing to package PicoLisp. Any assistance is highly appreciated. Cheers, - Alex -- Alexander Burger Software Lab. / 7fach GmbH Bahnhofstr. 24a, D-86462 Langweid http://twitter.com/Regenaxer a...@software-lab.de +49 8230 5060 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Best Regards, Kalpa Pathum Welivitigoda http://about.me/callkalpa -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Regards, Buddhike Chandradeepa Kurera(bckurera) Fedora Ambassador Sri Lanka Event Liaison - Design Team Email: bckur...@fedoraproject.org | IRC: bckurera -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Best Regards, Kalpa Pathum Welivitigoda http://fedoraproject.org/wiki/User:Callkalpa http://about.me/callkalpa -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Regards, Buddhike Chandradeepa Kurera(bckurera) Fedora Ambassador Sri Lanka Event Liaison - Design Team Email: bckur...@fedoraproject.org | IRC: bckurera -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Best Regards, Kalpa Pathum Welivitigoda http://fedoraproject.org/wiki/User:Callkalpa http://about.me/callkalpa -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
On 11/05/2011 07:02 PM, Tom Lane wrote: The list of packages that need to be rebuilt is attached. I suggest maintainers take this opportunity to review whether all these packages really need to be linked against libpng - I'm positive that the list contains a lot of packages that don't. -Wl,--as-needed in LDFLAGS (in addition to RPM_LD_FLAGS) is one easy way that can be applied in many cases to get rid of unnecessary linkage bloat. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Self Introduction
Having been a Fedora (and RedHat before that) user for more years then I care to think about I have decided that it must be high time for me to contribute my first package. So I have opened a review request for libgxps with the aim of getting support for XPS files into evince. The review request is here: https://bugzilla.redhat.com/show_bug.cgi?id=751568 Now all I need is a sponsor and some reviews... Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: xfce-weather-plugin stopped working
Johannes Lips wrote: http://developer.yahoo.com/weather/ is this perhaps an alternative? Perhaps we could collect weather services and then choose the service which makes it easiest to port the plugin. The KDE Plasma weather widget, which prides itself on only using sources whose usage in this context was allowed by the data provider, supports the following sources: * BBC (data from the UK Meteorological Office, international) * Environment Canada (Canada only) * NOAA (international, but no forecasts) * wetter.com (international, note that this is NOT weather.com) (and the Debian weather which reports how broken Debian unstable currently is using the weather metaphor, LOL, I guess we could use something like that for Rawhide as well ;-) ). If you want to comply with the ToS, some sources may have some specific requirements for use of their service. In particular, the BBC wants itself and the UK MET Office to be credited with a link, which is why that credit link below the forecasts got added to the widget. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
Ville Skyttä wrote: I suggest maintainers take this opportunity to review whether all these packages really need to be linked against libpng - I'm positive that the list contains a lot of packages that don't. -Wl,--as-needed in LDFLAGS (in addition to RPM_LD_FLAGS) is one easy way that can be applied in many cases to get rid of unnecessary linkage bloat. Why is this not the default in Fedora? Mandriva has been using that by default for ages, and it shouldn't be any more invasive than the -Wl,--no-add-needed (note: add != as) change done in Fedora 13. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: reporting bugs
Reindl Harald wrote: yes - because most maintainers are having bugzilla-accounts upstream and reading the uptream-mailing-lists and are much more cooperative as the KDE SIG, especially Kevin Kofler Yes, we have Bugzilla accounts upstream. But as I explained, upstream wants to talk to the actual person experiencing the bug, not to a middleman. Plus, we get many bug reports, it'd be very time-consuming for us to forward them all upstream, whereas you as a user (hopefully) have much fewer bug reports to deal with. It's not our job to play stille Post for you (a game which necessarily loses information with every middleman you introduce). if you than report a bundle of new introduced bugs upstream you are told in the case of KDE yous hould file for every piece a seperate bugreport Of course! It is just plain impossible to work with a bug report which conflates several, totally different issues, which need to be tracked and fixed separately. Upstream will also require one bug report per issue. It's part of the absolute basics of bug reporting. We just cannot track what's fixed and what's still open if we have multiple issues in one report, because a report can only be either open or closed. guys this is not the way you can act with users treat them report exactly where and how you like it, a few peopole will do, most will never again report any bug and stop testing packages and later if there are too few testers maintainers are whining why? Thankfully, not all users are as lazy and arrogant as you. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
Richard Shaw hobbes1...@gmail.com writes: This is my first time as a contributor to run into this. Do I simply need to increment by release by 1 (or .1?) and build? If no source-code changes are needed, then yes, it's sufficient to increment the release number (either way that suits you) and rebuild in rawhide. I assume you're thinking of OpenImageIO? [ checks results of test runs... ] You will need a source-code patch for that one, because it uses the symbol Z_BEST_COMPRESSION, which is exported by zlib.h, which is no longer automatically included by png.h. So you'll need to add #include zlib.h to whichever file(s) need that. It might be that there are further changes needed --- the error on that symbol was as far as my test build got. Once you've got it working, you should pester your upstream to include the changes, since libpng 1.5 is certainly something they're going to have to deal with. regards, tom lane -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: reporting bugs
Am 05.11.2011 20:18, schrieb Kevin Kofler: Reindl Harald wrote: yes - because most maintainers are having bugzilla-accounts upstream and reading the uptream-mailing-lists and are much more cooperative as the KDE SIG, especially Kevin Kofler Yes, we have Bugzilla accounts upstream. But as I explained, upstream wants to talk to the actual person experiencing the bug, not to a middleman. Plus, we get many bug reports, it'd be very time-consuming for us to forward them all upstream, whereas you as a user (hopefully) have much fewer bug reports to deal with. It's not our job to play stille Post for you (a game which necessarily loses information with every middleman you introduce). most maintainers see this different and only the fact that fedora-packages are mostly patched makes it not useful throw all upstream first the sense of a distribution for users is have a centralized source for packages and problems, if your standard-answer is report upstream you are damaging the benefits of a distribution for users i have filled MANY bugreports in the last years and really often some hours later there was a new version on koji, maintainer aksed to try this, confirmed as works now and the maintainer submitted his patch upstream and included it as long iht was not fixed upstream in the fedora-packages - this way users start to love fedora, the maintainers and all peopole from users, maintainers to upstream developers are happy - your way of handling bugreports is the exactly oppiste of this if you than report a bundle of new introduced bugs upstream you are told in the case of KDE yous hould file for every piece a seperate bugreport https://bugs.kde.org/show_bug.cgi?id=236025 is the best example that this is not useful - in this case some random guy decided to replace a whole io-subsytem from scratch without any knowledge what he is doing for POSSIBLE get better performance sometimes later which is not true in exactly this case because the limit is the network and not the kio-slave after such a useless, not needed replacement force users open a bunch of bugreports instead revert the whole changes and release them if they are finished and useable is the wrong way anyways: fact is that if you punsih users how to report bugs in such ways the result will be for MANY of them stop reporting bugs signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
On Sat, Nov 5, 2011 at 2:34 PM, Tom Lane t...@redhat.com wrote: Richard Shaw hobbes1...@gmail.com writes: This is my first time as a contributor to run into this. Do I simply need to increment by release by 1 (or .1?) and build? If no source-code changes are needed, then yes, it's sufficient to increment the release number (either way that suits you) and rebuild in rawhide. I assume you're thinking of OpenImageIO? [ checks results of test runs... ] You will need a source-code patch for that one, because it uses the symbol Z_BEST_COMPRESSION, which is exported by zlib.h, which is no longer automatically included by png.h. So you'll need to add #include zlib.h to whichever file(s) need that. It might be that there are further changes needed --- the error on that symbol was as far as my test build got. Yup, I figured that out! I'm still not a C programmer but my hacker skills are improving. I ended up grep'ing through /usr/include for Z_BEST_COMPRESSION and found that zlib.h had what I needed. I checked upstream and the master branch already has the fix but the (updated) 0.10.3 still does not. I'm doing a local mock build to make sure my patch works. Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 16 Final Release Declared GOLD!
On Sat, 2011-11-05 at 17:04 +, mike cloaked wrote: On Sat, Nov 5, 2011 at 5:22 AM, Adam Williamson awill...@redhat.com wrote: There are various 'hot topics' exposed during the F16 cycle that we'll likely expand the matrix to cover better in F17 - bootloader location issues, EFI issues, USB installer issues (when we first drew up the installation tests, using USB sticks for installation was very rare, and I think you couldn't actually write non-live images to USB at all), and Last night I used livecd-iso-to-disk to write the rc5 64 bit DVD install iso to an 8 GiB usbkey - which I am planning to test this evening to install to a desktop i.e. the usbkey will be my install (source) medium. I have used this method for several years - and not had a failure yet - I will report if there are any problems when I do this install for f16 Ah, that's far too simple. ;) See, the problem we solved in RC5 only came when you wrote the installer to USB with l-i-t-d *and then used it to upgrade an F15 system*. The problem was that anaconda doesn't filter out the USB key it's installing from as a potential bootloader installation target, and it orders the preferred bootloader target disks in the order they're presented by the BIOS - and when you boot from a USB stick, the BIOS presents it as the first disk. So when you run the traditional installer from a USB stick, the USB stick starts out as the preferred bootloader target disk. Why does this only affect upgrades, and why didn't we catch it before? Well, on fresh installs, you get the 'cleardiskssel' screen, which is the one where you put 'install target devices' on the right and 'data storage devices' (i.e. leave these alone!) on the left, and pick one of the 'install target devices' to be the bootloader device with a radio button. On upgrades, you _don't_ get that screen. So on a fresh install it doesn't really matter which device anaconda would have chosen as the bootloader target, as in practice you get to make the decision anyway, and because of various other factors I won't go into here, that screen doesn't 'default' to anything - it doesn't default to nominating the USB stick as the bootloader target device. Why didn't we catch it before? Before F16, when you upgraded, the default action was not to actually write a new bootloader. The default action was just to update the existing bootloader *configuration file* in the Fedora installation being upgraded. Since this was almost always what you wanted to do, very few people switched to the 'install new bootloader' option when upgrading, which makes it much less likely we'd catch this bug. And _finally_, there is another dialog you _do_ see when you upgrade, which essentially is designed to let you choose whether to put the bootloader on the MBR or on the first partition of the target disk. It has a drop-down labelled 'BIOS boot order' which is intended to let you correct the ordering of the disks if anaconda somehow read it wrong - what it really does is change the (hd0), (hd1) etc etc order that the grub config file uses. But prior to F16, it would also change the target disk for the bootloader install - so if anaconda had decided the USB stick was the target disk, you could fiddle the BIOS boot order in that dropdown and use that to make it pick the hard disk instead. So there used to be a way to work around the problem. Put all that together, and you get an F16 blocker. But it's a hell of a lot of moving parts...and that's one of the problems anaconda team and QA face all the time. The pending F17 anaconda UI re-design isn't just intended to make anaconda look shinier and be more user-friendly; it's also intended to rethink a lot of these paths which have grown complex and messy over time and are just badly designed. You may have noticed in the above that there are two overlapping dialogs about bootloader location, and you might get one or the other or both or neither depending on what installation path you choose exactly, which is kind of silly. That's one of the things the UI rewrite will be able to improve, and hence make everyone's job easier, we hope... -- 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
Re: Heads up: libpng bumped to 1.5.x in rawhide
On Sat, 05 Nov 2011 20:12:28 +0200, VS (Ville) wrote: On 11/05/2011 07:02 PM, Tom Lane wrote: The list of packages that need to be rebuilt is attached. I suggest maintainers take this opportunity to review whether all these packages really need to be linked against libpng - I'm positive that the list contains a lot of packages that don't. Well-spotted, but how to fix it? Lots of executables end up linked with libpng12 due to other libs (cairo, gdk-pixbuf2) being linked with it. Neither -lpng12 or -lpng is added explicitly. -Wl,--as-needed in LDFLAGS (in addition to RPM_LD_FLAGS) is one easy way that can be applied in many cases to get rid of unnecessary linkage bloat. Last time that has come up (long ago!) it didn't work for me. Still doesn't. Example package: geeqie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 16 Final Release Declared GOLD!
On Sat, Nov 5, 2011 at 8:20 PM, Adam Williamson awill...@redhat.com wrote: See, the problem we solved in RC5 only came when you wrote the installer to USB with l-i-t-d *and then used it to upgrade an F15 system*. The problem was that anaconda doesn't filter out the USB key it's installing from as a potential bootloader installation target, and it orders the preferred bootloader target disks in the order they're presented by the BIOS - and when you boot from a USB stick, the BIOS presents it as the Wow - OK! I decided to try another tack this evening on my test machine which was running F15 - I placed the F16 install iso on a partition which would not be touched - and loop mounted it - then pulled vmlinuz and initrd.img into /boot, and made a new stanza in /boot/grub/grub.conf (another technique I have used for years). It booted into the installer just fine - but here is the catch/snag - instead of being able to point the install to using the iso on the unused partition it asks for a network location for the repos -but I could not get it to use the local iso! Maybe I am being dumb or is this something that can't be done with F16 installs? Now the install is off and running but of course will take a lot longer than using the local iso for the packages - but of course I have now formatted the root partition so I can't go back to the start point! Have I done something dumb here? Or have I missed something in getting an install to run off my HD? -- mike c -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 16 Final Release Declared GOLD!
On Sat, Nov 5, 2011 at 8:30 PM, mike cloaked mike.cloa...@gmail.com wrote: I decided to try another tack this evening on my test machine which was running F15 - I placed the F16 install iso on a partition which would not be touched - and loop mounted it - then pulled vmlinuz and initrd.img into /boot, and made a new stanza in /boot/grub/grub.conf (another technique I have used for years). It booted into the installer just fine - but here is the catch/snag - instead of being able to point the install to using the iso on the unused partition it asks for a network location for the repos -but I could not get it to use the local iso! Maybe I am being dumb or is this something that can't be done with F16 installs? Now the install is off and running but of course will take a lot longer than using the local iso for the packages - but of course I have now formatted the root partition so I can't go back to the start point! Have I done something dumb here? Or have I missed something in getting an install to run off my HD? Thinking about it I am now wondering if I should have added repo=hd:device to the grub stanza kernel line. -- mike c -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: reporting bugs
Ian Malone wrote: What would be nice would be the ability to forward bugs upstream from within bugzilla. Yes, definitely! But the problem is that getting it right is hard, and requires closer cooperation with upstream infrastructure than we currently have. (In particular, we'd like the bug to show up as reported by the original reporter in Fedora and/or with that original reporter CCed, without them having to register for an upstream account first.) Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 heads up: gnome-shell for everyone!
enaut wrote: I am one of them and I went directly from the tilling-WM Xmonad to gnome 3! So you can't say it's only for absolute noobs :). The fact that you were using a tiling WM first shows that you are much more willing to adapt to unconventional designs than most other users. I, for one, want my computer to work the way I learned and interiorized a computer works, any innovative interface destroys my automatisms and confuses me. I'm using Plasma Desktop with the Classic menu (not the default fancy Kickoff), only 1 virtual desktop and only the default activity. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: reporting bugs
On Sat, 05 Nov 2011 09:49:16 +0100, RH (Reindl) wrote: guys this is not the way you can act with users treat them report exactly where and how you like it, a few peopole will do, most will never again report any bug and stop testing packages and later if there are too few testers maintainers are whining why? If it's many users who are affected by the same bug, surely one of them can contribute a little bit and report the bug directly to the software developers. This is especially true for bugs the package maintainer cannot reproduce. Refusal to help with testing and bug-reporting will backfire eventually. It will be one of the users who will start whining about a pet peeve bug. Still, a user reporting a bug in Fedora bugzilla should get _some_ response rather sooner than later, even if it were a canned response or a fully automated one. Btw, with ABRT, many users just dump their report into bugzilla with only a few added words (if at all) and without out paying attention to NEEDINFO or questions asked by the package maintainer(s). -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: reporting bugs
Dne 5.11.2011 21:40, Kevin Kofler napsal(a): Ian Malone wrote: What would be nice would be the ability to forward bugs upstream from within bugzilla. Yes, definitely! But the problem is that getting it right is hard, and requires closer cooperation with upstream infrastructure than we currently have. (In particular, we'd like the bug to show up as reported by the original reporter in Fedora and/or with that original reporter CCed, without them having to register for an upstream account first.) Just to add I told you so http://article.gmane.org/gmane.linux.redhat.fedora.devel/79936 Unfortunately, bugzilla still doesn't support inter-site communication. List of the upstream (yes ;)) bugs concerning this could be provided upon the request. Also, I am quite sure, that a Perl hacker willing to help with their fixing would be warmly welcomed. Best, Matěj -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
Michael Schwendt wrote: Lots of executables end up linked with libpng12 due to other libs (cairo, gdk-pixbuf2) being linked with it. Neither -lpng12 or -lpng is added explicitly. Not due to them being LINKED with it, but due to them shipping .pc or .la files (probably .pc, since we normally don't ship .la files in Fedora) which add -lpng12 when you didn't ask for it. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 heads up: gnome-shell for everyone!
Mathieu Bridon bochecha at fedoraproject.org writes: Right now, if I want to start an app, I just hit alt+f2, type the first few letters, hit tab and then enter. No zoom, no search, no expose, no workspaces, no dash. Just see it that way: you have one powerful interface to do advanced stuff (reorganizing windows, editing your favorites, searching,...) and a few simple keyboard shortcuts to do those same actions faster: - alt+f2 to run an app - ctrl+alt+arrow up/down to change workspace Etc... Tried and true advice for the broken _graphical_ UI - just use keyboard shortcuts, type etc. Straight back to the 80s. Nothing broken here. If _nothing_ was broken, you wouldn't have to resort to shortcuts (which can, of course, be added to most UIs - this is not in question). It's obvious that Gnome 3 doesn't work for you. It does - in fallback mode. It's very nice, actually. I would like to continue using Gnome, otherwise I wouldn't discuss any of it here. -- Bojan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
On 11/05/2011 11:20 PM, Michael Schwendt wrote: On Sat, 05 Nov 2011 22:02:42 +0100, KK (Kevin) wrote: Lots of executables end up linked with libpng12 due to other libs (cairo, gdk-pixbuf2) being linked with it. Neither -lpng12 or -lpng is added explicitly. Not due to them being LINKED with it, but due to them shipping .pc or .la files (probably .pc, since we normally don't ship .la files in Fedora) which add -lpng12 when you didn't ask for it. No. If that were the case, -lpng12 would appear on the linker command-line. It doesn't. How are you checking whether your executable ended up linked with something? If with ldd, note that it's recursive. AFAIU for example eu-readelf -d /path/to/something | grep NEEDED shows a better picture which is also mirrored in package dependencies. Configuring geeqie with %configure --enable-lirc LDFLAGS=-Wl,--as-needed ...instead of plain %configure --enable-lirc in a F-15 mock test build I just did from the devel branch dropped the number of shared libs listed in the eu-readelf command above for /usr/bin/geeqie from 25 to 15, and libpng* no longer appears in the resulting package's dependencies. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Nomination period for Fedora Board, FESCo, and FAmSCo elections closes Nov. 5
On Fri, Nov 04, 2011 at 08:16:57 -0700, Robyn Bergeron rberg...@redhat.com wrote: Full information about the elections, including the elections schedule, and links to where one may nominate, can be seen here: https://fedoraproject.org/wiki/Elections This misses an important link. FESCO has their policy for elections at: https://fedoraproject.org/wiki/FESCo_election_policy One of the listed requirements is that nominees be members of the packager group. We currently have a FESCO nominee who participates in QA who does not qualify for FESCO if the information on that page is still accurate. This should probably get clarified before the election gets started. I think FESCO dates back before there was a formal QA group and it may make sense to modify the requirements for FESCO members in light of changes over the last 3 years. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
Le 23/07/2011 18:40, Olivier BONHOMME a écrit : Hello everybody, I am Olivier from France. I work now as a System/Network Architect in the Spatial domain especially in Satellite telecommunications. I work every day on Linux Platform especially Fedora / Redhat / CentOS platform doing software and hardware integration, architecture and packaging work. Moreover, I try to contribute to some projects like the SUDO French translation [1] and the Fusiondirectory project. [2] On this project, I maintain the public services and I am in charge of the RPM packaging. About that I have two Review requests opened about this project [3] [4] and it would be nice to participate to the integration in Fedora. Thanks for have read me. Regards, Olivier BONHOMME [1] - https://pootle.fusiondirectory.org/projects/sudo_debian/ [2] - http://www.fusiondirectory.org [3] - https://bugzilla.redhat.com/show_bug.cgi?id=701028 [4] - https://bugzilla.redhat.com/show_bug.cgi?id=704672 Hello, Our team just released the 1.0.2 version and we are still looking for a sponsor in order to integrate the Fedora and EPEL distribution. So if someone is interested, please see the updated request : https://bugzilla.redhat.com/show_bug.cgi?id=704672 Thanks Regards, Olivier BONHOMME -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
Michael Schwendt mschwe...@gmail.com writes: On Sun, 06 Nov 2011 00:03:28 +0200, VS (Ville) wrote: How are you checking whether your executable ended up linked with something? Admittedly, I trusted Tom Lane's list of affected packages, looked at ldd -u -r output and then examined the source. My list was just the result of repoquery --whatrequires. I don't claim to have inquired any more closely than that as to what depends on libpng. I did notice that a lot of them don't seem to have any BuildRequires for libpng --- but that doesn't mean it's not getting pulled in indirectly. regards, tom lane -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
On Sat, 05 Nov 2011 19:07:44 -0400, TL (Tom) wrote: On Sun, 06 Nov 2011 00:03:28 +0200, VS (Ville) wrote: How are you checking whether your executable ended up linked with something? Admittedly, I trusted Tom Lane's list of affected packages, looked at ldd -u -r output and then examined the source. My list was just the result of repoquery --whatrequires. I don't claim to have inquired any more closely than that as to what depends on libpng. I did notice that a lot of them don't seem to have any BuildRequires for libpng --- but that doesn't mean it's not getting pulled in indirectly. The last Rawhide build of geeqie also doesn't depend on libpng*. F-15 does, however, which might be where you've run repoquery. Never mind. ;) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
Michael Schwendt mschwe...@gmail.com writes: On Sat, 05 Nov 2011 19:07:44 -0400, TL (Tom) wrote: My list was just the result of repoquery --whatrequires. The last Rawhide build of geeqie also doesn't depend on libpng*. F-15 does, however, which might be where you've run repoquery. Hmm ... actually I did it on an F-14 box. My notes say I did repoquery --repoid=fedora-rawhide --whatrequires ... but I've had problems before with repoquery not doing what I thought it would. Can anyone elucidate on the proper incantation for this? regards, tom lane -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Nomination period for Fedora Board, FESCo, and FAmSCo elections closes Nov. 5
Sorry (about the lack of clarification, *and* for top-posting - on a sucky client) - I was going for brevity, and mistakenly thought that the policies/requirements for each election was on the main election page and/or each nomination page - and it's not, which should also be corrected. -Robyn - Original Message - From: Bruno Wolff III br...@wolff.to To: Robyn Bergeron rberg...@redhat.com Cc: t...@lists.fedoraproject.org, devel@lists.fedoraproject.org Sent: Saturday, November 5, 2011 3:29:38 PM Subject: Re: Nomination period for Fedora Board, FESCo, and FAmSCo elections closes Nov. 5 On Fri, Nov 04, 2011 at 08:16:57 -0700, Robyn Bergeron rberg...@redhat.com wrote: Full information about the elections, including the elections schedule, and links to where one may nominate, can be seen here: https://fedoraproject.org/wiki/Elections This misses an important link. FESCO has their policy for elections at: https://fedoraproject.org/wiki/FESCo_election_policy One of the listed requirements is that nominees be members of the packager group. We currently have a FESCO nominee who participates in QA who does not qualify for FESCO if the information on that page is still accurate. This should probably get clarified before the election gets started. I think FESCO dates back before there was a formal QA group and it may make sense to modify the requirements for FESCO members in light of changes over the last 3 years. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 heads up: gnome-shell for everyone!
Kevin Kofler kevin.kofler at chello.at writes: I, for one, want my computer to work the way I learned and interiorized a computer works, any innovative interface destroys my automatisms and confuses me. I'm using Plasma Desktop with the Classic menu (not the default fancy Kickoff), only 1 virtual desktop and only the default activity. I'm not actually arguing against certain features of gnome-shell based on what I'm used to. For instance, I am not disputing that having an apps menu that can be searched and is both flat and nested is useful. I'm not disputing that having one panel is better than two, because it takes less precious desktop space. I'm not disputing that having search in general is useful etc. What I'm disputing is usefulness of the overview. It brings nothing to the table - for anyone. Rationalisations for it as as funny as rationalisations against the taskbar. Usually we are told that users would be too confused by seeing workspaces/taskbar on the panel or some such. Who are these poor souls that get confused by having more visibility that also gives them the ability to directly navigate to where they want to go, while taking no more space from the desktop? With the taskbar, we've been told that it's not a true representation of running apps. The next piece of advice is usually that dash can also be used to switch tasks. I guess the dash is then a true representation of running apps. Probably because it's vertical. ;-) With overview, shell introduces unnecessary view switches (at least two for each other task), UI elements user never asked for etc. Just makes things less visible, more cumbersome and slower to use. Not to mention annoying. Just think of doing a cut and paste from one workspace to the next using shell and overview using nothing but GUI. I reckon you'd get a vertigo. :-) -- Bojan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: xfce-weather-plugin stopped working
Once upon a time, Kevin Kofler kevin.kof...@chello.at said: The KDE Plasma weather widget, which prides itself on only using sources whose usage in this context was allowed by the data provider To be fair, I believe that the usage of weather.com by a number of open source projects was within the policies. However, policies change, and sometimes on relatively short notice. I think weather.com was the default for a number of projects, and that probably was costing The Weather Channel money (that didn't give them anything in return). -- Chris Adams cmad...@hiwaay.net 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
Re: Heads up: libpng bumped to 1.5.x in rawhide
Once upon a time, Ville Skyttä ville.sky...@iki.fi said: How are you checking whether your executable ended up linked with something? If with ldd, note that it's recursive. AFAIU for example eu-readelf -d /path/to/something | grep NEEDED shows a better picture which is also mirrored in package dependencies. Hmm, I didn't know that. Which does RPM use when generating dependencies? It would appear that it is is using ldd; should that be changed? -- Chris Adams cmad...@hiwaay.net 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
Re: Nomination period for Fedora Board, FESCo, and FAmSCo elections closes Nov. 5
On Sat, Nov 05, 2011 at 05:29:38PM -0500, Bruno Wolff III wrote: On Fri, Nov 04, 2011 at 08:16:57 -0700, Robyn Bergeron rberg...@redhat.com wrote: Full information about the elections, including the elections schedule, and links to where one may nominate, can be seen here: https://fedoraproject.org/wiki/Elections This misses an important link. FESCO has their policy for elections at: https://fedoraproject.org/wiki/FESCo_election_policy One of the listed requirements is that nominees be members of the packager group. We currently have a FESCO nominee who participates in QA who does not qualify for FESCO if the information on that page is still accurate. This should probably get clarified before the election gets started. I think FESCO dates back before there was a formal QA group and it may make sense to modify the requirements for FESCO members in light of changes over the last 3 years. This has come up before in recent-ish-ly (My memory seems to think about two election cycles ago so ~1 year. But I'm getting old and time may be passing me by faster than I think :-). At that time it was still thought that packager group made sense for people serving on FESCo. I don't remember any new information that differed from the discussion wy back in time when FESCo opened up the electorate to groups outside of packager but kept packager as a requirement for nominees. Note that this is just history; the people who make up FESCo these days may take the same arguments and apply a different weight to them than the people who discussed and decided upon this in the past. -Toshio pgppoNyNXVp4v.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: libpng bumped to 1.5.x in rawhide
Chris Adams wrote: Hmm, I didn't know that. Which does RPM use when generating dependencies? It would appear that it is is using ldd; should that be changed? No, RPM does not pull in recursive soname dependencies, only direct ones. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File IO-Prompt-0.997001.tar.gz uploaded to lookaside cache by iarnell
A file has been added to the lookaside cache for perl-IO-Prompt: c1311dd2122cca28426394acf2aed2ba IO-Prompt-0.997001.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Prompt] update to 0.997001
commit 74286c3e6f641a7ea7e94f8e0e0d40b2818008de
Author: Iain Arnell iarn...@gmail.com
Date: Sat Nov 5 08:19:48 2011 +0100
update to 0.997001
.gitignore |1 +
perl-IO-Prompt.spec | 12
sources |2 +-
3 files changed, 10 insertions(+), 5 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 8693504..17ebb00 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
IO-Prompt-0.997.tar.gz
+/IO-Prompt-0.997001.tar.gz
diff --git a/perl-IO-Prompt.spec b/perl-IO-Prompt.spec
index a86b288..05c036e 100644
--- a/perl-IO-Prompt.spec
+++ b/perl-IO-Prompt.spec
@@ -1,10 +1,11 @@
Name: perl-IO-Prompt
Summary:Interactively prompt for user input
-Version:0.997
-Release:6%{?dist}
+%global cpanver 0.997001
+Version:0.997.001
+Release:1%{?dist}
License:GPL+ or Artistic
Group: Development/Libraries
-Source0:
http://search.cpan.org/CPAN/authors/id/D/DC/DCONWAY/IO-Prompt-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/D/DC/DCONWAY/IO-Prompt-%{cpanver}.tar.gz
URL:http://search.cpan.org/dist/IO-Prompt
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
@@ -34,7 +35,7 @@ prompted.
%prep
-%setup -q -n IO-Prompt-%{version}
+%setup -q -n IO-Prompt-%{cpanver}
find . -type f -exec chmod -c -x {} ';'
@@ -69,6 +70,9 @@ rm -rf %{buildroot}
%changelog
+* Sat Nov 05 2011 Iain Arnell iarn...@gmail.com 0.997.001-1
+- update to latest upstream version
+
* Tue Jun 21 2011 Marcela Mašláňová mmasl...@redhat.com - 0.997-6
- Perl mass rebuild
diff --git a/sources b/sources
index bacc407..c23d694 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-3f6a8610db9c541e07daffde650f0e7d IO-Prompt-0.997.tar.gz
+c1311dd2122cca28426394acf2aed2ba IO-Prompt-0.997001.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Prompt] apply patch to fix rt#69084
commit 62efa2d83869967180720a7212db0f0d00d23c95
Author: Iain Arnell iarn...@gmail.com
Date: Sat Nov 5 08:22:40 2011 +0100
apply patch to fix rt#69084
perl-IO-Prompt-rt69084.patch | 33 +
perl-IO-Prompt.spec |6 ++
2 files changed, 39 insertions(+), 0 deletions(-)
---
diff --git a/perl-IO-Prompt-rt69084.patch b/perl-IO-Prompt-rt69084.patch
new file mode 100644
index 000..3ab3c37
--- /dev/null
+++ b/perl-IO-Prompt-rt69084.patch
@@ -0,0 +1,33 @@
+From 8300962b023580328f78b86aa1776d369769 Mon Sep 17 00:00:00 2001
+From: Fuji, Goro gf...@cpan.org
+Date: Sat, 25 Jun 2011 11:16:10 +0900
+Subject: [PATCH] Use Scalar::Util::openhandle() instead of $io-opend
+
+---
+ lib/IO/Prompt.pm |3 ++-
+ 1 files changed, 2 insertions(+), 1 deletions(-)
+
+diff --git a/lib/IO/Prompt.pm b/lib/IO/Prompt.pm
+index 343d204..e0db947 100644
+--- a/lib/IO/Prompt.pm
b/lib/IO/Prompt.pm
+@@ -11,6 +11,7 @@ no warnings 'utf8';
+ our @EXPORT= qw( prompt );
+ our @EXPORT_OK = qw( hand_print get_input );
+
++use Scalar::Util;
+ use IO::Handle;
+ use Term::ReadKey;
+ use POSIX qw( isprint );
+@@ -185,7 +186,7 @@ sub prompt {
+ else {
+ no strict 'refs';
+ my $ARGV = $caller . ::ARGV;
+-unless (*$ARGV-opened) {
++unless (Scalar::Util::openhandle(*$ARGV)) {
+ $$ARGV = shift(@$ARGV) || '-';
+ open $ARGV or croak Can't open $$ARGV: $!;
+ }
+--
+1.7.5.4
+
diff --git a/perl-IO-Prompt.spec b/perl-IO-Prompt.spec
index 05c036e..198337f 100644
--- a/perl-IO-Prompt.spec
+++ b/perl-IO-Prompt.spec
@@ -6,6 +6,10 @@ Release:1%{?dist}
License:GPL+ or Artistic
Group: Development/Libraries
Source0:
http://search.cpan.org/CPAN/authors/id/D/DC/DCONWAY/IO-Prompt-%{cpanver}.tar.gz
+# doesn't work on 5.14 if you call prompt() in non-main package
+# see https://rt.cpan.org/Public/Bug/Display.html?id=69084
+# and
https://github.com/gfx/p5-IO-Prompt-patched/commit/8300962b023580328f78b86aa1776d369769.patch
+Patch0: perl-IO-Prompt-rt69084.patch
URL:http://search.cpan.org/dist/IO-Prompt
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
@@ -36,6 +40,7 @@ prompted.
%prep
%setup -q -n IO-Prompt-%{cpanver}
+%patch0 -p1
find . -type f -exec chmod -c -x {} ';'
@@ -72,6 +77,7 @@ rm -rf %{buildroot}
%changelog
* Sat Nov 05 2011 Iain Arnell iarn...@gmail.com 0.997.001-1
- update to latest upstream version
+- apply patch to fix rt#69084
* Tue Jun 21 2011 Marcela Mašláňová mmasl...@redhat.com - 0.997-6
- Perl mass rebuild
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Prompt] fix test scripts' line endings
commit 16ff290ca2a0d81199787ceb9833356631841ec9
Author: Iain Arnell iarn...@gmail.com
Date: Sat Nov 5 08:28:46 2011 +0100
fix test scripts' line endings
perl-IO-Prompt.spec |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
---
diff --git a/perl-IO-Prompt.spec b/perl-IO-Prompt.spec
index 198337f..76a533c 100644
--- a/perl-IO-Prompt.spec
+++ b/perl-IO-Prompt.spec
@@ -42,6 +42,8 @@ prompted.
%setup -q -n IO-Prompt-%{cpanver}
%patch0 -p1
+sed -i 's/\r//' t/*.t
+
find . -type f -exec chmod -c -x {} ';'
%build
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Prompt] use bcond to disable tests by default
commit 267098850d62641f0b48b9bb3f69c2fc71eabe9f
Author: Iain Arnell iarn...@gmail.com
Date: Sat Nov 5 08:37:09 2011 +0100
use bcond to disable tests by default
perl-IO-Prompt.spec | 12 ++--
1 files changed, 10 insertions(+), 2 deletions(-)
---
diff --git a/perl-IO-Prompt.spec b/perl-IO-Prompt.spec
index 76a533c..bc602d6 100644
--- a/perl-IO-Prompt.spec
+++ b/perl-IO-Prompt.spec
@@ -15,11 +15,16 @@ BuildRoot:
%{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
BuildArch: noarch
+# tests require working /dev/tty - disabled by default for koji
+# see https://rt.cpan.org/Public/Bug/Display.html?id=54807
+%bcond_with check
+
BuildRequires: perl(IO::Handle)
BuildRequires: perl(POSIX)
BuildRequires: perl(Term::ReadKey)
BuildRequires: perl(Test::More)
BuildRequires: perl(Test::Pod)
+BuildRequires: perl(Test::Pod::Coverage)
BuildRequires: perl(version)
BuildRequires: perl(Want)
@@ -61,8 +66,11 @@ find %{buildroot} -type d -depth -exec rmdir {} 2/dev/null
';'
%check
-%{?!_with_chec: echo Not running tests unless --with check is specificed }
-%{?_with_check: make test }
+%if %{with check}
+make test
+%else
+echo Not running tests unless --with check is specified
+%endif
%clean
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Prompt] remove unnecessary explicit requires
commit d15966658f9d29f44655b87788390d2f39ce38ff
Author: Iain Arnell iarn...@gmail.com
Date: Sat Nov 5 08:43:51 2011 +0100
remove unnecessary explicit requires
perl-IO-Prompt.spec |7 +--
1 files changed, 1 insertions(+), 6 deletions(-)
---
diff --git a/perl-IO-Prompt.spec b/perl-IO-Prompt.spec
index bc602d6..4980436 100644
--- a/perl-IO-Prompt.spec
+++ b/perl-IO-Prompt.spec
@@ -28,12 +28,6 @@ BuildRequires: perl(Test::Pod::Coverage)
BuildRequires: perl(version)
BuildRequires: perl(Want)
-Requires: perl(IO::Handle)
-Requires: perl(POSIX)
-Requires: perl(Term::ReadKey)
-Requires: perl(version)
-Requires: perl(Want)
-
%{?perl_default_filter}
%{?perl_default_subpackage_tests}
@@ -88,6 +82,7 @@ rm -rf %{buildroot}
* Sat Nov 05 2011 Iain Arnell iarn...@gmail.com 0.997.001-1
- update to latest upstream version
- apply patch to fix rt#69084
+- remove unnecessary explicit requires
* Tue Jun 21 2011 Marcela Mašláňová mmasl...@redhat.com - 0.997-6
- Perl mass rebuild
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Prompt/f16] (5 commits) ...remove unnecessary explicit requires
Summary of changes: 74286c3... update to 0.997001 (*) 62efa2d... apply patch to fix rt#69084 (*) 16ff290... fix test scripts' line endings (*) 2670988... use bcond to disable tests by default (*) d159666... remove unnecessary explicit requires (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 750805] Fails to build on ARM, needs to use default setjmp not ucontext
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=750805 --- Comment #9 from Henrik Nordström hen...@henriknordstrom.net 2011-11-05 04:52:26 EDT --- It's a runtime issue detected by the test suite. I by accident did not have FORTIFY_SOURCE enabled when testing the first change. Coro (and pth) both abuses setjmp in the same manner for establishing new stacks per context, but with FORTIFY_SOURCE enabled glibc verifies that setjmp only sets the stack pointer to an earlier stack frame in the current stack and aborts if the stack change looks odd. *** longjmp causes uninitialized stack frame ***: /usr/bin/perl terminated it's a valid error message in normal specified use of setjmp, but do not apply to the special (outside specifications) use by Coro for establishing another stack context entirely, outside the current stack. -- 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-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 751548] New: perl-Log-Log4perl-1.34 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-Log-Log4perl-1.34 is available https://bugzilla.redhat.com/show_bug.cgi?id=751548 Summary: perl-Log-Log4perl-1.34 is available Product: Fedora Version: rawhide Platform: Unspecified OS/Version: Unspecified Status: NEW Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Component: perl-Log-Log4perl AssignedTo: mmasl...@redhat.com ReportedBy: upstream-release-monitor...@fedoraproject.org QAContact: extras...@fedoraproject.org CC: fedora-perl-devel-l...@redhat.com, mmasl...@redhat.com Classification: Fedora Story Points: --- Type: --- Latest upstream release: 1.34 Current version in Fedora Rawhide: 1.33 URL: http://search.cpan.org/dist/Log-Log4perl/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 751550] New: perl-MooseX-MarkAsMethods-0.14 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-MooseX-MarkAsMethods-0.14 is available https://bugzilla.redhat.com/show_bug.cgi?id=751550 Summary: perl-MooseX-MarkAsMethods-0.14 is available Product: Fedora Version: rawhide Platform: Unspecified OS/Version: Unspecified Status: NEW Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Component: perl-MooseX-MarkAsMethods AssignedTo: ppi...@redhat.com ReportedBy: upstream-release-monitor...@fedoraproject.org QAContact: extras...@fedoraproject.org CC: fedora-perl-devel-l...@redhat.com, mmasl...@redhat.com, ppi...@redhat.com Classification: Fedora Story Points: --- Type: --- Latest upstream release: 0.14 Current version in Fedora Rawhide: 0.13 URL: http://search.cpan.org/dist/MooseX-MarkAsMethods/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 751549] New: perl-Math-MatrixReal-2.09 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-Math-MatrixReal-2.09 is available https://bugzilla.redhat.com/show_bug.cgi?id=751549 Summary: perl-Math-MatrixReal-2.09 is available Product: Fedora Version: rawhide Platform: Unspecified OS/Version: Unspecified Status: NEW Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Component: perl-Math-MatrixReal AssignedTo: mmasl...@redhat.com ReportedBy: upstream-release-monitor...@fedoraproject.org QAContact: extras...@fedoraproject.org CC: fedora-perl-devel-l...@redhat.com, pertu...@free.fr, mmasl...@redhat.com Classification: Fedora Story Points: --- Type: --- Latest upstream release: 2.09 Current version in Fedora Rawhide: 2.08 URL: http://search.cpan.org/dist/Math-MatrixReal/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 746941] perl-Mojolicious-2.23 is available
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=746941 Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org changed: What|Removed |Added Summary|perl-Mojolicious-2.21 is|perl-Mojolicious-2.23 is |available |available --- Comment #13 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org 2011-11-05 07:35:21 EDT --- Latest upstream release: 2.23 Current version in Fedora Rawhide: 1.99 URL: http://search.cpan.org/dist/Mojolicious/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 746196] perlbrew-0.31 is available
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=746196 Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org changed: What|Removed |Added Summary|perlbrew-0.30 is available |perlbrew-0.31 is available --- Comment #1 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org 2011-11-05 07:38:02 EDT --- Latest upstream release: 0.31 Current version in Fedora Rawhide: 0.29 URL: http://search.cpan.org/dist/App-perlbrew/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
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-9.fc16.noarch requires perl(:MODULE_COMPAT_5.12.3) On i386: perl-Pugs-Compiler-Rule-0.37-9.fc16.noarch requires perl(:MODULE_COMPAT_5.12.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-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
