Re: Python 2.7 removal outline

[RW via freebsd-ports]

On Fri, 26 Mar 2021 13:55:33 +1100 (EST)
Dave Horsfall wrote:

> On Thu, 25 Mar 2021, George Mitchell wrote:
> 
> >> [...] it is really not for everybody to use overlays in current
> >> state (overlays are poor documented at least). [...]  
> >
> > Until this thread I had never heard of them.  --
> > George  
> 
> I can't remember the last time I used overlays (certainly with CP/M);
> I didn't know that FreeBSD even supported them (why bother when
> you've got VM?).

I doubt that meaning of overlay is going to be relevant. I'd not heard
of it either, but from looking in ports/Mk/ it seems to be a way of
modifying port builds.
___
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: bogus warning from pkg

[RW via freebsd-ports]

On Mon, 15 Feb 2021 12:39:13 -0800
Steve Kargl wrote:


> BTW, there is no documentation as what 'pkg bootstrap -f'
> does.  In particular, the -f option is no described.
> 
>From pkg(8) (in 12.2):

 bootstrap
 This is for compatibility with the pkg(7) bootstrapper.
 If pkg is already installed, nothing is done.

 If invoked with the -f flag an attempt will be made to
 reinstall pkg from remote repository.


>From pkg(7)

 pkg bootstrap [-f]
Attempt to bootstrap and do not forward anything to
pkg(8) after it is installed.  If the -f flag is
specified, then pkg(8) will be fetched and installed
regardless if it is already installed.
___
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: portsnap

[RW via freebsd-ports]

On Wed, 30 Dec 2020 11:02:55 -0700
Edward Sanford Sutton, III wrote:


> portsnap is a shell script where fetch is used for downloads.

It uses fetch for some things, but fetching the actual updates uses
phttpget(8) which supports pipelined HTTP requests. 

___
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: [HEADS UP] Planned deprecation of portsnap

[RW via freebsd-ports]

On Sun, 9 Aug 2020 16:43:28 +0100
Matthew Seaman wrote:

> On 09/08/2020 07:03, Stefan Ehmann wrote:
> > I usually run `pkg version` to see what packages have changed.
> > 
> > Previously, that was a more or less instant operation, now it takes
> > over 100 seconds. The problem is that /usr/ports/INDEX-12 is
> > missing.  
> 
> Yes.  For historical reason, the order of precedence for the source of
> information about available packages that pkg(8) uses is:
> 
>* INDEX file
>* A checked-out copy of /usr/ports
>* The pkg repository catalogue
> 
> In my humble opinion, it's the third of those options that is actually
> the best, both in terms of speed and accuracy. 

Inaccurate because the ports tree used to create the packages is
typically a bit behind the current tree.

What I'd like to see is a simple way to update the ports tree to match
what was used to build the current packages in the repository. 

If you update most packages using pkg, but build a few locally, the
difference in tree versions can cause problems.

___
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: cad/gmsh port

[RW via freebsd-ports]

On Thu, 12 Mar 2020 16:19:20 +
Montgomery-Smith, Stephen wrote:


> For some reason fetch freezes when the ports tries to build cad/gmsh. 
> But if I download the tarball via my web browser, it works.  

It also happens with wget and curl. What's particularly odd is that
fetch took 2 hours to time out.
___
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: Aria2 and magnets

[RW via freebsd-ports]

On Wed, 4 Mar 2020 17:19:06 -0700
@lbutlr wrote:

> Brand new install of aria2 and I tried to grab the FreBSD 12.1 amd64
> image via a magnet link:
...
> After about 30 minutes the only thing I get is updates showing 0
> Bytes downloaded.
...
> 
> Downloading a torrent file, in this case Ubuntu server, works fine:

Perhaps DHT is blocked in your firewall. It's also worth rechecking the
magnet link in case the Ubuntu download bootstrapped DHT.
___
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: good gui bit-torrent client?

[RW via freebsd-ports]

On Fri, 28 Feb 2020 18:49:02 -0500
Robert Huff wrote:

>   I used to use azureus/vuze, but it hasn't been maintained is
> quite a while.

I used azureus a long time ago, and liked it, but IIRC at the time it
didn't scale very well when managing many torrents and its java
dependencies were a pain.

I tried several clients a few years ago and the one I liked best was
qBittorrent. It also was the one that was most like azureus.
___
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: MariaDB 10.3.17

[RW via freebsd-ports]

On Sun, 4 Aug 2019 13:00:52 -0600
The Doctor wrote:

> MariaDB 10.3.17 is out?
> 
> Who is supposed to be looking after this port?
> 

  cd /usr/ports//
  make maintainer
___
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: Spamassassin/GeoIP2

[RW via freebsd-ports]

On Sat, 9 Mar 2019 16:52:01 +0100
Xavier wrote:

> Hello,
> 
> Since GeoIP is deprecated, I installed GeoIP2 instead.
> 
> Now, sa-update fails with> plugin: failed to parse plugin (from @INC):
> Bareword "GEOIP_MEMORY_CACHE"...

GeoIP2 does require extra configuration. You need to download a
database file and set:

country_db_type  GeoIP2
country_db_path  

If you don't do that, or something goes wrong, the RelayCountry plugin
tries to use GeoIP instead.
___
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"

nvidia-driver failed after 11.1 to 11.2 update

[RW via freebsd-ports]

I recently updated from 11.1 to 11.2 and the nvidia-driver failed to
initialize afterwards. Switching from 'quarterly' to 'latest'  didn't
help, but reinstalling from the port fixed it. 

Perhaps the 'latest' version needs to be rebuilt against a newer
kernel, or have I done something strange?
___
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: RUN_DEPENDS and portmaster

[RW via freebsd-ports]

On Wed, 19 Sep 2018 14:14:42 +0200 (CEST)
Marco Beishuizen wrote:

> On Wed, 19 Sep 2018, the wise Thomas Mueller wrote:
> 
> > This discussion of portmaster prompts me to ask, what is the status
> > of portupgrade?
> >
> > I used portupgrade at first but subsequently switched to
> > portmaster.  
> 
> I still use portupgrade daily and it works fine. 

I presume that's because you use a restricted set of packages. Without
flavor support portupgrade can't always get the port directory from the
origin.


> Afaik the maintainer
> is adding support for flavors into portupgrade but I don't know the
> status of it:
> 
> https://lists.freebsd.org/pipermail/freebsd-ports/2017-December/111445.html

That said "in the next few weeks" last year. 
___
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: Cannot specify ntpd binary in ports with ntpd startup file.

[RW via freebsd-ports]

On Tue, 28 Aug 2018 17:34:08 -0700 (PDT)
Dan Mahoney (Gushi) wrote:

> 1) Got the version wrong.  I'm on 10.4.
> 
> 2) Forgot a subject.  Whoops.
> 
> 3) Forgot to cc maintainer.  Doh!
> 
> -Dan
> 
> On Tue, 28 Aug 2018, Dan Mahoney (Gushi) wrote:
> 
> > Hey all,
> >
> > Funny question.  I'm on FreeBSD 11.4, and would like to use the
> > latest version of NTP, which is in pkg.

If you mean opennntp, that's not a later version, it's a different
implementation.

> > The version in pkg doesn't have a startup script, which I'm not
> > sure is supposed to be the case. 

My ports tree is a bit out of date, but it does appear to have a
startup script. Where you looking in /usr/local/etc/rc.d/?

___
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: portsnap not honoring WORKDIR and PORTSDIR?

[RW via freebsd-ports]

On Sat, 21 Apr 2018 16:49:13 -0600
Gary Aitken wrote:

> Is portsnap supposed to honor WORKDIR and PORTSDIR?
> 
> These are defined in /etc/portsnap.conf, and it's not clear to me
> whether they are honored only via the .conf file or whether they
> are supposed to be honored from the environment as well.
> 
> They appear to not be honored from the environment, and I'm wondering
> whether that is deliberate or an oversight that should be corrected.
> 


It's deliberate:


# Initialize parameters to null, just in case they're
# set in the environment.
init_params() {
KEYPRINT=""
EXTRACTPATH=""
WORKDIR=""
PORTSDIR=""
...

___
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: Suggesting new virtual categories: physics and chemistry

[RW via freebsd-ports]

On Thu, 14 Dec 2017 08:47:38 -0800
Yuri wrote:

> Some ports naturally fall under these categories:
> 
> https://reviews.freebsd.org/D13481

Science isn't particularly large:


$ for d in `make -V SUBDIR` ;do  echo  "`find $d/ -maxdepth 1 -type d
|wc -l`  $d"   ;done  |sort -n | tail -n 30
 179  converters
 191  emulators
 195  x11-fonts
 196  science
 199  net-im
 209  comms
 222  dns
 248  archivers
 253  editors
 269  print
 283  deskutils
 295  x11-toolkits
 301  japanese
 362  lang
 391  net-mgmt
 459  multimedia
 513  misc
 535  x11
 749  mail
 754  math
 895  audio
1044  databases
1120  graphics
1200  games
1274  security
1364  sysutils
1481  net
1810  textproc
2543  www
6105  devel
___
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: Flavor part of package origin?

[RW via freebsd-ports]

On Mon, 11 Dec 2017 14:38:59 +0100
Mathieu Arnold wrote:

> Le 11/12/2017 à 10:12, Stefan Esser a écrit :
> > $ pkg info -o '*setuptools*'
> > py27-setuptools-36.5.0 devel/py-setuptools@py27
> > py36-setuptools-36.5.0 devel/py-setuptools@py36  
> 
> 
> I really do not like the look of this. The origin always has been a
> directory name, with this change, it would become some abstract thing.

It's not all that abstract if you can simply strip the end part off. 
___
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: Procmail Vulnerabilities check

[RW via freebsd-ports]

On Sun, 10 Dec 2017 10:10:30 -0800
Kevin Oberman wrote:


> Strongly agree! Support ofr some basics like .forward is really a
> requirement. It is used for too many "normal" mail operations
> including private dropmail or procmail setups as well as forwarding
> to a smartmail system.

This is actually an argument for taking sendmail out of the base system.
If you need to install dropmail or procmail as a package you might
just as well install an MTA in the same way. 
___
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: Bogofilter contrib scripts treated as docs

[RW via freebsd-ports]

On Thu, 9 Nov 2017 23:12:48 +0100
Matthias Andree wrote:

> Am 06.11.2017 um 20:19 schrieb RW:
> > 
> > I just noticed that the bogofilter perl and shell scripts from the
> > contrib directory (see below) only get installed if bogofilter is
> > built with the DOCS option.
> > 
> > 
> > .for i in bfproxy.pl bogofilter-milter.pl bogo.R bogofilter-qfe.sh \
> >mime.get.rfc822.pl parmtest.sh printmaildir.pl \
> >bogominitrain.pl \
> >randomtrain.sh scramble.sh spamitarium.pl stripsearch.pl
> > trainbogo.sh ${INSTALL_SCRIPT} ${WRKSRC}/contrib/${i}
> > ${STAGEDIR}${DOCSDIR}/contrib/${i} .endfor
> >   
> 
> Yes, that is true, and these are contrib/uted, so are not necessary
> for normal operation.  

Neither are bogolexer, bogotune or bogoutil. Some of these scripts are
arguably more useful and can be essential for normal operation if a
system has been set-up to rely on them. The loss of spamitarium or
bogofilter-milter can stop bogofilter from being run.

> So what are you suggesting?

They aren't documentation, they're functional. Losing functionality
when deselecting DOCS is a serious POLA violation.

If they need to be optional it should be a separate option, but they
are only 216kB in total.




___
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"

Bogofilter contrib scripts treated as docs

[RW via freebsd-ports]

I just noticed that the bogofilter perl and shell scripts from the contrib
directory (see below) only get installed if bogofilter is built with the 
DOCS option.


.for i in bfproxy.pl bogofilter-milter.pl bogo.R bogofilter-qfe.sh \
   mime.get.rfc822.pl parmtest.sh printmaildir.pl \
   bogominitrain.pl \
   randomtrain.sh scramble.sh spamitarium.pl stripsearch.pl trainbogo.sh 
 ${INSTALL_SCRIPT} ${WRKSRC}/contrib/${i}  
${STAGEDIR}${DOCSDIR}/contrib/${i} 
.endfor
___
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: Status of portupgrade and portmaster?

[RW via freebsd-ports]

On Sun, 01 Oct 2017 20:53:29 +0200
Vlad K. wrote:

> On 2017-10-01 18:24, RW via freebsd-ports wrote:
> > 
> > Do you mean as opposed to installing the dependencies from the
> > repository, or are you saying that it rebuilds them?  
> 
> Poudriere builds isolated, in jails. That means it's not reusing 
> packages installed on the host, nor from another repo, if those are 
> needed as (build) dependencies.

I meant installing up-to-date packages from the *local* repository. So
if only Firefox needs to be updated would Poudriere first install
Firefox's dependencies into the jail from locally generated package
files before building Firefox.

If that happens then there wouldn't be much incentive to use anything
from the host as any package installed on the host would be in the
local repository - you'd just save a few installs.

 
___
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: Status of portupgrade and portmaster?

[RW via freebsd-ports]

On Sun, 01 Oct 2017 12:26:25 +0200
Vlad K. wrote:

> Another problem is poudriere's inability to reuse already installed 
> packages, if they're a dependency for something being built by it. 
> Personally I'd never use that option, as I want clean, isolated
> rebuilds of everything affected, but I can understand how quick
> building of one or two packages could use already installed deps, if
> people wanted that (and break any promise of integrity facilitated
> with isolated builds).

Do you mean as opposed to installing the dependencies from the
repository, or are you saying that it rebuilds them?   
___
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: Status of portupgrade and portmaster?

[RW via freebsd-ports]

On Sat, 30 Sep 2017 10:34:11 +
Carmel NY wrote:


> I have just the opposite experience. With "portupgrade" I was getting
> all too many dependencies installed that I had no use for. I
> personally appreciate synth's finer-grain installation philosophy.

But presumably that's just portupgrade installing build dependencies
and not removing them automatically.  
___
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: Synth and circular dependencies

[RW via freebsd-ports]

On Tue, 22 Aug 2017 06:34:15 +
Thomas Mueller wrote:


> It was very disconcerting when I would do a massive portupgrade
> before going to bed and subsequently find portupgrade stopped for an
> options dialog. 

FWIW portupgrade has a -c option to avoid that.
 
___
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: Synth and circular dependencies

[RW via freebsd-ports]

On Mon, 21 Aug 2017 13:19:24 +
Thomas Mueller wrote:


> But on this computer, no such system crashes, but I ran into circular
> dependencies 

Try removing any port options that aren't absolutely essential.

> It seems the ports go overboard with an awful lot of dependencies, of
> which not all install with the main port.  So I expect some of these
> dependencies might be false dependencies.

They are probably just build dependencies.
___
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: Question on Amavis and ramdisk

[RW via freebsd-ports]

On Mon, 21 Aug 2017 14:47:43 +0200
Willem Jan Withagen wrote:

> Hi,
> 
> In the amavis rc.d file is noted:
> ""
> "WARNING: using ramdisk is reported to be unstable and"
> "thus it is highly recommended to be turned off."
> ""
> 
> And this warning seems there since 2012



Actually it came in with revision 228889 in 2009. The script at
that point didn't allow for tmpfs and only checks for an existing md
device before creating a malloc md device (i.e. in unswapable wired
kernel memory).  IIRC there used to be a warning about this kind of md
device being able to cause crashes.

___
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: pkg and packages

[RW via freebsd-ports]

On Mon, 8 May 2017 09:29:47 -0700
Freddie Cash wrote:


> ​Samba + GVFS + Thunar doesn't make your FreeBSD filesystems
> available from Windows machines.  It makes your Windows file shares
> available on FreeBSD, and they show up in Thunar just like other
> folders.  GVFS uses libsmbclient and/or smbclient itself to access
> the CIFS/SMB shares, and abstracts all that away to make it look like
> just another folder.​

It seems strange that this support is controlled by setting a port
option called "Trash Panel Applet plugin" rather than one called "Gnome
Virtual Filesystem".
___
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: pkg and packages

[RW via freebsd-ports]

On Thu, 04 May 2017 07:43:30 -0600
Jim Trigg wrote:

> ISTR that it's Thunar that depends on Samba by default.

Yes it looks like it came in when Thunar defaulted to depending on the
"Trash Panel Applet Plugin". Unfortunately the options framework
caches old defaults.
___
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: pkg and packages

[RW via freebsd-ports]

On Thu, 04 May 2017 08:09:47 -0400
scratch65...@att.net wrote:
> 
> I can't imagine what code could possibly be in thunar and samba
> that the xfce desktop would need, particularly since the desktop
> is very simple, and also because I've never got samba
> functionality for free after installing xfce which if you're
> right I should have done.  But I'll check on that, and report
> back.  

AFAIK samba isn't a dependency of XFCE. I don't have it and it's not in
the output of make all-depends-list.

Thunar is scarcely "unrelated", it's the XFCE integrated file manager.
XFCE uses the  libthunarx library if built with the Thunar option.

If you want something without integrated utilities you might be better
off with a window manager, like Fluxbox, rather than a desktop
environment. 

It is possible to have XFCE without THUNAR from ports, or by building
custom packages.   
___
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: portmaster installation trampling on my binary packages???

[RW via freebsd-ports]

On Sun, 19 Mar 2017 21:57:48 +
Ethan Grammatikidis wrote:


> I'm not sure I understand. Are "latest" and "quarterly" ports trees?
>

The default packages for releases are built from a series of branches
of the main ports tree that are made split-off every three months, and
then just get security updates.

 
> Oh, reading section 4 of the handbook got me into this mess. :)
> Perhaps I'm too tired to read it properly, because I don't see
> anything to suggest I avoid mixing packages & ports freely.

The main problem is  mixing packages from different versions of the
ports tree. You would probably have got away with that if you'd updated
as much as possible with pkg and then just updated the few remaining
packages from ports, but ideally you should use the same version of the
ports tree that was used to build the package files. Your problem today
was that you told portmaster to upgrade *everything* from ports.
___
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: portmaster installation trampling on my binary packages???

[RW via freebsd-ports]

On Sun, 19 Mar 2017 18:35:26 +
Ethan Grammatikidis wrote:

> Hi. I'm quite new to FreeBSD. I'm getting a system up & running
> slowly, working around my chronic fatigue. Today I'm updating for the
> first time. Base system and pkg update appeared to go well. I haven't
> rebooted, wanting to get everything done before reboot.
> 
> https://www.freebsd.org/doc/handbook/ports-using.html
> This handook page says "ports-mgmt/portmaster is a very small utility
> for upgrading installed ports. It is designed to use the tools
> installed with the FreeBSD base system without depending on other
> ports or databases." That sounds just fine to me, so I did the usual
> to install portmaster, cd to its directory, and make install clean. 
> 
> So far, so good. Then I ran portmaster -a, and it all went
> pear-shaped. 

When you do a make install you are installing a package; all
other things being equal, there's really no difference between that and
installing a package file created on the FreeBSD build machines.  

When you run portmaster -a you are telling it to upgrade all your
installed packages that are not up-to-date with your ports tree
using ports. Since pkg uses a quarterly branch by default, that's likely
to be very different to the current tree, so it's likely to be a major
rebuild. 

If portmaster upgraded anything, you need to either let it complete, or
put everything back to the previous state.  If no one has a better
suggestion you could just use pkg to deinstall everything, then
reinstall what you want.



  

___
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: spamassassin does not list all required packages (3.4.1_9)

[RW via freebsd-ports]

On Sun, 26 Feb 2017 00:06:56 +
RW wrote:


> I'm not seeing these errors, but I'm guessing that they are caused by
> the OP using an internationalized domain name somewhere in the SA
> configuration. Most likely the name of server that spamd runs on.

Or maybe an accidental non-ascii character has got in.
___
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: spamassassin does not list all required packages (3.4.1_9)

[RW via freebsd-ports]

On Sat, 25 Feb 2017 12:34:54 -0800
Chris H wrote:

> On Sat, 25 Feb 2017 11:50:50 -0500 (EST) "Igor R."
>  wrote
> 
> > Hello!
> > 
> > As far as I can tell, spamassassin-3.4.1_9 does not list all
> > required p5 packages, which results in 3 error messages
> > in /var/log/maillog upon starting the package:
 spamd starts and seemingly works (maybe not fully?).
> > 
> > Installing the three packages by hand got rid of the error messages.
> > p5-Net-IDN-Encode
> > p5-URI
> > p5-Net-LibIDN
> > 

> This seems worthy of a pr(1).
> Could you create one for it, please
> (https://bugs.freebsd.org/bugzilla/)?


I'm not seeing these errors, but I'm guessing that they are caused by
the OP using an internationalized domain name somewhere in the SA
configuration. Most likely the name of server that spamd runs on.

The warning is coming from a file installed by the perl library port
security/p5-IO-Socket-SSL which has an IDN option that is off by
default. Possibly this should be on by default.
___
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: Do I need /var/db/portsnap/distfiles and /usr/port/distfiles?

[RW via freebsd-ports]

On Fri, 17 Feb 2017 08:32:17 +1100 (EST)
Dave Horsfall wrote:

> There is only the one FreeBSD box in my stable, hence I don't need to 
> build packages for others.  

It's to to do with whether you use ports, rather than if you build
package for other boxes. 

> It's a somewhat minimalist box (all I can 
> afford), and I'd like to recover some space.  Can I just delete their 
> contents?
> 
> aneurin# du -sk /usr/ports/distfiles /var/db/portsnap/files 
> 965198/usr/ports/distfiles

This is a cache, so you can delete it, or trim it with distclean
(installed with portupgrade), or portmaster. 

> 106594/var/db/portsnap/files

If you don't use portsnap then you can delete everything
under /var/db/portsnap. Don't delete these files if you do.
___
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: Port management tools (was: Status of synth)

[RW via freebsd-ports]

On Thu, 16 Feb 2017 09:19:24 -0500
George Mitchell wrote:


> > Yeah, I really like this a lot more than going through all the
> > config screens.  Back when I used portupgrade, I found that it was
> > too easy to accidentally set some option for a port to a
> > non-default value where it would persist forever. [...]  
> 
> This is in a nutshell why one group of FreeBSD users love portmaster
> so much.  I switched from portugrade to portmaster a long time ago
> for this very reason.

Do you mean because you didn't want to type "-c"?
___
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: devel/check

[RW via freebsd-ports]

On Sun, 12 Feb 2017 09:08:29 +1000
Andy Farkas wrote:

> On 12/02/2017 08:59, Matthew Seaman wrote:
> > On 11/02/2017 22:57, Andy Farkas wrote:  
> >> The -f flag is not mentioned in the man page for pkg(8).
> >>  
> > Try reading the pkg-delete(8) man page.
> >  
> 
> To be fair, the pkg(8) man page does not mention that pkg(8) calls
> sub-programmes  like pkg-delete(8).

It doesn't, pkg-delete is just the documentation for "pkg delete".
___
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: ports and dependency hell

[RW via freebsd-ports]

On Wed, 8 Feb 2017 16:03:56 +0800
Julian Elischer wrote:

> On 8/2/17 3:17 am, Grzegorz Junka wrote:
> >
> > On 07/02/2017 18:03, Julian Elischer wrote:  
> >> This is a serious post  on a serious issue that ports framework 
> >> people seem unaware of.
> >> (...)
> >>
> >> The call "It just works under linux, select the versions you want 
> >> of each package and type make" is often heard around the company. 
> >> And management is not totally deaf.
> >>  
> >
> > Hi Julian,
> > I may not fully understand how it works but what prevents you from 
> > getting sources for the version you want and typing make in them, 
> > exactly the way you do it in Linux? It should pick up the versions 
> > of dependencies currently installed in the system and compile for 
> > them. Is it only when you want to use the ports infrastructure that 
> > poses a problem?  
> 
> Nothing stops me from doing that. It's just that means that the ports 
> infrastructure is useless and a complete waste of time right?
> I'm no ready to admit that, however I may just be in denial.


It wasn't entirely clear what you were comparing FreeBSD ports with,
is it specifically buildroot2?

___
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: portsnap temporary files

[RW via freebsd-ports]

On Sat, 7 Jan 2017 06:51:44 +1100 (EST)
Dave Horsfall wrote:

> Is there some reason why portsnap cannot clean
> up /var/db/portsnap/files? I've just had to remove a zillion of them,
> a bunch at a time because "rm" choked on the arg list.

If you mean files under /var/db/portsnap/files/ then these are not
temporary files, they are the compressed snapshot, and you should not
delete them without very good reason. They are supposed to persist and
may remain unmodified for many months. 


Zillion is a bit vague, there should be one file for each port plus one
for each file outside a port directory. I have ~27k files.


The temporary .gz files are stored in the directory above and may be
deleted. 


___
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: mail/spamassassin config option AS_ROOT is confusing

[RW via freebsd-ports]

On Tue, 20 Dec 2016 11:53:43 -0700
Mike Brown wrote:

> The AS_ROOT option in the mail/spamassassin port is really confusing
> to me. Given that its description is "Run spamd as root
> (recommended)", what actually happens is somewhat bonkers:
> 
> The main spamd process always runs as root. If AS_ROOT is enabled,
> then the child processes who do all the work will not run as root,
> but rather as unprivileged user spamd. If AS_ROOT is disabled, then
> the children *will* run as root, but as needed they will setuid to
> the user calling spamc. 
> Which setting you want depends on where user prefs and Bayes data is
> stored. If it's in user-owned ~/.spamassassin directories, then you
> want AS_ROOT disabled or you'll get a plethora of error messages and
> lock file warnings relating to permissions, since user spamd can't
> write where it needs to.

That shouldn't happen as the default (without virtual users) is to
use /var/spool/spamd, the spamd user's home directory.

> It took me a while to figure this out on a fresh installation. I
> enabled the option, thinking "yes, of course I want it to run as
> root, so that it can write to the users' home directories"... then I
> was confused when it ended up not running as root but rather as user
> spamd, and the behavior I wanted was only possible if I configured
> the port to *not* run spamd as root.
> 
> I guess I am just griping, but I would like to think there is a
> better way to describe and name the configuration option. Maybe
> AS_SPAMD_USER with description "Run spamd as unprivileged user
> (recommended)"? 

I never noticed this because (probably like a lot of people) the first
thing I did was set my own spamd_flags in rc.conf and that overrides
the effect of AS_ROOT. 

I do agree it's confusing. I've CC'ed the maintainer. 


___
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: The ports collection has some serious issues

[RW via freebsd-ports]

On Thu, 15 Dec 2016 07:40:46 -0700 (MST)
Warren Block wrote:

> On Thu, 8 Dec 2016, Matt Smith wrote:
> 
> > On Dec 08 05:16, Daniil Berendeev wrote:  
> >> 
> >> Although portmaster is not releated to the FreeBSD project and is
> >> an outside tool, there aren't any alternatives from the project
> >> itself. So use it or die. Not a nice situation.  
> >
> > People have been trying to get portmaster deprecated and removed
> > from the handbook but have met with resistance.  
> 
> Well, yes.  Because it works, has no dependencies, and there is no 
> equivalent replacement.  Except maybe portupgrade, which has legacy 
> problems like poor default options.

That's a very minor issue, and an absurd excuse to rule-out portupgrade.
___
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: The ports collection has some serious issues

[RW via freebsd-ports]

On Sun, 11 Dec 2016 19:42:07 -0700
Janky Jay, III wrote:

> Hello scratch,
> 
> On 12/11/2016 03:35 PM, scratch65...@att.net wrote:
> > I have to admit that I avoid ports if at all possible because
> > I've hardly ever been able to do a build that ran to completion. 
> > There's always some piece of code that's missing and can't be
> > found, or is the wrong version, et lengthy cetera.   I've never
> > done release engineering, but I honestly can't imagine how some
> > of the stuff that makes its way into the ports tree ever got past
> > QA.  It would get someone sacked if it happened in industry.
> > 
> > If the dev schedule would SLOW DOWN and the commitment switched
> > to quality from the current emphasis on frequency, with separate
> > trees for alpha-, beta-, and real release-quality, fully-vetted
> > code, the ports system might become usable again.  
> 
>   This very, VERY rarely happens to me and I use ports *ONLY* in
> production environments.

I have a desktop with a lot of server ports installed on it and find
that the build problems I have are overwhelmingly desktop related. 

Even on the desktop I don't find it to be more than an irritation.
___
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: mail/mixmaster port issue

[RW via freebsd-ports]

On Sat, 10 Dec 2016 15:36:35 +0100
Kurt Jaeger wrote:

> Hi!
> 
> > > > My portmaster is stopping at mail/mixmaster saying broken
> > > > cannot find file
> > > > 
> > > > Running FreeBSD 11.
> > > > 
> > > > I checked and mixmaster is still avilable at sourceforge.
> > > > 
> > > > Please fix.  
> > > 
> > > Where would you get the distfiles with the same checksum ?
> > > 
> > > Can you provide a URL ?
> > > 
> > > The stuff on sourceforge is 3.0, not 3.0.2d ?  
> 
> > FYI  from the Makefile  
> 
> The Makefile fetches the distfiles from the distcache, not from any
> upstream. So the upstream is no longer available. So the port
> is BROKEN and marked as such.

If it's fetched from FreeBSD's own cache rather than a local cache,
anyone can build it just by removing the BROKEN line. I've never
understood why this is done, what's the point of supporting backup
servers in the ports makefiles if a port is marked as BROKEN every time
it's useful.
___
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: The ports collection has some serious issues

[RW via freebsd-ports]

On Thu, 8 Dec 2016 05:16:24 +
Daniil Berendeev wrote:

> 1) portmaster is not nice for the user.
> If it comes over an error even in one little tiny port that is a
> dependency for something bigger , it will abort its work and leave all
> the other ports not updated. So, if you try to to do `portmaster -af`,
> you should not forget `-m DISABLE_VULNERABILITIES=yes` (we will return
> to this one later) and you must pray to God for not coming around a
> circular dependency or some port that would fail to deinstall its
> older version. You can't leave portmaster for a night to update all
> the needed ports and deal with broken ones in the morning, you need
> to cherry pick the broken ports and ignore them, and then try to deal
> with them.
> 
> Although portmaster is not releated to the FreeBSD project and is an
> outside tool, there aren't any alternatives from the project itself.
> So use it or die. Not a nice situation.

There's portupgrade. It doesn't stop on the first error but carries on
with ports that don't depend on any broken ports. 
___
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: harder and harder to avoid pkg

[RW via freebsd-ports]

On Tue, 11 Oct 2016 11:59:47 -0700
Julian Elischer wrote:

> As the number of dependencies between packages get ever higher, it 
> becomes more and more difficult to compile packages and the
> dependence on binary precompiled packages is increased. However
> binary packages are unsuitable for some situations.  We really need
> to follow the lead of some of the Linux groups and have -runtime and
> -devel versions of packages,  OR  we what woudlbe smarter, woudl be
> to have several "sub manifests" to allow unpacking in different
> environments.
> 
> 
> A simple example:   libxml2
> 
> This package installs include files and libraries and dicumentation
> etc.
> 
> yet if I build an appliance , I want it to only install a singe file.
> 
> /usr/local/lib/libxml2.so.2

What practical problem does installing the include files and man pages
cause you?
___
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: FreeBSD Port: devel/libsysinfo

[RW via freebsd-ports]

On Wed, 21 Sep 2016 18:03:37 -0400
Robert Burmeister wrote:

> FreeBSD 10.3 i386.
> 
> lxde-meta 1.0_7, "meta-port" of the LXDE desktop
> x11/lxde-meta
> dependes on lxpanel 0.6.2_1, Lightweight X11 desktop panel
> x11/lxpanel
> which depends on libsysinfo 0.0.2_1, GNU libc's sysinfo port for
> FreeBSD devel/libsysinfo
> which is now
> "BROKEN: Unfetchable (google code has gone away)"


The file is in FreeBSD's distfile cache, which is the fallback server
for ports, so if you comment out that BROKEN=... line from the
Makefile it should work. The last I heard that cache had years of
retention, so marking the port as broken seems a bit premature to me.
___
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: GeForce GTX 750 Ti upgraded to unsupported

[RW via freebsd-ports]

On Thu, 8 Sep 2016 15:54:17 -0700
Russell L. Carter wrote:

> Greetings,
> 
> Since I upgraded to 11/stable from 10/stable, it appears that my video
> card is no longer supported by either nvidia-driver or
> nvidia-driver-340:
> 
>   77.208] (WW) NV: Ignoring unsupported device 0x10de1380 (GM107 
> [GeForce GTX 750 Ti]) at 01@00:00:0

NV is the xorg nvidia driver, not the proprietary driver from
x11/nvidia-driver*.

Do you have an xorg.conf that specifies nvidia? You can generate one
with nvidia-xconfig from  x11/nvidia-xconfig.
___
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: Firefox 47.0 hangs when accessing cnn.com

[RW via freebsd-ports]

On Tue, 7 Jun 2016 20:18:52 -0700
Kevin Oberman wrote:

> You should be able to use ports-mgmt/portdowngrade. This assumes that
> you still have the distribution file, as I suspect that it's no longer
> available for download from Mozilla. Check, though.

You can get many old versions:

http://download.cdn.mozilla.net/pub/firefox/releases/

If this weren't the norm then there would never have been much
point to distributing ports trees in installation ISOs.

Even if a file disappears from all the mirrors, the ports system
will fall-back to FreeBSDs own distfile cache.   
___
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: Poudriere question

[RW via freebsd-ports]

On Tue, 10 May 2016 17:05:20 +0200
Guido Falsi wrote:


> Never seen poudriere remove distfiles, nor the ports tree do that,
> what change are you referring to?
> 
The problem isn't anything to do with poudriere.

It was caused by a change to the checksum target in ports. The checksum
of a pre-existing file is tested and if it fails, the file is deleted
and a new version is downloaded. The point of this is presumably to
remove re-rolled distfiles. The problem is that a file that fails the
checksum is usually either a useful incomplete file from an interrupted
download, or a download in progress.

___
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: Poudriere question

[RW via freebsd-ports]

On Tue, 10 May 2016 14:35:35 +0200
Guido Falsi wrote:

> On 05/10/16 13:35, RW via freebsd-ports wrote:
> > On Mon, 9 May 2016 20:15:12 +0200
> > Guido Falsi wrote:
> >   
> >> On 05/09/16 19:52, Fernando Apesteguía wrote:  
> >>> Hi all,
> >>>
> >>> Is it safe to use different invocations of poudriere concurrently
> >>> for different jails but using the same ports collection?
> >>> 
> >>
> >> Yes it is, or at least should be.
> >>
> >> The ports trees are mounted read only in the jails, the wrkdir is
> >> defined at a different path.  
> > 
> > What about the distfiles directory? 
> > 
> > Having two "make checksums" running on the same file used to work
> > fairly well, but not any more because the target now deletes an
> > incomplete file rather than trying to resume it.
> > 
> > This wont damage packages, but it can cause two "make checksums" to
> > get locked in a cycle of deleting each other's files and end w
> > one getting a failed checksum.   
> 
> Yes it happens, I even have used the same disfiles over NFS with more
> than one machine/poudriere accessing it.
> 
> The various instances do overwrite each other and checksums do fail
> but usually in the end one of them "wins" and the correct file ends
> up being completed, with other instances reading that one. I agree
> this happens just by chance and not due to good design.

Only the last process will terminate with a complete file and without
error, when another process runs out of retries, the file with the
directory entry is a download in progress which will fail the checksum.

If it commonly ends-up working in poudriere that's probably a property
of how  poudriere orders things. But you still have the problem of
wasted time and bandwidth. This problem is most likely with large
distfiles and there's at least one that's 1 GB.


The way this used to work is that the second process would try to
resume the download which presumably  involved getting a lock on the
file. For smaller files it would just work. Worst case was that the
second process would fail after a timeout.

I think the change came in to delete possible re-rolled distfiles
automatically (a relatively minor problem), but in the process it
created this problem and also broke resuming downloads. 

I don't see the reason for checking and deleting the file before
attempting to resume it.



> As far as I understand Unix Filesystem semantics each download
> actually creates a new file, with only the last one to start
> referencing the actual file visible on the filesystem. So the last
> one starting to download is the one which will "win" creating the
> correct file on the FS, then checksumming it and going on. The other
> files have actuay been deleted and are simply removed from disk as
> soon as the download ends, if at that point the "winning" one has
> finished the download, they will checksum that file.
> 
> There is a chance of the loosing download to end before the winning
> one ends and overwriting it again, but in my experience with at most
> 3-4 instances over NFS it usually fixes itself in the long run.
> 
> IMHO best solution is to make sure you already have distfiles on disk
> for what you are going to build.
> 
___
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: Poudriere question

[RW via freebsd-ports]

On Mon, 9 May 2016 20:15:12 +0200
Guido Falsi wrote:

> On 05/09/16 19:52, Fernando Apesteguía wrote:
> > Hi all,
> > 
> > Is it safe to use different invocations of poudriere concurrently
> > for different jails but using the same ports collection?
> >   
> 
> Yes it is, or at least should be.
> 
> The ports trees are mounted read only in the jails, the wrkdir is
> defined at a different path.

What about the distfiles directory? 

Having two "make checksums" running on the same file used to work
fairly well, but not any more because the target now deletes an
incomplete file rather than trying to resume it.

This wont damage packages, but it can cause two "make checksums" to get
locked in a cycle of deleting each other's files and end with one
getting a failed checksum. 
___
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: Ports tree gone unstable?

[RW via freebsd-ports]

On Wed, 27 Apr 2016 23:48:43 -0700 (PDT)
Don Lewis wrote:


> I'd lose many hours of potential build time.  Because of the
> infrequent upgrades I would have to deal with all of the intervening
> special cases in UPDATING that accumulated between upgrades, and the
> portupgrade -fr and -a options didn't interoperate well, so I ended
> up having to build some ports multiple times. If things crashed,
> then I'd have to run portupgrade -rf again, rebuilding a lot of
> things unnecessarily since there was no way of doing a restart.

FWIW the  portupgrade -fr entries in UPDATING only need be followed if
you are doing a partial update. Any port affected by these gets its port
revision bumped, so is rebuilt as part of a portupgrade -a.

___
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: Deriving base port/package names

[RW via freebsd-ports]

On Fri, 8 Apr 2016 06:29:31 -0700 (PDT)
Roger Marquis wrote:

> Ronald F. Guilmette wrote:
> > what would be a proper sort of sed command to extract
> > _just_ the port/package names, without the version numbers
> > attached?  
> 
> This has changed in the past so may not currently be 100% correct but
> these should work:
> 
>awk -F'-[0-9]' '{ print $1 }'
> 
> or:
> 
>sed 's/-[0-9].*$//'

A port name can contain digits and hyphens, so this could remove
part of the name. 

Miroslav's version is better because it requires that the part that's
stripped only has a hyphen as it's first character.
___
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: Is it possible to specify which files are backed up to MASTER_SITE_BACKUP?

[RW via freebsd-ports]

On Sun, 29 Nov 2015 21:57:17 -0800
Yuri wrote:

> I have the complex fetch stage which takes one set of distfiles, and 
> produces another distfile, only that distfile is used in build.
> 
> There is the variable CKSUMFILES that controls which distfiles are 
> included in distinfo (in my case all of them should be there). But
> how do I control which distfiles get to MASTER_SITE_BACKUP? Is there
> a variable that controls this, distinct from DISTFILES? In my case I
> only want the distfile that my fetch produces to be cached in 
> MASTER_SITE_BACKUP. How can I do this?

I don't think you can, AFAIK it's just an ordinary DISTDIR that's
populated by port testing and package building.
___
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: ccache's cleanup algorithm

[RW via freebsd-ports]

On Tue, 03 Nov 2015 07:26:46 -0600
Scott Bennett wrote:

>  In ccache's cleanup.c module, the comments say that files are
> deleted from the cache on a LRU basis.  However, the code refers to
> mtime, not atime, so it appears that ccache is, in reality, using a
> Least Recently *Modified* basis upon which to expire files from the
> cache.  Is that really what ccache does?  Or did I miss something?
> If it's really using LRM instead of LRU, can anyone explain why?


That did use to be the case a long time ago, but I wrote a patch to
update the mtimes after a cache hit. The mtime updates are still there,
see from_cache() in ccache.c.

Using the file atimes wouldn't work well because they can be
accidentally updated by file searches, and  a lot of filesytems
are mounted with noatime anyway.
___
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: distfiles cleaner

[RW via freebsd-ports]

On Mon, 19 Oct 2015 14:16:37 +0200
Julian H. Stacey wrote:

> Hi ports@
> What is the modern equivalent of this obsolete stuff please ?
> 
> http://www.freebsd.org/cgi/man.cgi?query=portsclean=1=0=FreeBSD+9.0-RELEASE+and+Ports
>   portsclean --distclean
>   Clean out all the distfiles that are not referenced by any
>   port in the ports tree.
> 
> https://wiki.freebsd.org/portupgrade
>   Portupgrade (aka pkgtools)
>   last edited 2012-08-01

Why are you looking at the wiki? The code was updated only a few months
ago?

 https://svnweb.freebsd.org/ports/head/ports-mgmt/portupgrade/

I think the case for portupgrade and portsclean is now much stronger
than it was before they were fully converted to pkg. That removed all
the problems associated with maintaining a secondary database. The
conversion to pkg replaced portmaster's best code and portupgrade's
worst.


BTW I recently switched from distviper to portsclean. I used to prefer
distviper because of its speed, but that speed comes from assuming that
all distinfo files are called distinfo, which isn't true. I found
it was unconditionally removing the files for linux ports. It's also
never been converted to pkg which breaks its fast mode.  
___
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: rc script problem - pidfile not being recognised

[RW via freebsd-ports]

On Sat, 12 Sep 2015 08:02:11 -0700 (PDT)
Roger Marquis wrote:

> RW via freebsd-ports wrote:
> > You'd rather an rc script fails at run-time and shuts down the wrong
> > daemon than fail when the script is being developed?
> 
> It's not so much where the script fails than that it fails in the
> first place.  Neither a pidfile nor a command_interpreter needs to be
> required for an rc scripts to work.  These are nice features but
> making them mandatory is at best a sort of premature optimization.

It's not mandatory; you only need to define it if you want to be
able to stop an interpreted  daemon using the default method.

If you have some other way of shutting down a daemon without knowing its
name and PID  then you can just supply a stop function to do it.



> The freebsd rc script environment is already far too OS-specific and
> un-editable, often containing no readable shell code at all.

That's not been my experience. Occasionally it might a bit harder to
customise the script, but that's outweighed by all the times an override
can be made cleanly in rc.conf, without having to modify an installed
script. I've found that practically all customizations can be done
through rc.conf, and the rest usually involve editing an existing
stop/start function.

And rcng make it easy to keep multiple copies of the same rc file, you
can keep separate config and switch between them from rc.conf.


> What if
> your interpreter changes from say python2.7 to python for example?
> Does that mean you have to reinstall all the associated packages or
> edit their rc scripts?

If the interpreter changes from python2.7 to python, you'd have to
change the shebangs anyway.

 
___
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: rc script problem - pidfile not being recognised

[RW via freebsd-ports]

On Sat, 12 Sep 2015 01:46:23 +0200
Michelle Sullivan wrote:

> Roger Marquis wrote:
> > RW via freebsd-ports wrote:
> >> It needs both. It won't use just the pid file because the pid
> >> might have been reassigned to another process if the original
> >> daemon died without deleting its pid file.
> >
> > Why would this rc script *require* a command_interpreter variable
> > to use the pidfile variable?  I'm curious because this violates
> > KIS, the principle of least surprise and few rc scripts seem to
> > have this variable defined.
> >
> > Using command_interpreter is good to be sure, for for the reason
> > listed, but rc scripts should not fail if it is undefined.
> 
> +1 to that.

You'd rather an rc script fails at run-time and shuts down the wrong
daemon than fail when the script is being developed?
___
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: rc script problem - pidfile not being recognised

[RW via freebsd-ports]

On Fri, 11 Sep 2015 16:55:58 +0100 (BST)
Kevin Golding wrote:

> - Original Message -
> > From: "RW via freebsd-ports" <freebsd-ports@freebsd.org>
> > Sent: Friday, 11 September, 2015 4:18:50 PM
> > 

> > did you set the command_interpreter variable, probably you need
> > 
> > command_interpreter=/usr/local/bin/python2.7
> 
> And that seems to have fixed it - thank you.
> 
> I still think there's an error in reading the pidfile since I think
> this means I'm using the process name rather than the pid but it does
> the job so I won't worry too much for today. 

It needs both. It won't use just the pid file because the pid
might have been reassigned to another process if the original daemon
died without deleting its pid file. 
___
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: rc script problem - pidfile not being recognised

[RW via freebsd-ports]

On Fri, 11 Sep 2015 09:46:31 -0700 (PDT)
Roger Marquis wrote:

> RW via freebsd-ports wrote:
> > It needs both. It won't use just the pid file because the pid
> > might have been reassigned to another process if the original daemon
> > died without deleting its pid file.
> 
> Why would this rc script *require* a command_interpreter variable to
> use the pidfile variable?  I'm curious because this violates KIS, the
> principle of least surprise and few rc scripts seem to have this
> variable defined.
> 
> Using command_interpreter is good to be sure, for for the reason
> listed, but rc scripts should not fail if it is undefined.

IIRC  the name is always checked. When an interpreted script is run
using a shebang the command in the output of ps doesn't match the
command used to start the script, so command_interpreter is needed to
get a match.
___
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: rc script problem - pidfile not being recognised

[RW via freebsd-ports]

On Fri, 11 Sep 2015 15:42:18 +0100 (BST)
Kevin Golding wrote:

> I've been trying to work on a new port and it's my first that uses an
> rc script so I've been expecting a few bumps, but there's one thing I
> can't seem to fix and it's a blocker. I can't stop the daemon!
> 
> It dopes create a pidfile so I have the following line in my script:
> 
> pidfile="/var/run/${name}.pid"
> 
..
> # ps -waux | grep fuglu
> nobody   24013   0.0  0.5 139532  37372  -  I 3:57PM
> 0:01.03 /usr/local/bin/python2.7 /usr/local/bin/fuglu

did you set the command_interpreter variable, probably you need

command_interpreter=/usr/local/bin/python2.7
___
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: www/squid's cache dir

[RW via freebsd-ports]

On Tue, 14 Jul 2015 21:39:39 -0700 (MST)
timp wrote:




  Squid can use more than one cache directory, so it makes sense to
  have the default cache directory as a sub-directory of squid/.
 
 Additional cache dirs can be created manually by user in /var/squid, I
 agree. Like /var/squid/cache{1,2,3} etc whatever.
 But these dirs can be created manually in /var/cache too. Like
 /var/cache/squid{1,2,3}. I can't see any difference.

If you can't see any difference, what the point's in making a change?
___
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: www/squid's cache dir

[RW via freebsd-ports]

On Wed, 15 Jul 2015 04:25:56 -0700 (MST)
timp wrote:

 Ok, so you don't see the difference too, do you?

Actually I do see the difference - I think the current layout is
better. My point was that I can't see any difference isn't a good
argument for making disruptive change.
 

I think it's obvious that putting multiple caches under one squid
directory is better than having multiple squid directories.


 The point is get rid of dirs which we don't really need for this port,
 and place cache to suitable dir which is made in base system for such
 purposes.
 Just for order. You think it's bad idea?


I think it's cleaner to have a default location for squid caches,
rather than just a default cache location.   There's an unnecessary
directory to the same extent as there is with a single home directory
under /home.  

Whether squid goes under /var or /var/cache is a completely different
issue. In the second case you would need /var/cache/squid/cache.




 2015-07-15 14:08 GMT+03:00 freebsd-ports mailing list [via FreeBSD]
 ml-node+s1045724n6025455...@n5.nabble.com:
  On Tue, 14 Jul 2015 21:39:39 -0700 (MST)
  timp wrote:
 
 
 
 
   Squid can use more than one cache directory, so it makes sense to
   have the default cache directory as a sub-directory of squid/.
 
  Additional cache dirs can be created manually by user
  in /var/squid, I agree. Like /var/squid/cache{1,2,3} etc whatever.
  But these dirs can be created manually in /var/cache too. Like
  /var/cache/squid{1,2,3}. I can't see any difference.

Please don't top-post.
___
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: www/squid's cache dir

[RW via freebsd-ports]

On Tue, 14 Jul 2015 12:33:33 +0300
Pavel Timofeev wrote:

 Hi!
 
 A question was born in my mind about www/squid port:
 
 Do we really need a separate /var/squid dir for 'cache' and always
 empty 'logs' subdirs?
 Squid's logs are really in /var/log/squid, not in /var/squid/logs.
 
 So I think what if we had cache dir like /var/cache/squid, and got rig
 of /var/squid at all?
 What do you think?

I can see a case for fixing the Makefile so the log directory is
created in the right place. Moving the squid directory itself wouldn't
avoid creating /var/squid/logs.

Squid can use more than one cache directory, so it makes sense to have
the default cache directory as a sub-directory of squid/.
___
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: About Gxneur

[RW via freebsd-ports]

On Sun, 21 Jun 2015 16:48:39 -0400
kpn...@pobox.com wrote:

 On Sat, Jun 20, 2015 at 11:33:08AM +0300, ??? ??? wrote:
  Hello!
  
  I apologize for my English, I use a translator.
  I noticed that when I install gxneur is one problem. Xneur
  installed and working properly. But gxneur not want to run without
  further action. Namely the creation of links to / usr / locale /
  lib on two libraries from / usr / locale / lib / xneur ?hen
  everything is working correctly.
 
 Your translator seems to have mangled the software names. What
 language are you translating _from_?


$ make quicksearch name=xneur
Port:   gxneur-0.15.0_2
Path:   /usr/ports/deskutils/gxneur
Info:   GTK frontend for XNeur keyboard layout switcher

Port:   xneur-0.15.0_6
Path:   /usr/ports/deskutils/xneur
Info:   Auto keyboard switcher





 Question:
 
 gxneuer = Gnome?
 Xneur = X11?
___
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: Difference between fetch(1) and firefox http-access

[RW]

On Mon, 8 Dec 2014 10:59:54 +0100
O. Hartmann wrote:

 Sorry for the noise, many thanks for the quick solution ...

For future reference, cross-posting to multiple mailing lists is widely
considered to be bad netiquette (unless it's absolutely essential). 

If you don't get a quick answer, threads can descend into chaos because
not everyone will be subscribed to all the lists.

Even if no broken threads are created, some people will still find it
annoying to have a second unread version of the same thread.

___
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: Deleting ports distfiles

[RW]

On Mon, 17 Nov 2014 07:40:03 -0600
Adam Vande More wrote:

 On Mon, Nov 17, 2014 at 7:12 AM, RW rwmailli...@googlemail.com
 wrote:
 
  portmaster removes any files not associated with currently installed
  packages, the other two do can do that, but also have the option to
  leave any files that are still up-to-date with respect to the ports
  tree.
 
 
 This is a misleading statement.  portmaster also has that option.

My mistake. I'd always assumed that in  -t --clean-distfiles the
-t had its usual meaning of recurse through port dependencies. What
makes that particularly confusing is that recursing to handle missing
dependencies would be a useful option.


I'd still recommend distviper over portmaster because it's faster.
___
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

claws-mail's build dependency on Tex Live

[RW]

If you build claws-mail from ports you might want to think about
unchecking the manual option. It brings in a build dependency on 
textproc/docbook-utils which in turn depends on print/texlive-texmf.
This has a 1663 MB distfile and installs 1477 MB of files.

Obviously the manual option needs to be on by default, but perhaps
there should be a warning in the port menu. pkg doesn't show build
dependencies, so it's not obvious where texlive came from.



___
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: Deleting ports distfiles

[RW]

On Sun, 16 Nov 2014 14:10:00 -0900
Royce Williams wrote:

 On Sun, Nov 16, 2014 at 1:55 PM, andrew clarke m...@ozzmosis.com
 wrote:
  On Sun 2014-11-16 23:29:37 UTC+0100, Dr. Peter Voigt
  (pvo...@uos.de) wrote:
 
  I have just seen that /usr/ports/distfiles has grown up to 12 GiB.
  My hopefully not too stupid question is: Can I safely delete all
  files under /usr/ports/distfiles, e.g.
 
  # rm -rf /usr/ports/distfiles/*
 
  I strongly suppose so but I am not sure. Thanks for any feedback.
 
  Yes. Missing distfiles will be redownloaded when/if you rebuild a
  port.
 
 You can also delete just the unused ones, if you're using portmaster
 or portupgrade ('portsclean' command).  See the bottom of the Using
 the Ports Collection docs page:
 
 https://www.freebsd.org/doc/handbook/ports-using.html
 
 Even if you don't use portmaster for anything else, using it for this
 purpose is worth the install, IMO.

portupgrade's portsclean utility and distviper (from
sysutils/bsdadminscripts) can do it more flexibly.

portmaster removes any files not associated with currently installed
packages, the other two do can do that, but also have the option to
leave any files that are still up-to-date with respect to the ports
tree. Most distfiles are replaced every few months, so it doesn't make
a huge difference in terms of disk space. 
___
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: new dependency for emacs-nox11

[RW]

On Fri, 07 Nov 2014 10:27:39 -0500
Lowell Gilbert wrote:

 Vick Khera vi...@khera.org writes:
 
  Emacs 24.4 update in ports pulls in a new dependency:
  desktop-file-utils. This in turn pulls in a big swath of additional
  packages including python, perl, pcre, glib.
 
 I don't think so. desktop-file-utils doesn't seem to pull in anything
 that isn't already required for emacs (glib being the big one, and
 libintl the only other, according to pkg info). 

Out of idle curiosity I removed the desktop-file-utils dependency and
did a make all-depends-list in the nox slave port - glib wasn't there.
___
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: Reducing the size of the ports tree (brainstorm v2)

[RW]

On Sat, 1 Nov 2014 00:07:23 +0100
Tijl Coosemans wrote:

 On Fri, 31 Oct 2014 19:56:21 +0100 Baptiste Daroussin
 b...@freebsd.org wrote:
  Hi all,
  
  tijl@ spotted an interesting point, distinfo and pkg-descr files
  files convenient are taking a lot of space for free, we can
  reduce the size of the while ports tree by a factor 2 by simply
  merging them into one of the other files (Makefile and/or
  pkg-plist) from my testing it really devides significantly the size
  of the tree.
  
  Problem is how to merge them if we want to.
  
  What we do not want to loose:
  - Easyness of parsing distinfo
  - Easyness to get informations about the description
  

I think it's worth remembering that this saves an amount of storage
that can be had for around 1 penny/cent. The threshold for this being
more trouble than it's worth is pretty low.




  so far I have not been able to figure out a user friendly way
  
  Ideas I got so far only concerns pkg-descr:
  Adding an entry in the Makefile for the WWW:
  WWW= bla
  or an entry in the plist: @www http...
  
  for the description the Makefile is not suitable as multi line
  entry in Makefiles are painful
  Maybe a new keyword:
  @descr EOD
  mydesc
  in 
  multiline
  EOD
  
  which could easily be added to the plist parser in pkg. But I'm do
  not find that very friendly in particular for make(1) to extract
  the data.
  
  Concerning the distinfo I have no idea.
  
  so this mail is a call of ideas :), if nothing nice ideas is found
  we will just do nothing here :)
 
 For distinfo I was thinking about something like this in the Makefile:
 
 DIST_FILES=   FOO BAR
 
 FOO_FILE= foo-1.0
 FOO_SITES=http://www.example.com/foo/
 FOO_SIZE= 12345
 FOO_SHA256=   0123456789abcdef.
 
 BAR_FILE= bar-2.0
 BAR_SITES=http://www.example.com/bar/
 BAR_SIZE= 54321
 BAR_SHA256=   .fedcba9876543210
 
 If bsd.port.mk then contained this:
 DIST_FILES?=  DIST
 DIST_FILE?=
 ${PORTNAME}-${DISTVERSIONPREFIX}${DISTVERSION}${DISTVERSIONSUFFIX}
 
 Then for ports with a single distfile named after PORTNAME (the large
 majority), the above would reduce to:
 
 DIST_SITES=   http://www.example.com/foo/
 DIST_SIZE=12345
 DIST_SHA256=  0123456789abcdef.
 
 Also, if BAR_SITES is the same as FOO_SITES you can use somthing like
 BAR_SITES=${FOO_SITES} of course.


distviper and portsclean -D access all the distinfo files in the tree.
They could be heavily slowed if that information had to be got through
make targets.


___
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: service doen't get started at boottime, but can start manually

[RW]

On Sun, 7 Sep 2014 09:43:08 +0200
O. Hartmann wrote:

 
 I renamed the script back to refdb.sh by now and the service starts
 again as expected.  I guess the spawning into a subshell fails
 somehow at that point when booting the box.

FWIW refdb.sh works because /etc/rc.d/local will run pre-rcng
legacy scripts if they have a .sh extension.
___
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: service doen't get started at boottime, but can start manually

[RW]

On Sun, 7 Sep 2014 10:02:24 -0500
Scot Hetzel wrote:

 On Sun, Sep 7, 2014 at 8:38 AM, RW rwmailli...@googlemail.com wrote:
  On Sun, 7 Sep 2014 09:43:08 +0200
  O. Hartmann wrote:
 
 
  I renamed the script back to refdb.sh by now and the service
  starts again as expected.  I guess the spawning into a subshell
  fails somehow at that point when booting the box.
 
  FWIW refdb.sh works because /etc/rc.d/local will run pre-rcng
  legacy scripts if they have a .sh extension.
 
 /etc/rc.d/local doesn't run the pre-rcng scripts.

Sorry, that should have been localpkg.
___
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: service doen't get started at boottime, but can start manually

[RW]

On Sun, 07 Sep 2014 18:00:24 +0100
Mike Clarke wrote:

 On Sunday 07 Sep 2014 09:53:51 Scot Hetzel wrote:
 
  The scripts in 3-6, and 8 are wrong.  According to /etc/rc.subr, the
  '# PROVIDE: ' is mandatory to detect a rc script:
 
 Well it appears that they are only half wrong.
 
 Scripts without PROVIDE will work if they're in /etc/rc.d but not if 
 in /usr/local/etc/rc.d. I have run a test case to confirm this.

Whether or not you can get away without PROVIDE  a script should still
have one in case it's needed for other ports or local scripts.
___
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: Berkeley DB 4 and portupgrade

[RW]

On Mon, 25 Aug 2014 17:05:31 +0200
Matthias Andree wrote:


 You're looking in the wrong places, you should have:
 /usr/ports/INDEX-10.db and /var/db/pkg/pkgdb.db

As Chris Rees pointed out pkgdb.db isn't created anymore.
___
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

Berkeley DB 4 and portupgrade

[RW]

I've lost track of how portupgrade works these days (10.0). Has it
switched to using pkg's sqlite database? 


I was wondering whether I needed to do anything for the DB 4x
deletions, but I don't see a separate database file:

$ ls -l /var/db/pkg
total 41638
-rw-r--r--  1 root  wheel  39279616 23 Aug 14:55 local.sqlite
-rw-r--r--  1 root  wheel 38912 15 Sep  2013 repo-packagesite.sqlite
-r--r--r--  1 root  wheel   3236956 22 Aug 11:23 vuln.xml

___
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

make checksum problems

[RW]

There seems to be a change in make checksum where it's deleting
preexisting files that don't match their checksums. 

This is having two effects:

1. downloads don't resume any more because the partial file is deleted

2. if a make checksum runs while another make process is downloading a
   distfile, the file is deleted and a new file is created. The first
   process is then writing to a deleted file, so when it completes it
   checks the new incomplete file and deletes that. This can cycle until
   they both reach their FETCH_REGET limit. Usually one ends up with a
   checksum error. 


I suspect that 2  may be affecting portmaster, which runs make checksum
in the background. I have a script that does something similar, and I've
been seeing occasional failed builds like this with portupgrade.

 
Is this a known problem? I don't like to file a PR without doing a
search, and Bugzilla searches are all hanging with Please stand
by 
___
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: A simple ports question

[RW]

On Tue, 3 Jun 2014 21:15:15 +0200
Baptiste Daroussin wrote:

 On Tue, Jun 03, 2014 at 12:09:10PM -0700, Ronald F. Guilmette wrote:
  
  
  Functionally, what is the difference between:
  
 pkg_delete Y
  
  and:
  
 cd /usr/ports/X/Y; make deinstall
  
  ?
  
 none

There is one important difference, make deinstall passes -f to
pkg_delete to force the deletion.


___
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

Is Pan working for anyone?

[RW]

Is Pan working for anyone? The PR from last year has been closed,
but I'm still seeing it dump core with a segmentation fault on
FreeBSD 10.0. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=182203

___
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: smplayer dependency on mplayer1

[RW]

On Mon, 19 May 2014 17:54:26 -0700
Ronald F. Guilmette wrote:

 
 Looking at the Makefile for multimedia/smplayer it appears to me
 that smplayer is dependent upon the 1.x version of mplayer being
 installed, however there exists what I would guess is a later
 and better version of mplayer called multimedia/mplayer2 in the
 ports tree.
 
 So why is smplayer dependent upon an oldre (and now obsolete?)
 version of mplayer?

mplayer2 is a fork of mplayer, not a later version.
___
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: Repair pkgng

[RW]

On Thu, 10 Apr 2014 08:07:55 -0500
Scot Hetzel wrote:


 Portmaster is not breaking hier(7).

It's not, because it's information about what was used to build the
packages, so /var/db/pkg is a legitimate location.


 Portmaster was originally designed to use the old pkg tools
 (pkg_install, ...), it has ALWAYS placed it's files
 (PM_UPGRADE_DONE_FLAG, +IGNOREME, distfiles) in
 /var/db/pkg/${PKGNAME}.
 
 The options framework is relatively new in regards to portmaster, as
 portmaster was created before the options framework existed.

It's newer than the recently reworked version of the options
framework, but /var/db/port was used for options before that.
___
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: Repair pkgng

[RW]

On Thu, 10 Apr 2014 15:03:09 +0100
RW wrote:


 It's newer than the recently reworked version of the options
 framework, but /var/db/port was used for options before that.

Sorry, I meant: the recently reworked version of the options
framework is newer than portmaster,
___
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 abilities (was: pkgng vs. portupgrade reporting ports outdated)

[RW]

On Sat, 05 Apr 2014 07:55:48 -0400
Robert Huff wrote:

 Matthew Seaman matt...@freebsd.org writes:
 
pkg(8) does a damn sight more than the old pkg_tools.
 
   Granted, though much of it I currently have little use
 for.  :-)
 
   pkgng can do almost everything the old system can, and does it
   better.
  
 s/almost//
 
   OK, Obi-wan - what's the replacement for:
 
   a) portsclean with the C, D (single and double), and L
   options?  (Use no more than two commands.)
   b) pkg_sort ?
 
   With these, I will cheerfully delete portupgrade.

portupgrade isn't part of the old pkg_tools
___
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: Spamd

[RW]

On Thu, 03 Apr 2014 14:48:25 +0200
Jos Chrispijn wrote:

 
 Sergey V. Dyatko:
  use `sockstat -l4 -p783` instead. It show you what user-command-pid 
  listen that port
 
 USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN
 ADDRESS root perl   1404  5  tcp4   127.0.0.1:783 *:*
 root perl   1403  5  tcp4   127.0.0.1:783 *:*
 root perl   1402  5  tcp4   127.0.0.1:783 *:*
 
 Is this Perl itself or is this a program that uses Perl for this port?

It'll be  the spamassassin master process and default of two children.

By the look of it the rc.d script couldn't find a spamassassin perl
process that matched the PID in the pid file so couldn't shut the old
version down before starting the new. This is commonly because the pid
file isn't writeable, but using port 783 implies that it started as
root.

Check that the current pid file contains a correct value.  
___
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: Spamd

[RW]

On Thu, 03 Apr 2014 15:49:47 +0100
Matthew Seaman wrote:

 On 04/03/14 13:57, Jos Chrispijn wrote:
  Sergey V. Dyatko:
  use `sockstat -l4 -p783` instead. It show you what user-command-pid
  listen that port
  
  I killed process 1402 and started Spamd. That did the trick, thanks!
  
  I am very curious:
  
  a. why Perl occupied that port.
  Tried to retrieve this information from logfiles in /var/log but no
  success. May that be an inward traffic issue on port 783 that
  triggered Perl and kept it occupied for Spamd?
  
  b. Is it unsafe or possible to let spamd use another port if 783 is
  occupied. May that be a security risk?
 
 Assuming 'spamd' here is part of spamassassin then it is a daemon
 written in perl, and the command name will show up as perl in sockstat
 listings.
 
 In my experience, it is quite common for this daemon to end up running
 under a different PID than the one recorded under /var/run -- so the
 system initialization scripts 'sa-spamd' think it isn't running, and
 then you get the fight over access to port 783 the OP saw.  Killing
 the processes using port 783 and restarting spamd should work.
 
 The situation is complicated by the /other/ spamd -- which is an
 OpenBSD thing which works via pf to implement greylisting, teergrube
 and various other anti-spam things.  Meaning the SpamAssassin
 'sa-spamd' startup script can't simply kill anything called spamd.

Support for pid files is built into rcng and used a combination of pid
and name, sa-spamd uses this and correctly passes the expected pid
file path to spamd. 

In my experience it does normally work, unless spamd is started as an
unprivileged user via the spamd_user variable in rc.conf, rather
dropping privileges - that's not happening here because the existing
process used port 783.
___
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: Spamd

[RW]

On Fri, 04 Apr 2014 06:57:29 +1100
John Marshall wrote:

 On 04/04/2014 05:13, Jos Chrispijn wrote:
 Since my last Spamd port update I get this error when I try to
  start spamd:
 spamd not running? (check /var/run/spamd/spamd.pid).
 Starting spamd.
 
 For SpamAssassin, you need to provide the pidfile specification in
 /etc/rc.conf.
 
   mta4# grep pidfile /etc/rc.conf
   spamd_pidfile=/var/run/spamd/spamd.pid


That's already the default.
___
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: Why would a port use its own existence as an excuse to fail install?

[RW]

On Sat, 15 Feb 2014 22:14:54 -0600
Matthew D. Fuller wrote:


 A nice thing about portmaster is that it's smarter than portupgrade.
 ...
 In this case, I'd guess, portmaster ... Which fails, since it's
 already installed, thus...

For me portupgrade did that upgrade perfectly even though I forgot to
read UPDATING. pkg check reports no errors.
___
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

ccache and clang/llvm links

[RW]

I was wondering why the ccache compiler link options for clang and llvm
are off by default. AFAIK these links don't affect World build, so I was
wondering if there are any serious problems with ports.
___
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: Portmanager vs portupgrade

[RW]

On Thu, 23 Jan 2014 12:39:59 +
Matthew Seaman wrote:


 maintained by the same people (bdrewery mostly).  portupgrade requires
 you to install ruby as well: that's probably the biggest deciding
 factor still extant. 

For me the biggest factor is that portupgrade doesn't stop on the first
error, it carries on building ports that don't depend on failed ports
and then presents a summary of the problems at the end. 

This is a big advantage on desktop installations where there are a lot
more ports and they are generally less reliable.
___
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: Ports via svn, make fetchindex and make compatibility with NetBSD

[RW]

On Tue, 03 Dec 2013 13:27:57 +
Matthew Seaman wrote:

 If you do need a copy of the index, then you have two choices
 
* build your own.  'make index' will thrash your machine for
 upwards of twenty minutes, 


That's pessimistic, on my low-end i5 with low-performance disks,
it takes between 2.25 and 3.5 minutes (depending on how many files are
already cached) with no noticeable impact on performance.

___
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: Ports via svn, make fetchindex and make compatibility with NetBSD

[RW]

On Tue, 3 Dec 2013 04:41:17 -0800 (PST)
Thomas Mueller wrote:

 Is it necessary to make fetchindex after downloading or updating the
 ports tree using svn?

Not absolutely, it's needed for portupgrade, port searches, and a number
of utilities use it for speeding various things up.

 I have new installations of head and 10-stable where I so far can't
 connect to the Internet, though I can from Linux and NetBSD-current
 amd64.
 
 So I use subversion, built on NetBSD from pkgsrc, to checkout and
 update ports tree as well as system source tree.
 
 But I believe I can't run make fetchindex without Internet
 connection.
 

You can run make index instead, it takes about 3 minutes on my
desktop.
___
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: Upgrading Perl... Somebody just shoot me and put me out of my misery!

[RW]

On Fri, 22 Nov 2013 00:25:26 -0800
Ronald F. Guilmette wrote:


 Anyway, the specific broken port I'm trying to fix at the moment is
 net/p5-Socket, which is failing thusly:

I had to revert the switch to threaded perl because of this,
dns/p5-Net-DNS, net/p5-IP-Country and converters/p5-Encode-Detect.

___
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: Ports distfiles mirror - e.g. ftp://ftp4.de.freebsd.org/FreeBSD/distfiles/

[RW]

On Thu, 31 Oct 2013 19:00:52 +0100
Matthias Petermann wrote:


 Is there some automatic mechanism in place which does this mirroring,
 or is this done manually from a ports committer once he commits a new
 or updated port? I'm just curious because I can find the distfiles
 from some of my maintained ports there, and from some not.

I'm not sure about that specific URL, but IIRC FreeBSD keeps a cache of
distfiles downloaded for package building purposes and makes it
available as a last-resort mirror.
___
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: bsdadminscripts and pkng

[RW]

On Thu, 31 Oct 2013 23:13:38 -0700 (PDT)
Jakub Lach wrote:

 Actually, nevermind those. They are supporting pkng just fine.
 
 Real bumps when converted to pkgng was:
 
 - portmaster cannot use packages for dependencies- huge let down
 - pkg_cleanup doesn't support pkng


distviper uses pkg_info when used in fast mode (i.e. when it retains
only distfiles for installed ports).



___
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: multimedia/libbluray -- IGNORE... Why?

[RW]

On Fri, 04 Oct 2013 12:01:19 -0700
Ronald F. Guilmette wrote:

 
 In message 20131004113101.GB42900@oldfaithful.bebik.local, you
 wrote:
 
 Hi,
 
 I Made a check in the SVN and libbluray was never
 marked IGNORE, at least BROKEN for some java reasons.

Setting BROKEN sets IGNORE.

 Well, I'm just showing you what portupgrade -a reported...
 
 - multimedia/libbluray (marked as IGNORE)
 
 Are you sure isn't a dependencie problem ?
 
 No, but I have no reason whatsoever to believe that is.

# cd /usr/ports/multimedia/libbluray

# make config

 ?? libbluray-0.3.0,1 ? ?
 ??
 ? ? ? [x] JAVA  Enable Blu-Ray Java support  ? ? ?
 ??
 ?
 ... 


# make
===  libbluray-0.3.0,1 is marked as broken: Does not build with JAVA.
*** Error code 1




Alternately:

# make -V IGNORE
is marked as broken: Does not build with JAVA



Or just read the Makefile:

.if ${PORT_OPTIONS:MJAVA}
BROKEN= Does not build with JAVA
   ...
.endif
___
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: Packages missing after Re-installation with portmaster

[RW]

On Sat, 5 Oct 2013 12:44:52 +0200
Fabian Keil wrote:

 I'm occasionally missing packages after trying to rebuild them with
 portmaster. For example I just lost liferea:
 
 fk@r500 ~ $portmaster liferea
 
 === Currently installed version: liferea-1.8.15
...
 === SU Running pkg_delete for liferea-1.8.15
 Deinstallation has been requested for the following 1 packages:
 
   liferea-1.8.15
 
 The deinstallation will free 3 MB
 [1/1] Deleting liferea-1.8.15... done
 
 === SU Running make install
...
 Has anyone seen this behaviour?

What behaviour? The old version was removed and the new one installed.
I don't see any evidence that anything was lost.

___
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: multimedia/libbluray -- IGNORE... Why?

[RW]

On Fri, 04 Oct 2013 04:17:12 -0700
Ronald F. Guilmette wrote:

 
 
 Why is the multimedia/libbluray port marked as IGNORE in the current
 ports tree?

If you try to build it, it will tell you why.

 More to the point, why didn't whoever marked it as IGNORE have the
 simple courtesy to put at least some explanitory note about the
 marking of this port (as IGNORE) into the UPDATING file?

That's not what UPDATING is for. 


___
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: SVN RELEASE_9_2_0

[RW]

On Tue, 01 Oct 2013 06:56:32 +
Thomas Mueller wrote:

 # Is FreeBSD doing something new?  I don't see an SVN tag for ports
 for # the 9.2 release.  Historically the ports tree was tagged and
 built a # little before -stable got tagged for release.
  
 # Thanks,
 # Jason
 
 Ports don't belong to a specific FreeBSD version.
 
 It's the built packages that are prepared shortly before release.
 
 For the ports and doc trees, you would go for head (current).

He's not talking about a branch. It was a tag that allowed one to fetch
the snapshot of the ports tree that was included on the release CDs and
from which the release packages were built.
___
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

dspam looking for libhash_drv.so in wrong location

[RW]

Under 10-current I've had a problem with dspam failing with the error:

  dlopen() failed: /usr/local/lib/libhash_drv.so: Cannot
  open /usr/local/lib/libhash_drv.so

The actual library is located under  /usr/local/lib/dspam/.

(I have it working again with a temporary symlink)
___
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: Perl port to select in make.conf

[RW]

On Tue, 3 Sep 2013 12:22:23 +0400 (MSK)
Dmitry Morozovsky wrote:

 On Mon, 2 Sep 2013, RW wrote:
 

  When you install perl (as part of an upgrade or as a dependency) it
  writes the new PERL_VERSION into make.conf.
 
 Well, all would go well unless it was a *special* make.conf used for
 poudriere bulk building instead of system one.
 
 Well, possibly I should use 'could stop' instead of
 definitively-looking 'will stop'

I don't see why that would stop perl being updated, the minor and
major versions are sufficient to identify the correct port. An out of
date patch level in PERL_VERSION could affect dependent ports that have
very fine grained version requirements, and need a specific patch level,
but that's very rare.
___
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: Perl port to select in make.conf

[RW]

On Tue, 03 Sep 2013 07:46:03 -0500
Mark Felder wrote:

 On Sun, Sep 1, 2013, at 13:31, Dmitry Morozovsky wrote:
  Dear colleagues,
  
  which variable should be defined in make.conf to switch from
  current 5.14 to, 
  say, 5.16 (for poudriere package building)? 
  
  Naive 
  
  PERL_VER=5.16
  
  does not seem to work, and I want to not chase minor version
  changes.
  
 
 PERL_PORT
 
 example:
 
 PERL_PORT=perl5.14

If you set PERL_PORT, and PERL_VERSION doesn't get spammed into the
correct make.conf (see rest of thread), then dependent ports see the
default PERL_LEVEL and PERL_VERSION.

# grep PERL /etc/make.conf
PERL_PORT=perl5.16

# cd /ports/mail/p5-Mail-SpamAssassin/

# make -V PERL_LEVEL
501404
# make -V PERL_VERSION
5.14.4
___
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: Perl port to select in make.conf

[RW]

On Sun, 1 Sep 2013 23:01:48 +0400 (MSK)
Dmitry Morozovsky wrote:

 On Sun, 1 Sep 2013, Boris Samorodov wrote:
 
  Приветствую, Дмитрий -- давно не виделись, ;-)
 
 sme here ;)
 
   which variable should be defined in make.conf to switch from
   current 5.14 to, say, 5.16 (for poudriere package building)? 
   
   Naive 
   
   PERL_VER=5.16
   
   does not seem to work, and I want to not chase minor version
   changes.
  
  I use PERL_VERSION=5.16.3.
 
 It definitely works, but will stop with 5.16 upgrade; that is the
 situation to avoid.

If you mean it will stop 5.16.3 being upgraded to 5.16.4, it wont
(unless there's something specific in the way poudriere handles perl). 

When you install perl (as part of an upgrade or as a dependency) it
writes the new PERL_VERSION into make.conf.


___
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: sysutils/fusefs-ntfs fusefs_enable=YES

[RW]

On Thu, 22 Aug 2013 06:41:33 -0500
Mark Felder wrote:

 On Wed, Aug 21, 2013, at 17:09, RW wrote:

  I see what's happened. Earlier in the year,against my better
  judgement, I move to CURRENT in futile attempt to make intel KMS
  work. It looks like fuse has been moved into the base system,
  but /etc/rc.d/ hasn't yet been updated to reflect that. 
 
 
 There isn't an /etc/rc.d/ for every kernel module. If you want to use
 fuse on FreeBSD 10 and later just put fuse_load=YES in loader.conf.
 The rc.d script in the port was just a nice courtesy. I don't think
 it's likely we'll see an /etc/rc.d/fuse script appear in the base
 system.

I have added it to loader.conf, but the reason I brought it up was that
I thought the documentation might be out of date, which appears to be
the case. 

If nothing's been decided I can't really submit a documentation
patch.

If anyone's interested the relevant files are:

sysutils/ntfsprogs/files/README.FreeBSD
sysutils/fusefs-ntfs/files/README.FreeBSD
___
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