Re: MP3 licensing over - can we remove LAME restrictions?

[Mathias Picker]

Am Freitag, den 19.05.2017, 13:29 +0200 schrieb Alexander Leidinger:
> Quoting Matthieu Volat <ma...@alkumuna.eu> (from Tue, 16 May 2017  
> 17:31:39 +0200):
> 
> > 
> > On Tue, 16 May 2017 14:44:52 +
> > Ben Woods <woods...@gmail.com> wrote:
> > 
> > > 
> > > On Tue, 9 May 2017 at 1:07 pm, Koichiro IWAO <m...@vmeta.jp>
> > > wrote:
> > > 
> > > > 
> > > > Hi,
> > > > 
> > > > FYI, MP3 is coming back to Fedora. I think FreeBSD may able to
> > > > do that.
> > > > https://fedoramagazine.org/full-mp3-support-coming-soon-to-fedo
> > > > ra/
> > > > 
> > > If this analysis is correct, it sounds like the final patents
> > > will expire
> > > by the end of this year?
> > > 
> > > http://www.tunequest.org/a-big-list-of-mp3-patents/20070226/
> 
> > 
> > https://www.iis.fraunhofer.de/en/ff/amm/prod/audiocodec/audiocodecs
> > /mp3.html
> > 
> > That should be it? Now we can wait for aac, h264, h265 ;)
> 
> See the comment in the LAME port next to the RESTRICTED line.
> 
> Bye,
> Alexander.
> 

I *love* this kind of thoroughness!

:) Mathias

-- 
Mathias Picker
Geschäftsführer
mathias.pic...@virtual-earth.de

virtual earth Gesellschaft für Wissens re/prä sentation mbH
http://www.virtual-earth.de/   HRB126870
supp...@virtual-earth.de   Westendstr. 142
089 / 1250 3943    80339 München

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Zimbra Port

[Mathias Picker]

Am 1. Juni 2016 16:19:56 MESZ, schrieb Jim Ohlstein :
>Sorry for the top post. 
>
>We use Zimbra on an Ubuntu LTS VM with storage via iSCSI. 
>
>Given the magnitude, I honestly don't think ports or packages is really
>the way to go. I believe that most people use a dedicated (to Zimbra)
>server or VM. 

I second this.

There allready is a version of zimbra on FreeBSD and it's intentionally not a 
real port https://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD

I used to use this, but I'm now running a CentOS instance just for zimbra.

And I don't think zimbra outside of /opt is ever going to happen, it's coded 
into too many places.

You might want to rethink this…

Cheers, Mathias
>
>If I were to approach this project, I'd do it outside of ports, maybe
>on github, or possibly as a VM image. 
>
>That's not to say it can't be done, rather that a project of this size
>requires a layout that is not native to FreeBSD ports, and it's so
>massive with so many moving parts, having to comply with the ports
>infrastructure, and to maintain it, is probably far more effort than
>it's worth. 
>
>Jim Ohlstein
>> On Jun 1, 2016, at 9:47 AM, rs  wrote:
>> 
>> Hello List,
>> 
>> I am trying to create a port of the zimbra collaboration suite. I am
>in contact with upstream and they are actively helping in making a port
>happen.
>> 
>> It would be my first FreeBSD port (although I have a lot of linux
>knowledge and know how to create packages for .deb).
>> 
>> My first steps involve right now making everything compile (Zimbra
>includes *a lot* of libraries themselves instead of relying on the OS
>to provide them).
>> 
>> I have a couple of questions though:
>> 
>> * Zimbra expects itself to be installed to /opt/zimbra. It is not
>easy to change that, /opt/zimbra is hardcoded in a lot of places. Its a
>longterm goal of mine to help clean that up, but it is not possible
>right now. Are there any problems with a package which installs to
>/opt?
>> 
>> * The Zimbra source is huge, a git clone is about 13 GigaBytes. I am
>not sure on how source that big is handled correctly in ports. (e.g. is
>it OK that every make does a git clone and you have to wait until you
>get the 13 GB of data? Would this be a problem for the FreeBSD build
>cluster infrastructure to create the packages?, ...)
>> 
>> * On the porters handbook it says to fetch a tarball from http/ftp,
>is it also possible to directly work with git and clone a repository?
>> 
>> This is the right place to get help started in porting? FreeBSD has
>so much mailing lists :-)
>> 
>> Thank you,
>> Best
>> RAy
>> ___
>> freebsd-ports@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to
>"freebsd-ports-unsubscr...@freebsd.org"
>___
>freebsd-ports@freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-ports
>To unsubscribe, send any mail to
>"freebsd-ports-unsubscr...@freebsd.org"

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

synth just deleted 290 ports on my machine on second try ;)

[Mathias Picker]

Very funny, for a system that advertises as "just install and run".

What happened: I installed synth (out of curiosity) and did a sudo
synth upgrade-system on my FreeBSD 10.2-RELEASE-p9 system a few days
ago. Synth then build aboout 800 packages, then deleted many of them
again (???) citing a "failed dependency check", then installed a few
updated ones.

I started synth again yesterday to see if it was just something strange
in ports the first time, and it was allmost the same, building about
800 packages, deleting many of them, only now synth then had pkg delete
a few hundred installed packages on my machine. WTF? I mean, deleting
kdelibs and evolution is not a nice action.

The system was mostly using the FreeBSD repository before. I only build
password-store, blender and apache24 from ports, all because of some
non-standard settings. 

Any tips on what to do now? Trying to reinstall evolution makes pkg
want to downgrade itself (1.6.4 to 1.6.2, which doesn't really work all
that well, it goes into and endless loop after pkg 1.6.2 is installed.
I've fixed this, but I guess the same will happen when I try to install
kde via pkg.

What can I do now, other than using portmaster to rebuild all ports?

Thanks, Mathias

P.S.: synth logs, terminal output and pkg info are at http://virtual
-earth.de/synth-logs.txz
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Removing documentation

[Mathias Picker]

Am Montag, den 08.02.2016, 08:35 +0100 schrieb John Marino:
> On 2/8/2016 7:43 AM, Peter Jeremy wrote:

> On 2016-Feb-07 15:28:56 +0100, John Marino 
> wrote:
> > > Please do an honest "fly-off" between ports-mgmt/portmaster and
> > > ports-mgmt/synth.  I would love to hear what signficant thing
> > > portmaster
> > > can do that Synth can't.  (honestly)
> 

While I like the ideas of synth, and hoped I could use it to just build
my 3-8 ports with modified options, on first look I found many things
suggesting that it's not yet ready:

- shows uninteresting eye candy instead of build
- stops at every conf file version mismatch requiring me to start make
config by hand, and then to re-run when it discovers the next mismatch.
I mean, WTF?
- using prebuild packages requires fetching and installing them all
into the local repository? pkg can use multiple repositories with
different priorities, so this seems to clutter my system unnecessarily.
- building blender rebuilds audio/jack every time???
- after building blender successfully, ignores (deletes?) the package
with the cryptic error msg:  
- wants to build > 100 ports on my system, whereas portmaster -a just
build 31 ports.
-  

If I could just rebuild blender, apache, password store with my local
options and install them into a local repository, that would be nice
indeed, saving me from installing poudriere for this minor task.

And I don't mind the ncurses dependency one bit...

To comment on the original bug report: removing portmaster from
documentation seems to be a bit premature. It's working fine for me,
and it seems quite a lot simpler to me than synth, which makes it
preferable in my book.

Thinking about it, I'm not even sure the clean room build aproach of
synth is actually preferable to portmaster, the messy portmaster
aproach will pick up any messy thing (e.g. library) I did to my system,
which might be exactly what I want. Have to think about this some
more...


Cheers, Mathias

> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "
> freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: PHP7 package?

[Mathias Picker]

Am 7. Februar 2016 17:19:05 MEZ, schrieb Dan Busarow :
>On 2/7/16 9:06 AM, Kurt Jaeger wrote:
>> Hi!
>> 
>>> What I'm looking for is a package version so that in the future I
>can run
>>>
>>>  pkg upgrade
>>> or
>>>  pkg upgrade php7x
>> 
>> If you clone the repo from miwi, use it to build your own pkg repo,
>> you can use pkg upgrade to install those packages.
>> 
>> That's how I did it my testbox. If you need more details on how to do
>it,
>> I can add a few more details.
>
>More details would be great.  I've never built my own repo

You might try ports-mgmt/synth, a new tool intending to replace 
portmaster/portsupgrade.

synth builds and installs packages into a local pkg repository before upgrading 
the system. The simplest option I know of.

I've never used it, but I'm contemplating trying it out…

/ Mathias
>
>Thanks,
>Dan
>
>ll___
>freebsd-ports@freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-ports
>To unsubscribe, send any mail to
>"freebsd-ports-unsubscr...@freebsd.org"

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [CFT] SSP Package Repository available

[Mathias Picker]

On Mi, 2014-08-20 at 11:34 -0500, Bryan Drewery wrote:
 On 9/21/2013 5:49 AM, Bryan Drewery wrote:
  Ports now support enabling Stack Protector [1] support on FreeBSD 10
  i386 and amd64, and older releases on amd64 only currently.
  
  Support may be added for earlier i386 releases once all ports properly
  respect LDFLAGS.
  
  To enable, just add WITH_SSP=yes to your make.conf and rebuild all ports.
  
  The default SSP_CLFAGS is -fstack-protector, but -fstack-protector-all
  may optionally be set instead.
  
  Please help test this on your system. We would like to eventually enable
  this by default, but need to identify any major ports that have run-time
  issues due to it.
  
  [1] https://en.wikipedia.org/wiki/Buffer_overflow_protection
  
 
 We have not had any feedback on this yet and want to get it enabled by
 default for ports and packages.
 
 We now have a repository that you can use rather than the default to
 help test. We need your help to identify any issues before switching the
 default.
 
 This repository is available for:
 
 head
 10.0
 9.1,9.2,9.3
 
 It is not available for 8.4. If someone is willing to test on 8.4 I will
 build a repository for it.
 
 Place this in /usr/local/etc/pkgs/repos/FreeBSD_ssp.conf:
 
 FreeBSD: { enabled: no }
 FreeBSD_ssp: {
   url: pkg+http://pkg.FreeBSD.org/${ABI}/ssp;,
   mirror_type: srv,
   signature_type: fingerprints,
   fingerprints: /usr/share/keys/pkg,
   enabled: yes
 }
 
 Once that is done you should force reinstall packages from this repository:
 
   pkg update
   pkg upgrade -f

This wants me to downgrade pkg to 1.2.7, so I didn't try...

Cheers, Mathias
 
 Thanks for your help!
 Bryan Drewery
 On behalf of portmgr.
 



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Rawtherapee does not start on 10-STABLE

[Mathias Picker]

Hi,

I just tried to build RawTherapee and it dumps core with

Terminating due to uncaught exception 0x8109ae740 of type
Glib::ConvertError

I then 

- rebuild world from today, 
- switched off the collation fix in glib and optimizations in 
  rawtherapee
- did a portsnap fetch update and 
- rebuild glib, glibmm and rawtherapee with debug symbols, 
- deleted .config/RawTherapee*
- unset LANG and LC_ALL

and got the following stack trace:

(gdb) run
Starting program: /usr/local/bin/rawtherapee 
[New LWP 100486]
[New Thread 80f006400 (LWP 100486)]
Terminating due to uncaught exception 0x810275980 of type Glib::ConvertError

Program received signal SIGABRT, Aborted.
[Switching to Thread 80f006400 (LWP 100486)]
0x000808d5a2ca in thr_kill () from /lib/libc.so.7
(gdb) bt
#0  0x000808d5a2ca in thr_kill () from /lib/libc.so.7
#1  0x000808e21b39 in abort () from /lib/libc.so.7
#2  0x0008086aa7da in ?? () from /lib/libcxxrt.so.1
#3  0x00080242803b in Glib::ConvertError::throw_func (gobject=0x8102822c0)
at convert.cc:322
#4  0x000802458cff in Glib::Error::throw_exception (gobject=0x8102822c0)
at error.cc:167
#5  0x00080247cf0a in Glib::operator (os=..., utf8_string=...)
at ustring.cc:1401
#6  0x00652687 in Glib::ustring::FormatStream::streamGlib::ustring (
this=0x7fffb7e0, value=...)
at /usr/local/include/glibmm-2.4/glibmm/ustring.h:1057
#7  0x00652105 in Glib::ustring::formatGlib::ustring, char [9] 
(a1=..., 
a2=...) at /usr/local/include/glibmm-2.4/glibmm/ustring.h:1145
#8  0x0064f138 in RTImage::setPaths (opt=...)
at 
/usr/ports/graphics/rawtherapee/work/rawtherapee-4.0.12/rtgui/rtimage.cc:101
#9  0x0069944f in main (argc=1, argv=0x7fffd3d8)
at /usr/ports/graphics/rawtherapee/work/rawtherapee-4.0.12/rtgui/main.cc:239

I'm a bit out of my depth here, I'm more a dynamic language type...

Any ideas where I should look?

My system is a mobile phenom laptop with ati graphics, running 
FreeBSD marcopolo 10.0-STABLE FreeBSD 10.0-STABLE #14 r261827: Thu Feb 13 
13:13:01 CET 2014 mathiasp@marcopolo:/usr/obj/usr/src/sys/GENERIC  amd64
and KDE4 as desktop enviroment. Ah, and I unset LC_ALL before running 
rawtherapee...

Thanks,

Mathias



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

rubygem-bundler trouble on 10-stable

[Mathias Picker]

Hi all,

I'm trying to get middleman up and running on a freshly installed
10-stable machine.
I installed kde4, which pulled in ruby 1.9.3. I then installed the
system rubygems and bundler. 

Finally I checked out a project that worked fine on 9-stable, also with
ruby 1.9, and I get:

marcopolo% bundle install
Fetching gem metadata from https://rubygems.org/...
Fetching gem metadata from https://rubygems.org/..
Using RedCloth (4.2.9) 
Using i18n (0.6.5) 

Gem::Exception: Cannot load gem at
[/usr/local/lib/ruby/gems/2.0/cache/multi_json-1.8.2.gem]
in /usr/home/mathiasp/Projekte/Omanimali/omanimali-web
An error occurred while installing multi_json (1.8.2), and Bundler
cannot continue.
Make sure that `gem install multi_json -v '1.8.2'` succeeds before
bundling.

?? This is not what I expect. Trying bundler --path ~/.gem made the
bundle, but the ffi (1.9.3) bombed on 10-stable with 

library.rb:123:in `block in ffi_lib': Could not open library
'libc.so': /usr/lib/libc.so: invalid file format (LoadError)

:(

In 9-stable bundler would use all systems libs and then ask for my
password to install all other gems. I can find no reason why it changed
its behaviour. 

For testing purposes, I upgraded ruby and all gems to ruby 2.0, and then
I created a fresh user to try this with a fresh home directory. Both
show the exact same error msg.


Any idea? I really need to to get this running -  my 9-stable disk died
2 days after I got BETA3 installed, I guess it was miffed at being
replaced...


Thanks for any help, tips, debugging directions,

Mathias

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: rubygem-bundler trouble on 10-stable

[Mathias Picker]

On Thu, 2013-11-14 at 18:05 +0100, Mathias Picker wrote:
 Hi all,
 
 I'm trying to get middleman up and running on a freshly installed
 10-stable machine.
 I installed kde4, which pulled in ruby 1.9.3. I then installed the
 system rubygems and bundler. 
 
 Finally I checked out a project that worked fine on 9-stable, also with
 ruby 1.9, and I get:
 
 marcopolo% bundle install
 Fetching gem metadata from https://rubygems.org/...
 Fetching gem metadata from https://rubygems.org/..
 Using RedCloth (4.2.9) 
 Using i18n (0.6.5) 
 
 Gem::Exception: Cannot load gem at
 [/usr/local/lib/ruby/gems/2.0/cache/multi_json-1.8.2.gem]
 in /usr/home/mathiasp/Projekte/Omanimali/omanimali-web
 An error occurred while installing multi_json (1.8.2), and Bundler
 cannot continue.
 Make sure that `gem install multi_json -v '1.8.2'` succeeds before
 bundling.
 
 ?? This is not what I expect. Trying bundler --path ~/.gem made the
 bundle, but the ffi (1.9.3) bombed on 10-stable with 
 
 library.rb:123:in `block in ffi_lib': Could not open library
 'libc.so': /usr/lib/libc.so: invalid file format (LoadError)
 
 :(
 
 In 9-stable bundler would use all systems libs and then ask for my
 password to install all other gems. I can find no reason why it changed
 its behaviour. 
 
 For testing purposes, I upgraded ruby and all gems to ruby 2.0, and then
 I created a fresh user to try this with a fresh home directory. Both
 show the exact same error msg.
 
 
 Any idea? I really need to to get this running -  my 9-stable disk died
 2 days after I got BETA3 installed, I guess it was miffed at being
 replaced...
 

Silly me, I forgot to add any info ;)

marcopolo% uname -a
FreeBSD marcopolo.fritz.box 10.0-BETA3 FreeBSD 10.0-BETA3 #1 r258128M:
Thu Nov 14 12:53:53 CET 2013
mathi...@marcopolo.fritz.box:/usr/obj/usr/src/sys/GENERIC  amd64

marcopolo% pkg info|grep ruby
plasma-scriptengine-ruby-4.10.5_1 Plasma scriptengine for Ruby
rbenv-0.4.0_2  Manage multiple versions of ruby
ruby-2.0.0.195_1,1 An object-oriented interpreted scripting
language
ruby20-gems-1.8.25 Package management framework for the Ruby
language
ruby20-korundum-4.10.5_1   Ruby bindings for KDE
ruby20-qtruby-4.10.5   Ruby bindings for Qt
rubygem-bundler-1.3.5  A tool that manages gem dependencies for
ruby applications
rubygem-chunky_png-1.2.8   Ruby library to read and write PNG images
rubygem-compass-0.12.2 Provides an open-source CSS authoring
framework
rubygem-ffi-1.9.0  Extension for dynamic libraries  binding
functions
rubygem-fssm-0.2.10Provides a state tracking and event
firing utility
rubygem-i18n-0.6.5,2   New wave Internationalization support for
Ruby
rubygem-redcloth-4.2.9 A module for using Textile in Ruby
rubygem-sass-3.2.9 Sass is an extension of CSS3

marcopolo% ruby -v
ruby 2.0.0p195 (2013-05-14 revision 40734) [amd64-freebsd10]
marcopolo% gem -v
1.8.25
marcopolo% bundle -v
Bundler version 1.3.5

marcopolo% gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.8.25
  - RUBY VERSION: 2.0.0 (2013-05-14 patchlevel 195) [amd64-freebsd10]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/2.0
  - RUBY EXECUTABLE: /usr/local/bin/ruby20
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
- ruby
- amd64-freebsd-10
  - GEM PATHS:
 - /usr/local/lib/ruby/gems/2.0
 - /home/mathiasp/.gem/ruby/2.0
  - GEM CONFIGURATION:
 - :update_sources = true
 - :verbose = true
 - :benchmark = false
 - :backtrace = false
 - :bulk_threshold = 1000
  - REMOTE SOURCES:
 - http://rubygems.org/

And updating to a current rubygems didn't work either... 

 
 Thanks for any help, tips, debugging directions,
 
 Mathias
 
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Sorry, my bad (Was: Re: rubygem-bundler trouble on 10-stable)

[Mathias Picker]

:( I needed to install sudo :(

Cheers, Mathias

On Thu, 2013-11-14 at 18:09 +0100, Mathias Picker wrote:
 On Thu, 2013-11-14 at 18:05 +0100, Mathias Picker wrote:
  Hi all,
  
  I'm trying to get middleman up and running on a freshly installed
  10-stable machine.
  I installed kde4, which pulled in ruby 1.9.3. I then installed the
  system rubygems and bundler. 
  
  Finally I checked out a project that worked fine on 9-stable, also with
  ruby 1.9, and I get:
  
  marcopolo% bundle install
  Fetching gem metadata from https://rubygems.org/...
  Fetching gem metadata from https://rubygems.org/..
  Using RedCloth (4.2.9) 
  Using i18n (0.6.5) 
  
  Gem::Exception: Cannot load gem at
  [/usr/local/lib/ruby/gems/2.0/cache/multi_json-1.8.2.gem]
  in /usr/home/mathiasp/Projekte/Omanimali/omanimali-web
  An error occurred while installing multi_json (1.8.2), and Bundler
  cannot continue.
  Make sure that `gem install multi_json -v '1.8.2'` succeeds before
  bundling.
  
  ?? This is not what I expect. Trying bundler --path ~/.gem made the
  bundle, but the ffi (1.9.3) bombed on 10-stable with 
  
  library.rb:123:in `block in ffi_lib': Could not open library
  'libc.so': /usr/lib/libc.so: invalid file format (LoadError)
  
  :(
  
  In 9-stable bundler would use all systems libs and then ask for my
  password to install all other gems. I can find no reason why it changed
  its behaviour. 
  
  For testing purposes, I upgraded ruby and all gems to ruby 2.0, and then
  I created a fresh user to try this with a fresh home directory. Both
  show the exact same error msg.
  
  
  Any idea? I really need to to get this running -  my 9-stable disk died
  2 days after I got BETA3 installed, I guess it was miffed at being
  replaced...
  
 
 Silly me, I forgot to add any info ;)
 
 marcopolo% uname -a
 FreeBSD marcopolo.fritz.box 10.0-BETA3 FreeBSD 10.0-BETA3 #1 r258128M:
 Thu Nov 14 12:53:53 CET 2013
 mathi...@marcopolo.fritz.box:/usr/obj/usr/src/sys/GENERIC  amd64
 
 marcopolo% pkg info|grep ruby
 plasma-scriptengine-ruby-4.10.5_1 Plasma scriptengine for Ruby
 rbenv-0.4.0_2  Manage multiple versions of ruby
 ruby-2.0.0.195_1,1 An object-oriented interpreted scripting
 language
 ruby20-gems-1.8.25 Package management framework for the Ruby
 language
 ruby20-korundum-4.10.5_1   Ruby bindings for KDE
 ruby20-qtruby-4.10.5   Ruby bindings for Qt
 rubygem-bundler-1.3.5  A tool that manages gem dependencies for
 ruby applications
 rubygem-chunky_png-1.2.8   Ruby library to read and write PNG images
 rubygem-compass-0.12.2 Provides an open-source CSS authoring
 framework
 rubygem-ffi-1.9.0  Extension for dynamic libraries  binding
 functions
 rubygem-fssm-0.2.10Provides a state tracking and event
 firing utility
 rubygem-i18n-0.6.5,2   New wave Internationalization support for
 Ruby
 rubygem-redcloth-4.2.9 A module for using Textile in Ruby
 rubygem-sass-3.2.9 Sass is an extension of CSS3
 
 marcopolo% ruby -v
 ruby 2.0.0p195 (2013-05-14 revision 40734) [amd64-freebsd10]
 marcopolo% gem -v
 1.8.25
 marcopolo% bundle -v
 Bundler version 1.3.5
 
 marcopolo% gem env
 RubyGems Environment:
   - RUBYGEMS VERSION: 1.8.25
   - RUBY VERSION: 2.0.0 (2013-05-14 patchlevel 195) [amd64-freebsd10]
   - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/2.0
   - RUBY EXECUTABLE: /usr/local/bin/ruby20
   - EXECUTABLE DIRECTORY: /usr/local/bin
   - RUBYGEMS PLATFORMS:
 - ruby
 - amd64-freebsd-10
   - GEM PATHS:
  - /usr/local/lib/ruby/gems/2.0
  - /home/mathiasp/.gem/ruby/2.0
   - GEM CONFIGURATION:
  - :update_sources = true
  - :verbose = true
  - :benchmark = false
  - :backtrace = false
  - :bulk_threshold = 1000
   - REMOTE SOURCES:
  - http://rubygems.org/
 
 And updating to a current rubygems didn't work either... 
 
  
  Thanks for any help, tips, debugging directions,
  
  Mathias
  
  ___
  freebsd-ports@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-ports
  To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
 


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Update fails for kactivitymanagerd-4.10.5_1

[Mathias Picker]

Am Dienstag, den 15.10.2013, 13:57 +0200 schrieb Alberto Villa:
 On Tue, Oct 15, 2013 at 1:43 PM, Baptiste Daroussin b...@freebsd.org wrote:
  We have to limit the number of compilers we do support, and given the 
  different
  possible options people can have: CLANG_IS_CC WITHOUT_CLANG WITHOUT_GCC it 
  would
  be a nightmare to support all combinaison.
 
 Actually I was discussing another issue, that is: lang/clang33 doesn't
 provide c++11 features, according to the attached log. I'll try
 changing it to c++11-lib and see what happens, but I think c++11-lang
 should be enough. Am i wrong?

I just stumbled about this, and c++11-lib solved it for me.

Thanks, Mathias


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: [HEADSUP] Staging, packaging and more

[Mathias Picker]

Pascal Schmid pas...@lechindianer.de schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/06/2013 07:21 PM, Bernhard Fröhlich wrote:
 On Sun, Oct 6, 2013 at 2:20 PM, Ulrich Spörlein u...@freebsd.org
wrote:
 2013/10/4 Bryan Drewery br...@shatow.net:
 On Fri, Oct 04, 2013 at 09:01:58AM +0200, Baptiste Daroussin wrote:
 On Fri, Oct 04, 2013 at 08:57:53AM +0200, Erwin Lansing wrote:
 On Fri, Oct 04, 2013 at 08:32:59AM +0200, Baptiste Daroussin
wrote:
 
 Please no devel packages.
 
 Seconded.
 
 What's wrong with devel packages?
 
 It complicates things for developers and custom software on
FreeBSD. The typical
 situation that I see on most Linux platforms is a lot of
confusion by people, why
 their custom software XYZ does not properly build - the most
common answer: they
 forgot to install a tremendous amount of dev packages,
containing headers, build
 tools and whatnot. On FreeBSD, you can rely on the fact that if
you installed e.g.
 libGL, you can start building your own GL applications without
the need to install
 several libGL-dev, libX11-dev, ... packages first. This is
something, which I
 personally see as a big plus of the FreeBSD ports system and
which makes FreeBSD
 attractive as a development platform.
 
 
 On the other ends, that makes the package fat for embedded
systems, that also makes
 some arbitrary runtime conflicts between packages (because they
both provide the same
 symlink on the .so, while we could live with 2 version at
runtime), that leads to
 tons of potential issue while building locally, and that makes
having sometime insane
 issues with dependency tracking. Why having .a, .la, .h etc in
production servers? It
 could greatly reduce PBI size, etc.
 
 Personnaly I do have no strong opinion in one or another
direction. Should we be 
 nicer with developers? with end users? with embedded world? That
is the question to
 face to decide if -devel packages is where we want to go or not.
 
 
 If we chose to go down that path, at least we should chose a
different name as we've
 used the -devel suffix for many years for developmental versions.
 
 I must agree that it is one of the things high on my list of
things that irritate me
 with several Linux distributions but I can see the point for for
embedded systems as
 well.  But can't we have both?  Create three packages, a default
full package and split
 packages of -bin, -lib, and even -doc.  My first though twas to
make the full package
 a meta-package that would install the split packages in the
background, but that would
 probably be confusing for users at the end of the day, so rather
just have it be a real
 package.
 
 I do like that idea very much, and it is easily doable with stage
:)
 
 +1 to splitting packages for embedded usage.
 
 -1 for the split, as it will not fix anybody's problem.
 
 On regular machines, disk space is cheap and having to install more
packages is just annoying
 to users. Think of the time wasted that people are told to apt-get
libfoo-dev before they can
 build anything from github, or similar.
 
 If you actually *are* space constricted on your tiny embedded
machine, what the fuck are you
 doing with the sqlite database and all the metadata about
ports/packages anyway? Just rm
 /usr/include and /usr/share/doc, /usr/share/man, etc. when building
your disk image. But you
 are doing that already anyway, so this solves no actual problem for
you.
 
 My two cents Uli
 
 I also don't see why we need to optimize our packages for an embedded
environment that is
 usually very customized. Wouldn't it make more sense to provide some
proper port / packaging
 options/flags that help to optimize size of the packages without
touching header files? People
 could use that flags and poudriere to build their packages together
with all their other 
 compiler flags and cpu optimisations.
 

+1

As far as I can see Daniel Nebdal's approach (WITH_DEV_FILES flag,
and defaulting to yes)
sounds promising.

+1 

This doesn't change things in the standard case and follows existing patterns, 
so I like it, too.

Mathias


Pascal
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.21 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSUZ9hAAoJEAWefonBOgAfDlUP/3117hVdZ6WhrygIGnctSb49
V+i0SggAFxXuvFFYlkjexrWFpjMPN2H7vBtR9DVbLNwqb4En+mVj/LVY1ejS9TAQ
gj/nKlK6HNdVQWQD8qLfzFUAzWwnSBco/rIOiGkOrHuvFSUCTV5gPehoJ+Vg8Qnz
dyUp5SByePNpY1MGMTJZh9gKWJFtTe8DcanDBCVL65rZf/eOVPyiMwlQK+Fy2AQj
OQgJxhkWJzvl5V9THsMGiSCzJ+9EMoC620F9WEs3MvO0Ky2zIercFJ2bDaks6CXn
arNTsqTT1zI0sZNGNQMrnxYtQPgV3oCEAggj4ZOG0FkhmBkxWNOPUyahBUE/V8ds
tvLvugzVzqeaIJWg3IKDNEfGGh0ZnAMhUakUHyJPDhuCLgb498uwElesmgaSvlky
eotS4cWGVp2lquuf/xPRRl82K4ciozZi3mttRmrfoznK69p1HJbepCn9maIhFkii
WqLTjKVkeZ778is8mw8dom/Qb8OEj+XR6Vetq7cLg4Is//zieKzSvMWm7QrW1dAI
zohAjP+lMP5d3TEmeVqvSZhQ9ticzqGGaW4U7zxxRZ0Y/zxkBwe3cIBEpjTpnW9p
/a0DJ3JodVBo79N2JheIqweCK9RPn8rOK5HxujnWcJ3jbQAgCxOdLd9iyN6IxOjI
3pHI9pO++Am9ReFvL/Uy
=qm+q
-END PGP SIGNATURE-

Re: [HEADSUP] Staging, packaging and more

[Mathias Picker]

Am Samstag, den 05.10.2013, 11:57 +0200 schrieb Miroslav Lachman:
 
 Baptiste Daroussin wrote:
  On Fri, Oct 04, 2013 at 02:22:52PM +0200, Miroslav Lachman wrote:
  Baptiste Daroussin wrote:
  On Fri, Oct 04, 2013 at 08:00:43AM +0100, Matthew Seaman wrote:
  On 04/10/2013 07:32, Baptiste Daroussin wrote:
  On the other ends, that makes the package fat for embedded systems, 
  that also
  makes some arbitrary runtime conflicts between packages (because they 
  both
  provide the same symlink on the .so, while we could live with 2 version 
  at
  runtime), that leads to tons of potential issue while building locally, 
  and
  that makes having sometime insane issues with dependency tracking. Why 
  having
  .a, .la, .h etc in production servers? It could greatly reduce PBI 
  size, etc.
 
  Personnaly I do have no strong opinion in one or another direction. 
  Should we be
  nicer with developers? with end users? with embedded world? That is the 
  question
  to face to decide if -devel packages is where we want to go or not.
 
  Can't we have the best of both worlds?
 
  We're already planning on creating sub-packages for eg. docs and
  examples.  The default will be to install docs etc. sub-packages
  automatically unless the user opts out in some way.  I imagine there
  will be a global switch somewhere -- in pkg.conf or similar[*].
 
  Couldn't we work devel packages in the same way? Install by default
  alongside the main package unless explicitly requested not to.
 
  I think having the capability to selectively install parts of packages
  like this is important and useful functionality and something that will
  be indispensible for eg. embedded platforms.  But not an option that the
  vast majority of ordinary users will need to exercise.
 
   Cheers,
 
   Matthew
 
  [*] The precise mechanism for choosing which sub-package bits to install
  has not yet been written.  If anyone has any bright ideas about how this
  should all work, then I'd be interested to hear them.
 
 
  That is another possiblity, I do prefer Erwin's idea about the -full, but 
  this
  also makes a lot of sense.
 
  I really like the current state with full packages. Disk space is cheap,
  full packages is default for whole FreeBSD existence and it is easy to
  maintain the system with it. If I want portA and portB, I just install
  portA and portB and if I want to see installed ports, I see two ports
  installed and not a bunch of lines like:
  portA-bin
  portA-doc
  portA-dev
  portB-bin
  portB-doc
  portB-dev
 
  When I need to update those ports, I will update two ports, not six or
  more ports / sub ports.
 
  Embedded systems are corner case, where many things need to be tweaked
  anyway.
 
  So I like the idea of default full packages with possibility to
  optionally select and install sub parts for those who really need the
  fine grained list of packages.
 
  That is because you keep thinking you have to build those ports yourself, 
  we are
  here speaking of binary packages.
 
 I don't think it's about building ports. It's about the list of what I 
 need to have installed and maintained on our systems. And with this 
 split to more packages, then the list will grow and tracking of changes 
 and dependencies will become hell like on Linux distributions.

+1

Mathias

 
 Miroslav Lachman
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: [HEADSUP] Staging, packaging and more

[Mathias Picker]

Am Freitag, den 04.10.2013, 06:12 -0500 schrieb Bryan Drewery:
 On Fri, Oct 04, 2013 at 09:01:58AM +0200, Baptiste Daroussin wrote:
  On Fri, Oct 04, 2013 at 08:57:53AM +0200, Erwin Lansing wrote:
   On Fri, Oct 04, 2013 at 08:32:59AM +0200, Baptiste Daroussin wrote:
   
Please no devel packages.
  
   Seconded.
 
  What's wrong with devel packages?
 
 It complicates things for developers and custom software on
 FreeBSD. The typical situation that I see on most Linux platforms is a
 lot of confusion by people, why their custom software XYZ does not
 properly build - the most common answer: they forgot to install a
 tremendous amount of dev packages, containing headers, build tools and
 whatnot.
 On FreeBSD, you can rely on the fact that if you installed e.g. libGL,
 you can start building your own GL applications without the need to
 install several libGL-dev, libX11-dev, ... packages first.
 This is something, which I personally see as a big plus of the FreeBSD
 ports system and which makes FreeBSD attractive as a development 
 platform.
 

On the other ends, that makes the package fat for embedded systems, 
that also
makes some arbitrary runtime conflicts between packages (because they 
both
provide the same symlink on the .so, while we could live with 2 version 
at
runtime), that leads to tons of potential issue while building locally, 
and
that makes having sometime insane issues with dependency tracking. Why 
having
.a, .la, .h etc in production servers? It could greatly reduce PBI 
size, etc.

Personnaly I do have no strong opinion in one or another direction. 
Should we be
nicer with developers? with end users? with embedded world? That is the 
question
to face to decide if -devel packages is where we want to go or not.

   
   If we chose to go down that path, at least we should chose a different
   name as we've used the -devel suffix for many years for developmental
   versions.
   
   I must agree that it is one of the things high on my list of things that
   irritate me with several Linux distributions but I can see the point for
   for embedded systems as well.  But can't we have both?  Create three
   packages, a default full package and split packages of -bin, -lib,
   and even -doc.  My first though twas to make the full package a
   meta-package that would install the split packages in the background,
   but that would probably be confusing for users at the end of the day, so
   rather just have it be a real package.
   
  I do like that idea very much, and it is easily doable with stage :)
 
 +1 to splitting packages for embedded usage.

For me, the full packages of FreeBSD where allways one big plus. I
*hate* trying to compile anything and having to (find and) blow up my
package count. Just more things to keep track of. 

Disk space is cheap, and it's getting cheaper, even on embedded systems.
Is this really the time to optimize for a special case that might even
(slowly) fade away as storage even in tiny system grows and grows? 


Regards, Mathias




 
  
  regards,
  Bapt
 
 


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: pkgng: sqlite: database is locked

[Mathias Picker]

And again, this time with mongodb only.

Running portmaster databases/mongodb I get:


pkg: sqlite: database is locked
Assertion failed: (db-lock_count == 0), function pkgdb_close, file
pkgdb.c, line 842.
Abort trap (core dumped)

===  Installing for mongodb-2.2.0_1

There is no lock on the db right after this. Looks more like a pkg
problem, don't you think.

here is a Backtrace:

(gdb) bt
#0  0x00609d4c in thr_kill ()
#1  0x00669068 in abort ()
#2  0x006514e0 in __assert ()
#3  0x004160e8 in pkgdb_close (db=0x800c08060) at pkgdb.c:842
#4  0x00403342 in exec_delete (argc=1, argv=0x7fffcb08)

at /usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/../pkg//delete.c:120
#5  0x004051c8 in main (argc=3, argv=0x7fffcaf8)

at /usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/../pkg//main.c:328

Cheers, Mathias

On Do, 2012-12-13 at 08:16 -0600, Bryan Drewery wrote:
 On 12/13/2012 5:16 AM, Baptiste Daroussin wrote:
  On Thu, Dec 13, 2012 at 12:08:00PM +0100, Mathias Picker wrote:
  (FYI: if I stop responding, I will be in hospital, I'm waiting for an
  operation...)
  
  Take care of yourself, we will continue investigating, health first !

Thanks a lot (!!).

  
 
  OK, I can reproduce it now reliably, running portmaster -a, the
  following is happening three times now:
 
 
  sounds like a pkgng support in portmaster bugs we will investigate
  
 
 Yes, portmaster has an obscure job bug even without pkgng. It manifests
 with the Terminated output. I believe it's causing the pkgng db to be
 opened twice here.
 
 I'm looking into it.
 


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

pkgng: sqlite: database is locked

[Mathias Picker]

(FYI: if I stop responding, I will be in hospital, I'm waiting for an
operation...)

OK, I can reproduce it now reliably, running portmaster -a, the
following is happening three times now:



===  Building for p5-IO-Socket-SSL-1.81
cp lib/IO/Socket/SSL.pm blib/lib/IO/Socket/SSL.pm
Manifying blib/man3/IO::Socket::SSL.3
pkg: sqlite: database is locked
Assertion failed: (db-lock_count == 0), function pkgdb_close, file
pkgdb.c, line 842.
Abort trap (core dumped)


No locks active

mp# fstat /var/db/pkg/pkgdb.db /var/db/pkg/local.sqlite
USER CMD  PID   FD MOUNT  INUM MODE SZ|DV R/W
NAME
mp# sockstat | grep -e local.sqlite -e pkgdb.db
mp# 

So I guess ist's a pkg problem

Which additional information might be needed to debug this?

I just wanted to recompile pkg with debug info, but get

mp# make
/usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/pkg-static: not
found
*** [check-vulnerable] Error code 127

Stop in /usr/ports/ports-mgmt/pkg.
mp# make extract
/usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/pkg-static: not
found
*** [check-vulnerable] Error code 127

Stop in /usr/ports/ports-mgmt/pkg.

?? Never seen this... Will have to investigate before continuing.

/ Mathias

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: pkgng: sqlite: database is locked

[Mathias Picker]

Oh well, after building pkg with debug the error went away... :(

I rebuild pkg just before I started portmaster -a the first time, so
either it's the time it took to rebuild pkg with debug, or the debug
build itself...

Portmaster is still running, so maybe it comes up again

Cheers, Mathias

Am Donnerstag, den 13.12.2012, 12:16 +0100 schrieb Baptiste Daroussin:
 On Thu, Dec 13, 2012 at 12:08:00PM +0100, Mathias Picker wrote:
  (FYI: if I stop responding, I will be in hospital, I'm waiting for an
  operation...)
 
 Take care of yourself, we will continue investigating, health first !
 
  
  OK, I can reproduce it now reliably, running portmaster -a, the
  following is happening three times now:
  
  
 sounds like a pkgng support in portmaster bugs we will investigate
 
 Thanks.
 
 regards,
 Bapt
  
  ===  Building for p5-IO-Socket-SSL-1.81
  cp lib/IO/Socket/SSL.pm blib/lib/IO/Socket/SSL.pm
  Manifying blib/man3/IO::Socket::SSL.3
  pkg: sqlite: database is locked
  Assertion failed: (db-lock_count == 0), function pkgdb_close, file
  pkgdb.c, line 842.
  Abort trap (core dumped)
  
  
  No locks active
  
  mp# fstat /var/db/pkg/pkgdb.db /var/db/pkg/local.sqlite
  USER CMD  PID   FD MOUNT  INUM MODE SZ|DV R/W
  NAME
  mp# sockstat | grep -e local.sqlite -e pkgdb.db
  mp# 
  
  So I guess ist's a pkg problem
  
  Which additional information might be needed to debug this?
  
  I just wanted to recompile pkg with debug info, but get
  
  mp# make
  /usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/pkg-static: not
  found
  *** [check-vulnerable] Error code 127
  
  Stop in /usr/ports/ports-mgmt/pkg.
  mp# make extract
  /usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/pkg-static: not
  found
  *** [check-vulnerable] Error code 127
  
  Stop in /usr/ports/ports-mgmt/pkg.
  
  ?? Never seen this... Will have to investigate before continuing.
  
  / Mathias
  
  ___
  freebsd-ports@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-ports
  To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

pkgng: sqlite: database is locked

[Mathias Picker]

I'm getting sqlite: database is locked errors with pkg. For deinstalls
(portmaster updates) and fresh port installs with make install. The
latest is

===   Registering installation for MuSE-0.9.2_14
Installing MuSE-0.9.2_14... done
pkg: sqlite: database is locked

which results in muse not being registered in the pkg database...

How can I investigate this further? This persists between reboots, and
for fresh pkg runs. 

I'm hesitating to upgrade all the changes after the ports freeze has
been lifted...

I'm using a FreeBSD-stable and have changed to pkgng maybe two weeks
ago. At the first portmaster -a after the upgrade, I think everything
went smooth, and then more and more of these errors popped up.
Everything is build using gcc.

mp# uname -a
FreeBSD mp.virtual-earth.de 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #28
r243882: Wed Dec  5 18:28:39 CET 2012
mathi...@mp.virtual-earth.de:/usr/obj/usr/src/sys/GENERIC  amd64

mp# pkg -v
1.0.3

Any help apreciated,

Mathias


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)

[Mathias Picker]

Am Dienstag, den 11.12.2012, 18:16 +0200 schrieb Kimmo Paasiala:
 On Tue, Dec 11, 2012 at 5:55 PM, Bryan Drewery bdrew...@freebsd.org wrote:
  (As maintainer) I'm proposing to make -w the default for portmaster.
  This will preserve old shared libraries when upgrading. This helps 2 things:
 
  1. Prevents a broken system during upgrades
  2. Prevents a broken system after upgrading for ports that did not get a
  PORTREVISION bump from a shared library update.
 
  You have certainly ran into this problem with large library updates such
  as png, pcre, openssl, etc.
 
  Portupgrade has always done this as default, and I have never seen any
  problems arise from it. It also cleans up prevents duplicated library
  versions. If portmaster is not already doing this, I will ensure it does.
 
  You could then use pkg_libchk to rebuild any lingering ports if you
  wanted to ensure your system was using the latest. Then cleanout the
  preserved shared library.
 
  Of course there will be a way to stick to the old default of not
  preserving the libraries.
 
  Someone may consider this a POLA violation, but I consider that a broken
  system from missing libraries and PORTREVISION bumps is more of a POLA
  violation.
 
 
  The other option to ensuring that all ports work correctly after a
  shared library update is to just rebuild any port which recursively is
  affected by another port being updated. I think this is fine in
  scenarios such as tinderbox/poudriere, but with end-user compiling ports
  on their system, this may quickly become too much of a burden.
 
 
  Regards,
  Bryan Drewery
 
 
 
 Absolutely yes from me. The -w option is real lifesaver and should be
 on by default.

+1

Cheers, Mathias

 
 -Kimmo
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: pkgng: sqlite: database is locked

[Mathias Picker]

Am Dienstag, den 11.12.2012, 19:02 +0100 schrieb Olli Hauer:
 On 2012-12-11 15:13, Mathias Picker wrote:
  I'm getting sqlite: database is locked errors with pkg. For deinstalls
  (portmaster updates) and fresh port installs with make install. The
  latest is
  
  ===   Registering installation for MuSE-0.9.2_14
  Installing MuSE-0.9.2_14... done
  pkg: sqlite: database is locked
  
  which results in muse not being registered in the pkg database...
  
  How can I investigate this further? This persists between reboots, and
  for fresh pkg runs. 
  
  I'm hesitating to upgrade all the changes after the ports freeze has
  been lifted...
  
  I'm using a FreeBSD-stable and have changed to pkgng maybe two weeks
  ago. At the first portmaster -a after the upgrade, I think everything
  went smooth, and then more and more of these errors popped up.
  Everything is build using gcc.
  
  mp# uname -a
  FreeBSD mp.virtual-earth.de 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #28
  r243882: Wed Dec  5 18:28:39 CET 2012
  mathi...@mp.virtual-earth.de:/usr/obj/usr/src/sys/GENERIC  amd64
  
  mp# pkg -v
  1.0.3
  
  Any help apreciated,
  
  Mathias
  
 
 Hi Mathias,
 
 maybe you could find with one of the commands the process which
 locks the database.
 
 # fstat /var/db/pkg/pkgdb.db /var/db/pkg/local.sqlite
 # sockstat | grep -e local.sqlite -e pkgdb.db

OK:
mp# fstat /var/db/pkg/pkgdb.db /var/db/pkg/local.sqlite
USER CMD  PID   FD MOUNT  INUM MODE SZ|DV R/W
NAME
mp# sockstat | grep -e local.sqlite -e pkgdb.db
mp# 

I retried the muse install which gave me an error before, now it works
fine?? Maybe it's only after portmaster runs?

Maybe a pkg invocation which does not release the lock? I will look into
this again.

Thanks, Mathias

 
 --
 Regards,
 olli
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: PORT: multimedia/phonon-xine

[Mathias Picker]

Use  phonon-gstreamer.

portmaster -o multimedia/phonon-gstreamer multimedia/phonon-xine

/ Mathias

On Sa.,   3. Mär. 2012 13:36:14 CET, Jerry je...@seibercom.net wrote:

 Attempting to build the multimedia/phonon-xine port produces this
 error message:
 
 ===   phonon-xine-4.4.4_2 is marked as broken: deprecated upstream;
 refuses to build with libxine 1.2.x. *** Error code 1
 
 What is the status of getting this port fixed or the recommended
 procedure to circumvent this problem?
 
 -- 
 Jerry ♔
 
 Disclaimer: off-list followups get on-list replies or get ignored.
 Please do not ignore the Reply-To header.
 __
 
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: FreeBSD Port: graphics/rawtherapee

[Mathias Picker]

Am Dienstag, den 14.02.2012, 20:43 +0100 schrieb Heino Tiedemann:
 Mathias Picker mathias.pic...@virtual-earth.de wrote:
 
  Good god, 
 
  I must have worn both my eye patches at the same time.
 
  Sorry,
 
  Mathias
 
 Mayby you can try to install graphics/rawtherapee - just to approve
 (or discard) my problem.

Sure. The rawtherapee build just completed without errors.

It's still not usable for me, it freezes while loading a raw from my
camera.

FreeBSD mp.virtual-earth.de 9.0-STABLE FreeBSD 9.0-STABLE #5: Wed Feb  8
13:14:32 CET 2012
mathi...@mp.virtual-earth.de:/usr/obj/usr/src/sys/GENERIC  amd64

default cc, nothing unusual on this machine I'm aware of.


 
 Heino
 
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: FreeBSD Port: graphics/rawtherapee

[Mathias Picker]

Strange, I can build it just fine, only it crashes without the crude
workaround described here:

http://bugzilla.rawstudio.org/show_bug.cgi?id=525

mp% uname -a
FreeBSD mp.virtual-earth.de 9.0-STABLE FreeBSD 9.0-STABLE #5: Wed Feb  8
13:14:32 CET 2012
mathi...@mp.virtual-earth.de:/usr/obj/usr/src/sys/GENERIC  amd64


Am Montag, den 13.02.2012, 17:39 +0100 schrieb Heino Tiedemann:
 Hi,
 
 is there anyone who likes zu make graphics/rawtherapee builadable?
 
 At the moment ist seems to be broken (also on i386).
 
 See: http://www.freebsd.org/cgi/query-pr.cgi?pr=164714
 
 
 
 Heino
 
 
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

-- 
Mathias Picker
Geschäftsführer
mathias.pic...@virtual-earth.de

virtual earth Gesellschaft für Wissens re/prä sentation mbH
http://www.virtual-earth.de/   HRB126870
supp...@virtual-earth.de   Dietlindenstr. 15
0152 / 5617 8344   80802 München

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: FreeBSD Port: graphics/rawtherapee

[Mathias Picker]

Good god, 

I must have worn both my eye patches at the same time.

Sorry,

Mathias

Am Montag, den 13.02.2012, 22:12 +0100 schrieb Heino Tiedemann:
 Mathias Picker mathias.pic...@virtual-earth.de wrote:
 
  Strange, I can build it just fine, only it crashes without the crude
  workaround described here:
 
  http://bugzilla.rawstudio.org/show_bug.cgi?id=525
 
 
 That has the Toppic RAWSTUDIO.
 
 I am talking about RAWTHERAPEE
 
 Heino
 
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

-- 
Mathias Picker
Geschäftsführer
mathias.pic...@virtual-earth.de

virtual earth Gesellschaft für Wissens re/prä sentation mbH
http://www.virtual-earth.de/   HRB126870
supp...@virtual-earth.de   Dietlindenstr. 15
0152 / 5617 8344   80802 München

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Small question about FreeNX for freebsd.

[Mathias Picker]

The following patch works mostly on 7.0. I had troubles on 6.0, but that
might have been a problem with my configuration.

Fonts look horrible with subpixel anti-aliasing, but greyscale is fine.

Also, the color chooser for the gnome background is broken, but all
others (gimp, inkscape, OOo) work fine.

All other features seem to work fine. I tried the 3.0 client on windows,
the 1.4 on FreeBSD and the 3.0 on Mac (had to manually adjust the
keyboard)

Cheers, Mathias

--- nx-X11/config/cf/FreeBSD.cf.orig2007-11-28 
+++ nx-X11/config/cf/FreeBSD.cf 2007-11-28 
@@ -65,7 +65,7 @@
 
 #if (OSMajorVersion = 3)
 #define HasIssetugid   YES
-#define HasPollYES
+#define HasPollNO
 #endif
 
 #if OSMajorVersion = 4
@@ -82,6 +82,7 @@
  * Multi-thread safe libs 
  */
 /* 2.2.7 and later has libc_r (POSIX threads) */
+/* 7.0 and later have libpthread instead of libc_r */
 #if OSMajorVersion == 2  OSMinorVersion == 2  OSTeenyVersion = 7
|| \
 OSMajorVersion = 3
 # ifndef HasLibPthread
@@ -106,7 +107,7 @@
 #   define NeedUIThrStubs  YES
 #  endif
 #  if (OSRelVersion = 500016)
-#   define ThreadsLibraries-lc_r
+#   define ThreadsLibraries-lpthread
 #  else
 #   define ThreadsLibraries-pthread
 #  endif

Am Mittwoch, den 28.11.2007, 08:55 -0500 schrieb dewey hylton:
 Quoting Jim van Wel [EMAIL PROTECTED]:
 
  Hi there,
  
  Are you going to update this soon to a newer version in the ports? Just
  wondering because of the old version number, and using it of course ;)
  
  Greetings,
  
  Jim.
 
 the freenx and nxserver ports go hand-in-hand; freenx cannot be updated 
 without
 first updating nxserver. unfortunately, i have been so far unable to build 
 later
 nxserver sources under xorg-7.x and haven't received working patches either. i
 spent plenty of time on the project myself but have been unable to make it 
 work
 myself - i need help. patches are welcomed.
 
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: x11/ati-driver

[Mathias Picker]

Am Sonntag, den 07.10.2007, 00:54 + schrieb mr. phreak:
 Hi!
 
 I'm trying to make the ati-fglrx driver work under freebsd-6.2 - 
 RELEASE. I've had no success. After installing from ports I simply get 
 'can't find fglrx ' from Xorg.0.log.

Where did you get your fglrx driver? As far as I know, only the
open-source driver (e.g. x11-drivers/xf86-video-ati, and ati in
xorg.conf) exists on freebsd...

Or am I wrong?

 
 Is there anyone out there with a successful install of this driver?  Or 
 perhaps another sollution for making tv-out work for the radeon 
 9200-cards? I'm on Xorg 7.2.

The current open-source driver supports xrandr and (at least on my acer
travelmate) video out.

Cheers, Mathias

 
 
 Best regards,
 J
 
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

xorg 7.3: ati card comes up blank

[Mathias Picker]

After my upgrade on -current to xorg 7.3 the ATI Radeon RV350 Mobility
9600 M10 NP in my travelmate 290 comes up blank. I'm now using the vesa
driver. Has anyone else experienced this?

my sytem: FreeBSD mp.virtual-earth.de 7.0-CURRENT FreeBSD 7.0-CURRENT
#3: Fri Sep 14   

xorg.conf: happens also without xorg.conf

one additional data point: if I try to disable one of the other outputs
(e.g. monitor-vga, monitor-S-video) the X server does not start at all
but says there are no usable screens configured...? 


Thanks for any help, Mathias



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]