-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello dear engineers.
I have prepared some new packages for Debian, would you be interested?
These packages have been verified and have the confirmed tags.
1. vifm
RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093235
https
On Sat, Jan 18, 2025 at 02:07:43PM -0500, Tiago Bortoletto Vaz wrote:
> > > It is very much appreciated that you were diligent and consulted
> > > documentation (and this list) before trying to sponsor packages as a DM.
> > > Technically, it's not possible. See:
> > >
> > > https://wiki.debian.org
Hi Christian,
On Sat, Jan 18, 2025 at 04:55:55PM GMT, Christian Kastner wrote:
> Hi Tiago,
>
> On 2025-01-17 14:51, Tiago Bortoletto Vaz wrote:
> > It is very much appreciated that you were diligent and consulted
> > documentation (and this list) before trying to sponsor packages as a DM.
> > Tec
Hi Tiago,
On 2025-01-17 14:51, Tiago Bortoletto Vaz wrote:
> It is very much appreciated that you were diligent and consulted
> documentation (and this list) before trying to sponsor packages as a DM.
> Technically, it's not possible. See:
>
> https://wiki.debian.org/DebianMaintainer#Granting_Per
Hi Cordell,
On Thu, Jan 16, 2025 at 03:36:15PM GMT, Cordell Bloor wrote:
> Hello,
>
> I'm a Debian Maintainer with upload permissions for various packages in the
> ROCm GPU compute stack. The Debian ROCm Team has a few Sponsored Maintainers
> contributing to our packages, bu
On Fri, Jan 17, 2025 at 07:23:51AM +0100, Geert Stappers wrote:
> > This all seems consistent with the theory that it would be inappropriate for
> > me as a Debian Maintainer to sponsor an upload from a Sponsored Maintainer,
> > even if I have permission to independently upload
On Thu, Jan 16, 2025 at 03:36:15PM -0700, Cordell Bloor wrote:
> Hello,
Hi there,
> I'm a Debian Maintainer with upload permissions for various packages in the
> ROCm GPU compute stack. The Debian ROCm Team has a few Sponsored Maintainers
> contributing to our packages, but i
Hello,
I'm a Debian Maintainer with upload permissions for various packages in
the ROCm GPU compute stack. The Debian ROCm Team has a few Sponsored
Maintainers contributing to our packages, but is short on Debian
Developers to review them. One of the DDs that I work with has suggested
t
Control: tags -1 -confirmed
Control: tags -1 +moreinfo
Aidan,
Preamble...
Thank you for taking the time to prepare this package and your contribution to
the Debian project.
This review is offered to help package submitters to Debian mentors inorder to
improve their packages prior to possible
Hi!
Salsa CI is a great system for all aspiring Debian packagers to test
their packages before requesting review from mentors, or for even
experienced packagers before uploading to Debian.
Anyone with a Salsa account can use it. Simply follow the README at
https://salsa.debian.org/salsa-ci-team
Hi,
On Sat, Dec 21, 2024 at 11:00:06PM GMT, Otto Kekäläinen wrote:
> Hi!
>
> Salsa CI is a great system for all aspiring Debian packagers to test
> their packages before requesting review from mentors, or for even
> experienced packagers before uploading to Debian.
>
>
Thanks Phil and Marc for the feedback!
I updated the intro as suggested by Marc.
I also wrote a new wiki page https://wiki.debian.org/SalsaCI. This is
intentionally a minimal stub that recommends readers to see the README
in the project instead. Feel free to sprinkle links to this page
elsewhere
On Sun, Dec 22, 2024 at 11:27:07AM -0800, Otto Kekäläinen wrote:
> I also wrote a new wiki page https://wiki.debian.org/SalsaCI.
Thank you. That will be helpful to find the information.
Greetings
Marc
--
-
Marc Haber
On Sat, Dec 21, 2024 at 11:00:06PM -0800, Otto Kekäläinen wrote:
> Salsa CI is a great system for all aspiring Debian packagers to test
> their packages before requesting review from mentors, or for even
> experienced packagers before uploading to Debian.
>
> Anyone with a Salsa
Hi,
On Sat, Dec 21, 2024 at 11:00:06PM -0800, Otto Kekäläinen wrote:
> Salsa CI is a great system for all aspiring Debian packagers to test
> their packages before requesting review from mentors, or for even
> experienced packagers before uploading to Debian.
>
> Anyone with a Sa
On Sat, 2024-12-21 at 23:00 -0800, Otto Kekäläinen wrote:
> Hi!
>
> Salsa CI is a great system for all aspiring Debian packagers to test
> their packages before requesting review from mentors, or for even
> experienced packagers before uploading to Debian.
>
> Anyone with a
Hi!
Salsa CI is a great system for all aspiring Debian packagers to test
their packages before requesting review from mentors, or for even
experienced packagers before uploading to Debian.
Anyone with a Salsa account can use it. Simply follow the README at
https://salsa.debian.org/salsa-ci-team
Hi,
Just for awareness: Debian already has Debcraft, which builds Debian
packages in an isolated Docker environment. It supports both Docker
and Podman, and it also has a bunch of other automation to help do
quick rebuilds of packages after modifications, and compare how the
end result changed
Dear all DDs,
Below is a package list of the currently "confirmed", as being in good order
packages that are awaiting a DD review and possible upload to Debian. If DDs
could spare the time to pick up a package or two and finish off the package
mentor process it would be greatly a
Control: tags -1 -moreinfo
Control: tags -1 +confirmed
Aidan,
Preamble...
Thank you for taking the time to prepare this package and your contribution
to the Debian project.
The review below is for assistance. This review is offered to help package
submitters to Debian mentors inorder to
ll DDs,
It has been suggested that I need to supply a list of the current "confirmed"
packages requiring a sponsor that need a DD to review and possibly upload to
Debian when ready. Below is that list.
#1072910 RFS: lsp-treemacs/0.5-1 -- treemacs integration for Emacs LSP
RFS: https://bugs
Dear all DDs,
Below is the link to the page of currently "confirmed" as being in good order
packages that are awaiting a DD review and possible upload to Debian. If DDs
could spare the time to pick up a package or two and finish off the package
mentor process it would be greatly a
Hi!
A small group of Debian Developers are meeting for lunch on Sept 20th
in downtown Vancouver, B.C., Canada.
If there are any aspiring Debian Developers/Maintainers here on
debian-mentors@ who live close by and want to join, drop me a message
for details.
- Otto
Control: tags -1 +confirmed
Xyue,
Preamble...
Thank you for taking the time to prepare this package and your contribution
to the Debian project.
The review below is for assistance. This review is offered to help package
submitters to Debian mentors inorder to improve their packages prior to
Hi all,
for some historic reasons some of our (Debian TeX task force)
repositories are sitting on github. I'd like to use the Debian provided
CI/CD even on these repos. Here [1] is description how this could be
done, but I'm failing to implement it, b/c some steps can't
Hi Debian Developers,
Our package marked as "confirmed" that has languished on mentors for quite
some time is our package of the day.
Please could a DD with a little free time, graciously give it your time and
show this package some love?
Package: graphite-carbon
Links...
* Mento
Hi!
On Wed, 2024-08-28 at 03:10:51 +0900, Yunseong Kim wrote:
> Initially packaging works for syzkaller
Thanks for reaching out to the lists as suggested on IRC. :)
Prompted by the initial request in there, I had done a quick review pass
over the commit provided and added comments inline, just i
to Package). Then you will want to file a RFS (Requst for Sponsor).
> Instructions for both are at (which I assume you have already found):
>
> https://mentors.debian.net/intro-maintainers/
>
Very quick indeed. The package is not in a state to be reviewed.
I will offer the Debi
Hi Soren,
Thank you for the kind guidance.
On 8/28/24 3:36 오전, Soren Stoutner wrote:
> Yunseong,
>
> Thank you for your work on this. As a next step, I would recommend you
> upload
> the package to the Mentors website.
>
> https://mentors.debian.net/
>
> That will assist you in finding a sp
On Tuesday, August 27, 2024 12:06:55 PM MST Yunseong Kim wrote:
> I've uploaded my syzkaller package on mentors.debian.net.
That was quick of you. If you haven’t already, you’ll want to file an ITP
(Intent to Package). Then you will want to file a RFS (Requst for Sponsor).
Instructions for bo
Yunseong,
Thank you for your work on this. As a next step, I would recommend you upload
the package to the Mentors website.
https://mentors.debian.net/
That will assist you in finding a sponsor.
On Tuesday, August 27, 2024 11:17:37 AM MST Yunseong Kim wrote:
> Hi debian mentor and debian
Hi debian mentor and debian-go member,
This is my first time working on Debian packaging, so I need some advice.
This link is my syzkaller repository on salsa.
Link:
https://salsa.debian.org/yunseongkim/syzkaller/-/tree/debian?ref_type=heads
This is the dpkg-buildpackage log.
Link: https
Initially packaging works for syzkaller
Signed-off-by: Yunseong Kim
---
debian/.gitignore| 3 ++
debian/changelog | 5 +++
debian/compat| 1 +
debian/control | 12 +++
debian/copyright | 26 ++
debian/files | 2 ++
debian/rules | 84
Dear all DDs,
Below is the link to the page of currently "confirmed" being in good order
packages that are awaiting a DD review and possible upload. If DDs could
spare the time to pick up a package or two and finish off the package mentor
process it would be greatly appreciated.
https://bugs.debi
P,
> Java and C/C++ in college.
>
There's a big community in Brazil (https://debianbrasil.org.br/). You can
join it to #debian-br and #debian-deve-br in OFTC.
> I've known GNU/Linux since 2008 and lately I'd like to be able to
> contribute to Debian in some way in my free time.
On 2024-08-18 19:37 -0300, Isael Sousa wrote:
> Hello everyone,
Welcome,
> I've known GNU/Linux since 2008 and lately I'd like to be able to
> contribute to Debian in some way in my free time.
>
> I would like to start packaging some GoLang code and would like to kn
e with GoLang, Python and JavaScript. I've also worked with PHP,
> Java and C/C++ in college.
>
> I've known GNU/Linux since 2008 and lately I'd like to be able to
> contribute to Debian in some way in my free time.
>
> I would like to start packaging some GoLang code an
Hello everyone,
I'm Isael, I live in Fortaleza-CE, Brazil. I'm a developer and I have
experience with GoLang, Python and JavaScript. I've also worked with PHP,
Java and C/C++ in college.
I've known GNU/Linux since 2008 and lately I'd like to be able to
contribute to Debi
iner access of salsa repo[2].
Can someone please add me as a maintainer to the repo? My username is
akashdoppalapudi[3].
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038633
[2] https://salsa.debian.org/debian/acr
[3] https://salsa.debian.org/akashdoppalapudi
Thanks & Regard
].
>
> Can someone please add me as a maintainer to the repo? My username is
> akashdoppalapudi[3].
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038633
> [2] https://salsa.debian.org/debian/acr
> [3] https://salsa.debian.org/akashdoppalapudi
>
> Thanks &
/bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038633
[2] https://salsa.debian.org/debian/acr
[3] https://salsa.debian.org/akashdoppalapudi
Thanks & Regards,
--
Akash Doppalapudi
OpenPGP_0xBCBCAE31ECE05007.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
issues)
against packages that have known false positives.
Excellent idea, and could be used for your svg files.
Maybe an optional file like debian/licenserecon-excluded-files,
that just lists the files to be excluded from the check.
Regards.
Peter
P.S.
Timing isn't great here, as I shall be
Peter,
On Tuesday, August 6, 2024 7:38:45 AM MST Peter B wrote:
> > In addition to the other comments, lrc is prone to a high number of
>
> false
>
> > positives. It is helpful as a tool, but its failure often doesn’t
>
> indicate
>
> > there is an actual problem. So, people should probab
> In addition to the other comments, lrc is prone to a high number of
false
> positives. It is helpful as a tool, but its failure often doesn’t
indicate
> there is an actual problem. So, people should probably enable it
manually in
> their CI instead of it being automatic.
Please report
checks, I found out that there is an integration with
> > Salsa CI available to get on the spot lrc reports, just by doing
> >
> > include:
> > -
> >
> > https://salsa.debian.org/debian/licenserecon/raw/main/debian/
licenserecon.ym
> > l
> >
> >
> Not everyone has a DEP5 compatible debian/copyright file and
> force-activating that check for those packages would immediately break
> their CI without providing any benefit.
the CI could detect the DEP5 copyright and run the test only when relevant :)
to get on the spot lrc reports, just by doing
>
> include:
> -
> https://salsa.debian.org/debian/licenserecon/raw/main/debian/licenserecon.yml
>
> Maybe you can advertise this to more people already using Salsa CI and
> DEP5 copyright files to reduce unnecessary round tr
en Hartge below.
> >
> > WRT the license checks, I found out that there is an integration with
> > Salsa CI available to get on the spot lrc reports, just by doing
> >
> > include:
> > -
> > https://salsa.debian.org/debian/licenserecon/raw/main/debian/licenser
On 05.08.24 16:52, PICCA Frederic-Emmanuel wrote:
WRT the license checks, I found out that there is an integration with
Salsa CI available to get on the spot lrc reports, just by doing
include:
-
https://salsa.debian.org/debian/licenserecon/raw/main/debian/licenserecon.yml
> and why
Hi all,
Tip of the day today comes from Sven Hartge below.
WRT the license checks, I found out that there is an integration with
Salsa CI available to get on the spot lrc reports, just by doing
include:
-
https://salsa.debian.org/debian/licenserecon/raw/main/debian/licenserecon.yml
Maybe you
On Thu, 2024-07-25 at 22:27 +0800, solomoncyj wrote:
> The files needed for creation may be downloaded from
> https://github.com/russellbanks/Komac/archive/refs/tags/v2.3.0.tar.gz
> and prepared by using the `cargo-deb` cargo package
See Debian Go Team documentation for packaging in
The files needed for creation may be downloaded from
https://github.com/russellbanks/Komac/archive/refs/tags/v2.3.0.tar.gz
and prepared by using the `cargo-deb` cargo package
Xiyue,
Preamble...
Thank you for taking the time to create this package and your contribution
to the Debian project.
The review below is for assistance. This review is offered to help
package submitters to Debian mentors inorder to improve their packages
prior to possible sponsorship into
Xiyue,
Preamble...
Thank you for taking the time to create this package and your contribution
to the Debian project.
The review below is for assistance. This review is offered to help
package submitters to Debian mentors inorder to improve their packages
prior to possible sponsorship into
Colin,
Many thanks for the prompt updating of the package. I have added
an updated review on the packages mentor page[1].
[1] https://mentors.debian.net/package/ipp-crypto/
Regards
Phil
--
"I play the game for the game’s own sake"
Arthur Conan Doyle - The Adventure of the Bruce-Partington P
Hello,
This is a call for Debian mentorship.
My background is in science and engineering, as well as in scientific
computing. I'm especially active in scientific programming, contributing
to a large number of projects on gitlab/github/salsa (I already have a
farhi-guest account in the l
Am Mon, Jul 15, 2024 at 08:59:11PM GMT, schrieb Steven Schubiger:
> Pierre Gruet wrote:
> > Thanks for digging into this matter. Yes, keeping the flags is something I
> > have already seen. If you don't want to fix it in your main software, it
> > could be patched in D
Pierre Gruet wrote:
> Thanks for digging into this matter. Yes, keeping the flags is something I
> have already seen. If you don't want to fix it in your main software, it
> could be patched in Debian, I have already done this sort of things e.g. in
>
> https://sources.d
Hi again Philip,
I've added the necessary symbols files and uploaded ipp-crypto again for
review.
Regards,
Colin
On 09/07/2024 19:35, Phil Wyett wrote:
Colin,
Preamble...
Thanks for taking time to create this package and your contribution to Debian.
The below review is for assis
Hi Steven,
Le 14/07/2024 à 16:51, Steven Schubiger a écrit :
Pierre Gruet wrote:
I am sponsoring right now your package colorize/0.66 into Debian, as you
submitted it on mentors.debian.org last month.
Thank you so much! :)
You're welcome :)
I will juste change the version numb
Pierre Gruet wrote:
> I am sponsoring right now your package colorize/0.66 into Debian, as you
> submitted it on mentors.debian.org last month.
Thank you so much! :)
> I will juste change the version number in debian/watch : 3 to 4.
Yeah, that makes sense. It makes less sense (to me)
[Sending again so that it appears on the RFS bug page]
Le 14/07/2024 à 08:06, Pierre Gruet a écrit :
Hello Steven,
I am sponsoring right now your package colorize/0.66 into Debian, as you
submitted it on mentors.debian.org last month.
I will juste change the version number in debian/watch
Evening all Debian Developers,
Below is a curated list of packages in Debian Mentors[1] that are felt to be
ready for review and possible sponsorship into Debian.
rumur - https://mentors.debian.net/package/rumur/
RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071427
c-evo-dh - https
Control: tags -1 + moreinfo
Aidan,
Preamble...
Thank you for taking the time to create this package and your contribution to
the Debian project.
The below review is for assistance. It is offered to help submitters of
packages to Debian mentors improve their packages prior to possible
Colin,
Preamble...
Thanks for taking time to create this package and your contribution to Debian.
The below review is for assistance. It is offered to help submitters of
packages to Debian mentors improve their packages prior to possible
sponsorship into Debian. There is no obligation on behalf
Hi Phil,
I re-uploaded the ipp-crypto package with the changes you requested
except for the copyright holder changes on the debian directory as
progress on this stage is stuck pending an agreement with the current
copyright holder.
I hope the changes are OK,
Colin
On 28/06/2024 11:04, Phil
On Fri, 2024-06-28 at 14:42 -0700, Soren Stoutner wrote:
> For clarity purposes, Debian uses the name Expat for what most people call
> the MIT license.
>
> "There are many versions of the MIT license. Please use Expat instead, when
> it matches.”
>
> https://ww
For clarity purposes, Debian uses the name Expat for what most people call the
MIT license.
"There are many versions of the MIT license[1]. Please use Expat instead, when
it matches.”
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/[2]
https://www.debian.org/legal/lic
On Friday, June 28, 2024 11:26:16 AM MST Yavor Doganov wrote:
> Phil Wyett wrote:
> > To eliminate the following lintian warning.
> >
> > I debian-watch-uses-insecure-uri
>
> This is not a warning but a lintian I: tag; I don't give a flying
> flute about th
Phil Wyett wrote:
> To eliminate the following lintian warning.
>
> I debian-watch-uses-insecure-uri
This is not a warning but a lintian I: tag; I don't give a flying
flute about that.
> Maybe you could use the URL below.
>
> https://ftp.gnustep.org/pub/gnustep/core/
Hi Yavor,
To eliminate the following lintian warning.
I debian-watch-uses-insecure-uri
ftp://ftp.gnustep.org/pub/gnustep/core/ [debian/watch:4]
Maybe you could use the URL below.
https://ftp.gnustep.org/pub/gnustep/core/
Regards
Phil
--
Internet Relay Chat (IRC): kathenas
Website
On Fri, 2024-06-28 at 12:25 +0100, Phil Wyett wrote:
> Hi Kai-Chuan,
>
> Preamble...
>
> Thanks for taking time to create this package and your contribution to Debian.
>
> The below review is for assistance. It is offered to help submitters of
> packages to Debian mentor
Hi Kai-Chuan,
Preamble...
Thanks for taking time to create this package and your contribution to Debian.
The below review is for assistance. It is offered to help submitters of
packages to Debian mentors improve their packages prior to possible
sponsorship into Debian. There is no obligation on
Hi Colin,
Preamble...
Thanks for taking time to create this package and your contribution to Debian.
The below review is for assistance. It is offered to help submitters of
packages to Debian mentors improve their packages prior to possible
sponsorship into Debian. There is no obligation on
you at
some point please have an audit of the source tree and 'debian/copyright'.
philwyett@ks-windu:~/Development/builder/debian/mentoring/audacious-plugins-4.4$
lrc
en: Versions: recon 1.11 check 3.3.9-1
Parsing Source Tree
Reading copyright
Running licenseche
Your message dated Thu, 20 Jun 2024 09:55:37 +0200
with message-id
and subject line Re: RFS: debian-el/37.13 -- Emacs helpers specific to Debian
users
has caused the Debian Bug report #1073184,
regarding RFS: debian-el/37.13 -- Emacs helpers specific to Debian users
to be marked as done.
This
tps://mentors.debian.net/package/hello/>
Alternatively, you can download the package with 'dget' using this command:
dget -x
https://mentors.debian.net/debian/pool/main/d/debpic/debpic_1.0.0.dsc
Changes since the last upload:
* Initial Release.
Regards,
Aidan Gallagher
Hello,
+ ;; hence break the generated template. Suggested by suggested by Nis
Suggested by twice? :)
(uploading)
G.
OpenPGP_signature.asc
Description: OpenPGP digital signature
27; to
be recognized there. However i noticed, that the --list-cmds group 'other' scans
the /usr/bin/ directory, where our old friend 'git-debrebase' and friends
already reside and are being successfully recognized by git. Thus i prepared a
change (in my salsa repo: in
https
#x27;s not the whole story with gbp. With gbp
> you're always dealing with both a debian and an upstream branch so the MR
> model doesn't fit since it just deals with the one branch you point it
> at. That doesn't really hurt as long as you remember to push your upstream
&g
On Wed, Apr 24, 2024 at 10:06:49PM +0200, Samo Pogačnik wrote:
> Ok, so i'll prepare merge request in salsa gitlab, after pushing my
> change in my working branch?
So creating a MR is fine but it's not the whole story with gbp. With gbp
you're always dealing with both a d
where our old friend 'git-debrebase' and friends
> already reside and are being successfully recognized by git. Thus i prepared a
> change (in my salsa repo: in
> https://salsa.debian.org/spog/git-subrepo/-/tree/debian/sid) to change the
> target installation directory, which seems t
aging-tutorial.en.pdf
> I can't find a recording of it but the slides are pretty extensive.
>
> In video format there is
>
https://debconf22.debconf.org/talks/79-introduction-to-setting-up-the-debian-packaging-development-environment/
> but I can't vouch for that one.
>
obtuse, I could ofc. just make the adjustment myself but
> I'm still trying to hone your git collab maintanance skillz :)
>
Ok, so i'll prepare merge request in salsa gitlab, after pushing my change in my
working branch?
> > idea was to reverse the gbp's view on its branche
;what changed since the last version" in the end, not a blow
> by blow of the git changes we used to get there. It's a judgement call tho.
>
> +
> + [ Samo Pogačnik ]
> + * Updated debian/control info
>
> Needs to be a lot more specifict than that. In d/changelog
d in maintaining git-subrepo in Debian?
>
> I'm trying to limit my personal packaging work to stuff I actually use on a
> regular basis and apparently subrepo is not that essential, but as a DD I
> can now sponsor any uploads and help you with figuring out the Debian
> workfl
at changed since the last version" in the end, not a blow
by blow of the git changes we used to get there. It's a judgement call tho.
+
+ [ Samo Pogačnik ]
+ * Updated debian/control info
Needs to be a lot more specifict than that. In d/changelog you're talking
to two main groups
Hi Samo,
On Mon, Apr 15, 2024 at 09:13:03PM +0200, Samo Pogačnik wrote:
> Thanks for the review. I followed your suggestions above and recommited
> d/control and
> d/changelog.
>
> > As for the Vcs change: I'd prefer if we put the git repo in the debian/*
> > namespa
Hi Samo,
On Sun, Mar 31, 2024 at 01:42:48PM +0200, Samo Pogačnik wrote:
> I prepared a new git-subrepo in salsa as a fork of your project (
> https://salsa.debian.org/spog/git-subrepo). Then i updated upstream and
> prepared
debby> a new 'debian/sid' branch. Would you be
Hi Samo,
wouldn't you know it I've become a DD before I got a response to the
git-subrepo ITP/RFS ;) I also completely forgot about it until I needed it
just now.
Are you still interested in maintaining git-subrepo in Debian?
I'm trying to limit my personal packaging work to s
Hi Samo,
On Mon, Apr 01, 2024 at 07:54:09PM +0200, Samo Pogačnik wrote:
> > Workflow wise I don't see why you needed to make a merge commit at
> > d0cc659. Can you explan what you were doing?
>
> Well, after i updated the upstream branch, i wanted to preserve your
> orig
t to play around with
rebasing of debian branch onto each renewed upstream. I assume rebasing workflow
shoud somehow avoid commiting patch series into main-working branch. I
understood git-debrebase figured that out, but ... (see below)
> > >
> I wish we could use a rebase workflow wit
count, so that i am properly accessing your 'git-subrepo' repo. I was
also able to setup debian-sid chrooted environment on my old Ubuntu laptop up to
the point that i think i can successfully rebuild your current 'git-subrepo'
project using the following commands
Hi Daniel,
I prepared a new git-subrepo in salsa as a fork of your project (
https://salsa.debian.org/spog/git-subrepo). Then i updated upstream and prepared
a new 'debian/sid' branch. Would you be so kind to take a look at it and comment
on what should be changed/fixed and how
Hi Samo,
On Fri, Mar 15, 2024 at 06:42:54PM +0100, Samo Pogačnik wrote:
> Dne 11.03.2024 (pon) ob 20:18 +0100 je Daniel Gröber napisal(a):
> > Are you still interested in maintaining git-subrepo in Debian?
>
> please excuse me for my late response, but my situation from 2020/21 whe
On Mon, Apr 01, 2024 at 11:07:50PM +0200, Daniel Gröber wrote:
> I wish we could use a rebase workflow with gbp but I haven't found a way to
> do it yet. At least not with gbp import-ref as-is. We could work on a patch
> for it I suppose ;)
Looking at git-debrebase (https://www.youtube.com/watch?v
wise I don't see why you needed to make a merge commit at
> d0cc659. Can you explan what you were doing?
>
Well, after i updated the upstream branch, i wanted to preserve your original
debian/sid branch, so i renamed it and merged it into the new debian/sid branch,
based at the latest 0.
ven if what you need to know is like
> > 5% of that.
>
> Thanks for all your input, i'll try to setup the debian/build environment
> first
> and go through the provided links. Which debian-specific tools do you find
> essential in your workflow, so that i can focus on th
On Tue, 30 Apr 2024 23:08:42 +0200,
Dimitrios Antoniou wrote:
>Hi,
>
>I have a background in software engineering, albeit limited experience with
>C, C++ and Python. I'm looking to join the Debian community and start
>contributing to the project. I was hoping to get some guid
Welcome to Debian!
There are a lot of different ways someone can get started contributing to
Debian. Some of
them are described at:
https://mentors.debian.net/intro-maintainers/[1]
I would recommend reading over the resources on that page. If you have any
questions as
you go, this mailing
1 - 100 of 5300 matches
Mail list logo
