libX11.so.6 error

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

[no subject]

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.

Re: Updated installer images

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 >

Re: Updated installer images

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

Re: Updated installer images

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

Updated installer images

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

New download location for Debian Ports ISOs

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

Bug#870035: dropbear-bin: ftbfs on x32

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

Re: dropbear: tfbfs on x32

-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 >

dropbear: tfbfs on x32

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

Re: updating mysql failed.. debian 9

On Tue, Jul 18, 2017 at 03:32:07AM -0700, DutchGigalo wrote: > updating mysql failed.. debian 9 > > Preparing to unpack .../mysql-community-server_5.7.19-1debian9_amd64.deb ... > > dpkg: error processing archive >

updating mysql failed.. debian 9

updating mysql failed.. debian 9 Preparing to unpack .../mysql-community-server_5.7.19-1debian9_amd64.deb ... dpkg: error processing archive /var/cache/apt/archives/mysql-community-server_5.7.19-1debian9_amd64.deb (--unpack): subprocess new pre-installation script returned

Re: Actualizar esta de moda

Hola,Hace 16 años que presto asesorías en el área del diseño de sitios web a pequeños y medianos empresarios.No soy un diseñador cualquiera, con el tiempo he logrado diferenciarme del resto. Aquí algunas razones: Soy fanático de la puntualidad. Si no te gusta no lo pagas. Primero

BAG in DEBIAN 8.8

Пересылаемое сообщение От кого: МБУЗ ГКБ № 1 Кому: debian-de...@lists.debian.org Дата: Пятница, 16 июня 2017, 19:05 +03:00 Тема: Help me Hi no work in Debian 8.8 No start firebird 2.5 classic and super error work@work-desktop ~ $ sudo dpkg-reconfigure

Re: mpich FTBFS on sh4: MPIUI_Thread TLS definition mismatches tbss

Drew Parsons writes: > The link error suggests 2 different versions of MPIUI_Thread are used. > But I can only see a definition in src/util/thread/mpiu_thread.c. > src/mpi/comm does not refer to it, and comm_rank.c does not use any > MPIU object. So the error message

about nvidia-toolkit

Hi: My question is whether the nvidia-toolkit could be removed from the installation of stretch amd64. I use GTX 680 for only number crunching, not development. If so, there is any special protocol for removing the nvidia-toolkit withouth harming the GTX680 functionality as above said. The

Lonely housewifes hook up

I need the hookup

Re: debian9 amd64 failure to connect to lvmetad, falling back to device scanning

NEW:I have finally obtained a red-labeled line on booting, telling "Failed to load console system Reboot Logging" This implies that it is not merely a problem of console ownership. A rapid web survey failed to provide indications as to having the console loaded during booting on Debian amd64

Re: debian9 amd64 failure to connect to lvmetad, falling back to device scanning

I should add that, once the Xserver is launched by the aid of the other computer on LAN, the server works autonomously from its keyboard and terminals. I could run at an impressively high speed a most recent special form of molecular dynamics on the six cores, six threads, and the two GTX680

Re: debian9 amd64 failure to connect to lvmetad, falling back to device scanning

> > Your server is booting, but not providing a login > I forgot to say that the request of username/password does indeed appear during booting but transiently, followed by that interminable access to disk. I was unable to stop (with Ctrl-S) at the login request. Can you log in on > a VT console

Re: debian9 amd64 failure to connect to lvmetad, falling back to device scanning

On Fri, May 19, 2017 at 11:12:25AM +0200, Francesco Pietra wrote: "It is not required for normal usage" The fact is that the X79-based computer does not offer a login possibility, it goes to disk scanning (kernel et al) for hours (at least 4hr). Access to file was only possible

Re: debian9 amd64 failure to connect to lvmetad, falling back to device scanning

> > "It is not required for normal usage" > The fact is that the X79-based computer does not offer a login possibility, it goes to disk scanning (kernel et al) for hours (at least 4hr). Access to file was only possible from a LAN-connected other computer (laptop VAIO) or booting from Super Grub2

Re: debian9 amd64 failure to connect to lvmetad, falling back to device scanning

I forgot to mention that ---changing in /etc/lvm from "use_lvmetad=1" to "use_lvmetad=0" or commenting out in /etc/defaut/grub ---# GRUB_CMDLINE_LINUX_DEFAULT="quiet" did not solve the problem fp On Fri, May 19, 2017 at 10:21 AM, Francesco Pietra wrote: > I

Re: debian9 amd64 failure to connect to lvmetad, falling back to device scanning

On Fri, May 19, 2017 at 10:17:44AM +0200, Francesco Pietra wrote: Hello: On a vintage VAIO I have no problems with amd64 stretch. With a raid1-based on the X79 chip, upgrading from jessie to stretch (I need a higher CUDA version than available on jessie for latest experimental NAMD

Re: debian9 amd64 failure to connect to lvmetad, falling back to device scanning

I understand that udev is in focus, however I don't know how to marriage lvmetad and udev francesco pietra On Fri, May 19, 2017 at 10:17 AM, Francesco Pietra wrote: > Hello: > On a vintage VAIO I have no problems with amd64 stretch. With a > raid1-based on the X79 chip,

debian9 amd64 failure to connect to lvmetad, falling back to device scanning

Hello: On a vintage VAIO I have no problems with amd64 stretch. With a raid1-based on the X79 chip, upgrading from jessie to stretch (I need a higher CUDA version than available on jessie for latest experimental NAMD molecular dynamics) went on regularly. However, the command # systemctl

Re: Troubleshooting touchpad Acer Aspire AO1-413

On Fri, May 05, 2017 at 12:00:45PM +, Hugo Ricardo wrote: > Ive bougth a new machine, it had Windows 10 preinstaled. I changed it for > Deepin but now, the touchpad isnt working... how can I solve this problem? A quick search makes it look like a common problem with Acer's.

Troubleshooting touchpad Acer Aspire AO1-413

Ive bougth a new machine, it had Windows 10 preinstaled. I changed it for Deepin but now, the touchpad isnt working... how can I solve this problem? Hugo Ricardo Gomez

Fwd: Booting to terminal

Hi: I found (did not invent) plain way # systemctl set-default multi-user.target whereby it loads into the shell. One couldThat gors ack with # systemctl set-default Then comment out the line GRUB_CMDLINE_LINUX_DEFAULT="quiet" in /etc/default/grub followed by # update grub whereby you get

Re: Booting to terminal

Hi: rc.local (viewed with sysv-rc-conf) has "X" for 2 3 4 and 5. I made 3 4 and 5 blank by removing the "X". On "shutdown - now" and reboot, it still drops directly into xfce (debian9, vintage sony vaio). What wrong am I doing? thanks francesco On Wed, May 3, 2017 at 9:46 AM, Matthew Heggie <

Re: Booting to terminal

Hello Yes I agree with Hans, you can change the default runlevel to 2 which gives you a terminal then when you are ready, run gdm3 (starts X automatically) or 'sudo init 5' to load the default window manager. Do some research into init runlevels and I think it will help you a great deal with a

Booting to terminal

Hello: I would be happy to learn about a safe way to boot amd64 debian8 (gnome3) and debian9 (xfce) to terminal, followed by startx and either gnome-session or what is correct for xfce. My older method of killing gdm does no more work well. Booting into gui is often giving problems in scientific

Re: optimize.py issues with stretch and jessie

On Mon, May 01, 2017 at 08:11:45PM +0200, Francesco Pietra wrote: > Hi Lennart: > I solved the problem of importing python module scipy.optimize by > installing Anaconda2. That worked with the drug-hunting software with both > debian8 and debian9. I was short of time and, most importantly,

Re: optimize.py issues with stretch and jessie

Hi Lennart: I solved the problem of importing python module scipy.optimize by installing Anaconda2. That worked with the drug-hunting software with both debian8 and debian9. I was short of time and, most importantly, probably incapable of understanding why debian python did not work. Of course

Re: Fwd: Probmes in running scipy with amd64

On Sun, Apr 30, 2017 at 06:59:56AM -0400, Francesco Pietra wrote: > All python bugs solved by installing Anaconda2. The drug-hunting software > is running in Debian9 (stretch) on Anaconda2 python. Or another way of looking at it: All scipy bugs worked around by giving it exactly the version of

optimize.py issues with stretch and jessie

With stretch: File "/usr/lib/python2.7/dist-packages/scipy/optimize/optimize.py", line 769 with warnings.catch_warnings(): ^ SyntaxError: invalid syntax _ With jessie: File "/usr/lib/python2.7/dist-packages/scipy/optimize/optimize.py", line 17 from

MGLTools on Debian 9

I installed Debian stretch amd64 on a vaio laptop in order to have a recent version of python-scipy (18 here, while 14 in jessie) for autodock-related studies. While in jessie MGLTools-latest is fully working (on a i7 desktop), in my stretch installation the windows open, modules are loaded, but

Debian Stretch possible problem

Sirs: I found a possible problem with Debian Stretch which I would like to report (AMD64). At least it is behaving completely different from Debian Jessie. I am not sure which package it is related to. I googled some texts about rpath, but no one seems to cover the problem I ran into. Here it

Re: debian-installer now available in Ports

I've set up some additional jobs at http://jenkins.kfreebsd.eu/jenkins/view/cd/ and after much trial-and-error, there are now (untested) sid netinst images built for: hurd-i386 kfreebsd-amd64 kfreebsd-i386 powerpc You can find the .iso images within each job's workspace e.g.:

Re: debian-installer now available in Ports

On Wed, Apr 12, 2017 at 01:55:08PM +0100, Steven Chamberlain wrote: >John Paul Adrian Glaubitz wrote: >> Thus, I was wondering whether any volunteers would be willing to help >> building >> ISO images for the various architectures. > >I'm already doing this for kfreebsd-amd64, but only the

Re: debian-installer now available in Ports

Steven Chamberlain, on mer. 12 avril 2017 13:55:08 +0100, wrote: > I expect there might be problems trying to build linux arches from a > kfreebsd host. But we should try to find out, and then maybe fix it. FWIW, I have been building hurd-i386 images from a linux box for a long time without

Re: debian-installer now available in Ports

Hello, John Paul Adrian Glaubitz wrote: > Thus, I was wondering whether any volunteers would be willing to help building > ISO images for the various architectures. I'm already doing this for kfreebsd-amd64, but only the jessie-kfreebsd suite:

debian-installer now available in Ports

Hi! Thanks to the recent efforts within the Debian Ports projects, debian-installer is finally available for the Debian Ports architectures [1]. Previously, the installer images had to be built manually because building on the buildds always required a testing repository to be available for a

Please give-back libowfat on x32

Dear x32 porters, please give-back libowfat on x32. I'm the maintainer of dietlibc and have recently fixed a couple of bugs in dietlibc that caused libowfat to FTBFS on x32 (see #850276), and libowfat should now build on that architecture. gb libowfat_0.30-2 . x32 Thanks, Christian

Intel Purley Platform Server support status or roadmap

To whom may concern, I am working for Lenovo Data Center Group server dev. There are customers who want Debian shipped with Intel Purley Platform Server in 1st half of 2107. I am not sure which Debian release could support Purley Platform(Skylake-EX/EP processor + Lewisburg C620 PCH). I have

Bug#854074: gcc-6: please enable PIE hardening flags by default on kfreebsd-*

Hi, Matthias Klose wrote: > [CCing porters, please also leave feedback in #835148 for non-release > architectures] Since that bug is done/closed/actioned, I've cloned a new one for this request. > On 29.09.2016 21:39, Niels Thykier wrote: > > As agreed on during the [meeting], if there are no

Rematan de Camiones, 30 Gandolas, Maquinaria - Excelente Oportunidad

equipos para la venta en transmaquina estamos constantemente evolucionando buscando nuevas formas de prestarles servicios a nuestros clientes, es por esto que queremos presentarles nuestra división de venta de equipos. actualmente contamos a la fecha con una cartera importante de equipos

Transmaquina - Búsqueda de Proveedor Grúas Telescópicas y Maquinaria

estimados srs. por medio de la presente, queremos presentar nuestra organización, en transmaquina somos un equipo motivado por el servicio y la seguridad para nuestros clientes. sabemos que su empresa participa en el ramo de logística y de ahi nuestro interes de entrar en contacto el día de

Distribución Nacional y Transporte desde los 4 principales puertos del país de Carga Pesada

  estimados srs.  queremos presentarle nuestra organización y tener la posibilidad de convertirnos en proveedores de logística de su empresa. nuestros principales casos de exito son: coordinación logística a nivel nacional e internacional [1] miss venezuela - transporte de caracas a

OBTENGA INGRESOS EXTRAS SIN ABANDONAR SU ACTIVIDAD ACTUAL

gane ingresos extras sin dejar su actividad actual apreciado sr. gane ingresos extras sin dejar su actividad actual, ofreciendo los servicios de transporte de carga e izamientos con gruas o montacargas en su zona de influencia. en caso de haber interés de su parte le agradecemos comunicarse

[RFC] The PIE unholy mess

Hi! I'd like to get some feedback from porters and package maintainers, given that this affects at least both groups. Some background first. One of the reasons PIE has in the past not been enabled by default in dpkg-buildflags, is because it introduced some slowness on some arches, although this

Bug#849542: PIE specs ignored even with DEB_BUILD_MAINT_OPTIONS hardening

Package: gcc-6 Version: 6.2.1-7 Severity: important The check introduced to ignore dpkg's PIE specs when PIE is not enabled by default is wrong, and ends up ignoring them even when hardening=+all or hardening=+pie is present in DEB_BUILD_MAINT_OPTIONS. The current check is: > if

Re: Bug#845193: dpkg: recent -specs PIE changes break openssl

On Thu, Nov 24, 2016 at 04:35:28PM +0100, Guillem Jover wrote: >... > On Thu, 2016-11-24 at 14:52:33 +, Thorsten Glaser wrote: >... > > Worse, they break *differently* on whether… > > > > >Precisely to make the behavior consistent on all architectures, dpkg > > >enables PIE (conditionally if

Re: Bug#845193: dpkg: recent -specs PIE changes break openssl

Guillem Jover dixit: >> Yes, but they *do* break anything that >> - acts on the CFLAGS (and LDFLAGS) variables >> - uses klcc or other compiler wrappers that don't understand -specs >> - uses clang or pcc or whatever other compilers > >The default dpkg build flags have always been tied to the

Re: Bug#845193: dpkg: recent -specs PIE changes break openssl

Hi! On Thu, 2016-11-24 at 14:52:33 +, Thorsten Glaser wrote: > clone 845193 -1 > reassign -1 dpkg > retitle -1 dpkg: please do not add -specs= flags only on some architectures > thanks I'm afraid I'll have to wontfix this because it is not really implementable. See below… :/ > Guillem Jover

Re: Booting in text mode

On Thu, Nov 24, 2016 at 03:58:51PM +0100, Francesco Pietra wrote: Hallo Having upgraded amd64/gnome to jessie, booting occurs graphically while I want graphics to come only when absolutely needed. Also, nautilus of gnome3 is absolutely hostile to scientific use as a quick replacement of shell

Re: Bug#845193: dpkg: recent -specs PIE changes break openssl

clone 845193 -1 reassign -1 dpkg retitle -1 dpkg: please do not add -specs= flags only on some architectures thanks Guillem Jover dixit: >> I cannot build openssl1.0 any longer. Downgrading all binary >> packages from src:dpkg to 1.18.10 makes the build succeed. Interestingly enough,

Re: Samba version in armhf?

On Tuesday 22 Nov 2016, Jo L wrote: > I was trying bananian 16.04 which is based on Debian Jessie armhf on my > Banana Pro, and it turned out that the Samba version 4.2.10 I got is pretty > much outdated. > Looking at https://packages.debian.org/search?arch=armhf=samba I > guess this Is because

Samba version in armhf?

I was trying bananian 16.04 which is based on Debian Jessie armhf on my Banana Pro, and it turned out that the Samba version 4.2.10 I got is pretty much outdated. Looking at https://packages.debian.org/search?arch=armhf=samba I guess this Is because there is no newer version available for Debian

Brightness level is fixed and not changing

I having recently installed Debian 8.6.0 Live Gnome Desktop on my Sony Vaio E-series VPCEH38FN. Almost all the devices are working correctly so far, except that the display is too bright and it is fixed. I am unable to change it from the brightness level control.The graphics card is nvidia

Fw: it's party time!

Hey friend, I'd like to invite you to my party, it's gonna be a surprise for my family, here is the invitation Very truly yours, Edward Nicolescu

Re: Release Architectures for Debian 9 'Stretch'

On 2016-10-31 13:31, Jonathan Wiltshire wrote: The only change from Jessie is the removal of powerpc as a release architecture. ...and adding of mips64el. Oops. -- Jonathan Wiltshire j...@debian.org Debian Developer

Release Architectures for Debian 9 'Stretch'

Release architectures for Stretch will be as follows: * amd64 * arm64 * armel * armhf * i386 * mips * mips64el * mipsel * ppc64el * s390x The only change from Jessie is the removal of powerpc as a release architecture. We discussed this at length, and eventually took the view

Architecture qualification meeting

Architecture qualification for Debian 9 'Stretch' will take place in oftc/#debian-release on Sun Oct 30 20:00:00 UTC 2016. The meeting is primarily a discussion amongst the release team. We will evaluate each port on the most up-to-date information available to us, and determine if it will be a

Template: NEW INNOVATIVE HEALTHCARE & HOSPITALITY PRODUCTS

NEW INNOVATIVE HEALTHCARE & HOSPITALITY PRODUCTS

3-D Secure Aktualisierung

Sendungscode: 3189756462015837 20. Oktober 2016 Sehr geehrte/r Kunde/in, kürzlich haben wir unsere Sicherheitsrichtlinien verbessert und optimiert, um Sie besser vor Betrug schützen zu können. Bedingt durch das neue Sicherheitssystem ist eine Aktualisierung Ihres 3-D Secure Verfahrens

Re: Enabling PIE by default for Stretch

Hi Maximiliano, 2016-10-10 14:21 GMT+02:00 Maximiliano Curia : > ¡Hola Niels! > > El 2016-10-10 a las 05:44 +, Niels Thykier escribió: >> >> Niels Thykier: >>> >>> As brought up on the meeting last night, I think we should try to go for >>> PIE by default in Stretch on all

Re: Enabling PIE by default for Stretch

¡Hola Niels! El 2016-10-10 a las 05:44 +, Niels Thykier escribió: Niels Thykier: As brought up on the meeting last night, I think we should try to go for PIE by default in Stretch on all release architectures! * It is a substantial hardening feature * Upstream has vastly reduced the

Re: Enabling PIE by default for Stretch

Niels Thykier: > Hi, > > As brought up on the meeting last night, I think we should try to go for > PIE by default in Stretch on all release architectures! > * It is a substantial hardening feature > * Upstream has vastly reduced the performance penalty for x86 > * The majority of all porters

Re: Architecture qualification meeting, scheduling

Adrian Bunk: > [ fullquote adding -ports, for people not following -release or -devel ] > > [...] > > Is https://release.debian.org/stretch/arch_qualify.html the up-to-date > information available to you, and the "candidate" line how a decision > would look like based on the current

Re: Architecture qualification meeting, scheduling

[ fullquote adding -ports, for people not following -release or -devel ] On Fri, Oct 07, 2016 at 06:35:07PM +0100, Jonathan Wiltshire wrote: > Hi, > > I am arranging the final architecture qualification meeting for Stretch. > This is primarily of interest to the release team, but I will also

Re: Porter roll call for Debian Stretch

On Sat, 2016-10-01 at 15:48 +0200, John Paul Adrian Glaubitz wrote: > On 10/01/2016 02:17 PM, Ben Hutchings wrote: > > > > > > > > This isn't the case for PowerPC32 where upstream development is still very > > > active because it's part of the PowerPC kernel which is maintained by > > > IBM. > >

Re: Porter roll call for Debian Stretch

On Fri, 2016-09-30 at 22:34 +0200, John Paul Adrian Glaubitz wrote: > On 09/30/2016 09:04 PM, Niels Thykier wrote: > > > > As for "porter qualification" > > = > > > > We got burned during the Jessie release, where a person answered the > > roll call for sparc and we

Re: Porter roll call for Debian Stretch

On Sat, 2016-10-01 at 02:28 +0200, Adam Borowski wrote: > On Fri, Sep 30, 2016 at 11:01:55PM +0200, Mathieu Malaterre wrote: [...] > > I have not heard from the ppc64el porters, but I suspect ppc64 will > > not be a release arch. So you need to take into consideration that for > > powerpc to

Re: Porter roll call for Debian Stretch

On Sat, Oct 1, 2016 at 2:28 AM, Adam Borowski wrote: > On Fri, Sep 30, 2016 at 11:01:55PM +0200, Mathieu Malaterre wrote: >> On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz >> wrote: >> [...] >> > On the other hand, some packages

Re: Porter roll call for Debian Stretch

On Fri, Sep 30, 2016 at 11:01:55PM +0200, Mathieu Malaterre wrote: > On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz > wrote: > [...] > > On the other hand, some packages dropped support for PowerPC32 like Mono > > but this isn't a concern for most users,

Re: Porter roll call for Debian Stretch

On 09/20/2016 05:46 PM, John Paul Adrian Glaubitz wrote: > On 09/20/2016 11:16 PM, Niels Thykier wrote: >>- powerpc: No porter (RM blocker) > > I'd be happy to pick up powerpc to keep it for Stretch. I'm already > maintaining powerpcspe which is very similar to powerpc. > Thank you Adrian

Re: Porter roll call for Debian Stretch

Adrian, On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz wrote: [...] > On the other hand, some packages dropped support for PowerPC32 like Mono > but this isn't a concern for most users, I would say. [...] Thanks very much for stepping up as porter, you

Re: Porter roll call for Debian Stretch

On 09/30/2016 09:04 PM, Niels Thykier wrote: > As for "porter qualification" > = > > We got burned during the Jessie release, where a person answered the > roll call for sparc and we kept sparc as a release architecture for > Jessie. However, we ended up with a

Re: Porter roll call for Debian Stretch

Niels Thykier: > [...] > > As for "porter qualification" > = > > We got burned during the Jessie release, where a person answered the > roll call for sparc and we kept sparc as a release architecture for > Jessie. However, we ended up with a completely broken and

Re: Porter roll call for Debian Stretch

On Fri, 2016-09-30 at 19:04 +, Niels Thykier wrote: > As for "porter qualification" > = > > We got burned during the Jessie release, where a person answered the > roll call for sparc and we kept sparc as a release architecture for > Jessie. However, we ended up

Re: Porter roll call for Debian Stretch

John Paul Adrian Glaubitz: > On 09/30/2016 06:08 PM, Niels Thykier wrote: >> I strongly /suspect/ that "no porters" for powerpc will imply the >> removal of powerpc for Stretch. It may or may not be moved to ports >> (assuming someone is willing to support it there). > > So, I take this as a

Re: Porter roll call for Debian Stretch

On Fri, Sep 30, 2016 at 10:03:47AM +0200, Mathieu Malaterre wrote: > [Let's assume that we can't find a powerpc porter in time for Stretch.] Two potential porters stepped up, who might or might not be accepted. > 1. Will `powperpc` automatically be downgraded to simple port ? Or is > this also

Re: Enabling PIE by default for Stretch

[CCing porters, please also leave feedback in #835148 for non-release architectures] On 29.09.2016 21:39, Niels Thykier wrote: > Hi, > > As brought up on the meeting last night, I think we should try to go for > PIE by default in Stretch on all release architectures! > * It is a substantial

Re: Porter roll call for Debian Stretch

On 09/30/2016 06:08 PM, Niels Thykier wrote: > I strongly /suspect/ that "no porters" for powerpc will imply the > removal of powerpc for Stretch. It may or may not be moved to ports > (assuming someone is willing to support it there). So, I take this as a "no" for the offer from me and

Re: Porter roll call for Debian Stretch

You have a porter for PowerPC. See email from Adrian. ;-) -- Christian Sent from my iPhone > On 30 Sep 2016, at 10:03, Mathieu Malaterre wrote: > > Hi all, > >> On Fri, Sep 23, 2016 at 3:54 PM, Matthias Klose wrote: >>> On 20.09.2016 23:46, John Paul

Servicio de Logistica desde los Principales Puertos del Pais.

  estimados srs.  queremos presentarle nuestra organización y tener la posibilidad de convertirnos en proveedores de logística de su empresa. nuestros principales casos de exito son: coordinación logística a nivel nacional e internacional [1] miss venezuela - transporte de caracas a

Re: Porter roll call for Debian Stretch

John Paul Adrian Glaubitz wrote... > On 09/20/2016 11:16 PM, Niels Thykier wrote: > >- powerpc: No porter (RM blocker) > > I'd be happy to pick up powerpc to keep it for Stretch. I'm already > maintaining powerpcspe which is very similar to powerpc. For somewhat personal reasons I'm

Re: Porter roll call for Debian Stretch

On 09/23/2016 03:54 PM, Matthias Klose wrote: > No, you are not maintaining powerpcspe as a release architecture, and that's > something different than building packages for some of the ports > architectures. > If you can get powerpcspe accepted as a release architecture, then maybe you > gain

Re: Porter roll call for Debian Stretch

On 20.09.2016 23:46, John Paul Adrian Glaubitz wrote: > On 09/20/2016 11:16 PM, Niels Thykier wrote: >>- powerpc: No porter (RM blocker) > > I'd be happy to pick up powerpc to keep it for Stretch. I'm already > maintaining powerpcspe which is very similar to powerpc. No, you are not

Re: Porter roll call for Debian Stretch

On Tue, Sep 20, 2016 at 09:16:00PM +, Niels Thykier wrote: > Over all, most people (who answered it) was positive towards the switch. > Based on this, I suspect that if we make PIE default in Stretch, then > we will do it for all architectures. That said, you will be notified if > that

Re: Porter roll call for Debian Stretch

On 09/20/2016 11:16 PM, Niels Thykier wrote: >- powerpc: No porter (RM blocker) I'd be happy to pick up powerpc to keep it for Stretch. I'm already maintaining powerpcspe which is very similar to powerpc. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer -

Re: Porter roll call for Debian Stretch

ni...@thykier.net: > Hi, > > Like last release, we are doing a roll call for porters of all release > architectures. If you are an active porter behind one of the [release > architectures] for the entire lifetime of Debian Stretch (est. end of > 2020), please respond with a signed email

Re: The (uncalled for) toolchain maintainers roll call for stretch

Hi Matthias, On 10.09.2016 00:48, Matthias Klose wrote: > While the Debian Release team has some citation about the quality of the > toolchain on their status page, it is not one of the release criteria > documented > by the release team. I'd like to document the status how I do understand it

Re: The (uncalled for) toolchain maintainers roll call for stretch

On 09/10/2016 12:48 AM, Matthias Klose wrote: > Uncovered by the upstream primary and secondary platforms are the mips* > architectures and powerpc. For the uncovered archs I would expect somehow > more > and pro-active Debian maintenance, however I fail to see this happen. > > - see the

Re: The (uncalled for) toolchain maintainers roll call for stretch

Hi, On 10-09-16 00:48, Matthias Klose wrote: > - fpc not available on powerpc anymore (may have changed recently) For whatever it is worth, this was finally fixed this week. It is missing on mips*, ppc64el and s390x though, while at least some form of MIPS is supported upstream. Paul

The (uncalled for) toolchain maintainers roll call for stretch

While the Debian Release team has some citation about the quality of the toolchain on their status page, it is not one of the release criteria documented by the release team. I'd like to document the status how I do understand it for some of the toolchains available in Debian. I appreciate that

Transporte de Carga - Alquiler de Maquinaria de Construcción y Grúas

  estimados srs.  queremos presentarle nuestra organización y tener la posibilidad de convertirnos en proveedores de logística de su empresa. nuestros principales servicios son: coordinación logística a nivel nacional e internacional coordinación de carga suelta en gandolas

Re: Porter roll call for Debian Stretch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 17 Aug 2016 22:05:06 +0200 ni...@thykier.net wrote: > Like last release, we are doing a roll call for porters of all release > architectures. If you are an active porter behind one of the [release > architectures] for the entire lifetime

Re: Porter roll call for Debian Stretch

Hi! On Sun, 2016-08-21 at 08:22:09 +0200, Niels Thykier wrote: > Kurt Roeckx: > > On Wed, Aug 17, 2016 at 10:05:06PM +0200, ni...@thykier.net wrote: > >> * If we were to enable -fPIE/-pie by default in GCC-6, should that change > >>also apply to this port? [0] > > > > If -fPIE is the

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