Hi,
Quoting Aurelien Jarno (2024-05-20 11:49:32)
> > > > That's all legacy stuff and I really don't want to touch it anymore.
> > > > Going from the other side, maybe libc6.postinst could use something
> > > > more reliable than ischroot()? Is systemd-detect-virt able to figure
> > > > out the
Hi,
Quoting Chris Hofstaedtler (2024-05-20 10:38:04)
> * Johannes Schauer Marin Rodrigues [240520 07:35]:
> > [..] But maybe it [glibc's postinst] should be doing some
> > more involved checks about what PID 1 is? It could then make sure to only
> > call
> > systemd
Quoting Helmut Grohne (2024-05-20 07:17:54)
> Hi Chris,
>
> On Mon, May 20, 2024 at 01:02:32AM +0200, Chris Hofstaedtler wrote:
> > "..., when using telinit from systemd-sysv"
> >
> > It would seem like a reasonable assumption that systemd-sysv's
> > telinit uses systemd-specific stuff, like
Package: dash
Version: 0.5.12-6
Severity: wishlist
Tags: patch
Hi,
please consider cherry-picking this patch from upstream git:
https://git.kernel.org/pub/scm/utils/dash/dash.git/commit/?id=6347b9fc52d742f36a0276cdea06cd9ad1f02c77
It even works fine when backported to bookworm dash :)
Before:
r details see bug #542747 which is also referenced
in the description of the unreleased-changes tag. More details also here:
https://salsa.debian.org/lintian/lintian/-/commit/25be3ba45884334e7e07c7643b5e4fd4ad5a21ee#note_182777
> On Sun, 12 May 2024 23:10:14 +0200 Johannes Schauer Marin Rodrigues wrote:
>
Hi,
Quoting Guillem Jover (2024-05-14 10:24:09)
> When I proposed suppressing the creation of the symlink I had in mind and had
> locally the first approach, because it's less noisy, and I assume users on
> those kind of systems will have logic somewhere to handle that case anyway.
sure, works
Package: dpkg
Version: 1.21.22
Severity: wishlist
Tags: patch
Hi,
dpkg postinst fails to create the start-stop-daemon compatibility
symlink if /usr does not exist:
ln: failed to create symbolic link '/sbin/start-stop-daemon': No such file
or directory
Getting into this situation requires
Hi,
Quoting Francesco Poli (2024-05-12 00:32:42)
> On Sat, 13 Apr 2024 14:50:05 +0200 Francesco Poli wrote:
> > On Fri, 12 Apr 2024 19:57:23 +0200 Johannes Schauer Marin Rodrigues wrote:
> > > Quoting Francesco Poli (wintermute) (2024-04-11 00:13:51)
> > > &g
Hi,
Quoting Francesco Poli (wintermute) (2024-05-12 21:06:24)
> I am still trying to set up sbuild-qemu to build (and check/test) Debian
> packages.
>
> After creating the virtual machine image:
>
> $ mkdir -p ~/.cache/sbuild/build
> $ cd /dev/shm
> $ TMPDIR=/dev/shm
Hi,
Quoting Johannes Schauer Marin Rodrigues (2024-04-28 19:34:07)
> unfortunately, this problem is not transient but reproducible. The problem
> is, that the involved libraries which are 404 have alternative 64bit time_t
> versions in unstable:
>
> libssl3 -> lib
Control: tag -1 + unreproducible
Hi,
Quoting Richard Ulrich (2024-04-30 10:44:46)
> We use fakechroot for building a live OS that starts out with debootstrap.
> This worked fine for a while, but started to fail last week. Now apt crashes
> when it ties to download anything:
> [...]
> I am
Source: libarchive
Version: 3.7.2-2
Severity: normal
X-Debbugs-Cc: debian-m...@lists.debian.org, ty...@mit.edu
Control: affects -1 src:e2fsprogs
Hi,
the upload of e2fsprogs 1.47.1~rc1-1 to unstable yesterday uses a new
feature where libarchive is used to create filesystem images from
tarballs.
Quoting Aurelien Jarno (2024-04-28 15:57:29)
> When running sbuild in unshare chroot mode, it is not possible to write to
> /dev/stdout:
>
> | echo test > /dev/stdout
> | sh: 1: cannot create /dev/stdout: Permission denied
>
> This is the reason of the FTBFS of at least clisp and supervisor when
Hi,
Quoting Chris Hofstaedtler (2024-04-28 18:30:56)
> the autopkgtests for mmdebstrap as part of migration tests for testing/amd64
> fail with apt reporting 'Not found' errors.
>
> As an example, for this scenario:
> mmdebstrap 1.4.3-6
> util-linux/2.40-8 gdm3/46.0-2 sssd/2
> src:util-linux
Package: reform-setup-wizard
Version: 0.1.0-1
Severity: serious
As it says in subject.
Hi Keith,
On Thu, 14 Jul 2022 15:19:22 +0100 Steve Capper wrote:
> With some stracing, it became apparent that the newlib headers were
> pulling in an extra stdint.h (that wasn't part of newlib). I rebuilt the
> gcc-arm-none-eabi package with the "provide-stdint-for-embedded.patch"
> removed.
Quoting Milan Kupcevic (2024-04-21 01:03:12)
> On 4/20/24 15:59, Johannes Schauer Marin Rodrigues wrote:
> > Quoting Milan Kupcevic (2024-04-20 21:46:14)
> >> On 4/20/24 15:05, Johannes Schauer Marin Rodrigues wrote: [...]
> >>> Quoting Milan Kupcevic (2024-04-20
Quoting Milan Kupcevic (2024-04-20 21:46:14)
> On 4/20/24 15:05, Johannes Schauer Marin Rodrigues wrote: [...]
> > Quoting Milan Kupcevic (2024-04-20 20:50:27)
> >> This package builds just fine either on or off an island. The "pre-built
> >> artifacts" i
Hi,
Quoting Milan Kupcevic (2024-04-20 20:50:27)
> This package builds just fine either on or off an island. The "pre-built
> artifacts" is actually the build support provided by the upstream for their
> official release package. It is nice to rebuild the build support, but is not
> required nor
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-de...@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-de...@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-de...@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-de...@lists.debian.org
* Package name: tinyusb
Version : 0.16.0
Upstream Contact: Ha Thach
* URL : https://www.tinyusb.org/
* License : Expat
Programming Lang: C
Hi Francesco,
Quoting Francesco Poli (wintermute) (2024-04-11 00:13:51)
> I am trying to set up sbuild-qemu to build (and test) Debian packages.
>
> After creating the virtual machine image:
>
> $ mkdir -p ~/.cache/sbuild/build
> $ cd /dev/shm
> $ TMPDIR=/dev/shm
Hi,
Quoting Santiago Vila (2024-04-04 20:03:08)
> El 4/4/24 a las 19:29, Johannes Schauer Marin Rodrigues escribió:
> > Also I'm curious: what is your motivation for using unshare mode if you are
> > creating your chroots using superuser privileges?
> >
> > And are you
Hi,
Quoting Santiago Vila (2024-04-04 20:35:47)
> El 4/4/24 a las 19:44, Johannes Schauer Marin Rodrigues escribió:
> > instead of doing that, you could've worked around this by just placing the
> > build log into a dedicated temporary directory and then copying it to where
&
Hi,
Quoting Santiago Vila (2024-04-04 15:02:05)
> El 4/4/24 a las 14:07, Johannes Schauer Marin Rodrigues escribió:
> > well this is an old bug. How have you worked around it being open for the
> > past
> > six years?
>
> This is important for me, so I'm still pat
Hi,
Quoting Santiago Vila (2024-04-04 15:24:13)
> > how did you create that tarball?
>
> debootstrap to a directory
> cd /chroot/directory
> tar czvf /srv/whatever.tar.gz *
>
> Yes, I know what using "." instead of "*" would solve the problem, but as I
> said,
> sbuild already supports
Hi,
Quoting Santiago Vila (2024-04-04 12:17:14)
> While trying to use the unshare backend I found this error:
>
> tar: dev/full: Cannot mknod: Operation not permitted
> tar: dev/urandom: Cannot mknod: Operation not permitted
> tar: dev/console: Cannot mknod: Operation not permitted
> tar:
Hi,
well this is an old bug. How have you worked around it being open for the past
six years?
Quoting Santiago Vila (2024-04-04 12:57:13)
> I've simplified the proposed patch to the one in the attach, and now it is
> probably as small as it can be without losing readability (two lines).
>
> It
Hi Christian,
Quoting Johannes Schauer Marin Rodrigues (2024-03-28 10:05:53)
> Christian, can you give this a try as well?
I think sbuild-qemu-boot and sbuild-qemu-update should do the same as
autopkgtest did here:
https://salsa.debian.org/ci-team/autopkgtest/-/com
Hi,
Quoting Francesco Poli (2024-03-28 09:40:27)
> > But your system does not have /usr/share/OVMF/OVMF_CODE.fd?
> Where should it be?
it's from the package ovmf.
> Debian package [search says] it should be in package 'ovmf'. However, the
> [file list] seems to disagree...
>
> [search says]:
On 2024-03-28 08:26, Francesco Poli wrote:
$ sbuild-qemu-update --boot=efi \
~/var/cache/sbuild/sid-amd64.img 1> update.out 2> update.err
You added --boot=efi, good!
before (last 100 chars): "/share/OVMF/OVMF_CODE.fd: Could not open
'/usr/share/OVMF/OVMF_CODE.fd': No such file or
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues
X-Debbugs-Cc: debian-de...@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-de...@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,
On Wed, 6 Mar 2024 11:04:01 +0100 Paride Legovini wrote:
> On Sun, 03 Mar 2024 16:26:41 +0100 Benjamin Drung wrote:
> > Time to join this discussion. The current default was the preference of
> > the author 14 years ago. My taste has change a bit since then. I am open
> > to change the
Hi Stefano & Christian,
On Tue, 23 Jan 2024 14:30:07 + stefa...@debian.org wrote:
> Hi Debian (2024.01.23_13:41:47_+)
> > This seems to be because "incus exec" is trying to write ~/.config/incus,
> > but HOME has been set to /sbuild-nonexistent outside it.
>
> Filed an incus upstream bug
Hi PrelevatedInsider17763 and User0,
On Sat, 24 Feb 2024 11:51:29 + Member Madden Insider Dev 25120
wrote:
> I don't think that this project will not be worth it, I think this is a good
> masterpiece and will be worth it. By the way, if there was a beginner in this
> Linux distro, and if
Hi,
Quoting Helmut Grohne (2024-01-15 13:04:27)
> Simon worked a lot on making gobject-introspection workable with cross
> compilation and this work has hit unstable now. While this seems to work
> fine with autotools, it tends to fail with meson.
I've just learned from Simon McVittie in
Hi,
Quoting Christian Kastner (2023-03-23 09:53:05)
> Attempting to build a package with the autopkgtest-virt-podman backend fails
> because of what I suspect is an issue with $HOME directory handling. podman
> needs $HOME on the host to find containers, but it defaults to
> /sbuild-nonexistent,
Source: python-lsp-black
Version: 2.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sylves...@debian.org
Hi,
python-lsp-black currently FTBFS in unstable. To track down the reason,
I ran debbisect:
DEBIAN_BISECT_SRCPKG=python-lsp-black debbisect
Source: fop
Version: 1:2.8-2
Severity: normal
Tags: patch
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timezones
Hi,
even when keeping SOURCE_DATE_EPOCH equal, varying the timezone via the TZ
environment variable produces
Package: fop
Version: 1:2.8-2
Severity: normal
Tags: patch
Hi,
if I'm not mistaken, the fop utility is not doing anything architecture
dependent. If that assertion is correct, please consider marking it as
Multi-Arch: foreign. I submitted a patch here:
Control: tag -1 + pending
Hi Francesco
Quoting Francesco Poli (2024-02-12 22:46:29)
> On Mon, 29 Jan 2024 21:07:52 +0100 Francesco Poli wrote:
> > Yes, I think it makes sense to have a separate bug report, so that I
> > can be easily notified, once it becomes pending and once it gets closed.
>
Source: krb5
Version: 1.20.1-5+b1
Severity: serious
Tags: ftbfs
Hi,
there as a binNMU "Rebuild to sync binNMU versions" for krb5 and that
failed for arm64, armel and ppc64el:
https://buildd.debian.org/status/package.php?p=krb5
The error logs look very similar:
making check in lib/rpc...
Source: sysvinit
Version: 3.08-6
Severity: normal
Tags: patch
X-Debbugs-Cc: debian-h...@lists.debian.org
User: debian-h...@lists.debian.org
Usertags: hurd-i386
User: debian-d...@lists.debian.org
Usertags: dpkg-root-support
Hi,
this bug is similar to #1063629 in that it removes another use of
Package: util-linux
Version: 2.39.3-6
Severity: normal
Tags: patch
X-Debbugs-Cc: debian-h...@lists.debian.org
User: debian-h...@lists.debian.org
Usertags: hurd-i386
User: debian-d...@lists.debian.org
Usertags: dpkg-root-support
Hi,
when using dpkg --force-script-chrootless to create foreign
Source: sysvinit
Version: 3.08-6
Severity: normal
Tags: patch
User: debian-d...@lists.debian.org
Usertags: dpkg-root-support
X-Debbugs-Cc: debian-h...@lists.debian.org
Hi,
In 2014, code was added to to the sysvinit-core.postinst to fix up
/etc/inittab files on hurd which had /libexec/getty
Source: glibc
Version: 2.37-15
Severity: normal
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
X-Debbugs-Cc: debian-h...@lists.debian.org, debian-cr...@lists.debian.org
Hi,
one of the reasons for DPKG_ROOT support in packages close to the essential and
build-essential set is to
Control: retitle -1 building less from source fails the island test
On Fri, 09 Feb 2024 00:24:00 +0100 Johannes Schauer Marin Rodrigues
wrote:
> the current curl packaging
The first sentence in my mail should've been
> the current less packaging
Apologies for the confusion!
cheers,
Source: less
Version: 590-2
Severity: serious
Tags: patch
Hi,
the current curl packaging uses pre-built artifacts from the upstream
tarball without regenerating them. Attempting to regenerate them by
running "make -f Makefile.aut" proceeds to call curl to download stuff
from
Source: navit
Version: 0.5.6+dfsg.1-2
Severity: normal
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
X-Debbugs-Cc: debian-cr...@lists.debian.org
Hi,
TLDR; navit fails to cross build from source because it sets
CMAKE_TOOLCHAIN_FILE=/etc/dpkg-cross/cmake/CMakeCross.txt in
Hi,
On 2024-01-31 09:15, Ken Sharp wrote:
Do I need to submit the patch somewhere else or is this the correct
place?
the bts is the correct place but debootstrap is maintained by unpaid
volunteers like many other open source projects. So getting your patch
merged depends on somebody finding
Package: systemd
Version: 252.19-1~deb12u1
Severity: normal
Hi,
steps to reproduce:
$ debvm-create
[...]
$ debvm-run
[...]
root@testvm:~# systemctl status systemd-binfmt.service
○ systemd-binfmt.service - Set Up Additional Binary Formats
Loaded: loaded
Quoting Francesco Poli (2024-01-29 20:54:25)
> On Mon, 29 Jan 2024 10:21:29 +0100 Johannes Schauer Marin Rodrigues wrote:
>
> [...]
> > With that said, I think mmdebstrap-autopkgtest-build-qemu should keep
> > using raw images.
>
> OK, after reading these opinions
Hi,
On 2024-01-29 00:07, Francesco Poli wrote:
I was under the impression that the qcow2 format was the recommended
one for QEMU/KVM virtual machine images. At least, qemu-img(1)
describes it as "the most versatile format"...
Anyway, if you think that the raw format is a better choice for
Hi,
Quoting Francesco Poli (2024-01-29 00:12:27)
> Maybe this bug report should cloned and reassigned to sbuild-qemu?
if you like (for example because you want to subscribe to it and notified when
it gets closed) then feel free to clone it. Personally, as long as the issue is
tracked some place
Hi,
Quoting Francesco Poli (2024-01-29 00:07:08)
> What's *your* umask? Is it Debian default (022), by chance?
yes.
> This seems to work with Debian default umask (022):
>
> $ printf '%o\n' "$(( 0666 - 00022 ))"
> 644
>
> but fails whenever a umask includes an octal digit equal to 7, due
Hi,
On Sun, 28 Jan 2024 19:00:25 +0100 Tomasz Rybak wrote:
> I'm running MNT Reform, so using non-Debian kernel. The rest of packages are
> from Debian.
hello, fellow Reform user. :)
> I'm not sure which solution would be better:
> a) Move required file from /usr/share to /etc (e.g.
Hi,
On Sun, 28 Jan 2024 20:29:30 + Mathias Gibbens wrote:
> distrobuilder is an image building tool for LXC and Incus.
independent on whether this is packaged or not, could you complete the entry
for distrobuilder in this table?
https://wiki.debian.org/SystemBuildTools#General_tools
Hi,
Quoting Johannes Schauer Marin Rodrigues (2024-01-28 00:46:10)
> Quoting Francesco Poli (wintermute) (2024-01-27 19:44:15)
> > Is there any special tweak or configuration needed to use
> > sbuild-qemu-update with mmdebstrap-autopkgtest-build-qemu VM images? Where
> &g
Quoting Francesco Poli (wintermute) (2024-01-27 19:44:15)
> As I said in bug report [#1061634], I've been able to create a QEMU/KVM
> virtual machine image for autopkgtests:
>
> $ mkdir -p ~/var/cache/sbuild/
> $ cd /dev/shm
> $ TMPDIR=/dev/shm mmdebstrap-autopkgtest-build-qemu \
>
Hi,
Quoting Francesco Poli (wintermute) (2024-01-27 19:20:08)
> I've been able to create a QEMU/KVM virtual machine image for autopkgtests:
>
> $ mkdir -p ~/var/cache/sbuild/
> $ cd /dev/shm
> $ TMPDIR=/dev/shm mmdebstrap-autopkgtest-build-qemu \
> --size=25G --boot=efi
Hi,
On Tue, 16 Jan 2024 20:43:11 +0100 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
thank you for your bug!
> Couldn't find include 'GObject-2.0.gir' (search path: '['/usr/share/gir-1.0',
> '/usr/lib/x86_64-linux-gnu/gir-1.0',
>
Hi Francesco,
Quoting Johannes Schauer Marin Rodrigues (2024-01-23 08:56:24)
> I'm planning to close this bug with this patch:
>
> https://paste.debian.net/hidden/844859ff/
>
> Amongst other improvements, if "$IMAGE" cannot be accessed by the unshared
> u
Control: tag -1 + pending
Hi,
I'm planning to close this bug with this patch:
https://paste.debian.net/hidden/844859ff/
Amongst other improvements, if "$IMAGE" cannot be accessed by the unshared
user, it will error out early with a (hopefully) helpful error message.
Thanks!
cheers, josch
-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * cherry-pick upstream commit to prevent reverse B-D of libimath-dev
+from requiring python3-imath being installed
+ * libimath-dev: drop dependency on python3-imath (Closes: #-1)
+
+ -- Johannes Schauer Marin Rodrigues Mon, 22
Source: mesa
Version: 24.0.0~rc2-1.1
Severity: normal
Hi,
I'm trying to build mesa 24 from experimental on bookworm. Since rusticl
requires rust-bindgen 0.66 and since building that and the surrounding
rust packages on bookworm is infeasible, I decided to disable rusticl by
excluding my host
Hi Aidan,
On Thu, 18 Jan 2024 16:52:26 +0100 Andrey Rakhmatullin wrote:
> I see you added this tool to the list of similar tools on the wiki so you
> at least know about that list. So how is your tool better than other tools
> on that list, or at least than the ones packaged in Debian?
> Please
Hi,
thank you Helmut for your (again) very thorough reply. Just as with your
last large mail to this bug, I can only second the things you said and
have very little to add.
On 2024-01-16 07:29, Helmut Grohne wrote:
On Tue, Jan 16, 2024 at 12:21:46AM +0100, Francesco Poli wrote:
Well,
Hi,
Quoting Francesco Poli (2024-01-14 18:33:14)
> The partition table has been altered.
> Syncing disks.
> $ echo $?
> 0
> $ ls -lF --si sid_amd64.img
> -rw-r-xrwx 1 $USER $USER 670M Jan 14 17:21 sid_amd64.img*
>
> However, if I attempt to use the resulting image, autopkgtest
>
Source: imath
Version: 3.1.9-3
Severity: normal
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Hi,
imath currently fails to cross build from source because it doesn't declare its
dependencies correctly. The patch at the bottom fixes this problem.
- it marks
Hi,
Quoting Johannes Schauer Marin Rodrigues (2024-01-13 20:18:34)
> Quoting Helmut Grohne (2024-01-12 21:58:00)
> > > What can cause mkfs.ext4 to fail with a "Permission denied" error?
> > I think this is our typical problem when dealing with user namespaces
Hi,
Quoting Helmut Grohne (2024-01-12 21:58:00)
> > What can cause mkfs.ext4 to fail with a "Permission denied" error?
> I think this is our typical problem when dealing with user namespaces. I
> guess that the thing that fails here is mkfs.ext4 opening the target image
> file (to be formatted).
Hi,
Quoting Francesco Poli (2024-01-12 20:05:02)
> On Thu, 11 Jan 2024 21:04:16 +0100 Johannes Schauer Marin Rodrigues wrote:
> > Do you see yourself debugging this further by yourself? You probably
> > understand that it's hard for me to investigate something that I cannot
On 2024-01-11 23:40, Bastian Germann wrote:
Ping. It is now 1 week until this will auto-remove several packages.
Please consider releasing and packaging the new release.
Whoops, sorry!! And thank you for the ping.
This has now been taken care of. The version I just uploaded has the
Hi,
Quoting Francesco Poli (2024-01-11 08:58:49)
> On Thu, 11 Jan 2024 00:45:50 +0100 Johannes Schauer Marin Rodrigues wrote:
> > Interesting! I'm unable to reproduce either of these issues and I'm also
> > puzzled why you get this "permission denied" error. On my
Hi,
Quoting Francesco Poli (wintermute) (2024-01-10 23:54:30)
> I am giving mmdebstrap-autopkgtest-build-qemu a try.
thank you!
> The following command fails:
>
> $ mmdebstrap-autopkgtest-build-qemu --boot=efi sid sid_amd64.img
>
> during some package installation with "no space left on
Control: affects -1 + mmdebstrap
Hi,
Quoting Chris Hofstaedtler (2024-01-09 18:46:14)
> On Tue, Oct 17, 2023 at 04:36:19PM +0200, Helmut Grohne wrote:
> [Move systemd files to /usr]
> > I'm attaching a patch for your convenience.
>
> Could I ask you to apply this patch some time soon, please?
>
Hi Francesco,
On 2023-12-28 15:47, Francesco Poli wrote:
I stayed tuned and I saw that mmdebstrap/1.4.0-1 ships a
mmdebstrap-autopkgtest-build-qemu that does not require superuser
privileges (according to its man page).
Do I understand correctly that this new script is one of the building
Quoting Paul Gevers (2024-01-06 13:20:11)
> Thanks for being elaborate in your reply, it matches what I was thinking. (I
> wasn't aware of the other examples though).
there are certainly more examples. For example I maintain the package box64
which allows running amd64 binaries on arm64 but
Quoting Paul Gevers (2024-01-05 20:15:22)
> Thanks for reaching out.
Thank Helmut for poking me in #debian-apt :)
> For britney2, the Sources stanza would also be needed; then we could use this
> to generate britney2 testcases. I created 10 of those yesterday by hand [1].
>
> The simplest for
Hi,
On Thu, 4 Jan 2024 21:04:57 +0100 Paul Gevers wrote:
> [20:21:54] agreed, but britney2 doesn't handle :any on virtual
> packages in any way (neither binary dep nor build dep)
> [20:22:10] (and I'm not sure whether that's legal in any way)
> [20:23:08] agreed
> [20:23:28] which I'm
Control: severity -1 serious
Hi,
now that I know that BUILT_MODULE_NAME[0] and DEST_MODULE_LOCATION[0] break it,
I found other packages via codesearch.d.n that use that syntax and I was
wondering whether they break as well.
The following packages fail to install in unstable right now:
Quoting Askar Safin (2024-01-02 16:05:03)
> It follows from my interpretation of the phrase "Subject to
> dependency constraints" from "man apt_preferences", that
> first apt should exclude logically inconsistent solutions. So it
> should first exclude "libuv1-dev 1.9.1-3", because it is
>
Hi Andreas,
thank you so much for your fast reply!
Quoting Andreas Beckmann (2024-01-03 02:53:20)
> Which dkms package version was used to build the failing package? Does█
> it make a difference (or even ftbfs) if it gets rebuilt with 3.0.12-3?
According to the Installed-Build-Depends field of
Package: dkms
Version: 3.0.12-3
Severity: normal
Hi,
the problem appears since 3.0.12-3 and not with 3.0.12-1. The package that
fails since this change in the dkms package is not part of Debian but its
packaging source can be found here:
Control: severity -1 serious
Hi Bastian,
thank you for your bug!
I'm raising its severity as this makes the package have a RC bug.
Quoting Bastian Germann (2024-01-02 18:02:45)
> The tests fail with the latest pymupdf: AttributeError: 'Shape' object has no
> attribute 'insertText'
>
>
Hi,
On Mon, 25 Dec 2023 13:25:19 +0100 "Ajayi Olatunji O."
wrote:
> * Package name: ruby-deb-version
>
> Version : 1.0.2
> Upstream Author : Nemo
>
> * URL : https://github.com/captn3m0/ruby-deb-version#readme
> * License : MIT
> Programming
Hi,
I'm the author of the change that removed Priority:Required packages from
build-essential. Since there has been no other input to this bug I thought I
just weigh in with my two cents.
On Tue, 5 Dec 2023 22:39:51 + Harlan Lieberman-Berg
wrote:
> On Mon, 30 Oct 2023 17:14:57 +0100 Marc
Hi,
Quoting Emanuele Rocca (2023-12-04 11:49:30)
> some compiler flags are architecture specific and should not leak when
> cross-building.
>
> As an example, -fcf-protection is x86-specific, and the following fails:
>
> aarch64-linux-gnu-gcc-13 -fcf-protection
>
> Similarly,
Hi,
Quoting Hilmar Preusse (2023-12-01 23:10:36)
> I run sbuild as following:
>
> sbuild --no-run-lintian --arch-all --dist=sid *.dsc -d unstable-amd64-sbuild
>
> , where unstable-amd64-sbuild references a chroot. Updating the chroot is
> done:
>
> sudo sbuild-update -udcar
Hi,
Quoting Dima Kogan (2023-12-01 05:11:19)
> Johannes Schauer Marin Rodrigues writes:
> >> Would that work, though?
> > Yes. Did you try it and it did not work? What was the error message?
>
> No :) I wanted to read about what it did first. I tried it just now,
>
Hi,
Quoting Dima Kogan (2023-11-28 17:25:01)
> I sorta expected that there was extra complexity here that made
> debugging difficult. It's unfortunate.
to be fair, I have yet to see a problem involving apt pinning that was not
difficult. If the wrong package that got installed did not make you
Hi Dima,
qick top post as I'm about to head out for work and I don't have access to my
Debian mail there. I'll write you a more complete reply in ~12 hours when I'm
back.
Until then, the short answer is: you cannot re-run that apt-get in a shell
because of the file descriptors that are passed,
Hi,
Quoting Jochen Sprickerhof (2023-11-24 13:06:31)
> The difference is due to mmdebstrap opening a extra namespace here:
>
> https://sources.debian.org/src/mmdebstrap/1.4.0-1/mmdebstrap/#L1707
this is is only invoked for --chrooted-*-hooks but CLONE_NEWNS is also what
mmdebstrap unshares by
Hi,
On Thu, 23 Nov 2023 19:52:13 +0100 Julian Andres Klode wrote:
> > I consider dpkg-source's behaviour, of excluding .gitignore by default,
> > to be wrong:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908747
> > (You may recall that report, since you commented on it.)
> I see, I
Hi,
Quoting Dima Kogan (2023-11-23 02:54:16)
> Hi. I'm seeing a failure that I understand very well, but yet don't know
> how to debug or fix. Any suggestions would be appreciated.
>
> I'm making an Ubuntu/focal image that has a bunch of stuff installed,
> and can serve as a base for
Package: init-system-helpers
Version: 1.65.2
Severity: normal
Tags: patch
User: debian-d...@lists.debian.org
Usertags: dpkg-root-support
Hi,
when trying to create a Hurd chroot using chrootless mode with DPKG_ROOT we
noticed that update-rc.d incorrectly handles sysvinit. The patch in this merge
Package: sbuild
Version: 0.85.0
Severity: normal
Hi,
steps to reproduce:
--chroot-setup-commands='ischroot && echo "is chroot" || echo "is not
chroot"
in contrast to mmdebstrap unshare mode, the contents of
/proc/1/mountinfo and /proc/self/mountinfo are the same in sbuild. See
1 - 100 of 2354 matches
Mail list logo
