public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Valters Jansons <valter.jansons@gmail.com>
Cc: "Hans-Christoph Steiner" <hans@guardianproject.info>,
	"Stefan Schantl" <stefan.schantl@ipfire.org>,
	"Peter Müller" <peter.mueller@ipfire.org>,
	"Jochen Sprickerhof" <jspricke@debian.org>,
	location@lists.ipfire.org
Subject: Re: Upload libloc to Debian
Date: Wed, 26 Mar 2025 10:17:17 +0000	[thread overview]
Message-ID: <50924840-11D7-4132-9124-576EB7B13549@ipfire.org> (raw)
In-Reply-To: <CA+sCei1C8QXxh6MB9U7bJ5U8EpW2V5Qi+xvh7rpDvNEDNjcjVg@mail.gmail.com>

Hello Valters,

> On 25 Mar 2025, at 18:56, Valters Jansons <valter.jansons@gmail.com> wrote:
> 
> On Sun, Mar 23, 2025 at 2:18 PM Michael Tremer
> <michael.tremer@ipfire.org> wrote:
>> 
>>> On 23 Mar 2025, at 08:31, Hans-Christoph Steiner <hans@guardianproject.info> wrote:
>>> 
>>> 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.
> 
> Hans-Christoph, I opened
> https://salsa.debian.org/debian/libloc/-/merge_requests/3 for address
> endianess to be fixed (s390x failure: 10.0.0.0.in-addr.arpa. versus
> 0.0.0.10.in-addr.arpa.) I also opened
> https://salsa.debian.org/debian/libloc/-/merge_requests/2 for symbols
> to be fixed, resolving lintian's error. I further noticed the
> libloc-database watch file is not configured for filename format
> changes, so I opened
> https://salsa.debian.org/debian/libloc-database/-/merge_requests/2 for
> that. Let me know if you have any thoughts either in email or on the
> pull requests.

Thank you for helping to get the upstream version nice and shiny.

> Michael, I haven't looked further into it, but mips64el architecture
> failed to build due to undefined _ABIO32 and _ABIN32. If you have any
> proposals, they would presumably be good to include in the "upstream"
> project directly. The build log is visible at
> https://buildd.debian.org/status/fetch.php?pkg=libloc&arch=mips64el&ver=0.9.18-1&stamp=1742656796&raw=0

Yes, this is the error that I got. I did not look further into it because I am not aware of any users of MIPS for libloc, or even as a whole.

I assumed this was a problem in Python. Looking for the two constants, I am not sure which one to set, because hardcoding this would break the build for other MIPS architectures.

What would you suggest to fix this?

-Michael

> --Valters Jansons



  reply	other threads:[~2025-03-26 10:17 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
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 [this message]
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=50924840-11D7-4132-9124-576EB7B13549@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=hans@guardianproject.info \
    --cc=jspricke@debian.org \
    --cc=location@lists.ipfire.org \
    --cc=peter.mueller@ipfire.org \
    --cc=stefan.schantl@ipfire.org \
    --cc=valter.jansons@gmail.com \
    /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