Bug#1029949: RFS: selint/1.3.0-2 -- Static code analysis of refpolicy style SELinux policies

2023-01-29 Thread Christian Göttsche
Package: sponsorship-requests
Severity: important
Justification: allows src:refpolicy migration

Dear mentors,

I am looking for a sponsor for my package "selint":

 * Package name : selint
   Version  : 1.3.0-2
   Upstream contact : Daniel Burgener 
 * URL  : https://github.com/SELinuxProject/selint
 * License  : Apache-2.0
 * Vcs  : https://salsa.debian.org/selinux-team/selint
   Section  : devel

The source builds the following binary packages:

  selint - Static code analysis of refpolicy style SELinux policies

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/selint/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/s/selint/selint_1.3.0-2.dsc

Changes since the last upload:

 selint (1.3.0-2) unstable; urgency=medium
 .
   * debian: run functional tests
   * debian: skip building tests with nocheck
   * d/tests/refpolicy-test: support zstd compressed source
   * d/clean: delete generated testsuite artifacts to build twice

Regards,
-- 
  Christian Göttsche



Bug#1029950: RFS: uriparser/0.9.7+dfsg-2 -- URI parsing library compliant with RFC 3986

2023-01-29 Thread Jörg Frings-Fürst
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "uriparser":

   Package name : uriparser
   Version  : 0.9.7+dfsg-2
   Upstream contact : Sebastian Pipping 
   URL  : http://uriparser.sourceforge.net
   License  : BSD-3-clause, LGPL-2.1+
   Vcs  : https://jff.email/cgit/uriparser.git
   Section  : libs

The source builds the following binary packages:

  liburiparser1 - URI parsing library compliant with RFC 3986
  liburiparser-dev - development files for uriparser
  liburiparser-doc - documentation files for uriparser

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/uriparser/

Alternatively, you can download the package with 'dget' using this
command:

 dget -x 
https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.9.7+dfsg-2.dsc

or from

 git https://jff.email/cgit/uriparser.git?h=release%2Fdebian%2F0.9.7%2Bdfsg-2



Changes since the last upload:

 uriparser (0.9.7+dfsg-2) unstable; urgency=medium
 .
   * debian/liburiparser-dev.install:
 - Add usr/lib/*/cmake/uriparser-* (Closes: +1029143).
   * Declare compliance with Debian Policy 4.6.2.0 (No changes needed).
   * debian/copyright:
 - Add year 2023 to myself.

CU
Jörg


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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


Bug#1025642: RFS: d11amp/0.61-1 [ITP] -- Simple MP3 player

2023-01-29 Thread James Addison
Package: sponsorship-requests
Followup-For: Bug #1025642

Hi Thomas,

Can you confirm that the content of the default theme files that are
generated/unpacked by the source code to d11amp are your own work, or
have a license that is compatible with distribution as part of a Debian
package?

(if possible it could be simpler to bundle them as individual files outside
of the source code, making it easier for developers and users alike to
determine their contents and/or customize them)

Thanks,
James



Re: gbp import-orig: how to choose compression (xz)

2023-01-29 Thread Lorenzo
On Sat, 28 Jan 2023 19:24:37 +0100
Andrey Rakhmatullin  wrote:

> On Fri, Jan 27, 2023 at 06:02:34PM +0100, Lorenzo wrote:
> > Hello mentors,
> > 
> > I want to import a new svn snapshot to update a Debian package,
> > the salsa git repo is already configured for gbp, so I did
> > 
> > $ gbp import-orig -u1.5+svn38408 ../upstreamsvn/mplayer
> > 
> > upstream/mplayer is a directory with the unpacked svn checkout.
> > Gbp creates a ../upstreamsvn/mplayer_1.5+svn38408.orig.tar.gz
> > archieve (not a tar.xz); it also uses tar.gz in the pristine-tar
> > branch.
> As far as I can see this is not configurable, all locally-repacked
> tarballs are repacked as .tar.gz.

Yes, by looking at gbp.conf(5) and manpages of other gbp-* I couldn't
find an option to control the compression type when importing a new
upstream snapshot.
As a workaround it seems that if I compress manually as tar.xz and then
feed the archive to gbp import-orig the xz format is kept. However I
prefer to let gbp handle all steps.

> 
> > One problem with the tar.gz is that debian/gbp.conf has
> > compression = xz
> So this configuration is wrong ad you need to change it.
I didn't write in my previous message, but the watch file of this
project looks for a tar.xz when downloading a new upstream release.
I'm going to try
compression = auto
in the hope that it works both for tar.xz releases and
tar.gz snapshots.

> 
> > so when I push to salsa the salsa-ci fails because it searches for a
> > tar.xz archieve
> (I'm still surprised that people apparently don't build locally, only
> on salsa-ci)
(I build locally with sbuild and use salsa-ci for piuparts and other
tests)

Lorenzo




Bug#1025642: RFS: d11amp/0.61-1 [ITP] -- Simple MP3 player

2023-01-29 Thread Thomas Dettbarn

Hello James.

Yes! I confirm. I confirm very much. :)
No, it is not of my design, it is Christian's. (Since he is not a 
subscriber to the

Debian mailing list, I took the liberty of putting him into CC.)

The theme is DEFINITELY, 100% CC-0 Licensed. It was my decision to do so,
so distributions like Debian would to be able to create and share 
screenshots

FREELY, which, as I learned from my other project dMagnetic, is sometimes
problematic.


"Bundling them as individual files outside the source code" was 
something I was
already thinking about. At the moment, making them part of the source 
code is
the easiest solution for me. In future versions I can make the .BMP 
files part of

the tarball and store them in the /usr/local/share folder, for example.

Anyways, interested designers can already extract them easily with

% d11amp --gui.theme.dumpdefault=tmp/

modify them with gimp (or whatever), and test them out with

% d11amp --gui.theme.dir=tmp/

The tool to make them part of the source code again is not very mature 
at this

point, but you can find it here:

https://github.com/dettus/d11amp/tree/main/mark4/tools


Does this answer your questions?


Thomas Dettbarn


On 1/29/23 15:24, James Addison wrote:

Package: sponsorship-requests
Followup-For: Bug #1025642

Hi Thomas,

Can you confirm that the content of the default theme files that are
generated/unpacked by the source code to d11amp are your own work, or
have a license that is compatible with distribution as part of a Debian
package?

(if possible it could be simpler to bundle them as individual files outside
of the source code, making it easier for developers and users alike to
determine their contents and/or customize them)

Thanks,
James





Bug#1025642: RFS: d11amp/0.61-1 [ITP] -- Simple MP3 player

2023-01-29 Thread Christian Ruesch

On 1/29/23 16:42, Thomas Dettbarn wrote:

Hello James.

Yes! I confirm. I confirm very much. :)
No, it is not of my design, it is Christian's. (Since he is not a 
subscriber to the

Debian mailing list, I took the liberty of putting him into CC.)

The theme is DEFINITELY, 100% CC-0 Licensed. It was my decision to do so,
so distributions like Debian would to be able to create and share 
screenshots

FREELY, which, as I learned from my other project dMagnetic, is sometimes
problematic.


"Bundling them as individual files outside the source code" was 
something I was
already thinking about. At the moment, making them part of the source 
code is
the easiest solution for me. In future versions I can make the .BMP 
files part of

the tarball and store them in the /usr/local/share folder, for example.

Anyways, interested designers can already extract them easily with

% d11amp --gui.theme.dumpdefault=tmp/

modify them with gimp (or whatever), and test them out with

% d11amp --gui.theme.dir=tmp/

The tool to make them part of the source code again is not very mature 
at this

point, but you can find it here:

https://github.com/dettus/d11amp/tree/main/mark4/tools


Does this answer your questions?


Thomas Dettbarn


On 1/29/23 15:24, James Addison wrote:

Package: sponsorship-requests
Followup-For: Bug #1025642

Hi Thomas,

Can you confirm that the content of the default theme files that are
generated/unpacked by the source code to d11amp are your own work, or
have a license that is compatible with distribution as part of a Debian
package?

(if possible it could be simpler to bundle them as individual files 
outside

of the source code, making it easier for developers and users alike to
determine their contents and/or customize them)

Thanks,
James



Hi James,

as creator of the d11amp default skin I confirm that the skin is 100% 
CC-0 licensed.  I made the skin for my buddy Thomas Dettbarn.  Every 
pixel of the skin is 100% made by me and was created with Gimp on Debian 
Sid.


All the best,
Christian



Bug#1025642: RFS: d11amp/0.61-1 [ITP] -- Simple MP3 player

2023-01-29 Thread James Addison
Package: sponsorship-requests
Followup-For: Bug #1025642

Thanks Thomas, Christian!

Great to hear that the contents are CC-0 :)  And yep, that completely answers
my question, thank you.

Thomas: something that should avoid anyone else having the same confusion as me
in future would be to add a debian/copyright stanza, containing only a single
entry for 'Files: src/gui/default_theme.c', that adds a copyright attribution
for both Christian and yourself -- with an explanatory 'Comment' field about
the contents of 'defaultThemePacked'.

I'm not an expert, and maybe nitpicking - so please double-check whether that
makes sense to you and read the Debian policy documents if necessary - but I
think it could be a small improvement.



libhx lintian error "no-code-sections"

2023-01-29 Thread Jörg Frings-Fürst
Hello,


I have a problem with the lintian error "no-code-sections" in the
package libhx.


No matter if I set the parameters


export DEB_CFLAGS_MAINT_APPEND = -flto=auto -ffat-lto-objects


or not the error message remains. 


Can someone look over this?

The readelf output see at [1][2].


Thanks in advance!

CU
Jörg
 

[1] https://paste.debian.net/1268873
[2] https://paste.debian.net/1268874


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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


Bug#1029967: RFS: streamlink/5.2.1-1 -- CLI for extracting video streams from various websites to a video player

2023-01-29 Thread Alexis Murzeau

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "streamlink" for a new
upstream version 5.2.1.

  * Package name: streamlink
Version : 5.2.1-1
Upstream Author : Streamlink Team
  * URL : https://streamlink.github.io/
  * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
Section : python

It builds those binary packages:

   python3-streamlink - Python module for extracting video streams from
various websites
   python3-streamlink-doc - CLI for extracting video streams from various
websites (documentation)
   streamlink - CLI for extracting video streams from various websites to
a video player

To access further information about this package, please visit the
following URL:
   https://mentors.debian.net/package/streamlink


Alternatively, one can download the package with dget using this command:

   dget -x 
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_5.2.1-1.dsc

Changes since the last upload to unstable:
streamlink (5.2.1-1) unstable; urgency=medium

   * New upstream version 5.2.1
   * d/copyright: update copyright years with 2023
   * d/examples: don't install examples, they were removed

  -- Alexis Murzeau   Sun, 29 Jan 2023 13:00:22 +0100


Regards,
--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F



























OpenPGP_signature
Description: OpenPGP digital signature


Re: gbp import-orig: how to choose compression (xz)

2023-01-29 Thread Andrey Rakhmatullin
On Sun, Jan 29, 2023 at 03:45:26PM +0100, Lorenzo wrote:
> > > One problem with the tar.gz is that debian/gbp.conf has
> > > compression = xz
> > So this configuration is wrong ad you need to change it.
> I didn't write in my previous message, but the watch file of this
> project looks for a tar.xz when downloading a new upstream release.
Are you mixing released tarballs and contents of some SVN repo in the same
package repo then? Or what is your workflow?




Bug#1025642: RFS: d11amp/0.61-1 [ITP] -- Simple MP3 player

2023-01-29 Thread Thomas Dettbarn


On 1/29/23 17:46, James Addison wrote:


Thomas: something that should avoid anyone else having the same confusion as me
in future would be to add a debian/copyright stanza, containing only a single
entry for 'Files: src/gui/default_theme.c', that adds a copyright attribution
for both Christian and yourself -- with an explanatory 'Comment' field about
the contents of 'defaultThemePacked'.

I'm not an expert, and maybe nitpicking - so please double-check whether that
makes sense to you and read the Debian policy documents if necessary - but I
think it could be a small improvement.


Nitpicking is good! :)
Thank you so much for your input.


Okay, so I prepared the copyright file and intend to apply it to my 
package.

Please find it attached to this email. Does it contain what you meant?

If not, could you provide me with a better example than what I just 
whipped up?



Thomas

Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: dmagnetic
Upstream-Contact: Thomas Dettbarn 
Source: https://www.dettus.net/dMagnetic/
#
# Please double check copyright with the licensecheck(1) command.

Files: *
Copyright: 2020 Thomas Dettbarn 
License:   BSD-2-Clause
 Redistribution and use in source and binary forms, with or without 
modification,
 are permitted provided that the following conditions are met:
 .
 1. Redistributions of source code must retain the above copyright notice, this
 list of conditions and the following disclaimer.
 .
 2. Redistributions in binary form must reproduce the above copyright notice,
 this list of conditions and the following disclaimer in the documentation
 and/or other materials provided with the distribution.
 .
 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
 DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
 FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
 CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
 OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Files: debian/*
Copyright: 2020 Thomas Dettbarn 
License:   GPL-2+
 This package is free software; you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by
 the Free Software Foundation; either version 2 of the License, or
 (at your option) any later version.
 .
 This package is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
 .
 You should have received a copy of the GNU General Public License
 along with this program. If not, see 
 .
 On Debian systems, the complete text of the GNU General
 Public License version 2 can be found in "/usr/share/common-licenses/GPL-2".

Files: src/gui/default_theme.c
Copyright: 2022 Christian Ruesch 
   2023 Thomas Dettbarn 
Comment: The file contains a lookup table, which, when unpacked, produces
 the default theme. The theme has been licensed explicitly as
 Creative Commons 0 (Version 1.0), so that taking and sharing
 screenshots is permitted. 
License: CC0
  Creative Commons Legal Code
  
  CC0 1.0 Universal
  
  CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
  LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
  ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
  INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
  REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
  PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
  THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
  HEREUNDER.
  
  Statement of Purpose
  
  The laws of most jurisdictions throughout the world automatically confer
  exclusive Copyright and Related Rights (defined below) upon the creator
  and subsequent owner(s) (each and all, an "owner") of an original work of
  authorship and/or a database (each, a "Work").
  
  Certain owners wish to permanently relinquish those rights to a Work for
  the purpose of contributing to a commons of creative, cultural and
  scientific works ("Commons") that the public can reliably and without fear
  of later claims of infringement build upon, modify, incorporate in other
  works, reuse and redistribute as freely as possible in any form whatsoever
  and for any purposes, including without limitation commercial purposes.
  These ow

Bug#1029981: RFS: kmscon/9.0.0-4 -- Simple terminal emulator based on Kernel Mode Setting

2023-01-29 Thread Victor Westerhuis
Package: sponsorship-requests
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear mentors,

I am looking for a sponsor for my package "kmscon":

 * Package name : kmscon
   Version  : 9.0.0-4
   Upstream contact : https://github.com/Aetf/kmscon/issues
 * URL  : https://github.com/Aetf/kmscon
 * License  : public-domain, LGPL-2.1+, Expat, Expat and HPND, GPL-2 
with Font exception
 * Vcs  : https://salsa.debian.org/viccie30/kmscon
   Section  : utils

The source builds the following binary packages:

  kmscon - Simple terminal emulator based on Kernel Mode Setting

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/kmscon/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/k/kmscon/kmscon_9.0.0-4.dsc

Changes since the last upload:

 kmscon (9.0.0-4) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster (oldstable).
 .
   [ Victor Westerhuis ]
   * Update standards version to 4.6.2, no changes needed.
   * Disable -Werror=array-bounds.

This update fixes an (erroneous) build failure from -Werror=array-bounds when
building with LTO enabled. It should build on Ubuntu again and migrate to lunar.
Right now the migration is blocked, see 
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#kmscon.

Groet, Regards,
- -- 
  Victor Westerhuis

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE6OxII3T+o0Ujs6ECQz2Rq5dHQPsFAmPWy90THHZpY3RvckB3
ZXN0ZXJodS5pcwAKCRBDPZGrl0dA+3eTD/wKMVhUQFtc8fCIfZknMObZzvCObkAq
nnG2VCz9tVKFw0AothZ/AcjRg/qLiRc20zlw4061jNgEqoYGj/477IBfMBJsdLP/
ihhV0I3ZT8+a+TKUbeJij8KBReeuvcNvmKE/rC/l7ZRvpz/DF5if7AC5Jr8vhIBm
dGybAk59hV+r226SmP3BQ/buQDFQ2zRgWzCHE+n/64UIV7YvQFd1drSC9wI5lOCF
Ru38PEwEcCqDfOnocdzUNmtB6gM9UrgJS6flM2l0/KJYwYv6KF4Md2uwCXjMe/88
P7rsKx/RR06LQ+PUa9xbYx75p8BuxEYsFOVXnZnvQdIuVeol7d+oCrMS9eyEaIe9
saY6PqnVBRFdjIkPqFbdaQWdzysX3qHdpH386fJnVJlA+bqL8AQO3pOK3eY6hl5r
2zNDROlABpJDe8btG1J1+GyP5edq5hO7ojR9Stm+uVECQgLeybV1jghW8+oz8C7u
ZL5TyqcsdzkS1TkS0esZVTQidiBzNmJR4eY0+6375fufIclQ/jnfHr3aPeB8j+T+
oPhj9xwjmkV7L5SNFM/z0aCXvav9kEc3Uo4nt496OqrGIY4GLguLrCUz+qWU32sS
NZ+rlpy9rX8vejM2LFTm0JLSqhZ9a0a9JrKvEz059VdiNg2cFOiY5Zs0kBGbn6m/
y09GIrvaw5czXg==
=tuZm
-END PGP SIGNATURE-



Bug#1025642: RFS: d11amp/0.61-1 [ITP] -- Simple MP3 player

2023-01-29 Thread Thomas Dettbarn

On 1/29/23 17:46, James Addison wrote:

Thomas: something that should avoid anyone else having the same confusion as me
in future would be to add a debian/copyright stanza, containing only a single
entry for 'Files: src/gui/default_theme.c', that adds a copyright attribution
for both Christian and yourself -- with an explanatory 'Comment' field about
the contents of 'defaultThemePacked'.

I'm not an expert, and maybe nitpicking - so please double-check whether that
makes sense to you and read the Debian policy documents if necessary - but I
think it could be a small improvement.

No, nitpicking is fine!
(ESPECIALLY from sponsors. ;) )

It helps me getting better.

Anyways, I changed the copyright file, as requested. May I bother you to 
have a look?



Thomas



Bug#1025642: RFS: d11amp/0.61-1 [ITP] -- Simple MP3 player

2023-01-29 Thread James Addison
Package: sponsorship-requests
Followup-For: Bug #1025642

You're welcome (although I'll mention: I'm not eligible to be a sponsor here,
and am only commenting as a peer reviewer).

I'm not sure about that copyright file, because it's stating that the license
for the entire src/gui/default_theme.c file is CC-0 - is that what you intend?

(my assumption was that your code in that file is intended to be BSD-2-clause,
but since there are encoded representations of other files included within
it, we should explain what the copyright terms that apply to those files are)



Bug#1029989: RFS: budgie-desktop/10.7-1 -- Desktop package for budgie-desktop

2023-01-29 Thread David Mohammed
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "budgie-desktop":

 * Package name : budgie-desktop
   Version  : 10.7-1
   Upstream contact : Budgie Developers 
 * URL  : https://github.com/buddiesofbudgie/budgie-desktop
 * License  : GPL-2+, CC0-1.0, LGPL-2.1+, GPL-2
 * Vcs  : https://github.com/ubuntubudgie/budgie-desktop/tree/debian
   Section  : x11

The source builds the following binary packages:

  budgie-core - Core package for Budgie-Desktop
  budgie-core-dev - Development package for budgie-desktop
  budgie-desktop - Desktop package for budgie-desktop
  budgie-desktop-doc - documentation files for the budgie-desktop
  gir1.2-budgie-1.0 - GNOME introspection library for budgie-desktop
  gir1.2-budgieraven-1.0 - GNOME introspection library for
budgie-desktop (raven)
  libbudgie-appindexer0 - Menu library for budgie-desktop
  libbudgie-raven-plugin0 - Raven Plugin library for budgie-desktop
  libbudgie-plugin0 - Plugin library for budgie-desktop
  libbudgie-private0 - Budgie Private library for budgie-desktop
  libbudgietheme0 - Theme library for budgie-desktop
  libraven0 - Raven library for budgie-desktop

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/budgie-desktop/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/b/budgie-desktop/budgie-desktop_10.7-1.dsc

Background:
I am the Debian Maintainer for this package and have been since its
inception in 2016.

Upstream has just released v10.7 today.  In preparation for this I
have kept Debian up-to-date with
git master builds to allow further testing by Debian end-users to
allow for a much wider testing scope thus assuring for a stable
release.  This was done primarily due to the upcoming freeze dates.

The last update to debian was 4 weeks ago.  This release primarily
captures the last 4 weeks of upstream work mainly focussed on
providing an API for developers to add capability together with some
GUI refinements & polish.  No new end-user functionality was added.

The API changes have resulted in two additional binary packages hence
my request for sponsorship - to review the final release package and
sponsor before uploading to ftp-masters.

Changes since the last upload:

 budgie-desktop (10.7-1) experimental; urgency=medium
 .
   * New upstream release
 upstream release announcement in install changelogs
   * Packaging Changes
 d/changelog-announcement incorporates upstream release notice
 d/rules install new BudgieRaven typelib in the girepository
 d/control add gir1.2-budgieraven-1.0 binary package
 d/control add libbudgie-raven-plugin0 binary package
 d/control clarify the description for libbudgie-plugin0
 d/control update budgie-core-dev dependencies for the new
 binaries
 d/watch and d/upstream change to signed for this upstream release
 d/libbudgie-private0.symbols update
 d/libraven0.symbols update
 d/libbudgie-raven-plugin.symbols create and populate
 d/copyright - update year to 2023, adjust specific copyright for files
  due to applet source restructure, remove copyright for polkitdialog
  since src files removed in upstream tarball
 d/copyright - replace CC-BY-SA copyright for the default.jpg file with
 CC0-1.0 since upstream has replaced the default.jpg image
 (See README for the revised license designation)
 Refresh Rework-keyboard-handling-to-layouts-ibus-handling.patch
 Refresh show-tray-icon.patch

Regards,
-- 
  David Mohammed