How to build circular dependant packages in debian
Hi, How build a package A where it has a circular dependent package B (where package B is depend on package A). Regards, Danishka
Re: How to build circular dependant packages in debian
On Sat, Sep 18, 2021 at 02:17:59PM +0530, open infra wrote: > Hi, > > How build a package A where it has a circular dependent package B (where > package B is depend on package A). It depends. Do you have a question about specific packages? And why do you need to build them? -- WBR, wRAR signature.asc Description: PGP signature
Re: How to build circular dependant packages in debian
On 2021-09-18 14:17 +0530, open infra wrote: >Hi, >How build a package A where it has a circular dependent package B (where >package B is depend on package A). Once they are both in the archive it's not a problem. You just specifiy the dependencies and build each against the version of the other currently in the archive. For the initial bootstrap you can use whatever local bootstrap is expedient, then do binary uploads of one before a normal source upload of the other. It's a good idea to encode the bootstrap into the package dependencies if you can, e.g. if a build excluding some feature removes the circular dependency in a package, so you can do that minimal build of A first, then build B then build 'full' A. This is what 'build profiles' are for: https://wiki.debian.org/BuildProfileSpec Doing this keeps debian bootstrappable for new architectures, and helps you if you need to re-do the bootstrap of the pair again (e.g due to major api changes in both packages together). We don't have a way of doing a profiled build in the archive, but you can upload a version of A that forces the minimal build (and doesn't mention the 'B' dependency), let that build, then upload B and (once built OK) upload a full A. Sometimes people use 'foo-bootstrap' package names so that the minimal and full versions of a package can be distinguished. HTH Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Bug#994594: ITP: time-decode -- timestamp decoder and converter
Package: wnpp Severity: wishlist Owner: Jan Gru X-Debbugs-Cc: debian-devel@lists.debian.org, debian-security-to...@lists.debian.org * Package name: time-decode Version : 3.1.1 Upstream Author : Corey Forman * URL : https://github.com/digitalsleuth/time_decode * License : MIT Programming Lang: Python Description : timestamp decoder and converter time-decode provides the functionality to decode various timestamps and UUIDs to aid digital forensics and incident response processes. The supported formats range from common ones, like Unix epochs, WebKit/Chrome timestamps and Microsoft's FILETIME to more exotic formats like LDAP/Active Directory timestamps and Metasploit payload UUIDs. In addition, even timestamps used by some social media services, like Twitter, are included. ** Relevance of the package In most DFIR investigations temporal information is particularly important. Analysts often stumble over various timestamps and need to convert and normalize them quickly. While toolkits like plaso can help with the normalization of logfiles in bulk, Debian's package archives lack tooling for the convenient conversion of single timestamps of either known or unknown format. Given this finding and my experience from using it, time-decode seems to be an valuable prospective package to round off Debian's collection of forensic tools. ** Maintainenace plan I suggest to maintain time-decode inside the pkg-security-team's repository on salsa, since most of the packages related to forensics live there. However, I am looking for a sponsor for this package - ideally a member of the pkg-security-team.
Re: How to build circular dependant packages in debian
On Sat, Sep 18, 2021 at 02:17:59PM +0530, open infra wrote: > How build a package A where it has a circular dependent package B (where > package B is depend on package A). You try not to, at all costs. Bastian -- A woman should have compassion. -- Kirk, "Catspaw", stardate 3018.2
Bug#994607: ITP: python-pytest-xprocess -- pytest plugin for managing processes across test runs
Package: wnpp Severity: wishlist Owner: Thomas Goirand X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: python-pytest-xprocess Version : 0.18.1 Upstream Author : Holger Krekel * URL : https://github.com/pytest-dev/pytest-xprocess/ * License : Expat Programming Lang: Python Description : pytest plugin for managing processes across test runs Pytest has for objective to allow the developers to limit the boilerplate code around the tests, promoting the use of built-in mechanisms such as the assert keyword. . Pytest-xprocess is a pytest plugin for managing processes across test runs.
Bug#994609: ITP: python-exhale -- Sphinx automated C++ API generation support
Package: wnpp Severity: wishlist Owner: Timo Röhling X-Debbugs-Cc: debian-devel@lists.debian.org, roehl...@debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-exhale Version : Upstream Author : Stephen McDowell * URL : https://exhale.readthedocs.io/en/latest/ * License : BSD-3-Clause Programming Lang: Python Description : Sphinx automated C++ API generation support Exhale is a Sphinx extension that depends on the excellent Breathe extension which enables parsing Doxygen documentation into the Sphinx domain. Exhale provides a layer of automation, enabling launching Doxygen and generating the full website all from your conf.py. This package is a new dependency of CycloneDDS 0.8.0. I will package and maintain it as part of the Python Team. -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmFF7RkACgkQ+C8H+466 LVnUuwwApQrc5TjTguqoBw/Ssne1Zet6IW6m7ojoiuznb23FF60nIyV7duzsuNQq 7l9+pD72tKCTAtD/6y8FiBysIWgCbbdMhcABMG3lptJ2dmZJgrD6mOOKXEecb+y7 ieaFbmzYE2meysXb7nHd/wfg3JGzjsMfZrpRPiTnX5B0vJ6v56vYPOSwsga15OVJ n8u9XkAjPypw7jDcxgmWxmOAtk4c4iHu0SlWRnXnLDfXIC/TMboCAhvV6EeuLK38 PJHYuM+2a4EgBIaXn1wz/ZDetBhrwon42fRVAaTE/V2uH08N+uYPn3KrTHMVfp7d 4BJ46dCAyXI7uXCZY4PVs7UUps0Q1MmX51dY49OQeX71ysX//7hj0q/REsiT1FKo SboUviunhR6dILXuBY1RZr4Qo3inqCboqRuPaduVQnw4iFEbk9iEGJhcCym0Z+Xy QrwocIW1Elw43xZ7cCUXVKUQ4AibcytP3YOL2e5ZL66QCOXwCon73ijuQEbUhv03 F8kTmf9Y =rUKn -END PGP SIGNATURE-
Re: How to build circular dependant packages in debian
On 2021-09-18 13:59:17 +0500 (+0500), Andrey Rahmatullin wrote: > On Sat, Sep 18, 2021 at 02:17:59PM +0530, open infra wrote: > > How build a package A where it has a circular dependent package > > B (where package B is depend on package A). > > It depends. Do you have a question about specific packages? And > why do you need to build them? As I understand it, the context here is bootstrapping a new "edge networking" focused Debian derivative with a number of third-party patches to existing source packages: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-September/012058.html https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008846_debian_build.html In this particular case, because it's not a full-blown port to a new processor architecture or anything, it seems like it shouldn't all need to be bootstrapped entirely from scratch. Ideally, many of the build dependencies could be satisfied initially from unadulterated packages already available in Debian, and then replaced with custom patched versions once any problem dependency cycles have been broken. -- Jeremy Stanley signature.asc Description: PGP signature
Bug#994620: ITP: python3-fbtftp -- fbtftp is Facebook's implementation of a dynamic TFTP server framework. It lets you create custom TFTP servers and wrap your own logic into it in a very simple manne
Package: wnpp Severity: wishlist Owner: Luiz Amaral X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: python3-fbtftp Version : 0.5 Upstream Author : Angelo Failla * URL : https://github.com/facebook/fbtftp/ * License : (MIT) Programming Lang: (Python) Description : fbtftp is Facebook's implementation of a dynamic TFTP server framework. It lets you create custom TFTP servers and wrap your own logic into it in a very simple manner. python3-fbtftp is a dependency of a TFTP proxy built by me that is used to provision hardware at our datacenter. We currently build it internally and publish it on our internal repository, but I figured this would be a nice opportunity to get started with official Debian Packaging. I need a sponsor for this package.
Bug#994625: ITP: carl9170fw -- libre firmware for AR9170 USB wireless adapters
Package: wnpp Severity: wishlist Owner: John Scott X-Debbugs-Cc: debian-devel@lists.debian.org, debian-ker...@lists.debian.org Control: block -1 by 986778 Control: block 890601 by -1 Control: affects -1 linux-firmware-free * Package name : carl9170fw Version : 1.9.9-399-gcd480b9 Upstream Author : Linux wireless maintainers * URL : https://github.com/chunkeey/carl9170fw * License : mostly GPLv2-only Programming Lang: C Description : libre firmware for AR9170 USB wireless adapters This is carl9170, the libre firmware for Qualcomm Atheros's AR9170 802.11n USB wireless adapters that complements the carl9170 Linux driver. carl9170 is already shipped in firmware-linux-free, but the primary objective of transitioning it into this new source package is to get it building from source. This is possible with the SuperH bare-metal cross toolchain I'm packaging. I will need sponsorship for this package (and am currently seeking sponsors for the cross toolchain too); the Kernel Team may help with the former. Regardless, co-maintainers/uploaders are welcome and I'd be glad to help prospective contributors get adapters, as they can be a little tricky to find. signature.asc Description: This is a digitally signed message part
Bug#994629: ITP: tml -- tiny tool and go library for markup language for terminal output
Package: wnpp Severity: wishlist Owner: Nobuhiro Iwamatsu * Package name: tml Version : 0.4.0 Upstream Author : Liam Galvin * URL : https://github.com/liamg/tml * License : public-domain Programming Lang: Go Description : tiny tool and go library for markup language for terminal output A Go library and standalone binary to make the output of coloured/formatted text in the terminal easier and more readable.
Bug#994630: ITP: golang-github-knqyf263-go-apk-version -- A golang library for parsing apk package versions
Package: wnpp Severity: wishlist Owner: Nobuhiro Iwamatsu * Package name: golang-github-knqyf263-go-apk-version Version : 0.0~git20200609.041fdbb Upstream Author : Teppei Fukuda * URL : https://github.com/knqyf263/go-apk-version * License : Apache-2.0 Programming Lang: Go Description : A golang library for parsing apk package versions go-apk-version is a golang library for parsing and comparing versions for apk.
Re: How to build circular dependant packages in debian
On Sat, Sep 18, 2021 at 8:48 AM open infra wrote: > How build a package A where it has a circular dependent package B (where > package B is depend on package A). Jeremy Stanley pointed out that this is for the StarlingX project, please consider merging StarlingX changes back to Debian and our upstream projects and contributing new packages back into Debian itself. https://lists.debian.org/msgid-search/20210918143436.55h6b2i2z6hpp...@yuggoth.org http://lists.starlingx.io/pipermail/starlingx-discuss/2021-September/012058.html https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008846_debian_build.html https://mentors.debian.net/intro-maintainers As others have pointed out, build profiles are the answer for resolving circular build dependencies. -- bye, pabs https://wiki.debian.org/PaulWise
Re: How to build circular dependant packages in debian
On Sat, Sep 18, 2021 at 2:35 PM Jeremy Stanley wrote: > As I understand it, the context here is bootstrapping a new "edge > networking" focused Debian derivative with a number of third-party > patches to existing source packages: Thanks for pointing this out, asked them to contribute back to Debian. > http://lists.starlingx.io/pipermail/starlingx-discuss/2021-September/012058.html Hmm, this site has a confusing way of not supporting https. > In this particular case, because it's not a full-blown port to a new > processor architecture or anything, it seems like it shouldn't all > need to be bootstrapped entirely from scratch. Ideally, many of the > build dependencies could be satisfied initially from unadulterated > packages already available in Debian, and then replaced with custom > patched versions once any problem dependency cycles have been > broken. As others have pointed out, this seems like the exact use-case for build profiles. -- bye, pabs https://wiki.debian.org/PaulWise
Re: How to build circular dependant packages in debian
Hi Jeremy, Yes, this is about use of Debian builds in the starlingx. Regards, Danishka On Sat, Sep 18, 2021 at 8:05 PM Jeremy Stanley wrote: > On 2021-09-18 13:59:17 +0500 (+0500), Andrey Rahmatullin wrote: > > On Sat, Sep 18, 2021 at 02:17:59PM +0530, open infra wrote: > > > How build a package A where it has a circular dependent package > > > B (where package B is depend on package A). > > > > It depends. Do you have a question about specific packages? And > > why do you need to build them? > > As I understand it, the context here is bootstrapping a new "edge > networking" focused Debian derivative with a number of third-party > patches to existing source packages: > > > http://lists.starlingx.io/pipermail/starlingx-discuss/2021-September/012058.html > > > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008846_debian_build.html > > In this particular case, because it's not a full-blown port to a new > processor architecture or anything, it seems like it shouldn't all > need to be bootstrapped entirely from scratch. Ideally, many of the > build dependencies could be satisfied initially from unadulterated > packages already available in Debian, and then replaced with custom > patched versions once any problem dependency cycles have been > broken. > -- > Jeremy Stanley >
