Bug#1069942: RFS: imsprog/1.3.7-1 -- Linux chip programmer for CH341a devices

2024-05-18 Thread Fabio Fantoni

On Thu, 16 May 2024 12:47:44 +0200 Tobias Frost  wrote:
> >
> >   * Don't fixed: P: imsprog source:
> > package-uses-old-debhelper-compat-version 12 - I want to maintain
> > compatibility for |Jammy| and |Focal| releases.
>
> If you package for different distributions, let me recommend me to 
utilize
> dedicated branches for those, for example by following the DEP14 
proposal;

> this will allow to optimize for the different Debian derivates.
>
> For a Debian upload, please use a acutal compat level; >12 has a lots of
> benefits.

Hi, I think compat 12 is not too old and can be keeped for now to make 
possible to do unofficial build and individual build (any people also 
without experience) on multiple Debian versions and derivatives still 
supported easier and faster using debian/latest.


About creation of other packaging branches following DEP14 I think is 
good only for official build (for example possible official backports), 
but before I think is good update the package to 1.3.9-1 before consider 
doing official backports and don't backports of 1.3.2-1.




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1069920: libtimezonemap: fixed-up port to libsoup3

2024-04-27 Thread Fabio Fantoni

Il 27/04/2024 07:03, Steve Langasek ha scritto:

Package: libtimezonemap
Version: 0.4.6-6
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear maintainers,

Because webkit2gtk has now moved to libsoup3, and because we have
reverse-dependencies that require both libtimezonemap and webkit2gtk, I have
done the work in Ubuntu to fix up the port of libtimezonemap to libsoup3.

This has been confirmed to work in the timezone picker in oem-config as used
on our Ubuntu images for Raspberry Pi and has shipped in Ubuntu 24.04 LTS.

Please consider including this revised patch in Debian.

Thanks,


Hi, you already opened a bug for this time ago 
(https://bugs.debian.org/1068679) and was solved in 0.4.6-7 
(https://tracker.debian.org/news/1518035/accepted-libtimezonemap-046-7-source-into-unstable/)


This was only a mistake or is there something to fix something did I miss?



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1068679: port-to-libsoup3.patch looks bad

2024-04-09 Thread Fabio Fantoni

Il 09/04/2024 02:43, Steve Langasek ha scritto:

Package: libtimezonemap
Version: 0.4.6-6
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch

Hello,

This is a follow-up to bug #1037940 which is now archived.

With the move of webkit2gtk to libsoup3, this now becomes non-negotiable for
us in Ubuntu, as ubiquity requires both webkit and libtimezonemap.

I have taken a stab at fixing this patch up based on the feedback in the
other bug and have something that passes libtimezonemap's own build-time
tests, and ubiquity's tests, though it's hard to tell how much the latter
actually matters for verifying libtimezonemap correctness due to mocking.

Please consider this for inclusion in Debian as well.

Thanks,


Thanks for your work, I'll do a new upload including it as soon as I'll 
have time




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1064672: virt-manager: FTBFS: AssertionError: Command was: ./virt-xml test-for-virtxml --add-device --host-device 0x04b3:0x4485 --update --confirm --debug --connect __virtinst_test__test:///<

2024-04-05 Thread Fabio Fantoni
libvirt 10.1.0 uploaded some days after my patch introduced new issue, I 
gave a fast look to upstream git but I didn't found a possible fix and I 
don't have enough time to check better and try to fix




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1017729: cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon

2024-04-03 Thread Fabio Fantoni

Control: severity -1 serious

in the last cinnamon I switched cinnamon-l10n from recommended to 
dependency, but to block this transition to testing I have to 
temporarily set an RC bug, so I set this


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057386: ITP: imsprog -- linux chip programmer for CH341a devices

2024-03-27 Thread Fabio Fantoni
On Tue, 26 Mar 2024 19:48:13 +0100 Carsten Schoenert 
 wrote:

> Hello Mikhail,
>
> Am 26.03.24 um 08:37 schrieb Kosolapov Ivan:
> > Hello, Carsten!
> > I have built a new version of IMSProg (v1.3.3).
> > Can you please tell me how I can get this version to you? Do I have to
> > upload the new version on mentors.debian or do you get it from GitHub?
>
> I pulled the git tree from GitHub and build the package from that source.
>
> I can build an updated version from the same tree again.
> The current entries in debian/latest looking an bit odd and chaotic.
>
>
> Can you rebase the last tree commits into one and keep at lest the
> following lines in the changelog? (Once the package is within the
> archive of course such rebasing should not happen anymore. Have a look
> into existing changelog entries from other files for examples how to
> write the entries.)
>
> * New upstream release 1.3.3
> * Initial release (Closes: #1057386)
>
> The last entry is needed with every new upstream version that is getting
> uploaded for automatic closing the ITP bug report if the FTP master


Hi, about rebase of latest tree commits into one I also think can be 
good, about d/changelog entries instead I'm not sure what you mean.


I suggested it here: 
https://github.com/bigbigmdm/IMSProg/commit/21f8b17153bba0472c68f14d0382f3d3d50aa0a6#commitcomment-140195336


Because I saw all initial packages in NEW that have uploaded multiple 
versions have new entry like to be treated as if they were already 
uploaded into the repository, or are they wrong? (I supposed are correct 
as are all DDs to upload)


Anyway I'm not completely sure about this since all the packages I added 
I always made further uploads only after they were accepted by ftp-master




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1067733: iptables: regression in 1.8.9 with -n breaks portblock in resource-agents

2024-03-26 Thread Fabio Pedretti
> Version 1.8.10 fixed this bug (see "udp" and "tcp" in "prot") in
> https://git.netfilter.org/iptables/commit/?id=34f085b1607364f4eaded1140060dcaf965a2649

iptables 1.8.10 was released on 2023-10-10, but this commit was merged
in 2024-02-07, so it is not fixed in 1.8.10, but it will be in the
release after that.



Bug#1065131: electron: GPU process crash with AMDGPU, ac: Unknown GPU, using 0 for raster_config

2024-03-25 Thread Fabio Pedretti
Version: 24.0.3-1+b1

Great, they belong to the same source package and should be both upgraded.
Closing.

> With mesa-va-drivers:amd64 24.0.3-1+b1 and libgl1-mesa-dri:amd64
> 23.3.3-3, the result is the same.
>
> But with also updating libgl1-mesa-dri:amd64 to 24.0.3-1+b1, the issue
> is fixed.



Bug#1062963: patch is incomplete

2024-03-22 Thread Fabio Fantoni

Il 22/03/2024 03:31, Matthias Klose ha scritto:

Control: reopen -1
Control: tags -1 + ftbfs patch

some library names in the symbols file were omitted.
patch attached.
http://launchpadlibrarian.net/720580389/muffin_6.0.1-1build1_6.0.1-1ubuntu1.diff.gz 



thanks, I didn't notice that, I just noticed another bad breaks/replaces 
issue in libmuffin-dev


on nmu to unstable was fixed, I'll fix in experimental too



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1067207: mesa: switch statement too large, might need -mlong-jump-table-offsets

2024-03-20 Thread Fabio Pedretti
Maybe it's better to file an issue or send a MR upstream:
https://gitlab.freedesktop.org/mesa/mesa/-/issues
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests

It looks like m68k was considered in the past:
https://cgit.freedesktop.org/mesa/mesa/log/?qt=grep=m68k



Bug#1067199: RFS: bleachbit/4.6.0-3 [ITA] [RC] -- delete unnecessary files from the system

2024-03-19 Thread Fabio Fantoni

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name : bleachbit
   Version  : 4.6.0-3
   Upstream contact : Andrew Ziem 
 * URL  : https://www.bleachbit.org/
 * License  : CC0-1.0, GPL-3+
 * Vcs  : 
https://salsa.debian.org/python-team/packages/bleachbit

   Section  : admin

The source builds the following binary packages:

  bleachbit - delete unnecessary files from the system

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/bleachbit/bleachbit_4.6.0-3.dsc


Changes since the last upload:

 bleachbit (4.6.0-3) unstable; urgency=medium
 .
   * Return to Debian Python Team and add myself to uploaders (Closes: 
#1065808)

   * Remove libgtk-3-0 from depends (Closes: #1067171)

Regards,
--
  Fabio Fantoni



Bug#405859: GLUT_ALPHA does not work with DRI

2024-03-18 Thread Fabio Pedretti
Version: 8.0-1

mga driver was removed from mesa since 8.0 in 2012:
https://docs.mesa3d.org/relnotes/8.0.html



Bug#646929: libgl1-mesa-glx: message "failed to create drawable" when starting Firefox

2024-03-18 Thread Fabio Pedretti
Version: 8.0-1

It looks like this was addressed in mesa years ago with this commit:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=4833104718677caad0027d5e7539ca9bba389392



Bug#775235: use llvm's getCPUTargetFeatures() over getHostCPUName()

2024-03-18 Thread Fabio Pedretti
It looks like the src/gallium/auxiliary/gallivm/lp_bld_misc.cpp file
in mesa was heavily updated for managing newer llvm versions, even if
mesa is still using getHostCPUName and still not getCPUTargetFeatures.

Michael, do you think there is still something to do in mesa?

Steve and Bernhard, are you still able to reproduce the original issue?



Bug#901533: mesa: please build intel_sanitize_gpu tool

2024-03-17 Thread Fabio Pedretti
There is a MR here, but needs to be updated:
https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/26



Bug#1018207: mesa: missing svga gallium driver for arm64

2024-03-17 Thread Fabio Pedretti
Version: 22.2.0-1

"svga" gallium driver was added in 22.2.0-1.



Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available

2024-03-17 Thread Fabio Pedretti
This was fixed in mutter 43.8 and 44.4 as per mutter report
https://gitlab.gnome.org/GNOME/mutter/-/issues/2602



Bug#1041647: radeonsi: no VAAPI support (regression)

2024-03-17 Thread Fabio Pedretti
Closing as per previous comment.



Bug#1065131: electron: GPU process crash with AMDGPU, ac: Unknown GPU, using 0 for raster_config

2024-03-17 Thread Fabio Pedretti
Can you try again with 24.0.3-1 ?
Thanks.

Il giorno ven 1 mar 2024 alle ore 00:12 Alexis Murzeau
 ha scritto:
>
> Package: mesa-va-drivers
> Version: 24.0.1-1
> Severity: important
>
> * What led up to the situation?
> Upgrading mesa-va-drivers to version 24.0.1-1 cause GPU process craches
> in electron based applications.



Bug#1017819: libgl1-mesa-dri: Memory leak in iris_dri.so causes Xorg to eat all memory and crash every few days

2024-03-17 Thread Fabio Pedretti
Current Debian stable (12, bookworm) has the fix.



Bug#1001836: libgl1-mesa-dri: Incorrect texture blitting/mapping seen on Intel (Mesa issue #4412)

2024-03-17 Thread Fabio Pedretti
Version: 21.0.3-1

Fixed since 21.0.3-1, as per upstream bug report.



Bug#1065654: mesa ftbfs with time_t64

2024-03-08 Thread Fabio Pedretti
Il Ven 8 Mar 2024, 11:21 Matthias Klose  ha scritto:

> On 08.03.24 11:00, Fabio Pedretti wrote:
> > Already fixed upstream, the patch will be included since 24.0.3 (will
> > be released in 5 days):
> >
> https://cgit.freedesktop.org/mesa/mesa/commit/?h=staging/24.0=8ea039019761ecc25d49f075aef50de6e81db854
>
> no, that commit is only fixing one occurrence.
>

The other file is not built in Debian, a fix will anyway also be included
in 24.0.3.

>


Bug#1065654: mesa ftbfs with time_t64

2024-03-08 Thread Fabio Pedretti
Already fixed upstream, the patch will be included since 24.0.3 (will
be released in 5 days):
https://cgit.freedesktop.org/mesa/mesa/commit/?h=staging/24.0=8ea039019761ecc25d49f075aef50de6e81db854


Il giorno ven 8 mar 2024 alle ore 10:27 Matthias Klose
 ha scritto:
>
> Package: src:mesa
> Version: 24.0.2-1
> Severity: serious
> Tags: sid trixie patch
>
> mesa ftbfs with time_t64, patch attached. I didn't check if the
> _TIMET_BITS are used in the affected files.
>
> There's also a bug in the profile support. WINE cannot be built without
> LLVM, and therefore should be disabled.



Bug#1065594: cinnamon: Blocks a huge number of packages for being updated

2024-03-07 Thread Fabio Fantoni

Il 07/03/2024 08:30, Michael Rasmussen ha scritto:

Package: cinnamon
Version: 5.8.4-4
Severity: important

Dear Maintainer,

Cinnamon have been left on the station while all other packages have
left with the train ;-)
Currently this is state on my installations:
apt upgrade
0 upgraded, 0 newly installed, 0 to remove and 565 not upgraded.
apt full-upgrade
509 upgraded, 285 newly installed, 702 to remove and 8 not upgraded.

So either build a new release of Cinnamon 5.8 or move the 6.0.4
which have been wainting for over a month in experimental from
experimental to unstable.

Thanks.


Hi, is not cinnamon blocking dist-upgrade but issues with big 64-bit 
time_t transition 
(https://lists.debian.org/debian-devel/2024/03/msg00092.html).


Upload 6.0 to unstable now (before t64 transition finished) risk to add 
other issues, for example someone have done in ubuntu and remained 
blocked in proposed 
(https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#cinnamon) 
but cinnamon-translation that have reverse recommends (and not depends) 
is already migrated but with breaks on reverse recommends (to avoid 
issues of partial upgrade) risk to be removed (and are also unable to 
install it in new installations).


There are also archs like armhf and armel where can't build 
(https://buildd.debian.org/status/package.php?p=cinnamon-desktop) for 
transition issue and will block also migration to testing (except 
cinnamon-translation), so upload 6.0 to unstable now will have the same 
issues of ubuntu.





OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

2024-02-26 Thread Fabio Pedretti
Ubuntu fixed it with this patch:
https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz



Bug#1056117: meson: generates non-determinstic .pkgconfig files

2024-02-25 Thread Fabio Pedretti
Source-Version: 1.3.1-1

Fixed upstream in 1.3.1.



Bug#1057386: [Pkg-electronics-devel] imsprog , #1057386

2024-02-20 Thread Fabio Fantoni
Hi, is it possible to upload this shortly to try to include before the 
feature freeze on Ubuntu 24.04? (February 29th)


I helped to improve the packaging, and now seems ready to me, but I'm 
only DM and I can't upload new packages.


2 DD did a review on mentors over the past weeks and the recommended 
changes have been made, but it seems they haven't had time to review it 
again recently.




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition

2024-02-19 Thread Fabio Fantoni

Il 18/02/2024 01:20, Steve Langasek ha scritto:

Hi,

It is easiest for us to include cinnamon in the batch NMUs to unstable.

Thanks,


ok, thanks, only small reminder to include the missed Breaks 
(https://salsa.debian.org/cinnamon-team/cinnamon-desktop/-/commit/b06e59910a83b2252b866d051ffe7c5ea6f6742f) 
in the NMU patch




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1063776: nagios-plugins-contrib: add a check for lvm thinpool

2024-02-12 Thread Fabio Fantoni

Package: nagios-plugins-contrib
Version:  45.20231212
Severity: wishlist

Dear Maintainer,

searching a check for lvm thinpool to avoid data corruption due to 
unexpected full I didn't found one check on the available on Debian 
packages.


I found one and tested: https://github.com/neingeist/check_lvm_thinpools

Is possible add it please? Or is there a better or one already included 
for do a similar check I didn't found?




Bug#1063662: bleachbit: Depends on transitional policykit-1

2024-02-10 Thread Fabio Fantoni

Control: merge -1 1025545

Il 10/02/2024 18:37, Martin-Éric Racine ha scritto:> Package: bleachbit

> Version: 4.4.2-1
> Severity: important
>

> Bleachbit version 4.4.2-1 depends on policykit-1 which is a 
transitional package that pulls pkexec and polkitd. Dependencies should 
be upgraded accordingly.


Hi, latest version is 4.6.0-1, before report is good check the latest 
version, this was already reported in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025545 and solved in 
4.4.2-2:



bleachbit (4.4.2-2) unstable; urgency=medium

* Team upload
* d/control: remove policykit-1 depends (Closes: #1025545)

-- Fabio Fantoni  Thu, 10 Aug 2023 11:21:13 +




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1062963: muffin: NMU diff for 64-bit time_t transition

2024-02-04 Thread Fabio Fantoni

Il 04/02/2024 08:55, Graham Inggs ha scritto:

Source: muffin
Version: 5.8.1-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
muffin as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for muffin
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.


Hi, thanks for your work.

Looking the patch in d/control these change in libmuffin-dev seems wrong 
to me:


-Breaks: libmuffin0 (<< 5.4.1-1~)
-Replaces: libmuffin0 (<< 5.4.1-1~)
+Breaks: libmuffin0t64 (<< 5.4.1-1~)
+Replaces: libmuffin0t64 (<< 5.4.1-1~)

and it should remain libmuffin0, or I'm wrong?



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition

2024-02-04 Thread Fabio Fantoni

Thanks for all the replies and sorry if I wasted your time.

After reading all your answers, some mails on debian-devel and other 
discussions on IRC I should have understood enough.


The transition with package renames and other rebuilds handled triggered 
as a batch in cooperation with the buildd maintainers seems better that 
my idea of uploading all cinnamon 6.0 packages without rename (but 
breaks). I started test of 6.0 package prepared in git but I think not 
enough if transition will happen shorly (less than one week).


do you still want to migrate also cinnamon-desktop chain despite the 
trouble I gave you?




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition

2024-02-01 Thread Fabio Fantoni
Hi, today I saw there is an autotransition that check the renamed 
libraries, so I must keep them?


https://release.debian.org/transitions/html/auto-cinnamon-desktop.html



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1061952: freerdp2: NMU diff for 64-bit time_t transition

2024-02-01 Thread Fabio Fantoni
hi, if not already spotted, keep attention that NMU missed needed 
replaces and breaks.


as reported also by 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061982




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition

2024-01-31 Thread Fabio Fantoni

Il 31/01/2024 22:24, Steve Langasek ha scritto:

On Wed, Jan 31, 2024 at 02:01:06PM +0100, Fabio Fantoni wrote:

I'm also making some improvements that I know are needed for the cinnamon
packages but slowly so as not to risk coming close to burnout again
(spending less time on the PC, at least in my free time), I'll add to the
list also to add the missed breaks of reverse deps.

Ok, if you handle it this way via additional breaks, then I think that's
sufficient for this transition and you can consider this bug resolved once
1) the dpkg change is uploaded to unstable, and 2) there's a subsequent
cinnamon transition in unstable with updated breaks.

I didn't look carefully about the time_t change as today's is the first
notice I've seen regarding one of the packages I maintain and also with
immediate NMU. I saw the transition on debian-devel ML I had looked fast at
a list of packages involved but there were no packages that I maintain
(which is why I didn't look exactly as I didn't have time and thought that
there was no were afflicted packages).

Well, there were several attempts to include a dd-list for maintainers to
review?  Your name is in the list here fwiw

   https://lists.debian.org/debian-devel/2024/01/msg00041.html

(Unfortunately lists.debian.org has been silently dropping messages on me
throughout the month, so not all of my attempts to notify maintainers via
debian-devel succeeded!)

I am un-tagging this bug 'pending' so it's clear this isn't a package we as
NMUers should be uploading to unstable.

On Wed, Jan 31, 2024 at 09:52:42PM +0100, Fabio Fantoni wrote:

I applied NMU diff to git experimental (with the work for 6.0 in progress)
and I spotted 2 mistake, one important is missed breaks with
libcinnamon-desktop4: 
https://salsa.debian.org/cinnamon-team/cinnamon-desktop/-/commit/b06e59910a83b2252b866d051ffe7c5ea6f6742f
This will cause serious issue and must be fixed before upload to unstable
FWIK.

Indeed, sorry, it looks like the conversion script wasn't able to handle
the case where an existing Breaks: field is present, but it's multiline and
there are no packages listed on the first line.  I'll take a look at fixing
the script.

But if you prefer to manage the transition with Breaks: rather than a
package rename, then you can forgo all of this anyway for your package.


About dpkg change to wait before unstable upload is about a version still
not uploaded, right? I don't saw new dpkg version in experimental

Correct.  Since the experimental uploads are just for clearing binary NEW
and doing usrmerge analysis, we determined belatedly that no dpkg upload was
needed.

Thanks,


Thanks for your reply.

I'm a bit confused, there was an immediate upload in experimental with 
rename and now you tell me I can do it without but with breaks.


so if this weekend I manage to upload all the packages for cinnamon 6.0 
to experimental, can I also remove the rename that was done?
and then, perhaps after 1-2 weeks, migrate everyone to unstable (barring 
unforeseen events) and it would be fine or are there specific time 
ranges to be respected for time_t transition?


basically what is needed for this migration is a new upload of 
cinnamon-desktop and all its inverse dependencies (having strict depends 
and breaks as if it were a soname bump) and the same should be done with 
muffin (already included) which I saw in the list that you linked me, right?




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition

2024-01-31 Thread Fabio Fantoni
I applied NMU diff to git experimental (with the work for 6.0 in 
progress) and I spotted 2 mistake, one important is missed breaks with 
libcinnamon-desktop4: 
https://salsa.debian.org/cinnamon-team/cinnamon-desktop/-/commit/b06e59910a83b2252b866d051ffe7c5ea6f6742f 



This will cause serious issue and must be fixed before upload to 
unstable FWIK.


About dpkg change to wait before unstable upload is about a version 
still not uploaded, right? I don't saw new dpkg version in experimental


At the moment I'm not sure how I should proceed.



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter

2024-01-31 Thread Fabio Pedretti
You can try installing version 24.0.0~rc3-1 in experimental, which
should have this issue fixed.



Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition

2024-01-31 Thread Fabio Fantoni

Il 31/01/2024 11:06, Steve Langasek ha scritto:

I see that there are versioned breaks from libcinnamon-desktop to older
versions of a number of its reverse-dependencies.  But not all of them!
libmuffin0, gir1.2-cinnamondesktop-3.0, and cinnamon itself appear to have
versioned depends on libcinnamon-desktop4 without being listed in the
Breaks:.  Furthermore, the change to the time_t ABI is not fixed to an
upstream release cycle; so if you upload the next version to unstable before
the dpkg change, you will have to upload again and then ABI skew is still
possible?  If it's only present in the archive in unstable for a short
period of time then you can make the case that it doesn't need a rename and
a transition.  But for the moment it looks to me like a transition will be
needed.

Thanks for your reply, unfortunately I don't have much time these days 
and I was planning to invest it to complete the preparation of cinnamon 
6.0 for experimental for the upload of 9 components together 
(cinnamon-desktop, cinnamon-translations, cinnamon-sessions, 
cinnamon-screensaver, cinnamon-settings-daemon, cinnamon-control-center, 
muffin, nemo, cinnamon), after testing and improve it for upload 
migration before ubuntu 24.04 feature freeze (so take cinnamon 6.0 with 
autosync from debian).


I'm also making some improvements that I know are needed for the 
cinnamon packages but slowly so as not to risk coming close to burnout 
again (spending less time on the PC, at least in my free time), I'll add 
to the list also to add the missed breaks of reverse deps.


I didn't look carefully about the time_t change as today's is the first 
notice I've seen regarding one of the packages I maintain and also with 
immediate NMU. I saw the transition on debian-devel ML I had looked fast 
at a list of packages involved but there were no packages that I 
maintain (which is why I didn't look exactly as I didn't have time and 
thought that there was no were afflicted packages).


in practice only a rebuild would be necessary but does this rebuild have 
to be done at certain times?


Now I see the upload in experimental has been accepted and I have to 
keep them, right?


What I need to know is about uploading to unstable, what I have to wait 
exactly? and then within what limit must it be done? to understand how 
to organize the other cinnamon 6.0 uploads that I need to do so as not 
to create problems for this transition.






OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter

2024-01-31 Thread Fabio Pedretti
Hi jim_p, if you are referring to:
https://gitlab.archlinux.org/archlinux/packaging/packages/mesa/-/commit/15e037dba159f893360d642e4efa13e09682b080
I don't think is related to this issue.
I suggest to report it here: https://gitlab.freedesktop.org/mesa/mesa/-/issues
In your log this looks relevant:
[   0.318][v][vo/gpu/vaapi] using EGL dmabuf interop
[   0.319][v][vo/gpu/vaapi] Trying to open a x11 VA display...
[   0.319][d][vo/gpu/vaapi/vaapi] libva: VA-API version 1.20.0
[   0.319][d][vo/gpu/vaapi/vaapi] libva: Trying to open
/usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
[   0.328][d][vo/gpu/vaapi/vaapi] libva: Found init function __vaDriverInit_1_20
[   0.340][d][vo/gpu/vaapi/vaapi] libva: va_openDriver() returns 0
[   0.341][v][vo/gpu/vaapi/vaapi] Initialized VAAPI: version 1.20
[   0.341][d][ffmpeg] AVHWDeviceContext: VAAPI driver: Mesa Gallium
driver 23.3.4-1 for AMD CAICOS (DRM 2.50.0 / 6.5.0-5-amd64, LLVM
17.0.6).
[   0.341][d][ffmpeg] AVHWDeviceContext: Driver not found in known
nonstandard list, using standard behaviour.
[   0.341][v][vo/gpu/vaapi] Going to probe surface formats (may log
bogus errors)...
[   0.344][d][vo/gpu/vaapi] Failed to create mapper
[   0.344][d][vo/gpu/vaapi] Unsupported format: yuyv422
[   0.345][d][vo/gpu/vaapi] Failed to create mapper
[   0.345][d][vo/gpu/vaapi] Unsupported format: uyvy422
[   0.346][d][vo/gpu/vaapi] vaExportSurfaceHandle() failed (an
unsupported memory type was supplied)
[   0.346][d][vo/gpu/vaapi] Unsupported format: argb
[   0.346][d][vo/gpu/vaapi] Supported formats:
[   0.346][d][vo/gpu/vaapi]  nv12
[   0.346][d][vo/gpu/vaapi]  p010
[   0.346][d][vo/gpu/vaapi]  yuv420p
[   0.346][d][vo/gpu/vaapi]  gray
[   0.346][d][vo/gpu/vaapi]  yuv444p
[   0.346][d][vo/gpu/vaapi]  bgra
[   0.346][d][vo/gpu/vaapi]  rgba
[   0.346][d][vo/gpu/vaapi]  bgr0
[   0.346][d][vo/gpu/vaapi]  rgb0
[   0.346][v][vo/gpu/vaapi] Done probing surface formats.



Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition

2024-01-31 Thread Fabio Fantoni

Il 31/01/2024 09:54, Steve Langasek ha scritto:

Source: cinnamon-desktop
Version: 5.8.0-2
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
cinnamon-desktop as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for cinnamon-desktop
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.

Hi, this rename is really needed? Cinnamon upstream don't don't soname 
bump even when needed and we use strict depends and upload of multiple 
component together as a workaround every major version, I've almost 
finished the next one which I would have done within a few days.


I don't have much time but I was also trying to reduce the differences 
and conflicts with the upstream packaging which causes reports of 
hundreds of users trying to upgrade the cinnamon packages but the 
upgrade fails due to conflicts.





OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#787764: libvpx2: vp9 encoding is significantly slower in 1.4.0 than in 1.3.0

2024-01-30 Thread Fabio Pedretti
Hi Matt, can you check if the performance regression you noticed with
1.4.0 was resolved with a newer libvpx release?
You may also eventually check the upstream issues report at
https://bugs.chromium.org/p/webm/issues/list
Thanks.



Bug#1015532: libvpx: ftbfs with LTO (link time optimization) enabled

2024-01-30 Thread Fabio Pedretti
forwarded 1015532 https://bugs.chromium.org/p/webm/issues/detail?id=1736
thanks



Bug#1061547: freeipmi: ipmi-sensors - internal IPMI error with kcs driver

2024-01-27 Thread Fabio Fantoni
unfortunately at the moment there is a regression related to those 2 
functions which has caused the build to fail in almost all architectures


https://buildd.debian.org/status/package.php?p=freeipmi=sid

I also reported upstream:

https://github.com/chu11/freeipmi-mirror/issues/70

I tried to do some quick revert tests but unfortunately at the moment I 
didn't succeed and I don't have enough time to prepare a sufficiently 
updated Debian on my raspberry (for reproduce the issue) to continue 
with the tests


any help is welcome



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1061547: freeipmi: ipmi-sensors - internal IPMI error with kcs driver

2024-01-27 Thread Fabio Fantoni

Il 26/01/2024 09:48, Yannick Martin ha scritto:

Hello,

Since freeipmi-1.6.9, ipmi queries via kcs driver may not work.
I opened an issue on upstream project: http://savannah.gnu.org/support/?111010

Is it possible to rebuild bookworm freeipmi packages with this ?

Regards


Thanks for report, for now I uploaded to unstable.

About do a stable proposed update is not easy/fast: 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable


If patch is small and risk of regression is small is possible.

The fix is only this upstream commit 
https://github.com/chu11/freeipmi-mirror/commit/379c8569711d808c3366a99d1dfac5e414858800 
and not other patch need to be applied to bookworm version?




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1056906: debuild: cannot disable lintian

2024-01-23 Thread Fabio Pedretti
Please close this issue. Thanks.



Bug#1061021: cinnamon-control-center: FTBFS: Package 'libevdev', required by 'libwacom', not found

2024-01-16 Thread Fabio Fantoni

Il 16/01/2024 20:29, Lucas Nussbaum ha scritto:

CMake binary for host machine is not cached
CMake binary missing from cross or native file, or env var undefined.
Trying a default CMake fallback at cmake
Did not find CMake 'cmake'
Found CMake: NO
Dependency lookup for libwacom with method 'cmake' failed: CMake binary for 
machine host machine not found. Giving up.
Run-time dependency libwacom found: NO

../meson.build:86:14: ERROR: Dependency lookup for libwacom with method 
'pkgconfig' failed: Could not generate cflags for libwacom:
Package libevdev was not found in the pkg-config search path.
Perhaps you should add the directory containing `libevdev.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libevdev', required by 'libwacom', not found

dh_auto_configure: error: cd obj-x86_64-linux-gnu && 
DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload 
--buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var 
--libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 returned exit code 1
make: *** [debian/rules:10: binary] Error 25


Thanks for your work about FTBFS reports.

libevdev seems don't required by cinnamon-control-center but by wacom, 
from a fast look I saw require it but don't have libevdev-dev dep.


anyway is already reported by 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060687


I don't think is a good thing add libevdev-dev build-dep. in 
cinnamon-control-center as temporary workaround and should wait fix in 
libwacom instead, or I'm wrong?




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1059940: cinnamon-session: missing dependencies on required typelibs

2024-01-03 Thread Fabio Fantoni

Il 03/01/2024 22:59, Simon McVittie ha scritto:

This is off-topic for #1059678, really, so I'm converting it into a
separate bug report.

Yes, if your application does this:


import gi
gi.require_version('Gtk', '3.0')
gi.require_version('XApp', '1.0')
from gi.repository import GLib, Gio, Gtk, Gdk, XApp

in a required component, then it should have dependencies on
gir1.2-gtk-3.0, gir1.2-xapp-1.0, gir1.2-glib-2.0, gir1.2-gio-2.0 and
gir1.2-gdk-3.0, as well as python3-gi.

(gir1.2-gio-2.0 is a virtual package provided by gir1.2-glib-2.0,
and gir1.2-gdk-3.0 is a virtual package provided by gir1.2-gtk-3.0,
so strictly speaking you don't need to add those two dependencies,
but I think it's clearer and more robust to write them out explicitly
rather than thinking about how to minimize the list.)

If the dependencies are in an unimportant part of the package (like
the plugins in exaile, #1059625), then it would be OK to downgrade
them to Recommends or Suggests, or perhaps even close this bug with no
action. Conversely, if cinnamon-session-quit.py is an important part of
this package, then they should be hard dependencies (and this bug report
should be RC).

More generally, if your application loads FooBar-2.3.typelib, then it
should usually have a dependency on gir1.2-foobar-2.3. The package names
are mechanically derived from the typelib name.

Please seefile:///usr/share/doc/gobject-introspection/policy.txt.gz
for more information.

If there are other Cinnamon components that import typelibs via PyGObject
(or cjs or gjs) but don't have a dependency on the required typelib,
then please fix those too.


Thanks for the report, cinnamon-session 5.8.1-2 don't have python files, 
cinnamon-session-quit.py was added in 6.0, is in salsa git for next 
upload to experimental for now, I have added the python and gir deps and 
I'll add other gir deps for the packages will be splitted, based on what 
you wrote in cjs bugreport, I'll check also other components when 
preparing 6.0 packages




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1059678: libcjs0: please depend on gir1.2-girepository-2.0 and other typelibs used by built-in modules

2024-01-03 Thread Fabio Fantoni

Il 03/01/2024 20:04, Simon McVittie ha scritto:

On Sat, 30 Dec 2023 at 00:02:51 +, Simon McVittie wrote:

cjs contains code that explicitly loads the GIRepository-2.0 typelib
(in modules/script/package.js, which is the implementation of the
imports.package API).

GIRepository is currently part of gir1.2-glib-2.0, but it will need
to be moved to a separate binary package during the GNOME 46 cycle,
as a result of most of gir1.2-glib-2.0 moving to src:glib2.0 (which has
broken some of the API/ABI in the process, resulting in it shipping an
incompatible GIRepository-3.0 instead). A preliminary version of this
package split has been uploaded to experimental and is waiting in the NEW
queue:
https://salsa.debian.org/gnome-team/gobject-introspection/-/tree/debian/new

(In the meantime this change has passed through NEW and reached experimental)


To ensure that the imports.package API continues to work
correctly for cjs applications, please add an explicit dependency on
gir1.2-girepository-2.0, as in the attached patch 0001 (this corresponds
to the change I uploaded in gjs 1.78.1-2). In current trixie/sid,
this is a virtual package provided by gir1.2-glib-2.0, but in future,
I expect it to become a separate binary package.

For completeness, I think it would be best to add explicit dependencies
on all of the typelibs imported by the built-in modules in cjs'
modules/script/: I believe the attached patch 0002 is correct for this
(this corresponds to gjs 1.78.1-3).

I don't use Cinnamon or its applications myself, so I haven't tested
the attached patches, but to the best of my knowledge they're correct.

In practice, the only cjs application seems to be the cinnamon desktop
shell itself (Cinnamon's equivalent of GNOME Shell), and that doesn't
seem to use the imports.package API, so this missing dependency is
probably not going to break it. As a result, this is probably not RC
even with the proposed version of gobject-introspection.
Thanks for report and the patches, about apply them in debian unstable 
is ok for the provides.


Thinking about the next PR I would upstream so it will support the next 
Ubuntu LTS but it must also support the current Debian Stable and 
current ubuntu LTS.


From a fast look to  bookworm version 
(https://buildd.debian.org/status/fetch.php?pkg=gobject-introspection=amd64=1.74.0-3=1674166945=0) 
provides are present and the jammy version 
(https://buildd.debian.org/status/fetch.php?pkg=gobject-introspection=amd64=1.72.0-1=1647611197=0) 
also, so will be ok also for upstream, right?


I was also wondering about "gi.repository import" of python scripts, 
present in other components, it don't will be the same needs of depends? 
I mean for example 
https://github.com/linuxmint/cinnamon-session/blob/master/cinnamon-session-quit/cinnamon-session-quit.py


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057391: cinnamon and private GIR XML

2023-12-23 Thread Fabio Fantoni
Big thanks to Simon McVittie for good explain about some things I 
couldn't find enough information about.


Combined with what I had already seen, we need to move the cinnamon gir 
to a private path, then once done I can move it to cinnamon-common to 
align with the upstream.


Cinnamon girs are not used by other packages or non-packaged software 
but only recently added upon request and therefore used only in rare 
cases by developers (based on what I found). So I don't think it's a 
problem for them to do additional manual operations such as installing 
the necessary -dev packages. If it were up to me it wouldn't be a 
problem to add the cinnamon-dev package in which to move the girs and 
have all the necessary dependencies but I fear that the upstream 
wouldn't want it and I want to avoid confict with upstream is possible. 
However there doesn't seem to be a need for this package if I'm not 
mistaken.


About dh_girepository so is not needed use it with private gir, so I 
could remove it and it will only be necessary to manage it if any future 
changes are made that will automatically scan for any gir (even private 
ones), right? If future changes will scan for private gir add of 
"--no-dev-dependencies" can be useful but given the rare case it doesn't 
seem very important to me and we could manage with the override. Or you 
are sure to do this changes so I keep override to avoid another future 
fail to build?


About muffin gir private (as actually) is needed for fork of integrated 
things, muffin packages on debian seems ok now, or I'm wrong? upstream 
also had improved packaging when a rebase was done, only one thing seems 
missed, the move of /usr/libexec/muffin-restart-helper out of libmuffin0 
package (upstream moved from muffin package to libmuffin0 in 4.0 and 
keeped it). On debian packages we don't moved same of upstream or it 
would go against shared library package policies. or am I wrong?






OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1059329: cinnamon-desktop-environment: dependency on noto-font installs too many fonts, fontlist exploded.

2023-12-22 Thread Fabio Fantoni
Hi, this was already reported by other people and fixed in 5.8.0 (that 
is in unstable/testing) moving fonts-noto from deps to recommends.


I was thinking if it might be useful to further reduce the default 
installation (with recommended) by replacing fonts-noto with 
fonts-noto-core, but I don't know how much the fonts of the other 
packages recommended by fonts-noto are used.


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057391: cinnamon: FTBFS: dh_girepository: error: Could not find Clutter-0.gir dependency

2023-12-09 Thread Fabio Fantoni
Thanks for all informations, I did some changes in git, moved gir files 
in /usr/share/cinnamon


the package for the split should be cinnamon-dev, with only gir I 
thinked gir1.2-cinnamon-0.1-dev, what is correct and/or best?


upstream tends to avoid new packages even when in theory they would be 
needed, therefore go through NEW for other new packages is highly 
unlikely. If add -dev package has to be done I should do it. what do you 
recommend?


about needed -dev deps for gir, that in cinnamon package is not good, 
can still remove these dependencies or would it just be a temporary 
thing until the split into a new package but normally they must be 
present? (so sooner or later the separate package that has them must be 
made sooner or later)


user testing cinnamon 6 on sid spotted -dev package in 
gir1.2-cscreensaver-1.0 actually not present, so I suppose added from 
recent dh_girepository changes. upstream have all in libcscreensaver0, 
so I created at least gir1.2-cscreensaver-1.0 in 5.4.1-2 to solve the 
policy issue (I not tried to do a PR for upstream now) but I put also 
gir file in it instead create -dev package for only it. I must create 
gir1.2-cscreensaver-1.0-dev with gir and all needed -dev deps or is 
possible remove the -dev deps?


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057391: cinnamon: FTBFS: dh_girepository: error: Could not find Clutter-0.gir dependency

2023-12-08 Thread Fabio Fantoni

I tried to look on recent gobject-introspection changes

About muffin I tried to add "Provides: ${gir:Provides}" to -dev package 
but it didn't added anything, I tried after saw 
https://salsa.debian.org/gnome-team/gobject-introspection/-/commit/d3611aaf3d8d98ca910b5f1e96f68a579538507f


I not understand what I should do about muffin as have only one packages 
with private gir, maintain one gir package will remain ok? I should add 
only a manual Provides in -dev package?


About cinnamon I saw that add this fixed the build:


override_dh_girepository:
dh_girepository --verbose /usr/lib/$(DEB_HOST_MULTIARCH)/muffin


from the build the output was:


dh_girepository --verbose /usr/lib/x86_64-linux-gnu/muffin
|
Package: cinnamon
||
Public GIR XML directory: debian/cinnamon/usr/share/gir-1.0
||
GIR XML: St-1.0.gir
||
Dependency: Clutter-0.gir
||
Dependency: ClutterX11-0.gir
||
Dependency: Gtk-3.0.gir
||
Dependency: Meta-0.gir
||
GIR XML: Cinnamon-0.1.gir
||
Dependency: CMenu-3.0.gir
||
Dependency: Clutter-0.gir
||
Dependency: ClutterX11-0.gir
||
Dependency: Cogl-0.gir
||
Dependency: CoglPango-0.gir
||
Dependency: Meta-0.gir
||
Dependency: St-1.0.gir
||
rm -f
||
cinnamon Provides gir1.2-st-1.0-dev (= 5.8.4-4~+salsaci+20231208+166)
||
mv debian/cinnamon.substvars.new debian/cinnamon.substvars
||
cinnamon Provides gir1.2-cinnamon-0.1-dev (= 
5.8.4-4~+salsaci+20231208+166)

||
mv debian/cinnamon.substvars.new debian/cinnamon.substvars
||
Dependency: Clutter-0.gir
||
cinnamon Depends libmuffin-dev (>= 5.8~) for Clutter-0.gir (version 
taken from libmuffin-dev in B-D)

||
mv debian/cinnamon.substvars.new debian/cinnamon.substvars
||
Dependency: ClutterX11-0.gir
||
cinnamon Depends libmuffin-dev (>= 5.8~) for ClutterX11-0.gir (version 
taken from libmuffin-dev in B-D)

||
Dependency: Gtk-3.0.gir
||
Dependency: Gtk-3.0.gir
||
dh_girepository: warning: libgtk-3-dev should have Provides: 
gir1.2-gtk-3.0-dev (= ${binary:Version})

||
cinnamon Depends libgtk-3-dev (>= 3.9.12) for Gtk-3.0.gir (version 
taken from libgtk-3-dev in B-D)

||
mv debian/cinnamon.substvars.new debian/cinnamon.substvars
||
Dependency: Meta-0.gir
||
cinnamon Depends libmuffin-dev (>= 5.8~) for Meta-0.gir (version taken 
from libmuffin-dev in B-D)

||
Dependency: CMenu-3.0.gir
||
Dependency: CMenu-3.0.gir
||
dh_girepository: warning: libcinnamon-menu-3-dev should have Provides: 
gir1.2-cmenu-3.0-dev (= ${binary:Version})

||
cinnamon Depends libcinnamon-menu-3-dev (>= 5.4~) for CMenu-3.0.gir 
(version taken from libcinnamon-menu-3-dev in B-D)

||
mv debian/cinnamon.substvars.new debian/cinnamon.substvars
||
Dependency: Cogl-0.gir
||
cinnamon Depends libmuffin-dev (>= 5.8~) for Cogl-0.gir (version taken 
from libmuffin-dev in B-D)

||
Dependency: CoglPango-0.gir
||
cinnamon Depends libmuffin-dev (>= 5.8~) for CoglPango-0.gir (version 
taken from libmuffin-dev in B-D)

||
Dependency: St-1.0.gir
||
found in the same package
||
Package: cinnamon-common
||
rm -f
||
Package: cinnamon-doc
||rm -f|
and seems it should add some -dev packages as cinnamon deps that I think 
not good, I suppose I should create a new package instead like 
gir1.2-cinnamon-0.1-dev, or I'm wrong?


on cinnamon full -dev package is not needed but only gir files for few 
cases (only developer I think) can be useful so was added in cinnamon 
package


anyway when I tried to look artifact 
(https://salsa.debian.org/cinnamon-team/cinnamon/-/commit/c74a32e74374e5c61e7546c2f28a6a858e2f6999/pipelines?ref=master) 
cinnamon packages don't have -dev deps wrote by dh_girepository, is it 
correct?


thanks for any reply



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057391: cinnamon: FTBFS: dh_girepository: error: Could not find Clutter-0.gir dependency

2023-12-04 Thread Fabio Fantoni

Il 04/12/2023 22:14, Holger Schröder ha scritto:



The same thing happens when you try to build Cinnamon 6.0.0


https://github.com/linuxmint/cinnamon


/hsp


Is not related to cinnamon itself but to latest gobject-introspection 
changes in sid/testing


I don't know what is the good way to fix it, a possibile workaround I 
suppose is add provide for each gir but it doesn't seem like a good idea 
add 6 provides in a muffin package


I'll try to see if someone recommend something better, otherwise I'll 
try anyway






OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1054645:

2023-11-30 Thread Fabio Pedretti
forwarded 1054645 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10228
thanks



Bug#1057033: nemo: Several MIME types not recognized on GVFS mounted volumes

2023-11-28 Thread Fabio Fantoni

Control: fixed -1 5.8.5-2

Hi, thanks for the report.

Problem reproduced immediately when seeing a .doc file on share smb, on 
Sid with nemo 5.8.5 is not present so was fixed but from a fast search I 
don't found the possible commit of fix, only one related to video 
thumbnails from network shares 
(https://github.com/linuxmint/nemo/pull/3265) but should not be related FWIK


Even if the fix commit were found, however, it is not a bug important 
enough to propose a stable update.


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1056906: debuild: cannot disable lintian

2023-11-26 Thread Fabio Pedretti
Il giorno dom 26 nov 2023 alle ore 14:37 Adam D. Barratt
 ha scritto:
>
> Control: tags -1 + moreinfo
>
> On Sun, 2023-11-26 at 14:06 +0100, Fabio Pedretti wrote:
> > when I add --no-lintian (as found in debuild man page) option
> > to debuild, I get the following error:
> >
> > ...
> >  dpkg-buildpackage -us -uc -ui -S -sd -d --no-lintian
> > dpkg-buildpackage: error: unknown option or argument --no-lintian
>
> That suggests you've added it in the wrong part of the command line.
> https://manpages.debian.org/bookworm/devscripts/debuild.1.en.html
> clearly shows in the synopsis that all debuild-specific options must
> come _before_ any dpkg-buildpackage-specific options, and that --(no-
> )lintian affects the behaviour of debuild itself, so falls into the
> former set.
>
> What *exactly* does your debuild invocation look like?

You are right, I was calling it this way:
debuild -S -sd -d -kMYKEY --no-lintian
while this way it works:
debuild --no-lintian -S -sd -d -kMYKEY

About the man page, it says:
debuild [debuild options] [dpkg‐buildpackage options] [--lintian‐opts
lintian options]
which let me suppose lintian options have to be called at last. But it
is just for the specific --lintian‐opts, not --(no-)lintian, OK.

> > I also tried setting:
> > export DEBUILD_LINTIAN=no
> > but it still uses lintian.
> >
>
> If you've added that to your shell, or a file like .profile, then
> that's not particularly surprising, given that the same manpage also
> says that DEBUILD_LINTIAN is a configuration variable, which is read
> from one of two files, and "[e]nvironment variable settings are ignored
> when these configuration files are read". (In common with almost every
> variable any script in devscripts uses.)

/etc/devscripts.conf says "This file is sourced by /bin/bash ...",
however, as you says, there is that note in debuild man page.

Thanks for the quick reply, I suppose we could close this issue.



Bug#1053241: glibc: please apply upstream patch to fix slow fstat

2023-11-26 Thread Fabio Pedretti
Il giorno dom 26 nov 2023 alle ore 16:28 Aurelien Jarno
 ha scritto:
>
> Hi,
>
> On 2023-09-29 21:52, Fabio Pedretti wrote:
> > Package: glibc
> > Version: 2.36-9+deb12u1
> > Severity: normal
> > X-Debbugs-Cc: pedretti.fa...@gmail.com
> >
> > Dear Maintainer,
> >
> > glibc uses a slow version of fstat. Details are documented
> > here: https://lwn.net/Articles/944214/
> >
> > A patch to fix this was merged in glibc:
> > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=551101e8240b7514fc646d1722f8b79c90362b8f
> >
> > The patch applies cleanly and builds fine also on bookworm glibc.
> > Please consider apply it to fix slow fstat.
>
> This patch changes the syscall used by binaries, so it has to be
> considered with a lot of care in a stable release, it could break
> existing seccomp filters. In any case it has to live a few months in
> testing/unstable first.
>
> Note that the kernel patch that improves the performance of fstatat, has
> not been merge to the upstream stable tree, nor to bookworm.
>
> In order to better understand the need for this patch in bookworm, could
> you please give some details about your workload and the performance
> impact it has?

I did some test with my use case, borg backup with many unchanged
files, see https://github.com/borgbackup/borg/issues/4498 for some
background and system calls impact, where borg 1.2 slow downs a lot
vs. borg 1.1.

I checked using strace the patch, it did the job (newfstatat calls
were replaced with fstat), and I'd hoped that it would improve
performance, however my use case improved just marginally (difficult
to have reproducible data in my case, but it was like 5%).

I didn't notice any other regression, however.

I see the glibc patch is still only on 2.39, while even Debian
experimental has just 2.38.

The alternative kernel patch is in 6.6 (as you say, still not in Debian).

Given all of this, I agree we can wait to land it on trixie and leave
bookworm as is, so feel free to just close the issue in this case.

Thanks for your time.



Bug#1056906: debuild: cannot disable lintian

2023-11-26 Thread Fabio Pedretti
Package: devscripts
Version: 2.23.6
Severity: normal
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

when I add --no-lintian (as found in debuild man page) option
to debuild, I get the following error:

...
 dpkg-buildpackage -us -uc -ui -S -sd -d --no-lintian
dpkg-buildpackage: error: unknown option or argument --no-lintian

Use --help for program usage information.
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -S -sd -d --no-lintian failed
...

I also tried setting:
export DEBUILD_LINTIAN=no
but it still uses lintian.



Bug#1056731: RFS: backintime/1.4.1-0.1 [NMU] -- simple backup/snapshot system (graphical interface)

2023-11-25 Thread Fabio Fantoni

Il 25/11/2023 20:52, Tobias Frost ha scritto:

Hi Fabio,

Am Sat, Nov 25, 2023 at 07:33:32PM +0100 schrieb Fabio Fantoni:

Il 25/11/2023 18:10, Tobias Frost ha scritto:

This seems a bit ouf of scope for an NMU (new upstream releases are
NMUed only in exceptional cases) and #998105 is severity normal and
#973760 is severity minor. (Please see the developers reference about
NMUs.

Do you have additional information why this should be an NMU?
I'm seeing you are member of the repo, should your name be added as
Uploaders and this be a regular upload?
Did you reach out to the maintainers and get an ACK from them?


Hi, thanks for reply. I recently did some help on this package because I use
it, so when I see cases with issue and/or new upstream version (with useful
things) where a lot of time passes I try to help if I have time.

even if #998105 is only set "normal" is "a regression" that make users that
backup over ssh waste time to found the workaround, I tried also to be fixed
for bookworm (before release) with a upload with only this fix 
(https://salsa.debian.org/jmw/pkg-backintime/-/commit/0066cffd98aa09c5528cb94abedda5a1a5e59e3e)
but was rejected by the maintainer, then he replied to me who just wanted to
wait for the bookworm release and have additional things before making a new
upload. so I gave up and waited until after the new upstream version came
out (and I still waited another month before doing anything)

It seems that commit was done during or just before the hard-freeze, and thus 
not
acceptable as per release policy.

The problem's severiy "normal" seems to be appropiate, too.


Although it is not such a long time or with such serious bugs from the
general point of view of debian, some upstream developers and users have
come to consider this package as abandoned, here is an example:
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2039271 (anyway
In that case it would not have been possible to upload the new upstream
version anyway as that Ubuntu version was in freeze)

(Ubuntu != Debian.)
And as you say on the launchpad bug, 4 uploads a year well means this package
is maintained.


I would prefer a normal upload (from the maintainer), already prepared and
tested, it also saves time, but unfortunately as I wrote at the moment I
have not received any response and I had only been given permission for the
repository previously where I already started to prepare for new upload one
month ago. I also write to upload with delay for give another possibility to
the maintainer, if he will have time

regarding the maintainers list I think it would be good to have it in the
debian python team but doing this or possibly adding me as co-maintainer is
a choice of the current maintainer. however I can't guarantee that I would
have enough time to follow it and make quick enough uploads when needed in
the long term.

If the maintainer responds to me in the future I will ask if he wants do
something.

thanks for your explanations. Unfortunatly, I fear that your NMU is outside of
the scope of NMUs, despite the good intentions you have.

NMUing a new upstream version is only appropiate under certain conditions. For
example it is preferred to have dedicated patches to fix problems (but not
during a freeze, of course)

So if you come up with dedicated fixes, this NMU can go forward, otherwise, I
fear, not, unless the maintainer actively acked. (There is also no bug that
expressed the intention that you are going to NMU on the package's BTS)

Other option would be to invoke the ITS process, but I'm not sure (as in I did
not check in depth),whether the package would be eligble. Of course, you will
have to commit to the maintainance of the package then.
(But a NMU does also, albeit not to the same extend.)

thanks for reply, don't seems needed ITS for now, the maintainer is 
active (https://salsa.debian.org/jmw), probably only have few time and 
some periods where he doesn't even can't reply to mail


I'll wait a little longer for now




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1056731: RFS: backintime/1.4.1-0.1 [NMU] -- simple backup/snapshot system (graphical interface)

2023-11-25 Thread Fabio Fantoni

Il 25/11/2023 18:10, Tobias Frost ha scritto:

This seems a bit ouf of scope for an NMU (new upstream releases are
NMUed only in exceptional cases) and #998105 is severity normal and
#973760 is severity minor. (Please see the developers reference about
NMUs.

Do you have additional information why this should be an NMU?
I'm seeing you are member of the repo, should your name be added as
Uploaders and this be a regular upload?
Did you reach out to the maintainers and get an ACK from them?

Hi, thanks for reply. I recently did some help on this package because I 
use it, so when I see cases with issue and/or new upstream version (with 
useful things) where a lot of time passes I try to help if I have time.


even if #998105 is only set "normal" is "a regression" that make users 
that backup over ssh waste time to found the workaround, I tried also to 
be fixed for bookworm (before release) with a upload with only this fix 
(https://salsa.debian.org/jmw/pkg-backintime/-/commit/0066cffd98aa09c5528cb94abedda5a1a5e59e3e) 
but was rejected by the maintainer, then he replied to me who just 
wanted to wait for the bookworm release and have additional things 
before making a new upload. so I gave up and waited until after the new 
upstream version came out (and I still waited another month before doing 
anything)


Although it is not such a long time or with such serious bugs from the 
general point of view of debian, some upstream developers and users have 
come to consider this package as abandoned, here is an example: 
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug /2039271 
(anyway In that case it would not have been possible to upload the new 
upstream version anyway as that Ubuntu version was in freeze)


I would prefer a normal upload (from the maintainer), already prepared 
and tested, it also saves time, but unfortunately as I wrote at the 
moment I have not received any response and I had only been given 
permission for the repository previously where I already started to 
prepare for new upload one month ago. I also write to upload with delay 
for give another possibility to the maintainer, if he will have time


regarding the maintainers list I think it would be good to have it in 
the debian python team but doing this or possibly adding me as 
co-maintainer is a choice of the current maintainer. however I can't 
guarantee that I would have enough time to follow it and make quick 
enough uploads when needed in the long term.


If the maintainer responds to me in the future I will ask if he wants do 
something.





OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#973760: backintime-common: in backintime.py function smartRemoveList missing return value

2023-11-25 Thread Fabio Fantoni

Control: reopen -1

This was not really solved in debian, will be solved in next upload



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1056731: RFS: backintime/1.4.1-0.1 [NMU] -- simple backup/snapshot system (graphical interface)

2023-11-25 Thread Fabio Fantoni

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : backintime
   Version  : 1.4.1-0.1
 * URL  : https://github.com/bit-team/backintime
 * License  : GPL-2+
 * Vcs  : https://salsa.debian.org/jmw/pkg-backintime
   Section  : utils

The source builds the following binary packages:

  backintime-common - simple backup/snapshot system (common files)
  backintime-qt - simple backup/snapshot system (graphical interface)

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/backintime/backintime_1.4.1-0.1.dsc


After one month from new upstream version without no activity on debian 
packaging I prepared it on git https://salsa.debian.org/jmw/pkg-backintime


After some days, 21 day ago I also write a mail to maintainer without 
reply for now


So I prepared this NMU, can someone upload it with a delay of few days 
please? to give a further upload possibility to the maintainer, just as 
I have not uploaded the release commit to git (I will only do it if the 
nmu reaches the repository)



Changes since the last upload:

 backintime (1.4.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * New upstream version 1.4.1 (Closes: #998105, #973760)
   * d/patches: remove one patch applied upstream
   * Update d/copyright

Regards,
--
  Fabio Fantoni



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1050264: Updating the bleachbit Uploaders list

2023-11-24 Thread Fabio Fantoni
Hi, when I'll have time I'll prepare for next upload with latest 
upstream version and also fixing this, is ok move debian python team as 
maintainer and remove Hugo remaining without a person in the maintainers 
list (uploaders field)?


Lately I've been helping this package a bit occasionally since no one 
was working on it and it's one of the software I use but I don't know if 
I have enough time to maintain it well (doing quick uploads as needed) 
and in the long term. So I don't know is good whether to join uploaders 
or not.




OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1022034: policyd-rate-limit: Uses deprecated yaml.load

2023-10-04 Thread Fabio
Package: policyd-rate-limit
Version: 1.0.1.1-2.1
Followup-For: Bug #1022034

Dear Maintainer,

seems that utils.py use an old syntax, I've applied this patch:

88c88
< self._config = yaml.load(f)
---
> self._config = yaml.load(f, 
> Loader=yaml.SafeLoader)

to the file:

usr/lib/python3/dist-packages/policyd_rate_limit/utils.py

Still testing but seems resolved.

-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-12-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages policyd-rate-limit depends on:
ii  adduser  3.134
ii  init-system-helpers  1.65.2
ii  python3  3.11.2-1+b1
ii  python3-yaml 6.0-3+b2

policyd-rate-limit recommends no packages.

Versions of packages policyd-rate-limit suggests:
pn  python3-mysqldb   
ii  python3-psycopg2  2.9.5-1+b1

-- no debconf information



Bug#1053306: libxapp1: xapp-sn-watcher.desktop file should be in the xapp-sn-watcher debian package

2023-10-03 Thread Fabio Fantoni

Il 03/10/2023 21:21, Alban Browaeys ha scritto:

$ apt policy libxapp1
libxapp1:
   Installé : 2.6.1-1
   Candidat : 2.6.1-1
  Table de version :
  *** 2.6.1-1 500
  90 http://ftp.debian.org/debian sid/main amd64 Packages
 500 http://deb.debian.org/debian trixie/main amd64 Packages
 100 /var/lib/dpkg/status
  2.4.2-3 500
 500 http://deb.debian.org/debian bookworm/main amd64 Packages
  1.2.2-1 500
 500 http://httpredir.debian.org/debian buster/main amd64 Packages

ls /etc/xdg/autostart/xapp-sn-watcher.desktop
/etc/xdg/autostart/xapp-sn-watcher.desktop

dpkg -S  /etc/xdg/autostart/xapp-sn-watcher.desktop
libxapp1:amd64: /etc/xdg/autostart/xapp-sn-watcher.desktop

dpkg-query -W -f='${Conffiles}\n' | grep obsolete$ |grep xapp-sn
  /etc/xdg/autostart/xapp-sn-watcher.desktop a9fa3be7aaf46761adcdb856c63c125f 
obsolete


It could still be
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886389
still all the report I found in it, tell the files are owned by the new
package but still marked as obsolete.

Here, the file is still owned by the old package. I do not even have
the new package xapp-sn-watcher installed.

So maybe it is the same bug but without installing the new package the
ownership is also not removed from the old package.
This might help define the origin of this bug.

Cheers,
Alban

this is for xapp-sn-watcher not installed in this case rm_conffile will 
works correctly but installing also xapp-sn-watcher will remove 
xapp-sn-watcher.desktop broking it after the upgrade so I couldn't do it 
as I wrote, I did some tests looking for a workaround but unfortunately 
I didn't find any and the "best" solution was to not to use rm_conffile.


after this new issue (with people that don't install recommends) I 
thinked about increase to depends but I think is a problem have circular 
depends (xapp-sn-watcher depends on libxapp1)


so I suppose that the best thing it would fix that old bug in dpkg, but 
I don't know how


or someone have another idea? any advice is welcome



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1053306: libxapp1: xapp-sn-watcher.desktop file should be in the xapp-sn-watcher debian package

2023-10-01 Thread Fabio Fantoni

Il 01/10/2023 12:33, Alban Browaeys ha scritto:

Package: libxapp1
Version: 2.6.1-1
Severity: normal

Dear Maintainer,
I get this error in my logs:
oct. 01 12:19:15 hermes systemd-xdg-autostart-generator[501717]: Exec binary 
'/usr/lib/x86_64-linux-gnu/xapps/sn-watcher/xapp-sn-watcher' does not exist: No 
such file or directory
oct. 01 12:19:15 hermes systemd-xdg-autostart-generator[501717]: 
/etc/xdg/autostart/xapp-sn-watcher.desktop: not generating unit, error parsing 
Exec= line: No such file or directory

it turns out I have libxapp1:amd64 2.6.1-1 installed but not xapp-sn-watcher.

I believe the xapp-sn-watcher.desktop shipped by libxapp1 should be shipped by
the xapp-sn-watcher package.


Hi, from the version you are reporting xapp-sn-watcher.desktop is 
already in xapp-sn-watcher package: 
https://packages.debian.org/sid/amd64/xapp-sn-watcher/filelist


file was moved latest time in 2.4.2-1 (from xapp package) and first time 
in 2.2.6-1 (from libxapp1)


I suppose the issue you spotted is related to old conffile moved (in 
case your system was upgraded and was installed intially with version < 
2.2.6-1, where there was the first move from libxapp1), relating to it 
there is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983441 but is 
blocked by another bug in dpkg (that I'm unable to fix it) and as wrote 
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886389 is 
impossible use rm_conffile in case of move from one binary package to 
another of the same source or the file of the new package will be 
removed broking it


since the unexpected case you spotted is more that simply "mark as 
obsolete" I think is good to reply on bug #886389 that now seems 
considered minor and without progress




OpenPGP_signature
Description: OpenPGP digital signature


Bug#1053241: glibc: please apply upstream patch to fix slow fstat

2023-09-29 Thread Fabio Pedretti
Package: glibc
Version: 2.36-9+deb12u1
Severity: normal
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

glibc uses a slow version of fstat. Details are documented
here: https://lwn.net/Articles/944214/

A patch to fix this was merged in glibc:
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=551101e8240b7514fc646d1722f8b79c90362b8f

The patch applies cleanly and builds fine also on bookworm glibc.
Please consider apply it to fix slow fstat.

Thanks.



Bug#1052453: rust-bindgen-cli: Build error: Unknown section 'FIXME-IN-THE-SOURCE-SECTION'

2023-09-22 Thread Fabio Pedretti
Package: rust-bindgen-cli
Version: 0.66.1-3
Severity: normal
Tags: ftbfs
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

trying to build the package on Ubuntu, the package get rejected with
this error:

Unknown section 'FIXME-IN-THE-SOURCE-SECTION'

Thanks.



Bug#842335: ITP: mint-themes -- A collection of Mint themes

2023-09-13 Thread Fabio Fantoni

Il 13/09/2023 23:05, Arturo Ingenito ha scritto:
Thank you for adding mint-themes but I think we need another package 
to fit full mint theme.
I noticed mint-themes doesn't cutomize the cursor which is specified 
by mint-cursor-themes.

Could you add this?
https://github.com/linuxmint/mint-cursor-themes


Hi, the main cursor theme (bibata) was already packages in debian (not 
by cinnamon team) and conflict with this package, as specified in 
https://github.com/linuxmint/mint-cursor-themes/issues/2


at the moment I don't see any particular interest in bringing the mint 
cursor package to Debian (modified by removing the already present and 
conflicting half)


I would like to complete the mint-theme but unfortunately it is blocked 
by mint-x-icons on which I have licensing doubts and icon problems with 
trademarks 
(https://github.com/linuxmint/mint-x-icons/issues/198#issuecomment-1598702838)


there was no news and I no longer invested time in it

the license probably can be acceptable the GPL-3, same of from was 
forked but about check and doing a patch that remove all icons with 
trademarks issue may require big time (I'm not sure is ok only the list 
from faenza theme)


but any help to proceed would be welcome if anyone wanted



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1051210: cinnamon: bug in cinnamon-settings

2023-09-04 Thread Fabio Fantoni

Il 04/09/2023 16:04, Walter Valenti ha scritto:

Package: cinnamon
Version: 5.6.8-1
Severity: minor
X-Debbugs-Cc: debian-cinna...@lists.debian.org, waltervale...@yahoo.it


In System Settings -> Appareance -> Backgrouds, in not possible change the
background image.
This the error for example:



Failed to convert /usr/share/desktop-base/joy-inksplat-
theme/wallpaper/contents/images/3840x2160.svg: module 'PIL.Image' has no
attribute 'ANTIALIAS'

Hi, thanks for report, I already saw it time ago at the merge of the fix 
upstream: 
https://github.com/linuxmint/cinnamon/commit/fce9aad1ebb290802dc550e8dae6344dddf9dec1


I was waiting for new upstream bugfix release but if will not be 
released I'll add that patch in debian/patches on next cinnamon upload 
to experimental or unstable




OpenPGP_signature
Description: OpenPGP digital signature


Bug#1050664: firehol: please install contrib/ipset-apply.sh into firehol-tools

2023-08-27 Thread Fabio Pedretti
Package: firehol
Version: 3.1.7+ds-2.1
Severity: wishlist
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

firehol source package has 2 tools in the contrib dir: dnsbl-ipset.sh
and ipset-apply.sh.
The latter however is not installed. Please install also ipset-apply.sh
since it is a useful tool.

Thanks.



Bug#1042147: virt-manager: FTBFS: AssertionError: Conversion outputs did not match.

2023-08-27 Thread Fabio Fantoni
after saw the autoremove from testing on 08 September for an RC and 
nobody working on it I did a search upstream for the fix, was not 
present so I created the patch and forwarded upstream 
(https://github.com/virt-manager/virt-manager/pull/559). After I created 
an MR: 
https://salsa.debian.org/libvirt-team/virt-manager/-/merge_requests/16


can someone merge and release new build before the autoremove from 
testing please?




OpenPGP_signature
Description: OpenPGP digital signature


Bug#1050151: RM: gnome-shell-extension-sound-device-chooser -- ROM; unmaintained, not compatible with GNOME 43+

2023-08-20 Thread Fabio A. De Muzio Tobich

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: 1018...@bugs.debian.org, ftob...@debian.org

--
⢀⣴⠾⠻⢶⣦
⣾⠁⢠⠒⠀⣿⡁   Fabio Augusto De Muzio Tobich
⢿⡄⠘⠷⠚⠋⠀   9730 4066 E5AE FAC2 2683  D03D 4FB3 B4D3 7EF6 3B2E
⠈⠳⣄


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#943865: src:mesa: Please build Mesa SWR rasterizer on amd64 and i386

2023-08-14 Thread Fabio Pedretti
block 943865 with 1006202
thanks

SWR was removed from mesa, but it is still available in mesa-amber



Bug#1042508: RFS: xdg-desktop-portal-xapp/1.0.3-1 [ITP] -- Xapp's Cinnamon, MATE and Xfce backends for xdg-desktop-portal

2023-07-29 Thread Fabio Fantoni

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "xdg-desktop-portal-xapp":

 * Package name : xdg-desktop-portal-xapp
   Version  : 1.0.3-1
   Upstream contact : Linux Mint Project 
 * URL  : https://github.com/linuxmint/xdg-desktop-portal-xapp
 * License  : LGPL-2.1+, LGPL-2+
 * Vcs  : 
https://salsa.debian.org/cinnamon-team/xdg-desktop-portal-xapp

   Section  : gnome

The source builds the following binary packages:

  xdg-desktop-portal-xapp - Xapp's Cinnamon, MATE and Xfce backends for 
xdg-desktop-portal


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


  https://mentors.debian.net/package/xdg-desktop-portal-xapp/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/x/xdg-desktop-portal-xapp/xdg-desktop-portal-xapp_1.0.3-1.dsc


First upload was rejected for d/copyright to fix, I didn't check good 
keeping near the d/copyright of the package from xdg-desktop-portal-xapp 
was forked, now I hope to do it right after a good check.



Changes for the initial release:

 xdg-desktop-portal-xapp (1.0.3-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #1038946)

Regards,
--
  Fabio Fantoni



Bug#1041243: mesa: please remove control file, as control.in is present

2023-07-25 Thread Fabio Pedretti
Il Mar 25 Lug 2023, 09:54 Timo Aaltonen  ha scritto:

> On 16.7.2023 15.30, Fabio Pedretti wrote:
> > Source: mesa
> > Version: 22.3.6-1+deb12u1
> > Severity: normal
> > X-Debbugs-Cc: pedretti.fa...@gmail.com
> >
> > Please remove control file in git, since there is already control.in,
> and
> > control is automatically generated during build.
>
> regeneration doesn't work when d/control is removed
>

Mmm, I didn't tryed, but there are other .in files (libglx-mesa0.links.in
and libosmesa6.links.in) without the generated file... maybe control is
special.

>


Bug#1023205: bullseye-pu: package memtest86+/6.00-1

2023-07-23 Thread Fabio Fantoni

Il 23/07/2023 14:50, Felix Zielcke ha scritto:

(Adding Fabio)

Am Sonntag, dem 23.07.2023 um 13:42 +0100 schrieb Jonathan Wiltshire:

Control: tag -1 moreinfo

Hi,

On Mon, Oct 31, 2022 at 05:38:07PM +0100, Felix Zielcke wrote:

memtest86+ 5.01-3.1 in stable is very old and doestn't run
correctly
on recent hardware.

In the meantime I see there has been a backport of 6 to bullseye-
backports.
Is it still the best course of action to remove 5.01-3.1 from stable,
or
does it work well enough on old hardware to be worth keeping?

Thanks,


Hi,

actually now I think we could just keep it in bullseye. Anyone with
recent hardware could get it from backports and probable also will (if
not have already) upgrade to bookworm.
Or what do you think Fabio? Should the old memtest still be removed
from oldstable?

I at least didn't get any complains about the old version, since I
became a co-maintainer of memtest86+


Hi, old version doesn't work on many hardwares but deleting memtest86+ 
from oldstable repo doesn't seem like a good thing to me, rather now 
that there is a new stable I suppose oldstable is much less used and 
relevant and could stay that way; because I suppose that almost all 
sysadmin/users now have the new iso and in case they need to test the 
old systems without being able to load the iso, they install the new 
memtest86+ version from backports before. or am I wrong?




OpenPGP_signature
Description: OpenPGP digital signature


Bug#1009027: mesa: Please enable these new drivers and features available since mesa 22

2023-07-16 Thread Fabio Pedretti
> There is also the VULKAN_DRIVERS virtio-experimental , I don't know
> however if it's ready for use (archlinux ships it
> https://bbs.archlinux.org/viewtopic.php?id=265471 ).

Since 23.2 virtio-experimental was renamed upstream to virtio and is
no longer considered experimental:
https://cgit.freedesktop.org/mesa/mesa/commit?id=7d76038712ea099424e906d8a4c19ad5c932f7e3
https://cgit.freedesktop.org/mesa/mesa/commit/?id=bdc82f52d7d16b05a9922534be00fba39e3a1c5b



Bug#1041243: mesa: please remove control file, as control.in is present

2023-07-16 Thread Fabio Pedretti
Source: mesa
Version: 22.3.6-1+deb12u1
Severity: normal
X-Debbugs-Cc: pedretti.fa...@gmail.com

Please remove control file in git, since there is already control.in, and
control is automatically generated during build.



Bug#1017619: nautilus-wipe not present in bookworm

2023-07-15 Thread Fabio Follin
Dear nautilus-wipe maintainers and uploaders,

I recently upgraded my system to debian 12 and I was surprised that
nautilus-wipe was not present in bookworm and not even in testing.

It is planned to add it back in testing from sid and maybe also add it
to bookworm-backports?

Thanks a lot for your work.
Best regards,
Fabio Follin



Bug#1038946: please add a long description

2023-06-26 Thread Fabio Fantoni

Il 26/06/2023 12:30, Tomas Pospisek ha scritto:
Instead of solely having a short description that says "$FOO is a $BAZ 
for $BAR" where it's not immediately clear without particular 
knowledge what $FOO and $BAR are, please add a short text, that 
explains what $FOO and $BAR actually do. Something like:


"Xapp is an application that does . xdg-desktop-portal allows you
 to do this and that. This package adds infrastructure to support Xapp 
via

 xdg-desktop-portal on Cinnamon, MATE and Xfce."

Thanks,
*t


Thanks for reply, long description was already added to git of the 
package: 
https://salsa.debian.org/cinnamon-team/xdg-desktop-portal-xapp/-/blob/debian/latest/debian/control


Description: Xapp's Cinnamon, MATE and Xfce backends for 
xdg-desktop-portal
xdg-desktop-portal-xapp provides an implementation for the 
desktop-agnostic

xdg-desktop-portal service for Cinnamon, MATE and Xfce.
This allows sandboxed applications to request services and information 
from

outside the sandbox in the MATE, Xfce and Cinnamon environments.
I taken as base the upstream one (for mint packages) and tried to 
improve it but suggestions on further improvements are appreciated




OpenPGP_signature
Description: OpenPGP digital signature


Bug#1038946: ITP: xdg-desktop-portal-xapp -- Xapp's Cinnamon, MATE and Xfce backends for xdg-desktop-portal

2023-06-23 Thread Fabio Fantoni

Package: wnpp
Severity: wishlist
Owner: Fabio Fantoni 
X-Debbugs-Cc: debian-de...@lists.debian.org, fantonifa...@tiscali.it

* Package name    : xdg-desktop-portal-xapp
  Version : 1.0.1
  Upstream Contact: Linux Mint Project 
* URL : https://github.com/linuxmint/xdg-desktop-portal-xapp
* License : GPL-2+ and LGPL-2+ and LGPL-2.1+
  Description : Xapp's Cinnamon, MATE and Xfce backends for 
xdg-desktop-portal



I'll package it under the debian cinnamon team:
https://salsa.debian.org/cinnamon-team/xdg-desktop-portal-xapp



Bug#1038630: cinnamon: depends on obsolete policykit-1-gnome

2023-06-22 Thread Fabio Fantoni

Control: tags -1 - fixed-upstream

the upstream bug linked was closed 2 years ago when upstream had chosen 
to continue to use policykit-1-gnome "as solution" but now that 
policykit-1-gnome will be remove can't be considered as "fixed upstream"




OpenPGP_signature
Description: OpenPGP digital signature


Bug#1037940: port-to-libsoup3.patch looks bad

2023-06-17 Thread Fabio Fantoni

Il 14/06/2023 16:46, Michael Catanzaro ha scritto:

Package: libtimezonemap1
Version: 0.4.6-5
X-Debbugs-CC: itzswirlz2...@outlook.com

Hi maintainers, somebody noticed that you had ported libtimezonemap to 
libsoup 3 and I was asked to look into whether the patch would be good 
for Fedora or upstream. I noticed several problems. (1) The patch 
casts a const char* to a GUri*. That's not going to work. (2) It also 
frees a GAsyncResult using an incorrect free function, g_free() when 
it should be g_object_unref(). (3) It casts a SoupMessage to a 
SoupSession, which won't work. (4) The call to 
soup_session_get_async_result_message() looks like it wouldn't do 
anything even if it was called with a SoupSession rather than a 
SoupMessage.


I'm excited to see more libsoup 3 porting, but I recommend dropping 
this patch. I see it has not yet graduated from experimental to sid, 
so that's good.


Thanks for report, I hadn't fully test soup3 porting but only build, 
install of package and one fast check to one thing that should use 
libtimezonemap before the upload to experimental.


I can't try to fix the soup3 patch soon so I'll drop it for now for do 
an upload to unstable with crash fix for glib 2.76 before its migration 
to unstable.


If Joshua or somebody will do a fixed patch for soup3 I'll do another 
upload to experimental.




OpenPGP_signature
Description: OpenPGP digital signature


Bug#1036970: 0ad: third party library (mbedtls) needs to be updated

2023-06-01 Thread Fabio Pedretti
forwarded 1036970 https://trac.wildfiregames.com/ticket/6816
thanks



Bug#1035998: unblock: cinnamon-settings-daemon/5.6.2-2

2023-05-12 Thread Fabio Fantoni

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: cinnamon-settings-dae...@packages.debian.org, 
fantonifa...@tiscali.it

Control: affects -1 + src:cinnamon-settings-daemon

Please unblock package cinnamon-settings-daemon

5.6.2-2 Remove broken symlinks to csd-locate-pointer and
csd-list-wacom that was removed in a previous upstream version
but I missed to remove also symlinks in packaging.

I think is good to have in bookworm.


[ Risks ]
I consider the risk of regression very small

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock cinnamon-settings-daemon/5.6.2-2diff --git a/debian/changelog b/debian/changelog
index f843ec7..1e1e385 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+cinnamon-settings-daemon (5.6.2-2) unstable; urgency=medium
+
+  * Remove broken symlinks to csd-locate-pointer and csd-list-wacom
+Thanks to Andreas Beckmann (Closes: #1035860)
+
+ -- Fabio Fantoni   Wed, 10 May 2023 22:15:56 +0200
+
 cinnamon-settings-daemon (5.6.2-1) unstable; urgency=medium
 
   * New upstream bugfix version 5.6.2
diff --git a/debian/cinnamon-settings-daemon.links 
b/debian/cinnamon-settings-daemon.links
index a4091cb..bb49c47 100644
--- a/debian/cinnamon-settings-daemon.links
+++ b/debian/cinnamon-settings-daemon.links
@@ -8,7 +8,6 @@ 
usr/lib/${DEB_HOST_MULTIARCH}/cinnamon-settings-daemon/csd-datetime-mechanism us
 usr/lib/${DEB_HOST_MULTIARCH}/cinnamon-settings-daemon/csd-housekeeping 
usr/bin/csd-housekeeping
 usr/lib/${DEB_HOST_MULTIARCH}/cinnamon-settings-daemon/csd-input-helper 
usr/bin/csd-input-helper
 usr/lib/${DEB_HOST_MULTIARCH}/cinnamon-settings-daemon/csd-keyboard 
usr/bin/csd-keyboard
-usr/lib/${DEB_HOST_MULTIARCH}/cinnamon-settings-daemon/csd-locate-pointer 
usr/bin/csd-locate-pointer
 usr/lib/${DEB_HOST_MULTIARCH}/cinnamon-settings-daemon/csd-media-keys 
usr/bin/csd-media-keys
 usr/lib/${DEB_HOST_MULTIARCH}/cinnamon-settings-daemon/csd-power 
usr/bin/csd-power
 usr/lib/${DEB_HOST_MULTIARCH}/cinnamon-settings-daemon/csd-printer 
usr/bin/csd-printer
diff --git a/debian/rules b/debian/rules
index 2d8df78..4db072e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -20,8 +20,7 @@ override_dh_link:
dh_link
 ifeq ($(DEB_HOST_ARCH_OS),linux)
 ifneq (${DEB_HOST_ARCH},s390x)
-   dh_link -p cinnamon-settings-daemon 
usr/lib/$(DEB_HOST_MULTIARCH)/cinnamon-settings-daemon/csd-list-wacom 
usr/bin/csd-list-wacom \
-   usr/lib/$(DEB_HOST_MULTIARCH)/cinnamon-settings-daemon/csd-wacom 
usr/bin/csd-wacom
+   dh_link -p cinnamon-settings-daemon 
usr/lib/$(DEB_HOST_MULTIARCH)/cinnamon-settings-daemon/csd-wacom 
usr/bin/csd-wacom
 endif
 endif
 


Bug#1035744: memtest86+: new upstream version

2023-05-08 Thread Fabio Fantoni

Il 08/05/2023 17:22, Christoph Anton Mitterer ha scritto:

Package: memtest86+
Version: 6.10-4
Severity: wishlist

Hey.

6.20 is out :-)

Cheers,
Chris.


Hi, Felix Zielcke already uploaded 6.20-1 into experimental, the new 
version for bookworm is too late, there is the "hard freeze" and I 
suppose Felix uploaded to experimental instead unstable to make possible 
an urgent fixes upload for bookworm if will be needed, even if I suppose 
there is very low probability to spot RC bugs on 6.10-4




OpenPGP_signature
Description: OpenPGP digital signature


Bug#1034162: unblock: cinnamon/5.6.8-1

2023-04-10 Thread Fabio Fantoni

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: cinna...@packages.debian.org, fantonifa...@tiscali.it
Control: affects -1 + src:cinnamon

Please unblock package cinnamon

5.6.8-1 include a new bugfix release with some fixes:
- grouped-window-list: Make appGroup's flashButton sane, fix invalid 
source id.

- cinnamon-screenshot.c: Disable unredirection when taking a screenshot.
- remove unused import cairo
- cs_themes: load theme thumbnail from XDG_DATA_DIRS
- gwl: Fix typo.
- sound applet: Clear the source ID in Seeker._timerCallback().
- window-list: Fix signal name for tile notifications.
- overrides.js: Silently fail to install polyfills.

One fix seems a "big patch" 
(https://github.com/linuxmint/cinnamon/commit/fcffd73eace934c817db394d347705f81e564f3c)
but solves cinnamon crash in some cases doing screenshot 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032912)


No regression found or reported, I think is good to have in bookworm.

[ Risks ]
I consider the risk of regression small

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock cinnamon/5.6.8-1
diff --git a/debian/changelog b/debian/changelog
index 6ca12b51a..8bd8d7d27 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cinnamon (5.6.8-1) unstable; urgency=medium
+
+  * New upstream bugfix version 5.6.8 (Closes: #1032912)
+
+ -- Fabio Fantoni   Sun, 19 Mar 2023 22:38:37 +0100
+
 cinnamon (5.6.7-1) unstable; urgency=medium
 
   * New upstream version 5.6.7
diff --git 
a/files/usr/share/cinnamon/applets/grouped-window-l...@cinnamon.org/appGroup.js 
b/files/usr/share/cinnamon/applets/grouped-window-l...@cinnamon.org/appGroup.js
index ef0a7e5b8..9ca6b37d5 100644
--- 
a/files/usr/share/cinnamon/applets/grouped-window-l...@cinnamon.org/appGroup.js
+++ 
b/files/usr/share/cinnamon/applets/grouped-window-l...@cinnamon.org/appGroup.js
@@ -1,6 +1,7 @@
 const Cinnamon = imports.gi.Cinnamon;
 const Meta = imports.gi.Meta;
 const Clutter = imports.gi.Clutter;
+const GLib = imports.gi.GLib;
 const St = imports.gi.St;
 const Main = imports.ui.main;
 const Tweener = imports.ui.tweener;
@@ -304,35 +305,40 @@ class AppGroup {
 if (this._needsAttention) return;
 
 this._needsAttention = true;
-let counter = 0;
-this.flashButton(counter);
+this.flashButton();
 }
 
-flashButton(counter) {
-if (!this._needsAttention || !this.actor) return;
+flashButton() {
+if (!this._needsAttention || !this.actor || this.flashTimer)
+return;
 
-// If the app was closed during a flash sequence, stop looping.
-if (!this.groupState.groupReady && this.groupState.isFavoriteApp) {
-
this.actor.remove_style_class_name('grouped-window-list-item-demands-attention');
+if (!this.groupState.groupReady && this.groupState.isFavoriteApp)
 return;
-}
 
-this.actor.remove_style_pseudo_class('active');
-
this.actor.add_style_class_name('grouped-window-list-item-demands-attention');
-if (counter < FLASH_MAX_COUNT) {
-this.flashTimer = Mainloop.timeout_add(FLASH_INTERVAL, () => {
-if (this.actor && 
this.actor.has_style_class_name('grouped-window-list-item-demands-attention')) {
-
this.actor.remove_style_class_name('grouped-window-list-item-demands-attention');
-this.actor.add_style_pseudo_class('active');
-}
+let counter = 0;
+const sc = "grouped-window-list-item-demands-attention";
 
-this.flashTimer = Mainloop.timeout_add(FLASH_INTERVAL, () => {
-this.flashButton(++counter);
-});
-});
-} else {
-this.flashTimer = 0;
-}
+this.flashTimer = Mainloop.timeout_add(FLASH_INTERVAL, () => {
+if (!this._needsAttention) {
+this.flashTimer = 0;
+return GLib.SOURCE_REMOVE;
+}
+
+if (this.actor.has_style_class_name(sc)) {
+this.actor.add_style_class_name("active");
+this.actor.remove_style_class_name(sc);
+}
+else {
+this.actor.remove_style_class_name("active")
+this.actor.add_style_class_name(sc);
+}
+
+const continueFlashing = (counter++ < FLASH_MAX_COUNT);
+if (!continueFlashing) {
+this.flashTimer = 0;
+}
+return continueFlashing;
+});
 }
 
 getPreferredWidth(actor, forHeight, alloc) {
@@ -597,9 +603,7 @@ class AppGroup {
 if (hasFocus) {
 this.listState.trigger('u

Bug#1034161: unblock: muffin/5.6.4-1

2023-04-10 Thread Fabio Fantoni

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: muf...@packages.debian.org, fantonifa...@tiscali.it
Control: affects -1 + src:muffin

Please unblock package muffin

5.6.4-1 include a new bugfix release with some fixes:
- meta-gpu-xrandr: Account for the current user text scale factor when 
calculating the crtc scale based on Xft.dpi.

- window.c: Allow meta_window_get_xwindow() to be used with introspection.
- window.c: Restore property notify for the tile mode property.
- place.c: Add missing import.
- display.c: Make meta_display_get_pointer_window() available to 
cinnamon again.

- clutter-text.c: Remove redundant clutter_text_set_buffer call in finalize.

The symbol added is not a new function but only export of existant function,
making it available again to cinnamon.

I also added replace of libgdk-pixbuf2.0-dev build-dep. with 
libgdk-pixbuf-2.0-dev,
libgdk-pixbuf2.0-dev is a transition metapackage from bullseye so should 
don't

be a risk FWIK.

No regression found or reported, I think is good to have in bookworm.

[ Risks ]
I consider the risk of regression small

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock muffin/5.6.4-1
diff --git a/clutter/clutter/clutter-text.c b/clutter/clutter/clutter-text.c
index 3da410f..e18ed4c 100644
--- a/clutter/clutter/clutter-text.c
+++ b/clutter/clutter/clutter-text.c
@@ -1807,7 +1807,6 @@ clutter_text_finalize (GObject *gobject)
 
   clutter_text_dirty_paint_volume (self);
 
-  clutter_text_set_buffer (self, NULL);
   g_free (priv->font_name);
 
   g_clear_object (>input_focus);
diff --git a/debian/changelog b/debian/changelog
index 88556cf..e435e28 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+muffin (5.6.4-1) unstable; urgency=medium
+
+  * New upstream bugfix version 5.6.4
+  * Replace libgdk-pixbuf2.0-dev build-dep. with libgdk-pixbuf-2.0-dev
+  * Update symbols
+
+ -- Fabio Fantoni   Sun, 19 Mar 2023 22:33:27 +0100
+
 muffin (5.6.3-1) unstable; urgency=medium
 
   * New upstream version 5.6.3
diff --git a/debian/control b/debian/control
index 130f0e7..0626f50 100644
--- a/debian/control
+++ b/debian/control
@@ -149,7 +149,7 @@ Depends: gir1.2-meta-muffin-0.0 (= ${binary:Version}),
  libcinnamon-desktop-dev (>= 5.6),
  libdrm-dev,
  libegl1-mesa-dev,
- libgdk-pixbuf2.0-dev,
+ libgdk-pixbuf-2.0-dev,
  libgles2-mesa-dev | libgles2-dev,
  libglib2.0-dev,
  libgraphene-1.0-dev (>= 1.9.3),
diff --git a/debian/libmuffin0.symbols b/debian/libmuffin0.symbols
index 2a1f2eb..279e3ed 100644
--- a/debian/libmuffin0.symbols
+++ b/debian/libmuffin0.symbols
@@ -2136,6 +2136,7 @@ libmuffin.so.0 libmuffin0 #MINVER#
  meta_display_get_monitor_scale@Base 5.4.1
  meta_display_get_n_monitors@Base 5.4.1
  meta_display_get_pad_action_label@Base 5.4.1
+ meta_display_get_pointer_window@Base 5.6.4
  meta_display_get_primary_monitor@Base 5.4.1
  meta_display_get_selection@Base 5.4.1
  meta_display_get_size@Base 5.4.1
diff --git a/meson.build b/meson.build
index 63b5fad..d4b4590 100644
--- a/meson.build
+++ b/meson.build
@@ -1,5 +1,5 @@
 project('muffin', 'c',
-  version: '5.6.3',
+  version: '5.6.4',
   meson_version: '>= 0.50.0',
   license: 'GPLv2+'
 )
diff --git a/src/backends/meta-settings-private.h 
b/src/backends/meta-settings-private.h
index a7241ce..8965e1c 100644
--- a/src/backends/meta-settings-private.h
+++ b/src/backends/meta-settings-private.h
@@ -58,6 +58,8 @@ void meta_settings_update_ui_scaling_factor (MetaSettings 
*settings);
 gboolean meta_settings_get_global_scaling_factor (MetaSettings *settings,
   int  *scaing_factor);
 
+double meta_settings_get_font_scaling_factor (MetaSettings *settings);
+
 META_EXPORT_TEST
 gboolean meta_settings_is_experimental_feature_enabled (MetaSettings   
*settings,
 
MetaExperimentalFeature feature);
diff --git a/src/backends/meta-settings.c b/src/backends/meta-settings.c
index e544d65..f4a692f 100644
--- a/src/backends/meta-settings.c
+++ b/src/backends/meta-settings.c
@@ -223,6 +223,12 @@ meta_settings_update_font_dpi (MetaSettings *settings)
 g_signal_emit (settings, signals[FONT_DPI_CHANGED], 0);
 }
 
+double
+meta_settings_get_font_scaling_factor(MetaSettings *settings)
+{
+return g_settings_get_double (settings->interface_settings, 
"text-scaling-factor");
+}
+
 int
 meta_settings_get_font_dpi (MetaSettings *settings)
 {
diff --git a/src/backends/x11/meta-gpu-xrandr.c 
b/src/backends/x11/meta-gpu-xrandr.c
index 65a3c30..f2563e6 100644
--- a/src/backends/x11/meta-gpu-xrandr.c
+++ b/src/backends/x11/meta-gpu-xrandr.c
@@ -98,6 +98,10 @@ static int
 get_current_dpi_sca

Bug#1033830: unblock: nemo/5.6.4-1

2023-04-02 Thread Fabio Fantoni

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: n...@packages.debian.org, fantonifa...@tiscali.it
Control: affects -1 + src:nemo

Please unblock package nemo

5.6.4-1 include a new bugfix release with some fixes:
- nemo-view-dnd.c: Fix the check for a web link's title, and use the url 
if it's missing.
- nemo-mime-actions.c: Prioritize an http link to open in a browser, 
regardless of the mimetype of the link's target.

- Fix for List View thumbnail scaling at HiDPI
- list-view: Scale the thumbnail correctly when applying emblems, and 
fix the emblem sanity checks everywhere.
- file info: Use generic methods for attributes that aren't guaranteed 
to be supported by the filesystem.


No regression found or reported, I think is good to have in bookworm.

[ Risks ]
I consider the risk of regression small

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock nemo/5.6.4-1
diff --git a/debian/changelog b/debian/changelog
index e59ea892..29baa503 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+nemo (5.6.4-1) unstable; urgency=medium
+
+  * New upstream bugfix version 5.6.4
+
+ -- Fabio Fantoni   Sun, 19 Mar 2023 22:36:15 +0100
+
 nemo (5.6.3-1) unstable; urgency=medium
 
   * New upstream version 5.6.3
diff --git a/libnemo-private/nemo-directory-async.c 
b/libnemo-private/nemo-directory-async.c
index 3a892739..b4eb02f3 100644
--- a/libnemo-private/nemo-directory-async.c
+++ b/libnemo-private/nemo-directory-async.c
@@ -824,6 +824,7 @@ static gboolean
 should_skip_file (NemoDirectory *directory, GFileInfo *info)
 {
static gboolean show_hidden_files_changed_callback_installed = FALSE;
+gboolean is_hidden;
 
/* Add the callback once for the life of our process */
if (!show_hidden_files_changed_callback_installed) {
@@ -838,13 +839,14 @@ should_skip_file (NemoDirectory *directory, GFileInfo 
*info)
show_hidden_files_changed_callback (NULL);
}
 
-   if (!show_hidden_files &&
-   (g_file_info_get_is_hidden (info) ||
-g_file_info_get_is_backup (info))) {
-   return TRUE;
-   }
+is_hidden = g_file_info_get_attribute_boolean (info, 
G_FILE_ATTRIBUTE_STANDARD_IS_HIDDEN) ||
+g_file_info_get_attribute_boolean (info, 
G_FILE_ATTRIBUTE_STANDARD_IS_BACKUP);
 
-   return FALSE;
+if (!show_hidden_files && is_hidden) {
+return TRUE;
+}
+
+return FALSE;
 }
 
 static void
@@ -915,7 +917,8 @@ dequeue_pending_idle_callback (gpointer callback_data)
dir_load_state->load_file_count += 1;
 
/* Add the MIME type to the set. */
-   mimetype = g_file_info_get_content_type (file_info);
+mimetype = g_file_info_get_attribute_string (file_info, 
G_FILE_ATTRIBUTE_STANDARD_CONTENT_TYPE);
+
if (mimetype != NULL) {
istr_set_insert 
(dir_load_state->load_mime_list_hash,
 mimetype);
@@ -2961,7 +2964,8 @@ mime_list_one (MimeListState *state,
return;
}
 
-   mime_type = g_file_info_get_content_type (info);
+mime_type = g_file_info_get_attribute_string (info, 
G_FILE_ATTRIBUTE_STANDARD_CONTENT_TYPE);
+
if (mime_type != NULL) {
istr_set_insert (state->mime_list_hash, mime_type);
}
diff --git a/libnemo-private/nemo-file.c b/libnemo-private/nemo-file.c
index 629feedb..ba8a8555 100644
--- a/libnemo-private/nemo-file.c
+++ b/libnemo-private/nemo-file.c
@@ -2274,6 +2274,7 @@ update_info_internal (NemoFile *file,
const char *trash_orig_path;
const char *group, *owner, *owner_real;
gboolean free_owner, free_group;
+const char *edit_name;
 
if (file->details->is_gone) {
return FALSE;
@@ -2304,9 +2305,11 @@ update_info_internal (NemoFile *file,
}
file->details->got_file_info = TRUE;
 
+edit_name = g_file_info_get_attribute_string (info, 
G_FILE_ATTRIBUTE_STANDARD_EDIT_NAME);
+
changed |= nemo_file_set_display_name (file,
  g_file_info_get_display_name 
(info),
- g_file_info_get_edit_name 
(info),
+ edit_name,
  FALSE);
 
file_type = g_file_info_get_file_type (info);
@@ -2339,13 +2342,15 @@ update_info_internal (NemoFile *file,
}
}
 
-   is_symlink = g_file_info_get_is_symlink (info);
+is_symlink = g_file_info_get_attribute_boolean (info, 
G_FILE_ATTRIBUTE_STANDARD_IS_SYMLINK);
if (fi

Bug#1033829: RFS: backintime/1.3.3-4.1 [NMU] -- simple backup/snapshot system (graphical interface)

2023-04-02 Thread Fabio Fantoni

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : backintime
   Version  : 1.3.3-4.1
 * URL  : https://github.com/bit-team/backintime
 * License  : GPL-2+, GFDL-NIV-1.1+
 * Vcs  : https://salsa.debian.org/jmw/pkg-backintime
   Section  : utils

One important bug (#998105) was fixed upstream one month ago,
three weeks ago Sven Geuer prepared an MR and tested it,
2 weeks ago I also did fast test and pushed the commit,
no reply from maintaner, I also tried to sent him a mail
without replies, I suppose is busy recently.
I think is good do a new upload for this and after try to
request an unblock request for debian 12.
Can someone upload this MNU with delay of 2-3 days please?
(to still give to maintainer the possibility for do normal upload)

The source builds the following binary packages:

  backintime-common - simple backup/snapshot system (common files)
  backintime-qt - simple backup/snapshot system (graphical interface)

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/backintime/backintime_1.3.3-4.1.dsc

Changes since the last upload:

 backintime (1.3.3-4.1) unstable; urgency=medium
 .
   [ Sven Geuer ]
   * Add ChainerBackend keyring support to fix password lookup error
 (Closes: #998105)
 .
   [ Fabio Fantoni ]
   * Non-maintainer upload.

Regards,
--
  Fabio Fantoni



Bug#998105: backintime-qt: Fails to access the keyring with python3-keyring 23.2.0-1

2023-03-29 Thread Fabio Fantoni

Il 29/03/2023 10:11, c.bu...@posteo.jp ha scritto:

Do I see it correct that the commit was done but not yet uploaded?

In result there should be a 1.3.3-5, right?

 There is still no reply  from Jonathan Wiltshire, I also sent him a 
mail some days ago.


I'll probably try to do a NMU in the weekend



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1033612: unblock: cinnamon-settings-daemon/5.6.2-1

2023-03-28 Thread Fabio Fantoni

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: cinnamon-settings-dae...@packages.debian.org, 
fantonifa...@tiscali.it

Control: affects -1 + src:cinnamon-settings-daemon

Please unblock package cinnamon-settings-daemon

5.6.2-1 include a new bugfix release with 2 fixes:
- xsettings: Round the Xft.dpi setting to an integer
- power: Fix free order

I also added replace of libfontconfig1-dev build-dep. with 
libfontconfig-dev,

libfontconfig1-dev is a transition metapackage from bullseye so should don't
be a risk FWIK.

No regression found or reported, I think is good to have in bookworm.

[ Risks ]
I consider the risk of regression very small

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock cinnamon-settings-daemon/5.6.2-1
diff --git a/debian/changelog b/debian/changelog
index 170bcc6..f843ec7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+cinnamon-settings-daemon (5.6.2-1) unstable; urgency=medium
+
+  * New upstream bugfix version 5.6.2
+  * Replace libfontconfig1-dev build-dep. with libfontconfig-dev
+
+ -- Fabio Fantoni   Sun, 19 Mar 2023 22:29:11 +0100
+
 cinnamon-settings-daemon (5.6.1-1) unstable; urgency=medium
 
   [ Debian Janitor ]
diff --git a/debian/control b/debian/control
index a8ec4c0..1ca4a36 100644
--- a/debian/control
+++ b/debian/control
@@ -18,7 +18,7 @@ Build-Depends:
  libcinnamon-desktop-dev (>= 5.6.1~),
  libcolord-dev,
  libcups2-dev,
- libfontconfig1-dev,
+ libfontconfig-dev,
  libglib2.0-dev,
  libgnomekbd-dev,
  libgtk-3-dev,
diff --git a/meson.build b/meson.build
index ab48440..108d7e5 100644
--- a/meson.build
+++ b/meson.build
@@ -1,4 +1,4 @@
-project('cinnamon-settings-daemon', 'c', version: '5.6.1', meson_version: '>= 
0.47')
+project('cinnamon-settings-daemon', 'c', version: '5.6.2', meson_version: '>= 
0.47')
 
 gnome = import('gnome')
 i18n = import('i18n')
diff --git a/plugins/power/gpm-idletime.c b/plugins/power/gpm-idletime.c
index 1a41a14..aaadb89 100644
--- a/plugins/power/gpm-idletime.c
+++ b/plugins/power/gpm-idletime.c
@@ -349,8 +349,8 @@ gpm_idletime_alarm_free (GpmIdletime *idletime,
alarm_item->xalarm);
 }
 g_object_unref (alarm_item->idletime);
-g_free (alarm_item);
 g_ptr_array_remove (idletime->priv->array, alarm_item);
+g_free (alarm_item);
 return TRUE;
 }
 
diff --git a/plugins/xsettings/csd-xsettings-manager.c 
b/plugins/xsettings/csd-xsettings-manager.c
index 30bbbed..07ab142 100644
--- a/plugins/xsettings/csd-xsettings-manager.c
+++ b/plugins/xsettings/csd-xsettings-manager.c
@@ -761,8 +761,8 @@ xft_settings_set_xresources (CinnamonSettingsXftSettings 
*settings)
 
 g_debug("xft_settings_set_xresources: orig res '%s'", add_string->str);
 
-update_property (add_string, "Xft.dpi",
-g_ascii_dtostr (dpibuf, sizeof (dpibuf), 
(double) settings->scaled_dpi / 1024.0));
+g_snprintf (dpibuf, sizeof (dpibuf), "%d", (int) (settings->scaled_dpi 
/ 1024.0 + 0.5));
+update_property (add_string, "Xft.dpi", dpibuf);
 update_property (add_string, "Xft.antialias",
 settings->antialias ? "1" : "0");
 update_property (add_string, "Xft.hinting",


Bug#1032912: cinnamon: Taking a screenshot of a full screen window crashes cinnamon

2023-03-14 Thread Fabio Fantoni

Il 13/03/2023 23:35, Konomi ha scritto:

Package: cinnamon
Version: 5.6.7-1
Severity: important
X-Debbugs-Cc: konomikit...@gmail.com

Dear Maintainer,

Taking a screenshot of a full screen window will crash the desktop. But only
when using the "Take a screenshot of a window" shortcut. I found a possibly
related bug report upstream [1]. But I'm unsure if it's the same bug.

[1] https://github.com/linuxmint/cinnamon/issues/11500


thanks for report, I did a fast test but I not reproduced it, I did a 
fast testing build adding an upstream patch mentioned in the issue you 
linked if you want try if solves the issue:


http://debomatic-amd64.debian.net/distribution#unstable/cinnamon/5.6.7-1.1



Steps to reproduce:

1. Run a full screen program such as a media player playing video or a game.
SuperTuxKart works well for example.
2. Press Alt+Print Screen (Take a screenshot of a window).
3. Cinnamon will crash and ask you to restart it.

Systemd journal:

Mar 14 09:33:29 debian kernel: pool-cinnamon[3285]: segfault at 1c ip
7f9a58610a99 sp 7f9a297f99d0 error 4 in
libcairo.so.2.11600.0[7f9a5856d000+cf000] likely on CPU 2 (core 0, socket 0)
Mar 14 09:33:29 debian kernel: Code: ef e8 5b d0 f5 ff bf 0b 00 00 00 e8 41 2d
f7 ff 89 03 eb e8 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 55 53 48 89 fb 48 83
ec 18 <8b> 6f 1c 64 48 8b 04 25 28 00 00 00 48 89 44 24 08 31 c0 85 ed 75

~/.xsession-errors:

** Message: 09:32:31.770: Unable to use GNOME Shell's builtin screenshot
interface, resorting to fallback X11.
Exception in thread Thread-2 (wait_for_process):
Traceback (most recent call last):
   File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
 self.run()
   File "/usr/lib/python3.11/threading.py", line 975, in run
 self._target(*self._args, **self._kwargs)
   File "/usr/bin/cinnamon-launcher", line 88, in wait_for_process
 os.execvp(FALLBACK_COMMAND, (FALLBACK_COMMAND,) + FALLBACK_ARGS)
   File "", line 574, in execvp
   File "", line 616, in _execvpe
   File "", line 607, in _execvpe
FileNotFoundError: [Errno 2] No such file or directory
None: no process found






OpenPGP_signature
Description: OpenPGP digital signature


Bug#1014058: closed by Marc Haber (Re: Bug#1014058: exim4-daemon-heavy: please compile with SPF and DMARC support)

2023-03-14 Thread Fabio Muzzi




Uhm... closed because it's a duplicate of  itself?


--
Fabio "Kurgan" Muzzi

- IZ4UFQ -

"Il massimo danno con il minimo sforzo"



Bug#1032851: mesa: FTBFS in dirty env if clang-14 is installed

2023-03-13 Thread Fabio Pedretti
On ubuntu jammy it breaks even with clang-15 installed, if
libclang1-14 is also installed, see:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8470



Bug#919234: ttls fails with tls 1.3, enabled by default

2023-03-07 Thread Fabio PEDRETTI
Hi, 3.2.1 currently in testing fixed most issues, however there is
still an issue preventing freeradius working with TLS 1.3.

The issue was reported upstream at:
https://github.com/FreeRADIUS/freeradius-server/issues/4878
and the commit fixing it is:
https://github.com/FreeRADIUS/freeradius-server/commit/0812bc1768cedc420adc03e86893d798fa19e872

That commit is already included in upstream 3.2.2.

So please consider upgrading to 3.2.2 (suggested, given this release
also fixes some other bugs), or apply the mentioned commit.

I updated the severity and forwarded bug reflecting this.

Thanks!

-- 


Informativa sulla Privacy: https://www.unibs.it/it/node/1452 




Bug#919234:

2023-03-07 Thread Fabio PEDRETTI
-- 
ing. Fabio Pedretti
Responsabile U.O.C. "Reti e Sicurezza Informatica"
Università degli Studi di Brescia
Via Valotti, 9 - 25121 Brescia
E-mail: fabio.pedre...@unibs.it

-- 


Informativa sulla Privacy: https://www.unibs.it/it/node/1452 
<https://www.unibs.it/it/node/1452>


Bug#1031086: piupart: fails in many packages for /etc/systemd/system/multi-user.target.wants/e2scrub_reap.service not owned that is not related to package tested

2023-02-11 Thread Fabio Fantoni

Package: piuparts
Version: 1.1.5
Severity: important
X-Debbugs-Cc: e2fspr...@packages.debian.org

Hi, I saw on many packages that piupart fails for error not related to 
the package tested, for example from 
https://piuparts.debian.org/stable2sid/fail/cinnamon-desktop-data_5.6.1-1.log



0m49.1s ERROR: FAIL: After purging files have disappeared:
   /etc/systemd/system/multi-user.target.wants/  not owned
   /etc/systemd/system/multi-user.target.wants/e2scrub_reap.service -> 
/lib/systemd/system/e2scrub_reap.service   not owned

I spotted the same error on piupart tests of other packages, for example:

https://piuparts.debian.org/stable2sid/fail/cinnamon-control-center-data_5.6.1-1.log
https://piuparts.debian.org/stable2sid/fail/muffin-common_5.6.3-1.log
https://piuparts.debian.org/stable2sid/fail/nemo-data_5.6.3-1.log
https://piuparts.debian.org/stable2sid/fail/xapps-common_2.4.2-3.log

Is possible solve this or ignore it to make piupart tests fails only 
with real issue with the package tested please?




OpenPGP_signature
Description: OpenPGP digital signature


Bug#254210: memtest86+: Memtest86+ incorrectly generates BadRAM-patch location information

2023-02-10 Thread Fabio Fantoni
I saw on upstream git history that there was some improvements related 
to badram output included in 6.10: 
https://github.com/memtest86plus/memtest86plus/pull/178


if someone will test it please tell me if sectors reported to set in 
badram works correctly in 6.10 and this bug can be closed




OpenPGP_signature
Description: OpenPGP digital signature


  1   2   3   4   5   6   7   8   9   10   >