Package: wnpp
Severity: wishlist
Owner: "Stéphane Glondu"
* Package name: ocaml-ipaddr
Version : 1.0.0
Upstream Author : David Sheets, Anil Madhavapeddy, Hugo Heuzard
* URL : https://github.com/mirage/ocaml-ipaddr
* License : ISC
Programming Lang: OCaml
Des
On Wed, Jun 18, 2014 at 02:08:59PM +0200, Jakub Wilk wrote:
> Somewhere in another universe, someone proposed moving Developer's
> Reference to the wiki. One of the arguments was that it would let
> you make changes _quickly_. I'm shamelessly :-P disclosing a message
> in this thread:
Since the en
On Thu, Jun 19, 2014 at 4:46 AM, Thorsten Glaser wrote:
> It’s a bit more than a table. Also, the process involves some
> unfree-for-a-BSD (GNU GPL) code that does part of the transformation.
> For jupp, I have to do other parts by hand, including review…
Could you explain in more detail?
Perhap
On Thu, Jun 19, 2014 at 1:27 AM, Jay Berkenbilt wrote:
> I'd have to study it a little more, but I'm not sure this actually makes
> sense for a package like ICU whose sole purpose in life is handling
> Unicode.
Could you explain in more detail, I'm not following your thought process here?
How do
Henrique de Moraes Holschuh dixit:
>Make it generic, instead. You could just automatize the table update
>through a script, and allow it to either fetch the data over the network
>using curl/wget/whatever (default), or to get the data from a local file.
It’s a bit more than a table. Also, the pr
Package: wnpp
Severity: wishlist
Owner: nodiscc
* Package name: bleufear-gtk-theme
Version : 1.0
Upstream Author : Max Fierke
* URL : https://github.com/maxfierke/BleuFear
* License : GPL
Programming Lang: Other
Description : A dark theme with a wild s
Processing commands for cont...@bugs.debian.org:
> reassign 752008 src:gnome
Bug #752008 [general] Subject: general: Unable to set my status as "Available"
in GNOME 3
Bug reassigned from package 'general' to 'src:gnome'.
Warning: Unknown package 'src:gnome'
Warning: Unknown package 'src:gnome'
I
Subject: general: Unable to set my status as "Available" in GNOME 3
Package: general
Severity: normal
Dear Maintainer,
Please find answers to your questions which may be helpful to track the issue.
* What led up to the situation?
I tried to change my status to "Available" by clickin
On Wed, Jun 18, 2014 at 10:27:23AM -0700, Russ Allbery wrote:
> Luca Filipozzi writes:
> > On Wed, Jun 18, 2014 at 10:05:32AM -0700, Russ Allbery wrote:
>
> >> This is only true if the root CA is maintained with the same level of
> >> security as the PGP signing key for the archive. While that's
Luca Filipozzi writes:
> On Wed, Jun 18, 2014 at 10:05:32AM -0700, Russ Allbery wrote:
>> This is only true if the root CA is maintained with the same level of
>> security as the PGP signing key for the archive. While that's
>> something that we could probably do (although it's worth not
>> unde
Paul Wise wrote:
> Hi all,
>
> Unicode 7.0 was recently released. I discovered some source packages
> contain outdated copies of various Unicode data files. At minimum, the
> following packages embed part of the Unicode data (UnicodeData.txt).
>
> . . .
>
> Please ask your upstreams to remove th
On Wed, Jun 18, 2014 at 10:05:32AM -0700, Russ Allbery wrote:
> Vincent Lefevre writes:
> > On 2014-06-17 13:20:59 +0100, Simon McVittie wrote:
>
> >> It should be possible to make a CA certificate that is only considered to
> >> be valid for the spi-inc.org and debian.org subtrees, and then trus
On Wed, 2014-06-18 at 20:29:59 +0800, Paul Wise wrote:
> If your package converts the Unicode data to another format at build
> time you should add a Built-Using header to the relevant binary
> packages. The fntsample package is an example of how to do this.
>
> https://www.debian.org/doc/debian-p
Vincent Lefevre writes:
> On 2014-06-17 13:20:59 +0100, Simon McVittie wrote:
>> It should be possible to make a CA certificate that is only considered
>> to be valid for the spi-inc.org and debian.org subtrees, and then trust
>> the assertion that SPI control that certificate - but in widely-use
On Wed, Jun 18, 2014 at 11:33 PM, Alastair McKinstry wrote:
> I updated unicode-data already to 7.0, so the data is present and
> packaged in Debian
> so there is no need to fetch via curl, etc.
> Build-Dep on unicode-data and then updates should simply be a binNMU ?
That is fine for Debian but u
I updated unicode-data already to 7.0, so the data is present and
packaged in Debian
so there is no need to fetch via curl, etc.
Build-Dep on unicode-data and then updates should simply be a binNMU ?
regards
Alastair
On 18/06/2014 14:40, Paul Wise wrote:
> On Wed, Jun 18, 2014 at 9:22 PM, Henrique
Hello!
It came up that people should move away from the transitional package
iproute, and instead use iproute2
I guess it's time to remind everyone again that I intend to drop
iproute transitional package post-jessie release.
It would thus be very good if there are no reverse dependencies
le
On Wed, Jun 18, 2014 at 04:10:19PM +0200, Vincent Lefevre wrote:
> But I wonder whether it is a good idea to promote only non-secure URL's
> to the source (at least if there are no associated signtures), as some
> packages do. One may also wonder whether the package maintainer has
> used such a URL
The Debian Policy Manual on
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
says:
12.5 Copyright information
[...]
In addition, the copyright file must say where the upstream sources
(if any) were obtained, and should name the original authors.
But I wonder whe
On Wed, Jun 18, 2014 at 9:22 PM, Henrique de Moraes Holschuh wrote:
> Make it generic, instead. You could just automatize the table update
> through a script, and allow it to either fetch the data over the network
> using curl/wget/whatever (default), or to get the data from a local file.
That w
On 2014-06-18 14:20:10 +1000, Russell Stuart wrote:
> So you need X.509 PKI (even with all its flaws) during that first
> contact. But after you've sent them money or downloaded their software
> you have formed a trust relationship with whoever controls that cert far
> stronger than the assurances
On Wed, 18 Jun 2014, Thorsten Glaser wrote:
> Furthermore, with upstream *and* Debian maintainer hat on, I refuse to
> use a Debian-specific “special way” here. I will only fix this upstream
> (and there, there is no unicode-data package).
Make it generic, instead. You could just automatize the t
On Wed, Jun 18, 2014 at 02:54:43PM +0200, Thorsten Glaser wrote:
> > Unicode 7.0 was recently released. I discovered some source packages
> > contain outdated copies of various Unicode data files. At minimum, the
>
> I know that xterm’s wcwidth.c direly needs updating, and that mgk
> doesn’t do th
On 2014-06-17 13:20:59 +0100, Simon McVittie wrote:
> It should be possible to make a CA certificate that is only considered
> to be valid for the spi-inc.org and debian.org subtrees, and then trust
> the assertion that SPI control that certificate - but in widely-used
> applications, that isn't po
On Wed, 18 Jun 2014, Paul Wise wrote:
> Unicode 7.0 was recently released. I discovered some source packages
> contain outdated copies of various Unicode data files. At minimum, the
For mine, mksh and jupp do, but they do not use the data files directly.
Instead, when Unicode is updated, I change
Hi all,
Unicode 7.0 was recently released. I discovered some source packages
contain outdated copies of various Unicode data files. At minimum, the
following packages embed part of the Unicode data (UnicodeData.txt).
There are probably many more embedding different parts of the Unicode
data, ren
(so not going to comment on the first part of the thread, beside maybe:
Its really sad that it is even suggested that DDs would need a technical
solution for the inherently social problem of a co-worker dying…)
On Wed, Jun 18, 2014 at 04:21:36AM +0200, Christoph Anton Mitterer wrote:
> On Mon, 201
Somewhere in another universe, someone proposed moving Developer's
Reference to the wiki. One of the arguments was that it would let you
make changes _quickly_. I'm shamelessly :-P disclosing a message in this
thread:
* Stefano Zacchiroli , 2014-06-18, 13:39:
Right. But do we really want that
* Holger Levsen , 2014-06-18, 12:46:
usually one should depend on a fixed hash in such downloader
packages... doing it with gpg is securely possible, but much more
complicated.
and then for each update you need to update the launcher package -
thats an aweful lot of work for little / no gain
Hi,
On Mittwoch, 18. Juni 2014, Christoph Anton Mitterer wrote:
> torbrowser-launcher seems to use the keys from the upstream
> developers... basically giving them (who are not DDs) the potential
> power to install _any_ code in the system of Debian users.
fun fact: there's at least one DD among
Hello!
In preparation for the upcoming upower transition maintainers (and
other volunteers) will need to verify their packages still works.
Why am I stating the obvious?
The new upower version has been sitting in experimental for almost
4 months now for people to test. (On top of this I personal
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: r-cran-brew
Version : 1.0-6
Upstream Author : Jeffrey Horner
* URL : http://cran.r-project.org/web/packages/brew/
* License : GPL2
Programming Lang: R
Description : GNU R templating
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: r-cran-matrixstats
Version : 0.10.0
Upstream Author : Henrik Bengtsson
* URL : http://cran.r-project.org/web/packages/matrixStats/
* License : Artistic-2.0
Programming Lang: R
Descriptio
33 matches
Mail list logo
