Bug#1065417: ITP: omd -- omd-ocaml
Package: wnpp Severity: wishlist Owner: Bo YU X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: omd Version : 2.0.0 Upstream Contact: a...@recoil.org * URL : https://github.com/ocaml/omd * License : ISC Programming Lang: OCaml Description : extensible Markdown library and tool in "pure OCaml" Omd is an OCaml library designed to parse, manipulate, and print Markdown into different formats. In addition to the library, a command-line tool omd is included to easily convert markdown into HTML. Omd aims for compliance with the CommonMark standard. We are currently compliant with 0.30 of the ComonMark spec. --->> This is a denpendency of sail[0]. [0]: https://github.com/rems-project/sail -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#1065419: ITP: sail-ocaml -- Sail architecture definition language
Package: wnpp Severity: wishlist Owner: Bo YU X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: sail-ocaml Version : 0.17.1 Upstream Contact: rems-project * URL : https://github.com/rems-project/sail * License : BSD-2-Clause Programming Lang: OCaml Description : Sail architecture definition language with OCaml Sail is a language for describing the instruction-set architecture (ISA) semantics of processors. Sail aims to provide a engineer-friendly, vendor-pseudocode-like language for describing instruction semantics. It is essentially a first-order imperative language, but with lightweight dependent typing for numeric types and bitvector lengths, which are automatically checked using Z3. Given a Sail definition, the tool will type-check it and generate documentation, executable emulators (in C and OCaml), theorem-prover definitions (for Isabelle, HOL4, and Coq), and definitions to integrate with our RMEM and isla-axiomatic tools for concurrency semantics. The Isla engine provides SMT-based symbolic evaluation for Sail models, and the Islaris verification tool integrates Isla output with the Iris program logic to support proof about binary code in Coq. Not all models are integrated with all tools - see the most recent papers and models for descriptions of the current state. >>>-- This is a denpendency of sail-riscv[0] and I will maintain it under Debian OCaml team. [0]: https://github.com/riscv/sail-riscv -- Regards, -- Bo YU signature.asc Description: PGP signature
Re: hardinfo rebooted as hardinfo2 - community edition - RELEASE 2.0.12
On Sun, Mar 03, 2024 at 09:25:41PM +0100, hwspeedy wrote: > Hi Simon Quiqley, (CC: debian-devel) > > I'm trying to figure out how to get the hardinfo2 - release 2.0.12 into > debian repository. > hardinfo2 is a community fork of hardinfo and should continue as hardinfo > package, currently maintained in debian by Simon Quiqley. Then the logical way forward is to ask Simon to switch the package to hardinfo2 and continue maintaining it (if they are still interested, as the last maintainer upload was in 2018). > Salvo Tomaselli suggested to do ITP Only if you want to package and maintain it yourself, and only if it should be a new package separate from the existing hardinfo one. > - But the pro's on "#debian-mentors on oftc" are so out of my league. - I am > missing the overview - eg. how to test the debian build system with packages If you want to make and maintain the package yourself you should start at https://mentors.debian.net/intro-maintainers > do I need a salsa git? No, it's just encouraged. > - Is this for project maintainers also? No, anyone can have a salsa account. > Why does CPack not work with debian build system I don't know if it can even generate source packages (generating a source package, let alone a proper Policy-compliant one, is likely out of scope for it), but even if it does, you still need to make it correct, Policy-compliant and uptodate. Making trivial source package is the easiest part of maintainership anyway. > - could a small script fix it > like: > https://github.com/hardinfo2/hardinfo2/blob/master/tools/create_debian_source.sh It doesn't really make sense to make a script that creates the initial source package as you only need to do that once. And no, you cannot just ship debmake results that you didn't even try to build. -- WBR, wRAR signature.asc Description: PGP signature
Re: New requirements for APT repository signing
Sune Vuorela dixit: >In theory. I don't know if there are any statistics on 'popular' >3rdparty repositories and their keys. But assuming they're doing key Hm. My own private repo should be ok (3072R), but my Launchpad PPAs incidentally are not okay (1024D). Since this comes from Canonical, they really should message all affected Launchpad users and tell them how to rotate their PPAs’ keys (I vaguely recall searching for that and not finding it once). bye, //mirabilos -- Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit gerechnet, darum bin ich blutverschmiert… wer konnte ahnen, daß SIE so reagier’n… gestern Nacht ist mein IRC-Netzwerk explodiert~~~ (as of 2021-06-15 The MirOS Project temporarily reconvenes on OFTC)
Re: New requirements for APT repository signing
On Mon, Mar 4, 2024 at 8:40 AM Thorsten Glaser wrote: > Hm. My own private repo should be ok (3072R), but my Launchpad PPAs > incidentally are not okay (1024D). > > Since this comes from Canonical, they really should message all > affected Launchpad users and tell them how to rotate their PPAs’ keys > (I vaguely recall searching for that and not finding it once). It is not possible to rotate your PPA keys yourself, but Canonical is handling it according to https://discourse.ubuntu.com/t/new-requirements-for-apt-repository-signing-in-24-04/42854 Thank you, Jeremy Bícha
Re: New requirements for APT repository signing
On Mon, Mar 04, 2024 at 07:47:08AM -, Sune Vuorela wrote: > In theory. I don't know if there are any statistics on 'popular' > 3rdparty repositories and their keys. I suspect src:extrepo-data is a good starting point for anyone interested in generating such statistics... -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ The moon landing 50 years ago was paid by taxes, while Bezos space trip was paid by not paying taxes. signature.asc Description: PGP signature
Bug#1065462: ITP: netconsd -- The Netconsole Daemon
Package: wnpp Severity: wishlist Owner: Michel Lind X-Debbugs-Cc: debian-devel@lists.debian.org, mic...@michel-slm.name * Package name: netconsd Version : 0.4 Upstream Contact: Dave Jones * URL : https://github.com/facebook/netconsd * License : BSD Programming Lang: C Description : The Netconsole Daemon This is a daemon for receiving and processing logs from the Linux Kernel, as emitted over a network by the kernel's netconsole module. It supports both the old "legacy" text-only format, and the new extended format added in v4.4. The core of the daemon does nothing but process messages and drop them: in order to make the daemon useful, the user must supply one or more "output modules". These modules are shared object files which expose a small ABI that is called by netconsd with the content and metadata for netconsole messages it receives.
Bug#1065468: ITP: python-rpcq -- RPC framework and message specification for Rigetti QCS
Package: wnpp Severity: wishlist Owner: Yogeswaran Umasankar X-Debbugs-Cc: debian-devel@lists.debian.org, kd8...@gmail.com * Package name: python-rpcq Version : 3.11.0 Upstream Contact: Rigetti Computing * URL : https://github.com/rigetti/rpcq * License : Apache-2.0 Programming Lang: Python Description : RPC framework and message specification for Rigetti QCS Asynchronous RPC client-server framework and message specification for Rigetti Quantum Cloud Services (QCS). Implements an efficient transport protocol by using ZeroMQ (ZMQ) sockets and MessagePack (msgpack) serialization. Not intended to be a full-featured replacement for other frameworks like gRPC or Apache Thrift. It is depend for other python packages such as pyquil. I planned to maintain it under DPT, and need sponsorship.
