On 2022-05-26, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Thanks for doing the rebuild testing!
> Relevant part (hopefully):
Would it be at all possible to update your script to compress and attach
data over a certain size? This
Source: qutemol
Version: 0.4.1~cvs2008-14
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -g
Source: python-bitcoinlib
Version: 0.11.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: veusz
Version: 3.3.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
>
Source: power-profiles-daemon
Version: 0.10.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: oscrypto
Version: 1.2.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
Source: netgen
Version: 6.2.2006+really6.2.1905+dfsg-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: gitless
Version: 0.8.8-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: pixz
Version: 1.0.7-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering
Source: libbluray
Version: 1:1.3.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering
Source: libqapt
Version: 3.0.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd
Source: deepin-album
Version: 5.9.1+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: pidgin-librvp
Version: 0.9.7cvs-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]:
Source: gl-image-display
Version: 0.10-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++
Source: freeimage
Version: 3.18.0+ds2-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: ruby-jwt
Version: 2.3.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: olm
Version: 3.2.11~dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: ignition-physics
Version: 5.1.0+ds1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: posterazor
Version: 1.5.1-10
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -g
Source: tclxml
Version: 1:3.2.7-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc
Source: fis-gtm
Version: 6.3-014-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/cc
Source: casacore-data-sources
Version: 2-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: ignition-common3
Version: 3.14.0+dfsg-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: libio-async-ssl-perl
Version: 0.22-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: colmap
Version: 3.7-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -g -O2
Source: emscripten
Version: 3.1.5~dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
I'd really like to know how anyone could ever come to the conclusion
that a package that has nothing to do with graphic drivers needs to be
auto-removed.
Martin-Éric
On Thu, May 26, 2022 at 9:01 AM Debian testing autoremoval watch
wrote:
>
> upgrade-system 1.9.1.0 is marked for autoremoval from
On Thu, 26 May 2022 09:31:00 +0300
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?=
wrote:
> I'd really like to know how anyone could ever come to the conclusion
> that a package that has nothing to do with graphic drivers needs to be
> auto-removed.
>
> Martin-Éric
>
> On Thu, May 26, 2022 at 9:01 AM
Control: retitle -1 O: casparcg-server -- layered real-time video compositor to
multiple outputs)
No-one showed any interest since I asked for someone to adopt this
package, so I guess it is time to orphan it.
--
Happy hacking
Petter Reinholdtsen
Package: wnpp
Owner: Andrius Merkys
Severity: wishlist
Control: block -1 by 1011507
* Package name: prodigy
Version : 2.0.0
Upstream Author : Computational Structural Biology Group at Utrecht
University
* URL : https://github.com/haddocking/prodigy
I'd really like to know why a package that that nothing to do with
NVIDIA drivers came to be marked for auto-removal.
Martin-Éric
On Thu, May 26, 2022 at 9:04 AM Debian testing autoremoval watch
wrote:
>
> xserver-xorg-video-geode 2.11.20-9 is marked for autoremoval from testing on
>
Source: switcheroo-control
Version: 2.4-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]:
Source: libpdfbox-graphics2d-java
Version: 0.35-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: gir-to-d
Version: 0.22.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/ld:
Source: pykafka
Version: 2.7.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
>
Source: gtk-d
Version: 3.10.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: capsule-maven-nextflow
Version: 1.0.3.1+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: ruby-certificate-authority
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: lombok-ast
Version: 0.2+ds-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: opensaml
Version: 3.2.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering
hspell - yet another package which has nothing to do with nvidia or
graphics (it's a Hebrew spell checker, with no graphics...)
that got "autoremoved" because of the nvidia bug... Very strange, and I
hope somebody corrects it.
-- Forwarded message -
From: Debian testing
On 2022-05-16 22:38:44 [+0200], Jérémy Lal wrote:
> Last time so many openssl-related test failures happened,
> OPENSSL_CONF env was set to a relative path, and nodejs/openssl3
> expected an absolute path.
I don't understand why mipsel is different here. The init looks okay. I
copied the .cnf
[M. Zhou]
> Source: casparcg-server
> Version: 2.2.0+dfsg-2.1
> Severity: important
>
> tbb -> onetbb transition breaks this package due to upstream overhaul.
Thank you for the heads up.
Note, casparcg-server currently have a request for adaptation in
https://bugs.debian.org/959124 > and I am
Source: ruby-rack-oauth2
Version: 1.19.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: gmsh
Version: 4.8.4+ds2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -g -O2
Source: networking-mlnx
Version: 1:16.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]:
Source: oce
Version: 0.18.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/ld:
>
Source: ruby-ntlm
Version: 0.6.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: ignition-common
Version: 4.5.0+ds-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: python-apt
Version: 2.3.0
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> x86_64-linux-gnu-gcc
Source: kicad
Version: 6.0.5+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd
Source: apriltag
Version: 3.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/cc -g -O2
On Thursday, 26 May 2022 08:38:04 CEST Ramon Fried wrote:
> On Thu, 26 May 2022 09:31:00 +0300
> =?UTF-8?Q?Martin=2D=C3=89ric_Racine?=
> wrote:
> > I'd really like to know how anyone could ever come to the conclusion
> > that a package that has nothing to do with graphic drivers needs to be
> >
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: debian-ker...@lists.debian.org
Dear mentors,
I am looking for a sponsor for my package "open-ath9k-htc-firmware":
* Package name : open-ath9k-htc-firmware
Version : 1.4.0-106-gc583009+dfsg1-2
Upstream Author :
Package: diffutils
Version: 1:3.7-5
Upstream provides version 3.8. Do you think you could include it into
Debian for Bookworm?
Thank you very much in advance
Harri
Source: golang-github-hashicorp-go-getter
Version: 1.4.1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: codeh...@debian.org, Debian Security Team
Hi,
The following vulnerabilities were published for
golang-github-hashicorp-go-getter.
CVE-2022-26945[0]:
| HashiCorp go-getter
Source: salmon
Version: 1.6.0+ds1-1
Severity: normal
Tags: ftbfs
Hello,
tbb/onetbb transition (#1007222) is currently in the planning. During
test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-8
in experimental, current source failed to build with the following:
[ 4%]
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: buster
Severity: normal
This is an long overdue update to the clamav package. It is a stable
update provided by upstream closing CVEs bugs:
- CVE-2022-20770 (Possible infinite loop vulnerability in the CHM
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bullseye
Severity: normal
This is an long overdue update to the clamav package. It is a stable
update provided by upstream closing CVEs bugs:
- CVE-2022-20770 (Possible infinite loop vulnerability in the
Control: retitle -1 autoremoval false positive bug:
https://bugs.debian.org/1011268 -- nvidia-graphics-drivers-tesla-470:
CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191,
CVE-2022-28192
Control: block -1 with 1011268
On 26/05/2022 08.31, Martin-Éric Racine
Package: open-vm-tools
Version: 12.0.5
Severity: Serious
VMware Tools 12.0.5 is GA as of May 24, 2022.
For complete details, see:
https://github.com/vmware/open-vm-tools/releases/tag/stable-12.0.5
Release Notes are available at:
Hello,
Sorry for my late reply...
On Sat, May 06, 2017 at 11:39:56AM -0400, Theodore Ts'o wrote:
> Sorry, no. Just to be clear, is what you want is to be able to
> convert flag value to a string (instead of printing it to stdio FILE
> handle)? Or to go the other way --- e.g., given a charafter
Op wo 25 mei 2022 21:36 schreef Adam Borowski :
> And how, pray tell, may I know in advance what terminal will be used on the
> other end of the serial link? Especially if it's a box people ssh into
> from
> random places, using a plethora of various terminals on their side?
> That's the most
Control: block -1 by 1011710
This is #1011710. Anton is aware of it and in the progress of fixing
it.
--
tobi
Control: block -1 by 1011710
This is #1011710. Anton is aware of it and in the progress of fixing
it.
--
tobi
Am 26.05.22 um 06:05 schrieb xiao sheng wen(肖盛文):
Files: libs/protocol/network_protocol.h
Copyright:1995, 1996, 1997, and 1998 WIDE Project.
1982, 1986, 1993 The Regents of the University of California.
License: BSD-3-clause
Comment: The upstream distribution does not contain an
Source: gazebo
Version: 11.10.1+dfsg-2
Severity: normal
Tags: ftbfs
Hello,
tbb/onetbb transition (#1007222) is currently in the planning. During
test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-9
in experimental, current source failed to build with the following:
[ 42%]
Package: wnpp
Severity: wishlist
Owner: Osamu Aoki
X-Debbugs-Cc: debian-de...@lists.debian.org, Ethan Djeric
, Francisco Lopes
* Package name: interception-tools
Version : 0.6.8
Upstream Author : Francisco Lopes
* URL : https://gitlab.com/interception/linux/tools
*
libfreeimage3 debend tiff, now tiff api is changed,
deepin-album depend libfreeimage3, so deepin-album builded failed
reassign 1011719 src:eccodes-python
found 1011719 eccodes-python/2:1.4.2-1
affects 1011719 src:satpy
thanks
On 5/26/22 08:13, Lucas Nussbaum wrote:
/usr/lib/python3/dist-packages/eccodes/__init__.py:13: in
from .eccodes import * # noqa
and dlocate:
- Forwarded message from Debian testing autoremoval watch
-
Date: Thu, 26 May 2022 04:45:56 +
From: Debian testing autoremoval watch
To: dloc...@packages.debian.org
Subject: dlocate is marked for autoremoval from testing
dlocate 1.10 is marked for autoremoval from
Package: onionshare
Version: 2.2-3
Severity: important
Tags: patch upstream
X-Debbugs-Cc: boy...@riseup.net
Dear Maintainer,
* What led up to the situation?
In Tails 5.0, onionshare 2.2-3 is installed, Python2 is not.
>From Nautilus, I want to right-click a file and share it via OnionShare.
Package: ecmwflibs
Version: 0.4.16
Severity: normal
This package has several problems:
credits() uses a file that is not shipped with the package
versions() uses hard-coded values (at compile-time) not the Debian releases
-- System Information:
Debian Release: 11.3
APT prefers
On Wed, May 25, 2022 at 05:22:57PM +0200, David Prévot wrote:
> I noticed a difference in the file(1) output that might be a clue:
>
> $ file php-react-promise_2.*deb
> php-react-promise_2.7.0-2_all.deb: sticky Debian binary package (format 2.0),
> with control.tar.xz, data compression xz
>
i think this is about tiff pack.s bug
used tiff tiff-4.3.0-8 build ok
http://deb.debian.org/debian/pool/main/t/tiff/tiff_4.3.0-8.dsc
then use latest pbuilder sid chroot failed for tiff 4.4.0~rc1-1 api
changed
On Thu, 26 May 2022 06:26:29 + John Scott wrote:
This package was previously uploaded, but failed to clear NEW because my
introduction of a udeb wasn't fully vetted. This upload drops the udeb
so we can fix the FTBFS; perhaps it can be reintroduced later.
I think Bastian Germann has been
On Thu, 26 May 2022 at 12:39:51 +0200, Sebastian Ramacher wrote:
> interimap's autopkgtests fail with openssl 3:
I believe this is due to #1011038 and/or #1011051. AFAICT nothing needs
doing on the interimap side while these are open. Leaving -1 open
though so no one files a duplicate.
--
Dev list,
Someone apparently made a commit to the autoremoval hinter that makes
it mark packages unrelated to an RC-bug package getting marked for
autoremoval.
Could someone please look into this?
Thanks!
Martin-Éric
On Thu, May 26, 2022 at 10:38 AM Debian testing autoremoval watch
wrote:
>
Source: gdb-doc
Version: 11.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
the latest upload of gdb-doc FTBFS in a minimal buildd chroot:
[...]
checking for library containing dlopen... none required
checking whether to use expat... no
configure: WARNING: expat
Source: freesas
Version: 0.9.0-4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed that
freesas could not be built
On 2022-05-20 13:07:55 [+0200], Jérémy Lal wrote:
> nodejs dynamically links to openssl, and since openssl >= 3,
> on mipsel, some of its tests are failing, see
> https://buildd.debian.org/status/package.php?p=nodejs
>
> The failures look like openssl was configured with no-err, e.g:
>
Control: reopen -1
Control: reassign -1 dkms 3.0.3-1
Control: retitle -1 dkms: autopkgtest mixes headers from sid and testing
The following packages have unmet dependencies:
linux-headers-5.17.0-2-arm64 : Depends: linux-kbuild-5.17 (>=
5.17.6-1) but 5.17.3-1 is to be installed
Package: wnpp
Severity: wishlist
* Package name: rtl8723bt-firmware
Upstream Author : Vasily Khoruzhick
* URL : https://github.com/anarsoul/rtl8723bt-firmware
* License : binary-redist-Realtek-restrictive (non-free)
Description : Bluetooth firmware for rtl8723cs
Source: pyjwt
Version: 2.3.0-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: codeh...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for pyjwt.
CVE-2022-29217[0]:
| PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple
| different
Control: tags -1 confirmed
Le 26/05/2022 à 08:45, Lucas Nussbaum a écrit :
Source: symfony
Version: 5.4.6+dfsg-1
Severity: serious
Justification: FTBFS
Thanks Lucas! Got hit by those while preparing an upgrade. Now I know
it’s “caused” by external elements. I “just” need to find which ones
Package: lintian-brush
Version: 0.124
Severity: minor
Hello Jelmer,
Hello Lintian-Brush co-maintainers,
This is a report about to debianize hurl
( Hurl is written in Rust
Hurl, run and test HTTP requests with plain text.
https://github.com/Orange-OpenSource/hurl )
In the upstream git tree
Source: interimap
Version: 0.5.7-1
Severity: serious
Tags: sid bookworm
X-Debbugs-Cc: sramac...@debian.org
interimap's autopkgtests fail with openssl 3:
standard error:
>>> interimap 0.5.7
Error:
Hi Bastian,
Thanks for your quick reply.
在 2022/5/26 17:26, Bastian Germann 写道:
>
> Please change the last comment to say:
> struct iphdr comes from FreeBSD and is modified by the upstream author.
> The other parts of this file is written by the upstream author.
>
> Otherwise this looks
Package: cloud.debian.org
Severity: normal
X-Debbugs-Cc: a.t.chadw...@gmail.com
Dear base box maintainers:
I don’t know if this should be a documentation fix or an image fix. I’ll
just lay out the problem with as much detail as I can so that people can
search it and find better workarounds. I
Does libpam-tmpdir just sets TMPDIR to this special value or does it
somehow force all commands to use /tmp/user// ?
Does this workaround may work for you?
# TMPDIR= fai-make-nfsroot
or
# TMPDIR=/tmp fai-make-nfsroot
I'll try to avoid adding TMPDIR=/tmp into the fai code (at several
On Wed, May 25, 2022 at 01:58:58PM +0100, Rik Mills wrote:
> The issue can be worked around by adding /etc/sudoers.d/kdesu with the
> contents
>
> Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty
kdesu is cordially invited to ship that file in the package, fixing the
issue for everybody.
Package: logrotate
Version: 3.20.1-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
-- Package-specific info:
Contents of /etc/logrotate.d
total 84
-rw-r--r-- 1 root root 120 Sep 5 2019 alternatives
-rw-r--r-- 1 root root 442
Dear maintainer(s),
I worked on upgrading this package to the current debhelper compat level
(13). Attached is the corresponding patch.
I have verified the generated package is bit-for-bit identical to the
version currently in the archive.
Best regards,
ArnaudFrom
Is libb2 a dependency of coreutils (for b2sum)?
-- Forwarded message -
From: Robert Ransom
Date: Thu, May 26, 2022, 07:47
Subject: 1011146: nvidia-graphics-drivers-tesla-470 is a dependency of libb2
To:
Hi Folks,
I've tried to give packaging netavark a shot, but it seems it requires a
number of other rust modules, such as rust-iptables, to be packaged. Also,
it seems to require a number of existing packages in debian to be upgraded.
I did manage to build it with all modules vendored in, and I'm
Package: cloud.debian.org
Followup-For: Bug #1011756
X-Debbugs-Cc: a.t.chadw...@gmail.com
I should add that the debian/bullseye64 image works perfectly using the
instructions given. No need to fiddle with the SSH config while it’s
half-up.
- Andrew
Source: bidi-clojure
Version: 2.1.6-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]:
Source: allure
Version: 0.9.5.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
Source: cfgrib
Version: 0.9.10.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: cabal-debian
Version: 5.0.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules
1 - 100 of 346 matches
Mail list logo