Re: Some success; some problems with x11/nvidia-driver-460.39_1
On 07/02/2021 16:05, David Wolfskill wrote: > On those same laptops, however, I get panices running head (either > main-n244659-689561d40322 or main-n244663-f6e8256a965d). As I was > unable to get crash dumps, I took screenshots; they are available at > https://www.catwhisker.org/~david/FreeBSD/ports/nvidia-driver/head_panics/ The crash is because a part of extra-patch-src_nvidia-modeset_nvidia-modeset-freebsd.c needs to be applied even for 460.039, but now the patch file is applied only for earlier versions. The needed part modifies nvkms_alloc_ref_ptr function. I guess that the patch needs to be split in two. P.S. The maintainer is CC-ed. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox became much slower
On 01/11/2017 14:18, Stefan Esser wrote: > uMatrix has lots of pre-configured rules (blocks trackers and known > malware sites), but I'm using it in conjunction with uBlock from the > same developers. I used to use uBlock but at the time I got an impression that the addon itself ate away resources and slowed down my browser. What's your impression of it at this time? Thank you. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: py-backports.* conflict
[ping] On 18/05/2017 15:40, Andriy Gapon wrote: > > After the update of devel/py-backports.functools_lru_cache to 1.4 it started > to > conflict with devel/py-backports.shutil_get_terminal_size: > > py27-backports.functools_lru_cache-1.4 [FreeBSD] conflicts with > py27-backports.shutil_get_terminal_size-1.0.0 [installed] on > /usr/local/lib/python2.7/site-packages/backports/__init__.py > > It would be very inconvenient if only a single of py-backports.* ports could > be > installed at a time. > > Is it possible to fix the problem? > -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
py-backports.* conflict
After the update of devel/py-backports.functools_lru_cache to 1.4 it started to conflict with devel/py-backports.shutil_get_terminal_size: py27-backports.functools_lru_cache-1.4 [FreeBSD] conflicts with py27-backports.shutil_get_terminal_size-1.0.0 [installed] on /usr/local/lib/python2.7/site-packages/backports/__init__.py It would be very inconvenient if only a single of py-backports.* ports could be installed at a time. Is it possible to fix the problem? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pousdriere: "Failed ports: textproc/py-sphinx:build-depends"
On 01/04/2017 15:24, David Wolfskill wrote: > Usually, my poudriere runs are ... uneventful (which is a Good Thing). > > This morning, however, textproc/py-sphinx apparently had "an issue"; > that snowballed into 211 (out of 402) ports being skipped. > > Checking the log directory, I see no hints about textproc/py-sphinx; > here's what I do see, starting with an excerpt of the typescript from > the poudriere run: I experienced something like that a little while earlier. I think that it is related to the renaming of setuptools port (see UPDATING entry 20170316). Apparently poudriere doesn't handle it well. At least it didn't in my case. I did something like the following to resolve the issue: # poudriere bulk -C devel/py-setuptools27 # poudriere bulk -C devel/py-setuptools # poudriere bulk -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Thunderbird and UPDATING 20170302
FWIW, the following "hack" allowed me to keep my current profile and re-enabled
lightning in it.
First, I removed the addon before upgrading thunderbird. Not sure if this was a
requirement.
After upgrading thunderbird and mucking with it for some time I did the
following.
Shut down thunderbird.
Backed up ~/.thunderbird//prefs.js file.
Opened the file in editor.
Found lines with extensions.lastAppVersion and extensions.lastPlatformVersion,
and "downgraded" thunderbird version in them (changed 45.7.1 to 45.7.0).
Removed line with
extensions.installedDistroAddon.{e2fda1a4-762b-4020-b5ad-a41df1933103} in it.
Restarted thunderbird. And lightning was back.
Not sure if the above steps are sufficient. Perhaps something in what I
described as 'mucking' was required too.
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Thunderbird and UPDATING 20170302
On 02/03/2017 22:52, Andrea Venturoli wrote: > Hello. > > I read that "After changes in the packaging of the Lightning extension, > profiles > using this extension have to be re-created". > > Will this mean I should recreate the *Lightning* part of the profile (like > removing the calendars, upgrading, then adding them back again)? > Or does this mean I'll have to recreate the whole ThunderBird profile??? > > In the latter case, is there any workaround? > > I'm asking before upgrading, since I have a couple of profiles with a roughly > 70 > accounts in them (each with its own specific, non-standard, settings, with its > own set of subscriptions, etc...); recreating them would be a couple of > nightmares... I would like to second this question. If the upgrade means that I lose all my settings (including configurations for all email accounts and addons) and I have to re-create them from scratch, then that will hurt a lot. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: qt related pkg upgrade problem
On 22/02/2017 00:51, Jack L. wrote: > On Tue, Feb 21, 2017 at 2:12 PM, Andriy Gapon <a...@freebsd.org> wrote: >> >> I tried the following today with the latest FreeBSD packages >> (FreeBSD:12:amd64): >> >> # pkg upgrade >> ... >> Checking integrity... done (7 conflicting) >> - qtchooser-39 [FreeBSD] conflicts with qt4-linguisttools-4.8.7 [installed] >> on >> /usr/local/bin/lconvert >> ... >> Conflicts with the existing packages have been found. >> One more solver iteration is needed to resolve them. >> The following 178 package(s) will be affected (of 0 checked): >> ... >> Number of packages to be installed: 1 >> Number of packages to be upgraded: 107 >> Number of packages to be reinstalled: 56 >> The process will require 50 MiB more space. >> Proceed with this action? [y/N]: y >> [1/178] Installing qtchooser-39... >> pkg: qtchooser-39 conflicts with qt4-linguisttools-4.8.7 (installs files into >> the same place). Problematic file: /usr/local/bin/lconvert >> >> >> I thought that that "one more solver iteration" resolved this. >> Shouldn't pkg first upgrade or remove the installed conflicting packages >> before >> trying to install qtchooser? >> I read UPDATING, it mentioned the big Qt change, but it didn't have any >> special >> upgrade instructions... >> >> How can I proceed from here? >> Thank you! > > > I just uninstalled qt4-linguisttools-4.8.7 and that fixed the issue > I event didn't have to do that... It's magic - I ran pkg upgrade again and it did the right thing this time: Proceed with this action? [y/N]: y [1/176] Deinstalling qt4-xmlpatterns-tool-4.8.7... [1/176] Deleting files for qt4-xmlpatterns-tool-4.8.7: 100% [2/176] Deinstalling qt4-rcc-4.8.7... [2/176] Deleting files for qt4-rcc-4.8.7: 100% [3/176] Deinstalling qt4-qdbusviewer-4.8.7... [3/176] Deleting files for qt4-qdbusviewer-4.8.7: 100% [4/176] Deinstalling qt4-pixeltool-4.8.7... [4/176] Deleting files for qt4-pixeltool-4.8.7: 100% [5/176] Deinstalling qt4-linguisttools-4.8.7... [5/176] Deleting files for qt4-linguisttools-4.8.7: 100% [6/176] Deinstalling qt4-help-tools-4.8.7... [6/176] Deleting files for qt4-help-tools-4.8.7: 100% [7/176] Deinstalling qt4-dbus-4.8.7... [7/176] Deleting files for qt4-dbus-4.8.7: 100% [8/176] Installing qtchooser-39... [8/176] Extracting qtchooser-39: 100% ... It seems like even when pkg doesn't upgrade any packages it still does something. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
qt related pkg upgrade problem
I tried the following today with the latest FreeBSD packages (FreeBSD:12:amd64): # pkg upgrade ... Checking integrity... done (7 conflicting) - qtchooser-39 [FreeBSD] conflicts with qt4-linguisttools-4.8.7 [installed] on /usr/local/bin/lconvert ... Conflicts with the existing packages have been found. One more solver iteration is needed to resolve them. The following 178 package(s) will be affected (of 0 checked): ... Number of packages to be installed: 1 Number of packages to be upgraded: 107 Number of packages to be reinstalled: 56 The process will require 50 MiB more space. Proceed with this action? [y/N]: y [1/178] Installing qtchooser-39... pkg: qtchooser-39 conflicts with qt4-linguisttools-4.8.7 (installs files into the same place). Problematic file: /usr/local/bin/lconvert I thought that that "one more solver iteration" resolved this. Shouldn't pkg first upgrade or remove the installed conflicting packages before trying to install qtchooser? I read UPDATING, it mentioned the big Qt change, but it didn't have any special upgrade instructions... How can I proceed from here? Thank you! -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: radeon GL woes
On 18/02/2017 21:15, Russell L. Carter wrote: > So I've run into the radeon problem on xorg upgrade, running > mpv gives the > > libGL error: Version 7 or imageFromFds image extension not found > libGL error: failed to load driver: r600 > > error. I've been told that this is benign error and the r600 driver actually works. This is somehow related to DRI3 not being supported, but I don't know details. freebsd-x11@ could be a better list for this question. > Adding /usr/local/etc/X11/xorg.conf.d/dri.conf: > > Section "Device" > Identifier "Radeon" > Driver "radeon" > Option "DRI" "2" > EndSection > > has no effect. Nor does setting Option "DRI" "3" > > I am running without an xorg file, it has up till now > run great. > > I've reinstalled everything that I can think of, I build > via poudriere, and I got rid of the llvm37 and llvm38 that > were lurking on this system. > > Any ideas? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox build broken
On 09/02/2017 16:17, Dimitry Andric wrote: > On 9 Feb 2017, at 14:03, Domagoj Stolfa <domagoj.sto...@gmail.com> wrote: >> >> It would seem that the firefox build is broken on 12.0-CURRENT. I've been >> getting the same error as seem on [1]. Has anyone else experienced this? >> >> [1] >> https://lists.freebsd.org/pipermail/freebsd-pkg-fallout/Week-of-Mon-20170206/408053.html > > It's a problem in the DTRACE option. See https://bugs.freebsd.org/216871 . > > For now, if you don't need DTrace support, just turn it off. Can this be done by default? So, that the binary packages for "FreeBSD 12" can be built. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ATI, libdrm, gnome
On 15/01/2017 15:40, Danilo G. Baio (dbaio) wrote: > On Sun, Jan 15, 2017 at 01:13:41PM +0200, Andriy Gapon wrote: >> On 15/01/2017 00:42, Baptiste Daroussin wrote: >>> If you know how to use svn and are actually using svn for the ports tree >>> can you >>> try reverting the radeon upgrade (only that) (same with git :))? >>> >> >> I can confirm a similar kind of problem with KDE 4 after upgrading to the >> latest >> packages. I downgraded xf86-video-ati to the previous version that I had >> (7.5.0) and the problem is gone. >> >> More details. I see the KDM login screen, I can log in, > > Almost the same with SLIM, after login, shows up a black screen. > >> I see the KDE splash >> screen and its gets updated with the startup progress. But in the end the >> splash stays on and I never see the actual desktop. I can verify with ps >> that >> all programs that should start are running and I do not see anything unusual >> in >> their state. So, it feels like the screen is just not being updated after a >> certain stage. > > I noticed that dbus is not being running after update. > pkg: dbus upgraded: 1.8.20 -> 1.10.14 > > Starting dbus. > Failed to start message bus: Could not get UID and GID for username > "messagebus" > > Box with FreeBSD 11 amd64 and quarterly packages. I don't have that problem... dbus-1.10.14_1 $ service dbus status dbus is running as pid 1588. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ATI, libdrm, gnome
On 15/01/2017 00:42, Baptiste Daroussin wrote: > If you know how to use svn and are actually using svn for the ports tree can > you > try reverting the radeon upgrade (only that) (same with git :))? > I can confirm a similar kind of problem with KDE 4 after upgrading to the latest packages. I downgraded xf86-video-ati to the previous version that I had (7.5.0) and the problem is gone. More details. I see the KDM login screen, I can log in, I see the KDE splash screen and its gets updated with the startup progress. But in the end the splash stays on and I never see the actual desktop. I can verify with ps that all programs that should start are running and I do not see anything unusual in their state. So, it feels like the screen is just not being updated after a certain stage. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: openldap-client vs openldap-sasl-client (Miroslav Lachman)
On 11/01/2017 03:27, Miroslav Lachman wrote: > It should be fixed now in the ports tree. I don't know when new packages will > be > available for pkg install / pkg upgrade. > > https://svnweb.freebsd.org/ports?view=revision=431079 Good news! Thanks for the fix. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
openldap-client vs openldap-sasl-client
Do you I understand correctly that it is impossible now to install both samba44 and libreoffice using the official FreeBSD package repository? Or samba44 and KDE? If yes, then that sucks... -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
install header files required for development with libzfs_core
JFYI. I bumped __FreeBSD_version to 1200013 to mark this change.
Forwarded Message
Subject: svn commit: r307131 - head/include
Date: Wed, 12 Oct 2016 07:08:32 + (UTC)
From: Andriy Gapon <a...@freebsd.org>
To: src-committ...@freebsd.org, svn-src-...@freebsd.org,
svn-src-h...@freebsd.org
Author: avg
Date: Wed Oct 12 07:08:32 2016
New Revision: 307131
URL: https://svnweb.freebsd.org/changeset/base/307131
Log:
install header files required development with libzfs_core
libzfs_core provides a rather limited but committed (stable) interface
for working with ZFS. We install libzfs_core shared library but we do
not install header files required for developing programs that use
the library. This change is to install the required header files
libzfs_core.h, libnvpair.h and sys/nvpair.h.
The headers are installed into the same locations as on illumos.
Reviewed by:mav, markj
Differential Revision: https://reviews.freebsd.org/D8005
Modified:
head/include/Makefile
Modified: head/include/Makefile
==
--- head/include/Makefile Wed Oct 12 06:58:01 2016(r307130)
+++ head/include/Makefile Wed Oct 12 07:08:32 2016(r307131)
@@ -237,6 +237,17 @@ copies: .PHONY .META
cd ${.CURDIR}/../sys/teken; \
${INSTALL} -C ${TAG_ARGS} -o ${BINOWN} -g ${BINGRP} -m 444 teken.h \
${DESTDIR}${INCLUDEDIR}/teken
+.if ${MK_CDDL} != "no"
+ cd ${.CURDIR}/../cddl/contrib/opensolaris/lib/libzfs_core/common; \
+ ${INSTALL} -C ${TAG_ARGS} -o ${BINOWN} -g ${BINGRP} -m 444
libzfs_core.h \
+ ${DESTDIR}${INCLUDEDIR}
+ cd ${.CURDIR}/../cddl/contrib/opensolaris/lib/libnvpair; \
+ ${INSTALL} -C ${TAG_ARGS} -o ${BINOWN} -g ${BINGRP} -m 444 libnvpair.h \
+ ${DESTDIR}${INCLUDEDIR}
+ cd ${.CURDIR}/../sys/cddl/contrib/opensolaris/uts/common/sys; \
+ ${INSTALL} -C ${TAG_ARGS} -o ${BINOWN} -g ${BINGRP} -m 444 nvpair.h \
+ ${DESTDIR}${INCLUDEDIR}/sys
+.endif
symlinks: .PHONY .META
@${ECHO} "Setting up symlinks to kernel source tree..."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gnu screen incompatibility?
On 08/07/2016 09:50, Greg Rivers wrote: > On Friday, July 08, 2016 09:43:17 Andriy Gapon wrote: >> It seems that screen 4.4.0_1 can not connect to sessions started with >> the previous version 4.3.x. At least that was the case for me. >> > I noticed that too, but: > > $ pkg info -D screen > screen-4.4.0_1: > Always: > = > > As of GNU Screen 4.4.0: > > Note that there was fix to screen message structure field > responsible for $TERM handling, making it impossible > to attach to older versions. > > = Oh, I overlooked this... I checked UPDATING and there was nothing related in it. It would be nice to get this kind of a message before a package is actually upgraded, not after, as happens with pkg. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
gnu screen incompatibility?
It seems that screen 4.4.0_1 can not connect to sessions started with the previous version 4.3.x. At least that was the case for me. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
patch for smartmontools on latest head
http://dpaste.com/1B04AVB I believe that this patch should do the right thing on all version of FreeBSD, so it could be better to integrate it upstream, if possible. Without the patch the port fails with errors like: ./freebsd_nvme_ioctl.h:34:8: error: redefinition of 'nvme_command' -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: thunderbird-45.1.1 change "Retention policy" not effect
On 08/06/2016 10:56, Sam Fourman Jr. wrote: > Confirmed > > Sam Fourman Jr. > > On Wed, Jun 8, 2016 at 12:26 AM, Alex V. Petrov <alexvpet...@gmail.com> > wrote: > >> Properties folder - tab "Retention policy" - in any case button "OK" >> doing nothing. Please report to thunderbird developers (mozilla?). -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: minor(?) problem with pkg crashing
On 20/04/2016 17:36, Baptiste Daroussin wrote: > On Wed, Apr 20, 2016 at 03:30:08PM +0300, Andriy Gapon wrote: >> On 20/04/2016 11:39, Baptiste Daroussin wrote: >>> On Wed, Apr 20, 2016 at 11:27:22AM +0300, Andriy Gapon wrote: >>>> pkg 1.7.2 crashed at the end of upgrade run, after completing all the >>>> upgrades. >>>> Unfortunately no debug symbols, but it looks like a double free or >>>> something >>>> like that, seems that this happens only if >>>>> Conflicts with the existing packages have been found. >>>>> One more solver iteration is needed to resolve them. >>>> >>>> The crash is in pkg_jobs_free() -> pkg_free() -> free() >>>> >>> Did it happen only once, or is it a reproducible case for you? >> >> Reproducible. >> > Do you have a core file? Yes, but pkg / libpkg is without debug symbols. E.g.: Core was generated by `pkg'. Program terminated with signal SIGBUS, Bus error. #0 __je_bitmap_unset (bitmap=, binfo=, bit=) at /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/internal/bitmap.h:248 warning: Source file is more recent than executable. 248 *gp = g; (gdb) bt #0 __je_bitmap_unset (bitmap=, binfo=, bit=) at /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/internal/bitmap.h:248 #1 arena_run_reg_dalloc (run=, ptr=) at jemalloc_arena.c:342 #2 arena_dalloc_bin_locked_impl (arena=, chunk=, ptr=, bitselm=, junked=) at jemalloc_arena.c:2732 #3 0x0008024ad4f1 in __je_tcache_bin_flush_small (tsd=, tcache=, tbin=, binind=, rem=) at jemalloc_tcache.c:132 #4 0x0008024d1230 in __je_tcache_dalloc_small (tsd=0x134c4992d87fd, tcache=, ptr=, binind=2, slow_path=false) at /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/internal/tcache.h:417 #5 __je_arena_dalloc (ptr=, tcache=, slow_path=false, tsd=) at /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/internal/arena.h:1370 #6 __je_idalloctm (is_metadata=false, slow_path=false, tsd=, ptr=, tcache=) at /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/internal/jemalloc_internal.h:1056 #7 __je_iqalloc (tsd=, ptr=, tcache=, slow_path=) at /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/internal/jemalloc_internal.h:1080 #8 ifree (tsd=, ptr=, tcache=, slow_path=) at jemalloc_jemalloc.c:1823 #9 0x0008024d161e in __free (ptr=0x80376b9e0) at jemalloc_jemalloc.c:1928 #10 0x00080086ffa1 in ?? () from /usr/local/lib/libpkg.so.3 #11 0x0008008608fa in ?? () from /usr/local/lib/libpkg.so.3 #12 0x00080086055d in pkg_free () from /usr/local/lib/libpkg.so.3 #13 0x00080088a7ee in ?? () from /usr/local/lib/libpkg.so.3 #14 0x00080087c97e in pkg_jobs_free () from /usr/local/lib/libpkg.so.3 #15 0x004163f3 in ?? () #16 0x0040fc1d in ?? () #17 0x004064bf in ?? () #18 0x00080064a000 in ?? () #19 0x in ?? () -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xchat vs freenode
On 20/04/2016 14:49, Matthew Seaman wrote: > On 04/20/16 12:15, Andriy Gapon wrote: >> >> It seems that most of FreeNode servers now reject SSLv3. >> They simply reset a TCP connection after Client Hello message with that >> protocol. xchat appears to be hardcoded to use SSLv3, so it now has a >> trouble >> connecting to the FreeNode servers with SSL enabled. >> >> Here are some bug reports describing the problem for Linux distributions: >> https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1381484 >> https://bugzilla.redhat.com/show_bug.cgi?id=1091544 >> >> This patch seems to fix the issue for me: >> https://bugzilla.redhat.com/attachment.cgi?id=889894=diff >> > > Bernard Spil has a whole raft of patches for these sort of bugs > available from https://wiki.freebsd.org/OpenSSL/No-SSLv3 > > I've been using his patch to irc/xchat happily for several months. That's a very good job and a resource. Thank you and Bernard. I hope that xchat's collective maintainer will include the patch into the port. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: minor(?) problem with pkg crashing
On 20/04/2016 11:39, Baptiste Daroussin wrote: > On Wed, Apr 20, 2016 at 11:27:22AM +0300, Andriy Gapon wrote: >> pkg 1.7.2 crashed at the end of upgrade run, after completing all the >> upgrades. >> Unfortunately no debug symbols, but it looks like a double free or something >> like that, seems that this happens only if >>> Conflicts with the existing packages have been found. >>> One more solver iteration is needed to resolve them. >> >> The crash is in pkg_jobs_free() -> pkg_free() -> free() >> > Did it happen only once, or is it a reproducible case for you? Reproducible. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
xchat vs freenode
It seems that most of FreeNode servers now reject SSLv3. They simply reset a TCP connection after Client Hello message with that protocol. xchat appears to be hardcoded to use SSLv3, so it now has a trouble connecting to the FreeNode servers with SSL enabled. Here are some bug reports describing the problem for Linux distributions: https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1381484 https://bugzilla.redhat.com/show_bug.cgi?id=1091544 This patch seems to fix the issue for me: https://bugzilla.redhat.com/attachment.cgi?id=889894=diff -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
minor(?) problem with pkg crashing
pkg 1.7.2 crashed at the end of upgrade run, after completing all the upgrades. Unfortunately no debug symbols, but it looks like a double free or something like that, seems that this happens only if > Conflicts with the existing packages have been found. > One more solver iteration is needed to resolve them. The crash is in pkg_jobs_free() -> pkg_free() -> free() -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: 'porting' AMD compiler suite
On 14/04/2016 05:38, William A. Mahaffey III wrote: > All seems OK w/ the system headers (I know, shocking ), the required files > defining a '__uintptr_t' are in fact unconditionally included, so it must be > something else (bad defines somewhere, or ). I am still chasing Apologies, but are you serious?.. $ fgrep -r __uintptr_t /usr/include/ ... /usr/include/x86/_types.h:typedef __uint64_t __uintptr_t; /usr/include/x86/_types.h:typedef __uint32_t __uintptr_t; ... This is on an amd64 head system. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
kodi vs samba
Mickaël, could you please change kodi's samba dependency from samba-nmblookup to samba36? The difference between those packages is not that big size-wise, but the current dependency is a headache for those who want to use both kodi and samba on the same machine. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
hplip-plugin
Does anyone have an HP USB-connected printer that *requires* hplip-plugin working after updating to the latest version? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg vs hplip
On 17/03/2016 21:41, Andriy Gapon wrote: > > I am trying to upgrade to the latest official packages and I am getting the > following: > > $ pkg upgrade > ... > Installed packages to be UPGRADED: > ... > hplip-plugin: 3.14.10 -> 3.16.2 [poudriere] > hplip: 3.14.10_1 -> 3.16.2_1 [FreeBSD] > gutenprint-ijs: 5.2.10_1 -> 5.2.10_2 [FreeBSD] > gutenprint-cups: 5.2.10_1 -> 5.2.10_2 [FreeBSD] > gutenprint-base: 5.2.10_1 -> 5.2.10_2 [FreeBSD] > gtk3: 3.18.8 -> 3.18.8_1 [FreeBSD] > gtk2: 2.24.29 -> 2.24.29_1 [FreeBSD] > giflib: 5.1.2_1 -> 5.1.2_2 [FreeBSD] > ghostscript9-base: 9.06_11 -> 9.06_12 [FreeBSD] > gdb: 7.10_5 -> 7.11 [poudriere] > foomatic-filters: 4.0.17_5 -> 4.0.17_6 [FreeBSD] > firefox: 45.0_1,1 -> 45.0_3,1 [FreeBSD] > epdfview: 0.1.8_10 -> 0.1.8_11 [FreeBSD] > eclipse: 4.5.1 -> 4.5.2 [FreeBSD] > cups-filters: 1.8.2 -> 1.8.2_2 [FreeBSD] > cups: 2.0.3_1 -> 2.1.3_1 [FreeBSD] > ... > The process will require 90 MiB more space. > 379 MiB to be downloaded. > > Proceed with this action? [y/N]: y > ... > Fetching py27-attrs-15.2.0.txz: 100% 18 KiB 18.1kB/s00:01 > Checking integrity... done (16 conflicting) > pkg: Cannot solve problem using SAT solver: > require rule: package hplip(r) depends on a requirement provided by: > net-snmp(l)net-snmp(l)net-snmp(l) > require rule: package hplip(r) depends on a requirement provided by: > cups-image(l)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r) > require rule: package hplip(r) depends on a requirement provided by: > cups-client(l)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r) > require rule: package hplip(r) depends on a requirement provided by: > sane-backends(l)epkowa(r)sane-backends(l)sane-backends(l) > require rule: package hplip(r) depends on a requirement provided by: > dbus(l)dbus(l)dbus(l) > require rule: package hplip(r) depends on a requirement provided by: > jpeg-turbo(l)mozjpeg(r)jpeg(r)jpeg-turbo(l)jpeg-turbo(l) > upgrade rule: upgrade local hplip-3.16.2_1 to remote hplip-3.16.2_1 > upgrade rule: upgrade local hplip-3.16.2_1 to remote hplip-3.16.2_1 > upgrade rule: upgrade local hplip-3.14.10_1 to remote hplip-3.16.2_1 > cannot install package hplip, remove it from request? [Y/n]: > I can not figure out what the problem is here. Followup: I answered Y and kept answering Y when I was prompted 3 more times, but after that some magic happened and pkg announced that it is going to do the following: Installed packages to be REMOVED: foomatic-filters-4.0.17_5 cups-client-2.0.3_2 cups-image-2.0.3_2 cups-base-2.0.3_5 cups-pstoraster-8.15.4_8 New packages to be INSTALLED: py27-attrs: 15.2.0 [FreeBSD] Installed packages to be UPGRADED: qpdf: 5.1.2_1 -> 5.1.2_2 [FreeBSD] ghostscript9-base: 9.06_11 -> 9.06_12 [FreeBSD] cups: 2.0.3_1 -> 2.1.3_1 [FreeBSD] cups-filters: 1.8.2 -> 1.8.2_2 [FreeBSD] ... hplip: 3.14.10_1 -> 3.16.2_1 [FreeBSD] ... hplip-plugin: 3.14.10 -> 3.16.2 [poudriere] ... This seems to be correct. > Please note that I use a multi-repository configuration: the official > repository > for most packages and a local, poudriere-built one for some packages including > hplip-plugin. > > Any help would be appreciated! > -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
pkg vs hplip
I am trying to upgrade to the latest official packages and I am getting the following: $ pkg upgrade ... Installed packages to be UPGRADED: ... hplip-plugin: 3.14.10 -> 3.16.2 [poudriere] hplip: 3.14.10_1 -> 3.16.2_1 [FreeBSD] gutenprint-ijs: 5.2.10_1 -> 5.2.10_2 [FreeBSD] gutenprint-cups: 5.2.10_1 -> 5.2.10_2 [FreeBSD] gutenprint-base: 5.2.10_1 -> 5.2.10_2 [FreeBSD] gtk3: 3.18.8 -> 3.18.8_1 [FreeBSD] gtk2: 2.24.29 -> 2.24.29_1 [FreeBSD] giflib: 5.1.2_1 -> 5.1.2_2 [FreeBSD] ghostscript9-base: 9.06_11 -> 9.06_12 [FreeBSD] gdb: 7.10_5 -> 7.11 [poudriere] foomatic-filters: 4.0.17_5 -> 4.0.17_6 [FreeBSD] firefox: 45.0_1,1 -> 45.0_3,1 [FreeBSD] epdfview: 0.1.8_10 -> 0.1.8_11 [FreeBSD] eclipse: 4.5.1 -> 4.5.2 [FreeBSD] cups-filters: 1.8.2 -> 1.8.2_2 [FreeBSD] cups: 2.0.3_1 -> 2.1.3_1 [FreeBSD] ... The process will require 90 MiB more space. 379 MiB to be downloaded. Proceed with this action? [y/N]: y ... Fetching py27-attrs-15.2.0.txz: 100% 18 KiB 18.1kB/s00:01 Checking integrity... done (16 conflicting) pkg: Cannot solve problem using SAT solver: require rule: package hplip(r) depends on a requirement provided by: net-snmp(l)net-snmp(l)net-snmp(l) require rule: package hplip(r) depends on a requirement provided by: cups-image(l)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r) require rule: package hplip(r) depends on a requirement provided by: cups-client(l)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r)cups(r) require rule: package hplip(r) depends on a requirement provided by: sane-backends(l)epkowa(r)sane-backends(l)sane-backends(l) require rule: package hplip(r) depends on a requirement provided by: dbus(l)dbus(l)dbus(l) require rule: package hplip(r) depends on a requirement provided by: jpeg-turbo(l)mozjpeg(r)jpeg(r)jpeg-turbo(l)jpeg-turbo(l) upgrade rule: upgrade local hplip-3.16.2_1 to remote hplip-3.16.2_1 upgrade rule: upgrade local hplip-3.16.2_1 to remote hplip-3.16.2_1 upgrade rule: upgrade local hplip-3.14.10_1 to remote hplip-3.16.2_1 cannot install package hplip, remove it from request? [Y/n]: I can not figure out what the problem is here. Please note that I use a multi-repository configuration: the official repository for most packages and a local, poudriere-built one for some packages including hplip-plugin. Any help would be appreciated! -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: unexpected package dependency
On 19/02/2016 03:55, Perry Hutchison wrote: > Andriy Gapon <a...@freebsd.org> wrote: >> On 17/02/2016 11:28, Perry Hutchison wrote: >>> I had not expected to find gcc listed (in packagesite.yaml) as a >>> dependency of the sysutils/cpuburn package. I can understand a >>> _port_ needing gcc (at build time), but does the cpuburn _package_ >>> actually require gcc at _runtime_? >> >> I don't believe so. AFAIR, it builds static binaries. > > So would the inclusion of gcc in the "deps" for sysutils/cpuburn (in > packagesite.yaml) be caused by a problem with the way the dependencies > are specified in the port, or with the way they are handled by the > package-generation mechanism? (I'm trying to figure out which to file > a PR against -- and I'm not all that familiar with pkgng details.) > My recollection is that the ports infrastructure does not allow to specify whether a non-base compiler (like GCC for FreeBSD 11) is required only as a compiler (that is, only during the build time) or if its run-time is required as well. The latter is always assumed. But I could be mistaken. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: unexpected package dependency
On 17/02/2016 11:28, Perry Hutchison wrote: > I had not expected to find gcc listed (in packagesite.yaml) as a > dependency of the sysutils/cpuburn package. I can understand a > _port_ needing gcc (at build time), but does the cpuburn _package_ > actually require gcc at _runtime_? > I don't believe so. AFAIR, it builds static binaries. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: skype4 on -current: error while loading shared libraries: libpulse-mainloop-glib.so.0
On 14/08/2015 02:40, Anton Shterenlikht wrote:
> Anybody else is seeing this?
>
> $ skype
> /usr/local/share/skype/skype: error while loading shared libraries:
> libpulse-mainloop-glib.so.0: cannot open shared object file: No such file or
> directory
>
> $ pkg info -xl pulse | grep mainloop-glib.so
> /usr/local/lib/libpulse-mainloop-glib.so
> /usr/local/lib/libpulse-mainloop-glib.so.0
> /usr/local/lib/libpulse-mainloop-glib.so.0.0.5
>
It's several months since Anton asked this question and now I have to ask
exactly the same one.
I've built net-im/skype4 without VIDEO option using poudriere and installed it
like this:
$ pkg install net-im/skype4
[snip]
New packages to be INSTALLED:
skype4: 4.3.0.37,1 [poudriere]
linux-c6-qt47-x11: 4.7.2_1 [FreeBSD]
linux-c6-alsa-lib: 1.0.22_2 [poudriere]
linux-c6-qt47: 4.7.2_1 [FreeBSD]
linux-c6-hicolor-icon-theme: 0.5_3 [poudriere]
linux-c6-dbus-libs: 1.2.24_4 [poudriere]
linux-c6-dri: 10.1_1 [poudriere]
linux-c6-qt47-webkit: 4.7.2_1 [FreeBSD]
linux-skype_oss_wrapper: 0.1.1 [FreeBSD]
[snip]
Running skype results in:
$ skype
/usr/local/share/skype/skype: error while loading shared libraries:
libpulse-mainloop-glib.so.0: cannot open shared object file: No such file or
directory
ldd produces this:
$ env LD_LIBRARY_PATH=/lib/skype_oss_wrapper:${LD_LIBRARY_PATH}
/compat/linux/bin/bash /compat/linux/usr/bin/ldd /usr/local/share/skype/skype |
fgrep pulse
/usr/local/share/skype/skype: /lib/skype_oss_wrapper/libpulse.so.0: no version
information available (required by /usr/lib/qt47/libphonon.so.4)
libpulse-mainloop-glib.so.0 => not found
libpulse.so.0 => /lib/skype_oss_wrapper/libpulse.so.0 (0x249c9000)
libpulse-mainloop-glib.so.0 => not found
With a little bit of help from Google I found this thread and in particular the
following post: http://article.gmane.org/gmane.os.freebsd.devel.ports/127782
In the end I had to do a slightly different thing:
$ pkg install linux-c6-pulseaudio-libs
$ cd /compat/linux
$ rpm2archive < ~/tmp/pulseaudio-libs-glib2-0.9.21-21.el6.i686.rpm| tar xvf -
x ./usr/lib/libpulse-mainloop-glib.so.0
x ./usr/lib/libpulse-mainloop-glib.so.0.0.4
Where pulseaudio-libs-glib2-0.9.21-21.el6.i686.rpm was downloaded from the
Internet in advance.
After this skype seems to finally work, but it would be nice if I hadn't to do
the extra steps. Maybe I did something wrong before installing skype?
BTW, it seems that libpulse-mainloop-glib.so.0 dependency comes from
/compat/linux/usr/lib/qt47/libphonon.so.4.
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
tmate
Has anyone tried to port tmate yet? http://tmate.io/ -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg install kodi does not like samba
On 26/05/2015 21:36, Timur I. Bakeyev wrote: Well, it's all said in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177786. I've added samba36-nmblookup as a courtesy for the xmbc/kodi project while ago so it's not depend on full samba package, but now it's going too far in the request to drop nmblookup from samba36 itself.. The real solution(are we done with GSOC projects for this year already?) would be ability to build multiple packages out of one port, since we already have stagedir. So, only one extra step is required, similar the way it's done in Debian. Timur, thank you for the information! It probably makes sense to just drop samba-nmblookup unless someone provides a better fix. I think that the support for multiple packages from the same work could take a while to materialize. Meanwhile, does anybody know if there is any way to coerce pkg into accepting samba36 as a dependency instead of samba36-nmblookup? On Tue, May 26, 2015 at 7:38 PM, Andriy Gapon a...@freebsd.org mailto:a...@freebsd.org wrote: Not sure if this is a problem with multimedia/kodi port or if it is with pkg or both: $ pkg install kodi 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 integrity... done (1 conflicting) Checking integrity... done (0 conflicting) The following 13 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: samba36-3.6.25 New packages to be INSTALLED: kodi: 14.2 [FreeBSD] tinyxml: 2.6.2_1 [FreeBSD] samba36-nmblookup: 3.6.25 [FreeBSD] libnfs: 1.3.0_1 [FreeBSD] libcec: 2.2.0 [FreeBSD] libbluray: 0.7.0,1 [FreeBSD] libbdplus: 0.1.2 [FreeBSD] libaacs: 0.8.0 [FreeBSD] libass: 0.12.1 [FreeBSD] sdl2: 2.0.3_4 [FreeBSD] shairplay: 0.9.0.20140422 [FreeBSD] lzo2: 2.09 [FreeBSD] So, pkg wants to replace samba36 with samba36-nmblookup. I think that those packages conflict because samba36 provides a superset of what samba36-nmblookup provides. So, there should be no reason to not just use samba36. Finally, why do we need net/samba-nmblookup at all? Seems like kodi is its only user and it is not a light-weight port already. -- Andriy Gapon -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
pkg install kodi does not like samba
Not sure if this is a problem with multimedia/kodi port or if it is with pkg or both: $ pkg install kodi 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 integrity... done (1 conflicting) Checking integrity... done (0 conflicting) The following 13 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: samba36-3.6.25 New packages to be INSTALLED: kodi: 14.2 [FreeBSD] tinyxml: 2.6.2_1 [FreeBSD] samba36-nmblookup: 3.6.25 [FreeBSD] libnfs: 1.3.0_1 [FreeBSD] libcec: 2.2.0 [FreeBSD] libbluray: 0.7.0,1 [FreeBSD] libbdplus: 0.1.2 [FreeBSD] libaacs: 0.8.0 [FreeBSD] libass: 0.12.1 [FreeBSD] sdl2: 2.0.3_4 [FreeBSD] shairplay: 0.9.0.20140422 [FreeBSD] lzo2: 2.09 [FreeBSD] So, pkg wants to replace samba36 with samba36-nmblookup. I think that those packages conflict because samba36 provides a superset of what samba36-nmblookup provides. So, there should be no reason to not just use samba36. Finally, why do we need net/samba-nmblookup at all? Seems like kodi is its only user and it is not a light-weight port already. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg 1.5.1 wants to remove locked packages
On 13/05/2015 18:54, Baptiste Daroussin wrote: On Wed, May 13, 2015 at 03:45:58PM +, Henry Hu wrote: On Wed, May 13, 2015 at 2:18 PM Andriy Gapon a...@freebsd.org wrote: I can also confirm this problem. Although in my case the packages are not locked still it's not nice for pkg to remove them: $ pkg upgrade ... All repositories are up-to-date. Checking for upgrades (946 candidates): 100% Processing candidates (946 candidates): 100% The following 705 package(s) will be affected (of 0 checked): [*] Installed packages to be REMOVED: libreoffice-4.3.5_2 digikam-3.5.0_6,2 kipi-plugin-calendar-3.5.0_3 kipi-plugins-3.5.0_3,1 Using pkg search, you can see that these packages are not present in the repo currently. Maybe pkg finds that it can't find updated version so it can only remove them? yes but only because one of their dependencies is being updated as well and might break those ports after the upgrade Once the package building is done again those packages will appear again in the repo and the problem will be gone. Thank you for the information. pkg's behavior makes much more sense now. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg 1.5.1 wants to remove locked packages
I can also confirm this problem. Although in my case the packages are not locked still it's not nice for pkg to remove them: $ pkg upgrade ... All repositories are up-to-date. Checking for upgrades (946 candidates): 100% Processing candidates (946 candidates): 100% The following 705 package(s) will be affected (of 0 checked): [*] Installed packages to be REMOVED: libreoffice-4.3.5_2 digikam-3.5.0_6,2 kipi-plugin-calendar-3.5.0_3 kipi-plugins-3.5.0_3,1 New packages to be INSTALLED: ... I mean I can reinstall libreoffice, digikam and others after pkg is done, but I shouldn't have to do that. If the solver sees a need to remove some packages it should take care to install them back. [*] Unrelated: 705 out of 0 looks confusing. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg upgrade gives: Assertion failed
On 18/12/2014 00:49, Dan Langille wrote: I am installing from my own repo onto FreeBSD 9.3 with pkg 1.4.0 $ sudo pkg upgrade -f Have you just switched from pkg 1.3.x? If yes, please try pkg update -f before pkg upgrade. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg upgrade gives: Assertion failed
On 18/12/2014 01:19, Dan Langille wrote: On Dec 17, 2014, at 6:06 PM, Andriy Gapon a...@freebsd.org wrote: On 18/12/2014 00:49, Dan Langille wrote: I am installing from my own repo onto FreeBSD 9.3 with pkg 1.4.0 $ sudo pkg upgrade -f Have you just switched from pkg 1.3.x? yes. If yes, please try pkg update -f before pkg upgrade. Hmmm, I usually do that every time. But, success. Thank you. Next time you see me, tell me this story and that I owe you a beer. ;) Cool :) Although, I promise to pass that beer to anyone who can fix this problem :) Really, the pkg update -f step should not be required in this situation. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
libgstreamer-0.10.so.0: Undefined symbol ppoll
I have a program linked to libgstreamer and after upgrading to the latest official packages (gstreamer-0.10.36_2) the program does not run anymore: /usr/local/lib/libgstreamer-0.10.so.0: Undefined symbol ppoll Indeed: $ nm -D /usr/local/lib/libgstreamer-0.10.so.0 | fgrep ppoll U ppoll I wonder what package provides a library that provides the required ppoll on FreeBSD. Thank you! -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: libgstreamer-0.10.so.0: Undefined symbol ppoll
On 14/12/2014 10:36, Konstantin Belousov wrote: On Sun, Dec 14, 2014 at 10:17:16AM +0200, Andriy Gapon wrote: I have a program linked to libgstreamer and after upgrading to the latest official packages (gstreamer-0.10.36_2) the program does not run anymore: /usr/local/lib/libgstreamer-0.10.so.0: Undefined symbol ppoll Indeed: $ nm -D /usr/local/lib/libgstreamer-0.10.so.0 | fgrep ppoll U ppoll I wonder what package provides a library that provides the required ppoll on FreeBSD. The symbol is provided by libc.so.7. What is your branch, and how old is your world ? Thank you for the quick answer! This is head, r273579, almost two months old. I guess I need to catch up. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
editors/vim: /usr/local/share/vim/vimrc
It seems that the latest official vim package now installs /usr/local/share/vim/vimrc file with non-trivial content and that vim actually honors that file. That results in significant changes in vim's behavior comparing to the previous version. POLA? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
mail/thunderbird: ENIGMAIL LIGHTNING are now off by default
I've just upgraded my packages to the latest available from the FreeBSD official repository and thunderbird does not have Enigmail and Lightning. Hmm. Looks like www/firefox/Makefile.options overrides OPTIONS_DEFAULT from mail/thunderbird/Makefile -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg 1.4 freeze please test test test!
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-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: latest freebsd:11:x86:64 repo and ruby 1.9 - 2.0
On 20/10/2014 00:43, Craig Rodrigues wrote: On Sat, Oct 18, 2014 at 2:29 AM, Andriy Gapon a...@freebsd.org mailto:a...@freebsd.org wrote: Then the real problem, I do not want these packages to be removed except for ruby-1.9.3.547_3,1. In other words, I want to keep using zfs-snapshot-mgmt, libchk, hub and porttools. What should I do? Did you try to pkg lock the packages that you don't want removed? No, I didn't it. Previously I didn't have any reason to. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: latest freebsd:11:x86:64 repo and ruby 1.9 - 2.0
On 20/10/2014 01:08, Baptiste Daroussin wrote: On Sat, Oct 18, 2014 at 12:29:27PM +0300, Andriy Gapon wrote: $ pkg upgrade 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 (24 candidates): 100% Checking integrity... done (1 conflicting) Checking integrity... done (0 conflicting) The following 24 packages will be affected (of 0 checked): First, a minor nit: of 0 checked? Installed packages to be REMOVED: ruby-1.9.3.547_3,1 porttools-1.02 newfile-1.0.14_4 hub-1.12.2 libchk-1.10.3 zfs-snapshot-mgmt-20090201_2 Then the real problem, I do not want these packages to be removed except for ruby-1.9.3.547_3,1. In other words, I want to keep using zfs-snapshot-mgmt, libchk, hub and porttools. What should I do? Just accept the upgrade and reinstall them they are there. we need to improve the solver to prevent that. OK. This should work for me this time, but in general we can see how annoying this could be if dozens of packages would be affected. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
latest freebsd:11:x86:64 repo and ruby 1.9 - 2.0
$ pkg upgrade
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 (24 candidates): 100%
Checking integrity... done (1 conflicting)
Checking integrity... done (0 conflicting)
The following 24 packages will be affected (of 0 checked):
First, a minor nit: of 0 checked?
Installed packages to be REMOVED:
ruby-1.9.3.547_3,1
porttools-1.02
newfile-1.0.14_4
hub-1.12.2
libchk-1.10.3
zfs-snapshot-mgmt-20090201_2
Then the real problem, I do not want these packages to be removed except for
ruby-1.9.3.547_3,1. In other words, I want to keep using zfs-snapshot-mgmt,
libchk, hub and porttools. What should I do?
BTW, the updating entry for ruby says If you use pkgng, simply upgrade.
New packages to be INSTALLED:
ruby: 2.0.0.576_1,1 [FreeBSD]
Installed packages to be UPGRADED:
zsh: 5.0.6_2 - 5.0.7 [FreeBSD]
libgpg-error: 1.15 - 1.16 [FreeBSD]
p11-kit: 0.20.3_1 - 0.22.1 [FreeBSD]
ImageMagick: 6.8.9.8_1,1 - 6.8.9.8_2,1 [FreeBSD]
hplip: 3.14.4_3 - 3.14.4_4 [FreeBSD]
mediastreamer: 2.10.0_5 - 2.10.0_6 [FreeBSD]
curl: 7.38.0_1 - 7.38.0_2 [FreeBSD]
GeoIP: 1.6.2_1 - 1.6.2_2 [FreeBSD]
portlint: 2.15.4 - 2.15.6 [FreeBSD]
apache22: 2.2.29_1 - 2.2.29_2 [FreeBSD]
chromium: 37.0.2062.124_1 - 38.0.2125.101_1 [FreeBSD]
libmodplug: 0.8.8.5_1 - 0.8.8.5_2 [FreeBSD]
syslinux: 6.02 - 6.02_1 [FreeBSD]
gmake: 3.82_2 - 4.1 [FreeBSD]
tbb: 4.3.0 - 4.3.0_1 [FreeBSD]
mk-configure: 0.27.0 - 0.28.0 [FreeBSD]
Installed packages to be REINSTALLED:
vim-7.4.430_2 [FreeBSD] (needed shared library changed)
The process will require 20 MB more space.
Proceed with this action? [y/N]:
And my pkg configuration:
Version : 1.3.8
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: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:x86:64/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-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
devel/git vs gui
I've noticed that pre-built packages for git do not contain the gui component. Is possible to flip the options' default? Or, better but more laborious, provide a separate git-gui port? Thanks a lot! -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
GraphicsMagick + perl
Would anyone be so kind to add a perl option to GraphicsMagick similarly to ImageMagick? Currently GraphicsMagick is always configured --without-perl. Thanks! -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [CFT] boost 1.55.0
on 13/12/2013 10:47 Baptiste Daroussin said the following: It uses a modern compiler (sorry I haven't been able to make it use gcc from base at all, so it uses clang33 or gcc47+ from ports on FreeBSD 9.1 and FreeBSD 8.*, clang33 from base in FreeBSD 9.2 (if available) and cc on 10+) Just a question before I try. Are the above compiler choices hard-coded? Or will the port obey my wish to use gcc48 as the ports compiler on FreeBSD 11? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
(bsd)patch vs ports
When building ports on head I sometimes see messages like the following during a patch phase: === Applying FreeBSD patches for firefox-25.0_1,1 No such line 262 in input file, ignoring === Applying NSS patches No such line 194 in input file, ignoring No such line 658 in input file, ignoring No such line 52 in input file, ignoring No such line 45 in input file, ignoring Is this a cause for concern? Do those messages mean that potentially important patches are not actually applied? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Fwd: Re: audio/mumble/files/patch-compiler.pri
Could anybody please remove QMAKE_LFLAGS = -Wl line from audio/mumble/files/patch-compiler.pri ? Thanks! Original Message In-Reply-To:525cf09c.3060...@freebsd.org References: 525cf09c.3060...@freebsd.org From: Marius Nünnerich mar...@nuenneri.ch Date: Sat, 9 Nov 2013 10:09:39 + Message-ID: CABOWjPmE8njhRL1N8e23bH0kwegRv+ERT9ZCTNH57=nafbt...@mail.gmail.com Subject:Re: audio/mumble/files/patch-compiler.pri To: Andriy Gapon a...@freebsd.org Hey Andriy, sorry, I have no idea what that's supposed to do. I asked lme@ to remove me as the maintainer of that port as I'm not using it anymore. On Tue, Oct 15, 2013 at 8:37 AM, Andriy Gapon a...@freebsd.org mailto:a...@freebsd.org wrote: Guys, I've got a question about audio/mumble/files/patch-compiler.pri, in particular the following line: + QMAKE_LFLAGS = -Wl What's this supposed to do? As far as I know, -Wl,something means pass something to linker. In this case there is no something. I am not familiar with this usage of -Wl. In fact, gcc48 (unlike earlier versions?) seems to complain about it: g++48: error: unrecognized command line option '-Wl' -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
WITH_DEBUG messing CFLAGS
I wonder what is the thinking behind CFLAGS cleansing in the following snippet
from bsd.port.mk:
.if defined(WITH_DEBUG) !defined(WITHOUT_DEBUG)
STRIP_CMD= ${TRUE}
DEBUG_FLAGS?= -g
CFLAGS:=${CFLAGS:N-O*:N-fno-strict*} ${DEBUG_FLAGS}
.endif
If I want to control optimization level for WITH_DEBUG, then I can always pass
-O0 or -Owhatever in DEBUG_FLAGS. But there is no way for me to say leave
CFLAGS alone.
Besides, the quoted logic seems to be incomplete with respect to CXXFLAGS.
I think that the CFLAGS line should be changed simply to:
CFLAGS+=${DEBUG_FLAGS}
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
CC, CPP etc vs CONFIGURE_ENV
I wonder why do-configure target explicitly sets things like CC=${CC}
CPP=${CPP} etc in configure script environment as opposed to them just being
placed into CONFIGURE_ENV.
What is the technical reason?
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: CC, CPP etc vs CONFIGURE_ENV
on 06/11/2013 17:11 Charles Swiger said the following:
Hi--
On Nov 6, 2013, at 6:27 AM, Andriy Gapon a...@freebsd.org wrote:
I wonder why do-configure target explicitly sets things like CC=${CC}
CPP=${CPP} etc in configure script environment as opposed to them just
being
placed into CONFIGURE_ENV.
What is the technical reason?
Setting $CC and such worked with older ./configure which didn't implement
$CONFIGURE_ENV.
It also plays more nicely with things which roll their own ./configure as a
shim
that isn't actually GNU autoconf.
Apologies, you seem to think that CONFIGURE_ENV is an environment variable of
its own. But, as far as I can see, it is not. It is a make variable with a
value that expands to FOO=BAR VAR=VAL ... and those FOO, VAR, etc are the
environment variables that are to be set in configure's environment:
${SETENV} ... ${CONFIGURE_ENV} ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}
So, either I didn't understand what you said or what you said is not relevant.
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng repository priorities
on 03/11/2013 04:00 Michael Gmelin said the following: On Sat, 02 Nov 2013 21:44:43 -0400 Nikolai Lifanov lifa...@mail.lifanov.com wrote: Is there any documentation about how to use PKGNG repository priorities? I heard that these are available. Currently, I have my repository configurations like this: 1-myrepo.conf 2-anotherrepo.conf 3-someotherthirdpartyrepo.conf This roughly prefers stuff from what appears first in asciibetical order. I would like to use the official FreeBSD package sets, but to do this, I need to always prefer a package from a local repository (WITH_NEW_XORG, WITH_KMS) if a package is available in it. How can I set this kind of preference? According to pkg-repository(5): WORKING WITH MULTIPLE REPOSITORIES Where several different repositories are configured pkg will search amongst them all in the order specified, unless directed to use a single repository by the -r -flag -to pkg-fetch(8), pkg-install(8), pkg-upgrade, pkg-search or pkg-rquery. The search order is as displayed in the output of pkg -v -v This information does not seem to match the reality though: https://github.com/freebsd/pkg/issues/632 Also, pkg-repository(5) provides useful information on how to pin some packages to a certain repository, but be aware of the following bug: https://github.com/freebsd/pkg/issues/631 Speaking from my own practical experience with multi-repository setup. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
pkgng multi-repository support description
Is there a document that describes how pkgng multi-repository support works? I am trying to understand what pkgng does when different versions of the same package are present in different repositories. Practically, I want to achieve the following. One repository is designated as primary. If a package is present in the primary repository, then its presence in other repositories is completely ignored. Alternatively, the following could also work for me. A package remembers from what repository it was originally installed and all future upgrades are taken from the same repository. What I want to avoid is a package flip-flopping between being installed from different repositories depending on their update pace. This is useful e.g. when I have my local repository for some packages that I want to build with special options but I also want to install all other packages from some other repository which is not under my control. So I fear that the other repository gets a newer version of a package than what my repository has, then pkg upgrade would upgrade the package and thus it won't have any customizations until my repository catches up. Thank you very much. P.S. https://github.com/freebsd/pkg#multirepos seems to be outdated? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: security/gnupg installation failed
[ping] on 05/10/2013 15:03 Andriy Gapon said the following: I have the following configuration for the port: === The following configuration options are available for gnupg-2.0.22: PINENTRY=on: Use pinentry LDAP=off: LDAP keyserver interface SCDAEMON=off: Enable Smartcard daemon (with libusb) CURL=on: Use the real curl library (worked around if no) GPGSM=off: Enable GPGSM (requires LDAP) KDNS=off: Use DNS CERT helper STD_SOCKET=off: Use standard socket for agent NLS=off: Native Language Support DOCS=off: Build and/or install documentation SUID_GPG=off: Install GPG with suid === Use 'make config' to modify these settings Installation fails like this: === Checking if security/gnupg already installed === Registering installation for gnupg-2.0.22 as automatic pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/com-certs.pem): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.be.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.ca.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.cs.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.da.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.de.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.el.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.eo.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.es.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.et.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.fi.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.fr.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.gl.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.hu.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.id.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.it.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.ja.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.nb.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.pl.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.pt.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.pt_BR.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.ro.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.ru.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.sk.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.sv.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.tr.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.zh_CN.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.zh_TW.txt): No such file or directory pkg-static: lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/qualified.txt): No such file or directory *** Error code 74 -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing
Re: [HEADSUP] Staging, packaging and more
on 03/10/2013 11:48 Baptiste Daroussin said the following: This also allows lots of new features to come: - Allow to create sub-packages - Allow to create debuginfo packages. I'd like to mention a few other possibilities along the same lines: - doc packages - examples packages - devel packages (headers, tools and other files required for compiling dependent software, but not generally needed for an end user) All open up to a debate, of course. Thank you very much for doing this major step! - Allow to do a lot of sanity check in the staging area to improve our QA -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
multimedia/dirac compilation fails with gcc46
parseunit_byteio.cpp:127:23: error: variable 'next_parse_code' set but not used [-Werror=unused-but-set-variable] parseunit_byteio.cpp:131:13: error: variable 'next_unit_next_parse_offset' set but not used [-Werror=unused-but-set-variable] -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: chromium-28.0.1500.71 build failed on a system without base gcc
on 04/08/2013 15:10 George Liaskos said the following:
Try this,
diff --git a/www/chromium/Makefile b/www/chromium/Makefile
index af1fd1b..dab973d 100644
--- a/www/chromium/Makefile
+++ b/www/chromium/Makefile
@@ -192,7 +192,7 @@ post-patch:
${WRKSRC}/ui/base/strings/app_locale_settings_th.xtb
do-configure:
- cd ${WRKSRC} \
+ cd ${WRKSRC} CC=${CC} CXX=${CXX} \
GYP_DEFINES=${GYP_DEFINES} ${PYTHON_CMD} \
./build/gyp_chromium chrome/chrome.gyp --depth .
Thank you very much! This has helped.
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
glib-2.36.3 build fails with gcc46
glib-2.36.3 build fails with gcc46: glib-unix.c: In function 'g_unix_open_pipe': glib-unix.c:97:5: error: implicit declaration of function 'pipe2' [-Werror=implicit-function-declaration] cc1: some warnings being treated as errors I think that unistd.h must be included. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: glib-2.36.3 build fails with gcc46
on 03/08/2013 16:33 Andriy Gapon said the following: glib-2.36.3 build fails with gcc46: glib-unix.c: In function 'g_unix_open_pipe': glib-unix.c:97:5: error: implicit declaration of function 'pipe2' [-Werror=implicit-function-declaration] cc1: some warnings being treated as errors I think that unistd.h must be included. Sorry for the noise, this was a pilot error. I use head, but keep forgetting that once in a while lang/gcc* have to be rebuilt after changes in the system headers (because those gccs install some fixed versions of them in /usr/local/lib/gcc*/gcc/*/*/include-fixed/). -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: chromium-28.0.1500.71 build failed on a system without base gcc
[ping] on 19/07/2013 18:15 Andriy Gapon said the following: On this system I do not build and install base gcc (WITHOUT_GCC=yes), cc is clang. I do have lang/gcc (gcc 4.6.x) installed, though. cd /usr/obj/ports/usr/ports/www/chromium/work/chromium-courgette-redacted-28.0.1500.71 GYP_DEFINES=use_cups=1 use_system_yasm=1 use_system_libxml=1 use_system_ffmpeg=0 use_system_libusb=1 use_system_libevent=1 use_system_libvpx=0 linux_breakpad=0 linux_strip_binary=1 linux_use_tcmalloc=0 linux_use_heapchecker=0 test_isolation_mode=noop clang_use_chrome_plugins=0 disable_nacl=1 enable_webrtc=1 enable_openmax=1 enable_one_click_signin=1 no_gc_sections=1 os_ver=135 prefix_dir=/usr/local python_ver=2.7 google_api_key=AIzaSyBsp9n41JLW8jCokwn7vhoaMejDFRd1mp8 google_default_client_id=996322985003.apps.googleusercontent.com google_default_client_secret=IR1za9-1VK0zZ0f_O8MVFicn ffmpeg_branding=Chrome proprietary_codecs=1 use_pulseaudio=0 gcc_version=46 buildtype=Official /usr/local/bin/python2.7 ./build/gyp_chromium chrome/chrome.gyp --depth . Updating projects from gyp files... g++: not found compiler_version.py failed to execute: g++ -dumpversion Command 'g++ -dumpversion' returned non-zero exit status 127 -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
ftp/curl build fails
I am using gcc46 to build ports. Port configuration: === The following configuration options are available for curl-7.31.0: CA_BUNDLE=on: Install CA bundle for OpenSSL COOKIES=on: Cookies support CURL_DEBUG=off: cURL debug memory tracking DEBUG=off: Install debug symbols DOCS=on: Build and/or install documentation EXAMPLES=on: Build and/or install examples GSSAPI=on: GSSAPI support IDN=off: International Domain Names support IPV6=off: IPv6 protocol support LDAP=off: LDAP support LDAPS=off: LDAPS support LIBSSH2=on: SCP/SFTP support via libssh2 NTLM=off: NTLM authentication support PROXY=on: Proxy support RTMP=off: RTMP protocol support via librtmp SPNEGO=on: SPNEGO (RFC 4178) support TLS_SRP=on: TLS-SRP (Secure Remote Password) support DNS resolving options: you can only select none or one of them CARES=on: Asynchronous DNS resolution via c-ares THREADED_RESOLVER=off: Threaded DNS resolver SSL protocol support: you can only select none or one of them CYASSL=off: SSL/TLS support via CyaSSL GNUTLS=off: SSL/TLS support via GnuTLS NSS=off: SSL/TLS support via NSS OPENSSL=on: SSL/TLS support via OpenSSL POLARSSL=off: SSL/TLS support via PolarSSL Failure: In file included from file.c:52:0: urldata.h:439:3: error: unknown type name 'OM_uint32' urldata.h:440:3: error: unknown type name 'gss_ctx_id_t' urldata.h:441:3: error: unknown type name 'gss_name_t' urldata.h:442:3: error: unknown type name 'gss_buffer_desc' The problem seems to be that fbopenssl installs its own gssapi.h file in /usr/local/include/fbopenssl/gssapi.h and /usr/local/include/fbopenssl is on the include path before /usr/include. And that gssapi.h is not the intended one. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: new make vs security/vpnc
on 09/07/2013 10:25 Tijl Coosemans said the following: On 2013-07-09 00:05, Andriy Gapon wrote: Seems like the problem boils down to this: $ make -V MAKEFILE /usr/ports/security/vpnc/Makefile $ fmake -V MAKEFILE Makefile The only explicit assignments of MAKEFILE that I could find in ports infrastructure are these: /usr/ports/Mk/bsd.port.mk:MAKEFILE?= Makefile /usr/ports/Mk/bsd.gnustep.mk:MAKEFILE= GNUmakefile The problem is probably that .OBJDIR (/usr/obj/usr/ports/security/vpnc) exists. Bmake assigns an absolute path to MAKEFILE in that case. Bingo! I use WRKDIRPREFIX=/usr/obj/*ports*, so i am not sure how /usr/obj/usr/ports/security/vpnc came to exist. A timestamp on it is 1 year old, so I won't be able to recall now. Thank you! MAKEFILE is an internal variable of make and bsd.port.mk uses it for another purpose. It should use another name like MAKE_FILE imho. I agree. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
port options are not saved in some ports
It seems that port options do not stick in the following ports: ukrainian/kde4-l10n russian/kde4-l10n Could you please take a look? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
new make vs security/vpnc
Using recent head and the latest ports as of now. $ cd /usr/ports/security/vpnc $ make === Building for vpnc-0.5.3_8 /usr/ports/security/vpnc/Makefile:37: *** missing separator. Stop. *** Error code 1 But fmake works just fine without any error. In my ports tree Makefile:37 is: .include bsd.port.options.mk Please advise. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: new make vs security/vpnc
on 09/07/2013 00:07 Andriy Gapon said the following: Using recent head and the latest ports as of now. $ cd /usr/ports/security/vpnc $ make === Building for vpnc-0.5.3_8 /usr/ports/security/vpnc/Makefile:37: *** missing separator. Stop. *** Error code 1 But fmake works just fine without any error. In my ports tree Makefile:37 is: .include bsd.port.options.mk Please advise. A quick followup. I ran make -dA and noticed the following in the output: *** Failed target: do-build *** Failed command: (cd /usr/obj/ports/usr/ports/security/vpnc/work/vpnc-0.5.3; if ! /usr/bin/env BINS=cisco-decrypt SHELL=/bin/sh NO_LINT=YES ADDR2LINE=/usr/local/bin/addr2line AR=/usr/local/bin/ar AS=/usr/local/bin/as CPPFILT=/usr/local/bin/c++filt GPROF=/usr/local/bin/gprof LD=/usr/local/bin/ld NM=/usr/local/bin/nm OBJCOPY=/usr/local/bin/objcopy OBJDUMP=/usr/local/bin/objdump RANLIB=/usr/local/bin/ranlib READELF=/usr/local/bin/readelf SIZE=/usr/local/bin/size STRINGS=/usr/local/bin/strings PREFIX=/usr/local LOCALBASE=/usr/local MOTIFLIB=-L/usr/local/lib -lXm -lXp LIBDIR=/usr/lib CC=gcc46 CFLAGS=-O2 -pipe -O2 -fno-strict-aliasing -pipe -march=amdfam10 -DOPENSSL_GPL_VIOLATION -DCISCO_PATCH_VERSION -march=amdfam10 -march=amdfam10 CPP=cpp46 CPPFLAGS= LDFLAGS= -lcrypto -Wl,-rpath=/usr/local/lib/gcc46 -L/usr/local/lib/gcc46 -Wl,-rpath=/usr/local/lib/gcc46 -L/usr/local/lib/gcc46 CXX=g++46 CXXFLAGS=-O2 -pipe -O2 -fno-strict-aliasing -pipe -march=amdfam10 -DOPENSSL_GPL_VIOLATION -DCISCO_PATCH_VERSION -march=amdfam10 -march=amdfam10 -O2 -fno-strict-aliasing -pipe -march=amdfam10 -march=amdfam10 MANPREFIX=/usr/local BSD_INSTALL_PROGRAM=install -s -o root -g wheel -m 555 BSD_INSTALL_LIB=install -s -o root -g wheel -m 444 BSD_INSTALL_SCRIPT=install -o root -g wheel -m 555 BSD_INSTALL_DATA=install -o root -g wheel -m 444 BSD_INSTALL_MAN=install -o root -g wheel -m 444 gmake -f /usr/ports/security/vpnc/Makefile -j`/sbin/sysctl -n kern.smp.cpus` all; then if [ -n ] ; then echo === Compilation failed unexpectedly.; (echo ) | /usr/bin/fmt 75 79 ; fi; false; fi) This is quite a large snippet, so here is a smaller and more obvious one: gmake -f /usr/ports/security/vpnc/Makefile -j`/sbin/sysctl -n kern.smp.cpus` all And indeed: $ gmake Makefile:37: *** missing separator. Stop. The port has USES= ... gmake but that's supposed to affect what is used inside the working directory. It's certainly a bug that gmake is run with the port's make file. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: new make vs security/vpnc
Seems like the problem boils down to this: $ make -V MAKEFILE /usr/ports/security/vpnc/Makefile $ fmake -V MAKEFILE Makefile The only explicit assignments of MAKEFILE that I could find in ports infrastructure are these: /usr/ports/Mk/bsd.port.mk:MAKEFILE?=Makefile /usr/ports/Mk/bsd.gnustep.mk:MAKEFILE= GNUmakefile -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: softirq and tasklets
on 22/05/2013 15:37 Orit Moskovich said the following: Hi, Is there an equivalent concept for Linux softirq and tasklets in FreeBSD? If not, what will be the closest way to implement them? With the takqueue taskqueue_swi which executes its tasks in the context of an interrupt? A filter routine or interrupt thread defined in bus_setup_intr...? This is an odd mailing list for the question. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: graphics/digikam-kde4 does not build on CURRENT
on 01/04/2013 16:28 Rainer Hurling said the following: This happens on 10.0-CURRENT r248896 (amd64; clang compiled). I am wondering if I am the only one with this error? No. digikam port has to be updated to a more recent version to be compatible with some newer APIs. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
multimedia/kino: Option number is ambiguous (number-footnotes, number-sections)
For some reason multimedia/kino build fails for me with the following messages: texi2html -monolithic -number doc/ffplay-doc.texi Option number is ambiguous (number-footnotes, number-sections) Try `texi2html --help' for more information. The following change (suggested by someone on irc) seems to help: --- ffmpeg/Makefile.orig2012-12-14 20:22:21.792498012 +0200 +++ ffmpeg/Makefile 2012-12-14 20:22:42.924498798 +0200 @@ -129,7 +129,7 @@ $(ALLMANPAGES)) doc/%.html: doc/%.texi - texi2html -monolithic -number $ + texi2html -monolithic -number-sections $ mv $(@F) $@ doc/%.pod: doc/%-doc.texi -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
graphics/OpenEXR: patch for gcc46+
--- exrenvmap/blurImage.cpp.orig2012-11-23 23:23:48.714449156 +0200 +++ exrenvmap/blurImage.cpp 2012-11-23 23:24:09.765447850 +0200 @@ -45,6 +45,7 @@ #include Iex.h #include iostream #include algorithm +#include cstring using namespace std; using namespace Imf; This patch is required because memcpy(3) is used in the file. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
graphics/ilmbase: gcc46+ patch
--- Imath/ImathMatrix.h.orig2012-11-23 23:29:16.401450990 +0200 +++ Imath/ImathMatrix.h 2012-11-23 23:29:37.622449298 +0200 @@ -51,6 +51,7 @@ #include iostream #include iomanip +#include cstring #if (defined _WIN32 || defined _WIN64) defined _MSC_VER // suppress exception specification warnings This patch is required because memset and memcpy are used in this file. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
download2.berlios.de problem
It looks like download2.berlios.de consistently refuses connection. download.berlios.de still works fine. But it seems that the way fetch works download2 gets picked first and then it is retried forever in such a situation if -a flag is used. Maybe download2 should eb dropped from MASTER_SITE_BERLIOS? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
sysutils/ntfsprogs: problem with GNOMEVFS2
If GNOMEVFS2 option is selected in sysutils/ntfsprogs, then make-ing of any target becomes impossible: /usr/ports/Mk/bsd.gnome.mk, line 657: The Pre include part of bsd.gnome.mk part is not included. Did you forget WANT_GNOME=yes before bsd.port.pre.mk? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
pkgng: lcms2-2.4 conflicts with lcms-1.19_1,1
Not sure if my environment is messed up or if it is OK, but i have both lcms and lcms2 installed, and there is a bunch of packages that depend on them. I've been using pkgng for a while now and it never complained about these packages, but now it produces the following error: Installing lcms2-2.4... pkg: lcms2-2.4 conflicts with lcms-1.19_1,1 (installs files into the same place). Problematic file: /usr/local/man/man1/jpegicc.1.gz -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng: lcms2-2.4 conflicts with lcms-1.19_1,1
on 08/10/2012 18:51 Oliver Heesakkers said the following: Op ma 08 okt 2012 18:30:12 schreef Andriy Gapon: Not sure if my environment is messed up or if it is OK, but i have both lcms and lcms2 installed, and there is a bunch of packages that depend on them. I've been using pkgng for a while now and it never complained about these packages, but now it produces the following error: Installing lcms2-2.4... pkg: lcms2-2.4 conflicts with lcms-1.19_1,1 (installs files into the same place). Problematic file: /usr/local/man/man1/jpegicc.1.gz Now that the following patch has been committed, this issue should no longer exist (jpegicc vs jpgicc and tifficc vs tificc): http://www.freebsd.org/cgi/query-pr.cgi?pr=172465 The commit just reached me via portsnap, everything is fine now. Thank you! -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
conflict between devel/patch and gettext ?
At least pkgng reports/detects it: pkg: patch-2.7 conflicts with gettext-0.18.1.1 (installs files into the same place). Problematic file: /usr/local/lib/charset.alias -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
graphics/libfpx fails with gcc46 because of new warnings
files/Makefile.bsd has WARNS=3, but: /usr/obj/ports/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ri_image/ptile.cpp: In static member function 'static void PTile::FreeAncientBuffers(long int)': /usr/obj/ports/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ri_image/ptile.cpp:778:24: error: variable 'timeNow' set but not used [-Werror=unused-but-set-variable] /usr/obj/ports/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ri_image/ptile.cpp: In static member function 'static void PTile::FreeAncientBuffers(long int)': /usr/obj/ports/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ri_image/ptile.cpp:778:24: error: variable 'timeNow' set but not used [-Werror=unused-but-set-variable] WARNS=1 helps... -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: conflict between devel/patch and gettext ?
on 05/10/2012 19:28 Greg Larkin said the following: On 10/5/12 4:33 AM, Andriy Gapon wrote: At least pkgng reports/detects it: pkg: patch-2.7 conflicts with gettext-0.18.1.1 (installs files into the same place). Problematic file: /usr/local/lib/charset.alias Hello Andriy, I just committed the fix, so please try the build again with pkgng. Thank you! It works fine now. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [devel/newfile] - Problem with patch.
on 25/09/2012 15:05 TAKATSU Tomonari said the following: Did you install and update ports tree via portsnap? This problem is caused by the SVN to CVS exporter. Please consider using svn instead of portsnap to update ports tree. This is a wrong advice. portsnap MUST be well supported. Whatever feeds should be fixed, probably there is no reason to feed portsnap via svn-cvs exported. See also http://docs.freebsd.org/cgi/mid.cgi?87zk4fnng6.fsf and http://docs.freebsd.org/cgi/mid.cgi?D7122959-18EF-4BFA-90B2-D40D83287F63 . -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [FreeBSD-Announce] Announcing the end of port CVS
on 07/09/2012 14:57 Steven Hartland said the following: Is there no way to tell it not to delete unknown files so we don't have to add addional steps to the workflow flow of adding additional patches to local port builds? I would hazard a recommendation to use something like git-svn / svk /etc if you are going to have local ports development on top of the official tree. There is a git clone of ports on github. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
gdb75 dumps core on startup
Program terminated with signal 11, Segmentation fault ... #0 0x004777e2 in i386_use_watchpoints () #1 0x00476bbd in _initialize_amd64fbsd_nat () #2 0x0060deea in initialize_all_files () #3 0x005e710f in gdb_init () #4 0x00549086 in relocate_gdb_directory () #5 0x00547aa4 in catch_errors () #6 0x00548bb4 in gdb_main () #7 0x00457ea9 in main () This is on amd64 head. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: gdb75 dumps core on startup
on 27/08/2012 17:03 Andriy Gapon said the following: Program terminated with signal 11, Segmentation fault ... #0 0x004777e2 in i386_use_watchpoints () #1 0x00476bbd in _initialize_amd64fbsd_nat () #2 0x0060deea in initialize_all_files () #3 0x005e710f in gdb_init () #4 0x00549086 in relocate_gdb_directory () #5 0x00547aa4 in catch_errors () #6 0x00548bb4 in gdb_main () #7 0x00457ea9 in main () This is on amd64 head. The problem seems to be caused by files/patch-gdb-amd64-nat.h, which for some cryptic reason removes prototype of amd64bsd_target() from amd64-nat.h. That allows the code to be compilable still (sloppy gdb developers!) but the assumed return type of the function becomes int instead of a pointer which it really is. Thus, the returned pointer value gets truncated on amd64 and as a result an invalid pointer is passed to i386_use_watchpoints() from _initialize_amd64fbsd_nat(). Oh, looking at the patch in PR ports/165357 (http://www.freebsd.org/cgi/query-pr.cgi?pr=165357), it seems that amd64bsd_target() should have re-appeared in a new header file amd64bsd-nat.h... But that part of the patch seems to be incorrect in that it would create files/amd64bsd-nat.h instead of a patch file to create amd64bsd-nat.h in the source directory. Apparently this file never made it as a result. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: gdb75 dumps core on startup
on 27/08/2012 17:44 Andriy Gapon said the following: on 27/08/2012 17:03 Andriy Gapon said the following: Program terminated with signal 11, Segmentation fault ... #0 0x004777e2 in i386_use_watchpoints () #1 0x00476bbd in _initialize_amd64fbsd_nat () #2 0x0060deea in initialize_all_files () #3 0x005e710f in gdb_init () #4 0x00549086 in relocate_gdb_directory () #5 0x00547aa4 in catch_errors () #6 0x00548bb4 in gdb_main () #7 0x00457ea9 in main () This is on amd64 head. The problem seems to be caused by files/patch-gdb-amd64-nat.h, which for some cryptic reason removes prototype of amd64bsd_target() from amd64-nat.h. That allows the code to be compilable still (sloppy gdb developers!) but the assumed return type of the function becomes int instead of a pointer which it really is. Thus, the returned pointer value gets truncated on amd64 and as a result an invalid pointer is passed to i386_use_watchpoints() from _initialize_amd64fbsd_nat(). Oh, looking at the patch in PR ports/165357 (http://www.freebsd.org/cgi/query-pr.cgi?pr=165357), it seems that amd64bsd_target() should have re-appeared in a new header file amd64bsd-nat.h... But that part of the patch seems to be incorrect in that it would create files/amd64bsd-nat.h instead of a patch file to create amd64bsd-nat.h in the source directory. Apparently this file never made it as a result. Oh, oops, I misread history a bit and I see now that amd64bsd-nat.h is included upstream. But since the upstream version doesn't have a prototype for amd64bsd_target(), then files/patch-gdb-amd64-nat.h should be dropped. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: gdb75 dumps core on startup
on 27/08/2012 17:48 Luca Pizzamiglio said the following: I'm waiting someone commit this: ports/171109 Great, thanks! On Mon, Aug 27, 2012 at 4:44 PM, Andriy Gapon a...@freebsd.org wrote: on 27/08/2012 17:03 Andriy Gapon said the following: Program terminated with signal 11, Segmentation fault ... #0 0x004777e2 in i386_use_watchpoints () #1 0x00476bbd in _initialize_amd64fbsd_nat () #2 0x0060deea in initialize_all_files () #3 0x005e710f in gdb_init () #4 0x00549086 in relocate_gdb_directory () #5 0x00547aa4 in catch_errors () #6 0x00548bb4 in gdb_main () #7 0x00457ea9 in main () This is on amd64 head. The problem seems to be caused by files/patch-gdb-amd64-nat.h, which for some cryptic reason removes prototype of amd64bsd_target() from amd64-nat.h. That allows the code to be compilable still (sloppy gdb developers!) but the assumed return type of the function becomes int instead of a pointer which it really is. Thus, the returned pointer value gets truncated on amd64 and as a result an invalid pointer is passed to i386_use_watchpoints() from _initialize_amd64fbsd_nat(). Oh, looking at the patch in PR ports/165357 (http://www.freebsd.org/cgi/query-pr.cgi?pr=165357), it seems that amd64bsd_target() should have re-appeared in a new header file amd64bsd-nat.h... But that part of the patch seems to be incorrect in that it would create files/amd64bsd-nat.h instead of a patch file to create amd64bsd-nat.h in the source directory. Apparently this file never made it as a result. -- Andriy Gapon -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: gdb75 dumps core on startup
on 27/08/2012 17:51 Andriy Gapon said the following:
on 27/08/2012 17:48 Luca Pizzamiglio said the following:
I'm waiting someone commit this:
ports/171109
Great, thanks!
BTW, you might want to fix another issue along the way: make reinstall fails
because of an existing symlink. -f option to ${LN} should fix that.
install -o root -g wheel -m 555
/usr/obj/ports/usr/ports/devel/gdb/work/gdb-7.5/gdb/gdb /usr/local/bin/gdb75
/bin/ln /usr/local/bin/gdb75 /usr/local/bin/gdbtui75
ln: /usr/local/bin/gdbtui75: File exists
*** [do-install] Error code 1
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng, textproc/p5-XML-SAX-Expat: Syntax error: { unexpected (expecting then)
on 21/08/2012 12:08 Chris Rees said the following:
On 21 August 2012 09:47, Anton Shterenlikht me...@bristol.ac.uk wrote:
# cd /usr/ports/textproc/p5-XML-SAX-Expat
# make deinstall make reinstall
=== Deinstalling for textproc/p5-XML-SAX-Expat
=== Deinstalling p5-XML-SAX-Expat-0.40
The following packages will be deinstalled:
p5-XML-SAX-Expat-0.40
The deinstallation will free 22 kB
Deinstalling p5-XML-SAX-Expat-0.40...p5-XML-SAX-Expat-0.40 is required by:
p5-XML-Simple-2.20 icon-naming-utils-0.8.90, deleting anyway
Syntax error: { unexpected (expecting then)
pkg: DEINSTALL script failed
*** [deinstall] Error code 3
Stop in /usr/ports/textproc/p5-XML-SAX-Expat.
# pkg -vvv
version: 1.0-rc6
abi: freebsd:10:ia64:64
db dir: /var/db/pkg
cache dir: /var/cache/pkg
ports dir: /usr/ports
Log into syslog: yes
Assume always yes: no
Handle rc scripts: no
Track shlibs: no
Automatic dependency tracking: no
Custom keywords directory: none
Developer mode: no
Repository: ftp://ftp.freebsd.org/pub/pkgng
#
How long have you had this installed?
Steve Wills [1] fixed the pkg-deinstall script yesterday, but
evidently you still have an older version.
Right, but it's hard to upgrade to the new version without deinstalling the old
version, isn't it? :-)
If pkg delete hasn't removed it, try pkg delete -f, then reinstall.
pkg delete -f won't help (as already shown in the original message).
Instead, as Baptiste advised me:
cd /usr/ports/textproc/p5-XML-SAX-Expat
make install FORCE_PKG_REGISTER=1
In the case of pkgng the above command should do the right thing in this case
(in-place upgrade).
[1]
http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/p5-XML-SAX-Expat/pkg-deinstall
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: graphics/libfpx: use of bsd.lib.mk and warnings
On 28.07.2012 12:25, Thomas Zander wrote: It also causes the port to use clang when setting CC=clang in /etc/src.conf (!) which fails here. I am truly and utterly surprised that nobody seems to have this problem. The idea of using bsd.lib.mk is simple: here are the sources, please, build me a shared library :-) Does it fail to build with clang? -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: graphics/libfpx: use of bsd.lib.mk and warnings
on 28/07/2012 19:28 Andriy Gapon said the following: On 28.07.2012 12:25, Thomas Zander wrote: It also causes the port to use clang when setting CC=clang in /etc/src.conf (!) which fails here. I am truly and utterly surprised that nobody seems to have this problem. The idea of using bsd.lib.mk is simple: here are the sources, please, build me a shared library :-) Does it fail to build with clang? -mi I very much wonder how the above email ended up having From: set to _my_ email address. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] LibreOffice build issues
on 26/07/2012 03:31 Jung-uk Kim said the following: I guess you had installed OpenSSL from ports. ;-) Yes, bingo. Now I am able to build it with GCC 4.6: http://people.freebsd.org/~jkim/libreoffice-20120725.tar.bz2 Basically, bsd.openssl.mk adds -rpath=/usr/lib:/usr/local/lib to LDFLAGS first, then bsd.gcc.mk adds -Wl,-rpath=/usr/local/lib/gcc46 to it later. Before: % make -V LDFLAGS -rpath=/usr/lib:/usr/local/lib % make -V LDFLAGS USE_OPENSSL_BASE=yes -rpath=/usr/lib:/usr/local/lib % make -V LDFLAGS USE_OPENSSL_PORT=yes -rpath=/usr/local/lib % make -V LDFLAGS USE_OPENSSL_BASE=yes WITH_GCC=yes -rpath=/usr/lib:/usr/local/lib -Wl,-rpath=/usr/local/lib/gcc46 % make -V LDFLAGS USE_OPENSSL_PORT=yes WITH_GCC=yes -rpath=/usr/local/lib -Wl,-rpath=/usr/local/lib/gcc46 For WITH_GCC case, I just defined OPENSSL_LDFLAGS as -rpath=/usr/local/lib/gcc46. After: % make -V LDFLAGS -rpath=/usr/lib:/usr/local/lib % make -V LDFLAGS USE_OPENSSL_BASE=yes -rpath=/usr/lib:/usr/local/lib % make -V LDFLAGS USE_OPENSSL_PORT=yes -rpath=/usr/local/lib % make -V LDFLAGS USE_OPENSSL_BASE=yes WITH_GCC=yes -rpath=/usr/local/lib/gcc46 -rpath=/usr/lib:/usr/local/lib -Wl,-rpath=/usr/local/lib/gcc46 % make -V LDFLAGS USE_OPENSSL_PORT=yes WITH_GCC=yes -rpath=/usr/local/lib/gcc46 -rpath=/usr/local/lib -Wl,-rpath=/usr/local/lib/gcc46 It's ugly but it's good enough for now. Please note this is really a bug in bsd.openssl.mk (and/or bsd.port.mk depending on how you look at it). It shouldn't have added /usr/lib in the first place. It is only needed for OPENSSL_PORT case and just /usr/local/lib itself. Also, bsd.gcc.mk had to be included before all bsd.foo.mk, whatever touches rpath. Good analysis and catch! I think that just dropping /usr/lib from rpath should be sufficient, but the way you are doing it could be safer in the long term. Thank you. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: (semi-)official git mirror of ports svn repo?
on 24/07/2012 18:58 Ulrich Spörlein said the following: Yes, it's to become the official one, once I get my act together. It's still missing the git-notes, but that will be fixed later and doesn't impact anything, really. So please use git://github.com/freebsd/freebsd-ports.git or the source as a fallback git://git.freebsd.org/freebsd-ports.git Thank you very much! P.S. Also thank you for teaching me about Mail-Followup-To :-) -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] LibreOffice build issues
Just a note: yesterday I built the port using GCC 4.6 and external cppunit also built with GCC 4.6 (in fact almost all of my ports are built with that compiler). I did not run into any problems whatsoever. I am a little bit saddened that GCC46 option was thrown out. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] LibreOffice build issues
on 23/07/2012 23:49 Jung-uk Kim said the following: On 2012-07-23 16:34:34 -0400, Andriy Gapon wrote: Just a note: yesterday I built the port using GCC 4.6 and external cppunit also built with GCC 4.6 (in fact almost all of my ports are built with that compiler). I did not run into any problems whatsoever. I am a little bit saddened that GCC46 option was thrown out. We can re-add it but it makes the Makefile little too complicated. :-( Here is what I used: http://people.freebsd.org/~avg/libreoffice-Makefile.txt But of course I have my own version of bsd.gcc.mk which allows WITH_GCC=gcc46 in make.conf to do the right thing (mostly). -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
(semi-)official git mirror of ports svn repo?
Do we have a (semi-)official git mirror of the new ports _svn_ repo? Something either FreeBSD hosted/managed or maintained by prominent ports developers on github/gitorious/elsewhere? I looked at gitorious, github and freebsd.your.org and only this github repository seems to be active: https://github.com/freebsd/freebsd-ports/commits/master But note sure if it based off svn. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: RFE - FreeBSD Port: zfs-snapshot-mgmt-20090201_2
on 29/06/2012 09:39 Karli Sjöberg said the following:
Thanks, that was fast!
# patch /usr/local/bin/zfs-snapshot-mgmt zfs-snapshot-mgmt.patch
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--
|--- zfs-snapshot-mgmt2010-06-02 05:31:28.759931924 +0300
|+++ zfs-snapshot-mgmt2010-06-01 01:49:46.665034414 +0300
--
Patching file /usr/local/bin/zfs-snapshot-mgmt using Plan A...
patch: malformed patch at line 12: @name).readlines.collect.select {
|item|
item[0, @name.length + 1] == @name +
OK, so that didn´t go that well. Manually editing the script to what I think
you
ment:
I should have remembered that copy+paste over email usually doesn't work very
well. So here is the patch again:
http://people.freebsd.org/~avg/snapshot.list.diff
/usr/local/bin/zfs-snapshot-mgmt:
# def snapshots(prefix)
#path = File.join(@mount_point, '.zfs', 'snapshot')
#Dir.open(path).select do |name|
# name[0, prefix.length] == prefix
#end.map { |name| SnapshotInfo.new(name, @name, prefix) }
# end
#path = File.join(@mount_point, '.zfs', 'snapshot')
#Dir.open(path).select do |name|
s = IO.popen('zfs list -r -t snapshot -H -o name
'@name).readlines.collect.select { |item| item[0, @name.length + 1] == @name
'@'
}.map { |item| item[@name.length + 1 .. -1] }
s.select do |name|
name[0, prefix.length] == prefix
end.map { |name| SnapshotInfo.new(name, @name, prefix) }
end
But recieves from cron:
/usr/local/bin/zfs-snapshot-mgmt:138: syntax error, unexpected tIVAR,
expecting ')'
... -t snapshot -H -o name '@name).readlines.collect.select { |...
^
/usr/local/bin/zfs-snapshot-mgmt:138: syntax error, unexpected tSTRING_BEG,
expecting '}'
..., @name.length + 1] == @name '@' }.map { |item| item[@name.l...
^
/usr/local/bin/zfs-snapshot-mgmt:188: syntax error, unexpected kEND,
expecting $end
/Karli
29 jun 2012 kl. 01.20 skrev Andriy Gapon:
on 28/06/2012 11:16 Karli Sjöberg said the following:
Hi!
I am a storage-technician working at the Swedish University of Agriculture
and we are using zfs-snapshot-mgmt to create scheduled snapshots, but are
failing on our disaster-recovery machine because of:
/usr/local/bin/zfs-snapshot-mgmt:130:in `join': can't convert nil into
String
(TypeError)
from /usr/local/bin/zfs-snapshot-mgmt:130:in `snapshots'
from /usr/local/bin/zfs-snapshot-mgmt:137:in `snapshots_to_remove'
from /usr/local/bin/zfs-snapshot-mgmt:145:in `remove_snapshots'
from /usr/local/bin/zfs-snapshot-mgmt:213
from /usr/local/bin/zfs-snapshot-mgmt:210:in `each'
from /usr/local/bin/zfs-snapshot-mgmt:210
Now, since this is a disaster-recovery unit, I would rather not have to have
all filesystems mounted for the script to function as we have many servers
with many file systems backing up towards this unit, which would result in
quite alot of mounts that are completely unnecessary to the backup server
itself. I also consider it a potential security risk having all these file
systems, from all of these different machines mounted in the same
place(server). I mean, if someone would like to steal as much valuable data
as possible, why crack hundreds of servers and steal it piece by piece when
you could just crack one and have it all, right? That doesn´t really make
sense because if someone were to crack the backup server they could just
mount all filesystems themselves, but only if they knew they were there. But
also having them mounted feels like just handing it to them.
Unfortunately I know nothing about programming so I can´t be of any help,
besides testing patches, but do you think this can be done? Change the
script
so that it doesn´t require the file systems to be mounted for it to be able
to take snapshots?
How about this?
--- zfs-snapshot-mgmt2010-06-02 05:31:28.759931924 +0300
+++ zfs-snapshot-mgmt2010-06-01 01:49:46.665034414 +0300
@@ -127,8 +127,10 @@
end
def snapshots(prefix)
-path = File.join(@mount_point, '.zfs', 'snapshot')
-Dir.open(path).select do |name|
+#path = File.join(@mount_point, '.zfs', 'snapshot')
+#Dir.open(path).select do |name|
+s = IO.popen('zfs list -r -t snapshot -H -o name ' +
@name).readlines.collect.select { |item| item[0, @name.length + 1] == @name +
'@' }.map { |item| item[@name.length + 1 .. -1] }
+s.select do |name|
name[0, prefix.length] == prefix
end.map { |name| SnapshotInfo.new(name, @name, prefix) }
end
--
Andriy Gapon
Med Vänliga Hälsningar
---
Karli Sjöberg
Swedish University of Agricultural Sciences
Box 7079 (Visiting Address Kronåsvägen 8)
S-750 07 Uppsala, Sweden
Phone: +46-(0)18-67 15 66
karli.sjob...@slu.se mailto:karli.sjob...@adm.slu.se
--
Andriy Gapon
Re: RFE - FreeBSD Port: zfs-snapshot-mgmt-20090201_2
on 28/06/2012 11:16 Karli Sjöberg said the following:
Hi!
I am a storage-technician working at the Swedish University of Agriculture
and we are using zfs-snapshot-mgmt to create scheduled snapshots, but are
failing on our disaster-recovery machine because of:
/usr/local/bin/zfs-snapshot-mgmt:130:in `join': can't convert nil into String
(TypeError)
from /usr/local/bin/zfs-snapshot-mgmt:130:in `snapshots'
from /usr/local/bin/zfs-snapshot-mgmt:137:in `snapshots_to_remove'
from /usr/local/bin/zfs-snapshot-mgmt:145:in `remove_snapshots'
from /usr/local/bin/zfs-snapshot-mgmt:213
from /usr/local/bin/zfs-snapshot-mgmt:210:in `each'
from /usr/local/bin/zfs-snapshot-mgmt:210
Now, since this is a disaster-recovery unit, I would rather not have to have
all filesystems mounted for the script to function as we have many servers
with many file systems backing up towards this unit, which would result in
quite alot of mounts that are completely unnecessary to the backup server
itself. I also consider it a potential security risk having all these file
systems, from all of these different machines mounted in the same
place(server). I mean, if someone would like to steal as much valuable data
as possible, why crack hundreds of servers and steal it piece by piece when
you could just crack one and have it all, right? That doesn´t really make
sense because if someone were to crack the backup server they could just
mount all filesystems themselves, but only if they knew they were there. But
also having them mounted feels like just handing it to them.
Unfortunately I know nothing about programming so I can´t be of any help,
besides testing patches, but do you think this can be done? Change the script
so that it doesn´t require the file systems to be mounted for it to be able
to take snapshots?
How about this?
--- zfs-snapshot-mgmt 2010-06-02 05:31:28.759931924 +0300
+++ zfs-snapshot-mgmt 2010-06-01 01:49:46.665034414 +0300
@@ -127,8 +127,10 @@
end
def snapshots(prefix)
-path = File.join(@mount_point, '.zfs', 'snapshot')
-Dir.open(path).select do |name|
+#path = File.join(@mount_point, '.zfs', 'snapshot')
+#Dir.open(path).select do |name|
+s = IO.popen('zfs list -r -t snapshot -H -o name ' +
@name).readlines.collect.select { |item| item[0, @name.length + 1] == @name +
'@' }.map { |item| item[@name.length + 1 .. -1] }
+s.select do |name|
name[0, prefix.length] == prefix
end.map { |name| SnapshotInfo.new(name, @name, prefix) }
end
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
