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 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
[ 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 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
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 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
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 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
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 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 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 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 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 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 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
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 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 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 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 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 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 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
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 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
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 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
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 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
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
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
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 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
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
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 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
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
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
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: 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: 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-blueimp-md5
Version : 2.7.0
Upstream Author : Sebastian Tschan
* URL : https://github.com/blueimp/JavaScript-MD5
* License : Expat
Programming Lang: JavaScript
Description
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
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
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 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.)
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
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 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: glui
Version : 2.37
Upstream Author : Paul Rademacher, Bill Baxter, John Kew, Nigel Stewart
* URL : https://github.com/libglui/glui/wiki
* License : ZLIB
Programming Lang: C
Hi,
Quoting Josh Triplett (2015-11-01 21:33:19)
> "Binary" seems a bit excessive for several reasons. First, it seems
> redundant with the "Source" entries in Packages files; we don't
> necessarily need a two-way cross-reference at all here. And second, we
> could assume that a missing entry mea
Hi,
Quoting Julian Andres Klode (2015-12-21 13:43:41)
> On Mon, Dec 21, 2015 at 01:35:21PM +0100, Alberto Salvia Novella wrote:
> > Julian Andres Klode:
> > > It just happens that some of the newly installed dependencies are also
> > > Suggested by other installed packages, and thus are not remove
Hi,
Quoting Stefano Zacchiroli (2016-01-04 23:14:11)
> On Mon, Jan 04, 2016 at 07:45:37AM +, Niels Thykier wrote:
> > Your second item has been brought up before with different
> > focus/rationale/purpose. At least I remember there being an interest
> > in splitting "non-free" into "non-free/
Hi,
Quoting Jerome BENOIT (2016-01-05 08:25:47)
> On 05/01/16 08:15, Johannes Schauer wrote:
> > Hi,
> >
> > Quoting Stefano Zacchiroli (2016-01-04 23:14:11)
> >> On Mon, Jan 04, 2016 at 07:45:37AM +, Niels Thykier wrote:
> >>> Your second item
Hi,
Quoting Ralf Treinen (2016-01-13 08:11:40)
> On Mon, Jan 11, 2016 at 05:25:40PM +0100, Julian Andres Klode wrote:
>
> > the following packages contain lines matching the
> > expression:
> > /var/lib/apt/lists/.*(Packages|Sources)
> >
> > Those files may be compressed by any compressor
Hi,
Quoting Felipe Sateler (2016-01-15 13:33:37)
> You are trying to create implications. a => b is the same as !a || b, which
> is how I expressed the dependencies above. This is easy to do for versioned
> dependencies, but not so easy for non-versioned ones (you cannot have
> !package in the Dep
Hi,
Quoting Thorsten Glaser (2016-01-18 21:16:16)
> On Mon, 18 Jan 2016, Waldemar Brodkorb wrote:
> > From a good friend I would expect some more positive feedback
> > for my hobby project ;)
> I said, it has its niche, but I doubt it has a place
> as a generic Debian package… libraries are genera
Hi,
Quoting Bastien ROUCARIES (2016-01-31 00:49:14)
> Could you document on wiki how can we begin as a package manager. For
> instance I could not achieve to parse
> http://bootstrap.debian.net/cross_all/imagemagick.html
I apologize. Since I wrote the software it is hard for me to put myself into
Hi Stephen and Bastien,
Quoting Stephen Kitt (2016-01-31 11:49:32)
> I'll give it a shot... (And add this later to the wiki.)
which page will you be editing?
> As I understand it, the page lists *dependency* problems which prevent:
It is indeed important to stress that these are only dependency
Hi,
Quoting Helmut Grohne (2016-02-02 20:40:38)
> On Tue, Feb 02, 2016 at 11:39:50AM -0500, Theodore Ts'o wrote:
> > I see these haven't entered testing because:
> >
> > * 183 days old (needed 5 days)
> > * crossbuild-essential-arm64/amd64 unsatisfiable Depends: libc6-dev:arm64
> > * crossbuild-e
Hi,
Quoting Niels Thykier (2016-02-02 23:27:21)
> Britney does *not* look at Build-Depends. Only (Pre-)Depends.
okay, thanks for clarifying!
> So, Britney's dependency resolver ("InstallabilityTester") actually supports
> all of that. What is lacking is support for passing the information to t
Hi Nokubi,
Quoting Bastien ROUCARIES (2016-02-10 10:29:46)
> On Wed, Feb 10, 2016 at 8:12 AM, NOKUBI Takatsugu wrote:
> > I am a maintainer of chasen package. It contains chasen-config, it
> > work as pkg-config like but it's a single script.
> >
> > Latest lintain reports:
> > E: libchasen-dev:
Hi,
Quoting Jakub Wilk (2016-02-11 12:44:34)
> * Johannes Schauer , 2016-02-10, 11:09:
> >The old-style-config-script tag which src:chasen suffers from as well and
> >which was also linked to by Bastien contains more valuable information. The
> >important message is: please u
Hi,
Quoting IOhannes m zmölnig (Debian/GNU) (2016-02-11 13:17:36)
> thank you very much for all your efforts!
let me express my gratitude as well!
Thank you for all your hard work! It seems installing gitlab pulled in more
than 330 (!!) ruby packages.
> now i only need a migration plan :-)
If
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
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 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 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 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 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 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 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
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
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
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
; 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 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
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 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 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 Helmut,
Quoting Helmut Grohne (2024-06-06 09:28:52)
> I have just uploaded
> * base-files
> * bash
> * dash
> * glibc
> * util-linux
> to unstable. These were the last remaining packages shipping aliased
> files inside the package set relevant to debootstrap.
thank you (and freexian for f
Hi,
Quoting Simon Richter (2024-06-06 11:32:33)
> > Would it be possible to set in stone that packages are supposed to always
> > be built in an environment where LC_ALL=C.UTF-8, or, in other words, that
> > builders must set LC_ALL=C.UTF-8?
>
> This would be the opposite of the current rule.
>
Hi,
Quoting Hakan Bayındır (2024-06-06 12:32:27)
> On 6.06.2024 ÖS 1:08, Johannes Schauer Marin Rodrigues wrote:
> > Quoting Simon Richter (2024-06-06 11:32:33)
> >>> Would it be possible to set in stone that packages are supposed to always
> >>> be built in an
Hi,
Quoting Helmut Grohne (2024-06-25 10:16:20)
> In this work, limitations with --chroot-mode=unshare became apparent and that
> lead to Johannes, Jochen and me sitting down in Berlin pondering ideas on how
> to improve the situation. That is a longer story, but eventually Timo Röhling
> asked th
Hi,
Quoting Simon McVittie (2024-06-27 15:59:01)
> On Thu, 27 Jun 2024 at 11:46:51 +0200, Helmut Grohne wrote:
> > I don't quite understand the need for a Dockerfile here. I suspect that
> > this is the obvious way that works reliably, but my impression was that
> > using podman import would be ea
Simon,
Quoting Simon McVittie (2024-06-27 19:16:54)
> On Thu, 27 Jun 2024 at 17:26:20 +0200, Johannes Schauer Marin Rodrigues wrote:
> > But, if everybody is so excited about this, where are the sbuild
> > contributors
> > implementing this?
>
> I'm sorry, con
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-fo...@lists.debian.org
* Package name: fonts-iosevka-term
Version : 31.0.0
Upstream Contact: Renzhi Li aka. Belleve Invis
* URL : https
Hi Otto,
Quoting Otto Kekäläinen (2024-07-28 00:38:40)
> I have drafted a new DEP at
> https://salsa.debian.org/dep-team/deps/-/merge_requests/8 titled "DEP-18:
> Enable true open collaboration on all Debian packages".
>
> Direct link to raw text:
> https://salsa.debian.org/dep-team/deps/-/raw/79
Hi,
Quoting Otto Kekäläinen (2024-08-02 17:23:51)
> I agree that Salsa is sometimes a bit sluggish
> (https://salsa.debian.org/salsa/support/-/issues/395),
what kind of hardware do you have? For people like me who are on slower
hardware, the web experience is absolutely not funny and "a bit slugg
Quoting Todd Zullinger (2024-08-15 01:12:01)
> Piper McCorkle wrote:
> > On Wednesday, 14 August 2024 16:43:54 CDT Agathe Porte wrote:
> >> Or maybe I could tar the upstream .git folder and store everything else
> >> as plain files? But still a binary blob in source package. And
> >> extracting the
Quoting Otto Kekäläinen (2024-08-19 03:45:37)
> I tried to use codesearch.debian.net to find out how many packages have a
> debian/gbp.conf but it seems it can't be used to simply list packages that
> have a specific file, it always also needs a search terms to look up inside
> the file.
>
> With
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: reform-handbook
Version : 2024-08-19
Upstream Contact: Lukas F. Hartmann
* URL : https://source.mnt.re/reform/reform-handbook
Hi,
Quoting Helmut Grohne (2024-08-20 07:28:52)
> What do you think about the proposed criteria and suggested set of source
> packages? Is it reasonable to remove these packages from unstable? In a
> sense, it is extending the idea of the testing auto remover to unstable.
> Similarly, a package ca
Hi,
Quoting Otto Kekäläinen (2024-08-27 08:42:53)
> > Before pushing for new ways of representing Debian stuff in git, I think it
> > would be a good idea to learn from all the other distros and distro-like
> > systems successfully using git [1]. Debian is not the only distro that
> > wants to use
Hi,
Quoting Steve McIntyre (2023-05-15 02:54:02)
> On Mon, May 15, 2023 at 12:24:15AM +0100, Luca Boccassi wrote:
> >On Sun, 14 May 2023 at 22:37, Josh Triplett wrote:
> >
> >> The x86-64 ABI is set. Feel free to make the case to the next
> >> architecture designer that their new ABI should have
Hi,
Quoting G. Branden Robinson (2023-05-19 16:19:35)
> > If people have strong opinions about that plan, let us know please.
>
> Well, maybe not a strong view, but a sense of vague unease--possibly an
> ill-informed one. As someone who has used SIMH for "real" work[1], I
> have to ask how someo
Hi,
Quoting Diederik de Haas (2023-05-31 00:51:06)
> > If people have strong opinions about that plan, let us know please.
>
> I have *strong* opinions about this.
>
> https://lists.debian.org/debian-kernel/2023/01/msg00372.html was a message/
> plea to not forget about supporting OLD systems.
>
Quoting Marco d'Itri (2023-06-09 09:41:43)
> On Jun 08, Raphael Hertzog wrote:
> > And creating the required symlinks would be done by those (standalone)
> > maintainer scripts...
> >
> > I don't know if we already have some rule/invariant in the configuration
> > order of the unpacked packages,
Hi,
Quoting Helmut Grohne (2023-06-09 15:22:39)
> Add a new package usrmerge-support (or whatever). It is a bit similar to
> multiarch-support: It must not have any dependencies or pre-dependencies. It
> will not have files, but maintainer scripts. Those scripts set up protective
> diversions on b
Hi,
mmdebstrap author here. This is the other bootstrapping tool which is currently
sitting at ~17% of the popcon value of debootstrap.
Quoting Helmut Grohne (2023-06-28 21:37:44)
> Once that is settled, the next big question is how to handle bootstrapping.
> We had a number of people arguing in
Hi,
Quoting Helmut Grohne (2023-07-12 15:34:38)
> This thread hopefully becomes more of a FYI than a discussion. I've turned
> those hacky scripts into some Python code that continuously (4 times a day)
> analyzes the archive for some of the problems summarized in DEP17. Interested
> parties may f
201 - 300 of 472 matches
Mail list logo
