From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4ZLFb608kdz331L for ; Sun, 23 Mar 2025 12:18:42 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature RSA-PSS (4096 bits)) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ZLFb50Hs7z32vy for ; Sun, 23 Mar 2025 12:18:41 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ZLFb41Xvdz96g; Sun, 23 Mar 2025 12:18:39 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1742732320; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YqEU51jLaAhebSCWJPbf8oaJ4NAbCjoxQ+U3Lcb8BLU=; b=YIkr3u9/+8CKzSuAKT2ZzQrVsB7cFmfL/U79c4LFsyGxiZ5xL8hDi4Jlm2s9iFY1TW5Cdk s4wtKX0aZgC4/iDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1742732320; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YqEU51jLaAhebSCWJPbf8oaJ4NAbCjoxQ+U3Lcb8BLU=; b=qCMRRoofBQXStNO+/xekRU/12CmViqZmawdBznaeB88Grv78S1FLOT/Z+wFJdZ4sGs0uA6 UDZkdPahSBdflP9tVE3wJgOotEHnQErOvO/RXghhEnZoNuB5LRc45kinZq64Ok9uRU6J6a QU+wgNTBbAIOvZtN8idiTS5O2UPv++3ml9/YwgOf4FyeleupNaB8/wq2aNJOgFxKtxRte5 a2rsPG0meqGyAP/8GzdvHuc9mLV/FiV6e1lFjmovAi9QLoJXShVBAgCbSApzBgw/Rw6kDs v2RXiHQriHOfxW62OITqlPPGx3d5+27n9mMgb9obtHmhY/Q626itquzaPJTfzA== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Upload libloc to Debian From: Michael Tremer In-Reply-To: <633f6312-7914-45db-882b-cb890a6f770c@guardianproject.info> Date: Sun, 23 Mar 2025 12:18:39 +0000 Cc: Stefan Schantl , =?utf-8?Q?Peter_M=C3=BCller?= , location@lists.ipfire.org, Jochen Sprickerhof Content-Transfer-Encoding: quoted-printable Message-Id: <7A44A48A-9689-42AF-BC45-2B945CB9F0E1@ipfire.org> References: <4DB03F40-8299-4448-ADCE-064905D6B831@ipfire.org> <53A0D651-73FD-4A97-81E9-DC2D7565D7EF@ipfire.org> <26719411-D6EA-46E4-8259-487E39E72F7F@ipfire.org> <3D9CC9EB-55CB-49F8-85B2-C79E3B1629FD@ipfire.org> <048f09d9-9985-a356-fed1-4cd8e286b87e@guardianproject.info> <968D3231-FFDF-4347-8A43-C0C6DF5ED887@ipfire.org> <9c740e42-cd03-428c-814a-fa8bdee99db9@guardianproject.info> <968FAB68-729C-4367-BA24-FDC1D1F885A7@ipfire.org> <6e7a9c4e-63c1-4896-bdb0-e621542ca3a7@guardianproject.info> <2B3195A3-B3AC-4002-A18B-275C58DDAA80@ipfire.org> <633f6312-7914-45db-882b-cb890a6f770c@guardianproject.info> To: Hans-Christoph Steiner Hello, > On 23 Mar 2025, at 08:31, Hans-Christoph Steiner = wrote: >=20 > Hey Michael, >=20 > Great to hear about all your work on libloc, it is really a key = package. One possibility that might streamline things is if you = maintained your Debian packaging in = https://salsa.debian.org/debian/libloc/ or as a fork of it. That = already includes a lot of tests around the Debian package and = integration: > https://salsa.debian.org/debian/libloc/-/pipelines/836918 I agree that it would be nice to get these things closer together. I = however remember that there were some problems that I discussed with = Jochen some long time ago and which I cannot remember any more :) Those = were a mix of me having very little experience with the Debian build = system, different requirements for the different releases (trixie seems = to have a different package naming system for libraries) and therefore = massive confusion on my part. I also have no interest in publishing any = packages outside for the purpose of development, so I didn=E2=80=99t = think it was worth to spend any time on this. Any pointers on how we can make this all go together? I believe the = closer the two repositories are to each other, the less work for all of = us. > Then for your CI, you could make the CI job copy the debian/ dir from = that repo. And then there would be no need to maintain the debian/ dir = in the libloc git repo. But how do I build my test packages then? I need to be able to make = changes as well. > I uploaded 0.9.18, it is in unstable awaiting the autopkgtest run. = 0.9.17 made it into trixie already. Thank you very much! Let me know if there are any problems. Looking through the files I noticed a security contact here: = https://salsa.debian.org/debian/libloc/-/blob/master/debian/upstream/metad= ata?ref_type=3Dheads; Could you please add security@ipfire.org = or a note that people can check a box on = Bugzilla to submit a non-public ticket? The Git repository should also = be https://git.ipfire.org/?p=3Dlocation/libloc.git;a=3Dsummary as I = don=E2=80=99t think we will continue using GitHub that much longer. It = only serves as a mirror with no other benefit for us. Best, -Michael >=20 > All the best, > Hans >=20 > Michael Tremer: >> Hello, >> Great! Let me know whenever I can help testing or whether you need = any changes. >> In the meantime I have been setting up a little Jenkins pipeline = which should help us to provide better releases. There could be done = much more here, but for that I would require some more time i.e. = funding=E2=80=A6 >> The current status is here: https://jenkins.ipfire.org/job/libloc/ >> But so far we are building for Debian, Ubuntu, Fedora and Archlinux. = We are also building Debian packages for pretty much all supported = architectures which are amd64, arm64, armel, armhf, i386, ppc64el, = s390x. This has already helped me finding a big-endian issue which is = fixed here: >> = https://git.ipfire.org/?p=3Dlocation/libloc.git;a=3Dcommitdiff;h=3Dafc5330= f56d74b4a9142b800d994d623d7cd29e8 >> The pipeline outputs some Debian packages. These are not supported to = be used by regular users, because I would rather have the latest version = of our package in the official distribution. They are however useful for = testing because I can install them really quick wherever I need them. = Therefore it would be great if these packages would be as close to = upstream as possible so that we are actually testing the same thing. I = would be happy to receive patches if you are up for that. >> Best, >> -Michael >>> On 19 Mar 2025, at 09:10, Hans-Christoph Steiner = wrote: >>>=20 >>>=20 >>> I uploaded 0.9.17 to Debian already, and will upload 0.9.18 once = 0.9.17 is in testing. After 0.9.18 makes it to testing, I'll try = enabling the lua-location binary package, it looks easy. It'll have to = go through the NEW queue, so it might not make it into trixie/testing. >>>=20 >>> Michael Tremer: >>>> Hello everyone, >>>> I have a release tagged here: = https://source.ipfire.org/releases/libloc/libloc-0.9.18.tar.gz >>>> = https://git.ipfire.org/?p=3Dlocation/libloc.git;a=3Dshortlog;h=3D8cbdc19cd= a26d37dca354135c2825fa6a4d94ff4 >>>> Please let me know if you find any regressions. >>>> Best, >>>> -Michael >>>>> On 6 Mar 2025, at 10:48, Michael Tremer = wrote: >>>>>=20 >>>>> Hello Hans, >>>>>=20 >>>>> Thanks for your email. >>>>>=20 >>>>> Yes, there has been a lot of work being going into the library in = the past year. We have made huge improvements to the importer which now = several orders of magnitude faster, we have added Lua bindings and = generally improved stability and performance. However, I don=E2=80=99t = remember where I have left off. Time has been running out. >>>>>=20 >>>>> It would be great to have the latest changes in Debian, because = Trixie is coming up fast. We should definitely have the latest version = in the release whenever it will come out. >>>>>=20 >>>>> Is there a deadline for all of this? I would have to squeeze a = release into my schedule and first of all making sure that we are = releasing good software without introducing any new problems. >>>>>=20 >>>>> -Michael >>>>>=20 >>>>>> On 5 Mar 2025, at 18:25, Hans-Christoph Steiner = wrote: >>>>>>=20 >>>>>>=20 >>>>>> Hey IPFire crew! >>>>>>=20 >>>>>> I'm just looking at updating libloc in Debian. It looks like = there are a lot of commits in git that are not part of a release. Do = you have plans to make a release soon? >>>>>>=20 >>>>>> All the best, >>>>>> Hans >>>>>>=20 >>>>>> Michael Tremer: >>>>>>> Hello everyone, >>>>>>> HC, thank you for your contribution to our little project. If = you find anything else, please feel free to send patches. >>>>>>> And thank you Stefan for getting this into the repository. >>>>>>> Best, >>>>>>> -Michael >>>>>>>> On 2 Mar 2023, at 16:19, Stefan Schantl = wrote: >>>>>>>>=20 >>>>>>>> Hello Hans-Christoph, >>>>>>>>=20 >>>>>>>> a big thanks for writing and sharing your script. I've added it = to the >>>>>>>> official libloc source code by the following commit: >>>>>>>>=20 >>>>>>>> = ttps://git.ipfire.org/?p=3Dlocation/libloc.git;a=3Dcommit;h=3D02a7d6ec0bb7= 9f9 >>>>>>>> 62ffe0746d311b3454b11a3db >>>>>>>>=20 >>>>>>>> Best regards, >>>>>>>>=20 >>>>>>>> -Stefan >>>>>>>>>=20 >>>>>>>>> Hey all, >>>>>>>>>=20 >>>>>>>>> I just uploaded a new version of the libloc Debian package = that >>>>>>>>> includes bash >>>>>>>>> completion for the 'location' command. I would like to see = this file >>>>>>>>> included >>>>>>>>> upstream in your git, so it is also attached to the email. >>>>>>>>>=20 >>>>>>>>> If you want to try it, either install location 0.9.16-2 from = Debian, >>>>>>>>> or stick >>>>>>>>> the attached file in /etc/bash_completion.d/location and open = a new >>>>>>>>> bash shell. >>>>>>>>>=20 >>>>>>>>> .hc >>>>>>>>>=20 >>>>>>>>> Jochen Sprickerhof: >>>>>>>>>> Hi Michael, >>>>>>>>>>=20 >>>>>>>>>> * Michael Tremer [2022-08-16 = 10:00]: >>>>>>>>>>>> https://buildd.debian.org/status/package.php?p=3Dlibloc >>>>>>>>>>>=20 >>>>>>>>>>> I installed a virtual machine with mips64el and the = testsuite >>>>>>>>>>> weirdly runs >>>>>>>>>>> through. >>>>>>>>>>=20 >>>>>>>>>> I was able to reproduce it using ppc64el: >>>>>>>>>>=20 >>>>>>>>>> # echo "deb-src http://deb.debian.org/debian unstable main" = >> >>>>>>>>>> /etc/apt/sources.list >>>>>>>>>> # apt update >>>>>>>>>> # apt build-dep libloc >>>>>>>>>> # apt source --compile libloc >>>>>>>>>>=20 >>>>>>>>>> Interestingly the new version now also fails on mipsel, so = maybe it >>>>>>>>>> is a flaky >>>>>>>>>> test? >>>>>>>>>>=20 >>>>>>>>>> = https://buildd.debian.org/status/logs.php?pkg=3Dlibloc&arch=3Dmipsel >>>>>>>>>>=20 >>>>>>>>>> Given that it compiled before this means we should try to fix = the >>>>>>>>>> bug as it is >>>>>>>>>> blocks testing migration, otherwise: >>>>>>>>>>=20 >>>>>>>>>> https://tracker.debian.org/pkg/libloc >>>>>>>>>>=20 >>>>>>>>>> (The other option would be to request removal of the old = mipsel >>>>>>>>>> version.) >>>>>>>>>>=20 >>>>>>>>>>> Additionally, the packages don=E2=80=99t build for Debian = any more using >>>>>>>>>>> my script. >>>>>>>>>>>=20 >>>>>>>>>>> I opened a bug ticket with the error here: >>>>>>>>>>> https://bugzilla.ipfire.org/show_bug.cgi?id=3D12912 >>>>>>>>>>=20 >>>>>>>>>> Looks like you try to cross build (installing = crossbuild-essential- >>>>>>>>>> arm64:amd64), >>>>>>>>>> maybe that's currently broken. You can try installing = qemu-user- >>>>>>>>>> static and >>>>>>>>>> replace --host with --arch in debian/build.sh. >>>>>>>>>> Btw. sbuild updates the chroot before building so there = should be >>>>>>>>>> no need to >>>>>>>>>> throw it away (for a stable release). >>>>>>>>>>=20 >>>>>>>>>> Cheers Jochen >>>>>>>>>=20 >>>>>>>>> --=20 >>>>>>>>> Signal: +13478504872 >>>>>>>>> PGP fingerprint: EE66 20C7 136B 0D2C 456C 0A4D E9E2 8DEA 00AA = 5556 >>>>>>>>> = https://keys.openpgp.org/search?q=3DEE6620C7136B0D2C456C0A4DE9E28DEA00AA55= 56 >>>>>>>>=20 >>>>>>>>=20 >>>>>>=20 >>>>>> --=20 >>>>>> Signal: +13478504872 >>>>>> PGP fingerprint: EE66 20C7 136B 0D2C 456C 0A4D E9E2 8DEA 00AA = 5556 >>>>>=20 >>>=20 >>> --=20 >>> Signal: +13478504872 >>> PGP fingerprint: EE66 20C7 136B 0D2C 456C 0A4D E9E2 8DEA 00AA 5556 >=20 > --=20 > Signal: +13478504872 > PGP fingerprint: EE66 20C7 136B 0D2C 456C 0A4D E9E2 8DEA 00AA 5556