Problem with clamav-0.90.1_1
Hi, The latest version has a bug in the clamav-clamd.sh and clamav-freshclam.sh files. It does not contain the prefix /usr/local when calling rc.subr. The previous versions always had this right. Regards, Nicki ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Current unassigned ports problem reports
Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems Serious problems S Tracker Resp. Description o ports/106369vpnd caused kernel panic with ppp mode o ports/106372vpnd can't run with slip mode o ports/107229sysutils/coreutils: gcp fails to set default ACL which o ports/107536editors/scite: Can't write on SciTE text editor f ports/108077www/linux-flashplugin9 crashes linux-firefox f ports/108105building biology/platon fails. f ports/108413net/vnc does not works. f ports/108537print/hplip: Build failure f ports/108543math/R (R-2.4.0/R-2.4.1) won't upgrade/install on f ports/108606Courier MTA terminates abnormaly after installation f ports/108748mod_fcgid 1.10 does not work inside jail f ports/109160net/samba3 crashes freebsd when accessing a share resi f ports/109422sysutils/gnomebaker-0.6.1: could not find signal handl f ports/110027DOS in silc-server, update available f ports/110035Port fix for sysutils/be_agent o ports/110224Address change for SPAMCOP in 'spamcup.pl' o ports/110382New port: x11/oooqs2 - OpenOffice 2.x quickstarter for f ports/110454Joomla port Makefile has incorrect url for package 18 problems total. Non-critical problems S Tracker Resp. Description s ports/59254 ports that write something after bsd.port.mk f ports/94073 [NEW PORTS] x11-toolkits/libsmokeqt, x11-toolkits/libs f ports/94074 [NEW PORTS] x11-toolkits/ruby-qt3, x11-toolkits/kde3: f ports/95990 New Port: emulators/xjoypad s ports/96731 textproc/docbook-utils doesn`t build f ports/100650audio/moc dumps core when detach/quit o ports/100896[new ports] emulators/vmware-server-guestd1 emulators/ f ports/102093new port (restoring from Attic): fix games/myth2_demo o ports/103395security/gnome-ssh-askpass interferes with gnome-scree f ports/105473ports/sysutils/cpdup -o doesn't work as advertised f ports/107267[new port] science/dcmtk -- DICOM toolkit o ports/107354net/icmpinfo: icmpinfo -vvv does not recocnize any ICM f ports/107368audio/normalize: [patch] - normalize-mp3 and normalize f ports/107621net/proxychains doens't compile on 4 and 5 f ports/107937jailed net/isc-dhcp3-server wouldn't run with an immut f ports/108021New Port : gpsim Microchip(t) PIC emulator f ports/108104print/hplip: documentation gets installed though NOPOR f ports/108115new port: devel/pstreams: C++ utility for simple IOStr o ports/108595pstree (sysutils/psmisc) don't work in jail f ports/108723kxgenerator never worked for me f ports/108788[patch] sysutils/fusefs-kmod: Add BASE option f ports/108801www/mod_perl2: Apache-2.0.59 / mod_perl-2-2.0.3_1 freq f ports/108853Contradiction of CONFLICTS¡¡ f ports/109041security/tinyca doesn't allow for user installed OpenS f ports/109045security/xca compile fails: x509rev.cpp:63: error: inv f ports/109231update sysutils/fusefs-wdfs to new version o ports/109344restore .svn support to security/metasploit-devel f ports/109432[Update Version] x11-toolkits/tktable to 2.9 f ports/109535Eggdrop SSL error f ports/109609security/ca-roots
Re: SoC application: please comment!
What I'd like to see added, is a flag, which would cause bsd.port.mk to simply ignore the explicit shared libraries' major numbers in LIB_DEPENDS. In almost all cases requiring a specific number does not make sense (not from a user's point of view, anyway). It only causes unneccessary rebuilds: * install mplayer, which uses libFOO.X * wait a week * update the ports-tree * try to install vlc -- oops, because of the shlib number bump of libFOO, got to rebuild the libFOO and the mplayer, which uses it. Of course, vlc would use libFOO.X just as well libFOO.X+1 -- in almost all cases. So there is no point in _forcing_ the user to rebuild all that... The proposed knob would allow the users to ignore the numbers. I hope, of course, that the flag will, eventually, become default... -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems running pkgdb -fF
Running pkgdb -Ff today gives me the following error: Stale origin: 'multimedia/totem-gstreamer': perhaps moved or obsoleted. - The port 'multimedia/totem-gstreamer' was moved to 'multimedia/totem' on 2007-03-19 because: multimedia/totem now uses gstreamer by default sed: 1: s|^\(@comment[: unbalanced brackets ([]) Failed to rewrite /var/db/pkg/totem-gstreamer-2.16.5/+CONTENTS: Command failed [exit code 1]: sed \s|^(@comment[\ \\ \][\ \\ \]*ORIGIN:).*\\\$|1multimedia/totem|\ /var/db/pkg/totem-gstreamer-2.16.5/+CONTENTS /tmp/+CONTENTS.71426.0 This is with portupgrade 2.2.6_2,2 on both 6-STABLE i386 and 7-CURRENT amd64. I don't think I did anything funky with the totem MOVED entry. This seems to be a problem with pkgdb. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
FreeBSD Port: hk_classes-0.8.1
Hi, After upgrading to knoda and hk_classes 0.8.1 on FreeBSD 6.2 and KDE 3.5.5, I'm having some problems. The iconv library installed doesn't support 'WCHAR_T' which is causing problems when any report is rendered in knoda. The installed iconv library version is 1.9.2. This library is directly referenced in the port requirements of hk_classes and knoda, yet it doesn't support the 'WCHAR_T' character set and I can't believe no one else hasn't had any issues like this. I'm at a dead end so far and I need to get knoda working properly. Is there anything (please, I'm begging) that anyone can suggest that I try. I'm at my wits end. Nearly desperate, Eric [EMAIL PROTECTED] P.S. You wouldn't want me to be forced to switch to Microsoft Access would you? That may be my only recourse. Another round lost for the open source community. :-) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems running pkgdb -fF
multimedia/totem now uses gstreamer by default sed: 1: s|^\(@comment[: unbalanced brackets ([]) Perhaps there is a specific problem here, but i have observed corruption under FreeBSD-6.2. Several times on my laptop where various applications suddenly misbehave, rebooting cures that, but once firefox was corrupted and i had to reinstall it. Since it has several experimental drivers i can perhaps blame them. But once i have found completely corrupted +CONTENTS files on my desktop which has supported hardware. The corrupted entry was flagged by my check_pkg.py first time i used it on /var/db/pkg. Of course this is the sort of thing absolutely impossible to characterize. -- Michel TALON ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems running pkgdb -fF
On Mon, Mar 19, 2007 at 02:52:21PM -0400 I heard the voice of Joe Marcus Clarke, and lo! it spake thus: sed: 1: s|^\(@comment[: unbalanced brackets ([]) Failed to rewrite /var/db/pkg/totem-gstreamer-2.16.5/+CONTENTS: Command failed [exit code 1]: sed \s|^(@comment[\ \\ \][\ \\ \]*ORIGIN:).*\\\$|1multimedia/totem|\ /var/db/pkg/totem-gstreamer-2.16.5/+CONTENTS /tmp/+CONTENTS.71426.0 FWIW, I saw this happen on one or two boxes a week or two ago. Couldn't make heads or tales of where it was coming from, but manually reinstalling the port in question made it go away, so I just mentally filed it away. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems running pkgdb -fF
in message [EMAIL PROTECTED],
wrote Joe Marcus Clarke thusly...
Running pkgdb -Ff today gives me the following error:
Stale origin: 'multimedia/totem-gstreamer': perhaps moved or obsoleted.
- The port 'multimedia/totem-gstreamer' was moved to 'multimedia/totem' on
2007-03-19 because:
multimedia/totem now uses gstreamer by default
sed: 1: s|^\(@comment[: unbalanced brackets ([])
Failed to rewrite /var/db/pkg/totem-gstreamer-2.16.5/+CONTENTS: Command
failed [exit code 1]: sed \s|^(@comment[\ \\ \][\ \\
\]*ORIGIN:).*\\\$|1multimedia/totem|\
/var/db/pkg/totem-gstreamer-2.16.5/+CONTENTS /tmp/+CONTENTS.71426.0
This is with portupgrade 2.2.6_2,2 on both 6-STABLE i386 and
7-CURRENT amd64. I don't think I did anything funky with the
totem MOVED entry. This seems to be a problem with pkgdb.
Looks like sed command gets broken on unescaped|uncared-for otherwise
important space character. The command is being made in
modify_origin() in pkgtools.rb ...
792 if grep_q_file(/[EMAIL PROTECTED] \t]+ORIGIN:/, contents_file)
793 command = shelljoin('sed',
794 s|^\\(@comment[ \t][ \t]*ORIGIN:\\).*$|\\1#{origin}|)
795 else
796 command = (cat; echo '@comment ORIGIN:#{origin}')
797 end
798
799 filter_file(command, contents_file)
... which is being executed in filter_file() ...
838 xsystem(#{command} #{file} #{tmpfile})
Here is minimized case which causes above problem ...
# for shelljoin()
require pkgmisc
origin = 'some/where'
file = '/tmp/in-file'
tmpfile = '/tmp/out-file'
cmd = shelljoin('sed', s|^\\(@comment[ \t][ \t]*ORIGIN:\\).*$|\\1#{origin}|)
system(#{cmd} #{file} #{tmpfile})
Perhaps another version of shelljoin() is needed specifically tuned
for sed. I myself would do the substitution in Ruby itself, or failing
that in Perl or awk.
- Parv
--
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports management tools in the base (Was: Re: cvs commit: www/en/projects/ideas ideas.xml)
Pav Lucistnik wrote: Alexander Leidinger píše v po 19. 03. 2007 v 12:51 +0100: Quoting Pav Lucistnik [EMAIL PROTECTED] (from Sun, 18 Mar 2007 16:38:50 + (UTC)): pav 2007-03-18 16:38:50 UTC FreeBSD doc repository Modified files: en/projects/ideasideas.xml Log: Add four new ports related entries: 4) portupgrade in base thing Isn't portmaster something which would fit here already? I didn't looked at it, I just judge from what I did read in the lists. Possibly. But it still isn't either finished or in base. This thread started with the ideas page entry here: http://www.freebsd.org/projects/ideas/index.html#p-ports-upgrade In response to Pav's suggestion above, I haven't put portmaster in the base for a few reasons, the most important one of which is that my feeling is that the only ports related tool that should be in the base is pkg_add. I think that the rest of them should be ports themselves, which not only is cleaner architecturally, but also has a lot of advantages when it comes to things like adding new features to them. Another reason, for whatever it's worth, is that up till now no one has suggested that it go into the base (which is fine with me). As for it not being finished, is any software project ever really finished? :) I'm pretty close to the end of the list of features that I was ever interested in implementing, and I've added almost every feature that users have asked for (with the notable exception of installing packages). So I would classify the project as mature, and if there is clamor for it to go into the base, I would be willing to do so. That said, I would have a great deal of concern over the idea of having something that implemented a lot of portupgrade's features in the base. I say this with all due respect to sem, and everyone else who's been involved in the development of portupgrade. I think it's a fine tool, and I am all for the idea of people developing and using tools that meet their interest and needs. I have never viewed portmaster as a competitor of portupgrade, and indeed I've said many times that it's not even on my radar to be working on a portupgrade replacement. My concern is related to the idea of having such a tool in the base dramatically expanding the complexity of the ports infrastructure beyond what it is already. Personally I've noticed a lot of additional complexity that has been added since portupgrade first starting becoming popular, and my gut feeling is that a lot of things are done with the rationale oh, they can just use portupgrade to fix things up after I'm done. If we want to re-architect the ports system so that it _requires_ some sort of database other than /var/db/pkg, fine. Let's have that discussion (which I realize would be the nightmare bikeshed from hell), but let's not back into it by adding a portupgrade-like tool to the base which becomes mandatory inch by inch. As for the requirements in the ideas page ... The required functionality is: * fixing @pkgdep records in +CONTENTS file * fixing +REQUIRED_BY records Portmaster already does these two, and that part of the code is very mature since it's one of the first features I wanted for myself when I started developing it. * storing old copies of shared libraries after shmajor number change in /usr/local/lib/compat/pkg Portmaster doesn't do this currently. I have mixed feelings about whether this is even a good idea or not. I'd be happy to elaborate on why if anyone cares. * upwards and downwards recursive modes If I understand you correctly, what portmaster does currently when building a port (a depth-first traversal of the dependency tree) would be considered downwardly recursive, and the -r function (ala portupgrade's) might be considered upwardly recursive, but I'm not 100% sure I'm right here. :) I think one meta-requirement that is implied on the web page but not stated is that the tool not rely on any features that don't already exist in the base. Since portmaster is written in /bin/sh, and doesn't rely on any databases to do its work, it meets that requirement. Now having said all that, I still want to reiterate my point that I feel the conversation we _should_ be having is moving all the ports/package management tools other than pkg_add into the ports tree, but if people are determined to put a port management tool into the base, then yes, I'd like portmaster to be considered for that role. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports management tools in the base (Was: Re: cvs commit: www/en/projects/ideas ideas.xml)
Doug Barton píše v po 19. 03. 2007 v 17:25 -0700: Pav Lucistnik wrote: Alexander Leidinger píše v po 19. 03. 2007 v 12:51 +0100: Quoting Pav Lucistnik [EMAIL PROTECTED] (from Sun, 18 Mar 2007 16:38:50 + (UTC)): pav 2007-03-18 16:38:50 UTC FreeBSD doc repository Modified files: en/projects/ideasideas.xml Log: Add four new ports related entries: 4) portupgrade in base thing Isn't portmaster something which would fit here already? I didn't looked at it, I just judge from what I did read in the lists. Possibly. But it still isn't either finished or in base. This thread started with the ideas page entry here: http://www.freebsd.org/projects/ideas/index.html#p-ports-upgrade I haven't put portmaster in the base for a few reasons, the most important one of which is that my feeling is that the only ports related tool that should be in the base is pkg_add. I think that the rest of them should be ports themselves, which not only is cleaner architecturally, but also has a lot of advantages when it comes to things like adding new features to them. My point of view is that the essential ports/package functionality should be contained in the base system in the moment the sysinstall or make installworld finishes it's job. I consider smooth upgrading of installed packages a part of essential functionality. If you're worried about the version embedded into a release being imposed on users for next two years, well, there's always possibility to pull a newer version of portmaster from port and install it on older systems automatically. It has been done with pkg_install suite in the past. So I would classify the project as mature, Great. I was tracking your development lately, so it's good to hear that. I should try portmaster again soonish. As for the requirements in the ideas page ... * storing old copies of shared libraries after shmajor number change in /usr/local/lib/compat/pkg Portmaster doesn't do this currently. I have mixed feelings about whether this is even a good idea or not. I'd be happy to elaborate on why if anyone cares. I find this a massively desirable feature to have. Defaults to on, can be turned off. It essentially allows people to upgrade gettext to 0.16.1 and don't worry. An acompanying utility which would try to prune /usr/local/lib/compat/pkg, rebuilding binaries that link these old libs, and ultimately deleting the libs, would be nice. I have something locally, but it's a gross hack. * upwards and downwards recursive modes If I understand you correctly, what portmaster does currently when building a port (a depth-first traversal of the dependency tree) would be considered downwardly recursive, and the -r function (ala portupgrade's) might be considered upwardly recursive, but I'm not 100% sure I'm right here. :) You understood it 100%. I think one meta-requirement that is implied on the web page but not stated is that the tool not rely on any features that don't already exist in the base. Since portmaster is written in /bin/sh, and doesn't rely on any databases to do its work, it meets that requirement. Yes, that's kinda understood that anything in base must be fully operational with only the resources available in base. -- Pav Lucistnik [EMAIL PROTECTED] [EMAIL PROTECTED] Canada is a country whose main exports are hockey players and cold fronts. Our main imports are baseball players and acid rain. -- Pierre Elliott Trudeau signature.asc Description: Toto je digitálně podepsaná část zprávy
[REMINDER] how to get the best use out of GNATS
Recently the bugbusting team has been seeing a few cases where PRs are being submitted without a clear understanding of how best to do so. Although there is a document that references this*, please let me reiterate a few points: - Please only send one PR for a particular problem. The mail queue and spam filtering take ~10 minutes to run (more if your address is greylisted) so you will not see an immediate email reply or update on the website. Please wait a few hours before assuming that something has gone wrong; if you think it has, please email bugmeister@ and we will look at it. - Your email address has to have a valid reverse lookup to be accepted. If the machine you are submitting from does not have this, please acquire and use a free email account such as [EMAIL PROTECTED] - Your email address will be public (in the database). If you do not want this, please use a free email account. - If your email bounces, it is much less likely that someone is going to be able to contact you if they need futher information about your problem. - Please trim replies when following-up. The database already has a copy. - Please do not use HTML mail. The GNATS spam-filters are set up to assume that such mail is spam. They are almost always correct. - Do not use content-type/quoted-printable. This will merely scramble your patches into unusability. - Remember, your submissions are going into a database, so any email mangling is undesireable. - Submissions of more than 500k are quarantined as possible spam. If your patch (or traceback) are that large, please consider posting them somewhere on the web and just submitting a URL. - The category for all ports is 'ports', not 'www' if your port is 'www/foo', nor 'misc' if your port is 'misc/bar'. This affects the automated systems that assign and track PRs. - In fact, the 'misc' category is almost always wrong. Its only legitimate uses are for a few things such as build infrastructure and boot loader code. If your problem is with the base system, it is almost certainly either kern or bin (unless you think it is particular to a processor or motherboard, in which case it is i386/amd64/etc.). Thanks. Mark Linimon, for the bugbusting team *http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
