Bug#953875: runit - default installation wants to remove systemd

2020-03-14 Thread Bastian Blank
Source: runit Version: 2.1.2-35 Severity: critical An installation attempt on a default system (with recommends enabled) of runit wants to replace the installed init: | $ sudo apt install runit | Reading package lists... Done | Building dependency tree | Reading state information... Done | The

Re: cloud-init should not depend on cloud-guest-utils anymore

2020-03-08 Thread Bastian Blank
On Sat, Mar 07, 2020 at 01:40:53AM +0100, Marco d'Itri wrote: > Nowadays (since Debian 10) systemd can automatically grow file systems > and swap partitions just by adding the x-systemd.growfs flag to fstab. Thanks for letting us know. I added the flag and as announced it works fine:

Re: Xen update request and status

2020-03-02 Thread Bastian Blank
ne about Xen. Also there are no plans to support Xen for a possible Jessie ELTS. Regards, Bastian Blank -- Oh, that sound of male ego. You travel halfway across the galaxy and it's still the same song. -- Eve McHuron, "Mudd's Women", stardate 1330.1

Re: Xen update request and status

2020-02-24 Thread Bastian Blank
Hi Robert On Sat, Feb 22, 2020 at 09:14:10AM -0500, Roberto C. Sánchez wrote: > Is it then Credativ's intent to continue maintenance of Xen 4.4? If so, > could you provide some information on when we might expect the next > update? If not, I would like to request that you begin the process of >

Using Salsa via OIDC to authenticate to AWS

2020-02-18 Thread Bastian Blank
Hi folks Next step in our quest to have usable AWS accounts is user handling. I looked into the available options. Those are local account or federation via SAML or OpenID Connect. Federation needs both an external user source and some glue, due to the internal handling in AWS. Local users

Bug#950079: grub-cloud-amd64: prompting due to modified conffiles which were not modified by the user: /etc/default/grub

2020-02-17 Thread Bastian Blank
Control: severity -1 important On Tue, Jan 28, 2020 at 09:25:28PM +0100, Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed the piuparts > upgrade test because dpkg detected a conffile as being modified and then > prompted the user for an action. As there is no

Bug#950079: grub-cloud-amd64: prompting due to modified conffiles which were not modified by the user: /etc/default/grub

2020-02-17 Thread Bastian Blank
Control: severity -1 important On Tue, Jan 28, 2020 at 09:25:28PM +0100, Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed the piuparts > upgrade test because dpkg detected a conffile as being modified and then > prompted the user for an action. As there is no

Bug#950079: grub-cloud-amd64: prompting due to modified conffiles which were not modified by the user: /etc/default/grub

2020-02-17 Thread Bastian Blank
Control: severity -1 important On Tue, Jan 28, 2020 at 09:25:28PM +0100, Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed the piuparts > upgrade test because dpkg detected a conffile as being modified and then > prompted the user for an action. As there is no

Re: moving mg from salsa to github?

2020-02-15 Thread Bastian Blank
Hi Harald On Sat, Feb 15, 2020 at 02:16:27PM +0100, 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. This is nothing uncommon. > No tags. So this upstream doesn't make releases but only

[SECURITY] [DLA 2101-1] libemail-address-list-perl security update

2020-02-12 Thread Bastian Blank
Package: libemail-address-list-perl Version: 0.05-1+deb8u1 CVE ID : CVE-2018-18898 An denial of service via an algorithmic complexity attack on email address parsing have been identified in libemail-address-list-perl. For Debian 8 "Jessie", this problem has been fixed

[Git][security-tracker-team/security-tracker][master] Reserve DLA-2101-1 for libemail-address-list-perl

2020-02-12 Thread Bastian Blank
Bastian Blank pushed to branch master at Debian Security Tracker / security-tracker Commits: e37a8577 by Bastian Blank at 2020-02-12T15:20:22+01:00 Reserve DLA-2101-1 for libemail-address-list-perl - - - - - 2 changed files: - data/CVE/list - data/DLA/list Changes

Re: Message encoding by guessing

2020-02-09 Thread Bastian Blank
On Sun, Feb 09, 2020 at 01:45:21PM +0300, wes...@199903.xyz wrote: > How to guess the message body’s language encoding if message didn’t have MIME > charset set?  The message may be encoded with utf8, gb2312, gbk or something > others, but it didn’t have an charset header. Well, text/*, with

Re: Contacting cloud team for hosting blends.debian.net [elb...@debian.org: Re: Any sponsoring for a VM possible (Was: Rackspace ending free hosting for blends.debian.net)]

2020-02-09 Thread Bastian Blank
Hi On Thu, Feb 06, 2020 at 08:10:52PM +0100, Andreas Tille wrote: > [Sorry for the delay. I'm not reading the list and just found it now in the > archive.] I sent the original to andr...@an3as.eu too. It was properly received by mail.an3as.eu[88.198.124.37]:25, replying with "250 OK

Re: Heads up: persistent journal has been enabled in systemd

2020-02-05 Thread Bastian Blank
Hi Scott On Wed, Feb 05, 2020 at 07:44:25AM +, Scott Kitterman wrote: > >> Of course the fact that I can't use all the tools available to > >manipulate text > >> files to follow or analyze logs is problematic. If I'm using > >journalctl, how > >> do I replicate 'tail -f

Re: Heads up: persistent journal has been enabled in systemd

2020-02-04 Thread Bastian Blank
On Wed, Feb 05, 2020 at 09:39:19AM +1100, Dmitry Smirnov wrote: > For example, if a certain daemon manifested a condition when a message is > logged too often, then with Rsyslog I could suppress noise by something like > the following This is a workaround for another problem. Fix the real

Re: Contacting cloud team for hosting blends.debian.net [elb...@debian.org: Re: Any sponsoring for a VM possible (Was: Rackspace ending free hosting for blends.debian.net)]

2020-02-01 Thread Bastian Blank
On Fri, Jan 31, 2020 at 08:59:36PM +0100, Andreas Tille wrote: > I admit I'm not educated about those technical details. All I know is > that time for blends.debian.net is running out today. A simple answer > like: "We can not provide any VM to replace blends.debian.net" or "We > could provide

Bug#950167: Acknowledgement (icinga2-bin - Racy timeout in API: No data received on new API connection)

2020-01-29 Thread Bastian Blank
Hi It seems like I found a workaround: hard disable TLS 1.3 in OpenSSL: /etc/ssl/openssl.conf: | [system_default_sect] | MinProtocol = TLSv1.2 | MaxProtocol = TLSv1.2 | CipherString = DEFAULT@SECLEVEL=2 Bastian -- Military secrets are the most fleeting of all. -- Spock, "The

Bug#950167: icinga2-bin - Racy timeout in API: No data received on new API connection

2020-01-29 Thread Bastian Blank
Package: icinga2-bin Version: 2.10.3-2 Severity: important Hi I upgraded the master and one satelite of a larger Icinga2 setup to Buster. After the upgrade those two instances where unable to establish a working API connection. Connections between the new master and the Stretch instances still

Bug#947847: please install systemd-sysusers using update-alternatives

2020-01-29 Thread Bastian Blank
On Wed, Jan 29, 2020 at 05:06:31PM +0100, Svante Signell wrote: > * E) systemd is not available on non-Linux - You don't need an alternative for something that does not exist. - Have you ever tried to build those parts of the systemd package on your favorite glibc non-Linux? Bastian --

Bug#949788: s390-dasd FTCBFS: strips with the build architecture strip

2020-01-24 Thread Bastian Blank
Moin On Sat, Jan 25, 2020 at 05:50:40AM +0100, Helmut Grohne wrote: > s390-dasd fails to cross build from source, because it strips using the > build architecture strip during build. Beyond breaking cross > compilation, this also breaks DEB_BUILD_OPTIONS=nostrip as well as > generation of -dbgsym

Bug#949788: s390-dasd FTCBFS: strips with the build architecture strip

2020-01-24 Thread Bastian Blank
Moin On Sat, Jan 25, 2020 at 05:50:40AM +0100, Helmut Grohne wrote: > s390-dasd fails to cross build from source, because it strips using the > build architecture strip during build. Beyond breaking cross > compilation, this also breaks DEB_BUILD_OPTIONS=nostrip as well as > generation of -dbgsym

Accepted waagent 2.2.45-2 (source) into unstable

2020-01-20 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Jan 2020 16:34:23 +0100 Source: waagent Architecture: source Version: 2.2.45-2 Distribution: unstable Urgency: medium Maintainer: Bastian Blank Changed-By: Bastian Blank Changes: waagent (2.2.45-2) unstable; urgency

Bug#948041: impossible to update libbpf without updating the kernel

2020-01-18 Thread Bastian Blank
On Wed, Jan 15, 2020 at 12:50:16PM +, Sudip Mukherjee wrote: > On Wed, Jan 15, 2020 at 06:12:05AM +, Jonathan Nieder wrote: > > I agree --- if upstream development were happening in > > https://github.com/libbpf/libbpf then this would be a no-brainer. It > > appears to instead be a mirror

Bug#948041: impossible to update libbpf without updating the kernel

2020-01-18 Thread Bastian Blank
On Wed, Jan 15, 2020 at 12:50:16PM +, Sudip Mukherjee wrote: > On Wed, Jan 15, 2020 at 06:12:05AM +, Jonathan Nieder wrote: > > I agree --- if upstream development were happening in > > https://github.com/libbpf/libbpf then this would be a no-brainer. It > > appears to instead be a mirror

Bug#948041: impossible to update libbpf without updating the kernel

2020-01-12 Thread Bastian Blank
Hi Sudip On Sun, Jan 12, 2020 at 12:28:20AM +, Sudip Mukherjee wrote: > On Fri, Jan 03, 2020 at 08:23:58PM +, Sudip Mukherjee wrote: > > > What are the benefits of doing so? > > The only benefit will be that we will be able to update the libraries > > irrespective of kernel update. libbpf

Bug#948041: impossible to update libbpf without updating the kernel

2020-01-12 Thread Bastian Blank
Hi Sudip On Sun, Jan 12, 2020 at 12:28:20AM +, Sudip Mukherjee wrote: > On Fri, Jan 03, 2020 at 08:23:58PM +, Sudip Mukherjee wrote: > > > What are the benefits of doing so? > > The only benefit will be that we will be able to update the libraries > > irrespective of kernel update. libbpf

Bug#947220: lvm2: System unbootable with cached root and latest kernel

2020-01-09 Thread Bastian Blank
Control: reassign -1 thin-provisioning-tools Control: forcemerge 931514 -1 Moin On Mon, Dec 23, 2019 at 03:05:15AM +, Stefanos Harhalakis wrote: > Justification: breaks the whole system No, it does not. However, this is fixed in thin-provisioning-tools. Bastian -- Peace was the way.

Bug#947220: lvm2: System unbootable with cached root and latest kernel

2020-01-09 Thread Bastian Blank
Control: reassign -1 thin-provisioning-tools Control: forcemerge 931514 -1 Moin On Mon, Dec 23, 2019 at 03:05:15AM +, Stefanos Harhalakis wrote: > Justification: breaks the whole system No, it does not. However, this is fixed in thin-provisioning-tools. Bastian -- Peace was the way.

Accepted lvm2 2.03.07-1 (source) into unstable

2020-01-07 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 07 Jan 2020 14:44:41 +0100 Source: lvm2 Architecture: source Version: 2.03.07-1 Distribution: unstable Urgency: medium Maintainer: Debian LVM Team Changed-By: Bastian Blank Changes: lvm2 (2.03.07-1) unstable; urgency=medium

Accepted thin-provisioning-tools 0.8.5-4 (source) into unstable

2020-01-07 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 07 Jan 2020 11:21:13 +0100 Source: thin-provisioning-tools Architecture: source Version: 0.8.5-4 Distribution: unstable Urgency: medium Maintainer: Debian LVM Team Changed-By: Bastian Blank Changes: thin-provisioning-tools

Accepted lvm2 2.03.02-4 (source) into unstable

2020-01-06 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 06 Jan 2020 17:53:00 +0100 Source: lvm2 Architecture: source Version: 2.03.02-4 Distribution: unstable Urgency: medium Maintainer: Debian LVM Team Changed-By: Bastian Blank Changes: lvm2 (2.03.02-4) unstable; urgency=medium

Accepted dpkg-source-gitarchive 0.1.2 (source) into unstable

2020-01-06 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 06 Jan 2020 17:50:40 +0100 Source: dpkg-source-gitarchive Architecture: source Version: 0.1.2 Distribution: unstable Urgency: medium Maintainer: Bastian Blank Changed-By: Bastian Blank Changes: dpkg-source-gitarchive (0.1.2

Re: opentmpfiles & opensysusers, and its use in the Debian policy

2020-01-03 Thread Bastian Blank
On Fri, Jan 03, 2020 at 02:29:37PM -0500, The Wanderer wrote: > The accepting of init scripts seemed to me like an essential piece of > making sure those scripts would be present wherever they would be > needed. Your suggestion above seems to provide a way to make it less > essential, and thus

Bug#948041: impossible to update libbpf without updating the kernel

2020-01-03 Thread Bastian Blank
Hi Marco On Fri, Jan 03, 2020 at 06:59:36PM +0100, Marco d'Itri wrote: > On Jan 03, Sudip Mukherjee wrote: > > Do we package libbpf from their github repo independent of the kernel > > update? Then we will need to remove the libbpf building bits from the > > Debian kernel source and create a

Bug#948041: impossible to update libbpf without updating the kernel

2020-01-03 Thread Bastian Blank
Hi Marco On Fri, Jan 03, 2020 at 06:59:36PM +0100, Marco d'Itri wrote: > On Jan 03, Sudip Mukherjee wrote: > > Do we package libbpf from their github repo independent of the kernel > > update? Then we will need to remove the libbpf building bits from the > > Debian kernel source and create a

Re: opentmpfiles & opensysusers, and its use in the Debian policy

2020-01-03 Thread Bastian Blank
On Fri, Jan 03, 2020 at 10:31:53AM -0800, Russ Allbery wrote: > Support for kFreeBSD and Hurd is obviously a valid argument in favor of > some level of support for non-systemd implementations. But then there is the question on how much work it would be to port the **systemd** implementations to

Accepted thin-provisioning-tools 0.8.5-3 (source) into unstable

2020-01-03 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Jan 2020 14:37:26 +0100 Source: thin-provisioning-tools Architecture: source Version: 0.8.5-3 Distribution: unstable Urgency: medium Maintainer: Debian LVM Team Changed-By: Bastian Blank Closes: 931514 Changes: thin

Accepted dpkg-source-gitarchive 0.1.1 (source) into unstable

2020-01-03 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Jan 2020 13:23:12 +0100 Source: dpkg-source-gitarchive Architecture: source Version: 0.1.1 Distribution: unstable Urgency: medium Maintainer: Bastian Blank Changed-By: Bastian Blank Changes: dpkg-source-gitarchive (0.1.1

Accepted ipxe 1.0.0+git-20190125.36a4c85-4 (source) into unstable

2020-01-02 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Jan 2020 21:36:39 +0100 Source: ipxe Architecture: source Version: 1.0.0+git-20190125.36a4c85-4 Distribution: unstable Urgency: medium Maintainer: Bastian Blank Changed-By: Bastian Blank Closes: 947267 Changes: ipxe

Accepted dpkg-source-gitarchive 0.1.0 (source all) into unstable, unstable

2020-01-02 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Jan 2020 17:28:13 +0100 Source: dpkg-source-gitarchive Binary: dpkg-source-gitarchive Architecture: source all Version: 0.1.0 Distribution: unstable Urgency: medium Maintainer: Bastian Blank Changed-By: Bastian Blank

Re: STARTTLS and PCI requirements

2020-01-02 Thread Bastian Blank
On Thu, Jan 02, 2020 at 12:16:33PM -0500, James B. Byrne wrote: > We recently were forced by our PCI compliance audit to change our > permissible ciphers. I speculate that this is the source of our > problem. Our revised cipher list is: Don't, as long as you don't enforce encryption as well.

[Pkg-javascript-devel] node-clipboard_1.7.1-1_amd64.changes REJECTED

2020-01-01 Thread Bastian Blank
Dear maintainer This package produces a lot of lintian warnings: W: node-clipboard: nodejs-module-installed-in-usr-lib usr/lib/nodejs/clipboard/dist/clipboard.js W: node-clipboard: nodejs-module-installed-in-usr-lib usr/lib/nodejs/clipboard/lib/clipboard-action.js Also, node-clipboard

Re: smtpd_policy_service_timeout question

2019-12-29 Thread Bastian Blank
Hi Scott On Sun, Dec 29, 2019 at 10:04:39AM -0500, Scott Kitterman wrote: > For the policy server in question, the 100s default should be more than 2x > the > maximum time the policy request can take, even if DNS is very slow, The policy service is supposed to do proper timeouts for everything

Re: are Debian mentors nuts? the DebConf scandal

2019-12-28 Thread Bastian Blank
Hi Matthew On Sun, Dec 29, 2019 at 04:59:27AM +, Matthew Garrett wrote: > Just in case anyone's wondering - I checked with Mary-Anne Wolf (who I > met at Libreplanet some years ago) and she didn't send this mail. > Someone faked her identity. This mail was sent via the same way as the

Sentry for Debian services?

2019-12-25 Thread Bastian Blank
Hi Salsa is a pretty complex beast. As such it got errors. And especially user visible errors. To manage and correlate information about such errors it supports Sentry, which is the de-facto standard to do that work. Sure, the same information can be read from the log, but this is not really

Bug#925411: Removing kernel-package? (was: kernel-package: Not suitable for release)

2019-12-25 Thread Bastian Blank
Hi Manoj Do you oppose that we finally shoot kernel-package dead, aka remove it from the archive? Regards, Bastian -- Youth doesn't excuse everything. -- Dr. Janice Lester (in Kirk's body), "Turnabout Intruder", stardate 5928.5.

Bug#925411: Removing kernel-package? (was: kernel-package: Not suitable for release)

2019-12-25 Thread Bastian Blank
Hi Manoj Do you oppose that we finally shoot kernel-package dead, aka remove it from the archive? Regards, Bastian -- Youth doesn't excuse everything. -- Dr. Janice Lester (in Kirk's body), "Turnabout Intruder", stardate 5928.5.

Bug#947340: linux-base: can't be upgraded

2019-12-25 Thread Bastian Blank
Hi Christoph On Wed, Dec 25, 2019 at 03:06:19AM +0100, Christoph Anton Mitterer wrote: > Since last April, the package can't be upgraded as it conflicts with > the current version of kernel-common. kernel-common was neither released in Stretch, nor in Buster. > but then this should be reflected

Bug#947340: linux-base: can't be upgraded

2019-12-25 Thread Bastian Blank
Hi Christoph On Wed, Dec 25, 2019 at 03:06:19AM +0100, Christoph Anton Mitterer wrote: > Since last April, the package can't be upgraded as it conflicts with > the current version of kernel-common. kernel-common was neither released in Stretch, nor in Buster. > but then this should be reflected

Bug#947340: linux-base: can't be upgraded

2019-12-25 Thread Bastian Blank
Hi Christoph On Wed, Dec 25, 2019 at 03:06:19AM +0100, Christoph Anton Mitterer wrote: > Since last April, the package can't be upgraded as it conflicts with > the current version of kernel-common. kernel-common was neither released in Stretch, nor in Buster. > but then this should be reflected

Accepted ipxe 1.0.0+git-20190125.36a4c85-3 (source) into unstable

2019-12-19 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Dec 2019 19:32:59 +0100 Source: ipxe Architecture: source Version: 1.0.0+git-20190125.36a4c85-3 Distribution: unstable Urgency: medium Maintainer: Bastian Blank Changed-By: Bastian Blank Closes: 947024 Changes: ipxe

Bug#947024: ipxe-qemu: grub2 tests fail after upgrade to 1.0.0+git-20190125.36a4c85-2

2019-12-19 Thread Bastian Blank
Control: tags -1 pending Hi Colin On Thu, Dec 19, 2019 at 05:14:11PM +, Colin Watson wrote: > OK, I bisected this to this commit: > > https://salsa.debian.org/waldi/ipxe/commit/56212b3037321d709184c5aed48b91b0a1bbd06e > Happy to try further tests if you have any suggestions. I feared it

Bug#947024: ipxe-qemu: grub2 tests fail after upgrade to 1.0.0+git-20190125.36a4c85-2

2019-12-19 Thread Bastian Blank
Control: tags -1 pending Hi Colin On Thu, Dec 19, 2019 at 05:14:11PM +, Colin Watson wrote: > OK, I bisected this to this commit: > > https://salsa.debian.org/waldi/ipxe/commit/56212b3037321d709184c5aed48b91b0a1bbd06e > Happy to try further tests if you have any suggestions. I feared it

Accepted ipxe 1.0.0+git-20190125.36a4c85-2 (source) into unstable

2019-12-14 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 14 Dec 2019 21:43:28 +0100 Source: ipxe Architecture: source Version: 1.0.0+git-20190125.36a4c85-2 Distribution: unstable Urgency: medium Maintainer: Bastian Blank Changed-By: Bastian Blank Closes: 944321 Changes: ipxe

Accepted thin-provisioning-tools 0.8.5-2 (source) into unstable

2019-12-14 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 14 Dec 2019 18:24:35 +0100 Source: thin-provisioning-tools Architecture: source Version: 0.8.5-2 Distribution: unstable Urgency: medium Maintainer: Debian LVM Team Changed-By: Bastian Blank Closes: 930685 Changes: thin

Re: list of upstream tarball signing schemes?

2019-12-13 Thread Bastian Blank
On Fri, Dec 13, 2019 at 10:55:34AM +0100, Thomas Koch wrote: > I'm packaging nix: https://nixos.org/releases/nix/latest > It releases 3 files: > nix-2.3.1.tar.xz.asc - which signs the .sha256 Why does this not contain a signature of the file itself? The correct filename for this schema would be

Accepted thin-provisioning-tools 0.8.5-1 (source) into unstable

2019-12-12 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Dec 2019 22:17:43 +0100 Source: thin-provisioning-tools Architecture: source Version: 0.8.5-1 Distribution: unstable Urgency: medium Maintainer: Debian LVM Team Changed-By: Bastian Blank Changes: thin-provisioning-tools

Accepted grub-cloud 0.0.5 (source) into unstable

2019-12-08 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 08 Dec 2019 13:35:18 +0100 Source: grub-cloud Architecture: source Version: 0.0.5 Distribution: unstable Urgency: medium Maintainer: Debian Cloud Team Changed-By: Bastian Blank Changes: grub-cloud (0.0.5) unstable; urgency

Accepted waagent 2.2.45-1 (source) into unstable

2019-12-06 Thread Bastian Blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 Dec 2019 14:00:41 +0100 Source: waagent Architecture: source Version: 2.2.45-1 Distribution: unstable Urgency: medium Maintainer: Bastian Blank Changed-By: Bastian Blank Closes: 911701 Changes: waagent (2.2.45-1

Bug#945542: [Pkg-rust-maintainers] Bug#945542: debcargo -- Randomly adds and removes binary packages

2019-11-30 Thread Bastian Blank
Hi Russ On Fri, Nov 29, 2019 at 10:35:04AM -0800, Russ Allbery wrote: > Procedurally in Debian neither of these are justifications for setting the > severity to serious. This is not a Policy requirement that has reached > consensus, and the release team is the team in Debian that has the >

Bug#945542: [Pkg-rust-maintainers] Bug#945542: Bug#945542: debcargo -- Randomly adds and removes binary packages

2019-11-29 Thread Bastian Blank
On Fri, Nov 29, 2019 at 02:49:21PM +0100, Sylvestre Ledru wrote: > Le 29/11/2019 à 14:07, Bastian Blank a écrit : > > The output of debcargo breaks the Debian archive by increasing the > > Package file much more then it needs to do. > Breaks seems a strong word, no? It adds blo

Bug#945542: [Pkg-rust-maintainers] Bug#945542: debcargo -- Randomly adds and removes binary packages

2019-11-29 Thread Bastian Blank
Hi Ximin On Fri, Nov 29, 2019 at 12:24:38PM +, Ximin Luo wrote: > > On Tue, Nov 26, 2019 at 10:25:51PM +, Ximin Luo wrote: > > Please stop fiddling with severities. > The maintainer of a package decides the severities and whether things are > bugs or not. Neither have you provided a

Bug#945542: debcargo -- Randomly adds and removes binary packages

2019-11-29 Thread Bastian Blank
Hi Ximin On Tue, Nov 26, 2019 at 10:25:51PM +, Ximin Luo wrote: > Control: severity -1 normal Please stop fiddling with severities. > The more precise reason, as I have explained many times already, is because > the cargo package manager supports crates having optional dependencies. It is

Bug#945542: debcargo -- Randomly adds and removes binary packages

2019-11-29 Thread Bastian Blank
Hi Ximin On Tue, Nov 26, 2019 at 10:25:51PM +, Ximin Luo wrote: > Control: severity -1 normal Please stop fiddling with severities. > The more precise reason, as I have explained many times already, is because > the cargo package manager supports crates having optional dependencies. It is

Bug#945542: debcargo -- Randomly adds and removes binary packages

2019-11-29 Thread Bastian Blank
Control: severity -1 serious On Tue, Nov 26, 2019 at 10:25:51PM +, Ximin Luo wrote: > The more precise reason, as I have explained many times already, is because > the cargo package manager supports crates having optional dependencies. It is > not feasible to automatically merge

Bug#945542: debcargo -- Adds and removes binary packages

2019-11-26 Thread Bastian Blank
Hi Sylvestre On Tue, Nov 26, 2019 at 07:31:05PM +0100, Sylvestre Ledru wrote: > > I'm filling this as bug now. Please discuss this issue there. > First, this isn't random. This is generated from the features of the crate. > I am not sure to understand what is wrong with that? It isn't uncommon

Bug#945542: debcargo -- Adds and removes binary packages

2019-11-26 Thread Bastian Blank
Hi Sylvestre On Tue, Nov 26, 2019 at 07:31:05PM +0100, Sylvestre Ledru wrote: > > I'm filling this as bug now. Please discuss this issue there. > First, this isn't random. This is generated from the features of the crate. > I am not sure to understand what is wrong with that? It isn't uncommon

Bug#945542: debcargo -- Randomly adds and removes binary packages

2019-11-26 Thread Bastian Blank
Package: debcargo Severity: serious Hi Sylvestre I'm filling this as bug now. Please discuss this issue there. I'm setting it to serious as several ftp team members told you not to do that. On Thu, Oct 17, 2019 at 06:57:33PM +0200, Sylvestre Ledru wrote: > Le 17/10/2019 à 18:52, Ansgar a

Bug#945542: debcargo -- Randomly adds and removes binary packages

2019-11-26 Thread Bastian Blank
Package: debcargo Severity: serious Hi Sylvestre I'm filling this as bug now. Please discuss this issue there. I'm setting it to serious as several ftp team members told you not to do that. On Thu, Oct 17, 2019 at 06:57:33PM +0200, Sylvestre Ledru wrote: > Le 17/10/2019 à 18:52, Ansgar a

Bug#944920: Revise terminology used to specify requirements

2019-11-17 Thread Bastian Blank
On Sun, Nov 17, 2019 at 10:10:11AM -0800, Russ Allbery wrote: > +The Release Team may, at their discretion, downgrade a Policy requirement > +to a Policy recommendation for a given release of the Debian distribution. > +This may be done for only a specific package or for the archive as a > +whole.

Bug#944920: Revise terminology used to specify requirements

2019-11-17 Thread Bastian Blank
On Sun, Nov 17, 2019 at 10:10:11AM -0800, Russ Allbery wrote: > +The Release Team may, at their discretion, downgrade a Policy requirement > +to a Policy recommendation for a given release of the Debian distribution. > +This may be done for only a specific package or for the archive as a > +whole.

Re: Draft text on Init Systems GR

2019-11-17 Thread Bastian Blank
Hi Brian On Fri, Nov 15, 2019 at 01:10:58AM -0500, Brian Gupta wrote: > Do you think it's ok in any case to remove init scripts. Let's say an > upstream stops maintaining init scripts, I would like to know if this is a real world problem. Please provide an example of a package where the init

Bug#944839: linux-image-5.2.0-0.bpo.3-rt-amd64-unsigned: issues for application crash with this kernel

2019-11-16 Thread Bastian Blank
On Fri, Nov 15, 2019 at 11:23:09PM -0500, westlake wrote: > When this kernel is used, the latest version of chrome crashes saying it > can't launch because it is not able to create its own sandbox. > (chrome "Version 78.0.3904.97 (Official Build) (64-bit)") Please try: | sysctl -w

Bug#944839: linux-image-5.2.0-0.bpo.3-rt-amd64-unsigned: issues for application crash with this kernel

2019-11-16 Thread Bastian Blank
On Fri, Nov 15, 2019 at 11:23:09PM -0500, westlake wrote: > When this kernel is used, the latest version of chrome crashes saying it > can't launch because it is not able to create its own sandbox. > (chrome "Version 78.0.3904.97 (Official Build) (64-bit)") Please try: | sysctl -w

Re: Disabling TLS 1.0/1.1, is it advisable?

2019-11-06 Thread Bastian Blank
On Wed, Nov 06, 2019 at 08:54:17AM -0600, Bryan K. Walton wrote: > Apple, Google, Microsoft, and Mozilla have all announced that they will > be deprecating TLS 1.0 and 1.1 in March 2020, in their web browsers. Mail is not a web browser. > Similarly, SSL Labs has announced that they will be

Bug#944039: ITP: docker-systemctl-replacement -- daemonless "systemctl" command to manage services without SystemD

2019-11-03 Thread Bastian Blank
Hi Dmitry On Sun, Nov 03, 2019 at 07:33:59PM +1100, Dmitry Smirnov wrote: >Package name: docker-systemctl-replacement "docker" only shows up in the name of the package. What is this about? Also "docker" is the trademark of the software called "moby". > Description: daemonless

Bug#944039: ITP: docker-systemctl-replacement -- daemonless "systemctl" command to manage services without SystemD

2019-11-03 Thread Bastian Blank
Hi Dmitry On Sun, Nov 03, 2019 at 07:33:59PM +1100, Dmitry Smirnov wrote: >Package name: docker-systemctl-replacement "docker" only shows up in the name of the package. What is this about? Also "docker" is the trademark of the software called "moby". > Description: daemonless

Re: Bug / feature request: Display debian.org in browser language

2019-10-31 Thread Bastian Blank
On Thu, Oct 31, 2019 at 06:53:39PM +0100, Carsten Schoenert wrote: > We typically use the BTS (Bug Tracker System) for dealing with issues. > https://www.debian.org/Bugs/ You could try to setup a custom issue tracker via:

Re: Postfix ignores smtpd_tls_security_level = encrypt ?

2019-10-31 Thread Bastian Blank
On Thu, Oct 31, 2019 at 03:58:03PM +0100, Ferdinand Goldmann wrote: > I need a Postfix (3.3) installation to only accept mails sent after STARTTLS, > so I've set smtpd_tls_security_level = encrypt in main.cf. However, Postfix > still allows sending mails withouth encryption. accept != send.

Re: TZ=UTC wrong?

2019-10-30 Thread Bastian Blank
Hi Holger On Wed, Oct 30, 2019 at 12:42:54PM +, Holger Levsen wrote: > On Tue, Oct 29, 2019 at 09:00:15PM +0200, Niko Tyni wrote: > > On Mon, Oct 28, 2019 at 12:28:32PM +0100, Guillem Jover wrote: > > > Just noticed this change from the changelog. :) UTC is not really a > > > proper timezone

Re: [RFC] Proposal for new source format

2019-10-29 Thread Bastian Blank
Hi Russ On Tue, Oct 29, 2019 at 12:19:03PM -0700, Russ Allbery wrote: > Could you help me understand what this would look like? Is it something > like this workflow? > > 1. tag2upload determines the local Git tree that should be uploaded as a >new source package. > > 2. tag2upload locally

Re: [RFC] Proposal for new source format

2019-10-29 Thread Bastian Blank
On Tue, Oct 22, 2019 at 07:33:47AM -0400, Sam Hartman wrote: > My initial reaction is that this is additional complexity in a direction > that we don't need. It is not a question of complexity. It is a question of trust and who we want and need to trust. If we abolish the principle that we want

Re: [RFC] Proposal for new source format

2019-10-29 Thread Bastian Blank
On Tue, Oct 22, 2019 at 07:33:47AM -0400, Sam Hartman wrote: > My initial reaction is that this is additional complexity in a direction > that we don't need. It is not a question of complexity. It is a question of trust and who we want and need to trust. If we abolish the principle that we want

Re: Building Debian source packages reproducibly (was: Re: [RFC] Proposal for new source format)

2019-10-29 Thread Bastian Blank
Hi Didier On Mon, Oct 28, 2019 at 10:05:11AM +0100, Didier 'OdyX' Raboud wrote: > Of course, all of this can only work if we can have, or make the ".git to > .dsc" conversion reproducible; hence my query. Now, please read the first mail of this thread again. Yes, maybe parts of it are unclear,

Bug#943536: lintian: Stop shipping profile 'debian/ftp-master-auto-reject'

2019-10-25 Thread Bastian Blank
On Fri, Oct 25, 2019 at 02:37:33PM -0700, Felix Lechner wrote: > Based on information from #debian-ftp, which is recorded in part below, the > profile is no longer being used. It will be removed in the near future. How will this command line option work afterwards? | -F, --ftp-master-rejects |

Bug#943536: lintian: Stop shipping profile 'debian/ftp-master-auto-reject'

2019-10-25 Thread Bastian Blank
On Fri, Oct 25, 2019 at 02:37:33PM -0700, Felix Lechner wrote: > Based on information from #debian-ftp, which is recorded in part below, the > profile is no longer being used. It will be removed in the near future. How will this command line option work afterwards? | -F, --ftp-master-rejects |

Re: reject_unknown_sender_domain seems not to work

2019-10-25 Thread Bastian Blank
On Fri, Oct 25, 2019 at 11:37:04AM +0200, Lars Liedtke wrote: > Right and not :-( Sadly, our crystal ball is in revision. So please do as you are told and read http://www.postfix.org/DEBUG_README.html#mail. Bastian -- The heart is not a logical organ. -- Dr. Janet Wallace,

Re: Bug#942893: ftp.debian.org: please drop MD5sum lines from Packages

2019-10-24 Thread Bastian Blank
Hi Ansgar On Tue, Oct 22, 2019 at 11:51:56PM +0200, Ansgar wrote: > We could look into either > - writing MD5sum in a separate file only used by debian-cd (if present, >otherwise debian-cd should fall back to using Packages), or We still do that, see /indices/md5sum.gz. Bastian --

Bug#942893: ftp.debian.org: please drop MD5sum lines from Packages

2019-10-24 Thread Bastian Blank
Hi Ansgar On Tue, Oct 22, 2019 at 11:51:56PM +0200, Ansgar wrote: > We could look into either > - writing MD5sum in a separate file only used by debian-cd (if present, >otherwise debian-cd should fall back to using Packages), or We still do that, see /indices/md5sum.gz. Bastian --

Re: [RFC] Proposal for new source format

2019-10-23 Thread Bastian Blank
Hi Ansgar Thanks for filling in the gaps I left in my explanation. On Wed, Oct 23, 2019 at 10:15:16AM +0200, Ansgar wrote: > kernel.org uses a similar scheme: there are signatures for the > uncompressed tarballs by the maintainer (linux-*.tar.sign). In addition > there is a sha256sums.asc which

Re: [RFC] Proposal for new source format

2019-10-22 Thread Bastian Blank
Hi Russ On Mon, Oct 21, 2019 at 09:29:05PM -0700, Russ Allbery wrote: > If we're going to go to the trouble of defining a new source format, I'd > prefer we embrace a VCS-based one rather than once again rolling our own > idiosyncratic representation of a tree of files I'm not completely sure

Re: Working go-1.13 on ppc64 G5?

2019-10-21 Thread Bastian Blank
On Mon, Oct 21, 2019 at 08:09:35PM -0700, Christian Calderon wrote: > I've installed go-1.13 on my G5 (Quad 2.5) but I get an Illegal Instruction > error. Is there any hope of getting this to run on my architecture or do I > need to try to make things work with gnu-go? My ultimate goal is to get >

[RFC] Proposal for new source format

2019-10-21 Thread Bastian Blank
Hi Debian in form of dpkg have a rather strict view on how our source packages should look like. - Files need to be compressed and are recorded as such, which is a hard problem and give rise to tools like pristine-tar and such. - Different formats require different version formats. The native

[RFC] Proposal for new source format

2019-10-21 Thread Bastian Blank
Hi Debian in form of dpkg have a rather strict view on how our source packages should look like. - Files need to be compressed and are recorded as such, which is a hard problem and give rise to tools like pristine-tar and such. - Different formats require different version formats. The native

Merge request friendly handling of debian/changelog

2019-10-21 Thread Bastian Blank
Moin In Debian most people prefer to have changelog entries with all changes, so changes always contain a modification to debian/changelog. If we also start to use merge requests on Salsa, all those changes will contain modifications to debian/changelog, which will usualy conflict with each

Merge request friendly handling of debian/changelog

2019-10-21 Thread Bastian Blank
Moin In Debian most people prefer to have changelog entries with all changes, so changes always contain a modification to debian/changelog. If we also start to use merge requests on Salsa, all those changes will contain modifications to debian/changelog, which will usualy conflict with each

Re: FTBFS on i386 for user mode linux

2019-10-21 Thread Bastian Blank
On Mon, Oct 21, 2019 at 11:28:33AM +0530, Ritesh Raj Sarraf wrote: > I recently refreshed User Mode Linux to version 5.2 in Debian Unstable. > The package built fine for amd64 but for i386, I have run into the > following build failure. What did you find about it yourself? > ld -r -dp -o

Bug#942576: RM: icinga2 [armel mips64el mipsel s390x] -- ROM; Unblock testing migration

2019-10-18 Thread Bastian Blank
Control: reassign -1 src:icinga2 Control: retitle -1 icinga2 - FTBFS on release architectures Control: severity -1 serious Hi Bas On Fri, Oct 18, 2019 at 02:22:17PM +0200, Sebastiaan Couwenberg wrote: > On 10/18/19 2:11 PM, Bastian Blank wrote: > > On Fri, Oct 18, 2019 at 01:53:22PM +

Bug#942576: RM: icinga2 [armel mips64el mipsel s390x] -- ROM; Unblock testing migration

2019-10-18 Thread Bastian Blank
Control: reassign -1 src:icinga2 Control: retitle -1 icinga2 - FTBFS on release architectures Control: severity -1 serious Hi Bas On Fri, Oct 18, 2019 at 01:53:22PM +0200, Bas Couwenberg wrote: > Please remove icinga2 from armel, mips64el, mipsel & s390x to unblock testing > migration due to

Bug#942456: python-flask-marshmallow - Incomplete debian/copyright

2019-10-16 Thread Bastian Blank
Source: python-flask-marshmallow Version: 0.10.1-1 Severity: serious Justication: Policy §12.5 X-Debbugs-CC: ftpmas...@debian.org, guptautkarsh2...@gmail.com, python-modules-t...@lists.alioth.debian.org I just accepted python-flask-marshmallow from NEW. docs/_themes/flask/static/flasky.css_t

<    8   9   10   11   12   13   14   15   16   17   >