Control: forwarded 1067952
https://lists.gnu.org/archive/html/bug-mes/2024-01/msg8.html
On 2024-03-29, Kentaro HAYASHI wrote:
> mes 0.26-1 fails to build on armhf.
>
> FYI:
>
> https://buildd.debian.org/status/fetch.php?pkg=mes=armhf=0.26-1=1704511792=0
Yeah, forwarded this upstream in
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
Control: forwarded 1064748 https://debbugs.gnu.org/69518
Control: tags 1064748 confirmed
The actual failed tests are:
test-name: fold-available-packages with/without cache
test-name: find-packages-by-name with cache
test-name: find-packages-by-name + version, with cache
test-name:
: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.
+(Closes
On 2023-09-26, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
...
>> cc1: error: ‘-fcf-protection=full’ is not supported for this target
>> make[3]: *** [/<>/Makefile:1816: include/generated/env.in]
>>
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:
Control: tags 1042918 pending
On 2023-08-02, Stefano Rivera wrote:
> I thought we'd managed to avoid this, in #1035645, but we just did the
> transition, and I see reprotest is FTBFS:
...
> py311: commands[0] .pybuild/cpython3_3.11_reprotest/build>
> .tox/py311/bin/python -m coverage r
> un
On 2023-07-16, Simon McVittie wrote:
> On Sat, 15 Jul 2023 at 18:27:24 +0200, Adam Borowski wrote:
>> But, what matters here is the CTTE ruling in #1035831 -- for the time being,
>> packages must not move files between locations affected by the aliasing.
>
> If that happens in reality, then yes,
On 2023-06-25, Ingo Saitz wrote:
> libdeb.so is both in binutils-x86-64-linux-gnu and binutils-msp430 in
> the same location. This was not the case in ~ti1, where libdeb.so was in
> /usr/lib/bfd-plugins/libdep.so. Thus the upgrade fails:
>
> Preparing to unpack
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&qu
c62fcbde299245ffcd027fd524f2fd2419d874c4 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Fri, 9 Jun 2023 18:44:06 -0700
Subject: Makefile: Ensure perl path is set to '/usr/bin/perl'.
Using 'which' to detect the path to perl may result in /bin/perl,
which is only typically available on usrmerge systems
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
Control: severity 1033845 important
Given that this only affects a single platform, and there are other
tested working boot options for this platform, I am downgrading the
severity to important.
On 2023-04-02, Wolf wrote:
> If the u-boot is installed on the internal emmc then u-boot is failing
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
Package: firefox-esr
Version: 102.9.0esr-1
Severity: grave
X-Debbugs-Cc: vagr...@debian.org
After upgrading to the latest firefox-esr, all web pages fail to display
anything... except those in my pinned tabs, although those also fail to do
anything other than display presumably cached content?
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
On 2023-02-01, Jérôme Charaoui wrote:
> I don't know how common that is in build environments, but it's not
> something that I have or think I should have in my build (sbuild) or
> test (autopkgtest) environments.
I was able to reproduce the issue with sbuild.
This appears to be because sbuild
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
Control: found 1029066 230
On 2023-01-17, Gianfranco Costamagna wrote:
> Hello, your package FTBFS when internet is not available during control file
> regeneration phase
...
> debian/tests/control.sh
> Generating the debian/tests/control file...
...
> ERROR: Could not find a version that
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"
On 2022-12-28, Rick Thomas wrote:
> A Cubox-i running Debian bullseye (11.6). According to versions> It has "u-boot-tools" (version 2021.01+dfsg-5) installed,
> but none of the u-boot- packages installed.
>
> If I reboot it and watch the serial console, I see it showing "U-boot
> 2021.01-dfsg-5"
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
On 2023-01-05, Christopher Obbard wrote:
> On Thu, 2023-01-05 at 13:21 -0300, Walter Lozano wrote:
>> Thank you for your help here! I also did some testing, and everything
>> looks OK. The only thing to mention is that the the script
>> u-boot-install-rockchip does not auto detect my board.
>>
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
On 2023-01-05, Christopher Obbard wrote:
> I've tested the following platforms and updated the wiki with my
> results:
>
>
> - roc-pc-rk3399, 2023.01-rc4+dfsg-1 from experimental
> - SD boot: works
> - MAC address: correctly derived from serial number
>
> - roc-pc-rk3399,
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
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 issu
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
Package: u-boot
Version: 2022.04+dfsg-2
Severity: serious
Control: fixed -1 2022.10+dfsg-2
X-Debbugs-Cc: vagr...@debian.org, m...@drkrebs.de, t...@cyrius.com,
i...@debian.org
At least two people have reported the same issue on sheevaplug and
guruplug failing to boot with a message "FDT and ATAGS
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:
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
- 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 inode::i_bdev, which was removed in Linux 5.11.
+- Use set_disk_ro() instead of set_device_ro(). The latter was not meant to
+
On 2022-12-13, 张 宁 wrote:
> I understand why it fail to boot.
>
> static int parse_label(char **c, struct pxe_menu *cfg)
> it failed to parse "kalsrseed", and move to uplayer, and uplayer still don't
> know how to handle it.
> and affected "append"
Thanks for looking into it!
> I don't have old
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:
Control: forwarded 1020087 https://github.com/artyom-poptsov/guile-ssh/issues/34
On 2022-09-18, Lucas Nussbaum wrote:
>> make[5]: Entering directory '/<>/debian/build/guile-3.0/tests'
>> PASS: log.scm
>> FAIL: server.scm
>> PASS: session.scm
>> FAIL: client-server.scm
>> PASS: popen.scm
>> PASS:
On 2022-10-11, Philip Rinn wrote:
> OK, I used a custom bootstrap script now and that works:
For clarity, sounds like you used u-boot-menu (at my suggestion), which
does not use boot scripts...
> U-Boot 2022.10+dfsg-1 (Oct 04 2022 - 00:06:38 +) Allwinner Technology
>
> CPU: Allwinner A64
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:
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:
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: normal
> Tags:
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:
Control: forwarded 1011863 https://issues.guix.gnu.org/55506
Control: tags 1011863 fixed-upstream
On 2022-06-08, Vagrant Cascadian wrote:
> On 2022-05-26, Vagrant Cascadian wrote:
>> On 2022-05-26, Lucas Nussbaum wrote:
>>> During a rebuild of all packages in sid, your packa
On 2022-05-26, Vagrant Cascadian wrote:
> On 2022-05-26, Lucas Nussbaum wrote:
>> During a rebuild of all packages in sid, your package failed to build
>> on amd64.
...
>>> PASS: tests/channels.scm - latest-channel-instances, missing introduction
>>> for 'gu
On 2022-05-26, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Thanks for doing the rebuild testing!
> Relevant part (hopefully):
Would it be at all possible to update your script to compress and attach
data over a certain size? This
Control: notfound 997434 2.9.1.4-4
On 2022-05-14, Vagrant Cascadian wrote:
> Version: 2.9.1.4-4
Given that the fixed version and the originally reported version are the
same... mark this as notfound in the original version. Hopefully that
actually works.
Seems like it was a transient toolch
1 - 100 of 374 matches
Mail list logo
