Ports marked as IGNORE - (cups-pdf) & (urlview) why - how long?

[David Southwell]

Hi just curious about:

- print/cups-pdf (marked as IGNORE)
- textproc/urlview (marked as IGNORE)

Anyone know what is happening with these? Get IGNORE with portupgrade -a.

Thanks in advance for some info

David

[Doug Barton]

David Southwell wrote:
> Hi just curious about:
>
> - print/cups-pdf (marked as IGNORE)
> - textproc/urlview (marked as IGNORE)
>
> Anyone know what is happening with these? Get IGNORE with portupgrade -a.

$ cd /usr/ports/print/cups-pdf
$ make
===> cups-pdf-2.5.0 is marked as broken: does not install.
*** Error code 1

Stop in /usr/local/ports/print/cups-pdf.

$ portmaster .
===>>> Port directory: /usr/ports/print/cups-pdf
===>>> This port is marked BROKEN
===>>> does not install

===>>> If you are sure you can build it, remove the
BROKEN line in the Makefile and try again.

hth,

Doug

PS, Josh, if this e-mail address still works for you, howdy! :)

--

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

[David Southwell]

> David Southwell wrote:
> > Hi just curious about:
> >
> > - print/cups-pdf (marked as IGNORE)
> > - textproc/urlview (marked as IGNORE)
> >
> > Anyone know what is happening with these? Get IGNORE with portupgrade -a.
>
> $ cd /usr/ports/print/cups-pdf
> $ make
> ===> cups-pdf-2.5.0 is marked as broken: does not install.
> *** Error code 1
>
> Stop in /usr/local/ports/print/cups-pdf.
>
>
> $ portmaster .
> ===>>> Port directory: /usr/ports/print/cups-pdf
> ===>>> This port is marked BROKEN
> ===>>> does not install
>
> ===>>> If you are sure you can build it, remove the
> BROKEN line in the Makefile and try again.
>
>
> hth,
>
> Doug
>
> PS, Josh, if this e-mail address still works for you, howdy! :)
>

I am wondering what changes have taken place to change this from a functioning
port to one that justifies it being labelled as broken. It must have compiled
OK for me as I already have cups-pdf-2.5.0 installed which appears to be the
same version. I heard some rumour that it was failing on ubuntu but not on
freebsd. Is there any truth in that?

Is there any provision to ensure that something which should be marked as
broken for ubuntu is not, in consequence,automatically marked as broken when
on freebsd?

dns1# pkg_info |grep cups
cups-base-1.4.2_3 Common UNIX Printing System: Server
cups-client-1.4.2_3 Common UNIX Printing System: Library cups
cups-image-1.4.2_3 Common UNIX Printing System: Library cupsimage
cups-pdf-2.5.0 A virtual printer for CUPS to produce PDF files
cups-pstoraster-8.15.4_4 Postscript interpreter for CUPS printing to non-PS
printers
cups-samba-6.0_2 The Common UNIX Printing System: MS Windows client
drivers
cups-smb-backend-1.0_2 A CUPS backend for printing to Windows servers
gnome-cups-manager-0.31_10,1 Admistration tool for cups
gutenprint-cups-5.2.4 GutenPrint Printer Driver
libgnomecups-0.2.3_2,1 Support library for gnome cups admistration
py26-cups-1.9.46 CUPS bindings for Python
dns1#

[Alexey Shuvaev]

Strange, but you can try to figure out what happening at pointyhat:
http://people.freebsd.org/~fenner/errorlogs/si...@olofsson.de-date.html

0.02$,
Alexey.

[Koop Mast]

No.
http://www.freebsd.org/cgi/cvsweb.cgi/ports/print/cups-pdf/Makefile
http://portsmon.freebsd.org/portoverview.py?category=print&portname=cups-pdf

-Koop

> dns1# pkg_info |grep cups
> cups-base-1.4.2_3 Common UNIX Printing System: Server
> cups-client-1.4.2_3 Common UNIX Printing System: Library cups
> cups-image-1.4.2_3 Common UNIX Printing System: Library cupsimage
> cups-pdf-2.5.0 A virtual printer for CUPS to produce PDF files
> cups-pstoraster-8.15.4_4 Postscript interpreter for CUPS printing to non-PS
> printers
> cups-samba-6.0_2 The Common UNIX Printing System: MS Windows client
> drivers
> cups-smb-backend-1.0_2 A CUPS backend for printing to Windows servers
> gnome-cups-manager-0.31_10,1 Admistration tool for cups
> gutenprint-cups-5.2.4 GutenPrint Printer Driver
> libgnomecups-0.2.3_2,1 Support library for gnome cups admistration
> py26-cups-1.9.46 CUPS bindings for Python
> dns1#
>
>

> _______________________________________________
> freebs...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-port...@freebsd.org"
>

[David Southwell]

Maybe it was failing for pointhat - but certainly did not fail on my Freebsd
p3 amd64 (Intel Quad core). It was after I upgraded to 2.5.0 that it was
labelled as broken.

I have removed the Broke line from Makefile. It compiles without compalining
but I have not tried to deinstall/reinstall in case I break the appl.

Comments please?

david

[thi...@freebsd.org]

Selon David Southwell <da...@vizion2000.net> le Mar 22 dï¿œc 12:23:58 2009 :

[Cc: trimmed]

> I am wondering what changes have taken place to change this from a
> functioning
> port to one that justifies it being labelled as broken. It must have compiled
> OK for me as I already have cups-pdf-2.5.0 installed which appears to be the
> same version. I heard some rumour that it was failing on ubuntu but not on
> freebsd. Is there any truth in that?

Just answering about urlview: a patch is included in PR ports/141148

<http://www.freebsd.org/cgi/query-pr.cgi?pr=141148>

Feel free to apply it!

Regards,
--
Th. Thomas.

[David Southwell]

Thierry added his wisdom on 22nd Dec:
> Selon David Southwell <da...@vizion2000.net> le Mar 22 d�c 12:23:58 2009 :

> On Tue, Dec 22, 2009 at 11:23:58AM +0000, David Southwell wrote:

>> > > >David Southwell wrote:
> > > >> Hi just curious about:
> > > >>
> > > >> - print/cups-pdf (marked as IGNORE)
> > > >> - textproc/urlview (marked as IGNORE)
> > > >>
> > > >> Anyone know what is happening with these? Get IGNORE with portupgrade
> > > >> -a.
> > >
> > > >$ cd /usr/ports/print/cups-pdf
> > > >$ make
> > > >===> cups-pdf-2.5.0 is marked as broken: does not install.
> > > >*** Error code 1
> > >
> > > >Stop in /usr/local/ports/print/cups-pdf.
> > >
> > >
> > > >$ portmaster .
> > > >===>>> Port directory: /usr/ports/print/cups-pdf
> > > > ===>>> This port is marked BROKEN
> > > > ===>>> does not install
> > >
> > > > ===>>> If you are sure you can build it, remove the
> > > > BROKEN line in the Makefile and try again.
> > >
> > >
> > > >hth,
> > >
> > > >Doug
> > >
> > > >PS, Josh, if this e-mail address still works for you, howdy! :)
> >

> > I am wondering what changes have taken place to change this from a
> > functioning port to one that justifies it being labelled as broken. It
> > must have compiled OK for me as I already have cups-pdf-2.5.0 installed
> > which appears to be the same version. I heard some rumour that it was
> > failing on ubuntu but not on freebsd. Is there any truth in that?
> >

> > Is there any provision to ensure that something which should be marked as
> > broken for ubuntu is not, in consequence,automatically marked as broken
> > when on freebsd?
> >
> > dns1# pkg_info |grep cups
> > cups-base-1.4.2_3 Common UNIX Printing System: Server
> > cups-client-1.4.2_3 Common UNIX Printing System: Library cups
> > cups-image-1.4.2_3 Common UNIX Printing System: Library cupsimage
> > cups-pdf-2.5.0 A virtual printer for CUPS to produce PDF files
> > cups-pstoraster-8.15.4_4 Postscript interpreter for CUPS printing to
> > non-PS printers
> > cups-samba-6.0_2 The Common UNIX Printing System: MS Windows client
> > drivers
> > cups-smb-backend-1.0_2 A CUPS backend for printing to Windows servers
> > gnome-cups-manager-0.31_10,1 Admistration tool for cups
> > gutenprint-cups-5.2.4 GutenPrint Printer Driver
> > libgnomecups-0.2.3_2,1 Support library for gnome cups admistration
> > py26-cups-1.9.46 CUPS bindings for Python
> > dns1#
>

>> Strange, but you can try to figure out what happening at pointyhat:
>> http://people.freebsd.org/~fenner/errorlogs/si...@olofsson.de-date.html
>
>>Maybe it was failing for pointhat - but certainly did not fail on my
Freebsd
>>p3 amd64 (Intel Quad core). It was after I upgraded to 2.5.0 that it was
>>labelled as broken.

>>I have removed the Broke line from Makefile. It compiles without compalining
>>but I have not tried to deinstall/reinstall in case I break the appl.

>>Comments please?

> Just answering about urlview: a patch is included in PR ports/141148

>
> <http://www.freebsd.org/cgi/query-pr.cgi?pr=141148>
>
> Feel free to apply it!
>
> Regards,
>

Thanks Th
Thats great - so urlview solved -- anyone able to solve the anomalies on cups-
pdf?
David

[David Southwell]

> Looks like the problem would have been fixed in PR ports/141375, which
> modified the cups-base port to create the directory in question. As that
> fix was applied on the 12th at 19:39 and the last pointyhat test on
> cups-pdf appears to have been on the same day at 20:57 I reckon pointyhat
> just missed getting the fix for at least one of its test cases by about ><
> that much.
>
> Cheers,
>
> Matthew
>
Well spotted Mathew! So can anyone test it out afresh on pointyhat and commit
as appropriate?

Thanks David

[Doug Barton]

David Southwell wrote:
>>>> ===> cups-pdf-2.5.0 is marked as broken: does not install.

> I have removed the Broke line from Makefile. It compiles without compalining

Why do you think the fact that it compiles is relevant? :)

Doug

[David Southwell]

> > Looks like all the PR's were not in place before the test was run on
> > pointyhat.
>
> pointyhat doesn't have anything to do with PRs. It runs based on what
> is checked into CVS when its runs start. How would it be able to do
> otherwise? The ports PR count is currently 998. How is a computer
> program going to know which ones are relevant or correct?
>
> > I deduced from the information on my system that the error was more
> > likely due to a false positive for failure by the testing procedure
> > rather than due to an inherent failure in the code.
>
> build error != install error. If you look at the two error logs, you'll
> see that those are install errors (files required to be installed not
> installed; files required to be deinstalled not being deinstalled).
>
> Ports that do not allow a clean install/deinstall cycle are broken,
> whether they compile or not.
>
> mcl
>
Yes I agree BUT it is suggested that the reason that there was not a clean
install/deinstall cycle was because the pointyhat test may have been done
without the benefit of PR ports 141375. Here is Mathew Seaman's take on it:

"Looks like the problem would have been fixed in PR ports/141375, which
modified
the cups-base port to create the directory in question. As that fix was
applied
on the 12th at 19:39 and the last pointyhat test on cups-pdf appears to have
been
on the same day at 20:57 I reckon pointyhat just missed getting the fix for at
least one of its test cases by about >< that much."

What we need now is another test on pointyhat to see whether his speculation
is accurate. It seems highly probable to me.

Time will tell

David

[David Southwell]

> _______________________________________________
Well that was it! Compiles and installs when the Makefile is amended. So the
pointy hat run must have started before the fix was applied even though the
test was done after. I suppose the only thing that could prevent similar
"false positives for failure" would be for the pointy hat test cycle to
include a second check on failures after the run ends to pick up any fixes
which had been applied between the start of the run and any individual test.
However this is probably such a rare occurence that the effort to amend the
procedure may not be justified. It is a useful reminder that pointyhat
failures can, under such restricted circumstances, be misleading. Mind you I
would prefer a few extra "false failures" than one "false passes"!!

David