On 4 April 2024 02:52:29 CEST, David Landry wrote:
>Good evening,
>
>The bug involving compiling/installing nvidia-kernel-dkms is still present.
>The result of the bug is that following a reboot after the erroneous
>installation noted below, my display drivers get completely disabled,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: severity -1 important
On Tue, 2024-03-26 at 12:25 +0100, Matthias Klose wrote:
> Package: src:ifuse
> Version: 1.1.4~git20181007.3b00243-1
> Severity: serious
> Tags: sid trixie ftbfs patch
>
> ifuse ftbfs from source, not finding the
FYI, this only seems to affect the description for the -S switch in the
man-page; The files section at the bottom is fine.
On 2024-04-04 00:14:27 [+0200], Guillem Jover wrote:
> Hi!
Hi,
> I initially was thinking that a conditionally triggered activation
> when upgrading from the affected versions would be sufficient, but if
> people have already upgraded, then that will still leave them with the
> malicious stuff in
package release.debian.org
tags 1068084 = bookworm pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian bookworm.
Thanks for your contribution!
Upload details
==
Package: intel-microcode
Version:
On 04/04/24 21:36, Salvatore Bonaccorso wrote:
> Source: nghttp2
> Version: 1.60.0-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
>
> Hi,
>
> The following vulnerability was published for nghttp2.
>
>
Package: reapr
Version: 1.0.18+dfsg-5
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, reapr
depends on both libtabixpp0 and libtabixpp0t64. As a
result it is uninstallable on architectures that are undergoing
the
Package: riseup-vpn
Version: 0.21.11+ds1-5
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, riseup-vpn
depends on both libqt5widgets5 and libqt5widgets5t64. As a
result it is uninstallable on architectures that are
On Thu, Apr 04, 2024 at 07:14:48PM +0100, Alex Constantino wrote:
> This reverts commit 5a838e5d5825c85556011478abde708251cc0776.
>
> Changes from commit 5a838e5d5825 ("drm/qxl: simplify qxl_fence_wait") would
> result in a '[TTM] Buffer eviction failed' exception whenever it reached a
> timeout.
On Do 04 Apr 2024 17:53:07 CEST, Peter Green wrote:
Package: lomiri-system-settings
Version: 1.1.0-2
Severity: grave
lomiri-system-settings depends on
lomiri-system-settings-security-privacy, which
is not availble on armel, armhf or mips64el.
The reason, or at least one reason, it is not
Hi,
Quoting Santiago Vila (2024-04-04 20:03:08)
> El 4/4/24 a las 19:29, Johannes Schauer Marin Rodrigues escribió:
> > Also I'm curious: what is your motivation for using unshare mode if you are
> > creating your chroots using superuser privileges?
> >
> > And are you really storing your chroots
Hi Cris,
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.
And now I can't have pglistener on testing.
Best regards,
On Sat, 09 Dec 2023
Package: pkgconf
Version: 1.8.1-1
Severity: normal
X-Debbugs-Cc: earl_c...@yahoo.com
Dear Maintainer,
In Debian bullseye, pkgconf would deduplicate -L options:
# foo.pc
libdir=/opt/lib
Name: foo
Description: The foo library
Version: 1.0.0
Requires.private: bar
Libs:
Hi,
in static-pie, relocations get processed in _start, before main() is
called. In musl, this is done by linking with rcrt1.o as start file
instead of crt1.o. And that file processes all relative relocations. You
can check with readelf -r what the relocation types are. If they are not
relative,
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "dpkg-dev-el":
* Package name : dpkg-dev-el
Version : 37.12
Upstream contact : Debian Emacsen Team
* URL : [fill in URL of upstream's web site]
* License
Package: pyode
Version: 1.2.0.dev15-4
Severity: grave
Tags: patch
Justification: renders package unusable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: bdr...@debian.org
Dear Maintainer,
the python3-pyode package is empty, because it silently fails
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
pypy3 needs rebuilding for the time64 transition (it currently depends on
libssl3).
nmu pypy3_7.3.15+dfsg-1 . ANY . unstable . -m "rebuild for time64"
-- System Information:
Debian
Galera patch releases have been accepted as stable updates before. That is
also what users expect.
Thanks for reminding about this though, I yad forgotten about it. Will do
it next weekend.
Package: libqt5-ukui-style1
Version: 1.0.8-1
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, libqt5-ukui-style1
depends on both libqt5widgets5 and libqt5widgets5. As a
result it is uninstallable on architectures
On Thu, Apr 04, 2024 at 01:22:19PM -0700, Russ Allbery wrote:
> I'm not sure what I think about that. We have a general escape hatch
> already for non-free packages in Policy 2.2.3 that says they may not fully
> comply with Policy, which may be sufficient.
But precisely, we _do_ want non-free
Package: steam-installer
Version: 1:1.0.0.75+ds-6
Severity: minor
X-Debbugs-Cc: jared...@pm.me
Dear Maintainer,
I just removed steam with "apt purge steam-installer". In the process it warned
me that ~/.steam would not be removed and I should remove it manually (I did).
But I also noticed
I forgot to mention the exact GRUB versions:
- My Debian 10.13 Netinst based installer had GRUB: 2.06-3~deb10u1
- My Debian 10 based installed system had GRUB: 2.06-3~deb10u4
- My Debian 11.9 Netinst based installer had GRUB: 2.06-3~deb11u6
- My Debian 11 based installed system had GRUB:
Sometimes, it does not crash with a smashed stack but instead:
Setting up sasl2-bin (2.1.28+dfsg1-6+b1) ...
BDB0002 __fop_file_setup: Retry limit (100) exceeded
saslpasswd2: generic failure
dpkg: error processing package sasl2-bin (--configure):
installed sasl2-bin package post-installation
This problem continues to occur with curl 7.74.0 on Debian GNU/Linux
11 (bullseye) on WSL:
curl 7.74.0 (x86_64-pc-linux-gnu) libcurl/7.74.0 OpenSSL/1.1.1w
zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.3.0)
libssh2/1.9.0 nghttp2/1.43.0 librtmp/2.3
Release-Date: 2020-12-09,
Hi,
I don’t think a /etc/cron.yearly/ should be created as directory,
given that the default /etc/crontab never executes anything in it
even if anacron may do.
bye,
//mirabilos
--
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich blutverschmiert… wer
eribe...@debian.org, Matthias Geiger
Bcc:
Subject: Re: false positive NONVERBOSE BUILD for rust code in Python modules
Reply-To:
Hi,
I am having similar issue in another package 'python-cotengrust' [0].
The link for buildlog [1].
[0]
El 23/12/23 a las 3:07, Otto Kekäläinen escribió:
Sure, this will be fixed (automatically) with uploading latest upstream minor
release as stable update, and I intend to do it in coming 1-2 weeks.
Hi. Can you elaborate on that? Release managers do not usually allow
new upstream releases in
Control: retitle -1 src:r-cran-rstanarm: FTBFS on mips64el and risc64
Control: reopen -1
Control: tags -1 upstream
Control: forwarded -1 https://github.com/stan-dev/rstanarm/issues/619
thanks
As per autobuilders log[1] the package fails to build on mips64el and risc64
with
...
g++ -std=gnu++17
Hi!
On Thu, 2024-04-04 at 23:13:03 +0200, Sebastian Andrzej Siewior wrote:
> On 2024-04-04 00:14:27 [+0200], Guillem Jover wrote:
> > I initially was thinking that a conditionally triggered activation
> > when upgrading from the affected versions would be sufficient, but if
> > people have
On Wed 2024-04-03 13:03:19 +0800, Sean Whitton wrote:
> Thanks, but can you sign this off? Ty!
Sure, attached. Let me know if you need anything different.
--dkg
From b522c1cc6201f75ab6103954016bbb719d4dd2fa Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Tue, 30 Jan 2024
On Tue, Mar 26, 2024 at 12:39:23PM +0100, Lorenzo wrote:
> Hi Matija,
>
> could you please test the attached refreshed script and report if it
> works as expected for your use case?
Thanks!
I can confirm that attached /etc/init.d/pdns-recursor seems to work
just fine on my SysV based Debian
Suggested init.d script to orphan-sysvinit-scripts package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065133
--
Opinions above are GNU-copylefted.
Hi,
Quoting Santiago Vila (2024-04-04 20:35:47)
> El 4/4/24 a las 19:44, Johannes Schauer Marin Rodrigues escribió:
> > instead of doing that, you could've worked around this by just placing the
> > build log into a dedicated temporary directory and then copying it to where
> > you
> > want it
Hi Andreas,
after routine-update dh_missing failed due to compat level 13 which
defaults to fail if some files are not installed.
Yep, encountered that in other places as well when updating a few (old!)
things.
This made me aware that upstream in principle installs a test suite
we could use
On Thu, Apr 04, 2024 at 07:50:40PM +, Thorsten Glaser wrote:
> Szabolcs Nagy dixit:
>
> >the next culprit is gcc (each target can have their own
>
> gcc-13_13.2.0-23
>
> >static pie specs) or the way you invoked gcc (not visible
>
> As I wrote earlier, though with more flags. Dropping all
David Bremner writes:
> Xiyue Deng writes:
>
>>
>> Will re-evaluate if XEmacs compatibility would be dropped.
>>
>> [1]
>> https://salsa.debian.org/emacsen-team/dpkg-dev-el/-/commit/132669ed6d6ee19a440234b943625da9cd6e2d9b
>>
>
> Does the package currently work (somehow?) with XEmacs? At least
Rich Felker dixit:
>I seem to recall the musl-gcc wrapper does not handle static-pie
>right.
Hmm. Inhowfar? And it does seem to work fine on the other
architectures.
>A real cross toolchain should.
I fear that that’s out of question for Debian.
I’ve got a github action test setup for mksh
Sebastian Andrzej Siewior dixit:
>the older "previous" kernel has it.
And that won’t be fixed even with a trigger.
Used to be -uk all would, but (#1065698) that doesn’t work any more.
Given how widespread the info already is and that it affects sid and
a subset of trixie users, maybe go with
Unfortunately, this applies to unstable now too, and did apply to
trixie until it resulted in autoremoval of the package. Would it
help if I were to backport the fix from upstream? Or is the plan to
just wait? (I can always build my own local package from upstream
source, but this doesn't really
Ah. That makes sense. Thanks, Christian!
On 2024-04-04 04:30, Christian Kastner wrote:
I just rebuilt rocfft to 6.0.2 but the issue is still present. But that
was naive, there are other < 6.0 components in the stack that could
affect this.
The problem appeared in rocfft 5.5.1 when rocm-hipamd
Control: tags -1 + patch
On 04.04.2024 21:57, Peter Green wrote:
Hi,
After being rebuilt for the time64 transition, perdition
depends on both libvanessa-socket2 and libvanessa-socket2.
As a result it is uninstallable.
Interesting in this case, the uninstallability seems to apply to all
Package: kanshi
Version: 1.5.1-2
Severity: normal
X-Debbugs-Cc: Daniel Kahn Gillmor
I'm using sway 1.9-1 with kanshi. When i plug in an external monitor,
kanshi matches it appropriately against my configuration, and it
configures the monitor appropriately.
However, when i do `swaymsg reload`,
Dixi quod…
>Hmm, actually… I could… test whether that one fixes static-pie
>on zelenka. Or at least the same approach. I’ll get back with
>report from that.
Having looked at the spec file, the only extra things the stock
specs do that the overriding specs don’t is:
*link:
[…]
Control: reassign -1 lomiri-system-settings-security-privacy
Control: found -1 1.0.2-2
On Do 04 Apr 2024 17:53:07 CEST, Peter Green wrote:
Package: lomiri-system-settings
Version: 1.1.0-2
Severity: grave
lomiri-system-settings depends on
lomiri-system-settings-security-privacy, which
is
Package: python3-dask
Version: 2023.12.1+dfsg-2
Severity: serious
Control: affects -1 src:pandas
Control: block 1068104 by -1
Importing dask.dataframe currently fails with the error
TypeError: descriptor '__call__' for 'type' objects doesn't apply to a
'property' object
amd64
Package: populations
Version: 1.2.33+svn0120106+dfsg-6
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition,
populations still depends on libqt5xml5,
rather than libqt5xml5t64. As a result it is uninstallable on
Package: pflogsumm
Version: 1.1.5-8
Severity: important
Tags: patch
X-Debbugs-Cc: st...@hkust.se
Dear Maintainer,
Pflogsumm reports zero mails on day 1-9 of every month
Stock debian postfix version
Patch:
--- /usr/sbin/pflogsumm.orig2024-04-05 00:45:38.214914066 +0200
+++
Dixi quod…
>Now I (or someone) is going to have to reduce that to a testcase, so
No success with that, unfortunately.
>But this does seem to be a toolchain bug: adding -static-pie to the
>glibc dynamic-pie link command and…
>
>(gdb) print initcoms
>$1 = {0xda494 "typeset", 0x0, 0x0, 0x0,
Package: rakarrack
Version: 0.6.1-8
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, rakarrack
depends on both libasound2 and libasound2t64. As a
result it is uninstallable on architectures that are undergoing
the
Package: wnpp
Severity: wishlist
Owner: Yogeswaran Umasankar
X-Debbugs-Cc: debian-de...@lists.debian.org, kd8...@gmail.com
* Package name: python-asv-runner
Version : 0.2.1
Upstream Contact: Rohit Goswami , Michael Droettboom
* URL :
Am Fri, Apr 05, 2024 at 05:04:37AM + schrieb Thorsten Glaser:
> Should be correct:
>
> /usr/libexec/gcc/s390x-linux-gnu/13/collect2 -fno-lto -dynamic-linker
> /lib/ld-musl-s390x.so.1 -nostdlib -static -static -pie --no-dynamic-linker -o
> mksh /usr/lib/s390x-linux-musl/rcrt1.o
Markus Wichmann dixit:
>can check with readelf -r what the relocation types are. If they are not
>relative, they will not be processed.
Gotcha! They are all R_390_RELATIVE except for:
00045ff0 00110016 R_390_64 00042c58 u_ops + 70
00045ff8 00110016 R_390_64
Hi Sascha,
Am Thu, Apr 04, 2024 at 10:33:16PM +0200 schrieb Sascha Steinbiss:
> Interesting to see that there is no ltrsift-examples package indeed. But
> I must have had my reasons back then...
>
> Anyway, to be honest I don't see much long-term future for LTRsift. I am
> actually surprised to
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
libsoup2.4.1 was renamed to libsoup-2.4.1 for the time64 transition.
It seems that the new version of libgrss was built a bit too early and, on most
architectures, picked up a dependency on
Package: gir1.2-keybinder-0.0
Version: 0.3.1-2.3
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
libkeybinder0 has been renamed to libkeybinder0t64, however gir1.2keybinder0.0
still depends on the former on most architectures. As a result it is
uninstallable on architectures
user release.debian.org
usertag 1064533 time-t-downgrade
severity 1064533 important
Hi
On 04-04-2024 4:25 a.m., handsome_feng wrote:
If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.
The excuses shows
Hi Thomas
On 2024-04-03 08:09:59 +0200, Thomas Orgis wrote:
> Hi again,
>
> (after Easter hiatus … or rather xz backdoor meltdown?)
>
> I had a stab at this, detecting a system that forces 64 bit offsets on
> a 32 bit base in configure. This is to ensure that you do not encounter
> the same
Package: gpa
Version: 0.10.0-5
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, gpa depends
on both libgpgme11 and libgpg11t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf
Source: util-linux
Version: 2.40-1
Severity: important
Tags: upstream
X-Debbugs-Cc: debian-m...@lists.debian.org
Control: forwarded -1 https://github.com/util-linux/util-linux/issues/2867
Apparently on mips64el we have a kernel issue that make
mkfds-multiplexing-{pselect6,poll,ppoll} fail.
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: team+pyt...@tracker.debian.org
* Package name: python-chainstream
Version : 1.0.1
Upstream Contact: Reuben Thomas
* URL : https://github.com/rrthomas/chainstream
* License : CC-BY-SA-4.0
Programming Lang: Python
Source: python-oslo.messaging
Version: 14.7.0-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: hostname
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed that
On Sat, Feb 24, 2024 at 09:59:48AM +0100, Sebastian Ramacher wrote:
> Source: faketime
> Version: 0.9.10-2.1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
>
>
Control: tags -1 pending
FYI an implementation is committed[1] and will be shipped with the next release.
[1]
https://salsa.debian.org/emacsen-team/dpkg-dev-el/-/commit/7f438a42f33f31b86ec2e36bc2cc303cd1d298c6
--
Xiyue Deng
Control: tags -1 patch
Package: samba
Version: 2:4.17.12+dfsg-0+deb12u1
Severity: wishlist
X-Debbugs-Cc: hibbsncc1...@gmail.com
Dear Maintainer,
I noticed that the group policy tool (/usr/sbin/samba-gpupdate) in Debian is
stored in the samba package. This seems to be a poor choice of placement as
group policies are
Hi!
Glad at least someone starts to talk about it. Thank you J MO for this.
Normally the SYSOPs will just purge the official package and start to
package themselves silently, however, Debian shouldn't work this way, it
will be usable for novices and the attack of surface will become larger
Source: autopkgtest
Version: 5.33
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it recently started to fail a lot on ppc64el. The failures seem
related to the host that runs the
Package: elpa-dpkg-dev-el
Version: 37.11
Severity: minor
We have attempted to fix most comp warnings in [1]. However, there are
XEmacs compatible code that still causes some comp warnings, so using
this bug to track this. The current list of warnings are as the
following:
,
| ■ Warning
Package: indi-apogee
Version: 0.10.0-5
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, indi-apogee depends
on both libapogee3 and libapogee3t64. As a
result it is uninstallable on architectures that are undergoing
the time64
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: lib...@packages.debian.org
Control: affects -1 + src:libzia
User: ftp.debian@packages.debian.org
Usertags: remove
Hi,
I had somehow assumed that #1064844 would result in the removal of
libzia from both unstable and experimental, but of
Package: pkgconf
Version: 1.8.1-1
Severity: normal
X-Debbugs-Cc: earl_c...@yahoo.com
Dear Maintainer,
Starting in Debian bookworm, the output of pkgconf includes a trailing
whitespace which might affect programs consuming its output:
$ pkgconf --libs glib-2.0 | od -bc
000 055 154 147 154
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission
Submission-Type: new
Site: mirror.neftm.ru
Archive-architecture: amd64
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: https://neftm.ru
Country: RU Russian Federation
Location: Moscow
On Thu, Apr 04, 2024 at 05:54:51AM +0200, Salvatore Bonaccorso wrote:
> Hi Marco,
>
> [CC'ing security team]
>
> On Mon, Apr 01, 2024 at 04:25:05PM +0200, Marco d'Itri wrote:
> > Control: found -1 5.0.0-1
> > Control: fixed -1 7.4.2
> >
> > On Nov 17, Salvatore Bonaccorso wrote:
> >
> > >
On 2024-04-02 00:35, Cordell Bloor wrote:
> I tried to reproduce the rocfft callback bug with a W6800 (gfx1030). I
> used a Debian Unstable docker container on an Ubuntu Noble host, but the
> tests all passed. This made me realize that the test failure pattern on
> the CI is that all the
Control: tags -1 patch
Control: severity -1 serious
(probably makes nbconvert/nbsphinx unusable)
xml-html-clean is in
NEWhttps://ftp-master.debian.org/new/lxml-html-clean_0.1.0-1.html
Thanks - that and adding it to the Depends of python3-nbconvert should
fix this bug.
From codesearch,
On 3/25/24 7:17 PM, Julian Gilbey wrote:
So this is a plea for anyone looking for something really helpful to
do: it would be great to have a group of developers finally package
this! There was some initial work done (see the RFP bug report for
details:
Control: tags -1 confirmed
Hi,
On 03-04-2024 10:31 p.m., Andres Salomon wrote:
I'd like to go ahead and upload
123.0.6312.105-1~deb13u1 to trixie.
I have $(reschedule --days=0)-ed your upload to DELAYED. I'll do a final
check when that lands before unblocking.
Thanks for you patience.
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: u...@packages.debian.org
Control: affects -1 + src:uif
Please accept a minor fix for the uif firewall script. With this
change, uif now also supports VLAN ethX.Y
On Wed, 03 Apr 2024 16:58:35 +0200 Detlev Zundel wrote:
> With the latest gnome-terminal, this long-running process gets stopped when
> the
> terminal is not visible.
>
> ii libvte-2.91-0 0.75.91-2
This bug sounds the same as upstream report
Control: tags 620185 + pending
FYI a potential fix is applied[1] and will be shipped with the next
release.
[1]
https://salsa.debian.org/emacsen-team/dpkg-dev-el/-/commit/d9cb4cce57d2c887bdb9e74c97b0f8951cbd8b1b
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "badwolf":
* Package name : badwolf
Version : 1.3.0-1
Upstream contact : Haelwenn (lanodan) Monnier
* URL : https://hacktivis.me/projects/badwolf/
* License : BSD-3-clause
* Vcs :
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
It seems that the new version of gyoto was built a bit too early and, on most
architectures, picked up a dependency on libcfitsio10 rather than
libcfitsio10t64.
nmu gyoto_2.0.2-1.1 . ANY .
Package: squashfuse
Version: 0.5.2-0.1
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for squashfuse (versioned as 0.5.2-0.2) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru
Am 04.04.24 um 07:21 schrieb Julian Gilbey:
Hi Michael,
Ah, you've probably just solved my problem - thank you! I had no idea
that there was another network management tool involved. A quick look
suggests that it's ifupdown, so I'll try removing that and see what
happens.
Don't forget to
On Apr 04, Salvatore Bonaccorso wrote:
> While I do agree (and it was filled with this severity), the bug
> severity would not be RC, varnish currently seem to lack active
> maintainership.
Not anymore: https://salsa.debian.org/md/varnish/ .
--
ciao,
Marco
signature.asc
Description: PGP
Source: grokevt
Version: 0.5.0-5
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed that
grokevt could not be built
Source: ttconv
Version: 1.0.8-1
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
ttconv could not be built
Source: ludevit
Version: 9.2-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed that
ludevit could not be built
Package: autopkgtest
Version: 5.34
Severity: normal
I tried to run with the new --lxcpath option but it fails:
"""
admin@ci-worker01:~$ /usr/bin/autopkgtest debputy -- lxc --sudo
autopkgtest-testing-i386 --lxcpath=/tmp -ddd
autopkgtest [10:00:08]: starting date and time: 2024-04-04
On Wed, Mar 01, 2023 at 08:30:12AM +0100, Jakub Wilk wrote:
> Package: faketime
> Version: 0.9.10-2.1
> Severity: grave
>
> faketime no longer works on i386:
>
>$ faketime -f '2008-12-24 08:15:42' date -R
>Wed, 01 Mar 2023 08:25:58 +0100
The reason here is that date uses
Package: openapi-specification
Version: 3.1.0-1
Severity: normal
Hi!
Would it be possible to include the OpenAPI-Specification examples in
the Debian package? (Adding debian/examples with the single line:
examples/*
would do it.) They're used in the test suite of a package I'm trying
to
Package: ftp.debian.org
Please remove python3.10, superseded by 3.11 and 3.12.
Source: coda
Version: 2.25.2-1
Severity: serious
Tags: upstream ftbfs patch
Justification: makes the package in question unusable or mostly so
User: debian-...@lists.debian.org
Usertags: hdf-4.3
Dear Maintainer,
Your package FTBFS while performing test rebuilds with HDF 4.3.20.
The attached
See:
https://salsa.debian.org/televic-team/tcnopen
--
g. Marc
GPG: 827C FD74 BA46 8152 A041 F3A0 7A6A 4F17 5995 A65B
On 29/03/2024 00:06, Adrian Bunk wrote:
Hi,
attached are proposed debdiffs for updating gtkwave to 3.3.118 in
{bookworm,bullseye,buster}-security for review for a DSA
(and as preview for buster).
General notes:
As suggested by the security team in #1060407, this is a backport of a
new
Package: xdm
Version: 1:1.1.11-3+b2
Severity: normal
X-Debbugs-Cc: none, Łukasz Stelmach
Dear Maintainer,
pam_keyinit is missing from the /etc/pam.d/xdm configuration
file. Therefore, it is not possible to access the session keyring from
programs running in a session started by xdm.
The patch
This commit replicates commits[1][2] from the openssh package.
Closes
[1]
https://salsa.debian.org/ssh-team/openssh/-/commit/ca7f6f719ad5f168b25165caaff658f21c784c4e
[2]
https://salsa.debian.org/ssh-team/openssh/-/commit/dc461e571bcc56f8d95e83c731007636d8e79da5
Closes: #1068378
---
Control: tags -1 pending
FYI a fix is applied[1] and will be shipped with the next release. Note
that there are still some code that are retained for potential XEmacs
compatibility, which will be tracked in Bug#1068370[2].
[1]
Control: tags -1 pending
FYI a fix is applied[1] and will be shipped with the next release. Note
that there are still some code that are retained for potential XEmacs
compatibility, which will be tracked in Bug#1068370[2].
[1]
Control: tags -1 pending
FYI the DEP-5 headers in copyright files are implemented[1] and will be
shipped in the next version.
The DEP-3 part still needs to be done but may be more involved as it
should work with diff mode. Please feel free to file a separate
tracking bug for this.
[1]
1 - 100 of 198 matches
Mail list logo
