ake: stopped in /usr/ports/shells/bash
> (bash)5025}
>
>> On Jul 8, 2020, at 5:33 PM, Michael Butler
>> wrote:
>>
>> Did the bmake update break the updating of ports or something else?
>>
>> # sudo -E portmaster -a
>> ===>>> Gathering disti
Did the bmake update break the updating of ports or something else?
# sudo -E portmaster -a
===>>> Gathering distinfo list for installed ports
===>>> Starting check of installed ports for available updates
make: "/usr/ports/Mk/Uses/python.mk" line 384: warning: Strin
te break the updating of ports or something else?
>
> # sudo -E portmaster -a
> ===>>> Gathering distinfo list for installed ports
>
> ===>>> Starting check of installed ports for available updates
> make: "/usr/ports/Mk/Uses/python.mk" line 384: wa
On 04/05/2014 09:46, Marc UBM wrote:
> After my last port rebuild (libxml, libxcb, etc.) I realized that
> portmaster is still populating /var/db/pkg with the old db scheme (i.e.
> one directory for each port). At the same time, local.sqlite exists and
> is up to date (I can query th
; > > couple of ports like lang/perl5.16, then portmaster compiles, installs
> > > and - corrupt the port-system, because it tries to "lstat" files it can
> > > not find and ends up at the end of an unfinished installation. This
> > > leaves the entry i
On Thu, Oct 03, 2013 at 02:17:34PM +0200, O. Hartmann wrote:
> When NO_STAGE=yes is missing in the port's Makefile, as it is for a
> couple of ports like lang/perl5.16, then portmaster compiles, installs
> and - corrupt the port-system, because it tries to "lstat" files it
When NO_STAGE=yes is missing in the port's Makefile, as it is for a
couple of ports like lang/perl5.16, then portmaster compiles, installs
and - corrupt the port-system, because it tries to "lstat" files it can
not find and ends up at the end of an unfinished installation. This
l
wiyh this programs protupograde and portmaster.
In the last weekend, I updated my src and ports dirs and in the
/usr/ports/UPDATING have this message:
8<= Cut
20130929:
AFFECTS: users of x11/pixman
AUTHOR: zeis...@freebsd.org
The library version of x11/pixman has changed, and
Le 17/09/2013 10:35, Daniel Nebdal a écrit :
> Is it still required to add WITH_PKGNG=YES to /etc/make.conf to get
> pkgng support in portmaster, or is that default in 10 / now?
It's default.
--
Florent Peterschmitt | Please:
flor...@peterschmitt.fr| * Avoid HT
gt;> please? Or is better to use something different?
>>
>> Portmaster works for me on FreeBSD 10-CURRENT. Be sure to use an
>> up-to-date ports tree and install an up-to-date portmaster.
>>
>
> Mitja
>
> http://www.redbubble.com/people/lumiwa
>
Is it still
Thank ou.
On Sep 16, 2013, at 7:15 PM, Matthias Andree wrote:
> Am 17.09.2013 01:04, schrieb ajtiM:
>> Again me…
>> I was (am) long postmaster user. Is it possible to use on FreeBSD 10 too,
>> please? Or is better to use something different?
>
> Portmaster works f
Am 17.09.2013 01:04, schrieb ajtiM:
> Again me…
> I was (am) long postmaster user. Is it possible to use on FreeBSD 10 too,
> please? Or is better to use something different?
Portmaster works for me on FreeBSD 10-CURRENT. Be sure to use an
up-to-date ports tree and install an u
Again me…
I was (am) long postmaster user. Is it possible to use on FreeBSD 10 too,
please? Or is better to use something different?
Thank in advance.
Mitja
http://www.redbubble.com/people/lumiwa
___
freebsd-current@freebsd.org mailing list
http:
Am 03/06/13 18:32, schrieb Jan Beich:
> "Hartmann, O." writes:
>
>> *** [do-extract] Signal 13
>
> I have the same issue but it usually happens on `make install'.
> And reverting r247804 seems to be the workaround. Can you confirm?
I went back as far as r247479 and everything is perfect as i
"Hartmann, O." writes:
> *** [do-extract] Signal 13
I have the same issue but it usually happens on `make install'.
And reverting r247804 seems to be the workaround. Can you confirm?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
fails to start so X11
>> is without mouse.
>>
>> Trying to rebuild the port dbus fails in a SIGNAL 13 while [do-extract].
>>
>> This is weird. I can not extract and rebuild ports anymore, every port I
>> try to rebuild with portmaster fails with the very
fails to start so X11
>> is without mouse.
>>
>> Trying to rebuild the port dbus fails in a SIGNAL 13 while [do-extract].
>>
>> This is weird. I can not extract and rebuild ports anymore, every port I
>> try to rebuild with portmaster fails with the very
in a SIGNAL 13 while [do-extract].
This is weird. I can not extract and rebuild ports anymore, every port I
try to rebuild with portmaster fails with the very same fault:
=> SHA256 Checksum OK for dbus-1.4.14.tar.gz.
*** [do-extract] Signal 13
This is SIGPIPE, so maybe your tar is broken? W
weird. I can not extract and rebuild ports anymore, every port I
try to rebuild with portmaster fails with the very same fault:
=> SHA256 Checksum OK for dbus-1.4.14.tar.gz.
*** [do-extract] Signal 13
Stop in /usr/ports/devel/dbus.
===>>> make failed for devel/dbus
===>>> A
Hello,
Concerning the new pkg system, I reckon that my port updates can take a
drought.
Would it be best to deinstall portmaster for now? Portmaster typically
updates itself, but this might be a special case.
Currently, my postmaster run ends like this:
===>>> Cannot continue
===>
On 10/16/2012 8:00 AM, Pavel Timofeev wrote:
> Hi! Thank you for this extremely perfect work!
> I've found a small inaccuracy when I use portmaster with pkgng (WITH_PKGNG
> in /etc/make.conf and use_pkgng in portmaster.rc).
> In such case portmaster still fills
> /v
On Mon, 15 Oct 2012, Darrel wrote:
Would it be best to deinstall portmaster for now? Portmaster typically
updates itself, but this might be a special case.
I got it:
# cd /usr/port/ports-mgmt/portmaster
# make deinstall
# make rmconfig
# make reinstall
- select pkgngpatch > O
On 15/10/2012 18:13, Darrel wrote:
> Hello,
>
> Concerning the new pkg system, I reckon that my port updates can take a
> drought.
>
> Would it be best to deinstall portmaster for now? Portmaster typically
> updates itself, but this might be a special case.
>
> C
Hello,
Concerning the new pkg system, I reckon that my port updates can take a
drought.
Would it be best to deinstall portmaster for now? Portmaster typically
updates itself, but this might be a special case.
Currently, my postmaster run ends like this:
===>>> Cannot
I can not anymore install or reinstall (using portmaster, patched for
>> pkgng) the ports
>>
>> security/cyrus-sasl2
>> net/openldap24-client
>>
>> When performing an update (no matter which one), The installation
>> process dies when installing the p
On 8/18/2012 4:07 AM, O. Hartmann wrote:
My setups on all boxes using OpenLDAP, the port
net/opendldap24-client/server has security/cyrus-sasl2 enabled.
I use nsswitch and nascd.
The problem:
I can not anymore install or reinstall (using portmaster, patched for
pkgng) the ports
security/cyrus
o problems so far.
Well, the issue:
The setup:
My setups on all boxes using OpenLDAP, the port
net/opendldap24-client/server has security/cyrus-sasl2 enabled.
I use nsswitch and nascd.
My systems are all compiled using CLANG.
The problem:
I can not anymore install or reinstall (using portmaste
s precise I can be without the exact terminology!).
>
>> An installation failed due to pkg(ng) was missing libarchive.so via
>> portmaster or via core dumping install(1). By installing on one box, my
>> home box, port security/cyrus-sasl2 manually, luckily install(1) and
>
On Fri, Aug 17, 2012 at 09:44:40AM +0200, Hartmann, O. wrote:
> >> An installation failed due to pkg(ng) was missing libarchive.so via
> >
> > There is pkg-static for recovering in this type of situation.
>
> Oh ... I'm new to pkg(ng).
>
No worries. It is a nice thing to know about, since afte
y, r239295 Wed August 15 17:04:51 CEST 2012
>> amd64, I had to recompile all requirements of port Apache22, since after
>> the port update it core dumped.
>>
>> On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and
>> installation of all "portmaste
; SIGNAL 11. Booting into multiuser mode is impossible, login core dumps
> SIGNAL 11, many other daemons, too. The only way is to boot into single
> user mode.
I'm not drawing a correlation between this and unrelated coredumping processes.
> An installation failed due to pkg(ng) was m
On Thu, Aug 16, 2012 at 11:33 AM, O. Hartmann
wrote:
> I ran into a very delicate and nasty situation.
Please don't cross-post / double-post.
Thanks,
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and
installation of all "portmaster -f apache-2.2" requirements went perfect.
On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a
sudden(!), while reinstalling port security/cyrus-sasl2, things started
to fail in
On 8/16/2012 10:33 AM, Hartmann, O. wrote:
> I tried to find rescue images and a rescue DVD of a snap shot server,
> but there is no way to crawl through the informations on the web pages
> towards a snapshot. All folders end up in 2011 and highly outdated
> (www.freebsd.org, I didn't look at mirro
d to recompile all requirements of port Apache22, since after
> the port update it core dumped.
>
> On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and
> installation of all "portmaster -f apache-2.2" requirements went perfect.
>
> On both FreeBSD 10
FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and
installation of all "portmaster -f apache-2.2" requirements went perfect.
On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a
sudden(!), while reinstalling port security/cyrus-sasl2, things started
to
On 8/9/2012 8:26 AM, Chris Rees wrote:
> On 7 Aug 2012 15:50, "O. Hartmann" wrote:
>>
>> On 08/07/12 15:39, Bryan Drewery wrote:
>>> On 8/7/2012 4:31 AM, O. Hartmann wrote:
>>>> ports-mgmt/portmaster installs still the old fashioned style folders o
2012/8/9 Chris Rees :
> On 7 Aug 2012 15:50, "O. Hartmann" wrote:
>>
>> On 08/07/12 15:39, Bryan Drewery wrote:
>> > On 8/7/2012 4:31 AM, O. Hartmann wrote:
>> >> ports-mgmt/portmaster installs still the old fashioned style folders of
>> >
On 7 Aug 2012 15:50, "O. Hartmann" wrote:
>
> On 08/07/12 15:39, Bryan Drewery wrote:
> > On 8/7/2012 4:31 AM, O. Hartmann wrote:
> >> ports-mgmt/portmaster installs still the old fashioned style folders of
> >> ports in /var/db/pkg. I thought ith the new
On 8/7/2012 4:31 AM, O. Hartmann wrote:
> ports-mgmt/portmaster installs still the old fashioned style folders of
> ports in /var/db/pkg. I thought ith the new scheme of pkg, everything is
> going into a file based SQLite3 DB?
Also ensure WITH_PKGNG=yes is in your /etc/make.conf. My las
On 8/7/2012 4:31 AM, O. Hartmann wrote:
> Hello.
> I tried to switch to the new tool pkg. I'm still installing my ports via
> sources and compiling, but I appreciate the more stable dependency
> tracking of pkg(ng).
> Therefore, I patched, as reuqired and recommended, ports-mgm
Hello.
I tried to switch to the new tool pkg. I'm still installing my ports via
sources and compiling, but I appreciate the more stable dependency
tracking of pkg(ng).
Therefore, I patched, as reuqired and recommended, ports-mgmt/portmaster.
I performed a portmaster --check-depends after
On 23/07/2012 10:31, Hartmann, O. wrote:
> portmaster now is not recognizing anymore the format of the /var/db/pkg
> folder - for those considered the knowledged no surprise, for me simply
> the indication that portmaster usage isn't usable as usual.
You need to patch portmaster s
On 23/07/2012 09:43, Hartmann, O. wrote:
> I'd like to try pkgng with portmaster. I see that "pkg2ng" is involving
> the directory /var/db/pkg, so this implies that there may implications
> also for usage with ports-mgmt/portmaster. portmaster is supposed to be
> the t
On 23/07/2012 09:43, Hartmann, O. wrote:
> Hello.
>
> I'd like to try pkgng with portmaster. I see that "pkg2ng" is involving
> the directory /var/db/pkg, so this implies that there may implications
> also for usage with ports-mgmt/portmaster. portmaster is suppos
On 07/23/12 11:07, Chris Rees wrote:
> On 23 Jul 2012 09:44, "Hartmann, O." wrote:
>>
>> Hello.
>>
>> I'd like to try pkgng with portmaster. I see that "pkg2ng" is involving
>> the directory /var/db/pkg, so this implies that there may
On 23 Jul 2012 09:44, "Hartmann, O." wrote:
>
> Hello.
>
> I'd like to try pkgng with portmaster. I see that "pkg2ng" is involving
> the directory /var/db/pkg, so this implies that there may implications
> also for usage with ports-mgmt/portmast
Hello.
I'd like to try pkgng with portmaster. I see that "pkg2ng" is involving
the directory /var/db/pkg, so this implies that there may implications
also for usage with ports-mgmt/portmaster. portmaster is supposed to be
the tool completely dependend on system's toolsets, is
48 matches
Mail list logo
