Bug#1027359: [Pkg-electronics-devel] Bug#1027359: arduino-builder: FTBFS in bullseye (missing build-depends on tzdata)

2022-12-31 Thread Rock Storm
On Sat, 2022-12-31 at 15:15 +0100, Santiago Vila wrote:
> El 31/12/22 a las 14:33, Rock Storm escribió:
> > This is interesting because that test didn't fail before and we
> > didn't
> > need the tzdata package installed.
> 
> The tests always failed (in bullseye) in a chroot not containing
> tzdata.
>  From my own autobuilders:
> 
> Status: failed  arduino-builder_1.3.25-2_amd64-
> 20210129T121615.663Z
> Status: failed  arduino-builder_1.3.25-2_amd64-
> 20210129T132227.024Z
> 
> Part of the problem is that debootstrap installs tzdata by default
> even
> if it's not build-essential, but that's a bug in debootstrap:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837060
> 
> The other part of the problem is that people use debootstrap "as is",
> without asking it not to install tzdata, which produces non-minimal
> chroots in which packages which build ok are still not guaranteed
> to have their build-dependencies right.

This makes perfect sense. Thanks for the explanation.

Happy new year!

-- 
⢀⣤⣀⣼⣧⣀⣤⡀  Rock Storm
⣀⣿⣿⠟⠻⣿⣿⣀  Open Source Advocate
⠛⣿⣿⡄⢠⣿⣿⠛  https://github.com/rockstorm101
⠰⡿⠿⠁⠈⠿⢿⠆  C304 34B3 632C 464C 2FAF C741 0439 CF52 C968 32FD



Bug#1027359: [Pkg-electronics-devel] Bug#1027359: arduino-builder: FTBFS in bullseye (missing build-depends on tzdata)

2022-12-31 Thread Rock Storm
On Fri, 2022-12-30 at 19:00 +0100, Santiago Vila wrote:
> Note: I'm using the "patch" tag because there is an obvious fix
> (indicated in the subject).
> 
> [...]
> 
> If this is really a bug in one of the build-depends, please use
> reassign and affects, so that this is still visible in the BTS web
> page for this package.
> 

This is interesting because that test didn't fail before and we didn't
need the tzdata package installed. Which makes me think something has
changed in the archive that wasn't there before. I know the fix seems
simple but I wonder if there is something else going on. Something out
of the scope of arduino-builder?


Regards,

-- 
⢀⣤⣀⣼⣧⣀⣤⡀  Rock Storm
⣀⣿⣿⠟⠻⣿⣿⣀  Open Source Advocate
⠛⣿⣿⡄⢠⣿⣿⠛  https://github.com/rockstorm101
⠰⡿⠿⠁⠈⠿⢿⠆  C304 34B3 632C 464C 2FAF C741 0439 CF52 C968 32FD



Bug#981300: [Pkg-electronics-devel] Bug#981300: arduino-core-avr breaks arduino-mk

2021-01-28 Thread Rock Storm
Hi guys,

On Fri, Jan 29, 2021 at 07:00:32AM +0100, Carsten Schoenert wrote:
> Control: reassign -1 arduino-mk
> Control: rename -1 arduino-mk: needs to depend on arduino >=
> 2:1.8.13+dfsg1-1
> Control: severity -1 serious
>
> Hello Simon,
>
> thanks for reporting!
>
> Am 28.01.21 um 22:42 schrieb debi...@the-jedi.co.uk:
> > Package: arduino
> > Version: 1.8.13+dfsg1-1
> >
> > The recent rename of arduino-core to arduino-core-avr breaks the Depends
> > in arduino-mk:
> >
> > Depends:
> >   arduino-core (>= 1:1.0+dfsg-8),
>
> This is not fully correct, the old package arduino-core got melted into
> arduino, arduino-core-avr is a new dependency of arduino.
>
> arduino-mk needs to get adjusted, it needs to change this existing
> Depends into
>
>  arduino-core (>= 2:1.8.13+dfsg1-1)

This is interesting because '2:1.8.13+dfsg1-1' is already greater than
or equal to '1:1.0+dfsg-8'. So unless I'm missing something there the
current line on 'arduino-mk' control file should be fine.

I thought problems like these will not arise thanks to the line in the
current arduino control file that says:

Provides:
 arduino-core

Which is the bit I fear is not working properly. Maybe a version number
needs to be added to that line? I'll give that a try later today.


> > So doing a dist-upgrade and pulling in the new arduino, arduino-core-avr
> > etc; removes arduino-core and arduino-mk
>
> The removal of arduino-core is a thing what we want and need, the
> removal of ardunino-mk is grounded on the non updated correct adjusted
> new dependency. But maybe an updated arduino-mk is now also needed, I
> haven't looked into this yet.
>
> > Also why are you just now packaging arduino-builder when arduino-cli has
> > already replaced it?
> Yes, there is arduino-cli already out there. But we decided to stick for
> now with arduino-builder because arduino-cli brings in a lot of Go
> related new package dependencies which we wouldn't get into Debian
> before the final package freeze for Debian Bullseye. We wanted to have
> the option that it's really likely that we can get arduino and related
> packages ready for Bullseye.
> And that's also the reason why arduino-builder isn't the most resent
> version, this would also need at least three more new Go packages as
> build dependency.
>
> So it's not that we don't want to use arduino-cli, it was a weight out
> of what's possible in the given time span.

I just want to add here that, as stated by the Arduino Team
"[arduino-cli] is currently under active development: anything can
change at any time, API and UI must be considered unstable until we
release version 1.0.0." Which makes it, in my opinion, unsuitable to
released on Debian stable.

Regards,

--
Rock Storm
GPG KeyID: 4096R/C96832FD



Bug#939658: marked as pending in printrun

2020-12-13 Thread Rock Storm
Control: tag -1 pending

Hello,

Bug #939658 in printrun reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/3dprinting-team/printrun/-/commit/f0248afe80d939c2885586ae1d0229006724de06


d/copyright: Reorganise and update to latest code

Closes: #939658


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/939658



Bug#975899: deluge: Deluge refuses to start properly

2020-11-28 Thread Rock Storm
Package: deluge
Version: 2.0.3-3
Followup-For: Bug #975899
X-Debbugs-Cc: rockst...@gmx.com

Dear Maintainer,

I'm facing the exact same issue reported by Ara. However I don't think
the deluge is to blame for this since the latest revision of deluge
dates back to July 2020. Nonetheless, the package is completely
unusable at the moment.

I've tried the solutions proposed on Arch's forums [1]. No luck here.
Locale was already set "properly", python3-cairo was already installed
and python-gobject is uninstallable on my system.

[1]: https://bbs.archlinux.org/viewtopic.php?id=252811

I believe the one to blame is the python upgrade from 3.8 to 3.9.
However I've failed to prove it since trying to downgrade blows the
system out.

Please let me know if I can help in anyway to debug this further.

Regards,
Rock


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages deluge depends on:
ii  deluge-gtk  2.0.3-3
ii  python3 3.9.0-3
ii  python3-libtorrent  1.2.9-0.1

deluge recommends no packages.

deluge suggests no packages.

-- no debconf information

--
Rock Storm
GPG KeyID: 4096R/C96832FD



Bug#939658: Copyright Clarification Requested Upstream

2020-05-23 Thread Rock Storm
Hi all,

I'm sorry it took me this long to action on this. As an update, I've
requested copyright information to be clarified upstream on several PRs,
of which only one remains open [1]. Next upstream release will contain
the updated copyright info. So this bug is somehow blocked until that
happens unless somebody shows me another way forward.

[1]: https://github.com/kliment/Printrun/pull/1048

Regards,

-- 
Rock Storm
GPG KeyID: 4096R/C96832FD


signature.asc
Description: PGP signature


Bug#940215: Acknowledgement and Gratitude

2020-04-22 Thread Rock Storm
Hi Bouyan Yang,

Thanks a lot for taking care of this. I also appreciate the fact that
you prepared a PR. It's merged now I'm happy with all the changes. Thank
you for the upload. I don't know if it's possible but feel free to upload
straight away if you want.

Regards,

--
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD



Bug#934912: printrun: depends on cruft package.

2019-08-16 Thread Rock Storm
On Fri, Aug 16, 2019 at 02:36:27PM +0100, peter green wrote:
> printrun depends on python-cairosvg which is no longer built by the cairosvg 
> source package.
>
> If you want your package to stay around you probably need to migrate to 
> python 3.

Hi, thanks for reporting. The new version of Printrun, which uses python
3, is already prepared. It will hopefully be uploaded soon.

Cheers,

--
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD



Bug#917884: mate-dock-applet: Adding a new dock does nothing

2019-01-22 Thread Rock Storm
On Tue, Jan 22, 2019 at 10:25:24AM +, Mike Gabriel wrote:
> I think, the missing dependency is python3-dbus.
> 
> Do you think you can re-test the installation procedure, reproduce this bug
> and then try to install python3-dbus and see if that fixes things? If I

You are right. Went back to system status with the non-working mate
dock. Installed just 'python3-dbus' and dock was back again in the
panel. I wish I could provide some kind of tracebacks here but I'm
relying purely on whether I see the panel or not.

> The question is: is python3-dbus the only dep that is missing.

All I can say for certain is that 'python3-dbus' is the only dependency I
was missing. If another dependency is missing from the list but I happen
to have it installed by any chance, I could not say.

Thanks,

-- 
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD


signature.asc
Description: PGP signature


Bug#917884: It might be a missing dependency

2019-01-21 Thread Rock Storm
On Sat, Jan 19, 2019 at 10:19:34AM -0500, John Scott wrote:
> Hello.
> 
> I'm not the maintainer, but I replied to your bug report [1] and noticed that 
> I forgot to CC you by mistake. I'm including what I'd sent.

Hi John, thank you for sending me the e-mail directly, not only I forgot
to subscribe but I also forgot about this report. I'm so sorry.

I found a workaround to the problem by chance and I've been happily
using the mate dock since then. It turns out installing
'system-config-printer' solves the issue. So I guess one of the
following dependencies of system-config-printer is also a missing
dependency for 'mate-dock-applet':

ii  gir1.2-gdkpixbuf-2.0  2.38.0+dfsg-7
ii  gir1.2-glib-2.0   1.58.3-2
ii  gir1.2-gtk-3.03.24.3-1
ii  gir1.2-notify-0.7 0.7.7-4
ii  gir1.2-packagekitglib-1.0 1.1.12-1
ii  gir1.2-pango-1.0  1.42.4-6
ii  gir1.2-polkit-1.0 0.105-25
ii  python3   3.7.2-1
ii  python3-cups  1.9.73-2+b1
ii  python3-cupshelpers   1.5.11-4
ii  python3-dbus  1.2.8-2+b3
ii  python3-gi3.30.4-1
ii  system-config-printer-common  1.5.11-4


I suspect it is 'gir1.2-packagekitglib-1.0' but I'll leave this to the
maintainers.

> > Could you be using Wayland by any chance, like with GNOME 3? For me,
> > mate-panel crashes there regardless of applets used. Since the applet works
> > fine for me, I hope you don't mind that I reduce the bug severity.

I know it is high, but I believe the severity was correctly set as per
[1]. Whatever the problem is, it "makes the package in question
unusable".

 [1]: https://www.debian.org/Bugs/Developer#severities

> > I suggest that you try invoking mate-panel from the command-line, attempt to
> > add the applet again, and see if it gives any output that might be
> > meaningful  to be posted here.

I'd be happy to provide any feedback to debug this. Running 'mate-panel'
on the command line however does nothing (which was expected I guess).

$ mate-panel
    Cannot register the panel shell: there is already one running.

How can I create a new panel from the command line?

Thanks a lot,

-- 
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD


signature.asc
Description: PGP signature


Bug#917884: mate-dock-applet: Adding a new dock does nothing

2018-12-31 Thread Rock Storm
Package: mate-dock-applet
Version: 0.87-1
Severity: grave

Dear Maintainer,

After a recent system upgrade, I've lost the dock applet. It is no
longer shown on the panel. As said in the subject, adding a new one does
nothing. No new dock is shown on the panel either. 

This upgrade I did, did not affect the mate-dock-applet package itself,
so it might be a problem with one of its dependencies instead. I've
tried downgrading to version 0.75-1 but it didn't work. I also tried
downgrading the following dependencies with no luck:

 gir1.2-freedesktop:amd64 (1.58.3-1 > 1.58.2-2)
 gir1.2-glib-2.0:amd64 (1.58.3-1 > 1.58.2-2)
 gir1.2-notify-0.7:amd64 (0.7.7-4 > 0.7.7-2)

I'm sorry I couldn't help further, my knowledge here is limited.

Please let me know if there's anything else I could try to debug this.

Thanks a lot,

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mate-dock-applet depends on:
ii  bamfdaemon   0.5.4-1
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-bamf-30.5.4-1
ii  gir1.2-gdkpixbuf-2.0 2.38.0+dfsg-7
ii  gir1.2-glib-2.0  1.58.3-1
ii  gir1.2-gtk-3.0   3.24.2-3
ii  gir1.2-mate-panel1.20.3-1
ii  gir1.2-notify-0.70.7.7-4
ii  gir1.2-wnck-3.0  3.30.0-2
ii  libglib2.0-bin   2.58.1-2
ii  mate-panel   1.20.3-1
ii  python3  3.7.1-3
ii  python3-gi-cairo 3.30.4-1
ii  python3-pil  5.3.0-1
ii  python3-xdg  0.25-4
ii  python3-xlib 0.23-2

mate-dock-applet recommends no packages.

mate-dock-applet suggests no packages.

-- no debconf information


-- 
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD



Bug#917788: libmedc11: Overwrites a file from libmedc1v5

2018-12-30 Thread Rock Storm
Package: libmedc11
Severity: grave

Dear Maintainer,

While trying to update freecad I run into the following broken apt
state:

Preparing to unpack .../libmedc11_4.0.0+repack-3_amd64.deb ...
Unpacking libmedc11:amd64 (4.0.0+repack-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/libmedc11_4.0.0+repack-3_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libmedC.so.11.0.0', which is 
also in package libmedc1v5:amd64 4.0.0+repack-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libmedc11_4.0.0+repack-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've followed the solution given in this post [1] to fix it. It is also
suggested that a line such as 'Conflict: libmedc1v5' be added to the
control file.

 [1]: https://askubuntu.com/a/433510


Thanks a lot,
Rock

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libmedc11 depends on:
ii  libc62.28-3
ii  libgcc1  1:8.2.0-13
iu  libhdf5-openmpi-103  1.10.4+repack-4
ii  libopenmpi3  3.1.3-6
ii  libstdc++6   8.2.0-13

libmedc11 recommends no packages.

Versions of packages libmedc11 suggests:
pn  libmed-doc
pn  libmed-tools  

-- 
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD



Bug#855533: mate-dock-applet completely unusable

2018-08-19 Thread Rock Storm
On Sun, Aug 19, 2018 at 12:00:54AM +, Mike Gabriel wrote:
> Does it help, if you additionally install gir1.2-notify-0.7?

Hi, it does help yes. Installing dock-applet 0.86 and gir1.2-notify-0.7
shows the dock in the panel again. However I am not able to make it
look as it did on version 0.75-1. This is how version 0.75-1 looks like
[1] (applet has the same background as the rest of the panel). With
version 0.86-1 and gir1.2-notify-0.7 I am unable to change the
dock-applet's background color to match the rest of the panel [2]. 

 [1] https://imgur.com/a/ePR2wV3 
 [2] https://imgur.com/a/vTCjApt 

Thanks a lot for your time,

-- 
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD



Bug#878011: yagv: Won't start. No module named future

2017-10-08 Thread Rock Storm
Package: yagv
Version: 0.4~20130422.r5bd15ed+dfsg-3
Severity: grave

Dear Maintainer,

Tried to start yagv but I got the following:

$ yagv
Failed to get python-future
Traceback (most recent call last):
  File "/usr/bin/yagv", line 5, in 
import pyglet
  File "/usr/lib/python2.7/dist-packages/pyglet/__init__.py", line 56,
in 
import future
ImportError: No module named future


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages yagv depends on:
ii  python 2.7.14-1
ii  python-pyglet  1.3.0~rc1-1

yagv recommends no packages.

yagv suggests no packages.

-- no debconf information

-- 
Regards,
Rock



Bug#819960: totem: This file cannot be played over the network. Try downloading it locally first.

2016-04-04 Thread Rock Storm
Dear Maintainers,

I'm having this very same problem but I believe it is not related to
totem exactly but to some of its dependencies.

The problem started after an "apt-get upgrade" where totem was not
updated but the following totem-related packages were:

Packages totem depends on that were updated:
gstreamer1.0-clutter-3.03.0.16-1->  3.0.18-1
libglib2.0-02.46.2-3->  2.48.0-1
libgstreamer1.0-0   1.6.3-1 ->  1.8.0-1

Packages totem recommends that were updated:
gstreamer1.0-libav  1.6.3-1 ->  1.8.0-1
gstreamer1.0-pulseaudio 1.6.3-1 ->  1.8.0-1

Thanks,
Rock

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages totem depends on:
ii  gnome-icon-theme3.12.0-1
ii  gnome-icon-theme-symbolic   3.12.0-1
ii  grilo-plugins-0.2   0.2.14-5+b1
ii  gsettings-desktop-schemas   3.18.1-1
ii  gstreamer1.0-clutter-3.03.0.18-1
ii  gstreamer1.0-plugins-bad1.6.3-1+b1
ii  gstreamer1.0-plugins-base   1.6.3-1
ii  gstreamer1.0-plugins-good   1.6.3-1
ii  gstreamer1.0-x  1.6.3-1
ii  libc6   2.21-9
ii  libcairo2   1.14.6-1
ii  libgdk-pixbuf2.0-0  2.32.3-1.2
ii  libglib2.0-02.48.0-1
ii  libgstreamer-plugins-base1.0-0  1.6.3-1
ii  libgstreamer1.0-0   1.8.0-1
ii  libgtk-3-0  3.18.9-1
ii  libnautilus-extension1a 3.18.5-1
ii  libpango-1.0-0  1.38.1-1
ii  libpangocairo-1.0-0 1.38.1-1
ii  libtotem-plparser18 3.10.6-2
ii  libtotem0   3.18.1-2+b1
ii  libx11-62:1.6.3-1
ii  totem-common3.18.1-2

Versions of packages totem recommends:
ii  gstreamer1.0-libav 1.8.0-1
ii  gstreamer1.0-plugins-ugly  1.6.3-1
ii  gstreamer1.0-pulseaudio1.8.0-1
ii  totem-plugins  3.18.1-2+b1

Versions of packages totem suggests:
pn  gnome-codec-install  

-- no debconf information

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