Processed: Re: Bug#678086: ftp.debian.org: Please remove wherpygo and python-lua from testing
Processing commands for cont...@bugs.debian.org: > reassign 678086 release.debian.org Bug #678086 [ftp.debian.org] ftp.debian.org: Please remove wherpygo and python-lua from testing Bug reassigned from package 'ftp.debian.org' to 'release.debian.org'. Ignoring request to alter found versions of bug #678086 to the same values previously set Ignoring request to alter fixed versions of bug #678086 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 678086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678086 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.134008710524665.transcr...@bugs.debian.org
Re: Bug#661991: should libtrash be removed?
Hello, libtrash is indeed not maintained anymore AFAIK. Please file the appropriate RoM / RoQA if you have the time to do so. Otherwise, I'll do it myself. Thank you for taking the time to review this bug. El 16/06/12 21:42, Willi Mann escribió: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! Your package libtrash has an RC bug since the beginning of march. The bug can easily be reproduced on amd64: It does not save files from being deleted, but it causes a segfault in in vim and other binaries. But even on i386, the package does not appear to work as explained in the documentation - I also could not get it to rescue any file I deleted with rm. It only created SYSTEM_ROOT within ~/Trash. I tried to debug the Segfault on amd64, but I could not gain any further insight as the breakpoints I set were ignored, and the backtrace I got with valgrind did not fit what I saw in the source code. I'm wondering whether the package should be removed, as the latest upstream version is 3.2, which was released in 2008, so it seems pretty much unmaintained. The latest upload also dates back to 2008. Also, the package does not have any reverse dependencies. Note that problems I mentioned can also reproduced in stable, so if the package is removed from testing, it should probably also get removed from stable. Greetings from Salzburg BSP Willi -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJP3OF+AAoJEIy+IZx0V22BjgkP/0J72jvH2G0N/u5Vv6qJhIHK apozNd6QAoQvUESqoLdUKHH7HzkKcD278CmS16h1MWuhSE+BvFkgfw9UmaKTUsjA p/H2Um/qOZXj0vAkR8J5QIx/v+9QGa3X/zCYOKN+bdRoprSgSVz95H9QY3VgKsG6 NeZ6vUlXYFqATelhEm3kELonl4dNo+CMckJMyKFQMRDTucxhiPe6KzE61U+H5P08 4ygN30omqJMGWa1DYeBKX5+ZbQylgd0C3iuIKEWoh9itZywbVJ8GVOTsuQ2hp6/F ZIQWjdhp6DUgFrhhPbD7k4OC72mKy23l9ojF3L0YtQFtlrZ+h9YBRedZaz3OUlJ4 cnE28IJkW5589v3fzyf8f4s536GTT5xWUzIJ3deMjfRXcPNszcnqcGs6M3d+WMkC VFPnCKrr0HxN68llbVuZw1QLwp/hWSVrpkrF+e48V/szYnj2SUbXMRBOzyPk0zJ7 ljG8iSbmUUS+h5bqU6F0m80Wd9vBqbrL+U/ckzOAKjJWyTvSKLsLSW0iI7+FHWn9 4jOAKZ6umAEkL8QDkW+5Vz6yC/C3dgnOyulaWkvRVRVmNXCTsMqJ5N4McFyAUmqX JJJZtbXYfEI4vrXMQvg9wfn9bQVrnGzePz1sYbgGd0cUe5uPOxvobYmVbKCYeFYN Cm33BjvqCIEdRs9XBO/u =/Kll -END PGP SIGNATURE- -- 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/4fdfb2de.7010...@adv-solutions.net
Re: Bug#678008: debian-installer: "Space fun" theme considered harmful
Holger, Thanks for your helpful replies. Can we keep this bug report open, as a way of tracking this issue in the period before Wheezy release? While I understand that the debate has passed and it's probably too late to get the radical changes the OP requested, perhaps there's still some wiggle-room. Personally I agree with the OP: space-fun is OK as a demo of the new gnome features, but it's unprofessional looking and not suitable for a general release. I've decided that, unfortunately, I can't win that argument. So I'm taking this opportunity to hope and pray for some kind of "theme" capability in the new Wheezy desktops that allows us old fuddy- duddy types to at least get something more to our liking after the fact of installation. Is there some place we (members of the fuddy- duddy party) can make our voices heard where it will do some good? I've just subscribed to "debian-desktop"; is that the best place? Are there other places as well? Enjoy! Rick On Jun 18, 2012, at 10:43 AM, Holger Levsen wrote: Hi, On Montag, 18. Juni 2012, Cyril Brulebois wrote: My question was rather: - when does the final theme get chosen? - what is the timeline to include the needed changes in the relevant packages? - who is coordinating all that? IOW, whom do we need to prod? yo que se, but this is another pointer: http://lists.debian.org/debian-desktop/2012/01/msg00018.html not sure whats the current status on this. cheers, Holger -- 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/2337fbdc-385b-4c64-8c06-0f9b73de4...@pobox.com
Bug#672820: transition: libcdio
Hi, On Mon, 14 May 2012 01:00:40 +0200, Julien Cristau wrote: > On Mon, May 14, 2012 at 00:30:10 +0200, Nicolas Boullis wrote: > > ¹ I somehow missed the requirement to request transitions as bug reports > > against the release.debian.org pseudo-package, and asked it about 2 > > months ago as a simple e-mail to debian-release@l.d.o, but my message > > remained unanswered. > > > Not really a requirement, but the bts makes tracking stuff easier. In > any case our backlog for transition requests is longer than two months > right now, unfortunately. As you (Julien) discovered, mednafen has a potential FTBFS related to its construction of Built-Using (#677867). Given that the current package binNMU'd correctly on all platforms except hurd-i386, I suppose I should wait until the libcdio transition is over before uploading a fix, shouldn't I? The reason I ask is since other packages are holding up the transition, I wondered if fixing a potential FTBFS warranted an upload despite the transition. I've uploaded a new version of the experimental version of mednafen, with only the fix for #677867, and that built correctly on hurd-i386. Regards, Stephen signature.asc Description: PGP signature
Re: gmsh in Wheezy
On Mon, Jun 18, 2012 at 09:34:15PM +0200, Anton Gladky wrote: > there is a scientific package gmsh [1], which is now hanging in sid, > because bug #617931 is keeping it (the bug against opencascade license). > feel++ is blocked also because of that problem. > > Is it possible to let this package to migrate to wheezy? I do not speak for the release team, but you need to get the licensing issue sorted out before gmsh can migrate to Wheezy (in fact, since the bug report suggests that it is undistributable, you're in danger of it being removed altogether). -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 i have six years of solaris sysadmin experience, from 8->10. i am well qualified to say it is made from bonghits layered on top of bonghits -- 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/20120618201517.gm5...@lupin.home.powdarrmonkey.net
Processed: reassign 678045 to ftp.debian.org, retitle 678045 to RM: jcaptcha -- RoM; Unneeded, FTBFS with Java7
Processing commands for cont...@bugs.debian.org: > reassign 678045 ftp.debian.org Bug #678045 [release.debian.org] RM: jcaptcha/2.0~alpha1-3 Bug reassigned from package 'release.debian.org' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #678045 to the same values previously set Ignoring request to alter fixed versions of bug #678045 to the same values previously set > retitle 678045 RM: jcaptcha -- RoM; Unneeded, FTBFS with Java7 Bug #678045 [ftp.debian.org] RM: jcaptcha/2.0~alpha1-3 Changed Bug title to 'RM: jcaptcha -- RoM; Unneeded, FTBFS with Java7' from 'RM: jcaptcha/2.0~alpha1-3' > thanks Stopping processing here. Please contact me if you need assistance. -- 678045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678045 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.13400496944367.transcr...@bugs.debian.org
Bug#678045: RM: jcaptcha/2.0~alpha1-3
Hello James, James Page (18/06/2012): > jcaptcha was originally packaged to support Jenkins; however Jenkins > upstream no longer requires this package and it uses Sun Java 6 > internal API's so is not compatible with openjdk-7 (and unlikely to be > so). > > Please remove from Debian testing/unstable. please reassign to ftp.debian.org once you have read: http://wiki.debian.org/ftpmaster_Removals Thanks already. Mraw, KiBi. signature.asc Description: Digital signature
Bug#678045: RM: jcaptcha/2.0~alpha1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 jcaptcha was originally packaged to support Jenkins; however Jenkins upstream no longer requires this package and it uses Sun Java 6 internal API's so is not compatible with openjdk-7 (and unlikely to be so). Please remove from Debian testing/unstable. Thanks - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0-5-generic (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP34R7AAoJEL/srsug59jDnQoQALewqkfLQG1+qD4b6qRmqB9d WNtsM8vq7pX1XieVjHy9vMaFNvyn6FtpcdLOtQKQ6iNJfQpuuP3leGDqhF8C0ep+ SDFOSu7y8kqmR3n+KrUfYtSOp7nUa6JLz96ReHB0LLO51YJtYu6FCtkJ4KTZfuz9 vLicP3qXyt7dGMOVOGF+fRr5Zqwuldk4tPcSaD2e+zdUhjFMmpIiY/To1/7y1s1f 8WQGjU1M3sJCesPQdp4EC8C+t3TGTymEKd9HSJl6wo0X8AbcFAqBHcBNzMxpoH+0 mauiI9tyPCynOyhRVfw4zRiGS+f3zQFHJ/Pt+MzZmSuqma9Wp0ySRFFxMvus43nR K8rk04IwVA7EhYWlRLn1J2sHvlT8smJIx46J4IcAoaqlhHATxaui/ZaxEZkqvayh W8SrzRIgkGPSfdVGEexs97dTZL70IITP+Ymi6BM7DWn9hM5bXp4XRZr4lcB03suw taAZG5U2AGS1vHBouDLNuRnT+zghYSA0kiLyZIahv33bwspaqt5Ob+SynExTzxv5 kH6/reFQ/VCqR8GPQ6cUlbB1188OGauNpEajpmF81VGmhcwk/6LzoYovyvv6PY1B zBLsyVZnFaIK0eBZ6t73VM95Fhrwte3KttCxdvg35P/svOx61TLhokr3q67Wgahx iKhglBTvBUEqZKyDjk71 =WN3i -END PGP SIGNATURE- -- 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/20120618194150.22740.29389.reportbug@hendrix.shouse.local
gmsh in Wheezy
Dear release team, there is a scientific package gmsh [1], which is now hanging in sid, because bug #617931 is keeping it (the bug against opencascade license). feel++ is blocked also because of that problem. Is it possible to let this package to migrate to wheezy? Thank you. Anton [1] http://packages.qa.debian.org/g/gmsh.html -- 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/calf6qjmqkqqmb3kwhsi7iwdxo5nm0zzob_40jjxnwn+rofe...@mail.gmail.com
Bug#672820: failed attempt to build xmms2, blocking libcdio transition.
Hi, On 18/06/12 20:01, Rémi Vanicat wrote: > [...] in > both case waf or gcc hang, and the build was killed after some time. I think there is a problem affecting Python threads on kfreebsd-* currently, perhaps a bug in our glibc, and this has been seen sometimes when building other packages that use waf: samba4, guitarix. It seems random, so in some cases they build okay after being given back to the buildds for another attempt. (Looks like xmms2 just built successfully after a giveback). The cause of this may be difficult to track down; it's not easy to reproduce it on demand. Sorry for the inconvenience! Regards, -- Steven Chamberlain ste...@pyro.eu.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/4fdf80bf.9060...@pyro.eu.org
Bug#672820: failed attempt to build xmms2, blocking libcdio transition.
Hello Debian/BSD hackers, I've recently upload an new version of xmms2 to fix an FTBS[1] and help a libcdio transition[2]. But the build failed on both kfreebsd buildd (fano[3] and finzi[4]) at very different stage of compilation, but in both case waf or gcc hang, and the build was killed after some time. Is there anything I should know/do about this problem on the kfreebsd port? Thanks [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676100 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672820 [3] https://buildd.debian.org/status/fetch.php?pkg=xmms2&arch=kfreebsd-amd64&ver=0.8%2Bdfsg-3&stamp=1340024041 [4] https://buildd.debian.org/status/fetch.php?pkg=xmms2&arch=kfreebsd-i386&ver=0.8%2Bdfsg-3&stamp=1340032320 -- Rémi Vanicat -- 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/878vfkbg1x@gmail.com
Bug#667863: marked as done (transition: octave 3.2 -> 3.6)
Your message dated Mon, 18 Jun 2012 20:34:21 +0200 with message-id <20120618183421.gd7...@radis.cristau.org> and subject line Re: Bug#667863: transition: octave 3.2 -> 3.6 has caused the Debian Bug report #667863, regarding transition: octave 3.2 -> 3.6 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.) -- 667863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition The Debian Octave Group (DOG) is preparing the transition from Octave 3.2 to 3.6. There will be an important impact on the Debian ecosystem because we abandoned the versioned naming scheme. Indeed, the Octave package currently in stable/testing is called octave3.2. From now on, it will be called simply octave (which will conflict/replace octave3.2). After the transition is completed, we will ask for the removal of the octave3.2* packages. This will affect a large number of packages in testing. We are coordinating this transition through our wiki page [1]. There are two types of packages involved. First, the Octave-Forge [2] packages that are maintained by the DOG itself. We have already ported all of them and requested removal of the obsolete ones. Second, packages not maintained by the DOG that have reverse dependencies on the octave3.2* packages. The situation of each one of these packages have been analyzed and appropriate bug reports with patches have been filed [3]. We have also filed a RC bug report (Bug#661521) against the octave package currently in unstable (version 3.6.1-4). We will wait until all Octave-Forge packages, at least, are ready for migration into testing before we close that bug report. The expected date when this will happen is April 15, 2012. Best, Rafael Laboissière [1] http://wiki.debian.org/Teams/DebianOctaveGroup#Migration_to_git-buildpackage_and_Octave_3.6 [2] http://octave.sf.net [3] http://wiki.debian.org/Teams/DebianOctaveGroup#Reverse_dependencies_on_octave3.2.2A_packages --- End Message --- --- Begin Message --- On Mon, Jun 18, 2012 at 20:27:42 +0200, Cyril Brulebois wrote: > kibi@franck:~$ dak ls octave3.2 -S -s testing > kibi@franck:~$ > > All done I think? > Indeed. Closing. Cheers, Julien --- End Message ---
Bug#667863: transition: octave 3.2 -> 3.6
Hello folks, Rafael Laboissiere (13/06/2012): > I am not familiar with how ftpmaster works, but according to the Wiki > [1], the octave3.2 package will be removed automatically from testing, > once pfstools_1.8.5-0.1 (5 days from now) and debian-edu_1.700 (3 days > from now) will migrate into testing. Indeed, the situation in testing > right now is as follows: > > $ apt-cache rdepends octave3.2 > octave3.2 > Reverse Depends: > pfstools > octave-pfstools > octave3.2-htmldoc > octave3.2-headers > octave3.2-emacsen > octave3.2-doc > octave3.2-dbg > octave > octave > education-mathematics kibi@franck:~$ dak ls octave3.2 -S -s testing kibi@franck:~$ All done I think? Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#678008: debian-installer: "Space fun" theme considered harmful
Hi, On Montag, 18. Juni 2012, Cyril Brulebois wrote: > My question was rather: > - when does the final theme get chosen? > - what is the timeline to include the needed changes in the relevant >packages? > - who is coordinating all that? > > IOW, whom do we need to prod? yo que se, but this is another pointer: http://lists.debian.org/debian-desktop/2012/01/msg00018.html not sure whats the current status on this. cheers, Holger -- 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/201206181943.29132.hol...@layer-acht.org
Re: Bug#678008: debian-installer: "Space fun" theme considered harmful
(Adding the release team to cc.) Holger Levsen (18/06/2012): > KiBi (18/06/2012): > > How do I follow the status on that topic, be it on the > > syslinux/isolinux, gnome, kde, xfce, etc. side? > > I'm subscribed to debian-desk...@lists.debian.org for that purpose, > that's were some artists discuss designs and desire some cluefull > sponsor/packager to improve theming support for the whole distro. > > I'm also subscribed to desktop-base in the pts... My question was rather: - when does the final theme get chosen? - what is the timeline to include the needed changes in the relevant packages? - who is coordinating all that? IOW, whom do we need to prod? Mraw, KiBi. signature.asc Description: Digital signature
Bug#677620: transition: GNOME 3.4: evolution 3.4
On Fri, Jun 15, 2012 at 02:13:25PM +0200, Michael Biebl wrote: > Involves several soname bumps: > > - libebook-1.2-12 → libebook-1.2-16 > - libecal-1.2-10 → libecal-1.2-13 > - libedata-book-1.2-11 → libedata-book-1.2-13 > - libedataserver-1.2-15 → libedataserver-1.2-16 > - libcamel-1.2-29 → libcamel-1.2-33 > - libedata-cal-1.2-13 → libedata-cal-1.2-15 > - libebackend-1.2-1 → libebackend-1.2-2 > > is_affected = .build-depends > ~/lib(|ecal1.2|edataserver1.2|edataserverui-3.0|ebook1.2|edata-book1.2|edata-cal1.2|ebackend1.2)-dev/ > | .build-depends ~ /evolution-data-server-dev/; > is_good = .depends ~ > /lib(|ebook-1.2-16|ecal-1.2-13|edata-book-1.2-13|edataserver-1.2-16|camel-1.2-33|edata-cal-1.2-15|ebackend-1.2-2)/; > is_bad = .depends ~ > /lib(ebook-1.2-12|ecal-1.2-10|edata-book-1.2-11|edataserver-1.2-15|camel-1.2-29|edata-cal-1.2-13|ebackend-1.2-1)/; Hmm. Either I miss something, or the above is wrong: from e-d-s 3.4.2-2s experimental upload: libcamel-1.2-33 - Evolution MIME message handling library libcamel1.2-dev - Development files for libcamel libebackend-1.2-2 - Utility library for evolution data servers libebackend1.2-dev - Utility library for evolution data servers (development files) libebook-1.2-13 - Client library for evolution address books libebook1.2-dev - Client library for evolution address books (development files) libecal-1.2-11 - Client library for evolution calendars libecal1.2-dev - Client library for evolution calendars (development files) libedata-book-1.2-13 - Backend library for evolution address books libedata-book1.2-dev - Backend library for evolution address books (development files) libedata-cal-1.2-15 - Backend library for evolution calendars libedata-cal1.2-dev - Backend library for evolution calendars (development files) libedataserver-1.2-16 - Utility library for evolution data servers libedataserver1.2-dev - Utility library for evolution data servers (development files) libedataserverui-3.0-1 - GUI utility library for evolution data servers libedataserverui-3.0-dev - GUI utility library for evolution data servers (development files - libebook-1.2-12 → libebook-1.2-13 - libecal-1.2-10 → libecal-1.2-11 sound more right, which makes the tracker need the following: is_affected = .build-depends ~/lib(|ecal1.2|edataserver1.2|edataserverui-3.0|ebook1.2|edata-book1.2|edata-cal1.2|ebackend1.2)-dev/ | .build-depends ~ /evolution-data-server-dev/; is_good = .depends ~ /lib(|ebook-1.2-13|ecal-1.2-11|edata-book-1.2-13|edataserver-1.2-16|camel-1.2-33|edata-cal-1.2-15|ebackend-1.2-2)/; is_bad = .depends ~ /lib(ebook-1.2-12|ecal-1.2-10|edata-book-1.2-11|edataserver-1.2-15|camel-1.2-29|edata-cal-1.2-13|ebackend-1.2-1)/; Regards, Rene -- 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/20120618164154.ge20...@rene-engelhard.de
Bug#677620: transition: GNOME 3.4: evolution 3.4
On Mon, Jun 18, 2012 at 04:30:18PM +0200, Rene Engelhard wrote: > http://cgit.freedesktop.org/libreoffice/core/tree/connectivity/source/drivers/evoab2/EApi.cxx?h=libreoffice-3-5-4 Oh, and evene if it built it obviously won't work ;) Regards, Rene -- 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/20120618143718.gd20...@rene-engelhard.de
Bug#677620: transition: GNOME 3.4: evolution 3.4
Hi, On Fri, Jun 15, 2012 at 02:13:25PM +0200, Michael Biebl wrote: > Involves several soname bumps: > > - libebook-1.2-12 → libebook-1.2-16 [...] > * binNMUs (build tested) [...] > - libreoffice Really? http://cgit.freedesktop.org/libreoffice/core/tree/connectivity/source/drivers/evoab2/EApi.cxx?h=libreoffice-3-5-4 together with http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=blob;f=rules;h=4a018d0a3c0ae82c6255b8e5c3f1a699151eccd4;hb=HEAD#l2892 http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=blob;f=scripts/get_libebook_dep.sh;h=6fefd62073fb08937348bc74547fdba33c08a959;hb=HEAD doesn't make me think it builds (it at least most probably will not create a proper dep) -> source upload needed. Regards, Rene -- 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/20120618143018.gc20...@rene-engelhard.de
Processed: Re: Bug#677620: transition: GNOME 3.4: evolution 3.4
Processing commands for cont...@bugs.debian.org: > tags 677620 + pending Bug #677620 [release.debian.org] transition: GNOME 3.4: evolution 3.4 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 677620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677620 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.134002855919087.transcr...@bugs.debian.org
Bug#677620: transition: GNOME 3.4: evolution 3.4
tags 677620 + pending thanks On 15/06/2012 14:13, Michael Biebl wrote: We want evolution 3.4 for wheezy. This means updating gtkhtml4.0, evolution-data-server, evolution and the reverse dependencies of those packages. Please go ahead with the uploads. Let's try to do this transition quickly :) I've generated the ben trackers: http://release.debian.org/transitions/html/gtkhtml4.0.html http://release.debian.org/transitions/html/evolution3.4.html Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.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/4fdf2dcd.7010...@dogguy.org
Uploading linux (3.2.21-1)
I intend to release Linux 3.2.21 on Tuesday and upload to unstable shortly after. The pending Debian changes should fix the FTBFS on various architectures in 3.2.20-1. Other changes turn CPUs into normal devices which generate hotplug events and can (on x86) trigger module auto-loading. I expect that we will also add support for the Dreamplug ARM platform, but this is not yet committed. There *will* be an ABI bump. Ben. -- Ben Hutchings Time is nature's way of making sure that everything doesn't happen at once. signature.asc Description: This is a digitally signed message part
Processed (with 1 errors): Cloning & closing 677983: [cpl: FTBFS on armel, ia64, kfreebsd-*, s390x, sparc]
Processing commands for cont...@bugs.debian.org:
> retitle 677893 cpl: FTBFS on ia64, kfreebsd-*, s390x
Bug #677893 {Done: Ole Streicher } [src:cpl] cpl: FTBFS on
armel, ia64, kfreebsd-*, s390x, sparc
Changed Bug title to 'cpl: FTBFS on ia64, kfreebsd-*, s390x' from 'cpl: FTBFS
on armel, ia64, kfreebsd-*, s390x, sparc'
> fixed 677983 6.1.1-1
Failed to add fixed on 677983: Unable to read any bugs successfully.
> unblock 671853 by 677967
Bug #671853 [release.debian.org] Transition: cpl
671853 was blocked by: 671675 677893
671853 was blocking: 677967 677968
Removed blocking bug(s) of 671853: 677967
> unblock 671853 by 677968
Bug #671853 [release.debian.org] Transition: cpl
671853 was blocked by: 671675 677893
671853 was blocking: 677967 677968
Removed blocking bug(s) of 671853: 677968
> found 677967 6.1.1-1
Bug #677967 {Done: Ole Streicher } [src:cpl] cpl: FTBS on
armel
Marked as found in versions cpl/6.1.1-1 and reopened.
> reopen 677967
Bug #677967 [src:cpl] cpl: FTBS on armel
Bug 677967 is not marked as done; doing nothing.
> found 677968 6.1.1-1
Bug #677968 {Done: Ole Streicher } [src:cpl] cpl: FTBS on
sparc
Marked as found in versions cpl/6.1.1-1 and reopened.
> reopen 677968
Bug #677968 [src:cpl] cpl: FTBS on sparc
Bug 677968 is not marked as done; doing nothing.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
671853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671853
677893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677893
677967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677967
677968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677968
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.134001197318075.transcr...@bugs.debian.org
Processed: Cloning & closing 677983: [cpl: FTBFS on armel, ia64, kfreebsd-*, s390x, sparc]
Processing commands for cont...@bugs.debian.org:
> clone 677893 -1 -2
Bug #677893 {Done: Ole Streicher } [src:cpl] cpl: FTBFS on
armel, ia64, kfreebsd-*, s390x, sparc
Bug 677893 cloned as bugs 677967-677968
677967 was not blocked by any bugs.
677967 was blocking: 671853
Added blocking bug(s) of 677967: 671853
677968 was not blocked by any bugs.
677968 was blocking: 671853
Added blocking bug(s) of 677968: 671853
> retitle -1 cpl: FTBS on armel
Bug #677967 {Done: Ole Streicher } [src:cpl] cpl: FTBFS on
armel, ia64, kfreebsd-*, s390x, sparc
Changed Bug title to 'cpl: FTBS on armel' from 'cpl: FTBFS on armel, ia64,
kfreebsd-*, s390x, sparc'
> severity -1 normal
Bug #677967 {Done: Ole Streicher } [src:cpl] cpl: FTBS on
armel
Severity set to 'normal' from 'serious'
> retitle -2 cpl: FTBS on sparc
Bug #677968 {Done: Ole Streicher } [src:cpl] cpl: FTBFS on
armel, ia64, kfreebsd-*, s390x, sparc
Changed Bug title to 'cpl: FTBS on sparc' from 'cpl: FTBFS on armel, ia64,
kfreebsd-*, s390x, sparc'
> severity -2 normal
Bug #677968 {Done: Ole Streicher } [src:cpl] cpl: FTBS on
sparc
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
677893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677893
677967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677967
677968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677968
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.134001121414854.transcr...@bugs.debian.org
