Re: Strange armel build error
On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: > Or just exclude that architecture i. e., list all archs but armel? If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel package in testing. That will allow the package to migrate even if armel is missing. Regards, Stephen pgpeskC3WTzHw.pgp Description: OpenPGP digital signature
Bug#1078949: ITP: golang-github-http-wasm-http-wasm-host-go -- HTTP middleware libraries implemented by http-wasm WebAssembly Guest modules
Package: wnpp Severity: wishlist Owner: Aloïs Micard * Package name: golang-github-http-wasm-http-wasm-host-go Version : 0.6.0-1 Upstream Author : http-wasm * URL : https://github.com/http-wasm/http-wasm-host-go * License : Apache-2.0 Programming Lang: Go Description : HTTP middleware libraries implemented by http-wasm WebAssembly Guest modules This package is required for Traefik. Cheers,
Re: Strange armel build error
Hi Stephen, On 18/08/2024 09:04, Stephen Kitt wrote: On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: Or just exclude that architecture i. e., list all archs but armel? If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel package in testing. That will allow the package to migrate even if armel is missing. This looks to me like a sound solution in this case. After all, opencpn is a full-fledged GUI leaf package without reverse deps and zero users on armel hardware. But then again, how is this done? --alec
Bug#1078950: ITP: wazero -- wazero: the zero dependency WebAssembly runtime for Go developers
Package: wnpp Severity: wishlist Owner: Aloïs Micard * Package name: wazero Version : 1.8.0-1 Upstream Author : Tetrate Labs * URL : https://github.com/tetratelabs/wazero * License : Apache-2.0 Programming Lang: Go Description : wazero: the zero dependency WebAssembly runtime for Go developers wazero: the zero dependency WebAssembly runtime for Go developers . wazero is a WebAssembly Core Specification 1.0 (https://www.w3.org/TR/2019/REC-wasm-core-1-20191205/) and 2.0 (https://www.w3.org/TR/2022/WD-wasm-core-2-20220419/) compliant runtime written in Go. It has *zero dependencies*, and doesn't rely on CGO. This means you can run applications in other languages and still keep cross compilation. . wazero's 1.0 release (https://tetrate.io/blog/introducing-wazero-from- tetrate/) happened in March 2023, and is in use (https://wazero.io/community/users/) by many projects and production sites. . This is a indirect dependency of Traefik. It is also a wonderful runtime for WASM. Cheers.
Re: Strange armel build error
On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: > Hi Stephen, > > On 18/08/2024 09:04, Stephen Kitt wrote: > > On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas > > wrote: > > > Or just exclude that architecture i. e., list all archs but armel? > > If you can’t fix the build, you don’t need to exclude the architecture — you > > can ask for removal of the armel package in testing. That will allow the > > package to migrate even if armel is missing. > > > This looks to me like a sound solution in this case. After all, opencpn is a > full-fledged GUI leaf package without reverse deps and zero users on armel > hardware. But then again, how is this done? If by this you mean asking for a removal then reportbug release.debian.org -- WBR, wRAR signature.asc Description: PGP signature
Re: Strange armel build error
On Sun, 2024-08-18 at 14:23 +0500, Andrey Rakhmatullin wrote: > On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: > > Hi Stephen, > > > > On 18/08/2024 09:04, Stephen Kitt wrote: > > [...] > > > If you can’t fix the build, you don’t need to exclude the > > > architecture — you > > > can ask for removal of the armel package in testing. That will > > > allow the > > > package to migrate even if armel is missing. > > > > > This looks to me like a sound solution in this case. After all, > > opencpn is a > > full-fledged GUI leaf package without reverse deps and zero users > > on armel > > hardware. But then again, how is this done? > > If by this you mean asking for a removal then reportbug > release.debian.org Not for an architecture-specific removal. Those happen in unstable and then propagate to testing, so it's ftp.debian.org. Regards, Adam
Re: Strange armel build error
Hi; On 18/08/2024 06:11, Wookey wrote: On 2024-08-17 17:58 +0200, Alec Leamas wrote: To make it more interesting, the simple -latomic fix doesn't seem to cut it That's a pity, it sounds plausible. I'll try to take a look. Thanks! That said, unless you have oceans of time, perhaps it might make sense to follow Stephen's "exclude from testing" path. > To me, the reasonable approach would be to inform the porter list (need to > figure out which) and then disable armel for now. As soon as there is a > solution I could and should upload it. Sent a message to debian-...@lists.debian.org, not yet in the archives. Making an upload disabling armel i. e., listing all working archs besides armel for now. Cheers! --alec
Re: Strange armel build error
Hi list, On 18/08/2024 11:23, Andrey Rakhmatullin wrote: On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: Hi Stephen, On 18/08/2024 09:04, Stephen Kitt wrote: On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: Or just exclude that architecture i. e., list all archs but armel? If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel package in testing. That will allow the package to migrate even if armel is missing. This looks to me like a sound solution in this case. After all, opencpn is a full-fledged GUI leaf package without reverse deps and zero users on armel hardware. But then again, how is this done? If by this you mean asking for a removal then reportbug release.debian.org I do. But I am new enough to not really understand what "reportbug release.debian.org" means... --alec
Re: Strange armel build error
On 8/18/24 11:23 AM, Andrey Rakhmatullin wrote: On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: On 18/08/2024 09:04, Stephen Kitt wrote: On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: Or just exclude that architecture i. e., list all archs but armel? If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel package in testing. That will allow the package to migrate even if armel is missing. This looks to me like a sound solution in this case. After all, opencpn is a full-fledged GUI leaf package without reverse deps and zero users on armel hardware. But then again, how is this done? If by this you mean asking for a removal then reportbug release.debian.org Better file an RM bugreport for unstable against ftp.debian.org, that also gets the package removed from testing once its gone from unstable. And your package no longer blocks transitions of its dependencies for which it gets rebuilt in unstable. See also: https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#removing-packages https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#removals-from-testing Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Re: Strange armel build error
On 18/08/2024 11:35, Adam D. Barratt wrote: On Sun, 2024-08-18 at 14:23 +0500, Andrey Rakhmatullin wrote: On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: [...]-- If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel package in testing. That will allow the package to migrate even if armel is missing. This looks to me like a sound solution in this case. After all, opencpn is a full-fledged GUI leaf package without reverse deps and zero users on armel hardware. But then again, how is this done? If by this you mean asking for a removal then reportbug release.debian.org Not for an architecture-specific removal. Those happen in unstable and then propagate to testing, so it's ftp.debian.org. Ah... there is a reportbug utility which is useful here. New discoveries every day. Filed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078953 Cheers! --alec
Re: Accepting DEP14?
Il 17/08/2024 12:00, Jonas Smedegaard ha scritto:
Quoting Fabio Fantoni (2024-08-17 11:20:01)
Il 17/08/2024 10:47, Jonas Smedegaard ha scritto:
Hi Chris,
Quoting Chris Hofstaedtler (2024-08-17 10:17:19)
On Fri, 16 Aug 2024 23:36:31 +0200, gregor herrmann wrote:
IMO, and from discussions in the Debian Perl Group, the blocker is
the conversion of existing repos, both on salsa (which should be
doable via the API as suggested in the sketches mentioned above) and
also locally for hundreds of developer machines [git fails horribly
on the upstream/ → upstream/latest change].
I want to echo this pain. When changing the layout it seems almost
better to start from scratch.
I have in the past found it confusing how to handle it, but now I find
it tolerable (and don't recognize the "better to start from scratch"
judgement), after I figured out (as also hinted at in one of the links
by gregor) that you need to do the following, in that order:
1. unlock branch "upstream" on salsa
2. rename branch "upstream" → "upstream/latest" on salsa (or delete it)
rename branch in salsa would be very handy, i searched for it when i
converted some repositories but i didn't find it, can you tell me how to
do it please?
I cannot (I sloppily drop the branch and the republish a moment later),
but please see the links mentioned by Gregor.
- Jonas
I tried using salsa cli tool from Gregor link but rename of upstream
branch failed.
I did this trying on one project:
salsa --group cinnamon-team protect_branch xapp master no
salsa --verbose --group cinnamon-team rename_branch xapp
--source-branch=master --dest-branch=debian/latest
# this failed to delete master, changed default branch from salsa
website (in Settings->Repository) and deleted master branch (from website)
salsa --group cinnamon-team protect_branch xapp debian/latest m d
# after these the conversion from master to debian/latest seems correct,
rename of upstream branch instead fails
salsa --verbose --no-fail --group cinnamon-team rename_branch xapp
--source-branch=upstream --dest-branch=upstream/latest
salsa info: cinnamon-team id is 2992
salsa info: Project xapp => cinnamon-team/xapp
salsa info: cinnamon-team/xapp id is 17710
salsa info: Configuring xapp
salsa warn: Branch rename has failed for xapp
salsa info: Error POSTing
https://salsa.debian.org/api/v4/projects/17710/repository/branches (HTTP
400): Bad Request {"message":"Failed to create branch 'upstream/late...
at /usr/share/perl5/Devscripts/Salsa/rename_branch.pm line 26.
Error above on Sid with devscripts 2.23.7 but I tried also on older system
Someone had rename of upstream branch working?
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1078992: ITP: pacman.c -- simple Pacman clone
Package: wnpp Severity: wishlist Owner: Alex Myczko X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: pacman.c Version : 0+git20240818+ds Upstream Authors: Andre Weissflog URL : https://github.com/floooh/pacman.c * License : MIT Description : simple Pacman clone This is a Pacman clone written in C99 with minimal dependencies.
Bug#1078993: ITP: golang-github-mimuret-golang-iij-dpf -- IIJ DNS Platform Service API for Go
Package: wnpp Severity: wishlist Owner: Aloïs Micard * Package name: golang-github-mimuret-golang-iij-dpf Version : 0.9.1-1 Upstream Author : Manabu Sonoda * URL : https://github.com/mimuret/golang-iij-dpf * License : Expat Programming Lang: Go Description : IIJ DNS Platform Service API for Go IIJ DNS Platform Service API for Go . This package is needed for Traefik. Cheers,
Bug#1078999: ITP: golang-github-desertbit-timer -- Go Timer implementation with a fixed Reset behavior
Package: wnpp Severity: wishlist Owner: Aloïs Micard * Package name: golang-github-desertbit-timer Version : 1.0.1-1 Upstream Author : DesertBit * URL : https://github.com/desertbit/timer * License : Expat Programming Lang: Go Description : Go Timer implementation with a fixed Reset behavior Go Timer implementation with a fixed Reset behavior . This package is needed for Traefik. Cheers,
Bug#1079002: ITP: golang-uber-ratelimit -- A Go blocking leaky-bucket rate limit implementation
Package: wnpp Severity: wishlist Owner: Aloïs Micard * Package name: golang-uber-ratelimit Version : 0.3.1-1 Upstream Author : Uber Go * URL : https://github.com/uber-go/ratelimit * License : Expat Programming Lang: Go Description : A Go blocking leaky-bucket rate limit implementation This package provides a Golang implementation of the leaky-bucket rate limit algorithm. This implementation refills the bucket based on the time elapsed between requests instead of requiring an interval clock to fill the bucket discretely. . This is required to package Traefik. Cheers,
Bug#1079011: ITP: marknote -- Simple markdown note management app.
Package: wnpp Severity: wishlist Owner: Vincent Pinon X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: marknote Version : 1.3.0 Upstream Contact: Mathis Brüchert * URL : https://invent.kde.org/office/marknote * License : GPL Programming Lang: C++ Description : Simple markdown note management app. It supports a wide range of formating options useful for taking every day notes, like bold, italic, underlined and strike through fonts as well as headings, lists, check boxes, images and more. I'm using it after trying several other markdown editors and note taking apps and like it: it's light, nice and does the job. I'm ready to maintain for the forseable future, with the Qt/KDE team.
Bug#1079016: ITP: golang-github-dnsimple-dnsimple-go -- The DNSimple API client for Go.
Package: wnpp Severity: wishlist Owner: Aloïs Micard * Package name: golang-github-dnsimple-dnsimple-go Version : 2.0.0-1 Upstream Author : DNSimple * URL : https://github.com/dnsimple/dnsimple-go * License : Expat Programming Lang: Go Description : The DNSimple API client for Go. A Go client for the DNSimple API v2 (https://developer.dnsimple.com/v2/). . This package is required for Traefik. Cheers,
debian/gbp.cnf analytics? (Re: Re: Accepting DEP14?)
Hi! I am happily using debian/gbp.conf and debian-branch=debian/latest in all of my packages but based on the DEP14 discussion seems some people prefer debian/sid or debian/unstable (and some of them upload to experimental from the branch despite the name, and some maintain a separate debian/experimental branch for experimental uploads). However this the responses are just a sample based on who happens to have time to read debian-devel@ discussions. I tried to use codesearch.debian.net to find out how many packages have a debian/gbp.conf but it seems it can't be used to simply list packages that have a specific file, it always also needs a search terms to look up inside the file. With https://codesearch.debian.net/search?q=path%3Adebian%2Fgbp.conf+debian-branch+%3F%3D+%3Fdebian%2Flatest&literal=0 I was able to find that 1655 packages have either "debian-branch = debian/latest" or "debian-branch=debian/latest". Is there some easy way to iterate every single Debian package and extract just one single file from them without having to download all packages? I'd like to see how many % of all Debian packages have a gbp.conf file, and then download all of them to do stats on what they contain. - Otto
Re: debian/gbp.cnf analytics? (Re: Re: Accepting DEP14?)
Quoting Otto Kekäläinen (2024-08-19 03:45:37) > I tried to use codesearch.debian.net to find out how many packages have a > debian/gbp.conf but it seems it can't be used to simply list packages that > have a specific file, it always also needs a search terms to look up inside > the file. > > With > https://codesearch.debian.net/search?q=path%3Adebian%2Fgbp.conf+debian-branch+%3F%3D+%3Fdebian%2Flatest&literal=0 > I was able to find that 1655 packages have either "debian-branch = > debian/latest" or "debian-branch=debian/latest". > > Is there some easy way to iterate every single Debian package and > extract just one single file from them without having to download all > packages? > > I'd like to see how many % of all Debian packages have a gbp.conf file, and > then download all of them to do stats on what they contain. finding out which package contains a given file is better done via the Contents files from our mirrors. The apt-file tool provides an easy interface to search these contents files and answer the question "which package contains a file or path that looks like this". By default, apt-file will only download (and search) Contents files for binary packages and not source packages. To change that, edit /etc/apt/apt.conf.d/50apt-file.conf and change DefaultEnabled from "false" to "true" in the section deb-src::Contents-dsc. Once that is done you run "apt update" to download the newly enabled Contents files and then you can run a search like this: $ apt-file --index-names dsc search debian/gbp.conf You need to add --index-names because the default value is "deb" and that would only search through binary packages. Thanks! cheers, josch signature.asc Description: signature
Re: debian/gbp.cnf analytics? (Re: Re: Accepting DEP14?)
Hi Otto Getting the list of source packages with a particular file in them can be done by apt-file (see "--index-names dsc"). sources.debian.org can provide single files - you need an API call to find the correct URL for the file first. I don't know if the service admins would get upset at 1655 files being downloaded in the following fashion. apt-file search --index-names dsc --package-only debian/gbp.conf | while read pkg; do echo -n $pkg url=$(curl -s https://sources.debian.org/api/src/zzuf/0.15-4/debian/gbp.conf/ | jq -r .raw_url) curl -s https://sources.debian.org/$url > $pkg echo . done (takes 1-2s per source package it seems) sources.d.o can also do lookups by file sha256sum. The simple 2-line gbp.conf that sets debian/master is in 183 source packages according to: https://sources.debian.org/api/sha256/?checksum=c4a26b58ec236eab6919435af0267c29840191a97beeb3caa4712e42a6d51be8 which might permit some pre-filtering of the list of packages to inspect. regards Stuart -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Re: debian/gbp.cnf analytics? (Re: Re: Accepting DEP14?)
For those playing along at home... On 19/08/2024 14:53, Stuart Prescott wrote: url=$(curl -s https://sources.debian.org/api/src/zzuf/0.15-4/debian/gbp.conf/ | jq -r .raw_url) The API URL should obviously be https://sources.debian.org/api/src/$pkg/latest/debian/gbp.conf/ and curl will also need -L to follow the redirect from 'latest' to the specific version: url=$(curl -sL https://sources.debian.org/api/src/$pkg/latest/debian/gbp.conf/ | jq -r .raw_url) -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#1079027: ITP: golang-github-infobloxopen-infoblox-go-client -- Infoblox NIOS WAPI Go Client library
Package: wnpp Severity: wishlist Owner: Aloïs Micard * Package name: golang-github-infobloxopen-infoblox-go-client Version : 2.7.0-1 Upstream Author : InfobloxOpen * URL : https://github.com/infobloxopen/infoblox-go-client * License : Apache-2.0 Programming Lang: Go Description : Infoblox NIOS WAPI Go Client library An Infoblox NIOS WAPI client library in Golang. The library enables us to do a CRUD operations on NIOS Objects. . This library is required for Traefik. Cheers,
