The new implementation of rwho, see #1013361, does come with a systemd
unit,
it's waiting in the new queue.
The new rwho from ruptime, https://bugs.debian.org/1013361
has no such limit.
It is waiting in the new queue to get processed.
With the new ruptime, see https://bugs.debian.org/1013361
you can easily configure this option.
Package: apt-xapian-index
Version: 0.53
Severity: normal
apt-xapian-index uses python3-six in a single place
but forget to declare a depedency on it
apt-xapian-index would better be ported
to properly use the "io" module dirrectly
(one line change)
$ grep ' six' /bin -r 2>/dev/null | grep
Version: 0.28.debian-7+rm
Dear submitter,
as the package human-icon-theme has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
human-icon-theme | 0.28.debian-7 | source, all
--- Reason ---
RoQA; Obsolete, unmaintained, alternatives exist
Version: 0.26.debian-6+rm
Dear submitter,
as the package tangerine-icon-theme has just been removed from the Debian
archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
tangerine-icon-theme | 0.26.debian-6 | source, all
--- Reason ---
RoQA; Obsolete, unmaintained, alternatives exist
Your message dated Mon, 26 Jun 2023 00:03:34 +
with message-id
and subject line Bug#1039065: Removed package(s) from unstable
has caused the Debian Bug report #520780,
regarding please remove dependency on tangerine-icon-theme
to be marked as done.
This means that you claim that the problem
Package: wvstreams
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
wvstreams has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: watchcatd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
watchcatd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: vzctl
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
vzctl has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because
Package: tircd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
tircd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because
Package: tetrinetx
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
tetrinetx has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: tenshi
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
tenshi has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: tcpspy
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
tcpspy has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: sysrqd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
sysrqd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: snmptrapfmt
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
snmptrapfmt has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this
Package: sleepd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
sleepd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: sendmail
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
sendmail has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: rinetd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
rinetd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: qpsmtpd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
qpsmtpd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: proxsmtp
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
proxsmtp has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: powerman
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
powerman has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: partimage
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
partimage has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: pads
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
pads has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because a
Package: olpc-powerd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
olpc-powerd has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this
Package: omnievents
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
omnievents has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this
Package: olpc-kbdshim
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
olpc-kbdshim has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this
Package: netkit-rwho
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
netkit-rwho has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this
Package: mpt-status
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
mpt-status has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this
Package: mini-httpd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
mini-httpd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this
Package: masqmail
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
masqmail has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: mason
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
mason has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because
Package: lprng
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
lprng has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because
Package: latd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
latd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because a
Package: isakmpd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
isakmpd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: iptotal
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
iptotal has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: httpry
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
httpry has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: gsm0710muxd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
gsm0710muxd has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this
Package: freewnn
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
freewnn has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: freelan
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
freelan has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: esekeyd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
esekeyd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: elida
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
elida has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because
Package: dnprogs
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
dnprogs has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: dmucs
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
dmucs has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because
Package: dhis-server
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
dhis-server has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this
Package: dhis-client
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
dhis-client has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this
Package: cpufreqd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
cpufreqd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: couriergraph
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
couriergraph has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this
Package: c-icap
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
c-icap has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: canna
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
canna has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because
Package: bwbar
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
bwbar has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because
Package: bluemon
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
bluemon has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: bandwidthd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
bandwidthd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this
Package: avr-evtd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
avr-evtd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked
Package: apf-firewall
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
apf-firewall has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this
Package: amavisd-milter
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
amavisd-milter has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 25 Jun 2023 14:06:39 -0700
Source: binutils-msp430
Architecture: source
Version: 2.24~ti3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By:
binutils-msp430_2.24~ti3_source.changes uploaded successfully to localhost
along with the files:
binutils-msp430_2.24~ti3.dsc
binutils-msp430_2.24~ti3.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Source: collada2gltf
Severity: serious
Justification: devref
Dear Maintainer,
Your package embed a copy a yajl
Could you:
- build against yajl package
- remove by repacking the code copy in order to avoid in the future accidental
code compilation against the embed code copy
Thanks
Bastien
Source: antigrav
Version: 0.0.3-10
Severity: important
Tags: ftbfs trixie sid
I tried recompiling antigrav with libsdl1.2-compat-dev instead of
libsdl1.2-dev, in preparation for having src:sdl12-compat take over the
libsdl1.2-dev package name.
I found that antigrav failed to build from source
On Thu, 15 Jun 2023 at 12:29:14 +0100, Simon McVittie wrote:
> 4. Install libsdl1.2-compat-dev and recompile the package.
I tried this on a porterbox and it seems to build fine, other than the
missing build-dependency on pkgconf that I reported as #1039074 (which
I intend to work around by making
On Thu, 15 Jun 2023 at 12:28:56 +0100, Simon McVittie wrote:
> 4. Install libsdl1.2-compat-dev and recompile the package.
I tried this on a porterbox and it seems to build fine. I didn't test
the resulting binaries.
smcv
On Thu, 15 Jun 2023 at 12:28:35 +0100, Simon McVittie wrote:
> 4. Install libsdl1.2-compat-dev and recompile the package.
I tried this on a porterbox and it seems to build fine, other than
the missing build-dependency on libglu1-mesa-dev reported as #1039072
(which I'm going to work around by
Source: adplay
Version: 1.8.1-3
Severity: important
Tags: ftbfs trixie sid
I tried compiling adplay on a porterbox with libsdl1.2-compat-dev
instead of libsdl1.2-dev, in preparation for having a future version of
sdl12-compat take over the libsdl1.2-dev name.
I found that adplay FTBFS with:
>
Source: achilles
Version: 2-12
Severity: important
Tags: trixie sid ftbfs
achilles includes but does not have the corresponding
build-dependency on libglu1-mesa-dev.
At the moment it compiles successfully anyway, because libsdl1.2-dev
pulls in libglu1-mesa-dev; but it fails to build when
67 matches
Mail list logo
