Re: I thought "pkg updating" would alert me about python...?

Van: Tatsuki Makino Datum: 2 mei 2021 22:36 Aan: Ronald Klop , freebsd-ports@freebsd.org Onderwerp: Re: I thought "pkg updating" would alert me about python...? Ronald Klop wrote on 2021/05/03 05:14: > The UPDATING entry should have said something like "users of lang/pytho

Re: I thought "pkg updating" would alert me about python...?

Ronald Klop wrote on 2021/05/03 05:14: > The UPDATING entry should have said something like "users of lang/python*" to > work. The behavior of this is strange. I have the following python* in my environment. python, python27, python3, python37 and python38 AFFECTS: users of py

Re: I thought "pkg updating" would alert me about python...?

On 5/2/21 4:20 PM, David Wolfskill wrote: I just re-verified the behavior, so -- even though I have already started taking evasive action (updating python), I figured it may be of use to show what I'm seeing; maybe I'm confused: Local ports tree is updated; previous ports update was

I thought "pkg updating" would alert me about python...?

I just re-verified the behavior, so -- even though I have already started taking evasive action (updating python), I figured it may be of use to show what I'm seeing; maybe I'm confused: Local ports tree is updated; previous ports update was a week ago. I happen to know that there

Re: Changing daemon user, dir ownership and updating packages

On Mon, Apr 26, 2021 at 10:13 PM Dewayne Geraghty < dewa...@heuristicsystems.com.au> wrote: > On 26/04/2021 6:03 pm, Stefan Bethke wrote: > > But that still leaves pkg updating the ownership/mode of existing > directories as a surprise on updating a package. I think the "ri

Re: Changing daemon user, dir ownership and updating packages

On 26/04/2021 6:03 pm, Stefan Bethke wrote: > But that still leaves pkg updating the ownership/mode of existing directories > as a surprise on updating a package. I think the "right" thing here would be > a kind of three-way merge between changes an updated package brings in

Re: Changing daemon user, dir ownership and updating packages

> > > I believe this to be best practice. Is there a better way to have pkg > create these dirs if they're missing, but not touch them if they are there > already? > > Adam has suggested a couple of approaches, but what I would really like is > a common, documented way

Re: Changing daemon user, dir ownership and updating packages

but not touch them if they are there already? Adam has suggested a couple of approaches, but what I would really like is a common, documented way for ports to handle this situation. Updating ownership and mode of entries in the rc script automatically feels wrong to me, especially if it's

Changing daemon user, dir ownership and updating packages

As the maintainer, I've received this bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255009 If you'd like to run the daemon under a user different from the default git, you also need to change the ownership of the working directories, especially /var/*/gitea. The expectation is t

Re: Updating poudriere to use gitup

* Carmel [20210407 06:03]: > Is there a 'How-to" posted on how to convert poudriere to use 'gitup' or > even "git" if necessary? Poudriere doesn't support gitup (so far?) Your options are to use methods git or null, see poudriere-ports(8). To use gitup with poudriere, configure your ports with m

Re: Updating poudriere to use gitup

Hi! > With the change in the FreeBSD ports system, I have started to use > "gitup". I have this working fine. Unfortunately, I cannot figure out > how to get poudriere, version 3.3.99.20210303_1 to use 'gitup' too. It > insists on using 'portsnap'. This is on a FreeBSD 11.4-p9 system. > > Is ther

Updating poudriere to use gitup

With the change in the FreeBSD ports system, I have started to use "gitup". I have this working fine. Unfortunately, I cannot figure out how to get poudriere, version 3.3.99.20210303_1 to use 'gitup' too. It insists on using 'portsnap'. This is on a FreeBSD 11.4-p9 system. Is there a 'How-to" post

Re: Problems with updating a port due to top directory in tarball

On Sat, 6 Mar 2021, Kevin Oberman wrote: On Wed, Mar 3, 2021 at 10:15 PM Hiroo Ono wrote: On 2021年3月4日木曜日 9時00分32秒 JST, Kevin Oberman wrote: I'm trying to update a port I maintain. Since I last updated, it moved from ISC to github and it uses unusual naming conventions. The distfile is "

Re: Problems with updating a port due to top directory in tarball

On Wed, Mar 3, 2021 at 10:15 PM Hiroo Ono wrote: > > On 2021年3月4日木曜日 9時00分32秒 JST, Kevin Oberman wrote: > > I'm trying to update a port I maintain. Since I last updated, it moved > from > > ISC to github and it uses unusual naming conventions. > > > > The distfile is "irrtoolset/archive/release-5

Re: Problems with updating a port due to top directory in tarball

On 2021年3月4日木曜日 9時00分32秒 JST, Kevin Oberman wrote: I'm trying to update a port I maintain. Since I last updated, it moved from ISC to github and it uses unusual naming conventions. The distfile is "irrtoolset/archive/release-5.1.3.tar.gz". I can work around this with a DIST_SUBDIR and DISTNAME,

Re: Problems with updating a port due to top directory in tarball

I am resending this mail because I put the wrong From for the first time. On 2021年3月4日木曜日 9時00分32秒 JST, Kevin Oberman wrote: I'm trying to update a port I maintain. Since I last updated, it moved from ISC to github and it uses unusual naming conventions. The distfile is "irrtoolset/archive/rele

Re: Problems with updating a port due to top directory in tarball

Thanks to both of you. Looks like I can continue working on the port, now! -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.

Re: Problems with updating a port due to top directory in tarball

Kevin Oberman writes: > I'm trying to update a port I maintain. Since I last updated, it moved from > ISC to github and it uses unusual naming conventions. > > The distfile is "irrtoolset/archive/release-5.1.3.tar.gz". I can work > around this with a DIST_SUBDIR and DISTNAME, but when the extract

Re: Problems with updating a port due to top directory in tarball

On 2021-03-04 00:00, Kevin Oberman wrote: I'm trying to update a port I maintain. Since I last updated, it moved from ISC to github and it uses unusual naming conventions. The distfile is "irrtoolset/archive/release-5.1.3.tar.gz". I can work around this with a DIST_SUBDIR and DISTNAME, but when

Problems with updating a port due to top directory in tarball

I'm trying to update a port I maintain. Since I last updated, it moved from ISC to github and it uses unusual naming conventions. The distfile is "irrtoolset/archive/release-5.1.3.tar.gz". I can work around this with a DIST_SUBDIR and DISTNAME, but when the extract takes place, the top directory

Re: Updating emulators/i386-wine-devel but get a runtime error

Nevermind, it was that WINEDLLPATH was missing. -Neel On 2021-02-23 13:01, Neel Chauhan wrote: Hi freebsd-ports@ I recently adopted emulators/i386-wine-devel and am attempting to update it to 6.2 along with adding 14.0 support. Phabricator URL: https://reviews.freebsd.org/D28908 When I attem

Updating emulators/i386-wine-devel but get a runtime error

Hi freebsd-ports@ I recently adopted emulators/i386-wine-devel and am attempting to update it to 6.2 along with adding 14.0 support. Phabricator URL: https://reviews.freebsd.org/D28908 When I attempt to run the `wine` command, I get this error: root@omen:/usr/ports.dev/emulators/i386-wine-de

Re: Phabricator Review: Updating the GNUstep Ports

The phrase "The Port" in this email should mean "This patch", sorry for the wrong wording. -Neel On 2021-02-13 14:15, Neel Chauhan wrote: Hi freebsd-ports@, I have a review on Phabricator to update the GNUstep Ports: https://reviews.freebsd.org/D28654 The Port mainly updates: * devel/gnuste

Phabricator Review: Updating the GNUstep Ports

Hi freebsd-ports@, I have a review on Phabricator to update the GNUstep Ports: https://reviews.freebsd.org/D28654 The Port mainly updates: * devel/gnustep-make: Update to 2.8.0 * lang/gnustep-base: Update to 1.27.0 * x11-toolkits/gnustep-back: update to 0.28.0 * x11-toolkits/gnustep-gui: upda

Re: Updating devel/tbb - Introducing devel/onetbb

r change > before your update can be committed. I would then add reports to update > other dependencies that block my update. > > At most you submit 20 reports to say xx/yy port needs updating. There is > devel/pybugz and ports-mgmt/freebsd-bugzilla-cli that could automate >

Re: Updating devel/tbb - Introducing devel/onetbb

would then add reports to update other dependencies that block my update. At most you submit 20 reports to say xx/yy port needs updating. There is devel/pybugz and ports-mgmt/freebsd-bugzilla-cli that could automate that but I haven't used them so can't recommend either. Then all the depe

Re: Updating devel/tbb - Introducing devel/onetbb

On Saturday, January 9, 2021 9:49:24 AM CET Shane Ambler wrote: Hello Shane, Thanks for your reply. > > - leave devel/tbb in place and introduce a new port: devel/onetbb > > While I would generally support moving the old libs to a new portname, > the fact that the project has renamed itself mak

Re: Updating devel/tbb - Introducing devel/onetbb

On 8/1/21 9:51 pm, Ganael Laplanche wrote: > - leave devel/tbb in place and introduce a new port: devel/onetbb While I would generally support moving the old libs to a new portname, the fact that the project has renamed itself makes this acceptable. > - design devel/onetbb to install files in de

Updating devel/tbb - Introducing devel/onetbb

Hello, First of all, happy new year :) Intel oneAPI tbb (formerly known as Intel tbb) 2021.1 has been released and has deprecated several interfaces over tbb 2020. See: https://software.intel.com/content/www/us/en/develop/articles/intel-oneapi-threading-building-blocks-release-notes.html a

Updating x11-toolkits/scintilla

Hello everyone, I have been pretty behind on updating ports I maintain so I have been looking into updating x11-toolkits/scintilla from the current version in ports of 4.3.2 to the current actual version of 4.4.5. It appears as if scintilla is working towards making the lexers part of the

Re: Poudriere: Installing or updating jails fail with cp/utils.c error

riere/jails/F114i386/usr/src/bin/cp/utils.c:466:9: note: forward > > declaration of 'struct acl' > > struct acl *aclp; > >^ > > 2 errors generated. > > *** [/poudriere/jails/F114i386/usr/src/bin/cp/utils.o] Error code 1 > > > >

Re: Poudriere: Installing or updating jails fail with cp/utils.c error

erated. > *** [/poudriere/jails/F114i386/usr/src/bin/cp/utils.o] Error code 1 > > make[5]: stopped in > /usr/obj/i386.i386/poudriere/jails/F114i386/usr/src/rescue/rescue > > > This happens on a recent 13.0-CURRENT amd64 (r366190). Updating HEAD > jails work fine so far.

Re: Might an UPDATING entry be appropriate for a MINIMAL_PKG_VERSION bump?

c delete-old delete-old-libs mergemaster shutdown -r +1 > > Hence my query: Is an UPDATING entry warranted when MINIMAL_PKG_VERSION is > bumped? > Normally, when pkg appears in pkg version -L =, it is replaced immediately because something of a bug in it h

Re: Might an UPDATING entry be appropriate for a MINIMAL_PKG_VERSION bump?

on/S1/obj/usr/src/amd64.amd64/sys/CANARY make -B clean build | ===> Cleaning for nvidia-driver-440.100_1 | ===> nvidia-driver-440.100_1 pkg(8) must be version 1.15.9 or greater, but | you have 1.15.8. You must upgrade the ports-mgmt/pkg port first. | *** Error code 1 | | Stop. Hence my query:

Re: Might an UPDATING entry be appropriate for a MINIMAL_PKG_VERSION bump?

rts-mgmt/pkg. > > In each case (so far), I have then updated ports-mgmt/pkg, then > re-started the base OS build/install. > > I believe that it would be helpful to have an UPDATING entry reflect > that "evasive action" is required when MINIMAL_PKG_VERSION is bumped.

Might an UPDATING entry be appropriate for a MINIMAL_PKG_VERSION bump?

rebooted the newly-built base OS... and "?ports" includes ports-mgmt/pkg. In each case (so far), I have then updated ports-mgmt/pkg, then re-started the base OS build/install. I believe that it would be helpful to have an UPDATING entry reflect that "evasive action&qu

Poudriere: Installing or updating jails fail with cp/utils.c error

/rescue This happens on a recent 13.0-CURRENT amd64 (r366190). Updating HEAD jails work fine so far. Am I doing something wrong? I thought, the cp/utils.c problem was solved some time ago? Thanks for any insight and help. Regards, Rainer Hurling

Re: Segmentation fault happens after updating mail/postfix to 3.5.5

On Sun, 26 Jul 2020 11:59:25 +0900 (JST), Yasuhiro KIMURA stated: >Hello All, > >After updating mail/postfix to 3.5.5 following warning message appears >in /var/log/maillog. > >Jul 26 11:47:34 eastasia postfix/smtpd[93696]: connect from >maybe.home.utahime.org[192.168.174

Segmentation fault happens after updating mail/postfix to 3.5.5

Hello All, After updating mail/postfix to 3.5.5 following warning message appears in /var/log/maillog. Jul 26 11:47:34 eastasia postfix/smtpd[93696]: connect from maybe.home.utahime.org[192.168.174.201] Jul 26 11:47:34 eastasia postfix/smtpd[93696]: SSL_accept error from maybe.home.utahime.org

Re: Updating py27-* ports

On Sat, 4 Jul 2020 10:23:09 -0600, @lbutlr stated: >On 04 Jul 2020, at 08:30, Carmel wrote: >> I see that you are putting it all on one line. That is probably >> easier. I like the separate entries technique simply because I find >> it easier to read myself or quickly comment out an entry. > >I

Re: Updating py27-* ports

Hello. As for packages that require py27-*, I think it's better to leave it to poudriere. Then I think the py27-* package can be cleaned up with the following command. # If you are running poudriere bulk as follows. # poudriere bulk -f ~/pkglist -j name poudriere pkgclean -f ~/pkglist -j name

Re: Updating py27-* ports

On 04 Jul 2020, at 08:30, Carmel wrote: > I see that you are putting it all on one line. That is probably easier. > I like the separate entries technique simply because I find it easier > to read myself or quickly comment out an entry. I agree that separate lines have advantages. When making chan

Re: Updating py27-* ports

## Carmel (carmel...@outlook.com): > DEFAULT_VERSIONS+=python2=3.7 Forcing python 2 to be python 3.7 will probably break - as far as I can see, there're safeguards in place which will prevent this. In most cases, the python2 dependency is there because upstream hasn't updated their code yet. (Tha

Re: Updating py27-* ports

On 2020-07-04 16:30, Carmel wrote: What I have never been able to get a definitive answer to is exactly what the "+" does or if it is even needed, I have seen 'default_versions" both with and without it. The way I understand it, += appends. Thus: FOO=bar FOO+=quux will result in FOO having the

Re: Updating py27-* ports

Hi! > >> update these ports? I was thinking of placing this in the > >> "poudriere.d/make.conf" file: [...] > What I have never been able to get a definitive answer to is exactly > what the "+" does or if it is even needed, I have seen > 'default_versions" both with and without it. The file is re

Re: Updating py27-* ports

On Sat, 4 Jul 2020 16:11:29 +0200, Kurt Jaeger stated: >Hi! > >> I use 'poudriere' to maintain my ports. I still have a few ports that >> depend on the depreciated py27. What is the recommended method to >> update these ports? I was thinking of placing this in the >> "poudriere.d/make.conf" file: >

Re: Updating py27-* ports

Hi! > I use 'poudriere' to maintain my ports. I still have a few ports that > depend on the depreciated py27. What is the recommended method to > update these ports? I was thinking of placing this in the > "poudriere.d/make.conf" file: > > DEFAULT_VERSIONS+=python=3.7 > DEFAULT_VERSIONS+=python2=

Updating py27-* ports

I use 'poudriere' to maintain my ports. I still have a few ports that depend on the depreciated py27. What is the recommended method to update these ports? I was thinking of placing this in the "poudriere.d/make.conf" file: DEFAULT_VERSIONS+=python=3.7 DEFAULT_VERSIONS+=python2=3.7 DEFAULT_VERSION

Re: Json-c, bind, and updating

On 10/06/20 03:18, Steve Kargl wrote: On Tue, Jun 09, 2020 at 11:45:28PM -0600, @lbutlr wrote: This has happened in the past, but it happened again this weekend when an update to ;ibjson-c did not update bind, rendering bind unable to load libjson-c.so.4 because it had been replaced with libjs

Re: Json-c, bind, and updating

On Tue, Jun 09, 2020 at 11:45:28PM -0600, @lbutlr wrote: > This has happened in the past, but it happened again this weekend when an > update to ;ibjson-c did not update bind, rendering bind unable to load > libjson-c.so.4 because it had been replaced with libjson-c.so.5. > man libmap.conf Thi

Json-c, bind, and updating

This has happened in the past, but it happened again this weekend when an update to ;ibjson-c did not update bind, rendering bind unable to load libjson-c.so.4 because it had been replaced with libjson-c.so.5. In a rush I simply linked libjson-c.so.4 -> libjson-c.so.5 and all is happy AFAICT. W

Updating Samba

The latest stable release of Samba is "4.11.2". The newest port version is "4.10.10". Are there plans to update Samba to the latest stable release or is there a specific reason that it cannot be done at this time? -- Carmel ___ freebsd-ports@freebsd.org

Re: [Circumvented] Problem updating gimp-app-2.10.12_2, 1 to gimp-app-2.10.12_3, 1

On Mon, Sep 2, 2019 at 4:41 AM David Wolfskill wrote: > On Mon, Sep 02, 2019 at 01:34:50PM +0200, Walter Schwarzenfeld wrote: > > Try recompile graphics/libspiro. > > > > Thanks. As noted, I did (along with graphics/gegl), and that appears to > have circumvented the problem. > > I wrote the

Re: [Circumvented] Problem updating gimp-app-2.10.12_2,1 to gimp-app-2.10.12_3,1

Sorry,seems I only read the half of the post. ___ 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: [Circumvented] Problem updating gimp-app-2.10.12_2,1 to gimp-app-2.10.12_3,1

On Mon, Sep 02, 2019 at 01:34:50PM +0200, Walter Schwarzenfeld wrote: > Try recompile graphics/libspiro. > Thanks. As noted, I did (along with graphics/gegl), and that appears to have circumvented the problem. I wrote the note so that others might make use of my experience: the issue is res

Re: [Circumvented] Problem updating gimp-app-2.10.12_2,1 to gimp-app-2.10.12_3,1

Try recompile graphics/libspiro. ___ 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"

[Circumvented] Problem updating gimp-app-2.10.12_2,1 to gimp-app-2.10.12_3,1

I update base FreeBSD and the installed ports on my laptop daily; usually, this works out quite well (which I think says something very positive about FreeBSD). This morning, the attempt to update graphics/gimp-app failed; I was able to get it to work by manually re-building and -installing graphi

Re: Updating Samba

On 2019-06-20 14:17, Carmel NY wrote: > The 20190619 entry in "UPDATING" recommends certain actions for > updating Samba4[6-8] utilizing either 'portmaster' or 'portupgrade'. > Are there4 any special actions that have to be taken if utilizing Poudriere b

Updating Samba

The 20190619 entry in "UPDATING" recommends certain actions for updating Samba4[6-8] utilizing either 'portmaster' or 'portupgrade'. Are there4 any special actions that have to be taken if utilizing 'poudriere'? Thanks! -- Carmel NY _

devel/autogen upgrade will fail. UPDATING needs an entry

Upgrading devel/autogen will fail as the build procedure will attempt to run the new version, but will find the old library version and error. An entry in UPDATING to the effect that "pkg delete autogen" should by run and then autogen should be reinstalled. This does not apply up upgr

Re: Updating Postfix

On 21 Mar 2019, at 06:25, Carmel NY wrote: > I am just inquiring to find out if there is any specific reason for > these ports not being updated. In the past, the releases and the > FreeBSD ports system were kept virtually in sync. There was some talk when 3.4.0 came out about withdrawing it, and

Updating Postfix

Both Postfix 3.4 stable release and Postfix 3.5 experimental release were released over a month ago. In fact, the stable release is now at Postfix 3.4.4. The posts system still has postfix-3.3.3,1 as the stable release and Postfix-3.4.20181202,5 as the development release. I am just inquiring to

Re: Updating the sysutils/paladin port

Hi! > sysutils/paladin has version 2.0.0 available; the port could use updating. > The PR is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236111; hoping > we can get a committer to look at it sometime soon. Done. -- p...@opsec.eu+49 171 3101372On

Updating the sysutils/paladin port

sysutils/paladin has version 2.0.0 available; the port could use updating. The PR is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236111; hoping we can get a committer to look at it sometime soon. ___ freebsd-ports@freebsd.org mailing list https

Re: Updating perl

On 14/12/2018 10:44, Carmel NY wrote: > Using poudriere, I attempted to update my system to the new "perl 5.28". I > made the necessary changes in the "make.conf" files and then attempted to run > poudriere. At the very beginning of the run, poudriere issued a warning that > "security/py-certbot |

Re: Updating perl

On 14/12/2018 9:44 pm, Carmel NY wrote: Using poudriere, I attempted to update my system to the new "perl 5.28". I made the necessary changes in the "make.conf" files and then attempted to run poudriere. At the very beginning of the run, poudriere issued a warning that "security/py-certbot | py36

Re: Updating poudriere jail

On Fri 2018-12-14 11:13:16 UTC+, Carmel NY (carmel...@outlook.com) wrote: > ># build Postfix with Cyrus SASL support > >mail_postfix_SET=SASL > > > >Of course, be sure to point your FreeBSD 12.0-REL systems to your new 12.0 > >repo, instead of your old 11.x repo. > > > >Regards > >Andrew > >

Re: Updating poudriere jail

On Fri, 14 Dec 2018 07:29:18 +1100, andrew clarke stated: >On Thu 2018-12-13 19:43:30 UTC+, Carmel NY (carmel...@outlook.com) wrote: > >> I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the >> new version 12, what do I have to do to update the poudriere jail? Plus, >> if

Updating perl

Using poudriere, I attempted to update my system to the new "perl 5.28". I made the necessary changes in the "make.conf" files and then attempted to run poudriere. At the very beginning of the run, poudriere issued a warning that "security/py-certbot | py36-certbot-0.29.1_1,1" failed. This is from

Re: Updating poudriere jail

On 14/12/2018 05:41, Kurt Jaeger wrote: I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the new version 12, what do I have to do to update the poudriere jail? Plus, if I do update, will I have to rebuild all of my installed applications? I had a jail '120' created as po

Re: Updating poudriere jail

Hi! > I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the > new version 12, what do I have to do to update the poudriere jail? Plus, if I > do update, will I have to rebuild all of my installed applications? I had a jail '120' created as poudriere jail -c -v 12.0-RC3 -a am

Re: Updating poudriere jail

On Thu 2018-12-13 19:43:30 UTC+, Carmel NY (carmel...@outlook.com) wrote: > I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the > new version 12, what do I have to do to update the poudriere jail? Plus, if I > do update, will I have to rebuild all of my installed applica

Re: Updating poudriere jail

On Thu, Dec 13, 2018 at 1:01 PM Carmel NY wrote: > > On Thu, 13 Dec 2018 12:49:07 -0700, Adam Weinberger stated: > > >On Thu, Dec 13, 2018 at 12:43 PM Carmel NY wrote: > >> > >> I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the > >> new version 12, what do I have to do to

Re: Updating poudriere jail

On Thu, 13 Dec 2018 12:49:07 -0700, Adam Weinberger stated: >On Thu, Dec 13, 2018 at 12:43 PM Carmel NY wrote: >> >> I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the >> new version 12, what do I have to do to update the poudriere jail? Plus, >> if I do update, will I hav

Re: Updating poudriere jail

On Thu, Dec 13, 2018 at 12:43 PM Carmel NY wrote: > > I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the > new version 12, what do I have to do to update the poudriere jail? Plus, if I > do update, will I have to rebuild all of my installed applications? It's not really po

Updating poudriere jail

I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the new version 12, what do I have to do to update the poudriere jail? Plus, if I do update, will I have to rebuild all of my installed applications? Thanks :) -- Carmel ___ freebsd

Updating "mysql80-server" port

My daily security run summary includes the following: Checking for packages with security vulnerabilities: Database fetched: Sun Dec 9 03:18:49 EST 2018 mysql80-server-8.0.12_2 This has been included in the report for quite some time now. After doing some quick checking, I find that MySQL 8.0.13

Re: Unable to update repository FreeBSD Error updating repositories

Hi! > > Soon, although it's unclear, when. Give the team a few more days or > > build yourself your own repo using poudriere ? > poudriere - or synth, which might be more user-friendly? I'm using poudriere, because synth is limited to those architectures where ada is available. -- p...@opsec.e

Re: Unable to update repository FreeBSD Error updating repositories

On 10/22/18 9:39 AM, Kurt Jaeger wrote: Soon, although it's unclear, when. Give the team a few more days or build yourself your own repo using poudriere ? poudriere - or synth, which might be more user-friendly? -- Rebecca Cran ___ freebsd-port

Re: Unable to update repository FreeBSD Error updating repositories

Andy opened a PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232530 ___ 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: Unable to update repository FreeBSD Error updating repositories

Hi! > is "translated" in ...pkg.FreeBSD.org/FreeBSD:13:amd64/latest... > but currently http://pkg.FreeBSD.org/ hasn't "FreeBSD:13:amd64". > The question is: When will be it added? Soon, although it's unclear, when. Give the team a few more days or build yourself your own repo using poudriere ?

Re: Unable to update repository FreeBSD Error updating repositories

> What does "Warning: Major OS version upgrade detected" mean? And what > should you do about it? Thanks in advance, appreciate any help. > > # pkg-static install -f pkg > pkg-static: Warning: Major OS version upgrade detected. Running > "pkg-static ins

Re: Unable to update repository FreeBSD Error updating repositories

This http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest/ side seems not to exist on http://pkg.freebsd.org/. Maybe, you try to change the ABI in your /etc/pkg/repos/FreeBSD.conf to 12 install "pkg" and if it is successful recomp

Unable to update repository FreeBSD Error updating repositories

r OS version upgrade detected. Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... pkg-static: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory pkg-static: http://pkg.FreeBSD.org/FreeBSD

Re: Wrong hint while updating p5-Net-SMTP-SSL

On Mon, Aug 20, 2018 at 11:53:07AM +0200, free...@doom-labs.net wrote: > Ahoi! > > If you try upgrading mentioned port you get: > ---8<-- > > ===>>> p5-Net-SMTP-SSL-1.04 > > ===>>> The mail/p5-Net-SMTP-SSL port has been deleted: Has expired: > Deprecated by upstream, use Net::SMTP instead > ===>

Wrong hint while updating p5-Net-SMTP-SSL

Ahoi! If you try upgrading mentioned port you get: ---8<-- ===>>> p5-Net-SMTP-SSL-1.04 ===>>> The mail/p5-Net-SMTP-SSL port has been deleted: Has expired: Deprecated by upstream, use Net::SMTP instead ===>>> Aborting update ---8<--- I guess this should be either NET:SMTPS or (even better) m

Re: Request clear steps for updating own port

to upgrade the port from 1.6 to 1.7 so as to > >reflect new names of kde4 packages. > > > >I seem to have completely lost memory of what I have to do to get the > >port updated properly in FreeBSD ports. Can someone be kind enough to > >guide me what steps are needed for upda

Re: Request clear steps for updating own port

memory of what I have to do to get the >port updated properly in FreeBSD ports. Can someone be kind enough to >guide me what steps are needed for updating one's own port? > >My port uses GitHub and is located at: >https://github.com/bourne-again/mkdesktop > >Essentially, I

Request clear steps for updating own port

someone be kind enough to guide me what steps are needed for updating one's own port? My port uses GitHub and is located at: https://github.com/bourne-again/mkdesktop Essentially, I have an updated Makefile/distinfo which I need to get merged into FreeBSD ports. I have updated the

Re: Updating www/py-recaptcha

On 22/04/2018 22:14, Dan Mahoney (Gushi) wrote: > 2) I can't figure out how to tell what packages (if any) depend on this > -- I know how to do it with *installed* packages, but not *all packages > total*, so I know who to reach out to for having them update.  Can > someone clue me in? cd /usr/p

Re: Updating www/py-recaptcha

On 2018-04-23 01:44:27 (+0430), Dan Mahoney (Gushi) wrote: This port is pretty much useless as a dependency, since Google has now deprecated the v1 captcha (which is all this code can do). Oh wow. I completely forgot I'm maintaining this. I haven't had a use for it in ages. It's been fixed

Updating www/py-recaptcha

All, This port is pretty much useless as a dependency, since Google has now deprecated the v1 captcha (which is all this code can do). It's been fixed here: https://github.com/redhat-infosec/python-recaptcha (I.e. the module name this code generates uses the same import name, but any underly

Re: UPDATING RSS feed

On 03/31/18 19:34, Kevin Oberman wrote: I moved to: http://updating.kojevnikov.com/ Thanks a lot! bye av. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "

Re: Perl version change and ports/UPDATING

On Sat, Mar 31, 2018 at 04:23:54PM -0700, Kevin Oberman wrote: > On Sat, Mar 31, 2018 at 7:25 AM, David Wolfskill > wrote: > ... > > But "pkg updating -i" fails to display the 20180330 entry for me; > > it does show entries for some(?) other ports I have inst

Re: Perl version change and ports/UPDATING

On Sat, Mar 31, 2018 at 7:25 AM, David Wolfskill wrote: > While the actual change to the Perl version works fine for me, I > find that invoking "pkg updating" fails to display the 20180330 > ports/UPDATING entry. I got lucky, because I found out about the > change

Re: UPDATING RSS feed

On Fri, Mar 30, 2018 at 9:45 AM, Andrea Venturoli wrote: > Hello. > > I used to read ports' UPDATING via RSS, but now the feed I was using (from > versia) seems to be gone. > > Anyone knows of another one? > > I looked into FreshPorts, but didn't find a way t

UPDATING RSS feed

Hello. I used to read ports' UPDATING via RSS, but now the feed I was using (from versia) seems to be gone. Anyone knows of another one? I looked into FreshPorts, but didn't find a way to get this specific feed. bye & Tha

Perl version change and ports/UPDATING

While the actual change to the Perl version works fine for me, I find that invoking "pkg updating" fails to display the 20180330 ports/UPDATING entry. I got lucky, because I found out about the change a different way. I maintain /usr/ports as an SVN working copy, using a local priv

Re: A note on updating security/gnupg20 -> gnupg

y updated the list of packages to build on my build machine, to replace security/gnupg20 by security/gnupg.) My concern about that last point is that if I were only updating ports via "pkg upgrade", I would not have known that security/gnupg20 no longer existed (well, unless I read the svn-p

A note on updating security/gnupg20 -> gnupg

hine, to replace security/gnupg20 by security/gnupg.) My concern about that last point is that if I were only updating ports via "pkg upgrade", I would not have known that security/gnupg20 no longer existed (well, unless I read the svn-ports-head list, or polled the svn log for ports/securi

  1   2   3   4   5   6   7   8   9   10   >