Re: [Guidelines Change] Changes to the Packaging Guidelines

On Mar 8, 2014 11:57 AM, "Kevin Kofler" wrote: > > Tom Callaway wrote: > > > Changes to python-setuptools in F20 cause easy_install to install egg > > files instead of egg directories by default. This sometimes causes > > problems for rpms of multi-version python modules as the egg filenames > > a

Re: [Guidelines Change] Changes to the Packaging Guidelines

On Mar 8, 2014 11:57 AM, "Kevin Kofler" wrote: > > Tom Callaway wrote: > > The prohibition against packages installing files into /bin, /sbin, > > /lib, and /lib4 has been removed and a section explaining how Fedora's > > UsrMove? feature interacts with the rpm %files section has been added. > >

Re: qt-creator arm build timing out

On Sun, 09 Mar 2014 00:31:20 +0100 Kevin Kofler wrote: > I wrote: > > Sandro Mani wrote: > >> Argh, it timed out again [1]. Any other suggestions? > > > > ExcludeArch: %{arm} > > PS: To be clear, according to the policies, you should: > 1. File a bug against your own package: > Subject: ARM bui

Re: qt-creator arm build timing out

I wrote: > Sandro Mani wrote: >> Argh, it timed out again [1]. Any other suggestions? > > ExcludeArch: %{arm} PS: To be clear, according to the policies, you should: 1. File a bug against your own package: Subject: ARM builders time out when building %{name} Description: The ARM builders are so f

Re: qt-creator arm build timing out

Sandro Mani wrote: > Argh, it timed out again [1]. Any other suggestions? ExcludeArch: %{arm} Kevin Kofler (who has once again had to deal with glacially slow ARM builds, qt and qtwebkit in particular, and is really angry that ARM has been made a primary architecture despite the speed i

Re: qt-creator arm build timing out

On 03/08/2014 11:15 PM, Sandro Mani wrote: > On 08.03.2014 23:10, Kalev Lember wrote: >> On 03/08/2014 10:50 PM, Sandro Mani wrote: >>> Argh, it timed out again [1]. Any other suggestions? >> >> Try reducing the debuginfo level for arm. C++ code sometimes leads to >> massive debuginfo which could b

Re: Orphaning simple scan

On 03/08/2014 06:28 PM, Simone Caronni wrote: > On 8 March 2014 18:24, Rahul Sundaram > wrote: > > I don't have direct access to a personal scanner anymore and don't > have the time to handle bug reports without a device to test. I > have orphaned simple s

Re: qt-creator arm build timing out

On 08.03.2014 23:10, Kalev Lember wrote: On 03/08/2014 10:50 PM, Sandro Mani wrote: On 07.03.2014 14:09, Sandro Mani wrote: On 07.03.2014 14:05, Dan Horák wrote: On Fri, 07 Mar 2014 13:53:24 +0100 Sandro Mani wrote: Hi, I'm trying to build qt-creator [1], but the builds fail due to the ar

Re: qt-creator arm build timing out

On 03/08/2014 10:50 PM, Sandro Mani wrote: > On 07.03.2014 14:09, Sandro Mani wrote: >> On 07.03.2014 14:05, Dan Horák wrote: >>> On Fri, 07 Mar 2014 13:53:24 +0100 >>> Sandro Mani wrote: >>> Hi, I'm trying to build qt-creator [1], but the builds fail due to the arm build timin

Re: [Guidelines Change] Changes to the Packaging Guidelines

On 03/08/2014 01:56 PM, Kevin Kofler wrote: > Hmmm, I know I'm late to the discussion (and I hadn't thought of it when the > discussion first came up) couldn't we use something like this > (foo-dummymain.spec): > > Name: foo-dummymain > ExclusiveArch: %{ix86} > … > # the actual noarch package buil

Re: qt-creator arm build timing out

On 07.03.2014 14:09, Sandro Mani wrote: On 07.03.2014 14:05, Dan Horák wrote: On Fri, 07 Mar 2014 13:53:24 +0100 Sandro Mani wrote: Hi, I'm trying to build qt-creator [1], but the builds fail due to the arm build timing out. Is there anyway I can increase the timeout? can you resubmit wit

Re: Read this if your package includes a status notifier / system tray icon

Hi On Sat, Mar 8, 2014 at 4:24 PM, Kevin Kofler wrote: > * Wayland rendering the legacy XEmbed-based spec (that has been used as the > interoperability "lingua franca" so far, despite having been deprecated > by > both sides of the equation) entirely obsolete > instead, and thus restarting

Re: Read this if your package includes a status notifier / system tray icon

drago01 wrote: > Its not about "complaining" can you stop your "they vs. us" attitude? > The spec have been put up for review > and issues where found and the ones that wrote the spec refused to > address them in a meaningful way (or not at all). That's just not true. A revision was uploaded. The

Rebuilding 9 Qt 4 packages in Rawhide for -debuginfo issue

Hi, as per: https://bugzilla.redhat.com/show_bug.cgi?id=1074041 due to a bug in qt-devel, several packages using qmake-qt4 to build accidentally had their debugging information stripped before the -debuginfo extraction, resulting in empty -debuginfo packages. I went through all the Qt-4-using p

Re: Read this if your package includes a status notifier / system tray icon

On Sat, Mar 8, 2014 at 9:23 PM, Kevin Kofler wrote: > drago01 wrote: >> You make it sound like Dan's review only talks about names. But that's >> not the case. > > The main author of the spec made a revision in which he integrated some of > the suggestions: > http://lists.freedesktop.org/archives/

Re: Read this if your package includes a status notifier / system tray icon

drago01 wrote: > You make it sound like Dan's review only talks about names. But that's > not the case. The main author of the spec made a revision in which he integrated some of the suggestions: http://lists.freedesktop.org/archives/xdg/2010-January/011246.html (even one of the name changes, whi

Re: [Guidelines Change] Changes to the Packaging Guidelines

Tom Callaway wrote: > The Naming Guidelines for python modules has been updated to remove the > exception for packages which have a "py" prefix in the upstream name. > This change comes at a time when python2 and python3 modules are > commonly built from the same package and all python3 modules are

Re: Read this if your package includes a status notifier / system tray icon

On 8 March 2014 17:55, Kevin Kofler wrote: > To properly integrate with the other desktops, GNOME has no other choice but > to implement that spec I'm not sure that's a terribly convincing argument. Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mai

Re: Read this if your package includes a status notifier / system tray icon

On Sat, Mar 8, 2014 at 7:45 PM, Kevin Kofler wrote: > Rahul Sundaram wrote: >> Yes and I am convinced that not enough effort was taken to address the >> concerns expressed. This is probably lost opportunity already but one >> could strive to do better on future specs. > > So you think the KDE dev

Re: Read this if your package includes a status notifier / system tray icon

Rahul Sundaram wrote: > Yes and I am convinced that not enough effort was taken to address the > concerns expressed. This is probably lost opportunity already but one > could strive to do better on future specs. So you think the KDE developers should have renamed those D-Bus methods and signals,

Re: audio/video software

LM wrote: > Is anyone currently working on software that fits this category? For > example, I've been looking at the source code for > xine-lib-1.1.21-pruned.tar.xz. It hasn't been updated in a while and > a newer version of xine in source control and Sourceforge has support > for webm and some o

Re: Read this if your package includes a status notifier / system tray icon

Hi On Sat, Mar 8, 2014 at 12:55 PM, Kevin Kofler wrote: > Rahul Sundaram wrote: > > If a single desktop environment wants to just implement something, they > > can go ahead and do so but that doesn't make it a real specification. > For > > other desktop environments to adopt it, it needs to be

Re: pdftk retired?

Orcan Ogetbil wrote: > The only things I read in the thread are "GCJ is abandoned" and "we > really want to get rid of GCJ". Am I supposed to come to the > conclusion that the GCJ package is dropped from Fedora? If so, where > is this decision made? Why was it made without consulting GCJ users? >

Re: Read this if your package includes a status notifier / system tray icon

Rahul Sundaram wrote: > There is no need to assume that clarifying something requires changing > existing code and changing existing code doesn't necessarily require > breaking compatibility Have you seen the changes they requested? http://lists.freedesktop.org/archives/xdg/2010-January/011228.htm

[Guidelines Change] Changes to the Packaging Guidelines

We've been very bad at announcing changes to the Packaging Guidelines. So very bad. Bear with us as we announce all the changes we should have been announcing in the past, but failed to do. Again, so bad. --- The Mersenne Twister implementation (mt19937ar) has been granted a general bundling exce

Re: Read this if your package includes a status notifier / system tray icon

Rahul Sundaram wrote: > If a single desktop environment wants to just implement something, they > can go ahead and do so but that doesn't make it a real specification. For > other desktop environments to adopt it, it needs to be a collaborative and > shared effort. Part of that is addressing conc

Re: Read this if your package includes a status notifier / system tray icon

Dan Williams wrote: > "obvious to everyone" - assuming that everyone understands something the > same way is about the worst way to write a specification. You need to > explicitly state what that understanding is, otherwise it's not a > specification, it's a vague idea and everyone will have a dif

Re: Orphaning simple scan

On 8 March 2014 18:24, Rahul Sundaram wrote: > I don't have direct access to a personal scanner anymore and don't have > the time to handle bug reports without a device to test. I have orphaned > simple scan now. Please feel free to take it. > Thanks for maintaining this so far, I've taken it

Orphaning simple scan

Hi I don't have direct access to a personal scanner anymore and don't have the time to handle bug reports without a device to test. I have orphaned simple scan now. Please feel free to take it. Thanks! Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/

audio/video software

I apologize in advance if this is the wrong list to post to. I tried posting/asking through the fedora-join mailing list and got no response at all. I'm doing some research for an article on patent unencumbered Open Source software at: https://schoolforge.net/wiki/index.php?title=Patents_and_Open

Re: F21 System Wide Change: u-boot syslinux by default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 8 Mar 2014 10:22:57 + Peter Robinson wrote: > >> Add syslinux support to u-boot enabling both pxelinux and extlinux > >> support. simplifying booting arm machines, making anaconda > >> installs easy and overall providing for a better user

Re: F21 System Wide Change: u-boot syslinux by default

>> Add syslinux support to u-boot enabling both pxelinux and extlinux support. >> simplifying booting arm machines, making anaconda installs easy and overall >> providing for a better user experience. Default u-boot to using syslinux >> config >> files for booting. pxelinux for network and extlinu

Re: F21 System Wide Change: u-boot syslinux by default

>> Add syslinux support to u-boot enabling both pxelinux and extlinux support. >> simplifying booting arm machines, making anaconda installs easy and overall >> providing for a better user experience. Default u-boot to using syslinux >> config >> files for booting. pxelinux for network and extlinu

Re: F21 System Wide Change: u-boot syslinux by default

On Fri, Mar 07, 2014 at 03:58:44PM +0100, Jaroslav Reznik wrote: > Add syslinux support to u-boot enabling both pxelinux and extlinux support. > simplifying booting arm machines, making anaconda installs easy and overall > providing for a better user experience. Default u-boot to using syslinux