Re: Port: astro/sunclock: Malaysia is in the wrong time zone

[Greg 'groggy' Lehey]

On Sunday, 21 March 2021 at 14:39:41 +0800, Erich Dollansky wrote:
> On Sun, 21 Mar 2021 17:03:30 +1100
> raf  wrote:
>
>> On Sun, Mar 21, 2021 at 11:31:34AM +0800, Erich Dollansky
>>  wrote:
>>
>>> Hi,
>>>
>>> I just noticed that Malaysia is in the same time zone as Jawa
>>> (Indonesia) and Thailand.  Wikipedia says for Malaysia UTC+8 and for
>>> Jawa and Thailand UTC + 7.
>>>
>>> Is there no maintainer for this port as this list is listed as
>>> maintainer.
>>
>> I don't know anything about the sunclock port on
>> FreeBSD, but I have been using it on Linux and macOS
>> for decades, so I thought I pipe up.
>>
>> Part of Malaysia (the part containing Kuala Lumpur) is
>> directly South of Thailand, so it wouldn't be
>> surprising if that part had the same timezone as
>
> Malaysia is in the wrong time zone just as Singapore.

Malaysia and Singapore are in the correct time zones, UTC+8.  So is
Thailand.  That's what their governments decided.  Time zones have
only a passing similarity with solar time.  In (West) Malaysia's case,
they decided to adopt the East Malaysian time to get rid of the
discrepancy.  Before that, it was UTC+7:30 in the west and UTC+8 in
the east.  You can find all this in so many places, but the easiest
might be
https://www.timetemperature.com/time-zone-maps/large-world-time-zone-map.shtml
or https://en.wikipedia.org/wiki/Malaysia.

>> Perhaps the other part (around Brunei) has a different time zone,
>> and Wikipedia is referring to that part? If so, maybe Wikipedia is
>> incomplete?

No, Wikipedia is correct in this case.  So is the tz database at
/usr/src/contrib/tzdata/asia

>> I must admit, I don't know where to see timezone information in
>> sunclock. I can click on places, and it shows the solar time, which
>> makes sense, and the solar time between the two parts of Malaysia
>> are about an hour apart.
>>
>> Ah, it's in the Sunclockrc file. But it only seems to
>> store timezones for cities, not countries, and I think
>> the only Malaysian city it has is Kuala Lumpur.
>
> Yes, and the information given for Bangkok, Kuala Lumpur and Jakarta
> are correct.

FWIW, since 1 January 1982 Malaysia has only one time zone, with
offset UTC+8.  Singapore chose to go with Malaysia on the same date.

>> It contains these lines (for part of Malaysia and
>> Thailand):
>>
>>   addcity 2|KualaLumpur|3.133|101.700|PST-8
>>   addcity 2|Bangkok|13.833|100.483|TST-7
>>
>> You'd think that they'd have their own timezone
>> abbreviations, and not have to borrow abbreviations
>> from other countries so many timezones away. I don't
>> even know what TST is supposed to mean.
>
> The time zone abbreviations are also unknown to me.

Indeed, it doesn't inspire confidence.

>> The manpage says that the timezone needs to be the name
>> of a file under /usr/share/zoneinfo (or whatever
>> directory is used on your system). So it should accept
>> "Asia/Kuala_Lumpur" instead of "PST-8".
>>
>> Can you see if that works? If so, I'd be willing to do
>> an audit and update all of the timezones in Sunclockrc
>> to use the modern, geographic names for timezones. It
>> would take a while, though.
>
> We first would have to get an idea of where to look. When showing
> the map, Malaysia should share the colour with China. But it shares
> its colour with Thailand an the western part of Indonesia.

I've lost track of the map, but it's not important.  There's no
dispute about the time zones in the four countries (except that
Indonesia has several time zones, and only Waktu Indonesia Tengah
matches Malaysia.  But Java is in Waktu Indonesia Barat, UTC+7).

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Port upgrade: dead in the water

[Greg 'groggy' Lehey]

On Friday, 15 January 2021 at 22:16:44 -0600, Kyle Evans wrote:
> On Fri, Jan 15, 2021 at 10:00 PM Greg 'groggy' Lehey  wrote:
>>
>> After years I have finally got round to upgrading my main computer.
>> My intention is to upgrade the ports as well, but pkg doesn't want to
>> play nice:
>>
>>   # pkg-static install -f pkg
>>   pkg-static: Warning: Major OS version upgrade detected.  Running 
>> "pkg-static install -f pkg" recommended
>>  ...
>> I'm happy to blow everything away, but is there a way to extract
>> something that pkg can use to determine which packages to install?
>
> `pkg bootstrap -f` should recover pkg to something usable

Thanks.  That seems to help.

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Port upgrade: dead in the water

[Greg 'groggy' Lehey]

After years I have finally got round to upgrading my main computer.
My intention is to upgrade the ports as well, but pkg doesn't want to
play nice:

  # pkg-static install -f pkg
  pkg-static: Warning: Major OS version upgrade detected.  Running "pkg-static 
install -f pkg" recommended
  Updating FreeBSD repository catalogue...
  pkg-static: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
  pkg-static: Repository FreeBSD load error: meta cannot be loaded No error: 0
  Fetching meta.txz: 100%916 B   0.9kB/s00:01
  pkg-static: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
  repository FreeBSD has no meta file, using default settings
  Fetching packagesite.txz: 100%6 MiB 582.8kB/s00:11
  pkg-static: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
  pkg-static: Repository FreeBSD load error: meta cannot be loaded No error: 0
  Unable to open created repository FreeBSD
  Unable to update repository FreeBSD
  Error updating repositories!

I'm happy to blow everything away, but is there a way to extract
something that pkg can use to determine which packages to install?

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

xtset raison d'etre (was: Aggressive ports removal)

[Greg 'groggy' Lehey]

On Monday, 31 August 2020 at  8:03:32 +1000, Dave Horsfall wrote:
> [ I seem to have missed the post to which this refers ]

Sorry, I nearly missed this one because you didn't change the Subject:
line.

> On Sun, 30 Aug 2020, Niclas Zeising wrote:
>>> Exactly.  Another case in point: x11/xtset.  Maintenance stopped in
>>> 1993, 11 days after the FreeBSD project came into existence.  It works

Well, no, he quoted:

On Sunday, 30 August 2020 at  9:27:07 +1000, Greg 'groggy' Lehey wrote:
>
> Exactly.  Another case in point: x11/xtset.  Maintenance stopped in
> ...

> What does "xtset" do that the following script does not?  I picked it up
> from $JOB a couple of decades ago.
>
>  /usr/local/bin/wintit:
> ...

It inserts text in the same control sequence, but formats them based
on format “metavariables".  From the man page (which I'll send you
separately):

   xtset -t %u (%T) %h:%D

 might set the title text to

   root (ttyp0) myhost:usr/src

Clearly it's not rocket science, which is why it has worked well until
some wise person decided that predicates are no longer acceptable in C
(see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249017).  It
still works well.

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Aggressive ports removal (was: svn commit: r546907 - head/x11-clocks/wmtime)

[Greg 'groggy' Lehey]

Sorry for the length of the quotes, but I've added people who might
not have seen the (relatively long) thread on this subject.  This
seems the best message to refer to.

On Saturday, 29 August 2020 at 16:09:12 +0200, Stefan Esser wrote:
> Am 29.08.20 um 15:32 schrieb Niclas Zeising:
>> On 2020-08-29 14:48, Michael Gmelin wrote:
>>> As I???ve seen quite a lot of similar commits:
>>>
>>> Is our policy now to deprecate ports (with one month notice) that
>>> aren???t maintained/have a dead upstream, even though the ports still
>>> work okay and aren???t the type that requires much maintenance anyway?
>>>
>>
>> Hi!
>> As far as I know, there is no official policy, this was something that
>> Tobias (tcberner@) and I (mostly I) agreed on, since we're doing a lot
>> of the lifting when it comes to -fno-common.
>>
>> However, there is a lot of stale, old, unmaintained and possibly broken
>> software in the Ports tree, and I viewed this as a chance to clean out
>> some of the cruft.  All these ports take resources from people needing
>> to fix them, from the build cluster which is building them, and so on.
>> Since there is no upstream fix for -fno-common, and there is no
>> maintainer, I thought it would be a good idea to deprecate such ports,
>> since there is no apparent interest in them.  -fno-common is the new
>> standard way of building C code (both llvm 11 and gcc 10 defaults to
>> it).  If someone is interested in the port, they can easily submit a PR
>> to maintain the port and remove the deprecation (or commit the fix, if
>> they are a FreeBSD committer).
>> If they are removed, and someone in the future decides to take care of
>> one (or more) of them, they can easily be resurrected, since they will
>> live on in SVN (and git) history.
>
> No maintainer and no changes for a long time does not imply that there
> is no interest in a port!
>
> If it just works, serves its purpose for those using a minimal X11
> environment (there are still twm users) and there is no indication
> of a lingering security problem, then why depreciate and later delete
> such a working port?

Exactly.  Another case in point: x11/xtset.  Maintenance stopped in
1993, 11 days after the FreeBSD project came into existence.  It works
fine, and I find it very useful.  If at some time in the future it
should no longer work with the latest and greatest iteration of the C
programming language or ports structure, that shouldn't be a reason to
discard it.

My suggestion:

  1. Decisions to deprecate remove ports should be made only by
 portmgr@.
  2. Ports are not broken because they don't easily adapt to some new
 ports framework.
  3. Ports should not be removed without community consultation, which
 should last for at least n months, with m reminders being sent.

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Gratuitous port splitting (was: Port Avidemux)

[Greg 'groggy' Lehey]

On Friday, 22 May 2020 at 21:38:44 -0700, Kevin Oberman wrote:
> On Fri, May 22, 2020 at 1:55 PM Wiebe Pestman  wrote:
>
>> Dear maintainer(s),
>> Today I tried to install the port avidemux-2.7.4_1, but unfortunately
>> without success.
>> When running the command "make install" the whole process proceeds
>> without any error message.
>> But at the end there is no binary ...
>> Neither in /usr/local/bin, nor in
>>
>> /usr/ports/multimedia/avidemux/work/stage/usr/local/bin
>>
>> Am I overlooking something in the installation procedure?
>> The kernel on my machine is:
>>
>> FreeBSD zwaluw 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC amd64
>>
>> Hope to get an answer from you :-)
>> Best regards from Holland,
>> Wiebe Pestman
>
> avidemux does not install any executable. Oddly, it just installs libraries
> and the like. You must also install avidemux-plugins and  either or both
> avidemux-cli and avidemux-qt5. If you only need the GUI, you can skip
> avidemux-cli.
>
> The command to run the GUI version of avidemux is avidemux3_qt5. The CLI
> interface is avidemux3_cli.

Yes, I've run into this problem too.  Arguably it's broken.  The
official documentation expects it to be a single installation, and I
don't see any reason to split avidemux into five ports (there's also
avidemux-qt4).  What good is the avidemux port on its own?  Or the
combination of avidemux-qt5 without avidemux-plugins?  Just finding
out that you need all this stuff is a pain.  I'd recommend folding
both of these ports, and probably avidemux-cli, into the ports
avidemux-qt4 and avidemux-qt5.

At the very least there should be a warning in avidemux/pkg-descr, but
I don't think that's the right approach.

Thoughts?
Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Pkg repository is broken...

[Greg 'groggy' Lehey]

On Saturday,  7 March 2020 at 23:55:33 +0100, Michael Gmelin wrote:

[More irrelevant text deleted, also dropping current@]

Is it really so difficult to trim your replies?

>> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey  wrote:
>>
>> ???On Saturday,  7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote:
>>> This was only an issue on the "latest" branch. If you don't alter
>>> "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly"
>>> branch, which fortunately wasn't affected.
>>
>> No, this isn't necessarily correct.  I have never modified this file,
>> but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest
>> with this revision string:
>>
>>  # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z 
>> bdrewery $
>>
>> Despite the age, this appears to identical to the current version,
>> according to svn blame.  Arguably this should be the default anyway.
>
> Installing 12.1 from install media gives you quarterly.

Yes, quite possibly.  But as I said, it's not always the case.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Pkg repository is broken...

[Greg 'groggy' Lehey]

On Saturday,  7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote:

[much irrelevant text deleted]

People, please trim your replies.  Only relevant text should remain

> On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble  wrote:
>>
>> I installed 12.1 on a new laptop yesterday, I have not experienced
>> issues with pkg.
>
> This was only an issue on the "latest" branch. If you don't alter
> "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly"
> branch, which fortunately wasn't affected.

No, this isn't necessarily correct.  I have never modified this file,
but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest
with this revision string:

  # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z 
bdrewery $

Despite the age, this appears to identical to the current version,
according to svn blame.  Arguably this should be the default anyway.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Pkg repository is broken...

[Greg 'groggy' Lehey]

On Friday,  6 March 2020 at 12:29:44 +0100, Lars Engels wrote:
> On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote:
>>
>> Any workarounds in the meantime?  This must affect a lot of people,
>> including those who use 12-:
>>
>>   pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64
>>   pkg: repository FreeBSD contains packages with wrong ABI: 
>> FreeBSD:12.0:amd64
>
> Still broken for me on 12.1.

Strange.  Mine cleared up automatically the following day.

It's also strange how few replies I have received.  Two private
messages (why?), yours, and that was it.  You'd think that people
would be screaming.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Pkg repository is broken...

[Greg 'groggy' Lehey]

On Monday,  2 March 2020 at 17:58:01 +, marco wrote:
> On Sun, Mar 01, 2020 at 04:50:59PM -0500, you (Brennan Vincent) sent the 
> following to [freebsd-current] :
>> Apparently something has its ABI erroneously listed as FreeBSD:13.0:amd64
>> instead of FreeBSD:13:amd64.
>>
>> ```
>> $ sudo pkg update -f
>> Updating FreeBSD repository catalogue...
>> Fetching meta.conf: 100%163 B   0.2kB/s00:01
>> Fetching packagesite.txz: 100%6 MiB   6.4MB/s00:01
>> Processing entries:  72%
>> pkg: wrong architecture: FreeBSD:13.0:amd64 instead of FreeBSD:13:amd64
>> pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:13.0:amd64
>> Processing entries: 100%
>> Unable to update repository FreeBSD
>> Error updating repositories!
>
> Ran into this very same problem today too.
> Just learned on #freebsd that the repos are temporarily borked and
> people are working hard to fix it.

Any workarounds in the meantime?  This must affect a lot of people,
including those who use 12-:

  pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64
  pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: [package - head-i386-default][graphics/hugin] Failed for hugin-2019.0.0_1 in build

[Greg 'groggy' Lehey]

I've received a number of these messages.  Based on the fact that they
seem to be a jail mismatch, I assume that this has nothing to do with
the port itself.  Can somebody confirm or deny this?  If I need to do
something, please explain.

Greg

On Friday, 19 April 2019 at  7:16:33 +, pkg-fall...@freebsd.org wrote:
> You are receiving this mail as a port that you maintain
> is failing to build on the FreeBSD package build server.
> Please investigate the failure and submit a PR to fix
> build.
>
> Maintainer: g...@freebsd.org
> Last committer: jbe...@freebsd.org
> Ident:  $FreeBSD: head/graphics/hugin/Makefile 498698 2019-04-12 
> 06:36:31Z jbeich $
> Log URL:
> http://beefy11.nyi.freebsd.org/data/head-i386-default/p499228_s346255/logs/hugin-2019.0.0_1.log
> Build URL:  
> http://beefy11.nyi.freebsd.org/build.html?mastername=head-i386-default=p499228_s346255
> Log:
>
> =>> Building graphics/hugin
> build started at Fri Apr 19 06:55:36 UTC 2019
> port directory: /usr/ports/graphics/hugin
> package name: hugin-2019.0.0_1
> building for: FreeBSD head-i386-default-job-02 13.0-CURRENT FreeBSD 
> 13.0-CURRENT 1300018 i386
> maintained by: g...@freebsd.org
> Makefile ident:  $FreeBSD: head/graphics/hugin/Makefile 498698 2019-04-12 
> 06:36:31Z jbeich $
> Poudriere version: 3.2.8-3-g02cc9753
> Host OSVERSION: 139
> Jail OSVERSION: 1300018
> Job Id: 02
>
> !!! Jail is newer than host. (Jail: 1300018, Host: 139) !!!
> !!! This is not supported. !!!
> !!! Host kernel must be same or newer than jail. !!!
> !!! Expect build failures. !!!

--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: All those notes...

[Greg 'groggy' Lehey]

On Monday,  8 January 2018 at  8:48:04 +1100, Dave Horsfall wrote:
> I'm not quite sure what happened since my last weekly "pkg update" etc but
> it sure got busy:
>
>  Checking for upgrades (198 candidates): 100%
>  Processing candidates (198 candidates): 100%
>  The following 110 package(s) will be affected (of 0 checked):
>
> ...
>
> This was accompanied by zillions of notes, warning me to "do this" and
> "avoid doing that" etc.  Err, were those notes squirreled away somewhere,
> or do I have to hope that I don't lose the window and its scrollback
> buffer?

I pipe the output of pkg to a file.  It's worth the trouble.  I don't
know any other way to keep track of what this particular instance did.
The notes themselves are in the pkg-message file for the individual
ports.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: License and adopting software

[Greg 'groggy' Lehey]

[format recovered]

On Sunday, 10 December 2017 at 23:31:33 -0800, Chris H wrote:
> On Mon, 11 Dec 2017 12:24:53 +0800 "blubee blubeeme"  
> said
>> On Mon, Dec 11, 2017 at 12:21 PM, Jonathan Chen  wrote:
>>> On 11 December 2017 at 17:17, blubee blubeeme  wrote:
 I like some old software that's <= GPL2 but it seems like the original
 developer is not and have not done any work on the software sine mid
 2000.

 I'd like to pick up the project, fix bugs BUT i'd like to migrate
 from GPL to BSD license.

 How does one go about doing that? I have seen the GPL code but it
 could be re-written how would that affect me re-writing the code
 with a new copy center license?
>>>
>>> You basically have to get the original author to reassign copyright to
>>> you; after which you can do whatever you like to it. If you're basing
>>> your new work on the original work, you have to respect the LICENCE
>>> that it came with.
>
> It's also worth noting; you can dual-license it. That is:
> their code == their license
> your code (additions) == your license

No, you can't.  Read the conditions of the GPL license.  If you add
code to a GPL product, the additions become subject to the GPL.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: License and adopting software

[Greg 'groggy' Lehey]

On Monday, 11 December 2017 at 12:24:53 +0800, blubee blubeeme wrote:
> On Mon, Dec 11, 2017 at 12:21 PM, Jonathan Chen  wrote:
>
>> On 11 December 2017 at 17:17, blubee blubeeme  wrote:
>>> I like some old software that's <= GPL2 but it seems like the
>>> original developer is not and have not done any work on the
>>> software sine mid 2000.
>>>
>>> I'd like to pick up the project, fix bugs BUT i'd like to migrate
>>> from GPL to BSD license.
>>>
>>> How does one go about doing that? I have seen the GPL code but it
>>> could be re-written how would that affect me re-writing the code
>>> with a new copy center license?

If you rewrite the code from scratch, you can apply any license you
like, as long as you don't copy *any* of the code.  Determination of
whether you have done so or not is tricky, and you can end up creating
bike sheds.

>> You basically have to get the original author to reassign copyright
>> to you; after which you can do whatever you like to it. If you're
>> basing your new work on the original work, you have to respect the
>> LICENCE that it came with.
>>
> There has been no update since 2005 and I've tried many times this year to
> get in touch w/ the original author. There has been no response, that's why
> I am asking here.

Unfortunately, without the agreement of all parties who have
contributed to the software, you can't change the license.  Is GPL
such a big deal?

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: make reinstall does not work

[Greg 'groggy' Lehey]

On Sunday, 10 December 2017 at 20:32:38 +0100, Walter Schwarzenfeld wrote:
> Look at the link in Shawn Webb's post:
>
> bapt (Baptisse Daroussin) wrote
>
>   *bapt  * replied Nov 16, 2017
>   
> 

You should have quoted that in your reply.  And are we really now
using github as the primary repository?

> because it should have always been like that, the real
> reinstallation was make deinstall reinstall, the fact one needs not
> to run deinstall first was a bug introduced very very long ago

This doesn't make much sense to me.  If I do a make deinstall, the
package is gone.  Then all I need is a make install, and that does,
indeed, work.  make reinstall by itself also used to work.  I'll go
with the others and assume that this was a transient bug.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: make reinstall does not work

[Greg 'groggy' Lehey]

On Saturday,  9 December 2017 at 12:04:02 +0100, Walter Schwarzenfeld wrote:
> Thanks, this explains and solved the problem.

What?  And how?

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: make reinstall does not work

[Greg 'groggy' Lehey]

On Friday,  8 December 2017 at 18:29:25 -0500, Shawn Webb wrote:
> On Fri, Dec 08, 2017 at 10:35:50PM +0100, Walter Schwarzenfeld wrote:
>> I had a strange error: Make reinstall does not work anymore in the port
>> (10.3-amd64) also FORCE_PKG_REGISTER.
>>
>> All other make commands works fine. I don't know if it is related to
>> FLAVORS.
>>
>> make reinstall ended up e.g. with:
>>
>> ??Registering installation for gtk2-2.24.31
>> *** Error code 70
>>
>> Stop.
>> make[2]: stopped in /usr/ports/x11-toolkits/gtk20
>> *** Error code 1
>>
>> Stop.
>> make[1]: stopped in /usr/ports/x11-toolkits/gtk20
>> *** Error code 1
>>
>> Any idea or suggestion?
>
> This is due to this commit:
> https://github.com/freebsd/pkg/commit/7991c49665419916210ad589d4a85fd2a7f58b37
>
> The standard procedure for reinstall is to do a deinstall first. I
> guess it's pretty common just to issue `make reinstall` (which is what
> I used to do as well). However, that's not the originally intended
> behavior as designed in the Ports build framework.
>
> So: just do a `make deinstall reinstall`. It'll work that way.

This makes no sense to me.  Why not just 'make deinstall install'?

Unfortunately 10 minutes of searching weren't enough to find anything
in the handbook.  What happened to the flat view?

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: make reinstall does not work

[Greg 'groggy' Lehey]

[rearranged]

On Friday,  8 December 2017 at 23:42:40 +0100, Jaap Akkerhuis wrote:
>> On Dec 8, 2017, at 22:35, Walter Schwarzenfeld  
>> wrote:
>>
>> I had a strange error: Make reinstall does not work anymore in the port 
>> (10.3-amd64) also FORCE_PKG_REGISTER.
>>
>> All other make commands works fine. I don't know if it is related to FLAVORS.
>>
>> make reinstall ended up e.g. with:
>>
>>  Registering installation for gtk2-2.24.31
>> *** Error code 70
>>
>> Stop.
>
> When I see this Error code 70 I do a make deinstall and then a make
> install. That worked for me

Yes, I've seen this too and used the same workaround.

Has something changed?  Does 'make reinstall' still work for others?

Greg
--
Sent from my desktop computer.
Finger g...@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: THANK YOU for flavors! (fwd)

[Greg 'groggy' Lehey]

On Thursday,  7 December 2017 at 11:02:51 +1100, Dave Horsfall wrote:
> On Thu, 7 Dec 2017 11:01:51 +1100 (EST), Dave Horsfall wrote:

Since we're being pedantic, note that this should be AEDT.
EST is ambiguous, but in general refers to the east coast of
the USA.

>> Serious question: is "FLAVOUR" accepted as an alias, or
>> does the rest of the world have to put up with American
>> spelling?

Think of it as a keyword.  No national origin necessary.

We really have better things to think of.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Time for a firefox-56 port?

[Greg 'groggy' Lehey]

On Sunday, 26 November 2017 at 14:22:18 +1100, Greg 'groggy' Lehey wrote:
> On Saturday, 25 November 2017 at 20:36:09 -0600, Zhihao Yuan wrote:
>> So give it up, try Pale Moon.
>
> Does Pale Moon address my issues, specifically something to match
> firemacs and It's all text!?  There's nothing that suggests it does.

I've installed it now on a Microsoft box, and how about that, yes, it
does support those addons.  Potentially it's usable, but it would
respect POLA to add the firefox-56 port, as I suggested at the
beginning.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Time for a firefox-56 port?

[Greg 'groggy' Lehey]

On Saturday, 25 November 2017 at 22:27:47 -0500, Adam McDougall wrote:
> On 11/23/2017 20:11, Greg 'groggy' Lehey wrote:
>> I've just installed the latest version of firefox and confirmed that
>> it breaks both of the addons that make firefox bearable for me
>> (firemacs, https://addons.mozilla.org/en-US/firefox/addon/firemacs/
>> and It's All Text!,
>> https://addons.mozilla.org/en-US/firefox/addon/its-all-text/).  So I
>> can't use it.
>>
>> I'm sure I'm not the only person who relies on old addons.  How about
>> a firefox-56 port until the current problems die down?
>
> I think www/firefox-esr would give you something like 6 months more of
> pre-57 codebase?

Yes, I saw that, but the pkg-descr doesn't say what good it is, and
the Makefile shows that it's based on 52.5.0, which seems to be rather
older than necessary.

> https://www.mozilla.org/en-US/firefox/organizations/faq/

Thanks.  That helps.  I've updated pkg-descr.  It also shows that
52.5.0 in fact corresponds to Firefox 57, so the port doesn't help
after all.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Time for a firefox-56 port?

[Greg 'groggy' Lehey]

On Saturday, 25 November 2017 at 20:36:09 -0600, Zhihao Yuan wrote:
> On Nov 25, 2017 8:15 PM, "Greg 'groggy' Lehey" <g...@freebsd.org> wrote:
>
>> It doesn't address the addon issue.  I expect that gradually the
>> addons will get updated to the new interfaces, so this is just a
>> temporary thing.

It would help if you would quote my text correctly.

> Oh, no, these addons are permanently dead,

Only when the firefox-56 sources are gone.  That's the point of my
original message.  For the time being I can just reinstall the cached
firefox-56 package, but it would be nice to have a label to hang on
it.

> and your best hope is to find alternatives, such as those made for
> Chrome.

I have found no corresponding alternatives for Chrome.

> The addons have been given 2 years to switch, and if that haven't
> happen, that's unlikely to happen starting from today.

The actual death of the plugins is a strong incentive to (finally) do
something about it.

> So give it up, try Pale Moon.

Does Pale Moon address my issues, specifically something to match
firemacs and It's all text!?  There's nothing that suggests it does.
I'm certainly no friend of firefox, but at least I have in the past
been able to bend it to be almost bearable.  I haven't managed that
with Chrome, and I have seen nothing to suggest that Pale Moon does
any better.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Time for a firefox-56 port?

[Greg 'groggy' Lehey]

On Saturday, 25 November 2017 at 19:33:18 -0600, Zhihao Yuan wrote:
> On Nov 25, 2017 6:31 PM, "Greg 'groggy' Lehey" <g...@freebsd.org> wrote:
>
>> I'm sure I'm not the only person who relies on old addons.  How
>> about a firefox-56 port until the current problems die down?
>
> Here is a port for the Palemoon browser:
>
>   https://www.freshports.org/www/palemoon/

It doesn't address the addon issue.  I expect that gradually the
addons will get updated to the new interfaces, so this is just a
temporary thing.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Time for a firefox-56 port?

[Greg 'groggy' Lehey]

I've just installed the latest version of firefox and confirmed that
it breaks both of the addons that make firefox bearable for me
(firemacs, https://addons.mozilla.org/en-US/firefox/addon/firemacs/
and It's All Text!,
https://addons.mozilla.org/en-US/firefox/addon/its-all-text/).  So I
can't use it.

I'm sure I'm not the only person who relies on old addons.  How about
a firefox-56 port until the current problems die down?

Greg
--
Sent from my desktop computer.
Finger g...@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: [HEADUP] FLAVORS landing.

[Greg 'groggy' Lehey]

On Wednesday, 27 September 2017 at  4:39:29 +1000, Andy Farkas wrote:
> On 27/09/2017 04:22, Mathieu Arnold wrote:
>
>> Please read the whole email.
>
> What are FLAVORS and why do I need it?
>
> Is there somewhere that explains the intent and purpose?

Thank you!  Just the question I was going to ask.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: PR looking for committer

[Greg 'groggy' Lehey]

On Tuesday,  5 September 2017 at 15:56:12 +0200, Fernando Apesteguía wrote:
> Hi,
>
> Can a committer have a look at this? It blocks another port update
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222001

Probably.  In fact, you've probably caused several committers to look
at it, but possibly not the correct one.  If you say what it refers
to, you have a better chance to get something done about it.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: I went to install 11.1 yesterday

[Greg 'groggy' Lehey]

On Sunday, 20 August 2017 at  7:50:52 -0400, scratch65...@att.net wrote:
> ...as a dual-boot with W7, but discovered that, like Linux (or at
> least Ubuntu) 11 doesn't support MBR.  So no dual-boot with older
> Windows.

People, this question has nothing to do with ports.  If you awnt a
mailing list, choose one from
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources-mail.html
freensd-questions used to be the way to go, but now people use forums,
which you can find at https://forums.freebsd.org/

Please don't follow up here.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

graphics/glew (was: FreeBSD ports you maintain which are out of date)

[Greg 'groggy' Lehey]

On Saturday, 12 August 2017 at 10:14:18 +, portsc...@freebsd.org wrote:
> Dear port maintainer,
>
> The portscout new distfile checker has detected that one or more of your
> ports appears to be out of date...
>
> Port| Current version | New 
> version
> +-+
> graphics/glew   | 1.13.0  | 2.1.0
> +-+

Some of my ports depend on this.  Is anybody else looking at it?
Otherwise I'll take a look.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: FreeBSD Port: nvidia-driver-375.66

[Greg 'groggy' Lehey]

On Monday, 17 July 2017 at 15:58:05 -0700, David P. Discher wrote:
> There is a new version of the nvidia driver on there site as of may 9th ???
>
> Version: 381.22
> Release Date: 2017.5.9
>
> This Added support for GeForce GT 1030 ??? which I???d imagine
> others may start trying to use like myself.  This older driver
> doesn???t work at all with the 1030.

While you're doing it, please look at pkg-message.  It seems that now
you need to kldload nvidia-modeset, and not nvidia.  The current
message is obscure and possibly incorrect for supported chip sets.
I'll send you a suggested update if you like.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: PRs in need of some TLC

[Greg 'groggy' Lehey]

On Monday, 26 June 2017 at 21:48:14 +0200, Martin Waschbüsch wrote:
> Hi all,
>
> could someone have a look at these PRs (they are linked) and provide
> some tender loving care? ;-)
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220177
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220190
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220191

If you say which ports are involved, you're more likely to get
attention.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: The ports collection has some serious issues

[Greg 'groggy' Lehey]

On Saturday, 17 December 2016 at 20:16:12 -0600, John Marino wrote:
> On 12/17/2016 19:35, Peter Jeremy wrote:
>> $ cd /usr/ports/ports-mgmt/synth/ && make
>> [ about an hour of grinding away elided ]
>> ===>   ini_file_manager-03_2 depends on file: /usr/local/gcc6-aux/bin/ada - 
>> not found
>> ===>  gcc6-aux-20160822 is only for amd64 i386, while you are running armv6.
>>
>> Overall, a total failure.
>>
>> OTOH, portmaster installs in a minute or so and runs perfectly well.  I fail
>> to see why you are so insistant on replacing it with something that doesn't
>> work at all.
>
> Real smooth there, Slick.

Sarcasm might get you somewhere, but I'm not sure you want to be
there.

> It's been mentioned several times in this thread alone that Ada is
> only available for i386 and amd64.  I think you already knew that
> and thus this is a pure troll.

I think Peter has highlighted a significant weakness.  A tool that
doesn't work on all platforms is hardly a replacement for a core tool
that does.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: FOCAL

[Greg 'groggy' Lehey]

On Saturday,  3 December 2016 at 11:40:36 +1100, Dave Horsfall wrote:
> Be there an implementation of FOCAL?  I have a hankering to get back to my
> early programming days :-)

Heh.  I have a paper tape from my first year at uni somewhere in the
mess on my desk.  It's been there for at least 10 years, and it's
short enough for it to be practical to read it in by eye, but I
haven't got more than a third of the way through.  It's in FOCAL-69,
and does some world-shattering calculations like mean and standard
deviation.  It would be fun to run it again--once.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Alternatives to rsync

[Greg 'groggy' Lehey]

On Monday, 17 October 2016 at  6:51:05 -0700, Freddie Cash wrote:
> On Oct 17, 2016 1:21 AM, "Lars Engels"  wrote:
>>
>> rsync 2 has a different algorithm for checking if a file changed. The
>> new one is much faster.
>
> Rsync 2 also spent a long time building a list of changes files first,
> before transferring any data.
>
> Rsync 3 starts building the file list, then starts transferring data while
> it continues to build the file list. This drops the total time spent by a
> large factor. Our backup times dropped by about an hour per server
> switching from 2 to 3.
>
> Something else to consider when looking at resurrecting version 2.

I can see no good reason to use rsync 2 in favour of 3.  But reko is
concerned by the GPL number, not rsync number.

The other thing to consider is whether rsync 2 is faster than the
other alternative software.  I suspect that it is.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Alternatives to rsync

[Greg 'groggy' Lehey]

On Friday, 14 October 2016 at  8:01:51 +0300, reko.turja--- via freebsd-ports 
wrote:
>
> Greg, I've actually put some thought in making a local port of
> rsync2. I've done some research on it and it seems to be fairly
> usable and security patched still.

Even simpler, use the old version of the current rsync port.  Check
out with svn, which (svn log) can also tell you when the last rsync 2
version was.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Alternatives to rsync

[Greg 'groggy' Lehey]

On Thursday, 13 October 2016 at 18:13:39 +1030, Shane Ambler wrote:
> On 13/10/2016 15:09, reko.turja--- via freebsd-ports wrote:
>> One of my users is needing rsync like functionality to transfer changed
>> contents of some directories between couple of machines. As rsync 3
>> isn't open source, but GPL3 it's out of question in order to keep the
>> system untainted.
>>
>> The software should be relatively lightweight - no fullblown
>> mirroring/backup is needed. Also hints how to achieve similar ends using
>> maybe tar/ssh might do.
>
> sysutils/cpdup provides similar functionality to rsync and is bsd licensed.

Does anybody have information on how efficient it is in comparison
with rsync?  Apart from that, I agree with the other comments.  But if
Reko wants a non-GPL3 package, for whatever reason, what's wrong with
an older version of rsync?

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: dependency explosions

[Greg 'groggy' Lehey]

On Monday,  3 October 2016 at 20:41:08 -0400, Baho Utot wrote:
>
> On 10/03/16 19:21, Greg 'groggy' Lehey wrote:
>> On Monday,  3 October 2016 at 14:14:13 +0200, Mathieu Arnold wrote:
>>> Le 01/10/2016 à 04:35, Julian Elischer a écrit :
>>>> Such a 'minimum' install should probably be the default when coming
>>>> in as a dependency, as there is an increasing tendency to configure
>>>> things with all the bells and whistles.
>>> The bare minimum will never be the default.  The default is what will
>>> fit most people, so that they can use our packages out of the box.
>> Not necessarily disagreeing with you, but I recently installed a new
>> version of firefox, and I was amazed by the number and nature of the
>> dependencies.  It totalled 497 MB, including:
>>
>>Fetching chromium-52.0.2743.116_1.txz: .. done
>>Fetching opera-12.16_6.txz: .. done
>>Fetching apache-openoffice-4.1.2_9.txz: .. done
>>Fetching libreoffice-5.0.6_3.txz: .. done
>>Fetching gimp-2.8.18,2.txz: . done
>>Fetching hugin-2016.2.0.txz: .. done
>>Fetching mplayer-1.3.0.20160912_1.txz: .. done
>>Fetching samba42-4.2.14.txz: .. done
>>Fetching emacs24-24.5_3,3.txz: .. done
>>
>> Chromium?  Opera?  Emacs?  Both OpenOffice and LibreOffice?
>>
>> I don't know if this always happens, but there's an issue here.  I
>> have a few unfinished thoughts about how it could occur, but so far
>> all I can confirm is that there is an issue.
>>
>> Is there a way to display these dependencies in a tree structure?
>
> $ make -C /usr/ports/www/firefox all-depends-list
> /usr/ports/ports-mgmt/pkg
> /usr/ports/devel/nspr
> /usr/ports/devel/gmake
> ...

That isn't a tree.  It also doesn't show the dependencies I mentioned
above.  And yes, I ran it locally.  On reflection, it's probably
because firefox requires an update to a library used by other
packages, so they need to be upgraded too.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: dependency explosions

[Greg 'groggy' Lehey]

On Monday,  3 October 2016 at 14:14:13 +0200, Mathieu Arnold wrote:
> Le 01/10/2016 à 04:35, Julian Elischer a écrit :
>> Such a 'minimum' install should probably be the default when coming
>> in as a dependency, as there is an increasing tendency to configure
>> things with all the bells and whistles.
>
> The bare minimum will never be the default.  The default is what will
> fit most people, so that they can use our packages out of the box.

Not necessarily disagreeing with you, but I recently installed a new
version of firefox, and I was amazed by the number and nature of the
dependencies.  It totalled 497 MB, including:

  Fetching chromium-52.0.2743.116_1.txz: .. done
  Fetching opera-12.16_6.txz: .. done
  Fetching apache-openoffice-4.1.2_9.txz: .. done
  Fetching libreoffice-5.0.6_3.txz: .. done
  Fetching gimp-2.8.18,2.txz: . done
  Fetching hugin-2016.2.0.txz: .. done
  Fetching mplayer-1.3.0.20160912_1.txz: .. done
  Fetching samba42-4.2.14.txz: .. done
  Fetching emacs24-24.5_3,3.txz: .. done

Chromium?  Opera?  Emacs?  Both OpenOffice and LibreOffice?

I don't know if this always happens, but there's an issue here.  I
have a few unfinished thoughts about how it could occur, but so far
all I can confirm is that there is an issue.

Is there a way to display these dependencies in a tree structure?

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: FreeBSD Port: digikam-4.14.0,2

[Greg 'groggy' Lehey]

On Thursday, 26 May 2016 at 22:29:32 +0200, delipu wrote:
> Hi,
>
> is it possible to enable mysql support with digikam. In earlier versions
> it was enabled by default. Without access to my database it is pretty
> useless now. Any help much appreciated.

Looking at the Makefile, it's still there, but you need to
specifically enable it with 'make config'.  Have you tried that?

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: FreeBSD ports you maintain which are out of date

[Greg 'groggy' Lehey]

On Saturday, 14 May 2016 at 13:47:01 +, portsc...@freebsd.org wrote:
> 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
> +-+
> graphics/libraw | 0.17.1  | 0.17.2
> +-+

FWIW, I took a look at this.  The base port has been updated, but the
demosaic pack option hasn't.  The change log suggests that it's just
cosmetic, so it's probably not (yet) worth the trouble.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: databases/mariadb100-client fails to compile

[Greg 'groggy' Lehey]

On Tuesday, 10 May 2016 at 10:03:24 +1000, Peter Jeremy wrote:
> I'm unable to get databases/mariadb100-client to compile on 10-stable/amd64.
> It fails as follows:
>
> Scanning dependencies of target mysqlclient
> gmake[4]: Leaving directory 
> '/var/obj/usr/ports/databases/mariadb100-client/work/mariadb-10.0.25'
> gmake[4]: Entering directory 
> '/var/obj/usr/ports/databases/mariadb100-client/work/mariadb-10.0.25'
> [ 92%] Building C object 
> libmysql/CMakeFiles/mysqlclient.dir/mysqlclient_depends.c.o
> [ 92%] Linking CXX shared library libmysqlclient.so
> [ 93%] Linking C static library libmysqlclient.a
> /usr/bin/ld: /usr/lib/libssl.a(ssl_err.o): relocation R_X86_64_32 against `a 
> local symbol' can not be used when making a shared object; recompile with 
> -fPIC
> /usr/lib/libssl.a: could not read symbols: Bad value
> c++: error: linker command failed with exit code 1 (use -v to see invocation)
> libmysql/CMakeFiles/libmysql.dir/build.make:110: recipe for target 
> 'libmysql/libmysqlclient.so.18' failed
> gmake[4]: *** [libmysql/libmysqlclient.so.18] Error 1
> gmake[4]: Leaving directory 
> '/var/obj/usr/ports/databases/mariadb100-client/work/mariadb-10.0.25'

"Me too", on a base installation of 10-STABLE.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: PRs ready for commit

[Greg 'groggy' Lehey]

On Wednesday,  4 May 2016 at  7:34:40 +0200, Bradley T. Hughes wrote:
> Howdy!
>
> I've got a few PRs up that are ready for a willing and able committer:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209214
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209215
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209216

If you say what port(s) they refer to, you might get more response.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Strangenesses with package dependencies

[Greg 'groggy' Lehey]

On Thursday,  7 April 2016 at  3:03:47 -0700, Don Lewis wrote:
> On  7 Apr, Don Lewis wrote:
>> On  7 Apr, Greg 'groggy' Lehey wrote:
>>> Bug 208575 describes a problem installing the hugin package: most of
>>> the dependencies didn't get installed...
>>
>> Not that it helps, but I tried buiding the package and ran into this
>> plist problem:
>> ...
>
> If I fix that problem, use poudriere to build the package, then run
>   poudriere testport -i -o graphics/hugin
> to rebuild it in a jail, then run
>   pkg delete -a
> do deinstall all the installed packages, and then run
>   pkg install hugin
> I see:
> ...
>
> It looks to me like everything in LIB_DEPENDS and RUN_DEPENDS is
> included in that list.  If I answer "y" at the above prompt, 145
> packages get installed.  All of the ones that were mentioned as missing
> in the PR were installed.

It's strange that this should cause pkg to fail silently, but if
that's all there is, I'm happy.  Thanks a lot for your help.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://tinyurl.com/broken-mua


signature.asc
Description: PGP signature

Strangenesses with package dependencies

[Greg 'groggy' Lehey]

Bug 208575 describes a problem installing the hugin package: most of
the dependencies didn't get installed.  It works fine building the
port from source, and neither I nor edwin@ (ex-mentor) can work out
why.  Here's what I get when I try 'pkg install hugin' on my test box:

  FreeBSD stable.lemis.com 10.3-STABLE FreeBSD 10.3-STABLE #0: Thu Apr  7 
13:13:03 AEST 2016 
r...@stable.lemis.com:/usr/obj/eureka/home/src/FreeBSD/svn/stable/10/sys/GENERIC
  amd64

  New packages to be INSTALLED:
hugin: 2016.0.0_1
p5-Image-ExifTool: 10.10
vigra: 1.11.0
hdf5: 1.8.15_1
fftw3-float: 3.3.3_2

In /usr/ports/graphics/hugin, make run-depends-list lists all the
dependencies.

Looking at the package
(http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/hugin-2016.0.0_1.txz),
the file +MANIFEST contains the names of all the dependencies.  After
replacing , with \n, I get stuff like:

  "OpenEXR":{"origin":"graphics/OpenEXR"
  "version":"2.2.0_5"}
  "glew":{"origin":"graphics/glew"
  "version":"1.13.0"}

All the missing dependencies are listed in +MANIFEST.  I don't know
enough about the format to determine if something's wrong, but
currently this looks like a pkg issue to me.

Any thoughts?  Anything else I can try?  The package is very new
(2016-Apr-07 01:59), not quite 6 hours old.  And yes, I've checked
that the problem still occurs with this version.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://tinyurl.com/broken-mua


signature.asc
Description: PGP signature

Re: Maintainer gone?

[Greg 'groggy' Lehey]

On Wednesday, 24 February 2016 at 17:55:02 +0100, Heino Tiedemann wrote:
> Hi,
>
> I had an open PR since some weeks. It seems, the the maintainer is
> gone. In the first time we had a living discussion about that
> problem. Ha made a spacial patch, so I tested it ?V but: did not work.
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205257

Not just for you: when sending messages like this, more detail would
help.  Who's the maintainer (r...@freebsd.org)?  What's the port
(graphics/gimp-gmic-plugin)?  When did you last hear from the
maintainer (14 December 2015)?  Have you tried to contact him directly
since then?

This isn't just being pedantic.  People reading your message may not
be bothered to follow the link, and unless they think it might be of
interest, they're likely to just delete it without follow-up.  If it
turns out to be something that they know about, or they know of the
whereabouts of rm@, you might get some action.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


signature.asc
Description: PGP signature

synth documentation (was: Removing documentation)

[Greg 'groggy' Lehey]

On Tuesday,  9 February 2016 at 15:08:22 +0100, John Marino wrote:
>
> Do you think the illustrated README on the github page is helpful?
>
> https://github.com/jrmarino/synth

I looked at that a couple of days ago.  It's certainly much better
than anything else I've seen on github, but it's still written from
the programmer's viewpoint: "this is how synth is structured, and what
it does".  What I was referring to in an earlier mail, and which a
couple of other people have also mentioned, is the answer to the
question "How do I use synth to do *this*?".

I installed the synth package a couple of days ago, mainly to take a
look.  And yes, I agree, if you're happy with the package (I would
be), the Ada dependencies and long build times aren't an issue.  I'm
sure the learning curve isn't overly steep, but it was enough to keep
me from running it just for the fun of it.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


signature.asc
Description: PGP signature

Discussions in closed PRs

[Greg 'groggy' Lehey]

Further to my mail yesterday, wblock@ closed PR 206922 (about whether
portmaster should be documented in the handbook).  But it refuses to
die!  After closure, there have been another 12 entries discussing the
relative merits of portmaster and synth, during which it eventuated
that marino@ wants to remove portmaster and replace it with synth.
This PR was just preparing the way.

I'm agnostic about the relative merits, since I don't use either.  But
the arguments go this way:

For portmaster: it's there, it works, and it has few dependencies.
Against portmaster: it's not maintained (hasn't been for 9 Whole
Months), and it has open PRs (3 of them,

For synth: it does everything!
Against synth: it's written in Ada.

I'm not taking a stance here, but if there's to be a discussion, it
should be in the open, not in the entrails of an only marginally
related dead PR.  I'm not going to spam the list with the messages,
but if you're interested in the topic, please take a look and continue
the discussion here, not in the PR.

One thing of interest is this overview of how synth works:
http://downloads.dragonlace.net/misc/synth-img/synth-arch.png

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


signature.asc
Description: PGP signature

Moving to synth (was: Removing documentation)

[Greg 'groggy' Lehey]

On Monday,  8 February 2016 at 23:15:45 +0100, John Marino wrote:
> On 2/8/2016 11:07 PM, Greg 'groggy' Lehey wrote:
>> I think you're missing the point.  If this were the criterion for
>> becoming maintainer, there's a good chance that nobody would
>> volunteer.  Your suggestion would work in a corporate environment, but
>> that's not us.
>
> I have said repeatedly that this criteria is unique to portmaster
> due to it's presence in the handbook and to its [apparent]
> importance in the ports ecosystem.

This wasn't very obvious.

> I am NOT saying this is the criteria for every port.  However, I would
> rather nobody volunteer if they aren't qualified so that decisions
> aren't kicked down the road like a can. I'm not looking to check a box
> resulting in no improvement, I want somebody qualified or not at all.

And that's what you're getting: not at all.

So how would things improve in this respect if we change to synth?
There we need a maintainer who understands Ada.  OK, at the moment
that's you.  But what happens when you relinquish maintainership for
whatever reason?

My feeling on the matter is that there's space for more than one tool,
as Mathias suggested.  But I think it would help synth to have
user-oriented documentation similar to that for portmaster or
portupgrade ("to achieve this, do this...").  I could see this as a
good addition to the handbook (4.5.3.3).  A(n objective) discussion of
the pros and cons of the three alternatives would also be useful.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


signature.asc
Description: PGP signature

Re: Removing documentation

[Greg 'groggy' Lehey]

On Monday,  8 February 2016 at 14:47:27 +0100, John Marino wrote:
> On 2/8/2016 2:40 PM, Mark Linimon wrote:
>> On Sun, Feb 07, 2016 at 03:21:49PM +0100, John Marino wrote:
>>> Anybody proposing to be maintainer, in my opinion, should first be
>>> required to take over every open PR in bugzilla
>>
>> thus ensuring that no one would ever take it.
>
> If the candidate is incapable of handling the PRs, why should s/he
> be annointed the maintainer?

I think you're missing the point.  If this were the criterion for
becoming maintainer, there's a good chance that nobody would
volunteer.  Your suggestion would work in a corporate environment, but
that's not us.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


signature.asc
Description: PGP signature

Re: Removing documentation

[Greg 'groggy' Lehey]

On Sunday,  7 February 2016 at 12:44:32 +0100, Torsten Zühlsdorff wrote:
> Hello,
>
>>> You have a tool presented as "official" that hasn't had it's
>>> original maintainer in 4 years and was only kept on life support up
>>> until 9 months ago.
>>
>> Agreed, the "official" (the term used is "recommended") status is
>> gone.  But that's a reason to fix the documentation, not remove it.
>> As I see it, we have three choices, in increasing order of
>> desirability:
>>
>> 1.  Remove all mention of portmaster.  That's what this PR recommends.
>> 2.  Do nothing.
>> 3.  Update the documentation to indicate the current status,
>>  recommending alternatives if possible.
>
> Number 4 is missing: find a maintainer for it.

Yes.  It was there in my draft, and I removed it.  It's a separate
issue: I was asking here about what to do with documentation for used,
but unmaintained packages.  But you make a good point: if there's a
lapse in maintainership, and the product then becomes maintained
again, you don't want to lose the documentation.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


signature.asc
Description: PGP signature

Removing documentation (was: [Bug 206922] Handbook: Chapter 4.5+ changes)

[Greg 'groggy' Lehey]

I'm bringing this to the attention of the ports community to try to
come up with a consensus about how to handle existing documentation
for ageing packages, in this case portmaster.

This bug report suggests removing the documentation for portmaster
because it is out of date and no longer maintained.

But it's still in the ports tree, and people still use it.  The
current wording (4.5.3.1) claims it is the recommended tool, which is
clearly out of date.  marino@ (the submitter) writes:

On Friday,  5 February 2016 at  7:33:33 +, bugzilla-nore...@freebsd.org 
wrote:
>
> You have a tool presented as "official" that hasn't had it's
> original maintainer in 4 years and was only kept on life support up
> until 9 months ago.

Agreed, the "official" (the term used is "recommended") status is
gone.  But that's a reason to fix the documentation, not remove it.
As I see it, we have three choices, in increasing order of
desirability:

1.  Remove all mention of portmaster.  That's what this PR recommends.
2.  Do nothing.
3.  Update the documentation to indicate the current status,
recommending alternatives if possible.

The real issue here is that we shouldn't remove documentation for
software that is still available.  In addition, wblock@ writes:

On Friday,  5 February 2016 at 14:48:07 +, bugzilla-nore...@freebsd.org 
wrote:
>
> At present, portmaster still has no direct competition...

More generally, the way I see it is simple: we should try to keep the
documentation as up-to-date as possible.  This means that we don't
remove documentation for existing packages.  It also means that we may
need to change the content of the documentation if the status (not
necessarily the content) of the package changes.

One of the arguments for removing it from the handbook is that it has
a man page.  That has some merit, but it doesn't help the people who
have used portmaster and now don't know what to do.  Even if portmgr
is deprecated, the documentation should suggest a replacement.

Can portmgr@ come up with a clear, easy-to-understand policy?

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


signature.asc
Description: PGP signature

Re: svn: E000022: ?\A0@@?\C8V @8@@@?\84?\D4

[Greg 'groggy' Lehey]

On Wednesday,  9 December 2015 at 20:58:37 +0100, Matthias Apitz wrote:
> El día Wednesday, December 09, 2015 a las 08:51:05PM +0100, O. Hartmann 
> escribió:
>
>> Found a strange entry in ports/www/links1:
>>
>>
>> total 435
>>  766755 -rw-r--r-- 1 root  wheel  uarch0B Dec  9 16:26 
>> ???@@?V?@8?@@@??
>>   29563 drwxr-xr-x 3 root  wheel  uarch8B Dec  9 16:26 ./
>
> The file was created at Dec 9 16:26, i.e. today. Any chance to get
> the name of the dirent in hex to understand the CodePoints?

Not that I know of, but you can get them in octal with the -B option
to ls.  That must say something about how old the option is :-)

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


signature.asc
Description: PGP signature

Re: Ports with duplicate LATEST_LINKs

[Greg 'groggy' Lehey]

On Wednesday, 19 August 2015 at  9:15:00 +1000, Greg 'groggy' Lehey wrote:
 On Tuesday, 18 August 2015 at 12:37:31 +, Ports Index build wrote:
 Dear port maintainers,

 The following list includes ports maintained by you that have duplicate
 LATEST_LINK values.

 Without counting, it looks like a complete list of all ports,
 unsorted.  Would it be possible to modify the script to send a list of
 relevant ports to each committer affected?

Note to self:

1.  Read thread.
2.  Understand.
3.  Reply if necessary.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


pgpmAAuqyR4za.pgp
Description: PGP signature

Re: Ports with duplicate LATEST_LINKs

[Greg 'groggy' Lehey]

On Tuesday, 18 August 2015 at 12:37:31 +, Ports Index build wrote:
 Dear port maintainers,

 The following list includes ports maintained by you that have duplicate
 LATEST_LINK values.

Without counting, it looks like a complete list of all ports,
unsorted.  Would it be possible to modify the script to send a list of
relevant ports to each committer affected?

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


pgp4Jh11Hj09K.pgp
Description: PGP signature

Re: pkg mirrors broken

[Greg 'groggy' Lehey]

On Thursday,  8 January 2015 at 20:03:32 -0800, Doug Barton wrote:
 On 1/8/15 8:00 PM, Doug Barton wrote:
 FYI:

 === Waiting on fetch  checksum for ports-mgmt/pkg ===
 fetch: http://mirror.shatow.net/freebsd/pkg/pkg-1.4.4.tar.xz: Forbidden

 ... and again:

 = Attempting to fetch
 http://distcache.eu.FreeBSD.org/local-distfiles/portmgr/pkg-1.4.4.tar.xz
 fetch:
 http://distcache.eu.FreeBSD.org/local-distfiles/portmgr/pkg-1.4.4.tar.xz:
 Not Found

Race condition, perhaps?  I upgraded pkg about an hour ago, and I got
1.4.3.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


pgpCq6JsK8I25.pgp
Description: PGP signature

Re: value of maintaining emacs-mode packages in ports

[Greg 'groggy' Lehey]

On Sunday, 23 November 2014 at  0:32:14 +0100, Christopher J. Ruwe wrote:
 I am well aware that very probably I might be starting a rant thread,
 however, I am genuinely interested in opinions from the community.

 Since version 24, Emacs, the very good operating system missing only a
 decent editor, has developed a package manager for Emacs
 extensions. Some good repos exist, packages are usually installed to
 /.emacs.d and I have come to really enjoy that way of installing
 packages.

 In that light and as the ports maintainer of math/ess, the Emacs
 speaks statistics R-mode of emacs, I am asking myself specifically
 whether I add any real benefit in maintaining math/ess. More
 generally, I am interested in community answers as to whether it is
 really useful to maintain Emacs-extension-packages in ports.

A good question.  I was wondering that myself.  I'd be happy to retire
our versions.

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


pgpoItR6O_7dd.pgp
Description: PGP signature

Re: Requesting Committer Attention for ports/184011 (Pkgng support in net-mgmt/nagios-check_ports)

[Greg 'groggy' Lehey]

On Sunday, 16 February 2014 at 20:08:28 -0600, Ryan Frederick wrote:
 I'd like to request that a committer take a gander at ports/184011 for
 me when possible. This is a pr I submitted three months ago and was
 never acted upon by the previous maintainer.

Always a good idea to quote text that the maintainer might recognize,
like I've done in the Subject: line.  You can't expect every ports
maintainer to go and look to see if it's his.

Sorry, not my area.

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua


pgpwDEPP82O3s.pgp
Description: PGP signature

Re: Call for testers: MythTV 0.21 port upgrade

[Greg 'groggy' Lehey]

On Thursday, 22 January 2009 at 20:41:01 -0500, Greg Larkin wrote:
 Greg 'groggy' Lehey wrote:
 On another machine, where I have a MySQL server with an old version of
 the mythconverg database, I can't start it: it connects to the
 database, finds that it's the wrong version, and stops again.  I
 suspect that I could fix that with mythtv-setup, but the port doesn't
 install it.  Would it be difficult to get it to do so?

 I specifically removed mythtv-setup from the new mythtv-frontend port
 because I read somewhere (perhaps on the Gentoo site?) that it's not
 needed for a frontend-only installation.

It seems that you can get by without it, and agreed, a lot has to do
with the backend.

 If that's not the case, let me know, and I'll add it back in.  There
 are lots of folks out there that are using MythTV in a real
 configuration, and I'm not there yet.  I have a mini-PC here to set
 up with a tuner card, etc., but I haven't gotten to it yet.

I don't feel expert in the matter either, so maybe we should wait
until there are more convincing reasons.

Greg
--
See complete headers for address and phone numbers.


pgpE0lV54Dwfw.pgp
Description: PGP signature

Re: Call for testers: MythTV 0.21 port upgrade

[Greg 'groggy' Lehey]

On Sunday, 18 January 2009 at 12:24:47 +, Craig Butler wrote:
 On another machine, where I have a MySQL server with an old version of
 the mythconverg database, I can't start it: it connects to the
 database, finds that it's the wrong version, and stops again.  I
 suspect that I could fix that with mythtv-setup, but the port doesn't
 install it.  Would it be difficult to get it to do so?

 This is usually handles my the updated mythbackend, it automatically
 updated my database when moving from 0.20 to 0.21...

This is a backup database for testing purposes, and has nothing to do
with the myth installation.  As Torfinn says, it's a nuisance that it
won't go past it.  I solved the issue by stopping the local mysqld,
setting up mythfrontend with the remote database, then starting mysqld
again.

 Also, every time I stop the front end, it SIGSEGVs.  I haven't
 investigated why.

 Aye, this happens on the old .20 release and the pre-released 0.21 and
 now this version.  Its not really a problem just need to tidy up the
 core dumps.

This is the state of modern multimedia software, I suppose.  SIGSGEVs
in running programs are always a problem.

 How do you find the livetv does yours stutter after some adverts
 fade to black ?

I haven't seen any stuttering.  But I barely watch live TV at all, so
that doesn't mean much.

What I have seen, both on live TV and recordings, is that sometimes
the front end will trip over itself and not display anything except
for the screen overlays.  Under these circumstances it seems to hang,
but tcpdump shows that it's actually transferring data (p will stop
and start the stream, for example).  It's doing it right now, with the
rather unusual situation of displaying a completely transparent
(invisible) full-screen window.  I can iconify it and deiconify it,
but apart from the fact that it also grabs focus when deiconified,
that's the only way I know it's there.  Pressing ESC gets out of it.
Weird.  I don't know how much this has to do with the port, though.
I'll investigate further.  And, of course, when I stop it I get:

  [1]+  Segmentation fault: 11  (core dumped) mythfrontend

Greg
--
See complete headers for address and phone numbers.


pgpXc4o907ILG.pgp
Description: PGP signature

Re: Call for testers: MythTV 0.21 port upgrade

[Greg 'groggy' Lehey]

On Thursday, 15 January 2009 at 17:35:40 -0500, Greg Larkin wrote:

 Hello all of you MythTV supporters with the collective patience of the
 universe!

 I recently committed mythtv-frontend (PR 127856) and mythtv-themes (PR
 127857), and please let me know if you see any problems with the updates.

OK, I've built mythtv-frontend.  On a machine with no prior
installation, it finds the machine running a MythTV 0.21 back end (how?).
I needed to extract the password to the MySQL database
from the back end, but then it seems to work.

On another machine, where I have a MySQL server with an old version of
the mythconverg database, I can't start it: it connects to the
database, finds that it's the wrong version, and stops again.  I
suspect that I could fix that with mythtv-setup, but the port doesn't
install it.  Would it be difficult to get it to do so?

Also, every time I stop the front end, it SIGSEGVs.  I haven't
investigated why.

Greg
--
See complete headers for address and phone numbers.


pgpfx7JOZdOcb.pgp
Description: PGP signature

Re: Call for testers: MythTV 0.21 port upgrade

[Greg 'groggy' Lehey]

On Friday, 31 October 2008 at 16:05:16 -0400, Greg Larkin wrote:

 I've been working on PR 126343
 (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/126343) to get MythTV
 upgraded to 0.21 on FreeBSD.

Sorry for the slow reply.  I've been busy with other things, and
currently I'm not in a position to test a new MythTV version.

As ex-maintainer of this port, however, I've received a number of
notifications from the MythTV developers of build fixes for FreeBSD.
Are you aware of them?  I can bounce them all to you if you like, or
if there's consensus, I can send them to [EMAIL PROTECTED]

One thing that has been a bone of contention in this port is the
handling of deleting the 'mythtv' user when removing the port.  I
don't believe that the user should disappear just because the port is
removed; it's often easier to remove a port and reinstall it rather
than upgrade it.  I'm told that the correct behaviour is that the user
should only be removed if no files under ~mythtv have changed.

One of the PRs mentioned here has addressed this issue, but after
cursory examination I'm not sure it does it right.  In particular,
just not creating the user is not a solution.

Greg
--
See complete headers for address and phone numbers.


pgpm5bJn8qMGM.pgp
Description: PGP signature

Keyboard problems with xorg 7.2 and Dell Inspiron 5100?

[Greg 'groggy' Lehey]

I've just upgraded my Inspiron 5100 to the latest and greatest X.org
release, 7.2.  Using the standard configuration options (either no
config file, or the one generated by X -configure), most keys on the
keyboard don't react.  I've ran xev against the server and find that
the only keys that react are the modifier keys.

The same machine runs fine with Knoppix 5.2, which has X.org 7.1.1,
and it ran fine under FreeBSD with a previous version of X.org
6.9.mumble.

Looking at the log file, nothing obvious reaches out and grabs me.  In
particular, the keyboard-related information corresponds exactly with
the Knoppix log file (modulo keyboard layout).

Has anybody else seen this?  Any ideas?

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers.


pgp143RmILow3.pgp
Description: PGP signature

Re: HEADSUP: removing the old cyrus-sasl port

[Greg 'groggy' Lehey]

On Friday, 30 March 2007 at 19:05:17 +0200, Gabor Kovesdan wrote:
 Dear Port Maintainers,

 I would like to inform you that the security/cyrus-sasl port is
 deprecated and expired. It is pretty old and not really supported any
 more. ...

 Could you please modify your ports to use cyrus-sasl2 instead or
 remove the support for the old cyrus-sasl port, please?

Is it really necessary to maintain the name cyrus-sasl2 for the
current port?  I'd much rather see it renamed cyrus-sasl.

Greg
--
See complete headers for address and phone numbers.


pgpq2RN58peRK.pgp
Description: PGP signature

Re: Porting a Linux application to FreeBSD

[Greg 'groggy' Lehey]

On Monday, 12 February 2007 at 14:35:34 -0800, [EMAIL PROTECTED] wrote:
 Hello,
 I was referred here by some people in the hackers@ list because I asked
 a porting related question and I should have asked it on this list.
 I was wondering steps people had used in the past for porting linux
 applications, ...

I can't answer your specific question, but you might like to read
Porting UNIX Software, available at
http://www.lemis.com/grog/Documentation/PUS/

Greg
--
See complete headers for address and phone numbers.


pgppYcH7DBoCc.pgp
Description: PGP signature

Re: unable to fetch mysql-5.0.33.tar.gz

[Greg 'groggy' Lehey]

On Friday,  9 February 2007 at 15:06:59 -0800, Noah wrote:

 any clues how I can find the mysql-5.0.33.tar.gz file so I can build the
 port?

You have already fetched it, but something went wrong:

 ===  Extracting for mysql-server-5.0.33
 = MD5 Checksum mismatch for mysql-5.0.33.tar.gz.
 = SHA256 Checksum mismatch for mysql-5.0.33.tar.gz.

This probably means that you have fetched a partial archive (i.e. the
fetch was interrupted and you tried again).

 = mysql-5.0.33.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
 = Attempting to fetch from ftp://ftp.easynet.be/mysql/Downloads/MySQL-5.0/.
 fetch: mysql-5.0.33.tar.gz: local modification time does not match remote

This is arguably a bug in the fetch logic: it compares the timestamp
of the partial archive on your system (the time when the fetch
aborted) with the timestamp of the archive it's trying to fetch, and
of course they don't match.

You should have a file /usr/ports/distfiles/mysql-5.0.33.tar.gz on
your system.  Remove it, try again, and all should be well.

Greg
--
See complete headers for address and phone numbers.


pgpXXLYZcGmvt.pgp
Description: PGP signature

Removing linphone?

[Greg 'groggy' Lehey]

I've just tried to reinstall the linphone port and see that it's
marked broken and deprecated.  Does anybody know of an alternative
which supplies a command-line SIP client?

Greg
--
See complete headers for address and phone numbers.


pgpODw5K3adWJ.pgp
Description: PGP signature

Building a port for an X11 hardware driver

[Greg 'groggy' Lehey]

I've recently bought a a VIA K8M890-based motherboard.  This chip set
has onboard VGA, but it's not supported by X.org or XFree86 (well, the
vesa driver recognizes it, but that's not saying much).  On the other
hand, VIA has X.org drivers for it in source form, which for some
reason X.org has not incorporated into the distribution.  So it makes
sense to port them.

Problem: how do I do that?  The most obvious approach is to extract
x11-servers/xorg-server and replace the via driver with the VIA code.
But that sounds tacky.

My understanding of the Ports Collection is not really up to this
task.  If somebody wants to take over the project, feel free.
Otherwise I'd be grateful for some hand-holding.

The source tarball is at
http://www.viaarena.com/Driver/k8m800_890-p4m890xf41068-kernel-src_20060707.tgz
(and yes, though the name suggests that the drivers are for XFree86,
the accompanying documentation (src/ReleaseNotes.txt) talks of X.org).
There's also another, less powerful package at
http://www.viaarena.com/Driver/k8m890xf40069-kernel-src_20060620.tgz.
See also
http://www.viaarena.com/default.aspx?PageID=420OSID=25CatID=2580SubCatID=164
for some minimal documentation.

Greg
--
See complete headers for address and phone numbers.


pgpnAG9Y0sfSl.pgp
Description: PGP signature