Source: gbatnav
Version: 1.0.4cvs20051004-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused
Source: pacman4console
Version: 1.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused
Source: a56
Version: 1.3+dfsg-10
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change
Source: nstreams
Version: 1.0.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused
Source: adasockets
Version: 1.12-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused
Source: qm-dsp
Version: 1.7.1-7.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused
On Wed, Mar 13, 2024 at 09:44:02AM +0100, Miguel Angel Rojas wrote:
> > If "apt upgrade" is saying that it removes packages, that is a bug, yes.
>
> @david: it is not a bug, apparently.
Yeah, but for different reasons. I know that exists & even use it
frequently… but its two different things for
Source: mtree-netbsd
Version: 20180822-7
Severity: serious
Tags: ftbfs
As part of the time64 transition, -Werror=implicit-function-declaration
was enabled in default build flags. This makes mtree-netbsd fail to
build from source. A build ends with:
| gcc -DHAVE_CONFIG_H -Wdate-time
Hi,
On Sat, Mar 09, 2024 at 09:50:11PM +0100, Sebastian Ramacher wrote:
> > I'd now like to coordinate a time of upload. Given that chroots are
> > rebuilt in Wednesday and Sunday, I suggest we pick a Thursday morning
> > for the actual upload. If I unexpectedly break stuff, I still have a few
>
Control: retitle -1 nmu: zeromq3
It seems that it should be nmu instead of gb because currently they are
"Installed" state.
As buildd given-back action says:
> Package in state Installed, cannot giveback. ✗
nmu zeromq3_4.3.5-1+b1 . ANY . unstable . -m "Rebuild to sync with
64bit time_t
On Sat, 18 Mar 2023 at 14:46:47 +0100, Andrea Bolognani wrote:
> In other words, upstream developers have retroactively added symbols
> (fuse_new_31) to existing symbol groups (FUSE_3.1).
...
> really this looks like an upstream
> bug in my opinion: even if the function was present in the source
>
On Wed, Mar 13, 2024 at 03:09:03PM +0500, Andrey Rakhmatullin wrote:
> On Sun, Mar 10, 2024 at 05:51:43AM -0400, Thomas Dickey wrote:
> > | configure:7811: gcc -c -g -O2 -Werror=implicit-function-declaration
> > | -ffile-prefix-map=/<>=. -fstack-protector-strong
> > | -fstack-clash-protection
Package: dict-vera,dict-wn,dictd
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
When installing dict-vera, dict-wn and dictd, and removing or purging
then all in same apt batch execution fails like this:
Afinstallerer dict-gcide (0.48.5+nmu2) ...
Afinstallerer dict-jargon
Control: tag 1066090 fixed-upstream
On Wed, 13 Mar 2024 at 00:30, Tim Connors wrote:
> I'm guessing it's looking at field 22 starttime in /proc/$pid/stat?
> starttime is seconds since boot. Since the process exists in the
> parent system as well, starttime will surely be seconds since host
>
On Tue, 12 Mar 2024 at 23:13:30 -0500, Steven Robbins wrote:
> I checked the build logs for cargo and noticed that most architectures have
> been built on the buildds. All release arches except armel & armhf. How is
> it that these two have build dep installability problems but others do not?
On Sun, 04 Feb 2024 09:15:42 +0100 Tollef Fog Heen
wrote:
> Package: initramfs-tools-core
> Version: 0.142
> Severity: wishlist
>
> It would be nice if initramfs-tools-core used zstdmt (multi-threaded)
> instead of plain zstd when creating the initramfs. On my system, that
> saves about 15% of
Package: wnpp
Severity: wishlist
Owner: Guilherme Puida Moreira
* Package name: golang-github-schollz-pake
Version : 3.0.5-1
Upstream Author : Zack
* URL : https://github.com/schollz/pake
* License : Expat
Programming Lang: Go
Description : Generate a
> On Thu, Mar 07, 2024 at 05:02:29PM +0200, Peter Pentchev wrote:
>> On Thu, Mar 07, 2024 at 03:25:01PM +0100, Manuel Traut wrote:
>>> On 7 Feb 2024, at 18:27, Dima Kogan wrote:
>>>
>>> Hi. Thanks for your contribution. I looked at the upstream code a tiny
>>> bit, and it looks like it might
Package: liblapackpp-dev
Version: 2023.11.05-1
Severity: normal
Dear Maintainer,
liblapackpp-dev lacks a dependency on libblaspp-dev.
The latter is needed as
/usr/lib//cmake/lapackpp/lapackConfig.cmake
has a ``find_dependency(blaspp)'' command.
Cheers,
--
Pierre
-- System Information:
Hi,
On Fri, 27 Oct 2023 21:42:50 +0200 Lucas Nussbaum wrote:
> Source: opam
> Version: 2.1.5-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231027 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package
On Mon, Sep 04, 2023 at 07:28:06AM -0400, Reinhard Tartler wrote:
> I'll try to patch podman to use the older API, but it seems to me the
> docker.io package in debian is lagging several upstream releases behind
> anyways.
>
> any plans to upgrade it soon?
Echoing Reinhard here. Lots of external
Control: tags -1 + moreinfo
On Wed, Mar 13, 2024 at 12:17:12AM +0100, Antoine Sirinelli wrote:
> When I create a new custom network, the dns is not enabled:
>
> $ podman network create test
> test
> $ podman network inspect test
>
> [...]
>
> The outcome should have "dns_enabled" to true.
Per
On Sun, Mar 10, 2024 at 05:51:43AM -0400, Thomas Dickey wrote:
> | configure:7811: gcc -c -g -O2 -Werror=implicit-function-declaration
> | -ffile-prefix-map=/<>=. -fstack-protector-strong
> | -fstack-clash-protection -Wformat -Werror=format-security -fPIE
> | -D_LARGEFILE_SOURCE
[22:39] * | h01ger filed a bug about 5/6/15/16 loosing network now
[22:40] * | mapreri ponders the accuracy: the link was still up, so perhaps it
only lost the IP somehow?
[22:40] next time I will look up the dhcp lease if there is anything
odd
[22:40] mapreri: that pondering could be the
On Sun, Mar 10, 2024 at 11:19:48PM +0100, Sebastian Ramacher wrote:
> hmm/hmm.c: In function ‘invert’:
> hmm/hmm.c:703:15: error: implicit declaration of function ‘dgetrf_’
> [-Werror=implicit-function-declaration]
> 703 | ret = dgetrf_(, , a, , ipiv, ); /* ret should
> be zero,
On Sat, Mar 09, 2024 at 10:42:33PM +0100, Sebastian Ramacher wrote:
> /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I../.. -I../../src/include -I../../src -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g
> -O2
On Sat, Mar 09, 2024 at 09:54:29PM +0100, Sebastian Ramacher wrote:
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib/driver
> -I../../include -I../../include/ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
>
package: jenkins.debian.org
not strictly a jenkins.d.o topic, but it would be nice to have mastadon
mentions on #reproducible-builds again in that channel.
https://github.com/hackspace-marburg/troet
is a Mastodon plugin for Sopel IRC bots, sopel is available in Debian.
--
cheers,
On Wed, Mar 13, 2024 at 12:35:14AM -0700, Chandler Sobel-Sorenson wrote:
> I concur and also request `--no-all-versions` apply to `apt-cache
> policy` command as well.
What would this achieve; what is the use case?
I literally see no point in having 'policy' limited to a single version
(and
> This is because reprepro does not generate or support these
> dep11/Components-*.ym.gz files...
My workaround was to download Components files:
${YOUR_MIRROR}/dists/bookworm/main/dep11/Components-amd64.yml.gz
and
${YOUR_MIRROR}/dists/bookworm/non-free-firmware/dep11/Components-amd64.yml.gz
Package: pekwm
Version: 0.1.18-1
Severity: wishlist
X-Debbugs-Cc: a.t.chadw...@gmail.com
Dear Maintainer,
A new version of pekwm, 0.30.0, has been available from upstream since Jan
2023. I understand that it comes with a bunch of desktop-focused utilities
now. Please can you consider updating
Hi there,
> If "apt upgrade" is saying that it removes packages, that is a bug, yes.
@david: it is not a bug, apparently.
To put everything in a nutshell:
- "apt upgrade" can remove packages
- "apt upgrade" accepts specific packages to be upgraded
Therefore, this behaviour is expected
Control: tags -1 pending
Sean Whitton writes:
> Hello,
>
> On Tue 12 Mar 2024 at 08:47pm -07, Xiyue Deng wrote:
>
>> Sean Whitton writes:
>>
>>> Hello Xiyue,
>>>
>>> Do you still intend to adopt persp-projectile?
>>>
>>> Thanks.
>>
>> Yes. And it seems I forgot to close this ITA bug in the
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: networking-generic-switch
Version : 7.2.0
Upstream Contact: OpenStack Foundation
* URL : https://github.com/openstack/networking-generic-switch
*
Christoph Biedl wrote...
> So, assuming this is the cause here, the fix is pretty simple:
(...)
> +#ifdef INET6
> if (if6_is_up)
> sif6down(0);
> +#endif
This was silently done as part of
commit 80b8744eb42c7493794f3e3fe0bf1ce14f53e6dd
Author: Eivind Næss
Date: Fri Aug 6
On Mon, Mar 04, 2024 at 07:34:06PM +0100, Sven Joachim wrote:
> Not really, these arches now default to a 64-bit time_t and therefore
> you get the conflicting types (suseconds_t is a long int,
> __suseconds64_t a long long int). This has nothing to do with implicit
> function declarations.
It's
On Tuesday, March 12, 2024 11:56:48 PM CET Thorsten Glaser wrote:
> Source: gnupg2
> Version: 2.2.40-1.1
> Severity: serious
> Justification: ftbfs
> X-Debbugs-Cc: t...@mirbsd.de
>
> Trying to binNMU gnupg2 to make it installable during t64 transition,
> I notice the following configury output:
I concur and also request `--no-all-versions` apply to `apt-cache
policy` command as well.
Perhaps, instead, a new option with argument `--versions=N` could be
implemented, allowing a limited number of versions to be returned, with
`--versions=0` or `--versions=none` being the equivalent of
The patch below builds for me on the hppa platform.
Testcases needs verifying on physical hardware though.
Helge
diff -up ./testsuite/path.c.org ./testsuite/path.c
--- ./testsuite/path.c.org 2024-03-13 07:01:04.610222544 +
+++ ./testsuite/path.c 2024-03-13 07:11:16.630339502 +
@@
Control: tags -1 wontfix
Andreas Metzler:
On 2024-03-10 Niels Thykier wrote:
Andreas Metzler:
[...]
supporting build-profiles like nodoc with dh_install seems to cumbersome.
Any reason for not using dh_installdocs, which does `nodoc` out of the box?
Hello Niels
Because for this
Hi Ted,
On Sun, Mar 10, 2024 at 09:56:46PM +0100, Helmut Grohne wrote:
> I've uploaded this to experimental directly to clear NEW and to get a
> dumat report quickly. Barring your opposition, I'll NMU this to unstable
> as well.
Given reviews from Michael Hudson-Doyle, Matthias Klose and Steve
Source: mate-equake-applet
Version: 1.3.8.2-1.1
Severity: serious
Tags: ftbfs
Due to the time64 transition -Werror=implicit-function-declaration was
turned on by default in unstable. This change makes mate-equake-applet
fail to build from source. Relevant snippet:
| equake_processdata.c: In
Hello,
On Tue 12 Mar 2024 at 08:47pm -07, Xiyue Deng wrote:
> Sean Whitton writes:
>
>> Hello Xiyue,
>>
>> Do you still intend to adopt persp-projectile?
>>
>> Thanks.
>
> Yes. And it seems I forgot to close this ITA bug in the Changelog. Can
> we close this directly instead?
We could, but I
Source: erlang-jiffy
Version: 1.1.1-2
Severity: normal
X-Debbugs-Cc: wuruil...@loongson.cn
User: debian-de...@lists.debian.org
Usertags: loong64
Dear Maintainer,
Erlang-jiffy has a compilation error in the loong64 architecture.
The attached patch solves the problem. Please refer to it supports
Hi,
On 2024-03-12 23:22, Preuße, Hilmar wrote:
> On 12.03.2024 21:59, Aurelien Jarno wrote:
>
> Hi Aurelien,
>
> > Starting with glibc 2.31, support for NIS (libnsl library) has been
> > moved to a separate libnsl2 package. In order to allow a smooth
> > transition, a libnsl-dev has been added
701 - 745 of 745 matches
Mail list logo
