Re: Bug 18 i386 installer
Hi, this should be covered by https://bugzilla.redhat.com/show_bug.cgi?id=893892, (ie your latest traceback is in https://bugzilla.redhat.com/show_bug.cgi?id=893892#c26) We have updates image with simple fix for F18 Common Bugs: http://fedoraproject.org/wiki/Common_F18_bugs#Live_installation_on_machines_with_WWAN_network_card_freezes For F19 I'm going to work on more generic fix of ifcfg files handling. Radek On 01/20/2013 01:16 AM, Benjamin Adams wrote: During the network install section I got the fallowing: Next Item was: Traceback (most recent call last): File /usr/lib/python2.7/site-packages/pyanaconda/threads.py, line 91, in run threading.Thread.run(self, *args, **kwargs) File /usr/lib/python2.7/threading.py, line 504, in run self.__target(*self.__args, **self.__kwargs) File /usr/lib/python2.7/site-packages/pyanaconda/install.py, line 72, in doConfiguration ksdata.network.execute(storage, ksdata, instClass) File /usr/lib/python2.7/site-packages/pyanaconda/kickstart.py, line 759, in execute network.write_network_config(storage, ksdata, instClass, ROOT_PATH) File /usr/lib/python2.7/site-packages/pyanaconda/network.py, line 929, in write_network_config write_sysconfig_network(rootpath, ksdata, overwrite=flags.livecdInstall) File /usr/lib/python2.7/site-packages/pyanaconda/network.py, line 840, in write_sysconfig_network dev.loadIfcfgFile() File /usr/lib/python2.7/site-packages/pyanaconda/network.py, line 311, in loadIfcfgFile IfcfgFile.read(self) File /usr/lib/python2.7/site-packages/pyanaconda/simpleconfig.py, line 187, in read SimpleConfigFile.read(self, self.path) File /usr/lib/python2.7/site-packages/pyanaconda/simpleconfig.py, line 77, in read with open(filename) as f: IOError: [Errno 2] No such file or directory: '/etc/sysconfig/network-scripts/ifcfg-ttyUSB0' contents of /etc/sysconfig/network-scripts: [liveuser@localhost ~]$ ls /etc/sysconfig/network-scripts/ ifcfg-lo ifdown-postifup-ipppifup-sit ifcfg-p2p1ifdown-ppp ifup-ipv6ifup-tunnel ifcfg-wifinetwork ifdown-routes ifup-ipx ifup-wireless ifdownifdown-sit ifup-isdninit.ipv6-global ifdown-bnep ifdown-tunnel ifup-plipkeys-wifinetwork ifdown-ethifup ifup-plusb network-functions ifdown-ippp ifup-aliases ifup-postnetwork-functions-ipv6 ifdown-ipv6 ifup-bnep ifup-ppp ifdown-isdn ifup-eth ifup-routes Still some changes need will look later on. Ben On Sat, Jan 19, 2013 at 6:56 PM, Benjamin Adams benjamindad...@gmail.com wrote: hello, I did a fix change to the installer. This is on i386 not sure about x64 coding. Fix was in file: /usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py line 960: from @hostname.setter def hostname(self, value): self.entry_hostname.set_text(value) To: @hostname.setter def hostname(self, value): +if not value: +value = 'localhost' self.entry_hostname.set_text(value) Installing also on wireless without network connection. Thanks, Ben Adams On Sat, Jan 19, 2013 at 5:37 PM, Benjamin Adams benjamindad...@gmail.com wrote: I'm on a IBM T60 I get the fallowing error on the welcome screen with languages. I select English (US) ... Hitting Continue I get: (Attached is my dmesg) (anaconda:2413): Gtk-WARNING **: Overriding tab label for notebook Traceback (most recent call last): File /usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/__init__.py, line 77, in lambda self.window.connect(continue-clicked, lambda *args: self._on_continue_clicked(cb)) File /usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/welcome.py, line 287, in _on_continue_clicked StandaloneSpoke._on_continue_clicked(self, cb) File /usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/__init__.py, line 73, in _on_continue_clicked cb() File /usr/lib/python2.7/site-packages/pyanaconda/ui/gui/__init__.py, line 234, in _on_continue_clicked nextAction = self._instantiateAction(self._actions[1]) File /usr/lib/python2.7/site-packages/pyanaconda/ui/gui/__init__.py, line 77, in _instantiateAction obj = actionClass(self.data, self.storage, self.payload, self.instclass) File /usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py, line 1091, in __init__ self.network_control_box.hostname = self.data.network.hostname File /usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py, line 960, in hostname self.entry_hostname.set_text(value) File /usr/lib/python2.7/site-packages/gi/types.py, line 47, in function return info.invoke(*args, **kwargs) TypeError: Argument 1 does not allow None as a value I know some python. Don't have time to debug now but will look tonight. Ben -- test mailing list test@lists.fedoraproject.org To unsubscribe:
Re: Blocker process: tracker bug / whiteboard naming proposal
The proposal is this: fXXalpha fXXalpha-freezebreak fXXbeta fXXbeta-freezebreak fXXfinal fXXfinal-freezebreak acceptedblocker acceptedfb Big thumbs up. A few things for consideration: 1. Do we need numbers in the alias? We always release just a single Fedora at a time. 2. Do we need F in the alias? Unless our aliases clash, we don't need to distinguish Fedora from the other projects in Bugzilla. 3. As Jared mentioned, a freeze exception sounds better (and explains better) than a freeze break. Unfortunately it's longer. So we can end up also with this: AlphaBlocker AlphaFreezeException BetaBlocker BetaFreezeException FinalBlocker FinalFreezeException But that's just an idea. Your proposal above is great improvement as well and I don't have any objections to it. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Bugzilla bug
I tried to report a problem with bugzilla but bugzilla crashes:
[caf@omen h]$ bugzilla new
Traceback (most recent call last):
File /bin/bugzilla, line 813, in module
main()
File /bin/bugzilla, line 590, in main
data[a] = i.split(',')
AttributeError: 'NoneType' object has no attribute 'split'
[caf@omen h]$
--
Chuck Forsberg WA7KGX c...@omen.com www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc The High Reliability Software
10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Spamd won't listen to spamc
This is the maillog entry I get when I try to pass an email to spamc. ]: spamd: unauthorized connection from omen.com [70.89.176.169] at port 55566 at /usr/bin/spamd line 1271. Jan 21 02:03:51 omen spamd[25898]: prefork: child states: II -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc The High Reliability Software 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Bugzilla bug
On Mon, 21 Jan 2013 02:02:40 -0800, Chuck Forsberg WA7KGX N2469R wrote:
I tried to report a problem with bugzilla but bugzilla crashes:
[caf@omen h]$ bugzilla new
Traceback (most recent call last):
File /bin/bugzilla, line 813, in module
main()
File /bin/bugzilla, line 590, in main
data[a] = i.split(',')
AttributeError: 'NoneType' object has no attribute 'split'
[caf@omen h]$
Then use the working web pages at http://bugzilla.redhat.com and report
that there about python-bugzilla. ;) Unless you've used the script
incorrectly. It could be broken, however, since most people use the web
pages (or other XML-RPC based scripts).
The more convenient Fedora bug link at
http://bugz.fedoraproject.org/python-bugzilla
also still exists.
In general: http://bugz.fedoraproject.org/SOURCE_RPM_NAME_HERE
--
Fedora release 18 (Spherical Cow) - Linux 3.7.2-204.fc18.x86_64
loadavg: 0.90 0.37 0.22
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Re: Blocker process: tracker bug / whiteboard naming proposal
On 01/21/2013 09:48 AM, Kamil Paral wrote: The proposal is this: fXXalpha fXXalpha-freezebreak fXXbeta fXXbeta-freezebreak fXXfinal fXXfinal-freezebreak acceptedblocker acceptedfb Big thumbs up. A few things for consideration: 1. Do we need numbers in the alias? We always release just a single Fedora at a time. 2. Do we need F in the alias? Unless our aliases clash, we don't need to distinguish Fedora from the other projects in Bugzilla. 3. As Jared mentioned, a freeze exception sounds better (and explains better) than a freeze break. Unfortunately it's longer. So we can end up also with this: AlphaBlocker AlphaFreezeException BetaBlocker BetaFreezeException FinalBlocker FinalFreezeException But that's just an idea. Your proposal above is great improvement as well and I don't have any objections to it. I ack Jared's FreezeException and Kamil's proposal/idea JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20130121 changes
Compose started at Mon Jan 21 08:15:11 UTC 2013 Broken deps for x86_64 -- [bootconf] bootconf-1.4-6.fc18.noarch requires grub [epiphany-extensions] epiphany-extensions-3.6.0-1.fc19.x86_64 requires epiphany(abi) = 0:3.6 [fawkes] fawkes-guis-0.5.0-5.fc19.i686 requires libgraph.so.5 fawkes-guis-0.5.0-5.fc19.x86_64 requires libgraph.so.5()(64bit) [flowcanvas] flowcanvas-0.7.1-7.fc18.i686 requires libgraph.so.5 flowcanvas-0.7.1-7.fc18.x86_64 requires libgraph.so.5()(64bit) [freeipa] freeipa-server-strict-3.1.0-1.fc19.x86_64 requires pki-ca = 0:10.0.0 freeipa-server-strict-3.1.0-1.fc19.x86_64 requires 389-ds-base = 0:1.3.0 [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 [gdal] gdal-1.9.1-15.fc19.x86_64 requires libpoppler.so.26()(64bit) gdal-java-1.9.1-15.fc19.i686 requires libpoppler.so.26 gdal-java-1.9.1-15.fc19.x86_64 requires libpoppler.so.26()(64bit) gdal-libs-1.9.1-15.fc19.i686 requires libpoppler.so.26 gdal-libs-1.9.1-15.fc19.x86_64 requires libpoppler.so.26()(64bit) gdal-perl-1.9.1-15.fc19.x86_64 requires libpoppler.so.26()(64bit) gdal-ruby-1.9.1-15.fc19.x86_64 requires libpoppler.so.26()(64bit) [gdb-heap] gdb-heap-0.5-11.fc19.x86_64 requires glibc(x86-64) = 0:2.16.90 [gdcm] gdcm-2.0.18-6.fc18.i686 requires libpoppler.so.26 gdcm-2.0.18-6.fc18.x86_64 requires libpoppler.so.26()(64bit) [gfal] gfal-1.14.0-1.fc18.i686 requires libgsoap.so.2 gfal-1.14.0-1.fc18.x86_64 requires libgsoap.so.2()(64bit) gfal-doc-1.14.0-1.fc18.x86_64 requires libgsoap.so.2()(64bit) gfal-python-1.14.0-1.fc18.x86_64 requires libgsoap.so.2()(64bit) [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) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSinteger-gmp-0.4.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHShttp-types-0.6.11-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHShashable-1.1.2.3-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSghc-prim-0.2.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSfilepath-1.3.0.0-ghc7.4.1.so()(64bit) ghc-wai-extra-1.2.0.4-4.fc18.x86_64 requires libHSfast-logger-0.0.2-ghc7.4.1.so()(64bit)
Re: Blocker process: tracker bug / whiteboard naming proposal
On Po, 2013-01-21 at 04:48 -0500, Kamil Paral wrote: The proposal is this: fXXalpha fXXalpha-freezebreak fXXbeta fXXbeta-freezebreak fXXfinal fXXfinal-freezebreak acceptedblocker acceptedfb Big thumbs up. A few things for consideration: 1. Do we need numbers in the alias? We always release just a single Fedora at a time. 2. Do we need F in the alias? Unless our aliases clash, we don't need to distinguish Fedora from the other projects in Bugzilla. 3. As Jared mentioned, a freeze exception sounds better (and explains better) than a freeze break. Unfortunately it's longer. So we can end up also with this: AlphaBlocker AlphaFreezeException BetaBlocker BetaFreezeException FinalBlocker FinalFreezeException But that's just an idea. Your proposal above is great improvement as well and I don't have any objections to it. That sounds great. Easy to remember, easy to use :) I'm +1. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Spamd won't listen to spamc
On 01/21/2013 10:06 AM, Chuck Forsberg WA7KGX N2469R wrote: This is the maillog entry I get when I try to pass an email to spamc. ]: spamd: unauthorized connection from omen.com [70.89.176.169] at port 55566 at /usr/bin/spamd line 1271. Jan 21 02:03:51 omen spamd[25898]: prefork: child states: II This mailing list is NOT for general help. Use the users list: https://admin.fedoraproject.org/mailman/listinfo/users Also learn how to ask smart questions: http://www.catb.org/esr/faqs/smart-questions.html#intro Or consult spamd upstream documentation on how to list and allow clients JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
fedup network download
I have a few boxes that use a local repository that is rsync'd for both fedora and updates. When I tried out fedup --network the tool showed the names of my local repos. However, when it started package downloads I noticed the speed to be 100k to 500k per second range. This would indicate that fedup is downloading from an Internet mirror (6mbit Internet) instead of my local mirror (gigabit network). I found, through ss, that fedup is indeed connected to an FTP server on the Internet (ftp-chi.osuosl.org). Is fedup hardcoded to use the default fedora and updates repos even if they are disabled? Thanks, Michael -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Spamd won't listen to spamc
On 01/21/2013 06:01 AM, Jóhann B. Guðmundsson wrote: On 01/21/2013 10:06 AM, Chuck Forsberg WA7KGX N2469R wrote: This is the maillog entry I get when I try to pass an email to spamc. ]: spamd: unauthorized connection from omen.com [70.89.176.169] at port 55566 at /usr/bin/spamd line 1271. Jan 21 02:03:51 omen spamd[25898]: prefork: child states: II This mailing list is NOT for general help. Use the users list: https://admin.fedoraproject.org/mailman/listinfo/users Also learn how to ask smart questions: http://www.catb.org/esr/faqs/smart-questions.html#intro Or consult spamd upstream documentation on how to list and allow clients JBG I have been using spamc since at least 2006 and probably longer. # send mail through Spamassassin :0fw |spamc Now all of a sudden Fedora 18 breaks the .procmailrc entry that was suggested in the documentation. Smells like a bug to me. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc The High Reliability Software 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Spamd won't listen to spamc
On 01/21/2013 04:56 PM, Chuck Forsberg WA7KGX N2469R wrote: On 01/21/2013 06:01 AM, Jóhann B. Guðmundsson wrote: On 01/21/2013 10:06 AM, Chuck Forsberg WA7KGX N2469R wrote: This is the maillog entry I get when I try to pass an email to spamc. ]: spamd: unauthorized connection from omen.com [70.89.176.169] at port 55566 at /usr/bin/spamd line 1271. Jan 21 02:03:51 omen spamd[25898]: prefork: child states: II This mailing list is NOT for general help. Use the users list: https://admin.fedoraproject.org/mailman/listinfo/users Also learn how to ask smart questions: http://www.catb.org/esr/faqs/smart-questions.html#intro Or consult spamd upstream documentation on how to list and allow clients JBG I have been using spamc since at least 2006 and probably longer. # send mail through Spamassassin :0fw |spamc Now all of a sudden Fedora 18 breaks the .procmailrc entry that was suggested in the documentation. Smells like a bug to me. To me it sounds like misconfigured/unconfigured spamd which lacks -A 70.89.176.169 which allows omen.com to connect to it. ( By default only localhost is allowed ) thus user issue hence off topic for this list... JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Blocker process: tracker bug / whiteboard naming proposal
On Mon, Jan 21, 2013 at 04:48:56AM -0500, Kamil Paral wrote: Big thumbs up. A few things for consideration: 1. Do we need numbers in the alias? We always release just a single Fedora at a time. If they're _not_ per release, all of the old dependencies will need to be removed from the alias after each release, causing a lot of churn. I don't know how important it is to save the history for its own sake, but I think avoiding the need to clear the bug is worth it. 2. Do we need F in the alias? Unless our aliases clash, we don't need to distinguish Fedora from the other projects in Bugzilla. I think it makes it more clear that we're talking about a Fedora-wide thing, not a process specific to each package. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Spamd won't listen to spamc
On 01/21/2013 09:01 AM, Jóhann B. Guðmundsson wrote: On 01/21/2013 04:56 PM, Chuck Forsberg WA7KGX N2469R wrote: On 01/21/2013 06:01 AM, Jóhann B. Guðmundsson wrote: On 01/21/2013 10:06 AM, Chuck Forsberg WA7KGX N2469R wrote: This is the maillog entry I get when I try to pass an email to spamc. ]: spamd: unauthorized connection from omen.com [70.89.176.169] at port 55566 at /usr/bin/spamd line 1271. Jan 21 02:03:51 omen spamd[25898]: prefork: child states: II This mailing list is NOT for general help. Use the users list: https://admin.fedoraproject.org/mailman/listinfo/users Also learn how to ask smart questions: http://www.catb.org/esr/faqs/smart-questions.html#intro Or consult spamd upstream documentation on how to list and allow clients JBG I have been using spamc since at least 2006 and probably longer. # send mail through Spamassassin :0fw |spamc Now all of a sudden Fedora 18 breaks the .procmailrc entry that was suggested in the documentation. Smells like a bug to me. To me it sounds like misconfigured/unconfigured spamd which lacks -A 70.89.176.169 which allows omen.com to connect to it. ( By default only localhost is allowed ) thus user issue hence off topic for this list... JBG As has been the case for the last 6+ years, the calling spamc has been on the same machine as spamd. Something has changed in Fedora 18 to break it. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc The High Reliability Software 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Spamd won't listen to spamc
On 01/21/2013 05:34 PM, Chuck Forsberg WA7KGX N2469R wrote: On 01/21/2013 09:01 AM, Jóhann B. Guðmundsson wrote: On 01/21/2013 04:56 PM, Chuck Forsberg WA7KGX N2469R wrote: On 01/21/2013 06:01 AM, Jóhann B. Guðmundsson wrote: On 01/21/2013 10:06 AM, Chuck Forsberg WA7KGX N2469R wrote: This is the maillog entry I get when I try to pass an email to spamc. ]: spamd: unauthorized connection from omen.com [70.89.176.169] at port 55566 at /usr/bin/spamd line 1271. Jan 21 02:03:51 omen spamd[25898]: prefork: child states: II This mailing list is NOT for general help. Use the users list: https://admin.fedoraproject.org/mailman/listinfo/users Also learn how to ask smart questions: http://www.catb.org/esr/faqs/smart-questions.html#intro Or consult spamd upstream documentation on how to list and allow clients JBG I have been using spamc since at least 2006 and probably longer. # send mail through Spamassassin :0fw |spamc Now all of a sudden Fedora 18 breaks the .procmailrc entry that was suggested in the documentation. Smells like a bug to me. To me it sounds like misconfigured/unconfigured spamd which lacks -A 70.89.176.169 which allows omen.com to connect to it. ( By default only localhost is allowed ) thus user issue hence off topic for this list... JBG As has been the case for the last 6+ years, the calling spamc has been on the same machine as spamd. Something has changed in Fedora 18 to break it. Then file a bug against spamd and attach it's debug out put to it. JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Spamd won't listen to spamc
On Mon, 21 Jan 2013, Chuck Forsberg WA7KGX N2469R wrote: ]: spamd: unauthorized connection from omen.com [70.89.176.169] at port 55566 at /usr/bin/spamd line 1271. Jan 21 02:03:51 omen spamd[25898]: prefork: child states: II :0fw |spamc ... As has been the case for the last 6+ years, the calling spamc has been on the same machine as spamd. Something has changed in Fedora 18 to break it. Times change, and the new kid is: ... systemd I would be suspicious of a corner case of systemd, and it not handling the external interface connection, but ... that needs some research first To partition the problem, perhaps change your iptables to pass all on that IP, add a spamd 'listening interface' rules [/etc/sysconfig/spamassassin -- a '-i' option, although the man page implies all interfaces are neing listened on to accept your boxes 'external' IP, and change your spamc connection to use 127.0.0.1, all come to mind -- Russ herrold -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Spamd won't listen to spamc
On 01/21/2013 05:51 PM, R P Herrold wrote: Times change, and the new kid is: ... systemd The service bugs ( as always ) should be first filed against the relevant services ( spamd ) then it's maintainer will move it against systemd if it turns out it's actually causing it ( which more often than not is not the case ) JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Blocker process: tracker bug / whiteboard naming proposal
On Mon, 2013-01-21 at 12:08 -0500, Matthew Miller wrote: On Mon, Jan 21, 2013 at 04:48:56AM -0500, Kamil Paral wrote: Big thumbs up. A few things for consideration: 1. Do we need numbers in the alias? We always release just a single Fedora at a time. If they're _not_ per release, all of the old dependencies will need to be removed from the alias after each release, causing a lot of churn. I don't know how important it is to save the history for its own sake, but I think avoiding the need to clear the bug is worth it. My first reaction was this, and then I realized, wait, we're talking about the *alias*. Not the bug ID. The alias is transferrable. It's not one tracker bug for all Alpha blockers ever, but one alias which transfers from bug to bug: we create a new set of bugs for each cycle, but we just transfer the alias from the old to the new. We can keep track of the old bug IDs in the wiki (we already do this, in fact) so we can still relatively easily find old trackers. Proposing a small refinement: we apply the release specific alias names to the old trackers after each release. So right now the F19 bugs would be AlphaBlocker, AlphaFreezeException etc: when F19 goes out, we transfer those aliases to the F20 bugs, and make the F19 bugs F19AlphaBlocker, F19AlphaFreezeException etc. We can even apply this retroactively all the way back through the bug database (add those aliases to the old bugs) so we can always find the trackers for any release via the same format. So a big ack to Kamil's idea. It makes a huge amount of sense and simplifies things so much: at any time ever, if you want to nominate a bug as blocking the Alpha, mark it as AlphaBlocker. D'oh. On the 'F' thing: the only issue to remember is that Bugzilla is shared with RHEL. But RHEL has a different blocker process and I think the changes of them deciding they want to use the same aliases is quite small, and if it happens, we can tweak things a bit later (just add 'Fedora' or 'F' or whatever into the aliases). For now I'm a big +1 to the simple option. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Blocker process: tracker bug / whiteboard naming proposal
On Mon, Jan 21, 2013 at 11:57:12 -0600, Adam Williamson awill...@redhat.com wrote: Proposing a small refinement: we apply the release specific alias names to the old trackers after each release. So right now the F19 bugs would be AlphaBlocker, AlphaFreezeException etc: when F19 goes out, we transfer those aliases to the F20 bugs, and make the F19 bugs F19AlphaBlocker, F19AlphaFreezeException etc. We can even apply this retroactively all the way back through the bug database (add those aliases to the old bugs) so we can always find the trackers for any release via the same format. I think you want to do the numbered aliases at the start of the cycle, not at the end. That way people can use the numbers consisantly while including the develoment release. (This might make scripting easier.) The other stuff all looks good. Names will be easier to remember and be more understandable. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Spamd won't listen to spamc
On 01/21/2013 06:06 PM, Chuck Forsberg WA7KGX N2469R wrote: This is the maillog entry I get when I try to pass an email to spamc. ]: spamd: unauthorized connection from omen.com [70.89.176.169] at port 55566 at /usr/bin/spamd line 1271. Jan 21 02:03:51 omen spamd[25898]: prefork: child states: II You should be sending these questions to the users list since F18 has been released. You are more than likely to get a better response then posting here. However.. While I don't currently have sendmail configured and/or using procmail, I don't think my system has any problem root 26947 1 0 07:27 ?00:00:02 /usr/bin/spamd --pidfile /var/run/spamd.pid -d -c -m5 -H root 26948 26947 0 07:27 ?00:00:00 spamd child root 26949 26947 0 07:27 ?00:00:00 spamd child netstat -nap returns tcp0 0 127.0.0.1:783 0.0.0.0:* LISTEN 26947/spamd.pid -d and spamc test.eml returns the message with the following headers added X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f18x X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=DKIM_SIGNED,RCVD_IN_DNSWL_MED, SPF_PASS,T_DKIM_INVALID,T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.2 additionally [egreshko@f18x ~]$ telnet localhost 783 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. helo SPAMD/1.0 76 Bad header line: helo Connection closed by foreign host. Which is what I would expect... With the following recorded in the maillog as expected Jan 22 00:02:26 f18x spamd[26948]: spamd: connection from localhost [127.0.0.1] at port 47657 Jan 22 00:02:40 f18x spamd[26948]: spamd: bad protocol: header error: helo Jan 22 00:02:40 f18x spamd[26947]: prefork: child states: II -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry Compiled -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
version update permission for Bugs
I'm CC on several bugs that need to be moved to a newer version. What process do I need to go through to get that update power? So far, my comments to such bugs that it's needed have gone unheeded. I have a 32bit F18 installation I want to move to 64 bit and Rawhide, in two steps if necessary. Is 32 to 64 via installer something that needs testing in Rawhide, or should I just install Rawhide fresh? -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
