Re: [gentoo-user] Re: Untrusted PGP signing key

[Consus]

On Sun, May 24, 2020 at 07:08:41PM +0100, Michael wrote:
> Check your /usr/share/openpgp-keys/gentoo-release.asc file.  This is the hash 
> I get here:
> 
> $ sha512sum gentoo-release.asc
> 3b168b7e43ad2cf4f042be585abc761c5786f55c94592dc916d13a1ef5557f047e614a7d70827471ace113f16eceb4e455228c4a5f7b9293f6a185a8e5183781
>   
> gentoo-release.asc

Same hash. Weird.

Re: [gentoo-user] Re: Untrusted PGP signing key

[Michael]

On Sunday, 24 May 2020 18:36:28 BST Nikos Chantziaras wrote:
> On 24/05/2020 20:15, Consus wrote:
> > I've got this today:
> > $ sudo emerge --sync
> > Checking signature ...
> > gpg: Signature made Sun 24 May 2020 03:56:07 MSK
> > gpg:using RSA key
> > E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
> > gpg: Good signature from "Gentoo ebuild repository signing key 
(Automated
> > Signing Key) " [unknown] gpg:
> > aka "Gentoo Portage Snapshot Signing Key (Automated Signing Key)"
> > [unknown] gpg: WARNING: Using untrusted key!
> > ...
> > 
> > Is this warning expected?
> 
> Certainly not.

Check your /usr/share/openpgp-keys/gentoo-release.asc file.  This is the hash 
I get here:

$ sha512sum gentoo-release.asc
3b168b7e43ad2cf4f042be585abc761c5786f55c94592dc916d13a1ef5557f047e614a7d70827471ace113f16eceb4e455228c4a5f7b9293f6a185a8e5183781
  
gentoo-release.asc

and these are the keys it contains:

$ gpg gentoo-release.asc 
gpg: enabled debug flags: memstat
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
gpg: keydb: handles=0 locks=0 parse=0 get=0
gpg:build=0 update=0 insert=0 delete=0
gpg:reset=0 found=0 not=0 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=37 cached=0 good=0 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
  outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x calls=0 bytes=0
gpg: secmem usage: 0/65536 bytes in 0 blocks
pub   rsa4096 2011-11-25 [C] [expires: 2021-01-01]
  DCD05B71EAB94199527F44ACDB6B8C1F96D8BF6D
uid   Gentoo Portage Snapshot Signing Key (Automated Signing Key)
sigDB6B8C1F96D8BF6D 2019-10-30   [selfsig]
sigDB6B8C1F96D8BF6D 2011-11-25   [selfsig]
sigDB6B8C1F96D8BF6D 2015-11-23   [selfsig]
sigDB6B8C1F96D8BF6D 2016-07-01   [selfsig]
sigDB6B8C1F96D8BF6D 2018-01-27   [selfsig]
sigDB6B8C1F96D8BF6D 2019-04-27   [selfsig]
uid   Gentoo ebuild repository signing key (Automated Signing Key) 

sigDB6B8C1F96D8BF6D 2019-10-30   [selfsig]
sigDB6B8C1F96D8BF6D 2019-01-01   [selfsig]
sigDB6B8C1F96D8BF6D 2019-04-27   [selfsig]
sigDB6B8C1F96D8BF6D 2018-07-04   [selfsig]
sub   rsa4096 2011-11-25 [S] [expires: 2021-01-01]
sigDB6B8C1F96D8BF6D 2019-04-27   [keybind]
sigDB6B8C1F96D8BF6D 2019-10-30   [keybind]
pub   dsa1024 2004-07-20 [SC] [expires: 2020-07-01]
  D99EAC7379A850BCE47DA5F29E6438C817072058
uid   Gentoo Linux Release Engineering (Gentoo Linux Release Signing 
Key) 
sig9E6438C817072058 2018-06-28   [selfsig]
sig9E6438C817072058 2006-08-16   [selfsig]
sig9E6438C817072058 2016-07-01   [selfsig]
sig9E6438C817072058 2004-07-20   [selfsig]
sig9E6438C817072058 2004-07-20   [selfsig]
sub   elg2048 2004-07-20 [E] [expires: 2020-07-01]
sig9E6438C817072058 2018-06-28   [keybind]
pub   rsa4096 2009-08-25 [SC] [expires: 2021-01-01]
  13EBBDBEDE7A12775DFDB1BABB572E0E2D182910
uid   Gentoo Linux Release Engineering (Automated Weekly Release Key) 

sigBB572E0E2D182910 2019-10-30   [selfsig]
sigBB572E0E2D182910 2013-08-24   [selfsig]
sigBB572E0E2D182910 2015-08-26   [selfsig]
sigBB572E0E2D182910 2009-08-25   [selfsig]
sigBB572E0E2D182910 2009-08-25   [selfsig]
sigBB572E0E2D182910 2017-08-22   [selfsig]
sigBB572E0E2D182910 2019-02-23   [selfsig]
sigBB572E0E2D182910 2019-04-27   [selfsig]
sigBB572E0E2D182910 2019-02-24   [selfsig]
sub   rsa2048 2019-02-23 [S] [expires: 2021-01-01]
sigBB572E0E2D182910 2019-04-27   [keybind]
sigBB572E0E2D182910 2019-10-30   [keybind]
pub   rsa4096 2018-05-28 [C] [expires: 2021-01-01]
  EF9538C9E8E64311A52CDEDFA13D0EF1914E7A72
uid   Gentoo repository mirrors (automated git signing key) 

sigA13D0EF1914E7A72 2019-10-30   [selfsig]
sigA13D0EF1914E7A72 2018-05-28   [selfsig]
sigA13D0EF1914E7A72 2018-05-29   [selfsig]
sigA13D0EF1914E7A72 2018-11-25   [selfsig]
sigA13D0EF1914E7A72 2019-02-23   [selfsig]
sigA13D0EF1914E7A72 2019-04-27   [selfsig]
sub   rsa2048 2018-05-28 [S] [expires: 2021-01-01]
sigA13D0EF1914E7A72 2019-04-27   [keybind]
sigA13D0EF1914E7A72 2019-10-30   [keybind]


More information:  https://www.gentoo.org/downloads/signatures/

signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Re: Untrusted PGP signing key

[Nikos Chantziaras]

On 24/05/2020 20:15, Consus wrote:

I've got this today:

$ sudo emerge --sync
Checking signature ...
gpg: Signature made Sun 24 May 2020 03:56:07 MSK
gpg:using RSA key 
E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
gpg: Good signature from "Gentoo ebuild repository signing key (Automated Signing 
Key) " [unknown]
gpg: aka "Gentoo Portage Snapshot Signing Key (Automated 
Signing Key)" [unknown]
gpg: WARNING: Using untrusted key!
...

Is this warning expected?


Certainly not.

Re: [gentoo-user] Seagate ST8000NM0065 PMR or SMR plus NAS SAS SATA question

[Dale]

David Haller wrote:
> Hello,
>
> On Fri, 22 May 2020, antlists wrote:
>> On 22/05/2020 19:23, Rich Freeman wrote:
>>> A big problem with drive-managed SMR is that it basically has to
>>> assume the OS is dumb, which means most writes are in-place with no
>>> trims, assuming the drive even supports trim.
>> I think the problem with the current WD Reds is, in part, that the ATA-4 spec
>> is required to support trim, but the ATA-3 spec is the current version.
>> Whoops ...
> ATA-8 is the current spec. Though practically unused. The used spec is
> ATA-7 in virtually all drives for IIRC the last 10ish years or so.
>
> Did you mean SATA specs? Well, then there's only SATA-1 (1.5GBit/s),
> SATA-2, (3.0GBit/s) and SATA-3 (6.0GBit/s), and of the latter SATA
> revision 3.1 introduced TRIM[2]. Oh, and rev. 3.3 introduced some
> extras for SMR [3].
>
> HTH,
> -dnh
>
> [1] https://en.wikipedia.org/wiki/Parallel_ATA
> [2] 
> https://en.wikipedia.org/wiki/Serial_ATA#SATA_revision_3.0_(6_Gbit/s,_600_MB/s,_Serial_ATA-600)
> [3] https://en.wikipedia.org/wiki/Serial_ATA#SATA_revision_3.3
>


Given the info in link 3, does that mean that OSs and their layers will
start adding options to help make SMR drives work better?  In other
words, file system support, LVM support if needed and maybe even
something that will make RAID setups work better?  From the way it
sounds, right now there is basically none of that.  Everything happens
on the drive and once it hits the limit of what it can handle, things
start screeching to a halt with the OS left in the dark about what is
going on exactly.  If SMR is going to be the new thing, it needs to work
better, RAID seems to really need that help. 

Dale

:-)  :-) 

[gentoo-user] Untrusted PGP signing key

[Consus]

Hi guys,

I've got this today:

$ sudo emerge --sync
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
 * Using keys from /usr/share/openpgp-keys/gentoo-release.asc
 * Refreshing keys via WKD ... [ ok ]
Fetching most recent snapshot ...
Trying to retrieve 20200523 snapshot from 
https://mirror.yandex.ru/gentoo-distfiles ...
Fetching file gentoo-20200523.tar.xz.md5sum ...
Fetching file gentoo-20200523.tar.xz.gpgsig ...
Fetching file gentoo-20200523.tar.xz ...
Checking digest ...
Checking signature ...
gpg: Signature made Sun 24 May 2020 03:56:07 MSK
gpg:using RSA key 
E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
gpg: Good signature from "Gentoo ebuild repository signing key 
(Automated Signing Key) " [unknown]
gpg: aka "Gentoo Portage Snapshot Signing Key 
(Automated Signing Key)" [unknown]
gpg: WARNING: Using untrusted key!
...

Is this warning expected?

Re: [gentoo-user] Seagate ST8000NM0065 PMR or SMR plus NAS SAS SATA question

[David Haller]

Hello,

On Sat, 23 May 2020, John Covici wrote:
>On Sat, 23 May 2020 11:39:40 -0400, David Haller wrote:
>> WD Red WD*EFRX are PMR.
>> WD Red WD*EFAX are SMR (AFAIK, could be, that some are PMR).
>> 
>> ISTR, that the "Red Pro" are all PMR (so far).
>
>How about WD4001FFSX-68JNUN0? I hope its pmr.

That's a "Red Pro" ...

-dnh

-- 
There are some people who clearly shouldn't be put in charge of
any office-equipment more technical than a blunt finger dipped
in water-soluble ink.-- Tanuki

Re: [gentoo-user] handbrake fails to compile

[Neil Bothwick]

On Sun, 24 May 2020 09:50:53 -0400, Jack wrote:

> > My question was:
> > "Is the bug tracker secureVud somehow against search machine robots
> > somehow or via robots.txt or is it me using a foreign language
> > wrongly?"

> In my opinion, neither.  I don't think they are explicitly blocked, but 
> search engines index pages by following links, so bug reports may well 
> not get indexed if they are not pointed to by some other page that does 
> get indexed.  How would a search engine find a bug page without knowing 
> how to search bugzilla?  I very often search both Google and bugzilla, 
> and often don't find any overlap.

b.g.o has a list of bugs reported in the last 24 hours or 7 days, so
seeding the search engine with those would find all bug reports in due
course. I often turn op reports on the bug trackers of other distros (and
github) when searching for help on an issue, so there isn't a general
lack of indexing of bug trackers.

Having said that, I always use the bgo search first as I find it superior
to Google's, unlike the forum search engine.


-- 
Neil Bothwick

"Unthinking respect for authority is the greatest enemy of truth."
 (Albert Einstein)


pgpEJJ1bmA8v4.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] handbrake fails to compile

[Jack]

On 5/24/20 8:33 AM, tu...@posteo.de wrote:

On 05/24 08:10, Pengcheng Xu wrote:

-Original Message-
From: tu...@posteo.de 
Sent: Sunday, May 24, 2020 7:16 PM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] handbrake fails to compile

On 05/24 11:54, Neil Bothwick wrote:

On Sun, 24 May 2020 12:44:20 +0200, tu...@posteo.de wrote:


media-video/handbrake-1.3.2:0/0::gentoo fails to compile (I am on
"unstable").

Searching online I found, that running perl-cleaner would fix that
problem which I done:

perl-cleaner --all

  - but without success.

Message was:

  * ERROR: media-video/handbrake-1.3.2::gentoo failed (compile phase):
  *   emake failed

I attached the build.log. If any further information are added I
will be happy to post them.

How can I fix that?

Try the patch in https://bugs.gentoo.org/724650

mkdir -p /etc/portage/patches/media-video/handbrake-1.3.2

and drop the patch into that directory.


--
Neil Bothwick

If a stealth bomber crashes in a forest, will it make a sound?

Hi Neil,

that works! Thanks  a lot.

A more general question: It is not the first time I searched for fixes for
compilation failures I came accross and I never got a link into the gentoo bug
tracker. As search terms I used "handbrake gentoo compile failure".

Is the bug tracker secureVud somehow against search machine robots somehow or
via robots.txt or is it me using a foreign language wrongly?

Instead, you may want to search for anything relevant on the Bugzilla, forums, 
and mailing list archives *first* :)

Hi,

I am a non native speaker -- when I asked using the wrong words.

My question was:
"Is the bug tracker secureVud somehow against search machine robots somehow or via 
robots.txt or is it me using a foreign language wrongly?"

Cheers!
Meino


In my opinion, neither.  I don't think they are explicitly blocked, but 
search engines index pages by following links, so bug reports may well 
not get indexed if they are not pointed to by some other page that does 
get indexed.  How would a search engine find a bug page without knowing 
how to search bugzilla?  I very often search both Google and bugzilla, 
and often don't find any overlap.


Jack

Re: [gentoo-user] handbrake fails to compile

[R]

tu...@posteo.de writes:

On 05/24 11:12, R wrote:
`cat 
/usr/portage/media-video/handbrake/handbrake-1.3.0-r2.ebuild`

Also, do you have media-video/handbrake-1.3.2-*r2* ?

then *r2 has been released secongs after my syincing...h...


o_O
My bad! I was too hasty and mis-typed.
It was actually *1.3.0-r2* I checked.

Soz.

R

Re: [gentoo-user] handbrake fails to compile

[tuxic]

On 05/24 08:10, Pengcheng Xu wrote:
> > -Original Message-
> > From: tu...@posteo.de 
> > Sent: Sunday, May 24, 2020 7:16 PM
> > To: gentoo-user@lists.gentoo.org
> > Subject: Re: [gentoo-user] handbrake fails to compile
> > 
> > On 05/24 11:54, Neil Bothwick wrote:
> > > On Sun, 24 May 2020 12:44:20 +0200, tu...@posteo.de wrote:
> > >
> > > > media-video/handbrake-1.3.2:0/0::gentoo fails to compile (I am on
> > > > "unstable").
> > > >
> > > > Searching online I found, that running perl-cleaner would fix that
> > > > problem which I done:
> > > >
> > > > perl-cleaner --all
> > > >
> > > >  - but without success.
> > > >
> > > > Message was:
> > > >
> > > >  * ERROR: media-video/handbrake-1.3.2::gentoo failed (compile phase):
> > > >  *   emake failed
> > > >
> > > > I attached the build.log. If any further information are added I
> > > > will be happy to post them.
> > > >
> > > > How can I fix that?
> > >
> > > Try the patch in https://bugs.gentoo.org/724650
> > >
> > > mkdir -p /etc/portage/patches/media-video/handbrake-1.3.2
> > >
> > > and drop the patch into that directory.
> > >
> > >
> > > --
> > > Neil Bothwick
> > >
> > > If a stealth bomber crashes in a forest, will it make a sound?
> > 
> > Hi Neil,
> > 
> > that works! Thanks  a lot.
> > 
> > A more general question: It is not the first time I searched for fixes for
> > compilation failures I came accross and I never got a link into the gentoo 
> > bug
> > tracker. As search terms I used "handbrake gentoo compile failure".
> > 
> > Is the bug tracker secureVud somehow against search machine robots somehow 
> > or
> > via robots.txt or is it me using a foreign language wrongly?
> 
> Instead, you may want to search for anything relevant on the Bugzilla, 
> forums, and mailing list archives *first* :)

Hi,

I am a non native speaker -- when I asked using the wrong words.

My question was: 
"Is the bug tracker secureVud somehow against search machine robots somehow or 
via robots.txt or is it me using a foreign language wrongly?"

Cheers!
Meino



> 
> > 
> > Cheers!
> > Meino
> > 
> > 
> > 
> > 
> 
> Regards,
> -- 
> Pengcheng Xu
> https://jsteward.moe

RE: [gentoo-user] handbrake fails to compile

[Pengcheng Xu]

> -Original Message-
> From: tu...@posteo.de 
> Sent: Sunday, May 24, 2020 7:16 PM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] handbrake fails to compile
> 
> On 05/24 11:54, Neil Bothwick wrote:
> > On Sun, 24 May 2020 12:44:20 +0200, tu...@posteo.de wrote:
> >
> > > media-video/handbrake-1.3.2:0/0::gentoo fails to compile (I am on
> > > "unstable").
> > >
> > > Searching online I found, that running perl-cleaner would fix that
> > > problem which I done:
> > >
> > > perl-cleaner --all
> > >
> > >  - but without success.
> > >
> > > Message was:
> > >
> > >  * ERROR: media-video/handbrake-1.3.2::gentoo failed (compile phase):
> > >  *   emake failed
> > >
> > > I attached the build.log. If any further information are added I
> > > will be happy to post them.
> > >
> > > How can I fix that?
> >
> > Try the patch in https://bugs.gentoo.org/724650
> >
> > mkdir -p /etc/portage/patches/media-video/handbrake-1.3.2
> >
> > and drop the patch into that directory.
> >
> >
> > --
> > Neil Bothwick
> >
> > If a stealth bomber crashes in a forest, will it make a sound?
> 
> Hi Neil,
> 
> that works! Thanks  a lot.
> 
> A more general question: It is not the first time I searched for fixes for
> compilation failures I came accross and I never got a link into the gentoo bug
> tracker. As search terms I used "handbrake gentoo compile failure".
> 
> Is the bug tracker secured somehow against search machine robots somehow or
> via robots.txt or is it me using a foreign language wrongly?

Instead, you may want to search for anything relevant on the Bugzilla, forums, 
and mailing list archives *first* :)

> 
> Cheers!
> Meino
> 
> 
> 
> 

Regards,
-- 
Pengcheng Xu
https://jsteward.moe


openpgp-digital-signature.asc
Description: PGP signature

Re: [gentoo-user] handbrake fails to compile

[Neil Bothwick]

On Sun, 24 May 2020 13:15:37 +0200, tu...@posteo.de wrote:

> A more general question: It is not the first time I searched for 
> fixes for compilation failures I came accross and I never got a 
> link into the gentoo bug tracker. As search terms I used
> "handbrake gentoo compile failure".

I found it by searching for "handbrake ALL" on b.g.o. The ALL means
closed bugs are also returned, which increases the number of results but
also means it returns the bug where your issue has been both reported and
fixed.


-- 
Neil Bothwick

Religious error: (A)tone, (R)epent, (I)mmolate?


pgpfiEY1g6Mi9.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] handbrake fails to compile

[tuxic]

On 05/24 11:12, R wrote:
> 
> tu...@posteo.de writes:
> 
> > media-video/handbrake-1.3.2:0/0::gentoo fails to compile (I am on
> > "unstable").
> > 
> 
> > Message was:
> > 
> >  * ERROR: media-video/handbrake-1.3.2::gentoo failed (compile  phase):
> >  *   emake failed
> 
> Funny, when I `cat` the ebuild, it has a few TODO items.
> And it says documentation building is broken; in the compile phase.
> 
> `cat /usr/portage/media-video/handbrake/handbrake-1.3.0-r2.ebuild`
> 
> ...
> src_compile(){
> ...
># TODO: Documentation building is currently broken, try tofix
> it.
>#
># if use doc ; then
>#   emake -C build doc
># fi
> 
> Also, do you have media-video/handbrake-1.3.2-*r2* ?
> You might want to trying syncing up again, if you don't.
> 
> > How can I fix that?
> Maybe try:
> `USE="-doc" emerge -av1 media-video/handbrake`
> 
> Or:
> `emerge --sync && #command above`
> 
> Regards,
> Roger
> 

Hi,

then *r2 has been released secongs after my syincing...h...

Syncing again currentlyplease hold the linebeep
Syncing again currentlyplease hold the linebeep
Syncing again currentlyplease hold the linebeep

...

# >eix handbrake
[I] media-video/handbrake
 Available versions:  (~)1.2.2-r3 (~)1.3.0-r2 (~)1.3.2 ***l {+fdk 
gstreamer gtk libav-aac numa nvenc x265}
 Installed versions:  1.3.2(01:08:05 PM 05/24/2020)(fdk gtk x265 -gstreamer 
-libav-aac -numa -nvenc)
 Homepage:http://handbrake.fr/
 Description: Open-source, GPL-licensed, multiplatform, 
multithreaded video transcoder

no update was triggered...handbrake-1.3.2-r2 is missing here.

I fixed that with the patch Neil gaves me just before. So handbrake
itsself is fixed locally...but where is handbrake-1.3.2-r2?

My sunc-command:
ionice -c 3 -n 13 nice -n 5 eix-sync ;ionice -c 3 -n 13 nice -n 5 emerge 
--update --newuse --deep --with-bdeps=y --tree --keep-going --backtrack=30 -v 
--verbose-conflicts -1 @world


Cheers!
Meino

Re: [gentoo-user] handbrake fails to compile

[tuxic]

On 05/24 11:54, Neil Bothwick wrote:
> On Sun, 24 May 2020 12:44:20 +0200, tu...@posteo.de wrote:
> 
> > media-video/handbrake-1.3.2:0/0::gentoo fails to compile (I am on
> > "unstable").
> > 
> > Searching online I found, that running perl-cleaner would fix that
> > problem which I done:
> > 
> > perl-cleaner --all
> > 
> >  - but without success.
> > 
> > Message was:
> > 
> >  * ERROR: media-video/handbrake-1.3.2::gentoo failed (compile phase):
> >  *   emake failed
> > 
> > I attached the build.log. If any further information are added I will
> > be happy to post them.
> > 
> > How can I fix that?
> 
> Try the patch in https://bugs.gentoo.org/724650
> 
> mkdir -p /etc/portage/patches/media-video/handbrake-1.3.2
> 
> and drop the patch into that directory.
> 
> 
> -- 
> Neil Bothwick
> 
> If a stealth bomber crashes in a forest, will it make a sound?

Hi Neil,

that works! Thanks  a lot.

A more general question: It is not the first time I searched for 
fixes for compilation failures I came accross and I never got a 
link into the gentoo bug tracker. As search terms I used
"handbrake gentoo compile failure".

Is the bug tracker secured somehow against search machine robots
somehow or via robots.txt or is it me using a foreign language
wrongly?

Cheers!
Meino

Re: [gentoo-user] handbrake fails to compile

[R]

tu...@posteo.de writes:

media-video/handbrake-1.3.2:0/0::gentoo fails to compile (I am 
on

"unstable").




Message was:

 * ERROR: media-video/handbrake-1.3.2::gentoo failed (compile 
 phase):

 *   emake failed


Funny, when I `cat` the ebuild, it has a few TODO items.
And it says documentation building is broken; in the compile 
phase.


`cat 
/usr/portage/media-video/handbrake/handbrake-1.3.0-r2.ebuild`


...
src_compile(){
...
   # TODO: Documentation building is currently broken, try to 
   fix it.

   #
   # if use doc ; then
   #   emake -C build doc
   # fi

Also, do you have media-video/handbrake-1.3.2-*r2* ?
You might want to trying syncing up again, if you don't.


How can I fix that?

Maybe try:
`USE="-doc" emerge -av1 media-video/handbrake`

Or:
`emerge --sync && #command above`

Regards,
Roger

Re: [gentoo-user] handbrake fails to compile

[Alarig Le Lay]

Hi,

On Sun 24 May 2020 12:44:20 GMT, tu...@posteo.de wrote:
> Message was:
> 
>  * ERROR: media-video/handbrake-1.3.2::gentoo failed (compile phase):
>  *   emake failed

No, the error is here:

> /usr/bin/g++ -pipe -Wl,-S -Wl,-O1 -Wl,--as-needed -fmessage-length=0 -Wall 
> -Wno-format-truncation -g0 -O3 -O2 -pipe -march=native -mfpmath=sse -msse2 
> -I./libhb/ -Iinclude -I/usr/include/libxml2 -o HandBrakeCLI -Wl,--start-group 
> test/parsecsv.o test/test.o ./libhb/libhandbrake.a -Llib -lass -lavformat 
> -lavfilter -lavcodec -lavutil -lswresample -lpostproc -lmp3lame -ldvdnav 
> -ldvdread -lfribidi -lswscale -lvpx -ltheoraenc -ltheoradec -lvorbis 
> -lvorbisenc -logg -lx264 -lbluray -lfreetype -lxml2 -lbz2 -lz -ljansson 
> -lharfbuzz -lopus -lspeex -llzma -ldav1d -lfontconfig -lpthread -ldl -lm 
> -Wl,--end-group
> /usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/../../../../x86_64-pc-linux-gnu/bin/ld:
>  ./libhb/libhandbrake.a(common.o): undefined reference to symbol 
> 'x265_api_query'
> /usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/../../../../x86_64-pc-linux-gnu/bin/ld:
>  /usr/lib64/libx265.so.179: error adding symbols: DSO missing from command 
> line
> collect2: error: ld returned 1 exit status
> make: *** [../test/module.rules:47: HandBrakeCLI] Error 1
> make: *** Waiting for unfinished jobs

It seems to be an error in the Makefile:
https://stackoverflow.com/questions/19901934/libpthread-so-0-error-adding-symbols-dso-missing-from-command-line

Regards,
-- 
Alarig

Re: [gentoo-user] handbrake fails to compile

[Neil Bothwick]

On Sun, 24 May 2020 12:44:20 +0200, tu...@posteo.de wrote:

> media-video/handbrake-1.3.2:0/0::gentoo fails to compile (I am on
> "unstable").
> 
> Searching online I found, that running perl-cleaner would fix that
> problem which I done:
> 
> perl-cleaner --all
> 
>  - but without success.
> 
> Message was:
> 
>  * ERROR: media-video/handbrake-1.3.2::gentoo failed (compile phase):
>  *   emake failed
> 
> I attached the build.log. If any further information are added I will
> be happy to post them.
> 
> How can I fix that?

Try the patch in https://bugs.gentoo.org/724650

mkdir -p /etc/portage/patches/media-video/handbrake-1.3.2

and drop the patch into that directory.


-- 
Neil Bothwick

If a stealth bomber crashes in a forest, will it make a sound?


pgpUlKIB28726.pgp
Description: OpenPGP digital signature

[gentoo-user] handbrake fails to compile

[tuxic]

Hi,

media-video/handbrake-1.3.2:0/0::gentoo fails to compile (I am on
"unstable").

Searching online I found, that running perl-cleaner would fix that
problem which I done:

perl-cleaner --all

 - but without success.

Message was:

 * ERROR: media-video/handbrake-1.3.2::gentoo failed (compile phase):
 *   emake failed

I attached the build.log. If any further information are added I will
be happy to post them.

How can I fix that?

Cheers!
Meino


 * Package:media-video/handbrake-1.3.2
 * Repository: gentoo
 * Maintainer: thev00...@gentoo.org
 * USE:abi_x86_64 amd64 elibc_glibc fdk gtk kernel_linux userland_GNU 
x265
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Using python3.8 to build
>>> Unpacking source...
>>> Unpacking handbrake-1.3.2.tar.bz2 to 
>>> /var/tmp/portage/media-video/handbrake-1.3.2/work
>>> Source unpacked in /var/tmp/portage/media-video/handbrake-1.3.2/work
>>> Preparing source in 
>>> /var/tmp/portage/media-video/handbrake-1.3.2/work/HandBrake-1.3.2 ...
 * Applying handbrake--remove-dvdnav-dup.patch ...
 [ ok ]
 * Applying handbrake--remove-faac-dependency.patch ...
 [ ok ]
 * Applying handbrake-1.3.0-dont-search-for-python.patch ...
 [ ok ]
 * Running eautoreconf in 
'/var/tmp/portage/media-video/handbrake-1.3.2/work/HandBrake-1.3.2/gtk' ...
 * Running autopoint --force ...
 [ ok ]
 * Running libtoolize --install --copy --force --automake ...
 [ ok ]
 * Running aclocal -I m4 ...
 [ ok ]
 * Running autoconf --force ...
 [ ok ]
 * Running autoheader ...
 [ ok ]
 * Running automake --add-missing --copy --foreign --force-missing ...
 [ ok ]
 * Running elibtoolize in: HandBrake-1.3.2/gtk/
 *   Applying portage/1.2.0 patch ...
 *   Applying sed/1.5.6 patch ...
 *   Applying as-needed/2.4.3 patch ...
>>> Source prepared.
>>> Configuring source in 
>>> /var/tmp/portage/media-video/handbrake-1.3.2/work/HandBrake-1.3.2 ...
probe: build tuple...(pass) x86_64-pc-linux-gnu
  + ./make/config.guess
  : b'x86_64-pc-linux-gnu'
find: ar...(pass) /usr/bin/ar
  : name[0] = ar
find: cp...(pass) /bin/cp
  : name[0] = cp
find: gm4...(pass) /usr/bin/m4
  : name[0] = gm4
  : name[1] = m4
find: mkdir...(pass) /bin/mkdir
  : name[0] = mkdir
find: gpatch...(pass) /usr/bin/patch
  : name[0] = gpatch
  : name[1] = patch
find: rm...(pass) /bin/rm
  : name[0] = rm
find: ranlib...(pass) /usr/bin/ranlib
  : name[0] = ranlib
find: strip...(pass) /usr/bin/strip
  : name[0] = strip
find: gtar...(pass) /bin/tar
  : name[0] = gtar
  : name[1] = tar
find: python3.8...(pass) /usr/bin/python3.8
  : name[0] = python3.8
find: gcc...(pass) /usr/bin/gcc
  : name[0] = gcc
find: gmake...(pass) /usr/bin/gmake
  : name[0] = gmake
  : name[1] = make
find: autoconf...(pass) /usr/bin/autoconf
  : name[0] = autoconf
find: automake...(pass) /usr/bin/automake
  : name[0] = automake
find: libtool...(pass) /usr/bin/libtool
  : name[0] = libtool
find: lipo...(fail) not found
  : name[0] = lipo
find: pkg-config...(pass) /usr/bin/pkg-config
  : name[0] = pkg-config
find: meson...(pass) /usr/bin/meson
  : name[0] = meson
find: nasm...(pass) /usr/bin/nasm
  : name[0] = nasm
find: ninja-build...(pass) /usr/bin/ninja
  : name[0] = ninja-build
  : name[1] = ninja
find: xcodebuild...(fail) not found
  : name[0] = xcodebuild
compute: available architectures...(pass) x86_64
  : 
probe: number of CPU cores...(pass) 12
  : 
probe: repo info...(fail) code 128
  + ./scripts/repo-info.sh .
  : b'fatal: not a git repository (or any parent up to mount point /)'
  : b'Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not 
set).'
  : b'fatal: not a git repository (or any parent up to mount point /)'
  : b'Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not 
set).'
  : b'Not a valid repository.'
probe: version.txt...(pass)
compute: project data...(pass) HandBrake (release)
  : 
version probe: autoconf 2.69.0...(pass) 2.69
  + /usr/bin/autoconf --version
  : b'autoconf (GNU Autoconf) 2.69'
  : b'Copyright (C) 2012 Free Software Foundation, Inc.'
  : b'License GPLv3+/Autoconf: GNU GPL version 3 or later'
  : b', 
'
  : b'This is free software: you are free to change and redistribute it.'
  : b'There is NO WARRANTY, to the extent permitted by law.'
  : b''
  : b'Written by David J. MacKenzie and Akim Demaille.'
version probe: automake 1.13.0...(pass) 1.16.2
  + /usr/bin/automake --version
  : b'automake (GNU automake) 1.16.2'
  : b'Copyright (C) 2020 Free Software Foundation, Inc.'
  : b'License GPLv2+: GNU GPL version 2 or later 
'
  : b'This is free software: you are free to change and redistribute it.'
  : b'There is NO WARRANTY, to the extent permitted by law.'
  : b''
  : b'Written by Tom Tromey '
  : b'   and Alexandre Duret-Lutz .'
version probe: pkg-config 0.27.0...(pass) 0.29.2
  + /usr/bin/pkg-config --version
  : b'0.29.2'
version probe: meson