On Sat, Feb 18, 2017 at 9:39 AM, Ben Finney wrote:
> Does the resulting repository automatically get published on Alioth,
> managed by ‘cgit’ at a ‘anonscm.debian.org’ URL?
cgit doesn't do any management, it just publishes existing repos.
User repositories are available at URLs like these:
http
Wouter Verhelst writes:
> […] for future reference, this is ridiculously easy for anyone who's a
> Debian Developer or otherwise has an account on alioth:
>
> ssh to git.debian.org, and run:
>
> mkdir -p public_git/repo.git
> cd public_git/repo.git
> git init --bare
>
> log out again; then, in yo
Bernd Zeimetz writes:
> hi,
>
> just fyi:
>
> On 02/04/2017 02:14 PM, Stig Sandbeck Mathisen wrote:
>> I've noted the presence of gogs (https://gogs.io/)
>
> insteaf of gogs using https://github.com/go-gitea/gitea seem the
> better idea, it is a fork of gogs which is actually in development and
>
On Wed, Feb 08, 2017 at 01:36:13PM +0100, Wouter Verhelst wrote:
> On Thu, Jan 19, 2017 at 06:20:30PM +0100, Michael Stapelberg wrote:
> > Would a mirror of the git repository on alioth be sufficient? I had
> > planned to set that up, but didn’t get around to it yet. Any help with
> > that would be
hi,
just fyi:
On 02/04/2017 02:14 PM, Stig Sandbeck Mathisen wrote:
> I've noted the presence of gogs (https://gogs.io/)
insteaf of gogs using https://github.com/go-gitea/gitea seem the better
idea, it is a fork of gogs which is actually in development and has an
active upstream.
cheers,
bern
On Wed, 08 Feb 2017, Wouter Verhelst wrote:
> On Thu, Jan 19, 2017 at 06:20:30PM +0100, Michael Stapelberg wrote:
> > Would a mirror of the git repository on alioth be sufficient? I had
> > planned to set that up, but didn’t get around to it yet. Any help with
> > that would be very welcome.
>
>
On Thu, Jan 19, 2017 at 06:20:30PM +0100, Michael Stapelberg wrote:
> Would a mirror of the git repository on alioth be sufficient? I had
> planned to set that up, but didn’t get around to it yet. Any help with
> that would be very welcome.
I realize you've already done so, but for future referenc
On Sunday, February 05, 2017 10:05:13 AM Pirate Praveen wrote:
> On ഞായര് 05 ഫെബ്രുവരി 2017 04:07 രാവിലെ, Jonathan Dowland wrote:
> > I'm getting deja vu, this has all been discussed already on -devel in
> > recent months, please check the archives for further details, I'm fairly
> > sure people a
On ഞായര് 05 ഫെബ്രുവരി 2017 04:07 രാവിലെ, Jonathan Dowland wrote:
> I'm getting deja vu, this has all been discussed already on -devel in
> recent months, please check the archives for further details, I'm fairly
> sure people are already working on this (Pirate Praveen was at least).
Just for the
Hello Bernd,
On Sat, Feb 04, 2017 at 01:23:25PM +0100, Bernd Zeimetz wrote:
> On 01/30/2017 05:45 PM, Sean Whitton wrote:
> > I agree, they aren't as good. However, they're very nearly as good, and
> > it's too common to overstate how good GitHub's workflow is.
>
> Nearly as good? Where can I cl
Hello Wouter,
On Sat, Feb 04, 2017 at 08:20:25AM +0100, Wouter Verhelst wrote:
> On Mon, Jan 30, 2017 at 09:51:51AM -0700, Sean Whitton wrote:
> > Firstly, it is not clear to me how the barrier to getting involved with
> > more substantial bugs is affected by the fact that I can trivially
> > subm
On Sat, Feb 04, 2017 at 02:14:20PM +0100, Stig Sandbeck Mathisen wrote:
> I've noted the presence of gogs (https://gogs.io/) and pagure
> (https://pagure.io/pagure), which look to be completely free projects,
> but haven't tried any of them yet. https://rocketgit.com/op/doc/compare
> has a compari
❦ 4 février 2017 16:48 +0100, Alec Leamas :
>> A Github-like interface is totally compatible with the CLI: pull
>> requests are exposed as branches, you can merge, modify, do anything you
>> like. The web UI tries to catch up with what you do (if you merge
>> through the CLI, the web interface
On 04/02/17 15:58, Vincent Bernat wrote:
A Github-like interface is totally compatible with the CLI: pull
requests are exposed as branches, you can merge, modify, do anything you
like. The web UI tries to catch up with what you do (if you merge
through the CLI, the web interface will detect th
❦ 4 février 2017 14:07 +0100, Alec Leamas :
> And, this is not that simple.You do have a point in that the github
> interface is good for you and many others. OTOH, I actually prefer the
> commandline, and there are a few more on this list who also do. There
> just isn't a "good" UX, although t
Bernd Zeimetz writes:
> On 01/30/2017 05:45 PM, Sean Whitton wrote:
>> I agree, they aren't as good. However, they're very nearly as good,
>> and it's too common to overstate how good GitHub's workflow is.
>
> Nearly as good? Where can I click 'merge' in a web gui in Debian???
Just under the "
On 04/02/17 13:23, Bernd Zeimetz wrote:
On 01/30/2017 05:45 PM, Sean Whitton wrote:
I agree, they aren't as good. However, they're very nearly as good, and
it's too common to overstate how good GitHub's workflow is.
Nearly as good? Where can I click 'merge' in a web gui in Debian???
Pl
On 01/30/2017 05:45 PM, Sean Whitton wrote:
> I agree, they aren't as good. However, they're very nearly as good, and
> it's too common to overstate how good GitHub's workflow is.
Nearly as good? Where can I click 'merge' in a web gui in Debian???
--
Bernd Zeimetz
On Mon, Jan 30, 2017 at 09:51:51AM -0700, Sean Whitton wrote:
> Firstly, it is not clear to me how the barrier to getting involved with
> more substantial bugs is affected by the fact that I can trivially
> submit typo fixes. What did you have in mind?
How big was your first ever contribution to
On Wed, Jan 18, 2017 at 06:23:16PM +0100, Michael Stapelberg wrote:
> We’d love to hear your feedback and thoughts.
Thanks, really nice. This should motivate me to create manpages some
of my packages are missing. May https://manpages.debian.org/ rise
high in search engine rankings!
Riku
Hi Michael
Am 18.01.2017 um 18:23 schrieb Michael Stapelberg:
> https://manpages.debian.org has been modernized! We have just launched
Thanks a lot, this looks really nice.
One feature I'd like to see added is search as you type, like
tracker.d.o offers.
Regards,
Michael
--
Why is
On Mon, Jan 30, 2017 at 01:54:28PM +0100, Alec Leamas wrote:
> Easy enough for me. But Sean and Bernd has a point, the github workflow
> *is* easier. It's also used by so many that it's well established.
>
> That said, the very idea with debian is about free software; free as in Open
> Source. An
Hi,
Michael Stapelberg (2017-01-18):
> https://manpages.debian.org has been modernized! We have just launched
> a major update to our manpage repository. What used to be served via a
> CGI script is now a statically generated website, and therefore
> blazingly fast.
Many thanks, thi
Hello Bernd,
On Mon, Jan 30, 2017 at 04:10:38PM +0100, Bernd Zeimetz wrote:
> On 01/30/2017 02:14 PM, Holger Levsen wrote:
> > To be clear, I do believe in owning ones infrastructures, but I also see
> > how this encourages small contributions and makes them easy and I do see
> > this as a good th
Dear Alec,
On Mon, Jan 30, 2017 at 01:54:28PM +0100, Alec Leamas wrote:
> Easy enough for me. But Sean and Bernd has a point, the github workflow
> *is* easier.
Just to be clear, I wasn't one of those arguing that it's easier.
> But, we cannot just say "our tools are as good as github". Because
On 01/30/2017 02:14 PM, Holger Levsen wrote:
> On Mon, Jan 30, 2017 at 07:53:58AM -0500, The Wanderer wrote:
>> Are you saying that people are writing and submitting patches via a
>> Web-based editor interface, and that you're recommending that people
>> consider _accepting_ those patches, when t
On 01/30/2017 01:53 PM, The Wanderer wrote:
> Are you saying that people are writing and submitting patches via a
> Web-based editor interface,
yes, nothing wrong with that.
> and that you're recommending that people
> consider _accepting_ those patches, when they haven't even been
> _build-tes
On Mon, Jan 30, 2017 at 07:53:58AM -0500, The Wanderer wrote:
> Are you saying that people are writing and submitting patches via a
> Web-based editor interface, and that you're recommending that people
> consider _accepting_ those patches, when they haven't even been
> _build-tested_ before submis
On 30/01/17 13:59, Paul Wise wrote:
On Mon, Jan 30, 2017 at 8:54 PM, Alec Leamas wrote:
But, we cannot just say "our tools are as good as github".
Because they are not.
That is a very subjective statement. I for one really really dislike
github and much prefer other workflows.
Agreed, slo
On 30 January 2017 at 12:53, The Wanderer wrote:
> On 2017-01-30 at 07:38, Bernd Zeimetz wrote:
>
>> On 01/30/2017 01:32 PM, The Wanderer wrote:
>>
>>> If someone isn't cloning the repository locally, how is that
>>> someone creating the patch which is in the git repo which is
>>> requested to be
On Mon, Jan 30, 2017 at 8:54 PM, Alec Leamas wrote:
> But, we cannot just say "our tools are as good as github".
> Because they are not.
That is a very subjective statement. I for one really really dislike
github and much prefer other workflows.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On 30/01/17 13:32, The Wanderer wrote:
On 2017-01-30 at 03:54, Bernd Zeimetz wrote:
On 01/30/2017 12:44 AM, Sean Whitton wrote:
Same here. Also since I've moved my major packages to github, a
constant stream of pull requests for even simple bugs like typos
is coming in. People are used to
On 2017-01-30 at 07:38, Bernd Zeimetz wrote:
> On 01/30/2017 01:32 PM, The Wanderer wrote:
>
>> If someone isn't cloning the repository locally, how is that
>> someone creating the patch which is in the git repo which is
>> requested to be pulled?
>
> Choose a random file in a random repository
On 01/30/2017 01:32 PM, The Wanderer wrote:
> If someone isn't cloning the repository locally, how is that someone
> creating the patch which is in the git repo which is requested to be
> pulled?
Choose a random file in a random repository you are not allowed to
commit to. Click on the edit butt
On 2017-01-30 at 03:54, Bernd Zeimetz wrote:
> On 01/30/2017 12:44 AM, Sean Whitton wrote:
>>> Same here. Also since I've moved my major packages to github, a
>>> constant stream of pull requests for even simple bugs like typos
>>> is coming in. People are used to github and how to create a pull
On 01/30/2017 12:44 AM, Sean Whitton wrote:
>> Same here. Also since I've moved my major packages to github, a constant
>> stream of pull requests for even simple bugs like typos is coming in.
>> People are used to github and how to create a pull request on the web
>> interface, and I can just me
Hello,
On Fri, Jan 27, 2017 at 10:46:16PM +0100, Bernd Zeimetz wrote:
> On 01/19/2017 09:43 AM, Michael Stapelberg wrote:
> > I agree. However, I prioritize “free software needs people who work on
> > it”, and by using GitHub, contributions are made significantly easier
> > for a large number of p
On Thu, Jan 19, 2017 at 4:24 AM Michael Stapelberg
wrote:
> Furthermore, the design of the site has been updated and now includes
>
navigation panels that allow quick access to the manpage in other
> Debian versions, other binary packages, other sections and other
> languages. Speaking of languag
On 01/19/2017 09:43 AM, Michael Stapelberg wrote:
> I agree. However, I prioritize “free software needs people who work on
> it”, and by using GitHub, contributions are made significantly easier
> for a large number of people.
>
> In my personal experience, I can say that I would not be able to
writes ("Re: manpages.debian.org has been modernized!"):
>>> On Wed, Jan 18, 2017 at 11:37 PM, Ian Jackson
>>> > Also, I think the exact running version of Debian services should be
>>> > publicly available. And, unless this is made so easy that the service
>>&g
The fallback has a drawback: it downloads both assets,
regardless of support.
Could you please verify whether the -based fallback works for
you? See https://people.debian.org/~stapelberg/fallback/i3.1.en.html
for a demo.
On Mon, Jan 23, 2017 at 10:02 AM, Michael Stapelberg
wrote:
> I’m using SV
On Wed, 2017-01-25 at 09:09 +0100, Michael Stapelberg wrote:
> Could you please verify whether the -based fallback works for
> you? See https://people.debian.org/~stapelberg/fallback/i3.1.en.html
> for a demo.
The SVG is downloaded but there is no fallback on high security.
I wouldn't worry about
Makes sense to me.
On Tue, Jan 24, 2017 at 9:34 AM, Javier Fernandez-Sanguino
wrote:
> On 23 January 2017 at 22:22, Michael Stapelberg
> wrote:
>>
>> Thanks!
>>
>> I think we could put rewriterules in place to redirect hotlinks to the
>> cgi script to the correct place. I can take care of it if
On 23 January 2017 at 22:22, Michael Stapelberg
wrote:
> Thanks!
>
> I think we could put rewriterules in place to redirect hotlinks to the
> cgi script to the correct place. I can take care of it if you want me
> to.
Thanks Michael. I suggest we wait some time (a month?), go then through the
Thanks!
I think we could put rewriterules in place to redirect hotlinks to the
cgi script to the correct place. I can take care of it if you want me
to.
On Mon, Jan 23, 2017 at 10:19 PM, Javier Fernandez-Sanguino
wrote:
>
> On 20 January 2017 at 10:25, Javier Fernandez-Sanguino
> wrote:
>>
>>
>
On 20 January 2017 at 10:25, Javier Fernandez-Sanguino
wrote:
>
>
> This weekend I will modify the CGI so that it redirects to the new
> (static) content for users that at some point still go to the old one. It
> seems that the redirects get cached in the browser permanently because I
> (wrongly)
I’m using SVG because it scales to whichever DPI your monitor might
have. I’ll have a look at switching to later, thanks.
On Mon, Jan 23, 2017 at 10:00 AM, Paul Wise wrote:
> On Mon, 2017-01-23 at 08:47 +0100, Michael Stapelberg wrote:
>
>> Could you clarify how I can implement a fallback in a w
On Mon, 2017-01-23 at 08:47 +0100, Michael Stapelberg wrote:
> Could you clarify how I can implement a fallback in a way that works
> for Tor Browser please?
The solution here appears to work:
https://css-tricks.com/a-complete-guide-to-svg-fallbacks/#fallback-object
In this case, the page cons
On 23 January 2017 at 08:49, Paul Wise wrote:
> On Mon, 2017-01-23 at 08:45 +0100, Michael Stapelberg wrote:
>
> > What would be the best way to trigger on mirror pushes?
>
> I'm not sure about that, please ask #debian-mirrors
> or failing that #debian-admin, and or the lists.
Basicly, you give
On Thu, Jan 19, 2017 at 11:52 AM, Paul Wise wrote:
> On Thu, 2017-01-19 at 09:35 +0100, Michael Stapelberg wrote:
>
>> To: Paul Wise
>
> I'm subscribed :)
>
>> No. Isn’t that a violation of the FHS (see
>> http://www.pathname.com/fhs/pub/fhs-2.3.html#USRSHAREARCHITECTUREINDEPENDENTDATA)
>> and
On Thu, Jan 19, 2017 at 4:41 AM, Paul Wise wrote:
> On Thu, Jan 19, 2017 at 1:23 AM, Michael Stapelberg wrote:
>
>> https://manpages.debian.org has been modernized! We have just launched
>> a major update to our manpage repository. What used to be served via a
>> CGI sc
On Mon, 2017-01-23 at 08:45 +0100, Michael Stapelberg wrote:
> What would be the best way to trigger on mirror pushes?
I'm not sure about that, please ask #debian-mirrors
or failing that #debian-admin, and or the lists.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description:
On 20 January 2017 at 06:01, Kushal Kumaran wrote:
> Ian Jackson writes:
>
> > Michael Stapelberg writes ("Re: manpages.debian.org has been
> modernized!"):
> >> On Thu, Jan 19, 2017 at 4:43 PM, Ian Jackson
> >> wrote:
> >> > mariner:~&g
Ian Jackson writes:
> Michael Stapelberg writes ("Re: manpages.debian.org has been modernized!"):
>> On Thu, Jan 19, 2017 at 4:43 PM, Ian Jackson
>> wrote:
>> > mariner:~> curl -s
>> > 'https://manpages.debian.org/cgi-bin/man.cgi?query=make
Ian Jackson writes:
> For a debian.org service, I would like to be able to check out the
> running version without interacting with a proprietary online service.
I have been looking at the GitLab instance hosted at FOSS Community
India's servers, https://git.fosscommunity.in/>. It's been working
Ian Jackson schrieb am Donnerstag, dem 19. Jänner 2017:
> Michael Stapelberg writes ("Re: manpages.debian.org has been modernized!"):
> > On Thu, Jan 19, 2017 at 4:46 PM, Ian Jackson
> > > AFAICT this program is not packaged for Debian.
> >
> > The p
Michael Stapelberg writes ("Re: manpages.debian.org has been modernized!"):
> On Thu, Jan 19, 2017 at 4:46 PM, Ian Jackson
> > AFAICT this program is not packaged for Debian.
>
> The program is packaged for Debian:
> https://packages.debian.org/stretch/mandoc. I have
Michael Stapelberg writes ("Re: manpages.debian.org has been modernized!"):
> On Thu, Jan 19, 2017 at 4:43 PM, Ian Jackson
> wrote:
> > mariner:~> curl -s
> > 'https://manpages.debian.org/cgi-bin/man.cgi?query=make&apropos=0&sektion=0&manpath=De
On Thu, Jan 19, 2017 at 4:46 PM, Ian Jackson
wrote:
> Michael Stapelberg writes ("Re: manpages.debian.org has been modernized!"):
>> On Thu, Jan 19, 2017 at 4:41 AM, Paul Wise wrote:
>> > The manual page converter seems to use line breaks rather than proper
>>
On Thu, Jan 19, 2017 at 4:43 PM, Ian Jackson
wrote:
> Michael Stapelberg writes ("Re: manpages.debian.org has been modernized!"):
>> On Wed, Jan 18, 2017 at 11:37 PM, Ian Jackson
>> > Also, I think the exact running version of Debian services should be
>> >
Michael Stapelberg writes ("Re: manpages.debian.org has been modernized!"):
> On Thu, Jan 19, 2017 at 4:41 AM, Paul Wise wrote:
> > The manual page converter seems to use line breaks rather than proper
> > paragraph tags.
>
> Could you report this issue upstream
Michael Stapelberg writes ("Re: manpages.debian.org has been modernized!"):
> On Wed, Jan 18, 2017 at 11:37 PM, Ian Jackson
> > Also, I think the exact running version of Debian services should be
> > publicly available. And, unless this is made so easy that the service
On Thu, 2017-01-19 at 09:35 +0100, Michael Stapelberg wrote:
> To: Paul Wise
I'm subscribed :)
> No. Isn’t that a violation of the FHS (see
> http://www.pathname.com/fhs/pub/fhs-2.3.html#USRSHAREARCHITECTUREINDEPENDENTDATA)
> and Debian policy?
I suppose. I don't think we test for it though?
Thanks, this is great!
signature.asc
Description: Digital signature
On Thu, Jan 19, 2017 at 4:41 AM, Paul Wise wrote:
> On Thu, Jan 19, 2017 at 1:23 AM, Michael Stapelberg wrote:
>
>> https://manpages.debian.org has been modernized! We have just launched
>> a major update to our manpage repository. What used to be served via a
>> CGI sc
On Wed, Jan 18, 2017 at 11:37 PM, Ian Jackson
wrote:
> Michael Stapelberg writes ("manpages.debian.org has been modernized!"):
>> https://manpages.debian.org has been modernized!
>
> Awesome! Thanks to everyone.
>
>> https://github.com/Debian/debiman. In case yo
On Thu, Jan 19, 2017 at 1:05 AM, Henrique de Moraes Holschuh
wrote:
> On Wed, 18 Jan 2017, Michael Stapelberg wrote:
>> https://manpages.debian.org has been modernized! We have just launched
>> a major update to our manpage repository. What used to be served via a
>>
On Thu, Jan 19, 2017 at 6:37 AM, Ian Jackson wrote:
> As you might expect, I'm uncomfortable about the use of the
> proprietary github service for this. I realise that we don't
> necessarily have entirely comparable alternatives, but Free Software
> needs free tools.[1]
Agreed for both bugs and
On Thu, Jan 19, 2017 at 1:23 AM, Michael Stapelberg wrote:
> https://manpages.debian.org has been modernized! We have just launched
> a major update to our manpage repository. What used to be served via a
> CGI script is now a statically generated website, and therefore
> blazingly fa
On Wed, 18 Jan 2017, Michael Stapelberg wrote:
> https://manpages.debian.org has been modernized! We have just launched
> a major update to our manpage repository. What used to be served via a
> CGI script is now a statically generated website, and therefore
> blazingly fast.
Oooh,
Michael Stapelberg writes ("manpages.debian.org has been modernized!"):
> https://manpages.debian.org has been modernized!
Awesome! Thanks to everyone.
> https://github.com/Debian/debiman. In case you would like to use it to
> run a similar manpage repository (or convert yo
Philipp Kern writes ("Re: manpages.debian.org has been modernized!"):
> Most services don't do that. Which is also related to the fact that they
> wouldn't run the code from stable but the machines need to run stable to
> be supportable by our awesome sysadmins.
On 2017-01-18 19:34, Marcin Kulisz wrote:
I'm not volunteering to do the above but I think that services running
in d.o
domain should be available from Debian main.
Most services don't do that. Which is also related to the fact that they
wouldn't run the code from stable but the machines need
On 2017-01-18 18:23:16, Michael Stapelberg wrote:
> https://manpages.debian.org has been modernized! We have just launched
> a major update to our manpage repository. What used to be served via a
> CGI script is now a statically generated website, and therefore
> blazingly fast.
Than
https://manpages.debian.org has been modernized! We have just launched
a major update to our manpage repository. What used to be served via a
CGI script is now a statically generated website, and therefore
blazingly fast.
While we were at it, we have restructured the paths so that we can
serve
75 matches
Mail list logo
