Dear Kurt,
Thank you very much for your quick reply.
Regards!
--
Albert Gabàs - Astabis
Information Risk Management
Nacional: +34 902 800 872 | Fax: +34 931 980 591
Barcelona: +34 931 980 181 | Madrid: +34 911 333 071
> -Missatge original-
> De: Kurt Jaeger [mailto:p...@opsec.eu]
On Sat, Oct 11, 2014 at 08:45:51AM +0100, Chris Rees wrote:
>
>
> On 28 September 2014 11:36:41 BST, Baptiste Daroussin
> wrote:
> >On Sat, Sep 27, 2014 at 03:52:56PM -0400, Dan Langille wrote:
> >> Today I encountered these build messages with poudriere:
> >>
> >> Invalid PGSQL default versio
On Sat, Oct 11, 2014 at 6:08 AM, William Grzybowski wrote:
> Should be fixed now, small typo in the option depends.
>
> Thanks.
>
> On Sat, Oct 11, 2014 at 9:59 AM, Beeblebrox wrote:
> > Build fails if tiff is enabled (py27-pillow-2.6.0)
> >
> > OPTIONS_FILE_SET+=TIFF
> > Gives: "ValueError: --e
Thanks for the answer, doc!
I thought the linux-c6-hicolor-icon-theme related message was a pkgng internal
(sqlite) complaint. Following your input I have:
* folder ownership - root/wheel
* contents owned by other packages awaiting upgrade? - NO
* would "pkg upgrade" have removed them? - Well, N
El día Saturday, October 11, 2014 a las 07:34:26PM +0200, Kurt Jaeger escribió:
> > > I'm surprised that USE_TEX=texlive in poudriere does not pull it in.
> >
> > Mee too.
> >
> > > Can you provide a build log to show this ?
> >
> > Will do this tomorrow.
>
> There's a commit which changed tex
On 11/10/2014 18:55, Beeblebrox wrote:
> I'm getting several errors during "pkg upgrade" on pkg 1.3.8
>
> At fist I thought this was a port error, because "pkg upgrade" actually
> breaks on this:
> "Installing linux-c6-hicolor-icon-theme-0.5: 0%
> pkg: archive_read_extract(): Can't replace exist
I'm getting several errors during "pkg upgrade" on pkg 1.3.8
At fist I thought this was a port error, because "pkg upgrade" actually
breaks on this:
"Installing linux-c6-hicolor-icon-theme-0.5: 0%
pkg: archive_read_extract(): Can't replace existing directory with
non-directory"
But then I notic
package install this that this that seems to complete most of the installs, but
if one of the ports has a conflict
then the upgrades are not registered. For example, todays conflict between
py-pillow and py-imaging resulted
in (that is, despite of the conflict...) two successful upgrades
mbu
Hi!
> > How do you invoke muttprint and what does it call and what does it do
> > in the end ? Does it really generate a .ps to send to the printer ?
>
> Hi,
>
> I'm using muttprint to print mail from the MUA mutt; the mail is piped
> into the configured print cmd:
[...]
Thanks, this helps.
>
El día Saturday, October 11, 2014 a las 06:28:57PM +0200, Kurt Jaeger escribió:
> Hi!
>
> > > mat@ mailed that
> > >
> > > USE_TEX=latex dvipsk
> > >
> > > should be used instead of the two additional run_deps.
> >
> > A side note:
> >
> > bapt switched from 'latex' to texlive:
> [...]
>
> >
On Sat, Oct 11, 2014 at 6:42 PM, Kurt Jaeger wrote:
> Hi!
>
>> Not sure what you are talking about, but USE_TEX=texlive doesn't exit.
>
> I think Matthias refers to this:
>
> https://lists.freebsd.org/pipermail/svn-ports-all/2014-April/054544.html
>
> where
>
> USE_TEX=texlive
>
> was committed.
Hi!
> Not sure what you are talking about, but USE_TEX=texlive doesn't exit.
I think Matthias refers to this:
https://lists.freebsd.org/pipermail/svn-ports-all/2014-April/054544.html
where
USE_TEX=texlive
was committed. I'm by no means an expert in the TeX ports universe,
so any hint is appr
On Sat, Oct 11, 2014 at 6:28 PM, Kurt Jaeger wrote:
> Hi!
>
>> > mat@ mailed that
>> >
>> > USE_TEX=latex dvipsk
>> >
>> > should be used instead of the two additional run_deps.
>>
>> A side note:
>>
>> bapt switched from 'latex' to texlive:
> [...]
>
>> > Can you test if this works in your use-ca
Hi!
> > mat@ mailed that
> >
> > USE_TEX=latex dvipsk
> >
> > should be used instead of the two additional run_deps.
>
> A side note:
>
> bapt switched from 'latex' to texlive:
[...]
> > Can you test if this works in your use-case and report the results ?
Btw, what is your use-case ?
How do
El día Saturday, October 11, 2014 a las 05:20:16PM +0200, Kurt Jaeger escribió:
Hi,
I have removed Lukas Ruf from the thread because he
said to me that he does not use FreeBSD since ~1995.
> mat@ mailed that
>
> USE_TEX=latex dvipsk
>
> should be used instead of the two additional run_deps.
Hi!
> > I need print/muttprint to print my mails.
> > Should I file a PR with the patch or could someone commit it?
>
> A PR is always preferred for the audit trail. I committed it, with
> the change of maintainer mentioned below.
mat@ mailed that
USE_TEX=latex dvipsk
should be used instead o
Daniel Austin via freebsd-ports wrote:
> Hi,
>
> On 11/10/2014 14:34, Michelle Sullivan wrote:
>> scratch65...@att.net wrote:
You are missing this:
https://www.freebsd.org/security/advisories/FreeBSD-EN-14:03.pkg.asc
freebsd-update can provide it.
>>>
>>> Thank you for the
Hi,
On 11/10/2014 14:34, Michelle Sullivan wrote:
scratch65...@att.net wrote:
You are missing this:
https://www.freebsd.org/security/advisories/FreeBSD-EN-14:03.pkg.asc
freebsd-update can provide it.
Thank you for the pointer.
What puzzles me is why the problem wasn't fixed for o/s version
On Fri, 10 Oct 2014 13:49:54 -0500, you wrote:
>On Fri, Oct 10, 2014, at 13:29, Auld Besom wrote:
>>
>> I had it as ${ABI} to begin with, but had no luck that way either
>> (see below). Then I changed it, unaware that that first 8 was
>> the version, or even that there are o/s version-dependent
scratch65...@att.net wrote:
> On Fri, 10 Oct 2014 14:47:27 -0500, you wrote:
>
>
>> On 10/10/2014 1:12 PM, scratch65...@att.net wrote:
>>
>>> On Fri, 10 Oct 2014 12:57:42 -0500, Brian Drewery wrote:
>>>
>>>
find /usr/share/keys/pkg -exec sha256 {} +
>>> No such fil
On Fri, 10 Oct 2014 14:47:27 -0500, you wrote:
>On 10/10/2014 1:12 PM, scratch65...@att.net wrote:
>> On Fri, 10 Oct 2014 12:57:42 -0500, Brian Drewery wrote:
>>
>>> find /usr/share/keys/pkg -exec sha256 {} +
>>
>> No such file
>
>That's your problem. You are missing the signature fingerprints t
Should be fixed now, small typo in the option depends.
Thanks.
On Sat, Oct 11, 2014 at 9:59 AM, Beeblebrox wrote:
> Build fails if tiff is enabled (py27-pillow-2.6.0)
>
> OPTIONS_FILE_SET+=TIFF
> Gives: "ValueError: --enable-tiff requested but tiff not found, aborting"
>
> Just advising in case
Lars Engels wrote:
> On Sat, Oct 11, 2014 at 12:15:54AM +0200, Michelle Sullivan wrote:
>
>> Mark Felder wrote:
>>
>>> On Fri, Oct 10, 2014, at 14:47, Bryan Drewery wrote:
>>>
>>>
On 10/10/2014 1:12 PM, scratch65...@att.net wrote:
> On Fri, 10 Oct
Build fails if tiff is enabled (py27-pillow-2.6.0)
OPTIONS_FILE_SET+=TIFF
Gives: "ValueError: --enable-tiff requested but tiff not found, aborting"
Just advising in case you have not been made aware.
Regards.
-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context
On Sat, Oct 11, 2014 at 12:15:54AM +0200, Michelle Sullivan wrote:
> Mark Felder wrote:
> > On Fri, Oct 10, 2014, at 14:47, Bryan Drewery wrote:
> >
> >> On 10/10/2014 1:12 PM, scratch65...@att.net wrote:
> >>
> >>> On Fri, 10 Oct 2014 12:57:42 -0500, Brian Drewery wrote:
> >>>
> >>>
Hi!
> I need print/muttprint to print my mails. I'm using 11-CURRENT, ports
> from SVN and poudriere to build them. The Makefile of the port does not
> pull in enough latex infrastructure, a patch is below. With this it
> works fine.
>
> Should I file a PR with the patch or could someone commit i
Hello,
I need print/muttprint to print my mails. I'm using 11-CURRENT, ports
from SVN and poudriere to build them. The Makefile of the port does not
pull in enough latex infrastructure, a patch is below. With this it
works fine.
Should I file a PR with the patch or could someone commit it?
As M
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
Hi!
> Please, update the port to the latest version that fixes security
> vulnerabilities.
Update done.
--
p...@opsec.eu+49 171 3101372 6 years to go !
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd
Hi!
> To whom do I send an updated YAF port definition? I updated the Makefile
> and the distinfo file and ran a build test through poudriere.
Maybe the pkg-plist needs a fix as well ?
===> Checking for items in STAGEDIR missing from pkg-plist
Error: Orphaned: bin/ipfixDump
Error: Orphaned: lib/
Hi!
> To whom do I send an updated YAF port definition?
To bugzilla:
https://bugs.freebsd.org/bugzilla/enter_bug.cgi
> I updated the Makefile
> and the distinfo file and ran a build test through poudriere.
So, if you submit a problem report, also attach the poudriere build logs,
that helps.
-
On 28 September 2014 11:36:41 BST, Baptiste Daroussin wrote:
>On Sat, Sep 27, 2014 at 03:52:56PM -0400, Dan Langille wrote:
>> Today I encountered these build messages with poudriere:
>>
>> Invalid PGSQL default version 92; valid versions are 8.4 9.0 9.1 9.2
>9.3 9.4
>>
>> These messages origi
32 matches
Mail list logo
