Re: [Dragora-users] Qi bug: all packages from blacklist have name by ${program}@${category}

[DustDFG]

On Wed, Aug 3, 2022 at 3:51 PM Matías Fonzo <selk@dragora.org> wrote:
>
> El 2022-08-03 00:50, DustDFG escribió:
> > On Tue, Aug 2, 2022 at 5:20 PM Matías Fonzo <selk@dragora.org> wrote:
> >>
> >> El 2022-08-02 00:52, DustDFG escribió:
> >> > On Mon, Aug 1, 2022 at 7:41 PM Matías Fonzo <selk@dragora.org> wrote:
> >> >>
> >> >> El 2022-07-23 01:38, DustDFG escribió:
> >> >> > Hello!
> >> >>
> >> >> Hi! :-)
> >> >>
> >> >> >
> >> >> > The subject line describes a problem.
> >> >>
> >> >> Where exactly? I can't find it.
> >> >>
> >> >
> >> > Ok. Maybe, it is because you got message from dragora-users...
> >> >
> >> > The subject line:
> >> >
> >> > "Qi bug: all packages from blacklist have name by
> >> > ${program}@${category}"
> >>
> >> I would appreciate any other details or description, line of code
> >> where
> >> the problem is, if it is in a configuration file, unexpected behavior.
> >> The subject line seems general, and I can't find it where it is.
> >>
> >
> > Ok. I don't know where mistake is but I can guess. It is related for
> > all packages from blacklist. All packages from blacklist have one
> > peculiarity. When you try to install \ upgrade \ build the package
> > installs to temporary location or have temporary .replace file and in
> > the end must receive final normal name. It looks like it doesn't
> > happen.
>
> If you can provide the steps you performed, I may be able to reproduce
> it.
>
>

I built the dragora. I opened OUTPUT.bootstrap/stage/usr/pkg and I saw
there qi@tools, musl@libs and other packages that follow normal name
convention