Re: [macports-ports] 01/02: New port for wallet @1.3

Hi Ryan, On Sat, Nov 05, 2016 at 03:40:48AM -0500, Ryan Schmidt wrote: > You should not use newlines in notes, unless you actually want the > user to see a newline there, for example if you are starting a new > paragraph or are constructing a list of items. Thanks, fixed:

Re: PR usage by people with commit access

Hi, On Fri, Nov 04, 2016 at 10:10:44AM -0700, Ivan Larionov wrote: > I think this is a good practice for port maintainers with write access > to repository still use PRs instead of direct commits to master. I agree, with some limitations: > * Better visibility of changes. Instead of cloning

Using a different bugtracker [Was: Re: Poll: should Trac send email notifications when adding or replacing an attachment?]

itations we actually found, which is why we ended up staying with Trac. We also looked into other bugtrackers, and there was no clear benefit over Trac to justify switching. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge

Re: Proposal for a MacPorts'ish commit message template

On Wed, Nov 02, 2016 at 05:46:16PM -0500, Ryan Schmidt wrote: > Well, you mentioned vim. Very occasionally I use that. I don't > remember seeing any particular syntax highlighting in it when editing > a commit message. You need syntax highlighting (:syntax on) and ideally color enabled.

Re: GitHub usernames as maintainers

On Wed, Nov 02, 2016 at 06:45:21PM -0400, Brandon Allbery wrote: > For me, it looks too much like an email address when combined with > other things (e.g. "maintainers openmaintainer @foo"). I think that's a formatting problem. We could just as well print https://github.com/neverpanic in the

Re: Proposal for a MacPorts'ish commit message template

On Wed, Nov 02, 2016 at 05:33:28PM -0500, Ryan Schmidt wrote: > > vim does that with syntax highlighting automatically nowadays when > > it notices you are writing a commit message. If you need an > > indication on your line width, may I suggest you configure your > > editor appropriately? > >

Re: GitHub usernames as maintainers

On Wed, Nov 02, 2016 at 05:27:30PM -0500, Ryan Schmidt wrote: > On Nov 2, 2016, at 1:49 AM, Mojca Miklavec wrote: > > It would be nice if "port info" would also print the github > > usernames of maintainers. > > When we were originally planning the transition to GitHub, I suggested > that we

Re: [macports-ports] branch master updated: libcxx: Bump to 3.9.0 (#52666)

Hi, On Wed, Nov 02, 2016 at 09:57:37AM -0700, Bradley Giesbrecht wrote: > Can you pass multiple tickets (closes x y z)? Yes, space-separated, comma-separated, or because the ticket references are quite long, just with multiple Closes $ticket lines. -- Clemens

Re: Proposal for a MacPorts'ish commit message template

Hi, On Tue, Nov 01, 2016 at 11:51:52PM +0100, Marko Käning wrote: > I know that many of you weren't in favour of a commit message > template, but I propose one anyway, which I derived from KDE’s neat > one, Developers are free to use your template if they want to. We don't want to mandate using

GitHub usernames as maintainers [Was: Re: [macports-ports] branch master updated: berkeleygw: Remove svn $Id$ line.]

On Tue, Nov 01, 2016 at 07:42:23PM +0100, Mojca Miklavec wrote: > If someone submits a pull request for a maintained port, the > maintainer should probably be notified explicitly with @username. The > problem is that currently only Trac maintainers have access to that > mapping. It's not a set of

Re: rev-upgrade question

On Tue, Nov 01, 2016 at 07:09:48PM +0100, Marko Käning wrote: > how can I convince rev-upgrade to actually rebuild broken ports if > 'revupgrade_mode' is set to ‘report' in macports.conf? You can specifically rebuild them manually using port -nf upgrade $port.

Re: Removing "$Id$" lines

Hi, On Tue, Nov 01, 2016 at 10:38:42AM -0700, Bradley Giesbrecht wrote: > Would it work as well to have the buildbots ignore commits with > unchanged epoch_version_revision. That's https://trac.macports.org/ticket/52765. It would still take the time to process the change and figure out that a

Re: querying the registry for reverse dependencies

Hi, On Tue, Nov 01, 2016 at 03:10:30PM +0100, René J.V. Bertin wrote: > A variant of my earlier question: is there a magic formula to query > the registry which files (and/or ports) depend on a given binary file? > IOW, an elegant alternative to something like No, there's no such thing in the

Re: [macports-ports] branch master updated: jasper: needs a revbump

On Mon, Oct 31, 2016 at 08:08:26PM +0100, Marko Käning wrote: > Doesn’t the second build of jasper justify the revbump, or should we > simply ignore this and let rev-upgrade take care of it?? The revbump is justified. Your commit message should have mentioned why it was necessary, though. --

Re: Moving to GitHub: Status Update, Action Required

Hi, On Mon, Oct 31, 2016 at 10:25:33AM +0100, Davide Liessi wrote: > I have just noticed in one of my GitHub repositories that in Settings > -> Options there is a "Merge button" section that lets you > enable/disable the behaviours of the merge button described in the > above link. > Maybe you

Re: GitHub migration complete

Hi, On Mon, Oct 31, 2016 at 10:18:42AM +0100, René J. V. Bertin wrote: > I may have overlooked this, but does github have any provisions that > would allow the PortIndex files to be generated on the server and > served with the actual repo contents? That would probably give a very > significant

GitHub migration complete

in Trac against the "server/hosting" component. On behalf of the MacPorts migration team, Lawrence Velázquez Rainer Müller Ryan Schmidt Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.o

Subversion switched to read-only

Hi everybody, we are making Subversion read-only in a couple of seconds. If you get an error message when comitting that is expected. We will re-configure a couple of hooks and tools to the new GitHub-based setup and then enable write access on GitHub. We try to keep the downtime short and will

Re: Compiling dnsmasq with dnssec support?

Hi, On Sun, Oct 30, 2016 at 04:50:33PM +0100, Johannes Kastl wrote: > Thanks Rainer, I'll try that. I'd suggest to just enable it without a variant. If it's configurable at runtime, I don't see the need to make users jump through hoops. -- Clemens

Re: git fetch fails because of gnutls_handshake

Hi, On Sat, Oct 29, 2016 at 08:21:23PM -0700, Fred Wright wrote: > Though if the new "Cc me" button were any smaller, it would be > considered a web bug. :-) That's https://trac.macports.org/ticket/52675 If you have time, read through the ticket and submit a pull request to fix it. --

Re: git fetch fails because of gnutls_handshake

Hi, On Sat, Oct 29, 2016 at 02:48:32PM +0200, René J.V. Bertin wrote: > Hi, > > I'm seeing this on one of my systems (haven't been able to try others yet): > > {{{ > DEBUG: Executing org.macports.fetch (git) > ---> git-2.10.1.tar.gz doesn't seem to exist in >

Re: querying the registry for installed files

On Fri, Oct 28, 2016 at 08:41:58PM +0200, René J.V. Bertin wrote: > I think the registry keeps track of all installed files, whether they > belong to active or inactive ports, right? > If so, is there a way to query the registry with a filename pattern, > to obtain the full paths of known matching

Re: Trac down again

On Wed, Oct 26, 2016 at 09:13:33PM +0200, Marko Käning wrote: > Where is our trac again? I've kicked it. Not exactly sure what causes these outages, it's probably some crawler that fills a queue with requests and causes all of them to be dropped due to timeout after a while. We're keeping an eye

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. >

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

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

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.)

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

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

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,

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

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: 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

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 >

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,

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

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

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" ...)

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

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

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 t

Moving to GitHub: Status Update, Action Required

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

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

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: 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: 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 >

Re: reasons for `port provides` not working?

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: reasons for `port provides` not working?

cPorts. 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: 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: CMake issue: binary (needed during build) links againts /opt/local/lib/foo.dylib

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 (which I assumed because

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 https:/

Re: Working with Git

ry-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, -- Clemens La

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

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

ndling 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.macosfor

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

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

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

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 <c...@macports.org> wrote: > > > > I didn't include this because it's not how I normally work. I > > usually only create branches for larger changes. I woul

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

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.macosforge.or

RFC: mp-buildbot failcache

= --- mpbb-install-port (revision 152544) +++ mpbb-install-port (working copy) @@ -55,10 +55,15 @@ time_start=$(date +%s) # $option_prefix is set in mpbb # shellcheck disable=SC2154 -if ! "${option_prefix}/bin/port&q

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

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: 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

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,

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. >

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

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:

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 > Changes: >

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

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:

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

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

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

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:

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

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: Reason why default rsync URL was changed to a tarball

ss 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: [150004] trunk/dports/python/py-ipython/Portfile

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

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

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

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: >

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

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

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

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

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: 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

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

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-

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

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

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

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

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

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: 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

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: 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

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

  1   2   3   4   5   6   7   >