Dear,
(Note: This mail was sent through my personal e-mail address instead of my
work one (steven.tond...@dentsplysirona.com) because our corporate mail
server is badly configured (SPF Fail), something I will not be able to
change)
On December 6th I provided a ticket with path to update the ‘mo
Thanks for the heads-up, commited in a8560584ef.
On 21 dicembre 2016 at 09:28:58, Steven Tondeur (steventond...@gmail.com) wrote:
The ticket has been assigned on the same day (hurray!); no further
communication since then. Can you review/commit the patch included in the
ticket?
signature.asc
While trying to push a small change (shell/xonsh) I managed to rebase
AND merge the about 300 commits since my previous update,
as a results those 300 commits in master now are "duplicated".
The files in master are unaltered, except for the actual portfile I
was pushing, but the history is now mes
On 2016-12-21 11:41, Andrea D'Amore wrote:
> While trying to push a small change (shell/xonsh) I managed to rebase
> AND merge the about 300 commits since my previous update,
> as a results those 300 commits in master now are "duplicated".
>
> The files in master are unaltered, except for the actu
On 2016-12-21 04:20, Jeremy Huddleston Sequoia wrote:
> Can we please configure base on these older builders to use MacPorts'
> libcurl+libressl/newer OpenSSL (or just a special one we can install to
> /opt/curl) instead of the host's version? More and more source mirrors are
> dropping support
Found the issue, got send this related issue
https://trac.macports.org/ticket/50469.
I commented out a line from /opt/local/etc/macports/macports.conf;
macportsuser root
And it works, no idea why that line is in that file as I don't believe
I would have ever put it in their myself.
ansible is no
On 21 December 2016 at 12:38, Rainer Müller wrote:
> On 2016-12-21 11:41, Andrea D'Amore wrote:
>> While trying to push a small change (shell/xonsh) I managed to rebase
>> AND merge the about 300 commits since my previous update,
>> as a results those 300 commits in master now are "duplicated".
>>
Hi,
Here's what the competing system is doing:
https://github.com/Homebrew/homebrew-boneyard
Citation:
This repository contains formulae that were removed from other
repositories. Common reasons for retiring formulae to the boneyard
include lack of upstream maintenance or problems integratin
I've created a clean branch on my fork. If you want to clean the
history, first cancel branch protection in repository's settings, then do
git remote add https://github.com/l2dy/macports-ports.git
git fetch --all
git checkout master
git reset --hard l2dy/fix-history
git push -f
to reset mas
On 2016-12-21 16:39, Mojca Miklavec wrote:
> On 21 December 2016 at 12:38, Rainer Müller wrote:
>> On 2016-12-21 11:41, Andrea D'Amore wrote:
>>> While trying to push a small change (shell/xonsh) I managed to rebase
>>> AND merge the about 300 commits since my previous update,
>>> as a results thos
On 21 December 2016 at 17:33, Rainer Müller wrote:
> On 2016-12-21 16:39, Mojca Miklavec wrote:
>> On 21 December 2016 at 12:38, Rainer Müller wrote:
>>> On 2016-12-21 11:41, Andrea D'Amore wrote:
While trying to push a small change (shell/xonsh) I managed to rebase
AND merge the about 3
> On Dec 21, 2016, at 06:22, Vincent wrote:
>
> Vincent (Veence) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/6879a39dde564230f06179065fe1afeeed8a8175
>
> The following commit(s) were added to refs/heads/master by thi
On Dec 21, 2016, at 04:41, Andrea D'Amore wrote:
> While trying to push a small change (shell/xonsh) I managed to rebase
> AND merge the about 300 commits since my previous update,
> as a results those 300 commits in master now are "duplicated".
>
> The files in master are unaltered, except for
On 21 December 2016 at 18:44, Ryan Schmidt wrote:
> On Dec 21, 2016, at 04:41, Andrea D'Amore wrote:
>
>> While trying to push a small change (shell/xonsh) I managed to rebase
>> AND merge the about 300 commits since my previous update,
>> as a results those 300 commits in master now are "duplicate
I agree with Mojca, it looks messy now!
We better fix it fast.
Someone with admin access to the repo should be able to fix this if we don’t
wait too long.
I think we should somehow make sure that such merged branches cannot be pushed
to the main repo, if rebasing is our policy for all committers
> On Dec 20, 2016, at 20:00, Kurt Hindenburg wrote:
>
> Kurt Hindenburg (kurthindenburg) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/ae81c668093b56cc220726e69154fa6f73e23f2d
>
> The following commit(s) were added to
On Dec 21, 2016, at 8:18 AM, John Patrick wrote:
> I commented out a line from /opt/local/etc/macports/macports.conf;
> macportsuser root
That should never be set that way.
> And it works, no idea why that line is in that file as I don't believe
> I would have ever put it in their myself.
That'
Hi Andrea,
I just saw this when running portindex on my El Capitan VM:
Failed to parse file shells/xonsh/Portfile with subport 'xonsh-devel':
invalid command name "BASHwards-looking”
Greets,
Marko
On Dec 21, 2016, at 3:47 PM, Marko Käning wrote:
> I just saw this when running portindex on my El Capitan VM:
>
> Failed to parse file shells/xonsh/Portfile with subport 'xonsh-devel':
> invalid command name "BASHwards-looking”
yep, I just pushed a fix for the missing \ in the descriptio
On 21 Dec 2016, at 21:51 , Daniel J. Luke wrote:
> yep, I just pushed a fix for the missing \ in the description in the subport.
:) Just wanted to push that fix myself, but you beat me there!
On 2016-12-22 07:41 , Daniel J. Luke wrote:
On Dec 21, 2016, at 8:18 AM, John Patrick wrote:
I commented out a line from /opt/local/etc/macports/macports.conf;
macportsuser root
That should never be set that way.
And it works, no idea why that line is in that file as I don't believe
I would
One of the ways to avoid it is to review things you're going to merge. And
one of the easiest ways to do it is to open a PR on github where you can
clearly see which commits you're going to merge. I was similar errors
multiple times when people do `git pull` instead of `git pull --rebase` and
it wa
On 21 December 2016 at 21:54, Marko Käning wrote:
> On 21 Dec 2016, at 21:51 , Daniel J. Luke wrote:
>> yep, I just pushed a fix for the missing \ in the description in the subport.
> :) Just wanted to push that fix myself, but you beat me there!
Be honest, you guys are just scared of my push-fu
On 21 December 2016 at 22:38, Ivan Larionov wrote:
> One of the ways to avoid it is to review things you're going to merge. And
> one of the easiest ways to do it is to open a PR on github where you can
> clearly see which commits you're going to merge.
That doesn't necessarily help. The author ca
24 matches
Mail list logo
