public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Hans-Christoph Steiner <hans@guardianproject.info>
Cc: "Stefan Schantl" <stefan.schantl@ipfire.org>,
	"Peter Müller" <peter.mueller@ipfire.org>,
	location@lists.ipfire.org
Subject: Re: Upload libloc to Debian
Date: Thu, 6 Mar 2025 10:48:19 +0000	[thread overview]
Message-ID: <968FAB68-729C-4367-BA24-FDC1D1F885A7@ipfire.org> (raw)
In-Reply-To: <9c740e42-cd03-428c-814a-fa8bdee99db9@guardianproject.info>

Hello Hans,

Thanks for your email.

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’t remember where I have left off. Time has been running out.

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.

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.

-Michael

> On 5 Mar 2025, at 18:25, Hans-Christoph Steiner <hans@guardianproject.info> wrote:
> 
> 
> Hey IPFire crew!
> 
> 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?
> 
> All the best,
> Hans
> 
> 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 <stefan.schantl@ipfire.org> wrote:
>>> 
>>> Hello Hans-Christoph,
>>> 
>>> a big thanks for writing and sharing your script. I've added it to the
>>> official libloc source code by the following commit:
>>> 
>>> ttps://git.ipfire.org/?p=location/libloc.git;a=commit;h=02a7d6ec0bb79f9
>>> 62ffe0746d311b3454b11a3db
>>> 
>>> Best regards,
>>> 
>>> -Stefan
>>>> 
>>>> Hey all,
>>>> 
>>>> 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.
>>>> 
>>>> 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.
>>>> 
>>>> .hc
>>>> 
>>>> Jochen Sprickerhof:
>>>>> Hi Michael,
>>>>> 
>>>>> * Michael Tremer <michael.tremer@ipfire.org> [2022-08-16 10:00]:
>>>>>>> https://buildd.debian.org/status/package.php?p=libloc
>>>>>> 
>>>>>> I installed a virtual machine with mips64el and the testsuite
>>>>>> weirdly runs
>>>>>> through.
>>>>> 
>>>>> I was able to reproduce it using ppc64el:
>>>>> 
>>>>> # echo "deb-src http://deb.debian.org/debian unstable main" >>
>>>>> /etc/apt/sources.list
>>>>> # apt update
>>>>> # apt build-dep libloc
>>>>> # apt source --compile libloc
>>>>> 
>>>>> Interestingly the new version now also fails on mipsel, so maybe it
>>>>> is a flaky
>>>>> test?
>>>>> 
>>>>> https://buildd.debian.org/status/logs.php?pkg=libloc&arch=mipsel
>>>>> 
>>>>> Given that it compiled before this means we should try to fix the
>>>>> bug as it is
>>>>> blocks testing migration, otherwise:
>>>>> 
>>>>> https://tracker.debian.org/pkg/libloc
>>>>> 
>>>>> (The other option would be to request removal of the old mipsel
>>>>> version.)
>>>>> 
>>>>>> Additionally, the packages don’t build for Debian any more using
>>>>>> my script.
>>>>>> 
>>>>>> I opened a bug ticket with the error here:
>>>>>> https://bugzilla.ipfire.org/show_bug.cgi?id=12912
>>>>> 
>>>>> 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).
>>>>> 
>>>>> Cheers Jochen
>>>> 
>>>> -- 
>>>> Signal: +13478504872
>>>> PGP fingerprint: EE66 20C7 136B 0D2C 456C  0A4D E9E2 8DEA 00AA 5556
>>>> https://keys.openpgp.org/search?q=EE6620C7136B0D2C456C0A4DE9E28DEA00AA5556
>>> 
>>> 
> 
> -- 
> Signal: +13478504872
> PGP fingerprint: EE66 20C7 136B 0D2C 456C  0A4D E9E2 8DEA 00AA 5556



  parent reply	other threads:[~2025-03-06 10:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <82DB10C8-A848-42EF-B395-3E27205E81D8@ipfire.org>
2022-07-02  6:57 ` Jochen Sprickerhof
2022-07-05 14:28   ` Michael Tremer
2022-07-06  7:41     ` Jochen Sprickerhof
2022-07-06  8:29       ` Michael Tremer
2022-07-07  5:46         ` Jochen Sprickerhof
2022-07-08  9:13           ` Michael Tremer
2022-07-08  9:58             ` Jochen Sprickerhof
2022-07-08 11:02               ` Michael Tremer
2022-07-08 12:56                 ` Jochen Sprickerhof
2022-07-13 12:12                   ` Michael Tremer
2022-07-22 21:06                     ` Jochen Sprickerhof
2022-08-16  9:00                       ` Michael Tremer
2022-08-17 13:17                         ` Jochen Sprickerhof
     [not found]                           ` <048f09d9-9985-a356-fed1-4cd8e286b87e@guardianproject.info>
2023-03-02 16:19                             ` Stefan Schantl
2023-03-02 17:26                               ` Michael Tremer
     [not found]                                 ` <9c740e42-cd03-428c-814a-fa8bdee99db9@guardianproject.info>
2025-03-06 10:48                                   ` Michael Tremer [this message]
2025-03-10 14:32                                     ` Michael Tremer
     [not found]                                       ` <6e7a9c4e-63c1-4896-bdb0-e621542ca3a7@guardianproject.info>
2025-03-19 10:41                                         ` Michael Tremer
     [not found]                                           ` <633f6312-7914-45db-882b-cb890a6f770c@guardianproject.info>
2025-03-23 12:18                                             ` Michael Tremer
2025-03-25 18:56                                               ` Valters Jansons
2025-03-26 10:17                                                 ` Michael Tremer
2025-03-27  0:25                                                   ` Valters Jansons
2025-03-27 16:39                                                     ` Michael Tremer
2025-03-27 16:55                                                       ` Jochen Sprickerhof
2025-03-28 12:39                                                         ` Michael Tremer
     [not found]                                                       ` <9068f306-8558-4913-8c4e-dad8dc0ee42d@guardianproject.info>
2025-03-28 13:02                                                         ` Michael Tremer
     [not found]                                                         ` <3209250b-4bb9-42f1-89d2-63ac86085148@guardianproject.info>
2025-03-28 13:05                                                           ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=968FAB68-729C-4367-BA24-FDC1D1F885A7@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=hans@guardianproject.info \
    --cc=location@lists.ipfire.org \
    --cc=peter.mueller@ipfire.org \
    --cc=stefan.schantl@ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox