[RFS] I need an sponsor for 2 Go packages
Hello I'm the maintainer of asciinema, a while ago upstream decided to rewrite it in Go, previously it was a Python app. I've made a package for it, and the 2 dependencies that were missing in the archive, one of those dependencies was already sponsored/uploaded, but the sponsor has no time to sponsor the 2 missing packages. asciinema git.debian.org:/git/pkg-go/packages/asciinema.git https://mentors.debian.net/debian/pool/main/a/asciinema/asciinema_1.2.0-1.dsc golang-github-creack-termios git.debian.org:/git/pkg-go/packages/golang-github-creack-termios.git https://mentors.debian.net/debian/pool/main/g/golang-github-creack-termios/golang-github-creack-termios_0.0~git20160520.0.01ff290-1.dsc I'm a DM, I already maintain other packages and have upload permissions, this uploads would close 3 bugs. I thank in advance any review/sponsor, upstream doesn't support the Python version anymore so I would like to have the Go version in time for the freeze -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa signature.asc Description: PGP signature
Re: [RFS] I need an sponsor for 2 Go packages
On Thu, Jul 28, 2016 at 02:04:02AM +0200, Daniele Tricoli wrote: > Hello Gustavo, > > On Wednesday, July 27, 2016 03:17:29 PM gustavo panizzo wrote: > > I'm the maintainer of asciinema, a while ago upstream decided to rewrite > > it in Go, previously it was a Python app. > > It seems upstream went back to Python: > http://blog.asciinema.org/post/and-now-for-something-completely-different/ :-O > > I think it is better to update to 1.3, and skip the Go release. I will do that, what a waste of time!. thanks for the catch, I had the package ready for some time, I didn't check their blog > > Kind regards, > > -- > Daniele Tricoli 'eriol' > https://mornie.org -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa signature.asc Description: PGP signature
Re: [RFS] I need an sponsor for 2 Go packages
On Wed, Jul 27, 2016 at 05:13:16PM +, Gianfranco Costamagna wrote: > Hi, > Gianfranco Upstream went back to Python, so I won't upload this version or its needed dependency, i if you are interested in golang-github-creack-termios, you can take the package from alioth, its ready IMHO, only 3 lintian warnings - debian-watch-may-check-gpg-signature upstream doesn't do releases, I placed a debian/watch file in place in case they start doing them. - no-upstream-changelog upstream doesn't keep a changelog - extended-description-is-probably-too-short upstream readme.md file is only 1 sentence, this pkg is an small library there is not much to say about it thanks for your time, I apologize for the change of plans. PS: can I ping you when I have the new asciinema package? -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa signature.asc Description: PGP signature
Re: [RFS] I need an sponsor for 2 Go packages
On Thu, Jul 28, 2016 at 06:26:10AM +, Gianfranco Costamagna wrote: > Hi, > > > >PS: can I ping you when I have the new asciinema package? > > > I'm not a go developer, so somebody from your team might be better suitable > to look at the packages, but you can count on me as a backup sponsor. > (BTW go seems a really nice and funny language, so I might learn it one day) > > > and if the package becomes Python again... even better, I can do it Gianfranco, i've uploaded version 1.3.0-1 to mentors, would you sponsor it? https://mentors.debian.net/debian/pool/main/a/asciinema/asciinema_1.3.0-1.dsc and git repo on alioth ssh://git.debian.org/git/collab-maint/asciinema.git thanks! -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa signature.asc Description: PGP signature
Re: [RFS] I need an sponsor for 2 Go packages
On Fri, Jul 29, 2016 at 03:22:27PM +, Gianfranco Costamagna wrote: > Hi, > > >Gianfranco, i've uploaded version 1.3.0-1 to mentors, would you sponsor it? > > > >https://mentors.debian.net/debian/pool/main/a/asciinema/asciinema_1.3.0-1.dsc > > > uploaded with one change: > Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/asciinema.git > > > ^^ this is the updated Vcs field, gitweb is dead and unsupported (and broken) still works for this pkg, i verified it. for consistency i will keep the change on the next upload > > thanks, thank you! > > G. -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa
iptables-persistent/1.0.4+nmu1 [NMU] [RC]
Hello, I'm looking for a sponsor for my NMU on iptables-persistent It closes an RC bug, I've validated the fix my machines with different network configurations. the debdiff is attached I've worked with iptables-persistent git repo but I won't push my changes until the updated package is on the archive. Also the binary can be downloaded from -mentors https://mentors.debian.net/debian/pool/main/i/iptables-persistent/iptables-persistent_1.0.4+nmu1.dsc Changes since the last upload: iptables-persistent (1.0.4+nmu1) unstable; urgency=low * Non-maintainer upload. * Loads the firewall before network-pre.target, as suggested by systemd upstream. (Closes: #829640). thanks! -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa diff -Nru iptables-persistent-1.0.4/debian/changelog iptables-persistent-1.0.4+nmu1/debian/changelog --- iptables-persistent-1.0.4/debian/changelog 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/debian/changelog 2016-08-21 13:05:39.0 +0800 @@ -1,3 +1,11 @@ +iptables-persistent (1.0.4+nmu1) unstable; urgency=low + + * Non-maintainer upload. + * Loads the firewall before network-pre.target, as suggested by systemd +upstream. (Closes: #829640). + + -- gustavo panizzo Sun, 21 Aug 2016 13:05:39 +0800 + iptables-persistent (1.0.4) unstable; urgency=medium * [d52b9e] During flush, set policy before flushing rules (Closes: #749790) diff -Nru iptables-persistent-1.0.4/debian/compat iptables-persistent-1.0.4+nmu1/debian/compat --- iptables-persistent-1.0.4/debian/compat 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/debian/compat 2016-08-21 13:05:06.0 +0800 @@ -1 +1 @@ -7 +9 diff -Nru iptables-persistent-1.0.4/debian/control iptables-persistent-1.0.4+nmu1/debian/control --- iptables-persistent-1.0.4/debian/control 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/debian/control 2016-08-21 13:05:06.0 +0800 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Jonathan Wiltshire Build-Depends: debhelper (>= 7.0.50~), dh-systemd, po-debconf -Standards-Version: 3.9.5 +Standards-Version: 3.9.6 Vcs-Browser: http://anonscm.debian.org/cgit/collab-maint/iptables-persistent.git/ Vcs-Git: git://anonscm.debian.org/collab-maint/iptables-persistent.git diff -Nru iptables-persistent-1.0.4/debian/rules iptables-persistent-1.0.4+nmu1/debian/rules --- iptables-persistent-1.0.4/debian/rules 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/debian/rules 2016-08-21 13:05:06.0 +0800 @@ -4,5 +4,5 @@ dh_installinit -- start 37 S . stop 37 0 1 6 . %: - dh --with systemd $@ + dh $@ --with systemd diff -Nru iptables-persistent-1.0.4/plugins/15-ip4tables iptables-persistent-1.0.4+nmu1/plugins/15-ip4tables --- iptables-persistent-1.0.4/plugins/15-ip4tables 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/plugins/15-ip4tables 2016-08-21 13:05:06.0 +0800 @@ -35,8 +35,8 @@ if [ ! -f /proc/net/ip_tables_names ]; then echo "Warning: skipping IPv4 (no modules loaded)" elif [ -x /sbin/iptables-save ]; then -touch /etc/iptables/rules.v4 -chmod 0640 /etc/iptables/rules.v4 + touch /etc/iptables/rules.v4 + chmod 0640 /etc/iptables/rules.v4 iptables-save > /etc/iptables/rules.v4 if [ $? -ne 0 ]; then rc=1 diff -Nru iptables-persistent-1.0.4/plugins/25-ip6tables iptables-persistent-1.0.4+nmu1/plugins/25-ip6tables --- iptables-persistent-1.0.4/plugins/25-ip6tables 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/plugins/25-ip6tables 2016-08-21 13:05:06.0 +0800 @@ -35,8 +35,8 @@ if [ ! -f /proc/net/ip6_tables_names ]; then log_action_cont_msg "Warning: skipping IPv6 (no modules loaded)" elif [ -x /sbin/ip6tables-save ]; then -touch /etc/iptables/rules.v6 -chmod 0640 /etc/iptables/rules.v6 + touch /etc/iptables/rules.v6 + chmod 0640 /etc/iptables/rules.v6 ip6tables-save > /etc/iptables/rules.v6 if [ $? -ne 0 ]; then rc=1 diff -Nru iptables-persistent-1.0.4/systemd/netfilter-persistent.service iptables-persistent-1.0.4+nmu1/systemd/netfilter-persistent.service --- iptables-persistent-1.0.4/systemd/netfilter-persistent.service 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/systemd/netfilter-persistent.service 2016-08-21 13:05:39.0 +0800 @@ -1,7 +1,8 @@ [Unit] Description=netfilter persistent configuration DefaultDependencies=no -Before=network.target +Before=network-pre.target +Wants=network-pre.target Wants=systemd-modules-load.service local-fs.target After=systemd-modules-load.service local-fs.target signature.asc Description: PGP signature
Bug#835081: RFS: iptables-persistent/1.0.4+nmu1 [NMU] [RC]
Gianfranco/BTS, here is a new debdiff with the changes discused yesterday. cheers -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa diff -Nru iptables-persistent-1.0.4/debian/changelog iptables-persistent-1.0.4+nmu1/debian/changelog --- iptables-persistent-1.0.4/debian/changelog 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/debian/changelog 2016-08-21 13:05:39.0 +0800 @@ -1,3 +1,18 @@ +iptables-persistent (1.0.4+nmu1) unstable; urgency=low + + [ Jonathan Wiltshire ] + * Update debhelper to compat level 9 + * Standards version 3.9.6 no changes needed. + * Re-tab plugins/15-ip4tables and plugins/25-ip6tables + + [ gustavo panizzo ] + * Non-maintainer upload. + * Starts netfilter-persistent service before network-pre.target, +as suggested by systemd upstream. Thanks to Patrick Schleizer +(Closes: #829640). + + -- gustavo panizzo Sun, 21 Aug 2016 13:05:39 +0800 + iptables-persistent (1.0.4) unstable; urgency=medium * [d52b9e] During flush, set policy before flushing rules (Closes: #749790) diff -Nru iptables-persistent-1.0.4/debian/compat iptables-persistent-1.0.4+nmu1/debian/compat --- iptables-persistent-1.0.4/debian/compat 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/debian/compat 2016-08-21 13:05:06.0 +0800 @@ -1 +1 @@ -7 +9 diff -Nru iptables-persistent-1.0.4/debian/control iptables-persistent-1.0.4+nmu1/debian/control --- iptables-persistent-1.0.4/debian/control 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/debian/control 2016-08-21 13:05:06.0 +0800 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Jonathan Wiltshire Build-Depends: debhelper (>= 7.0.50~), dh-systemd, po-debconf -Standards-Version: 3.9.5 +Standards-Version: 3.9.6 Vcs-Browser: http://anonscm.debian.org/cgit/collab-maint/iptables-persistent.git/ Vcs-Git: git://anonscm.debian.org/collab-maint/iptables-persistent.git diff -Nru iptables-persistent-1.0.4/debian/rules iptables-persistent-1.0.4+nmu1/debian/rules --- iptables-persistent-1.0.4/debian/rules 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/debian/rules 2016-08-21 13:05:06.0 +0800 @@ -4,5 +4,5 @@ dh_installinit -- start 37 S . stop 37 0 1 6 . %: - dh --with systemd $@ + dh $@ --with systemd diff -Nru iptables-persistent-1.0.4/plugins/15-ip4tables iptables-persistent-1.0.4+nmu1/plugins/15-ip4tables --- iptables-persistent-1.0.4/plugins/15-ip4tables 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/plugins/15-ip4tables 2016-08-21 13:05:06.0 +0800 @@ -35,8 +35,8 @@ if [ ! -f /proc/net/ip_tables_names ]; then echo "Warning: skipping IPv4 (no modules loaded)" elif [ -x /sbin/iptables-save ]; then -touch /etc/iptables/rules.v4 -chmod 0640 /etc/iptables/rules.v4 + touch /etc/iptables/rules.v4 + chmod 0640 /etc/iptables/rules.v4 iptables-save > /etc/iptables/rules.v4 if [ $? -ne 0 ]; then rc=1 diff -Nru iptables-persistent-1.0.4/plugins/25-ip6tables iptables-persistent-1.0.4+nmu1/plugins/25-ip6tables --- iptables-persistent-1.0.4/plugins/25-ip6tables 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/plugins/25-ip6tables 2016-08-21 13:05:06.0 +0800 @@ -35,8 +35,8 @@ if [ ! -f /proc/net/ip6_tables_names ]; then log_action_cont_msg "Warning: skipping IPv6 (no modules loaded)" elif [ -x /sbin/ip6tables-save ]; then -touch /etc/iptables/rules.v6 -chmod 0640 /etc/iptables/rules.v6 + touch /etc/iptables/rules.v6 + chmod 0640 /etc/iptables/rules.v6 ip6tables-save > /etc/iptables/rules.v6 if [ $? -ne 0 ]; then rc=1 diff -Nru iptables-persistent-1.0.4/systemd/netfilter-persistent.service iptables-persistent-1.0.4+nmu1/systemd/netfilter-persistent.service --- iptables-persistent-1.0.4/systemd/netfilter-persistent.service 2016-01-03 03:46:08.0 +0800 +++ iptables-persistent-1.0.4+nmu1/systemd/netfilter-persistent.service 2016-08-21 13:05:39.0 +0800 @@ -1,10 +1,16 @@ [Unit] Description=netfilter persistent configuration DefaultDependencies=no -Before=network.target + +Before=network-pre.target +Wants=network-pre.target + Wants=systemd-modules-load.service local-fs.target After=systemd-modules-load.service local-fs.target +Conflicts=shutdown.target +Before=shutdown.target + [Service] Type=oneshot RemainAfterExit=yes @@ -13,4 +19,3 @@ [Install] WantedBy=multi-user.target - signature.asc Description: PGP signature
How long to wait between RFA and QA upload?
Hello Recently I NMU'ed tsocks, as the shape of the package wasn't good [1] in the RFS email I said that I'd try to get the package orphaned so I can do a proper QA upload. The maintainer orphaned the package 2 days ago, #842555. I don't want to adopt the package, but I do use it so I want to see it in good shape, how long should I wait for others that may adopt the package before I do a QA upload?. I was going to send a notice regarding my QA upload to the O bug but I think it may discourage people from adopting the package. The only guidance I found is 2 weeks, https://qa.debian.org/orphaned.html TL;DR how long should I wait between an O bug and a QA upload? thanks! [1] we can further discuss this, but I don't think is necessary at this point -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa signature.asc Description: PGP signature
Re: How long to wait between RFA and QA upload?
On Tue, Nov 01, 2016 at 06:38:13AM +0100, Adam Borowski wrote: ... > > Orphaned packages are up for grabs the moment the O is filed. thanks to Adam, Paul, and Gianfranco for your responses, I'll start to work on the QA upload asap cheers! -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa
Re: debexpo bug on upload
On Sun, Nov 13, 2016 at 01:20:46AM +1100, Scott Leggett wrote: > Unfortunately, I spoke too soon.. the .buildinfo upload failed with 403 > Forbidden again :( Remove the .buildinfo line from the .changes file, then sign and upload. mentors.d.n does not accept .buildinfo files yet > > Would you be able to remove that file too? :) AFAIK, there is a cronjob that removes the incomplete uploads after some time -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa
Re: can't upldoad to mentors
Remove the buildinfo line from the changes file, sign, and upload again On November 16, 2016 12:53:46 AM GMT+08:00, "Félix Sipma" wrote: >Hi! > >It seems like I can't upload to mentors anymore... Do you think there >is a >problem on my side? > >$ dput mentors ../build-area/patat_0.4.0.0-1_amd64.changes >Uploading patat using http to mentors (host: mentors.debian.net; >directory: /upload) >running checksum: verify checksums before uploading >running gpg: check GnuPG signatures before the upload >gpg: Signature made 2016-11-15T15:29:52 CET >gpg:using RSA key >611F861BAE64C6C14A26522FA710823E33BDDA81 >gpg: Good signature from "Félix Sipma " >[ultimate] >gpg: aka "Félix Sipma " >[ultimate] >gpg: aka "Félix Sipma " >[ultimate] >Primary key fingerprint: 2E6B 7C0E 128B 8F9B 16DA A76A 5857 883E 277D >B3CC > Subkey fingerprint: 611F 861B AE64 C6C1 4A26 522F A710 823E 33BD DA81 > >running suite-mismatch: check the target distribution for common errors >running protected-distribution: warn before uploading to distributions >where a special policy applies >Uploading patat_0.4.0.0-1.dsc >Upload permissions error > > You either don't have the rights to upload a file, or, if this is on >ftp-master, you may have tried to overwrite a file already on the >server. > >Continuing anyway in case you want to recover from an incomplete >upload. >No file was uploaded, however. >Uploading patat_0.4.0.0.orig.tar.gz >Upload permissions error > > You either don't have the rights to upload a file, or, if this is on >ftp-master, you may have tried to overwrite a file already on the >server. > >Continuing anyway in case you want to recover from an incomplete >upload. >No file was uploaded, however. >Uploading patat_0.4.0.0-1.debian.tar.xz >^[[AUpload permissions error > > You either don't have the rights to upload a file, or, if this is on >ftp-master, you may have tried to overwrite a file already on the >server. > >Continuing anyway in case you want to recover from an incomplete >upload. >No file was uploaded, however. >Uploading patat_0.4.0.0-1_20161115T142950z-7b479c6b.buildinfo >Upload permissions error > > You either don't have the rights to upload a file, or, if this is on >ftp-master, you may have tried to overwrite a file already on the >server. > >Continuing anyway in case you want to recover from an incomplete >upload. >No file was uploaded, however. >Uploading patat_0.4.0.0-1_amd64.deb >Upload permissions error > > You either don't have the rights to upload a file, or, if this is on >ftp-master, you may have tried to overwrite a file already on the >server. > >Continuing anyway in case you want to recover from an incomplete >upload. >No file was uploaded, however. >Uploading patat_0.4.0.0-1_amd64.changes >Upload permissions error > > You either don't have the rights to upload a file, or, if this is on >ftp-master, you may have tried to overwrite a file already on the >server. > >Continuing anyway in case you want to recover from an incomplete >upload. >No file was uploaded, however. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: can't upload to mentors
On Fri, Nov 18, 2016 at 04:54:20PM +0100, Félix Sipma wrote: > After all it does not seem that it has been uploaded... > > I may have typed to fast "dput patat_0.4.0.0-1_amd64.changes" without > mentioning mentors. Anyway, it seems like the package is uploaded ftp-master > UploadQueue... Is it possible to verify if the package is there? Can I remove > it from there and upload it to mentors, so that I can ask for a sponsor for > this new version of the package? the default upload target (to call it somehow) for dput is ftp-master to avoid useless uploads to ftp-master you can overwrite the default target with random stuff $ cat ~/.dput.cf [DEFAULT] fqdn = dev.null incoming = /upload/c87718ea80a8bf3873f797e7adf794e1 default_host_main = dev.null -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa
Re: can't upload to mentors
On Wed, Nov 23, 2016 at 05:57:50PM +0100, Félix Sipma wrote: > At the end, it seems that there was an (unknown and not fixed) bug in debexpo. > > The workflow that worked was: > - do a source-only build of the package can i ask you why are you doing source-only uploads? i did a lot of binary+source uploads in the last days without an issue (after removing .buildinfo from .changes) -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa
Re: can't upload to mentors
On Thu, Nov 24, 2016 at 07:24:31AM +, Gianfranco Costamagna wrote: > Hi Gustavo, > > > >can i ask you why are you doing source-only uploads? > > > >i did a lot of binary+source uploads in the last days without an issue > >(after removing > >.buildinfo from .changes) > > > knowing that mentors discards binaries (and sponsors should do it anyway), > what is the > reason for uploading them, other than wasting bandwidth? :) to be honest, i don't have a good reason besides testing the resulting deb and that is my existing workflow i do sbuild or pdebuilder or export GIT_PBUILDER_OPTIONS=--twice ; export ARCH=amd64 ;export DIST=sid; \ gbp buildpackage --git-builder=git-pbuilder -d --git-verbose on top of a debian source tree and it always works, so why change? > > I think a source-only upload is more error-prone than a manual edit of > changes file, > and source-only have lots of reasons to exist, so why don't use them? :p i'm not sure i follow you here, but here goes my reasoning anyway ftp-master will request a binary upload, so why don't do the same for mentors since is the very thing you're going to be doing later down the road. i'd love if ftp-master accepted source only or even better discard the uploaded binaries, but is not the way it is today i'm very tempted to do uploads to debian using !amd64 binaries to be sure that the binary used by (most of the) users hasn't been build by me but a buildd! > > BTW congrats for your nm process end! > > Gianfranco -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa
Re: can't upload to mentors
On Thu, Nov 24, 2016 at 05:23:25PM +0100, Félix Sipma wrote: > On 2016-11-24 11:21+0800, gustavo panizzo (gfa) wrote: > > can i ask you why are you doing source-only uploads? > > > > i did a lot of binary+source uploads in the last days without an issue > > (after removing > > .buildinfo from .changes) > > Sure! > > - First I was told to remove the .buildinfo from the binary .changes and sign > it again, which did not work. i did this 3 or 4 times last week - delete all resulting files from previous builds but the orig.tar.gz, the result directory should only have the orig.tar.gz file before you start to build - sbuid/pbuilder/gbp to create a binary+source package - edit the .changes file to remove the .builinfo line - sign the .changes, debsign mypackage_1.8beta5+ds1-2_amd64.changes - upload to mentors, dput mentors mypackage_1.8beta5+ds1-2_amd64.changes if you want to upload again you have to wait until the crojob delete the files before upload connect to ftp://mentors.debian.net and check your files are not there - wait until the other cronjob accepts the package and sends you an email letting you know it worked :) - profit! :) i *think* you signed the .changes, edited and signed again. if you follow above's steps and keeps failing (remember to wait for the cronjobs...) paste the output of every command here and i'll help you. but it shouldn't, as i said i did it like 3 times last week > - Then I was told to do a source only upload, which did not work either. > - Then I was told to go to #debian-mentors to find what was going on, which > did > work: there appeared to be a (still present and not identified) bug in > debexpo. yeah, debexpo doesn't like .buildinfo files (maybe other bugs i'm not aware) good luck! -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa
when salvage a package?
Hello I was tempted to do a QA upload for ora2pg [0], which is nice software because helps people to move out from Oracle DB, but the popcon value is very low (< 12) [1] and the package has only one bug open, an automatic RC bug [2], that shows that doesn't have many users out there. The software is outdated, and the maintainer O the package. I wonder if salvaging the package is the right thing to do or should let it die or even RM after Stretch TL;DR I want to salvage a package but (maybe) nobody uses it, should I do salvage it anyway? [0] https://tracker.debian.org/pkg/ora2pg [1] https://qa.debian.org/popcon.php?package=ora2pg [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833249 -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa signature.asc Description: PGP signature
tool to rebuild all build-deps of a package
Hello Is there any tool I can use to rebuild all packages which B-D/D on my package? i want to do a local test before bumping it on the archive Extra points for running the autopkgtests (if any) thanks! PS: pkg is python-pytest-timeout -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa
Re: Build on hurd-i386 and kfreebsd-amd64 ... at home
On 2015-07-20 16:34, Johannes Schauer wrote: > > crossbuilding is not equal to native building. I think Daniel was looking for > a > way to test if their packages build natively on hurd-i386 or kfreebsd-amd64. > But crossbuilding from linux (which I'll just assume Daniel runs on their > host) > to hurd or kfreebsd will lead to different results than natively building on > these kernels in (probably) most cases. would that make the test useless? I build test using qemu-static- before upload to debian to avoid FTBFS when the package reach the buildd network i'm just starting to do it but it appears to work fine -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55ade13b.80...@zumbi.com.ar
Re: Build on hurd-i386 and kfreebsd-amd64 ... at home
On 2015-07-21 19:02, Johannes Schauer wrote: > Hi, > > Quoting gustavo panizzo (gfa) (2015-07-21 08:05:47) >> On 2015-07-20 16:34, Johannes Schauer wrote: >>> crossbuilding is not equal to native building. I think Daniel was looking >>> for a >>> way to test if their packages build natively on hurd-i386 or kfreebsd-amd64. >>> But crossbuilding from linux (which I'll just assume Daniel runs on their >>> host) >>> to hurd or kfreebsd will lead to different results than natively building on >>> these kernels in (probably) most cases. >> would that make the test useless? I build test using qemu-static- >> before upload to debian to avoid FTBFS when the package reach the buildd >> network > > are you using qemu-static- to build on linux for hurd or kfreebsd? no, in the quick test i did it didn't work (their binfmt appears to be the same) > > The *only* 100% sure way to know if your package builds on the buildds is... > to > upload and build your packages on the buildds. that's the thing i want to avoid, useless uploads > > The second best way is to build either on real hardware (your own or a > porterbox) or in a virtual machine which emulates a whole machine, including a > kernel. > > The third best way is to only emulate the architecture but not the kernel. > This > is what qemu-user does. This will probably let you run into kernel specific > problems. [ snip ] well what I do worked in the test I did, for example trinity 1.5-1 FTBFS on mips, mipsel and sparc due a missing include header, that i could catch using qemu-static-XXX. I agree that more complex interactions between the userspace and the kernel may not work. I tough that qemu-static-XXX would be better than you show, but hey! I didn't load a kernel so it is kinda expected I didn't want to but I think i will create a set of vm, one for each debian arch, and automate the build on it, I looked how to create a buildd machine but is think is too much. I will stick to libvirt+scripts to launch the build on different arch. :( i didn't want to use more vm, pbuilder is so cool and easy to maintain > > And sure, if your package does noting fancy but just calls cp a couple of > times > to put everything in the right location, then nothing will go wrong with the > qemu-user method. But if your package is that simple, then you probably also > don't need to test it. again, dependencies and includes sometimes are different across arch, that could be spotted > > cheers, josch > cheers -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55af07f5.60...@zumbi.com.ar
