Bug#924685: package ready for upload
Hi Antoine, > At your convenience, please review the changes I've done on the package, > and let me know when I can upload it. Thanks so much for moving this forward! It looks great to me, please upload at your convenience. > PS: and I think you should get rid of the debian/ branches on your end > so there's no ambiguity about where the package is maintained. Ack, I'll sort this out within the Wikimedia folks involved. I think all future uploads will land in Debian first (will add myself to uploaders when the next release comes out). Cheers and have a great weekend, Moritz
Bug#924685: RFP: cumin -- An automation and orchestration framework
Hi, > Heck, you shouldn't even need to build your own debs if we do this > right; this will trickle down to bookworm and, from there, backports, > ubuntu, etc. Agreed, from my perspective an upstream-included debian/ dir is only useful until it gets packaged. From that point onwards fetching a Debian source package for rebuilds is way simpler and downstream distros like Ubuntu sync from Debian anyway instead of an upstream repo. It's also one thing less to maintain/keep in sync. Cheers, Moritz
Bug#924685: RFP: cumin -- An automation and orchestration framework
Hi Antoine, [Adding Riccardo Coccilo, my colleague at Wikimedia and the primary author of Cumin to CC] > which makes me wonder: should we drop the debian branch on github and > gerrit? or should we (say, debian sponsors) pull changes from you and > sync them to salsa? > > how should we play this long term? My proposal would be to discard the debian branch on gerrit/github and make salsa.debian.org the authoritative repository for Cumin debs (and just build backports for apt.wikimedia.org based on the latest version on salsa/unstable). But let's hear from Riccardo on this as well. Cheers, Moritz
Bug#924685: RFP: cumin -- An automation and orchestration framework
Hi, > On 2022-11-18 14:49:28, Moritz Mühlenhoff wrote: > > There is https://apt.wikimedia.org/wikimedia/pool/main/c/cumin/ which > > would be a good starting point. > > ... if you don't mind, I'll start here instead: > > https://github.com/wikimedia/cumin/tree/debian > > i assume those are roughly equivalent? Yeah, the canonical repo is https://gerrit.wikimedia.org/g/operations/software/cumin, but the Github mirror will also do fine. Cheers, Moritz
Bug#924685: RFP: cumin -- An automation and orchestration framework
Antoine wrote: Thanks! I would put that in the Python team, is that okay? Probably next > week too. > Sure, Python team sounds good to me as well. Cheers, Moritz
Bug#924685: RFP: cumin -- An automation and orchestration framework
Hi Antoine, > > NEW was thawed, and I just reinstalled cumin in a virtualenv, and > > thought of this bug. :) Need help with the packaging? I'd be happy to > > just throw it in the python packaging team... > > Ping! did you receive that message? Sorry for the late reply, this got backlogged in my inbox! It would be fantastic if you could bootstrap an initial upload, let's maybe just pick debian/cumin on Salsa? I'd like to lure some of my Debian-savvy, but not yet-DDs/DMs, colleagues into the maintenance as well :-) There is https://apt.wikimedia.org/wikimedia/pool/main/c/cumin/ which would be a good starting point. Cheers. Moritz
Bug#1013132: ITP: BabaSSL -- BabaSSL is a base library for modern cryptography and communication security protocols.
Am Wed, Jun 22, 2022 at 02:28:36PM + schrieb Lance Lin: > Hello Marco, > > > What is the plan? Are there any current or new packages which will > > depend on it? > > Yes, from my understanding it is a "drop in" replacement for OpenSSL. One of > my packages (Workflow) uses it but can also use OpenSSL. Then make it use OpenSSL. If there's anything exciting in BabaSSL, they should submit it for inclusion in OpenSSL. We should aim for fewer crypto libraries in our stable releases, not more. Or if the goal is rather to experiment and expose BabaSSL to the many archs we have in Debian, then keep it in unstable only by filing a bug to block it from testing. Cheers, Moritz
Bug#945271: python-ipcalc: Oprhaning package
On Fri, Nov 22, 2019 at 09:23:59AM +0100, Florian Pelgrim wrote: > Package: python-ipcalc > Version: 1.99.0-3.1 > Severity: important > > Hi community, > > I'm going to orphan this package. > > TL;DR I'm fine to have this package removed from the debian project. > IMHO it's dead and will not come back to life. > > sshfp is the only package having python-ipcalc as a dependency, but this > code has been touched last time 2015. So it is pure python2 and will > probably be also removed soon. sshfp has been removed in the mean time, so I've just filed an RM bug. Cheers, Moritz
Bug#886679: Bug#937400: pycaml: Python2 removal in sid/bullseye
On Tue, Jan 14, 2020 at 11:06:22AM +0100, Stéphane Glondu wrote: > Le 21/11/2019 à 15:26, Stéphane Glondu a écrit : > > pycaml is deprecated in favour of pyml (in NEW). The only reverse > > dependency, coccinelle, is supposed to switch to pyml. Once it's done, > > we can remove pycaml. > > pyml is now in testing. > > Emmanuel Arias (in CC) has shown interest in adopting coccinelle (#886679). > > Emmanuel, what is the status of packaging a new version of coccinelle? A new version of coccinelle has been uploaded, so let's remove pycaml now? Cheers, Moritz
Bug#930137: ITA: nicotine -- graphical client for the SoulSeek peer-to-peer system
On Sat, Mar 21, 2020 at 09:53:10PM +0100, Moritz Mühlenhoff wrote: > On Thu, Jun 20, 2019 at 07:30:12PM -0600, Josue Ortega wrote: > > rename 930137 ITA: nicotine -- graphical client for the SoulSeek > > peer-to-peer > > Hi Josue, > what's the status here? Are you still interested in adopting it and working on > it? Otherwise I'll file an RM bug soon, as nicotine isn't ported to Python 3 > and one of the last dependencies on pygtk2 (which is also going away like Py2) I did that now. nicotine can still be introduced when ported to gtk3/Py3. Cheers, Moritz
Bug#930137: ITA: nicotine -- graphical client for the SoulSeek peer-to-peer system
On Thu, Jun 20, 2019 at 07:30:12PM -0600, Josue Ortega wrote: > rename 930137 ITA: nicotine -- graphical client for the SoulSeek peer-to-peer Hi Josue, what's the status here? Are you still interested in adopting it and working on it? Otherwise I'll file an RM bug soon, as nicotine isn't ported to Python 3 and one of the last dependencies on pygtk2 (which is also going away like Py2) Cheers, Moritz
Bug#719792: RFA: reconf-inetd & DEP9 -- maintainer script for programmatic updates of inetd.conf
On Thu, Aug 15, 2013 at 01:19:08PM +0100, Serafeim Zanikolas wrote: > Package: wnpp > Severity: normal > > I request an adopter for the reconf-inetd package. > > The package description is: > reconf-inetd is a dpkg-trigger script that updates the configuration of the > internet superserver. It is a replacement for update-inetd, as per DEP9. > . > If the above does not mean anything to you, then you most certainly do not > need this package. > > > I do not have the time to be the sole driver of DEP9, and its implementation, > reconf-inetd. reconf-inetd is pretty much complete, it works, and it comes > with dozens of system tests. Remaining work includes: > > - port to python 3 Hi Serafeim, Let's remove reconf-inetd? The lack of a Python 3 port is now a pressing issue given that Python 2 is removed and It's RFAd since 2013, there are no rdeps and inetd itself is going away in favour of systemd socket activation over time. Cheers, Moritz
Bug#944565: O: ldm -- LTSP display manager
On Fri, Dec 27, 2019 at 02:58:58PM -0800, Vagrant Cascadian wrote: > On 2019-11-12, Jonathan Carter wrote: > > On 2019/11/12 00:29, Vagrant Cascadian wrote: > >> Newer versions of LTSP no longer make use of LDM; it is no longer > >> maintained upstream. > > > > In my opinion, ltspfs, ldm-themes and ldm won't be of particular use of > > anyone. Any objections if I file for them to be removed from the archive > > instead? > > Now that it has been several weeks and nobody has stepped up to take > over, sure, go ahead and file removal requests! I'd also add > ltsp-manager/experimental to the list, while you're at it. I just filed an RM bug for ldm (as I had just released the DSA for it and better to get it removed than spending another sid upload on it :) Cheers, Moritz
Bug#874843: [cdcat] Future Qt4 removal from Buster
On Mon, Aug 26, 2019 at 09:30:48AM +0200, Eduard Bloch wrote: > reassign 874843 wnpp > retitle 874843 RFA: cdcat - maintain disk media contents catalog > thanks > > Hallo Moritz, > * Moritz Mühlenhoff [Thu, Aug 22 2019, 11:16:12PM]: > > On Sat, Sep 09, 2017 at 09:03:03PM +0200, Lisandro Damián Nicanor Pérez > > Meyer wrote: > > > Source: cdcat > > > > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > > > as [announced] in: > > > > > > [announced] > > > <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> > > > > > > Therefore, please take the time and: > > > - contact your upstream (if existing) and ask about the state of a Qt5 > > > port of your application > > > - if there are no activities regarding porting, investigate whether there > > > are > > > suitable alternatives for your users > > > - if there is a Qt5 port that is not yet packaged, consider packaging it > > > - if both the Qt4 and the Qt5 versions already coexist in the Debian > > > archives, consider removing the Qt4 version > > > > Eduard, > > cdcat is dead upstream, are you planning to port it to Qt5 yourself or > > should > > it be removed from the archive? > > IMHO, unless some wants to contribute here, it can go for good. > > TBH it was not just porting to Qt5 but also architectural issues in later > versions which I refused to package the way they were designed > (depending on build-time config and weird 3rd party libs). And I don't > have time nor much interest to continue here. > > Thanks for pushing, I am making this request RFA for now and it can > become RoM by the time you are RoMing qt4. We're now wrapping up the remaining rev deps of Qt4 and noone adopted it since then so I just filed a removal bug. Cheers, Moritz
Bug#914577: fixed in dropwatch 1.5.1-1
On Tue, Nov 12, 2019 at 11:02:13AM +, Dmitry Smirnov wrote: > Maintainer: Dmitry Smirnov > Changed-By: Dmitry Smirnov > Description: > dropwatch - tool for detecting and diagnosing dropped network packets > Closes: 914577 > Changes: > dropwatch (1.5.1-1) unstable; urgency=medium > . >* Initial release (Closes: #914577). Why did you take over that ITP without even syncing up with the person (CCed) who indicated to be working on it in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914577#10 ? https://salsa.debian.org/akosiaris-guest/dropwatch had a package waiting for sponsorship/upload. Cheers, Moritz
Bug#566364: ITA: doc-central
On Thu, Apr 19, 2018 at 04:19:24AM +, Trout, Diane E. wrote: > retitle 566364 ITA: doc-central -- web-based documentation browser > owner 566364 ! > thanks > > I'd like to go ahead and adopt doc-central, I do use it occasionally > and it really could stand to be updated to late 2010 coding styles. Hi, are you still planning to adopt doc-central? Otherwise I'd file a removal bug next. Cheers, Moritz
Bug#923034: FreeRADIUS status
On Sat, Feb 23, 2019 at 02:25:49PM -0500, Alan DeKok wrote: > I'll note that Debian also packages "livingston-radius", which hasn't had > any source changes in 20 years. There's no mailing list, no support, and it > doesn't implement any of the modern RADIUS standards. > > Including that package does a disservice to people who install it, and then > realize it's next to useless. Thanks for the pointer, I've just requested livingston-radius's removal from the archive. Cheers, Moritz
Bug#924659: ITP: fossology -- FOSSology is an open source license compliance software system and toolkit.
On Fri, Mar 15, 2019 at 08:27:57PM +0530, Gaurav Mishra wrote: > Package: wnpp > Severity: wishlist > Owner: Gaurav Mishra > > Package name : fossology > Version : 3.4.0 > Upstream Author : Michael Jaeger > URL : https://www.fossology.org/ > License : GPL-2.0-only, LGPL-2.1-only > Programming Lang: C, C++, PHP > Description : FOSSology is an open source license compliance software > system and toolkit. > > FOSSology is an open source license compliance software system and > toolkit. As a toolkit you can run license, copyright and export control > scans from the command line. As a system, a database and web ui are > provided to give you a compliance workflow. License, copyright and export > scanners are tools used in the workflow. > > - Why is this package useful/relevant? >- FOSSology is a famous tool used for open source license compliance. > We have a large database of users which can be benifited by > publishing this as a Debian package. > - Do you use it? >- You can check https://www.fossology.org/ to get a list of compaines > and organizations using FOSSology. > - How do you plan to maintain it? >- FOSSology is currently maintained at > https://github.com/fossology/fossology. I have created a mirror for > the same at https://salsa.debian.org/fossology-team/fossology. > - Are you looking for co-maintainers or a sponsor? >- We are looking for a sponsor to help us publish FOSSology as a > Debian package. Cool! fossology already used to be in Debian until 2012, BTW: https://packages.qa.debian.org/f/fossology.html Cheers, Moritz
Bug#917557: O: reportbug-ng -- Easy to use alternative to Debian's classic reportbug
On Fri, Dec 28, 2018 at 05:47:18PM +0100, Bastian Venthur wrote: > Package: wnpp > Severity: normal > > I intend to orphan the reportbug-ng package. I've been asking for help > maintaining it years ago without response, so I'm now orphaning it. The > current > popcon value is around 300, so it may be save to just get rid of it. Right now close to the freeze is probably the best time to remove it, otherwise it ends up in a stable release mostly unsupported. Thanks for maintaining it over the years! Cheers, Moritz
Bug#891510: O: h323plus
On Mon, Feb 26, 2018 at 12:01:35PM +0100, Bernhard Schmidt wrote: > Package: wnpp > Severity: normal > > Hi, > > on behalf of the Debian VoIP team I intent to orphan the package > h323plus. > > It is a reverse dependency of > > - gnugk (orphaned in #891509) > - openam (RM requested in #891508) > > The version currently in Debian has been released 6 years ago. Upstream > still appears to be active. > > If there are no takers I intend to RM it from the archive end of March > 2018, together with gnugk. Given noone stepped forward and both gnugk and h323plus are currently RC-buggy due to a lack of compatibility with OpenSSL 1.1, let's proceed with removal of them? Cheers, Moritz
Bug#832420: QtWebEngine ready for upload
On Mon, Oct 31, 2016 at 12:27:13PM +0100, Sandro Knauß wrote: > Hey, > > I don't know if you heard about QtWebEngine - it is a Web browser engine for > Qt applications. And is using a patched chromium (49.0.2623.111)( inside src/ > 3rdparty/chromium) as webengine. Qt itself depecated QWebKit and pushing > everyone to use QWebEngine instead. > Unfortunately we didn't found a way to share parts with the chromium package : > ( But this means, that security vulnerable that hit chromium may also affect > QtWebEngine and the other way round. > > For post Stretch we hopefully can find a solution to get rid of this copy... Hi, I don't think we're realistically be able to cover that with security support (and QT upstream won't be able either): chromium is a highly volatile target and the only way we're able to support it is by following their upstream releases, which makes aggressive changes over time. So QWebEngine in stretch will be as unsupported as as in QWebkit was in jessie: https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.en.html#browser-security Cheers, Moritz
Bug#835086: RFP: nextcloud -- self-hosted cloud services
On Mon, Aug 22, 2016 at 12:02:59PM +0200, Xavier Bestel wrote: > Package: wnpp > Severity: wishlist > > * Package name: nextcloud > Version : 9 > Upstream Author : Frank Karlitschek > * URL : https://www.nextcloud.com/ > * License : AGPL > Programming Lang: PHP > Description : self-hosted cloud services > > Nextcloud gives you a private, secure way to share, work with others and > access your own data using an easy to use interface. Be it music, calendar > appointments, bookmarks, email or your documents, Nextcloud keeps your data > safe. > Nextcloud gives organizations control over their data. Manage access to data > and communication across devices and platforms, on-premise, on existing > storage or with cloud storage. Nextcloud integrates in your infrastructure, > offering the extensibility and features you need. > > Given that Nextcloud is an Owncloud fork, with the same people behind it, and > that Owncloud upstream has always had a difficult relationship with distro > maintainers, there may be problems for packaging that correctly. > But Nextcloud is still a highly relevant package for Debian. Nack. It's not an important package if we can't support it properly. Let's not repeat the owncloud disaster. Cheers, Moritz
Bug#777694: ITA: icu -- Development utilities for International Components for Unicode
On Mon, Feb 16, 2015 at 12:12:02AM +0100, László Böszörményi (GCS) wrote: > Hi all, > > On Thu, Feb 12, 2015 at 4:50 PM, wrote: > > It would be great if you (or any co-maintainer) would initially > > take care of the open icu security issues in jessie/sid (with > > a minimal upload to sid + unblock request to the release team): > > > > https://security-tracker.debian.org/tracker/CVE-2014-9654 > > https://security-tracker.debian.org/tracker/CVE-2014-7940 > > https://security-tracker.debian.org/tracker/CVE-2014-7926 > > https://security-tracker.debian.org/tracker/CVE-2014-7923 > > https://security-tracker.debian.org/tracker/CVE-2014-6585 > I'm ready with the first iteration[1]. I've backported all security > fixes. Anyone would like to, please test it. > If someone has exploits, I'm looking for reports how those work on > this Debian package version. I noticed that Mike has been working on a NMU as well, adding him to CC. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150216182933.GA2437@pisco.westfalen.local
Bug#729203: Packaging for FFmpeg avoiding conflicts with libav
On Tue, Feb 25, 2014 at 11:30:25PM +0100, Andreas Cadhalpun wrote: > But then the security team represented by Moritz stated that they > would not support both FFmpeg and libav, so they are the only ones > affected negatively by FFmpeg in stable. Thus I think it doesn't > make much sense to discuss with anyone but the security team. > > Ideally the security team should now evaluate which of the two are > better from a security point of view and based on this decide, which > one they would prefer to see in jessie. > But if they don't, someone else will have to make this decision. Personally I've fine with either libav or ffmpeg. This decision should be made by the Debian multimedia maintainers, since they're affected the most. Anyway, as said before I EOD for me, please stop CCing me on everthing. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140226155439.GG4558@pisco.westfalen.local
Bug#729203: Packaging for FFmpeg avoiding conflicts with libav
On Wed, Feb 26, 2014 at 02:30:47AM +0100, Michael Niedermayer wrote: > > Yes, it's the latter: I didn't badmouth ffmpeg in any way: it was said that > > libav > > fixed less Google fuzzer samples than libav; for which I added my > > observation that when > > I looked at several CVE assignments for ffmpeg fixes the affected code > > didn't exist in libav releases and that explains the difference in numbers. > > That doesn't mean that ffmpeg is worse than libav, it simply means that the > > code has diverged and different code is affected. > > I belive maybe some things are a bit mixed up here > The "less fixes in libav" stuff was AFAIK a comparission between the > libav and ffmpeg git master branches I'm referring to issues listed on ffmpeg.org/security for which I checked the applicability to libav as in Debian. One thing I remember was the g2meet codec which wasn't in any libav branch in Debian. Anyway, I don't have time to discuss this in depth. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140226154909.GF4558@pisco.westfalen.local
Bug#729203: Packaging for FFmpeg avoiding conflicts with libav
On Sun, Feb 23, 2014 at 11:36:36PM +0100, Andreas Cadhalpun wrote: > Hi Moritz, > > On 23.02.2014 22:56, Moritz Mühlenhoff wrote: > >I don't have the time nor the interest to discuss this at length, so > >EOD from my side. > > since you started this discussion by effectively preventing FFmpeg > from being uploaded, I take it that you ending this discussion now > means FFmpeg can be uploaded and you prefer to "be working with the > release team to sort this out for jessie", after FFmpeg has reached > testing. No, it means I don't have the time, nor nerve to discuss this. We're after all busy to keep Debian secure and sick of maintainers who only focus on their pet package and neglegt the overall maintainability of the Debian archive. The security team made it abundantly clear that we will only support either solution. If you go ahead with the ITP we'll file an RC bug against ffmpeg to prevent it's transition to testing. You can then sort out how/whether ffmpeg should _replace_ libav, but both are not an option. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140225165702.GA2960@pisco.westfalen.local
Bug#729203: Packaging for FFmpeg avoiding conflicts with libav
On Sun, Feb 23, 2014 at 12:48:34PM +0200, Adrian Bunk wrote: > On Sun, Feb 23, 2014 at 10:53:18AM +0100, Moritz Mühlenhoff wrote: > > On Sat, Feb 22, 2014 at 08:18:20PM +0100, Andreas Cadhalpun wrote: > >... > > > But should they decide that it will not be possible to support both > > > packages for security updates, your argumentation would clearly > > > favor ffmpeg over libav, probably leading to the removal of libav > > > from the archive. > > > > I don't think that's the case. We've looked into many security issues > > in ffmpeg which didn't affect libav, either because experimental > > code wasn't merged yet or because code was rewritten in libav and not > > affected. > > A significant factor is that libav provides a subset of FFmpeg, > and breaks existing APIs frequently. I don't have the time nor the interest to discuss this at length, so EOD from my side. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140223215636.GA3103@pisco.westfalen.local
Bug#729203: Packaging for FFmpeg avoiding conflicts with libav
On Sat, Feb 22, 2014 at 08:18:20PM +0100, Andreas Cadhalpun wrote: > >>Adrian, do you agree that this is sane? > >> > >>If the security team is not willing to support both, they can ask the TC > >>to decide which one to use, but this does not prevent an upload of FFmpeg. > > > >I don't see why security would complain: as things stand there are > >hundreds of security issues that have been fixed in ffmpeg (see the > >Google audit) which have not been fixed in libav... It seems to me > >ffmpeg is only more secure than libav at this point... > > Previously, Moritz Mühlenhoff from the security team voiced his > concerns about having to apply security fixes for both [1]: > "But we still try to minimise such cases as much as possible. And for > libav/ffmpeg this simply isn't managable at all due to the huge stream > of security issues trickling in. We need definitely need to pick one > solution only." > > I do not share these concerns, as there are e.g. mysql and mariadb > happily coexisting They are not "happily coexisting", we'll be working with the release team to sort this out for jessie. >, but then again, I'm not on the security team. Exactly. It makes it really easy to not share concerns if you're not affected by the work imposed from the decision. > But should they decide that it will not be possible to support both > packages for security updates, your argumentation would clearly > favor ffmpeg over libav, probably leading to the removal of libav > from the archive. I don't think that's the case. We've looked into many security issues in ffmpeg which didn't affect libav, either because experimental code wasn't merged yet or because code was rewritten in libav and not affected. Also ffmpeg hasn't have long term branches which is a major benefit of libav. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140223095318.GA3141@pisco.westfalen.local
Bug#734880: ITP: percona-xtradb-cluster-5.5 -- Synchronously replicated, highly available MySQL
On Mon, Jan 13, 2014 at 04:18:04PM +, James Page wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi Moritz > > On 13/01/14 16:06, Moritz Mühlenhoff wrote: > >> Percona XtraDB Cluster provides synchronous replication, > >> supports > >>> multi-master replication, parallel applying on slaves, > >>> automatic node provisioning with primary focus on data > >>> consistency. > > Is this another copy of the mysql code base? > > > > If so, that's not feasible! > > Percona XtraDB Cluster (PXC) provides a highly-available MySQL > solution which is based upon the MySQL codebase, but has a quite > distinctly different set of features - specifically synchronous > replication provided by Galera. > > This impacts on the standard features of MySQL - for example, query > cache configuration which is a popular performance optimization is not > available - so its not feasible to have a single mysql-* package that > provides both feature sets. > > Percona closely track the upstream MySQL codebase and ship > security/point releases fairly promptly after Oracle releases them. So we'll need to ship security updates for Percona six times a year, which totally sucks as database are notoriously ugly to test. Are you reliably commiting to prepare tested security updates for oldstable and stable througout the entire life cycle of Jessie? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140116214435.GA5580@pisco.westfalen.local
Bug#734892: ITP: percona-xtradb-cluster-galera-2.x -- Synchronous multi-master replication plugin for transactional applications
On Fri, Jan 10, 2014 at 04:22:46PM +, James Page wrote: > Package: wnpp > Severity: wishlist > Owner: James Page > > * Package name: percona-xtradb-cluster-galera-2.x > Version : 2.x branch > * URL : http://launchpad.net/galera > * License : GPL-3 > Programming Lang: C, C++ > Description : Synchronous multi-master replication plugin for > transactional applications > > Galera implements wsrep pluggable interface, as defined in project: > https://launchpad.net/wsrep and can provide several replication modes > and topologies, including the ultimate Synchronous Multi-Master replication. > > This package contains the version of galera that will be aligned to > the Percona XtraDB Cluster 5.5 package. Is this another copy of the mysql code base? If so, that's not feasible! It's already bad enough that mariadb was uploaded in addition to mysql. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140113160634.GA5218@pisco.westfalen.local
Bug#734880: ITP: percona-xtradb-cluster-5.5 -- Synchronously replicated, highly available MySQL
On Fri, Jan 10, 2014 at 03:49:06PM +, James Page wrote: > Package: wnpp > Severity: wishlist > Owner: James Page > > * Package name: percona-xtradb-cluster-5.5 > Version : 5.5.34-25.9 > * URL : http://launchpad.net/percona-xtradb-cluster > * License : GPL-2 + others > Programming Lang: C, C++ > Description : Synchronously replicated, highly available MySQL > > Percona XtraDB Cluster is based on the Percona Server database > server and provides a High Availability solution. > > Percona XtraDB Cluster provides synchronous replication, supports > multi-master replication, parallel applying on slaves, automatic > node provisioning with primary focus on data consistency. Is this another copy of the mysql code base? If so, that's not feasible! It's already bad enough that mariadb was uploaded in addition to mysql. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140113160658.GB5218@pisco.westfalen.local
Bug#717854: O: dmake -- make utility used to build OpenOffice.org
retitle 717854 RM: orphaned, obsoleted by current libreoffice reassign 717854 ftp.debian.org thanks On Wed, Oct 23, 2013 at 08:35:05AM +0200, Rene Engelhard wrote: > Hi, > > On Tue, Oct 22, 2013 at 06:13:50PM +0200, Moritz Muehlenhoff wrote: > > On Thu, Jul 25, 2013 at 06:14:02PM +0200, Rene Engelhard wrote: > > > Package: wnpp > > > Severity: normal > > > > > > As the description says. Only used by OpenOffice.org (and then OpenOffice > > > and > > > LibreOffice). > > > > > > With LibreOffice 4.1.0 (just uploaded) the nw buildsystem named "gbuild" > > > (which > > > was there before in (bigger) parts) is complete and thus it only > > > uses GNU make now -> noneed for dmake -> no interest at all anymore. > > > > > > I guess if noone wants totake it it should be removed... > > > > Three months have passed, shall we go ahead with the removal? > > I am obviously biased, but imho we can do, yes. Reassigning to ftp.debian.org for removal. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131023171211.GA30881@pisco.westfalen.local
Bug#720876: ITP: doxia-1.0 -- 1.0 alpha version of Doxia from codehaus
On Sun, Aug 25, 2013 at 11:22:09PM +0200, Steffen Moeller wrote: > Package: wnpp > Severity: wishlist > Owner: Steffen Moeller > > * Package name: doxia-1.0 > Version : 1.0~alpha-6 > * URL : http://svn.apache.org/viewvc/maven/doxia/doxia/tags/ > Programming Lang: Java > Description : 1.0 alpha version of Doxia from codehaus > > Doxia from Codehaus moved to Apache about six years ago. I happen to have > run into a reverse dependency that needs classes from the org.codehaus path, > still. Then you need to fix the code in question to use the current version and not introduce a six year old piece of unmaintained code! We already have way too many outdated Java classes maintained by pkg-java, which we needed for an initial upload and which were more or less abandoned later on. Chers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130826140052.GA5465@pisco.westfalen.local
Bug#666490: O: svgalib -- console SVGA display libraries
On Mon, May 27, 2013 at 08:29:57PM +0200, Moritz Mühlenhoff wrote: > > Apart from mplayer and zgv, all of these rebuild fine without > > libsvga1-dev; they can use X and some can use fb (I can provide > > patches of course and NMU where necessary). mplayer FTBFS anyway > > because of changes in liblivemedia (#708140). zgv only builds a > > svgalib-based binary; it can in theory be built with SDL instead but > > that fails. All the svgalib-specific packages have low popcon scores. > > I'll file bugs soon and coordinate the removal. About half of the reverse deps have been dealt with. The remaining ones are: * gnuboy -> Bug 72 * lcdproc -> Bug 711096 * mplayer -> Bug 711578 * synaesthesia -> Bug 711552 * vlc -> Bug 713989 * pearpc -> Bug 714002 * fpc -> Bug 714025 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130624215434.GA30056@pisco.westfalen.local
Bug#666490: O: svgalib -- console SVGA display libraries
On Mon, May 13, 2013 at 07:30:20PM +0200, Stephen Kitt wrote: > Hi, > > On Sun, Apr 01, 2012 at 02:59:24AM +0100, Ben Hutchings wrote: > > Thanks for your work, but isn't it time we quietly got rid of this > > library? Video memory and mode setting should be managed by the kernel, > > not by applications. It's bad enough that we had the X server doing > > this for years (and still do on some hardware). I agree. > I've looked into this; svgalib's reverse dependencies are: > * bochs (bochs-svga) > * gnuboy (gnuboy-svga) > * lcdproc (no svgalib-specific package) > * links2 (no svgalib-specific package) > * mplayer (no svgalib-specific package) > * qcam (no svgalib-specific package) > * spectemu (spectemu-svga) > * synaesthesia (no svgalib-specific package) > * thrust (no svgalib-specific package) > * tmview (dvisvga) > * zgv (no svgalib-specific package) > > Apart from mplayer and zgv, all of these rebuild fine without > libsvga1-dev; they can use X and some can use fb (I can provide > patches of course and NMU where necessary). mplayer FTBFS anyway > because of changes in liblivemedia (#708140). zgv only builds a > svgalib-based binary; it can in theory be built with SDL instead but > that fails. All the svgalib-specific packages have low popcon scores. I'll file bugs soon and coordinate the removal. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130527182957.GA6134@pisco.westfalen.local
Bug#478543: New game for ScummVM: Lure of the Temptress
On Fri, Feb 08, 2013 at 07:50:18PM +0100, Markus Koschany wrote: > Hello Moritz, hello David > > > I have packaged "Lure of the Temptress" for Debian. [1] The game is very > similar to your packages Beneath a Steel Sky and Flight of the Amazon > Queen which have been available for a long time in Debian Main. I'm > writing to you because i believe you can comment on an non-technical > issue with the game which also affects your packages. Nice, I even packaged that some time ago, but apparently I never uploaded it and now I can't find the src package. I'll sponsor the upload over the weekend! What about packaging dreamweb as a next target? :-) Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130208211648.GB5141@pisco.westfalen.local
Bug#614131: O: doc-linux -- Linux HOWTOs und FAQs
On Sun, Apr 08, 2012 at 06:15:09PM +0200, Moritz Mühlenhoff wrote: > On Sat, Feb 19, 2011 at 11:08:09PM +0100, Frank Lichtenheld wrote: > > Package: wnpp > > Severity: normal > > > > None of the maintainers seem to be interested in this > > package anymore (including me). > > > > There is an Alioth project pkg-doc-linux which can be > > used. > > > > The problem with this package is that it really needs > > to be completely redone. It should include the actual > > source for the documents and build the formats from > > this. Last time I checked the means to do so were not > > readily available from upstream, but this must have > > been over two years ago, so a lot might have changed. > > > > If noone takes over this package, it should probably > > be removed sooner rather than later. > > There's no visible outcome of the ITA since nearly a year > (CCed for possible comments). > > Should we go ahead with the removal for Wheezy? The addresss peter.littm...@kpl-consulting.de bounces, so I'm going ahead with filing a removal bug. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120408173504.GA4847@pisco.westfalen.local
Bug#614131: O: doc-linux -- Linux HOWTOs und FAQs
On Sat, Feb 19, 2011 at 11:08:09PM +0100, Frank Lichtenheld wrote: > Package: wnpp > Severity: normal > > None of the maintainers seem to be interested in this > package anymore (including me). > > There is an Alioth project pkg-doc-linux which can be > used. > > The problem with this package is that it really needs > to be completely redone. It should include the actual > source for the documents and build the formats from > this. Last time I checked the means to do so were not > readily available from upstream, but this must have > been over two years ago, so a lot might have changed. > > If noone takes over this package, it should probably > be removed sooner rather than later. There's no visible outcome of the ITA since nearly a year (CCed for possible comments). Should we go ahead with the removal for Wheezy? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120408161509.GA29169@pisco.westfalen.local
Bug#635516: Packaging of dvdstyler
On Sat, Feb 18, 2012 at 10:34:17AM +0100, Fabrice Coutadeur wrote: > Would you mind if I assign this bug to myself and work on it? Please go ahead. I started to work on it during DebConf, but more important issues came up. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120219192327.GC9443@pisco.westfalen.local
Bug#623831: RFA: textpattern -- flexible and easy-to-use content management system
On Wed, Jan 11, 2012 at 08:43:59PM +0100, Vincent Bernat wrote: > OoO Lors de la soirée naissante du mercredi 11 janvier 2012, vers 18:42, > Moritz Muehlenhoff disait : > > >> The popcon is very low (18) and therefore I will request for its > >> removal in a few months if I get no adopter. > > > Eight months have passed and the popcon is even lower. Shall we go > > ahead with the removal? > > Yes, please. Should I file a RM or retitle this bug? Just reassign to ftp.debian.org Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120112164442.GA3679@pisco.westfalen.local
Bug#540362: O: xfs -- X font server
On Tue, Jul 19, 2011 at 03:06:57AM -0700, Vagrant Cascadian wrote: > On Mon, Jul 18, 2011 at 10:22:05PM +0200, Moritz Muehlenhoff wrote: > > On Fri, Aug 07, 2009 at 03:58:50PM +0200, Julien Cristau wrote: > > > The X Strike Force would like to get rid of xfs; it's not needed in most > > > (all?) use cases, since most X clients now use Xft and/or pango to > > > render text, not core X fonts (even emacs, these days! :)) > > > > > > So xfs wants to either get removed or get a new maintainer. Maybe LTSP > > > people, if they still use this? > > > > Adding LTSP maintainers to CC; is xfs (the font server, not the > > filesystem) still in use in LTSP? > > LTSP works fine without XFS. > > I think debian-edu may still be using it, as it's recommended in > education-thin-client-server. no idea if it's actually used. Debian Edu people, can you comment on this? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110730081711.GA6711@pisco.westfalen.local
Bug#635516: ITP: dvdstyler -- DVD authoring and burning tool
On Tue, Jul 26, 2011 at 04:08:25PM +0200, Dominique Dumont wrote: > On Tuesday 26 July 2011 16:02:42 Moritz Muehlenhoff wrote: > > Package: wnpp > > Severity: wishlist > > Owner: Moritz Muehlenhoff > > Note that dvdstyler is provided by debian-multimedia (officially outside > Debian) I'm aware of that. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110726152051.GA3228@pisco.westfalen.local
Bug#565466: ITA : fdutils -- Linux floppy utilities
On Mon, May 03, 2010 at 11:25:38PM +0200, Matteo Cypriani wrote: > retitle 565466 ITA: fdutils -- Linux floppy utilities > owner 565466 ! This was nine months ago. What's the status? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110217223524.GA3522@pisco.westfalen.local
Bug#521932: ITA: songwrite -- guitar tablature editor and player
On Sun, Jul 04, 2010 at 09:23:27PM -0600, Jorge Dardón wrote: > retitle 521932 ITA: songwrite -- guitar tablature editor and player > owner 521932 ! > thanks > > Hello, I will adopt this package More than half a year has passed, what's the status? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110217223232.GA3134@pisco.westfalen.local
Bug#572656: your mail
On Wed, Mar 10, 2010 at 11:47:14AM -0500, Jonathan Niehof wrote: > retitle 572656 ITA: pam-shield -- locks out remote attackers trying > password guessing > owner 572656 ! > thanks This was nearly a year ago. What's the status? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110217223823.GA3930@pisco.westfalen.local
Bug#565754: your mail
On Tue, Mar 30, 2010 at 12:03:06PM -0700, Ryan Niebur wrote: > retitle 565754 ITA: python-contract -- Programming by contract for python > owner 565754 ! > thanks > > I'll take this as it's a dependency of tritium. What's the status? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110216230150.GA4760@pisco.westfalen.local