Processed: Re: Bug#991419: new upstream (0.7.1)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 991419 -1
Bug #991419 [ck] new upstream (0.7.1)
Bug 991419 cloned as bug 991427
> retitle -1 ITA: ck -- Concurrency Kit
Bug #991427 [ck] new upstream (0.7.1)
Changed Bug title to 'ITA: ck -- Concurrency Kit' from 'new upstream (0.7.1)'.
> reassign -1 wnpp
Bug #991427 [ck] ITA: ck -- Concurrency Kit
Bug reassigned from package 'ck' to 'wnpp'.
Ignoring request to alter found versions of bug #991427 to the same values 
previously set
Ignoring request to alter fixed versions of bug #991427 to the same values 
previously set
> owner -1 Daniel Baumann 
Bug #991427 [wnpp] ITA: ck -- Concurrency Kit
Owner recorded as Daniel Baumann .
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
991419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991419
991427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#988116: ITP: libdecor-0.1 -- client-side decoration library for Wayland

[Simon McVittie]

On Thu, 06 May 2021 at 00:11:37 +0100, Christian Rauch wrote:
> I am already maintaining an Ubuntu ppa at:
> https://launchpad.net/~christianrauch/+archive/ubuntu/libdecoration
> but would like to upstream the package into Debian.

Is the packaging you used in that Ubuntu PPA already available as a
git tree?

> Since this is my first time packaging a library for Debian, I could use
> support from a co-maintainer who is familiar with Wayland

More important would be to have a co-maintainer who is familiar with
packaging shared libraries, I think. There are some subtleties that are
important to get right.

It would probably make sense for the SDL team and/or the GNOME team to
be in Maintainer and/or Uploaders for this package - SDL wants to use it,
and it comes from GNOME infrastructure and uses GNOME-adjacent libraries
and coding conventions. I'm in both teams and would be willing to
co-maintain. I can help to implement the suggestions below, or you
could do them, whichever you'd prefer.

I haven't yet reviewed the upstream code at all (except for the build
system MR), but a Debian Developer will need to do that before upload,
to check for legality/licensing issues and make sure the code isn't
malicious or obviously broken (I'm sure it isn't, but someone should check).

Some quick review of the version from the PPA:

Package naming:
- Source package name should be libdecor-0 now that upstream has
  co-installable naming conventions
- libdecor binary package should be renamed libdecor-0-0 to match the
  SONAME libdecor-0.so.0, with Conflicts: libdecor, Replaces: libdecor
  to avoid conflicts with the unofficial PPA package
- libdecor-dev binary package should be renamed libdecor-0-dev to match
  the .pc file, with Conflicts: libdecor-dev, Replaces: libdecor-dev
- libdecor-plugin-cairo should maybe be renamed libdecor-plugin-1-cairo
  or something, to reflect plugin_api_version

d/control:
- libdecor dependency on libwayland-client0 should be unnecessary, you
  should find that ${shlibs:Depends} adds a suitable dependency
- Similarly libdecor-plugin-cairo dependency on libcairo2 and
  libpangocairo-1.0-0 should come from ${shlibs:Depends}
- libdecor-plugin-cairo should probably have Provides: libdecor-plugin-1
- libdecor-0-0 should probably have
  Recommends: libdecor-plugin-1-cairo | libdecor-plugin-1
  so that third-party plugins (if any) can Provides: libdecor-plugin-1
- The Standards-Version is very out of date, please check that the package
  follows current Debian Policy and then set it to the current Policy
  version (4.5.1 at time of writing)
- libdecor-plugin-cairo needs a long Description

d/compat:
- Please use the recommended debhelper compat level (13) for new packages,
  unless there is a very good reason to require an older compat level.
  The preferred way to do this is to add
  Build-Depends: debhelper-compat (= 13) and delete d/compat.

d/copyright:
- The version of the MIT/X11 license quoted here is called "Expat" in
  d/copyright files, to distinguish it from the many other licenses
  used by MIT and X11.
- You can probably use

  Files: *
  Copyright: (the same as you have now)
  License: Expat

  on the assumption that .gitignore, README, meson.build, etc. have the
  same copyright holders and licensing as the rest of the package.
- Please declare a copyright holder (you or your employer) and a license
  (probably Expat) for the debian directory.
- The copyright file isn't following copyright-format 1.0 syntax yet.
  Please see the python3-vdf package (which I maintain) for an example of
  a copyright file for a package with the same license as this one.

d/README.Debian:
- If you don't have anything to say here, please delete it

d/rules:
- Probably best to remove the commented-out stuff
- I would suggest enabling the demos and installing them in a new
  libdecor-tests package - otherwise it'll be hard to do manual testing
  on this package without having the patched SDL available. This will
  need some extra build-dependencies.

  If this package later gains automated tests, the libdecor-tests package
  could contain those too.

  Ideally the libdecor-tests package would have Build-Profiles: 
  (I can help with this).

d/source/format:
- Should be 3.0 (quilt) instead of 3.0 (native) for a package with an
  upstream developer outside Debian

d/git-build-recipe.manifest:
- This should be removed for an official Debian package.

Other:
- There should be a debian/watch to download the latest official upstream
  release. If upstream doesn't release tarballs then use something similar
  to 
https://salsa.debian.org/gnome-team/gnome-desktop-testing/-/blob/debian/2018.1+git20210629-1/debian/watch
  to download it directly from git.
- I think all shared library packages should have at least a superficial
  autopkgtest, for example similar to the ones in
  

  or 

Bug#991427: marked as done (ITA: ck -- Concurrency Kit)

[Debian Bug Tracking System]

Your message dated Fri, 23 Jul 2021 12:03:32 +
with message-id 
and subject line Bug#991427: fixed in ck 0.6.0-2
has caused the Debian Bug report #991427,
regarding ITA: ck -- Concurrency Kit
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
991427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ck

Hi Robert

Thank you for maintaining "ck" in Debian.

One of my packages (dnsperf) requires ck which unfortunately is
currently not build on armel. I've locally built and verified the
current "ck" upstream version (0.7.1) on amd64/i386 and all arm*
architectures.

I saw that your last upload of it was in 2017 and collected some dust
since. Are you still interested in maintaining "ck"? Do you like some help?

Given it's a build-dependency of dnsperf (and a few other packages of
mine), I'd be happy to take the package over in case you're not
interested anymore.

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: ck
Source-Version: 0.6.0-2
Done: Daniel Baumann 

We believe that the bug you reported is fixed in the latest version of
ck, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 991...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated ck 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 23 Jul 2021 13:25:19 +0200
Source: ck
Architecture: source
Version: 0.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 991427
Changes:
 ck (0.6.0-2) unstable; urgency=medium
 .
   * Uploading to unstable.
   * New maintainer (Closes: #991427), thanks to Robert for his past work.
   * Updating vcs fields.
Checksums-Sha1:
 0c6713d98f95d8f7713519d83605920fcaa7ed5e 1968 ck_0.6.0-2.dsc
 e71ca7e968e60f10f332d852315cc6463c90d16f 5642 ck_0.6.0-2.debian.tar.gz
 a1a150bde4baf7d888b3af5c4d9715ac86a08695 6092 ck_0.6.0-2_amd64.buildinfo
Checksums-Sha256:
 5a52c737d917f33c93d934395e249e1eb1abf9606dbedcb1f8fc5eba1f580468 1968 
ck_0.6.0-2.dsc
 df2b81c322a1babb741dc52d9d9fde3453cf539cc19569099310aece50a28787 5642 
ck_0.6.0-2.debian.tar.gz
 97b4a10be2d4bf6b7ec944503e1bb6f27bc55a34a001e1c6497f5bef67993f00 6092 
ck_0.6.0-2_amd64.buildinfo
Files:
 0f0a7f6ded72a2e965106166ae8055f7 1968 libs optional ck_0.6.0-2.dsc
 7ff95826ec61afba26f3e0a5448d2646 5642 libs optional ck_0.6.0-2.debian.tar.gz
 aea5026f0bf33b5028f9adaf15bd5a1d 6092 libs optional ck_0.6.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmD6rTEACgkQVc8b+Yar
uceA7BAAijqvVfDQzZzHFx8uJ9vBNhx+MmMSWSOpJ1gBqcmDPySOInXpmDNpRmoi
lpDlpy0OE97Oo4tc8zu5qc6iXOXmAp2QE+VdnT0ClFM9Bo7qGB8HzyznCcwFUqJ/
BbGTYMpG2JPSOR9TU3tE5ymcXnSDsDc6HNV7MmLG16LLR2VjKkXz7++rmtx2NOLu
aNZM88FDRvqG7t2gYRPQIe4d+cAfZQWKreyAD4kdDr5BaW3lE6JII3dm5LEe6T2/
Ov2kMsgtDxTYaaNIVCKG9gHkx9c9y2sGyVH8VUO7Itl88ZMYB45/selxg8bI5PmK
oLGNhArYqPNCMNblvr3so372yrfPx5kKEHCON+o3A5+jwZORRKvienCOKq0pQC6s
7LDXVGdfZ+/d10yg+SvVBx+RT0hZx0PhBemove82rbuJCcZ2TQ/k6H7bVstBVmcI
DAzOYkR/6398gsXNnpjd5q1eXhaATToftp4q/dkHglqAgSniLXTubXSXMFtE6nvF
Bfdt55aSn6F4ijZMrRytIBFY72VD4+/l3MA5t3PRMlqVmnSK7phfUPlWfoyJnFli
B8J/Y1SCzm2d16tKjka+0cq9zSVm152wP01YDY7iUtlOOw9IrD6SemshJRcUqkQ3
kFW44AiZ5WtMkDQkk9NXw0/uZj72OlHH6kcE3zJp5g9ehHz7BgE=
=WP7J
-END PGP SIGNATURE End Message ---

Bug#991435: ITP: jasmin-lang -- Jasmin is a workbench for high-assurance and high-speed cryptography. Jasmin implementations aim at being efficient, safe, correct, and secure.

[Marcel Fourné]

Package: wnpp
Severity: wishlist
Owner: Marcel Fourné 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: jasmin-lang
  Version : 0.1
  Upstream Author : jasmin-users and developers mailing list 

* URL : https://github.com/jasmin-lang/jasmin/wiki
* License : CECILL-B
  Programming Lang: Coq, Ocaml
  Description : Jasmin is a workbench for high-assurance and high-speed 
cryptography. Jasmin implementations aim at being efficient, safe, correct, and 
secure.

The Jasmin programming language smoothly combines high-level and low-level 
constructs, so as to support “assembly in the head” programming. Programmers 
can control many low-level details that are performance-critical: instruction 
selection and scheduling, what registers to spill and when, etc. They can also 
rely on high-level abstractions (variables, functions, arrays, loops, etc.) to 
structure their code and make it more amenable to formal verification.

The package is relevant to implementors as well as researchers in cryptography. 
It can be used to compile, interpret and extract programs to EasyCrypt, which 
is then used for the cryptographic proofs.

I plan to maintain the packages myself, but I am also very open to team 
maintenance for example among the Debian Ocaml Group. Since I am not a Debian 
Developer, I need a sponsor.

Bug#991436: ITP: easycrypt -- EasyCrypt: Computer-Aided Cryptographic Proofs

[Marcel Fourné]

Package: wnpp
Severity: wishlist
Owner: Marcel Fourné 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: easycrypt
  Version : 1.0
  Upstream Author : Easycrypt-club mailing list 

* URL : https://www.easycrypt.info
* License : CECILL-C, parts under CECILL-B
  Programming Lang: Ocaml
  Description : EasyCrypt: Computer-Aided Cryptographic Proofs

EasyCrypt is a toolset for reasoning about relational properties of 
probabilistic computations with adversarial code. Its main application is the 
construction and verification of game-based cryptographic proofs.

The package is relevant to implementors as well as researchers in cryptography. 
It can be used to check proofs extracted from Jasmin programs, but is useful in 
itself as a framework for cryptographic protocol proofs.

I plan to maintain the packages myself, but I am also very open to team 
maintenance for example among the Debian Ocaml Group. Since I am not a Debian 
Developer, I need a sponsor.

Bug#988116: ITP: libdecor-0.1 -- client-side decoration library for Wayland

[Christian Rauch]

Am 23.07.21 um 11:35 schrieb Simon McVittie:
> Is the packaging you used in that Ubuntu PPA already available as a
> git tree?

Yes. The ppa is using my "libdecor-packaging" repo [1] for the packaging
information. The ppa is merging the source tree and the packaging tree
to generate the packages daily.

> I'm in both teams and would be willing to
> co-maintain. I can help to implement the suggestions below, or you
> could do them, whichever you'd prefer.

Thank you. I don't mind implementing your suggestions, while you take a
look at the code.

How should I update the package information according to your
suggestions? Shall I just update my packaging repo and you pull from it?
Or do you have to create a repo at salsa.debian.org and take pull
requests from me?

Best,
Christian

[1] https://gitlab.gnome.org/christian-rauch/libdecor-packaging

Información AGOSTO 2021

[FOESCO]

Buenos días



Contactamos con vuestra empresa para informamos que se encuentra abierto el 
plazo de inscripción de Cursos Bonificables para empleados (AGOSTO- SEPTIEMBRE 
2021).

Los cursos pueden iniciarse en los meses de AGOSTO (Por defecto) o SEPTIEMBRE.


Adjuntamos listado con más de 1000 Cursos Bonificables Online disponibles.

Recordamos que todos los cursos disponibles son 100% Bonificables con cargo al 
Crédito de Formación 2021.


Podéis confirmarnos que os ha llegado el listado correctamente?



Un cordial saludo.


Alex Pons
Director FOESCO


Departamento de Formación Bonificable.
FOESCO Formación Estatal Continua.
Entidad Organizadora: B200592AA
Tel: 910 323 794
(Horario de 9h a 15h y de 17h a 20h de Lunes a Viernes)

FOESCO ofrece formación a empresas y trabajadores en activo a través de cursos 
bonificados por la Fundación Estatal para la Formación en el Empleo (antiguo 
FORCEM) que gestiona las acciones formativas de FORMACIÓN CONTINUA para 
trabajadores y se rige por la ley 30/2015 de 9 de Septiembre.

Antes de imprimir este e-mail piense bien si es necesario hacerlo. FOESCO Tfno: 
910 382 880. La información transmitida en este mensaje está dirigida solamente 
a las personas o entidades que figuran en el encabezamiento y contiene 
información confidencial, por lo que, si usted lo recibiera por error, por 
favor destrúyalo sin copiarlo, usarlo ni distribuirlo, comunicándolo 
inmediatamente al emisor del mensaje. De conformidad con lo dispuesto en el 
Reglamento Europeo del 2016/679, del 27 de Abril de 2016, FOESCO le informa que 
los datos por usted suministrados serán tratados con las medidas de seguridad 
conformes a la normativa vigente que se requiere. Dichos datos serán empleados 
con fines de gestión. Para el ejercicio de sus derechos de transparencia, 
información, acceso, rectificación, supresión o derecho al olvido, limitación 
del tratamiento , portabilidad de datos y oposición de sus datos de carácter 
personal deberá dirigirse a la dirección del Responsable del tratamiento a C/ 
LAGUNA DEL MARQUESADO Nº10, 28021, MADRID, "PULSANDO AQUI" 
 y "ENVIAR".

Bug#988116: ITP: libdecor-0.1 -- client-side decoration library for Wayland

[Simon McVittie]

On Fri, 23 Jul 2021 at 19:00:02 +0100, Christian Rauch wrote:
> Am 23.07.21 um 11:35 schrieb Simon McVittie:
> > Is the packaging you used in that Ubuntu PPA already available as a
> > git tree?
> 
> Yes. The ppa is using my "libdecor-packaging" repo [1] for the packaging
> information. The ppa is merging the source tree and the packaging tree
> to generate the packages daily.

Thanks, I've pulled from there as a basis for an initial packaging repo:
https://salsa.debian.org/sdl-team/libdecor-0

I would strongly prefer the git repo to be "source included", like the
one for libsdl2 - that fits the policies of both the SDL and GNOME teams.

> How should I update the package information according to your
> suggestions? Shall I just update my packaging repo and you pull from it?
> Or do you have to create a repo at salsa.debian.org and take pull
> requests from me?

Some of the changes I suggested will make it incompatible with the
packages currently in your PPA (i.e. break upgrades), so it might be
best to have a "clean break" between the PPA and the official Debian
packaging, by forking https://salsa.debian.org/sdl-team/libdecor-0 on
salsa.debian.org and doing new packaging work there.

I can give you commit access to that packaging repo when we've got a bit
further, but you'll need an account on salsa.debian.org first, and it
might be best to do at least the first few changes as merge requests.

smcv

Bug#951374: RFP: gh -- the GitHub CLI

[Nicholas Guriev]

Hello!

I personally find that "gh" is quite short name for a package that will
go into a general purpose software catalog like Debian repository. Would
you mind choosing something like "github-cli" as source and binary
package name and mentioning the sortcut "gh" in a package description?
So anyone could find the program by means of `apt-cache search`.
Acronyms gh and gn (which stands for Google's Generate Ninja) are
visually similar, and I'm afraid they are easily confused.

What do you make of this proposal?



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