Bug#1049902: raspi-firmware on non-rpi arm64

2023-09-06 Thread Adam Borowski
gwolf wrote: > The only risk I can think of is that the bug might still impact users of > non-Raspberry ARM systems. However, the likelihood of having it installed is > minor (due to the available hardware being different). Given that the laptop I use on the DebConf right now has 100% likelihood

Bug#1021406: nmu: * against debhelper 13.9.1

2022-10-07 Thread Adam Borowski
Package: release.debian.org Severity: normal Hi! The following packages in unstable still have binaries built against debhelper 13.9, which adds spurious dependencies on "systemd | systemd-tmpfiles". This causes at least the following problems: * forced init switch with !systemd (with an

Re: Porter roll call for Debian Bookworm

2021-12-31 Thread Adam Borowski
ge arch-specific bugs - fix arch-related bugs ~~ - have ported and regularly test the persistent memory stack - regularly troll the IRC channel I am a DD. Adam Borowski """ Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁

Bug#995304: bullseye-pu: package pmdk/1.10-2

2021-09-29 Thread Adam Borowski
-2+deb11u1) bullseye; urgency=high + + * Fix missing barriers after non-temporal memcpy. + + -- Adam Borowski Tue, 28 Sep 2021 17:41:00 +0200 + pmdk (1.10-2) unstable; urgency=high * Fix insufficient flushing on ARMv8.2+ (closes: #990573). diff -Nru pmdk-1.10/debian/patches/0001-common-fix-m

Bug#992193: RM: birdtray/1.5-1

2021-08-15 Thread Adam Borowski
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi! As thunderbird is an animal more equal than others and gets to update to major new upstream releases inside stable, related packages are likely to get broken. This happened over a year ago

Bug#991062: unblock: apache2/2.4.48-3.1

2021-07-13 Thread Adam Borowski
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi! Please unblock package apache2. After a bunch of random changes from experimental got into testing, there were regressions. Forbidding such changes is pretty much the point of the

Bug#988500: unblock: btrfs-progs/5.10.1-2

2021-05-14 Thread Adam Borowski
-14 02:52:17.0 +0200 @@ -1,3 +1,9 @@ +btrfs-progs (5.10.1-2) unstable; urgency=medium + + * Fix failure to add new devices via a devmapper path. Closes: #982990 + + -- Adam Borowski Fri, 14 May 2021 02:52:17 +0200 + btrfs-progs (5.10.1-1) unstable; urgency=medium * New upstream

Bug#980832: nmu: tor_0.4.4.6-1

2021-01-22 Thread Adam Borowski
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi! The tor package is paranoid about version of libzstd, and currently says: [warn] Tor was compiled with zstd 1.4.5, but is running with zstd 1.4.8. ↪ For safety, we'll avoid using

Bug#968502: buster-pu: arch-test needs to be updated in stable to include s390x fix

2020-08-18 Thread Adam Borowski
On Mon, Aug 17, 2020 at 07:31:01PM +0100, Adam D. Barratt wrote: > On Sun, 2020-08-16 at 15:43 +0200, Adam Borowski wrote: > > +arch-test (0.15-2+deb10u1) buster; urgency=medium > + > + * Fix s390x detection sometimes failing (Alexander Efremkin). > > Please go ahead. Tha

Bug#968502: buster-pu: arch-test needs to be updated in stable to include s390x fix

2020-08-16 Thread Adam Borowski
@@ -1,3 +1,9 @@ +arch-test (0.15-2+deb10u1) buster; urgency=medium + + * Fix s390x detection sometimes failing (Alexander Efremkin). + + -- Adam Borowski Sun, 16 Aug 2020 15:25:50 +0200 + arch-test (0.15-2) unstable; urgency=medium * Don't check for SWP on armel; it's not needed in the vast majorit

Bug#933605: nmu: pmdk-convert_1.5.1-1

2019-07-31 Thread Adam Borowski
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi! Because of the new "binary upload needed for NEW but banned for migration", the package is stuck in unstable. Please rebuild. I uploaded with arm64 as a sacrificial arch with no build

Re: Bits from the Release Team: ride like the wind, Bullseye!

2019-07-11 Thread Adam Borowski
On Thu, Jul 11, 2019 at 09:34:07PM +0200, gregor herrmann wrote: > You indeed missed someone (for obvious reasons): I'd like to thank > the release team for their excellent work! +1 > On Sun, 07 Jul 2019 02:47:00 +0100, Jonathan Wiltshire wrote: > > The release of buster also means the bullseye

Bug#925489: marked as done (unblock: elogind/241.1-1+debian1)

2019-04-09 Thread Adam Borowski
On Mon, Apr 08, 2019 at 02:57:03PM +, Debian Bug Tracking System wrote: > > I am aware that the debdiff against testing (239.3+20190131-1+debian1) is > > significantly larger than you would normally want at this stage in the > > release > > cycle. However, I believe it is warranted and ask

Bug#925489: unblock: elogind/241.1-1+debian1

2019-03-26 Thread Adam Borowski
On Tue, Mar 26, 2019 at 06:52:11PM +0100, Michael Biebl wrote: > Just to set the record straight here: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923244 > > This bug report is from Mon, 25 Feb 2019 11:49:14 + That's the "plan 3" bug. We had plan 1 over a year ago. > That this

Bug#925489: unblock: elogind/241.1-1+debian1

2019-03-26 Thread Adam Borowski
It's not a "niche" area. Without this, any modern GUI desktop environments are not installable with any pid 1 other than systemd. That'd be a massive regression that's certainly not acceptable (and it's caused by removal of a systemd component with a hard dependency). This regression had a

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

2018-12-11 Thread Adam Borowski
[Oy vey, crosspost list from hell -- not sure how to trim...] On Tue, Dec 11, 2018 at 09:46:21PM +0100, Gregor Riepl wrote: > I do think this just reinforces the point that second-class architectures > should have better, more robust support from the Debian project. > For example, arch-specific

Bug#909007: stretch-pu: package firetray/0.6.1+dfsg-1

2018-10-28 Thread Adam Borowski
On Sat, Oct 27, 2018 at 09:46:19PM +0100, Adam D. Barratt wrote: > On Sat, 2018-10-27 at 22:44 +0200, Adam Borowski wrote: > > On Sat, Oct 27, 2018 at 04:21:09PM +0100, Adam D. Barratt wrote: > > > Control: tags -1 + confirmed > > > > In the meantime, anothe

Bug#909007: stretch-pu: package firetray/0.6.1+dfsg-1

2018-10-27 Thread Adam Borowski
On Sat, Oct 27, 2018 at 04:21:09PM +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Mon, 2018-09-17 at 13:09 +0200, Adam Borowski wrote: > > I'm afraid that the security update of thunderbird from 52 to 60 > > broke firetray, which, despite being a mere

Bug#909007: please include in stretch-updates

2018-09-22 Thread Adam Borowski
Hi! The upstream bug includes reports from users who tried the updated package on stable (stretch and ascii). Minus some confusion they had wrt apt source, it sounds like all is ok. Discussed in later parts of https://github.com/foudfou/FireTray/issues/238 Thus, it would be nice if you could

Bug#909007: stretch-pu: package firetray/0.6.1+dfsg-1

2018-09-17 Thread Adam Borowski
On Mon, Sep 17, 2018 at 08:02:10AM -1000, David Prévot wrote: > Le 17/09/2018 à 01:09, Adam Borowski a écrit : > > > The updated package is 100% identical to the version in unstable, only the > > version number differs (+deb9u1). > > Please, use ~deb9u1 instead: you don

Bug#909007: stretch-pu: package firetray/0.6.1+dfsg-1

2018-09-17 Thread Adam Borowski
ngelog2018-09-17 12:36:49.0 +0200 @@ -1,3 +1,12 @@ +firetray (0.6.1+dfsg-1+deb9u1) stretch; urgency=medium + + * Non-maintainer upload. + * Fix for Thunderbird 60 (by Fritjof Toelstede, Gabriele, and me). +Closes: #906852, #895451. + * Firefox and Iceweasel are no longer supported.

Re: Bug#873733: RFC: whitelist isa-support to allow it to abort installation?

2017-09-18 Thread Adam Borowski
On Mon, Sep 18, 2017 at 11:55:28AM +, Holger Levsen wrote: > Dear release team, > > I would like to ask you for your opinion on "#873733: please whitelist > isa-support so it's allowed to fail piuparts testing" to prevent piuparts > results from blocking isa-support's migration to testing.

Bug#865390: nmu: fonts-fantasque-sans_1.7.1~dfsg-1

2017-06-20 Thread Adam Borowski
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi! This font has some issues when built with fontforge 20120713, that have been solved in 20160404. All it takes is a clean rebuild against the version in stretch or unstable. Obviously,

Bug#851435: 0.11~beta4-1 -> 0.11-1

2017-01-28 Thread Adam Borowski
Control: retitle -1 unblock: duperemove/0.11-1 Hi! On Jan 26 (ie, 10 days before the hard freeze) I've sponsor-uploaded Peter's update, which replaces a beta with a regular upstream release, plus misc changes to the packaging. The rationale being, if you agree to let it pass, we want the package

Bug#851435: unblock: duperemove/0.11~beta4-1

2017-01-14 Thread Adam Borowski
Package: release.debian.org Severity: wishlist User: release.debian@packages.debian.org Usertags: unblock Hi! Would it be possible to unblock duperemove for stretch? It was uploaded 2¾ days before the 10-day deadline, but somehow it sat in NEW until now. Yeah, it's our fault -- the ITP was

Bug#840378: another stable update

2016-11-13 Thread Adam Borowski
On Sun, Nov 13, 2016 at 05:42:57PM +, Adam D. Barratt wrote: > On Mon, 2016-10-17 at 10:16 +0200, Salvatore Bonaccorso wrote: > > JFTR, I'm perfectly fine if -- in case accepted by the SRM -- my > > proposed debdiff just get squashed in in Mateusz upload, or if he > > want's to do the upload.

Bug#840378: #840378: another stable update

2016-10-17 Thread Adam Borowski
On Mon, Oct 17, 2016 at 08:34:05AM +0100, Adam D. Barratt wrote: > On 2016-10-17 1:03, Adam Borowski wrote: > >I see we have two different stable update attempts for openbox, both > >versioned 3.5.2-8+deb8u1: > >* NMU by Salvatore Bonaccorso fixing #808138 > >* maintaine

Bug#840378: #840378: another stable update

2016-10-16 Thread Adam Borowski
Hi guys! I see we have two different stable update attempts for openbox, both versioned 3.5.2-8+deb8u1: * NMU by Salvatore Bonaccorso fixing #808138 * maintainer upload by Mateusz Łukasik fixing #838326 (RFS #841017) I have no opinion about appropriateness of both updates, but as they seem to be

Bug#822487: jessie-pu: package mathematica-fonts/17+deb8u1

2016-04-24 Thread Adam Borowski
issing Depends: wget (closes: #817820). + + -- Adam Borowski <kilob...@angband.pl> Mon, 25 Apr 2016 00:06:16 +0200 + mathematica-fonts (17) unstable; urgency=medium * Updated Debconf Dutch translations. Thanks to Frans Spiesschaert diff -Nru mathematica-fonts-17/debian/control mathemat

Bug#807639: nmu: clementine_1.2.3+git1354-gdaddbde+dfsg-1

2015-12-10 Thread Adam Borowski
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu clementine_1.2.3+git1354-gdaddbde+dfsg-1 . ANY . unstable . -m "Rebuild against libechonest2.3" Hi! Due to a transition done wrong, clementine built against libechonest2.1 crashes on

Bug#769746: RM: lletters-media/0.1.9a-5

2014-11-15 Thread Adam Borowski
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi! Please remove lletters-media from jessie, it's a data package for lletters which is not a part of jessie, with nil chances of being introduced. -- To UNSUBSCRIBE, email to

Re: Jessie Freeze - What is the next release name? (jessie+1)

2014-11-08 Thread Adam Borowski
On Sat, Nov 08, 2014 at 06:13:31PM +0100, Javier Barroso wrote: On Wed, Nov 05, 2014 at 11:56:49PM +, Jonathan Wiltshire wrote: The release team is pleased to announce that Debian 8.0 Jessie is frozen. I thought usually this type of announcement comes with next release name. I

Proposed release goal: UTF-8 support

2013-09-30 Thread Adam Borowski
Hi! As previously (https://lists.debian.org/debian-devel/2013/08/msg00217.html) discussed, I'd like to propose improving support for UTF-8. All material shipped with Debian should be encoded this way, or, for media with an opaque format, as something capable of storing any Unicode character,

Re: Roll call for porters of architectures in sid and testing

2013-09-19 Thread Adam Borowski
On Sun, Sep 01, 2013 at 09:33:51AM +0200, Niels Thykier wrote: roll-call If ports not in unstable count, you can conditionally chalk me up for x32. Conditionally, as I refuse to do so if I were the only official porter, as I have little clue about the toolchain. Thus, I'd be up for these: -

Re: Bug#640499: hardening, too

2012-08-18 Thread Adam Borowski
On Sat, Aug 18, 2012 at 01:04:42PM +0200, Cyril Brulebois wrote: Adam Borowski kilob...@angband.pl (18/08/2012): I just got bit by the lack of multiarch here (wine is broken on amd64 if nvidia is involved), and wrote a multiarchification patch before realizing there's already one here

accepted but not in unstable yet: crawl

2010-08-06 Thread Adam Borowski
Hi! Somehow, even though crawl 2:0.7.1-3 has been uploaded and accepted on 9:02 this morning, it hasn't been picked up by either of the two dinstall runs since then. While buildds swiftly did their work and all arches except hurd-i386 and -ports are already built, all the results (including