Bug#1057684: [request-tracker-maintainers] Bug#1057684: request-tracker5: leaves alternatives after purge: /usr/sbin/rt-clean-attributes -> /etc/alternatives/rt-clean-attributes
Hi Andreas, > during a test with piuparts I noticed your package left unowned files on > the system after purge, which is a violation of policy 6.8: > > The leftover files are actually alternatives that were installed by the > package but have not been properly removed. Thank you for for reporting this, I thought I had it nicely clean, but it seems my testing didn't pick up all the things. #sigh I'll fix these issues. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1055128: [request-tracker-maintainers] Bug#1055128: request-tracker5: Incorrect CVE mentioned in request-tracker5 changelog
Control: found 1055128 5.0.5+dfsg-1 On Wed, 2023-11-01 at 09:11 +1100, Geoff Crompton wrote: > I noticed in the changelog entry for 5.0.3+dfsg-3~deb12u2 > CVE-2023-41620 is mentioned. But the description fro that CVE matches > the description for CVE-2023-41260 on > https://docs.bestpractical.com/release-notes/rt/5.0.5 > > I think there is a minor typo in the changelog. I noticed this typo is > also present in the changelog for 5.0.5+dfsg-1 on > https://metadata.ftp-master.debian.org/changelogs//main/r/request- > tracker5/request-tracker5_5.0.5+dfsg-1_changelog. Dammit. I was double checking those. Thank you for raising this. I've pushed commits to fix these in the next upload of each version, but I won't upload new versions just to fix this. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1040996: Davical defines a Content-Security-Policy without scoping it to its own resources
Hi Alain, Thanks for the bug report. I have added a fix to DAViCal so the CSP is only applied to the Directory as suggested. I'm looking at your .well-known request, but I don't think DAViCal and NextCloud can co-exist so easily as it looks like they both have overlapping well-known paths. I would expect they need to go into their own vhost. And while I could limit the rewrites, we still have: RewriteRule ^(.*)$ /caldav.php$1 [NC,L] I think there'll be far too many different options to want to split that out. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1040996: [DAViCal-devel] Bug#1040996: Why "form-action 'self' sis.redsys.es"?
On Mon, 2023-10-23 at 10:05 +0200, Philipp Marek via DAViCal-devel wrote: > For that config line, why is > > form-action 'self' sis.redsys.es > > set up as a default? > > I guess that's a left-over for testing from upstream, > but that should be removed in the official default config file. That is a mistake which I accidentally introduced. Funnily enough was raised on the davical-devel mailing list today. I have already submitted an MR to resolve this. -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1053438: molly-guard: Support configuration management tools like Ansible
Package: molly-guard Version: 0.7.2 Severity: wishlist Tags: patch Dear Maintainer, While working on adding a snippet to molly-guard to check for running VMs and prompt if there are any, we discovered that the standard approach for systems managed by Ansible is to bypass molly-guard completely. See https://docs.ansible.com/ansible/8/collections/ansible/builtin/reboot_module.html and search for molly-guard. We use Ansible, and I think this sucks, as I want molly-guard to protect reboots for other situations. I have modified molly-guard to detect being run by Ansible and not ask questions, just exit 1 and refuse to take action. We have deployed this to some of our fleet and have found it to work fine. Would you please consider merging this change? Changes are here: https://salsa.debian.org/puck/molly-guard/-/commits/conf-mgmt This also includes patches for general housekeeping of the package. In addition, I have considered whether the prompt logic and sigh() should be moved into shutdown.in and allowed to be generic. I'd be interested to hear your thoughts, and I'd be happy to have a punt at that. Kind regards, Andrew -- System Information: Debian Release: 12.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 6.1.0-12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_AUX Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages molly-guard depends on: ii procps 2:4.0.2-3 molly-guard recommends no packages. molly-guard suggests no packages. -- no debconf information
Bug#986707: rt4-db-mysql: should declare an incompatibility with mysql 8
The problem I can see with conflicting with mysql-server-8.0 is that a user could have both MySQL and MariaDB installed on the same server, as they should be able to co-exist (listen on different ports). If we conflict, then we prevent that. The issue is that in Debian default-mysql-client and virtual-mysql-client (and -server) depend on mariadb, but in Ubuntu they depend on mysql. Perhaps we should explicitly depend on the mariadb packages. Thinking about this is a bit further, this does seem the best option. RT 5.0.4 supports MySQL 8, which is now in Debian Unstable, so this'd only apply to the RT4 packages now. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1050048: [request-tracker-maintainers] Bug#1050048: request-tracker5: depends on obsolete package fonts-noto-hinted
Control: tag -1 + pending Upload currently blocked while I try and find the dependency that is causing our tests to fail. -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1042985: libgnupg-interface-perl: FTBFS with Perl 5.38: Insecure directory in $ENV{PATH} while running with -T switch
Control: forwarded -1 https://rt.cpan.org/Ticket/Display.html?id=149323 Control: tag -1 + fixed pending Hi Niko, Thank you for Cc'ing me, yes, I'm still interested. I've had a look, and prepared a patch and forwarded it to upstream. This is now in Salsa - I can't upload it as I'm not an Uploader nor a DD (yet). The test which broke is one I wrote to test GnuPG::Interface when running taint mode as there are packages in Debian that use that and they break when GnuPG::Interface breaks. > Hm, possibly perl should add a Breaks for earlier versions once this is > fixed. Yeah, seems sensible. I expect this'll probably affect other packages as well. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz | signature.asc Description: This is a digitally signed message part
Bug#1043041: RM: rt-extension-elapsedbusinesstime/experimental -- ROM; No longer required in experimental
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rt-extension-elapsedbusinesst...@packages.debian.org Control: affects -1 + src:rt-extension-elapsedbusinesstime Hi, This package has been uploaded to unstable, please remove it from experimental. Kind regards, Andrew
Bug#1040975: CW font disabled in groff-base v1.23
Control: reassign -1 groff-base Control: affects -1 perl Hey, I think a change in groff-base to re-enable the CW font alias might be reasonable. This affects a number of other packages, not just perl (via pod2man), for example: puck@dirk:~$ man --warnings /usr/share/man/man1/strace.1.gz > /dev/null troff::88: warning: macro 'IX' not defined troff::119: warning: cannot select font 'CW' troff::124: warning: cannot select font 'CW' ... (Lintian excludes the IX macro which is why that is present) Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz | signature.asc Description: This is a digitally signed message part
Bug#1040975: perl: pod2man uses CW, groff-base no longer supports this by default
Package: perl Version: 5.36.0-7 Severity: normal Dear Maintainer, groff-base v1.23 has been uploaded to unstable, which disables the CW macro by default. This causes errors like this to be generated with pod2man now: puck@dirk:~$ pod2man /usr/share/perl/5.36.0/version.pod | nroff -man | grep CW troff::145: warning: cannot select font 'CW' troff::182: warning: cannot select font 'CW' troff::191: warning: cannot select font 'CW' troff::205: warning: cannot select font 'CW' troff::207: warning: cannot select font 'CW' ... This is causing lintian to be upset when build packages, e.g.: W: rt-extension-mergeusers-common: groff-message troff::115: warning: cannot select font 'CW' [usr/share/man/man3/RT::Extension::MergeUsers.3pm.gz:1] This version of groff-base introduces a new option in /etc/groff/man.local: .\" "CW" is not a portable font name, but some man pages use it anyway. .\" Uncomment this to suppress warnings produced by such pages. This .\" test remaps the font to roman ("R") on nroff (terminal) devices. You .\" might prefer to remap it to bold ("B") instead. .\" .if n .ftr CW R Now, is it pod2man or groff-base that is at fault here? Perl 5.38 still uses CW in pod2man by default. Cheers, Andrew -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages perl depends on: ii dpkg 1.21.22 ii libperl5.365.36.0-7 ii perl-base 5.36.0-7 ii perl-modules-5.36 5.36.0-7 Versions of packages perl recommends: ii netbase 6.4 Versions of packages perl suggests: pn libtap-harness-archive-perl ii libterm-readline-gnu-perl1.45-1 ii libterm-readline-perl-perl 1.0303-2.1 ii make 4.3-4.1 ii perl-doc 5.36.0-7 -- no debconf information
Bug#1039742: [DAViCal-devel] Bug#1039742: Add support for phpunit 10
Hi Athos, Thank you! As upstream, I've merged the MR -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#903960: Possibly fixed?
Hey, The upstream bug in gtk has been closed, with the fix being merged into gtk- 3-24 branch in Nov 2019 and was included in GTK 3.24.13. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1038344: bookworm-pu: package request-tracker5/5.0.3+dfsg-2+deb12u1
On Mon, 2023-06-26 at 07:01 +0100, Jonathan Wiltshire wrote: > On Mon, Jun 26, 2023 at 04:42:27PM +1200, Andrew Ruthven wrote: > > Changelog updated as requested, and uploaded to bookworm. > > You need a tilde in the version, not a plus ("lower than"). I'll reject > the > upload, you can upload a fixed version whenever you like. Doh. Fixed. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1038344: bookworm-pu: package request-tracker5/5.0.3+dfsg-2+deb12u1
On Sun, 2023-06-25 at 17:43 +0100, Jonathan Wiltshire wrote: > Control: tag -1 confirmed > > I just happened to look at this; otherwise as it was still tagged > "moreinfo" it would probably have been waiting for attention for quite a > while. Oops, I did wonder if I should change the tag. > As 5.0.3+dfsg-3 in unstable is limited to these changes anyway, you can > backport it directly and the version history makes things a bit clearer > for > some infrastructure. Just add a changelog entry on top of the unstable > version, "Backport to bookworm" or something, version 5.0.3+dfsg- > 3~deb12u1, > target bookworm. Don't remove the changelog for 5.0.3+dfsg-3. > > Example: > https://release.debian.org/proposed-updates/bookworm_diffs/onionshare_2.6-5~deb12u1.debdiff > > Other than that, please go ahead. Awesome, thank you. I figured it'd make life easier to upload only these changes to unstable initially. Changelog updated as requested, and uploaded to bookworm. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1038344: bookworm-pu: package request-tracker5/5.0.3+dfsg-2+deb12u1
[Resent Cc'ing in the bug, Evolution dropped it first time round, sigh] On Sat, 2023-06-17 at 13:05 +0100, Adam D. Barratt wrote: > You appear to have attached a binary debdiff. Please provide a _source_ > debdiff for checking. My apologies, first time I've done this. I had generated it as well. Please find the source debdiff attached. The patches are managed using git-dpm which is why the git commit ID has changed for all of them. The patch in question is debianize_version.diff . Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz | diff -Nru request-tracker5-5.0.3+dfsg/debian/changelog request-tracker5-5.0.3+dfsg/debian/changelog --- request-tracker5-5.0.3+dfsg/debian/changelog 2022-07-22 01:28:17.0 +1200 +++ request-tracker5-5.0.3+dfsg/debian/changelog 2023-06-11 14:19:13.0 +1200 @@ -1,3 +1,11 @@ +request-tracker5 (5.0.3+dfsg-2+deb12u1) bookworm; urgency=medium + + * Strip Debian version suffix from generated hyperlinks to upstream docs +(Closes: 1033304). + * Fix the changelog date entry for the 5.0.3+dfsg-2 release. + + -- Andrew Ruthven Sun, 11 Jun 2023 14:19:13 +1200 + request-tracker5 (5.0.3+dfsg-2) unstable; urgency=medium * Add more fields to d/upstream/metadata @@ -13,7 +21,7 @@ * Remove dependency on lsb-base as it is an obsolete package. * Refresh d/copyright - -- Andrew Ruthven Fri, 22 Jul 2022 01:28:17 +1200 + -- Andrew Ruthven Sat, 04 Feb 2023 12:30:17 +1300 request-tracker5 (5.0.3+dfsg-1.1) unstable; urgency=medium diff -Nru request-tracker5-5.0.3+dfsg/debian/.git-dpm request-tracker5-5.0.3+dfsg/debian/.git-dpm --- request-tracker5-5.0.3+dfsg/debian/.git-dpm 2022-07-22 01:28:17.0 +1200 +++ request-tracker5-5.0.3+dfsg/debian/.git-dpm 2023-06-05 20:13:11.0 +1200 @@ -1,6 +1,6 @@ # see git-dpm(1) from git-dpm package -c18433eb098f64a7c1d81502e7bcc689a2df0943 -c18433eb098f64a7c1d81502e7bcc689a2df0943 +28481171ee3345c8bed6efb9d5a46cfce1547fc0 +28481171ee3345c8bed6efb9d5a46cfce1547fc0 52cb0ca22325e7a067f0a3411ffb55ef03d47aa4 52cb0ca22325e7a067f0a3411ffb55ef03d47aa4 request-tracker5_5.0.3+dfsg.orig.tar.gz diff -Nru request-tracker5-5.0.3+dfsg/debian/patches/debianize_charts.diff request-tracker5-5.0.3+dfsg/debian/patches/debianize_charts.diff --- request-tracker5-5.0.3+dfsg/debian/patches/debianize_charts.diff 2022-07-22 01:28:17.0 +1200 +++ request-tracker5-5.0.3+dfsg/debian/patches/debianize_charts.diff 2023-06-05 20:13:11.0 +1200 @@ -1,4 +1,4 @@ -From 90ca199172517271447e571d777964324343ef1a Mon Sep 17 00:00:00 2001 +From e4a897eeca21986a0fe788ad15edb6f500c99772 Mon Sep 17 00:00:00 2001 From: Andrew Ruthven Date: Thu, 9 Jul 2020 23:03:35 +1200 Subject: On Debian there is no need to install the GD modules if GD is diff -Nru request-tracker5-5.0.3+dfsg/debian/patches/debianize_commands.diff request-tracker5-5.0.3+dfsg/debian/patches/debianize_commands.diff --- request-tracker5-5.0.3+dfsg/debian/patches/debianize_commands.diff 2022-07-22 01:28:17.0 +1200 +++ request-tracker5-5.0.3+dfsg/debian/patches/debianize_commands.diff 2023-06-05 20:13:11.0 +1200 @@ -1,4 +1,4 @@ -From 13f2358416863200df51361f2643e7ec35680748 Mon Sep 17 00:00:00 2001 +From 2b5ef414f9d88dc4321d602dda5556c6bd04eb90 Mon Sep 17 00:00:00 2001 From: Andrew Ruthven Date: Thu, 9 Jul 2020 22:53:09 +1200 Subject: Use Debian location of commands and data diff -Nru request-tracker5-5.0.3+dfsg/debian/patches/debianize_extensions.diff request-tracker5-5.0.3+dfsg/debian/patches/debianize_extensions.diff --- request-tracker5-5.0.3+dfsg/debian/patches/debianize_extensions.diff 2022-07-22 01:28:17.0 +1200 +++ request-tracker5-5.0.3+dfsg/debian/patches/debianize_extensions.diff 2023-06-05 20:13:11.0 +1200 @@ -1,4 +1,4 @@ -From 4ea4ef63b501e9c635c0d18340f15107427f59be Mon Sep 17 00:00:00 2001 +From 83787c6f7b0c8f3683bc06c756575e444e2fc808 Mon Sep 17 00:00:00 2001 From: Andrew Ruthven Date: Thu, 9 Jul 2020 22:33:55 +1200 Subject: Point to Debian locaton of mason_data. diff -Nru request-tracker5-5.0.3+dfsg/debian/patches/debianize_version.diff request-tracker5-5.0.3+dfsg/debian/patches/debianize_version.diff --- request-tracker5-5.0.3+dfsg/debian/patches/debianize_version.diff 2022-07-22 01:28:17.0 +1200 +++ request-tracker5-5.0.3+dfsg/debian/patches/debianize_version.diff 2023-06-05 20:13:11.0 +1200 @@ -1,4 +1,4 @@ -From 55312fbba42fbedd49061601741d5960061d5703 Mon Sep 17 00:00:00 2001 +From e00d7b16bc8b70db0125349ead6841adfa1d4c32 Mon Sep 17 00:00:00 2001 From: Dominic Hargreaves Date: Thu, 31 Dec 2015 12:17:56 + Subject: Extract the correct (Debian) version number in configure.ac @@ -8,9 +8,10 @@ Patch-Name: debianize_version.diff --- - configure.ac | 8 - share/html/Elements/Footer | 2 +- - 2 files changed, 5 insertions(+), 5 deletions(-) + config
Bug#1038344: bookworm-pu: package request-tracker5/5.0.3+dfsg-2+deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: request-track...@packages.debian.org Control: affects -1 + src:request-tracker5 [ Reason ] The version in bookworm includes a bug where the suffix we append to the upstream version is included in a generated URL for accessing documentation about configuration settings presented in the UI. Bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033304 We weren't able to include this in the bookworm releases as our packages suffered a FTBFS issue due to a rhino and closure-compiler issue, as discussed here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036159 By the time the issues with closure-compiler and rhino were resolved it was too late to get a fixed version of request-tracker5 into bookworm. I have also included a minor fix to the date string in d/changelog for 5.0.3+dfsg-2 as I failed to update the date when I uploaded that version, and then due to the FTBFS issue I wasn't able to resolve it when I spotted it. Version 5.0.3+dfsg-3 in unstable only includes the fixes which are proposed for bookworm. [ Impact ] When an RT administrator attempts to look up the documentation for a configuration setting, they'll get a 404. [ Tests ] I have installed the proposed packages on my personal RT installation running bookworm, and verified that the generated links are correct and work. [ Risks ] Low risk. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] d/patch/debianize_version.diff now modifies share/html/Admin/Tools/Config/Elements/Option to strip everything after and including '+dfsg-' from the version string. [ Other info ] I acknowledge that it would be preferable to link to documentation contained within the running system, but our packages don't currently configure the generated documentation to be accessible via the web. File lists identical (after any substitutions)
Bug#1037248: ITP: libcss-inliner-perl -- Convert CSS
Package: wnpp Owner: Andrew Ruthven Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libcss-inliner-perl Version : 4018 Upstream Author : Kevin Kamel * URL : https://metacpan.org/release/CSS-Inliner * License : Artistic or GPL-1+ Programming Lang: Perl Description : Convert CSS
Bug#1037246: ITP: libhtml-query-perl -- perform jQuery-like queries on HTML::Element trees
Package: wnpp Owner: Andrew Ruthven Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libhtml-query-perl Version : 0.09 Upstream Author : Kevin Kamel * URL : https://metacpan.org/release/HTML-Query * License : Artistic or GPL-1+ Programming Lang: Perl Description : perform jQuery-like queries on HTML::Element trees The HTML::Query module is an add-on for the HTML::Tree module set. It provides a simple way to select one or more elements from a tree using a query syntax inspired by jQuery. This selector syntax will be reassuringly familiar to anyone who has ever written a CSS selector. HTML::Query is not an attempt to provide a complete (or even near-complete) implementation of jQuery in Perl (see Ingy's pQuery module for a more ambitious attempt at that). Rather, it borrows some of the tried and tested selector syntax from jQuery (and CSS) that can easily be mapped onto the look_down() method provided by the HTML::Element module. The package will be maintained under the umbrella of the Debian Perl Group. This package is being added to Debian as it is dependency for CSS::Inliner which will be used by v5.0.4 of Request Tracker. -- Generated with the help of dpt-gen-itp(1) from pkg-perl-tools. -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1037117: ITP: libbadger-perl -- Badger application programming toolkit
Package: wnpp Owner: Andrew Ruthven Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libbadger-perl Version : 0.16 Upstream Author : Andy Wardley * URL : https://metacpan.org/release/Badger * License : Artistic or GPL-1+ Programming Lang: Perl Description : Badger application programming toolkit The Badger toolkit is a collection of Perl modules designed to simplify the process of building object-oriented Perl applications. It provides a set of foundation classes upon which you can quickly build robust and reliable systems that are simple, skimpy and scalable. The package will be maintained under the umbrella of the Debian Perl Group. This package is being added to Debian as it is an indirect build dependency for CSS::Inliner which will be used by v5.0.4 of Request Tracker. -- Generated with the help of dpt-gen-itp(1) from pkg-perl-tools. -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1037110: ITP: libgraphviz2-perl -- Perl interface to the GraphViz graphing tool
Package: wnpp Owner: Andrew Ruthven Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libgraphviz2-perl Version : 2.67 Upstream Author : Ron Savage * URL : https://metacpan.org/release/GraphViz2 * License : Artistic or GPL-1+ Programming Lang: Perl Description : Perl interface to the GraphViz graphing tool This module provides an interface to layout and image generation of directed and undirected graphs in a variety of formats (PostScript, PNG, etc.) using the "dot", "neato", "twopi", "circo" and "fdp" programs from the GraphViz project (http://www.graphviz.org/ or http://www.research.att.com/sw/tools/graphviz/). This is a complete rewrite of the module in libgraphviz-perl which extends support to all the latest features of Graphviz. It is not backwards compatible with libgraphviz-perl. In addition, the GraphViz Perl module is deprecated[0], GraphViz2 is the replacement. GraphViz2 is a dependency of Request Tracker v5.0.4. The package will be maintained under the umbrella of the Debian Perl Group. [0] https://metacpan.org/pod/GraphViz -- Generated with the help of dpt-gen-itp(1) from pkg-perl-tools. -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz | signature.asc Description: This is a digitally signed message part
Bug#1037109: ITP: libtest-snapshot-perl -- test against data stored in automatically-named file
Package: wnpp Owner: Andrew Ruthven Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name : libtest-snapshot-perl Version : 0.06 Upstream Author : Ed J * URL : https://metacpan.org/release/Test-Snapshot * License : GPL-1+ or Artistic Programming Lang: Perl Description : test against data stored in automatically-named file Not connected with Test::Snapshots, which is based on a similar concept but for running executables. Implements a function to automate the storing and updating of expected test outputs. This is based on the idea known in frontend development circles as "snapshot testing", hence the module name. The package will be maintained under the umbrella of the Debian Perl Group. This module is required for building the GraphViz2 Perl module which I'm about to file an ITP about. [Apologies for the previous email, first time I've submitted an ITP for a number of years!] -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz | signature.asc Description: This is a digitally signed message part
Bug#1035538: nautilus: Missing dependency on "eject" package
Package: nautilus Version: 43.2-1 Severity: important Dear Maintainer, If the eject package isn't installed, when you try to eject a USB device (I didn't test anything else), then Nautilus is unable to eject the device and throws up an error like: Error ejecting /dev/sda: Error spawning command-line `eject '/dev/sda'': Failed to execute chidl process "eject" (No such file or directory) (g-exec-error-quark, 8). I reckon that the natilus package should depend on the eject package. Cheers, Andrew -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_AUX Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nautilus depends on: ii bubblewrap 0.8.0-2 ii desktop-file-utils 0.26-1 ii gsettings-desktop-schemas 43.0-1 ii gvfs1.50.3-1 ii libadwaita-1-0 1.2.2-1 ii libc6 2.36-9 ii libcairo2 1.16.0-7 ii libcloudproviders0 0.3.1-2 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libgexiv2-2 0.14.0-1+b1 ii libglib2.0-02.74.6-2 ii libglib2.0-data 2.74.6-2 ii libgnome-autoar-0-0 0.4.3-1 ii libgnome-desktop-4-243.2-2 ii libgstreamer-plugins-base1.0-0 1.22.0-3 ii libgstreamer1.0-0 1.22.0-2 ii libgtk-4-1 4.8.3+ds-2 ii libnautilus-extension4 43.2-1 ii libpango-1.0-0 1.50.12+ds-1 ii libportal-gtk4-10.6-4 ii libportal1 0.6-4 ii libselinux1 3.4-1+b5 ii libtracker-sparql-3.0-0 3.4.2-1 ii nautilus-data 43.2-1 ii shared-mime-info2.2-1 ii tracker 3.4.2-1 ii tracker-extract 3.4.3-1 ii tracker-miner-fs3.4.3-1 Versions of packages nautilus recommends: ii gnome-sushi 43.0-2 ii gvfs-backends 1.50.3-1 pn libgdk-pixbuf2.0-bin ii librsvg2-common 2.54.5+dfsg-1 Versions of packages nautilus suggests: ii eog 43.2-1 ii evince [pdf-viewer] 43.1-2+b1 pn nautilus-extension-brasero ii nautilus-sendto 3.8.6-3.1 ii totem 43.0-2 ii vlc [mp3-decoder] 3.0.18-2 ii xdg-user-dirs 0.18-1 -- no debconf information
Bug#1030749: Bug#1031587: [request-tracker-maintainers] Bug#1031587: Handling of the request-tracker4 -> request-tracker5 transition in bookworm
Hi folks, > Sorry for the long delay. Myself and, I think, Andrew have been short > on time. Yes, my apologies, I've been very busy the last couple of months. > The transition is basically ready to go, but I've been rethinking the > need > to drop request-tracker4, given it will all be quite tight. It turns > out that > request-tracker4 is still supported upstream > (https://bestpractical.com/release-policy) > and there's no specific EoL set. When we first started the plan to > deprecate request-tracker4 in Debian, I think we were assuming > otherwise. > The package is in good shape and I believe otherwise ready to be > released. > > If Andrew is in agreement, I therefore think we should let request- > tracker4 > be released with the next release. We can reconsider whether to drop > it from > the release + 1 at a more leisurely pace. The work we've done to date > will not > be wasted effort. Yes, I'm okay with keeping request-tracker4 in Bookworm, as Dominic says, the package is in good shape. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1033304: request-tracker5: debianisation of version interferes with doc linking
Hey, Thank you for the bug report. I'm just testing a fix now. This doesn't affect the RT4 packages as RT4 doesn't have a web interface for configuring RT, and even when viewing the config, it doesn't link to the docs. Cheers, Andrew On Wed, 2023-03-22 at 11:51 +1100, AP wrote: > > RT5 (and possibly RT4) uses the version number to generate a URL for > its documentation. > This URL is in use when configuring the system via the web interface > (click on a config > name and it takes you to the help for it). > > As a result the help results in a 404 until you manually remove the > debian component of > the version. > > This error is the result of the debianize_version.diff patch which > changes the version > globally. -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1031587: [request-tracker-maintainers] Bug#1031587: Handling of the request-tracker4 -> request-tracker5 transition in bookworm
On Sun, 2023-02-19 at 00:12 +0200, Adrian Bunk wrote: > https://release.debian.org/testing/freeze_policy.html#soft > > ... > Dropping or adding binary packages to a source package, moving > binaries between source packages or renaming source or binary > packages is no longer allowed. Packages with these changes will not > be allowed to migrate to testing. These changes are also no longer > appropriate in unstable. > ... > > > The problem is that opening of #1030749 is de facto > a request-tracker4 -> request-tracker5 transition that > happened 4 weeks after the deadline for transitions. The soft freeze date snuck up on us. :( Given the minimal impact to packages, is this a transition? If you look at the release and EOL dates on https://bestpractical.com/release-policy/ you'll see that Best Practical typically end of life releases 3-4 years after the next release. 5.0 was released in 2020, therefore it is worth considering that 4.4 will most likely be EOL in 2023 or 2024. For practical support reasons, we're concerned about releasing Bookworm with 4.4. > There are two options for resolving this: > 1. Treat #1030749 as a forbidden transition and ship both versions > of request-tracker in bookworm, or > 2. grant reverse dependencies an exception from the soft freeze > rules for the request-tracker4 -> request-tracker5 transition. > > > For option 2 I looked at the 9 reverse dependencies of request- > tracker4 > in the autoremoval list: > > RT extension installer that has to stop depending on > both versions: > - libmodule-install-rtx-perl This will need to updated after all the below packages are updated. > No package remame required, has to upgrade to the upstream version > that supports request-tracker5: > - librt-extension-commandbymail-perl We've had updated packaging ready to go for a while, but it looks like we'd forgotten to upload it. Current proposed package does introduce new packages, but we could drop that and re-use the existing package name. > Ships packages for both versions and has to drop the > request-tracker4 package: > - rt-extension-assets-import-csv > > request-tracker4 -> request-tracker5 transition prepared > in experimental: > - rt-extension-customfieldsonupdate > - rt-extension-calendar > - rt-extension-jsgantt > - rt-extension-nagios > - rt-extension-smsnotify Some of these will need to be updated, but that is relatively straightforward. > Update to latest upstream version and package rename required: > - rt-extension-repeatticket Again, we have updated packaging ready, again includes new package names. But the splitting into new packages can be dropped. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1029342: Fixed version of request-tracker5 released
Hi bert, Thank you for the detailed information, and the TL;DR;. I now have a working version of the request-tracker5 package, which I've just uploaded to unstable. So, our immediate concern is resolved. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1011845: FTBFS: make[1]: *** [Makefile:272: testdeps] Error 1
Hey Lucas, I expect the the output from rt-test-dependencies in this case is a false lead. I believe this is actually caused by the update of OpenSSL to 3.0 causing one of the tests to fail. I filed a bug for this yesterday: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013730 . Today I happened update our packaging to resolve the dependencies issue as mentioned in this bug report. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#1013730: FTBFS: S/MIME test fails with OpenSSL 3.0
Package: request-tracker4 Version: 4.4.5+dfsg-1 Severity: serious Tags: ftbfs upstream Justification: fails to build from source To preempt other people reporting this. The unit test t/mail/smime/realmail.t fails with OpenSSL 3.0.x due to DES being deprecated and the sample emails used by the test use DES. I have a fix for this, but I want to hear from upstream first as I'm not convinced that enabling DES is the correct approach. This issue is also in 5.0-trunk. Cheers, Andrew -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages request-tracker4 depends on: ii dbconfig-common 2.0.21 ii debconf [debconf-2.0]1.5.79 ii fonts-droid-fallback 1:6.0.1r16-1.1 ii fonts-noto-hinted20201225-1 ii libapache-session-perl 1.94-1 ii libbusiness-hours-perl 0.13-1 ii libcgi-emulate-psgi-perl 0.23-2 ii libcgi-pm-perl 4.54-1 ii libcgi-psgi-perl 0.15-3 ii libclass-accessor-perl 0.51-1 ii libclone-perl0.45-1+b2 ii libconvert-color-perl0.12-1 ii libcpanel-json-xs-perl 4.29-1 ii libcrypt-eksblowfish-perl0.009-3 ii libcrypt-x509-perl 0.54-1 ii libcss-minifier-xs-perl 0.13-1+b1 ii libcss-squish-perl 0.10-1 ii libdata-guid-perl0.050-1 ii libdata-ical-perl0.24+dfsg-1 ii libdata-page-pageset-perl1.02-2 ii libdate-extract-perl 0.06-2 ii libdate-manip-perl 6.88-1 ii libdatetime-format-natural-perl 1.13-1 ii libdatetime-locale-perl 1:1.35-1 ii libdatetime-perl 2:1.57-1 ii libdbi-perl 1.643-3+b2 ii libdbix-searchbuilder-perl 1.71-2 ii libdevel-globaldestruction-perl 0.14-2 ii libemail-address-list-perl 0.06-1 ii libemail-address-perl1.912-1 ii libencode-perl 3.17-1 ii libfile-sharedir-perl1.118-1 ii libfile-which-perl 1.27-1 ii libgd-graph-perl 1.54~ds-3 ii libgd-text-perl 0.86-10 ii libgnupg-interface-perl 1.02-1 ii libgraphviz-perl 2.24-1 ii libhtml-formattext-withlinks-andtables-perl 0.07-2 ii libhtml-formattext-withlinks-perl0.15-2 ii libhtml-gumbo-perl 0.18-2+b4 ii libhtml-mason-perl 1:1.59-1 ii libhtml-mason-psgihandler-perl 0.53-2 ii libhtml-quoted-perl 0.04-2 ii libhtml-rewriteattributes-perl 0.05-2 ii libhtml-scrubber-perl0.19-1 ii libhttp-message-perl 6.37-1 ii libipc-run-perl 20200505.0-1 ii libipc-run3-perl 0.048-2 ii libjavascript-minifier-xs-perl 0.15-1+b1 ii libjson-perl 4.06000-1 ii liblist-moreutils-perl 0.430-2 ii liblocale-maketext-fuzzy-perl0.11-2 ii liblocale-maketext-lexicon-perl 1.00-2 ii liblog-dispatch-perl 2.70-1 ii libmailtools-perl2.21-1 ii libmime-tools-perl 5.509-2 ii libmime-types-perl 2.22-1 ii libmodule-refresh-perl 0.18-1 ii libmodule-versions-report-perl 1.06-3 ii libnet-cidr-perl 0.21-1 ii libnet-ip-perl 1.26-2 ii libnet-ldap-perl 1:0.6800+dfsg-1 ii libnet-ssleay-perl 1.92-2 ii libperlio-eol-perl 0.17-2 ii libplack-perl1.0048-1 ii libregexp-common-net-cidr-perl 0.03-1 ii libregexp-common-perl2017060201-2 ii libregexp-ipv6-perl 0.03-3 ii librole-basic-perl 0.13-3 ii
Bug#874257: Fixed now?
Hey, I have tested rt-dump-metadata against a copy of our production installation which has a large number of CustomFields running RT 4.4.4. This appears to work correctly now. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#765872: Repeating request
Hey, If we had /etc/rkhunter.d present, then other packages (like etckeeper) could deploy config snippets into there to ignore their files. In the case of etckeeper: ALLOWHIDDENFILE=/etc/.gitignore ALLOWHIDDENFILE=/etc/.etckeeper ALLOWHIDDENDIR=/etc/.git Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#932594: Handle /usr/bin/egrep etc
Hey, I have just spent a little bit of time digging into this, as I want rkhunter to work (almost) turnkey, without needing users to have to customise any configuration files. In answer to John, sadly EXISTWHITELIST doesn't handle this situation, it says that the the listed files/directories don't need to exist. However we need to tell rkhunter that egrep and fgrep are allowed to be scripts. My approach has been two fold so far, and this feels really really ugly, but, oh well. If we modify /etc/default/rkhunter then it can modify /etc/rkhunter.conf before we run rkhunter via either cron or apt. So even if there is a transient change, it'll get picked up and corrected eventually. I added this to /etc/default/rkhunter.conf (I also made it handle lwp-request being present, since I hit that as well): -- BEGIN -- # Okay, this is ugly, modify rkhunter.conf to be able to know where fgrep and # egrep are. See https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=932594 if [ -f /bin/fgrep ] then if $(grep -q "SCRIPTWHITELIST=/usr/bin/egrep" /etc/rkhunter.conf) then sed -i 's,^SCRIPTWHITELIST=/usr/bin/fgrep,SCRIPTWHITELIST=/bin/fgrep,' \ /etc/rkhunter.conf sed -i 's,^SCRIPTWHITELIST=/usr/bin/egrep,SCRIPTWHITELIST=/bin/egrep,' \ /etc/rkhunter.conf fi elif [ -f /usr/bin/fgrep ] then if $(grep -q "SCRIPTWHITELIST=/bin/egrep" /etc/rkhunter.conf) then then sed -i 's,^SCRIPTWHITELIST=/bin/fgrep,SCRIPTWHITELIST=/usr/bin/fgrep,' \ /etc/rkhunter.conf sed -i 's,^SCRIPTWHITELIST=/bin/egrep,SCRIPTWHITELIST=/usr/bin/egrep,' \ /etc/rkhunter.conf fi fi # If lwp-request is present, then we need SCRIPTWHITELIST for it. if [ -f /usr/bin/lwp-request ] if $(grep -q "^#SCRIPTWHITELIST=/usr/bin/lwp-request" /etc/rkhunter.conf) sed -i 's,^#\(SCRIPTWHITELIST=/usr/bin/lwp-request\),\1,' \ /etc/rkhunter.conf fi fi -- END -- Then in /usr/share/rkhunter/scripts/rkhupd.sh we add near the top: -- BEGIN -- . /etc/default/rkhunter -- END -- I'm sorry. -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#972985: Missed bullseye
Just for anyone else who looks at this bug report, unfortunately it wasn't included in Bullseye. -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#987779: fai-server: fai-cd generates ISO images which can't renew a DHCP lease during build
Package: fai-server Version: 5.10.2 Severity: normal Dear Maintainer, As requested by Thomas, I'm creating this bug report following a post on the mailing list. When fai-cd builds a bootable ISO image, Dracut acts as a DHCP client, but is a single shot only and doesn't continue to run. Once the DHCP lease expires nothing on the machine being built renews the lease. On a PXE boot installation, the Linux kernel takes care of the DHCP lease renewal for us. Ideally FAI would start dhclient - if required - to ensure that DHCP leases are renewed as required. This can be a difficult situation to diagnose, because if you're using an NFSROOT, once the IP expires and is removed the system effectively hangs. Cheers, Andrew -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fai-server depends on: ii debootstrap 1.0.123 ii e2fsprogs1.46.2-1 ii fai-client 5.10.2 ii xz-utils 5.2.5-2 Versions of packages fai-server recommends: ii dosfstools4.2-1 pn isc-dhcp-server ii libproc-daemon-perl 0.23-1 ii mtools4.0.27-1 pn nfs-kernel-server ii openbsd-inetd [inet-superserver] 0.20160825-5 ii openssh-client1:8.4p1-5 ii openssh-server1:8.4p1-5 pn tftpd-hpa | atftpd Versions of packages fai-server suggests: ii binutils 2.35.2-2 pn debmirror ii fai-setup-storage 5.10.2 pn grub2 ii perl-tk1:804.035-0.1+b1 ii qemu-utils 1:5.2+dfsg-10 pn reprepro ii squashfs-tools 1:4.4-2 ii xorriso1.5.2-1 -- Configuration Files: /etc/fai/NFSROOT changed [not included] /etc/fai/apt/sources.list changed [not included] /etc/fai/nfsroot.conf changed [not included] -- no debconf information
Bug#986981: libreoffice-writer: Input freezes while auto-save occurs
Package: libreoffice-writer Version: 1:7.0.4-3 Severity: normal Dear Maintainer, Very recently I have noticed that while LibreOffice Writer is auto-saving a document, focus of the window is lost, and anything that is typed goes ... who knows where? When the auto-save is complete focus is returned to the Writer window. This is incredibly off-putting! This didn't use to be the case, unfortunately I can't pin-point this to a time or version when it started happening. Cheers, Andrew -- System Information: Debian Release: bullseye/sid APT prefers common APT policy: (500, 'common'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=UTF-8) (ignored: LC_ALL set to en_NZ.UTF-8), LANGUAGE=en_NZ:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice depends on: ii libreoffice-base1:7.0.4-3 ii libreoffice-calc1:7.0.4-3 ii libreoffice-core1:7.0.4-3 ii libreoffice-draw1:7.0.4-3 ii libreoffice-impress 1:7.0.4-3 ii libreoffice-math1:7.0.4-3 ii libreoffice-report-builder-bin 1:7.0.4-3 ii libreoffice-writer 1:7.0.4-3 ii python3-uno 1:7.0.4-3 Versions of packages libreoffice recommends: ii fonts-crosextra-caladea 20130214-2.1 ii fonts-crosextra-carlito 20130920-1.1 ii fonts-dejavu2.37-2 ii fonts-liberation1:1.07.4-11 ii fonts-liberation2 2.1.2-2 ii fonts-linuxlibertine5.3.0-6 ii fonts-noto-core 20201225-1 ii fonts-noto-extra20201225-1 ii fonts-noto-mono 20201225-1 ii fonts-noto-ui-core 20201225-1 ii fonts-sil-gentium-basic 1.102-1.1 ii libreoffice-java-common 1:7.0.4-3 ii libreoffice-nlpsolver 0.9+LibO7.0.4-3 ii libreoffice-report-builder 1:7.0.4-3 ii libreoffice-script-provider-bsh 1:7.0.4-3 ii libreoffice-script-provider-js 1:7.0.4-3 ii libreoffice-script-provider-python 1:7.0.4-3 ii libreoffice-sdbc-mysql 1:7.0.4-3 ii libreoffice-sdbc-postgresql 1:7.0.4-3 ii libreoffice-wiki-publisher 1.2.0+LibO7.0.4-3 Versions of packages libreoffice suggests: ii cups-bsd2.3.3op2-3 ii default-jre [java8-runtime] 2:1.11-72 ii firefox-esr 78.9.0esr-1 ii ghostscript 9.53.3~dfsg-7 ii gnupg 2.2.27-1 pn gpa ii gstreamer1.0-libav 1:1.18.4-dmo1 ii gstreamer1.0-plugins-bad1:1.18.4-dmo3 ii gstreamer1.0-plugins-base 1.18.4-dmo1 ii gstreamer1.0-plugins-good 1.18.4-dmo1 ii gstreamer1.0-plugins-ugly 1:1.18.4-dmo1 pn hunspell-dictionary ii hyphen-pt-pt [hyphen-hyphenation-patterns] 1:7.1.0~rc3-3 ii imagemagick 8:6.9.11.60+dfsg-1 ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1 ii libgl1 1.3.2-1 pn libofficebean-java ii libreoffice-gnome 1:7.0.4-3 pn libreoffice-grammarcheck pn libreoffice-help pn libreoffice-l10n ii libreoffice-librelogo 1:7.0.4-3 ii libsane11.0.31-4 ii libxrender1 1:0.9.10-1 ii myspell-en-nz [myspell-dictionary] 20160923-1 ii myspell-mi-nz [myspell-dictionary] 20160923-1 pn mythes-thesaurus pn openclipart2-libreoffice | openclipart-libreoffice ii openjdk-11-jre [java8-runtime] 11.0.11+4-1 ii openjdk-8-jre [java8-runtime] 8u222-b10-1~deb9u1 pn pstoedit pn unixodbc Versions of packages libreoffice-core depends on: ii fontconfig 2.13.1-4.2 ii fonts-opensymbol2:102.11+LibO7.0.4-3 ii libboost-locale1.74.0 1.74.0-9 ii libc6 2.31-11 ii libcairo2 1.16.0-5 ii libclucene-contribs1v5 2.3.3.4+dfsg-1+b1 ii libclucene-core1v5 2.3.3.4+dfsg-1+b1 ii libcmis-0.5-5v5
Bug#985374: error: embedding is not possible - RAID+LVM+ext4
Package: grub-pc Version: 2.04-16 Severity: important Dear Maintainer, grub-pc 2.04-16 is unable to embed core.img on my machine (I install on two hard drives): Setting up grub-pc (2.04-16) ... Installing for i386-pc platform. grub-install: warning: your core.img is unusually large. It won't fit in the embedding area. grub-install: error: embedding is not possible, but this is required for RAID and LVM install. Installing for i386-pc platform. grub-install: warning: your core.img is unusually large. It won't fit in the embedding area. grub-install: error: embedding is not possible, but this is required for RAID and LVM install. * What led up to the situation? Running an apt upgrade that upgrades from version 2.04-15 to 2.04-16. * What exactly did you do (or not do) that was effective (or ineffective)? To enable embedding of the core.img I have to downgrade to 2.04-15. There are a number of these types of bug reports, but it appears that different versions of grub-pc tend to trigger them, so I decided to submit a new bug report. Please feel free to merge this one if that is an appropriate action to take. Cheers, Andrew -- Package-specific info: *** BEGIN /proc/mounts /dev/md3 / ext3 rw,relatime,errors=remount-ro 0 0 /dev/VG/VG-usr /usr ext3 rw,relatime 0 0 /dev/mapper/VG-tmp /tmp ext2 rw,relatime 0 0 /dev/mapper/VG-srv /srv ext4 rw,relatime 0 0 /dev/md0 /boot ext2 rw,relatime 0 0 /dev/mapper/VG-VG--scratch /scratch ext3 rw,relatime 0 0 /dev/mapper/VG-VG--var /var ext3 rw,relatime 0 0 /dev/mapper/VG-VG--home /home ext3 rw,relatime 0 0 /dev/mapper/VG-VG--home /var/lib/schroot/union/underlay/sid-amd64-sbuild-1a304339-632f-4334-aadb-fe415d5e8910 ext3 rw,relatime 0 0 /dev/mapper/VG-VG--var /run/schroot/mount/sid-amd64-sbuild-1a304339-632f-4334-aadb-fe415d5e8910/build ext3 rw,relatime 0 0 /dev/mapper/VG-VG--home /var/lib/schroot/union/underlay/sid-amd64-sbuild-20b67ce0-f23f-4f47-9247-fda7c0d92b13 ext3 rw,relatime 0 0 /dev/mapper/VG-VG--var /run/schroot/mount/sid-amd64-sbuild-20b67ce0-f23f-4f47-9247-fda7c0d92b13/build ext3 rw,relatime 0 0 /dev/mapper/VG-VG--home /var/lib/schroot/union/underlay/sid-amd64-sbuild-9769b236-5aa6-4518-a77c-2d67f8c7c9d2 ext3 rw,relatime 0 0 /dev/mapper/VG-VG--var /run/schroot/mount/sid-amd64-sbuild-9769b236-5aa6-4518-a77c-2d67f8c7c9d2/build ext3 rw,relatime 0 0 /dev/mapper/VG-VG--home /var/lib/schroot/union/underlay/sid-amd64-sbuild-e1eecccb-36e8-4691-82ab-2da987405a3c ext3 rw,relatime 0 0 /dev/mapper/VG-VG--var /run/schroot/mount/sid-amd64-sbuild-e1eecccb-36e8-4691-82ab-2da987405a3c/build ext3 rw,relatime 0 0 *** END /proc/mounts *** BEGIN /boot/grub/device.map (hd0) /dev/disk/by-id/raid-VG-VG--usr (hd1) /dev/disk/by-id/raid-VG-VG--var (hd2) /dev/disk/by-id/raid-VG-VG--home (hd3) /dev/disk/by-id/raid-VG-VG--scratch (hd4) /dev/disk/by-id/raid-VG-tmp (hd5) /dev/disk/by-id/raid-VG-vservers (hd6) /dev/disk/by-id/raid-VG- (hd7) /dev/disk/by-id/raid-VG-fai--test (hd8) /dev/disk/by-id/raid-VG-test--vm--0 (hd9) /dev/disk/by-id/lvm-pv-uuid-OUObOt-SilW-Hg30-7J5H-uso3-Ychn-C2FVR2 (hd10) /dev/disk/by-id/lvm-pv-uuid-YlRE7l-bTvN-38yC-ZTm2-innD-eBq8-RCY9qE (hd11) /dev/disk/by-id/lvm-pv-uuid-wzHKWm-0CjU-gYzN-RHR9-G2OK-sV5J-WXDId1 (hd12) /dev/disk/by-id/ata-WDC_WD10EZEX-00WN4A0_WD-WMC6Y0F2J3F4 (hd13) /dev/disk/by-id/ata-WDC_WD10EZEX-00WN4A0_WD-WMC6Y0F3KFHN *** END /boot/grub/device.map *** BEGIN /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then set have_grubenv=true load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="0" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod lvm insmod ext2 set root='lvmid/uFGFNk-DXwp-6J4A-CrZO-FBZL-mty4-zuU4x7/ooLKhD-MI2u-ReeZ-1VAb-E3YV-gd6T-wuNt1t' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root
Bug#983752: request-tracker5.service uses /usr/bin/true, which isn't present on all systems
Package: request-tracker5 Version: 5.0.1+dfsg-1 Severity: important Dear Maintainer, The request-tracker5 service file uses /usr/bin/true, on some Debian systems this doesn't exist, and is actually located in /bin/true . The cloud image I used for testing this has /bin symlinked to /usr/bin. #sigh Andrew
Bug#981647: libgnupg-interface-perl 1.01 breaks ssh-agent msva-perl ...
On Wed, 2021-02-10 at 22:01 +, Dominic Hargreaves wrote: > On Sun, Feb 07, 2021 at 11:42:43PM +, Dominic Hargreaves wrote: > > Andrew, was this intentional? Maybe we should just restore that > > part > > of the patch? > > Ah, I expect the change to /usr/bin/gpg was lost when applying an > altered upstream version of the patch. So my tentative fix > was correct and just the previous behaviour, with the upstream > changes and the Debian-specific changes now in separate files. > Uploaded. You are correct, that was accidental while I was updating the patches. You fix looks correct to me. Thank you! Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#982202: ITP: libmodule-install-substitute-perl -- Module::Install::Substitute - substitute values into files before install
Hi Dominic, I built this package and it was uploaded last year on bug 975956. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
Bug#846029: [request-tracker-maintainers] Bug#846029: Bug#846029: request-tracker4: uses deprecated gpg1
Hey, On Mon, 2021-01-04 at 11:03 +, Dominic Hargreaves wrote: > On Tue, Dec 15, 2020 at 10:47:30PM +0100, Chris Hofstaedtler wrote: > > > Maybe its time to switch RT4 to gnupg2? > > Andrew: I think that this just means replicating the changes you made > in RT5 to drop the gpg1 patches and update the dependency? Do you > foresee > any issues with this? The changes I made for our RT5 packaging are already in the RT4 branch. I think we should be safe to switch RT to using gnupg2. This will probably require a note in debian/NEWS as people may need to update how they handle gpg passphrases. The only dependency change we need to make is Build-Depends. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz| linux.conf.au 2020, Gold Coast, AU https://catalystcloud.nz | https://lca2020.linux.org.au
Bug#975956: ITP: libmodule-install-substitute-perl -- substitute values into files before install
Package: wnpp Severity: wishlist Owner: Andrew Ruthven X-Debbugs-Cc: debian-de...@lists.debian.org Package name: libmodule-install-substitute-perl Version : 0.03 Upstream Author : Ruslan U. Zakirov URL : http://www.example.org/ License : Artistic or GPL-1+ Programming Lang: Perl Description : substitute values into files before install This is extension for Module::Install system that allow you to substitute values into files before install, for example paths to libs or binary This package is used during the build stage of a number of Request Tracker extensions which I'm in the process of updating in preparation of Bullseye and the Request Tracker 5.0 release. I intend to have this package within the Perl Team.
Bug#972847: libdbd-pg-perl: last_insert_id doesn't work against PostgreSQL 12 (or greater)
Package: libdbd-pg-perl Version: 3.7.4-3 Severity: important Dear Maintainer, The version of DBD::Pg in Buster (and earlier) is incompatible with PostgreSQL 12 (or greater) if the application code using DBD::Pg uses the last_insert_id function. The last_insert_id method uses the pg_attrdef.adsrc column which was removed in Pg 12 (search for adsrc): https://www.postgresql.org/docs/12/release-12.html DBD::Pg removed the usage of pg_attrdef.adsrc in version 3.8.0 with commit: 88d2f8f1fc95bcd16e95d3fc667783fb7a9ab05b I've set this as important as it may affect people running PostgreSQL from the pgdg repos provided by PostgreSQL. This bug shouldn't affect bullseye which currently has version 3.14.2. Cheers, Andrew -- System Information: Debian Release: 10.6 APT prefers common APT policy: (500, 'common'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.227-vs2.3.9.12-beng (SMP w/8 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=UTF-8) (ignored: LC_ALL set to en_NZ.UTF-8), LANGUAGE=en_NZ:en (charmap=UTF-8) (ignored: LC_ALL set to en_NZ.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libdbd-pg-perl depends on: ii libc6 2.28-10 ii libdbi-perl [perl-dbdabi-94] 1.642-1+deb10u1 ii libpq511.9-0+deb10u1 ii perl 5.28.1-6+deb10u1 ii perl-base [perlapi-5.28.1]5.28.1-6+deb10u1 libdbd-pg-perl recommends no packages. libdbd-pg-perl suggests no packages. -- no debconf information
Bug#969401: Fixed upstream
Hey, First, apologies for including the template text - it was off the bottom of my editor and I forgot to remove it. This is fixed upstream in commit 18edc98f9d08883f340087cfefbdf05c585d56f7 which is in B.02.19 . It also fixes the 'Unknown' string which I have observed on one of my machines. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud:| This space intentionally left blank https://catalystcloud.nz|
Bug#969401: lshw: -version parameter prints blank line only
Package: lshw Version: 02.18.85-0.1 Severity: normal Dear Maintainer, Running lshw with the -version parameter should display the version of lshw, instead it displays a blank line. For example: puck@flick:~$ lshw -version puck@flick:~$ Testing this on Stretch with lshw v 02.18-0.1, it works. This also affects Ubuntu Focal (02.18.85-0.3ubuntu2), it works okay on Bionic (02.18-0.1ubuntu6.18.04.1), I haven't checked any non-LTS Ubuntu releases. Cheers, Andrew *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers common APT policy: (500, 'common'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=UTF-8) (ignored: LC_ALL set to en_NZ.UTF-8), LANGUAGE=en_NZ:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lshw depends on: ii libc6 2.31-3 ii libgcc-s1 10.2.0-5 ii libstdc++6 10.2.0-5 Versions of packages lshw recommends: ii pciutils 1:3.7.0-2 ii usbutils 1:012-2 lshw suggests no packages. -- no debconf information
Bug#967017: [request-tracker-maintainers] Bug#967017: Bug#967017: request-tracker4: FTBFS: can't exec /usr/bin/gpg
On Mon, 2020-08-03 at 15:48 +0100, Dominic Hargreaves wrote: > This seems related to changes in libgnupg-interface-perl, which on > the > face of it is ignoring the instruction to use 'gpg1' (configured via > the test_gnupg_interface_gpg1.diff patch). I can't immediately see > why > that's happening but it seems related to the recent changes > libgnupg-interface-perl. > > Andrew, any clues? Yes, this is related. I hadn't spotted it because I have both gpg and gpg1 installed on my workstation. If gpg isn't present, then I can reproduce this. The issue is with how GnuPG::Interface checks for the version of the gpg binary that is being run. A minor change to RT::Crypt::GnuPG in RT fixes this. I've written the patch to resolve this bug, pushed it to Salsa and raised a bug with Best Practical: https://rt.bestpractical.com/SelfService/Display.html?id=36623 I also find it a little puzzling though, I've checked the source in unstable and the patch name is test_gnupg-interface_gpg1.diff but the name of the patch used in the build log is test_gnupg- interface_gnupg.diff . This isn't in git, bullseye or unstable. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud:| This space intentionally left blank https://catalystcloud.nz|
Bug#964878: GnuPG::Interface doesn't work with Taint mode
Hey, Because of the use of "exec", GnuPG::Interface isn't Taint safe. I've prepared a patch and will hopefully have it uploaded soon. Reported upstream with a patch here: https://rt.cpan.org/Ticket/Display.html?id=133041 . Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud:| This space intentionally left blank https://catalystcloud.nz|
Bug#964879: [request-tracker-maintainers] Bug#964879: Bug#964879: request-tracker4: FTBFS: broken by libgnupg-interface-perl
Hey, It took a bit of digging. This is caused by an interaction between RT and GnuPG::Interface. I believe that RT is using the GnuPG::Interface correctly. GnuPG::Interface knows the version of the GPG binary being used, and uses the --pinentry-mode argument if that is supported - which needs gpg v2.2. If the binary is changed after the object has been instantiated then the version isn't changed. I've updated our libgnupg-interface-perl with a patch to fix this, and submitted it upstream here: https://rt.cpan.org/Ticket/Display.html?id=133021 Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud:| This space intentionally left blank https://catalystcloud.nz|
Bug#964879: [request-tracker-maintainers] Bug#964879: request-tracker4: FTBFS: broken by libgnupg-interface-perl
Hmmm, this is likely a bug in libgnupg-interface-perl v1.00. It should be able to work with both gpg v1 and v2.4, and certainly as I was reviewing the packaging for v1.00 it certainly tries to. Our RT v4.4.4 packages are forcing the use of gpg v1. I'll have a look at libgnupg-interface-perl tonight. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud:| This space intentionally left blank https://catalystcloud.nz|
Bug#887551: Updated Email::Address
Hey, Email::Address is now maintained again. 1.910 fixed CVE-2015-7686, Buster and newer have 1.912, the fix was backported to Stretch. Best Practical have stated they won't switch to Email::Address::XS. Can we close this bug? Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud:| This space intentionally left blank https://catalystcloud.nz|
Bug#963946: ITP: libpath-dispatcher-perl -- flexible and extensible dispatcher module
Package: wnpp Severity: wishlist Owner: Andrew Ruthven * Package name: libpath-dispatcher-perl Version : 1.07 Upstream Author : Shawn M Moore * URL : https://metacpan.org/pod/Path::Dispatcher * License : GPL v1+ or Artistic License Programming Lang: Perl Description : flexible and extensible dispatcher module Path::Dispatcher is a Perl module that allows a program to determine which code to execute by matching a path against a list of rules. Dispatch takes a path and returns a list of matches; from there, you can "run" the rules that matched. Developers may also inspect which rules were matched without executing their codeblocks. This package is a dependency on the upcoming Request Tracker 5 release. It has been in Debian in the past but was removed for Buster due to a dependency on a deprecated package[0]. Path::Dispatcher has since been updated to remove that dependency. The Debian Perl Group will maintain this package. Updated packaging for Debian is here: https://salsa.debian.org/perl-team/modules/packages/libpath-dispatcher-perl Cheers, Andrew [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845804
Bug#960896: ITP: rt4-extension-assetautoname -- AssetAutoName extension (Request Tracker)
Package: wnpp Severity: wishlist Owner: Andrew Ruthven * Package name: rt4-extension-assetautoname Version : 0.02 Upstream Author : Andrew Ruthven * URL : https://metacpan.org/release/RT-Extension-AssetAutoName * License : GPL-2 Programming Lang: Perl Description : AssetAutoName extension (Request Tracker) This extension adds automatic asset name generation from other fields to Request Tracker. This package will be part of the request-tracker-maintainers team. We use it as work, and it has proven useful to other folks as well. I found I hadn't uploaded it to CPAN, I've just uploaded it, it hasn't been processed yet.
Bug#960895: ITP: rt-extension-elapsedbusinesstime -- ElapsedBusinessTime extension (Request Tracker)
Package: wnpp Severity: wishlist Owner: Andrew Ruthven * Package name: rt-extension-elapsedbusinesstime Version : 0.03 Upstream Author : Andrew Ruthven * URL : https://metacpan.org/release/RT-Extension-ElapsedBusinessTime * License : GPL-2 Programming Lang: Perl Description : ElapsedBusinessTime extension (Request Tracker) This extension adds a fields for elapsed business time (general, and forced into hours or minutes) in reports for tickets within Request Tracker. This package will be maintained by the request-tracker-maintainers team. We use this package at work, and there other Request Tracker installations using it.
Bug#886525: ITP: rt4-extension-mergeusers -- Merge users (Request Tracker)
Hey Gabriel, I don't have a readily available .deb, but I can provide if you want. Otherwise the git repo is on Salsa and you can just build one yourself. https://salsa.debian.org/request-tracker-team/rt-extension-mergeusers Cheers, Andrew On Sun, 2020-05-10 at 14:12 -0400, Gabriel Filion wrote: > Hello, > > On Sun, 07 Jan 2018 23:39:36 +1300 Andrew Ruthven > wrote: > > Package: wnpp > > Severity: wishlist > > Owner: Andrew Ruthven > > > > * Package name: rt4-extension-mergeusers > > Version : 1.03 > > Upstream Author : Best Practical Solutions, LLC < > > modu...@bestpractical.com> > > * URL : > > https://metacpan.org/release/RT-Extension-MergeUsers > > * License : GPL v2 > > Programming Lang: Perl > > Description : Merge users (Request Tracker) > > > > This extension allows merging users in Request Tracker. > > > > You always end up with duplicate users in a ticketing system since > > people > > use different email addresses. This extension provides a mechanism > > to > > manage that better. > > > > The intial packaging work has been carried but by myself for my > > employer. > > Ongoing maintenance will be by the Debian Request Tracker Group (of > > which > > I'm a member). > > I'm quite interested in seeing this extension packaged in debian. Do > you > have your packaging work published somewhere that I could retrieve? > -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2021, Canberra, AU Catalyst Cloud:| http://lca2021.linux.org.au/ https://catalystcloud.nz|
Bug#894998: ITP: rt4-extension-rest2 -- REST2 API extension (Request Tracker)
Hey Gabriel, You can fetch a .deb from: http://mirror.catalyst.net.nz/catalyst/debian/dists/jessie/request-tracker/binary-all/rt4-extension-rest2_1.08c-1_all.deb The "debian" branch is here: https://github.com/catalyst-cloud/rt-extension-rest2/commits/debian Upstream is about to release v 1.09 which includes a number of features I've added. Once that is released, then I'll build an updated package. If someone is prepared to sponsor it (I'm a DM, not a DD), then I' happy to load it. Cheers, Andrew On Sun, 2020-05-10 at 14:11 -0400, Gabriel Filion wrote: > Hello, > > On Fri, 06 Apr 2018 14:57:30 +1200 Andrew Ruthven > wrote: > > Package: wnpp > > Severity: wishlist > > Owner: Andrew Ruthven > > > > * Package name: rt4-extension-rest2 > > Version : 1.03 > > Upstream Author : Best Practical Solutions < > > modu...@bestpractical.com> > > * URL : https://metacpan.org/release/RT-Extension-REST2 > > * License : GPLv2 > > Programming Lang: Perl > > Description : REST2 API extension (Request Tracker) > > > > This extension adds a modern REST API to Request Tracker. > > > > The existing API for RT is a rather painful RFC822 (yes email) > > based > > system via HTTP. This extension provides a much nicer JSON based > > RESTful > > interface. > > > > The intial packaging work has been carried but by myself for my > > employer. > > Ongoing maintenance will be by the Debian Request Tracker Group (of > > which > > I'm a member). > > I'm quite interested in seeing this extension packaged in debian. Do > you > have your packaging work published somewhere that I could retrieve? > -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2021, Canberra, AU Catalyst Cloud:| http://lca2021.linux.org.au/ https://catalystcloud.nz|
Bug#940167: Limitation on VG name in setup-storage?
Hi Thomas, Looking at the disk_config file again, I'm not actually making any LVs inside the VG (they're made later when KVM instances are spun on up on these machines). Removing \- works okay for creating a VG with a hyphen in the name. Cheers, Andrew On Fri, 2019-09-13 at 11:45 +0200, Thomas Lange wrote: > Hi Andrew, > > you've said that removing \- from the regex works for you. I cannot > reproduce this. When I use a vg name like vg-ssd7 I get the error > > ERROR (line 13): Invalid volume: Was expecting /^vg\s+/, or >/^raid([0156]|10)\s+/, or /^btrfs >(single|raid([0156]|10))\s+/, or >/^(luks|luks:"[^"]+"|tmp|swap)\s+/, or > /^tmpfs\s+/, or >/^nfs\s+([^\s]+)\s+/, or type > > ERROR (line 13): Invalid line: Was expecting '\n' but found "vg-ssd7- > root / 3G-25G ext4 noatime,rw" instead > > > Can you please send me your disk_config that is working for you using > a hyphen. > -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2020, Gold Coast, AU Catalyst Cloud:|https://lca2020.linux.org.au/ https://catalystcloud.nz|
Bug#926424: cloud-init: No log rotation
Package: cloud-init Version: 18.3 Severity: wishlist Tags: patch Dear Maintainer, The cloud-init system logs to the follow files: - /var/log/cloud-init-output.log - /var/log/cloud-init.log There is nothing shipped which rotates these log files, which is a shame as they'll grow everytime an instance is rebooted. We have some customers with reasonably large log files now... Please find attached a proposed logrotate file. Cheers, Andrew *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-trunk-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cloud-init depends on: ii cloud-guest-utils 0.29-1 ii fdisk 2.33.1-0.1 ii gdisk 1.0.3-1.1 ii ifupdown0.8.35 ii locales 2.28-8 ii lsb-base10.2019031300 ii lsb-release 10.2019031300 ii net-tools 1.60+git20180626.aebd88e-1 ii procps 2:3.3.15-2 ii python3 3.7.3-1 pn python3-configobj ii python3-jinja2 2.10-1 pn python3-jsonpatch pn python3-jsonschema pn python3-oauthlib ii python3-requests2.21.0-1 ii python3-six 1.12.0-1 ii python3-yaml3.13-2 ii util-linux 2.33.1-0.1 Versions of packages cloud-init recommends: ii eatmydata 105-7 ii sudo 1.8.27-1 Versions of packages cloud-init suggests: ii btrfs-progs 4.20.2-1 ii e2fsprogs1.45.0-1 ii xfsprogs 4.20.0-1 /var/log/cloud-init.log /var/log/cloud-init-output.log { weekly rotate 4 compress delaycompress missingok notifempty }
Bug#919271: base-files: Provide easy access to motd
reassign 919271 debianutils thanks Hey, On Mon, 2019-01-14 at 12:47 +0100, Santiago Vila wrote: > > Since we've started having dynamic generation of the system MOTD, > > re-displaying it is hard. Especially if people are using SSH > > connection > > sharing. > > I have some buster machines at work and the motd is displayed when I > ssh into them. Did this problem you mention start to happen recently? > > Also, you will not want the motd to be shown on ordinary ssh > commands, > will you? > > ssh remote-machine ls > list-of-files.txt > > (I assume this is not what you want). Sorry, this isn't an ssh related request. I have the motd displayed when on my first connection to a remote system for an interactive shell. My comment about ssh was merely that to see the motd again you need to login again, potentially removing the ControlMaster file for the remote machine you're logging into. Before we had dynamic motd generation, if something was modifying the motd file, you could just cat /etc/motd to see the contents. It is no longer so trivial. > > How about a /bin/motd (or /usr/bin) command which runs the > > following: > > > > run-parts /etc/update-motd.d; cat /etc/motd > > Hmm, no, no binaries in the base-files package, please. > This is already supposed to be handled by some PAM setting at > /etc/pam.d. Yes, it is currently happening via a PAM module. When you first enter an interactive session. > See this bug for some details: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859124 > > (This is the bug which asked me to introduce 10-uname as a sane > default to recover the old behaviour). > > > I've filed this bug report against base-files as this package > > delivers > > /etc/update-motd.d/10-uname. > > This is just a hook so that other parts of the system do something > with it, it does not mean that base-files takes care of the run-parts > thing. Okay, fair enough. > > Incidentally, the description for base-files says that it delivers > > /etc/motd, which it doesn't anymore. > > It is still true that base-files contains the "master" default > i.e. "The programs included with the Debian GNU/Linux system are free > software. etc" but everything else is handled in other packages. Oops, I see how that is happening now. My bad. > I'm going to assume that your main problem is that you would like to > see > /etc/motd in ssh sessions. > > So I'm reassigning this to openssh-server. The bug may still not be > there but I think it's closer. Sorry, incorrect assumption. This has nothing to do with openssh- server. I suspect that debianutils might be a better package, so I've re-assigned this bug to that package. Thank you for you response! -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2019, Christchurch, NZ Catalyst Cloud: | https://lca2019.linux.org.au/ https://catalystcloud.nz|
Bug#919271: base-files: Provide easy access to motd
Package: base-files Version: 10.1 Severity: wishlist Dear Maintainer, Since we've started having dynamic generation of the system MOTD, re-displaying it is hard. Especially if people are using SSH connection sharing. How about a /bin/motd (or /usr/bin) command which runs the following: run-parts /etc/update-motd.d; cat /etc/motd I've filed this bug report against base-files as this package delivers /etc/update-motd.d/10-uname. Incidentally, the description for base-files says that it delivers /etc/motd, which it doesn't anymore. Cheers, Andrew *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages base-files depends on: ii gawk [awk] 1:4.2.1+dfsg-1 ii mawk [awk] 1.3.3-17+b3 base-files recommends no packages. base-files suggests no packages. -- Configuration Files: /etc/profile changed [not included] -- no debconf information
Bug#772801: Proposed systemd file
Hi Francois, I'm not sure if you're still using mythtv-status, but I'd like to run a proposed systemd service past you. I have created one which is oneshot, but in the process I have also added functionality so that it is possible to use `systemctl stop mythtv-status` to stop the motd being updated. I have also added direct support for /etc/update-motd.d . It seems to be working okay on my laptop which is running systemd. There are a bunch of other features, everything is up in my git repo: http://git.etc.gen.nz/cgi-bin/gitweb.cgi?p=mythtv-status.git;a=summary and I'll be looking to upload to Debian in the next couple of days. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2019, Christchurch, NZ Catalyst Cloud: | https://lca2019.linux.org.au/ https://catalystcloud.nz|[Unit] Description=MythTV Status After=network.target mythtv-backend.service Wants=mythtv-backend.service Documentation=man:mythtv-status [Service] Type=oneshot RemainAfterExit=true ExecStart=/bin/sh -c "rm /var/lib/mythtv-status/motd_update_disabled || true" ExecStart=/usr/sbin/mythtv-update-motd ExecStop=/bin/sh -c "touch /var/lib/mythtv-status/motd_update_disabled; rm /run/motd.mythtv-status || true"; [Install] WantedBy=multi-user.target
Bug#911372: fai-setup-storage: setup-storage shouldn't use aes-cbc as default for LUKS containers
On Thu, 2018-12-20 at 13:36 +0100, Thomas Lange wrote: > > > > > > On Fri, 21 Dec 2018 01:27:09 +1300, Andrew Ruthven > > > > > etc.gen.nz> said: > > > Using the default of cryptsetup sounds sane, however I'd still > like the > > option of over riding this. > OK, then I can just remove this code, and it's still possible to set > your own parameters. Here's the diff [snip] Looks good to me. -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2019, Christchurch, NZ Catalyst Cloud: | https://lca2019.linux.org.au/ https://catalystcloud.nz|
Bug#911372: fai-setup-storage: setup-storage shouldn't use aes-cbc as default for LUKS containers
On Thu, 2018-12-20 at 13:06 +0100, Thomas Lange wrote: > I was also thinking about the choice of removing this option and > using > the default of crytpsetup. > > @Andrew: What's you oppinion on this, since you've added the code for > lukscreateopts? Hey, Using the default of cryptsetup sounds sane, however I'd still like the option of over riding this. The reason I added the options was so that we could use the correct settings to make use of the crypto features in the CPUs we use. Newer CPUs might require different settings, so it'd be good to allow flexibility. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2019, Christchurch, NZ Catalyst Cloud: | https://lca2019.linux.org.au/ https://catalystcloud.nz|
Bug#703010: (no subject)
On Fri, 2018-11-09 at 20:01 +, Dmitry Bogatov wrote: > > On my laptop, there is no VxID in /proc/self/status: [snip] That is correct, as I noted it is only present if you are running a kernel with the vserver patch applied. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz| linux.conf.au 2019, Christchurch, NZ https://catalystcloud.nz | https://lca2019.linux.org.au
Bug#902684: mythtv-status: motd functionality not working correctly
Hey, Thanks Ian. Funnily enough, back when I first wrote mythtv-status I had it generated the motd file on the fly in /etc/update-motd.d, but that slowed logging in far too much. I'm still wary about doing that as we're putting in a dependency on the performance of a potentially remote machine, which might be off. I think I'll go down the path of generating /var/run/mythtv-status.motd (or similar) and then having a snippet cat that file. Cheers, Andrew On Fri, 2018-06-29 at 16:27 +0100, Ian Campbell wrote: > Package: mythtv-status > Version: 0.10.8-1 > Severity: normal > > Hello, > > I just installed this package and the motd updating functionality is > not > working. I can see that it is correctly populating > /var/run/motd.dynamic but > that is not being incorporated into the actual motd (wherever that > is/however > that happens). > > In a mail to mythtv-user[0] another user noticed that apparently it > is now > necessary (on Ubuntu) to create a snippet in /etc/update-motd.d. I've > not tried > this on my Debian system yet, but I note that the directory does > exist. > > The patch there is ok as a local workaround, I think, but maybe not > appropriate > for the package, I'd guess either creating /var/run/mythtv- > status.motd and > having a snippet produce that or just having a snippet produce the > desired > content on the fly would be better. > > Thanks, > Ian. > > [0] http://lists.mythtv.org/pipermail/mythtv-users/2018-June/396660.h > tml > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') > Architecture: i386 (i686) > Foreign Architectures: amd64 > > Kernel: Linux 4.16.0-2-686-pae (SMP w/2 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), > LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > Init: sysvinit (via /sbin/init) > LSM: AppArmor: enabled > > Versions of packages mythtv-status depends on: > ii debconf [debconf-2.0] 1.5.66 > ii libconfig-auto-perl0.44-1 > ii libdate-manip-perl 6.71-1 > ii libmime-tools-perl 5.509-1 > ii libsys-sigaction-perl 0.23-1 > ii libwww-perl6.33-1 > ii libxml-libxml-perl 2.0128+dfsg-5 > ii lsb-base 9.20170808 > ii perl 5.26.2-5 > > Versions of packages mythtv-status recommends: > ii libmythtv-perl29.1+fixes20180603.git1777cc4425-dmo1 > ii libnet-upnp-perl 1.4.3-1 > > Versions of packages mythtv-status suggests: > pn molly-guard > > -- debconf information: > * mythtv-status/email: none > * mythtv-status/host: localhost > * mythtv-status/enable: true > -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2019, Christchurch, NZ Catalyst Cloud: | https://lca2019.linux.org.au/ https://catalystcloud.nz|
Bug#894998: ITP: rt4-extension-rest2 -- REST2 API extension (Request Tracker)
Package: wnpp Severity: wishlist Owner: Andrew Ruthven <and...@etc.gen.nz> * Package name: rt4-extension-rest2 Version : 1.03 Upstream Author : Best Practical Solutions <modu...@bestpractical.com> * URL : https://metacpan.org/release/RT-Extension-REST2 * License : GPLv2 Programming Lang: Perl Description : REST2 API extension (Request Tracker) This extension adds a modern REST API to Request Tracker. The existing API for RT is a rather painful RFC822 (yes email) based system via HTTP. This extension provides a much nicer JSON based RESTful interface. The intial packaging work has been carried but by myself for my employer. Ongoing maintenance will be by the Debian Request Tracker Group (of which I'm a member).
Bug#889636: ITP: rt4-extension-resetpassword -- Reset Password extension (Request Tracker)
Package: wnpp Severity: wishlist Owner: Andrew Ruthven <and...@etc.gen.nz> * Package name: rt4-extension-resetpassword Version : 1.04 Upstream Author : Best Practical Solutions <modu...@bestpractical.com> * URL : https://metacpan.org/release/RT-Extension-ResetPassword * License : GPLv2 Programming Lang: Perl Description : Reset Password extension (Request Tracker) This extension allows users to get a reset password link in Request Tracker. RT doesn't come out of the box with an ability for users to reset their passwords if they forget them, or if they aren't set. This extension adds that ability. The intial packaging work has been carried but by myself for my employer. Ongoing maintenance will be by the Debian Request Tracker Group (of which I'm a member).
Bug#886526: ITP: rt4-extension-commandbymail -- Change metadata of ticket via email (Request Tracker)
Hi Tollef, On Sun, 2018-01-07 at 13:29 +0100, Tollef Fog Heen wrote: > ]] Andrew Ruthven > > > The intial packaging work has been carried but by myself for my > > employer. > > Ongoing maintenance will be by the Debian Request Tracker Group (of > > which > > I'm a member). > > This is already packaged as librt-extension-commandbymail-perl, but > feel > free to have the team take it over. (I'm the maintainer.) Yeah, I spotted that when I went to add the Closes line to my changelog and found I already had the old ITP bug number in there. ;) Having the team take it over makes sense to me. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2018, Sydney, AU New Zealand's only Cloud: | Just a little bit of history https://catalyst.net.nz/cloud | http://linux.conf.au
Bug#886526: ITP: rt4-extension-commandbymail -- Change metadata of ticket via email (Request Tracker)
Package: wnpp Severity: wishlist Owner: Andrew Ruthven <and...@etc.gen.nz> * Package name: rt4-extension-commandbymail Version : 3.00 Upstream Author : Best Practical Solutions, LLC <modu...@bestpractical.com> * URL : https://metacpan.org/release/RT-Extension-CommandByMail * License : GPL v2 Programming Lang: Perl Description : Change metadata of ticket via email (Request Tracker) This extension allows you to manage tickets via email interface. You may put commands into the beginning of a mail, and extension will apply them. The intial packaging work has been carried but by myself for my employer. Ongoing maintenance will be by the Debian Request Tracker Group (of which I'm a member).
Bug#886527: ITP: rt4-extension-assets-import-csv -- Import Assets from CSV files (Request Tracker)
Package: wnpp Severity: wishlist Owner: Andrew Ruthven <and...@etc.gen.nz> * Package name: rt4-extension-assets-import-csv Version : 2.2 Upstream Author : Best Practical Solutions, LLC <modu...@bestpractical.com> * URL : https://metacpan.org/release/RT-Extension-Assets-Import-CSV * License : GPL v2 Programming Lang: Perl Description : Import Assets from CSV files (Request Tracker) This extension allows importing and updating Asset records from CSV files. This is for RT 4.4.x, solutions for older versions available on CPAN. Request Tracker 4.4.0 introduced an Assets module. This package allows both importing assets from CSV files, and to update existing assets using CSV files as well. The intial packaging work has been carried but by myself for my employer. Ongoing maintenance will be by the Debian Request Tracker Group (of which I'm a mmember).
Bug#886525: ITP: rt4-extension-mergeusers -- Merge users (Request Tracker)
Package: wnpp Severity: wishlist Owner: Andrew Ruthven <and...@etc.gen.nz> * Package name: rt4-extension-mergeusers Version : 1.03 Upstream Author : Best Practical Solutions, LLC <modu...@bestpractical.com> * URL : https://metacpan.org/release/RT-Extension-MergeUsers * License : GPL v2 Programming Lang: Perl Description : Merge users (Request Tracker) This extension allows merging users in Request Tracker. You always end up with duplicate users in a ticketing system since people use different email addresses. This extension provides a mechanism to manage that better. The intial packaging work has been carried but by myself for my employer. Ongoing maintenance will be by the Debian Request Tracker Group (of which I'm a member).
Bug#881985: [request-tracker-maintainers] Bug#881985: Bug#881985: request-tracker4: Correctly set RT version in configure if a Debian epoch is used
On Thu, 2018-01-04 at 21:57 +, Dominic Hargreaves wrote: > Hi Andrew, > > I actually committed essentially that change a while ago but didn't > feel it warranted an upload by itself. Sorry that wasn't clear - > I should have commented at the same time as tagging pending. Ah, no worries. I just thought I should clean up the patch since I was doing other RT work. Thanks for commiting it. -- Andrew Ruthven, Wellington, New Zealand Data Centre Manager MIITP At work: andrew.ruth...@catalyst.net.nz At home: and...@etc.gen.nz Card : http://qr.catalyst.net.nz/907675e1 Cloud : NZs only real cloud - https://catalyst.net.nz/cloud GPG fpr: C603 FC4E 600F 1CEC D1C8 D97C 4B53 D931 E4D3 E863 LCA2018: Just a little bit of history repeating - http://linux.conf.au
Bug#881985: [request-tracker-maintainers] Bug#881985: request-tracker4: Correctly set RT version in configure if a Debian epoch is used
Update patch to only strip the epoch off the version is attached. -- Andrew Ruthven, Wellington, New Zealand Data Centre Manager MIITP At work: andrew.ruth...@catalyst.net.nz At home: and...@etc.gen.nz Card : http://qr.catalyst.net.nz/907675e1 Cloud : NZs only real cloud - https://catalyst.net.nz/cloud GPG fpr: C603 FC4E 600F 1CEC D1C8 D97C 4B53 D931 E4D3 E863 LCA2018: Just a little bit of history repeating - http://linux.conf.au --- debian/patches/debianize_version.diff 2017-08-30 07:05:39.0 +1200 +++ ../rt-patches/debianize_version.diff 2018-01-03 14:22:22.964614844 +1300 @@ -6,6 +6,9 @@ Also make clear in the web interface that this version number is from Debian. +Updated to strip any epoch off the version. Commands taken from +/usr/share/dpkg/pkg-info.mk . + Patch-Name: debianize_version.diff --- configure.ac | 8 @@ -21,7 +24,7 @@ dnl Setup autoconf AC_PREREQ([2.53]) -AC_INIT(RT, m4_esyscmd([( git describe --tags || cat ./.tag 2> /dev/null || echo "rt-3.9.EXPORTED" )| tr -d "\n"]), [rt-b...@bestpractical.com]) -+AC_INIT(RT, m4_esyscmd([( dpkg-parsechangelog -SVersion )| tr -d "\n"]), [https://www.debian.org/Bugs/Reporting]) ++AC_INIT(RT, m4_esyscmd([( dpkg-parsechangelog -SVersion | sed -e 's/^[0-9]*://' )| tr -d "\n"]), [https://www.debian.org/Bugs/Reporting]) AC_CONFIG_SRCDIR([lib/RT.pm]) dnl Save our incant early since $@ gets overwritten by some macros.
Bug#881985: [request-tracker-maintainers] Bug#881985: request-tracker4: Correctly set RT version in configure if a Debian epoch is used
On Sun, 2017-11-26 at 19:34 +, Dominic Hargreaves wrote: > Thanks, though with both sed calls there would be no point in > applying > the change at all as we're back to the plain upstream version :) Yeah, I realised after I'd prepared the patch that showing the Debian patch level might have been deliberate. ;) In any case, please keep the first sed so that folks can continue to use an epoch to over ride the official Debian packages. > > I also note that the same diff currently sets the date to 2016 in > > the > > footer. > > The date is already 2016 in the version in stretch, so that looks > correct? Ah, 4.4.1 *was* released in 2016. I thought it was 2017 for some reason. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand Data Centre Manager MIITP At work: andrew.ruth...@catalyst.net.nz At home: and...@etc.gen.nz Card : http://qr.catalyst.net.nz/907675e1 Cloud : NZs only real cloud - https://catalyst.net.nz/cloud GPG fpr: C603 FC4E 600F 1CEC D1C8 D97C 4B53 D931 E4D3 E863 LCA2018: Just a little bit of history repeating - http://linux.conf.au
Bug#881984: request-tracker4: Modify debian/rules to allow rebuilding
Source: request-tracker4 Version: 4.4.1 Severity: minor Tags: patch Dear Maintainer, When retrying to rebuild the .debs for RT, I found that a few generated files and directories we either not correctly removed, or not even attemped to be removed. Also, if the configure wasn't present, then building failed. The attached patch to debian/rules fixes these issues. Cheers, Andrew -- System Information: Debian Release: 9.1 APT prefers common APT policy: (500, 'common'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Andrew Ruthven, Wellington, New Zealand MIITP At work: andrew.ruth...@catalyst.net.nz At home: and...@etc.gen.nz Cloud : NZs only real cloud - https://catalyst.net.nz/cloud GPG fpr: C603 FC4E 600F 1CEC D1C8 D97C 4B53 D931 E4D3 E863 LCA2018: Just a little bit of history repeating - http://linux.conf.au--- debian/rules2017-08-29 19:05:39.0 + +++ ../rules2017-11-15 00:45:17.548156696 + @@ -23,6 +23,7 @@ build-arch: build-stamp build-indep: build-stamp +configure: build-stamp build-stamp: configure dh_testdir @@ -86,7 +87,8 @@ # Restore shipped generated files -find bak -type f -print | sed -e 's/^bak\///' | while read f; do mv bak/$$f $$f; done -rm -rf bak - rm -f config.status config.log config.pld bak html-docs + rm -rf html-docs + rm -f config.status config.log config.pld bak t/tmp/ports t/data/gnupg/keyrings/random_seed dh_autoreconf_clean dh_clean build-stamp @@ -141,6 +143,9 @@ find $(RT_PKG)/usr/share/$(RT)/lib -type f -name '*.in' -print0 | xargs -0 --no-run-if-empty rm rm -f $(RT_PKG)/usr/share/$(RT)/etc/upgrade/*.in + # Remove a test file + rm -f .prove + # This is generated by the maintainer scripts $(RM) $(RT_PKG)/usr/share/$(RT)/etc/RT_SiteConfig.pm
Bug#881985: request-tracker4: Correctly set RT version in configure if a Debian epoch is used
Source: request-tracker4 Severity: minor Tags: patch Dear Maintainer, I need to build a custom RT package to include some custom patches that haven't been accepted upstream yet. When I do that, I set an epoch on the Debian version to ensure that we don't accidentally upgrade to a newer version from Debian. With the 4.4.x packages this has caused RT to think the version is 0.0.0, which causes a bunch of issues. The attached patch modifies debian/patches/debian_version.diff to strip off an epoch, if present, and the Debian patch level from the version presented by RT. If you want to keep the Debian patch level, then remove the first call to sed. I also note that the same diff currently sets the date to 2016 in the footer. Cheers, Andrew -- System Information: Debian Release: 9.1 APT prefers common APT policy: (500, 'common'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Andrew Ruthven, Wellington, New Zealand MIITP At work: andrew.ruth...@catalyst.net.nz At home: and...@etc.gen.nz Cloud : NZs only real cloud - https://catalyst.net.nz/cloud GPG fpr: C603 FC4E 600F 1CEC D1C8 D97C 4B53 D931 E4D3 E863 LCA2018: Just a little bit of history repeating - http://linux.conf.au--- debian/patches/debianize_version.diff 2017-08-29 19:05:39.0 + +++ ../rt-patches/debianize_version.diff2017-11-14 23:42:45.762257327 + @@ -6,6 +6,9 @@ Also make clear in the web interface that this version number is from Debian. +Updated to strip the epoch and Debian patch off the version. Commands +taken from /usr/share/dpkg/pkg-info.mk . + Patch-Name: debianize_version.diff --- configure.ac | 8 @@ -21,7 +24,7 @@ dnl Setup autoconf AC_PREREQ([2.53]) -AC_INIT(RT, m4_esyscmd([( git describe --tags || cat ./.tag 2> /dev/null || echo "rt-3.9.EXPORTED" )| tr -d "\n"]), [rt-b...@bestpractical.com]) -+AC_INIT(RT, m4_esyscmd([( dpkg-parsechangelog -SVersion )| tr -d "\n"]), [https://www.debian.org/Bugs/Reporting]) ++AC_INIT(RT, m4_esyscmd([( dpkg-parsechangelog -SVersion | sed -e 's/-[^-]*$//' | sed -e 's/^[0-9]*://' )| tr -d "\n"]), [https://www.debian.org/Bugs/Reporting]) AC_CONFIG_SRCDIR([lib/RT.pm]) dnl Save our incant early since $@ gets overwritten by some macros.
Bug#853121: Still using gnocchi-dbsync
Version: 3.0.0-2 Package: gnocchi-common Hey, It appears that #832792 hasn't been completely resolved. I've just tried to install 3.0.0-2 and it's still using gnocchi-dbsync - which no longer exists: Setting up gnocchi-common (3.0.0-2) ... PKG-Openstack now calling: dbc_go gnocchi-common configure 3.0.0-2 Now calling gnocchi-dbsync: this may take a while... sh: gnocchi-dbsync: command not found dpkg: error processing package gnocchi-common (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: gnocchi-common E: Sub-process /usr/bin/dpkg returned an error code (1) dirk:~# Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2017, Hobart, AU New Zealand's only Cloud: | The Future of Open Source https://catalyst.net.nz/cloud | http://linux.conf.au signature.asc Description: This is a digitally signed message part
Bug#837119: signing-party: sig2dot is broken with gpg 2.1
Package: signing-party Version: 2.4-1 Severity: normal Dear Maintainer, The regular expressions in sig2dot don't match the new output format in gpg 2.1 The new output format is (using the same keys as in the script): pub dsa1024 2003-08-01 [SC] 75D8908EBD35E31D94D102EF10557B83807CAC25 uid [marginal] Michael Ablassmeier (abi)sig 3CE04080E9456ADE2 2004-02-07 Michael Schiansky Cheers, Andrew -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages signing-party depends on: ii gnupg 2.1.15-2 ii libc6 2.24-2 ii libclass-methodmaker-perl 2.24-1+b1 ii libgnupg-interface-perl0.52-3 ii libmailtools-perl 2.13-1 ii libmd0 0.0.0-2 ii libmime-tools-perl 5.508-1 ii libnet-idn-encode-perl 2.300-1+b1 ii libterm-readkey-perl 2.33-1+b1 ii libtext-template-perl 1.46-1 pn perl:any pn python:any ii qprint 1.1.dfsg.2-2 Versions of packages signing-party recommends: ii dialog 1.3-20160828-1 ii libgd-perl [libgd-gd2-perl] 2.53-2.1 ii libpaper-utils 1.1.24+nmu4 ii postfix [mail-transport-agent] 3.1.0-5+b1 ii whiptail0.52.18-3 Versions of packages signing-party suggests: pn fonts-noto-cjk ii fonts-noto-mono20160724-1 ii imagemagick8:6.8.9.9-7.2 pn mutt pn qrencode ii texlive-font-utils 2016.20160819-1 ii texlive-latex-extra2016.20160819-1 ii texlive-latex-recommended 2016.20160819-2 ii texlive-xetex 2016.20160819-2 ii wipe 0.22-4 -- no debconf information
Bug#832792: gnocchi-common: Postinst uses gnocchi-dbsync which no longer exists
Package: gnocchi-common Version: 2.0.2-6 Severity: important Dear Maintainer, The postinst for this package attempts to use gnocchi-dbsync. This command was renamed upstream to gnocchi-upgrade. See: https://github.com/openstack/gnocchi/commit/85bef730942dee660e4e87614aee3a212d7adf31 This blocks the package from being able to be installed. Editing the postinst file allows me to get further on installing the package. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages gnocchi-common depends on: ii adduser3.115 ii dbconfig-common2.0.4 ii debconf [debconf-2.0] 1.5.59 ii python-gnocchi 2.0.2-6 gnocchi-common recommends no packages. gnocchi-common suggests no packages. -- debconf information excluded
Bug#423458: dnscap packaged
On Sat, 2015-10-17 at 02:34 -0400, Sergio Durigan Junior wrote: > It seems the work on this package has been pretty unstable. I am > planning to work on packaging this (once and for all). Does anybody > have anything against? Hi Sergio, I no longer require dnscap at work, but please go ahead and do the work that's required. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2016 New Zealand's only Cloud: | LCA By the Bay, Geelong, AU https://catalyst.net.nz/cloud | http://lca2016.linux.org.au
Bug#415701: Packaging ready for review
Hi, One of my colleagues asked to have RT::Extension::CommandByMail deployed on our RT instance. I prefer to use Debian packages so I've a package, the changes are available in a git repo here: https://github.com/catalyst/rt-extension-commandbymail/tree/dpkg If folks are happy with it, then I'll submit a pull request for upstream and we can upload it to Debian. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2016 New Zealand's only Cloud: | LCA By the Bay, Geelong, AU https://catalyst.net.nz/cloud | http://lca2016.linux.org.au -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772516: unblock: mythtv-status/0.10.6-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mythtv-status Version 0.10.4 in testing has two bugs: - It doesn't correctly handle UTF-8 in generated emails with Perl 5.20 (which will be released with Jessie) - no bug has been raised for this - It incorrectly strips out some information - bug #729400 I have also signed this new version with my new 4096 bit GPG key and xz is now used. Appropriate debdiff's are attached. The debdiff against the dsc files excludes the test files added for testing #729400 to reduce the noise and the manpage which only shows bumps. unblock mythtv-status/0.10.6-1 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.17-vs2.3.6.13-beng (SMP w/8 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash File lists identical (after any substitutions) Control files: lines which differ (wdiff format) Installed-Size: [-146-] {+147+} Version: [-0.10.4-1-] {+0.10.6-1+} diff -Nru --exclude '*.t' --exclude '*.xml' --exclude '*.1' mythtv-status-0.10.4/ChangeLog mythtv-status-0.10.6/ChangeLog --- mythtv-status-0.10.4/ChangeLog 2013-10-28 22:39:56.0 +1300 +++ mythtv-status-0.10.6/ChangeLog 2014-12-05 10:18:31.0 +1300 @@ -1,3 +1,15 @@ +2014-12-02 Andrew Ruthven + Add in more UTF-8 encodings as required for Perl v5.18, thanks to + Jan Schneider for reporting the UTF-8 issue. + +2014-09-11 Andrew Ruthven + Spotted that if the next recording is in 30 hours, then it is + displayed as 0 Days, 3. Correct it so it'll be displayed + as 30 Hours. Also fixes an issue where 0 hours was removed + if the hour was a multiple of 10. Thanks to Stephan Seitz for + reporting the multiple of 10 issue. + + 2013-10-28 Andrew Ruthven Guard against zero total disk space, this affected Werner Mahr. diff -Nru --exclude '*.t' --exclude '*.xml' --exclude '*.1' mythtv-status-0.10.4/bin/mythtv-status mythtv-status-0.10.6/bin/mythtv-status --- mythtv-status-0.10.4/bin/mythtv-status 2013-10-28 22:39:56.0 +1300 +++ mythtv-status-0.10.6/bin/mythtv-status 2014-12-05 10:18:31.0 +1300 @@ -85,7 +85,7 @@ my $return_code_only = 0; -my $VERSION = '0.10.4'; +my $VERSION = '0.10.6'; # Some display blocks are disabled by default: $c-{'display'}{'Shows due to Auto Expire'} = 0; @@ -477,7 +477,7 @@ } $str =~ s/\b1 (Day|Hour|Minute)s/1 $1/g; -$str =~ s/(, )?0 Hours(, )?//; +$str =~ s/\b0 (Days|Hours)(, )?//; $str =~ s/, 0 Minutes$//; if ($seconds = $c-{'recording_in_warn'}) { @@ -681,10 +681,10 @@ my $mail = MIME::Entity-build( To = $c-{'email'}, - Subject = $title . (defined $suffix ? - $suffix : ''), + Subject = encode('UTF-8', $title . (defined $suffix ? - $suffix : '')), Charset = $charset, Encoding= quoted-printable, - Data= $output + Data= encode('UTF-8', $output), ); $mail-send('sendmail'); diff -Nru --exclude '*.t' --exclude '*.xml' --exclude '*.1' mythtv-status-0.10.4/debian/changelog mythtv-status-0.10.6/debian/changelog --- mythtv-status-0.10.4/debian/changelog 2013-10-28 23:03:44.0 +1300 +++ mythtv-status-0.10.6/debian/changelog 2014-12-05 10:23:14.0 +1300 @@ -1,3 +1,21 @@ +mythtv-status (0.10.6-1) unstable; urgency=low + + * New upstream release. + * Brings in a minor change that was on master, but missed from the +release-0.10 git branch. + * Update standards version to 3.9.6. + + -- Andrew Ruthven and...@etc.gen.nz Fri, 05 Dec 2014 10:17:37 +1300 + +mythtv-status (0.10.5-1) unstable; urgency=low + + * New upstream release (Closes: #729400). + * Fix sending emails with UTF-8 characters in them with Perl = 5.18. + * Fix removing 0 hours from Next Recording In if the hour is a multiple +of 10. + + -- Andrew Ruthven and...@etc.gen.nz Tue, 02 Dec 2014 20:29:13 +1300 + mythtv-status (0.10.4-1) unstable; urgency=low * New upstream release (Closes: #724166, #709377, #709449). diff -Nru --exclude '*.t' --exclude '*.xml' --exclude '*.1' mythtv-status-0.10.4/debian/control mythtv-status-0.10.6/debian/control --- mythtv-status-0.10.4/debian/control 2013-10-28 23:00:07.0 +1300 +++ mythtv-status-0.10.6/debian/control 2014-12-05 10:22:42.0 +1300 @@ -3,7 +3,7 @@ Priority: extra Maintainer: Andrew Ruthven and...@etc.gen.nz Build-Depends: debhelper (= 6), po-debconf -Standards-Version: 3.9.4 +Standards-Version: 3.9.6 Homepage: http://www.etc.gen.nz/projects/mythtv/mythtv-status.html Vcs-Git: http://git.etc.gen.nz/mythtv-status.git Vcs-Browser: http://git.etc.gen.nz/cgi-bin/gitweb.cgi?p=mythtv-status.git;a=summary
Bug#729400: mythtv-status: Value for Next recording in is sometimes wrong
Hi Stephen, This smells like timezone issues. Sadly I'm stuck on MythTV 0.24 so I've not seen any of these timezone issues! Next time you see it, could you please run mythtv-status with -s bug729400.xml and send me the resulting file so that I can attempt to reproduce the issue? Cheers, Andrew -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2014 | Come swan on the Swan River |http://linux.conf.au signature.asc Description: This is a digitally signed message part
Bug#727057: network-manager: Fails to install if netdev group already exists
Package: network-manager Version: 0.9.8.0-5 Severity: normal Dear Maintainer, While upgrade my Sid box, network-manager failed to install cause the postinst exited as the netdev group already exists, causing the addgroup command to fail. The addgroup should probably use a construct similar to this: if ! getent group netdev /dev/null then addgroup --quiet --system netdev fi Cheers! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10.13-vs2.3.6.6-beng (SMP w/8 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager depends on: ii adduser3.113+nmu3 ii dbus 1.6.16-1 ii isc-dhcp-client4.2.4-7 ii libc6 2.17-93 ii libdbus-1-31.6.16-1 ii libdbus-glib-1-2 0.100.2-1 ii libgcrypt111.5.3-2 ii libglib2.0-0 2.36.4-1 ii libgnutls262.12.23-8 ii libgudev-1.0-0 204-5 ii libnl-3-2003.2.21-1 ii libnl-genl-3-200 3.2.21-1 ii libnl-route-3-200 3.2.21-1 ii libnm-glib40.9.8.0-5 ii libnm-util20.9.8.0-5 ii libpolkit-gobject-1-0 0.105-4 ii libuuid1 2.20.1-5.5 ii lsb-base 4.1+Debian12 ii udev 204-5 ii wpasupplicant 1.0-3+b2 Versions of packages network-manager recommends: ii crda 1.1.2-1 ii dnsmasq-base 2.66-4 ii iptables 1.4.20-2 ii modemmanager 0.5.2.0-2 ii policykit-1 0.105-4 ii ppp 2.4.5-5.2 Versions of packages network-manager suggests: pn avahi-autoipd none -- Configuration Files: /etc/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla [Errno 13] Permission denied: u'/etc/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727057: [Pkg-utopia-maintainers] Bug#727057: network-manager: Fails to install if netdev group already exists
On Tue, 2013-10-22 at 00:05 +0200, Michael Biebl wrote: This getent check is not necessary: # addgroup --system netdev addgroup: The group `netdev' already exists as a system group. Exiting. # echo $? 0 If addgroup fails for you, please file a bug against adduser. Sadly if the group is not a system group, then it exits with return code 1 and a warning that the GID isn't in the system group range. This may be an edge case, but it certainly stopped network-manager from upgrading. Cheers! -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2014 | Come swan on the Swan River |http://linux.conf.au signature.asc Description: This is a digitally signed message part
Bug#703010: debianutils: ischroot can no longer detect vservers
On Tue, 2013-07-30 at 16:32 +, Clint Adams wrote: On Tue, Jul 30, 2013 at 09:00:15PM +1200, Andrew Ruthven wrote: Totally agree. The problem is with tools that don't run in a chroot, if they are in a chroot, break horribly. Mostly they're stuff run from init.d... I think that's what /usr/sbin/policy-rc.d is for. Sadly /usr/sbin/policy-rc.d won't fix the initscripts issue as it in is in the packages postinst. It is all about setting up the /run symlink and associated bits and pieces. It takes one approach if it is in a chroot and a totally different approach if it is a physical host. The sysvinit postinst script also uses ischroot. Cheers! -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2014 | Come swan on the Swan River |http://linux.conf.au signature.asc Description: This is a digitally signed message part
Bug#703010: debianutils: ischroot can no longer detect vservers
On Sun, 2013-07-28 at 00:47 +, Clint Adams wrote: On Fri, Mar 15, 2013 at 09:16:45PM +1300, Andrew Ruthven wrote: The big downside to that approach that I can see is that according to the changelog ischroot was implemented to *stop* people having checks spread all over the place. And as we've just discovered those checks break over time as things progress. Better to have them in one place, than spread around. I don't know; it seems pretty stupid to base script behavior on whether one is in a chroot or not. Totally agree. The problem is with tools that don't run in a chroot, if they are in a chroot, break horribly. Mostly they're stuff run from init.d... -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://linux.conf.au signature.asc Description: This is a digitally signed message part
Bug#703010: debianutils: ischroot can no longer detect vservers
On Fri, 2013-03-15 at 03:33 +, Clint Adams wrote: On newer vserver patches a better check is to look for a VxID line in /proc/self/status. If the line is present you're running a vserver kernel. If the value is 0, then you're on the physical host, anything else means you're in a vserver. I wonder if it's better to have the initscripts postinst do the grep than to parse /proc/self/status in ischroot. The big downside to that approach that I can see is that according to the changelog ischroot was implemented to *stop* people having checks spread all over the place. And as we've just discovered those checks break over time as things progress. Better to have them in one place, than spread around. I guess that question comes down to, is the mount that initscripts postinst doing appropriate in chroots in general? At a guess no, otherwise it wouldn't use ischroot. I have proposed patch for ischroot that is attached to bug #703012 (curse the BTS for not creating my bug reports in a timely manner). Cheers! -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://linux.conf.au signature.asc Description: This is a digitally signed message part
Bug#703011: debianutils: ischroot can no longer detect vservers
Package: debianutils Version: 4.3.4 Severity: important Tags: patch [resubmitting as something seems to have gone wrong with creating the bug] [third time's the charm?] Dear Maintainer, The ischroot code checks to see if it can access /proc/1/root to determine if it is a running inside a chroot. Within vservers you can now read /proc/1/root so it is no longer a sufficient test for vservers. On newer vserver patches a better check is to look for a VxID line in /proc/self/status. If the line is present you're running a vserver kernel. If the value is 0, then you're on the physical host, anything else means you're in a vserver. Inside a vserver: puck@build-sid-amd64:/$ grep VxID /proc/self/status VxID: 12 puck@build-sid-amd64:/$ On the physical host: build-servers:~$ grep VxID /proc/self/status VxID: 0 puck@build-servers:~$ A patch that adds this behaviour is attached, please feel free to rewrite! Also, method that I've supplied works for non-root users as well, but I haven't added that support. I've set this bug report to important as it is stopping initscripts from being installable on a Wheezy vserver. This is the case on Linux kernel 3.4 + 2.3.3.9 vserver patch. The 3.2 kernel set of patches is not affected by this change of behaviour. Cheers! -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-28-vserver (SMP w/1 CPU core) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages debianutils depends on: ii libc6 2.13-37 ii sensible-utils 0.0.7 debianutils recommends no packages. debianutils suggests no packages. -- no debconf information --- ischroot.c.orig 2013-03-12 22:00:36.235819225 +1300 +++ ischroot.c 2013-03-12 22:33:08.744874725 +1300 @@ -76,9 +76,31 @@ return 2; /* Root can not read /proc/1/root, assume vserver or similar */ return 0; - } else if ((st1.st_dev == st2.st_dev) (st1.st_ino == st2.st_ino)) + } else if ((st1.st_dev == st2.st_dev) (st1.st_ino == st2.st_ino)) { +/* but look more closely for vserver, see if VxID != 0 */ + +FILE *status=fopen(/proc/self/status, r); +size_t linesiz=0; +char* linebuf=0; +char* vxidline=0; +ssize_t linelen=0; +unsigned int vxid = 0; +while (linelen=getline(linebuf, linesiz, status)0) { + vxidline = strstr(linebuf, VxID:); + if (vxidline != NULL) { +sscanf(linebuf, %*s %u, vxid); + +if (vxid == 0) + /* Host system */ + return 1; +else + return 0; + } +} +free (linebuf); +fclose(status); return 1; - else + } else return 0; } signature.asc Description: This is a digitally signed message part
Bug#703010: debianutils: ischroot can no longer detect vservers
Package: debianutils Version: 4.3.4 Severity: important [resubmitting as something seems to have gone wrong with creating the bug] Dear Maintainer, The ischroot code checks to see if it can access /proc/1/root to determine if it is a running inside a chroot. Within vservers you can now read /proc/1/root so it is no longer a sufficient test for vservers. On newer vserver patches a better check is to look for a VxID line in /proc/self/status. If the line is present you're running a vserver kernel. If the value is 0, then you're on the physical host, anything else means you're in a vserver. Inside a vserver: puck@build-sid-amd64:/$ grep VxID /proc/self/status VxID: 12 puck@build-sid-amd64:/$ On the physical host: build-servers:~$ grep VxID /proc/self/status VxID: 0 puck@build-servers:~$ I've set this bug report to important as it is stopping initscripts from being installable on a Wheezy vserver. This is the case on Linux kernel 3.4 + 2.3.3.9 vserver patch. The 3.2 kernel set of patches is not affected by this change of behaviour. Cheers! -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-28-vserver (SMP w/1 CPU core) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages debianutils depends on: ii libc6 2.13-37 ii sensible-utils 0.0.7 debianutils recommends no packages. debianutils suggests no packages. -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#703012: debianutils: ischroot can no longer detect vservers
Package: debianutils Version: 4.3.4 Severity: important [resubmitting as something seems to have gone wrong with creating the bug] [third time's the charm?] Dear Maintainer, The ischroot code checks to see if it can access /proc/1/root to determine if it is a running inside a chroot. Within vservers you can now read /proc/1/root so it is no longer a sufficient test for vservers. On newer vserver patches a better check is to look for a VxID line in /proc/self/status. If the line is present you're running a vserver kernel. If the value is 0, then you're on the physical host, anything else means you're in a vserver. Inside a vserver: puck@build-sid-amd64:/$ grep VxID /proc/self/status VxID: 12 puck@build-sid-amd64:/$ On the physical host: build-servers:~$ grep VxID /proc/self/status VxID: 0 puck@build-servers:~$ A patch that adds this behaviour is attached, please feel free to rewrite! Also, method that I've supplied works for non-root users as well, but I haven't added that support. I've set this bug report to important as it is stopping initscripts from being installable on a Wheezy vserver. This is the case on Linux kernel 3.4 + 2.3.3.9 vserver patch. The 3.2 kernel set of patches is not affected by this change of behaviour. Cheers! -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-28-vserver (SMP w/1 CPU core) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages debianutils depends on: ii libc6 2.13-37 ii sensible-utils 0.0.7 debianutils recommends no packages. debianutils suggests no packages. -- no debconf information --- ischroot.c.orig 2013-03-12 22:00:36.235819225 +1300 +++ ischroot.c 2013-03-12 22:33:08.744874725 +1300 @@ -76,9 +76,31 @@ return 2; /* Root can not read /proc/1/root, assume vserver or similar */ return 0; - } else if ((st1.st_dev == st2.st_dev) (st1.st_ino == st2.st_ino)) + } else if ((st1.st_dev == st2.st_dev) (st1.st_ino == st2.st_ino)) { +/* but look more closely for vserver, see if VxID != 0 */ + +FILE *status=fopen(/proc/self/status, r); +size_t linesiz=0; +char* linebuf=0; +char* vxidline=0; +ssize_t linelen=0; +unsigned int vxid = 0; +while (linelen=getline(linebuf, linesiz, status)0) { + vxidline = strstr(linebuf, VxID:); + if (vxidline != NULL) { +sscanf(linebuf, %*s %u, vxid); + +if (vxid == 0) + /* Host system */ + return 1; +else + return 0; + } +} +free (linebuf); +fclose(status); return 1; - else + } else return 0; } signature.asc Description: This is a digitally signed message part
Bug#701875: fai-client: install_packages doesn't support package/target syntax
Package: fai-client Version: 3.4.7 Severity: normal We tried to put a package in the package_config file with the following: linux-image-3.2.0-0.bpo.4-amd64/squeeze-backports But install_packages declared that the package: linux-image-3.2.0-0.bpo.4-amd64/squeeze-backports didn't exist, which is lies. The installable function has a regex which pick out the package name, but it doesn't support the above syntax. The attached patch adds this support (against master). Cheers! -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-28-vserver (SMP w/1 CPU core) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages fai-client depends on: ii file 5.04-5+squeeze2 Determines file type using magic ii iproute20100519-3networking and traffic control too ii libapt-pkg-perl0.1.24+b1 Perl interface to libapt-pkg ii perl 5.10.1-17squeeze4 Larry Wall's Practical Extraction Versions of packages fai-client recommends: ii cfengine2 2.2.10-2 Tool for configuring and maintaini ii debconf-utils 1.5.36.1 debconf utilities fai-client suggests no packages. -- Configuration Files: /etc/fai/fai.conf changed [not included] -- no debconf information From 1285f9491282ee6c6fa61f4fe78909756e6a2015 Mon Sep 17 00:00:00 2001 From: Andrew Ruthven p...@catalyst.net.nz Date: Tue, 26 Feb 2013 15:05:33 +1300 Subject: [PATCH] This regex was incorrectly throwing away targetted installs. For example: package/squeeze-backports Was being rejected. This patch pulls out package and allows us to see if it exists. --- bin/install_packages |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bin/install_packages b/bin/install_packages index 2f1b6b8..2bbde36 100755 --- a/bin/install_packages +++ b/bin/install_packages @@ -440,7 +440,7 @@ sub mkpackagelist { # simulate APTs and aptitudes understanding of special package names # suffixed by -, + -elsif ( $pack =~ /^(.+)[_=+-]$/ and $cache-exists($1)) { +elsif ( $pack =~ /^(.+?)(?:\/.+|[_=+-])$/ and $cache-exists($1)) { if (defined ($cache-{$1}{VersionList})) { push @known, $pack; -- 1.7.10.4
Bug#691548: unblock: mythtv-status/0.10.2-2
On Wed, 2012-12-19 at 20:16 +0100, Julien Cristau wrote: On Sat, Oct 27, 2012 at 15:08:29 +1300, Andrew Ruthven wrote: The version in unstable removes some extraneous debugging from the init.d (bug #681684) and adds support for the new dynamic motd logic in Wheezy (bug #688034 should probably be flagged as Important). Meh. What business does this thing have to mess with motd... Because it is useful? And on some hardware running it in real time while a user is logging in is slow enough that it is a real pain, that was my original use case. diff -Nru mythtv-status-0.10.2/debian/init.d mythtv-status-0.10.2/debian/init.d --- mythtv-status-0.10.2/debian/init.d 2012-03-22 23:33:58.0 +1300 +++ mythtv-status-0.10.2/debian/init.d 2012-10-02 21:47:53.0 +1300 @@ -21,8 +21,8 @@ # Provides: mythtv-status # Required-Start:$remote_fs # Required-Stop: $remote_fs -# Should-Start: $named mythtv-backend -# Should-Stop: $named mythtv-backend +# Should-Start: $named mythtv-backend $motd +# Should-Stop: $named mythtv-backend $motd What's $motd? Shouldn't this be motd (no $)? A bug. I've just uploaded a new .deb to unstable to fix this and a minor verbosity that could occur in some cases. I've attached two debdiffs: 0.10.2-1 (wheezy) - 0.10.2-3 (new package) 0.10.2-2 (sid)- 0.10.2-3 (new package) The only other change in the debdiff is the Perl version used to generate the man page. Cheers! -- Andrew Ruthven, Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://lca2013.linux.org.au diff -Nru mythtv-status-0.10.2/debian/changelog mythtv-status-0.10.2/debian/changelog --- mythtv-status-0.10.2/debian/changelog 2012-07-07 16:34:36.0 +1200 +++ mythtv-status-0.10.2/debian/changelog 2012-12-20 10:31:07.0 +1300 @@ -1,3 +1,18 @@ +mythtv-status (0.10.2-3) unstable; urgency=low + + * Fix the use of motd as a facility name, shouldn't be $motd. +Reported by Julian Cristau, thank you. + * Don't abort the init.d if we can't remove /var/run/motd.orig. + + -- Andrew Ruthven and...@etc.gen.nz Thu, 20 Dec 2012 10:29:31 +1300 + +mythtv-status (0.10.2-2) unstable; urgency=low + + * Handle a stale temp file more gracefully (Closes: #681684) + * base-files 6.11 in Wheezy uses /var/run/motd.dynamic (Closes: #688034) + + -- Andrew Ruthven and...@etc.gen.nz Tue, 02 Oct 2012 21:50:10 +1300 + mythtv-status (0.10.2-1) unstable; urgency=low * New upstream release. (Closes: #680358) diff -Nru mythtv-status-0.10.2/debian/init.d mythtv-status-0.10.2/debian/init.d --- mythtv-status-0.10.2/debian/init.d 2012-03-22 23:33:58.0 +1300 +++ mythtv-status-0.10.2/debian/init.d 2012-12-20 10:29:04.0 +1300 @@ -21,8 +21,8 @@ # Provides: mythtv-status # Required-Start:$remote_fs # Required-Stop: $remote_fs -# Should-Start: $named mythtv-backend -# Should-Stop: $named mythtv-backend +# Should-Start: $named mythtv-backend motd +# Should-Stop: $named mythtv-backend motd # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Update the MOTD with the MythTV status @@ -35,6 +35,7 @@ NAME=mythtv-status# Introduce the short server's name here DESC=MythTV Status # Introduce a short description here TEMPFILE=/var/run/motd.mythtv-status +WORKFILE=/var/run/motd test -x $DAEMON || exit 0 @@ -53,6 +54,9 @@ exit fi +# Debian Wheezy+ handles the MOTD differently. +[ -f /var/run/motd.dynamic ] WORKFILE=/var/run/motd.dynamic + set -e case $1 in @@ -60,14 +64,18 @@ log_daemon_msg Updating $DESC $NAME # Just incase someone has removed their motd file. -[ -f /var/run/motd ] || touch /var/run/motd -[ -f /var/run/motd.orig ] || cp /var/run/motd /var/run/motd.orig +[ -f $WORKFILE ] || touch $WORKFILE +[ -f /var/run/motd.orig ] || cp $WORKFILE /var/run/motd.orig +# If the tempfile is less than 15 minutes old, object, otherwise +# we'll assume that something went wrong and remove it. if [ -f $TEMPFILE ]; then - echo Hey, $TEMPFILE already exists 12 - ls -l /var/run/motd* 12 - ps -ef | grep mythtv-status 12 - cat /var/run/motd.new 12 + AGE=$(stat -c %Z $TEMPFILE); + if expr $AGE \ $(date +'%s') - 900 + then +log_warning_msg I think another $NAME is running. +exit 1 + fi fi cp /var/run/motd.orig $TEMPFILE @@ -77,12 +85,10 @@ $DAEMON $ARGS -h $HOST $TEMPFILE || ret=$? if [ $ret -eq 0 -o $ret -eq 1 ]; then if [ ! -f $TEMPFILE ]; then -# My file has gone away. WTF?! Spit out some debugging. - echo Odd, $TEMPFILE has gone away. Start: $date, End: $(date) 12 -ls -l /var/run/motd* 12 -ps -ef | grep mythtv-status 12 +log_failure_msg My temporary
Bug#691548: unblock: mythtv-status/0.10.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mythtv-status The version in unstable removes some extraneous debugging from the init.d (bug #681684) and adds support for the new dynamic motd logic in Wheezy (bug #688034 should probably be flagged as Important). diff -Nru mythtv-status-0.10.2/debian/changelog mythtv-status-0.10.2/debian/changelog --- mythtv-status-0.10.2/debian/changelog 2012-07-07 16:34:36.0 +1200 +++ mythtv-status-0.10.2/debian/changelog 2012-10-02 21:50:36.0 +1300 @@ -1,3 +1,10 @@ +mythtv-status (0.10.2-2) unstable; urgency=low + + * Handle a stale temp file more gracefully (Closes: #681684) + * base-files 6.11 in Wheezy uses /var/run/motd.dynamic (Closes: #688034) + + -- Andrew Ruthven and...@etc.gen.nz Tue, 02 Oct 2012 21:50:10 +1300 + mythtv-status (0.10.2-1) unstable; urgency=low * New upstream release. (Closes: #680358) diff -Nru mythtv-status-0.10.2/debian/init.d mythtv-status-0.10.2/debian/init.d --- mythtv-status-0.10.2/debian/init.d 2012-03-22 23:33:58.0 +1300 +++ mythtv-status-0.10.2/debian/init.d 2012-10-02 21:47:53.0 +1300 @@ -21,8 +21,8 @@ # Provides: mythtv-status # Required-Start:$remote_fs # Required-Stop: $remote_fs -# Should-Start: $named mythtv-backend -# Should-Stop: $named mythtv-backend +# Should-Start: $named mythtv-backend $motd +# Should-Stop: $named mythtv-backend $motd # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Update the MOTD with the MythTV status @@ -35,6 +35,7 @@ NAME=mythtv-status# Introduce the short server's name here DESC=MythTV Status # Introduce a short description here TEMPFILE=/var/run/motd.mythtv-status +WORKFILE=/var/run/motd test -x $DAEMON || exit 0 @@ -53,6 +54,9 @@ exit fi +# Debian Wheezy+ handles the MOTD differently. +[ -f /var/run/motd.dynamic ] WORKFILE=/var/run/motd.dynamic + set -e case $1 in @@ -60,14 +64,18 @@ log_daemon_msg Updating $DESC $NAME # Just incase someone has removed their motd file. -[ -f /var/run/motd ] || touch /var/run/motd -[ -f /var/run/motd.orig ] || cp /var/run/motd /var/run/motd.orig +[ -f $WORKFILE ] || touch $WORKFILE +[ -f /var/run/motd.orig ] || cp $WORKFILE /var/run/motd.orig +# If the tempfile is less than 15 minutes old, object, otherwise +# we'll assume that something went wrong and remove it. if [ -f $TEMPFILE ]; then - echo Hey, $TEMPFILE already exists 12 - ls -l /var/run/motd* 12 - ps -ef | grep mythtv-status 12 - cat /var/run/motd.new 12 + AGE=$(stat -c %Z $TEMPFILE); + if expr $AGE \ $(date +'%s') - 900 + then +log_warning_msg I think another $NAME is running. +exit 1 + fi fi cp /var/run/motd.orig $TEMPFILE @@ -77,12 +85,10 @@ $DAEMON $ARGS -h $HOST $TEMPFILE || ret=$? if [ $ret -eq 0 -o $ret -eq 1 ]; then if [ ! -f $TEMPFILE ]; then -# My file has gone away. WTF?! Spit out some debugging. - echo Odd, $TEMPFILE has gone away. Start: $date, End: $(date) 12 -ls -l /var/run/motd* 12 -ps -ef | grep mythtv-status 12 +log_failure_msg My temporary file has gone away, failed. +exit 1 else -mv $TEMPFILE /var/run/motd +mv $TEMPFILE $WORKFILE fi log_end_msg 0 else @@ -91,7 +97,7 @@ ;; stop) log_daemon_msg Stopping $DESC $NAME -[ -f /var/run/motd.orig ] cp /var/run/motd.orig /var/run/motd +[ -f /var/run/motd.orig ] cp /var/run/motd.orig $WORKFILE rm /var/run/motd.orig log_end_msg 0 ;; @@ -100,11 +106,11 @@ log_failure_msg $NAME is not running exit 1 fi -if [ ! -f /var/run/motd ]; then - log_failure_msg $NAME is not running (no motd file!) +if [ ! -f $WORKFILE ]; then + log_failure_msg $NAME is not running (no motd file)! exit 1 fi -if [ $(date -d 15 minutes ago +%s) -gt $(stat -c %Y /var/run/motd) ] +if [ $(date -d 15 minutes ago +%s) -gt $(stat -c %Y $WORKFILE) ] then log_failure_msg $NAME is not running (motd file is stale) exit 1 diff -Nru mythtv-status-0.10.2/debian/mythtv-status.1 mythtv-status-0.10.2/debian/mythtv-status.1 --- mythtv-status-0.10.2/debian/mythtv-status.1 2012-07-07 22:39:39.0 +1200 +++ mythtv-status-0.10.2/debian/mythtv-status.1 2012-10-03 14:39:16.0 +1300 @@ -124,7 +124,7 @@ .\ .\ .IX Title MYTHTV-STATUS 1 -.TH MYTHTV-STATUS 1 2012-07-07 perl v5.14.2 User Contributed Perl Documentation +.TH MYTHTV-STATUS 1 2012-07-12 perl v5.14.2 User Contributed Perl Documentation .\ For nroff, turn off justification. Always turn off hyphenation; it makes .\ way too many mistakes in technical documents. .if n .ad
Bug#423458: dnscap packaged
On Thu, 2012-10-25 at 15:00 +0200, Marc Haber wrote: On Tue, Feb 07, 2012 at 12:39:18AM +, Andrew Ruthven wrote: Our git repo for dnscap is here: http://git.catalyst.net.nz/dnscap.git I'm waiting for a minor update to a patch we're carrying, then we can upload it to unstable. What's the status for that? Is that minor update there now? Yes, and you're prodded made me go and check for a new release, so I've just updated the packaging to dnscap v141. I am a DD and can sponsor your upload to unstable. If you want me to help, please build a source package and make it available for me. Having it sponsored would be great. I'm a DM, so I'll be able to continue to maintain it once it is uploaded. I should really get around to becoming a DD. ;) The git repo is here: http://git.catalyst.net.nz/dnscap.git You can grab the source package and an amd64 binary from here: http://magnus.catalyst.net.nz/~puck/dnscap_debian.tar.gz Thank you! -- Andrew Ruthven, Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://lca2013.linux.org.au signature.asc Description: This is a digitally signed message part
Bug#688034: mythtv-status: No update of /etc/motd anymore
Hi Stephan, Hmmm, it looks like /run/motd.dynamic is only updated by /etc/init.d/motd at system boot. Perhaps if the LSB headers for mythtv-status are updated to depend on motd I can then subvert motd.dynamic okay. Looks like I need to update my home Sid box to test this out. Cheers! -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://linux.conf.au signature.asc Description: This is a digitally signed message part
Bug#688034: mythtv-status: No update of /etc/motd anymore
Hi Stephan, Would you please try the attached patch? This is against the init.d in version 0.10.2-1. Cheers! On Tue, 2012-09-18 at 15:16 +0200, Stephan Seitz wrote: Package: mythtv-status Version: 0.10.2-1 Severity: normal Tags: patch Dear Maintainer, since the last update of base-files the output of mythtv-status isn’t found in /etc/motd anymore. Checking /etc/init.d/motd and /etc/init.d/mythtv-status I think the upgrade should go into /var/run/motd.dynamic which is read by pam_motd together with the static /etc/motd. I have change /etc/init.d/mythtv-status so that it works for me (patch attached). Maybe it is useful for you as well. Shade and sweet water! Stephan -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.4-Dom0 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mythtv-status depends on: ii debconf [debconf-2.0] 1.5.46 ii libconfig-auto-perl0.42-1 ii libdate-manip-perl 6.32-1 ii libmime-tools-perl 5.503-1 ii libsys-sigaction-perl 0.13-1 ii libwww-perl6.04-1 ii libxml-libxml-perl 2.0001+dfsg-1 ii perl 5.14.2-13 Versions of packages mythtv-status recommends: ii libmythtv-perl0.25.2-dmo3 ii libnet-upnp-perl 1.4.2-1 Versions of packages mythtv-status suggests: ii molly-guard 0.4.5-1 -- debconf information excluded -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://linux.conf.au diff --git a/debian/init.d b/debian/init.d index f7a083e..7b8c024 100644 --- a/debian/init.d +++ b/debian/init.d @@ -21,8 +21,8 @@ # Provides: mythtv-status # Required-Start:$remote_fs # Required-Stop: $remote_fs -# Should-Start: $named mythtv-backend -# Should-Stop: $named mythtv-backend +# Should-Start: $named mythtv-backend $motd +# Should-Stop: $named mythtv-backend $motd # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Update the MOTD with the MythTV status @@ -60,14 +60,18 @@ case $1 in log_daemon_msg Updating $DESC $NAME # Just incase someone has removed their motd file. -[ -f /var/run/motd ] || touch /var/run/motd -[ -f /var/run/motd.orig ] || cp /var/run/motd /var/run/motd.orig +[ -f /var/run/motd.dynamic ] || touch /var/run/motd.dynamic +[ -f /var/run/motd.orig ] || cp /var/run/motd.dynamic /var/run/motd.orig +# If the tempfile is less than 15 minutes old, object, otherwise +# we'll assume that something went wrong and remove it. if [ -f $TEMPFILE ]; then - echo Hey, $TEMPFILE already exists 12 - ls -l /var/run/motd* 12 - ps -ef | grep mythtv-status 12 - cat /var/run/motd.new 12 + AGE=$(stat -c %Z $TEMPFILE); + if expr $AGE \ $(date +'%s') - 900 + then +log_warning_msg I think another $NAME is running. +exit 1 + fi fi cp /var/run/motd.orig $TEMPFILE @@ -77,12 +81,10 @@ case $1 in $DAEMON $ARGS -h $HOST $TEMPFILE || ret=$? if [ $ret -eq 0 -o $ret -eq 1 ]; then if [ ! -f $TEMPFILE ]; then -# My file has gone away. WTF?! Spit out some debugging. - echo Odd, $TEMPFILE has gone away. Start: $date, End: $(date) 12 -ls -l /var/run/motd* 12 -ps -ef | grep mythtv-status 12 +log_failure_msg My temporary file has gone away, failed. +exit 1 else -mv $TEMPFILE /var/run/motd +mv $TEMPFILE /var/run/motd.dynamic fi log_end_msg 0 else @@ -91,7 +93,7 @@ case $1 in ;; stop) log_daemon_msg Stopping $DESC $NAME -[ -f /var/run/motd.orig ] cp /var/run/motd.orig /var/run/motd +[ -f /var/run/motd.orig ] cp /var/run/motd.orig /var/run/motd.dynamic rm /var/run/motd.orig log_end_msg 0 ;; @@ -100,11 +102,11 @@ case $1 in log_failure_msg $NAME is not running exit 1 fi -if [ ! -f /var/run/motd ]; then +if [ ! -f /var/run/motd.dynamic ]; then log_failure_msg $NAME is not running (no motd file!) exit 1 fi -if [ $(date -d 15 minutes ago +%s) -gt $(stat -c %Y /var/run/motd) ] +if [ $(date -d 15 minutes ago +%s) -gt $(stat -c %Y /var/run/motd.dynamic) ] then log_failure_msg $NAME is not running (motd file is stale) exit 1 signature.asc Description: This is a digitally signed message part
Bug#681684: mythtv-status: cron job crashes if /var/run/motd.mythtv-status already present
Ah, that's some stale debug code that shouldn't have been there. I've also added some logic so that a stale TEMPFILE should be ignored on the basis that mythtv-status either died, or was killed. I'll push out an new version shortly. On Sun, 2012-07-15 at 16:09 +0100, Julian Gilbey wrote: Package: mythtv-status Version: 0.10.1-1 Tags: patch I'm getting loads of messages to root saying things along the lines of: Hey, /var/run/motd.mythtv-status already exists -rw-r--r-- 1 root root 355 Jul 15 12:04 /var/run/motd -rw-r--r-- 1 root root 355 Jul 15 12:05 /var/run/motd.mythtv-status -rw-r--r-- 1 root root 355 Jul 15 12:05 /var/run/motd.orig root 14201 14045 0 16:02 pts/300:00:00 /bin/sh /etc/init.d/mythtv-status reload root 14209 14201 0 16:02 pts/300:00:00 grep mythtv-status cat: /var/run/motd.new: No such file or directory Is the intention for /etc/init.d/mythtv-status to bomb out when the temp file already exists or to keep on going, but just to warn? If the first, then the /etc/init.d/mythtv-status file should say in the block on lines 66-71: if [ -f $TEMPFILE ]; then [...] exit 1 fi If it is not, then the cat /var/run/motd.new command should be protected (line 70) by writing: cat /var/run/motd.new 12 || true This way, the script will continue even if the file does not exist (which will probably be the case). (A separate bug: if it is giving a warning, it should probably use the log_warning_msg function instead of echo.) Julian -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://linux.conf.au signature.asc Description: This is a digitally signed message part
Bug#434570: A way to detect nfsroot
Hey, I've just run into this bug as well. Is it possibly to have /etc/init.d/mountnfs.sh could detect if nfsroot is being used. Perhaps look if /proc/cmdline contains nfsroot= ? Or if ip= is set. Cheers! -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://linux.conf.au signature.asc Description: This is a digitally signed message part
Bug#680753: unblock: mythtv-status/0.10.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mythtv-status This version fixes BTS bugs: #680358 - Bug if the next recording is more than 1 day in the future #680372 - Danish debconf translation As I'm also the upstream maintainer fixing 680358 by cutting a new release seemed a good idea. I also noticed yesterday a bug with UTF-8, and another one which required two occurences of 23058 with 58. The debdiff is fairly length because I added a test case for the UTF-8 bug, and fixed a failing test. Cheers! unblock mythtv-status/0.10.2-1 -- System Information: Debian Release: wheezy/sid APT prefers common APT policy: (500, 'common'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.20-vs2.3.2.10-beng (SMP w/2 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ (charmap=ISO-8859-1) (ignored: LC_ALL set to en_NZ) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679055: istgt: Add support to reload the istgt.conf file.
Hi Arno, On Tue, 2012-06-26 at 11:11 +0200, Arno Töll wrote: On 26.06.2012 06:07, and...@etc.gen.nz wrote: The attached patch, ported from FreeBSD, adds a refresh command to istgtcontrol to allow telling istgt to reload istgt.conf and update the running configuration, all without restarting the daemon. Did you contact the upstream author? As far as I'm informed he was planning to add reload LUN reload support to the upcoming 0.5 series but I didn't hear since. I haven't contacted the upstream author, two reasons, 1) I was hoping that the FreeBSD guys had, and 2) I wanted to make sure I submitted the patch to the BTS with at least a few days before the wheezy freeze! Anyway, thanks for your patch which looks quite good at a first glance. I'll review and test later so that it will end in Wheezy before the freeze. Thank you, that'd be awesome. A couple of things I've noticed that are missing (in my opinion), no SIGHUP support in the daemon and to have a LogicalUnit refresh you need to change the name of it (this is arguably understandable) and the other feature that would be nice to have is to change the advertised size of the block device if it changes. But I didn't actually write the patch and I'm not about to delve in the bowels of the code! Cheers! -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://linux.conf.au signature.asc Description: This is a digitally signed message part
Bug#678932: Correction: Depends on libio-socket-inet6-perl
Hi Dom, On Mon, 2012-06-25 at 07:56 +0100, Dom wrote: Apologies, The actual package I needed to install was libio-socket-inet6-perl. libsocket6-perl was pulled in as a dependancy of libio-socket-inet6-perl. This is actually a missing dependency from the libmythtv-perl package which is what installs /usr/share/perl5/IO/Socket/INET/MythTV.pm . This package isn't in Debian, but rather comes from deb-multimedia.org, so I've Cc'ed Christian in rather than transfer the bug. Cheers! -- Andrew Ruthven Wellington, New Zealand At home: and...@etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://linux.conf.au signature.asc Description: This is a digitally signed message part