Bug#899623: *prod* Please fix omniorb-dfsg bug #899623?
Hello, On Sat 28 Mar 2020 at 17:28 +0100, Ivo De Decker wrote: > On Sun, Mar 10, 2019 at 01:59:50PM +, Steve McIntyre wrote: >> Hi guys, >> >> I don't know if you've even seen this RC bug. Could you please update >> the maintainer address to point to something that works? > > Any news on this? Are you still interested in maintaining omniorb-dfsg? > > The last maintainer upload was in 2015. Maybe this package should be orphaned > instead? Yes, this package should really be orphaned and possibly even removed now if there are RC bugs and no dependencies for it. I've never been a DD myself only maintained this for a few years together with Thomas, but AFAIK both me or Thomas have stopped maintaining this for years now. IIRC I attempted to orphan this at some point, but it may never have had the upload and svn seems gone by now too... Apologies for not getting the state of the package correctly and the extra work it causes you. Cheers, Floris
Bug#624740: python-omniorb: FTBFS without python2.5
Hi On 1 May 2011 06:37, Scott Kitterman wrote: > Package: python-omniorb > Version: 3.5-1 > Severity: serious > Justification: fails to build from source This has been fixed in r267 of svn.debian.org/svn/pkg-corba/trunk/python-omniorb, so someone needs to upload this now. Usually Thomas Girard does this but I don't know how much time he has (we don't tend to be the fastest team ;-)) so if this is urgent for the transition then maybe someone else could upload this after checking with him? Regards Floris -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#571417: omniorb4: superseded by omniorb-dfsg, should be removed?
On Thu, Feb 25, 2010 at 02:11:35PM +0100, Lucas Nussbaum wrote: > Shouldn't this package be removed from Debian? Looks like it is > superseded by omniorb-dfsg. omniorb-dfsg provides replacement packages for all of the binary packages in omniorb4. It is my understanding from [0] that this makes omniorb4 an orphan and therefore an explicit request is not required. But not having much experience with this I might be wrong, so let me know if I should file an explicit removal request anyway. Regards Floris [0] http://www.debian.org/doc/developers-reference/pkgs.html#removing-pkgs -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#550629: python-pyorbit-omg and python-omniorb-omg: error when trying to install together
On Sun, Oct 11, 2009 at 06:25:24PM +0200, Ralf Treinen wrote: > This is a serious bug as it makes installation fail. Possible > solutions are to have the two packages conflict, to rename the common > file in one of the two packages, or to remove the file from one > package and have this package depend on the other package. File > diversions or a Replace relation are another possibility. Looking at the contents of both packages I think they should conflict. I will add this for the next version of python-omniorb-omg in our svn repo, with a note in the package description explaining this. Regards Floris -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#477438: roundup: Security update 1.2.1-5+etch1 breaks page rendering
Package: roundup Version: 1.2.1-5+etch1 Severity: grave Tags: patch Justification: renders package unusable Hi The recent security update into etch, 1.2.1-5+etch1 breaks the page rendering (templating) of roundup making all the trackers it runs useless. For the benefit of search engines, here the last part of the traceback: [...] File "", line 2, in f File "/usr/lib/python2.4/site-packages/roundup/cgi/templating.py", line 1200, in __str__ return self.plain() File "/usr/lib/python2.4/site-packages/roundup/cgi/templating.py", line 1760, in plain if escape: NameError: global name 'escape' is not defined Comparing the code of templating.py with the previous version makes the fix obvious luckily. In templating.py on line 2698 change: def plain(self): back into: def plain(self, escape=0): Note that I didn't cross-check the CVE (it mentions escaping user input in #472643) so maybe defaulting to the old '0' is not correct and it should be '1' to fix the CVE. I don't know that much about it, all I know is that I want a working system (and since it's internal I trust my users...) Regards Floris -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages roundup depends on: ii python2.4.4-2An interactive high-level object-o ii python-central0.5.12 register and build utility for Pyt roundup recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
