Re: Home made tutorial to help beginners into packaging
Hello Sébastien, thanks for your work, I'll study it intensivly. I try also to document my steps preferred in German (automatic translation to English). You can find it at https://salsa.debian.org/ddp-team/dpb It is also written in LaTex. Kind regards Mechtilde Am 14.07.24 um 11:43 schrieb Sébastien Le Roux: Dear all, about 18 month ago I became a Fedora packager, and a little bit latter a Debian packager, a completely new experience for me. My goal at the time was to package my software atomes and benefit from the amazing officials channels of the open source community. As soon as I started this process I decided to document it, first let's be honest I would not be able to remember everything, but also and mostly I wanted to help others to do the same. I work in public research where many people know how to write code, but do not how to share it, so I wanted to help to improve that situation. I am pleased to release this document today at: https://github.com/Slookeur/OPEN You will find there the sources (I am a LaTeX person) and the latest PDF. The document covers as much as I could do it the entire process from building systems, git, hosting platform, and finally packaging (Fedora and Debian mainly, but I also give a quick look to Flatpack and Appimage). I hope you find this document useful, feel free to share it, feel free to adapt it: open source is the way ! Finally I had tremendous help along the way: Among the Fedora community, my Fedora mentor: Alexander Ploumistos thank you ! Among the Debian community, my Debian mentor: Pierre Gruet thank you ! Sébastien -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#688397: ITP: loook -- Search filestrings in ODF textstrings
Package: wnpp Severity: wishlist Owner: Mechtilde * Package name: loook Version : 0.6.8 Upstream Author : Daniel Naber * URL : http://www.danielnaber.de/loook/ * License : GPLv2+ Programming Lang: Python Description : Search filestrings in ODF textstrings -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120922113720.21967.56901.reportbug@localhost
Bug#665454: ITP: canzelay-client -- Canzeley -- It is the client application to organize a German Law Office
Package: wnpp Severity: wishlist Owner: Mechtilde * Package name: canzelay-client Version : 0.3.0 Upstream Author : Dr. jur Michael Stehmann * URL : http://www.canzeley.de/ * License : GPL 3+ Programming Lang: StarBasic / OpenOffice.org Basic or later and SQL Description : Canzeley -- It is the client application to organize a German Law Office -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120324114853.8807.73083.reportbug@localhost
Re: Developer repositories for Debian
Hello Am 05.05.2015 um 23:45 schrieb Mike Hommey: > On Sun, May 05, 2013 at 02:22:04PM +0200, Joerg Jaspert wrote: >> Hello world, >> >> Now with wheezy happy and out the door, we should finally tackle a long >> open issue. Developer repositories (AKA PPA) for Debian. > > Now with jessie happy and out the door, what is the status of Developer > repositories for Debian? Why can't you use people.debian.org for this? Kind regards > > Mike > > -- Mechtilde Stehmann ## PGP encryption welcome ## Key-ID 0x141AAD7F signature.asc Description: OpenPGP digital signature
Re: CentOS and Debian/Ubuntu release cycles
Hello Stephan, Am 09.12.20 um 17:25 schrieb Stephan Lachnit: > Hi all, > > maybe you already have heard it, CentOS is basically dead now. It used to be > an exact RHEL clone, but now it's kind of an RHEL beta [1]. > > Now what does that have to do with Debian? > > When we look into why people use CentOS, the reason is pretty simple: it is > (or was) binary-compatible with RHEL, just without the support [2]. > I was reading comments from people that use RHEL on their production, but > CentOS at home or for testing, because you don't need to pay for it. > These use cases now don't work anymore, forcing them into either paying for > RHEL, or moving to a different ecosystem. > > The more I started thinking about it, the more I wondered about why Debian > Stable and Ubuntu LTS are *not* binary-compatible. > It just doesn't make sense to me. Both Debian Stable and Ubuntu LTS provide a > more "long term" approach than let's say Fedora. > And while Ubuntu LTS is based on Debian, it is not based on Debian Stable, > even though they have release cycle of two years. > It would seem kinda obvious that Debian and Ubuntu have a common freeze > period and work on LTS maintenance together. > > Does anyone know why this is not the case? I suspect some historical reasons, > but I couldn't find anything quickly. IMO one difference is that Debian supoorts all packages in stable main for the release cycle of about 2 years and one year after, Ubuntu supports only packages in main not in universe. so Ubuntu only supports a small part of the repo as LTS. Kind regards Mechtilde > > - Stephan > > [1] https://blog.centos.org/2020/12/future-is-centos-stream/ > [2] It's easy to find comments on various blogs or social media, but for sake > of completeness let me just mention that CERN [3], [4]. > [3] https://linux.web.cern.ch/centos/ > [4] https://linux.web.cern.ch/other/ > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
Re: On doing 3000 no-source-change source-only uploads in January 2021
Hello Holger, I will do my part myself ASAP Kind regards Mechtilde Am 31.12.20 um 14:21 schrieb Holger Levsen: > Hi Bernd, > > On Thu, Dec 31, 2020 at 02:16:23PM +0100, Bernd Zeimetz wrote: >>> as described in Message-ID: <20201231124509.gb3...@layer-acht.org> >>> or >>> http://layer-acht.org/thinking/blog/20201231-no-source-change-source-uploads/ >>> I plan to do 3000 NMUs soon. >> Thanks for your work! > > thanks! > >> Although the high number of packages makes me wonder, if at least a >> quick MIA check of the maintainers is warranted, or - if those packages >> are needed in bullseye at all. >> Of course, there are some packages which are working just fine with the >> same source for years, but at least some debhelper/compat or policy >> check and upload at some point makes sense. >> >> I think Debian should sometimes be better and faster in removing >> unmaintained stuff. > > while I agree in principle I have to say that in practice it's not doable > for me, uploading 3000 packages doing just the basic checks that I do is a > major task already, if I add any other QA measure which requieres human > consideration (like removal) it becomes a much much bigger task, deluting > my original goal of fixing the issue of missing .buildinfo files. Even > just running lintian-brush would at least double the amount, though I believe > the impact would be even higher. > > that said, I filed a bug to get src:embedian-archive-keyring removed from > sid and then bullseye. That was one striking example I found going through > those first 570 packages... > > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
Re: Figuring how to work with team-maintained packages on salsa
Hello I started to automate and to document my way to Debian packaging with git-buildpackage. You can find the German description under people.debian.org/~mechtilde/Dokumentation It is work in Progress Some people starting to translate it into English The source code is at salsa.debian.org/ddp-team/dpb Kind regards Mechtilde Am 04.06.21 um 20:49 schrieb Helmut Grohne: > On Fri, Jun 04, 2021 at 07:43:59PM +0200, Florian Weimer wrote: >> I want to add a few patches to this repository: >> >> <https://salsa.debian.org/glibc-team/glibc/> >> >> Surely there must be some tool support to help with that? I know how >> to do it manually (perhaps even involving quilt). Has every Debian >> developer their own script for that? (It's like this in RPM land …) > > There is no homogeneity on git repositories. The sad truth is that if > you want to work with arbitrary packages in a homogeneous way, it is > best to avoid git entirely and work with .debdiffs instead. Eventually, > dgit might solve this, but its adoption still is fairly low. > > Most of the time we're in favour of choice, flexibility and diversity. > This is one of the areas where diversity kills productivity. We've > mostly realized that for packaging helpers and the majority of the > archive uses dh now. It'll take another decade for us to realize this on > the vcs level. > > Raphaël tried to formalize this in > https://lists.debian.org/20140815141601.ga11...@x230-buxy.home.ouaza.com, > but consensus wasn't reached back then in 2014. He did a stab via DEP-14 > starting at > https://lists.debian.org/2014212624.ga19...@home.ouaza.com, but that > wasn't released either. For his work on dgit, Ian Jackson started an > informal survey on git packaging workflows at > https://lists.debian.org/21933.9687.747175.762...@chiark.greenend.org.uk. > Sam Harmann continued the effort in 2019 with > https://lists.debian.org/tslh86j7hgt@suchdamage.org. The one thing > that we learned in all this is that there are only few things we agree > on and that everyone wants to keep using their workflow. > > As someone who regularly does archive-wide work, I can tell that this > diversity is a barrier to contributing. > > Helmut > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
Translation of salsa.debian.org/ddp-team/dpb
Hello, I have started a machine translation from https://ddp-team.pages.debian.net/dpb/BuildWithGBP.pdf at https://salsa.debian.org/ddp-team/dpb. I know that this is not a good translation. It should first help to understand what is written there. Help from native speakers is very welcome. Please contact me Kind regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Update GnuPG failed
Hello, since tha update on thursday I can't use GPG on Stretch. There is gpg version 2.1.15-4. Unter Jessie all things are fine with gpg 1.4.18 Unter Stretch I have no access to my private key and the public keyring. I only see the keys which incomes with the mails after the update What happens? The files of the secret key and the public keyring are identical with the backup and at the Jessie machine. What is the best way to fix it? Kind regards Mechtilde Stehmann -- ## Apache OpenOffice.org ## Freie Office Suite für Linux, MacOSX, Windows ## Debian ## Loook, calender-exchange-provider, libreoffice-canzeley-client ## PGP encryption welcome ## Key-ID 0x141AAD7F
Re: Future of the Tryton suite in Debian
Hello, It seems to be a problem to persuade the upstream develover how important it is to publish in Linux repositories. I discussed very often with them about this topic. I tried to elaborate their benefits of a release in the Linux distributions. Many of them only see their own application and don't want to look to the interaction among different applications. Kind regards Mechtilde Am 05.04.2018 um 11:42 schrieb Mathias Behrle: > Dear fellow developers, > > while it is unusual to publish the plans for every and each package I am > posting nevertheless this informal message, because there are 100+ packages > involved. > > > The short message > > I don't plan to continue the maintenance of the Tryton suite in my *free* > time. > > > The current state > > - The migration of team and repos to salsa is finished. > - An actualized and quite up-to-date version 4.6.x of all > packages is uploaded to unstable. > - The last bug fix release was uploaded. > - I will continue to package the bug fix releases for 4.6, but I won't package > the new upcoming version 4.8 under current circumstances. > > > What does this mean? > > Unless someone steps up to sponsor financially the packaging or takes over the > maintenance I will orphan the suite in due time before the release of buster > and recommend its removal (version 4.6 will be unsupported at the approximate > ETA of the release of buster). > > > The background > > I am maintaining the suite since now ~8 years, being member of the Tryton > project since the very beginning since ~10 years. My primary motivation was to > give some important reference to the Tryton project as well as to complete the > userland of Debian. I considered this to be a win-win-situation for Tryton as > well as for Debian users. > > The current evaluation of the situation shows unfortunately a different > result: > - After years of continued discussions and confrontations I have to realize, > that the Tryton project still doesn't meet my least expectations of a real > community project. Furthermore the work of maintaining Tryton in Debian is > quite low valued in Tryton. Constitutional questions and differing opinions > are mostly considered annoying. There is a clear tendance to prefer > exclusive > instead of inclusive behavior (which e.g. recently led due to poor and > repudiative communication to the removal of the OpenSUSE packages from the > website). > - The benefit of Tryton in Debian main is quite limited for our users. To get > a sustainable solution it is mostly better to use the backports at > debian.tryton.org. Thus the packages in main are indeed a very good base to > start the backports from, but they are not really the best alternative for > everyday use. > > Having said this it is now no more appropriate to invest my personal free time > into it. I will be glad to continue the work, if some user or company will > step > up with financial sponsoring. > > > So far in a nutshell, > Mathias signature.asc Description: OpenPGP digital signature
Bug#902333: ITP: tbsync -- Thunderbird/Lightning Add-On to support MS Exchange Calendar etc.
Package: wnpp Severity: wishlist Owner: Mechtilde * Package name: tbsync Version : 0.7.9 Upstream Author : John bieling * URL : https://github.com/jobisoft/TbSync * License : GPL v2+ Programming Lang: Javascript Description : Thunderbird/Lightning Add-On to support MS Exchange Calendar etc. Synchronize Exchange ActiveSync accounts (contacts, tasks and calendars) to Thunderbird, supports Office 365, Outlook.com, Freenet, Strato, Hotmail, Kopano and other EAS compatible servers. So it is possible to use a calandar at Exchange server with TB 60 +
Re: Building Debian packages in CI (ick)
Hello, one short remark Am 19.07.2018 um 18:06 schrieb Lars Wirzenius: > I've recently made the first release of ick, my CI engine > (https://ick.liw.fi/), which was built by ick itself. It went OK, but > the process needs improvement. This mail has some pondering on how > the process of building Debian packages should happen in the best > possible taste. > * `foo_1.2-1~debian8.dsc` — source package for Debian 8 > * `foo_1.2-1~debian8.debian.tar.xz` — Debian packaging and changes > * `foo_1.2-1~debian8_amd64.deb` — binary package for Debian 8, amd64 > * `foo_1.2-1~debian8_riscv.deb` — binary package for Debian 8, riscv > > * `foo_1.2-1~debian9.dsc` — source package for Debian 9 > * `foo_1.2-1~debian9.debian.tar.xz` — Debian packaging and changes > * `foo_1.2-1~debian9_amd64.deb` — binary package for Debian 9, amd64 > * `foo_1.2-1~debian9_riscv.deb` — binary package for Debian 9, riscv Please regard that foo_1.2-1~debian9 is greater than foo_1.2-1~debian10, which stand for Debian Buster -- Mechtilde Stehmann ## Debian Developer ## Loook, calender-exchange-provider, libreoffice-canzeley-client ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Bug#906853: ITP: tbsync -- [Thunderbird Add-On] Sync contacts, tasks and calendars to thunderbird. Currently supporting Exchange ActiveSync (EAS) and sabre/dav (CalDAV & CardDAV)
Package: wnpp Severity: wishlist Owner: Mechtilde * Package name: tbsync Version : 0.7.12 Upstream Author : Name john.biel...@gmx.de * URL : https://github.com/jobisoft/TbSync * License : GPL v3 Programming Lang: Javascript Description : [Thunderbird Add-On] Sync contacts, tasks and calendars to thunderbird. Currently supporting Exchange ActiveSync (EAS) and sabre/dav (CalDAV & CardDAV) Synchronize Exchange ActiveSync accounts (contacts, tasks and calendars) to Thunderbird, supports Office 365, Outlook.com, Freenet, Strato, Hotmail, Kopano and other EAS compatible servers. This package helps to connect to calender and contacts which are provided by a server named above. It has a similar functionality to calendar-exchange-provider which doesn't work any more with thunderbird >=60 I use it myself. I will do the package as I did it with calendar-exchange- provider.
Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)
Hello,
Am 15.05.2017 um 21:45 schrieb Zlatan Todoric:
>
>
> On 05/15/2017 02:02 PM, Lars Wirzenius wrote:
>> On Mon, May 15, 2017 at 01:42:09PM +0200, Arturo Borrero Gonzalez wrote:
>>> On 15 May 2017 at 13:30, Paul Wise wrote:
>>>> TBH if I was confronted with the new LXDE web design with CSS turned
>>>> on, I would probably just close the page. The old page is way more
>>>> informative and less heavy on the marketing.
>>>>
>>> Hi Paul,
>>>
>>> I believe that what we are actually looking for is a bit of
>>> improvement in the marketing side.
>>> Modern and fancy things.
>>>
>>> The LXDE example is good on that.
>> http://lxde.org/ seems to be the site in question. I agree with Paul,
>> I don't like it, and when I encounter pages in that style, I tend to
>> close the window.
>
> Then lets forget about getting newcomers (fresh blood) to Debian as
> you're so close minded to modern/new things - the same way they probably
> close the window when they see '90 style with a lot of text that
> actually says nothing. We are strange with our talks last few debconfs -
> we want new people but we don't want to break our precious habits nor do
> we want to give freedom to others to express themselves if they don't
> fit into our circle of thinking which must be the best one.
these two questions come into my mind:
What does a "newcomer" expect from such a website?
what do we expect from a newcomer?
>> * It's not nearly information-dense enough. www.debian.org is too
>> dense, but the lxde one goes too far in the other direction.
>> Something in between would be good.
>>
>> * It's hard for me to navigate or to find anything. It has a short
>> one-sentence summary ("Desktop environment for all"), but nowhere on
>> the front page does it mention that it works on Linux. That
>> information is probably on some other page, linked from the front
>> page, but finding that is someone else's job.
>>
> Well Debian on its page doesn't mention it is Linux based or has Linux
> kernel or at all word Linux. And short sentences are fine - no one is
> forcing you to learn all plane parts and how it works to just board it
> and come from point A to B. If we want users, you need to understand
> that they just want a nice looking and working OS, they don't want to be
> preached about it. For devs - we just need to have something like "Want
> To Become Debian Developer" and link it to some good doc.
>
To go from user to dev is a gliding way.
"Want To Become Debian Developer" is the last step for a dev not the
first one. IMO
We should try to differ into the different tasks for the user e.g:
* Installation
* Configuration
* Applications
* ...
* How can I help
* Structure of the Packages
* Packaging
* ...
my 2 cents
--
Mechtilde Stehmann
## Apache OpenOffice.org
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## Loook, calender-exchange-provider, libreoffice-canzeley-client
## PGP encryption welcome
## Key-ID 0x141AAD7F
signature.asc
Description: OpenPGP digital signature
Re: IMPORTANT: Do live Debian images have a future?
Hello Steve, thanks for your work on this task. I myself use it from time to time to show how Debian can looks like without installing at the target machine. So I have USB Sticks with me (with the inofficial non-free image). Kind regards Mechtilde Am 26.06.2017 um 16:08 schrieb Steve McIntyre: > [ Note the cross-posting... ] > > Hey folks, > > Background: we released live images for Stretch using new tooling, > namely live-wrapper. It is better than what we had before (live-build) > in a number of ways, particularly in terms of build reliability and > some important new features (e.g. UEFI support). But it's also less > mature and has seen less testing. There have been bugs because of > that. I have fixes for most of the ones I know about [1], and I'm > still working on more bugfixes yet. > > While the bugs are annoying, what worries me more is that they were > only spotted in release builds. There had been testing versions of > live images available for multiple weeks beforehand, presumably with > the same bugs included. (Almost) none of them reported. This shows > that we don't have enough people using these live images and/or caring > about filing bugs. > > We have a similar lack of involvement in terms of the content of the > live images. As I said above, I'm happy that we now have a reliable > tool for building our live images - that makes my life much > easier. But I honestly have no idea if the multiple desktop-specific > live images are actually reasonable representations of each of the > desktops. For example, I *seriously* hope that normal KDE > installations are not effected by #865382 like our live KDE > images. Validation by the various desktop teams would be useful here. > > The current situation is *not* good enough. I ended up getting > involved in live image production because the images needed making, > and I was already the main person organising production of Debian's > official images. To be frank, I had (and still have) no direct use for > the live images myself and I don't *particularly* care about them all > that much. Despite that, I've ended up spending a lot of time working > on them. A few other people have also spent a lot of time working in > this area - thanks are due to those people too. But it's still not > enough. > > If our live images are going to be good enough to meet the standards > that Debian users deserve and expect, we need *consistent*, > *sustained* involvement from a lot more people. Please tell me if > you're going to help. If we don't see a radical improvement soon, I'll > simply disable building live images altogether to remove the false > promises they're making. > > [1] > https://get.debian.org/images/release/current-live/amd64/iso-hybrid/#issues > -- Mechtilde Stehmann ## Apache OpenOffice.org ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## Loook, calender-exchange-provider, libreoffice-canzeley-client ## PGP encryption welcome ## Key-ID 0x141AAD7F signature.asc Description: OpenPGP digital signature
Re: trying to use wireless not from gnome... what's the incantation?
Hello, For Lan and WLan i use network-manager under XFCE succesfully. Regards Mechtilde Am 23.05.2016 um 08:28 schrieb Adam Borowski: > On Sun, May 22, 2016 at 08:42:12PM -0800, Britton Kerin wrote: >> Got a new laptop after 10 years of excellent stable ancient debian, >> and my wireless works from gnome, and only from gnome. Unfortunately >> I find that gnome3 is not for me. I've been trying dwm. >> >> No combination of nmcli ifconfig iw ip rfkill unblock wpa_supplicant >> /etc/network/interfaces etc. that I've tried makes wireless work >> outside of gnome, and I've googled much and tried many of them. It >> seems like a waste of time, since clearly nm-applet and/or >> NetworkManager knows the magic spell. > If for whatever reason NetworkManager doesn't work for you, and you want an > easy to use alternative, I'd recommend wicd. > > Using low-level tools can indeed be tricky, so while they're more powerful > than anything NM or wicd can do, they're an overkill and a waste of learning > time if what you want is regular use of a single interface. > >> I'm posting here both in hope of a solution, and because this seems >> like a bug. How come this only works from gnome? nmcli in particular >> looks like it's trying to be a general-purpose solution, but somehow >> it too only works from gnome. > NM is closely tied to Gnome so regressions in non-Gnome use aren't > surprising. > signature.asc Description: OpenPGP digital signature
Re: Apt-secure and upgrading to bullseye
Hello, Am 10.07.19 um 14:30 schrieb Julian Gilbey: > On Wed, Jul 10, 2019 at 12:31:51PM +0100, Julian Gilbey wrote: >> Hooray, buster's released! Congrats to all! >> >> So I tried upgrading my machine to bullseye today, and >> aptitude/apt-get update don't like this, giving me errors such as: >> >> E: Repository 'http://ftp.uk.debian.org/debian testing InRelease' changed >> its 'Codename' value from 'buster' to 'bullseye' >> N: This must be accepted explicitly before updates for this repository can >> be applied. See apt-secure(8) manpage for details. >> >> So I read apt-secure(8), which gives no indication of how to "accept >> this explicitly", and neither do any of the linked wiki pages. >> >> Any suggestions? >> >> (And obviously something needs changing so that people aren't stung >> when bullseye is released.) > > Ah, turns out it's a known bug with aptitude. The solution is to run > "apt update", which interactively asks what to do with these changes. that is the reason, why I didn't have this problem. I use apt-get / apt all the time. > > Best wishes, > >Julian > Kind regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: what about package for my simple program
Hello Am 02.08.23 um 16:40 schrieb Олег Пучинин: sf.net/projects/go-brut-x you can try to package it yourself. For questions about packaging use debian-ment...@lists.debian.org -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Re: what about package for my simple program
Please answer to the list address. What did you try? What doesn't work? Where can we see shat you try? Regards Mechtilde Am 03.08.23 um 08:55 schrieb Олег Пучинин: I tried :( чт, 3 авг. 2023 г. в 12:18, Mechtilde Stehmann : Hello Am 02.08.23 um 16:40 schrieb Олег Пучинин: sf.net/projects/go-brut-x you can try to package it yourself. For questions about packaging use debian-ment...@lists.debian.org -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Re: Salsa License list
Hello Paul, Am 08.12.20 um 14:51 schrieb Paul Sutton: > Hi > > I am working on some presentations for free software, and putting these > on https://salsa.debian.org/ > > Some of the presentations are also for the Academy team. > > However while the license template lists > > GPL 3 > Lesser GPL > The GNU Affero General Public License > > The > The GNU Free Documentation License > does not appear to be listed as a template, would it be possible to as > the salsa maintainers to perhaps include this please. > > If possible could the template also include some of the Creative commons > licenses too please. > The Free Documentation License isn't free without any problems. You can set unfree options: https://www.gnu.org/licenses/fdl-howto-opt.en.html That's the reasson why the docuemntation of the gcc https://packages.debian.org/bullseye/gcc-10-doc or the https://packages.debian.org/bullseye/emacs-common-non-dfsg is in non-free > The GNU Free Documentation License > https://www.gnu.org/licenses/licenses.html > > > Thanks > > Paul Sutton > Kind regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
Re: Debian's branches and release model
Hello, Am 20.10.21 um 02:43 schrieb Thomas Goirand: > Hi Simon, > > For me, the long freeze are very problematic. They may spawn for 6 > months, which is how long it takes for a new OpenStack release to show > up, and then I don't know where to upload it... :/ You can upload it to experimental > > As a result, the Wallaby release of OpenStack (released last spring) > never had the time to migrate fully to testing, for example, because I > uploaded Xena (released last October). > > Anyways, here's my reply inline below... > > On 10/18/21 6:54 PM, Simon McVittie wrote: >> It >> also aligns the incentives for enough people to make sure that we can >> successfully make a release in a finite time - even developers who >> don't really care about releases and just want the latest versions >> are incentivized to fix enough things to make the next release happen, >> so that the freeze will end and they can get back to uploading the >> latest versions to unstable. > > I don't know how you can make sure that using testing-proposed-updates > instead of unstable would suddenly demotivate everyone that cares about > about next stable. Could you explain? > > On 10/18/21 6:54 PM, Simon McVittie wrote: >> However, the problem with freezing testing but not freezing unstable is >> that if you do that, all updates to testing during the freeze (to fix the >> release-critical bugs that stop it from already being ready for release) >> have to go into testing via testing-proposed-updates, which approximately >> nobody uses. > > We don't use it, because we're told to use unstable... > > If we were told that it's ok to upload changes to unstable during the > freeze, and upload to testing-proposed-updates, we'd do it (and IMO, > it'd be a very good move from the release team). > >> Having code changes for our next stable release be essentially untested >> is not great from a QA perspective - if nobody is trying out those new >> versions except for their maintainer, then nobody can find and report the >> (potentially serious) bugs that only happen in system configurations that >> differ from the maintainer's system. That's why the release team strongly >> discourages packages going into testing via testing-proposed-updates, and >> encourages packages going into testing via unstable. > > If we were, during the freeze, directed to upload fixes to > testing-proposed-updates, then there would be more people adding it to > their sources.list during the freeze. > > Cheers, > > Thomas Goirand (zigo) > -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Bug#1001942: ITP: python3-imap-tools -- Work with email by IMAP in Python
Package: wnpp Severity: wishlist Owner: Mechtilde Stehmann X-Debbugs-Cc: debian-devel@lists.debian.org, mechti...@debian.org * Package name: python3-imap-tools Version : 0.50.2 Upstream Author : Vladimir Kaukin * URL : https://github.com/ikvk/imap_tools * License : Apache-2.0 Programming Lang: Python Description : Work with email by IMAP in Python It is a dependency for another package? This is a dependency for paperless (#986227) How do you plan to maintain it? inside a packaging team (check list at https://wiki.debian.org/Teams)? I want to package it inside the Python-Team. Kind regards Mechtilde
Re: application tool
Hello Greg you should ask at ubuntu-m...@lists.ubuntu.com Kind regards Mechtilde Am 09.09.22 um 06:07 schrieb Qx: Hello all! I am Greg and I am new on this list. I have two errands: 1)i have coded a tool which I would like to release for ubuntu. Can someone please advice as to how this is correctly done? 2)I would like to become a motu member/contributor. please advice how to proceed. Thank you, Greg -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Problems while searching for a new upstream version
Hello, for most of my packages I get the following message at tracker.debian.org (e.g. for tbsync) uscan had problems while searching for a new upstream version: In watchfile debian/watch, reading webpage https://github.com/jobisoft/TbSync/releases/ failed: 429 too many requests How can I solve it? Kind regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: Binary uploads into the archive
Hello Dennis, Am 29.10.24 um 14:56 schrieb Dennis van Dok: On 28-10-2024 22:09, Daniel Leidert wrote: Hi, by accident, I uploaded a binary package today (ruby-rouge) instead of its source-package into the archive. I expected the binary package being rejected once I discovered my mistake. But it was accepted instead, and it was also not being rebuilt. Didn't we turn off binary package uploads? Shouldn't this be rejected? Coincidentally did the exact same thing (with igtf-policy-bundle); but this is now stuck as it cannot migrate to testing (unless somebody manually intervenes). I think what I should do is update the release number and do another (source only) upload. You can do a new upload by increasing the revision number and an entry in changelog that this is an source only upload. Dennis Regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1082027: ITP: webext-folder-account -- Manage folder accounts
Package: wnpp Severity: wishlist Owner: Mechtilde Stehmann X-Debbugs-Cc: debian-devel@lists.debian.org, mechti...@debian.org * Package name: webext-folder-account Version : 12.0 Upstream Contact: Hartmut Welpmann * URL : https://github.com/Welpy-cw/Folder-Account> * License : MIT Programming Lang: Javascript Description : Manage folder accounts Lets you associate user accounts and identities with specific folders. Great for multiple users who share TB, or for managing mailing lists. - Some friends and I use it? - I plan to maintain it inside the webext-team
Re: Simpler git workflow for packaging with upstreamless repositories
Hello Andrey, Am 26.11.24 um 17:44 schrieb Andrey Rakhmatullin: On Tue, Nov 26, 2024 at 04:27:37PM +0100, Simon Josefsson wrote: One possible rebuttal to this is "gbp needs to do the right thing then". Currently gbp by default generates a broken tarball, which is also a source of confusion for many. Do you have a bug report number? -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Bits from DPL / Feedback on attracting newcomers
Hello Soren, Am 04.12.24 um 19:18 schrieb Soren Stoutner: Robert, I appreciate your addition to the discussion. On Wednesday, December 4, 2024 8:53:07 AM MST Robert Chéramy wrote: 1) Documentation 2. A vast amount of the step-by-step documentation written for beginners regarding how to package for the first time is subtly outdated in ways that become very confusing to beginners. Usually, at the time the documentation was written, it was correct. But things change quickly in Debian, and often nobody revisits and updates these howto guides. I had the same problems as my start becoming a Maintainer. I started with an very small new package and tried to understand the steps I have to do. Then I started to write a Script to do the packaging in the same way every time. then I did it with some more packages. Also the discussions "how can I start? etc. get me to write down all steps. And the script increases. Also the description increases.You can find it at salsa.debian.org. it is work in progress. This is no additional documentation. It tries to collect the information from different documents, which exists. It describes, why it is necessary to do something. My experience is. it is not easy to describe packaging for newcomer. Every newcomer has different questions and different problems with starting packaging. So we should encourage everyone to ask and contact people in a team, in a local or language group or the persons who sign the key. Kind regards -- Mechtilde Stehmann ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1094988: ITP: mustang-cli -- PDF invoice metadata library in ZUGFeRD format.
Package: wnpp Followup-For: Bug #1094988 Owner: Mechtilde Stehmann X-Debbugs-Cc: debian-devel@lists.debian.org, mechti...@debian.org I propose "mustang-cli" is a better name for this library The package name itself will be libmustang-cli-java
Bug#1094988: ITP: mustang-invoice -- PDF invoice metadata library in ZUGFeRD format.
Package: wnpp Severity: wishlist Owner: Mechtilde Stehmann X-Debbugs-Cc: debian-devel@lists.debian.org, mechti...@debian.org * Package name: mustang-invoice Version : 2.16.1 Upstream Contact: Name Jochen Stärk https://www.mustangproject.org/ * License : Apache License v2 Programming Lang: Java Description : PDF invoice metadata library in ZUGFeRD format. Read, write, validate and/or convert electronic invoices using the commandline version (download on the commandline page) or read how to embed the java library in your software. Why is this package useful/relevant? It is a possible library to read and/or right electonic invoices and bills. It is a dependency for - jverein - and other applications which handles with invoices and bills There is no other packages providing similar functionality I want to maintain it inside the Java-Team. Technical assistance is welcome Kind regards
Re: Problems to find sponsors (Was: Bits from DPL)
Hello Phil, Am 10.12.24 um 06:49 schrieb Phil Wyett: On Mon, 2024-12-09 at 15:58 -0800, Xiyue Deng wrote: Hi Sam, Sam Hartman writes: As a none DD I do basic build testing and validation of packages and their files in-order to bring them up to a minimum standard for a DD to then look at. This is to encourage Debian Developers to review and sponsor packages in mentors. A mentors package submission at the stage tagged 'confirmed' on the RFS bug means it is decent shape and be less of a strain on a DD's time. I use the sbuild using unshare[1] setup which can also run lintian, piuparts and autopkgtest test when configured. Can you provide a documentation of your configuration to do it. I want to incluce it into the documentation at salsa.debian.org/ddp-team/dpb. I want to integrate it into the workflow described there. Thank xou in advance Regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1093223: RFH: tbsync -- Thunderbird/Lightning Add-On to support MS Exchange Calendar etc.
Package: wnpp Severity: normal X-Debbugs-Cc: tbs...@packages.debian.org, debian-devel@lists.debian.org, mechti...@debian.org Control: affects -1 + src:tbsync I request assistance with maintaining the tbsync package. This should expand 6to dav-4-tbsync and eas-4-tbsync The package description is: Synchronize Exchange ActiveSync accounts (contacts, tasks and calendars) to Thunderbird, supports Office 365, Outlook.com, Freenet, Strato, Hotmail, Kopano and other EAS compatible servers. I have no longer access to an Exchange-Calender. I need help to test the updates also for stable-proposal.
Re: Bug#1106057: ITP: gwh -- git-buildpackage workflow helper
Hello,
Am 20.05.25 um 13:32 schrieb Andrey Rakhmatullin:
On Tue, May 20, 2025 at 01:03:47PM +0200, Mechtilde Stehmann wrote:
I'm deeply concerned that the "surface area" of Debian packaging
tools is too large already for new folk, and adding something like
gwh into the archive makes that problem worse.
I would really like to see an effort to improve gbp itself directly
at least first. Have you tried to do that?
I try to describe, how packaging with gbp (git-buildpackage) can work,
including the workflow and why.
It should help to unterstand the process of packaging.
salsa.debian.org/ddp-team/dpb
"The main script which the book explains ("Programmskript") is called
"build-gbp.sh""
This also sounds like an extra wrapper. It's also unlikely to be related
to gbp based on what I've read.
It is a script to assist you going through the packaging process not
really an extra wrapper.
Regards
--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
OpenPGP_signature.asc
Description: OpenPGP digital signature
Re: Bug#1106057: ITP: gwh -- git-buildpackage workflow helper
Hello, Am 20.05.25 um 12:07 schrieb Jonathan Dowland: I'm deeply concerned that the "surface area" of Debian packaging tools is too large already for new folk, and adding something like gwh into the archive makes that problem worse. I would really like to see an effort to improve gbp itself directly at least first. Have you tried to do that? I try to describe, how packaging with gbp (git-buildpackage) can work, including the workflow and why. It should help to unterstand the process of packaging. salsa.debian.org/ddp-team/dpb Help is appreciated Regards Mechtilde From the README, I see I'm still in the process of turning these from a bunch of files in my ~/bin and ~/.config and so on into something that can be of use to more people. This warning will disappear once I'm confident most of the rough edges have been smoothed out. IMHO, putting this in the archive is premature. I think most feedback on ITPs (like this) just goes into the void. Can I be explicit in asking you Roland, to withdraw this ITP, at least until you have exhausted options for improving gbp itself? -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature.asc Description: OpenPGP digital signature
Re: New contributor experience
Hello, Am 21.06.25 um 22:39 schrieb Andrey Rakhmatullin: On Sat, Jun 21, 2025 at 08:54:08PM +0200, Alex wrote: We get a question of "this is #d-mentors, how do I get a mentor assigned" on #d-mentors every several months, for which the answer is always "there is no such thing, please ask specific questions". There is the [MoM][0] in the Debian Med-Team. MoM means "Mentoring of the Month" https://salsa.debian.org/med-team/community/MoM/-/wikis/Mentoring-of-the-Month-(MoM) Is or was? According to that page, last updated 3 years ago, while there was some significant activity in 2014-2015 (10 years ago) it died out around 2017. It was also team-specific. That still exists. We want to expand it for more projects. We also want to discuss it at the upcoming DebConf25 next month. i hop we can meet each other. Regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#963504: ITP: novaworx -- Novaworx IDE - (Closed: #963504)
Package: wnpp Followup-For: Bug #963504 Owner: Mechtilde Stehmann X-Debbugs-Cc: debian-devel@lists.debian.org, mechti...@debian.org I don't want to package Jlawyer anymore. So it isn't necessary anymore to package nowaworx Kind regards
Bug#1107896: ITP: hvjavacal -
Package: wnpp Severity: wishlist Owner: Mechtilde Stehmann X-Debbugs-Cc: debian-devel@lists.debian.org, mechti...@debian.org, 948221-d...@bugs.debian.org Close this report. This package isn't needed anymore
Bug#948221: Closed
Package: wnpp Followup-For: Bug #948221 Owner: Mechtilde Stehmann X-Debbugs-Cc: debian-devel@lists.debian.org, 948221-d...@bugs.debian.org, mechti...@debian.org I want to close this bug report this package isn't needed to fullfill the dependencies of JVerein
Bug#948221: ITP: hvjavacal -- Calendar tool - Closed
Package: wnpp Followup-For: Bug #948221 Owner: Mechtilde Stehmann X-Debbugs-Cc: debian-devel@lists.debian.org, 948221-d...@bugs.debian.org, 1107896-d...@bugs.debian.org, mechti...@debian.org This It isn't needed to package this library to fullfill the dependencies for JVerein.
