Re: rawhide report: 20100115 changes

2010/1/15 Rawhide Report wrote: > Compose started at Fri Jan 15 08:15:05 UTC 2010 > [..] >        ghc-cgi-devel-3001.1.7.1-3.fc13.i686 requires ghc = 0:6.10.4 >        ghc-cgi-devel-3001.1.7.1-3.fc13.i686 requires ghc-network-devel = > 0:2.2.1.4 >        ghc-cgi-devel-3001.1.7.1-3.fc13.i686 requir

Re: Mirrorlist problems?

On Wed, 20 Jan 2010, Robert 'Bob' Jensen wrote: > > - "Andrew McNabb" wrote: > > > I just installed a new machine with Fedora 12 this evening, and > > Anaconda > > gave an error about not being able to get the repository metadata. I > > ended up switching the URL from the default mirrorlist

Re: Orphaning Candidate packages for removal due to FTBFS, implications

On Tue, 19 Jan 2010, Jens Petersen wrote: > - "Seth Vidal" wrote: >> which is why All we're suggesting is filing a bug and/or some other >> kind of notification that says "are you alive". > > To clarify, only for FTBFS, right? > There's a lot more details involved. When I have the full spe

Re: Mirrorlist problems?

- "Andrew McNabb" wrote: > I just installed a new machine with Fedora 12 this evening, and > Anaconda > gave an error about not being able to get the repository metadata. I > ended up switching the URL from the default mirrorlist to a specific > mirror, and the installation worked. Now tha

Mirrorlist problems?

I just installed a new machine with Fedora 12 this evening, and Anaconda gave an error about not being able to get the repository metadata. I ended up switching the URL from the default mirrorlist to a specific mirror, and the installation worked. Now that the system is installed, I tried to use

Re: Orphaning Candidate packages for removal due to FTBFS, implications

- "Seth Vidal" wrote: > which is why All we're suggesting is filing a bug and/or some other > kind of notification that says "are you alive". To clarify, only for FTBFS, right? Jens -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Re: New plugin for system-config-network (PPTP)

>*2009/12/28 Сергей Варюхин >:* >>* Hi, i created new plugin for system-config-network (PPTP-connection type) *>>* and posted my patch in RFE report to bugzilla *>>* (https://bugzilla.redhat.com/show_bug.cgi?id=550054). Also i have send *>>* p

Re: ABRT frustrating for users and developers

On Tue, Jan 19, 2010 at 10:06 PM, Adam Williamson wrote: > On Tue, 2010-01-19 at 11:44 +0100, Jiri Moskovcak wrote: > > > > Package updates to ABRT > > > should receive a lot of testing in order to avoid rushed "stable" > > releases > > > that result in less useful bz tickets. > > > > I agree, we

Re: libcdio update

Hi, On 01/19/2010 09:43 AM, Adrian Reber wrote: > I would like to update libcdio to the latest version (0.82). This > requires a rebuild of its dependencies: > > audacious-plugins > gvfs > kover > libcddb > oxine > pycdio > qmmp > xfce4-cddrive-plugin > xmms2 > > If the maintainers of the above pa

Re: [389-devel] Please review: Allow modrdn to move subtree and rename non-leaf node

On 01/19/2010 01:50 PM, Rich Megginson wrote: > Noriko Hosoi wrote: > >> Allow modrdn to move subtree and rename non-leaf node >> >> This patch includes >> - replacing the entrydn index with the entryrdn index >> - replacing a full DN in each entry in the DB with an RDN >>

Re: ABRT frustrating for users and developers

On Tue, 2010-01-19 at 11:44 +0100, Jiri Moskovcak wrote: > > Package updates to ABRT > > should receive a lot of testing in order to avoid rushed "stable" > releases > > that result in less useful bz tickets. > > I agree, we (ABRT team) do a lot of testing before new release, but of > > course c

Re: [389-devel] Please review: Allow modrdn to move subtree and rename non-leaf node

Noriko Hosoi wrote: > Allow modrdn to move subtree and rename non-leaf node > > This patch includes > - replacing the entrydn index with the entryrdn index > - replacing a full DN in each entry in the DB with an RDN > - extending Slapi_Entry, entry2str, and str2entry to absorb the

Re: Orphaning Candidate packages for removal due to FTBFS, implications

On Sun, 17 Jan 2010 20:52:12 +0100 Till Maas wrote: > The list of packages you announced that are going to be orphaned and > the list of packages that were orphaned are not the same. > recordmydesktop was on the to-be-orphaned list but afaics was not > orphaned and also was not mentioned in your

Re: Orphaning Candidate packages for removal due to FTBFS, implications

On Sun, 17 Jan 2010 20:48:25 +0100 Till Maas wrote: > On Sat, Jan 16, 2010 at 10:39:50AM -0700, Kevin Fenzi wrote: > > On Sat, 16 Jan 2010 10:39:54 +0100 > > Till Maas wrote: > > > > > > Indeed. I don't see much activity from them. > > > > Have you tried sending them an email? > > > > If not,

Re: Sources file audit - 2010-01-06

On Tue, 19 Jan 2010 13:18:33 +0100 Thomas Moschny wrote: > 2010/1/10 Kevin Fenzi : > > thm:BADSOURCE:httperf-0.9.0.tar.gz:httperf > > Project URLs changed. Fixed in CVS, not rebuilt. > > (But why was this BADSOURCE? Checked, and both tar files at old url > ftp://ftp.hpl.hp.com/pub/httperf/httpe

Meeting Summary/Minutes for (2010-01-19) FESCo meeting

Here's the summary/minutes from todays meeting: Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2010-01-19/fesco.2010-01-19-20.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2010-01-19/fesco.2010-01-19-20.00.txt Log: http://meetbot.fedoraproj

Re: Building sources twice

On Monday 18 January 2010 10:10:34 pm Toshio Kuratomi wrote: > We have a few packages that need to build themselves from their sources > twice. For instance, vim builds three times (a minimal version for > /bin/vi, and two versions with more dependencies for /usr/bin/vim and > /usr/bin/gvim). Wor

Re: Building sources twice

On 01/19/2010 07:47 AM, Joe Orton wrote: > Most projects should allow use to use "VPATH" builds where > srcdir!=builddir, if not it is generally pretty simple to fix up the > Makefiles to support this. Generally you'll do: > > mkdir build-one&& cd build-one > ../configure --some-options > m

Re: Globally-visible executables with parallel python 2 and python 3 stacks

On Fri, 2010-01-15 at 16:53 -0500, Toshio Kuratomi wrote: > On Fri, Jan 15, 2010 at 11:45:05AM -0500, David Malcolm wrote: > > On Fri, 2010-01-15 at 10:55 -0500, Toshio Kuratomi wrote: > > > This reasoning (needed for testing) doesn't appeal to me at all. The > > > general case should be that we s

Re: berlios.de compromised since 2005

On Tue, 19 Jan 2010, Dominic Hopf wrote: > Am Mittwoch, den 13.01.2010, 12:23 -0500 schrieb Seth Vidal: >> dmaphy:graphem:http://graphem.berlios.de/ > > I contacted upstream concerning this Package as soon as I read your mail > last week. Upstream made the security audit at the weekend and we ca

Re: Building sources twice

On Tue, Jan 19, 2010 at 02:47:54PM +, Joe Orton wrote: > On Mon, Jan 18, 2010 at 11:10:34PM -0500, Toshio Kuratomi wrote: > > We have a few packages that need to build themselves from their sources > > twice. For instance, vim builds three times (a minimal version for /bin/vi, > > and two vers

Re: berlios.de compromised since 2005

Am Mittwoch, den 13.01.2010, 12:23 -0500 schrieb Seth Vidal: > dmaphy:graphem:http://graphem.berlios.de/ I contacted upstream concerning this Package as soon as I read your mail last week. Upstream made the security audit at the weekend and we can verify now that everything is okay with graphem, e

Re: rb_libtorrent has broken deps in Rawhide

Thank you for bumping and rebuilding it. http://koji.fedoraproject.org/koji/buildinfo?buildID=151914 On Tue, 2010-01-19 at 18:55 +0200, Ville Skyttä wrote: > On Tuesday 19 January 2010, Leigh Scott wrote: > > At the moment I am unable to build qbittorrent and torium (springlobby > > as well) at

Re: rb_libtorrent has broken deps in Rawhide

On Tuesday 19 January 2010, Leigh Scott wrote: > At the moment I am unable to build qbittorrent and torium (springlobby > as well) at Koji due to broken deps. > I have emailed Peter and requested commit rights for the devel branch > but received no response. Maybe he's still offline? http://lists.

KDE-SIG meeting report (03/2010)

This is a report of the weekly KDE-SIG-Meeting with a summary of the topics that were discussed. If you want to add a comment please reply to this email or add it to the related meeting page. -- = Weekly KDE Summary

Re: ABRT frustrating for users and developers

On 01/17/2010 07:41 AM, Michael Schwendt wrote: > The request to give the RAM some testing is not impolite. I absolutely agree---it is usually a simple test that people can run with minimal guidance, and it can possibly detect problems that would otherwise be very hard to diagnose (I personally ha

Re: Orphaning Candidate packages for removal due to FTBFS, implications

On Tue, 19 Jan 2010, Thomas Moschny wrote: > 2010/1/18 Seth Vidal : >> 1. extraordinarily stable >> [...] >> in ANY of those cases I'd want to start thinking about nuking the pkg from >> fedora. > > Are you serious? > As a heart attack. -sv -- devel mailing list devel@lists.fedoraproject.org

Re: Orphaning Candidate packages for removal due to FTBFS, implications

2010/1/18 Seth Vidal : > 1. extraordinarily stable > [...] > in ANY of those cases I'd want to start thinking about nuking the pkg from > fedora. Are you serious? - Thomas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Re: libcdio update

- "Adrian Reber" wrote: > On Tue, Jan 19, 2010 at 11:31:50AM +0100, Michael Schwendt wrote: > > On Tue, 19 Jan 2010 09:43:49 +0100, Adrian wrote: > > > > > I would like to update libcdio to the latest version (0.82). This > > > requires a rebuild of its dependencies: > > > > > > audaci

Re: Orphaning Candidate packages for removal due to FTBFS, implications

On Tue, 19 Jan 2010, Toshio Kuratomi wrote: > After some talk on IRC yesterday, skvidal is the person doing work on this > at them moment. His plan is to implement tests that try to tell if > individual packages are maintained and get people to orphan those that are > not. Here's his general pl

Re: Orphaning Candidate packages for removal due to FTBFS, implications

On Mon, Jan 18, 2010 at 10:27:04PM -0800, Adam Williamson wrote: > On Mon, 2010-01-18 at 11:55 -0800, Jesse Keating wrote: > > On Mon, 2010-01-18 at 20:44 +0100, Till Maas wrote: > > > > > > Imho the only real problem from your list is, if a package is > > > unmaintained, because if it is maintain

Re: Building sources twice

On Mon, Jan 18, 2010 at 11:10:34PM -0500, Toshio Kuratomi wrote: > We have a few packages that need to build themselves from their sources > twice. For instance, vim builds three times (a minimal version for /bin/vi, > and two versions with more dependencies for /usr/bin/vim and > /usr/bin/gvim).

Re: libcdio update

On Tue, Jan 19, 2010 at 11:31:50AM +0100, Michael Schwendt wrote: > On Tue, 19 Jan 2010 09:43:49 +0100, Adrian wrote: > > > I would like to update libcdio to the latest version (0.82). This > > requires a rebuild of its dependencies: > > > > audacious-plugins > > gvfs > > kover > > libcddb > > ox

Fedora packages for upcoming wxWidgets 3.0 available

Hello, wxWidgets developers are hard working on the upcoming major version 3.0. To make life of Fedora users and maintainers easier I started building recent snapshots and pre-releases as Fedora-compatible RPM packages. The libraries are installable in parallel with the regular 2.8.x, devel sub-pa

Re: Orphaning Candidate packages for removal due to FTBFS, implications

On Mon, 18 Jan 2010, Adam Williamson wrote: > On Mon, 2010-01-18 at 12:25 -0500, Seth Vidal wrote: > >> If we do that check before the alpha release that should let us track >> down >> awol maintainers and unmaintained pkgs pretty easily, I think. >> >> thoughts? > > There's trivial packages whi

Re: Orphaning some packages

Henrique Junior wrote: > Hello folks, > Due to an increasing lack of time I'm leaving my packages orphaned. > Even if I want, I will not be able to devote the attention they deserve. > I would like to thank all the kind help I received over time in the > task of maintaining these packages. > bkch

Re: Orphaning some packages

2010/1/19 Henrique Junior : > Hello folks, > Due to an increasing lack of time I'm leaving my packages orphaned. Even if > I want, I will not be able to devote the attention they deserve. > I would like to thank all the kind help I received over time in the task of > maintaining these packages. > b

Orphaning some packages

Hello folks, Due to an increasing lack of time I'm leaving my packages orphaned. Even if I want, I will not be able to devote the attention they deserve. I would like to thank all the kind help I received over time in the task of maintaining these packages. bkchem and python-oasa, preferably, shoul

Re: question about state of F11 kernel

On Tue, Jan 19, 2010 at 01:05:52PM +0100, Michał Piotrowski wrote: >Hi, > >What is the state of F11 kernel? AFAIK 2.6.30 is not supported by >upstream for a month. Upgrade to 2.6.31 doesn't solve this problem, >because 2.6.31.12 is probably the latest from 31 series. I have seen >failed 2.6.32 buil

Re: rawhide report: 20100115 changes

On Fri, Jan 15, 2010 at 2:59 PM, Rawhide Report wrote: > Compose started at Fri Jan 15 08:15:05 UTC 2010 > > firefox-3.6.1-0.10.rc1.fc13 > --- > * Wed Jan 13 2010 Martin Stransky - 3.6.1-0.10.rc1 > - Update to 3.6.1 RC1 > > Summary: > Added Packages: 5 > Removed Packages:

Re: Sources file audit - 2010-01-06

2010/1/10 Kevin Fenzi : > thm:BADSOURCE:httperf-0.9.0.tar.gz:httperf Project URLs changed. Fixed in CVS, not rebuilt. (But why was this BADSOURCE? Checked, and both tar files at old url ftp://ftp.hpl.hp.com/pub/httperf/httperf-0.9.0.tar.gz and new url http://httperf.googlecode.com/files/httperf-0

rb_libtorrent has broken deps in Rawhide

At the moment I am unable to build qbittorrent and torium (springlobby as well) at Koji due to broken deps. I have emailed Peter and requested commit rights for the devel branch but received no response. Would it be possible for a proven packager to rebuild rb_libtorrent against the latest boost ve

question about state of F11 kernel

Hi, What is the state of F11 kernel? AFAIK 2.6.30 is not supported by upstream for a month. Upgrade to 2.6.31 doesn't solve this problem, because 2.6.31.12 is probably the latest from 31 series. I have seen failed 2.6.32 build for F11 in koji http://koji.fedoraproject.org/koji/buildinfo?buildID=15

Re: ABRT frustrating for users and developers

On 01/19/2010 11:27 AM, Michael Schwendt wrote: On Mon, 18 Jan 2010 21:49:05 -0800, Adam wrote: On Sat, 2010-01-16 at 16:01 +0100, Christoph Wickert wrote: * abrt is frustrating for users: Today I received my first "No need for a reply...I will stop submitting tickets." Can s

Re: libcdio update

On Tue, 19 Jan 2010 09:43:49 +0100, Adrian wrote: > I would like to update libcdio to the latest version (0.82). This > requires a rebuild of its dependencies: > > audacious-plugins > gvfs > kover > libcddb > oxine > pycdio > qmmp > xfce4-cddrive-plugin > xmms2 > > If the maintainers of the abov

Re: ABRT frustrating for users and developers

On Mon, 18 Jan 2010 21:49:05 -0800, Adam wrote: > On Sat, 2010-01-16 at 16:01 +0100, Christoph Wickert wrote: > > > * abrt is frustrating for users: Today I received my first "No > > need for a reply...I will stop submitting tickets." > > > > Can somebody confirm my observations? >

Re: ABRT useful for this user

On 01/18/2010 11:02 PM, Paul W. Frields wrote: On Mon, Jan 18, 2010 at 01:59:27PM -0700, Stephen John Smoogen wrote: I just wanted to say thanks to the guys who integrated ABRT into F12. It has rough edges and I know it needs improvement, but I have filed more 'bugs' than in many past releases w

libcdio update

I would like to update libcdio to the latest version (0.82). This requires a rebuild of its dependencies: audacious-plugins gvfs kover libcddb oxine pycdio qmmp xfce4-cddrive-plugin xmms2 If the maintainers of the above packages do not object I would do all the necessary rebuilds.

Re: libdrm vs mesa updates - update group for bodhi?

Hi, On Tue, Jan 19, 2010 at 05:03, Dave Airlie wrote: > So I say libdrm was going to be karma'ed into updates, and > I thought I'd disabled that but it all got confused a few days ago. There was a bug with auto-karma that got enabled no matter what each time you created / edited an update (see b