t work with original-awk
is found when changing the default, but I would be surprised if this
would uncover a large number of bugs.
> Regards,
> Branden
>...
cu
Adrian
On Sun, Apr 20, 2025 at 06:58:36PM -0500, G. Branden Robinson wrote:
> Hi Adrian,
Hi Branden,
> At 2025-04-21T01:34:56+0300, Adrian Bunk wrote:
>...
> My impression from watching countless upgrades over the years is that,
> when any Essential package is available for upgrade, upg
then there's the normal time-waste like "the package ships
a bash-completion file that uses awk, grep, sed and sort - that's
dependencies on four essential packages".
> Regards,
> Branden
>...
cu
Adrian
On Sun, Apr 20, 2025 at 06:25:53PM +0100, Josh Triplett wrote:
> On Sun, Apr 20, 2025 at 02:56:58PM +0300, Adrian Bunk wrote:
> > On Thu, Apr 17, 2025 at 01:38:18PM -0700, Josh Triplett wrote:
> > > Simon Josefsson wrote:
> > > > Debian trixie images ship with
On Sun, Apr 20, 2025 at 07:44:34PM +0100, Josh Triplett wrote:
> On Sun, Apr 20, 2025 at 08:58:29PM +0300, Adrian Bunk wrote:
> > On Sun, Apr 20, 2025 at 06:05:13PM +0100, Josh Triplett wrote:
> > > On Sun, Apr 20, 2025 at 12:48:08PM +0200, Simon Josefsson wrote:
> > &
would be for the use case where a user does not want to be able to
install security updates, but does need binary compatibility with Debian.
That's a rare use case.
When binary compatibility is not required, source-based distributions
will always provide smaller images with slightly better performance.
cu
Adrian
awk (for those that happen to be
>reproducible)
>...
Tools like awk/sed/perl would have to stay part of the build
essential set if they get dropped from the essential set.
Example:
/usr/share/aclocal/libtool.m4:AC_REQUIRE([AC_PROG_AWK])dnl
> Helmut
cu
Adrian
nd sed in the
relevant package set could immediately be replaced with usage of the
essential Perl.
Unless someone wants to get rid of Perl in the essential set,
which is 10 times the size of AWK and sed combined.
The sane starting point would be discussing which tools should be part
of the (tra
eam integration in the official Rust compiler is
rather slow unfortunately.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
On Sat, 2024-10-26 at 11:08 +0200, John Paul Adrian Glaubitz wrote:
> I just realized that this doesn't work because kiwi doesn't have a setup.py
> anymore but just uses pyproject.toml. Do you know how it works in this case?
OK, I just remove every custom override and let debhe
Hi Timo,
On Sat, 2024-10-26 at 10:15 +0200, John Paul Adrian Glaubitz wrote:
> On Fri, 2024-10-25 at 22:19 +0200, Timo Röhling wrote:
> > I ran into this issue with old-style setuptools packages (i.e.,
> > packages with a setup.py); AFAIK the entry_points mechanism needs
> &
le different because we use
> --system-site-packages virtualenvs, but they can be a good way to deal
> with this.
Can you name any package using this mechanism so I can have a look?
I'm not really experienced with tox, so it would be great to have some
guidance in the form of sample
t;
>
> export PYBUILD_BEFORE_TEST=\
> {interpreter} setup.py egg_info; \
> cp -r {dir}/src/*.egg-info {build_dir}
>
> export PYBUILD_AFTER_TEST=\
> rm -r {dir}/src/*.egg-info {build_dir}/*.egg-info
Thanks, this is what I was looking for. I will give this a try.
Hi Andrey,
thanks a lot for the fast and already helpful reply!
On Thu, 2024-10-24 at 16:03 +0500, Andrey Rakhmatullin wrote:
> On Thu, Oct 24, 2024 at 12:44:45PM +0200, John Paul Adrian Glaubitz wrote:
> > (Please CC as I'm not subscribed to debian-devel)
>
> (this is ho
er nocheck nobench, $(DEB_BUILD_OPTIONS)),)
/bin/sh -c "cd test/unit && pytest-3"
endif
However, that doesn't work and the tests still fail.
Does anyone have a suggestion how to solve? I would like to update the kiwi
package to the latest upstream version before
et me
know.
Thanks,
Adrian
> [1] https://db.debian.org/machines.cgi?host=shenzhou
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
nding problems for Turkish users.
cu
Adrian
't
seem to be much documentation available for pybuild which explains how to adjust
PYTHONPATH for running the testuite.
Note that I tried this with kiwi 10.0.16 plus the patch from [3]. I put up a
little
reproducer in [4].
Does anyone know how to make pybuild set the proper PYTHONPATH so that
g to fix two other bugs, one being missing SDL-2
support and the other the FTBFS after rebuild from the same source unpack.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
found the malicious code without knowing that there is
something hidden?
> cheers,
> kpcyrd
cu
Adrian
# build-to-host.m4 serial 30
dnl Copyright (C) 2023-2024 Free Software Foundation, Inc.
dnl This file is free software; the Free Software Foundation
dnl gives unlimited permission to copy and/or
On Sat, Apr 06, 2024 at 07:13:22PM +0800, Sean Whitton wrote:
> Hello,
>
> On Fri 05 Apr 2024 at 01:31am +03, Adrian Bunk wrote:
>
> >
> > Right now the preferred form of source in Debian is an upstream-signed
> > release tarball, NOT anything from git.
>
> T
On Fri, Apr 05, 2024 at 01:30:51AM +0200, kpcyrd wrote:
> On 4/5/24 12:31 AM, Adrian Bunk wrote:
> > Hashes of "git archive" tarballs are anyway not stable,
> > so whatever a maintainer generates is not worse than what is on Github.
> >
> > Any proper
ee.
But for that writing tooling would be the trivial part,
architectural topics like where to store the commit ID
and where to store the git tree would be the harder parts.
Or perhaps stop using tarballs in Debian as sole permitted
form of source.
> cheers,
> kpcyrd
cu
Adrian
pcyrd/backseat-signed
>
> The README
>...
"This requires some squinting since in Debian the source tarball is
commonly recompressed so only the inner .tar is compared"
This doesn't sound true.
> Let me know what you think. 🖤
>
> Happy feet,
> kpcyrd
cu
Adrian
On Tue, Apr 02, 2024 at 06:05:22PM +0100, Colin Watson wrote:
> On Tue, Apr 02, 2024 at 06:57:20PM +0300, Adrian Bunk wrote:
> > On Mon, Apr 01, 2024 at 08:07:27PM +0200, Guillem Jover wrote:
> > > On Sat, 2024-03-30 at 14:16:21 +0100, Guillem Jover wrote:
> > > > Th
rading/downgrading the gnulib m4 files
(like the one used in the xz backdoor) without upgrading/downgrading
the corresponding gnulib C files?
> Thanks,
> Guillem
cu
Adrian
o break them, or
> require a lot of pain for people who are building on MacPorts, et. al.
>...
Everything you mention should already be supported by Meson.
> - Ted
cu
Adrian
On Mon, Apr 01, 2024 at 12:02:09PM +0200, Bastian Blank wrote:
> Hi
>
> On Sun, Mar 31, 2024 at 07:48:35PM +0300, Adrian Bunk wrote:
> > > What we can do unilaterally is to disallow vendoring those files.
> > These files are supposed to be vendored in release tarballs,
&
ult so it's all moot anyway.
>...
The first step of the xz exploit was in a vendored gnulib m4 file that
is not (and should not be) in git and that does not get updated by
dh_autoreconf.
cu
Adrian
tead.
> Does it help? At least in the case of autoconf it removes one common
> source of hard to read files.
>...
But I doubt every DD would be able to review the 2k LOC non-vendored
autoconf code in xz.
The experimental cmake build of xz also has 2700 LOC.
> Bastian
cu
Adrian
On Sun, Mar 31, 2024 at 03:07:53AM +0100, Colin Watson wrote:
> On Sun, Mar 31, 2024 at 04:14:13AM +0300, Adrian Bunk wrote:
> > The timing of the 5.6.0 release might have been to make it into the
> > upcoming Ubuntu LTS, it didn't miss it by much.
>
> It didn't mi
y more secure,
but an intentional backdoor that gets detected early is rather
rare so far.
> -Jonathan
cu
Adrian
On Sat, Mar 30, 2024 at 11:28:07PM +0100, Pierre-Elliott Bécue wrote:
>...
> I'd be happy to have Debian France care about buying and having yubikeys
> delivered to any DD over the world.
Including Russia?
cu
Adrian
ood option.
In many cases our upstream source is the unsigned tarball Github
automatically provides for every tag, which invites MITM attacks.
The hash of these tarballs is expected to change over time, which makes
it harder to reliably verify that the upstream sources we have in the
archive match what is provided upstream.
cu
Adrian
one more last-minute fix",
but using tags would also invite to manipulation similar to what
happened with xz at any point after the release.
> Best,
> Antonio Russo
cu
Adrian
Hi,
On Tue, 2024-03-05 at 09:56 +0100, John Paul Adrian Glaubitz wrote:
> I would like to ask for help with the t64 transition for m68k, powerpc and
> sh4 because it's getting too much for me alone and I'm really exhausted.
>
> I have build many packages for powerpc already
lot for the detailed analysis. In fact, libhtml-parser-perl has not
been rebuilt against the time64_t
Perl package yet [1] which would align with your explanation. I'll try to
rebuild the package locally and if
it fixes the problem, I'll binNMU it for powerpc.
Your explanation will enab
Hi,
On Tue, 2024-03-05 at 23:10 +0100, John Paul Adrian Glaubitz wrote:
> >
> > oks like it's built with dpkg-dev_1.22.4 but the time64 build flags are
> > only activated with 1.22.5.
>
> Ah, that would explain it, thank you so much!
>
> > I think there
On Wed, 2024-03-06 at 00:08 +0200, Niko Tyni wrote:
> (Oops, forgot the Cc you asked for. So resending. Apologies for the
> duplicate on the list.)
No worries.
> On Tue, Mar 05, 2024 at 09:17:17PM +0100, John Paul Adrian Glaubitz wrote:
>
> > I am getting strange Perl erro
&ver=0.38-3&stamp=1709663348&raw=0
I have already rebuilt Perl once again against the new time64_t libraries,
but that didn't help although the package builds fine locally.
Does anyone knowledgeable with Perl know what's going on?
Thanks,
Adrian
PS: Please CC me, I am not
On Tue, 2024-03-05 at 09:56 +0100, John Paul Adrian Glaubitz wrote:
> For m68k, there is mitchy.debian.net and for powerpc, there is
> perotto.debian.net.
>
> For sh4, qemu-user can be used.
>
> Chroots here: https://people.debian.org/~glaubitz/chroots/
I'm collecting
l, so please CC.
For m68k, there is mitchy.debian.net and for powerpc, there is
perotto.debian.net.
For sh4, qemu-user can be used.
Chroots here: https://people.debian.org/~glaubitz/chroots/
Thank you,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Ph
uildd queue once it has become
stuck due to Mini-DAK as used by Debian Ports not supporting cruft [1].
Thanks,
Adrian
> [1] https://lists.debian.org/debian-sparc/2017/12/msg00060.html
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-G
C kernel driver is not
a problem for the "Ability to further support 32bit architectures",
that's a gcc bug that should be reported upstream just like you wouldn't
suggest dropping amd64 if gcc would ICE on one kernel driver on that
architecture.
> Bastian
cu
Adrian
any issues, so I am confident it should work for
everyone else.
For questions and problems reports, please drop me an email or join
#debian-ports
on OFTC IRC network.
Thanks,
Adrian
> [1] https://db.debian.org/machines.cgi?host=stadler
--
.''`. John Paul Adrian Glaubitz
:
[2]. I have CC'ed two engineers from Loongson to make them aware
of the bug so they can work on a patch to add loong64 support.
Thanks,
Adrian
> [1]
> https://buildd.debian.org/status/fetch.php?pkg=xaw3d&arch=loong64&ver=1.5%2BF-1.1&stamp=1693526902&raw=0
> [2] h
.
- Please disable Ada, D, Go and M2 for loong64 in debian/rules.def.
- Please add "!loong64" for gdb in debian/control.m4
The attached patch implements these changes.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-
On Wed, Aug 09, 2023 at 02:26:17PM +0800, Paul Wise wrote:
> On Tue, 2023-08-08 at 18:32 +0300, Adrian Bunk wrote:
>
> > Manual opt-in for our > 11k -dev packages is a significant cost
> > that would have to be justified by the people who oppose opt-out.
>
> You
On Tue, Aug 08, 2023 at 09:19:16AM -0300, Antonio Terceiro wrote:
> On Tue, Aug 08, 2023 at 11:35:01AM +0300, Adrian Bunk wrote:
> > On Tue, Aug 08, 2023 at 06:46:38AM -, Sune Vuorela wrote:
> > > On 2023-08-07, Benjamin Drung wrote:
> > > > while working a wh
ould be whether
pkgconf --cflags .pc
returns 0 for every pkgconfig file in a package.
That would also catch a common kind of bugs.
cu
Adrian
hether
it should be opt-in or opt-out.
> /Sune
cu
Adrian
d to the check script.
>...
The opposite problem also exists, where it is documented that only
one/few "main" headers are supposed to be included directly by users
and the other headers are internal headers only to be included by
the "main" headers (or by other internal headers).
glibc and GNOME would be examples for this.
cu
Adrian
t; basically non existent or available for the normal user.
>
> That sounds like a new port would be needed,
>...
No, that's not required.
We've already had baseline lowering in ports in the past (and could do
that even for a release architecture) by changing the default in gcc
and then binNMUing all packages.
> bye,
> pabs
cu
Adrian
On Sat, Aug 05, 2023 at 07:40:36PM +0200, Andrey Rakhmatullin wrote:
> On Sat, Aug 05, 2023 at 08:10:35PM +0300, Adrian Bunk wrote:
> > Debian maintainers with proper git workflows are already exporting all
> > their changes from git to debian/patches/ as one file - currently the
On Sat, Aug 05, 2023 at 08:55:03PM +0200, Lucas Nussbaum wrote:
> On 05/08/23 at 19:20 +0300, Adrian Bunk wrote:
> > On Sat, Aug 05, 2023 at 05:06:27PM +0200, Lucas Nussbaum wrote:
> > >...
> > > Packages tested: 29883 (I filtered out those that take a ver
for many packages is preventing a lot of
proper and easy tooling for many things, including here.
> smcv
>...
cu
Adrian
On Wed, Jul 26, 2023 at 06:24:49PM +0200, Aurelien Jarno wrote:
> Hi,
>
> On 2023-07-24 23:07, Adrian Bunk wrote:
> > On Sun, Jul 23, 2023 at 08:36:53PM +0100, Mark Hymers wrote:
> > > On Sun, 23, Jul, 2023 at 08:36:15PM +0200, Paul Gevers spoke thus..
> > > >
ect talks about "failing to build twice in a row",
but the contents mostly talks about dpkg-source.
Based on my workflows I can say that building twice in a row, defined as
dpkg-buildpackage -b --no-sign && dpkg-buildpackage -b --no-sign
works for > 99% of all packages in the archive.
> Lucas
cu
Adrian
: missing files, aborting")
>...
These unproblematic cases that result in a FTBFS are usually not the
only cases.
The real problem are the unknown number of packages that are affected
but don't FTBFS where this will only have an effect after the next
upload or binNMU.
> Cheers
> Timo
>...
cu
Adrian
mips64el and mipsel.
Separate build infrastructures with differently configured buildds
running on different types of hardware between unstable/experimental
and oldstable/stable for the same architecture is something that
might not be a good idea.
> Mark
cu
Adrian
age as a Debian
Developer on behalf on the person who created the package and doesn't have
upload rights themselves.
See: https://wiki.debian.org/DebianMentorsFaq#Sponsored_Packages
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`
lly about to buy such a scale with USB and I would therefore
be interested in sponsoring this package. Let me know if you're interested.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
On Sat, Mar 04, 2023 at 07:43:37PM +, Scott Kitterman wrote:
> On March 4, 2023 5:25:35 PM UTC, Adrian Bunk wrote:
> >On Wed, Mar 01, 2023 at 05:54:38PM -0700, Sean Whitton wrote:
> >>
> >> This is a matter of perspective. The fact that dak doesn't store git
On Wed, Mar 01, 2023 at 05:54:38PM -0700, Sean Whitton wrote:
> Hello,
Hi Sean,
> On Sun 26 Feb 2023 at 11:38PM +02, Adrian Bunk wrote:
>
> > On Sun, Feb 26, 2023 at 09:57:34PM +0100, Diederik de Haas wrote:
> >> On Sunday, 26 February 2023 20:06:26 CET Adrian Bunk w
On Sun, Feb 26, 2023 at 08:25:25PM +0100, Helmut Grohne wrote:
> On Sun, Feb 26, 2023 at 07:15:45PM +0200, Adrian Bunk wrote:
> > What you describe is an RC bug as soon as the more recent toolchain
> > becomes default, and the correct solution is to not bui
far less related than you hope:
People tend to be either terse or verbose,
not terse in the package but verbose in git commits.
And when trying to improve verbosity, this shouldn't be only
in the git metadata outside the package.
> Cheers,
> Diederik
cu
Adrian
On Sun, Feb 26, 2023 at 09:57:34PM +0100, Diederik de Haas wrote:
> On Sunday, 26 February 2023 20:06:26 CET Adrian Bunk wrote:
>...
> > For anything in Debian, the package sources in Debian would not
> > disappear when a repository (or salsa) disappears.
>
> Question
On Sun, Feb 26, 2023 at 07:09:59PM +0100, Daniel Leidert wrote:
> Am Sonntag, dem 26.02.2023 um 19:45 +0200 schrieb Adrian Bunk:
> >
> [..]
> > Debian Policy §4.9 says that *attempting* to access the internet
> > is forbidden:
> >
> > For packages in the mai
unity/community/discussions/48173
> where VundleVim (vim plugin manager) disappeared 'out of the blue'.
> (that vundlevim isn't packaged for Debian is irrelevant)
For anything in Debian, the package sources in Debian would not
disappear when a repository (or salsa) disappears.
cu
Adrian
On Sun, Feb 26, 2023 at 04:32:59PM +0100, Daniel Leidert wrote:
> Am Sonntag, dem 26.02.2023 um 16:57 +0200 schrieb Adrian Bunk:
> > On Sun, Feb 26, 2023 at 03:47:49PM +0100, Daniel Leidert wrote:
> > > Am Samstag, dem 25.02.2023 um 16:15 +0200 schrieb Adrian Bunk:
> > &
voids most of the problems
you are worried about (but is not a general solution).
> Helmut
cu
Adrian
grant a term of protection in excess
of those provided by the preceding paragraphs.
...
> --Sam
cu
Adrian
to support Vcs-Bzr but not Vcs-Cvs,
and there is no requirement for tools to drop working support for
something that is no longer specified.
Vcs-Browser is Vcs agnostic and would stay permitted for any kind of Vcs,
including ones never listed in Policy.
> Thanks for any comments,
> Bastian
cu
Adrian
ndoc for generating the manpage for the command-line program.
This made the new libflac unavailable on several ports architectures.
Someone will have to make the build dependency on pandoc and the
contents of debian/flac.install architecture-dependent, or create
a separate binary-all flac-common package for the manpage.
cu
Adrian
g on orphaned packages or doing NMUs, it is also often useful
for me to see the amount/age/contents of bugs in a package as an
indication in what state it is.
cu
Adrian
ser evil for us will be to configure packages
differently when one or all MPI implementations are going away on 32-bit.
For example:
ffmpeg -> codec2 -> octave -> sundials -> sundials does not build with MPICH
One of these four arrows must be broken.
That's work and not fun work, but likely the lesser evil.
cu
Adrian
On Mon, Feb 13, 2023 at 10:33:51AM +, Holger Levsen wrote:
> On Sat, Feb 11, 2023 at 10:45:16PM +0200, Adrian Bunk wrote:
> > On Mon, Feb 06, 2023 at 10:07:59AM -0700, Sam Hartman wrote:
> > > Most of us do not prefer to close bugs simply because they are old.
> > It cr
le compromise might be if
upstream says "32-bit patches are welcome" and requires an
--i-know-that-32-bit-support-is-unsupported-and-might-be-broken
configure flag when building for 32-bit archs.
> Best regards
> Alastair
cu
Adrian
[1] https://bugs.debian.org/cgi-bin/bugr
a serious attempt at fixing the bug in exchange for the effort.
It is bad enough that we are often not good at trying to resolve bugs
where users have sometimes spent considerable effort at writing a good
bug report, but asking users to do pointless work would be horrible.
cu
Adrian
[1] especially if
On Sun, Jan 29, 2023 at 05:00:56AM +0100, Guillem Jover wrote:
> On Sat, 2023-01-28 at 21:35:01 +0200, Adrian Bunk wrote:
> > I don't think such arguments are bringing us forward,
> > we should rather resolve the problem that these differ.
> >
> > All/Most(?) p
lled on the buildd.
>...
This seems to be a regression in rust-rustls 0.20.8-1:
Package: librust-rustls-dev
Provides: ..., libstring-shellquote-perl
> - Jonas
cu
Adrian
On Sat, Jan 28, 2023 at 10:23:19PM +0100, Santiago Vila wrote:
> El 28/1/23 a las 22:18, Adrian Bunk escribió:
> > On Sat, Jan 28, 2023 at 09:45:14PM +0100, Santiago Vila wrote:
> > > ...
> > > The other one: There are a bunch of packages whose unit tests rely o
re makes 100 packages FTBFS that do need tzdata
during the build, but previously got it installed through other
build dependencies.
> As you requested, I think the above two are technical reasons, not
> merely "because policy says so".
Thanks, I do appreciate that.
> Thanks.
cu
Adrian
s for the hello package installed by ~ 0.5%, this size
decrease does not strike me as a sufficient reason for reducing the
build essential set.
Everyone can feel free to disagree with me on the previous paragraph,
but please argue technically and not based on wording in policy.
> Regards,
> Guillem
cu
Adrian
to fulfill the Build-Conflicts.
> Thanks!
>
> cheers, josch
cu
Adrian
orce what was enforced
differently in the past, and what is still true in practice today.
It should at least be discussed first whether packages like tzdata that
have been a part of the build essential set should stay there.
> Thanks!
>
> cheers, josch
cu
Adrian
S that do not happen
on the buildds of release architectures are usually not RC.
> Thanks.
cu
Adrian
On Sat, Jan 28, 2023 at 12:20:16AM +0100, Santiago Vila wrote:
> El 27/1/23 a las 22:37, Adrian Bunk escribió:
> > On Fri, Dec 16, 2022 at 02:15:13AM +0100, Santiago Vila wrote:
...
> > I am right now looking at #1027382, and the first question is how I can
> > make apt remov
e welcome - but none of these are critical for our releases since
none of these impact how packages are built for bookworm on our buildds.
> Thanks.
Thanks
Adrian
for sparc and m68k? (Where both the needed KDE packages are
uninstallable)
Adrian, as there seems to be various arches (and reasons) will you speak
upstream?
Yes, I have already replied upstream. I will follow up there tonight.
One of the biggest problems for Debian Ports remains the lack o
itecture support for it.
I will see what I can do.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
package-is-broken-on-ppc64el [ppc64el],...
This might not be the most elegant solution, but it should be sufficient
to solve the problem in this thread and it does not require any tool changes.
> Thanks,
> Guillem
cu
Adrian
quot;
A relevant quesion would be whether this is [!s390x] or [littleendian].
There are 5 additional big endian architectures in ports,
plus people elsewhere apparently working on ports like arm64eb.
And while it is unclear whether s390x has any users at all on Debian,
ports architectures like hppa or powerpc do have users.
cu
Adrian
t ports or all little endian
ports create much extra work for anyone adding support for a new 64bit
little endian architecture.
> Samuel
cu
Adrian
rsion is in the archive on that architecture".
On release architectures people are usually fast with getting stale
versions of no longer buildable packages removed since it prevents
testing migration.
> Samuel
cu
Adrian
ther anyone
can give me some hints on how to convert the images provided at [1] from
ext4 to btrfs.
Thanks,
Adriam
[1] https://cloud.debian.org/cdimage/cloud/OpenStack/
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=23960
--
.''`. John Paul Adrian Glaubitz
: :' : Debi
Package: debhelper
Version: 13.8
Severity: serious
X-Debbugs-Cc: debian-devel@lists.debian.org
[ debian-devel is in Cc for getting further input. ]
dh_dwz is part of the standard sequence in dh since debhelper compat 12.
dwz offers small optimizations of debug info, the typical benefit
seems to
On Fri, Jul 15, 2022 at 07:10:55PM +, Andrew M.A. Cater wrote:
> On Fri, Jul 15, 2022 at 07:05:09PM +0300, Adrian Bunk wrote:
>...
> > Debian is not a project that fights for trans people or fights for
> > denazification or fights for whatever other non-technical top
ng one dislikes or
disagrees with "harassment" or *phobic.
> Thank you,
> Jeremy Bicha
cu
Adrian
.
The best timing for such a change would be immediately after the release
of bookworm.
> Matthias
cu
Adrian
1 - 100 of 1261 matches
Mail list logo
