public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Results from latest test of pakfire-builder
Date: Fri, 03 Nov 2023 20:13:46 +0100	[thread overview]
Message-ID: <b7baad4c-e3ee-424f-849f-6b07ca459699@ipfire.org> (raw)
In-Reply-To: <E7A35B59-360B-4DE7-95F8-83F6F1747E5A@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 13213 bytes --]

Hi Michael,

On 03/11/2023 16:05, Michael Tremer wrote:
> Hello Adolf,
> 
>> On 2 Nov 2023, at 14:24, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> On 02/11/2023 09:25, Michael Tremer wrote:
>>> Hello Adolf,
>>> I have been looking into this in depth and I cannot find a way to make the builder work with all its features unless it is running as root.
>>> So please add a “sudo” to the command line and let me know if that brings you any further.
>>
>> I "know" sudo is required but for some reason I keep forgetting to use it with pakfire-builder. Sorry.
> 
> I added a check to the CLI tool which will simply complain if it is not running as root.
> 
> It would have been great if we could generally run pakfire as non-privileged users, but there are so many obstacles in the way right now that I do not think that it is a good investment of time to fix those. We are talking about many weeks of development time, and other things have a higher priority. We will however never get to a point where pakfire will be able to do all the things as a non-privileged user than root, because the kernel wouldn’t allow it.
> 
>> Maybe a check could be added to give an error if it is being run without root permissions.
> 
> Done.
> 
>> Anyway I will try and not repeat this mistake again.
>>
>> I have redone a git pull and build etc with the latest pakfire and then retried the pakfire-builder build beep/beep.nm command but with sudo.
> 
> Could you run the same thing with strace -o output.log between sudo and pakfire-builder?
> 
> It looks like something is getting stuck somewhere…

Just tried the same thing again, but via a different network connection 
and everything worked completely with no issues.

I successfully built beep with no issues, so it looks like everything is 
working as expected.

Not sure what happened with the previous attempt when it seemed to get 
stuck. I can't go back and try again on that network connection.

I also tried building sqlite which failed but that looks to be related 
to something about sqlite, rather than the pakfire code if I am 
understanding it correctly.

Running build stage 'install'
[   01:08.0316] + '[' -d /build/source/sqlite-autoconf-3430100/ ']'
[   01:08.0316] + cd /build/source/sqlite-autoconf-3430100/
[   01:08.0316] + mkdir -pv /var/tmp/pakfire-buildroot.X58n6n
[   01:08.0317] + make -O DESTDIR=/var/tmp/pakfire-buildroot.X58n6n install
[   01:08.0322] make[1]: Entering directory 
'/build/source/sqlite-autoconf-3430100'
[   01:08.0326]  /usr/bin/mkdir -p 
'/var/tmp/pakfire-buildroot.X58n6n/usr/lib64'
[   01:08.0328]  /bin/sh ./libtool   --mode=install /usr/bin/install -c 
  libsqlite3.la '/var/tmp/pakfire-buildroot.X58n6n/usr/lib64'
[   01:08.0353] ./libtool: line 3109: 0: Bad file descriptor
[   01:08.0354] make[1]: *** [Makefile:471: install-libLTLIBRARIES] Error 1
[   01:08.0354] make[1]: Leaving directory 
'/build/source/sqlite-autoconf-3430100'
[   01:08.0354] make: *** [Makefile:915: install-am] Error 2
Build stage 'install' failed with status 2
Could not build sqlite/sqlite.nm


Regards,

Adolf.

> 
> -Michael
> 
>> The following occurred:
>>
>> sudo pakfire-builder build beep/beep.nm
>> Package Database: stable 153k     0B/s 100%%
>> Package Database: testing [--------------------------] 0        0B/s ETA  : --:--:--   0%
>>
>> Nothing further happened after that. It never changed from 0%.
>>
>> The following was in the logs from the above command and output.
>>
>> pakfire[12076]: Mounting /var/tmp/pakfire-root-SZSk4U from pakfire_ramdisk (tmpfs - (null))
>> pakfire[12076]: Ramdisk mounted at /var/tmp/pakfire-root-SZSk4U ((null))
>> pakfire[12076]: Fetching SUBID from /etc/subuid for root
>> pakfire[12076]: Fetching SUBID from /etc/subgid for root
>> pakfire[12076]: RLIMIT_NOFILE set to 524288
>> pakfire[12076]: Pakfire initialized at 0x55f5470bdf10
>> pakfire[12076]:   user   = root (0)
>> pakfire[12076]:   group  = root (0)
>> pakfire[12076]:   arch   = x86_64 (x86_64)
>> pakfire[12076]:   path   = /var/tmp/pakfire-root-SZSk4U
>> pakfire[12076]: Reading configuration
>> pakfire[12076]: Reading repository configuration from /var/tmp/pakfire-root-SZSk4U/etc/pakfire/repos
>> pakfire[12076]:   Distribution: IPFire 3
>> pakfire[12076]:     name       = IPFire
>> pakfire[12076]:     id         = ipfire
>> pakfire[12076]:     version    = 3
>> pakfire[12076]:     version_id = 3
>> pakfire[12076]:     vendor     = IPFire Project
>> pakfire[12076]:     slogan     = An Open Source Firewall Solution
>> pakfire[12076]: Executing database query: PRAGMA foreign_keys = ON
>> pakfire[12076]: Executing database query: PRAGMA case_sensitive_like = ON
>> pakfire[12076]: Could not find last modification timestamp
>> pakfire[12076]: The database was last modified at 0
>> pakfire[12076]: Executing database query: PRAGMA secure_delete = OFF
>> pakfire[12076]: Executing database query: PRAGMA journal_mode = WAL
>> pakfire[12076]: Executing database query: BEGIN TRANSACTION
>> pakfire[12076]: Executing database query: CREATE TABLE IF NOT EXISTS settings(key TEXT, val TEXT)
>> pakfire[12076]: Executing database query: CREATE UNIQUE INDEX IF NOT EXISTS settings_key ON settings(key)
>> pakfire[12076]: Executing database query: CREATE TABLE IF NOT EXISTS packages(id              INTEGER PRIMARY KEY, name            TEXT, evr            TEXT, arch            TEXT, groups          TEXT, filename      TEXT, size            INTEGER, inst_size       INTEGER, digest_type     INTEGER, digest          BLOB, license         TEXT, summary         TEXT, description     TEXT, uuid            TEXT, vendor          TEXT, build_host      TEXT, build_time      INTEGER, installed       INTEGER, userinstalled   INTEGER, repository      TEXT, source_name     TEXT, source_evr      TEXT, source_arch     TEXT, distribution    TEXT)
>> pakfire[12076]: Executing database query: CREATE INDEX IF NOT EXISTS packages_name ON packages(name)
>> pakfire[12076]: Executing database query: CREATE UNIQUE INDEX IF NOT EXISTS packages_uuid ON packages(uuid)
>> pakfire[12076]: Executing database query: CREATE TABLE IF NOT EXISTS dependencies(pkg            INTEGER, type           TEXT, dependency TEXT, FOREIGN KEY (pkg) REFERENCES packages(id) ON DELETE CASCADE)
>> pakfire[12076]: Executing database query: CREATE INDEX IF NOT EXISTS dependencies_pkg_index ON dependencies(pkg)
>> pakfire[12076]: Executing database query: CREATE TABLE IF NOT EXISTS files(id                INTEGER PRIMARY KEY, path              TEXT, pkg               INTEGER, size              INTEGER, config INTEGER, datafile          INTEGER, mode              INTEGER, uname         TEXT, gname             TEXT, ctime             INTEGER, mtime            INTEGER, mimetype          TEXT, capabilities      TEXT, digest_sha2_512   BLOB, digest_sha2_256   BLOB, digest_blake2b512 BLOB, digest_blake2s256 BLOB, digest_sha3_512   BLOB, digest_sha3_256   BLOB, FOREIGN KEY (pkg) REFERENCES packages(id) ON DELETE CASCADE)
>> pakfire[12076]: Executing database query: CREATE INDEX IF NOT EXISTS files_pkg_index ON files(pkg)
>> pakfire[12076]: Executing database query: CREATE INDEX IF NOT EXISTS files_path_index ON files(path)
>> pakfire[12076]: Executing database query: CREATE TABLE IF NOT EXISTS scriptlets(id             INTEGER PRIMARY KEY, pkg            INTEGER, type           TEXT, scriptlet      TEXT, FOREIGN KEY (pkg) REFERENCES packages(id) ON DELETE CASCADE)
>> pakfire[12076]: Executing database query: CREATE INDEX IF NOT EXISTS scriptlets_pkg_index ON scriptlets(pkg)
>> pakfire[12076]: Setting arch to 'x86_64'
>> pakfire[12076]: Setting schema to '8'
>> pakfire[12076]: Setting last_modified_at to '1698931504'
>> pakfire[12076]: Executing database query: COMMIT
>> pakfire[12076]: Loading package database...
>> pakfire[12076]: Loading package database completed in 0.2360ms
>> pakfire[12076]: Executing database query: PRAGMA optimize
>> pakfire[12076]: Executing database query: PRAGMA wal_checkpoint = TRUNCATE
>> pakfire[12076]: Creating repository stable
>> pakfire[12076]: Creating repository testing
>> pakfire[12076]: Creating repository local
>> pakfire[12076]: Repository URL updated:
>> pakfire[12076]:   From: https://pakfire.ipfire.org/files/repos/ipfire-3/stable/%{arch}/
>> pakfire[12076]:   To  : https://pakfire.ipfire.org/files/repos/ipfire-3/stable/x86_64/
>> pakfire[12076]: Reading repository metadata from /root/.cache/pakfire/ipfire/3/x86_64/stable/repodata/repomd.json...
>> pakfire[12076]: Read package database from /root/.cache/pakfire/ipfire/3/x86_64/stable/repodata/2023-11-01-1226.1698841581.solv.zst...
>> pakfire[12076]: pool: repo_add_solv took 8 ms
>> pakfire[12076]: pool: repo size: 15 solvables
>> pakfire[12076]: pool: repo memory used: 5 K incore, 1 K idarray
>> pakfire[12076]: Repository URL updated:
>> pakfire[12076]:   From: https://pakfire.ipfire.org/files/repos/ipfire-3/testing/%{arch}/
>> pakfire[12076]:   To  : https://pakfire.ipfire.org/files/repos/ipfire-3/testing/x86_64/
>> pakfire[12076]: Reading repository metadata from /root/.cache/pakfire/ipfire/3/x86_64/testing/repodata/repomd.json...
>>
>>
>> Nothing further after that last line until I pressed Ctrl C after about 2 minutes.
>>
>> Here are the contents of the directories mentioned for the stable and testing repos.
>>
>>
>> ls -hal /root/.cache/pakfire/ipfire/3/x86_64/stable/repodata/
>> total 168K
>> drwxr-xr-x 2 root root 4.0K Nov  2 14:25 .
>> drwxr-xr-x 3 root root 4.0K Nov  2 14:25 ..
>> -rw------- 1 root root 153K Nov  2 14:25 2023-11-01-1226.1698841581.solv.zst
>> -rw------- 1 root root   94 Nov  2 14:25 repomd.json
>>
>>
>> ls -hal /root/.cache/pakfire/ipfire/3/x86_64/testing/repodata/
>> total 12K
>> drwxr-xr-x 2 root root 4.0K Nov  2 14:25 .
>> drwxr-xr-x 3 root root 4.0K Nov  2 14:25 ..
>> -rw------- 1 root root   94 Nov  2 14:25 repomd.json
>>
>>
>> Hope the above helps. If anything more info required just let me know.
>>
>> Regards,
>> Adolf.
>>
>>> -Michael
>>>> On 30 Oct 2023, at 17:56, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>> On 30/10/2023 11:01, Michael Tremer wrote:
>>>>> Hello Adolf,
>>>>> Thanks for giving this a try. Is there anything in the logs?
>>>>
>>>> In the forum I always remind people to look at the logs. On my Arch Linux systems I always search through the logs when I have a problem.
>>>>
>>>> For some reason with this pakfire package I seem to forget to look in the logs.
>>>>
>>>> Here is what I found when running pakfire-builder build beep/beep.nm (adding --debug made no difference)
>>>>
>>>> pakfire[2137]: Mounting /var/tmp/pakfire-root-KRBTNG from pakfire_ramdisk (tmpfs - (null))
>>>> pakfire[2137]: Could not mount /var/tmp/pakfire-root-KRBTNG: Operation not permitted
>>>> pakfire[2137]: Could not mount ramdisk at /var/tmp/pakfire-root-KRBTNG ((null)): Unknown error -1
>>>>
>>>> Regards,
>>>>
>>>> Adolf.
>>>>
>>>>> You can add —-debug to get some more output.
>>>>> Best,
>>>>> -Michael
>>>>>> On 29 Oct 2023, at 13:23, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> I updated my pakfire branch by doing a git pull with all the latest changes and built everything again.
>>>>>>
>>>>>> Then tested out by running sudo pakfire-builder build beep/beep.nm
>>>>>>
>>>>>> Result was again just going to the prompt with nothing happening.
>>>>>>
>>>>>> Ran the commands with gdb and got following result.
>>>>>>
>>>>>> sudo gdb pakfire-builder
>>>>>> GNU gdb (GDB) 13.2
>>>>>> Copyright (C) 2023 Free Software Foundation, Inc.
>>>>>> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
>>>>>> This is free software: you are free to change and redistribute it.
>>>>>> There is NO WARRANTY, to the extent permitted by law.
>>>>>> Type "show copying" and "show warranty" for details.
>>>>>> This GDB was configured as "x86_64-pc-linux-gnu".
>>>>>> Type "show configuration" for configuration details.
>>>>>> For bug reporting instructions, please see:
>>>>>> <https://www.gnu.org/software/gdb/bugs/>.
>>>>>> Find the GDB manual and other documentation resources online at:
>>>>>>      <http://www.gnu.org/software/gdb/documentation/>.
>>>>>>
>>>>>> For help, type "help".
>>>>>> Type "apropos word" to search for commands related to "word"...
>>>>>> Reading symbols from pakfire-builder...
>>>>>> (gdb) run build beep/beep.nm
>>>>>> Starting program: /usr/bin/pakfire-builder build beep/beep.nm
>>>>>> [Thread debugging using libthread_db enabled]
>>>>>> Using host libthread_db library "/usr/lib/libthread_db.so.1".
>>>>>> [New Thread 0x7ffff57dd6c0 (LWP 12756)]
>>>>>> [Thread 0x7ffff57dd6c0 (LWP 12756) exited]
>>>>>> [Inferior 1 (process 12752) exited with code 0377]
>>>>>> (gdb)
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>> Adolf.
>>>>>>
>>>>>> -- 
>>>>>> Sent from my laptop
>>>>>>
>>>>
>>>> -- 
>>>> Sent from my laptop
>>
>> -- 
>> Sent from my laptop
> 
> 

-- 
Sent from my laptop

  reply	other threads:[~2023-11-03 19:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29 13:23 Adolf Belka
2023-10-30 10:01 ` Michael Tremer
2023-10-30 17:56   ` Adolf Belka
2023-11-02  8:25     ` Michael Tremer
2023-11-02 14:24       ` Adolf Belka
2023-11-03 15:05         ` Michael Tremer
2023-11-03 19:13           ` Adolf Belka [this message]
2023-11-27  8:54             ` Adolf Belka

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=b7baad4c-e3ee-424f-849f-6b07ca459699@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.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