Re: Web page for distro life cycle stage

[Shakthi Kannan]

Hi,

--- On Wed, Nov 4, 2009 at 4:41 AM, Mat Booth  wrote:
| Can't this be inferred from https://admin.fedoraproject.org/updates ?
\--

I was looking at something with less text, and having a pictorial
representation. Sometimes, a picture is a thousand words!

SK

-- 
Shakthi Kannan
http://www.shakthimaan.com

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: A question about allow_unconfined_mmap_low in f11 amd selinux

[Adam Jackson]

On Tue, 2009-11-03 at 21:31 +, Mike Cloaked wrote:
> For people running wine or Crossover and using MS Office 2003 and related 
> codes
> it is necessary to do:
> # setsebool -P allow_unconfined_mmap_low 1
> To prevent AVC denials.
> 
> However there is recent publicity at 
> http://www.theregister.co.uk/2009/11/03/linux_kernel_vulnerability/
> which highlights that there is still a vulnerability in the kernel if this is
> set.
> 
> For people running f11 with this boolean set how can one run wine and still
> remain secure? i.e. what should an admin do to protect the system?

You can't.

If I'm being slightly less flip: run wine in a kvm instance with selinux
disabled, forward X to the host.

- 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

A question about allow_unconfined_mmap_low in f11 amd selinux

[Mike Cloaked]

For people running wine or Crossover and using MS Office 2003 and related codes
it is necessary to do:
# setsebool -P allow_unconfined_mmap_low 1
To prevent AVC denials.

However there is recent publicity at 
http://www.theregister.co.uk/2009/11/03/linux_kernel_vulnerability/
which highlights that there is still a vulnerability in the kernel if this is
set.

For people running f11 with this boolean set how can one run wine and still
remain secure? i.e. what should an admin do to protect the system?

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: help debugging segfault with alienarena 7.32

[Tom "spot" Callaway]

On 11/03/2009 02:16 PM, Jerry James wrote:

> This seems to happen only when portaudio is installed.  Uninstall
> portaudio and alienarena starts up.  I'm not sure exactly what is
> going on here, but it seems that alienarena is both trying to dlopen
> libopenal, and is linked against it.  Check it:
> 
> ldd /usr/libexec/alienarena | grep -F openal
> 
> My guess (and it is just a guess) is that this is triggering multiple
> initializations of portaudio.  Try this patch:

This gets me past the initial segfault, thanks!

Of course, now the game won't actually start in single-player mode:

 CRX Initialized 

Received signal 11, exiting...
Received signal 11, exiting...
Received signal 11, exiting...
Received signal 11, exiting...
XIO:  fatal IO error 0 (Success) on X server "�o�"
  after 2628 requests (2619 known processed) with 0 events remaining.
AL lib: ALc.c:1641: exit(): closing 1 Device
AL lib: ALc.c:1570: alcCloseDevice(): destroying 1 Context
AL lib: ALc.c:1259: alcDestroyContext(): deleting 129 Source(s)
--- Loading game.so ---
AL lib: ALc.c:1579: alcCloseDevice(): deleting 256 Buffer(s)

Running it again, I get:

 CRX Initialized 

Received signal 11, exiting...
Received signal 11, exiting...
XIO:  fatal IO error 0 (Success) on X server "P�%"
  after 657 requests (654 known processed) with 0 events remaining.
AL lib: ALc.c:1641: exit(): closing 1 Device
AL lib: ALc.c:1570: alcCloseDevice(): destroying 1 Context
Received signal 11, exiting...
Received signal 11, exiting...
*** glibc detected *** ./crx: free(): invalid pointer:
0x07263c00 ***
Received signal 11, exiting...
*** glibc detected *** ./crx: free(): invalid pointer:
0x07263c00 ***
Segmentation fault

Valgrind isn't much more help:

==22231== Process terminating with default action of signal 11 (SIGSEGV)
==22231==  Bad permissions for mapped region at address 0xFA9CB20
==22231==at 0xA1663E0: pthread_cond_wait@@GLIBC_2.3.2
(pthread_cond_wait.S:170)
==22231==by 0xF88B3BA: ??? (in /usr/lib64/libportaudio.so.2.0.0)

The latest patched build is here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1786476

It does work in multi-player mode, just not single player.

Any more ideas? :)

~spot

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Kevin Kofler]

Joerg Schilling wrote:
> You seem to miss that the license mkisofs is using is called "GPL" and not
> "GPL FAQ", so the quoting you mention do not apply.

The FAQ is the legal interpretation of the GPL given by the FSF, who are the 
folks who wrote the license, so why would you trust them less than Sun's 
lawyers? And Eben Moglen, whom you misquoted as agreeing with your bizarre 
position, was actually involved in writing both the GPL itself and the FAQ.

> The GPL requires the entire work to be under GPL and the "entire work
> mkisofs" _is_ of course under GPL.

The entire work includes any code which is linked into the same executable, 
statically or dynamically. A program is not complete without its required 
libraries, it doesn't work at all without them.

Kevin Kofler

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Mesa 7.6.0 bugs

[Bojan Smojver]

New mesa (7.6.0) is causing trouble for people using F-11/12 code (see
bugs #524338 and #509528 for instance).

Are there fixes available for these problems? Last time 7.6.0 packages
were built was Sept 21, which is a month and a half ago and it seems
that concerns from the above bugs are not being addressed.

Is it too late to revert to 7.5.x, which used to work fine?

-- 
Bojan

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Seth Vidal]

On Tue, 3 Nov 2009, Kevin Kofler wrote:


Joerg Schilling wrote:

Libburn is based on a wrong asumption: libburn only works partly on Linux
in non-root mode


Actually, burning as non-root works just fine on GNU/Linux.


and the vast majority of other OS needs root permissions to burn.


Those OSes are broken and need to be fixed.


Installing a GUI suid root is an absolute no-go as GUIs are so compley
that it is hard to audit the code for security problems.


We know this very well. All the Fedora system-config-* tools are being more
or less rewritten to use PolicyKit to only do the parts as root which need
to run as root instead of running the whole GUI config tool as root. The
same is happening with KDE's System Settings and the KAuth framework (which
is based on PolicyKit on GNU/Linux).

But the point is that CD/DVD/BluRay burning does not and should not require
root privileges at all!



Kevin,
 please. Stop responding.

-sv

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: help debugging segfault with alienarena 7.32

[Jerry James]

On Tue, Nov 3, 2009 at 9:45 AM, Tom "spot" Callaway  wrote:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffea1e0710 (LWP 18791)]
> pthread_cond_wait@@GLIBC_2.3.2 () at
> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:170
> 170             LOCK
> Current language:  auto
> The current source language is "auto; currently asm".
> (gdb) info threads
> * 6 Thread 0x7fffea1e0710 (LWP 18791)  pthread_cond_wait@@GLIBC_2.3.2 ()
> at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:170
>  1 Thread 0x77fb77e0 (LWP 18784)  _dl_map_object
> (loader=0x77fcc4d0, name=0x7660574a "libportaudio.so.2",
>    preloaded=, type=,
> trace_mode=, mode=-1879048190, nsid=0) at
> dl-load.c:1981

This seems to happen only when portaudio is installed.  Uninstall
portaudio and alienarena starts up.  I'm not sure exactly what is
going on here, but it seems that alienarena is both trying to dlopen
libopenal, and is linked against it.  Check it:

ldd /usr/libexec/alienarena | grep -F openal

My guess (and it is just a guess) is that this is triggering multiple
initializations of portaudio.  Try this patch:

diff -dur alienarena-7.32.ORIG/source/Makefile alienarena-7.32/source/Makefile
--- alienarena-7.32.ORIG/source/Makefile2009-11-02 19:01:01.0 
-0700
+++ alienarena-7.32/source/Makefile 2009-11-03 12:05:38.283115734 -0700
@@ -266,7 +266,7 @@


 $(BUILDDIR)/crx : $(CODERED_OBJS) $(SOUND_OPENAL_OBJS) $(REF_GL_OBJS)
$(REF_GL_GLX_OBJS)
-   $(CC) $(CFLAGS) -o $@ $(CODERED_OBJS) $(LDFLAGS) $(REF_GL_OBJS)
$(REF_GL_GLX_OBJS) $(GLXLDFLAGS) $(OPENALLDFLAGS) $(VORBISLDFLAGS)
$(CURLLDFLAGS) $(JPEGLDFLAGS)
+   $(CC) $(CFLAGS) -o $@ $(CODERED_OBJS) $(LDFLAGS) $(REF_GL_OBJS)
$(REF_GL_GLX_OBJS) $(GLXLDFLAGS) $(VORBISLDFLAGS) $(CURLLDFLAGS)
$(JPEGLDFLAGS)

 $(BUILDDIR)/client/cl_ents.o :$(CLIENT_DIR)/cl_ents.c
$(DO_CC)

-- 
Jerry James
http://www.jamezone.org/

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: help debugging segfault with alienarena 7.32

[John Reiser]

FWIW, it looks like the backtrace is within the C++ start-up code that
runs all non-empty constructors for global C++ variables, which gets
called before "main" starts for a C++ program.

Does
   (gdb) break call_init
before
   (gdb) run
give you a working breakpoint?



It does, but it doesn't seem to be terribly useful in debugging, as it
keeps hitting that breakpoint over and over and over.


(gdb) set stop-on-solib-events 1
(gdb) run  <>
Stopped due to shared library event
(gdb) info shared
FromTo  Syms Read   Shared Object Library
0x00dc2830  0x00ddb27f  Yes /lib/ld-linux.so.2
0x00ae4410  0x00ae45e8  Yes a.out
(gdb) c
Continuing.
Stopped due to shared library event
(gdb) info shared
FromTo  Syms Read   Shared Object Library
0x00dc2830  0x00ddb27f  Yes /lib/ld-linux.so.2
0x00ae4410  0x00ae45e8  Yes a.out
0x00e5a840  0x00f68c78  Yes /lib/libc.so.6

  etc.

You might run afoul of this years-old bug:
  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179072

Post the build, or a pointer to it, plus the needed environment?

--

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Web page for distro life cycle stage

[Ikem Krueger]

> Web page for distro life cycle stage

> If a release is in freeze, it can be in marked in an yellow circle, and when 
> we can push packages to a release, it can be in a green circle, similar to 
> traffic signal lights

I like this idea. :)

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Web page for distro life cycle stage

[Mat Booth]

2009/11/3 Ikem Krueger :
>> Web page for distro life cycle stage
>
>> If a release is in freeze, it can be in marked in an yellow circle, and when 
>> we can push packages to a release, it can be in a green circle, similar to 
>> traffic signal lights
>
> I like this idea. :)
>

Can't this be inferred from https://admin.fedoraproject.org/updates ?


-- 
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

texlive-2009 tlmgr

[Neal Becker]

tlmgr
Can't locate TeXLive/TLPOBJ.pm in @INC (@INC contains: 
/usr/share/texlive/tlpkg /usr/local/lib64/perl5/site_perl/5.10.0/x86_64-
linux-thread-multi /usr/local/lib/perl5/site_perl/5.10.0 
/usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi 
/usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl 
/usr/lib64/perl5/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/5.10.0 
/usr/lib/perl5/site_perl .) at /usr/bin/tlmgr line 36.
BEGIN failed--compilation aborted at /usr/bin/tlmgr line 36.

sure enough, /usr/share/texlive/tlpkg dir exists, but is empty.

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Seth Vidal]

On Tue, 3 Nov 2009, Kevin Kofler wrote:


Joerg Schilling wrote:

You seem to miss that the license mkisofs is using is called "GPL" and not
"GPL FAQ", so the quoting you mention do not apply.


The FAQ is the legal interpretation of the GPL given by the FSF, who are the
folks who wrote the license, so why would you trust them less than Sun's
lawyers? And Eben Moglen, whom you misquoted as agreeing with your bizarre
position, was actually involved in writing both the GPL itself and the FAQ.


The GPL requires the entire work to be under GPL and the "entire work
mkisofs" _is_ of course under GPL.


The entire work includes any code which is linked into the same executable,
statically or dynamically. A program is not complete without its required
libraries, it doesn't work at all without them.


This thread is closed.

Do not comment on it anymore.

Sincerely,

Your friendly neighborhood hall monitor.
-sv

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Seth Vidal]

On Tue, 3 Nov 2009, King InuYasha wrote:


GPLv2: End of Section 3, middle of the paragraph right after clause 3c.GPLv3: 
Explicit separate definition in Section 1.

GPLv2 Quote:

"The source code for a work means the preferred form of the work for making 
modifications to it. For an executable work,
complete source code means all the source code for all modules it contains, 
plus any associated interface definition
files, plus the scripts used to control compilation and installation of the 
executable. However, as a special exception,
the source code distributed need not include anything that is normally 
distributed (in either source or binary form) with
the major components (compiler, kernel, and so on) of the operating system on 
which the executable runs, unless that
component itself accompanies the executable."

GPLv3 Quote:

"The “System Libraries” of an executable work include anything, other than the 
work as a whole, that (a) is included in
the normal form of packaging a Major Component, but which is not part of that 
Major Component, and (b) serves only to
enable use of the work with that Major Component, or to implement a Standard 
Interface for which an implementation is
available to the public in source code form. A “Major Component”, in this 
context, means a major essential component
(kernel, window system, and so on) of the specific operating system (if any) on 
which the executable work runs, or a
compiler used to produce the work, or an object code interpreter used to run 
it."

I hope this satisfies you.


This thread is closed.


please do not post any additional comments to it.

-sv
-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Claudio Tomasoni is now MIA

[Jon Ciesla]

Kevin Fenzi wrote:

On Sun, 01 Nov 2009 02:45:10 +0100
Christoph Wickert  wrote:

  

This is a follow-up to my mail from October 9th [1]
As per unresponsive package maintainer policy, Claudio is now
officially considered missing in action and his packages [2] will be
orphaned.



I can ack this per the procedure as a FESCo member. 

I am going to orphan those packages now. 


kevin
  

Thanks.  Tennix (and it's bug) taken.

-J

--
in your fear, seek only peace
in your fear, seek only love

-d. bowie

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Claudio Tomasoni is now MIA

[Kevin Fenzi]

On Sun, 01 Nov 2009 02:45:10 +0100
Christoph Wickert  wrote:

> This is a follow-up to my mail from October 9th [1]
> As per unresponsive package maintainer policy, Claudio is now
> officially considered missing in action and his packages [2] will be
> orphaned.

I can ack this per the procedure as a FESCo member. 

I am going to orphan those packages now. 

kevin


signature.asc
Description: PGP signature
-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: help debugging segfault with alienarena 7.32

[Tom "spot" Callaway]

On 11/03/2009 12:16 PM, David Malcolm wrote:
> On Tue, 2009-11-03 at 11:45 -0500, Tom "spot" Callaway wrote:
>> I need to rebuild alienarena for all targets due to a security issue, so
>> I decided to update to 7.32, but unfortunately, the 7.32 build segfaults
>> immediately on Fedora 12 (x86_64), and gdb isn't much help (gdb output
>> is at the bottom).
> 
> FWIW, it looks like the backtrace is within the C++ start-up code that
> runs all non-empty constructors for global C++ variables, which gets
> called before "main" starts for a C++ program.
> 
> Does
>   (gdb) break call_init
> before
>   (gdb) run
> give you a working breakpoint?

It does, but it doesn't seem to be terribly useful in debugging, as it
keeps hitting that breakpoint over and over and over. I admit to being
reasonably clueless with gdb.

~spot

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Kevin Kofler]

Joerg Schilling wrote:
> Libburn is based on a wrong asumption: libburn only works partly on Linux
> in non-root mode

Actually, burning as non-root works just fine on GNU/Linux.

> and the vast majority of other OS needs root permissions to burn.

Those OSes are broken and need to be fixed.

> Installing a GUI suid root is an absolute no-go as GUIs are so compley
> that it is hard to audit the code for security problems.

We know this very well. All the Fedora system-config-* tools are being more 
or less rewritten to use PolicyKit to only do the parts as root which need 
to run as root instead of running the whole GUI config tool as root. The 
same is happening with KDE's System Settings and the KAuth framework (which 
is based on PolicyKit on GNU/Linux).

But the point is that CD/DVD/BluRay burning does not and should not require 
root privileges at all!

Kevin Kofler

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[King InuYasha]

GPLv2: End of Section 3, middle of the paragraph right after clause 3c.
GPLv3: Explicit separate definition in Section 1.

GPLv2 Quote:

"The source code for a work means the preferred form of the work for making
modifications to it. For an executable work, complete source code means all
the source code for all modules it contains, plus any associated interface
definition files, plus the scripts used to control compilation and
installation of the executable. However, as a special exception, the source
code distributed need not include anything that is normally distributed (in
either source or binary form) with the major components (compiler, kernel,
and so on) of the operating system on which the executable runs, unless that
component itself accompanies the executable."

GPLv3 Quote:

"The “System Libraries” of an executable work include anything, other than
the work as a whole, that (a) is included in the normal form of packaging a
Major Component, but which is not part of that Major Component, and (b)
serves only to enable use of the work with that Major Component, or to
implement a Standard Interface for which an implementation is available to
the public in source code form. A “Major Component”, in this context, means
a major essential component (kernel, window system, and so on) of the
specific operating system (if any) on which the executable work runs, or a
compiler used to produce the work, or an object code interpreter used to run
it."

I hope this satisfies you.


On Tue, Nov 3, 2009 at 9:19 AM, Joerg Schilling <
joerg.schill...@fokus.fraunhofer.de> wrote:

> King InuYasha  wrote:
>
> > While it is true that the GPL permits linking to CDDL libraries, that is
> > only in the case if the library is a "system library," which is a library
> > that is NECESSARY for working on a particular OS. This is usually how it
> is
>
> Please show me the exact place in the GPL text thatyou have in mind to
> prove your claim.
>
> Jörg
>
> --
>  
> EMail:jo...@schily.isdn.cs.tu-berlin.de(home)
>  Jörg Schilling D-13353 Berlin
>   j...@cs.tu-berlin.de(uni)
>   joerg.schill...@fokus.fraunhofer.de (work) Blog:
> http://schily.blogspot.com/
>  URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
>
> --
> 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: orphaning (eol) gtk-qt-engine

[Matthew Woehlke]

Kevin Kofler wrote:

Petrus de Calguarium wrote:

By the way, colours on old kde3 apps doesn't work,
either, despite enabling for non-kde4 applications in
system settings (kftpgrabber) - I can see it already:
file a bug report :-)


There's already an ages-old bug report, the upstream KDE developers don't 
care. :-(


...or maybe the upstream developers don't know how to fix it. Help welcomed.

(Actually, it's more accurate to say that I am not aware of anyone 
maintaining the 'export colors' functionality. Jeremy Whiting and I are 
- last I knew, anyway :-) - the nominal maintainers for color kcm stuff, 
and I certainly fix anything I can, but I know next to nothing about how 
the export colors stuff works. Ergo, I am not able to fix it.)


FTR, exporting colors to GTK seems flaky also, but I'm not sure it's a 
KDE problem. I've noticed that after I force the export code to run 
(basically, make any change and apply it - even toggle a checkbox twice, 
you just need to be able to press 'apply'), the first app will be right, 
but the next one gets default colors. At least for Mozilla apps (FF, TB) 
and IIRC gitk. OTOH, Inkscape seems okay.



I might try to fix this somehow.


If you are able to help, that would be /much/ appreciated. Please don't 
hesitate to work upstream, I would very much like to see these issues 
resolved.


--
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
--
HIPPOS feel unacknowledged. HIPPOS get angry.
> PRAISE HIPPOS
HIPPOS seem somewhat placated.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: libsndfile status?

[Orcan Ogetbil]

On Tue, Nov 3, 2009 at 4:48 AM, Michael Schwendt wrote:
> https://admin.fedoraproject.org/pkgdb/packages/bugs/libsndfile
>
> What's up with libsndfile in Fedora and EPEL?
> There are open tickets about CVEs filed in March.
> There are additional tickets without any reply.
>

Yeah, things go a little slow with libsndfile. Because of the old
version we have in < Fedora 12 we also are not able to update some of
our audio packages.
I requested for comaintainership to fix the bugs filed to Fedora.

Orcan

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: help debugging segfault with alienarena 7.32

[David Malcolm]

On Tue, 2009-11-03 at 11:45 -0500, Tom "spot" Callaway wrote:
> I need to rebuild alienarena for all targets due to a security issue, so
> I decided to update to 7.32, but unfortunately, the 7.32 build segfaults
> immediately on Fedora 12 (x86_64), and gdb isn't much help (gdb output
> is at the bottom).

FWIW, it looks like the backtrace is within the C++ start-up code that
runs all non-empty constructors for global C++ variables, which gets
called before "main" starts for a C++ program.

Does
  (gdb) break call_init
before
  (gdb) run
give you a working breakpoint?

[snip]

Hope this is helpful
Dave


-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Web page for distro life cycle stage

[Shakthi Kannan]

Hi,

Is there a web-page or is it possible to have one that shows the
Fedora distro release and its stage in the release cycle?

For example, if a release such as Fedora 9, is not supported, one can
have it shown with a red circle. If a release is in freeze, it can be
in marked in an yellow circle, and when we can push packages to a
release, it can be in a green circle, similar to traffic signal
lights?

While, we do receive e-mails on freeze updates, I thought it will be
simpler to just check a web-page rather than having to go through
mailing list archives?

Suggestions welcome.

SK

-- 
Shakthi Kannan
http://www.shakthimaan.com

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

help debugging segfault with alienarena 7.32

[Tom "spot" Callaway]

I need to rebuild alienarena for all targets due to a security issue, so
I decided to update to 7.32, but unfortunately, the 7.32 build segfaults
immediately on Fedora 12 (x86_64), and gdb isn't much help (gdb output
is at the bottom).

Now, it is worth noting that the alienarena client does dlopen the
openal-soft library by name:

   const char libopenal_name[] = "libopenal.so.1.9.563";
   void *dynlib;

   dynlib = dlopen( libopenal_name, RTLD_LAZY | RTLD_GLOBAL );

However, I can't seem to find a breakpoint that gdb will hit before the
app segfaults, and printfs never get triggered.

Any and all help is appreciated, as I'd like to get this fixed before F-12.

[s...@pterodactyl release]$ gdb ./crx
GNU gdb (GDB) Fedora (7.0-3.fc12)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from
/home/spot/cvs/alienarena/F-12/alienarena-7.32/source/release/crx...done.
(gdb) run
Starting program:
/home/spot/cvs/alienarena/F-12/alienarena-7.32/source/release/crx
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffea1e0710 (LWP 18787)]
[Thread 0x7fffea1e0710 (LWP 18787) exited]
[New Thread 0x7fffea1e0710 (LWP 18788)]
[Thread 0x7fffea1e0710 (LWP 18788) exited]
[New Thread 0x7fffea1e0710 (LWP 18789)]
[Thread 0x7fffea1e0710 (LWP 18789) exited]
[New Thread 0x7fffea1e0710 (LWP 18790)]
[Thread 0x7fffea1e0710 (LWP 18790) exited]
[New Thread 0x7fffea1e0710 (LWP 18791)]
Detaching after fork from child process 18792.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffea1e0710 (LWP 18791)]
pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:170
170 LOCK
Current language:  auto
The current source language is "auto; currently asm".
(gdb) info threads
* 6 Thread 0x7fffea1e0710 (LWP 18791)  pthread_cond_wait@@GLIBC_2.3.2 ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:170
  1 Thread 0x77fb77e0 (LWP 18784)  _dl_map_object
(loader=0x77fcc4d0, name=0x7660574a "libportaudio.so.2",
preloaded=, type=,
trace_mode=, mode=-1879048190, nsid=0) at
dl-load.c:1981
(gdb) bt
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:170
#1  0x7fffeff883bb in ?? ()
#2  0x7fffea1e0710 in ?? ()
#3  0x74f8696a in start_thread (arg=) at
pthread_create.c:297
#4  0x75aaa8bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x in ?? ()
(gdb) thread 1
[Switching to thread 1 (Thread 0x77fb77e0 (LWP 18784))]#0
_dl_map_object (loader=0x77fcc4d0, name=0x7660574a
"libportaudio.so.2",
preloaded=, type=,
trace_mode=, mode=-1879048190, nsid=0) at
dl-load.c:1981
1981  if (__builtin_expect (l->l_soname_added, 1)
Current language:  auto
The current source language is "auto; currently c".
(gdb) bt
#0  _dl_map_object (loader=0x77fcc4d0, name=0x7660574a
"libportaudio.so.2", preloaded=, type=,
trace_mode=, mode=-1879048190, nsid=0) at
dl-load.c:1981
#1  0x77df0299 in dl_open_worker (a=) at
dl-open.c:254
#2  0x77deb7c6 in _dl_catch_error (objname=, errstring=, mallocedp=,
operate=, args=) at
dl-error.c:178
#3  0x77defca7 in _dl_open (file=0x7660574a
"libportaudio.so.2", mode=-2147483646, caller_dlopen=0x765ffaf1,
nsid=-2, argc=1,
argv=, env=0x7fffe0c8) at dl-open.c:583
#4  0x77955f66 in dlopen_doit (a=) at
dlopen.c:67
#5  0x77deb7c6 in _dl_catch_error (objname=, errstring=, mallocedp=,
operate=, args=) at
dl-error.c:178
#6  0x7795629c in _dlerror_run (operate=0x77955f00
, args=0x7fffdeb0) at dlerror.c:164
#7  0x77955ee1 in __dlopen (file=,
mode=) at dlopen.c:88
#8  0x765ffaf1 in pa_load () at
/usr/src/debug/openal-soft/Alc/portaudio.c:66
#9  0x765ffee8 in alc_pa_probe (type=1) at
/usr/src/debug/openal-soft/Alc/portaudio.c:289
#10 0x765e8bfe in alc_init () at
/usr/src/debug/openal-soft/Alc/ALc.c:297
#11 0x76602556 in __do_global_ctors_aux () from
/usr/lib64/libopenal.so.1
#12 0x765d8aeb in _init () from /usr/lib64/libopenal.so.1
#13 0x7fffe0c8 in ?? ()
#14 0x77debb29 in call_init (l=0x77fcc4d0, argc=-159341768,
argv=0x7fffe0b8, env=0x7fffe0c8) at dl-init.c:70
#15 0x77debcaf in _dl_init (main_map=0x77ffe0e8, argc=1,
argv=0x7fffe0b8, env=0x7fffe0c8) at dl-init.c:134
#16 0x77dddb2a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#17 0x0001 in ?? ()
#18 0x7fffe3d4 in ?? ()
#19 0x in ?? ()
(g

KDE-SIG weekly report (45/2009)

[Jaroslav Reznik]

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 =

Week: 45/2009

Time: 2009-11-03 14:00 UTC

Meeting page: https://fedoraproject.org/wiki/SIGs/KDE/Meetings/2009-11-03

Meeting minutes: http://meetbot.fedoraproject.org/fedora-
meeting/2009-11-03/fedora-meeting.2009-11-03-14.08.txt

Meeting log: http://meetbot.fedoraproject.org/fedora-
meeting/2009-11-03/fedora-meeting.2009-11-03-14.08.log.html

--

= Participants =

BenBoeckel
JaroslavReznik
KevinKofler
RexDieter
StevenParrish
ThanNgo
ThomasJanssen
Ryan Rix

--

= Agenda =

*  topics to discuss:
o KDE-4.3.3 state
o Fedora 12 looming soon, remaining issues/blockers?
o constantine-kde-theme-extras, aka packaging Mosaico kdm/ksplash theme?
o VOIP meetings

= Summary =

o KDE-4.3.3 state
* 4.3.3 is imported into devel/ branch
* some remaining issues - kdebindings & kde-l10n doesn't build
** Kevin_Kofler suggest mathstuff hint how to fix kdebindings
** rdieter will fix kde-l10n issues

o Fedora 12 looming soon, remaining issues/blockers?
* a lot of KDE SIG members are using Fedora 12 already
* beta still had the "install to hd link on desktop lacking execute 
permission" problem
* "SELinux is preventing the /bin/loadkeys from using potentially mislabeled 
files (Documents)." bug [1] added to Fedora 12 blockers tracker

o constantine-kde-theme-extras, aka packaging Mosaico kdm/ksplash theme?
* we agreed we don't want it, if someone is willing to fix issues, we're not 
blocking it
* issues:
** KDM colors do not match latest wallpaper
** KSplash rectangles have bad looking shaddows
* jreznik will import old Constantine to SVN

o VOIP meetings
* not for regular meetings (at least for now)
* we try to set conference call from FUDCon

--

= Next Meeting =

http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2009-11-10

--

= Links =

[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=529951

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

texlive-2009 breakage?

[Neal Becker]

I had texlive* installed.

After today's update, I no longer have any /usr/share/texlive directory!

I'm guessing some install script removed it??

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

King InuYasha  wrote:

> While it is true that the GPL permits linking to CDDL libraries, that is
> only in the case if the library is a "system library," which is a library
> that is NECESSARY for working on a particular OS. This is usually how it is

Please show me the exact place in the GPL text thatyou have in mind to 
prove your claim.

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

Simo Sorce  wrote:

> On Tue, 2009-11-03 at 12:58 +0100, Joerg Schilling wrote:
> > 
> > The conclusion of all lawyers I did talk to, is that there is no legal
> > problem 
> > with original source.
>
> There is no problem with the **source**, but the binary results most
> probably cannot be distributed, because they combine in a single work 2
> incompatible licenses.

Mkisofs is fully under GPL and there is no single work created that
combines licenses. For this reason, there is no problem with the binaries.
Note that Sun of course distributes binaries and that Sun legal checked whether
distributing binaries from cdrtools could cause problems. 

> Have you thought about using GPLv3 instead ?

When the first GPLv3 draft was announced, the GPLv3 looked very interisting as
GPLv3 was announced to be more permissive against OSS than GPLv2 but 
unfortunately, 
the final GPLv3 is a more restrictive license than GPLv2.

> It may be more compatible with CDDL (needs to be run through real
> lawyers first of course).

While the GPLv2 gives explicit compatibility for GPLd programs to use any kind
of independent library (as an independent library does not create a drived work
from just linking against it), GPLv3 introduced a limitation against such 
combinations that is not in GPLv2.

BTW: I am happy to see your post as this is the first post from a Red Hat person
that looks respectful and interested in a solution. I hope we can find a 
solution for the current problem.



Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[King InuYasha]

On Tue, Nov 3, 2009 at 8:53 AM, Joerg Schilling <
joerg.schill...@fokus.fraunhofer.de> wrote:

> Chris Adams  wrote:
>
> > You have refused to cite specific legal problems with cdrkit, so there
> > are no "known legal problems" that anyone can see.  The proper reporting
> > method is bugzilla.redhat.com; can you point to where you reported them?
>
> It seems that you did never check this as otherwise you did know the
> reports.
>
> Jörg
>
>
Just with a quick search in the Red Hat Bugzilla, only though distro section
Fedora, I found this:
https://bugzilla.redhat.com/buglist.cgi?component=cdrkit&product=Fedora

Listed
39 bugs. A quick look shows a disturbing amount of WONTFIX (ignoring
rhbz#472924). But I also see things have still been progressing. However,
what I want to know is what prompted the relicense to CDDL in the first
place? From what I can see, Jörg Schilling, you are the maintainer and
creator of the "original software" cdrtools. Also, why are you so hostile to
cdrkit? The implicitly permits forking via its redistribution clause. If you
wanted to be able to mix with proprietary code and non-Linux systems, the
LGPL would have been just as good.

While it is true that the GPL permits linking to CDDL libraries, that is
only in the case if the library is a "system library," which is a library
that is NECESSARY for working on a particular OS. This is usually how it is
justified that GPL software can be built using Visual Studio on Windows,
even if I personally don't like it. The runtime library in Windows is almost
certainly not GPL compatible, as was the case for many other UNIX
application runtime libraries at the time. That is what they built into the
GPL, not a "free for all" library linking exception.
-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Simo Sorce]

On Tue, 2009-11-03 at 15:43 +0100, Josephine Tannhäuser wrote:
> The quality of the content of your Messages sometimes extremly differs
> from your behavior, your way how you tell it. Perhaps it is me (as a
> woman) who is very sensitive in that case.

Josephine,
be reassured, it's definitely not you.

Jörg is a known "personality" ...

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Simo Sorce]

On Tue, 2009-11-03 at 12:58 +0100, Joerg Schilling wrote:
> 
> The conclusion of all lawyers I did talk to, is that there is no legal
> problem 
> with original source.

There is no problem with the **source**, but the binary results most
probably cannot be distributed, because they combine in a single work 2
incompatible licenses.

Have you thought about using GPLv3 instead ?
It may be more compatible with CDDL (needs to be run through real
lawyers first of course).

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

Chris Adams  wrote:

> You have refused to cite specific legal problems with cdrkit, so there
> are no "known legal problems" that anyone can see.  The proper reporting
> method is bugzilla.redhat.com; can you point to where you reported them?

It seems that you did never check this as otherwise you did know the reports.

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Tom "spot" Callaway]

On 11/03/2009 09:52 AM, Chris Adams wrote:
> Once upon a time, Joerg Schilling  said:
>> -Redhat continues to distribute "cdrkit" although there are
>>  known legal problems with it and Redhat has been informed more that
>>  once about this fact.
> 
> it is "Red Hat", not "Redhat" (and this is Fedora).
> 
> You have refused to cite specific legal problems with cdrkit, so there
> are no "known legal problems" that anyone can see.  The proper reporting
> method is bugzilla.redhat.com; can you point to where you reported them?

Guys, this is a friendly pre-warning. This thread is now covered under
the hall-monitor policy. Feel free to take this discussion to
fedora-legal, or preferrably, off-list. Future posts on this thread will
receive a formal warning.

See: https://fedoraproject.org/wiki/Hall_Monitor_Policy

~spot

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Buyer Beware: A Major Change in NFS (in Rawhide) is about to happen

[Doug Ledford]

On 11/03/2009 07:47 AM, Steve Dickson wrote:
> On 11/02/2009 03:02 PM, Jesse Keating wrote:
>> On Mon, 2009-11-02 at 14:23 -0500, Steve Dickson wrote:
>>> I'm not sure about this... Actually I like the fact we can define a 
>>> pseudo root other than '/'... which means you really want a live exported
>>> directory with the fsid=0 option... If I am understanding what you are 
>>> saying... 
>>
>> No, that's not what he's saying.  Even if you define a different psuedo
>> root other than /, it's likely more common to /not/ want that root
>> exported in whole, but rather smaller parts of it, just like you don't
>> want / exported in whole, you only want subdirectories exported.
> Lets add some context to this since I *really* do want to understand 
> what you guys are saying... 
> 
> /export *(ro,fsid=0)
> /export/home *(rw)
> 
> With the above exports the only part of the server's real root ('/')
> that is exposed is the /export directory. So when a client does a 
>  'mount -o v4 server:/ /mnt'
> 
> The client will only be able to see /mnt/home (or the /export/home
> export).
> 
> So as far as exposure, being able to define the root the client 
> will see, I think, is good thing since it will protect (or hide) 
> the rest of server's real root directories... 
> 
> So this is why I'm understanding why the '/export' of the 
> '/export *(ro,fsid=0)' should not be a live export directory? 

I understand that, what I'm saying is that the setting of the pseudo
root and the setting of an export *NEED* to be two different things.  In
the past, any NFS export was always a real export and the only pseudo
root was always the / filesystem, *BUT* just because the / filesystem
was the pseudo root did *NOT* mean that the / filesystem itself was
mountable by clients unless it was exported in a separate export line
(get the distinction here: pseudo root existed, but wasn't exported).
Now you are telling us to create a pseudo root entry in the exports
file, and that entry is indicated by fsid=0, but you are also telling us
that simply the act of setting that entry will then add *both* a pseudo
root and a live export of the pseudo root to the world.  There are many
situations I can imagine where I need the pseudo root to be something I
don't actually export, the most common and immediate case being that I
serve both NFSv4 and NFSv{3,2} where their pseudo root is always / and I
want both to have the same namespace and therefore I need v4 to have a /
pseudo root.

So, what should an exports file look like if I want to have a shared
v2/v3/v4 exports?  Let's say I actually *do* want my / filesystem to be
ro mountable, then it should look like this:

/ *(ro,fsid=0) # this to set the pseudo root for v4
/ *(ro)# this to export /
/home *(rw)# you get the point

If, on the other hand, I have v2/v3/v4 enabled and I want them to have
the same mount points, and / is not one of those mount points, it should
look like this:

/ *(ro,fsid=0) # again, this should set the pseudo root *only*
/home *(rw)# now all versions see this mount, and this mount only

Now, are you saying that we should just leave out setting the pseudo
root if we don't want / to be exported in this case and that will get us
the same thing because the default pseudo root will be / anyway?  If so,
that's broken behavior (that leaving the pseudo root to be a default
will set the root but not export it while setting the root will cause
the root to be exported).

As another scenario consider this:  I serve out files to Windows, Mac,
and Linux computers.  The files are all located under /srv.  It would be
reasonable for me to define /srv as my pseudo root, especially as I have
multiple linux specific directories immediately under /srv (/srv/Linux,
/srv/Fedora, /srv/RHEL*, /srv/koji).  However, I also have /srv/OS-X and
/srv/Windows.  So let's say I create the exports file as such:

/srv *(ro,fsid=0)
/srv/Linux *(rw)
/srv/Fedora *(ro)
/srv/RHEL4 *(ro)
/srv/RHEL5 *(ro)
/srv/koji *(ro)

What I want out of this is on all of my clients, I want (expect) the
following command to fail:

mount server:/ /srv

I want the following command to succeed:

mount server:/Linux /srv/Linux

So, my point in all of this is that for the entire existence of the
pseudo root to date, it has always existed without also being exported
unless explicitly exported aside from being set.  You can not now change
that so that setting the pseudo root also exports it.  This would be a
massive regression.  More importantly though, there are any number of
perfectly valid scenarios where one might want to set the pseudo root
without also exporting it.  Forcing those two acts to be one and the
same more or less renders the whole feature so broken as to be
impractical to use, by design.

-- 
Doug Ledford 
  GPG KeyID: CFBFF194
  http://people.redhat.com/dledford

Infiniband specific RPMs available at
  http://people.redhat.com/dledford/Infiniband



signature.asc
D

Re: Wodim trouble

[Chris Adams]

Once upon a time, Joerg Schilling  said:
> - Redhat continues to distribute "cdrkit" although there are
>   known legal problems with it and Redhat has been informed more that
>   once about this fact.

it is "Red Hat", not "Redhat" (and this is Fedora).

You have refused to cite specific legal problems with cdrkit, so there
are no "known legal problems" that anyone can see.  The proper reporting
method is bugzilla.redhat.com; can you point to where you reported them?

-- 
Chris Adams 
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

"Tom \"spot\" Callaway"  wrote:

> Since nothing has changed, please consider this thread closed. Continued
> postings will be handled under the moderation policies.

So let us conclude:

-   Redhat continues to distribute "cdrkit" although there are
known legal problems with it and Redhat has been informed more that
once about this fact.

-   Redhat still does not like to distribute the legal original software.

-   Redhat still ignores the demands of the users that like to have
usable software.

Is this what redhat understands by "living OpenSource"?

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Josephine Tannhäuser]

2009/11/3, Joerg Schilling :
> Fortunately, you are of limited relevance and other people did not behave
> hostile but friendly ;-)
Sorry Joerg,

but Imho it isn't friendly to come to a booth, thump the table and
say: "Remove illegal software from fedora distribution, mature at the
end of the year, or I will sue you." This isn't a friendly way.

The booth-personnel and the bystanders didn't know with this action
WHO you are or WHAT do you really want.. btw it's imho a little bit
duffy to come with this request to a booth on an event like
"Chemnitzer Linux Tage".

The quality of the content of your Messages sometimes extremly differs
from your behavior, your way how you tell it. Perhaps it is me (as a
woman) who is very sensitive in that case.

Perhaps this is sometimes the reason that differs the pov of your
counterpart "you have the point" from "you are a troll". Think about
it, perhaps twice!
-- 
Josephine "Fine" Tannhäuser
2.6.29.6-213.fc11.i586

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Tom "spot" Callaway]

On 11/03/2009 09:13 AM, Matěj Cepl wrote:
> Dne 3.11.2009 02:55, King InuYasha napsal(a):
>> The only thing I can figure out from this conversation is that the CDDL
>> is supposed to be incompatible with the GPL. If that's the case, why not
>> simply ask the original creator to kindly dual license it? 
> 
> You must be new here :)
> Concerning legal issues with cdrkit, please, take a look at
> http://thread.gmane.org/gmane.linux.redhat.fedora.legal/473
> 
> and of course
> 
>   \|||/
>   (o o)
>  |ooO~~(_)~~~|
>  | Please|
>  | don't feed the|
>  | TROLLS !  |
>  '~~Ooo~~'
>  |__|__|
>   || ||
>  ooO Ooo

Indeed. Specifically, the formal stance of the Fedora Project (and Red
Hat Legal) is contained within my original reply to Mr. Schilling here:

http://article.gmane.org/gmane.linux.redhat.fedora.legal/528

Since nothing has changed, please consider this thread closed. Continued
postings will be handled under the moderation policies.

Thanks,

~spot

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: PPC not getting __WORDSIZE set

[Jakub Jelinek]

On Tue, Nov 03, 2009 at 09:28:45AM -0500, Adam Jackson wrote:
> What header defines __ILP32__ or __LP64__?

Nothing defines __ILP32__, only __LP64__:

$ gcc -m64 -E -dD -xc /dev/null | grep LP64
#define _LP64 1
#define __LP64__ 1
$ gcc -m32 -E -dD -xc /dev/null | grep LP64

Jakub

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: PPC not getting __WORDSIZE set

[Adam Jackson]

On Mon, 2009-11-02 at 23:34 +0100, Jakub Jelinek wrote:
> On Mon, Nov 02, 2009 at 05:15:50PM -0500, Bryan Kearney wrote:
> > Word of warning.. I am no too familiar with C across platforms.  I am  
> > trying to package ruby-ffi (spec file is at [1]) and when I do a scratch  
> > build in Koji [2] it runs fine on x86 but is failing in ppc_64. It  
> > appears that __WORDSIZE is not being set [3]. I looked at the CFLags for  
> > the x86_64 and they are the same, so I assumed things would run fine.  
> > Can anyone point me at what to look at next?
> 
> __WORDSIZE is a glibc internal macro, packages shouldn't be using it.
> Whether it is defined or not depends on whether any of the headers that are
> included needed to check that macro or not.
> 
> You should be using __LP64__ or similar macros instead.

atropine:~% : | cpp -dM | grep -c LP 
0

What header defines __ILP32__ or __LP64__?

Of course there's also:

atropine:~% : | cpp -dM | grep SIZEOF
#define __SIZEOF_INT__ 4
#define __SIZEOF_POINTER__ 4
#define __SIZEOF_LONG__ 4
#define __SIZEOF_LONG_DOUBLE__ 12
#define __SIZEOF_SIZE_T__ 4
#define __SIZEOF_WINT_T__ 4
#define __SIZEOF_PTRDIFF_T__ 4
#define __SIZEOF_FLOAT__ 4
#define __SIZEOF_SHORT__ 2
#define __SIZEOF_WCHAR_T__ 4
#define __SIZEOF_DOUBLE__ 8
#define __SIZEOF_LONG_LONG__ 8

- 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: Wodim trouble

[Aioanei Rares]

On 11/03/2009 03:08 PM, Joerg Schilling wrote:

Josephine Tannhäuser  wrote:

   

2009/11/3, Joerg Schilling:
 

Josephine Tannhäuser  wrote:
It seems that you have not been there.
   

I was there and I was shocked about your behavior.
 

Fortunately, you are of limited relevance and other people did not behave
hostile but friendly ;-)

Jörg

   
Yeah, good way to expect any collaboration with that attitude. Keep up 
the good work.


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Matěj Cepl]

Dne 3.11.2009 02:55, King InuYasha napsal(a):
> The only thing I can figure out from this conversation is that the CDDL
> is supposed to be incompatible with the GPL. If that's the case, why not
> simply ask the original creator to kindly dual license it? 

You must be new here :)
Concerning legal issues with cdrkit, please, take a look at
http://thread.gmane.org/gmane.linux.redhat.fedora.legal/473

and of course

  \|||/
  (o o)
 |ooO~~(_)~~~|
 | Please|
 | don't feed the|
 | TROLLS !  |
 '~~Ooo~~'
 |__|__|
  || ||
 ooO Ooo


-- 
http://www.ceplovi.cz/matej/, Jabber: mceplceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC

Faithful love is what people look for in a person; ...
   -- Proverbs 19:22 (NJB)

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

rawhide report: 20091103 changes

[Rawhide Report]

Compose started at Tue Nov  3 06:15:13 UTC 2009













New package calibre
E-book converter and library management
New package intrace
Traceroute-like application for network reconnaisance
New package perl-Makefile-Parser
Simple parser for Makefiles
New package python-tornado
Scalable, non-blocking web server and tools
New package rubygem-abstract
Allows you to define an abstract method in Ruby
Removed package DeviceKit
Removed package sublib
Updated Packages:

CGAL-3.5-1.fc12
---
* Sun Oct 18 2009  - 3.5-1
- New upstream release: finale version of CGAL-3.5.


DeviceKit-disks-009-1.fc12
--
* Mon Nov 02 2009 David Zeuthen  - 009-1.fc12
- Update to release 009 (bugfixes, #528874)


PackageKit-0.5.4-0.1.20091029git.fc12
-
* Thu Oct 29 2009 Richard Hughes   - 0.5.4-0.1.20091029git
- Update to a newer git snapshot from the 0.5.x series.
- Check the language code exists before we search for it.
- Add the missing InstallSignature role from the backend auto-detection.
- Disable repos that are not contactable at backend start.
- Don't allow double clicking SRPM and fix the cryptic message.
- Fixes #529349, #531105, #530945, #531306 and #530264


PyQwt-5.2.0-2.fc12
--
* Wed Oct 28 2009 Tadej Janež  5.2.0-2
- made qplt.py executable (to fix a rpmlint error)
- removed html/.buildinfo from sphinx documentation (to fix a rpmlint error)
- changed BuildRequires from numpy to numpy-f2py to cope with the numpy
  package split
- temporarily removed qwt.py* files which conflict with the ones provided
  by the PyQt4 package


anaconda-12.42-1.fc12
-
* Fri Oct 30 2009 Chris Lumens  - 12.42-1
- Use the new anaconda image in fedora-logos (#529267). (jkeating)
- Also mark the Back button as translatable (#526925). (clumens)
- Call udev_trigger with "change", not "add", to populate udev db. (#531052)
  (dlehman)
- Allow callers of udev_trigger to specify the action string. (dlehman)
- Add the bcm5974 kernel module needed for some touchpads (#474225).
  (clumens)
- Fix "resize failed: 1" errors for ext2/ext3/ext4 (#517491). (dcantrell)
- Put the icon back on the Back button on livecd installs (#526925).
  (clumens)
- Use /dev/mapper/live-osimg-min instead of the old device node name
  (#526789). (clumens)


asterisk-sounds-core-1.4.16-2.fc12
--
* Mon Nov 02 2009 Jeffrey C. Ollie  - 1.4.16-2
- Remove fr/1.g729 as it's triggering an error in magic_file(3) (BZ#532489)

* Mon Oct 05 2009 Jeffrey C. Ollie  - 1.4.16-1
- Update to 1.4.16.


at-spi-1.28.1-1.fc12

* Mon Oct 19 2009 Matthias Clasen  - 1.28.1-1
- Update to 1.28.1


bluez-4.57-2.fc12
-
* Mon Nov 02 2009 Bastien Nocera  4.57-2
- Move the rfcomm.conf to the compat package, otherwise
   the comments at the top of it are confusing

* Sun Nov 01 2009 Bastien Nocera  4.57-1
- Update to 4.57


brltty-4.1-3.fc12
-
* Sun Nov 01 2009 Stepan Kasal  - 4.1-3
- build the TTY driver (it was disabled since it first appered in 3.7.2-1)
- build with speech-dispatcher, packed into a separate sub-package

* Fri Oct 30 2009 Stepan Kasal  - 4.1-2
- move data-directory back to default: /etc/brltty
- move brltty to /bin and /lib, so that it can be used to repair the system
  without /usr mounted (#276181)
- move vstp and libbrlttybba.so to brlapi
- brltty no longer requires brlapi
- brlapi now requires brltty from the same build


celt-0.7.0-1.fc12
-
* Fri Oct 30 2009 Peter Robinson  0.7.0-1
- New 0.7.0 upstream release


cernlib-2006-34.fc12

* Thu Oct 01 2009 Hans de Goede  2006-34
- Fix FTBFS

* Fri Jul 24 2009 Fedora Release Engineering  
- 2006-33
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild


dalston-0.1.11-1.fc12
-
* Thu Oct 29 2009 Peter Robinson  0.1.11-1
- new upstream 0.1.11 release


desktop-backgrounds-9.0.0-11

* Tue Nov 03 2009 Christoph Wickert  - 9.0.0-11
- Bump release for RC

* Sun Nov 01 2009 Christoph Wickert  - 9.0.0-10
- Update for F12 constantine artwork


eclipse-3.5.1-4.fc12

* Fri Oct 30 2009 Andrew Overholt  1:3.5.1-4
- Make /usr/bin/eclipse a wrapper script due to rhbz#531675 (e.o#290395).

* Wed Oct 28 2009 Alexander Kurtakov  1:3.5.1-2
- Don't install 2 desktop files. (rhbz #530450)


eclipse-photran-5.0.0-0.2.200910081739.fc12
---
* Fri Oct 30 2009 Orion Poplawski  - 5.0.0-0.2.200910081739
- Cleanup spec headers
- Drop gcj support
- Add needed Requires


epiphany-extensions-2.28.1-2.fc12
-
* Sun Nov 01 2009 Matthias Clasen  - 2.28.1-2
- Don't require epiphany-devel (#529624)


gbirthday-0.5.2-3.fc12
--
* Fri Oct 30 2009 Thomas Spura  0.5.2-1
- New Release

* Fri Oct 30 2009 Thomas Spura  0.5.2-2
- little problem with 'mak

Re: Wodim trouble

[Joerg Schilling]

Josephine Tannhäuser  wrote:

> 2009/11/3, Joerg Schilling :
> > Josephine Tannhäuser  wrote:
> > It seems that you have not been there.
> I was there and I was shocked about your behavior.

Fortunately, you are of limited relevance and other people did not behave 
hostile but friendly ;-)

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Richard Hughes]

2009/11/3 Joerg Schilling :
> if there legal department was wrong. I still do not understand why Companies
> like Redhat do not siply ask their lawyers for legal assistence. If they did,
> they would have better advise about cdrtools.

Just a small thing that drives me crazy. The company name is "Red Hat"
not Redhat. People don't write your name Joergschilling, do they?
Thanks.

Richard.

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

Kevin Kofler  wrote:

> Joerg Schilling wrote:
> > There are some people who claim that there is a legal problem with the
> > original software but none of the persons who spread this claim (including
> > people from redhat) did ever make a valid legal statement that could
> > confirm a problem. As there are no valid legal arguments _against_ the
> > situation in cdrtoools, there is obviously no way to discuss things and we
> > need to rate the claims against cdrtools as libel.
>
> They are making a very concrete claim: if one piece of some program is under 
> the GPL, the ENTIRE program, including all its libraries, MUST be under the 
> GPL or a compatible license. This is confirmed e.g. by the FSF:
> http://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean
> http://www.gnu.org/licenses/gpl-faq.html#MereAggregation
> http://www.gnu.org/licenses/gpl-faq.html#GPLModuleLicense
> http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs

You seem to miss that the license mkisofs is using is called "GPL" and not 
"GPL FAQ", so the quoting you mention do not apply.

The GPL requires the entire work to be under GPL and the "entire work mkisofs" 
_is_ of course under GPL.

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

Julian Sikorski  wrote:


> Ok, putting the ad personam arguments aside, there are two important facts:
> - cdrecord is still under active development, but there might be a
> problem with distributability (Sun lawyers say there is not, but I guess

There is no problem with distributibility as Sun would risk being sued
if there legal department was wrong. I still do not understand why Companies
like Redhat do not siply ask their lawyers for legal assistence. If they did,
they would have better advise about cdrtools.

> RH would like to make their own legal review to be on the safe side)
> - cdrkit is in sort of maintenance mode, and it does not support UDF
> filesystem for DVD discs correctly, and the situation is unlikely to improve

Cdrkit is unmaitained and has legal problems. Companies who distribute cdrkit
ignore the legal problems and need to be aware of legal consequences.


> - libburn is also developed actively, but it lacks UDF support as well [1]
> So, while waiting for libburn to improve, we could either take over
> cdrkit development, or do a(nother) legal review of cdrecord. It seems
> that the latter should be simpler, given that it's a one-time effort.

Libburn is based on a wrong asumption: libburn only works partly on Linux in 
non-root mode and the vast majority of other OS needs root permissions to burn.
Creating a burn library (well it is non-portable) based on these constraints 
will result in GUI applications that are non-portable and would require root
permissions on most platforms. Installing a GUI suid root is an absolute no-go
as GUIs are so compley that it is hard to audit the code for security problems.

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Including windows-binary files for cross compiling into package

[Richard W.M. Jones]

On Mon, Oct 26, 2009 at 07:42:56PM +0100, Joost van der Sluis wrote:
> On Mon, 2009-10-26 at 11:15 -0700, Roland McGrath wrote:
> > If it's true cross support, then that should be a noarch package and the
> > file names it uses should not depend on %{_lib} that way.  
> > Arguably it even belongs in %{_sharedir}, since it is fixed binary content
> > across all host machines.
> 
> Those files are not architecture independent. They are somewhat similar
> to .o files. They contain the run time library for the language,
> compiled to native windows object files. If you want to compile your own
> program with them afterwards, they are linked together into a windows
> executable.
> 
> You could argue that they should belong in a -devel package. But since
> this package is a compiler, we decided not to split it up into a devel
> package and a non-devel package. As that would be pointless, as one will
> not work without the other.

Sorry, I'm late on this one.  Yes the files *are* arch independent
from the point of view of the host, so they should be noarch.  The
real problem is that RPM and the rest of the toolchain doesn't
understand the cross-compilation situation at all.

Anyway you may find the Fedora MinGW packaging guidelines to be
helpful, and it would be useful to make your package compatible with
the other ones, even if that deviates from upstream a little bit.

  http://fedoraproject.org/wiki/Packaging/MinGW
  http://fedoraproject.org/wiki/MinGW
  http://fedoraproject.org/wiki/MinGW/Packaging_issues

We've also packaged some things, such as the OCaml cross-compiler,
which sound very similar to the Pascal case you describe.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

Mat??j Cepl  wrote:

> Dne 3.11.2009 05:22, Ankur Sinha napsal(a):
> > I just wanted to know if wodim is usable (i mean without wasting dvds
> > like its doing currently for me). From the discussion, I feel it's still
> > buggy and therefore I'm going to shift to another program (maybe
> > growisofs).
>
> Yes, wodim is perfect. Joerg is just spreading FUD.

And Earth is a disk.

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Josephine Tannhäuser]

2009/11/3, Joerg Schilling :
> Josephine Tannhäuser  wrote:
> It seems that you have not been there.
I was there and I was shocked about your behavior.
-- 
Josephine "Fine" Tannhäuser
2.6.29.6-213.fc11.i586

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Buyer Beware: A Major Change in NFS (in Rawhide) is about to happen

[Steve Dickson]

On 11/02/2009 03:02 PM, Jesse Keating wrote:
> On Mon, 2009-11-02 at 14:23 -0500, Steve Dickson wrote:
>> I'm not sure about this... Actually I like the fact we can define a 
>> pseudo root other than '/'... which means you really want a live exported
>> directory with the fsid=0 option... If I am understanding what you are 
>> saying... 
> 
> No, that's not what he's saying.  Even if you define a different psuedo
> root other than /, it's likely more common to /not/ want that root
> exported in whole, but rather smaller parts of it, just like you don't
> want / exported in whole, you only want subdirectories exported.
Lets add some context to this since I *really* do want to understand 
what you guys are saying... 

/export *(ro,fsid=0)
/export/home *(rw)

With the above exports the only part of the server's real root ('/')
that is exposed is the /export directory. So when a client does a 
 'mount -o v4 server:/ /mnt'

The client will only be able to see /mnt/home (or the /export/home
export).

So as far as exposure, being able to define the root the client 
will see, I think, is good thing since it will protect (or hide) 
the rest of server's real root directories... 

So this is why I'm understanding why the '/export' of the 
'/export *(ro,fsid=0)' should not be a live export directory? 

steved.

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

Josephine Tannhäuser  wrote:

> 2009/11/3 Conrad Meyer 
>
> > In this case, upstream (wodim) is a fork of Joerg Schilling's project.
> > Wodim
> > was forked from cdrecord because Joerg is crazy. Joerg likes to call wodim
> > "the broken fork" and cdrecord "the original software".
> >
> He visited all the booths of linux distributions at "Chemnitzer Linux Tage"
> and started some trouble.

It seems that you have not been there.

I have a good relationship to Linux developers and projects and I did have nice 
conversations with many people in Chemnitz. 

Note that there was even a very good relationship with Debian _before_ Eduard 
Bloch became packetizer for cdrtools and started his attacks. It is obvious that
the problems we are still wasting out time with is just one hostile person 
called Eduard Bloch.

I hope that the OSS community finds a way to workaround the problems he created.

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

texlive-2009 man & info

[Neal Becker]

I'm trying texlive-2009 packages for f11.  I see man and info pages get 
installed (not in standard system locations, but into texlive tree), but man 
and info search paths don't seem to be setup to find them.

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

King InuYasha  wrote:

> The only thing I can figure out from this conversation is that the CDDL is
> supposed to be incompatible with the GPL. If that's the case, why not simply
> ask the original creator to kindly dual license it?

First, it is definitely wrong that the CDDL was made incompatible with the GPL.
The person who brouhgt this claim into public is a former Sun Employee who was
disappointed that the restrictions in the GPL made the GPL impossible for use
with OpenSolaris.

In fact, the GPL is incompatible to nearly all licenses around and this is 
definitely an intended "feature" from the authors of the GPL.


For our discussion, it is important to know whether a possible _general_ 
incompatibility between two licenses could affect a _special_ situation in a
collective work, so let us have a look at the GPL:

The GPL forbids to mix GPL and non-GPL within _one_ _single_ work
and the GPL forbids to create a derived work from a GPLd work
if the derived work is not put under GPL.

Let us look at the "work" mkisofs. This work is a _pure_ GPLd work. It does
not mix GPL and non-GPL code in a single work. With mkisofs, there is also no 
"derived work" that has to be taken into account. The fact that mkisofs
links against CDDLd libs does not create a derived work but ist only a permitted
collective work.


For a more detailed review, please have a look at this book from Lawrence Rosen:
http://www.rosenlaw.com/Rosen_Ch06.pdf who is an independent lawyer who counsels
the OpenSource initiative. The relevent parts for the mkisofs case are on page 
128.


People wo claim that mkisofs has a problem usually missinterpret GPL section 3, 
the paragraph that is past 3 c): This special exception was introduced because
the GPL precursor did contain an illegal claim that forced distributors of 
binaries from GPLd programs to distribute the source of the GPLd program _plus_
the libc from the Operating System the binary was compiled for. As this is a 
claim that is in conflict with the permissions that have been given with the OS
license, the GPL tried to enforce something that was impossible. In the late 
1980s, the so called OS library exception was added in order to prevent 
distributors of binaries to be forced to do illegal things. This section is 
obviously absolutely not related to any special license compatibility grant. It 
just allows to avoid being forced to ship libc.

The conclusion of all lawyers I did talk to, is that there is no legal problem 
with original source.

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Kevin Kofler]

Joerg Schilling wrote:
> There are some people who claim that there is a legal problem with the
> original software but none of the persons who spread this claim (including
> people from redhat) did ever make a valid legal statement that could
> confirm a problem. As there are no valid legal arguments _against_ the
> situation in cdrtoools, there is obviously no way to discuss things and we
> need to rate the claims against cdrtools as libel.

They are making a very concrete claim: if one piece of some program is under 
the GPL, the ENTIRE program, including all its libraries, MUST be under the 
GPL or a compatible license. This is confirmed e.g. by the FSF:
http://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean
http://www.gnu.org/licenses/gpl-faq.html#MereAggregation
http://www.gnu.org/licenses/gpl-faq.html#GPLModuleLicense
http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs

> I even tried to discuss the social problem with some people from redhat
> but I was only given FUD instead of arguments. In return, I repeatedly
> asked for legal arguments that could be discussed, to no avail. So redhat
> also proves the same and it is obvious that there are no valid legal
> arguments that could confirm a problem with the original softare.

That's just false. You refused to take legal arguments from Fedora's legal 
contact (who is responsible for communication between RH Legal and the 
Fedora community) on the grounds that he's not a lawyer and demanded to 
speak directly to the lawyers. You ignored all the arguments he brought up, 
no matter how valid.

> Note that the GPL was designed to be compatible with all independently
> developed libraries under any license. This is a decision that was made in
> the late 1980s and I know the background of this diiscussion as I did take
> part in it. The GPL would have been completely unuaable if it was not made
> legally compatible with any independent library under any license.

Then I have a breaking news for you: the GPL *is* "completely unusable". 
Nevermind all those projects who can use it just fine while honoring these 
terms you refuse to accept. :-/

> Even Eben Moglen confirmed that there is absolutely no problem with
> letting GPLd programs use CDDLs libs as this is of course no more then
> "mere aggregation", and permitted by the GPL.

You are misrepresenting Eben Moglen's position. The FSF's GPL FAQ, which he 
helped write, clearly says "If the modules are included in the same 
executable file, they are definitely combined in one program. If modules are 
designed to run linked together in a shared address space, that almost 
surely means combining them into one program." So this is not "mere 
aggregation".

> Sun did make a legal review on cdrtools im May 2006 already, but in order
> to be very sure, I asked Sun legal to repeat the legal review on cdrtools
> last autumn. After doing the review, Sun legal confirmed again that there
> is no problem with the original software.

Red Hat, like pretty much any other company, cannot trust other companies' 
legal departments. The relevant opinion is going to be Red Hat Legal's, 
sorry. (And FWIW, I have no idea why Sun is coming to that conclusion which 
directly contradicts the FSF's opinion, see the GPL FAQ.)

> It seems that the people who claim legal problems do not like to get into
> a discussion as with a fact based discussion, it would be easy to prove
> that they are wrong.

It is you who boycotted the fact-based discussion on ad hominem grounds 
(i.e. "you're not a lawyer, I won't listen to you", nevermind that you 
aren't one either).

Kevin Kofler

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Gianluca Sforna]

On Tue, Nov 3, 2009 at 11:58 AM, Julian Sikorski  wrote:
> So, while waiting for libburn to improve, we could either take over
> cdrkit development, or do a(nother) legal review of cdrecord. It seems
> that the latter should be simpler, given that it's a one-time effort.
>
Already done around June:
http://thread.gmane.org/gmane.linux.redhat.fedora.legal/473


-- 
Gianluca Sforna

http://morefedora.blogspot.com
http://www.linkedin.com/in/gianlucasforna

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Julian Sikorski]

W dniu 03.11.2009 11:37, Matěj Cepl pisze:
> Dne 3.11.2009 05:22, Ankur Sinha napsal(a):
>> I just wanted to know if wodim is usable (i mean without wasting dvds
>> like its doing currently for me). From the discussion, I feel it's still
>> buggy and therefore I'm going to shift to another program (maybe
>> growisofs).
> 
> Yes, wodim is perfect. Joerg is just spreading FUD.
> 
> Matěj
> 
Ok, putting the ad personam arguments aside, there are two important facts:
- cdrecord is still under active development, but there might be a
problem with distributability (Sun lawyers say there is not, but I guess
RH would like to make their own legal review to be on the safe side)
- cdrkit is in sort of maintenance mode, and it does not support UDF
filesystem for DVD discs correctly, and the situation is unlikely to improve
- libburn is also developed actively, but it lacks UDF support as well [1]
So, while waiting for libburn to improve, we could either take over
cdrkit development, or do a(nother) legal review of cdrecord. It seems
that the latter should be simpler, given that it's a one-time effort.

Julian

[1] http://libburnia-project.org/ticket/106

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: FESCo meeting summary for 20091030

[Michael Schwendt]

On Mon, 2 Nov 2009 23:08:53 -0500, Jon wrote:

> * fluidsynth and PA  (jds2001, 17:04:44)
>   * LINK: http://markmail.org/message/bovdqb7na3zor2ck - without
> comment.  (mjg59, 17:17:07)
>   * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=500087#c13
> (jds2001, 17:19:22)
>   * AGREED: PA backend for fluidsynth must be built. If the current
> maintainer refuses, Kevin_Kofler will take over as maintainer.
> (jds2001, 17:32:01)

17:18:45  the package is a leafnode
17:18:47  NOTHING requires
17:18:48  it

Not true. See: repoquery --whatrequires fluidsynth-libs --alldeps

Building with PA support would add a dependency also to the backend
library package, not just to the console ui.

-- 
Btw, note that it could be built also with additional PortAudio support. ;·)

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Matěj Cepl]

Dne 3.11.2009 05:22, Ankur Sinha napsal(a):
> I just wanted to know if wodim is usable (i mean without wasting dvds
> like its doing currently for me). From the discussion, I feel it's still
> buggy and therefore I'm going to shift to another program (maybe
> growisofs).

Yes, wodim is perfect. Joerg is just spreading FUD.

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mceplceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC

Always make new mistakes
   -- Esther Dyson

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

Julian Sikorski  wrote:

> > On 11/02/2009 03:47 PM, Denis Leroy wrote:
> >> On 11/02/2009 07:18 PM, Adam Jackson wrote:
> >>> That may be true, but since cdrecord is not shippable, it's a pretty
> >>> vacuous truth.
> >>
> >> Out of curiosity, was that just because of the GPL2-CDDL mix ? Or was
> >> there another reason ? Last I checked, only mkisofs is affected by that
> >> and the rest of cdrecord is pure CDDL. If we patched mkisofs away, would
> >> it be shippable ?

...

> opensuse are shipping cdrecord, maybe it would be worth checking what
> they changed, if at all?

There is no legal problem with the original software, there is only a social
problem caused by a hostile downstream (a Debian packager). See 
http://cdrecord.berlios.de/private/linux-dist.html for an overview.

Let me give you some background on the legal situation:

There are some people who claim that there is a legal problem with the original
software but none of the persons who spread this claim (including people from 
redhat) did ever make a valid legal statement that could confirm a problem. As 
there are no valid legal arguments _against_ the situation in cdrtoools, there 
is obviously no way to discuss things and we need to rate the claims against 
cdrtools as libel.

I even tried to discuss the social problem with some people from redhat but I 
was only given FUD instead of arguments. In return, I repeatedly asked for legal
arguments that could be discussed, to no avail. So redhat also proves the same
and it is obvious that there are no valid legal arguments that could confirm a 
problem with the original softare.

Note that the GPL was designed to be compatible with all independently 
developed libraries under any license. This is a decision that was made in the 
late 1980s and I know the background of this diiscussion as I did take part in 
it. The GPL would have been completely unuaable if it was not made legally 
compatible with any independent library under any license. Even Eben Moglen 
confirmed that there is absolutely no problem with letting GPLd programs use
CDDLs libs as this is of course no more then "mere aggregation", and permitted
by the GPL.

On the other side, there is Sun. Sun is the biggest Donator of OSS and Sun 
definitely runs a legal review on _every_ piece of OSS that is going to make
it into Sun's Solaris distribution. This is needed because Sun also is the 
biggest target for atacks and legal cases and Sun for this reason is extremely
careful with distributing OSS. I can confirm that Sun lawyers are also very 
effective with detecting legal problems as they did themself find that 
"libcdio" creates a legal problem in GNOME. Sun immediately stopped shipping 
"libcdio" and we did create a replacement library that calls "cdda2wav" in 
order to avoid legal problems and in order to give better audio results. 

Sun did make a legal review on cdrtools im May 2006 already, but in order to 
be very sure, I asked Sun legal to repeat the legal review on cdrtools last 
autumn. After doing the review, Sun legal confirmed again that there is no 
problem with the original software.


It seems that the people who claim legal problems do not like to get into a 
discussion as with a fact based discussion, it would be easy to prove that 
they are wrong. As we have trustworthy confirmations from several sides,
I propose to asume that there is no legal problem dist distributing cdrtools
as long as nobody gives valid legal arguments.


Note that Suse already ships cdrtools again and that even Jörg Jaspert, the FTP 
master from Debian in a legally binding way agreed on distributing the original 
cdrtools again for Debian as soon as possible. See also:

http://cdrecord.berlios.de/private/linux-dist.html#Sun

It would be interesting to hear _arguments_ from redhat on why redhat still only
ships a broken fork with legal problems instead of the working original 
software that has no known legal problems




Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: GRUB2 In Fedora

[Rudolf Kastl]

2009/11/3 Liang Suilong :
> Some Linux distros has migrated from grub-0.97 to grub2-1.97. Grub2 provides
> more useful features to users. And it is more easy to add a new  file system
> support. But I can not see Fedora has any plan for GRUB2. I read a feature
> page on Fedora wiki. There is no progress on grub2.
> Now Fedora official repo offers grub2 package. However the version is quite
> strange. Fedora provides grub2-1.98. In fact, this version was 1.96 grabbed
> from svn repo on Aug 27th, 2008. Also, maintainer adds some patches to fix
> the bug. But GNU released grub2-1.97 just now.
> In addition, I try to write grub2 into MBR of the HDD. I do not know why. Is
> there a bug in grub2?
> --
> http://www.liangsuilong.info
> 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
>

see: http://fedoraproject.org/wiki/Features/Grub2

as for the outdated version... feel free to open a bug ticket and
request an update to the latest stable version of grub2.

kind regards,
Rudolf Kastl

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Kevin Kofler]

King InuYasha wrote:
> The only thing I can figure out from this conversation is that the CDDL is
> supposed to be incompatible with the GPL. If that's the case, why not
> simply ask the original creator to kindly dual license it?

We did, many times. He refuses to acknowledge there's any problem at all and 
insists that mixing the CDDL and the GPL is legal (despite the FSF and many 
others clearly saying it's not), citing some Sun lawyers (who clearly have 
an agenda to push the CDDL).

Kevin Kofler

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

libsndfile status?

[Michael Schwendt]

https://admin.fedoraproject.org/pkgdb/packages/bugs/libsndfile

What's up with libsndfile in Fedora and EPEL?
There are open tickets about CVEs filed in March.
There are additional tickets without any reply.

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: updating F11 GNOME release

[Kevin Kofler]

Josephine Tannhäuser wrote:

> 2009/11/2 Matthias Clasen 
> 
>> We don't do jumps to the next major GNOME version within a released
>> Fedora, that would be incompatible with our understanding of a released
>> product.
>>
> I hope the KDE-sig will take up this stance on her own releasecycles.

Uh, why? What's wrong with our updates (other than them being updates ;-) )? 
Any concrete complaints?

Kevin Kofler

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

Bastien Nocera  wrote:

> > The person from the GNOME project just verified that he attacks people who 
> > are 
> > helpful. He does not seem to be important.
>
> The person being Olav Vitters, one of the GNOME bugmasters, and that was
> at my request, after you polluted the GNOME Bugzilla with rants about
> your inadequately licensed software. Pur-lease.

Everybody can check the GNOME bugtracking system himself and verify that I have 
been banned for explaining the _technical_ background of a reported bug and for 
giving instructions on how to work around the problem.

It is obvious that Olav Vitters (and ayou??) made a social attack against an 
author 
of OpenSource software.

You are not very convincing...

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Joerg Schilling]

Ankur Sinha  wrote:

> Looks like another thread going the wrong way. 
>
> I just wanted to know if wodim is usable (i mean without wasting dvds
> like its doing currently for me). From the discussion, I feel it's still
> buggy and therefore I'm going to shift to another program (maybe
> growisofs).

Well, people like you who try to use the fork know that it is just having too
many bugs for being useful. Please note that growisofs is not the solution for 
a wider problem: growisofs of course needs mkisofs and redhat does not ship
a working mkisofs bug the broken "genisoimage".

Growisofs is also known to have problems with some DVD drives where cdrecord
has no problem.

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Josephine Tannhäuser]

2009/11/3 Conrad Meyer 

> In this case, upstream (wodim) is a fork of Joerg Schilling's project.
> Wodim
> was forked from cdrecord because Joerg is crazy. Joerg likes to call wodim
> "the broken fork" and cdrecord "the original software".
>
He visited all the booths of linux distributions at "Chemnitzer Linux Tage"
and started some trouble.
The ML and BZ of the Linuxdistros, which are using wodim is the outlet of
Jörgs furious anger about the fork and the debian maintainer who is the
upstream coder of wodim!  There was already a 'wodim vs. cdrecord'
discussion at fedora-legal-list.

I have a big respect for Jörg, not for him as person, but for his
attainments!
-- 
Josephine "Fine" Tannhäuser
2.6.29.6-213.fc11.i586
-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Wodim trouble

[Conrad Meyer]

On Monday 02 November 2009 05:55:49 pm King InuYasha wrote:
> What is going on here? I thought Fedora only shipped upstream code? What's
> all this business about having broken forks and licensing issues?
> 
> The only thing I can figure out from this conversation is that the CDDL is
> supposed to be incompatible with the GPL. If that's the case, why not
>  simply ask the original creator to kindly dual license it?

In this case, upstream (wodim) is a fork of Joerg Schilling's project. Wodim 
was forked from cdrecord because Joerg is crazy. Joerg likes to call wodim 
"the broken fork" and cdrecord "the original software".

Hope that helps,
-- 
Conrad Meyer 

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: GRUB2 In Fedora

[Joshua C.]

2009/11/3 Liang Suilong :
> Some Linux distros has migrated from grub-0.97 to grub2-1.97. Grub2 provides
> more useful features to users. And it is more easy to add a new  file system
> support. But I can not see Fedora has any plan for GRUB2. I read a feature
> page on Fedora wiki. There is no progress on grub2.
> Now Fedora official repo offers grub2 package. However the version is quite
> strange. Fedora provides grub2-1.98. In fact, this version was 1.96 grabbed
> from svn repo on Aug 27th, 2008. Also, maintainer adds some patches to fix
> the bug. But GNU released grub2-1.97 just now.
> In addition, I try to write grub2 into MBR of the HDD. I do not know why. Is
> there a bug in grub2?
> --
> http://www.liangsuilong.info
> 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
>

I don't see any need for this. The current grub (0.97) can boot from
ext4, works fine with windows and other distros and has almost (no)
other issues. why to fix it when it ain't broken?

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list