This is bug 516201 - I'll merge them.
Upstream and I are working on fixing this, there are two patches
already proposed and we need to determine which is the correct way to
fix the problem.
Colin
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subje
t;
> we are down to two users in testing with one of them fixed in
> experimental.
Upstream committed the necessary changes to switch to the 1.1 API
earlier this month, so that should be in OpenSSH 7.9. There's usually a
release every few months, so I think we should be OK to just w
Package: pinta
Version: 1.6-2
Followup-For: Bug #877106
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Using the paintbrush tool
* What exactly did you do (or not do) that was effective (or
ineffective)?
o use them.
The project is effectively dead upstream and has been for some time.
This is mostly because it is no longer secure. It is for this reason
that I recommend it's removal.
Colin
On 18/11/17 14:04, Nomen Nescio wrote:
> You continue to misunderstand the bug report. This is not a feature
> request for 4k key support.
I know that. What you fail to realise is that the mixmaster
*specification* makes no mention of 4k keys!
bly?) the fix from #644421
should be restored and libedit should once again link against libtinfo
rather than libncurses.
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #741464 in grub2 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/grub-team/grub/commit/26f3349694ee739cc3711a7fd8a61be49b8d0e
nfiguration in the encrypted filesystem.
Thanks for following up. This is tracked in
https://bugs.debian.org/917117, and I've just committed a fix sent to me
for that, so the next upload to unstable should sort this out.
--
Colin Watson [cjwat...@debian.org]
On 21/02/2019 07:51, Andreas Tille wrote:
> I will apply the patch and do a team upload. Since I can not see any
> activity of Colin Tuckley I think it might be a good idea to move the
> package to Debian Games team. Colin, if I do not hear from you I assume
> you are OK with this
On Thu, Feb 14, 2019 at 09:44:46AM -0700, Kevin Locke wrote:
> On Thu, 2019-02-14 at 13:52 +0000, Colin Watson wrote:
> > On Wed, Feb 13, 2019 at 10:51:17PM -0700, Kevin Locke wrote:
> >> The problem is that the ellipsized choice text can't be mapped back
> >> to th
FWIW, the debconf bug that cut off the message has been fixed (in
1.5.70, although it required a follow-up fix in 1.5.71).
On Sat, Jan 19, 2019 at 11:49:54AM +0100, Vincent Lefevre wrote:
> On 2019-01-12 13:33:35 +0000, Colin Watson wrote:
> > I can see the argument that it might be conv
Control: tag -1 pending
Hello,
Bug #919029 in grub2 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/grub-team/grub/commit/e579f7503c1e5d3425c81dfc32c2d6cf818a4a
On Tue, Feb 26, 2019 at 04:01:33PM +0100, Vincent Lefevre wrote:
> On 2019-02-26 12:44:41 +0000, Colin Watson wrote:
> > Of course, the grub-pc maintainer script doesn't know either. All it
> > has available to it is a /dev/disk/by-id/ path that no longer points to
> >
Control: tag -1 pending
Hello,
Bug #922741 in grub2 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/grub-team/grub/commit/a4261650c1a446d8ef53a18b6e1fe9bd1097fc
in your name. I'll
upload it soon along with other pending changes.
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #919344 in openssh 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/ssh-team/openssh/commit/3115064e04541741d558cbb7b8ecab49ea
Control: tag -1 pending
Hello,
Bug #920269 in groff 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/groff/commit/8239da115b70c9194033c30aa4dfa83a74ac38c4
On Mon, Jan 02, 2017 at 12:37:32PM +0100, Thorsten Glaser wrote:
> On Sat, 31 Dec 2016, Colin Watson wrote:
> > The current postinst is certainly trying to use ucf in such a way, so
> > let's try to debug this. Please could you:
>
> Oh ok. Let me check that this system
ript returned error exit status
> 127
This is a bug in init-select, not in GRUB.
/etc/default/grub.d/init-select.cfg needs to check whether
/usr/lib/init-select/get-init exists before trying to invoke it, because
the package might have been removed but not purged.
(Fixing this properly for upgr
On Sat, Jul 21, 2018 at 02:22:16PM +0200, gregor herrmann wrote:
> On Sat, 21 Jul 2018 15:13:30 +0300, Niko Tyni wrote:
> > Not quite but we're close now (thanks again Colin!). The old Qt frontend
> > and the corresponding build dependency on libqtgui4-perl are still there
>
Control: tag -1 pending
Hello,
Bug #629405 in debconf 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/pkg-debconf/debconf/commit/5ac79b52c73e3db5f60266f55d65fa
quot;libqtgui4-perl based frontend
> might need to be removed") then.
That's now fixed, so as far as debconf is concerned you can remove
qt4-perl.
--
Colin Watson [cjwat...@debian.org]
; Test failed: 2018-08-14 00:00:37 Tuesday
Is this consistently reproducible? I think I've seen this locally on
occasion, but it's always gone away when I tried to debug it.
--
Colin Watson [cjwat...@debian.org]
> XUL addons are no longer supported.
Yeah, I think it's time to put this package to bed. ftpmaster, please
remove it.
Thanks,
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #812574 in grub2 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/grub-team/grub/commit/e4e7c3fae0fe7682f4c1215daeb6830716eb1b
o me to be a debconf bug rather than something that should
be worked around in grub-pc, though.
--
Colin Watson [cjwat...@debian.org]
the corresponding -signed version to
show up, if you need that, but in theory it should be on its way; I'm
not entirely familiar with all the archive-side plumbing that produces
that as yet.)
Thanks,
--
Colin Watson [cjwat...@debian.org]
On Sat, Jan 12, 2019 at 02:00:36PM +0100, Vincent Lefevre wrote:
> On 2019-01-12 10:36:02 +0000, Colin Watson wrote:
> > The rest of the bug is figuring out why the dialog box was
> > malformed. Perhaps it's because the long ID of /dev/dm-0 caused it
> > to overflow, and
On Sat, Jan 12, 2019 at 02:11:25PM +0100, Vincent Lefevre wrote:
> On 2019-01-12 10:36:02 +0000, Colin Watson wrote:
> > The ID changing is presumably the systemd bug you mentioned, and that
> > seems to be the grave part of this.
>
> Actually, I think that the fact tha
st the version of
grub-cloud-amd64 in stretch-backports needs to be fixed to stop
hijacking grub2-common's conffiles. After that has been done, I would
be happy to add Breaks/Replaces on grub-cloud-amd64 (<< fixed-version).
--
Colin Watson [cjwat...@debian.org]
On Wed, Jan 23, 2019 at 03:21:53PM +0100, Jakub Wilk wrote:
> * Colin Watson , 2019-01-23, 13:56:
> > Perl >= 5.20 has the safer <<>> operator,
>
> It was actually added only in Perl 5.22.
Sorry, indeed so - I grepped the perl*delta man pages for it but misread
&qu
On Wed, Jan 23, 2019 at 03:02:26PM +, Ralph Corderoy wrote:
> Hi Colin,
>
> > So this option would also lose support for Debian 8 (currently
> > oldstable).
>
> Also, `<<>>' doesn't support `-' to mean stdin.
> That might affect users
of the new upstream
option are quite different. "ssh -G " will print the
configuration that will be active when connecting to that host.)
--
Colin Watson [cjwat...@debian.org]
This is now fixed in unstable - package transition is unfortunately
blocked by a toolchain problem on arm* - so touching the bug *again* to
prevent removal.
This is now fixed in unstable - package transition is unfortunately
blocked by a toolchain problem on arm* - so touching the bug *again* to
prevent removal.
I don't think I need to trouble the release
team requesting a freeze exception to get it into bookworm; it can wait
until the next release. In the meantime, I recommend that you make your
minimal build environment truly minimal - it shouldn't have
non-build-essential packages installed.
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
My quick read of the situation is this looks like this is just a case of
the maintainer having stepped away -- I'd hate to see this package get
removed as we approach the bookworm freeze especially as I'm a user of
it. Can we get this package moved to it being up for adoption to at
least get th
.21-2
ii libnet-dns-perl 1.36-1
ii perl [libdigest-sha-perl] 5.36.0-7
libmail-dkim-perl recommends no packages.
libmail-dkim-perl suggests no packages.
-- no debconf information
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
applying the same
workaround there.
--
Colin Watson (he/him) [cjwat...@debian.org]
test_asynciothreadsafescheduler.py::TestAsyncIOThreadSafeScheduler::test_asyncio_threadsafe_schedule_action_due
=== 13 failed, 1309 passed, 10 skipped, 9 warnings in 20.51s
===
E: pybuild pybuild:386: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.11_rx/build; python3.11 -m pytest tests
This looks like https://github.com/ReactiveX/RxPY/issues/588, but it
also seems that we're several upstream versions behind. Would packaging
4.0.4 be in order? If this is too big a migration though (I see from
https://github.com/ReactiveX/RxPY/blob/master/docs/migration.rst that it
doesn't look entirely trivial), at least cherry-picking that fix for now
would probably be a good idea.
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #930531 in grub2 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/grub-team/grub/commit/f05b2405603e80801890b11fd887a172b8830e
led
Versions of packages gif2png depends on:
ii libc62.28-10
ii libpng16-16 1.6.36-6
Versions of packages gif2png recommends:
ii python 2.7.16-1
gif2png suggests no packages.
-- no debconf information
Thanks,
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #931038 in grub2 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/grub-team/grub/commit/8ea1f080e02eea50983d3b2f95c62badabe53e
lain how very disappointing that is.
That said, I see that nobody has yet linked to
https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html
in this bug, which discusses some issues with LUKS header format
versions. It's not clear whether that's the problem that everyone i
and things seem to work fine for me (without removing
--nounzip); my Xen system doesn't use UEFI, though.
I'm CCing a few folks who've contributed to GRUB's Xen support in one
way or another in the recent past; hopefully at least one of them can
help here?
Thanks,
--
Colin Watson [cjwat...@debian.org]
ding to any specific version, but rather
simply by upgrading or downgrading to *any* version with a different
interface between core image and modules. While this happens to have
been somewhat stable for a while, it could in principle change as
frequently as every single package upload, so the NEWS file isn't a
suitable place to discuss it.
--
Colin Watson [cjwat...@debian.org]
On Mon, Jul 15, 2019 at 01:51:59AM +0200, Diederik de Haas wrote:
> On maandag 15 juli 2019 00:33:31 CEST Colin Watson wrote:
> > > In the not too distant future, I'll remove that old drive (with WinXP on
> > > it) from my system and my guess is that I then will hav
try to the packages from stretch in order to make
> sure it's grub2 the culprit of the issues you are seeing?
For the record, the multiboot2 backports in question are still stuck
behind #930420, so aren't generally available yet. Trying the packages
*currently* in stretch will probab
h one of those questions and
answering them. Since you appear to have multiple disks, it seems quite
likely that the firmware might be booting from an EFI System Partition
that isn't the same as the one you have mounted on /boot/efi, and if so
then that's something you need to correct.
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #928727 in python-tblib 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/python-team/modules/python-tblib/commit/f153e2cd18054
t /dev/disk/by-id/ata-foo
/dev/disk/by-id/ata-bar' | sudo debconf-set-selections
sudo dpkg-reconfigure --unseen-only grub-pc
(I would not disagree that this should be easier; but this has been the
case for a long time, and isn't new in 2.04.)
--
Colin Watson [cjwat...@debian.org]
onfigure grub-pc" and select
all the disks that your firmware might boot from at the "GRUB install
devices:" prompt.
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #978515 in grub2 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/grub-team/grub/-/commit/fdff3397ab772d328e179bc34900f045df84
sulting /boot/grub/grub.cfg
* any output from "sudo update-grub"
--
Colin Watson (he/him) [cjwat...@debian.org]
upstream for a proper fix. I've proposed a better fix
just now:
https://code.launchpad.net/~cjwatson/lazr.config/zope.interface-5.0.0/+merge/396876
--
Colin Watson (he/him) [cjwat...@debian.org]
On Mon, Jan 25, 2021 at 10:59:28PM +, Colin Watson wrote:
> On Sat, Jan 02, 2021 at 12:24:05AM +, Debian Bug Tracking System wrote:
> >* Disable test `test_not_stackable` which fails for python3.9
> > (Closes: #970148)
>
> Thanks for sorting out the imme
you've upgraded openssh-server then that will include the updated
seccomp filters anyway. Changing openssh-server in buster might help,
but if so it would be much simpler to take the approach above
(backporting the seccomp filter fixes) rather than doing symbol
versioning hacks.
--
Colin
and 127.0.0.1
only. These pseudo-addresses are unconditionally available."
That's what sshd does in its default configuration. If it doesn't work,
the systemd documentation suggests that something else is not fulfilling
its end of a contract somewhere.
--
Colin Watson (he/him) [cjwat...@debian.org]
UEFI mode, grub-install ignores the device name you give it, and
always installs to the EFI System Partition on /boot/efi.
Could you please post the full output of "grub-install --debug"?
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #966575 in grub2 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/grub-team/grub/-/commit/e6f75471fd2046dbebcd6fc02585bb3c567b
Control: tag -1 pending
Hello,
Bug #973199 in python-libnacl 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/python-team/packages/python-libnacl/-/commit/4bb192
Control: tag -1 pending
Hello,
Bug #973199 in python-libnacl 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/python-team/packages/python-libnacl/-/commit/fb39af
b.
The upstream changes since 2.9.3 are not otherwise especially intrusive
(mostly new translations), so I think I'll deal with this by doing a new
upstream release and packaging that. I'm working on that now.
--
Colin Watson (he/him) [cjwat...@debian.org]
log something to dmesg,
which is probably the best that can be done. (I haven't tested that as
yet, though.)
--
Colin Watson (he/him) [cjwat...@debian.org]
I'm not opposed to some kind of mention in the release notes, I suppose,
but it feels like more of a general operations manual sort of thing (for
example, it might happen on the next upgrade after a subtly-botched disk
swap), and I'm not sure where would be best. This isn't particularly
specific to any one Debian release.
--
Colin Watson (he/him) [cjwat...@debian.org]
+= --with-libs=-lcrypt
endif
+# Avoid using libmd even if it's installed; see
+# https://bugs.debian.org/982705.
+confflags += ac_cv_header_sha2_h=false
+
# Everything above here is common to the deb and udeb builds.
confflags_udeb := $(confflags)
Thanks,
--
Colin Watson (he/him)
On Mon, Feb 15, 2021 at 01:52:59AM +0100, Andreas Henriksson wrote:
> On Sun, Feb 14, 2021 at 01:05:11PM +0000, Colin Watson wrote:
> > How about this approach instead? Given the choice between a
> > packaging-only change and one that requires another patch against
> > upst
Control: tag -1 pending
Hello,
Bug #982705 in openssh 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/ssh-team/openssh/-/commit/d0cee71ebcde7400f7caa1fcbf0f9973
On Mon, Feb 15, 2021 at 11:31:45AM +0100, Andreas Henriksson wrote:
> On Mon, Feb 15, 2021 at 09:41:30AM +0000, Colin Watson wrote:
> > FWIW, I think your patch in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982705#25 is correct
> > (even if I prefer to take a di
ave no such facility.)
So yes, I agree that there's not much point keeping this around in the
archive out of nostalgia. ftpmaster, please remove browser-history.
Thanks,
--
Colin Watson [cjwat...@debian.org]
nfmodule is
sourced to be called twice, which you probably weren't. This is
documented under HACKS in debconf-devel(7).
Thanks,
--
Colin Watson [cjwat...@debian.org]
ve for an exception.
I will upload it after the release. However I think there are still a
couple of minor bugs when it is used in testing that do *not* occur when
it is used in current stable. These are to do with editing text fields,
after using the 'del' or 'backspace' key to d
essing:
>cqrlog
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> Please get this fixed in jessie.
This is fixed in a pending upload.
However the pending upload is stalled by the release freeze due to
upstream changes which are too invasive.
Please downgrade this bug or otherwise flag it as pending so that cqrlog
users are not impacted.
Colin
y, so
let's try to debug this. Please could you:
* attach /var/lib/ucf/cache/:etc:default:grub
* attach /etc/default/grub
* show the output of "grep /etc/default/grub /var/lib/ucf/hashfile"
With any luck that will be enough to make some progress
l what it does. But this
was broken in devscripts 58eb4a4a5e006bf9a2589da0ef2f36aa0d81ed8c when
changing debuild to use dpkg-buildpackage --check-command.
I don't want to pass an explicit "don't run lintian" option, because
git-build-recipe should probably have much the same behaviour as the
documented (but no longer implemented) behaviour of debuild: that is,
run lintian if it's installed, but don't worry about it if it isn't.
Please restore the check for whether lintian exists at least in the case
where it was not explicitly requested by command-line option or
configuration variable.
Thanks,
--
Colin Watson [cjwat...@ubuntu.com]
On Tue, Dec 06, 2016 at 10:54:21PM -0500, James McCoy wrote:
> On Tue, Dec 06, 2016 at 10:39:44AM +0000, Colin Watson wrote:
> > […]
> > subprocess.CalledProcessError: Command '['/usr/bin/debuild',
> > '--tgz-check', '-i', '-I
On 22/07/17 10:08, Adrian Bunk wrote:
> This was fixed in 3.1-3, but the bug is back in 3.1-5
Sorry about that - a bit of confusion with two people working on the
package at the same time.
fixed in libsodium
1.0.13 (the failure was with 1.0.12).
Before embarking on any more time-consuming investigation, could the
build be given back to see if libsodium 1.0.13 helps?
gb python-libnacl_1.5.2-1 . all
Thanks,
--
Colin Watson [cjwat...@debian.org]
gt; a unit test.
Good point, thanks. I've sent a fix upstream as
https://github.com/saltstack/libnacl/pull/99.
--
Colin Watson [cjwat...@debian.org]
default and
just re-enable this, as it will probably go away eventually. Would it
be acceptable to add a NEWS file entry documenting this change, and
perhaps a release notes entry? That would give you a chance to make
adjustments before upgrading.
--
Colin Watson [cjwat...@debian.org]
. You can put the intended default for
that line ("#PermitRootLogin prohibit-password") in place and it will be
preserved appropriately.
--
Colin Watson [cjwat...@debian.org]
mpact is minimal.
> That seems maybe a worthwhile thing to do post-stretch?
Yep.
Cheers,
--
Colin Watson [cjwat...@debian.org]
ways
change later if there's progress on this upstream.
Thanks,
--
Colin Watson [cjwat...@debian.org]
tag 817771 patch pending
tag 833233 patch pending
thanks
Dear maintainer,
I've prepared an NMU for yapps2 (versioned as 2.1.1-17.4) and uploaded
it to DELAYED/0. Please feel free to tell me if I should delay it
longer.
Regards,
--
Colin Watson [
My previous NMU failed to build on the autobuilders due to a
pre-existing bug in debian/rules; the version of sbuild I tested with
didn't pick that up. I've uploaded this further change to fix that.
--
Colin Watson [cjwat...@debian.org]
diff -u ya
t the
*exact* output (there will be quite a lot of it):
sh -x /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg
--
Colin Watson [cjwat...@debian.org]
-friendly way.
Other than that, for people who don't see or don't fully read the
NEWS.Debian file I already provided, the best I can do is reassign this
to the release notes to lift some of these warnings up to there.
Thanks,
--
Colin Watson [cjwat...@debian.org]
t updated.
You already filed this bug and I already responded to it, so I'm merging
the duplicate.
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #926735 in parted 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/parted-team/parted/commit/82a400795e78b08f4cf3fbe1192353105
b-core/loader/arm/linux.c, grub-core/loader/efi/fdt.c should only be
compiled if GRUB_MACHINE_EFI is defined.
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #927888 in grub2 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/grub-team/grub/commit/000b835ba506ef3e0422c243209b2853cfb8c6
Control: tag -1 pending
Hello,
Bug #1005550 in password-store 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/password-store/-/commit/188c3d86aeef48ae7ac
this confusion is visible for Ubuntu users here:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1916651
I think this is worth fixing before it causes problems for users doing
stable upgrades.
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #990879 in base-passwd 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/base-passwd/-/commit/bf262828aae9a6ddbc6bcb539c
t that both grub-install and efibootmgr are getting EINTR here
(albeit with different subsequent effects) suggests to me that the
problem is at a lower level. This looks like it's probably a kernel
bug, or maybe (though less likely IMO) a bug in the efivar userspace
library. Reassigning to the kernel for now.
I suspect "strace -f -s 1024 grub-install --target=x86_64-efi" and
"strace -f -s 1024 efibootmgr" might be helpful, along with checking
dmesg to see if the kernel is logging any errors there.
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #940911 in grub2 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/grub-team/grub/-/commit/80ffd292d9cab51fd6f9adf60ae98f9cee84
ye.)
> Bug report 913916 seems to be related but I am not sure if it is
> reporting the same issue.
That was against 2.02~beta3-5+deb9u1, and I essentially rewrote
grub-install's UEFI boot variable handling in 2.02+dfsg1-14. It could
probably only be the same issue if it turns out
A65030AD50308659 -> ../../sda1
> lrwxrwxrwx 1 root root 10 Mar 8 11:15 DE31-8EDF -> ../../sda2
> lrwxrwxrwx 1 root root 10 Mar 8 11:14 a49dde0e-f2e4-4679-8c56-b9013d7b0fd2
> -> ../../sda5
> *** END /dev/disk/by-uuid
I notice that not all your partitions are mounted. What's on partitions
1, 3, and 4? ("sudo parted -s /dev/sda print" might help.)
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
ce /dev/sda1
>/var/log/grub-install.out 2>&1
... and then extract the resulting /var/log/grub-install.out file (e.g.
using the "Save debug logs" main menu entry)?
If you're able to also run "grub-install --debug /dev/sda1" on a working
buster system (assuming the PReP partition is on /dev/sda1 there too)
and provide the full output for comparison purposes, that would be
helpful as well. You may need to clear that partition first using dd,
but if so grub-install should tell you the necessary command.
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #934713 in os-prober 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/installer-team/os-prober/-/commit/4ba8cc3630c06873236965
1 - 100 of 1221 matches
Mail list logo
