On Wed, Feb 28, 2024 at 11:31:05AM +0100, Helmut Grohne wrote:
> Not sure what happened here exactly. The current libboinc7t64 in
> unstable version 7.24.1+dfsg-2.1 has the following it is uploaded
> debian/control file (from the dsc):
>
> | Package: libboinc7t64
> | Architecture: any
> |
Processing commands for cont...@bugs.debian.org:
> severity 1064629 serious
Bug #1064629 [libamd-comgr2] libamd-comgr2: segfault in rocfft
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1064629:
On Wed, Feb 28, 2024 at 09:38:06PM +, Luca Boccassi wrote:
> On Wed, 28 Feb 2024 at 20:15, Steve Langasek wrote:
> > On Wed, Feb 07, 2024 at 08:05:52PM +, Holger Levsen wrote:
> > > On Wed, Feb 07, 2024 at 04:25:17PM +, Luca Boccassi wrote:
> > > > Control: tags -1 -pending
> > > >
Your message dated Wed, 28 Feb 2024 23:21:56 +
with message-id
and subject line Bug#1062114: fixed in gocr 0.52-6.1
has caused the Debian Bug report #1062114,
regarding gocr: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 28 Feb 2024 23:22:48 +
with message-id
and subject line Bug#1062115: fixed in google-glog 0.6.0-2.1
has caused the Debian Bug report #1062115,
regarding google-glog: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 28 Feb 2024 23:22:58 +
with message-id
and subject line Bug#1062116: fixed in google-perftools 2.15-1.1
has caused the Debian Bug report #1062116,
regarding google-perftools: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that
Your message dated Wed, 28 Feb 2024 23:21:02 +
with message-id
and subject line Bug#1062476: fixed in gnuradio 3.10.9.2-1.1
has caused the Debian Bug report #1062476,
regarding gnuradio: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Your message dated Wed, 28 Feb 2024 23:36:36 +
with message-id
and subject line Bug#1064711: fixed in libplacebo 6.338.2-2
has caused the Debian Bug report #1064711,
regarding libplacebo: FTBFS: ld: cannot find -lexecinfo: No such file or
directory
to be marked as done.
This means that you
Source: pam
Version: 1.5.3-4
Severity: serious
Usertags: time-t
Justification: breaks buildd chroot build
Hello,
When running:
debootstrap --keyring /usr/share/keyrings/debian-archive-keyring.gpg
--include=apt,fakeroot,ca-certificates --variant=buildd --arch=amd64
--merged-usr sid
Processing control commands:
> clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Bug #1064983 [src:nvidia-graphics-drivers] nvidia-graphics-drivers:
CVE-2024-0074, CVE-2024-0075, CVE-2022-42265, CVE-2024-0078
Bug 1064983 cloned as bugs 1064984-1064991
> reassign -2 src:nvidia-graphics-drivers-legacy-340xx
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2024-0074,
Source: azure-uamqp-python
Version: 1.6.8-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for azure-uamqp-python.
CVE-2024-27099[0]:
| The uAMQP is a C library for AMQP 1.0 communication to Azure
Source: pgpool2
Version: 4.3.7-1
Severity: serious
Dear Maintainer,
armhf has -Werror=implicit-function-declaration enabled in default gcc flags of
gcc-13 13.2.0-16.1.
pgpool2 has a number of implicit function declarations causing the build
failure[1]
[1]
Control: close -1
On Wed, 28 Feb 2024 at 20:15, Steve Langasek wrote:
> On Wed, Feb 07, 2024 at 08:05:52PM +, Holger Levsen wrote:
> > On Wed, Feb 07, 2024 at 04:25:17PM +, Luca Boccassi wrote:
> > > Control: tags -1 -pending
> > > Control: close -1
> > [...]
> > > There are no mentions
Processing control commands:
> close -1
Bug #1062259 [src:libcomps] libcomps: NMU diff for 64-bit time_t transition
Marked Bug as done
--
1062259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On 2024-02-28 19:20:58 +0100, Vincent Lefevre wrote:
> Before the upgrade to gnuplot 6, everything was fine. But after
> the upgrade, I get a window where nothing is drawn, i.e. I just
> get what's *behind* the window. That's always reproducible on
> this machine.
>
> I've tried GNUTERM=wxt only.
Reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=218538
Source: libhinawa
Version: 4.0.1-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
Apologies, but it appears that somehow we failed to file a bug report sooner
about libhinawa or
Your message dated Wed, 28 Feb 2024 20:56:52 +
with message-id
and subject line Bug#1064974: fixed in alsa-lib 1.2.10-3.2
has caused the Debian Bug report #1064974,
regarding alsa-lib: Missing libasound2t64 / libasound2-udeb relation
to be marked as done.
This means that you claim that the
Your message dated Wed, 28 Feb 2024 20:57:12 +
with message-id
and subject line Bug#1064978: fixed in android-platform-frameworks-native
1:10.0.0+r36-1.2
has caused the Debian Bug report #1064978,
regarding android-platform-frameworks-native_10.0.0+r36-1.1_all-buildd.changes
REJECTED
to be
Processing commands for cont...@bugs.debian.org:
> reassign 1064824 node-d3 5.16.0+~cs5.28.10-1
Bug #1064824 [libjs-d3-tip] libjs-d3-tip: TypeError: h.map is not a function
Bug reassigned from package 'libjs-d3-tip' to 'node-d3'.
No longer marked as found in versions d3-tip.js/0.7.1-5.
Ignoring
On Wed, 28 Feb 2024 at 22:40, Steve Langasek wrote:
>
> On Wed, Feb 28, 2024 at 09:38:06PM +, Luca Boccassi wrote:
> > On Wed, 28 Feb 2024 at 20:15, Steve Langasek wrote:
> > > On Wed, Feb 07, 2024 at 08:05:52PM +, Holger Levsen wrote:
> > > > On Wed, Feb 07, 2024 at 04:25:17PM +,
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Your message dated Wed, 28 Feb 2024 23:12:58 +
with message-id
and subject line Bug#1064740: fixed in ffmpeg 7:6.1.1-2
has caused the Debian Bug report #1064740,
regarding ffmpeg: FTBFS: test.c:2:(.text.startup+0x19): undefined reference to
`closesocket'
to be marked as done.
This means
Processing control commands:
> tag -1 pending
Bug #1064740 [src:ffmpeg] ffmpeg: FTBFS: test.c:2:(.text.startup+0x19):
undefined reference to `closesocket'
Added tag(s) pending.
--
1064740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064740
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1064740 in ffmpeg 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:
(the first patch had the same number as the package I uploaded to
experimental and so got rejected. oops!)
On Thu, 29 Feb 2024 at 12:21, wrote:
> Dear maintainer,
>
> Please find attached a final version of this patch for the time_t
> transition. This patch is being uploaded to unstable.
>
>
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Hi. I'd like to get more clarity.
- You see the issue when you try to plot anything at all?
- You say "plot x" and you get a plot window, but it's all white, or
something?
- Only with the "qt" terminal?
You can try to change your window manager, qt versions, etc, etc. If no
trigger is found,
Your message dated Wed, 28 Feb 2024 23:27:20 +0100
with message-id <170915924043.14347.5710876776069057...@auryn.jones.dk>
and subject line Re: Processed: retitle 1061577 to rust-io: RUSTSEC-2020-0021:
CVE-2020-35876: use-after-free buffer access when a future is leaked
has caused the Debian Bug
Your message dated Wed, 28 Feb 2024 19:48:07 +
with message-id
and subject line Bug#1063598: fixed in python-fastparquet 2024.2.0-1
has caused the Debian Bug report #1063598,
regarding python-fastparquet: FTBFS: Python.h: No such file or directory
to be marked as done.
This means that you
Source: tdfsb
Version: 0.0.10-3
Severity: serious
Justification: policy 4.6
tdfsb's compile.sh fails to terminate with an error when one of the
invoked build commands fails. This violates Debian policy section 4.6. A
relatively simple counter measure would be adding "set -e" to the
script.
Processing commands for cont...@bugs.debian.org:
> # time_t transition started
> severity 1061888 serious
Bug #1061888 [src:anfo] anfo: NMU diff for 64-bit time_t transition
Severity set to 'serious' from 'important'
> severity 1061920 serious
Bug #1061920 [src:arrayfire] arrayfire: NMU diff for
Source: nodejs
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System
Please find attached an NMU patch for this issue, dropping
android-platform-frameworks-native-headers from this package since it is now
built at a higher version from a different source package.
On Wed, Feb 28, 2024 at 06:32:26PM +0100, Aurelien Jarno wrote:
> Source:
Dear Maintainers,
Would it be possible to consider a merge request[1] that addresses this issue?
Best Regards,
Vladimir.
[1] https://salsa.debian.org/postgresql/pgpool2/-/merge_requests/5
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Your message dated Wed, 28 Feb 2024 23:46:41 +
with message-id
and subject line Bug#1062692: fixed in libusb3380 0.0.1+git20190125.c83d1e9-2.1
has caused the Debian Bug report #1062692,
regarding libusb3380: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you
Your message dated Wed, 28 Feb 2024 23:46:33 +
with message-id
and subject line Bug#1062691: fixed in liburcu 0.14.0-3.1
has caused the Debian Bug report #1062691,
regarding liburcu: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 28 Feb 2024 23:46:50 +
with message-id
and subject line Bug#1062693: fixed in libusbgx 0.2.0-3.1
has caused the Debian Bug report #1062693,
regarding libusbgx: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 28 Feb 2024 23:47:11 +
with message-id
and subject line Bug#1062695: fixed in libvbz-hdf-plugin 1.0.2-3.1
has caused the Debian Bug report #1062695,
regarding libvbz-hdf-plugin: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that
Processing control commands:
> tag -1 pending
Bug #1064950 [src:apache2] apache2: (Legacy?) "Depends: apache2-data (=
${source:Version})," in debian/control breaks binNMU builds.
Added tag(s) pending.
--
1064950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064950
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #1064950 in apache2 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 #1064812 in barbican 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:
Processing control commands:
> tag -1 pending
Bug #1064812 [src:barbican] barbican: FTBFS: AttributeError: module
'OpenSSL.crypto' has no attribute 'load_pkcs7_data'
Added tag(s) pending.
--
1064812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064812
Debian Bug Tracking System
Contact
Processing control commands:
> severity 1039731 serious
Bug #1039731 [src:php-laravel-lumen-framework] php-laravel-lumen-framework:
FTBFS with symfony 6: unsatisfiable build-dependencies
Severity set to 'serious' from 'important'
> severity 1051989 serious
Bug #1051989 [kanboard] kanboard: FTBFS
Your message dated Wed, 28 Feb 2024 10:29:18 +
with message-id
and subject line Bug#1058138: fixed in pyeapi 1.0.2-1
has caused the Debian Bug report #1058138,
regarding pyeapi: FTBFS: ModuleNotFoundError: No module named 'imp'
to be marked as done.
This means that you claim that the problem
Processing control commands:
> reopen -1
Bug #1061984 {Done: Gianfranco Costamagna }
[libboinc7t64,libboinc-app7t64] libboinc-app7t64 and libboinc7t64 have an
undeclared file conflict
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared,
Control: reopen -1
On Tue, Jan 30, 2024 at 01:37:42PM -0800, Steve Langasek wrote:
> > libboinc-app7t64 and libboinc7t64 have an undeclared file conflict. This
> > may result in an unpack error from dpkg.
>
> Sigh. Thanks for the Cc:.
>
> That's because boinc has an idiosyncratic
Processing control commands:
> tags -1 upstream
Bug #1026587 [src:cerealizer] cerealizer: FTBFS: TypeError: __dict__ must be
set to a dictionary, not a 'NoneType'
Added tag(s) upstream.
> forwarded -1 j...@lesfleursdunormal.fr
Bug #1026587 [src:cerealizer] cerealizer: FTBFS: TypeError: __dict__
control: fixed -1 7.24.1+dfsg-3
control: close -1
thanks!
G.
OpenPGP_signature.asc
Description: OpenPGP digital signature
Processing control commands:
> fixed -1 7.24.1+dfsg-3
Bug #1061984 [libboinc7t64,libboinc-app7t64] libboinc-app7t64 and libboinc7t64
have an undeclared file conflict
There is no source info for the package 'libboinc7t64' at version
'7.24.1+dfsg-3' with architecture ''
There is no source info
Your message dated Wed, 28 Feb 2024 09:49:55 +
with message-id
and subject line Bug#1064812: fixed in barbican 1:17.0.0-3
has caused the Debian Bug report #1064812,
regarding barbican: FTBFS: AttributeError: module 'OpenSSL.crypto' has no
attribute 'load_pkcs7_data'
to be marked as done.
Processing control commands:
> severity -1 normal
Bug #1064945 [grub-efi-amd64] grub-efi-amd64: Sudden boot failures on ZFS
systems
Severity set to 'normal' from 'critical'
> tag -1 - patch
Bug #1064945 [grub-efi-amd64] grub-efi-amd64: Sudden boot failures on ZFS
systems
Removed tag(s) patch.
Control: severity -1 normal
Control: tag -1 - patch
On Tue, Feb 27, 2024 at 10:36:01PM -0600, John Goerzen wrote:
> Package: grub-efi-amd64
> Version: 2.06-13+deb12u1
> Severity: critical
> Tags: upstream patch
> Justification: breaks the whole system
>
> My system suddenly refused to start up
Control: tags -1 upstream
Control: forwarded -1 j...@lesfleursdunormal.fr
Hi Jean-Baptiste,
the Debian packaged version of cerealizer recieved a bug
report about a build failure
TypeError: __dict__ must be set to a dictionary, not a 'NoneType'
You can read the relevant part of the build
Your message dated Wed, 28 Feb 2024 12:19:54 +
with message-id
and subject line Bug#1061317: fixed in gemrb 0.9.2+dfsg-1
has caused the Debian Bug report #1061317,
regarding gemrb ftbfs with Python 3.12 as default
to be marked as done.
This means that you claim that the problem has been
Source: fontforge
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for fontforge.
CVE-2024-25081[0]:
| Splinefont in FontForge through 20230101 allows command injection
| via crafted filenames.
CVE-2024-25082[1]:
|
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Processing control commands:
> forwarded -1 https://github.com/biopython/biopython/issues/4640
Bug #1064147 [src:python-biopython] ftbfs: test failures affecting
Bio.SeqIO.SeqXmIIO
Set Bug forwarded-to-address to
'https://github.com/biopython/biopython/issues/4640'.
> tags -1 + sid
Bug #1064147
Control: forwarded -1 https://github.com/biopython/biopython/issues/4640
Control: tags -1 + sid
Control: tags -1 - testing
I'm dry on even pinpointing what change is causing Biopython
1.81 to fail those tests, maybe upstream will have a better
idea. If nothing, there remains the option to skip
Source: android-platform-frameworks-native
Version: 10.0.0+r36-1.1
Severity: serious
X-Debbugs-Cc: vor...@debian.org
On 2024-02-28 02:02, Debian FTP Masters wrote:
>
>
> Version check failed:
> Your upload included the binary package
> android-platform-frameworks-native-headers, version
Source: apt
Version: 2.7.12+nmu1
Severity: serious
While there are no upgrade issues with apt itself (according
to "apt install -s apt"), aptitude does not want to upgrade
apt automatically, while this just appears to be a package
rename:
# aptitude install apt
The following packages will be
Processing control commands:
> reassign -1 aptitude
Bug #1064969 [src:apt] apt: can't upgrade with aptitude
Bug reassigned from package 'src:apt' to 'aptitude'.
No longer marked as found in versions apt/2.7.12+nmu1.
Ignoring request to alter fixed versions of bug #1064969 to the same values
Control: reassign -1 aptitude
On Wed, Feb 28, 2024 at 03:49:12PM +0100, Vincent Lefevre wrote:
> Source: apt
> Version: 2.7.12+nmu1
> Severity: serious
>
> While there are no upgrade issues with apt itself (according
> to "apt install -s apt"), aptitude does not want to upgrade
> apt
Processing control commands:
> tag -1 pending
Bug #1064689 [src:objgraph] objgraph: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.
--
1064689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064689
Control: tag -1 pending
Hello,
Bug #1064689 in objgraph 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:
Your message dated Wed, 28 Feb 2024 15:49:35 +
with message-id
and subject line Bug#1064689: fixed in objgraph 3.6.1-1
has caused the Debian Bug report #1064689,
regarding objgraph: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.12 3.11" returned exit code
On 2024-02-28 15:56:56 +0100, Julian Andres Klode wrote:
> aptitude is not our chosen tool for distribution upgrades, as such
> failures there are not release critical for the packages. So while
> this is release critical for aptitude, it's a wishlist bug for apt
> that probably would end up being
Processing commands for cont...@bugs.debian.org:
> found 1064969 0.8.13-5
Bug #1064969 [aptitude] apt: can't upgrade with aptitude
Marked as found in versions aptitude/0.8.13-5.
> retitle 1064969 aptitude: can't upgrade apt due to rename of library package
Bug #1064969 [aptitude] apt: can't
Your message dated Wed, 28 Feb 2024 13:19:46 +
with message-id
and subject line Bug#1061604: fixed in cctbx 2023.12+ds2+~3.17.0+ds1-4
has caused the Debian Bug report #1061604,
regarding cctbx: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been
Source: alsa-lib
Version: 1.2.10-3.1
Severity: serious
Tags: d-i a11y
Justification: makes brltty FTBFS
User: debian-...@lists.debian.org
Usertags: time-t
Hello,
The t64 change apparently missed adding a relation between the
libasound2t64 deb and the libasound2-udeb udeb libraries, to that
Processing control commands:
> severity -1 normal
Bug #1064969 [aptitude] aptitude: can't upgrade apt due to rename of library
package
Severity set to 'normal' from 'serious'
--
1064969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064969
Debian Bug Tracking System
Contact
Control: severity -1 normal
On 2024-02-28 15:49 +0100, Vincent Lefevre wrote:
> Source: apt
> Version: 2.7.12+nmu1
> Severity: serious
>
> While there are no upgrade issues with apt itself (according
> to "apt install -s apt"), aptitude does not want to upgrade
> apt automatically, while this
Hi Yavor,
On Wed, 20 Dec 2023 21:18:20 +0200 Yavor Doganov wrote:
Please find attached a patch; build-tested only (although the
package's own testsuite has some checks which test this
functionality).
Thanks for the patch, I uploaded it to Debian and so far noone
complained ;-)
But the
Processing commands for cont...@bugs.debian.org:
> tags 1064966 + upstream
Bug #1064966 [src:apache-mime4j] apache-mime4j: CVE-2024-21742
Added tag(s) upstream.
> forwarded 1064966 https://github.com/apache/james-mime4j/pull/91
Bug #1064966 [src:apache-mime4j] apache-mime4j: CVE-2024-21742
Set
Your message dated Wed, 28 Feb 2024 17:44:28 +
with message-id
and subject line Bug#1058435: fixed in orsopy 1.2.0-1
has caused the Debian Bug report #1058435,
regarding orsopy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.12 3.11" returned exit code 13
Source: lvm2
Version: 2.03.22-1
Severity: serious
Hi,
filing this issue with severity RC to prevent testing migration.
It appears the new LVM release breaks both systemd and multipath-tools's
autopkgtest suite
https://ci.debian.net/packages/m/multipath-tools/testing/amd64/43382441/
Hello,
I think this package should be removed from Debian.
In addition to the FTBFS issues:
- Project appears to be abandoned upstream, last commit was 6 years ago
- The future of Vagrant in Debian is in serious doubt (see #104)
- It's currently blocking the transition of the latest
Your message dated Wed, 28 Feb 2024 18:05:38 +
with message-id
and subject line Bug#1064750: fixed in bornagain 21.1+ds3-3
has caused the Debian Bug report #1064750,
regarding bornagain: FTBFS: make[1]: *** [debian/rules:41:
override_dh_auto_configure] Error 2
to be marked as done.
This
Your message dated Wed, 28 Feb 2024 18:14:23 +
with message-id
and subject line Bug#1062096: fixed in colpack 1.0.10-7.1
has caused the Debian Bug report #1062096,
regarding colpack: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Package: gnuplot-qt
Version: 6.0.0+dfsg1-1
Severity: grave
Justification: renders package unusable
Before the upgrade to gnuplot 6, everything was fine. But after
the upgrade, I get a window where nothing is drawn, i.e. I just
get what's *behind* the window. That's always reproducible on
this
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Your message dated Wed, 28 Feb 2024 23:49:58 +
with message-id
and subject line Bug#1063152: fixed in mumps 5.6.2-2.1
has caused the Debian Bug report #1063152,
regarding mumps: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 28 Feb 2024 23:52:56 +
with message-id
and subject line Bug#1063163: fixed in ncl 6.6.2.dfsg.1-4.1
has caused the Debian Bug report #1063163,
regarding ncl: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 28 Feb 2024 23:51:34 +
with message-id
and subject line Bug#1063160: fixed in ncap 1.9.2-8.1
has caused the Debian Bug report #1063160,
regarding ncap: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 29 Feb 2024 00:25:02 +
with message-id
and subject line Bug#1053111: fixed in e2fsprogs 1.47.0-2.2
has caused the Debian Bug report #1053111,
regarding e2fsprogs FTBFS when systemd.pc changes systemdsystemunitdir
to be marked as done.
This means that you claim that
Your message dated Thu, 29 Feb 2024 00:25:12 +
with message-id
and subject line Bug#1062525: fixed in eegdev 0.2-8.1
has caused the Debian Bug report #1062525,
regarding eegdev: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 29 Feb 2024 00:33:55 +
with message-id
and subject line Bug#1062121: fixed in gr-air-modes 0.0.20210211-3.1
has caused the Debian Bug report #1062121,
regarding gr-air-modes: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that
Your message dated Thu, 29 Feb 2024 00:33:33 +
with message-id
and subject line Bug#1062118: fixed in gpaste 44.1-2.1
has caused the Debian Bug report #1062118,
regarding gpaste: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 29 Feb 2024 01:14:21 +
with message-id
and subject line Bug#1063049: fixed in visp 3.6.0-2.1
has caused the Debian Bug report #1063049,
regarding visp: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
On Wed, Feb 28, 2024 at 05:10:37PM -0800, Steve Langasek wrote:
> > If you then run vnlog_fields_generated.h (which, again, #includes
> > vnlog.h) through abi-compliance-checker, you'll see that it passes.
> > vnl-gen-header doesn't support any time-related types, so this is y2k38
> > safe.
> If
Source: nut
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System
Your message dated Thu, 29 Feb 2024 01:51:32 +
with message-id
and subject line Bug#1062131: fixed in groonga 13.1.1+dfsg-1.1
has caused the Debian Bug report #1062131,
regarding groonga: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 29 Feb 2024 01:51:41 +
with message-id
and subject line Bug#1062132: fixed in group-service 1.4.0-2.1
has caused the Debian Bug report #1062132,
regarding group-service: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the
1 - 100 of 337 matches
Mail list logo
