/../../../libguile-ssh/session-func.c:243:1: warning: control reaches end
> of non-void function [-Wreturn-type]
>243 | }
>| ^
This appears due to the update of libssh to 0.11.x. 0.10.x still built
fine when I checked a couple weeks ago, when I forwarded the issue
upstream.
live well,
vagrant
signature.asc
Description: PGP signature
least,
so I uploaded a new version of guile-gcrypt to trigger a rebuild.
live well,
vagrant
signature.asc
Description: PGP signature
Control: forwarded 1081025 https://github.com/epoptes/epoptes/issues/193
On 2024-09-06, Vagrant Cascadian wrote:
> Running epoptes on debian trixie results in:
>
> $ epoptes
> Traceback (most recent call last):
> File "/usr/bin/epoptes", line 20, in
>
python3-stdlib-extensions-3124-1-source-into-unstable/
live well,
vagrant
signature.asc
Description: PGP signature
Control: tag -1 pending
Hello,
Bug #1073710 in guix reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian/guix/-/commit/1cf003a48bcb2fa4d09776dd536e7425fe84660
1792&raw=0
Yeah, forwarded this upstream in January, but have not yet found a fix.
live well,
vagrant
signature.asc
Description: PGP signature
Control: fixed 1064748 1.4.0-6
Marking this as fixed in 1.4.0-6, although strictly speaking, this is
only worked around by disabling the tests, so the bug should remain
open.
live well,
vagrant
signature.asc
Description: PGP signature
-locations with cache
live well,
vagrant
signature.asc
Description: PGP signature
28 03:25:42.0 -0800
+++ lirc-0.10.1/debian/changelog2023-12-05 15:52:45.0 -0800
@@ -1,3 +1,28 @@
+lirc (0.10.1-7.3) unstable; urgency=medium
+
+ [ Vagrant Cascadian ]
+ * Non-maintainer upload.
+ * tools: Do not embed build date and kernel version in various files.
+(C
added to the default compiler
flags.
I have disabled this feature in git for now, although a better fix might
be preferred allowing this to be used on other targets where it did not
cause an issue.
live well,
vagrant
signature.asc
Description: PGP signature
Control: tag -1 pending
Hello,
Bug #1052724 in u-boot reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian/u-boot/-/commit/8ecfe9557fcfd217c2df88f183a4c3b3144
you want to replace py.test there with pytest.
Great suggestion! Worked for me locally and in salsa-ci.
Pushed to git:
https://salsa.debian.org/reproducible-builds/reprotest/-/commit/3d01047ae75ffc3fc30ad11aeec1a0dd9994d849
live well,
vagrant
signature.asc
Description: PGP signature
uld essentially
have to implement a reproducible builds style test to check for
differences...
After upgrading the infrastructure to bookworm, testing usrmerge
variations broke again, and so is currently disabled... though I have
configured the paths_vary_due_to_usrmerge issue so that old known issues
are not automatically removed anymore.
live well,
vagrant
signature.asc
Description: PGP signature
lso in package binutils-x86-64-linux-gnu 2.40.50.20230622-1
> Errors were encountered while processing:
> /var/cache/apt/archives/binutils-msp430_2.24~ti2_amd64.deb
Thanks for the report!
My bad, this points to some even deeper problems with the updates to
this package...
live well,
vagrant
signature.asc
Description: PGP signature
tested in unstable and experimental.
Thanks for maintaining manderlbot!
live well,
vagrant
From 1d8e42b99a87810397cd1c50c36c79d545192575 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Sat, 10 Jun 2023 07:10:24 -0700
Subject: [PATCH] debian/rules: Specify path to "erl"
instead of using 'which' to detect the path, which is
compatible with both usrmerge and non-usrmerge systems.
According to my local tests, with this patch applied bglibs should build
reproducibly on tests.reproducible-builds.org!
Thanks for maintaining bglibs!
live well,
va
r maintaining php8.2!
live well,
vagrant
From 830b885bf5495bd079bf698c7a3352ccf7a38633 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Thu, 13 Apr 2023 15:59:57 -0700
Subject: [PATCH] scripts/php*.in: Explicitly define the path to sed.
The full path is detected by configure, resulting
> CONFIG_CMD_BOOTZ=y
> @@ -56,6 +57,8 @@ CONFIG_LED=y
> CONFIG_LED_GPIO=y
> CONFIG_MISC=y
> CONFIG_ROCKCHIP_EFUSE=y
> +CONFIG_MMC_HS200_SUPPORT=y
> +CONFIG_SPL_MMC_HS200_SUPPORT=y
> CONFIG_MMC_DW=y
> CONFIG_MMC_DW_ROCKCHIP=y
> CONFIG_MMC_SDHCI=y
Would you consider submitting a patch upstream?
live well,
vagrant
signature.asc
Description: PGP signature
On 2023-03-15, Vagrant Cascadian wrote:
> After upgrading to the latest firefox-esr, all web pages fail to display
> anything...
...
> Are there any unversioned or missing dependencies on something that
> should also come from sid?
Apparently, it needs libnss3 2:3.89-1 from sid to w
from sid? I typically run bookworm, but occasionally
pull in specific packages from sid as desired. This usually has worked
fine over many years, so it is a bit surprising!
live well,
vagrant
-- Package-specific info:
-- Addons package information
-- System Information:
Debian Release
On 2023-02-02, Vagrant Cascadian wrote:
> On 2023-02-01, Jérôme Charaoui wrote:
>> Perhaps an alternative would be to add "puppet-agent" as a build
>> dependency, because that package will create a "puppet" user in the
>> environment.
And for complet
r things or has many other
dependencies. Would it make sense to have a package that just creates a
user and nothing else?
live well,
vagrant
signature.asc
Description: PGP signature
On 2022-12-29, Ian Campbell wrote:
> On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote:
>> dreamplug
>
> booting u-boot and Debian both from external mmc
>
> testing: 2022.04+dfsg-2+b1 "FDT and ATAGS support not compiled in" then
> resets and loops doi
t, xmlbeans, xxd, xz-utils,
> zip, zstd,
Confirmed that it also affects the version in bookworm:
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope.html
And according to test history, may go back to much earlier versions
(222+)... although there were some other possible FTBFS issues that may
have affected older versions, and I don't immediately see a way to look
at the logs from older versions.
live well,
vagrant
signature.asc
Description: PGP signature
Control: severity 1027176 important
On 2023-01-05, Vagrant Cascadian wrote:
> Control: retitle 1027176 u-boot-amlogic: broken non-EFI boot on amlogic boards
...
> At this point, I am assuming that all the amlogic builds are affected,
> and worst case we include the "noefi"
pful that shows with the reboot is
> CPU: Freescale i.MX6Q rev 1.3
> Board: MX6 Cubox-i
For Cubox-i install u-boot-imx and see
/usr/share/doc/u-boot-imx/README.Debian for instructions on how to
actually install the boot firmware onto microSD.
live well,
vagrant
signature.asc
Description: PGP signature
Control: retitle 1027176 u-boot-amlogic: broken non-EFI boot on amlogic boards
On 2023-01-05, Frédéric Danis wrote:
> On 03/01/2023 18:55, Vagrant Cascadian wrote:
>> Sounds like the bug *is* reproducible with unstable and experiemental
>> versions, from reading the logs; look
, we
> could add those in if we really wanted to. The 5.10 based kernels use
> devicetrees based on mainline, so are unaffected.
I would definitely be amenable to such a patch, although probably best
in a separate bug report and/or merge request. Could even use some
wildcards, if appropriate.
live well,
vagrant
signature.asc
Description: PGP signature
On 2023-01-04, Jochen Sprickerhof wrote:
> * Vagrant Cascadian [2022-12-28 16:56]:
>>> If you have access to any of these boards, please consider testing
>>> u-boot versions as packaged in debian for versions from debian stable
>>> (2021.01*), testing (2022
rrectly derived from serial number
Thanks for the tests!
> @Vagrant, about roc-pc-rk3399, can you please backport
> debian/patches/rockchip/rockchip-roc-pc-rk3399-Enable-rockchip-efuse-
> support.patch to the next unstable release ?
2023.01 should be released in a few days and I hope to
On 2023-01-03, Vagrant Cascadian wrote:
> On 2023-01-03, Vagrant Cascadian wrote:
>> On 2023-01-02, Vagrant Cascadian wrote:
>>> On 2023-01-02, Vagrant Cascadian wrote:
>>>> On 2022-12-28, Vagrant Cascadian wrote:
>>>>> The odroid-c2 fails to b
On 2023-01-03, Vagrant Cascadian wrote:
> On 2023-01-02, Vagrant Cascadian wrote:
>> On 2023-01-02, Vagrant Cascadian wrote:
>>> On 2022-12-28, Vagrant Cascadian wrote:
>>>> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
>>>>
On 2023-01-03, Frédéric Danis wrote:
> On 03/01/2023 18:55, Vagrant Cascadian wrote:
>> On 2023-01-03, Frédéric Danis wrote:
>>> Afaiu, the bug is not reproducible with unstable and experimental
>>> versions, but boot crash before starting the kernel, see
>>>
On 2023-01-02, Vagrant Cascadian wrote:
> On 2023-01-02, Vagrant Cascadian wrote:
>> On 2022-12-28, Vagrant Cascadian wrote:
>>> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
>>> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. Th
On 2023-01-03, Frédéric Danis wrote:
> On 29/12/2022 00:07, Vagrant Cascadian wrote:
>> On 2022-12-28, Vagrant Cascadian wrote:
>>> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
>>> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1
On 2023-01-02, Vagrant Cascadian wrote:
> On 2022-12-28, Vagrant Cascadian wrote:
>> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
>> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
>> commit triggering the issue h
On 2022-12-28, Vagrant Cascadian wrote:
> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
> commit triggering the issue has been identified as:
>
> a9bf024b2933bba0e23038892970a18b72dfaeb4
.10+dfsg-2 and
2023.01~rc4+dfsg-1 from Debian.
live well,
vagrant
signature.asc
Description: PGP signature
On 2022-12-29, Diederik de Haas wrote:
> On Thursday, 29 December 2022 00:21:05 CET Vagrant Cascadian wrote:
>> debian stable (2021.01*), testing (2022.04*), unstable (2022.10*)
>> and experimental (2023.01-rc*)
>>
>> # arm64
>> ...
>> rock64-rk3328
>
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> te
On 2022-12-22, Vagrant Cascadian wrote:
> On 2022-08-20, Vagrant Cascadian wrote:
>> On 2022-08-10, Vagrant Cascadian wrote:
>>> This bug is just to delay migration to testing while more platforms get
>>> tested. If you have a relevent board, please consider testing a
Control: tag -1 pending
Hello,
Bug #1011863 in guix reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian/guix/-/commit/6b1c4a4ff194a9e225c0629a87e7d3a218a8b2c
On 2022-08-20, Vagrant Cascadian wrote:
> On 2022-08-10, Vagrant Cascadian wrote:
>> This bug is just to delay migration to testing while more platforms get
>> tested. If you have a relevent board, please consider testing and
>> reporting the status:
>>
>> http
1 (Closes: #1005413):
+- Remove exception specifications
+ * Fix module build for recent kernel versions (Closes: #1005414):
+- Stop generating module vermagic in cloop.c. This has always been handled
+ by modpost and doing it here now results in build failure.
+- Avoid using i
eper problem... though
maybe it is the best we have.
For now I uploaded a version that reverted the kaslrseed support and
will test more thoroughly before re-uploading with the kaslrseed support
enabled again.
live well,
vagrant
signature.asc
Description: PGP signature
Control: tag -1 pending
Hello,
Bug #1025954 in u-boot-menu reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian/u-boot-menu/-/commit/ce91ec282087632dea7b1d5be
er 2022 and compatibility issues in guile-ssh's test suite.
I've confirmed the issue on guile-ssh 0.13.x, 0.15.x and 0.16.x locally,
and the reproducible builds tests also confirm this rough timing:
https://tests.reproducible-builds.org/debian/history/amd64/guile-ssh.html
Forwarded the bug upstream.
live well,
vagrant
signature.asc
Description: PGP signature
addr_r $fdt_addr_r"). I've seen this before, and don't recall
coming up with a resolution.
Wild guess; maybe the flash-kernel boot.scr gets the wrong console
settings (e.g. serial vs. hdmi or whatnot), while u-boot-menu just uses
the default console specified in the .dtb?
live well,
vagrant
signature.asc
Description: PGP signature
On 2022-08-10, Vagrant Cascadian wrote:
> This bug is just to delay migration to testing while more platforms get
> tested. If you have a relevent board, please consider testing and
> reporting the status:
>
> https://wiki.debian.org/U-boot/Status
Well, this turned out to be pre
Source: u-boot
Version: 2022.07+dfsg-1
Severity: serious
X-Debbugs-Cc: Vagrant Cascadian
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please consider testing and
reporting the status:
https://wiki.debian.org/U-boot/Status
live
Control: severity 1012996 important
On 2022-07-22, Vagrant Cascadian wrote:
> Looks like mes 0.24 test suite failed with GCC-12?
>
> I have not yet tried to reproduce it myself, but this is a bigger issue
> now that GCC-12 is the default compiler in Debian.
Yup, definitely fails
Control: tags 1016848 pending
On 2022-08-08, Graham Inggs wrote:
> Source: librecast
> Version: 0.5.1-2
> Severity: serious
>
> Hi Maintainer
>
> debian/control contains:
>
> Section: unknown
This was fixed in git a couple days ago:
https://salsa.debian.org
Control: tag -1 pending
Hello,
Bug #1016565 in librecast reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/vagrant/librecast/-/commit
Control: forwarded 1012996
https://lists.gnu.org/archive/html/bug-mes/2022-07/msg0.html
Looks like mes 0.24 test suite failed with GCC-12?
I have not yet tried to reproduce it myself, but this is a bigger issue
now that GCC-12 is the default compiler in Debian.
live well,
vagrant
On 2022-06-16, Matthias Klose wrote:
> Package: src:mes
> Version: 0.24-1
> Severity: norm
1 - 100 of 400 matches
Mail list logo
