e 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]
se if
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 Watson (he/him)
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 ou
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]
oot/grub/grub.cfg
* any output from "sudo update-grub"
--
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:
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:
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:
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:
nstruct it to install to the right place, even if you
didn't do it as part of the initial recovery process.
--
Colin Watson (he/him) [cjwat...@debian.org]
if you do this interactively then hopefully it'll be
reasonably clear how to make whatever minor adjustments are needed. I
think it's essentially just the bind-mounts that you were missing when
you tried to chroot later on.)
--
Colin Watson (he/him) [cjwat...@debian.org]
we need to consider the migration path carefully. In terms of
specifics, I'm not sure I want to extend /etc/default/grub for this,
though; that has configuration file management issues, and generally I
don't really want to overload the upstream grub-mkconfig configuration
file with packaging-spec
Package: grub-efi-amd64
Version: 2.02+dfsg1-20+deb10u2
... and we can ask for more information from there.
--
Colin Watson (he/him) [cjwat...@debian.org]
of guesswork; that's one of my other suggestions in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966575#102. :-) We do
have to be pretty conservative though, as going overboard is likely to
break some multiboot setups.
--
Colin Watson (he/him) [cjwat...@debian.org]
problem that would have been exposed
by any change of a similar magnitude, I don't think it makes sense for
it to block migration of this new version to testing.
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #950473 in openssh-ssh1 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:
ackage is ready? This will make your
> package FTBFS as the and
> headers will be gone.
Ugh, sorry for the inconvenience - I'd neglected to subscribe to
openssh-ssh1 bugs and so didn't notice this report. Fixing now.
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #966211 in trn4 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:
agree it might be worth backporting this fix, but why would you be
updating libc on stable? (The only reason I can think of would be
partial upgrades to bullseye, which is hardly Severity: critical yet.)
--
Colin Watson (he/him) [cjwat...@debian.org]
the glibc-2.30 and glibc-2.31
tags upstream, though I haven't looked at the Debian patches.
--
Colin Watson (he/him) [cjwat...@debian.org]
On Tue, Jun 23, 2020 at 01:39:29PM +0200, Michael Meskes wrote:
> Colin Watson wrote:
> > man would be broken between the end of step 1 and the end of step 5.
> > I think this is undesirable and unnecessary.
>
> Good points. However, I still don't see where this creates prob
On Tue, Jun 23, 2020 at 11:02:02AM +0200, Michael Meskes wrote:
> Colin Watson wrote:
> > However, in order to make buster → bullseye upgrades work properly,
> > I think it's necessary to have bsdmainutils depend on bsdextrautils
> > for at least one release cycle. Otherwise
On Mon, Jun 22, 2020 at 09:18:59PM +0100, Colin Watson wrote:
> I'm going to upload man-db with a dependency on bsdextrautils |
> bsdmainutils (<< 12.1.1~) shortly. (There's been a bit of a delay
> because of some unrelated po4a-induced breakage that I had to stop and
> fix upst
need to consult man pages to work out what to do.
The only reliable way I can think of to avoid this kind of problem is to
have a hard dependency for a while as a transitional measure.
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #958236 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:
on3-wsgi-intercept (<< 1.9.0) once a fixed version exists in the
archive, so I'm cloning a part of this bug for that.
--
Colin Watson [cjwat...@debian.org]
up taking for pydoctor
was to take a copy of the bits of epydoc that they needed and port those
bits to Python 3 themselves.
(This is second-hand; I'm not on the Twisted team, but I contribute a
fair bit there and generally keep an eye on what they're doing since we
rely on Twisted at work.)
--
Col
t I deliberately keep in a clean state for
this sort of thing, and it worked fine for me.)
--
Colin Watson [cjwat...@debian.org]
On Sat, Jan 11, 2020 at 01:20:49PM +, Colin Watson wrote:
> I have some other things to do this weekend, but I'll chase this up with
> upstream and arrange for this to get into appropriate Debian packages.
It turned out that upstream had committed a fix a few days ago [1], so I
cherry-
Control: tag -1 pending
Hello,
Bug #946242 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:
things to do this weekend, but I'll chase this up with
upstream and arrange for this to get into appropriate Debian packages.
--
Colin Watson [cjwat...@debian.org]
On Mon, Dec 23, 2019 at 06:29:05PM -0500, Sandro Tosi wrote:
> Colin Watson wrote:
> > I've made a DELAYED/10 NMU to fix these bugs, as well as removing the
> > Python 2 binary package and fixing #911730. I think that gets things
>
> thanks for quickly addressing this. I
On Mon, Dec 23, 2019 at 06:42:00PM +, Colin Watson wrote:
> On Sun, Dec 22, 2019 at 06:57:24PM -0500, Sandro Tosi wrote:
> > Python 2 is end-of-life, and there are no more rdeps for python-yapps2, but
> > python3-yapps2 seems broken beyond repair: #911753, #911752.
>
debian.
> if i dont hear back within a week with a good reason to keep it, i'll file for
> its removal.
Please don't - keymapper needs it and isn't itself useless, and I
successfully ported keymapper to Python 3 despite the bugs in yapps2.
The bugs (which I filed) are annoying but not fat
On Thu, Dec 19, 2019 at 07:32:48PM +0100, Bastian Blank wrote:
> On Thu, Dec 19, 2019 at 05:14:11PM +0000, Colin Watson wrote:
> > OK, I bisected this to this commit:
> >
> > https://salsa.debian.org/waldi/ipxe/commit/56212b3037321d709184c5aed48b91b0a1bbd06e
> >
On Thu, Dec 19, 2019 at 04:32:32PM +, Colin Watson wrote:
> On Thu, Dec 19, 2019 at 04:15:55PM +0000, Colin Watson wrote:
> > With ipxe-qemu 1.0.0+git-20190125.36a4c85-1, it runs for a few seconds
> > then exits 0. With 1.0.0+git-20190125.36a4c85-2, it hangs apparently
>
On Thu, Dec 19, 2019 at 04:15:55PM +, Colin Watson wrote:
> With ipxe-qemu 1.0.0+git-20190125.36a4c85-1, it runs for a few seconds
> then exits 0. With 1.0.0+git-20190125.36a4c85-2, it hangs apparently
> forever (grub2's test suite kills it after a minute, but I've left it
ved.
Since you're building it locally already, it would be helpful if you
could follow the debugging instructions in a comment near the top of
sandbox-seccomp-filter.c (either the auditctl approach, or if that
doesn't work on such an old kernel, the ""uncomment this macro&q
On Fri, Aug 30, 2019 at 09:31:00AM +0100, Colin Watson wrote:
> Yep. I have a branch in progress locally to convert this to Python 3,
> but need to spend some time finishing it off and validating that it
> produces identical output.
I was stuck on this for a long time bec
' | 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]
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:
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]
e 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 probably not get you very
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 the
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]
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]
ery 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 in
this bug has, but
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:
epends 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 #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:
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:
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 #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:
t updated.
You already filed this bug and I already responded to it, so I'm merging
the duplicate.
--
Colin Watson [cjwat...@debian.org]
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]
s bug? The setup described in
https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no=924151#20
doesn't reproduce this problem, and I need something along those lines
that does reproduce this in order to fix it.
Thanks,
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 help
On Sun, Mar 10, 2019 at 05:30:02PM +0100, Joerg Jaspert wrote:
> On 15337 March 1977, Colin Watson wrote:
> > (Not by guided partitioning though, as I believe that always gives you a
> > separate unencrypted /boot right now, and you
Control: tag -1 pending
Hello,
Bug #891434 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:
Control: tag -1 pending
Hello,
Bug #924814 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:
n there.
Release team: is there some way to make sure that this mismatched
migration doesn't happen in future? It seems that the promotion
machinery ought to have prevented this, particularly due to the way it
caused Built-Using to be violated.
--
Colin Watson [cjwat...@debian.org]
hours of work left to do on it, not to mention upstream review.
However, I'm reasonably hopeful that I'll have this done for buster.
--
Colin Watson [cjwat...@debian.org]
talled or not (since the -signed image is monolithic
rather than relying on "insmod" commands). And it would be helpful to
get the full output of "grub-install --debug".
Thanks,
--
Colin Watson [cjwat...@debian.org]
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:
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:
in your name. I'll
upload it soon along with other pending changes.
--
Colin Watson [cjwat...@debian.org]
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:
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
> > a
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:
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 c
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 the cho
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]
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:
ff Perl scripts that use `<>'.
Ah, yes - in that case I agree that that isn't a good option.
--
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
s 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 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
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 de
rresponding -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]
something that should
be worked around in grub-pc, though.
--
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:
Control: tag -1 pending
Hello,
Bug #915735 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:
On Wed, Nov 14, 2018 at 05:02:08AM +, peter green wrote:
> keymapper depends on python-yapps2 which does not appear to exist, did
> you mean to depend on python-yapps?
Urgh, yes, silly mistake, sorry! Upload on its way.
--
Colin Watson
Much appreciated, thanks! I've cancelled my NMU.
--
Colin Watson [cjwat...@debian.org]
implementation-detail
workaround.)
Regards,
--
Colin Watson [cjwat...@debian.org]
diff -u yapps2-2.2.1/debian/changelog yapps2-2.2.1/debian/changelog
--- yapps2-2.2.1/debian/changelog
+++ yapps2-2.2.1/debian/changelog
@@ -1,3 +1,11 @@
+yapps2 (2.2.1-2.1) unstable
ntry_point
ModuleNotFoundError: No module named 'pkg_resources'
yapps2 needs to depend on python3-pkg-resources.
Thanks,
--
Colin Watson [cjwat...@debian.org]
e to
determine that there's an endless-loop-type bug here.
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #886178 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:
INUX_ROOT_DEVICE="ZFS=${rpool}${bootfs}"
+ LINUX_ROOT_DEVICE="ZFS=${rpool}${bootfs%/}"
;;
esac
Thanks,
--
Colin Watson [cjwat...@debian.org]
then it could easily
end up confused about which is the current scan code set (see the
changes to query_mode in particular) and so end up using the wrong set,
or possibly even send a nonsense command somehow. It seems worth
testing if you can.
--
Colin Watson [cjwat...@debian.org]
However, I think GRUB can at least manage to delete all but one entry
from the same distributor rather than all of them, and if it finds one
remaining entry then it can modify that rather than writing a brand new
variable. As I understand it, that would probably be enough to fix this
bug?
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #863801 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:
Control: tag -1 pending
Hello,
Bug #906470 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:
Control: tag -1 pending
Hello,
Bug #912034 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:
gainst yapps2 ...).
--
Colin Watson [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #910959 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:
Control: tag -1 pending
Hello,
Bug #908162 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:
r your patch there, which looks as
reasonable as it's likely to get - I'm having a few unrelated
difficulties getting a test environment completely working, but I'll
upload as soon as I've sorted that out.
--
Colin Watson [cjwat...@debian.org]
nd I
don't think you need to do this. I will consider your patch but have
been busy on a project at work that has a deadline of Wednesday, so
please hold off as if this patch is wrong it will be complicated to
unwind properly. I promise I'll look at it ASAP after Wednesday.
--
Colin Watson [cjwat...@debian.org]
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 wait f
> 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]
101 - 200 of 805 matches
Mail list logo
