Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: libanyevent-i3-perl
Version : 0.04
Upstream Author : Michael Stapelberg
* URL : http://search.cpan.org/dist/AnyEvent-I3/
* License : Artistic or GPL-1+
Programming Lang: Perl
Hi Mark,
* [16.05.09 17:00]:
> I've been looking for a solution to the problem of duplicating my user
> environment across different machines. My search has included anything
> I could find between the extremes of "manual copying" to "cfengine",
> but until now I've not been lucky in finding anyth
Hi Mark,
* [17.05.09 01:35]:
> My goal or use case is not entirely limited to "duplicating _my_ user
> environment across different machines" as I wrote above. I am actualy
> seeking the ability to package up the environment of any user on any
> machine. What that gives me is a quick path to produ
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: libtomcrypt
Version : 1.17
Upstream Author : Tom St Denis
* URL : http://www.libtomcrypt.com/
* License : Public Domain
Programming Lang: C
Description : public domain open
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: libnet-inet6glue-perl
Version : 0.3-1
Upstream Author : Steffen Ullrich
* URL : http://search.cpan.org/dist/Net-INET6Glue/
* License : Perl
Programming Lang: Perl
Description
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: libiniparser
Version : 3.1
Upstream Author : Nicolas Devillard
* URL : http://ndevilla.free.fr/iniparser/
* License : MIT/X11
Programming Lang: C
Description : stand-alone ini
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: dunst
Version : 0.1+git20120621
Upstream Author : Sascha Kruse
* URL : http://knopwob.github.com/dunst/
* License : BSD
Programming Lang: C
Description : minimalistic
Package: wnpp
Owner: Michael Stapelberg
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org
* Package name: libplack-middleware-csrfblock-perl
Version : 0.03
Upstream Author : Rintaro Ishizaki
* URL : http://search.cpan.org
Hi Vincent,
Quoting Vincent Lefevre (2012-07-22 15:53:13)
> I don't think there's anything wrong with enhancing the way that
> sysvinit works, as long as the user can still use the update-rc.d
> method.
There is: update-rc.d is a defined interface which works with sysvinit
and other init systems (
Hello,
In the past, we have had multiple heated discussions involving
systemd. We (the pkg-systemd-maintainers team) would like to better
understand why some people dislike systemd.
Therefore, we have created a survey, which you can find at
http://survey.zekjur.net/index.php/391182
Please only s
Hi Lucas,
Lucas Nussbaum writes:
> I think that one reason why we risk having another init systems
> discussion is that there hasn't been (TTBOMK) a good effort to summarize
> the various point raised and your answers (as systemd maintainers) to
> them. Such a "systemd demystification" effort wou
Hi,
Thanks for participating, everyone!
find the results at:
http://people.debian.org/~stapelberg/2013/05/27/systemd-survey-results.html
Another discussion is really not necessary at this point. Quote from the
page:
I know this is a controversial topic. Please don’t start yet another
sy
Hi Ondřej,
Ondřej Surý writes:
> Practical question: if I were to support systemd .service, upstart
> init job and/or OpenRC together with standard sysvinit
> script, how do I check for currently used init system from sysvinit
> script to not start the service for a second time?
>
> Is there som
Hi,
since some people might not read planet debian, here is a link to my
first blog post in a series of posts dealing with the results of the
Debian systemd survey:
http://people.debian.org/~stapelberg/2013/06/09/systemd-bloat.html
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to debian-
Hi Bjørn,
Thanks for your well-put mail. As far as I understand it, your concern
is that libraries might exit() (either due to actually calling exit() or
due to having a bug) and therefore take pid 1 with them.
I am sure that the systemd developers are very aware of this fact. They
even published
Hi Thomas,
Thomas Goirand writes:
> In this blog post, you tell that it's possible not to use all the
> components of systemd. Then, the immediate question that pops to my
> mind: what are *your* intentions then, in Debian (or, said in another
> way, what would you like to do if you where the onl
Hi Ondřej,
Ondřej Surý writes:
> and if I match this with the table at:
> http://people.debian.org/~stapelberg/docs/systemd-dependencies.html I get
> the result that you will _not_ compile systemd with:
>
> libselinux.so
> libpam.so
> libwrap.so
> libaudit.so
> libkmod.so
>
> because they are mar
Hi Ondřej,
Ondřej Surý writes:
> I still think you should also update the table with information if the
> library is actually used in PID 1 (or in forked process) as hmh suggested:
>
>> It would be best to enhance
>> http://people.debian.org/~stapelberg/docs/systemd-dependencies.html with
>> info
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: codesearch
Version : 0.0~hg20120502
Upstream Author : Russ Cox
* URL : http://code.google.com/p/codesearch
* License : BSD
Programming Lang: Go
Description : Indexed regular
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-pq-dev
Version : 0.0~git20130606-1
Upstream Author : Blake Mizerany
* URL : https://github.com/lib/pq
* License : Expat
Programming Lang: Go
Description : pure Go
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-godebiancontrol-dev
Version : 0.0~git20121130-1
Upstream Author : Michael Stapelberg
* URL : https://github.com/mstap/godebiancontrol
* License : BSD
Programming Lang: Go
Hi,
since some people might not read planet debian, here is a link to my
second blog post in a series of posts dealing with the results of the
Debian systemd survey:
http://people.debian.org/~stapelberg/2013/07/01/systemd-transition.html
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to d
Hi Vincent,
Vincent Danjean writes:
> Thank you for this article. Reading it make me think about something
> I would like to know: if I install systemd and boot with it (using grub
> parameter) as described in the article, what occurs when I type
> /etc/init.d/apache2 start
Fair question.
When y
Hi Arief,
Arief M Utama writes:
> Ever since after Wheezy released, with gnome-3 and systemd, I still can't
> suspend my laptop by closing the lid like it used to be.
Note that wheezy does not use systemd by default. Are you 100% sure you
are using systemd? Check “ps auxf” to see if systemd is yo
Hi,
since some people might not read planet debian, here is a link to my
third blog post in a series of posts dealing with the results of the
Debian systemd survey:
http://people.debian.org/~stapelberg/2013/07/13/systemd-not-portable.html
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to
Hi,
I am sorry for starting yet another thread on systemd, but we feel this
particular post is important and should spread as widely as possible
(i.e. beyond just readers of planet debian):
http://people.debian.org/~stapelberg/2013/07/14/systemd-how-to-help.html
tl;dr: whatever you end up doing,
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: xcb-util-cursor
Version : 0.0.99
Upstream Author : Michael Stapelberg
* URL : http://xcb.freedesktop.org/
* License : MIT/X
Programming Lang: C
Description : utility libraries
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: dh-golang
Version : 1.0
Upstream Author : Michael Stapelberg
* License : BSD
Programming Lang: Perl
Description : debhelper add-on for packaging software written in Go
(golang)
dh-golang
Hi Asheesh,
I just watched your talk on my way home from DebConf and decided I want
to join you in the welcoming team or whatever it will be called :).
A few more details on what will be happening and what is the expectation
of me (and others) would be appreciated.
--
Best regards,
Michael
--
Hi Steven,
Steven Chamberlain writes:
> Wouldn't ZFS be a more natural way to do something like this?
Possibly, but I have zero hopes of getting it set up and supported by
DSA, so we can’t use it for this service.
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists
Hi Luca,
Luca Filipozzi writes:
> Why do you say that when you haven't even asked?
Because I thought the answer was going to be “not in the Linux kernel,
no chance”.
> To address this specific thread, the challenge with ZFS is not that we don't
> like the idea (I'm keen on it, actually) but that
Package: wnpp
Owner: Michael Stapelberg
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org
* Package name: libprivileges-drop-perl
Version : 1.03
Upstream Author : Troels Liebe Bentsen
* URL : http://search.cpan.org/dist
Package: wnpp
Owner: Michael Stapelberg
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: all-knowing-dns
Version : 1.0
Upstream Author : Michael Stapelberg, C<< >>
* URL : http://search.cpan.org/dist/AllKnowingDN
Hi Svante,
Excerpts from Svante Signell's message of 2012-04-01 20:56:40 +0200:
> Adding to the problems with NM, it is not even possible to edit or add a
> connection: Failed to add new connection: (32) Insufficient privileges.
>
> Looks like you have to start the graphical environment with: Con
Hi,
I hereby announce a new Debian project: Debian Code Search.
Debian Code Search is a search engine for program source code within
Debian.
It allows you to search all ≈ 17000 source packages,
containing 130 GiB of FLOSS source code (including Debian
packaging) with regular expressions.
You ca
Hi alberto,
alberto fuentes writes:
> roughly speaking, how does it work internally?
It uses a trigram index and the RE2 regular expression engine.
My work is based on Russ Cox’s ideas and code published at
http://swtch.com/~rsc/regexp/regexp4.html
In case you are interested, I’m happy to send
Hi Neil,
Neil Williams writes:
> It's pleasingly quick, which is always good. Might need to be able to
> exclude the debian/ directory from searches.
File regular expressions and a minus operator is already on the TODO
list :-).
> First thing which occurs to me is that I'd prefer a summary page
Hi Joachim,
Joachim Breitner writes:
> Since you have all code extracted anyways, could you extend the page to
> allow for easy code browsing? Might be faster than "apt-get source;
> less ..." sometimes.
Very basic code browsing is on my agenda, but zack@ mentioned he wants
to build a new sources
Hi Chris,
Chris Bannister writes:
> See:
> http://grammar.about.com/od/words/a/amount.htm
> http://grammarist.com/usage/amount-number/
Thanks. I have heard about this rule but must have forgotten it.
I changed the text and will push an update soon.
--
Best regards,
Michael
--
To UNSUBSCRIBE
Hi Neil,
Neil Williams writes:
> That's just swamped by licences, as would be received and lots of other
> common words (which are, rightly or wrongly, used as variable names or
> as part of function names).
Well, of course searching for common words will result in a lot of
results. Asking the ot
Hi Neil,
Neil Williams writes:
> Just because a file doesn't end in .pl, doesn't mean it isn't perl -
> Policy mandates that perl in /usr/bin does not end in .pl Is this only
> finding perl modules and perl scripts in /usr/share?
As the FAQ¹ states, this is filtering by file extension. I will kee
Hi,
I am co-maintainer of the golang package and spent a few hours on trying
to figure out how to best create Debian packages for libraries and
programs which are implemented in Go.
I have documented my thoughts, conclusions and example packaging on:
http://wiki.debian.org/MichaelStapelberg/GoPac
Hi Paul,
> Since golang apparently doesn't support dynamic linking, every package
> built against a golang library will have to include an appropriate
> Built-Using header. You will probably also want a lintian test for
> this to autoreject anything without this header.
Thanks, I was not aware of
Hi Dmitrijs,
Dmitrijs Ledkovs writes:
> What about multiarch?
I tried to address this on the wiki page, see
http://wiki.debian.org/MichaelStapelberg/GoPackaging#Multi-Arch.2Fcross-compiling
Essentially, I currently believe that multi-arch does not make sense for
go, since we are only dealing wit
Hi Simon,
Simon McVittie writes:
> Where does gccgo look for Go sources (src)?
> Where does gccgo look for Go "static libraries" (pkg)?
> Where does gccgo look for Go dynamic libraries? (Presumably the same
> places where gcc looks for C dynamic libraries?)
I can’t really answer these questions i
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: wit
Version : 2.10a
Upstream Author : Dirk Clemens
* URL : http://wit.wiimm.de/
* License : GPL-2+
Programming Lang: C
Description : manipulate Wii and GameCube ISO images and
Hi Bernhard,
"Bernhard R. Link" writes:
> Please also consider "codesearch-golang". Especially with longer package
> names not everything can show the full name so the beginning should be
> the more important information.
Given that we already have python-* and ruby-*, I’d find golang-* more
cons
Hi Shawn,
Shawn writes:
> Henceforth when a go program depends on a go library, those go
> libraries are ALWAYS compiled in statically. Static linking causes
> many problems for distributions like Debian, and therefore this
Can you please tell us which specific problems are caused by static
linki
Hi Bernhard,
"Bernhard R. Link" writes:
>> >> (and of course just “codesearch” for the binaries).
>> >
>> > I assume s/binaries/sources/? And I'd suggest to just not policy the
>> No, I really meant binaries, as in “cgrep”, “cindex” and “csearch” in
>> this specific case.
>
> And what is the name
Hi Guillem,
Thanks for your explanations, most points make sense to me. Two
questions remain:
Guillem Jover writes:
> - Private dependencies, as they leak to rdeps. When a library uses
> another library privately this dependency gets linked in directly
> in all other rdeps, when
Hi Matthias,
Matthias Klose writes:
> Calling gc the "official" compiler seems to be misleading. gccgo in
That’s why I called it “official”, not official.
> wheezy supports the Go API 1.0, and the standard library 1.0.3,
> supports dynamic linking, supports multiarch, makes the distinction
> for
Hi Shawn,
shawnland...@gmail.com writes:
> I am not sure how or if lld works on .a files, but I am pretty sure
> that this binary is linked against libc6 and libgo1. If I invoke gccgo
> directly that is the result.
If by “this binary” you mean godebiancontrol.a, then no:
ldd /tmp/golang/pkg/linux
Hi Shawn,
shawnland...@gmail.com writes:
> [...]
> use of these .a files. You have to look at the resulting binaries.
But in this discussion we are talking about building _library_ packages,
not binaries. I would like to focus on the question of how to build a Go
package (such as github.com/mstap/
Hi Reinhard,
Reinhard Tartler writes:
> Consider this from the application perspective: Say an application
> links against a library libfoo.a. At some point, libfoo decides to
> include compression support, and requires functionality from libz. No
> problem for the library package maintainer; he
Hi Florian,
Florian Weimer writes:
> My main worry is that, for example, a fix in another, otherwise
> unrelated dependency prompts a rebuild, and this picks up behavioral
> changes which haven't been visible before, but lingering in the static
> library. Essentially, we end up with non-reproduc
Hi Florian,
Florian Weimer writes:
>> Could you provide an example please? I don’t understand how this is
>> different with static linking than with dynamic linking yet.
>
> With dynamic linking, you pick up the behavior change along with
> "apt-get upgrade", so I expect that we get much more tes
Hi,
I have been in contact with a few Go people and we have worked out the
following:
Go libraries (not binaries!) should be present in Debian _only_ for the
purpose of building Debian binary packages. They should not be used
directly for Go development¹.
Go library Debian packages such as golan
Hi Hilko,
Hilko Bengen writes:
> This is a pity for those of us who don't really subscribe to "get
> everything from github as needed" model of distributing software.
Yes, but at the same time, it makes Go much more consistent across
multiple platforms. We should tackle one issue at a time. I sup
Hi Wouter,
Wouter Verhelst writes:
> "consistency across multiple platforms" has been claimed as a benefit
> for allowing "gem update --system" to replace half of the ruby binary
> package, amongst other things. It wasn't a good argument then, and it
> isn't a good argument now.
I am not familiar
Hi Chow,
Chow Loong Jin writes:
> 1. If software that depends on native packages is installed using "go get"
> or whatever other language-specific package manager, e.g. pip for Python
> or
> gem for Ruby is installed, there is no way to declare a dependency on
> those. For example,
Hi Hilko,
Hilko Bengen writes:
> I drew a different conclusion from Ian's messages the thread you
> mentioned (see the quotes below). Apparently, one *can* build shared
> libraries using gccgo, but they are not currently usable using dlopen().
> My impression was that this means that regular use
Hi Jack,
Jack Andrews writes:
> i really like the readline in bash - it seems bash is "vi complete" in
> vi mode.
Unfortunately it’s not vim-complete (not sure about “pure” vi), take for
example this command line:
foo "bar" baz
Then, press Escape, 0, w, w, c, i, " — nothing happens, but in
Hi Matthias,
Matthias Klose writes:
> Am 31.01.2013 13:02, schrieb Hilko Bengen:
>> 2. -fno-split-stack
>>Otherwise I could not link executables and got the following error
>>message:
>>/usr/bin/ld.bfd.real: cindex: hidden symbol `__morestack' in
>>/usr/lib/gcc/x86_64-linux-gnu/4
Hi Hilko,
Hilko Bengen writes:
> /usr/local. This is not what "sudo go get" currently (version 1:1.0.2-2)
> does -- it happily puts both source and binary files into GOROOT
> (=/usr/lib/go). This is bound to break things in interesting ways at
> some point.
Indeed. This is when having an empty GO
Hi Hilko,
Hilko Bengen writes:
> Sure. See the Makefile at the end of this mail. Please note that I
> [...]
Thanks for the instructions. I reproduced them and got shared libraries
plus dynamically linked binaries.
Aside from details about the split stack flags, now one big question
arises:
Assu
Hi Andreas,
I wholeheartedly agree. I have written about this in 2012-11¹, but in my
article, I complained about the way bugreports are handled, which, IMO,
are much too free-form to be useful for RC bug hunters.
Anyway, I definitely share your experience that many RC bugs are
hardware-specific o
Hi Tollef,
Tollef Fog Heen writes:
> Buildbot is pretty crap at managing slaves that disappear and come back
> and such.
This works fine for me, I have never had any trouble with that (and yes,
my build slaves have disconnected/reconnected quite a few times). Using
buildbot since more than a year
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: kanla
Version : 1.1
Upstream Author : Michael Stapelberg
* URL : http://kanla.zekjur.net/
* License : BSD
Programming Lang: Perl
Description : small-scale alerting daemon
Hi Arno,
Arno Töll writes:
> ... which "assign[s] random color shit
> to [your] name" [1]. You've got the choice to use an avatar, or someone
> assigns one to you.
FYI, this is not a technical necessity. If called correctly, gravatar
(so probably libravatar, too) can return a specific image, e.g.
Hi Nikolaus,
Nikolaus Rath writes:
> But why not make it a proper package in the first place if the source is
> GPL?
bdrung@ explained this in the ITP bug already:
> I tried, but failed miserable. Some libraries needs to be packaged and
> the upstream build system needs to be bent to build on De
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-go.tools
Version : 0.0~hg20131126-1
Upstream Author : The Go Authors
* URL : https://code.google.com/p/go.tools/
* License : BSD-3-clause
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: simple-tpm-pk11
Version : 0.0~git20140216-1
Upstream Author : Thomas Habets
* URL : https://github.com/ThomasHabets/simple-tpm-pk11
* License : apache2
Programming Lang: C
Hi Thomas,
Thomas Weber writes:
> And for those packages where it does not matter, it will cost extra
> developer concentration/time in ignoring the noise. Sorry, but this
> feels like being good for some, bad for all others. Developers
> interested in the information should add bug scripts now a
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-sorcix-irc-dev
Version : 1.1.0
Upstream Author : Vic Demuzere
* URL : https://github.com/sorcix/irc
* License : Expat
Programming Lang: Go
Description : generic support
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: robustirc-bridge
Version : 1.1
Upstream Author : The RobustIRC authors
* URL : http://robustirc.net/
* License : BSD-3-clause
Programming Lang: Go
Description : bridges
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: irssi-plugin-robustirc
Version : 0.1
Upstream Author : Michael Stapelberg
* URL : https://github.com/robustirc/irssi-robustirc
* License : GPL-2+
Programming Lang: C
Description
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-github-jacobsa-oglematchers
Version : 0.0~git20150320
Upstream Author : Aaron Jacobs
* URL : https://github.com/jacobsa/oglematchers
* License : Apache-2.0
Programming Lang
On Sun, Jul 19, 2015 at 11:28 PM, Ian Jackson <
ijack...@chiark.greenend.org.uk> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I am pleased to announce dgit 1.0, which can be used, as applicable,
> by all contributors and downstreams.
>
> dgit allows you to treat the Debian archiv
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: linux-firmware-raspi3
Version : 1.20161123
Upstream Author : Raspberry Pi Foundation
* URL : https://github.com/raspberrypi/firmware
* License : Proprietary
Description
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 all
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 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 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 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
>> >
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 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#USRSH
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
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 f
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:
>>
>>
>
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 cor
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 us
source of the debian-specific assets we use.
This should give you everything you need to reproduce byte-for-byte
identical output.
On Thu, Jan 19, 2017 at 6:20 PM, Michael Stapelberg
wrote:
> On Thu, Jan 19, 2017 at 4:43 PM, Ian Jackson
> wrote:
>> Michael Stapelberg
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-go4
Version : 0.0~git20180103.fba789b-1
Upstream Author : go4 authors
* URL : https://github.com/camlistore/go4
* License : Apache-2.0
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-gopkg-warnings.v0
Version : 0.1.2-1
Upstream Author : Péter Surányi
* URL : https://github.com/go-warnings/warnings
* License : BSD-2-clause
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-pault-go-blobstore
Version : 0.0~git20180314.d6d187c-1
Upstream Author : Paul Tagliamonte
* URL : https://github.com/paultag/go-blobstore
* License : Expat
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-pault-go-archive
Version : 0.0~git20180223.29fe7b6-1
Upstream Author : Paul Tagliamonte
* URL : https://github.com/paultag/go-archive
* License : Expat
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: debiman
Version : 0.0~git20180224.8582b7f-1
Upstream Author : Michael Stapelberg
* URL : https://github.com/Debian/debiman
* License : Apache-2.0
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-github-golang-geo
Version : 0.0~git20170112.0.f819552-1
Upstream Author : Google Inc.
* URL : https://github.com/golang/geo
* License : Apache-2.0
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: golang-golang-x-debug
Version : 0.0~git20160621.0.fb50892-1
Upstream Author : The Go Authors
* URL : https://golang.org/x/debug
* License : BSD-3-clause
Programming Lang: Go
Hey,
pabs, what’s the current status on this? AFAICT, you mentioned you
wanted to come up with a spec on the RepositoryFormat wiki page. I don’t
see that on the RepositoryFormat wiki page yet.
Is there any way to help?
I’m also interested in this issue due to hardcoding in manpages.d.o,
which I’
1 - 100 of 112 matches
Mail list logo
