libpng to 1.6.19, CVE-2015-8126

econd paragraph, third bullet point: "A critical port is broken that affects many users." Let me know if you object to the change. [1] https://guide.macports.org/#project.update-policies.nonmaintainer -- Clemens Lang ___ macports-dev mailing li

Re: Trace mode

different processes, before we enable it by default. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Trace mode

or a single port, so the output may have been completely unrepresentative. I would welcome better measurements. > What kind of caching? See Daniel's link. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org http

Re: boost, akonadi and rev-upgrade

to load the library using dlopen(3) at runtime, or the two boost versions are ABI-compatible, but implementation changed to cause new exceptions. A third possibility would be that boost was built against a different C++ runtime library than akonadi. The backtrace would tell us mor

Re: port xmh: upgrade failure due to trace mode?

es before building a package. Trace mode hides runtime dependencies from the build. Consequently, for a build without trace mode, xbitmaps is actually there and being used in all cases. This is a corner case that trace mode reveals, but is pretty harmless in practice. -- Cle

Re: v8 upgrade

method to obtain the dependencies for v8, so the Portfile needs some work to make this happen. Patches would be very welcome on this. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman

Build Reproducibility Workshop Report

oducible-builds.org/docs/ [4] https://reproducible-builds.org/specs/source-date-epoch/ [5] https://diffoscope.org/ [6] https://lists.reproducible-builds.org/pipermail/diffoscope/2015-December/00.html -- Clemens Lang MacPorts Developer ___ macports-

Re: Build Reproducibility Workshop Report

Hello Rainer, hello Mojca, On Wed, Dec 09, 2015 at 12:14:42PM +0100, Rainer Müller wrote: > > To track down the differences that cause builds to be non-reproducible, > > a couple of people from the Debian reproducible builds effort have > > written diffoscope [5], a python diff tool that will inte

Re: [MacPorts] ReproducibleBuilds added

On Wed, Dec 09, 2015 at 09:14:12AM -0800, Ryan Schmidt wrote: > On Dec 9, 2015, at 9:01 AM, MacPorts wrote: > > > > Page "ReproducibleBuilds" was added by rai...@macports.org > > Comment: New page, mostly a stub to be referenced in commit messages > Can we combine this page and > https://trac.ma

Re: Vector graphic with the MacPorts logo

common capital M and the slight bulge on the top of the capital P. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Vector graphic with the MacPorts logo

- On 10 Dec, 2015, at 15:22, Sean Mehta s...@mehta.io wrote: > I believe that it's Myriad Pro. Indeed, good catch. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/

Re: Build Reproducibility Workshop Report

On Wed, Dec 09, 2015 at 05:21:09PM -0800, Ryan Schmidt wrote: > Apple hardware is available. Virtualizing OS X on Apple hardware is no > problem; we do it today with our existing buildbot builders. > [...] > I'm open to changes in the buildbot builder setup or replacing it, if > there's something b

Re: Build Reproducibility Workshop Report

On Thu, Dec 10, 2015 at 05:39:47PM -0600, Ryan Schmidt wrote: > But it thought we were saying the portindex wouldn't be generated > correctly if use-commit-times=yes. I certainly remember problems along > those lines years ago... The portindex generation re-indexes all Portfiles whose mtime is new

Re: writing Tcl port utilities

(re-sent from correct sender address for the list) Hi René, On Tue, Dec 15, 2015 at 05:40:30PM +0100, René J.V. Bertin wrote: > On Tuesday December 15 2015 10:17:58 Daniel J. Luke wrote: > > > Anything is possible, although this seems like a bad idea to me. > > I agree it could lead to lots of

Re: portindex ignores (filters out) unchanged port

Hello, On Sun, Dec 27, 2015 at 11:10:45PM +0100, René J.V. Bertin wrote: > I had a look at the PortIndex files, and while `portindex` claimed it > reused the existing kf5-kate entry, I actually found 2 entries for > kate. > So I tried a hunch: rather than having > kde/kate/Portfile -> port:kate >

Re: portindex ignores (filters out) unchanged port

On Mon, Dec 28, 2015 at 12:35:17AM +0100, René J.V. Bertin wrote: > On Monday December 28 2015 00:11:28 Clemens Lang wrote: > > > and fix your directory naming first. If the Portfile provides > > kf5-kate, it should be in a kf5-kate directory. > > I'd just a

Re: Survey: How do you commit?

Hi Ryan, On Fri, Jan 01, 2016 at 11:43:17PM -0600, Ryan Schmidt wrote: > How do you commit to the MacPorts Subversion repository? > > Using a Subversion working copy and "svn commit"? This. > Using a Git clone and git-svn? > Some other method? > > Do you have any complaints about that method o

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

Hi, On Tue, Jan 05, 2016 at 12:44:49PM -0600, Ryan Schmidt wrote: > > I'm not comfortable with installing unchecked files on user systems. > The whole point of the checksum system is to verify that the files > that are installed on user systems are the same files that were tested > by the maintai

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

Hi, On Thu, Jan 07, 2016 at 12:12:20PM -0600, Eric A. Borisch wrote: > Bringing this back to the original point, it looks like there was some > discussion (I think) in this thread of making alocation (possibly > integrated in terms of access accounts with svn commit access) > available to store a

Re: How to find all dependents of go?

Hi, On Thu, Jan 14, 2016 at 09:28:48PM +0100, Christoph Iserlohn wrote: > But > $ port dependents go > returns > go has no dependents. > which is clearly wrong. I have several ports depending on go installed, e.g.: > $ port installed go-tools > The following ports are currently installed: > go-t

Re: [144726] trunk/dports/science

Hi Ryan, On Sat, Jan 16, 2016 at 09:25:15AM -0600, Ryan Schmidt wrote: > Instead of overriding the fetch, checksum and extract phases, you > should declare that the port has no distfiles, by writing on a line by > itself: > > distfiles > > With no distfiles, the master_sites line isn't needed ei

Re: Dependences of textinfo

Hi, On Wed, Jan 20, 2016 at 05:58:09AM -0700, Marcus Calhoun-Lopez wrote: > Most ports that use texinfo probably require only a subset of these > external programs. Whose job is it to provide these dependencies? > > As far as I can tell, there are three options: > (1) texinfo has runtime depe

Re: VLC cannot play MKV files?

On Wed, Jan 27, 2016 at 03:00:52PM +0100, Rainer Müller wrote: > > I think the system bsdtar doesn't support this on all OS X versions > > that do support hfs compression. > > Right, on my OS X 10.10.5 Yosemite it does not seem to be supported. In > the ticket you said it was not supported on OS X

Re: about keeping a checksums table in a separate file

On Tue, Feb 02, 2016 at 10:32:23AM +0100, René J.V. Bertin wrote: > How important is the whole checksumming feature really? Checksumming is a critical security feature. It must stay. > Anything goes wrong during transmission (fetch), and the archive is > very likely not to unpack successfully.

Re: Distinguishing between deactivated ports than I want to keep and outdated port I no longer care about

Hi, On Wed, Feb 24, 2016 at 01:56:55AM -0600, Ryan Schmidt wrote: > > Is there any equivalent of "port installed" that also shows whether > > a port was requested > > No, but you can show installed requested ports with "port installed > requested" and installed unrequested ports with "port instal

Re: PortIndex2MySQL run failure on Sunday 2016-03-06 at 07:00:01

Hi, On Sun, Mar 06, 2016 at 07:15:29PM +0100, Mojca Miklavec wrote: > Whooops, I'm sorry, I didn't think about the possibility of this > scenariot. > > Are you able to help me out to come up with a proper patch or should > we simply replace > > if {[active_variants gtk3 quartz ""]} { >

Re: registry backup (and upgrade --force)

Hello, On Sun, Apr 03, 2016 at 11:31:47AM +0200, René J.V. Bertin wrote: > Subsequent port commands hung without even a line of debug output, > which I finally presumed due to registry corruption. How did you presume that? Are you sure your assumption is correct? > I think something like this al

Re: PortGroup directory hierarchy/priority

Hi, On Sun, Apr 03, 2016 at 01:26:01PM +0200, René J.V. Bertin wrote: > I tend to view PortGroups as header files, that is files where you > move variables and code that should be available to more than just the > port that "goes with" the PortGroup. PortGroups are not headers, they are just mere

Re: registry backup (and upgrade --force)

On Sun, Apr 03, 2016 at 11:19:33PM +1000, Joshua Root wrote: > Not if they have outdated dependencies. Upgrade without -n is a > recursive operation. Good point. > Not passing the --force flag on to the deps by default would be ok I > guess, but what if the user wants that? Doesn't the global -f

Re: registry backup (and upgrade --force)

Hi, On Sun, Apr 03, 2016 at 05:56:49PM +0200, René J.V. Bertin wrote: > >How did you presume that? Are you sure your assumption is correct? > > The only sensible feedback I got was from the CrashReporter after I > sent a SIGTERM (^]) which showed a backtrace into sqlite fsck > functions. I also t

Re: PortGroup directory hierarchy/priority

On Mon, Apr 04, 2016 at 12:37:05AM +0200, René J.V. Bertin wrote: > Take a custom version of a port "foo" which has a corresponding > PortGroup "foo". That PortGroup contains information foo's dependents > require, and that is not identical between the custom and default > port:foo. What kind of i

Re: PortGroup directory hierarchy/priority

Hi, On Mon, Apr 04, 2016 at 10:42:16AM +0200, René J.V. Bertin wrote: > Typically paths defined through variables indeed, or configure > settings, Paths and flags should be part of configuration files installed by a port, e.g. CMake config files or pkg-config files. > plus the occasional pre- or

Re: registry backup (and upgrade --force)

On Mon, Apr 04, 2016 at 06:42:24PM +0200, René J. V. Bertin wrote: > Thanks for the suggestion. Curiously that went just fine, but it also > seems to contradict the previous claim that any interaction with an > sqlite3 db modifies it. No, any writing interaction modifies it (that should be obvious

Re: registry backup (and upgrade --force)

Hi, On Mon, Apr 04, 2016 at 07:04:46PM +0200, René J.V. Bertin wrote: > How would one check that (without putting my whole install at risk)? http://serverfault.com/questions/8048/how-can-i-verify-that-a-sqlite-db3-file-is-valid-consistent See also https://trac.macports.org/browser/trunk/base/src

Re: PortGroup directory hierarchy/priority

Hi, On Mon, Apr 04, 2016 at 08:17:55PM +0200, René J.V. Bertin wrote: > > > There's only one way to enforce the reproducible build principle > > > all the way, and that's to remove the whole possibility of > > > building from source so that users can only install official, > > > binary packages.

Re: PortGroup directory hierarchy/priority

On Wed, Apr 06, 2016 at 10:48:00AM +0200, René J. V. Bertin wrote: > > Builds can be made bit-by-bit reproducible even when building from > > source. It's not even particularly difficult for a lot of ports, as > > long as the toolchain stays the same, timestamp issues are handled > > and the enviro

Re: registry backup (and upgrade --force)

Hi, On Wed, Apr 06, 2016 at 03:08:09PM +0200, René J. V. Bertin wrote: > That doesn't teach me much new > %> bunzip2 < /opt/local/var/macports/registry/registry-corrupt.db.bz2 > kk.db > %> /opt/local/bin/sqlite3 kk.db > %> .load MacPorts-svn/src/cregistry/macports.sqlext > %> pragma integrity_chec

Re: Errors should probably come after notes?

Hi, On Fri, Apr 08, 2016 at 09:29:35PM +0200, Mojca Miklavec wrote: > What I don't like so much is that the notes come *after* the error > report. I ended up with about 10 notes following the error, so I could > easily have missed the fact that there was an error at all (I had to > scroll a few sc

Re: Getting new port comitted: asciidoctor

Hello Guido, On Tue, Apr 19, 2016 at 08:49:28AM +0200, Guido Kollerie wrote: > Can the new port `asciidoctor` be committed by someone? Suggested > changes were made. All that remains is for someone to add it to the > ports collection. > > https://trac.macports.org/ticket/51087 Committed in https

Re: [MacPorts] MacPortsDevelopers modified

Hi Marius, On Wed, Apr 27, 2016 at 12:39:18AM +, MacPorts wrote: > Page "MacPortsDevelopers" was changed by m...@macports.org > Diff URL: > > Revision 293 > Changes: > ---8<--8<--8<--8<--8<--8<

Re: file/dir name case (in)sensitivity

Hi, On Fri, May 06, 2016 at 12:51:57PM +0200, René J.V. Bertin wrote: > Would it be worthwhile to figure out and put up an advanced topic > describing how to set up MacPorts to use a case-sensitive ${prefix} > while still being able to benefit from binary packages? Our buildbots use case-sensitiv

Re: Debian/Ubuntu-style -dev ports

Hi, On Thu, May 19, 2016 at 12:45:48AM +0200, René J.V. Bertin wrote: > On Wednesday May 18 2016 17:50:00 Brandon Allbery wrote: > > > The problem with this is that if a MacPorts user can't get something from a > > prebuilt package, you have to force both the "user" and "developer" ports > > to b

Re: [150004] trunk/dports/python/py-ipython/Portfile

: Unable to verify file checksums -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Reason why default rsync URL was changed to a tarball

s a flag we could pass to tar to only extract new or changed files that would speed up this process? -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [150874] trunk/dports/lang/python32

FWIW, I agree with Lawrence here. I think we should improve our patch naming, especially since it doesn't really matter *where* a patch comes from, either. Why do we really need to know whether a patch-*.diff file comes from MacPorts when compared to a different patch? We should be judging patches

Re: Determine before installation whether a port can be installed

Hi, On Thu, Jul 28, 2016 at 03:21:56AM -0500, Ryan Schmidt wrote: > However, as I've said, there are other reasons why a port might not be > able to install. Should we really modify MacPorts base and create new > variables to accommodate each of those reasons? Is there a specific > objection to wh

Re: [151215] contrib/mp-buildbot

Hi Mojca, a couple of review comments inline below. On Wed, Aug 10, 2016 at 11:09:30AM -0700, mo...@macports.org wrote: > Revision: 151215 > https://trac.macports.org/changeset/151215 > Author: mo...@macports.org > Date: 2016-08-10 11:09:29 -0700 (Wed, 10 Aug 2016) > Log Message:

ports.tar update frequency on new mirror

Hi Ryan, I'm wondering what update frequency I can expect for ports.tar on the new main mirror. I have a cronjob set up that regularly checks whether ports.tar has not been updated in a while; it came in handy a couple of times because most developers usually sync using SVN and would not notice t

Re: our buildslaves' Python and bash

Hi, On Wed, Aug 10, 2016 at 04:52:02PM -0400, Lawrence Velázquez wrote: > Are the buildslaves using the OS-provided bash (for mpbb) and > MacPorts' python27 (for Buildbot), or what? It's very likely the OS-provided bash, since mpbb's shebang says /bin/bash. As for Python, I think there's a separa

Re: How to discontinue ports completely (py26 deprecation) ...

On Wed, Aug 10, 2016 at 04:47:25PM -0500, Ryan Schmidt wrote: > On Aug 10, 2016, at 13:18, Peter Danecek wrote: > > > > However, how would we procede in this case, when we have no explicit > > replacement to indicate? > > I believe the obsolete 1.0 portgroup can accommodate this: include the > p

Re: [151264] contrib/mp-buildbot/mpbb-install-port

Hi Mojca, On Wed, Aug 10, 2016 at 11:48:51PM -0700, mo...@macports.org wrote: > Revision: 151264 > https://trac.macports.org/changeset/151264 > Author: mo...@macports.org > Date: 2016-08-10 23:48:51 -0700 (Wed, 10 Aug 2016) > Log Message: > --- > mp-buildbot/install-port: a

Re: [151267] contrib/mp-buildbot

Hi Mojca, On Thu, Aug 11, 2016 at 01:03:06AM -0700, mo...@macports.org wrote: > Revision: 151267 > https://trac.macports.org/changeset/151267 > Author: mo...@macports.org > Date: 2016-08-11 01:03:06 -0700 (Thu, 11 Aug 2016) > Log Message: > --- > mp-buildbot: add (not too h

Re: [MacPorts] WorkingWithGit modified

Hi Marko, On Sun, Aug 21, 2016 at 06:55:25AM +, MacPorts wrote: > Page "WorkingWithGit" was changed by m...@macports.org > Diff URL: > > Revision 20 > Comment: Add basic setup info based on KDE's configuration hints > Chan

Re: how about a 'snowleopardfixes' library port?

Hi, On Tue, Aug 23, 2016 at 10:00:05AM -0700, Ken Cunningham wrote: > clang -dynamiclib -std=gnu99 strnlen.c getline.c -current_version 1.0 > -compatibility_version 1.0 -o libsnowleopardfixes.a.dylib You need -install_name ${prefix}/lib/libsnowleopardfixes.a.dylib here. > configure:3663: ./conf

Fakeroot destrooting [Was: Re: lldb ...]

Hi, On Fri, Sep 09, 2016 at 01:59:50PM -0700, Jeremy Huddleston Sequoia wrote: > > As an aside, I'd be in favour of setting up MacPorts such that > > ${prefix} is owned by a ${macports_operator} who's got admin rights > > (= myself) and reserve use of actual root privilege to those few > > ports t

Re: Fakeroot destrooting [Was: Re: lldb ...]

Hi, On Sat, Sep 10, 2016 at 02:42:36PM +0200, René J.V. Bertin wrote: > >Except that fakeroot uses library preloading, a technique that's more > >or less dead on modern OS X thanks to Apple's changes related to SIP: > >DYLD_INSERT_LIBRARIES is stripped for all binaries with the SIP bit > >set. >

Re: Fakeroot destrooting [Was: Re: lldb ...]

Hi, On Sat, Sep 10, 2016 at 03:45:25PM +0200, René J.V. Bertin wrote: > But I see quite a few items on there that are unlikely to call other > applications. If this is only about preserving DYLD_LIBRARY_PRELOAD, > why do you need to treat utilities like cat or rm? cat and rm deal with files, cons

Re: Fakeroot destrooting [Was: Re: lldb ...]

Hi, On Sat, Sep 10, 2016 at 09:14:16AM -0700, Jeremy Huddleston Sequoia wrote: > No, the DYLD_INSERT_LIBRARIES approach is the right one here. > Interested users would need to disable SIP. "Interested users" would be everybody who uses MacPorts. I'd vote against telling all our users to disable S

Re: [152507] contrib/mp-buildbot/mpbb-cleanup

Hi, On Sun, Sep 11, 2016 at 11:47:58AM -0700, rai...@macports.org wrote: > Revision: 152507 > https://trac.macports.org/changeset/152507 > Author: rai...@macports.org > Date: 2016-09-11 11:47:58 -0700 (Sun, 11 Sep 2016) > Log Message: > --- > buildbot: skip cleanup if port

Re: [152507] contrib/mp-buildbot/mpbb-cleanup

Hi, On Mon, Sep 12, 2016 at 10:53:04AM +0200, Rainer Müller wrote: > The 'return' just skips everything else in this step, so that would be > covered. Yes, sorry, I haven't had my coffee yet. > Another solution would be to run selfupdate before the cleanup step to > ensure we always cleanup with

RFC: mp-buildbot failcache

ose +# shellcheck disable=SC2086 +failcache_success "$depname" $depvariants dependencies_counter=$((dependencies_counter + 1)) fi done Index: mpbb-install-port ======= --- mpbb-i

Re: Goodbye Mac OS Forge, hello GitHub

I think the conversion rules should be good to go, but IIRC Ryan wanted to do some commit message rewriting for ticket references. I'm not sure what the state on this is. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.mac

Re: [MacPorts] WorkingWithGit modified

On Fri, Sep 23, 2016 at 01:08:38PM -0500, Ryan Schmidt wrote: > Something I did not see discussed on this page was that after you > fork, and before you start making changes, you should create a branch > specific to the work you are doing. I didn't include this because it's not how I normally work

Re: [MacPorts] WorkingWithGit modified

Hi, On Fri, Sep 23, 2016 at 01:38:43PM -0500, Ryan Schmidt wrote: > > On Sep 23, 2016, at 13:33, Clemens Lang wrote: > > > > I didn't include this because it's not how I normally work. I > > usually only create branches for larger changes. I wouldn'

Re: [MacPorts] WorkingWithGit modified

Hi, On Fri, Sep 23, 2016 at 11:56:19AM -0700, Sterling Smith wrote: > Being a co-maintainer of a software project hosted on GitHub, where > the main developer does not use branches leads to inconsistencies in > how his contributions are handled vs other developers. What would those inconsistencie

Re: [MacPorts] WorkingWithGit modified

Hi, On Fri, Sep 23, 2016 at 02:14:25PM -0500, Ryan Schmidt wrote: > True but I'd like to default to assuming a user will make a valuable > contribution and will want to make additional contributions in the > future. And our track record of accepting patches in Trac in a timely > fashion is not goo

Re: [153120] trunk/dports/fuse/sshfs

Hi, On Mon, Sep 26, 2016 at 11:23:17AM -0700, Dan Ports wrote: > For me, the main benefit is that it's immediately obvious where the > patch comes from, and, since it's github, how it relates to the > release version. (In this case, it's a backported patch from an > unreleased version.) This is s

Re: CMake issue: binary (needed during build) links againts /opt/local/lib/foo.dylib

TH_handling Try changing - CMAKE_BUILD_WITH_INSTALL_RPATH (it should be false), - CMAKE_SKIP_BUILD_RPATH (should be false) and - CMAKE_INSTALL_RPATH_USE_LINK_PATH (try both?) HTH, -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.mac

Re: ${prefix} as a disk-image (was: #49559: nepomuk-core can't be installed on a case-sensitive system)

Hi, On Sat, Oct 01, 2016 at 10:33:08PM +0200, René J.V. Bertin wrote: > I coined this admittedly a bit wild idea the other day that all of > ${prefix} could be hosted on a R/W dynamic disk image, aka a sparse > image or sparse bundle. Sparse Bundles have the huge downside that they don't shrink a

Re: Working with Git

d used git cherry-pick $your_commit_id. I then edited your change using git commit --amend and git rebase --interactive and pushed. The Author field of the commit was not modified, but the Committer field was changed to me, which is why you see "ryandesign committed with neverpanic". HTH,

Re: CMake issue: binary (needed during build) links againts /opt/local/lib/foo.dylib

ing. > The command "otool -L cfg" reports >@rpath/libMiKTeX209-core.1.dylib That looks correct, but really depends on what "cfg"'s rpath is. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org ht

Re: CMake issue: binary (needed during build) links againts /opt/local/lib/foo.dylib

uot; is a binary. I'm not sure whether it gets installed, but it > does, then the path is definitely wrong. The settings I gave you tell CMake to re-link the binary without an rpath on 'make install', so if you ran this in the build tree (whi

Re: Issues with oudated ports / GitHub

Hi, On Fri, Oct 07, 2016 at 09:13:11AM -0500, Ryan Schmidt wrote: > Regarding updating pandoc, see https://trac.macports.org/ticket/48324 > Regarding updating ghc, see https://trac.macports.org/ticket/48899 > Regarding old llvm on Sierra, see https://trac.macports.org/ticket/52424 As a follow-up

Re: reasons for `port provides` not working?

ocally are not supported by MacPorts. I won't spend any time diagnosing this unless you can show that it's broken in a fresh install. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: reasons for `port provides` not working?

quot;unless you can proof it's me, it's you" isn't helpful. I've had enough of it. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Documentation overhaul

Hi, On Mon, Oct 10, 2016 at 09:44:17PM +0200, Rainer Müller wrote: > Now here is Marcel offering his help with the documentation. I do not > want to turn down his offer or stop him from contributing in any way. > > [...] > > If Marcel has time right now, I think he should just start with the > do

Re: MP Cert Revoked?

/twitter.com/globalsign/status/786505261842247680 See also http://apple.stackexchange.com/a/257082 The problem is with the intermediate, not with our certificate, it seems. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosfor

Re: advanced bash-ing for long compiles

"fixes" it. If preventing indexing is the sole reason for > hiding the directory, wouldn't using ".metadata_never_index" be better? MacPorts re-hides the directory. Indexing is the only reason to hide it. If you have a link to documentation th

Re: 2nd MacPorts Meeting & Online Meeting

Hi, On Mon, Oct 10, 2016 at 07:53:13AM +0200, Mojca Miklavec wrote: > Me and Aljaž would be willing to host the MacPorts meeting in 2017 > again. Thanks, and sorry for not putting a plan together to do it in Munich in the fall. Seems I need to improve my time management :) > In addition to the

Re: 2nd MacPorts Meeting & Online Meeting

Hi Marko, On Mon, Oct 17, 2016 at 12:38:20AM +0200, Marko Käning wrote: > now that you say it… Weren’t you aiming at the Wiesn earlier this > year? ;-) Well, as you noticed, that didn't happen ;) > I noticed that there is eventually an official MacPorts ports git repo > [1] online since a few d

Moving to GitHub: Status Update, Action Required

ation team, Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Trac & Subversion available again

Hello MacPorts users and developers, On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote: > Due to the current SVN and Trac downtime, we are also discussing to > make the move of Trac sooner if that helps us restore service earlier. > We will keep you informed on this. D

Re: Moving to GitHub: Status Update, Action Required

Hi, On Sat, Oct 22, 2016 at 02:31:32PM +0200, Marko Käning wrote: > When reading the WorkingWithGit wiki page [1] I saw how port > contributors can post their suggestions to MacPorts via "Pull > Requests”, yet it does not get clear from that text how those PRs will > then actually be included into

Re: port:qt5 and (proposed) port:qt5-kde cohabitation

On Sun, Oct 23, 2016 at 11:25:52AM +0200, René J.V. Bertin wrote: > SVN is being retired completely? Yes, SVN is being retired completely. Have you not read the announcement emails? > I noticed it for Trac (which isn't a complete improvement *). I'm not > aware that git allows pulling only change

Re: port:qt5 and (proposed) port:qt5-kde cohabitation

Hi, On Sun, Oct 23, 2016 at 05:01:08PM +0200, René J.V. Bertin wrote: > Apparently not, were they sent on this ML? If so I must have applied > too strict filters (basically "don't send list messages and don't > filter copies sent to my own address" ...) https://lists.macosforge.org/pipermail/macp

Re: port:qt5 and (proposed) port:qt5-kde cohabitation

Hi, On Sun, Oct 23, 2016 at 06:01:13PM +0200, René J.V. Bertin wrote: > Thanks for the archive links. A quick scan suggests that my "shadow" > tree I referred to will be a new working copy of the git repo, from > where I'll filter things into the current svn tree. There will be no svn tree in a w

Re: port:qt5 and (proposed) port:qt5-kde cohabitation

On Sun, Oct 23, 2016 at 08:00:25PM +0200, René J.V. Bertin wrote: > I meant my local copy evidently which I'll most like keep in > sources.conf and update from the new git working copy. If the svn > history is migrated to github I'll be able to delete the .svn > directory. Sorry, I was assuming th

Re: Git tools for managing patchsets

Hi, On Mon, Oct 24, 2016 at 09:37:37AM -0700, Michael wrote: > So since MacPorts is moving to git, and from what I saw in the "how to > use git" docs you mentioned, you apparently want people to work with > patchsets rebased onto the current head from upstream. > > As I was thinking about that, I

Re: Trac & Subversion available again

Hi, On Mon, Oct 24, 2016 at 12:54:23PM -0400, Daniel J. Luke wrote: > This looks like it's true for me as well (cannot edit tickets beyond > making comments). Try clearing your cache (a force-reload should do that). It seems the problem can also be that the edit form is there, but hidden for you

Re: Moving to GitHub: Status Update, Action Required

Hi, On Mon, Oct 24, 2016 at 06:50:47PM +0200, Mojca Miklavec wrote: > Is that true also for any other email we used prior to becoming > committers? Yes. > Can new emails be added later? Yes, but you'll have to relogin. > How exactly does it work when people enter multiple emails? (Judging > fr

Re: Git tools for managing patchsets

Hi, On Mon, Oct 24, 2016 at 10:29:19AM -0700, Michael wrote: > My understanding -- and maybe this is my error here -- is that your > patches have to be constantly rebased onto the current version every > time the upstream releases a new version. I think our understanding of what "upstream" is in

Re: Moving to GitHub: Status Update, Action Required

On Mon, Oct 24, 2016 at 07:47:18PM +0200, Mojca Miklavec wrote: > I can send you a screenshot comparing the version I opened two hours > ago and the same page reloaded just now. The result changed in the > meantime. In any case I can no longer provide you any broken example > (there are still some

Re: Moving to GitHub: Status Update, Action Required

Hi, On Mon, Oct 24, 2016 at 08:00:04PM +0200, Vincent Habchi wrote: > I’ve bought Coda 2 when I use to do a bit of HTML development. Can I > use it to check out - tinker with the new MacPorts GIT repository? You should check with the developers of Coda on their Git support. I don't think a tool b

Re: Moving to GitHub: Status Update, Action Required

On Mon, Oct 24, 2016 at 08:22:38PM +0200, Mojca Miklavec wrote: > Even if the method of achieving this is not prescribed***, I wouldn't > mind a bit of testing before screwing up the real repository. > > *** But having some cheatsheet would help. Sure, feel free to create a fork, play around, add

Re: Git tools for managing patchsets

On Mon, Oct 24, 2016 at 11:57:51PM +0200, Marko Käning wrote: > The only question mark I have there is: > > Will we ask the committers to squash their changesets or prefer to > clutter the main repo with potentially many tiny iterations for the > changed ports?? I think "clutter

Re: Moving to GitHub: Status Update, Action Required

Hi, On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote: > A description of how exactly one would rebase (potentially squash and > history-rewrite) a submitted PR onto current master should be on our > WorkingWithGit wiki page. the easiest approach is just clicking the button that does t

Re: "Failed to open portfile from registry" while reinstalling because of configure.optflags

Hi, On Tue, Oct 25, 2016 at 08:34:31AM -0500, Ryan Schmidt wrote: > I don't know the answers to your questions, but I wanted to mention > that I also have noticed the "Failed to open portfile from registry" > error far more often than seems normal to me. ("Never" would seem > normal to me.) Inter

Re: "Failed to open portfile from registry" while reinstalling because of configure.optflags

Hi, On Tue, Oct 25, 2016 at 05:06:27PM -0500, Ryan Schmidt wrote: > Ah. So the error message is just wrong? There isn't actually a problem > opening the portfile from the registry; there's a problem running the > portfile that was successfully opened and read? Yes, unless of course you randomly d

Re: "Failed to open portfile from registry" while reinstalling because of configure.optflags

Hi, On Wed, Oct 26, 2016 at 12:29:10AM +0200, René J.V. Bertin wrote: > The issue I mentioned that I fixed was such an example of an > oversight. I'd imposed the condition of reading a "companion" > PortGroup from the same directory as the main PortGroup, and that > condition cannot hold for copie

Re: "Failed to open portfile from registry" while reinstalling because of configure.optflags

Hi, On Wed, Oct 26, 2016 at 02:17:53AM +0200, René J.V. Bertin wrote: > Yeah. There could be a check if the Portfile exists to catch the 1st > possibility That would introduce a race condition, wouldn't it? Checking whether a file exists before doing something with it is a classic mistake. > and

  1   2   3   4   5   6   7   8   >