from:"was was"

libX11.so.6 error

2017-09-13 Thread Francesco Pietra

Resent inserting the subjet

While attempting to create a virtual scree with the remote cluster, the
error arose:

/loader/pyi_importers.py", line 409, in load_module
> ImportError: /usr/lib/x86_64-linux-gnu/libX11.so.6: undefined symbol:
> xcb_poll_for_reply64
>

I am at debaian9 amd64. No problem with local graphiocs.

Thasnks for advice

francesco pietra

[no subject]

2017-09-13 Thread Francesco Pietra

While attempting to create a virtual scree with the remote cluster, the
error arose:

/loader/pyi_importers.py", line 409, in load_module
> ImportError: /usr/lib/x86_64-linux-gnu/libX11.so.6: undefined symbol:
> xcb_poll_for_reply64
>

I am at debaian9 amd64. No problem with local graphiocs.

Thasnks for advice

francesco pietra

Re: Updated installer images

2017-09-11 Thread Witold Baryluk

Hi John. Thanks a lot for these images for alpha, I will be trying them
soon probably, as I was unlucky with some previous ones. :)

Thanks.


2017-09-10 21:35 GMT+02:00 Anatoly Pugachev :

> On Sun, Sep 10, 2017 at 10:12 PM, Christoph Biedl
>  wrote:
> > John Paul Adrian Glaubitz wrote...
> >
> >> Please test and report back on the individual architecture
> >> mailing lists
> >
> > So far, the ride for ppc64 has been *extremely* painful. This is not
> > necessarly due to your efforts, but it feels a lot like nobody ever has
> > tried to set up Debian on a G5 using netboot.
> >
> > So far (might be incomplete, and I'm both tired and fairly upset):
> >
> > * Any reasonable documentation on this anywhere? No about how to set up
> >   DHCP/TFTP server, I've done this many time. But what about which files
> >   are needed, and how to provide a netboot-adjusted yaboot.conf, and
> >   mostly: How to make yaboot make using it?
> >
> > * The OF bootloader needs two rounds to load yaboot.
> >
> > * yaboot should either get a decent on-line help or see bitrot.
> >
> > * yaboot's "conf /path/to/config" command, when initially using netboot,
> >   happiliy ignores the file name but retrieves 01-xx-yy-xx-yy-xx-yy
> >   using TFTP instead.
> >
> > * After a lot of trickery, the installer's vmlinux now gets loaded. At a
> >   whopping 6 kbyte/sec (yes: six kilobytes). Just to remind you, kernel
> >   and initrd take some 35 megabytes, and the G5 has already turned to
> >   airplane mode. My neighbors will love me.
> >
> > This isn't getting anywhere useful soon.
>
> I was able to install netboot sparc64 ldom (but not latest sid version
> , which is too big to load by OBP. There's also #645657 debian bug,
> but somehow it got closed).
>
> Also, installed ppc64 LPAR, failed to install yaboot and using grub2
> on Power8 server, but that installation wasn't netboot, but usual
> iso/cdrom install.
>
> I could probably try to install test ppc64 lpar with netboot just to
> check how it will go, but i need to know where do i get netboot image,
> since https://cdimage.debian.org/cdimage/ports/ does not have netboot
> images.
>
> Thanks
>
>


-- 
Witold Baryluk
My PGP keys for 2017-02-17 - 2019-02-17:
5B8C 48CB 8B2F CF53 CA55  0995 16D9 6FA2 20A8 F130
https://functor.xyz/pgp/witold.baryluk-gmail.gpg.asc
https://keys.mailvelope.com/pks/lookup?op=get=0x16D96FA220A8F130

Re: Updated installer images

2017-09-10 Thread Anatoly Pugachev

On Sun, Sep 10, 2017 at 10:12 PM, Christoph Biedl
 wrote:
> John Paul Adrian Glaubitz wrote...
>
>> Please test and report back on the individual architecture
>> mailing lists
>
> So far, the ride for ppc64 has been *extremely* painful. This is not
> necessarly due to your efforts, but it feels a lot like nobody ever has
> tried to set up Debian on a G5 using netboot.
>
> So far (might be incomplete, and I'm both tired and fairly upset):
>
> * Any reasonable documentation on this anywhere? No about how to set up
>   DHCP/TFTP server, I've done this many time. But what about which files
>   are needed, and how to provide a netboot-adjusted yaboot.conf, and
>   mostly: How to make yaboot make using it?
>
> * The OF bootloader needs two rounds to load yaboot.
>
> * yaboot should either get a decent on-line help or see bitrot.
>
> * yaboot's "conf /path/to/config" command, when initially using netboot,
>   happiliy ignores the file name but retrieves 01-xx-yy-xx-yy-xx-yy
>   using TFTP instead.
>
> * After a lot of trickery, the installer's vmlinux now gets loaded. At a
>   whopping 6 kbyte/sec (yes: six kilobytes). Just to remind you, kernel
>   and initrd take some 35 megabytes, and the G5 has already turned to
>   airplane mode. My neighbors will love me.
>
> This isn't getting anywhere useful soon.

I was able to install netboot sparc64 ldom (but not latest sid version
, which is too big to load by OBP. There's also #645657 debian bug,
but somehow it got closed).

Also, installed ppc64 LPAR, failed to install yaboot and using grub2
on Power8 server, but that installation wasn't netboot, but usual
iso/cdrom install.

I could probably try to install test ppc64 lpar with netboot just to
check how it will go, but i need to know where do i get netboot image,
since https://cdimage.debian.org/cdimage/ports/ does not have netboot
images.

Thanks

Re: Updated installer images

2017-09-10 Thread Christoph Biedl

John Paul Adrian Glaubitz wrote...

> Please test and report back on the individual architecture
> mailing lists

So far, the ride for ppc64 has been *extremely* painful. This is not
necessarly due to your efforts, but it feels a lot like nobody ever has
tried to set up Debian on a G5 using netboot.

So far (might be incomplete, and I'm both tired and fairly upset):

* Any reasonable documentation on this anywhere? No about how to set up
  DHCP/TFTP server, I've done this many time. But what about which files
  are needed, and how to provide a netboot-adjusted yaboot.conf, and
  mostly: How to make yaboot make using it?

* The OF bootloader needs two rounds to load yaboot.

* yaboot should either get a decent on-line help or see bitrot.

* yaboot's "conf /path/to/config" command, when initially using netboot,
  happiliy ignores the file name but retrieves 01-xx-yy-xx-yy-xx-yy
  using TFTP instead.

* After a lot of trickery, the installer's vmlinux now gets loaded. At a
  whopping 6 kbyte/sec (yes: six kilobytes). Just to remind you, kernel
  and initrd take some 35 megabytes, and the G5 has already turned to
  airplane mode. My neighbors will love me.

This isn't getting anywhere useful soon.

Christoph


signature.asc
Description: Digital signature

Updated installer images

2017-09-08 Thread John Paul Adrian Glaubitz


Hi!

I have generated an updated set of debian-installer images for
Debian Ports which also now includes alpha [1].

I have fixed the installation issues on hppa and sparc64, in
both cases the bootloader installer was missing.

ppc64 has still some issues with the partition manager, but I'm
working on fixing that.

Please test and report back on the individual architecture
mailing lists, i.e. please don't post to debian-ports@l.d.o
as this reaches the mailing lists of all ports.

Adrian


[1] https://cdimage.debian.org/cdimage/ports/


--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

New download location for Debian Ports ISOs

2017-09-06 Thread John Paul Adrian Glaubitz

Hi!

I am cross-posting this to debian-ports@l.d.o because it affects all
Debian Ports architectures.

As of today, we will be using Debian's official cdimage mirror to host
the installation images for Debian Ports, the images can be found in [1].

I have uploaded images for hppa, m68k, ppc64 and sparc64. I am working
on uploading more images. Images for alpha are currently missing due to
issues with the Linux kernel packages which fails to build on alpha at
the moment.

Please test the images as thoroughly as you can and report your results
to the appropriate architecture-specific mailing lists. Please do not
post to this mailing list, debian-ports@l.d.o, as this will cross-post
your mail to ALL Debian Ports architectures mailing lists.

A huge thanks to Steve McIntyre and the Debian Sysadmins for providing
us access to the official cdimage mirror.

Thanks,
Adrian

> [1] https://cdimage.debian.org/cdimage/ports/

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#870035: dropbear-bin: ftbfs on x32

2017-07-29 Thread Matthias Fritzsche

Package: dropbear-bin
Version: 2017.75-1
Severity: normal
User: debian-amd64@lists.debian.org
Usertags: x32

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

I just saw that there is only an very old version of dropbear in the
repository and tried to build current 2017.75. This fails in the file
tomcrypt_macros.h with an error similar to
https://wiki.debian.org/X32Port#amd64_assembly.

Attached is a full build log.

kind regards
txt.file

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEE1NOunmXPptEkFyWqOb+C9VkIZegFAll8LcUUHHR4dC5maWxl
QHR4dGZpbGUuZXUACgkQOb+C9VkIZehnIBAAkMy+0k+NrJhNyf5ep1bxD/54L+et
FVGGg1f80UophMfnC83EH8UjapvJ1aNtmizpt4dcFMcnaneMFzPd6FZZZwUueNJ4
4F5yQJfIh4SnJBWWlOvjGH9WNMTXkWx6RnwZFV+Z1ITSCorgf70bjM7GNKg2WR5D
8yQ2sU5VVp50/Li2RWR2pOewbupyWaor0XV6q1YLb60qFoGcHiZoe/b9qh5zs/ZP
2mkb5sh2oUnDi2WhbwLnEYZReMwoFSdtJm8OIO2zCS5oskcNqEICB53b6seIuKe5
Th+cLM/MOaFWsr36qlLnjF546ocBiu54Vk48Hc7Cba+pH7YzxPNm+cz27nhIVh6M
VlkpuInLwDXgCtMtnAy7QgLPMzitfoGhMqfN52srdPFDIevEcVyzsO7zvyD/vTqA
0E353uNX83LxuDVEbwEYUwZjSk/x3agqvvJUDNnJbIGeZ61vJmNrVSH1m4wWVUzb
AJr8ZFdUd/fYH1CMklhcND5xO2KDDOmMa/vf0MxnYx/0txJ0wfvQNa2G6qQsFIuS
8x3CDsIp6f3cSfEXdk7cOZHQ0e8kuQD4JTNQ5wvOy7FF9AW2pCE83AoJMik9jsIt
0BgoUKtyc36aG103z1Nw9ke9yczuTD48ntSDHRIwcfk6RuQmGqEPrHfz67+lGJoI
hNMxP9sTE8QjRSM=
=SRln
-END PGP SIGNATURE-
 dpkg-buildpackage -rfakeroot -us -uc
dpkg-buildpackage: info: source package dropbear
dpkg-buildpackage: info: source version 2017.75-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Guilhem Moulin 
 dpkg-source --before-build dropbear-2017.75
dpkg-buildpackage: info: host architecture x32
 fakeroot debian/rules clean
dh clean --with=autoreconf
   dh_testdir
   dh_auto_clean
   dh_autoreconf_clean
   dh_clean
 dpkg-source -b dropbear-2017.75
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building dropbear using existing 
./dropbear_2017.75.orig.tar.bz2
dpkg-source: info: building dropbear in dropbear_2017.75-1.debian.tar.xz
dpkg-source: info: building dropbear in dropbear_2017.75-1.dsc
 debian/rules build
dh build --with=autoreconf
   dh_testdir
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/home/txt/workspace/dropbear-2017.75'
dh_auto_configure -- --enable-bundled-libtom \
  CC='gcc' CFLAGS='-g -O2 
-fdebug-prefix-map=/home/txt/workspace/dropbear-2017.75=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -DSFTPSERVER_PATH="\"/usr/lib/sftp-server\""' \
  
./configure --build=x86_64-linux-gnux32 --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnux32 
--libexecdir=\${prefix}/lib/x86_64-linux-gnux32 --disable-maintainer-mode 
--disable-dependency-tracking --enable-bundled-libtom CC=gcc "CFLAGS=-g -O2 
-fdebug-prefix-map=/home/txt/workspace/dropbear-2017.75=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -DSFTPSERVER_PATH=\"\\\"/usr/lib/sftp-server\\\"\""
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether make sets $(MAKE)... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking build system type... x86_64-pc-linux-gnux32
checking host system type... x86_64-pc-linux-gnux32
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking for install... install
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether __UCLIBC__ is declared... no
checking for crypt... no
checking for crypt in -lcrypt... yes
checking for deflate in -lz... yes
configure: Enabling zlib
configure: Disabling PAM
configure: Using openpty if available
checking for library containing openpty... -lutil
configure: Enabling syslog
checking shadow.h usability... yes
checking shadow.h presence...

Re: dropbear: tfbfs on x32

2017-07-29 Thread John Paul Adrian Glaubitz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello Matthias!

On 07/29/2017 07:55 AM, txt.file wrote:
> I just saw that there is only an very old version of dropbear in the 
> repository and tried to build current 2017.75. This fails in the file 
> tomcrypt_macros.h with an error similar to 
> https://wiki.debian.org/X32Port#amd64_assembly.

Please refrain from posting such issues to debian-po...@lists.debian.org
as this is a list which cross-posts to all ports mailing lists.

Instead, just file a bug report against dropbear and tag it as "x32"

User: debian-amd64@lists.debian.org
Usertags: x32
X-Debbugs-CC: debian-amd64@lists.debian.org

If you want to reach Debian Ports, please use debian-ports-devel@l.d.o
instead.

Thanks,
Adrian

- -- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAll8KMQACgkQdCY7N/W1
+RPDdg//cXTyzqTgV6Q92bliaNLpnHFQUSfByNxVuMnJUU9cSfQ6DSNDZbmE0Sz3
P1Vdy3ozfkWMDJmP4uBhclG2mEVRFwRA7aRVBBVP/+ibdsTYFTU31yWVVvdrHpkk
k5W5qU8RVK8epAw1g6WGF7oxz1aixXIQF8yHamK9HI6Ywi3lbFB0J+kHHdxWXmt7
gRtWd0YCzcYESRg7bMC6fP3q8fEMeU8sSxQ6MDkfY6NpYw4DmE7vjUzV4vpVgapi
bF1IFqN7xWoLPCy5IiPjKYbKyAISHpFEPMPi1DAPXuClXLsfZtK3jJDRw9iddj6Y
adnG+NuAcoNM+HYRfrezKkZuLGBm1NJqXjcyTf17cIrQIGIZvTi4R+Lop85U7ymi
9dIHu3xF0zG5FbviKdpzjBIHMndblS5cGzuyRy+NJL1pUVyfzOf/KgVqVlcCOM9p
4f2vT+pT5+X3ZzocxQ/Kf6ySqGKnqznXhj+lGOs1Ix/dNpuyp1UyQouyAYjxCXdi
GTuDDrODb+F1iJKkMYdO76FgbPVLby8vRDrGW33iwKMUHslPAxR7GM88A2DbbM9s
v7BG+jQkTleIvoNNrWLWrYCX/ZYTQHHlFX6qppstge1pAzukZO74E+oJPKvGNrre
tuFFkFKU6yarOilJP7uB9kHR0MaDzFhAVSpWJPZF79pm2AhwcF4=
=rX5e
-END PGP SIGNATURE-

I just saw that there is only an very old version of dropbear in the
repository and tried to build current 2017.75. This fails in the file
tomcrypt_macros.h with an error similar to
https://wiki.debian.org/X32Port#amd64_assembly.

Attached is a full build log.

kind regards
txt.file
dpkg-buildpackage -rfakeroot -us -uc
dpkg-buildpackage: info: source package dropbear
dpkg-buildpackage: info: source version 2017.75-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Guilhem Moulin
dpkg-source --before-build dropbear-2017.75
dpkg-buildpackage: info: host architecture x32
fakeroot debian/rules clean
dh clean --with=autoreconf
dh_testdir
dh_auto_clean
dh_autoreconf_clean
dh_clean
dpkg-source -b dropbear-2017.75
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building dropbear using existing ./dropbear_2017.75.orig.tar.bz2
dpkg-source: info: building dropbear in dropbear_2017.75-1.debian.tar.xz
dpkg-source: info: building dropbear in dropbear_2017.75-1.dsc
debian/rules build
dh build --with=autoreconf
dh_testdir
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/home/txt/workspace/dropbear-2017.75'
dh_auto_configure -- --enable-bundled-libtom \
CC='gcc' CFLAGS='-g -O2 -fdebug-prefix-map=/home/txt/workspace/dropbear-2017.75=. -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -DSFTPSERVER_PATH="\"/usr/lib/sftp-server\""' \

./configure --build=x86_64-linux-gnux32 --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnux32 --libexecdir=\${prefix}/lib/x86_64-linux-gnux32 --disable-maintainer-mode --disable-dependency-tracking --enable-bundled-libtom CC=gcc "CFLAGS=-g -O2 -fdebug-prefix-map=/home/txt/workspace/dropbear-2017.75=. -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -DSFTPSERVER_PATH=\"\\\"/usr/lib/sftp-server\\\"\""
configure: WARNING: unrecognized options: --disable-silent-rules, --disable-maintainer-mode, --disable-dependency-tracking
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether make sets $(MAKE)... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking build system type... x86_64-pc-linux-gnux32
checking host system type... x86_64-pc-linux-gnux32
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking for install... install
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether __UCLIBC__ is declared... no
checking for crypt... no
checking for crypt in -lcrypt... yes
checking for deflate in -lz... yes
configure: Enabling zlib
configure: Disabling PAM
configure: Using openpty if available
checking for library containing openpty... -lutil
configure: Enabling syslog
checking shadow.h usability... yes
checking shadow.h presence... yes
checking for shadow.h... yes
configure: Using shadow passwords if available
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking netinet/tcp.h usability... yes
checking netinet/tcp.h presence... yes
checking for netinet/tcp.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking for unistd.h... (cached) yes
checking crypt.h usability...

< 1 2 3 4 5 6 7 8 9 10 >

301 - 400 of 22900 matches

Mail list logo