Hi,
Quoting Adam D. Barratt (2024-04-28 01:09:28)
> > Seeing mirror functionality being uncertain, I have started to track
> > archive.debian.org as a Git-LFS repository on gitlab.com.
> Please don't. If there's a problem with debian.org services then we should
> fix that, not start adding more
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: autotiling
Version : 1.9.1
Upstream Contact: Piotr Miller
* URL : https://github.com/nwg-piotr/autotiling/
* License : GPL-3
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: pico-sdk
Version : 1.5.1
Upstream Contact: https://github.com/raspberrypi/pico-sdk/issues
* URL : https://github.com/raspberrypi/pico
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: picotool
Version : 1.1.2
Upstream Contact: Graham Sanderson
* URL : https://github.com/raspberrypi/picotool/
* License : BSD-3
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: tinyusb
Version : 0.16.0
Upstream Contact: Ha Thach
* URL : https://www.tinyusb.org/
* License : Expat
Programming Lang: C
Quoting Andreas Tille (2024-04-10 22:44:25)
> > I do understand the argument that lots of different workflows adds
> > friction. But I'm just still using what used to be _the_ standard one
> > (insofar as we ever had such a thing). Putting everything in salsa/git
> > doesn't standardise workflows
Hi Wookey and all,
Quoting Wookey (2024-04-09 18:52:43)
> On 2024-04-08 21:44 +0900, Simon Richter wrote:
> > Testing a package requires me to commit everything into git first, so I
> > have to remember to squash all these commits later.
> Right - this was (one of the) main thing(s) that annoyed
Quoting Bill Allombert (2024-04-08 23:49:05)
> Le Sun, Apr 07, 2024 at 11:37:47PM +0200, Gioele Barabucci a écrit :
> > On 07/04/24 23:11, Bill Allombert wrote:
> > > > What is your opinion about pushing logtool to Salsa?
> > >
> > > Not speaking for logtool obviously, but maintaining simple
Hi,
Quoting Wookey (2024-04-07 22:42:34)
> On 2024-04-07 16:04 +0200, Andreas Tille wrote:
> > Am Sun, Apr 07, 2024 at 03:31:43PM +0200 schrieb Wouter Verhelst:
> > > [Feel free to quote any part of this email which I wrote outside of this
> > > mailinglist]
> > OK, moving the discussion to
Hi,
Quoting Andrey Rakhmatullin (2024-04-01 09:58:21)
> On Mon, Apr 01, 2024 at 01:03:04PM +1000, Russell Stuart wrote:
> > On 1/4/24 10:18, gregor herrmann wrote:
> > > % dpkg -S $(which mv > coreutils: /usr/bin/mv
> >
> > On bookworm:
> >
> > $ dpkg -S $(which mv)
> > dpkg-query: no
Hi,
Quoting Christian Kastner (2024-03-30 19:49:48)
> On 2024-03-30 17:00, Marco d'Itri wrote:
> > On Mar 30, Jonathan Carter wrote:
> >
> >> Another big question for me is whether I should really still
> >> package/upload/etc from an unstable machine. It seems that it may be
> >> prudent
> >
Quoting Samuel Thibault (2024-03-24 18:20:30)
> - making sure that the Debian release eventually only contains non-profile
> builds should be relatively easy thanks to the buildinfo files (they
> currently only contain them in the DEB_BUILD_PROFILES environment variable,
> they could be added as
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: tuigreet
Version : 0.8.0
Upstream Contact: Antoine POPINEAU
* URL : https://github.com/apognu/tuigreet/
* License : GPL-3.0
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: reform-setup-wizard
Version : 0.1.0
Upstream Contact: Lukas F. Hartmann
* URL : https://source.mnt.re/reform/mnt-reform-setup-wizard
Hi,
Quoting David Bremner (2024-03-01 14:09:36)
> Nilesh Patra writes:
> > When I want to fix autopkgtests for a package on a particular architecture,
> > I currently see no way to run autopkgtests before I dput since porter boxes
> > do not provide root access which autopkgtest needs.
> >
> >
Hi,
Quoting Julian Andres Klode (2024-02-28 20:20:12)
> APT 2.7.13 just landed in unstable and with GnuPG 2.4.5 installed,
> or 2.4.4 with a backport from the 2.4 branch, requires repositories
> to be signed using one of
>
> - RSA keys of at least 2048 bit
> - Ed25519
> - Ed448
>
> Any other
Hi,
Quoting John Paul Adrian Glaubitz (2024-02-13 00:33:03)
> (Please CC me in replies as I'm not subscribed to debian-devel)
then maybe you have missed the last time this topic came up:
https://lists.debian.org/169097599149.3513878.11315997455981479167@localhost
> does anyone know whether
Hi,
Quoting Loren M. Lang (2024-02-01 04:08:59)
> I have a package
which package is that?
> which has an extensive test suite that relies on using docker/podman to
> create a container for it's test runner and mounts the build tree read-only
> inside it.
Why does it need docker/podman
Hi Otto,
Quoting Otto Kekäläinen (2024-01-29 07:06:51)
> > > It would be nice though if the version in Debian was newer :)
> >
> > I probably won't update it until it is suitable for inclusion in a
> > stable release. This means at minimum being relatively safe to run in
> > an untrusted source
Hi,
Quoting Luca Boccassi (2024-01-24 12:59:38)
> There's always option B: recognize that the Rust/Go ecosystems are not
> designed to be compatible with the Linux distributions model, and are instead
> designed to be as convenient as possible for a _single_ application developer
> and its users
Hi,
On 2024-01-18 00:38, Simon McVittie wrote:
On Wed, 17 Jan 2024 at 23:15:03 +0100, Matthias Geiger wrote:
Am 17.01.24 um 23:00 schrieb Simon McVittie:
> Public GIR XML (Foo-1.gir) is normally in the -dev package alongside the
> C headers, but recent versions of gobject-introspection define
Hi,
Quoting Ansgar (2024-01-07 20:39:57)
> I would like to extend Debian Policy on libraries depending on services
> (daemons) that they can speak to.
>
> Let me bring to examples, one made up,, one for which I filed a bug
> recently. But as far as I can tell this question comes up from time to
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 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
> |
>
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 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 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 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
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 Simon McVittie (2023-08-06 12:27:04)
> On Sat, 05 Aug 2023 at 21:29:08 +0200, Andrey Rakhmatullin wrote:
> > I expect all Python packages that ship
> > $name.egg-info and don't remove it in clean and don't exclude it via
> > extend-diff-ignore (all of which is unneeded busywork even
Hi,
Quoting Guillem Jover (2023-08-09 20:55:17)
> On Wed, 2023-08-09 at 19:55:41 +0200, Johannes Schauer Marin Rodrigues wrote:
> > I would only consider switching the default if at the same time, some checks
> > were done that made sure that the result is bit-by-bit identical to t
Hi,
Quoting Stefano Rivera (2023-08-09 14:38:56)
> Personally, I have my sbuild configured to build a source package after the
> build, so that I can be sure that I don't regress my own packages' clean
> target. It would be nice if this was a default feature in sbuild, for most
> packages this is
Hi,
Quoting Benjamin Drung (2023-08-07 20:43:36)
> while working a whole week on fixing failing C/C++ header compilations for
> armhf time_t [1], I noticed a common pattern: The library -dev packages was
> missing one or more dependencies on another -dev package. Over 200 -dev
> packages are
Quoting Timo Röhling (2023-08-05 21:07:34)
> * Lucas Nussbaum [2023-08-05 17:06]:
> >An example sbuild invocation to reproduce failures is:
> [omitted the command line equivalent of Tolstoy's War and Peace]
>
> If we decide that this issue is important enough that people should
> care and mass
Hi,
snapshot.debian.org is getting worse again. There is not a single snapshot for
August yet and the last days of July are spotty:
http://snapshot.debian.org/archive/debian/?year=2023=7
None for the 29. and only a single timestamp for the 26., 27., 28. and 30.
There should be four per day. The
Hi,
Quoting Michael Biebl (2023-07-25 16:16:35)
> apparently, we in Debian struggle to find good opportunities where to spend
> our money.
>
> I think support for qemu runners, i.e. supporting isolation-machine in
> autopkgtest on both debci and salsa ci would be an excellent opportunity.
is
Quoting Simon McVittie (2023-07-17 12:10:52)
> On Mon, 17 Jul 2023 at 08:57:51 +, Holger Levsen wrote:
> > On Sun, Jul 16, 2023 at 11:41:36AM +0100, Simon McVittie wrote:
> > > On Sun, 16 Jul 2023 at 00:03:00 +0200, Adam Borowski wrote:
> > > > due to Build-Depends
> > > > being inadequate
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
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-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
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 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.
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
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
Quoting Helmut Grohne (2023-02-24 08:27:53)
> shellcheck:
> * grml-debootstrap
not run with DEB_BUILD_OPTIONS=nocheck
https://sources.debian.org/src/grml-debootstrap/0.103/debian/rules/?hl=13#L13
> * josm-installer
not run with DEB_BUILD_OPTIONS=nocheck
Quoting Helmut Grohne (2023-02-24 07:19:41)
> As such, I propose a generic DEB_BUILD_OPTIONS=nowerror modelled after the
> original observation, but meant to also match other checkers such as
> shellcheck. The general idea should be that a warning should that can be
> non-fatal should be non-fatal
Quoting Santiago Vila (2023-02-10 11:12:09)
> El 10/2/23 a las 3:18, Johannes Schauer Marin Rodrigues escribió:
> > I do not understand what makes you think that only packages using
> > dh_fixperms
> > -X are affected? I think what makes the two packages that I found fail to
Hi,
Quoting Santiago Vila (2023-02-09 17:32:08)
> El 9/2/23 a las 15:37, Johannes Schauer Marin Rodrigues escribió:
> > I wanted to bring fakeroot bugs #1023286 and #1030638 to the attention of a
> > wider audience because even though I filed these bugs,
>
> Thanks for bring
Hi,
I wanted to bring fakeroot bugs #1023286 and #1030638 to the attention of a
wider audience because even though I filed these bugs, I do not see myself
finding the time to track down and correct their consequence for all the source
package builds that happened since their introduction with the
Hi,
Quoting Stéphane Glondu (2023-02-07 16:41:47)
> When building packages, a -ffile-prefix-map option is automatically injected
> into CFLAGS. Where does it come from? Since when?
probably due to
Quoting Ansgar (2023-01-28 14:41:31)
> Johannes Schauer Marin Rodrigues writes:
> > I think the much more interesting question is in what environment we want to
> > build our packages in. Currently, on buildds, we build them in a chroot that
> > has Priority:required and bu
Quoting Holger Levsen (2023-01-28 14:53:37)
> On Sat, Jan 28, 2023 at 02:28:30PM +0100, Johannes Schauer Marin Rodrigues
> wrote:
> > could we decouple the policy and bug severity question from the question of
> > what a buildd chroot should contain, please?
> [...]
> &
Quoting Timo Röhling (2023-01-28 13:30:42)
> Hi Andreas,
>
> * Andreas Henriksson [2023-01-28 12:50]:
> >Policy is not a religion. Policy has many bugs. Policy is very outdated.
> >[...]
> >Here's an example you could follow:
> >https://lists.debian.org/debian-policy/2022/12/msg00023.html
> Your
Quoting Ian Jackson (2023-01-07 16:35:17)
> Thanks. I considered this but it seemed overkill
maybe
> (and it won't inherit the dependency versions selected by autopkgtest).
Yes it will. When creating the chroot for the virtual machine, you use the apt
sources configured by the autopkgtest
Hi,
Quoting Ian Jackson (2023-01-06 17:59:58)
> This all seems very complex. I definitely want to have something working
> before something like that could exist. Also, I think it would be a good
> idea to do something ad-hoc, ideally in a number of packages, to gain
> experience so we know
Quoting Paul Gevers (2023-01-05 12:26:09)
> Once accepted, the proposed workflow should also become documented in Debian
> policy.
I think how transitions are done is not even documented in the dev-ref right
now, no?
Last time I was uploading a package for a transition I followed
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: box64
Version : 0.2.0
Upstream Contact: Sebastien Chevalier
* URL : https://github.com/ptitSeb/box64
* License : Expat
Hi,
Quoting Theodore Ts'o (2022-12-27 05:19:45)
> On Mon, Dec 26, 2022 at 08:45:53PM +0100, Santiago Vila wrote:
> > El 26/12/22 a las 20:29, Theodore Ts'o escribió:
> > > I: The directory does not exist inside the chroot.
> >
> > This is really a problem with schroot. I guess that this will not
Hi,
Quoting David Kalnischkies (2022-12-18 17:18:28)
> On Fri, Dec 16, 2022 at 03:38:17PM +0100, Santiago Vila wrote:
> > Then there is "e2fsprogs", which apt seems to treat as if it were
> > an essential package:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826587
>
> As Julian
Quoting Santiago Vila (2022-12-16 02:15:13)
> I've just filed 21 bugs with subject "Missing build-depends on tzdata"
> in bookworm (as tzdata is not build-essential).
thank you for that!
> I can think of two solutions for this:
>
> A) Either debootstrap, when using buildd profile, installs only
Quoting Niels Thykier (2022-12-15 10:59:10)
> Long story short:
>
> * Bug in fakeroot (#1023286 + #1024544)
> * Me thinking it was a bug in debhelper so I tried to fix it
> (which did not work and broke on the way in)
> * Me realizing it was a bug in fakeroot and my change did not
>
Quoting Zhang Ning (2022-11-03 11:45:17)
> 6, gcc, binutils: need help, I don't know how to submit a patch to Debian
> toolchain-team, don't accept a poll request.
>
> 7, m4, diffutils: need help, I don't know where is correct upstream[1][2],
> the patch[3][4] is for generated files, but Debian
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
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
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 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
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 Paul,
Quoting Paul Gevers (2022-10-13 17:25:36)
> On 13-10-2022 14:20, Johannes Schauer Marin Rodrigues wrote:
> > Quoting Paul Gevers (2022-10-13 10:00:42)
> >> Please also consider supporting the nodoc build profile. We are aware
> >> that nodoc is regularly use
Quoting Paul Gevers (2022-10-13 10:00:42)
> Please also consider supporting the nodoc build profile. We are aware
> that nodoc is regularly used in a non-reproducible way (as intended,
> but with this consequence), so checking for correctness of this
> profile may be a bit harder. Ideally, using
Quoting Bastian Blank (2022-10-09 10:24:26)
> On Sun, Oct 09, 2022 at 09:41:29AM +0200, Johannes Schauer Marin Rodrigues
> wrote:
> > This breaks a number of setups like:
> >
> > - the sbuild autopkgtest
> >https://salsa.debian.org/debian/sbuild/-/jobs/3
Hi,
the last upload of src:systemd (251.5-1) enabled firstboot by default on
Debian. From debian/changelog:
* Enable firstboot, disabled by default on Debian.
Currently the first-boot conditions are not met by any Debian
image (/etc/machine-id with content uninitialized, so we can
Hi,
Quoting Hideki Yamane (2022-10-07 03:39:39)
> On Thu, 6 Oct 2022 17:45:06 +0200 Michael Biebl wrote:
> > If you are using salsa, you can utilize all the features gitlab
> > provides. E.g. in src:systemd, we use
> >
Hi,
Quoting Lucas Nussbaum (2022-10-02 21:51:52)
> On 02/10/22 at 04:23 +0200, Adam Borowski wrote:
> > Nǐmen hǎo!
> > I did another _source_ rebuild of the archive -- checking if every package
> > is capable of repacking its source. Ie, if you can unpack it, (possibly
> > modify), and pack
Hi,
Quoting Paul Wise (2022-09-20 02:38:30)
> On Mon, 2022-09-19 at 20:50 +0900, Hideki Yamane wrote:
> > Recent changes in GitHub releases pages, I cannot check upstream
> > version with uscan. How do you deal with it?
>
> If you are using the automatically generated tarballs, then
> just
Quoting Roland Clobus (2022-09-21 22:03:33)
> As to the origin of my question: The snapshot-mirror has been offline for a
> while, and I've used deb.debian.org to generate my test images (for the
> reproducible live-build-based live-ISO images). I've compared the timestamps
> of the InRelease file
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,
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
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 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 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 Matthias,
no idea why you CC-ed debian-devel@lists.debian.org with your bug. This is a
bug about using Debian so the correct mailing list would be
debian-u...@lists.debian.org. The mailing list you chose is for the development
of Debian.
I'm closing this bug because what you experienced is
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
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 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
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 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
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
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 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
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
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
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
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
1 - 100 of 125 matches
Mail list logo
