while, the past couple of days I've been updating
> > > the ported dependencies to their last versions and fixing their
> > > regression tests. My plan is to submit the port someday this week. If
> > > you'd like to test them already, you can find the ports here:
>
ession tests. My plan is to submit the port someday this week. If
> > you'd like to test them already, you can find the ports here:
> > https://www.thyssentishman.com/git/ports/log.html
>
> I'd like to submit the port(s) today or tomorrow. In total, I'll be
> sub
//www.thyssentishman.com/git/ports/log.html
I'd like to submit the port(s) today or tomorrow. In total, I'll be
submitting 13 ports, so before I send anything I'd like to discuss the
format of the submission. The port dependency tree is the following:
devel/med
graphics/pcl
Le Thu, Oct 03, 2024 at 01:11:40AM +0100, Stuart Henderson a écrit :
> On 2024/10/02 18:52, Christian Schulte wrote:
> > tweak any options in the config editor without reading about what to
> > change, why to change it and what consequences a change has. This is
> > very time consuming and you'd
On 10/3/24 02:11, Stuart Henderson wrote:
> On 2024/10/02 18:52, Christian Schulte wrote:
>
>> example user.js would be very helpful. Normally, you would not want to
>> tweak any options in the config editor without reading about what to
>> change, why to change it and what consequences a change h
to send HTML mails or plaintext messages with format flowed, maybe
> >
> > what makes you think that?
>
> <http://www.openbsd.org/mail.html>
people using OpenBSD to write email don't just use it for OpenBSD mailing
lists.
> Someone using OpenBSD will sooner or late
On 10/2/24 10:26, Stuart Henderson wrote:
> On 2024/10/02 03:51, Christian Schulte wrote:
>> Hello @ports,
>>
>> considering someone using Thunderbird on OpenBSD would very unlikely
>> want to send HTML mails or plaintext messages with format flowed, maybe
>
>
On 2024/10/02 03:51, Christian Schulte wrote:
> Hello @ports,
>
> considering someone using Thunderbird on OpenBSD would very unlikely
> want to send HTML mails or plaintext messages with format flowed, maybe
what makes you think that?
> it would be ok to override some defaults
> On Oct 1, 2024, at 6:53 PM, Christian Schulte wrote:
>
> maybe
> it would be ok to override some defaults
This is always a good place to stop and reconsider an idea.
Hello @ports,
considering someone using Thunderbird on OpenBSD would very unlikely
want to send HTML mails or plaintext messages with format flowed, maybe
it would be ok to override some defaults of Thunderbird to stop it doing
so by default.
Would this be in option for the port?
Index: mail
Hi, ports@:
Here is a patch for devel/p5-DateTime-Format-Natural:
i) Update to 1.18
ii) Add 2 missing DEPENDS
It build well and pass all tests on amd64-current system.
4 ports depend on it:
www/p5-HTML-FormFu and www/p5-XML-Feed build well
and pass all tests with this
On 2023/07/21 15:29, Antoine Jacoutot wrote:
> On Fri, Jul 21, 2023 at 11:59:21AM +0100, Stuart Henderson wrote:
> > On 2023/07/21 12:51, Antoine Jacoutot wrote:
> > > Alright. I will do that.
> >
> > great, thanks! (and sorry about the eztra portroach version spam from me
> > adding the metacpan
On Fri, Jul 21, 2023 at 11:59:21AM +0100, Stuart Henderson wrote:
> On 2023/07/21 12:51, Antoine Jacoutot wrote:
> > Alright. I will do that.
>
> great, thanks! (and sorry about the eztra portroach version spam from me
> adding the metacpan fallback URL, which meant that more ports/versions
> sta
On 2023/07/21 12:51, Antoine Jacoutot wrote:
> Alright. I will do that.
great, thanks! (and sorry about the eztra portroach version spam from me
adding the metacpan fallback URL, which meant that more ports/versions
started hitting this).
;>> On Thu, Jul 20, 2023 at 10:24:10AM +0100, Stuart Henderson wrote:
>>>>> portroach doesn't reliably use the site handler for cpan, various ports
>>>>> (notably those with Foo-Bar-v1.23 format distfile names) fallback to
>>>>> direc
iably use the site handler for cpan, various ports
> > > > (notably those with Foo-Bar-v1.23 format distfile names) fallback to
> > > > directory listing. For example see the "L" instead of "S" for
> > > > p5-Sys-Virt in
> > > > ht
> (notably those with Foo-Bar-v1.23 format distfile names) fallback to
> > > directory listing. For example see the "L" instead of "S" for
> > > p5-Sys-Virt in
> > > https://portroach.openbsd.org/antoine%20jacoutot%20%3cajacou...@openbsd.org%3E.html
&g
On 2023/07/20 14:27, Antoine Jacoutot wrote:
> On Thu, Jul 20, 2023 at 10:24:10AM +0100, Stuart Henderson wrote:
> > portroach doesn't reliably use the site handler for cpan, various ports
> > (notably those with Foo-Bar-v1.23 format distfile names) fallback to
> > dire
On Thu, Jul 20, 2023 at 10:24:10AM +0100, Stuart Henderson wrote:
> portroach doesn't reliably use the site handler for cpan, various ports
> (notably those with Foo-Bar-v1.23 format distfile names) fallback to
> directory listing. For example see the "L" instead of
portroach doesn't reliably use the site handler for cpan, various ports
(notably those with Foo-Bar-v1.23 format distfile names) fallback to
directory listing. For example see the "L" instead of "S" for
p5-Sys-Virt in
https://portroach.openbsd.org/antoine%20jacoutot%2
ere is a patch to create 2 new
> > > > ports:devel/p5-DateTime-Format-Oracle
> > > > and converters/p5-Convert-NLS_DATE_FORMAT. Both are required by the
> > > > update of databases/p5-Rose-DB.
> > > >Both new port build well and pass all tests on amd64
On 2023/03/30 21:03, Alexander Bluhm wrote:
> On Fri, Mar 10, 2023 at 12:08:52AM +0100, Alexander Bluhm wrote:
> > On Wed, Mar 08, 2023 at 02:21:45AM +, wen heping wrote:
> > >Here is a patch to create 2 new ports:devel/p5-DateTime-Format-Oracle
> > >
On Fri, Mar 10, 2023 at 12:08:52AM +0100, Alexander Bluhm wrote:
> On Wed, Mar 08, 2023 at 02:21:45AM +, wen heping wrote:
> >Here is a patch to create 2 new ports:devel/p5-DateTime-Format-Oracle
> > and converters/p5-Convert-NLS_DATE_FORMAT. Both are required by the
On Wed, Mar 08, 2023 at 02:21:45AM +, wen heping wrote:
>Here is a patch to create 2 new ports:devel/p5-DateTime-Format-Oracle
> and converters/p5-Convert-NLS_DATE_FORMAT. Both are required by the
> update of databases/p5-Rose-DB.
>Both new port build well and pass all te
Hi, ports@:
Here is a patch to create 2 new ports:devel/p5-DateTime-Format-Oracle
and converters/p5-Convert-NLS_DATE_FORMAT. Both are required by the
update of databases/p5-Rose-DB.
Both new port build well and pass all tests on amd64-current system.
Cheers !
wen
newports.tar.gz
I've looked a bit more...
if we want to have a bit more specifiers, than what's already in the code,
it wants a bit more love to clean up various things.
The strtol on width is the tip of the iceberg.
ormatting.
>
> On 4 December 2021 12:47:30 Christopher Zimmermann wrote:
>
> > Hi,
> >
> > current ocaml uses %02d format specifier in its autoconf. This is not
> > supported by our base m4. I had no idea how to force autoconf to use
> > devel/m4. So I adde
uses %02d format specifier in its autoconf. This is not
supported by our base m4. I had no idea how to force autoconf to use
devel/m4. So I added support for this flag to base m4. OK?
Alternatively suggestions are welcome how to force use of
/usr/local/bin/gm4 instead of /usr/bin/m4.
Christopher
- long width;
+ int width;
and then:
- width = strtol(argv[pos++], NULL, 10);
+ width = (int)strtol(argv[pos++], NULL, 10);
This is not right.
You need to leave the type as long, and then range check it. I understand
you are uncomfortable
Hi,
current ocaml uses %02d format specifier in its autoconf. This is not
supported by our base m4. I had no idea how to force autoconf to use
devel/m4. So I added support for this flag to base m4. OK?
Alternatively suggestions are welcome how to force use of
/usr/local/bin/gm4 instead of
On 2021/09/14 05:42, Theo Buehler wrote:
> On Tue, Sep 07, 2021 at 09:10:39PM +0100, Stuart Henderson wrote:
> > > devel/libvstr The OpenBSD ports mailing-list
> >
> > I don't remember what libvstr was imported for originally but it's
> > unused in ports, I propose removing it
>
> Conv
On Tue, Sep 07, 2021 at 09:10:39PM +0100, Stuart Henderson wrote:
> > devel/libvstr The OpenBSD ports mailing-list
>
> I don't remember what libvstr was imported for originally but it's
> unused in ports, I propose removing it
Converting it to avoid %n will be a bit of work (18 files w
Stuart Henderson wrote:
> On 2021/09/10 20:38, Stefan Hagen wrote:
> > Indeed. The diff should be discarded.
>
> It does still need something for cdr_drv.c though,
>
> 284 error("Driver types:\n");
> 285 for (d = drivers; *d != (cdr_t *)NULL; d++) {
> 286 error("%s
On 2021/09/10 20:38, Stefan Hagen wrote:
> Indeed. The diff should be discarded.
It does still need something for cdr_drv.c though,
284 error("Driver types:\n");
285 for (d = drivers; *d != (cdr_t *)NULL; d++) {
286 error("%s%n",
^^
287
Theo de Raadt wrote:
> This change is really weird.
>
> %n in a scanning string isn't the same as %n in a format string.
>
> Is clang mistakenly flagging %n in scanning strings? That might be a
> mistake. clang should only be inspecting *printf style format strings.
This change is really weird.
%n in a scanning string isn't the same as %n in a format string.
Is clang mistakenly flagging %n in scanning strings? That might be a
mistake. clang should only be inspecting *printf style format strings.
The change to libc has no impact on scanning st
On Fri, Sep 10, 2021 at 08:03:04PM +0200, Stefan Hagen wrote:
> Hi,
>
> This removes the '%n' format specifier from sysutils/cdrtools.
The warning is about *printf %n, not sscanf %n. The problem is in a
different file, according to naddy's list
./sysutils/cdrtools.log:c
Hi,
This removes the '%n' format specifier from sysutils/cdrtools.
Test: %n is used to align this list and it works like before:
# cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-openbsd7.0) Copyright (C)
1995-2010 J�rg Schilling
Using libscg version 'schily
On Fri, 10 Sep 2021 at 16:29:57 +0200, Christian Weisgerber wrote:
> Here's the list of remaining ports with
>
> warning: '%n' format specifier support is deactivated and will call abort(3)
>
> These need to be fixed before the release.
> net/dnstracer
Here's the list of remaining ports with
warning: '%n' format specifier support is deactivated and will call abort(3)
These need to be fixed before the release.
databases/openldap23The OpenBSD ports mailing-list
devel/adb The OpenBSD ports mailing-list
On Wed, Sep 08, 2021 at 01:37:34PM +0100, Stuart Henderson wrote:
> On 2021/09/07 21:24, Christian Weisgerber wrote:
> > Earlier today, semarie@ committed a change that will now cause base
> > clang to warn when the %n specifier appears in a format string for
> > the printf(3
Stuart Henderson wrote:
> On 2021/09/07 21:24, Christian Weisgerber wrote:
> > Earlier today, semarie@ committed a change that will now cause base
> > clang to warn when the %n specifier appears in a format string for
> > the printf(3) family of functions:
> >
> &g
On 2021/09/07 21:24, Christian Weisgerber wrote:
> Earlier today, semarie@ committed a change that will now cause base
> clang to warn when the %n specifier appears in a format string for
> the printf(3) family of functions:
>
> warning: '%n' format specifier support is
Stuart Henderson:
> henning: do you still use openldap 2.3? if not, the port is a bit of a
> source of problems and it would be helpful to remove it (these days 2.4
> has a backend which is nothing to do with berkeley db which iirc was the
> original problem)
In case we still need it, we can just
h-rts_Stats_c
===
RCS file: patches/patch-rts_Stats_c
diff -N patches/patch-rts_Stats_c
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-rts_Stats_c 7 Sep 2021 20:42:00 -
@@ -0,0 +1,53 @@
+$OpenBSD$
+
+Kill use of %n format specifier.
+
+Index: rts/Sta
ier today, semarie@ committed a change that will now cause base
> clang to warn when the %n specifier appears in a format string for
> the printf(3) family of functions:
>
> warning: '%n' format specifier support is deactivated and will call abort(3)
>
> I already ran a
Earlier today, semarie@ committed a change that will now cause base
clang to warn when the %n specifier appears in a format string for
the printf(3) family of functions:
warning: '%n' format specifier support is deactivated and will call abort(3)
I already ran a full amd64 bulk build
On Mon, Sep 06, 2021 at 02:01:08PM +0100, Stuart Henderson wrote:
> On 2021/09/06 14:48, Marc Espie wrote:
> > On Fri, Sep 03, 2021 at 01:34:57PM -0600, Aaron Bieber wrote:
> > >
> > > Kurt Mosiejczuk writes:
> > >
> > > > On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote:
> > > >
> >
On 2021/09/06 14:48, Marc Espie wrote:
> On Fri, Sep 03, 2021 at 01:34:57PM -0600, Aaron Bieber wrote:
> >
> > Kurt Mosiejczuk writes:
> >
> > > On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote:
> > >
> > >> How many is multiple? :D - the Go stuff is gonna get ugly(er?)!
> > >
> > >>
On Fri, Sep 03, 2021 at 01:34:57PM -0600, Aaron Bieber wrote:
>
> Kurt Mosiejczuk writes:
>
> > On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote:
> >
> >> How many is multiple? :D - the Go stuff is gonna get ugly(er?)!
> >
> >> net/go-ipfs for example, the output is useless because i
On 2021/09/03 15:20, Kurt Mosiejczuk wrote:
> On Fri, Sep 03, 2021 at 06:30:01PM +, Klemens Nanni wrote:
>
> > Put it into a `show-checksums' target so the regular `makesum' does not
> > get slowed down on already big/slow ports?
>
> I don't understand this suggestion. makesum only gets run w
Kurt Mosiejczuk writes:
> On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote:
>
>> How many is multiple? :D - the Go stuff is gonna get ugly(er?)!
>
>> net/go-ipfs for example, the output is useless because it's so big :D
>
> Does go actually publish base64 SHA256 hashes for their mod
On Fri, Sep 03, 2021 at 06:30:01PM +, Klemens Nanni wrote:
> Put it into a `show-checksums' target so the regular `makesum' does not
> get slowed down on already big/slow ports?
I don't understand this suggestion. makesum only gets run when one updates
a port. The existing output it fairly us
On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote:
> How many is multiple? :D - the Go stuff is gonna get ugly(er?)!
> net/go-ipfs for example, the output is useless because it's so big :D
Does go actually publish base64 SHA256 hashes for their modules?
If not, it's not the size of th
On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote:
>
> Kurt Mosiejczuk writes:
>
> > Whenever I update a port or create a new one, to verify the hashes I have
> > to run sha256(1) or md5(1) on the distfile. makesum does display our SHA256
> > has, b
Kurt Mosiejczuk writes:
> Whenever I update a port or create a new one, to verify the hashes I have
> to run sha256(1) or md5(1) on the distfile. makesum does display our SHA256
> has, but we use base64 format and everywhere else (that I've interacted with)
> uses hexadecimal
Whenever I update a port or create a new one, to verify the hashes I have
to run sha256(1) or md5(1) on the distfile. makesum does display our SHA256
has, but we use base64 format and everywhere else (that I've interacted with)
uses hexadecimal format.
This diff makes the makesum target spi
Hi, ports@:
Here is a patch for devel/p5-DateTime-Format-Flexible:
i) Update to 0.33
ii) Remove unneeded RUN_D as per upstream change.
It build well and pass all tests on amd64-current system.
Only one port depend on it, www/p5-XML-Feed, build
well and pass all tests on
Hi, ports@:
Here is a patch for devel/p5-DateTime-Format-ISO8601:
i) Update to 0.15
ii) Update DEPENDS
It build well and pass all tests on amd64-current system.
Two ports depends on it:
databases/p5-Jifty-DBI
net/p5-RPC-XML
Both build well and pass all tests with
Hi, ports@:
Here is a simple patch for devel/p5-DateTime-Format-Flexible to update to
0.32.
It build well and pass all tests on amd64-head system.
No other ports depend on it.
Comments? OK?
wen
Index: Makefile
===
RCS file
On Thu, 4 Jul 2019 11:43:52 +0100
Stuart Henderson wrote:
> On 2019/07/04 00:24, wen heping wrote:
> > Hi, ports@:
> >
> > Here is an patch to create devel/p5-DateTime-Format-Flexible,
> > which is needed by the update of p5-XML-Feed.
> >It build well
On 2019/07/04 00:24, wen heping wrote:
> Hi, ports@:
>
> Here is an patch to create devel/p5-DateTime-Format-Flexible, which is
> needed by the
> update of p5-XML-Feed.
>It build well and passed all tests on my amd64-head system.
>
>Comments? OK?
>
> Regards,
> wen
>
>
OK sthen@
Hi, ports@:
Here is an patch to create devel/p5-DateTime-Format-Flexible, which is
needed by the
update of p5-XML-Feed.
It build well and passed all tests on my amd64-head system.
Comments? OK?
Regards,
wen
p5-DateTime-Format-Flexible-p0.tar.gz
Description: p5-DateTime-Format
On Wed, May 15, 2019 at 01:32:34AM +0200, Charlene Wendling wrote:
> Here is another quick update for Text::Format.
>
> The only upstream change is a move to Dist::Zilla for distribution [0].
>
> Port-wise it's also a simple update.
>
> Testing:
>
> - &#
Here is another quick update for Text::Format.
The only upstream change is a move to Dist::Zilla for distribution [0].
Port-wise it's also a simple update.
Testing:
- 'make test' passes
- there are 2 consumers: net/p5-Net-eBay and www/p5-Object-eBay.
They pass their tests
Here is an update for String::Format.
What's new upstream [0]:
- tooling changes that don't impact downstream
- fix "Unescaped left brace in regex is deprecated here
(and will be fatal in Perl 5.32)". It's very needed
because some tests on other ports are fai
t with clang, successfully, but it fails at runtime.
> > This is what i get, even with a simple "hello world", on OpenBSD
> > 6.4-current (GENERIC)
> > #263 (2018/11/09):
> >
> > $ ./hello
> > ld.so: hello: unsupported insecure BSS PLT o
t;hello world", on OpenBSD 6.4-current (GENERIC)
> #263 (2018/11/09):
>
> $ ./hello
> ld.so: hello: unsupported insecure BSS PLT object
>
> Recently, support for BSS PLT format has been deleted [3].
>
> Is it possible to fix clang so we get binaries that work at runtime?
to build
a port with clang, successfully, but it fails at runtime. This is what i
get, even with a simple "hello world", on OpenBSD 6.4-current (GENERIC)
#263 (2018/11/09):
$ ./hello
ld.so: hello: unsupported insecure BSS PLT object
Recently, support for BSS PLT format has been delete
Hi Jeremie,
Jeremie Courreges-Anglas wrote on Sun, Aug 26, 2018 at 03:15:48AM +0200:
> On Sat, Aug 25 2018, Ingo Schwarze wrote:
[...]
>> So i think it is time for groff to switch over to install manual
>> page sources and have mandoc do the formatting on demand like for
>> (almost) every other
On Sat, Aug 25 2018, Ingo Schwarze wrote:
> Hi,
Hi Ingo,
> you may have noticed a flurry of mandoc commits lately: mandoc is now
> able to format the manual pages of the GNU troff package. As usual,
> a few unimportant formatting differences remain, mostly whitespace,
> b
Hi,
you may have noticed a flurry of mandoc commits lately: mandoc is now
able to format the manual pages of the GNU troff package. As usual,
a few unimportant formatting differences remain, mostly whitespace,
but nothing very serious.
So i think it is time for groff to switch over to install
Original Message
Subject: [dvd+rw-tools][error][openbsd] why do I have to restart the
computer after a dvd + rw-format
Date: 2018-02-14 11:49
From: david-mau...@netdefi.com
To: ap...@fy.chalmers.se
Hello,
why do I have to restart the computer after a dvd + rw-format
before
Fri, 25 Mar 2016 20:27:08 -0700 Jeremy Evans
> On Fri, Mar 25, 2016 at 10:47 AM, Chris Bennett <
> chrisbenn...@bennettconstruction.us> wrote:
>
> > With this format, I have to copy/paste each rm -rf, groupdel, etc by hand.
> > Could these messages be changed to s
estion.
Having this change would encourage copy-paste tempting practice, which
is neither safe nor practical.
Processing the output with simple tools like cut and xargs is at your
disposal, if you are so burdened for a couple of repetitions.
> > > With this format, I have to copy/paste each
Fri, 25 Mar 2016 12:47:01 -0500 Chris Bennett
> After I delete packages, especially pkg_delete -X, I get a long list of
> instructions like:
>
You should also run rm -rf /
>
> With this format, I have to copy/paste each rm -rf, groupdel, etc by hand.
> Could these mess
On Sat, Mar 26, 2016 at 10:34:46AM +, Stuart Henderson wrote:
> On 2016/03/25 12:47, Chris Bennett wrote:
> > After I delete packages, especially pkg_delete -X, I get a long list of
> > instructions like:
>
> ..
>
> You know you can use pkg_delete -c if you want to remove these extra
> files?
On 2016/03/25 12:47, Chris Bennett wrote:
> After I delete packages, especially pkg_delete -X, I get a long list of
> instructions like:
..
You know you can use pkg_delete -c if you want to remove these extra
files?
On Fri, Mar 25, 2016 at 10:47 AM, Chris Bennett <
chrisbenn...@bennettconstruction.us> wrote:
> With this format, I have to copy/paste each rm -rf, groupdel, etc by hand.
> Could these messages be changed to something easier to use like:
>
>
> --- -hplip-3.16.2 ---
|| true
> --- -net-snmp-5.7.3p6 ---
> You should also run rm -rf /var/net-snmp/*
> --- -sane-backends-1.0.25p2 ---
> You should also run rm -rf /var/spool/lock/sane/*
>
> With this format, I have to copy/paste each rm -rf, groupdel, etc by hand.
> Cou
On Fri, Mar 25, 2016 at 04:51:40PM -0400, dan mclaughlin wrote:
> the magic of unix; you can work around this with some sed.
Funny how we never see the obvious thing right in front of us. I do
this sort of stuff all of the time, just never occurred to me to do
it here. Thanks.
That's why I always
a diff to prevent this. Not sure if it was committed.
> > With this format, I have to copy/paste each rm -rf, groupdel, etc by hand.
> > Could these messages be changed to something easier to use like:
> >
> rm -rf /
> >
> > This would make these commands very si
rue
--- -net-snmp-5.7.3p6 ---
You should also run rm -rf /var/net-snmp/*
--- -sane-backends-1.0.25p2 ---
You should also run rm -rf /var/spool/lock/sane/*
With this format, I have to copy/paste each rm -rf, groupdel, etc by hand.
Could these messages be changed
Hi,
This diff updates p5-Email-Date-Format to the latest release.
- take maintainer
Comments ? OK ?
Cheers,
benoit
Index: Makefile
===
RCS file: /cvs/ports/mail/p5-Email-Date-Format/Makefile,v
retrieving revision 1.4
diff -u -p
On Tue, Jul 01, 2014 at 11:11:45AM +0100, Stuart Henderson wrote:
> On 2014/07/01 11:57, Marc Espie wrote:
> > I've just switched on "out-of-order" packages, after much testing.
> >
> > What this means:
> >
> > new packages won't be compatible with older pkg_add. Most specifically,
> > the plist
On 2014/07/01 11:57, Marc Espie wrote:
> I've just switched on "out-of-order" packages, after much testing.
>
> What this means:
>
> new packages won't be compatible with older pkg_add. Most specifically,
> the plist order may no longer match the packing-list.
>
> -> if you see strange pkg_add e
I've just switched on "out-of-order" packages, after much testing.
What this means:
new packages won't be compatible with older pkg_add. Most specifically,
the plist order may no longer match the packing-list.
-> if you see strange pkg_add errors, and your base system is not uptodate,
that's you
ok.
On 2014/03/15 16:18, Andrew Fresh wrote:
> And take maintinership.
>
> OK?
definitely :)
And take maintainership.
OK?
Update due to test breakage with the newer p5-DateTime
Index: devel/p5-DateTime-Format-Strptime//Makefile
===
RCS file: /cvs/ports/devel/p5-DateTime-Format-Strptime/Makefile,v
retrieving revision 1.15
And take maintinership.
OK?
Tests don't pass with the newer p5-DateTime.
Index: devel/p5-DateTime-Format-Builder/Makefile
===
RCS file: /cvs/ports/devel/p5-DateTime-Format-Builder/Makefile,v
retrieving revision 1.10
diff -u
On Sat, 7 Dec 2013 10:46:13 +, Stuart Henderson wrote:
> On 2013/12/06 17:05, Michael Brown wrote:
> > On 02/12/13 14:59, Jiri B wrote:
> > ># gmake bin/undionly.kpxe
> > > [BIN] bin/undionly.kpxe.bin
> > > [ZINFO] bin/undionly.kpxe.zinfo
> > > [ZBIN] bin/undionly.kpxe.zbin
> > >Add at 0x
On 2013/12/06 17:05, Michael Brown wrote:
> On 02/12/13 14:59, Jiri B wrote:
> ># gmake bin/undionly.kpxe
> > [BIN] bin/undionly.kpxe.bin
> > [ZINFO] bin/undionly.kpxe.zinfo
> > [ZBIN] bin/undionly.kpxe.zbin
> >Add at 0x787 outside output buffer
> >Makefile.housekeeping:1052: recipe for targe
On 02/12/13 14:59, Jiri B wrote:
# gmake bin/undionly.kpxe
[BIN] bin/undionly.kpxe.bin
[ZINFO] bin/undionly.kpxe.zinfo
[ZBIN] bin/undionly.kpxe.zbin
Add at 0x787 outside output buffer
Makefile.housekeeping:1052: recipe for target 'bin/undionly.kpxe.zbin' failed
gmake: *** [bin/undionly.k
Oops, forgotten attachment :)
> Till now OK, in attachment there's my WIP port.
jirib
ipxe.tar.gz
Description: application/tar-gz
On Mon, Dec 02, 2013 at 04:46:58PM +, Stuart Henderson wrote:
> On 2013/12/02 09:59, Jiri B wrote:
> > On Sun, Dec 01, 2013 at 06:35:24AM -0500, Jiri B wrote:
> > > [...complains about 3 yrs old source...]
>
> This 06:35 mail didn't make it through, and the 09:59 mail doesn't make a lot
> of s
On Sun, Dec 01, 2013 at 06:35:24AM -0500, Jiri B wrote:
> [...complains about 3 yrs old source...]
I was using old source (v1.0.0). With todays git version it fails here:
-%-
# gmake bin/undionly.kpxe
[BIN] bin/undionly.kpxe.bin
[ZINFO] bin/undionly.kpxe.zinfo
[ZBIN] bin/undi
Hi,
This diff updates p5-DateTime-Format-Strptime to the latest release 1.52.
Tested on amd64, regression ok.
Comments ? OK ?
Cheers,
benoit
Index: Makefile
===
RCS file: /cvs/ports/devel/p5-DateTime-Format-Strptime/Makefile,v
Hi,
This diff updates p5-DateTime-Format-Builder to the latest release 0.80.
Tested on amd64, regression ok.
Comments ? OK ?
Cheers,
benoit
Index: Makefile
===
RCS file: /cvs/ports/devel/p5-DateTime-Format-Builder/Makefile,v
Still waiting for an OK.
On Mon, Oct 01, 2012 at 02:35:32AM +0200, Alexander Bluhm wrote:
> Hi,
>
> - update p5-Time-Format to 1.12
> - use no groff
> - patch broken tests
>
> For some reasons the regression tests produced errors like this.
> Can't locate packa
1 - 100 of 137 matches
Mail list logo
