Re: pkgin does not install anything after upgrade to 9.2

[r0ller]

Hi Greg,

Thanks for the suggestion. I'm still doing the backup but will come back with 
the outcome.

Best regards,
r0ller

 Eredeti levél 
Feladó: Greg Troxel < g...@lexort.com (Link -> mailto:g...@lexort.com) >
Dátum: 2021 július 9 13:06:24
Tárgy: Re: pkgin does not install anything after upgrade to 9.2
Címzett: r0ller < netbsd-users@netbsd.org (Link -> 
mailto:netbsd-users@netbsd.org)

Boot to single user and full fsck. Also make the backups you have been meaning 
to get around to right away

Re: pkgin does not install anything after upgrade to 9.2

[Greg Troxel]

Boot to single user and full fsck.  Also make the backups you have been meaning 
to get around to right away

Re: pkgin does not install anything after upgrade to 9.2

[r0ller]

Hi Greg,

Thanks for your suggestions! It indeed seems to be corrupted :( I tried 
to nuke (rm -rf) the directory


/usr/pkg/pkgdb/p5-Net-SSLeay-1.88nb1 but I got back that the directory 
is not empty which is pretty unusual for rm -rf. Now, when I try to list 
its contents, three files are shown:


+COMMENT, +CONTENTS, +DESCR

However, when listing with ls -al, I get the error:

ls: +COMMENT: No such file or directory

ls: +CONTENTS: No such file or directory

ls: +DESCR: No such file or directory

I tried to execute fsck for the node number (fsck 35752122) of the 
directory but I got back:


fsck: cannot open '/dev/35752122': No such file or directory


Is there any solution for this?

Best regards,

r0ller


On 7/8/21 7:26 PM, Greg Troxel wrote:

r0ller  writes:
The only error I see in pkg_install-err.log (which is not shown as 
error) which seems to block each pkg install is: pkg_admin: Cannot 
read +CONTENTS of package p5-Net-SSLeay-1.88nb1 Does anyone have any 
hint? 
pkg_admin rebuild-tree pkg_admin check make sure your variables in 
mk.conf are set to point to your pkgdb. See 
https://www.pkgsrc.org/pkgdb-change/ and set the variables even if you 
think it's not necessary. look in /usr/pkg/pkgdb/p5-Net-SSLeay-1.88nb1 
and see if there is indeed no +CONTENTS. If true, you have had some 
corruption and I would rm -rf the p5-Net-SSLeay-1.88nb1 directory, and 
then you'll have to reinstall it.

Re: pkgin does not install anything after upgrade to 9.2

[Greg Troxel]

r0ller  writes:

> The only error I see in pkg_install-err.log (which is not shown as
> error) which seems to block each pkg install is:
>
> pkg_admin: Cannot read +CONTENTS of package p5-Net-SSLeay-1.88nb1
>
> Does anyone have any hint?


pkg_admin rebuild-tree
pkg_admin check

make sure your variables in mk.conf are set to point to your pkgdb.  See
  https://www.pkgsrc.org/pkgdb-change/
and set the variables even if you think it's not necessary.

look in /usr/pkg/pkgdb/p5-Net-SSLeay-1.88nb1 and see if there is indeed
no +CONTENTS.  If true, you have had some corruption and I would rm -rf
the p5-Net-SSLeay-1.88nb1 directory, and then you'll have to reinstall
it.



signature.asc
Description: PGP signature

Re: pkgin does not install anything after upgrade to 9.2

[nia]

On Thu, Jul 08, 2021 at 04:14:08PM +0200, Martin Husemann wrote:
> On Thu, Jul 08, 2021 at 02:36:17PM +0200, r0ller wrote:
> > is quite noticeable when starting firefox. However, after changing
> > repositories.conf to point to amd64/9.2/All and upgrading all packages,
> > nothing seems to have been upgraded and pkgin does not seem to install
> > anything.
> 
> The repositories are identical (9.2 is actually a symlink on the server
> pointing at the 9.0 repo).
> 
> Martin

to expand: pkgsrc is developed separately and has a separate release
schedule (approx. every 3 months, though packages can take a while to
build). I switch the 9.0 link to the latest pkgsrc branch when I think
it's ready.

Re: pkgin does not install anything after upgrade to 9.2

[Martin Husemann]

On Thu, Jul 08, 2021 at 02:36:17PM +0200, r0ller wrote:
> is quite noticeable when starting firefox. However, after changing
> repositories.conf to point to amd64/9.2/All and upgrading all packages,
> nothing seems to have been upgraded and pkgin does not seem to install
> anything.

The repositories are identical (9.2 is actually a symlink on the server
pointing at the 9.0 repo).

Martin

Re: pkgin repo

[Bob Bernstein]

On Wed, 7 Apr 2021, Dan Cîrnaț wrote:

Telling pkgin: 'pkgin install gdm' led to 59 packages being 
"refreshed", and 4 more installed.


Please be aware that those pkgin repos only have packages for 
the main pkgsrc tree, excluding pkgsrc-wip. The gdm version 
there is 2.x., an old one.


I did not suffer a version downgrade; still at gdm-40.0.

Thank you.

--
RSB

Re: pkgin repo

[Ottavio Caruso]

On 06/04/2021 22:54, Bob Bernstein wrote:

I am taking a first run at pkgin. It fails trying to get a file from:

https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$arch/9.99.81/All

...which can be found in my /usr/pkg/etc/pkgin/repositories.conf.

I have here:
  $ uname -a
NetBSD nebbytwo 9.99.81 NetBSD 9.99.81 (GENERIC) #0: Sat Mar 20 14:30:50 
UTC 2021 
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64


Given the version of -current I have, what pkgin repository URI should I 
use?




I'd use
https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/9.0_current/

which should be a symlink to the latest current builds, if cdn.* follows 
the same layout as ftp.*


--
Ottavio Caruso

Re: pkgin repo

[Dan Cîrnaț]

On 07.04.21 03:44, Bob Bernstein wrote:


Telling pkgin: 'pkgin install gdm' led to 59 packages being "refreshed", 
and 4 more installed.




Please be aware that those pkgin repos only have packages for the main
pkgsrc tree, excluding pkgsrc-wip. The gdm version there is 2.x., an
old one.

Dan

Re: pkgin repo

[Bob Bernstein]

On Wed, 7 Apr 2021, Chavdar Ivanov wrote:

I don't think there are "official" pkgin repos for -current. 
However, check https://pkgsrc.joyent.com/install-on-netbsd/ .



What I put in my /usr/pkg/etc/pkgin/reposiories.conf was:

https://pkgsrc.joyent.com/packages/NetBSD/trunk/x86_64/All/

Telling pkgin: 'pkgin install gdm' led to 59 packages being 
"refreshed", and 4 more installed.


And I appear to have managed not to break anything that was 
already working.


9-)

Thank you.

--
RSB

Re: pkgin repo

[Chavdar Ivanov]

On Tue, 6 Apr 2021 at 22:54, Bob Bernstein  wrote:
>
> I am taking a first run at pkgin. It fails trying to get a file
> from:
>
> https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$arch/9.99.81/All
>
> ...which can be found in my
> /usr/pkg/etc/pkgin/repositories.conf.
>
> I have here:
>   $ uname -a
> NetBSD nebbytwo 9.99.81 NetBSD 9.99.81 (GENERIC) #0: Sat Mar 20
> 14:30:50 UTC 2021
> mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
> amd64


I don't think there are "official" pkgin repos for -current. However,
check https://pkgsrc.joyent.com/install-on-netbsd/ . .
 I haven't used this repo yet, as I maintain a subset at home for the
packages I use.


>
> Given the version of -current I have, what pkgin repository URI
> should I use?
>
> Thank You!
>
> --
> RSB
>


--

Re: pkgin refresh vs. upgrade?

[Lars-Johan Liman]

Mike,

I neglected to thank you for this answer!

Thanks, that actually makes sense.

Cheers,
  /Liman

On 17/06/2020 07:39, Lars-Johan Liman wrote:
>> Hi!

mpumf...@mudcovered.org.uk 2020-06-17 09:37 [+0100]:
> This is all based on observation rather than documentation.

>> When running pkgin to upgrade one or more packages, it often says "X
>> packages to refresh, Y packages to upgrade".

> Refresh means the version hasn't changed but the package has been
> rebuilt since you last installed it from the repository.

>> What's the difference between a refresh and an upgrade of a package?

> Upgrade indicates a version change.

>> And where is it documented? ;-)

> That I don't know. Reason I know the answer is that I build my own
> binary packages and because my build method builds everything every
> time I see a lot more refreshes that I suspect would happen with
> packages coming from a bulk build.

> Mike

Re: pkgin refresh vs. upgrade?

[Mike Pumford]

On 17/06/2020 07:39, Lars-Johan Liman wrote:

Hi!


This is all based on observation rather than documentation.


When running pkgin to upgrade one or more packages, it often says "X
packages to refresh, Y packages to upgrade".

Refresh means the version hasn't changed but the package has been 
rebuilt since you last installed it from the repository.



What's the difference between a refresh and an upgrade of a package?


Upgrade indicates a version change.

And where is it documented? ;-)

That I don't know. Reason I know the answer is that I build my own 
binary packages and because my build method builds everything every time 
I see a lot more refreshes that I suspect would happen with packages 
coming from a bulk build.


Mike

Re: pkgin error (possible workaround)

[matthew sporleder]

Thanks for the report.

On Thu, May 21, 2020 at 12:38 PM Greg Troxel  wrote:
>
> Lars-Johan Liman  writes:
>
> > I've found that the x86_64 and amd64 directories seem to be out of sync
> > on cdn.netbsd.org. In short, pkg_summary seems to be updated in x86_64
> > but not in amd64. For me the following simple workaround worked:
>
> Thanks for the specific report.
>
> > I modified the repository pointer in
> >
> > /usr/pkg/etc/pkgin/repositories.conf
> >
> > from:
> >
> > http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/9.0/All
> >
> > to:
> >
> > http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/9.0/All
>
> amd64 is the name of the port, which is about specific hardware aas well
> as the instruction set, and packages are generally shared among all
> ports with the same instruction set and ABI.   So arguably x86_64 is
> preferred anyway -- even if x86_64 appears only on the amd64 port!
>
> For your info, on ftp.netbsd.org, in /pub/pkgsrc/packages/NetBSD, doing
> ls -l (and skipping the other lines) one gets:
>
>   lrwxrwxr-x   1 joerg netbsd 6 May 28  2008 amd64 -> x86_64
>   drwxrwxr-x  16 pkgmastr  netbsd  1024 May 15 02:57 x86_64
>
> I can confirm the bad behavior.  Fetching
>
>wget 
> http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/9.0/All/pkg_summary.bz2
>wget 
> http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/9.0/All/pkg_summary.bz2
>
> I get the following: (.1 is 2nd fetch):
>
>   -rw-r--r--  1 gdt  users3270343 May 17 16:03 pkg_summary.bz2
>   -rw-r--r--  1 gdt  users3258465 May 21 10:54 pkg_summary.bz2.1

Re: pkgin error (possible workaround)

[Greg Troxel]

Lars-Johan Liman  writes:

> I've found that the x86_64 and amd64 directories seem to be out of sync
> on cdn.netbsd.org. In short, pkg_summary seems to be updated in x86_64
> but not in amd64. For me the following simple workaround worked:

Thanks for the specific report.

> I modified the repository pointer in
>
> /usr/pkg/etc/pkgin/repositories.conf
>
> from:
>
> http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/9.0/All
>
> to:
>
> http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/9.0/All

amd64 is the name of the port, which is about specific hardware aas well
as the instruction set, and packages are generally shared among all
ports with the same instruction set and ABI.   So arguably x86_64 is
preferred anyway -- even if x86_64 appears only on the amd64 port!

For your info, on ftp.netbsd.org, in /pub/pkgsrc/packages/NetBSD, doing
ls -l (and skipping the other lines) one gets:

  lrwxrwxr-x   1 joerg netbsd 6 May 28  2008 amd64 -> x86_64
  drwxrwxr-x  16 pkgmastr  netbsd  1024 May 15 02:57 x86_64

I can confirm the bad behavior.  Fetching

   wget 
http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/9.0/All/pkg_summary.bz2
   wget 
http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/9.0/All/pkg_summary.bz2

I get the following: (.1 is 2nd fetch):

  -rw-r--r--  1 gdt  users3270343 May 17 16:03 pkg_summary.bz2
  -rw-r--r--  1 gdt  users3258465 May 21 10:54 pkg_summary.bz2.1

Re: pkgin error (possible workaround)

[Lars-Johan Liman]

Hi Dima (all)!

I've found that the x86_64 and amd64 directories seem to be out of sync
on cdn.netbsd.org. In short, pkg_summary seems to be updated in x86_64
but not in amd64. For me the following simple workaround worked:

I modified the repository pointer in

/usr/pkg/etc/pkgin/repositories.conf

from:

http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/9.0/All

to:

http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/9.0/All

then ran

# pkgin update

... and it now works just fine.

Why they are out of sync is "beyond my paygrade", and I leave it up to
pkgsrc powers that be to figure that one out. ;-)

Cheers,
  /Liman


kab...@lich.phys.spbu.ru 2020-05-15 19:39 [+0300]:
> I had same problems and I've found that CDN directory contents may be
> not in sync with pkg_summary. I tried to work it out (thinking 
> there might be one server not in sync) but had short time and no
> success so that time I just switched to legacy source.

> How cdn is organized in short? It would be nice to know that to 
> catch the one next time we face the problem.

> On Fri, May 15, 2020 at 12:16:18PM -0400, nottobay wrote:
>> It is saying no such file or directory for /var/db/cache but /var/db/ at
>> 454982 out of 38176044 so space isn't the problem,
>> 
>> On Fri, May 15, 2020, 11:38  wrote:
>> 
>> > Hello,
>> >
>> > On Fri, May 15, 2020 at 11:22:59AM -0400, nottobay wrote:
>> > >I keep getting a bunch of errors saying "download error 
>> > >size does not match pkg_summary" I try just telling it to proceed but
>> > the
>> > >package still doesn't install. I have already tried forcing a pgkin
>> > update
>> > >and it didn't fix it, and I'm using the default repo the NetBSD 9
>> > >installer gave me. How would I fix this?
>> >
>> > Do you have enough disk space in the directry pkin is trying to cache
>> > the downloads? That is, what does
>> >
>> > df /var/db/cache/
>> >
>> > say?
>> >
>> > -is
>> >

> -- 
> Sincerely yours,
> Dima Veselov
> Physics R Establishment of Saint-Petersburg University

-- 
#-
# Lars-Johan Liman, M.Sc.! E-mail: li...@cafax.se
# Cafax AB   ! HTTP  : //www.cafax.se/
# Computer Consultants, Sweden   ! Voice : +46 8 - 564 702 30
#-

Re: pkgin error

[Martin Neitzel]

Hi Matthew,

MN> http://cdn.Netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/...
MN> http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/...
MN> yielded different data.  Both hostnames resolved to the same IP addresses

MS> I fixed the host header thing when that was pointed out.

Thanks for fixing it (back when), and yes, the URL case didn't make a
difference yesterday.  Great to know that shouldn't be any worry anymore.

MS> Anyway try it now.

Much better -- pefect!  Yesterday's different pkgs per 8.0 8.2 8.2 version

MN> % echo 0 1 2 | xargs -n1 -I XX lynx -head -dump 
http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.XX/All/p5-Authen-SASL-2.16nb7.tgz
 | grep Length
MN> Content-Length: 24900
MN> Content-Length: 24892
MN> Content-Length: 24900

changed to 24892 for all three 8.x directories, now matching what's
advertised in the pkg_summary.bz2 (which was "update"able today, too).

All outstanding pkgs downloaded fine today (07:23 UTC),
all 60 pkgs were refreshed/upgraded/installed without a hitch.

Thanks!

Martin Neitzel

Re: pkgin error

[matthew sporleder]

On Sat, May 16, 2020 at 8:42 AM Martin Neitzel
 wrote:
>
> ill> Same here.
> ill>
> ill> $ echo "select file_size from remote_pkg where pkgname like
> ill> 'xmlcatmgr%'" | sqlite3 pkgin.db
> ill> 25004
> ill>
> ill> $ ftp
> ill> 
> https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.0/All/xmlcatmgr-2.2nb1.tgz
> ill> 24864 bytes retrieved in 00:00 (16.63 MiB/s)
>
> Some observations on this:
>
> % echo 0 1 2 | xargs -n1 -I XX lynx -head -dump 
> http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.XX/All/xmlcatmgr-2.2nb1.tgz
>  | grep Length
> Content-Length: 24864
> Content-Length: 24864
> Content-Length: 25004
>
> This actually figures with my(!, see below) long "select" info:
>
> sqlite> select *  from remote_pkg where pkgname like 'xmlcat%' ;
>   PKG_ID = 21533
>  FULLPKGNAME = xmlcatmgr-2.2nb1
>  PKGNAME = xmlcatmgr
>  PKGVERS = 2.2nb1
>   BUILD_DATE = 2020-03-28 20:22:48 +
>  COMMENT = XML and SGML catalog manager
>  LICENSE = modified-bsd
> PKGTOOLS_VERSION = 20091115
> HOMEPAGE = http://xmlcatmgr.sourceforge.net/
>   OS_VERSION = 8.0
>  DESCRIPTION =
>  PKGPATH = textproc/xmlcatmgr
>  PKG_OPTIONS =
>   CATEGORIES = textproc
> SIZE_PKG = 50583
>FILE_SIZE = 25004
>OPSYS = NetBSD
>   REPOSITORY = 
> http://cdn.Netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.2/All
>
>
> Looks like Roland is rather using the 8.0 repo?
>
> I essentially noticed the same problem here, too, after...
>
> - an update on the netbsd-8 branch on May 2nd and
> - moving my /usr/pkg/etc/pkgin/repositories.conf
>   from http://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/8.1/All
>   to   http://cdn.Netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.2/All
> - having nothing at all happen on "pkgin update" until
>   May 11 00:52 /var/db/pkgin/pkgin.db
>
> For "pkgin upgrade", this resulted in:
>
> 31 packages to refresh:  (xmlcatmgr-2.2nb1 ... ... ...)
> 19 packages to upgrade:
> 2 packages to install:  heimdal-1.5.3nb24 openssl-1.1.1e
>
> (I was mostly surprised about the "refresh" section.  Where does this
> come from, what is this supposed to mean?)
>
> Since I'm referring to 8.2 pkg repository, details differ for me,
> I guess I am seeing the same problem but maybe from the other side.
>
> I can still confirm the problem / the error message seen from
> my side, albeit with other packages.
>
> I get the error message with:
> download error: p5-Authen-SASL-2.16nb7 size does not match pkg_summary
>
> and [abridged]:
>
> sqlite> select *  from remote_pkg where pkgname like 'p5-Authen-SASL' ;
>   PKG_ID = 6173
>  FULLPKGNAME = p5-Authen-SASL-2.16nb7
>   BUILD_DATE = 2020-04-01 03:57:23 +
>   OS_VERSION = 8.0
> SIZE_PKG = 119267
>FILE_SIZE = 24892
>   REPOSITORY = 
> http://cdn.Netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.2/All
>
> % echo 0 1 2 | xargs -n1 -I XX lynx -head -dump 
> http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.XX/All/p5-Authen-SASL-2.16nb7.tgz
>  | grep Length
> Content-Length: 24900
> Content-Length: 24892
> Content-Length: 24900
>
> D'oh!
>
>
> This is not the first time this madness happens.  The last time was around
> last summer and some kind fellow on the ircnet #netbsd pointed out to me
> that the URLs
>
> http://cdn.Netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/...
> http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/...
>^
>|
>
> yielded different data.  Both hostnames resolved to the same IP addresses
> (as they should) but the Fastly CDN servers were apparently treating the
> requests in different ways depending on the case in the Host: headers.
>
> Martin Neitzel

I fixed the host header thing when that was pointed out.

Anyway try it now.

Re: pkgin error

[Martin Neitzel]

ill> Same here.
ill>
ill> $ echo "select file_size from remote_pkg where pkgname like
ill> 'xmlcatmgr%'" | sqlite3 pkgin.db
ill> 25004
ill>
ill> $ ftp
ill> 
https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.0/All/xmlcatmgr-2.2nb1.tgz
ill> 24864 bytes retrieved in 00:00 (16.63 MiB/s)

Some observations on this:

% echo 0 1 2 | xargs -n1 -I XX lynx -head -dump 
http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.XX/All/xmlcatmgr-2.2nb1.tgz
 | grep Length
Content-Length: 24864
Content-Length: 24864
Content-Length: 25004

This actually figures with my(!, see below) long "select" info:

sqlite> select *  from remote_pkg where pkgname like 'xmlcat%' ;
  PKG_ID = 21533
 FULLPKGNAME = xmlcatmgr-2.2nb1
 PKGNAME = xmlcatmgr
 PKGVERS = 2.2nb1
  BUILD_DATE = 2020-03-28 20:22:48 +
 COMMENT = XML and SGML catalog manager
 LICENSE = modified-bsd
PKGTOOLS_VERSION = 20091115
HOMEPAGE = http://xmlcatmgr.sourceforge.net/
  OS_VERSION = 8.0
 DESCRIPTION = 
 PKGPATH = textproc/xmlcatmgr
 PKG_OPTIONS = 
  CATEGORIES = textproc
SIZE_PKG = 50583
   FILE_SIZE = 25004
   OPSYS = NetBSD
  REPOSITORY = 
http://cdn.Netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.2/All


Looks like Roland is rather using the 8.0 repo?

I essentially noticed the same problem here, too, after...

- an update on the netbsd-8 branch on May 2nd and
- moving my /usr/pkg/etc/pkgin/repositories.conf
  from http://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/8.1/All
  to   http://cdn.Netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.2/All
- having nothing at all happen on "pkgin update" until
  May 11 00:52 /var/db/pkgin/pkgin.db

For "pkgin upgrade", this resulted in:

31 packages to refresh:  (xmlcatmgr-2.2nb1 ... ... ...)
19 packages to upgrade:
2 packages to install:  heimdal-1.5.3nb24 openssl-1.1.1e

(I was mostly surprised about the "refresh" section.  Where does this
come from, what is this supposed to mean?)

Since I'm referring to 8.2 pkg repository, details differ for me,
I guess I am seeing the same problem but maybe from the other side.

I can still confirm the problem / the error message seen from
my side, albeit with other packages.

I get the error message with:
download error: p5-Authen-SASL-2.16nb7 size does not match pkg_summary

and [abridged]:

sqlite> select *  from remote_pkg where pkgname like 'p5-Authen-SASL' ;
  PKG_ID = 6173
 FULLPKGNAME = p5-Authen-SASL-2.16nb7
  BUILD_DATE = 2020-04-01 03:57:23 +
  OS_VERSION = 8.0
SIZE_PKG = 119267
   FILE_SIZE = 24892
  REPOSITORY = 
http://cdn.Netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.2/All

% echo 0 1 2 | xargs -n1 -I XX lynx -head -dump 
http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.XX/All/p5-Authen-SASL-2.16nb7.tgz
 | grep Length
Content-Length: 24900
Content-Length: 24892
Content-Length: 24900

D'oh!


This is not the first time this madness happens.  The last time was around
last summer and some kind fellow on the ircnet #netbsd pointed out to me
that the URLs

http://cdn.Netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/...
http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/...
   ^
   |

yielded different data.  Both hostnames resolved to the same IP addresses
(as they should) but the Fastly CDN servers were apparently treating the
requests in different ways depending on the case in the Host: headers.

Martin Neitzel

Re: pkgin error

[Roland Illig]

On 15.05.2020 17:22, nottobay wrote:

I keep getting a bunch of errors saying "download error 
size does not match pkg_summary" I try just telling it to proceed but
the package still doesn't install. I have already tried forcing a pgkin
update and it didn't fix it, and I'm using the default repo the NetBSD 9
installer gave me. How would I fix this?


Same here.

$ echo "select file_size from remote_pkg where pkgname like
'xmlcatmgr%'" | sqlite3 pkgin.db
25004

$ ftp
https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.0/All/xmlcatmgr-2.2nb1.tgz
24864 bytes retrieved in 00:00 (16.63 MiB/s)

The strange thing is that the +BUILD_INFO inside that package says:

BUILD_DATE=2019-12-21 05:36:25 +

Yet the mtime on cdn.NetBSD.org is 28-Mar-2020 20:22.

What's going on here? In this situation I'm missing cryptographically
signed packages since the default transport protocol is "http" without
any "s".

Re: pkgin error

[Dima Veselov]

I had same problems and I've found that CDN directory contents may be
not in sync with pkg_summary. I tried to work it out (thinking 
there might be one server not in sync) but had short time and no
success so that time I just switched to legacy source.

How cdn is organized in short? It would be nice to know that to 
catch the one next time we face the problem.

On Fri, May 15, 2020 at 12:16:18PM -0400, nottobay wrote:
> It is saying no such file or directory for /var/db/cache but /var/db/ at
> 454982 out of 38176044 so space isn't the problem,
> 
> On Fri, May 15, 2020, 11:38  wrote:
> 
> > Hello,
> >
> > On Fri, May 15, 2020 at 11:22:59AM -0400, nottobay wrote:
> > >I keep getting a bunch of errors saying "download error 
> > >size does not match pkg_summary" I try just telling it to proceed but
> > the
> > >package still doesn't install. I have already tried forcing a pgkin
> > update
> > >and it didn't fix it, and I'm using the default repo the NetBSD 9
> > >installer gave me. How would I fix this?
> >
> > Do you have enough disk space in the directry pkin is trying to cache
> > the downloads? That is, what does
> >
> > df /var/db/cache/
> >
> > say?
> >
> > -is
> >

-- 
Sincerely yours,
Dima Veselov
Physics R Establishment of Saint-Petersburg University

Re: pkgin error

[nottobay]

It is saying no such file or directory for /var/db/cache but /var/db/ at
454982 out of 38176044 so space isn't the problem,

On Fri, May 15, 2020, 11:38  wrote:

> Hello,
>
> On Fri, May 15, 2020 at 11:22:59AM -0400, nottobay wrote:
> >I keep getting a bunch of errors saying "download error 
> >size does not match pkg_summary" I try just telling it to proceed but
> the
> >package still doesn't install. I have already tried forcing a pgkin
> update
> >and it didn't fix it, and I'm using the default repo the NetBSD 9
> >installer gave me. How would I fix this?
>
> Do you have enough disk space in the directry pkin is trying to cache
> the downloads? That is, what does
>
> df /var/db/cache/
>
> say?
>
> -is
>

Re: pkgin error

[ignatios]

Hello,

On Fri, May 15, 2020 at 11:22:59AM -0400, nottobay wrote:
>I keep getting a bunch of errors saying "download error 
>size does not match pkg_summary" I try just telling it to proceed but the
>package still doesn't install. I have already tried forcing a pgkin update
>and it didn't fix it, and I'm using the default repo the NetBSD 9
>installer gave me. How would I fix this?

Do you have enough disk space in the directry pkin is trying to cache
the downloads? That is, what does 

df /var/db/cache/

say?

-is

Re: pkgin

[Pedro Pinho]

Thx!
Yes, that's understandable. Still, https://gitlab.com/iMil/pkgin
looks to be outdated as well :(
The best would be if http://pkgin.net/ pointed to
https://github.com/joyent/pkgin which seems to be the master branch.

Den fre 19 okt. 2018 15:45matthew sporleder  skrev:

> On Thu, Oct 18, 2018 at 3:24 AM Pedro Pinho  wrote:
> >
> > Hi all,
> > I'm rather new to NetBSD, been using it on a laptop for about 3 months
> now, amd64 8.0. I'm really enjoying this OS and everything is working fine.
> So, sorry if this has already been answered...
> >
> > Why does http://pkgin.net/ points to https://github.com/NetBSDfr/pkgin ?
> > This github repo has not seen any commit for the last two years.
> > Wouldn't be better if it would point to https://github.com/joyent/pkgin
> , just like pkgsrc.se does?
> > Is there a reason for it?
> >
> > Thanks!
>
> I'm guessing it has something to do with the text you can find here:
> https://github.com/iMilnb  :)
>
> Anyway good suggestion.
>

Re: pkgin

[matthew sporleder]

On Thu, Oct 18, 2018 at 3:24 AM Pedro Pinho  wrote:
>
> Hi all,
> I'm rather new to NetBSD, been using it on a laptop for about 3 months now, 
> amd64 8.0. I'm really enjoying this OS and everything is working fine. So, 
> sorry if this has already been answered...
>
> Why does http://pkgin.net/ points to https://github.com/NetBSDfr/pkgin ?
> This github repo has not seen any commit for the last two years.
> Wouldn't be better if it would point to https://github.com/joyent/pkgin , 
> just like pkgsrc.se does?
> Is there a reason for it?
>
> Thanks!

I'm guessing it has something to do with the text you can find here:
https://github.com/iMilnb  :)

Anyway good suggestion.

Re: pkgin repo change

[Pedro Pinho]

Thanks!
Just waiting for the mirrors to sync, then I'll change back my
repositories.conf
:)

Den ons 19 sep. 2018 06:21  skrev:

> On Tue, Sep 18, 2018 at 08:59:55PM -0400, Eric Hawicz wrote:
> > On 9/18/2018 4:37 AM, Pedro Pinho wrote:
> > > This morning trying to update/upgrade my system I got the following,
> > > |~$ sudo pkgin update Password: processing remote summary
> > > (http://ftp.fr.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/8.0 pkgin:
> > > Could not fetch
> > > http://ftp.fr.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/8.0/All|
> > > Looking closer at the problem, I found that the repo has changed
> > > yesterday at 06:25, and the correct URL should now be
> > >
> http://ftp.fr.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.0_2018Q2/All/
> > >
> > > This is not an issue, as I only had to edit
> > > /usr/pkg/etc/pkgin/repositories.conf on my system and everything is
> good
> > > again.
> > > I'm new to NetBSD and I'm wondering where/if such changes are usually
> > > not announced.
> >
> > That sounds to me like a "8.0" symlink was lost.  We have symlinks for
> > various other releases, and 8.0 symlinks for other architectures, so I'm
> > guessing this is just a mistake.
> > I'm cc'ing the pkgsrc releng team, who can probably do something to fix
> > this.
>
> now there's
> 7.1 -> 7.1_2018Q2
> 7.1.1 -> 7.1
> 7.1.2 -> 7.1
> 7.2 -> 7.1
> 8.0 -> 8.0_2018Q2
> for NetBSD/{i386,amd64}.
>
> Hopefully nobody has a script to set it to some weird configuration.
>

Re: pkgin repo change

[maya]

On Tue, Sep 18, 2018 at 08:59:55PM -0400, Eric Hawicz wrote:
> On 9/18/2018 4:37 AM, Pedro Pinho wrote:
> > This morning trying to update/upgrade my system I got the following,
> > |~$ sudo pkgin update Password: processing remote summary
> > (http://ftp.fr.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/8.0 pkgin:
> > Could not fetch
> > http://ftp.fr.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/8.0/All|
> > Looking closer at the problem, I found that the repo has changed
> > yesterday at 06:25, and the correct URL should now be
> > http://ftp.fr.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.0_2018Q2/All/
> > 
> > This is not an issue, as I only had to edit
> > /usr/pkg/etc/pkgin/repositories.conf on my system and everything is good
> > again.
> > I'm new to NetBSD and I'm wondering where/if such changes are usually
> > not announced.
> 
> That sounds to me like a "8.0" symlink was lost.  We have symlinks for
> various other releases, and 8.0 symlinks for other architectures, so I'm
> guessing this is just a mistake.
> I'm cc'ing the pkgsrc releng team, who can probably do something to fix
> this.

now there's
7.1 -> 7.1_2018Q2
7.1.1 -> 7.1
7.1.2 -> 7.1
7.2 -> 7.1
8.0 -> 8.0_2018Q2
for NetBSD/{i386,amd64}.

Hopefully nobody has a script to set it to some weird configuration.

Re: pkgin repo change

[Eric Hawicz]

On 9/18/2018 4:37 AM, Pedro Pinho wrote:

This morning trying to update/upgrade my system I got the following,
|~$ sudo pkgin update Password: processing remote summary 
(http://ftp.fr.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/8.0 pkgin: 
Could not fetch 
http://ftp.fr.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/8.0/All|
Looking closer at the problem, I found that the repo has changed 
yesterday at 06:25, and the correct URL should now be 
http://ftp.fr.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.0_2018Q2/All/


This is not an issue, as I only had to edit 
/usr/pkg/etc/pkgin/repositories.conf on my system and everything is 
good again.
I'm new to NetBSD and I'm wondering where/if such changes are usually 
not announced.


That sounds to me like a "8.0" symlink was lost.  We have symlinks for 
various other releases, and 8.0 symlinks for other architectures, so I'm 
guessing this is just a mistake.
I'm cc'ing the pkgsrc releng team, who can probably do something to fix 
this.


Eric

Re: pkgin with NetBSD 8.0_BETA

[Greg Troxel]

George Georgalis  writes:

> Thanks for the breakout, trying to work out the best way to smooth the
> ride. Indeed, I had a kernel derived 8.0 ${PKG_PATH}/pkgin and a
> personal pkgin configuration script hard coded the (7.0.2) repository,
> artifacts trying to reliably derive it in the past.

The pkgsrc/pkgin world expects a match between kernel, userland, and
built packages (and hence PKGPATH).  Departing from that will cause
trouble

> Today, an invalid repositories.conf.example is installed as part of
> pkg_add ${PKG_PATH}/pkgin
>
> ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/$arch/8.99.1/All

That sounds like a bug, and you  can perhaps figure out where it comes
from and report it with a patch to fix it.

> Why? it is unclear when that repository would ever be valid. Could the
> pkgin install derive and setup a functional configuration, as a best
> (better) guess? Or, Is it possible to identify a PKG_PATH scheme that
> is reliable across the various (pre-)releases, at least for kernels
> that have compatible binaries available?

The approach seems to be to do this at build time.  If pkgin while built
on 8.0_BETA produces a path of 8.99.1, that sounds wrong.

But the real issue is that for other than real releases, it's iffy if
there are packages.

In general, people not on releases probably have to pay attention to all
these details, figure out if there are packages, adjust the path, and be
careful.   As always, patches weclome if you can smooth out rough edges
in a sound way.


signature.asc
Description: PGP signature

Re: pkgin with NetBSD 8.0_BETA

[George Georgalis]

On Thu, Sep 7, 2017 at 7:45 AM, Greg Troxel  wrote:
>
> George Georgalis  writes:
>
>> Not sure if I'm doing something wrong or if this relates to _BETA.
>
> I would not be surpised by some rough edges around 8.0 pre-release.

Thanks for the breakout, trying to work out the best way to smooth the
ride. Indeed, I had a kernel derived 8.0 ${PKG_PATH}/pkgin and a
personal pkgin configuration script hard coded the (7.0.2) repository,
artifacts trying to reliably derive it in the past.

Today, an invalid repositories.conf.example is installed as part of
pkg_add ${PKG_PATH}/pkgin

ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/$arch/8.99.1/All

Why? it is unclear when that repository would ever be valid. Could the
pkgin install derive and setup a functional configuration, as a best
(better) guess? Or, Is it possible to identify a PKG_PATH scheme that
is reliable across the various (pre-)releases, at least for kernels
that have compatible binaries available?

-George


-- 
George Georgalis, (415) 894-2710, http://www.galis.org/

Re: pkgin with NetBSD 8.0_BETA

[Greg Troxel]

George Georgalis  writes:

> Not sure if I'm doing something wrong or if this relates to _BETA.

I would not be surpised by some rough edges around 8.0 pre-release.

> After a minimal (GENERIC.201708260340Z) amd64 install,
>
> # URLROOT="http://ftp.netbsd.org/pub/;
> # PKG_PATH="${URLROOT}/pkgsrc/packages/NetBSD/$(uname -m)/$(uname
> -r|cut -f 1 -d _)/All"
> # echo ${PKG_PATH}
> http://ftp.netbsd.org/pub//pkgsrc/packages/NetBSD/amd64/8.0/All
> # pkg_add ${PKG_PATH}/pkgin
> pkg_add: package `pkgin-0.9.4nb6' already recorded as installed

This does not make sense.  You said "after a minimal install". but
pkg_add says it is already installed.   I would recommend doing
"pkg_info" and looking in /var/db/pkg to see what is there.

> # pkg_add ${PKG_PATH}/openssl
> pkg_add: package `openssl-1.0.2k' already recorded as installed

Again, "already".  Why do you want to install openssl?  The base system
version should be fine.  But that is probably not your issue.

> # pkgin update
> Shared object "libcrypto.so.8" not found

There is a /lib/libcrypto.so.8 in NetBSD 7 stable; mine has a ctime of
9/5 which is the most recent time I did an update along the branch.

My pkgin, built for -7 and running on 7, links against libcrypto.so.8,
and works.

I would recommend, after you are really sure you are stating with just
8.0 beta and not other stuff, to download the packages manually, unpack
them in a temp dir, and see what they are linked against.   You have
enough steps and uncertainty going on that it's hard to tell what the
issue is.

I grabbed the pkgin binary from the ftp server, located at:

  /pub/pkgsrc/packages/NetBSD/x86_64/8.0_2017Q2/All

(amd64 is a symlink to x86_64, and 8.0 to 8.0_2017Q2, so this seems like
your PKGPATH) and untarred it and ran ldd and got:

./pkgin:
-lbz2.1 => /usr/lib/libbz2.so.1
-lgcc_s.1 => /usr/lib/libgcc_s.so.1
-lc.12 => /usr/lib/libc.so.12
-lz.1 => /usr/lib/libz.so.1
-larchive.4 => not found
-lpthread.1 => /usr/lib/libpthread.so.1
-lcrypto.12 => not found
-lssl.12 => not found
-lsqlite3.1 => /usr/lib/libsqlite3.so.1

which looks right - the 12 matches your listing of what's on your system.



You are using packages built against 8, but consider the situation
before 8 was branched and before there were packages for 8.  If one
wanted to run current and use packages from 7, the thing to do would be
to install 7 and then update to current, so that the old libs are
around.

But, in general it does not work to e.g. mix packages built on current
and packages built on 7, because they'll end up pulling in different
library versions.



signature.asc
Description: PGP signature

Re: pkgin: how to remove all package

[Ivan "Rambius" Ivanov]

Hello,

Thank you for the link. The examples in it use pkg_delete, though. Are
there plans to extend pkgin remove with similar functionality?

Regards
rambius

On Wed, Jul 26, 2017 at 4:30 PM, Jay Patel  wrote:
> I think this should do the trick
> https://wiki.netbsd.org/pkgsrc/how_to_upgrade_packages/#index8h2
>
> On 26-Jul-2017 6:55 PM, "Ivan "Rambius" Ivanov"
>  wrote:
>>
>> Hello,
>>
>> How can I remove all installed packages using pkgin?
>>
>> Regards
>> rambius
>>
>> --
>> Tangra Mega Rock: http://www.radiotangra.com



-- 
Tangra Mega Rock: http://www.radiotangra.com

Re: pkgin: how to remove all package

[Jay Patel]

I think this should do the trick
https://wiki.netbsd.org/pkgsrc/how_to_upgrade_packages/#index8h2

On 26-Jul-2017 6:55 PM, "Ivan "Rambius" Ivanov" <
rambiusparkisan...@gmail.com> wrote:

> Hello,
>
> How can I remove all installed packages using pkgin?
>
> Regards
> rambius
>
> --
> Tangra Mega Rock: http://www.radiotangra.com
>

Re: pkgin giving "download mismatch"

[D'Arcy J.M. Cain]

On Wed, 2 Sep 2015 12:37:40 -0400
"D'Arcy J.M. Cain"  wrote:
> The actual size of the file is 414007 bytes.  The file size shown in
> the summary file is 1528317.  This is the output of "pkg_info -Xa" as
> suggested by the guide.  So where does it get 70120480?  That number
> is not in the package summary at all.

Well, I don't know what changed, pkgin or pkg_info but here's what I
had to do.  The guide says that "pkg_info -X -a" gives me the summary
that I need but it doesn't.  Here is my script that does.

#! /bin/sh

ALL=/usr/pkgsrc/packages/All

pkg_info -X -a | while read x
do
  echo $x
  if [ "`echo $x | cut -d= -f1`" = "PKGNAME" ]
  then
eval $(stat -s "$ALL/$(echo $x | cut -d= -f2).tgz")
echo "FILESIZE=$st_size"
  fi
done | gzip > $ALL/pkg_summary.gz

This takes just over a minute to run.  It sure would be nice if
pkg_info were to grow a FILESIZE output line.

-- 
D'Arcy J.M. Cain 
http://www.NetBSD.org/ IM:da...@vex.net

Re: pkgin giving "download mismatch"

[D'Arcy J.M. Cain]

On Thu, 27 Aug 2015 08:57:27 -0400
"D'Arcy J.M. Cain"  wrote:
> downloading packages...
> p5-Mozilla-CA-20150826.tgz 100%  155KB 155.0KB/s 155.0KB/s 00:00
> pkgin: download
> mismatch: /var/db/pkgin/cache/p5-Mozilla-CA-20150826.tgz

Anyone have any clue here yet?  I just upgraded my pkgin to the latest
version (pkg_delete/pkg_add still works) and still have the same
problem.

-- 
D'Arcy J.M. Cain 
http://www.NetBSD.org/ IM:da...@vex.net

Re: pkgin giving "download mismatch"

[D'Arcy J.M. Cain]

On Wed, 2 Sep 2015 11:29:53 -0400
"D'Arcy J.M. Cain"  wrote:
> Anyone have any clue here yet?  I just upgraded my pkgin to the latest
> version (pkg_delete/pkg_add still works) and still have the same
> problem.

I think I have found the problem.  I added a bit of debug code to pkgin
and now the error message is:

 download mismatch: /var/db/pkgin/cache/py27-setuptools-18.2.tgz 414007
 70120480

The actual size of the file is 414007 bytes.  The file size shown in
the summary file is 1528317.  This is the output of "pkg_info -Xa" as
suggested by the guide.  So where does it get 70120480?  That number is
not in the package summary at all.

-- 
D'Arcy J.M. Cain 
http://www.NetBSD.org/ IM:da...@vex.net

Re: pkgin giving download mismatch

[Ottavio Caruso]

On 27 August 2015 at 13:57, D'Arcy J.M. Cain da...@netbsd.org wrote:
 Then I went to the
 repository server and did rm
 -rf /usr/pkgsrc/packages/* /var/db/pkg* /usr/pkg/* and rebuilt
 everything from scratch and still have the issue.

Is this your own repository server or a NetBSD mirror?

-- 
Ottavio

Re: pkgin giving download mismatch

[Jeremy C. Reed]

Maybe on download server side the pkg_summary(5) available database 
doesn't match the actual download package.

Re: pkgin giving download mismatch

[D'Arcy J.M. Cain]

On Thu, 27 Aug 2015 15:54:14 +0100
Ottavio Caruso ottavio2006-net...@yahoo.com wrote:
 On 27 August 2015 at 13:57, D'Arcy J.M. Cain da...@netbsd.org wrote:
  Then I went to the
  repository server and did rm
  -rf /usr/pkgsrc/packages/* /var/db/pkg* /usr/pkg/* and rebuilt
  everything from scratch and still have the issue.
 
 Is this your own repository server or a NetBSD mirror?

My own.  I build everything from source with my own options and then
propagate it to all of my servers.

-- 
D'Arcy J.M. Cain da...@netbsd.org
http://www.NetBSD.org/ IM:da...@vex.net

Re: pkgin giving download mismatch

[D'Arcy J.M. Cain]

On Thu, 27 Aug 2015 09:51:00 -0500 (CDT)
Jeremy C. Reed r...@reedmedia.net wrote:
 Maybe on download server side the pkg_summary(5) available database 
 doesn't match the actual download package.

As I said, I wiped out everything on both sides and started over.
Everything is freshly built.


-- 
D'Arcy J.M. Cain da...@netbsd.org
http://www.NetBSD.org/ IM:da...@vex.net

Re: pkgin giving download mismatch

[D'Arcy J.M. Cain]

On Thu, 27 Aug 2015 16:11:24 +0100
Ottavio Caruso ottavio2006-net...@yahoo.com wrote:
 What's in your repositories.conf?

The system default.  I haven't touched it.  Instead I have set
PKG_REPOS in my environment to point to my repository.

Side issue - I also set PKG_PATH to the same thing for pkg_add.  It
would have been nice if both tools used the same environment variable.

-- 
D'Arcy J.M. Cain da...@netbsd.org
http://www.NetBSD.org/ IM:da...@vex.net

Re: pkgin fails to install in the install kernel

[David Brownlee]

It was using more than 640M of VM?

While I agree not having a failure reported as success would be the
top priority, the thought that it was using that much VM during
install is... scary.

What arch is this on? i386 has a set_swap() in sysinst to use
swapspace if less than 32M of ram, but amd64 does not... I suspect
that check should be made MI...


On 15 November 2014 16:15, Andy Ruhl acr...@gmail.com wrote:
 I've attached 3 screenshots. During each attempt, I was installing in a
 virtual machine. The first (that I didn't document) was a Linux KVM. This
 time was on VMWare Fusion (with screenshots). Each time I set it up with 128
 megs of memory, 512 megs of swap, and a 15 gig disk.

 The concern is not necessarily that the pkgin config process failed, it's
 that it was marked as completed afterward.

 Andy

 On Fri, Nov 14, 2014 at 3:37 PM, Andy Ruhl acr...@gmail.com wrote:

 Hello all.

 I just had something happen that I didn't capture but I will try to at
 some point.

 This is when trying to install pkgin using the install kernel just after
 the full install of sets is finished.

 During the building database phase, it issued a message something like
 killed, ran out of swap.

 But the process ended and returned to the menu. The process was marked as
 DONE.

 Seems like it should be marked failed if the process fails?

 I searched a bit and I see a few PRs but nothing specific to pkgin failing
 and then getting marked DONE. Is this a bug?

 Andy

Re: pkgin fails to install in the install kernel

[David Brownlee]

On 16 November 2014 13:50, Andy Ruhl acr...@gmail.com wrote:
 On Sun, Nov 16, 2014 at 5:49 AM, David Brownlee a...@absd.org wrote:

 It was using more than 640M of VM?

 While I agree not having a failure reported as success would be the
 top priority, the thought that it was using that much VM during
 install is... scary.

 What arch is this on? i386 has a set_swap() in sysinst to use
 swapspace if less than 32M of ram, but amd64 does not... I suspect
 that check should be made MI...

 It was amd64, specifically from here:
 ftp://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201411140020Z/amd64/installation/cdrom/boot.iso

OK, so that would have been more than 128M (actually from reading the
source, that would have been 128M for i386 also - see email to
tech-install@ re making set_swap() MI)

 I just tried i386 from the same build date and unfortunately there is no
 pkgin for it yet so I didn't prove what you said.

 I can test another version if that would be helpful.

If you had some space time it would be great if you could take a poke
at sysinst and add the return value checks missing in the run_program
calls that use pkgin. Otherwise I can see if I have time sometime
soon...

Re: Pkgin Binaries

[Francisco Valladolid H.]

Hi.

NetBSD binary packages for 6.1.5 don't exist, you can use

ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/6.0_2014Q3/All

6.1.5 directory is symlink to 6.0

Regards
On Nov 11, 2014 5:44 PM, Will Dignazio wdigna...@gmail.com wrote:

 I'm not sure if this was intentional, but it appears that the built binary
 packages for 6.1.5, and several others have been removed. I noticed earlier
 today when doing an install, when the binary pkgin setup failed.

 I've looked around, but there doesn't seem to be a schedule or notification
 about it. Was there a reason, or is there a typical schedule on which they
 are
 removed and rebuilt?

 Mirror in question:
 http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/6.1.5/

 Though it appears that almost all of the 6.X.X have 'lost' their built
 packages.

 -- Will

Re: Pkgin Binaries

[Will Dignazio]

Hello,

Strange, is that symlink intermittent? I had used the 6.1.5 url
previously without
any problems.

Thanks!

-- Will

On Tue, Nov 11, 2014 at 7:03 PM, Francisco Valladolid H.
fic...@gmail.com wrote:
 Hi.

 NetBSD binary packages for 6.1.5 don't exist, you can use

 ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/6.0_2014Q3/All

 6.1.5 directory is symlink to 6.0

 Regards

 On Nov 11, 2014 5:44 PM, Will Dignazio wdigna...@gmail.com wrote:

 I'm not sure if this was intentional, but it appears that the built binary
 packages for 6.1.5, and several others have been removed. I noticed
 earlier
 today when doing an install, when the binary pkgin setup failed.

 I've looked around, but there doesn't seem to be a schedule or
 notification
 about it. Was there a reason, or is there a typical schedule on which they
 are
 removed and rebuilt?

 Mirror in question:
 http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/6.1.5/

 Though it appears that almost all of the 6.X.X have 'lost' their built
 packages.

 -- Will



-- 
Bytes go in, words go out

Re: Pkgin Binaries

[Will Dignazio]

Ah, never mind, I see what happened. I didn't realize the quarter had changed.

Although, I find it odd that the new symlink is set before the
directory is populated
with built packages.

-- Will

On Tue, Nov 11, 2014 at 7:09 PM, Will Dignazio wdigna...@gmail.com wrote:
 Hello,

 Strange, is that symlink intermittent? I had used the 6.1.5 url
 previously without
 any problems.

 Thanks!

 -- Will

 On Tue, Nov 11, 2014 at 7:03 PM, Francisco Valladolid H.
 fic...@gmail.com wrote:
 Hi.

 NetBSD binary packages for 6.1.5 don't exist, you can use

 ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/6.0_2014Q3/All

 6.1.5 directory is symlink to 6.0

 Regards

 On Nov 11, 2014 5:44 PM, Will Dignazio wdigna...@gmail.com wrote:

 I'm not sure if this was intentional, but it appears that the built binary
 packages for 6.1.5, and several others have been removed. I noticed
 earlier
 today when doing an install, when the binary pkgin setup failed.

 I've looked around, but there doesn't seem to be a schedule or
 notification
 about it. Was there a reason, or is there a typical schedule on which they
 are
 removed and rebuilt?

 Mirror in question:
 http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/6.1.5/

 Though it appears that almost all of the 6.X.X have 'lost' their built
 packages.

 -- Will



 --
 Bytes go in, words go out



-- 
Bytes go in, words go out

Re: Pkgin Binaries

[Greg Troxel]

Will Dignazio wdigna...@gmail.com writes:

 Strange, is that symlink intermittent? I had used the 6.1.5 url
 previously without
 any problems.

I really doubt it's intermittent.  I read the message, misremembered,
and went to the i386 directory, and 6.1.5 was missing, and I added it
and assumed I had addressed the question.  The place it points to really
does have packages.

In amd64, the symlink was already there, but the place it pointed to
didn't get the packages uploaded.

But the symlink is just a symlink in a filesystem on the machine that
hosts the ftp space.


pgphLiIm4NJhw.pgp
Description: PGP signature

Re: Aw: Re: pkgin: mplayer-1.1.1nb1 is not available on the repository

[Aleksej Saushev]

Carsten Kunze carsten.ku...@arcor.de writes:

  Are not all packages available for all amd64 NetBSD releases? And if
 yes--why did pkgin not know this?
 
 You cannot distribute useful binary package for MPlayer for legal reasons.

 I know that from Linux, but had not expected it on NetBSD.

This is the problem in the law, not in NetBSD.

 But if that's the reason why does pkgin avail list it?
 Or do I have do setup an alternative server path to be able to install it?

Just build it from the source, it takes only fifteen minutes with decent
hardware and internet connectivity.


-- 
HE CE3OH...

Re: pkgin: mplayer-1.1.1nb1 is not available on the repository

[Aleksej Saushev]

Carsten Kunze carsten.ku...@arcor.de writes:

 on trying to install mplayer on NetBSD 6.1.4 amd64 I got the following output:

 # pkgin install mplayer
 calculating dependencies... done.

 nothing to upgrade.

...

 I did not setup a special server for that so the default server is used.

 Are not all packages available for all amd64 NetBSD releases? And if yes--why 
 did pkgin not know this?

You cannot distribute useful binary package for MPlayer for legal reasons.


-- 
HE CE3OH...

Aw: Re: pkgin: mplayer-1.1.1nb1 is not available on the repository

[Carsten Kunze]

  Are not all packages available for all amd64 NetBSD releases? And if
 yes--why did pkgin not know this?
 
 You cannot distribute useful binary package for MPlayer for legal reasons.

I know that from Linux, but had not expected it on NetBSD.

But if that's the reason why does pkgin avail list it? Or do I have do setup 
an alternative server path to be able to install it?

Aw: Re: pkgin: mplayer-1.1.1nb1 is not available on the repository

[Carsten Kunze]

 Did you do a
 
 pkgin up

The system had been installed 3 days ago. I did not made an update, but if I do 
it does not change anything.

 by any chance?  When I do a
 
 pkgin av
 
 it shows that
 
 mplayer-1.1.1nb3  Fast, cross-platform movie player
 
 is available.

Exactly what I am saying. It thinks it is available but it is not (I get the 
same output like you, but if I do the install it is not there.)

Re: Re: pkgin: mplayer-1.1.1nb1 is not available on the repository

[Christian Koch]

On Thu, Jul 17, 2014 at 12:11:26AM +0200, Carsten Kunze wrote:
   Are not all packages available for all amd64 NetBSD releases? And if
  yes--why did pkgin not know this?
  
  You cannot distribute useful binary package for MPlayer for legal reasons.
 
 I know that from Linux, but had not expected it on NetBSD.
 
 But if that's the reason why does pkgin avail list it?

I'm not sure. But as already mentioned, it would be worth performing pkgin up
-- there's a version of the MPlayer package newer than what your system is aware
of. 

On Thu, Jul 17, 2014 at 12:11:26AM +0200, Carsten Kunze wrote:
 Or do I have do setup an alternative server path to be able to install it?

Depending on what you need from MPlayer, it *will* be necessary to let pkgsrc
know about some non-default details.

For example, the following is in my /etc/mk.conf:

LIBDVDCSS_MASTER_SITES=http://download.videolan.org/pub/libdvdcss/
ACCEPTABLE_LICENSES+= libdvdcss-license
ACCEPTABLE_LICENSES+= mplayer-codec-license

This lets me play commercial DVDs on my NetBSD laptop. But AFAIK the only way to
install MPlayer this way is to not use binary pakages -- you'll have to compile
from source.

-Christian

Re: Aw: Re: pkgin: mplayer-1.1.1nb1 is not available on the repository

[Jeremy C. Reed]

On Thu, 17 Jul 2014, Carsten Kunze wrote:

 But if that's the reason why does pkgin avail list it? Or do I have 
 do setup an alternative server path to be able to install it?

I assume the pkg_summary(5) database was created using a repo of 
packages that included some packages not allowed to be served. The 
problem package was either removed or at least not uploaded. So the 
list of available packages doesn't match.

I didn't look at old email in this thread to see what repo has problem. 
But I have a few scripts to check sanity of the repo and see many 
potential problems, including:
http://ftp.netbsd.org/pub/NetBSD/misc/reed/pkgsrc-package-sanity/missing-or-old-pkg_summary.txt

See 
http://ftp.netbsd.org/pub/NetBSD/misc/reed/pkgsrc-package-sanity/README 
for some details