Bug#986184: ITP: dialect -- translation application
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-devel@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: dialect Version : 1.2.0 Upstream Author : gi-lom * URL : https://github.com/gi-lom/dialect/ * License : GPL-3+ Programming Lang: Python Description : translation app for GTK environments Dialect is a simple translation app for GTK environments - Features: * Translation based on the googletrans Python API, an unofficial API for Google Translate * Translation based on the LibreTranslate API, allowing you use any instance available online * Translation history * Automatic language detection * Text to speech * Clipboard buttons -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmBkNLYACgkQLHwxRsGg ASFqiBAAri83OZNlCGdO7LN8n1N1tY5V6ejvSOLfGJI6kMH/VYqobfiydlCtT3/J 1EdhkkAZaqND+XaaH01DKFWVQxYO1NWOGsw06I7iLoWUFN1/vhjlCZMncJksMbbN Q2/QncbPgjzM74Wh5ksDQ+XRHAuqNsnkx26aqid0LDSuw8INuRiHV95eu2SDfzDA xvTPLaeJTU+8TubTUmYw0uL2omk3+koZ46sJ8AyoMv3BePrp2RPItfoCk6CVw/cW IkzkKkHYT/HwlgKaJL69l5sS1Yr7Dy3+R9sXcmaI1ILToFTZkISA5Z6mVVdmrVkL 115TULPxmhDoP4D+AHonbdjOJVWFnJ54LU+jqQjYVvvRUmQ7WaK71vtQBaTX1XZK ZnTZPpuNTA40oZQdjdmzpduo5FzBrPAm9L+FLiqLthcMwYU7+Imn0IhWJJwW87Xa sZtxCOYWIEOx6TTY4mJPplGkfBIOCJLvMiMNgOf/IP663tVxFidWijpHrOaeFwa8 tjkTf9zdj2lGl39WhbesfsfZhNCLCTzHR1QnkgUpGNQcDH2nziwVTKovTsKDePYd QGj2irT/W6mApsx/PyNTXrmrejQ3klR/iIpo5jghdn6lrrLOhVZ3MSm+Lr4GVc0V M7SEnAzAKmwAMA7Iuyy9BCjKJlVfFAnuoM32tcm1SuMoKyG/lo8= =U/zy -END PGP SIGNATURE-
Bug#986202: ITP: nextcloud-notify-push -- Nextcloud push notification server
Package: wnpp Severity: wishlist Owner: Jonas Meurer X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: nextcloud-notify-push Version : 0.1.6 Upstream Author : Robin Appelman * URL : https://github.com/nextcloud/notify_push * License : AGPL Programming Lang: Rust Description : Nextcloud push notification server Nextcloud notify-push attempts to solve the issue where Nextcloud clients have to periodically check the server if any files have been changed. In order to keep sync snappy, clients wants to check for updates often, which increases the load on the server. . By providing a way for the server to send update notifications to the clients, the need for the clients to make these checks can be greatly reduced. . This package contains the notify-push server.
Re: Changed Github download URLs are affecting lots of existing watch files
On Sun, Mar 28, 2021 at 06:41:52AM +, Paul Wise wrote: > The problem with it was that it was entirely separate to the > maintainer's files so it was often different to their preferred way of > doing things. One option for doing this more optimally would be to add > some code to vcswatch to extract debian/watch files from the Vcs-* > repos and pass those to UDD, which could then run uscan with the VCS > debian/watch files where they are newer than the package. That would be extremely helpful. > Some additional points for the thread in general: > > I would suggest packages using GitHub are better off using the uscan > git mode rather than the GitHub releases/tags pages, since those are > now paginated and don't list all tags/releases. But I do not want an uscan warning for every single commit. Is git mode able to distinguish random commits from official releases (tags)? I'm using git mode only for the case that upstream refuses to use tags or is not reliably tagging releases (and I consider this only the second if not third best option). Kind regards Andreas. -- http://fam-tille.de
Re: Changed Github download URLs are affecting lots of existing watch files
Hi Wookey, On Sat, Mar 27, 2021 at 10:45:42PM +, Wookey wrote: > > Has anyone tried asking github if they are willing to specify and > support a stable interface (maybe even revert this change for the time > being). It's quite a big deal when they change these things, > especially just before a stable release. > > Having a reliable way to check the current release version is a > significant feature for a platform like theirs, and it wouldn't be > hard to keep the old URLs working for a couple of years to allow a > smooth switch to a specified long-term interface. I admit when I wrote my initial mail I was thinking about these lines but did not suggested it since I was not sure whether this is helpful in the end. Even if Github might be *that* friendly to Debian (which I'm not sure whether this will actually happen at all) it is only one example what could happen if we stick to the way we detect new upstream versions the way we are doing it now. My favourite solution would be to rather use the idea to base this on the VCSwatch result and automatically change VCS. Kind regards Andreas. -- http://fam-tille.de
Re: Tips for debugging/testing debian/control Depends/Breaks etc changes?
On Mon, Mar 29, 2021 at 07:12:18AM -0700, Otto Kekäläinen wrote: > apt install --with-source ./Packages -s mariadb-server mariadb-client > libmariadbclient18 I just want to add here, that --with-source also works with other apt commands like "upgrade". Depending on what you want to test, it might be more realistic to use these rather than making complicated explicit requests no 'normal' user will ever perform. > The debugging options produce a ton of output which I did not yet > learn to ready, but I'll paste it here below for reference for others > to see what the resolver debug output looks like: On the surface the problem you are facing is: > Broken mariadb-server-10.5:amd64 Conflicts on mysql-server:amd64 < > 5.7.30-0ubuntu0.18.04.1 -> 5.7.33-0ubuntu0.18.04.1 @ii umU > (< > 1:10.5.10+maria~bionic) > Considering mysql-server:amd64 0 as a solution to mariadb-server-10.5:amd64 > 0 > MarkKeep mariadb-server-10.5:amd64 < none -> 1:10.5.10+maria~bionic @un uN > Ib > FU=0 > Holding Back mariadb-server-10.5:amd64 rather than change mysql-server:amd64 That is one of the first decisions the problem resolver (second half) makes as these two packages want to be installed, but no sufficient reason is found to remove what works currently on the system (mysql-server) by bringing in something else (mariadb-server-10.5). The second line has them both listed as having 0 points – packages earn points by being depended on by other installed packages, lose some for conflicts on them, and a bunch of other reasons in both categories. Users hate then packages are removed, so apt tends to hate that, too. apt and friends even have entire commands which allow you to upgrade as far as you can go without removes as upgrades usually give you new features (and bugs) to play with while removes do the opposite. For me, this whole situation seems wrong though. Why do you have versioned package names (mariadb-server-*) when they are all mutually exclusive with one another due to all shipping the same binary? Either embrace versioned names like e.g. gcc/clang do or drop the pretense and ship an unversioned mariadb-server. Most packages aren't packaged versioned after all and that is (mostly) fine (same for client and co which only makes this more complicated and worse). Mixing the two causes your users to experience the worst of both worlds: The packages can not be co-installed forcing them through the change in one sitting and they are an upgrade nightmare as there will always be one more situation in which apt (or another resolver, or even a human) decides that (part of) an upgrade is not worth the perceived cost. Best regards David Kalnischkies signature.asc Description: PGP signature
Bug#986219: ITP: gnome-shell-extension-shelltile -- tiling window extension for GNOME Shell
Package: wnpp Severity: wishlist Owner: Fabio Augusto De Muzio Tobich X-Debbugs-Cc: debian-devel@lists.debian.org, ftob...@gmail.com * Package name: gnome-shell-extension-shelltile Version : 61+git20210205.1d56815-1 Upstream Author : Emanuele Sabellico * URL : https://github.com/emasab/shelltile * License : GPL-2+ Programming Lang: JavaScript Description : tiling window extension for GNOME Shell Just move a window to the edges of the screen to create a tiling, otherwise move a window over another one, holding down the Control key. Grouped windows minimize, resize, raise and change workspace together. Move or maximize a window to remove it from the group.
Re: Changed Github download URLs are affecting lots of existing watch files
On Wed, Mar 31, 2021 at 3:46 PM Andreas Tille wrote: > But I do not want an uscan warning for every single commit. Is git mode > able to distinguish random commits from official releases (tags)? The manual page lists an option for that so it seems likely. -- bye, pabs https://wiki.debian.org/PaulWise
Re: Changed Github download URLs are affecting lots of existing watch files
On Wed, Mar 31, 2021 at 3:50 PM Andreas Tille wrote: > My favourite solution would be to rather use the idea to base this > on the VCSwatch result and automatically change VCS. VCSwatch only looks at repositories linked from Debian Vcs-* headers, not the upstream VCS repositories. -- bye, pabs https://wiki.debian.org/PaulWise
Re: Realtek RTL8723DE, RTL8821CE, RTL8822BE and RTL8822CE chipsets
On Tue, Mar 30, 2021 at 10:20:03PM +0500, Andrey Rahmatullin wrote: Not sure what hardware you are talking about but the majority of WiFI hardware is supported by the mainline kernels, at least after you load their firmware. I assume you haven't tried very much wifi hardware. Realistically, the state of wifi support is still terrible. The best thing to do is try to buy something known to be supported, but that's relatively difficult for most people because the name on the box generally has nothing to do with the chips inside the box.
Re: Realtek RTL8723DE, RTL8821CE, RTL8822BE and RTL8822CE chipsets
On Wed, Mar 31, 2021 at 10:38:11PM -0400, Michael Stone wrote: > On Tue, Mar 30, 2021 at 10:20:03PM +0500, Andrey Rahmatullin wrote: > > Not sure what hardware you are talking about but the majority of WiFI > > hardware is supported by the mainline kernels, at least after you load > > their firmware. > > I assume you haven't tried very much wifi hardware. Realistically, the state > of wifi support is still terrible. The best thing to do is try to buy > something known to be supported, but that's relatively difficult for most > people because the name on the box generally has nothing to do with the > chips inside the box. Can you please list some unsupported chips in addition to these specific Realtek ones? -- WBR, wRAR signature.asc Description: PGP signature
