Re: Help wanted with dist-cvs to git conversion
On Thursday 10 December 2009 09:12:46 pm Seth Vidal wrote: On Thu, 10 Dec 2009, Jesse Keating wrote: I'm currently playing with a utility called parsecvs to convert our cvs stuff into git. This utility can also translate the raw usernames that CVS has into more useful names+email addresses that you'd typically get out of git. But to make this conversion it needs a translation file. It would be really helpful if somebody could generate a file for me that is in the format of: username=firstname lastname email eg: jkeating=Jesse Keating jkeat...@fedoraproject.org notting=Bill Nottingham nott...@fedoraproject.org For the initial testing, just giving every user a @feodraproject.org domain would be sufficient, however we should have a discussion about whether to use this email address or to use the user's real email address. I just did this on fedorapeople.org not against fas but I suspect that's the same set of users. #!/usr/bin/python -tt import pwd for pw in pwd.getpwall(): if pw.pw_uid 1: continue msg='%s=%s %...@fedoraproject.org' % (pw.pw_name, pw.pw_gecos, pw.pw_name) print msg the file with these contents is in my homedir on fedorapeople.org as: wacky-list-for-git if you want me to do it directly talking to fas I'll do it in the morning. -sv A script that grabs the entries from FAS, and outputs everything as UTF-8 files: http://konradm.fedorapeople.org/usernamelist.py Results with FAS emails (in my $HOME on fedorapeople.org): FAS-users-normalemails or fedoraproject.org emails: FAS-users-fedoraprojectemails 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: Help wanted with dist-cvs to git conversion
On Thursday 10 December 2009 09:28:43 pm Conrad Meyer wrote: A script that grabs the entries from FAS, and outputs everything as UTF-8 files: http://konradm.fedorapeople.org/usernamelist.py I forgot to mention, this requires the 'python-fedora' package. (Doh!) 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: Help with packaging
On Sunday 06 December 2009 04:01:54 pm Robert Spanton wrote: On Tue, 2009-11-24 at 19:16 -0800, Conrad Meyer wrote: I'm experiencing trouble trying to get one of my packages (sdcc) to build for Fedora 12. It builds on Fedora 11 and older (just double-checked in mock). It seems to be some sort of change in how RPM uses __os_install_post or how brp- strip-static-archive works between F11 and F12. Anyone familiar with any such changes? You might find it useful to have a look at what I'm doing in msp430-libc with __os_install_post. I think I was inspired to do this by what was done in avr-libc. Thanks, I'll try doing that now. Unfortunately it seems like that will stop rpmbuild from stripping the (native) sdcc binaries, but I'd like to see the package building. RPM seems to be one of those things where knowledge is passed on by word of mouth between generations :-/ Yes, and perhaps more work could be done with rpm to improve support for cross-compiler-related packages. p.s. Sorry for not replying sooner -- I don't read all posts to fedora-devel, as I would go insane :-P I'm glad to get any help. Thanks, -- 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
Help with packaging
Hi list,
I'm experiencing trouble trying to get one of my packages (sdcc) to build for
Fedora 12. It builds on Fedora 11 and older (just double-checked in mock). It
seems to be some sort of change in how RPM uses __os_install_post or how brp-
strip-static-archive works between F11 and F12. Anyone familiar with any such
changes?
http://linux.dell.com/files/fedora/FixBuildRequires/mock-
results/x86_64/sdcc-2.9.0-4.fc12.src.rpm/result/build.log
Some background info for those unfamiliar with sdcc: sdcc is a compiler
targeting embedded devices. It bundles some archives that contain object code
for these other architectures -- chmodded 644, in %{_datadir} -- I don't even
know why brp-strip* dives into %{_datadir} anyway.
Thanks,
--
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: Improve the way rpm decides what is newer
On Saturday 21 November 2009 01:38:35 am drago01 wrote: We should just use release epochs, people might hate them for whatever reasons, but they would easily prevent such issues from happing. The problem with this system, which has been pointed out before, is that upgrades using the Fedora N release DVD on an up-to-date Fedora N-1 system will replace newer versions of packages with older ones -- this is bad. 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: PackageKit policy: background and plans
On Thursday 19 November 2009 09:09:15 pm James Morris wrote: On Thu, 19 Nov 2009, Owen Taylor wrote: Among the decisions Richard made was allowing all users to install signed packages from the Fedora repositories. This was clearly the right behavior for the common case of a single-user system, where the only user is also the administrator. I don't think this is clearly the right behavior at all. ... I think it's fair to say that having this happen as root would generally be worse than it happening as an unprivileged user. For the latter, the attacker would need to also then succeed with a local privilege escalation attack to the same effect. On the contrary. On the typical single user system, it's just as bad if an attacker can steal / delete / modify the user's files as it is if the attacker can modify / delete system files. Privilege escalation isn't needed to delete everything the single user cares about. 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: Broken deps for rawhide the past few days
On Tuesday 17 November 2009 06:50:58 am Jesse Keating wrote: On Mon, 2009-11-16 at 11:22 -0800, Jesse Keating wrote: Many of you received emails over the weekend and this morning regarding broken deps in rawhide. If these emails mentioned that the deps were broken on ppc or ppc64 they can be ignored. We are no longer producing ppc/ppc64 as a primary arch, however we forgot to tag the config change that enacted this on our compose tools. We were attempting to compose ppc(64) trees with only noarch packages, and well things didn't work so hot. We should have this fixed today so that future emails about broken deps will be about actual broken deps, not broken configurations. Sorry for the mailbombing. *sigh* While we were successful in building a new mash package that would avoid making ppc repos, we forgot to update one of the rawhide creation configs so that it used dist-f13 content as opposed to dist-f12. So the rawhide creation process has been using dist-f12 content all this time to build up the chroot, which would then compose dist-f13 content. This means that the dist-f12 version of mash was used, not the dist-f13 version we built to disable ppc. I've corrected that. Third try to kill the ppc deps should be the charm. Could we just not send emails tomorrow, double check that it produces the correct result, and re-enable them for the next day? In case there's something else we-shouldn't-have-missed-but-we-did? -- 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: Promoting i386 version over x86_64?
On Tuesday 17 November 2009 10:55:22 pm Josephine Tannhäuser wrote: I think this is a script which reads your currently used architecture and provide a dl link. please insert a x86_64 livecd and try it again! That doesn't appear to be true. I double checked that the user agent string Firefox is sending includes x86_64, and I still get the 32-bit version suggested. 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: FESCO ticket#270 - preupgrade and F-12
On Thursday 12 November 2009 12:10:13 pm James Laska wrote: *snip* So there's 174MB of usable space maximum, and usually 158MB available. preupgrade now requires at least 167MB free space on /boot: F12 installer images: 143MB (8mb larger than F11!) F12 kernel: 18MB (10mb larger than F11!) RPM/anaconda tmpfiles: =8MB (measured in stupid tests) Total: 167MB (Was 149MB in F11 - no problem!) Is part of the reason the F-12 kernel is so much larger that the debugging switch is still flipped on? 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: Orphaning packages
On Friday 30 October 2009 09:01:39 am Mary Ellen Foster wrote: 2009/7/14 Conrad Meyer ceme...@u.washington.edu: I intend to orphan the JRuby package and some of the dependencies I don't believe anything else uses. It's a piece of software upstream really doesn't intend to be packaged, and bumping to new versions is a constant struggle. Furthermore, I don't have anymore use for it. Here is the list of packages I'll orphan sometime in the next week or so: - bytelist - constantine - jcodings - jline - jna-posix - joni - jvyamlb Hello! I'm sorry to come in three and a half months after the fact (does that mean that they'll all have to be re-reviewed? :( ), but jruby is a dependency of some Java stuff that I'm currently working on so I'd like to take over these packages. MEF They're all orphaned in pkgdb. I'm not sure what process you'll need to go through to take them over (at the least, you'll probably have to talk to rel- eng to get the dead.package's removed). 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: Feature request: AMD K10 thermal sensors
On Thursday 29 October 2009 07:08:44 am Christoph Höger wrote: Am Donnerstag, den 29.10.2009, 14:51 +0100 schrieb Michal Schmidt: Dne 29.10.2009 12:38, Christoph Höger napsal(a): since a year or so the AMD K10 thermal sensors module (k10temp) seems to be floating around the web. I would appreciate some kernel packager integrating it into the fedora 11 stock kernel - since without it I can not build (and trust!) a silent cooling system. Any plans on this issue? AMD K10 sensors support has been repeatedly refused by upstream lm_sensors developers because of the sensors' unreliability. e.g. Rudolf Marek said in LKML on 2009-08-28: There is a problem that all chips of fam10h have some errata which renders the monitoring driver unusable. Some people proposed a workaround if temps look too suspicious to refuse to load. This is against a sense of monitoring to refuse the values where they don't look right. So there is no driver. So this means there is no chance to get my thermal sensors working under fedora? Perhaps see if RPMFusion will carry the kmod. 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
Packaging files that rpmbuild's auto-{requires,provides} trips on
Hi, I'm packaging some data files for a package and having trouble getting rpmbuild to finish. At some point in (I'm guessing) the autorequires/provides scripts, file(1) returns a 1 code, and rpmbuild chokes and dies. So, my question here is: 1) How do I get these scripts to ignore this file? and also: 2) Should the autorequires/provides scripts die when they stumble across a file file(1) errors on, or should they just assume it doesn't require or provide anything? Thanks, -- 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: tagging of non critical path package into F-12?
On Thursday 15 October 2009 12:51:28 am Peter Robinson wrote: Hi All, I presume that the reason that tagging requests aren't being done is due to the upcoming beta but is there a reason that non core or critical path packages can't be tagged in. I have a number of Moblin packages that fix various issues, in particular a rebuild of network-manager-netbook to fix networking against the latest NM build that hit just before the cut off. Given that none of these packages would be anywhere near any of the official spins is there any particular reason they can't be tagged in? Or if not when will they be reviewed? Peter Hi, If they're not on any of the official spins, what benefit does tagging them into dist-f12 provide over having them as updates? (Pushing updates is the suggested approach unless there's some reason it won't work in your case.) 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: Retiring ksensors, possibly id3lib as well?
On Wednesday 07 October 2009 12:55:10 pm Lyos Gemini Norezel wrote: On 10/07/2009 03:19 PM, Björn Persson wrote: Lyos Gemini Norezel wrote: Is there valid, logical, reasoning to continue to support such old code? Are there any bugs that are so severe that we can't continue using the software? No, actually. Surprisingly enough... there are no current bugs open against id3lib. If not: Why throw out working software just because it's old? Don't security risks grow exponentially as software 'bit rots'? Is it possible that id3lib is 'complete'? The id3 format isn't extremely complicated, it may just be a completely finished library. (Keep in mind, though, that I'm not familiar with the code.) As far as being a security risk... it's not a network daemon, and there's no reason it should have suid root or anything like that. I imagine the worst you could do is throw a malformed media file at it. 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: GCC update breaks PPC?
On Wednesday 09 September 2009 07:44:26 pm Michel Alexandre Salim wrote: Has anyone noticed any problem with the PPC build servers in the past day or so? I've been building LLVM with no problem on Koji, but today I've had 2 virtual memory exhaustions, and now this: http://koji.fedoraproject.org/koji/taskinfo?taskID=1667095 Thanks, Maybe http://article.gmane.org/gmane.linux.redhat.fedora.devel/120454 . 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: clang static analyzer: use it!
On Tuesday 08 September 2009 07:33:10 am Michel Alexandre Salim wrote: The latest Rawhide llvm build: http://koji.fedoraproject.org/koji/buildinfo?buildID=130997 -- which you'd probably have to install manually until it hits the Rawhide mirrors -- have clang's analyzer packaged. Once it lands properly you can have llvm, llvm-clang (the compiler) and llvm-clang-analyzer installed by simply doing yum install llvm-clang-analyzer I might push this into F-11 too, once LLVM 2.6 comes out, if simply to provide the analyzer to our F-11 users. Please do :). 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: kernel 2.6.29.6-217.2.3.fc11 compiled from source will not boot
On Sunday 09 August 2009 11:16:12 pm Markus Kesaromous wrote: There is something seriously wrong with this kernel release. Again -- the list you want is fedora-kernel-list, NOT fedora-devel-list. 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: Adding concurrency/multithreading support to par2cmdline
On Friday 31 July 2009 13:03:06 Erik van Pienbroek wrote: [snip] The current version of par2cmdline in Fedora is 0.4. This is also the latest upstream version. There hasn't been any upstream activity ever since the year 2004 [1]. Some time ago, par2cmdline was forked by somebody [2] and concurrency/multithreading support was added to it using Intel's Threading Building Blocks. Also worth noting: AIUI the -tbb fork of par2cmdline fixes bugs that were present in the original version we currently have in Fedora, as well as taking advantage of multiple cores. There is a compile-time option to disable the TBB portions (but leave the fixes for the bugs) that we plan on using on arches other than x86 and x86_64. 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: What to do with release number on new EL-5 branch
On Sunday 26 July 2009 01:47:55 pm Richard Fearn wrote: Hi, I've just had an EL-5 branch created for my disktype[1] package. The new branch is a copy of the devel branch, so the NVR is currently disktype-9-5. Should I build the package as-is (so the first EPEL version is 9-5), or clear the changelog and start from 9-1 again for the EL-5 branch? I looked on a few pages[2][3][4] for information on this, but couldn't see anything. Thanks, Rich [1]: https://admin.fedoraproject.org/pkgdb/packages/name/disktype [2]: http://fedoraproject.org/wiki/Using_CVS_FAQ_for_package_maintainers [3]: http://fedoraproject.org/wiki/PackageMaintainers/CVSAdminProcedure [4]: http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies There is nothing wrong with starting at 9-5. 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: What to do with release number on new EL-5 branch
On Sunday 26 July 2009 07:50:14 pm Toshio Kuratomi wrote:
On 07/26/2009 01:52 PM, Conrad Meyer wrote:
On Sunday 26 July 2009 01:47:55 pm Richard Fearn wrote:
Hi,
I've just had an EL-5 branch created for my disktype[1] package. The
new branch is a copy of the devel branch, so the NVR is currently
disktype-9-5.
Should I build the package as-is (so the first EPEL version is 9-5),
or clear the changelog and start from 9-1 again for the EL-5 branch?
I looked on a few pages[2][3][4] for information on this, but couldn't
see anything.
Thanks,
Rich
[1]: https://admin.fedoraproject.org/pkgdb/packages/name/disktype
[2]: http://fedoraproject.org/wiki/Using_CVS_FAQ_for_package_maintainers
[3]: http://fedoraproject.org/wiki/PackageMaintainers/CVSAdminProcedure
[4]: http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies
There is nothing wrong with starting at 9-5.
Using the disttag can make it clearer that a package comes from epel as
opposed to someone installing the Fedora package onto an EL-5 system and
expecting it to work.
https://fedoraproject.org/wiki/Packaging/DistTag
-Toshio
Er, I am not saying don't use dist, just that starting at 5%{?dist} instead
of 1%{?dist} is completely fine.
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: rawhide report: 20090721 changes
On Wednesday 22 July 2009 01:05:23 am Rahul Sundaram wrote:
On 07/21/2009 09:00 PM, Rawhide Report wrote:
Compose started at Tue Jul 21 06:15:03 UTC 2009
New package ghc-editline
Haskell %{pgk_name} library
Obvious typo and it passed through review as well.
Rahul
I noticed this, but I don't think it's a typo. In the rpm it gets evaluated as
Haskell editline library, I imagine.
--
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: rawhide report: 20090721 changes
On Wednesday 22 July 2009 01:35:34 am Peter Robinson wrote:
On 07/21/2009 09:00 PM, Rawhide Report wrote:
Compose started at Tue Jul 21 06:15:03 UTC 2009
New package ghc-editline
Haskell %{pgk_name} library
Obvious typo and it passed through review as well.
Rahul
I noticed this, but I don't think it's a typo. In the rpm it gets
evaluated as Haskell editline library, I imagine.
I think he means pgk should read pkg, or maybe even just use the
standard rpm %{name} variable.
Peter
Oh, wow, I didn't notice pgk either. Sorry! %{name} isn't entirely correct
because you get ghc-%{pkg_name} instead of %{pkg_name}.
--
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: bchunk: dead package
On Tuesday 14 July 2009 03:56:34 am Michael Schwendt wrote: https://fedorahosted.org/rel-eng/ticket/1977 bchunk is said to be obsolete, because shntool (also in Fedora) would be superior. If you disagree and find a good reason to adopt bchunk, please find a solution for the open ticket. Originally, I had sponsored Alan Olson (alano) when he wanted to take over this old package in Fedora. A deal that hasn't worked out this time. The single bugzilla ticket (#439661)is without a response/action since over a year. And attempts at contacting alano via private mail and bugzilla have been fruitless. As such, I've removed him from the FAS Packager group, too. From reading the ticket[0], it looks like the Debian patch solves the issue -- I would like to take the package. [0]: https://bugzilla.redhat.com/show_bug.cgi?id=439661 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
Orphaning packages
Hi, I intend to orphan the JRuby package and some of the dependencies I don't believe anything else uses. It's a piece of software upstream really doesn't intend to be packaged, and bumping to new versions is a constant struggle. Furthermore, I don't have anymore use for it. Here is the list of packages I'll orphan sometime in the next week or so: - bytelist - constantine - jcodings - jline - jna-posix - joni - jvyamlb If anyone wants any of them, let me know. (In case it's not obvious, they are all java packages.) 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: Orphaning par2cmdline
On Tuesday 30 June 2009 01:47:37 am Laurent Rineau wrote: I have just orphaned par2cmdline¹. I am not using that package for more than one year, now, and I was doing the minimal maintenance (taking care of mass- rebuilds and so on). Erik van Pienbroek (erik-fed...@vanpienbroek.nl) is already willing to maintain it, as he is currently maintaining NTTPgrab, that needs par2cmdline. See the discussion in the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=508772#c1 ¹) https://admin.fedoraproject.org/pkgdb/packages/name/par2cmdline -- Laurent Rineau http://fedoraproject.org/wiki/LaurentRineau Erik, I'd like to join you as a co-maintainer if it is ok with you. A package I maintain also requires par2cmdline (hellanzb). 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: Changing the default 32-bit x86 arch for Fedora 12
On Monday 15 June 2009 02:48:44 pm Jerry James wrote: On Mon, Jun 15, 2009 at 3:42 PM, Bill Nottinghamnott...@redhat.com wrote: Not that it matters for Fedora, but I doubt many people are paying $whatever_the_price_of_RHEL_is to run on a 6, 7, 10-year old machine. And RHEL 5 only supports (base) i686 or greater already. You know, I haven't seen anybody object to the i686 part yet. All of the objections, as far as I have noticed, have been to the + SSE2 part. I have an i586 machine currently running Fedora 10, but I don't object to switching to i686 only for Fedora 12. 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: Bittorrent speeds...
On Tuesday 09 June 2009 08:45:27 pm Nathanael D. Noblet wrote: Hello, Is it just me or is the torrent a bit slow. I typically download TV shows at 1.5MB/s (MB, not Mb). 150-300MB in 4-5 minutes. This torrent is sitting around 20-40KB/s... Anything I can do about that? Is the tracker swamped or ??? -- Nathanael d. Noblet T: 403.875.4613 I was getting speeds in excess of a few megabytes a second on the Fedora 11 torrents, I'm not sure why you're having trouble. 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: Maintainer Responsibilities
On Wednesday 03 June 2009 11:40:42 pm Ralf Corsepius wrote: Conrad Meyer wrote: 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? Have you ever seen an open source car? The Fedora car manufacturer is the fedora community, assembling it from upstream components. Ralf That's the idea, opensource behaves completely different from a car manufacturer. -- 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: 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: alsa forth and back?
On Friday 30 January 2009 04:20:30 pm Axel Thimm wrote: Hi, alsa was demoted from 1.0.18 to 1.0.17 in the latest kernel packages. Could someone explain why? Thanks! If you follow fedora-devel-list, you'll notice there were some regressions in 1.0.18 that broke sound for some users. They decided to revert to 1.0.17 instead of waiting for 1.0.19 release. Regards, -- Conrad Meyer kon...@tylerc.org ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: alsa forth and back?
On Friday 30 January 2009 05:01:48 pm Ozan Çağlayan wrote: Conrad Meyer wrote: On Friday 30 January 2009 04:20:30 pm Axel Thimm wrote: Hi, alsa was demoted from 1.0.18 to 1.0.17 in the latest kernel packages. Could someone explain why? Thanks! If you follow fedora-devel-list, you'll notice there were some regressions in 1.0.18 that broke sound for some users. They decided to revert to 1.0.17 instead of waiting for 1.0.19 release. Regards, 1.0.19 is already out. s/waiting for 1.0.19 release/waiting to test 1.0.19 for regressions/ -- Conrad Meyer kon...@tylerc.org ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: Switching Fedora to pae kernel by default?
On Tuesday 20 January 2009 01:06:17 am Avi Kivity wrote: Eric Paris wrote: I've got a P3 (Coppermine) with 256M memory running F10. My significant other took it with her to Antarctica (Well F9 has been to Antarctica but it'll be F10 in Antarctica next month). You can only run one app at a time and have to be patient, but it's perfectly usable (and noone cares if this laptop is lost, stolen or destroyed [aside from her being pissed she lost all her research data]). I wouldn't/couldn't to use it as a daily machine, so while I'm in favor of -PAE default, F10 is usable on such small machines. I don't care if old machines need some bit twiddling to get to work, but we aren't dead yet :) By F12 you'll be down to zero apps at the same time, and slow... We can keep the non-PAE kernel, but as non-default in recognition that technology has moved on. I have a P1 with 128M of memory running F9 just fine, I just keep it at runlevel 3. It works great. -- Conrad Meyer kon...@tylerc.org ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
