control: retitle -1 ITA: sniproxy -- Transparent TLS and HTTP layer 4 proxy
with SNI support
control: owner -1 !
Thanks for your work on sniproxy over the years!
G'luck,
Peter
--
Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/
I'm happy to have co-maintainers, but with less than a dozen packages in my list
I would hope to be able to keep it in good shape.
Package: wnpp
Severity: wishlist
Owner: Peter
X-Debbugs-Cc: debian-de...@lists.debian.org, pe...@pblackman.plus.com
* Package name : cevomapgen
Version : 26
Upstream Contact:
* URL : https://sourceforge.net/projects/cevomapgen/
* License : GPL3+
Programming
ccess to a Salsa repository, how the CI will go.
I actually prefer the look of asunder and am therefore more likely to continue
to use it over grimripper.
(I realise this is subjective)
Regards,
Peter
Package renamed;
* Package name : grimripper
Version : 3.0.0-1
Upstream contact : Salamandar
* URL : https://gitlab.gnome.org/Salamandar/GrimRipper
* License : GPL-2, CC0-1.0
* Vcs : TBD
Section : sound
The source builds th
On Fri, 5 May 2023 17:59:01 +0200 Bastian Germann wrote:
> On Sat, 29 Apr 2023 20:10:02 +0100 Peter Blackman wrote:
> > cdreaper is the Gtk3 fork of asunder
> > https://tracker.debian.org/pkg/asunder
> >
> > I would like to set up a packaging VCS on Salsa under the
package: tracker.debian.org
The "news" on the tracker pages seems to be updating, but the information
on package versions does not. This is most noticable for new Packages
where the page still says "Package is gone" over a week after the
package was first uploaded.
https://tracker.debian.org/pkg
Upstream have now renamed the project to GrimRipper
https://gitlab.gnome.org/Salamandar/GrimRipper
On May 4, 2023 3:35:40 PM Pascal Hambourg wrote:
On 04/05/2023 at 16:21, Peter Ehlert wrote:
"Install the GRUB boot loader" menu ... 6 items
Enter device manually
/dev/sda (usb-SanDisk ...
/dev/sdb (ata-WL4000G ...
/dev/sdc (ata-WDC_WD300...
/dev/sdd (ata-WDC_WD300...
/de
On 5/2/23 11:59, Pascal Hambourg wrote:
On 02/05/2023 at 15:21, Peter Ehlert wrote:
DI asks on which drive to install GRUB
User says disk X
DI attempts to install on Drive Y
result ... GRUB does not get installed at all
This is completely different from what I understood.
The statement
On 4/30/23 01:17, Pascal Hambourg wrote:
On 30/04/2023 at 01:47, Peter Ehlert wrote:
On 4/29/23 15:41, Pascal Hambourg wrote:
On 29/04/2023 at 16:02, Peter Ehlert wrote:
reboot gave me the Old GRUB menu, not including my new system.
What do you mean by "old GRUB menu" ? The
On 4/29/23 15:41, Pascal Hambourg wrote:
Hello Peter,
On 29/04/2023 at 16:02, Peter Ehlert wrote:
Legacy aka BIOS booting
system has 4 physical disk drives, all GPT partition tables
only one drive has a partition with bios_grub
install was on a drive without bios_grub
when install was
On 4/29/23 09:21, Steve McIntyre wrote:
On Sat, Apr 29, 2023 at 08:51:48AM -0700, Peter Ehlert wrote:
On 4/29/23 07:23, Steve McIntyre wrote:
Hi Peter,
Could you please share a copy of the installer logs? You should be
able to find them in /var/log/installer on the installed system.
there
th 'dget' using this command:
dget -x
https://mentors.debian.net/debian/pool/main/c/cdreaper/cdreaper_3.0.0-1.dsc
Changes for the initial release:
cdreaper (3.0.0-1) unstable; urgency=medium
.
* Initial release (Closes: #1035103)
Regards,
--
Peter Blackman
Package: wnpp
Severity: wishlist
Owner: Peter
X-Debbugs-Cc: debian-de...@lists.debian.org, pe...@pblackman.plus.com
* Package name : cdreaper
Version : 3.0.0
Upstream Contact: Salamandar
* URL : https://gitlab.gnome.org/Salamandar/Reaper
* License : GPL2
Control: tags -1 -moreinfo
On Fri, Apr 28, 2023 at 08:55:51PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo confirmed
>
> On 2023-04-28 04:58:51 +0300, Peter Pentchev wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.deb
Package: grub-installer
Boot method: USB
Image version: debian-bookworm-DI-rc2-amd64-netinst.iso
download from Debian
Date: 2023-04-28 ~17
Machine: HP Z820 Workstation
Processor: 2x 8-core model: Intel Xeon E5-2687W
Memory: 47.06 GiB
Partitions:
peter@RC2net:~$ df -T
Filesystem Type 1K
On 28/04/2023 18:58, Fabian Grünbichler wrote:
I see no practical issue with 2 meaning we can't have multiple semver
suffix packages variants of a single crate installed - having the
unversioned and one semver suffix package in one suite at any given time
should already be the exception, having m
On 28/04/2023 06:05, Helmut Grohne wrote:
Can you go into more detail as to what you mean with "don't support
version ranges"?
You can place a lower bound on the version, place an upper bound
on the version or constrain to a precise version. But you can't
constrain to a range of versions.
I
reassign 1034865 rust-virtiofsd
thanks
On 28/04/2023 05:23, Michael Tokarev wrote:
I'm sorry about this.. - I planned but forgot to include the link,
here it is:
https://buildd.debian.org/status/fetch.php?pkg=rust-virtiofsd&arch=riscv64&ver=1.5.1-2&stamp=1682451850&raw=0
The real error seems
+Replaces older versions of
+the -dev one. Closes: #1034935
+
+ -- Peter Pentchev Fri, 28 Apr 2023 04:48:28 +0300
+
libmodulemd (2.14.0-2) unstable; urgency=medium
* Use the GitHub API in the watch file.
diff -Nru libmodulemd-2.14.0/debian/control libmodulemd-2.14.0/debian/control
Summarising a number of bug reports by Helmut Ghrone:
Please ensure that librust---dev has sufficient Breaks and
Replaces declarations.
The issue specifically appears to be that the breaks+replaces are declared
against a virtual package, it seems dpkg is honoring the breaks against the
virtua
Package: singular
Version: 1:4.3.1-p3+ds-1
Severity: serious
Justification: rc-policy - "Packages must be buildable within the same release"
singular build-depends on python3-brial. python3-brial recently added a
dependency on python3-sage making it uninstallable on many architectures.
As a resul
On 23/04/2023 21:07, Paul Gevers wrote:
Can you point to a discussion where we might draw the conclusion that
this is common practice or consensus? I *personally* [no hats on] find
that distinction a bit weird although I can see how we would come to
it and also why.
No, I can't point to a dis
On 23/04/2023 19:19, Paul Gevers wrote:
I claim this is wrong. Would python3-sage one day build on more
architectures, this list would need manual updating. Instead of
hard-coding the list, it's better to ensure the build doesn't happen
or fails on architectures where python3-sage is not av
reassign 1034723 rust-h2
thanks
The following vulnerability was published for rust-hyper.
CVE-2023-26964[0]:
|/An issue was discovered in hyper v0.13.7. h2-0.2.4 Stream stacking /|/occurs
when the H2 component processes HTTP2 RST_STREAM frames. As a /|/result, the
memory and CPU usage are hig
Package: usb.ids
Version: 2023.01.16-1
Severity: minor
The UI at http://www.linux-usb.org/usb-ids.html, and the email
submission interface, do not permit submissions of anything but
vendors, devices, and classes. Here are some other typos I found just
by paging through the usb.ids file. If you h
Hi,
thank you very much for confirming the problem.
I have also tried with the cinnamon desktop and this also failed to work
properly with (an updated) debian-testing. In addition i tried with a
linux mint release (21.1) and mate which worked fine.
=== mint 21.1
$ dpkg -l | grep 'ii mate-des
Package: python3-brial
Version: 1.2.11-2
Severity: serious
X-debbugs-cc: singu...@packages.debian.org
python3-brial recently added a dependency on python3-sage, however python3-sage
is only available on amd64, arm64, i386 and riscv64.
This also means that the build-depends of singular on those a
Source: openssh
Version: 1:9.1p1-2
Severity: minor
I have no idea what possessed you to fix the dates on those
20-year-old changelog entries, but since you care ... 1:3.0.2p1-2 is
still wrong.
The correct fix was not s/Sat/Sun/ but s/2003/2002/.
It would be nice to have a new upstream version with support for fetching keys
via DANE.
I tried to update to the new upstream version but ended up running into
a number of missing build-dependencies.
Not in Debian at all
* librust-dot-writer-0.1+default-dev (>= 0.1.3-~~)
Newer version neede
I've uploaded the new version of rust-bstr to experimental, I have also
prepared but
not uploaded updates for the reverse dependencies, notes on rdeps below.
assert_cmd - new upstream 2.0.8 prepared and patch dropped in debcargo-conf
(even newer upstream releases are available but have new depe
https://rustsec.org/advisories/RUSTSEC-2023-0031.html
https://github.com/mvdnes/spin-rs/issues/148
0123456789001234567890012345678900123456789001234567890012345678900123456789001234567890
https://codesearch.debian.net/search?q=try_call_once&literal=1 returns 8
results.
4 in rust-pnce-cell and
On 13/04/2023 15:31, Peter Green wrote:
I've filed a bug with sequoia upstream. I haven't investigated the other
packages at this time.
I just did a quick test of sniffglue, ron and ureq, sniffglue and ron were
all able to run "cargo test --all --all-targets --all-features&qu
BTW, Fabian messages sent to bug reports are not sent to the sumbitter
by default, if you are replying to a submitter you need to put them
in to/cc or they may not see your reply.
Fabian Grünbichler wrote:
hope that's okay for the time being :) feel free to ping the bug if you
have the feeling t
Package: libavcodec60
Version: 7:6.0-1
Severity: minor
libavcodec{59,60} cannot be co-installed because both depend on exact
versions of libswresample4. (Also, libavfilter{8,9} have the same
issue.)
This will require an all-or-nothing library transition, and it means I
can't install ffmpeg 6.0 f
On 06/04/2023 11:44, Christian Marillat wrote:
On 06 avril 2023 11:26, Peter B wrote:
I think this problem is now resolved.
The big red ERROR texts in the Watch column on my DDPO page are slowly going
away.
I don't know. I re-written my watch files to check sourceforge.net
inste
net/debian/pool/main/p/profile-cleaner/profile-cleaner_2.44-1.dsc
Changes for the initial release:
profile-cleaner (2.44-1) unstable; urgency=medium
.
* Initial release. (Closes: #1033413)
Regards,
Peter Blackman
backporting the patch with
> the fix.
Hi,
Thanks for filing this bug report.
The patch is already included in libzstd 1.5.4+dfsg2-5 in unstable;
I guess I will have to ask the release managers for a freeze exception so
that this version migrates to testing.
G'luck,
Peter
--
I think this problem is now resolved.
The big red ERROR texts in the Watch column on my DDPO page are slowly going
away.
Cheers,
Peter
On Wed, 29 Mar 2023 08:05:01 +0200 Christian Marillat
wrote:
> Package: qa.debian.org
> Severity: normal
>
> Dear Maintainer,
>
> For s
10:45:22 2023
|
|
|
| power: server power is currently: Off
It'd be nice if the system actually rebooted on a reboot :)
Cheers,
weasel
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.o
On Sat, 01 Apr 2023, Peter Palfrader wrote:
> --- /usr/lib/nagios/plugins/check_running_kernel2023-03-08
> 11:28:49.0 +0100
> +++ ./check_running_kernel 2023-04-01 11:35:33.643925332 +0200
> @@ -164,6 +164,8 @@
> cat_vmlinux "$image" "\x
extract kernel image." 2>&1
exit 1
root@nautilus:~#
Cheers,
weasel
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `-https://www.debian.org/
Package: wnpp
Severity: wishlist
Owner: Peter
X-Debbugs-Cc: debian-de...@lists.debian.org, pe...@pblackman.plus.com
* Package name : profile-cleaner
Version : 2.44
* URL : https://github.com/graysky2/profile-cleaner
* License : Expat
Programming Lang: Bash
severity 103 normal
retitle 103 rust-encoding is unmaintained upstream
severity 104 normal
retitle 104 rust-boxfnonce is unmaintained upstream
severity 105 normal
retitle 105 rust-const-cstr is unmaintained upstream
(summarising several bugs)
there is https://rustsec.org/
hanks everyone, and keep up the great work!
G'luck,
Peter
--
Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
signature.asc
Description: PGP signature
2023-03-20 at 17:56, Peter Rosin wrote:
> Dear Maintainer,
>
> After crashing the kernel with "echo c > /proc/sysrq-trigger" the
> watchdoggery sometimes failes to trigger a reboot. It's as if the
> watchdog daemon continues to successfully perform its checks an
Package: strawberry
Version: 1.0.14-1
Severity: important
Tags: upstream
X-Debbugs-Cc: pe...@pblackman.plus.com
A bug affecting the tag editor can cause possible corruption of media files.
Versions affected are all versions from 0.9.1 to the current latest 1.0.15.
The issue occurs whenever you e
he "if (tbinary == NULL)" test is moved to before the
fork() call in the check_bin() function in that patch. But maybe
I misread something?
Anyway, please repair the broken fork test (or adjust the manual
to the new reality.)
Cheers,
Peter
-- System Information:
Debian Release
On Sat, Mar 18, 2023 at 11:25:52PM +0200, Peter Pentchev wrote:
> On Thu, Mar 09, 2023 at 04:39:16PM +, John David Anglin wrote:
> > Source: libzstd
> > Version: 1.5.4+dfsg2-4
> > Severity: normal
> > Tags: ftbfs
[snip]
> > 1.5.2+dfsg2-3 was okay.
>
>
s failed in -1,
so I disabled them in -2, then I applied an upstream fix and reenabled them in
-3, thinking that everything would be fine, but it was not :)
So yeah, thanks again for keeping track and filing this bug!
G'luck,
Peter
--
Peter Pentchev r...@ringlet.net r...@debian.org p
Package: mailman3-web
Version: 0+20200530-2.1
Severity: normal
Dear Maintainer,
I had a working mailman3 installation. I did 'apt upgrade' which pulled
in a new python3-hyperkitty and nginx. Now when trying to manage
'held messages' on a list:
-- the checkbox next to 'Subject' does not toggle
Attaching patchDescription: Fix missing crtbeginS.o on mipsel
Add mipsel to the case statement, so the gcc library folder
is defined in /etc/fpc/cfg
Forwarded: No
Author: Peter Blackman
Last-Update: 2023-03-14
Index: b/fpcsrc/packages/fpmkunit/src/fpmkunit.pp
Package: fp-compiler-3.2.2
Version: 3.2.2+dfsg-18
Severity: important
Tags: patch upstream ftbfs sid bookworm
Usertags: mipsel
Forwarded: https://gitlab.com/freepascal.org/fpc/source/-/issues/40201
X-Debbugs-Cc: debian-m...@lists.debian.org
Dear Maintainer,
* What led up to the situation?
rror string, and nothing else on the line, ie.
# In 3.0.0+dfsg-5 elbrus added fp-fix-timestamps that expects
d/source/timestamps
# lintian bug: http://bugs.debian.org/825222
unknown-file-in-debian-source
Cheers,
Peter
It seems the problem only occurs if a style sheet is selected.
Sadly, not fixed in release 0.8
reopen 1032854
reassign 1032854 rust-lock-api-0.1
retitle 1032854 rust-lock-api-0.1: RUSTSEC-2020-0070: lock_api: Some lock_api
lock guard objects can cause data races
thanks
I was made aware on IRC that RUSTSEC-2020-0070 also affects
rust-lock-api-0.1.
The only reverse dependency of rust-lock-
Package: dgit
dget -d http://deb.debian.org/debian/pool/main/g/git/git_2.39.2-1.1.dsc
mkdir dgittest
cd dgittest
git init
dgit import-dsc ../git_2.39.2-1.1.dsc +workingbranch
results in.
Dgit metadata in .dsc: specified git info (debian)
dgit: import-dsc of .dsc with Dgit field, using git hash
I've prepared an NMU for rust-kvm-bindings (versioned as 0.5.0-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it.
It's not my place to tell you to cancel it, but I can tell you that it
it will not clear the path for testing migration.
The new version of rust-k
Please try to update this tool in order to have a more recent version
in Bookworm!
I tried to update sequoia-wot and got
dpkg-checkbuilddeps: error: Unmet build dependencies:
librust-clap-mangen-0.2+default-dev librust-openpgp-cert-d-0.1+default-dev
librust-sequoia-cert-store-0.2+default-dev
retitle 1032446 rust-brotli fails to build with std and unsafe features enabled
together
thanks
Would it be possible to consider addressing the compilation errors or
the package removal?
The compile errors only happen when both the "std" (enabled by default)
and "unsafe" (disabled by default
Package: python3-django-hyperkitty
Followup-For: Bug #1031928
Control: severity -1 normal
next attempt ...
--
_ | Peter J. Holzer| Story must make more sense than reality.
|_|_) ||
| | | h...@hjp.at |-- Charles Stross, "Creative writing
__/ |
Package: python3-django-hyperkitty
Version: 1.3.4-4
Severity: normal
On 2023-03-02 20:30:04 +0100, Peter J. Holzer wrote:
> On 2023-03-02 19:53:12 +0100, Peter J. Holzer wrote:
> > So it seems that my suspicion that {% compress js %}...{% endcompress %}
> > wasn't working properly was correct. But of course that raises the
> > question
On 2023-03-03 11:57:14 +, James Addison wrote:
> Package: python3-django-hyperkitty
> Followup-For: Bug #1031928
> X-Debbugs-Cc: h...@hjp.at
>
> Hi Peter - one more thought from me:
>
> Would you be willing to send your patch to the upstream hyperkitty project[1]
>
Raised upstream
https://github.com/trialuser02/qt6ct/issues/25
I've noticed that the font settings are saved if one just hits [OK],
but lost if one hits [Apply] first.
On 2023-03-02 19:53:12 +0100, Peter J. Holzer wrote:
> So it seems that my suspicion that {% compress js %}...{% endcompress %}
> wasn't working properly was correct. But of course that raises the
> question why that would fail on one system and work on another. I'll
> inv
On 2023-03-02 01:32:55 +, James Addison wrote:
> Package: python3-django-hyperkitty
> Followup-For: Bug #1031928
> X-Debbugs-Cc: h...@hjp.at
> Control: tags -1 moreinfo
>
> Hi Peter,
>
> I'd like to gain some experience with configuring email infrastructure, and
Package: linphone-cli
Version: 4.4.21-2
Severity: important
X-Debbugs-Cc: pe...@easthope.ca
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempted to use linphone-cli. Command linphonec.
* What e
Package: python3-django-hyperkitty
Version: 1.3.4-4
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
I set up mailman3 including the web interface and the hyperkitty
archiver with Apache2 and a test mailing list.
Upon accessing the archive at
https:///mailman3
At the time you wrote this, i think the sq package description was
pretty similar to what it is today:
It looks like the description we have today was written when sq was
first packaged, but wasn't actually incorporated into the package
until later because of https://bugs.debian.org/cgi-bin/bugr
On Tue, Feb 21, 2023 at 12:39:53AM +0200, Peter Pentchev wrote:
> On Mon, Feb 20, 2023 at 05:23:28PM -0500, Boyuan Yang wrote:
> > Hi,
> >
> > 在 2023-02-21星期二的 00:38 +0530，Nilesh Patra写道：
> > > On Fri, 17 Feb 2023 07:51:48 +0100 Lucas Nussbaum
> > >
s?
Oof. Sorry about that. I guess I didn't consider the python-zstandard
package at all until now.
As I am a member of both the pkg-rpm and pkg-python teams, I could try to
update the packages in sync from now on, possibly adding something like
Breaks: python-zstandard (<< version-I-a
pload.
+
+ [ Jochen Sprickerhof ]
+ * Add patch to fix FTBFS on i386.
+Thanks to Adrian Bunk (Closes: 1004869)
+ * Use execute_after_ in d/rules
+ * Set R³ in d/control
+
+ -- Peter Michael Green Sun, 19 Feb 2023 00:50:57 +
+
python-xarray (2023.01.0-1) unstable; urgency=medium
this issue:
https://github.com/yt-dlp/yt-dlp/commit/149eb0bbf34fa8fdf8d1e2aa28e17479d099e26b
Best regards,
Peter
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-3-amd64 (SMP w/16 C
is a problem which was introduced by fuse3 3.13.1. A fix has
been provided by upstream:
https://github.com/libfuse/libfuse/commit/d7560cc9916b086bfe5d86459cc9f04033edd904
Best regards,
Peter
s I do the rebuilding manually and then upload
binaries+source. The binaries can rebuild the sources, but the old binaries
cannot.
Is this setup still supported with the new rules or is this the last hurrah
from the cmucl package?
Best regards, Peter
I'll raise it upstream.
==
On 15/02/2023 00:22, Christopher Cramer wrote:
qt5ct does not work either.
Working fine here, I suggest you raise that as a separate bug.
Cheers,
Peter
I recently became aware that mumble's build-dependencies were no longer
satisfiable on armhf due to a missing zeroc-ice. I looked at the build
logs for zeroc-ice and all were green. So I looked at the removal log
and found the following.
[Date: Sun, 12 Feb 2023 17:56:51 -] [ftpmaster: Scott
please package versione 0.13.0 of rust-asn1.
It's a semver bump, which given how dependencies are typically specified
in the rust world probablly counts as a transition. Unfortunately upstream
doesn't provide a changelog so it's difficult for me to tell how
substantial the changes actually are.
On 09/02/2023 23:43, Michele Martone wrote:
On 20230209@17:50, Peter Green wrote:
Package: librsb
Version: 1.3.0.2+dfsg-1
Tags: bookworm, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
User
for you?"
and
"One further thought.
I assume you are using TrueType fonts.
Which specific font(s) are you having the issue with?
I'm using liberation fonts here. {fonts-liberation2}"
Regards,
Peter B
The following packages have unmet dependencies:
librust-rspotify-dev : Depends: librust-base64-0.12+default-dev
Depends: librust-itertools-0.9+default-dev
Depends: librust-rand-0.7+default-dev
Depends: librust-reqwest-0.9+de
The following packages have unmet dependencies:
librust-rust-code-analysis-dev : Depends: librust-petgraph-0.5+default-dev
Depends: librust-phf-0.8+default-dev
Depends: librust-phf-0.8+macros-dev
reopen 1007026
thanks
* Revert to nom 4, porting to nom 7 seems to be non-trivial and I do not
want to further increase the proliferation of nom versions in Debian.
As I said in the initial mail, I did indeed patch weedle to revert
to nom 4. However in doing so I caused an API break. As
Package: librsb
Version: 1.3.0.2+dfsg-1
Tags: bookworm, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable
librsb build-depends on coccinelle which appears to have been removed
on armh
Package: rust-sequoia-keyring-linter
Version: 1.0.0-1
Severity: serious
rust-rpassword was recently updated to version 6.x, but sequoia-keyring-linter
still depends on version 5.x. I have checked crates.io and upstream git, and
there does not appear to be an upstream patch available.
on bumping
Package: initramfs-tools
Version: 0.140
Severity: normal
X-Debbugs-Cc: peter.na...@kit.edu
Dear Maintainer,
when using uboot ... update-initramfs triggers flash-kernel to _always_
write latest kernel version into flash-memory.
Even if this might be helpful in many cases ... there are situations
Package: wnpp
Severity: wishlist
Owner: Peter Pentchev
X-Debbugs-Cc: debian-de...@lists.debian.org, team+pyt...@tracker.debian.org,
r...@debian.org
* Package name: python-parse-stages
Version : 0.1.1
Upstream Contact: Peter Pentchev
* URL : https://gitlab.com
Package: wnpp
Severity: wishlist
Owner: Peter Pentchev
X-Debbugs-Cc: debian-de...@lists.debian.org, team+pyt...@tracker.debian.org,
r...@debian.org
* Package name: python-test-stages
Version : 0.1.1
Upstream Contact: Peter Pentchev
* URL : https://gitlab.com
tatic
OR TARGET zstd::libzstd_shared )
...
/<>/cmake/FindWrapZSTD.cmake(28): if(TARGET zstd::libzstd_static )
/<>/cmake/FindWrapZSTD.cmake(29): set(zstdtargetsuffix _static )
...
So qt6-base's cmake/FindWrapZSTD.cmake file asks CMake about the zstd
configuration, then correctly
I also tried a newer kernel version e.g.
* 5.19.0-0.deb11.2-marvell
* 6.0.0-0.deb11.6-marvell
which does not solve the problem - kernel Warning during boot is still
there.
New Upstream version
Package name : c-evo-dh
Version : 1.7-1
Upstream contact : Peter
URL : https://sourceforge.net/projects/c-evo-eh/
License : CC-BY-3.0, CC-BY-SA-3.0-US, CC0-1.0, GPL-2+
Vcs : https://salsa.debian.org/PeterB/c
Package: xraylib
While working on the python 3.11 transition in raspbian bookworm I ran
into a build failure of xraylib. I went and checked Debian reproducible
builds and found failures there too on armhf and i386 but not on arm64
or amd64. I also looked at the official build logs for Debian armh
Please consider enabling feature socks now: Package rust-socks is now in Debian.
The socks feature of rust-reqwest depends on the tokio-socks crate, not the
socks
crate.
I found that the kernel warning disappears when I prevent the modules
*xhci_pci* and *xhci_hcd* from being loaded during boot.
Package: dask.distributed
Version: 2022.12.1+ds.1-1
Severity: serious
X-debbugs-cc:
pkg-grass-de...@lists.alioth.debian.org,debian-science-maintain...@lists.alioth.debian.org
The autopkgtest for dask.distributed is failing.
https://ci.debian.net/data/autopkgtest/testing/amd64/d/dask.distributed
Package: dgit
mkdir dgittest
cd dgittest
dget -d
http://deb.debian.org/debian/pool/main/p/python-coverage/python-coverage_6.5.0+dfsg1-2.dsc
mkdir repo
cd repo
git init
dgit import-dsc ../python-coverage_6.5.0+dfsg1-2.dsc +workingbranch
Dgit metadata in .dsc: NO git hash
using existing python-co
Package: pushpin
Version: 1.36.0-1
Severity: serious
The new version of pushpin added a dependency on jsonwebtoken,
unfortunately jsonwebtoken depends in ring, which is only available
on x86* and arm*. There is work upstream to make ring more
portable but it seems unlikely to feature in a stable
sudo service mailman3-web start
fixed it.
--
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW
Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm.
701 - 800 of 7652 matches
Mail list logo
