The removal scripts in the new cfengine 3.15.2 packages also have issues.
While cleaning up after my testing for the initial bug report, I
encountered the following.
# apt-get purge cfengine3
Reading package lists... Done
Building dependency tree
Reading state information... Done
The
Package: cfengine3
Version: 3.15.2-2
Severity: grave
Justification: renders package unusable
First, thank you for packaging cfengine 3.15.2.
Unfortunately, the new cfengine 3.15.2 package in sid/unstable is
broken and non-functional.
What led up to the situation?
Upgrading from cfengine 3.12.1
A strong argument for updating the Debian packages to cfengine 3.15 LTS
is that upstream will stop supporting and patching the 3.12 LTS branch
sometime in early 2021.
Upstream will support the latest 3.15 LTS branch until the end of 2022
or early 2023.
I found the associated ath10k mailing list thread
https://www.mail-archive.com/ath10k@lists.infradead.org/msg12068.html
In that thread, Wen Gong (author of the changes in git commit
2dc016599cfa9672a147528ca26d70c3654a5423)
Package: src:linux
Version: 5.6.7-1
Severity: normal
After upgrading to linux-image-5.6.0-1-amd64 on my Linux-based
wireless access-point (AP), hostapd is no longer able to configure
the Atheros radios for the 5 GHz band.
On the old 5.5 kernel, `iw list` shows the following for the 5 GHz band.
Package: cfengine3
Version: 3.12.1-2
Severity: wishlist
The upstream version of cfengine community edition currently has two
long-term support (LTS) versions: 3.12.4 and the newer 3.15.1.
If Debian needs to stay on the 3.12 LTS branch,
upgrading from 3.12.1 to 3.12.4 would at least sync up with
Package: suricata
Version: 1:5.0.2-3
Severity: normal
Tags: patch
As part of the migration away from /var/run/ to /run/,
systemd produces log events containing the following.
"/lib/systemd/system/suricata.service:10: PIDFile= references a path below
legacy directory /var/run/, updating
Package: radvd
Version: 1:2.17-2+b1
Severity: normal
Tags: patch
As part of the migration away from /var/run/ to /run/, systemd produces
log events containing the following. These log events are generated
every 5 minutes (cluttering the logs and consuming log space).
Package: cfengine3
Version: 3.12.1-2
Severity: normal
Dear cfengine3 Maintainer,
The cfengine3 package should create the /var/lib/cfengine3/plugins
directory during installation.
Without this directory, the /var/log/cfengine3/promise_summary.log
log file records update.cf never completing
Upstream has released hledger 1.17
https://hledger.org/release-notes.html
Also, I saw that hledger 1.14 has been removed from Debian testing due to FTBS
issues on s390x
https://tracker.debian.org/news/1099686/haskell-hledger-removed-from-testing/
I'm not a Haskell programmer, but since hledger
Package: hledger
Version: 1.14.2-1+b1
Severity: wishlist
Upstream has released hledger 1.16.2, which includes a
number of improvements in versions 1.15.x and 1.16.x.
https://hledger.org/release-notes.html
One improvement relevant to building and packaging is
that hledger 1.16 added support for
Package: keepassxc
Version: 2.4.3+dfsg.1-1+b1
Followup-For: Bug #946450
Upstream has released 2.5.2, which includes fixes for multiple
crashes, memory leaks, and other bugs.
https://keepassxc.org/blog/2020-01-04-2.5.2-released/
The KeePassXC-Browser add-ons for Firefox and Chromium are also
Package: hugo
Version: 0.18.1-1+b2
Severity: wishlist
Dear Maintainer,
Debian unstable and testing currently package Hugo 0.18.1.
Hugo 0.19 through 0.20.6 have been released upstream since February.
https://github.com/spf13/hugo/releases
Given some of the bug fixes, new features, and
A friend and I both encountered this problem with our Yubikey 4 devices
after upgrading to gnupg and scdaemon 2.1.18-3.
Here is what I found, along with a partial solution.
The new scdaemon does NOT get along with pcscd anymore.
There is a race condition for which one opens the Yubikey device
My original bug report was against systemd 230.
I believe this issue was fixed as a result of various IPv6
changes somewhere in the development of 231 or 232.
> Try checking /proc/sys/net/ipv6/conf/$INTERFACE/accept_ra
> You'll notice "all" has the system-global setting you're seeing
> with
Package: systemd
Version: 230-2
Severity: normal
According on the systemd.network manual page:
IPv6AcceptRouterAdvertisements=
Force the setting of the accept_ra ...
Takes a boolean.
... note that systemd's setting of 1
corresponds to kernel's setting of 2.
This documented
Package: ntp
Version: 1:4.2.8p4+dfsg-3+b1
Followup-For: Bug #809344
Tags: patch
Since the original bug report didn't have the "patch" tag, I'm following
up to add the patch tag.
--- ntp.orig 2016-03-30 19:04:47.859783599 -0600
+++ ntp.fixed 2016-03-30 19:31:39.542680609 -0600
@@ -40,9 +40,9 @@
Package: ntp
Version: 1:4.2.8p4+dfsg-3+b1
Followup-For: Bug #809344
I recently noticed this same issue with the dhcp hook
not removing the new "pool" lines from copied ntp.conf.
This issue is still present in 1:4.2.8p4+dfsg-3+b1.
I can also confirm that the patch provided by Ron
in the initial
Source: gr-osmosdr
Followup-For: Bug #791062
gr-osmosdr is now uninstallable in unstable/sid.
Debian unstable recently switched to GCC-5 as the default compiler.
Debian unstable also recently upgraded from libboost1.55 (old ABI)
to libboost1.58 (new ABI), and from gnuradio 3.7.5 (old ABI)
to
Package: libpqxx-4.0
Severity: important
Debian unstable has migrated to GCC-5, which has a new, and incompatible, ABI.
https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
As a result, libpqxx is no longer installable on Debian unstable.
=
# aptitude install libpqxx-4.0
The following
Package: postfix-pgsql
Version: 2.11.1-1
Severity: important
Dear Maintainer,
Debian jessie just updated libpq5 from 9.3.4-2 to 9.4~beta2-1.
Unfortunately, postfix-pgsql fails when using libpq5 9.4~beta2-1
with error messages like the following from Postfix:
=
postfix/trivial-rewrite:
The issue being specific to the non-proxy case is a possibility.
James reported that his config using proxy:pgsql: is working fine.
My configuration is non-proxy with configuration lines like these:
smtpd_sender_login_maps =
pgsql:/etc/postfix/pgsql/smtpd_sender_login_maps.cf
I've verified that the issue is with non-proxy configurations.
I converted my configuration to use proxy:pgsql: variants,
and now everything works just fine with libpq5 9.4~beta2-1.
On 07/31/2014 07:26 PM, Michael Berg wrote:
The issue being specific to the non-proxy case is a possibility
Package: qca-tls
Version: 1.0-4
Severity: normal
qca-tls currently depends on libssl0.9.8.
However, libssl0.9.8 is no longer available in the unstable archive
(everything is migrating to libssl1.0.0).
Recompiling qca-tls to link against libssl1.0.0
will fix this dependency issue.
-- System
Package: sgml-data
Version: 2.0.5
Severity: normal
When installing/upgrading sgml-data:
Unpacking replacement sgml-data ...
Setting up sgml-data (2.0.5) ...
WARNING: You are using the compatibility symlink `update-catalog'.
WARNING: This command will disappear in the future (see
Package: mercurial
Version: 1.5.2-1
Severity: wishlist
Mercurial 1.5.4 is available and includes several improvement and fixes.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel:
Package: postgresql-contrib-8.4
Version: 8.4.2-2
Severity: important
postgresql-contrib-8.4 depends on libossp-uuid15,
but libossp-uuid16 was recently added to the archive
and libossp-uuid15 was removed.
postgresql-contrib-8.4 needs to be rebuilt against libossp-uuid16.
-- System Information:
Package: binutils-avr
Version: 2.20-1
Severity: normal
binutils-avr 2.20-2 tries to overwrite /usr/share/info/gprof.info.gz,
which is also in package binutils-doc 2.20-2.
So binutils-avr and binutils-doc (both at 2.20-2) can not be
installed together.
-- System Information:
Debian Release:
Package: libghc6-stream-dev
Version: 0.2.2-3+b1
Severity: wishlist
Current upstream version is 0.3.2.
http://hackage.haskell.org/package/Stream
Note that there are new dependencies on other Haskell libraries
over the current 0.2.2 dependencies.
-- System Information:
Debian Release: squeeze/sid
Package: libghc6-network-dev
Version: 2.2.0.1-4
Severity: wishlist
Version 2.2.1.3 is available upstream.
http://hackage.haskell.org/package/network
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64
Package: qps
Version: 1.9.18.6-2.2
Severity: grave
Justification: renders package unusable
$ qps
Segmentation fault
$ gdb qps
(no debugging symbols found)
(gdb) run
Starting program: /usr/bin/qps
[Thread debugging using libthread_db enabled]
[New Thread 0x7f6043a32760 (LWP 22540)]
Program
Package: monotone
Version: 0.43-3
Severity: grave
Justification: renders package unusable
libbotan1.8 was recently upgraded from 1.8.1 to 1.8.2.
$ mtn
mtn: error while loading shared libraries: libbotan-1.8.1.so:
cannot open shared object file: No such file or directory
$ ldd /usr/bin/mtn
Package: monotone
Version: 0.40-7
Severity: wishlist
Monotone 0.42 was released in December.
Monotone 0.42 (and 0.41) includes a number of bug fixes
on 0.40 (which is what is currently in the repository)
http://monotone.ca/NEWS
According to the upgrade notes it doesn't require database or
Package: libsqlite3-0
Version: 3.5.8-2
Severity: important
When trying to link some code I'm writing against libsqlite3-0 3.5.8-2,
I get the following error messages from the linker:
=
/usr/lib/libsqlite3.so.0: undefined reference to `dlsym'
/usr/lib/libsqlite3.so.0: undefined reference to
Package: trang
Version: 20030619-6
Severity: grave
Justification: renders package unusable
$ cat foo.rnc
start = foo | bar
foo = element foo { text }
bar = element bar { text }
^D
$ trang -I rnc -O rng foo.rnc foo.rng
Exception in thread main java.lang.NullPointerException
*** Got
Package: emacs22-common
Version: 22.2+1-1
Severity: normal
Since the upgrade to emacs 22.2, whenever I specify a file to open on the
command line, open a file with C-x C-f, or open a file through the menu,
emacs splits the windows into two frames -- the top frame has no content,
the bottom frame
Package: cupsys-client
Version: 1.3.7-1
Severity: minor
The .gz manual pages installed by cupsys-client (and a few by cupsys-bsd)
are not in gzip format.
$ file /usr/share/man/man8/cupsenable.8.gz
/usr/share/man/man8/cupsenable.8.gz: troff or preprocessor input text
When man2html is run from
Package: monotone
Version: 0.38-1
Severity: wishlist
Monotone 0.39 was released back in February.
http://www.monotone.ca/NEWS
The new version fixes several bugs and makes changes needed to
build with gcc-4.3 (needed for the upcoming 4.3 migration).
Thank you for maintaining this package.
--
Package: clamav-freshclam
Version: 0.91.2-4
Severity: normal
Whenever clamav-freshclam updates my virus definition files, I get the following
error message the next time I try to run clamscan as a normal user:
$ clamscan file_to_scan
LibClamAV Error: cli_load(): Can't open file
Package: luatex
Version: 0.11.2-1
Severity: grave
Justification: renders package unusable
luatex is currently uninstallable in sid because it depends on the obsoleted
libpoppler1 which has been removed from sid.
If a user works around this problem by installing libpoppler1 from another
archive,
Package: libruby1.8
Version: 1.8.6.111-1
Severity: important
Tags: patch
I have several programs that use REXML to generate XML documents.
Calling Document.write to output the XML document currently fails
and aborts execution with the following error message.
Package: libnoise0
Version: 0.9.0+1.0.0-RC1-1
Severity: wishlist
According to
http://sourceforge.net/projects/libnoise/
http://libnoise.sourceforge.net/downloads/index.html
libnoise 1.0.0 was released back in April 2007.
It would be great if 1.0.0 made it into the Debian repository.
-- System
Package: monotone-server
Version: 0.35-2
Severity: normal
monotone-server creates /var/run/monotone/ with
user=root, group=root, and permissions=drwxr-xr-x
Since /etc/init.d/monotone starts mtn as
user=monotone, group=monotone
the mtn process can not write to /var/run/monotone/.
The mtn process
Package: manpages-dev
Version: 2.49-1
Severity: normal
/usr/share/man/man2/epoll_pwait.2.gz is a self-referencing symlink:
$ ls -l /usr/share/man/man2/epoll_pwait.2.gz
lrwxrwxrwx 1 root root 16 2007-05-22 08:33 /usr/share/man/man2/epoll_pwait.2.gz
- epoll_pwait.2.gz
$ realpath
Package: trang
Version: 20030619-5.1+b1
Severity: important
=
# apt-get install trang
The following packages have unmet dependencies.
trang: Depends: libgcj7-0 (= 4.1.1-12) but it is not installable
E: Broken packages
=
libgcj7-0 is no longer in the sid/unstable archive.
libgcj7-1
Package: gaim-otr
Version: 3.0.0+cvs20060530-3
Severity: grave
Justification: renders package unusable
After installing gaim-otr, when gaim is started it pops up a dialog box
titled GStreamer Failure and with contents GStreamer failed to initialize
In the console I started gaim from, several
Package: mozilla-mplayer
Version: 3.31-1
Severity: minor
The mozilla-mplayer package contains the following dangling symbolic links:
/usr/lib/firefox/plugins/mplayerplug-in-gmp.so -
../../mozilla/plugins/mplayerplug-in-gmp.so
/usr/lib/firefox/plugins/mplayerplug-in-gmp.xpt -
Package: libnss-ldap
Followup-For: Bug #376426
This bug just got a bit more serious. On AMD64 the only libnss-ldap
package available in the archive is now 251-5
(so AMD64 users no longer have the option of downgrading to 238-1).
Meaning there is no functional binary libnss-ldap package for
Package: slapd
Version: 2.3.25-1
Severity: normal
I've had this problem in both slapd 2.3.24-2 and 2.3.25-1.
When slapd is running as root, everything works perfectly. But when running
as a non-root user (like the new default openldap), TLS connections fail.
This effects both port 389+starttls
Package: dokuwiki
Version: 0.0.20060309-3
Severity: normal
Tags: patch
When short_open_tag = Off is set in the php.ini file (which is recommended),
one of the lines in /usr/share/dokuwiki/lib/tpl/default/footer.html that uses
PHP short open tags causes errors to be logged to the apache logs.
The
Package: mpd
Version: 0.11.5-6
Severity: wishlist
The mpd daemon currently binds to (and listens on) all active network
interfaces by default.
It would be good from a security viewpoint to either include the line
bind_to_address 127.0.0.1
in the default mpd.conf or to ask the user
Package: xmms-flac
Version: 1.1.2-1
Severity: grave
Justification: renders package unusable
After upgrading to xmms-flac 1.1.2-1 in unstable, xmms is unable to
successfully start (it is killed by SIGABRT).
If xmms-flac is uninstalled or downgraded, xmms is able to start again.
With xmms-flac
Package: libpam-umask
Version: 0.02
Severity: grave
Justification: renders package unusable
The latest libpam-umask (0.02) encounters a SIGSEGV (Segmentation fault)
that prevents all uses from logging in through any path that references
pam_umask.so in the PAM configuration.
This even effects
Package: dsniff
Version: 2.4b1-11
Severity: important
dsniff currently Depends on libnids1 (= 1.20), but libnids1 was recently
changed to libnids1.20 in Debian/unstable - making dsniff uninstallable.
Given that the version of the source code is the same at 1.20 (only the package
name changed),
Package: libnss-ldap
Version: 238-1
Severity: important
After upgrading libnss-ldap from 220-1 to 238-1, users were unable to log in
via gdm anymore. Attempting to log in as root (which is in /etc/passwd)
produces the following:
debian login: root
Password:
login:
55 matches
Mail list logo
