From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] poppler: Fix rootfile.
Date: Sat, 14 May 2022 11:43:59 +0200 [thread overview]
Message-ID: <7a1e53bc-2403-d80b-c5d6-7ea9f57f977e@ipfire.org> (raw)
In-Reply-To: <afa98aea-5306-d424-77d0-087cd8c0abb6@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2571 bytes --]
Hi Stefan and All,
On 14/05/2022 11:12, Adolf Belka wrote:
> Hi Stefan and All,
>
> You have found several of these, all from patch submissions of mine.
>
> I have figured out what has been happening with these when I submitted them.
>
> When the logfile in the build has changed files with a + at the start of the line I go though the file with my simple xfce based editor mousepad.
>
> It has a find and replace function on it where I put + for the find and for the replace I left it empty and then I go one by one through the lines and if it is a library file, or other file that should be used then I replace the + with nothing.
>
> mousepad has obviously had some changes because now it no longer allows the replace box to be empty and if I leave it empty then it takes the first entry in the history list which at that time was #. If I was doing it now then the first entry in my history is xxxMACHINExxx so that would have been added in place of the + which would have been easier to spot that I had made a mistake
>
> Sorry for causing this problem.Unfortunately I am not sure how many I have messed up like this. I will try and have a search through my patch submission history and see if I can spot anything else.
>
I searched all the submissions that covered this period and it looks like all the ones where I added a # at the start of a needed library line have been found.
Regards,
Adolf.
> I will look for a new simple gui text editor that will allow me to do a replace with nothing or I will have to have a look at doing it in the terminal.
>
> Regards,
>
> Adolf.
>
> Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>
>
> On 13/05/2022 23:26, Stefan Schantl wrote:
>> libpoppler.so.120.0.0 contains all the functions and symbols which
>> are required by the tools linked against it.
>>
>> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
>> ---
>> config/rootfiles/common/poppler | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/config/rootfiles/common/poppler b/config/rootfiles/common/poppler
>> index 0ea058043..5c6f48e00 100644
>> --- a/config/rootfiles/common/poppler
>> +++ b/config/rootfiles/common/poppler
>> @@ -174,7 +174,7 @@ usr/lib/libpoppler-glib.so.8
>> usr/lib/libpoppler-glib.so.8.23.0
>> #usr/lib/libpoppler.so
>> usr/lib/libpoppler.so.120
>> -#usr/lib/libpoppler.so.120.0.0
>> +usr/lib/libpoppler.so.120.0.0
>> #usr/lib/pkgconfig/poppler-cpp.pc
>> #usr/lib/pkgconfig/poppler-glib.pc
>> #usr/lib/pkgconfig/poppler.pc
prev parent reply other threads:[~2022-05-14 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 21:26 Stefan Schantl
2022-05-14 9:12 ` Adolf Belka
2022-05-14 9:43 ` Adolf Belka [this message]
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=7a1e53bc-2403-d80b-c5d6-7ea9f57f977e@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