Bug#878443: dgit: add checkout subcommand?

Package: dgit Version: 3.12 Severity: wishlist % dgit clone i3status % cd i3status % git branch * dgit/sid At this point, I can use “dgit fetch jessie” to get the dgit/dgit/jessie remote populated, but I don’t see an easy way to actually check it out. Currently, I’m using: % git checkout -b

Bug#878433: dgit-maint-merge(7) workflow for converting an existing package does not work

it expects • it mentions “debian.tar”, which I assume doesn’t apply here • it claims my package uses source format v2.0, but I’m using v3.0 On Fri, Oct 13, 2017 at 10:37 AM, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote: > Michael Stapelberg writes ("Bug#878433: dgit-maint-mer

Bug#878433: dgit-maint-merge(7) workflow for converting an existing package does not work

Package: dgit Version: 3.12 Severity: normal I read the following section of the dgit-maint-merge(7): https://manpages.debian.org/stretch/dgit/dgit-maint-merge.7.en.html#Existing_git_history_using_another_workflow And tried to apply it to one of my packages: % gbp clone

Bug#811565: [uscan] git mode: allow for scanning repositories without tags

Almost a month has passed. What’s the current status? The pkg-go group is still eagerly waiting for this. If there is any way we can help, please let us know. On Mon, Sep 18, 2017 at 3:04 AM, Osamu Aoki wrote: > Hi, > > On Mon, Sep 18, 2017 at 01:20:22PM +0800, Shengjing

Bug#878164: dunst systemd service and dbus service are both suboptimal

I can’t find it either. Maybe Simon (the last dbus uploader) knows? On Tue, Oct 10, 2017 at 11:43 PM, Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote: > On Tue 2017-10-10 22:27:23 +0200, Michael Stapelberg wrote: >> Okay, so I think the issue is that we have a

Bug#839108: [pkg-go] Bug#839108: dh-golang: Please document behavior and variables used

Thanks for the hint, I wasn’t aware of that! I’ll document the variables and upload a new version. On Sat, Sep 23, 2017 at 12:08 PM, Shengjing Zhu <i...@zhsj.me> wrote: > On Tue, 20 Jun 2017 09:49:26 +0200 Michael Stapelberg > <stapelb...@debian.org> wrote: >> Hi Guille

Bug#878164: dunst systemd service and dbus service are both suboptimal

dunst.service. Verify using systemctl --user status dunst.service. On Tue, Oct 10, 2017 at 8:12 PM, Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote: > On Tue 2017-10-10 19:16:28 +0200, Michael Stapelberg wrote: >> Please refer to https://github.com/systemd/systemd/issues/892. I have

Bug#878164: dunst systemd service and dbus service are both suboptimal

Please refer to https://github.com/systemd/systemd/issues/892. I have only skimmed that, so if you could figure out what we need to change upstream in dunst or downstream in the packaging to make this work, that’d be appreciated. Thanks! On Tue, Oct 10, 2017 at 6:31 PM, Daniel Kahn Gillmor

Bug#878161: nm.debian.org: suggested gpg command line does not work

Package: nm.debian.org Severity: normal On e.g. https://nm.debian.org/process/388/advocate/statement/create, I read the following prose: > Use gpg --clearsign --default-key to generate the signed statement. However, the --default-key option expects an argument: % gpg --clearsign --default-key

Bug#877969: please add a way to clone a specific version of a package

Package: dgit Version: 3.12 Severity: wishlist Currently, dgit can clone packages from a specific suite (e.g. sid). It would be useful if dgit could clone a specific version of a package, too. The use-case is to obtain a git working directory in a ready-to-build state for the specific package

Bug#865069: [Pkg-raspi-maintainers] Bug#865069: uncompress kernel images

Sorry for the long radio silence. On Thu, Jun 22, 2017 at 2:58 AM, Martin Schitter <m...@mur.at> wrote: > On 2017-06-19 11:39, Michael Stapelberg wrote: >> >> Could you supply a tested patch which accomplishes this please? I only >> use the Debian kernel images.

Bug#877911: Please set CONFIG_BRCMFMAC_SDIO=y for WiFi on the Raspberry Pi 3

Source: linux Severity: wishlist Thanks for the linux/4.13.4-1 upload! On the Raspberry Pi 3, the Broadcom BRCM43430 chip is connected via SDIO. Hence, the brcmfmac driver’s config option CONFIG_BRCMFMAC_SDIO=y needs to be set, otherwise the driver won’t find the chip. I verified this works by

Bug#255572: ITP: cc65 -- Cross development suite for 65xxx processors, necesary for nesicide env

Indeed, I can confirm that compilation works now. Can you upload the package to Debian please? :) On Fri, Oct 6, 2017 at 11:26 PM, László Böszörményi (GCS) <g...@debian.org> wrote: > On Fri, Oct 6, 2017 at 10:26 PM, Michael Stapelberg > <stapelb...@debian.org> wrote: >

Bug#255572: ITP: cc65 -- Cross development suite for 65xxx processors, necesary for nesicide env

hare/cc65/include. On Fri, Oct 6, 2017 at 9:21 PM, László Böszörményi (GCS) <g...@debian.org> wrote: > On Fri, Oct 6, 2017 at 11:00 AM, Michael Stapelberg > <stapelb...@debian.org> wrote: >> Great! Thanks for letting us know, please keep us posted on the progress. > OK, you

Bug#877802: include file name and line number in output

Sorry for not being more clear: when I run lintian (notably, without -i), I get output such as: % lintian dunst_1.2.0-1_amd64.changes I: dunst source: testsuite-autopkgtest-missing P: dunst source: debian-watch-may-check-gpg-signature I: dunst: dbus-session-service-wrong-name

Bug#255572: ITP: cc65 -- Cross development suite for 65xxx processors, necesary for nesicide env

Great! Thanks for letting us know, please keep us posted on the progress. On Fri, Oct 6, 2017 at 1:21 AM, László Böszörményi (GCS) <g...@debian.org> wrote: > On Fri, Oct 6, 2017 at 7:39 AM, Michael Stapelberg > <stapelb...@debian.org> wrote: >> László, did you

Bug#877855: debootstrap does not carry --components across --foreign/--second-stage

Package: debootstrap Version: 1.0.91 Severity: normal This debootstrap invocation generates the expected sources.list: % sudo debootstrap --components main,contrib,non-free \ --variant - testing /tmp/bootstr http://deb.debian.org/debian % cat /tmp/bootstr/etc/apt/sources.list deb

Bug#255572: ITP: cc65 -- Cross development suite for 65xxx processors, necesary for nesicide env

László, did you see my message? Any word on this? I’m still interested :) On Thu, Nov 3, 2016 at 9:06 AM, Michael Stapelberg <stapelb...@debian.org> wrote: > Hi László, > > "László Böszörményi (GCS)" <g...@debian.org> writes: >> [1] https://ftp-master.

Bug#877802: include file name and line number in output

Package: lintian Version: 2.5.54 Severity: wishlist It would be great if lintian could include the relevant file name and line number in each line of output. That way, users could easily jump to the issue at hand by using their editor’s “compilation mode” (Emacs), quickfix (Vim) or similar

Bug#876692: owfs FTBFS with debhelper 10.9

Thanks for taking care of it. I’ll let you handle it :) On Mon, Oct 2, 2017 at 1:35 AM, Vincent Danjean <vdanj...@debian.org> wrote: > Le 02/10/2017 à 09:49, Michael Stapelberg a écrit : >> Hi Vincent, >> > [...] >> Are you working on a fix for this or would you lik

Bug#876692: owfs FTBFS with debhelper 10.9

Hi Vincent, Adrian Bunk writes: > Source: owfs > Version: 3.1p5-1 > Severity: serious > Tags: buster sid > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/owfs.html > > ... >debian/rules override_dh_makeshlibs > make[1]: Entering directory

Bug#877285: libyajl_s.a should be named libyajl.a

Package: libyajl-dev Version: 2.1.0-2+b3 Severity: normal When statically linking software which uses libyajl, the linker can’t find libyajl as-is: % ../configure LDFLAGS=-static % make […] /usr/bin/ld: cannot find -lyajl […] Copying the file helps: % sudo cp

Bug#876106: lists.debian.org: please create debian-go mailing list

Package: lists.debian.org Severity: wishlist Name: debian-go Rationale: replacement for our current list on alioth Category: Developers Subscription Policy: open Post Policy: open Web Archive: yes Short description: Debian Go Packaging Team Long description: We, the Debian Go Packaging Team,

Bug#875884: i3status FTCBFS: uses the build architecture toolchain

control: tags -1 + pending Applied, thanks. In the future, using git-format-patch and/or a corresponding upstream pull request would make things slightly easier for me :) On Fri, Sep 15, 2017 at 5:06 PM, Helmut Grohne wrote: > Source: i3status > Version: 2.11-1 > Tags: patch

Bug#874763: Ability to install local debs (or volatile sources) not documented in manpage

Package: apt Version: 1.5~rc1 Severity: normal apt supports installing packages via e.g. “apt install ./keyring.deb”. Not everybody knows this¹, and in fact it turns out to not be documented in the manpage. Apparently, the feature was originally introduced in commit

Bug#874595: dunst crashed with SIGSEGV in xdgSearchableConfigDirectories()

control: reassign -1 libxdg-basedir1 This crash seems to happen in libxdg-basedir: > #0 0x7f0e1fda8c28 in xdgSearchableConfigDirectories () at > /usr/lib/libxdg-basedir.so.1 > #1 0x7f0e1fda8e0b in xdgConfigOpen () at /usr/lib/libxdg-basedir.so.1

Bug#853515: libwebsockets: ftbfs with GCC-7

Hi, Gianfranco Costamagna writes: > the new 2.3.0 release seems to build correctly with gcc-7 If cherry-picking the fixes, or packaging the new upstream release isn’t feasible, I think we could fix this issue the same way that

Bug#853579: nut: ftbfs with GCC-7

Hi, Laurent, do you have time to upload a fix, or would you prefer an NMU? This is somewhat time-critical, because this RC bug will cause freeradius to be removed from testing. -- Best regards, Michael

Bug#871062: collectd: FTBFS: client.c:621:23: error: '%s' directive output may be truncated writing up to 1023 bytes into a region of size 1010 [-Werror=format-truncation=]

Hi, Steve Langasek writes: > The attached one-liner patch corrects this build failure by simply ignoring > the (IMHO uninteresting) new gcc-7 warning. I think this is a reasonable > way to handle this until it gets fixed upstream. Marc, Sebastian, does either of

Bug#872600: [Pkg-raspi-maintainers] Bug#872600: RFP: open-rpi-firmware -- Open source VPU side bootloader for Raspberry Pi

FWIW, I think it doesn’t make sense to package this (or upload it, rather) until we can run a headless Raspberry Pi system with it (i.e. once DMA, Ethernet and USB work). I don’t expect tooling to be a big issue. On Sat, Aug 19, 2017 at 7:18 AM, Petter Reinholdtsen wrote: > >

Bug#872158: [Pkg-freeradius-maintainers] Bug#872158: logrotate config file overrides global options for other log files

control: tags -1 + pending Thanks for the detailed report. I uploaded a fix. On Mon, Aug 14, 2017 at 7:36 PM, Justin Pasher wrote: > Package: freeradius > Version: 3.0.12+dfsg-5+deb9u1 > > The logrotate config file that ships with freeradius sets global options > in its

Bug#872163: Doesn’t compress files due to override_dh_compress

Source: xchat Version: 2.8.8-10 Severity: normal Tags: patch In binary package “xchat”, changelog, changelog.Debian and xchat.1 are not compressed, even though they should be. This is because of the following override in debian/rules: override_dh_compress: dh_compress -X.pl

Bug#811565: [uscan] git mode: allow for scanning repositories without tags

Ah, thanks for the correction. In that case, we should probably try a shallow clone first, then fall back to a non-shallow clone :). On Fri, Aug 11, 2017 at 7:41 PM, Shengjing Zhu <i...@zhsj.me> wrote: > On Fri, Aug 11, 2017 at 9:55 PM, Michael Stapelberg > <stapelb...@debian.or

Bug#811565: [uscan] git mode: allow for scanning repositories without tags

, I’d recommend first translating https URLs into git URLs, then (later) use the GitHub API. On Fri, Aug 11, 2017 at 6:51 AM, Osamu Aoki <os...@debian.org> wrote: > Hi, > > On Thu, Aug 10, 2017 at 09:37:33AM +0200, Michael Stapelberg wrote: > > Here’s an example: https://gith

Bug#859867: [buildd-tools-devel] Bug#859867: Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

Sounds good. Are you willing to contribute to this? I have no experience with autopkgtest at all. On Thu, Aug 10, 2017 at 6:41 AM, Raphael Hertzog <hert...@debian.org> wrote: > Hello guys, > > On Sat, 05 Aug 2017, Michael Stapelberg wrote: > > Thanks for the thorough rev

Bug#811565: [pkg-go] Bug#811565: [uscan] git mode: allow for scanning repositories without tags

On Thu, Aug 10, 2017 at 9:34 AM, Osamu Aoki <os...@debian.org> wrote: > Hi, > > On Thu, Aug 10, 2017 at 08:19:20AM +0200, Michael Stapelberg wrote: > > On Thu, Aug 10, 2017 at 6:50 AM, Osamu Aoki <os...@debian.org> wrote: > > > > The functionality

Bug#811565: [pkg-go] Bug#811565: [uscan] git mode: allow for scanning repositories without tags

On Thu, Aug 10, 2017 at 6:50 AM, Osamu Aoki <os...@debian.org> wrote: > Hi, > > > On Wed, Aug 09, 2017 at 07:54:05AM -0700, Michael Stapelberg wrote: > > Thanks for sharing your tool! > > Thank you but I don't use go nor perl regulary :-( I wish uscan was in > P

Bug#811565: [pkg-go] Bug#811565: [uscan] git mode: allow for scanning repositories without tags

On Wed, Aug 9, 2017 at 6:54 PM, Shengjing Zhu <i...@zhsj.me> wrote: > Thanks for the comment. > > On Wed, Aug 9, 2017 at 10:54 PM, Michael Stapelberg > <stapelb...@debian.org> wrote: > > 1. I think that infrastructure which the pkg-go team critically and very

Bug#811565: [pkg-go] Bug#811565: [uscan] git mode: allow for scanning repositories without tags

Thanks for sharing your tool! I also considered implementing such a tool, but ultimately decided against it for a number of reasons: 1. I think that infrastructure which the pkg-go team critically and very visibly depends on should eventually be hosted by DSA under debian.org. I don’t see them

Bug#863089: Please provide post-processed logs output for manpages.d.o

are missing as well in the new files. > > indeed. Michael, please! :) > > Thanks! > > > -- > cheers, > Holger > -- Best regards, Michael From 000720e089dbe0ae731a1f2dba139d1290146f31 Mon Sep 17 00:00:00 2001 From: Michael Stapelberg <stapelb...@debian.org>

Bug#870829: Contradicting warnings/errors: useless-autoreconf-build-depends vs. missing-build-dependency-for-dh-addon

On Sat, Aug 5, 2017 at 6:25 PM, Mattia Rizzolo <mat...@debian.org> wrote: > On Sat, Aug 05, 2017 at 05:47:39PM +0200, Michael Stapelberg wrote: > > build-dependency was unnecessary with debhelper ≥ 10 and should be > removed: > > > > W: mdocml source: useless-auto

Bug#859867: [buildd-tools-devel] Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

control: block -1 by 870260 Thanks for the thorough review. It took me quite a bit to address all these comments :). Find the updated patch attached, and answers inline: On Wed, Aug 2, 2017 at 8:11 AM, Johannes Schauer <jo...@debian.org> wrote: > Quoting Michael Stapelberg (2017-08-01

Bug#870829: Contradicting warnings/errors: useless-autoreconf-build-depends vs. missing-build-dependency-for-dh-addon

Package: lintian Version: 2.5.52 Severity: normal When packaging mdocml 1.14.3, lintian noted that the autotools-dev build-dependency was unnecessary with debhelper ≥ 10 and should be removed: W: mdocml source: useless-autoreconf-build-depends autotools-dev After doing that, lintian noted that

Bug#863089: [Piuparts-devel] Bug#863089: Bug#863089: Bug#863089: Bug#863089: Please provide post-processed logs output for manpages.d.o

But I already added golang-any to Build-Depends in my patch? Also, I thought the update-piuparts-slave-setup script deploys directly from git? `go version` on pejacevic seems to work fine, so I’m not sure I follow what the issue is. On Thu, Aug 3, 2017 at 6:09 AM, Holger Levsen

Bug#863089: [Piuparts-devel] Bug#863089: Bug#863089: Bug#863089: Please provide post-processed logs output for manpages.d.o

On Thu, Aug 3, 2017 at 5:42 AM, Holger Levsen <hol...@layer-acht.org> wrote: > On Tue, Aug 01, 2017 at 11:30:11AM +0200, Michael Stapelberg wrote: > > Sure: https://github.com/stapelberg/piuparts/commits/distill > > cool, thanks, merged and deployed on pejacevic! > Thank

Bug#870451: sbuild-update-all is missing the executable bit

Package: sbuild Version: 0.73.0-4 Severity: normal The instructions in /usr/share/doc/sbuild/examples/sbuild-update-all recommend to directly run the script from cron: # 1. Update all sbuild chroots four times a day (at 00:15/06:15/12:15/18:15): # # 15 */6 * * * root

Bug#859867: [buildd-tools-devel] Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

Alright! Patch attached and provided inline, for your convenience: >From b29b1faf6bafb4b6e51b4e99d0febc81abbb543c Mon Sep 17 00:00:00 2001 From: Michael Stapelberg <stapelb...@debian.org> Date: Tue, 1 Aug 2017 23:13:36 +0200 Subject: [PATCH] add sbuild-debian-developer-setup package

Bug#863089: [Piuparts-devel] Bug#863089: Bug#863089: Please provide post-processed logs output for manpages.d.o

org> wrote: > Hi Michael, > > sorry for the delay here… > > On Thu, Jun 01, 2017 at 09:30:50PM +0200, Michael Stapelberg wrote: > > Alright, then. Find attached a patch against the piuparts git to add > > debiman-piuparts-distill. You can build it by running “go b

Bug#859867: [buildd-tools-devel] Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

That works for me :). How shall we proceed? Should I prepare a patch against the sbuild package? On Tue, Aug 1, 2017 at 11:00 AM, Johannes Schauer <jo...@debian.org> wrote: > Quoting Michael Stapelberg (2017-08-01 10:51:41) > > I think the following suggestion takes care of all t

Bug#859867: [buildd-tools-devel] Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

On Mon, Jul 31, 2017 at 4:24 PM, Johannes Schauer <jo...@debian.org> wrote: > Quoting Michael Stapelberg (2017-07-31 14:19:16) > > Unless I’m mistaken, the following is what we’d need to recommend to new > > users: > > > > % sudo apt install sbuild apt-cacher-n

Bug#868041: [Pkg-freeradius-maintainers] Bug#868041: freeradius: jessie-backports available

someone steps up and commits to the additional maintenance effort, I’m afraid I don’t have the capacity to move this along. Thanks! On Fri, Jul 21, 2017 at 11:13 AM, Maxime Lareo <maxime.la...@infomaniak.com> wrote: > Hi there, > > On 07/11/2017 04:02 PM, Michael Stapelberg wrote: >

Bug#859867: [buildd-tools-devel] Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

On Sun, Jul 30, 2017 at 7:53 PM, Johannes Schauer <jo...@debian.org> wrote: > Hi, > > Quoting Michael Stapelberg (2017-06-02 18:23:02) > > Thanks for the review. Answers inline: > > sorry for the delay. I'm under a pile of work and this wasn't on the top > of my >

Bug#870263: [PATCH] Update defaults (--build-arch-all, --run-lintian)

rom: Michael Stapelberg <stapelb...@debian.org> Date: Mon, 31 Jul 2017 14:05:02 +0200 Subject: [PATCH 1/2] Build arch: all packages by default. --- lib/Sbuild/Conf.pm | 2 +- man/sbuild.1.in| 5 ++--- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/lib/Sbuild/Conf.pm b/l

Bug#870260: [PATCH] sbuild-createchroot: add --command-prefix

rom: Michael Stapelberg <stapelb...@debian.org> Date: Mon, 31 Jul 2017 13:48:03 +0200 Subject: [PATCH] sbuild-createchroot: add --command-prefix Successfully tested using: % sudo ./bin/sbuild-createchroot --include=eatmydata \ --chroot-suffix=eatmydata --command-prefix=eatmydata \ stretch /s

Bug#859867: [buildd-tools-devel] Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

josch, friendly ping? :) On Fri, Jun 2, 2017 at 6:23 PM, Michael Stapelberg <stapelb...@debian.org> wrote: > Thanks for the review. Answers inline: > > On Wed, May 24, 2017 at 11:03 AM, Johannes Schauer <jo...@debian.org> > wrote: > >> Hi, >> >>

Bug#811565: [uscan] git mode: allow for scanning repositories without tags

On Sun, Jul 30, 2017 at 6:10 AM, Osamu Aoki <os...@debian.org> wrote: > Hi, > > (I switched my ISP. No more osamua...@e01.itscom.net Thanks for the > reminder) > > On Sat, Jul 29, 2017 at 06:44:43PM +0200, Michael Stapelberg wrote: > > Hi Osamu, > > >

Bug#811565: [uscan] git mode: allow for scanning repositories without tags

Hi Osamu, Sorry for the late reply, and thanks for looking into this! Replies inline: Osamu Aoki writes: > How should we explicitly specify such variables, I guess it should be > through "opts=..." such as: > > opts="mode=git, pretty=0.0~git%cd.%h, date=%Y%m%d%H%M"

Bug#870056: nmu: robustirc-bridge_1.7-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu This is the first binNMU I schedule, mostly to see how this all works before I file a larger one. I realized that robustirc-bridge (and other Go binary packages) were built using the Go 1.7

Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

rari <tin...@tincho.org> wrote: > > On 27/07/17 14:05, Michael Stapelberg wrote: > >> It does break the API, as evinced by one build failure. > >> > >> I’m not aware of situations in the past where we created a new binary. > >> How would we name them? Is it wo

Bug#869800: [pkg-go] Bug#869800: Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

On Thu, Jul 27, 2017 at 6:23 AM, Martín Ferrari <tin...@tincho.org> wrote: > On 27/07/17 14:05, Michael Stapelberg wrote: > > It does break the API, as evinced by one build failure. > > > > I’m not aware of situations in the past where we created a new binary.

Bug#869800: [pkg-go] Bug#869800: Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

It does break the API, as evinced by one build failure. I’m not aware of situations in the past where we created a new binary. How would we name them? Is it worth the trouble? Personally, I would just update the new version + the fixed affected packages in one go, to reduce the breakage to a

Bug#869859: Please set Acquire::Retries default to >0

Source: apt Severity: wishlist Occasionally, networks (such as the internet) are unreliable. I have observed many transient network failures, be it between my machines and the Debian mirror network, or be it in the CDNs behind deb.debian.org. This causes pain in many different scenarios; I’d like

Bug#869682: [Pkg-freeradius-maintainers] Bug#869682: freeradius: Import ldap module in python_rlm freeradius crash

[+cc debian-python] Sorry, I have no idea what’s going wrong here or how to fix this. Maybe the debian-python team can help? On Tue, Jul 25, 2017 at 5:32 PM, Gabriel Detraz wrote: > Package: freeradius > Version: 3.0.12+dfsg-5 > Severity: normal > > Dear Maintainer, > > I

Bug#869376: [pkg-go] Bug#869376: FTBFS: newer golang-github-stretchr-testify breaks tests

An upstream fix is now available at https://github.com/ncw/rclone/commit/db6009126df98a0a35975ca2fb7271a8493e1e30 Do you want to apply it, or shall I go ahead? On Sat, Jul 22, 2017 at 8:58 PM, Michael Stapelberg <stapelb...@debian.org> wrote: > Source: rclone > Version: 1.36-

Bug#761627: libtomcrypt-dev: arch-dependent file in "Multi-Arch: same" package

AM, François Poirotte <fpoiro...@gmail.com> wrote: > Hi Michael, > > I believe the freeze has been lifted following the release of Debian > Stretch a few weeks ago. > Could you take another look at the proposed patch? > > Best regards, > François > > On 05/14/201

Bug#862755: RFS: golang-github-go-ini-ini/1.27.0-1

Hi Félix, Thanks for your work on the package. Félix Sipma writes: > Here are the remaining issues (logs attached): > > 2017/07/10 21:02:40 FAILED: grafana_2.6.0+dfsg-3 (see > buildlogs/grafana_2.6.0+dfsg-3) > 2017/07/10 21:02:40 FAILED: nomad_0.4.0+dfsg-1 (see >

Bug#868937: ITP: golang-github-kurin-blazer -- A Golang library for Backblaze's B2.

Package: wnpp Severity: wishlist Owner: Michael Stapelberg <stapelb...@debian.org> * Package name: golang-github-kurin-blazer Version : 0.0~git20170711.0.612082e-1 Upstream Author : Toby Burress * URL : https://github.com/kurin/blazer * License : Apac

Bug#868761: [Pkg-freeradius-maintainers] Bug#868761: freeradius: New upstream version 2.2.10 fixing security critical bugs

Help with this would be appreciated. I’m not sure about the appropriate processes, so if you could clarify that with the security/release team, that’d be helpful. On Tue, Jul 18, 2017 at 3:51 AM, Karsten Heymann wrote: > Subject: freeradius: New upstream version

Bug#868765: [Pkg-freeradius-maintainers] Bug#868765: freeradius: New upstream version 3.0.15 fixing security critical bugs

Thanks for the heads-up. I’ll work on packaging the new upstream release later today. On Tue, Jul 18, 2017 at 4:06 AM, Karsten Heymann wrote: > Package: freeradius > Version: 3.0.12+dfsg-5 > Severity: grave > Tags: upstream security > Justification: user security hole

Bug#867913: i3lock in Gnome allows window view/kill etc

Pull requests or hints in an upstream issue (at https://github.com/i3/i3lock) to improve the situation are very welcome :). On Wed, Jul 12, 2017 at 11:28 AM, Barak A. Pearlmutter < ba...@pearlmutter.net> wrote: > I think you're right: it is not possible to lock the screen properly > in xwayland,

Bug#868041: [Pkg-freeradius-maintainers] Bug#868041: freeradius: jessie-backports available

On Tue, Jul 11, 2017 at 3:52 PM, Maxime Lareo wrote: > Package: freeradius > Version: 3.0.12+dfsg-5~bpo8+1 > Severity: wishlist > User: product...@infomaniak.com > Usertag: infomaniak.com-packaging > > Dear Maintainer, > > We needed freeradius 3.X on jessie at work,

Bug#867913: i3lock in Gnome allows window view/kill etc

On first glance, this sounds like an issue with XWayland, so possibly this issue needs to be re-assigned. Note that i3lock is not tested under Wayland at all, and won’t be for the foreseeable future. Please use a screenlocker for Wayland instead. On Mon, Jul 10, 2017 at 4:38 PM, Barak A.

Bug#867246: dh_installman incorrectly optimized away when using --fail-missing and building arch-any packages only

On Wed, Jul 5, 2017 at 12:30 PM, Niels Thykier <ni...@thykier.net> wrote: > Control: tags -1 patch > > On Wed, 05 Jul 2017 08:18:49 +0200 Michael Stapelberg > <stapelb...@debian.org> wrote: > > Package: debhelper > > Version: 10.6.1 > > Severity: normal

Bug#867246: dh_installman incorrectly optimized away when using --fail-missing and building arch-any packages only

Package: debhelper Version: 10.6.1 Severity: normal See [1] for an example: commit [2] switched to dh_missing --fail-missing, which works when building arch:all packages as well, but fails when building architecture-dependent packages only (such as the buildds do). This can be worked around by

Bug#852166: Contains a large number of auto-generated stub manpages

> Dear Michael, > > Le dimanche 22 janvier 2017 à 09:56 +0100, Michael Stapelberg a écrit : > > Package: liblapack-doc-man > > Version: 3.7.0-1 > > Severity: normal > > > > liblapack-doc-man installs 10770 files into /usr/share/man/man3, all of > which >

Bug#866978: [Pkg-freeradius-maintainers] Bug#866978: freeradius FTBFS: recipe for target 'override_dh_missing' failed

I’m stumped as to why sbuild works locally, but not on the buildds o_O. On Mon, Jul 3, 2017 at 12:57 AM, Adrian Bunk wrote: > Source: freeradius > Version: 3.0.14+dfsg-1 > Severity: serious > > https://buildd.debian.org/status/package.php?p=freeradius=sid > > ... >

Bug#865087: [Pkg-freeradius-maintainers] Bug#865087: freeradius-mysql: Obsolete and misleading files in /etc/freeradius/sql/

ma.sql -> main/mysql/schema.sql > wimax.conf -> main/mysql/extras/wimax/queries.conf > wimax.sql -> main/mysql/extras/wimax/schema.sql > > On Monday 19 June 2017, Michael Stapelberg wrote: > > I don’t use FreeRADIUS with MySQL, so I never noticed. Do you suggest to > > just

Bug#864945: [Pkg-raspi-maintainers] Bug#864945: wrong sort order in kernel postinst hook

control: tags -1 + pending Thanks for the report and patch. I reproduced the problem and verified your fix works as intended. The patch is now committed and will be included in the next upload:

Bug#839108: [pkg-go] Bug#839108: dh-golang: Please document behavior and variables used

On Wed, Jun 21, 2017 at 1:21 AM, Ian Campbell <i...@debian.org> wrote: > On Wed, 2017-06-21 at 06:28 +0200, Guillem Jover wrote: > > Hi! > > > > On Tue, 2017-06-20 at 09:49:26 +0200, Michael Stapelberg wrote: > > > > > Guillem Jover <guil...@debian.

Bug#822743: dh-golang: should assist in calculating -dev packages Depends:

Hi, currently going through the bugs of dh-golang. Is there anything that remains to be done here? If so, could someone please summarize the discussion and explain what it is? Thanks! -- Best regards, Michael

Bug#822668: Processed: cloning 822386, reassign -1 to dh-golang ..., severity of -1 is important

control: severity -1 wishlist control: retitle -1 Make dh_golang work without --buildsystem golang Hi, Michael Hudson-Doyle <michael.hud...@canonical.com> writes: > On 27 April 2016 at 19:22, Michael Stapelberg <stapelb...@debian.org> wrote: >> Can you please explain why dh

Bug#839108: dh-golang: Please document behavior and variables used

Hi Guillem, Thanks for your report! Guillem Jover writes: > Please document at least the variables from the environment that > directly affect the behavior such as GOPATH, DH_GOPKG, > DH_GOLANG_INSTALL_ALL, DH_GOLANG_INSTALL_EXTRA, DH_GOLANG_BUILDPKG, >

Bug#841074: dh-golang: Do not emit misc:Built-Using substvar for arch:all packages

control: tags -1 pending Hi Guillem, Guillem Jover writes: > This helper generates a misc:Built-Using substvar for all involved > packages, but that seems wrong for packages that do not statically > embed any Go modules when building, in case they are -dev packages > that

Bug#865069: [Pkg-raspi-maintainers] Bug#865069: uncompress kernel images

Could you supply a tested patch which accomplishes this please? I only use the Debian kernel images. Thanks. On Sun, Jun 18, 2017 at 5:17 PM, Martin Schitter wrote: > Package: raspi3-firmware > Version: 1.20170317-4 > > the raspi3-firmware kernel postinstall hook should take care

Bug#865087: [Pkg-freeradius-maintainers] Bug#865087: freeradius-mysql: Obsolete and misleading files in /etc/freeradius/sql/

I don’t use FreeRADIUS with MySQL, so I never noticed. Do you suggest to just delete the file? On Mon, Jun 19, 2017 at 12:39 AM, Ondrej Zary wrote: > Package: freeradius-mysql > Version: 3.0.12+dfsg-5 > Severity: normal > > Dear Maintainer, > freeradius-mysql package

Bug#864343: Add mips64el for 1.6

1.8 is already in the archive, so I’m not sure why you’re talking about 1.6 :). Note that the mips64el port is marked experimental by upstream. I’m not sure whether we should include experimental ports. On Wed, Jun 7, 2017 at 2:08 AM, Mathieu Malaterre wrote: > Package:

Bug#863673: [Pkg-freeradius-maintainers] Bug#863673: CVE-2017-9148: FreeRADIUS TLS resumption authentication bypass

it with respect for > a jessie(-security) upload: > > On Thu, Jun 01, 2017 at 11:09:17PM +0200, Michael Stapelberg wrote: > > The original question of how to proceed still stands. I sent the patch in > > my previous message; do you want me to upload it, or do you want to > upload

Bug#859867: [buildd-tools-devel] Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

Thanks for the review. Answers inline: On Wed, May 24, 2017 at 11:03 AM, Johannes Schauer wrote: > Hi, > > Quoting Geert Stappers (2017-05-21 08:43:31) > > the debian/postinst now here inline > > thanks, that allows me to comment easily. > > > # Add to group sbuild all

Bug#863673: [Pkg-freeradius-maintainers] Bug#863673: CVE-2017-9148: FreeRADIUS TLS resumption authentication bypass

uploaded to anything but unstable/experimental). On Thu, Jun 1, 2017 at 9:34 AM, Salvatore Bonaccorso <car...@debian.org> wrote: > Hi > > On Thu, Jun 01, 2017 at 08:54:57AM +0200, Michael Stapelberg wrote: > > I got the idea from https://www.debian.org/security/faq

Bug#863089: [Piuparts-devel] Bug#863089: Please provide post-processed logs output for manpages.d.o

1:32:46AM +0200, Michael Stapelberg wrote: > > The fact that these manpages are included at all is what the > > slave-alternative handling got us :) > > ah! > > > > ok, I'll request this once we got closer… (see below) > > Thanks :). > > done (as you kn

Bug#863707: simple-tpm-pk11: FTBFS: ./m4/test-driver: line 107: 4695 Aborted (core dumped)

Thomas, here are the steps to reproduce using docker. They should be easily transferrable to a VM: % docker run -t -i debian:sid /bin/bash root# echo deb-src http://deb.debian.org/debian sid main >> /etc/apt/sources.list root# apt update root# apt build-dep simple-tpm-pk11 root# apt source

Bug#863673: [Pkg-freeradius-maintainers] Bug#863673: CVE-2017-9148: FreeRADIUS TLS resumption authentication bypass

. Please let me know how to proceed from here. On Wed, May 31, 2017 at 10:32 PM, Moritz Muehlenhoff <j...@debian.org> wrote: > On Tue, May 30, 2017 at 05:50:20PM +0200, Michael Stapelberg wrote: > > security-team, can you take care of applying the patch to stable and > > oldsta

Bug#863707: simple-tpm-pk11: FTBFS: ./m4/test-driver: line 107: 4695 Aborted (core dumped)

Thanks for the report. Do you have a VM in which upstream (Thomas Habets) could reproduce the failure? Or any other details about the setup that might help? On Tue, May 30, 2017 at 10:43 AM, Chris Lamb wrote: > Source: simple-tpm-pk11 > Version: 0.06-1 > Severity: serious >

Bug#859934: [Pkg-utopia-maintainers] Bug#859934: enable captive portal checking by default

Thank you very much for working on this. One nit regarding the package long description: we should mention the privacy implications of this package. My suggestion: No user data is transmitted in the connectivity checks, but merely contacting the Debian connectivity check servers reveals that the

Bug#863089: [Piuparts-devel] Bug#863089: Please provide post-processed logs output for manpages.d.o

On Tue, May 30, 2017 at 4:43 PM, Holger Levsen <hol...@layer-acht.org> wrote: > On Tue, May 23, 2017 at 09:55:11AM +0200, Michael Stapelberg wrote: > > I’m not subscribed, so please keep me cc'ed :). > > ok! > > > > ok, so only parsing 4 suites… how long did the

Bug#863735: unblock: freeradius/3.0.12+dfsg-5

+dfsg/debian/changelog 2017-05-30 17:18:34.0 +0200 @@ -1,3 +1,9 @@ +freeradius (3.0.12+dfsg-5) unstable; urgency=high + + * disable session cache to address CVE-2017-9148 (closes: #863673) + + -- Michael Stapelberg <stapelb...@debian.org> Tue, 30 May 2017 17:18:34 +0200 + free

Bug#863673: [Pkg-freeradius-maintainers] Bug#863673: CVE-2017-9148: FreeRADIUS TLS resumption authentication bypass

you. On Tue, May 30, 2017 at 8:29 AM, Michael Stapelberg <stapelb...@debian.org> wrote: > control: owner -1 ! > > I prepared a patch for this issue and emailed the FreeRADIUS security team > asking for review. I’ll upload the patch once they confirm its > effectiveness. >

Bug#863673: [Pkg-freeradius-maintainers] Bug#863673: CVE-2017-9148: FreeRADIUS TLS resumption authentication bypass

control: owner -1 ! I prepared a patch for this issue and emailed the FreeRADIUS security team asking for review. I’ll upload the patch once they confirm its effectiveness. On Mon, May 29, 2017 at 11:16 PM, Guido Günther wrote: > Package: freeradius > Version: 3.0.12+dfsg-4 >

Bug#863089: [Piuparts-devel] Bug#863089: Please provide post-processed logs output for manpages.d.o

On Tue, May 23, 2017 at 9:55 AM, Michael Stapelberg <stapelb...@debian.org> wrote: > > > On Tue, May 23, 2017 at 3:34 AM, Holger Levsen <hol...@layer-acht.org> > wrote: > >> Hi Michael, >> >> are you subscribed to this bug or do you need cc:s? >&

Bug#859867: [buildd-tools-devel] Bug#859867: Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

Thanks for the feedback. Any suggestions as to how the script should be called, and which options it should have, if any? On Wed, May 24, 2017 at 1:17 AM, Johannes Schauer <jo...@debian.org> wrote: > Hello all, > > Quoting Ansgar Burchardt (2017-05-24 08:42:37) > > Michae

<    1   2   3   4   5   6   7   8   9   10   >