FAS mails in Spanish?

2011-11-19 Thread Martin Sourada
Hi,

just a few minutes ago I received a mail from FAS (I've double checked
that the info inside is correct and that it indeed came from fedora
infra machines) informing me of a user requesting a membership in one
of the groups I have sponsor status in. That wouldn't be surprising
were it not for the text being in Spanish (or maybe Portugal, I don't
speak these languages so I cannot tell them apart just by looking):

"El usuario Fedora @user-nick-and-mail-address@ ha
solicitado membresia para @user-nick@ en el grupo @group-name@ y
necesita un patrocinador.."

Now, the mail text is so simple I can understand the important part
without the need to translate, but I certainly would prefer to receive
such e-mails in English. Is there a chance I've set something wrong?
I've checked I have locale set to en in FAS web...

Regards,
Martin


signature.asc
Description: PGP signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Unable to get other machines to connect to samba in rawhide

2011-11-19 Thread Paul F. Johnson
Hi,

Not sure why Samba is playing up anymore, but it's dead. I've not
changed the setup (set as share with various users who should be able to
access the main box), but nothing.

The samba logs aren't that useful...

[2011/11/19 20:56:49,  0] smbd/server.c:1045(main)
  smbd version 3.6.1-75.fc17 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2011
[2011/11/19 20:56:49.501040,  0] smbd/server.c:1101(main)
  standard input is not a socket, assuming -D option

It then complains about not being able to connect to a socket

is this sort of output normal or is samba acting up?

s-c-samba is set for people to login as users (rather than share etc),
but it's still not showing on other machines (all-win7).

Paul

-- 
Vertraue mir, ich weiss, was ich mache...

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Package segfaults when built with -O2 but not with -O0

2011-11-19 Thread Kevin Kofler
Ralf Corsepius wrote:

> On 11/19/2011 06:23 AM, Gregory Maxwell wrote:
>> On Fri, Nov 18, 2011 at 11:27 PM, Ralf Corsepius 
>> wrote:
>>> If GCC is sure something is wrong, it is supposed to raise errors.
>>
>> This isn't true. E.g. you can write code which reads and uses
>> uninitialized memory
>> where the compiler is _absolutely sure_ of it. You still just get a
>> warning.
> Well, ... this would qualify as a bug in GCC, IMHO.

Unfortunately, that's what the standard requires. It requires the compiler 
to accept the code, but it allows it to compile it to anything, even to 
something deleting all your data.

Kevin Kofler

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Package segfaults when built with -O2 but not with -O0

2011-11-19 Thread Ralf Corsepius
On 11/19/2011 06:23 AM, Gregory Maxwell wrote:
> On Fri, Nov 18, 2011 at 11:27 PM, Ralf Corsepius  wrote:
>> [1] -Wstrict-aliasing is one of these cases.
>> The spots such warnings point to, often are broken, but not always,
>> because GCC has difficulties in identifying these.
>
> This use to be more true, but there are multiple levels of -Wstrict-aliasing
I know.

> and
> I would be _highly_ surprised if the default gave a false alarm.
At least older gccs (IIRC, gcc-4.4.x) did fairly often.
gcc-4.6.x is less agressively warning.

>> If GCC is sure something is wrong, it is supposed to raise errors.
>
> This isn't true. E.g. you can write code which reads and uses
> uninitialized memory
> where the compiler is _absolutely sure_ of it. You still just get a warning.
Well, ... this would qualify as a bug in GCC, IMHO.

Ralf

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Package segfaults when built with -O2 but not with -O0

2011-11-19 Thread Ralf Corsepius
On 11/19/2011 01:23 PM, Andrew Haley wrote:
> On 11/18/2011 11:32 PM, Tom Lane wrote:
>> Andrew Haley  writes:
 On 11/18/2011 05:53 PM, Ralf Corsepius wrote:
>> pptp.c:459:33: warning: dereferencing type-punned pointer might break
>> strict-aliasing rules [-Wstrict-aliasing]
 Bingo!  Bugs like this must be fixed.
>> Sometimes that's easier said than done.  -fno-strict-aliasing might be
>> your friend.
>
> It's always easier said than done!  Still, one could argue
> that -fno-strict-aliasing is a fix, kinda sorta.
It's a work-around to evaluate whether aliasing actucally is the cause 
of this BZ.

> My point is
> that you've got to do *something*; this warning must not be
> ignored.

The code in question is a classic of the GCC-aliasing cases:
sockaddr vs. sockaddr_{in,un,..} casts.

The standard work-around to the GCC warnings would be using unions, 
containing fields of these types. Whether these spots actually are 
affected by aliasing issues, is a different matter.

[I have seen cases of this sort, where aliasing actually had malicious 
effects, but I've also seen cases it didn't.]

Ralf
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

rawhide report: 20111119 changes

2011-11-19 Thread Rawhide Report
Compose started at Sat Nov 19 08:15:17 UTC 2011

Broken deps for x86_64
--
OpenGTL-0.9.15.1-3.fc17.x86_64 requires libLLVM-2.9.so()(64bit)
OpenGTL-devel-0.9.15.1-3.fc17.i686 requires libLLVM-2.9.so
OpenGTL-devel-0.9.15.1-3.fc17.x86_64 requires libLLVM-2.9.so()(64bit)
OpenGTL-libs-0.9.15.1-3.fc17.i686 requires libLLVM-2.9.so
OpenGTL-libs-0.9.15.1-3.fc17.x86_64 requires libLLVM-2.9.so()(64bit)
1:anerley-0.3.0-5.fc17.i686 requires libedataserver-1.2.so.15
1:anerley-0.3.0-5.fc17.i686 requires libcamel-1.2.so.29
1:anerley-0.3.0-5.fc17.x86_64 requires libedataserver-1.2.so.15()(64bit)
1:anerley-0.3.0-5.fc17.x86_64 requires libcamel-1.2.so.29()(64bit)
claws-mail-plugins-archive-3.7.10-7.fc17.x86_64 requires 
libarchive.so.2()(64bit)
comoonics-cdsl-py-0.2-18.noarch requires comoonics-base-py
comoonics-cluster-py-0.1-24.noarch requires comoonics-base-py
contextkit-0.5.15-2.fc15.i686 requires libcdb.so.1
contextkit-0.5.15-2.fc15.x86_64 requires libcdb.so.1()(64bit)
couchdb-1.0.3-2.fc16.x86_64 requires libicuuc.so.46()(64bit)
couchdb-1.0.3-2.fc16.x86_64 requires libicui18n.so.46()(64bit)
couchdb-1.0.3-2.fc16.x86_64 requires libicudata.so.46()(64bit)
curry-0.9.11-7.fc12.x86_64 requires libgmp.so.3()(64bit)
cvs2cl-2.73-1.fc17.noarch requires 
perl(CVS::Utils::ChangeLog::EntrySet::Output)
dh-make-0.55-3.fc15.noarch requires debhelper
dogtag-pki-9.0.0-8.fc17.noarch requires pki-console >= 0:9.0.5
ease-0.4-9.fc17.i686 requires libpoppler.so.18
ease-0.4-9.fc17.i686 requires libclutter-gtk-0.10.so.0
ease-0.4-9.fc17.i686 requires libarchive.so.2
ease-0.4-9.fc17.x86_64 requires libpoppler.so.18()(64bit)
ease-0.4-9.fc17.x86_64 requires libclutter-gtk-0.10.so.0()(64bit)
ease-0.4-9.fc17.x86_64 requires libarchive.so.2()(64bit)
ease-devel-0.4-9.fc17.i686 requires pkgconfig(clutter-gtk-0.10)
ease-devel-0.4-9.fc17.x86_64 requires pkgconfig(clutter-gtk-0.10)
emacs-spice-mode-1.2.25-6.fc17.noarch requires gwave
evolution-couchdb-0.5.91-4.fc17.x86_64 requires 
libedataserver-1.2.so.15()(64bit)
evolution-couchdb-0.5.91-4.fc17.x86_64 requires 
libedata-cal-1.2.so.13()(64bit)
evolution-couchdb-0.5.91-4.fc17.x86_64 requires 
libedata-book-1.2.so.11()(64bit)
evolution-couchdb-0.5.91-4.fc17.x86_64 requires 
libecal-1.2.so.10()(64bit)
evolution-couchdb-0.5.91-4.fc17.x86_64 requires 
libcamel-provider-1.2.so.29()(64bit)
evolution-couchdb-0.5.91-4.fc17.x86_64 requires 
libcamel-1.2.so.29()(64bit)
fldigi-3.21.7-1.fc16.x86_64 requires libfltk_images.so.1.1()(64bit)
fldigi-3.21.7-1.fc16.x86_64 requires libfltk.so.1.1()(64bit)
gcc-python2-debug-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17
gcc-python2-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17
gcc-python3-debug-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17
gcc-python3-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17
1:geda-gattrib-1.6.2-2.fc16.x86_64 requires libgmp.so.3()(64bit)
1:geda-gnetlist-1.6.2-2.fc16.x86_64 requires libgmp.so.3()(64bit)
1:geda-gschem-1.6.2-2.fc16.x86_64 requires libgmp.so.3()(64bit)
1:geda-gsymcheck-1.6.2-2.fc16.x86_64 requires libgmp.so.3()(64bit)
1:geda-utils-1.6.2-2.fc16.x86_64 requires libgmp.so.3()(64bit)
genius-1.0.12-2.fc15.x86_64 requires libgmp.so.3()(64bit)
gnome-do-plugins-banshee-0.8.4-2.fc16.x86_64 requires 
mono(Banshee.CollectionIndexer) = 0:2.0.0.0
gnome-genius-1.0.12-2.fc15.x86_64 requires libgmp.so.3()(64bit)
gnome-phone-manager-0.66-6.fc17.x86_64 requires 
libedataserver-1.2.so.15()(64bit)
gnome-phone-manager-0.66-6.fc17.x86_64 requires 
libcamel-1.2.so.29()(64bit)
gnome-phone-manager-telepathy-0.66-6.fc17.x86_64 requires 
libedataserver-1.2.so.15()(64bit)
gnome-phone-manager-telepathy-0.66-6.fc17.x86_64 requires 
libcamel-1.2.so.29()(64bit)
gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires 
libgpilotdconduit.so.3()(64bit)
gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires 
libgpilotdcm.so.4()(64bit)
gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires 
libgpilotd.so.5()(64bit)
gphpedit-0.9.95-0.2.20090209snap.fc15.x86_64 requires 
libgtkhtml-2.so.0()(64bit)
gpx-viewer-0.2.0-3.fc14.x86_64 requires libgdl-1.so.3()(64bit)
gpx-viewer-0.2.0-3.fc14.x86_64 requires 
libclutter-gtk-0.10.so.0()(64bit)
gpx-viewer-0.2.0-3.fc14.x86_64 requires 
libchamplain-gtk-0.6.so.0()(64bit)
gpx-viewer-0.2.0-3.fc14.x86_64 requires libchamplain-0.6.so.0()(64bit)
gscribble-0.1.2-1.fc16.noarch requires gnome-python2-gtkhtml2
gstreamer-java-swt-1.5-1.fc16.x86_64 requires libswt3-gtk2
  

Re: Package segfaults when built with -O2 but not with -O0

2011-11-19 Thread Andrew Haley
On 11/18/2011 11:32 PM, Tom Lane wrote:
> Andrew Haley  writes:
>> > On 11/18/2011 05:53 PM, Ralf Corsepius wrote:
>>> >> pptp.c:459:33: warning: dereferencing type-punned pointer might break 
>>> >> strict-aliasing rules [-Wstrict-aliasing]
>> > Bingo!  Bugs like this must be fixed.
> Sometimes that's easier said than done.  -fno-strict-aliasing might be
> your friend.

It's always easier said than done!  Still, one could argue
that -fno-strict-aliasing is a fix, kinda sorta.  My point is
that you've got to do *something*; this warning must not be
ignored.

Andrew.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel