Re: Porter roll call for Debian Bookworm

Hi A friendly reminder about the porter roll call for bookworm. On Sat, 2 Oct 2021 at 11:57, Graham Inggs wrote: > We are doing a roll call for porters of all prospective release > architectures. If you are an active porter behind one of these > architectures [1] and intend to continue for the

Re: Porter roll call for Debian Bookworm

Hi, I am an active porter for the following architecture and I intend to continue for the development cycle of Debian Bookworm (est. release mid-2023): For ppc64el, I - test most packages on this architecture - run a Debian testing or unstable system that I use regularly - fix ppc64el-related bug

Re: Itinerary for your date

I am 99 years old and broke.  Can she help me to pay rent? Regards  Leslie Leslie Satenstein Montréal Québec, Canada On Monday, May 31, 2021, 3:36:15 a.m. EDT, gliddensidhu4...@hotmail.com wrote: Jasmine is interested in you. Respond to her here. About Jasmine: Age - 25 years ol

Re: Porter roll call for Debian Bullseye

On Sun, Dec 06, 2020 at 01:03:17PM +0100, Matthias Klose wrote: > On 12/1/20 5:02 AM, YunQiang Su wrote: > > I am sorry for the later response. > >Hi, > > > > I am an active porter for the following architectures and I intend > > to continue this for the lifetime of the Bullseye release (

Re: Porter roll call for Debian Bullseye

Hi, sorry for the late reply and thanks a lot Graham for pinging me directly. I didn't monitor -devel closely lately, but I am an active porter for the following architecture and I intend to continue this for the lifetime of the Bullseye release (est. end of 2024): For ppc64el, I - test most pack

Re: Porter roll call for Debian Bullseye

On 2020-11-02 22:23 +0200, Graham Inggs wrote: > Hi > > We are doing a roll call for porters of all release architectures. If > you are an active porter behind one of the release architectures [1] > for the entire lifetime of Debian Bullseye (est. end of 2024), please > respond with a signed emai

Re: Porter roll call for Debian Bullseye

On Sun, Dec 06, 2020 at 01:03:17PM +0100, Matthias Klose wrote: > On 12/1/20 5:02 AM, YunQiang Su wrote: > > I am sorry for the later response. > >Hi, > > > > I am an active porter for the following architectures and I intend > > to continue this for the lifetime of the Bullseye release (

Re: Porter roll call for Debian Bullseye

On 12/1/20 5:02 AM, YunQiang Su wrote: > I am sorry for the later response. >Hi, > > I am an active porter for the following architectures and I intend > to continue this for the lifetime of the Bullseye release (est. end > of 2024): > > For mipsel and mips64el, I > - test most pac

Re: Porter roll call for Debian Bullseye

On 2020-11-20, Graham Inggs wrote: > A friendly reminder about the porter roll call for bullseye. > > On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote: >> We are doing a roll call for porters of all release architectures. If >> you are an active porter behind one of the release architectures [1] >

Re: Porter roll call for Debian Bullseye

Hi A friendly reminder about the porter roll call for bullseye. On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote: > We are doing a roll call for porters of all release architectures. If > you are an active porter behind one of the release architectures [1] > for the entire lifetime of Debian Bul

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

* Florian Weimer: >> * Concern for mips, mips64el, mipsel and ppc64el: no upstream support >>in GCC >>(Raised by the GCC maintainer; carried over from stretch) > > I'm surprised to read this. ppc64el features prominently in the > toolchain work I do (though I personally do not work on th

Re: nforce4, Harddisk SATA, DVD-Burner ATAPI: How can I keep ide-scsifrom loading?

Sent from my iPhone

Re: nforce4, Harddisk SATA, DVD-Burner ATAPI: How can I keep ide-scsifrom loading?

Sent from my iPhone

Re: Sarge Release Notes - Architecture specific news?

Sent from my iPhone

Re: Hello - About MySql installation on Debian Server 10 (Buster)

You need download & then install the binary file from official repo of MySQL: https://dev.mysql.com/downloads/repo/apt/ Unlike other database systems, native MySQL is not present in the Debian 10 distribution, since its license is not GPL. Fortunately, MySQL offers official repositories from which

Re: package working

On Thursday, 2 January 2020 16:35:19 GMT Shah Rukh wrote: > hi ! sir my name is shahrukh . i am from india > i am installing arm packages buy > this package > libncurses5-dbg > and > libncursesw5-dbg > package is not working and not updated . > please libncursesw5-dbg and libncursesw5-dbg package p

Re: test

On Fri, Dec 13, 2019 at 7:16 PM qorg11 wrote: > > this is a test please ignore Try alt.test, https://groups.google.com/forum/#!forum/alt.test

Re: systemd on amd64

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, On 22/8/19 6:21 pm, Steffen Grunewald wrote: > On Thu, 2019-08-22 at 13:49:22 +1000, Andrew McGlashan wrote: >> >> Any help would be appreciated. > > Check "Devuan >> Beowulf", >> currently under development. Or even "Devuan ASCII" -- s

Re: systemd on amd64

On Thu, 2019-08-22 at 13:49:22 +1000, Andrew McGlashan wrote: > > >> >> Any help would be appreciated. > > Check "Devuan Beowulf", > currently under development. > Or even "Devuan ASCII" -- stable. AFAIR Jack had asked for Buster... ASCII is Stretch. - S

Re: systemd on amd64

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, On 22/8/19 1:46 am, Steffen Grunewald wrote: > On Wed, 2019-08-21 at 12:08:07 -0300, Jack Warkentin wrote: >> Hi everybody > >> >> I would like to install Buster on my amd64 machine *without* systemd. Is >> this possible? If so, how? I have r

Re: systemd on amd64

On Wed, 2019-08-21 at 12:08:07 -0300, Jack Warkentin wrote: > Hi everybody > > I would like to install Buster on my amd64 machine *without* systemd. Is > this possible? If so, how? I have read the entire installation manual and > could not find anything about how to do this. Also. I could find not

Re: systemd on amd64

On 8/21/19 5:08 PM, Jack Warkentin wrote: Hi everybody I would like to install Buster on my amd64 machine *without* systemd. Is this possible? If so, how? I have read the entire installation manual and could not find anything about how to do this. Also. I could find nothing about it in the

Re: Innstaling 64bit Debian new comptuer wiith M2. with SDD

Yes. On 09/08/2019 12:25, E Sutton wrote: > Is it possble to innstaling 64bit  Debian new computer  wiith M2. with > SDD > signature.asc Description: OpenPGP digital signature

Re: Same procedure as every year: GCC defaults change (GCC 9)

On Jul 28 2019, Aurelien Jarno wrote: > The two MIPS libffi patches have been accepted upstream (i.e. in the > libffi git repository) 1.5 years ago for one and 4 years ago for the > other. I know there hasn't been any recent libffi release, so what can > be done to sync the gcc repository? Would

Re: Same procedure as every year: GCC defaults change (GCC 9)

On 2019-07-27 17:28, Matthias Klose wrote: > GCC 9 was released earlier this year, it is now available in Debian > testing/unstable. I am planning to do the defaults change in mid August, > around > the time of the expected first GCC 9 point release (9.2.0). > > There are only soname changes for

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

urelien Jarno >> Sent: Saturday, May 25, 2019 4:56 PM >> To: debian-h...@lists.debian.org; debian-...@lists.debian.org; debian- >> de...@lists.debian.org; debian-po...@lists.debian.org; ftpmaster@ports- >> master.debian.org >> Subject: Re: Hurd-i386 and kfreebsd-{i386,amd6

RE: Hurd-i386 and kfreebsd-{i386,amd64} removal

From: Aurelien Jarno > Sent: Saturday, May 25, 2019 4:56 PM > To: debian-h...@lists.debian.org; debian-...@lists.debian.org; debian- > de...@lists.debian.org; debian-po...@lists.debian.org; ftpmaster@ports- > master.debian.org > Subject: Re: Hurd-i386 and kfreebsd-{i386,amd64} remov

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

On 15413 March 1977, Aurelien Jarno wrote: Thats ok, end of May is a nice point to take. Thanks for the work and the timeframe for the rest! kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports. As hurd-i386 has been moved earlier, it means that all the 3 architectures have now

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

On 2019-05-25 13:00, Manuel A. Fernandez Montecelo wrote: > Hi, > > Em sáb, 25 de mai de 2019 às 10:57, Aurelien Jarno > escreveu: > > > > kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports. As > > hurd-i386 has been moved earlier, it means that all the 3 architectures > > have

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

Hi, Em sáb, 25 de mai de 2019 às 10:57, Aurelien Jarno escreveu: > > kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports. As > hurd-i386 has been moved earlier, it means that all the 3 architectures > have now been moved. Nice :-) Not sure who's the admin (I couldn't find the a

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

Hi, On 2019-04-24 12:34, Joerg Jaspert wrote: > On 15381 March 1977, Aurelien Jarno wrote: > > > > > It would be nice to have a bit more than 2 weeks to do all of that. > > > Ok. How much? Is 6 or 8 weeks better? I don't think, given how long this > > > is on the table already, it doesn't make mu

Re: can we got xorg in debian 10 ?

On Thu, Apr 25, 2019 at 08:39:34AM +0200, Omnis Moriar wrote: > Can we got xorg in minumal version of debian with X-window system ??? I > fight for xorg couse Wayland is our danger to linux world I don't get it. https://packages.debian.org/search?keywords=xorg-server seems so show xorg is in jess

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

On 15381 March 1977, Aurelien Jarno wrote: > It would be nice to have a bit more than 2 weeks to do all of that. Ok. How much? Is 6 or 8 weeks better? I don't think, given how long this is on the table already, it doesn't make much difference if its 2 or 8. Just something thats clear defined and

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

On 2019-04-13 17:01, Joerg Jaspert wrote: > On 15371 March 1977, Aurelien Jarno wrote: > > > > How is the move to debian-ports supposed to happen? I won't have the > > > time to do anything about it within the 2 weeks. > > > The process to inject all packages to debian-ports is to get all the > >

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

On 13.04.19 17:01, Joerg Jaspert wrote: > On 15371 March 1977, Aurelien Jarno wrote: > >>> How is the move to debian-ports supposed to happen? I won't have the >>> time to do anything about it within the 2 weeks. > >> The process to inject all packages to debian-ports is to get all the >> deb, ud

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

On 15371 March 1977, Aurelien Jarno wrote: How is the move to debian-ports supposed to happen? I won't have the time to do anything about it within the 2 weeks. The process to inject all packages to debian-ports is to get all the deb, udeb and buildinfo files from the archives (main and debug

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

On 4/13/2019 12:49 PM, Aurelien Jarno wrote: > The process to inject all packages to debian-ports is to get all the > deb, udeb and buildinfo files from the archives (main and debug) and > associate them with the .changes files that are hosted on coccia. We'll > also need to fetch all the associate

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

On 2019-04-12 23:01, Samuel Thibault wrote: > Hello, > > Joerg Jaspert, le ven. 12 avril 2019 22:48:42 +0200, a ecrit: > > back in August 2018 we discussed architecture inclusion into > > unstable/experimental. > > > > Today we had our regular FTPMaster meeting and discussed hurd and both > > kfr

Re: gotop

On Mon, Apr 01, 2019 at 01:46:00PM +0200, Elimar Riesebieter wrote: > > Hi all, > > I tried to build gotop [0;1;2] on ppc. To build the binary golang-go > (>= 1.5) is needed but not available on ports. Hence I tried to > build golang-go from sources. On ppc it doesn't build the > binary golang-go

Re: about Firefox for buster

On Fri, Feb 08, 2019 at 07:39:31AM +0100, Francesco Pietra wrote: > Hello > Since a few months Firefox can't be installed on amd64 buster. What is > wrong about? Have you tried walking on the sea? please post logs

Re: Salvex Global Solutions for Surplus Heavy Equipment Sales

The seller has the right to reject any and all bids, > can add a reserve at anytime and may re-list the item on commercial > classified if they are not satisfied with the bid > results. Salvex is not the seller, but operates to assist the seller in > adv

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

This thread went OT talking about ports, but oh well… On Wed, Dec 12, 2018 at 04:03:25AM +0100, Adam Borowski wrote: > On Tue, Dec 11, 2018 at 09:46:21PM +0100, Gregor Riepl wrote: > > The build and package delivery infrastructure should offer the same features > > for both first and second class

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

[Oy vey, crosspost list from hell -- not sure how to trim...] On Tue, Dec 11, 2018 at 09:46:21PM +0100, Gregor Riepl wrote: > I do think this just reinforces the point that second-class architectures > should have better, more robust support from the Debian project. > For example, arch-specific p

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

Hi Adrian I do think this just reinforces the point that second-class architectures should have better, more robust support from the Debian project. For example, arch-specific packages most decidedly have a place in Debian (although they should not be the norm). There will always be such packages

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

Hello! On 12/9/18 3:18 PM, Matthias Klose wrote: > To me it looks sometimes that Debian is used for testing by upstream, and for > that the mips architectures don't need to be release architectures. A note on this: If you decide to move MIPS to Debian Ports, you will make the port unusable to mos

Re: chrome asks for password

El 9/12/18 a las 15:13, Francesco Pietra escribió: Hi all Since firefox did no more work with my installations of debian amd64, I installed chromium. Which asks for password to unlock keyring. Could Debian Just leave it blank -- Happy hacking Lectura obligatoria: https://qorg.xyz/preguntas-

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On 07.07.18 17:24, YunQiang Su wrote: > Niels Thykier 于2018年6月28日周四 上午4:06写道： >> List of concerns for architectures >> == >> >> The following is a summary from the current architecture qualification >> table. >> >> * Concern for ppc64el and s390x: we are dependent

Re: severe bug dpkg following upgrade to buster

Little bit OT: I am not sure, if I understood that correct, but as the manual says, "su" is preserving the environment and "su -" is creating a new one. However, for becoming root, I am using "su -", but when I want to edit files with root privileges with a graphical editor (i.e. kwrite), I alw

Re: severe bug dpkg following upgrade to buster

On Fri, Nov 30, 2018 at 07:59:06PM +, ael wrote: > zless /usr/share/doc/util-linux/NEWS.Debian.gz is where this was > announced. Wow, I never knew the su command used to have such misbehaviours on Debian. I guess being used to doing 'su -' from years of using different unix systems I never no

Re: severe bug dpkg following upgrade to buster

On Fri, Nov 30, 2018 at 11:12:26AM -0500, Lennart Sorensen wrote: > On Sat, Nov 24, 2018 at 08:43:29PM +0100, Francesco Pietra wrote: > > Hi > > Following amd64 upgrade from stretch to buster on both a vaio laptop and an > > asus desktop,command disappeared, while a severe bug arose with > > dpkg

Re: severe bug dpkg following upgrade to buster

Thanks, I set the house in order with much less elegant commands francesco On Fri, Nov 30, 2018 at 5:12 PM Lennart Sorensen < lsore...@csclub.uwaterloo.ca> wrote: > On Sat, Nov 24, 2018 at 08:43:29PM +0100, Francesco Pietra wrote: > > Hi > > Following amd64 upgrade from stretch to buster on both

Re: severe bug dpkg following upgrade to buster

On Sat, Nov 24, 2018 at 08:43:29PM +0100, Francesco Pietra wrote: > Hi > Following amd64 upgrade from stretch to buster on both a vaio laptop and an > asus desktop,command disappeared, while a severe bug arose with > dpkg that breaks upgrade/install > > pkg: warning: 'ldconfig' not found in PATH

Re: x32: unstable: Lack of libelf1 package.

El 27/11/18 a las 0:13, Mike Mestnik escribió: iproute2 depends of libelf1 and that has no x32 build, making the base-files package uninstallable. try # apt install libelf1:i386, i tried running that, and apt says that i already have libelf1:i386 installed. Thanks. You welcome -- Happy hac

Re: proposta ordine

On 26/11/18 15:28, Vanessa De Rose wrote: Ciao, Ti piacerebbe aumentare SUBITO i tuoi followers sul tuo profilo instagram ? Se ancora non hai provato il nostro servizio di vendita followers è questo il momento buono ! Abbiamo pensato di estendere ad oggi gli sconti del blackfriday e puoi acq

Re: severe bug dpkg following upgrade to buster

are you trying to invent warm water? fp On Sun, Nov 25, 2018 at 12:16 AM qorg11 wrote: > > On 24/11/18 20:43, Francesco Pietra wrote: > > Hi > > Following amd64 upgrade from stretch to buster on both a vaio laptop and > an > > asus desktop,command disappeared, while a severe bug arose > with >

Re: severe bug dpkg following upgrade to buster

On 24/11/18 20:43, Francesco Pietra wrote: Hi Following amd64 upgrade from stretch to buster on both a vaio laptop and an asus desktop,command disappeared, while a severe bug arose with dpkg that breaks upgrade/install shutdown command can be only executed by root user, so try su root befor

Re: Error with LD_PRELOAD

Hi Antti, I was sinking into a glass of water. Thanks a lot, francesco On Thu, Nov 22, 2018 at 10:51 AM Antti Kultanen wrote: > Hi, > > On Sun, 18 Nov 2018, Francesco Pietra wrote: > > > Commands below: > > > > francesco@vaio64:~/servers/cineca/RCM_remote_visualization$ > LD_PRELOAD=/home/france

Re: Error with LD_PRELOAD

Hi, On Sun, 18 Nov 2018, Francesco Pietra wrote: Commands below: francesco@vaio64:~/servers/cineca/RCM_remote_visualization$ LD_PRELOAD=/home/francesco/servers/cineca/RCM_remote_visualization/libX11.so.6 /bin/ls libX11.so.6 RCM_linux_64bit francesco@vaio64:~/servers/cineca/RCM_remote_visual

Re: armel/armhf arch qualification for buster: call for DSA, Security, toolchain concernsj

Hi Roger! On 07/23/2018 10:42 AM, Roger Shimizu wrote: > I talked to a few people about keeping armel in buster, during 1st and > 2nd day in debcamp. > Seems the blocker is just the buildd server hardware, and memory size it has. According to my colleague Alex Graf at SUSE, you can definitely bui

Re: armel/armhf arch qualification for buster: call for DSA, Security, toolchain concernsj

Dear armel/armhf shakeholders, I talked to a few people about keeping armel in buster, during 1st and 2nd day in debcamp. Seems the blocker is just the buildd server hardware, and memory size it has. On Fri, Jun 29, 2018 at 7:04 PM, W. Martin Borgert wrote: > > Quoting Uwe Kleine-König : >> >> I

Re: Debian/MIPSeb: proposal to drop mipseb port?

Hi! You should ask in a more public forum rather than on Debian mailing lists if you want to know about potential users. Adrian > On Jul 7, 2018, at 8:31 AM, YunQiang Su wrote: > > Hi, folks, > due to lack of enough man power and build machines for 3 mips* port at > the same time, I think tha

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

Niels Thykier 于2018年6月28日周四 上午4:06写道： > > Hi, > > > As part of the interim architecture qualification for buster, we request > that DSA, the security team and the toolchain maintainers review and > update their list of known concerns for buster release architectures. > > Summary of the current con

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

* Riku Voipio: > On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote: >> * Niels Thykier: >> >> > armel/armhf: >> > >> > >> > * Undesirable to keep the hardware running beyond 2020. armhf VM >> >support uncertain. (DSA) >> >- Source: [DSA Sprint report] >> >> Fe

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On Fri, Jun 29, 2018 at 10:20:50AM +0100, Luke Kenneth Casson Leighton wrote: > in addition, arm64 is usually speculative OoO (Cavium ThunderX V1 > being a notable exception) which means it's vulnerable to spectre and > meltdown attacks, whereas 32-bit ARM is exclusively in-order. if you > want t

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On Fri, Jun 29, 2018 at 12:50 PM, Julien Cristau wrote: > Everyone, please avoid followups to debian-po...@lists.debian.org. > Unless something is relevant to *all* architectures (hint: discussion of > riscv or arm issues don't qualify), keep replies to the appropriate > port-specific mailing lis

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On 06/27/2018 10:03 PM, Niels Thykier wrote: > Hi, > > > As part of the interim architecture qualification for buster, we request > that DSA, the security team and the toolchain maintainers review and > update their list of known concerns for buster release architectures. > Everyone, please avoi

Re: Arch qualification for buster: call for DSA, Security, toolchain concernsj

On Fri, Jun 29, 2018 at 12:06 PM, John Paul Adrian Glaubitz wrote: > On 06/29/2018 10:41 AM, Luke Kenneth Casson Leighton wrote: >> On Fri, Jun 29, 2018 at 8:16 AM, Uwe Kleine-König >> wrote: >> In short, the hardware (development boards) we're currently using to build armel and armhf

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On Fri, Jun 29, 2018 at 12:23 PM, Adam D. Barratt wrote: >> i don't know: i'm an outsider who doesn't have the information in >> short-term memory, which is why i cc'd the debian-riscv team as they >> have current facts and knowledge foremost in their minds. which is >> why i included them. > >

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On Fri, 2018-06-29 at 11:44 +0100, Luke Kenneth Casson Leighton wrote: [...] > On Fri, Jun 29, 2018 at 10:35 AM, Adam D. Barratt > wrote: > > > >  what is the reason why that package is not moving forward? > > > > I assume you're referring to the dpkg upload that's in proposed- > > updates > > w

Re: Arch qualification for buster: call for DSA, Security, toolchain concernsj

On 06/29/2018 10:41 AM, Luke Kenneth Casson Leighton wrote: > On Fri, Jun 29, 2018 at 8:16 AM, Uwe Kleine-König > wrote: > >>> In short, the hardware (development boards) we're currently using to >>> build armel and armhf packages aren't up to our standards, and we >>> really, really want them t

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Fri, Jun 29, 2018 at 10:35 AM, Adam D. Barratt wrote: >> what is the reason why that package is not moving forward? > > I assume you're referring to the dpkg upload that's in proposed-updates > waiting for the point

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On Fri, 2018-06-29 at 10:20 +0100, Luke Kenneth Casson Leighton wrote: [...] >  debian-riscv has been repeatedly asking for a single zero-impact > line > to be included in *one* file in *one* dpkg-related package which > would > allow riscv to stop being a NMU architecture and become part of > debi

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On Wed, Jun 27, 2018 at 9:03 PM, Niels Thykier wrote: > armel/armhf: > > > * Undesirable to keep the hardware running beyond 2020. armhf VM >support uncertain. (DSA) >- Source: [DSA Sprint report] [other affected 32-bit architectures removed but still relevant] ... i'm

Re: Arch qualification for buster: call for DSA, Security, toolchain concernsj

On Fri, Jun 29, 2018 at 8:16 AM, Uwe Kleine-König wrote: > Hello, > > On Wed, Jun 27, 2018 at 08:03:00PM +, Niels Thykier wrote: >> armel/armhf: >> >> >> * Undesirable to keep the hardware running beyond 2020. armhf VM >>support uncertain. (DSA) >>- Source: [DSA Sprint

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote: > * Niels Thykier: > > > armel/armhf: > > > > > > * Undesirable to keep the hardware running beyond 2020. armhf VM > >support uncertain. (DSA) > >- Source: [DSA Sprint report] > > Fedora is facing an issue runn

Re: Arch qualification for buster: call for DSA, Security, toolchain concernsj

Hello, On Wed, Jun 27, 2018 at 08:03:00PM +, Niels Thykier wrote: > armel/armhf: > > > * Undesirable to keep the hardware running beyond 2020. armhf VM >support uncertain. (DSA) >- Source: [DSA Sprint report] > > [DSA Sprint report]: > https://lists.debian.org/debian-p

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

* Niels Thykier: > armel/armhf: > > > * Undesirable to keep the hardware running beyond 2020. armhf VM >support uncertain. (DSA) >- Source: [DSA Sprint report] Fedora is facing an issue running armhf under virtualization on arm64:

Re: Archiving the attic folders from d-i for ports

On Fri, Apr 27, 2018 at 05:37:25AM +0200, John Paul Adrian Glaubitz wrote: > Since there are still some repositories that we need for debian-ports > in the attic, I was wondering whether we should take care of the > attic stuff and move it over to salsa or github. Could you show a list? Just migr

Re: Bug#895193: transition: openmpi

Control: tags -1 confirmed On 11/04/18 11:12, Alastair McKinstry wrote: > > > On 11/04/2018 10:07, John Paul Adrian Glaubitz wrote: >> On 04/11/2018 10:53 AM, Alastair McKinstry wrote: >>> As of 3.0.1, openmpi now works on Big-Endian powerpc (which was to be a >>> problem; it had been dropped up

Re: Bug#895193: transition: openmpi

On 04/11/2018 10:53 AM, Alastair McKinstry wrote: As of 3.0.1, openmpi now works on Big-Endian powerpc (which was to be a problem; it had been dropped upstream because of an unknown bug, now fixed). Oh, really, they fixed that? I already had given up hopes and therefore ignored the thread on gi

Re: Bug#895193: transition: openmpi

On 11/04/2018 10:07, John Paul Adrian Glaubitz wrote: > On 04/11/2018 10:53 AM, Alastair McKinstry wrote: >> As of 3.0.1, openmpi now works on Big-Endian powerpc (which was to be a >> problem; it had been dropped upstream because of an unknown bug, now >> fixed). > > Oh, really, they fixed that?

Re: Bug#895193: transition: openmpi

As of 3.0.1, openmpi now works on Big-Endian powerpc (which was to be a problem; it had been dropped upstream because of an unknown bug, now fixed). The other non-release archs were failing due to missing dependencies: in particular java support (not used by any package in stable/testing) and pmix

Re: Bug#884472: qbs: FTBFS on x32: qbs-setup-qt (qmake?) bus error

On lunes, 18 de diciembre de 2017 11:29:19 -03 Aaron M. Ucko wrote: > Lisandro Damián Nicanor Pérez Meyer writes: > > El 15 dic. 2017 1:39 p.m., "Aaron M. Ucko" escribió: > [...] > > > + /<>/qbs-1.8.1+dfsg/bin/qbs-setup-qt /usr/bin/qmake > > > > qbs_autotests > > > > Bus error > > [...] >

Re: BTS usertag and X-Debbugs-CC for x32?

On Tue, Dec 19, 2017 at 04:51:29PM +0100, John Paul Adrian Glaubitz wrote: > On 12/19/2017 04:49 PM, Aaron M. Ucko wrote: > > Should we stick with that convention or switch to a different address? > > Either way, pabs has a script that can adjust any necessary metadata. > > Also, Adrian G. recommen

Re: BTS usertag and X-Debbugs-CC for x32?

On 12/19/2017 04:49 PM, Aaron M. Ucko wrote: > Should we stick with that convention or switch to a different address? > Either way, pabs has a script that can adjust any necessary metadata. > Also, Adrian G. recommends explicitly copying porters on these bug > reports, generally via the usertag's a

Re: Bug#884472: qbs: FTBFS on x32: qbs-setup-qt (qmake?) bus error

Lisandro Damián Nicanor Pérez Meyer writes: > El 15 dic. 2017 1:39 p.m., "Aaron M. Ucko" escribió: > [...] > + /<>/qbs-1.8.1+dfsg/bin/qbs-setup-qt /usr/bin/qmake > qbs_autotests > Bus error [...] > In my experience bus errors are arch-related. Of course this case might be > different, but I

Re: Can an iMac 24" with Core2 Duo run Debian AMD64?

I have successfully used debian-mac-8.7.1-amd64-netinst.iso to install a 64-bit OS on a Mac mini 2,1, which also has a 64-bit capable Core 2 Duo and a 32bit EFI. Perhaps a current debian-mac-x.x.x-amd64-netinst.iso from http://cdimage.debian.org/cdimage/release/current/amd64/iso-cd/ will also work

Re: Can an iMac 24" with Core2 Duo run Debian AMD64?

Yes it can but you have to install differently. That series of mac has some different 32bit/64 bit EFI type issues. It is best to use a regular non EFI installer to install Linux on it. I had a macbook with the same type of issue. The error you pasted is exactly the same one I encountered when

Re: libX11.so.6 in a chroot

Hi Thomas: Thanks a lot for LD_PRELOAD. It works fine for remote visualization at a cluster with GPUs francesco On Wed, Sep 27, 2017 at 10:02 AM, Thomas Lamprecht wrote: > Hi, > > On 09/26/2017 06:43 PM, Francesco Pietra wrote: > >> How to make available system-wide (to a program for remote vis

Re: libX11.so.6 in a chroot

Hi, On 09/26/2017 06:43 PM, Francesco Pietra wrote: How to make available system-wide (to a program for remote visualization on which I have no command, as it is provided as a binary file) a previous version of libX11.so.6 in a chroot? Specifically, I mean making available that library of deb

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 > wrote: > > John Paul Adrian Glaubitz wrote... > > > >>

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 to your efforts, but it feels a l

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 netboot

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 >

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 > /var/cache/apt/archives/mysql-community-server_5.7.19-1debian9_amd

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 diseño,

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 doesn't make sense to me. c

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 stre

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 combin

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

Back to your suspicion about the GTX680, I was really surprised that the Xserver could be raised from the other computer (vaio) on the LAN, only as a superuser. I had to change "allowed_users=console" (which is default on all my linux boxes) to "allowed_users=anybody" in /etc/X11/Xwrapper.config.

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