Package: debian-cd
Followup-For: Bug #1031696
Thank you again Thomas.
I've opened a merge request at
https://salsa.debian.org/images-team/debian-cd/-/merge_requests/30
My Debian mirror is still under construction, hence the 'draft' status for
the merge request (to indicate that I'm not certain
Package: debian-cd
Followup-For: Bug #1031696
X-Debbugs-Cc: scdbac...@gmx.net
Please find below a proposed update to the commit message under discussion:
nonfree-firmware: when creating on-disc firmware links, use the same link
creation logic as archive-area links
This changeset swi
Followup-For: Bug #1031696
Thinking aloud: as an alternative, would adding the '-f' flag to MKISOFS
achieve the desired result for both documentation and firmware files, without
requiring any other changes?
(I'll mention as context that there are symlinks in the debian-faq tarball
that is used as
Package: debian-cd
Followup-For: Bug #1031696
> >Thinking aloud: as an alternative, would adding the '-f' flag to MKISOFS
> >achieve the desired result for both documentation and firmware files, without
> >requiring any other changes?
> No, then I expect we'll simply end up with duplicate copies
Followup-For: Bug #1031696
Control: tags -1 - moreinfo
I've been able to build local NETINST ISO images successfully using the merged
changes (thanks, Steve), and was also able to file-copy them to a FAT32
filesystem and successfully boot from that into Debian Installer using QEMU.
Building imag
Followup-For: Bug #1000955
Control: severity -1 normal
A summary of a side-discussion between Filippo and myself about this bug:
* Although the bug doesn't appear reproducible today, the cause hasn't been
confirmed.
* We both agreed that it makes sense for bugs to continue to stay open u
Source: pylint
Followup-For: Bug #1032544
X-Debbugs-Cc: w...@wrar.name, lu...@debian.org
> This may be related, or just a duplicate, to #1032043, fixed in the newer
> version which is already in testing.
Yep, agreed that the updated testing package upload fixes this.
(it looks like the testing d
Followup-For: Bug #960727
Control: block -1 by 1031909
Followup-For: Bug #1031696
On Mon, 13 Mar 2023 01:04:26 +, James Addison wrote:
> I've been able to build local NETINST ISO images successfully using the merged
> changes (thanks, Steve), and was also able to file-copy them to a FAT32
> filesystem and successfully boot from th
Package: debian-cd
Followup-For: Bug #1031696
On Wed, 15 Mar 2023 00:04:28 +, James Addison wrote:
> I haven't (have not) been able to install Debian from FAT32-based media
> created
> using file-copy from either of these two approaches.
> In both cases d-i integrity ch
Package: python3-tk
Followup-For: Bug #1031909
Dear Maintainer,
Please find a merge request on Salsa to resolve this issue for future versions
of python3-tk at
https://salsa.debian.org/cpython-team/python3-stdlib/-/merge_requests/5
This has been tested by installing the previous version of the
Followup-For: Bug #1031909
Control: tags -1 patch
Package: release-notes
Followup-For: Bug #1033065
X-Debbugs-Cc: 1005...@bugs.debian.org
Control: affects 1005863 net-tools
Control: tags -1 moreinfo
> While a kernel compiled for Geode LX (essentially a basic i686 without the
> optional CPU features) still ships in Debian, many packages enforce C
Package: release-notes
Followup-For: Bug #1033065
X-Debbugs-Cc: martin-eric.rac...@iki.fi
Hi Martin-Éric - I intended to send my previous comment to you, but forgot to
add you to on carbon-copy.
Roughly speaking: I'm wondering whether there is a way that we can scan i386
architecture packages in
Package: wnpp
Followup-For: Bug #1026277
Control: tags -1 - help pending
Based on developing a better understanding of Debian's usertags, I don't think
that the 'help' and 'pending' tags currently apply here, so I'm going to remove
them from the bug. Reasoning below:
* my interpretation of 'pe
Package: release-notes
Followup-For: Bug #1033065
X-Debbugs-Cc: martin-eric.rac...@iki.fi
I've used the following commands to confirm that the i386 sudo/1.9.9-1 package
contains the bugreport-relevant NOPL opcode:
# obtain an archived copy of the affected binary package
$ wget2
http://snapsh
Package: gcc-11
Followup-For: Bug #1005863
X-Debbugs-Cc: martin-eric.rac...@iki.fi
Control: affects -1 - sudo net-tools
Control: affects -1 + libjavascriptcoregtk-4.0-18
Control: affects -1 + gobjc++-12-x86-64-linux-gnu
Control: affects -1 + libfsapfs-dev
Dear Maintainer and Martin-Éric,
Using a
Package: gcc-11
Followup-For: Bug #1005863
X-Debbugs-Cc: martin-eric.rac...@iki.fi
Control: affects -1 + sudo
> That's three potential positives; in total, the check ran on approximately
> thirty-two thousand (32340, to be more precise) packages.
My apologies: there was a bug in the script to run
Package: gcc-11
Followup-For: Bug #1005863
X-Debbugs-Cc: martin-eric.rac...@iki.fi
Ok; I should have realised that scanning the entire contents of the i386
bookworm archive for particular opcodes across _all_ files on a single machine
seemed to complete surprisingly quickly..
Please find attached
Followup-For: Bug #1032347
X-Debbugs-Cc: gunna...@debian.org
Hi Gunnar - although we agreed to close this bug, I'd like to add a message
about your comment:
> At some point of time, when configuring the keyboard configuration on
> the system level, you apparently set that value. To see how it co
Package: gcc-11
Followup-For: Bug #1005863
X-Debbugs-Cc: martin-eric.rac...@iki.fi
> So my guess is that approximately 6-7% of i386 packages in bookworm _that
> contain binaries or shared libraries_ are susceptible to this bug.
...
> It's also a larger number of packages than we could expect ind
Package: gcc-11
Followup-For: Bug #1005863
X-Debbugs-Cc: debian-...@lists.debian.org, debian-rele...@lists.debian.org,
debian-pol...@lists.debian.org
Hi folks,
Bug #1005863 describes a gcc-11 behaviour that results in software that exits
ungracefully on Geode LX i686 hardware. Despite self-repo
On Mon, 20 Mar 2023 at 07:22, Bastian Blank wrote:
>
> On Sun, Mar 19, 2023 at 11:47:21PM +, James Addison wrote:
> > Would it be fair to raise the severity of this bug to a release-critical
> > level?
>
> No, it would be fair to remove Geode LX from the set of suppor
Package: release-notes
Followup-For: Bug #1033065
X-Debbugs-Cc: p...@debian.org, ballo...@debian.org
Dear Maintainer and Éric-Martin (with Bill on carbon copy),
Please find linked below a previous release note from Debian 9.0 (stretch)
that we could use to provide relevant user guidance:
https:/
Followup-For: Bug #1005863
X-Debbugs-Cc: ballo...@debian.org
Control: reassign -1 binutils 2.38-1
Reassigning this from package 'gcc' to 'binutils':
It looks like it is GNU binutils[1] (and in particular, the GNU assembler)
that is responsible for producing the assembly opcodes for a binary compi
Followup-For: Bug #1032347
Control: archive -1
Followup-For: Bug #1032351
Control: archive -1
Package: release-notes
Followup-For: Bug #1033065
X-Debbugs-Cc: elb...@debian.org
Control: severity -1 serious
Increasing this bug's severity to a release-critical, based on mailing list
discussion[1].
Paul: bug #1005863 has most of the relevant context for Debian, although I'd
recommend the foll
Followup-For: Bug #1005886
X-Debbugs-Cc: powe...@gmail.com
Control: reassign -1 cdimage.debian.org
Control: retitle -1 cdimage.debian.org: bookworm net-install CD hangs on
"Detecting Network Hardware"
Sorry (both to you Tony, and also the Debian CD team) for confusion and wasting
time - I mistake
Package: apt
Severity: wishlist
Similar to the way that 'apt changelog ' displays the changelog for a
given package -- and downloads the relevant entries if they are not available
locally -- it could be convenient to allow users to review dpkg-parsechangelog
compatible NEWS.Debian.gz history for p
Source: x265
Version: 3.5-2
Severity: wishlist
Dear Maintainer,
The use of nasm 'ALIGNMODE p6'[1] in upstream's x265 source results in the nasm
assembler emitting multi-byte no-op (NOPL) instructions that are not compatible
with all systems within Debian's i386 baseline (for example: Geode LX doe
Followup-For: Bug #1005863
Control: affects -1 = sudo
Source: libselinux
Followup-For: Bug #1022964
X-Debbugs-Cc: hel...@subdivi.de
Hi Helmut,
Could you check whether the patch is missing a 'call ruby_env' line in the
debian/rules 'override_dh_auto_clean' target?
(it looks like it could be, but I may be mistaken)
Thanks,
James
Package: rustc
Followup-For: Bug #973414
X-Debbugs-Cc: martin-eric.rac...@iki.fi, fierel...@gmail.com, s...@debian.org,
ru...@packages.debian.org
I've been trying to track down 'NOPL' opcodes in Debian's i386 bookworm archive
and many of the affected cases appear Rust and/or LLVM-related.
The si
On Fri, 24 Mar 2023 at 13:50, Helmut Grohne wrote:
>
> Thank you very much for your review and the attention to detail. I
> concur with your observation and have updated the patch accordingly.
> This part slipped my testing, because I never tried the clean target and
> most cross builds never clea
Followup-For: Bug #973414
On Fri, 24 Mar 2023 14:23:18 +, James wrote:
> In particular, one area to look at:
>
>
> https://github.com/llvm/llvm-project/blob/llvmorg-14.0.6/clang/lib/Driver/ToolChains/Arch/X86.cpp#L25-L70
Line range correction:
https://github.com/llvm/llvm-project/blob/
Package: rustc
Followup-For: Bug #973414
> On Fri, 24 Mar 2023 14:23:18 +, James wrote:
> > In particular, one area to look at:
> >
> >
> > https://github.com/llvm/llvm-project/blob/llvmorg-14.0.6/clang/lib/Driver/ToolChains/Arch/X86.cpp#L25-L70
>
> Line range correction:
>
>
> https://g
Package: graphite-carbon
Severity: minor
Tags: patch
X-Debbugs-Cc: j...@jp-hosting.net
Dear Maintainer,
It looks like the 'debian/watch' file for graphite-carbon may be outdated.
PyPi has updated their simple package index pages to update the hash format
associated with each published package f
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: j...@jp-hosting.net
* Package name: python3-surt
Version : 0.3.1
Upstream Author : Raj
* URL : https://github.com/internetarchive/surt.git/
* License : AGPLv3
Programming Lang: Python
Description : transfor
Initial release. Closes: #1026277
Regards,
--
James Addison
Package: sponsorship-requests
Followup-For: Bug #1025642
The copyright file from the latest package on mentors.debian.net is clearer,
thanks!
However: I think we should still clarify that 'default_theme.c' is _also_
covered by the default-applied BSD-2-Clause license terms of the package.
The De
Source: harfbuzz
Followup-For: Bug #1029845
Potentially relevant context:
- https://github.com/flutter/flutter/issues/16886
- https://lists.debian.org/debian-legal/2011/05/msg5.html
Source: harfbuzz
Followup-For: Bug #1029845
Based on the previous: I think that the font was probably accidentally
committed to source control while testing a fix for the issue reported on
GitHub - and so following upstream's removal of the font seems to make sense,
given that there doesn't appear
Package: debian-policy
Followup-For: Bug #1029211
Hi Gunnar,
Please find linked below two edits based on initial proofreading of your patch:
-
https://salsa.debian.org/jayaddison/policy/-/commit/775f589a7cf0c27ee7103eec7a16b29eccbf3d02
-
https://salsa.debian.org/jayaddison/policy/-/commit/0
Source: pygame-sdl2
Followup-For: Bug #1030177
Dear Maintainer,
There's an upstream 'setuptools' issue[1] tracking these InvalidVersion
exceptions: basically, version parsing is checking for PEP440[2] adherence.
Updating the egg_info tag[2] for pygame-sdl2 to match the spec should resolve
the pr
Package: nsscache
Followup-For: Bug #1028454
Hi Thomas,
It looks like the functionality from python3-mock upstream[1] has been included
into Python >= 3.3. Would it make sense for nsswitch to migrate from mox3 to
the stdlib implementation instead of python3-mock?
Thanks,
James
[1] - https://gi
Package: www.debian.org
Followup-For: Bug #922621
Control: forwarded -1
https://salsa.debian.org/webmaster-team/webwml/-/merge_requests/207
Package: www.debian.org
Followup-For: Bug #791506
Dear Maintainer,
When I have *both* pt-BR and pt locales enabled in my browser (Firefox 102),
then this bug appears: the 'pt' Release Notes links appear in bold instead of
the expected 'pt_BR' links appearing in bold.
When I remove pt, then the p
Package: python3.10
Followup-For: Bug #1030530
Perhaps a strange or seemingly off-topic question, but: is it fair to assume
that Python 3.11's improved (typical) performance characteristics should likely
result in similar-scale energy consumption reductions?
(I'd be likely, although cannot guara
Source: openjfx
Followup-For: Bug #1026962
Could the following build-related scripting be something to do with it?
-
https://salsa.debian.org/java-team/openjfx/-/blob/debian/11.0.11+1-1.1/modules/javafx.web/src/main/native/Tools/Scripts/webkitdirs.pm#L494-499
-
https://salsa.debian.org/jav
Package: lintian
Followup-For: Bug #1028125
Hi Rene,
Do you know whether this is a regression (as in: did lintian/file previously
correctly identify the file type for GB18030.txt)?
There seems to be some code adjustments in libmagic recently, in particular
related to PE32 file types. I didn't m
Package: dhewm3
Version: 1.5.2+dfsg-1
Severity: normal
Dear Maintainer,
I've recently been looking at some of the dhewm3 upstream source code as part
of packaging another game based on dhewm3 (quadrilateralcowboy), and today I've
been re-reviewing the copyright entries in my package.
There isn't
Package: www.debian.org
Followup-For: Bug #791506
Control: retitle -1 [www.debian.org] Release notes are translated per-language,
not per-locale
> Content negotiation works well: if you have pt-BR and pt locales enabled in
> browser, and go to https://www.debian.org/releases/bullseye/releasenotes
Source: pytorch-vision
Version: 0.14.1-1
Followup-For: Bug #1030736
For this version, the control file contains[1] 'X-Python3-Version: 3.10, 3.11'.
Adding that configuration to the *dh-python* source package (as a test), the
'Depends' entry for the resulting .deb file contains:
Depends: python
Source: python-pycdlib
Followup-For: Bug #1030535
Control: tags -1 fixed-upstream
Dear Maintainer,
This Python3.11 compatibility issue (along with a few similar fixups) is
resolved in version 1.13.0 of pycdlib (latest at the time-of-writing is 1.14.0).
Thanks,
James
Source: pysdl2
Followup-For: Bug #1030676
Control: forwarded -1 https://github.com/py-sdl/py-sdl2/issues/227
Control: tags -1 fixed-upstream
It looks like this has been fixed upstream in version 0.9.12 of the library.
Package: nodejs
Followup-For: Bug #1030284
Hi Thorsten,
Are you able to determine whether https://github.com/nodejs/node/issues/41163
(and/or any of the guidance within that thread) seems relevant to this bug?
If so, your repro example could be useful to help upstream/contributors to
develop and
Package: wnpp
Severity: wishlist
Owner: James Addison
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: ruff
Version : 0.0.243
Upstream Contact: Charlie Marsh
* URL : https://github.com/charliermarsh/ruff/
* License : MIT
Programming Lang: Rust
Package: debian-i18n
Followup-For: Bug #1030856
Control: tags -1 moreinfo
Hi Nicola - please can you provide additional information for this bug report?
(for example: what language and locale options are available in the installer,
and what is not possible currently in the selection process?)
Source: pysdl2
Followup-For: Bug #1030676
On Tue, 07 Feb 2023 at 21:07:50 +, Simon McVittie wrote:
> I have intentionally not uploaded those versions to unstable when doing
> team-uploads to stop it from regressing and blocking libsdl2, because
> I have no good way to test them: nothing in Deb
Package: wnpp
Followup-For: Bug #1026277
Control: tags -1 pending help bookworm-ignore
Package: wnpp
Followup-For: Bug #1026277
Control: tags -1 -bookworm-ignore
Source: qemu
Followup-For: Bug #1030545
For anyone else looking into this bug: it seemed to me that 'qcow2.c' is a
likely candidate for this infinite looping[1] behaviour to originate from.
The fact that metadata preallocation is enabled when it occurs could be
relevant information too.
(my gues
Source: qemu
Followup-For: Bug #1030545
(ack - that does seem like an unusually-timed coincidence. continuing on with
some unrelated investigation, though...)
There's a commit[1] from Y2019 that appears to describe a similar set of
circumstances - iothreads blocked forever for a bunch of backend
Package: www.debian.org
Followup-For: Bug #791506
Never mind; I think that my suggestion to place both links in bold-format text
was probably quite strange and can be ignored. It was an attempt to find
something like a workaround or solution (debatable) within the constraints of
what is sensible
Source: python-xlib
Followup-For: Bug #838713
X-Debbugs-Cc: j...@jp-hosting.net, andre...@debian.org
Hello,
I agree with Emmanuel that the problem has been solved (for *most* releases of
Debian) by the existing patch[1] that replaces texi2html with makeinfo in the
python-xlib HTML documentation b
Source: python-suntime
Followup-For: Bug #1017073
X-Debbugs-Cc: j...@jp-hosting.net
Control: close -1 1.2.5-5
The package's changelog format is valid again in salsa following a refresh[1]
that re-combined a divergent development history. Release 1.2.5-5 looks good
in terms of build reproducibil
Source: sphinx
Followup-For: Bug #998059
X-Debbugs-Cc: debian-pyt...@lists.debian.org
(context: cross-posting based on an idea[1] that has been discussed upstream in
sphinx's GitHub repository about how to resolve locale-based build variance)
The SPHINXOPTS[2] environment variable provides a way
Package: wnpp
Severity: wishlist
Owner: James Addison
X-Debbugs-Cc: debian-de...@lists.debian.org, j...@jp-hosting.net
* Package name: quadrilateralcowboy
Version : 1.0.0
Upstream Contact: Brendon Chung
* URL : https://www.blendogames.com/qc/
* License
Source: pytango
Followup-For: Bug #1024078
As a maintenance note: it looks like upstream pytango v9.4.0 should resolve
this; it includes compatibility[1] with Python 3.11.
That release is currently planned[2] for the end of January, 2023.
[1] - https://gitlab.com/tango-controls/pytango/-/merge_
Package: wnpp
Followup-For: Bug #1026277
X-Debbugs-Cc: debian-devel-ga...@lists.debian.org
Hi folks,
This is my first attempt at Debian packaging: I've begun an effort to package
the GPLv3-licensed game "Quadrilateral Cowboy"[1][2], and would appreciate help
from potential sponsors.
It's possi
Source: psi4
Version: 1:1.3.2+dfsg-3
Followup-For: Bug #1027025
X-Debbugs-Cc: j...@jp-hosting.net
Based on some upstream discussion[1] of the same ImportError, it looks like
this is
related to the PYTHON_MODULE_EXTENSION suffix applied to the 'core' module at
build-time
by pybind11-related build
Source: psi4
Version: 1:1.3.2+dfsg-3
Followup-For: Bug #1027025
I've opened a merge request[1] to address what I thought was a cmake-related
build failure cause on Python 3.11, described in my previous message.. however
it looks like the package has built successfully since then - so I might hav
Source: python-ratelimiter
Version: 1.2.0.post0-3
Followup-For: Bug #1025119
It looks like the upstream package is no longer maintained[1], so it could be
challenging to find a good resolution for this bug.
There are a couple of unmerged possible fixes provided by contributors[2][3] --
personal
Source: gensio
Version: 2.5.1-2
Followup-For: Bug #1026667
Dear Maintainer,
Please find a merge request on Debian Salsa at
https://salsa.debian.org/debian/gensio/-/merge_requests/2 that addresses this
build failure.
Two fixups were required:
1. A hardcoded reference[1] to Python3.10 was adj
Dear Maintainer,
Please find a merge request hyperlinked below that is intended to
address the build failure described in this bug:
https://salsa.debian.org/pkg-llvm-team/halide/-/merge_requests/2
Thank you,
James
Source: sphinx
Version: 3.2.1-2
Followup-For: Bug #998059
X-Debbugs-Cc: j...@jp-hosting.net
After taking another look at this issue a couple of weeks ago, and some further
discussion with Chris on the relevant GitHub issue, it seemed like a better
approach (instead of disabling objects.inv outpu
Source: python-tomli-w
Followup-For: Bug #1024521
X-Debbugs-Cc: j...@jp-hosting.net
After puzzling over this same issue today (an empty .../usr/bin/ directory
entry appearing in the data.tar file of a python3-tomli_2.0.1-1 package), I can
confirm that the problem occurred with dh-python=5.202210
Source: python-tomli
Followup-For: Bug #994979
X-Debbugs-Cc: j...@jp-hosting.net
I'm reasonably confident that this bug can now be closed. From some digging
around earlier today:
- The dh-python update mentioned by Stefano addressed the direct_url.json build
reproducibility issue
- Despite a
acher wrote:
>
> On 2023-03-25 19:56:32 +, James Addison wrote:
> > Source: libass
> > Version: 1:0.17.1-1
> > Followup-For: Bug #1033381
> > Control: retitle -1 libass: nasm: use i386-baseline compatible NOP alignment
> > Control: tags -1 patch
> >
Package: wnpp
Severity: wishlist
* Package name: edit-tf
Version : 1.0.0
Upstream Contact: Simon Rawles
* URL : https://edit.tf/
* License : GPL-3
Programming Lang: HTML, JavaScript
Description : teletext frame editor for use within web browsers
edit-t
Package: dpkg-dev
Followup-For: Bug #1021292
X-Debbugs-Cc: woo...@wookware.org, debian-de...@lists.debian.org
> We decided that the best thing to do was create a new hardening flags
> feature called 'branch' to add to the existing set. This enables
> -mbranch-protection=standard on arm64, and
> -f
Package: rustc
Followup-For: Bug #973414
> Today I plan to rebuild rustc on Debian i386 with RUSTC_FLAGS (different to
> RUSTFLAGS) configured for i686 during the build. That's inspired by a comment
> here: https://github.com/rust-lang/rust/pull/31110#issuecomment-174327810
>
> To implement that
Package: lintian
Followup-For: Bug #1033294
X-Debbugs-Cc: patrice.dur...@gmail.com, debian...@lists.debian.org
As guidance for potential contributors: it looks like the logic for the
existing 'python-module-in-wrong-location' check (mentioned in the mailing list
thread) is here:
https://sources.d
Hi Brendon (and with the relevant Debian bug thread on cc),
I've uploaded a copy of the packaged quadrilateralcowboy game source -
with some small modifications and fixes, including ARM64 support - to
the 'mentors.debian.net' pre-review site at
https://mentors.debian.net/package/quadrilateralcowbo
Package: rustc
Followup-For: Bug #973414
X-Debbugs-Cc: fierel...@gmail.com
After a few false starts, I've built libstd-rust-dev:i386 targeting i686 in the
way I'd expected (and to clarify: the interpretation I'm using is to match
Debian's baseline and a strict-ish reading of what P6 / i686 was whe
ebian is viable on baseline hardware.
.
Ref: https://wiki.debian.org/ArchitectureSpecificsMemo#i386-1
Author: James Addison
Last-Update: Wed 29 Mar 18:24:38 BST 2023
Bug: https://bugs.debian.org/973414
Forwarded: not-needed
X-Not-Forwarded-Because: upstream consensus on i686 differs
---
---
rustc-1.63.0+dfsg1.o
Package: rustc
Followup-For: Bug #973414
X-Debbugs-Cc: fierel...@gmail.com
Hi Fierelier - thanks for your previous comment, here's my reply, slightly
later than I'd hoped:
On Wed, 29 Mar 2023 00:10:52 +0200, Fierelier wrote:
> - issue 1: i386, i486, i586, i686 are considered as Pentium 4 in LLVM,
Package: release-notes
Followup-For: Bug #1033564
X-Debbugs-Cc: anar...@debian.org
Hi Antoine - this seems related to - perhaps an extension of? - some discussion
on Salsa: https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/142
(I'll admit that I don't tend to use 'pipx' either. I
es
> > > that only process the packages detected by lintian.
On Mon, 20 Mar 2023 12:05:24 +, James Addison wrote:
> > That's not a bad idea. Are there any reasons that that might _not_ be a
> > good
> > idea before filing a wishlist bug? (performance, implicat
Followup-For: Bug #973414
X-Debbugs-Cc: fierel...@gmail.com
On Mon, 3 Apr 2023 23:07:35 +0200, Fierelier wrote:
> * In terms of confusion: I think using the Rust i586 toolchain, and
> building for i586 with Rust might be less confusing, because altering
> the i686 definitions for rustc will make i
Followup-For: Bug #994274
X-Debbugs-Cc: lu...@schwaighofer.name, pk...@debian.org, timo.lindf...@iki.fi
Hi Lukas, Philipp, Timo,
Does reverting the removal[1] of 'efisetjmp.h' from 'efi.h' in src:gnu-efi
produce successful results?
That occurred between gnu-efi versions 3.0.9 and 3.0.13 if I rea
Package: python3-sphinx
Followup-For: Bug #998059
X-Debbugs-Cc: la...@debian.org
Control: found -1 4.5.0
Control: notfound -1 5.0.0
Dear Maintainer,
My updated understanding is that this issue was fixed[1] in version 5.0.0 of
Sphinx.
I've documented[2] the process I followed using 'git bisect' t
On Mon, 19 Dec 2022 at 12:03, Simon McVittie wrote:
>
> If it's a DFSG engine with non-redistributable data, then it will
> need to go in the contrib archive area, and please look into teaching
> game-data-packager to make an accompanying non-redistributable -data
> package on users' systems. Quak
Source: mailman3
Version: 3.3.7-3
Followup-For: Bug #1028994
Dear Maintainer,
There is hopefully good news relating to this bug: upstream has discovered the
same problem and fixed it after version v3.3.7 - the fix is included in v3.3.8
of mailman3.
(the fix includes removal of a 'coroutine' de
On Tue, 17 Jan 2023 at 14:33, Pierre-Elliott Bécue wrote:
>
> I intend to do a full sweep on mailman suite in the next week, so don't
> worry too much! :)
Brilliant - thank you :)
Package: linux-image-6.1.0-1-rt-amd64
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
When attempting to boot a ThinkPad X230 from kernel build 6.1.0-1-rt-amd64, the
following error occurs (transcribed from screen; apologies in advance for any
typos):
[...] No filesy
Package: src:linux
Followup-For: Bug #1029336
Thanks, Salvatore - I can confirm that the issue is fixed after an install of
version 6.1.7-1 from 'unstable'.
The system _also_ boots fine after installing version 6.1.4-1 from 'testing'.
Perhaps there was a corrupt/misconfigured initrd build on the
Source: guidata
Followup-For: Bug #1028084
Dear Maintainer,
Maybe some good news:
It's possible that the Debian janitor has already taken care of the tasks
required to fix this failure, if the following analysis is correct:
- Upstream version v2.3.1 includes Python 3.11 compatibility[1]
- The
Source: djangorestframework
Followup-For: Bug #1028871
In pygments (an upstream dependency) version 2.13.0, HTML rendering was
updated[1] to use inline elements to encapsulate whitespace.
To address some resulting test failures, upstream pinned[2] to pygments version
2.12.0 recently.
Currently D
101 - 200 of 621 matches
Mail list logo
