Thanks for the list. Do you mind sharing how you generated it?
On Thu, Jan 24, 2019 at 3:00 PM Dr. Tobias Quathamer
wrote:
> Am 24.01.2019 um 09:12 schrieb Emilio Pozuelo Monfort:
> > On 24/01/2019 08:58, Michael Stapelberg wrote:
> >> Last time, pochu@ (cc'ed) helpfully
On Tue, Jul 3, 2018 at 10:29 PM, Adam D. Barratt
wrote:
> On Tue, 2018-07-03 at 22:20 +0200, Michael Stapelberg wrote:
> >
> >
> > On Tue, Jul 3, 2018 at 10:01 PM, Adam D. Barratt > barratt.org.uk> wrote:
> [...]
> > > The metadata for #891919 suggests tha
On Tue, Jul 3, 2018 at 10:01 PM, Adam D. Barratt
wrote:
> Control: tags -1 + moreinfo
>
> On Mon, 2018-03-12 at 19:23 +0100, Michael Stapelberg wrote:
> > I would like to apply the attached update to the i3-wm package to
> > satisfy a user
> > request (#891919) fo
)
+
+ -- Michael Stapelberg <stapelb...@debian.org> Mon, 12 Mar 2018 19:16:41 +0100
+
i3-wm (4.13-1) unstable; urgency=medium
* New upstream release.
diff -Nru i3-wm-4.13/debian/patches/fix-mark-restart-crash.patch
i3-wm-4.13/debian/patches/fix-mark-restart-crash.patch
--- i3-wm-4.13/debian/patch
the wanna-build access question.
On Sat, Feb 17, 2018 at 9:07 AM, Emilio Pozuelo Monfort <po...@debian.org>
wrote:
> Sorry for the delay,
>
> On 11/02/18 14:28, Michael Stapelberg wrote:
> > On Sat, Feb 10, 2018 at 1:14 PM, Philipp Kern <pk...@debian.org> wrote:
> >
&g
On Sat, Feb 10, 2018 at 1:14 PM, Philipp Kern <pk...@debian.org> wrote:
> On 02/10/2018 09:26 AM, Julien Cristau wrote:
> > On Tue, Jan 30, 2018 at 20:45:44 +0100, Emilio Pozuelo Monfort wrote:
> >
> >> On 30/01/18 08:54, Michael Stapelberg wrote:
> >>>
binNMUs for unstable.
On Wed, Jan 31, 2018 at 5:03 PM, Moritz Muehlenhoff <j...@inutil.org> wrote:
> On Wed, Jan 31, 2018 at 04:16:21PM +0100, Michael Stapelberg wrote:
> > [+t...@security.debian.org for their okay]
> >
> > On Wed, Jan 31, 2018 at 3:38 PM, Bastian Bla
[+t...@security.debian.org for their okay]
On Wed, Jan 31, 2018 at 3:38 PM, Bastian Blank <wa...@debian.org> wrote:
> On Wed, Jan 31, 2018 at 03:01:18PM +0100, Michael Stapelberg wrote:
> > Hector Oron pointed out in the Debian RT that the release-team should
> give
>
the release team please file such a ticket?
Thanks!
On Wed, Jan 31, 2018 at 11:35 AM, Philipp Kern <pk...@debian.org> wrote:
> On 31.01.2018 09:20, Michael Stapelberg wrote:
> > Thanks for the quick reply.
> >
> > Can we grant myself access for the time being
Thanks! Filed #94 for the security issue. Will contact the wanna-build
team directly.
On Tue, Jan 30, 2018 at 8:45 PM, Emilio Pozuelo Monfort <po...@debian.org>
wrote:
> On 30/01/18 08:54, Michael Stapelberg wrote:
> > This would also be very helpful for fixing securit
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
To address security issue #888777, please schedule binNMUs for the following
binary packages:
nmu docker.io
nmu prometheus-blackbox-exporter
nmu coyim
nmu rawdns
nmu goiardi
nmu
This would also be very helpful for fixing security issue #888777.
On Sun, Jan 28, 2018 at 8:31 PM, Michael Stapelberg <stapelb...@debian.org>
wrote:
> Friendly ping? Still interested in getting this set up.
>
> On Mon, Jan 8, 2018 at 6:56 PM, Michael Stapelberg <stapelb...@d
Friendly ping? Still interested in getting this set up.
On Mon, Jan 8, 2018 at 6:56 PM, Michael Stapelberg <stapelb...@debian.org>
wrote:
> Thanks for the clarification.
>
> So, what’s the next step in this process? Should I file a bug somewhere?
> An RT ticket? An email?
>
Thanks for the clarification.
So, what’s the next step in this process? Should I file a bug somewhere? An
RT ticket? An email?
On Sun, Jan 7, 2018 at 11:26 AM, Julien Cristau <jcris...@debian.org> wrote:
> On Sat, Jan 6, 2018 at 19:19:13 +0100, Michael Stapelberg wrote:
>
>
On Sat, Jan 6, 2018 at 6:30 PM, Julien Cristau <jcris...@debian.org> wrote:
> [moving this off the (now archived) bug]
>
Thanks for the pointer!
>
> On Sat, Jan 6, 2018 at 18:00:48 +0100, Michael Stapelberg wrote:
>
> > On Sat, Dec 2, 2017 at 8:20 PM, Julien C
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
+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
On Tue, May 16, 2017 at 6:46 AM, Steve Langasek <vor...@debian.org> wrote:
> On Mon, May 15, 2017 at 03:17:03PM -0700, Steve Langasek wrote:
> > On Mon, May 15, 2017 at 08:56:08AM +0200, Michael Stapelberg wrote:
> > > >> Package: golang-github-gosexy-gettext-dev
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package golang-github-armon-go-metrics
This is part of the fix for Debian bug #860608: Go library packages
should not use the Built-Using tag at all, and a few packages are
On Sat, May 6, 2017 at 2:20 PM, Michael Stapelberg <stapelb...@debian.org>
wrote:
>
>
> On Tue, May 2, 2017 at 10:23 AM, Michael Hudson-Doyle <
> michael.hud...@canonical.com> wrote:
>
>> On 2 May 2017 at 19:23, Michael Stapelberg <stapelb...@debian.org>
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package golang-pty
This is part of the fix for Debian bug #860608: Go library packages
should not use the Built-Using tag at all, and a few packages are
still referencing a
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package golang-objx
This is part of the fix for Debian bug #860608: Go library packages
should not use the Built-Using tag at all, and a few packages are
still referencing a
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package golang-github-hashicorp-go-msgpack
This is part of the fix for Debian bug #860608: Go library packages
should not use the Built-Using tag at all, and a few packages
On Tue, May 2, 2017 at 10:23 AM, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> On 2 May 2017 at 19:23, Michael Stapelberg <stapelb...@debian.org> wrote:
>
>> Sorry for the late reply, I’ve been swamped.
>>
>> On Fri, Apr 21, 2017 at 10:28
Sorry for the late reply, I’ve been swamped.
On Fri, Apr 21, 2017 at 10:28 AM, Niels Thykier <ni...@thykier.net> wrote:
> Michael Stapelberg:
> > On Fri, Apr 21, 2017 at 9:45 AM, Niels Thykier <ni...@thykier.net>
> wrote:
> >
> >> [...]
> >>&g
On Fri, Apr 21, 2017 at 9:45 AM, Niels Thykier <ni...@thykier.net> wrote:
> Michael Stapelberg:
> > On Wed, Apr 19, 2017 at 12:05 PM, Michael Hudson-Doyle <
> > michael.hud...@canonical.com> wrote:
> >
> >> [...]
> >>> 0.7.0+ds-3),
On Wed, Apr 19, 2017 at 12:05 PM, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> On 19 April 2017 at 20:55, Lucas Nussbaum <lu...@debian.org> wrote:
>
>> On 19/04/17 at 09:05 +0200, Michael Stapelberg wrote:
>> > This is the third time an FTBFS r
+0100
@@ -1,3 +1,10 @@
+irssi-plugin-robustirc (0.6-4) unstable; urgency=medium
+
+ * debian/patches/uint64.diff: add missing % signs which rendered the patch
+entirely broken (closes: #854434)
+
+ -- Michael Stapelberg <stapelb...@debian.org> Mon, 20 Feb 2017 08:46:32 +0100
+
irssi-
@@ -1,3 +1,11 @@
+irssi-plugin-robustirc (0.6-3) unstable; urgency=medium
+
+ * debian/patches/uint64.diff: ensure last_id_id and last_id_reply are 64-bit
+(fixes duplicate messages showing up when network connection is
+interrupted) (closes: #854434)
+
+ -- Michael Stapelberg <stap
+++ i3-wm-4.8/debian/changelog 2015-02-15 13:24:57.0 +0100
@@ -1,3 +1,11 @@
+i3-wm (4.8-2) unstable; urgency=medium
+
+ * Backport two bugfixes:
+- backport-dpi-fix.patch (Closes: #778460)
+- backport-i3bar-tray-fix.patch (Closes: #778461)
+
+ -- Michael Stapelberg stapelb
://wiki.debian.org/ReleaseGoals/systemd
== Advocates ==
* Michael Stapelberg (stapelb...@debian.org)
* Gergely Nagy (alger...@debian.org)
* Moritz Muehlenhoff (j...@debian.org)
* Tollef Fog Heen (tfh...@debian.org)
* Michael Biebl (bi...@debian.org)
== Volunteers ==
* Michael Stapelberg (stapelb
Hi Bastian,
Bastian Blank wa...@debian.org writes:
On Sat, Sep 21, 2013 at 06:45:41PM +0200, Michael Stapelberg wrote:
sysvinit scripts that many of our current packages provide. However,
when a package ships a native systemd service file in addition to the
sysvinit script, users enjoy
Hi Bastian,
Bastian Blank wa...@debian.org writes:
On Sat, Sep 21, 2013 at 07:50:22PM +0200, Michael Stapelberg wrote:
Bastian Blank wa...@debian.org writes:
On Sat, Sep 21, 2013 at 06:45:41PM +0200, Michael Stapelberg wrote:
sysvinit scripts that many of our current packages provide
Hi Mattia,
Mattia Dongili malat...@debian.org writes:
I don't see a valid reason to get a newer version in wheezy at this
stage of the freeze.
I agree.
Adam, here is the diffstat between the version currently in wheezy
(upstream git commit f07ee8aa562b7cee0138a88219169f501fd9c041) and the
Hi Mattia,
Mattia Dongili malat...@debian.org writes:
yes it is, that's what Al did already:
http://ftp-master.debian.org/new/acpica-unix_20130214-0.3.html
I see.
release-team: What’s your take on this? Can we get the new version into
Debian in time for wheezy or how should we handle this?
--
@@
+openbox (3.5.0-7) unstable; urgency=low
+
+ * QA upload.
+ * Apply upstream fix for an infinite loop when disabling RandR outputs
+(Closes: #697571)
+
+ -- Michael Stapelberg stapelb...@debian.org Wed, 27 Mar 2013 14:16:10 +0100
+
openbox (3.5.0-6) unstable; urgency=low
* Add
Hi,
at this point I cannot spend any more time on this bug report.
Given that the bug report is without maintainer reply since more than
half a year, and there are merely 160 people voting for it via popcon, I
wonder if we should just drop file-rc from Debian in order to reduce
init system
Hi Adam,
Adam D. Barratt a...@adam-barratt.org.uk writes:
Ping?
As discussed in IRC, I uploaded 2.92+dfsg1-0.1~deb7u1 to
testing-proposed-updates.
Sorry for taking so long to react on this one.
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
Hi Adam,
Adam D. Barratt a...@adam-barratt.org.uk writes:
Hmm, presumably it worked at some point, given there are armhf binaries
in unstable. :-(
Ack. My guess is that it worked with gcc 4.6.
Given that 3.1 appears never to have managed to build on several
architectures in unstable (a
Hi Adam,
Adam D. Barratt a...@adam-barratt.org.uk writes:
I wasn't particularly suggesting re-introducing 3.0 to unstable.
However, given that packages from tpu get essentially no testing at all
(no pun intended) before hitting testing, being able to prove a patch in
unstable first avoids a
Hi Adam,
Michael Stapelberg stapelb...@debian.org writes:
Therefore, I will now build it on armhf, which will take around a day.
Update: the armhf build failed because about 100 testcases fail.
I have no clue on how to fix this and can’t spend much more time on
debugging this either.
Given
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: tpu
Hello,
I would like to upload clang/3.0-6.1+deb7u0 to testing-proposed-updates
to fix #693208 in wheezy. At the moment, 3.0-6 is in testing, 3.1-8 is
in unstable.
#693208 is about clang
Hi Adam,
Adam D. Barratt a...@adam-barratt.org.uk writes:
What's the status of getting this fixed in unstable, as already
requested by Julien in #693208?
Why is it necessary to fix this in unstable? This’d require introducing
an epoch. Let me know if you insist on it, but I don’t understand why
Hi Adam,
Adam D. Barratt a...@adam-barratt.org.uk writes:
Ideas welcome...
At this point I’d vote to disable the testsuite entirely for getting
this into wheezy.
Daniel, what do you say?
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a
On Wed, 12 Dec 2012 12:11:12 +0100
intrigeri intrig...@debian.org wrote:
A new upstream release was uploaded to unstable since then, so this
unblock request can't be satisfied as is. Please either update or
close it.
Actually, unstable got 2.64-1 _and_ 2.65-1 by now.
Simon: Are these uploads
-01 18:35:47.0 +0100
@@ -1,3 +1,10 @@
+i3-wm (4.2-2) unstable; urgency=low
+
+ * Backport commit 1089b0b to fix resizing floating windows by height
+(Closes: #696758)
+
+ -- Michael Stapelberg stapelb...@debian.org Tue, 01 Jan 2013 18:35:45 +0100
+
i3-wm (4.2-1) unstable; urgency=low
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: tpu
Hello,
I would like to upload xdotool/1:2.20100701.2961-3+deb7u1 to
testing-proposed-updates to fix #680824 in wheezy. At the moment,
1:2.20100701.2961-3 is in wheezy and 1:2.20110530.1-6
Hi Adam,
Adam D. Barratt a...@adam-barratt.org.uk writes:
I would like to upload xdotool/1:2.20100701.2961-3+deb7u1 to
testing-proposed-updates to fix #680824 in wheezy. At the moment,
1:2.20100701.2961-3 is in wheezy and 1:2.20110530.1-6 (many
changes) is in unstable.
Please go ahead;
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package simile-timeline
The only change from 2.3.0-1 (currently in testing) is that a different
version of the orig tarball is used to fix #645133 (generated
files included
owned by nobody:nogroup.
+
+ -- Michael Stapelberg stapelb...@debian.org Tue, 04 Dec 2012 22:05:44 +0100
+
ample (0.5.7-6.1) unstable; urgency=low
* Non-maintainer upload.
diff -u ample-0.5.7/debian/postrm ample-0.5.7/debian/postrm
--- ample-0.5.7/debian/postrm
+++ ample-0.5.7/debian/postrm
Hi,
Michael Stapelberg stapelb...@debian.org writes:
Dear release team: I want to upload a new version of libanyevent-i3-perl
to testing-proposed-updates which is the same version as currently in
testing + commits
http://code.stapelberg.de/git/AnyEvent-I3/commit/?id
On Mon, 26 Nov 2012 13:25:12 +0100
Sylvestre Ledru sylves...@debian.org wrote:
Regarding the current clang packages in the repositories (3.0 in
testing, 3.1 in unstable), you would have to add an epoch to
downgrade clang to 3.0 in unstable with a fix and then have to fix
migrated to
On Mon, 16 Jan 2012 21:20:07 +0100
Lucas Nussbaum lu...@debian.org wrote:
Dear release team, at some point before the wheezy release, we need to
decide what to do with Ruby 1.9.X on ia64. It has been broken for
months, and hasn't seen any activity in Debian (#539141) or upstream
.
+ * Add patch to add -P in the init script with either iproute or net-tools
+(Thanks Andreas Henriksson)
+ * Add dependency on iproute | net-tools (Closes: #672926)
+
+ -- Michael Stapelberg stapelb...@debian.org Mon, 03 Dec 2012 23:42:59 +0100
+
oidentd (2.0.8-4) unstable; urgency=low
Squires)
+(Closes: #600549)
+
+ -- Michael Stapelberg stapelb...@debian.org Tue, 04 Dec 2012 01:13:59 +0100
+
mscompress (0.3-3.1) unstable; urgency=low
* Non-maintainer upload.
diff -u mscompress-0.3/debian/control mscompress-0.3/debian/control
--- mscompress-0.3/debian/control
+++ mscompress
Hi Adam,
Adam D. Barratt a...@adam-barratt.org.uk writes:
Thanks for the fix. Given that the only change is to a file in debian/,
why is it being applied as a patch rather than simply updating the init
script?
Good point, this was my mistake.
How do we proceed?
--
Best regards,
Michael
--
Hi Julien,
Julien Cristau jcris...@debian.org writes:
You fix it in 2.0.8-4.2?
Done. In 2.0.8-5 since it’s a QA upload since oidentd has been orphaned.
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
sigit is a low-popcon package (18 installations) which was last updated
upstream in 2006 and in Debian in 2007.
http://bugs.debian.org/673369 is a message to the maintainer without
reply since
Hi Niels,
Niels Thykier ni...@thykier.net writes:
By the looks of it, I think a removal from sid is probably a better
choice in the long run. If you agree, lets reassign this bug to the
ftp-masters. Once/if the ftp-masters remove sigit from sid, it will
probably disappear from testing
Hi,
intrigeri intrig...@debian.org writes:
I'm not speaking for the release team, but I believe this unblock
request would get more attention and have more chances to be processed
if the proposed changes were limited to fixing the bugs that need to
be fixed.
I think so, too.
Dear release
Hi Cyril,
Cyril Brulebois k...@debian.org writes:
Rule #1 on http://release.debian.org/wheezy/freeze_policy.html
I understand that, but at the same time there is rule #6 and I’d
definitely say that it applies :-).
In any case, the decision is up to the release team. I can only say that
I think
/changelog2012-08-02 00:07:33.0 +0200
@@ -1,3 +1,10 @@
+dunst (0.2.0-3) unstable; urgency=low
+
+ * Ship org.knopwob.dunst.service so that dunst gets D-Bus-activated when a
+notification arrives. Thanks Jakob Haufe. (Closes: #683089)
+
+ -- Michael Stapelberg stapelb...@debian.org Thu
)
+
+ -- Michael Stapelberg stapelb...@debian.org Fri, 20 Jul 2012 17:59:38 +0200
+
golang (2:1.0.2-1) unstable; urgency=low
[ Ondřej Surý ]
* Imported Upstream version 1.0.2
* Update Vcs fields to reflect new git repository location
- * Kill get-orig-source, since 1.0.0, the tarballs can
to uploaders
+ * bump standards-version (no changes required)
+ * set debian/source/format to 3.0 (quilt)
+ * update debian/copyright
+ * add Vcs-* fields to debian/control
+
+ -- Michael Stapelberg stapelb...@debian.org Fri, 20 Jul 2012 18:52:16 +0200
+
libanyevent-i3-perl (0.08-1) unstable
Hi Julien,
Quoting Julien Cristau (2012-07-20 20:23:08)
+ * set debian/source/format to 3.0 (quilt)
That's anything bug minimal.
Why is it not minimal? The package itself does not contain any patches,
so I consider this a formality. Could you elaborate please?
Best regards,
Michael
--
To
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package dunst
The only change between 0.2.0-1 (currently in testing) and 0.2.0-2 is
the added Provides: notification-daemon, which fixes bug #681732.
Here is the debdiff:
Hi releaseteam,
Could you please integrate mxallowd 1.6b-2 from unstable (currently in
incoming.debian.org) to lenny? It fixes the following important bugs:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503408
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503409
67 matches
Mail list logo
