Bug#936924: Moving libsvm to Debian Science team

On 2019-12-25 18:08, Chen-Tse Tsai wrote: > Thanks Andreas and Christian for the updates/comments. I agree that I > should have been more verbose in the changelog. I'm tracing all the > commits to learn more about packaging. I was playing with gbp for > updating upstream. I really like how it

Bug#936924: Moving libsvm to Debian Science team

On 2019-12-25 10:59, Andreas Tille wrote: > Kind regards > >Andreas. I've re-read my original message and feel that I was overly harsh. I was irritated about the rushed upgrade as in private communication with Chen-Tse, I highlighted precisely the possible complexity of this upgrade and

Bug#936924: Moving libsvm to Debian Science team

Andreas, what are you doing? On 2019-12-25 07:52, Andreas Tille wrote: > On Tue, Dec 24, 2019 at 10:39:55AM -0500, Chen-Tse Tsai wrote: >> I just submitted a PR for dropping python2 dependencies: >> https://salsa.debian.org/science-team/libsvm/merge_requests/1 >> >> Any comment is appreciated.

Bug#936924: Moving libsvm to Debian Science team

Hi all, Regarding liblinear: I thought I already set the Maintainer to Debian Science Team, I guess I missed it. On 2019-12-21 20:11, Chen-Tse Tsai wrote: > I've created an account on Salsa. > > Do you think we should remove cdbs and use another build system > instead? Please let me know if

Bug#946450: New upstream version 2.5.1

Source: keepassxc Version: 2.4.3+dfsg.1-1 Severity: wishlist I'm being bitten by a bug that was supposedly fixed in 2.5.1 [1], but while I have a workaround for 2.4.3, I'd greatly appreciate an update to the new upstream version :-) [1] https://github.com/keepassxreboot/keepassxc/issues/3985

Bug#945855: RM: pyevolve -- ROM; Python2, inactive upstream

Package: ftp.debian.org Severity: normal Please remove pyevolve from unstable. The popcon is low, and there has been no upstream activity in years. It's still Python 2 only and because of the points raised in the previous sentence, I don't think that the effort of converting to Python 3 would be

Bug#945856: RM: libmpikmeans -- ROM; abandoned, low popcon

Package: ftp.debian.org Severity: normal Please remove libmpikmeans from unstable. There hasn't been upstream activity in 8 years, and its popcon is very low. There's an RC bug because it's still Python 2 only, but without an active upstream, I don't think that the effort of converting to Python

Bug#935921: libpam-cap doesn't work with sudo because PAM_REINITIALIZE_CRED is ignored

On 07.11.19 12:42, Daniel Gröber wrote: > Great, now that this is in sid would it be possible to get the fix > added to the buster version of the package as well? I would really > like not to have to maintain my local patched version ;) I'm afraid the window for the 10.2 release is just about

Bug#944261: ITB: python-seaborn -- Python data visualization library

Package: wnpp Severity: wishlist Owner: Christian Kastner X-Debbugs-CC: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org, debian-scie...@lists.debian.org * Package name: python-seaborn Version : 0.9.0 Upstream Author : Michael Waskom * URL : https

Bug#911509: Update to libcap2.26

Hi Kevin, On Mon, 3 Dec 2018 Kevin Locke wrote: > On Sun, 2018-10-21 at 09:52 +0200, Christian Brauner wrote: > > We recently pushed support for ambient capabilities and namespaces > > filesystem capabilities > > to libcap2 [1]. Together with Andrew Morgan, Serge Hallyn and I have > > released a

Bug#943483: Please release new version of pristine-tar

Source: pristine-tar Version: 1.46 Severity: wishlist Hi, My package libcap2 is currently affected by #892029 resp. #913218 (pristine-xz can't reproduce tarballs created with pixz), both of which have a fix committed a while ago and are pending upload. I would greatly appreciate if that

Bug#942209: buster-pu: package cron/3.0pl1-134

obsolete SELinux API (Closes: #924716) + + -- Christian Kastner Fri, 11 Oct 2019 09:58:52 +0200 + cron (3.0pl1-134) unstable; urgency=medium * Increase maximum crontab length to 10,000 lines. diff -u cron-3.0pl1/user.c cron-3.0pl1/user.c --- cron-3.0pl1/user.c +++ cron-3.0pl1/user.c

Bug#806225: cron: please consider to migrate to '3.0 (quilt)' source format

Hi Sandro, On 26.11.15 00:12, Sandro Tosi wrote: >> Once I've cleaned things up, I'll gladly come back to you for help and >> review! This is a big change, and I'd feel much more comfortable with >> more eyes looking into this. > > absolutely, anytime! thanks! It's been a while (even by Debian

Bug#924716: cron: diff for NMU version 3.0pl1-134.1

Hi Laurent, sorry for the delay. I changed something in my bug subscription mails, and never saw this bug (probably because I'm "only" in Uploaders). On 13.09.19 16:49, Laurent Bigonville wrote: > Control: tags 924716 + pending > > > Dear maintainer, > > I've prepared an NMU for cron

Bug#930971: unblock: cron/3.0pl1-134

pl1/debian/NEWS @@ -1,3 +1,9 @@ +cron (3.0pl1-134) unstable; urgency=medium + + * crontabs are now limited to 10,000 lines, up from the previous 1,000. + + -- Christian Kastner Sun, 23 Jun 2019 19:45:57 +0200 + cron (3.0pl1-133) unstable; urgency=medium * As a reasonable protective measure

Bug#925250: unblock: cron/3.0pl1-133

Hi, brief update: Since the upload, one new bug has been reported for one of the security fixes, which had been cherry-picked for jessie-security. See below. Otherwise, -133 has not triggered any new bug reports so far. On 2019-03-21 20:19:01 +0100 Christian Kastner wrote:> I'd like to requ

Bug#925276: cron: Maximum crontab limit applied needlessly to system crontabs

control: severity -1 important On 22.03.19 12:52, Antti Salmela wrote: > On Fri, Mar 22, 2019 at 11:38:44AM +0100, Christian Kastner wrote: >> I'm wondering as to the practical significance, though. Were you >> affected by this limit (in which case I would increa

Bug#925276: cron: Maximum crontab limit applied needlessly to system crontabs

Hi, On 2019-03-22 09:51, Antti Salmela wrote: > Package: cron > Version: 3.0pl1-127+deb8u2 > Severity: normal > > Dear Maintainer, > > fix for CVE-2019-9705 is also limiting cron.d files > under /etc/cron.d. I think following patch should be applied. Thanks for the suggestion; at first glance,

Bug#925250: unblock: cron/3.0pl1-133

*) malloc(sizeof(user))) == NULL) { errno = ENOMEM; + return; } if ((u->name = strdup(fname)) == NULL) { free(u); errno = ENOMEM; + return; } u->mtime = old_mtime; u->

Bug#925142: hp-plugin generates libsane udev rules lacking LABEL

Package: hplip Version: 3.18.12+dfsg0-2 Severity: minor The utility hp-plugin generated a file S99-2000S1.rules in /etc/udev/rules.d/, which I've attached. This sets up permissions for my HP LaserJet Pro MFP 176n. Note that in line 26, there's a GOTO="libsane_rules_end", but there is no LABEL=

Bug#924796: unblock: keyutils/1.6-6

, as these are + performed by the test upstream-runtime-tests. + + -- Christian Kastner Wed, 06 Mar 2019 17:18:19 +0100 + +keyutils (1.6-5) unstable; urgency=medium + + * d/tests: +- Save all output to $AUTOPKGTEST_ARTIFACTS + * d/tests: +- Run individual tests in AUTOPKGTEST_TMP subdirs, just in case

Bug#924638: cron: scheduled command execution problems

On 16.03.19 11:47, Antonio wrote: >> Note that `man crontab` leads to to crontab(1), not crontab(5). >> Perhaps that was the source of confusion. > > To avoid confusion, on crontab(1) we could add something like: "Note: > some characters, like the percentage, have a special treatment. I'm afraid

Bug#924510: cron runs job at wrong time; ignores values in /etc/crontab; after upgrade to buster

Hi, On 13.03.19 20:16, Tony Walker wrote: > I upgraded to Buster from stretch and noticed that my cron jobs were > running at ~7:38 AM > instead of the time in my /etc/crontab. After some troubleshooting, I > did reinstall by > installing from 9.7 media followed immediately by apt full-upgrade.

Bug#785512: regression: cannot find iso image on usb stick any more

On Thu, 28 May 2015 15:26:05 +0100 Philip Hands wrote:> It looks to me as though we're missing iso-scan and load-iso from the > cdrom target, and that as a result we neither include the loop module, > nor do we attempt to mount the usb stick, nor look for the ISO therein. This is an ancient

Bug#924199: Removing an LVM snapshot logs `dmsetup info` error

On 10.03.19 11:07, Michael Biebl wrote: > I suppose this is caused by > > https://github.com/systemd/systemd/commit/a75211421fc9366068e6d9446e8e567246c72feb > > Could you check if > https://github.com/systemd/systemd/commit/3c37dadf627677eef62fcfc0c0f07cc67c748a9e > helps? Yes, that solved the

Bug#924199: Removing an LVM snapshot logs `dmsetup info` error

Package: udev Version: 241-1 Severity: minor Removing an LVM snapshot logs an error. Steps to reproduce: # lvcreate --snapshot --size 500M --name testsnap $SOMEVOLUME # lvremove --force testsnap # journalctl -n 1 systemd-udevd[21406]: Process '/sbin/dmsetup info -j 254 -m 14 -c

Bug#923156: keyutils autopkgtest shows failure on armhf

On 06.03.19 08:56, Steve Langasek wrote: > On Sat, Mar 02, 2019 at 11:52:05AM +0100, Christian Kastner wrote: > >> Side note: saving away the artifacts in $AUTOPKGTEST_ARTIFACTS >> apparently didn't work on Ubuntu's side; the artifacts tarball only >> contains the usual

Bug#923706: quilt annotate requires ed

On 2019-03-04 08:29:29 Christian Kastner wrote: > # Create the first patch > $ quilt new short.patch && quilt add short.txt > $ sed -i '5d' short.txt && quilt refresh Addendum: if you instead add a line, $ echo "addition" >> short.txt &

Bug#923706: quilt annotate requires ed

Package: quilt Version: 0.65-3 Severity: important Executing `quilt annotate`, at somepoint, apparently requires ed to be installed. Steps to reproduce: # Create a test directory $ mkdir /tmp/quiltbug && cd /tmp/quiltbug # Create a short test file $ for file in /etc/cron.*; do echo

Bug#801328: crontab(5) has incorrect information about bash's $PATH handling

Tag: + confirmed pending Hi Tim, On 2015-10-08 16:36:26 Tim Landscheidt wrote: > |An alternative for setting up the commands path is using the > |fact that many shells will treat the tilde(~) as substitution > |of $HOME, so if you use bash for your tasks you can use

Bug#895024: Error: bad hour; while reading /etc/crontab makes the cron do nothing

Tags: + unreproducible moreinfo Hi Salvo, On 2018-06-04 12:57:37 Salvo Tomaselli wrote: > I had made a mistake while writing crontab, and had reversed hours and > minutes. > > This happened: > Error: bad hour; while reading /etc/crontab > > Hoewver, cron then doesn't run any job at all. In

Bug#893575: crontab.5: Some fixes in the manual

Tags: + pending Hi Bjarni, On 2018-03-20 00:38 Bjarni Ingi Gislason wrote: > Package: cron > Version: 3.0pl1-130 > Severity: minor > Tags: patch Thank you very much for these fixes! I just applied them, and will include them in the next release. Regards, Christian

Bug#923156: keyutils autopkgtest shows failure on armhf

On 02.03.19 06:42, Steve Langasek wrote: > On Sun, Feb 24, 2019 at 05:39:30PM +0100, Christian Kastner wrote: >> The logs don't offer that much, so I was planning to upload a 1.6-5 soon >> that also saves away all the test artifacts for analysis (it still FTBFS >> on alpha

Bug#923156: keyutils autopkgtest shows failure on armhf

Hi Steve, On 24.02.19 16:12, Steve Langasek wrote: > I see that since 1.6-3, keyutils now tries to split its autopkgtests between > those that do require machine isolation, and those that do not. Just for clarification: I messed this up a bit, the net result was that both tests were identical in

Bug#922267: dh_missing reports missing files, though installed

Hi Niels, On 23.02.19 13:14, Niels Thykier wrote: > On Wed, 13 Feb 2019 22:18:18 +0100 Christian Kastner wrote: >> With an override and dh_missing --fail-tmp, I get >> >> dh_missing: usr/bin/mpi_assign exists in debian/tmp but is not installed >> to anywhe

Bug#898119: cron: Removal of sharp character at the end of line in the header

Tags: + confirmed pending On Mon, 7 May 2018 15:58:57 +0200 =?UTF-8?Q?St=C3=A9phane_Blondon?= wrote: > --- cron_3.0pl1-130.diff.orig 2018-05-07 15:50:16.539054242 +0200 > +++ cron_3.0pl1-130.diff 2018-05-07 15:53:13.851529214 +0200 > @@ -2326,7 +2326,7 @@ > +"# \n" > +"# To define the

Bug#922795: dh_compress in compat 12: examples still being compressed

Package: debhelper Version: 12.1 Severity: normal In src:libfann, a subdirectory examples/datasets is provided with datasets for the examples. I used to have a dh_compress -Xexamples but when dropping this after moving to compat 12, these got compressed anyway, so there might be an issue with

Bug#685506: debian-policy: Please add field Files-Excluded to machine readable copyright files definition

On 2012-08-21 14:34:50 +0200 Andreas Tille wrote:> I would propose the following addition to > > http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ > > --- 8< - > Files-Excluded > -- > >

Bug#922267: dh_missing reports missing files, though installed

Package: debhelper Version: 12.1 Severity: normal I just uploaded libmpikmeans_1.5+dfsg-6. During its build, I noticed dh_missing report two files, even though they were installed. With an override and dh_missing --fail-tmp, I get dh_missing: usr/bin/mpi_assign exists in debian/tmp but is not

Bug#922171: autopkgtest-build-lxc: Network availability test fails

On Tue, 12 Feb 2019 22:29:00 +0100 Christian Kastner wrote: > see attached patch. I was a bit too hasty. Here's a patch that works for both old and new option names. >From 20746a2b3a323bac12c8bcfe9b9206f8474b0268 Mon Sep 17 00:00:00 2001 From: Christian Kastner Date: Tue, 12 Feb 2019 22

Bug#922171: autopkgtest-build-lxc: Network availability test fails

apt stuff. Regards, Christian >From b4834e41736131a3889c964c60f468a4c42d49e1 Mon Sep 17 00:00:00 2001 From: Christian Kastner Date: Tue, 12 Feb 2019 22:18:27 +0100 Subject: [PATCH] lxc/default.conf: lxc.network.type is now lxc.net.0.type This was introduced to package lxc by commit ba9e2

Bug#922074: RM: diveintopython3 -- ROM; abandoned, obsolete, low popcon

Package: ftp.debian.org Severity: normal Please remove diveintopython3 from unstable. Upstream vanished in 2011, and some mirrors and forks have gone cold as well. I looked at updating the package to point to other mirrors, but because of the lack of updates since 2011, I would no longer

Bug#921675: sbuild-createchroot: Please set umask to 0022

Package: sbuild Version: 0.78.0-2 Severity: minor Hi, Please consider setting umask to 0022 in sbuild-createchroot. My root has 0027, and together with schroot of type=lvm-snapshot, this results in an unusable chroot. The first indication is an EPERM when finishing up: $ umask 0027 $

Bug#921569: Please stop suggesting python-keyczar

-django-extension, and communicating this change to your upstream. [1] https://github.com/google/keyczar#known-security-issues -- Christian Kastner

Bug#921568: Please stop suggesting python-keyczar

-keyrings.alt, and communicating this change to your upstream. [1] https://github.com/google/keyczar#known-security-issues -- Christian Kastner

Bug#864466: cron: group crontab to root escalation via postinst

On 2017-06-12 23:17, Christian Kastner wrote: > Please find attached a first draft of a (so far only rudimentally > tested) patch for this issue. I attached an updated version in which I reverted a last-minute change breaking the name comparison. diff --git a/debian/postinst b/debian/po

Bug#864466: cron: group crontab to root escalation via postinst

Control: tag -1 +patch Hi Salvatore, On 2017-06-09 20:23, Salvatore Bonaccorso wrote: > On Fri, Jun 09, 2017 at 07:40:18AM +0200, Salvatore Bonaccorso wrote: >> There is reported a group crontab to root escalation via the postinst >> in Debian and Ubuntu, as stated in the oss-security post: >>

Bug#850692: pyrit: failed with 'BitEnumField' object has no attribute 'names'

Hi all, first of all, apologies for the late reply. I moved in February, and I'm still in the process of settling in. I have still to unpack my development machine... On 2017-02-14 09:39, Raphael Hertzog wrote: > On Mon, 09 Jan 2017, Sophie Brun wrote: >> AttributeError: 'BitEnumField' object

Bug#834674: pyevolve: FTBFS in testing (Format: "jpeg" not recognized)

Control: reassign -1 graphviz Control: merge -1 827806 Hi Santiago, On 2016-08-18 00:21, Santiago Vila wrote: > Traceback (most recent call last): > File "pyevolve_ex19_gp.py", line 85, in > main_run() > File "pyevolve_ex19_gp.py", line 82, in main_run > graph.write_jpeg('tree.png',

Bug#834215: Original raw image no longer chowned when using --owner and --convert-cqow2

see much of a use case to keep both, especially when qcow2 is explicitly being requested. Regards, Christian From 960e830f066d9116bd6b8e28424a604644fc8738 Mon Sep 17 00:00:00 2001 From: Christian Kastner <c...@kvr.at> Date: Sat, 13 Aug 2016 09:33:41 +0200 Subject: [PATCH] Also chown raw i

Bug#831817: gitinspector: Missing Js lib

Package: gitinspector Version: 0.3.2+dfsg-1 Severity: normal A typo in patch Use-jQuery-libraries-from-the-Debian-archive.patch breaks the inclusion of the jQuery library "tablesorter". Reported against upstream [1], but as upstream concludes correctly, this is a Debian-specific bug. [1]

Bug#831035: autopkgtest.1: Replace remnant "---" with "--"

On Wed, 13 Jul 2016 21:54:26 +0200 Christian Kastner <c...@debian.org> wrote: > I found a remaining occurrence of "---" in autopkgtest(1). Forgot the attachment, sorry! From 2b69a2eb1b04d79d822283ee5c011a39676ae7db Mon Sep 17 00:00:00 2001 From: Christian Kastner <c...@kvr

Bug#831035: autopkgtest.1: Replace remnant "---" with "--"

Package: autopkgtest Version: 4.0.2 Severity: minor Tags: patch I found a remaining occurrence of "---" in autopkgtest(1). Regards, Christian signature.asc Description: OpenPGP digital signature

Bug#831030: vmdebootstrap: With both --owner and --convert-qcow2, also convert the qcow2 image

this. Regards, Christian From 6e383b38a06e4d251a6e5f559578d26d519fd69c Mon Sep 17 00:00:00 2001 From: Christian Kastner <c...@kvr.at> Date: Wed, 13 Jul 2016 20:33:01 +0200 Subject: [PATCH 4/4] When chowning, also chown generated qcow2 When using both --owner and --convert-qcow2 to

Bug#831029: vmdebootstrap: Move qcow2 conversion to after system_cleanup

against HEAD of master implements this. Regards, Christian From abea99bd9ef4164e317ad25546c24d738d7da68b Mon Sep 17 00:00:00 2001 From: Christian Kastner <c...@kvr.at> Date: Wed, 13 Jul 2016 20:29:56 +0200 Subject: [PATCH 3/4] Move qcow2 conversion to after system cleanup Otherwise, the

Bug#831025: vmdebootstrap: Switch to --no-systemd-networkd in man page

. Regards, Christian From 7f15c9db39cf08b856d6cb0703f5e113abb17445 Mon Sep 17 00:00:00 2001 From: Christian Kastner <c...@kvr.at> Date: Wed, 13 Jul 2016 20:24:56 +0200 Subject: [PATCH 2/4] Switch to --no-systemd-networkd in man page The default value for the systemd-networkd option is Tr

Bug#822180: Please reset umask before creating files

Control: tag -1 + patch On Thu, 21 Apr 2016 22:44:28 +0200 Christian Kastner <c...@debian.org> wrote: > The umask of the invoking user currently affects how files within the VM > are created. Side effects may include various services failing to start, > eg networking: > &

Bug#829496: kpartx -d ( detach ) option silently fails

uot;, > device); > exit(1); > } > printf("loop deleted : %s\n", device); > } > break; I've sent the attached patch

Bug#827806: pyevolve: FTBFS: Program terminated with status: 1. stderr follows: Format: "jpeg" not recognized

On 2016-07-03 12:30, László Böszörményi (GCS) wrote: > In that clean chroot, may you rebuild -13 from source? Then install > it still in that chroot and see the output of 'dot'. You were right: with a rebuilt -13, jpeg is no longer present in 'device', either: device : canon cmap

Bug#827806: pyevolve: FTBFS: Program terminated with status: 1. stderr follows: Format: "jpeg" not recognized

On 2016-07-03 09:26, László Böszörményi (GCS) wrote: > Hi Christian, > > On Sat, Jul 2, 2016 at 10:05 PM, Christian Kastner <c...@debian.org> wrote: >> On 2016-07-02 22:03, Christian Kastner wrote: >>> Support for jpeg seems to have disappeared in graphviz 2.38.

Bug#827806: pyevolve: FTBFS: Program terminated with status: 1. stderr follows: Format: "jpeg" not recognized

Control: reassign -1 graphviz Hi Laszlo, On 2016-06-21 11:59, Chris Lamb wrote: > Source: pyevolve > Version: 0.6~rc1+svn398+dfsg-9 > Severity: serious > Justification: fails to build from source > User: reproducible-bui...@lists.alioth.debian.org > Usertags: ftbfs > X-Debbugs-Cc:

Bug#827806: pyevolve: FTBFS: Program terminated with status: 1. stderr follows: Format: "jpeg" not recognized

On 2016-07-02 22:03, Christian Kastner wrote: > Support for jpeg seems to have disappeared in graphviz 2.38.0-14: > > $ dot -Tjpeg > Format: "jpeg" not recognized. Use one of: canon cmap cmapx cmapx_np dot > eps fig gd gd2 gv imap imap_np ismap pdf pic plain

Bug#825949: pam_systemd(su:session): Cannot create session: Already running in a session

On Tue, 31 May 2016 18:53:43 +0200 (CEST) Santiago Vila wrote: > Since I upgraded to stretch, logcheck sends me messages like this each > time I do "su -" to become root: > > Security Events for su > =-=-=-=-=-=-=-=-=-=-=- > [...] mymachine su[4887]: pam_systemd(su:session):

Bug#824032: libsvm: Would it be possible to upgrade the package to the latest upstream release?

On 2016-05-11 21:51, Dominique Belhachemi wrote: > Thanks for the update Christian, it will leave all changes up to you guys. > > Two more comments: > > 1. Please compare the file size with/without binaries. > 828K libsvm-3.21.tar.gz > 137K libsvm_3.21+dfsg.orig.tar.gz Oh, it's definitely on

Bug#824032: libsvm: Would it be possible to upgrade the package to the latest upstream release?

On 2016-05-11 17:38, Dominique Belhachemi wrote: > I am preparing a NMU to fix #823880. Please don't, see my recent mail to #823880. > Your patch looks good Yes in general, but most changes are unacceptable within the context of an NMU. > and I can integrate it as well as a new python3-libsvm

Bug#823880: libsvm : binary files in source package

Control: severity -1 minor Hi Dominique, On 2016-05-10 01:52, Dominique Belhachemi wrote: > Package: libsvm > Version: 3.12-1.1 > Severity: serious > > The source package contains binary files, see > > https://sources.debian.net/src/libsvm/3.12-1.1/windows/ >

Bug#823556: RFP: mattermost -- self-hosted team communication service

Package: wnpp Severity: wishlist * Package name: mattermost Version : 2.2.0 Upstream Author : Mattermost, Inc. * URL : http://www.mattermost.org/ * License : Apache-2 Programming Lang: Go, React Description : self-hosted team communication service

Bug#823470: RFS: sequitur-g2p/0.0.r1668.r3-1 -- Grapheme to Phoneme conversion tool

On 2016-05-05 17:16, Giulio Paci wrote: >> One thing I'm not quite sure I follow yet is the change in the version >> numbering scheme, both upstream and in the package. This is how it looks >> to me: >> >> 1. Upstream re-used revision r1668 and added a -r3 suffix >> -> "r1668" trades a bit of

Bug#823470: RFS: sequitur-g2p/0.0.r1668.r3-1 -- Grapheme to Phoneme conversion tool

Hi Giulio, On 2016-05-05 03:57, Giulio Paci wrote: > I am looking for a sponsor for an updated version of my package "sequitur-g2p" >git clone git://anonscm.debian.org/collab-maint/sequitur-g2p.git > A package review is very welcome as well. Looks good to me. Nice to see that upstream

Bug#815088: cron: sysv init script has "Required-Start: $remote_fs" but systemd service does not

Control: tag -1 confirmed pending Hi Sandro, On 2016-02-18 16:45, Sandro Tosi wrote: > i just noticed the systemd service for cron doesnt define a depencency on > remote-fs.target , while the sysv init script have the "Required-Start: > $remote_fs". I think that dependency should be added.

Bug#811126: cron: MIME-Version header not set thus Content-Type and other MIME headers may be ignored

Control: tag -1 moreinfo Hi, On 2016-01-15 22:18, Vincent Caron wrote: > Package: cron > Version: 3.0pl1-127+deb8u1 ^^^ This version already contains this fix; it first included in 3.0pl1-125. Is it possible that you got your versions mixed up? > when sending command

Bug#814678: cron: No information given about syntax error in /etc/crontab

Control: severity -1 minor On 2016-02-14 00:36, teo8...@gmail.com wrote: > Package: cron > Version: 3.0pl1-124 > Severity: important I downgraded the severity as objectively speaking, this is a cosmetic issue. >* What led up to the situation? > > Have a syntax error in /etc/crontab > >

Bug#750645: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

Control: tag -1 + confirmed pending On 2015-09-26 10:47, Tobias Kranz wrote: > Setting up cron (3.0pl1-127+deb8u1) ... > update-rc.d: warning: start and stop actions are no longer supported; > falling back to defaults > > I think this is triggered by the postinst script (in my case package >

Bug#823161: RFA: libcgroup -- library and utilities for using the Linux Control Group mechanism

Package: wnpp Severity: normal I request an adopter for the libcgroup package. It provides a library, a PAM module, and executables, all used for manipulating, controlling, administering, and monitoring of the Control Groups mechanism of the Linux kernel. Apart from the 3 open bugs, the package

Bug#809467: FTCBFS on non-linux: not found

Hi Helmut, Steven, On 2016-01-02 04:22, Steven Chamberlain wrote: > To clarify slightly, sys/capability.h *is* found, because a copy is > bundled in libcap/sys/. But it depends on arch-specific Linux headers. > > Helmut Grohne wrote: >> Steven, can you confirm that libcap2 can be crossed after

Bug#822360: RFS: sequitur-g2p/0.0.r1668-3 -- Grapheme to Phoneme conversion tool

control: owner -1 ! Hi Giulio, I'd be happy to sponsor your package. On 2016-04-23 21:06, Giulio Paci wrote: > I am looking for a sponsor for an updated version of my package "sequitur-g2p" > > You can download the package with git using this command: > >git clone

Bug#821877: python3.5.1-11 causes a 90 second delay to startup time on cinnamon desktop

On Wed, 20 Apr 2016 07:21:45 +0100 peter wrote: > using current installed version 3.5.1-10 of all the above my startup > time to > login screen, > as shown by the first line of systemd-analyze critical-chain is : > graphical.target @2.918s > > If I upgrade them all to

Bug#822180: Please reset umask before creating files

Package: vmdebootstrap Version: 1.5-1 Severity: normal The umask of the invoking user currently affects how files within the VM are created. Side effects may include various services failing to start, eg networking: > [FAILED] Failed to start Network Service. > See 'systemctl status

Bug#809167: cron: Cron Daemon Use-After-Free Vulnerability May Cause Local Root Privilege Escalation

Hi, thank you for your report. I've already spent a good amount of time analyzing the potential impact of this flaw, but I would like to refrain from further public comments until I have discussed this with security@d.o. Thanks, Christian On 2015-12-27 19:57, Cron Daemon Use-After-Free

Bug#806225: cron: please consider to migrate to '3.0 (quilt)' source format

Hi Sandro, On 2015-11-25 16:04, Sandro Tosi wrote: > Hello, > I found myself in a situation where I need to patch cron, and it is a huge > pain > to handle that patch when the source package contains the debian changes > directly applied to the upstream source code. > > Looking at the git repo

Bug#806225: cron: please consider to migrate to '3.0 (quilt)' source format

On 2015-11-25 22:01, Sandro Tosi wrote: > On Wed, Nov 25, 2015 at 8:20 PM, Christian Kastner <c...@debian.org> wrote: >>> I'm wondering if you plan on switching to '3.0 (quilt)' anytime soon, >>> eventually >>> resurrecting the work done for 79fc563. >>

Bug#804343: RFS: libsvm/3.20-1 [NMU] -- library implementing support vector machines

Hi, On 2015-11-07 18:21, Gianfranco Costamagna wrote: >>libsvm (3.20-1) unstable; urgency=medium >> >> * Non-maintainer upload. [...] > >> * Import new upstream version. > > > this is really out of an NMU scope, do you have any evidence about the > maintainer > being MIA/not interested

Bug#804426: gitinspector: FTBFS: ImportError: No module named unittest2

Control: tag -1 confirmed pending Hi Chris, On 2015-11-08 12:51, Chris Lamb wrote: > Dear Maintainer, > > gitinspector fails to build from source in unstable/amd64: > > == > ERROR: tests.test_comment

Bug#804081: lightdm-gtk-greeter-settings does not build reproducibly

Hi James, On 2015-11-07 04:32, James Lu wrote: > I've made the changes in setup.py to sort the fields in > installation_config in the Git tree. However, when running the build > multiple times, the output .deb's from the different tries still don't > have the same checksum. debbindiff seems to be

Bug#804081: lightdm-gtk-greeter-settings does not build reproducibly

Source: lightdm-gtk-greeter-settings Version: 1.2.0-1 Severity: minor Hi, lightdm-gtk-greeter-settings does not build reproducibly. This is because 'installation_config.py', a file produced at build time, is not generated deterministically. This file is created by write_config() in setup.py.

Bug#803680: Transistion: liblinear

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, I just accidentally uploaded the new version of liblinear to unstable, instead of my intended target experimental :-/ This bumps the SONAME in unstable. liblinear has two reverse

Bug#801209: autopkgtest: adt-setup-vm tries to use host's network interface name

Hi Martin, On 2015-10-08 15:59, Martin Pitt wrote: > Control: tag -1 pending > > Christian Seiler [2015-10-07 15:24 +0200]: >> adt-setup-vm tries to use the host's network interface name when called >> from e.g. vmdebootstrap. Especially if the recommended command in the >> man page of

Bug#801237: mactel-boot review

On 2015-10-23 21:47, Bernhard Reiter wrote: > Am 2015-10-23 um 18:47 schrieb Gianfranco Costamagna: >> Control: owner -1 ! Control: tags -1 moreinfo > >> Hi, the packaging looks fine, however I don't understand what the >> code is supposed to do. > >> seems that the purpose of this code is to

Bug#790104: RFS: lightdm-gtk-greeter-settings/1.2.0-1 [ITP]

On 2015-10-11 07:54, James Lu wrote: >> d/copyright: >> - The license appears to be GPL-3, not GPL-3+ (at least in the handful >>of files I checked). This also requires correction of the free- >>standing license block (the last paragraph) > > I see. Ubuntu's packaging wrote the license

Bug#706352: New upstream version available: 2.2.0

Control: tag -1 pending On 2015-03-02 16:23, Salvador Fandino wrote: > Python bindings for 2.2 are available from GitHub. > > http://leenissen.dk/fann/wp/language-bindings/ > > The CPP bindings are available on the main package. > > Anyway, the library is completely backward compatible, so

Bug#790104: RFS: lightdm-gtk-greeter-settings/1.2.0-1 [ITP]

Hi James, a review of your package follows: On 2015-06-27 06:59, James Lu wrote: > I am looking for a sponsor for my package "lightdm-gtk-greeter-settings". > > * Package name: lightdm-gtk-greeter-settings >Version : 1.2.0-1 >Upstream Author : Andrew P.

Bug#788244: libpam-cgroup: Does not do anything

Hi Reco, On 2015-06-09 20:15, Reco wrote: > Current stable version for libpam-cgroup suffers from severe > programming error, which prevents libpam-cgroup from doing anything > at all. > > libpam-cgroup calls 'cgroup_change_cgroup_uid_gid_flags' libcgroup > function with CGFLAG_USECACHE.

Bug#800075: ITP: python-fann2 -- Python bindings for FANN

Package: wnpp Severity: wishlist Owner: Christian Kastner <c...@debian.org> * Package name: python-fann2 Version : 1.0.7 Upstream Author : FutureLinkCorporation * URL : https://github.com/FutureLinkCorporation/fann2 * License : LGPL-2.1+ Programmin

Bug#799805: kytea: Problem with upcoming new version of liblinear

Source: kytea Version: 0.4.6+dfsg-2 Severity: important Hi, I recently uploaded a new version of liblinear to experimental. This new version bumps the SONAME. Among other things, the declaration of "struct problem" in linear.h changed: > struct problem > { > int l, n; > - int *y;

Bug#787328: RFS: mpd-sima/0.13.1-1

(replying just to the issues I raised) On 2015-09-15 21:00, Geoff wrote: >> - It is helpful to be more explicit about some changes. You mention, >> for example, that the package has been converted to Python 3. The >> fact that the Python 2 package has been dropped is merely implied. >>

Bug#787328: RFS: mpd-sima/0.13.1-1

Hi Geoff, Gianfranco already beat me to the review; nevertheless, here are some additional notes I had prepared, based on the package I saw on Sunday (the package is no longer visible on mentors.d.n). On 2015-09-14 12:32, Gianfranco Costamagna wrote: > lets review: > > 1) you dropped 0.10.0-2

Bug#780528: python-liblinear: This package is out of date, they've released liblinear version 1.96.

Control: tag -1 + pending On Sun, 15 Mar 2015 18:01:24 +0100 Christian Kastner <deb...@kvr.at> wrote: > On 2015-03-15 17:35, Arbiter Yang wrote: > > Liblinear's github page: https://github.com/cjlin1/liblinear/ > > > > The version version of this package is 1.8, It se

Bug#798157: FTBFS on musl-linux-any: ULONG_MAX undefined

Control: tag -1 pending Hi Helmut, On 2015-09-06 11:45, Helmut Grohne wrote: > keyutils currently FTBFS when built against the musl C library. > This issue is not specific not musl nor to cross building. The relevant > file key.dns_resolver.c uses the macros UINT_MAX and ULONG_MAX without >

Bug#796886: FTCBFS: links -lattr with build arch compiler but does not Build-Depends: libattr-dev:native

Hi Helmut, On 2015-08-25 15:18, Helmut Grohne wrote: The 1:2.24-10 upload introduced a regression with cross building. (I accidentally deleted the build log, sorry.) At some point it compiles _makenames.c with $(BUILD_CC) (which is correct), but it now passes $(LDFLAGS) which can only be used

Bug#796913: gbp-dch: --no-git-author does not seem to have an effect

Package: git-buildpackage Version: 0.6.32 Severity: minor Using --no-git-author with gbp-dch does not seem to have an effect; gbp-dch always used name and email from git-config. I expected it to use DEBFULLNAME and DEBEMAIL. Regards, Christian

<    1   2   3   4   5   6   7   8   9   >