quarterly?
If that's the case you should merge it (if you're not a committer just
file a PR asking for that, explaining which commits should be merged and
why)
(message resent with correct email address to the list)
--
Guido Falsi
similar issues with this code.
I'm not advocating doing this in general. In fact patching the code to
not cause these errors should be the solution, but for old code that is
not going to change upstream, maybe disabling the warnings is the
correct fix.
--
Guido Falsi
any further big
change to change the "default" version.
Any opinion? if no work is already underway IO could start looking into
Plan 1, but it will take a little time before I get anything I can share.
--
Guido Falsi
r sunpoet (as podofo maintainer)
opinion. Maybe he also already has a plan or is working on something
that I don't know about.
--
Guido Falsi
th a strange
xfce4 issue I need to address.
Give me a few days to look into this.
--
Guido Falsi
On 27/05/23 19:37, Guido Falsi wrote:
On 27/05/23 13:24, Po-Chuan Hsieh wrote:
>
>> plan 2 - Another option is doing the same as above, but my
updating
>> podofo to the latest version and moving old 0.9.x to a
graphics/podofo09
>> (or whateve
uildboxes, people use binary packages almost all the time in linux.
Developers don't care to keep low overhead in their builds and with
dependency. The ports tree cannot mitigate this external pressure.
Anyway building from ports on live machines has always been bad practice
for a lot of reasons.
--
Guido Falsi
loaded at boot time
and not affect the currently running system?
UPDATING entry 20230906 has all the details.
--
Guido Falsi
On 25/09/23 19:35, Gareth de Vaux wrote:
On Mon 2023-09-25 (17:38), Guido Falsi wrote:
UPDATING entry 20230906 has all the details.
UPDATING entry 20230906 is the reason for the question - it does not say how
to safely migrate - do you uninstall devcpu-data and then install cpu-microcode
On 25/09/23 19:50, Gareth de Vaux wrote:
On Mon 2023-09-25 (17:38), Guido Falsi wrote:
This one, which calls in py-cryptography which requires rust.
Thanks
There is a more general aspect to this. In the rest of the unix world
software is now almost universally build using CI systems and
On 25/09/23 20:33, Guido Falsi wrote:
On 25/09/23 19:50, Gareth de Vaux wrote:
On Mon 2023-09-25 (17:38), Guido Falsi wrote:
This one, which calls in py-cryptography which requires rust.
Thanks
There is a more general aspect to this. In the rest of the unix world
software is now almost
On 25/09/23 22:21, George Mitchell wrote:
On 9/25/23 11:38, Guido Falsi wrote:
[...]
There is a more general aspect to this. In the rest of the unix world
software is now almost universally build using CI systems and
buildboxes, people use binary packages almost all the time in linux
ommit/a587ae7a3741d56a3991d030a8d08b6e9e619f07
[2] https://github.com/freebsd/poudriere/issues/806
--
Guido Falsi
On 26/09/23 00:06, Dave Horsfall wrote:
On Mon, 25 Sep 2023, Guido Falsi wrote:
Anyway building from ports on live machines has always been bad practice
for a lot of reasons.
That's fine if you can afford a spare system just for building...
Again, anyone can do things the way he p
old version of software (to avoid heavy dependencies or
whatever) is a landmine waiting to go off
The problem showed up now because the landmine of keeping an old version
of py-cryptography in the tree finally went off.
I'm sure there are more similar landmines waiting to explode under our
f
no benefit.
--
Guido Falsi
On 26/09/23 13:46, Alexander Leidinger wrote:
Am 2023-09-26 09:44, schrieb Guido Falsi:
My poudriere machine rarely can do a build run without rebuilding one
or more of rust, some version of clang, some version of gcc,
qt[56]-webengine, py-qt6 (this one does most of the work single
threaded
On 26/09/23 17:26, Jose Quinteiro wrote:
On 9/25/23 13:21, George Mitchell wrote:
On 9/25/23 11:38, Guido Falsi wrote:
[...]
There is a more general aspect to this. In the rest of the unix world
software is now almost universally build using CI systems and
buildboxes, people use binary
On 26/09/23 17:44, Jose Quinteiro wrote:
On 9/26/23 00:17, Guido Falsi wrote:
On 26/09/23 08:53, Helge Oldach wrote:
Gareth de Vaux wrote on Mon, 25 Sep 2023 17:06:54 +0200 (CEST):
Hi all, I've just upgraded bind916 which brought half my system down
since
it suddenly required a mounta
On 27/09/23 02:28, Jose Quinteiro wrote:
On 9/26/23 09:14, Guido Falsi wrote:
(snip)
And yet I remember a proposal that would have prevented this requirement
on one of these lists. Separate base SSL from ports SSL. Force ports to
use ports SSL and prune back base SSL to the bare minimum
- no routing
The only way to know for sure is reading the source code.
--
Guido Falsi
On 27/09/23 12:57, Guido Falsi wrote:
On 27/09/23 12:54, Alexander Leidinger wrote:
Am 2023-09-27 10:56, schrieb Charlie Li:
In poudriere, apart from the fetch phase, network access is not
allowed by default so spawning a server that listens on an IP that
does not necessarily exist that
On 27/09/23 13:00, Alexander Leidinger wrote:
Am 2023-09-27 12:57, schrieb Guido Falsi:
On 27/09/23 12:54, Alexander Leidinger wrote:
Am 2023-09-27 10:56, schrieb Charlie Li:
In poudriere, apart from the fetch phase, network access is not
allowed by default so spawning a server that listens
d.
If you have a broken repo (due to -S or some other unknown reason) you
will need to rebuild it from scratch (-c option) to get a pristine and
hopefully working one.
--
Guido Falsi
On 16/10/23 13:03, DutchDaemon - FreeBSD Forums Administrator wrote:
On 16/10/2023 12:57, Guido Falsi wrote:
On 16/10/23 11:19, DutchDaemon - FreeBSD Forums Administrator wrote:
I found this one after a full rebuild in Poudriere:
ld-elf.so.1: Shared object "libssl.so.11" not found
On 16/10/23 13:09, DutchDaemon - FreeBSD Forums Administrator wrote:
On 16/10/2023 13:07, Guido Falsi wrote:
On 16/10/23 13:03, DutchDaemon - FreeBSD Forums Administrator wrote:
On 16/10/2023 12:57, Guido Falsi wrote:
On 16/10/23 11:19, DutchDaemon - FreeBSD Forums Administrator wrote:
I
On 16/10/23 13:13, Guido Falsi wrote:
On 16/10/23 13:09, DutchDaemon - FreeBSD Forums Administrator wrote:
On 16/10/2023 13:07, Guido Falsi wrote:
On 16/10/23 13:03, DutchDaemon - FreeBSD Forums Administrator wrote:
On 16/10/2023 12:57, Guido Falsi wrote:
On 16/10/23 11:19, DutchDaemon
On 16/10/23 13:14, DutchDaemon - FreeBSD Forums Administrator wrote:
On 16/10/2023 13:07, Guido Falsi wrote:
On 16/10/23 13:03, DutchDaemon - FreeBSD Forums Administrator wrote:
On 16/10/2023 12:57, Guido Falsi wrote:
On 16/10/23 11:19, DutchDaemon - FreeBSD Forums Administrator wrote:
I
But, since they use it, in my attempt to update the
port I will keep such wording in pkg-descr, although I tend to mildly
disagree.
--
Guido Falsi
On 21/10/23 17:20, Guido Falsi wrote:
Hi all,
As you may have noticed there is a new version of the Midori browser.
This new version is an almost complete rewrite based on Gecko (it really
looks like a fork of Firefox LTS, looking at the new source code),
published by a new entity that
no need to descend in class attacks, it is not going to help you
get support any faster.
--
Guido Falsi
On 21/11/23 22:00, Edward Sanford Sutton, III wrote:
On 11/21/23 09:21, Guido Falsi wrote:
On 21/11/23 16:39, Richard Childers wrote:
I was using ungoogled-chromium and I had 60+ tabs that I can now not
get back because ungoogled-chromium has been withdrawn from circulation.
why are these
y to
build. SO they disappear more often.
But any port can fail to build and if it fails there is a reason,
providing an old package with the same name is inherently dangerous.
--
Guido Falsi
ch:
https://github.com/freebsd/poudriere/commit/8726f468060a8886cdfac6d20cae4c997f735406
Hope this helps!
--
Guido Falsi
ou need to put it after ".include ". But I
don't think that's the best strategy, you'd be better off leveraging
USES=php and flavorizing your port, using PHP_VER.
Not many live examples in the ports tree, but maybe you can find some
inspiration in some of these Makefiles:
databases/pear-DoctrineDBAL/Makefile
devel/php-composer/Makefile
Hope this information helps.
--
Guido Falsi
p+composer part making a port could make sense, but why
upstream is not creating a proper distribution with all required files?
--
Guido Falsi
On 11/12/23 18:59, Alexander Leidinger wrote:
Am 2023-12-11 14:43, schrieb Guido Falsi:
As a side note, if what you are trying to port is a pure PHP project
using composer, I'm not sure creating pa port of it is really a good
idea. The whole idea of composer is that it is handling depende
On 12/12/23 11:21, Alexander Leidinger wrote:
Am 2023-12-11 21:19, schrieb Guido Falsi:
I gave you suggestions on how to work around these
(properties|features|limitations|rules|whatever) of the ports tree. I
would be more interested to hear if you found those useful or not.
Distributing
LE_SET+=PULSEAUDIO
OPTIONS_FILE_SET+=SNDIO
Looks like a missing -lm to me.
--
Guido Falsi
the issue.
Like some python or perl package (if those are used by firefox for the
build) or to pkgconfig/autoconf tools?
I'm just guessing here.
Stefan Ehmann escreveu (terça, 13/02/2024 à(s) 21:42):
On Tuesday, February 13, 2024 9:58:54 PM CET Guido Falsi wrote:
On 13/02/24
e -S option, is something I would not suggest. At least not unless one
is able to really understand what is going on; it also has the problem
that once you end up with a broken repo set the only fix is to start
from scratch (AFAIK).
--
Guido Falsi
are built using
poudriere, so ports must work in poudriere, and maintainers should also
verify and test that.
--
Guido Falsi
"dropin" replacement.
Work, maybe a lot of it, will be needed to replace an existing setup.
--
Guido Falsi
details, which are
not necessarily logical or in any way connected with the information
already present) need to be added by hand after manual discovery.
--
Guido Falsi
s, in
which case you'll need to modify their list.
--
Guido Falsi
On 25/10/21 10:02, Per olof Ljungmark wrote:
On 10/25/21 09:51, Guido Falsi wrote:
On 25/10/21 08:14, Per olof Ljungmark wrote:
FreeBSD 12-STABLE from Oct 15
nextcloudclient 3.3.5
I get popup messages from the client stating "Untrusted Certificate
Cannot connect securely to [server
On 25/10/21 16:22, Per olof Ljungmark wrote:
On 10/25/21 09:51, Guido Falsi wrote:
On 25/10/21 08:14, Per olof Ljungmark wrote:
FreeBSD 12-STABLE from Oct 15
nextcloudclient 3.3.5
I get popup messages from the client stating "Untrusted Certificate
Cannot connect securely to [server
uld not be added to newly created ports, also because the
information is easy to find in the repo history.
I don't think there is any rule for existing ones, I personally leave
them there unless requested to do anything different.
--
Guido Falsi
refox for example) started behaving very differently than it
does on other OSes for no good technical reason.
OTOH a valid technical reason could be dropping some functionality
depending on some API not available on FreeBSD, just to make an example
from the top of my head.
--
Guido Falsi
On 14/11/21 20:32, Rob LA LAU wrote:
And hi again,
On 14/11/2021 19:42, Guido Falsi wrote:
> IN fact I would very astonished if some port (say firefox for
example) started behaving very differently than it does on other OSes
for no good technical reason.
True.
But what if we're not
On 15/11/21 09:42, Rob LA LAU wrote:
Hi,
On 14/11/2021 20:49, Guido Falsi wrote:
You talk about "adding a periodic script". That is not even a real
modification to the upstream software IMHO. Just adding some glue code
for FreeBSD. If the script does what it advertises, and has no
but sadly
sometimes things become "unpleasant" (please anyone avoid being the one
bringing unpleasantness)
--
Guido Falsi
On 16/11/21 11:34, Rob LA LAU wrote:
Hi,
On 15/11/2021 10:21, Guido Falsi wrote:
You look too worried by the "functionality added" part.
Yes, I am worried. Of course I am.
Now I feel compelled to reply to all this rant of yours because you are
replying to me, but I really have l
On 16/11/21 11:56, Kurt Jaeger wrote:
Hi!
On 15/11/2021 10:21, Guido Falsi wrote:
You look too worried by the "functionality added" part.
Yes, I am worried. Of course I am.
When I first asked my question the day before yesterday, the first
responses were in the line of "port
have time to try to diagnose it
though.
Did you file a bug report in bugzilla so this can be tracked?
--
Guido Falsi
und
(the segmentation fault should be xfce-session)
I'm writing right away to let the issue known, maybe I only need to
force reinstall some ports, and once identified I can just bump
PORTREVISION.
If anyone has any idea, suggestions are welcome.
--
Guido Falsi
On 30/04/22 18:39, Guido Falsi wrote:
Hi,
The recent update to dbus to 1.14 seems to cause issues with xfce startup.
I've not investigated it much still, but I'm unable to login into xfce
after the upgrade, a window comes out saying it cannot connect to the
settings manager, and xf
find some way to do further testing and to debug
this, but I"m not sure how to get insight on the process.
My idea is that dbus-launch has somewhat changed behavior, but I'm just
guessing here.
--
Guido Falsi
marked your bug as blocking for it.
I'll followup there with findings and patches, if I happen to be able
to provide any.
[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263014
--
Guido Falsi
On 24/11/24 18:18, Dimitry Andric wrote:
On 24 Nov 2024, at 18:07, Guido Falsi wrote:
On 23/11/24 15:56, Guido Falsi wrote:
On 23/11/24 15:34, Guido Falsi wrote:
On 21/11/24 18:33, Guido Falsi wrote:
On 21/11/24 18:27, Dimitry Andric wrote:
On 21 Nov 2024, at 18:17, Guido Falsi wrote
On 23/11/24 15:56, Guido Falsi wrote:
On 23/11/24 15:34, Guido Falsi wrote:
On 21/11/24 18:33, Guido Falsi wrote:
On 21/11/24 18:27, Dimitry Andric wrote:
On 21 Nov 2024, at 18:17, Guido Falsi wrote:
On 20/11/24 23:50, Guido Falsi wrote:
On 20/11/24 22:14, Dimitry Andric wrote:
On 20 Nov
head both in host and in
the jails.
I'm also using ccache, but that does not look relevant.
--
Guido Falsi
On 25/11/24 22:18, Dag-Erling Smørgrav wrote:
Mark Millard writes:
Guido Falsi writes:
On 25/11/24 09:17, Dag-Erling Smørgrav wrote:
Dimitry Andric writes:
Probably best to create a bugzilla ticket, but as I said before, I
cannot reproduce this.
I can. My builder is running 15 and sees
On 26/11/24 18:29, Doug Moore wrote:
I think @kib has found the source of the problem. I've attached an
attempt to fix it.
Thanks for your work!
I have noticed this is already in base and upgraded successfully, issue
is now solved for me.
Sorry for the delay in reporting this.
--
On 20/11/24 22:14, Dimitry Andric wrote:
On 20 Nov 2024, at 18:32, Guido Falsi wrote:
I've noticed that recently some ports are dumping core during builds of
dependencies in head in poudriere.
I'm seeing this for example with sassc crashing while trying to build
x11-themes/grey
ol27 + 25
```
which points me to this upstream line of code:
https://github.com/sass/libsass/blob/7037f03fabeb2b18b5efa84403f5a6d7a990f460/src/units.hpp#L11
I could change the way it derives PI, but I'm not sure this is the
correct fix.
Thanks in advance for any insight!
--
Guido Falsi
associated with
use of tmpfs .
Interesting discovery, I'm also using USE_TMPFS=all
I'll try to do a test without that but I won't be able before tomorrow I
think.
--
Guido Falsi
On 25/11/24 23:15, Dimitry Andric wrote:
On 25 Nov 2024, at 23:12, Mark Millard wrote:
On Nov 25, 2024, at 13:27, Guido Falsi wrote:
On 25/11/24 22:18, Dag-Erling Smørgrav wrote:
Mark Millard writes:
Guido Falsi writes:
On 25/11/24 09:17, Dag-Erling Smørgrav wrote:
Dimitry Andric
On 02/01/25 01:38, Tomoaki AOKI wrote:
On Wed, 1 Jan 2025 19:50:50 +0100
Guido Falsi wrote:
Don't see a good reason to force everyone to use an old version.
Anyway the ports tree is open source, nothing stops anyone from
proposing (with himself as maintainer) a new port for the old ve
On 02/02/25 09:02, Baptiste Daroussin wrote:
Le 1 février 2025 23:36:12 GMT+01:00, Guido Falsi a écrit :
On 01/02/25 22:56, Baptiste Daroussin wrote:
On Sat 01 Feb 22:40, Baptiste Daroussin wrote:
On Fri 31 Jan 19:13, Baptiste Daroussin wrote:
On Fri 31 Jan 18:18, Guido Falsi wrote:
On 27
On 01/02/25 22:56, Baptiste Daroussin wrote:
On Sat 01 Feb 22:40, Baptiste Daroussin wrote:
On Fri 31 Jan 19:13, Baptiste Daroussin wrote:
On Fri 31 Jan 18:18, Guido Falsi wrote:
On 27/01/25 10:56, Nuno Teixeira wrote:
Hello Rainer,
> Wouldn't this be the right time to get Bapt@
round for gcc,
and would not solve the underlaying issue whatever that is.
My patch to poudriere is also a workaround, but I do hope this helps
identifying the real problem.
--
Guido Falsi
work around.
[1] https://github.com/freebsd/poudriere/pull/1204
--
Guido Falsi
On 31/01/25 19:13, Baptiste Daroussin wrote:
On Fri 31 Jan 18:18, Guido Falsi wrote:
On 27/01/25 10:56, Nuno Teixeira wrote:
Hello Rainer,
> Wouldn't this be the right time to get Bapt@ involved? After all, he has
> worked intensively on the pkg updates.
Yes it is. I&#x
On 20/11/24 23:50, Guido Falsi wrote:
On 20/11/24 22:14, Dimitry Andric wrote:
On 20 Nov 2024, at 18:32, Guido Falsi wrote:
I've noticed that recently some ports are dumping core during builds
of dependencies in head in poudriere.
I'm seeing this for example with sassc crashing wh
On 21/11/24 18:27, Dimitry Andric wrote:
On 21 Nov 2024, at 18:17, Guido Falsi wrote:
On 20/11/24 23:50, Guido Falsi wrote:
On 20/11/24 22:14, Dimitry Andric wrote:
On 20 Nov 2024, at 18:32, Guido Falsi wrote:
I've noticed that recently some ports are dumping core during buil
On 21/11/24 18:33, Guido Falsi wrote:
On 21/11/24 18:27, Dimitry Andric wrote:
On 21 Nov 2024, at 18:17, Guido Falsi wrote:
On 20/11/24 23:50, Guido Falsi wrote:
On 20/11/24 22:14, Dimitry Andric wrote:
On 20 Nov 2024, at 18:32, Guido Falsi wrote:
I've noticed that recently some port
On 23/11/24 15:34, Guido Falsi wrote:
On 21/11/24 18:33, Guido Falsi wrote:
On 21/11/24 18:27, Dimitry Andric wrote:
On 21 Nov 2024, at 18:17, Guido Falsi wrote:
On 20/11/24 23:50, Guido Falsi wrote:
On 20/11/24 22:14, Dimitry Andric wrote:
On 20 Nov 2024, at 18:32, Guido Falsi wrote
00:00] Building devel/llvm19@default |
llvm19-19.1.7: missed shlib PORTREVISION chase
Looks like an issue in poudriere shlib checks, but could be induced by
something else.
Unluckily I have no idea how the 32bit library checks work.
--
Guido Falsi
ghostwriter/-/blob/release/24.12/CMakeLists.txt#L21
--
Guido Falsi
On 02/01/25 13:57, Tomoaki AOKI wrote:
On Thu, 2 Jan 2025 08:41:27 +0100
Guido Falsi wrote:
On 02/01/25 01:38, Tomoaki AOKI wrote:
On Wed, 1 Jan 2025 19:50:50 +0100
Guido Falsi wrote:
Don't see a good reason to force everyone to use an old version.
Anyway the ports tree is open s
this
behaviour.
--
Guido Falsi
do is create a new user on your machine and log
into xfce4 with that user. If that user can see all the fonts, then at
least you know it's most probably an xfce configuration issue.
--
Guido Falsi
On 13/07/21 17:34, Guido Falsi via ports wrote:
On 13/07/21 16:04, Janky Jay, III wrote:
When I open Mousepad, there are a couple additional fonts (that must
come with the application?) such as Sans, Serif and Serto but, again, no
other fonts such as the Artwiz, Terminus, Caladea
On 13/07/21 17:55, Janky Jay, III wrote:
Hi Guido,
On 7/13/21 9:51 AM, Guido Falsi via ports wrote:
On 13/07/21 17:34, Guido Falsi via ports wrote:
On 13/07/21 16:04, Janky Jay, III wrote:
When I open Mousepad, there are a couple additional fonts (that
must
come with the application
es without interfering with the host system installation.
Vagrant can also be helpful in simplifying repetitive tasks with VMs.
--
Guido Falsi
er did the
good work! -- George
Great to hear this.
I have noticed XFCE upstream did a lot of work regarding
internationalization, so it's quite posssible the updates that happened
in the while did fix this too.
--
Guido Falsi
ould
force rebuilding the font caches.
I also see various suggestions to add paths to xorg.conf or xorg.conf.d
Do you have any? I think modern xorg does not need those and does a
pretty good job at autodetecting fonts, such lines could actually
confuse it.
--
Guido Falsi
88 matches
Mail list logo
