Re: Debian openssh option review: considering splitting out GSS-API key exchange

libc and that's it... And that benefits everything that links to TCP wrappers... I also like to have the (old-school) standard extra layer of protection that libwrap can provide. I'd like to find a way to keep it useful for sshd. -- Henrique de Moraes Holschuh

Re: xz backdoor

d a VM though, when stable + container is not enough. -- Henrique de Moraes Holschuh

Re: Populating non-free firmware?

er: Henrique de Moraes Holschuh) > - amd64-microcode (maintainer: Henrique de Moraes Holschuh) Please email me directly when it is time to do such upload changing the archive section. I assume we (maintainers) don't need to do the usual dance of opening a bug to change the Dak override fi

Re: Bug#987980: ITP: infamous-plugins -- Infamous Plugins is a collection of open-source LV2 plugins

thing else more suitable... After all, lv2 is not the only thing with infamous plugins out there ;-) -- Henrique de Moraes Holschuh

Re: Bug#982945: ITP: asyncfuture -- Enhanced Qfuture (Qt) interface

Wookey, > Description : Enhanced Qfuture (Qt) interface > > AsyncFuture is designed to enhance the QFuture function, removing.. Maybe this should be prefixed with qt- since it is qt-specific and otherwise somewhat a generic naming? -- Henrique de Moraes Holschuh

Re: Making Debian available

That FAQ entry neither explains things well enough, nor is it very helpful. It could use an update... Heck, I am not even sure the installer could use anything in that non-free CD set to actually load non-free firmware at *install time* (as opposed to installing it to be available on the final system after a reboot) without a lot of manual intervention... -- Henrique de Moraes Holschuh

Re: Release status of i386 for Bullseye and long term support for 3 years?

orkloads. But I am fine keeping the status-quo of current i686 baseline as well: requiring SSE2 would kick out a non-trivial number of non-Intel processor models, I think we went over this the last time a "i386" baseline bump was considered. -- Henrique de Moraes Holschuh

Re: Pybliographer

tps://wiki.debian.org/RFP And include the explanation above. -- Henrique de Moraes Holschuh

Re: freepats (was: Re: Intend to remove obsolete debhelper compat levels 5 and 6 before the release of bookworm (bullseye + 1)

On Sat, 11 Jul 2020, Henrique de Moraes Holschuh wrote: > On Sat, 11 Jul 2020, Niels Thykier wrote: > > This is a heads up about my intention to remove debhelper compat levels > > 5 and 6. This is also an intention to do a MFB for this removal now at > > ... > > &

freepats (was: Re: Intend to remove obsolete debhelper compat levels 5 and 6 before the release of bookworm (bullseye + 1)

On Sat, 11 Jul 2020, Niels Thykier wrote: > This is a heads up about my intention to remove debhelper compat levels > 5 and 6. This is also an intention to do a MFB for this removal now at ... > Henrique de Moraes Holschuh >freepats Oh wow, I haven't looked at this packa

Re: Bug#964265: ITP: exfatprogs -- tools to create, check and label exFAT filesystems

On Sun, 05 Jul 2020, Andrei POPESCU wrote: > On Sb, 04 iul 20, 19:56:45, s...@stormbind.net wrote: > > While fuse-exfat can be coinstalled at any moment exfat-utils and > > exfatprogs will for now conflict with each other. > > Isn't this the typical use-case for alternatives? It depends. Are

Re: moving mg from salsa to github?

On Sat, 15 Feb 2020, Harald Dunkel wrote: > I am maintainer for mg, currently on salsa. Problem is, upstream > doesn't release tar balls anymore, but moved the code to github. > No tags. > > How can I tell Salsa? Should I drop the upstream and pristine-tar > branches on Salsa and integrate the

Accepted amd64-microcode 3.20191218.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 20 Dec 2019 18:36:27 -0300 Source: amd64-microcode Binary: amd64-microcode Architecture: source amd64 Version: 3.20191218.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Re: Vital fix to console-common stuck in testing for three months

On Mon, 16 Dec 2019, Oskar Berggren wrote: > This was reported in August 2019 as a grave bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935096 > > It was fixed early September in 0.7.91 and migrated to testing 2019-09-13: > https://tracker.debian.org/pkg/console-common > > Sadly, this

Accepted intel-microcode 3.20191115.2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 10 Dec 2019 23:10:19 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20191115.2 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Accepted intel-microcode 3.20191115.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Nov 2019 23:14:58 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20191115.1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique de

Accepted intel-microcode 3.20191113.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Nov 2019 00:43:54 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20191113.1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique de

Accepted intel-microcode 3.20191112.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Nov 2019 23:21:54 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20191112.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Accepted amd64-microcode 3.20191021.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Oct 2019 21:00:17 -0300 Source: amd64-microcode Binary: amd64-microcode Architecture: source amd64 Version: 3.20191021.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Accepted intel-microcode 3.20190918.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Sep 2019 00:38:50 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20190918.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Re: Programs contain ads - acceptable for packaging for Debian?

On Thu, 20 Jun 2019, Samuel Thibault wrote: > Bagas Sanjaya, le jeu. 20 juin 2019 20:16:08 +0700, a ecrit: > > On 20/06/19 20.11, W. Martin Borgert wrote: > > > Quoting Bagas Sanjaya : > > > > Such ads is displayed only when users have Internet connection, and > > > > there is no way to patch ZZZ

Accepted intel-microcode 3.20190618.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Jun 2019 09:05:54 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20190618.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Re: Official non-official Debian backporting versioning scheme

On Tue, 21 May 2019, Scott Kitterman wrote: > In Debian we use version-revision (where revision is sometimes complex for > backports and stable updates). If you use version-~revision where revision > is > some thing similar to, but different than that used for security updates, > stable

Accepted intel-microcode 3.20190514.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 14 May 2019 21:49:08 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20190514.1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique de

Re: Golang >= 1.12 in Buster?

On Mon, 15 Apr 2019, Thomas Goirand wrote: > On 4/15/19 9:24 AM, Hideki Yamane wrote: > > On Sun, 14 Apr 2019 21:11:09 +0200 > > "Dr. Tobias Quathamer" wrote: > >> I think it's the right decision of the release team to stick with golang > >> 1.11 for buster. The previous migration from golang

Re: DDs brasileiros(as) na DebConf19

On Fri, Apr 5, 2019, at 13:29, Paulo Henrique de Lima Santana wrote: > Como está a expectativa para vir para a DebConf19? Ainda indefinida :( Mas é certo que não poderei ir ao debcamp. -- Henrique de Moraes Holschuh

Accepted intel-microcode 3.20190312.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Mar 2019 21:07:54 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20190312.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Accepted amd64-microcode 3.20181128.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 15 Dec 2018 18:42:12 -0200 Source: amd64-microcode Binary: amd64-microcode Architecture: source amd64 Version: 3.20181128.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Accepted intel-microcode 3.20180807a.2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Oct 2018 19:52:40 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20180807a.2 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Accepted intel-microcode 3.20180807a.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 24 Aug 2018 08:53:53 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20180807a.1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique de

Re: salsa.debian.org maintenance (GitLab 11.1.4 upgrade, external storage migration)

On Mon, 13 Aug 2018, Alexander Wirt wrote: > We don't rely on it. There will be a backup on debian infastructure so that > we will be able to change to different providers at every time. ... > But using gce allows us to to support use cases different use case than just > git (like lfs, build

Bug#904917: general: Gnome randomly crash and restart to login.

On Sun, 29 Jul 2018, Riccardo Gagliarducci wrote: > on Lenovo laptop ideapad 520 Gnome randomly crash and, after some seconds of Are you using the latest version of the ideapad 520 firmware (BIOS/UEFI and EC) ? If not, please upgrade it. -- Henrique Holschuh

Re: Research survey: Impact of Microsoft Acquisition of GitHub

On Fri, 13 Jul 2018, Dominik George wrote: > > I don't think categorizing these things as spam is the right thing to do > > -- although ignoring them most of the time is. > > If they don't care enough about privacy and free software before doing a > survey in a privacy and free software community

Accepted intel-microcode 3.20180703.2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 05 Jul 2018 14:26:36 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20180703.2 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Accepted intel-microcode 3.20180703.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 05 Jul 2018 10:03:53 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20180703.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique

Accepted amd64-microcode 3.20180524.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 May 2018 15:38:22 -0300 Source: amd64-microcode Binary: amd64-microcode Architecture: source amd64 Version: 3.20180524.1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

Accepted amd64-microcode 3.20180515.1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 May 2018 13:51:06 -0300 Source: amd64-microcode Binary: amd64-microcode Architecture: amd64 i386 source Version: 3.20180515.1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh <h...@debian.

Accepted amd64-microcode 3.20171205.2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 04 May 2018 07:51:40 -0300 Source: amd64-microcode Binary: amd64-microcode Architecture: source amd64 Version: 3.20171205.2 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.

Accepted intel-microcode 3.20180425.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 02 May 2018 16:48:44 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20180425.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.

Accepted intel-microcode 3.20180312.1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 14 Mar 2018 09:21:24 -0300 Source: intel-microcode Binary: intel-microcode Architecture: amd64 i386 source Version: 3.20180312.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.

Re: Systemd dependencies

On Mon, 26 Feb 2018, Roberto C. Sánchez wrote: > On Mon, Feb 26, 2018 at 11:53:27AM +0100, Bastian Blank wrote: > > On Mon, Feb 26, 2018 at 11:13:03AM +0100, Michael Meskes wrote: > > > > However I really would start one step before. What exactly do you > > > > think > > > > a service dependency

Accepted autotools-dev 20180224.1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Feb 2018 13:00:57 -0300 Source: autotools-dev Binary: autotools-dev Architecture: source all Version: 20180224.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

Re: Debian part of a version number when epoch is bumped

On Wed, 14 Feb 2018, Vincent Bernat wrote: > ❦ 14 février 2018 12:53 +0100, Wouter Verhelst  : > >> > Would it hurt to take those epoch bumps into Debian? > >> > >> Depends on what you mean by hurt. I see epochs being used w/o much > >> tought or care, on many situations where

Accepted iucode-tool 2.3.1-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Feb 2018 22:42:31 -0200 Source: iucode-tool Binary: iucode-tool Architecture: source amd64 Version: 2.3.1-1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

Accepted iucode-tool 2.3-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 28 Jan 2018 13:46:14 -0200 Source: iucode-tool Binary: iucode-tool Architecture: source amd64 Version: 2.3-1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.org> Changed-By: He

Accepted intel-microcode 3.20180108.1+really20171117.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Jan 2018 23:01:59 -0200 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20180108.1+really20171117.1 Distribution: unstable Urgency: critical Maintainer: Henrique de Moraes Holschuh &l

Accepted intel-microcode 3.20180108.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jan 2018 00:23:44 -0200 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20180108.1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

Accepted amd64-microcode 3.20171205.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Jan 2018 12:19:57 -0200 Source: amd64-microcode Binary: amd64-microcode Architecture: source amd64 Version: 3.20171205.1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

Accepted intel-microcode 3.20171215.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 04 Jan 2018 23:04:38 -0200 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20171215.1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

Accepted autotools-dev 20171216.1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Dec 2017 13:05:22 -0200 Source: autotools-dev Binary: autotools-dev Architecture: source all Version: 20171216.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

Accepted intel-microcode 3.20171117.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 18 Nov 2017 18:55:09 -0200 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20171117.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.

Re: Summary of the 2038 BoF at DC17

On Sat, 02 Sep 2017, Steve McIntyre wrote: > Massive numbers of libraries are going to need updates, possibly more > than people realise. Anything embedding a time_t will obviously need > changing. However, many more structures will embed a timeval or > timespec and they're also broken. Almost

Accepted iucode-tool 2.2-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Aug 2017 15:47:46 -0300 Source: iucode-tool Binary: iucode-tool Architecture: source amd64 Version: 2.2-1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.org> Changed-By: He

Re: X facts about Debian - some fact checking and looking for ideas.

On Mon, 28 Aug 2017, shirish शिरीष wrote: > It would be helpful if somebody has one of the 1996 packages snapshots > and can share how the changelogs were at that point of time. That > might give a bit of reference as to how things were and if there were > any changes between them and now.

Re: Call for volunteers: FTP Team

On Thu, 17 Aug 2017, Joerg Jaspert wrote: > On 14767 March 1977, Jonathan Carter wrote: > >> it has been quite a while since the last call for volunteers, so here is > >> an update: Yeah, we still need people, and we want you. Well, that is, > >> if you are a Debian Developer, for this. If you are

Intel Skylake/Kaby Lake Hyper-threading bug update

TL;DR: Intel has issued public microcode updates in 2017-07-07, fixing the hyper-threading errata on every affected processor. These updates have been included in the stable and oldstable point releases from 2017-07-22. The microcode updates in the "intel-microcode" packages with the base

Re: Naming of network devices - how to improve it in buster

On Sat, 15 Jul 2017, Adam Borowski wrote: > > This will match any interface that has MAC address 01:23:45:67:89:ab, > > and will use the "foo" stanzas to configure it. > > Awesome! This sounds like the best solution so far. It is indeed Very Cool, but it might not solve one little thing:

Re: Naming of network devices - how to improve it in buster

On Fri, 14 Jul 2017, Tom H wrote: > > I've never seen the kernel vary the order it enumerates a PCI bus. It doesn't, the last time it changed was on 2.4->2.6. OTOH, *driver probe* ordering can and does change, especially when device probes are being done in parallel. It is best to not get bus

Re: Naming of network devices - how to improve it in buster

On Wed, 12 Jul 2017, Michael Biebl wrote: > Am 12.07.2017 um 18:58 schrieb Matt Zagrabelny: > > On Wed, Jul 12, 2017 at 11:47 AM, Michael Biebl > > wrote: > > > > Am 12.07.2017 um 17:35 schrieb Marc Haber: > > > My finger memory will still type

Accepted intel-microcode 3.20170707.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 08 Jul 2017 19:04:27 -0300 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20170707.1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

Re: Corruption in CPU

On Tue, 27 Jun 2017, Armin Avdic wrote: > Hello, I saw your article on corrupted data and I have reason to believe > that the bad code goes as far back to Intel Pentium D processors, in my The Intel Pentium D is a very old processor, and its hyper-threading is very different from the recent

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

(updated perl script, it now needs the "liblist-moreutils-perl" package) On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > > This warning advisory is relevant for users of systems with the Intel > > proce

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

(updates, hopefully the last ones...) On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > Fast-forward a few months, and Mark Shinwell noticed the mention of a > possible fix for a microcode defect with unknown hit-ratio in the > intel-microcode package changelog. H

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

On Mon, 26 Jun 2017, Holger Levsen wrote: > Are there any other public bug reports which got fixed by this, or is the > ocaml issue the only known issue which gets fixed by installing this microcode > update? As far as I know, so far OCaml is the only one that was verified to be caused by the

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

for the inconvenience. On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > Once you know your processor model name, you can check the two lists > below: > > * List of Intel processors code-named "Skylake": > http://ark.intel.com/products/codename/37572/Skylake > >

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

For the record: the email with the perl script doesn't contain malware. The "malware" alert came from an extremely badly configured system that violates every best practice in the field: it sends email to every original recipient (and not just to local users), and it FORGES its headers to look

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > This warning advisory is relevant for users of systems with the Intel > processors code-named "Skylake" and "Kaby Lake". These are: the 6th and > 7th generation Intel Core processors (desktop, embedded, mobi

[WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

This warning advisory is relevant for users of systems with the Intel processors code-named "Skylake" and "Kaby Lake". These are: the 6th and 7th generation Intel Core processors (desktop, embedded, mobile and HEDT), their related server processors (such as Xeon v5 and Xeon v6), as well as select

Accepted iucode-tool 2.1.2-2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 18 Jun 2017 22:46:47 -0300 Source: iucode-tool Binary: iucode-tool Architecture: source amd64 Version: 2.1.2-2 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

Re: Please add lzip support in the repository

On Fri, 16 Jun 2017, Adrian Bunk wrote: > On Thu, Jun 15, 2017 at 08:36:48PM -0300, Henrique de Moraes Holschuh wrote: > >... > > We pretty much need Debian packages to be 100% correct in the first > > place, they are not going to be subject to lossy recovery from > >

Re: Please add lzip support in the repository

On Thu, 15 Jun 2017, mariabi...@gmail.com wrote: > PS: lzip version available in Debian is 1.16, but the last one is 1.19. Maybe > it's time to update! :) lzip 1.19 is available just in Debian experimental, because we are in final-countdown nearly-absolute freeze: we will release the next Debian

Re: Please add lzip support in the repository

On Thu, 15 Jun 2017, Christoph Biedl wrote: > Also I doubt the reduced disk space and network bandwitdth usage of any > new kid on the block (there's also zstd) really justifies the work > needed to implement the support in the many tools that deal with the > files. I might be convinced

Re: Too many Recommends (in particular on mail-transport-agent)

On Mon, 12 Jun 2017, Anthony DeRobertis wrote: > Of course—for the under 100K being saved here, only Rube Goldberg would > approve. It is a bit less than 1MiB saved on an AMD system when you purge intel-microcode, but even that is likely to not be considered worth the cost of the extra (empty)

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On Sun, 11 Jun 2017, Sean Whitton wrote: > Henrique de Moraes Holschuh <h...@debian.org> writes: > > > Not just that. If it is for NMUs, one also has to ensure it matches > > what got uploaded (regardless of method: NMU patch, PR, branch...). > > I'm not su

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On Fri, 09 Jun 2017, Tollef Fog Heen wrote: > > Per the DEP: > > > > > it is very useful for a maintainer to know that a change has been > > > approved by someone who has been trusted by the project with the > > > technical ability to NMU the package > > > > This would be much more cumbersome to

Re: Switch default installation image link?

On Tue, 06 Jun 2017, Adam Borowski wrote: > No one installs i386 new -- machines that are non-amd64-capable are: > * mainstream machines from 2004 and earlier That date is incorrect. I can't give you a precise date, but the Thinkpad T43 with a 32-bit Centrino Pentium-M was **launched** in

Re: Too many Recommends (in particular on mail-transport-agent)

On Fri, 02 Jun 2017, Anthony DeRobertis wrote: > On 06/01/2017 01:00 PM, Henrique de Moraes Holschuh wrote: > >Anything on the top three priorities (critical, alert and emergency) is > >supposed to be displayed immediately to all logged-in users (including > >remote

Re: Too many Recommends (in particular on mail-transport-agent)

On Thu, 01 Jun 2017, Anthony DeRobertis wrote: > On May 31, 2017 3:51:33 AM EDT, Simon McVittie > wrote: > >Can't it report this via the system log? (syslog, systemd-journald) > > The kernel already does, but of course the system log has a lot of > messages, every several

Re: Too many Recommends (in particular on mail-transport-agent)

On Wed, 31 May 2017, Adam Borowski wrote: > Thus, axing this dependency or degrading it to Suggests would be probably a > good idea. And there's hundreds if not thousands of Recommends of this kind > that need to be looked at -- this example is just more prominent as it > affects every Debian

Accepted intel-microcode 3.20170511.1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 15 May 2017 15:12:25 -0300 Source: intel-microcode Binary: intel-microcode Architecture: amd64 i386 source Version: 3.20170511.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.

Re: Machine Parsable Release Information Specification

On Fri, 05 May 2017, Benjamin Drung wrote: > I am sending this mail to the development list of the distributions > CentOS, Debian, Fedora, openSUSE and Ubuntu. I am working for > ProfitBricks and we provide public images in our cloud for these > distributions. > > Currently I know no way to

Re: policy for shipping sysctl.d snippets in packages?

On Sun, 23 Apr 2017, Evgeni Golov wrote: > Both, procps and systemd support (/usr)?/lib/sysctl.d/*.conf, however only > one package (systemd-coredump) uses it, all others drop files in > /etc/sysctl.d. Please drop it in /etc, debhelper/dh should mark it as conffile and everything will work.

Re: changelog practice, unfinalised vs UNRELEASED vs ~version

for changelog-updating commits before release (or maybe at the tip of every ready-for-integration branch, etc), but... [1] refer to dpkg-mergechangelogs(1) for the git driver for debian/changelog, for example. [2] as in "less busywork" while hacking, and no weird (and possibly maintenanc

Re: Fwd: [Bug 1671099] [NEW] GNOME Software catalog entry missing for Runescape

On Wed, 08 Mar 2017, Carlos Donizete Froes wrote: > Minha pergunta é, sera que a politica do Ubuntu não esta mais aceitando mais > este formato de imagem .xpm e no Debian também não poderei, tendo que passar > para formato .png ? Debian não considera AppStream ou GNOME software catalog como

Accepted iucode-tool 2.1.2-1 (source amd64) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 15 Feb 2017 20:53:55 -0200 Source: iucode-tool Binary: iucode-tool Architecture: source amd64 Version: 2.1.2-1 Distribution: experimental Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

Re: manpages.debian.org has been modernized!

On Wed, 18 Jan 2017, Michael Stapelberg wrote: > https://manpages.debian.org has been modernized! We have just launched > a major update to our manpage repository. What used to be served via a > CGI script is now a statically generated website, and therefore > blazingly fast. Oooh, nice! A big

Accepted iucode-tool 2.1.1-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 13 Jan 2017 10:36:00 -0200 Source: iucode-tool Binary: iucode-tool Architecture: source amd64 Version: 2.1.1-1 Distribution: unstable Urgency: high Maintainer: Henrique de Moraes Holschuh <h...@debian.org> Changed-By: He

Re: Debian Member - Talk

rar em contato com ela para obter uma visão geral no âmbito internacional... --   Henrique de Moraes Holschuh <h...@debian.org>

Accepted amd64-microcode 3.20160316.3 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Nov 2016 23:54:53 -0200 Source: amd64-microcode Binary: amd64-microcode Architecture: source amd64 Version: 3.20160316.3 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.

Re: Installing missing conffiles (was Re: dpkg no longer installs conffiles??)

On Wed, 30 Nov 2016, Guillem Jover wrote: > On Tue, 2016-11-29 at 19:18:41 +0100, Simon Richter wrote: > > To force reinstallation of configuration files, invoke dpkg with the > > "--force-confmiss" option when installing. This will only restore > > missing configuration files, but not overwrite

Re: Difference in behaviour between pbuilder and sbuild

set and exported inside debian/rules. -- Henrique de Moraes Holschuh <h...@debian.org>

Re: OpenSSL 1.1.0

On Thu, 24 Nov 2016, Adrian Bunk wrote: > On Wed, Nov 23, 2016 at 11:50:12PM -0200, Henrique de Moraes Holschuh wrote: > > On Thu, 24 Nov 2016, Kurt Roeckx wrote: > >... > > > > So, if Qt *ever* exposes its use of openssl anywere in its APIs, it > > > >

Re: OpenSSL 1.1.0

On Thu, 24 Nov 2016, Kurt Roeckx wrote: > I've always had the impression that there are or used to be > probems using using dlopen()/dlsym(). Maybe related to some things > like RTDL_GLOBAL that causes the symbol lookup to go to the wrong > library. Do you know of any problems related to that?

Re: OpenSSL 1.1.0

use of openssl anywere in its APIs, it might not be safe. If it doesn't (i.e. at most you have a qt flag that says "use SSL", etc), then it should be fine. -- Henrique de Moraes Holschuh <h...@debian.org>

Re: libc recently more aggressive about pthread locks in stable ?

On Thu, Nov 17, 2016, at 12:12, Adrian Bunk wrote: > On Thu, Nov 17, 2016 at 11:38:46AM -0200, Henrique de Moraes Holschuh > wrote: > > On Thu, Nov 17, 2016, at 09:50, Adrian Bunk wrote: > > > But we do already have > 1 year of widespread testing by users > > > run

Re: libc recently more aggressive about pthread locks in stable ?

664: stepping Y0 -- BDE85 fixed by up-to-date microcode). Also, Broadwell-EN/EP/EX (Core Extreme 5th gen, Xeon E5v4 and E7v4) are not blacklisted, either. -- Henrique de Moraes Holschuh <h...@debian.org>

Re: libc recently more aggressive about pthread locks in stable ?

On Thu, Nov 17, 2016, at 09:11, Lucas Nussbaum wrote: > On 17/11/16 at 08:31 -0200, Henrique de Moraes Holschuh wrote: > > The deal with *current* Debian stable is that, if the breakage is too > > widespread, we simply might not be able to do the right thing (fix the > > r

Re: libc recently more aggressive about pthread locks in stable ?

On Sun, Nov 13, 2016, at 14:42, Lucas Nussbaum wrote: > On 12/11/16 at 18:51 -0200, Henrique de Moraes Holschuh wrote: > > Thanks for trying a build run with TSX enabled. > > > > On Sat, 12 Nov 2016, Lucas Nussbaum wrote: > > > I did an archive rebuild on Amazon E

Re: libc recently more aggressive about pthread locks in stable ?

On Wed, Nov 9, 2016, at 06:26, Lucas Nussbaum wrote: > On 08/11/16 at 16:01 -0200, Henrique de Moraes Holschuh wrote: > > I fear it might be bad, but > > I would love to be pleasantly surprised that people did get libpthreads > > locking right most of the time... > &

Accepted autotools-dev 20161112.1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 12 Nov 2016 18:18:52 -0200 Source: autotools-dev Binary: autotools-dev Architecture: source all Version: 20161112.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh <h...@debian.org> C

  1   2   3   4   5   6   7   8   9   10   >