Fw: pkgng and pkgdb

hi, all: i used to use "pkgdb -Ff" along with old wonderful "pkg_whatever" to keep my freebsd station healthy. but i was told the new era of pkg is coming and so i made switch to pkgng. the question is: what is the equivalent of "pkgdb -Ff"? for pkg? for "

Re: question about pkgng

On Sun, February 2, 2014 4:58 pm, Waitman Gobble wrote: > Hi, > > > I updated my laptop to: > > > # uname -a > FreeBSD akira.waitman.net 11.0-CURRENT FreeBSD 11.0-CURRENT #1: Sun Feb 2 > 21:45:49 PST 2014 r...@akira.waitman.net:/usr/obj/usr/src/sys/AKIRA > amd64 > Scratch this question, it

question about pkgng

2014) Then I ran 'pkg update' and 'pkg upgrade' But when I went to install a new port I received errors about boost, I used pkgng to update boost. # pkg install boost-all Updating repository catalogue The following 5 packages will be installed: Upgrading icu:

Re: PKGNG: virtualbox-ose wants lang/gcc AND pdftk wants lang/gcc46

+--On 12 janvier 2014 03:00:53 +0100 vermaden wrote: | Where is the logic?I can not install lang/gcc and lang/gcc46 both at the | same time.Any hints? How to use BOTH virtualbox and pdftk using | PKGNG? Hum, I fixed this on January 4th[1], so it should be fixed in the current packages set. 1

Re: PKGNG: virtualbox-ose wants lang/gcc AND pdftk wants lang/gcc46

On Sun, 12 Jan 2014 03:00:53 +0100 vermaden wrote: > Where is the logic?I can not install lang/gcc and lang/gcc46 both at > the same time.Any hints? How to use BOTH virtualbox and pdftk using > PKGNG? Please send ports/package related emails to the freebsd-ports mailing list. To an

PKGNG: virtualbox-ose wants lang/gcc AND pdftk wants lang/gcc46

Where is the logic?I can not install lang/gcc and lang/gcc46 both at the same time.Any hints? How to use BOTH virtualbox and pdftk using PKGNG?Regards,vermaden# pkg install virtualbox-oseUpdating repository catalogueThe following 50 packages will be installed:    Reinstalling mkfontdir

Re: [HEADSUP] recursive dependency registration is gone for pkgng users

From: Baptiste Daroussin Subject: [HEADSUP] recursive dependency registration is gone for pkgng users Date: Sat, 28 Dec 2013 15:52:50 +0100 > as a side effect, > tinderbox and poudriere users do need to rebuild all their packages from > scratch. Does this mean rebuilding is necessar

Re: [HEADSUP] recursive dependency registration is gone for pkgng users

On Sun, Dec 29, 2013 at 01:31:22AM +0900, Yasuhiro KIMURA wrote: > From: Baptiste Daroussin > Subject: [HEADSUP] recursive dependency registration is gone for pkgng users > Date: Sat, 28 Dec 2013 15:52:50 +0100 > > > as a side effect, > > tinderbox and poudriere user

[HEADSUP] recursive dependency registration is gone for pkgng users

Hi all, With r337100, we do stop registering recursively the dependency. As a result the dependency tracking is better and finer grain, as a side effect, tinderbox and poudriere users do need to rebuild all their packages from scratch. For poudriere pass the -c to the bulk option. regards, Bapt

Re: [Review] bsdconfig pkgng integration

On Nov 6, 2013, at 5:13 PM, Teske, Devin wrote: > > On Nov 6, 2013, at 5:02 PM, Glen Barber wrote: > >> On Thu, Nov 07, 2013 at 12:48:02AM +, Teske, Devin wrote: >>> I think that you're thinking that: >>> >>> pkg.eu.freebsd.org >>> pkg.us-east.freebsd.org >>> pkg.us-west.freebsd.org >>> >

Re: [Review] bsdconfig pkgng integration

On Nov 6, 2013, at 5:02 PM, Glen Barber wrote: > On Thu, Nov 07, 2013 at 12:48:02AM +, Teske, Devin wrote: >> I think that you're thinking that: >> >> pkg.eu.freebsd.org >> pkg.us-east.freebsd.org >> pkg.us-west.freebsd.org >> >> Will somehow change? > > I think you're thinking they *won't

Re: [Review] bsdconfig pkgng integration

On Thu, Nov 07, 2013 at 12:48:02AM +, Teske, Devin wrote: > I think that you're thinking that: > > pkg.eu.freebsd.org > pkg.us-east.freebsd.org > pkg.us-west.freebsd.org > > Will somehow change? I think you're thinking they *won't* change. Don't assume. Glen pgpYvjMEXknes.pgp Descriptio

Re: [Review] bsdconfig pkgng integration

On Nov 6, 2013, at 4:22 PM, Glen Barber wrote: > On Thu, Nov 07, 2013 at 12:13:49AM +, Teske, Devin wrote: >> So what hard-coding are you talking about? >> > > You are trying to hard-code hostnames for a service in the FreeBSD > src/ tree, when it is *absolutely* unnecessary. > Not all ho

Re: [Review] bsdconfig pkgng integration

On Thu, Nov 07, 2013 at 12:13:49AM +, Teske, Devin wrote: > So what hard-coding are you talking about? > You are trying to hard-code hostnames for a service in the FreeBSD src/ tree, when it is *absolutely* unnecessary. > You talk about how "if a node goes down we take it out of DNS" > but t

Re: [Review] bsdconfig pkgng integration

On Nov 6, 2013, at 4:01 PM, Glen Barber wrote: > On Wed, Nov 06, 2013 at 11:53:28PM +, Teske, Devin wrote: >>> And if we need to change something with the infrastructure, we now have >>> to tell people that this was done. You are putting hard-coded >>> limitations on us. Don't. >>> >> >>

Re: [Review] bsdconfig pkgng integration

On Nov 6, 2013, at 3:53 PM, Teske, Devin wrote: > > On Nov 6, 2013, at 3:44 PM, Glen Barber wrote: > >> On Wed, Nov 06, 2013 at 11:37:43PM +, Teske, Devin wrote: You do not need to show any servers except pkg.FreeBSD.org. >>> >>> Bapt *just* got finished telling me in IRC that we shou

Re: [Review] bsdconfig pkgng integration

On Wed, Nov 06, 2013 at 11:53:28PM +, Teske, Devin wrote: > > And if we need to change something with the infrastructure, we now have > > to tell people that this was done. You are putting hard-coded > > limitations on us. Don't. > > > > I disagree. > > You're making the argument for "what

Re: [Review] bsdconfig pkgng integration

On Nov 6, 2013, at 3:44 PM, Glen Barber wrote: > On Wed, Nov 06, 2013 at 11:37:43PM +, Teske, Devin wrote: >>> You do not need to show any servers except pkg.FreeBSD.org. >> >> Bapt *just* got finished telling me in IRC that we should also list: >> >> pkg.eu >> pkg.us-* >> > > Why? > >>

Re: [Review] bsdconfig pkgng integration

On Wed, Nov 06, 2013 at 11:37:43PM +, Teske, Devin wrote: > > You do not need to show any servers except pkg.FreeBSD.org. > > Bapt *just* got finished telling me in IRC that we should also list: > > pkg.eu > pkg.us-* > Why? > Which I assume to be the same make/model of pkg.f.o (does not >

Re: [Review] bsdconfig pkgng integration

On Nov 6, 2013, at 3:32 PM, Glen Barber wrote: > On Wed, Nov 06, 2013 at 11:28:25PM +, Teske, Devin wrote: >> We do not ever want to display the contents of the SVR record in the list. >> There are multiple pkg*.freebsd.org SVR zones. >> > > You do not need to show any servers except pkg.Fr

Re: [Review] bsdconfig pkgng integration

On Wed, Nov 06, 2013 at 11:28:25PM +, Teske, Devin wrote: > We do not ever want to display the contents of the SVR record in the list. > There are multiple pkg*.freebsd.org SVR zones. > You do not need to show any servers except pkg.FreeBSD.org. In fact, you can use that by default, and not

Re: [Review] bsdconfig pkgng integration

On Nov 6, 2013, at 3:19 PM, Allan Jude wrote: > On 2013-11-06 18:15, Teske, Devin wrote: >> On Nov 6, 2013, at 3:02 PM, Allan Jude wrote: >> >>> On 2013-11-06 13:32, Teske, Devin wrote: Subject says it all. I need a review on the attached patch. Come on, you know you w

Re: [Review] bsdconfig pkgng integration

On 2013-11-06 18:15, Teske, Devin wrote: > On Nov 6, 2013, at 3:02 PM, Allan Jude wrote: > >> On 2013-11-06 13:32, Teske, Devin wrote: >>> Subject says it all. >>> >>> I need a review on the attached patch. >>> >>> Come on, you know you want to... >>> >> I think you missed something, you attached a

Re: [Review] bsdconfig pkgng integration

On Nov 6, 2013, at 3:02 PM, Allan Jude wrote: > On 2013-11-06 13:32, Teske, Devin wrote: >> Subject says it all. >> >> I need a review on the attached patch. >> >> Come on, you know you want to... >> > I think you missed something, you attached a 1 line diff > Oh I see... too much to review.

Re: [Review] bsdconfig pkgng integration

On 2013-11-06 13:32, Teske, Devin wrote: > Subject says it all. > > I need a review on the attached patch. > > Come on, you know you want to... > I think you missed something, you attached a 1 line diff -- Allan Jude signature.asc Description: OpenPGP digital signature

[Review] bsdconfig pkgng integration

Subject says it all. I need a review on the attached patch. Come on, you know you want to... -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not d

Re: Plugins support in pkgng

That's very nice, but I still prefer pkg_cleanup as you don't have to go one by one. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-Plugins-support-in-pkgng-tp5739664p5858340.html Sent from the freebsd-current mailing list archive at

Re: Official FreeBSD Binary Packages now available for pkgng

On Sat, 02 Nov 2013 12:28:06 + Matthew Seaman wrote: > > Which is not always true, especially in heavily firewalled > > environments. > > I feel no obligation to do anything to encourage people that > deliberately break the DNS. They've made their bed, and now they have > to lie in it. In

Re: Official FreeBSD Binary Packages now available for pkgng

Am 02/11/13 23:19, schrieb Mark Felder: On Nov 2, 2013, at 3:27 PM, Adrian Chadd wrote: A lot of HTTP infrastructure lives on anycast DNS, HTTP redirects and geoip records. Saying it's broken and not feasible is nonsense. More specifically what I was referring to was the fact that tradition

Re: Official FreeBSD Binary Packages now available for pkgng

On Nov 2, 2013, at 3:27 PM, Adrian Chadd wrote: > A lot of HTTP infrastructure lives on anycast DNS, HTTP redirects and > geoip records. Saying it's broken and not feasible is nonsense. More specifically what I was referring to was the fact that traditionally HTTP failover with round-robin A r

Re: Official FreeBSD Binary Packages now available for pkgng

quot;all" you have to do is require all the servers in your farm to handle requests for 'pkg.freebsd.org' rather than 'somethinguniqueperhost.freebsd.org' and then teach pkgng to actually issue requests for that, and caching will mostly just work again. Right now you're

Re: Official FreeBSD Binary Packages now available for pkgng

Am 02.11.2013 11:50, schrieb Matthew Seaman: > On 02/11/2013 10:15, Matthias Andree wrote: >> I understand from Eric's pist that the issue is that through his >> limiting proxies, the SRV are not available at all so he does not even >> get to the point where he could get the pkgN.nyi.freebsd.org >>

Re: Official FreeBSD Binary Packages now available for pkgng

On Nov 2, 2013, at 11:54 AM, Adrian Chadd wrote: > You're using a DNS feature which > isn't well adopted/supported and you haven't provided a fallback > legacy, well tested path. But SRV has been widely deployed since… before 2000? It’s literally the backbone of Active Directory deployments. H

Re: Official FreeBSD Binary Packages now available for pkgng

ects to cope. You're using a DNS feature which isn't well adopted/supported and you haven't provided a fallback legacy, well tested path. In short, you've taken the least supported paths, glued it into the least HTTP caching scalable paths and not created a suitable fallback. I hate

Re: Official FreeBSD Binary Packages now available for pkgng

On Sat, 02 Nov 2013 09:01:56 -0500, Eric van Gyzen wrote: > On 11/02/2013 07:28 AM, Matthew Seaman wrote: >> I feel no obligation to do anything to encourage people that >> deliberately break the DNS. They've made their bed, and now they have >> to lie in it. > > Eric Camachat didn't break the

Re: Official FreeBSD Binary Packages now available for pkgng

p proxies also for https urls. This all works based on the assumption that no direct dns lookups are required on the machines itself but all dns stuff is done on the proxy. Your description makes me believe that this won't work for pkgng. So it's not that people in the real world break their

Re: Official FreeBSD Binary Packages now available for pkgng

Hi! > On 02/11/2013 10:15, Matthias Andree wrote: > > I understand from Eric's pist that the issue is that through his > > limiting proxies, the SRV are not available at all so he does not even > > get to the point where he could get the pkgN.nyi.freebsd.org > > name

Re: Official FreeBSD Binary Packages now available for pkgng

On 11/02/2013 07:28 AM, Matthew Seaman wrote: On 02/11/2013 11:37, Kurt Jaeger wrote: Hi! On 02/11/2013 10:15, Matthias Andree wrote: I understand from Eric's pist that the issue is that through his limiting proxies, the SRV are not available at all so he does not even get to the point where

Re: Official FreeBSD Binary Packages now available for pkgng

On 02/11/2013 11:37, Kurt Jaeger wrote: > Hi! > >> On 02/11/2013 10:15, Matthias Andree wrote: >>> I understand from Eric's pist that the issue is that through his >>> limiting proxies, the SRV are not available at all so he does not even >>> get to the point where he could get the pkgN.nyi.freebs

Re: Official FreeBSD Binary Packages now available for pkgng

On 02/11/2013 10:15, Matthias Andree wrote: > I understand from Eric's pist that the issue is that through his > limiting proxies, the SRV are not available at all so he does not even > get to the point where he could get the pkgN.nyi.freebsd.org > name back. That doe

Re: Official FreeBSD Binary Packages now available for pkgng

Matthew Seaman schrieb: >On 02/11/2013 01:55, Eric van Gyzen wrote: >> This kind of proxy configuration is not uncommon. It would be >awesome >> if this would Just Work. It would remove an impediment to adoption, >> which is especially important in the kind of environments that have >this >> k

Re: Official FreeBSD Binary Packages now available for pkgng

On 02/11/2013 01:55, Eric van Gyzen wrote: > This kind of proxy configuration is not uncommon. It would be awesome > if this would Just Work. It would remove an impediment to adoption, > which is especially important in the kind of environments that have this > kind of proxy configuration. > > S

Re: Official FreeBSD Binary Packages now available for pkgng

On 10/31/2013 05:21 PM, Freddie Cash wrote: >tried pkg.freebsd.org it got below. >Our DNS server can resolve proxy server only. >Only proxy server can resolve internet sites, this is how our company force >all traffic went through proxy server. > >Eric > >Network Error (dns_server_failure) > >

Re: Official FreeBSD Binary Packages now available for pkgng

On Thu, Oct 31, 2013 at 3:15 PM, Eric Camachat wrote: > browsing www.freebsd.org worked fine. > tried pkg.freebsd.org it got below. > Our DNS server can resolve proxy server only. > Only proxy server can resolve internet sites, this is how our company force > all traffic went through proxy server.

Re: Official FreeBSD Binary Packages now available for pkgng

browsing www.freebsd.org worked fine. tried pkg.freebsd.org it got below. Our DNS server can resolve proxy server only. Only proxy server can resolve internet sites, this is how our company force all traffic went through proxy server. Eric Network Error (dns_server_failure) Your request could

Re: Official FreeBSD Binary Packages now available for pkgng

On 31/10/2013 21:38, Bryan Drewery wrote: > On 10/31/2013 4:25 PM, Eric Camachat wrote: >> > Same result, neither pkg+http:// nor http+pkg:// worked with proxy server. >> > > Top-posting kills babies > > pkg+http is NOT supported in 1.1 and as I said, changes nothing. Also the request that pkg(8

Re: Official FreeBSD Binary Packages now available for pkgng

On 10/31/2013 3:47 PM, Eric Camachat wrote: > It doesn't work with our (microsoft) proxy server, see below. > > root@basay:/usr/local/etc/pkg/repos # pkg update -f > Updating repository catalogue > pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/digests.txz: Service > Unavailable > pkg: No di

Re: Official FreeBSD Binary Packages now available for pkgng

On 31/10/2013 21:04, Allan Jude wrote: > I wonder if the http+pkg:// protocol can solve this, likely will require > a patch to fetch to implement the logic to do the dns lookup and make > the proxies request for the real hostname It's pkg+http:// or pkg+https:// or pkg+ssh:// or -- well, you get t

Re: Official FreeBSD Binary Packages now available for pkgng

an now either continue to use ports with >> portmaster/portupgrade, as >>>>>>> before or switch to using binary packages only. >>>>>>> >>>>>>> >>>>>>> To use binary packages: >>>>>>> >>>

Re: Official FreeBSD Binary Packages now available for pkgng

using binary packages only. > >>>>> > >>>>> > >>>>> To use binary packages: > >>>>> > >>>>> 1. Ensure your pkg(8) is up-to-date. 'pkg -v' should say at least > >>>>>1.1.4_8. If it does no

Re: Official FreeBSD Binary Packages now available for pkgng

>>>>1.1.4_8. If it does not, first upgrade from ports. >>>>> 2. Remove any repository-specific configuration from >>>>>/usr/local/etc/pkg.conf, such as PACKAGESITE, MIRROR_TYPE, PUBKEY. >>>>>If this leaves your pkg.conf empty, just

Re: Official FreeBSD Binary Packages now available for pkgng

mirror_type: "srv", >>> enabled: "yes" >>> } >>> >>> * Note that pkg.FreeBSD.org does not have a browsable web page on it and >>> does not have a DNS A record. This is intended as it is an SRV host. >>> pkg(8) knows how to prop

Re: Official FreeBSD Binary Packages now available for pkgng

pkg.FreeBSD.org does not have a browsable web page on it and >> does not have a DNS A record. This is intended as it is an SRV host. >> pkg(8) knows how to properly use it. You can use 'pkg search' to browse >> the available packages in the repository. >> >> Mirrors you m

Re: Official FreeBSD Binary Packages now available for pkgng

it and > does not have a DNS A record. This is intended as it is an SRV host. > pkg(8) knows how to properly use it. You can use 'pkg search' to browse > the available packages in the repository. > > Mirrors you may use instead of the global pkg.FreeBSD.org: > > pkg.eu

Official FreeBSD Binary Packages now available for pkgng

ws how to properly use it. You can use 'pkg search' to browse the available packages in the repository. Mirrors you may use instead of the global pkg.FreeBSD.org: pkg.eu.FreeBSD.org pkg.us-east.FreeBSD.org pkg.us-west.FreeBSD.org Your system is now ready to use pac

Re: pkgng

According to Adrian Chadd: > .. well, where'd you point it to? On my own machine I generate the packages myself with poudriere because I have multiple jails I update. On a more generic machine, I use pkg-test.freebsd.org. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.f

Re: pkgng

.. well, where'd you point it to? -adrian On 23 August 2013 23:04, Hideki Yamamoto wrote: > Hi, > > I solved my problem by myself. > I update PACKAGESITE in /usr/local/etc/pkg.conf in accordance with > the information in another expert web site. > > --- > > > > 2013/8/24 Hideki Yamamoto > >

Re: pkgng

Hi, I solved my problem by myself. I update PACKAGESITE in /usr/local/etc/pkg.conf in accordance with the information in another expert web site. --- 2013/8/24 Hideki Yamamoto > > Hi, > > As I moved from old pkg_xxx to pkg2ng. > But I cannot install any new packages as follows: > > # rm -f

pkgng

Hi, As I moved from old pkg_xxx to pkg2ng. But I cannot install any new packages as follows: # rm -f/var/db/pkg* # pkg2ng # pkg install gs freebsd:9:x86:32, freebsd:9:x86:32, freebsd:9:x86:32, freebsd:9:x86:32, freebsd:9:x86:32, freebsd:9:x86:32 - - - - freebsd:9:x86:32, freebs

[HEADS UP] New pkgng git location

Pkg has moved from http://github.com/pkgng/pkgng to http://github.com/freebsd/pkg Please update any links or git checkouts you have. You can update your git checkout with: > git remote set-url origin git://github.com/freebsd/pkg.git pkgng/pkgng -- Regards, Bryan Drewery signature.

Re: newnfs pkgng database corruption?

a few "portmaster -a" runs without pkgng database corruption. I've not > tested it for very long, but so far, things look good. > > Lars Great thank you I'll activate this for all database located on a network filesystem. Thank you very much! Bapt pgppQ4uGA6loz.pgp Description: PGP signature

Re: newnfs pkgng database corruption?

Hi, On Apr 22, 2013, at 2:56, Baptiste Daroussin wrote: > As anyone been able to test this patch? I've been running with it for a few days. I've done a reinstall of all ports plus a few "portmaster -a" runs without pkgng database corruption. I've not tested

Re: newnfs pkgng database corruption?

the client and server at the > > >time this error occurs, looking at them in wireshark might be > > >useful? > > > > I will try all of those things. > > > > But first, a question that someone who understands pkgng will be able to > > answerr

Re: newnfs pkgng database corruption?

s, but since Error 70 wasn't an errno.h error number, it isn't a stale fh problem and, as such, there isn't any evidence that bits are getting messed with by the network layers. rick > > But first, a question that someone who understands pkgng will be > > able to a

Re: newnfs pkgng database corruption?

disabling that on the > > network interface. Same goes for checksum offload.) > > > > rick > > ps: If you can capture packets between the client and server at the > >time this error occurs, looking at them in wireshark might be > >useful? > > I

Re: newnfs pkgng database corruption?

If you can capture packets between the client and server at the >time this error occurs, looking at them in wireshark might be >useful? I will try all of those things. But first, a question that someone who understands pkgng will be able to answerr: Is this "fake-pkg" pr

Re: newnfs pkgng database corruption?

Lars Eggert wrote: > Hi, > > On Apr 11, 2013, at 1:28, Rick Macklem wrote: > > Error code 70 is ESTALE (or NFSERR_STALE, if you prefer). The server > > replies with that when the file no longer exists. > > > > File locking doesn't stop a file from being removed, as far as I > > know. > > but the

Re: newnfs pkgng database corruption?

On Thu, Apr 11, 2013 at 08:44:01AM +, Eggert, Lars wrote: > Hi, > > On Apr 11, 2013, at 10:30, Baptiste Daroussin wrote: > > First, I think you can recover your database. > > that would be great. > > > Can you try the following command: > > > > # mv /var/db/pkg/local.sqlite /var/db/pkg/bac

Re: newnfs pkgng database corruption?

Hi, On Apr 11, 2013, at 10:30, Baptiste Daroussin wrote: > First, I think you can recover your database. that would be great. > Can you try the following command: > > # mv /var/db/pkg/local.sqlite /var/db/pkg/backup.sqlite > # echo '.dump' | pkg shell /var/db/pkg/backup.sqlite | pkg shell Tha

Re: newnfs pkgng database corruption?

On Thu, Apr 11, 2013 at 05:52:52AM +, Eggert, Lars wrote: > Hi, > > On Apr 11, 2013, at 0:16, Baptiste Daroussin wrote: > > Will you be able to test it? > > yes. (But I will be traveling for the next two weeks and so the turnaround > may be a bit longer than normal.) > > Lars First, I thi

Re: newnfs pkgng database corruption?

Hi, On Apr 11, 2013, at 0:16, Baptiste Daroussin wrote: > Will you be able to test it? yes. (But I will be traveling for the next two weeks and so the turnaround may be a bit longer than normal.) Lars ___ freebsd-current@freebsd.org mailing list http

Re: newnfs pkgng database corruption?

Hi, On Apr 11, 2013, at 1:28, Rick Macklem wrote: > Error code 70 is ESTALE (or NFSERR_STALE, if you prefer). The server > replies with that when the file no longer exists. > > File locking doesn't stop a file from being removed, as far as I know. but the file is still there. Lars

Re: newnfs pkgng database corruption?

Lars Eggert wrote: > Hi, > > on a diskless server, I keep the ports tree and pkgng databases on a > newnfs NFSv4 mount. After a bunch of "portmaster -a" runs, the pkgng > sqlite database appears to get corrupted. For example, when I try to > update an existing port,

Re: newnfs pkgng database corruption?

h NFSv4, the locking system is integrated with the main protocol, it's no > longer separate. > > > If that is the case, there is anyway a bug in pkgng that should catch the > > problem and refuse to operate in such situation, I know sqlite to provide a > > mechanism tha

Re: newnfs pkgng database corruption?

gt; If that is the case, there is anyway a bug in pkgng that should catch the > problem and refuse to operate in such situation, I know sqlite to provide a > mechanism that allow us to be able to catch this, I'm not sure yet to use it. Not sure about that. In case anyone wonders

Re: newnfs pkgng database corruption?

On Wed, Apr 10, 2013 at 07:42:30AM +, Eggert, Lars wrote: > Hi, > > on a diskless server, I keep the ports tree and pkgng databases on a newnfs > NFSv4 mount. After a bunch of "portmaster -a" runs, the pkgng sqlite database > appears to get corrupted. For example

newnfs pkgng database corruption?

Hi, on a diskless server, I keep the ports tree and pkgng databases on a newnfs NFSv4 mount. After a bunch of "portmaster -a" runs, the pkgng sqlite database appears to get corrupted. For example, when I try to update an existing port, this happens: root@five:~ # portmaster port

Re: [HEADS UP] pkgng binary packages regression in 1.0.9. Fixed in 1.0.9_1

On Wed, Mar 20, 2013 at 04:20:02PM +0100, Matthias Gamsjager wrote: > > Due to the security incident, there are still no official FreeBSD > > packages. > > Do you know what the status is on that issue? I'd also like to find out what the status of this is. The packages at: ftp://ftp.freebsd.org

Re: [HEADS UP] pkgng binary packages regression in 1.0.9. Fixed in 1.0.9_1

On 20/03/2013 15:20, Matthias Gamsjager wrote: >> Due to the security incident, there are still no official FreeBSD >> packages. >> > > > Do you know what the status is on that issue? Unchanged so far. No official pkgng packages yet. However, an end to the wait is

Re: [HEADS UP] pkgng binary packages regression in 1.0.9. Fixed in 1.0.9_1

> Due to the security incident, there are still no official FreeBSD > packages. > Do you know what the status is on that issue? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

[HEADS UP] pkgng binary packages regression in 1.0.9. Fixed in 1.0.9_1

This only affects binary-packages-only users. pkg 1.0.9 had a regression with 'pkg update' that will prevent updating your repository. Please skip this version and use 1.0.9_1. This version was only in ports for 7 hours. Due to the security incident, there are still no official FreeBSD packages.

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

On Wed, 2013-03-13 at 09:54 -0500, Bryan Drewery wrote: > On 3/13/2013 8:55 AM, O. Hartmann wrote: > > On Wed, 2013-03-13 at 07:26 -0500, Bryan Drewery wrote: > >> On 3/13/2013 7:21 AM, O. Hartmann wrote: > >>> On Wed, 2013-03-13 at 04:49 -0500, Bryan Drewery wrote: > On 3/13/2013 2:55 AM, O.

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

On 3/13/2013 8:55 AM, O. Hartmann wrote: > On Wed, 2013-03-13 at 07:26 -0500, Bryan Drewery wrote: >> On 3/13/2013 7:21 AM, O. Hartmann wrote: >>> On Wed, 2013-03-13 at 04:49 -0500, Bryan Drewery wrote: On 3/13/2013 2:55 AM, O. Hartmann wrote: > On Tue, 2013-03-12 at 17:16 -0500, Bryan Dre

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

On Wed, 2013-03-13 at 07:26 -0500, Bryan Drewery wrote: > On 3/13/2013 7:21 AM, O. Hartmann wrote: > > On Wed, 2013-03-13 at 04:49 -0500, Bryan Drewery wrote: > >> On 3/13/2013 2:55 AM, O. Hartmann wrote: > >>> On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: > I have just committed a f

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

On 3/13/2013 7:21 AM, O. Hartmann wrote: > On Wed, 2013-03-13 at 04:49 -0500, Bryan Drewery wrote: >> On 3/13/2013 2:55 AM, O. Hartmann wrote: >>> On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: I have just committed a fix to the ports tree for this. >>> >>> Hello. >>> >>> We

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

On Wed, 2013-03-13 at 04:49 -0500, Bryan Drewery wrote: > On 3/13/2013 2:55 AM, O. Hartmann wrote: > > On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: > >> I have just committed a fix to the ports tree for this. > >> > >> > > > > Hello. > > > > Well, I just updated the port's tree a few m

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

On 3/13/2013 2:55 AM, O. Hartmann wrote: > On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: >> I have just committed a fix to the ports tree for this. >> >> > > Hello. > > Well, I just updated the port's tree a few minutes ago and can not see > any changes by now. The port's tree is at >

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: > On 3/10/2013 6:44 AM, O. Hartmann wrote: > > On > > FreeBSD 10.0-CURRENT #0 r248128: Sun Mar 10 10:41:10 CET 2013 > > I receive the error message below when trying to update installed port > > openldap24-sasl-client: > > > > ===> Cleaning

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

On 3/10/2013 6:44 AM, O. Hartmann wrote: > On > FreeBSD 10.0-CURRENT #0 r248128: Sun Mar 10 10:41:10 CET 2013 > I receive the error message below when trying to update installed port > openldap24-sasl-client: > > ===> Cleaning for openldap-sasl-client-2.4.33_1 > ===>>> Waiting on fetch & checksum

CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

On FreeBSD 10.0-CURRENT #0 r248128: Sun Mar 10 10:41:10 CET 2013 I receive the error message below when trying to update installed port openldap24-sasl-client: ===> Cleaning for openldap-sasl-client-2.4.33_1 ===>>> Waiting on fetch & checksum for net/openldap24-sasl-client <<<=== ===> openldap-

Re: Compilation error (pkgng)

On Jan 23, 2013, at 12:14 AM, Alie Tan wrote: > Seems this check-in causing compilation error: > > http://freshbsd.org/commit/freebsd/r245828 > > -nonliteral -c /usr/src/usr.sbin/pkg_install/lib/pkgng.c -o pkgng.o > /usr/src/usr.sbin/pkg_install/lib/pkgng.c:53:45: error: expected ')' >rc

Compilation error (pkgng)

Seems this check-in causing compilation error: http://freshbsd.org/commit/freebsd/r245828 -nonliteral -c /usr/src/usr.sbin/pkg_install/lib/pkgng.c -o pkgng.o /usr/src/usr.sbin/pkg_install/lib/pkgng.c:53:45: error: expected ')' rc = snprintf(pkgngpath, sizeof(pkgngpath) "%s/local.sqlite",

Re: [HEADSUP] current switched by default to pkgng

Hello, Baptiste. You wrote 3 ноября 2012 г., 3:56:22: BD> The BSDmc project (http://code.google.com/p/bsdmc/) uses nanobsd BD> and pkgng, have a look in particular at the BD> following diff: http://code.google.com/p/bsdmc/source/detail?r=75 BD> Maybe you can find something helpfu

Re: [HEADSUP] current switched by default to pkgng

freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" The BSDmc project (http://code.google.com/p/bsdmc/) uses nanobsd and pkgng, have a look in particular a

Re: [HEADSUP] current switched by default to pkgng

th legacy pkg_install > tools. > LS> Did somebody update nanobsd scripts? ;-) > Simple replacing "pkg_add" with "pkg add" doesn't work ;-) > I know some people have some patches for nanobsd that should work with pkgng, but I don't know much about it. regards, Bapt pgpfb3i653wn8.pgp Description: PGP signature

Re: [HEADSUP] current switched by default to pkgng

Hello, Lev. You wrote 2 ноября 2012 г., 23:24:28: BD>> Make sure to read UPDATING (from ports) to correctly migrate your system or find BD>> instruction to make your system still running with legacy pkg_install tools. LS> Did somebody update nanobsd scripts? ;-) Simple replacing "pkg_add" with

Re: [HEADSUP] current switched by default to pkgng

Hello, Baptiste. You wrote 10 октября 2012 г., 17:44:21: BD> Make sure to read UPDATING (from ports) to correctly migrate your system or find BD> instruction to make your system still running with legacy pkg_install tools. Did somebody update nanobsd scripts? ;-) -- // Black Lion AKA Lev Sereb

Re: pkgng and vmware-tools

Actually, I was mentioning their oficial tools, which provided as a cd with esxi. I thought maybe.situatiin like these will require some fake, but working pkg_info (and maybe other tools too, this could.be made as a different wrapper-port) when pkg are used and pkg_legacy not present (they should g

pkgng and vmware-tools

JFYI: When installing vmware tools from ESXI 5.x, their script trying to discover X, and some packages by invoking pkg_info (as it seems): pkg_info: Don't use the pkg_ tools if you are using pkgng pkg_info: no packages installed pkg_info: Don't use the pkg_ tools if you are using pkgn

Re: [HEADSUP] current switched by default to pkgng

;workalike", with many additional > vimpager-1.7.5 Use ViM as a pager > Athlon5000# Yeah, not all packages have -nox11 port due to current infrastructure and design as previously mentioned. You may want to check vim-lite if it fits your need. At least it does for me. Tho

  1   2   3   4   >