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
Hi Sergei,
thank you, that works for me, too!
Cheers,
Lukas
Am 01.02.23 um 10:06 schrieb Sergei Golovan:
Hi Lucas,
On Tue, Jan 31, 2023 at 7:27 PM Lukas Märdian wrote:
Dear Sergei,
please switch the order of tk8.6's Recommends so that xterm is only the
fallback option if nothing
Hi Lucas,
On Tue, Jan 31, 2023 at 7:27 PM Lukas Märdian wrote:
>
> Dear Sergei,
>
> please switch the order of tk8.6's Recommends so that xterm is only the
> fallback option if nothing else provides x-terminal-emulator.
I won't switch the dependencies, but I'll dro
Package: tk8.6
Version: 8.6.13-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com
Dear Sergei,
please switch the order of tk8.6's Recommends so that xterm is only the
fallback option if nothing else pro
Package: src:linux
Version: 6.1.4-1
Severity: normal
X-Debbugs-Cc: yan...@web.de
Dear Maintainer,
after upgrading from linx-5.19.x to linux-6.0.x the priority order of
the internal battery (nonremovable) and the removable battery have
switched. The internal battery is considered nr. 0 by `acpi
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: haskell-byte-or...@packages.debian.org
Control: affects -1 + src:haskell-byte-order
Dear ftp team,
Please remove haskell-byte-order from 32 bit architectures, since it
depends on
Package: python3-h5py
Version: 3.7.0-3
Severity: normal
Dear Maintainer,
I am packaging pymca and when I build it I get this error message
D: dh_python3 pydist:173: trying to find dependency for h5py
(python=None)
D: dh_python3 pydist:277: invoking dpkg -S
*python3/*/[Hh]5[Pp][Yy]-?*.*-info
Control: found -1 2.4.7-4
Control: retitle -1 libtool: the generated run path order is incorrect,
yielding failures with "make check", e.g. for Solaris
Updated the title to mention Solaris, so that this bug report can be
found more easily (I currently have this issue only with Solaris
On Sun, Oct 02, 2022 at 04:00:58PM +0100, Colin Watson wrote:
> Control: tag -1 fixed-upstream
> Success!
> https://gitlab.com/cjwatson/man-db/-/compare/5d2594d0a0...866c3571d3
awesome!
On Sun, Oct 02, 2022 at 05:56:19PM +0100, Colin Watson wrote:
> I thought I'd set SOURCE_DATE_EPOCH, but I'd
On Sun, Oct 02, 2022 at 05:50:07PM +0200, Johannes Schauer Marin Rodrigues
wrote:
> Quoting Colin Watson (2022-10-02 17:00:58)
> > As well as more localized testing, I built a .deb with this and used
> > josch's instructions from the start of this bug to build mmdebstrap
> > tarballs via disorderf
Quoting Colin Watson (2022-10-02 17:00:58)
> Success!
>
> https://gitlab.com/cjwatson/man-db/-/compare/5d2594d0a0...866c3571d3
Thank you!! :D
>
> As well as more localized testing, I built a .deb with this and used
> josch's instructions from the start of this bug to build mmdebstrap
> tarbal
Control: tag -1 fixed-upstream
Success!
https://gitlab.com/cjwatson/man-db/-/compare/5d2594d0a0...866c3571d3
As well as more localized testing, I built a .deb with this and used
josch's instructions from the start of this bug to build mmdebstrap
tarballs via disorderfs, using
"--hook-dir=/usr/
Source: haskell-byte-order
Version: 0.1.3.0-1
Severity: serious
Tags: sid bookworm
X-Debbugs-Cc: sramac...@debian.org
haskell-byte-order is BD-Uninstallable on 32 bit architectures:
∙ ∙ haskell-byte-order unsatisfiable Build-Depends(-Arch) on armel:
libghc-wide-word-dev (>= 0.1.1)
∙ ∙ hask
Hi Colin,
On Sun, Sep 25, 2022 at 11:18:19PM +0100, Colin Watson wrote:
> This weekend's work has been:
> https://gitlab.com/cjwatson/man-db/-/compare/bb0f7086ba...5d2594d0a0
wow, impressive!
(and thank you for taking care of man-db for so many years now! :)
[...]
> I'll need a bit more conce
This weekend's work has been:
https://gitlab.com/cjwatson/man-db/-/compare/bb0f7086ba...5d2594d0a0
A lot of this was code rearrangement that I needed to do before I could
make progress on the real issues, but if you look at the NEWS.md diff
you'll see a number of changes that relate to this bug
Hi Colin,
On Thu, Sep 22, 2022 at 08:53:07PM +0100, Colin Watson wrote:
> Yeah, this has taken me a bit longer than expected, but I have in fact
> been making some progress. josch's patch has been very useful in that
> it provides an easy way to see differences between unsorted and sorted
> trave
ich other entries, so that the end result doesn't
change depending on the scan order. With that, I'm down to on the order
of 150 lines of diff of accessdb output against the result of josch's
patch, and I think there are only about one or two problems left.
A lot of the remaining diff
> "Sam" == Sam Morris writes:
Sam> When using a container image that has an older version of some
Sam> of the binary packages from krb5 in it, installing krb5-user
Sam> results in binary packages being installed that are a mix of
Sam> the newer and older version.
Thanks for f
hi!
Colin, what's the status of this bug? You said you were working on improving
josch' patch in May 2022...?! :)
Also, the bug is currently tagged 'patch', I guess it's appropriate to remove
that tag?
josch: btw you said you you submitted other patches missing freeing of memory,
have you update
Source: krb5
Version: 1.20-1
Severity: normal
X-Debbugs-Cc: s...@robots.org.uk
When using a container image that has an older version of some of the
binary packages from krb5 in it, installing krb5-user results in binary
packages being installed that are a mix of the newer and older version.
The
: Emacs completion style that matches multiple
regexps in any order
This Emacs package offers a completion style, that is an
completion matching engine, capable of matching multiple regexps,
each following different regexp syntax, in any order.
Aymeric Agon-Rambosson
Package: dh-cargo
Version: 24
Severity: normal
X-Debbugs-Cc: r...@graphiant.com
The order of the cargo:X-Cargo-Built-Using substitution generated by dh-cargo-
built-using for binary Rust packages can vary if LC_ALL is set when building.
This means that the contents of the binary package can vary
ng the resulting
> image with QEMU with Secure Boot enforced. Unfortunately, the
> OVMF_VARS*.ms.fd seems to define a boot order where the EFI shell is
> placed before the disk.
Hm.. that must be a side effect of enrolling the keys, but I'm not
sure why that would be. Certainly we cou
Package: src:linux
Version: 5.18.5-1
Severity: wishlist
X-Debbugs-Cc: yaslama+bugs.debian@gmail.com
Thanks!
riable to tar.
>>
>> It does not appear to affect the sort order on
>> tests.reproducible-builds.org, but it does appear to cause issues when
>> testing with reprotest, and so may occur in other situations in the
>> wild.
>>
>>
>> The attached p
: BSD-3-clause and CC-BY-4.0
Programming Lang: Coq
Description : high-order concurrent separation logic framework for Coq
This package provides a high-order concurrent separation
logic framework for Coq, which means it is useful to reason
about safety of concurrent programs.
.
Coq is a
parsnp 1.7.4 does no longer need this because it comes with
https://github.com/marbl/parsnp/pull/117
Control: tag -1 moreinfo
On Tue, 20 Feb 2018 04:30:54 +0100 Thilo Molitor wrote:
> Package: src:linux
> Version: 4.9.65-3+deb9u2
Can you still reproduce this with a recent kernel like 5.10 from current
Debian Stable?
signature.asc
Description: This is a digitally signed message part.
FILE
> >
> > /* strlen(newdir->d_name) could be replaced by newdir->d_reclen */
> >
> > - while ((newdir = readdir (dir)) != NULL) {
> > - if (*newdir->d_name == '.' &&
> > - strlen (newdir->d_na
rlen (newdir->d_name) < (size_t) 3)
> + while (n--) {
I guess this might have been borrowed from the example in the scandir(3)
manual page, because it goes in reverse order; I don't think there's a
good reason to do that.
> + free(namelist);
This leaks memory. We ne
Hi Colin,
Quoting Johannes Schauer Marin Rodrigues (2022-05-15 00:20:57)
> I now have a patch (attached).
do you have an approximate ETA for when you think you'll be able to upload a
version of man-db that fixes this issue? I'm trying to decide whether I should
make a new mmdebstrap release that
ppear to affect the sort order on
> tests.reproducible-builds.org, but it does appear to cause issues when
> testing with reprotest, and so may occur in other situations in the
> wild.
>
>
> The attached patch fixes this by passing it as a make variable rather
> than a quoted
ttached the contents of /var/cache/man/index.db so that you can see
> that it is indeed the order that differs between individual runs.
I now have a patch (attached).
Thanks!
cheers, josch--- a/src/check_mandirs.c
+++ b/src/check_mandirs.c
@@ -342,8 +342,8 @@ static void add_dir_entries (MYDBM_
. Quoting from resolv.conf(5)
...
However, drill seems to use all entries in a random(?) order. Or at least in
an order
which changes from one run to another, causing failures which come and go
depending on
whether the nameserver works on the primary link or not.
Hi Bjørn!
Drill is a dns
Control: tag 1006783 confirmed
Florian Ernst wrote...
(...)
> Please consider whether it's worthwhile to include libdumbnet support
> into tcpreplay, thanks.
Hello, and sorry for taking so long to respond.
Still, you suggestion seems sensible to include, I'll re-visit when it
comes to another u
A few utilities are still sensitive to block device order and this
causes issues for those. Nothing on the hardware explains this. The
controller thinks the device has a lower number, the device should
respond much faster.
The lowest level is the cciss driver.
--
(\___(\___(\__ -
https://qa.debian.org/excuses.php?package=dpkg
https://ci.debian.net/data/autopkgtest/testing/amd64/a/apt/20465752/log.gz
(68/287) Testcase test-apt-tagfile-fields-order: -Class
-Conffiles
-Config-Version
-MSDOS-Filename
-Optional
-Original-Maintainer
-Package-Revision
-Package_Revision
-Recomm
Control: retitle -1 mirrors must support also HTTPS in order to be considered
official
> This is related to: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992692
Quoting https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992692#37
This change is more about recognizing HTTPS as
Package: general
Severity: wishlist
Since the beginning of F-Droid, we have required that official package repos and
mirrors use HTTPS. We have encouraged all of them to have HTTPS. I think
Debian should do the same. There are already very many Debian mirrors that do
support HTTPS, here's
Control: tag -1 pending
On Sat, 05 Mar 2022 at 17:17:07 +0100, Guilhem Moulin wrote:
> For do_start() we're reading crypttab(5) sequentially as we don't have
> enough information about nesting, however for do_stop() we have that
> information in the mapping table, so no need to reverse crypttab(5)
Control: retitle -1 `/etc/init.d/cryptdisks stop` should safely traverse nested
block device stacks
Control: tag -1 - moreinfo
On Sat, 05 Mar 2022 at 16:54:07 +0100, Guenther Brunthaler wrote:
> which is exactly the same as do_start() does. And hence the entries are
> processed in the same
Am Sat, 5 Mar 2022 13:32:24 +0100
schrieb Guilhem Moulin :
> I believe cryptdisks_start(8) and cryptdisks_stop(8) processes
> mappings in the order given on the command line, which is
> intentional. Are you talking about SysV init scripts?
Yes, you are right. The problem actually
Control: tag -1 moreinfo
On Sat, 05 Mar 2022 at 13:13:57 +0100, Guenther Brunthaler wrote:
> When creating nested dmcrypt mappings in /etc/crtypttab,
> cryptdisks_start processes them from top to bottom.
I believe cryptdisks_start(8) and cryptdisks_stop(8) processes mappings
in the order
this works fine for unlocking the encrypted disks, cryptdisk_stop
tries to remove the dmcrypt mappings in the same order which is clearly
wrong: It tries to remove the base mapping before any mappings bases on
it, which will fail because the base mapping is "busy" at that point.
1 - 100 of 2517 matches
Mail list logo
