[QAT] r334036: 2x leftovers, 1x depend (depend_package in devel/libnotify), 5x success

2013-11-17 Thread Ports-QAT
atus: DEPEND (DEPEND_PACKAGE IN DEVEL/LIBNOTIFY) Log: https://qat.redports.org//~swi...@freebsd.org/20131116232400-56738-227457/libnotify-0.7.5.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~swi...@freebsd.org/20131116232400-5

10-CURRENT && ports/devel/libnotify does not build

2011-11-04 Thread Matthias Apitz
Hello, ports/devel/libnotify (requested by www/firefox36) does not build in 10-CURRENT (ports uptodate to November 3 from CVS): # make ... checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for PACKAGE... yes checking for TESTS

Re: libproxy and libnotify the story continues :D

2011-08-31 Thread Rainer Hurling
Oops, I just realized that this was answered in another mail from Michal Varga. Sorry for the noise. On 31.08.2011 19:06 (UTC+1), Rainer Hurling wrote: On 31.08.2011 11:14 (UTC+1), Johan Hendriks wrote: Hello all, i also ran into the libproxy upgrade problems. So i tried al the stuff i found

Re: libproxy and libnotify the story continues :D

2011-08-31 Thread Rainer Hurling
On 31.08.2011 11:14 (UTC+1), Johan Hendriks wrote: Hello all, i also ran into the libproxy upgrade problems. So i tried al the stuff i found on the mailling list so far. I tried the solution from j.kim find /usr/local/lib -name "*.la" | \ xargs grep -l /usr/local/lib/libproxy.la | \

RE: libproxy and libnotify the story continues :D

2011-08-31 Thread Johan Hendriks
Van: Michal Varga [varga.mic...@gmail.com] Verzonden: woensdag 31 augustus 2011 11:19 Aan: Johan Hendriks CC: freebsd-ports@freebsd.org Onderwerp: Re: libproxy and libnotify the story continues :D >This is another iteration of the same old is

Re: libproxy and libnotify the story continues :D

2011-08-31 Thread Michal Varga
On Wed, 2011-08-31 at 09:13 +, Johan Hendriks wrote: > Hello all, i also ran into the libproxy upgrade problems. > > So i tried al the stuff i found on the mailling list so far. > > I tried the solution from j.kim > > find /usr/local/lib -name "*.la" | \ > xargs grep -l /usr/local/lib/

libproxy and libnotify the story continues :D

2011-08-31 Thread Johan Hendriks
Hello all, i also ran into the libproxy upgrade problems. So i tried al the stuff i found on the mailling list so far. I tried the solution from j.kim find /usr/local/lib -name "*.la" | \ xargs grep -l /usr/local/lib/libproxy.la | \ xargs -L 1 pkg_info -W | \ awk '{ print

libproxy and libnotify the story continues :D

2011-08-31 Thread Johan Hendriks
Hello all, i also ran into the libproxy upgrade problems. So i tried al the stuff i found on the mailling list so far. I tried the solution from j.kim find /usr/local/lib -name "*.la" | \ xargs grep -l /usr/local/lib/libproxy.la | \ xargs -L 1 pkg_info -W | \ awk '{ print

gimp-gmic-plugin unbreak (Was: Re: libnotify)

2011-08-30 Thread Ruslan Mahmatkhanov
Koop Mast wrote on 24.08.2011 16:20: On Wed, 2011-08-24 at 14:45 +0400, Ruslan Mahmatkhanov wrote: ajtiM wrote on 24.08.2011 14:38: Stop in /usr/ports/graphics/gimp-gmic-plugin. *** Error code 1 Stop in /usr/ports/graphics/gimp-gmic-plugin. ===>>> make failed for graphics/gimp-gmic-plugin

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Sahil Tandon
On Mon, 2011-08-29 at 00:28:42 +0200, Michal Varga wrote: > Yes, I have read the thread and that's why I didn't feel need to add > anything directly related to _the issue_ - as everything needed was > already said, and solved, by that time. > > I'm not sure why exactly are you accusing me of ad h

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Doug Barton
On 8/28/2011 3:28 PM, Michal Varga wrote: > Not every person that doesn't write in pink letters is > necessarilly a troll, and not every person making a sarcastic comment > about a pretty frustrating situation is there to make a personal attack > (on you, or anyone else). Being frustrated and/or a

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Michal Varga
On Sun, 2011-08-28 at 17:14 -0400, Sahil Tandon wrote: > > Replies like these already made me discard like 20 of my own emails in > > the past, mid-write, exactly because of this expected outcome - > > accusations of trolling, because, why not, that's really what it's all > > about, right. > > Hav

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Sahil Tandon
On Sun, 2011-08-28 at 13:57:18 -0700, Doug Barton wrote: > On 8/28/2011 11:33 AM, Kostik Belousov wrote: > > Ignoring or removing the option makes the ports upgrade without user > > intervention. > > Neither of those is a valid option (pardon the pun). The primary goal > is to avoid breaking the

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Sahil Tandon
On Sun, 2011-08-28 at 22:54:49 +0200, Michal Varga wrote: > On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: > > [...] > > Criminal? Indifference? This sort of troll-ish hyperbole is decidedly > > unhelpful. I do agree that a note in UPDATING is appropriate. > > [...] > > Ah, more troll

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Doug Barton
On 8/28/2011 11:33 AM, Kostik Belousov wrote: > Apparently, this have to be written explicitely. Users, who upgrade > their ports, are not presented with the configuration dialog. The dialog is re-presented to the user if the quantity of options has changed. That's a feature. See my previous messa

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Michal Varga
On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: [...] > Criminal? Indifference? This sort of troll-ish hyperbole is decidedly > unhelpful. I do agree that a note in UPDATING is appropriate. [...] > Ah, more trolling. To contribute my random few cents to the debate (without actually con

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Sahil Tandon
On Sun, 2011-08-28 at 15:22:34 -0400, Jerry wrote: > On Sun, 28 Aug 2011 14:45:42 -0400 > Sahil Tandon articulated: > > > I am sorry users have had to "intervene" in managing their systems, > > but rather than removing the option entirely, I prefer mandree@'s more > > structural suggestion of re-

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Jerry
On Sun, 28 Aug 2011 14:45:42 -0400 Sahil Tandon articulated: > I am sorry users have had to "intervene" in managing their systems, > but rather than removing the option entirely, I prefer mandree@'s more > structural suggestion of re-prompting the user when defaults change. > In the meantime, a no

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Kostik Belousov
n Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: > >> > > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: > >> > > > >> > > > My question is what changed? It worked before updating "libnotify". > >> > > > Is &

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Sahil Tandon
; > > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: > > > > > > > > > My question is what changed? It worked before updating "libnotify". Is > > > > > "libnotify" the culprit or "GNUTLS" or something else and

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Chris Rees
2011-08-28 at 11:30:27 -0400, Carmel wrote: >> > > >> > > > My question is what changed? It worked before updating "libnotify". Is >> > > > "libnotify" the culprit or "GNUTLS" or something else and why didn't >> &

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Kostik Belousov
> > My question is what changed? It worked before updating "libnotify". Is > > > > "libnotify" the culprit or "GNUTLS" or something else and why didn't > > > > anyone catch this problem sooner? > > > > > > The cha

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Sahil Tandon
On Sun, 2011-08-28 at 20:30:59 +0300, Kostik Belousov wrote: > On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: > > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: > > > > > My question is what changed? It worked before updating "libnotify". I

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Chris Rees
On 28 August 2011 18:30, Kostik Belousov wrote: > On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: >> On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: >> >> > My question is what changed? It worked before updating "libnotify". Is >>

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Kostik Belousov
On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: > > > My question is what changed? It worked before updating "libnotify". Is > > "libnotify" the culprit or "GNUTLS" or something e

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Leslie Jensen
2011-08-28 16:33, Chris Rees skrev: make -C /usr/ports/print/cups-client config, disable TLS. Chris On 28 Aug 2011 15:15, "Leslie Jensen" wrote: Following the instructions in /usr/ports/UPDATING I issued the command portmaster -r libnotify-0 And after a while I get

Re: OPTIONS framework bug vs. SSL issues (was: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken)

2011-08-28 Thread Sahil Tandon
On Sun, 2011-08-28 at 19:41:02 +0200, Matthias Andree wrote: > just a brain flash: bsd.port.mk currently re-prompts OPTIONS if > they've changed, for instance, through addition. > > Should we change this feature in b.p.mk so that it also re-prompt the > user when the defaults have changed? Sound

Re: OPTIONS framework bug vs. SSL issues (was: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken)

2011-08-28 Thread Matthias Andree
Am 28.08.2011 16:33, schrieb Chris Rees: > make -C /usr/ports/print/cups-client config, disable TLS. > > Chris > On 28 Aug 2011 15:15, "Leslie Jensen" wrote: >> >> Following the instructions in /usr/ports/UPDATING I issued the command >> >> >>

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Sahil Tandon
On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: > My question is what changed? It worked before updating "libnotify". Is > "libnotify" the culprit or "GNUTLS" or something else and why didn't > anyone catch this problem sooner? The chain of depen

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Carmel
On Sun, 28 Aug 2011 10:30:31 -0400 Robert Huff articulated: > Leslie Jensen writes: > > > > Following the instructions in /usr/ports/UPDATING I issued the > > command > > > > portmaster -r libnotify-0 > > > > And after a while I get this e

How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Robert Huff
Leslie Jensen writes: > > Following the instructions in /usr/ports/UPDATING I issued the command > > > portmaster -r libnotify-0 > > And after a while I get this error > > Dependency check complete for print/cups-client > libnotify-0.5.2 >>

Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Chris Rees
make -C /usr/ports/print/cups-client config, disable TLS. Chris On 28 Aug 2011 15:15, "Leslie Jensen" wrote: > > Following the instructions in /usr/ports/UPDATING I issued the command > > > portmaster -r libnotify-0 > > And after a while I get this error > >

How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

2011-08-28 Thread Leslie Jensen
Following the instructions in /usr/ports/UPDATING I issued the command portmaster -r libnotify-0 And after a while I get this error Dependency check complete for print/cups-client libnotify-0.5.2 >> swt-devel-3.6.m5_2,1 >> apache-ant-1.8.2 >> jdk-1.6.0.3p4_25 &g

Re: libnotify & notification-daemon oddness

2011-08-26 Thread Olivier Duchateau
2011/8/26 Jimmie James : > libnotify-0.7.3_1 > notification-daemon-0.7.1 > FreeBSD jimmiejaz.org 8.2-STABLE FreeBSD 8.2-STABLE #0: Sun Jun 26 08:42:45 > EDT 2011     jim...@jimmiejaz.org:/usr/obj/usr/src/sys/FORTYTWO  i386 > > After following the portupgrade steps to update libn

libnotify & notification-daemon oddness

2011-08-26 Thread Jimmie James
libnotify-0.7.3_1 notification-daemon-0.7.1 FreeBSD jimmiejaz.org 8.2-STABLE FreeBSD 8.2-STABLE #0: Sun Jun 26 08:42:45 EDT 2011 jim...@jimmiejaz.org:/usr/obj/usr/src/sys/FORTYTWO i386 After following the portupgrade steps to update libnotify and libproxy (notification-daemon got

Re: libnotify

2011-08-26 Thread Ruslan Mahmatkhanov
Koop Mast wrote on 24.08.2011 16:20: On Wed, 2011-08-24 at 14:45 +0400, Ruslan Mahmatkhanov wrote: ajtiM wrote on 24.08.2011 14:38: Stop in /usr/ports/graphics/gimp-gmic-plugin. *** Error code 1 Stop in /usr/ports/graphics/gimp-gmic-plugin. ===>>> make failed for graphics/gimp-gmic-plugin

Re: Update of libnotify and libproxy failed

2011-08-25 Thread Rainer Hurling
Am 25.08.2011 11:45 (UTC+1) schrieb Matthias Andree: Am 25.08.2011 11:37, schrieb Rainer Hurling: Am 25.08.2011 10:20 (UTC+1) schrieb Matthias Andree: Am 25.08.2011 09:25, schrieb Rainer Hurling: I tried to update libnotify and libproxy as described in UPDATING from 20110823. After

Re: Update of libnotify and libproxy failed

2011-08-25 Thread Doug Barton
On 08/25/2011 03:11, Doug Barton wrote: > Having given this some more thought, you could do a poor man's version > of multiple -r by doing this: portmaster --check-depends > pkg_info -qR libnotify-0\* libproxy-0\* | sort -u > list > > portmaster libnotify-0 libproxy-0

Re: Update of libnotify and libproxy failed

2011-08-25 Thread Doug Barton
On 08/25/2011 03:02, Florian Riehm wrote: > I tried Dougs way of upgrading and got in trouble too. Brasero don't > build because of a similar failture like Rainers Error during the > py-gnome-desktop build. You have to update libnotify and libproxy first > because some ports d

Re: Update of libnotify and libproxy failed

2011-08-25 Thread Florian Riehm
Am 25.08.2011 09:25, schrieb Rainer Hurling: I tried to update libnotify and libproxy as described in UPDATING from 20110823. After successfully building and installing some ports the process stops when it tries to build x11-toolkits/py-gnome-desktop

Re: Update of libnotify and libproxy failed

2011-08-25 Thread Matthias Andree
Am 25.08.2011 11:37, schrieb Rainer Hurling: > Am 25.08.2011 10:20 (UTC+1) schrieb Matthias Andree: >> Am 25.08.2011 09:25, schrieb Rainer Hurling: >>> I tried to update libnotify and libproxy as described in UPDATING from >>> 20110823. >>> >>> After su

Re: Update of libnotify and libproxy failed

2011-08-25 Thread Rainer Hurling
Am 25.08.2011 10:20 (UTC+1) schrieb Matthias Andree: Am 25.08.2011 09:25, schrieb Rainer Hurling: I tried to update libnotify and libproxy as described in UPDATING from 20110823. After successfully building and installing some ports the process stops when it tries to build x11-toolkits/py

Re: portmaster -r vs. ports/UPDATING (was: libnotify)

2011-08-25 Thread Matthias Andree
Am 24.08.2011 23:51, schrieb Doug Barton: > On Wed, 24 Aug 2011 05:38:50 -0500 > ajtiM wrote: > >> My system: FreeBSD 8.2-RELEASE-p1 >> >> I did: >> >> portmaster -r libnotify-0.\* >> libproxy-0.\* portmaster -a > > It's not clea

Re: libnotify

2011-08-25 Thread Doug Barton
On 08/24/2011 23:09, Koop Mast wrote: > Ok I didn't know this. I cannot possibly say this enough: Read The Man Page -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS.

Re: Update of libnotify and libproxy failed

2011-08-25 Thread Matthias Andree
Am 25.08.2011 09:25, schrieb Rainer Hurling: > I tried to update libnotify and libproxy as described in UPDATING from > 20110823. > > After successfully building and installing some ports the process stops > when it tries to build x11-toolkits/p

Update of libnotify and libproxy failed

2011-08-25 Thread Rainer Hurling
I tried to update libnotify and libproxy as described in UPDATING from 20110823. After successfully building and installing some ports the process stops when it tries to build x11-toolkits/py-gnome-desktop: mv -f .deps/ecal_la-evo-calendar.Tpo

Re: libnotify

2011-08-24 Thread Koop Mast
On 24-8-2011 23:51, Doug Barton wrote: On Wed, 24 Aug 2011 05:38:50 -0500 ajtiM wrote: My system: FreeBSD 8.2-RELEASE-p1 I did: portmaster -r libnotify-0.\* libproxy-0.\* portmaster -a It's not clear to me exactly what you were trying to accomplish there, but a few notes T

UPDATING entry incorrect (20110823: AFFECTS: users of devel/libnotify and net/libproxy)

2011-08-24 Thread Dmytro Pryanyshnikov
Hello! > kwm 2011-08-23 18:37:22 UTC > > FreeBSD ports repository > > Modified files: >.UPDATING > Log: > Add instructions for the libnotify and libproxy shlib bumps. ... > # portmaster -r libnotify-0.\* libproxy-0.\* It'

Re: libnotify

2011-08-24 Thread ajtiM
On Wednesday 24 August 2011 16:51:57 Doug Barton wrote: > On Wed, 24 Aug 2011 05:38:50 -0500 > > ajtiM wrote: > > My system: FreeBSD 8.2-RELEASE-p1 > > > > I did: > > portmaster -r libnotify-0.\* > > > > libproxy-0.\* portmaster -a > > I

Re: libnotify

2011-08-24 Thread Doug Barton
On Wed, 24 Aug 2011 05:38:50 -0500 ajtiM wrote: > My system: FreeBSD 8.2-RELEASE-p1 > > I did: > > portmaster -r libnotify-0.\* > libproxy-0.\* portmaster -a It's not clear to me exactly what you were trying to accomplish there, but a few notes The -r option

Re: libnotify

2011-08-24 Thread Koop Mast
On Wed, 2011-08-24 at 14:45 +0400, Ruslan Mahmatkhanov wrote: > ajtiM wrote on 24.08.2011 14:38: > > > Stop in /usr/ports/graphics/gimp-gmic-plugin. > > *** Error code 1 > > > > Stop in /usr/ports/graphics/gimp-gmic-plugin. > > > > ===>>> make failed for graphics/gimp-gmic-plugin > > ===>>> Abor

Re: libnotify

2011-08-24 Thread Ruslan Mahmatkhanov
ajtiM wrote on 24.08.2011 14:38: Stop in /usr/ports/graphics/gimp-gmic-plugin. *** Error code 1 Stop in /usr/ports/graphics/gimp-gmic-plugin. ===>>> make failed for graphics/gimp-gmic-plugin ===>>> Aborting update Too bad. I did not deal with recent updates yet, so i'll try to realize what

libnotify

2011-08-24 Thread ajtiM
My system: FreeBSD 8.2-RELEASE-p1 I did: portmaster -r libnotify-0.\* libproxy-0.\* portmaster -a And it stopped at: ===> License check disabled, port has not defined LICENSE ===> Found saved configuration for gim