Re: Catalina

[Al Varnell via macports-users]

It is true that they loosened the NDA two or three years back, but only that it 
excludes any information that has already been made public (primarily via the 
annual WWDC conference, but could also be otherwise made public through no 
fault of your own, except that you may not post screen shots of, write public 
reviews of, or redistribute any such materials.). 

For those that have access, the English developer NDA is at 
>.

The Public Beta NDA is at >.

Sections 4-6 of the former are the same as sections 5-7 of the latter, for all 
practical purposes.

Also note these word in the Public Beta NDA "you agree that you will not 
disclose, publish, or otherwise disseminate any Confidential Information to 
anyone other than individuals who are enrolled in the same individual seed as 
you..." which would appear to limit discussions between the two groups.

-Al-

> On Jul 8, 2019, at 18:56, Mark Anderson  > wrote:
> 
> I can open feedback via radar or whatever as I’m in the developer program  
> but also they loosened the NDA a bit a few years back. A bunch of us made a 
> fuss sometime after swift came out since it was vital to help each other 
> before the release. That’s why you can learn about SwiftUI and the like on 
> the Internet today even with the NDA in place. That said, look up the 
> restrictions. Things like screenshots are forbidden. And we should probably 
> just discuss among those of us with a developer account (or public beta) but 
> I don’t know that agreement.
> 
> —Mark
> 
> On Mon, Jul 8, 2019 at 8:25 PM Al Varnell via macports-users 
>  > wrote:
> I would not be allowed to even say if I was, but my understanding is that 
> Feedback submissions from the public beta program are only considered in 
> aggregate and never responded back to individuals.
> 
> Sent from my iPad
> 
> -Al-
> 
> > On Jul 8, 2019, at 12:53, Peter Homann  > > wrote:
> > 
> > NDA.
> 
> -- 
> Sent from Gmail Mobile on iPhone
> 
> 


smime.p7s
Description: S/MIME cryptographic signature

Re: Catalina

[Mark Anderson]

I can open feedback via radar or whatever as I’m in the developer program
 but also they loosened the NDA a bit a few years back. A bunch of us made
a fuss sometime after swift came out since it was vital to help each other
before the release. That’s why you can learn about SwiftUI and the like on
the Internet today even with the NDA in place. That said, look up the
restrictions. Things like screenshots are forbidden. And we should probably
just discuss among those of us with a developer account (or public beta)
but I don’t know that agreement.

—Mark

On Mon, Jul 8, 2019 at 8:25 PM Al Varnell via macports-users <
macports-users@lists.macports.org> wrote:

> I would not be allowed to even say if I was, but my understanding is that
> Feedback submissions from the public beta program are only considered in
> aggregate and never responded back to individuals.
>
> Sent from my iPad
>
> -Al-
>
> > On Jul 8, 2019, at 12:53, Peter Homann  wrote:
> >
> > NDA.
>
> --
Sent from Gmail Mobile on iPhone

Re: Catalina

[Al Varnell via macports-users]

I would not be allowed to even say if I was, but my understanding is that 
Feedback submissions from the public beta program are only considered in 
aggregate and never responded back to individuals.

Sent from my iPad

-Al-

> On Jul 8, 2019, at 12:53, Peter Homann  wrote:
> 
> NDA.

Is XSANE supported under Sierra?

[Dave Horsfall]

MacBook running Sierra + all patches (it will *not* go further), XSANE 
0.999.


The scanner is an Epson Perfection1240 (pretty old now) and XSANE stopped 
seeing it around the time I upgraded to Sierra (or could have been a minor 
update, as I rarely use it).  USB info sees it, so it's not the OS as 
such; I'm guessing that the API has changed?


USB:

  Perfection1240:

  Product ID:   0x010b
  Vendor ID:0x04b8  (Seiko Epson Corp.)
  Version:  1.03
  Speed:Up to 12 Mb/sec
  Manufacturer: EPSON
  Location ID:  0x0410 / 2
  Current Available (mA):   500
  Extra Operating Current (mA): 0

port info xsane:

  xsane @0.999 (graphics, x11)
  Variants: disable_gimp

  Description:  This is an X11 frontend for the Scanner Access Now Easy
Project.
  Homepage: https://www.openhub.net/p/xsane

  Build Dependencies:   pkgconfig
  Library Dependencies: gimp2, jpeg, gtk2, libpng, sane-backends, lcms
  Platforms:darwin
  License:  GPL-2
  Maintainers:  Email: michael.kl...@puffin.lb.shuttle.de, GitHub:
mklein-de
Policy: openmaintainer

Thanks.

-- Dave

Re: Catalina

[Andrew Udvare]

On 08/07/2019 15:57, Mark Anderson wrote:
> I am.

I am also.



signature.asc
Description: OpenPGP digital signature

Re: Catalina

[Mark Anderson]

I am.

On Mon, Jul 8, 2019 at 3:53 PM Peter Homann  wrote:

> Anyone else on the MacOS beta program and now have Catalina? I have an
> issue I want to discuss, but without breaching the NDA.
>
> I have logged my issue through Apple's feedback process, but I would guess
> their first response will be that it isn't a MacOS problem, but a Macport
> issue.
> Thanks in advance,
> Peter
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
Sent from Gmail Mobile on iPhone

Catalina

[Peter Homann]

Anyone else on the MacOS beta program and now have Catalina? I have an issue I 
want to discuss, but without breaching the NDA.

I have logged my issue through Apple's feedback process, but I would guess 
their first response will be that it isn't a MacOS problem, but a Macport 
issue. 
Thanks in advance, 
Peter
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: texlive no longer finds (some of) its style files?

[Mojca Miklavec]

On Mon, 8 Jul 2019 at 14:27, Ryan Schmidt wrote:
>
> I don't think MacPorts will uninstall a port unless you tell it to (directly 
> by name@version_revision+variants, or using a pseudoport (like "inactive" or 
> "leaves"), or using port(1)'s "-u" flag).
>
> What could happen, though, is that MacPorts might deactivate a port if 
> another port has replaced its functionality. For example, if a port 
> texlive-old no longer exists but a port texlive-new now provides the same 
> files that texlive-old used to, then when you install or upgrade texlive-new, 
> it will automatically deactivate texlive-old. The result should be that the 
> files you want are still there. If somehow that didn't end up being the case, 
> you could reactivate texlive-old.
>
> If you selectively update ports, you can run into situations where some of a 
> port's dependencies have been updated but others haven't. This can result in 
> a variety of problems, possibly including the one you mentioned. For this 
> reason, we recommend using "sudo port upgrade outdated" to upgrade all of the 
> outdated ports at once, and not selectively upgrading ports.

With TeX Live one can definitely run into situations of a package
being in one collection, then moved to another collection next year.
And your document suddenly no longer compiles despite having the same
packages installed (but now some files missing), and the only safe way
around it is to install the full texlive.

Mojca

Re: texlive no longer finds (some of) its style files?

[Ryan Schmidt]

On Jul 8, 2019, at 07:34, joerg van den hoff wrote:

> On 08.07.19 14:27 , Ryan Schmidt wrote:
> 
>> I don't think MacPorts will uninstall a port unless you tell it to (directly 
>> by name@version_revision+variants, or using a pseudoport (like "inactive" or 
>> "leaves"), or using port(1)'s "-u" flag).
>> What could happen, though, is that MacPorts might deactivate a port if 
>> another port has replaced its functionality. For example, if a port 
>> texlive-old no longer exists but a port texlive-new now provides the same 
>> files that texlive-old used to, then when you install or upgrade 
>> texlive-new, it will automatically deactivate texlive-old. The result should 
>> be that the files you want are still there. If somehow that didn't end up 
>> being the case, you could reactivate texlive-old.
>> If you selectively update ports, you can run into situations where some of a 
>> port's dependencies have been updated but others haven't. This can result in 
>> a variety of problems, possibly including the one you mentioned. For this 
>> reason, we recommend using "sudo port upgrade outdated" to upgrade all of 
>> the outdated ports at once, and not selectively upgrading ports.
> 
> OK, understood. I can confirm that the problem arose after issuing `port 
> upgrade texlive' rather than doing a full upgrade of all outdated packages. I 
> was not aware that this is (or might be) insufficient to get the respective 
> package fully upgraded (including _all_ dependencies).

I agree that "sudo port upgrade texlive" should work for upgrading texlive and 
all of its dependencies. However, any other installed ports might then be in a 
non-working state. "sudo port upgrade outdated" should return those other ports 
to working condition.

Re: samba4

[rmgls]

HEllo Rayan, 

thanks for the link. 

i will correct the address book then.

Raoul



> On 8 Jul 2019, at 12:42, Ryan Schmidt  wrote:
> 
> 
> 
> On Jul 6, 2019, at 11:27, rmgls wrote:
> 
>> trying to build samba4 i get these errors, 
> 
> There are a few 6-year-old tickets open about the samba4 port, including a 
> build failure (for a different reason than the one you encountered) and a 
> need to update the port:
> 
> https://trac.macports.org/query?status=!closed=~samba4
> 
> So I would suspect that nobody will be able to build the port until someone 
> volunteers to fix it.
> 
> 
> P.S: Please use our new list addresses at lists.macports.org, not the older 
> hostname you used which we deprecated in 2016.
> 

Re: texlive no longer finds (some of) its style files?

[Ryan Schmidt]

On Jul 8, 2019, at 06:10, joerg van den hoff wrote:

> On 08.07.19 08:28 , Dan Ports wrote:
>> On Sat, Jun 29, 2019 at 06:29:57PM +0200, joerg van den hoff wrote:
>>> would `port upgrade texlive' throw out an old texlive-latex-extra rather
>>> than upgrading (or ignoring) it? it shouldn't do that but could it?
>> Yes, this can happen on occasion.
>> MacPorts doesn't have great support for enforcing that a bunch of
>> ports, like all of texlive, should be upgraded at once. In particular,
>> if a file moves from the older version of one port to the newer
>> version of another, which happens fairly often with texlive, it can
>> create a false conflict. There are hacks in some of the portfiles to
>> forcibly deactivate conflicts so this doesn't break the upgrade.
>> Usually this works out fine, and the new versions of all of the ports
>> get installed correctly. Depending on the order the upgrades are run
>> in, though, and especially if the upgrade is interrupted, some package
>> might be uninstalled.
>> Dan
> 
> thanks for confirming that this is a known problem/limitation. I will try to 
> remember this if I encounter that situation again. it sure is unfortunate, 
> though, that an installed package can
> get unwittingly uninstalled especially one that is part of the texlive "mess" 
> ...
> 
> but anyway. I have used macports long enough to really appreciate how much 
> smoother it works these
> days. thanks a lot to everybody involved!.

I don't think MacPorts will uninstall a port unless you tell it to (directly by 
name@version_revision+variants, or using a pseudoport (like "inactive" or 
"leaves"), or using port(1)'s "-u" flag).

What could happen, though, is that MacPorts might deactivate a port if another 
port has replaced its functionality. For example, if a port texlive-old no 
longer exists but a port texlive-new now provides the same files that 
texlive-old used to, then when you install or upgrade texlive-new, it will 
automatically deactivate texlive-old. The result should be that the files you 
want are still there. If somehow that didn't end up being the case, you could 
reactivate texlive-old.

If you selectively update ports, you can run into situations where some of a 
port's dependencies have been updated but others haven't. This can result in a 
variety of problems, possibly including the one you mentioned. For this reason, 
we recommend using "sudo port upgrade outdated" to upgrade all of the outdated 
ports at once, and not selectively upgrading ports.

Re: texlive no longer finds (some of) its style files?

[joerg van den hoff]

On 08.07.19 08:28 , Dan Ports wrote:

On Sat, Jun 29, 2019 at 06:29:57PM +0200, joerg van den hoff wrote:

would `port upgrade texlive' throw out an old texlive-latex-extra rather
than upgrading (or ignoring) it? it shouldn't do that but could it?


Yes, this can happen on occasion.

MacPorts doesn't have great support for enforcing that a bunch of
ports, like all of texlive, should be upgraded at once. In particular,
if a file moves from the older version of one port to the newer
version of another, which happens fairly often with texlive, it can
create a false conflict. There are hacks in some of the portfiles to
forcibly deactivate conflicts so this doesn't break the upgrade.

Usually this works out fine, and the new versions of all of the ports
get installed correctly. Depending on the order the upgrades are run
in, though, and especially if the upgrade is interrupted, some package
might be uninstalled.

Dan



thanks for confirming that this is a known problem/limitation. I will try to remember this if I 
encounter that situation again. it sure is unfortunate, though, that an installed package can

get unwittingly uninstalled especially one that is part of the texlive "mess" 
...

but anyway. I have used macports long enough to really appreciate how much 
smoother it works these
days. thanks a lot to everybody involved!.

Re: macports-installation: do I have to install xcode?

[Ryan Schmidt]

On Jul 4, 2019, at 12:12, Hongxia (Laura) Hao wrote:

> I am wondering if I need to install the whole xcode app before
> installing macports? Does that work if I only install the xcode
> command line tools?

As of right now, MacPorts assumes that Xcode exists, so our official 
recommendation is to install Xcode so that you will be able to install any 
port. Not all ports require Xcode, but if you try to install a port that does 
require it, and you have not installed it, you will get a build failure.

The decision to make MacPorts work this way dates from the early days of Mac OS 
X before the command line tools were a thing that you could install without 
installing Xcode. There is work underway for Google Summer of Code 2019 to 
allow individual ports to indicate whether they require Xcode so that we could 
provide a more user-friendly error message if Xcode is missing but needed.

We have an automated build system that produces binaries of many of our ports. 
If you install a port for which a binary is available, you don't need Xcode nor 
the command line tools; MacPorts simply downloads and installs the binary.

If you install a port for which a binary is not available but which needs to be 
compiled by a C/C++ compiler, either Xcode or the command line tools needs to 
be installed to provide that compiler. Some ports can only be compiled with a 
full Xcode installation present. Others can be compiled using just the files 
provided by the command line tools.

Re: ImageMagick Display command

[Ryan Schmidt]

On Jul 3, 2019, at 10:41, Christoph Kukulies wrote:

> I ran in a Terminal the ImageMagick command: 
> 
> $ display image.jpg
> 
> and got:
> 
> display: delegate library support not built-in '' (X11) @ 
> error/display.c/DisplayImageCommand/1900.

When I Googled that error message, the suggestion I saw was to install 
ImageMagick with X11 support. In MacPorts, that means installing it with the 
+x11 variant (sudo port install ImageMagick +x11). That variant is on by 
default, so perhaps you had deliberately disabled it when installing 
ImageMagick.

If you are still getting this error but you do have ImageMagick installed with 
the +x11 variant, let us know.

Re: samba4

[Ryan Schmidt]

On Jul 6, 2019, at 11:27, rmgls wrote:

> trying to build samba4 i get these errors, 

There are a few 6-year-old tickets open about the samba4 port, including a 
build failure (for a different reason than the one you encountered) and a need 
to update the port:

https://trac.macports.org/query?status=!closed=~samba4

So I would suspect that nobody will be able to build the port until someone 
volunteers to fix it.


P.S: Please use our new list addresses at lists.macports.org, not the older 
hostname you used which we deprecated in 2016.

Re: texlive no longer finds (some of) its style files?

[Dan Ports]

On Sat, Jun 29, 2019 at 06:29:57PM +0200, joerg van den hoff wrote:
> would `port upgrade texlive' throw out an old texlive-latex-extra rather
> than upgrading (or ignoring) it? it shouldn't do that but could it?

Yes, this can happen on occasion.

MacPorts doesn't have great support for enforcing that a bunch of
ports, like all of texlive, should be upgraded at once. In particular,
if a file moves from the older version of one port to the newer
version of another, which happens fairly often with texlive, it can
create a false conflict. There are hacks in some of the portfiles to
forcibly deactivate conflicts so this doesn't break the upgrade.

Usually this works out fine, and the new versions of all of the ports
get installed correctly. Depending on the order the upgrades are run
in, though, and especially if the upgrade is interrupted, some package
might be uninstalled.

Dan

-- 
Dan R. K. Ports  https://drkp.net/