New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Undefined symbol "utimensat" #8

Closed
rknetwork opened this Issue Jan 14, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@rknetwork

rknetwork commented Jan 14, 2017

I'm getting Undefined symbol "utimensat" error when trying to upgrade to version 0.2.6.

root@host:/usr/home/alex # pkg upgrade indexinfo
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
indexinfo: 0.2.5 -> 0.2.6

Number of packages to be upgraded: 1

Proceed with this action? [y/N]: y
[1/1] Upgrading indexinfo from 0.2.5 to 0.2.6...
[1/1] Extracting indexinfo-0.2.6: 0%/usr/local/lib/libpkg.so.3: Undefined symbol "utimensat"

@bapt

This comment has been minimized.

Show comment
Hide comment
@bapt

bapt Jan 14, 2017

Owner

1 this has nothing to do with indexinfo as pkg is complaining, second that means you are using packages built on FreeBSD 10.3 on a box which is probably 10.1 or 10.2 (which are not supported anymore (since January 1rst)). You need to upgrade to a supported version of freebsd or stop using freebsd packages mirror and build your own.

Owner

bapt commented Jan 14, 2017

1 this has nothing to do with indexinfo as pkg is complaining, second that means you are using packages built on FreeBSD 10.3 on a box which is probably 10.1 or 10.2 (which are not supported anymore (since January 1rst)). You need to upgrade to a supported version of freebsd or stop using freebsd packages mirror and build your own.

@bapt bapt closed this Jan 14, 2017

@rknetwork

This comment has been minimized.

Show comment
Hide comment
@rknetwork

rknetwork Jan 14, 2017

Could you provide a reference to the following statement?

using packages ..... 10.1 or 10.2 (which are not supported anymore (since January 1rst)

rknetwork commented Jan 14, 2017

Could you provide a reference to the following statement?

using packages ..... 10.1 or 10.2 (which are not supported anymore (since January 1rst)

@bapt

This comment has been minimized.

Show comment
Hide comment
@bapt

bapt Jan 14, 2017

Owner

freebsd builds official packages on the lowest supported version of a given branch meaning 10.1 until January 1rst, on January 1rst support was dropped for 10.1 and 10.2 meaning the packages are now built on 10.3 (which includes new symbols like openat, utimensat etc.)
see freebsd/pkg#1526

To check what versions of freebsd are supported: https://www.freebsd.org/security/

And the announcements: https://lists.freebsd.org/pipermail/freebsd-announce/2016-October/001754.html
https://lists.freebsd.org/pipermail/freebsd-announce/2017-January/001779.html

Owner

bapt commented Jan 14, 2017

freebsd builds official packages on the lowest supported version of a given branch meaning 10.1 until January 1rst, on January 1rst support was dropped for 10.1 and 10.2 meaning the packages are now built on 10.3 (which includes new symbols like openat, utimensat etc.)
see freebsd/pkg#1526

To check what versions of freebsd are supported: https://www.freebsd.org/security/

And the announcements: https://lists.freebsd.org/pipermail/freebsd-announce/2016-October/001754.html
https://lists.freebsd.org/pipermail/freebsd-announce/2017-January/001779.html

@rknetwork

This comment has been minimized.

Show comment
Hide comment
@rknetwork

rknetwork commented Jan 14, 2017

Thanks

@glaszig

This comment has been minimized.

Show comment
Hide comment
@glaszig

glaszig Feb 18, 2017

i just solved this without upgrading the entire OS by just using the proper FreeBSD repo url.

# freebsd-version
10.2-RELEASE-p10
# cat /usr/local/etc/pkg/repos/FreeBSD.conf
FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/release_2",
  enabled: yes
}

http://glasz.org/sheeplog/2017/02/freebsd-usrlocalliblibpkgso3-undefined-symbol-utimensat.html

glaszig commented Feb 18, 2017

i just solved this without upgrading the entire OS by just using the proper FreeBSD repo url.

# freebsd-version
10.2-RELEASE-p10
# cat /usr/local/etc/pkg/repos/FreeBSD.conf
FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/release_2",
  enabled: yes
}

http://glasz.org/sheeplog/2017/02/freebsd-usrlocalliblibpkgso3-undefined-symbol-utimensat.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment