I have uploaded an NMU fix to DELAYED/10 earlier today. Please, see
the last 2 commits on top of the following for details:
https://salsa.debian.org/patryk/libnitrokey
Hey Scott,
since nitrokey-app has been kickout of testing today, I want to ask
about the update? Do you need some help I could offer?
Best,
Jan
Am 21.08.20 um 00:01 schrieb Scott Kitterman:
> I will take care of it. The removal isn't scheduled for almost a month, so
> there is plenty of time.
I will take care of it. The removal isn't scheduled for almost a month, so
there is plenty of time.
Scott K
On Thursday, August 20, 2020 12:28:17 PM EDT Jan Luca Naumann wrote:
> Hey Scott,
>
> could you update the package? Since this is marked as RC bug,
> libnitrokey and all depending
Hey Scott,
could you update the package? Since this is marked as RC bug,
libnitrokey and all depending packages are kicked out of testing.
Best,
Jan
On Mon, 03 Aug 2020 13:54:57 + Scott Kitterman
wrote:
> This is probably a result of a new GCC version. C++ symbols can be painful
> to
This is probably a result of a new GCC version. C++ symbols can be painful to
manage. This will be trivial to update the next time I update the package.
Scott K
On August 3, 2020 9:15:16 AM UTC, Szczepan Zalega | Nitrokey
wrote:
>On 8/3/20 10:41 AM, Lucas Nussbaum wrote:
>>
On 8/3/20 10:41 AM, Lucas Nussbaum wrote:
> (optional=templinst|arch=!amd64 !arm64 !x32)
> (optional=templinst)
Hi!
As far as I see the problem comes from the listing format difference,
not the actual symbol change.
E.g.:
```
- (optional=templinst|arch=!amd64 !arm64
Source: libnitrokey
Version: 3.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory
7 matches
Mail list logo
