On 15/06, Tom Swartz wrote:
Hi all,
The majority of my work happens behind corporate firewalls where ssh out
via port 22 is not an option.
Is there a way to configure GitHub-like SSH via HTTPS ports?
https://help.github.com/articles/using-ssh-over-the-https-port/
I'd be greatly appreciative
Hi all,
The majority of my work happens behind corporate firewalls where ssh out
via port 22 is not an option.
Is there a way to configure GitHub-like SSH via HTTPS ports?
https://help.github.com/articles/using-ssh-over-the-https-port/
I'd be greatly appreciative if this was the case.
Thanks!
It is not necessarily Arch's problem that a tiny minority of users have the
standard connection methods blocked. While it would be nice if lots of
options are offered for every possible scenario, that may not necessarily
happen.
Think of Github's alternative method as being a bonus, not something
On Mon, 15 Jun 2015 at 23:37:16, Daniel Sandman wrote:
So I fucked up I was going to move over my AUR packages to AUR4.
Couldn't log in on AUR4 and I wanted to make a new user anyway. So I
deleted my account on on AUR. Now I am unable to recreate it on AUR4 as
I use the same email
On Mon, Jun 15, 2015 at 1:18 AM, Phillip Smith fuka...@gmail.com wrote:
Rght! Gotcha! That makes a lot more sense -- I was assuming there
was something required within the umbrella repo to setup/configure
the child repos etc.
Thanks, I'll go have a play :)
On the advice of Marcel Korpel
Em 15-06-2015 22:20, Tom Swartz escreveu:
I'm not requiring that others solve my problem, Giancarlo.
As mentioned, this is an impossibility in our organization, and (I'm sure)
many others.
Not that many, I hope.
There are many technical reasons for this limitation in our organization,
too
On 16 June 2015 at 14:26, Eli Schwartz eschwart...@gmail.com wrote:
FWIW you can use filter-branch to run mksrcinfo on each folder in your
current aur-packages repo, then merge in my base branch and continue on as
before. Might have to resolve a conflict between our .gitignores, (I may be
Instead of requiring others to solve your problem, you should explain to
your network administrators that this rule is counterproductive. I don't
really think that this will hinder adoption since port 22 is the default
ssh port.
I'm not requiring that others solve my problem, Giancarlo.
As
Em 15-06-2015 16:26, Tom Swartz escreveu:
With all due respect, requiring that a user punch holes in their security
firewalls is not a proper or long term solution to the issue at hand.
It is the only solution.
For home users, this might be a valid (although no less sane) solution, but
in
2015-06-15 16:33 GMT-03:00 Giancarlo Razzolini grazzol...@gmail.com:
Em 15-06-2015 16:26, Tom Swartz escreveu:
With all due respect, requiring that a user punch holes in their security
firewalls is not a proper or long term solution to the issue at hand.
It is the only solution.
Is not
Le 15/06/2015 22:00, Pablo Lezaeta Reyes a écrit :
2015-06-15 16:33 GMT-03:00 Giancarlo Razzolini grazzol...@gmail.com:
Em 15-06-2015 16:26, Tom Swartz escreveu:
A rule that denies outgoing SSH access is a dumb one. It doesn't protect
the rest of the devices on the network.
In my school
So I fucked up I was going to move over my AUR packages to AUR4.
Couldn't log in on AUR4 and I wanted to make a new user anyway. So I
deleted my account on on AUR. Now I am unable to recreate it on AUR4 as
I use the same email address. Is there any sane way to fix this?
If your network admins don't know the difference between incoming and
outgoing ports, or not opening things like ssh ports to the internet that
really isn't an Arch problem...
- Justin
--
Regards,
Justin Dray
E: jus...@dray.be
M: 0433348284
=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 1 new package in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 6 packages missing signoffs
* 4 packages older than 14 days
On 15 June 2015 at 15:25, Eli Schwartz eschwart...@gmail.com wrote:
Like I said, you should be able to pretend it is one vanilla repo,
just like many people used to track their AUR3 packages. But .SRCINFO
is required for this one, because each folder is *exported* to the
AUR4.
Rght!
Em 15-06-2015 17:00, Pablo Lezaeta Reyes escreveu:
Is not the only as pointer in this thread,
also you not considered the idea that burocracy for somethink that
simple as oppen a port could take months if not year or even coutless
failed attempts?
Well, each organization has it's own
16 matches
Mail list logo
