Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

freebsd-gnome Digest, Vol 359, Issue 1

1 view

Skip to first unread message

freebsd-gn...@freebsd.org

unread,

Mar 8, 2010, 7:00:08 AM3/8/10

to freebs...@freebsd.org

Send freebsd-gnome mailing list submissions to
freebs...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
or, via email, send a message with subject or body 'help' to
freebsd-gn...@freebsd.org

You can reach the person managing the list at
freebsd-g...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-gnome digest..."

Today's Topics:

1. FreeBSD Gnome Installation Script (David Childers)
2. Re: FreeBSD Gnome Installation Script (Michal Varga)
3. Re: marcuscom and www/epiphany-extensions (Michal Varga)
4. Re: marcuscom and www/epiphany-extensions (Joe Marcus Clarke)
5. Re: hald vs dvd+rw (Joe Marcus Clarke)
6. Re: narrowed down troubles with devel/gobject-introspection
(Joe Marcus Clarke)
7. Re: [ports-...@FreeBSD.org: libgweather-2.28.0_1 failed
on sparc64 7] (Joe Marcus Clarke)
8. Re: narrowed down troubles with devel/gobject-introspection
(Mikhail T.)
9. Re: marcuscom and www/epiphany-extensions (Michal Varga)
10. Re: marcuscom and www/epiphany-extensions (Joe Marcus Clarke)
11. Re: hald vs dvd+rw (Andriy Gapon)
12. Current problem reports assigned to gn...@FreeBSD.org
(FreeBSD bugmaster)

----------------------------------------------------------------------

Message: 1
Date: Sun, 07 Mar 2010 13:53:05 -0600
From: David Childers <sa...@scvi.net>
Subject: FreeBSD Gnome Installation Script
To: freebs...@freebsd.org
Message-ID: <4B940421...@scvi.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Greetings,

I have created a installation script that will allow users to easily
install and configure the Gnome desktop on the FreeBSD platform.

You can view the documentation here:
www.scribd.com/doc/27366469/Gnome-Desktop-Installation-Script-For-FreeBSD

I am currently working on a hardening / lockdown script for Desktop
computers running FreeBSD.

Both scripts can be used on either i386 or amd64 platforms.

Any feed back would greatly be appreciated.

Dave

------------------------------

Message: 2
Date: Mon, 8 Mar 2010 01:48:23 +0100
From: Michal Varga <varga....@gmail.com>
Subject: Re: FreeBSD Gnome Installation Script
To: David Childers <sa...@scvi.net>
Cc: freebs...@freebsd.org
Message-ID:
<3f1fd1ea1003071648j37b...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Sun, Mar 7, 2010 at 20:53, David Childers <sa...@scvi.net> wrote:
> Greetings,
>
> I have created a installation script that will allow users to easily install
> and configure the Gnome desktop on the FreeBSD platform.
>
> You can view the documentation here:
> www.scribd.com/doc/27366469/Gnome-Desktop-Installation-Script-For-FreeBSD
>
> I am currently working on a hardening / lockdown script for Desktop
> computers running FreeBSD.
>
> Both scripts can be used on either i386 or amd64 platforms.
>
> Any feed back would greatly be appreciated.
>
OK, here is one:
"Hello, you have an old version of Adobe Flash Player. To use iPaper
(and lots of other stuff on the web) you need to get the latest Flash
player."
(in fact, I have none and I plan for it to stay that way)

Here is another one:
"Log in to Download This Document
email address or username
password
New to Scribd?
Sign Up for a free account today"

Is this some kind of joke by a chance?

------------------------------

Message: 3
Date: Mon, 8 Mar 2010 02:06:38 +0100
From: Michal Varga <varga....@gmail.com>
Subject: Re: marcuscom and www/epiphany-extensions
To: Koop Mast <k...@freebsd.org>
Cc: gn...@freebsd.org, Joe Marcus Clarke <mar...@freebsd.org>
Message-ID:
<3f1fd1ea1003071706i6f...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Fri, Mar 5, 2010 at 15:47, Koop Mast <k...@freebsd.org> wrote:
> Thanks for the work. I committed it to MC with some minor tweaks.
> About updating, we will pick it up when it get released. Or if a release
> of any gnome port goes unnoticed, feel free to poke any of us about it.
>
> -Koop
>
Thanks for taking care of it. By the way, about updating - some time
not so long ago, I remember Marcus asking for more user support, as
the FreeBSD Gnome team was supposedly stretchting pretty thin. If
that's not the case anymore, even better then, of course. I was just
under impression that there is probably not enough people to do all of
it, so taking care of few less-popular packages that I know I'm
actively using wouldn't be a bad thing.

------------------------------

Message: 4
Date: Sun, 07 Mar 2010 20:18:09 -0500
From: Joe Marcus Clarke <mar...@marcuscom.com>
Subject: Re: marcuscom and www/epiphany-extensions
To: Michal Varga <varga....@gmail.com>
Cc: gn...@freebsd.org, Koop Mast <k...@freebsd.org>
Message-ID: <1268011089.9...@shumai.marcuscom.com>
Content-Type: text/plain; charset="iso-8859-1"

On Mon, 2010-03-08 at 02:06 +0100, Michal Varga wrote:
> On Fri, Mar 5, 2010 at 15:47, Koop Mast <k...@freebsd.org> wrote:
> > Thanks for the work. I committed it to MC with some minor tweaks.
> > About updating, we will pick it up when it get released. Or if a release
> > of any gnome port goes unnoticed, feel free to poke any of us about it.
> >
> > -Koop
> >
> Thanks for taking care of it. By the way, about updating - some time
> not so long ago, I remember Marcus asking for more user support, as
> the FreeBSD Gnome team was supposedly stretchting pretty thin. If
> that's not the case anymore, even better then, of course. I was just
> under impression that there is probably not enough people to do all of
> it, so taking care of few less-popular packages that I know I'm
> actively using wouldn't be a bad thing.

We are spread thin, and we can always use help. The major work, though,
is typically with the first-time port or first-time minor version bump
update. After that, the micro revs are typically trivial.

But there are a lot of components to GNOME, and even bumping versions
and distinfos can get tiresome. GNOME 2.29.92 is imminent, so if you
want to jump in, and help with the updates, you are more than welcome to
do so.

Joe

--
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20100308/7ed9f10d/attachment-0001.pgp

------------------------------

Message: 5
Date: Sun, 07 Mar 2010 20:20:56 -0500
From: Joe Marcus Clarke <mar...@marcuscom.com>
Subject: Re: hald vs dvd+rw
To: Andriy Gapon <a...@icyb.net.ua>
Cc: gn...@freebsd.org
Message-ID: <1268011256.9...@shumai.marcuscom.com>
Content-Type: text/plain; charset="iso-8859-1"

On Thu, 2010-03-04 at 19:14 +0200, Andriy Gapon wrote:
> It seems that hald behavior might be causing some issues with re-writing DVD�RW
> media. I specifically mean the case when media already contains CD9660 or UDF
> filesystem and is being re-written with new data.
> It seems that when hald notices old volume going away, it attempts to re-taste the
> media while a burning program, e.g. growisofs, may be writing data to the media.
> At the very least it produces messages in system log like the following:
> kernel: (cd0:ahcich5:0:0:0): READ TOC/PMA/ATIP. CDB: 43 0 0 0 0 0 0 0 4 0
> kernel: (cd0:ahcich5:0:0:0): CAM status: SCSI Status Error
> kernel: (cd0:ahcich5:0:0:0): SCSI status: Check Condition
> kernel: (cd0:ahcich5:0:0:0): SCSI sense: NOT READY asc:4,8 (Logical unit not
> ready, long write in progress)
>
> At the worst, it causes confusion for the burning program.
> This happens with recent versions of 9-CURRENT and 8-STABLE, when using atacam and
> ahci driver for programs like growisofs from dvd+rw-tools and cdrecord from
> cdrecord-devel. And, of course, for frontends that use those as backends.
>
> I am not sure how to resolve this properly.
> Perhaps, hald could have a special treatment for 'Logical unit not ready, long
> write in progress' sense from TEST UNIT READY command.

Have you followed the steps at
http://www.freebsd.org/gnome/docs/halfaq.html#q6 to lock the device in
hal, and prevent access while burning your media?

Joe

------------------------------

Message: 6
Date: Sun, 07 Mar 2010 20:21:50 -0500
From: Joe Marcus Clarke <mar...@marcuscom.com>
Subject: Re: narrowed down troubles with devel/gobject-introspection
To: "Mikhail T." <mi+...@aldan.algebra.com>
Cc: gn...@freebsd.org, k...@freebsd.org, pyt...@freebsd.org
Message-ID: <1268011310.9...@shumai.marcuscom.com>
Content-Type: text/plain; charset="utf-8"

On Mon, 2010-03-01 at 22:54 -0500, Mikhail T. wrote:
> Ok, some Python script somewhere is trying to do chflags on a file under
> ~/.cache. On this system, my home directory is NFS-mounted and the
> chflags fails. This should not be a fatal error, but it is... CC-ing
> Python-maintainers... Yours,

The recommended workaround for gobject-introspection is to symlink
~/.cache/g-ir-scanner to /dev/null, or some locally mounted directory.

Joe

>
> -mi
>
> Mikhail T. написав(ла):
> > Building devel/gobject-introspection -- a requirement for various
> > things, including gstreamer and thus KDE4 -- fails here:
> >
> > /bin/sh /opt/bin/libtool --tag=CC --mode=link cc
> > -I/opt/include/glib-2.0 -I/opt/lib/glib-2.0/include -D_REENTRANT
> > -I/opt/include/glib-2.0 -I/opt/lib/glib-2.0/include -Wsign-compare
> > -Wcast-align -Wpointer-arith -Wnested-externs -Wmissing-prototypes
> > -Wmissing-declarations -Wchar-subscripts -Wall -O2 -pipe
> > -march=pentium4 -fno-strict-aliasing -avoid-version -L/opt/lib -o
> > libannotation.la -rpath /opt/unused annotation.lo -L/opt/lib
> > -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -pthread
> > -L/opt/lib -lgthread-2.0 -lglib-2.0
> > libtool: link: cc -shared .libs/annotation.o -Wl,-rpath
> > -Wl,/opt/lib -Wl,-rpath -Wl,/opt/lib -L/opt/lib
> > /opt/lib/libgio-2.0.so /opt/lib/libgobject-2.0.so
> > /opt/lib/libgmodule-2.0.so /opt/lib/libgthread-2.0.so -pthread
> > /opt/lib/libglib-2.0.so -licui18n /opt/lib/libintl.so
> > /opt/lib/libiconv.so /opt/lib/libpcre.so -march=pentium4 -pthread
> > -pthread -pthread -pthread -Wl,-soname -Wl,libannotation.so -o
> > .libs/libannotation.so
> > libtool: link: ar cru .libs/libannotation.a annotation.o
> > libtool: link: ranlib .libs/libannotation.a
> > libtool: link: ( cd ".libs" && rm -f "libannotation.la" && ln -s
> > "../libannotation.la" "libannotation.la" )
> > env LPATH=.libs env PYTHONPATH=../..:../..:YTHONPATH
> > UNINSTALLED_INTROSPECTION_SRCDIR=../..
> > UNINSTALLED_INTROSPECTION_BUILDDIR=../.. ../../tools/g-ir-scanner -v
> > --add-include-path=../../gir --add-include-path=. -v
> > --add-include-path=../../gir --add-include-path=.
> > --namespace=annotation --nsversion=1.0 --libtool="/bin/sh
> > /opt/bin/libtool" --library=libannotation.la --pkg=gobject-2.0
> > --include=GObject-2.0 --include=utility-1.0 ./annotation.c
> > ./annotation.h --output annotation-1.0.gir
> > Traceback (most recent call last):
> > File "../../tools/g-ir-scanner", line 38, in <module>
> > sys.exit(scanner_main(sys.argv))
> > File
> > "/home/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.7/giscanner/scannermain.py",
> > line 277, in scanner_main
> > transformer.register_include(include_obj)
> > File
> > "/home/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.7/giscanner/transformer.py",
> > line 112, in register_include
> > self._parse_include(filename)
> > File
> > "/home/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.7/giscanner/transformer.py",
> > line 137, in _parse_include
> > self._cachestore.store(filename, parser)
> > File
> > "/home/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.7/giscanner/cachestore.py",
> > line 112, in store
> > shutil.move(tmp_filename, store_filename)
> > File "/opt/lib/python2.6/shutil.py", line 264, in move
> > copy2(src, real_dst)
> > File "/opt/lib/python2.6/shutil.py", line 100, in copy2
> > copystat(src, dst)
> > File "/opt/lib/python2.6/shutil.py", line 77, in copystat
> > os.chflags(dst, st.st_flags)
> > OSError: [Errno 45] Operation not supported:
> > '/home/mi/.cache/g-ir-scanner/fc59b7fa095cd6403cb3917129208269cb202f6b'
> > gmake[3]: *** [annotation-1.0.gir] Error 1
> > gmake[3]: Leaving directory
> > `/home/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.7/tests/scanner'
> > gmake[2]: *** [all-recursive] Error 1
> > gmake[2]: Leaving directory
> > `/home/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.7/tests'
> > gmake[1]: *** [all-recursive] Error 1
> > gmake[1]: Leaving directory
> > `/home/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.7'
> > gmake: *** [all] Error 2
> > *** Error code 1
> >
> > Stop in /usr/ports/devel/gobject-introspection.
> > *** Error code 1
> >
> > Stop in /usr/ports/multimedia/gstreamer.
> > *** Error code 1
> >
> > Stop in /usr/ports/multimedia/gstreamer-plugins.
> > *** Error code 1
> >
> > Stop in /usr/ports/multimedia/qt4-phonon-gst.
> > *** Error code 1
> >
> > Stop in /usr/ports/www/qt4-webkit.
> > *** Error code 1
> >
> > Stop in /usr/ports/devel/qt4-assistant.
> > *** Error code 1
> >
> > Stop in /usr/ports/x11/kdelibs4.
> > *** Error code 1
> >
> > Stop in /usr/ports/x11/kdebase4.
> _______________________________________________
> freebs...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> To unsubscribe, send any mail to "freebsd-gnom...@freebsd.org"
>

------------------------------

Message: 7
Date: Sun, 07 Mar 2010 20:34:40 -0500
From: Joe Marcus Clarke <mar...@marcuscom.com>
Subject: Re: [ports-...@FreeBSD.org: libgweather-2.28.0_1 failed
on sparc64 7]
To: Mark Linimon <lin...@lonesome.com>
Cc: gn...@freebsd.org
Message-ID: <1268012080.9...@shumai.marcuscom.com>
Content-Type: text/plain; charset="iso-8859-1"

On Thu, 2010-02-25 at 00:23 -0600, Mark Linimon wrote:
> I'm trying to build sparc64-7 packages for release.
>
> This started failing on sparc64-7 on 2010-02-12. I don't even know what
> "error 137" is. Does anyone have any idea?
>

The kernel appears to be killing the process. This part of the build
can get quite CPU and memory intensive. Are there any errors in dmesg
which may give more of a clue as to why this is failing?

Joe

------------------------------

Message: 8
Date: Sun, 07 Mar 2010 21:07:52 -0500
From: "Mikhail T." <mi+...@aldan.algebra.com>
Subject: Re: narrowed down troubles with devel/gobject-introspection
To: Joe Marcus Clarke <mar...@marcuscom.com>
Cc: gn...@freebsd.org, k...@freebsd.org, pyt...@freebsd.org
Message-ID: <4B945BF8...@aldan.algebra.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 07.03.2010 20:21, Joe Marcus Clarke wrote:
> The recommended workaround for gobject-introspection is to symlink
> ~/.cache/g-ir-scanner to /dev/null, or some locally mounted directory.
>
Thanks, I built the port as `root', whose home is local. But, in
general, a build, that uses anything outside the ${WRKDIR} is buggy...
Perhaps, all that's needed is some env-variable? Yours,

-mi

------------------------------

Message: 9
Date: Mon, 8 Mar 2010 03:09:41 +0100
From: Michal Varga <varga....@gmail.com>
Subject: Re: marcuscom and www/epiphany-extensions
To: Joe Marcus Clarke <mar...@marcuscom.com>
Cc: gn...@freebsd.org, Koop Mast <k...@freebsd.org>
Message-ID:
<3f1fd1ea1003071809i4a...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Mon, Mar 8, 2010 at 02:18, Joe Marcus Clarke <mar...@marcuscom.com> wrote:
> We are spread thin, and we can always use help. The major work, though,
> is typically with the first-time port or first-time minor version bump
> update. After that, the micro revs are typically trivial.
>
> But there are a lot of components to GNOME, and even bumping versions
> and distinfos can get tiresome. GNOME 2.29.92 is imminent, so if you
> want to jump in, and help with the updates, you are more than welcome to
> do so.
>
> Joe
>
Yep, that's what I had in mind.

Are there any mechanisms in place to 'book' a particular set of
components that I'd plan to keep an eye on? To explain, there are two
particular issues that concern me.

First - I have, for example, no accessibility users (incl. myself), or
the whole tomboy/mono hilarity, or say, packagekit. While I probably
could blindly port the next release in queue, see if it builds, run
some plist checks, etc., I wouldn't be able to see if it actually
works, as in the best case scanario, I wouldn't have a clue about the
proper function of that component (so let's say, while I'm aware what
Orca is generally supposed to achieve, I have no idea about particular
details of a common accessibility users's setup and how he uses it. So
I might pretty much port a version that has "well, it seems to be able
to start" as the only working feature).

Second is the work duplication - obviously it doesn't to any good when
two people spent last few hours on a bunch of ports, then submit them
at about the same time, only to see that they both also duplicated
half of the work of each other (and I can only do that probably few
times a week, there are those usual "full time job / kids" issues). I
can imagine that especially first few days after a new Gnome release,
this would happen regularly without any "these ports are mine, don't
touch them" in place, so I presume there is something that deals with
it.

So that would be my question, how does one properly jump in without
running straight into those issues? I don't expect a badge and a
baseball cap, but I guess there is some kind of semi-internal memo
about proper work protocols that I should read before I start.

------------------------------

Message: 10
Date: Mon, 08 Mar 2010 00:44:50 -0500
From: Joe Marcus Clarke <mar...@marcuscom.com>
Subject: Re: marcuscom and www/epiphany-extensions
To: Michal Varga <varga....@gmail.com>
Cc: gn...@freebsd.org, Koop Mast <k...@freebsd.org>
Message-ID: <1268027090.9...@shumai.marcuscom.com>
Content-Type: text/plain; charset="iso-8859-1"

On Mon, 2010-03-08 at 03:09 +0100, Michal Varga wrote:
> On Mon, Mar 8, 2010 at 02:18, Joe Marcus Clarke <mar...@marcuscom.com> wrote:
> > We are spread thin, and we can always use help. The major work, though,
> > is typically with the first-time port or first-time minor version bump
> > update. After that, the micro revs are typically trivial.
> >
> > But there are a lot of components to GNOME, and even bumping versions
> > and distinfos can get tiresome. GNOME 2.29.92 is imminent, so if you
> > want to jump in, and help with the updates, you are more than welcome to
> > do so.
> >
> > Joe
> >
> Yep, that's what I had in mind.
>
> Are there any mechanisms in place to 'book' a particular set of
> components that I'd plan to keep an eye on? To explain, there are two
> particular issues that concern me.

Not really. We hang out on IRC (on #freebsd-gnome on Freenode).
Usually what happens is that someone will say, "hey, is anyone working
on X?" If not, then that person will take the port. I typically
monitor ftp-release-list on http://lists.gnome.org, and work my way down
the list.

>
> First - I have, for example, no accessibility users (incl. myself), or
> the whole tomboy/mono hilarity, or say, packagekit. While I probably
> could blindly port the next release in queue, see if it builds, run
> some plist checks, etc., I wouldn't be able to see if it actually
> works, as in the best case scanario, I wouldn't have a clue about the
> proper function of that component (so let's say, while I'm aware what
> Orca is generally supposed to achieve, I have no idea about particular
> details of a common accessibility users's setup and how he uses it. So
> I might pretty much port a version that has "well, it seems to be able
> to start" as the only working feature).

We operate in the same manner. While some of us can test certain ports,
we can't test them all. We do basic sanity checks, and rely on our
users who may be more familiar with how the ports should work to alert
us to problems.

>
> Second is the work duplication - obviously it doesn't to any good when
> two people spent last few hours on a bunch of ports, then submit them
> at about the same time, only to see that they both also duplicated
> half of the work of each other (and I can only do that probably few
> times a week, there are those usual "full time job / kids" issues). I
> can imagine that especially first few days after a new Gnome release,
> this would happen regularly without any "these ports are mine, don't
> touch them" in place, so I presume there is something that deals with
> it.

IRC is probably the best.

Joe

------------------------------

Message: 11
Date: Mon, 08 Mar 2010 10:36:15 +0200
From: Andriy Gapon <a...@icyb.net.ua>
Subject: Re: hald vs dvd+rw
To: Joe Marcus Clarke <mar...@marcuscom.com>
Cc: gn...@freebsd.org
Message-ID: <4B94B6FF...@icyb.net.ua>
Content-Type: text/plain; charset=ISO-8859-1

on 08/03/2010 03:20 Joe Marcus Clarke said the following:
> On Thu, 2010-03-04 at 19:14 +0200, Andriy Gapon wrote:
>> It seems that hald behavior might be causing some issues with re-writing DVD�RW
>> media. I specifically mean the case when media already contains CD9660 or UDF
>> filesystem and is being re-written with new data.
>> It seems that when hald notices old volume going away, it attempts to re-taste the
>> media while a burning program, e.g. growisofs, may be writing data to the media.
>> At the very least it produces messages in system log like the following:
>> kernel: (cd0:ahcich5:0:0:0): READ TOC/PMA/ATIP. CDB: 43 0 0 0 0 0 0 0 4 0
>> kernel: (cd0:ahcich5:0:0:0): CAM status: SCSI Status Error
>> kernel: (cd0:ahcich5:0:0:0): SCSI status: Check Condition
>> kernel: (cd0:ahcich5:0:0:0): SCSI sense: NOT READY asc:4,8 (Logical unit not
>> ready, long write in progress)
>>
>> At the worst, it causes confusion for the burning program.
>> This happens with recent versions of 9-CURRENT and 8-STABLE, when using atacam and
>> ahci driver for programs like growisofs from dvd+rw-tools and cdrecord from
>> cdrecord-devel. And, of course, for frontends that use those as backends.
>>
>> I am not sure how to resolve this properly.
>> Perhaps, hald could have a special treatment for 'Logical unit not ready, long
>> write in progress' sense from TEST UNIT READY command.
>
> Have you followed the steps at
> http://www.freebsd.org/gnome/docs/halfaq.html#q6 to lock the device in
> hal, and prevent access while burning your media?

No, I haven't. Thank you for the information!
OTOH, I tried burning with k3b (from k3b-kde4), which is supposed to be smart
about hal, but got exactly the same issue.

--
Andriy Gapon

------------------------------

Message: 12
Date: Mon, 8 Mar 2010 11:07:22 GMT
From: FreeBSD bugmaster <bugm...@FreeBSD.org>
Subject: Current problem reports assigned to gn...@FreeBSD.org
To: gn...@FreeBSD.org
Message-ID: <201003081107....@freefall.freebsd.org>

Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker Resp. Description
--------------------------------------------------------------------------------
o ports/144457 gnome print/system-config-printer does not compile due to in
o ports/144352 gnome [patch] sysutils/hal: UFS disks remount immediately af
p ports/143852 gnome port devel/seed fails because freshly built seed segfa
o ports/143260 gnome devel/gobject-introspection writes files in $HOME
o ports/142903 gnome graphics/inkscape hangs for an infinite loop when open
o ports/142549 gnome sysutils/hal: hald cannot find DVD/CS anymore
o ports/141397 gnome x11/gnome2: gnome desktop prevents umount without '-f'
s ports/141162 gnome x11-toolkits/pango 1.26 introduces crashes with epipha
s ports/141033 gnome [PATCH] allow to build devel/libsoup without gnome
o ports/140533 gnome bsd.gnome.mk - mtree may get parameters w/o space
o ports/140216 gnome [patch] devel/nspr does not check POLLHUP in PR_Connec
s ports/137367 gnome net/libproxy: add menu option to configure dependence
a ports/134361 gnome devel/gvfs ports with smbclient support doesn't pass a
o ports/132304 gnome ports/devel/dbus misses /var/db/dbus/machine-id in dis
o ports/128810 gnome AMD 64 port installation not working on textproc/libxm

15 problems total.

------------------------------

End of freebsd-gnome Digest, Vol 359, Issue 1
*********************************************

0 new messages