Quoting Holger Levsen (2019-05-14 17:38:15)
> > Now one can turn this argument upside down. One can say: unstable is the QA
> > area. Britney prevents testing migration on autopkgtest/piuparts/ missing
> > binaries. In that case, we should simply stop filing such things in the BTS
> > and stop doin
Quoting Adrian Bunk (2019-05-14 10:11:46)
> On Mon, May 13, 2019 at 11:08:21PM +0200, gregor herrmann wrote:
> > On Mon, 13 May 2019 22:22:32 +0300, Adrian Bunk wrote:
> >
> > > In my experience, keeping existing packages at exotic build systems or
> > > ancient dh compat levels causes fewer prob
Quoting Sam Hartman (2019-05-13 21:49:20)
> > "Holger" == Holger Levsen writes:
> Holger> On Mon, May 13, 2019 at 03:37:55PM -0400, Sam Hartman wrote:
> Bernd> gcc also needs a compiler to build - so I think it should be
> Bernd> safe to allow debhelper to build its package using
>
Hi,
Quoting Mo Zhou (2019-04-08 11:58:26)
> The header script is not really what debian/rules does. For example,
> when you are going to build some official Debian package, you may want
> to do the following:
>
> $ debcheckout foobar
> $ cd foobar; gbp export-orig; debuild -S -nc
> $ sbuild
Hi,
Quoting Geert Stappers (2019-03-24 09:53:58)
> > bear with me if the topic of the upcoming european copyright law (aka §13)
> > has been discussed in other mailing lists. As being responsible for
> > screenshots.debian.net I honestly am a bit worried about the implications.
> > As usual??? IAN
Quoting Mo Zhou (2019-03-08 12:08:54)
> (2) Is it a good idea to write a test script, that manually sets up a qemu VM
> then tests the module[1]? (Such that we can get rid of the isolation-machine
> restriction, and make Debian CI test the ZFS kernel module)
I attempted that for my package mmdebst
Quoting Paul Wise (2019-01-19 04:38:04)
> > At
> >
> > https://qa.debian.org/debcheck.php?dist=unstable&package=fonts-sawarabi-mincho,
> > it show as below but debhelper-compat (= 12) is satisfied in sid
> > > BuildDepends
> > >
> > > Package declares a build time dependency on debhelper-compat
Hi,
Quoting Axel Beckert (2019-01-06 01:39:09)
> while trying to get the nocheck build profile working, I stumbled over
> some discrepancies between
>
> * Debian Policy §4.9.1,
> * dpkg-buildflags (behaviour + man page), and
> * lintian's long description of the tag
> override_dh_auto_test-does
Hi,
Quoting Pirate Praveen (2018-12-15 07:17:14)
> On 12/15/18 4:11 AM, Bernd Zeimetz wrote:
> > I'm wondering if somebody implemented a salsa pipeline to rebuild the
> > reverse-deps of a library?
> >
> > Is there some example/docker image to build on?
> https://salsa.debian.org/ruby-team/meta/b
Hi,
Quoting Holger Wansing (2018-08-25 20:30:15)
> The manpage of sbuild-createchroot contains commandline examples for several
> use cases, but not for cross-compiling.
yes, because sbuild-createchroot has nothing to do with cross-compiling.
chroots that you use to compile natively or cross with
Hi,
Quoting Benjamin Drung (2018-08-01 16:28:54)
> > Build Debian packages using OverlayFS and systemd namespace
> > containers.
> >
> > conbuilder creates a base filesystem using debootstrap, then
> > overlays it with a filesystem to install the required dependencies
> > and finally runs the bui
Quoting Chow Loong Jin (2018-05-03 06:27:01)
> On Wed, May 02, 2018 at 11:23:56AM +0200, Thomas Goirand wrote:
> > [...]
> > Frankly, I don't see the point in writing this kind of software. Sbuild
> > works super well with the overlay backend, and already has throw-able
> > chroots in tmpfs. Adding
Quoting Ian Jackson (2018-05-01 16:38:28)
> Geert Stappers writes ("Re: Announce: docker-buildpackage"):
> > On Tue, May 01, 2018 at 09:41:13PM +0800, Paul Wise wrote:
> > > On Tue, May 1, 2018 at 9:23 PM, Enrico Weigelt, metux IT consult wrote:
> > > > I've written a tool for isolated deb builds i
Hi,
Quoting Adam Borowski (2018-04-15 22:30:47)
> On Sun, Apr 15, 2018 at 09:45:45PM +0200, Helmut Grohne wrote:
> > On Sun, Apr 15, 2018 at 09:38:27PM +0200, Christoph Biedl wrote:
> > > The src:file package doesn't ship python{,3}-magic any longer, the change
> > > was two months ago. Mind to ch
Quoting Nikolaus Rath (2018-01-11 22:15:44)
> On Jan 11 2018, Johannes Schauer wrote:
> > We can check whether two binary packages built with a different set of
> > build profiles active are actually the same by using the tools from
> > the reproducible builds project.
> N
Quoting Philipp Kern (2018-01-11 00:20:17)
> On 2018-01-10 22:53, Johannes Schauer wrote:
> > But unless we want to pull a full Gentoo here and really make the
> > information with which build profile a given binary package was built part
> > of the binary package and
Quoting Steve Langasek (2018-01-10 21:49:02)
> On Mon, Jan 08, 2018 at 08:36:50PM -0500, Michael Stone wrote:
> > On Mon, Jan 08, 2018 at 12:09:09PM -0800, Steve Langasek wrote:
> > > Top-posting to just say +1, and that I was going to reply with much the
> > > same.
>
> > > I don't even think the
Hi,
Quoting Steve Langasek (2018-01-10 21:52:44)
> On Tue, Jan 09, 2018 at 03:07:01PM +0100, Johannes Schauer wrote:
> > Such a header could be introduced but that would be undesirable for two
> > reasons:
>
> > - it would make it hard to check whether the binary packag
Quoting Paul Wise (2018-01-10 02:40:07)
> On Tue, Jan 9, 2018 at 10:07 PM, Johannes Schauer wrote:
> > No, there is no header in the binary packages that indicates with which
> > profile a source package was built to generate the given binary package.
> Is this information
Quoting Jeremy Bicha (2018-01-09 17:35:30)
> On Tue, Jan 9, 2018 at 9:07 AM, Johannes Schauer wrote:
> > So we
> > could talk about whether we should allow more build profiles that change
> > binary
> > package contents but so far I don't see the use case for
Quoting Adrian Bunk (2018-01-09 20:54:31)
> On Tue, Jan 09, 2018 at 01:22:33PM -0500, Michael Stone wrote:
> > On Tue, Jan 09, 2018 at 11:35:30AM -0500, Jeremy Bicha wrote:
> > > At times, Ubuntu needs to avoid certain build-dependencies because
> > > they would add an unwanted "universe" binary de
Quoting Simon McVittie (2018-01-09 17:42:04)
> On Tue, 09 Jan 2018 at 15:40:04 +, Wookey wrote:
> > On 2018-01-09 15:07 +0100, Johannes Schauer wrote:
> > > Thus, we keep packages built with a different build profile but the same
> > > name/version/arcitecture b
Quoting Wookey (2018-01-09 06:03:26)
> On 2018-01-08 20:36 -0500, Michael Stone wrote:
> > How, then, would you tell by looking at the package name+version which kind
> > of package you have?
> The package header says what profiles it was built with. The package
> name+version doesn't change - tha
Quoting Hleb Valoshka (2018-01-04 19:35:28)
> On 1/3/18, Andrew Shadura wrote:
> > Do we really need systemd-less builds? I'm not convinced this is something
> > relevant to Debian.
> [...]
> https://wiki.debian.org/BuildProfileSpec#Derivative_specific_profiles
>
> At least some DD have a differe
Quoting Simon McVittie (2018-01-03 14:30:55)
> On Wed, 03 Jan 2018 at 15:12:51 +0300, Hleb Valoshka wrote:
> > Please introduce official nosystemd build profile so downstream
> > distributions can send patches to package maintainers with
> > systemd-less build instead of keep them in home.
>
> In
Quoting Josh Triplett (2017-10-24 04:29:32)
> Philipp Kern wrote:
> > I think that's a very important observation. I don't think you can
> > necessarily conclude that the system where the package is initially
> > installed is the system were the code is executed.
> >
> > In many kinds of image-base
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: orocos-bfl
Version : 0.8.0
Upstream Author : Tinne De Laet, Klaas Gadeyne
* URL : http://www.orocos.org/bfl
* License : LGPL-2.1+
Programming Lang: C++
Description : Orocos
Quoting Andreas Metzler (2017-09-27 19:38:22)
> Andreas Tille wrote:
> [...]
> > To answer Mattias question why not using source uploads all the time:
> > Once I have build the package to see whether all those lintian issues
> > are fixed I want to fix I have a sensible package to upload and someh
Quoting Julian Andres Klode (2017-08-19 00:18:54)
> > > Currently (for Buster) the fdisk package is being made
> > > 'pseudo-essential' via a dependency from the Essential util-linux
> > > package, where the tools was split out from. (This is also to support
> > > upgrades from Stretch to Buster.)
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: rss-bridge
Version : 2017-08-03
Upstream Author : sebsauvage
Mitsukarenai
Pierre Mazière
logmanoriginal
* URL : https://github.com
Quoting Steffen Möller (2017-07-29 18:05:27)
> On 29.07.17 17:51, Jeff wrote:
> > On 29/07/17 17:26, Steffen Möller wrote: >> The HPC community does not want
> > to need root privileges to get their
> >> software installed/used on the HPC setup. This excludes regular >>
> Debian packages, traditio
Quoting Paul Wise (2017-07-22 13:34:46)
> I would wager most Debian packages are not bit-for-bit identical when you
> vary the installation prefix (and Debian build tools don't support doing that
> AFAICT), but you can almost fake user-installable packages using existing
> binary packages using som
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: libjs-blueimp-md5
Version : 2.7.0
Upstream Author : Sebastian Tschan
* URL : https://github.com/blueimp/JavaScript-MD5
* License : Expat
Programming Lang: JavaScript
Description
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: libjs-toastr
Version : 2.1.3
Upstream Author : John Papa , Tim Ferrell
* URL : http://codeseven.github.io/toastr/
* License : Expat
Programming Lang: JavaScript
Description
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: libjs-bootbox
Version : 4.4.0
Upstream Author : Nick Payne
* URL : http://bootboxjs.com/
* License : Expat
Programming Lang: JavaScript
Description : programmatic dialog boxes
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: node-webrtc-adapter
Version : 4.1.0
Upstream Author : Philipp Hancke
* URL : https://github.com/webrtc/adapter
* License : BSD-3-Clause
Programming Lang: JavaScript
Description
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: node-sdp
Version : 2.2.0
Upstream Author : Philipp Hancke
* URL : https://github.com/fippo/sdp
* License : Expat
Programming Lang: JavaScript
Description : SDP parsing and
Hi,
Quoting Christoph Biedl (2017-06-27 00:37:33)
> Let's be honest: Shell scripts, while easy to write, carry too many risks of
> unsafe programming. So while your proposed fixing is a step in the right
> direction, this is all just band-aid. We (as in Debian) should look forward
> and try to rep
Quoting Christian Seiler (2017-06-07 15:26:35)
> - You install package A, which Recommends: B, but you don't
> want B, notice that at the time, and either remove B
> afterwards, or install A with --no-install-recommends. But
> then you install package C at a later point in time, which
Quoting James Clarke (2017-05-22 16:25:38)
> But I notice that for the sbuild path, schroot is completely missing,
Maybe I should also point out that schroot is just the *default* sbuild chroot
backend. It also supports the "sudo" mode (which essentially just uses "sudo
chroot") and the autopkgte
Quoting Jonathan Dowland (2017-05-15 10:25:30)
> On Sun, May 14, 2017 at 10:06:06PM +0100, Ben Hutchings wrote:
> > git: 18907
> > svn: 2377
>
> ^ how many of these are from teams (like pkg-gnome, at one point at least)
> who want to switch to git but lack the time or person-power or motivation to
Hi,
Quoting Timo Weingärtner (2017-03-24 16:56:51)
> These apt settings keep my systems clean and I guess they would also help
> build chroots:
>
> Apt::AutoRemove::RecommendsImportant "false";
> Apt::AutoRemove::SuggestsImportant "false";
> Apt::Install-Recommends "false";
> Apt::Install-Sugges
Hi Mattia,
Quoting Mattia Rizzolo (2017-01-09 11:27:30)
> On Sun, Jan 08, 2017 at 01:05:37PM +0100, Johannes Schauer wrote:
> > Mattia, please see below for a pbuilder-specific question.
>
> Thanks for CCing me; I'm not following this thread anymore (as it
> surpassed the
Hi,
Quoting Ian Jackson (2017-01-09 18:33:51)
> Johannes Schauer writes ("Re: Feedback on 3.0 source format problems"):
> > Sbuild could do this cleanup itself if there was a way to
> > automatically determine whether the user would like their tree to be
> &g
Hi all,
Mattia, please see below for a pbuilder-specific question.
Quoting James Clarke (2017-01-08 12:14:07)
> This turns out to be true. Working in a patches-applied tree:
>
> $ dpkg-source --before-build .
> $ dpkg-source -b .
> $ dpkg-source --after-build .
>
> leaves the patche
Hi,
Quoting Thibaut Paumard (2017-01-07 07:12:59)
> I manage my patches using quilt. I would really prefer if sbuild et al.
> would revert the patches after building by default, but that's life. I
> respect that other people have other views.
you could always file a wishlist bug against sbuild wi
Hi,
Quoting Ben Finney (2017-01-01 23:37:19)
> Adam Borowski writes:
> > I wonder, would it be better if we switched to using the word "depender" in
> > place of "reverse dependency"?
>
> I don't know a simple term in English that carries that meaning.
>
> To me, “depender” feel like a neologis
Hi,
Quoting Adam Borowski (2016-12-27 17:56:59)
> Current procedure of subscribing to a bug is an abomination: you need FOUR
> mails for something that could be done by default.
I feel you. This is why I long stopped subscribing to bugs I file. The
ping-pong is too bothersome for me. Now I just k
Hi,
Quoting Mattia Rizzolo (2016-12-18 11:38:24)
> On Sat, Dec 17, 2016 at 09:27:12PM -0500, James McCoy wrote:
> > As Arno hinted at, it's to have reliable builds. A transient inability
> > to install the first arm of an alternation should caused a dep-wait
> > state, not building with the alter
Hi,
Quoting James McCoy (2016-12-18 16:04:47)
> On Sun, Dec 18, 2016 at 02:26:09PM +0100, Ondrej Novy wrote:
> > Hi,
> >
> > 2016-12-18 14:14 GMT+01:00 James McCoy :
> >
> > Well, sbuild's man page documents that the aptitude resolver will check
> > alternatives. If it doesn't in practic
Quoting Josh Triplett (2016-12-12 18:19:03)
> (I'd love to auto-generate Build-Depends too, but that would require a much
> larger overhaul, and the last time that came up the answer was a resounding
> "no".)
for reasons why auto-generated Build-Depends are a bad idea, see:
https://bugs.debian.or
Hi,
Quoting Nikolaus Rath (2016-12-11 21:17:50)
> I would like to start using dgit for one of my packages, using the
> dgit-maint-merge workflow.
>
> If I understood correctly, following the dgit-maint-merge(7)
> instructions for the initial setup will give me a repository with only
> the upstrea
Hi,
Quoting Wouter Verhelst (2016-12-01 16:24:16)
> On Mon, Nov 14, 2016 at 06:10:57PM +0100, Johannes Schauer wrote:
> > But maybe to talk about this option: what would speak against changing the
> > "nmu" command of wanna-build to also add an option that allows setting
Hi,
Quoting Mattia Rizzolo (2016-11-28 13:39:46)
> On Mon, Nov 28, 2016 at 11:17:21PM +1100, Scott Leggett wrote:
> > But that means that pbuilder is carrying my local environment over to the
> > build environment - so the build environment is no longer pristine. Is
> > that behaviour intentional
[ disclaimer: sbuild maintainer here - totally biased ]
Quoting Mattia Rizzolo (2016-11-28 12:06:19)
> On Mon, Nov 28, 2016 at 09:52:39PM +1100, Scott Leggett wrote:
> > (inspired by a blog post[0]), [0]
> > https://people.debian.org/~stapelberg/2016/11/25/build-tools.html
> I'll only say that 1)
Hi,
Quoting Hideki Yamane (2016-11-23 08:24:27)
> Just a question, sometimes some dependency-broken packages would go into
> repository and apt may complain it. Of course, someone would report it and
> maintainers would fix it soon, but 0 dependency-broken packages is best.
>
> Can we integra
Hi,
Quoting Holger Levsen (2016-11-14 18:25:34)
> To me it seems a binNMU should change SOURCE_DATE_EPOCH, as debian/changelog
> gets modified by changelog.$arch, so it's actually a different source which
> is being build.
debian/changelog doesn't get modified by changelog.$arch. The latter is
ge
Hi,
Quoting Ian Jackson (2016-11-14 17:33:55)
> Unless the timestamp is of the binnmu request, plumbing to try to get
> the same timestamp will be difficult.
>
> I'm not a fan of the idea of merely adding 1 second per binnmu. That
> would mean that making a second binnmu correctly would involve
Hi,
Quoting Ian Jackson (2016-11-14 14:52:18)
>I don't think it is possible to make the binnmu timestamp the same
>across architectures. For example, a package might be rebuilt only
>on some architectures. I don't think we want to change that. In
>particular, even if we were pre
Hi,
Quoting Mattia Rizzolo (2016-11-13 11:48:02)
> On Sun, Nov 13, 2016 at 10:44:34AM +, Holger Levsen wrote:
> > if the only valid usecase of binary uploads is bootstraping an arch (which
> > I'm not sure is the only valid use case, but I cannot come up with another
> > right now…), I think w
Hi,
Quoting Colin Watson (2016-11-12 18:09:22)
> > * it supports only a single build-indep architecture rather than a list
>
> Not so; you have misread the code. It is a list of architectures that
> architecture-independent binary packages can be on.
>
> > I propose the new field to be a list p
Hi,
Quoting Ximin Luo (2016-11-10 18:13:00)
> Holger Levsen wrote:
> > On Thu, Nov 10, 2016 at 08:59:48AM -0200, Johannes Schauer wrote:
> > > One solution would be to increase SOURCE_DATE_EPOCH by 1 second for every
> > > binNMU to a package.
> >
Hi,
Quoting Colin Watson (2016-11-12 03:58:04)
> On Sat, Nov 12, 2016 at 12:58:13AM +0100, Adam Borowski wrote:
> > * wanna-build(?)'s resolution of arch-specific build-depends is buggy. For
> > example, my package arch-test wants, among others:
> > binutils-x86-64-linux-gnu [!amd64 !i386 !x32] w
Hi,
Quoting Niko Tyni (2016-11-10 10:01:38)
> On Thu, Nov 10, 2016 at 10:34:33AM +, Holger Levsen wrote:
> > can someone please point at a real life/archive example of such a file?
> > (a binNMU .changes file with Binary-Only-Changes field…)
>
> That's in the .buildinfo file (not .changes), a
Hi,
Quoting Emilio Pozuelo Monfort (2016-11-10 07:04:55)
> On 10/11/16 10:00, Ansgar Burchardt wrote:
> > The date from the last sourceful upload should probably still be used
> > for any date/time information included in generated files to ensure
> > they are identical on all architectures (or at
Hi,
Quoiting Holger Levsen (2016-11-10 07:48:33)
> On Thu, Nov 10, 2016 at 10:38:45AM +0100, Emilio Pozuelo Monfort wrote:
> > > I see. And this changelog.$arch is neither part of the source package,
> > > the .changes file nor the .buildinfo file, it's just included in the
> > > binary packages?
Quoting Mattia Rizzolo (2016-11-09 16:45:43)
> Also, a personal pledge to everybody who's reading this: please don't attach
> yourself to your packages like mussels on a rock.
on that topic, I am warmly recommending Enrico Zini's "semi serious stand up
comedy notes":
Compersion, n: the feelin
Hi all,
Quoting Ian Jackson (2016-11-08 21:48:12)
> Guillem Jover writes ("Re: misleading timestamps in binnmus"):
> > So the actual problem is that the last timestamp gets reused for the
> > binNMUs, which seems totally bogus to me. This needs to be fixed in
> > whatever is injecting the binNMU e
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
We (Robotics section of Debian Science team) are packaging ROS (Robot OS:
http://www.ros.org/) for Debian. ROS uses many packages already in Debian,
but also has a set of core/toolchain/build-system packages which are not yet
uploaded
Hi,
Quoting Jakub Wilk (2016-09-07 19:29:05)
> * Vincent Bernat , 2016-09-07, 07:17:
> >both pbuilder and sbuild are using an isolated network namespace
>
> I know about pbuilder, but [citation needed] for sbuild.
there is no out-of-the-box functionality that provides this for sbuild. There
is a
Hi,
Quoting Johannes Schauer (2016-08-17 19:24:51)
> does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> chroots?
>
> I would like to remove some code from sbuild which is only useful for chroots
> with very old apt inside (specifically apt without support f
Hi Arturo,
Quoting Arturo Borrero Gonzalez (2016-08-26 09:19:23)
> here the author of that changelog line.
>
> The rationale for the change was:
> * the default init system in debian is systemd
> * I don't have any sysvinit system to keep sysvinit files under any
> kind of maintenance
> * sysv
Hi,
Quoting The Wanderer (2016-08-25 15:29:27)
> In other words: the problem here is the fact that apt's priorities in
> this regard are messed up.
>
> If there exists a dependency solution which will achieve the result
> requested on the command line (here, installing the lower version of the
>
Hi,
Quoting Johannes Schauer (2016-08-22 14:58:36)
> Quoting Ian Jackson (2016-08-22 12:55:48)
> > But even worse is that it would no longer be possible to sensibly
> > compute build orders without pre-building every package in a source
> > archive, because it would not be p
Hi,
Quoting Ian Jackson (2016-08-22 12:55:48)
> But even worse is that it would no longer be possible to sensibly
> compute build orders without pre-building every package in a source
> archive, because it would not be possible to statically determine
> which binary packages are supposed to come f
Hi,
Quoting Dimitri John Ledkov (2016-08-21 23:32:17)
> Surely old sbuild gpg key handing works correctly with gpg1. (Try gpg1
> first, if missing use gpg, assume it's classic gpg1)
>
> With new enough apt, no gpg key handing is needed.
>
> No support for gpg2 is needed, as any chroots with gpg
Hi,
Quoting Peter Samuelson (2016-08-21 11:45:35)
> [Johannes Schauer]
> > Old sbuild will not help you. The problem is mainly, that older
> > chroots contain an apt installation that has no support for the
> > [trusted=yes] option in sources.list.
>
> So if someone r
Hi,
Quoting Ian Jackson (2016-08-19 14:25:52)
> (Would it not be possible to generate the key inside the chroot? I
> guess there are probably other problems with that.)
that would require lots of time and entropy - unless somebody knows how to
trick gpg to generate a private/public key pair from
Hi,
Quoting Ian Jackson (2016-08-19 14:04:40)
> And to those others who replied, I would like to point out that answers of
> the form "oh no surely they don't" to questions like Johannes's can be
> harmful.
I read their answers as: "I don't think it is necessary for sbuild to support a
distributi
Hi,
does anybody plan to use sbuild in Stretch with Debian Squeeze or older
chroots?
I would like to remove some code from sbuild which is only useful for chroots
with very old apt inside (specifically apt without support for [trusted=yes] in
the sources.list). Maintaining this piece of code take
Hi,
Quoting Paul Wise (2016-08-10 17:32:15)
> On Wed, Aug 10, 2016 at 6:09 PM, Jakub Wilk wrote:
> > (And there's probably more that this simplistic search doesn't catch...)
>
> apt-key usage for instance:
>
> https://codesearch.debian.net/search?q=\bapt-key\b.*--recv%28-keys%3F%29%3F\s%2B%280x%
Hi,
Quoting Paul Wise (2016-08-10 05:12:55)
> The only possible way to solve this in general terms is, accurate document
> the copyright/license of the source package using the machine-readable format
> and during builds, track the transformation of input files in the source
> package to output fi
Hi,
Quoting Daniel Kahn Gillmor (2016-08-04 18:29:03)
> One of the main differences is that all access to your secret key will be
> handled through gpg-agent, which should be automatically launched as needed.
it might be important to note that gpg launching this gpg-agent process is not
optional
Hi,
Quoting Christian Seiler (2016-08-04 10:03:04)
> Shell snipped I used to get this data:
> awk '/^Package:/ { pkg = $2; }
> /^Installed-Size:/ { is = $2; }
> /^Size:/ { print pkg, $2, is }' \
> < /var/lib/apt/lists/*_debian_dists_sid_main_binary-amd64_Packages \
> | sort -k3 -n
Hi,
Quoting Iustin Pop (2016-05-28 00:53:18)
> If we go that way, they we should make it abstract: introduce Vcs-Path
> and Vcs-Layout. Both of these are completely independent of the software
> that hosts the code.
this would also make it possible to have spaces in the path name without having
t
Hi,
Quoting Jakub Wilk (2016-05-30 13:08:47)
> * Johannes Schauer , 2016-05-28, 10:04:
> >I was investigating this problem last year and as far as my research
> >went, there is no tracing method in existence which reliably traces
> >system calls in general, file system
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
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 files for
> binary packages. That is a hard project s
; and well-defined semantics.
>
> So in a way, I agree: It requires a bootstrap planner. Johannes Schauer
> spent a gsoc and much more to lay the groundwork for it. Though it can
> only start working once we clean the mess created by inconsistent stage
> profiles with no meaning.
>
Hi,
Quoting Pirate Praveen (2016-04-08 09:48:59)
> On 2016, ഏപ്രിൽ 8 12:42:30 PM IST, Tiago Ilieve wrote:
> >Maybe you can use an environment that's a little bit closer to a
> >standard system installation (at least to a point where you can expect
> >normal APT behavior), like a Docker or LXC con
Quoting Paul Wise (2016-03-31 08:42:58)
> On Thu, Mar 31, 2016 at 2:38 PM, Johannes Schauer wrote:
> > It looks mightily impressive! When I read about this originally I didn't
> > find a link with so many details and even screenshots - thanks for that! It
> > seems they
Quoting Paul Wise (2016-03-30 19:52:51)
> Looks like Microsoft went with a Linux syscall emulation layer for the
> Windows kernel:
>
> http://blog.dustinkirkland.com/2016/03/ubuntu-on-windows.html
if I understand it correctly, then this should indeed solve Eric's original
message.
It looks mighti
Hi,
Quoting Bill Allombert (2016-03-16 10:30:58)
> On Tue, Mar 15, 2016 at 11:15:16PM +0100, Joerg Jaspert wrote:
> > Additionally I turned off generating gzip compressed versions of those
> > files, xz is there.
>
> Does all services that read Packages files handle xz already ?
dose3 consumes P
Hi,
Quoting PICCA Frederic-Emmanuel (2016-02-28 10:09:45)
> I am preparing the next tango package, so I need to build the doc with lyx.
>
> But then I get this error message.
>
> make[5]: Entering directory '/<>/tango-9.2.0~a+dfsg/build/doc/src'
> cd ../../../doc/src; /usr/bin/lyx --export pdf2
Hi,
Quoting Pirate Praveen (2016-02-21 12:31:25)
> On Monday 15 February 2016 11:35 PM, Pirate Praveen wrote:
> >> systemd does not create any pid files. It only reads them to
> >> figure out which PID of a multi-process Type=forking service is
> >> the main PID of that service.
> >
> > Thanks fo
Hi,
Quoting Christian Seiler (2016-02-15 16:30:26)
> - the other services that use ExecStart=/bin/sh bin/$NAME start
>and ExecStop=/bin/sh bin/$NAME stop are problematic, because
>in the systemd service file you declare PIDFile to be in
>/run/gitlab, while the configuration that's rea
Hi,
Quoting Marco d'Itri (2016-02-15 16:05:20)
> On Feb 15, Pirate Praveen wrote:
> > More systemd troubles.
> >
> > While trying to move files that are created at runtime to /var,
> > I realized /var/run/gitlab won't persist across reboots. I have added
> This is not related to systemd, BTW.
Hi,
Quoting Paul Wise (2016-02-12 02:02:53)
> On Wed, Feb 10, 2016 at 9:09 PM, Johannes Schauer wrote:
> > A bit OT: the old-style-config-script lintian description links to a 404
> > page
> > on sources.debian.net. Maybe this link should be updated? Is there a way to
> &
Hi,
Quoting Bastien Roucaries (2016-02-12 10:10:10)
> Le 12 février 2016 02:02:53 GMT+01:00, Paul Wise a écrit :
> >On Wed, Feb 10, 2016 at 9:09 PM, Johannes Schauer wrote:
> >
> >> A bit OT: the old-style-config-script lintian description links to a
> >404 page
>
Hi,
Quoting Pirate Praveen (2016-02-11 16:58:56)
> You can use,
>
> systemctl start gitlab.target
>
> as init script has problems with systemd. The installation is complete
> otherwise.
>
> I added systemd unit files already and I will add a check for systemd to fix
> the bug.
thanks, that
201 - 300 of 433 matches
Mail list logo
