Hi,
Quoting Nikolaus Rath (2016-05-29 22:11:58)
> Did you write down your findings in some more detail somewhere?
no, sorry.
> I'd be curious why e.g. a LD_PRELOAD based wrapper would not work for all
> important cases.
For me "all important cases" were "compilation of all debian source package
On Sun, 2016-05-29 at 23:32 -0400, Jason Briggs wrote:
> I do not know why upstream has not done anything.
I would suggest a thread CCing upstream, the Debian maintainer, the
Fedora maintainer and the Ubuntu maintainer asking for clarification.
--
bye,
pabs
https://wiki.debian.org/PaulWise
s
Thank you for the detailed information.
I do not know why upstream has not done anything. In mailing list someone from
Xorg acknowledged that offscreen surfaces are known problem and suggested the
first workaround
(https://lists.freedesktop.org/archives/spice-devel/2012-November/011479.html)
a
On Mon, May 30, 2016 at 4:10 AM, Jason Briggs wrote:
> Hello, sorry to disturb, a resource said to contact this list:
> https://www.debian.org/doc/manuals/developers-reference/beyond-pkging.html#mia-qa
Laurent is definitely not MIA, last mail is yesterday:
https://bugs.debian.org/cgi-bin/bugrep
Package: wnpp
Severity: wishlist
Owner: Chris Lamb
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: tab
Upstream Author : Wayne Cripps
* URL : https://github.com/mandovinnie/Lute-Tab
* License : BSD
Programming Lang: C
Description : Typesetter for lute
Hello, sorry to disturb, a resource said to contact this list:
https://www.debian.org/doc/manuals/developers-reference/beyond-pkging.html#mia-qa
There is a very impeding bug in the kvm spice/qxl package:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801081
The maintainer replied once and th
On May 28 2016, Johannes Schauer wrote:
> Hi,
>
> Quoting Paul Wise (2016-05-28 06:45:44)
>> I think it would be interesting to automatically track how each file
>> in a binary package was created and which files they were derived
>> from. Then we could automatically generate proper copyright file
Hi,
minor correction. Our packaging does not use parallelism of the.compiler, but
the rebuild-all-tool (dht make-all) can run multiple builds in parallel, using
-j n.
Greetings,Joachim
Am 29. Mai 2016 14:43:54 MESZ, schrieb Sean Whitton :
>Hello,
>
>I received an offer of some computing power
* Sean Whitton , 2016-05-29, 21:43:
The disc space required would be the total of:
- all the source packages & orig tarballs that have the haskell group
specified as the Maintainer:
- plus all the binary packages built from those
- plus a base sid debootstrap chroot (around 1.6GB)
A chroot w
Hello,
I received an offer of some computing power off-list. Thank you for
your reply, regardless. For posterity I'll answer your questions:
On Sun, May 29, 2016 at 02:14:40PM +0200, Michael Tautschnig wrote:
> Is this a single-core endeavour, or would would you benefit from
> multiple cores?
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-as...@lists.debian.org,
pkg-tcltk-de...@lists.alioth.debian.org
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
* Package name: tkblt
Version : 3.0.1
Upstream Author : William Joye
* URL : https://github.com/SA
Hi Sean,
On Sun, May 29, 2016 at 20:32:43 +0900, Sean Whitton wrote:
> Dear all,
>
> The Debian Haskell Group has picked a target set of package versions to
> freeze on for stretch. I'm working to upgrade packages in the DHG
> source package git repository to the target versions. This requires
Dear all,
The Debian Haskell Group has picked a target set of package versions to
freeze on for stretch. I'm working to upgrade packages in the DHG
source package git repository to the target versions. This requires
quite a lot of computation, and the only machine I have access to until
late Jul
[2016-05-28 13:20] Stefano Zacchiroli
> On Sat, May 28, 2016 at 02:18:51AM +0300, Dmitry Bogatov wrote:
> > But seems we do not have tools to check it. Probably, we need some way
> > to mark licenses of whole binary packages. WDYT?
>
> You're correct that we have no way to document the licenses o
On Sun, May 29, 2016 at 12:00:28AM +0200, Rene Engelhard wrote:
> > > e.g. if you have a package 1.0 and add a complete branch update as a patch
> > > (or upgrade to a snapshot) one should do a 1.0+gitYYYDDMM-1 or whatever
> > > format
> > > you choose. Not 1.0-15 or so.
> > Here the question is "
15 matches
Mail list logo
