On Wed, 31 May 2023 at 16:38, Cyril Brulebois wrote:
>
> Control: severity -1 wishlist
>
> James Addison (2023-05-31):
> > After the changes made to address bug #924301 (mountpoints for ext[n]
> > filesystems that have insufficient free blocks are not automatically
&g
Package: debian-installer
Followup-For: Bug #651280
X-Debbugs-Cc: debian-b...@lists.debian.org, skirpic...@gmail.com
Control: severity -1 serious
After the changes made to address bug #924301 (mountpoints for ext[n]
filesystems that have insufficient free blocks are not automatically checked
for
Source: hw-detect
Followup-For: Bug #1030519
X-Debbugs-Cc: a.dalm2...@googlemail.com
Hi Alexander,
I've been reviewing your patch and would like to suggest extracting the
following changes from it to consider and apply individually:
1. Supporting firmware filenames that contain spaces.
2.
Package: wnpp
Severity: normal
The bashdb utility looks useful for interactively debugging bash scripts, but
currently lacks a maintainer. It was previously included in Debian and was
removed[1] in Y2017.
[1] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870992
Followup-For: Bug #1035543
On Wed, 31 May 2023 09:55:13 +0100, James wrote:
> On Fri, 05 May 2023 11:04:29 +0200, Andreas wrote:
> > If I install systemd into the bullseye chroot and upgrade that to
> > bookworm, both systemd and e2fsprogs are still installed, but
> >
Followup-For: Bug #1035543
On Fri, 05 May 2023 11:04:29 +0200, Andreas wrote:
> If I install systemd into the bullseye chroot and upgrade that to
> bookworm, both systemd and e2fsprogs are still installed, but
> /etc/systemd/system/multi-user.target.wants/e2scrub_reap.service
> does *NOT* get
Package: e2fsprogs
Followup-For: Bug #1035543
X-Debbugs-Cc: ty...@mit.edu, bi...@debian.org, hel...@subdivi.de,
jspri...@debian.org, ans...@debian.org, a...@debian.org,
debian.bugrep...@wodny.org
Would a 'move /etc/systemd/system/default.target.wants/e2scrub_reap.service
to
Followup-For: Bug #1035543
X-Debbugs-Cc: ty...@mit.edu, bi...@debian.org, hel...@subdivi.de,
jspri...@debian.org, ans...@debian.org, a...@debian.org,
debian.bugrep...@wodny.org
I've been 'approximately' testing this locally on bookworm by:
* Editing the Install.WantedBy in
Package: release-notes
Followup-For: Bug #932957
X-Debbugs-Cc: hwans...@mailbox.org
Oops - there were a couple of problems with my most recent message here:
* Forgot to cc you on the details, Holger (in short summary: the ReST 'only'
directive[1] may be helpful here, and could be used with
Package: release-notes
Followup-For: Bug #932957
> Yes, filtering the content for the different architectures does not work yet.
Ah, and I said I would help with that :)
Although I don't yet know exactly how it's going to interact with the build
process, I _think_ that a feature we could use
Followup-For: Bug #1026277
On Sun, 28 May 2023 16:50:31 +0100, James wrote:
> * My release signing has been inconsistent, partly because I'm not sure I
> have a long-term commitment to being a Debian Maintainer/Developer, and
> partly because I'm not sure I can reliably keep those keys
Followup-For: Bug #1030835
X-Debbugs-Cc: charlie.r.ma...@gmail.com
Hi Charlie,
I'd like for 'ruff' to be packaged in Debian at some point, and am beginning
that process, although it could take some time (I'm not all that familiar with
Rust yet, and from what I've learned about the Debian rust
Followup-For: Bug #1026277
There are a bunch of mistakes that I've made along the way while attempting to
package this game. Some that I'd note are:
* I could've made more of an effort and waiting longer for upstream contact
before listing an upstream email address (sorry for any
Package: release-notes
Followup-For: Bug #932957
X-Debbugs-Cc: hwans...@mailbox.org
Hi Holger,
I noticed one more problem with the output of the ReST release-notes:
Filtering of architecture-specific sections does not seem to be taking place,
so the 'Supported Architectures'[1] section for
On Sun, 14 May 2023 15:21:24 -0400, Ted wrote:
> On Sun, May 14, 2023 at 06:03:59PM +0200, Michael Biebl wrote:
> > > Please reassign it there together with instructions how to fix it, i.e.
> > > what should be done in the maintainer scripts.
>
> Can someone send the instructions on how to fix
Package: wnpp
Severity: wishlist
* Package name: aerofoil
Version : 1.1.2
Upstream Contact: Eric Lasota
* URL : https://github.com/elasota/Aerofoil/
* License : GPL-2
Programming Lang: C
Description : Multiplatform port of 1994 Macintosh game 'Glider
Followup-For: Bug #932957
X-Debbugs-Cc: hwans...@mailbox.org
On Mon, 22 May 2023 23:40:46 +0100, James wrote:
> On Sun, 21 May 2023 10:16:36 +0200, Holger wrote:
> > There is also a problem using entities (or now called substitutions) in
> > quoted lines like
>
> > deb
Followup-For: Bug #932957
X-Debbugs-Cc: hwans...@mailbox.org
On Sun, 21 May 2023 10:16:36 +0200, Holger wrote:
> There is also a problem using entities (or now called substitutions) in
> quoted lines like
> deb https://deb.debian.org/debian RELEASENAME main contrib
Ok, yep - I understand
Followup-For: Bug #932957
X-Debbugs-Cc: hwans...@mailbox.org
Hi Holger,
> Please note the in the URL!
> I could not get this working with sphinx (if someone knows better, please
> contact me!)
Could the 'extlinks' feature[1] of Sphinx be helpful to migrate those?
(it allows defining URL
Package: e2fsprogs
Followup-For: Bug #1035543
X-Debbugs-Cc: a...@debian.org, bi...@debian.org
I'm having trouble reconciling these two log lines during the upgrade without
systemd:
ls: cannot access '/etc/systemd/system/multi-user.target.wants': No such file
or directory
...
Followup-For: Bug #1030545
X-Debbugs-Cc: ben...@debian.org, dipak.zo...@ibm.com
Hi Hilko (plus Dipak, fix author on cc for awareness),
Debian kernel package 5.10.179-1 that includes a fix for this has been accepted
into the stable-security (bullseye-security) suite today, and should resolve
this
Followup-For: Bug #1030284
I decline to participate further with this bugreport, although others are
welcome to pick up from the patches I've submitted (please don't merge them
as-is; modify them to apply corrections).
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@mirbsd.de
It does seem to (continue to) function, at least on x86:
~/dygraphs-2.2.0$ NODE_PATH=/usr/share/nodejs
../nodejs-18.13.0+dfsg1/out/Release/node /usr/bin/babeljs --config-file
$PWD/babel.config.json --compact false --source-maps inline
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@mirbsd.de
Hmm.. although the build itself succeeded, there was a unit test failure that
appears related to the change:
not ok 3213 sequential/test-fs-stat-sync-overflow
---
duration_ms: 1.111
severity: fail
exitcode: 1
stack: |-
checks can be
problematic
* places comparison constants on the lhs for safety
I'll post test results when they are available.
Cheers,
James
Description: Request an rlimit-determined stack size from V8
Author: James Addison
Bug-Debian: https://bugs.debian.org/1030284
--- /dev/null
+++ nodejs
On Sat, 13 May 2023 at 12:15, James Addison wrote:
>
> On Sat, 13 May 2023 at 11:14, James Addison wrote:
> >
> > On Sat, 13 May 2023 at 02:18, Thorsten Glaser wrote:
> > >
> > > James Addison dixit:
> > >
> > > >I'm going to stay invo
On Sat, 13 May 2023 at 11:14, James Addison wrote:
>
> On Sat, 13 May 2023 at 02:18, Thorsten Glaser wrote:
> >
> > James Addison dixit:
> >
> > >I'm going to stay involved with this thread, but I think that it is
> > >upon you to develop or provide fur
On Sat, 13 May 2023 at 02:18, Thorsten Glaser wrote:
>
> James Addison dixit:
>
> >I'm going to stay involved with this thread, but I think that it is
> >upon you to develop or provide further guidance towards a patch if
> >it's something you'd like to have implemente
On Fri, 12 May 2023 at 23:23, James Addison wrote:
>
> On Fri, 12 May 2023 at 16:54, Thorsten Glaser wrote:
> >
> > Yes, but given the usual ulimit, the new limit would be 4+ times
> > the old one, much much harder to reach.
>
> That does sound promising.
>
>
On Fri, 12 May 2023 at 16:54, Thorsten Glaser wrote:
>
> Yes, but given the usual ulimit, the new limit would be 4+ times
> the old one, much much harder to reach.
That does sound promising.
I've followed up on this discussion with the relevant upstream NodeJS
thread, and beyond there to the
On Thu, 11 May 2023 at 23:54, Thorsten Glaser wrote:
>
> James Addison dixit:
>
> >On Thu, 11 May 2023 at 02:43, Andres Salomon wrote:
>
> >> For ARM64, he says that raising the stack limit is not safe for v8
> >> *embedded inside WebView*, and therefore
On Thu, 11 May 2023 at 02:43, Andres Salomon wrote:
>
> On Sat, 11 Mar 2023 11:04:15 + James Addison
> wrote:
> > Package: nodejs
> > Followup-For: Bug #1030284
> > X-Debbugs-Cc: t...@debian.org
> >
> > Guidance received from the V8 project (
Followup-For: Bug #1035878
Control: reassign -1 linux-image-6.1.0-8-arm64
The RPi team suggested that this is likely to be a Linux kernel issue, and I've
tested an updated v6.1.21 kernel build of theirs (including the likely fix[1])
that does resolve the problem.
[1] -
Followup-For: Bug #1035878
Control: forwarded -1 https://github.com/raspberrypi/linux/issues/5462
Package: raspi-firmware
Severity: normal
Dear Maintainer,
I've installed a RPi 400 system using a regular build of Debian Installer
(bookworm RC2), and have begun using the official RPi firmware (as distributed
in the 'raspi-firmware' bookworm package - including bootcode.bin) to start the
the
Package: firmware-brcm80211
Followup-For: Bug #999485
X-Debbugs-Cc: gw...@gwolf.org, didi.deb...@cknow.org, 1023...@bugs.debian.org
Dear Maintainer,
> There is now a license available for the brcmfmac43456 firmware: it's included
> in the relevant RPF package metadata, in the usual copyright
On Mon, 8 May 2023 at 14:57, Diederik de Haas wrote:
>
> On Monday, 8 May 2023 14:08:14 CEST James Addison wrote:
> > On Mon, 1 May 2023 11:18:03 +0100, James Addison
> > wrote:
> > > > Diederik de Haas (2023-04-30):
> > > > > And that's exa
Package: firmware-brcm80211
Followup-For: Bug #1029843
X-Debbugs-Cc: k...@debian.org, didi.deb...@cknow.org,
debian-b...@lists.debian.org, p...@akeo.ie
On Mon, 1 May 2023 11:18:03 +0100, James Addison wrote:
> > Diederik de Haas (2023-04-30):
> > > And that's exact
Package: firmware-brcm80211
Followup-For: Bug #999485
X-Debbugs-Cc: gw...@gwolf.org, didi.deb...@cknow.org, 1023...@bugs.debian.org
> The other option is that they get included upstream in
> linux-firmware.git by upstream?
As an update about this: in the past it seems that one of the blockers
Followup-For: Bug #1035505
X-Debbugs-Cc: didi.deb...@cknow.org, 1029...@bugs.debian.org, k...@debian.org
Yep, those two issues seem accurate to me: splitting the config file list (a
trickier prospect than it seemed it should be, because newlines have been
converted into spaces), and then quoting
Source: firmware-nonfree
Followup-For: Bug #1035505
X-Debbugs-Cc: didi.deb...@cknow.org, 1029...@bugs.debian.org, k...@debian.org
Looks like a silently-handled exception here:
Source: firmware-nonfree
Followup-For: Bug #1035505
X-Debbugs-Cc: didi.deb...@cknow.org, 1029...@bugs.debian.org, k...@debian.org
Hey Diederik,
I think that the edits to 'debian/config/brcm80211/defines' may be the cause
of the space-escaping issue (noticed that in your fork on Salsa).
Building
ting systems on the same machine, other than to
mention that I do think it's highly compatible and that that's
something that maintainers, developers and users care about.
> On 2023.05.03 17:29, James Addison wrote:
> >* Perhaps Devicetree is a better default in EDK2 for ARM systems?
> > (
Package: src:linux
Followup-For: Bug #1029843
X-Debbugs-Cc: p...@akeo.ie, k...@debian.org, didi.deb...@cknow.org,
debian-b...@lists.debian.org, 1029...@bugs.debian.org, 1035...@bugs.debian.org,
989...@bugs.debian.org, debian-...@lists.debian.org
Control: retitle -1 brcmfmac: requested firmware
Followup-For: Bug #1030519
Control: unmerge -1
Control: reassign -1 hw-detect
Control: retitle -1 hw-detect: firmware file path handling is fragile
Control: unmerge 1029843 1030519
Control: reassign 1029843 src:linux
Control: retitle 1029843 brcmfmac: requested firmware filename
inconsistent with linux-firmware.git on non-devicetree systems
Control: affects 1029843 firmware-brcm80211 raspi-firmware
Dear Maintainer,
This bugreport relates to
On Wed, 3 May 2023 at 16:49, Cyril Brulebois wrote:
> James Addison (2023-05-03):
> > After editing and rebuilding the Device Tree (DTS) files, and
> > deploying those changes to the system, I can confirm that adjusting
> > the 'model' field value in there has no effec
Mystery may be (partially) solved. Responses inline below.
On Wed, 3 May 2023 at 15:17, Diederik de Haas wrote:
>
> On Wednesday, 3 May 2023 03:41:05 CEST James Addison wrote:
> > I think that the vendor name is coming from a DMI fallback:
> > ...
> > https://sources.deb
On Wed, 3 May 2023 at 03:02, Cyril Brulebois wrote:
> James Addison (2023-05-03):
> > I think that the vendor name is coming from a DMI fallback:
> > https://sources.debian.org/src/linux/6.1.25-1/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c/?hl=487#L4
On Wed, 3 May 2023 at 04:03, Cyril Brulebois wrote:
> James Addison (2023-05-01):
> > On Mon, 1 May 2023 at 17:53, Cyril Brulebois wrote:
> > I do see that guestfs-tools references[1] them, and I suppose other
> > downstream software could do as well. But within the insta
Control: retitle -1 hw-detect: firmware file path handling is fragile
Control: clone -1 -2
Control: reassign -2 src:linux
Control: retitle -2 brcmfmac: firmware filename inconsistency with
linux-firmware.git
On Wed, 3 May 2023 at 00:34, Cyril Brulebois wrote:
>
> James Addison (2023
Package: installation-reports
Followup-For: Bug #1035392
> The only customized dnsmasq setting required was:
>
> pxe-service=0, "Raspberry Pi Boot"
Oops, I lied. There was one other relevant dnsmasq setting:
dhcp-boot=bootnetaa64.efi
(telling the device what EFI filename to retrieve and
On Mon, 1 May 2023 at 20:03, Cyril Brulebois wrote:
> James Addison (2023-05-01):
> > Also, the brcmfmac kernel module code mentions[3] that it can load
> > board-specific firmware file paths. I'm not yet sure whether that's
> > relevant (either now, or in future).
>
&
Package: installation-reports
Severity: normal
Tags: d-i
Boot method: network
Image version: [2023-04-28] Bookworm Release Candidate 2 Installer
Date: 2023-05-02
Machine: Raspberry Pi 400
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev devtmpfs
On Mon, 1 May 2023 at 17:53, Cyril Brulebois wrote:
>
> James Addison (2023-05-01):
> > I understand that line of thinking, but we note that we have already
> > received feedback on Salsa[1] from a user whose Bookworm installation
> > workflow has been affected, and con
Source: preseed
Followup-For: Bug #1031643
As requested, the hostname-param-ignores-DHCP regression bug has been filed
separately: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035349
On Mon, 1 May 2023 at 16:00, Cyril Brulebois wrote:
> James Addison (2023-05-01):
> > Conditions:
> >
> > * Preseed alias 'hostname' configured on the kernel command-line
> > * There is a DHCP server on the installation-target's network that will
> > pr
Source: preseed
Version: 1.115
Severity: important
Tags: d-i
Dear Maintainer,
This bugreport is a subset/related-to bug #1031643, also in preseed.
When the 'hostname' preseed alias for 'netcfg/get_hostname' is provided to
Bookworm's RC 2 installer as a kernel command-line argument, the value
Source: preseed
Followup-For: Bug #1031643
X-Debbugs-Cc: car...@debian.org, a...@debian.org, freyerm...@physik.uni-bonn.de
Hi folks,
This is nitpicky, but I think there is an important-ish further detail to
report.
The fix applied does repopulate the 'hostname' variable so that env2debconf can
On Mon, 1 May 2023 at 03:00, Cyril Brulebois wrote:
> Diederik de Haas (2023-04-30):
> > I suggest we stick to `brcmfmac43455-sdio.raspberrypi,4-model-b.txt` as that
> > is its name in the upstream repo:
> > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
>
> Yes
Followup-For: Bug #1029843
X-Debbugs-Cc: a.dalm2...@googlemail.com, p...@akeo.ie,
debian-b...@lists.debian.org
Control: reassign -1 hw-detect
Control: merge -1 1030519
Control: affects -1 raspi-firmware
Control: title -1 check-missing-firmware: patch for files with space
characters, mediamount
Package: containers-storage
Followup-For: Bug #1034871
X-Debbugs-Cc: siret...@gmail.com, cy...@debamax.com, deb...@jfarr.cc
On Wed, 26 Apr 2023 07:11:50 -0400, Reinhard wrote:
> It indeed sounds like a significant papercut. I'm seeking for further
> thoughts and opinions: Is this something worth
Package: smplayer
Version: 22.7.0~ds0-1
Severity: important
Tags: upstream
Control: forwarded -1 https://github.com/smplayer-dev/smplayer/issues/668
Dear Maintainer,
There appears to be a problematic interaction between smplayer and mplayer
when running in a Wayland based environment:
When
Package: libgtk-3-0
Version: 3.24.37-2
Followup-For: Bug #1034289
Control: severity -1 important
As mentioned previously: although this bug seemed RC-level in the context of
Inkscape, libgtk3 has a sizable set of dependent packages, so in that context,
and given that release-preparation time is
On Mon, 24 Apr 2023 at 14:05, James Addison wrote:
>
> However: I do have problems playing an MP4 video file with the
> 'default' video output driver selected. Maybe that is the same issue
> with VAAPI.. or maybe something else. I'll spend some time to check,
> I think that eithe
On Sun, 23 Apr 2023 at 00:28, Nicholas D Steeves wrote:
>
> You're welcome! Also, yes, your hypothesis about DVB support being lost
> when the Debian packages adapted to upstream's waf-to-meson change was
> correct. The way always screen for this type of thing is using the
>
Package: libgtk-3-0
Followup-For: Bug #1034289
X-Debbugs-Cc: giuseppe.bilo...@gmail.com
Hi Giuseppe,
If possible: can you share some more information about your use-case for XIM
as an input method (either with Inkscape in particular, or more generally on
the relevant system(s)).
Thanks,
James
Followup-For: Bug #1034289
X-Debbugs-Cc: giuseppe.bilo...@gmail.com, debian-multime...@lists.debian.org
Control: reassign -1 libgtk-3-0
Control: affects -1 inkscape
Control: tags -1 patch
After testing the patch (that is based on a suggestion in an upstream GTK bug
discussion thread[1]), I can
Package: inkscape
Version: 1.2.2-2+b1
Followup-For: Bug #1034289
After installing a fresh Debian bookworm system and installing the 'inkscape'
package (version 1.2.2-2+b1), I can confirm that this issue is reproducible; it
can be found by running:
$ GTK_IM_MODULE=xim inkscape
... and from
/2560
[2] - https://gitlab.gnome.org/GNOME/gtk/-/issues/2560#note_757809
Description: gdkwindow: allow frame paint events to occur for non-toplevel
windows
.
Partially-reverts upstream commit fc569f1ac6ff108afc17f7f439480273826af3a6.
Author: James Addison
Bug: https://gitlab.gnome.org/GNOME/gtk/-/is
Source: mpv
Followup-For: Bug #1026060
X-Debbugs-Cc: s...@debian.org
Thanks, Nicholas!
Although I don't have a DVB device to test with locally, the fix makes sense
to me, and I'm glad to read from Alf's report that it is working.
Regards,
James
Source: mpv
Followup-For: Bug #1026060
X-Debbugs-Cc: patchesthomas@web.de, alf.debian...@gmx.de
Hi,
I haven't 100% confirmed this, but from some inspection it looks like DVB
support may be disabled-by-default based on the meson options[1] in the source
package for mpv.
The upstream source
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'
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
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
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, implications
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
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
/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.orig/compiler/rustc_target/src/spec/i686_unknown_linux_gnu.rs
+++ rustc
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
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
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:
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
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
>
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
:
>
> 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
> >
> > Pleas
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:
>
>
>
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:
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
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
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
Followup-For: Bug #1005863
Control: affects -1 = sudo
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
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
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
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
Followup-For: Bug #1032351
Control: archive -1
Followup-For: Bug #1032347
Control: archive -1
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
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:
201 - 300 of 497 matches
Mail list logo
