Bug#1021750: general: the nodelalloc mount option should be used by default for ext4 in /etc/fstab

[nick black]

i'm pretty sure that the corruption issues leading to the
nodelalloc option were considered largely remedied by the
"auto_da_alloc" capability introduced (and enabled by default)
in 2.6.30? how would nodelalloc equal the performance of
delalloc? nodelalloc was all about reliability for programs that
weren't conforming to certain POSIX semantics, as i recall.

Re: Firmware GR result - what happens next?

[Paul Wise]

On Thu, 2022-10-13 at 17:35 +0200, Julien Cristau wrote:

> I'd prefer if we could make things work vs making things fail,
> however loudly.

There seem to be a few ways to deal with this transition:

1. Document it in the release notes and let users handle it. This means
lots of users won't get security updates for firmware (which are mostly
only issued for x86 CPU microcode), since lots of folks won't read the
release notes. This also means lots of support requests when users
can't find the firmware package they wanted.

2. Add some code somewhere to automatically modify the apt sources,
somehow ensure that code is run by all Debian users and hope that other
automated processes (like ansible/puppet) don't overwrite those changes
and hope that users aren't storing apt sources config in packages,
which would mean conffile prompts after the modification happens.

3. Add some code to apt to download non-free-firmware when non-free is
available in the sources and the downloaded Release files. This would
solve the issue for Debian and all other derivatives too, if they
decide to add a new non-free-firmware component too. This might not
be accepted by apt developers as it is kind of a hack to special-case
Debian component semantics in apt, although maybe a component mapping
config option would be accepted. This might result in extra Debian
support requests when users notice the new component in `apt update`. 
This might not work for users of tools not based on apt, like cupt?
This wouldn't result in users without non-free getting any non-free
firmware though, which maybe we want since it is the new default?

4. Keep all non-free-firmware packages in non-free too. This would be
backwards compatible, but may expose bugs in dak, debian-cd, apt and
other tools, so IIRC this has been vetoed by the archive and CD teams.
This also wouldn't result in users without non-free getting any of the
non-free firmware, which maybe we want since it is the new default?

Personally I would choose 4 first, I expect any potential issues could
be easily fixed before the freeze. Next I would choose 3. Next I would
choose 1 because I think /etc belongs to the sysadmin not packages.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#1021750: general: the nodelalloc mount option should be used by default for ext4 in /etc/fstab

[Vincent Lefevre]

Package: general
Severity: normal

The /etc/fstab file is created using by default ext4 with just
the errors=remount-ro option. However, the Debian FAQ recommends
the nodelalloc mount option to avoid performance degradation and
preserve data safety:

https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_Why_is_dpkg_so_slow_when_using_new_filesystems_such_as_btrfs_or_ext4.3F

  For ext4, use instead the "nodelalloc" mount option, which should
  fix both the performance degradation and the data safety issues,
  and not for just dpkg, but for any application in the system.

So this option should be used by default for btrfs and ext4.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Work-needing packages report for Oct 14, 2022

[wnpp]

The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.

Total number of orphaned packages: 1261 (new: 2)
Total number of packages offered up for adoption: 172 (new: 0)
Total number of packages requested help for: 61 (new: 0)

Please refer to https://www.debian.org/devel/wnpp/ for more information.



The following packages have been orphaned:

   elm-mode (#1021459), orphaned 5 days ago
 Installations reported by Popcon: 14
 Bug Report URL: https://bugs.debian.org/1021459

   elpa-rust-mode (#1021460), orphaned 5 days ago
 Description: Major Emacs mode for editing Rust source code
 Installations reported by Popcon: 199
 Bug Report URL: https://bugs.debian.org/1021460

1259 older packages have been omitted from this listing, see
https://www.debian.org/devel/wnpp/orphaned for a complete list.



No new packages have been given up for adoption, but a total of 172 packages
are awaiting adoption.  See https://www.debian.org/devel/wnpp/rfa_bypackage
for a complete list.



For the following packages help is requested:

   apache2 (#910917), requested 1461 days ago
 Description: Apache HTTP Server
 Reverse Depends: apache2 apache2-ssl-dev apache2-suexec-custom
   apache2-suexec-pristine backuppc bfh-container-server
   courier-webadmin cvsweb debbugs-web doc-central (129 more omitted)
 Installations reported by Popcon: 96870
 Bug Report URL: https://bugs.debian.org/910917

   apparmor (#1006872), requested 220 days ago
 Description: user-space parser utility for AppArmor
 Reverse Depends: apparmor-notify apparmor-profiles
   apparmor-profiles-extra apparmor-utils content-hub-testability
   dbus-broker dbus-daemon dbus-tests debian-cloud-images-packages
   dovecot-core (18 more omitted)
 Installations reported by Popcon: 187530
 Bug Report URL: https://bugs.debian.org/1006872

   aufs (#963191), requested 845 days ago
 Description: driver for a union mount for Linux filesystems
 Reverse Depends: fsprotect
 Installations reported by Popcon: 7380
 Bug Report URL: https://bugs.debian.org/963191

   autopkgtest (#846328), requested 2143 days ago
 Description: automatic as-installed testing for Debian packages
 Reverse Depends: debci-worker sbuild-qemu
 Installations reported by Popcon: 1158
 Bug Report URL: https://bugs.debian.org/846328

   balsa (#642906), requested 4036 days ago
 Description: An e-mail client for GNOME
 Reverse Depends: balsa
 Installations reported by Popcon: 603
 Bug Report URL: https://bugs.debian.org/642906

   cargo (#860116), requested 2011 days ago
 Description: Rust package manager
 Reverse Depends: dh-cargo python3-setuptools-rust rust-all
 Installations reported by Popcon: 2780
 Bug Report URL: https://bugs.debian.org/860116

   chromium (#1016047), requested 79 days ago
 Description: web browser
 Reverse Depends: chromium chromium-driver chromium-l10n
   chromium-shell icingaweb2-module-pdfexport node-puppeteer
   qunit-selenium x2gothinclient-minidesktop
 Installations reported by Popcon: 25196
 Bug Report URL: https://bugs.debian.org/1016047

   courier (#978755), requested 651 days ago
 Description: Courier mail server
 Reverse Depends: courier-faxmail courier-filter-perl courier-imap
   courier-ldap courier-mlm courier-mta courier-pcp courier-pop
   courier-webadmin couriergrey (3 more omitted)
 Installations reported by Popcon: 814
 Bug Report URL: https://bugs.debian.org/978755

   cron (#984736), requested 585 days ago
 Description: new maintainer need
 Reverse Depends: apticron autolog backintime-common bcron
   btrfsmaintenance buildd checksecurity clamtk cricket cron (24 more
   omitted)
 Installations reported by Popcon: 206233
 Bug Report URL: https://bugs.debian.org/984736

   crun (#1016183), requested 77 days ago
 Description: lightweight OCI runtime for running containers
 Reverse Depends: podman
 Installations reported by Popcon: 1484
 Bug Report URL: https://bugs.debian.org/1016183

   cyrus-imapd (#921717), requested 1343 days ago
 Description: Cyrus mail system - IMAP support
 Reverse Depends: cyrus-admin cyrus-caldav cyrus-clients cyrus-dev
   cyrus-imapd cyrus-murder cyrus-nntpd cyrus-pop3d cyrus-replication
 Installations reported by Popcon: 389
 Bug Report URL: https://bugs.debian.org/921717

   debtags (#962579), requested 855 days ago
 Description: Debian Package Tags support tools
 Reverse Depends: packagesearch
 Installations reported by Popcon: 1371
 Bug Report URL: https://bugs.debian.org/9625

Bug#1021743: ITP: sugarjar -- A Git/GitHub helper

[Michel Alexandre Salim]

Package: wnpp
Severity: wishlist
Owner: Michel Alexandre Salim 
X-Debbugs-Cc: debian-devel@lists.debian.org, mic...@michel-slm.name

* Package name: sugarjar
  Version : 0.0.11
  Upstream Author : Phil Dibowitz 
* URL : https://github.com/jaymzh/sugarjar
* License : Apache
  Programming Lang: Ruby
  Description : A Git/GitHub helper

SugarJar is a git/github helper. It needs one of the GitHub CLI's: the current
default is hub, but there is experimental support for gh.

SugarJar is inspired by arcanist, and its replacement at Meta, JellyFish.
Many of the features they provide for the Phabricator workflow this aims
to bring to the GitHub workflow.

In particular there are a lot of helpers for using a squash-merge workflow
that is poorly handled by the standard toolsets.

If you miss Mondrian or Phabricator - this is the tool for you!

I plan to maintain it myself, though I'd explore joining the Debian Ruby
team or granting them upload rights. I'm a Debian Maintainer so I would
initially need a sponsor to do the initial FTP upload.

Bug#1021741: ITP: golang-github-slack-go-slack -- access the Slack API in Go (library)

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-github-slack-go-slack
  Version : 0.11.3-1
  Upstream Author : Norberto Lopes
* URL : https://github.com/slack-go/slack
* License : BSD-2-clause
  Programming Lang: Go
  Description : access the Slack API in Go (library)

 This is the original Slack library for Go created by Norberto Lopes,
 transferred to a GitHub organization. This library supports most if
 not all of the api.slack.com REST calls, as well as the Real-Time
 Messaging protocol over websocket, in a fully managed way.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021731: ITP: a-el -- functions for dealing with associative structures

[Lev Lamberov]

Package: wnpp
Owner: Lev Lamberov 
Severity: wishlist

* Package name: a-el
  Version : 1.0.0
  Upstream Author : Arne Brasseur 
* URL or Web page : https://github.com/plexus/a.el
* License : GPL-3+
  Programming Lang: Emacs Lisp
  Description : functions for dealing with associative structures

Library for dealing with associative data structures: alists, hash-maps,
and vectors (for vectors, the indices are treated as keys).

This library is largely inspired by Clojure, it has many of the
functions found in clojure.core, prefixed with `a-'. All functions treat
their arguments as immutable, so e.g. `a-assoc' will clone the
hash-table or alist it is given. Keep this in mind when writing
performance sensitive code.

This is a new dependency of pcre2el, needed to fix RC bug. The package
will be maintained under Debian Emacsen team umbrella.

Re: Firmware GR result - what happens next?

[Wouter Verhelst]

On Thu, Oct 13, 2022 at 04:13:57PM +0100, Steve McIntyre wrote:
> On Thu, Oct 13, 2022 at 05:08:57PM +0200, Julien Cristau wrote:
> >On Thu, Oct 06, 2022 at 05:13:22PM +0200, Tobias Frost wrote:
> >> Maybe and idea would to do something like isa-support does for e.g 
> >> sseX-support
> >> on CPUs that does not have that feature: It fails on installation with an 
> >> debconf message, IIRC.
> >> So that would allow something like "new package" | 
> >> "you-need-to-enable-nonfree-firmware-reminder-package"
> >> 
> >Failing on installation is a terrible user experience, let's not, pretty
> >please.
> 
> It's not great, no. Do you have a better suggestion for making sure
> people update sources.list?

We can display a debconf error (which debconf tries really really hard
to show to the user) and then succeed?

Alternatively, the package could install an apt hook that nags the user
every time they run "apt update" or equivalent, and that turns silent if
the updated firmware packages are installed (because of the difference
between "purge" and "remove").

-- 
 w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}

I will have a Tin-Actinium-Potassium mixture, thanks.

Re: bits from the release team: are you ready to skate yet?

[Paul Gevers]

Hi,

On 13-10-2022 17:32, Johannes Schauer Marin Rodrigues wrote:

hrm... maybe I misunderstand but I thought your initial mail talked about build
profiles (aka DEB_BUILD_PROFILES) and not build options (aka
DEB_BUILD_OPTIONS). The policy section you cite is about DEB_BUILD_OPTIONS and
not about DEB_BUILD_PROFILES.

As far as I know, build profiles are not documented in policy at all yet. The
bug for that is https://bugs.debian.org/757760

Am I missing something?


Ok, maybe I mixed things up a bit. In the end, what matters for the 
Release Team is that we (potentially; in the future) want to *use* 
 declared Build-Dependencies to figure out what we consider key 
packages. Building documentation is important, but if we can choose 
between not building documentation and not building at all, we prefer 
the former (exceptions exist, as always).


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Re: Firmware GR result - what happens next?

[Tobias Frost]

On Thu, Oct 13, 2022 at 05:08:57PM +0200, Julien Cristau wrote:
> On Thu, Oct 06, 2022 at 05:13:22PM +0200, Tobias Frost wrote:
> > Maybe and idea would to do something like isa-support does for e.g 
> > sseX-support
> > on CPUs that does not have that feature: It fails on installation with an 
> > debconf message, IIRC.
> > So that would allow something like "new package" | 
> > "you-need-to-enable-nonfree-firmware-reminder-package"
> > 
> Failing on installation is a terrible user experience, let's not, pretty
> please.

I'd prefer failing loudly to failing silently.
 
> Cheers,
> Julien

Re: Firmware GR result - what happens next?

[Julien Cristau]

On Thu, Oct 13, 2022 at 05:17:59PM +0200, Tobias Frost wrote:
> On Thu, Oct 13, 2022 at 05:08:57PM +0200, Julien Cristau wrote:
> > On Thu, Oct 06, 2022 at 05:13:22PM +0200, Tobias Frost wrote:
> > > Maybe and idea would to do something like isa-support does for e.g 
> > > sseX-support
> > > on CPUs that does not have that feature: It fails on installation with an 
> > > debconf message, IIRC.
> > > So that would allow something like "new package" | 
> > > "you-need-to-enable-nonfree-firmware-reminder-package"
> > > 
> > Failing on installation is a terrible user experience, let's not, pretty
> > please.
> 
> I'd prefer failing loudly to failing silently.
>  
I'd prefer if we could make things work vs making things fail, however loudly.

Cheers,
Julien

Re: bits from the release team: are you ready to skate yet?

[Johannes Schauer Marin Rodrigues]

Hi Paul,

Quoting Paul Gevers (2022-10-13 17:25:36)
> On 13-10-2022 14:20, Johannes Schauer Marin Rodrigues wrote:
> > Quoting Paul Gevers (2022-10-13 10:00:42)
> >> Please also consider supporting the nodoc build profile. We are aware
> >> that nodoc is regularly used in a non-reproducible way (as intended,
> >> but with this consequence), so checking for correctness of this
> >> profile may be a bit harder. Ideally, using the profile would just
> >> make documentation binaries virtually empty.
> > 
> > No. Ideally, using the nodoc profile would make documentation binaries not 
> > be
> > emitted at all. This then also makes checking for correctness a lot easier
> > because then all binary packages built with the nodoc profile will be
> > bit-by-bit identical if your source package builds reproducibly.
> 
> Policy [1] says something else:
> """
> This option does not change the set of binary packages generated by the 
> source package, but documentation-only binary packages may be nearly 
> empty when built with this option.
> """
> I suggest you try and get policy updated.
> 
> [1]
> https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options

hrm... maybe I misunderstand but I thought your initial mail talked about build
profiles (aka DEB_BUILD_PROFILES) and not build options (aka
DEB_BUILD_OPTIONS). The policy section you cite is about DEB_BUILD_OPTIONS and
not about DEB_BUILD_PROFILES.

As far as I know, build profiles are not documented in policy at all yet. The
bug for that is https://bugs.debian.org/757760

Am I missing something?

Thanks!

cheers, josch

signature.asc
Description: signature

Re: bits from the release team: are you ready to skate yet?

[Paul Gevers]

Hi josch,

On 13-10-2022 14:20, Johannes Schauer Marin Rodrigues wrote:

Quoting Paul Gevers (2022-10-13 10:00:42)

Please also consider supporting the nodoc build profile. We are aware
that nodoc is regularly used in a non-reproducible way (as intended,
but with this consequence), so checking for correctness of this
profile may be a bit harder. Ideally, using the profile would just
make documentation binaries virtually empty.


No. Ideally, using the nodoc profile would make documentation binaries not be
emitted at all. This then also makes checking for correctness a lot easier
because then all binary packages built with the nodoc profile will be
bit-by-bit identical if your source package builds reproducibly.


Policy [1] says something else:
"""
This option does not change the set of binary packages generated by the 
source package, but documentation-only binary packages may be nearly 
empty when built with this option.

"""
I suggest you try and get policy updated.

[1] 
https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Re: Firmware GR result - what happens next?

[Steve McIntyre]

On Thu, Oct 13, 2022 at 05:08:57PM +0200, Julien Cristau wrote:
>On Thu, Oct 06, 2022 at 05:13:22PM +0200, Tobias Frost wrote:
>> Maybe and idea would to do something like isa-support does for e.g 
>> sseX-support
>> on CPUs that does not have that feature: It fails on installation with an 
>> debconf message, IIRC.
>> So that would allow something like "new package" | 
>> "you-need-to-enable-nonfree-firmware-reminder-package"
>> 
>Failing on installation is a terrible user experience, let's not, pretty
>please.

It's not great, no. Do you have a better suggestion for making sure
people update sources.list?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
 ability to read or write anything that is longer than one hundred and sixty
 characters."  -- Ignatios Souvatzis

Re: Firmware GR result - what happens next?

[Julien Cristau]

On Thu, Oct 06, 2022 at 05:13:22PM +0200, Tobias Frost wrote:
> Maybe and idea would to do something like isa-support does for e.g 
> sseX-support
> on CPUs that does not have that feature: It fails on installation with an 
> debconf message, IIRC.
> So that would allow something like "new package" | 
> "you-need-to-enable-nonfree-firmware-reminder-package"
> 
Failing on installation is a terrible user experience, let's not, pretty
please.

Cheers,
Julien

More on nonfree firmware transitional packages (was: Firmware GR result - what happens next?)

[Santiago Ruano Rincón]

El 06/10/22 a las 17:13, Tobias Frost escribió:
> On Thu, Oct 06, 2022 at 05:03:20PM +0200, Julien Cristau wrote:
> > On Thu, Oct  6, 2022 at 15:45:25 +0100, Steve McIntyre wrote:
> > 
> > > On Wed, Oct 05, 2022 at 10:11:27PM +0200, Julien Cristau wrote:
> > > >On Sun, Oct 02, 2022 at 08:21:31PM +0100, Steve McIntyre wrote:
> > > >> On Sun, Oct 02, 2022 at 11:08:47AM -0400, Michael Stone wrote:
> > > >> >On Sun, Oct 02, 2022 at 03:53:00PM +0100, Steve McIntyre wrote:
> > > >> >> On Sun, Oct 02, 2022 at 04:43:47PM +0200, Michael Biebl wrote:
> > > >> >> > What's the plan for upgraded systems with an existing 
> > > >> >> > /etc/apt/sources.list.
> > > >> >> > Will the new n-f-f section added on upgrades automatically(if 
> > > >> >> > non-free was
> > > >> >> > enabled before)?
> > > >> >> 
> > > >> >> So this is the one bit that I don't think we currently have a good
> > > >> >> answer for. We've never had a specific script to run on upgrades 
> > > >> >> (like
> > > >> >> Ubuntu do), so this kind of potentially breaking change doesn't 
> > > >> >> really
> > > >> >> have an obvious place to be fixed.
> > > >> >
> > > >> >Is there a reason to not continue to make the packages available in 
> > > >> >non-free?
> > > >> >I don't see a reason to force any change on existing systems.
> > > >> 
> > > >> Two things:
> > > >> 
> > > >>  1. I'm worried what bugs we might expose by having packages be in two
> > > >> components at once.
> > > >>  2. I really don't like the idea of leaving two different
> > > >> configurations in the wild; it'll confuse people and is more
> > > >> likely to cause issues in the future IMHO.
> > > >> 
> > > >> Plus, as Shengjing Zhu points out: we already expect people to manage
> > > >> the sources.list anyway on upgrades.
> > > >> 
> > > >I think in the absence of a release upgrade script (which I very much
> > > >doubt will happen, and be tested, and we can rely will be used, for
> > > >bookworm), Michael's suggestion seems like a reasonable way forward.  I
> > > >imagine we'll need to patch dak to allow that, but it seems like it
> > > >should be tractable?
> > > 
> > > I'm also worried what effect this will have on other tools that have
> > > to grok the archive (mirror tools, debian-cd, etc.). I'm not going to
> > > try and veto having things in more than one component, but (ugh!) I
> > > really think it's ugly. Actually, I think I'd much prefer Santiago's
> > > idea:
> > > 
> > > > Couldn't we handle this via transitional firware* non-free packages,
> > > > that depend on bookworm non-free-firmware packages?
> > > 
> > > We'd need to add some transitional binary packages for the small
> > > number of n-f-f source packages. That way people would get errors from
> > > apt if they don't read our warnings and update. Maybe this is a way
> > > forward?
> > > 
> > I don't think that will work well, the packages will likely just be held
> > at the old version if the new ones are uninstallable because the new
> > component isn't enabled.

Good point!

> Maybe and idea would to do something like isa-support does for e.g 
> sseX-support
> on CPUs that does not have that feature: It fails on installation with an 
> debconf message, IIRC.
> So that would allow something like "new package" | 
> "you-need-to-enable-nonfree-firmware-reminder-package"

And this could solve the issue, indeed. Picking up my other mail in the
thread, the transitional packages could be summarised like this:

bullseye:
firmware-linux-nonfree (non-free)
bookworm:
firmware-linux-nonfree (non-free) - empty
Depends: firmware-linux-nonfree-bookworm* (non-free-firmware) |
 non-free-firmware-needed-warning-package
trixie:
firmware-linux-nonfree-bookworm (non-free-firmware) - empty
Depends: firmware-linux-nonfree (non-free-firmware)
trixie+1 (forky):
firmware-linux-nonfree (non-free-firmware)
and so on.

* find a better name/suffix

Would this make sense?

I could volunteer to test this and propose the needed new package,
unless someone else wants to do it.

Cheers,

 -- Santiago


signature.asc
Description: PGP signature

Bug#1021725: ITP: golang-github-alexliesenfeld-health -- simple and flexible health check library for Go

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-github-alexliesenfeld-health
  Version : 0.6.0-1
  Upstream Author : Alexander Liesenfeld
* URL : https://github.com/alexliesenfeld/health
* License : Expat
  Programming Lang: Go
  Description : simple and flexible health check library for Go

 This library provides an http.Handler that acts as a health endpoint. It
 can be used by cloud infrastructure or other services to determine the
 availability of an application.

 Rather than simply returning a response with HTTP status code 200, this
 library allows building health checks that test the availability of all
 required dependencies. The HTTP response contains the aggregated health
 result and details about the health status of each component.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021724: ITP: golang-github-crowdsecurity-machineid -- get the unique machine identifier of any host (library)

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-github-crowdsecurity-machineid
  Version : 1.0.3-1
  Upstream Author : crowdsec
* URL : https://github.com/crowdsecurity/machineid
* License : Expat
  Programming Lang: Go
  Description : get the unique machine identifier of any host (library)

 This package returns the OS native machine UUID/GUID, which the OS
 uses for internal needs. All machine IDs are usually generated during
 system installation and stay constant for all subsequent boots.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021723: ITP: golang-github-hashicorp-hcl-v2 -- Go implementation of HashiCorp Configuration Language (version 2)

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-github-hashicorp-hcl-v2
  Version : 2.14.1-1
  Upstream Author : HashiCorp
* URL : https://github.com/hashicorp/hcl
* License : MPL-2.0
  Programming Lang: Go
  Description : Go implementation of HashiCorp Configuration Language 
(version 2)

 HCL (HashiCorp Configuration Language) is a configuration language built by
 HashiCorp. The goal of HCL is to build a structured configuration language that
 is both human and machine friendly for use with command-line tools, but
 specifically targeted towards DevOps tools, servers, etc.

 HCL is also fully JSON compatible. That is, JSON can be used as completely
 valid input to a system expecting HCL. This helps makes systems interoperable
 with other systems.

 HCL is heavily inspired by libucl, nginx configuration, and others similar.

 This package contains the source.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html

There's an existing golang-github-hashicorp-hcl package, kind of stalled
at version 1.0.0, which is depended on by close to 100 packages. It
seems prudent to introduce a -v2 package for hashicorp/hcl/v2, leaving it
up to reverse dependencies to switch to the new version if and when they
so desire.


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021722: ITP: golang-github-r3labs-diff -- diffing library for Go structures

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-github-r3labs-diff
  Version : 3.0.0-1
  Upstream Author : R3 Labs
* URL : https://github.com/r3labs/diff
* License : MPL-2.0
  Programming Lang: Go
  Description : diffing library for Go structures

 Utilizing field tags and reflection, this library makes it possible
 to compare two structures of the same type and create a changelog of
 all modified values. The produced changelog can easily be serialized
 to JSON.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021721: ITP: golang-entgo-ent -- entity framework for Go

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-entgo-ent
  Version : 0.11.3-1
  Upstream Author : Ent Foundation
* URL : https://github.com/ent/ent
* License : Apache-2.0
  Programming Lang: Go
  Description : entity framework for Go

 The ent package is a simple, yet powerful entity framework for Go,
 that makes it easy to build and maintain applications with large
 data-models.

 Highlights include:
  - Schema As Code - model any database schema as Go objects.
  - Easily Traverse Any Graph - run queries, aggregations and traverse
any graph structure easily.
  - Statically Typed And Explicit API - 100% statically typed and
explicit API using code generation.
  - Multi Storage Driver - supports MySQL, PostgreSQL, SQLite and
Gremlin.
  - Extendable - simple to extend and customize using Go templates.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html

This package replaces the existing golang-github-facebook-ent, which can
be removed after crowdsec has been updated.


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021720: ITP: golang-github-c-robinson-iplib -- library for working with IP addresses and networks in Go

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-github-c-robinson-iplib
  Version : 1.0.3-1
  Upstream Author : Chad Robinson
* URL : https://github.com/c-robinson/iplib
* License : Expat
  Programming Lang: Go
  Description : library for working with IP addresses and networks in Go

 IPLib is built around and on top of the address primitives found in
 the net package, trying to make them more accessible and easier to
 manipulate, in the spirit of Python's ipaddress and Ruby's ipaddr
 libraries.

 It features:
  - tools performing common tasks against regular net.IP objects;
  - an iplib.Net interface that enhances net.IPNet.

 It also features two submodules:
  - iana: referencing IP netblocks against the Internet Assigned
Numbers Authority's Special IP Address Registry;
  - iid: generating and validating IPv6 Interface Identifiers,
including RFC4291 modified EUI64 and RFC7217 Semantically Opaque
addresses.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021719: ITP: golang-github-jszwec-csvutil -- fast and idiomatic mapping between CSV and Go values (library)

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-github-jszwec-csvutil
  Version : 1.7.1-1
  Upstream Author : Jacek Szwec
* URL : https://github.com/jszwec/csvutil
* License : Expat
  Programming Lang: Go
  Description : fast and idiomatic mapping between CSV and Go values 
(library)

 This package provides provides fast, idiomatic, and dependency-free
 mapping between CSV and Go values. It is not a CSV parser, it is based
 on the Reader and Writer interfaces which are implemented by e.g the
 standard Go csv package. It is possible to choose any other CSV writer
 or reader which may be more performant.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021717: ITP: golang-github-confluentinc-bincover -- easily measure code coverage of Golang binaries (library)

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-github-confluentinc-bincover
  Version : 0.2.0-1
  Upstream Author : Confluent Inc.
* URL : https://github.com/confluentinc/bincover
* License : Expat
  Programming Lang: Go
  Description : easily measure code coverage of Golang binaries (library)

 Bincover is a ready-to-use, generic solution to test Go binaries,
 which is robust enough to handle panics and OS exits. It provides a
 simple and flexible API that generates an “instrumented binary” that
 can measure its own coverage, runs it with user-specified command
 line arguments and environment variables, and merges coverage
 profiles generated from multiple test runs.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021718: ITP: golang-github-crowdsecurity-grokky -- pure Golang Grok-like library

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-github-crowdsecurity-grokky
  Version : 0.1.0-1
  Upstream Author : crowdsec
* URL : https://github.com/crowdsecurity/grokky
* License : WTFPL
  Programming Lang: Go
  Description : pure Golang Grok-like library

 grokky is a pure Golang Grok-like patterns library with a particular
 focus on parsing log files, and on performance (leveraging the RE2
 regular expression engine instead of Oniguruma).

 The library was designed for creating many patterns and using them
 many times, while not retaining the exact same behaviors and features
 as the original library. The main goals are simplicity, speed, and
 ease of use.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html

This package replaces the existing golang-github-logrusorgru-grokky,
which can be removed after crowdsec has been updated.


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021716: ITP: golang-ariga-atlas -- manage your database schemas with Atlas (library)

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-ariga-atlas
  Version : 0.7.2-1
  Upstream Author : Ariga
* URL : https://github.com/ariga/atlas
* License : Apache-2.0
  Programming Lang: Go
  Description : manage your database schemas with Atlas (library)

 Atlas is an open source tool that helps developers manage their
 database schemas by applying modern DevOps principles. Contrary to
 existing tools, Atlas intelligently plans schema migrations for
 you. Atlas users can use the Atlas DDL (data definition language) to
 describe their desired database schema and use the command-line tool
 to plan and apply the migrations to their systems.

 It supports the following databases: MySQL, MariaDB, PostgresSQL,
 SQLite, TiDB, CockroachDB.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1021715: ITP: golang-github-crowdsecurity-dlog -- Go library to parse the Docker Logs stream (library)

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois 

* Package name: golang-github-crowdsecurity-dlog
  Version : 0.0.2-1
  Upstream Author : crowdsec
* URL : https://github.com/crowdsecurity/dlog
* License : Apache-2.0
  Programming Lang: Go
  Description : Go library to parse the Docker Logs stream (library)

 This library parses the binary Docker Logs stream into plain text.
 Given the full response body to a /containers//logs request, it
 strips off the log headers and returns the actual plain text message.


This is a requirement to update crowdsec:
  https://lists.debian.org/debian-go/2022/10/msg00018.html


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Re: bits from the release team: are you ready to skate yet?

[Johannes Schauer Marin Rodrigues]

Quoting Paul Gevers (2022-10-13 10:00:42)
> Please also consider supporting the nodoc build profile. We are aware
> that nodoc is regularly used in a non-reproducible way (as intended,
> but with this consequence), so checking for correctness of this
> profile may be a bit harder. Ideally, using the profile would just
> make documentation binaries virtually empty.

No. Ideally, using the nodoc profile would make documentation binaries not be
emitted at all. This then also makes checking for correctness a lot easier
because then all binary packages built with the nodoc profile will be
bit-by-bit identical if your source package builds reproducibly.

This can be achieved by adding this to the binary package stanza in d/control:

Package: foo-doc
Architecture: all
Build-Profiles: 

Then, in d/rules you can surround code that creates the foo-doc package with a
conditional like this one:

ifneq (,$(filter foo-doc,$(shell dh_listpackages)))
# do stuff needed to build foo-doc
endif

Using dh_listpackages you also automatically catch other cases in which foo-doc
might not get built other than the nodoc build profile being active, for
example for an arch:any-only build.

Also, do not forget to add the build dependencies necessary to build foo-doc to
Build-Depends-Indep instead of keeping them in Build-Depends if your foo-doc
package is Architecture:all.

Thanks!

cheers, josch

signature.asc
Description: signature

Re: /boot partition too small

[Andreas Tille]

Hi,

Am Fri, Oct 07, 2022 at 07:13:12AM +0200 schrieb Enrico Zini:
> On Thu, Oct 06, 2022 at 06:16:56PM +0200, Michael Biebl wrote:
> 
> > Can you clarify? Is the new intramfs generated in /boot or generated outside
> > of /boot but copied to /boot under a different name so it can be replaced
> > atomically?
> > I assume this is done for robustness reasons. Maybe, if space is as tight as
> > in such situations, one could compromise here?
> 
> The situation went somewhat like this:
> 
> 1. I have 2 kernels installed, a new one arrives
> 2. Installation of the 3rd one fails as usual, /boot contains 2 and a
>half kernels
> 3. I remove the kernel I'm not using, /boot contains 1 and a half
>kernels
> 4. dpkg --configure -a keeps failing for lack of disk space
> 5. I manually remove the initrd file of the new, not fully installed
>kernel
> 6. apt install --reinstall of the new kernel succeeds (dpkg --configure
>-a didn't generate the missing initrd)
> 
> I haven't had a chance to investigate why with a failed configure phase
> an old initrd was left there, and why configure failed but a new
> configure didn't regenerate the initd, so it may be that I hit a corner
> case.

In case it helps: I have also a laptop featuring this problem which
I also solve the very same way as Enrico (but shame on me was always
to lazy to report).

Just to confirm that Enrico is not the only one - probably there is
quite a number of installations out there and some of the users will
be scared to go steps 3.-6.

Kind regards
Andreas.

-- 
http://fam-tille.de

Re: Russian locale on reprotest in Salsa CI?

[Andreas Tille]

Am Thu, Oct 13, 2022 at 10:53:55AM +0200 schrieb Santiago Ruano Rincón:
> > Well, scroll up a bit. It starts all fine in English, only the last make
> > appears to switch.
> > Build system doing something fun?
> 
> like varying the locale where the package is built. It is a reprotest
> thing.

Ahhh, so reprotest is changing to a random locale and compares the
result with C?

OK, this makes sense.

Thanks for the explanation

 Andreas.

-- 
http://fam-tille.de

Re: Russian locale on reprotest in Salsa CI?

[Santiago Ruano Rincón]

El 13/10/22 a las 10:48, Joerg Jaspert escribió:
> Am 2022-10-13 10:13, schrieb Andreas Tille:
> 
> > my Russian is a bit rusty but I can understand what I can read here:
> >https://salsa.debian.org/science-team/cimfomfa/-/jobs/3372898#L1249
> 
> > I'm just a bit astonished to see this locale set.  No idea what's wrong
> > here but I think this should be switched to English.
> 
> Well, scroll up a bit. It starts all fine in English, only the last make
> appears to switch.
> Build system doing something fun?

like varying the locale where the package is built. It is a reprotest
thing.


signature.asc
Description: PGP signature

Un amigo ha compartido un mensaje de la Comunidad de Soporte HP con usted.

[MyLuckShopMyLu]

Aprenda más acerca de nuestro Foro de usuarios de HP @ http://www.hp.com/foro



Foro de usuarios de HP
Participe en la conversación.



MyLuckShopMyLu (qvg993...@foxmail.com) participa del Comunidad de Soporte HP y 
encontró un tema que le gustaría compartir con usted:

https://h30467.www3.hp.com/t5/Impresi%C3%B3n-escaneo-fax-y-copia/Resetar-de-forma-manual-la-impresora-OfficeJet-6950/m-p/1238302#M123580

MyLuckShopMyLu dice:

专业邮件群发QQ:635107993，转化率高效果好，营销老手很喜欢。QQ:635107993。邮件群发是成本最低效果最好的营销方式之一。

专业邮件群发QQ:635107993，转化率高效果好，营销老手很喜欢。QQ:635107993。邮件群发是成本最低效果最好的营销方式之一。

专业邮件群发QQ:635107993，转化率高效果好，营销老手很喜欢。QQ:635107993。邮件群发是成本最低效果最好的营销方式之一。

专业邮件群发QQ:635107993，转化率高效果好，营销老手很喜欢。QQ:635107993。邮件群发是成本最低效果最好的营销方式之一。

专业邮件群发QQ:635107993，转化率高效果好，营销老手很喜欢。QQ:635107993。邮件群发是成本最低效果最好的营销方式之一。

专业邮件群发QQ:635107993，转化率高效果好，营销老手很喜欢。QQ:635107993。邮件群发是成本最低效果最好的营销方式之一。


















































































































































































Esperamos que nos visite pronto.

Equipo del Comunidad de Soporte HP


MyLuckShopMyLu a traves del Comunidad de Soporte HP ha enviado este mensaje a 
debian-devel@lists.debian.org.



The URLs below are provided for you to cut and paste into your browser for easy 
access.

Subscribe to board @ 
https://h30467.www3.hp.com/t5/t5/user/myprofilepage/tab/user-subscriptions%3Aemail-subscriptions
Actualice sus configuraciones @ 
https://h30467.www3.hp.com/t5/t5/user/myprofilepage/tab/user-subscriptions%3Aemail-subscriptions
Dejar de recibir notificaciones? @ 
https://h30467.www3.hp.com/t5/user/RemoveUserEmailPage/user-id/-1/mail-message-tracking/L96RPBE64ZYNPV



Copyright 2013 Hewlett-Packard Development Company, L.P.

Re: Russian locale on reprotest in Salsa CI?

[Joerg Jaspert]

Am 2022-10-13 10:13, schrieb Andreas Tille:


my Russian is a bit rusty but I can understand what I can read here:
   https://salsa.debian.org/science-team/cimfomfa/-/jobs/3372898#L1249



I'm just a bit astonished to see this locale set.  No idea what's wrong
here but I think this should be switched to English.


Well, scroll up a bit. It starts all fine in English, only the last make 
appears to switch.

Build system doing something fun?

Not a salsa thing.

--
bye Joerg

Russian locale on reprotest in Salsa CI?

[Andreas Tille]

Hi,

my Russian is a bit rusty but I can understand what I can read here:

   https://salsa.debian.org/science-team/cimfomfa/-/jobs/3372898#L1249

I'm just a bit astonished to see this locale set.  No idea what's wrong
here but I think this should be switched to English.

Kind regards
   Andreas.

-- 
http://fam-tille.de

Bug#1021695: ITP: librocprim2-dev -- parallel primatives for GPU-accelerated code

[Cordell Bloor]

Package: wnpp
Severity: wishlist
Owner: Cordell Bloor 
X-Debbugs-Cc: debian-devel@lists.debian.org, debian...@lists.debian.org

* Package name: librocprim2-dev
  Version : 5.3.0
  Upstream Author : Advanced Micro Devices, Inc.
* URL : https://github.com/ROCmSoftwarePlatform/rocPRIM
* License : Expat (MIT/X)
  Programming Lang: C, C++
  Description : parallel primatives for GPU-accelerated code

rocPRIM is a header-only library providing HIP parallel primitives for
developing performant GPU-accelerated code on the AMD ROCm platform.

This package is a dependency of several libraries for scientific
computing on AMD GPUs, including rocthrust, rocsparse, rocalution,
hipcub, pytorch and tensorflow. It fulfills a similar role in the
AMD ROCm platform as CUB does in NVIDIA's CUDA platform.

This package is part of AMD's ROCm stack and will be maintained
under the Debian AI team umbrella.

Benchmark BTRFS vs. REISER4 vs. F2FS with compression

[Yadd]

Hi all,

one friend published a comparison of FS with compression. I'm sharing 
here in case anyone is interested

https://lab.nethence.com/fsbench/2022-10.html

Cheers,
Yadd