Re: Fedora-buildsys-list Digest, Vol 52, Issue 2
I just solved this problem, and I send to maillist. You can search it! 2009/6/3 lixiao-a lixia...@163.com Thanks for your help ,but I still have the problem.I copied the virtual machines to a new PC.so the yum depository still visit the old IP.So the mock buildroot init has error.How to make it visit the new IP?Could you help me? -- 网易全新推出企业邮箱 http://qiye.163.com/?ft=2 -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list -- 李建 msn lijian@gmail.com -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: When I modified the koji server'ip from one to another, the yum use the old ip already!
李建 wrote:
I've solv this probole. the /usr/sbin/kojid have following code:
--
2584 #cmd.append('--update')
2585 #if options.createrepo_skip_stat:
2586 #cmd.append('--skip-stat')
==
I commented it , so the createrepo run as follow (see createrepo.log):
It seems a little silly to comment out code that can be disabled with a
configuration option (createrepo_skip_stat). Of course, there is no
option to disable the --update.
When I need to force the system to regenerate repos from scratch I just
expire them in the db. This works because kojid will only recycle
repodata from a repo in the READY state. Anyway, to expire all current
repos, I'd use this sql command:
- update repo set state = 2 where state in (0, 1);
You'll also need to cancel any newRepo tasks that were running beforehand.
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: When I modified the koji server'ip from one to another, the yum use the old ip already!
Good,the method you give is simple.I'll test later.My repo table in sql now
is following,Did you can tell me what's mean about state=3 ? and state=1
,and state=2 ?
Thank you very much ! I have draw a koji illustrative diagram , can you give
me some advices?
http://workplace.turbolinux.com.cn/attachments/120/koji%E5%8E%9F%E7%90%86%E5%9B%BE.png
**
I've write many docs about install koji server and use koji,all is chinese.
Can I put it on koji wiki ?
https://fedoraproject.org/wiki/Talk:Koji
koji= SELECT * from repo;
id | create_event | tag_id | state
+--++---
5 | 3848 | 2 | 3
6 | 3849 | 2 | 3
8 | 3860 | 1 | 3
7 | 3857 | 2 | 3
9 | 3861 | 2 | 3
10 | 3883 | 2 | 3
11 | 3899 | 2 | 3
12 | 3901 | 2 | 3
13 | 3982 | 2 | 3
14 | 4021 | 2 | 3
15 | 4044 | 2 | 3
16 | 4073 | 2 | 3
17 | 4117 | 2 | 3
18 | 4151 | 2 | 3
19 | 4160 | 2 | 3
20 | 4162 | 2 | 3
21 | 4189 | 2 | 3
22 | 4200 | 2 | 3
23 | 4305 | 2 | 3
24 | 4382 | 2 | 3
25 | 4431 | 2 | 3
27 | 4455 | 4 | 3
28 | 4457 | 4 | 3
29 | 4463 | 4 | 3
30 | 4494 | 4 | 3
31 | 4509 | 4 | 3
32 | 4511 | 4 | 3
33 | 4521 | 4 | 3
34 | 4531 | 4 | 3
40 | 7335 | 5 | 2
41 | 7348 | 3 | 2
42 | 7349 | 5 | 2
35 | 4540 | 4 | 3
43 | 7350 | 6 | 2
45 | 7356 | 6 | 2
46 | 7369 | 6 | 2
44 | 7355 | 4 | 2
47 | 7372 | 6 | 2
48 | 7373 | 4 | 2
49 | 7376 | 6 | 2
52 | 7392 | 6 | 2
56 | 7401 | 6 | 2
50 | 7379 | 4 | 2
51 | 7386 | 2 | 1
26 | 4441 | 2 | 3
53 | 7394 | 6 | 2
54 | 7396 | 6 | 2
57 | 7405 | 6 | 2
59 | 7424 | 4 | 1
55 | 7400 | 6 | 2
36 | 7290 | 6 | 3
37 | 7292 | 6 | 3
38 | 7318 | 6 | 3
39 | 7323 | 6 | 3
58 | 7410 | 6 | 2
61 | 7443 | 6 | 1
60 | 7441 | 6 | 2
(57 rows)
2009/6/4 Mike McLean mi...@redhat.com
李建 wrote:
I've solv this probole. the /usr/sbin/kojid have following code:
--
2584 #cmd.append('--update')
2585 #if options.createrepo_skip_stat:
2586 #cmd.append('--skip-stat')
==
I commented it , so the createrepo run as follow (see createrepo.log):
It seems a little silly to comment out code that can be disabled with a
configuration option (createrepo_skip_stat). Of course, there is no option
to disable the --update.
When I need to force the system to regenerate repos from scratch I just
expire them in the db. This works because kojid will only recycle repodata
from a repo in the READY state. Anyway, to expire all current repos, I'd use
this sql command:
- update repo set state = 2 where state in (0, 1);
You'll also need to cancel any newRepo tasks that were running beforehand.
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
--
李建
msn lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On 02.06.2009 22:30, Jesse Keating wrote: On Tue, 2009-06-02 at 21:30 +0200, Thorsten Leemhuis wrote: but if we get RC with the final name transferred to the mirrors ahead of time then they can be updated relative quickly as well, as only a few bit change. We don't do this as it tends to lead to leaks, and confusion as to whether the release has been done or not. Then put it in a temporary folder that is rsynced from the mirror masters, but not exported it to the world. Later it's just a update to the file and a hardlink to a proper place. Or simply ignore that there might be leaks problem more -- the clientele that is huntin for leaks before something is announced is doing something wrong already in any case. And if the whole process from finishing to release would be a whole lot shorter then it shortens the time where something leaks. CU knurd -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
Kevin Kofler, Wed, 03 Jun 2009 01:29:35 +0200: gmane.linux.redhat.fedora.testers http://list.gmane.org/fedora-test-l...@redhat.com -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Wed, 03 Jun 2009 05:09:49 +0200, Ralf wrote: Kevin Kofler wrote: Steve Grubb wrote: I don't want to start a long thread, but just to ask a couple questions for my own clarification. Does a maintainer's responsibilities end with packaging bugs? IOW, if there is a problem in the package that is _broken code_ do they need to do something about it or is it acceptable for them to close the bug and say talk to upstream? It's the reporter's job to report the bug upstream when asked to do so. I disagree. Reporters are users - customers if you like to. Consumers. Consumers of a product. And the product (albeit developed by upstream) is offered by Fedora, as the Fedora packagers prepare and build the packages for the Fedora software environment. Added value, and as such it's normal for the packagers to stay at the front with regard to incoming problem reports. You can't expect them to do anything, nor demand them to do anything, nor force them to do anything. On the contrary, a packager at least ought to have an opinion about every Fedora bugzilla ticket that is opened for the package. An opinion about whether a problem is reproducible, whether it may be specific to Fedora, whether it can be patched for Fedora, whether it is grave enough to be in need of major rewrites in the upstream code base, whether the report is not helpful, and so on. The Fedora packager ought to be aware of what the package users think about how usable the packaged software is in the Fedora environment. That said, I consider it to be a Fedora package's maintainer's job and duty to act as moderator/arbiter/coordinator to initiate appropriate communication/interaction between all different parties (reporter, packager, upstreams) when necessary/if required. This is particularly important when upstream doesn't have a bug tracking system, when it takes weeks till months for a new upstream release, when a problem requires the user to test unofficial updates (and patches that can be derived from SCM commits) where the Fedora packager may need to assist. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Wednesday 03 June 2009 11:47:26 Jaroslav Reznik wrote: PS: I'm not saying to not report bugs to RH bugzilla, we can help then but lack of direct communication between user and developer is issue, You're assuming that all those users are engineers and technical people. That might be true atm but at least I also would like to get the 'normal people' which are now ubuntu users. back to propritetary software which is the reason why most 'normal people' use windows and among the numbers, they have the control of everything (hw support etc). I'd like to see a day that my new display adapter works out of the box. I'd like to see that day as a Fedora user/community member. Tuju -- Better to have one, and not need it, than to need one and not have it. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Tue, 2009-06-02 at 16:17 -0400, Steve Grubb wrote: I don't want to start a long thread, but just to ask a couple questions for my own clarification. Does a maintainer's responsibilities end with packaging bugs? IOW, if there is a problem in the package that is _broken code_ do they need to do something about it or is it acceptable for them to close the bug and say talk to upstream? There are _some_ kinds of bug (feature requests, etc.) which it's reasonable for any decent maintainer to punt upstream. There are other kinds of bugs (crashes, security issues -- perhaps even _anything_ that's a real bug rather than an RFE) which the maintainer really _ought_ to deal with directly. Opinions vary on precisely where the boundary between those classes should be, but I'm fairly adamant it should be 'RFE vs. bug'. Any packager who _isn't_ capable of handling the latter class of bug probably shouldn't be maintaining the package without the assistance of a co-packager or their sponsor. Note that you don't _have_ to be able to code to handle a real bug in an acceptable fashion -- decent coordination with upstream can be perfectly sufficient, if upstream are responsive enough. But just closing the bug in our bugzilla as 'upstream' is rarely acceptable for a _real_ bug, IMHO. -- David WoodhouseOpen Source Technology Centre david.woodho...@intel.com Intel Corporation -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
uClibc orphaned
Hello, I want to split uClibc from busybox package - is here a volunteer who is willing to take care about it? Ivana Hutarova Varekova -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning some packages (brasero, transmission and more)
On 06/03/2009 12:50 PM, Denis Leroy wrote: In an effort to focus more on FOSS upstream development, I am going to be orphaning some of my Fedora packages in the near future, starting with this first batch. transmission Taken this. Co-maintainers welcome. Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Miércoles 03 Junio 2009 11:52:37 Juha Tuomala escribió: On Wednesday 03 June 2009 11:47:26 Jaroslav Reznik wrote: PS: I'm not saying to not report bugs to RH bugzilla, we can help then but lack of direct communication between user and developer is issue, You're assuming that all those users are engineers and technical people. That might be true atm but at least I also would like to get the 'normal people' which are now ubuntu users. Most bugs are filled by quite technically skilled users. For average users it doesn't depend if it is RH bugzilla or upstream's bugzilla - it's too complicated for them. I know - it's another story... For these people forums are much more better. Maybe we lack some tool for users - without technical details, more collecting only tool... Some easy GUI for Abrt? New Dr. Konqui is nice but still too complicated for average users. They don't click on send bug button but OK buttons and accepting the fact of crash... back to propritetary software which is the reason why most 'normal people' use windows and among the numbers, they have the control of everything (hw support etc). But if you observe bug or have some wish - there's no chance to talk to developer... I'd like to see a day that my new display adapter works out of the box. I'd like to see that day as a Fedora user/community member. I hope that day is close because I think it's worst problem of whole OSS Desktop :( Tuju -- Better to have one, and not need it, than to need one and not have it. Jaroslav -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: F11: kernel/boot hangs at creating initial device nodes with 2.6.30-rc6
On Mon, Jun 01, 2009 at 08:15:48AM +0300, Pasi Kärkkäinen wrote: Hello. Yesterday I installed latest F11/rawhide. The default installed kernel (2.6.29 something) works fine. I compiled custom 2.6.30-rc6 kernel, and created initrd for it, and tried booting it. Booting process gets stuck at creating initial device nodes. Any ideas? I assume that's during initrd execution.. Something missing from my kernel config? Any tips would be appreciated. Has anyone else seen this problem? -- Pasi -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibility Policy
On 05/06/2008 03:54 PM, Brian Pepple wrote: On Tue, 2008-05-06 at 07:26 -0700, Toshio Kuratomi wrote: snip Brian, we probably want to list the ways to deal with bug reports in the policy as many maintainers don't realize how many options there are for getting help fixing a bug. Here's what I've got right now (from Kevin's suggestion) in the section regarding bugs: If you find yourself unable to handle the load of bugs from your package(s), please ask for assistance on the fedora-devel and/or fedora-test lists. Teaching triagers about how to triage your bugs or getting help from other maintainers can not only reduce your load, but improve Fedora. Consider reaching out for some (more) co-maintainers to assist as well. Do we want to expand on that? FYI If bugs need (Re)testing or a component needs a speedup treatment in bodhi drop a testing request to fedora-test list and/or file a request in Fedora QA trac instance on https://fedorahosted.org/fedora-qa and we will take care of it. We also assisting in any test case creation, setup test day's etc. Dont hesitate to drop a mail to the test-list or open a ticktet in Fedora QA trac instance JBG begin:vcard fn:Johann B. Gudmundsson n:Gudmundsson;Johann B. org:Reiknistofnun - University of Iceland;IT Management adr:Taeknigardi;;Dunhagi 5;Reykjavik;;107;Iceland email;internet:johan...@hi.is title:Unix System Engineer RHCE,CCSA tel;work:+3545254267 tel;fax:+3545528801 tel;pager:N/A tel;home:N/A tel;cell:N/A url:www.rhi.hi.is version:2.1 end:vcard -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning some packages (brasero, transmission and more)
On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote: In an effort to focus more on FOSS upstream development, I am going to be orphaning some of my Fedora packages in the near future, starting with this first batch. brasero (high-maintenance) Wait... didn't we just make this the default CD/DVD buring application in the Fedora spin? http://fedoraproject.org/wiki/Features/Gnome2_26 And now it's orphaned? josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
Jaroslav Reznik wrote: On Miércoles 03 Junio 2009 05:09:49 Ralf Corsepius escribió: Kevin Kofler wrote: Steve Grubb wrote: I don't want to start a long thread, but just to ask a couple questions for my own clarification. Does a maintainer's responsibilities end with packaging bugs? IOW, if there is a problem in the package that is _broken code_ do they need to do something about it or is it acceptable for them to close the bug and say talk to upstream? It's the reporter's job to report the bug upstream when asked to do so. I disagree. Reporters are users - customers if you like to. You can't expect them to do anything, nor demand them to do anything, nor force them to do anything. We are not forcing anyone to do anything but we think direct communication between user and developer is much more better I consider maintainers redirecting arbitrary reporters to upstreams to be rude and hostile, because they are presuming the reporter to be * interested in tracking down bugs * interested in getting involved into upstreams * technically able to do so. This occasionally applies to developers - To normal users it usally doesn't apply, they want to have their issue fixed. Ralf -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning some packages (brasero, transmission and more)
Rahul Sundaram wrote: On 06/03/2009 05:18 PM, Josh Boyer wrote: On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote: In an effort to focus more on FOSS upstream development, I am going to be orphaning some of my Fedora packages in the near future, starting with this first batch. brasero (high-maintenance) Wait... didn't we just make this the default CD/DVD buring application in the Fedora spin? http://fedoraproject.org/wiki/Features/Gnome2_26 And now it's orphaned? Yep. Bad timing. Somebody should pick it up. Rahul Xavier Lamien said he'd pick it up, which I assume he'll do after Denis orphans it in pkgdb. -J -- in your fear, speak only peace in your fear, seek only love -d. bowie -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Tuesday 02 June 2009 07:34:17 pm Kevin Kofler wrote: Steve Grubb wrote: I don't want to start a long thread, but just to ask a couple questions for my own clarification. Does a maintainer's responsibilities end with packaging bugs? IOW, if there is a problem in the package that is _broken code_ do they need to do something about it or is it acceptable for them to close the bug and say talk to upstream? It's the reporter's job to report the bug upstream when asked to do so. And then should the bug be closed hoping that one day you pull in a package that solves the user's problem? Fixing bugs often requires two-way communication, so it's important for upstream to have a real reporter to talk to, I don't see why it should be the maintainer's job to play the relaying monkey. Its real simple. In reporting the bug, people are asked how to reproduce the bug. If its reproducible by the maintainer, the user is no longer required to solve the problem and all you need to do is ask them to do a retest. If the bug is not reproducible, then things do get a little trickier. I would still take the bug report to upstream and see if it rings any bells, but I would not close the bug. -Steve -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Tuesday 02 June 2009 11:09:49 pm Ralf Corsepius wrote: Kevin Kofler wrote: Steve Grubb wrote: I don't want to start a long thread, but just to ask a couple questions for my own clarification. Does a maintainer's responsibilities end with packaging bugs? IOW, if there is a problem in the package that is _broken code_ do they need to do something about it or is it acceptable for them to close the bug and say talk to upstream? It's the reporter's job to report the bug upstream when asked to do so. I disagree. Reporters are users - customers if you like to. You can't expect them to do anything, nor demand them to do anything, nor force them to do anything. That said, I consider it to be a Fedora package's maintainer's job and duty to act as moderator/arbiter/coordinator to initiate appropriate communication/interaction between all different parties (reporter, packager, upstreams) when necessary/if required. For the record, I agree with this sentiment. If there's a bug in my packages, I want to fix it and not cause the reporter to have to get upstream bz accounts or join upstream mail lists just because they reported a problem. I will interact with the reporter until I see the problem myself. And then I can fix it or show upstream the problem. Thanks everybody for the opinions. I just wanted to raise awareness on this topic. -Steve -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On Tue, Jun 02, 2009 at 08:15:32PM -0400, Josh Boyer wrote: We are facing some real limitations on our turn around time for things at the moment and they are only going to get worse as we have newer releases that will get the delta rpms. At the same time, the same people are getting raked over the coals for not getting bits out fast enough. We are working on this from a rel-eng standpoint, but advocating for a bit of discretion on what should be pushed as an update is not entirely a bad thing. Personally, I would love it if package maintainers slowed down a bit. But it's not an end solution. So certainly the leadership, defined as FESCo and FPB, is not in conflict with the contributor's apparent direction. As far as I can see, they haven't made a statement either way. If there is a group that was pushing for something that ran contrary, it was Rel-Eng. And given that Jesse and I both just said we're going to basically stop begging people to slow down on updates, I think even that group is trying to figure out a way to make things better. Hell, that's partly what this FAD is all about. If the FAD identifies some tangibles (hardware, etc.) that would help alleviate some of the time problems, I can tell you that Spot and I will do our best to procure them. From what I've heard others describe up until now, it doesn't seem like there's one clear roadblock in that regard -- just a huge mountain of tasks that our current systems have to chug through for composing, and no matter how you slice it, it takes a lot of time and I/O bandwidth. -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Wed, 03 Jun 2009 14:06:45 +0200, Ralf wrote: I consider users (esp. bug reporters) not to be the dumb pigs eating the hog wash they get for free, or clueless comsumer masses aborbing anything they don't pay for with money, but them to be the foundation of your work and them to be valuable business partners, paying in immaterial payment (e.g. feedback, such as bug reports). That's an idealistic [over-simplified] point of view which I don't want to agree with. There is no clear relationship, such as a seller and a purchaser (and the customer is king guideline doesn't apply), since the person who produces the packages may be the one to _give_ more than he _gets_ in return by the users. Or vice versa. All that's clear to me is that the packager fills the role of a provider, providing packaging services, and certain feedback from some package users may help with improving the quality of the provided product. In turn the provider ought to have interest in such an improvement and in boosting the relationship with the package users. Preferably, users with strong interest in a particular Fedora package sign up at the Fedora Account System, so they can subscribe to a package's watchbugzilla and watchcommit channels. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On Wed, Jun 03, 2009 at 08:55:48AM -0400, Paul W. Frields wrote: On Tue, Jun 02, 2009 at 08:15:32PM -0400, Josh Boyer wrote: We are facing some real limitations on our turn around time for things at the moment and they are only going to get worse as we have newer releases that will get the delta rpms. At the same time, the same people are getting raked over the coals for not getting bits out fast enough. We are working on this from a rel-eng standpoint, but advocating for a bit of discretion on what should be pushed as an update is not entirely a bad thing. Personally, I would love it if package maintainers slowed down a bit. But it's not an end solution. So certainly the leadership, defined as FESCo and FPB, is not in conflict with the contributor's apparent direction. As far as I can see, they haven't made a statement either way. If there is a group that was pushing for something that ran contrary, it was Rel-Eng. And given that Jesse and I both just said we're going to basically stop begging people to slow down on updates, I think even that group is trying to figure out a way to make things better. Hell, that's partly what this FAD is all about. If the FAD identifies some tangibles (hardware, etc.) that would help alleviate some of the time problems, I can tell you that Spot and I will do our best to procure them. From what I've heard others describe up until now, it doesn't seem like there's one clear roadblock in that regard -- just a huge mountain of tasks that our current systems have to chug through for composing, and no matter how you slice it, it takes a lot of time and I/O bandwidth. Yep. As a simple test, We'd like to do some experiments to see if running updates pushes and rawhide composes on separate boxen makes things worse or better or about the same. I don't think we need additional procured hardware for that, just a cloned guest which I already have a ticket opened for. Oh, and time. Always need time. If you or spot could procure time, let me know ;) josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
Michael Schwendt wrote: On Wed, 03 Jun 2009 14:06:45 +0200, Ralf wrote: I consider users (esp. bug reporters) not to be the dumb pigs eating the hog wash they get for free, or clueless comsumer masses aborbing anything they don't pay for with money, but them to be the foundation of your work and them to be valuable business partners, paying in immaterial payment (e.g. feedback, such as bug reports). That's an idealistic [over-simplified] point of view which I don't want to agree with. Well, whether it's idealistic or not is irrelevant. It's one of the foundations of open source. Or less abstract: I stopped reporting bugs against Fedora's evolution, because its @RH maintainer preferred to close bugs and tried to push me around to upstream. Wrt. evolution, I was an ordinary user and am not interested in getting further involved. As simple as it is: I felt sufficiently pissed of by this guy to leave him and his upstream alone, ... so be it, he wanted it this way. There are other packages and packagers (noteworthy many of the @RH) who exhibit the same push reporters around behavior. So is still anybody wondering why Fedora is permanently lacking people? This is one cause. Now combine this with the report bugs phrases certain people tend to reiterate? ... Experiences, such as the one I encountered with the evolution maintainer, are the cause why at least some people sense a foul taste when listening to them. Ralf -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning some packages (brasero, transmission and more)
On Wed, 2009-06-03 at 14:16 +0200, Denis Leroy wrote: On 06/03/2009 01:48 PM, Josh Boyer wrote: On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote: In an effort to focus more on FOSS upstream development, I am going to be orphaning some of my Fedora packages in the near future, starting with this first batch. brasero (high-maintenance) Wait... didn't we just make this the default CD/DVD buring application in the Fedora spin? http://fedoraproject.org/wiki/Features/Gnome2_26 And now it's orphaned? I merely want to transfer ownership to somebody new. Matthias Clasen and Bastien Nocera are already acting co-maintainers, and so I'm waiting to hear from them before transferring ownership, in case one of them has a strong desire to take over the package... I don't have a strong desire to own any package... but if nobody else picks it up, I will find an owner for it. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Tuesday 02 June 2009 06:17:02 pm Steven M. Parrish wrote: This is from the official Bugzappers page https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses#Upstreamin So, this raises the question about bugzappers. Should they be making the determination for maintainers that the reporter should have taken the issue upstream? Do bug zappers take into consideration the severity of the bug before pushing someone upstream? The bug is not a packaging bug, the package maintainer has no plans to work on this in the near future, and there is an upstream bug tracking system other than the Red Hat Bugzilla. Is there communication between maintainer and bugzapper before doing this? Maintainers should be free to either fix it locally (time permitting) and upstream the patch or request that the bug be filed at the upstream projects tracker for the upstream developers to resolve it. If it is sent upstream the bug is closed as UPSTREAM and our local report is cross-referenced to the upstream one. That way the maintainer and all interested parties can follow its progress. Not if its closed. How would I be notified that the fix is in Fedora? If the bug is severe enough, shouldn't the upstream commit be applied to Fedora's package and the package pushed out for testing? Is all this going to happen if the bug is closed? -Steve -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: welcome to fedora
Muayyad AlSadi wrote: maybe a trivial pygtk script ? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list +1 I was just about to suggest that. And, if alot of the text items are not embedded directly (i.e. loaded from /usr/share/welcome/ or something) they can be made multi-lingual, changed easily on each release, and even changed by re-spins. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning some packages (brasero, transmission and more)
Matthias Clasen wrote: On Wed, 2009-06-03 at 14:16 +0200, Denis Leroy wrote: On 06/03/2009 01:48 PM, Josh Boyer wrote: On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote: In an effort to focus more on FOSS upstream development, I am going to be orphaning some of my Fedora packages in the near future, starting with this first batch. brasero (high-maintenance) Wait... didn't we just make this the default CD/DVD buring application in the Fedora spin? http://fedoraproject.org/wiki/Features/Gnome2_26 And now it's orphaned? I merely want to transfer ownership to somebody new. Matthias Clasen and Bastien Nocera are already acting co-maintainers, and so I'm waiting to hear from them before transferring ownership, in case one of them has a strong desire to take over the package... I don't have a strong desire to own any package... but if nobody else picks it up, I will find an owner for it. See my previous message re Xavier Lamien . . . -- in your fear, speak only peace in your fear, seek only love -d. bowie -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Fedora 11 Test Day survey
Greetings, The Fedora QA team would like your feedback on Fedora 11 Test Days. You may have seen Adam Williamson's planet post [1] kicking off Fedora 12 Test Day planning. We're interested in identifying areas for improvement to increase participation and improve effectiveness. Please take 10-15 minutes to answer any/all of the questions below. You may reply to the mailing list, or send feedback directly to me. Your responses to this survey are instrumental in making Fedora 12 Test Days successful. Many thanks to Chris Ward for his help in getting things moving with the survey questions! === 1. How did you find out about Fedora Test Days? 2. Was sufficient documentation available to help you participate in a Fedora Test Day? If not, what did you find missing or in need of improvement? 3. Did you encounter any obstacles preventing participation in Fedora test Days? How might they have been avoided? Did you discover any workaround? 4. Were you able to locate and download installation media for testing? Did it function as expected? 5. What follow-up actions do you expect after the Test Day? Are your expectations currently being met? 6. Would you participate again in future Fedora Test Days? 7. Do you have any more general comments or any suggestions for improving future test days? === Thanks, James [1] http://www.happyassassin.net/2009/06/02/whats-goin-on-f12-test-days/ signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaning some packages (brasero, transmission and more)
On 06/03/2009 03:55 PM, Matthias Clasen wrote: On Wed, 2009-06-03 at 14:16 +0200, Denis Leroy wrote: On 06/03/2009 01:48 PM, Josh Boyer wrote: On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote: In an effort to focus more on FOSS upstream development, I am going to be orphaning some of my Fedora packages in the near future, starting with this first batch. brasero (high-maintenance) Wait... didn't we just make this the default CD/DVD buring application in the Fedora spin? http://fedoraproject.org/wiki/Features/Gnome2_26 And now it's orphaned? I merely want to transfer ownership to somebody new. Matthias Clasen and Bastien Nocera are already acting co-maintainers, and so I'm waiting to hear from them before transferring ownership, in case one of them has a strong desire to take over the package... I don't have a strong desire to own any package... but if nobody else picks it up, I will find an owner for it. I've released ownership. Xavier is the new owner. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 11 Test Day survey
On Wed, Jun 3, 2009 at 9:10 AM, James Laska jla...@redhat.com wrote: Greetings, The Fedora QA team would like your feedback on Fedora 11 Test Days. You may have seen Adam Williamson's planet post [1] kicking off Fedora 12 Test Day planning. We're interested in identifying areas for improvement to increase participation and improve effectiveness. Please take 10-15 minutes to answer any/all of the questions below. You may reply to the mailing list, or send feedback directly to me. Your responses to this survey are instrumental in making Fedora 12 Test Days successful. Many thanks to Chris Ward for his help in getting things moving with the survey questions! === 1. How did you find out about Fedora Test Days? 2. Was sufficient documentation available to help you participate in a Fedora Test Day? If not, what did you find missing or in need of improvement? 3. Did you encounter any obstacles preventing participation in Fedora test Days? How might they have been avoided? Did you discover any workaround? 4. Were you able to locate and download installation media for testing? Did it function as expected? 5. What follow-up actions do you expect after the Test Day? Are your expectations currently being met? 6. Would you participate again in future Fedora Test Days? 7. Do you have any more general comments or any suggestions for improving future test days? === Thanks, James [1] http://www.happyassassin.net/2009/06/02/whats-goin-on-f12-test-days/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list I'll answer these in order. 1. I got lucky when I looked in the mailing list. 2. Yes there was good enough docs for the test days to help me participate. 3. My biggest obstacle with test days was that they were not planned early enough. Most of the test days seemed to be planned less than 48 hours ahead of time. If test days were planned better, I could actually participate more. 4. Yes, I was able to download them. No, the media didn't work. It generally hung the computer, but that's not the fault of the test days. 5. I would expect a recap of the testing efforts so that Fedora people could analyze what the issues were, track them, and fix them. I suppose they are. The mailing list enabled them to do this, but there was no formal method of doing it. 6. If they were planned better, then maybe I would be able to set aside time to do them. I would like to participate in future Test Days. 7. Set up a reporting center just for Test Day feedback. Using the wiki is definitely not good enough. Additionally, Do not limit the test days to people subscribed to the mailing list. Take a page from Mozilla's books and announce those test days to the world. Unfortunately, to do that, test days need to be planned better. Hopefully this feedback helps :) -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Wed, Jun 3, 2009 at 06:46, Ralf Corsepius rc040...@freenet.de wrote: Michael Schwendt wrote: On Wed, 03 Jun 2009 14:06:45 +0200, Ralf wrote: I consider users (esp. bug reporters) not to be the dumb pigs eating the hog wash they get for free, or clueless comsumer masses aborbing anything they don't pay for with money, but them to be the foundation of your work and them to be valuable business partners, paying in immaterial payment (e.g. feedback, such as bug reports). That's an idealistic [over-simplified] point of view which I don't want to agree with. Well, whether it's idealistic or not is irrelevant. It's one of the foundations of open source. Or less abstract: I stopped reporting bugs against Fedora's evolution, because its @RH maintainer preferred to close bugs and tried to push me around to upstream. Wrt. evolution, I was an ordinary user and am not interested in getting further involved. As simple as it is: I felt sufficiently pissed of by this guy to leave him and his upstream alone, ... so be it, he wanted it this way. There are other packages and packagers (noteworthy many of the @RH) who exhibit the same push reporters around behavior. So is still anybody wondering why Fedora is permanently lacking people? This is one cause. Now combine this with the report bugs phrases certain people tend to reiterate? ... Experiences, such as the one I encountered with the evolution maintainer, are the cause why at least some people sense a foul taste when listening to them. As a bug reported I've come to peace with the concept that maintainers and upstream have personalities too. Sometimes people are happy to see bug reports, sometimes they ignore them and sometimes they seem to go out of their way to be unhelpful. For the same reason it can be difficult to report bugs since different packages can have wide variations in the amount of information they want you to collect, and strange incantations and commands you've never seen before. (Often of the gee I never knew that was even possible variety). The ones that get to me are 1) Bugs return over and over again with each new latest and greatest version or rewrite of previously working code. A few years ago it was USB devices that would mount one day on the desktop, then not mount, then mount, etc. Today it might be screen display powers off (or doesn't), battery level is correct (or reports battery-critical), sound works (or doesn't), compiz works (or doesn't), boot with graphic boot (or nomodeset yet again). 2) Bugs that get no attention, not even an acknowledgement. 3) Bugs where the maintainer (or triager) seems to go out of their way to be completely unhelpful. I think it is easy to forget how difficult and time-consuming it can be to produce a really good bug report. I'd say that 9 out of 10 bugs that I report leave me feeling that the not much was accomplished. It is that tenth bug report, the one where there is a reasonable interaction, where a problem gets resolved (and doesn't seem to reappear) that keeps me doing them. darrell -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 11 Test Day survey
James Laska wrote: 1. How did you find out about Fedora Test Days? Mailing list posting. 2. Was sufficient documentation available to help you participate in a Fedora Test Day? If not, what did you find missing or in need of improvement? Yes, I found everything I needed on the corresponding wiki page. 3. Did you encounter any obstacles preventing participation in Fedora test Days? How might they have been avoided? Did you discover any workaround? Time. Test days are sometimes not announced early enough for me, or I do not have them marked on my calendar so I forget about them. 4. Were you able to locate and download installation media for testing? Did it function as expected? Yes. Yes. 5. What follow-up actions do you expect after the Test Day? Are your expectations currently being met? I expected an analysis of the data received either by a mailing list post or an update on the wiki page. I saw neither and thought my data was just thrown into the wind. My expectations were not met. 6. Would you participate again in future Fedora Test Days? Yes. 7. Do you have any more general comments or any suggestions for improving future test days? Please get the Fedora calendar server going. I'd love to subscribe Thunderbird/Lightning to the QA calendar. People would be able to know about and participate in test days (or any QA event) without a mailing list subscription or a 24/7 IRC connection as it seems some things are discussed solely on IRC. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
rawhide report: 20090603 changes
Compose started at Wed Jun 3 06:15:03 UTC 2009 Updated Packages: anaconda-11.5.0.59-1.fc11 - * Tue Jun 02 2009 Chris Lumens clum...@redhat.com - 11.5.0.59-1 - Do not show disabled repos such as rawhide during the install (#503798). (jkeating) Summary: Added Packages: 0 Removed Packages: 0 Modified Packages: 1 Broken deps for ppc64 -- cabal2spec-0.12-1.fc11.noarch requires ghc 0:6.10.1-7 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On 06/03/2009 02:38 PM, Tom spot Callaway wrote: On 06/03/2009 09:01 AM, Josh Boyer wrote: Oh, and time. Always need time. If you or spot could procure time, let me know ;) Man, if I knew how to do that, I'd be a lot wealthier than I am now. ;) Extend the day to 36 hours Gosh feel like a millionaire already Sleep is overrated anyway. :) Johann who get's enough sleep when he's dead Gudmundsson begin:vcard fn:Johann B. Gudmundsson n:Gudmundsson;Johann B. org:Reiknistofnun - University of Iceland;IT Management adr:Taeknigardi;;Dunhagi 5;Reykjavik;;107;Iceland email;internet:johan...@hi.is title:Unix System Engineer RHCE,CCSA tel;work:+3545254267 tel;fax:+3545528801 tel;pager:N/A tel;home:N/A tel;cell:N/A url:www.rhi.hi.is version:2.1 end:vcard -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 11 Test Day survey
Thanks for the feedback! On Wed, 2009-06-03 at 20:16 +0530, Rahul Sundaram wrote: 5. What follow-up actions do you expect after the Test Day? Are your expectations currently being met? Yes. Although I was hoping there would be a test day for Ext4. I was too, but there were some schedule conflicts which kept it from happening on the QA side. In the end the only test day topic with focus on ext4 was around changing the anaconda default filesystem to ext4 (https://fedoraproject.org/wiki/QA/Test_Days/2009-02-05). Thanks, James signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: chkrootkit looking for new maintainer
Michael Schwendt wrote: I'm looking for somebody to become the chkrootkit package owner, preferably not anyone who just wants to increase the list of owned packages for some doubtful metrics. There are no open tickets for chkrootkit in Fedora. Last upstream release has been in Dec 2007. Upstream has been responsive, but not reliable with regard to merging non-Fedora-specific patches. I use it, and will take it if the co-maintainer isn't interested. -- in your fear, speak only peace in your fear, seek only love -d. bowie -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Orphaning Packages: audacious and dependencies
Hi. As I don't have the time to maintain audacious any more I'm orphaning the following packages: audacious audacious-plugins libmowgli mcs The last two are dependencies which, as far as I am aware, are used by nothing else. There is an accompanying package in the Voldemort Repository which contains the less free and more useful media codecs. That would be up for grabs, too, preferrably by the same person. There are several bugs open against the package, most of which will probably be fixed by the current upstream release. -- 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: Announcing Fedora Activity Day - Fedora Development Cycle 2009
It might have helped to find the problem earlier -- I for example got the impression that a lot of people had problems with the storage rewrite and thus aborted their tests with Alpha or Beta. There was no storage rewrite in the Alpha, so this isn't the case there. For the beta, you are correct. - Chris -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 11 Test Day survey
James Laska wrote: 1. How did you find out about Fedora Test Days? fedora-devel-announce 2. Was sufficient documentation available to help you participate in a Fedora Test Day? If not, what did you find missing or in need of improvement? The instructions were sufficient. 3. Did you encounter any obstacles preventing participation in Fedora test Days? How might they have been avoided? Did you discover any workaround? I found out about the Intel graphics test day too late to be able to participate on the right day. I first had to create a FAS account as I hadn't yet taken all the steps to become a packager. I got side-tracked by an incorrect error message in FAS and had some problems before I could report that. Then I had to create a Smolt profile. SmoltGUI crashed but I could work around the crash by changing the locale. Smolt using two kinds of UUIDs caused some confusion. I could eventually go through the test cases for Intel graphics a week after the actual test day. See also the next question: 4. Were you able to locate and download installation media for testing? Did it function as expected? Live CD images were linked from the wiki pages. I had no problems downloading them. I eventually managed to make a working live USB stick from the one for the Intel test day, after I transferred it to my work computer where I had Fedora 10 and could install the latest Syslinux from Rawhide. It wasn't possible to do this on Fedora 9. The live USB stick I made from the CD image for the Nvidia test day was more dead than live. It wouldn't boot, so I couldn't participate in that test day. 5. What follow-up actions do you expect after the Test Day? Are your expectations currently being met? I expected that someone would attempt to fix the bugs I reported. No such attempts have been mentioned in Bugzilla so far. I suppose I'll se whether they've been fixed when I upgrade to Fedora 11. Perhaps there would have been more interest in my reports if I had submitted them during the actual test day. 6. Would you participate again in future Fedora Test Days? If they cover some functionality that's particularly important to me or some less than common hardware that I have. Björn Persson signature.asc Description: This is a digitally signed message part. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
Jesse Keating (jkeat...@redhat.com) said: On Wed, 2009-06-03 at 13:49 -0400, Seth Vidal wrote: And the optimization there is fairly well known. We need to read in and not change the prestodelta file. It's on my short-ish createrepo list. Hrm, bill thought it was something on the mash side, where he validates the signature of all the existing deltas to catch if a gpg sig changed without a n-v-r bump. I haven't characterized that that is *definitely* what's causing pain, but it's a likely source. It's also a hard one to optimize unless you decree that packages will never change signatures, which doesn't seem practical. Bill -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On Wed, 3 Jun 2009, Bill Nottingham wrote: Jesse Keating (jkeat...@redhat.com) said: On Wed, 2009-06-03 at 13:49 -0400, Seth Vidal wrote: And the optimization there is fairly well known. We need to read in and not change the prestodelta file. It's on my short-ish createrepo list. Hrm, bill thought it was something on the mash side, where he validates the signature of all the existing deltas to catch if a gpg sig changed without a n-v-r bump. I haven't characterized that that is *definitely* what's causing pain, but it's a likely source. It's also a hard one to optimize unless you decree that packages will never change signatures, which doesn't seem practical. We could always go to detached signatures or auto-pkg signatures and then only manually sign the repomd's. -sv -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: (Most) Results from the Candidate Questionnaire are available now
Thorsten Leemhuis (fed...@leemhuis.info) said: The answers are quite interesting and as far as I can see can be quite helpful to decide whom to (not) vote for. So if you plan to vote in the elections I'd suggest you go and read the answers! Thanks for doing this! Bill -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
Juha Tuomala wrote: I agree. Demanding them to take any responsibility on that report, even testing it again makes them just think twice next time to report anything. [snip] Exactly. If the reporter wants to take part to that communication, good. But that should not expected. More reports is better than more active reporters, those latter ones wont disapper anywhere anyway. The reporter is the one who wants the bug fixed, it's them asking us to do something, they need to do their part. If you aren't willing to do anything to help us fix your bug, you'll just have to live with it forever. Reports aren't of much use if the reporter doesn't want to provide us with the necessary details, doesn't even bother checking whether the bug isn't already fixed when asked (If we can't reproduce the issue, how else are we to know whether it's fixed or whether we just don't have enough information on how to reproduce it?) and/or refuses to report the issue to the people who're actually able to fix it. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 11 Test Day survey
1. How did you find out about Fedora Test Days? Planet.fp.o 2. Was sufficient documentation available to help you participate in a Fedora Test Day? If not, what did you find missing or in need of improvement? Documentation was excellent. 3. Did you encounter any obstacles preventing participation in Fedora test Days? How might they have been avoided? Did you discover any workaround? None - only took part on the nouveau day though. 4. Were you able to locate and download installation media for testing? Did it function as expected? Yes. 5. What follow-up actions do you expect after the Test Day? Are your expectations currently being met? Bugs fixed. Possibly a summary of how the previous test day helped before talking about the next one? 6. Would you participate again in future Fedora Test Days? Yes, dependent on barrier to entry. 7. Do you have any more general comments or any suggestions for improving future test days? Just that I'm very glad they're happening. Well done. -- Christopher Brown -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
I agree. Demanding them to take any responsibility on that report, even testing it again makes them just think twice next time to report anything. [snip] Exactly. If the reporter wants to take part to that communication, good. But that should not expected. More reports is better than more active reporters, those latter ones wont disapper anywhere anyway. The reporter is the one who wants the bug fixed, it's them asking us to do something, they need to do their part. If you aren't willing to do anything to help us fix your bug, you'll just have to live with it forever. So as a package maintainer, you don't want a bug in a software you maintain to be fixed ? -- Mathieu Bridon (bochecha) -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
Steve Grubb wrote: For the record, I agree with this sentiment. If there's a bug in my packages, I want to fix it and not cause the reporter to have to get upstream bz accounts or join upstream mail lists just because they reported a problem. I will interact with the reporter until I see the problem myself. And then I can fix it or show upstream the problem. Maybe you package only stuff you're intimately familiar with from top to bottom and you get only very few bug reports. But in KDE, we get dozens of bug reports and it's a huge codebase. While most of the bugs are probably such that I could fix any of them on its own, there's no way I can fix all of them by myself (and even considering all the KDE SIG folks, we still don't have enough time to fix everything ourselves), nor would my fix necessarily be good enough to be accepted upstream (sometimes a good fix needs significant code changes which only the upstream maintainer of the affected code base is really qualified to do, and that's usually not a Fedora developer). So I think you're getting a better deal by us insisting on having the bugs handled upstream. I guess other codebases where bugs are expected to be filed upstream (e.g. Evolution, which was also brought up in this thread) are similar. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
Juha Tuomala wrote: Would to make the report then if she says 'no'? :) We'll just close it as INSUFFICIENT_DATA as with any other ignored needinfo request. To get the bug fixed, they need to report it to the proper place. It's a fact that knowledge increases when you move steps to upstream. Uh no, they request the exact same information we do. If you can't provide enough information for upstream, your bug report is just as incomplete and useless for us as it is for them. If a packager don't have time to do that stuff, he would probably need a co-maintainer(s) or less packages. So do you volunteer to be the bug forwarding monkey for KDE SIG? Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Wed, 2009-06-03 at 22:43 +0200, Emmanuel Seyman wrote: * Mathieu Bridon (bochecha) [03/06/2009 22:41] : So as a package maintainer, you don't want a bug in a software you maintain to be fixed ? Not everyone agrees on what is a bug. That's a feature ;) P.Yves -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: (Most) Results from the Candidate Questionnaire are available now
On 06/03/2009 04:55 PM, Josh Boyer wrote: On Wed, Jun 03, 2009 at 04:24:16PM -0400, Bill Nottingham wrote: Thorsten Leemhuis (fed...@leemhuis.info) said: The answers are quite interesting and as far as I can see can be quite helpful to decide whom to (not) vote for. So if you plan to vote in the elections I'd suggest you go and read the answers! Thanks for doing this! Agreed, thanks. I'd like to add that if anyone want's follow ups to answers, feel free to email the candidates too! A great big me too here. Also, if anyone isn't able to attend the townhall meetings, I'd be happy to answer any questions sent to me via email. Thanks, ~spot -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On Mon, Jun 01, 2009 at 06:45:07PM -0400, Tom spot Callaway wrote: On 06/01/2009 06:45 PM, Jesse Keating wrote: If we had I2 in PHX this would get a lot faster. We just need to hold some classes and get the PHX datacenter certified as a University. ;) Not necessarily. I don't see why the Fedora Project couldn't qualify as a Sponsored Participant on Internet2 [1]. In fact, Red Hat is already connected in Raleigh. I'd gladly help pursue this, but I may not be the right person seeing as I'm in Boston, not PHX. I2 also has a private lambda service where you can get your own dedicated 10Gig wavelength across the backbone [2]. It seems they are currently offering no-fee trials of this service to I2 connectors. Arizona State University is already on I2 via CENIC, and CENIC offers this Dynamic Circuit capability. MCNC in Durham where Red Hat is connected doesn't appear to have DCN though. [1] http://www.internet2.edu/network/participants/ Sponsored participants are individual educational institutions (including not-for-profit and for-profit K-20, technical, and trade schools), museums, art galleries, libraries, hospitals, as well as other non-educational, not-for-profit or for-profit organizations that require routine collaboration on instructional, clinical, and/or research projects, services, and content with Primary participants or with other Sponsored Participants. Such organizations typically are either not eligible or not able to become Internet2 members. [2] http://www.internet2.edu/network/dc/ To support the development, deployment, and use of innovative hybrid optical networking capabilities, Internet2 is initiating a no-fee trial of the Internet2 DCN. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: (Most) Results from the Candidate Questionnaire are available now
On Wed June 3 2009, Thorsten Leemhuis wrote: I had planed to put them in the wiki as a table was well, but ran out of time, sorry (²). I tried to add such a table[0], but I failed to enable the horizotnal scrollbar. I even enabled javascript for the wiki, but it still does not work. Is this somehow broken in our mediawiki CSS setup? I noticed the css files contain overflow:hidden in several places. Regards Till [0] https://fedoraproject.org/wiki/Elections/Questionnaire#Answers_Wiki_Table signature.asc Description: This is a digitally signed message part. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
Steven M. Parrish wrote: Many people have mentioned that it is not right to ask the users to file their bug reports upstream. I ask why not? Let me summarize what I already wrote elsewhere in this thread: * Users aren't necessarily developers. * Users aren't necessarily interested in getting involved upstream. * Users are reporting bugs against your product (your package in Fedora), not against upstream's work (somebody else's product). Let me try an analogy: How do you handle defects/malfunctions with your car? You'll visit your car dealer/a garage and report the issue to them. You'll expect them to identify the problem and to take appropriate steps to solve your issue. You don't expect them to direct you to the car's manufacturer or a component manufacturer and to discuss technical details you have no knowledge about with them (Is the stuttering engine cause by triac 7 in a component A you haven't heard about before or by the hall sensor in component B you also haven't heard about before). Obviously by reporting the issue to us they feel it is important and needs to be addressed. The took the time to open a RH bugzilla account to file the report, so I don't see why they can't take 60 seconds and open an upstream account as well. Here, my answer is: They are using Fedora/participating in Fedora and therefore have RH bugzilla account. They are not participating in these upstream projects. Ralf -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
On Wednesday 03 June 2009 10:23:05 pm Ralf Corsepius wrote: Let me try an analogy: How do you handle defects/malfunctions with your car? Did a bunch of hobbyists from around the world build your car by communicating over the internet? If so, I think it would be safer to stop driving immediately (EBADMETAPHOR). Regards, -- Conrad Meyer ceme...@u.washington.edu -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Are you using LXDE?
On Tue, Jun 02, 2009 at 08:27:09PM -0400, John Aldrich wrote: I don't HAVE an xorg.conf. How does one configure Fedora 10 to use the nouveau driver if one does not have an xorg.conf? I know that the old way used to be to hand-edit the xorg.conf, but since that doesn't exist any more, I'm at a loss for how to fix this. I know that it's installed as when I tried to install it earlier yum said it was already installed. sudo yum install system-config-display and then run system-config-display. it will create a new xorg.conf file. or you can just run nvidia-xconfig if you have kmod package. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Two monitors, modelines, xorg.conf, and all that...
I have a laptop whose widescreen LVDS reports these modelines (correctly, afaik): (II) intel(0): Modeline 1280x800x59.8 83.50 1280 1352 1480 1680 800 803 809 831 -hsync -vsync (49.7 kHz) (II) intel(0): Modeline 1024x768x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) intel(0): Modeline 800x600x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) intel(0): Modeline 640x480x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) I also have a widescreen VGA monitor, reporting these: (II) intel(0): Modeline 1680x1050x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz) (II) intel(0): Modeline 1680x1050x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz) (II) intel(0): Modeline 1400x1050x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz) (II) intel(0): Modeline 1280x1024x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz) (II) intel(0): Modeline 1280x1024x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz) (II) intel(0): Modeline 1440x900x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz) (II) intel(0): Modeline 1440x900x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz) (II) intel(0): Modeline 1280x960x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz) (II) intel(0): Modeline 1152x864x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz) (II) intel(0): Modeline 1024x768x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz) (II) intel(0): Modeline 1024x768x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz) (II) intel(0): Modeline 1024x768x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) intel(0): Modeline 832x624x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz) (II) intel(0): Modeline 800x600x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz) (II) intel(0): Modeline 800x600x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz) (II) intel(0): Modeline 800x600x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) intel(0): Modeline 800x600x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz) (II) intel(0): Modeline 640x480x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (II) intel(0): Modeline 640x480x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz) (II) intel(0): Modeline 640x480x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (II) intel(0): Modeline 640x480x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (II) intel(0): Modeline 720x400x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz) When I plug in the VGA, X chooses the highest common resolution, which happens to be 1024x768. I can only ponder as to why a 22 VGA monitor does not want to do 1280x800, but that's not the question. What I would like to have is the following setup: * when VGA is not plugged in, LVDS should be up with its native resolution (1280x800) * when VGA is plugged in, LVDS should be off, while VGA in its native resolution (1680x1050) It would be nice to have this hot-pluggable, but I don't mind restarting X or the computer for the change. Can anybody tell me how to configure xorg.conf to make this happen? My current xorg.conf is fairly simple so far: Section ServerLayout Identifier X.org Configured Screen Screen0 EndSection Section Device Option AccelMethod XAA Identifier Card0 Driver intel VendorName Intel Corporation BoardName Mobile GM965/GL960 Integrated Graphics Controller BusID PCI:0:2:0 EndSection Section Screen Identifier Screen0 Device Card0 EndSection The AccelMethod is set to XAA because of that famous intel random lockup thing (it doesn't eliminate the bug, just makes it more rare), everything else is autoconfigured. Thanks, :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Are you using LXDE?
2009/6/3 kira.lau...@gmail.com: On Tue, Jun 02, 2009 at 08:27:09PM -0400, John Aldrich wrote: I don't HAVE an xorg.conf. How does one configure Fedora 10 to use the nouveau driver if one does not have an xorg.conf? I know that the old way used to be to hand-edit the xorg.conf, but since that doesn't exist any more, I'm at a loss for how to fix this. I know that it's installed as when I tried to install it earlier yum said it was already installed. sudo yum install system-config-display and then run system-config-display. it will create a new xorg.conf file. or you can just run nvidia-xconfig if you have kmod package. Slight correction: to run nvidia-xconfig you need the xorg-x11-drv-nvidia package installed. -- Sam -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ibssl.so.7 ?!
On Tue, 2009-06-02 at 22:10 -0300, Germán Racca wrote: On Tue, 2009-06-02 at 21:53 -0300, Martín Marqués wrote: Germán, the problem is that preupgrade leaves out a bunch of kde apps: Checking for new repos for mirrors * preupgrade: fedora.c3sl.ufpr.br 6:kdelibs-4.2.3-2.fc10.x86_64 from installed has depsolving problems -- Missing Dependency: libssl.so.7()(64bit) is needed by package 6:kdelibs-4.2.3-2.fc10.x86_64 (installed) These are 64-bit, x86_64 packages. Well, as I have libssl.so.8 and libcrypto.so.8 installed, and KDE is looking for libssl.so.7 and libcrypto.so.7, I decided to create the symbolic links that KDE is looking for. I have the following: /usr/lib/libssl.so.8: symbolic link to `libssl.so.0.9.8k' /usr/lib/libcrypto.so.8: symbolic link to `libcrypto.so.0.9.8k' so I have created the following symbolic links: /usr/lib/libssl.so.7: symbolic link to `libssl.so.0.9.8k' /usr/lib/libcrypto.so.7: symbolic link to `libcrypto.so.0.9.8k' This is definately the wrong way to go. Do not work against the distribution! and with that now everything is working fine again. Anyway, my 'yum repolist' is as follows: fedoraFedora 11 - i386 enabled: 13,289 livna rpm.livna.org for 11 - i386 enabled: 3 rpmfusion-freeRPM Fusion for Fedora 11 - Free enabled:566 rpmfusion-free-updatesRPM Fusion for Fedora 11 - Free - Updates enabled: 0 rpmfusion-nonfree RPM Fusion for Fedora 11 - Nonfree enabled:240 rpmfusion-nonfree-updates RPM Fusion for Fedora 11 - Nonfree - Upda enabled: 0 updates Fedora 11 - i386 - Updates enabled: 1,293 These are 32-bit i386 repositories! i.e. you have updated a 64-bit installation to 32-bit, no wonder why it doesn't work. -- Jussi Lehtola Fedora Project Contributor jussileht...@fedoraproject.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: GPRS in Fedora 10
On Tue, Jun 2, 2009 at 3:56 PM, Adeel Akbar aak...@i2cinc.com wrote: Hi I want to run internet through GPRS service. Can anyone advice how we create dial up connection in Fedora 10 to connect with internet. Thanks Regards Adeel Akbar -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines Salam, Can you please also list what mobile do you have and what cable are you using to connect it with PC. Just have a look here http://www.shekhargovindarajan.com/open-source/fedora-x/ -- Regards, Mustafa Qasim Lahore, Pakistan Registered Linux User# 441709. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Questions with rsync
Will this command do the job for backup? rsync -vpa / /home/user/backup How would I exclude these files below: /lost+found /media /mnt and others which I do not need. And what is the compression lever by rsync (using -a option)? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Grub doesn't recognize hdd in F11 x86_64
Hello, I have problem booting F11 x86_64 (Preview and snapshot from May 28th - aka rc ) after installation. Used hardware is HP Pavilion dv5-1150ew. After smooth installation (both from LiveCD and DVD release) and reboot it stops at grub console. Issuing command root (hd , geometry (hdx) where x=0,1,2... gives no such device error 21. F11 was installed on fresh hdd with default partition layout. I even placed the bug report on bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=503180 , but with no response so far. I tried F10, Centos 5.3 and Ubuntu 9.04, but with no success. With erronr 21 ( Ubuntu) or installation crashed during partitioning ( F10, Centos ) hdd and memory tested and passed all OK. Tried a few BIOS versions -all the same And ... Vista boots OK. G ;-) Maybe someone could help me to make F11 bootable on this machine? Regards Marcin Wołyniak -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
I don't have colors in Midnight commander editor
Hello, I have fedora release 9 . I installed mc (midnight commander) by yum install mc. When I open xml files or c source files or java with mc editor (by pressing F4) I don't see any colors. (I mean colors of some keywords , like int (for c source file), lines starting with or -- for xml, etc.) On other fedora machines I **do** see colors with mc. Any ideas what can be the reason ? Rgs, Mark -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Joining wireless and wired networks
Hi, I've a computer at home I'm using for a network gateway, which has two ethernet cards and a wireless card. One of the ethernet cards connects to the outside world and the wireless side of the network connects to the internet using iptables to provide NAT and forward the packets over. The system is also running a dhcp server for the providing IP addresses to the wireless clients. What I want to do now is bring in the other ethernet card so computers attached to that part of the network can connect to the internet and access the services of the other machines on the network, regardless of whether they're on the gateway or the wireless network. I was considering bridging the wireless and the wired networks, but just wanted to ask for opinions, other options. I''m loooking at eventually getting a job working with linux systems, so it doesn't have to be a what would be best in a home environment solution. Thanks for the help, James -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ibssl.so.7 ?!
2009/6/3 Jussi Lehtola jussileht...@fedoraproject.org: On Tue, 2009-06-02 at 22:10 -0300, Germán Racca wrote: On Tue, 2009-06-02 at 21:53 -0300, Martín Marqués wrote: Germán, the problem is that preupgrade leaves out a bunch of kde apps: Checking for new repos for mirrors * preupgrade: fedora.c3sl.ufpr.br 6:kdelibs-4.2.3-2.fc10.x86_64 from installed has depsolving problems -- Missing Dependency: libssl.so.7()(64bit) is needed by package 6:kdelibs-4.2.3-2.fc10.x86_64 (installed) These are 64-bit, x86_64 packages. Those errors are from my upgrade (an AMD 64 laptop) fedora Fedora 11 - i386 enabled: 13,289 livna rpm.livna.org for 11 - i386 enabled: 3 rpmfusion-free RPM Fusion for Fedora 11 - Free enabled: 566 rpmfusion-free-updates RPM Fusion for Fedora 11 - Free - Updates enabled: 0 rpmfusion-nonfree RPM Fusion for Fedora 11 - Nonfree enabled: 240 rpmfusion-nonfree-updates RPM Fusion for Fedora 11 - Nonfree - Upda enabled: 0 updates Fedora 11 - i386 - Updates enabled: 1,293 These are 32-bit i386 repositories! These are from Germáns computer. Germán, what does yum update say? Do a yum clean all first. -- Martín Marqués select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ibssl.so.7 ?!
2009/6/2 Germán Racca german.ra...@gmail.com: Hello Martín, thanks for your answer. Well, as I have libssl.so.8 and libcrypto.so.8 installed, and KDE is looking for libssl.so.7 and libcrypto.so.7, I decided to create the symbolic links that KDE is looking for. I have the following: /usr/lib/libssl.so.8: symbolic link to `libssl.so.0.9.8k' /usr/lib/libcrypto.so.8: symbolic link to `libcrypto.so.0.9.8k' so I have created the following symbolic links: /usr/lib/libssl.so.7: symbolic link to `libssl.so.0.9.8k' /usr/lib/libcrypto.so.7: symbolic link to `libcrypto.so.0.9.8k' and with that now everything is working fine again. As Jussi said, this is bad thing to do. If at any time the kde applications need to use some specific thing that is in libssl.so.7 and not in libssl.so.8, you'll be doomed. -- Martín Marqués select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Questions with rsync
On Wed, Jun 3, 2009 at 8:02 PM, GMS S gms...@yahoo.com wrote: Will this command do the job for backup? rsync -vpa / /home/user/backup How would I exclude these files below: /lost+found /media /mnt if you man rsync , you can see two options for you: --exclude=PATTERN exclude files matching PATTERN --exclude-from=FILE read exclude patterns from FILE and others which I do not need. And what is the compression lever by rsync (using -a option)? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Questions with rsync
On Wed, 2009-06-03 at 03:02 -0700, GMS S wrote: Will this command do the job for backup? rsync -vpa / /home/user/backup How would I exclude these files below: /lost+found /media /mnt and others which I do not need. And what is the compression lever by rsync (using -a option)? I would pretty much recommend that you specifically omit /dev and /proc too. Save the filter to a text file and make it look something like this (I like the first one but you might not). + and - symbols should be obvious. - ~* - /lost+found/ + **/home/user/backup rsync -vpa --filter='. /path/to/rsync-filter' $source $destination I didn't think '-a' option indicates compression at all, only 'archive' and you might want '-u' option for update. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Upgrade FC3 to FC10
Have an old system that requires upgrade from existing FC3 configuration to FC10 for security concerns. Upgrade vice fresh install is necessary to maintain existing proprietary application loads. When attempt to utilize FC10 upgrade DVD it can not find a Linux load on HDD, though it is there. Also tried with FC9, same results. Any guidance would be appreciated. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrade FC3 to FC10
On Wed, 2009-06-03 at 09:10 -0400, Moessbauer, David wrote: Have an old system that requires upgrade from existing FC3 configuration to FC10 for security concerns. Upgrade vice fresh install is necessary to maintain existing proprietary application loads. You have proprietary software installed in FC3 that you want to work in the new OS too? When attempt to utilize FC10 upgrade DVD it can not find a Linux load on HDD, though it is there. Also tried with FC9, same results. Any guidance would be appreciated. Then F9 and F10 might be too new to be able to upgrade such an old installation. I wouldn't update to a new Fedora, if you have proprietary software that you still want to use. The libraries and so on may not be compatible with the old software. I suggest you update to CentOS 4 ( http://centos.org/ ), which is largely based on Fedora Core 3 so the update should be quite painless. You should even be able to do the update with yum. -- Jussi Lehtola Fedora Project Contributor jussileht...@fedoraproject.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Questions with rsync
[ I would pretty much recommend that you specifically omit /dev and /proc too. Save the filter to a text file and make it look something like this (I like the first one but you might not). + and - symbols should be obvious. - ~* - /lost+found/ + **/home/user/backup rsync -vpa --filter='. /path/to/rsync-filter' $source $destination I didn't think '-a' option indicates compression at all, only 'archive' and you might want '-u' option for update. Craig ] So what would be the final command if I exclude these directory? /lost+found /media /mnt /dev /proc /home/user/backup /dev Thanks. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Questions with rsync
On 6/3/09, GMS S gms...@yahoo.com wrote: Will this command do the job for backup? rsync -vpa / /home/user/backup How would I exclude these files below: /lost+found /media /mnt and others which I do not need. And what is the compression lever by rsync (using -a option)? Not an answer to your questions, but if you plan to use rsync for backup, have a look at this: http://www.mikerubel.org/computers/rsync_snapshots/ Andras -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: GPRS in Fedora 10
Hi Thanks for your support. I have Sony Ericson K320i with original data cable. Thanks Regards Adeel Akbar - Original Message - From: Mustafa Qasim ala...@gmail.com To: Community assistance, encouragement, and advice for using Fedora. fedora-list@redhat.com Sent: Wednesday, June 3, 2009 3:01:04 PM GMT +05:00 Tashkent Subject: Re: GPRS in Fedora 10 On Tue, Jun 2, 2009 at 3:56 PM, Adeel Akbar aak...@i2cinc.com wrote: Hi I want to run internet through GPRS service. Can anyone advice how we create dial up connection in Fedora 10 to connect with internet. Thanks Regards Adeel Akbar -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines Salam, Can you please also list what mobile do you have and what cable are you using to connect it with PC. Just have a look here http://www.shekhargovindarajan.com/open-source/fedora-x/ -- Regards, Mustafa Qasim Lahore, Pakistan Registered Linux User# 441709. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
postgresql f10 hangs on shutdown
PostgreSQL hangs on shutdown causing me to have to hit the hardware reset switch. Has anyone dealt with this issue? This has been occuring to me for a long time, but since I cannot find much evidence as to why it happens I haven't created a bug report. Evidence so far: -Before shutdown I can manually stop PostgreSQL successfully, but if I forget and perform a shutdown/restart, it hangs on stopping postgresql. -The process must be running for at least multiple hours. 4-8 hours seems to be long enough. Otherwise it will shutdown OK. -I don't even have to use a database for it to get into this bad state. The shutdown process turns off NetworkManager, then sshd, then postgresql, so I am unable to SSH in or log in to diagnose this issue. Any pointers would be appreciated. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Joining wireless and wired networks
James Allsopp wrote: Hi, I've a computer at home I'm using for a network gateway, which has two ethernet cards and a wireless card. One of the ethernet cards connects to the outside world and the wireless side of the network connects to the internet using iptables to provide NAT and forward the packets over. The system is also running a dhcp server for the providing IP addresses to the wireless clients. What I want to do now is bring in the other ethernet card so computers attached to that part of the network can connect to the internet and access the services of the other machines on the network, regardless of whether they're on the gateway or the wireless network. I was considering bridging the wireless and the wired networks, but just wanted to ask for opinions, other options. I''m loooking at eventually getting a job working with linux systems, so it doesn't have to be a what would be best in a home environment solution. Thanks for the help, James Setting up a bridge interface using the two NICs is probably the simplest. But if you want to play, you could put each NIC on its own subnet, and set up routing between them. It isn't too hard if you are using static addressing. If you are using dhcp, setting up the dhcp server is interesting. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: preupgrade or anaconda error
El día 2 de junio de 2009 19:16, Martín Marqués martin.marq...@gmail.com escribió: Got a wired connection and this is what bugzilla got: https://bugzilla.redhat.com/show_bug.cgi?id=503830 Got passed this. All packages got upgraded. The problem is that it's at the Finishing upgrade process. the last 40 minutes. Disk usage is high, and the load is at 1.05. I'll soon have to turn off the laptop, so what should I do? -- Martín Marqués select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Questions with rsync
On Wed, 2009-06-03 at 03:02 -0700, GMS S wrote: Will this command do the job for backup? rsync -vpa / /home/user/backup Er, isn't this recursive? poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Questions with rsync
On Wednesday 03 June 2009 08:35:50 Patrick O'Callaghan wrote: On Wed, 2009-06-03 at 03:02 -0700, GMS S wrote: Will this command do the job for backup? rsync -vpa / /home/user/backup Er, isn't this recursive? poc I didn't really like the behavior of the filter functionality in rsync so I took a different approach. I have a file called dirlist which is the list of root level directories I want to backup, this is coupled with a shell script (rsync_backup.sh) which runs my desired rsync command for each dirname found in the dirlist file. I also have a restore shell script (rsync_restore.sh). I use this to backup my Fedora10 laptop before I run any updates. I have had to go back and run the restore when updates caused video issues, the restore worked flawlessly. I've attached the dirlist and both rsync scripts (the backup and the restore), hope it's helpful. bin boot docs download etc home lib lib64 lost+found media mnt opt root sbin selinux srv tmp usr var rsync_backup.sh Description: application/shellscript rsync_restore.sh Description: application/shellscript -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: WUSB54G firmware
Kevin Kofler wrote: Bill Davidsen wrote: Jim, mine uses something called rt73.bin and I have no idea how it got in /lib/firmware... But that's what it appears to use. rt73 is a Ralink firmware, it has nothing to do with the OP's Prism WLAN. It comes from the rt73usb-firmware package. Let me state the facts and you can tell me why they don't mean the obvious... when I plug in the WUSH54G device, the disk blinks, the device blinks, and a wireless connection is made. On looking at the files in /lib/firmware I see that the most recently accessed file is rt73.bin. And that if I boot without plugging in the WUSH54G device that firmware is not accessed. I didn't pull that filename out of the sir, I looked to see what firmware was accessed. Are you saying that the access when the device is used is just a coincidence? -- Bill Davidsen david...@tmr.com We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fix /boot/grub/grub.conf to chainload Fedora 11 Preview?? and Fedora 9 with chainloader
Antonio Olivares wrote: Dear fellow Fedoreans, I have a machine which Windows, and Fedora 9 have coexisted happily since Fedora 9 was released. I shrunk the Windows Partition a bit more and setup an empty place where I installed Fedora 11 Preview(to update it to current Fedora 11 pre or rawhide whichever gets picked up via updates) Now I can boot windows and Fedora 11, but can't boot Fedora 9, everything is in there I can see the data, I just can't boot it. Here's output of fdisk and grub.conf for both Fedora 9 and Fedora 11?? soon to be This would have been easier to fix before installing the new version. Probably the fastest fix is to boot the new install, and re-install Grub to the boot record of /boot. The boot in the rescue mode of the install DVD or boot CD. Tell it you want to fix re-install the boot loader of the F9 install. After rebooting into F9, edit grub and add a chainloader entry to the F11 /boot directory. You can use the Windows entry as an example. Mike -- Black Holes are Where God Divided by Zero. signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
No icons or panels in Desktop, just wallpaper
I'm a beginner and had got a Fedora core 7 in my Laptop., It worked fine in the first days. But now on logging in to the desktop there is no Panels or Icons in the desktop. Just the Wallpaper. The cursor appears and it can be moved. I can't do anything., I just restarted. Done it many times but same thing happens. ** *Configuration* Intel Celeron-M 560, 2.13/1M/533 512MB DDRII 667 80GB SATA HDD -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: No icons or panels in Desktop, just wallpaper
ashin george wrote: I'm a beginner and had got a Fedora core 7 in my Laptop., It worked fine in the first days. But now on logging in to the desktop there is no Panels or Icons in the desktop. Just the Wallpaper. The cursor appears and it can be moved. I can't do anything., I just restarted. Done it many times but same thing happens. ** *Configuration* Intel Celeron-M 560, 2.13/1M/533 512MB DDRII 667 80GB SATA HDD Hi Ashin, I would recommend you update to Fedora 10 or 11 (out shortly). As you won't receive any furthrt updates for Fedora 7 http://fedoraproject.org/wiki/LifeCycle/EOL It is no longer supported. Frank -- msn: frankly3d skype: frankly3d Mailing-List Reply to: Mailing-List Still Learning, Unicode where possible -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Netbooks
On 06/02/2009 10:38 PM, Michael Leung wrote: Yes, that is the better to use the OS from the vendor. As far as I know, eee PC linux is customized . On Sun, May 31, 2009 at 4:18 AM, Wolfgang S. Rupprecht wolfgang.rupprecht+gnus200...@gmail.com mailto:wolfgang.rupprecht%2bgnus200...@gmail.com wrote: Ralf Corsepius rc040...@freenet.de mailto:rc040...@freenet.de writes: The OP asked about EeePC - Fedora or Ubuntu. My answer to this question would be: If you simply want to use your netbook, you're likely better off using the OS the HW vendor supplies. Some netbooks seem to be better than others. I have a Acer Aspire One here that works fine under F11. The wifi works fine as does NetworkManager once one gets around the bug that many of the config screens have the bottoms cut off and one needs to use and larger external LCD to setup the thing. This machine isn't for me. I simply can't use those small keyboards. Gimme 19mm key spacing or some environment where I never have to use the keyboard. -wolfgang -- Wolfgang S. Rupprecht Android 1.5 (Cupcake) and Fedora-11 -- fedora-list mailing list fedora-list@redhat.com mailto:fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- Regards, Michael Leung http://www.itblogs.info http://www.michaelleung.info Fedora 10 works perfectly for a Asus 701 and a 1000. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: Upgrade FC3 to FC10
Yes, we need applications to work in new OS too. Would CentOS4 address following security concerns: 1. Disable Executive Stack - IE: kernel must support NX feature 2. Linux Kernel Remote Denial of Service Vulnerability that affects kernels prior to 2.6.27.5 -Original Message- From: fedora-list-boun...@redhat.com [mailto:fedora-list-boun...@redhat.com] On Behalf Of Jussi Lehtola Sent: Wednesday, June 03, 2009 9:39 AM To: Community assistance, encouragement,and advice for using Fedora. Subject: Re: Upgrade FC3 to FC10 On Wed, 2009-06-03 at 09:10 -0400, Moessbauer, David wrote: Have an old system that requires upgrade from existing FC3 configuration to FC10 for security concerns. Upgrade vice fresh install is necessary to maintain existing proprietary application loads. You have proprietary software installed in FC3 that you want to work in the new OS too? When attempt to utilize FC10 upgrade DVD it can not find a Linux load on HDD, though it is there. Also tried with FC9, same results. Any guidance would be appreciated. Then F9 and F10 might be too new to be able to upgrade such an old installation. I wouldn't update to a new Fedora, if you have proprietary software that you still want to use. The libraries and so on may not be compatible with the old software. I suggest you update to CentOS 4 ( http://centos.org/ ), which is largely based on Fedora Core 3 so the update should be quite painless. You should even be able to do the update with yum. -- Jussi Lehtola Fedora Project Contributor jussileht...@fedoraproject.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Are you using LXDE?
Tim wrote: On Tue, 2009-06-02 at 20:27 -0400, John Aldrich wrote: How does one configure Fedora 10 to use the nouveau driver if one does not have an xorg.conf? I know that the old way used to be to hand-edit the xorg.conf, but since that doesn't exist any more, I'm at a loss for how to fix this. One option is to create one from scratch. There's plenty of samples on the web about how the xorg.conf file is formed. Do a bit of research. Two less error-prone ways are to install and use system-config-display or run Xorg with the option to create the file (sorry, don't remember it). I thought you could just use xdriver=noveau on the boot line, but I haven't looked at that stuff in a year or so and might be misremembering. -- Bill Davidsen david...@tmr.com We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: Upgrade FC3 to FC10
On Wed, 2009-06-03 at 11:31 -0400, Moessbauer, David wrote: Yes, we need applications to work in new OS too. Would CentOS4 address following security concerns: 1. Disable Executive Stack - IE: kernel must support NX feature 2. Linux Kernel Remote Denial of Service Vulnerability that affects kernels prior to 2.6.27.5 CentOS 4 was released in 2005 and will be supported AFAIK until 2012. There should be no security concerns with it. -- Jussi Lehtola Fedora Project Contributor jussileht...@fedoraproject.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: F10 stuck at grub -
http://www.gtlib.gatech.edu/pub/fedora.redhat/linux/releases/10/Fedora/i 386/os/images/ -Original Message- From: Bob Goodwin [mailto:bobgood...@wildblue.net] Sent: Tuesday, June 02, 2009 6:31 PM To: Community assistance, encouragement,and advice for using Fedora. Subject: Re: F10 stuck at grub - Smith, Herb wrote: You can also use a cd made from the boot.iso if it won't take your liveCD...same process. Is there a boot.iso file on the livecd? I can't find it, probably missing something but ... Bob -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrade FC3 to FC10
On Wed, 3 Jun 2009 11:31:35 -0400 Moessbauer, David dmoessba...@progeny.net wrote: Yes, we need applications to work in new OS too. Would CentOS4 address following security concerns: 1. Disable Executive Stack - IE: kernel must support NX feature Centos has it if I remember (assuming your CPU supports PAE and NX) 2. Linux Kernel Remote Denial of Service Vulnerability that affects kernels prior to 2.6.27.5 Insufficient information - which specific vulnerability (what vulnerability id ?) Centos is built from the same basic sources as Red Hat Enterprise Linux - so its long term maintained but without the guarantees, support and service stuff paying for Red Hat gets you. If you need long lifetimes of old code its probably more appropriate than Fedora -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: Upgrade FC3 to FC10
On Wed, 3 Jun 2009, Moessbauer, David wrote: Yes, we need applications to work in new OS too. Would CentOS4 address following security concerns: 1. Disable Executive Stack - IE: kernel must support NX feature 2. Linux Kernel Remote Denial of Service Vulnerability that affects kernels prior to 2.6.27.5 CentOS 4 is a clone of Red Hat's RHEL4 minus the trademarked stuff (like the Red Hat name and Red Hat specific icons) Jussi Lehtola wrote: I suggest you update to CentOS 4 ( http://centos.org/ ), which is largely based on Fedora Core 3 so the update should be quite painless. You should even be able to do the update with yum. You might have to tidy up a lot after a yum update (or indeed any other update from FC3 to CentOS 4), because some packages in a fully patched version of FC3 (eg. the kernel) will have a higher version number than Centos 4, since in RHEL security patches are often backported to the original version of the software in the distribution rather than using the later version that includes the fix. Michael Young -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: preupgrade or anaconda error
El día 3 de junio de 2009 11:28, Martín Marqués martin.marq...@gmail.com escribió: El día 2 de junio de 2009 19:16, Martín Marqués martin.marq...@gmail.com escribió: Got a wired connection and this is what bugzilla got: https://bugzilla.redhat.com/show_bug.cgi?id=503830 Got passed this. All packages got upgraded. The problem is that it's at the Finishing upgrade process. the last 40 minutes. Disk usage is high, and the load is at 1.05. I'll soon have to turn off the laptop, so what should I do? Never mind. It finally finish. It did take quite a long time to do so. -- Martín Marqués select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 stuck at grub -
Smith, Herb wrote: http://www.gtlib.gatech.edu/pub/fedora.redhat/linux/releases/10/Fedora/i 386/os/images/ Yes I found a site with the boot.iso stuff and put it on a cd. Even then I had problems and finally decided to remove the hard drives and replace them with one larger drive which was my ultimate intention anyway. Even then the livecd had trouble trying to install over an existing F-10 on that larger drive. I had to reformat it with fdisk ... Then the livecd install went as expected. I also learned a few other things I believe most of my trouble was due to an item in the BIOS setup that I had not noticed before which forced it to boot from the first drive and I had put everything on the second. I didn't notice that until I replaced the drives and went through the BIOS settings for the nth time! We get too late smart. Thanks to all for the help. Now to continue my file server experimentation. Bob -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Grub doesn't recognize hdd in F11 x86_64
marcin_wolyniak marcin_wolyn...@aster.pl writes: I have problem booting F11 x86_64 (Preview and snapshot from May 28th - aka rc ) after installation. Used hardware is HP Pavilion dv5-1150ew. After smooth installation (both from LiveCD and DVD release) and reboot it stops at grub console. Issuing command root (hd , geometry (hdx) where x=0,1,2... gives no such device error 21. F11 was installed on fresh hdd with default partition layout. Might it be this problem? Do you have more than one disk in the system? https://www.redhat.com/archives/fedora-test-list/2009-May/msg01392.html You might just need to do a grub-install. -wolfgang -- Wolfgang S. Rupprecht Android 1.5 (Cupcake) and Fedora-11 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
samba client
Hi list I want to ask what are the available client for samba on fedora. I know that kde and gnome integrate samba in the GUI. do you know any other clients Thanks in advance Regards -- http://ilovefedora.blogspot.com/ -- PhD candidate in Computer Science Address BP 108, Bureau de poste Tunis republique 1001 Tunis Tunisia tel: +216 97 246 706 fax: +216 71 391 166 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Two monitors, modelines, xorg.conf, and all that...
Marko Vojinovic vvma...@gmail.com writes: When I plug in the VGA, X chooses the highest common resolution, which happens to be 1024x768. I can only ponder as to why a 22 VGA monitor does not want to do 1280x800, but that's not the question. What I would like to have is the following setup: Under f11 this appears to have changed, at least for a Acer Aspire One netbook I just tested. When I plug a 1200x1600 monitor into it the desktop comes up 1200x1600 instead of the 1024x600 it is when only the native screen is attached. So the answer my be, just wait a few days and upgrade to f11. With preupgrade is should be a painless upgrade. -wolfgang -- Wolfgang S. Rupprecht Android 1.5 (Cupcake) and Fedora-11 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrade FC3 to FC10
Moessbauer, David dmoessba...@progeny.net writes: Have an old system that requires upgrade from existing FC3 configuration to FC10 for security concerns. Upgrade vice fresh install is necessary to maintain existing proprietary application loads.  When attempt to utilize FC10 upgrade DVD it can not find a Linux load on HDD, though it is there. Also tried with FC9, same results.  Any guidance would be appreciated. Buy a new disk, unplug the old one and do a clean install of f11 on it when f11 comes out in a week. Then recompile your proprietary software and run. If it fails, you can always put the old fc3 disk back in and wait till someone breaks in and destroys the system. At that point it won't matter that the proprietary stuff doesn't run on f11, because it won't run on the fc3 installation either. ;-) All joking aside, I don't see how you can avoid reinstalling your proprietary stuff under a more recent OS. -wolfgang -- Wolfgang S. Rupprecht Android 1.5 (Cupcake) and Fedora-11 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Questions with rsync
GMS S gms...@yahoo.com writes: Will this command do the job for backup? rsync -vpa / /home/user/backup How would I exclude these files below: /lost+found /media /mnt It is always a good idea to throw in an -x to these programs and then list the filesystems you want to backup explicitly. -wolfgang -- Wolfgang S. Rupprecht Android 1.5 (Cupcake) and Fedora-11 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Are you using LXDE?
On 6/3/09, Kevin Kofler kevin.kof...@chello.at wrote: Andras Simon wrote: Have you filed bug reports for your problems with nvida? They can't fix them if they don't know about them. [...] Plenty of users have filed KDE bugs with us which turned out to be NVidia proprietary driver bugs. (Of course we told them to report them to NVidia, whether they did or not is something I don't know.) Some got fixed, but for each issue they fix, some new one comes up. Couldn't this be a fair description of lots of OS software, too? That doesn't make them crap. Work in progress, perhaps. Andras -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Skype under Fedora-10
Tim wrote: On Mon, 2009-06-01 at 15:23 +0100, Timothy Murphy wrote: Incidentally, is there any alternative to Skype that works under Linux and Windows XP? Until someone hacks the proprietary Skype system, and I haven't seen any notice that someone has, you're not going to see a non-Skype program that can connect to other Skype programs. Skype's a lousy idea, for various reasons, and that's just one of them. A blanket statement bound to generate flames if I ever saw one. I might as well start the flame fest. I disagree, Tim. Skype is a good idea. There are bits that could be done better, but parts of the service require quite a bit of capital investment and there has to be a way to fund that. Subscriptions is one way. When I was in Europe two years ago, I was able to call my mother in the USA on her land line to check on her (she's 80 and lives alone). The cost using Skype was easily less than 25% of what it would have cost me using my cell phone and standard connections. That ability alone as well as the converse (permitting regular telephone users such as my mother the ability to contact my computer via a phone number) is terrific. My mom is something of a technophobe. She'll deal with the phone, but will have nothing whatsoever to do with computers (took me weeks to teach her how to use the OnStar in her car...and that uses voice commands!). You don't need to hack the system. Use H.323/SIP clients (ekiga, etc.) and talk computer-to-computer all you want. I don't buy the if it's on the Internet it HAS to be free, therefore we should hack into it mantra. If it's something that services a need I have, I don't mind paying for it--in fact I expect to. I don't believe in entitlements of any sort. In Skype's case, someone's got to pick up the bill for the PBX systems. They only charge if you intend to use the PBX anyway. Do you prepay your cell minutes? I'm always dumbfounded by people who do that yet expect their Internet access to be free. Do I wish their Linux client was more solid? Yes. Do I wish they had a native 64-bit version? Yes. Do I wish it was open source and able to be improved upon by others? Yes. However, even in its current state it works (even with PulseAudio) and I'm fine with it and their service. Your mileage may vary. -- - Rick Stevens, Systems Engineer ri...@nerd.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - Is that a buffer overflow or are you just happy to see me? - -- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Questions with rsync
GMS S wrote: [ I would pretty much recommend that you specifically omit /dev and /proc too. Save the filter to a text file and make it look something like this (I like the first one but you might not). + and - symbols should be obvious. - ~* - /lost+found/ + **/home/user/backup rsync -vpa --filter='. /path/to/rsync-filter' $source $destination I didn't think '-a' option indicates compression at all, only 'archive' and you might want '-u' option for update. Craig ] So what would be the final command if I exclude these directory? /lost+found /media /mnt /dev /proc /home/user/backup /dev I use this sort of thing with a 500GB USB drive (automounted at /media/500GB-Drive by Gnome): #!/bin/bash # Back up system to a specific directory given on the command # line or a default based on today's date. Excludes the /proc, # /sys, /dev and /media directories MYHOST=`hostname` TODAY=`date +%d-%b-%Y` if [ $# -lt 1 ]; then TGT=/media/500GB-Drive/$MYHOST-BackUp-$TODAY else TGT=$1 fi rsync -avXA --exclude-from=/etc/skipdirs.rsync / $TGT with /etc/skipdirs.rsync containing: /proc/* /sys/* /dev/* /media/* Tweak as you see fit. -- - Rick Stevens, Systems Engineer ri...@nerd.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - To err is human, to moo bovine. - -- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: update to F11 with yum
On Wed, 2009-06-03 at 11:51 -0500, Michael Cronenworth wrote: Alan Evans wrote: How do you do that? I have a small number of 32-bit packages on my desktop. If I try to remove, for example, glibc.i686, then it tries to take basesystem.noarch with it as a dependency! rpm -e glibc.i686 --nodeps (use with care...) use with care? If I wanted to hose a system, that command would be pretty close to the top of the list of things to do. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Grub doesn't recognize hdd in F11 x86_64
Dnia Wolfgang S. Rupprecht 03.06.2009 19:08 napisał(a): Might it be this problem? Do you have more than one disk in the system? https://www.redhat.com/archives/fedora-test-list/2009-May/msg01392.html You might just need to do a grub-install. -wolfgang Unfortunately this is laptop and has only one disk. I forgot mention that more details what I tried are in the bugzilla under the link mentioned in first post. I've already done the grub-install with no success. More, I've then lost the grub console after reboot. Only Error 21 message displayed with no console. -- Regards Marcin Wołyniak -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: WUSB54G firmware
Bill Davidsen david...@tmr.com writes: Kevin Kofler wrote: Bill Davidsen wrote: Jim, mine uses something called rt73.bin and I have no idea how it got in /lib/firmware... But that's what it appears to use. rt73 is a Ralink firmware, it has nothing to do with the OP's Prism WLAN. It comes from the rt73usb-firmware package. Let me state the facts and you can tell me why they don't mean the obvious... when I plug in the WUSH54G device, the disk blinks, the device blinks, and a wireless connection is made. On looking at the files in /lib/firmware I see that the most recently accessed file is rt73.bin. And that if I boot without plugging in the WUSH54G device that firmware is not accessed. I didn't pull that filename out of the sir, I looked to see what firmware was accessed. Are you saying that the access when the device is used is just a coincidence? Does /var/log/messages say anything interesting? On my laptop's embedded radio I see kernel-tagged syslog messages indicating which firmware file is getting loaded. If that were present it would put an end to any doubt. Jun 3 10:32:19 ancho kernel: b43 ssb0:0: firmware: requesting b43/ucode5.fw Jun 3 10:32:19 ancho kernel: b43 ssb0:0: firmware: requesting b43/pcm5.fw Jun 3 10:32:19 ancho kernel: b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw Jun 3 10:32:19 ancho kernel: b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw Jun 3 10:32:19 ancho kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) -wolfgang -- Wolfgang S. Rupprecht Android 1.5 (Cupcake) and Fedora-11 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
