Fix M-A bugs in stable?
Hi, follow-up to #713932. For some strange reason I did put a non-M-A file into libsasl2-2 instead of sasl2-bin where it's used, should I fix it in stable as well? Ondrej -- Ondřej Surý ond...@sury.org
Bug#709813: Please give back 0ad on amd64
Dear wanna-build team, Please give back 0ad on amd64 on a buildd other than barber (i.e. retry until some other buildd takes it). Currently, it FTBFS on barber due to Illegal instruction when running its testsuite, and it's proving to be problematic to trace the root cause of the issue. I cannot reproduce the FTBFS locally with an up-to-date pbuilder, and the build log doesn't seem to give any clues as to why barber is bailing out on the testsuite (ansgar and others on #debian-devel noted the presence of -msse, but that shouldn't be an issue on amd64). A bug against 0ad has already been filed concerning this issue (#712956) and I've filed a ticket with upstream [1] (which I'll pursue more agressively when I have time), I don't think it's a regression, and this is blocking the enet transition (#709813), so can you please give back 0ad? Thanks! gb 0ad_0.0.13-2+b1 . amd64 [1] http://trac.wildfiregames.com/ticket/1994 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CACZd_tCBovmU3pbnt+ofePnOH=V=wmx0swlw3hcb0pp7ubr...@mail.gmail.com
Processed: tagging 705692
Processing commands for cont...@bugs.debian.org: tags 705692 + pending Bug #705692 [release.debian.org] transition: packagekit 0.8 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 705692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13720588898349.transcr...@bugs.debian.org
Re: DSA concerns for jessie architectures
On Sat, 22 Jun 2013, Kurt Roeckx wrote: They currently seem to be running linux-image-2.6.32-ferroceon 2.6.32-1+buildd41 Did someone try the mv78xx0 kernel on those yet? Lack of out of band access makes trying on these impossible for us. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130624083606.ga15...@anguilla.noreply.org
Re: DSA concerns for jessie architectures (mips*)
On Sat, 22 Jun 2013, Andreas Barth wrote: * mips: existing machines are either not reliable or too slow to keep up; we suspect that they may not be easily replaceable. Also, if we buy more mipsel machines we could convert the mipsel swarms to mips ones (and so replace broken machines, see below) - mostly depends on how urgent you think this is. If our existing eight-year old hardware is the only mips machines we can reasonably get then that doesn't bode well for mips. We don't think relying on the SWARMs (alone) is an option. * mipsel: the porter machine and some of the buildd machines have an implementation error for one opcode; missing kernel in the archive Different answers - select the one you like most: 1. We could buy a some loongson 2f machines (or newer), see e.g. http://www.tekmote.nl/epages/61504599.sf/nl_NL/?ObjectPath=/Shops/61504599/Products/CFL-006 plus some memory. These machines have kernels in the archive, and not the hardware bug with choking on too many nop-instructions in a row. AIUI these machines have a maximum memory of only 1GB. That's probably OK for now but might be problematic in the long term. 3. We have currently two new machines with loongson 3a processors to test. It will take a bit of time to finally get a working kernel on these, but that would also decrease build-times quite much. When do you expect them to be usable? If not any time soon then maybe we should try to get a couple of loongson 2f machines. Would four machines of this type be sufficient to replace all our exist swarm and 2e machines as buildds? If so, should we just get 5 (4buildd+1porterbox)? Cheers, -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130624085150.gc15...@anguilla.noreply.org
Re: DSA concerns for jessie architectures (mips*)
On Mon, Jun 24, 2013 at 4:51 PM, Peter Palfrader wea...@debian.org wrote: On Sat, 22 Jun 2013, Andreas Barth wrote: * mips: existing machines are either not reliable or too slow to keep up; we suspect that they may not be easily replaceable. Also, if we buy more mipsel machines we could convert the mipsel swarms to mips ones (and so replace broken machines, see below) - mostly depends on how urgent you think this is. If our existing eight-year old hardware is the only mips machines we can reasonably get then that doesn't bode well for mips. We don't think relying on the SWARMs (alone) is an option. * mipsel: the porter machine and some of the buildd machines have an implementation error for one opcode; missing kernel in the archive Different answers - select the one you like most: 1. We could buy a some loongson 2f machines (or newer), see e.g. http://www.tekmote.nl/epages/61504599.sf/nl_NL/?ObjectPath=/Shops/61504599/Products/CFL-006 plus some memory. These machines have kernels in the archive, and not the hardware bug with choking on too many nop-instructions in a row. AIUI these machines have a maximum memory of only 1GB. That's probably OK for now but might be problematic in the long term. 3. We have currently two new machines with loongson 3a processors to test. It will take a bit of time to finally get a working kernel on these, but that would also decrease build-times quite much. When do you expect them to be usable? If not any time soon then maybe we should try to get a couple of loongson 2f machines. Would four machines of this type be sufficient to replace all our exist swarm and 2e machines as buildds? If so, should we just get 5 (4buildd+1porterbox)? We have two 3A notebooks that Lemote donated directly to the student and mentor of the MIPS N32/N64 port GSoC project, the only blocking issue to use them as official buildd is supporting patches aren't accepted by upstream, otherwise they are working fine. A self-built version of Linux 3.6 with Lemote patches is used right now. It was a 4-core SMP system with 2GB RAM installed (upgrade seems hard for the notebook, though the CPU itself supports more), and was tested to be quite stable when doing test build of some mips64el packages. The stability of hardware is somewhat temperature-sensitive, which means when they are running with full parallel building load, they are only tested to be stable in a server room cooling to 17°C, but hang once every 1 or 2 days when put in a room of 25°C. There is no remote management facility available to the notebook, dunno for development boards or servers. We could ask Lemote for donation if we want those machines to provide build power of Debian, and I volunteer to help if needed. Regards, Aron -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMr=8w55dxzd7sz3r2kfz8cr2+yyrriqpvomlfvykrqx64k...@mail.gmail.com
Re: DSA concerns for jessie architectures (mips*)
On Mon, Jun 24, 2013 at 4:51 PM, Peter Palfrader wrote: If our existing eight-year old hardware is the only mips machines we can reasonably get then that doesn't bode well for mips. We don't think relying on the SWARMs (alone) is an option. Perhaps Calvium will interested in providing newer hardware now that there is a MIPS N64 GSoC project underway. They offered some decent hardware last year in association with such a port: http://lists.debian.org/debian-mips/2012/02/msg1.html http://wiki.debian.org/SummerOfCode2013/Projects#MIPS_N32.2FN64_ABI_port http://wiki.debian.org/SummerOfCode2013/StudentApplications/EleanorChen -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6HMxq_1Myr0CRsQ8pHMsv04KFU_S9pRdUwD=j2mvrs...@mail.gmail.com
Re: DSA concerns for jessie architectures (mips*)
On Mon, Jun 24, 2013 at 5:29 PM, Paul Wise p...@debian.org wrote: On Mon, Jun 24, 2013 at 4:51 PM, Peter Palfrader wrote: If our existing eight-year old hardware is the only mips machines we can reasonably get then that doesn't bode well for mips. We don't think relying on the SWARMs (alone) is an option. Perhaps Calvium will interested in providing newer hardware now that there is a MIPS N64 GSoC project underway. They offered some decent hardware last year in association with such a port: http://lists.debian.org/debian-mips/2012/02/msg1.html http://wiki.debian.org/SummerOfCode2013/Projects#MIPS_N32.2FN64_ABI_port http://wiki.debian.org/SummerOfCode2013/StudentApplications/EleanorChen I believe Cavium's David Daney is on debian-mips, we can talk to him to see if there is any possibility of making donation. As for the GSoC project, the student seems to not get access to the hardware Cavium offered, nor the main mentor (Cc'ed), so there is no feedback about stability/other stuff about those hardware. Regards, Aron -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMr=8w6v_b-veo1ep6nmssxuqxpvyo6yzqb+u7bhtbreb+y...@mail.gmail.com
Bug#706971: marked as done (transition: attica 0.4)
Your message dated Mon, 24 Jun 2013 12:20:21 +0200 with message-id 20130624102021.gt5...@betterave.cristau.org and subject line Re: Bug#706971: transition: attica 0.4 has caused the Debian Bug report #706971, regarding transition: attica 0.4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 706971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hello, I would like to request a slot for a small libattica 0.4.x transition. The newer attica source is already in experimental, and the transition affects just few (KDE-related) sources. The SONAME change is the following: * libattica-dev (src:attica): libattica0 - libattica0.4 The sources affected by the transition are: choqok kde4libs kdeplasma-addons kde-runtime smokekde there are also calligra and parley which build-depend on libattica-dev and checking for it at cmake time but not actually using it; should be enough to ignore them. Ben file: title = attica 0.4; is_affected = .build-depends ~ /libattica-dev/; is_good = .depends ~ libattica0.4; is_bad = .depends ~ libattica0; Thanks, -- Pino ---End Message--- ---BeginMessage--- On Mon, May 6, 2013 at 17:20:13 +0200, Pino Toscano wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hello, I would like to request a slot for a small libattica 0.4.x transition. The newer attica source is already in experimental, and the transition affects just few (KDE-related) sources. The SONAME change is the following: * libattica-dev (src:attica): libattica0 - libattica0.4 libattica0.4 | 0.4.1-2 |testing | amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc No more libattica0. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#713969: nmu: fsl_4.1.9-7 pygdchart2_0.beta1-3.4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Now that libgdchart-gd2 is fixed, this would help move along the libgd2-libgd3 transition a bit more. nmu fsl_4.1.9-7 pygdchart2_0.beta1-3.4 . ALL . -m Rebuild against libgd3 Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130624115418.ga11...@sarantium.pelham.vpn.ucam.org
Bug#713969: nmu: fsl_4.1.9-7 pygdchart2_0.beta1-3.4
On Mon, Jun 24, 2013 at 02:06:34PM +0200, Julien Cristau wrote: On Mon, Jun 24, 2013 at 12:54:32 +0100, Colin Watson wrote: Now that libgdchart-gd2 is fixed, this would help move along the libgd2-libgd3 transition a bit more. nmu fsl_4.1.9-7 pygdchart2_0.beta1-3.4 . ALL . -m Rebuild against libgd3 Already done. (Please keep these things on the transition bug though, instead of opening new ones.) Ah, sorry, didn't know what the right thing was. Thanks. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130624121315.gx1...@riva.ucam.org
Bug#713975: RM: turpial/1.6.9-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi folks, I request the removal of turpial from stable and testing. turpial is a Twitter client that relies on API v1 and Twitter removed support for that on July 11th[1]. Later, upstream announced[2] that they are not going to support or maintain 1.6.9 branch so it makes no sense to keep including this package on stable and testing due to bugs like #712519. 1. https://dev.twitter.com/blog/api-v1-is-retired 2. http://turpial.org.ve/2013/06/why-turpial-169-is-not-working/ -- System Information: Debian Release: 6.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/ Faith means not wanting to know what is true. -- Nietzsche
Bug#713975: RM: turpial/1.6.9-1
On Mon, Jun 24, 2013 at 09:49:33 -0300, Miguel Landaeta wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi folks, I request the removal of turpial from stable and testing. Hinted for removal from testing. Cheers, Julien signature.asc Description: Digital signature
Re: DSA concerns for jessie architectures (mips*)
On Mon, Jun 24, 2013 at 05:34:42PM +0800, Aron Xu wrote: On Mon, Jun 24, 2013 at 5:29 PM, Paul Wise p...@debian.org wrote: On Mon, Jun 24, 2013 at 4:51 PM, Peter Palfrader wrote: If our existing eight-year old hardware is the only mips machines we can reasonably get then that doesn't bode well for mips. We don't think relying on the SWARMs (alone) is an option. Perhaps Cavium will interested in providing newer hardware now that there is a MIPS N64 GSoC project underway. They offered some decent hardware last year in association with such a port: http://lists.debian.org/debian-mips/2012/02/msg1.html http://wiki.debian.org/SummerOfCode2013/Projects#MIPS_N32.2FN64_ABI_port http://wiki.debian.org/SummerOfCode2013/StudentApplications/EleanorChen I believe Cavium's David Daney is on debian-mips, we can talk to him to see if there is any possibility of making donation. It would be wonderful to refresh our mips environment as our current mips environment is not healthy. We gladly accept hardware donations but would appreciate if the donated hardware be equivalent to that available commercially. Of the four existing donated boxen that we operate at ubcece, one has never worked (fatally defective) and two are very unreliable. We also had to modify them to boot on power-up. Do the Cavium machines have any remote management features (similar to Sun ALOM, HP iLO, Dell DRAC) that allow access to a serial console and to power management? Alternatively, can they be configured to power on after a power loss so we can attach them to a remotely controlled power distribution unit? Do they boot from local storage? Any help you can provide in securing newer mips equipment is appreciated. We MUST refresh our mips environment if we wish to continue offering a mips port. As mentioned, we will need a number of machines to satisfy the various requirements (geographically distributed buildd machines, accessible porter machine(s), etc.). As for the GSoC project, the student seems to not get access to the hardware Cavium offered, nor the main mentor (Cc'ed), so there is no feedback about stability/other stuff about those hardware. Why were the GSoC students unable to obtain access to the hardware? Thanks, Luca -- Luca Filipozzi // Debian System Administration Team http://www.crowdrise.com/SupportDebian -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130624140923.ga21...@emyr.net
Re: DSA concerns for jessie architectures (mips*)
On Mon, Jun 24, 2013 at 10:09 PM, Luca Filipozzi lfili...@debian.org wrote: On Mon, Jun 24, 2013 at 05:34:42PM +0800, Aron Xu wrote: On Mon, Jun 24, 2013 at 5:29 PM, Paul Wise p...@debian.org wrote: On Mon, Jun 24, 2013 at 4:51 PM, Peter Palfrader wrote: If our existing eight-year old hardware is the only mips machines we can reasonably get then that doesn't bode well for mips. We don't think relying on the SWARMs (alone) is an option. Perhaps Cavium will interested in providing newer hardware now that there is a MIPS N64 GSoC project underway. They offered some decent hardware last year in association with such a port: http://lists.debian.org/debian-mips/2012/02/msg1.html http://wiki.debian.org/SummerOfCode2013/Projects#MIPS_N32.2FN64_ABI_port http://wiki.debian.org/SummerOfCode2013/StudentApplications/EleanorChen I believe Cavium's David Daney is on debian-mips, we can talk to him to see if there is any possibility of making donation. It would be wonderful to refresh our mips environment as our current mips environment is not healthy. We gladly accept hardware donations but would appreciate if the donated hardware be equivalent to that available commercially. Of the four existing donated boxen that we operate at ubcece, one has never worked (fatally defective) and two are very unreliable. We also had to modify them to boot on power-up. Do the Cavium machines have any remote management features (similar to Sun ALOM, HP iLO, Dell DRAC) that allow access to a serial console and to power management? Alternatively, can they be configured to power on after a power loss so we can attach them to a remotely controlled power distribution unit? Do they boot from local storage? Any help you can provide in securing newer mips equipment is appreciated. We MUST refresh our mips environment if we wish to continue offering a mips port. As mentioned, we will need a number of machines to satisfy the various requirements (geographically distributed buildd machines, accessible porter machine(s), etc.). As for the GSoC project, the student seems to not get access to the hardware Cavium offered, nor the main mentor (Cc'ed), so there is no feedback about stability/other stuff about those hardware. Why were the GSoC students unable to obtain access to the hardware? David once said he has prepared the machine, but we haven't got response from him when asking for shell access. Also, are you interested in asking Lemote for there Loongson 3A machines? Regards, Aron -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMr=8w4BvXT=yYidQ3BP6Q-a6vJa1_Dsd=jaq9x5wpjctfb...@mail.gmail.com
Re: DSA concerns for jessie architectures (mips*)
On Mon, Jun 24, 2013 at 10:36:20PM +0800, Aron Xu wrote: On Mon, Jun 24, 2013 at 10:09 PM, Luca Filipozzi lfili...@debian.org wrote: On Mon, Jun 24, 2013 at 05:34:42PM +0800, Aron Xu wrote: On Mon, Jun 24, 2013 at 5:29 PM, Paul Wise p...@debian.org wrote: On Mon, Jun 24, 2013 at 4:51 PM, Peter Palfrader wrote: If our existing eight-year old hardware is the only mips machines we can reasonably get then that doesn't bode well for mips. We don't think relying on the SWARMs (alone) is an option. Perhaps Cavium will interested in providing newer hardware now that there is a MIPS N64 GSoC project underway. They offered some decent hardware last year in association with such a port: http://lists.debian.org/debian-mips/2012/02/msg1.html http://wiki.debian.org/SummerOfCode2013/Projects#MIPS_N32.2FN64_ABI_port http://wiki.debian.org/SummerOfCode2013/StudentApplications/EleanorChen I believe Cavium's David Daney is on debian-mips, we can talk to him to see if there is any possibility of making donation. It would be wonderful to refresh our mips environment as our current mips environment is not healthy. We gladly accept hardware donations but would appreciate if the donated hardware be equivalent to that available commercially. Of the four existing donated boxen that we operate at ubcece, one has never worked (fatally defective) and two are very unreliable. We also had to modify them to boot on power-up. Do the Cavium machines have any remote management features (similar to Sun ALOM, HP iLO, Dell DRAC) that allow access to a serial console and to power management? Alternatively, can they be configured to power on after a power loss so we can attach them to a remotely controlled power distribution unit? Do they boot from local storage? Any help you can provide in securing newer mips equipment is appreciated. We MUST refresh our mips environment if we wish to continue offering a mips port. As mentioned, we will need a number of machines to satisfy the various requirements (geographically distributed buildd machines, accessible porter machine(s), etc.). As for the GSoC project, the student seems to not get access to the hardware Cavium offered, nor the main mentor (Cc'ed), so there is no feedback about stability/other stuff about those hardware. Why were the GSoC students unable to obtain access to the hardware? David once said he has prepared the machine, but we haven't got response from him when asking for shell access. That's unfortunate. Also, are you interested in asking Lemote for there Loongson 3A machines? Sure. My objective is to get functioning equipment so that the mips port is supported. I'm prepared to receive a mix of equipment from a number of vendors or just from one... as long the requirements (commercially available, warranty / support, out of band management, etc.) are met, I'm not partial one way or the other. The only challenge I see with the 3A machines is the comment about needing a lot of energy/time to get a working kernel... that would be a problem for us, obviously. Thanks, Luca -- Luca Filipozzi http://www.crowdrise.com/SupportDebian -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130624153448.ga26...@emyr.net
Re: Bugs in packages meep-*
Dear release team, I uploaded the new versions to unstable now ... Thorsten On Wed, 12 Jun 2013, Thorsten Alteholz wrote: Dear release team, unfortunately the packages meep-* contain bugs that makes it impossible to develop own software with libmeep. As directory names are wrong, especially users of Live CDs might have problems using these packages now (actually I got the initial bug report from a user of such a CD). I attached four debdiffs for packages meep-lam4[1], meep-openmpi[2], meep-mpich2[3] and meep-mpi-default[4]. Can you please tell me whether these bugs shall be fixed in Wheezy. In case they should, as the versions in sid and wheezy are the same, shall I upload the new packages to sid now? Best regards Thorsten [1] meep-lam4: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711767 [2] meep-openmpi: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711766 [3] meep-mpich2: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711768 [4] meep-mpi-default: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711765 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.lnx.4.64.1306241906220.19...@tor.gallien.in-chemnitz.de
Re: DSA concerns for jessie architectures
On Sat, 2013-06-22 at 19:26 +0200, Martin Zobel-Helas wrote: At our recent Essen sprint, DSA went through the release qualification matrix (for wheezy, as there isn't one for jessie, yet) and defined a set of requirements that we consider necessary for us to support a port for the next stable release. [...] Based on the list of requirements enumerated above, we currentlty are concerned about the following architectures from the perspective of using them as debian.org machines: I've folded these in to an initial matrix for jessie, assuming that any architecture which was not explicitly mentioned is not currently a concern for DSA. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1372098990.4554.5.ca...@jacala.jungle.funky-badger.org
Bug#709813: Please give back 0ad on amd64
On Mon, Jun 24, 2013 at 12:19:03AM -0700, Vincent Cheng wrote: Dear wanna-build team, Please give back 0ad on amd64 on a buildd other than barber (i.e. retry until some other buildd takes it). I understand that the issue is in nvidia-texture-tools (#713966), and maybe we should wait for that to get fixed? I've set a dep-wait for that. Kurt -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130624194151.ga1...@roeckx.be
Re: DSA concerns for jessie architectures
]] Adam D. Barratt I've folded these in to an initial matrix for jessie, assuming that any architecture which was not explicitly mentioned is not currently a concern for DSA. Thanks, much appreciated! -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/m2wqpjxpew@rahvafeir.err.no
Re: DSA concerns for jessie architectures (mips*)
On Mon, 24 Jun 2013, Andreas Barth wrote: So, let's perhaps look at the situation again in two months and see where we are and if it's worth to do something else inbetween or not. Ok, please report back in two months time. Cheers, weasel -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130624194626.gn15...@anguilla.noreply.org
Bug#713975: RM: turpial/1.6.9-1
Control: clone -1 -2 Control: tags -2 + wheezy Control: retitle -2 RM: turpial -- RoM; broken by twitter changes On Mon, 2013-06-24 at 09:49 -0300, Miguel Landaeta wrote: I request the removal of turpial from stable and testing. Please don't use a single bug for removal from multiple suites; fixing. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1372107591.4554.8.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#713975: RM: turpial/1.6.9-1
Processing control commands: clone -1 -2 Bug #713975 [release.debian.org] RM: turpial/1.6.9-1 Bug 713975 cloned as bug 714023 tags -2 + wheezy Bug #714023 [release.debian.org] RM: turpial/1.6.9-1 Added tag(s) wheezy. retitle -2 RM: turpial -- RoM; broken by twitter changes Bug #714023 [release.debian.org] RM: turpial/1.6.9-1 Changed Bug title to 'RM: turpial -- RoM; broken by twitter changes' from 'RM: turpial/1.6.9-1' -- 713975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713975 714023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b713975.13721076018118.transcr...@bugs.debian.org
Re: DSA concerns for jessie architectures (mips*)
On 06/24/2013 07:36 AM, Aron Xu wrote: On Mon, Jun 24, 2013 at 10:09 PM, Luca Filipozzi lfili...@debian.org wrote: On Mon, Jun 24, 2013 at 05:34:42PM +0800, Aron Xu wrote: On Mon, Jun 24, 2013 at 5:29 PM, Paul Wise p...@debian.org wrote: On Mon, Jun 24, 2013 at 4:51 PM, Peter Palfrader wrote: If our existing eight-year old hardware is the only mips machines we can reasonably get then that doesn't bode well for mips. We don't think relying on the SWARMs (alone) is an option. Perhaps Cavium will interested in providing newer hardware now that there is a MIPS N64 GSoC project underway. They offered some decent hardware last year in association with such a port: http://lists.debian.org/debian-mips/2012/02/msg1.html http://wiki.debian.org/SummerOfCode2013/Projects#MIPS_N32.2FN64_ABI_port http://wiki.debian.org/SummerOfCode2013/StudentApplications/EleanorChen I believe Cavium's David Daney is on debian-mips, we can talk to him to see if there is any possibility of making donation. It would be wonderful to refresh our mips environment as our current mips environment is not healthy. We gladly accept hardware donations but would appreciate if the donated hardware be equivalent to that available commercially. Of the four existing donated boxen that we operate at ubcece, one has never worked (fatally defective) and two are very unreliable. We also had to modify them to boot on power-up. Do the Cavium machines have any remote management features (similar to Sun ALOM, HP iLO, Dell DRAC) that allow access to a serial console and to power management? Alternatively, can they be configured to power on after a power loss so we can attach them to a remotely controlled power distribution unit? Do they boot from local storage? Any help you can provide in securing newer mips equipment is appreciated. We MUST refresh our mips environment if we wish to continue offering a mips port. As mentioned, we will need a number of machines to satisfy the various requirements (geographically distributed buildd machines, accessible porter machine(s), etc.). As for the GSoC project, the student seems to not get access to the hardware Cavium offered, nor the main mentor (Cc'ed), so there is no feedback about stability/other stuff about those hardware. Why were the GSoC students unable to obtain access to the hardware? David once said he has prepared the machine, but we haven't got response from him when asking for shell access. The good news: Debian GNU/Linux 6.0 ebh5600-dd ttyS0 ebh5600-dd login: root Password: Last login: Tue Jun 4 11:25:39 PDT 2013 on ttyS0 Linux ebh5600-dd 3.9.4 #18 SMP PREEMPT Tue Jun 4 11:18:44 PDT 2013 mips64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. root@ebh5600-dd:~# uptime 15:11:53 up 20 days, 3:45, 1 user, load average: 0.00, 0.01, 0.05 root@ebh5600-dd:~# df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 910G 26G 838G 3% / tmpfs 2.0G 0 2.0G 0% /lib/init/rw udev 10M 24K 10M 1% /dev tmpfs 2.0G 0 2.0G 0% /dev/shm The slightly less good news: I am leaving on vacation until July 13, so I cannot get the thing on a public network until I get back. Also I don't recall any requests for shell access after the initial discussions about the system David Daney Also, are you interested in asking Lemote for there Loongson 3A machines? Regards, Aron -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c8b5f7.20...@gmail.com
Re: DSA concerns for jessie architectures (mips*)
On Mon, Jun 24, 2013 at 02:11:19PM -0700, David Daney wrote: On 06/24/2013 07:36 AM, Aron Xu wrote: On Mon, Jun 24, 2013 at 10:09 PM, Luca Filipozzi lfili...@debian.org wrote: On Mon, Jun 24, 2013 at 05:34:42PM +0800, Aron Xu wrote: On Mon, Jun 24, 2013 at 5:29 PM, Paul Wise p...@debian.org wrote: On Mon, Jun 24, 2013 at 4:51 PM, Peter Palfrader wrote: If our existing eight-year old hardware is the only mips machines we can reasonably get then that doesn't bode well for mips. We don't think relying on the SWARMs (alone) is an option. Perhaps Cavium will interested in providing newer hardware now that there is a MIPS N64 GSoC project underway. They offered some decent hardware last year in association with such a port: http://lists.debian.org/debian-mips/2012/02/msg1.html http://wiki.debian.org/SummerOfCode2013/Projects#MIPS_N32.2FN64_ABI_port http://wiki.debian.org/SummerOfCode2013/StudentApplications/EleanorChen I believe Cavium's David Daney is on debian-mips, we can talk to him to see if there is any possibility of making donation. It would be wonderful to refresh our mips environment as our current mips environment is not healthy. We gladly accept hardware donations but would appreciate if the donated hardware be equivalent to that available commercially. Of the four existing donated boxen that we operate at ubcece, one has never worked (fatally defective) and two are very unreliable. We also had to modify them to boot on power-up. Do the Cavium machines have any remote management features (similar to Sun ALOM, HP iLO, Dell DRAC) that allow access to a serial console and to power management? Alternatively, can they be configured to power on after a power loss so we can attach them to a remotely controlled power distribution unit? Do they boot from local storage? Any help you can provide in securing newer mips equipment is appreciated. We MUST refresh our mips environment if we wish to continue offering a mips port. As mentioned, we will need a number of machines to satisfy the various requirements (geographically distributed buildd machines, accessible porter machine(s), etc.). As for the GSoC project, the student seems to not get access to the hardware Cavium offered, nor the main mentor (Cc'ed), so there is no feedback about stability/other stuff about those hardware. Why were the GSoC students unable to obtain access to the hardware? David once said he has prepared the machine, but we haven't got response from him when asking for shell access. The good news: Debian GNU/Linux 6.0 ebh5600-dd ttyS0 ebh5600-dd login: root Password: Last login: Tue Jun 4 11:25:39 PDT 2013 on ttyS0 Linux ebh5600-dd 3.9.4 #18 SMP PREEMPT Tue Jun 4 11:18:44 PDT 2013 mips64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. root@ebh5600-dd:~# uptime 15:11:53 up 20 days, 3:45, 1 user, load average: 0.00, 0.01, 0.05 root@ebh5600-dd:~# df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 910G 26G 838G 3% / tmpfs 2.0G 0 2.0G 0% /lib/init/rw udev 10M 24K 10M 1% /dev tmpfs 2.0G 0 2.0G 0% /dev/shm The slightly less good news: I am leaving on vacation until July 13, so I cannot get the thing on a public network until I get back. That's great! Happy to continue the conversation regarding these machines when you return. Have a good vacation. Also I don't recall any requests for shell access after the initial discussions about the system Ah! Seems like some miscommunication or misunderstanding. Thanks for correcting the record. Let's chat when you get back, Luca -- Luca Filipozzi http://www.crowdrise.com/SupportDebian -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130624215058.ga...@emyr.net
Bug#710143: transition: libraw
2013/5/28 Luca Falavigna dktrkr...@debian.org: freeimage FTBFS (#710133), but upstream already has a patch to fix it. Also shotwell FTBFS (#710141), issue has been forwarded upstream. Blockers have patches to allow build against newer libraw, so this transition should proceed smoothly. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cadk7b0oeafwvh2oahufz851r+wz1tpnoggwk9b0jdr_kjdx...@mail.gmail.com