* Chris Hofstaedtler [240429 15:24]:
> > udisks2's autopkgtest fails when tried together with util-linux 2.40. An
> > example can be seen here:
> > https://ci.debian.net/packages/u/udisks2/testing/amd64/46012
Dear util-linux@,
in Debian, udisks2 2.10.1-6 (autopkg-)tests fail with util-linux
2.40, but passed with 2.39. We are not yet sure if this is directly
caused by util-linux, but it seems somewhat likely.
I won't get to it this week (also re: stable v2.40.1), but maybe
someone else has seen this
Control: reassign -1 dpkg
* Vincent Lefevre [240428 22:33]:
> Package: fdisk
> Version: 2.40-8
> Severity: serious
...
> Setting up util-linux (2.40-8) ...
> fstrim.service is a disabled or a static unit not running, not starting it.
> dpkg: error: dpkg frontend lock was locked by another
Source: mmdebstrap
Version: 1.4.3-6
Severity: serious
X-Debbugs-Cc: debian-rele...@lists.debian.org
Hi,
the autopkgtests for mmdebstrap as part of migration tests for
testing/amd64 fail with apt reporting 'Not found' errors.
As an example, for this scenario:
mmdebstrap 1.4.3-6
util-linux/2.40-8
Source: udisks2
Version: 2.10.1-6
Severity: serious
Hi,
udisks2's autopkgtest fails when tried together with util-linux 2.40. An
example can be seen here:
https://ci.debian.net/packages/u/udisks2/testing/amd64/46012968/
537s ==
Control: tag -1 pending
Hello,
Bug #1069923 in util-linux reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1069064 in util-linux reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
* Moritz Muehlenhoff [240425 08:44]:
> On Thu, Apr 25, 2024 at 08:37:14AM +0200, Chris Hofstaedtler wrote:
> > Hi Moritz,
> >
> > could we once again use the upstream release for stable?
> > debdiff 4.8.7-1 -> 4.8.8-1 is attached.
>
> Ack. Following the 4.8
On Wed, Apr 24, 2024 at 09:25:29AM +0300, Andrius Merkys wrote:
> Hi,
>
> On Mon, 19 Feb 2024 21:35:16 + Steve Langasek
> wrote:> Since turning on 64-bit time_t is being handled centrally through a
> change
> > to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
> >
Control: reassign -1 release.debian.org
Control: retitle -1 nmu: efingerd_1.6.7-1
Control: severity -1 normal
On Thu, Feb 29, 2024 at 02:41:54PM -0500, Boyuan Yang wrote:
> Severity: serious
> Justification: Policy 2.2.1
>
> Package efingerd depends on binary package libident, but this package
On Thu, Apr 04, 2024 at 07:16:34PM -0300, Paulo Henrique de Lima Santana wrote:
> Would be possible reintroduce libnss-db to testing?
>
> I'm asking because I'm maintainer of the pglistener package and I know there
> aren't plans to update the sofwtare with another database solution.
Well what's
ping to prevent autoremoval from testing, while time_t-64bit
migration is unfinished.
Hi Helmut,
On Mon, Apr 15, 2024 at 08:58:42PM +0200, Helmut Grohne wrote:
> I think I mentioned this on IRC already and you intended to revert, but
> nothing happened, so lets turn this into a bug for tracking purposes at
> least.
Indeed, I forgot to follow up afterwards. Thanks for keeping
On Fri, Apr 12, 2024 at 09:11:51AM +0200, Jan Katins wrote:
> Package: cryptsetup
> Version: 2:2.7.2-1
> Severity: normal
>
> Dear Maintainer,
>
> After a recent apt upgrade on a debian sid system (installed about 3
> years ago with an installer, choosing to encrypt the filesystem, no
> idea
unknown ‘-Werror=implicit-function-declaration’
+in cc1plus aborting the build.
+
+ -- Chris Hofstaedtler Thu, 11 Apr 2024 15:37:03 +0200
+
openzwave (1.6.1914+ds-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru openzwave-1.6.1914+ds/debian/control openzwave-1.6.1914+ds
)
+ * Replace Build-Depends: pkg-config (deprecated) with pkgconf
+
+ -- Chris Hofstaedtler Tue, 09 Apr 2024 09:28:44 +0200
+
tgt (1:1.0.85-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru tgt-1.0.85/debian/control tgt-1.0.85/debian/control
--- tgt-1.0.85/debian/control 2023-11-17 22:35
On Sun, Mar 24, 2024 at 03:42:18PM +0500, Andrey Rakhmatullin wrote:
> On Wed, Mar 13, 2024 at 01:03:20PM +0100, Lucas Nussbaum wrote:
> > > ./config.h:2540:11: fatal error: trio.h: No such file or directory
> > > 2540 | # include "trio.h"
> > > | ^~~~
> (this suggests that
Control: tags -1 + patch
Hi,
On Sun, Apr 07, 2024 at 01:28:11PM +0200, Sebastian Ramacher wrote:
> Source: tgt
> Version: 1:1.0.85-1.1
> Severity: serious
> Control: block #1065470 by -1
> X-Debbugs-Cc: sramac...@debian.org
>
> ceph no longer supports 32 bit architectures. Please stop build
>
Control: tag -1 pending
Hello,
Bug #1067849 in util-linux reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1067849 in util-linux reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tags -1 + pending
* Simon McVittie [240317 15:57]:
> Package: libruby
> Version: 1:3.1
[..]
> Now that libruby3.1t64 has reached unstable, libruby is uninstallable on
> the architectures affected by the 64-bit time_t transition,
[..]
> I suspect the only change needed here is to
Control: tag -1 pending
Hello,
Bug #1067043 in ruby-defaults reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Source: lintian
Version: 2.117.0
Severity: serious
dpkg has turned on -Werror=implicit-function-declaration on some
archs (compare #1065371 and the earlier bug requesting this). This
in turn causes lintian's autopkgtests to fail on armel, armhf and
maybe others, like this:
Control: tag -1 pending
Hello,
Bug #1065242 in util-linux reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
* Paul Gevers [240126 22:25]:
> Hi zeha,
>
> On 26-01-2024 10:21, Chris Hofstaedtler wrote:
> > I see this "works", but now the tests fail after one try on the
> > problematic worker and then are never retried. Can this please be
> > fixed?
>
> What do
clone 1059995 -1
reopen -1
reassign -1 systemd
found -1 systemd/254.3-1
forwarded -1 https://github.com/systemd/systemd/issues/31037
thanks
Dear systemd Packagers,
Paul Gevers noted that src:pdns's autopkgtests fail every so often
on a large amd64 debci worker and on s390x workers. Apparently a
Hi Paul,
* Paul Gevers [240104 18:14]:
> Can you figure out decent numbers for these? Below I printed the output of
> lsipc and AFAICT SHMMAX is already pretty big ;) (and the same on all our
> hosts, which is also true for MSGMAX).
>
> On the other hand, $(ipcs -a) doesn't show anything on the
Source: fsprotect
Severity: serious
fsprotect hasn't made it into bullseye or bookworm. It depends on
the broken aufs package. It hasn't seen a (non-QA) upload since
2017.
With this background I propose removal from unstable.
If you intend to keep fsprotect in Debian, please start maintaining
On Fri, Jan 12, 2024 at 08:02:53PM +0100, Paul Gevers wrote:
> Hi,
>
> On 12-01-2024 12:36, Chris Hofstaedtler wrote:
> > can you confirm two additional things please:
> >
> > 1) this happens only on the large host?
>
> https://ci.debian.net/packages/p/pdns/t
Hi,
can you confirm two additional things please:
1) this happens only on the large host?
2) this does not or does happen with other packages also requesting
the same settings from systemd, e.g. dnsdist or pdns-recursor?
Chris
Source: epics-base
Version: 7.0.7+dfsg1-5
Severity: serious
Tag: ftbfs
Your package failed to build from source in binNMUs to move systemd
files. Please see f.e. this build log:
https://buildd.debian.org/status/fetch.php?pkg=epics-base=amd64=7.0.7%2Bdfsg1-5%2Bb1=1704674513=0
Last parts:
Test
On Sun, Sep 03, 2023 at 08:26:00PM +0200, Moritz Mühlenhoff wrote:
> severity 877016 serious
> thanks
>
> Am Thu, Sep 28, 2017 at 06:51:30AM -0700 schrieb Mattia Dongili:
> > On Wed, Sep 27, 2017 at 03:16:52PM -0400, Phil Susi wrote:
> > > Package: cpufrequtils
> > > Version: 008-1
> > ...
> > >
On Thu, Jan 04, 2024 at 03:37:21PM +0100, Paul Gevers wrote:
> Hi,
>
> On 04-01-2024 15:08, Chris Hofstaedtler wrote:
> > It would seem that the host runs out of IPC space?
>
> What is IPC space?
https://manpages.debian.org/bookworm/manpages/sysvipc.7.en.html
https:
On Thu, Jan 04, 2024 at 02:42:59PM +0100, Paul Gevers wrote:
> 269s Dec 25 16:13:20 ci-359-77591125 (s_server)[3766]: pdns.service: Failed
> to set up IPC namespacing: Resource temporarily unavailable
> 269s Dec 25 16:13:20 ci-359-77591125 (s_server)[3766]: pdns.service: Failed
> at step NAMESPACE
installation of tbtacl-write. (Closes: #1058828)
+
+ -- Chris Hofstaedtler Sun, 24 Dec 2023 14:13:22 +0100
+
thunderbolt-tools (0.9.3-6) unstable; urgency=medium
* Roll in all fixes since 0.9.3, project is now in maintainence
diff -Nru thunderbolt-tools-0.9.3/debian/install thunderbolt-tools-0.9.3
systemdsystemunitdir from systemd.pc to determine systemd unit install
+path.
+ * udeb: move debian-installer-startup.d/S37alsa-utils-udeb into /usr/lib.
+
+ -- Chris Hofstaedtler Sun, 24 Dec 2023 12:42:40 +0100
+
alsa-utils (1.2.10-1) unstable; urgency=medium
* New upstream release.
diff -Nru alsa
severity 1057231 serious
severity 1057240 serious
severity 1057245 serious
severity 1058828 serious
thanks
udev.pc was changed today. Your package will now either FTBFS or
introduce a policy violation on a rebuild.
Chris
On Sat, Dec 16, 2023 at 02:51:03PM +, Debian Bug Tracking System wrote:
>* upload to experimental for dumat tool
>* Move udev files from /lib to /usr/lib, including protective diversion
> against Multi-Arch: same file loss scenario (DEP17 P7 M10).
> (Closes: #1058787)
Please
Hi,
* Pali Rohár [231216 11:35]:
> On Friday 15 December 2023 21:56:01 Chris Hofstaedtler wrote:
> Hello, I talked with the author of the netplug (Bryan O'Sullivan) and I
> got permission to continue working on this project. I can continue
> maintaining this package on Debian, so p
.
+
+ [Helmut Grohne]
+
+ * Install units using dh_installsystemd only. (Closes: #1054485)
+
+ -- Chris Hofstaedtler Tue, 19 Dec 2023 01:24:10 +0100
+
postfix (3.8.2-1) unstable; urgency=medium
[Scott Kitterman]
diff -Nru postfix-3.8.2/debian/postfix.dirs postfix-3.8.2/debian/postfix.dirs
--- postfix
Source: ceph
Version: 18.2.0+ds-1
Severity: serious
User: helm...@debian.org
Usertags: dep17p1
X-Debbugs-Cc: helm...@debian.org
Hi,
the file /lib/systemd/system/ceph-volume@.service was previously
part of the ceph-osd binary package, but has now moved to
ceph-volume. However, this file will also
Package: libmirisdr4
Version: 2.0.0-1
Severity: serious
Tags: patch
User: helm...@debian.org
Usertags: dep17p7
X-Debbugs-Cc: helm...@debian.org
Hi,
your package libmirisdr4 is marked Multi-Arch: Same and introduced a
new file into /lib.
I'm filing this bug now so your package will not hit
Source: netplug
Version: 1.2.9.2-3.2
Severity: serious
I'm filing this to get netplug removed from testing, with the goal
of removing it from unstable later, and before that happens, anyone
who wants to actually maintain this package can speak up.
As demonstrated today, having packages in stable
Control: found -1 scanbd/1.5.1-6+b1
Control: block -1 by 1058752
Hi Andreas,
I'm unsure what to do here. This problem is triggered by a behaviour
change in coreutils.
On Fri, Dec 15, 2023 at 03:17:18PM +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to
Package: coreutils
Version: 9.4-1
Severity: serious
Tags: upstream
Control: affects -1 initramfs-tools scanbd
Hi,
cp and mv -n changed their behaviour with regard to their exit code
when doing nothing, and also now write to stderr.
This causes a few problems in existing packages:
1)
systemdsystemunitdir changed in systemd.pc
+(Closes: #1057421)
+
+ -- Chris Hofstaedtler Fri, 15 Dec 2023 01:23:13 +0100
+
sysstat (12.6.1-1) unstable; urgency=medium
* New upstream stable version: fixes size_t overflow in sa_common.c
diff -Nru sysstat-12.6.1/debian/control sysstat-12.6.1
Hi everyone!
On Tue, Dec 12, 2023 at 03:08:49PM +0100, Helmut Grohne wrote:
[..
> Almost two weeks later, I'm back with what I hope is a solution.
[..]
> At the time of this writing, my preferred solution is restoring the lost
> files in postinst. Fortunately, they are all symlinks in the case of
Source: libnss-db
Version: 2.2.3pre1-8
Severity: serious
Tags: upstream
libnss-db is the so-called "Berkeley DB NSS". It last saw upstream
changes in 2001, and obviously depends on Berkeley DB 5.3. We want to
get rid of Berkeley DB, and now is as good a time as any other to stop
shipping
Control: severity -1 normal
Control: tags -1 = wontfix
* Svante Signell [231208 19:38]:
> On Fri, 2023-12-08 at 16:15 +0100, Svante Signell wrote:
> > reopen 1056980
> > severity 1056980 serious
> > tags 1056980 patch
> > thanks
>
> Sorry, forgot the patch!
>
> ---
to place udev rules file.
+ * Fix FTBFS by correcting usb_open retval check (Closes: #984100)
+ * Bump to dh compat level 13, away from obsolete level 9.
+Record not installed files in debian/not-installed.
+
+ -- Chris Hofstaedtler Fri, 08 Dec 2023 17:37:04 +0100
+
libdjconsole (0.1.3-3
Control: tags -1 + patch
* Chris Hofstaedtler :
> systemd.pc changed systemd_system_unit_dir to point to /usr. As a
> consequence, your package now FTBFS in unstable.
Please find a patch fixing this attached. It should also work if
sysstat is backported without additional changes.
Best,
Source: tracker-miners
Version: 3.4.6-1
Severity: serious
Tags: ftbfs
Dear Maintainer,
your package FTBFS in unstable, in my own test rebuild as well as on the Debian
buildds.
Build log snippet, hopefully relevant:
Traceback (most recent call last):
File
Hello Maitland,
* Chris Hofstaedtler [231205 20:01]:
> * Maitland Bottoms [231203 14:57]:
> > Helmut Grohne writes:
> > > Then when you retry it, please go for experimental first. Then have
> > > Chris or me check your upload is ok and only then proceed with
Source: pmix
Version: 5.0.1-3
Severity: serious
Tags: ftbfs
Dear Maintainer,
your package FTBFS in unstable, in my own test rebuild as well as on
reproducible-builds.org.
Build log snippet, hopefully relevant:
dh_missing: warning: usr/lib/x86_64-linux-gnu/pmix2/local/bin/cygdb exists
in
Source: ovn
Version: 23.09.0-1
Severity: serious
Tags: ftbfs
Dear Maintainer,
your package FTBFS in unstable, in my own test rebuild as well as on
reproducible-builds.org.
Build log snippet, hopefully relevant:
cd ovs && tar -xzf /usr/src/openvswitch/openvswitch.tar.gz
--strip-components=1
Source: sysstat
Version: 12.6.1-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: dep17m2
Dear Maintainer,
systemd.pc changed systemd_system_unit_dir to point to /usr. As a
consequence, your package now FTBFS in unstable. Due to a human
mistake this problem was not caught before
Source: cfengine3
Version: 3.21.0-3
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: dep17m2
Dear Maintainer,
systemd.pc changed systemd_system_unit_dir to point to /usr. As a
consequence, your package now FTBFS in unstable. Due to a human
mistake this problem was not caught
Source: gnustep-make
Version: 2.9.1-2
Severity: serious
Tags: ftbfs
Dear Maintainer,
gnustep-make-doc currently FTBFS in unstable, in both my own test build
and on reproducible-builds. Here is a part of the build log:
Installing GNUstep configuration file in
Source: aalib
Version: 1.4p5-50
Severity: serious
Tags: ftbfs
Rebuilding your package in unstable currently fails:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat
Hello Maitland,
* Maitland Bottoms [231203 14:57]:
> Helmut Grohne writes:
>
> > Then when you retry it, please go for experimental first. Then have
> > Chris or me check your upload is ok and only then proceed with uploading
> > to unstable.
>
> hackrf_2023.01.1-6 now in experimental is the
Hello Jonas,
* Scott Talbert [231203 14:06]:
> haskell-pandoc has been accepted into unstable, so I think you should be
> able to update src:pandoc to now build from the pandoc-cli hackage package.
[..]
Sorry for nudging here, but pandoc is used as a build dependency on
quite a few libraries
Source: modemmanager
Version: 1.22.0-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: dep17m2
Dear Maintainer,
modemmanager currently FTBFS in unstable, like this:
...
dh_auto_configure -- -Dgtk_doc=true \
-Ddbus_policy_dir=/usr/share/dbus-1/system.d \
Control: severity -1 normal
Control: tags -1 = wontfix
* Klaus Ethgen [231127 19:13]:
> Package: mingetty
> Version: 1.08-5
> Severity: grave
>
> After the recent update, init runns cracy trying to run mingetty.
> Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty"
[..]
> merged-usr: no
Control: tags -1 + patch
* Chris Hofstaedtler [231126 20:11]:
> your package apparently FTBFS, probably caused by the newer version of
> sphinx.
Please find a patch attached.
Chris
diff -Nru hackrf-2023.01.1/debian/rules hackrf-2023.01.1/debian/rules
--- hackrf-2023.01.1/debian/rules 2
Source: hackrf
Version: 2022.09.1-3
Severity: serious
Tags: ftbfs
Dear Maintainer,
your package apparently FTBFS, probably caused by the newer version of
sphinx.
Last few lines from the build log:
make[3]: Leaving directory '/<>/docs/build/latex'
make[2]: Leaving directory '/<>/docs'
cd
I will upload this patch in a few minutes. For your convenience,
please find an MR here:
https://salsa.debian.org/pkg-security-team/arpon/-/merge_requests/4
Chris
Package: tracker.debian.org
Severity: serious
Dear tracker.d.o owners,
as you probably have already noticed, the migration data for a lot of
packages appears stuck in the past, probably on or before 2023-11-14.
As an example, https://tracker.debian.org/pkg/multipath-tools shows "Too
young, only
leading to
+FTBFS. (Closes: #1040748)
+Fixing this in debhelper for all packages would obviously be preferred,
+but for now this has to do.
+
+ -- Chris Hofstaedtler Sun, 06 Aug 2023 14:42:07 +0200
+
pycairo (1.24.0-1) unstable; urgency=medium
* Team upload
diff -Nru pycairo-1.24.0
Hi,
after trying to fix this bug, on bookworm chkservice only shows
"Failed: Device or resource busy" for me. Also, upstream apparently
deleted the source repository.
Do you think its viable to fix this package or should it maybe be
removed instead?
Chris
Hi Anton,
* roehl...@debian.org :
> Source: wslay
[..]
>
> your package wslay will soon experience autopkgtest failures because
> the new CMake release 3.27 will issue a deprecation warning on stderr
> if cmake_minimum_required() asks for compatibility with CMake 3.4 or
> older.
I've opened an
+
+++ h2o-2.2.5+dfsg2/debian/changelog2023-03-21 12:40:38.0 +
@@ -1,3 +1,11 @@
+h2o (2.2.5+dfsg2-7) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove VCS tags from picohttpparser source files
+ * Disable failing mruby test (Closes: #1032554)
+
+ -- Chris
Control: severity -1 important
* Bastian Germann [230226 14:12]:
> Control: retitle -1 RM: mercurial-buildpackage -- RoQA; no users left
> Control: severity -1 serious
>
> On Tue, 20 Dec 2022 03:24:46 +0100 Chris Hofstaedtler wrote:
> > It would appear mercurial-buildpac
Source: libbase58
Version: 0.1.4-5
Severity: serious
libbase58 appears to be a leaf library package - nothing else in Debian
debends on it. Apparently it was introduced for some other
bitcoin-related libraries, which are gone again.
I would suggest we waste no resources on this for bookworm.
Source: scalc
Version: 0.2.4-6
Severity: serious
It appears src:scalc only builds a library package, and nothing in
Debian uses it. If people see value in keeping it in bookworm,
please speak up.
I'll note that there is a new, completely unrelated project using
the "scalc" name, so it might be a
* Adrian Bunk :
> Source: libcommoncpp2
[..]
> src:ucommon is the successor of libcommoncpp2, and the only
> remaining build dependency on libcommoncpp2-dev in
> vdr-plugin-fritzbox is stale.
It appears all r-(build-)deps are gone. Should src:libcommoncpp2
also go away from unstable?
Chris
* Dmitry Bogatov :
>
> [2019-03-16 00:41] Lorenzo Puliti
> > >Bogatov wrote:
> > >Dear git maintainer, you could plug this bug by adding
> > >`/var/lib/supervise/git-daemon' into `debian/git-daemon-run.dirs'.
> >
> > Dmitry, are you sure? runsv can create the 'git-daemon' directory if
> > it's
* YunQiang Su :
> 在 2022/1/14 23:30, Sandro Tosi 写道:
> > On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su
> > wrote:
> > >
> > > On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel
> > > wrote:
> > > > Built with gcc-11 and -fno-lto it doesn not work.
> > > >
> > > >
> > >
Control: retitle -1 VMs created on buster do not boot on bullseye
Control: severity -1 normal
Control: tags -1 + moreinfo
Control: reassign -1 virt-daemon
Hi everyone,
I just spent some time trying to reproduce this, until I re-read the
bug report more carefully. I think it says, in my words:
Source: golang-github-unknwon-i18n
Version: 0.0~git20170218.0.8372b90-1
Severity: serious
This package was introduced as a library used by gitea, but has not seen
updates in 5 years and gitea itself is also long gone. Upstream also has
given up on it many years ago.
Lets keep these bits out of
Source: golang-github-siddontang-go-snappy
Version: 0.0~git20140704.0.d8f7bb8-6.1
Severity: serious
This package was introduced for gitea, and has been orphaned once gitea
was removed. It has seen no updates since. Lets keep these libraries out
of testing.
Chris
Package: x-loader
Version: 1.5.1+git20110715+fca7cd2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Dear QA Group,
the package x-loader was recently gifted to you, but it FTBFS:
gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -msoft-float -Werror
* Niels Thykier :
> The fakeroot/1.30.1-1 FTBFS on mipsel (release arch) which blocks the fix
> for #1023286 from affecting mipsel binaries.
I'll note that the FTBFS is caused by a test failure in test
"t.chown". stat(1) is used to check the expected owner of a file,
and the test reveals (I
* Helge Kreutzmann :
> for what is worth:
> helge@samd:/tmp$ debget nghttp2
> Get:1 http://172.16.18.51:/ftp.de.debian.org/debian bullseye/main
> amd64 nghttp2 all 1.43.0-1 [14.4 kB]
> Fetched 14.4 kB in 0s (117 kB/s)
For anyone reading along: this "success" is, because nghttp2
switched to
* Sebastian Ramacher [221129 11:21]:
> Source: cmark-gfm
> Version: 0.29.0.gfm.6-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>
> https://buildd.debian.org/status/fetch.php?pkg=cmark-gfm=s390x=0.29.0.gfm.6-2=1666810004=0
>
The bug for release-notes is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021490
Chris
rom 095ac91986212502a7fb35c1de9808cf304e1e78 Mon Sep 17 00:00:00 2001
From: Chris Hofstaedtler
Date: Sun, 9 Oct 2022 11:47:33 +
Subject: [PATCH] git-daemon-run.postrm: remove -f flag from deluser call
Does not exist since #1002495 and was always wrong.
Signed-off-by: Chris Hofstaedtler
---
debian/git-dae
guile-3.0 3.0.8-2 builds fine (on the buildds and locally).
Should this bug be closed?
Chris
Control: severity -1 normal
0.11.2-2 added a workaround patch, so the FTBFS itself is gone.
Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: vzquota -- RoQA; orphaned, missing kernel support
Control: affects -2 src:vzquota
Control: severity -2 normal
Dear ftpmasters,
please remove vzquota. It is orphaned for a long time, and requires
kernel patches that
Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: vzctl -- RoQA; orphaned, missing kernel support
Control: affects -2 src:vzctl
Control: severity -2 normal
Dear ftpmasters,
please remove vzctl. It is orphaned for a long time, and requires
kernel patches that have
Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: severity -2 normal
Control: retitle -2 RM: charybdis -- RoQA; upstream dead; replacements exist
* Antoine Beaupré [220813 20:07]:
> On 2022-08-02 13:46:44, Chris Hofstaedtler wrote:
> > * Antoine Beaupre :
> >>
Control: severity -1 normal
Control: tags -1 + moreinfo
* Mcgiwer :
> I had discovered an very annoying and serious bug in the "mount" package:
>
> While attempting to mount a hard disk while beeing logged in locally in
> terminal (as root), the mount command forces following mount options:
>
16:44:50.0 +
+++ dmraid-1.0.0.rc16/debian/changelog 2022-08-02 23:30:56.0 +0000
@@ -1,3 +1,10 @@
+dmraid (1.0.0.rc16-11.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop udebs.
+
+ -- Chris Hofstaedtler Tue, 02 Aug 2022 23:30:56 +
+
dmraid (1.0.0.r
* Antoine Beaupre :
> After a somewhat long period of uncertainty, Charybdis has been
> finally abandoned upstream. The official git repository here:
>
> https://github.com/charybdis-ircd/charybdis
>
> .. is marked as "archived by the owner [and] read-only".
Is it time to file an RM bug, given
Control: reassign -1 src:linux
Dear Håkan,
thanks for reporting back and testing!
* Håkan T Johansson [220801 19:31]:
> On Sun, 31 Jul 2022, Chris Hofstaedtler wrote:
>
> > I can't see a difference that should matter from userspace.
> >
> > I have stared
* Andreas Beckmann :
> Are you installing that file manually instead of using dh_bugfiles -A ?
Obviously we did, because dh_bugfiles did not exist until October
2008. :-)
Switched to dh_bugfiles now, thanks.
Chris
Control: reassign -1 libspdlog1
Control: affects -1 gnuradio
* Jan - PE0SAT :
> ImportError: /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.10.3:
> undefined symbol:
> _ZN6spdlog5sinks15basic_file_sinkINS_7details10null_mutexEEC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEb
Hi Håkan,
* Håkan T Johansson [220730 23:43]:
> I have now tried with the mdadm 4.2~rc2-2 installed in both the chroot
> environment (tried only that first), and also the host system.
> Unfortunately, the host / fs is still affected when running
> 'update-initramfs -u', when /dev is not mounted.
Hi debian-boot,
* László Böszörményi (GCS) [220730 15:34]:
> On Sat, Jul 30, 2022 at 1:50 PM Chris Hofstaedtler wrote:
> > whats the status of dmraid? Do you have dmraid hardware or is this
> > merely on life-support?
> Please note dmraid upstream is dead for more than
Hi Laszlo,
whats the status of dmraid? Do you have dmraid hardware or is this
merely on life-support?
* Paul Gevers :
> What would you say about this? Even if d-i would not need it anymore, we
> would need work to drop the dependency chain via
> libblockdev/udisks2/gnome-control-center.
I'm
1 - 100 of 247 matches
Mail list logo
