I agree with automatic sorting of the output.
The -L option is useful for both humans and scripts, in both cases
sorting is either preferable or causes no problems (that I can think of.)
It can't be relied on that packages' internal file lists are in a
legible order.
Looking over the electrum link, it would appear this is an upstream bug. I am
going to look around upstream to see if it has already been reported, but if
not I will file a bug report. However, if anyone has time to get to it before
I do, feel free to go ahead.
--
Soren Stoutner
so...@debian
Package: libqt6widgets6
Version: 6.4.2+dfsg-10
Version: 6.8.2+dfsg-8
Severity: normal
Dear Maintainer,
In the default theme, QSortFilterProxyModel's arrows are backwards,
please consult attached screenshots of sample project
(https://www.walletfox.com/course/qsortfilterproxymodelexample.php).
I
On 5/10/25 5:26 AM, Chris Hofstaedtler wrote:
Source: xmake
Version: 2.9.9+ds-1
User: reproducible-bui...@lists.alioth.debian.org
Usertag: filesystem
Hi,
xmake's ./configure uses `find` to produce lists of build targets. The
files found are returned by `find` in filesystem order, which i
Source: xmake
Version: 2.9.9+ds-1
User: reproducible-bui...@lists.alioth.debian.org
Usertag: filesystem
Hi,
xmake's ./configure uses `find` to produce lists of build targets.
The files found are returned by `find` in filesystem order, which is
not deterministic.
This order then
quot;Exemple:" appears in the wrong place in one of the screens
where it appears.
I see that podebconf-display-po reconstructs the screens without access
to debian/templates (which is really convenient!).
On the other hand, maybe this behaviour (wrong order of some strings
that appear
Hi again Guido,
Today I created a loop 'for' to import several 'dsc' downloaded via debsnap
command. This loop was using the 'gbp import-dsc' command. For my surprise,
the order of upstream branches was truncated. So I added a 'sleep' command
after '
Package: linux-source
Severity: wishlist
Tags: upstream
X-Debbugs-Cc: corcodel.mar...@gmail.com
Hi
In linux kernel exist struct resource and i think is need some improvement in
order to parse easy from ACPI table:
Original structure bellow:
struct resource {
resource_size_t start
On 2025-02-28 13:28, Holger Wansing wrote:
I played around a bit on this topic, with gpt partition table both on BIOS
boot and UEFI boot, and I cannot reproduce such issue.
So, without further information I fear we cannot do much here...
Thanks for your efforts.
I will reinstall the box soon an
GPT partitions in "manual" mode, but d-i seems to
> >> have created them in a different order.
> >
> > Can you provide more details about how you created the partitions and
> > how they appear on disk ?
> > Ideally, can you attach /var/log/partman (if stil
On 2025-02-25 15:50, Pascal Hambourg wrote:
Control: reassign -1 partman-base
On 25/02/2025 at 14:43, Ralf Bergs wrote:
I created a bunch of GPT partitions in "manual" mode, but d-i seems to
have created them in a different order.
Can you provide more details about how you c
Control: reassign -1 partman-base
On 25/02/2025 at 14:43, Ralf Bergs wrote:
I created a bunch of GPT partitions in "manual" mode, but d-i seems to
have created them in a different order.
Can you provide more details about how you created the partitions and
how they appear on disk
Package: debian-installer
Severity: wishlist
Dear Maintainer,
I created a bunch of GPT partitions in "manual" mode, but d-i seems to
have created them in a different order.
I'm not sure if this is somehow mandated by GPT, but I don't think so,
I couldn't find anything
Control: tags -1 +confirmed
Joenio,
Preamble
Thank you for taking the time to prepare this package and your ongoing
contribution to the Debian project.
This review is offered to help package contributors to Debian mentors improve
their packages (where needed) prior to possible sponsors
Control: retitle -1 python-indexed -- Python dictionary indexed by
insertion order
: https://github.com/niklasf/indexed.py
* License : PSFL-2
* Vcs :
https://salsa.debian.org/python-team/packages/python-indexed
Section : python
The source builds the following binary packages:
python3-indexed - Python dictionary indexed by insertion order
To acce
p but at
> least I tried.
>
>
> Why should dependencies be installed in the correct order in the first place,
> in practice? Why can't they just be installed in a random order, and whatever
> crate needs to be actually compiled (or checked) is compiled/checked after
> t
generate the package's Cargo.lock, which needs all dependencies to be in the
registry in order to (at least) verify/compute checksums. The patch adds a
new `--no-lock` option that disables Cargo.lock generation/verification.
Building cargo with that patch and using the --no-lock option in dh-rust s
Package: dh-rust
Version: 0.0.10
Followup-For: Bug #1094199
X-Debbugs-Cc: noisyc...@tutanota.com, jo...@jones.dk, ben...@debian.org
Hi Jonas,
Just putting some ideas out there, not sure they will actually help but at
least I tried.
Why should dependencies be installed in the correct order in
Package: dh-rust
Version: 0.0.10
Followup-For: Bug #1094199
X-Debbugs-Cc: noisyc...@tutanota.com, jo...@jones.dk
Hi Jonas,
Has there been any progress on this bug? It is currently blocking the bindgen
transition (via oxigraph) and may possibly block other updates to come (some
evidence of this in
Quoting Santiago Vila (2025-01-26 13:41:18)
> affects 1094199 src:rust-curve25519-dalek
> thanks
>
> Hi. The new title fits perfectly with the problem
> in rust-curve25519-dalek I referred a few minutes ago :-)
Neat timing :-)
For the record, I guess you mean the below in bug#1094240:
Quoting S
affects 1094199 src:rust-curve25519-dalek
thanks
Hi. The new title fits perfectly with the problem
in rust-curve25519-dalek I referred a few minutes ago :-)
Thanks.
the fuse3 package or in the mount package.
> >
> > The problem is that mount passes the arguments of mount.fuse3 in the
> wrong
> > order.
> > Found by strace that this is what is passed:
> >
> > /sbin/mount.fuse3 -o rw,users,nosuid,nodev,exec sshfs#user@mac
On Tue, Jan 14, 2025 at 05:17:52PM +0200, Vassilis Virvilis wrote:
> Package: fuse3
> Version: 3.14.0-10
> Severity: normal
>
> Not sure if this a bug in the fuse3 package or in the mount package.
>
> The problem is that mount passes the arguments of mount.fuse3 in the wron
Package: fuse3
Version: 3.14.0-10
Severity: normal
Dear Maintainer,
Not sure if this a bug in the fuse3 package or in the mount package.
The problem is that mount passes the arguments of mount.fuse3 in the wrong
order.
Found by strace that this is what is passed:
/sbin/mount.fuse3 -o rw,users
Package: binutils-doc
Followup-For: Bug #1092870
Dear Maintainer,
I've completed testing the updated[1] patch using differing umask
and file system orderings (using disorderfs), and with the patch
applied, am able to build a reproducible result.
The sha256sum of binutils-doc_2.43.50.20250108-1_a
Package: binutils-doc
Followup-For: Bug #1092870
Dear Maintainer,
Apologies - my previous patch was malformed, and does not apply
cleanly. Please find attached an updated patch that removes two
mistaken newlines, removes two mistakenly added 't' characters, and
finally adds a DEP-3 Last-Updated
Package: binutils-doc
Followup-For: Bug #1092870
On Mon, 13 Jan 2025 01:52:20 +, I wrote:
> Test results from this process remain pending; it's taken me a while
> to figure out a suitable build commandline. To test the umask
> results before/after the patch, I intend to use:
>
> reprotest -
Package: binutils-doc
Followup-For: Bug #1092870
On Sun, 12 Jan 2025 15:56:58 +, I wrote:
> Please find the updated patch attached. I'll commence a test build
> of this locally using reprotest today.
Test results from this process remain pending; it's taken me a while
to figure out a suitabl
Package: binutils-doc
Followup-For: Bug #1092870
Control: tags -1 patch
On Sun, 12 Jan 2025 15:21:06 +, I wrote:
> I'll provide an updated gprofng-examples-tgz-deterministic.diff
> patch in a few moments to resolve these two items, and also to add
> the recommended[1] 'mtime' and 'pax-option'
examples.tar.gz file
in binutils-doc.
I believe that the filesystem read order and also umask-based
permissions applied to the source files when src:binutils is unpacked
also contribute towards nondeterministic output.
I'll provide an updated gprofng-examples-tgz-deterministic.diff
patch in
Package: g++-14
Version: 14.2.0-8
Severity: normal
Dear Maintainer,
* What led up to the situation?
When constructing a module file changing the order of importing system header
files may result in a compilation failure.
* What exactly did you do (or not do) that was effective (or
On 06/01/2025 at 08:16, Holger Wansing wrote:
Am 5. Januar 2025 14:40:32 MEZ schrieb Pascal Hambourg :
I found this bug report and thought it was a good idea so I rebased your commit on
current master and tested it on amd64/efi with and without efivars and on
amd64/generic -> ok.
Could you
Hi Pascal,
Am 5. Januar 2025 14:40:32 MEZ schrieb Pascal Hambourg :
>Hi,
>
>On Sat, 13 Jul 2019 09:24:06 +0200 Cyril Brulebois wrote:
>> Control: tag -1 patch
>>
>> Cyril Brulebois (2019-07-12):
>> > With stretch, we were getting efibootmgr's output in the installer's
>> > syslog, which could h
Hi,
On Sat, 13 Jul 2019 09:24:06 +0200 Cyril Brulebois wrote:
Control: tag -1 patch
Cyril Brulebois (2019-07-12):
> With stretch, we were getting efibootmgr's output in the installer's
> syslog, which could help track down issues related to the boot sequence.
>
> With buster, due to grub2's
.ds5-1) unstable; urgency=medium
[...]
-- Damyan Ivanov Sun, 29 Dec 2024 10:36:56 +
(i.e. in chronological order).
--
Vincent Lefèvre - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arith
Package: goldendict-ng
Version: 24.09.1-1
Severity: normal
Dear Maintainer,
goldendict-ng now needs qt6-svg-plugins (new package), instead of libqt6svg6,
in order to show its SVG toolbar icons.
Best,
Amr
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy
Control: forwarded -1
https://myrepos.branchable.com/todo/config___39__order__39___is_ignored_when___39__jobs__39_62__1/
Control: tag -1 patch
On Fri, 13 Dec 2024 11:51:43 +0300 Alper Nebi Yasak
wrote:
> I use git with git-worktree, so wanted to order those after the main
> reposi
Package: myrepos
Version: 1.20180726
Severity: normal
Hello,
I use git with git-worktree, so wanted to order those after the main
repositories they are part of, using the 'order' setting. However, I
see them processed out of order with e.g. jobs = 10.
A simple reproducer:
$ w
Package: kasts
Version: 24.08.3-1
Dear Maintainer,
kasts 24.08.3-1 should require qml6-module-org-kde-kirigamiaddons-settings as
runtime dependency, otherwise settings tab cannot
be accessed, i.e. "Settings" button in the bottom bar gets highlighted, but the
main page stays on whatever it was.
Programming Lang: Python3
Description : Python dictionary indexed by insertion order
indexed.IndexedOrderedDict (or indexed.Dict) is a Python dictionary that is
indexed by insertion order, it is feature compatible with
collections.OrderedDict as of Python 3.11 and can be used as a drop in
Package: desktop-base
Version: 12.0.6+nmu1~deb12u1
Severity: normal
X-Debbugs-Cc: debian.mournful...@passmail.net
If Konsole is started using krunner ssh-agent works. If Konsole is started
sing a shortcut ssh-agent is broken. This seems to be due to the way the
plasma session is initialised, and i
Package: bind9-doc
Followup-For: Bug #1064782
Control: fixed -1 bind9/9.20.2-1
Control: close -1
Hi Jonathan,
* Jonathan Kamens [2024-08-31 19:17]:
This is an edge case I don't know how to handle. We sort version
numbers in changelog entries in reverse order according to
apt_pkg.version_compare, which indeed considers 2:2.7.0-1+exp a newer
version number than 2:2.7.0-1. I checke
Thanks for the bug report.
This is an edge case I don't know how to handle. We sort version numbers
in changelog entries in reverse order according to
apt_pkg.version_compare, which indeed considers 2:2.7.0-1+exp a newer
version number than 2:2.7.0-1. I checked the Debian Policy Manual a
Package: bind9-doc
Followup-For: Bug #1064782
Control: tags -1 = upstream fixed-upstream
Package: bind9-doc
Followup-For: Bug #1064782
Control: forwarded -1 https://gitlab.isc.org/isc-projects/bind9/-/issues/4886
Package: qterminal
Version: 1.4.0-0ubuntu5
Severity: normal
File: /usr/bin/qterminal
Dear Maintainer,
When there are escape sequences, for example the ones that grep
sends to highlight found text in a different color, the display
order of right-to-left scripts like Hebrew and Arabic is
Package: apt
Version: 2.6.1
Severity: normal
apt.conf(5) talks about the ordering of the loading of config files,
but does not say why the order matters. At least not in the section
on ordering. (Behavor is implied where "clear" is explained.)
The present text (sid) is:
W
On 26/05/24 16:11, Luca Boccassi wrote:
See
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/162
I don't think anybody else here has the required knowledge to provide
any more info than we already have. Gioele could you please make a
recommendation and update the MR so that we can
s/162
> > >
> > >
> > This is indeed related. Yet the changes (as of today) do not seem
to fix
> > the order for `resolve'. This merge request seems to be waiting for
a
> > consensus before it can make progress.
>
> Indeed, we don't have a con
Control: tags -1 wontfix
Control: close -1
On Mon, 10 Dec 2018 14:21:33 +0100 Michael Biebl
wrote:
> Am 10.12.18 um 14:12 schrieb Michael Biebl:
> > Say you have test.service and test.target.
> > I'm not sure if there is a reliable way to detect whether the user
> > wanted test.service or test.ta
Package: wireplumber-doc
Version: 0.5.2-3
Dear Maintainer,
The "Locations of WirePlumber’s files" page is unclear about priority
in two places. The page starts with this statement:
WirePlumber’s default locations of its configuration files are
the following, in order o
Package: lists.debian.org
Severity: wishlist
X-Debbugs-Cc: nis.marten...@web.de
Dear listmaster,
The web archives like
https://lists.debian.org/debian-devel/
would be nicer to use if the latest months were listed first, because
right now it is always necessary to scroll down to reach the latest
a
Control: tags -1 moreinfo
Hi Patrick
On 2024-05-17 21:31:06 +0200, Patrick Winnertz wrote:
> Package: neovim
> Version: 0.9.5-7
> Severity: wishlist
>
> Hey,
>
> please add a neovim-dbg package so that it's easier to debug issues with
> neovim without the need to rebuild it locally.
Are you lo
Package: neovim
Version: 0.9.5-7
Severity: wishlist
Hey,
please add a neovim-dbg package so that it's easier to debug issues with
neovim without the need to rebuild it locally.
For that please compile with -g and without stripping :-)
(See: http://neovim.io/doc/user/debug.html)
Greetings
Pat
a broken AddSet() function, which results in
IPv4 and IPv6 addresses to be in reverse byte order at the nftables
level on LE systems (i.e. all release architectures but s930x).
This issue was confirmed to go away on LE systems once the bouncer gets
rebuilt against a fixed golang-github-google
: Expat
Programming Lang: Python
Description : Optimized Einsum is a tensor contraction order optimizer
Optimized einsum can significantly reduce the overall execution time
of einsum-like expressions by optimizing the expression's contraction
order and dispatching many operatio
* License : Expat
Programming Lang: Python
Description : Pytest plugin to randomly order tests and control random
seed
Randomness in testing can be quite powerful to discover hidden
flaws in the tests themselves, as well as giving a little more
coverage to your system. By resetting
(security, performance, and memory usage).
Installing mod_php also prevents configuring http2 in Apache, because it
depends on mpm_prefork.
Upstream recommends FPM and strongly discourages mod_php, so the package
should prefer FPM. Merely changing the order of dependencies to put fpm
first, wou
Package: apt-listchanges
Version: 4.4
Severity: normal
Hi Jonathan,
I just found that the changelog entries for cryptsetup are in the wrong
order:
$ mmdebstrap --include=cryptsetup-bin,apt-listchanges \
--chrooted-customize-hook="sed -i 's/testing/experimental/' \
/etc/apt/so
that the de-duplication is performed using a non-order-preserving
Python set[4] object, meaning that the resulting output documentation package
can vary at build-time.
Please find attached a patch that implements order-preserving de-duplication
of these tags. I've confirmed that the package
t, since two users
came even to the same solution.
After taking a step back I also find the solution quite elegant: It
preserves the order of the crypt devices as given by the local admin, it
just adds the devices that the local admin didn't specify while the
system knows a device is needed.
Package: imagemagick-6-doc
Version: 8:6.9.12.98+dfsg1-4
Severity: serious
Justification: Policy 7.6.2
On my new laptop, I can't upgrade the imagemagick packages
automatically from 8:6.9.11.60+dfsg-1.6 to 8:6.9.12.98+dfsg1-4
with aptitude (I need to enter the dependency resolution so
that imagemagi
On Sun, 5 Nov 2023 20:41:44 +0100 Sylvain Garrigues
wrote:
Le dimanche 5 novembre 2023, Michael Biebl a écrit :
>
> See https://salsa.debian.org/systemd-team/systemd/-/merge_requests/162
>
>
This is indeed related. Yet the changes (as of today) do not seem to fix
the order for `re
Le dimanche 5 novembre 2023, Michael Biebl a écrit :
>
> See https://salsa.debian.org/systemd-team/systemd/-/merge_requests/162
>
>
This is indeed related. Yet the changes (as of today) do not seem to fix
the order for `resolve'. This merge request seems to be waiting for a
co
Am 05.11.23 um 16:12 schrieb Sylvain Garrigues:
Package: libnss-resolve
Version: 252.17-1~deb12u1
X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org
The debian postinstall script for libnss-resolve inserts `resolve' in
the `hosts:' line of /etc/nsswitch.conf before `dns', therefore af
Package: libnss-resolve
Version: 252.17-1~deb12u1
X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org
The debian postinstall script for libnss-resolve inserts `resolve' in
the `hosts:' line of /etc/nsswitch.conf before `dns', therefore after
`files'. This does not seem optimal, as per `m
that
seems to have been left as is. I am now hitting the same issue on Debian
Bookworm.
update-initramfs does not generate entries of initrd's /cryptroot/crypttab in
the same order as system's /etc/crypttab, when entries tagged as "initramfs"
are placed before entries that
Package: mtr
Version: 0.95-1
Severity: normal
X-Debbugs-Cc: witold.bary...@gmail.com
user@debian:~$ mtr ‐-order "LSB" ::1
mtr: Failed to resolve host: ‐-order: Name or service not known
user@debian:~$ mtr ‐o "LSB" ::1
mtr: Failed to resolve host: ‐o: Name or service n
. Click the Application tab at the top.
> > 3. Press tab to cycle through the available LineEdit fields.
> > 4. Observe that the order is Application tab, Name, Description,
> > Comment, Environment Variables, Program, Browse button, Work path,
> > browse work path button,
ick the Application tab at the top.
> 3. Press tab to cycle through the available LineEdit fields.
> 4. Observe that the order is Application tab, Name, Description,
> Comment, Environment Variables, Program, Browse button, Work path,
> browse work path button, Arguments.
>
> The o
the order is Application tab, Name, Description,
Comment, Environment Variables, Program, Browse button, Work path,
browse work path button, Arguments.
The order is from top to bottom with the exception of Arguments being
skipped and then added last. The order should be completely top to
bottom. The
or disk ID.
I agree. That is why I used UUID for the fstab entries. But this drive
ordering issue is specific to the installer. The preseed is expecting
a /dev/sd* type of entry in order for partman to partition the correct
drive...or in my case (using software RAID1) drives.
If I understand
hat is why I used UUID for the fstab entries. But this drive
ordering issue is specific to the installer. The preseed is expecting
a /dev/sd* type of entry in order for partman to partition the correct
drive...or in my case (using software RAID1) drives.
> I advise to not hardcode /dev/sd* a
].
At [1] I've provided a minimal example to generate 2 ISO files with a small
difference.
With 'bsdtar -tf filename' it can be seen that the linked files are not
processed in the native order in the ISO file.
For comparison, 'isoinfo' outputs the files in the native order.
On 01/09/2023 at 01:17, Todd Morgan wrote:
When using the same method to install Debian 12, I am noticing that the
installer is detecting the drives out of order. It does not match what the
server BIOS or HPE ILO5 displays. With each PXE installation attempt the
ordering can vary. Looking in
PXE and a preseed file
for a touchless installation. This has been our standard method for Debian
installs for years, starting with "buster." It has worked VERY reliably for
us.
When using the same method to install Debian 12, I am noticing that the
installer is detecting the drives ou
y.49.137 dst=x.y.48.169
> > sport=35570 dport=636 src=153.0.170.10 dst=x.y.49.137
> > sport=636 dport=35570 [ASSURED] mark=0 use=1
> > ..
> >
> > Notice order of the 'src' address bytes.
> > When failover occures all TCP connections via
570
> dport=636 src=153.0.170.10 dst=x.y.49.137 sport=636 dport=35570 [ASSURED]
> mark=0 use=1
> ..
>
> Notice order of the 'src' address bytes.
> When failover occures all TCP connections via secondary balancer are
> broken as packets source addresses don't match
rk=0 use=1
..
bookworm:~$ sudo conntrack -L
..
tcp 6 431388 ESTABLISHED src=x.y.49.137 dst=x.y.48.169 sport=35570
dport=636 src=153.0.170.10 dst=x.y.49.137 sport=636 dport=35570 [ASSURED]
mark=0 use=1
..
Notice order of the 'src' address bytes.
When failover occures all TCP connections via se
Source: pytest-order
Version: 1.0.1-1
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild
Hi,
This package fails to build a source package after a successful build
(dpkg
-order. See the following command
after an import (important lines only):
$ git log
commit 17d263cee50d3f4b8ba881ca7216194672e7fdfb (HEAD -> debian/master, tag:
debian/1.9.4-2)
Author: Thiago Marques Siqueira
Date: Sun Jul 9 17:11:06 2023 +0100
[...]
commit 8b622b80fb70e9cbdbd071f1d7f714f3f9629
Hello,
I know what the problem is.
The problem is that nginx starts before all network interfaces are upped
up. I looked through all nginx unit files (nginx-common debian package)
and found that all versions, including Ubuntu 22.04, have incorrect
After & Wants.
All versions from the packag
I am seeing
upon the install following all upgrades and dist-upgrades.
(1) the monitors were out of order comared to how they were under MATE /
bullseye.
Using system/preferences/hardware/displays did not allow me to move the
displays in the proper order. (I had to shut the workstation down and
Source: python-pytest-random-order
Version: 1.1.0-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
your package implicitly depends on python3-py for its autopkgtest, which used
to be provided by python3-pytest. However, pytest has dropped that dependency
Source: src:eja
Severity: important
Dear Maintainer,
Could you repack in order to avoid to ship lua.
It will avoid false positive for shipping lua and avoid to accidentally compile
local lua instead of packaged lua
Thanks
Rouca
-- System Information:
Debian Release: trixie/sid
APT prefers
Source: blobby
Severity: important
Dear Maintainer,
Could you consider to repack in order to avoid to ship a non compiled lua ?
It is alway better to repack in this case, it avoid accidental compilation of
this embded library.
Rouca
-- System Information:
Debian Release: trixie/sid
APT
Source: bam
Severity: important
Dear Maintainer,
Could you consider to repack in order to avoid third party library like lua.
Even if they are not compiled, it could be accidentally compiled and thus is
not best pratice
Thanks
Rouca
-- System Information:
Debian Release: trixie/sid
APT
es reflect the order that was established by the
sorting (integer index value prepended to basename).
In case of sort-by-modification-time, the epoch with subseconds instead of
the index number is prepended. (Using Index number is also possible - with
two keystrokes.)
Arbitrarily reorder
On 2023-04-04, Vagrant Cascadian wrote:
> The files in the binutils tarball appear to be in arbitrary order,
> possibly affected by locale or filesystem differences:
>
>
> https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/armhf/diffoscope-results/binutils.html
>
>
Package: release-notes
Severity: minor
Tags: patch
Release Notes Maintainers,
In Chapter 2. What's new in Debian 12, the OpenJDK and OpenLDAP rows
are out of alphabetical order.
Patch (for the English version only) is below,
with the following fixes:
1) s/gnupg/gnupg2/
2) s/llvm-tool
Control: found 1033959 2.40-2
Control: found 1033958 2.40-2
Marking issues with versions in which it is still present.
live well,
vagrant
Some digging in the upstream stable-3.1 branch reveals two additional commits
required to resolve this regression:
https://trac.osgeo.org/postgis/changeset/11efb9f0cdc71cf2bdc4850491218495a07b18ba/git
https://trac.osgeo.org/postgis/changeset/8baf0b07b26df12d246c82bdae8ecd77371f3d24/git
With the
Source: binutils
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
The files in the binutils tarball appear to be in arbitrary order,
possibly affected by locale or filesystem differences
Package: ifupdown
Version: 0.8.35
Severity: normal
The man page of ifup(8) under "--all" option claims that "Interfaces are
brought down in the order in which they are currently listed in the state
file". However, the "for" loop seen below in read_all_state() fu
close 619265
thanks
Hi,
thank you for your report, however:
* the patches do not apply to the current upstream version anymore.
* even if they would, they are way to much of a burden to maintain
downstream/keep them debian specific and therefore rebase for every
new version, so they
On 2/16/23 15:05, Paul Cochrane wrote:
On Thu, Feb 16, 2023 at 02:44:36PM +0100, Sebastiaan Couwenberg wrote:
I'm not sure if it's worth the effort to fix this issue in bullseye with a
stable update. Since you've already done the work to patch package in
bullseye, can you prepare the stable upda
--
SRID=4326;POINT(-18.43494882292201 -89.27021258118658)
(1 row)
```
As one can see, the first element of the coordinate pair is completely
wrong.
We managed to isolate the problem to the issue [Polar Stereographic Axis
order wrong](https://trac.osgeo.org/pos
Package: strace
Version: 5.10-1
Version: 6.1-0.1
Severity: normal
Dear Maintainer,
When running this test program under strace, built with
cc qwe.c -g -target arm-linux-gnueabi -o qwe -fuse-ld=lld
(binary attached):
-- >8 --
#include
#include
#include
#in
1 - 100 of 2560 matches
Mail list logo
