Bug#973774: Please update Lazpaint package to latest 7.x release https://github.com/bgrabitmap/lazpaint/releases
That's planned. There are some bugs to fix (in particular with Qt5). Hopefully that will be ready soon. -- Johann ELSASS circu...@operamail.com On Wed, Nov 18, 2020, at 11:09 AM, Mantas Kriaučiūnas Baltix wrote: > Package: lazpaint > It seems Lazpaint package in Debian is from 2016 branch - 6.4.1 release, see > https://github.com/bgrabitmap/lazpaint/releases/tag/v6.4.1 > LazPaint 6.4.1 > circular17 released this on 28 May 2016 · 1417 commits to master since this > release > > Please update package to latest 7.x releas: > https://github.com/bgrabitmap/lazpaint/releases > > Should I report a separate issue about this? > > Thanks, > Mantas > -- > Naudokite laisvą Linux operacinę sistemą savo kompiuteryje - http://baltix.eu > Mantas Kriaučiūnas > Tel.: +370-614-53085 > Use Baltix GNU/Linux OS ! http://launchpad.net/baltix
Bug#973774: lazpaint: copyright file incorrect
Hello again Joerg, I guess you were talking about a missing entry in the copyright file for the bgrabitmap folder. So, yes, I will such entry. Still remains the question about the name to put in the License field. For now I have put LGPL-2 as that was the closest I could find in the license list. But is that ok? Shall I include the exception paragraph in the copyright file anyway? Regards, -- Johann ELSASS circu...@operamail.com
Bug#973774: lazpaint: copyright file incorrect
Hello Joerg, Ok to change it. Though I did not find it in the list. https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ How shall I call it in the License field? Would the following be ok? License: mLGPL-2 This program is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; version 2 with the following modification: . As a special exception, the copyright holders of this library give you permission to link this library with independent modules to produce an executable, regardless of the license terms of these independent modules, and to copy and distribute the resulting executable under terms of your choice, provided that you also meet, for each linked independent module, the terms and conditions of the license of that module. An independent module is a module which is not derived from or based on this library. If you modify this library, you may extend this exception to your version of the library, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version. . This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. . You should have received a copy of the GNU Lesser General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. . On Debian systems, the full text of the GNU Lesser General Public License version 2 can be found in the file '/usr/share/common-licenses/LGPL-2'. License: mLGPL-2+ This program is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version, with the following modification: . As a special exception, the copyright holders of this library give you permission to link this library with independent modules to produce an executable, regardless of the license terms of these independent modules, and to copy and distribute the resulting executable under terms of your choice, provided that you also meet, for each linked independent module, the terms and conditions of the license of that module. An independent module is a module which is not derived from or based on this library. If you modify this library, you may extend this exception to your version of the library, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version. . This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. . You should have received a copy of the GNU Lesser General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. . On Debian systems, the full text of the GNU Lesser General Public License version 2 can be found in the file '/usr/share/common-licenses/LGPL-2'. Regards, -- Johann ELSASS circu...@operamail.com
Bug#960742: RFS: lazpaint/6.4.1-1 [ITP] -- Graphics viewer and editor
Hello Tobi, I think the package is ok. As Lazarus only handles Gtk2 and Qt5, I have switched to Qt5 in this package. Note that it is easy to switch back to Gtk2 by specifying the TARGET=Gtk2 for make. That's upload 7 of: https://mentors.debian.net/package/lazpaint/ You can find it here as well: http://johann-elsass.net/debian/lazpaint/ All is generated from upstream an debian: https://github.com/bgrabitmap/lazpaint-upstream Regards
Bug#960742: RFS: lazpaint/7.1.3 ITP -- add LazPaint to Debian
Hello, I have added ITP bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972503 I have made the source package with the DSC file. The changelog points to the ITP number. http://johann-elsass.net/debian/lazpaint/lazpaint_6.4.1-1.dsc Is it all ok? Regards
Bug#972503: ITP: LazPaint -- Image editor with raster and vector layers
Package: wnpp Severity: wishlist * Package name: lazpaint Version : 6.4.1 Upstream Authors: Johann Elsass * URL : https://github.com/bgrabitmap/lazpaint * License : GPL-3+ Description : Image editor with raster and vector layers Can read layered files (lzp, ora, pdn), multi-images (gif, ico), flat files (bmp, jpeg, pcx, png, psd, tga, tiff, xpm, xwd), vectorial (svg), 3D (obj). Has drawing tools, phong shading, curve adjustments, filters and render some textures. Package will be available at http://johann-elsass.net/debian/lazpaint/
Bug#960742: RFS: lazpaint/7.1.3 ITP -- add LazPaint to Debian
I don't understand. In a previous message you said you tried it and got an error with "lazarus-project" dependency. Do you still get this error? About the DSC file, someone else mentioned it. I don't know about this format but this has been mentioned to me by someone. May be that's something done by a package maintainer or something? -- Johann ELSASS circu...@operamail.com On Tue, Oct 13, 2020, at 8:27 PM, Tobias Frost wrote: > On Tue, Oct 13, 2020 at 07:27:19PM +0200, Johann ELSASS wrote: > > Interesting. I will consider using it. > > > > So have you tried with the dependency change? > > I'll need a .dsc file for that.
Bug#960742: RFS: lazpaint/7.1.3 ITP -- add LazPaint to Debian
Interesting. I will consider using it. So have you tried with the dependency change? -- Johann ELSASS circu...@operamail.com On Tue, Oct 13, 2020, at 4:23 PM, Tobias Frost wrote: > https://pbuilder-team.pages.debian.net/pbuilder/ > > TL;DR: debuilder builds your package, but in a possibly dirty environment > (as it uses your system and everything which is installed). pbuilder uses > a chroot which is always up-to-date, avoiding there are not-declared Build- > Dependencies or not updated packages. If it builds there, is is likely that > it will also build on the official buildds. > > (Some alternative is sbuild, which behaviour is even closer to the buildds: > https://wiki.debian.org/sbuild). > > -- > tobi >
Bug#960742: RFS: lazpaint/7.1.3 ITP -- add LazPaint to Debian
Hello, I guess I have fixed the problem with the dependency. In fact "lazarus-project" is a package downloaded on Lazarus site to get latest version, but that's not the one in the Debian distribution. So I replaced it with "lcl" and it seems to compile. I don't know if using pbuilder matters nor what pbuilder is. What I found when looking about packages was using debuild. https://wiki.debian.org/Packaging/Intro -- Johann ELSASS circu...@operamail.com On Wed, Sep 9, 2020, at 10:10 PM, Tobias Frost wrote: > On Wed, Sep 09, 2020 at 11:23:17AM +0200, Johann ELSASS wrote: > > Hello, > > > > I have made a repository with everything in it. For now it is version 6.4.1. > > (Robin also replied, please read the bug mentioned there… Though it has no > solution it might help understanding mechanics) > > > > > It is there: https://github.com/bgrabitmap/lazpaint-upstream > > Thanks for that, I think that is a starting point, but still some way to go. > > First you need your build env fixed… I could not build the package; > however > I'm not using dpkg-buildpackage but pbuilder for the job. pbuilder is > closer to > how the buildds are working. You should find guides how to setup > pbuilder with > somre research. Then make sure to give it a spin using some known-good > source package: > For example > apt source hello && cd hello-*/ && pdebuild > > After that, try that with your package (you need to create an orig.tar. > before; > easiest way (but not 100% correct for later -- this is just to bootstrap you) > is just to tar up the cloned git repo as lazpaint_6.4.1.orig.tar.xz > > You will then see that the package is not building with pbuilder…* > So your next goal is then to fix that. I unfortunatly won't be able to help > much with lazbuild/lazarus problems, so you likely need to figure out stuff > yourself. ask here when you've got stuck. Taking a look at other (lazarus) > packages might help too, of course. > > pbuilder bails out with > The following packages have unmet dependencies: > pbuilder-satisfydepends-dummy : Depends: lazarus-project (>= 1.8.6) which > is a >virtual package and is not provided by any available package > > That means "lazarus-project" is as Build-Depends, there is no package > with that name. > Not sure what it needed here. But I think I saw something in the bug > Robin referenced. > > Once you've got your package compiling, let us know. > > I wish you best of luck: The first package is always the hardest -- and I fear > you did not choose the easiest one! > > Cheers, > -- > tobi > >
Bug#960742: RFS: lazpaint/7.1.3 ITP -- add LazPaint to Debian
Hello, I have made a repository with everything in it. For now it is version 6.4.1. It is there: https://github.com/bgrabitmap/lazpaint-upstream I will update that later to version 7.* when it is stable. Regards, -- Johann ELSASS circu...@operamail.com On Tue, Sep 8, 2020, at 5:26 PM, Tobias Frost wrote: > > > On Sat, May 16, 2020 at 11:28:34AM +0200, Johann ELSASS wrote: > > Hello Tobias, > > > > Thanks for your reply. I came up with the following. > > > > First install "lazarus-package" as it is required to compile. > > > > Then the source package would consist of the following: > > - in bgrabitmap subdir extract > > https://github.com/bgrabitmap/bgrabitmap/archive/master.zip > > - in bgracontrols subdir extract > > https://github.com/bgrabitmap/bgracontrols/archive/master.zip > > - in lazpaint subdir extract > > https://github.com/bgrabitmap/lazpaint/archive/master.zip > > - in the base dir add make.sh (provided as attachment of this mail) > > > > Running it compiles and creates the Deb package in > > lazpaint/lazpaint/release/debian/ > > > > Am I getting closer? > > I fear there you need to check the packaging mechanics in Debian … > E.g you can't have manual steps. Your (Debian) source package needs to > have all the instructions > to make a Debian package. The instructions are in the debian/ directory > of a source package… > > Maybe those resource will be of help for an introdcution to Debian > packageing: > - https://mentors.debian.net/intro-maintainers/ (esp. the linked > resources) > - https://wiki.debian.org/Packaging/Intro > - > https://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.en.pdf > > In shorter words, you need to produce a source package where you can simply > say > "dpkg-buildpackage" and this command generates a *.deb. > > The second problem: You cannot download external resources while > building a package. > So you need to have (IIUC) bgrabitmap, bgracontrols already as Debian > package > and "Build-Depend" (an entry in debian/control) to retrieve them. > > There should be lazarus based packages already in Debian. Maybe look at > those packages > ddrescueview, doublecmd, dozzaqueux, mricron, optgeo, transgui, vmg, > winff* > For that, do a apt-source $package to get the source and take a look at > it. Maybe it helps to get started… > (As said, it is the debian directory that is most important.) > > -- > tobi > > (* disclaimer: only a quick grep over sources, I did not check details > / suitability) > > > > > > > -- > > Johann ELSASS > > circu...@operamail.com > > > > On Sat, May 16, 2020, at 8:29 AM, Tobias Frost wrote: > > > Control: tags -1 wontfix > > > > > > Hi Johann, > > > > > > thanks for your interest to contribute to Debian! > > > However, it's unfortunatly not that straight forward… See below for > > > info and resources! > > > > > > On Sat, May 16, 2020 at 08:04:00AM +0200, Johann ELSASS wrote: > > > > Package: sponsorship-requests > > > > Severity: wishlist > > > > > > > > Dear mentors, > > > > > > > > I am looking for a sponsor for my package "lazpaint": > > > > > > > > * Package name: lazpaint > > > >Version : 7.1.3 > > > >Upstream Author : Johann ELSASS > > > > * URL : https://github.com/bgrabitmap/lazpaint/releases > > > > * License : GPL3 > > > > * Vcs : > > > > https://github.com/bgrabitmap/lazpaint/tree/master/lazpaint/release/debian > > > >Section : Graphics App > > > > > > > > I don't understand very well what I am supposed to write in here. > > > > > > > > What I can say is that I build the debian package for 32-bit and 64-bit > > > > using the binary produced by the dev environment Lazarus and that I put > > > > it into the package using the bash script in lazpaint/release/debian > > > > folder. > > > > > > You need to compile lazpaint _while_ creating the debian package, it is > > > not acceptable to pre-compile it and then > > > "just" copy the resulting binary into it. > > > > > > I'm not a Pascal guy, there should be a few examples in the Debian > > > archives which might gives you hints how to do it: > > > codesearch.debian.net on lazarus
Bug#960742: RFS: lazpaint/7.1.3 ITP -- add LazPaint to Debian
Hello Tobias, Thanks for your reply. I came up with the following. First install "lazarus-package" as it is required to compile. Then the source package would consist of the following: - in bgrabitmap subdir extract https://github.com/bgrabitmap/bgrabitmap/archive/master.zip - in bgracontrols subdir extract https://github.com/bgrabitmap/bgracontrols/archive/master.zip - in lazpaint subdir extract https://github.com/bgrabitmap/lazpaint/archive/master.zip - in the base dir add make.sh (provided as attachment of this mail) Running it compiles and creates the Deb package in lazpaint/lazpaint/release/debian/ Am I getting closer? -- Johann ELSASS circu...@operamail.com On Sat, May 16, 2020, at 8:29 AM, Tobias Frost wrote: > Control: tags -1 wontfix > > Hi Johann, > > thanks for your interest to contribute to Debian! > However, it's unfortunatly not that straight forward… See below for > info and resources! > > On Sat, May 16, 2020 at 08:04:00AM +0200, Johann ELSASS wrote: > > Package: sponsorship-requests > > Severity: wishlist > > > > Dear mentors, > > > > I am looking for a sponsor for my package "lazpaint": > > > > * Package name: lazpaint > >Version : 7.1.3 > >Upstream Author : Johann ELSASS > > * URL : https://github.com/bgrabitmap/lazpaint/releases > > * License : GPL3 > > * Vcs : > > https://github.com/bgrabitmap/lazpaint/tree/master/lazpaint/release/debian > >Section : Graphics App > > > > I don't understand very well what I am supposed to write in here. > > > > What I can say is that I build the debian package for 32-bit and 64-bit > > using the binary produced by the dev environment Lazarus and that I put it > > into the package using the bash script in lazpaint/release/debian folder. > > You need to compile lazpaint _while_ creating the debian package, it is > not acceptable to pre-compile it and then > "just" copy the resulting binary into it. > > I'm not a Pascal guy, there should be a few examples in the Debian > archives which might gives you hints how to do it: > codesearch.debian.net on lazarus in debian/control might give you hints > where to look for examples: > https://codesearch.debian.net/search?q=lazarus+path%3Adebian%2Fcontrol&literal=1&perpkg=1 > > Beside that, please read this resource as starting point: > https://mentors.debian.net/intro-maintainers > As you are also upstream, you might also want to read: > https://wiki.debian.org/UpstreamGuide > > Cheers, > tobi > > (marking as wont fix for now -- that means that it cannot be sponsored > that way and avoids > that other people spend uncessary time on this bug report. Remove the > tag when you are ready with > a package that compiles from source.) > > > To access further information about this package, please visit the > > following URL: > > > > https://github.com/bgrabitmap/lazpaint > > > > Regards, > > > > -- > > Johann > > > make.sh Description: application/shellscript
Bug#960742: RFS: lazpaint/7.1.3 ITP -- add LazPaint to Debian
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "lazpaint": * Package name: lazpaint Version : 7.1.3 Upstream Author : Johann ELSASS * URL : https://github.com/bgrabitmap/lazpaint/releases * License : GPL3 * Vcs : https://github.com/bgrabitmap/lazpaint/tree/master/lazpaint/release/debian Section : Graphics App I don't understand very well what I am supposed to write in here. What I can say is that I build the debian package for 32-bit and 64-bit using the binary produced by the dev environment Lazarus and that I put it into the package using the bash script in lazpaint/release/debian folder. To access further information about this package, please visit the following URL: https://github.com/bgrabitmap/lazpaint Regards, -- Johann
