On 2015-06-16 09:12:36 -0700, Russ Allbery wrote:
> There are a lot of really complex things you can do with versioning and
> cases where that version number is meaningful, but for the vast majority
> of libraries, I recommend not worrying about it and just always using some
> simple transform of t
Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg
* Package name: scala-xml
Version : 1.0.3
Upstream Author : Typesafe, Inc.
* URL : https://github.com/scala/scala-xml
* License : BSD-3-clause
Programming Lang: Scala
Description : Standard Scala XM
On Sun, 2015-06-14 at 14:08:24 +0200, Thomas Goirand wrote:
> On 06/14/2015 05:46 AM, Guillem Jover wrote:
> > Well if you want reproducible output, then use the same tool version.
>
> That's not possible: Jessie, Sid and Trusty don't have the same version,
> and we need to generate the orig.tar f
On 06/16/2015 04:26 PM, Vincent Lefevre wrote:
> And AFAIK, the request is not to drop xz support, just to add lzip
> support (though the "instead of" in the subject could be ambiguous).
Correct. I never thought lzip should replace xz completely, just an
option "instead" of xz... :)
Thomas
--
Hi,
it's time to prepare for GCC 5 as the default compiler in unstable. Compared to
earlier version bumps, the switch to GCC 5 is a bit more complicated because
libstdc++6 sees a few ABI incompatibilities, partially depending on the C++
standard version used for the builds. libstdc++6 will suppo
Vincent Lefevre wrote:
> On 2015-06-15 18:56:47 +0200, Andreas Metzler wrote:
[...]
>> No, it should not have been filed, since the same bug had been filed 5
>> times already.
> No, this is *not* the same bug that was filed. The bugs that were
> filed are claimed to be fixed in gnutls28/3.3.15-5,
Vincent Bernat writes:
> In libbsd, I see that you started with LIBBSD_0.0. Does this mean libbsd
> has always used symbol versioning? Otherwise, the start point would be
> to use the previous SONAME (computed from the previous -version-info),
> right?
There are a lot of really complex things yo
Guillem Jover wrote:
> In any case, barring better documentation or guides, using example
> implementations simpler than glibc might be useful to people. So I
> offer libbsd, but I'm sure there are many others. We could perhaps
> even create a wiki page listing some of those pointers.
libabc is a
+++ Thorsten Glaser [2015-06-16 13:39 +]:
> There are two coëxisting sets of nomenclature for cross-compiling around.
> Both are “correct” and have their merits, but they come from different
> cultures and have different goals.
>
> Unfortunately, variables like HOSTCC, TARGET_CC, CC_FOR_BUILD
On 2015-06-15 20:52:25 +0200, Magnus Holmgren wrote:
> But libgnutls-deb0-28 technically doesn't break libnettle4, nor does
> libnettle6. It's only certain combinations of three or more packages
> that are broken, something the dependency system can't handle.
Then either the dependency system shou
On 2015-06-15 18:56:47 +0200, Andreas Metzler wrote:
> Vincent Lefevre wrote:
> [...]
> >(Bug 788710 shouldn't have been closed, but changed to something
> >like what bug 788735 says.)
> [...]
>
> No, it should not have been filed, since the same bug had been filed 5
> times already.
No,
On 2015-06-15 05:04:46 +0200, Guillem Jover wrote:
> On Sun, 2015-06-14 at 16:48:21 +0200, Vincent Lefevre wrote:
> > (this example is a postfix mail log) and uses much less memory for
> > compression:
> >
> > $ sh -c 'ulimit -v 20; lzip -9 < mail.log > /dev/null'
> > $ sh -c 'ulimit -v 80
On Tue, Jun 16, 2015 at 9:29 PM, Peter Easthope wrote:
> What pdftohtml source is appropriate for jessie?
apt-cache search suggests it is in poppler-utils now:
https://sources.debian.net/src/poppler/jessie/utils/pdftohtml.cc
--
bye,
pabs
https://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE,
Hi,
There is no poppler-utils-dev package.
https://sources.debian.net/src/pdftohtml/ refers to etch
and sarge, which are somewhat outdated.
What pdftohtml source is appropriate for jessie?
Thanks, ... Peter E.
--
123456789 123456789 123456789 123456789 123456789 1234
❦ 16 juin 2015 15:50 +0200, Guillem Jover :
> In any case, barring better documentation or guides, using example
> implementations simpler than glibc might be useful to people. So I
> offer libbsd, but I'm sure there are many others. We could perhaps
> even create a wiki page listing some of tho
Hi!
On Tue, 2015-06-16 at 09:18:34 +0200, Vincent Bernat wrote:
> There is not a lot of documentation about how to handle that from an
> upstream point of view. There is the info page (section VERSION) of ld
> about -version-script.
That's true, there's lots of information spread all over the pla
Guillem Jover debian.org> writes:
> On Mon, 2015-05-11 at 01:34:08 +0200, Matthias Klose wrote:
> > On 05/10/2015 03:32 AM, Guillem Jover wrote:
> > > CC_FOR_BUILD = gcc
Plus, what Wookey said.
> > the above mentioned wiki pages still talk about HOSTCC and BUILDCC. Please
> > clarify when to us
Jonas Smedegaard jones.dk> writes:
> Standard approach in The Perl team seems to be to skip the license
> granting statement (i.e. verbatim-from-license-issuer text) and include
> only license boilerplates (i.e. verbatim-from-license-author texts),
That is rather… interesting… as the licence
Dimitri John Ledkov debian.org> writes:
> somebody else did a bad rebase, and then people started to query why I
You should just not accept rebase, *ever*.
[receive]
denyNonFastforwards = true
denyDeletes = true
This is the standard config of all Evolvis (FusionForge inhouse va
Jonas Smedegaard jones.dk> writes:
> What I do is add a custom build target that rewrites debian/control
> based on rmadison query resolving current archs for a given package.
Please don’t forget the debian-ports architectures for this. (I think
this is a point where not-even-on-dpo new archite
Ansgar Burchardt debian.org> writes:
> Please be aware that --force-yes makes apt ignore invalid signatures for
Ouch.
What is the equivalent of --force-yes with*out* --allow-unauthenticated,
then? This scenario (scheduled non-interactive upgrades) is common…
Thanks,
//mirabilos
Hi all,
I am trying to setup a Debian 8 machine running XEN, which I've
installed from the package manager, to use the USB passthrough.
It looks like I need to use the module xen-usbfront and xen-usbback,
which I can't find in the /lib/modules/(my kern)/*
Are there ways to get around this ?
Th
On Mon, 2015-06-15 at 18:25 +0100, pietrop wrote:
> Hi all,
>
> I am trying to setup a Debian 8 machine running XEN, which I've
> installed from the package manager, to use the USB passthrough.
>
> It looks like I need to use the module xen-usbfront and xen-usbback,
> which I can't find in the /l
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: python-rencode
Version: 1.0.3
Upstream Author: 2010 Andrew Resch
License: GPL-3+
URL: https://github.com/aresch/rencode
Vcs-Browser: http://anonscm.debian.org/cgit/collab-
Package: wnpp
Severity: wishlist
Owner: Daniel Stender
* Package name: ocropy
Version : 1.0
Upstream Author : Thomas Breuel
* URL : https://github.com/tmbdev/ocropy
* License : Apache-2.0
Programming Lang: Python
Description : Python OCR engine using r
❦ 15 juin 2015 20:20 -0700, Russ Allbery :
>>> To avoid confusing myself further, Russ and Neil, are you both talking
>>> about the "debian/symbols" files? I thought Russ might have been
>>> talking about "versioned symbols at DSO level" (e.g. symbol@LOW0 vs
>>> symbol@LOW1).
>
>> I'm pretty su
26 matches
Mail list logo
