OK - RE: Drupal 7.28 => 7.31...
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] > Enviat: dissabte, 11 / octubre / 2014 11:34 > Per a: Albert Gabàs | Astabis > A/c: m...@freebsd.org; po...@freebsd.org > Tema: Re: Drupal 7.28 => 7.31... > > 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.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: is bsd.database.mk out of sync with Uses/pgsql.mk?
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 version 92; valid versions are 8.4 9.0 9.1 9.2 > >9.3 9.4 > >> > >> These messages originate in Mk/Uses/pgsql.mk > >> > >> But Mk/bsd.database.mk claims a different format is correct: > >> > >> # DEFAULT_PGSQL_VER > >> # - PostgreSQL default version, currently 90. > >> > >> > >> Do you agree that the comments in Mk/bsd.database.mk need to updated? > > > >Everything should migrate to USES=pgsql and the code in bsd.database.mk > >should > >just die. > > > > I'm pretty sure I put developer warnings there too about this! > > Chris > Putting warning is ok but you should also driver the migration so far I did most of the migrations. Bapt pgp24N4jcNqag.pgp Description: PGP signature
Re: py-imaging vs. py-pillow
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: --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: > http://freebsd.1045724.n5.nabble.com/py-imaging-vs-py-pillow-tp5954043p5955962.html > > Sent from the freebsd-ports mailing list archive at Nabble.com. > > ___ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > > > -- > William Grzybowski / wg > FreeBSD Ports Committer > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > print/hplip is still building with py-imaging and I had to delete it to get py-opengl to update. I suspect that just changing "py-imaging" to "py-pillow" in Makefile would do the trick. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng-1.3.8: "pkg upgrade" showing some strange errors
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, NO * Solution: delete the folder /usr/compat/linux/usr/share/icons/hicolor Package will then install and the compat/linux/.../hicolor folder will be replaced by a symlink: hicolor -> /usr/local/share/icons/hicolor * "pkg delete -f linux-c6-hicolor-icon-theme" (which I had run before posting) neglected to delete above mentioned folder, which is essentially the same problem that pkg upgrade runs into. The other problem with math/octave-forge seems more complex. "pkg upgrade" finishes the job for this port, but spews out a ton of messages. The port binaries are also extremely slow to finish installing, which is another dimension of strange. The port probably needs revision, but you guys most likely know that already. Regards. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/pkgng-1-3-8-pkg-upgrade-showing-some-strange-errors-tp5956038p5956081.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: print/muttprint
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 texlive to texmf in September. > > /usr/ports/Mk/bsd.tex.mk > > has more info about USE_TEX, so please check that file for your > experiments. Hi, My current ports tree for poudriere is r364424 from August 9. As you say, I see with SVN certain changes in ports/Mk/bsd.tex.mk touching our issue. I will setup a new tree for poudriere and compile only print/muttprint in it. Stay tuned :-) Thanks for your time 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-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng-1.3.8: "pkg upgrade" showing some strange errors
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 existing directory with > non-directory" > > But then I noticed many octave-related ports had given install errors: > "load-octave-pkg: octave is installing ad-1.0.6.tar.gz. > 'dispatch' undefined near line 2 column 1 > error: called from '/usr/local/share/octave/packages/ad-1.0.6/PKG_ADD' in > file /usr/local/share/octave/packages/ad-1.0.6/PKG_ADD near line 2, column 1 > error: called from: > error: /usr/local/share/octave/3.8.1/m/pkg/private/install.m at line 241, > column 5 > error: /usr/local/share/octave/3.8.1/m/pkg/pkg.m at line 394, column 9 > load-octave-pkg: octave is installing ltfat-2.0.1.tar.gz. > panic: Bus error -- stopping myself... > > Are these errors related? Is this a pkgng error, or problem with the > individual ports? This is always a tricky thing for a packaging system to handle -- an existing directory being replaced by a file. pkg(8) won't remove a directory unless it is empty, so it can't create the identically named file. In effect the package is conflicting with an earlier version of itself. Actually, I don't know if the directory in question is empty or not: that would be a good thing to find out. Also if it isn't empty, are the contents owned by other packages awaiting upgrade and would your pkg upgrade run ultimately have removed them? pkg(8) crashing with a buss error is definitely a bug in pkg. However, the whole question of how to replace a directory with a file is mostly a problem with the port: yes, it should be possible to do such things, but it is always going to be fragile and sensible software developers will avoid doing such things. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
pkgng-1.3.8: "pkg upgrade" showing some strange errors
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 noticed many octave-related ports had given install errors: "load-octave-pkg: octave is installing ad-1.0.6.tar.gz. 'dispatch' undefined near line 2 column 1 error: called from '/usr/local/share/octave/packages/ad-1.0.6/PKG_ADD' in file /usr/local/share/octave/packages/ad-1.0.6/PKG_ADD near line 2, column 1 error: called from: error: /usr/local/share/octave/3.8.1/m/pkg/private/install.m at line 241, column 5 error: /usr/local/share/octave/3.8.1/m/pkg/pkg.m at line 394, column 9 load-octave-pkg: octave is installing ltfat-2.0.1.tar.gz. panic: Bus error -- stopping myself... Are these errors related? Is this a pkgng error, or problem with the individual ports? - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/pkgng-1-3-8-pkg-upgrade-showing-some-strange-errors-tp5956038.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Pkg regression (1); also a feature request (SEVERAL)
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 mbuffer --version # 20140302 pkg info ... ... mbuffer # mbuffer-2013.02.20_1 # falsely shows the upgrade as not having been done. thunderbird --version # 31.1.2 pkg info ... ... thunderbird thunderbird-31.1.0_1 # falsely shows the upgrade as not having been done. Each package was installed by a sequence of five or four ports with ended with a failure to install py27-imaging because of the py27-pillow having been installed. This almost never happened the legacy way, or could be fixed or discovered by portmaster or portupgrade or pkgdb -F etc So it seems a serious regression that should be prioritized. . The feature request involves "pkg upgrade" which is now... Ports to be installed (no particular alphabetical order) Ports to be upgraded Ports to be reinstalled (dependency changed) I'd like to see this more at... (appears to be an improvement from here...) Part 1. New installs . Skip this part and proceed to part 2? y/n Ports to be installed PORT because of PORT listed below PORT because of PORT listed below# and alphabetical Ports to be upgraded PORT resulitng in new install PORT PORT resulting in new install PORT Ports to be upgraded (dependencies changed)# and alphabetical PORT resulting in new install PORT PORT resulting in new install PORT Part 2. Do this step now? y/n Ports to be upgraded# alphabetical PORT PORT Ports to be reinstalled # alphabetical PORT PORT J. Bouquet ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: print/muttprint
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. > > > > and yes, when you compile the port directly with > > > > > > # make install > > > > > > 'USE_TEX= texlive' pulls in > > > Tex, but it does not if you compile the ports with poudriere. > > > > 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 texlive to texmf in September. /usr/ports/Mk/bsd.tex.mk has more info about USE_TEX, so please check that file for your experiments. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: print/muttprint
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:
> [...]
>
> > > Can you test if this works in your use-case and report the results ?
>
> Btw, what is your use-case ?
>
> 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:
set print_cmd="muttprint --printer pdf --paper A4 --rem_sig "
muttprint is a Perl script which needs among other tools:
# fgrep system /usr/local/bin/muttprint
system("latex -interaction=nonstopmode mail.tex >> $errorRedirection 2>&1");
system("latex -interaction=nonstopmode mail.tex >> $errorRedirection 2>&1");
system("dvips -t $paperformat -o $Temp{ps} $Temp{dvi} >> $errorRedirection
2>&1")
...
i.e. needs in PATH 'latex' and 'dvips'; at the end it will generate a
Postscript file and hand it over to CUPS which generates for me a PDF
file in disk, which does the above mentioned printer 'pdf' in CUPS (but
could as well print to any other printer defined in CUPS);
this is my use case;
>
> > > and yes, when you compile the port directly with
> >
> > # make install
> >
> > 'USE_TEX= texlive' pulls in
> > Tex, but it does not if you compile the ports with poudriere.
>
> 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.
Thx
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-170-4527211 | / \ - Respect for open standards
| en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: print/muttprint
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. I'm by no means an expert in the TeX ports universe, > so any hint is appreciated. texlive is the default, USE_TEX=texlive no longer exists (and you should have an error if you try to use it) Cheers, Antoine ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: print/muttprint
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 appreciated. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: print/muttprint
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-case and report the results ? > > Btw, what is your use-case ? > > 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 ? > >> > and yes, when you compile the port directly with >> >> # make install >> >> 'USE_TEX= texlive' pulls in >> Tex, but it does not if you compile the ports with poudriere. > > I'm surprised that USE_TEX=texlive in poudriere does not pull it in. > Can you provide a build log to show this ? Hi, Not sure what you are talking about, but USE_TEX=texlive doesn't exit. Cheers, Antoine > >> I brought >> this question up in freebsd-pkg@ but did not got any comments on this. >> >> I can revoke the change in my VM / poudriere and send in a complete log >> of the compilation of print/muttprint if someone is willing to dig into. > > Yes, please. > >> For the moment, I have not found any other solution as the two >> additional lines. > > Well, if it solves your problem, then it's definitly a good sign 8-) > > -- > p...@opsec.eu+49 171 3101372 6 years to > go ! > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: print/muttprint
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 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 ? > > and yes, when you compile the port directly with > > # make install > > 'USE_TEX= texlive' pulls in > Tex, but it does not if you compile the ports with poudriere. I'm surprised that USE_TEX=texlive in poudriere does not pull it in. Can you provide a build log to show this ? > I brought > this question up in freebsd-pkg@ but did not got any comments on this. > > I can revoke the change in my VM / poudriere and send in a complete log > of the compilation of print/muttprint if someone is willing to dig into. Yes, please. > For the moment, I have not found any other solution as the two > additional lines. Well, if it solves your problem, then it's definitly a good sign 8-) -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: print/muttprint
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. A side note: bapt switched from 'latex' to texlive: r350369 | bapt | 2014-04-06 17:42:15 +0200 (dom 06 de abr de 2014) | 3 líneas Support stage Switch from latex to texlive > > Can you test if this works in your use-case and report the results ? > and yes, when you compile the port directly with # make install 'USE_TEX= texlive' pulls in Tex, but it does not if you compile the ports with poudriere. I broough this question up in freebsd-pkg@ but did not got any comments on this. I can revoke the change in my VM / poudriere and send in a complete log of the compilation of print/muttprint if someone is willing to dig into. For the moment, I have not found any other solution as the two additional lines. Thx 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-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: print/muttprint
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 of the two additional run_deps. Can you test if this works in your use-case and report the results ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PKG not quite ready for prime time
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 pointer. >>> >>> What puzzles me is why the problem wasn't fixed for o/s versions >>> prior to 10.0 since it was being made mandatory for those >>> versions. That doesn't seem like good practice. >>> >> We have a winner! <3\ > > I've upgraded countless machines from 9.x to 10.x using freebsd-update > and have never come across this issue. (have done a few 8.x to 10.x > via 9.x and been fine too - but not many of these) > > What upgrade path did you use, what version did you come from, and > what version did you go to? Not talking about changing versions - talking about machines that are forced to use pkg that are not 10.x and the freebsd-update tool was used to patch the box at the same major version. Michelle -- Michelle Sullivan http://www.mhix.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PKG not quite ready for prime time
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 versions prior to 10.0 since it was being made mandatory for those versions. That doesn't seem like good practice. We have a winner! <3\ I've upgraded countless machines from 9.x to 10.x using freebsd-update and have never come across this issue. (have done a few 8.x to 10.x via 9.x and been fine too - but not many of these) What upgrade path did you use, what version did you come from, and what version did you go to? Thanks, Daniel. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PKG not quite ready for prime time
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
>> versions of pkg.
>>
>Pkg itself is compiled, not interpreted like Yum which is Python, so it
>does matter.
> And you of course want to ensure you're installing packages
>built for FreeBSD 9 on your FreeBSD 9 server.
[sigh] Yes. I'm old enough that I'm always sleep-deprived, and
after 8-10 hours of concentrated work I'm so foggy that my brain
goes unserviceable.
>
>The next error you're seeing is this:
>
>> pkg: Error loading trusted certificates
>
>This is due to your missing certificates in /usr/share/keys/pkg which
>are required due to your repository having:
>
> signature_type: "fingerprints",
> fingerprints: "/usr/share/keys/pkg",
>
>You could remove those lines to work around that, but you are lowering
>the security of your system as you cannot verify the integrity of your
>packages anymore. The fix is to populate your /usr/share/keys/pkg. I do
>not know why it did not come populated after your upgrade, but that's a
>discussion for another day. Let's get your keys:
>
># mkdir -p /usr/share/keys/pkg/trusted /usr/share/keys/pkg/revoked
># fetch -o /usr/share/keys/pkg/trusted/pkg.freebsd.org.2013102301
>"https://svnweb.freebsd.org/base/head/share/keys/pkg/trusted/pkg.freebsd.org.2013102301?revision=260605&view=co";
># chown root:wheel
>/usr/share/keys/pkg/trusted/pkg.freebsd.org.2013102301
># chmod 644 /usr/share/keys/pkg/trusted/pkg.freebsd.org.2013102301
Thank you. Those seem to fill in the gap. It's a pity that the
installer for pkg didn't do that part of the job.
>
>
>If you have problems with fetch because of the https you might have to
>use --no-verify-peers but at least compare the certificate and/or ensure
>the contents of the key match what's in the repository
>___
>freebsd-ports@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PKG not quite ready for prime time
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 file
>>>
>> That's your problem. You are missing the signature fingerprints to
>> compare against. As such Pkg is refusing to do anything to prevent MITM
>> attacks.
>>
>> 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 versions
> prior to 10.0 since it was being made mandatory for those
> versions. That doesn't seem like good practice.
>
We have a winner! <3\
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PKG not quite ready for prime time
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 to
>compare against. As such Pkg is refusing to do anything to prevent MITM
>attacks.
>
>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 versions
prior to 10.0 since it was being made mandatory for those
versions. That doesn't seem like good practice.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: py-imaging vs. py-pillow
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 you have not been made aware. > Regards. > > > > > - > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/py-imaging-vs-py-pillow-tp5954043p5955962.html > Sent from the freebsd-ports mailing list archive at Nabble.com. > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- William Grzybowski / wg FreeBSD Ports Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PKG not quite ready for prime time
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 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 to
compare against. As such Pkg is refusing to do anything to prevent MITM
attacks.
You are missing this:
https://www.freebsd.org/security/advisories/FreeBSD-EN-14:03.pkg.asc
freebsd-update can provide it.
>>> Ahh, good point. This is better advice. Even if your system was
>>> supposedly fully up to date freebsd-update would detect this is missing
>>> and repair it as it was part of an SA. This is better advice than my
>>> manual creation method :-)
>>>
>>>
>> Didn't on mine, I ran into the same problem - though it wasn't a show
>> stopper for me as I was trying to use my own repo - which also failed
>> using the docs... and nothing in the debug gave any clues or additional
>> information to the problem. Fortunately, I can read/write code, so I
>> fixed things myself.
>>
>
> Thanks for creating an PR.
>
Actually I noticed about 72 hours ago, and I'm still trying to fix
everything that was broken by the forced change... so there is no way
I'm going to be doing any PRs until that's all done... and 23rd Oct my
boss has me flying to SFO to discuss with the Eng & Ops team about
changing all my servers over from FreeBSD to Redhat - exactly what I
thought they would - been unable to update/patch any of my prod servers
against the Bash bug because the entire build system is broken because
of the 'End of life = This is the day its all going to break' issue...
so not really got any motivation to log any PRs now... or ever again.
Regards,
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: py-imaging vs. py-pillow
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: http://freebsd.1045724.n5.nabble.com/py-imaging-vs-py-pillow-tp5954043p5955962.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PKG not quite ready for prime time
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:
> >>>
> >>>
> find /usr/share/keys/pkg -exec sha256 {} +
>
> >>> No such file
> >>>
> >> That's your problem. You are missing the signature fingerprints to
> >> compare against. As such Pkg is refusing to do anything to prevent MITM
> >> attacks.
> >>
> >> You are missing this:
> >> https://www.freebsd.org/security/advisories/FreeBSD-EN-14:03.pkg.asc
> >>
> >> freebsd-update can provide it.
> >>
> >>
> >>
> >
> > Ahh, good point. This is better advice. Even if your system was
> > supposedly fully up to date freebsd-update would detect this is missing
> > and repair it as it was part of an SA. This is better advice than my
> > manual creation method :-)
> >
>
> Didn't on mine, I ran into the same problem - though it wasn't a show
> stopper for me as I was trying to use my own repo - which also failed
> using the docs... and nothing in the debug gave any clues or additional
> information to the problem. Fortunately, I can read/write code, so I
> fixed things myself.
Thanks for creating an PR.
pgpuYQLYjI3tQ.pgp
Description: PGP signature
Re: print/muttprint
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 it? A PR is always preferred for the audit trail. I committed it, with the change of maintainer mentioned below. Thanks! -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
print/muttprint
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 MAINTAINER is set to po...@freebsd.org it seems that there is no
real maintainer. I'm willing to step in and take it over.
Thx
matthias
*** print/muttprint/Makefile.orig 2014-08-09 12:44:47.0 +0200
--- print/muttprint/Makefile2014-10-11 09:35:41.0 +0200
***
*** 19,24
--- 19,26
OPTIONS_DEFINE= CUPS DOCS
RUN_DEPENDS= psnup:${PORTSDIR}/print/psutils \
+ latex:${PORTSDIR}/print/texlive-full \
+ dvips:${PORTSDIR}/print/tex-dvipsk \
uncompface:${PORTSDIR}/mail/faces \
convert:${PORTSDIR}/graphics/ImageMagick \
p5-TimeDate>=0:${PORTSDIR}/devel/p5-TimeDate \
--
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-170-4527211 | / \ - Respect for open standards
| en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
___
freebsd-ports@freebsd.org mailing list
http://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
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 +-+ astro/gpstk | 2.0 | 2.5 +-+ 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 http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Drupal 7.28 => 7.31...
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.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Update of port definition for YAF
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/yaf/ldapplugin.a Error: Orphaned: lib/yaf/ldapplugin.so Error: Orphaned: lib/yaf/ldapplugin.so.1 Error: Orphaned: lib/yaf/ldapplugin.so.1.0.1 Error: Orphaned: man/man1/ipfixDump.1.gz Have you informed the maintainer, diks...@sfc.wide.ad.jp ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Update of port definition for YAF
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. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: is bsd.database.mk out of sync with Uses/pgsql.mk?
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 originate in Mk/Uses/pgsql.mk >> >> But Mk/bsd.database.mk claims a different format is correct: >> >> # DEFAULT_PGSQL_VER >> # - PostgreSQL default version, currently 90. >> >> >> Do you agree that the comments in Mk/bsd.database.mk need to updated? > >Everything should migrate to USES=pgsql and the code in bsd.database.mk >should >just die. > I'm pretty sure I put developer warnings there too about this! Chris >regards, >Bapt -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
