Re: pkg 1.4 freeze please test test test!

[Kevin Oberman]

On Sun, Nov 9, 2014 at 11:43 PM, Matthias Andree 
wrote:

> Am 03.11.2014 um 22:48 schrieb Freddie Cash:
> > On Mon, Nov 3, 2014 at 1:40 PM, Hans Petter Selasky 
> wrote:
> >
> >> Is it possible when upgrading a system via "pkg" to selectivly switch
> >> upgrades ON/OFF. For example I have a custom ffmpeg install and would
> like
> >> to keep it every time I do a binary upgrade?
> >>
> >
> >
> > ​# man pkg-lock
> >
> > ;)
> >
> > I believe that's what you are looking for.​  No idea how well it works
> > long-term, though, or if you lock a large number of packages.
>
> It used to refuse portmaster upgrades of a locked port and was thus
> useless for mixed binary packages + portmaster use.  I haven't yet
> checked if pkg 1.4 has fixed this.
>

I don't think that this is considered to be a bug, so it is not fixed. Easy
work-around:
pkg unlock PACKAGE
portmaster PACKAGE
pkg lock PACKAGE

Personally I would prefer if portmaster did the unlock and lock, perhaps
tied to an option, but it's not a big issue as far as I can see. Just an
annoyance.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
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"

Re: pkg 1.4 freeze please test test test!

[Matthias Andree]

Am 03.11.2014 um 22:48 schrieb Freddie Cash:
> On Mon, Nov 3, 2014 at 1:40 PM, Hans Petter Selasky  wrote:
> 
>> Is it possible when upgrading a system via "pkg" to selectivly switch
>> upgrades ON/OFF. For example I have a custom ffmpeg install and would like
>> to keep it every time I do a binary upgrade?
>>
> 
> 
> ​# man pkg-lock
> 
> ;)
> 
> I believe that's what you are looking for.​  No idea how well it works
> long-term, though, or if you lock a large number of packages.

It used to refuse portmaster upgrades of a locked port and was thus
useless for mixed binary packages + portmaster use.  I haven't yet
checked if pkg 1.4 has fixed this.

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

Re: pkg 1.4 freeze please test test test!

[Hans Petter Selasky]

Hi,

Not sure why "pkg upgrade" stopped after #45. Maybe the error code below 
is incorrect or should not cause a halt?


[45/128] Installing linux-c6-hicolor-icon-theme-0.5:   0%
pkg: archive_read_extract(): Can't remove already-existing dir
[45/128] Installing linux-c6-hicolor-icon-theme-0.5: 100%
[45/128] Installing linux-c6-hicolor-icon-theme-0.5: 100%
xxx#

Solved it by manually going into the /usr/ports and installing the port 
in question.


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

Re: pkg 1.4 freeze please test test test!

[Marc UBM]

On Sat, 1 Nov 2014 23:45:49 +0100
Baptiste Daroussin  wrote:

> On Sat, Nov 01, 2014 at 04:13:32PM +0100, Marc UBM wrote:

[snip]

> > 
> > The update is failing for me with:
> > 
> > .../usr/ports/ports-mgmt/pkg-devel# make all install clean
> > ===>  Installing for pkg-1.4.0.a3
> > ===>  Checking if pkg already installed
> > pkg-static: sqlite error while executing DROP INDEX
> > packages_unique;CREATE UNIQUE INDEX packages_unique ON packages(name);
> > in file pkgdb.c:2246: UNIQUE constraint failed: packages.name *** Error
> > code 74
> > 
> > Stop.
> > make[1]: stopped in /usr/ports/ports-mgmt/pkg-devel
> > *** Error code 1
> > 
> > Stop.
> > make: stopped in /usr/ports/ports-mgmt/pkg-devel
> > 
> > 
> > 
> > portmaster fails with:
> > root@ubm:/usr/ports/ports-mgmt/pkg-devel# portmaster -d pkg
> > ===>>> No ORIGIN in /var/db/pkg/pkgconf-0.9.7/+CONTENTS
> > 
> > 
> > ===>>> Cannot continue
> > ===>>> Aborting update
> > 
> > ===>>> Killing background jobs
> > Terminated
> > ===>>> Exiting
> > 
> > make.conf related options:
> > 
> > #enable pkgng (might be superfluous)
> > WITH_PKGNG=yes
> > #enable PKGNG devel
> > WITH_PKGNG=devel
> > 
> > Am I doing something wrong?
> 
> You are doing nothing wrong but that probably means you have ancient packages
> that never got upgraded (in the old time it was allowed to have 2 packages
> installed with the same name) we have fixed that over the time and that is why
> we had unicity set to origin as a hack for a while, we are now moving to 
> unique
> name so you have to make sure that all your installed packages are up to date
> before moving to new pkg.
> 
> At least make sure you do not have 2 packages with the same name.
> 
> Concerning portmaster I have no idea why it now thinks you are not using
> pkg :(

I checked for packages with the same name and found none (via pkg
version). Meanwhile, the upgrade still fails for me. Has anybody got
any new ideas?

Thanks in advance!

Regards,
Marc

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

Re: pkg 1.4 freeze please test test test!

[Andriy Gapon]

On 29/10/2014 15:53, Baptiste Daroussin wrote:
> yes remove the current pkg
> 
> pkg delete -f pkg
> 
> install ports-mgmt/pkg-devel (adding WITH_PKG=devel in make.conf)
> use it

So, I followed these instructions and got pkg replaced with 1.4.0.p.a16.
Then I ran pkg upgrade like this:
$ pkg upgrade -y
Updating FreeBSD repository catalogue...
pkg: Repository FreeBSD has a wrong packagesite, need to re-create database
Fetching meta.txz: 100%   944 B   0.9k/s00:01
Fetching digests.txz: 100%2 MB   2.1M/s00:01
Fetching packagesite.txz: 100%5 MB   5.3M/s00:01
Processing new repository entries: 100%
FreeBSD repository update completed. 23591 packages processed:
  0 updated, 0 removed and 23591 added.
Updating poudriere repository catalogue...
poudriere repository is up-to-date.
Updating database digests format: 100%
New version of pkg detected; it needs to be installed first.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
Updating poudriere repository catalogue...
poudriere repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (297 candidates):   0%
Checking for upgrades (297 candidates):  10%
Checking for upgrades (297 candidates): 100%
Processing candidates (297 candidates): 100%
Assertion failed: (curvar != NULL), function pkg_solve_add_request_rule, file
pkg_solve.c, line 463.
Child process pid=78582 terminated abnormally: Abort trap

$ pkg -vv
Version : 1.4.0.pre-alpha16
PKG_DBDIR = "/usr/local/var/db/pkg";
PKG_CACHEDIR = "/var/cache/pkg";
PORTSDIR = "/usr/ports";
INDEXDIR = "";
INDEXFILE = "INDEX-11";
HANDLE_RC_SCRIPTS = false;
ASSUME_ALWAYS_YES = false;
REPOS_DIR [
"/etc/pkg/",
"/usr/local/etc/pkg/repos/",
]
PLIST_KEYWORDS_DIR = "";
SYSLOG = false;
ABI = "FreeBSD:11:amd64";
ALTABI = "freebsd:11:x86:64";
DEVELOPER_MODE = false;
VULNXML_SITE = "http://www.vuxml.org/freebsd/vuln.xml.bz2";;
FETCH_RETRY = 3;
PKG_PLUGINS_DIR = "/usr/local/lib/pkg/";
PKG_ENABLE_PLUGINS = true;
PLUGINS [
]
DEBUG_SCRIPTS = false;
PLUGINS_CONF_DIR = "/usr/local/etc/pkg/";
PERMISSIVE = false;
REPO_AUTOUPDATE = true;
NAMESERVER = "";
EVENT_PIPE = "";
FETCH_TIMEOUT = 30;
UNSET_TIMESTAMP = false;
SSH_RESTRICT_DIR = "";
PKG_ENV {
}
PKG_SSH_ARGS = "";
DEBUG_LEVEL = 0;
ALIAS {
}
CUDF_SOLVER = "";
SAT_SOLVER = "";
RUN_SCRIPTS = true;
CASE_SENSITIVE_MATCH = false;
LOCK_WAIT = 1;
LOCK_RETRIES = 5;
SQLITE_PROFILE = false;
WORKERS_COUNT = 0;
READ_LOCK = false;
PLIST_ACCEPT_DIRECTORIES = false;
IP_VERSION = 0;


Repositories:
  FreeBSD: {
url : "pkg+http://pkg.FreeBSD.org/FreeBSD:11:amd64/latest";,
enabled : yes,
mirror_type : "SRV",
signature_type  : "FINGERPRINTS",
fingerprints: "/usr/share/keys/pkg"
  }
  poudriere: {
url : 
"file:///usr/local/poudriere/data/packages/basejail-default",
enabled : yes
  }

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

Re: pkg 1.4 freeze please test test test!

[Kevin Oberman]

On Mon, Nov 3, 2014 at 11:03 PM, Kevin Oberman  wrote:

> Thanks you! That dies the trick.
>

Or, at least does the trick.

>
> R. Kevin Oberman, Network Engineer, Retired
> E-mail: rkober...@gmail.com
>
> On Mon, Nov 3, 2014 at 10:51 PM, Darren Pilgrim <
> list_free...@bluerosetech.com> wrote:
>
>> On 11/3/2014 9:50 PM, Kevin Oberman wrote:
>>
>>> I simply do periodic(8) weekly runs of "pkg version -vRl\<" to catch any
>>> port that has not been updated due to being locked. On option to only
>>> report locked packages would simplify this and looks to me like it would
>>> be
>>> pretty easy to add, but unless you have a lot of locked packages, it's
>>> not
>>> a problem.
>>>
>>
>> I just do `pkg info -ka | egrep 'yes$'`.
>>
>>
>>
>
___
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"

Re: pkg 1.4 freeze please test test test!

[Kevin Oberman]

Thanks you! That dies the trick.

R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com

On Mon, Nov 3, 2014 at 10:51 PM, Darren Pilgrim <
list_free...@bluerosetech.com> wrote:

> On 11/3/2014 9:50 PM, Kevin Oberman wrote:
>
>> I simply do periodic(8) weekly runs of "pkg version -vRl\<" to catch any
>> port that has not been updated due to being locked. On option to only
>> report locked packages would simplify this and looks to me like it would
>> be
>> pretty easy to add, but unless you have a lot of locked packages, it's not
>> a problem.
>>
>
> I just do `pkg info -ka | egrep 'yes$'`.
>
>
>
___
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"

Re: pkg 1.4 freeze please test test test!

[Darren Pilgrim]

On 11/3/2014 9:50 PM, Kevin Oberman wrote:

I simply do periodic(8) weekly runs of "pkg version -vRl\<" to catch any
port that has not been updated due to being locked. On option to only
report locked packages would simplify this and looks to me like it would be
pretty easy to add, but unless you have a lot of locked packages, it's not
a problem.


I just do `pkg info -ka | egrep 'yes$'`.


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

Re: pkg 1.4 freeze please test test test!

[Kevin Oberman]

--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman@gmail.comOn Mon, Nov 3, 2014 at 5:09 PM, Henry Hu <
henry.hu...@gmail.com> wrote:

> On Mon, Nov 3, 2014 at 4:48 PM, Freddie Cash  wrote:
>
> > On Mon, Nov 3, 2014 at 1:40 PM, Hans Petter Selasky 
> > wrote:
> >
> > > Is it possible when upgrading a system via "pkg" to selectivly switch
> > > upgrades ON/OFF. For example I have a custom ffmpeg install and would
> > like
> > > to keep it every time I do a binary upgrade?
> > >
> >
> >
> > ​# man pkg-lock
> >
> > ;)
> >
> > I believe that's what you are looking for.​  No idea how well it works
> > long-term, though, or if you lock a large number of packages.
> >
>
> I also use pkg-lock, but it has several problems:
> * You may miss updates. They are skipped during pkg upgrade
> * "xxx is locked and may not be modified" is displayed every time you do
> something like pkg upgrade. If you have multiple pkgs locked, it may be
> annoying.
>
> It would be easier to update the pkgs by having something like portmaster
> -P.
> --
> Cheers,
> Henry


I simply do periodic(8) weekly runs of "pkg version -vRl\<" to catch any
port that has not been updated due to being locked. On option to only
report locked packages would simplify this and looks to me like it would be
pretty easy to add, but unless you have a lot of locked packages, it's not
a problem.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
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"

Re: pkg 1.4 freeze please test test test!

[Henry Hu]

On Mon, Nov 3, 2014 at 4:48 PM, Freddie Cash  wrote:

> On Mon, Nov 3, 2014 at 1:40 PM, Hans Petter Selasky 
> wrote:
>
> > Is it possible when upgrading a system via "pkg" to selectivly switch
> > upgrades ON/OFF. For example I have a custom ffmpeg install and would
> like
> > to keep it every time I do a binary upgrade?
> >
>
>
> ​# man pkg-lock
>
> ;)
>
> I believe that's what you are looking for.​  No idea how well it works
> long-term, though, or if you lock a large number of packages.
>

I also use pkg-lock, but it has several problems:
* You may miss updates. They are skipped during pkg upgrade
* "xxx is locked and may not be modified" is displayed every time you do
something like pkg upgrade. If you have multiple pkgs locked, it may be
annoying.

It would be easier to update the pkgs by having something like portmaster
-P.

>
>
> --
> Freddie Cash
> fjwc...@gmail.com
> ___
> 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"




-- 
Cheers,
Henry
___
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"

Re: pkg 1.4 freeze please test test test!

[Freddie Cash]

On Mon, Nov 3, 2014 at 1:40 PM, Hans Petter Selasky  wrote:

> Is it possible when upgrading a system via "pkg" to selectivly switch
> upgrades ON/OFF. For example I have a custom ffmpeg install and would like
> to keep it every time I do a binary upgrade?
>


​# man pkg-lock

;)

I believe that's what you are looking for.​  No idea how well it works
long-term, though, or if you lock a large number of packages.


-- 
Freddie Cash
fjwc...@gmail.com
___
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"

Re: pkg 1.4 freeze please test test test!

[Hans Petter Selasky]

Hi,

Is it possible when upgrading a system via "pkg" to selectivly switch 
upgrades ON/OFF. For example I have a custom ffmpeg install and would 
like to keep it every time I do a binary upgrade?


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

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Sat, Nov 01, 2014 at 04:13:32PM +0100, Marc UBM wrote:
> On Wed, 29 Oct 2014 00:19:33 +0100
> Baptiste Daroussin  wrote:
> 
> > Hi all,
> > 
> > We are starting the release process of pkg 1.4, we want to have a better 
> > release
> > process than with every single previous version of pkg. For that we will 
> > need
> > you help!
> > 
> > pkg-devel has been updated to the latest version of pkg as of alpha2.
> > 
> > Changes you can expect in pkg 1.4 are the following:
> > - Loads of bug fixes
> > - Stricter checking of the path passed via the plist
> > - Removal of the bundled libyaml
> > - new --raw-format to chose the output format for info -R and search -R
> > - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become 
> > FreeBSD:10:amd64)
> >   the old ABI is available as a fallback in ALTABI
> > - pkg check now support a quiet mode
> > - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
> >   configuration files
> > - new @config keyword to mark a file as a config file (during
> >   upgrade/reinstallation it will try to merge the configuration with the 
> > one the
> >   user may have modified) an option AUTOMERGE is available to prevent
> >   automerging if automerge fails a .pkgnew file will be created along with 
> > the
> >   untouched user version of the configuration
> > - The update procedure has been improved and speed up a lot (in particular 
> > for
> >   machine with low resources)
> > - The unique identifier has been modified to be pkgname meaning now ports 
> > can be
> >   moved in new categories without having to be considered a different 
> > package
> > - Only libraries starting by lib* are added to the provided libraries
> > - General speed up of all operations
> > 
> > We need help in testing, but we also need help in writing regression tests !
> > The more we have tests the more stable the releases will be.
> > 
> > The release will also allow to be able to package base!
> > 
> > regards,
> > Bapt
> 
> The update is failing for me with:
> 
> .../usr/ports/ports-mgmt/pkg-devel# make all install clean
> ===>  Installing for pkg-1.4.0.a3
> ===>  Checking if pkg already installed
> pkg-static: sqlite error while executing DROP INDEX
> packages_unique;CREATE UNIQUE INDEX packages_unique ON packages(name);
> in file pkgdb.c:2246: UNIQUE constraint failed: packages.name *** Error
> code 74
> 
> Stop.
> make[1]: stopped in /usr/ports/ports-mgmt/pkg-devel
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/ports-mgmt/pkg-devel
> 
> 
> 
> portmaster fails with:
> root@ubm:/usr/ports/ports-mgmt/pkg-devel# portmaster -d pkg
> ===>>> No ORIGIN in /var/db/pkg/pkgconf-0.9.7/+CONTENTS
> 
> 
> ===>>> Cannot continue
> ===>>> Aborting update
> 
> ===>>> Killing background jobs
> Terminated
> ===>>> Exiting
> 
> make.conf related options:
> 
> #enable pkgng (might be superfluous)
> WITH_PKGNG=yes
> #enable PKGNG devel
> WITH_PKGNG=devel
> 
> Am I doing something wrong?

You are doing nothing wrong but that probably means you have ancient packages
that never got upgraded (in the old time it was allowed to have 2 packages
installed with the same name) we have fixed that over the time and that is why
we had unicity set to origin as a hack for a while, we are now moving to unique
name so you have to make sure that all your installed packages are up to date
before moving to new pkg.

At least make sure you do not have 2 packages with the same name.

Concerning portmaster I have no idea why it now thinks you are not using
pkg :(

regards,
Bapt


pgpZl_FQZwuMj.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Kurt Lidl]

I upgraded one of my machines to have pkg-devel on it
(1.4.0.alpha4), and attempted to recreate my test repo with it.

Version : 1.4.0.alpha4
PKG_DBDIR = "/tmp/pkg.tmp.67648";
PKG_CACHEDIR = "/var/cache/pkg";
PORTSDIR = "/usr/ports";
INDEXDIR = "";
INDEXFILE = "INDEX-9";
HANDLE_RC_SCRIPTS = false;
ASSUME_ALWAYS_YES = true;
REPOS_DIR [
"/usr/local/etc/pkg/repos",
]
PLIST_KEYWORDS_DIR = "";
SYSLOG = true;
ABI = "FreeBSD:9:amd64";
ALTABI = "freebsd:9:x86:64";
DEVELOPER_MODE = false;
VULNXML_SITE = "http://vuxml.freebsd.org/freebsd/vuln.xml.bz2";;
FETCH_RETRY = 3;
PKG_PLUGINS_DIR = "/usr/local/lib/pkg/";
PKG_ENABLE_PLUGINS = true;
PLUGINS [
]
DEBUG_SCRIPTS = false;
PLUGINS_CONF_DIR = "/usr/local/etc/pkg/";
PERMISSIVE = false;
REPO_AUTOUPDATE = false;
NAMESERVER = "";
EVENT_PIPE = "";
FETCH_TIMEOUT = 30;
UNSET_TIMESTAMP = false;
SSH_RESTRICT_DIR = "";
PKG_ENV {
}
PKG_SSH_ARGS = "";
DEBUG_LEVEL = 0;
ALIAS {
}
CUDF_SOLVER = "";
SAT_SOLVER = "";
RUN_SCRIPTS = true;
CASE_SENSITIVE_MATCH = false;
LOCK_WAIT = 1;
LOCK_RETRIES = 5;
SQLITE_PROFILE = false;
WORKERS_COUNT = 0;
READ_LOCK = false;
PLIST_ACCEPT_DIRECTORIES = false;
IP_VERSION = 0;
AUTOMERGE = true;


Repositories:
  X: {
url : "pkg+http://X/FreeBSD:9:amd64/latest";,
enabled : yes,
mirror_type : "SRV"
  }
Updating X repository catalogue...
Fetching meta.txz... done
Fetching packagesite.txz... done
Processing entries... done
X repository update completed. 506 packages processed
pkg: sqlite error while executing INSERT INTO pkg_search SELECT id, name 
|| '-' || version, origin FROM packages;CREATE INDEX packages_origin ON 
packages(origin COLLATE NOCASE);CREATE INDEX packages_name ON 
packages(name COLLATE NOCASE);CREATE INDEX packages_uid_nocase ON 
packages(name COLLATE NOCASE, origin COLLATE NOCASE);CREATE INDEX 
packages_version_nocase ON packages(name COLLATE NOCASE, version);CREATE 
INDEX packages_uid ON packages(name, origin);CREATE INDEX 
packages_version ON packages(name, version);CREATE UNIQUE INDEX 
packages_digest ON packages(manifestdigest); in file pkgdb.c:2246: 
UNIQUE constraint failed: packages.manifestdigest
Creating repository in 
/usr/obj/usr/src/release/packages/FreeBSD:9:amd64... done

Packing files for repository... done
Creating repository in 
/usr/obj/usr/src/release/packages/FreeBSD:9:amd64... done

Packing files for repository... done

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

Re: pkg 1.4 freeze please test test test!

[Lev Serebryakov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 29/10/2014 02:19, Baptiste Daroussin wrote:

> We are starting the release process of pkg 1.4, we want to have a
> better release process than with every single previous version of
> pkg. For that we will need you help!
> 
> pkg-devel has been updated to the latest version of pkg as of
> alpha2.
I have 1.4.0.p.a16 installed and have two problems now:

(1) Latest 11:amd64 package repository doesn't have newest package
(2) this package thinks, that 1.4.0.p.a16 is newer than 1.4.0.a4:

lev@labrat:~% pkg version -vIL=
...
pkg-devel-1.4.0.p.a16  >   succeeds index (index has 1.4.0.a4)
...
lev@labrat:~% sudo pkg -4 upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (216 candidates):  37%
pkg-devel~ports-mgmt/pkg-devel has no direct installation candidates,
change it to pkg-devel~ports-mgmt/pkg-devel? [Y/n]: y
Checking for upgrades (216 candidates): 100%
Processing candidates (216 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
lev@labrat:~%

- -- 
// Lev Serebryakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJUVOQAXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF
QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EeP1EUQALM9Hs2X1F3Zoa94RwpHK4XI
0H8/VWB/NA9J//UGqW1btikXpbSDRSA2DsjL3wzfk0Z0SNQrExrUlwthkv3n/llh
OPTthShVOijOGTuvE+voBuc0aGNDOfAodNaJKHncF/qai/6P3WqqGnxsuEGegZm4
JD0bM0OQfnoQz/xECWFOwJA6EFPgneAzCthpNkCFUbe0d7/hk9uDD3I6rmJPzT4T
pMRizelSZxNyMc0kVJZjfa/Zlj6h818R6puzbb3ErX0SyijyzyOKI1pAZ5mmSgl4
vPbMWELHQWVRRQS1KcvGfNJMgpYB0UG93flZ+E9M3h/ScBqdZc+2OqYUEd+ZiE/T
kPJ0oQw9t283banasA0k8Ej59478ZN1CxnmO766x96lqCTlbqbl3KFwgpNORCvas
/WBjV0T8ZgSf1gCh5WnFQDF0rmpfql4Ol0ynY4A8ToKtJsAUpQ+vwR8WieHRKWf9
28fqmq/+ZewX5mS/7/eZ/DZdlqgKSmWv7JbETVYR3IAkF1a3s38DrU1ZZ5TnUrPM
xWqvFC8hfW7aiMtzQ8OWW8WIFMC02/0oyxEqnFsVh/+IIsvXtTQOmPFd+tNlU3Xq
FjkqFJRmVBqLS2eXtNvF5WzOJrEJmAOkkYVzGAlpYQVAVie+UZHKu3D1A8B8+EPO
3PfdV96CUGhS56H9Z8R3
=v9Qt
-END PGP SIGNATURE-
___
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"

Re: pkg 1.4 freeze please test test test!

[Don Lewis]

On 29 Oct, Baptiste Daroussin wrote:
> On Wed, Oct 29, 2014 at 01:15:16PM -0700, Don Lewis wrote:
>> On 28 Oct, Don Lewis wrote:
>> > On 29 Oct, Baptiste Daroussin wrote:
>> >> Hi all,
>> >> 
>> >> We are starting the release process of pkg 1.4, we want to have a better 
>> >> release
>> >> process than with every single previous version of pkg. For that we will 
>> >> need
>> >> you help!
>> >> 
>> >> pkg-devel has been updated to the latest version of pkg as of alpha2.
>> >> 
>> >> Changes you can expect in pkg 1.4 are the following:
>> >> - Loads of bug fixes
>> > 
>> > I kind of doubt that I'll have time to test it, but I've stumbled across
>> > an interesting test case for package building with pkg-1.3.8_3.
>> > 
>> > When I tried to build a multimedia/2mandvd package with
>> > poudriere (either bulk or testport) in a FreeBSD 10 amd64 host and jail,
>> > pkg-static segfaults.  Portsmon also sees this failure, which also
>> > seems to be affecting head/amd64 as well:
>> > 
>> > 
>> > If I run poudriere jail -i to keep the jail around, I don't see any
>> > leftover core files, I'm guessing because pkg-static's cwd is in the r/o
>> > /usr/ports tree.  If I then cd /usr/ports/multimedia/2mandvd in the
>> > jail and run:
>> >make clean
>> >make stage
>> >make package
>> > pkg-static doesn't segfault, but it never exits either.  I left it
>> > running for a couple of days and it was still stuck at 100% CPU.  If
>> > I truss -p the process, I don't get any output, which means it's not
>> > doing any syscalls.
>> 
>> 
>> I found some time to test this version.  I added WITH_PKG=devel to the
>> make.conf file for the poudriere jail and ran:
>> 
>>  poudriere testport -j 101STABLEamd64 -o multimedia/2mandvd
> 
> Ah crap this 2mandvd again.
> 
> Ok I'll track it down, thanks

Seems to work fine on 8.4, both i386 and amd64, so it appears to be
sensitive to something in base.

> 2mandvd is a nightmare for me :)

Back when I was still using portupgrade to build packages, I didn't have
trouble building the package, but portupgrade would fail during the
deinstall phase for 2mandvd.  I think it was complaining about non-ASCII
characters in the plist, but I don't know where the error was coming
from.  I didn't have trouble manually doing the deinstall with pkg
delete, and then I could run portupgrade -Np.  I didn't think of trying
pkg-static to see if it behaved differently.

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

Re: pkg 1.4 freeze please test test test!

[Henry Hu]

On Wed, Oct 29, 2014 at 8:39 PM, Baptiste Daroussin 
wrote:

> On Thu, Oct 30, 2014 at 12:03:21AM +0100, Baptiste Daroussin wrote:
> > On Wed, Oct 29, 2014 at 06:07:44PM -0400, Henry Hu wrote:
> > > Hi,
> > >
> > >
> > > On Tue, Oct 28, 2014 at 7:19 PM, Baptiste Daroussin 
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > We are starting the release process of pkg 1.4, we want to have a
> better
> > > > release
> > > > process than with every single previous version of pkg. For that we
> will
> > > > need
> > > > you help!
> > > >
> > > > pkg-devel has been updated to the latest version of pkg as of alpha2.
> > > >
> > > > Changes you can expect in pkg 1.4 are the following:
> > > > - Loads of bug fixes
> > > > - Stricter checking of the path passed via the plist
> > > > - Removal of the bundled libyaml
> > > > - new --raw-format to chose the output format for info -R and search
> -R
> > > > - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become
> > > > FreeBSD:10:amd64)
> > > >   the old ABI is available as a fallback in ALTABI
> > > > - pkg check now support a quiet mode
> > > > - new 3 way merge code ("stolen" from the fossil-scm) to allow
> automerging
> > > >   configuration files
> > > > - new @config keyword to mark a file as a config file (during
> > > >   upgrade/reinstallation it will try to merge the configuration with
> the
> > > > one the
> > > >   user may have modified) an option AUTOMERGE is available to prevent
> > > >   automerging if automerge fails a .pkgnew file will be created
> along with
> > > > the
> > > >   untouched user version of the configuration
> > > > - The update procedure has been improved and speed up a lot (in
> particular
> > > > for
> > > >   machine with low resources)
> > > > - The unique identifier has been modified to be pkgname meaning now
> ports
> > > > can be
> > > >   moved in new categories without having to be considered a different
> > > > package
> > > > - Only libraries starting by lib* are added to the provided libraries
> > > > - General speed up of all operations
> > > >
> > > > We need help in testing, but we also need help in writing regression
> tests
> > > > !
> > > > The more we have tests the more stable the releases will be.
> > > >
> > > > The release will also allow to be able to package base!
> > > >
> > >
> > > I've just tried pkg-devel 1.4.0.alpha3 and found something strange:
> when a
> > > pkg is removed, pkgs which depend on it are not removed.
> > >
> > > For example:
> > >
> > > > sudo pkg remove libX11
> > > Checking integrity... done (0 conflicting)
> > > Deinstallation has been requested for the following 1 packages (of 0
> > > packages in the universe):
> > >
> > > Installed packages to be REMOVED:
> > > libX11-1.6.2_2,1
> > >
> > > The operation will free 6 MB.
> > >
> > > Proceed with deinstalling packages? [y/N]:
> > > > sudo pkg remove -R libX11
> > > Checking integrity... done (0 conflicting)
> > > Deinstallation has been requested for the following 1 packages (of 0
> > > packages in the universe):
> > >
> > > Installed packages to be REMOVED:
> > > libX11-1.6.2_2,1
> > >
> > > The operation will free 6 MB.
> > >
> > > Proceed with deinstalling packages? [y/N]:
> > >
> > Seems like can you store somewhere you /var/db/pkg/local.sqlite so that
> we can
> > fix your situation?
> >
> > Best regards,
> > Bapt
>
> Thanks fixed in the git master will be in alpha4
>

Thanks! Nice work!


> Actually you have lots of locked packages so on alpha4 pkg will just tell
> you
> that libX11 cannot be removed because of locks :)
>

Well, I don't like to lock pkgs, but that's the only option I know to keep
my packages with different options selected intact during pkg upgrade.


>
> regards,
> Bapt
>



-- 
Cheers,
Henry
___
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"

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Thu, Oct 30, 2014 at 12:03:21AM +0100, Baptiste Daroussin wrote:
> On Wed, Oct 29, 2014 at 06:07:44PM -0400, Henry Hu wrote:
> > Hi,
> > 
> > 
> > On Tue, Oct 28, 2014 at 7:19 PM, Baptiste Daroussin 
> > wrote:
> > 
> > > Hi all,
> > >
> > > We are starting the release process of pkg 1.4, we want to have a better
> > > release
> > > process than with every single previous version of pkg. For that we will
> > > need
> > > you help!
> > >
> > > pkg-devel has been updated to the latest version of pkg as of alpha2.
> > >
> > > Changes you can expect in pkg 1.4 are the following:
> > > - Loads of bug fixes
> > > - Stricter checking of the path passed via the plist
> > > - Removal of the bundled libyaml
> > > - new --raw-format to chose the output format for info -R and search -R
> > > - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become
> > > FreeBSD:10:amd64)
> > >   the old ABI is available as a fallback in ALTABI
> > > - pkg check now support a quiet mode
> > > - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
> > >   configuration files
> > > - new @config keyword to mark a file as a config file (during
> > >   upgrade/reinstallation it will try to merge the configuration with the
> > > one the
> > >   user may have modified) an option AUTOMERGE is available to prevent
> > >   automerging if automerge fails a .pkgnew file will be created along with
> > > the
> > >   untouched user version of the configuration
> > > - The update procedure has been improved and speed up a lot (in particular
> > > for
> > >   machine with low resources)
> > > - The unique identifier has been modified to be pkgname meaning now ports
> > > can be
> > >   moved in new categories without having to be considered a different
> > > package
> > > - Only libraries starting by lib* are added to the provided libraries
> > > - General speed up of all operations
> > >
> > > We need help in testing, but we also need help in writing regression tests
> > > !
> > > The more we have tests the more stable the releases will be.
> > >
> > > The release will also allow to be able to package base!
> > >
> > 
> > I've just tried pkg-devel 1.4.0.alpha3 and found something strange: when a
> > pkg is removed, pkgs which depend on it are not removed.
> > 
> > For example:
> > 
> > > sudo pkg remove libX11
> > Checking integrity... done (0 conflicting)
> > Deinstallation has been requested for the following 1 packages (of 0
> > packages in the universe):
> > 
> > Installed packages to be REMOVED:
> > libX11-1.6.2_2,1
> > 
> > The operation will free 6 MB.
> > 
> > Proceed with deinstalling packages? [y/N]:
> > > sudo pkg remove -R libX11
> > Checking integrity... done (0 conflicting)
> > Deinstallation has been requested for the following 1 packages (of 0
> > packages in the universe):
> > 
> > Installed packages to be REMOVED:
> > libX11-1.6.2_2,1
> > 
> > The operation will free 6 MB.
> > 
> > Proceed with deinstalling packages? [y/N]:
> > 
> Seems like can you store somewhere you /var/db/pkg/local.sqlite so that we can
> fix your situation?
> 
> Best regards,
> Bapt

Thanks fixed in the git master will be in alpha4
Actually you have lots of locked packages so on alpha4 pkg will just tell you
that libX11 cannot be removed because of locks :)

regards,
Bapt


pgpYQ7RQFkQU9.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 10:37:43PM +0100, Guido Falsi wrote:
> On 10/29/14 00:19, Baptiste Daroussin wrote:
> > Hi all,
> > 
> > We are starting the release process of pkg 1.4, we want to have a better 
> > release
> > process than with every single previous version of pkg. For that we will 
> > need
> > you help!
> 
> Hi, last version works fine, but, sometimes, core files show up in port
> directory...for no reason, really.
> 
> Noticed this while doing some make patch and make extract in a
> standalone port directory outside the ports tree.
> 
> Anyway are you interested in the core file for investigation?
> 
> This is a backtrace:
> 
> (gdb) bt
> #0  0x007df0bb in strlen ()
> #1  0x00402c88 in add_to_check (head=0x7fffe0f8,
> pkg=0x80105b600)
> at audit.c:79
> #2  0x0040200e in exec_audit (argc=1, argv=0x7fffe898)
> at audit.c:205
> #3  0x00411132 in main (argc=2, argv=0x7fffe890) at main.c:822
> 
Disable vulnerability checking in your ports tree waiting for pkg 1.4.0.alpha4
to be released (which should happen in a couple of hours now)

This has been fixed in git master

Best regards,
Bapt


pgpW__pcvVxnM.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 06:07:44PM -0400, Henry Hu wrote:
> Hi,
> 
> 
> On Tue, Oct 28, 2014 at 7:19 PM, Baptiste Daroussin 
> wrote:
> 
> > Hi all,
> >
> > We are starting the release process of pkg 1.4, we want to have a better
> > release
> > process than with every single previous version of pkg. For that we will
> > need
> > you help!
> >
> > pkg-devel has been updated to the latest version of pkg as of alpha2.
> >
> > Changes you can expect in pkg 1.4 are the following:
> > - Loads of bug fixes
> > - Stricter checking of the path passed via the plist
> > - Removal of the bundled libyaml
> > - new --raw-format to chose the output format for info -R and search -R
> > - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become
> > FreeBSD:10:amd64)
> >   the old ABI is available as a fallback in ALTABI
> > - pkg check now support a quiet mode
> > - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
> >   configuration files
> > - new @config keyword to mark a file as a config file (during
> >   upgrade/reinstallation it will try to merge the configuration with the
> > one the
> >   user may have modified) an option AUTOMERGE is available to prevent
> >   automerging if automerge fails a .pkgnew file will be created along with
> > the
> >   untouched user version of the configuration
> > - The update procedure has been improved and speed up a lot (in particular
> > for
> >   machine with low resources)
> > - The unique identifier has been modified to be pkgname meaning now ports
> > can be
> >   moved in new categories without having to be considered a different
> > package
> > - Only libraries starting by lib* are added to the provided libraries
> > - General speed up of all operations
> >
> > We need help in testing, but we also need help in writing regression tests
> > !
> > The more we have tests the more stable the releases will be.
> >
> > The release will also allow to be able to package base!
> >
> 
> I've just tried pkg-devel 1.4.0.alpha3 and found something strange: when a
> pkg is removed, pkgs which depend on it are not removed.
> 
> For example:
> 
> > sudo pkg remove libX11
> Checking integrity... done (0 conflicting)
> Deinstallation has been requested for the following 1 packages (of 0
> packages in the universe):
> 
> Installed packages to be REMOVED:
> libX11-1.6.2_2,1
> 
> The operation will free 6 MB.
> 
> Proceed with deinstalling packages? [y/N]:
> > sudo pkg remove -R libX11
> Checking integrity... done (0 conflicting)
> Deinstallation has been requested for the following 1 packages (of 0
> packages in the universe):
> 
> Installed packages to be REMOVED:
> libX11-1.6.2_2,1
> 
> The operation will free 6 MB.
> 
> Proceed with deinstalling packages? [y/N]:
> 
Seems like can you store somewhere you /var/db/pkg/local.sqlite so that we can
fix your situation?

Best regards,
Bapt


pgpYugd9P73SX.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Henry Hu]

Hi,


On Tue, Oct 28, 2014 at 7:19 PM, Baptiste Daroussin 
wrote:

> Hi all,
>
> We are starting the release process of pkg 1.4, we want to have a better
> release
> process than with every single previous version of pkg. For that we will
> need
> you help!
>
> pkg-devel has been updated to the latest version of pkg as of alpha2.
>
> Changes you can expect in pkg 1.4 are the following:
> - Loads of bug fixes
> - Stricter checking of the path passed via the plist
> - Removal of the bundled libyaml
> - new --raw-format to chose the output format for info -R and search -R
> - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become
> FreeBSD:10:amd64)
>   the old ABI is available as a fallback in ALTABI
> - pkg check now support a quiet mode
> - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
>   configuration files
> - new @config keyword to mark a file as a config file (during
>   upgrade/reinstallation it will try to merge the configuration with the
> one the
>   user may have modified) an option AUTOMERGE is available to prevent
>   automerging if automerge fails a .pkgnew file will be created along with
> the
>   untouched user version of the configuration
> - The update procedure has been improved and speed up a lot (in particular
> for
>   machine with low resources)
> - The unique identifier has been modified to be pkgname meaning now ports
> can be
>   moved in new categories without having to be considered a different
> package
> - Only libraries starting by lib* are added to the provided libraries
> - General speed up of all operations
>
> We need help in testing, but we also need help in writing regression tests
> !
> The more we have tests the more stable the releases will be.
>
> The release will also allow to be able to package base!
>

I've just tried pkg-devel 1.4.0.alpha3 and found something strange: when a
pkg is removed, pkgs which depend on it are not removed.

For example:

> sudo pkg remove libX11
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0
packages in the universe):

Installed packages to be REMOVED:
libX11-1.6.2_2,1

The operation will free 6 MB.

Proceed with deinstalling packages? [y/N]:
> sudo pkg remove -R libX11
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0
packages in the universe):

Installed packages to be REMOVED:
libX11-1.6.2_2,1

The operation will free 6 MB.

Proceed with deinstalling packages? [y/N]:

But pkg info -r libX11 produces a long list. If I downgrade to pkg 1.3.8,
pkg remove libX11 asks me to remove almost everything. Is this a regression?


>
> regards,
> Bapt
>



-- 
Cheers,
Henry
___
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"

Re: pkg 1.4 freeze please test test test!

[Guido Falsi]

On 10/29/14 00:19, Baptiste Daroussin wrote:
> Hi all,
> 
> We are starting the release process of pkg 1.4, we want to have a better 
> release
> process than with every single previous version of pkg. For that we will need
> you help!

Hi, last version works fine, but, sometimes, core files show up in port
directory...for no reason, really.

Noticed this while doing some make patch and make extract in a
standalone port directory outside the ports tree.

Anyway are you interested in the core file for investigation?

This is a backtrace:

(gdb) bt
#0  0x007df0bb in strlen ()
#1  0x00402c88 in add_to_check (head=0x7fffe0f8,
pkg=0x80105b600)
at audit.c:79
#2  0x0040200e in exec_audit (argc=1, argv=0x7fffe898)
at audit.c:205
#3  0x00411132 in main (argc=2, argv=0x7fffe890) at main.c:822

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

Re: pkg 1.4 freeze please test test test!

[Anton Afanasyev]

On Wed, Oct 29, 2014 at 1:08 PM, Baptiste Daroussin 
wrote:

> On Wed, Oct 29, 2014 at 01:05:49PM -0700, Anton Afanasyev wrote:
> > On Tue, Oct 28, 2014 at 4:19 PM, Baptiste Daroussin 
> > wrote:
> >
> > > - new 3 way merge code ("stolen" from the fossil-scm) to allow
> automerging
> > >   configuration files
> > > - new @config keyword to mark a file as a config file (during
> > >   upgrade/reinstallation it will try to merge the configuration with
> the
> > > one the
> > >   user may have modified) an option AUTOMERGE is available to prevent
> > >   automerging if automerge fails a .pkgnew file will be created along
> with
> > > the
> > >   untouched user version of the configuration
> > >
> > Would it make sense to let the user specify the merge tool to use and
> > always use it, instead of having to support the merge code within pkg?
>
> That will defeat cross installation/upgrades (install arm package in an
> arm chroot)
>
> but yes allowing a users to define their own merge tool in general instead
> of
> the internal one could make sense.
>
> regards,
> Bapt
>

I (and this is just a personal opinion of one man, of course) find it
better to be explicitly told that "this default config file has changed and
you need to review it and merge with your local changed copy, even if you
didn't make any drastic changes to your version", as opposed to "by the
way, we merged a new version of this config file with your changes", as
that forces one to know what and why has changed. I've already lost a
config file for one of my ports (squid, the last 2.something version) due
to it getting overwritten with the default, so wouldn't want anything like
that to happen again (and yes, I know, I must have backups; but that's not
the point here).

If auto-merging is going to stay, an option to turn it off and always use a
merge tool or perform the merge manually would be appreciated.


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

Re: pkg 1.4 freeze please test test test!

[Anton Afanasyev]

On Tue, Oct 28, 2014 at 4:19 PM, Baptiste Daroussin 
wrote:

> - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
>   configuration files
> - new @config keyword to mark a file as a config file (during
>   upgrade/reinstallation it will try to merge the configuration with the
> one the
>   user may have modified) an option AUTOMERGE is available to prevent
>   automerging if automerge fails a .pkgnew file will be created along with
> the
>   untouched user version of the configuration
>
Would it make sense to let the user specify the merge tool to use and
always use it, instead of having to support the merge code within pkg?


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

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 01:22:01PM -0700, Anton Afanasyev wrote:
> On Wed, Oct 29, 2014 at 1:08 PM, Baptiste Daroussin 
> wrote:
> 
> > On Wed, Oct 29, 2014 at 01:05:49PM -0700, Anton Afanasyev wrote:
> > > On Tue, Oct 28, 2014 at 4:19 PM, Baptiste Daroussin 
> > > wrote:
> > >
> > > > - new 3 way merge code ("stolen" from the fossil-scm) to allow
> > automerging
> > > >   configuration files
> > > > - new @config keyword to mark a file as a config file (during
> > > >   upgrade/reinstallation it will try to merge the configuration with
> > the
> > > > one the
> > > >   user may have modified) an option AUTOMERGE is available to prevent
> > > >   automerging if automerge fails a .pkgnew file will be created along
> > with
> > > > the
> > > >   untouched user version of the configuration
> > > >
> > > Would it make sense to let the user specify the merge tool to use and
> > > always use it, instead of having to support the merge code within pkg?
> >
> > That will defeat cross installation/upgrades (install arm package in an
> > arm chroot)
> >
> > but yes allowing a users to define their own merge tool in general instead
> > of
> > the internal one could make sense.
> >
> > regards,
> > Bapt
> >
> 
> I (and this is just a personal opinion of one man, of course) find it
> better to be explicitly told that "this default config file has changed and
> you need to review it and merge with your local changed copy, even if you
> didn't make any drastic changes to your version", as opposed to "by the
> way, we merged a new version of this config file with your changes", as
> that forces one to know what and why has changed. I've already lost a
> config file for one of my ports (squid, the last 2.something version) due
> to it getting overwritten with the default, so wouldn't want anything like
> that to happen again (and yes, I know, I must have backups; but that's not
> the point here).
> 
> If auto-merging is going to stay, an option to turn it off and always use a
> merge tool or perform the merge manually would be appreciated.

there is an option to turn it off as I said in the announcement:

AUTOMERGE: false

in pkg.conf

regards,
Bapt


pgpVXxrwSZPuB.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 01:15:16PM -0700, Don Lewis wrote:
> On 28 Oct, Don Lewis wrote:
> > On 29 Oct, Baptiste Daroussin wrote:
> >> Hi all,
> >> 
> >> We are starting the release process of pkg 1.4, we want to have a better 
> >> release
> >> process than with every single previous version of pkg. For that we will 
> >> need
> >> you help!
> >> 
> >> pkg-devel has been updated to the latest version of pkg as of alpha2.
> >> 
> >> Changes you can expect in pkg 1.4 are the following:
> >> - Loads of bug fixes
> > 
> > I kind of doubt that I'll have time to test it, but I've stumbled across
> > an interesting test case for package building with pkg-1.3.8_3.
> > 
> > When I tried to build a multimedia/2mandvd package with
> > poudriere (either bulk or testport) in a FreeBSD 10 amd64 host and jail,
> > pkg-static segfaults.  Portsmon also sees this failure, which also
> > seems to be affecting head/amd64 as well:
> > 
> > 
> > If I run poudriere jail -i to keep the jail around, I don't see any
> > leftover core files, I'm guessing because pkg-static's cwd is in the r/o
> > /usr/ports tree.  If I then cd /usr/ports/multimedia/2mandvd in the
> > jail and run:
> > make clean
> > make stage
> > make package
> > pkg-static doesn't segfault, but it never exits either.  I left it
> > running for a couple of days and it was still stuck at 100% CPU.  If
> > I truss -p the process, I don't get any output, which means it's not
> > doing any syscalls.
> 
> 
> I found some time to test this version.  I added WITH_PKG=devel to the
> make.conf file for the poudriere jail and ran:
> 
>   poudriere testport -j 101STABLEamd64 -o multimedia/2mandvd

Ah crap this 2mandvd again.

Ok I'll track it down, thanks

2mandvd is a nightmare for me :)

But a good testcase.

Thank you for pointing this to me

regards,
Bapt


pgpyK_SwhZyOE.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Don Lewis]

On 28 Oct, Don Lewis wrote:
> On 29 Oct, Baptiste Daroussin wrote:
>> Hi all,
>> 
>> We are starting the release process of pkg 1.4, we want to have a better 
>> release
>> process than with every single previous version of pkg. For that we will need
>> you help!
>> 
>> pkg-devel has been updated to the latest version of pkg as of alpha2.
>> 
>> Changes you can expect in pkg 1.4 are the following:
>> - Loads of bug fixes
> 
> I kind of doubt that I'll have time to test it, but I've stumbled across
> an interesting test case for package building with pkg-1.3.8_3.
> 
> When I tried to build a multimedia/2mandvd package with
> poudriere (either bulk or testport) in a FreeBSD 10 amd64 host and jail,
> pkg-static segfaults.  Portsmon also sees this failure, which also
> seems to be affecting head/amd64 as well:
> 
> 
> If I run poudriere jail -i to keep the jail around, I don't see any
> leftover core files, I'm guessing because pkg-static's cwd is in the r/o
> /usr/ports tree.  If I then cd /usr/ports/multimedia/2mandvd in the
> jail and run:
>   make clean
>   make stage
>   make package
> pkg-static doesn't segfault, but it never exits either.  I left it
> running for a couple of days and it was still stuck at 100% CPU.  If
> I truss -p the process, I don't get any output, which means it's not
> doing any syscalls.


I found some time to test this version.  I added WITH_PKG=devel to the
make.conf file for the poudriere jail and ran:

poudriere testport -j 101STABLEamd64 -o multimedia/2mandvd


>> Creating the reference jail... done
>> Mounting system devices for 101STABLEamd64-default
>> Mounting ports/packages/distfiles
>> Mounting packages from: 
/var/poudriere/data/packages/101STABLEamd64-default
>> Logs: 
/var/poudriere/data/logs/bulk/101STABLEamd64-default/2014-10-29_10h36m35s
>> Appending to make.conf: 
/usr/local/etc/poudriere.d/101STABLEamd64-make.conf
/etc/resolv.conf -> 
/var/poudriere/data/build/101STABLEamd64-default/ref/etc/resolv.conf
>> Starting jail 101STABLEamd64-default
>> Loading MOVED
>> Calculating ports order and dependencies
>> Sanity checking the repository
>> Deleting old version: desktop-file-utils-0.22_2.txz
[snip]
>> Deleting stale symlinks
>> Deleting empty directories
>> Cleaning the build queue
>> Building 99 packages using 4 builders
>> Starting/Cloning builders
>> Hit CTRL+t at any time to see build progress and stats
>> [01] Starting build of ports-mgmt/pkg-devel
>> [01] Finished build of ports-mgmt/pkg-devel: Success
[snip]
>> Stopping 4 builders
>> Portlint check
WARN: 
/var/poudriere/data/build/101STABLEamd64-default/ref/usr/ports/multimedia/2mandvd/pkg-plist:
 [497]: @dirrm[try] is deprecated.  If you require special directory handling, 
use @dir instead and consult the porter's handbook.
WARN: 
/var/poudriere/data/build/101STABLEamd64-default/ref/usr/ports/multimedia/2mandvd/pkg-plist:
 [498]: @dirrm[try] is deprecated.  If you require special directory handling, 
use @dir instead and consult the porter's handbook.
WARN: 
/var/poudriere/data/build/101STABLEamd64-default/ref/usr/ports/multimedia/2mandvd/pkg-plist:
 [499]: @dirrm[try] is deprecated.  If you require special directory handling, 
use @dir instead and consult the porter's handbook.
WARN: 
/var/poudriere/data/build/101STABLEamd64-default/ref/usr/ports/multimedia/2mandvd/pkg-plist:
 [500]: @dirrm[try] is deprecated.  If you require special directory handling, 
use @dir instead and consult the porter's handbook.
WARN: 
/var/poudriere/data/build/101STABLEamd64-default/ref/usr/ports/multimedia/2mandvd/pkg-plist:
 [501]: @dirrm[try] is deprecated.  If you require special directory handling, 
use @dir instead and consult the porter's handbook.
WARN: 
/var/poudriere/data/build/101STABLEamd64-default/ref/usr/ports/multimedia/2mandvd/pkg-plist:
 [502]: @dirrm[try] is deprecated.  If you require special directory handling, 
use @dir instead and consult the porter's handbook.
WARN: 
/var/poudriere/data/build/101STABLEamd64-default/ref/usr/ports/multimedia/2mandvd/pkg-plist:
 [503]: @dirrm[try] is deprecated.  If you require special directory handling, 
use @dir instead and consult the porter's handbook.
WARN: 
/var/poudriere/data/build/101STABLEamd64-default/ref/usr/ports/multimedia/2mandvd/pkg-plist:
 [504]: @dirrm[try] is deprecated.  If you require special directory handling, 
use @dir instead and consult the porter's handbook.
WARN: 
/var/poudriere/data/build/101STABLEamd64-default/ref/usr/ports/multimedia/2mandvd/pkg-plist:
 [505]: @dirrm[try] is deprecated.  If you require special directory handling, 
use @dir instead and consult the porter's handbook.
WARN: 
/var/poudriere/data/build/101STABLEamd64-default/ref/usr/ports/multimedia/2mandvd/pkg-plist:
 [506]: @dirrm[try] is deprecated.  If you require special directory hand

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 01:05:49PM -0700, Anton Afanasyev wrote:
> On Tue, Oct 28, 2014 at 4:19 PM, Baptiste Daroussin 
> wrote:
> 
> > - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
> >   configuration files
> > - new @config keyword to mark a file as a config file (during
> >   upgrade/reinstallation it will try to merge the configuration with the
> > one the
> >   user may have modified) an option AUTOMERGE is available to prevent
> >   automerging if automerge fails a .pkgnew file will be created along with
> > the
> >   untouched user version of the configuration
> >
> Would it make sense to let the user specify the merge tool to use and
> always use it, instead of having to support the merge code within pkg?

That will defeat cross installation/upgrades (install arm package in an arm 
chroot)

but yes allowing a users to define their own merge tool in general instead of
the internal one could make sense.

regards,
Bapt


pgpK7vWcb69Uc.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Slawa Olhovchenkov]

On Wed, Oct 29, 2014 at 03:07:14PM +0100, Baptiste Daroussin wrote:

> > > Why the help does a minor version has an inpact on the pecl? isn't the abi
> > > stable over minor versions?
> > 
> > I am don't know -- I am not php guru.
> > As result -- memcache module don't loaded and "class Memcache not
> > found".
> > May be just strict version check.
> > 
> 
> From what I do read from here:
> https://wiki.php.net/rfc/releaseprocess#releases_cycle
> 
> only going from X.Y to X.Y+1 needs to rebuild the extensions.
> and going from X.Y.Z to X.Y.Z+1 should be compatible

I don't know.
May be this is specific only for pecl-memcache.
May be reinstalling php lost information about installed extensions.
___
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"

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 05:10:58PM +0100, Daniel Gerzo wrote:
> On 2014-10-29 15:07, Baptiste Daroussin wrote:
> > On Wed, Oct 29, 2014 at 05:03:49PM +0400, Slawa Olhovchenkov wrote:
> >> On Wed, Oct 29, 2014 at 01:53:04PM +0100, Baptiste Daroussin wrote:
> >> 
> >> > > > How can we know pecl-memcache has to be reinstalled?
> >> > > >
> >> > > > We won't reinstall each time a version of a dep changes :)
> >> > >
> >> > > And what is solution?
> >> > > May be some flag on package (php) for reinstall all deps?
> >> >
> >> > I do have no idea, I'm open for suggestions :)
> >> > Either on the package side with triggers but that means implementing 
> >> > trigger in
> >> > package
> >> > Or in package side with provide/requires saying that this packages 
> >> > requires an
> >> > exact version of php meaning in case of upgrade of php the version would 
> >> > have
> >> > changed
> >> 
> >> May be (as workaround) some database witch this packages?
> >> List, or regexp.
> >> 
> >> This is need for some binary modules and don't need for "text"
> >> modules.
> >> But for some cases -- and for "text" modules too.
> >> 
> >> > Or someone has to be clever and find a ports only solution.
> >> 
> >> On ports side pecl-memcache rebuild on php version changed.
> >> 
> >> > Why the help does a minor version has an inpact on the pecl? isn't the 
> >> > abi
> >> > stable over minor versions?
> >> 
> >> I am don't know -- I am not php guru.
> >> As result -- memcache module don't loaded and "class Memcache not
> >> found".
> >> May be just strict version check.
> >> 
> > 
> > From what I do read from here:
> > https://wiki.php.net/rfc/releaseprocess#releases_cycle
> > 
> > only going from X.Y to X.Y+1 needs to rebuild the extensions.
> > and going from X.Y.Z to X.Y.Z+1 should be compatible
> 
> As far as I can tell from my own experience, every time I upgrade PHP, I 
> always have to also reinstall pecl- packages, and even some other things 
> like xcache, xdebug and so on.
> 
Right it is not a pkg problem them but a port one.

because same problem will occur with portmaster/portupgrade, the fix should go
in the ports tree, I have an idea will implement when I do have time.

regards,
Bapt


pgp4YLX84RpsE.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Daniel Gerzo]

On 2014-10-29 15:07, Baptiste Daroussin wrote:

On Wed, Oct 29, 2014 at 05:03:49PM +0400, Slawa Olhovchenkov wrote:

On Wed, Oct 29, 2014 at 01:53:04PM +0100, Baptiste Daroussin wrote:

> > > How can we know pecl-memcache has to be reinstalled?
> > >
> > > We won't reinstall each time a version of a dep changes :)
> >
> > And what is solution?
> > May be some flag on package (php) for reinstall all deps?
>
> I do have no idea, I'm open for suggestions :)
> Either on the package side with triggers but that means implementing trigger 
in
> package
> Or in package side with provide/requires saying that this packages requires an
> exact version of php meaning in case of upgrade of php the version would have
> changed

May be (as workaround) some database witch this packages?
List, or regexp.

This is need for some binary modules and don't need for "text"
modules.
But for some cases -- and for "text" modules too.

> Or someone has to be clever and find a ports only solution.

On ports side pecl-memcache rebuild on php version changed.

> Why the help does a minor version has an inpact on the pecl? isn't the abi
> stable over minor versions?

I am don't know -- I am not php guru.
As result -- memcache module don't loaded and "class Memcache not
found".
May be just strict version check.



From what I do read from here:
https://wiki.php.net/rfc/releaseprocess#releases_cycle

only going from X.Y to X.Y+1 needs to rebuild the extensions.
and going from X.Y.Z to X.Y.Z+1 should be compatible


As far as I can tell from my own experience, every time I upgrade PHP, I 
always have to also reinstall pecl- packages, and even some other things 
like xcache, xdebug and so on.


--
Kind regards
  Daniel
___
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"

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 05:03:49PM +0400, Slawa Olhovchenkov wrote:
> On Wed, Oct 29, 2014 at 01:53:04PM +0100, Baptiste Daroussin wrote:
> 
> > > > How can we know pecl-memcache has to be reinstalled?
> > > > 
> > > > We won't reinstall each time a version of a dep changes :)
> > > 
> > > And what is solution?
> > > May be some flag on package (php) for reinstall all deps?
> > 
> > I do have no idea, I'm open for suggestions :)
> > Either on the package side with triggers but that means implementing 
> > trigger in
> > package
> > Or in package side with provide/requires saying that this packages requires 
> > an
> > exact version of php meaning in case of upgrade of php the version would 
> > have
> > changed
> 
> May be (as workaround) some database witch this packages?
> List, or regexp.
> 
> This is need for some binary modules and don't need for "text"
> modules.
> But for some cases -- and for "text" modules too.
> 
> > Or someone has to be clever and find a ports only solution.
> 
> On ports side pecl-memcache rebuild on php version changed.
> 
> > Why the help does a minor version has an inpact on the pecl? isn't the abi
> > stable over minor versions?
> 
> I am don't know -- I am not php guru.
> As result -- memcache module don't loaded and "class Memcache not
> found".
> May be just strict version check.
> 

From what I do read from here:
https://wiki.php.net/rfc/releaseprocess#releases_cycle

only going from X.Y to X.Y+1 needs to rebuild the extensions.
and going from X.Y.Z to X.Y.Z+1 should be compatible

regards,
Bapt


pgpweYSUBItQL.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 02:12:37PM +0100, Cristiano Deana wrote:
> On Wed, Oct 29, 2014 at 12:19 AM, Baptiste Daroussin  wrote:
> 
> Hi Baptiste,
> 
> > We are starting the release process of pkg 1.4, we want to have a better 
> > release
> > process than with every single previous version of pkg. For that we will 
> > need
> > you help!
> 
> glad to help.
> I'd like to test it on a 10 system, so I suppose I have to install
> ports-mgmt/pkg-devel
> 
> Can we test it now, then remove it when 1.4 will be in -RELEASE or -STABLE?
> 
yes remove the current pkg

pkg delete -f pkg

install ports-mgmt/pkg-devel (adding WITH_PKG=devel in make.conf)
use it
when you want to go back to stable when 1.4 will be out:

pkg delete pkg
pkg bootstrap

regards,
Bapt


pgpFQWQ9FnFok.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 02:28:05PM +0100, Daniel Gerzo wrote:
> On 2014-10-29 13:53, Baptiste Daroussin wrote:
> >> > How can we know pecl-memcache has to be reinstalled?
> >> >
> >> > We won't reinstall each time a version of a dep changes :)
> >> 
> >> And what is solution?
> >> May be some flag on package (php) for reinstall all deps?
> > 
> > I do have no idea, I'm open for suggestions :)
> > Either on the package side with triggers but that means implementing 
> > trigger in
> > package
> > Or in package side with provide/requires saying that this packages 
> > requires an
> > exact version of php meaning in case of upgrade of php the version 
> > would have
> > changed
> > 
> > Or someone has to be clever and find a ports only solution.
> 
> This has been reported previously and the issue is bein tracked at 
> https://github.com/freebsd/pkg/issues/585
> It affects more then just pecl packages...

What I would like is a technical description of what happen what are the
symptoms and the real failure.

I need to know how often we should reinstall the package depending on php every
minor version? every medium version?
Which one should be reinstalled? all pear? all pecl, anything using phpize?

Right now the plan is to add the PHP_VERSION_ID to the version of the package
using phpize so each time php is bumped then the version changed and it is
reinstalled.

For example:
pecl-yaml-1.1.1 will become: pecl-yaml-1.1.1.50434 for 5.4.34

That is if only things using phpize needs to be reinstalled and that should be
fairly easy to do

regards,
Bapt


pgp50dXnx2oJh.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Daniel Gerzo]

On 2014-10-29 13:53, Baptiste Daroussin wrote:

> How can we know pecl-memcache has to be reinstalled?
>
> We won't reinstall each time a version of a dep changes :)

And what is solution?
May be some flag on package (php) for reinstall all deps?


I do have no idea, I'm open for suggestions :)
Either on the package side with triggers but that means implementing 
trigger in

package
Or in package side with provide/requires saying that this packages 
requires an
exact version of php meaning in case of upgrade of php the version 
would have

changed

Or someone has to be clever and find a ports only solution.


This has been reported previously and the issue is bein tracked at 
https://github.com/freebsd/pkg/issues/585

It affects more then just pecl packages...

--
Kind regards
  Daniel
___
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"

Re: pkg 1.4 freeze please test test test!

[Cristiano Deana]

On Wed, Oct 29, 2014 at 12:19 AM, Baptiste Daroussin  wrote:

Hi Baptiste,

> We are starting the release process of pkg 1.4, we want to have a better 
> release
> process than with every single previous version of pkg. For that we will need
> you help!

glad to help.
I'd like to test it on a 10 system, so I suppose I have to install
ports-mgmt/pkg-devel

Can we test it now, then remove it when 1.4 will be in -RELEASE or -STABLE?

Thank you

-- 
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/
___
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"

Re: pkg 1.4 freeze please test test test!

[Slawa Olhovchenkov]

On Wed, Oct 29, 2014 at 01:53:04PM +0100, Baptiste Daroussin wrote:

> > > How can we know pecl-memcache has to be reinstalled?
> > > 
> > > We won't reinstall each time a version of a dep changes :)
> > 
> > And what is solution?
> > May be some flag on package (php) for reinstall all deps?
> 
> I do have no idea, I'm open for suggestions :)
> Either on the package side with triggers but that means implementing trigger 
> in
> package
> Or in package side with provide/requires saying that this packages requires an
> exact version of php meaning in case of upgrade of php the version would have
> changed

May be (as workaround) some database witch this packages?
List, or regexp.

This is need for some binary modules and don't need for "text"
modules.
But for some cases -- and for "text" modules too.

> Or someone has to be clever and find a ports only solution.

On ports side pecl-memcache rebuild on php version changed.

> Why the help does a minor version has an inpact on the pecl? isn't the abi
> stable over minor versions?

I am don't know -- I am not php guru.
As result -- memcache module don't loaded and "class Memcache not
found".
May be just strict version check.

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

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 04:48:32PM +0400, Slawa Olhovchenkov wrote:
> On Wed, Oct 29, 2014 at 01:40:25PM +0100, Baptiste Daroussin wrote:
> 
> > On Wed, Oct 29, 2014 at 04:31:57PM +0400, Slawa Olhovchenkov wrote:
> > > On Wed, Oct 29, 2014 at 01:24:52PM +0100, Baptiste Daroussin wrote:
> > > 
> > > > On Wed, Oct 29, 2014 at 04:13:26PM +0400, Slawa Olhovchenkov wrote:
> > > > > On Wed, Oct 29, 2014 at 12:19:33AM +0100, Baptiste Daroussin wrote:
> > > > > 
> > > > > > Hi all,
> > > > > > 
> > > > > > We are starting the release process of pkg 1.4, we want to have a 
> > > > > > better release
> > > > > > process than with every single previous version of pkg. For that we 
> > > > > > will need
> > > > > > you help!
> > > > > 
> > > > > I have issuse, but I am not test on 1.4.
> > > > > I upgrade php (5.5.15 -> 5.5.17), pecl-memcache don't change version.
> > > > > pkg uprgade don't reinstall pecl-memcache (pourdure rebuild 
> > > > > pecl-memcache).
> > > > 
> > > > This is a problem with the port infrastructure for pecl
> > > 
> > > What problem?
> > > 
> > > deps: {
> > > php55-session: {
> > > origin: "www/php55-session",
> > > version: "5.5.17_1"
> > > },
> > > php55: {
> > > origin: "lang/php55",
> > > version: "5.5.17_1"
> > > },
> > > php55-zlib: {
> > > origin: "archivers/php55-zlib",
> > > version: "5.5.17_1"
> > > }
> > > }
> > > 
> > How can we know pecl-memcache has to be reinstalled?
> > 
> > We won't reinstall each time a version of a dep changes :)
> 
> And what is solution?
> May be some flag on package (php) for reinstall all deps?

I do have no idea, I'm open for suggestions :)
Either on the package side with triggers but that means implementing trigger in
package
Or in package side with provide/requires saying that this packages requires an
exact version of php meaning in case of upgrade of php the version would have
changed

Or someone has to be clever and find a ports only solution.

Why the help does a minor version has an inpact on the pecl? isn't the abi
stable over minor versions?

regards,
Bapt


pgpwpffZsiZwF.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Slawa Olhovchenkov]

On Wed, Oct 29, 2014 at 01:40:25PM +0100, Baptiste Daroussin wrote:

> On Wed, Oct 29, 2014 at 04:31:57PM +0400, Slawa Olhovchenkov wrote:
> > On Wed, Oct 29, 2014 at 01:24:52PM +0100, Baptiste Daroussin wrote:
> > 
> > > On Wed, Oct 29, 2014 at 04:13:26PM +0400, Slawa Olhovchenkov wrote:
> > > > On Wed, Oct 29, 2014 at 12:19:33AM +0100, Baptiste Daroussin wrote:
> > > > 
> > > > > Hi all,
> > > > > 
> > > > > We are starting the release process of pkg 1.4, we want to have a 
> > > > > better release
> > > > > process than with every single previous version of pkg. For that we 
> > > > > will need
> > > > > you help!
> > > > 
> > > > I have issuse, but I am not test on 1.4.
> > > > I upgrade php (5.5.15 -> 5.5.17), pecl-memcache don't change version.
> > > > pkg uprgade don't reinstall pecl-memcache (pourdure rebuild 
> > > > pecl-memcache).
> > > 
> > > This is a problem with the port infrastructure for pecl
> > 
> > What problem?
> > 
> > deps: {
> > php55-session: {
> > origin: "www/php55-session",
> > version: "5.5.17_1"
> > },
> > php55: {
> > origin: "lang/php55",
> > version: "5.5.17_1"
> > },
> > php55-zlib: {
> > origin: "archivers/php55-zlib",
> > version: "5.5.17_1"
> > }
> > }
> > 
> How can we know pecl-memcache has to be reinstalled?
> 
> We won't reinstall each time a version of a dep changes :)

And what is solution?
May be some flag on package (php) for reinstall all deps?
___
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"

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 04:31:57PM +0400, Slawa Olhovchenkov wrote:
> On Wed, Oct 29, 2014 at 01:24:52PM +0100, Baptiste Daroussin wrote:
> 
> > On Wed, Oct 29, 2014 at 04:13:26PM +0400, Slawa Olhovchenkov wrote:
> > > On Wed, Oct 29, 2014 at 12:19:33AM +0100, Baptiste Daroussin wrote:
> > > 
> > > > Hi all,
> > > > 
> > > > We are starting the release process of pkg 1.4, we want to have a 
> > > > better release
> > > > process than with every single previous version of pkg. For that we 
> > > > will need
> > > > you help!
> > > 
> > > I have issuse, but I am not test on 1.4.
> > > I upgrade php (5.5.15 -> 5.5.17), pecl-memcache don't change version.
> > > pkg uprgade don't reinstall pecl-memcache (pourdure rebuild 
> > > pecl-memcache).
> > 
> > This is a problem with the port infrastructure for pecl
> 
> What problem?
> 
> deps: {
> php55-session: {
> origin: "www/php55-session",
> version: "5.5.17_1"
> },
> php55: {
> origin: "lang/php55",
> version: "5.5.17_1"
> },
> php55-zlib: {
> origin: "archivers/php55-zlib",
> version: "5.5.17_1"
> }
> }
> 
How can we know pecl-memcache has to be reinstalled?

We won't reinstall each time a version of a dep changes :)

regards,
Bapt


pgpvGrQlx7Mur.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Slawa Olhovchenkov]

On Wed, Oct 29, 2014 at 01:24:52PM +0100, Baptiste Daroussin wrote:

> On Wed, Oct 29, 2014 at 04:13:26PM +0400, Slawa Olhovchenkov wrote:
> > On Wed, Oct 29, 2014 at 12:19:33AM +0100, Baptiste Daroussin wrote:
> > 
> > > Hi all,
> > > 
> > > We are starting the release process of pkg 1.4, we want to have a better 
> > > release
> > > process than with every single previous version of pkg. For that we will 
> > > need
> > > you help!
> > 
> > I have issuse, but I am not test on 1.4.
> > I upgrade php (5.5.15 -> 5.5.17), pecl-memcache don't change version.
> > pkg uprgade don't reinstall pecl-memcache (pourdure rebuild pecl-memcache).
> 
> This is a problem with the port infrastructure for pecl

What problem?

deps: {
php55-session: {
origin: "www/php55-session",
version: "5.5.17_1"
},
php55: {
origin: "lang/php55",
version: "5.5.17_1"
},
php55-zlib: {
origin: "archivers/php55-zlib",
version: "5.5.17_1"
}
}


> > > pkg-devel has been updated to the latest version of pkg as of alpha2.
> > > 
> > > Changes you can expect in pkg 1.4 are the following:
> > > - Loads of bug fixes
> > > - Stricter checking of the path passed via the plist
> > > - Removal of the bundled libyaml
> > > - new --raw-format to chose the output format for info -R and search -R
> > > - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become 
> > > FreeBSD:10:amd64)
> > >   the old ABI is available as a fallback in ALTABI
> > 
> > linux packages still freebsd:10:x86:32 ?
> 
> Yes for now, we plan to change that later.
> 
> regards,
> Bapt


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

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Wed, Oct 29, 2014 at 04:13:26PM +0400, Slawa Olhovchenkov wrote:
> On Wed, Oct 29, 2014 at 12:19:33AM +0100, Baptiste Daroussin wrote:
> 
> > Hi all,
> > 
> > We are starting the release process of pkg 1.4, we want to have a better 
> > release
> > process than with every single previous version of pkg. For that we will 
> > need
> > you help!
> 
> I have issuse, but I am not test on 1.4.
> I upgrade php (5.5.15 -> 5.5.17), pecl-memcache don't change version.
> pkg uprgade don't reinstall pecl-memcache (pourdure rebuild pecl-memcache).

This is a problem with the port infrastructure for pecl
> 
> > pkg-devel has been updated to the latest version of pkg as of alpha2.
> > 
> > Changes you can expect in pkg 1.4 are the following:
> > - Loads of bug fixes
> > - Stricter checking of the path passed via the plist
> > - Removal of the bundled libyaml
> > - new --raw-format to chose the output format for info -R and search -R
> > - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become 
> > FreeBSD:10:amd64)
> >   the old ABI is available as a fallback in ALTABI
> 
> linux packages still freebsd:10:x86:32 ?

Yes for now, we plan to change that later.

regards,
Bapt


pgpi5b78vzRan.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Slawa Olhovchenkov]

On Wed, Oct 29, 2014 at 12:19:33AM +0100, Baptiste Daroussin wrote:

> Hi all,
> 
> We are starting the release process of pkg 1.4, we want to have a better 
> release
> process than with every single previous version of pkg. For that we will need
> you help!

I have issuse, but I am not test on 1.4.
I upgrade php (5.5.15 -> 5.5.17), pecl-memcache don't change version.
pkg uprgade don't reinstall pecl-memcache (pourdure rebuild pecl-memcache).

> pkg-devel has been updated to the latest version of pkg as of alpha2.
> 
> Changes you can expect in pkg 1.4 are the following:
> - Loads of bug fixes
> - Stricter checking of the path passed via the plist
> - Removal of the bundled libyaml
> - new --raw-format to chose the output format for info -R and search -R
> - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become FreeBSD:10:amd64)
>   the old ABI is available as a fallback in ALTABI

linux packages still freebsd:10:x86:32 ?

> - pkg check now support a quiet mode
> - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
>   configuration files
> - new @config keyword to mark a file as a config file (during
>   upgrade/reinstallation it will try to merge the configuration with the one 
> the
>   user may have modified) an option AUTOMERGE is available to prevent
>   automerging if automerge fails a .pkgnew file will be created along with the
>   untouched user version of the configuration
> - The update procedure has been improved and speed up a lot (in particular for
>   machine with low resources)
> - The unique identifier has been modified to be pkgname meaning now ports can 
> be
>   moved in new categories without having to be considered a different package
> - Only libraries starting by lib* are added to the provided libraries
> - General speed up of all operations
> 
> We need help in testing, but we also need help in writing regression tests !
> The more we have tests the more stable the releases will be.
> 
> The release will also allow to be able to package base!
> 
> regards,
> Bapt


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

Re: pkg 1.4 freeze please test test test!

[Don Lewis]

On 29 Oct, Baptiste Daroussin wrote:
> Hi all,
> 
> We are starting the release process of pkg 1.4, we want to have a better 
> release
> process than with every single previous version of pkg. For that we will need
> you help!
> 
> pkg-devel has been updated to the latest version of pkg as of alpha2.
> 
> Changes you can expect in pkg 1.4 are the following:
> - Loads of bug fixes

I kind of doubt that I'll have time to test it, but I've stumbled across
an interesting test case for package building with pkg-1.3.8_3.

When I tried to build a multimedia/2mandvd package with
poudriere (either bulk or testport) in a FreeBSD 10 amd64 host and jail,
pkg-static segfaults.  Portsmon also sees this failure, which also
seems to be affecting head/amd64 as well:


If I run poudriere jail -i to keep the jail around, I don't see any
leftover core files, I'm guessing because pkg-static's cwd is in the r/o
/usr/ports tree.  If I then cd /usr/ports/multimedia/2mandvd in the
jail and run:
make clean
make stage
make package
pkg-static doesn't segfault, but it never exits either.  I left it
running for a couple of days and it was still stuck at 100% CPU.  If
I truss -p the process, I don't get any output, which means it's not
doing any syscalls.

I tried attaching gdb to the process, but got some strange error
messages that I didn't understand.  I then ran pkg-static under gdb with
the same command line arguments and it still looped forever.  I
interrupted it to get a stack trace, but that wasn't helpful because the
executable was stripped.

If I run pkg instead of pkg-static, it seems to work properly.

I was hoping to gather some more information to file a bug report, but
haven't had time to work on this in the last week.

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

Re: pkg 1.4 freeze please test test test!

[Cassiano Peixoto]

Hi guys,

Congrats, really good job.

How can i test package base? I didn't find any info about that.

Thanks.

On Tuesday, October 28, 2014, Baptiste Daroussin  wrote:

> Hi all,
>
> We are starting the release process of pkg 1.4, we want to have a better
> release
> process than with every single previous version of pkg. For that we will
> need
> you help!
>
> pkg-devel has been updated to the latest version of pkg as of alpha2.
>
> Changes you can expect in pkg 1.4 are the following:
> - Loads of bug fixes
> - Stricter checking of the path passed via the plist
> - Removal of the bundled libyaml
> - new --raw-format to chose the output format for info -R and search -R
> - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become
> FreeBSD:10:amd64)
>   the old ABI is available as a fallback in ALTABI
> - pkg check now support a quiet mode
> - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
>   configuration files
> - new @config keyword to mark a file as a config file (during
>   upgrade/reinstallation it will try to merge the configuration with the
> one the
>   user may have modified) an option AUTOMERGE is available to prevent
>   automerging if automerge fails a .pkgnew file will be created along with
> the
>   untouched user version of the configuration
> - The update procedure has been improved and speed up a lot (in particular
> for
>   machine with low resources)
> - The unique identifier has been modified to be pkgname meaning now ports
> can be
>   moved in new categories without having to be considered a different
> package
> - Only libraries starting by lib* are added to the provided libraries
> - General speed up of all operations
>
> We need help in testing, but we also need help in writing regression tests
> !
> The more we have tests the more stable the releases will be.
>
> The release will also allow to be able to package base!
>
> regards,
> Bapt
>
___
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"

Re: pkg 1.4 freeze please test test test!

[Allan Jude]

On 2014-10-28 19:35, Baptiste Daroussin wrote:
> On Tue, Oct 28, 2014 at 07:27:10PM -0400, Allan Jude wrote:
>> On 2014-10-28 19:19, Baptiste Daroussin wrote:
>>> Hi all,
>>>
>>> We are starting the release process of pkg 1.4, we want to have a better 
>>> release
>>> process than with every single previous version of pkg. For that we will 
>>> need
>>> you help!
>>>
>>> pkg-devel has been updated to the latest version of pkg as of alpha2.
>>>
>>> Changes you can expect in pkg 1.4 are the following:
>>> - Loads of bug fixes
>>> - Stricter checking of the path passed via the plist
>>> - Removal of the bundled libyaml
>>> - new --raw-format to chose the output format for info -R and search -R
>>> - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become 
>>> FreeBSD:10:amd64)
>>>   the old ABI is available as a fallback in ALTABI
>>> - pkg check now support a quiet mode
>>> - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
>>>   configuration files
>>> - new @config keyword to mark a file as a config file (during
>>>   upgrade/reinstallation it will try to merge the configuration with the 
>>> one the
>>>   user may have modified) an option AUTOMERGE is available to prevent
>>>   automerging if automerge fails a .pkgnew file will be created along with 
>>> the
>>>   untouched user version of the configuration
>>> - The update procedure has been improved and speed up a lot (in particular 
>>> for
>>>   machine with low resources)
>>> - The unique identifier has been modified to be pkgname meaning now ports 
>>> can be
>>>   moved in new categories without having to be considered a different 
>>> package
>>> - Only libraries starting by lib* are added to the provided libraries
>>> - General speed up of all operations
>>>
>>> We need help in testing, but we also need help in writing regression tests !
>>> The more we have tests the more stable the releases will be.
>>>
>>> The release will also allow to be able to package base!
>>>
>>> regards,
>>> Bapt
>>>
>>
>> Naming the option 'AUTOMERGE' when it stops the automatic merging, seems
>> like a really bad idea. Either make it AUTOMERGE=false or NOAUTHMERGE or
>> something.
> 
> The default it automerge: true you have to change it to automerge: false to
> prevent it to work
> 
> regards,
> Bapt
> 

Right, that makes sense, thank you.

-- 
Allan Jude



signature.asc
Description: OpenPGP digital signature

Re: pkg 1.4 freeze please test test test!

[Baptiste Daroussin]

On Tue, Oct 28, 2014 at 07:27:10PM -0400, Allan Jude wrote:
> On 2014-10-28 19:19, Baptiste Daroussin wrote:
> > Hi all,
> > 
> > We are starting the release process of pkg 1.4, we want to have a better 
> > release
> > process than with every single previous version of pkg. For that we will 
> > need
> > you help!
> > 
> > pkg-devel has been updated to the latest version of pkg as of alpha2.
> > 
> > Changes you can expect in pkg 1.4 are the following:
> > - Loads of bug fixes
> > - Stricter checking of the path passed via the plist
> > - Removal of the bundled libyaml
> > - new --raw-format to chose the output format for info -R and search -R
> > - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become 
> > FreeBSD:10:amd64)
> >   the old ABI is available as a fallback in ALTABI
> > - pkg check now support a quiet mode
> > - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
> >   configuration files
> > - new @config keyword to mark a file as a config file (during
> >   upgrade/reinstallation it will try to merge the configuration with the 
> > one the
> >   user may have modified) an option AUTOMERGE is available to prevent
> >   automerging if automerge fails a .pkgnew file will be created along with 
> > the
> >   untouched user version of the configuration
> > - The update procedure has been improved and speed up a lot (in particular 
> > for
> >   machine with low resources)
> > - The unique identifier has been modified to be pkgname meaning now ports 
> > can be
> >   moved in new categories without having to be considered a different 
> > package
> > - Only libraries starting by lib* are added to the provided libraries
> > - General speed up of all operations
> > 
> > We need help in testing, but we also need help in writing regression tests !
> > The more we have tests the more stable the releases will be.
> > 
> > The release will also allow to be able to package base!
> > 
> > regards,
> > Bapt
> > 
> 
> Naming the option 'AUTOMERGE' when it stops the automatic merging, seems
> like a really bad idea. Either make it AUTOMERGE=false or NOAUTHMERGE or
> something.

The default it automerge: true you have to change it to automerge: false to
prevent it to work

regards,
Bapt


pgp5gdNO3DuKP.pgp
Description: PGP signature

Re: pkg 1.4 freeze please test test test!

[Allan Jude]

On 2014-10-28 19:19, Baptiste Daroussin wrote:
> Hi all,
> 
> We are starting the release process of pkg 1.4, we want to have a better 
> release
> process than with every single previous version of pkg. For that we will need
> you help!
> 
> pkg-devel has been updated to the latest version of pkg as of alpha2.
> 
> Changes you can expect in pkg 1.4 are the following:
> - Loads of bug fixes
> - Stricter checking of the path passed via the plist
> - Removal of the bundled libyaml
> - new --raw-format to chose the output format for info -R and search -R
> - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become FreeBSD:10:amd64)
>   the old ABI is available as a fallback in ALTABI
> - pkg check now support a quiet mode
> - new 3 way merge code ("stolen" from the fossil-scm) to allow automerging
>   configuration files
> - new @config keyword to mark a file as a config file (during
>   upgrade/reinstallation it will try to merge the configuration with the one 
> the
>   user may have modified) an option AUTOMERGE is available to prevent
>   automerging if automerge fails a .pkgnew file will be created along with the
>   untouched user version of the configuration
> - The update procedure has been improved and speed up a lot (in particular for
>   machine with low resources)
> - The unique identifier has been modified to be pkgname meaning now ports can 
> be
>   moved in new categories without having to be considered a different package
> - Only libraries starting by lib* are added to the provided libraries
> - General speed up of all operations
> 
> We need help in testing, but we also need help in writing regression tests !
> The more we have tests the more stable the releases will be.
> 
> The release will also allow to be able to package base!
> 
> regards,
> Bapt
> 

Naming the option 'AUTOMERGE' when it stops the automatic merging, seems
like a really bad idea. Either make it AUTOMERGE=false or NOAUTHMERGE or
something.

-- 
Allan Jude



signature.asc
Description: OpenPGP digital signature