Source: qt6-base
Version: 6.7.2+dfsg-5
Followup-For: Bug #1035985
I'm not sure the bug subject is accurate for my 'bug' as I'm not having
errors, but there is a real possibility the configuration is not optimal
for 'embedded' systems, namely for OpenGL ES.
It's possible EGLFS is relevant here too.
On Tue Jan 14, 2025 at 8:38 PM CET, Michael Biebl wrote:
> Am 14.01.25 um 16:11 schrieb Diederik de Haas:
> > On Tue Jan 14, 2025 at 3:49 PM CET, Diederik de Haas via
> > Pkg-voip-maintainers wrote:
> >> On Thu Jan 9, 2025 at 6:55 PM CET, Michael Biebl wrote:
> >>
On Tue Jan 14, 2025 at 3:49 PM CET, Diederik de Haas via Pkg-voip-maintainers
wrote:
> On Thu Jan 9, 2025 at 6:55 PM CET, Michael Biebl wrote:
> > No, all you are supposed to do in your .install files is to use the
> > correct paths
> > /usr/lib/systemd/system/foo.service
&g
t thing to do on
the Debian side? If that's the case, then we know (?) that the problem
is indeed (still) in the upstream build system.
Or if the patch is incorrect, can you point out why/where and possibly
provide an (cmake based) example which I could use as inspiration?
Cheers,
Diederi
On Fri Jan 10, 2025 at 1:53 PM CET, Chris Hofstaedtler wrote:
> Yes, we expect Debian package maintainers to implement the simple thing.
In a project I'm part of there is this running joke:
"You sound like Diederik"
It involves kernel stuff and periodically there needs to be a rebase
onto a new u
On Sat Jan 11, 2025 at 10:11 PM CET, Andreas Barth wrote:
> Package: installation-reports
>
> Boot method: sdcard
> Image version: trixie
> Date: 2024-12-27 (download date)
>
> Machine: Banana Pi BPI-M1
> Processor: armhf ARM Cortex-A7
>
> Base System Installation Checklist:
> [O] = OK, [E] = Error
On Sun Aug 11, 2024 at 10:27 PM CEST, Sebastian Ramacher wrote:
> Source: golang-google-grpc
> Version: 1.64.0-6
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
>
> https://buildd.debian.org/stat
On Fri Jan 3, 2025 at 5:44 AM CET, Niels Thykier wrote:
> Package: developers-reference
> Severity: wishlist
> X-Debbugs-Cc: ni...@thykier.net
>
> The section 5.10.4 is about packages that are not portable to all
> architectures. Here it talks about changing the `Architecture` line and
> `Package
On Tue Jan 7, 2025 at 9:44 AM CET, Petter Reinholdtsen wrote:
> Note, I looked at updating to a newer upstream version, but no longer
> know how to do it with the salsa git repo.
>
> % uscan --download-version 3.1.1
> Newest version of dkms on remote site is 3.1.1, specified download version
>
On Mon Jan 6, 2025 at 9:02 AM CET, Petter Reinholdtsen wrote:
> [Diederik de Haas]
> > I was wondering why the autopkgtests were failing, till I realized the
> > problem may actually be in dkms itself.
> > It turns out the error messages come from debian/scripts/dkms-aut
Control: tag -1 moreinfo
On Tue Dec 24, 2024 at 4:10 PM CET, Philipp Kern wrote:
> Package: mumble
> Version: 1.5.517-2.1
> Severity: important
>
> Installed mumble without any prior config and it crashes on startup:
>
> [...]
> 2024-12-24 16:07:13.611 Wayland does not support QWindow::requestActi
On Sat Dec 21, 2024 at 12:03 AM CET, Vagrant Cascadian wrote:
> On 2024-12-20, Diederik de Haas wrote:
> > On Tue Jul 09, 2024 at 22:10 CEST, Salvatore Bonaccorso wrote:
> >> The following vulnerabilities were published for arm-trusted-firmware.
> >>
> >> CVE-
In my previous response I forgot to fix the Subject, so ignore the
'weird' subject, but not its contents, which is fine.
signature.asc
Description: PGP signature
Control: tag -1 fixed-upstream
On Wed Dec 18, 2024 at 12:02 PM CET, Robin Jarry wrote:
> Source: arm-trusted-firmware
> Version: 2.10.0+dfsg-1
> Severity: important
> Tags: security upstream
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
>
> The following vulnerabilities were publishe
On Tue Dec 17, 2024 at 1:04 PM CET, Guillem Jover wrote:
> On Tue, 2024-12-17 at 11:24:30 +0100, Diederik de Haas wrote:
> > On Tue Dec 17, 2024 at 4:32 AM CET, Guillem Jover wrote:
> > > On Mon, 2024-11-25 at 18:40:09 +0100, Diederik de Haas wrote:
> > > > Trying
Hi,
On Tue Dec 17, 2024 at 4:32 AM CET, Guillem Jover wrote:
> On Mon, 2024-11-25 at 18:40:09 +0100, Diederik de Haas wrote:
> > Package: dpkg-dev
> > Version: 1.22.11
> > Severity: wishlist
>
> > Trying to figure out what exactly the various variables from pkg
Control: tag -1 +patch -moreinfo
On 29 Aug 2023 17:55:08 +0200 Diederik de Haas wrote:
> Control: found -1 2022.04+dfsg-1
>
> On 23 Dec 2022 Vagrant Cascadian wrote:
> > Control: tags 1024851 moreinfo
> >
> > There is still a patch applied to enable usb sup
Hi Chris,
On Sat Dec 14, 2024 at 4:24 AM CET, Chris Knadle wrote:
> Before considering upgrades to a new version I have a debian-1.5.517-3
> bugfix release to do that I've been working on for some time. ...
>
> Thank you for seeing if the newer version can be built. I don't release
> a new versi
Control: retitle -1 mumble: New upstream stable release: 1.5.735
On Sat Dec 7, 2024 at 7:29 PM CET, Diederik de Haas via Pkg-voip-maintainers
wrote:
> On Sat Dec 7, 2024 at 7:07 PM CET, Diederik de Haas via Pkg-voip-maintainers
> wrote:
> > I just noticed I forgot to unwrap the Su
On Tue, 10 Dec 2024 07:01:43 +0100 Andreas Tille wrote:
> Control: retitle -1 lsdvd: Will be removed after Trixie release
> Thanks
>
> Given the discussion in the bug log I think it makes sense to do an
> upload by the Debian Multimedia team once. This bug should be turned
> into a request for r
Control: tag -1 fixed-upstream
The following commit added support for bootstrap-html (v5):
https://github.com/meetecho/janus-gateway/commit/5cc6c6c1f3cdaf96fc4adf19acff73f0006ccae9
which was the result of the following upstream PR:
https://github.com/meetecho/janus-gateway/pull/3300
and that would
Control: tag -1 fixed-upstream patch
On Mon, 09 Dec 2024 08:42:14 + Victor Seva
wrote:
> forwarded 1089503 https://github.com/sipwise/rtpengine/issues/1882
Upstream fixed it in the following commit
https://github.com/sipwise/rtpengine/commit/6b3f3b9698ed9670fedccd0db5f595d1c0db917e
And als
On Mon, 2 Dec 2024 16:00:18 +0100 Chris Hofstaedtler wrote:
> On Thu, Nov 14, 2024 at 11:11:43AM +0100, Guido Günther wrote:
> > Not in this case. 0.18 is considerably different regarding
> > e.g. rendering, damage tracking, etc. It's not just an API change.
>
> So, whats the plan here now?
>
>
On Sat Dec 7, 2024 at 7:07 PM CET, Diederik de Haas via Pkg-voip-maintainers
wrote:
> I just noticed I forgot to unwrap the Subject of the following patches:
> - 0009-debian-upstream-signing-key.asc-update-to-upstream-s.patch
> - 0011-debian-gbp.conf-Add-sign-tags-True-to-configurat
I just noticed I forgot to unwrap the Subject of the following patches:
- 0009-debian-upstream-signing-key.asc-update-to-upstream-s.patch
- 0011-debian-gbp.conf-Add-sign-tags-True-to-configuration.patch
- 1002-debian-Add-systemd-tmpfiles-support-for-Mumble-Serve.patch
- 1003-debian-copyright-Update
Your unwillingness to try to resolve a bug is truly spectacular :-/
>From both of you.
I've noticed several issues which I'm trying to find the root cause of and this
seemed like an excellent starting point.
What happens? Reassign to another package and immediately closing with a wont-
fix ... wi
Package: usr-is-merged
Version: 39
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
``systemctl status`` reports ``Tainted: unmerged-bin``, but the
usr-is-merged package description seems to indicate that this should not
be possible? "This package can be successfully installed onl
On Sun Dec 1, 2024 at 1:09 PM CET, Simon Josefsson wrote:
> "Diederik de Haas" writes:
>
> >> In case you make more than one snapshot per day, you can append a
> >> snapshot number after the date, e.g. 0.0~git20130606.2.b00ec39-1.
> >> This shoul
x27;s autotests
were run, but they should be relevant to current systems.
https://salsa.debian.org/diederik/xdg-utils/-/pipelines is where you can see
the Salsa CI pipeline succeeds, both for version 1.1.3-4.1 as with my updates
to 1.2.1.
HTH,
Diederik>From 194c0e0b10aea4721029db5e8ebd9
Package: dkms
Version: 3.1.0-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I was wondering why the autopkgtests were failing, till I realized the
problem may actually be in dkms itself.
It turns out the error messages come from debian/scripts/dkms-autopkgtest.
https://git
On Thu Nov 28, 2024 at 10:44 AM CET, Simon Josefsson wrote:
> Otto Kekäläinen writes:
>
> >> The commit hash. 007c9af.
> >
> > I disagree here - to me the git commit hash is the single most
> > important identifier for the software version if there are no actual
> > releases.
>
> FWIW, I used to b
changes aren't available in Stable.
> On Tue, Nov 26, 2024 at 12:50 PM Diederik de Haas
> wrote:
> >
> > On Tue Nov 26, 2024 at 7:32 PM CET, allan wrote:
> > > I'm afraid not - I downloaded it from debian.org's homepage this morning..
> >
> > Plea
On Tue Nov 26, 2024 at 7:32 PM CET, allan wrote:
> I'm afraid not - I downloaded it from debian.org's homepage this morning..
Please give the full URL to what you downloaded instead of letting other
people *guess* what you DL-ed.
> On Tue, Nov 26, 2024 at 12:28 PM Holger Wansing wrote:
> > allan
Package: dpkg-dev
Version: 1.22.11
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Trying to figure out what exactly the various variables from pkg-info.mk
return, I added a number of 'debug' statements to my (modified) clone of
ffmpeg package repo's debian/rules file and got t
Hi,
On Mon, 28 Aug 2017 10:07:07 -0400 Antoine Beaupre wrote:
> Source: sparse
> Version: 0.5.0-4
> Severity: important
>
> Since I uploaded the new version of horst (5.0, from 4.2), sparse now
> fails to parse its source code on some architecture. The buildds
> report problems with s390x and pp
On Wed, 13 Nov 2024 16:41:00 +0100 Emanuele Rocca wrote:
> Source: coccinelle
> Version: 1.2.deb-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
>
> During a rebuild of all packages in sid, coccinelle failed to build on
> arm64 and amd64 with the following error.
>
> [7]
>
On Tue Nov 19, 2024 at 1:12 PM CET, gregor herrmann wrote:
> On Tue, 19 Nov 2024 12:37:57 +0100, Bill Allombert wrote:
>
> > On Tue, Nov 19, 2024 at 06:29:25PM +0800, Sean Whitton wrote:
> > > On the other hand, is there much benefit? People used to typing
> > > 'less debian/README.source' would n
Package: bluez
Version: 5.77-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
While researching for bug #1087689 I noticed that
``--enable-deprecated`` was added to ``debian/rules`` 7 years ago.
Looking into the upstream code and I see the references to DEPRECATED
all point to
Package: bluez-obexd
Version: 5.77-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Today's upgrade wanted to install the following extra packages:
evolution-data-server-common{a} libcamel-1.2-64t64{a} libebackend-1.2-11t64{a}
libebook-1.2-21t64{a} libebook-contacts-1.2-4t64
Control: tag -1 upstream fixed-upstream
On Mon, 7 Oct 2024 12:27:11 -0400 Louis-Philippe Véronneau
wrote:
> Source: ranger
> Severity: important
>
> Python 3.13 removes a large amount of so called 'dead battery' libraries
> from the standard library.
>
> The following removed libraries were f
Hi Josch,
On Tue Nov 12, 2024 at 4:53 PM CET, Johannes Schauer Marin Rodrigues wrote:
> Quoting Diederik de Haas (2024-11-12 14:35:11)
> > I prefer to have config files in ``~/.config/`` and thereby unclutter my
> > home
> > dir. The XDG_CONFIG_HOME seems perfect for th
Package: sbuild
Version: 0.87.0
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I prefer to have config files in ``~/.config/`` and thereby unclutter my
home dir. It also much easier to put ``~/.config/`` under version control
then my whole HOME dir, which would be needed if I
Hi,
On Fri Nov 8, 2024 at 9:11 PM CET, Holger Wansing wrote:
> "Diederik de Haas" wrote (Sat, 19 Oct 2024 16:54:51
> +0200):
> > IOW: It was so, so close from working ... but it needs the 'boot' flag.
>
> This should now be fixed in the daily images, so
Hi,
On Tue Mar 12, 2024 at 11:19 AM CET, Simon McVittie wrote:
> Control: tags -1 + fixed-upstream
> Control: block -1 by 1061616
> Control: retitle 1061616 pixman: New upstream version 0.43.4
>
> On Mon, 29 Jan 2024 at 10:23:45 +, Simon McVittie wrote:
> > On Mon, 29 Jan 2024 at 05:13:59 +000
Source: pixman
Version: 0.44.0-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
https://buildd.debian.org/status/package.php?p=pixman shows that several
builds failed and I looked the ones from ``mips64el`` and ``riscv64``
and the failures were due to the tests getting killed
Hi,
On Thu Oct 24, 2024 at 9:08 PM CEST, Holger Wansing wrote:
> "Diederik de Haas" wrote (Sun, 20 Oct 2024 16:28:41
> +0200):
> > The 'cs21' device is a (different) Rock64 (rk3328):
> >
> > And now the partition stuff:
> >
> > ```
>
On Mon Oct 21, 2024 at 5:16 PM CEST, Pascal Hambourg wrote:
> On 21/10/2024 at 10:26, Diederik de Haas wrote:
> > On Sun Oct 20, 2024 at 8:49 PM CEST, Pascal Hambourg wrote:
> >> On 20/10/2024 at 16:28, Diederik de Haas wrote:
> >>>
> >>> ```
>
On Sun Oct 20, 2024 at 8:49 PM CEST, Pascal Hambourg wrote:
> On 20/10/2024 at 16:28, Diederik de Haas wrote:
> >
> > AFAIUI, UEFI requires GPT, but GPT does not require UEFI.
>
> No, UEFI does not require GPT, at least not on my amd64 machines
> (including QEMU+OVMF).
On Sun Oct 20, 2024 at 12:34 AM CEST, Pascal Hambourg wrote:
> On 19/10/2024 at 23:58, Holger Wansing wrote:
> >
> > This Rockchip system uses the legacy msdos partition table, right? (No UEFI,
> > thus no GPT).
> > With this partition table it should be possible and is confirmed to be
> > working
Hi,
On Sun Oct 20, 2024 at 2:24 AM CEST, Johannes Schauer Marin Rodrigues wrote:
> Quoting Diederik de Haas (2024-10-19 21:08:37)
> > I never create a separate /boot partition, which has several advantages
> > IMO. But the ARM ecosystem is ... let's say ... diverse.
> >
Hi Pascal,
On Sat Oct 19, 2024 at 8:37 PM CEST, Pascal Hambourg wrote:
> First, thank you for the detailed test report !
You're welcome.
> On 19/10/2024 at 16:54, Diederik de Haas wrote:
> > On Sat Oct 19, 2024 at 1:40 PM CEST, Holger Wansing wrote:
> >>
> >&g
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: s...@packages.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: rot8
Version : 1.0.0
Upstream Contact: Esra Fernau
* URL : https://github.com/efernau/rot8
* License : MIT
Programming Lang
Control: retitle -1 Please add color management support to wlroots
Control: found -1 0.18.1-1
Control: tag -1 patch
Control: forwarded -1
https://salsa.debian.org/swaywm-team/wlroots/-/merge_requests/35
On Thu Aug 29, 2024 at 2:16 PM CEST, Diederik de Haas wrote:
> Source: wlroots
> V
Control: tag -1 moreinfo
On Sat, 28 Sep 2024 03:09:54 + gabriel wrote:
> Package: src:linux
> Version: 6.11-1~exp1
>
> ipu6 mipi camera drivers were not part of previous kernels, now they have
> been upstreamed.
> After upgrading kernel to 6.11 the ipu6 kernel modules are loaded, however
> t
Package: liblcms2-dev
Version: 2.14-2+b1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Version 2.16-1 was uploaded to Experimental in the beginning of the
year, but it would be great if it was uploaded to Unstable too.
Cheers,
Diederik
- -- System Information:
Debian Rele
On Mon Sep 2, 2024 at 1:55 PM CEST, Guido Günther wrote:
> On Sun, Sep 01, 2024 at 08:15:36PM +0200, Diederik de Haas via
> Debian-on-mobile-maintainers wrote:
> > Package: wlr-randr
> >
> > Upstreamed release version 0.4.1 some time ago ...
> >
> > I made
Package: wlr-randr
Version: 0.3.0-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
Upstreamed release version 0.4.1 some time ago and it would be great to
have that in Debian.
I made an attempt at packaging that and you can find it here:
https://salsa.debian.org/diederik
On Sun Sep 1, 2024 at 14:39 CEST, Debian Bug Tracking System wrote:
> Source: wvkbd
> Architecture: source
> Version: 0.15-1
> Changed-By: Jochen Sprickerhof
> Closes: 1080072
> Changes:
> wvkbd (0.15-1) unstable; urgency=3Dmedium
> .
>* New upstream release (Closes: #1080072)
>* Rediff
Package: wvkbd
Version: 0.14.3-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Upstream has a new upstream version available, 0.15, and I'd like it a
lot of that could be packaged for Debian.
Could you possibly also rename your 'master' branch to 'upstream/latest'
so that it
m7ZtGrn7uaEFyMtQtElqLLVLqIxXdPRSVco89QEAk5LbdVV3qZVT
lplNL5vm+T3/iRg396h5dW5/83CmmwA=
=6SZw
-END PGP SIGNATURE-
>From 79b06c8ac9c8c0f983528e802cbe10ede153ade7 Mon Sep 17 00:00:00 2001
From: Diederik de Haas
Date: Wed, 28 Aug 2024 16:36:31 +0200
Subject: [PATCH] d/control: Update Build Dependencies
>From ``meson.buil
Control: tag -1 -patch -upstream -fixed-upstream
Control: notforwarded -1
On 26 Aug 2024 17:22:19 +0200 Diederik de Haas wrote:
> Control: tag -1 upstream fixed-upstream patch
> Control: forwarded -1 https://gitlab.freedesktop.org/pixman/pixman/-/issues/96
Oeps, my CC-ing this bug also mo
Control: tag -1 upstream fixed-upstream patch
Control: forwarded -1 https://gitlab.freedesktop.org/pixman/pixman/-/issues/96
On 12 Jul 2024 13:38:30 +0900 Mike Hommey wrote:
> Source: pixman
> Version: 0.42.2-1
> Severity: serious
>
> The package fails to build on armhf on current sid/testing wi
On Tue, 26 Mar 2024 01:06:34 +0200 Peter Pentchev wrote:
> Control: tag -1 + confirmed
>
> On Tue, Mar 26, 2024 at 01:29:08AM +0500, Andrey Rakhmatullin wrote:
> > Source: dante
> > Version: 1.4.3+dfsg-1
> > Severity: serious
> > Tags: ftbfs
> >
> > https://buildd.debian.org/status/fetch.php?pkg
Package: systemd
Version: 256.5-1
Severity: normal
X-Debbugs-Cc: debian-ker...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I build a custom (arm64) kernel based on Debian's config and in that I
disabled debug info, which in turn disabled ``CONFIG_DEBUG_INFO_BTF``.
Build was
On 07 Jun 2024 15:44:14 +0200 Diederik de Haas wrote:
> On Friday, 1 September 2023 12:02:30 CEST Diederik de Haas wrote:
> > > > AFAICT, TF-A for *rk356x* is really close to being mergeable?
> > > I'm not entirely sure about that. In any case, for th
On 26 May 2024 16:23:07 +0200 Diederik de Haas wrote:
> Source: arm-trusted-firmware
> Version: 2.10.0+dfsg-1
>
> Upstream recently released two new versions:
> - - lts-v2.10.4
> - - v2.11
>
> If you want to stay on a LTS release, then updating to 2.10.4 gives
> qu
On Tue Aug 20, 2024 at 11:45 PM CEST, Cyril Brulebois wrote:
> Emanuele Rocca (2024-08-20):
> > Package: python3-pkg-resources
> > Version: 72.2.0-1
> > Severity: serious
> >
> > Importing pkg_resources fails with the following error:
> >
> > (sid-amd64-sbuild)ema@ariel:~$ python3
> > Python 3
On Tue Aug 20, 2024 at 5:55 PM CEST, Antonio wrote:
> I tried to install the new version of kmod 33+20240816-2 but it seems to
> remove essential packages:
>
> $ sudo apt install kmod
> ...
>
> Upgrading:
> kmod libkmod-dev libkmod2
>
> REMOVING:
> cryptsetup-initramfs initramfs-tools
Control: notfound -1 30+20230519-1
On Mon Aug 19, 2024 at 12:59 PM CEST, Antonio wrote:
> because i did log report after system restore, so it took that version.
> The affected version is 33+20240816-1.
Thanks, updating/fixing the found versions then.
> Il 19/08/24 12:54, Diederik d
On Mon, 19 Aug 2024 09:45:26 +0200 Antonio wrote:
> Package: kmod
> Version: 30+20230519-1
Why did you report it against 30+20230519-1?
Because AFAICT 30+20230519-1 and 32+20240611-1 are fine.
signature.asc
Description: This is a digitally signed message part.
On Mon, 19 Aug 2024 11:41:59 +0200 Christoph Anton Mitterer
wrote:
> On Mon, 2024-08-19 at 05:12 +0200, Marco d'Itri wrote:
> > > With the new version, initramfs generation gives:
> > I know, the plan it to rebuild dracut-install.
>
> Thanks. Then I guess from my side we could also already close
Control: affects -1 dracut initramfs-tools
On Mon, 19 Aug 2024 16:18:44 +1200 Ash Joubert wrote:
> Control: severity -1 critical
>
> This bug is critical because the dracut failure results in a nonbootable
> initrd when followed by "apt-get install -f":
>
> update-initramfs: Generating /boot/i
On Mon Aug 12, 2024 at 1:43 AM CEST, Henrique de Moraes Holschuh wrote:
> > I got the *impression* that some heuristic was used to determine whether the
> > microcode update should be applied.
>
> No. It has a simple heuristic to not increase the initramfs size by adding AMD
> microcode updates unl
ow-ups:
>
>
> Pascal Hambourg wrote:
> > On 16/08/2024 at 00:27, Diederik de Haas wrote:
> > > On Thu Aug 15, 2024 at 10:24 PM CEST, Pascal Hambourg wrote:
> > >> Then I guess a 16 MiB unused partition could be added to relevant
> > >> recipes. Now,
On Fri Aug 16, 2024 at 8:39 AM CEST, Pascal Hambourg wrote:
> On 16/08/2024 at 00:27, Diederik de Haas wrote:
> > On Thu Aug 15, 2024 at 10:24 PM CEST, Pascal Hambourg wrote:
> >> Then I guess a 16 MiB unused partition could be added to relevant
> >> recipes. Now, whi
On Fri, 16 Aug 2024 13:37:48 +0200 Jonathan Carter wrote:
> Source: wlroots
> Version: 0.17.4-1
>
> Please consider updating wlroots to 0.18, as some new software need it
> as a dependency.
It's already available in Experimental. Note that the binary packages now have
"-0.18" in their names as
On Thu Aug 15, 2024 at 10:24 PM CEST, Pascal Hambourg wrote:
> Then I guess a 16 MiB unused partition could be added to relevant
> recipes. Now, which are the relevant recipes ? In other words, which
> arch/subarch need it ?
> Currently, partman-auto has the following recipes for ARM:
>
> recipes-a
On Thu Aug 15, 2024 at 5:50 PM CEST, Pascal Hambourg wrote:
> On 15/08/2024 at 16:25, Diederik de Haas wrote:
> >> I do not know any way to reserve unallocated space in recipes. The
> >> recipes could create a 16-MiB unused partition but the table in [2]
> >> lis
On Thu Aug 15, 2024 at 3:46 PM CEST, Pascal Hambourg wrote:
> On 15/08/2024 at 08:26, Holger Wansing wrote:
> > Am 15. August 2024 00:47:22 MESZ schrieb Diederik de Haas
> > :
> >>
> >> I'm not 100% sure if this fits into this subject/discussion, but .
On Mon Aug 12, 2024 at 1:05 PM CEST, Faidon Liambotis wrote:
> On Sun, Aug 11, 2024 at 12:31:21PM -0400, Reinhard Tartler wrote:
> > But you are right, ultimately this decision is up to the maintainer to make.
>
> Maintainer here :)
>
> For this particular case, I think removing -Werror made sense
On Thu Aug 15, 2024 at 8:26 AM CEST, Holger Wansing wrote:
> Am 15. August 2024 00:47:22 MESZ schrieb Diederik de Haas
> :
> >On ARM devices it would be very useful if the first 16MB would be
> >(automatically) reserved.
> >The U-Boot bootloader is normally put in th
On Fri Aug 9, 2024 at 10:08 PM CEST, Pascal Hambourg wrote:
> Guided partitioning with LVM already provides a feature to reserve space
> in the VG. Maybe it could be extended to guided partitioning with plain
> partitions.
I'm not 100% sure if this fits into this subject/discussion, but ...
On AR
On Sun Aug 11, 2024 at 6:31 PM CEST, Reinhard Tartler wrote:
> I'm afraid we'll have to agree to disagree
Agreed
signature.asc
Description: PGP signature
On Mon Aug 12, 2024 at 8:42 AM CEST, Petter Reinholdtsen wrote:
>
> Control: tags -1 + patch
>
> The following debian/patches/1020-ffmpeg-7.patch seem to fix the build:
>
> Description: More fixes for ffmpeg 7.0
> Use class method GetChannels() as a wrapper to get the ffmpeg version
> dependent i
On Sun Aug 11, 2024 at 4:56 PM CEST, Reinhard Tartler wrote:
> On 2024-08-11 08:55, Diederik de Haas wrote:
> > On 03 Aug 2024 11:08:58 -0400 Reinhard Tartler
> > wrote:
> >> I noticed this package is listed as low-NMU. As such, I'm taking the
> >> liberty o
Control: notforwarded -1
Control: tag -1 -fixed-upstream
On Sun Aug 11, 2024 at 3:43 PM CEST, Petter Reinholdtsen wrote:
> [Diederik de Haas]
> >> during a rebuild of the reverse dependencies for the transition to
> >> ffmpeg 7.0, your package failed to build
> >
>
On Sun Aug 11, 2024 at 3:43 PM CEST, Petter Reinholdtsen wrote:
> [Diederik de Haas]
> >> during a rebuild of the reverse dependencies for the transition to
> >> ffmpeg 7.0, your package failed to build
> >
> > Someone made a PR and that got merged upstream.
On 03 Aug 2024 11:08:58 -0400 Reinhard Tartler wrote:
> I noticed this package is listed as low-NMU. As such, I'm taking the
> liberty of uploading the following patch as NMU to sid:
> ...
> new file debian/patches/don-t-fail-on-unknown-gcc-warnings.patch
> @@ -0,0 +1,20 @@
> +From: Reinhard Tar
On Friday, 9 August 2024 08:02:42 CEST Bernhard Wörner wrote:
> Hello Diederik
> Hello Vagrant
>
> You wrote, that there are now the board configs in u-boot:
>
> configs/mt7986a_bpir3_emmc_defconfig configs/mt7986a_bpir3_sd_defconfig
>
> But the arm-trusted-firmware is missing.
>
> Is it possi
On Wednesday, 7 August 2024 20:33:02 CEST Holger Wansing wrote:
> > > Could probably solve the long standing issue
> > > "#987503 swap partition only 1 GB instead of at least 1 x RAM size"
> > > stating that hibernation is broken for machines with RAM bigger than
> > > 1G...
> >
> > Do you mean to
On dinsdag 23 juli 2024 17:56:34 CEST you wrote:
> > during a rebuild of the reverse dependencies for the transition to
> > ffmpeg 7.0, your package failed to build
>
> In the upstream git repo there are 2 commits on 2024-04-13 which probably do
> fix the FTBFS issue, but don't make it compatible
On Wednesday, 31 July 2024 16:37:48 CEST Pascal Hambourg wrote:
> On 31/07/2024 at 00:38, Thomas Hahn wrote:
> > On Fri, 26 Jul 2024 14:00:51 +0200 Pascal Hambourg
> >
> > wrote:
> > > firmware-nvidia-graphics was installed on systems which already had
> > > firmware-misc-nonfree because firmware
On Wed, 03 Jul 2024 12:47:52 + Matthias Klose wrote:
> Package: src:wasmedge
> Version: 0.13.5+dfsg-1
> Usertags: ftbfs-gcc-14
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
> severity of this report will
Control: reopen -1
Control: retitle -1 Please extend NEWS to clarify what users can and should do
On Saturday, 27 July 2024 11:30:37 CEST Dan Jacobson wrote:
> Yes. The news item needs to warn:
>
> ** Warning: if you take no action, upon the next boot you might
> 1. Not be able to network.
> 2. N
On Saturday, 27 July 2024 10:54:22 CEST Dan Jacobson wrote:
> That's exactly what happened to me.
> Not all users automatically install recommends.
Those users are ofc allowed to make that choice, but they then also accept the
consequences that go with it.
What you asked for is exactly how it wa
Control: found -1 6.3.7-1
On Friday, 26 July 2024 10:49:00 CEST Stefan wrote:
> The complete sentence is:
>
> oldest non-working kernel is 6.3.7 (package linux-image-6.3.0-1-amd64),
> 6.3.5 (latest version of package package linux-image-6.3.0-0-amd64) works.
Excellent, that narrows down the 'sus
On Thursday, 25 July 2024 20:50:23 CEST Holger Wansing wrote:
> Diederik de Haas wrote (Tue, 23 Jul 2024 22:14:46
> +0200):
> > > > >Or as I phrased it in https://bugs.debian.org/1076582#27 :
> > > > >"Maybe that document should be updated for this CENTU
On 25 Jul 2024 16:35:40 +0200 Diederik de Haas wrote:
> Source: libliftoff
> Version: 0.4.1-1
> Severity: minor
> Tags: patch
>
> https://tracker.debian.org/pkg/libliftoff reported it had a problem with
> finding a new upstream release, which does exist, so I updated the
&g
358bab5c Mon Sep 17 00:00:00 2001
From: Diederik de Haas
Date: Thu, 25 Jul 2024 16:27:11 +0200
Subject: [PATCH] d/watch: Update uscan params
https://tracker.debian.org/pkg/libliftoff reported the following issue:
"Problems while searching for a new upstream version"
And it (apparently) di
Control: tag -1 upstream fixed-upstream patch
On Wed, 03 Jul 2024 12:33:34 + Matthias Klose wrote:
> Package: src:libliftoff
> Version: 0.4.1-1
> Usertags: ftbfs-gcc-14
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-14/g++-14, but succeeds to build with gcc-13/
1 - 100 of 1081 matches
Mail list logo
