On Mon, Nov 11, 2024 at 03:45:51PM +, Aaron Boxer wrote:
> Hi Andrey,
>
> Thanks, I do have a sponsor, just have not had a response from him.
Then you should use the RFS mechanism.
--
WBR, wRAR
signature.asc
Description: PGP signature
> I have uploaded my latest package here:
> > https://mentors.debian.net/package/libgrokj2k/
> > I would greatly appreciate help uploading the package to unstable
>
>
> Please use the RFS mechanism.
>
> --
> WBR, wRAR
On Mon, Nov 11, 2024 at 01:43:19PM +, Aaron Boxer wrote:
> Dear Mentors,
>
> I have uploaded my latest package here:
> https://mentors.debian.net/package/libgrokj2k/
> I would greatly appreciate help uploading the package to unstable
Please use the RFS mechanism.
Dear Mentors,
I have uploaded my latest package here:
https://mentors.debian.net/package/libgrokj2k/
I would greatly appreciate help uploading the package to unstable
Many Thanks,
Aaron
>> Dear Mentors,
>
>> I have uploaded my latest package here:
>> https://mento
Hi Hilmar,
Thanks very much, I have submitted a bug report.
Aaron
On Mon, Mar 20, 2023 at 11:43 AM Preuße, Hilmar wrote:
> On 20.03.2023 16:38, Aaron Boxer wrote:
>
> Hi Aaron,
>
> are you subscribed to debian-devel-annou...@lists.debian.org ?
>
> > Thanks, Santiago. How do I contact the release
On 20.03.2023 16:38, Aaron Boxer wrote:
Hi Aaron,
are you subscribed to debian-devel-annou...@lists.debian.org ?
Thanks, Santiago. How do I contact the release team to ask about unblock ?
"According to schedule, we have frozen bookworm a bit more
(2023-03-12). This means that we are one step
in
> debian/changelog)
>
> Since your package doesn't have any autopkgtest, in this stage of the
> freeze, it requires an unblock from the release team, AFAIU:
> https://release.debian.org/testing/freeze_policy.html#hard
> So, before uploading, you need to get the ACK from them.
>
> Cheers,
>
> -- Santiago
>
ecord
about why you are targeting this change to testing. (And include that in
debian/changelog)
Since your package doesn't have any autopkgtest, in this stage of the
freeze, it requires an unblock from the release team, AFAIU:
https://release.debian.org/testing/freeze_policy.html#hard
So, b
Hi Folks,
I have successfully created a patched version of libgrokj2k to fix a serious
encoder bug.
https://mentors.debian.net/package/libgrokj2k/
Help uploading this to unstable would be greatly appreciated !
Thanks,
Aaron
On Thu, Sep 8, 2022 at 11:00 AM Adam Borowski wrote:
> On Thu, Sep 08, 2022 at 10:11:45AM -0400, Aaron Boxer wrote:
> > I just uploaded a new package for version 10.0 of this library.
> > Would someone be so kind as to upload the new package to unstable ?
> >
> > https://mentors.debian.net/packag
On Thu, Sep 08, 2022 at 10:11:45AM -0400, Aaron Boxer wrote:
> I just uploaded a new package for version 10.0 of this library.
> Would someone be so kind as to upload the new package to unstable ?
>
> https://mentors.debian.net/package/libgrokj2k/
--- libgrokj2k-9.7.5/debian/changelog 2022-04-1
Hi Folk,
I just uploaded a new package for version 10.0 of this library.
Would someone be so kind as to upload the new package to unstable ?
https://mentors.debian.net/package/libgrokj2k/
Many Thanks,
Aaron
On Mon, Jul 18, 2022 at 08:25:05PM +0200, David Given wrote:
> At first glance this seems a bit problematic, as it would require uploading
> packages which haven't been reviewed by a human. I'd be relying on the
> automation to spot any potential problems. But, if the packagi
seems a bit problematic, as it would require uploading
packages which haven't been reviewed by a human. I'd be relying on the
automation to spot any potential problems. But, if the packaging's not
changing --- which should be detectable --- I'm not sure that a human
review adds mu
On 2022-04-06 Adam Borowski wrote:
> On Wed, Apr 06, 2022 at 03:02:07PM +0100, Philip Wyett wrote:
> > Could someone point me to the documentation that relates to upload
> > of packages that have new binary packages i.e. name change during an
> > update? Specifically to the new/by-hand queue.
> D
On Wed, 2022-04-06 at 19:49 +0500, Andrey Rahmatullin wrote:
> On Wed, Apr 06, 2022 at 03:36:31PM +0100, Philip Wyett wrote:
> > > > Could someone point me to the documentation that relates to upload of
> > > > packages that have
> > > > new
> > > > binary
> > > > packages i.e. name change during
On Wed, Apr 06, 2022 at 03:36:31PM +0100, Philip Wyett wrote:
> > > Could someone point me to the documentation that relates to upload of
> > > packages that have new
> > > binary
> > > packages i.e. name change during an update? Specifically to the
> > > new/by-hand queue.
> > Can you explain th
On Wed, 2022-04-06 at 19:06 +0500, Andrey Rahmatullin wrote:
> On Wed, Apr 06, 2022 at 03:02:07PM +0100, Philip Wyett wrote:
> > Could someone point me to the documentation that relates to upload of
> > packages that have new
> > binary
> > packages i.e. name change during an update? Specifically
On Wed, Apr 06, 2022 at 03:37:33PM +0100, Philip Wyett wrote:
> > > Could someone point me to the documentation that relates to upload of
> > > packages that have new
> > > binary
> > > packages i.e. name change during an update? Specifically to the
> > > new/by-hand queue.
> >
> > Dunno where t
On Wed, 2022-04-06 at 16:16 +0200, Adam Borowski wrote:
> On Wed, Apr 06, 2022 at 03:02:07PM +0100, Philip Wyett wrote:
> > Could someone point me to the documentation that relates to upload of
> > packages that have new
> > binary
> > packages i.e. name change during an update? Specifically to th
On Wed, Apr 06, 2022 at 03:02:07PM +0100, Philip Wyett wrote:
> Could someone point me to the documentation that relates to upload of
> packages that have new binary
> packages i.e. name change during an update? Specifically to the new/by-hand
> queue.
Dunno where the docs are, but in short:
*
On Wed, Apr 06, 2022 at 03:02:07PM +0100, Philip Wyett wrote:
> Could someone point me to the documentation that relates to upload of
> packages that have new binary
> packages i.e. name change during an update? Specifically to the new/by-hand
> queue.
Can you explain the context for this? You ne
Hi all,
Could someone point me to the documentation that relates to upload of packages
that have new binary
packages i.e. name change during an update? Specifically to the new/by-hand
queue.
Regards
Phil
--
*** Playing the game for the games own sake. ***
WWW: https://kathenas.org
Twitter:
On 29.08.21 16:40, Baptiste Beauplat wrote:
On 2021/08/26 10:15 PM, Baptiste Beauplat wrote:
On 2021/08/26 02:41 PM, Sven Hartge wrote:
I noticed a little weirdness when uploading a package for multiple
suites, in my case for "bullseye-backports" and
"buster-backports-sloppy&
Hi Sven,
On 2021/08/26 10:15 PM, Baptiste Beauplat wrote:
> On 2021/08/26 02:41 PM, Sven Hartge wrote:
> > I noticed a little weirdness when uploading a package for multiple
> > suites, in my case for "bullseye-backports" and
> > "buster-backports-sloppy&quo
Hi Sven,
On 2021/08/26 02:41 PM, Sven Hartge wrote:
> I noticed a little weirdness when uploading a package for multiple
> suites, in my case for "bullseye-backports" and
> "buster-backports-sloppy".
>
> Reference is https://mentors.debian.net/package/radsecpro
Hello .*,
I noticed a little weirdness when uploading a package for multiple
suites, in my case for "bullseye-backports" and
"buster-backports-sloppy".
Reference is https://mentors.debian.net/package/radsecproxy/
I uploaded version 1.9.0-1~bpo10+1 first and then 1.9.0-1~
On Fri, Aug 23, 2019 at 12:11:29PM +0530, rishi gupta wrote:
> When a new package is uploaded very first time, does the foo-app_1.0.tar.xz
> and foo-app_1.0.dsc are mandatory.
> Do I need to upload both source and binary package or is it upto me if I
> want to upload just the binary package.
You al
Hi Team,
When a new package is uploaded very first time, does the foo-app_1.0.tar.xz
and foo-app_1.0.dsc are mandatory.
Do I need to upload both source and binary package or is it upto me if I
want to upload just the binary package.
Project is hosted on github and full source is available there.
Alright, thanks!
On Fri, Jul 19, 2019 at 4:44 PM Sven Hartge wrote:
>
> Nico Schlömer wrote:
>
> > From the gmsh repro-build, I'm getting
> > ```
> > /builds/science-team/gmsh/debian/output: found 38 matching files
> > ERROR: Uploading artifacts to coordina
Nico Schlömer wrote:
> From the gmsh repro-build, I'm getting
> ```
> /builds/science-team/gmsh/debian/output: found 38 matching files
> ERROR: Uploading artifacts to coordinator... too large archive
> id=227001 responseStatus=413 Request Entity Too Large status=413
> R
>From the gmsh repro-build, I'm getting
```
/builds/science-team/gmsh/debian/output: found 38 matching files
ERROR: Uploading artifacts to coordinator... too large archive
id=227001 responseStatus=413 Request Entity Too Large status=413
Request Entity Too Large token=XzzUdm1f
FATAL: t
ists.debian.org Sent: Monday,
25 February 2019, 16:04:49 GMTSubject: Re: Uploading Source Package
On Mon, Feb 25, 2019 at 11:00 AM Popout3D - popou...@yahoo.com wrote:
> ... I need to upload a source package.
>
> . . . The command is dput
> .changes which doesn't specify source/bi
On Mon, Feb 25, 2019 at 03:41:48PM +, Popout3D wrote:
> So it looks like I've got all the possible files I might need. The command is
> dput .changes which doesn't specify source/binary, so how do I ensure
> that dput uploads the source package?
.changes specifies what files will be uploaded,
On Mon, Feb 25, 2019 at 11:00 AM Popout3D - popou...@yahoo.com wrote:
> ... I need to upload a source package.
>
> . . . The command is dput
> .changes which doesn't specify source/binary, so how do I ensure that
> dput uploads the source package?
build the source, then dput the .changes of the
Looks good, uploading...
appened a few days ago, the importer crashed. At least for
> me it's more helpful if people email supp...@mentors.debian.net which I
> tend to read sooner than debian-mentors.
Hiccups have occurred before, so I thought the server is busy due to
people uploading more packages over the weeken
On 26.12.18 09:47, Mattia Rizzolo wrote:
> On Wed, Dec 26, 2018 at 10:10:50AM +0200, Yavor Doganov wrote:
>> On Tue, 25 Dec 2018 22:09:20 +0200,
>> Gunter Königsmann wrote:
>>> I have uploaded the new version to wxMaxima to mentors today. At least
>>> dput did tell me that the upload succeeded, bu
On Wed, Dec 26, 2018 at 10:10:50AM +0200, Yavor Doganov wrote:
> On Tue, 25 Dec 2018 22:09:20 +0200,
> Gunter Königsmann wrote:
> > I have uploaded the new version to wxMaxima to mentors today. At least
> > dput did tell me that the upload succeeded, but it never appeared on
> > mentors.debian.net.
On Tue, 25 Dec 2018 22:09:20 +0200,
Gunter Königsmann wrote:
> I have uploaded the new version to wxMaxima to mentors today. At least
> dput did tell me that the upload succeeded, but it never appeared on
> mentors.debian.net. Also I didn't receive the info that the package is
> uploaded.
I had ex
pload was able
to upload it again.
Since then there was no answer. A try to reupload the program yields
"403 forbidden".
Other programs seem to have succeeded uploading in the same timeframe =>
Don't know if I did anything that causes some process on the server to
block/crash.
Hi!!
El 27/10/18 a les 03:11, Paul Wise ha escrit:
> On Fri, Oct 26, 2018 at 8:33 PM Leopold Palomo-Avellaneda wrote:
>
>> I have an strange doubt. One of the package I maintain is a library (ompl)
>> and
>> now I would like to push a new version with new ABI.
>
> It sounds like you are upstrea
On Fri, Oct 26, 2018 at 8:33 PM Leopold Palomo-Avellaneda wrote:
> I have an strange doubt. One of the package I maintain is a library (ompl) and
> now I would like to push a new version with new ABI.
It sounds like you are upstream for this library?
Either way you might want to use abipkgdiff (
Hi,
I have an strange doubt. One of the package I maintain is a library (ompl) and
now I would like to push a new version with new ABI. I have done with others
libraries the procedure of ABI transition, with rebuild packages, etc. and it's
clear.
However, in this case there's no transition with
can also get their uid into the backports
> ACL. Please follow the instructions for Debian Developers."
>
> "The Debian Maintainer needs to have upload rights for the specific
> package they want to upload to backports (the same right they need for
> uploading that pa
ticket from other DDs is needed.
This is not true.
Non-DDs cannot look at tickets in the system, but they can submit them.
I was a DM uploading to backports long before becoming a DD and I
submitted the request to RT myself.
--
Sean Whitton
ease open a ticket in the debian request
tracker - please use the backports queue for the ticket."
[...]
"Debian Maintainers (DM) can also get their uid into the backports
ACL. Please follow the instructions for Debian Developers."
"The Debian Maintainer needs to have upload rights for th
;
> --
> 879881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879881
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> Date: Wed, 10 Jan 2018 09:13:07 +0200
> From: Jonathan Carter
> To: 879881-d...@bugs.debian.org
> Subject: Uploading pa
On Fri, Dec 1, 2017 at 7:46 PM, Sascha Manns wrote:
> Now i have fixed these things, and built a new package version. Should
> i delete the old package before uploading the new package version?
IIRC, reuploading will replace the older version.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Hello list,
i have uploaded a package some weeks ago to mentors.debian.net, which
was reviewed by a Sponsor. He mentioned some things to fix before
uploading to the official archive.
Now i have fixed these things, and built a new package version. Should
i delete the old package before uploading
On Mon, Aug 14, 2017 at 11:56:58AM +0200, Alec Leamas wrote:
> but need help with actually
> uploading the fix. Is there anyone out there which could give me a hand?
Several people here can help you out, but the process of asking for
sponsorship here is done by filing a RFS (Reque
which resolves it on mentors [1], but need help
with actually uploading the fix. Is there anyone out there which could
give me a hand?
Cheers!
--alec
[1] https://mentors.debian.net/package/lirc
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872074
PS: The 0.10.0-1 on mentors does not
Control: tag -1 pending
Yes, davmail_4.7.3.2438-1 will be uploaded.
Changes I made:
diff --git a/debian/changelog b/debian/changelog
index 7b11665..0d91d6d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -27,6 +27,10 @@ davmail (4.7.3.2438-1) unstable; urgency=medium
* debian/patches:
rt errors or warnings in my package.
>>>>
>>>
>>> Did you received the email from mentors confirming ?
>>>
>>>
>>> regards,
>>>
>>
>> Not, I didn't.
>>
>>
>
>
> I've upload another de
penning?
>>>
>>> lintian doesn't report errors or warnings in my package.
>>>
>>
>> Did you received the email from mentors confirming ?
>>
>>
>> regards,
>>
>
> Not, I didn't.
>
>
I've upload another debian pa
rs confirming ?
>>
>>
>> regards,
>>
>
> Not, I didn't.
>
>
I've upload another debian package with the same result.
$ dput mentors elisp-es_1.0-1_amd64.changes
Checking signature on .changes
gpg: Firmado el lun 26 oct 2015 17:48:37 CET usando clave
El 23/10/15 a las 17:46, Herbert Parentes Fortes Neto (hpfn) escribió:
> Hi,
>
>>
>> I've upload my debian package gccintro-es with dput, my dput.cfg is:
>>
>> [mentors]
>> fqdn = mentors.debian.net
>> incoming = /upload
>> method = http
>> allow_unsigned_uploads = 0
>> progress_indicator = 2
>> #
Hi,
>
> I've upload my debian package gccintro-es with dput, my dput.cfg is:
>
> [mentors]
> fqdn = mentors.debian.net
> incoming = /upload
> method = http
> allow_unsigned_uploads = 0
> progress_indicator = 2
> # Allow uploads for UNRELEASED packages
> allowed_distributions = .*
>
> The upload
Hello,
I've upload my debian package gccintro-es with dput, my dput.cfg is:
[mentors]
fqdn = mentors.debian.net
incoming = /upload
method = http
allow_unsigned_uploads = 0
progress_indicator = 2
# Allow uploads for UNRELEASED packages
allowed_distributions = .*
The upload process was successful
Sorry for spamming the list.
I had to remove some X-SA headers.
On Tue, 2015-01-27 at 23:51 +0100, W. van den Akker wrote:
> Hi mentors,
>
> Can any of the mentors upload the package Jabberd2 for me to unstable?
> I tried to get it in, but previous uploaders are to busy or non
> responsive. So
Hi mentors,
Can any of the mentors upload the package Jabberd2 for me to unstable?
I tried to get it in, but previous uploaders are to busy or non
responsive. So I need another volunteer who is willing to upload it for me.
There are a few fixes (missing source file and updated copyright file).
Th
On Tue, 2015-01-27 at 23:41 +0100, W. van den Akker wrote:
>
>
> Hi mentors,
>
> Can any of the mentors upload the package Jabberd2 for me to unstable?
> I tried to get it in, but previous uploaders are to busy or non
> responsive. So I need another volunteer who is willing to upload it for me.
* Osamu Aoki , 2014-04-23, 23:55:
If the package "foo" depends on the package "libbar-dev" and
"libbar-dev" is in new queue waiting for approval, can I upload the
package "foo" build on the sid chroot with the package "libbar-dev"
manually installed to it?
Or I should wait the package "libbar
Hi,
If the package "foo" depends on the package "libbar-dev" and
"libbar-dev" is in new queue waiting for approval, can I upload the
package "foo" build on the sid chroot with the package "libbar-dev"
manually installed to it?
Or I should wait the package "libbar-dev" to be moved to sid?
Regards
Thanks,
Is someone willing to upload the new version of the package?
It close a bug.
The package is here: git://anonscm.debian.org/pkg-xmpp/jabberd2.git
if also possible upload this one. It removes a obsolete dependency
git://anonscm.debian.org/pkg-xmpp/jabber-muc.git
Thanks!
WIllem
On Fri, 201
Hi,
> if also possible upload this one. It removes a obsolete dependency
> git://anonscm.debian.org/pkg-xmpp/jabber-muc.git
Let's see:
-Recommends: jabberd14 | jabberd2
+Recommends: jabberd2
I do not think that such small change requires upload.
Small note: I have fixed tiny typo in debian/copy
Package: jabberd2
Version: 2.2.17-1
Severity: serious
Justification: Policy 12.5
X-Debbugs-Cc: debian-mentors@lists.debian.org
Hi,
> Is someone willing to upload the new version of the package?
> It close a bug.
> The package is here: git://anonscm.debian.org/pkg-xmpp/jabberd2.git
At first you
Thank you very much, but I got it already.
Now I'm searching a sponsor :-)
Best Regards,
Julian Goestl
Am 10.02.2014 13:48, schrieb Tobias Frost:
There isn't a step-by-step manual for beginners.
I think, it should be added too.
Best Regards,
Julian Goestl
Can you elaborate where you're stuck
> There isn't a step-by-step manual for beginners.
> I think, it should be added too.
>
> Best Regards,
> Julian Goestl
Can you elaborate where you're stuck?
( eg using the checklist at http://mentors.debian.net/intro-maintainers , "4
Publish your Package")
Tobias
> Am 05.02.2014 20:33, schrieb
There isn't a step-by-step manual for beginners.
I think, it should be added too.
Best Regards,
Julian Goestl
Am 05.02.2014 20:33, schrieb Bart Martens:
On Wed, Feb 05, 2014 at 02:39:15PM +0100, Julian Göstl wrote:
Hi,
can anybody explain step-by-step how correctly sign and upload a
package t
On Wed, Feb 5, 2014 at 10:39 PM, Dariusz Dwornikowski wrote:
> 1. You have to create a key according to [1]
Also be sure to read the OpenPGP best practices:
https://we.riseup.net/debian/openpgp-best-practices
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-m
Hi,
1. You have to create a key according to [1]
2. You need to create your package, place your email and name in changelog.
3. Run debuild and debuild will sign your package, taking the key for the
email you have in your changelog.
4. As for mentors, here you have the instructions [2], section 4.
Hi,
can anybody explain step-by-step how correctly sign and upload a package
to mentors.debian.net?
Greetings
Julian Goestl
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.
Hi Elena,
thank you for your answer. Yes you are right, I had typo and hence it
uploads to main archive.
Matus Valo
On Tue, Jan 7, 2014 at 10:33 AM, Elena ``of Valhalla'' <
elena.valha...@gmail.com> wrote:
> On 2014-01-07 at 10:11:50 +0100, matus valo wrote:
> > I haven't found documentation a
On 2014-01-07 at 10:11:50 +0100, matus valo wrote:
> I haven't found documentation about procedure how to upload new version of
> package to mentors.debian.net. So I tried to upload it the same way as I
> uploaded original version. Nothing happened.
dput creates a $PKG.$ARCHIVE.upload file to pre
Hi,
I have uploaded successfully a package to mentors.debian.net. Afterwards I
found a sponsor, but he has some suggestions to my package. I implemented all
of them and then I tried to upload new version of my package to
mentors.debian.net. And here my troubles began.
I haven't found documentatio
On Fri, Aug 16, 2013 at 09:45:42AM +0200, Ross Gammon wrote:
> > I think lintian should catch that even with default options
> > (unless you "fixed" the warnings by making a NMU).
> Yes - I have prepared it as a NMU. But I am holding back and hoping
> the maintainer gets in touch (I have contacted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/16/2013 07:44 AM, Andrey Rahmatullin wrote:
> I think lintian should catch that even with default options
> (unless you "fixed" the warnings by making a NMU).
>
Yes - I have prepared it as a NMU. But I am holding back and hoping
the maintainer g
On Thu, Aug 15, 2013 at 11:11:08PM +0200, Ross Gammon wrote:
> >> But I notice on mentors.debian.net that there is a message
> >> saying that "the uploader is not in the package's "Maintainer"
> >> or "Uploaders" field.
> > Did y
#x27;s "Maintainer"
>> or "Uploaders" field.
> Did you run lintian before uploading?
>
Yes - and fixed all the errors and warnings, and the other easy things.
Even running lintian in pedantic mode does not pick this up though.
lintian -i -I --pedantic xyz.changes
Am
On Thu, Aug 15, 2013 at 10:05:32PM +0200, Ross Gammon wrote:
> But I notice on mentors.debian.net that there is a message saying that
> "the uploader is not in the package's "Maintainer" or "Uploaders" field.
Did you run lintian before uploading?
--
W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/2013 03:36 PM, Kumar Appaiah wrote:
> On Sun, Aug 11, 2013 at 04:16:31PM +0600, Andrey Rahmatullin
> wrote:
> Thanks Kumar - the "-k " did it! I saw it in
> --help, but I didn't think I would need it if I only had
> the one key.
On Sun, Aug 11, 2013 at 04:16:31PM +0600, Andrey Rahmatullin wrote:
> > > > Thanks Kumar - the "-k " did it! I saw it in --help, but I
> > > > didn't think I would need it if I only had the one key. Why didn't I
> > > > try it?!?
> > > You don't need to pass -k or similar options to any Debian tool
On Sat, Aug 10, 2013 at 10:16:59PM -0400, Kumar Appaiah wrote:
> > > > Personally, I use debsign -k to ensure
> > > > that my package is signed. Following this, you can open the
> > > > changes file and the dsc file to see that they have been
> > > > clearsigned.
> > >
> > > Thanks Kumar - the
On Sun, Aug 11, 2013 at 02:41:02AM +0600, Andrey Rahmatullin wrote:
> > > Personally, I use debsign -k to ensure
> > > that my package is signed. Following this, you can open the
> > > changes file and the dsc file to see that they have been
> > > clearsigned.
> >
> > Thanks Kumar - the "-k " d
On Sat, Aug 10, 2013 at 08:23:06PM +0200, Ross Gammon wrote:
> >> I have tried signing the the changes file with debsign "debsign
> >> foopackage.changes", but I assume this is just like the signing
> >> that the standard dpkg-buildpackage does?
> >
> > Personally, I use debsign -k to ensure
On Sat, Aug 10, 2013 at 08:23:06PM +0200, Ross Gammon wrote:
> On 08/10/2013 06:17 PM, Kumar Appaiah wrote:
> > Personally, I use debsign -k to ensure
> > that my package is signed. Following this, you can open the
> > changes file and the dsc file to see that they have been
> > clearsigned.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/10/2013 06:17 PM, Kumar Appaiah wrote:
> On Sat, Aug 10, 2013 at 04:38:28PM +0200, Ross Gammon wrote:
>> I have tried signing the the changes file with debsign "debsign
>> foopackage.changes", but I assume this is just like the signing
>> that
On Sat, Aug 10, 2013 at 04:38:28PM +0200, Ross Gammon wrote:
> I have tried signing the the changes file with debsign "debsign
> foopackage.changes", but I assume this is just like the signing that
> the standard dpkg-buildpackage does?
Personally, I use debsign -k to ensure that
my package is s
On Sat, 10 Aug 2013 16:38:28 +0200,
Ross Gammon wrote:
>Hi all,
>
>I have been googling this for a while now. Lots of people have
>problems with their keys, but not quite my problem!
>
>I have created a package with "dpkg-buildpackage -us -uc" because my
>key is not yet (but almost) signed by someo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I have been googling this for a while now. Lots of people have
problems with their keys, but not quite my problem!
I have created a package with "dpkg-buildpackage -us -uc" because my
key is not yet (but almost) signed by someone in the debia
Hi,
> > On Sun, Sep 30, 2012 at 01:12:38PM +0200, Daniel Pocock wrote:
> >> Can someone please let me know if this is my fault or a server
> >> issue?
> > There is already turnserver 0.6-1 on the mentors incoming queue,
> > did you try to upload it twice?
> >
>
> Yes, I made another change and t
On Sun, Sep 30, 2012 at 02:36:39PM +0200, Arno Töll wrote:
> Can someone please let me know if this is my fault or a server
> issue?
> >>> There is already turnserver 0.6-1 on the mentors incoming queue,
> >>> did you try to upload it twice?
> >> Yes, I made another change and then tried
Hi,
On 30.09.2012 14:30, Andrey Rahmatullin wrote:
> On Sun, Sep 30, 2012 at 02:23:26PM +0200, Daniel Pocock wrote:
Can someone please let me know if this is my fault or a server
issue?
>>> There is already turnserver 0.6-1 on the mentors incoming queue,
>>> did you try to upload it twic
On Sun, Sep 30, 2012 at 02:23:26PM +0200, Daniel Pocock wrote:
> >> Can someone please let me know if this is my fault or a server
> >> issue?
> > There is already turnserver 0.6-1 on the mentors incoming queue,
> > did you try to upload it twice?
> Yes, I made another change and then tried to uplo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/09/12 13:26, Andrey Rahmatullin wrote:
> On Sun, Sep 30, 2012 at 01:12:38PM +0200, Daniel Pocock wrote:
>> Can someone please let me know if this is my fault or a server
>> issue?
> There is already turnserver 0.6-1 on the mentors incoming queu
On Sun, Sep 30, 2012 at 01:12:38PM +0200, Daniel Pocock wrote:
> Can someone please let me know if this is my fault or a server issue?
There is already turnserver 0.6-1 on the mentors incoming queue, did you
try to upload it twice?
--
WBR, wRAR
signature.asc
Description: Digital signature
ture from "Daniel Pocock "
gpg: aka "Daniel Pocock "
gpg: aka "Daniel Pocock "
Good signature on /home/daniel/ws/turnserver.org/turnserver_0.6-1.dsc.
Uploading to mentors (via http to mentors.debian.net):
Uploading turnserver_0.6-1.dsc: Upload failed:
I'm having trouble uploading a package to mentors.debian.net:
$ dput mentors-ftp libre-jigsaw-pics_2012.02.14-1_amd64.changes
Checking signature on .changes
gpg: Signature made Sun 26 Feb 2012 09:02:18 PM PST using RSA key ID
D8B67ED0
gpg: Good signature from "Jonathan Hulka "
Go
On Thu, Jul 14, 2011 at 8:48 PM, Jakub Wilk wrote:
> * Kilian Krause , 2011-07-14, 20:34:
>>
>> If you can confirm that the symbols file for your last version and this
>> version match up perfectly, then the SONAME shouldn't have been bumped in
>> the first place
>
> Err, no, you can't conclude th
1 - 100 of 276 matches
Mail list logo
