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: parted is missing from addons list
Date: Tue, 26 Jul 2022 12:20:53 +0200	[thread overview]
Message-ID: <6cba0c2a-447c-d156-881a-629984e4aeaf@ipfire.org> (raw)
In-Reply-To: <D7C53221-3A47-46E8-B4B8-13BA5B490A7A@ipfire.org>

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

Hi Michael,

On 26/07/2022 11:06, Michael Tremer wrote:
> Hello Adolf,
> 
> The rootfile is in a wrong place for this being a package:
> 
> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/rootfiles/common/parted;hb=f26f08b464287f91ff6df849b9e77d354e72d4cb
> 
> Since 2014 it is part of the core distribution:
Thanks for that info.
> 
> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=29d997e6c425b82303a4835dbcbd260611d12357
> 
> Are you expecting a package and is parted missing on your system?
On the forum a user said that he looked for parted in the addon list and couldn't find it.

I then looked in the wiki and parted is still shown as being an addon, no mention of being a core program.

Then I looked in the lfs and it has a PAK_VER number which is what addons usually have so I didn't look at the rootfile or its location.

Looking back at the git history, I see the move from packages to common in 2014 but the lfs file was not altered to remove the PAK_VER number or the @$(PAK) line. That is what confused me.

I will raise a patch to make the parted lfs file be inline with a core program and will also modify the wiki.

Obviously when I did updates of parted it didn't click in my mind that I was updating the lfs as an addon but the rootfile was in the common directory. Oh Well!! Brain must have been on autopilot.

Regards,
Adolf.
> 
> -Michael
> 
>> On 26 Jul 2022, at 10:03, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi all,
>>
>>  From a discussion on the forum it has been found that parted is no longer in the packages-list and doesn't show up on the pakfire list because of that.
>>
>> I don't know when it got removed from there but updates have been getting done to parted, last was in May this year by myself and it is still in the build.
>>
>> How do we get parted back into the packages-list on the server?
>>
>>
>> Regards,
>>
>> Adolf
>>
> 

  reply	other threads:[~2022-07-26 10:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  9:03 Adolf Belka
2022-07-26  9:06 ` Michael Tremer
2022-07-26 10:20   ` Adolf Belka [this message]
2022-07-26 16:15     ` Jon Murphy
     [not found] <A613FCCA-66E9-4E5E-A773-70299A25553B@gmail.com>
2022-07-26 16:30 ` 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=6cba0c2a-447c-d156-881a-629984e4aeaf@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