Bug#991246: unblock: qemu/1:5.2+dfsg-11

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;

Bug#988186: unblock: qemu/1:5.2+dfsg-10

) + + -- 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

Bug#995439: bullseye-pu: package libslirp/4.4.0-1+deb11u1

- 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

Bug#995439: bullseye-pu: package libslirp/4.4.0-1+deb11u1

Control: tag -1 moreinfo Actually this particular upload does break some things, it seems. I'm investigating.. /mjt

Bug#995469: bullseye-pu: package libslirp/4.4.0-1+deb11u2

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

Bug#1034296: unblock: seabios/1.16.2-1

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

Bug#1034298: unblock: unbound/1.17.1-2

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

Bug#929607: unblock: qemu/1:3.1+dfsg-8 (pre-upload)

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

Bug#1009726: bullseye-pu: package samba/2:4.13.13+dfsg-1+deb11u4

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

Bug#1009726: broken build of samba_4.13.13+dfsg-1~deb11u3 on i386

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

Bug#1009726: bullseye-pu: package samba/2:4.13.13+dfsg-1+deb11u4

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

Bug#1009726: bullseye-pu: package samba/2:4.13.13+dfsg-1+deb11u4

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

Bug#1009726: bullseye-pu: package samba/2:4.13.13+dfsg-1+deb11u4

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

Bug#1009726: bullseye-pu: package samba/2:4.13.13+dfsg-1+deb11u4

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

Bug#1011267: "No test result" for superficial tests is misleading

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

Bug#1019096: bullseye-pu: package cifs-utils/2:6.11-3.1+deb11u2

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

Bug#965254: RM: openhackware/0.4.1+git-20140423.c559da7c-4.1

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

Bug#965254: RM: openhackware/0.4.1+git-20140423.c559da7c-4.1

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

Bug#852417: unblock: qemu/1:2.8+dfsg-2

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

Bug#852417: unblock: qemu/1:2.8+dfsg-2

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

Bug#798969: jessie-pu: package qemu/1:2.1+dfsg-12+deb8u5

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

Bug#859417: unblock: seabios/1.10.2-1

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

Bug#859599: unblock: qemu/1:2.8+dfsg-4

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

Bug#859599: unblock: qemu/1:2.8+dfsg-4

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

Bug#859599: unblock: qemu/1:2.8+dfsg-4

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

Bug#859599: unblock: qemu/1:2.8+dfsg-4

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 >>

Bug#926441: unblock: qemu/1:3.1+dfsg-7

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-

Bug#798969: jessie-pu: package qemu/1:2.1+dfsg-12+deb8u4

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

Re: lxc linux image flavour

Marco d'Itri wrote: > On Jan 24, maximilian attems wrote: [] >> On the negative side it doesn't have yet checkpointing support >> and not all net/ has netns support yet. > It's not just that, AFAIK there is no match for many of the > user_beancounters features (especially the accounting part) and

freeze exception for qemu-kvm package

Hello, the (chilly) Release Team! ;) I'm asking for a freeze exception for the package named qemu-kvm, and a companion transitional package kvm, which were in -unstable for 10 days already. Current package in testing is 0.12.4+dfsg-1. The unstable currently has0.12.5+dfsg-1. As it can be see

Bug#626003: pu: package qemu-kvm/0.12.5+dfsg-5+squeeze2

6) * fix long-standing migration bug on 32bits (closes: #625571) -- Michael Tokarev Sat, 07 May 2011 21:18:15 +0400 qemu-kvm is a full virtualization package for x86 hardware, it provides a "virtual hardware" (a VM) which can be used to install other operating systems. Here's

Bug#626003: pu: package qemu-kvm/0.12.5+dfsg-5+squeeze2

I forgot to show a debdiff for the request. It comes empty except of size and version difference: $ debdiff qemu-kvm_0.12.5+dfsg-5+squeeze1_i386.deb qemu-kvm_0.12.5+dfsg-5+squeeze2_i386.deb File lists identical (after any substitutions) Control files: lines which differ (wdiff format) --

Bug#626003: pu: package qemu-kvm/0.12.5+dfsg-5+squeeze2

09.05.2011 22:10, Philipp Kern wrote: > On Mon, May 09, 2011 at 12:44:54PM +0400, Michael Tokarev wrote: >> I forgot to show a debdiff for the request. > > Please debdiff the source, not the resulting binary. And yeah, I marked this > mail as to-do while on the road because the

Bug#626003: pu: package qemu-kvm/0.12.5+dfsg-5+squeeze2 (+squeeze3?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 17.05.2011 00:25, Philipp Kern wrote: > Hi, > > On Mon, May 09, 2011 at 10:49:51PM +0400, Michael Tokarev wrote: >> 09.05.2011 22:10, Philipp Kern wrote: >>> On Mon, May 09, 2011 at 12:44:54PM +0400, Michael Tokarev wrote:

unblocking busybox for -testing

Hello. Can you please unblock busybox 1:1.18.4-2 upload to go from unstable to testing? It has been in unstable for a long time already, and the only problem found so far has been fixed in subsequent upload. It's a new upstream version upload, so the changes are somewhat large for such a delicat

Bug#641155: pu: package mdadm/3.1.4-1+8efb9d1+squeeze1

The debdiff is provided below. The changes has been run-tested for the previously-buggy cases and for common non-error cases and appears to work fine. The upload has been prepared by me, Michael Tokarev, instead of usual uploader martin f. krafft, -- I'm currently helping with packaging mdadm

Bug#641155: pu: package mdadm/3.1.4-1+8efb9d1+squeeze1

On 11.09.2011 02:09, Philipp Kern wrote: > On Sun, Sep 11, 2011 at 01:09:35AM +0400, Michael Tokarev wrote: >> We'd like to upload a bugfix release of mdadm package for the >> next squeeze point release. There are mostly cosmetic changes, >> but some of the bugs are very

Re: Bug#598957: NMU of mdadm for squeeze-proposed-upates

On 13.09.2011 19:01, Dominic Hargreaves wrote: [] >> This is still unfixed in sid, though. > > Indeed so. > > In any case, since I have rolled this out on some servers I manage, > I thought I may as well confirm that a patch (attached) adopted from > >

Bug#698221: unblock: qemu/1.1.2+dfsg-5 qemu-kvm/1.1.2+dfsg-5

@ +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

Bug#698221: unblock: qemu/1.1.2+dfsg-5 qemu-kvm/1.1.2+dfsg-5

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...@

Bug#691710: unblock: mdadm/3.2.5-4 (pre-upload)

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

Bug#691710: unblock: mdadm/3.2.5-4 (pre-upload)

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

Bug#684355: unblock: autofs/5.0.6-3

startup and confuses upstart and systemd who start tracking wrong process. The patch just removes these checks assuming we always use recent enough versions. (Closes: #678555) -- Michael Tokarev Wed, 26 Sep 2012 21:15:05 +0400 autofs (5.0.6-4) unstable; urgency=low * configure

Bug#684355: unblock: autofs/5.0.6-3

On 26.09.2012 23:49, Michael Tokarev wrote: [] > Debdiff between wheezy and sid version will be sent in a separate > email, since it is large. The same but without upstream changes > (which are easily visible in the git tree referenced above) and > the removal of half-5.0.7 upstre

Bug#684355: unblock: autofs/5.0.7-2

autofs-5.0.7/debian/changelog 2012-10-06 13:06:37.0 +0400 @@ -1,3 +1,10 @@ +autofs (5.0.7-2) unstable; urgency=low + + * force transfer ucf autofs5=>autofs ownership for all ucf-managed +files (Closes: #689747) + + -- Michael Tokarev Sat, 06 Oct 2012 13:06:37 +0400 + auto

Bug#684355: unblock: autofs/5.0.6-3

On 10.10.2012 20:06, Julien Cristau wrote: > On Thu, Aug 9, 2012 at 09:39:22 +0400, Michael Tokarev wrote: > >> diff -Nru autofs-5.0.6/debian/autofs.init autofs-5.0.6/debian/autofs.init [] >> +NAME=autofs >> +PIDFILE="/run/$NAME.pid" >> > the PIDFIL

Bug#691710: unblock: mdadm/3.2.5-4 (pre-upload)

1670) + * super0: do not override uuid with homehost. The bug prevented +re-creating an array with v0.90 superblock with the specified uuid +when homehost is also specified. (Closes: #686703) + * several fixes for mdmon argument processing (Closes: #691671): +- allow --takeover when orig

Bug#856591: unblock: qemu/1:2.8+dfsg-3

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

Bug#856721: unblock: libcacard/1:2.5.0-3

-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

Bug#1035297: unblock: qemu/1:7.2+dfsg-6

. 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

Bug#1035297: unblock: qemu/1:7.2+dfsg-6

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

Bug#1035297: unblock: qemu/1:7.2+dfsg-6

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

Bug#1035927: unblock: samba/2:4.17.8+dfsg-1

* 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

Bug#1035927: unblock: samba/2:4.17.8+dfsg-1

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

Bug#1036040: unblock: qemu/1:7.2+dfsg-7

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

Bug#1036741: unblock: samba/2:4.17.8+dfsg-2

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

Bug#1040519: bookworm-pu: package samba/2:4.17.9+dfsg-0+deb12u1

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

Bug#1040519: bookworm-pu: package samba/2:4.17.9+dfsg-0+deb12u1

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

Bug#1040519: bookworm-pu: package samba/2:4.17.9+dfsg-0+deb12u1

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

Bug#1040519: bookworm-pu: package samba/2:4.17.9+dfsg-0+deb12u1

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

Bug#1040519: bookworm-pu: package samba/2:4.17.9+dfsg-0+deb12u1

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

Bug#1041037: bookworm-pu: package samba/2:4.17.9+dfsg-0+deb12u3

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

Bug#1041037: bookworm-pu: package samba/2:4.17.9+dfsg-0+deb12u3

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

Re: Bug#1039604: glusterfs: Drop support for 32-bit architectures

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

Re: Bug#1039604: glusterfs: Drop support for 32-bit architectures

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

Bug#1049955: bookworm-pu: package qemu/1:7.2+dfsg-7+deb12u2

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

Bug#1051594: bookworm-pu: package samba/2:4.17.11+dfsg-0+deb12u1

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

Bug#1049955: bookworm-pu: package qemu/1:7.2+dfsg-7+deb12u2

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

Bug#1052648: bookworm-pu: package unbound/1.17.1-2+deb12u1

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

Bug#1070801: bookworm-pu: package qemu/1:7.2+dfsg-7+deb12u6

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

Bug#1080378: transition: samba

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

Bug#1080378: transition: samba

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

Bug#1081535: nmu: llvm-toolchain-15_1:15.0.6-4+b1

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

Bug#1062044: qemu 7.2+dfsg-7+deb12u4 flagged for acceptance

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

Bug#1062044: qemu 7.2+dfsg-7+deb12u4 flagged for acceptance

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

Bug#1062044: qemu 7.2+dfsg-7+deb12u4 flagged for acceptance

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

Bug#1062044: qemu 7.2+dfsg-7+deb12u4 flagged for acceptance

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

Bug#1062044: qemu 7.2+dfsg-7+deb12u4 flagged for acceptance

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

Bug#1062044: qemu 7.2+dfsg-7+deb12u4 flagged for acceptance

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

Bug#768007: unblock: qemu/2.1+dfsg-7

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

Bug#769129: unblock: busybox/1:1.22.0-10

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

Bug#769129: unblock: busybox/1:1.22.0-10

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

Bug#769129: unblock: busybox/1:1.22.0-10

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

Bug#769129: unblock: busybox/1:1.22.0-10

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.

Bug#684005: unblock: busybox/1:1.20.0-6

e does not work anyway. (Closes: 681760) + + -- Michael Tokarev Sun, 22 Jul 2012 12:30:02 +0400 + busybox (1:1.20.0-5) unstable; urgency=low * enable various xargs features for all flavours, to make it work diff -Nru busybox-1.20.0/debian/patches/dont-force-no-alignment-for-s390.patch busy

pushing a few more qemu-kvm fixes from upstream

Hello again. There are quite a few fixes accumulated in qemu-kvm 1.1 stable upstream branch since qemu-kvm 1.1 debian release. Some of them are already included in the debian release. The others.. some aren't relevant for qemu-kvm (like non-x86 bits), some are just compiler warning suppressions o

Re: pushing a few more qemu-kvm fixes from upstream

RC bugs, but this is just the "minimal" severity possible for these bugs, -- the cases where each bug happens are quite important use cases for the packsage. A few comments about my original email below. On 08.08.2012 11:57, Michael Tokarev wrote: > Hello again. > > There are q

Bug#684355: unblock: autofs/5.0.6-3

/control is changed to list new maintainer address - this is important change by its own. The changelog, with a bit more comments: autofs (5.0.6-3) unstable; urgency=low [Michael Tokarev] * almost completely rewrote the startup script, make it cleaner, consistent and actually returning proper

Bug#684934: unblock: qemu-kvm/1.1.1+dfsg-1

On 25.08.2012 12:52, Julien Cristau wrote: > On Wed, Aug 15, 2012 at 00:26:01 +0400, Michael Tokarev wrote: > >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: unblock >> >> Please unblock pack

Bug#684355: unblock: autofs/5.0.6-3

retitle 684355 unblock: autofs/5.0.6-3 thanks On 09.08.2012 09:39, Michael Tokarev wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package autofs > > There are a few relativ

Bug#687153: unblock: qemu/1.1.2+dfsg-1 qemu-kvm/1.1.2+dfsg-1

On 10.09.2012 15:18, Michael Tokarev wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > We (qemu team) prepared new releases of qemu and qemu-kvm packages, > based on new upstream stable/bugfix rel

Bug#687153: unblock: qemu/1.1.2+dfsg-2 qemu-kvm/1.1.2+dfsg-2

Control: retitle -1 unblock: qemu/1.1.2+dfsg-2 qemu-kvm/1.1.2+dfsg-2 On 16.09.2012 00:58, Michael Tokarev wrote: > On 10.09.2012 15:18, Michael Tokarev wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usert

Bug#688218: unblock: busybox/1:1.20.0-7

patch: a rather trivial patch +to disable compatibility code for kernels <2.2.18 in nfs mount. +This was the only place in debian busybox which used +get_linux_version_code() function which was buggy on kernels with +less than 3 components version number. So instead of fixing th

Bug#773859: unblock: edk2/0~20131112.2590861a-3

@@ -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

Bug#775164: unblock: mdadm/3.3.2-5

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

Re: Re: Last hints for d-i, upload tomorrow

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 > >

Re: Last hints for d-i, upload tomorrow

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

bastardizing packages or stepping down

-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

Re: bastardizing packages or stepping down

-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: >&

Bug#771208: unblock: busybox/1:1.22.0-14

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

  1   2   >