Hi Franklin, On Thu, Dec 17, 2020 at 05:39:54PM +0800, Franklin Weng wrote: > Sorry for forgetting to reply your last ping.
I admit I'm super happy about your current response. ;-) > Currently all the work on ezgo packages are here: > https://gitlab.com/franklin1/debian-ezgo-temp > I used to send a mail asking you about removing all the current content on > debian blend and replaced by the contents of my current working repository > (i.e., moving back from gitlab to ezgo). But it's been a long time ago (at > least one year before but I didn't go finding it out). > > In the gitlab working repository I've updated it, preparing for ezgo15. Would you mind to work on https://salsa.debian.org/blends-team/ezgo This is where *official* Blends are maintained and where you can get help from the Blends team. > About ezgo-phet which is the PhET offline package, which we recommend a lot > but IIRC you said I couldn't put it in ezgo blends, I created another > repository here: https://gitlab.com/franklin1/ezgo-phet If I remember correctly it just does not belong into the *metapackages* that where created by the ezgo source package. Its perfectly fine to create a separate source and binary package ezgo-phet and in the metapackage add a dependency from this. But you should do that *right now* to not miss the deadline for the freeze for Debian 11. > Not sure what I should do next. I'll highly appreciate for your advices. Create a packaging repository for https://salsa.debian.org/???/ezgo-phet.git and package ezgo-phet there. The '???' are intentional since I have no idea where the best place might be. There is always https://salsa.debian.org/debian/ezgo-phet.git but I'd rather put those packages under team maintenance. So the question is whether we should ask Salsa admins to create ezgo-team. That would make sense if you plan to provide more ezgo specific packages. We have such teams for every other Blend so that would make perfectly sense - if and only if you would maintain your packages there. > Regards, Franklin Kind regards and thanks for your work on ezgo Andreas. > Andreas Tille <[email protected]> 於 2020年12月17日 週四 下午5:29寫道： > > > Hi again, > > > > this is my last warning before I'll ask ftpmaster for removal of the > > ezgo package. I personally consider it a shame since I think its a > > valuable contribution for our users but since it is not maintained it > > might confuse users more than it might help them. > > > > Kind regards > > > > Andreas. > > > > On Tue, Nov 17, 2020 at 03:03:44PM +0100, Andreas Tille wrote: > > > Hi Franklin, > > > > > > this is another ping. Would you mind clarifying the situation of the > > > ezgo metapackages. These are not maintained for a very long time. We > > > are facing the freeze for the next Debian stable release in about three > > > months. I consider ezgo not of releasable quality. Thus I'm tempted to > > > file an RC bug to remove it from Debian testing. Please let me know if > > > something remains unclear - I'll happily help you to fix ezgo > > > metapackages but we need some dialogue to make sure we have the same > > > expectations about these packages. > > > > > > Kind regards > > > > > > Andreas. > > > > > > On Wed, Jan 16, 2019 at 08:33:02AM +0100, Andreas Tille wrote: > > > > Hi Franklin, > > > > > > > > On Sun, Jan 06, 2019 at 09:32:19PM +0800, Franklin Weng wrote: > > > > > I've set up a temporary git repository. Please see: > > > > > > > > > > https://gitlab.com/franklin1/debian-ezgo-temp > > > > > > > > Besides the issue Jonas mentioned, I think there is another no-go: You > > > > can not simply throw a PhET tarball into the Debian source archive and > > > > unpack it in the postinst script. The correct was is to create a phet > > > > package and make an ezgo metapackage depend from it. > > > > > > > > In short: Blends source packages might carry some artwork or > > localisation > > > > stuff that does not have some separate upstream project but not whole > > > > third parties as payload. > > > > > > > > Please find a way to distribute this separately from the ezgo source > > > > package. > > > > > > > > Thank you in any case for your work on ezgo > > > > > > > > Andreas. > > > > > > > > > It contains the contents which works in our current ezgo version. > > > > > > > > > > As what I have said, there are three kinds of packages in this > > repository: > > > > > > > > > > 1. meta packages which will install more free software packages: > > > > > * defined in tasks, and will generate ezgo-office, ezgo-graphics, > > > > > ezgo-multimedia, ezgo-network, ezgo-games, ezgo-education, > > > > > ezgo-accessories and ezgo-tasks > > > > > 2. ezgo common packages, including public domain resources and > > packages > > > > > which would "fix" problems or add features to current software > > packages: > > > > > * ezgo packages used by all system: ezgo-artwork, ezgo-gallery, > > > > > ezgo-menu (independent versioning) > > > > > * public domain resources: ezgo-phet, ezgo-wordtest > > > > > * fixing or adding features to current software: ezgo-misc-* > > > > > 3. desktop environment setup: > > > > > * ezgo-kde5, ezgo-lxde, ezgo-xfce > > > > > * ezgo-gnome and ezgo-unity are dropped for now due to outdated > > and > > > > > lack of test > > > > > > > > > > I've tested them on Debian Stretch. I can now set up a Debian > > Stretch > > > > > with KDE Plasma desktop, then install ezgo-artwork, ezgo-kde5, > > > > > ezgo-menu, and necessary ezgo-misc / ezgo meta packages, to form a > > > > > (nearly) complete ezgo system. > > > > > > > > > > My problems are that, some of them would need to modify files which > > were > > > > > installed by other packages. For example, ezgo-misc-audacity moves > > > > > locales/zh/LC_MESSAGES/audacity.mo to zh_CN/LC_MESSAGES/ so that > > zh_TW > > > > > translation could work. AFAIK it violates Debian packaging rules but > > > > > such fix was necessary. Another example is ezgo-lxde which would > > change > > > > > the file content in /etc/xdg/lxsession/Lubuntu/desktop.conf. > > > > > > > > > > Please have a look at this repository and let's discuss the next > > step to > > > > > upload these packages back to Debian. > > > > > > > > > > Thanks, Franklin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > http://fam-tille.de > > > > > > > > > > > > > > -- > > > http://fam-tille.de > > > > > > > > > > -- > > http://fam-tille.de > > > > > -- > Franklin Weng > 中華民國軟體自由協會常務理事 > LibreOffice 導入專家 > LibreOffice 法人代表文件基金會董事會副主席、認證委員會委員 -- http://fam-tille.de
