Bug#713049: pu: gosa - fix mass import of users in wheezy
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
User: debian-...@lists.debian.org
Usertags: debian-edu
Here is a request to approve an upload of gosa to wheezy, to fix a bug
Debian Edu need to have fixed in our Debian Edu Wheezy release. The
same fix was uploaded as versoin 2.7.4-4.3 to unstable with this
changelog entry:
* debian/patches/fix-mass-ldapimport.patch: New patch, fixes LDAP mass
import, by Giorgio Pioda and Petter Reinholdtsen. (Closes: #698840)
We need it to make sure schools can create users for all teachers and
users in a school starting to use Debian Edu (or migrating to the new
version) without having to create them one by one.
Attached is the complete diff between version 2.7.4-4.3 in unstable and
version 2.7.4-4.2 in wheezy.
Please let us know if this is OK before we upload, and tell us which
version number to use for this upload.
--
Happy hacking
Petter Reinholdtsen
diff -Nru gosa-2.7.4/debian/changelog gosa-2.7.4/debian/changelog
--- gosa-2.7.4/debian/changelog 2013-02-07 21:28:31.0 +0100
+++ gosa-2.7.4/debian/changelog 2013-06-14 11:00:02.0 +0200
@@ -1,3 +1,11 @@
+gosa (2.7.4-4.3) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/patches/fix-mass-ldapimport.patch: New patch, fixes LDAP mass
+import, by Giorgio Pioda and Petter Reinholdtsen. (Closes: #698840)
+
+ -- Michael Banck Fri, 14 Jun 2013 10:59:37 +0200
+
gosa (2.7.4-4.2) unstable; urgency=low
[ Jonathan Wiltshire ]
diff -Nru gosa-2.7.4/debian/patches/fix-mass-ldapimport.patch gosa-2.7.4/debian/patches/fix-mass-ldapimport.patch
--- gosa-2.7.4/debian/patches/fix-mass-ldapimport.patch 1970-01-01 01:00:00.0 +0100
+++ gosa-2.7.4/debian/patches/fix-mass-ldapimport.patch 2013-06-14 10:58:23.0 +0200
@@ -0,0 +1,48 @@
+Index: addons/ldapmanager/class_csvimport.inc
+===
+--- gosa/ldapmanager/addons/ldapmanager/class_csvimport.inc (revisjon 21231)
gosa/ldapmanager/addons/ldapmanager/class_csvimport.inc (arbeidskopi)
+@@ -175,17 +175,25 @@
+
+
+ /* Set all submitted vars */
+-if(is_array($keys))
++if(is_array($keys)){
+ foreach($keys as $key) {
+ if($key != "status"){
+ $this->usertab->$key = $dat[$key];
++ foreach($this->usertab->by_object as $pname => $plugin){
++if(isset($this->usertab->by_object[$pname]->$key)){
++ $this->usertab->by_object[$pname]->$key = $dat[$key];
++}
++ }
+ }
+ }
++}
+
+ /* Initialize template */
+ if($this->csvinfo['tplid']!=0){
+- $this->usertab->adapt_from_template($this->csvinfo['arrtempls'][$this->csvinfo['tplid']]['dn']);
+- $this->usertab->save_object();
++ $tpl_dn = $this->csvinfo['arrtempls'][$this->csvinfo['tplid']]['dn'];
++ $this->usertab->adapt_from_template($tpl_dn,array("uid","cn","givenName","sn"));
++ $tpl_base = preg_replace("/^[^,]+,".preg_quote(get_people_ou(), '/i')."/", '', $tpl_dn);
++ $this->usertab->by_object['user']->base= $tpl_base;
+ } else {
+
+ /* Reset vars */
+Index: addons/ldapmanager/contentcsv.tpl
+===
+--- gosa/ldapmanager/addons/ldapmanager/contentcsv.tpl (revisjon 21231)
gosa/ldapmanager/addons/ldapmanager/contentcsv.tpl (arbeidskopi)
+@@ -1,5 +1,3 @@
+-Temporary disabled
+-
diff -Nru gosa-2.7.4/debian/patches/series gosa-2.7.4/debian/patches/series
--- gosa-2.7.4/debian/patches/series 2012-06-19 09:57:50.0 +0200
+++ gosa-2.7.4/debian/patches/series 2013-06-08 18:58:37.0 +0200
@@ -5,3 +5,4 @@
03_fix_class_mapping.patch
04_fix_locale_location.patch
no-image-warning.patch
+fix-mass-ldapimport.patch
plans for automake 1.11?
Hi, automake1.11 is currently Provided by the automake binary package in the automake1.11 source package. However, that binary package is superseded by the automake binary package built by the automake1.13 source package. As a result, the following 37 packages fail to build: aumix conky cstream dbus-c++ denemo enna enscript freetalk freqtweak garden-of-coloured-lights gesftpserver gmerlin hodie ical2html ijs jack-audio-connection-kit jamin jbig2dec kannel-sqlbox libgadu liblrdf libnfsidmap libshout madplay mailsync maxima morituri openocd pd-iemmatrix qonk source-highlight torcs ucommon unicap urlview webdruid xpilot-ng Do you plan to rename the automake binary package to automake1.11 (in the automake1.11 source package)? Or just to remove the automake1.11 source package? Thanks Lucas -- 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/20130622114748.ga24...@xanadu.blop.info
Bug#713798: nmu: check_0.9.10-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi, For some reasons, the detection whether specific flags were needed to compile with pthread support didn't return the correct value resulting in a generated .pc file missing some flags. I tried rebuilding the package on my amd64 machine and now needed flags are properly detected. See: #712140 nmu check_0.9.10-2 . ALL . -m "Properly detect flags needed for pthreads support" Cheers Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20130622161652.10137.90587.report...@fornost.bigon.be
Bug#710782: transition: openturns
On 2013/6/2 D. Barbier wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hello, > > openturns 1.1 has been uploaded into experimental, and introduces a > soname bump. Version 1.1-3 uploaded few days ago should build fine > everywhere if buildds have enough RAM, all issues found in earlier > versions should now be fixed. > Thus I would like to upload this version into unstable. > > No packages depend directly on libopenturns0.1, but eficas > build-depends on python-openturns (which itself depends on > libopenturns0.1/0.2) and feel++ build-depends on libopenturns-dev. It > is not clear to me whether these dependencies are really necessary, > but this is another story. > > Please tell me whether uploading openturns 1.1-3 into unstable is fine by you. Hello, Here is an update: * openturns 1.0-4 just received an RC bug (#713524), which is already fixed in experimental. * openturns 1.1-3 has still not been built on armel, mips and mipsel, and build failed on sparc with a cryptic message (The bug is not reproducible, so it is likely a hardware or OS problem) * Upstream is preparing a new release; I would really like to move 1.1 into sid so that I can upload 1.2 into experimental. Please tell me whether I can upload opennturns 1.1 into sid. Thanks, Denis -- 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/CAMqf4EG8fm++V+Sx9jinBVWqtVizU_VJUer=hkvv4zrevhq...@mail.gmail.com
DSA concerns for jessie architectures
[please consider replacing debian-ports@ldo with the appropriate port specific list when replying.] Comrades! 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. We have limited these requirements to whether DSA can support a port well or not, and we wanted to establish these requirements early in the release cycle so that our concerns can be addressed. Our requirements for machines are not new; they are: * reliability - The stable release manager requires that we operate three machines for each port: two buildd machines in different locations and one porter machine. These machines must be reliable (see mips for counterexample). * out of band management - We require the ability to manage the machines independently of their primary network interface: serial console or better, remotely-controllable power. * supportability - We require that the machines be commercialy available (within financial constraints) and that they be supportable through a warranty or post-warranty support or are otherwise easy to replace. * stability - We require that the machine's architecture have an actively-maintained stable kernel in the archive. * environment - We require that packages critical for DSA operations be available: puppet, samhain, syslog-ng, ferm/pf, etc. Historically, we have not been enforcing these requirements strictly and this has caused / continues to cause us significant operational challenges resulting in our inability to render the service levels that should reasonably be expected of us. Therefore, we believe it is important that all debian.org machines meet these requirements. 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: * armel: no remote management (being worked on); no archive kernel for the machines we use. * armhf: no remote management (being worked on). * hurd: no puppet/ruby broken (for 3 months+); lack of firewall support. * mips: existing machines are either not reliable or too slow to keep up; we suspect that they may not be easily replaceable. * mipsel: the porter machine and some of the buildd machines have an implementation error for one opcode; missing kernel in the archive * sparc: no working nflog (mild concern); no stable kernels in stable (compiling clisp for instance crashes the kernel reliably on smetana). We need to run sparc with oldstable kernels to provide stable machines. That's not an option for long. * s390/x: no stable kernels; not sourceable within our budgets (currently relying on sponsors - this has not been a problem so far). We believe that it is the responsibility of the porter community to either source hardware or provide DSA with proposals regarding the hardware Debian should buy. We encourage the porter community to actively assist DSA with the resolution of the above noted concerns regarding various ports. Thanks, Martin Zobel-Helas Debian System Administration Team -- "It pays to be obvious, especially if you have a reputation for being subtle." Martin Zobel-Helas Debian System Administrator Debian & GNU/Linux Developer Debian Listmaster http://about.me/zobel Debian Webmaster GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B signature.asc Description: Digital signature
Processed: Re: Bug#712622: pu: package wv2/0.4.2.dfsg.1-9.1
Processing control commands: > tags 712622 + confirmed - moreinfo Bug #712622 [release.debian.org] pu: package wv2/0.4.2.dfsg.1-9.1 Ignoring request to alter tags of bug #712622 to the same tags previously set Bug #712622 [release.debian.org] pu: package wv2/0.4.2.dfsg.1-9.1 Ignoring request to alter tags of bug #712622 to the same tags previously set > tags 712623 + confirmed - moreinfo Bug #712623 [release.debian.org] opu: package wv2/0.4.2.dfsg.1-1 Ignoring request to alter tags of bug #712623 to the same tags previously set Bug #712623 [release.debian.org] opu: package wv2/0.4.2.dfsg.1-1 Ignoring request to alter tags of bug #712623 to the same tags previously set -- 712622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712622 712623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712623 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.b712623.137192289422997.transcr...@bugs.debian.org
Bug#712622: pu: package wv2/0.4.2.dfsg.1-9.1
Control: tags 712622 + confirmed - moreinfo Control: tags 712623 + confirmed - moreinfo On Thu, 2013-06-20 at 02:36 +0100, Olly Betts wrote: > On Tue, Jun 18, 2013 at 07:26:39PM +0100, Adam D. Barratt wrote: > > What version were you proposing to use for the re-repack? > > I'm open to guidance as to what's best. > > The repacked upstream tarball would be the same as testing/unstable has, > so perhaps 0.4.2.dfsg.2-1~deb7+1 (and 0.4.2.dfsg.2-1~deb6+1 for opu)? ~deb7u1 and ~deb6u1 would be more consistent with our usual numbering policy (well, for wheezy, but ~squeeze wouldn't really work in this case). Other than that, if the only change is the removal of the files, please use "wheezy" and "squeeze" as the changelog distributions and go ahead. 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/1371922881.19215.8.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#712622: pu: package wv2/0.4.2.dfsg.1-9.1
Processing control commands: > tags 712622 + confirmed - moreinfo Bug #712622 [release.debian.org] pu: package wv2/0.4.2.dfsg.1-9.1 Added tag(s) confirmed. Bug #712622 [release.debian.org] pu: package wv2/0.4.2.dfsg.1-9.1 Removed tag(s) moreinfo. > tags 712623 + confirmed - moreinfo Bug #712623 [release.debian.org] opu: package wv2/0.4.2.dfsg.1-1 Added tag(s) confirmed. Bug #712623 [release.debian.org] opu: package wv2/0.4.2.dfsg.1-1 Removed tag(s) moreinfo. -- 712622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712622 712623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712623 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.b712622.137192289422988.transcr...@bugs.debian.org
Processed: user release.debian....@packages.debian.org, usertagging 713049, tagging 713049
Processing commands for cont...@bugs.debian.org: > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was a...@adam-barratt.org.uk). > # stable updates are not unblocks... > usertags 713049 = pu There were no usertags set. Usertags are now: pu. > tags 713049 + wheezy Bug #713049 [release.debian.org] pu: gosa - fix mass import of users in wheezy Added tag(s) wheezy. > thanks Stopping processing here. Please contact me if you need assistance. -- 713049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713049 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.137192307624477.transcr...@bugs.debian.org
Re: DSA concerns for jessie architectures
* Martin Zobel-Helas (zo...@debian.org) [130622 19:27]: > [please consider replacing debian-ports@ldo with the appropriate port > specific list when replying.] According to lists.d.o the status of debian-ports is: dead list. It at least isn't the list for all porters to read. > * mips: existing machines are either not reliable or too slow to keep > up; we suspect that they may not be easily replaceable. We're about to get newer machines which are both stable and fast (the two instable machines are pre-alpha versions, and should be replaced; but this is not an architecture-topic but rather an machine-topic). 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. > * 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. 2. We get the kernel team to accept the additional kernel config for 2e (I'm too lazy now to search for the bug report from ages ago, but the only difference needed to build kernels for our 2e-machines is an additional kernel config, no code changes necessary) 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. Andi -- 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/20130622180631.gy28...@mails.so.argh.org
Re: DSA concerns for jessie architectures
* Martin Zobel-Helas (zo...@debian.org) wrote: > [please consider replacing debian-ports@ldo with the appropriate port > specific list when replying.] > > * armel: no remote management (being worked on); no archive kernel for > the machines we use. > > * armhf: no remote management (being worked on). Generally I've seen most ARM boards managed via separate PDUs and serial concentrators; there are ARM systems that as I understand are built for remote management - but if you've got PDUs setup then you can control nigh on anything; and given the current draw on many of those machines it doesn't need to be expensive PDUs, simple USB driven relay setups can be sufficient (although it gets hairier if you want to control hard drive power etc). Dave -- -Open up your eyes, open up your mind, open up your code --- / Dr. David Alan Gilbert| Running GNU/Linux | Happy \ \ gro.gilbert @ treblig.org | | In Hex / \ _|_ http://www.treblig.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/20130622175739.GB25102@gallifrey
Re: DSA concerns for jessie architectures
Martin Zobel-Helas writes: > [please consider replacing debian-ports@ldo with the appropriate port > specific list when replying.] > > Comrades! > > 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. > > We have limited these requirements to whether DSA can support a port > well or not, and we wanted to establish these requirements early in the > release cycle so that our concerns can be addressed. > > Our requirements for machines are not new; they are: > > * reliability - The stable release manager requires that we operate > three machines for each port: two buildd machines in different > locations and one porter machine. These machines must be reliable > (see mips for counterexample). > * out of band management - We require the ability to manage the machines > independently of their primary network interface: serial console or > better, remotely-controllable power. > * supportability - We require that the machines be commercialy available > (within financial constraints) and that they be supportable through a > warranty or post-warranty support or are otherwise easy to replace. > * stability - We require that the machine's architecture have an > actively-maintained stable kernel in the archive. > * environment - We require that packages critical for DSA operations be > available: puppet, samhain, syslog-ng, ferm/pf, etc. > > Historically, we have not been enforcing these requirements strictly > and this has caused / continues to cause us significant operational > challenges resulting in our inability to render the service levels that > should reasonably be expected of us. Therefore, we believe it is > important that all debian.org machines meet these requirements. > > 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: > > * armel: no remote management (being worked on); no archive kernel for > the machines we use. afair buildd are: marvell DB-78x00 -> should be supported by armel kernel flavour mx78xx0 thecus n2100 -> should be supported by armel kernel flavour iop32x Please, can you explain what's exactily missing on kernel support side ? thanks, Arnaud -- 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/87bo6yar46@lebrac.rtp-net.org
Re: DSA concerns for jessie architectures
On Sat, Jun 22, 2013 at 09:21:29PM +0200, Arnaud Patard wrote: > Martin Zobel-Helas writes: > > > * armel: no remote management (being worked on); no archive kernel for > > the machines we use. > > > afair buildd are: > marvell DB-78x00 -> should be supported by armel kernel flavour mx78xx0 > thecus n2100 -> should be supported by armel kernel flavour iop32x > > Please, can you explain what's exactily missing on kernel support > side ? There is no mx78xx0 kernel in the Debian archive as far as I can see. There is a linux-image-3.2.0-4-iop32x however. 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/20130622194113.ga...@roeckx.be
Re: DSA concerns for jessie architectures
Kurt Roeckx writes: > On Sat, Jun 22, 2013 at 09:21:29PM +0200, Arnaud Patard wrote: >> Martin Zobel-Helas writes: >> >> > * armel: no remote management (being worked on); no archive kernel for >> > the machines we use. >> >> >> afair buildd are: >> marvell DB-78x00 -> should be supported by armel kernel flavour mx78xx0 >> thecus n2100 -> should be supported by armel kernel flavour iop32x >> >> Please, can you explain what's exactily missing on kernel support >> side ? > > There is no mx78xx0 kernel in the Debian archive as far as I can > see. There is a linux-image-3.2.0-4-iop32x however. > Sorry, I made a typo. It's mv78xx0: http://packages.debian.org/wheezy/linux-image-3.2.0-4-mv78xx0 Arnaud -- 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/877ghmaq0i@lebrac.rtp-net.org
Re: DSA concerns for jessie architectures
On Sat, Jun 22, 2013 at 09:45:17PM +0200, Arnaud Patard wrote: > Kurt Roeckx writes: > > > On Sat, Jun 22, 2013 at 09:21:29PM +0200, Arnaud Patard wrote: > >> Martin Zobel-Helas writes: > >> > >> > * armel: no remote management (being worked on); no archive kernel for > >> > the machines we use. > >> > >> > >> afair buildd are: > >> marvell DB-78x00 -> should be supported by armel kernel flavour mx78xx0 > >> thecus n2100 -> should be supported by armel kernel flavour iop32x > >> > >> Please, can you explain what's exactily missing on kernel support > >> side ? > > > > There is no mx78xx0 kernel in the Debian archive as far as I can > > see. There is a linux-image-3.2.0-4-iop32x however. > > > > Sorry, I made a typo. It's mv78xx0: > http://packages.debian.org/wheezy/linux-image-3.2.0-4-mv78xx0 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? 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/20130622195145.ga1...@roeckx.be
Processed: reassign 713263 to libgd-gd2-noxpm-perl, forcibly merging 709047 713263
Processing commands for cont...@bugs.debian.org: > reassign 713263 libgd-gd2-noxpm-perl Bug #713263 [src:libgd-gd2-noxpm-perl] libgd-gd2-noxpm-perl: FTBFS: tests failed Bug reassigned from package 'src:libgd-gd2-noxpm-perl' to 'libgd-gd2-noxpm-perl'. No longer marked as found in versions libgd-gd2-noxpm-perl/1:2.46-2. Ignoring request to alter fixed versions of bug #713263 to the same values previously set > forcemerge 709047 713263 Bug #709047 [libgd-gd2-noxpm-perl] libgd-gd2-noxpm-perl: fails tests with current libgd2 Bug #713263 [libgd-gd2-noxpm-perl] libgd-gd2-noxpm-perl: FTBFS: tests failed Set Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=85789'. 706828 was blocked by: 709040 711836 711822 709047 709050 711789 709048 701335 711787 710768 707502 706828 was not blocking any bugs. Added blocking bug(s) of 706828: 713263 712615 was blocked by: 708839 707406 708596 709047 709668 708841 709048 708572 705364 708025 676274 707502 712615 was not blocking any bugs. Added blocking bug(s) of 712615: 713263 Marked as found in versions libgd-gd2-noxpm-perl/1:2.46-2. Added tag(s) pending and patch. Merged 709047 713263 > thanks Stopping processing here. Please contact me if you need assistance. -- 706828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706828 709047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709047 712615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712615 713263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713263 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.137193543831214.transcr...@bugs.debian.org
Re: Current and upcoming toolchain changes for jessie
On Thu, Jun 13, 2013 at 02:51:43PM +0200, Matthias Klose wrote: > GCC 4.8 is now the default on all x86 architectures, and on all ARM > architectures (the latter confirmed by the Debian ARM porters). GCC 4.8 seems fine on s390x, it can build a running Linux kernel. On s390 something weird happened and I have to investigate what I broke. Bastian -- The face of war has never changed. Surely it is more logical to heal than to kill. -- Surak of Vulcan, "The Savage Curtain", stardate 5906.5 -- 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/20130622214838.ga3...@mail.waldi.eu.org
Processed: Re: Bug#713660: g3dviewer: FTBFS: gcc: error: unrecognized command line option '-V'
Processing commands for cont...@bugs.debian.org: > reassign 713660 libgtkglext1-dev 1.2.0-3 Bug #713660 [src:g3dviewer] g3dviewer: FTBFS: gcc: error: unrecognized command line option '-V' Bug reassigned from package 'src:g3dviewer' to 'libgtkglext1-dev'. No longer marked as found in versions g3dviewer/0.2.99.5~svn130-2. Ignoring request to alter fixed versions of bug #713660 to the same values previously set Bug #713660 [libgtkglext1-dev] g3dviewer: FTBFS: gcc: error: unrecognized command line option '-V' Marked as found in versions gtkglext/1.2.0-3. > forcemerge 711822 713660 Bug #711822 [libgtkglext1-dev] pcb: FTBFS (gtk/gtkgl.h: No such file or directory) Bug #713660 [libgtkglext1-dev] g3dviewer: FTBFS: gcc: error: unrecognized command line option '-V' 713453 was blocked by: 709554 710792 713258 711822 713453 was not blocking any bugs. Added blocking bug(s) of 713453: 713660 706828 was blocked by: 709040 711836 713263 711822 709047 709050 711789 709048 711787 701335 710768 707502 706828 was not blocking any bugs. Added blocking bug(s) of 706828: 713660 Added indication that 713660 affects pcb,g3dviewer Merged 711822 713660 > thanks Stopping processing here. Please contact me if you need assistance. -- 706828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706828 711822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711822 713453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713453 713660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713660 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.137197050825357.transcr...@bugs.debian.org
