Hi,
Quoting Sean Whitton (2019-07-23 17:47:45)
> > I prefer to build only once, if possible, generating both binary and source
> > .changes. Both in a clean chroot. Then I can try out my .debs and on
> > success just sign and dput. Works fine for me with pbuilder.
> ICBW but I am pretty sure that
Quoting Marc Haber (2019-07-24 08:17:19)
> On Mon, 22 Jul 2019 12:38:36 +0200, "Enrico Weigelt, metux IT consult"
> wrote:
> >Containerization is a valid approach for some kind of workloads
> >(eg. specific inhouse applications) that can be easily isolated from
> >the rest. But it comes with the
Quoting Marc Haber (2019-07-24 08:17:19)
> Do we have a build technology that uses containers instead of chroots yet?
Either using any container-based autopkgtest backend (like lxc or lxd):
$ sbuild --chroot-mode=autopkgtest --autopkgtest-virt-server=lxc
Or using the built-in "unshare"
Hi,
Quoting Paul Wise (2019-07-25 05:38:49)
> On Wed, Jul 24, 2019 at 2:42 PM Johannes Schauer wrote:
> > Or using the built-in "unshare" backend which uses linux user namespaces:
> >
> > $ sbuild --chroot-mode=unshare --chroot=debian-unstable.tar
>
&g
Hi,
Quoting Paul Wise (2019-07-26 04:31:29)
> > But you'd have to ask somebody who is more knowledgable about the security
> > implications of such a change. There certainly is a reason why #898446 is
> > still
> > open.
> >
> > Furthermore, since buildds currently use the schroot backend, I
Hi,
Quoting Simon McVittie (2019-07-26 09:51:24)
> schroot is also setuid root, and sbuild relies on this to set up the
> build-dependencies anyway, so in principle schroot/sbuild ought to be
> able to do something like this:
>
> - preparation step (as real root, in the chroot, with networking):
Quoting Samuel Thibault (2019-07-08 12:01:01)
> Thomas Goirand, le lun. 08 juil. 2019 11:57:45 +0200, a ecrit:
> > So if I understand correctly, I can just rebuild everything and do
> > source-only uploads, and the Debian infra will be smart enough to
> > understand how to build?
> Yes. Only the
Quoting Julian Andres Klode (2019-07-10 10:17:51)
> On Wed, Jul 10, 2019 at 10:10:41AM +0200, Philipp Kern wrote:
> > Given the timeline, shouldn't we also get oldstable to ship an InRelease
> > file?
> What's the use case for having oldstable in your sources.list on
> unstable/testing machines?
Quoting Paul Wise (2019-10-07 03:38:55)
> On Sun, Oct 6, 2019 at 7:23 PM Simon McVittie wrote:
> > FYI, this is because autopkgtest has an abstraction for multiple
> > container/virtualization mechanisms (lxc, lxd, qemu, schroot)
> It seems like this abstraction should be split out of the
Hi,
shameless plug for mmdebstrap incoming.
Quoting Philipp Kern (2019-10-07 13:21:36)
> On 10/7/2019 1:17 PM, Shengjing Zhu wrote:
> > On Mon, Oct 7, 2019 at 6:29 PM Simon McVittie wrote:
> >> On Mon, 07 Oct 2019 at 07:22:53 +0200, Johannes Schauer wrote:
> >&g
Hi,
Quoting Jonas Smedegaard (2019-10-08 10:30:45)
> Quoting Paul Wise (2019-10-08 02:35:14)
> > On Mon, 2019-10-07 at 11:29 +0100, Simon McVittie wrote:
> > > I think "re-bootstrap, don't upgrade" is an equally good principle for
> > > autopkgtest and sbuild? Both will be equally susceptible to
Hi,
Quoting Nicholas D Steeves (2019-10-05 18:41:55)
> Bernd Zeimetz writes:
> > On 10/5/19 3:31 AM, Paul Wise wrote:
> >> On Fri, Oct 4, 2019 at 10:49 PM Enrico Weigelt wrote:
> >>> On 24.07.19 08:17, Marc Haber wrote:
> Do we have a build technology that uses containers instead of chroots
Quoting Daniel Leidert (2020-02-26 10:27:03)
> Am Dienstag, den 25.02.2020, 17:40 + schrieb Ian Jackson:
> > For -devel, context is that Anthony Fok just uploaded a new upstream
> > version of pydoctor (a tool for extracting API docs for python
> > modules) in order to fix a couple of upstream
Quoting peter green (2020-02-27 22:54:19)
> > Relevant packages and bugs:
> > 943107 git-buildpackage: Python2 removal in sid/bullseye
> This bug is not marked as rc.
>
> Nevertheless I believe that this bug report is in-fact a false positive. From
> what I can tell git-buildpackage, even in
Hi,
Quoting Guillem Jover (2020-02-18 19:43:53)
> * If you are using raw debootstrap then just pass that option. Or
>just switch to use mmdebstrap which does not have a broken default,
>and is way way faster anyway.
since you mention mmdebstrap, let me add another reason against getting
Hi,
Quoting Simon McVittie (2020-01-16 19:47:02)
> I think I dimly remember someone setting up "the buildd from hell" which
> deliberately did this as a QA mechanism, but it doesn't seem to have
> continued in any systematic way.
is there more information about it somewhere? My inbox has only
Hi Daniel, Sam and all,
Quoting Sam Hartman (2020-01-17 01:27:52)
> > "Daniel" == Daniel Schepler writes:
>
> Daniel> (Incidentally, another offshoot was creating local patches to
> sbuild
> Daniel> which add an operation mode using systemd-nspawn --ephemeral to
> start
>
Quoting Sam Hartman (2020-01-17 09:45:43)
> > "Paul" == Paul Wise writes:
>
> Paul> On Mon, Jan 13, 2020 at 4:11 PM Wouter Verhelst wrote:
> >> You'll make it unnecessarily harder to bootstrap environments that need
> >> themselves to build if you do that.
>
> Paul> The idea
Hi,
Quoting Daniel Schepler (2020-01-17 17:58:09)
> > I'm also very excited about having yet another chroot backend being
> > integrated into sbuild! Though my first comment would be the same as I gave
> > those asking for a docker backend in #867176: maybe try adding that backend
> > to
Quoting Marvin Renich (2020-03-11 13:43:50)
> - policy-rc.d requires manually writing a shell script (a trivial
> one-liner for the "block all" case).
Not quite. From the first answer to OP's original question by Jonas:
Quoting Jonas Smedegaard (2020-03-07 22:36:44)
> Are you familiar with
Hi,
Quoting Russ Allbery (2020-03-25 03:25:49)
> Michael Lustfield writes:
> > One last thing to consider... NEW reviews are already an intense process.
> > If this package hit NEW /and/ we allowed vendored libs, you could safely
> > expect me to never complete that particular review. I doubt
Quoting Andrej Shadura (2020-03-26 22:24:41)
> On Thu, 26 Mar 2020 at 21:01, Russ Allbery wrote:
> > > An example: commercial users. They need to know *exactly* what they
> > > are running and under which licenses. They often want to be holier not
> > > only than the Pope, but holier than the
Hi,
Quoting Paul Wise (2020-03-30 10:20:08)
> On Mon, Mar 30, 2020 at 7:53 AM Shengjing Zhu wrote:
> > 1. There's no info loss if you convert from one to another.
> You definitely lose the (presumably non-free) television/game characters when
> converting from the original QR codes to plain text.
Hi,
Quoting Emilio Pozuelo Monfort (2020-03-30 13:24:01)
> We've just finished the transition to python3.8 as the default python3
> interpreter, which was a bit difficult due to some autopkgtest regressions in
> a few rdeps, and to the fact that many modules only build their extensions
> for the
Quoting Bernd Zeimetz (2020-04-26 20:34:12)
> On 4/26/20 12:41 AM, Thomas Goirand wrote:
> > On 4/25/20 11:14 PM, Bernd Zeimetz wrote:
> >> Actually I think 2FA should be enforced for everybody.
> >> Even debian.org related passwords might get lost.
> > I use strong password, stored with
Quoting Andreas Henriksson (2020-04-29 12:11:32)
> On Wed, Apr 29, 2020 at 11:58:53AM +0200, Jeff wrote:
> > Hi Simon,
> >
> > I don't understand why gscan2pdf is in the list, as the versions in
> > stable, testing and unstable are Perl packages which use libgtk3-perl.
> >
> > Can you explain?
>
Hi,
Quoting Mo Zhou (2020-03-20 16:07:04)
> That said, I agree that we move a step further considering a slim base system
> in a more constructive way. Spontaneously, I'd raise such a question: Is the
> changelogs the only files to blame for the waste of precious space? Some
> packages contains
Hi,
Quoting Marc Haber (2020-03-22 12:20:37)
> On Fri, 20 Mar 2020 10:16:00 +0100, David Kalnischkies
> wrote:
> >On Fri, Mar 20, 2020 at 12:50:29AM +0100, Adam Borowski wrote:
> >> In the rush for cutting away small bits of minbase, it looks like we forgot
> >> a big pile of junk:
Quoting Lucas Nussbaum (2020-03-23 07:44:50)
> However, in several cases, it seems that the problem is that sbuild does not
> install packages in Build-Depends-Indep when doing a source-only build, and
> then fails when doing 'debian/rules clean'. I wonder if that should be fixed
> in sbuild.
Hi,
Quoting Tomas Pospisek (2020-09-03 10:47:06)
> I think before jumping on this offer, one should consider this:
> https://www.aspi.org.au/report/uyghurs-sale
I think this is an important aspect to consider. Thanks a lot for bringing it
up!
Just as when we buy clothing or food, we often do
Hi Rebecca,
Quoting Rebecca N. Palmer (2020-05-25 10:57:02)
> The problem isn't the number of packages, but some specific packages
> that can't be displayed even when they are the only package requested:
> https://udd.debian.org/dmd/?email1node-file-entry-cache==html#todo
>
> These packages
Hi all,
Quoting Johannes Schauer (2020-05-25 14:00:45)
> Quoting Rebecca N. Palmer (2020-05-25 10:57:02)
> > The problem isn't the number of packages, but some specific packages
> > that can't be displayed even when they are the only package requested:
> > https://udd.d
Quoting Hideki Yamane (2020-05-26 15:48:47)
> Hi,
>
> autopkgtest on salsa-ci question, I've built mecab package and test
> it with autopkgtest on local machine. Then pushed to salsa, however,
> it failed on salsa-ci pipeline at autopkgtest.
> https://salsa.debian.org/nlp-ja-team/mecab/-/jobs
Hi,
Quoting Steffen Möller (2020-07-04 13:24:36)
> I just skimmed through https://trends.debian.net/ and am impressed. Many
> thanks for these figures.
same from me! :)
> Do you accept wishes for additional graphs? Mine would be on the number of
> build dependencies as a scale for software
Hi,
Quoting Benjamin Drung (2020-06-11 10:52:43)
> > > bdebstrap is an alternative to debootstrap and a wrapper around
> > > mmdebstrap to support YAML based configuration files. It inherits
> > > all
> > > benefits from mmdebstrap. The support for configuration allows
> > > storing
> > > all
Hi,
Quoting Christian Kastner (2020-07-16 14:08:34)
> On 2020-07-16 12:53, Pirate Praveen wrote:
> >> Generally speaking, I think it's a mistake to apply the question of
> >> "preferred form for modification" to unit test payloads. Unit tests are
> >> purely about functionality. The original
Quoting mat...@debian.org (2020-07-21 11:35:30)
> On Tue, Jul 21, 2020 at 11:11:13AM +0200, Wouter Verhelst wrote:
> > The reason we don't do this is because of bootstrapping: some tools
> > require themselves to build, so you need to cross-build them on a
> > different architecture, upload the
Hi,
Quoting Raphael Hertzog (2020-11-29 15:24:01)
> On Sun, 29 Nov 2020, Johannes Schauer Marin Rodrigues wrote:
> > The resulting tarball can then be used with the sbuild unshare backend. The
> > only time you need be root is to execute
> >
>
Hi,
Quoting Andrej Shadura (2020-11-10 10:27:44)
> On Tue, 10 Nov 2020, at 08:28, Paul Wise wrote:
> > > The current proposal is to reduce the main Packages.xz files size by
> > > splitting[4] out all of the packages that are not intended for users,
> > > writing those into an own file. Those
Hi,
Quoting RhineDevil (2020-11-29 20:33:22)
> A little proof of concept of what I'm aiming to is in the latest commits of
> https://salsa.debian.org/TanyaEleventhGoddess/sbuild, sbuild-createschroot is
> able to work with the commands as-is, but also features automatic detection
> of a possible
Hi,
Quoting Raphaël Hertzog (2020-11-29 11:42:16)
> I know that multiple developers started using podman and buildah to manage
> containers where they build their Debian packages. With user namespace
> supports, this allows rootless building (like the "unshare" chroot
> mode)... you don't even
Hi,
Quoting Russ Allbery (2020-12-14 23:54:37)
> > The point I'm making is that i386 processors are still incredibly common,
> > and we shouldn't abandon their users.
>
> Not abandoning users is a powerful motivating force, but it still has to
> succeed in motivating people. Debian can't make a
Hi,
Quoting Jonas Smedegaard (2021-01-27 16:15:17)
> I suspect that's not really the case - that instead apt tools might pick at
> random.
no, apt does not pick at random. The apt solver prefers the first alternative.
> It is my understanding that build daemons _ignore_ secondary entries
>
Quoting Helmut Grohne (2021-07-09 14:24:01)
> Another possibility (kudos to David Kalnischkies) would be exploiting
> something I might call a loophole in the Multi-Arch spec. While we don't
> currently use arch-qualified dependencies in the archive, the spec considers
> them and dpkg and apt
Hi,
Quoting Julian Gilbey (2021-02-10 22:51:39)
> I wonder if anyone has an idea about this thorny problem. I'm trying
> to create a package and thought I'd got something wrong, but have
> found the same behaviour happens with the "amp" package (version
> 0.6.1-1) and the "spherepack" package
Quoting Sebastian Ramacher (2021-02-11 10:00:42)
> > > A workaround for this problem is indeed to add
> > >
> > > --chroot-setup-commands="chmod 777 /dev/shm"
> > >
> > > to your sbuild invocation. A cursory glance into the pbuilder codebase
> > > reveals
> > > that pbuilder will mount a tmpfs
Hi Otto,
Quoting Otto Kekäläinen (2021-03-24 17:37:46)
> I've noticed I've spent quite a lot of time debugging various situations
> where the debian/control definitions for
> depends/breaks/replaces/conflicts/provides are not optimal.
>
> The waste of time is two-fold:
>
> 1) apt is not verbose
Quoting Simon McVittie (2021-04-04 13:55:21)
> On Sun, 04 Apr 2021 at 13:23:14 +0200, Joerg Jaspert wrote:
> > On 16093 March 1977, Dominik George wrote:
> > > That surprised me. If a package is free software, in ful laccordance
> > > with the DFSG, why is it put into contrib?
> >
> > There is,
Hi Norbert,
Quoting Norbert Preining (2021-03-17 03:55:53)
> in the Qt/KDE Team we use a script for test-building our groups of packages.
> Those groups need to be build in tiers (levels) so that later packages have
> access to the build of earlier levels. The script we currently use is based
>
Quoting Steinar H. Gunderson (2021-02-27 13:46:27)
> On Sat, Feb 27, 2021 at 12:29:34PM +, Thaddeus H. Black wrote:
> > I would prefer Kurt's option. Network silence is important. Network
> > noise would probably be a bug. A sysadmin should not be made to take
> > special precautions to
Quoting Ian Campbell (2021-02-24 18:50:39)
> What are the security implications for users/clients of using this or more
> importantly enabling it by default?
>
> Presumably clients have to trust that the server is not going to feed
> them malicious debug info. Are the tools which consume this
Quoting Andrej Shadura (2020-11-10 10:27:44)
> On Tue, 10 Nov 2020, at 08:28, Paul Wise wrote:
> > > The current proposal is to reduce the main Packages.xz files size by
> > > splitting[4] out all of the packages that are not intended for users,
> > > writing those into an own file. Those packages
Quoting Tim Woodall (2021-02-21 20:07:17)
> What I'm trying to do is build in a fakechroot. My idea was to unpack the
> core packages, fakeroot fakechroot chroot image apt-get install apt and have
> a base system to install build-deps etc.
>
> However, apt does not configure packages in the
Hi,
Quoting Tim Woodall (2021-02-21 18:22:19)
> base-passwd is marked as Essential: yes
>
> However, it actually creates the initial passwd and group files in the preinst
> script.
this reminds me of:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963788
Would this problem not also be
Quoting Sean Whitton (2021-08-18 22:21:15)
> On Wed 18 Aug 2021 at 11:10AM +02, Aurelien Jarno wrote:
>
> >> 9.1.1
> >> No package is allowed to install files in ``/usr/lib64/``. Previously,
> >> this prohibition only applied to packages for 64-bit architectures.
> >
> > This path is used
Quoting Jeremy Stanley (2021-08-20 18:34:22)
> > If so, I think the next step would be to open a bug with a summary of this
> > discussion. I'm happy to do that, but I'm not sure what package owns this
> > configuration.
> It's not owned directly by a particular package, I think D-I and various
>
Hi,
Quoting Mattia Rizzolo (2021-09-06 16:39:39)
> As the pbuilder maintainer, I've been asked to make it serve a non-working
> /etc/resolv.conf just to make that bug above moot, so I'm quite biased on the
> matter myself :)
sbuild already disables network access for all chroot backends that
Quoting Mattia Rizzolo (2021-09-14 15:34:36)
> On Tue, Sep 14, 2021 at 10:05:01AM +0200, Johannes Schauer Marin Rodrigues
> wrote:
> > Hi,
> >
> > Quoting Mattia Rizzolo (2021-09-06 16:39:39)
> > > As the pbuilder maintainer, I've been asked to make it serve a n
Hi,
On Thu, 23 Sep 2021 16:29:27 +0800 clay stan wrote:
> Package: wnpp
> Severity: wishlist
> Owner: clay stan
> X-Debbugs-Cc: debian-devel@lists.debian.org
>
> * Package name: dirsearch
> Version : 0.4.2
> Upstream Author : maurosoria
> * URL :
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org, jo...@debian.org
* Package name: wayvnc
Version : 0.4.1
Upstream Author : Andri Yngvason
* URL : https://github.com/any1/wayvnc
* License
Quoting Richard Laager (2021-11-10 20:16:31)
> Can we just enable LINENO in dash then, let the other packages FTBFS, and
> people who care about the packages that FTBFS can either:
in the best case, a package will FTBFS but it can also happen that the
configure script will just do something
Quoting Russ Allbery (2021-11-20 18:22:27)
> * Create a new essential package that contains these symlinks and that
> needs to be unpacked before any binaries are executed in the target file
> system. This has many of the advantages and drawbacks of the approach
> of putting the symlinks in
Hi Muhammad,
others already explained how packaging VCS are (sadly) basically a free-for-all
in Debian and that you will probably not get anything better than some
heuristics. I wanted to add some more ideas to the ones that were already
presented. So in addition to what was already said you can
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org, jo...@debian.org
* Package name: openstreetmap-carto
Version : 5.4.0
Upstream Author : Andy Allan
* URL : https://github.com/gravitystorm
Quoting Tobias Frost (2021-11-18 10:38:40)
> (speculatinng on the why you want it rejected: if you want to replace it with
> e.g. a newer version, you can just upload the new version)
slightly related question: if I upload a new version to NEW, will the Age of
the package be reset? I'm asking
Hi,
Quoting Uladzimir Bely (2021-10-28 10:58:26)
> When building a package with sbuild, some packages (dependencies of package
> being built) are internally downloaded and installed by apt. After the build
> finished, schroot is cleaned again (while everything is done in overlay)
>
> I need to
Hi Felix,
Quoting Felix Lechner (2021-11-04 20:25:28)
> On Thu, Nov 4, 2021 at 2:35 AM Johannes Schauer Marin Rodrigues
> wrote:
> > it seems the only tool that calls :any an "acceptor" is lintian
>
> I think the multiarch spec is confusing because of its termi
Quoting Felix Lechner (2021-11-04 20:17:49)
> For anyone having issues with Gitea's new dynamic download links [1] here is
> a debian/watch file that works.
>
> * * *
>
> version=4
> opts=\
> downloadurlmangle=s/\/releases\/tag\/(\d\S+)$/\/archive\/$1\.tar\.gz/,\
>
Hi,
Quoting Felix Lechner (2021-11-03 23:34:17)
> For a brief time between October 1 and October 15, Lintian gave potentially
> confusing advice on some build prerequisites. [1]
>
> The :any multiarch acceptor—a rarely used feature some other tools call the
> "muliarch qualifier"—
it seems the
Quoting Michael Biebl (2021-07-19 15:10:42)
> Am 19.07.21 um 03:36 schrieb Guillem Jover:
> > What I've also said multiple times, is that
> > merged-usr-via-moves-and-symlink-farms could have been implemented in
> > a fully automated way, by debhelper, w/o requiring any maintainer scripts,
> > all
Hi Adrian,
Quoting Adrian Bunk (2022-03-07 22:42:42)
> On Sun, Mar 06, 2022 at 09:25:45PM +0100, Lucas Nussbaum wrote:
> >...
> > I think that we should reduce the number of packages using the 1.0 format,
> > as
> > (1) format 3.0 has many advantages, as documented in
> >
Quoting Andreas Tille (2022-02-25 09:22:38)
> I had to decide between a "proper NMU" and an "upload that fits the packaging
> standards I apply to what I upload" (which includes maintained on Salsa,
> usage of dh, DEP5 copyright ... basically removing the smell from the
> package). I decided for
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org, jo...@debian.org
* Package name: debianutils-tempfile
Version : 4.11
Upstream Author : Johannes Schauer Marin Rodrigues
* URL : https
Hi,
Quoting Bill Allombert (2023-09-10 18:29:36)
> On Sun, Sep 10, 2023 at 09:00:22AM -0700, Russ Allbery wrote:
> > Jonas Smedegaard writes:
> > > Quoting Hideki Yamane (2023-09-10 11:00:07)
> > >> Hmm, how about providing license-common package and that depends on
> > >>
Hi,
Quoting Thomas Goirand (2023-09-19 09:50:45)
> I'm not sure if we should switch to zstd, or if xz will do the work, though
> I'd be delighted if the dpkg performances could be improved. I'm spending all
> of my days installing server, sometimes with 1.5 TB of RAM and 128 core (AMD
> Epyc...),
Hi,
Quoting Helmut Grohne (2023-09-23 20:18:21)
> Quoting Ian Jackson (2023-09-23 12:19:27)
> > To summarise that discussion: at that time the best available solution that
> > worked in ci.d.n seemed to be to write an ad-hoc script to run the tests in
> > qemu; three packes had done that, each
Hi Gard,
Quoting Gard Spreemann (2023-09-20 09:26:58)
> Paul Wise writes:
> > […] since the Rust packages are basically only used as build-deps and
> > therefore have no human users.
> I just wanted to raise awareness that some of us humans do use librust-*-dev
> packages directly, having put
Hi,
Quoting David Bremner (2023-09-28 16:40:13)
> Bastian Germann writes:
> > Source: nunit
> >
> > I intend to salvage nunit with the plan to orphan it in three weeks.
> > Please notify me if you object.
>
> In my opinion, your repeated "salvaging" of packages in order to orphan
> them is an
Hi,
Quoting Jonathan Kamens (2023-09-26 15:20:49)
> I'm trying to use sbuild to build my package, and it's failing to find
> piuparts:
>
> | Post Build
> |
>
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: reform-firedecor
Version :
Upstream Contact: Lukas F. Hartmann
* URL : https://github.com/mntmn/Firedecor
* License : Expat
Hi,
Quoting Gioele Barabucci (2023-10-15 17:59:32)
> On 15/10/23 17:33, Iustin Pop wrote:
> > At least you're not lazy. I am, so what I did many times is add a
> > build-depends on pandoc, and write the man page in rst or md. I think
> > that's a worse solution (pandoc is really heavy), but at
Hi,
Quoting John Goerzen (2023-08-13 23:32:03)
> On Sat, Aug 05 2023, Lucas Nussbaum wrote:
> > I wonder what we should do, because 5000+ failing packages is a lot...
> Let's think about the level of trouble we cause trying to tackle something
> that has clearly not bothered anyone for years.
Hi,
Quoting Dima Kogan (2023-08-13 22:54:48)
> I'm looking for a suggestion to fix a problem.
>
> I uploaded a package, and it cleared NEW a few days ago. I now see that
> it fails to build on most 32-bit arches becaues the compiler runs out of
> memory.
I ran into the same problem with my
Quoting Scott Talbert (2022-06-15 22:30:13)
> Is it possible to instruct the buildds to use a build profile when performing
> an official build (e.g., using nocheck to break a dependency loop)? If so,
> how?
No, it is not. Main reason is probably that nobody has found the time to
implement it
Quoting Steve McIntyre (2022-07-14 13:54:52)
> And I see you uploaded ~immediately - why even bother with an ITP?
I did that quite a few times in the past as well. Is there a rule of how long I
have to wait with my upload to NEW after filing the ITP?
signature.asc
Description: signature
Hi,
Quoting Andreas Tille (2022-03-21 11:55:09)
> Am Sat, Mar 19, 2022 at 08:37:28PM +0100 schrieb Erik Schanze:
> > Am 16.03.22 um 14:11 schrieb Andreas Tille:
> > > was not uploaded by its maintainer for >10 years.
> >
> > Yes, because upstream development was finished and packaging was
Quoting Thomas Goirand (2022-05-11 17:14:57)
> > For backwards compatibility, I think that the firmware component is
> > going to need to be a subset of non-free; i.e. packages are going to
> > need to be *copied* not moved from non-free to the firmware component,
> > which means they would be
Quoting Simon McVittie (2022-04-29 10:58:34)
> On Fri, 29 Apr 2022 at 08:34:48 +0100, Julian Gilbey wrote:
> > So can I suggest that
> > sbuild-setup(7) explains this a bit more and discusses setting up a
> > meaningful HOME directory?
>
> I'm sure patches are accepted, but the problem with this
Quoting Hakan Bayındır (2022-08-19 17:47:42)
> I’d object that, because after we rotate the logs, we use a lot of z
> commands, namely zcat, zgrep, zless. Which allows us process many gigabytes
> of gzip files without extracting them first.
>
> We have a big cluster at office and a central
Hi Paul,
Quoting Paul Gevers (2022-09-01 13:53:41)
> I am asking for help with investigating RC bug reports, judging
> severity, reproducing the issue, clarifying the problem, i.e. bug
> triaging of all RC bugs that haven't seen activity for a while and that
> are still affecting bookworm. Of
Quoting Andrej Shadura (2022-10-20 12:25:13)
> I’ve been rebuilding packages with pkgconf for the past couple of weeks, and
> it looks very good so far:
>
> http://pkgconf-migration.debian.net/
Thank you! Attached is a dd-list of those packages listed in the "Failures
only" page in case somebody
Quoting Andreas Henriksson (2022-10-20 12:13:24)
> Hello Debora Babb,
>
> On Wed, Oct 19, 2022 at 11:04:35PM -0700, Debora Velarde Babb wrote:
> > Greetings,
> >
> > The upstream package for tss2 has been renamed ibmtss. When the name
> > was changed upstream, the version number convention also
Quoting Philipp Kern (2022-10-20 14:29:13)
> On 20.10.22 13:40, Johannes Schauer Marin Rodrigues wrote:
> > Quoting Andreas Henriksson (2022-10-20 12:13:24)
> >> Cannot be used for packages that are used in build dependencies, as several
> >> build tools (like sbu
Hi Debora,
Quoting Debora Velarde Babb (2022-10-20 08:04:35)
> The upstream package for tss2 has been renamed ibmtss. When the name was
> changed upstream, the version number convention also changed. Upstream
> tss2-1470 was updated to ibmtss-1.3.0. The current version of ibmtss is now
>
Hi,
Quoting David Bremner (2022-10-22 18:16:12)
> Aurelien Jarno writes:
> > We lost access to the Power9 machine hosted at Unicamp, which was
> > hosting the ppc64el porterbox called plummer.d.o. A new porterbox called
> > platti.d.o has been setup as a replacement.
>
> It would be nifty if
Hi Russ,
Quoting Russ Allbery (2022-09-20 00:05:23)
> Johannes Schauer Marin Rodrigues writes:
> > in 2016 we filed our first DPKG_ROOT patch #824594 against
> > base-files. The dpkg version at the time just had included support for
> > the DPKG_ROOT variable being set f
Hi Roland,
Quoting Roland Clobus (2022-09-18 10:58:37)
> I'm looking for 'the' timestamp of the Debian Archive, which will allow me to
> virtually travel through time to re-generate a specific state of Debian.
Holger just suggested on IRC that I reply to your mail -- probably with my
Hi,
in 2016 we filed our first DPKG_ROOT patch #824594 against base-files. The dpkg
version at the time just had included support for the DPKG_ROOT variable being
set for maintainer scripts and we were excited to try out this new feature for
creating foreign architecture chroots. At the time we
Hi,
Quoting Josh Triplett (2022-09-11 15:26:52)
> Johannes Schauer Marin Rodrigues wrote:
> > What do you think? Is this the right solution to the problem? A few more
> > bits
> > about DPKG_ROOT as well as alternative solution proposals (including
> > reje
Hi,
Quoting Josh Triplett (2022-09-11 15:26:52)
> Johannes Schauer Marin Rodrigues wrote:
> > What do you think? Is this the right solution to the problem? A few more
> > bits
> > about DPKG_ROOT as well as alternative solution proposals (including
> > reje
401 - 500 of 581 matches
Mail list logo
