Re: net/qt5-network

[Tobias C. Berner]

Moin moin

As you see the Ignore-message, I would say that your make.conf is not
used by poudriere.


mfg Tobias

On Wed, 8 Jul 2020 at 13:10, Carmel NY  wrote:
>
> FreeBSD 11.4-RELEASE
>
> With a freshly updated ports tree, when I attempt to run poudriere to
> update the installed ports, I am greeted with this warning:
>
> [00:00:21] Ignoring net/qt5-network | qt5-network-5.15.0: is marked as 
> broken: Qt5 requires Openssl 1.1.1, upgrade to FreeBSD 12.x/13.x or add 
> DEFAULT_VERSIONS+=ssl=[openssl|libressl*] to /etc/make.conf
>
> Subsequently, 339 ports are skipped, and now I cannot get 'X' to start.
> I have "DEFAULT_VERSIONS+=ssl=openssl" in both the '/etc/make.conf'
> file and the 'poudriere.d/make.conf' file.
>
> $ openssl version
> OpenSSL 1.1.1g  21 Apr 2020
>
> I cannot install version 12 or 13 of FreeBSD because of an squashed
> bug, "https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666;
>
> I have I correct this problem?
>
> Thanks
>
> --
> Carmel
___
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"

Qt5-5.15 Packages for FreeBSD-11

[Tobias C. Berner]

Moin moin

Qt5 dropped support for OpenSSL 1.0 with Qt5-5.15.

As FreeBSD 11 only has OpenSSL 1.0 in base, that means
that there won't be any binary packages for net/qt5-network
and all ports depending on it once Qt5-5.15 lands in the
ports tree.

If you require qt5-network, you have two possible solutions
1) Upgrade to FreeBSD >=12
2) Build your own packages and switch to use OpenSSL from ports
(for all your ports).


We're sorry for the inconvenience.


mfg Tobias, with hat kde@.
___
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: Gratuitous port splitting (was: Port Avidemux)

[Tobias C. Berner]

I'm preparing a diff for this, and will let you know once it is ready
for testing.

mfg Tobias

On Mon, 25 May 2020 at 06:12, Tobias C. Berner  wrote:
>
> Moin moin
>
> From my side, I don't see a reason to have it split either. If there
> is no reason for the split for users, and only causes hassle, I don't
> see why the ports should remain split.
>
> My suggestion would be to just merge everything into one port, that is
> functional and gives you avidemux as a whole, usable package.
>
>
> mfg Tobias
>
> On Sun, 24 May 2020 at 23:46, Chris  wrote:
> >
> > On Sun, 24 May 2020 09:56:39 -0700 Freddie Cash fjwc...@gmail.com said
> >
> > > Perhaps the avidemux port should be renamed to avidemux-libs, and then a
> > > new avidemux meta-port could be created with basically just an OPTIONS
> > > screen where your pick which parts you want installed?
> > +1 for that.
> > I was going to propose making a meta-port called "avidemux" with options
> > that pull only what's required to create a functional port. But decided
> > to wait till I got through all my mail first, in case someone as (at least)
> > as smart as I am beat me to the proposal. ;-)
> >
> > --Chris
> > >
> > > Cheers,
> > > Freddie
> > >
> > > Typos due to smartphone keyboard.
> > > ___
> > > 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"
___
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: sqlite3 update to 3.31.0 breaks firefox and thunderbird

[Tobias C. Berner]

Moin moin

This should likely be added to firefox:
https://hg.mozilla.org/try/rev/8d7104bac33729b4da67954b07fb08371df39bd8


mfg Tobias

On Mon, 27 Jan 2020 at 01:00, David Wolfskill  wrote:
>
> On Sun, Jan 26, 2020 at 06:35:01PM -0500, Michael Butler wrote:
> > Both produce core dumps related to sqlite :-( Rebuilding both doesn't
> > fix either. Downgrading to 3.30.1 restores normal operation,
> > 
>
> Confirmed; thank you for the circumvention.
>
> Peace,
> david
> --
> David H. Wolfskill  da...@catwhisker.org
> "Now, with me, there's no lying." -- Donald J. Trump   ["??!?" -- me]
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
___
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: kdenlive-19.12.0 and 19.12.1 too slow to be usable

[Tobias C. Berner]

Moin moin

Could you open an upstream bug-report at  https://bugs.kde.org/


mfg Tobias

On Thu, 23 Jan 2020 at 21:41, Simon Gerraty  wrote:
>
> FYI, I fecthed and installed:
>
> https://pkg.freebsd.org/FreeBSD:11:amd64/release_3/All/kdenlive-18.12.3.txz
>
> which works much better.  I still get noise on tty - presumably from
> some of the libraries that kdenlive uses (there are all still from
> quarterly collection), but kdenlive works better, playhead tracks video
> ok and audio plays in sync.
>
> --sjg
>
> On Wed, 22 Jan 2020 10:19:30 -0800, Simon Gerraty writes:
> >Hi all.
> >
> >I cc'd ports, since kdenlive depends on lots of other packages.
> >
> >kdenlive-18.x was working fine on my
> >i9-7900X CPU @ 3.30GHz (10 core), with
> >NVIDIA GPU GeForce GTX 1050 Ti
> >
> >I recently ran pkg upgrade -f, and now with kdenlive-19.12.0
> >is it completely unusable.
> >
> >The display is sluggish (to put it kindly); the play head moves in big
> >jumps (stalls for several seconds at times), the video does not display
> >even close to smoothly, and the audio is out of sync.
> >
> >There is also a huge volume of debug info being spewed to tty, with what
> >looks like lots of errors.  Which I did not see with 18.x
> >
> >Since the release notes for kdenlive 19.12.1 mentioned disabling debug,
> >I tried downloading the kdenlive-19.12.1 from the latest pkg build, and
> >that installs and runs, but I still see lots of debug noise on tty
> >and the performance is still too bad to allow editing of anything.
> >
> >Just to confuse things further, a machine at work, which run pkg
> >upgrade -f at about the same time, kdenlive-19.12.0 works tollerably
> >despite the endless stream of debug output.
> >
> >That box has Xeon(R) CPU E5-2637 v3 @ 3.50GHz (8 core) with
> >NVIDIA GPU Quadro K4200 (GK104GL)
> >
> >Thoughts?
> >--sjg
___
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: Reminder: Qt4 next week

[Tobias C. Berner]

Hi there

Sorry, if the removal was too aggressive. You can just svn copy the port
from the revision prior to the removal and modify it to use Qt5.

mfg Tobias

On Thu, 28 Mar 2019 at 21:05, Hans Petter Selasky  wrote:

> On 3/17/19 10:44 AM, Tobias C. Berner wrote:
> > Moin moin
> >
> >
> > Qt4 is mostly gone now from the tree. With it probably some stuff people
> > would still like to use (e.g. audio/mumble), but were not upgraded in
> time.
> > Date date of the removal was chosen mid-march on purpose, so that there
> is
> > still some time before cutting the quarterly to bring these back with
> > Qt5 support enabled and have them in 2019Q2 without any hassle.
> >
>
> Hi,
>
> Sorry for not reading the e-mails.
>
> At least virtual_oss_ctl compiles with qt5. Only the port Makefile needs
> updating. How can I get this port back?
>
> --HPS
>
___
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: Reminder: Qt4 next week

[Tobias C. Berner]

Moin moin


Qt4 is mostly gone now from the tree. With it probably some stuff people
would still like to use (e.g. audio/mumble), but were not upgraded in time.
Date date of the removal was chosen mid-march on purpose, so that there is
still some time before cutting the quarterly to bring these back with
Qt5 support enabled and have them in 2019Q2 without any hassle.


mfg Tobias

On Sat, 9 Mar 2019 at 17:58, Tobias C. Berner  wrote:

> Moin moin
>
>
> This is a quick reminder that Qt4 will be removed from the tree next week.
> Please check the wiki page [1] for ports that you maintain which are still
> using Qt4,
> to see whether you can bump them to use Qt5, or want let them follow Qt4
> to the
> big software archeology museum in the sky.
>
>
> mfg Tobias
>
>
> [1] https://wiki.freebsd.org/KDE/DeprecatingQt4#preview
>
___
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"

Reminder: Qt4 next week

[Tobias C. Berner]

Moin moin


This is a quick reminder that Qt4 will be removed from the tree next week.
Please check the wiki page [1] for ports that you maintain which are still
using Qt4,
to see whether you can bump them to use Qt5, or want let them follow Qt4 to
the
big software archeology museum in the sky.


mfg Tobias


[1] https://wiki.freebsd.org/KDE/DeprecatingQt4#preview
___
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: Building qt5-gui port?

[Tobias C. Berner]

Moin moin

Make sure all your qt5-(qt5-gui dependency)-ports that are already
installed are at 5.12.0.


mfg Tobias

On Sun, 10 Feb 2019 at 06:28, Steve Kargl 
wrote:

> Anyone have any pointers on building x11-toolkits/qt5-gui on
> FreeBSD-current?  My attempts end with
>
> c++ -Wl,--as-needed -fstack-protector -Wl,--no-undefined
> -Wl,--version-script,QtGui.version -pthread -Wl,-rpath,/usr/local/lib/qt5
> -shared -Wl,-Bsymbolic-functions
> -Wl,--dynamic-list,/usr/ports/x11-toolkits/qt5-gui/work/qtbase-everywhere-src-5.12.0/src/gui/QtGui.dynlist
> -Wl,-soname,libQt5Gui.so.5 -o libQt5Gui.so.5.12.0 .obj/qaccessible.o
> .obj/qaccessiblecache.o  .obj/qaccessibleobject.o
> .obj/qaccessibleplugin.o  .obj/qplatformaccessibility.o
> .obj/qaccessiblebridge.o  .obj/qgenericpluginfactory.o
> .obj/qgenericplugin.o  .obj/qwindowsysteminterface.o
> .obj/qplatforminputcontextfactory.o  .obj/qplatforminputcontextplugin.o
> .obj/qplatforminputcontext.o  .obj/qplatformintegration.o
> .obj/qplatformscreen.o  .obj/qplatformintegrationfactory.o
> .obj/qplatformintegrationplugin.o  .obj/qplatformtheme.o
> .obj/qplatformthemefactory.o  .obj/qplatformthemeplugin.o
> .obj/qplatformwindow.o  .obj/qplatformoffscreensurface.o
> .obj/qplatformcursor.o  .obj/qplatformclipboard.o  .obj/qplatformnativei
>  nterface.o  .obj/qsessionmanager.o  .obj/qsurfaceformat.o
> .obj/qguiapplication.o  .obj/qwindow.o  .obj/qoffscreensurface.o
> .obj/qplatformsurface.o  .obj/qsurface.o  .obj/qclipboard.o
> .obj/qcursor.o  .obj/qevent.o  .obj/qinputmethod.o
> .obj/qinternalmimedata.o  .obj/qkeysequence.o  .obj/qkeymapper.o
> .obj/qpalette.o  .obj/qguivariant.o  .obj/qscreen.o  .obj/qshortcutmap.o
> .obj/qstylehints.o  .obj/qtouchdevice.o
> .obj/qplatformsharedgraphicscache.o  .obj/qplatformdialoghelper.o
> .obj/qplatformservices.o  .obj/qplatformsystemtrayicon.o
> .obj/qplatformsessionmanager.o  .obj/qplatformmenu.o  .obj/qpixelformat.o
> .obj/qpaintdevicewindow.o  .obj/qrasterwindow.o
> .obj/qplatformgraphicsbuffer.o  .obj/qplatformgraphicsbufferhelper.o
> .obj/qinputdevicemanager.o  .obj/qhighdpiscaling.o
> .obj/qtestsupport_gui.o  .obj/qdnd.o  .obj/qdrag.o  .obj/qplatformdrag.o
> .obj/qshapedpixmapdndwindow.o  .obj/qsimpledrag.o
> .obj/qplatformopenglcontext.o  .obj/qopenglcontext.o  .obj/qopenglwindow.o
> .obj/q
>  bitmap.o  .obj/qimage.o  .obj/qimage_conversions.o
> .obj/qimageiohandler.o  .obj/qimagereader.o
> .obj/qimagereaderwriterhelpers.o  .obj/qimagewriter.o
> .obj/qpaintengine_pic.o  .obj/qpicture.o  .obj/qpictureformatplugin.o
> .obj/qpixmap.o  .obj/qpixmapcache.o  .obj/qplatformpixmap.o
> .obj/qpixmap_raster.o  .obj/qpixmap_blitter.o
> .obj/qimagepixmapcleanuphooks.o  .obj/qicon.o  .obj/qiconloader.o
> .obj/qiconengine.o  .obj/qiconengineplugin.o  .obj/qmovie.o
> .obj/qbmphandler.o  .obj/qppmhandler.o  .obj/qxbmhandler.o
> .obj/qxpmhandler.o  .obj/qpnghandler.o  .obj/qfont.o  .obj/qfontengine.o
> .obj/qfontengineglyphcache.o  .obj/qfontsubset.o  .obj/qfontmetrics.o
> .obj/qfontdatabase.o  .obj/qtextengine.o  .obj/qtextlayout.o
> .obj/qtextformat.o  .obj/qtextobject.o  .obj/qtextoption.o
> .obj/qfragmentmap.o  .obj/qtextdocument.o  .obj/qtextdocument_p.o
> .obj/qtexthtmlparser.o  .obj/qabstracttextdocumentlayout.o
> .obj/qtextdocumentlayout.o  .obj/qtextcursor.o
> .obj/qtextdocumentfragment.o  .obj/q
>  textimagehandler.o  .obj/qtexttable.o  .obj/qtextlist.o
> .obj/qtextdocumentwriter.o  .obj/qsyntaxhighlighter.o  .obj/qstatictext.o
> .obj/qrawfont.o  .obj/qglyphrun.o  .obj/qdistancefield.o
> .obj/qinputcontrol.o  .obj/qfontengine_qpf2.o
> .obj/qplatformfontdatabase.o  .obj/qharfbuzzng.o  .obj/qtextodfwriter.o
> .obj/qzip.o  .obj/qcssparser.o  .obj/qbackingstore.o  .obj/qbezier.o
> .obj/qblendfunctions.o  .obj/qblittable.o  .obj/qbrush.o  .obj/qcolor.o
> .obj/qcolorprofile.o  .obj/qcompositionfunctions.o
> .obj/qcosmeticstroker.o  .obj/qdrawhelper.o  .obj/qemulationpaintengine.o
> .obj/qgrayraster.o  .obj/qimagescale.o  .obj/qmatrix.o  .obj/qmemrotate.o
> .obj/qoutlinemapper.o  .obj/qpagedpaintdevice.o  .obj/qpagelayout.o
> .obj/qpagesize.o  .obj/qpaintdevice.o  .obj/qpaintengine.o
> .obj/qpaintengineex.o  .obj/qpaintengine_blitter.o
> .obj/qpaintengine_raster.o  .obj/qpainter.o  .obj/qpainterpath.o
> .obj/qpathclipper.o  .obj/qpdf.o  .obj/qpdfwriter.o  .obj/qpen.o
> .obj/qpolygon.o  .obj/qraster
>  izer.o  .obj/qregion.o  .obj/qstroker.o  .obj/qtextureglyphcache.o
> .obj/qtransform.o  .obj/qtriangulatingstroker.o  .obj/qtriangulator.o
> .obj/qplatformbackingstore.o  .obj/qpathsimplifier.o  .obj/qcssutil.o
> .obj/qdesktopservices.o  .obj/qvalidator.o  .obj/qgridlayoutengine.o
> .obj/qabstractlayoutstyleinfo.o  .obj/qlayoutpolicy.o
> .obj/qshaderformat.o  .obj/qshadergenerator.o  .obj/qshadergraph.o
> .obj/qshadergraphloader.o  .obj/qshaderlanguage.o  .obj/qshadernode.o
> .obj/qshadernodeport.o  .obj/qshadernodesloader.o  .obj/qtexturefiledata.o
> .obj/qtexturefilereader.o  .obj/qpkmhandler.o  .obj/qktxhandler.o
> .obj/qgenericmatrix.o  

Re: Cannot mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped)

[Tobias C. Berner]

Hi there

Qt4 has nothing to do with this. The issue is caused by upgrading Qt5 from
5.9.4 to 5.10.1 without also rebuilding the Qt5 using
applications/libraries :)


mfg Tobias

On 31 May 2018 at 16:37, tech-lists  wrote:

> Hello lists,
>
> context: 11.2-PRERELEASE #0 r333458 / ports r471194
>
> with xpdf I get the following error:
>
> Cannot mix incompatible Qt library (version 0x50904) with this library
> (version 0x50a01),Abort (core dumped)
>
> I seem to have both qt4-4.8.7 and qt5-5.10.1 installed. I didn't install
> these directly though, seems they've been installed as dependencies of
> other ports. I'm using MATE desktop.
>
> I've tried reinstalling xfdf via pkg and the port with the same result. Is
> this a known problem/how can I fix? Have found no fix yet from GIS, most
> seem to point to deleting and reinstalling everything.
>
> thanks,
> --
> J.
> ___
> 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

[Tobias C. Berner]

Moin moin

Here's a script which should automatically fix the origin for the
kde4-versioned ports (based on the MOVED entries of r465345):
   http://people.freebsd.org/~tcberner/scripts/fix_kde4_origins.sh

It //should// set the origins properly for the moved ports, and the output
should be on the lines of
# ./fix_kde4_origins.sh
[...]
- sysutils/baloo-widgets [sysutils/baloo-widgets-kde4] is not installed.
+ Changing origin of nepomuk-core-4.14.3_14 from sysutils/nepomuk-core to
sysutils/nepomuk-core-kde4.
- sysutils/kfloppy [sysutils/kfloppy-kde4] is not installed.
- sysutils/ksystemlog [sysutils/ksystemlog-kde4] is not installed.
+ Changing origin of baloo-4.14.3_5 from sysutils/baloo to
sysutils/baloo-kde4.
+ Changing origin of kfilemetadata-4.14.3_13 from sysutils/kfilemetadata to
sysutils/kfilemetadata-kde4.
[...]


Please let me know if that works for you, or how I could improve it.


mfg Tobias



On 17 April 2018 at 17:43, Tijl Coosemans <t...@freebsd.org> wrote:

> On Tue, 17 Apr 2018 16:19:39 +0200 Tobias C. Berner wrote:
> > Long answer: KDE is shipped in mulitple, let's call them groups:
> >   - frameworks (libraries to build kde and qt applications) -- we call
> > these ports kf5-foo
> >   - plasma (the desktop) -- we'll call these ports plasma5-foo
> >   - applications (the applications)
> >
> > Now, previously during KDE SC4 days, this was a whole "blob". This is why
> > it made sense to call them all kde4-foo or foo-kde4.
> > Now with this new split there is no real notion to call an application
> > foo-kde5. For example during the transition in the last few
> > years many KDE Application releases were a mix of Qt4 and Qt5 (i.e.
> > kdelibs4 and kf5 based applications). So we would have had
> > a kate-kde5 that was using kdelibs-kde4 ... well that would have been
> > confusing too.
> >
> > The same thing will eventually happen when the next KDE Frameworks will
> > roll around I expect, where the applications get updated one after
> > another, with mixed releases in between.
> >
> > We opted for the same method as other ports use. A new version appears
> that
> > is incompatible, move "bar/foo" to "bar/foo3" and update "bar/foo" in
> > place.
>
> I don't think this is the norm.  All the big ports (perl, python, php,
> gcc, mysql, gtk, qt,...) just leave bar/foo and create bar/foo4.  In
> place updating to an incompatible version can be a complete surprise
> for users (POLA violation) and leave them with a broken system.
>
___
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

[Tobias C. Berner]

On 17 April 2018 at 14:00, Andriy Gapon  wrote:

> On 17/04/2018 10:24, Adriaan de Groot wrote:
> > So, there are roughly two migration paths: supposing someone has
> x11/kde4
> > installed, which has dependencies on many applications and a Plasma 4
> desktop,
> > kde@ wants (wanted) to make it possible to migrate to a still-KDE4
> desktop,
> > while renaming everything to have a -kde4 suffix. The other path is to
> migrate
> > to the latest-and-greatest-from-KDE .. we don't have a metaport for
> that, and
> > if we do get one it probably won't be called x11/kde5.
> >
> > For single applications, the migration looks similar: you had, around
> january
> > 2018, port . That's the KDE4 version. Now there is port -kde4,
> if
> > you want to stick to KDE4 software (which is no longer released
> upstream, and
> > is based on an EOL toolkit, but some people feel quite strongly about
> this).
> > Ports  are returning, without a suffix, to mean "the
> latest-and-greatest-
> > version-of-". This is consistent with other ports which have a
> ,
> > sometimes a -devel for upcoming things, and a - for
> older
> > versions if you have specific dependencies on old versions.
> >
> > Historically, things were a mess with naming with the KDE ports. We
> think
> > we've got a good scheme now: -kde4 (and in the far future,
> -kf5) for
> > versions of the software based on an older stack, and  for the
> current
> > one. But the pain of getting from the mess to something better organized
> has
> > to happen at some point.
>
> Moin moin

I am just curious why not have explicit -kde4 and -kde5.
>
I think that qt sets a good example and there is no confusion and no
> migration
>
Short answer: Because there is no kde5

Long answer: KDE is shipped in mulitple, let's call them groups:
  - frameworks (libraries to build kde and qt applications) -- we call
these ports kf5-foo
  - plasma (the desktop) -- we'll call these ports plasma5-foo
  - applications (the applications)

Now, previously during KDE SC4 days, this was a whole "blob". This is why
it made sense to call them all kde4-foo or foo-kde4.
Now with this new split there is no real notion to call an application
foo-kde5. For example during the transition in the last few
years many KDE Application releases were a mix of Qt4 and Qt5 (i.e.
kdelibs4 and kf5 based applications). So we would have had
a kate-kde5 that was using kdelibs-kde4 ... well that would have been
confusing too.

The same thing will eventually happen when the next KDE Frameworks will
roll around I expect, where the applications get
updated one after another, with mixed releases in between.

We opted for the same method as other ports use. A new version appears that
is incompatible, move "bar/foo" to "bar/foo3" and update "bar/foo" in
place.
This is not a new thing, it's just a lot in one go, I agree, and I'm sorry
for the inconvenience. However, let's not make a problem, that could
essentially
be solved by a pkg-delete followed by a pkg-add too complicated :)

I'll try to create a shell script to rewire the pkg's automatically to the
new origin...


mfg Tobias


pain in the future when 6 appears.
>
> --
> 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: multimedia/avidemux-qt4 compilation error

[Tobias C. Berner]

Hi there

See https://reviews.freebsd.org/D12178 for a partial fix.


mfg Tobias

On 12 September 2017 at 01:03, Grzegorz Junka  wrote:

> Which option may be responsible for this error:
>
> /wrkdirs/usr/ports/multimedia/avidemux-qt4/work/avidemux_2.6
> .11/avidemux/qt4/ADM_jobs/src/ADM_jobControl.cpp:115:58: error: unable to
> find string literal operator 'operator""y' with 'const char [8]', 'long
> unsigned int' arguments
>  #define MX(x,y) case ADM_JOB_##x: status->setIcon(QIcon(":/jobs/
> "y));break;
>
> Then it repeats a few times when compiling the ADM_jobControl file.
>
> GrzegorzJ
>
> ___
> 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: port head/x11/kde4-runtime not buildable due to missing distfile

[Tobias C. Berner]

Hi Matthias

It seems 16.12.3 was moved to Attic on kde's mirrors.

See: http://www.mirrorservice.org/sites/download.kde.org/ls-lR


I will fix ports to point to the new location shortly. Thanks for the headsup :)

You can fetch it from here in the meantime:
https://download.kde.org/Attic/applications/16.12.3/src/

mfg Tobias

On 20 May 2017 at 12:40, Matthias Apitz  wrote:
>
> Hello,
>
> I'm building ports in head (last svn update May 19) and the above port fails
> in poudriere due to missing distfile:
>
> # cat distinfo
> TIMESTAMP = 1490531914
> SHA256 (KDE/applications/16.12.3/kde-runtime-16.12.3.tar.xz) =
> 7e6406b9d85594fdedb2bd424316159f5633fbe8b28970338e4d81418f4017eb
> SIZE (KDE/applications/16.12.3/kde-runtime-16.12.3.tar.xz) = 7902924
>
> I spent an hour or so searching with Don G. for it with no luck.
> Has someone a private copy of it in local
> /usr/ports/distfiles/KDE/applications/16.12.3
>
> Thanks
>
> matthias
> --
> Matthias Apitz   |  /"\   ASCII Ribbon Campaign:
> E-mail: g...@unixarea.de |  \ /   - No HTML/RTF in E-mail
> WWW: http://www.unixarea.de/ |   X- No proprietary attachments
> phone: +49-176-38902045  |  / \   - Respect for open standards
>  | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
___
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: www/webkit-qt5 build failure?

[Tobias C. Berner]

Hi Jonathan

I cannot reproduce this here. Are your ports and packages up to date?

FreeBSD 10.3 jail:
[...]
Running configure tests...
[...]
Checking for icu... yes
[...]




mfg Tobias

On 28 September 2016 at 20:28, Jonathan Chen  wrote:

> Hi,
>
> I've just updated ports on a 10-STABLE/amd64 system, and in trying to
> build qt5-webkit. It currently stops abruptly with the following
> message:
>
> [...]
> User Timing ... no
> Vibration . no
> Video . yes
> Video Track ... yes
> WebGL . yes
> Web Audio . no
> Web Sockets ... yes
> Web Timing  yes
> Workers ... yes
> XHR Timeout ... yes
> XSLT .. yes
>
> The WebKit build was disabled for the following reasons:
> * ICU is required.
>
> I can't seem to find any knobs associated with ICU in the port. Have I
> missed something?
>
> Cheers.
> --
> Jonathan Chen 
>
___
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"