Re: New Flask ports: Flask-Moment, Flask-Mail, Flask-SAML, Flask-Kerberos

[John W. O'Brien]

On 2018/03/01 23:04, John W. O'Brien wrote:
> These new ports have not gotten any committer love for some time. I
> would appreciate any feedback or to have them added to the ports tree.
[...]
> 2017-12-26
> www/py-flask-moment
> https://bugs.freebsd.org/224587
>
> 2017-12-26
> mail/py-flask-mail
> https://bugs.freebsd.org/224588
> 
> 2018-01-16
> security/py-flask-kerberos
> https://bugs.freebsd.org/225199
> 
> 2018-01-16
> security/py-flask-saml
> https://bugs.freebsd.org/225202

Hello all,

Please excuse the cross-posting, but these new ports have not gotten any
attention from freebsd-python@ so I'm expanding the call for committers
to freebsd-ports@.

-- 
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B



signature.asc
Description: OpenPGP digital signature

Re: zsh 5.5: core dump during serial login

[Dr. Peter Voigt]

On Mon, 16 Apr 2018 12:56:45 +0200
Baptiste Daroussin  wrote:

> On Sun, Apr 15, 2018 at 12:33:08AM +0200, Dr. Peter Voigt wrote:
> > Today I upgraded shells/zsh to version 5.5 on my FreeBSD
> > 11.1-RELEASE-p9 machine.
> > 
> > During a login over serial line (wired or IPMI-SOL) I am immediately
> > kicked out after a successful login. Syslogd shows:
> > 
> >  xxx kernel: pid xxx (zsh), uid 0: exited on signal 8
> > (core dumped)
> > 
> > I immediately downgraded to zsh-5.4.2_1 and the error disappeared.
> > 
> > Is this a known error or should I created a ticket under
> > https://bugs.freebsd.org/  
> 
> I have never heard of that error, so yes I would like a bug report
> please
> 
> Best regards,
> Bapt

Bug ticket created:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227565

I hope the issue can be reproduced and fixed as soon as possible. I am
currently using downgraded zsh-5.4.2_1 while having the package in hold
status.

Regards,
Peter



pgpPLlHcgYkXA.pgp
Description: OpenPGP digital signature

Re: Conflicts due to renamed KDE4 ports

[Stefan Esser]

Am 16.04.18 um 21:13 schrieb Tijl Coosemans:
> On Mon, 16 Apr 2018 20:11:33 +0200 Stefan Esser  wrote:
>> When not even pkg can deal with this situation, how should portmaster?
>>
>> The packages are built without consideration for the requirements of a
>> running system, and pkg sees all the meta-information of all installed
>> packages and the one being processed and can e.g. see, that files will
>> conflict (which portmaster can only do after completely building the
>> port, which means that this is long after the decision to use that port
>> has been required).
>>
>>
>> The lack of consideration given by port maintainers is quite frustrating,
>> since it requires a lot of effort to work around the issues caused.
> 
> Like I said, IMHO it's not your problem, so you don't need to work around
> it and you don't have to feel frustrated by it.  Without an entry in MOVED
> there's no way for portmaster or pkg to know that the old akonadi needs to
> be replaced with akonadi-kde4.  If any user contacts you about this you
> can forward them to kde@ because they created the problem.
> 
> IMHO, entries in MOVED should stay for at least a year, if not several
> years, so kde@ should restore the kde4 MOVED entries and give the kde5
> ports a -kde5 suffix or something.  Hopefully there aren't that many users
> yet because you can't create MOVED entries for this move.

Seems that I misunderstood your reply ...

Yes, adding -kde5 to all ports that have got origins previously used for
KDE4 ports, and MOVED entries for those KDE4 ports would solve the issue.

It would have helped, if either port origin or package name of the KDE4
ports had been kept, since that would have allowed to link the ports and
packages over the change by the unchanged attribute.

The absolute minimum would have been a complete set of "pkg set -o" commands
to adjust the registered origins of all affected and installed KDE4 ports in
an UPDATING entry.

I'm not sure that poudriere can create packages that let pkg upgrade succeed
without file conflicts, unless the relation is revealed by the MOVED entries.


So, I agree with your proposal (previously also suggested by me) of MOVED
entries for the KDE4 ports and new non-conflicting origins for those KDE5
ports that re-use the previous KDE4 origins (obviously without MOVED entries,
but since the package names (without the version) remain unchanged for those
KDE5 ports, automatic port and package upgrades can work for them.

Regards, STefan
___
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"

magic syntax for most recent git from sourceforge?

[Gary Aitken]

Can anyone give me the magic formula for fetching the most recent git
distro from sourceforge for a ports Makefile?

The porter's handbook talks about how to fetch git repos from github
but not about how to get them from sourceforge.

I've tried a few things but can't get the right combo of MASTER_SITES
and PORTNAME, DISTFILE, and DISTVERSION

The git clone cmd is:
  git clone https://git.code.sf.net/p/nufraw/git nufraw-git

This particular git version says it is 0.41 but attempting to fetch
with from
  PORTVERSION=0.41
  MASTER_SITES=   https://sourceforge.net/projects/nufraw/files/latest/
doesn't work; PORTVERSION=  0.40 does.
I've also tried with
  DISTVERSION=07ebb73a
with no joy.

Thanks,

Gary
___
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: Conflicts due to renamed KDE4 ports

[Tijl Coosemans]

On Mon, 16 Apr 2018 20:11:33 +0200 Stefan Esser  wrote:
> Am 16.04.18 um 12:38 schrieb Tijl Coosemans:
>> On Sat, 14 Apr 2018 14:18:22 +0200 Stefan Esser  wrote:  
>>> The way the new KDE5/KF5 ports have been introduced a few weeks back has
>>> caused me quite some effort (more than 100 hours of work), and now there
>>> have been further changes to implement KDE5 support (which I generally
>>> appreciate), which cause further complications and seem not to be well
>>> thought out.
>>>
>>> These problems affect at least all portmaster users, but I guess portupgrade
>>> is affected as well and a "pkg upgrade" dry-run indicates, that it will also
>>> cause breakage to binary upgrades of KDE4 installations.  
>> 
>> Removing entries from MOVED after only a few weeks is a bad idea, but
>> it's not something you have to worry about.  As long as portmaster
>> behaves more or less the same as pkg you're good.  
> 
> I only tried a dry run, but it appears, that pkg does not deal with this
> situation correctly. Grzegorz Junka reported, that it did not work for
> him and he had to manually delete all KDE ports and re-install them from
> his repository built with poudriere.
> 
> 
> A correct decision is impossible given on the information in the ports.
> 
> It is correct to upgrade e.g. databases/akonadi (akonadi-1.13.0_6) to
> databases/akonadi-kde4 (akonadi-kde4-1.13.0_7), but neither the origin
> nor package name nor a MOVED entry provide that information.
> 
> It is not correct to replace databases/akonadi (akonadi-1.13.0_6) by
> databases/akonadi (akonadi-17.12.3), but this can only be seen by
> checking the forward and backward dependencies (which are for KDE5/QT5
> instead of KDE4/QT4 of the installed port).
> 
> The same considerations applied to another port may lead to different
> results. While pkg requires exact dependencies to be installed, it is
> possible to use alternatives to satisfy dependencies with portmaster.
> And this feature is heavily used, e.g. to use a different version of
> samba than the default hard-wired into package dependencies. But this
> flexibility needs a basis for deciding, whether such a replacement is
> valid and how to perform upgrades in that situation.
> 
> 
> If akonadi is installed only as a dependency of other ports, then pkg will
> install the akonadi-kde4 version. But since the old version is installed
> as an in-use dependency of other KDE4 ports, it will not be removed before
> the installation of the new version is attempted (which will lead to an
> install conflict, since files of an installed port are to be overwritten).
> 
> It is possible to manually and forcefully delete akonadi-1.13.0_6 before
> starting pkg upgrade for the KDE4 ports that depend on it. In that case,
> there is no conflict. But pkg autodelete cannot be used, since to remove
> the dependency on the old version, the (conflicting) new version must be
> registered in the ports that depend on akonadi.
> 
> If akonadi has been directly installed and not (only) as a dependency,
> the akonadi-17.12.3 will be considered to be an upgrade of akonadi-1.13.*
> (same origin and same package name, except for the version numbers). This
> will remove the required dependency from the KDE4 ports and will register
> the KDE5 version as new dependency of those ports (although it completely
> useless in that role).
> 
> 
> When not even pkg can deal with this situation, how should portmaster?
> 
> The packages are built without consideration for the requirements of a
> running system, and pkg sees all the meta-information of all installed
> packages and the one being processed and can e.g. see, that files will
> conflict (which portmaster can only do after completely building the
> port, which means that this is long after the decision to use that port
> has been required).
> 
> 
> The lack of consideration given by port maintainers is quite frustrating,
> since it requires a lot of effort to work around the issues caused.

Like I said, IMHO it's not your problem, so you don't need to work around
it and you don't have to feel frustrated by it.  Without an entry in MOVED
there's no way for portmaster or pkg to know that the old akonadi needs to
be replaced with akonadi-kde4.  If any user contacts you about this you
can forward them to kde@ because they created the problem.

IMHO, entries in MOVED should stay for at least a year, if not several
years, so kde@ should restore the kde4 MOVED entries and give the kde5
ports a -kde5 suffix or something.  Hopefully there aren't that many users
yet because you can't create MOVED entries for this move.
___
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: Conflicts due to renamed KDE4 ports

[Stefan Esser]

Am 16.04.18 um 12:38 schrieb Tijl Coosemans:
> On Sat, 14 Apr 2018 14:18:22 +0200 Stefan Esser  wrote:
>> The way the new KDE5/KF5 ports have been introduced a few weeks back has
>> caused me quite some effort (more than 100 hours of work), and now there
>> have been further changes to implement KDE5 support (which I generally
>> appreciate), which cause further complications and seem not to be well
>> thought out.
>>
>> These problems affect at least all portmaster users, but I guess portupgrade
>> is affected as well and a "pkg upgrade" dry-run indicates, that it will also
>> cause breakage to binary upgrades of KDE4 installations.
> 
> Removing entries from MOVED after only a few weeks is a bad idea, but
> it's not something you have to worry about.  As long as portmaster
> behaves more or less the same as pkg you're good.

I only tried a dry run, but it appears, that pkg does not deal with this
situation correctly. Grzegorz Junka reported, that it did not work for
him and he had to manually delete all KDE ports and re-install them from
his repository built with poudriere.


A correct decision is impossible given on the information in the ports.

It is correct to upgrade e.g. databases/akonadi (akonadi-1.13.0_6) to
databases/akonadi-kde4 (akonadi-kde4-1.13.0_7), but neither the origin
nor package name nor a MOVED entry provide that information.

It is not correct to replace databases/akonadi (akonadi-1.13.0_6) by
databases/akonadi (akonadi-17.12.3), but this can only be seen by
checking the forward and backward dependencies (which are for KDE5/QT5
instead of KDE4/QT4 of the installed port).

The same considerations applied to another port may lead to different
results. While pkg requires exact dependencies to be installed, it is
possible to use alternatives to satisfy dependencies with portmaster.
And this feature is heavily used, e.g. to use a different version of
samba than the default hard-wired into package dependencies. But this
flexibility needs a basis for deciding, whether such a replacement is
valid and how to perform upgrades in that situation.


If akonadi is installed only as a dependency of other ports, then pkg will
install the akonadi-kde4 version. But since the old version is installed
as an in-use dependency of other KDE4 ports, it will not be removed before
the installation of the new version is attempted (which will lead to an
install conflict, since files of an installed port are to be overwritten).

It is possible to manually and forcefully delete akonadi-1.13.0_6 before
starting pkg upgrade for the KDE4 ports that depend on it. In that case,
there is no conflict. But pkg autodelete cannot be used, since to remove
the dependency on the old version, the (conflicting) new version must be
registered in the ports that depend on akonadi.

If akonadi has been directly installed and not (only) as a dependency,
the akonadi-17.12.3 will be considered to be an upgrade of akonadi-1.13.*
(same origin and same package name, except for the version numbers). This
will remove the required dependency from the KDE4 ports and will register
the KDE5 version as new dependency of those ports (although it completely
useless in that role).


When not even pkg can deal with this situation, how should portmaster?

The packages are built without consideration for the requirements of a
running system, and pkg sees all the meta-information of all installed
packages and the one being processed and can e.g. see, that files will
conflict (which portmaster can only do after completely building the
port, which means that this is long after the decision to use that port
has been required).


The lack of consideration given by port maintainers is quite frustrating,
since it requires a lot of effort to work around the issues caused.

Regards, STefan
___
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: Please commit 227261

[Kurt Jaeger]

Hi!

> The bug has a maintainer-approved patch since April 3. Would someone 
> please commit this change? Thanks.

Done.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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"

Please commit 227261

[Mel Pilgrim]

The bug has a maintainer-approved patch since April 3. Would someone 
please commit this change? Thanks.

___
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: Some KDE4 desktop effects not working after pkg upgrade

[Mike Clarke]

On Monday 16 April 2018 10:28:42 Greg Rivers wrote:

> I reported the same issue on the FreeBSD KDE mailing list the other day:
> 
> 
> No responses yet.

Thanks for the info, I'll keep an eye on that thread in the FreeBSD KDE list.

-- 
Mike Clarke
___
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: Some KDE4 desktop effects not working after pkg upgrade

[Greg Rivers]

On Monday, April 16, 2018 15:12:49 Mike Clarke wrote:
> Yesterday's run of pkg upgrade appeared to work OK with 111 packages
> affected, except that i now find that most of my KDE desktop effects no
> longer work, ...
>
I reported the same issue on the FreeBSD KDE mailing list the other day:


No responses yet.

-- 
Greg Rivers
___
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: Removal of www/apache22

[Bernard Spil]

Hi All,

I've pulled the trigger on the removal of www/apache22.
I've kept mod_memcache_blok but marked it BROKEN pending maintaner update.

Added bofh@ as resin3 is also affected (option, default disabled).

If the port does work with Apache 2.4 (or with a patch), let me know
so we can add it again.

Cheers, Bernard.

2018-04-12 9:50 GMT+02:00 Hung-Yi Chen :
> Hi,
>
> www/mod_memcache_block can work with apache 2.4.
>
> I'll send a PR.
>
>
> 2018-04-12 4:35 GMT+08:00 Philip M. Gollucci :
>>
>> mod_log_mysql ->
>> https://github.com/freebsd/freebsd-ports/blob/master/www/mod_log_sql
>>
>> On Wed, Apr 11, 2018 at 12:52 PM, Łukasz Wąsikowski
>>  wrote:
>>>
>>> W dniu 2018-04-11 o 20:29, Bernard Spil pisze:
>>>
>>> > You are all maintainer of a port that depends on www/apache22. The
>>> > Apache 2.2 port has been marked EXPIRED for almost a year. I was about
>>> > to delete it but didn't want to go ahead without informing you. My
>>> > analysis of the dependent ports can be found in the FreeBSD wiki
>>> > https://wiki.freebsd.org/Apache#Apache_2.2
>>>
>>> [...]
>>>
>>> > www/mod_macro22 luk...@wasikowski.net
>>>
>>> This is apache 2.2 only version. Feature provided by this port is
>>> included in apache 2.4 , so feel free to bury www/mod_macro22.
>>>
>>> --
>>> best regards,
>>> Lukasz Wasikowski
>>> ___
>>> freebsd-apa...@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-apache
>>> To unsubscribe, send any mail to "freebsd-apache-unsubscr...@freebsd.org"
>>
>>
>>
>>
>> --
>>
>> -
>> 4096R/D21D2752 ECDF B597 B54B 7F92 753E  E0EA F699 A450 D21D 2752
>> Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354
>> Member,   Apache Software Foundation
>> Committer,FreeBSD Foundation
>> Consultant,   P6M7G8 Inc.
>> Director Cloud Technology,Capital One
>>
>> What doesn't kill us can only make us stronger;
>> Except it almost kills you.
>
>
___
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"

Some KDE4 desktop effects not working after pkg upgrade

[Mike Clarke]

Yesterday's run of pkg upgrade appeared to work OK with 111 packages affected, 
except that i now find that most of my KDE desktop effects no longer work, e.g. 
Taskbar Thumbnails, Cover Switch, Desktop Grid and Present Windows. These are 
all just eye candy so not a showstopper but it would be nice if I could get 
them working again.

I'm running on a Gigabyte Z97P-D3 motherboard and Intel i5 4460 with integrated 
graphics. 

KDE desktop effects are configured to use OpenGL3.1 compositing and Native 
graphics system and all the effects worked fine with that setting before the 
last upgrade.

Here's a list of all the packages affected by the upgrade:

-
The following 111 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
qjson-qt4: 0.9.0_2
polkit-qt4: 0.112.0_1
qca-qt4: 2.1.3_1
qca-qt5: 2.1.3_1
kf5-kinit: 5.44.0
kf5-kdelibs4support: 5.44.0
kf5-kded: 5.44.0
kf5-kdesignerplugin: 5.44.0
qt5-webkit: 5.212.0.a2_7
qt5-quick: 5.9.4_1
qt5-xmlpatterns: 5.9.4_1
qt5-sql: 5.9.4_1
qt5-webchannel: 5.9.4_1
gstreamer1-plugins-core: 1.12
gstreamer1-plugins-pango: 1.12.3
gstreamer1-plugins-ugly: 1.12.3
gstreamer1-plugins-theora: 1.12.3
gstreamer1-plugins-resindvd: 1.12.3
gstreamer1-plugins-dvdread: 1.12.3
gstreamer1-plugins-dts: 1.12.3
gstreamer1-libav: 1.12.3_1
gstreamer1-plugins-png: 1.12.3
gstreamer1-plugins-vorbis: 1.12.3
gstreamer1-plugins-ogg: 1.12.3
gstreamer1-plugins-mpg123: 1.12.3
mpg123: 1.25.10
gstreamer1-plugins-a52dec: 1.12.3
qt5-location: 5.9.4_1
qt5-sensors: 5.9.4_1
kf5-kdewebkit: 5.44.0
kf5-kplotting: 5.44.0
qt5-designer: 5.9.4_4
qt5-assistant: 5.9.4_1
qt5-help: 5.9.4_1
qt5-sqldrivers-sqlite3: 5.9.4
kf5-kemoticons: 5.44.0
kf5-kunitconversion: 5.44.0
kf5-kitemmodels: 5.44.0
qt5-webengine: 5.9.4_1
libsrtp: 1.6.0
kcontacts: 17.12.3
kcalcore: 17.12.3
libkgapi-kde4: 2.2.0_5
libktorrent-kde4: 1.3.1_18
kf5-knotifyconfig: 5.44.0
kf5-knewstuff: 5.44.0
kf5-kfilemetadata: 5.44.0
poppler-qt5: 0.57.0_1
kf5-kcmutils: 5.44.0
kf5-kpackage: 5.44.0
kf5-kdeclarative: 5.44.0
libkcddb: 17.12.3
p5-Mojolicious: 7.75
p5-EV: 4.22,1
p5-common-sense: 3.74

Installed packages to be UPGRADED:
wireshark: 2.4.5 -> 2.4.6
sqlite3: 3.22.0_2 -> 3.23.0
qt5-gui: 5.9.4_3 -> 5.9.4_4
qoauth: 2.0.0 -> 2.0.0_1
py27-pytz: 2018.3,1 -> 2018.4,1
poppler-glib: 0.57.0 -> 0.57.0_1
poppler: 0.57.0 -> 0.57.0_1
polkit-qt5: 0.112.0 -> 0.112.0_1
polkit-kde: 0.99.1_5 -> 0.99.1_6
p5-Crypt-OpenSSL-Random: 0.11 -> 0.12
okular-kde4: 4.14.3_11 -> 4.14.3_12
okteta-kde4: 4.14.3_4 -> 4.14.3_5
nss: 3.36 -> 3.36.1
mysql56-server: 5.6.39_2 -> 5.6.39_3
mysql56-client: 5.6.39_2 -> 5.6.39_3
mesa-libs: 17.3.1 -> 18.0.0
mesa-dri: 17.3.1_1 -> 18.0.0
libreoffice: 6.0.2_3 -> 6.0.3
libnghttp2: 1.31.0 -> 1.31.1
libkvkontakte: 4.12.0_2 -> 4.12.0_3
libktorrent: 1.3.1_17 -> 2.1.0_1
libkscreen: 1.0.5_4 -> 1.0.5_5
libkgapi: 2.2.0_3 -> 17.12.3
libkfbapi: 1.0_6 -> 1.0_7
ksirk-kde4: 4.14.3_4 -> 4.14.3_5
kopete-kde4: 4.14.3_8 -> 4.14.3_10
kipi-plugin-yandexfotki: 4.14.0_2 -> 4.14.0_3
kipi-plugin-videoslideshow: 4.14.0_4 -> 4.14.0_5
kipi-plugin-shwup: 4.14.0_2 -> 4.14.0_3
kipi-plugin-imgurexport: 4.14.0_2 -> 4.14.0_3
kipi-plugin-googleservices: 4.14.0_2 -> 4.14.0_3
kipi-plugin-facebook: 4.14.0_2 -> 4.14.0_3
kipi-plugin-dropbox: 4.14.0_2 -> 4.14.0_3
kipi-plugin-debianscreenshots: 4.14.0_2 -> 4.14.0_3
kget-kde4: 4.14.3_11 -> 4.14.3_13
kf5-kauth: 5.44.0 -> 5.44.0_1
kdeplasma-addons-kde4: 4.14.3_9 -> 4.14.3_11
kdepimlibs-kde4: 4.14.10_18 -> 4.14.10_19
kdepim-runtime-kde4: 4.14.10_10 -> 4.14.10_12
kdepim-kde4: 4.14.10_12 -> 4.14.10_13
kdenetwork-kde4: 4.14.3_3 -> 4.14.3_5
kdelibs-kde4: 4.14.38_1 -> 4.14.38_3
kde-workspace-kde4: 4.11.22_18 -> 4.11.22_19
kde: 4.14.3_5 -> 4.14.3_7
kcm-polkit-kde: 0.0.20121008_5 -> 0.0.20121008_6
kate-kde4: 4.14.3_4 -> 4.14.3_5
k3b: 2.0.3_5 -> 17.12.3
gstreamer1-qt4: 1.2.0_9 -> 1.2.0_10
gnupg: 2.2.5 -> 2.2.6
get_iplayer: 3.01 -> 3.13
gcc6: 6.4.0_4 -> 6.4.0_5
en_GB-libreoffice: 6.0.2_3 -> 6.0.3
ca_root_nss: 3.36 -> 3.36.1
brotli: 1.0.2,1 -> 1.0.4,1
baloo-kde4: 4.14.3_8 -> 4.14.3_9
ark-kde4: 4.14.3_4 -> 

Re: zsh 5.5: core dump during serial login

[Baptiste Daroussin]

On Sun, Apr 15, 2018 at 12:33:08AM +0200, Dr. Peter Voigt wrote:
> Today I upgraded shells/zsh to version 5.5 on my FreeBSD 11.1-RELEASE-p9
> machine.
> 
> During a login over serial line (wired or IPMI-SOL) I am immediately
> kicked out after a successful login. Syslogd shows:
> 
>  xxx kernel: pid xxx (zsh), uid 0: exited on signal 8 (core dumped)
> 
> I immediately downgraded to zsh-5.4.2_1 and the error disappeared.
> 
> Is this a known error or should I created a ticket under
> https://bugs.freebsd.org/

I have never heard of that error, so yes I would like a bug report please

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: reccomendation for a building architecture schematic diagram editor ?

[blubee blubeeme]

You might try cad/brlcad


On Mon, Apr 16, 2018, 17:55 Julian Elischer  wrote:

> On 16/4/18 4:32 pm, Kurt Jaeger wrote:
> > Hi!
> >
> >> Only port I can think of is xfig, which I've used for other things
> >>  https://svnweb.freebsd.org/ports/head/graphics/xfig/
> >> but wondering if something else more appropriate exists ?
> > If I did drawings in the past, I used xfig. graphics/dia is also
> > usable. Then there's kdiagram, but I never used it.
> >
> one of the oldest drawing tools ever, tgif ...
>
> I find it way better than some newer, fancier packages.
>
>
> ___
> 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"
>
___
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: Conflicts due to renamed KDE4 ports

[Tijl Coosemans]

On Sat, 14 Apr 2018 14:18:22 +0200 Stefan Esser  wrote:
> The way the new KDE5/KF5 ports have been introduced a few weeks back has
> caused me quite some effort (more than 100 hours of work), and now there
> have been further changes to implement KDE5 support (which I generally
> appreciate), which cause further complications and seem not to be well
> thought out.
> 
> These problems affect at least all portmaster users, but I guess portupgrade
> is affected as well and a "pkg upgrade" dry-run indicates, that it will also
> cause breakage to binary upgrades of KDE4 installations.

Removing entries from MOVED after only a few weeks is a bad idea, but
it's not something you have to worry about.  As long as portmaster
behaves more or less the same as pkg you're good.
___
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: reccomendation for a building architecture schematic diagram editor ?

[Julian Elischer]

On 16/4/18 4:32 pm, Kurt Jaeger wrote:

Hi!


Only port I can think of is xfig, which I've used for other things
https://svnweb.freebsd.org/ports/head/graphics/xfig/
but wondering if something else more appropriate exists ?

If I did drawings in the past, I used xfig. graphics/dia is also
usable. Then there's kdiagram, but I never used it.


one of the oldest drawing tools ever, tgif ...

I find it way better than some newer, fancier packages.


___
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: reccomendation for a building architecture schematic diagram editor ?

[Tijl Coosemans]

On Mon, 16 Apr 2018 10:21:20 +0200 "Julian H. Stacey"  wrote:
> Hi po...@freebsd.org people,
> Might any of you have a FreeBSD ports/ reccomendation for a building
> architecture schematic diagram editor, please ? To plan eg big house room
> layouts { furniture moves, building sale / rent} etc ?
> 
> I'm not looking for professional architects or structural engineers
> tools to plan new buildings.  I'm not looking for millimetre precise
> kitchen layout programs if such exist, I'm just looking to produce
> the sort of plan one gets from estate agents, and on landlord/
> tenant rental contracts etc.
> 
> I searched, but nothing from https://www.freebsd.org/cgi/ports.cgi
> 
> Only port I can think of is xfig, which I've used for other things
>   https://svnweb.freebsd.org/ports/head/graphics/xfig/
> but wondering if something else more appropriate exists ?
> 
> Looking for something to tart up my hand sketches & a raft of
> measurements hand written on them, taken from a laser measurer.
> 
> I'm not looking to include a bluetooth professional laser measurer
> to PC/android data transfer, though they exist, I just bought a
> much cheaper simple laser measurer, & content to hand edit.

maybe cad/sweethome3d
___
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: reccomendation for a building architecture schematic diagram editor ?

[Kurt Jaeger]

Hi!

> Only port I can think of is xfig, which I've used for other things
>   https://svnweb.freebsd.org/ports/head/graphics/xfig/
> but wondering if something else more appropriate exists ?

If I did drawings in the past, I used xfig. graphics/dia is also
usable. Then there's kdiagram, but I never used it.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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"

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
multimedia/vdr-plugin-femon | 1.7.17  | 2.4.0
+-+
multimedia/vdr-plugin-iptv  | 1.0.1   | 2.4.0
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

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

reccomendation for a building architecture schematic diagram editor ?

[Julian H. Stacey]

Hi po...@freebsd.org people,
Might any of you have a FreeBSD ports/ reccomendation for a building
architecture schematic diagram editor, please ? To plan eg big house room
layouts { furniture moves, building sale / rent} etc ?

I'm not looking for professional architects or structural engineers
tools to plan new buildings.  I'm not looking for millimetre precise
kitchen layout programs if such exist, I'm just looking to produce
the sort of plan one gets from estate agents, and on landlord/
tenant rental contracts etc.

I searched, but nothing from https://www.freebsd.org/cgi/ports.cgi

Only port I can think of is xfig, which I've used for other things
https://svnweb.freebsd.org/ports/head/graphics/xfig/
but wondering if something else more appropriate exists ?

Looking for something to tart up my hand sketches & a raft of
measurements hand written on them, taken from a laser measurer.

I'm not looking to include a bluetooth professional laser measurer
to PC/android data transfer, though they exist, I just bought a
much cheaper simple laser measurer, & content to hand edit.

Cheers,
Julian
-- 
Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich
 Brexit Referendum stole 3,700,000 votes, inc. 700,000 from British in EU.
 UK Govt. lied it's "democratic" in Article 50 letter to EU paragraph 3.
Petition for votes: http://berklix.eu/queen/
___
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"