On So, 29 Sep 2013, Stephen Kitt wrote:
Uninstall the libc6-amd64:i386 package.
See http://lists.debian.org/debian-mentors/2013/03/msg00139.html.
But watch out for http://bugs.debian.org/699206 - make sure you have a root
sash running somewhere so you can relink
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Norbert Preining prein...@logic.at schrieb:
On So, 29 Sep 2013, Stephen Kitt wrote:
Uninstall the libc6-amd64:i386 package.
See http://lists.debian.org/debian-mentors/2013/03/msg00139.html.
But watch out for http://bugs.debian.org/699206 -
Hi Dominik,
Simply put: Because you made no effort to fix it :).
Thanks for the very useful comment.
Yes, I care for RC bugs in my own packages ... and that are quite
a lot. So no time to fix RC bugs of other maintainers.
Norbert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Norbert Preining prein...@logic.at schrieb:
Hi Dominik,
Simply put: Because you made no effort to fix it :).
Thanks for the very useful comment.
Yes, I care for RC bugs in my own packages ... and that are quite
a lot. So no time to fix RC bugs
severity 699206 serious
thanks
Hi Dominik,
first of all, please stop including all the email and bottom-posting,
this is a pain and against usual netiquette.
Then ...
On Mo, 30 Sep 2013, Dominik George wrote:
If you accuse everyone else in the community
[...]
I did not accuse anyone, I
Hi everyone,
second try, with more data ..
default package texinfo, I am importing a new upstream into my git,
no changes to debian/rules or debian/control, rebuild.
From the debian/control:
..
Package: info
...
Architecture: any
Multi-Arch: foreign
...
After building the package looks like:
On 2013-09-28 22:18 +0200, Norbert Preining wrote:
since a short time when I build a binary package on my running system,
I cannot install the created .deb anymore because it depends on
libc-amd64 (= some.version) which somehow is not what I have although
I am running amd64 sid.
Uninstall
On 29-09-13 08:40, Norbert Preining wrote:
What is going wrong here?
For whatever reason, the amd64 build is picking up i386 paths. I don't
know how that happens, except that I expect it is some multi-arch
twitch. I recommend you build your packages in a chroot to avoid this
(an other) issues. I
On Sun, 29 Sep 2013 08:58:36 +0200, Sven Joachim svenj...@gmx.de wrote:
On 2013-09-28 22:18 +0200, Norbert Preining wrote:
since a short time when I build a binary package on my running system,
I cannot install the created .deb anymore because it depends on
libc-amd64 (= some.version) which
Hi everyone,
since a short time when I build a binary package on my running system, I cannot
install the created .deb anymore because it depends on
libc-amd64 (= some.version)
which somehow is not what I have although I am running amd64 sid.
Any suggestions?
Thanks
Norbert
On Sun, Sep 29, 2013 at 12:18:03AM +0400, Norbert Preining wrote:
since a short time when I build a binary package on my running system, I
cannot install the created .deb anymore because it depends on
libc-amd64 (= some.version)
which somehow is not what I have although I am running amd64
11 matches
Mail list logo