Re: Eternal 'good file hashes' list
Hi. On Tue, 20 Oct 2009 17:40:46 -0600, Stephen John Smoogen wrote: In most cases, you can get that information from the original RPM compared to the system... if you have the RPM :). rpm -Vp package_file_goes_here Which is pretty much what I want, just pulling the data from an external (signed) source instead of the local RPM database. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: How about releasing an update of xorg-x11-drv-intel for Fedora 11
James Antill wrote: Wow ... it's almost as if we need a place where developers could put _updates_ for a significant amount of time so that users could do some _testing_ on them, under each of their particular conditions. We could maybe use this instead of developers hitting the go button when they didn't get an avalanche of BZs immediately. We use updates-testing very carefully in KDE SIG. But many users only start trying out updates when they go stable, no matter how long they've been in testing. :-( So some bugs will always slip through the cracks (and not just in KDE). Any testing repository will by definition only be used by testers, i.e. by a rather small subset of our userbase. But I think that overall, our updates are a good thing. They aren't perfect, but no software is! And if you read the complaints about Vi$ta service packs rendering some systems unbootable, it's not like our competition is doing any better. AFAIK, we haven't had serious breakage like those KMail IMAP issues for a while now. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Rationale behind _cmake_skip_rpath choice in /etc/rpm/macros.cmake
Rex Dieter wrote:
I'm convinced to revert, I'll run the change by my fellow cmake
maintainers (I think we have buy-in from everyone though).
Please test that we really don't end up with standard paths like /usr/lib or
/usr/lib64 in the rpath of installed executables when doing that! Last time
we tried not using CMAKE_SKIP_RPATH, that's exactly what happened.
(Also note that %cmake_kde4 will probably always need the CMAKE_SKIP_RPATH
unless we can get CMake to understand that %{_libdir}/kde4/devel contains
only symlinks. But that's a separate issue from the above.)
Kevin Kofler
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Rationale behind _cmake_skip_rpath choice in /etc/rpm/macros.cmake
Theodore Papadopoulo wrote: According to http://www.itk.org/Wiki/CMake_RPATH_handling this is now corrected since almost two years (december 2007). We tried it in a 2.6.x, which is more recent than that, and it didn't work. (We ended up with things like /usr/lib or /usr/lib64 being set as an rpath, which is against Fedora guidelines.) The %_cmake_skip_rpath -DCMAKE_SKIP_RPATH:BOOL=ON is a change dating in last january. I cannot explain it as it was already cmake-2.6 as far as I can tell. That's because we had the issue with 2.6. Actually, cmake re-links libraries without rpath at installation time (according to the previous page). That information is outdated. 2.4 relinked the binaries, 2.6 uses some direct ELF editing hack to edit the rpath out instead (it's faster). The .shell wrappers are a KDE specificity. This is not standard cmake stuff. That's interesting. I thought these come from CMake itself. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Status of touchpad support in F12 for kdm?
Mike Cloaked wrote: Exactly which config interface are you referring to that enables this for xorg for kdm? Many systems do not have xorg.conf once installed, so presumably there is something else? Well, KDM runs as root, so usually root's KDE settings are relevant, but stock KDE doesn't have touchpad settings. We have kcm_touchpad which is being packaged, but the way its settings are loaded at startup probably only works for real KDE sessions, not KDM's minimal environment. (GDM runs an almost complete GNOME these days, they even run a window manager inside GDM! KDM has a much less bloated design.) Systemwide HAL FDI files will definitely work to set touchpad options for KDM. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Fwd: Request to update ATi OSS driver for Fedora 12
Today I upgrade my Fedora to Fedora 12 Beta, It looks very well. But I found ATi display driver does not run well. My display card is Sapphire HD3650 with 256MB GDDR3 VRAM (RV635). I choose OSS driver for my card. Glxgears runs so smoothly with xorg-x11-drv-ati because of KMS by default, nevertheless, rolling up and down in the gnome-terminal is quite slow. The performance of glxgears is about 210 frams per second. In addition, Switching to another window in Fedora 12 Beta is not as fast in Fedora 11. Later, I install xorg-x11-drv-radeonhd and set it by default in the system-config-display. Then I restart the X. I can not log into gnome. The screen turns white. I found xorg-x11-drv-radeonhd is too old, The version is 1.2.5 in the rawhide and the latest version 1.3.0 has been released for a long time. Now I turn back to xorg-x11-drv-ati. At last, I do not know which packages causes the problem, maybe xorg-x11-drv-ati, maybe xorg-x11-drv-radeonhd, maybe Mesa. So I suggest that packager updates some packge related to ATi R600/R700 display card. My Fedora 12 box is Athlon X2 4200+ and 2GB RAM, a 250GB HDD only for Fedora, a mainborad with MCP55SLI and a Sapphire HD3650. Another question, Will Fedora 12 provide Opensource 3D acceleration driver for R600/R700? -- urlhttp://www.liangsuilong.info/url Fight for freedom(3F） Ask not what your Linux distro can do for you! Ask what you can do for your Linux distro! -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fwd: Request to update ATi OSS driver for Fedora 12
On Wed, Oct 21, 2009 at 03:16:21PM +0800, Liang Suilong wrote: Another question, Will Fedora 12 provide Opensource 3D acceleration driver for R600/R700? From F12 beta announcment: * Graphics support improvements - Fedora 12 introduces experimental 3D support for AMD Radeon HD 2400 and later graphics cards. To try it out, install the mesa-dri-drivers-experimental package. -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Unresponsive maintainer for system-config-cluster
Hi, Jim Parsons left Red Hat a little while back and the only contact details I have is his Red Hat email address, which is of course no longer valid. I've opened a bugzilla #530027 as per the unresponsive maintainer procedure, but I was hoping to be able to skip the section regarding sending of messages since there seems little point sending to an email address which I know (and which other Red Hat employees can easily verify) will not be answered. Instead I've emailed the one other person who had access to that package and that has also gone unanswered (see the bugzilla). There are a number of outstanding bugs filed against system-config-cluster (including the fact that it seems that it has not passed an initial review) which I've listed out in the bugzilla. I would like to either fix (or preferably just remove) this package as it creates configs for GFS2 which are incorrect and is thus causing confusion to all who attempt to use it. Therefore this is my formal request to become maintainer of this package, Steve. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: F12 Security Updates not tagged (Re: Reminder: Tagging Policy for Fedora 12)
On Wed, Oct 21, 2009 at 02:27:46AM +0200, Christoph Wickert wrote: Am Dienstag, den 20.10.2009, 17:01 -0700 schrieb Jesse Keating: On Wed, 2009-10-21 at 01:11 +0200, Christoph Wickert wrote: What really scares me is that there is a number of security updates in bodhi that don't have a tag request in trac. Are maintainers that careless? We don't want F12 released with 6 weeks old security bugs, so it might be worth to mail their owners if there is no tag request. security is a pretty broad and vague moniker. Are any of these known privilege escalations, or could they just be crashers or DoS? AFAICS these are privilege escalations and a have CVE assigned: https://admin.fedoraproject.org/updates/ocaml-mysql-1.0.4-11.fc12 https://admin.fedoraproject.org/updates/ocaml-postgresql-1.12.3-1.fc12 https://admin.fedoraproject.org/updates/ocaml-camlimages-3.0.1-12.fc12.1 But these are already tagged and the submitter forgot to withdraw the requests. ... Didn't know I was supposed to. But as you say, all three had trac requests and rel-eng have dealt with them already. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Fedora 12 Beta
Hi, I just installed F12 Beta. Here are some thoughts 1 - during the first boot smolt panicked - there was an error related to time zones in python-sitepackages or something like that. 2 - I tried to reboot the system - ctrl + alt + del, but it stopped on process termination 3 - after reboot system wanted my root password for partition check - after I pressed each key, the system gave me a communicate about wrong password I guess this is a plymouth bug. I disabled it in grub conf and system works correctly. Is there any chance to completely remove plymouth from the system? (even from initrd) 4 - F12 boots really slow on my laptop http://www.stardust.webpages.pl/files/tmp/bootchart.png something wrong is happening while udev loading 5 - default gnome sound scheme is terrible The first impression isn't good. Regards, Michal -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
new tool: rpmguard - print important differences between RPMs
Hi, I have created a simple tool called rpmguard for checking differences between RPM packages. It is very similar to rpmdiff, but it prints only important changes, not all. Therefore it can be used every time a new package is built to easily see if something hasn’t went completely wrong. Read more on: http://kparal.wordpress.com/2009/10/21/rpmguard-print-important-differences-between-rpms/ Any comments welcome! Kamil -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
rawhide report: 20091021 changes
Compose started at Wed Oct 21 06:15:23 UTC 2009 Broken deps for ppc64 -- python-mwlib-0.11.2-3.20090522hg2956.fc12.ppc64 requires LabPlot New package adf-tribun-fonts A newsprint-like serif typeface New package gfs-ignacio-fonts A majuscule Greek font New package qtcurve-gtk2 This is a set of widget styles for Gtk2 based apps New package qtcurve-kde4 This is a set of widget styles for Qt4/KDE4 based apps New package vhostmd Virtualization host metrics daemon Removed package kerneloops Updated Packages: OpenEXR_CTL-1.0.1-9.fc12 * Tue Oct 20 2009 kwizart kwizart at gmail.com - 1.0.1-9 - Rebuild for F-12 * Fri Jul 24 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org - 1.0.1-8 - Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild OpenEXR_Viewers-1.0.1-7.fc12 * Tue Oct 20 2009 kwizart kwizart at gmail.com - 1.0.1-7 - Rebuild for F-12 * Fri Jul 24 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org - 1.0.1-6 - Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild PerceptualDiff-1.1.1-1.fc12 --- * Tue Oct 20 2009 kwizart kwizart at gmail.com - 1.1.1-1 - Update to 1.1.1 * Fri Jul 24 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org - 1.0.2-6 - Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild Pixie-2.2.6-3.fc12 -- * Tue Oct 20 2009 kwizart kwizart at gmail.com - 2.2.6-3 - Rebuild for F-12 * Fri Jul 24 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org - 2.2.6-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild boo-0.9.2.3383-2.fc12 - * Tue Oct 06 2009 Paul Lange pala...@gmx.de - 0.9.2.3383-2 - Move Boo.NAnt.Tasks.dll to boo-devel brasero-2.28.2-1.fc12 - * Tue Oct 20 2009 Matthias Clasen mcla...@redhat.com 2.28.2-1 - Update to 2.28.2 colossus-0.9.3-1.fc12 - * Fri Oct 16 2009 Bruno Wolff III br...@wolff.to - 0.9.3-1 - Rebase to 0.9.3 - Adjust script for grabbing source to be able to grab from branches - Fixed 2877055: Some GUI preferences don't load on startup - Fixed: 2864777 Illegal rangestrike over walls - Do not choose Experimental AI as A Random AI because it occasionally crashes - Fixed: 2859914 Balrog placement ignores score (aka: Balrog every 300 again, not 50) - Fixed: 2864790 Aborting load game with remote player - No GetPlayers dialog - Fixed: 2838276 my Strike Skill is wrong for nonnatives to bramble (actually, just improved the dialog to make it's meaning clearer) - Fixed: 2855208 Balrog exception in V0.9.2 (ConcurrentModificationException) - See: http://colossus.sourceforge.net/docs/RecentChangesDetails.html control-center-2.28.1-1.fc12 * Mon Oct 19 2009 Matthias Clasen mcla...@redhat.com 2.28.1-1 - Update to 2.28.1, just translation updates dmraid-1.0.0.rc16-4.fc12 * Fri Oct 16 2009 Heinz Mauelshagen hei...@redhat.com - 1.0.0.rc16-4 - bz526157: fix manual pages for dmraid.static and dm_dso_reg_tool - bz505562: ddf1 metadata format handler LSI persistent name fix - bz524168: fix pdc metadata format handler to report the correct number of devices in a RAID10 subset - bz528097: move libraries to /lib* in order to avoid catch22 with unmountable u/usr evince-2.28.1-1.fc12 * Tue Oct 20 2009 Marek Kasik mka...@redhat.com - 2.28.1-1 - Update to 2.28.1 - Add evince-pdf-print-revert.patch (reverts upstream's change - of print which revealed the bug #517310) filezilla-3.2.8.1-1.fc12 * Fri Oct 16 2009 kwizart kwizart at gmail.com - 3.2.8.1-1 - Update to 3.2.8.1 * Wed Oct 07 2009 kwizart kwizart at gmail.com - 3.2.8-1 - Update to 3.2.8 * Sat Oct 03 2009 kwizart kwizart at gmail.com - 3.2.8-0.1-rc1 - Update to 3.2.8-rc1 findutils-4.4.2-4.fc12 -- * Tue Oct 20 2009 Kamil Dudka kdu...@redhat.com - 1:4.4.2-4 - make it possible to recognize an autofs filesystem by find - add a new find's option -xautofs to not descend directories on autofs filesystems gdl-0.9-0.7.rc3.fc12 * Thu Oct 15 2009 - Orion Poplawski or...@cora.nwra.com - 0.9-0.7.rc3 - Update to 0.9rc3 - Drop gcc43, ppc64, friend patches fixed upstream - Add source for makecvstarball - Rebase antlr patch, add automake source version - Add conditionals for EPEL builds - Add %check section gnome-bluetooth-2.28.3-1.fc12 - * Tue Oct 20 2009 Bastien Nocera bnoc...@redhat.com 2.28.2-1 - Update to 2.28.2 * Tue Oct 20 2009 Bastien Nocera bnoc...@redhat.com 2.28.3-1 - Update to 2.28.3 gnome-keyring-2.28.1-2.fc12 --- * Mon Oct 19 2009 Tomas Bzatek tbza...@redhat.com - 2.28.1-1 - Update to 2.28.1 * Mon Oct 19 2009 Ray Strode rstr...@redhat.com
Re: new tool: rpmguard - print important differences between RPMs
On Wed, 2009-10-21 at 06:56 -0400, Kamil Paral wrote: I have created a simple tool called rpmguard for checking differences between RPM packages. It is very similar to rpmdiff, but it prints only important changes, not all. Therefore it can be used every time a new package is built to easily see if something hasn’t went completely wrong. Read more on: http://kparal.wordpress.com/2009/10/21/rpmguard-print-important-differences-between-rpms/ Any comments welcome! One more important difference to check between packages is changes in library symbols. There is tool exist called rpmsodiff to check it. Would be nice to see that integrated too. Alexey -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: F-12 upgrade experience with Dell D630
On Wed, Oct 21, 2009 at 1:28 PM, Peter Robinson pbrobin...@gmail.com wrote: As the Dell Latitude D630 is one of the more common devices that smolt reports being used by Fedora I thought I'd mention my upgrade experience and issues for F-12. Probably the two usual things that people query are grahics and wifi. The model I have has the Intel IWL-4965AGN device which as expected works fine. I'm having a few issues with the nouveau driver with plymouth in that it doesn't work at all but if I remove all the options from the kernel boot line it gets to X and apart from some initial corruption as GDM comes up its OK from there. I have no idea how to debug this. Try adding the parameter 'nomodeset' instead of removing any parameters. What happens then? It has certainly improved it. I wasn't in front of the machine as it booted this morning so I'll need to check out plymouth this evening but the responsiveness of the display is improved and I don't get duplicate mouse pointers now. The performance seems reduced compared to F-11 though :-( Probably the most annoying is the breakage of sound. This seems to have every other kernel/alsa/pulseaudio update and was an issue on and off right through F-11 as well so its not exactly surprising but also disappointing that one of the most common devices running Fedora has sound broken on a semi regular basis. Again some pointers in debugging this so it can be fixed by F-12 final would be great. https://fedoraproject.org/wiki/Bug_info_kernel_sound The only other very minor issue I see is that the icon spacing on the gnome panels is massive! This is currently being 'enthusiastically' discussed on fedora-desktop-list. :) Thanks for the pointer. I noticed its also been tweaked in todays rawhide. I've also noticed of late that yum performance has gone through the floor too. I never finished that. Its currently necking one core of a 2.5 ghz penryn and using nearly a gig of RAM. It literally now takes hours to update my Fit-PC (500mhz geode with 256Mb RAM). Peter -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Unresponsive maintainer for system-config-cluster
Hi, On 10/21/2009 11:11 AM, Steven Whitehouse wrote: Hi, Jim Parsons left Red Hat a little while back and the only contact details I have is his Red Hat email address, which is of course no longer valid. I've opened a bugzilla #530027 as per the unresponsive maintainer procedure, but I was hoping to be able to skip the section regarding sending of messages since there seems little point sending to an email address which I know (and which other Red Hat employees can easily verify) will not be answered. +1 from here...I already e-mailed Jim Parson a long long time (for sure more than a year) ago because of some trivial outstanding bugs in that package (missing requires, incorrect pam configuration, ...), some of them I fixed then, some are still left. I tried several times and didn't get any response. I would like to either fix (or preferably just remove) this package as it creates configs for GFS2 which are incorrect and is thus causing confusion to all who attempt to use it. Hm...I would appreciate keeping the package (...and could fix the very trivial of the remaining bugreports), how complicated would it be to fix the GFS2 configs? On the other hand, I've heard from somebody of the RH cluster team that the package is deprecated at all, how's that? Regards, Milos -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Unresponsive maintainer for system-config-cluster
Hi, On Wed, 2009-10-21 at 14:40 +0200, Milos Jakubicek wrote: Hi, On 10/21/2009 11:11 AM, Steven Whitehouse wrote: Hi, Jim Parsons left Red Hat a little while back and the only contact details I have is his Red Hat email address, which is of course no longer valid. I've opened a bugzilla #530027 as per the unresponsive maintainer procedure, but I was hoping to be able to skip the section regarding sending of messages since there seems little point sending to an email address which I know (and which other Red Hat employees can easily verify) will not be answered. +1 from here...I already e-mailed Jim Parson a long long time (for sure more than a year) ago because of some trivial outstanding bugs in that package (missing requires, incorrect pam configuration, ...), some of them I fixed then, some are still left. I tried several times and didn't get any response. I've actually found a few more since I wrote that list in the bz too. I would like to either fix (or preferably just remove) this package as it creates configs for GFS2 which are incorrect and is thus causing confusion to all who attempt to use it. Hm...I would appreciate keeping the package (...and could fix the very trivial of the remaining bugreports), how complicated would it be to fix the GFS2 configs? On the other hand, I've heard from somebody of the RH cluster team that the package is deprecated at all, how's that? Regards, Milos Well if someone wants to maintain it, then I suppose there is no issue. My understanding is that Conga is the preferred method for graphical configuration of clusters. Personally I use vi for cluster configuration :-) My main concern is the number of people who have tried to use this and landed up with incorrect/broken configurations or for whom the tool simply doesn't work. So once I've managed to get access to the package, if you or anybody else is keen to take it on then I'm happy to grant all the required privs or pass maintainership on to others as required, Steve. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Unresponsive maintainer for system-config-cluster
On Wed, Oct 21, 2009 at 01:57:14PM +0100, Steven Whitehouse wrote: Hi, On Wed, 2009-10-21 at 14:40 +0200, Milos Jakubicek wrote: Hi, On 10/21/2009 11:11 AM, Steven Whitehouse wrote: Hi, Jim Parsons left Red Hat a little while back and the only contact details I have is his Red Hat email address, which is of course no longer valid. I've opened a bugzilla #530027 as per the unresponsive maintainer procedure, but I was hoping to be able to skip the section regarding sending of messages since there seems little point sending to an email address which I know (and which other Red Hat employees can easily verify) will not be answered. +1 from here...I already e-mailed Jim Parson a long long time (for sure more than a year) ago because of some trivial outstanding bugs in that package (missing requires, incorrect pam configuration, ...), some of them I fixed then, some are still left. I tried several times and didn't get any response. I've actually found a few more since I wrote that list in the bz too. I would like to either fix (or preferably just remove) this package as it creates configs for GFS2 which are incorrect and is thus causing confusion to all who attempt to use it. Hm...I would appreciate keeping the package (...and could fix the very trivial of the remaining bugreports), how complicated would it be to fix the GFS2 configs? On the other hand, I've heard from somebody of the RH cluster team that the package is deprecated at all, how's that? Well if someone wants to maintain it, then I suppose there is no issue. My understanding is that Conga is the preferred method for graphical configuration of clusters. Personally I use vi for cluster configuration :-) I don't think its really viable to suggest that Conga is a replacement for system-config-cluster. One is a simple desktop UI for editing cluster config files. The other is a large web based management infrastructure. Certainly alot of people may want to use Conga, but I can well imagine people using s-c-c , wouldn't want to deploy a webapp just to get a tool to edit cluster config files Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Tag the F-12 updates?
On Tue, Oct 20, 2009 at 11:15:55PM -0400, Warren Togami wrote: sssd-0.6.1-2.fc12 skrooge-0.5.2-2.fc12 translate-toolkit-1.4.1-2.fc12 vhostmd-0.4-0.2.gitea2f772d.fc12 qtcurve-gtk2-0.69.0-1.fc12 qtcurve-kde4-0.69.0-1.fc12 gfs-ignacio-fonts-20090923-1.fc12 adf-tribun-fonts-1.13-1.fc12 gdl-0.9-0.7.rc3.fc12 Tagged these from the oldest bodhi requests. Need to sleep now. Will tag more tomorrow. I did quite a few more today and did some duplicate update cleanup. Will poke at this as I get time. For anyone else doing this work, please make sure to delete the updates after things are in f12-final. josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Rationale behind _cmake_skip_rpath choice in /etc/rpm/macros.cmake
Kevin Kofler wrote: Rex Dieter wrote: I'm convinced to revert, I'll run the change by my fellow cmake maintainers (I think we have buy-in from everyone though). Please test that we really don't end up with standard paths like /usr/lib or /usr/lib64 in the rpath of installed executables when doing that! Last time we tried not using CMAKE_SKIP_RPATH, that's exactly what happened. Yuck, First trial, rebuilding kdeplasma-addons without skip_rpath, yielded /usr/lib64 rpaths all over (as well as 1 instance of /usr/lib64/kde4/devel, as you alluded). -- Rex -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Beta
Dne 21.10.2009 12:31, Michał Piotrowski napsal: I just installed F12 Beta. Here are some thoughts Hello, Thank you for testing the Beta. 1 - during the first boot smolt panicked - there was an error related to time zones in python-sitepackages or something like that. 2 - I tried to reboot the system - ctrl + alt + del, but it stopped on process termination 3 - after reboot system wanted my root password for partition check - after I pressed each key, the system gave me a communicate about wrong password I guess this is a plymouth bug. I disabled it in grub conf and system works correctly. Is there any chance to completely remove plymouth from the system? (even from initrd) 4 - F12 boots really slow on my laptop http://www.stardust.webpages.pl/files/tmp/bootchart.png something wrong is happening while udev loading 5 - default gnome sound scheme is terrible Have you file Bugzilla tickets for any of these issues? If not yet, please do so and provide more detailed information if possible. Thanks, Michal -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Unresponsive maintainer for system-config-cluster
On 10/21/2009 03:21 PM, Steven Whitehouse wrote: I'm willing to accept that argument, and indeed just the same discussion is currently going on, on one of our internal lists too. The issue is who will do the work to get s-c-c back working again? Conga is actively maintained, and s-c-c is not at the moment. Every time I've asked people about it (and about fixing bugs) I've been told that its obsolete and will not be fixed. Well if they say that, then s-c-c should be really removed. I'd agree to comaintain it, but definitely don't have the capabilities (and time) to be the primary maintainer, that would need to be somebody from the RH cluster team or active in the cluster development (so that s-c-c would stay close to it). Regards, Milos -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: new tool: rpmguard - print important differences between RPMs
2009/10/21 Kamil Paral kpa...@redhat.com: Hi, I have created a simple tool called rpmguard for checking differences between RPM packages. It is very similar to rpmdiff, but it prints only important changes, not all. Therefore it can be used every time a new package is built to easily see if something hasn’t went completely wrong. Was it not easier to just add a less verbose mode to rpmdiff? -- Mat Booth A: Because it destroys the order of the conversation. Q: Why shouldn't you do it? A: Posting your reply above the original message. Q: What is top-posting? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Who do I send to get a package removed because of bad language.
On Wed, Oct 21, 2009 at 12:52:49PM -0400, Bill Nottingham wrote: I suspect the problem with that is attempting to determine a universal concept of 'offensive'. Heck, we might have no-offensive-packages-kde that conflicts with 'gnome-*', and no-offensive-packages-gnome... And you can't uninstall KDE without killing gnome since NetworkManager-gnome has a dependency on KDE... -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Virtual Machine Management - http://www.ovirt.org/ Is fearr Gaeilge bhriste ná Béarla cliste. pgp4eatsKE8k0.pgp Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Who do I send to get a package removed because of bad language.
On Wed, 2009-10-21 at 12:58 -0400, Darryl L. Pierce wrote: And you can't uninstall KDE without killing gnome since NetworkManager-gnome has a dependency on KDE... Um, what? Care to elaborate? -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating 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: Who do I send to get a package removed because of bad language.
Eric Springer (erik...@gmail.com) said: It's probably abusing the system and breaks a million guidelines, but what about making a no-offensive-packages package that explicitly conflicts with a list of offensive packages? I suspect the problem with that is attempting to determine a universal concept of 'offensive'. Heck, we might have no-offensive-packages-kde that conflicts with 'gnome-*', and no-offensive-packages-gnome... Bill -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Who do I send to get a package removed because of bad language.
On Wed, Oct 21, 2009 at 10:00:13AM -0700, Jesse Keating wrote: On Wed, 2009-10-21 at 12:58 -0400, Darryl L. Pierce wrote: And you can't uninstall KDE without killing gnome since NetworkManager-gnome has a dependency on KDE... Um, what? Care to elaborate? http://www.pastebin.org/46726 If you try to uninstall the KDE (K Desktop Environment) group then NetworkManager-gnome is marked for deletion as well. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Virtual Machine Management - http://www.ovirt.org/ Is fearr Gaeilge bhriste ná Béarla cliste. pgp2aEXLG7ESj.pgp Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Who do I send to get a package removed because of bad language.
On Wed, Oct 21, 2009 at 01:08:43PM -0400, Darryl L. Pierce wrote: On Wed, Oct 21, 2009 at 10:00:13AM -0700, Jesse Keating wrote: On Wed, 2009-10-21 at 12:58 -0400, Darryl L. Pierce wrote: And you can't uninstall KDE without killing gnome since NetworkManager-gnome has a dependency on KDE... Um, what? Care to elaborate? http://www.pastebin.org/46726 If you try to uninstall the KDE (K Desktop Environment) group then NetworkManager-gnome is marked for deletion as well. IIUC, you're mis-interpreting the YUM output there. NetworkManager-gnome doesn't have a dependancy on KDE, rather it happens to be part of the KDE (K Desktop Environment) group. ie in doing a 'groupremove' you explicitly asked YUM to remove 'NetworkManager-gnome' since its in that group. If you had just done an package level remove, eg 'yum remove kde*' then NetworkManager-gnome would not have been removed Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Who do I send to get a package removed because of bad language.
On Wed, Oct 21, 2009 at 06:22:04PM +0100, Daniel P. Berrange wrote: IIUC, you're mis-interpreting the YUM output there. NetworkManager-gnome doesn't have a dependancy on KDE, rather it happens to be part of the KDE (K Desktop Environment) group. ie in doing a 'groupremove' you explicitly asked YUM to remove 'NetworkManager-gnome' since its in that group. If you had just done an package level remove, eg 'yum remove kde*' then NetworkManager-gnome would not have been removed You're correct in that removing the KDE group attempts to remove the NetworkManager-gnome rpm. I remembered uninstalling KDE also removed NetworkManager-gnome which borked my laptop until I re-installed the RPM. That's something that should be fixed. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Virtual Machine Management - http://www.ovirt.org/ Is fearr Gaeilge bhriste ná Béarla cliste. pgpL6DB5bedco.pgp Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Who do I send to get a package removed because of bad language.
Darryl L. Pierce (dpie...@redhat.com) said: You're correct in that removing the KDE group attempts to remove the NetworkManager-gnome rpm. I remembered uninstalling KDE also removed NetworkManager-gnome which borked my laptop until I re-installed the RPM. That's something that should be fixed. I believe the documented solution is 'groupremove is bad and does not usually do what you want', FWIW. Bill -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Who do I send to get a package removed because of bad language.
On Wed, 2009-10-21 at 13:28 -0400, Darryl L. Pierce wrote: On Wed, Oct 21, 2009 at 06:22:04PM +0100, Daniel P. Berrange wrote: IIUC, you're mis-interpreting the YUM output there. NetworkManager-gnome doesn't have a dependancy on KDE, rather it happens to be part of the KDE (K Desktop Environment) group. ie in doing a 'groupremove' you explicitly asked YUM to remove 'NetworkManager-gnome' since its in that group. If you had just done an package level remove, eg 'yum remove kde*' then NetworkManager-gnome would not have been removed You're correct in that removing the KDE group attempts to remove the NetworkManager-gnome rpm. I remembered uninstalling KDE also removed NetworkManager-gnome which borked my laptop until I re-installed the RPM. That's something that should be fixed. Group removals are dangerous. Groups can share packages between them. Perhaps somebody should submit a patch to yum that gives groupremove a flag that says don't remove any package that is listed in any other group. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating 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: F-12 upgrade experience with Dell D630
On Wed, 2009-10-21 at 13:31 +0100, Peter Robinson wrote: On Wed, Oct 21, 2009 at 1:28 PM, Peter Robinson pbrobin...@gmail.com wrote: As the Dell Latitude D630 is one of the more common devices that smolt reports being used by Fedora I thought I'd mention my upgrade experience and issues for F-12. Probably the two usual things that people query are grahics and wifi. The model I have has the Intel IWL-4965AGN device which as expected works fine. I'm having a few issues with the nouveau driver with plymouth in that it doesn't work at all but if I remove all the options from the kernel boot line it gets to X and apart from some initial corruption as GDM comes up its OK from there. I have no idea how to debug this. Try adding the parameter 'nomodeset' instead of removing any parameters. What happens then? It has certainly improved it. I wasn't in front of the machine as it booted this morning so I'll need to check out plymouth this evening but the responsiveness of the display is improved and I don't get duplicate mouse pointers now. The performance seems reduced compared to F-11 though :-( Probably the most annoying is the breakage of sound. This seems to have every other kernel/alsa/pulseaudio update and was an issue on and off right through F-11 as well so its not exactly surprising but also disappointing that one of the most common devices running Fedora has sound broken on a semi regular basis. Again some pointers in debugging this so it can be fixed by F-12 final would be great. https://fedoraproject.org/wiki/Bug_info_kernel_sound The only other very minor issue I see is that the icon spacing on the gnome panels is massive! This is currently being 'enthusiastically' discussed on fedora-desktop-list. :) Thanks for the pointer. I noticed its also been tweaked in todays rawhide. I've also noticed of late that yum performance has gone through the floor too. I never finished that. Its currently necking one core of a 2.5 ghz penryn and using nearly a gig of RAM. It literally now takes hours to update my Fit-PC (500mhz geode with 256Mb RAM). Geode GX2/500 has basically zero cache (either L1 or L2), and 256MB is really the bare minimum for the install/upgrade process. You'll be swapping to disk a lot during the upgrade while the depsolving goes on, and yeah, it'll take quite a while. Dan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Who do I send to get a package removed because of bad language.
- Jesse Keating jkeat...@redhat.com wrote: On Wed, 2009-10-21 at 13:28 -0400, Darryl L. Pierce wrote: On Wed, Oct 21, 2009 at 06:22:04PM +0100, Daniel P. Berrange wrote: IIUC, you're mis-interpreting the YUM output there. NetworkManager-gnome doesn't have a dependancy on KDE, rather it happens to be part of the KDE (K Desktop Environment) group. ie in doing a 'groupremove' you explicitly asked YUM to remove 'NetworkManager-gnome' since its in that group. If you had just done an package level remove, eg 'yum remove kde*' then NetworkManager-gnome would not have been removed You're correct in that removing the KDE group attempts to remove the NetworkManager-gnome rpm. I remembered uninstalling KDE also removed NetworkManager-gnome which borked my laptop until I re-installed the RPM. That's something that should be fixed. Group removals are dangerous. Groups can share packages between them. Perhaps somebody should submit a patch to yum that gives groupremove a flag that says don't remove any package that is listed in any other group. Maybe just a confirmation (i.e: The following packages are also listed in other groups: superpackage -- awesomegroup, importantgroup uselesspackage -- evilgroup Are you sure you want to remove them? (Y/N) ? -Charley -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Who do I send to get a package removed because of bad language.
On Wed, 21 Oct 2009, Bill Nottingham wrote: Darryl L. Pierce (dpie...@redhat.com) said: You're correct in that removing the KDE group attempts to remove the NetworkManager-gnome rpm. I remembered uninstalling KDE also removed NetworkManager-gnome which borked my laptop until I re-installed the RPM. That's something that should be fixed. I believe the documented solution is 'groupremove is bad and does not usually do what you want', FWIW. groupremove does exactly what it says it will do - if we need to revisit then it'd be nice if we did it in such a way that we don't break everyone else. -sv -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Simplify non-responsive maintainers policy Part 2
On Wed, Oct 21, 2009 at 10:11:37AM +0100, Steven Whitehouse wrote: Hi, Jim Parsons left Red Hat a little while back and the only contact details I have is his Red Hat email address, which is of course no longer valid. I've opened a bugzilla #530027 as per the unresponsive maintainer procedure, but I was hoping to be able to skip the section regarding sending of messages since there seems little point sending to an email address which I know (and which other Red Hat employees can easily verify) will not be answered. Instead I've emailed the one other person who had access to that package and that has also gone unanswered (see the bugzilla). There are a number of outstanding bugs filed against system-config-cluster (including the fact that it seems that it has not passed an initial review) which I've listed out in the bugzilla. I would like to either fix (or preferably just remove) this package as it creates configs for GFS2 which are incorrect and is thus causing confusion to all who attempt to use it. Therefore this is my formal request to become maintainer of this package, I've talked to FESCo people on IRC and after some discussion I've gone ahead and reassigned ownership. Since people seem to like this, if you don't want to maintain and fix this package, please go through the orphan process rather than just retiring it. I went ahead and made the change this time for two reasons: 1) The email address for the current maintainer is not valid. 2) We have in the past had an unwritten policy about reassigning packages between a former Red Hat maintainer and a new Red Hat maintainer when the maintainer leaves the company and is no longer interested in Fedora. However, it was pointed out that this does tread in the area of the fast-track for non-responsive maintainers decided on in this FESCo ticket: https://fedorahosted.org/fesco/ticket/251 (not yet written up in the wiki. See https://fedorahosted.org/fesco/ticket/261 for getting policies written up quicker) So let's discuss -- * Should we expedite these requests in the future if the email address for the maintainer is no longer in existence? * Should we formalize the unwritten policy for Red Hat maintainers who leave the company and don't want to maintain their packages anymore? * Do we need sanity checks to be sure maintainers who do want to keep their packages do so? * Do we want something more generic that covers other compaines that pay their employees to package for Fedora? -Toshio pgpvUXqTo6AdS.pgp Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Who do I send to get a package removed because of bad language.
2009/10/21 Jesse Keating jkeat...@redhat.com: On Wed, 2009-10-21 at 13:28 -0400, Darryl L. Pierce wrote: On Wed, Oct 21, 2009 at 06:22:04PM +0100, Daniel P. Berrange wrote: IIUC, you're mis-interpreting the YUM output there. NetworkManager-gnome doesn't have a dependancy on KDE, rather it happens to be part of the KDE (K Desktop Environment) group. ie in doing a 'groupremove' you explicitly asked YUM to remove 'NetworkManager-gnome' since its in that group. If you had just done an package level remove, eg 'yum remove kde*' then NetworkManager-gnome would not have been removed You're correct in that removing the KDE group attempts to remove the NetworkManager-gnome rpm. I remembered uninstalling KDE also removed NetworkManager-gnome which borked my laptop until I re-installed the RPM. That's something that should be fixed. Group removals are dangerous. Groups can share packages between them. Perhaps somebody should submit a patch to yum that gives groupremove a flag that says don't remove any package that is listed in any other group. That is the perfect idea/solution. Sadly i can't volunteer. -- LG Thomas Dubium sapientiae initium -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Simplify non-responsive maintainers policy Part 2
On 10/21/2009 02:10 PM, Toshio Kuratomi wrote: I've talked to FESCo people on IRC and after some discussion I've gone ahead and reassigned ownership. Since people seem to like this, if you don't want to maintain and fix this package, please go through the orphan process rather than just retiring it. I went ahead and made the change this time for two reasons: 1) The email address for the current maintainer is not valid. 2) We have in the past had an unwritten policy about reassigning packages between a former Red Hat maintainer and a new Red Hat maintainer when the maintainer leaves the company and is no longer interested in Fedora. However, it was pointed out that this does tread in the area of the fast-track for non-responsive maintainers decided on in this FESCo ticket: https://fedorahosted.org/fesco/ticket/251 (not yet written up in the wiki. See https://fedorahosted.org/fesco/ticket/261 for getting policies written up quicker) So let's discuss -- * Should we expedite these requests in the future if the email address for the maintainer is no longer in existence? * Should we formalize the unwritten policy for Red Hat maintainers who leave the company and don't want to maintain their packages anymore? * Do we need sanity checks to be sure maintainers who do want to keep their packages do so? * Do we want something more generic that covers other compaines that pay their employees to package for Fedora? -Toshio Why not just require a secondary email address? This would solve most of the problems... no? Lyos Gemini Norezel attachment: Lyos_GeminiNorezel.vcf-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: F-12 upgrade experience with Dell D630
On Wed, Oct 21, 2009 at 6:47 PM, Dan Williams d...@redhat.com wrote: On Wed, 2009-10-21 at 13:31 +0100, Peter Robinson wrote: On Wed, Oct 21, 2009 at 1:28 PM, Peter Robinson pbrobin...@gmail.com wrote: As the Dell Latitude D630 is one of the more common devices that smolt reports being used by Fedora I thought I'd mention my upgrade experience and issues for F-12. Probably the two usual things that people query are grahics and wifi. The model I have has the Intel IWL-4965AGN device which as expected works fine. I'm having a few issues with the nouveau driver with plymouth in that it doesn't work at all but if I remove all the options from the kernel boot line it gets to X and apart from some initial corruption as GDM comes up its OK from there. I have no idea how to debug this. Try adding the parameter 'nomodeset' instead of removing any parameters. What happens then? It has certainly improved it. I wasn't in front of the machine as it booted this morning so I'll need to check out plymouth this evening but the responsiveness of the display is improved and I don't get duplicate mouse pointers now. The performance seems reduced compared to F-11 though :-( Probably the most annoying is the breakage of sound. This seems to have every other kernel/alsa/pulseaudio update and was an issue on and off right through F-11 as well so its not exactly surprising but also disappointing that one of the most common devices running Fedora has sound broken on a semi regular basis. Again some pointers in debugging this so it can be fixed by F-12 final would be great. https://fedoraproject.org/wiki/Bug_info_kernel_sound The only other very minor issue I see is that the icon spacing on the gnome panels is massive! This is currently being 'enthusiastically' discussed on fedora-desktop-list. :) Thanks for the pointer. I noticed its also been tweaked in todays rawhide. I've also noticed of late that yum performance has gone through the floor too. I never finished that. Its currently necking one core of a 2.5 ghz penryn and using nearly a gig of RAM. It literally now takes hours to update my Fit-PC (500mhz geode with 256Mb RAM). Geode GX2/500 has basically zero cache (either L1 or L2), and 256MB is really the bare minimum for the install/upgrade process. You'll be swapping to disk a lot during the upgrade while the depsolving goes on, and yeah, it'll take quite a while. Yea, but my Dell with a Centrino penryn processor with 6 meg of cache and 4 gig of RAM was horrific and earlier in F-12 it wasn't that bad even on the Geode. I couldn't use my Dell for over 20 mins while doing a single days worth of the current rawhide pushes. Peter -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: F-12 upgrade experience with Dell D630
On Tue, Oct 20, 2009 at 7:22 PM, Adam Williamson awill...@redhat.com wrote: On Tue, 2009-10-20 at 11:17 +0100, Peter Robinson wrote: Hi All, As the Dell Latitude D630 is one of the more common devices that smolt reports being used by Fedora I thought I'd mention my upgrade experience and issues for F-12. Probably the two usual things that people query are grahics and wifi. The model I have has the Intel IWL-4965AGN device which as expected works fine. I'm having a few issues with the nouveau driver with plymouth in that it doesn't work at all but if I remove all the options from the kernel boot line it gets to X and apart from some initial corruption as GDM comes up its OK from there. I have no idea how to debug this. Try adding the parameter 'nomodeset' instead of removing any parameters. What happens then? It all works just fine with modesetting off. Peter -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Notice: Fedora 12 Tagging Status Update
Fedora Release Engineering decided to deal with the 250+ backlog of Bodhi update requests by tagging them all into f12-final. Bodhi is now disabled for Fedora 12 updates. Questions = 1) Why tag all Update requests into f12-final? At this point of the schedule we realized that there were updates sitting in the queue from since October. They were sitting there. Not getting pushed to any repository. Rawhide gives these packages several more weeks of testing exposure. This was decided to be better than a flood of day zero updates that are poorly tested. 2) When will we be able to submit Updates again? Rel-eng will decide when to begin accepting Updates for Fedora 12 again during Monday's rel-eng meeting. Meanwhile please use the rel-eng ticketing system to request tagging into f12-final. 3) How do I file a tag request to include my package into Fedora 12? https://fedorahosted.org/rel-eng/ Please file tag request tickets here if you want your package build to be included in Fedora 12. Please include details like: * Full Name-Version-Release of your package(s) * What changed? * How risky is this change? * How important is this change? * How well tested is this package build? * Is this package in the critical-path list? 4) Which packages are critical-path? https://fedorahosted.org/pipermail/autoqa-results/2009-October/001714.html Unfortunately we do not yet have a permanent URL with the critical-path list. This page contains an auto-generated list of critical-path packages as of today. If your package is not critical-path and not a risk to others to update, then it is highly likely proper to tag at this point of the schedule. 5) How many untagged packages are there? koji list-tagged --latest dist-f12-updates-candidate This command lists all packages that are not tagged for f12-final. In some cases these are false positives because a newer package is instead tagged into f12-final. After you have tested your package and verified it doesn't make things worse, please file rel-eng tickets to have it included. Please direct questions to fedora-devel-list. Warren Togami wtog...@redhat.com ___ Fedora-devel-announce mailing list fedora-devel-annou...@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-announce -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
On updates to stable releases
I don't really want to revive the thread about automake 1.11, but I do want to point out that it did break actual buildability: http://koji.fedoraproject.org/koji/getfile?taskID=1761549name=build.log Please, people. Don't update things in stable releases just for fun. Particularly if your package is part of the build environment for something else. I don't care if it bills itself as just a bugfix release; that's how you know it's lying. - ajax 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: On updates to stable releases
On Wed, 21 Oct 2009, Adam Jackson wrote: I don't really want to revive the thread about automake 1.11, but I do want to point out that it did break actual buildability: http://koji.fedoraproject.org/koji/getfile?taskID=1761549name=build.log Please, people. Don't update things in stable releases just for fun. Particularly if your package is part of the build environment for something else. I don't care if it bills itself as just a bugfix release; that's how you know it's lying. Except when it is just a bugfix release and it maintains api compat. Yum has been, on the whole, pretty good about maintaining compatibility while fixing bugs. -sv -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: On updates to stable releases
On Wed, 2009-10-21 at 16:30 -0400, Seth Vidal wrote: On Wed, 21 Oct 2009, Adam Jackson wrote: I don't really want to revive the thread about automake 1.11, but I do want to point out that it did break actual buildability: http://koji.fedoraproject.org/koji/getfile?taskID=1761549name=build.log Please, people. Don't update things in stable releases just for fun. Particularly if your package is part of the build environment for something else. I don't care if it bills itself as just a bugfix release; that's how you know it's lying. Except when it is just a bugfix release and it maintains api compat. Yum has been, on the whole, pretty good about maintaining compatibility while fixing bugs. I was being hyperbolic, yes. - ajax 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: On updates to stable releases
On Wed, 21 Oct 2009, Adam Jackson wrote: I don't really want to revive the thread about automake 1.11, but I do want to point out that it did break actual buildability: http://koji.fedoraproject.org/koji/getfile?taskID=1761549name=build.log Please, people. Don't update things in stable releases just for fun. Particularly if your package is part of the build environment for something else. I don't care if it bills itself as just a bugfix release; that's how you know it's lying. It's getting to the point where we need something more than please. -Mike -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: On updates to stable releases
On Wed, 21 Oct 2009, Adam Jackson wrote: On Wed, 2009-10-21 at 16:30 -0400, Seth Vidal wrote: On Wed, 21 Oct 2009, Adam Jackson wrote: I don't really want to revive the thread about automake 1.11, but I do want to point out that it did break actual buildability: http://koji.fedoraproject.org/koji/getfile?taskID=1761549name=build.log Please, people. Don't update things in stable releases just for fun. Particularly if your package is part of the build environment for something else. I don't care if it bills itself as just a bugfix release; that's how you know it's lying. Except when it is just a bugfix release and it maintains api compat. Yum has been, on the whole, pretty good about maintaining compatibility while fixing bugs. I was being hyperbolic, yes. Something I've discovered in the not-so-distant past is that hyperbole is not always grokked by non-native speakers and tends to cause drama escalation. Your main point, though - that people in the build and critpath should be careful with upgrades is completely correct. -sv -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Eternal 'good file hashes' list
Am 2009-10-21 08:47, schrieb Ralf Ertzinger: Hi. On Tue, 20 Oct 2009 17:40:46 -0600, Stephen John Smoogen wrote: In most cases, you can get that information from the original RPM compared to the system... if you have the RPM :). rpm -Vppackage_file_goes_here Which is pretty much what I want, just pulling the data from an external (signed) source instead of the local RPM database. Running on the compromised system, or running somewhere else? Where are you running rpm from? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fwd: Request to update ATi OSS driver for Fedora 12
On Wed, 2009-10-21 at 15:16 +0800, Liang Suilong wrote: Today I upgrade my Fedora to Fedora 12 Beta, It looks very well. But I found ATi display driver does not run well. My display card is Sapphire HD3650 with 256MB GDDR3 VRAM (RV635). I choose OSS driver for my card. Glxgears runs so smoothly with xorg-x11-drv-ati because of KMS by default, nevertheless, rolling up and down in the gnome-terminal is quite slow. The performance of glxgears is about 210 frams per second. In addition, Switching to another window in Fedora 12 Beta is not as fast in Fedora 11. Later, I install xorg-x11-drv-radeonhd and set it by default in the system-config-display. Then I restart the X. I can not log into gnome. The screen turns white. I found xorg-x11-drv-radeonhd is too old, The version is 1.2.5 in the rawhide and the latest version 1.3.0 has been released for a long time. Now I turn back to xorg-x11-drv-ati. At last, I do not know which packages causes the problem, maybe xorg-x11-drv-ati, maybe xorg-x11-drv-radeonhd, maybe Mesa. So I suggest that packager updates some packge related to ATi R600/R700 display card. Fedora doesn't really care about the radeonhd driver. We may well even remove it at some point soon. The ati driver is the one you should use on Fedora, that's why it's the default. You do not get 3D acceleration out of the box on that card, r600 3D acceleration is too early to be enabled by default. If you want to try it out, install the mesa-dri-drivers-experimental package. For the slow 2D performance - _how_ slow is it, really? gnome-terminal has never been much of a speed demon. Does it get any faster if you boot with 'nomodeset' as a kernel parameter? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Beta
On Wed, 2009-10-21 at 12:31 +0200, Michał Piotrowski wrote: Hi, I just installed F12 Beta. Here are some thoughts 1 - during the first boot smolt panicked - there was an error related to time zones in python-sitepackages or something like that. Could you try to reproduce and provide more precise details on the error? There's not a lot we can do with that level of detail. 2 - I tried to reboot the system - ctrl + alt + del, but it stopped on process termination It _may_ not actually have stopped, rebooting from firstboot can be quite sluggish I've noticed, but goes through eventually. 3 - after reboot system wanted my root password for partition check - after I pressed each key, the system gave me a communicate about wrong password The fact that it wanted to do fsck at all may be https://bugzilla.redhat.com/show_bug.cgi?id=522969 , which is fixed in tomorrow's Rawhide. I guess this is a plymouth bug. I disabled it in grub conf and system works correctly. Is there any chance to completely remove plymouth from the system? (even from initrd) From a quick look, we don't have a bug filed for the fact that entering the root password at this point doesn't work with Plymouth. Could you please file one with a full description, and mark it as blocking F12Blocker? Thanks. 4 - F12 boots really slow on my laptop http://www.stardust.webpages.pl/files/tmp/bootchart.png something wrong is happening while udev loading Please file a bug for this, on 'udev' component for now, and CC Harald Hoyer (hhoyer at redhat). Thanks! 5 - default gnome sound scheme is terrible This is a pretty subjective topic. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Status of touchpad support in F12 for kdm?
On Mon October 19 2009, mcloaked wrote: Given the recent long thread concerning upstream decisions about defaults in Thunderbird 3.0beta4 it seems to me that just because upstream makes a specific decision does not always mean that is the best decision. What That discussion was not about the default in general, but about changing the default in an update for a stable Fedora release. I guess the default for Rawhide/F12 will be the same that upstream has. Regards Till 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: F-12 upgrade experience with Dell D630
On Wed, 2009-10-21 at 13:28 +0100, Peter Robinson wrote: Try adding the parameter 'nomodeset' instead of removing any parameters. What happens then? It has certainly improved it. I wasn't in front of the machine as it booted this morning so I'll need to check out plymouth this evening but the responsiveness of the display is improved and I don't get duplicate mouse pointers now. The performance seems reduced compared to F-11 though :-( In that case, could you file a bug, with appropriate information attached - see https://fedoraproject.org/wiki/How_to_debug_Xorg_problems - on the xorg-x11-drv-nouveau component, describing the symptoms, how 'nomodeset' changes them, and including the output of 'lspci -nn' to identify your card? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: new tool: rpmguard - print important differences between RPMs
On Wed, 2009-10-21 at 15:12 +, Mat Booth wrote: 2009/10/21 Kamil Paral kpa...@redhat.com: Hi, I have created a simple tool called rpmguard for checking differences between RPM packages. It is very similar to rpmdiff, but it prints only important changes, not all. Therefore it can be used every time a new package is built to easily see if something hasn’t went completely wrong. Was it not easier to just add a less verbose mode to rpmdiff? As we discussed in the QA meeting this week, that may well be ultimately what this becomes, but for now it's a separate tool while Kamil works on it. He may well end up submitting it as a patch for rpmdiff in the end. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
F12 media-less installer totally broken
Hi folks, I tried installing F12 fresh today without burning media. I had F11 on a lvm, and was installing F12 on another. Here's what happened: - Put the iso on a ntfs partition - Put the vmlinuz+initrd.img in F11's grub .. and boot into the installer, pointing it to install from HDD - The installer cannot pickup the iso - As an alternate I copied the iso to a server, and NFS shared its folder - I reboot the installer, point it to nfs .. again it fails to start anaconda - Third trial .. on that server I loop mount the iso on /opt and NFS share that - Boot installer, it tried to mount server:/opt/images (which fails!) (only /opt is shared) - Fourth trial: I expand the iso image completely on disk into a new directory, boot into the installer pointing it at that - Installer finally picks up, anaconda starts .. I click next a few times, partition and format my disk, then an error message mentions cannot load image #1, please insert the CD and try again ... arrgh - I give up, burn a DVD, and install from it just fine Regards -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Fedora 12 Blocker Bug Meeting #1 :: 2009-10-23 @ 15:00 UTC (11 AM EDT)
When: Friday, 2009-10-23 @ 15:00 UTC (11 AM EDT) Where: #fedora-bugzappers on irc.freenode.net We will be doing a follow-up to the meeting that was held today. Below is the list bugs still blocking the release of Fedora 12. 527048 - nss - NEW - nss-sysinit: system-wide nss sql empty key database shouldn't have a password 528005 - xorg-x11-drv-nouveau - NEW - X server crash 528222 - initscripts - NEW - LiveCD intermittently gets stuck during shutdown 509733 - gvfs - NEW - Process /usr/libexec/gvfs-gdu-volume-monitor received signal 11 528909 - DeviceKit-disks - NEW - DevKit 95-devkit-disks.rules should avoid scan all DM devices 517839 - hsqldb - NEW - bitxor and bitor both mapped to single bitor function 523110 - hsqldb - NEW - autoincrement bustage on column redefinition 513864 - firefox - NEW - Firefox crashes 501769 - kernel - NEW - intel hda: snd_pcm_avail/snd_pcm_delay overflows 523378 - kernel - NEW - [kernel] file system errors for recent 2.6.31 kernels 530169 - kernel - NEW - nouveau + gdm crashes 493472 - kernel - NEW - [945GM] KMS: LVDS wrongly detected as connected, DVI monitor resolution incorrectly set 514760 - redhat-lsb - NEW - cleanup script segfaults during yum upgrade 498968 - distribution - NEW - Fedora 12 Virtualization Target Blocker 521519 - gedit - NEW - gedit 2.27 leaking memory 527089 - plymouth - NEW - repaire console is not accessible 520480 - kde-settings - NEW - F12 KDE blocker 523815 - nautilus - NEW - nautilus hoses vino 514415 - xorg-x11-server - NEW - X server locks up every time notification is about to be displayed 518962 - xorg-x11-drv-ati - NEW - ATI - Caught signal 11 (Segmentation fault). Server aborting 522929 - xorg-x11-drv-ati - NEW - repeated system crashes 521512 - kernel - ASSIGNED - KMS: X Window Frozen with Radeon XPRESS 200M 526154 - thunderbird - ASSIGNED - localisation breaks sending mail 512845 - xulrunner - ASSIGNED - setroubleshoot: SELinux is preventing firefox from changing a writable memory segment executable. 526699 - anaconda - ASSIGNED - CryptoError: luks_format failed for '/dev/mapper/VolGroup-LogVol00' 517491 - anaconda - ASSIGNED - Anaconda fails if filesystem should be shrunk 528312 - xorg-x11-server - ASSIGNED - udev takes almost 100% CPU on resume from suspend (and Xorg are to be blamed) 522187 - pango - ASSIGNED - Java (so Eclipse too) crashes 521322 - xorg-x11-drv-ati - ASSIGNED - no graphics and no console for F12-Snap1-x86_64-Live 522137 - xorg-x11-drv-ati - ASSIGNED - Test_Day:2009-09-09_Radeon: Multiple tests crash X.org 522970 - xorg-x11-drv-ati - ASSIGNED - popup messages unreadable 493058 - anaconda - ASSIGNED - Custom partitioning creation/edit causes traceback 526549 - anaconda - ASSIGNED - rats_install kickstart fails due to swap device prompt 526021 - yaboot - ASSIGNED - f12 beta failed to boot on ppc platform after autopart and encrypted installation 506075 - kernel - ASSIGNED - snd_intel8x0: snd_pcm_avail()/ snd_pcm_delay() overflow 514000 - alsa-lib - ASSIGNED - Aureon 5.1 MkII can't do 5.1 anymore 523768 - alsa-utils - ASSIGNED - [abrt] crash detected in alsa-utils-1.0.21-2.fc12 514600 - kernel - ASSIGNED - Intel 82G965 requires 'nomodeset' workaround to get working text-mode 528537 - kernel - ASSIGNED - fails to get kickstart file over nfs. 528048 - xorg-x11-drv-intel - ASSIGNED - display black after resume 516057 - webkitgtk - ASSIGNED - gets whacked by selinux execmem check 527426 - plymouth - ASSIGNED - (plymouth) No text prompt for encryption password (but keyboard input is accepted) 520750 - PackageKit - ASSIGNED - Software Update windows checks for update does not stop .. 512944 - fast-user-switch-applet - ASSIGNED - fast-user-switching locks up login screen 527920 - gdm - ASSIGNED - gdm doesn't show user list and crashes - unable to login 523800 - xorg-x11-drv-neomagic - ASSIGNED - X.org doesn't work on ThinkPad 600X (NeoMagic MagicGraph256ZX) 527520 - anaconda - MODIFIED - post-install lxde system boots in text mode 526697 - anaconda - MODIFIED - Trying to change encryption status of partition ends with error message: The mount point is in use. Please pick another 527952 - anaconda - MODIFIED - AttributeError: 'NoneType' object has no attribute 'disk' 528317 - anaconda - MODIFIED - anaconda traceback in getDefaultTimeZone KeyError en_AU 529766 - NetworkManager - MODIFIED - applet won't start 517260 - anaconda - MODIFIED - liveinst fails at partitioning screen 519766 - nss - MODIFIED - (nss) FORTIFY_SOURCE buffer overflows and other issues in test suite 520162 - nss - MODIFIED - nss-devel no longer provides pkgconfig(nss) 524168 - anaconda - MODIFIED - Wrong RAID10 recognition in anaconda while dmraid shows correct values 529209 - livecd-tools - MODIFIED - PATCH: Tell dracut not to ask for LUKS passwords or activate mdraid sets 528097 - dmraid - MODIFIED - /sbin/dmraid needs possibly unmounted /usr/lib
Re: Simplify non-responsive maintainers policy Part 2
Lyos Gemini Norezel lyos.gemininore...@gmail.com writes: Why not just require a secondary email address? Require a secondary email address? Not everyone has one, or wants to hand it over if they do. That sounds more like a recipe for driving maintainers away than making sure you can contact them. regards, tom lane -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Beta
On Wed, 2009-10-21 at 17:08 -0500, Mike McGrath wrote: On Wed, 21 Oct 2009, Adam Williamson wrote: On Wed, 2009-10-21 at 12:31 +0200, Michał Piotrowski wrote: Hi, I just installed F12 Beta. Here are some thoughts 1 - during the first boot smolt panicked - there was an error related to time zones in python-sitepackages or something like that. Could you try to reproduce and provide more precise details on the error? There's not a lot we can do with that level of detail. The smolt firstboot thing is already fixed, just didn't make it in time for the beta, my bad. Is there a bug report I can reference so I can add this to the Common Bugs page with a reasonable level of detail? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: problem with dns
2009/10/21 Michał Piotrowski mkkp...@gmail.com: Hi, This is a problem that touches some of Fedora services. I've got a network 192.168.101.0 192.168.101.1 - this is my router 192.168.101.200 - ozzy - my F11 server 192.168.101.100 - dio - my Windows 6 workstation I use two DNS servers nameserver 192.168.1.1 nameserver 194.204.159.1 The problem shows up when my network 192.168.101.0 lose a connection with 192.168.1.0 and my primary DNS server is not available. [...] Every time when I try to use samba I get no response from ozzy. Here is what is happening for mc I think that such behavior is clearly wrong. But it's a long term issue. So maybe I'm wrong and this is a correct behavior? The daemons are doing reverse DNS lookups on the IP addresses and not getting any answers. You can either tweak that in the resolv.conf file so it doesn't take so long to give up (see the man page for options) or configure your services to ignore it. For sshd you just need to uncomment the following line in sshd.conf: #UseDns no But I don't see anything wrong with how things are happening in this situation. -- Giovanni. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Unable to download Fedora 12 beta using jigdo
Hi, I'm trying to download F12 beta DVD x86_64 iso using jigdo (I've used jigdo to download previous versions too). It successfully downloaded all files, but it doesn't accept downloaded install.img file and tries to download it again and again. I've tried downloading install.img several times (also using stand alone download applications) but jigdo doesn't accept any of them. As a result, jigdo doesn't compose the final .iso image because of 1 missing file. Does anybody have any ideas about the reason of failure? Has anybody downloaded F12 beta x86_64 using jigdo successfully? Thanks, Hedayat -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fwd: Request to update ATi OSS driver for Fedora 12
To Tomasz, Thank you! I have enabled compiz with ati oss drivers. To Adam Williamson Oh..So I need to remove radeonhd driver in my box. RadeonHD seems to be one part of xorg-x11-drv-ati. They provides the same things to ati users. But radeonhd only stand for R500/R600 later. Yes, When rolling up and down in the gnome-terminal. I move up my mouse but the scroll bar still stay at there for about 0.5 seconds to 1 seconds. You can feel delay obviously. But I do not try to disable KMS. Let me try it and report the problem to here. -- urlhttp://www.liangsuilong.info/url Fight for freedom(3F） Ask not what your Linux distro can do for you! Ask what you can do for your Linux distro! -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: the mass rebuild and i586 rpms?
Milos Jakubicek wrote: Most probably those are the packages which failed during the mass rebuild...there are still plenty of them: http://mjakubicek.fedorapeople.org/need-rebuild.html That list is out of date. I fixed clutter-gtkmm to build a while ago because it had broken dependencies, and the fixed build got tagged into dist-f12 already (and dist-f13 inherits it from there too). Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fwd: Request to update ATi OSS driver for Fedora 12
On Thu, 2009-10-22 at 08:36 +0800, Liang Suilong wrote: Oh..So I need to remove radeonhd driver in my box. RadeonHD seems to be one part of xorg-x11-drv-ati. They provides the same things to ati users. But radeonhd only stand for R500/R600 later. radeonhd is not part of ati, they are effectively in competition. They're two different drivers for the same hardware. ati is the one that Fedora supports. Yes, When rolling up and down in the gnome-terminal. I move up my mouse but the scroll bar still stay at there for about 0.5 seconds to 1 seconds. You can feel delay obviously. But I do not try to disable KMS. Let me try it and report the problem to here. Thanks, please let us know how it goes. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: On updates to stable releases
Adam Jackson wrote: I don't really want to revive the thread about automake 1.11, but I do want to point out that it did break actual buildability: http://koji.fedoraproject.org/koji/getfile?taskID=1761549name=build.log So xorg-x11-server needs a one-line patch to build again? I fail to see the big issue there. Please, people. Don't update things in stable releases just for fun. Particularly if your package is part of the build environment for something else. That also means something else may need the updated package to even build at all, and in fact this is the reason the automake update was requested and pushed. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: On updates to stable releases
On Wed, Oct 21, 2009 at 4:28 PM, Adam Jackson wrote: I don't really want to revive the thread about automake 1.11, but I do want to point out that it did break actual buildability: http://koji.fedoraproject.org/koji/getfile?taskID=1761549name=build.log Please, people. Don't update things in stable releases just for fun. Particularly if your package is part of the build environment for something else. I don't care if it bills itself as just a bugfix release; that's how you know it's lying. You missed the whole point of the previous discussion. It didn't go unnoticed, did it? I mean, a build failure is hard to miss. As soon as it fails to build you know that it failed to build. You can't be happy as if your package has been built successfully when it actually failed. If you are happy that your package failed to build, then either there is a problem with you or a problem with the rest of us. In either case the outcome is the same: The package *failed* to build. Please come up with an example where there are no warnings in the build logs and the package builds and installs fine, but it is broken. Orcan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
[Bug 530045] New: Dep versions in spec file
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Dep versions in spec file https://bugzilla.redhat.com/show_bug.cgi?id=530045 Summary: Dep versions in spec file Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: perl-Module-Install AssignedTo: st...@silug.org ReportedBy: e...@membled.com QAContact: extras...@fedoraproject.org CC: st...@silug.org, fedora-perl-devel-list@redhat.com Classification: Fedora The spec file doesn't give versions for some requirements, this tightens it up: --- perl-Module-Install.spec~ 2009-07-27 16:39:39.0 +0100 +++ perl-Module-Install.spec2009-10-21 11:19:31.0 +0100 @@ -15,10 +15,10 @@ BuildRequires: perl(Archive::Tar) BuildRequires: perl(CPAN) -BuildRequires: perl(Devel::PPPort) -BuildRequires: perl(ExtUtils::Install) +BuildRequires: perl(Devel::PPPort) = 3.16 +BuildRequires: perl(ExtUtils::Install) = 1.52 BuildRequires: perl(ExtUtils::MakeMaker) -BuildRequires: perl(ExtUtils::ParseXS) +BuildRequires: perl(ExtUtils::ParseXS) = 2.19 BuildRequires: perl(File::Remove) = 1.42 BuildRequires: perl(File::Spec) BuildRequires: perl(JSON) -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 530045] Dep versions in spec file
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=530045 --- Comment #1 from Ed Avis e...@membled.com 2009-10-21 06:27:24 EDT --- Note that according to its Makefile.PL, Module::Install requires Devel::PPPort version 3.16. But perl 5.10, currently the version in rawhide, only provides 3.13. I don't know what you will decide to do about this. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 530137] New: Fedora::Bugzilla - $bug-blocks_bug() fail
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Fedora::Bugzilla - $bug-blocks_bug() fail https://bugzilla.redhat.com/show_bug.cgi?id=530137 Summary: Fedora::Bugzilla - $bug-blocks_bug() fail Product: Fedora Version: 11 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-Fedora-Bugzilla AssignedTo: cw...@alumni.drew.edu ReportedBy: jpi...@redhat.com QAContact: extras...@fedoraproject.org CC: cw...@alumni.drew.edu, fedora-perl-devel-list@redhat.com, mmasl...@redhat.com Classification: Fedora Target Release: --- Created an attachment (id=365567) -- (https://bugzilla.redhat.com/attachment.cgi?id=365567) test script Description of problem: When I try to get bugs that bz depends on, it fails in a way below and returns only one bz 0. Version-Release number of selected component (if applicable): 0.10-1 - I tried 0.13 from CPAN and problem is still there. How reproducible: Always Steps to Reproduce: run attached script Actual results: blocks_bug Use of uninitialized value $_[1] in exists at /usr/lib/perl5/vendor_perl/5.10.0/MooseX/AttributeHelpers/MethodProvider/ImmutableHash.pm line 10. 0 all_blocked_bugs Expected results: blocks_bug 499884 all_blocked_bugs -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 530137] Fedora::Bugzilla - $bug-blocks_bug() fail
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=530137 --- Comment #1 from Jiri Pirko jpi...@redhat.com 2009-10-21 13:02:43 EDT --- Well all_blocked_bugs() returns bzs listed in Blocks field. This suggest following: Depends on *eq* blocks_bug() Blocks *eq* all_blocked_bugs() That doesn't sound good to me. Thoughts? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 529220] Fedora::Bugzilla - script gets stuck when getting a big BZ
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=529220 --- Comment #8 from Chris Weyl cw...@alumni.drew.edu 2009-10-21 23:51:41 EDT --- Ok, so no response from the author. I'm going to deploy 3.33 into production on a couple systems at work tomorrow and see what happens... Assuming everything goes OK (as I believe it will) I'll update our package here. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 530137] Fedora::Bugzilla - $bug-blocks_bug() fail
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=530137 Chris Weyl cw...@alumni.drew.edu changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #2 from Chris Weyl cw...@alumni.drew.edu 2009-10-22 01:44:42 EDT --- Yeah... Not good :) I've updated the blocks/depends atts and added tests to validate it. I haven't pushed it to the CPAN as 0.14 yet as I have some additional work to square away with the alias bits, but it is out on github... As well as documentation to write :) -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
