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 for m
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,
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 switch
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 again
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
> > https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/git
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
j
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
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 th
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
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
> 1.6.0.
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,
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 som
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
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 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
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 exp
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
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
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
https://wiki.de
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 what
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 runne
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 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 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 build
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
https://git.hadrons.org/cgit/debian/dpkg/dpkg.git/commit/?id=b60c243ba99b8483202a6f6a814476275204fdf
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 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
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
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 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
https://sources.debian.org/src/josm-inst
Quoting Alexandru Mihail (2024-10-15 18:12:57)
> As of today, 15th of October, I can't install lintian on current Sid.
> sources.list: deb https://deb.debian.org/debian/ unstable main contrib
> non-free non-free-firmware. If I can help with an apt list --installed or
> something, let me know.
thi
Hi,
Quoting Mazen Neifer (2024-10-07 18:31:14)
> The package aiocoap is in bad shape and was asked to be removed.
>
> I would like to maintain it. Is there any objection?
there is a process for this:
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
Thanks!
Hi Feri,
Quoting Ferenc Wágner (2024-10-12 19:39:27)
> The third example on https://wiki.debian.org/BuildProfileSpec is:
>
> Build-Depends: foo
>
> In this case, the source package would build depend on foo if either
> both, nocheck and cross are active or if the profile nocheck is
Hi Timo,
Quoting Timo Röhling (2024-10-16 10:00:25)
> >> The third example on https://wiki.debian.org/BuildProfileSpec is:
> >I now changed the example to one that is actually used in the wild.
> >I hope I didn't mess up the wording. Hope this makes things
> >clearer.
> The final sentence in the
Hi,
Quoting Aaron Rainbolt (2024-11-06 00:35:59)
> According to the Debian Policy Manual, section 7.2, the Recommends field in
> Debian packages "declares a strong, but not absolute, dependency. The
> Recommends field should list packages that would be found together with this
> one in all but unu
Quoting Hans (2024-11-12 09:35:08)
> However, maybe a link is alo no more needed, even with a seperated /boot
> partition.
It's just a symlink. What's the harm?
Having the symlink is very practical for bootloaders that are not grub.
Pointing an extlinux.conf or a boot.scr to /vmlinuz instead of h
Hi Vincent,
Quoting Vincent Bernat (2024-09-21 14:55:36)
> I am using qemu-user-static to compile to ARM64 from AMD64. There is a
> long-time bug with recent versions of QEMU where you would get a segfault:
>
> https://gitlab.com/qemu-project/qemu/-/issues/1913
>
> I was using qemu-user-static_7
Hi,
in general, for any cross-building issues, please feel free to write to
debian-cr...@lists.debian.org
Quoting Iustin Pop (2024-09-27 16:23:16)
> I just added a barebone config for one of my packages, and while the pipeline
> worked, I got an error for the arm64 cross-compile that seems to be
Quoting Simon Josefsson (2024-11-22 12:18:36)
> > I like to read of other people's workflows but then I often do not see how
> > their workflows can possibly fit my packages. There seem to be many people
> > who have the upstream git as part of their packaging git. I'm happy that
> > works for them
Hi,
Quoting phil995511 - (2024-11-22 02:29:31)
> Only kernel 6.13 will support the new GPUs that will be released in early
> 2025, the new Intel CPUs, the same for a whole bunch of new hardware...
>
> To be satisfied with kernel 6.12 would in my opinion be a big strategic
> mistake jeopardizing c
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: reform-tools
Version : 1.63
Upstream Contact: Lukas F. Hartmann
* URL : https://source.mnt.re/reform/reform-tools/
* License
Hi,
Quoting Sean Whitton (2024-11-24 01:23:24)
> This is interesting. One concern I have is speed -- isn't it always slower
> to have to unpack a tarball before the build instead of having a chroot under
> /srv/chroot that's always unpacked?
that is correct. Unpacking a tarball takes time. Havin
Hi Soren,
Quoting Soren Stoutner (2024-11-26 20:21:55)
> > Setting this will override the Distribution of the .changes file created by
> > sbuild with "unstable", ignoring what your package has set. Are you sure
> > you want this?
>
> I would like it to be able to build instead of fail when the c
Quoting Marco d'Itri (2024-11-26 23:34:24)
> On Nov 26, Jonathan Dowland wrote:
> > On Tue Nov 26, 2024 at 10:50 AM GMT, Andrey Rakhmatullin wrote:
> > > Yes, as they don't enable pristine-tar
> > Is pristine-tar still valuable these days?
> Not really. The debian branches of all of my packages[1]
Hi,
Quoting Soren Stoutner (2024-11-26 01:07:06)
> I suppose I should note that I have made a few modifications to the example
> file because it wasn’t behaving as expected. Specifically, I disabled the
> mmdebstgrap auto create because otherwise it was ignoring the tarball I had
> created in the
Hi,
Quoting Simon Richter (2025-01-17 11:43:39)
> In my own packages, I check if libatomic exists, and if it does, I
> unconditionally link if I use any atomics. I also check if the linker accepts
> --push-flags, if it does I generate a
> -Wl,--push-flags,--as-needed,-latomic,--pop-flags sequence,
Hi,
Quoting Otto Kekäläinen (2024-11-19 07:34:45)
> I am contemplating if I should also make videos on Debian packaging best
> practices, or have start a new Matrix channel specifically to help
> maintainers setup their git repositories correctly and find the optimal
> git-buildpackage commands fo
Hi,
Quoting Otto Kekäläinen (2024-11-23 00:09:41)
> You can have upstream git and tarballs at the same time, and even have DFSG
> cleanup take place and git show you exactly the differences of all the
> versions.
I'm interested in the DFSG cleanup. How can this be done while having an
upstream gi
Quoting nick black (2024-11-23 08:48:10)
> You now have glyphs which occupy more than one column. Are your
> columnar/tabular programs prepared for that? ﷽𒁭𒐫i
xfce-terminal renders this like this: https://mister-muffin.de/p/4o2v.png
No idea if this is correct and I'll leave the details to those w
Quoting Simon Josefsson (2024-11-22 12:54:02)
> Doesn't 'gbp import-orig --uscan' work if you have a watch-file like this:
>
> version=4
> opts="mode=git, pgpmode=none,\
> dversionmangle=s/\+ds\d*$//,repacksuffix=+ds" \
> https://github.com/withfig/autocomplete-tools.git \
> HEAD debian
Quoting Chris Hofstaedtler (2024-11-23 17:50:25)
> * Fabian Grünbichler [241123 15:31]:
> > A) move i386 rustc to Rust's i586 target (which doesn't have SSE out of the
> > box), instead of the i686-with-SSE2-disabled it currently uses
> > B) bump the i386 baseline in Debian to require SSE2, and s
Hi,
Quoting Gioele Barabucci (2025-01-24 09:49:27)
> > I disagree with this conclusion. Sometimes features are extensively
> > discussed in salsa merge requests or issues, and the entire discussion just
> > can't be summarized in a git commit message (and it is not desirable to
> > even attempt th
Quoting IOhannes m zmölnig (Debian GNU|Linux) (2025-01-27 12:27:12)
> On 1/26/25 01:10, gregor herrmann wrote:
> > Yes, and more importantly:
> >> - because it is not easy and fast to migrate and if you do it you have to
> >> redo the local repository, if you are alone working on the repository it
Quoting Thorsten Glaser (2025-01-15 00:50:55)
> There should be something in this that says that they need to do so in a way
> that matches ftpmaster policies.
Do we really need to explicitly codify "please work well together with your
fellow DDs" in the task description of delegates?
I think tha
Quoting Chris Knadle (2025-01-16 19:26:39)
> Looking at the manpage for dpkg-architecture, the variable I may want to
> conditionally build upon might be DEB_TARGET_ARCH rather than DEB_HOST_ARCH.
above the VARIABLES section in that man page there is the TERMS section which
explains:
target m
Hi Simon,
Quoting Simon Richter (2025-01-16 16:52:19)
> atomic operations require linking against libatomic — always have. Some
> architectures inline a few functions, which is how you get away with omitting
> the library on amd64 most of the time, but this is incorrect.
>
> No architecture speci
Hi,
you might want to consider bringing up what you think are problems with sbuild
on on the Debian BTS of sbuild instead of d-devel unless you think that this
topic deserves wider discussion. I put the relevant bug in CC. Maybe drop
debian-devel@lists.debian.org unless you think that this issue d
Quoting Johannes Schauer Marin Rodrigues (2025-02-10 10:48:35)
> Quoting Simon Richter (2025-01-17 11:43:39)
> > In my own packages, I check if libatomic exists, and if it does, I
> > unconditionally link if I use any atomics. I also check if the linker
> > accepts
> >
Hi Sean,
Quoting Sean Whitton (2025-03-15 02:49:58)
> - (At least some of) the packages are uploaded relatively often.
with the upcoming freeze, I do not expect too many uploads to be necessary (but
can be done if needed). But is that a problem?
> - You already use dgit to upload.
The wiki page
Hi Steven,
On 2025-04-21 07:19, Steven Robbins wrote:
I am able to reproduce it thanks to NoisyCoil's hint about
--aspcud-criteria. I'm working on a fix now.
Okay, I don't know how to solve this. The package is uploaded now for
unstable so the --aspcud thing no longer matters.
Using sbuild -
Hi Marc,
Quoting Marc Haber (2025-04-28 08:39:17)
> On Sun, 27 Apr 2025 15:08:18 +0200, "Andrea Pappacoda"
> wrote:
> >On Sun Apr 27, 2025 at 2:18 PM CEST, Marc Haber wrote:
> >> Useradd has grown most of that functionality in the last two decades.
> >> That leaves no space for adduser between us
Hi,
Quoting Josh Triplett (2025-04-20 19:05:13)
> On Sun, Apr 20, 2025 at 12:48:08PM +0200, Simon Josefsson wrote:
> > Josh Triplett writes:
> >
> > > And the extra symlinks in `/etc/alternatives` don't take much size; I
> > > agree you don't need update-alternatives, but then, you also don't
>
Hi,
Quoting Simon Josefsson (2025-05-06 11:34:47)
> The problem seems that it is generating a relative path to its own command
> expanded via PATH, which doesn't work because there is no /share symlink but
> there is /usr/share/.
>
> Is this a problem in 'gradle' (and other packages) that should
Hi,
Quoting Jonathan Dowland (2025-05-06 10:51:45)
> On Thu May 1, 2025 at 8:37 PM BST, Chris Hofstaedtler wrote:
> > Does anything actually _use_ the Build-Essential: yes line?
>
> I honestly don't know.
I've never seen it being used.
> I expect so, or the ftp-masters wouldn't be adding it to
Hi,
Quoting Simon Josefsson (2025-03-08 13:43:26)
> My point was that there is no reasonable way to gain confidence about
> security properties of any piece of non-free microcode. Everyone can now
> produce AMD microcode that corrupts your machine in advanced ways that evade
> detection, but we d
Quoting Andrey Rakhmatullin (2025-05-12 12:29:40)
> On Mon, May 12, 2025 at 11:58:45AM +0200, Santiago Vila wrote:
> >El 12/5/25 a las 9:49, Holger Levsen escribió:
> >>I dont want to use git-buildpackage and I don't want a gpb.conf. Please
> >>accept
> >>this. Thanks.
> >
> >I also don't like the
Hi Aaron,
Quoting Aaron Rainbolt (2025-06-13 15:51:50)
> > thank you for your work! I see that the mails, the issue and the bug report
> > you opened did not get much of a reply and I agree that that's not ideal.
> > On the other hand, you also did not send a patch. I realize that you linked
> > i
Hi Aaron,
Quoting Aaron Rainbolt (2025-06-12 21:31:02)
> Some time ago, I did a lot of work on getting a U-Boot + grub-efi-arm64
> boot flow to work on the Raspberry Pi 4 with Debian. I was able to get
> a proof-of-concept implementation to work correctly, and was interested
> in upstreaming my wo
Hi,
your subject suggests that you are looking for a solution for huge upstream
packages in general but reading your mail I get the feeling that you are
looking for a solution for src:linux specifically? I'm asking because the way
that src:linux is packaged in Debian contains a *lot* of custom cod
Quoting Jochen Sprickerhof (2025-07-24 09:11:41)
> * picca [2025-07-24 07:39]:
> >I prepared a directory with a bunch of sources packages.
> >
> >Now I need to build them in the right order with sbuild.
> >
> >Do we have somethings which could do this out of the box.
> >
> >something like
> >
> >s
401 - 472 of 472 matches
Mail list logo
