David Steele writes:
> On Wed, Dec 9, 2020 at 3:21 AM Ansgar wrote:
>> Given topydo just provides/conflicts with devtodo to provide the "todo"
>> binary, this seems to violate Policy 10.1 "Binaries" unless they provide
>> the same functionality.
[...]
> From where I stand, I would expect the
Package: debian-policy
9.1.2 recommends the following to create a directory under /usr/local:
```
if [ ! -e /usr/local/share/emacs ]; then
if mkdir /usr/local/share/emacs 2>/dev/null; then
if test -e /etc/staff-group-for-usr-local ; then
if chown root:staff
Ben Hutchings writes:
> The code signing service logs every file it signs, along with a hash of
> the detached signature, but I don't know where the logs are so I can't
> comapre with that.
I checked the audit log, but I don't think it will help much. It
currently records that:
- 2019-10-21
Package: debian-policy
Version: 4.4.1.1
Severity: minor
While checking the upgrade checklist I noticed this new requirement:
+---
| 4.9
|Required targets must not write outside of the unpacked source
|package tree, except for TMPDIR, /tmp and /var/tmp.
+---
The wording is a bit too
Package: texlive-fonts-extra
Version: 2019.20190930-2
Severity: serious
Hi,
when upgrading in Debian testing I saw the following error message:
+---
| Unpacking texlive-fonts-extra (2019.20190930-2) over (2019.20190830-1) ...
| dpkg: error processing archive
Package: clamav-daemon
Version: 0.101.4+dfsg-1
Severity: normal
After a user asked something about clamav on IRC, I noticed that
clamav-daemon's postinst creates a file
/etc/systemd/system/clamav-daemon.service.d/extend.conf with static
content:
+---
| echo "#Automatically Generated by
Package: src:runit
Version: 2.1.2-34
Severity: serious
I noticed that the last runit build is already taking over 13h on
buildds. The hppa build log[1] looks like the build failed due to an
endless loop.
I asked the other builds to be killed.
Ansgar
[1]
Package: bugs.debian.org
Severity: minor
Tags: upstream
It looks like debbugs always appends the bug report's msgid to the
`References` field when sending a follow-up message to the bug. This
should not be done when the msgid is already listed there.
(I noticed because this broke DKIM
Control: reassign -1 debian-policy
The section on initscripts has too much implementation details about
/etc/rcn.d; these are better explained by external documentation.
Also the rationale for why `DISABLED=yes` (or similar) fits better
into a footnote than the main text (IMHO).
(Policy also
Package: bugs.debian.org
Severity: normal
Tags: patch
The section on initscripts has too much implementation details about
/etc/rcn.d; these are better explained by external documentation.
Also the rationale for why `DISABLED=yes` (or similar) fits better
into a footnote than the main text
Package: gnome-terminal
Version: 3.34.0-1
Severity: minor
Tags: upstream
Changing the font size in one tab has an effect of other tabs: when
switching from tab A (with larger font size) to tab B (regular font
size), I can see that tab B gets restored with the larger font size
and is only then
Package: gnome-terminal
Version: 3.34.0-1
Severity: normal
Tags: upstream
I have a laptop with an external screen; internal and external screen
have different resolutions and DPI.
Since a recent update gnome-terminal and other GNOME applications use
the DPI from the wrong screen when the window
Package: dkimpy-milter
Version: 1.0.1-1
Severity: wishlist
Tags: upstream
Hi,
a recent mail to -devel@ resulted in the following header from dkimpy-milter:
Authentication-Results: [...]; dkim=fail (Bad 1024 bit rsa-sha256
signature.) header.d=[...] header.a=rsa-sha256
However the domain
Control: tag -1 moreinfo
Control: retitle -1 ftp.debian.org: `dak process-policy new` loses .buildinfo
files
The title says "loses .buildinfo files", but the IRC log says:
> tar tf /srv/ftp-master.debian.org/queue/done/2019/02.tar.xz | grep
> liblogger-simple-perl
>
Package: tor
Version: 0.3.5.8-1
Severity: normal
Tags: upstream
Hi,
I found the following warning in my log files:
+---
| Tor[2185]: Bug: Line unexpectedly reached at channel_tls_handle_cell at
../src/core/or/channeltls.c:. Stack trace: (on Tor 0.3.5.8 )
| Tor[2185]: Bug:
Package: gnupg
Version: 2.2.12-1
Severity: normal
Tags: upstream
>From man:gpg(1):
+---
| This format is deduced from the length of the string and its content
| or the 0x prefix. Note, that only the 20 byte version fingerprint
| is available with gpgsm (i.e. the SHA-1 hash of the certificate).
On Thu, 11 Jul 2019 13:26:34 +0200 Laurent Bigonville wrote:
> My understanding of the policy is that, if a package supports an
> alternative init (other than systemd) it must also support sysvinit.
>
> Also note that if the check is actually correct, this will create false
> positive for all the
Package: release-notes
Severity: normal
For bullseye, the security suite is now named bullseye-security
instead of buster/updates and users should adapt their sources.list
accordingly when upgrading.
People should probably use something like
deb http://security.debian.org/debian-security
Package: popularity-contest
Version: 1.67
Severity: wishlist
Hi,
it would be nice if popularity-contest would report which foreign
architecture are enabled, i.e. the list `dpkg
--print-foreign-architectures` should report.
In particular I'm interested in seeing how many people have enabled
i386
Package: ftp.debian.org
Removing packages from experimental when a newer version is available in
unstable should only happen after the package has been in unstable for a
few days.
This works around https://bugs.debian.org/865304 (too early removal of
overrides). It also keep binaries available
Philipp Kern writes:
> 20/06/2019 20:22, Ansgar Burchardt wrote:
>> You look up which uid the _apt user inside the chroot has and use that.
>
> Yeah, but that scales poorly if you have a centralized firewall
> policy. It means that you need to maintain dynamic rules. I know it's
Trek writes:
> Ansgar Burchardt wrote:
>> For limiting network access, I would recommend instead using network
>> namespaces (to only provide limited network access for all processes)
>> and/or user namespaces (if filtering for single UIDs is really
>> needed). Th
Package: apt,dselect
Severity: normal
Hi,
[ X-Debbugs-Cc'ed -boot@ for debootstrap ]
today I learned that debootstrap as special code to create the file
/var/lib/dpkg/cmethopt (contents: "apt apt"); this is the function
setup_dselect_method in functions. It seems wrong that debootstrap
has
Michael Biebl writes:
> On Wed, 19 Jun 2019 22:16:58 +0200 Ansgar Burchardt wrote:
>> I'm just a GNOME user, but from gdm3's changelog the default was
>> switched to Wayland in July 2017 (or August 2017 for unstable). I
>> myself only noticed the switch after reading
Ansgar Burchardt writes:
> (I don't maintain debootstrap.)
>
> I don't think it is a good idea to require debootstrap to know about
> such details.
>
> For limiting network access, I would recommend instead using network
> namespaces (to only provide limited network acc
Michael Schaller writes:
> At the end of the 'apt' package installation the '_apt' user will be
> created without specifying a fixed uid. This typically results in a
> differing '_apt' uid between the host system and the bootstrapped
> system. The differing '_apt' uid is problematic in case the
Jonathan Dowland writes:
> So far as I am aware there is still radio silence from active GNOME
> packaging team members regarding this issue. No comment yet on the
> patch I adapted, positive or negative; this bug (#927667) remains
> at an RC severity.
>
> I've not yet read all the thread that
Mattia Rizzolo writes:
> On Tue, Jun 18, 2019 at 06:29:12PM +0200, Ansgar Burchardt wrote:
>> The .buildinfo files are referred to in the .changes files; renaming
>> them would require updating the .changes file. The .changes files are
>> used to upload the security
On Mon, 2019-06-17 at 13:12 -0700, Vagrant Cascadian wrote:
> > This behaviour is really causing issues for the security-archive so in
> > one way or the other there needs to be a solution. Regularly we need
> > to fetch the buildd changes and build binary packages, resign them and
> > reupload
Package: libopenblas-base
Version: 0.3.5+ds-3
Severity: important
File: /usr/lib/x86_64-linux-gnu/libopenblas.so.0
Tags: upstream
OpenBLAS tries to use AVX-2 / AVX-512 even when it is not actually
available, causing programs to crash with SIGILL:
+---
| Thread 1 "cholmodtest" received signal
Package: src:coinor-ipopt
Version: 3.11.9-2.1
Severity: wishlist
The Debian version of IPopt lags quite a bit behind upstream: Debian
still ships 3.11.9 (released 2014-08-16); the current upstream release
is 3.12.13 (released 2019-04-08), but there were several releases in
between that were not
Package: src:coinor-ipopt
Version: 3.11.9-2.1
Severity: normal
I had some problems with IPopt using the sequential version of MUMPS
recently: as MUMPS provides dummy `MPI_*` functions, my program ended
up using some of them or MUMPS used some of the real MPI functions.
As mentioned in IPopt's
:41:56.0 +0200
@@ -1,3 +1,10 @@
+gmsh (4.1.3+ds1-2) buster; urgency=medium
+
+ * Team upload.
+ * debian/rules: Do not pass `-DOCC_INC=...` to cmake (Closes: #927808)
+
+ -- Ansgar Burchardt Fri, 17 May 2019 10:41:56 +0200
+
gmsh (4.1.3+ds1-1) unstable; urgency=medium
* [dbbbe82] New upstr
Paul Wise writes:
> On Thu, 11 Oct 2018 17:32:52 -0700 Sean Whitton wrote:
>> Instead, if there is indeed consensus, we should change it so that it
>> no longer says that doc-base registration is recommended.
>
> We need a cross-distro cross-desktop standard for an index of
> docs before we can
On Sun, 2019-05-05 at 16:05 +0200, Santiago Vila wrote:
> [ Ansgar: If you still can reproduce the assertion failure, please
> file
> a new bug. It's better not to mix different issues in the same report ].
The other assertion failure I had also disappeared this week. Not sure
if there is a
Control: reassign -1 src:dune-pdelab 2.6~20180302-1
Control: retitle -1 dune-pdelab: testpk fails with assertion failure
On Mon, 2019-04-08 at 08:42 +0200, Ansgar Burchardt wrote:
> This is a bug in dune-istl, though I'm not quite sure I understand
> what
> is exactly wrong.
Niels Thykier writes:
> We need new archive signing keys for buster, so we can include them in
> a debian-archive-keyring upload before the buster release.
The two keys are prepared; I'm waiting for a few more signatures from
other ftp masters.
FWIW they will be:
pub rsa4096 2019-04-14 [SC]
On Thu, 2019-04-11 at 11:49 +0200, Guido Günther wrote:
> E.g. for amd64 and stretch we'd have a file
>
>http://ftp.debian.org/debian/dists/stretch/main/installer-amd64/.treeinfo
>
> looking like
>
> [checksums]
> current/images/netboot/mini.iso = sha256:...
>
Control: reassign -1 src:dune-istl 2.6.0-2
Control: affects -1 src:dune-pdelab
Santiago Vila writes:
> /usr/include/dune/istl/paamg/transfer.hh:97:5: error: no declaration matches
> 'void Dune::Amg::Transfer Dune::Amg::SequentialInformation>::prolongateVector(const
> Dune::Amg::AggregatesMap&,
Package: matrix-synapse
Version: 0.99.2-1
Severity: normal
matrix-synapse installs several programs with fairly generic names to
/usr/bin, for example:
generate_config
hash_password
move_remote_media_to_new_store.py
I suggest that these are either moved to /usr/lib/matrix-synapse or
Steve McIntyre writes:
> Please unblock package fwupd
Please also unblock
fwupd-amd64-signed/1.2.5+2
fwupd-arm64-signed/1.2.5+2
fwupd-armhf-signed/1.2.5+2
fwupd-i386-signed/1.2.5+2
at the same time.
Ansgar
Steve McIntyre writes:
> Please unblock package fwupdate
Please also unblock
fwupdate-amd64-signed/12+4
fwupdate-arm64-signed/12+4
fwupdate-armhf-signed/12+4
fwupdate-i386-signed/12+4
at the same time.
Ansgar
On Wed, 20 Mar 2019 15:59:40 + Dimitri John Ledkov
wrote:
> On Wed, 20 Mar 2019 16:31:25 +0100 Ansgar Burchardt wrote:
> > Hi,
> >
> > the OpenSSL ./. GPL problem (if one sees it as a problem) is larger
> > than just libpq5: just looking at a small
Hi,
On Wed, 2019-03-20 at 16:31 +0100, Ansgar Burchardt wrote:
> the OpenSSL ./. GPL problem (if one sees it as a problem) is larger
> than just libpq5: just looking at a small sample of the direct rdeps
> of
> libssl1.1, one can find the following GPL-licensed prog
Hi,
the OpenSSL ./. GPL problem (if one sees it as a problem) is larger
than just libpq5: just looking at a small sample of the direct rdeps of
libssl1.1, one can find the following GPL-licensed programs linking it:
cryptsetup, wesnoth, mydumper, mupdf, gatling, kopete
Also amanda-client,
Package: openssh-client
Version: 1:7.9p1-6
Severity: normal
The file "This is a [file].txt" (w/o quotes) exists on `remote`.
The following does no longer work:
$ scp remote:'./"This is a [file].txt"' blubb
protocol error: filename does not match request
These however do still work:
$
Package: debian-policy
Version: 4.3.0.2
Severity: normal
Policy 10.5 (Symbolic links) currently has two classes of requirements:
Symlinks between /${x} and /${x} (same top-level directory) must use
relative links; symlinks between /${x} and /${y} (different top-level
directories).
The historic
Package: ftp.debian.org
Severity: normal
secure-boot-code-sign.py leaks database sessions. This leads to
failure when processing several packages.
I've attached the traceback.
Ansgar
ERROR:root:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sqlalchemy/pool.py", line
Package: src:mandos
Version: 1.8.3-2
Severity: serious
d/rules modifes d/control during build:
```
override_dh_shlibdeps-arch:
[...]
dpkg --compare-versions $$gnutls_version lt 3.6.0 \
&& sed --in-place --expression='s/libgnutls28-dev (>= 3\.6\.6)
| //' debian/control
Package: lists.debian.org
Severity: minor
Hi,
debian-private uses the following List-Archive field:
List-Archive:
It should be
file://master.debian.org/home/debian/archive/debian-private/
instead.
See also RFC 8089 and in particular the following parts:
+---
|Non-local files:
|
|
Steve McIntyre writes:
> On Fri, Jan 04, 2019 at 08:37:24PM +0200, Graham Inggs wrote:
>>This sounds like #918157.
>
> Nod. I'm seeing similar behaviour in a few more packages since tihs
> point, too. :-(
As mentioned on IRC: if you want to make sure that it is a problem with
OpenMPI, you can
Sean Whitton writes:
> On Wed 02 Jan 2019 at 12:29pm +0900, Ansgar Burchardt wrote:
>> I hereby propose to drop section 1.6 Translations and the following
>> sentence: "When translations of this document into languages other
>> than English disagree with the English te
Package: debian-policy
Version: 4.3.0.1
Severity: normal
Hi,
I hereby propose to drop section 1.6 Translations and the following
sentence: "When translations of this document into languages other
than English disagree with the English text, the English text takes
precedence."
If it is wrongly
Adam Borowski writes:
> Thus, the wording would be (as proposed by fsateler):
>
> logind: an org.freedesktop.login1 D-Bus API implementation
>
> default-logind: should be provided by the distribution's default logind
> provider (currently pam-systemd)
So any provider of logind would have to
Hi,
Ansgar Burchardt writes:
> emacs26 added support for systemd socket activation (which I'm looking
> forward to use).
I was asked on IRC to test this with the Debian package (1:26.1+1-2).
It works:
After starting the emacs.socket unit, systemd opens the socket:
+---
| [...] /ru
Package: src:julia
Version: 1.0.2-1
Severity: normal
Hi,
libjuliaX installs files to usr/lib/.../julia and thus has to
Replaces/Breaks every other version libjuliaY. However the point of
package renaming on soname change is that libjuliaX and libjuliaY can
be coinstalled (otherwise a Provides:
Package: src:julia
Version: 0.7.0-2
Severity: serious
Hi,
the source for contrib/windows/7zS.sfx seems to be missing. As the
file is probably not needed for Debian, it could just be removed from
Debian's source tarball.
Ansgar
Control: reassign -1 src:linux 4.19.9-1
On Thu, 20 Dec 2018 16:26:55 +0100 Vincent Lefevre wrote:
> After an upgrade of linux-image-amd64, which now depends on
> linux-image-4.19.0-1-amd64, on one machine I got:
>
> linux-image-4.19.0-1-amd64 4.19.9-1
>
> but on another machine I got:
>
>
Control: reopen -1
Dmitry Bogatov writes:
> control: tags -1 wontfix
>
> [2014-09-16 18:00] Ansgar Burchardt
>> The symlinks in /etc/rc?.d/* and /etc/default/* are configuration files,
>> but init script themselves are not (and if admins are supposed to modify
>> th
Hi,
I got around to rebuild emacs with libsystemd-dev installed. That is
enough for socket activation to work (with custom emacs.socket file):
+---
| run/user/[...]/emacs [...]
users:(("emacs",pid=26360,fd=3),("systemd",pid=2487,fd=23)) <->
+---( from ss output )
Ansgar
Package: emacs
Version: 1:26.1+1-1
Severity: normal
Hi,
emacs26 added support for systemd socket activation (which I'm looking
forward to use). However looking at the buildd log it seems this
isn't enabled:
+---
| Does Emacs use -lsystemd? no
+---[
Hi,
Hideki Yamane writes:
> On Sun, 2 Dec 2018 15:15:21 +
> Simon McVittie wrote:
>> > - What is the problem? (broken build for which packages? Just R?)
>>
>> The problem we're aware of is:
>>
>> Some packages auto-detect the absolute path to an executable (for example
>> bash or perl)
Adam Borowski writes:
> On Tue, Dec 04, 2018 at 06:48:45PM +0100, Ansgar Burchardt wrote:
>> In very rare cases (an estimated 0.3% of the archive or so). I'm fairly
>> confident that for more than 0.3% of the archive something can go wrong
>> when building in non-clean e
Ian Jackson writes:
> Ansgar Burchardt writes ("Bug#914897: debating the wrong thing"):
>> Switching to (1) or (3a-with-no-support-in-buster) will mean merged-/usr
>> systems would no longer be supported. In this case someone would have
>> to write a unusrm
Source: ucspi-tcp
Version: 1:0.88-4
Severity: normal
Vcs-* ist set to https://salsa.debian.org/debian/ucspi-tcp which is a
private repository. Please make the repository publically accessible.
Ansgar
Source: ucspi-tcp
Version: 1:0.88-4
Severity: grave
>From /usr/bin/date@:
+---
| /build/ucspi-tcp-J4veAW/ucspi-tcp-0.88/debian/ucspi-tcp/usr/bin/tcpclient
-RHl0 -- "${1-0}" 13 sh -c 'exec
/build/ucspi-tcp-J4veAW/ucspi-tcp-0.88/debian/ucspi-tcp/usr/bin/delcr <&6' |
cat -v
+---
Similar for
"Alexander E. Patrakov" writes:
> Ansgar Burchardt wrote:
>> Making the feature default was discussed years ago which you are surely
>> aware of. It's not mandatory.
>
> Unfortunately I have to disagree here. Merged /usr is already,
> de-facto, mandatory for ev
Adam Borowski writes:
> On Mon, Dec 03, 2018 at 10:25:46PM +0100, Ansgar Burchardt wrote:
> I believe the difference between those is less than between suboptions of 1
> and 3, but then, as an opponent of 2 as a whole I'm biased.
>
>> Switching to (1) or (3a-with-no-support-in
Gunnar Wolf writes:
> Adam Borowski dijo [Mon, Dec 03, 2018 at 12:36:29AM +0100]:
>> (...)
>> So, let's enumerate possible outcomes:
>>
>> 1. no usrmerge
>> 1a. no moves at all (no effort needed!)
>> 1b. moves via some dh_usrmove tool, until /bin is empty
>> 2. supporting both merged-usr and
+0100
@@ -1,3 +1,10 @@
+xfce4-session (4.13.1-1.1) UNRELEASED; urgency=medium
+
+ * Explicit pass `RM=/bin/rm` to configure to make build reproducible
+between merged-usr and non-merged-usr systems.
+
+ -- Ansgar Burchardt Mon, 03 Dec 2018 19:46:56 +0100
+
xfce4-session (4.13.1-1) experimental
Package: libmdds-dev
Version: 1.4.3-1
Severity: minor
User: m...@linux.it
Usertags: usrmerge
Hi,
while investigating package builds producing different results on
merged-/usr vs. non-merged-/usr systems, I noticed that libmdds-dev
ships a `Makefile` in /usr/share/doc/libmdds-dev/examples which
On Mon, 2018-12-03 at 16:35 +0100, Adam Borowski wrote:
> Use cases, for individual packages: (copied from a mail by smcv):
>
> """
> Packages that need to register their login sessions with logind
> (gdm3, lightdm, openssh-server):
> - remove libpam-systemd dependency
> - add
On Mon, 2018-12-03 at 12:38 +, Ian Jackson wrote:
> Ansgar Burchardt writes ("Bug#914897: debating the wrong thing"):
> > It is very demotivating to have discussed and implemented something
> > mostly years ago, for people then to come and complain "let's not
Package: anacron
Version: 2.3-26
Severity: normal
anacron.service currently uses KillMode=mixed. It probably should
not.
KillMode=mixed sends SIGTERM to anacron and then SIGKILL to any
processes started by anacron. The default (KillMode=control-group)
would send SIGTERM to all processes which
Hi,
please explain what components you are talking about and why they
shouldn't be allowed in Debian.
Ansgar
Adam Borowski writes:
> I see that we're debating the merits of merged-usr vs non-merged-usr, while
> expending lots of effort and filing bugs (requiring further urgent action of
> unrelated maintainers), for little gain.
There is no "urgent action" required (unlike, say, for the last glibc
Marc Haber writes:
> The next debhelper change might choose to give / instead of /usr as a
> target directory by default, moving hundreds of megabytes from /usr to /
> over time. My question was about the distant future, and not the current
> snapshot of things.
If anything then /usr would be the
Marc Haber writes:
> On Sat, Dec 01, 2018 at 11:36:45PM +0100, Didier 'OdyX' Raboud wrote:
>> Le samedi, 1 décembre 2018, 19.29:59 h CET Marc Haber a écrit :
>> > Will binaries move from /usr/bin to /bin? Or will binaries move from
>> > /bin to /usr/bin?
>>
>> A merged-/usr has a /bin → /usr/bin
Marc Haber writes:
> On Sat, Dec 01, 2018 at 07:20:57PM +0100, Didier 'OdyX' Raboud wrote:
>> * Currently, according to my `apt-file`, 259 binaries are shipped in /bin
>> directly, accross 85 packages. (for /sbin, 597 binaries for 190 packages).
>
> This might sound like a stupid question, what
Ansgar Burchardt writes:
> There were discussions about enabling this by default years ago, I
> don't think minor issues should be a reason to delay this change.
>
> Note that it has been delayed for after the stretch release as there
> were major issues back then (it was ena
.1) UNRELEASED; urgency=medium
+
+ * Explicit pass MKDIR_P, GREP and SED to configure to make build
+reproducible between merged-usr and non-merged-usr systems.
+
+ -- Ansgar Burchardt Sat, 01 Dec 2018 15:00:28 +0100
+
bsdowl (2.2.2-1) unstable; urgency=medium
* Initial release. (Closes: #760592)
to make build reproducible
+between merged-usr and non-merged-usr systems.
+
+ -- Ansgar Burchardt Sat, 01 Dec 2018 14:20:56 +0100
+
maildrop (2.9.3-2) unstable; urgency=medium
* Migrate VCS from alioth to salsa.
diff -Nru maildrop-2.9.3/debian/rules maildrop-2.9.3/debian/rules
--- maildrop
+reproducible between merged-usr and non-merged-usr systems.
+
+ -- Ansgar Burchardt Sat, 01 Dec 2018 13:41:09 +0100
+
nvi (1.81.6-13) unstable; urgency=medium
* QA upload.
diff -Nru nvi-1.81.6/debian/rules nvi-1.81.6/debian/rules
--- nvi-1.81.6/debian/rules 2016-12-31 05:03:39.0
) UNRELEASED; urgency=medium
+
+ * Explicit pass path to {u,}mount to configure to make build
+reproducible between merged-usr and non-merged-usr systems.
+
+ -- Ansgar Burchardt Sat, 01 Dec 2018 13:40:31 +0100
+
disk-manager (1.1.1-2) unstable; urgency=low
* Add Build-Depends-Indep on menu
-7.2.6/debian/changelog
@@ -1,3 +1,10 @@
+apsfilter (7.2.6-1.4) UNRELEASED; urgency=medium
+
+ * Explicit pass `--with-shell=/bin/bash` to configure to make build
+reproducible between merged-usr and non-merged-usr systems.
+
+ -- Ansgar Burchardt Sat, 01 Dec 2018 13:20:25 +0100
+
apsfilter
to configure to make build reproducible
+between merged-usr and non-merged-usr systems.
+
+ -- Ansgar Burchardt Sat, 01 Dec 2018 13:07:16 +0100
+
libsmi (0.4.8+dfsg2-15) unstable; urgency=medium
* Add /var/lib/snmp/mibs/site to the default search path for MIB files.
diff -Nru libsmi-0.4.8
On Fri, 2018-11-30 at 19:40 +0100, Didier 'OdyX' Raboud wrote:
> Dear Hideki, dear src:debootstrap maintainers,
>
> tl;dr: debootstrap maintainers; can you agree to disable "merged /usr" by
> default now, or are you OK letting the TC decide on this subject?
There were discussions about enabling
Simon McVittie writes:
> On Thu, 29 Nov 2018 at 18:34:42 +0100, Ansgar Burchardt wrote:
>> Regardless of debootstrap defaults or flag days, we could also consider
>> moving programs from /{s,}bin to /usr/{s,}bin with a compat symlink in
>> /{s,}bin
>
> I'm not co
Package: ftp.debian.org
Severity: normal
Please remove systemd-shim from the archive. It is dead upstream,
unmaintained, uninstallable and broken.
AFAIU people who like systemd-logind's features, but don't want to run
systemd-init for some reason plan to use elogind instead which has now
Adam Borowski writes:
> Andreas Henriksson wrote:
>> On Wed, Nov 28, 2018 at 03:14:20PM +, Ian Jackson wrote:
>> > Julien Cristau writes ("Re: Bug#914897: debootstrap, buster:
>> > Please disabled merged /usr by default"):
>> [...]
>> > > I'd suggest that this should be fixed by not shipping
2017-12-09 00:07:05.0 +0100
+++ bumblebee-3.2.1/debian/changelog2018-11-29 10:19:19.0 +0100
@@ -1,3 +1,9 @@
+bumblebee (3.2.1-18) UNRELEASED; urgency=medium
+
+ * Remove obsolete conffile /etc/init/bumblebeed.conf
+
+ -- Ansgar Burchardt Thu, 29 Nov 2018 10:19:19 +0100
Source: kmc
Version: 2.3+dfsg-6
Severity: normal
kmc installs programs to /bin. For a bioinformatics tool this seems
not correct; the programs should be installed to /usr/bin instead.
Ansgar
Package: ttygif
Version: 1.4.0-1
Severity: normal
The ttygif program is installed as /bin/ttygif. From the description
it should be installed as /usr/bin/ttygif instead.
Ansgar
PS: The Build-Depends: gcc-8 also looks incorrect as only `gcc` is
called by the Makefile.
Package: gaffitter
Version: 0.6.0-2
Severity: normal
The package install gaffitter to /bin, but it should be installed to
/usr/bin. From looking at the Makefile, passing prefix=/usr when
calling `make install` might be enough for this.
Ansgar
Package: systemd
Version: 239-11
Severity: minor
File: /bin/systemd
Running `systemd` in an interactive shell is not a good idea. To
avoid this happening by accident, the /bin/systemd ->
/lib/systemd/systemd symlink should no longer be shipped.
Documentation such as [1] still suggests to use
Hi,
Steve McIntyre writes:
> On Mon, Sep 03, 2018 at 09:45:39AM +0200, intrigeri wrote:
>>Hi,
>>
>>Sven Joachim:
>>> The package priorities on security.debian.org differ from the ones in
>>> the main archive
>>
>>Here's another brand new example:
>>
>>$ apt-cache show mutt | grep -E
Package: slrnpull
Version: 1.0.3+dfsg-2
I can confirm that slrnpull's cronjob still fails with "This account is
currently not available." in Debian testing (buster).
I'm also using RUNFROM='manually', but I'm not sure that is relevant
(the check for RUNFROM only occurs later in the cronjob).
Steve Langasek writes:
> On Wed, Oct 17, 2018 at 10:07:44AM +0200, Ansgar Burchardt wrote:
>> That exception does not exist in Policy; there is only an exception for
>> packages provided by the init implementation itself. Policy currently
>> requires the "Loose coupli
Russ Allbery writes:
> Ansgar Burchardt writes:
>> So shipping a daemon without init scripts is better than shipping one
>> with only a systemd unit?
>
> I don't believe such a daemon package (with no init script) should be
> included in Debian at *all*, as a matter of
Russ Allbery writes:
> Ansgar Burchardt writes:
>
>> a. tor@.service has no init script with the same name. This should be
>>fine. (Note: there is also both a "tor.service" and "tor" init
>>script.)
>
> Presumably this is fine for the sa
1 - 100 of 2294 matches
Mail list logo
