Package: mini-dinstall
Version: 0.7.0
Severity: normal
Tags: patch
Dear Maintainer,
It seems that due to gnupg fussiness, package signature verification
doesn't always work as intended:
mini-dinstall [3082992768] INFO: Booting mini-dinstall 0.7.0
mini-dinstall [3082992768] INFO:
Package: libxcrypt
Version: 4.4.33-1
Severity: wishlist
Tags: patch
User: debian-de...@lists.debian.org
Usertags: loongarch64
Hi libxcrypt maintainers,
Thanks for adding a symbols file for loong64 (LoongArch).
Please change the name of loong64 symbols file, from
On Thu, 11 Aug 2022 09:43:27 +0200 =?UTF-8?Q?Jelmer_Vernoo=C4=B3?=
wrote:
> This is still waiting for pyo3 to make it through NEW.
hey Jelmer,
in case you didnt see it, pyo3 has been accepted in unstable
https://tracker.debian.org/pkg/rust-pyo3 so maybe the effort to
package maturin can
* Vagrant Cascadian [2022-12-28 18:00]:
Hrm. This suggests the fix might not have been effective, which should
have been included in 2022.07... CCing upstream...
commit e744bf3a4ba442a0e9ee1c509c70e1452e3a15d0
Author: Tom Rini
Date: Wed Jun 8 14:30:14 2022 -0400
odroid_xu3: Fix
Source: cl-sql
Version: 6.7.1-3
Severity: serious
Control: close -1 6.7.2-1
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60
Hi.
On Wed, Dec 28, 2022 at 03:21:05PM -0800, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
> > On 2022-08-20, Vagrant Cascadian wrote:
> >> On 2022-08-10, Vagrant Cascadian wrote:
> >>> This bug is just to delay migration to testing while more platforms get
> >>>
On Friday, December 23, 2022 5:15:35 AM EST Sebastian Andrzej Siewior wrote:
> On 2022-12-22 18:31:37 [-0500], Scott Kitterman wrote:
> > I think we should focus on getting clamav up to 1.0.0 before the freeze
> > and
> > deal with the unrar bits later (should be easy enough to get a freeze
> >
Package: vtun
Version: 3.0.4-2
Severity: normal
Dear Maintainer,
Since v3.0.4 vtun doesn't create pidfile for client process like
vtund.NAME-10.1.2.3.pid.
It always rewrites pid in /run/vtund.server.pid that is wrong.
I think this is upstream's regresion between v3.0.3 and v3.0.4
Replacing a
Sadly, my sheevaplug was not revivable. I have a couple of OpenRD boxes and a
couple of CUBox-i boxes I can test for you, as well as a RaspberryPi-4B and a
couple of Orange-Pi boxes that can also be tested. I'll send results as I get
to them.
BTW, are there directions for installing and
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: golang-github-containers-p...@packages.debian.org,
siret...@tauware.de, siret...@gmail.com, Vignesh Raman
vignesh.ra...@collabora.com
Control: affects -1 +
Package: buildah
Version: 1.28.0+ds1-3
Severity: normal
User: de...@kali.org
Usertags: origin-kali
X-Debbugs-Cc: siret...@tauware.de
Dear Maintainer,
the buildah package currently in Sid (1.28.0+ds1-3) is affected by
upstream bug: https://github.com/containers/buildah/issues/4427
It is solved
Here's another Cubox-i. This one's running Bookworm.
shows a surprising number of u-boot-
packages installed, ( = exynos, imx, omap, sunxi) as well as plain
"u-boot". All of them are version 2022.04+dfsg-2+b1.
Rebooting while watching the serial console output says "U-Boot SPL
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: golang-github-containers-stor...@packages.debian.org,
siret...@tauware.de, siret...@gmail.com, Vignesh Raman
vignesh.ra...@collabora.com
Control: affects -1 +
A Cubox-i running Debian bullseye (11.6). According to It
has "u-boot-tools" (version 2021.01+dfsg-5) installed, but none of the
u-boot- packages installed.
If I reboot it and watch the serial console, I see it showing "U-boot
2021.01-dfsg-5" so that version must have gotten into the
Raspberry Pi 4B (8GB) running bullseye, but does not seem to have any version
of u-boot installed. Weird?
Running tells me that the following (among
lots of others) versions are available. Should I install one of them and see
what happens?
Package u-boot-rpi:
p 2021.01+dfsg-5 stable 500
Control: forwarded -1 https://sourceforge.net/p/gnuplot/bugs/2575/
On 2022-12-29 02:45:35 +0100, Vincent Lefevre wrote:
> The forward was for the missing terminal types. I have not reported
> this second bug upstream yet.
I've now reported the bug upstream.
--
Vincent Lefèvre - Web:
On 2022-12-25, Jochen Sprickerhof wrote:
> * Vagrant Cascadian [2022-11-04 14:22]:
>>On 2022-06-02, Jochen Sprickerhof wrote:
>>> with the latest u-boot-exynos in unstable it tries to load
>>> exynos5422-smdk5420xu4.dtb whereas linux-image-5.17.0-3-armmp only
>>> contains
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "nvidia-vaapi-driver":
* Package name : nvidia-vaapi-driver
Version : 0.0.8-1
Upstream contact : Stephen
* URL :
> > There are handful more errors in the form of:
> >
> > * ValueError: setting an array element with a sequence. The
> > requested array has an inhomogeneous shape after 1 dimensions. The
> > detected shape was (2,) + inhomogeneous part.
> > * Too many indices for array: array is
Control: retitle -1 gnuplot-doc: spurious menu at the end of Section 4 of
gnuplot.info breaks navigation in info
Control: notforwarded -1
The forward was for the missing terminal types. I have not reported
this second bug upstream yet.
On 2022-12-29 00:51:19 +0100, Vincent Lefevre wrote:
[...]
Package: keyboard-layout
Version: 1.213
Severity: important
Dear Maintainer,
After upgrading keyboard-configuration and console-setup from 1.212 to
1.213 and rebooting, I saw a "syntax error" message before my full-disk-
encryption passphrase prompt. I then failed several times to enter a
valid
On 2021-05-24 01:21:56 +0200, Vincent Lefevre wrote:
> After "info gnuplot", go to "Terminal_types::". One gets:
>
>
> 4 Terminal types
>
>
> * Menu:
>
> * complete_list_of_terminals::
>
> thanks! matplotlib/3.6.2-3 has been accepted in unstable
bugs have been filed:
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debian-python%40lists.debian.org=matplotlib3.6
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter:
Control: notfound -1 dgit/10.2
Control: fixed -1 dgit/10.2
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
tags -1 + pending
> This package ships /usr/share/zsh/vendor-completions/_awscli which I
> expect it to work like other files in zsh/vendor-completions.
>
> For example, I should have `aws` completion if I just called `compinit`
> in my zshrc.
>
> But I still need to `source
Control: severity -1 serious
Control: found -1 dgit/10.3
Control: block 944855 by -1
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Package: wnpp
Severity: normal
X-Debbugs-Cc: coco-...@packages.debian.org
Control: affects -1 + src:coco-cpp
The former maintainer is no longer active and per a discussion with the former
sponsor, I'm orphaning the coco-cpp package.
The package description is:
Coco/R is a compiler generator,
Package: dgit
Version; 10.3
Severity: serious
Control: block 944855 by -1
As per the deployment plan in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944855#29
it would be best if dgit 10.3 didn't migrate to testing until
the corresponding infrastructure has been deployed and tested
in the
Am Tue, Nov 29, 2022 at 10:04:34PM +0100 schrieb Salvatore Bonaccorso:
> Source: libetpan
> Version: 1.9.4-3
> Severity: important
> Tags: security upstream
> Forwarded: https://github.com/dinhvh/libetpan/issues/420
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
>
> Hi,
>
> The
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
Same bug. On boot it is broken. Playing music with `mplayer` seems to work
but no sound. pulseaudio --kill brings everything to life again. I waited a
few hours as an experiment to see if the sound died off but everything
seemed fine after restarting pulseaudio. dmesg seemed quite boring but I'm
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On Thursday, 29 December 2022 00:21:05 CET Vagrant Cascadian wrote:
> debian stable (2021.01*), testing (2022.04*), unstable (2022.10*)
> and experimental (2023.01-rc*)
>
> # arm64
> ...
> rock64-rk3328
I don't recall ever having issues with u-boot on my Rock64's, so for me
2022.04 - 2022.10
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
Package: wnpp
Severity: wishlist
Owner: Timo Röhling
X-Debbugs-Cc: debian-de...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: python-linetable
Version : 0.0.2
Upstream Author : Alessandro Molina
* URL :
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: primesense-nite-nonf...@packages.debian.org
Control: affects -1 + src:primesense-nite-nonfree
Please remove primesense-nite-nonfree. It's broken since 2014 (#771187)
and hasn't seen an
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
Control: unmerge -1
Control: retitle -1 gnuplot-doc: spurious menu at the end of Section 4 breaks
navigation
On 2022-11-22 15:08:10 +0100, Vincent Lefevre wrote:
> doc2texi.el has
>
> (defvar d2t-terminal-directory (expand-file-name "../term/")
> "Location of .trm files in gnuplot source
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
Source: scapy
Severity: normal
Tags: upstream
Dear maintainer(s),
I would like to give notice that we have released a new major version of Scapy
(2.5.0) ! Thanks a lot for the packaging work.
I also have a few notes/advices I thought I'd share regarding recent changes
and how to package
clap-derive-3 is merged. I don't know if dch should be amended (i.e. just one
entry). See
https://salsa.debian.org/rust-team/debcargo-conf/-/commit/5903ecc88fbd59b3dc2b8665e37d3750a97ab527
Cheers
werdahias
On Fri, 23 Dec 2022 14:53:02 +0100 Fabio Pedretti
wrote:
> Is this still an issue with 22.3.1-1?
If that helps, I have one Intel laptop with Haswell GPU and it works fine
with Mesa 22.3.1
(KDE Plasma).
Shmerl.
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please
On 2022-12-22, Vagrant Cascadian wrote:
> On 2022-08-20, Vagrant Cascadian wrote:
>> On 2022-08-10, Vagrant Cascadian wrote:
>>> This bug is just to delay migration to testing while more platforms get
>>> tested. If you have a relevent board, please consider testing and
>>> reporting the status:
Source: glslang
Version: 11.12.0-1
Severity: wishlist
Tags: patch
Hi, could you please consider marking glslang-tools as Multi-Arch: foreign?
This would allow packages like yuzu to cross-build without having to manually
specify :native on the build-dependency.
I've attached a patch for your
On 2022-12-28, Vagrant Cascadian wrote:
> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
> commit triggering the issue has been identified as:
>
> a9bf024b2933bba0e23038892970a18b72dfaeb4
>
Control: reassign 1026705 src:python-kajiki 0.9.1-1
Control: affects 1026705 src:python-pecan
* Lucas Nussbaum [2022-12-20 18:42]:
=== FAILURES ===
___ TestEngines.test_kajiki
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: selfh...@packages.debian.org
Control: affects -1 + src:selfhtml
Please remove selfhtml. The last upload was in 2008, it's RC-buggy (#1002966)
and these docs describe the state of
Source: netty
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security
Hi,
The following vulnerabilities were published for netty.
CVE-2022-41915[0]:
| Netty project is an event-driven asynchronous network application
| framework. In versions prior to 4.1.86.Final, when calling
Source: libde265
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security
Hi,
The following vulnerabilities were published for libde265.
CVE-2022-43235[0]:
| Libde265 v1.0.8 was discovered to contain a heap-buffer-overflow
| vulnerability via ff_hevc_put_hevc_epel_pixels_8_sse
These two bugs are related, I don't know if the owners want them
merged so I'm sending this to at least link them together for the
readers.
https://bugs.debian.org/955208
https://bugs.debian.org/1026333
Cheers,
--
Samuel Henrique
On 25/05/22 04:20 PM, Wolfgang Walter wrote:
Hi Wolfgang,
> opt-verify
>
> on the server side allows 2.5.6 clients to connect again. So it seems that
> 2.5 and 2.6 disagree on tun-mtu (as the warning is not logged if both sides
> are either 2.5.6 or 2.6).
Could you try again with the just
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: loganaly...@packages.debian.org
Control: affects -1 + src:loganalyzer
Please remove loganalyzer. It's broken since PHP 7 #974586, dropped
from testing since 15 months and hasn't seen a
Ondrej, Marco
According to the developers of sysrepo and libyang, 1.x is no longer being
maintained or supported.
So, I guess all related debian packages must be migrated to 2.x versions..
Kind regards
Irfan
On Wed, Dec 28, 2022 at 10:51 PM Marco d'Itri wrote:
> On Nov 10, Irfan Mohammad
Wow, for once an email from Bugs.Debian mailing list was sorted to the correct
folder!
> We will assist and supply the code to run on your side.
Why not just send off a message to the Konqueror Development lists to pull a
Google on that browser, but, also nail Desktop/device integration?
Kind
Package: wnpp
Severity: wishlist
Owner: Aurélien COUDERC
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian KDE Extras Team
* Package name: activity-aware-firefox
Version : 0.4.1
Upstream Contact: Matija Šuklje
* URL :
On Nov 10, Irfan Mohammad wrote:
> The currently provided version from debian for libyang2 is quite old,
> and a lot of new fixes have come in from the repository maintainers.
Ondrey, do you need help?
Are there specific reasons why a newer release has not been packaged?
--
ciao,
Marco
On Dec 22, Marco d'Itri wrote:
> Let's try this way: push your best attempt at a new package to your
> repository and I will review it and try to upload it.
> I will avoid further communications unless strictly needed.
https://github.com/FRRouting/frr/commits/debian/master is stuck to 2020:
Control: retitle -1 libapache-poi-java needs updates for newer xmlbeans
On Fri, 24 Jun 2022 09:54:32 +0200 =?ISO-8859-1?Q?S=E9bastien?= Villemot
wrote:
octave-io’s upstream
thinks that the problem comes from an incorrect combination of versions
between libapache-poi-java and xmlbeans. That
Hi,
On Thu, 26 May 2022 08:40:07 +0200 Lucas Nussbaum wrote:
Source: libspring-java
Version: 4.3.30-1
During a rebuild of all packages in sid, your package failed to build
on amd64.
This seems related to the new upstream version of xmlbeans earlier this
year. It seems to me that also
1 - 100 of 213 matches
Mail list logo
