Builds that pass locally but fail on sbuild? (Re: Reviving schroot as used by sbuild)

Hi Simon! > There are lots of options for doing this, some of which are listed in > . > > All of these have the same problem as cowbuilder, pbuilder, and any > other solution that is not sbuild + schroot: it isn't (currently) what > the

Re: Vendoring an unmaintained library?

Enriching original email: This is about whether packages transmission-gtk should use embedded copy of libb64 or depend on the outdated Debian package libb64. Upstream for libb64 seems dead and transmission devs have improved their embedded/vendored copy of libb64. Direct link: https://bugs.debia

Re: DD's, Debian Mentors needs you!

Hi! > https://mentors.debian.net/package/uriparser/ > https://mentors.debian.net/package/mailgraph/ This is the same maintainer, I can take this on. > https://mentors.debian.net/package/selint/ I have worked with this maintainer before, I can help him now too. After this Hexwalk still needs a

Re: GR: tag2upload

Hi! On Thu, 4 Jul 2024 at 13:32, Debian Project Secretary - Kurt Roeckx wrote: > A general resolution about tag2upload has been started. Details are at: > https://www.debian.org/vote/2024/vote_002 This GR was published without much context. I at least was much more enlightened after reading the

Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

Hi all, I have drafted a new DEP at https://salsa.debian.org/dep-team/deps/-/merge_requests/8 titled "DEP-18: Enable true open collaboration on all Debian packages". Direct link to raw text: https://salsa.debian.org/dep-team/deps/-/raw/798bfa5a1e1609afd4e48ee20aff80a82bcd4a2f/web/deps/dep18.mdwn

Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

Hi! > > I have drafted a new DEP at > > https://salsa.debian.org/dep-team/deps/-/merge_requests/8 titled "DEP-18: > > Enable true open collaboration on all Debian packages". > > > > Direct link to raw text: > > https://salsa.debian.org/dep-team/deps/-/raw/798bfa5a1e1609afd4e48ee20aff80a82bcd4a2f/w

Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

Hi! Thanks for the comments. Responding inline to the questions you raised: > Then it makes no effort to define communication channels. Before making some > time consuming change, it's usually better to just ask if that's a good idea .. > Then the document should enforce a particular commit style

Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

Hi! On Fri, 2 Aug 2024 at 02:27, Andrea Pappacoda wrote: .. > Before a certain way of doing things can be mandated or "warmly > recommended", the technology has to be as flawless as possible - and > today I wouldn't call Salsa "flawless", would you? Issues with > Salsa/GitLab: > > 1. It is so slo

Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

Hi, On Fri, 2 Aug 2024 at 16:27, Johannes Schauer Marin Rodrigues wrote: > Quoting Otto Kekäläinen (2024-08-02 17:23:51) > > I agree that Salsa is sometimes a bit sluggish > > (https://salsa.debian.org/salsa/support/-/issues/395), > > what kind of hardware do you have? For p

Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

Hi! > I have three feelings. > > > 1. Debian workflows are too fractured. The project would be better if we > asked people to standardize around a single (or a small number) of workflows. > To do so, the workflow would need to be flexible enough to handle the wide > range of technical needs

Re: lintian.debian.org off ?

Hi! On Fri, 9 Aug 2024 at 04:12, Nicolas Peugnet wrote: > > If there is interest in providing a page that only list the tag > > description (without the affected packages), it would be easier to add > > it to the existing UDD page (with an additional parameter for example) > > than to create a se

Salsa connection errors or slowness has improved (Re: Request for feedback on draft: DEP-18)

Hi! In the DEP-18 thread surprisingly many (e.g. Salvo, Johannes, Andrea, Gioele) complained about Salsa being slow to load, or having connectivity issues. I am thus happy to note that the Salsa admins posted in https://salsa.debian.org/salsa/support/-/issues/395 a comment stating that salsa.debi

Re: Accepting DEP14?

Yes to finalizing DEP-14 soon, but first I think we need to complete the technical work to have git-buildpackage use DEP-14 branch names by default. I tried implementing it but turned out a bit too involved.. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829444 Use DEP14 branch layout by defa

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/exper

Re: debian/gbp.cnf analytics? (Re: Re: Accepting DEP14?)

Hi! ## How many source packages are in Debian unstable as of today? ± zgrep "^Package: " Sources.gz | wc -l 38199 ## How many source packages have a gbp.conf? ± ls -1 *_gbp.conf | wc -l 13570 (24629 do not have it) ## What is the most popular 'debian-branch'? Note! The Sources.gz used to anal

DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

Hi! In short: I would very much like to see all top-150 packages run Salsa CI at least once before being uploaded to unstable. What people think is a reasonable way to proceed to reach this goal? Background: We have had several cases recently where an upload to Debian unstable causes widespread

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

Hi! > > I would very much like to see all top-150 packages run Salsa CI at > > least once before being uploaded to unstable. What people think is a > > reasonable way to proceed to reach this goal? > Advertise widely and frequently that there is a pool of people which is > happy to help investigat

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

Hi! > I'd like to rephrase your quest. What you really want is unstable to be > less unstable. Whilst a number of people disagree with that notion, I I don't think anybody disagrees that breaking a core packages and stopping (nearly) all other DDs from doing development for a day or two is accept

Re: [Debian-salsa-ci] DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

Hi! > And is this web page authoratative? Or just a false search positive? > > https://salsa.debian.org/salsa-ci-team/pipeline#basic-use > > It doesn't mention the "salsa" command at all, but maybe that isn't > the right web page. This goes back to my observation that it would be > helpful i

Re: DEP18 follow-up: Salsa CI vs Debusine

Hi Helmut! > > Let me suggest that there are more ways to do this. Freexian is putting > > a ton of effort into https://debusine.debian.net. It can do much of the > > same tasks as salsa-ci already (with less flexibility). Extending it to > > act as an upload-proxy that forwards your upload to the

Re: Validating tarballs against git repositories

On Tue, 2 Apr 2024 at 17:19, Jeremy Stanley wrote: > On 2024-04-02 16:44:54 -0700 (-0700), Russ Allbery wrote: > [...] > > I think a shallow clone of depth 1 is sufficient, although that's not > > sufficient to get the correct version number from Git in all cases. > [...] > > Some tools (python3-re

DEP-18: Git and GitLab usage in other Linux distros (Re: Representing Debian Metadata in Git)

Hi! Considering what other Linux distros are doing and what is popular among software developers today, Debian will probably gain more contributors and be more approachable if we don't reinvent too many custom things, and hence... .. > In the current DEP14/DEP18 discussions a lot of discussion wa

DEP-18 discussion summary (Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages)

hauer Marin Rodrigues, Andrea Pappacoda, and Gioele Barabucci, complained about Salsa/GitLab being slow or unreliable at times, which deterred contribution. Improvements to performance and uptime were seen as important. In response, Otto Kekäläinen noted that the Salsa admins had posted about upcoming

Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

Hi! > NOTE: The following idea might be out-of-scope in DEP-18, but specific > use-case to improve > collaboration in Debian, IMHO. > > Here is just an idea: put collaboration policy metadata in debian/control. > (The following idea assumes that non-maintainer DD tend to hesitate to > commit/merge

Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages

Hi Jonathan! The discussion was summarized in a separate "Summay" email by me on this list, and a comment in the MR (which merges the two discussions) and it just happened that the next day it was also covered in https://lwn.net/Articles/986480/ I am currently writing revision 2 of the proposal.

Re: lintian.debian.org off ?

Hi! Thank you, Nicolas and Luis-Philippe, stepping up here is highly appreciated and will benefit a large amount of Debian packagers and their collaborators. > > Please be honest :) I don't mind it at all if you tell me: "yeah, that > > was only a proof of concep", or "I'm motivated now, but I do

Re: DEP-18 discussion summary (Re: Request for feedback on draft: DEP-18: Enable true open collaboration on all Debian packages)

Hi! > Hi Otto, > Until recently I generally found Salsa response to be adequate, > but for the last couple of days it has been so > excruciatingly slow as to be almost unusable. > > > In response, Otto Kekäläinen noted that the Salsa admins > > had posted about upc

Re: lintian.debian.org off ?

Hi! Thanks both Lucas and Nicolas for your contributions to Debian. Can we agree to have both UDD and lintian.debian.org, as the work to develop the required systems already happened? I think both websites have their benefits. Having a lintian.debian.org site with links to man pages and addition

Re: Bug#745135: RFS: mariadb-10.0/10.0.10-1 [ITP] -- Latest version of worlds most popular non-Oracle database

Thanks for your interest in the package. I am the submitter and I haven't gotten any feedback so far on the package, so I assume it is simply waiting for somebody to have time to review it. It is almost identical to the current mariadb-5.5 package in Debian, so there shouldn't be any actual issues

Re: [debian-mysql] Will we see MariaDB in Jessie?

Hello, 2013/5/6 Thomas Goirand : > I wonder what the plans of the MySQL maintainers are concerning MySQL vs > MariaDB. Famously, Fedora made the switch. What will happen in Debian? > What kind of transition would this mean? Would it be a drop-in > replacement like Monty is pretending, or would it

Re: [debian-mysql] Will we see MariaDB in Jessie?

2013/5/6 Steven Ayre : > Having a policy on how such packages can coexist could then allow > other options to also be added cleanly (MySQL Cluster, Percona, Galera > etc). I've done my best to package MariaDB following best practices on Debian control files and conflict/replace rules. So I am conf

Re: Bug#732878: Add MariaDB as an alternative dependency

2013/12/25 Thomas Goirand : > Don't you think it would be more reasonable if the mariadb-client > contained a Provides: mysql-client, rather than changing each and every > software dependency in Debian? Currently the package contains "Provides: virtual-mysql-server" but I guess this needs to be re

Re: Bug#732878: Add MariaDB as an alternative dependency

Hello, 2013/12/25 Thomas Goirand : > Don't you think it would be more reasonable if the mariadb-client > contained a Provides: mysql-client, rather than changing each and every > software dependency in Debian? > > Adding debian-devel@, as I think it should be discussed more broadly. We discussed

Re: Bug#732878: Add MariaDB as an alternative dependency

2013/12/30 Otto Kekäläinen : > We discussed this on the pkg-maint-mysql list and the recommended policy is > now: > > All packages that at the moment depend directly on mysql-client should > instead have something like: > > Depends: the-one-they-tested-with | virtual-mysql-

Re: The future of MariaDB

Hello David, Sorry for the long delay in the reply, this list has so much traffic that I cannot follow it normally. 2015-02-11 0:35 GMT+02:00 David McMackins : > The latest version of libmariadb in Debian no longer works as a drop-in > replacement for MySQL. The library's name and include path ha

Re: Debian CI pipeline for Developers

la 10. marrask. 2018 klo 22.12 Agustin Henze (t...@debian.org) kirjoitti: .. > Please follow the README[0] to enable CI in your packages. > > [0] https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md I have been using the Salsa-CI (and modified versions of it) in all of my MariaDB

Help request: Contribute to MariaDB 10.3 in Debian efforts

Hello! I've spent the last months preparing MariaDB 10.3 for Debian. I am almost done, but there are a bunch of smaller issues I need help with. I would be glad for anybody who can look into the issues and give solution ideas - or even file a merge request on Debian's Gitlab instance where the Deb

Re: Help request: Contribute to MariaDB 10.3 in Debian efforts

Hello fellow Debian Developers and those who want to be one! MariaDB is a big package and it needs help. I've updated the list of newcomer friendly bugs in mariadb-10.3:https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=mariadb-10.3 Perfect for anybody who wants to learn Debian pa

Seeking hardening flag / blhc expoert

Hello! Is there any hardening flag / cmake expert around who could help me get the hardening flags perfect in MariaDB 10.3? Current state of build logs issues: https://qa.debian.org/bls/packages/m/mariadb-10.3.html The blhc tool currently outputs this: $ blhc --debian --line-numbers --color ${W

Re: Seeking hardening flag / blhc expoert

Hello! > > Is there any hardening flag / cmake expert around who could help me > > get the hardening flags perfect in MariaDB 10.3? > Start with https://wiki.debian.org/Hardening#Notes_for_packages_using_CMake I've read this section many times over but I don't get it. A workaround is presented bu

Re: Seeking hardening flag / blhc expoert

So apparently the 'D_FORTIFY_SOURCE=2' is in CPPFLAGS (not read by cmake) but not in CXXFLAGS (read by cmake)[1]. So maybe I should define? CXXFLAGS=$(CXXFLAGS) $(CPPFLAGS) This is the current state of mysqld, should I be happy with this or is it relevant that all functions are protected? harden

Re: Seeking hardening flag / blhc expoert

Hello! Thanks everybody for the pointers. I fixed it now with: Subject: [PATCH] Ensure cmake builds also apply CPPFLAGS flags for hardening to fully work --- debian/rules | 5 + 1 file changed, 5 insertions(+) diff --git a/debian/rules b/debian/rules index 3a16f8bfa..2e7536b9c 100755 ---

Re: lintian.debian.org off ?

> > > Host lintian.debian.org not found: 3(NXDOMAIN) > > > > > > is this expected ? > > > > Yes, it is replaced by the UDD interface: > > > > https://wiki.debian.org/Services/lintian.debian.org > > https://udd.debian.org/lintian/ Could we please have a HTTP 301 redirect from lintian.debian.org to

Salsa-CI featured on GitLab.com blog

Hi all! I just wanted to share that the story about Salsa-CI was featured a couple days ago at https://about.gitlab.com/blog/2023/09/19/debian-customizes-ci-tooling-with-gitlab/ Personally I think Salsa-CI is extremely useful and pleasant to use and understand, and it surely helped make Debian 12

Re: lintian.debian.org off ?

> > > > Host lintian.debian.org not found: 3(NXDOMAIN) > > > > > > > > is this expected ? > > > > > > Yes, it is replaced by the UDD interface: > > > > > > https://wiki.debian.org/Services/lintian.debian.org The page above links to two bug reports but I can't find any actual information about *why

Re: lintian.debian.org off ?

Hi! Thanks for the context - so there is no need technical incompatibility at play, but mostly a matter of having resources and time to do it. .. > Regarding the 301 redirection I'll see with the interested parties (DSA > and Lintian maintainers) if this option is fine with everyone. I could easi

Re: lintian.debian.org off ?

Hi! On Wed, 27 Sept 2023 at 13:27, Lucas Nussbaum wrote: > > Hi, > > #1042428 is the bug for "no explanation for lintian tags on UDD" > > On 26/09/23 at 21:35 -0700, Otto Kekäläinen wrote: > > I know Lintian tag info is available via command line, but I > &

Re: Bug#1042428: lintian.debian.org off ?

> > This issue still exists. I would now have the need to send the url > > https://lintian.debian.org/tags/service-file-is-not-a-file to upstream > > developers to learn about this Lintian issue, but the URL does not > > serve any contents nor does it redirect to a new location. > > > > I am still

Re: Bug#1042428: lintian.debian.org off ?

> >> I finally fixed this. Sorry for the delay. > >> > >> https://udd.debian.org/lintian?packages=entr has a link for each lintian > >> tag, that points to (e.g.) > >> https://udd.debian.org/lintian-tag.cgi?tag=superfluous-file-pattern > >> That page includes a description of the tag as well as al

Running Lintian against a debian/ directory?

Hi! Currently Lintian requires a (source or binary) package to check[1]. However, many of the Lintian source package checks (e.g. spelling of debian/changelog entries) don't strictly depend on anything being built. Is anyone aware of a way to run lintian directly on a debian/ directory contents a

Re: Running Lintian against a debian/ directory?

> Paul already answered the lintian part, so I will skip that. But I also > wanted to suggest looking into integrated spell-checking in your editor > if possible. Having integrated spell-check will enable a much faster > feedback loop. Thanks the reply, but basic spell checking is pretty much alre

Re: [Pkg-pascal-devel] Issue with fpc_3.2.2+dfsg-24 in Sid.

Hi Abou! I can't help with the issue at hand, but as general advice for the future: if you had Salsa-CI enabled at https://salsa.debian.org/pascal-team/fpc/-/pipelines the build-all and build-any jobs would have probably caught this before upload. Just open https://salsa.debian.org/pascal-team/fp

Re: DebGPT: how LLM can help debian development? demo available.

Hi! I've noticed that the most recent LLMs are actually very good at finding information, summarizing and giving code examples about Debian already without extra training. One just needs to double check that the answer was correct to not fall for when they are simply making up plausible sounding s

Static analyzer / linter for debian/rules?

Hi! Is anybody aware if there is some kind of static analyzer for the `debian/rules` file? I can do very basic syntax checking with `make --dry-run --makefile=debian/rules` which will error on serious syntax errors (which I already implemented in my CI workflow[1]). However, that or a general Ma

Bug#1060778: ITP: pulsar-edit -- A Community-led Hyper-Hackable Text Editor (formerly Atom)

Package: wnpp Severity: wishlist Owner: Otto Kekäläinen X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: pulsar-edit Version : 1.112.1 Upstream Contact: ad...@pulsar-edit.dev * URL : https://pulsar-edit.dev/ * License : MIT Programming Lang

Editor extensions to help editing debian/* files?

Hi! What editors and extensions are you using to augment your productivity and minimize mistakes when editing debian/* files? I am aware of dpkg-dev-el for Emacs mentioned in the DD reference[1]. I am a big fan of Pulsar[2] and recently found a 'language-debian' plugin for Pulsar[3], but didn't g

Re: Editor extensions to help editing debian/* files?

Hi! Thanks for the tip, Niels! It would be cool if dh_assistant had some kind of generic command like "dh_assistant validate" which would attempt to introspect all information silently and emit output only if it fails to parse something. Additionally it could emit a non-zero exit code on errors.

Re: Editor extensions to help editing debian/* files?

> I looked into better tooling/editor support in general for Debian > languages in general. I think the industry answer is that "someone" > ought to build a "language (LSP) server" for the Debian languages, which > would enable editors with LSP support[1] to get the same basic features. True - LSP

Re: Editor extensions to help editing debian/* files?

Hi! > Thats beginning to look like the history of check-all-the-things. Yeah, I remember looking into cats some years back as a place to learn what commands exist. Similarly I also occasionally browse https://pre-commit.com/hooks.html. The challenge with having all possible checkers is that they

Re: Editor extensions to help editing debian/* files?

Hi! > > It would be nice though if the version in Debian was newer :) > > I probably won't update it until it is suitable for inclusion in a > stable release. This means at minimum being relatively safe to run in > an untrusted source tree, probably by using debvm to generate a VM > containing the

Re: postgresql-16; wrong NMU versions (Re: 64-bit time_t transition in progress)

> Re: Steve Langasek > > Christoph Berg > >postgresql-16 (U) > > Please do not upload postgresql-16 before I ack the diff. > > I'll also note that *ALL* nmu diffs I've seen so far are using the > wrong version number in debian/changelog, missing the "~exp1" upload > from the actual upload. I'v

Re: postgresql-16; wrong NMU versions (Re: 64-bit time_t transition in progress)

> $ grep mariadb results/* > results/results_dumped.txt:libmariadb-dev > results/results_failed.txt:libmariadbd-dev > results/results_none.txt:libmariadb-dev > $ > > There was nothing unintentional here. libmariadb-dev is clean wrt time_t. > libmariadbd-dev failed to be analyzed because it has hea

Re: time_t transition and bugs

Thanks Steve for uploading a fixed curl on Saturday. Just checking did you notice amel/armhf are still not building due to secondary issues and n dependencies? https://buildd.debian.org/status/package.php?p=curl

openssl 3.1.5-1.1 effect on reverse dependencies

Hi Benjamin! You recently uploaded openssl 3.1.5-1.1. Are you tracking the effect it had on reverse dependencies? Do you have plans to do any follow-up uploads or +b1 rebuilds of other packages? For example curl is unable to satisfy build dependencies on armhf/armel at the moment: https://build

Re: 64-bit time_t transition: cargo needs manual intervention

Hi! Is anyone perhaps planning to fix cargo? For example curl isn't building on armel/armhf now and numerous packages that depend of curl are not building on armel/armhf. Thanks in advance to the person who steps up.

Re: 64-bit time_t transition: cargo needs manual intervention

Hi! pe 15. maalisk. 2024 klo 6.56 Fabian Grünbichler kirjoitti: > On Thu, Mar 14, 2024 at 10:03:57PM -0700, Otto Kekäläinen wrote: > > Hi! > > > > Is anyone perhaps planning to fix cargo? > > > > For example curl isn't building on armel/armhf now and num

Is it allowed to remove attribution in public domain "licensed" source code? (and pondering about ftp-level reviews)

Hi! While reviewing xz-utils commits I noticed that a bunch of old copyright holder names were removed in https://salsa.debian.org/debian/xz-utils/-/commit/d1b67558cbc06c449a0ae7b7c1694e277aef4a78. Is this OK to do so? Having source code in the public domain means that there is no copyright, so n

Re: xz backdoor

Hi! On Sat, 30 Mar 2024 at 14:32, Andrey Rakhmatullin wrote: > On Sat, Mar 30, 2024 at 10:49:33AM +0200, Jonathan Carter wrote: > > Another big question for me is whether I should really still > > package/upload/etc from an unstable machine. It seems that it may be prudent > > to consider it best

Re: Tool to build Debian packages not requiring root in containers ?

Hi! On Tue, 7 May 2024 at 15:27, Charles Plessy wrote: .. > I want to leverage our cluster to automate as much of the rebuilds as I > can, but could not find the right tool. I tried to run sbuild in a > Singularity image and this failed. However, I do not need the whole > power of engines like

Re: Tool to build Debian packages not requiring root in containers ?

Hi! ti 7. toukok. 2024 klo 23.01 Charles Plessy kirjoitti: > Le Tue, May 07, 2024 at 08:17:31PM -0700, Otto Kekäläinen a écrit : > > > > Can you give me an example of a package you want to build and what is > > the starting point, and I can tell you what command

Salsa - best thing in Debian in recent years? (Re: finally end single-person maintainership)

Hi Bill and Wookey! In a recent long thread on debian-devel you had somewhat negative sentiments towards the usefulness of Salsa. I do see you doing good technical work for Debian and recently a MR from Bill too, so I was thinking that maybe you will change your mind when you read more in-depth ar

Re: Salsa - best thing in Debian in recent years? (Re: finally end single-person maintainership)

> > My concern about Gitlab is not its *additions* to existing services, but > > its *duplications* of core services already in Debian. > > I agree, that's the key problem. I agree that duplication is bad - but I disagree that use of version control duplicates the use of the Debian archive for sou

Re: Salsa - best thing in Debian in recent years? (Re: finally end single-person maintainership)

Thanks for reply Jonas, > > You could go to > > https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19 and > > conduct a code review? > > > > You might discover that GitLab is useful and is not duplicating > > Debbugs or anything else in Debian - it is currently the only platform > > to

Re: Debian 10 "buster" moved to archive.debian.org

On Sat, 23 Mar 2024 at 01:32, Ansgar 🙀 wrote: > > Hi, > > Debian 10 "buster" has moved to archive.debian.org in order to free > space on the main mirror network. We plan to start removing files for > non-LTS architectures in about two weeks; the existing Release files > will then refer to no long

Re: Salsa - best thing in Debian in recent years? (Re: finally end single-person maintainership)

> > Ideally debbugs should be made non-native so that some else could > > maintain the Debian package. > > I'm happy to review patches that get the 2.6 branch of debbugs in shape > where it can be released into Debian again if someone wants to take that > effort. I've just assumed that anyone using

Re: Any volunteers for lintian co-maintenance?

Hi! > > If I am successful, then lintian can specialize its efforts into issues only > > visible in packaged artifacts and thereby reduce it scope a bit. > > Perfect. I'd love to have some policy checking at "the right point in > time". I'd love to support this but as far as I understand even yo

Re: finally end single-person maintainership

Hi Simon! > > A better approach would not treat Debian metadata as git data. Even the > > most vocal advocate of switching everything to Salsa writes in his MR > > that the changelog should not be touched in a commit, because it creates > > conflicts, and instead a manual step will need to be perf

Re: Salsa - best thing in Debian in recent years? (Re: finally end single-person maintainership)

Hi! On Sun, 19 May 2024 at 20:48, Don Armstrong wrote: > > On Sun, 19 May 2024, Bill Allombert wrote: > > Also debbugs is a special case: > > The debbugs Debian package (as opposed to the debbugs software) have never > > been > > really maintained. I am actually one of the very few users of this

Re: Debian 10 "buster" moved to archive.debian.org

Hi! So just to clarify, are you saying that a copy of https://security.debian.org/debian-security/dists/buster/ will never be archived at https://archive.debian.org/debian-security/dists/ like previous releases have been so far? This is not about getting *new security updates*, but purely a quest

Re: MBF: Building packages in the (not so distant) future

Plus one to this initiative! I also wanted to share the tip to use libfaketime as the easiest way to test if a build or test suite works on an arbitrary future date. I am currently testing that the MariaDB upstream test suite passes in 2037 and 2028 using libfaketime like this: https://salsa.debia

MariaDB 10.5 has entered Debian testing (will be in Bullseye)

adb-10.5 commits : 197 authors : 187 Otto Kekäläinen 94.9% 2 Christian Göttsche 1.0% 2 Helmut Grohne 1.0% 1 Aurelien Jarno 0.5% 1 Bastian Germann 0.5% 1 Christian Ehrhardt 0.5% 1 Daniel Black0.5% 1 Faustin Lammler 0.5%

Re: MariaDB 10.5 has entered Debian testing (will be in Bullseye)

to 26. marrask. 2020 klo 18.45 Thomas Goirand kirjoitti: > Hi Otto, > > On 11/26/20 4:44 PM, Otto Kekäläinen wrote: > > Hello! > > > > MariaDB 10.5 release 1:10.5.8-3 finally entered Debian testing > > today[1]. It has been in unstable since early September, and

Re: MariaDB 10.5 has entered Debian testing (will be in Bullseye)

> So, if I understand well, if I have 3 MariaDB Buster nodes in a cluster, > I just need to dist-upgrade them to Bullseye, and it will automagically > just work and upgrade to Galera 4? If so, that's just great, because > during our last discussion in Brazil, you told me about something a way > mor

Tools to better colorize the command-line experience?

Hello! Colorizing the command-line is an efficient way to make various output more readable. In particular when browsing log files it helps hugely if columns or certain key values are colorized. For this type of use case there is ccze packaged in Debian[1]. Lesspipe[2] is also somewhat known. I l

Re: Tools to better colorize the command-line experience?

On Fri, 8 Jan 2021 at 04:01, Seth Arnold wrote: > > On Thu, Jan 07, 2021 at 11:02:24PM +0200, Otto Kekäläinen wrote: > > Do you have any tips about generic command-line coloring programs? > > The bat package provides a batcat program that'll add colour to a lot of &

Tips for debugging/testing debian/control Depends/Breaks etc changes?

Hello! I've noticed I've spent quite a lot of time debugging various situations where the debian/control definitions for depends/breaks/replaces/conflicts/provides are not optimal. The waste of time is two-fold: 1) apt is not verbose enough 2) the cycle to rebuild/tests is too slow As an exampl

Re: Tips for debugging/testing debian/control Depends/Breaks etc changes?

Thanks David, using --with-sources is exactly what I needed. As a starting point I have the *.deb I've built. In the same directory I create a Packages file with: apt-ftparchive packages . > ./Packages Then I install using it: apt install --with-source ./Packages -s mariadb-server mariadb-client

File moved from one package to another - use Conflicts/Replaces or Breaks/Replaces?

Hello! In MariaDB we have over the years moved files around. A file that was first in e.g. mariadb-server-10.3 might have been moved to mariadb-server-core-10.3 and some years later to mariadb-client-core-10.5. The result is a massive debian/control file with a lot of Conflicts/Breaks/Replaces [1]

Re: File moved from one package to another - use Conflicts/Replaces or Breaks/Replaces?

Hell! On Sun, Apr 4, 2021 at 4:54 AM Andreas Metzler wrote: > > On 2021-04-03 Otto Kekäläinen wrote: > > Hello! > > > In MariaDB we have over the years moved files around. A file that was first > > in e.g. mariadb-server-10.3 might have been moved to > > mariad

Re: Tips for debugging/testing debian/control Depends/Breaks etc changes?

Hello! > For me, this whole situation seems wrong though. Why do you have > versioned package names (mariadb-server-*) when they are all mutually > exclusive with one another due to all shipping the same binary? This is how the MySQL packaging has been structured for the past 10 years or so. Ther

MariaDB Foundation looking to hire/contract Debian packaging expert

Hello! The MariaDB Foundation is seeking to get a Debian expert to work for them (plus if you are a DD). This is a great opportunity for Debian people to land a job/contract where they can work full-time on open source and with a big part of it related to Debian. Check out: https://mariadb.org/de

New systemd service file path?

Hello! I noticed that Lintian has recently started erroring on https://lintian.debian.org/tags/systemd-service-in-odd-location I can't find this requirement anywhere in the Debian Policy, e.g. https://www.debian.org/doc/debian-policy/ch-opersys.html#starting-system-services does not mention anyth

How to fix Lintian 'no-code-sections'?

Hello! Lintian in Debian unstable has a new test that my package is failing on: https://lintian.debian.org/tags/no-code-sections Can somebody who recently fixed this in their own package give some advice how I should fix it for mariadb-10.6? See example of Lintian error about libmariadbd.a in co

Re: How to fix Lintian 'no-code-sections'?

On Sat, Nov 27, 2021 at 5:30 AM Simon McVittie wrote: > > On Fri, 26 Nov 2021 at 22:10:45 -0800, Otto Kekäläinen wrote: > > Lintian in Debian unstable has a new test that my package is failing on: > > https://lintian.debian.org/tags/no-code-sections > > As with any Lintia

Re: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]

> > I think the answer to this should probably be established by the > > libpam-tmpdir maintainer and documented first, for fear of someone else > > later coming along and saying that the maintainer script incorrectly > > ignores TMPDIR because we started ignoring it to resolve this bug. So I > > c

Re: [Salsa CI] stop building dbgsym packages by default?

Hi! On Wed, 9 Nov 2022 at 01:08, Santiago Ruano Rincón wrote: > Aiming to reduce the space used in the salsa infrastructure by the > salsa-ci artifacts, and to avoid exceeding the size limit in build jobs, > we (Salsa CI Team) are planning to stop building dbgsym packages: > https://salsa.debian.

depends-on-obsolete-package lsb-base

Hi! Lintian just started erroring on 'depends-on-obsolete-package lsb-base' on many of my packages yesterday. There are no new uploads of lsb-base recently and I did not find any news about this topic. The Lintian page https://lintian.debian.org/tags/depends-on-obsolete-package is only about the e

Re: depends-on-obsolete-package lsb-base

Hi! On Wed, 18 Jan 2023 at 09:00, Andreas Metzler wrote: > > On 2023-01-18 Otto Kekäläinen wrote: > > Lintian just started erroring on 'depends-on-obsolete-package > > lsb-base' on many of my packages yesterday. There are no new uploads > [...] > >

Re: depends-on-obsolete-package lsb-base

> > About the execution of this change repository-wide: > > > > Is anyone working on feeding > > https://salsa.debian.org/lintian/lintian/-/blob/master/data/fields/obsolete-packages > > to https://janitor.debian.net/scrub-obsolete/ so that at least > > Salsa-maintained packages would swiftly get on

MariaDB 10.11 in Bookworm - call for contributions

Hello! (Stop reading if you don't use MariaDB) I am currently preparing the upload of MariaDB 10.11.2-2 to Debian unstable and aim for the highest possible quality. I am currently doing the bulk of the testing and packaging alone and to make sure that the quality is top notch, I would be glad to

  1   2   3   >