#706 closed Feature Request (invalid)

EasyPBI fails (en-freebsd-doc and de-freebsd-doc)

Reported by: mjollnirpaul Owned by:
Priority: major Milestone:
Component: System Configuration Version:
Keywords: Cc: trac-bugs@…

Description

I could not download these as packages with portinstall (??? that's a bad joke) and compiling them from source was a (big) pain, because I had to change PACKAGESITE to use 9-stable (not 9.1-release) manually -- took me a day to find why and how -- and now freebsd-update -IDS says the whole system is out-of-date. You guessed right that I'm not going to update myself and rely on your update-manager. At least I could update the packages shown by portaudit (incl. flashplayer but except for ruby). Plus, these two ports (the docs) are not tender maintained, they depend on chinese fonts (that fail by default and take a lot of attention, seems to be a typical chinese mannerism) although I found no single chinese character in dem docs, man.

=> Current PC-BSD 9.x shall include a "Release Notes.txt" on the desktop and the root fs telling about the hacking of FreeBSD sites in late 2012 and what to do to use packages & ports.
=> PC-BSD update-manager shall use portaudit internally and update affected ports -- if possible, use packages, if not, try unattended port build.
=> A local-only MTA shall be enabled by default.

Ok the target audience of PC-BSD is the average non-nerd user, I agree w/ that completely, but I guess in realitas it is mostly people already familiar w/ Unix coming from Linux, Solaris, or Mac, or other nerds coming from Windows who like to try BSD. So IMHO the freebsd-doc shall be easily available as packages (not ports) in all translations (split, not all bundled).

Then I started EasyPBI to supply the two ports as PBI. It failed. Several questions rise up:

I already have a freebsd base system (mostly unchanged) and the src tree (unchanged), why does EasyPBI download them again?
=> It would be enough to create a snapshot after/during install (I did that manually from within an xterm when the installer prompted me to reboot) that's a good idea anyway because newbies can quickly start over w/ a fresh system after they shot themselfes in the foot.
=> The same hold true after downloading & extracting src tree.

I already built and installed these ports, why does EasyPBI do all that again? It's PDFs and text files that can be copied!
=> EasyPBI needs to look of what type and where the target files are.

How can I make architecture-independant packages and PBIs? I'm definetely not going to do that again for all architectures, it's only data that can be copied. All we have to agree upon is that all-arch packages/PBIs be delivered in network byte order and what to do w/ that is left up to the arch.

Then it builds a pre-desktop default system: compile Perl, CUPS, Xorg, TeX etc. pp. -- hopefully this will be saved for the next PBI (why do I need CUPS to create a PDF? I thought GS is enough for that).
=> If EasyPBI does not save reasonable common stages: it should ask me where to save stages that I might need again and let me start there next time.
=> Common stages e.g. X11, KDE, LXDE,... could be availabe for download.

Maybe that's all a GIGO-problem, because the ports Makefiles are not maintained well (stale or broken dependencies as above, from copy&paste blindly).

After all, it takes hours (days?) to make a PBI of files that should be available for download as precompiled package(s), which is not anyone's mistake, but the status quo. Anyway, to say it polite, that's sub-optimal.
--
Qt conversation started.
Qt conversation finished.
Getting regional mirror...
Using mirror: http://www.mirrorservice.org/pub/pcbsd
Fetching FreeBSD chroot environment... This may take a while...
rel-amd64.txz

91 MB 1501 kBps

rel-amd64.md5 33 B 466 kBps
src-amd64.txz

92 MB 1104 kBps

Creating ZFS /usr/pbi/.pbi-world-amd64 dataset...
Extracting rel-amd64.txz...
Extracting src-amd64.txz...
Cloning /usr/pbi/.pbi-world-amd64 -> /usr/pbi/freebsddocumentation(english)-amd64.chroot
cannot create 'tank0/usr/pbi/freebsddocumentation(english)-amd64.chroot': invalid character '(' in name
pbi_makeport: Failed creating clean ZFS base snapshot
Cleaning /usr/pbi/freebsddocumentation(english)-amd64.chroot

Change History (2)

comment:1 Changed 21 months ago by mjollnirpaul

/usr/pbi/freebsddocumentation-english-amd64/bin/dvips -o article.ps article.dvi
This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com)
/usr/pbi/freebsddocumentation-english-amd64/bin/dvips: ! DVI file can't be opened.
* [article.ps] Error code 1

Stop in /usr/wrkdirprefix/usr/ports/misc/freebsd-doc-en/work/doc/en_US.ISO8859-1/articles/building-products.
* [all] Error code 1

Stop in /usr/wrkdirprefix/usr/ports/misc/freebsd-doc-en/work/doc/en_US.ISO8859-1/articles.
* [all] Error code 1

Stop in /usr/wrkdirprefix/usr/ports/misc/freebsd-doc-en/work/doc/en_US.ISO8859-1.
* [all] Error code 1

Stop in /usr/wrkdirprefix/usr/ports/misc/freebsd-doc-en/work/doc.
* [do-build] Error code 1

Stop in /usr/ports/misc/freebsd-doc-en.
===> Cleaning for en-freebsd-doc-40771_1,1
pbi_makeport_chroot: make install of misc/freebsd-doc-en/ failed!
Cleaning /usr/pbi/freebsddocumentation-english-amd64.chroot

comment:2 Changed 21 months ago by kenmoore

  • Resolution set to invalid
  • Status changed from new to closed

First, if you expect to get answers to general questions, you need to ask the questions on either the PC-BSD mailing lists or on the PC-BSD Forums. This is just a place for reporting and tracking bugs.

It sounds like you are simply confused by what the PBI format is and how it is used. I would recommend reading through some of the documentation on the PBI format. If you are still confused after that, I would be glad to talk to you about it on the forums.

As to the error that you posted at the bottom of your report, special characters (such as parentheses) are not allowed as part of the application name for a PBI.

The updated error that you posted looks like you simply have the command mis-typed, I think the article.dvi file needs to come before the article.ps file in the command (since it says that "article.ps" is not a dvi file).

Note: See TracTickets for help on using tickets.