ature unstable of @x-vfio-user-server
+
+ -- Michael Tokarev Fri, 01 Nov 2024 16:50:46 +0300
+
qemu (1:7.2+dfsg-7+deb12u7) bookworm; urgency=medium
* update to upstream 7.2.13 stable/bugfix release, v7.2.13.diff,
diff -Nru qemu-7.2+dfsg/debian/patches/series
qemu-7.2+dfsg/debian/patches/series
--
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: llvm-toolchain...@packages.debian.org
Control: affects -1 + src:llvm-toolchain-15
Apparently, llvm-toolchain-15 in bookworm has been
bin-NMUed on mips64el the same way as it's b
08.09.2024 19:26, Sebastian Ramacher wrote:
samba and its reverse dependencies migrated.
Yeah, yesterday iirc.
I hope to make this libndr thing to be a real library
so it wont require manual processing in cases like this.
/mjt
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: sa...@packages.debian.org, pkg-samba-ma...@lists.alioth.debian.org
Control: affects -1 + src:samba
There's a transition needed from libndr4 to libndr5.
This is a pure virtua
09.05.2024 14:53, Michael Tokarev wrote:
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: q...@packages.debian.org, pkg-qemu-de...@lists.alioth.debian.org
Control: affects -1 + src:qemu
[ Reason ]
There were 2
On Tue, 6 Feb 2024 19:37:46 +0300 Michael Tokarev wrote:
03.02.2024 12:47, Michael Tokarev wrote:
>>> It looks like we broke suspend/resume in this version of qemu.
>> Oops. Is that related to the cryptsetup failure, or a separate issue?
>
> Yes, it is related to cryptsetu
06.02.2024 20:55, Adam D. Barratt :
On Tue, 2024-02-06 at 20:49 +0300, Michael Tokarev wrote:
..
The change isn't small per se, as the commit is rather large (mostly
due to many changed tests, - it changes order of output in quite some
places). Here's the diffstat:
mon
06.02.2024 20:33, Adam D. Barratt:
On Tue, 2024-02-06 at 19:37 +0300, Michael Tokarev wrote:
problematic upstream commit (on master) is this one:
https://gitlab.com/qemu-project/qemu/-/commit/effd60c878176bcaf97fa7ce2b12d04bb8ead6f7
Technically we already froze p-u for 12.5 on Sunday evening
03.02.2024 12:47, Michael Tokarev wrote:
It looks like we broke suspend/resume in this version of qemu.
Oops. Is that related to the cryptsetup failure, or a separate issue?
Yes, it is related to cryptsetup autopkgtest failure. It looks
like this is the only place where suspend/resume code
03.02.2024 12:43, Adam D. Barratt :
..
I'm aware of the autopkgtest failure with cryptsetup, working on it
now.
It looks like we broke suspend/resume in this version of qemu.
Oops. Is that related to the cryptsetup failure, or a separate issue?
Yes, it is related to cryptsetup autopkgtest fai
01.02.2024 11:40, Adam D Barratt :
..
Package: qemu
Version: 7.2+dfsg-7+deb12u4
Explanation: new upstream stable release; irtio-net: correctly copy vnet header
when flushing TX [CVE-2023-6693]; fix null pointer dereference issue
[CVE-2023-6683]
There's a typo here, should be virtio-net.
I'm
x-812-fix-846-by-using-the-SSL_OP_IGNORE_UNEXPECTE.patch from upstream
+to fix error log flooding when using DNS over TLS with openssl 3.0.
+Closes: #1038243
+
+ -- Michael Tokarev Mon, 25 Sep 2023 18:45:40 +0300
+
unbound (1.17.1-2) unstable; urgency=medium
* unbound-helper: ret
23.09.2023 23:45, Adam D. Barratt wrote:
Control: tags -1 confirmed
On Thu, 2023-08-17 at 12:54 +0300, Michael Tokarev wrote:
There's a next upstream qemu stable/bugfix release, fixing a
big number of various issues, including 3 (minor) security
issues too. The full list is in the chan
10.09.2023 13:11, Michael Tokarev:
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: sa...@packages.debian.org, pkg-samba-ma...@lists.alioth.debian.org
Control: affects -1 + src:samba
[ Reason ]
There's a
x VRMA page size for ISA v3.0
+ - target/i386: Check CR0.TS before enter_mmx
+ - Update version for 7.2.5 release
+Closes: CVE-2023-3255, CVE-2023-3354, CVE-2023-3180
+
+ -- Michael Tokarev Thu, 17 Aug 2023 12:33:57 +0300
+
qemu (1:7.2+dfsg-7+deb12u1) bookworm; urgency=medium
* d/rule
20.07.2023 11:40, Patrick Matthäi wrote:
..
I have uploaded glusterfs 11.0-1 to experimental, it is limited to these
architectures:
amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64
Build-Depends: architecture-is-64-bits
fwiw, anyway. Ok.
So if nobody rises up I would start to
14.07.2023 20:02, Patrick Matthäi wrote:
*ping* (also adding some other maintainers of reverse depends)
I don't remember seeing this before.
Yes, I use libglusterfs-dev in Build-Depends of samba and qemu.
I think it is already reduced to 64bits on ubuntu for samba (or,
rather, i386 is excluded
This is https://bugs.debian.org/1041043 - #1041043, I forgot to file
debian bug report about this issue. It's closed now by the sid upload
of samba.
/mjt
apabilities-l2.patch
+Fix windows logon/trust issues with 2023-07 windows updates:
+https://bugzilla.samba.org/show_bug.cgi?id=15418
+
+ -- Michael Tokarev Fri, 14 Jul 2023 12:34:30 +0300
+
samba (2:4.17.9+dfsg-0+deb12u2) bookworm; urgency=medium
* link with -latomic explicitly on a few
09.07.2023 10:05, Michael Tokarev wrote:
...
Now after thought about all this in the morning, I think the following should
do it:
diff --git a/debian/changelog b/debian/changelog
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+samba (2:4.17.9+dfsg-0+deb12u2) bookworm; urgency
09.07.2023 01:45, Adrian Bunk wrote:
On Sun, Jul 09, 2023 at 01:13:55AM +0300, Michael Tokarev wrote:
09.07.2023 01:01, Adrian Bunk wrote:
This does apparently need the -latomic workaround from 2:4.18.3+dfsg-3:
https://buildd.debian.org/status/package.php?p=samba&suite=bookworm
Sigh!
Thi
09.07.2023 01:01, Adrian Bunk wrote:
This does apparently need the -latomic workaround from 2:4.18.3+dfsg-3:
https://buildd.debian.org/status/package.php?p=samba&suite=bookworm
Sigh!
This is the kerberos in-kernel tickets.. :(
I haven't realized until now that atomic8 thing come into the game
07.07.2023 10:58, Jonathan Wiltshire wrote:
Control: tag -1 confirmed
On Fri, Jul 07, 2023 at 10:03:07AM +0300, Michael Tokarev wrote:
[ Reason ]
Here's the next stable/bugfix release of samba, 4.17.9.
As has been the case with samba stable/bugfix releases, this
one is of an excellent qu
on NT_STATUS_RPC_SEC_PKG_ERROR
+ * remove dnsserver-rename-dns_name_equal.patch
+(included upstream)
+
+ -- Michael Tokarev Thu, 06 Jul 2023 23:00:33 +0300
+
samba (2:4.17.8+dfsg-2) unstable; urgency=medium
* dnsserver-rename-dns_name_equal.patch
diff -Nru --exclude '*.[1-8]' --exclu
ting next stable
+Fixes crashes of named with samba DLZ plugin due to
+symbol name conflict (dns_name_equal() function).
+There's no resulting code changes, just a symbol
+rename.
+https://bugzilla.samba.org/show_bug.cgi?id=14030
+Closes: #1036587, #927747
+
+ -- Mic
a new install until ipxe-qemu is installed too.
+
+An alternative would be to revert upstream commit 178e785fb
+(from 2014) to make rom loading failure a non-fatal error.
+
+ -- Michael Tokarev Sun, 14 May 2023 11:29:12 +0300
+
qemu (1:7.2+dfsg-6) unstable; urgency=medium
[ Michael To
12.05.2023 11:05, Sebastian Ramacher пишет:
Control: tags -1 moreinfo
On 2023-05-11 12:58:00 +0300, Michael Tokarev wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: sa...@packages.debian.org, pkg-samba-ma
* https://bugzilla.samba.org/show_bug.cgi?id=15360
+ Setting veto files = /.*/ break listing directories
+ * https://bugzilla.samba.org/show_bug.cgi?id=15366
+ wbinfo -u fails on ad dc with >1000 users
+ * d/gbp.conf: switch debian-branch to "bookworm"
+
+ -- Michael Tokarev
04.05.2023 00:00, Sebastian Ramacher wrote:
..
1. sync with upstream qemu stable/bugfix 7.2.1 release, by removing
all patches in debian/patches/master/ and replacing them all with
single debian/patches/v7.2.1.diff which is a diff between upstream
qemu 7.2.0 and 7.2.1 releases. This
30.04.2023 11:07, Michael Tokarev пишет:
...
branch, and also includes the forgotten .desktop file which
results in a missing icon file for qemu-system processes.
And as I found out later, I should not ship debian-specific qemu.desktop
file, since upstream provides its own, I just
. All changes, in my opinion, are worth to have in
bookworm, each and all were thought about with care.
unblock qemu/1:7.2+dfsg-6
=== begin changelog
qemu (1:7.2+dfsg-6) unstable; urgency=medium
[ Michael Tokarev ]
* sync with upstream v7.2.1 stable release, into d/patches/v7.2.1.diff.
A
18:28:54.0 +0300
+++ unbound-1.17.1/debian/changelog 2023-04-09 15:59:14.0 +0300
@@ -1,3 +1,10 @@
+unbound (1.17.1-2) unstable; urgency=medium
+
+ * unbound-helper: return 0 explicitly in a few places
+(Closes: #1019140)
+
+ -- Michael Tokarev Sun, 09 Apr 2023 15:59:14
rel-1.16.2 tag):
+this brings up to the exactly same state as our rel-1.16.1.patch
+did, and brings up 2 more fixes:
+- usb: fix wrong init of keyboard/mouse's if first interface
+ is not boot protocol
+- xen: require Xen info structure at 0x1000 to detect Xen
+
+ -- Michael Toka
ils-6.11/debian/changelog2022-08-27 03:20:00.0 +0300
@@ -1,3 +1,9 @@
+cifs-utils (2:6.11-3.1+deb11u2) bullseye; urgency=medium
+
+ * Fix non-parallel build. Closes: #993014.
+
+ -- Michael Tokarev Sat, 27 Aug 2022 02:20:00 +0200
+
cifs-utils (2:6.11-3.1+deb11u1) bullseye-security; urg
Package: release.debian.org
Severity: minor
User: release.debian@packages.debian.org
Usertags: britney
When a package provides only superficial tests, tracker.d.o page shows
"No test results" "result" for the autopkgtests. This is misleading,
especially since it links to a successful test resu
So, is there anything else needed on my side to help this?
I can re-send the debdiff (the change against the previous one was the
removal of closing of #1002059 from d/changelog which slipped there by
mistake, and going from -1+deb11u4 to -1~deb11u4 per carnil@ suggestion.
Thanks,
/mjt
26.04.2022 10:37, Salvatore Bonaccorso wrote:
Hi,
On Fri, Apr 15, 2022 at 05:12:38PM +0300, Michael Tokarev wrote:
* switch from weird ~deb11uN to the usual +deb11uN release numbering scheme
since a more recent upstream version is available in testing now
It is not really a change per
23.04.2022 11:28, Michael Tokarev wrote:
...
This also fixes a *sporaric* (rare) broken build which actually
happened with previous security update: #1006935, #1009855, #1002059
The #1002059 slipped there by a mistake. It is a different problem,
most likely a misconfiguration on the OP side
11uN release numbering scheme
+since a more recent upstream version is available in testing now
+ * d/salsa-ci.yml: target bullseye
+
+ -- Michael Tokarev Sat, 23 Apr 2022 11:13:39 +0300
+
samba (2:4.13.13+dfsg-1~deb11u3) bullseye-security; urgency=high
* Non-maintainer upload by the
Hello!
It turned out the security-uploaded build of samba on i386 is broken.
There were several reports about smbd segfaulting at startup or other
weirdness. This is specific to i386 build, the x64 build is fine (and
I know nothing about the other architectures).
An example bugreport is #1006935
3738-dsdb-crash-4.13-v03.patch
+to make patch deapply happy (quilt does not notice this situation)
+ * switch from weird ~deb11uN to the usual +deb11uN release numbering scheme
+since a more recent upstream version is available in testing now
+ * d/salsa-ci.yml: target bullseye
+
+ -- Michae
se:
libslirp (4.4.0-1+deb11u2) bullseye; urgency=medium
* fix-DHCP-broken-in-libslirp-v4.6.0.patch from upstream
this fixes previous change in this area
(bootp-limit-vendor-area-to-input-packet-CVE-2021-3592.patch).
https://gitlab.freedesktop.org/slirp/libslirp/-/issues/48
Control: tag -1 moreinfo
Actually this particular upload does break some things, it seems.
I'm investigating..
/mjt
- upd6-check-udp6_input-buffer-size-CVE-2021-3593.patch
Closes: #989994, CVE-2021-3593: invalid pointer init in udp6_input()
-- Michael Tokarev Thu, 30 Sep 2021 21:08:51 +0300
[ Other info ]
And here's the debdiff.
Thanks!
/mjt
diff -Nru libslirp-4.4.0/debian/change
3.patch
+(Closes: #983575, CVE-2020-29443)
+ * usb-limit-combined-packets-to-1-MiB-CVE-2021-3527.patch
+usb-redir-avoid-dynamic-stack-allocation-CVE-2021-3527.patch
+(Closes: #988157, CVE-2021-3527)
+
+ -- Michael Tokarev Sun, 18 Jul 2021 16:14:41 +0300
+
qemu (1:5.2+dfsg-10) unstable;
)
+
+ -- Michael Tokarev Fri, 16 Apr 2021 12:43:36 +0300
+
qemu (1:5.2+dfsg-9) unstable; urgency=medium
* do not make qemu-system-data dependent on qemu-system-foo
diff -Nru
qemu-5.2+dfsg/debian/patches/mptsas-remove-unused-MPTSASState.pending-CVE-2021-3392.patch
qemu-5.2+dfsg/debian
28.07.2020 10:53, Paul Gevers wrote:
..
> These request should normally be filed against ftp.debian.org and the
> package should be removed from unstable first (and then it's
> automatically removed from testing). Is there any reason why you request
> the removal from testing or should the bug just
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
The package openhackware builds a single binary blob, ppc_rom.bin,
which is a bios/firmware for old PowerPC machines.
This firmware were used by qemu package (namely, qemu-system-ppc)
to emulate
fixes booting U-Boot in UEFI mode on aarch32
+Closes: #927763
+ * stop qemu-system-common pre-depending on adduser
+ Closes: #929261
+
+ -- Michael Tokarev Mon, 27 May 2019 07:49:25 +0300
+
qemu (1:3.1+dfsg-7) unstable; urgency=high
[ Michael Tokarev ]
diff -Nru qemu-3.1+dfsg/d
ebian/changelog
--- qemu-3.1+dfsg/debian/changelog 2019-03-11 14:30:44.0 +0300
+++ qemu-3.1+dfsg/debian/changelog 2019-03-27 14:24:06.0 +0300
@@ -1,3 +1,26 @@
+qemu (1:3.1+dfsg-7) unstable; urgency=high
+
+ [ Michael Tokarev ]
+ * device_tree-don-t-use-load_image-CVE-2018-
19.04.2017 14:31, Michael Tokarev пишет:
> Control: tag -1 - moreinfo
>
> 18.04.2017 11:06, Niels Thykier wrote:
>
>>> unblock qemu/1:2.8+dfsg-4
>
>> Hi Michael,
>>
>> Please go ahead with this change set and let us know once it has been
>>
Control: tag -1 - moreinfo
18.04.2017 11:06, Niels Thykier wrote:
>> unblock qemu/1:2.8+dfsg-4
> Hi Michael,
>
> Please go ahead with this change set and let us know once it has been
> built on all relevant release architectures in unstable.
Thank you very much! It wasn't an easy job on your
12.04.2017 20:25, Niels Thykier wrote:
[]
>>> Just to be sure, are you recommending 1:2.8+dfsg-4 or that we go with
>>> upstream's 2.8.1 release?
>>
>> Historically, for some reason I don't remember what, we
>> kept the "major" upstream version and source in qemu and
>> used just a patch (v2.8.1.pa
05.04.2017 20:42, Niels Thykier wrote:
> Control: tags -1 moreinfo
>
> On Wed, 05 Apr 2017 09:35:19 +0300 Michael Tokarev wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: unblock
000 +0300
@@ -1,3 +1,12 @@
+seabios (1.10.2-1) unstable; urgency=medium
+
+ * new upstream stable/bugfix release,
+required for qemu 2.8.1+ due to ahci changes,
+plus fixes for guest resume from S3
+and ps/2 keyboard/mouse handling
+
+ -- Michael Tokarev Mon, 03 Apr 2017 13:47:29 +0300
+
s
-vcard_apdu_new-CVE-2017-6414.patch
+Closes: #856501, CVE-2017-6414
+ * dont-fail-if-caller-didn-t-pick-previous-response.patch
+
+ -- Michael Tokarev Sat, 04 Mar 2017 11:57:23 +0300
+
libcacard (1:2.5.0-2) unstable; urgency=medium
* add remove-requires.private.patch to remove
fsg/debian/changelog
--- qemu-2.8+dfsg/debian/changelog 2017-01-23 14:06:54.0 +0300
+++ qemu-2.8+dfsg/debian/changelog 2017-03-01 12:32:26.0 +0300
@@ -1,3 +1,63 @@
+qemu (1:2.8+dfsg-3) unstable; urgency=high
+
+ * urgency high due to security fixes
+
+ [ Michael Tokarev ]
+ * se
After some thoughts, I think this should be pushed to testing
faster. Because the features I enabled which are currently
in testing are just plain buggy, there are multiple security
bugs in virtio-3d display (which is being disabled in sid),
and because with just 2 weeks of this being in testing, i
ing of #769983 (multi-threaded linux-user) by 2.7
+ * mention closing of #842455, CVE-2016-9101 by 2.8
+ * audio-ac97-add-exit-function-CVE-2017-5525.patch (Closes: #852021)
+ * audio-es1370-add-exit-function-CVE-2017-5526.patch (Closes: #851910)
+ * watchdog-6300esb-add-exit-function-CVE-2016-10
28.06.2016 12:17, Julien Cristau wrote:
> Control: tag -1 moreinfo
>
> On Sat, Feb 20, 2016 at 18:19:49 +, Julien Cristau wrote:
Hmm. I haven't seen this email back in February.
Basically I gave up waiting for almost a year for this,
I don't even remember anymore what was in version 2.1.
M
Control: retitle -1 jessie-pu: package qemu/1:2.1+dfsg-12+deb8u5
14.09.2015 18:04, Michael Tokarev wrote:
> Package: release.debian.org
> Severity: normal
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
>
> I'd like to update qemu in j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
06.03.2015 15:02, Sam Hartman wrote:
[]
> So, you're involving the TC because you're hoping to better understand why
> your unblock was not approved?
>
> How are you hoping the TC can help? Here are some options I see:
>
> * Some folks on the TC ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
05.03.2015 15:08, Sam Hartman wrote:
>>>>>> "Adam" == Adam D Barratt writes:
>
> Adam> Hi, Making no comment on the remainder of the mail:
>
> Adam> On 2015-03-05 10:38, Michael Tokarev wrote:
>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I didn't really want to write this email, but it looks I now have to,
even if, for reasons which whill be shown below, don't expect any
good news from this.
Trying to make the story short.
For quite some time we had a bug in glibc in jessie w
27.01.2015 08:59, Christian PERRIER пишет:
> (CC'ed in case you guys subscribed to -release. I am subscribed
> so please no CC)
>
> Quoting Michael Tokarev (m...@tls.msk.ru):
>
>> So you're continuing to ruin my (hard in this case) work, spreading lies
>> (in
tion(-)
>
> diff --git a/debian/changelog b/debian/changelog
> index e78827c..7c18a73 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,7 +1,13 @@
> -busybox (1:1.22.0-10) UNRELEASED; urgency=low
> +busybox (1:1.22.0-14+deb8u1) UNRELEASED; urgency=low
>
>
3.3.2-3 release). (Closes: #764036, #771852)
* mention closing of #588965 #599352 #694513 by 3.3-1
-- Michael Tokarev Fri, 05 Dec 2014 17:29:22 +0300
@@ -84,7 +96,7 @@
mdadm (3.3-1) unstable; urgency=low
[ Michael Tokarev ]
- * new upstream 3.3 release (Closes: #718896 #588965
@@ -1,3 +1,17 @@
+edk2 (0~20131112.2590861a-3) unstable; urgency=medium
+
+ [ Steve Langasek ]
+ * debian/copyright: include a Disclaimer field to document clearly why
+this package is not in main. Closes: #742589.
+
+ [ Michael Tokarev ]
+ * apply gcc-4.9-align.patch kindly provided by
11.12.2014 17:23, Michael Tokarev wrote:
...
> The fix includes re-working a (debian-specific) patch which introduces a
> build-time search PATH instead of a single directory as used by qemu (since
> upstream qemu source includes firmware blobs from various projects in a
> single dir
upload to cancel 2.2+dfsg-1exp upload
+mistakenly done to unstable. No other changes.
+
+ -- Michael Tokarev Wed, 10 Dec 2014 00:52:28 +0300
+
+qemu (2.1+dfsg-10) unstable; urgency=medium
+
+ * make (debian-specific) x86 data path (with seabios and ipxe
+in it) non-x86-specific, since other
11.12.2014 13:02, Cyril Brulebois wrote:
> Hi,
Hello
> can you please still push your master branch and tags to the git
> repository? Last commit there points to debian/1.22.0-9 which is
> 5 revisions old, at least if I'm reading cgit and gitk properly.
Oh yeah. I'm sorry about that. Pushed no
11.12.2014 10:52, Ivo De Decker wrote:
[]
> As the libc issue with the static binary seems to be fixed in the libc version
> in both jessie and sid, the only remaining issue is the missing build-using,
> which can wait till after jessie.
>
> Could you do a new upload with only the security fix?
I
+
+ -- Michael Tokarev Thu, 04 Dec 2014 00:10:43 +0300
+
qemu (2.1+dfsg-8) unstable; urgency=low
[ Michael Tokarev ]
diff -Nru
qemu-2.1+dfsg/debian/patches/cirrus-don-t-overflow-CirrusVGAState-cirrus_bltbuf-CVE-2014-8106.patch
qemu-2.1+dfsg/debian/patches/cirrus-don-t-overflow-CirrusVGAStat
03.12.2014 21:37, Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
>
> On Sun, Nov 30, 2014 at 03:42:56PM +0100, Diederik de Haas wrote:
>> What needs to be done further so that busybox transitions into testing?
>> --
>> GPG: 0x138E41915C7EFED6
>
>
> Well, sid now has 1:1.22.0-14, so the be
tated changelog (complete debdiff is below):
qemu (2.1+dfsg-8) unstable; urgency=low
[ Michael Tokarev ]
* add Built-Using control field for qemu-user-static package:
take contents of qemu-user ${shlibs:Depends} and transform it
into list of source packages with versions. (Closes: #768926)
27.11.2014 19:00, Cyril Brulebois wrote:
> (Putting on my d-i RM fedora.)
Thank you for your review.
> Michael Tokarev (2014-11-27):
>> Please unblock package busybox. Last upload has one security bugfix
>> (CVE-2014-4607, #768945), the fix is from upstream stable branch,
&g
more attempt to fix the glibc build-depend for #769190, now
+using versioned build-dependency on libc-dev-bin which is named
+this way on all architectures (unlike libc6|libc6.1|libc0.1|libc0.3)
+
+ -- Michael Tokarev Fri, 14 Nov 2014 12:52:18 +0300
+
+busybox (1:1.22.0-13) unstable; ur
14.11.2014 13:12, Julien Cristau wrote:
> On Fri, Nov 14, 2014 at 13:02:04 +0300, Michael Tokarev wrote:
>
>> 14.11.2014 12:42, Julien Cristau wrote:
>>
>>> FWIW I don't believe build-conflicts on libc achieve anything, so I'm
>>> unhappy with -13.
14.11.2014 12:42, Julien Cristau wrote:
> FWIW I don't believe build-conflicts on libc achieve anything, so I'm
> unhappy with -13.
I'm not happy with it either, but why do you say it does not achieve
anything? Why do you say so, is this control field ignored?
At any rate I changed that to buil
11.11.2014 18:08, Michael Tokarev wrote:
> Please unblock package busybox. Last upload has one security bugfix
> (CVE-2014-4607, #768945), the fix is from upstream stable branch,
> fixing an integer overflow in lzo decompressor; it adds a Built-Using
> control field for busybox-st
long-standing lintian error, when package build
+alway produces busybox-syslogd package which is arch:all and should not
+be built on a buildd.
+
+ -- Michael Tokarev Tue, 11 Nov 2014 17:07:34 +0300
+
busybox (1:1.22.0-9) unstable; urgency=medium
* cherry-pick find /BITS patch from ups
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please consider unblocking package qemu. Current version has 2 security
fixes (CVE-2014-3689 and CVE-2014-7815) and a fix for possible data
corrupter which has biten several people already
18.04.2014 16:27, Adam D. Barratt wrote:
> On 2014-04-18 12:54, Michael Tokarev wrote:
>> 18.04.2014 15:40, Adam D. Barratt wrote:
>>> Not wishing to chase, just a gentle reminder that the window for getting
>>> updates in to 7.5 closes over the weekend. (Although get
18.04.2014 15:40, Adam D. Barratt wrote:
> On 2014-04-13 19:05, Michael Tokarev wrote:
[]
>>>> There's a pending security update for qemu fixing CVE-2014-0150 (#744221),
>>>> which uploads +deb7u1 for both qemu and qemu-kvm, fwiw.
>>>
>>> Okay, th
13.04.2014 22:04, Adam D. Barratt wrote:
> On Sun, 2014-04-13 at 21:49 +0400, Michael Tokarev wrote:
>> 13.04.2014 21:39, Adam D. Barratt wrote:
>>>
>>> On Sun, 2014-03-23 at 12:45 +0100, Gabriele Giacone wrote:
>>>> On Sun, Mar 23, 2014 at 01:48:34PM +04
13.04.2014 21:39, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Sun, 2014-03-23 at 12:45 +0100, Gabriele Giacone wrote:
>> On Sun, Mar 23, 2014 at 01:48:34PM +0400, Michael Tokarev wrote:
>>> Please note that the same changes should be done for qemu-kv
23.03.2014 05:31, Gabriele Giacone wrote:
>
> Package: release.debian.org
> Severity: normal
> Tags: wheezy
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Hello,
> this upload would fix two bugs with severity important regarding booting
> GNU/Hurd machines.
Please note that th
06.09.2013 10:42, Stéphane Glondu write:
[]
Now, xen-api FTBFS because of what looks like an API change in some (C)
dependency:
[]
On the other hand, there is a new upstream release (upstream version is
1.6 and unstable version is 1.3.2). It doesn't make sense to me to
invest time in this witho
Control: reopen -1
05.05.2013 12:00, Michael Tokarev wrote:
> Control: retitle -1 pu: busybox/1:1.20.0-8
Hmm. I didn't notice the bug has been closed...
Reopening it (now re-titled as a pu), instead of
submiting a new report, so that all the information
is in one place.
Thanks, and s
Control: retitle -1 pu: busybox/1:1.20.0-8
17.04.2013 22:54, Adam D. Barratt wrote:
> user release.debian@packages.debian.org
> tags 686502 + wheezy-ignore
> usertags 686502 + wheezy-can-defer
> thanks
>
> On Mon, 2013-04-08 at 09:51 +0200, Cyril Brulebois wrote:
>>
08.04.2013 11:57, Cyril Brulebois wrote:
> Forgot to mention one thing:
>
> Cyril Brulebois (08/04/2013):
>> My take is: until we hit real bugs in real situations, we keep busybox as it
>> is. If release managers want to cherry-pick a few fixes, I won't stop them
>> from requesting so. But as f
I'm pinging this bug, as we're getting seriously out of time.
Now, I guess, we should either let the whole thing go (it has
already been unblocked for, only d-i block remains), or mark
the relevant bugs as non-RC for wheezy.
Thanks,
/mjt
25.03.2013 15:38, Michael Tokarev wrote:
>
And sure thing I forgot to Cc debian-boot@. I think if this needs
to be discussed further, debian-boot@ should receive it too.
Thanks!
/mjt
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive
Let me start from scratch please. I wasn't aware of this
bugreport/discussion, and I made a mistake by not filing
a proper unblock request when I uploaded the busybox
package with all the fixes. So here are descriptions of
every change.
A sort of a fore-word first. Busybox is kind of unusual pa
25.03.2013 13:54, Didier Raboud wrote:
>> I propose to upload busybox to t-p-u with only the RC bugfixes (#686502
>> and #701965, CVE-2013-1813).
>
> IRC feedback on that subject lead to dropping the fix for #701965,
> rationale being http://bugs.debian.org/702278#17 .
That's lovely. I haven't
25.03.2013 13:37, Didier Raboud wrote:
> Hi all,
>
> I propose to upload busybox to t-p-u with only the RC bugfixes (#686502
> and #701965, CVE-2013-1813). I have cherry-picked thoses changes on top
> of wheezy's. The resulting debdiff is attached, with version
> 1:1.20.0-7+deb7u0.1.
I really hop
28.01.2013 05:07, Cyril Brulebois wrote:
Julien Cristau (26/01/2013):
3.2.5-5 unblocked. unblock-udeb pending d-i ack, probably post-rc1.
Looks like post-rc1 material to me indeed.
FWIW (not insisting for earlier inclusion, just noting), for the d-i,
the noticeable change is the inclusion
may become dirty on the next boot. So it is a change
with a good effect even for non-fakeraid arrays.
Thanks,
/mjt
29.10.2012 00:42, Michael Tokarev wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
This is a "pre-upload unbl
19.01.2013 15:23, Julien Cristau wrote:
> qemu{,-kvm} unblocked.
Thank you very much Julien!
/mjt
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50fd25b0.8070...@
@
+qemu (1.1.2+dfsg-5) unstable; urgency=low
+
+ * fix USB regression introduced in 1.1 (Closes: #683983)
+uhci-don-t-queue-up-packets-after-one-with-the-SPD-flag-set.patch
+Big thanks to Peter Schaefer (https://bugs.launchpad.net/bugs/1033727)
+ for the help identifying the fix.
+
+ -- Micha
1 - 100 of 144 matches
Mail list logo
