Re: Texlive schemes?
Am Dienstag, den 22.12.2009, 15:09 +0100 schrieb Jindrich Novy: > On Tue, Dec 22, 2009 at 11:45:52AM +0100, Christoph Höger wrote: > > Hi all, > > > > after texlive 2009 crashed my latex compiling process one day before I > > wanted to print my dipl-thesis (kpsewhich hanging indefinitely), I > > erased all texlive* files. > > > > From my last installation experience I learned that installing only > > texlive leaves you with a non-working system (for my needs), so I wanted > > to simplify things by installing the full or medium scheme. > > > > [choe...@choeger5 ~]$ LC_ALL=C sudo yum install texlive-scheme-full > > Loaded plugins: presto, refresh-packagekit > > Setting up Install Process > > No package texlive-scheme-full available. > > Nothing to do > > > > Shouldn't that work? > > Confirmed. I rewrote the the upstream -> Fedora repo script from > scratch where an error occured. It is fixed so please try again now. Installation seems to work now, but the installation of texlive-kpathsea-2009-3.16044.fc12.noarch (and possibly much more packages) hangs because kpsewhich hangs forever (using 100% cpu). Do you have any clue whats going on? Any chance to get this fixed before christmas? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Texlive schemes?
Am Dienstag, den 22.12.2009, 11:45 +0100 schrieb Christoph Höger: > Hi all, > > after texlive 2009 crashed my latex compiling process one day before I > wanted to print my dipl-thesis (kpsewhich hanging indefinitely), I > erased all texlive* files. > > From my last installation experience I learned that installing only > texlive leaves you with a non-working system (for my needs), so I wanted > to simplify things by installing the full or medium scheme. > > [choe...@choeger5 ~]$ LC_ALL=C sudo yum install texlive-scheme-full > Loaded plugins: presto, refresh-packagekit > Setting up Install Process > No package texlive-scheme-full available. > Nothing to do > > Shouldn't that work? Ok, basically it looks like _everything_ is broken currently. e.g.: > [choe...@choeger5 ~]$ LC_ALL=C sudo yum install texlive-bibtex-bin > Loaded plugins: presto, refresh-packagekit > Setting up Install Process > Resolving Dependencies > --> Running transaction check > ---> Package texlive-bibtex-bin.x86_64 0:2009-2.16044.fc12 set to be updated > --> Processing Dependency: texlive-bibtex = 2009 for package: > texlive-bibtex-bin-2009-2.16044.fc12.x86_64 > --> Processing Dependency: texlive = 2009 for package: > texlive-bibtex-bin-2009-2.16044.fc12.x86_64 > --> Processing Dependency: libkpathsea.so.5()(64bit) for package: > texlive-bibtex-bin-2009-2.16044.fc12.x86_64 > --> Running transaction check > ---> Package texlive.x86_64 0:2009-3.20091219.fc12 set to be updated > --> Processing Dependency: texlive-scheme-basic for package: > texlive-2009-3.20091219.fc12.x86_64 > --> Processing Dependency: texlive-collection-latexrecommended for package: > texlive-2009-3.20091219.fc12.x86_64 > ---> Package texlive-bibtex-bin.x86_64 0:2009-2.16044.fc12 set to be updated > --> Processing Dependency: texlive-bibtex = 2009 for package: > texlive-bibtex-bin-2009-2.16044.fc12.x86_64 > ---> Package texlive-kpathsea-lib.x86_64 0:2009-3.20091219.fc12 set to be > updated > --> Finished Dependency Resolution > texlive-2009-3.20091219.fc12.x86_64 from texlive has depsolving problems > --> Missing Dependency: texlive-collection-latexrecommended is needed by > package texlive-2009-3.20091219.fc12.x86_64 (texlive) > texlive-2009-3.20091219.fc12.x86_64 from texlive has depsolving problems > --> Missing Dependency: texlive-scheme-basic is needed by package > texlive-2009-3.20091219.fc12.x86_64 (texlive) > texlive-bibtex-bin-2009-2.16044.fc12.x86_64 from texlive has depsolving > problems > --> Missing Dependency: texlive-bibtex = 2009 is needed by package > texlive-bibtex-bin-2009-2.16044.fc12.x86_64 (texlive) > Error: Missing Dependency: texlive-scheme-basic is needed by package > texlive-2009-3.20091219.fc12.x86_64 (texlive) > Error: Missing Dependency: texlive-collection-latexrecommended is needed by > package texlive-2009-3.20091219.fc12.x86_64 (texlive) > Error: Missing Dependency: texlive-bibtex = 2009 is needed by package > texlive-bibtex-bin-2009-2.16044.fc12.x86_64 (texlive) > You could try using --skip-broken to work around the problem > You could try running: package-cleanup --problems > package-cleanup --dupes > rpm -Va --nofiles --nodigest > signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Texlive schemes?
Hi all, after texlive 2009 crashed my latex compiling process one day before I wanted to print my dipl-thesis (kpsewhich hanging indefinitely), I erased all texlive* files. From my last installation experience I learned that installing only texlive leaves you with a non-working system (for my needs), so I wanted to simplify things by installing the full or medium scheme. [choe...@choeger5 ~]$ LC_ALL=C sudo yum install texlive-scheme-full Loaded plugins: presto, refresh-packagekit Setting up Install Process No package texlive-scheme-full available. Nothing to do Shouldn't that work? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Bug in python?
Hi,
while I was investigating an offlineimap bug, the following happened
quite often:
File "/usr/lib64/python2.6/threading.py", line 497, in __bootstrap
self.__bootstrap_inner()
File "/usr/lib64/python2.6/threading.py", line 575, in
__bootstrap_inner
self.__stop()
File "/usr/lib64/python2.6/threading.py", line 586, in __stop
self.__block.notify_all()
File "/usr/lib64/python2.6/threading.py", line 289, in notifyAll
self.notify(len(self.__waiters))
File "/usr/lib64/python2.6/threading.py", line 277, in notify
self._note("%s.notify(): no waiters", self)
File "/usr/lib64/python2.6/threading.py", line 68, in _note
current_thread().name, format)
File "/usr/lib64/python2.6/threading.py", line 808, in currentThread
return _DummyThread()
File "/usr/lib64/python2.6/threading.py", line 788, in __init__
self._Thread__started.set()
File "/usr/lib64/python2.6/threading.py", line 378, in set
self.__cond.notify_all()
File "/usr/lib64/python2.6/threading.py", line 289, in notifyAll
self.notify(len(self.__waiters))
File "/usr/lib64/python2.6/threading.py", line 277, in notify
self._note("%s.notify(): no waiters", self)
File "/usr/lib64/python2.6/threading.py", line 68, in _note
current_thread().name, format)
File "/usr/lib64/python2.6/threading.py", line 808, in currentThread
return _DummyThread()
File "/usr/lib64/python2.6/threading.py", line 788, in __init__
self._Thread__started.set()
File "/usr/lib64/python2.6/threading.py", line 378, in set
self.__cond.notify_all()
File "/usr/lib64/python2.6/threading.py", line 289, in notifyAll
self.notify(len(self.__waiters))
File "/usr/lib64/python2.6/threading.py", line 277, in notify
self._note("%s.notify(): no waiters", self)
File "/usr/lib64/python2.6/threading.py", line 68, in _note
current_thread().name, format)
File "/usr/lib64/python2.6/threading.py", line 808, in currentThread
return _DummyThread()
File "/usr/lib64/python2.6/threading.py", line 788, in __init__
self._Thread__started.set()
File "/usr/lib64/python2.6/threading.py", line 378, in set
self.__cond.notify_all()
File "/usr/lib64/python2.6/threading.py", line 289, in notifyAll
Looks to me like calling _DummyThread() every time and then printing a
debug output is a bad idea, right?
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
audio group after upgrade
Hi, after my upgrade to f12 I could play any sound files. This was a odd problem: Not just my speakers stay silent, but the player won't even start. xmms complained: ** WARNING **: alsa_get_mixer(): Attaching to mixer hw:0 failed: Permission denied And, indeed, I was not in the audio group. (simple fix - so no problem for me) I assume that every user is in this group by default upon installation, so why does anaconda not handle this? (If no one noticed this yet, just think of this mail as a feature request) regards Christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
abrt bugzilla reporting - does it work?
Hi, I just wanted to report an evolution crash report with abrt. All I get (besides a stacktrace) is "libcurl failed HTTP Post". Since I suspect that libcurl generally can handle HTTP posts, I wonder if this is some general bug in abrt? Did anybody submit bugs successfully using this tool? regards Christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: [Fwd: Broken dependencies: offlineimap]
Am Dienstag, den 17.11.2009, 02:38 +0530 schrieb Rahul Sundaram: > On 11/17/2009 02:38 AM, Christoph Höger wrote: > > Hi, > > > > does anyone know what this means? Did we switch from Python 2.6 to 3.x > > or is python broken itself on rawhide? > > You can ignore them. Details at > > https://www.redhat.com/archives/fedora-devel-announce/2009-November/msg00010.html > > Rahul Ah, I should have noticed that, but this email was on top of my TODO this evening. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
[Fwd: Broken dependencies: offlineimap]
Hi, does anyone know what this means? Did we switch from Python 2.6 to 3.x or is python broken itself on rawhide? --- Begin Message --- offlineimap has broken dependencies in the development tree: On ppc: offlineimap-6.1.2-2.fc12.noarch requires python(abi) = 0:2.6 offlineimap-6.1.2-2.fc12.noarch requires /usr/bin/python On ppc64: offlineimap-6.1.2-2.fc12.noarch requires python(abi) = 0:2.6 offlineimap-6.1.2-2.fc12.noarch requires /usr/bin/python Please resolve this as soon as possible. --- End Message --- signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 has gone gold
Am Mittwoch, den 11.11.2009, 12:52 -0500 schrieb James Laska: > On Wed, 2009-11-11 at 17:06 +0100, Christoph Höger wrote: > > Am Montag, den 09.11.2009, 17:29 -0800 schrieb Jesse Keating: > > > We have just completed our Go / No Go meeting for Fedora 12 and have > > > reached the decision to Go. Fedora 12's package set is golden and we're > > > ready to stage things for shipping. Great work all around, I'm very > > > proud of this release. I'm sure there will be more back patting and > > > hand shaking to come, but Will Woods would like to remind everybody that > > > it's just 11 weeks until Fedora 13 Alpha freeze! > > > > Does that mean, preupgrade to rawhide will bring in the f12 packages? If > > so, there is a major issue with anaconda that crashes upon detecting the > > harddrives. This is a little bit troubling since I have nothing exotic > > here, just two sata hds. > > > > I saved the debug report, but without storage I probably saved it to a > > ram disk. > > If anyone can help me figuring out how to get a stacktrace to a running > > machine (except for pen&paper), I would be able to bring up some > > valuable information about that crash. > > The installer team has a fairly comprehensive wiki page on triaging > installation-related failures > (https://fedoraproject.org/wiki/How_to_debug_installation_problems). > > Are you able to save the traceback directly to bugzilla, instead of to > your local disk? Nope, but the tty2 hint was what I needed. https://bugzilla.redhat.com/show_bug.cgi?id=536906 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 has gone gold
Am Montag, den 09.11.2009, 17:29 -0800 schrieb Jesse Keating: > We have just completed our Go / No Go meeting for Fedora 12 and have > reached the decision to Go. Fedora 12's package set is golden and we're > ready to stage things for shipping. Great work all around, I'm very > proud of this release. I'm sure there will be more back patting and > hand shaking to come, but Will Woods would like to remind everybody that > it's just 11 weeks until Fedora 13 Alpha freeze! Does that mean, preupgrade to rawhide will bring in the f12 packages? If so, there is a major issue with anaconda that crashes upon detecting the harddrives. This is a little bit troubling since I have nothing exotic here, just two sata hds. I saved the debug report, but without storage I probably saved it to a ram disk. If anyone can help me figuring out how to get a stacktrace to a running machine (except for pen&paper), I would be able to bring up some valuable information about that crash. regards christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Feature request: AMD K10 thermal sensors
Am Donnerstag, den 29.10.2009, 14:51 +0100 schrieb Michal Schmidt: > Dne 29.10.2009 12:38, Christoph Höger napsal(a): > > since a year or so the AMD K10 thermal sensors module (k10temp) seems to > > be floating around the web. I would appreciate some kernel packager > > integrating it into the fedora 11 stock kernel - since without it I can > > not build (and trust!) a silent cooling system. > > > > Any plans on this issue? > > AMD K10 sensors support has been repeatedly refused by upstream > lm_sensors developers because of the sensors' unreliability. > > e.g. Rudolf Marek said in LKML on 2009-08-28: > > There is a problem that all chips of fam10h have some errata which renders > > the > > monitoring driver unusable. Some people proposed a workaround if temps look > > too > > suspicious to refuse to load. This is against a sense of monitoring to > > refuse > > the values where they don't look "right". So there is no driver. > > Michal Just one question: How are the lm_sensors names (10h, 11h) related to current processors? 11h seems to be WIP. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Feature request: AMD K10 thermal sensors
Am Donnerstag, den 29.10.2009, 14:51 +0100 schrieb Michal Schmidt: > Dne 29.10.2009 12:38, Christoph Höger napsal(a): > > since a year or so the AMD K10 thermal sensors module (k10temp) seems to > > be floating around the web. I would appreciate some kernel packager > > integrating it into the fedora 11 stock kernel - since without it I can > > not build (and trust!) a silent cooling system. > > > > Any plans on this issue? > > AMD K10 sensors support has been repeatedly refused by upstream > lm_sensors developers because of the sensors' unreliability. > > e.g. Rudolf Marek said in LKML on 2009-08-28: > > There is a problem that all chips of fam10h have some errata which renders > > the > > monitoring driver unusable. Some people proposed a workaround if temps look > > too > > suspicious to refuse to load. This is against a sense of monitoring to > > refuse > > the values where they don't look "right". So there is no driver. So this means there is no chance to get my thermal sensors working under fedora? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Feature request: AMD K10 thermal sensors
Hi, since a year or so the AMD K10 thermal sensors module (k10temp) seems to be floating around the web. I would appreciate some kernel packager integrating it into the fedora 11 stock kernel - since without it I can not build (and trust!) a silent cooling system. Any plans on this issue? regards Christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: ld ignoring parts of LD_LIBRARY_PATH?
Am Dienstag, den 27.10.2009, 10:30 +0100 schrieb Christoph Höger: > Hi, > > this is slightly off topic, but may be relevant for fedora developing, > too: > > I have set up a small test bed for an application I am converting to a > autotools build system. In this testbed I have: > > ./lib/libfoo.so > ./lib/bar/libbar.so > > When I add the lib/ entry to LD_LIBRARY_PATH it is recognized and > scanned for libraries. The same for the lib/bar entry. But when I add > both, the lib/ entry is ignored completely. Is this normal? > > regards Please forget this crap - I was confused by my headache this morning and did not see that the error occured during _compile time_ sry signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
ld ignoring parts of LD_LIBRARY_PATH?
Hi, this is slightly off topic, but may be relevant for fedora developing, too: I have set up a small test bed for an application I am converting to a autotools build system. In this testbed I have: ./lib/libfoo.so ./lib/bar/libbar.so When I add the lib/ entry to LD_LIBRARY_PATH it is recognized and scanned for libraries. The same for the lib/bar entry. But when I add both, the lib/ entry is ignored completely. Is this normal? regards Christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning some packages [Was: Re: Buyer Beware: A Major Change in NFS is about to happen]
Am Samstag, den 03.10.2009, 10:09 +0100 schrieb Peter Robinson: > > syncevolution -- SyncML client for evolution > > I'll take this one. > > Peter I've just commented on that package, but you're not yet maintaining it, so I'll repeat what I've discussed with Matěj already: 1. There is some bug with the libraries lying in /usr/lib/syncevolution without patching no binary works out of the box 2. The sync-ui binary (which I wanted to test the most ;)) is missing. regars Christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
mutt broken?
Hi, I am not sure if this is a bug or my misusage of something, but when I try to access my Maildir with mutt the deletion flags are correctly set on the first run but disappear when I close mutt. This means that all those mails that ended up in my Trash folder (e.g. in evolution) are now in my INBOX again. Has anybody seen this before? Shall I file a bug? regards christoph -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: bodhi formatting
Am Montag, den 14.09.2009, 11:51 +0200 schrieb Mathieu Bridon (bochecha): > Hi, > > > I wanted to be a good packager and include the upstream CHANGELOG lines > > in the update notes of bsf-2.4.0, but bodhi does not accept empty lines > > (error) nor linebreaks (ignored). How is that text supposed to be > > formatted? > > For best results, you can use the MarkDown syntax. > > Right now, PK understands it and will display it nicely. > > I'm working on it on the Bodhi side, so that Bodhi displays it nicely > as well. Patches are available, waiting for Luke to accept them or ask > me to rework them :) > https://fedorahosted.org/bodhi/ticket/286 Thanks for the hint. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
bodhi formatting
Hi, I wanted to be a good packager and include the upstream CHANGELOG lines in the update notes of bsf-2.4.0, but bodhi does not accept empty lines (error) nor linebreaks (ignored). How is that text supposed to be formatted? regards Christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
cannot mockbuild
Hi, when I try make mockbuild on the bsf package to test my changes, I get the following error: [r...@choeger5 devel]# yum --installroot /var/lib/mock/fedora-11-x86_64/root/ resolvedep ccache 'jython' 'java-gcj-compat-devel' 'ant' 'tomcat5-jsp-2.0-api' 'xalan-j2' 'servlet' 'jpackage-utils >= 1.6' Traceback (most recent call last): File "/usr/bin/yum", line 29, in yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 309, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 157, in main base.getOptionsConfig(args) File "/usr/share/yum-cli/cli.py", line 189, in getOptionsConfig self.conf File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 652, in conf = property(fget=lambda self: self._getConfig(), File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 239, in _getConfig self._conf = config.readMainConfig(startupconf) File "/usr/lib/python2.6/site-packages/yum/config.py", line 794, in readMainConfig yumvars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg) File "/usr/lib/python2.6/site-packages/yum/config.py", line 873, in _getsysver hdr = idx.next() StopIteration Any ideas what causes that? regards Christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Dragonfly Mail Agent
Am Dienstag, den 01.09.2009, 18:48 +0100 schrieb Jonathan Underwood: > 2009/8/31 Neal Becker : > > We already have ssmtp, esmtp. Is this something different? > > I don't think they have local mail delivery capability, though that is > being worked on for esmtp. Does dma have a local queue? Can I sendmail emails when I am offline? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Dragonfly Mail Agent
Hi, is dma packaged by someone? That would be the first step and I would happily test that thing (having postfix installed after Paul Frields advice which works well). regards Christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
network issues with kernel-2.6.29.6-217.2.8.fc11.i586
Hi all, I hope somebody can confirm this: The last days I had some trouble with my networking (both wireless and ethernet) in forms of high latency, strange arp behaviour etc. Today I could not even ping anything outside. The problem seemed to be that: 1. arp replys were ignored 2. if arp -s was used, anything else was ignored for the userspace That means: I pinged my nameserver, and tcpdump showed request and replys happily flowing around. But: ping did not get any packet. It reported 100% packet loss. That applies to any other userspace prog that uses a socket. I also had some wireless errors (iwlagn: microcode error) in my dmesg the days before. Currently I am using kernel-2.6.29.6-217.2.8.fc11.i586 and the problem arised after some minutes again. Looks like a buffer run full or somethign... Is there a workaround? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Empathy default in F12?
Am Sonntag, den 16.08.2009, 13:10 +0530 schrieb Rahul Sundaram: > On 08/16/2009 01:05 PM, Gregory Maxwell wrote: > > The F12 feature still indicates the switch to Empathy as a default IM > > client in Fedora. > > > > However, the talk page for the feature > > (https://fedoraproject.org/wiki/Talk:Features/Empathy) raises material > > concerns that the switch to Empathy would result in an insufficiently > > justified loss of functionality. > > > > Where does this currently stand? > > My understanding is that Empathy is still planned to be the default. > What specific concerns do you have? Well on fedora 10 it cannot connect to irc. Which makes it pretty unusable. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Feature proposal: Rebootless Installer
Am Dienstag, den 14.07.2009, 09:00 -0600 schrieb Douglas McClendon: > Christoph Höger wrote: > >> We are talking about a live cd installation, yes? You can close the > >> installer then. > > > > We were talking about anaconda. And I still don't know a sane (aka "no > > manual chroot") way to go from livecd into the fresh installed > > environment. > > If you look at the feature page and watch 18 minutes of youtube videos, > and/or look at my code, I think you'll have to admit there is 'a way' to > do it. I certainly won't be offended by the label 'insane' however, > unless of course you find technical problems with my implementation, in > which case, I still won't mind the label, I'll just go fix em. That was, of course, meant: Except for feature proposals discussed here ;) signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Feature proposal: Rebootless Installer
> We are talking about a live cd installation, yes? You can close the > installer then. We were talking about anaconda. And I still don't know a sane (aka "no manual chroot") way to go from livecd into the fresh installed environment. You surely agree that users that know about chroot are probably not the ones adressed with the "hey, cool, in this linux thingy i do not need to reboot after install" feature, don't you? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Feature proposal: Rebootless Installer
> Nobody is forced. You must be misremembering things. Huh? Plain installing worked without reboot? Did not notice that last weekend with f11 i386 dvd. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Feature proposal: Rebootless Installer
Hi, although (as others pointed out) a reboot may be necessary one way or the other, my opinion would be: Why not? Currently you are *forced* to reboot which now seems not to be a must have. So why not remove that force and allow the user to decide when to reboot? (Maybe one would like to install all available updates before he has to reboot *again* because kernel updates or stuff). So before any flaming starts: Please keep in mind that no one wants to *remove* reboot. ;) my 2ct christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: RFC: cronKit
Am Sonntag, den 12.07.2009, 22:22 +0200 schrieb Christoph Wickert: > Am Sonntag, den 12.07.2009, 22:09 +0200 schrieb Christoph Höger: > > Am Sonntag, den 12.07.2009, 22:04 +0200 schrieb Christoph Höger: > > > Am Sonntag, den 12.07.2009, 01:54 +0200 schrieb Christoph Wickert: > > > > How about http://www.gnomefiles.org/app.php/DoThisNow > > > > > > Looks, good, thanks Christoph. > > > > Darn. Not free. > > Sorry about that, I didn't notice. Time for a free port I think ;) Yes, after my exam in SOA, I can definetely need something to work on besides my thesis. That will fit that hole. I'll still need to see what language and tools I'll use. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: RFC: cronKit
Am Sonntag, den 12.07.2009, 22:04 +0200 schrieb Christoph Höger: > Am Sonntag, den 12.07.2009, 01:54 +0200 schrieb Christoph Wickert: > > How about http://www.gnomefiles.org/app.php/DoThisNow > > Looks, good, thanks Christoph. Darn. Not free. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: RFC: cronKit
Am Sonntag, den 12.07.2009, 01:54 +0200 schrieb Christoph Wickert: > How about http://www.gnomefiles.org/app.php/DoThisNow Looks, good, thanks Christoph. > No more kits please. ;) Whatever the new software would be named, pls > don't make another *kit. What about a KitKit to manage tham all? Or NameKit for controlling how newly created software will be named? ;) signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: delaying an update
Thanks. Did it. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: delaying an update
Am Mittwoch, den 08.07.2009, 17:41 +0300 schrieb Jussi Lehtola: > On Wed, 2009-07-08 at 09:30 -0500, Michael Cronenworth wrote: > > Christoph Höger on 07/08/2009 09:21 AM wrote: > > > > > > how do I do that? > > > > > > > Since you have not submitted it for "stable" I do not see any problem. > > Don't do anything. :) > > You might want to disable the automatic push to stable, though, in case > the package gets too much karma.. That's what I meant with "delay". So how do I do that? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
delaying an update
Hi, my latest update to offlineimap https://admin.fedoraproject.org/updates/offlineimap-6.1.0-2.fc11 has revealed a bug somewhere between offlineimap imaplib2 and kerberos. Since I do not know how to fix that, I would like to: a) delay that update from being pushed to stable as long as the situation is unclear b) cancel it if there is no upstream response in a week or so how do I do that? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: RFC: cronKit
Am Montag, den 06.07.2009, 16:02 -0400 schrieb Casey Dahlin: > On 07/06/2009 03:58 PM, Christoph Höger wrote: > > What I forgot to mention: Obviously it is not enough to know that there > > is a gnome session running. My programs should inherit the environment. > > > > I'll point out that upstart will do all this to some point, but I don't > expect you to wait around for us :) > > --CJD > Could it handle jobs as gnome child processes? Or would upstart solve that issue differently? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: RFC: cronKit
What I forgot to mention: Obviously it is not enough to know that there is a gnome session running. My programs should inherit the environment. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: RFC: cronKit
> ps u -C gnome-session | egrep -q "^till " && offlineimap Yeah, that would be a hack ;). signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
RFC: cronKit
Hi, since I sync my mail with the experimental gnome ui of offlineimap, I encounter a small problem: How do I tell cron to only invoke the job when I am logged in under gnome only? Since consolekit (correct me if I am wrong on that) does not provide a way to get that information (it is even unclear if dbus is running at all), I was thinking of the following solution: Since I want the job only to be run if I am logged in under gnome the main idea is to have a process added to the session that can handle crontab like jobs (aka cronKit) Do you have any advice on that? Does such a software already exist? regards Christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: certificate not (yet) active?
Am Donnerstag, den 02.07.2009, 14:02 +0200 schrieb Till Maas:
> On Thu July 2 2009, Christoph Höger wrote:
>
> > I had to create a new .fedora.cert this morning, because make
> > new-sources told me mine was out of date.
> > So I did but now make build runs into
> >
> > Error: [('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate
> > verify failed')]
> >
> > why that? (And I wanted to update offlineimap to 6.1.0 today *sniff*)
>
> Maybe you need to run fedora-packager-setup from fedora-packager again. If
> you
> edited your koji.conf, you may re-add your changes btw.
>
Thanks, that worked it out. It isn't the easiest thing to package from
two pcs and keep their data in sync.
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
certificate not (yet) active?
Hi,
I had to create a new .fedora.cert this morning, because make
new-sources told me mine was out of date.
So I did but now make build runs into
Error: [('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate
verify failed')]
why that? (And I wanted to update offlineimap to 6.1.0 today *sniff*)
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: [Phoronix] Ubuntu 9.04 vs. Fedora 11 Performance
> I don't think it's ever going to happen. The laypress should just die, > people need to go directly to the developers to get actual information. Wow. Cool statement. Next time I wonder if my algorithm actually does work in O(n) I am not going to read books or papers but ask turing himself. You should know that a _normal_ person cannot simply ask thousands of developers for reasons to use their software. That's why there are media. They simplify things because readers ask for simplification. You can hate them, but you'll always need them. So live with them! signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: [Phoronix] Ubuntu 9.04 vs. Fedora 11 Performance
Am Freitag, den 12.06.2009, 19:55 +1000 schrieb Eric Springer: > 2009/6/12 Christoph Höger : > > Could you explain why mp3 (or ogg) encoding is not a "real world" > > benchmark? I do this quite often. > > Because they are comparing file system on what is a CPU bound test. Notice > how all the file systems perform the same. That was their conclusion, too: Anyone who wants fastest possible encoding can use any filesystem. But it has to be measured, as the difference in ogg encoding shows. That's what makes up "Real World" tests IMO: To test even side effects no one would ever really think of. As in "real world" you will probably store your encoded files on your filesystem it is good to see that there are no regressions. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: [Phoronix] Ubuntu 9.04 vs. Fedora 11 Performance
Am Freitag, den 12.06.2009, 04:22 +0200 schrieb Dennis J.: > On 06/11/2009 10:07 PM, Eric Sandeen wrote: > > It may be better to engage them, though, and try to make the tests more > > correct, transparent and relevant they do have a lot of momentum. > > Which makes the crazy stuff hurt even more. :) > > They use MP3 encoding as a "real world benchmark" of ext4: > http://www.phoronix.com/scan.php?page=article&item=ext4_benchmarks&num=7 > > They don't seem to care what they measure or why or what the results > actually mean. Phoronix' "benchmarks" seem to be mostly about earning > Phoronix a bad reputation. Could you explain why mp3 (or ogg) encoding is not a "real world" benchmark? I do this quite often. I also think that knowing regressions (like there sqlite benchmark had shown for older kernels) is generally not that bad. Of course someone still needs to do some work, but as numbers may be irrelevant a trend is not. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: [Phoronix] Ubuntu 9.04 vs. Fedora 11 Performance
> The question becomes what is significantly different in the Apache > test? Is the Apache test essentially a network i/o test? What is > significantly different here that would not end up being tracked to an > upstream kernel networking stack regression? Is the apache performance > collatoral damage from selinux related latency?Something else in > userspace slowing Apache down. I've no idea. I can't imagine its > compiler related options on the Apache binaries. Without knowing how exactly the benchmark works I would guess that most of those apache requests are kernel calls so SELinux _might_ make a huge difference here. Perhaps somebody from the SELinux team should tell phoronix about it (and to _always_ test with SELinux disabled to measure the price of security). signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: evolution header: Mime-version: 1.0
Am Donnerstag, den 04.06.2009, 09:30 +0200 schrieb Christoph Höger: > Am Mittwoch, den 03.06.2009, 10:09 -0700 schrieb Johannes Erdfelt: > > On Wed, Jun 03, 2009, Christoph Höger wrote: > > > I see a small problem with evolution when sending to mailinglists. > > > Obviously evolution puts: Mime-version: 1.0 in the header, hypermail > > > searches for MIME-version: and cannot find that string. So it adds it. > > > In turn my mail provider bounces the return message that should be sent > > > to me complaining about duplicate header field. > > > > > > So who is wrong here? Hypermail or evolution? Is non uppercase letter > > > Mime-version allowed? Anyone knowing the answer? > > > > Hypermail. > > > > Headers should be matched in a case insensitive manner. > > > > JE > > Where do you get that conclusion from? I can only cite RFC 2045 which > says: > > > Messages composed in accordance with this document MUST include such > >a header field, with the following verbatim text: > > > > MIME-Version: 1.0 Found RFC 5234 myself. Thanks. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: evolution header: Mime-version: 1.0
Am Mittwoch, den 03.06.2009, 10:09 -0700 schrieb Johannes Erdfelt: > On Wed, Jun 03, 2009, Christoph Höger wrote: > > I see a small problem with evolution when sending to mailinglists. > > Obviously evolution puts: Mime-version: 1.0 in the header, hypermail > > searches for MIME-version: and cannot find that string. So it adds it. > > In turn my mail provider bounces the return message that should be sent > > to me complaining about duplicate header field. > > > > So who is wrong here? Hypermail or evolution? Is non uppercase letter > > Mime-version allowed? Anyone knowing the answer? > > Hypermail. > > Headers should be matched in a case insensitive manner. > > JE Where do you get that conclusion from? I can only cite RFC 2045 which says: > Messages composed in accordance with this document MUST include such >a header field, with the following verbatim text: > > MIME-Version: 1.0 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
evolution header: Mime-version: 1.0
Hi folks, I see a small problem with evolution when sending to mailinglists. Obviously evolution puts: Mime-version: 1.0 in the header, hypermail searches for MIME-version: and cannot find that string. So it adds it. In turn my mail provider bounces the return message that should be sent to me complaining about duplicate header field. So who is wrong here? Hypermail or evolution? Is non uppercase letter Mime-version allowed? Anyone knowing the answer? thanks christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaned eclipse-pydev
Isn't that this application with ads in it? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: thinkpad and acpi events
[choe...@choeger6 ~]$ lsmod | grep think thinkpad_acpi 53944 0 hwmon 2148 1 thinkpad_acpi Seems like it's there. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
compat c++
Hi, I was just wondering, if there is a compat c++ compiler package (or mode) available in fedora. The issue I encountered was that I got a lot of compiler errors because of strdup() malloc() etc. usages in c++ files without proper #include stuff. I am not a C++ expert, but I guess that there was a default behavior change between g++ 3 and 4. What I did was patching that package to get those #includes but as it contains a c++ code generator I also had to patch that. Although it seems to compile now, I still get zillions of "DO NOT CAST char* TO string YOU FOOL" warnings (wasn't there an option to get rid of them too?). Any kind of compat mode would make things alot easier (besides bringing the developers to write propert C++). regards christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
thinkpad and acpi events
Hi all, I encounter a little weirdness with the recent (aka 2.6.29.3-155.fc11.i586) kernel on my R61 Thinkpad: Neither Suspend on lid-shut nor reaction on power button work. It seems to me that there a no events registered by the driver. Does anyone else see that? Is there a way to log that events? regards christoph signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
