Package: nvidia-graphics-drivers
Version: 530.41.03-3
Hi,
I follow the discussion of "nvidia-graphics-drivers: please package
systemd power management scripts" [1] and
* Install new package nvidia-suspend-common: So, there are the systemd
unit files and "nvidia-sleep.sh"
* Set
On Thu, Nov 30, 2023 at 11:06:56PM +0100, Markus Koschany wrote:
> Source: libitext5-java
> Version: 5.5.13.3-2
> Severity: serious
> Tags: ftbfs sid
> User: a...@debian.org
> Usertags: bouncycastle-1.77
There are PDF signature and encryption test cases running as part of the
build, and I did
Control: tags -1 + patch
On 12/12/23 09:59, Yadd wrote:
Package: node-eslint-plugin-eslint-plugin
Version: 2.3.0+~0.3.0-4
Severity: serious
Tags: ftbfs
Justification: ftbfs
Hi,
when trying to reproduce node-eslint-plugin-eslint-plugin build, sbuild
fails. Below relevant logs:
eslint --format
On Thu, 2023-11-30 at 08:33 +0100, Patrick ZAJDA wrote:
> I am looking for a sponsor for my package "harmony":
Apologies for the delay.
Once these two issues are fixed I will sponsor the package:
> * Suppress Lintian warning about man page
It is incorrect to suppress valid lintian warnings,
Package: node-eslint-plugin-eslint-plugin
Version: 2.3.0+~0.3.0-3
Severity: important
Tags: ftbfs patch upstream
X-Debbugs-Cc: y...@debian.org
Hi,
here is a patch that updates AJV schemas. It is compatible with current
node-ajv 6 and node-ajv >= 8
Cheers,
Yadd
diff --git a/debian/changelog
Source: tar
Version: 1.34+dfsg-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for tar.
CVE-2023-39804[0]:
| Incorrectly handled extension attributes in PAX archives can lead to
| a crash
If you
Package: node-eslint-plugin-eslint-plugin
Version: 2.3.0+~0.3.0-4
Severity: serious
Tags: ftbfs
Justification: ftbfs
Hi,
when trying to reproduce node-eslint-plugin-eslint-plugin build, sbuild
fails. Below relevant logs:
eslint --format tap Xcomposer
TAP version 13
1..2
ok 1 -
Source: portalocker
Version: 2.2.1-1
Severity: normal
Tags: upstream
Forwarded: https://github.com/wolph/portalocker/issues/92
X-Debbugs-Cc: car...@debian.org,ald...@ee.ethz.ch
Hi
Locking on NFS mount does not work with portalocker, as a simple
reproducer:
, [ test-lock.py ]
| import
the fix was pushed with the latest point release
On 04/12/2023 01:14, mike wrote:
Package: mate-panel
Version: 1.27.0-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: okgomdjgbm...@gmail.com
Dear Maintainer,
like the title says.
It would be nice to backport the fix.
-- System Information:
* Helmut Grohne [2023-06-28 20:40]:
> $ printf "bucket X\n/11/11 c\n Y 1\n" | ledger -f - print
> /11/11 c
> Y 1
Alexis pointed out that this is the same as
https://github.com/ledger/ledger/issues/604
Note that there are a lot of bugs
Package: openjdk-17-jdk
Version: 17.0.9+9-2
Followup-For: Bug #1058076
X-Debbugs-Cc: pleat_00_quo...@icloud.com
Dear Maintainer,
Is there some way I can edit the original report? The file I attatched
accidentally leaked a bunch a private info in the java command line even though
I modified the
Salvatore Bonaccorso writes:
> Control: tags -1 + moreinfo
>
> Hi Steve,
>
> On Sun, Dec 10, 2023 at 07:41:15PM -0800, Steve VanDevender wrote:
> > Package: src:linux
> > Version: 6.1.66-1
> > Severity: grave
> > Tags: upstream
> > Justification: renders package unusable
> >
> > I
Control: tags 1054015 + pending
Dear maintainer,
I've prepared an NMU for ckb-next (versioned as 0.6.0+dfsg-0.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
This applies the same treatment to the udev install path.
Chris
diff -Nru
Package: rust-hyper-rustls
Version: 0.24.2-1
Severity: serious
Tags: patch
The autopkgtest for rust-hyper-rustls is failing, because the code in
test_alpn_http2 requires a runtime, but the feature requirements for
the test do not specify one.
A debdiff fixing this is attatched.diff -Nru
Source: lockdown
Severity: important
Hi,
lockdown missed bullseye and bookworm. It has an rc bug open since at
least 2020.
To me, it appears as if nobody cares about lockdown. Is it worth keeping
it around in unstable?
I would suggest to file an RM bug in a few weeks.
Chris
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 src:niceshaper
Dear ftpmasters,
please remove niceshaper.
It was removed from testing in 2020, has seen its last upload in 2016,
and since the removal nobody cared about doing
Package: src:linux
Version: 6.5.3-1~bpo12+1
Severity: wishlist
Tags: upstream
Dear Maintainer,
$ uptime
19:56:14 up 27 days, 8:01, 3 users, load average: 0.69, 0.49, 0.45
$ apt policy linux-image-6.5.0-0.deb12.1-amd64
linux-image-6.5.0-0.deb12.1-amd64:
Installed: 6.5.3-1~bpo12+1
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission
Submission-Type: new
Site: mirrors.cat.pdx.edu
Archive-architecture: amd64 arm64 armhf hurd-amd64 i386 riscv64
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Sage Imel
Country: US United
Source: python-cobra
Version: 0.26.3-2
Severity: important
Dear Maintainers,
python3-future is buggy and being removed out of Debian.
Your package declares an hardcoded dependency in d/control.
Current /setup.cfg also declare such dependency,
so it's better to first try to update to 0.29.
Source: duplicity
Version: 1.2.2-2
Severity: normal
The python3-future library is being removed from Debian:
it is unmaintained upstream & obsolete
and didn't build with Python 3.12.
duplicity is the top 1 remaining user of python3-future
Please package a new version of duplicity.
Greetings,
(Random Debian user who has used unstable/Sid - sharing my 2c)
Hi Dan,
On 11/12/23 20:40, Tianyu Chen wrote:
On Mon, 11 Dec 2023 15:22:24 +0800 Dan Jacobson wrote:
Today I out of habit hit RET to the following.
It removed much of my system.
On Mon, Dec 11, 2023 at 05:30:28PM +0100, Marco Moock wrote:
> The name teredo-debian.remlab.net doesn't resolve anymore as the operator
> closed down the service.
> teredo-debian.remlab.net can be used instead.
You gave the same server name twice here. Which service could work
nowadays?
C
On Thu, 7 Dec 2023 22:05:29 +1300 Vladimir Petko
wrote:
> As of today there are more test failures:
> Test Summary Report
> ---
> debian/test-out/eval/checks/documentation/manual/manpage-errors-from-man/generic.t
>
On Montag, 11. Dezember 2023 08:51:36 CET Martin-Éric Racine wrote:
[...]
>
> Unless I misunderstood, this is due to a change of debhelper behavior
> since compatibility level 10. This leaves me with two possible
> solutions:
>
> 1) No dh_install option. This will restart after upgrade (default
Hey.
Few weeks ago I've again stumbled over this, and tried to fix it, but
my Qt coding skills are worse than absolutely zero ^^
I did however found e.g. this:
https://gitlab.cs.fau.de/rudis/passt-mac/-/commit/00d4f8fc2c729b1baf723cacd2b5942b032b6784
which seems a commit that fixes a similar
On 10/12/2023 20:16, Julian Gilbey wrote:
> [...]I'd be in favour of doing the pandas
> transition now, which will allow Cython 3.0 to move into unstable.
Cython 3 is already in unstable; pandas is currently using cython-legacy.
And yes, my list of packages broken by pandas 2.x is those
Hey John.
On Wed, 2023-12-06 at 09:17 +0100, John Paul Adrian Glaubitz wrote:
> I am naturally aware of the new release because I am in direct
> contact with
> one of the upstream maintainers. The withheld update to 2.x is
> intentional
> for two reasons.
Ah I see. :-)
Then I wrongly thought
Source: python-canmatrix
Followup-For: Bug #1056461
This seems to really be a bug in python3-future:
```sh
$ python3-c "import past.builtins"
$ python3.12 -c "import past.builtins"
Traceback (most recent call last):
File "", line 1, in
File
Control: fixed -1 1.0.128+nmu2+deb12u1
On Thu, Dec 07, 2023 at 10:23:59AM +0100, Paolo Greppi wrote:
> Alberto's workaround (sudo apt install -t bookworm-backports
> debootstrap) worked for me.
This is working fine with the new version of debootstrap in bookworm,
i.e version
Just a random Debian user passerby; chiming in with my 2c...
On 11/12/23 18:51, Martin-Éric Racine wrote:
[...] This leaves me with two possible
solutions:
1) No dh_install option. This will restart after upgrade (default since dh 10).
Assuming that I understand correctly (this option will
Package: libcdb-dev
Version: 0.80-3
Severity: important
Control: affects -1 src:pdns
Hey,
libcdb-dev in stable ships libcdb.pc. The version in sid is missing this
file.
Given it still exists in the source package and stuff happens to it in
d/rules, I assume it should also be installed.
Thanks,
Package: mimedefang
Version: 3.3-1
Hi,
relay_is_blacklisted_multi sends out its multiple DNS requests at once,
and then uses IO::Select to wait for the various answers as they come in.
It has a loop in which it intends to remove each socket from the
IO::Select set as soon as it is done with it
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "mini-httpd":
* Package name : mini-httpd
Version : 1.30-6
Upstream contact : Jef Poskanzer j...@mail.acme.com
* URL :
control: tag -1 +patch
I'm checking the code in my previous fork !
So this PR first need to be applied.
https://github.com/pyxnat/pyxnat/pull/179
This can be used as a temporary patch
On 11.12.2023 21:30, Chris Hofstaedtler wrote:
On Mon, Dec 11, 2023 at 02:57:35PM +, Hilmar Preusse wrote:
Hi,
Severity: normal
This bug blocks the migration for now, I'll close
it, once the other two packages tend to migrate.
Pretty sure severity: normal does not block => raising.
On Fri, 8 Dec 2023 15:48:27 +0100 Emanuele Rocca wrote:
> Hi Simon,
>
> On 2023-12-07 08:39, Simon Josefsson wrote:
> > During debci autopkgtest of a new version of libgssglue on i386 I got
> > a failure like this, which is fatal and execution halts.
> >
> > 117s vex x86->IR: unhandled
okular and khelpcenter make kjs a key package via khtml.
While it is optional in okular, khelpcenter requires khtml.
This is changing with the 24.08.x versions, which will be part of Plasma 6.
When khelpcenter upgrades to a khtml-free version, this should be followed-up.
Source: pyxnat
Severity: normal
Dear Maintainers,
python3-future is being removed from Debian.
The current sources still contain stales references to "future".
These have been removed upstream since,
so any new release would also fix the problem.
Greetings
$ grep future -r
setup.py:
Well, its fixed, but why libclang-17.so.17 was used instead of libclang-17.so.1?
there is already libLLVM-17.so.1, so this is a pretty unique scheme,
which I haven't seen elsewhere.
Am Mi., 29. Nov. 2023 um 12:09 Uhr schrieb Debian Bug Tracking System
:
>
> This is an automatic notification
Hello,
Thank you for the quick answer and the details provided.
You can submit the test program to the upstream bugzilla, no problem.
Best regards,
Paulo Tomé
On Mon, Dec 11, 2023 at 9:36 PM Aurelien Jarno wrote:
> Hi,
>
> On 2023-12-09 18:23, Paulo Tomé wrote:
> > Package: libc6
> >
Hi Christoph,
Thanks for the quick response! We tried it again with the following inside
a Dockerfile:
FROM debian:bookworm-slim
RUN apt-get clean && apt-get update && apt-get install -y
--no-install-recommends libpq-dev=15.5-0+deb12u1
postgresql-client-15=15.5-0+deb12u1
And we get the
Control: forwarded -1 https://phabricator.kde.org/T11539
On Fri, 18 Aug 2023 14:26:46 +0200 Sune Stolborg Vuorela
wrote:
Note that okular 23.08 has migrated away from kjs.
libkf5kjs-dev is ist in Build-Depends. Please drop it with your next upload.
Before end of the year, upstream will
Hi,
On 2023-12-09 18:23, Paulo Tomé wrote:
> Package: libc6
> Version: 2.36-9+deb12u3
> Severity: normal
> Tags: upstream
> X-Debbugs-Cc: paulo.t...@gmail.com
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the
Control: block -1 by 1058031
This seems to be fixed upstream:
https://github.com/mcfletch/pyopengl/issues/99
The pyopengl test suite fails because pygame FTBFS with Python 3.12
(#1058031) this likely also affects the autopkgtest.
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182
Hi Ilias,
On Mon, Dec 11, 2023 at 10:08:49PM +0200, Ilias Tsitsimpis wrote:
> On Sun, Dec 10, 2023 at 09:01PM, Helmut Grohne wrote:
> > First and foremost, ghc now actively refuses being cross build with an
> > $(error ...). Would you mind weakening this to a $(warning ...)? While
> > that you
Source: yaz
Version: 5.34.0-1
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
yaz fails to cross build from source, because it hard codes the build
architecture pkg-config in two occasions. It thus fails finding the
relevant .pc files and fails. I'm attaching a patch for
Breaking news:
Am 11.12.23 um 19:14 schrieb Salvatore Bonaccorso:
> I have put binary packages for amd64 built in
> https://people.debian.org/~carnil/tmp/linux/1057967/
I confirm this test kernel is working fine for me, even with non-free
broadcom-sta.
(sent from
"
cat /proc/version
Linux
Hi,
On 2023-12-08 21:04, ChenPi11 wrote:
> Package: libc6
> Version: 2.37-13
> Severity: normal
> Tags: d-i
> X-Debbugs-Cc: wushengwuxi-msctino...@outlook.com
>
> Dear Maintainer,
>
> When apt was configuring the libc6:amd64 after I upgraded all packages, It
> lack of response for a long time
On 12/11/23 20:20, Michael Biebl wrote:
Is expecting a clean "fsck -n -f XXX" run wrong?
Have you tried "fsck.mode=force fsck.repair=yes" as well?
while not suspecting a defect in the manual pages, I tried all
combinations of yes/auto yes/preen. I have also tried rebooting now with
Package: postgresql-15
Version: 15.5-0+deb12u1
When I try to get the package it reports an error like below:
#12 3.623 Package postgresql-client-15 is not available, but is referred to
by another package.
#12 3.623 This may mean that the package is missing, has been obsoleted, or
#12 3.623 is
Control: tags -1 + moreinfo
Hi,
On Mon, Dec 11, 2023 at 04:02:16PM -0300, Dr. André Desgualdo Pereira wrote:
> Package: src:linux
> Version: 6.1.66-1
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led
Hi Alexandre,
Am Mon, Dec 11, 2023 at 09:18:16PM +0100 schrieb Alexandre Detiste:
> > https://github.com/lebigot/uncertainties/releases/tag/3.1.7
>
> +1
OK.
> > Also we should probably get rid of python-future at some point.
>
> I removed it from three games this week-end
> and filled 6 more
Control: severity -1 serious
On Mon, Dec 11, 2023 at 02:57:35PM +, Hilmar Preusse wrote:
> Severity: normal
> This bug blocks the migration for now, I'll close
> it, once the other two packages tend to migrate.
Pretty sure severity: normal does not block => raising.
C
On Mon, Dec 11, 2023 at 05:47:23PM +0100, Sven Joachim wrote:
> On 2023-12-11 16:22 +0100, Julien Cristau wrote:
>
> > Source: ncurses
> > Version: 6.4+20231121-1
> > Severity: important
> > Control: affects -1 mercurial
> > X-Debbugs-Cc: jcris...@debian.org
> >
> > Hi,
> >
> > Since a ncurses
Package: src:python-cloup
Version: 3.0.3-1
Severity: serious
Tags: sid trixie
python-cloup accesses the network while building the docs:
[...]
[autosummary] generating autosummary for: index.rst, pages/aliases.rst,
pages/arguments.rst, pages/changelog.rst, pages/constraints.rst,
Le lun. 11 déc. 2023 à 17:02, Jochen Sprickerhof a écrit :
> I think the right thing here is to package the new uncertainties version
> which drops the past import:
>
> https://github.com/lebigot/uncertainties/releases/tag/3.1.7
+1
> Also we should probably get rid of python-future at some
On 2023-12-11 17:47 +0100, Sven Joachim wrote:
> On 2023-12-11 16:22 +0100, Julien Cristau wrote:
>
>> Source: ncurses
>> Version: 6.4+20231121-1
>> Severity: important
>> Control: affects -1 mercurial
>> X-Debbugs-Cc: jcris...@debian.org
>>
>> Hi,
>>
>> Since a ncurses upgrade in testing
Hi Helmut,
On Sun, Dec 10, 2023 at 09:01PM, Helmut Grohne wrote:
> First and foremost, ghc now actively refuses being cross build with an
> $(error ...). Would you mind weakening this to a $(warning ...)? While
> that you don't want to support cross building of ghc, would you mind
> others (like
Source: insilicoseq
Severity: important
Dear Maintainers,
The removal of old unmaintained python3-future is being investigated.
A quick review of your package show stale references to "future" in:
- setup.py
- debian/control
Please patch them out and also report setup.py upstream.
Greetings,
Source: adios2
Followup-For: Bug #1058018
Control: severity -1 important
Call it teething issues. This is a new package, so I'm trying to avoid
making debian/control more verbose than it needs to be by not crowding
the fields with the strict specifications needed to avoid this error.
Once the
Package: python3-ntp
Version: 1.2.2+dfsg1-3
Severity: normal
Hey.
When upgrading to the current version, I got.
Setting up python3-ntp (1.2.2+dfsg1-3) ...
/usr/lib/python3/dist-packages/ntp/util.py:641: SyntaxWarning: invalid escape
sequence '\]'
m = re.match("([:.[\]]|\w)*", inhost)
Source: ditaa
Version: 0.10+ds1-1.3
Severity: important
Tags: ftbfs
Dear Maintainer,
The package fails to build from source in the sid chroot.
The relevant part of the build log:
dh binary --with javahelper
dh_update_autotools_config
dh_autoreconf
jh_linkjars
jh_build
As there were some questions along in this thread let me summarize
some points:
The issue affects fs/ext4 code, so no other filesystems are affected
(e.g. btrfs).
The issue affects all kernels which have the commit 91562895f803
("ext4: properly sync file size update after O_SYNC direct IO") from
Source: nipype
Severity: important
Dear Maintainer,
The remove of python3-future is being investigated:
it's obsolete and unmaintained and causes problems with Py3.12
It seems your package required it a long time ago.
Please now remove the hardcoded python3-future in d/control
and check
Sorry, I had the wrong branch of sstp-client checked out. Bastian, could you
please review my changes and upload if you see nothing wrong with it.
Otherwise, please let me know and I'll fix / update my notes.
Regards,- Eivind
På mandag 11. desember 2023 kl. 10:07:35 PST skrev Eivind Naess
On Mon, Dec 11, 2023 at 08:06:41PM +0100, Matthias Klose wrote:
> > [...]
> > Excellent - I didn't know about that. Are you OK for me to upload
> > versions of cython and cython-legacy which depend on this to fix the
> > Python 3.12 breakage?
>
> not for cython, which won't need that soonish for
Source: impacket
Severity: important
X-Debbugs-Cc: debian-pyt...@lists.debian.org
Dear Maitainer,
Upstream mistakenly added 'future' to the requirements in setup.py
Maybe they tought it was needed to get the
"from __future__ import ..." statements working.
That would had been "from future
Control: tags -1 + moreinfo
Hi Ilias,
there are reverse dependencies that need to be taken care of.
Please file for each package a different RM bug.
Please remove the moreinfo tag once that is done.
Thorsten
On 11/12/2023 14:20, Russell Coker wrote:
We have 2 different issues here. The first one is a SEGV related to sqlite,
that might be a sqlite bug. Have you tried writing a simple sqlite program or
using a sqlite utility to see if it also crashes?
Sorry, I have no ability to write such a
[please always CC the bug report on replies]
Am 11.12.23 um 19:47 schrieb Alessandro Ogier:
Ciao,
thanks for your reply.
I see there is something more complex than I'm able to figure out, but I
must report that upon reboot some trivial problems with the filesystem
persist so it doesn't
Source: multiqc
Severity: normal
X-Debbugs-Cc: debian-pyt...@lists.debian.org
Dear Maintainers,
Your package's setup.py declares an extraneous
dependency on old compatibility layer python3-future.
> setup.py:"future>0.14.0",
But it doesn't need it at all:
no import of "past" or
Source: galpy
Version: 1.8.1-2
Severity: important
X-Debbugs-Cc: debian-pyt...@lists.debian.org
Dear Maintainer,
The removal of the python3-future library is being evaluated.
It's obsolete & unmaitained upstream.
Your package seems not to have required python3-future for a long time.
Please
On 11.12.23 19:55, Julian Gilbey wrote:
On Mon, Dec 11, 2023 at 04:34:17PM +0100, Matthias Klose wrote:
On 11.12.23 16:19, Julian Gilbey wrote:
On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
[...]
You could package a non-conflicting cython-legacy, however that would
require
Package: binwalk
Version: 2.3.4+dfsg1-1
Severity: minor
X-Debbugs-Cc: werdah...@riseup.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainers,
thanks for providing binwalk. When digging into a firmware file I
noticed that the --disasm / -Y option does not work unless the required
Package: python3-sorted-nearest
Version: 0.0.38+dfsg-1.1
just seen that python3-sorted-nearest installs .pyx and .c files, both
probably don't belong into the binary package.
Package: src:linux
Version: 6.1.66-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Updating the kernel.
* What exactly did you do (or not do) that was effective (or
ineffective)?
It's officially stated in the upstream changelog:
## [v1.3.1](https://github.com/koed00/django-q/tree/v1.3.1) (2020-07-02)
[Full Changelog](https://github.com/koed00/django-q/compare/v1.3.0...v1.3.1)
--
- How is logging handled [\#209](https://github.com/Koed00/django-q/issues/209)
- ask
Ciao,
thanks for your reply.
I see there is something more complex than I'm able to figure out, but I
must report that upon reboot some trivial problems with the filesystem
persist so it doesn't seem like anything has really done.
Is expecting a clean "fsck -n -f XXX" run wrong?
Source: django-q
Version: 1.3.9-5
Severity: important
The python3-future is an old temporary solution
to have a billingual Python 2 + 3 codebase.
django-q doens't need it at all anymore.
The removal of python3-future is being investigated,
so please remove your package from the list to fix :-)
On Mon, Dec 11, 2023 at 04:34:17PM +0100, Matthias Klose wrote:
> On 11.12.23 16:19, Julian Gilbey wrote:
> > On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
> > > [...]
> > > You could package a non-conflicting cython-legacy, however that would
> > > require more changes, also how
Hi Fab, Apostolos and all,
My name is Phil Wyett (kathenas) and I am in the process of taking over as the
maintainer of
'librepfunc'.
I would ask that no commits or releases take place without my approval until
the transition is
complete.
I thank you for your assistance with this transition
Hi Fab and all,
My name is Phil Wyett (kathenas) and I am in the process of taking over as the
maintainer of
'w-scan-cpp'.
I would ask that no commits or releases take place without my approval until
the transition is
complete.
I thank you for your assistance with this transition and hope we
Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: a...@packages.debian.org
Control: affects -1 + src:amtk
The amtk source package was removed from Unstable with
https://bugs.debian.org/1056584
Please remove it from Experimental too.
Note that the
Am 11.12.23 um 18:30 schrieb Alessandro -oggei- Ogier:
Package: systemd
Version: 255-1
Severity: normal
Dear Maintainer,
while doing some checks for the recent kernel ext4 problem, I've
noticed fsck does not seem to be able to run at boot, the command
journalctl -u systemd-fsck-root
Package: devscripts
Version: 2.23.6
Tags: patch
The packages mk-build-deps builds work on only one architecture, even if the
built package architecture is "all". This is because the generated package
always includes a dependency on "build-essential:", where is a
specific architecture.
Because
Hi,
On Mon, Dec 11, 2023 at 01:27:07PM +0100, Kevin Price wrote:
> Thank you Salvatore!
>
> Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso:
> > It still would be helpfull if you can get to the logs of the previous
> > boot. After booting back in the working kernel, do you have anything
> >
Hi
I'm sorry for the semver breakage, the last version was a bit stressed
out due to the security problems with libgit2 not verifying server
signatures (that has since been fixed).
I think the best path forward might be to package the latest versions,
I have started that but not finished yet due
On Sat, Dec 02, 2023 at 01:22:04AM +0100, Guillem Jover wrote:
> Package: debian-policy
> Version: 4.6.2.0
> Severity: wishlist
>
> Hi!
>
> Starting with dpkg 1.22.0, it implements a dpkg-build-api mechanism
> similar in concept to the debhelper-compat levels.
>
> You can check its
I don't think it is released yet, and I don't think there is anything blocking
it. Let me have a day or two to figure it out. High priority stuff at work
På mandag 11. desember 2023 kl. 09:39:06 PST skrev Bastian Germann
følgende:
Hi Eivind,
I see you have released 1.0.19. Does this
Hi
Any new information, when will this be patched?
There are packages that can not be installed like nvidia-driver because
while installing it updates the system and the process fails.
Isn't possible to remove from the repo the corrupted kernel so that people
can install other packages?
Control: forwarded -1
https://salsa.debian.org/security-tracker-team/security-tracker/-/merge_requests/155
On 02/11/2023 07:01, Salvatore Bonaccorso wrote:
Control: tags -1 + confirmed
Hi,
On Mon, Oct 09, 2023 at 11:48:59AM +0200, Bastian Blank wrote:
Package: security-tracker
Severity:
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "urlview":
* Package name : urlview
Version : 1c-1
Upstream contact : https://lists.sr.ht/~nabijaczleweli/urlview-ng
* URL :
Source: gammapy
Version: 1.1-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
Hi Maintainer
gammapy FTBFS [1] with Python 3.12 as a supported version. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
Hi Eivind,
I see you have released 1.0.19. Does this fix the issue?
If so, please hand in a package update.
Thanks,
Bastian
On 11.12.23 08:12, Matthias Klose wrote:
On 10.12.23 14:06, Rebecca N. Palmer wrote:
Is this an acceptable amount of breakage or should we continue to
wait? Bear in mind that if we wait too long, we may be forced into it
by some transition further up the stack (e.g. a future Python or
numpy)
On Mon, 11 Dec 2023 10:38:40 +0100 helios.sola...@gmx.ch wrote:
> I have been running debian 12.3 with kernel 6.1.64-1 for a few hours,
> how can I find out whether the file system has been corrupted?
yes, I would also appreciate an explanation who could be affected,
how to diagnose the problem,
Hello,
downgrading `optclient` to the bookworm version (which implies the installation
of libcotp12) fixes the problem for me.
(please note, that *new* OTP keys created in a newer version of otpclient need
to be discarded and created again)
I just opened an upstream issue [1] for otclient
On Monday, December 11, 2023 5:26:14 PM CET Lisandro Damián Nicanor Pérez
Meyer wrote:
> > +1 from me. qtchooser is no longer supported for Qt >= 6, so going
> > this way is just awesome.
>
> Also worth to mention: this is something I should have done myself,
> but I currently lack the needed
Package: gitlab
Version: 16.0.8+ds1-2~fto12+2
Severity: important
Dear Maintainer,
Relevant section from the logs:
-
OpenSSL::PKey::PKeyError (pkeys are immutable on OpenSSL 3.0):
On 2023-12-11 16:57:34 +0100, Andreas Tille wrote:
> Am Mon, Dec 11, 2023 at 01:36:38PM +0100 schrieb Sebastian Ramacher:
> > > OK, but what is your suggestion? Reverting and have broken tests due to
> > > the pandoc issue?
> >
> > pandoc is fixed in unstable.
>
> Really? Salsa CI[1] says:
>
1 - 100 of 199 matches
Mail list logo
