"The karma value of your comment has been changed to zero, because you submitted the update."
Hello. I've just been hit by this while trying to add "-1" to karma, and I think that's a regression. Could somebody please fix this? Or at least could somebody explain why it's no longer possible to downvote your own builds? -- With best regards, Peter Lemenkov. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
pulseaudio maintainership status
Dear list, Dear Lennart, a week ago I have submitted a pulseaudio bug alongside with the patch [1]. There was no response so far. Knowing that Lennart is busy with systemd these days, I proceeded to check the pkgdb status of pulseaudio. The only other maintainer with commit access is lkundrak, who has been declared non-responsive a while ago himself, plus 3 request pending. To have such a critical subsystem barely maintained does not seem sustainable. I have already stepped up to co-maintain pavucontrol and paprefs, but PA proper is a whole other level. I have joined the waiting list and am willing communicate the issues between Fedora and upstream, but someone with an ability to fix bugs on their own would be welcome too. Lennart, could you please look at the pending ACL requests? Thank you. Merry Christmas everyone, Julian [1] https://bugzilla.redhat.com/show_bug.cgi?id=888422 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: "The karma value of your comment has been changed to zero, because you submitted the update."
On Tue, Dec 25, 2012 at 10:23 AM, Peter Lemenkov wrote: > Hello. > I've just been hit by this while trying to add "-1" to karma, and I > think that's a regression. Could somebody please fix this? Or at least > could somebody explain why it's no longer possible to downvote your > own builds? What's the point? You can/should just unpush the update ... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: "The karma value of your comment has been changed to zero, because you submitted the update."
2012/12/25 drago01 : > On Tue, Dec 25, 2012 at 10:23 AM, Peter Lemenkov wrote: >> Hello. >> I've just been hit by this while trying to add "-1" to karma, and I >> think that's a regression. Could somebody please fix this? Or at least >> could somebody explain why it's no longer possible to downvote your >> own builds? > What's the point? You can/should just unpush the update ... It's not always practical. Especially in case of a minor glitch in a big package. I still want to mention about an issue but don't want to unpush it right now. -- With best regards, Peter Lemenkov. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: "The karma value of your comment has been changed to zero, because you submitted the update."
On Tue, Dec 25, 2012 at 12:12 PM, Peter Lemenkov wrote: > 2012/12/25 drago01 : >> On Tue, Dec 25, 2012 at 10:23 AM, Peter Lemenkov wrote: >>> Hello. >>> I've just been hit by this while trying to add "-1" to karma, and I >>> think that's a regression. Could somebody please fix this? Or at least >>> could somebody explain why it's no longer possible to downvote your >>> own builds? > >> What's the point? You can/should just unpush the update ... > > It's not always practical. Especially in case of a minor glitch in a > big package. I still want to mention about an issue but don't want to > unpush it right now. Adding a negative karma is the wrong way to do it ... not everyone looks at the bodhi page. The best place to put such stuff in would be the update description. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20121225 changes
Compose started at Tue Dec 25 08:15:40 UTC 2012 Broken deps for x86_64 -- [airinv] airinv-0.1.2-5.fc19.i686 requires libstdairuicl.so.0.45 airinv-0.1.2-5.fc19.i686 requires libstdair.so.0.45 airinv-0.1.2-5.fc19.x86_64 requires libstdairuicl.so.0.45()(64bit) airinv-0.1.2-5.fc19.x86_64 requires libstdair.so.0.45()(64bit) [airrac] airrac-0.2.3-5.fc19.i686 requires libstdairuicl.so.0.45 airrac-0.2.3-5.fc19.i686 requires libstdair.so.0.45 airrac-0.2.3-5.fc19.x86_64 requires libstdairuicl.so.0.45()(64bit) airrac-0.2.3-5.fc19.x86_64 requires libstdair.so.0.45()(64bit) [airsched] airsched-0.1.4-5.fc19.i686 requires libstdairuicl.so.0.45 airsched-0.1.4-5.fc19.i686 requires libstdair.so.0.45 airsched-0.1.4-5.fc19.x86_64 requires libstdairuicl.so.0.45()(64bit) airsched-0.1.4-5.fc19.x86_64 requires libstdair.so.0.45()(64bit) [almanah] almanah-0.10.0-3.fc19.x86_64 requires libedataserverui-3.0.so.5()(64bit) almanah-0.10.0-3.fc19.x86_64 requires libcamel-1.2.so.42()(64bit) [ansible] ansible-fireball-0.9-1.fc19.noarch requires python-keyczar ansible-node-fireball-0.9-1.fc19.noarch requires python-keyczar [cp2k] cp2k-mpich2-2.3-1.fc19.x86_64 requires libmpichf90.so.3()(64bit) cp2k-mpich2-2.3-1.fc19.x86_64 requires libmpich.so.3()(64bit) [dogtag-pki] dogtag-pki-10.0.0-0.16.b3.fc19.noarch requires dogtag-pki-server-theme >= 0:10.0.0 [ekiga] ekiga-4.0.0-1.fc19.x86_64 requires libcamel-1.2.so.42()(64bit) [ember] ember-0.6.3-3.fc19.x86_64 requires libOgreMain.so.1.7.4()(64bit) [epiphany-extensions] epiphany-extensions-3.6.0-1.fc19.x86_64 requires epiphany(abi) = 0:3.6 [evolution-rss] 1:evolution-rss-0.3.92-3.fc19.x86_64 requires libevolution-utils.so()(64bit) 1:evolution-rss-0.3.92-3.fc19.x86_64 requires libemiscwidgets.so()(64bit) 1:evolution-rss-0.3.92-3.fc19.x86_64 requires libemail-utils.so()(64bit) 1:evolution-rss-0.3.92-3.fc19.x86_64 requires libedataserverui-3.0.so.5()(64bit) 1:evolution-rss-0.3.92-3.fc19.x86_64 requires libcamel-1.2.so.42()(64bit) [freeipa] freeipa-server-3.1.0-1.fc19.x86_64 requires dogtag-pki-server-theme [freewrl] freewrl-1.22.13.1-3.fc18.i686 requires libGLEW.so.1.7 freewrl-1.22.13.1-3.fc18.x86_64 requires libGLEW.so.1.7()(64bit) libEAI-1.22.13.1-3.fc18.i686 requires libGLEW.so.1.7 libEAI-1.22.13.1-3.fc18.x86_64 requires libGLEW.so.1.7()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python2-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python3-debug-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python3-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 [ghc-wai-extra] ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSzlib-conduit-0.4.0.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSzlib-bindings-0.1.0.1-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSzlib-0.5.3.3-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSwai-1.2.0.3-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSvoid-0.5.6-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSvault-0.2.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSunordered-containers-0.2.1.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSunix-2.5.1.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHStransformers-base-0.4.1-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHStransformers-0.3.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHStime-1.4-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHStext-0.11.2.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSsemigroups-0.8.3.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSresourcet-0.3.2.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSparsec-3.1.2-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSold-time-1.1.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSold-locale-1.0.0.4-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSnetwork-2.3.0.13-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSmtl-2.1.1-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSmonad-control-0.3.1.3-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSlifted-base-0.1.1-ghc7.4.1.so()(64bit
F-18 Branched report: 20121225 changes
Compose started at Tue Dec 25 09:15:56 UTC 2012 Summary: Added Packages: 0 Removed Packages: 0 Upgraded Packages: 0 Compose finished at Tue Dec 25 13:21:56 UTC 2012 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
About repo option in kickstart file
Hi, I've created and appended an repo option to a kickstart file, then I've created an iso with livecd-creator and it works fine. Packages of that repo are "installed" in the ISO file. The problem is that the repo file is not created in the installed system generated from LiveCD. Is that the expected behaviour? Should I download the repo file using a %post section? Thanks in advance! -- -- Sergio Belkin http://www.sergiobelkin.com Watch More TV http://sebelk.blogspot.com LPIC-2 Certified - http://www.lpi.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: About repo option in kickstart file
On Tue, 25 Dec 2012, Sergio Belkin wrote: I've created and appended an repo option to a kickstart file, then I've created an iso with livecd-creator and it works fine. Packages of that repo are "installed" in the ISO file. The problem is that the repo file is not created in the installed system generated from LiveCD. Is that the expected behaviour? Should I download the repo file using a %post section? Yes, you need to include it in a package, see the fedora-release package which you can use as a base for your custom-release package. Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
