[Bug 1587982] Re: Gnome Software catalog entry missing for Qsstv
I'm unsure of the Ubuntu process for that - if I could be pointed at documentation I might be able to do it. It shouldn't be a big process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587982 Title: Gnome Software catalog entry missing for Qsstv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qsstv/+bug/1587982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587982] Re: Gnome Software catalog entry missing for Qsstv
Hello, Debian uploader here! This should be sorted in the new 9.1.5+repack-1 release that's in Debian testing (and Yakkety Yak). I've removed the .xpm icon and replaced it with upstream's .png icon, and referenced this in the .desktop file. Can you guys have a check and tell me if that sorts the issue? Much Love, Hibby -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587982 Title: Gnome Software catalog entry missing for Qsstv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qsstv/+bug/1587982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506961] [NEW] Sync axmail 2.5-1 (universe) from Debian unstable (main)
Public bug reported: Please sync axmail 2.5-1 (universe) from Debian unstable (main) All changelog entries: axmail (2.5-1) unstable; urgency=medium * Initial release. (Closes: #799482) -- Dave Hibberd Mon, 12 Oct 2015 09:53:56 +0100 ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506961 Title: Sync axmail 2.5-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1506961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506830] [NEW] Sync uronode 2.3.1-2 (universe) from Debian testing (main)
Public bug reported: Please sync uronode 2.3.1-2 (universe) from Debian testing (main) All changelog entries: uronode (2.3.1-2) unstable; urgency=medium * Team upload. * Add Breaks+Replaces for ax25-node. (Closes: #800924) -- Iain R. Learmonth Mon, 05 Oct 2015 13:28:37 +0100 uronode (2.3.1-1) unstable; urgency=medium * Initial release. (Closes: #778843) -- Dave Hibberd Thu, 03 Sep 2015 23:37:40 +0100 ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506830 Title: Sync uronode 2.3.1-2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1506830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Ubuntu-hams-devel] [Bug 1872002] Re: [SRU] cqrlog needs to dependon mariadb instead of mysql
No problems. It is probably worth filing a bug against https://launchpad.net/ubuntu/+source/cqrlog/2.5.2-5 to help find someone to write the required patch and/or to stop it hitting the upcoming 24.10 release with a dependency on mariadb instead of mysql. As I'm generally unfamiliar with Ubuntu process and requirements, I'll leave that decision and task to others. Thanks for the review! -- Hibby Debian Developer Packet Radioist MM0RFN On Wed, 4 Sep 2024, at 2:38 PM, Robie Basak wrote: > To be clear: > > MySQL and MariaDB remain broadly compatible. Ubuntu has maintained its > status quo in defaulting to MySQL since before MariaDB existed. Users > expect consistency, and this means that packages in Ubuntu should > default to using MySQL over MariaDB unless the user has explicitly > chosen otherwise. > > If crqlog cannot work against MySQL, for example because it uses a > feature of MariaDB that MySQL doesn't have or is too difficult > technically to patch to use MySQL's equivalent feature instead, then > that's fine - it would be appropriate then to make an exception for this > package. But given how close the two forks are, and the nature of what > cqrlog does, this seems unlikely to me. > > If on the other hand a trivial patch could be used to maintain > compatibility against both MySQL and MariaDB, then I expect developers > who want to look after cqrlog in Ubuntu to write that trivial patch, > send it to Debian (since MySQL is still maintained in Debian sid) and to > upstream, etc. This requires investigation by an interested developer - > they don't have to be upstream. Given that MySQL has become more strict > about the SQL it accepts over time, it seems likely to me that this is > the issue and the fix would not only work for both sides of the fork, > but also be preferable for a change for upstream to accept anyway. > > We should avoid going back and forth in stable releases, so the long > term decision here for ongoing development and maintenance of the cqrlog > package in Ubuntu should be settled _before_ making changes to the > stable releases. > > If as reported this hasn't worked since Ubuntu 20.04, then clearly there > is no need for urgency here, and we should take the time to resolve this > situation properly to give the best experience to our users in the > future. > > For now, then, I'm rejecting these uploads from the queue. > > ** Changed in: cqrlog (Ubuntu Focal) >Status: In Progress => Incomplete > > ** Changed in: cqrlog (Ubuntu Jammy) >Status: In Progress => Incomplete > > ** Changed in: cqrlog (Ubuntu Noble) >Status: In Progress => Incomplete > > -- > You received this bug notification because you are a member of Ubuntu > ham developers, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1872002 > > Title: > [SRU] cqrlog needs to depend on mariadb instead of mysql > > Status in cqrlog package in Ubuntu: > Fix Released > Status in cqrlog source package in Focal: > Incomplete > Status in cqrlog source package in Jammy: > Incomplete > Status in cqrlog source package in Noble: > Incomplete > > Bug description: > [ Impact ] > > cqrlog is unusable for all users who will want to save their data > locally. It will fail to connect with the local database server when > any user tries to use it. > > Whenever any user tries to run the application for the first time, > the user will be asked in a dialogue box: > It seems you are trying to run this program for the first time, are > you going to save data to local machine? > If you say Yes, new databases will be created. This may take a while, > please be patient. > > The user has to click "Yes" to create local database to save data > locally. > > And, then it will fail and a new dialogue box will display: > MySQL could not be started. Please check if the MySQL server is > installed properly. > > Select close. > > Another dialogue box will popup with the error: > Error during connection to database: TMySQL57Connection : Server > connect failed. > > > [ Test Plan ] > > install cqrlog > > run cqrlog from a terminal or from the launcher > Select "Yes" in the dialogue box saying: > It seems you are trying to run this program for the first time, are > you going to save data to local machine? > If you say Yes, new databases will be created. This may take a while, > please be patient. > > if the package is fixed, it will display the window of "Database > connection" with Log001 on the first row. > > Click on "Open log" -> that will display a window of "Changelog" > click "Close" -> that will display the main window of cqrlog. > > Additional question will popup about new QSL managers database and > new DXCC tables. Select "No" for both these question. > > Just to confirm cqrlog is working, enter some dummy data. > > Enter "srutest" in the box labelled "Call", move to the box labelled > Name, and enter "name1". > Click
[Bug 1872002] Re: cqrlog needs to depend on mariadb instead of mysql
** Description changed: + [Impact] + Due to the difference in how Debian and Ubuntu ship the mysql-* packages, cqrlog has been using mysql-* packages in Ubuntu, which the package is not compatible with. This means users can successfully install, but the package fails on launch. + + In Debian, we ship mariadb-* to fulfil mysql-* requirements, but this is + not true with ubuntu [https://salsa.debian.org/mariadb- + team/mysql/-/blob/mysql-defaults/debian/master/debian/rules](Debian + Salsa ) + + [Test Plan] + This fix has already been tested and implemented in Debian upstream. However was not available in Debian until post-Noble release. + + This has already been tested manually by others, but as soon as a + version with the patch present is available, a user should install the + updated cqrlog package and the appropriate dependencies are installed so + the program should work as usual. + + [Regression Potential] + Extremely limited. Users on systems dating back to pre-jammy have not been able to use this package without manually installing mariadb, so no database migration is required unless they are upgrading from before hirsute, and they would need to migrate regardless of this bug. + + [Where problems could occur] + + Uncertain + + [Other Info] + This is already available in Debian Unstable, and also in Oracular due to the sync. + + I am the DD responsible for cqrlog in Debian but the SRU process is + unfamiliar to me, so some handholding and sponsorship is required! + + [Original Description] + Please update the cqrlog package (debian/control) to depend on mariadb server instead of mysql server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872002 Title: cqrlog needs to depend on mariadb instead of mysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1872002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Ubuntu-hams] [Bug 1896318] Re: [needs-packaging] Pleasepackage Gridtracker for Ubuntu
It'd be really helpful if my MUA offered reply to list but it was the bug and not the ubuntu-hams list! Take 2, this time to the bug report... I've had a couple of requests for this in Debian - it has a dependency on something called nwjs[1] which currently isn't packaged in the debian repos, so this becomes a bigger challenge to package! I'm reluctant to own nwjs as it's only used for this and I'm not fully committed to it, but it might make for an interesting friday night project. I think adding it to our repos is worth it however - purely becaue the 'install from repo' option that the gridtracker team currently ships I *think* uses a preinstall script to download and install nwjs, which breaks apt if you've got poor internet connectivity - I learned this on a field op last week! It was not a great user-experience to think "Oh well never mind, I can't pull ~120MB, let's use something else" and then have to do it *anyway* to download anything else. [1] https://nwjs.io/ Cheers, H -- Hibby Debian Developer Packet Radioist MM0RFN On Thu, 22 Aug 2024, at 5:25 PM, Mike McRoberts wrote: > Hi Logan. > > It already has been. See the URL below for instructions to add the repo to > your Ubuntu installation. > > https://gridtracker.org/index.php/downloads/install-from-repo > > 73, Mike/KY6MM > > > On Wed, Aug 21, 2024 at 11:15 PM Logan Rosen <1896...@bugs.launchpad.net> > wrote: > >> ** Description changed: >> >> Gridtracker is a application that is useable for radio amateurs. >> >> It works like Jtalert, but Jtalert is for windows only. >> >> Gridtracker can be found at : >> - https://tagloomis.com/grid-tracker/ >> + https://gridtracker.org/ >> >> GridTracker listens to traffic from WSJT-X and displays it on a map. >> It can also load adif files, like those used by CQrolg, a popular >> logging application. >> >> -- >> You received this bug notification because you are a member of Ubuntu >> Amateur Radio, which is subscribed to the bug report. >> https://bugs.launchpad.net/bugs/1896318 >> >> Title: >> [needs-packaging] Please package Gridtracker for Ubuntu >> >> Status in Ubuntu: >> New >> >> Bug description: >> Gridtracker is a application that is useable for radio amateurs. >> >> It works like Jtalert, but Jtalert is for windows only. >> >> Gridtracker can be found at : >> https://gridtracker.org/ >> >> GridTracker listens to traffic from WSJT-X and displays it on a map. >> It can also load adif files, like those used by CQrolg, a popular >> logging application. >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+bug/1896318/+subscriptions >> >> >> ___ >> Mailing list: https://launchpad.net/~ubuntu-hams >> Post to : ubuntu-h...@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~ubuntu-hams >> More help : https://help.launchpad.net/ListHelp >> > > -- > You received this bug notification because you are a member of Ubuntu > Amateur Radio, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1896318 > > Title: > [needs-packaging] Please package Gridtracker for Ubuntu > > Status in Ubuntu: > New > > Bug description: > Gridtracker is a application that is useable for radio amateurs. > > It works like Jtalert, but Jtalert is for windows only. > > Gridtracker can be found at : > https://gridtracker.org/ > > GridTracker listens to traffic from WSJT-X and displays it on a map. > It can also load adif files, like those used by CQrolg, a popular > logging application. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1896318/+subscriptions > > > ___ > Mailing list: https://launchpad.net/~ubuntu-hams > Post to : ubuntu-h...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~ubuntu-hams > More help : https://help.launchpad.net/ListHelp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896318 Title: [needs-packaging] Please package Gridtracker for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1896318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Ubuntu-hams-devel] [Bug 1872002] Re: [SRU] cqrlog needs to dependon mariadb instead of mysql
The application will not start with MySQL. The referred statement is from a post dated Jan 2009 just before mariadb first appeared. It is my opinion the shortdesc has not been updated either there or on the project's Github repo. The github repo lists a dependency on mariadb specifically [1] as does his control file for self-generated debs [2]. Testing reveals it builds with mysql but does not initialise correctly. Do affected users need to supply logs of the application failing to start on firstrun or similar? [1] https://github.com/ok2cqr/cqrlog?tab=readme-ov-file#dependencies [2] https://github.com/ok2cqr/cqrlog/blob/master/debian/control -- Hibby Debian Developer Packet Radioist MM0RFN On Thu, 29 Aug 2024, at 4:45 PM, Robie Basak wrote: > The upstream website at https://www.cqrlog.com/ says: > >> CQRLOG is an advanced ham radio logger based on MySQL database. > > In Ubuntu, we default to MySQL. I think switching to MariaDB by default > requires exceptional justification, such as the upstream and codebase > very clearly not being able to function with MySQL for a specific, > stated reason. > > If that's the case, please could you provide it? > > Otherwise, "cqrlog needs to depend on mariadb instead of mysql" seems > like an unjustified assumption. > > -- > You received this bug notification because you are a member of Ubuntu > ham developers, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1872002 > > Title: > [SRU] cqrlog needs to depend on mariadb instead of mysql > > Status in cqrlog package in Ubuntu: > Fix Released > Status in cqrlog source package in Focal: > In Progress > Status in cqrlog source package in Jammy: > In Progress > Status in cqrlog source package in Noble: > In Progress > > Bug description: > [ Impact ] > > cqrlog is unusable for all users who will want to save their data > locally. It will fail to connect with the local database server when > any user tries to use it. > > Whenever any user tries to run the application for the first time, > the user will be asked in a dialogue box: > It seems you are trying to run this program for the first time, are > you going to save data to local machine? > If you say Yes, new databases will be created. This may take a while, > please be patient. > > The user has to click "Yes" to create local database to save data > locally. > > And, then it will fail and a new dialogue box will display: > MySQL could not be started. Please check if the MySQL server is > installed properly. > > Select close. > > Another dialogue box will popup with the error: > Error during connection to database: TMySQL57Connection : Server > connect failed. > > > [ Test Plan ] > > install cqrlog > > run cqrlog from a terminal or from the launcher > Select "Yes" in the dialogue box saying: > It seems you are trying to run this program for the first time, are > you going to save data to local machine? > If you say Yes, new databases will be created. This may take a while, > please be patient. > > if the package is fixed, it will display the window of "Database > connection" with Log001 on the first row. > > Click on "Open log" -> that will display a window of "Changelog" > click "Close" -> that will display the main window of cqrlog. > > Additional question will popup about new QSL managers database and > new DXCC tables. Select "No" for both these question. > > Just to confirm cqrlog is working, enter some dummy data. > > Enter "srutest" in the box labelled "Call", move to the box labelled > Name, and enter "name1". > Click on "Save QSO". > > Close cqrlog window. > > Start cqrlog again. This time it will directly go to the window of > "Database connection" with Log001 on the first row. > Click on "Open log". This time it will directly go to the "cqrlog" > windows and will ask the additional questions about new QSL managers > database and new DXCC tables. > Select No for both. > > Enter "srutest" in the box labelled "Call", move to the box labelled > Name. The name will be autofilled now (taken from the previous > record). And on the top part of the window we should be able to see > the previous entry with timestamp. > > > [ Where problems could occur ] > > There is no change in the code. The only change is in the runtime > dependency to install mariadb instead of mysql and only impacts users > who uses local database. There is very miinimum chance of any > regression due to this change but as a worst case scenario if the > change causes some regression then the users who are using local > database will not see any new issue but will continue to see the same > problem as is now. > > [ Other Info ] > > 1. It has been fixed in the Debian package 2.5.2-5 which has been > synced to Oracular. > 2. As mentioned in the original Bug Description, the issue was caused > by a mismatch of mysql and mariadb. cqrlog needs mari
[Bug 1872002] Re: [SRU] cqrlog needs to depend on mariadb instead of mysql
HI there! > On 29 Aug 2024, at 17:31, Robie Basak <1872...@bugs.launchpad.net> wrote: > > On Thu, Aug 29, 2024 at 04:08:04PM -0000, Dave Hibberd wrote: >> The application will not start with MySQL. > > If it works with MariaDB but not MySQL, that doesn't necessarily mean > that it only supports MariaDB, or that there's not just a bug that needs > fixing to keep it compatible with both. The best I have is upstream saying it depends on mariadb not mysql[1] since version 2.5. I really don’t have time or knowledge to dig in to why this is the case, until this came around it was my understanding that they were compatible and I’ve followed upstream’s precedent in the Debian package. > >> Do affected users need to supply logs of the application failing to >> start on firstrun or similar? > > No. That's a given. What I'd like to see is an explanation of why the > package cannot be fixed to work with MySQL properly. > The problem that falls out of all this is that based on this bug when it got sent upstream to debian and that justification, I’ve moved the dependency to mariadb[2], not the virtual package. This has already been mirrored in the next release - granted, I’ve not checked if your mirror will automatically check If the preference in Ubuntu is to keep using mysql with this package, someone’s going to need to revert the change in the package that’s been mirrored for to not only depend on mysql and investigate why it’s not working or work with upstream to understand why they’re choosing to depend on mariadb instead. Cheers! [1] https://github.com/ok2cqr/cqrlog/issues/291#issuecomment-770383265 [2] https://salsa.debian.org/debian-hamradio-team/cqrlog/-/blob/master/debian/control?ref_type=heads#L36 -- Hibby Debian Developer Packet Radioist MM0RFN ** Bug watch added: github.com/ok2cqr/cqrlog/issues #291 https://github.com/ok2cqr/cqrlog/issues/291 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872002 Title: [SRU] cqrlog needs to depend on mariadb instead of mysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1872002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Ubuntu-hams-devel] [Bug 1872002] Re: [SRU] cqrlog needs to dependon mariadb instead of mysql
Someone has emailed the upstream author asking if he wishes to clarify his design choice for you. If there's any updates, I'll make sure they'll appear here. -- Hibby Debian Developer Packet Radioist MM0RFN -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872002 Title: [SRU] cqrlog needs to depend on mariadb instead of mysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1872002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872002] Re: cqrlog needs to depend on mariadb instead of mysql
Hi all, It turns out I agreed after some more thinking on the subject, so have committed a fix for this as 2.5.2-5 in Debian: https://tracker.debian.org/news/1538653/accepted-cqrlog-252-5-source- into-unstable/ Code's on salsa if you want to try a build and install - I ran it through my build infrastructure for jammy and noble and it builds successfully, but I haven't tested installing and running as I don't have a VM to hand. Cheers! Hibby -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872002 Title: cqrlog needs to depend on mariadb instead of mysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1872002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872002] Re: cqrlog needs to depend on mariadb instead of mysql
** Changed in: cqrlog (Ubuntu) Status: Confirmed => Fix Released ** Changed in: cqrlog (Ubuntu) Assignee: (unassigned) => Dave Hibberd (hibby) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872002 Title: cqrlog needs to depend on mariadb instead of mysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1872002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
